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.3.4.8 - 2018-09-10
6 Tor 0.3.4.8 is the first stable release in its series; it includes
7 compilation and portability fixes.
9 The Tor 0.3.4 series includes improvements for running Tor in
10 low-power and embedded environments, which should help performance in
11 general. We've begun work on better modularity, and included preliminary
12 changes on the directory authority side to accommodate a new bandwidth
13 measurement system. We've also integrated more continuous-integration
14 systems into our development process, and made corresponding changes to
15 Tor's testing infrastructure. Finally, we've continued to refine
16 our anti-denial-of-service code.
18 Below are the changes since 0.3.3.9. For a list of only the changes
19 since 0.3.4.7-rc, see the ChangeLog file.
21 o New system requirements:
22 - Tor no longer tries to support old operating systems without
23 mmap() or some local equivalent. Apparently, compilation on such
24 systems has been broken for some time, without anybody noticing or
25 complaining. Closes ticket 25398.
27 o Major features (directory authority, modularization):
28 - The directory authority subsystem has been modularized. The code
29 is now located in src/or/dirauth/, and is compiled in by default.
30 To disable the module, the configure option
31 --disable-module-dirauth has been added. This module may be
32 disabled by default in some future release. Closes ticket 25610.
34 o Major features (main loop, CPU usage):
35 - When Tor is disabled (via DisableNetwork or via hibernation), it
36 no longer needs to run any per-second events. This change should
37 make it easier for mobile applications to disable Tor while the
38 device is sleeping, or Tor is not running. Closes ticket 26063.
39 - Tor no longer enables all of its periodic events by default.
40 Previously, Tor would enable all possible main loop events,
41 regardless of whether it needed them. Furthermore, many of these
42 events are now disabled when Tor is hibernating or DisableNetwork
43 is set. This is a big step towards reducing client CPU usage by
44 reducing the amount of wake-ups the daemon does. Closes tickets
46 - The bandwidth-limitation logic has been refactored so that
47 bandwidth calculations are performed on-demand, rather than every
48 TokenBucketRefillInterval milliseconds. This change should improve
49 the granularity of our bandwidth calculations, and limit the
50 number of times that the Tor process needs to wake up when it is
51 idle. Closes ticket 25373.
52 - Move responsibility for many operations from a once-per-second
53 callback to a callback that is only scheduled as needed. Moving
54 this functionality has allowed us to disable the callback when
55 Tor's network is disabled. Once enough items are removed from our
56 once-per-second callback, we can eliminate it entirely to conserve
57 CPU when idle. The functionality removed includes: closing
58 connections, circuits, and channels (ticket 25932); consensus
59 voting (25937); flushing log callbacks (25951); honoring delayed
60 SIGNEWNYM requests (25949); rescanning the consensus cache
61 (25931); saving the state file to disk (25948); warning relay
62 operators about unreachable ports (25952); and keeping track of
65 o Minor features (accounting):
66 - When Tor becomes dormant, it now uses a scheduled event to wake up
67 at the right time. Previously, we would use the per-second timer
68 to check whether to wake up, but we no longer have any per-second
69 timers enabled when the network is disabled. Closes ticket 26064.
71 o Minor features (bug workaround):
72 - Compile correctly on systems that provide the C11 stdatomic.h
73 header, but where C11 atomic functions don't actually compile.
74 Closes ticket 26779; workaround for Debian issue 903709.
76 o Minor features (code quality):
77 - Add optional spell-checking for the Tor codebase, using the
78 "misspell" program. To use this feature, run "make check-typos".
81 o Minor features (compatibility):
82 - Tell OpenSSL to maintain backward compatibility with previous
83 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
84 ciphers are disabled by default. Closes ticket 27344.
85 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
86 the no-deprecated option, and builds correctly with them. Closes
87 tickets 19429, 19981, and 25353.
89 o Minor features (compilation):
90 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
91 tell the compiler not to include the system malloc implementation.
92 Fixes bug 20424; bugfix on 0.2.0.20-rc.
93 - Don't try to use a pragma to temporarily disable the
94 -Wunused-const-variable warning if the compiler doesn't support
95 it. Fixes bug 26785; bugfix on 0.3.2.11.
96 - When building Tor, prefer to use Python 3 over Python 2, and more
97 recent (contemplated) versions over older ones. Closes
100 o Minor features (compression, zstd):
101 - When running with zstd, Tor now considers using advanced functions
102 that the zstd maintainers have labeled as potentially unstable. To
103 prevent breakage, Tor will only use this functionality when the
104 runtime version of the zstd library matches the version with which
105 Tor was compiled. Closes ticket 25162.
107 o Minor features (configuration):
108 - The "DownloadSchedule" options have been renamed to end with
109 "DownloadInitialDelay". The old names are still allowed, but will
110 produce a warning. Comma-separated lists are still permitted for
111 these options, but all values after the first are ignored (as they
112 have been since 0.2.9). Closes ticket 23354.
114 o Minor features (continuous integration):
115 - Log the compiler path and version during Appveyor builds.
116 Implements ticket 27449.
117 - Show config.log and test-suite.log after failed Appveyor builds.
118 Also upload the zipped full logs as a build artifact. Implements
120 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
121 - Enable macOS builds in our Travis CI configuration. Closes
123 - Install libcap-dev and libseccomp2-dev so these optional
124 dependencies get tested on Travis CI. Closes ticket 26560.
125 - Only post Appveyor IRC notifications when the build fails.
126 Implements ticket 27275.
127 - Run asciidoc during Travis CI. Implements ticket 27087.
128 - Use ccache in our Travis CI configuration. Closes ticket 26952.
129 - Add the necessary configuration files for continuous integration
130 testing on Windows, via the Appveyor platform. Closes ticket
131 25549. Patches from Marcin Cieślak and Isis Lovecruft.
133 o Minor features (continuous integration, rust):
134 - Use cargo cache in our Travis CI configuration. Closes
137 o Minor features (control port):
138 - Introduce GETINFO "current-time/{local,utc}" to return the local
139 and UTC times respectively in ISO format. This helps a controller
140 like Tor Browser detect a time-related error. Closes ticket 25511.
141 Patch by Neel Chauhan.
142 - Introduce new fields to the CIRC_BW event. There are two new
143 fields in each of the read and written directions. The DELIVERED
144 fields report the total valid data on the circuit, as measured by
145 the payload sizes of verified and error-checked relay command
146 cells. The OVERHEAD fields report the total unused bytes in each
147 of these cells. Closes ticket 25903.
149 o Minor features (controller):
150 - The control port now exposes the list of HTTPTunnelPorts and
151 ExtOrPorts via GETINFO net/listeners/httptunnel and
152 net/listeners/extor respectively. Closes ticket 26647.
154 o Minor features (directory authorities):
155 - Stop warning about incomplete bw lines before the first complete
156 bw line has been found, so that additional header lines can be
157 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
158 - Authorities no longer vote to make the subprotocol version
159 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
160 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
162 o Minor features (directory authority):
163 - Directory authorities now open their key-pinning files as O_SYNC,
164 to limit their chances of accidentally writing partial lines.
167 o Minor features (directory authority, forward compatibility):
168 - Make the lines of the measured bandwidth file able to contain
169 their entries in any order. Previously, the node_id entry needed
170 to come first. Closes ticket 26004.
172 o Minor features (entry guards):
173 - Introduce a new torrc option NumPrimaryGuards for controlling the
174 number of primary guards. Closes ticket 25843.
176 o Minor features (geoip):
177 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
178 Country database. Closes ticket 27089.
180 o Minor features (performance):
181 - Avoid a needless call to malloc() when processing an incoming
182 relay cell. Closes ticket 24914.
183 - Make our timing-wheel code run a tiny bit faster on 32-bit
184 platforms, by preferring 32-bit math to 64-bit. Closes
186 - Avoid a needless malloc()/free() pair every time we handle an ntor
187 handshake. Closes ticket 25150.
189 o Minor features (Rust, portability):
190 - Rust cross-compilation is now supported. Closes ticket 25895.
192 o Minor features (testing):
193 - Add a unit test for voting_schedule_get_start_of_next_interval().
194 Closes ticket 26014, and helps make unit test coverage
196 - A new unittests module specifically for testing the functions in
197 the (new-ish) bridges.c module has been created with new
198 unittests, raising the code coverage percentages. Closes 25425.
199 - We now have improved testing for addressmap_get_virtual_address()
200 function. This should improve our test coverage, and make our test
201 coverage more deterministic. Closes ticket 25993.
203 o Minor features (timekeeping, circuit scheduling):
204 - When keeping track of how busy each circuit have been recently on
205 a given connection, use coarse-grained monotonic timers rather
206 than gettimeofday(). This change should marginally increase
207 accuracy and performance. Implements part of ticket 25927.
209 o Minor features (unit tests):
210 - Test complete bandwidth measurements files, and test that
211 incomplete bandwidth lines only give warnings when the end of the
212 header has not been detected. Fixes bug 25947; bugfix
215 o Minor bugfixes (bandwidth management):
216 - Consider ourselves "low on write bandwidth" if we have exhausted
217 our write bandwidth some time in the last second. This was the
218 documented behavior before, but the actual behavior was to change
219 this value every TokenBucketRefillInterval. Fixes bug 25828;
220 bugfix on 0.2.3.5-alpha.
222 o Minor bugfixes (C correctness):
223 - Add a missing lock acquisition in the shutdown code of the control
224 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
225 Coverity; this is CID 1433643.
227 o Minor bugfixes (code style):
228 - Fixed multiple includes of transports.h in src/or/connection.c
229 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
230 - Remove the unused variable n_possible from the function
231 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
233 o Minor bugfixes (compilation):
234 - Silence a spurious compiler warning on the GetAdaptersAddresses
235 function pointer cast. This issue is already fixed by 26481 in
236 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
237 bugfix on 0.2.3.11-alpha.
238 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
239 supported, and always fails. Some compilers warn about the
240 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
242 - Fix a compilation warning on some versions of GCC when building
243 code that calls routerinfo_get_my_routerinfo() twice, assuming
244 that the second call will succeed if the first one did. Fixes bug
245 26269; bugfix on 0.2.8.2-alpha.
246 - Refrain from compiling unit testing related object files when
247 --disable-unittests is set to configure script. Fixes bug 24891;
248 bugfix on 0.2.5.1-alpha.
249 - The --enable-fatal-warnings flag now affects Rust code as well.
251 - Avoid a compiler warning when casting the return value of
252 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
253 26283; bugfix on 0.2.4.10-alpha.
255 o Minor bugfixes (compilation, windows):
256 - Don't link or search for pthreads when building for Windows, even
257 if we are using build environment (like mingw) that provides a
258 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
260 o Minor bugfixes (continuous integration):
261 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
262 - Skip a pair of unreliable key generation tests on Windows, until
263 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
264 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
266 o Minor bugfixes (control port):
267 - Respond with more human-readable error messages to GETINFO exit-
268 policy/* requests. Also, let controller know if an error is
269 transient (response code 551) or not (response code 552). Fixes
270 bug 25852; bugfix on 0.2.8.1-alpha.
271 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
272 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
273 on 0.3.3.1-alpha. Patch by "akwizgran".
274 - Make CIRC_BW event reflect the total of all data sent on a
275 circuit, including padding and dropped cells. Also fix a mis-
276 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
277 bugfix on 0.2.5.2-alpha.
279 o Minor bugfixes (correctness, flow control):
280 - Upon receiving a stream-level SENDME cell, verify that our window
281 has not grown too large. Fixes bug 26214; bugfix on svn
284 o Minor bugfixes (directory authority):
285 - When voting for recommended versions, make sure that all of the
286 versions are well-formed and parsable. Fixes bug 26485; bugfix
289 o Minor bugfixes (directory client):
290 - When unverified-consensus is verified, rename it to cached-
291 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
292 - Fixed launching a certificate fetch always during the scheduled
293 periodic consensus fetch by fetching only in those cases when
294 consensus are waiting for certs. Fixes bug 24740; bugfix
297 o Minor bugfixes (error reporting):
298 - Improve tolerance for directory authorities with skewed clocks.
299 Previously, an authority with a clock more than 60 seconds ahead
300 could cause a client with a correct clock to warn that the
301 client's clock was behind. Now the clocks of a majority of
302 directory authorities have to be ahead of the client before this
303 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
305 o Minor bugfixes (in-process restart):
306 - Always call tor_free_all() when leaving tor_run_main(). When we
307 did not, restarting tor in-process would cause an assertion
308 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
310 o Minor bugfixes (Linux seccomp2 sandbox):
311 - Fix a bug in our sandboxing rules for the openat() syscall.
312 Previously, no openat() call would be permitted, which would break
313 filesystem operations on recent glibc versions. Fixes bug 25440;
314 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
316 o Minor bugfixes (logging):
317 - Improve the log message when connection initiators fail to
318 authenticate direct connections to relays. Fixes bug 26927; bugfix
321 o Minor bugfixes (onion services):
322 - Silence a spurious compiler warning in
323 rend_client_send_introduction(). Fixes bug 27463; bugfix
325 - Fix bug that causes services to not ever rotate their descriptors
326 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
328 - Recompute some consensus information after detecting a clock jump,
329 or after transitioning from a non-live consensus to a live
330 consensus. We do this to avoid having an outdated state, and
331 miscalculating the index for next-generation onion services. Fixes
332 bug 24977; bugfix on 0.3.2.1-alpha.
334 o Minor bugfixes (portability):
335 - Fix compilation of the unit tests on GNU/Hurd, which does not
336 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
338 - Work around two different bugs in the OS X 10.10 and later SDKs
339 that would prevent us from successfully targeting earlier versions
340 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
341 - Do not align mmap length, as it is not required by POSIX, and the
342 getpagesize function is deprecated. Fixes bug 25399; bugfix
345 o Minor bugfixes (portability, FreeBSD):
346 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
347 does not stringify on FreeBSD, so we switch to tor_asprintf().
348 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
350 o Minor bugfixes (relay statistics):
351 - When a relay is collecting internal statistics about how many
352 create cell requests it has seen of each type, accurately count
353 the requests from relays that temporarily fall out of the
354 consensus. (To be extra conservative, we were already ignoring
355 requests from clients in our counts, and we continue ignoring them
356 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
358 o Minor bugfixes (rust):
359 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
361 - Protover parsing was accepting the presence of whitespace in
362 version strings, which the C implementation would choke on, e.g.
363 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
364 - Protover parsing was ignoring a 2nd hyphen and everything after
365 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
367 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
368 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
369 - cd to ${abs_top_builddir}/src/rust before running cargo in
370 src/test/test_rust.sh. This makes the working directory consistent
371 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
373 o Minor bugfixes (single onion services, Tor2web):
374 - Log a protocol warning when single onion services or Tor2web
375 clients fail to authenticate direct connections to relays. Fixes
376 bug 26924; bugfix on 0.2.9.1-alpha.
378 o Minor bugfixes (test coverage tools):
379 - Update our "cov-diff" script to handle output from the latest
380 version of gcov, and to remove extraneous timestamp information
381 from its output. Fixes bugs 26101 and 26102; bugfix
384 o Minor bugfixes (testing):
385 - Disable core dumps in test_bt.sh, to avoid failures in "make
386 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
387 - When testing workqueue event-cancellation, make sure that we
388 actually cancel an event, and that cancel each event with equal
389 probability. (It was previously possible, though extremely
390 unlikely, for our event-canceling test not to cancel any events.)
391 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
392 - Repeat part of the test in test_client_pick_intro() a number of
393 times, to give it consistent coverage. Fixes bug 25996; bugfix
395 - Remove randomness from the hs_common/responsible_hsdirs test, so
396 that it always takes the same path through the function it tests.
397 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
398 - Change the behavior of the "channel/outbound" test so that it
399 never causes a 10-second rollover for the EWMA circuitmux code.
400 Previously, this behavior would happen randomly, and result in
401 fluctuating test coverage. Fixes bug 25994; bugfix
403 - Use X509_new() to allocate certificates that will be freed later
404 with X509_free(). Previously, some parts of the unit tests had
405 used tor_malloc_zero(), which is incorrect, and which caused test
406 failures on Windows when they were built with extra hardening.
407 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
409 - While running the circuit_timeout test, fix the PRNG to a
410 deterministic AES stream, so that the test coverage from this test
411 will itself be deterministic. Fixes bug 25995; bugfix
414 o Minor bugfixes (testing, bootstrap):
415 - When calculating bootstrap progress, check exit policies and the
416 exit flag. Previously, Tor would only check the exit flag, which
417 caused race conditions in small and fast networks like chutney.
418 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
420 o Minor bugfixes (testing, chutney):
421 - When running make test-network-all, use the mixed+hs-v2 network.
422 (A previous fix to chutney removed v3 onion services from the
423 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
424 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
425 - Before running make test-network-all, delete old logs and test
426 result files, to avoid spurious failures. Fixes bug 27295; bugfix
429 o Minor bugfixes (testing, openssl compatibility):
430 - Our "tortls/cert_matches_key" unit test no longer relies on
431 OpenSSL internals. Previously, it relied on unsupported OpenSSL
432 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
433 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
435 o Minor bugfixes (v3 onion services):
436 - Stop sending ed25519 link specifiers in v3 onion service introduce
437 cells and descriptors, when the rendezvous or introduction point
438 doesn't support ed25519 link authentication. Fixes bug 26627;
439 bugfix on 0.3.2.4-alpha.
441 o Minor bugfixes (vanguards):
442 - Allow the last hop in a vanguard circuit to be the same as our
443 first, to prevent the adversary from influencing guard node choice
444 by choice of last hop. Also prevent the creation of A - B - A
445 paths, or A - A paths, which are forbidden by relays. Fixes bug
446 25870; bugfix on 0.3.3.1-alpha.
448 o Minor bugfixes (Windows, compilation):
449 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
450 27185; bugfix on 0.2.2.2-alpha.
452 o Code simplification and refactoring:
453 - Remove duplicate code in parse_{c,s}method_line and bootstrap
454 their functionalities into a single function. Fixes bug 6236;
455 bugfix on 0.2.3.6-alpha.
456 - We remove the PortForwsrding and PortForwardingHelper options,
457 related functions, and the port_forwarding tests. These options
458 were used by the now-deprecated Vidalia to help ordinary users
459 become Tor relays or bridges. Closes ticket 25409. Patch by
461 - In order to make the OR and dir checking function in router.c less
462 confusing we renamed some functions and
463 consider_testing_reachability() has been split into
464 router_should_check_reachability() and
465 router_do_reachability_checks(). Also we improved the documentation
466 in some functions. Closes ticket 18918.
467 - Initial work to isolate Libevent usage to a handful of modules in
468 our codebase, to simplify our call structure, and so that we can
469 more easily change event loops in the future if needed. Closes
471 - Introduce a function to call getsockname() and return tor_addr_t,
472 to save a little complexity throughout the codebase. Closes
474 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
475 as hsdir_index is always present. Also, we move hsdir_index_t into
476 or.h. Closes ticket 23094. Patch by Neel Chauhan.
477 - Merge functions used for describing nodes and suppress the
478 functions that do not allocate memory for the output buffer
479 string. NODE_DESC_BUF_LEN constant and format_node_description()
480 function cannot be used externally from router.c module anymore.
481 Closes ticket 25432. Patch by valentecaio.
482 - Our main loop has been simplified so that all important operations
483 happen inside events. Previously, some operations had to happen
484 outside the event loop, to prevent infinite sequences of event
485 activations. Closes ticket 25374.
486 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
487 it in register_intro_circ() and service_intro_point_new(). This
488 prevents the digest from being re-calculated each time. Closes
489 ticket 23107. Patch by Neel Chauhan.
490 - Refactor token-bucket implementations to use a common backend.
492 - Remove extern declaration of stats_n_seconds_working variable from
493 main, protecting its accesses with get_uptime() and reset_uptime()
494 functions. Closes ticket 25081, patch by “valentecaio”.
495 - Remove our previous logic for "cached gettimeofday()" -- our
496 coarse monotonic timers are fast enough for this purpose, and far
497 less error-prone. Implements part of ticket 25927.
498 - Remove the return value for fascist_firewall_choose_address_base(),
499 and sister functions such as fascist_firewall_choose_address_node()
500 and fascist_firewall_choose_address_rs(). Also, while we're here,
501 initialize the ap argument as leaving it uninitialized can pose a
502 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
503 - Rename two fields of connection_t struct. timestamp_lastwritten is
504 renamed to timestamp_last_write_allowed and timestamp_lastread is
505 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
507 - Since Tor requires C99, remove our old workaround code for libc
508 implementations where free(NULL) doesn't work. Closes ticket 24484.
509 - Use our standard rate-limiting code to deal with excessive
510 libevent failures, rather than the hand-rolled logic we had
511 before. Closes ticket 26016.
512 - We remove the return value of node_get_prim_orport() and
513 node_get_prim_dirport(), and introduce node_get_prim_orport() in
514 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
515 check for a null address. Closes ticket 23873. Patch by
517 - We switch to should_record_bridge_info() in
518 geoip_note_client_seen() and options_need_geoip_info() instead of
519 accessing the configuration values directly. Fixes bug 25290;
520 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
522 o Deprecated features:
523 - As we are not recommending 0.2.5 anymore, we require relays that
524 once had an ed25519 key associated with their RSA key to always
525 have that key, instead of allowing them to drop back to a version
526 that didn't support ed25519. This means they need to use a new RSA
527 key if the want to downgrade to an older version of tor without
528 ed25519. Closes ticket 20522.
531 - Directory authorities will no longer support voting according to
532 any consensus method before consensus method 25. This keeps
533 authorities compatible with all authorities running 0.2.9.8 and
534 later, and does not break any clients or relays. Implements ticket
535 24378 and proposal 290.
536 - The PortForwarding and PortForwardingHelper features have been
537 removed. The reasoning is, given that implementations of NAT
538 traversal protocols within common consumer grade routers are
539 frequently buggy, and that the target audience for a NAT punching
540 feature is a perhaps less-technically-inclined relay operator,
541 when the helper fails to setup traversal the problems are usually
542 deep, ugly, and very router specific, making them horrendously
543 impossible for technical support to reliable assist with, and thus
544 resulting in frustration all around. Unfortunately, relay
545 operators who would like to run relays behind NATs will need to
546 become more familiar with the port forwarding configurations on
547 their local router. Closes 25409.
548 - The TestingEnableTbEmptyEvent option has been removed. It was used
549 in testing simulations to measure how often connection buckets
550 were emptied, in order to improve our scheduling, but it has not
551 been actively used in years. Closes ticket 25760.
552 - The old "round-robin" circuit multiplexer (circuitmux)
553 implementation has been removed, along with a fairly large set of
554 code that existed to support it. It has not been the default
555 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
556 but it still required an unreasonable amount of memory and CPU.
560 Changes in version 0.3.3.9 - 2018-07-13
561 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
562 bridge relays should upgrade.
564 o Directory authority changes:
565 - The "Bifroest" bridge authority has been retired; the new bridge
566 authority is "Serge", and it is operated by George from the
567 TorBSD project. Closes ticket 26771.
570 Changes in version 0.3.2.11 - 2018-07-13
571 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
572 bridge relays should upgrade. We also take this opportunity to backport
575 o Directory authority changes:
576 - The "Bifroest" bridge authority has been retired; the new bridge
577 authority is "Serge", and it is operated by George from the
578 TorBSD project. Closes ticket 26771.
580 o Directory authority changes (backport from 0.3.3.7):
581 - Add an IPv6 address for the "dannenberg" directory authority.
584 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
585 - When directory authorities read a zero-byte bandwidth file, they
586 would previously log a warning with the contents of an
587 uninitialised buffer. They now log a warning about the empty file
588 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
590 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
591 - Correctly detect when onion services get disabled after HUP. Fixes
592 bug 25761; bugfix on 0.3.2.1.
594 o Minor features (sandbox, backport from 0.3.3.4-alpha):
595 - Explicitly permit the poll() system call when the Linux
596 seccomp2-based sandbox is enabled: apparently, some versions of
597 libc use poll() when calling getpwnam(). Closes ticket 25313.
599 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
600 - Update the Travis CI configuration to use the stable Rust channel,
601 now that we have decided to require that. Closes ticket 25714.
603 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
604 - Our .travis.yml configuration now includes support for testing the
605 results of "make distcheck". (It's not uncommon for "make check"
606 to pass but "make distcheck" to fail.) Closes ticket 25814.
607 - Our Travis CI configuration now integrates with the Coveralls
608 coverage analysis tool. Closes ticket 25818.
610 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
611 - Add several checks to detect whether Tor relays are uploading
612 their descriptors without specifying why they regenerated them.
613 Diagnostic for ticket 25686.
615 o Minor features (compilation, backport from 0.3.4.4-rc):
616 - When building Tor, prefer to use Python 3 over Python 2, and more
617 recent (contemplated) versions over older ones. Closes
620 o Minor features (geoip):
621 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
622 Country database. Closes ticket 26674.
624 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
625 - Upon receiving a malformed connected cell, stop processing the
626 cell immediately. Previously we would mark the connection for
627 close, but continue processing the cell as if the connection were
628 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
630 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
631 - Allow the nanosleep() system call, which glibc uses to implement
632 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
634 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
635 - When running the hs_ntor_ref.py test, make sure only to pass
636 strings (rather than "bytes" objects) to the Python subprocess
637 module. Python 3 on Windows seems to require this. Fixes bug
638 26535; bugfix on 0.3.1.1-alpha.
639 - When running the ntor_ref.py test, make sure only to pass strings
640 (rather than "bytes" objects) to the Python subprocess module.
641 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
644 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
645 - Work around a change in OpenSSL 1.1.1 where return values that
646 would previously indicate "no password" now indicate an empty
647 password. Without this workaround, Tor instances running with
648 OpenSSL 1.1.1 would accept descriptors that other Tor instances
649 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
651 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
652 - Document that the PerConnBW{Rate,Burst} options will fall back to
653 their corresponding consensus parameters only if those parameters
654 are set. Previously we had claimed that these values would always
655 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
657 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
658 - Fix a compilation warning on some versions of GCC when building
659 code that calls routerinfo_get_my_routerinfo() twice, assuming
660 that the second call will succeed if the first one did. Fixes bug
661 26269; bugfix on 0.2.8.2-alpha.
663 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
664 - Don't consider Tor running as a client if the ControlPort is open,
665 but no actual client ports are open. Fixes bug 26062; bugfix
668 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
669 - Prevent a possible out-of-bounds smartlist read in
670 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
672 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
673 - Fix a very unlikely (impossible, we believe) null pointer
674 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
675 Coverity; this is CID 1430932.
677 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
678 - Fix a memory leak when a v3 onion service is configured and gets a
679 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
680 - When parsing the descriptor signature, look for the token plus an
681 extra white-space at the end. This is more correct but also will
682 allow us to support new fields that might start with "signature".
683 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
685 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
686 - Relays now correctly block attempts to re-extend to the previous
687 relay by Ed25519 identity. Previously they would warn in this
688 case, but not actually reject the attempt. Fixes bug 26158; bugfix
691 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
692 - Avoid a crash when running with DirPort set but ORPort turned off.
693 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
695 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
696 - Silence unused-const-variable warnings in zstd.h with some GCC
697 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
699 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
700 - Avoid intermittent test failures due to a test that had relied on
701 onion service introduction point creation finishing within 5
702 seconds of real clock time. Fixes bug 25450; bugfix
705 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
706 - Fix a C99 compliance issue in our configuration script that caused
707 compilation issues when compiling Tor with certain versions of
708 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
710 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
711 - Fix a number of small memory leaks identified by coverity. Fixes
712 bug 26467; bugfix on numerous Tor versions.
714 o Code simplification and refactoring (backport from 0.3.3.5-rc):
715 - Move the list of default directory authorities to its own file.
716 Closes ticket 24854. Patch by "beastr0".
719 Changes in version 0.2.9.16 - 2018-07-13
720 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
721 bridge relays should upgrade. We also take this opportunity to backport
724 o Directory authority changes:
725 - The "Bifroest" bridge authority has been retired; the new bridge
726 authority is "Serge", and it is operated by George from the
727 TorBSD project. Closes ticket 26771.
729 o Directory authority changes (backport from 0.3.3.7):
730 - Add an IPv6 address for the "dannenberg" directory authority.
733 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
734 - When directory authorities read a zero-byte bandwidth file, they
735 would previously log a warning with the contents of an
736 uninitialised buffer. They now log a warning about the empty file
737 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
739 o Minor features (sandbox, backport from 0.3.3.4-alpha):
740 - Explicitly permit the poll() system call when the Linux
741 seccomp2-based sandbox is enabled: apparently, some versions of
742 libc use poll() when calling getpwnam(). Closes ticket 25313.
744 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
745 - Our .travis.yml configuration now includes support for testing the
746 results of "make distcheck". (It's not uncommon for "make check"
747 to pass but "make distcheck" to fail.) Closes ticket 25814.
748 - Our Travis CI configuration now integrates with the Coveralls
749 coverage analysis tool. Closes ticket 25818.
751 o Minor features (compilation, backport from 0.3.4.4-rc):
752 - When building Tor, prefer to use Python 3 over Python 2, and more
753 recent (contemplated) versions over older ones. Closes
756 o Minor features (geoip):
757 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
758 Country database. Closes ticket 26674.
760 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
761 - Upon receiving a malformed connected cell, stop processing the
762 cell immediately. Previously we would mark the connection for
763 close, but continue processing the cell as if the connection were
764 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
766 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
767 - Allow the nanosleep() system call, which glibc uses to implement
768 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
770 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
771 - When running the ntor_ref.py test, make sure only to pass strings
772 (rather than "bytes" objects) to the Python subprocess module.
773 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
776 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
777 - Work around a change in OpenSSL 1.1.1 where return values that
778 would previously indicate "no password" now indicate an empty
779 password. Without this workaround, Tor instances running with
780 OpenSSL 1.1.1 would accept descriptors that other Tor instances
781 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
783 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
784 - Fix a compilation warning on some versions of GCC when building
785 code that calls routerinfo_get_my_routerinfo() twice, assuming
786 that the second call will succeed if the first one did. Fixes bug
787 26269; bugfix on 0.2.8.2-alpha.
789 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
790 - Don't consider Tor running as a client if the ControlPort is open,
791 but no actual client ports are open. Fixes bug 26062; bugfix
794 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
795 - Prevent a possible out-of-bounds smartlist read in
796 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
798 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
799 - Fix a very unlikely (impossible, we believe) null pointer
800 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
801 Coverity; this is CID 1430932.
803 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
804 - Fix a number of small memory leaks identified by coverity. Fixes
805 bug 26467; bugfix on numerous Tor versions.
807 o Code simplification and refactoring (backport from 0.3.3.5-rc):
808 - Move the list of default directory authorities to its own file.
809 Closes ticket 24854. Patch by "beastr0".
812 Changes in version 0.3.3.8 - 2018-07-09
813 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
814 fixes for a memory leak affecting directory authorities.
816 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
817 - Stop leaking memory on directory authorities when planning to
818 vote. This bug was crashing authorities by exhausting their
819 memory. Fixes bug 26435; bugfix on 0.3.3.6.
821 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
822 - Make sure that failing tests in Rust will actually cause the build
823 to fail: previously, they were ignored. Fixes bug 26258; bugfix
826 o Minor features (compilation, backport from 0.3.4.4-rc):
827 - When building Tor, prefer to use Python 3 over Python 2, and more
828 recent (contemplated) versions over older ones. Closes
831 o Minor features (geoip):
832 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
833 Country database. Closes ticket 26674.
835 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
836 - Add several checks to detect whether Tor relays are uploading
837 their descriptors without specifying why they regenerated them.
838 Diagnostic for ticket 25686.
840 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
841 - Don't count path selection failures as circuit build failures.
842 This change should eliminate cases where Tor blames its guard or
843 the network for situations like insufficient microdescriptors
844 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
847 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
848 - Fix a compilation warning on some versions of GCC when building
849 code that calls routerinfo_get_my_routerinfo() twice, assuming
850 that the second call will succeed if the first one did. Fixes bug
851 26269; bugfix on 0.2.8.2-alpha.
853 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
854 - Handle the HSADDRESS= argument to the HSPOST command properly.
855 (Previously, this argument was misparsed and thus ignored.) Fixes
856 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
858 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
859 - Fix a number of small memory leaks identified by coverity. Fixes
860 bug 26467; bugfix on numerous Tor versions.
862 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
863 - Relays now correctly block attempts to re-extend to the previous
864 relay by Ed25519 identity. Previously they would warn in this
865 case, but not actually reject the attempt. Fixes bug 26158; bugfix
868 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
869 - When shutting down, Tor now clears all the flags in the control.c
870 module. This should prevent a bug where authentication cookies are
871 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
873 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
874 - When running the hs_ntor_ref.py test, make sure only to pass
875 strings (rather than "bytes" objects) to the Python subprocess
876 module. Python 3 on Windows seems to require this. Fixes bug
877 26535; bugfix on 0.3.1.1-alpha.
878 - When running the ntor_ref.py test, make sure only to pass strings
879 (rather than "bytes" objects) to the Python subprocess module.
880 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
884 Changes in version 0.3.3.7 - 2018-06-12
885 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
886 fixes for bugs affecting compatibility and stability.
888 o Directory authority changes:
889 - Add an IPv6 address for the "dannenberg" directory authority.
892 o Minor features (geoip):
893 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
894 Country database. Closes ticket 26351.
896 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
897 - Work around a change in OpenSSL 1.1.1 where return values that
898 would previously indicate "no password" now indicate an empty
899 password. Without this workaround, Tor instances running with
900 OpenSSL 1.1.1 would accept descriptors that other Tor instances
901 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
903 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
904 - Silence unused-const-variable warnings in zstd.h with some GCC
905 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
907 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
908 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
909 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
910 miscounting the total number of circuits for these field values.)
911 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
913 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
914 - Prevent a possible out-of-bounds smartlist read in
915 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
917 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
918 - Only select relays when they have the descriptors we prefer to use
919 for them. This change fixes a bug where we could select a relay
920 because it had _some_ descriptor, but reject it later with a
921 nonfatal assertion error because it didn't have the exact one we
922 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
925 Changes in version 0.3.3.6 - 2018-05-22
926 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
927 backports several important fixes from the 0.3.4.1-alpha.
929 The Tor 0.3.3 series includes controller support and other
930 improvements for v3 onion services, official support for embedding Tor
931 within other applications, and our first non-trivial module written in
932 the Rust programming language. (Rust is still not enabled by default
933 when building Tor.) And as usual, there are numerous other smaller
934 bugfixes, features, and improvements.
936 Below are the changes since 0.3.2.10. For a list of only the changes
937 since 0.3.3.5-rc, see the ChangeLog file.
939 o New system requirements:
940 - When built with Rust, Tor now depends on version 0.2.39 of the
941 libc crate. Closes tickets 25310 and 25664.
943 o Major features (embedding):
944 - There is now a documented stable API for programs that need to
945 embed Tor. See tor_api.h for full documentation and known bugs.
947 - Tor now has support for restarting in the same process.
948 Controllers that run Tor using the "tor_api.h" interface can now
949 restart Tor after Tor has exited. This support is incomplete,
950 however: we fixed crash bugs that prevented it from working at
951 all, but many bugs probably remain, including a possibility of
952 security issues. Implements ticket 24581.
954 o Major features (IPv6, directory documents):
955 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
956 consensus. This information makes it easier for IPv6 clients to
957 bootstrap and choose reachable entry guards. Implements
959 - Add consensus method 28, which removes IPv6 ORPorts from
960 microdescriptors. Now that the consensus contains IPv6 ORPorts,
961 they are redundant in microdescs. This change will be used by Tor
962 clients on 0.2.8.x and later. (That is to say, with all Tor
963 clients that have IPv6 bootstrap and guard support.) Implements
965 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
966 set by different numbers of authorities. Fixes 23870
969 o Major features (onion service v3, control port):
970 - The control port now supports commands and events for v3 onion
971 services. It is now possible to create ephemeral v3 services using
972 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
973 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
974 DEL_ONION) have been extended to support v3 onion services. Closes
975 ticket 20699; implements proposal 284.
977 o Major features (onion services):
978 - Provide torrc options to pin the second and third hops of onion
979 service circuits to a list of nodes. The option HSLayer2Guards
980 pins the second hop, and the option HSLayer3Guards pins the third
981 hop. These options are for use in conjunction with experiments
982 with "vanguards" for preventing guard enumeration attacks. Closes
984 - When v3 onion service clients send introduce cells, they now
985 include the IPv6 address of the rendezvous point, if it has one.
986 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
987 in future Tor versions, IPv6-only v3 single onion services will be
988 able to use IPv6 addresses to connect directly to the rendezvous
989 point. Closes ticket 23577. Patch by Neel Chauhan.
991 o Major features (relay):
992 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
993 operator to use a more reasonable ("reduced") exit policy, rather
994 than the default one. If you want to run an exit node without
995 thinking too hard about which ports to allow, this one is for you.
996 Closes ticket 13605. Patch from Neel Chauhan.
998 o Major features (rust, portability, experimental):
999 - Tor now ships with an optional implementation of one of its
1000 smaller modules (protover.c) in the Rust programming language. To
1001 try it out, install a Rust build environment, and configure Tor
1002 with "--enable-rust --enable-cargo-online-mode". This should not
1003 cause any user-visible changes, but should help us gain more
1004 experience with Rust, and plan future Rust integration work.
1005 Implementation by Chelsea Komlo. Closes ticket 22840.
1007 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
1008 - When directory authorities read a zero-byte bandwidth file, they
1009 would previously log a warning with the contents of an
1010 uninitialised buffer. They now log a warning about the empty file
1011 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
1013 o Major bugfixes (security, directory authority, denial-of-service):
1014 - Fix a bug that could have allowed an attacker to force a directory
1015 authority to use up all its RAM by passing it a maliciously
1016 crafted protocol versions string. Fixes bug 25517; bugfix on
1017 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
1019 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
1020 - Avoid a rare assertion failure in the circuit build timeout code
1021 if we fail to allow any circuits to actually complete. Fixes bug
1022 25733; bugfix on 0.2.2.2-alpha.
1024 o Major bugfixes (netflow padding):
1025 - Stop adding unneeded channel padding right after we finish
1026 flushing to a connection that has been trying to flush for many
1027 seconds. Instead, treat all partial or complete flushes as
1028 activity on the channel, which will defer the time until we need
1029 to add padding. This fix should resolve confusing and scary log
1030 messages like "Channel padding timeout scheduled 221453ms in the
1031 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
1033 o Major bugfixes (networking):
1034 - Tor will no longer reject IPv6 address strings from Tor Browser
1035 when they are passed as hostnames in SOCKS5 requests. Fixes bug
1036 25036, bugfix on Tor 0.3.1.2.
1038 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
1039 - Correctly detect when onion services get disabled after HUP. Fixes
1040 bug 25761; bugfix on 0.3.2.1.
1042 o Major bugfixes (performance, load balancing):
1043 - Directory authorities no longer vote in favor of the Guard flag
1044 for relays without directory support. Starting in Tor
1045 0.3.0.1-alpha, clients have been avoiding using such relays in the
1046 Guard position, leading to increasingly broken load balancing for
1047 the 5%-or-so of Guards that don't advertise directory support.
1048 Fixes bug 22310; bugfix on 0.3.0.6.
1050 o Major bugfixes (relay):
1051 - If we have failed to connect to a relay and received a connection
1052 refused, timeout, or similar error (at the TCP level), do not try
1053 that same address/port again for 60 seconds after the failure has
1054 occurred. Fixes bug 24767; bugfix on 0.0.6.
1056 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
1057 - Impose a limit on circuit cell queue size. The limit can be
1058 controlled by a consensus parameter. Fixes bug 25226; bugfix
1061 o Minor features (cleanup):
1062 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
1063 when it stops. Closes ticket 23271.
1065 o Minor features (compatibility, backport from 0.3.4.1-alpha):
1066 - Avoid some compilation warnings with recent versions of LibreSSL.
1067 Closes ticket 26006.
1069 o Minor features (config options):
1070 - Change the way the default value for MaxMemInQueues is calculated.
1071 We now use 40% of the hardware RAM if the system has 8 GB RAM or
1072 more. Otherwise we use the former value of 75%. Closes
1075 o Minor features (continuous integration):
1076 - Update the Travis CI configuration to use the stable Rust channel,
1077 now that we have decided to require that. Closes ticket 25714.
1079 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
1080 - Our .travis.yml configuration now includes support for testing the
1081 results of "make distcheck". (It's not uncommon for "make check"
1082 to pass but "make distcheck" to fail.) Closes ticket 25814.
1083 - Our Travis CI configuration now integrates with the Coveralls
1084 coverage analysis tool. Closes ticket 25818.
1086 o Minor features (defensive programming):
1087 - Most of the functions in Tor that free objects have been replaced
1088 with macros that free the objects and set the corresponding
1089 pointers to NULL. This change should help prevent a large class of
1090 dangling pointer bugs. Closes ticket 24337.
1091 - Where possible, the tor_free() macro now only evaluates its input
1092 once. Part of ticket 24337.
1093 - Check that microdesc ed25519 ids are non-zero in
1094 node_get_ed25519_id() before returning them. Implements ticket
1095 24001, patch by "aruna1234".
1097 o Minor features (directory authority):
1098 - When directory authorities are unable to add signatures to a
1099 pending consensus, log the reason why. Closes ticket 24849.
1101 o Minor features (embedding):
1102 - Tor can now start with a preauthenticated control connection
1103 created by the process that launched it. This feature is meant for
1104 use by programs that want to launch and manage a Tor process
1105 without allowing other programs to manage it as well. For more
1106 information, see the __OwningControllerFD option documented in
1107 control-spec.txt. Closes ticket 23900.
1108 - On most errors that would cause Tor to exit, it now tries to
1109 return from the tor_main() function, rather than calling the
1110 system exit() function. Most users won't notice a difference here,
1111 but it should be significant for programs that run Tor inside a
1112 separate thread: they should now be able to survive Tor's exit
1113 conditions rather than having Tor shut down the entire process.
1114 Closes ticket 23848.
1115 - Applications that want to embed Tor can now tell Tor not to
1116 register any of its own POSIX signal handlers, using the
1117 __DisableSignalHandlers option. Closes ticket 24588.
1119 o Minor features (fallback directory list):
1120 - Avoid selecting fallbacks that change their IP addresses too
1121 often. Select more fallbacks by ignoring the Guard flag, and
1122 allowing lower cutoffs for the Running and V2Dir flags. Also allow
1123 a lower bandwidth, and a higher number of fallbacks per operator
1124 (5% of the list). Implements ticket 24785.
1125 - Update the fallback whitelist and blacklist based on opt-ins and
1126 relay changes. Closes tickets 22321, 24678, 22527, 24135,
1129 o Minor features (fallback directory mirror configuration):
1130 - Add a nickname to each fallback in a C comment. This makes it
1131 easier for operators to find their relays, and allows stem to use
1132 nicknames to identify fallbacks. Implements ticket 24600.
1133 - Add a type and version header to the fallback directory mirror
1134 file. Also add a delimiter to the end of each fallback entry. This
1135 helps external parsers like stem and Relay Search. Implements
1137 - Add an extrainfo cache flag for each fallback in a C comment. This
1138 allows stem to use fallbacks to fetch extra-info documents, rather
1139 than using authorities. Implements ticket 22759.
1140 - Add the generateFallbackDirLine.py script for automatically
1141 generating fallback directory mirror lines from relay fingerprints.
1142 No more typos! Add the lookupFallbackDirContact.py script for
1143 automatically looking up operator contact info from relay
1144 fingerprints. Implements ticket 24706, patch by teor and atagar.
1145 - Reject any fallback directory mirror that serves an expired
1146 consensus. Implements ticket 20942, patch by "minik".
1147 - Remove commas and equals signs from external string inputs to the
1148 fallback list. This avoids format confusion attacks. Implements
1150 - Remove the "weight=10" line from fallback directory mirror
1151 entries. Ticket 24681 will maintain the current fallback weights
1152 by changing Tor's default fallback weight to 10. Implements
1154 - Stop logging excessive information about fallback netblocks.
1155 Implements ticket 24791.
1157 o Minor features (forward-compatibility):
1158 - If a relay supports some link authentication protocol that we do
1159 not recognize, then include that relay's ed25519 key when telling
1160 other relays to extend to it. Previously, we treated future
1161 versions as if they were too old to support ed25519 link
1162 authentication. Closes ticket 20895.
1164 o Minor features (geoip):
1165 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
1166 database. Closes ticket 26104.
1168 o Minor features (heartbeat):
1169 - Add onion service information to our heartbeat logs, displaying
1170 stats about the activity of configured onion services. Closes
1173 o Minor features (instrumentation, development):
1174 - Add the MainloopStats option to allow developers to get
1175 instrumentation information from the main event loop via the
1176 heartbeat messages. We hope to use this to improve Tor's behavior
1177 when it's trying to sleep. Closes ticket 24605.
1179 o Minor features (IPv6):
1180 - Make IPv6-only clients wait for microdescs for relays, even if we
1181 were previously using descriptors (or were using them as a bridge)
1182 and have a cached descriptor for them. Implements ticket 23827.
1183 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
1184 them, rather than waiting to download microdescriptors. Implements
1187 o Minor features (log messages):
1188 - Improve log message in the out-of-memory handler to include
1189 information about memory usage from the different compression
1190 backends. Closes ticket 25372.
1191 - Improve a warning message that happens when we fail to re-parse an
1192 old router because of an expired certificate. Closes ticket 20020.
1193 - Make the log more quantitative when we hit MaxMemInQueues
1194 threshold exposing some values. Closes ticket 24501.
1196 o Minor features (logging):
1197 - Clarify the log messages produced when getrandom() or a related
1198 entropy-generation mechanism gives an error. Closes ticket 25120.
1199 - Added support for the Android logging subsystem. Closes
1202 o Minor features (performance):
1203 - Support predictive circuit building for onion service circuits
1204 with multiple layers of guards. Closes ticket 23101.
1205 - Use stdatomic.h where available, rather than mutexes, to implement
1206 atomic_counter_t. Closes ticket 23953.
1208 o Minor features (performance, 32-bit):
1209 - Improve performance on 32-bit systems by avoiding 64-bit division
1210 when calculating the timestamp in milliseconds for channel padding
1211 computations. Implements ticket 24613.
1212 - Improve performance on 32-bit systems by avoiding 64-bit division
1213 when timestamping cells and buffer chunks for OOM calculations.
1214 Implements ticket 24374.
1216 o Minor features (performance, OSX, iOS):
1217 - Use the mach_approximate_time() function (when available) to
1218 implement coarse monotonic time. Having a coarse time function
1219 should avoid a large number of system calls, and improve
1220 performance slightly, especially under load. Closes ticket 24427.
1222 o Minor features (performance, windows):
1223 - Improve performance on Windows Vista and Windows 7 by adjusting
1224 TCP send window size according to the recommendation from
1225 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
1228 o Minor features (sandbox):
1229 - Explicitly permit the poll() system call when the Linux
1230 seccomp2-based sandbox is enabled: apparently, some versions of
1231 libc use poll() when calling getpwnam(). Closes ticket 25313.
1233 o Minor features (storage, configuration):
1234 - Users can store cached directory documents somewhere other than
1235 the DataDirectory by using the CacheDirectory option. Similarly,
1236 the storage location for relay's keys can be overridden with the
1237 KeyDirectory option. Closes ticket 22703.
1239 o Minor features (testing):
1240 - Add a "make test-rust" target to run the rust tests only. Closes
1243 o Minor features (testing, debugging, embedding):
1244 - For development purposes, Tor now has a mode in which it runs for
1245 a few seconds, then stops, and starts again without exiting the
1246 process. This mode is meant to help us debug various issues with
1247 ticket 23847. To use this feature, compile with
1248 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
1249 environment variable. This is expected to crash a lot, and is
1250 really meant for developers only. It will likely be removed in a
1251 future release. Implements ticket 24583.
1253 o Minor bugfixes (build, rust):
1254 - Fix output of autoconf checks to display success messages for Rust
1255 dependencies and a suitable rustc compiler version. Fixes bug
1256 24612; bugfix on 0.3.1.3-alpha.
1257 - Don't pass the --quiet option to cargo: it seems to suppress some
1258 errors, which is not what we want to do when building. Fixes bug
1259 24518; bugfix on 0.3.1.7.
1260 - Build correctly when building from outside Tor's source tree with
1261 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
1264 o Minor bugfixes (C correctness):
1265 - Fix a very unlikely (impossible, we believe) null pointer
1266 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
1267 Coverity; this is CID 1430932.
1269 o Minor bugfixes (channel, client):
1270 - Better identify client connection when reporting to the geoip
1271 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
1273 o Minor bugfixes (circuit, cannibalization):
1274 - Don't cannibalize preemptively-built circuits if we no longer
1275 recognize their first hop. This situation can happen if our Guard
1276 relay went off the consensus after the circuit was created. Fixes
1277 bug 24469; bugfix on 0.0.6.
1279 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
1280 - Don't consider Tor running as a client if the ControlPort is open,
1281 but no actual client ports are open. Fixes bug 26062; bugfix
1284 o Minor bugfixes (compilation):
1285 - Fix a C99 compliance issue in our configuration script that caused
1286 compilation issues when compiling Tor with certain versions of
1287 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
1289 o Minor bugfixes (controller):
1290 - Restore the correct operation of the RESOLVE command, which had
1291 been broken since we added the ability to enable/disable DNS on
1292 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
1293 - Avoid a (nonfatal) assertion failure when extending a one-hop
1294 circuit from the controller to become a multihop circuit. Fixes
1295 bug 24903; bugfix on 0.2.5.2-alpha.
1297 o Minor bugfixes (correctness):
1298 - Remove a nonworking, unnecessary check to see whether a circuit
1299 hop's identity digest was set when the circuit failed. Fixes bug
1300 24927; bugfix on 0.2.4.4-alpha.
1302 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
1303 - Upon receiving a malformed connected cell, stop processing the
1304 cell immediately. Previously we would mark the connection for
1305 close, but continue processing the cell as if the connection were
1306 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
1308 o Minor bugfixes (directory authorities, IPv6):
1309 - When creating a routerstatus (vote) from a routerinfo (descriptor),
1310 set the IPv6 address to the unspecified IPv6 address, and
1311 explicitly initialize the port to zero. Fixes bug 24488; bugfix
1314 o Minor bugfixes (documentation):
1315 - Document that the PerConnBW{Rate,Burst} options will fall back to
1316 their corresponding consensus parameters only if those parameters
1317 are set. Previously we had claimed that these values would always
1318 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
1320 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
1321 - Stop saying in the manual that clients cache ipv4 dns answers from
1322 exit relays. We haven't used them since 0.2.6.3-alpha, and in
1323 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
1324 we forgot to say so in the man page. Fixes bug 26052; bugfix
1327 o Minor bugfixes (exit relay DNS retries):
1328 - Re-attempt timed-out DNS queries 3 times before failure, since our
1329 timeout is 5 seconds for them, but clients wait 10-15. Also allow
1330 slightly more timeouts per resolver when an exit has multiple
1331 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
1333 o Minor bugfixes (fallback directory mirrors):
1334 - Make updateFallbackDirs.py search harder for python. (Some OSs
1335 don't put it in /usr/bin.) Fixes bug 24708; bugfix
1338 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
1339 - When hibernating, close connections normally and allow them to
1340 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
1342 - Do not attempt to launch self-reachability tests when entering
1343 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
1344 - Resolve several bugs related to descriptor fetching on bridge
1345 clients with bandwidth accounting enabled. (This combination is
1346 not recommended!) Fixes a case of bug 12062; bugfix
1348 - When hibernating, do not attempt to launch DNS checks. Fixes a
1349 case of bug 12062; bugfix on 0.1.2.2-alpha.
1350 - When hibernating, do not try to upload or download descriptors.
1351 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
1353 o Minor bugfixes (IPv6, bridges):
1354 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
1355 bugfix on 0.2.8.2-alpha.
1356 - Tor now sets IPv6 address in the routerstatus as well as in the
1357 router descriptors when updating addresses for a bridge. Closes
1358 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
1360 o Minor bugfixes (Linux seccomp2 sandbox):
1361 - When running with the sandbox enabled, reload configuration files
1362 correctly even when %include was used. Previously we would crash.
1363 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
1365 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
1366 - Allow the nanosleep() system call, which glibc uses to implement
1367 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
1369 o Minor bugfixes (logging):
1370 - Fix a (mostly harmless) race condition when invoking
1371 LOG_PROTOCOL_WARN message from a subthread while the torrc options
1372 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
1374 o Minor bugfixes (man page, SocksPort):
1375 - Remove dead code from the old "SocksSocket" option, and rename
1376 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old
1377 option still works, but is deprecated. Fixes bug 24343; bugfix
1380 o Minor bugfixes (memory leaks):
1381 - Avoid possible at-exit memory leaks related to use of Libevent's
1382 event_base_once() function. (This function tends to leak memory if
1383 the event_base is closed before the event fires.) Fixes bug 24584;
1384 bugfix on 0.2.8.1-alpha.
1385 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
1388 o Minor bugfixes (network IPv6 test):
1389 - Tor's test scripts now check if "ping -6 ::1" works when the user
1390 runs "make test-network-all". Fixes bug 24677; bugfix on
1391 0.2.9.3-alpha. Patch by "ffmancera".
1393 o Minor bugfixes (networking):
1394 - string_is_valid_hostname() will not consider IP strings to be
1395 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
1397 o Minor bugfixes (onion service v3):
1398 - Avoid an assertion failure when the next onion service descriptor
1399 rotation type is out of sync with the consensus's valid-after
1400 time. Instead, log a warning message with extra information, so we
1401 can better hunt down the cause of this assertion. Fixes bug 25306;
1402 bugfix on 0.3.2.1-alpha.
1404 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
1405 - Fix a memory leak when a v3 onion service is configured and gets a
1406 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
1407 - When parsing the descriptor signature, look for the token plus an
1408 extra white-space at the end. This is more correct but also will
1409 allow us to support new fields that might start with "signature".
1410 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
1412 o Minor bugfixes (onion services):
1413 - If we are configured to offer a single onion service, don't log
1414 long-term established one hop rendezvous points in the heartbeat.
1415 Fixes bug 25116; bugfix on 0.2.9.6-rc.
1417 o Minor bugfixes (performance):
1418 - Reduce the number of circuits that will be opened at once during
1419 the circuit build timeout phase. This is done by increasing the
1420 idle timeout to 3 minutes, and lowering the maximum number of
1421 concurrent learning circuits to 10. Fixes bug 24769; bugfix
1423 - Avoid calling protocol_list_supports_protocol() from inside tight
1424 loops when running with cached routerinfo_t objects. Instead,
1425 summarize the relevant protocols as flags in the routerinfo_t, as
1426 we do for routerstatus_t objects. This change simplifies our code
1427 a little, and saves a large amount of short-term memory allocation
1428 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
1430 o Minor bugfixes (performance, timeouts):
1431 - Consider circuits for timeout as soon as they complete a hop. This
1432 is more accurate than applying the timeout in
1433 circuit_expire_building() because that function is only called
1434 once per second, which is now too slow for typical timeouts on the
1435 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
1436 - Use onion service circuits (and other circuits longer than 3 hops)
1437 to calculate a circuit build timeout. Previously, Tor only
1438 calculated its build timeout based on circuits that planned to be
1439 exactly 3 hops long. With this change, we include measurements
1440 from all circuits at the point where they complete their third
1441 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
1443 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
1444 - Avoid a crash when running with DirPort set but ORPort turned off.
1445 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
1447 o Minor bugfixes (Rust FFI):
1448 - Fix a minor memory leak which would happen whenever the C code
1449 would call the Rust implementation of
1450 protover_get_supported_protocols(). This was due to the C version
1451 returning a static string, whereas the Rust version newly allocated
1452 a CString to pass across the FFI boundary. Consequently, the C
1453 code was not expecting to need to free() what it was given. Fixes
1454 bug 25127; bugfix on 0.3.2.1-alpha.
1456 o Minor bugfixes (spelling):
1457 - Use the "misspell" tool to detect and fix typos throughout the
1458 source code. Fixes bug 23650; bugfix on various versions of Tor.
1459 Patch from Deepesh Pathak.
1461 o Minor bugfixes (testing):
1462 - Avoid intermittent test failures due to a test that had relied on
1463 onion service introduction point creation finishing within 5
1464 seconds of real clock time. Fixes bug 25450; bugfix
1466 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
1467 bugfix on 0.2.3.1-alpha.
1469 o Minor bugfixes (unit test, monotonic time):
1470 - Increase a constant (1msec to 10msec) in the monotonic time test
1471 that makes sure the nsec/usec/msec times read are synchronized.
1472 This change was needed to accommodate slow systems like armel or
1473 when the clock_gettime() is not a VDSO on the running kernel.
1474 Fixes bug 25113; bugfix on 0.2.9.1.
1476 o Code simplification and refactoring:
1477 - Move the list of default directory authorities to its own file.
1478 Closes ticket 24854. Patch by "beastr0".
1479 - Remove the old (deterministic) directory retry logic entirely:
1480 We've used exponential backoff exclusively for some time. Closes
1482 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
1484 - Remove a series of counters used to track circuit extend attempts
1485 and connection status but that in reality we aren't using for
1486 anything other than stats logged by a SIGUSR1 signal. Closes
1488 - Remove /usr/athena from search path in configure.ac. Closes
1490 - Remove duplicate code in node_has_curve25519_onion_key() and
1491 node_get_curve25519_onion_key(), and add a check for a zero
1492 microdesc curve25519 onion key. Closes ticket 23966, patch by
1493 "aruna1234" and teor.
1494 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
1495 memory allocations with large numbers of OR connections (e.g.
1496 relays). Closes ticket 24119.
1497 - Separate the function that deletes ephemeral files when Tor
1499 - Small changes to Tor's buf_t API to make it suitable for use as a
1500 general-purpose safe string constructor. Closes ticket 22342.
1501 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
1502 avoid source code identifier confusion. Closes ticket 24467.
1503 - The tor_git_revision[] constant no longer needs to be redeclared
1504 by everything that links against the rest of Tor. Done as part of
1505 ticket 23845, to simplify our external API.
1506 - We make extend_info_from_node() use node_get_curve25519_onion_key()
1507 introduced in ticket 23577 to access the curve25519 public keys
1508 rather than accessing it directly. Closes ticket 23760. Patch by
1510 - Add a function to log channels' scheduler state changes to aid
1511 debugging efforts. Closes ticket 24531.
1514 - Improved the documentation of AccountingStart parameter. Closes
1516 - Update the documentation for "Log" to include the current list of
1517 logging domains. Closes ticket 25378.
1518 - Add documentation on how to build tor with Rust dependencies
1519 without having to be online. Closes ticket 22907; bugfix
1521 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
1522 traffic. Closes ticket 24318.
1523 - Document that OutboundBindAddress doesn't apply to DNS requests.
1524 Closes ticket 22145. Patch from Aruna Maurya.
1526 o Code simplification and refactoring (channels):
1527 - Remove the incoming and outgoing channel queues. These were never
1528 used, but still took up a step in our fast path.
1529 - The majority of the channel unit tests have been rewritten and the
1530 code coverage has now been raised to 83.6% for channel.c. Closes
1532 - Remove other dead code from the channel subsystem: All together,
1533 this cleanup has removed more than 1500 lines of code overall and
1534 adding very little except for unit test.
1536 o Code simplification and refactoring (circuit rendezvous):
1537 - Split the client-side rendezvous circuit lookup into two
1538 functions: one that returns only established circuits and another
1539 that returns all kinds of circuits. Closes ticket 23459.
1541 o Code simplification and refactoring (controller):
1542 - Make most of the variables in networkstatus_getinfo_by_purpose()
1543 const. Implements ticket 24489.
1545 o Documentation (backport from 0.3.4.1-alpha):
1546 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
1547 ticket 25857. Patch from "CTassisF".
1549 o Documentation (man page):
1550 - The HiddenServiceVersion torrc option accepts only one number:
1551 either version 2 or 3. Closes ticket 25026; bugfix
1554 o Documentation (manpage, denial of service):
1555 - Provide more detail about the denial-of-service options, by
1556 listing each mitigation and explaining how they relate. Closes
1560 Changes in version 0.3.1.10 - 2018-03-03
1561 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
1564 It includes an important security fix for a remote crash attack
1565 against directory authorities, tracked as TROVE-2018-001.
1567 This release also backports our new system for improved resistance to
1568 denial-of-service attacks against relays.
1570 This release also fixes several minor bugs and annoyances from
1573 All directory authorities should upgrade to one of the versions
1574 released today. Relays running 0.3.1.x may wish to update to one of
1575 the versions released today, for the DoS mitigations.
1577 Please note: according to our release calendar, Tor 0.3.1 will no
1578 longer be supported after 1 July 2018. If you will be running Tor
1579 after that date, you should make sure to plan to upgrade to the latest
1580 stable version, or downgrade to 0.2.9 (which will receive long-term
1583 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1584 - Fix a protocol-list handling bug that could be used to remotely crash
1585 directory authorities with a null-pointer exception. Fixes bug 25074;
1586 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1589 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
1590 - Give relays some defenses against the recent network overload. We
1591 start with three defenses (default parameters in parentheses).
1592 First: if a single client address makes too many concurrent
1593 connections (>100), hang up on further connections. Second: if a
1594 single client address makes circuits too quickly (more than 3 per
1595 second, with an allowed burst of 90) while also having too many
1596 connections open (3), refuse new create cells for the next while
1597 (1-2 hours). Third: if a client asks to establish a rendezvous
1598 point to you directly, ignore the request. These defenses can be
1599 manually controlled by new torrc options, but relays will also
1600 take guidance from consensus parameters, so there's no need to
1601 configure anything manually. Implements ticket 24902.
1603 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
1604 - Update the sandbox rules so that they should now work correctly
1605 with Glibc 2.26. Closes ticket 24315.
1607 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
1608 - Fix an "off by 2" error in counting rendezvous failures on the
1609 onion service side. While we thought we would stop the rendezvous
1610 attempt after one failed circuit, we were actually making three
1611 circuit attempts before giving up. Now switch to a default of 2,
1612 and allow the consensus parameter "hs_service_max_rdv_failures" to
1613 override. Fixes bug 24895; bugfix on 0.0.6.
1615 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
1616 - Add Link protocol version 5 to the supported protocols list. Fixes
1617 bug 25070; bugfix on 0.3.1.1-alpha.
1619 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
1620 - Fix a set of false positives where relays would consider
1621 connections to other relays as being client-only connections (and
1622 thus e.g. deserving different link padding schemes) if those
1623 relays fell out of the consensus briefly. Now we look only at the
1624 initial handshake and whether the connection authenticated as a
1625 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1627 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
1628 - Make our OOM handler aware of the geoip client history cache so it
1629 doesn't fill up the memory. This check is important for IPv6 and
1630 our DoS mitigation subsystem. Closes ticket 25122.
1632 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
1633 - Change relay bandwidth reporting stats interval from 4 hours to 24
1634 hours in order to reduce the efficiency of guard discovery
1635 attacks. Fixes ticket 23856.
1637 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
1638 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1639 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1640 since they neither disabled TLS 1.3 nor enabled any of the
1641 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1642 Closes ticket 24978.
1644 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
1645 - The fallback directory list has been re-generated based on the
1646 current status of the network. Tor uses fallback directories to
1647 bootstrap when it doesn't yet have up-to-date directory
1648 information. Closes ticket 24801.
1649 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1650 prefer to bootstrap from fallback directory mirrors. This is a
1651 follow-up to 24679, which removed weights from the default
1652 fallbacks. Implements ticket 24681.
1654 o Minor features (geoip):
1655 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1658 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
1659 - Use the actual observed address of an incoming relay connection,
1660 not the canonical address of the relay from its descriptor, when
1661 making decisions about how to handle the incoming connection.
1662 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1664 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
1665 - Directory authorities, when refusing a descriptor from a rejected
1666 relay, now explicitly tell the relay (in its logs) to set a valid
1667 ContactInfo address and contact the bad-relays@ mailing list.
1668 Fixes bug 25170; bugfix on 0.2.9.1.
1670 o Minor bugfixes (address selection, backport from 0.3.2.9):
1671 - When the fascist_firewall_choose_address_ functions don't find a
1672 reachable address, set the returned address to the null address
1673 and port. This is a precautionary measure, because some callers do
1674 not check the return value. Fixes bug 24736; bugfix
1677 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
1678 - Fetch descriptors aggressively whenever we lack enough to build
1679 circuits, regardless of how many descriptors we are missing.
1680 Previously, we would delay launching the fetch when we had fewer
1681 than 15 missing descriptors, even if some of those descriptors
1682 were blocking circuits from building. Fixes bug 23985; bugfix on
1683 0.1.1.11-alpha. The effects of this bug became worse in
1684 0.3.0.3-alpha, when we began treating missing descriptors from our
1685 primary guards as a reason to delay circuits.
1686 - Don't try fetching microdescriptors from relays that have failed
1687 to deliver them in the past. Fixes bug 23817; bugfix
1690 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
1691 - Fix a signed/unsigned comparison warning introduced by our fix to
1692 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1694 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
1695 - Avoid a crash when attempting to use the seccomp2 sandbox together
1696 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1699 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1700 - Fix a possible crash on malformed consensus. If a consensus had
1701 contained an unparseable protocol line, it could have made clients
1702 and relays crash with a null-pointer exception. To exploit this
1703 issue, however, an attacker would need to be able to subvert the
1704 directory authority system. Fixes bug 25251; bugfix on
1705 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1707 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
1708 - Recover better from empty or corrupt files in the consensus cache
1709 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
1710 - When a consensus diff calculation is only partially successful,
1711 only record the successful parts as having succeeded. Partial
1712 success can happen if (for example) one compression method fails
1713 but the others succeed. Previously we misrecorded all the
1714 calculations as having succeeded, which would later cause a
1715 nonfatal assertion failure. Fixes bug 24086; bugfix
1718 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
1719 - Tor now updates its guard state when it reads a consensus
1720 regardless of whether it's missing descriptors. That makes tor use
1721 its primary guards to fetch descriptors in some edge cases where
1722 it would previously have used fallback directories. Fixes bug
1723 23862; bugfix on 0.3.0.1-alpha.
1725 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
1726 - Don't treat inability to store a cached consensus object as a bug:
1727 it can happen normally when we are out of disk space. Fixes bug
1728 24859; bugfix on 0.3.1.1-alpha.
1730 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
1731 - When queuing DESTROY cells on a channel, only queue the circuit-id
1732 and reason fields: not the entire 514-byte cell. This fix should
1733 help mitigate any bugs or attacks that fill up these queues, and
1734 free more RAM for other uses. Fixes bug 24666; bugfix
1737 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
1738 - When closing a connection via close_connection_immediately(), we
1739 mark it as "not blocked on bandwidth", to prevent later calls from
1740 trying to unblock it, and give it permission to read. This fixes a
1741 backtrace warning that can happen on relays under various
1742 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1744 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
1745 - When selecting relays by bandwidth, avoid a rounding error that
1746 could sometimes cause load to be imbalanced incorrectly.
1747 Previously, we would always round upwards; now, we round towards
1748 the nearest integer. This had the biggest effect when a relay's
1749 weight adjustments should have given it weight 0, but it got
1750 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1751 - When calculating the fraction of nodes that have descriptors, and
1752 all nodes in the network have zero bandwidths, count the number of
1753 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1754 - Actually log the total bandwidth in compute_weighted_bandwidths().
1755 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1757 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
1758 - Improve the performance of our consensus-diff application code
1759 when Tor is built with the --enable-fragile-hardening option set.
1760 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1762 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
1763 - Don't exit the Tor process if setrlimit() fails to change the file
1764 limit (which can happen sometimes on some versions of OSX). Fixes
1765 bug 21074; bugfix on 0.0.9pre5.
1767 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
1768 - Fix a bug in the bit-counting parts of our timing-wheel code on
1769 MSVC. (Note that MSVC is still not a supported build platform, due
1770 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
1773 o Minor bugfixes (relay, partial backport):
1774 - Make the internal channel_is_client() function look at what sort
1775 of connection handshake the other side used, rather than whether
1776 the other side ever sent a create_fast cell to us. Backports part
1777 of the fixes from bugs 22805 and 24898.
1779 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1780 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1782 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1783 bugfix on 0.2.9.4-alpha.
1785 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
1786 - Update the "rust dependencies" submodule to be a project-level
1787 repository, rather than a user repository. Closes ticket 25323.
1790 Changes in version 0.2.9.15 - 2018-03-03
1791 Tor 0.2.9.15 backports important security and stability bugfixes from
1794 It includes an important security fix for a remote crash attack
1795 against directory authorities, tracked as TROVE-2018-001.
1797 This release also backports our new system for improved resistance to
1798 denial-of-service attacks against relays.
1800 This release also fixes several minor bugs and annoyances from
1803 All directory authorities should upgrade to one of the versions
1804 released today. Relays running 0.2.9.x may wish to update to one of
1805 the versions released today, for the DoS mitigations.
1807 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1808 - Fix a protocol-list handling bug that could be used to remotely crash
1809 directory authorities with a null-pointer exception. Fixes bug 25074;
1810 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1813 o Major features (denial-of-service mitigation):
1814 - Give relays some defenses against the recent network overload. We
1815 start with three defenses (default parameters in parentheses).
1816 First: if a single client address makes too many concurrent
1817 connections (>100), hang up on further connections. Second: if a
1818 single client address makes circuits too quickly (more than 3 per
1819 second, with an allowed burst of 90) while also having too many
1820 connections open (3), refuse new create cells for the next while
1821 (1-2 hours). Third: if a client asks to establish a rendezvous
1822 point to you directly, ignore the request. These defenses can be
1823 manually controlled by new torrc options, but relays will also
1824 take guidance from consensus parameters, so there's no need to
1825 configure anything manually. Implements ticket 24902.
1827 o Major bugfixes (bootstrapping):
1828 - Fetch descriptors aggressively whenever we lack enough to build
1829 circuits, regardless of how many descriptors we are missing.
1830 Previously, we would delay launching the fetch when we had fewer
1831 than 15 missing descriptors, even if some of those descriptors
1832 were blocking circuits from building. Fixes bug 23985; bugfix on
1833 0.1.1.11-alpha. The effects of this bug became worse in
1834 0.3.0.3-alpha, when we began treating missing descriptors from our
1835 primary guards as a reason to delay circuits.
1837 o Major bugfixes (onion services, retry behavior):
1838 - Fix an "off by 2" error in counting rendezvous failures on the
1839 onion service side. While we thought we would stop the rendezvous
1840 attempt after one failed circuit, we were actually making three
1841 circuit attempts before giving up. Now switch to a default of 2,
1842 and allow the consensus parameter "hs_service_max_rdv_failures" to
1843 override. Fixes bug 24895; bugfix on 0.0.6.
1845 o Minor feature (relay statistics):
1846 - Change relay bandwidth reporting stats interval from 4 hours to 24
1847 hours in order to reduce the efficiency of guard discovery
1848 attacks. Fixes ticket 23856.
1850 o Minor features (compatibility, OpenSSL):
1851 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1852 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1853 since they neither disabled TLS 1.3 nor enabled any of the
1854 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1855 Closes ticket 24978.
1857 o Minor features (denial-of-service avoidance):
1858 - Make our OOM handler aware of the geoip client history cache so it
1859 doesn't fill up the memory. This check is important for IPv6 and
1860 our DoS mitigation subsystem. Closes ticket 25122.
1862 o Minor features (fallback directory mirrors):
1863 - The fallback directory list has been re-generated based on the
1864 current status of the network. Tor uses fallback directories to
1865 bootstrap when it doesn't yet have up-to-date directory
1866 information. Closes ticket 24801.
1867 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1868 prefer to bootstrap from fallback directory mirrors. This is a
1869 follow-up to 24679, which removed weights from the default
1870 fallbacks. Implements ticket 24681.
1872 o Minor features (geoip):
1873 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1876 o Minor features (linux seccomp2 sandbox):
1877 - Update the sandbox rules so that they should now work correctly
1878 with Glibc 2.26. Closes ticket 24315.
1880 o Minor bugfix (channel connection):
1881 - Use the actual observed address of an incoming relay connection,
1882 not the canonical address of the relay from its descriptor, when
1883 making decisions about how to handle the incoming connection.
1884 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1886 o Minor bugfix (directory authority):
1887 - Directory authorities, when refusing a descriptor from a rejected
1888 relay, now explicitly tell the relay (in its logs) to set a valid
1889 ContactInfo address and contact the bad-relays@ mailing list.
1890 Fixes bug 25170; bugfix on 0.2.9.1.
1892 o Minor bugfixes (address selection):
1893 - When the fascist_firewall_choose_address_ functions don't find a
1894 reachable address, set the returned address to the null address
1895 and port. This is a precautionary measure, because some callers do
1896 not check the return value. Fixes bug 24736; bugfix
1899 o Minor bugfixes (compilation):
1900 - Fix a signed/unsigned comparison warning introduced by our fix to
1901 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1903 o Minor bugfixes (control port, linux seccomp2 sandbox):
1904 - Avoid a crash when attempting to use the seccomp2 sandbox together
1905 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1908 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1909 - Fix a possible crash on malformed consensus. If a consensus had
1910 contained an unparseable protocol line, it could have made clients
1911 and relays crash with a null-pointer exception. To exploit this
1912 issue, however, an attacker would need to be able to subvert the
1913 directory authority system. Fixes bug 25251; bugfix on
1914 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1916 o Minor bugfixes (memory usage):
1917 - When queuing DESTROY cells on a channel, only queue the circuit-id
1918 and reason fields: not the entire 514-byte cell. This fix should
1919 help mitigate any bugs or attacks that fill up these queues, and
1920 free more RAM for other uses. Fixes bug 24666; bugfix
1923 o Minor bugfixes (network layer):
1924 - When closing a connection via close_connection_immediately(), we
1925 mark it as "not blocked on bandwidth", to prevent later calls from
1926 trying to unblock it, and give it permission to read. This fixes a
1927 backtrace warning that can happen on relays under various
1928 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1930 o Minor bugfixes (OSX):
1931 - Don't exit the Tor process if setrlimit() fails to change the file
1932 limit (which can happen sometimes on some versions of OSX). Fixes
1933 bug 21074; bugfix on 0.0.9pre5.
1935 o Minor bugfixes (path selection):
1936 - When selecting relays by bandwidth, avoid a rounding error that
1937 could sometimes cause load to be imbalanced incorrectly.
1938 Previously, we would always round upwards; now, we round towards
1939 the nearest integer. This had the biggest effect when a relay's
1940 weight adjustments should have given it weight 0, but it got
1941 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1942 - When calculating the fraction of nodes that have descriptors, and
1943 all nodes in the network have zero bandwidths, count the number of
1944 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1945 - Actually log the total bandwidth in compute_weighted_bandwidths().
1946 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1948 o Minor bugfixes (portability, msvc):
1949 - Fix a bug in the bit-counting parts of our timing-wheel code on
1950 MSVC. (Note that MSVC is still not a supported build platform, due
1951 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
1954 o Minor bugfixes (relay):
1955 - Make the internal channel_is_client() function look at what sort
1956 of connection handshake the other side used, rather than whether
1957 the other side ever sent a create_fast cell to us. Backports part
1958 of the fixes from bugs 22805 and 24898.
1960 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1961 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1963 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1964 bugfix on 0.2.9.4-alpha.
1967 Changes in version 0.3.2.10 - 2018-03-03
1968 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
1969 backports a number of bugfixes, including important fixes for security
1972 It includes an important security fix for a remote crash attack
1973 against directory authorities, tracked as TROVE-2018-001.
1975 Additionally, it backports a fix for a bug whose severity we have
1976 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
1977 triggered in order to crash relays with a use-after-free pattern. As
1978 such, we are now tracking that bug as TROVE-2018-002 and
1979 CVE-2018-0491, and backporting it to earlier releases. This bug
1980 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
1983 This release also backports our new system for improved resistance to
1984 denial-of-service attacks against relays.
1986 This release also fixes several minor bugs and annoyances from
1989 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
1990 today, for the fix to TROVE-2018-002. Directory authorities should
1991 also upgrade. (Relays on earlier versions might want to update too for
1992 the DoS mitigations.)
1994 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1995 - Fix a protocol-list handling bug that could be used to remotely crash
1996 directory authorities with a null-pointer exception. Fixes bug 25074;
1997 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
2000 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
2001 - Avoid adding the same channel twice in the KIST scheduler pending
2002 list, which could lead to remote denial-of-service use-after-free
2003 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
2005 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
2006 - Give relays some defenses against the recent network overload. We
2007 start with three defenses (default parameters in parentheses).
2008 First: if a single client address makes too many concurrent
2009 connections (>100), hang up on further connections. Second: if a
2010 single client address makes circuits too quickly (more than 3 per
2011 second, with an allowed burst of 90) while also having too many
2012 connections open (3), refuse new create cells for the next while
2013 (1-2 hours). Third: if a client asks to establish a rendezvous
2014 point to you directly, ignore the request. These defenses can be
2015 manually controlled by new torrc options, but relays will also
2016 take guidance from consensus parameters, so there's no need to
2017 configure anything manually. Implements ticket 24902.
2019 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
2020 - Fix an "off by 2" error in counting rendezvous failures on the
2021 onion service side. While we thought we would stop the rendezvous
2022 attempt after one failed circuit, we were actually making three
2023 circuit attempts before giving up. Now switch to a default of 2,
2024 and allow the consensus parameter "hs_service_max_rdv_failures" to
2025 override. Fixes bug 24895; bugfix on 0.0.6.
2026 - New-style (v3) onion services now obey the "max rendezvous circuit
2027 attempts" logic. Previously they would make as many rendezvous
2028 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
2029 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
2031 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
2032 - Add Link protocol version 5 to the supported protocols list. Fixes
2033 bug 25070; bugfix on 0.3.1.1-alpha.
2035 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
2036 - Fix a set of false positives where relays would consider
2037 connections to other relays as being client-only connections (and
2038 thus e.g. deserving different link padding schemes) if those
2039 relays fell out of the consensus briefly. Now we look only at the
2040 initial handshake and whether the connection authenticated as a
2041 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
2043 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
2044 - The scheduler subsystem was failing to promptly notice changes in
2045 consensus parameters, making it harder to switch schedulers
2046 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
2048 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
2049 - Make our OOM handler aware of the geoip client history cache so it
2050 doesn't fill up the memory. This check is important for IPv6 and
2051 our DoS mitigation subsystem. Closes ticket 25122.
2053 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
2054 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
2055 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
2056 since they neither disabled TLS 1.3 nor enabled any of the
2057 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
2058 Closes ticket 24978.
2060 o Minor features (geoip):
2061 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
2064 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
2065 - When logging a failure to create an onion service's descriptor,
2066 also log what the problem with the descriptor was. Diagnostic
2069 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
2070 - Use the actual observed address of an incoming relay connection,
2071 not the canonical address of the relay from its descriptor, when
2072 making decisions about how to handle the incoming connection.
2073 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
2075 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
2076 - Fix a possible crash on malformed consensus. If a consensus had
2077 contained an unparseable protocol line, it could have made clients
2078 and relays crash with a null-pointer exception. To exploit this
2079 issue, however, an attacker would need to be able to subvert the
2080 directory authority system. Fixes bug 25251; bugfix on
2081 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
2083 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
2084 - Directory authorities, when refusing a descriptor from a rejected
2085 relay, now explicitly tell the relay (in its logs) to set a valid
2086 ContactInfo address and contact the bad-relays@ mailing list.
2087 Fixes bug 25170; bugfix on 0.2.9.1.
2089 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
2090 - When building with Rust on OSX, link against libresolv, to work
2091 around the issue at https://github.com/rust-lang/rust/issues/46797.
2092 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
2094 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
2095 - Remove a BUG() statement when a client fetches an onion descriptor
2096 that has a lower revision counter than the one in its cache. This
2097 can happen in normal circumstances due to HSDir desync. Fixes bug
2098 24976; bugfix on 0.3.2.1-alpha.
2100 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
2101 - Don't treat inability to store a cached consensus object as a bug:
2102 it can happen normally when we are out of disk space. Fixes bug
2103 24859; bugfix on 0.3.1.1-alpha.
2105 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
2106 - Improve the performance of our consensus-diff application code
2107 when Tor is built with the --enable-fragile-hardening option set.
2108 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
2110 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
2111 - Don't exit the Tor process if setrlimit() fails to change the file
2112 limit (which can happen sometimes on some versions of OSX). Fixes
2113 bug 21074; bugfix on 0.0.9pre5.
2115 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
2116 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
2118 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
2119 bugfix on 0.2.9.4-alpha.
2121 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
2122 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
2123 25005; bugfix on 0.3.2.7-rc.
2125 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
2126 - Look at the "HSRend" protocol version, not the "HSDir" protocol
2127 version, when deciding whether a consensus entry can support the
2128 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
2129 bugfix on 0.3.2.1-alpha.
2131 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
2132 - Update the "rust dependencies" submodule to be a project-level
2133 repository, rather than a user repository. Closes ticket 25323.
2135 o Documentation (backport from 0.3.3.1-alpha)
2136 - Document that operators who run more than one relay or bridge are
2137 expected to set MyFamily and ContactInfo correctly. Closes
2141 Changes in version 0.3.2.9 - 2018-01-09
2142 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
2144 The 0.3.2 series includes our long-anticipated new onion service
2145 design, with numerous security features. (For more information, see
2146 our blog post at https://blog.torproject.org/fall-harvest.) We also
2147 have a new circuit scheduler algorithm for improved performance on
2148 relays everywhere (see https://blog.torproject.org/kist-and-tell),
2149 along with many smaller features and bugfixes.
2151 Per our stable release policy, we plan to support each stable release
2152 series for at least the next nine months, or for three months after
2153 the first stable release of the next series: whichever is longer. If
2154 you need a release with long-term support, we recommend that you stay
2155 with the 0.2.9 series.
2157 Below is a list of the changes since 0.3.1.7. For a list of all
2158 changes since 0.3.2.8-rc, see the ChangeLog file.
2160 o Directory authority changes:
2161 - Add "Bastet" as a ninth directory authority to the default list.
2162 Closes ticket 23910.
2163 - The directory authority "Longclaw" has changed its IP address.
2164 Closes ticket 23592.
2165 - Remove longclaw's IPv6 address, as it will soon change. Authority
2166 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2167 3/8 directory authorities with IPv6 addresses, but there are also
2168 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2169 - Add an IPv6 address for the "bastet" directory authority. Closes
2172 o Major features (next-generation onion services):
2173 - Tor now supports the next-generation onion services protocol for
2174 clients and services! As part of this release, the core of
2175 proposal 224 has been implemented and is available for
2176 experimentation and testing by our users. This newer version of
2177 onion services ("v3") features many improvements over the legacy
2180 a) Better crypto (replaced SHA1/DH/RSA1024
2181 with SHA3/ed25519/curve25519)
2183 b) Improved directory protocol, leaking much less information to
2186 c) Improved directory protocol, with smaller surface for
2189 d) Better onion address security against impersonation.
2191 e) More extensible introduction/rendezvous protocol.
2193 f) A cleaner and more modular codebase.
2195 You can identify a next-generation onion address by its length:
2196 they are 56 characters long, as in
2197 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
2199 In the future, we will release more options and features for v3
2200 onion services, but we first need a testing period, so that the
2201 current codebase matures and becomes more robust. Planned features
2202 include: offline keys, advanced client authorization, improved
2203 guard algorithms, and statistics. For full details, see
2206 Legacy ("v2") onion services will still work for the foreseeable
2207 future, and will remain the default until this new codebase gets
2208 tested and hardened. Service operators who want to experiment with
2209 the new system can use the 'HiddenServiceVersion 3' torrc
2210 directive along with the regular onion service configuration
2211 options. For more information, see our blog post at
2212 "https://blog.torproject.org/fall-harvest". Enjoy!
2214 o Major feature (scheduler, channel):
2215 - Tor now uses new schedulers to decide which circuits should
2216 deliver cells first, in order to improve congestion at relays. The
2217 first type is called "KIST" ("Kernel Informed Socket Transport"),
2218 and is only available on Linux-like systems: it uses feedback from
2219 the kernel to prevent the kernel's TCP buffers from growing too
2220 full. The second new scheduler type is called "KISTLite": it
2221 behaves the same as KIST, but runs on systems without kernel
2222 support for inspecting TCP implementation details. The old
2223 scheduler is still available, under the name "Vanilla". To change
2224 the default scheduler preference order, use the new "Schedulers"
2225 option. (The default preference order is "KIST,KISTLite,Vanilla".)
2227 Matt Traudt implemented KIST, based on research by Rob Jansen,
2228 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
2229 more information, see the design paper at
2230 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
2231 followup implementation paper at https://arxiv.org/abs/1709.01044.
2232 Closes ticket 12541. For more information, see our blog post at
2233 "https://blog.torproject.org/kist-and-tell".
2235 o Major bugfixes (security, general):
2236 - Fix a denial of service bug where an attacker could use a
2237 malformed directory object to cause a Tor instance to pause while
2238 OpenSSL would try to read a passphrase from the terminal. (Tor
2239 instances run without a terminal, which is the case for most Tor
2240 packages, are not impacted.) Fixes bug 24246; bugfix on every
2241 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2242 Found by OSS-Fuzz as testcase 6360145429790720.
2244 o Major bugfixes (security, directory authority):
2245 - Fix a denial of service issue where an attacker could crash a
2246 directory authority using a malformed router descriptor. Fixes bug
2247 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2250 o Major bugfixes (security, onion service v2):
2251 - Fix a use-after-free error that could crash v2 Tor onion services
2252 when they failed to open circuits while expiring introduction
2253 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2254 also tracked as TROVE-2017-013 and CVE-2017-8823.
2255 - When checking for replays in the INTRODUCE1 cell data for a
2256 (legacy) onion service, correctly detect replays in the RSA-
2257 encrypted part of the cell. We were previously checking for
2258 replays on the entire cell, but those can be circumvented due to
2259 the malleability of Tor's legacy hybrid encryption. This fix helps
2260 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2261 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2264 o Major bugfixes (security, relay):
2265 - When running as a relay, make sure that we never build a path
2266 through ourselves, even in the case where we have somehow lost the
2267 version of our descriptor appearing in the consensus. Fixes part
2268 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2269 as TROVE-2017-012 and CVE-2017-8822.
2270 - When running as a relay, make sure that we never choose ourselves
2271 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2272 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2274 o Major bugfixes (bootstrapping):
2275 - Fetch descriptors aggressively whenever we lack enough to build
2276 circuits, regardless of how many descriptors we are missing.
2277 Previously, we would delay launching the fetch when we had fewer
2278 than 15 missing descriptors, even if some of those descriptors
2279 were blocking circuits from building. Fixes bug 23985; bugfix on
2280 0.1.1.11-alpha. The effects of this bug became worse in
2281 0.3.0.3-alpha, when we began treating missing descriptors from our
2282 primary guards as a reason to delay circuits.
2283 - Don't try fetching microdescriptors from relays that have failed
2284 to deliver them in the past. Fixes bug 23817; bugfix
2287 o Major bugfixes (circuit prediction):
2288 - Fix circuit prediction logic so that a client doesn't treat a port
2289 as being "handled" by a circuit if that circuit already has
2290 isolation settings on it. This change should make Tor clients more
2291 responsive by improving their chances of having a pre-created
2292 circuit ready for use when a request arrives. Fixes bug 18859;
2293 bugfix on 0.2.3.3-alpha.
2295 o Major bugfixes (exit relays, DNS):
2296 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2297 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2298 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2299 identifying and finding a workaround to this bug and to Moritz,
2300 Arthur Edelstein, and Roger for helping to track it down and
2303 o Major bugfixes (relay, crash, assertion failure):
2304 - Fix a timing-based assertion failure that could occur when the
2305 circuit out-of-memory handler freed a connection's output buffer.
2306 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2308 o Major bugfixes (usability, control port):
2309 - Report trusted clock skew indications as bootstrap errors, so
2310 controllers can more easily alert users when their clocks are
2311 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
2313 o Minor features (bridge):
2314 - Bridge relays can now set the BridgeDistribution config option to
2315 add a "bridge-distribution-request" line to their bridge
2316 descriptor, which tells BridgeDB how they'd like their bridge
2317 address to be given out. (Note that as of Oct 2017, BridgeDB does
2318 not yet implement this feature.) As a side benefit, this feature
2319 provides a way to distinguish bridge descriptors from non-bridge
2320 descriptors. Implements tickets 18329.
2321 - When handling the USERADDR command on an ExtOrPort, warn when the
2322 transports provides a USERADDR with no port. In a future version,
2323 USERADDR commands of this format may be rejected. Detects problems
2324 related to ticket 23080.
2326 o Minor features (bug detection):
2327 - Log a warning message with a stack trace for any attempt to call
2328 get_options() during option validation. This pattern has caused
2329 subtle bugs in the past. Closes ticket 22281.
2331 o Minor features (build, compilation):
2332 - The "check-changes" feature is now part of the "make check" tests;
2333 we'll use it to try to prevent misformed changes files from
2334 accumulating. Closes ticket 23564.
2335 - Tor builds should now fail if there are any mismatches between the
2336 C type representing a configuration variable and the C type the
2337 data-driven parser uses to store a value there. Previously, we
2338 needed to check these by hand, which sometimes led to mistakes.
2339 Closes ticket 23643.
2341 o Minor features (client):
2342 - You can now use Tor as a tunneled HTTP proxy: use the new
2343 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
2344 requests. Closes ticket 22407.
2345 - Add an extra check to make sure that we always use the newer guard
2346 selection code for picking our guards. Closes ticket 22779.
2347 - When downloading (micro)descriptors, don't split the list into
2348 multiple requests unless we want at least 32 descriptors.
2349 Previously, we split at 4, not 32, which led to significant
2350 overhead in HTTP request size and degradation in compression
2351 performance. Closes ticket 23220.
2352 - Improve log messages when missing descriptors for primary guards.
2353 Resolves ticket 23670.
2355 o Minor features (command line):
2356 - Add a new commandline option, --key-expiration, which prints when
2357 the current signing key is going to expire. Implements ticket
2358 17639; patch by Isis Lovecruft.
2360 o Minor features (control port):
2361 - If an application tries to use the control port as an HTTP proxy,
2362 respond with a meaningful "This is the Tor control port" message,
2363 and log the event. Closes ticket 1667. Patch from Ravi
2365 - Provide better error message for GETINFO desc/(id|name) when not
2366 fetching router descriptors. Closes ticket 5847. Patch by
2368 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
2369 whether Tor will try to download router descriptors and
2370 microdescriptors respectively. Closes ticket 22684.
2371 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
2372 so controllers can tell whether the geoip databases are loaded.
2373 Closes ticket 23237.
2374 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
2375 events. Closes ticket 19254. Patch by "DonnchaC".
2377 o Minor features (development support):
2378 - Developers can now generate a call-graph for Tor using the
2379 "calltool" python program, which post-processes object dumps. It
2380 should work okay on many Linux and OSX platforms, and might work
2381 elsewhere too. To run it, install calltool from
2382 https://gitweb.torproject.org/user/nickm/calltool.git and run
2383 "make callgraph". Closes ticket 19307.
2385 o Minor features (directory authority):
2386 - Make the "Exit" flag assignment only depend on whether the exit
2387 policy allows connections to ports 80 and 443. Previously relays
2388 would get the Exit flag if they allowed connections to one of
2389 these ports and also port 6667. Resolves ticket 23637.
2391 o Minor features (ed25519):
2392 - Add validation function to checks for torsion components in
2393 ed25519 public keys, used by prop224 client-side code. Closes
2394 ticket 22006. Math help by Ian Goldberg.
2396 o Minor features (exit relay, DNS):
2397 - Improve the clarity and safety of the log message from evdns when
2398 receiving an apparently spoofed DNS reply. Closes ticket 3056.
2400 o Minor features (fallback directory mirrors):
2401 - The fallback directory list has been re-generated based on the
2402 current status of the network. Tor uses fallback directories to
2403 bootstrap when it doesn't yet have up-to-date directory
2404 information. Closes ticket 24801.
2405 - Make the default DirAuthorityFallbackRate 0.1, so that clients
2406 prefer to bootstrap from fallback directory mirrors. This is a
2407 follow-up to 24679, which removed weights from the default
2408 fallbacks. Implements ticket 24681.
2410 o Minor features (geoip):
2411 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
2414 o Minor features (integration, hardening):
2415 - Add a new NoExec option to prevent Tor from running other
2416 programs. When this option is set to 1, Tor will never try to run
2417 another program, regardless of the settings of
2418 PortForwardingHelper, ClientTransportPlugin, or
2419 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
2420 without restarting Tor. Closes ticket 22976.
2422 o Minor features (linux seccomp2 sandbox):
2423 - Update the sandbox rules so that they should now work correctly
2424 with Glibc 2.26. Closes ticket 24315.
2426 o Minor features (logging):
2427 - Provide better warnings when the getrandom() syscall fails. Closes
2429 - Downgrade a pair of log messages that could occur when an exit's
2430 resolver gave us an unusual (but not forbidden) response. Closes
2432 - Improve the message we log when re-enabling circuit build timeouts
2433 after having received a consensus. Closes ticket 20963.
2434 - Log more circuit information whenever we are about to try to
2435 package a relay cell on a circuit with a nonexistent n_chan.
2436 Attempt to diagnose ticket 8185.
2437 - Improve info-level log identification of particular circuits, to
2438 help with debugging. Closes ticket 23645.
2439 - Improve the warning message for specifying a relay by nickname.
2440 The previous message implied that nickname registration was still
2441 part of the Tor network design, which it isn't. Closes
2443 - If the sandbox filter fails to load, suggest to the user that
2444 their kernel might not support seccomp2. Closes ticket 23090.
2446 o Minor features (onion service, circuit, logging):
2447 - Improve logging of many callsite in the circuit subsystem to print
2448 the circuit identifier(s).
2449 - Log when we cleanup an intro point from a service so we know when
2450 and for what reason it happened. Closes ticket 23604.
2452 o Minor features (portability):
2453 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
2454 (It doesn't yet work with the sandbox enabled.) Closes
2456 - Check at configure time whether uint8_t is the same type as
2457 unsigned char. Lots of existing code already makes this
2458 assumption, and there could be strict aliasing issues if the
2459 assumption is violated. Closes ticket 22410.
2461 o Minor features (relay):
2462 - When choosing which circuits can be expired as unused, consider
2463 circuits from clients even if those clients used regular CREATE
2464 cells to make them; and do not consider circuits from relays even
2465 if they were made with CREATE_FAST. Part of ticket 22805.
2466 - Reject attempts to use relative file paths when RunAsDaemon is
2467 set. Previously, Tor would accept these, but the directory-
2468 changing step of RunAsDaemon would give strange and/or confusing
2469 results. Closes ticket 22731.
2471 o Minor features (relay statistics):
2472 - Change relay bandwidth reporting stats interval from 4 hours to 24
2473 hours in order to reduce the efficiency of guard discovery
2474 attacks. Fixes ticket 23856.
2476 o Minor features (reverted deprecations):
2477 - The ClientDNSRejectInternalAddresses flag can once again be set in
2478 non-testing Tor networks, so long as they do not use the default
2479 directory authorities. This change also removes the deprecation of
2480 this flag from 0.2.9.2-alpha. Closes ticket 21031.
2482 o Minor features (robustness):
2483 - Change several fatal assertions when flushing buffers into non-
2484 fatal assertions, to prevent any recurrence of 23690.
2486 o Minor features (startup, safety):
2487 - When configured to write a PID file, Tor now exits if it is unable
2488 to do so. Previously, it would warn and continue. Closes
2491 o Minor features (static analysis):
2492 - The BUG() macro has been changed slightly so that Coverity no
2493 longer complains about dead code if the bug is impossible. Closes
2496 o Minor features (testing):
2497 - Our fuzzing tests now test the encrypted portions of v3 onion
2498 service descriptors. Implements more of 21509.
2499 - Add a unit test to make sure that our own generated platform
2500 string will be accepted by directory authorities. Closes
2502 - The default chutney network tests now include tests for the v3
2503 onion service design. Make sure you have the latest version of
2504 chutney if you want to run these. Closes ticket 22437.
2505 - Add a unit test to verify that we can parse a hardcoded v2 onion
2506 service descriptor. Closes ticket 15554.
2508 o Minor bugfixes (address selection):
2509 - When the fascist_firewall_choose_address_ functions don't find a
2510 reachable address, set the returned address to the null address
2511 and port. This is a precautionary measure, because some callers do
2512 not check the return value. Fixes bug 24736; bugfix
2515 o Minor bugfixes (bootstrapping):
2516 - When warning about state file clock skew, report the correct
2517 direction for the detected skew. Fixes bug 23606; bugfix
2520 o Minor bugfixes (bridge clients, bootstrap):
2521 - Retry directory downloads when we get our first bridge descriptor
2522 during bootstrap or while reconnecting to the network. Keep
2523 retrying every time we get a bridge descriptor, until we have a
2524 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
2525 - Stop delaying bridge descriptor fetches when we have cached bridge
2526 descriptors. Instead, only delay bridge descriptor fetches when we
2527 have at least one reachable bridge. Fixes part of bug 24367;
2528 bugfix on 0.2.0.3-alpha.
2529 - Stop delaying directory fetches when we have cached bridge
2530 descriptors. Instead, only delay bridge descriptor fetches when
2531 all our bridges are definitely unreachable. Fixes part of bug
2532 24367; bugfix on 0.2.0.3-alpha.
2534 o Minor bugfixes (bridge):
2535 - Overwrite the bridge address earlier in the process of retrieving
2536 its descriptor, to make sure we reach it on the configured
2537 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
2539 o Minor bugfixes (build, compilation):
2540 - Fix a compilation warning when building with zstd support on
2541 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
2542 and fixed by Andreas Stieger.
2543 - When searching for OpenSSL, don't accept any OpenSSL library that
2544 lacks TLSv1_1_method(): Tor doesn't build with those versions.
2545 Additionally, look in /usr/local/opt/openssl, if it's present.
2546 These changes together repair the default build on OSX systems
2547 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
2548 - Fix a signed/unsigned comparison warning introduced by our fix to
2549 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
2550 - Fix a memory leak warning in one of the libevent-related
2551 configuration tests that could occur when manually specifying
2552 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
2553 Found and patched by Alex Xu.
2554 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
2555 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2557 o Minor bugfixes (certificate handling):
2558 - Fix a time handling bug in Tor certificates set to expire after
2559 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
2560 Coverity as CID 1415728.
2562 o Minor bugfixes (client):
2563 - By default, do not enable storage of client-side DNS values. These
2564 values were unused by default previously, but they should not have
2565 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
2567 o Minor bugfixes (client, usability):
2568 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
2569 SOCKS4a requests that contain IP address strings, even when
2570 SafeSocks in enabled, as this prevents user from connecting to
2571 known IP addresses without relying on DNS for resolving. SafeSocks
2572 still rejects SOCKS connections that connect to IP addresses when
2573 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
2574 bugfix on Tor 0.2.6.2-alpha.
2576 o Minor bugfixes (code correctness):
2577 - Call htons() in extend_cell_format() for encoding a 16-bit value.
2578 Previously we used ntohs(), which happens to behave the same on
2579 all the platforms we support, but which isn't really correct.
2580 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
2581 - For defense-in-depth, make the controller's write_escaped_data()
2582 function robust to extremely long inputs. Fixes bug 19281; bugfix
2583 on 0.1.1.1-alpha. Reported by Guido Vranken.
2584 - Fix several places in our codebase where a C compiler would be
2585 likely to eliminate a check, based on assuming that undefined
2586 behavior had not happened elsewhere in the code. These cases are
2587 usually a sign of redundant checking or dubious arithmetic. Found
2588 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
2589 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
2592 o Minor bugfixes (compression):
2593 - Handle a pathological case when decompressing Zstandard data when
2594 the output buffer size is zero. Fixes bug 23551; bugfix
2597 o Minor bugfixes (consensus expiry):
2598 - Check for adequate directory information correctly. Previously, Tor
2599 would reconsider whether it had sufficient directory information
2600 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
2602 o Minor bugfixes (control port, linux seccomp2 sandbox):
2603 - Avoid a crash when attempting to use the seccomp2 sandbox together
2604 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
2607 o Minor bugfixes (control port, onion services):
2608 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
2609 HS_DESC event when a service is not able to upload a descriptor.
2610 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
2612 o Minor bugfixes (directory cache):
2613 - Recover better from empty or corrupt files in the consensus cache
2614 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
2615 - When a consensus diff calculation is only partially successful,
2616 only record the successful parts as having succeeded. Partial
2617 success can happen if (for example) one compression method fails
2618 but the others succeed. Previously we misrecorded all the
2619 calculations as having succeeded, which would later cause a
2620 nonfatal assertion failure. Fixes bug 24086; bugfix
2623 o Minor bugfixes (directory client):
2624 - On failure to download directory information, delay retry attempts
2625 by a random amount based on the "decorrelated jitter" algorithm.
2626 Our previous delay algorithm tended to produce extra-long delays
2627 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
2629 o Minor bugfixes (directory protocol):
2630 - Directory servers now include a "Date:" http header for response
2631 codes other than 200. Clients starting with a skewed clock and a
2632 recent consensus were getting "304 Not modified" responses from
2633 directory authorities, so without the Date header, the client
2634 would never hear about a wrong clock. Fixes bug 23499; bugfix
2636 - Make clients wait for 6 seconds before trying to download a
2637 consensus from an authority. Fixes bug 17750; bugfix
2640 o Minor bugfixes (documentation):
2641 - Document better how to read gcov, and what our gcov postprocessing
2642 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
2643 - Fix manpage to not refer to the obsolete (and misspelled)
2644 UseEntryGuardsAsDirectoryGuards parameter in the description of
2645 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
2647 o Minor bugfixes (DoS-resistance):
2648 - If future code asks if there are any running bridges, without
2649 checking if bridges are enabled, log a BUG warning rather than
2650 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
2652 o Minor bugfixes (entry guards):
2653 - Tor now updates its guard state when it reads a consensus
2654 regardless of whether it's missing descriptors. That makes tor use
2655 its primary guards to fetch descriptors in some edge cases where
2656 it would previously have used fallback directories. Fixes bug
2657 23862; bugfix on 0.3.0.1-alpha.
2659 o Minor bugfixes (format strictness):
2660 - Restrict several data formats to decimal. Previously, the
2661 BuildTimeHistogram entries in the state file, the "bw=" entries in
2662 the bandwidth authority file, and the process IDs passed to the
2663 __OwningControllerProcess option could all be specified in hex or
2664 octal as well as in decimal. This was not an intentional feature.
2665 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
2668 o Minor bugfixes (heartbeat):
2669 - If we fail to write a heartbeat message, schedule a retry for the
2670 minimum heartbeat interval number of seconds in the future. Fixes
2671 bug 19476; bugfix on 0.2.3.1-alpha.
2673 o Minor bugfixes (logging):
2674 - Suppress a log notice when relay descriptors arrive. We already
2675 have a bootstrap progress for this so no need to log notice
2676 everytime tor receives relay descriptors. Microdescriptors behave
2677 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
2678 - Remove duplicate log messages regarding opening non-local
2679 SocksPorts upon parsing config and opening listeners at startup.
2680 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
2681 - Use a more comprehensible log message when telling the user
2682 they've excluded every running exit node. Fixes bug 7890; bugfix
2684 - When logging the number of descriptors we intend to download per
2685 directory request, do not log a number higher than then the number
2686 of descriptors we're fetching in total. Fixes bug 19648; bugfix
2688 - When warning about a directory owned by the wrong user, log the
2689 actual name of the user owning the directory. Previously, we'd log
2690 the name of the process owner twice. Fixes bug 23487; bugfix
2692 - Fix some messages on unexpected errors from the seccomp2 library.
2693 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
2694 - The tor specification says hop counts are 1-based, so fix two log
2695 messages that mistakenly logged 0-based hop counts. Fixes bug
2696 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
2697 Credit to Xiaofan Li for reporting this issue.
2699 o Minor bugfixes (logging, relay shutdown, annoyance):
2700 - When a circuit is marked for close, do not attempt to package any
2701 cells for channels on that circuit. Previously, we would detect
2702 this condition lower in the call stack, when we noticed that the
2703 circuit had no attached channel, and log an annoying message.
2704 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2706 o Minor bugfixes (memory safety, defensive programming):
2707 - Clear the target address when node_get_prim_orport() returns
2708 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2710 o Minor bugfixes (memory usage):
2711 - When queuing DESTROY cells on a channel, only queue the circuit-id
2712 and reason fields: not the entire 514-byte cell. This fix should
2713 help mitigate any bugs or attacks that fill up these queues, and
2714 free more RAM for other uses. Fixes bug 24666; bugfix
2717 o Minor bugfixes (network layer):
2718 - When closing a connection via close_connection_immediately(), we
2719 mark it as "not blocked on bandwidth", to prevent later calls from
2720 trying to unblock it, and give it permission to read. This fixes a
2721 backtrace warning that can happen on relays under various
2722 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
2724 o Minor bugfixes (onion services):
2725 - The introduction circuit was being timed out too quickly while
2726 waiting for the rendezvous circuit to complete. Keep the intro
2727 circuit around longer instead of timing out and reopening new ones
2728 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
2729 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2730 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2732 - When handling multiple SOCKS request for the same .onion address,
2733 only fetch the service descriptor once.
2734 - Avoid a possible double close of a circuit by the intro point on
2735 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2736 bugfix on 0.3.0.1-alpha.
2737 - When reloading configured onion services, copy all information
2738 from the old service object. Previously, some data was omitted,
2739 causing delays in descriptor upload, and other bugs. Fixes bug
2740 23790; bugfix on 0.2.1.9-alpha.
2742 o Minor bugfixes (path selection):
2743 - When selecting relays by bandwidth, avoid a rounding error that
2744 could sometimes cause load to be imbalanced incorrectly.
2745 Previously, we would always round upwards; now, we round towards
2746 the nearest integer. This had the biggest effect when a relay's
2747 weight adjustments should have given it weight 0, but it got
2748 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
2749 - When calculating the fraction of nodes that have descriptors, and
2750 all nodes in the network have zero bandwidths, count the number of
2751 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
2752 - Actually log the total bandwidth in compute_weighted_bandwidths().
2753 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
2755 o Minor bugfixes (portability):
2756 - Stop using the PATH_MAX variable, which is not defined on GNU
2757 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
2758 - Fix a bug in the bit-counting parts of our timing-wheel code on
2759 MSVC. (Note that MSVC is still not a supported build platform, due
2760 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
2763 o Minor bugfixes (relay):
2764 - When uploading our descriptor for the first time after startup,
2765 report the reason for uploading as "Tor just started" rather than
2766 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
2767 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2768 relays, to prevent spurious address resolutions and descriptor
2769 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2770 bugfix on in 0.2.8.1-alpha.
2771 - Avoid a crash when transitioning from client mode to bridge mode.
2772 Previously, we would launch the worker threads whenever our
2773 "public server" mode changed, but not when our "server" mode
2774 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2776 o Minor bugfixes (testing):
2777 - Fix a spurious fuzzing-only use of an uninitialized value. Found
2778 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
2779 - Test that IPv6-only clients can use microdescriptors when running
2780 "make test-network-all". Requires chutney master 61c28b9 or later.
2781 Closes ticket 24109.
2782 - Prevent scripts/test/coverage from attempting to move gcov output
2783 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
2784 - Capture and detect several "Result does not fit" warnings in unit
2785 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
2787 - Fix additional channelpadding unit test failures by using mocked
2788 time instead of actual time for all tests. Fixes bug 23608; bugfix
2790 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
2791 to correctly handle cases where a caller gives it an RSA key of
2792 under 160 bits. (This is not actually a bug in Tor itself, but
2793 rather in our fuzzing code.) Fixes bug 24247; bugfix on
2794 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
2795 - Fix a broken unit test for the OutboundAddress option: the parsing
2796 function was never returning an error on failure. Fixes bug 23366;
2797 bugfix on 0.3.0.3-alpha.
2798 - Fix a signed-integer overflow in the unit tests for
2799 dir/download_status_random_backoff, which was untriggered until we
2800 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
2802 o Minor bugfixes (usability, control port):
2803 - Stop making an unnecessary routerlist check in NETINFO clock skew
2804 detection; this was preventing clients from reporting NETINFO clock
2805 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
2807 o Code simplification and refactoring:
2808 - Remove various ways of testing circuits and connections for
2809 "clientness"; instead, favor channel_is_client(). Part of
2811 - Extract the code for handling newly-open channels into a separate
2812 function from the general code to handle channel state
2813 transitions. This change simplifies our callgraph, reducing the
2814 size of the largest strongly connected component by roughly a
2815 factor of two. Closes ticket 22608.
2816 - Remove dead code for largely unused statistics on the number of
2817 times we've attempted various public key operations. Fixes bug
2818 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
2819 - Remove several now-obsolete functions for asking about old
2820 variants directory authority status. Closes ticket 22311; patch
2822 - Remove some of the code that once supported "Named" and "Unnamed"
2823 routers. Authorities no longer vote for these flags. Closes
2825 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
2826 and old hidden services, to indicate that they aren't suitable for
2827 new protocols or formats. Closes ticket 23026.
2828 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
2829 22521. Patch from Neel Chauhan.
2830 - Split the enormous circuit_send_next_onion_skin() function into
2831 multiple subfunctions. Closes ticket 22804.
2832 - Split the portions of the buffer.c module that handle particular
2833 protocols into separate modules. Part of ticket 23149.
2834 - Use our test macros more consistently, to produce more useful
2835 error messages when our unit tests fail. Add coccinelle patches to
2836 allow us to re-check for test macro uses. Closes ticket 22497.
2838 o Deprecated features:
2839 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
2840 now deprecated; they do not apply to relays, and they have had no
2841 effect on clients since 0.2.8.x. Closes ticket 19704.
2842 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
2843 only applies to direct unencrypted HTTP connections to your
2844 directory server, which your Tor probably isn't using. Closes
2848 - Add notes in man page regarding OS support for the various
2849 scheduler types. Attempt to use less jargon in the scheduler
2850 section. Closes ticket 24254.
2851 - Clarify that the Address option is entirely about setting an
2852 advertised IPv4 address. Closes ticket 18891.
2853 - Clarify the manpage's use of the term "address" to clarify what
2854 kind of address is intended. Closes ticket 21405.
2855 - Document that onion service subdomains are allowed, and ignored.
2856 Closes ticket 18736.
2857 - Clarify in the manual that "Sandbox 1" is only supported on Linux
2858 kernels. Closes ticket 22677.
2859 - Document all values of PublishServerDescriptor in the manpage.
2860 Closes ticket 15645.
2861 - Improve the documentation for the directory port part of the
2862 DirAuthority line. Closes ticket 20152.
2863 - Restore documentation for the authorities' "approved-routers"
2864 file. Closes ticket 21148.
2867 - The AllowDotExit option has been removed as unsafe. It has been
2868 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
2869 - The ClientDNSRejectInternalAddresses flag can no longer be set on
2870 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
2871 Closes ticket 21031.
2872 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
2873 nobody was using it any longer. Closes ticket 22377.
2876 Changes in version 0.3.1.9 - 2017-12-01:
2877 Tor 0.3.1.9 backports important security and stability fixes from the
2878 0.3.2 development series. All Tor users should upgrade to this
2879 release, or to another of the releases coming out today.
2881 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2882 - Fix a denial of service bug where an attacker could use a
2883 malformed directory object to cause a Tor instance to pause while
2884 OpenSSL would try to read a passphrase from the terminal. (Tor
2885 instances run without a terminal, which is the case for most Tor
2886 packages, are not impacted.) Fixes bug 24246; bugfix on every
2887 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2888 Found by OSS-Fuzz as testcase 6360145429790720.
2889 - Fix a denial of service issue where an attacker could crash a
2890 directory authority using a malformed router descriptor. Fixes bug
2891 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2893 - When checking for replays in the INTRODUCE1 cell data for a
2894 (legacy) onion service, correctly detect replays in the RSA-
2895 encrypted part of the cell. We were previously checking for
2896 replays on the entire cell, but those can be circumvented due to
2897 the malleability of Tor's legacy hybrid encryption. This fix helps
2898 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2899 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2902 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2903 - Fix a use-after-free error that could crash v2 Tor onion services
2904 when they failed to open circuits while expiring introduction
2905 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2906 also tracked as TROVE-2017-013 and CVE-2017-8823.
2908 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2909 - When running as a relay, make sure that we never build a path
2910 through ourselves, even in the case where we have somehow lost the
2911 version of our descriptor appearing in the consensus. Fixes part
2912 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2913 as TROVE-2017-012 and CVE-2017-8822.
2914 - When running as a relay, make sure that we never choose ourselves
2915 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2916 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2918 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2919 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2920 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2921 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2922 identifying and finding a workaround to this bug and to Moritz,
2923 Arthur Edelstein, and Roger for helping to track it down and
2926 o Minor features (bridge):
2927 - Bridges now include notice in their descriptors that they are
2928 bridges, and notice of their distribution status, based on their
2929 publication settings. Implements ticket 18329. For more fine-
2930 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2933 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2934 - Add an IPv6 address for the "bastet" directory authority. Closes
2937 o Minor features (geoip):
2938 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2941 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2942 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2943 relays, to prevent spurious address resolutions and descriptor
2944 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2945 bugfix on in 0.2.8.1-alpha.
2947 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2948 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2949 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2951 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2952 - When a circuit is marked for close, do not attempt to package any
2953 cells for channels on that circuit. Previously, we would detect
2954 this condition lower in the call stack, when we noticed that the
2955 circuit had no attached channel, and log an annoying message.
2956 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2958 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
2959 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2960 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2963 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2964 - Avoid a crash when transitioning from client mode to bridge mode.
2965 Previously, we would launch the worker threads whenever our
2966 "public server" mode changed, but not when our "server" mode
2967 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2970 Changes in version 0.3.0.13 - 2017-12-01
2971 Tor 0.3.0.13 backports important security and stability bugfixes from
2972 later Tor releases. All Tor users should upgrade to this release, or
2973 to another of the releases coming out today.
2975 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
2976 2018. If you need a release with long-term support, please stick with
2977 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2979 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2980 - Fix a denial of service bug where an attacker could use a
2981 malformed directory object to cause a Tor instance to pause while
2982 OpenSSL would try to read a passphrase from the terminal. (Tor
2983 instances run without a terminal, which is the case for most Tor
2984 packages, are not impacted.) Fixes bug 24246; bugfix on every
2985 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2986 Found by OSS-Fuzz as testcase 6360145429790720.
2987 - Fix a denial of service issue where an attacker could crash a
2988 directory authority using a malformed router descriptor. Fixes bug
2989 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2991 - When checking for replays in the INTRODUCE1 cell data for a
2992 (legacy) onion service, correctly detect replays in the RSA-
2993 encrypted part of the cell. We were previously checking for
2994 replays on the entire cell, but those can be circumvented due to
2995 the malleability of Tor's legacy hybrid encryption. This fix helps
2996 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2997 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
3000 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
3001 - Fix a use-after-free error that could crash v2 Tor onion services
3002 when they failed to open circuits while expiring introduction
3003 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
3004 also tracked as TROVE-2017-013 and CVE-2017-8823.
3006 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
3007 - When running as a relay, make sure that we never build a path
3008 through ourselves, even in the case where we have somehow lost the
3009 version of our descriptor appearing in the consensus. Fixes part
3010 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
3011 as TROVE-2017-012 and CVE-2017-8822.
3012 - When running as a relay, make sure that we never choose ourselves
3013 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
3014 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
3016 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
3017 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
3018 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
3019 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
3020 identifying and finding a workaround to this bug and to Moritz,
3021 Arthur Edelstein, and Roger for helping to track it down and
3024 o Minor features (security, windows, backport from 0.3.1.1-alpha):
3025 - Enable a couple of pieces of Windows hardening: one
3026 (HeapEnableTerminationOnCorruption) that has been on-by-default
3027 since Windows 8, and unavailable before Windows 7; and one
3028 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
3029 affect us, but shouldn't do any harm. Closes ticket 21953.
3031 o Minor features (bridge, backport from 0.3.1.9):
3032 - Bridges now include notice in their descriptors that they are
3033 bridges, and notice of their distribution status, based on their
3034 publication settings. Implements ticket 18329. For more fine-
3035 grained control of how a bridge is distributed, upgrade to 0.3.2.x
3038 o Minor features (directory authority, backport from 0.3.2.6-alpha):
3039 - Add an IPv6 address for the "bastet" directory authority. Closes
3042 o Minor features (geoip):
3043 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
3046 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
3047 - Avoid unnecessary calls to directory_fetches_from_authorities() on
3048 relays, to prevent spurious address resolutions and descriptor
3049 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
3050 bugfix on in 0.2.8.1-alpha.
3052 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
3053 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
3054 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
3056 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
3057 - When a circuit is marked for close, do not attempt to package any
3058 cells for channels on that circuit. Previously, we would detect
3059 this condition lower in the call stack, when we noticed that the
3060 circuit had no attached channel, and log an annoying message.
3061 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
3063 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
3064 - Avoid a crash when transitioning from client mode to bridge mode.
3065 Previously, we would launch the worker threads whenever our
3066 "public server" mode changed, but not when our "server" mode
3067 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
3069 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
3070 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
3071 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
3074 Changes in version 0.2.9.14 - 2017-12-01
3075 Tor 0.3.0.13 backports important security and stability bugfixes from
3076 later Tor releases. All Tor users should upgrade to this release, or
3077 to another of the releases coming out today.
3079 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
3080 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
3081 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
3082 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
3083 identifying and finding a workaround to this bug and to Moritz,
3084 Arthur Edelstein, and Roger for helping to track it down and
3087 o Major bugfixes (security, backport from 0.3.2.6-alpha):
3088 - Fix a denial of service bug where an attacker could use a
3089 malformed directory object to cause a Tor instance to pause while
3090 OpenSSL would try to read a passphrase from the terminal. (Tor
3091 instances run without a terminal, which is the case for most Tor
3092 packages, are not impacted.) Fixes bug 24246; bugfix on every
3093 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
3094 Found by OSS-Fuzz as testcase 6360145429790720.
3095 - Fix a denial of service issue where an attacker could crash a
3096 directory authority using a malformed router descriptor. Fixes bug
3097 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
3099 - When checking for replays in the INTRODUCE1 cell data for a
3100 (legacy) onion service, correctly detect replays in the RSA-
3101 encrypted part of the cell. We were previously checking for
3102 replays on the entire cell, but those can be circumvented due to
3103 the malleability of Tor's legacy hybrid encryption. This fix helps
3104 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
3105 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
3108 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
3109 - Fix a use-after-free error that could crash v2 Tor onion services
3110 when they failed to open circuits while expiring introduction
3111 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
3112 also tracked as TROVE-2017-013 and CVE-2017-8823.
3114 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
3115 - When running as a relay, make sure that we never build a path
3116 through ourselves, even in the case where we have somehow lost the
3117 version of our descriptor appearing in the consensus. Fixes part
3118 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
3119 as TROVE-2017-012 and CVE-2017-8822.
3121 o Minor features (bridge, backport from 0.3.1.9):
3122 - Bridges now include notice in their descriptors that they are
3123 bridges, and notice of their distribution status, based on their
3124 publication settings. Implements ticket 18329. For more fine-
3125 grained control of how a bridge is distributed, upgrade to 0.3.2.x
3128 o Minor features (directory authority, backport from 0.3.2.6-alpha):
3129 - Add an IPv6 address for the "bastet" directory authority. Closes
3132 o Minor features (geoip):
3133 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
3136 o Minor features (security, windows, backport from 0.3.1.1-alpha):
3137 - Enable a couple of pieces of Windows hardening: one
3138 (HeapEnableTerminationOnCorruption) that has been on-by-default
3139 since Windows 8, and unavailable before Windows 7; and one
3140 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
3141 affect us, but shouldn't do any harm. Closes ticket 21953.
3143 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
3144 - Avoid unnecessary calls to directory_fetches_from_authorities() on
3145 relays, to prevent spurious address resolutions and descriptor
3146 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
3147 bugfix on in 0.2.8.1-alpha.
3149 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
3150 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
3151 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
3153 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
3154 - When a circuit is marked for close, do not attempt to package any
3155 cells for channels on that circuit. Previously, we would detect
3156 this condition lower in the call stack, when we noticed that the
3157 circuit had no attached channel, and log an annoying message.
3158 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
3160 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
3161 - Avoid a crash when transitioning from client mode to bridge mode.
3162 Previously, we would launch the worker threads whenever our
3163 "public server" mode changed, but not when our "server" mode
3164 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
3166 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
3167 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
3168 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
3171 Changes in version 0.2.8.17 - 2017-12-01
3172 Tor 0.2.8.17 backports important security and stability bugfixes from
3173 later Tor releases. All Tor users should upgrade to this release, or
3174 to another of the releases coming out today.
3176 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
3177 2018. If you need a release with long-term support, please upgrade with
3178 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3180 o Major bugfixes (security, backport from 0.3.2.6-alpha):
3181 - Fix a denial of service bug where an attacker could use a
3182 malformed directory object to cause a Tor instance to pause while
3183 OpenSSL would try to read a passphrase from the terminal. (Tor
3184 instances run without a terminal, which is the case for most Tor
3185 packages, are not impacted.) Fixes bug 24246; bugfix on every
3186 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
3187 Found by OSS-Fuzz as testcase 6360145429790720.
3188 - When checking for replays in the INTRODUCE1 cell data for a
3189 (legacy) onion service, correctly detect replays in the RSA-
3190 encrypted part of the cell. We were previously checking for
3191 replays on the entire cell, but those can be circumvented due to
3192 the malleability of Tor's legacy hybrid encryption. This fix helps
3193 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
3194 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
3197 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
3198 - Fix a use-after-free error that could crash v2 Tor onion services
3199 when they failed to open circuits while expiring introduction
3200 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
3201 also tracked as TROVE-2017-013 and CVE-2017-8823.
3203 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
3204 - When running as a relay, make sure that we never build a path through
3205 ourselves, even in the case where we have somehow lost the version of
3206 our descriptor appearing in the consensus. Fixes part of bug 21534;
3207 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
3210 o Minor features (bridge, backport from 0.3.1.9):
3211 - Bridges now include notice in their descriptors that they are
3212 bridges, and notice of their distribution status, based on their
3213 publication settings. Implements ticket 18329. For more fine-
3214 grained control of how a bridge is distributed, upgrade to 0.3.2.x
3217 o Minor features (directory authority, backport from 0.3.2.6-alpha):
3218 - Add an IPv6 address for the "bastet" directory authority. Closes
3221 o Minor features (geoip):
3222 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
3225 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
3226 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
3227 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
3230 Changes in version 0.2.5.16 - 2017-12-01
3231 Tor 0.2.5.13 backports important security and stability bugfixes from
3232 later Tor releases. All Tor users should upgrade to this release, or
3233 to another of the releases coming out today.
3235 Note: the Tor 0.2.5 series will no longer be supported after 1 May
3236 2018. If you need a release with long-term support, please upgrade to
3237 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3239 o Major bugfixes (security, backport from 0.3.2.6-alpha):
3240 - Fix a denial of service bug where an attacker could use a
3241 malformed directory object to cause a Tor instance to pause while
3242 OpenSSL would try to read a passphrase from the terminal. (Tor
3243 instances run without a terminal, which is the case for most Tor
3244 packages, are not impacted.) Fixes bug 24246; bugfix on every
3245 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
3246 Found by OSS-Fuzz as testcase 6360145429790720.
3247 - When checking for replays in the INTRODUCE1 cell data for a
3248 (legacy) onion service, correctly detect replays in the RSA-
3249 encrypted part of the cell. We were previously checking for
3250 replays on the entire cell, but those can be circumvented due to
3251 the malleability of Tor's legacy hybrid encryption. This fix helps
3252 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
3253 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
3256 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
3257 - When running as a relay, make sure that we never build a path
3258 through ourselves, even in the case where we have somehow lost the
3259 version of our descriptor appearing in the consensus. Fixes part
3260 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
3261 as TROVE-2017-012 and CVE-2017-8822.
3263 o Minor features (bridge, backport from 0.3.1.9):
3264 - Bridges now include notice in their descriptors that they are
3265 bridges, and notice of their distribution status, based on their
3266 publication settings. Implements ticket 18329. For more fine-
3267 grained control of how a bridge is distributed, upgrade to 0.3.2.x
3270 o Minor features (geoip):
3271 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
3275 Changes in version 0.2.5.15 - 2017-10-25
3276 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
3277 series. It also adds a new directory authority, Bastet.
3279 Note: the Tor 0.2.5 series will no longer be supported after 1 May
3280 2018. If you need a release with long-term support, please upgrade to
3281 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3283 o Directory authority changes:
3284 - Add "Bastet" as a ninth directory authority to the default list.
3285 Closes ticket 23910.
3286 - The directory authority "Longclaw" has changed its IP address.
3287 Closes ticket 23592.
3289 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3290 - Avoid an assertion failure bug affecting our implementation of
3291 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3292 handling of "0xx" differs from what we had expected. Fixes bug
3293 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3295 o Minor features (geoip):
3296 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3299 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3300 - Fix a memset() off the end of an array when packing cells. This
3301 bug should be harmless in practice, since the corrupted bytes are
3302 still in the same structure, and are always padding bytes,
3303 ignored, or immediately overwritten, depending on compiler
3304 behavior. Nevertheless, because the memset()'s purpose is to make
3305 sure that any other cell-handling bugs can't expose bytes to the
3306 network, we need to fix it. Fixes bug 22737; bugfix on
3307 0.2.4.11-alpha. Fixes CID 1401591.
3309 o Build features (backport from 0.3.1.5-alpha):
3310 - Tor's repository now includes a Travis Continuous Integration (CI)
3311 configuration file (.travis.yml). This is meant to help new
3312 developers and contributors who fork Tor to a Github repository be
3313 better able to test their changes, and understand what we expect
3314 to pass. To use this new build feature, you must fork Tor to your
3315 Github account, then go into the "Integrations" menu in the
3316 repository settings for your fork and enable Travis, then push
3317 your changes. Closes ticket 22636.
3320 Changes in version 0.2.8.16 - 2017-10-25
3321 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
3322 series, including a bugfix for a crash issue that had affected relays
3323 under memory pressure. It also adds a new directory authority, Bastet.
3325 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
3326 2018. If you need a release with long-term support, please stick with
3327 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3329 o Directory authority changes:
3330 - Add "Bastet" as a ninth directory authority to the default list.
3331 Closes ticket 23910.
3332 - The directory authority "Longclaw" has changed its IP address.
3333 Closes ticket 23592.
3335 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3336 - Fix a timing-based assertion failure that could occur when the
3337 circuit out-of-memory handler freed a connection's output buffer.
3338 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3340 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3341 - Remove longclaw's IPv6 address, as it will soon change. Authority
3342 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3343 3/8 directory authorities with IPv6 addresses, but there are also
3344 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3346 o Minor features (geoip):
3347 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3351 Changes in version 0.2.9.13 - 2017-10-25
3352 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
3353 series, including a bugfix for a crash issue that had affected relays
3354 under memory pressure. It also adds a new directory authority, Bastet.
3356 o Directory authority changes:
3357 - Add "Bastet" as a ninth directory authority to the default list.
3358 Closes ticket 23910.
3359 - The directory authority "Longclaw" has changed its IP address.
3360 Closes ticket 23592.
3362 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3363 - Fix a timing-based assertion failure that could occur when the
3364 circuit out-of-memory handler freed a connection's output buffer.
3365 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3367 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3368 - Remove longclaw's IPv6 address, as it will soon change. Authority
3369 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3370 3/8 directory authorities with IPv6 addresses, but there are also
3371 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3373 o Minor features (geoip):
3374 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3377 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
3378 - When a directory authority rejects a descriptor or extrainfo with
3379 a given digest, mark that digest as undownloadable, so that we do
3380 not attempt to download it again over and over. We previously
3381 tried to avoid downloading such descriptors by other means, but we
3382 didn't notice if we accidentally downloaded one anyway. This
3383 behavior became problematic in 0.2.7.2-alpha, when authorities
3384 began pinning Ed25519 keys. Fixes bug 22349; bugfix
3387 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
3388 - Clear the address when node_get_prim_orport() returns early.
3389 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
3391 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
3392 - When running as a Windows service, set the ID of the main thread
3393 correctly. Failure to do so made us fail to send log messages to
3394 the controller in 0.2.1.16-rc, slowed down controller event
3395 delivery in 0.2.7.3-rc and later, and crash with an assertion
3396 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
3397 Patch and diagnosis from "Vort".
3400 Changes in version 0.3.0.12 - 2017-10-25
3401 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
3402 series, including a bugfix for a crash issue that had affected relays
3403 under memory pressure. It also adds a new directory authority, Bastet.
3405 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
3406 2018. If you need a release with long-term support, please stick with
3407 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3409 o Directory authority changes:
3410 - Add "Bastet" as a ninth directory authority to the default list.
3411 Closes ticket 23910.
3412 - The directory authority "Longclaw" has changed its IP address.
3413 Closes ticket 23592.
3415 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3416 - Fix a timing-based assertion failure that could occur when the
3417 circuit out-of-memory handler freed a connection's output buffer.
3418 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3420 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3421 - Remove longclaw's IPv6 address, as it will soon change. Authority
3422 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3423 3/8 directory authorities with IPv6 addresses, but there are also
3424 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3426 o Minor features (geoip):
3427 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3430 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
3431 - When a directory authority rejects a descriptor or extrainfo with
3432 a given digest, mark that digest as undownloadable, so that we do
3433 not attempt to download it again over and over. We previously
3434 tried to avoid downloading such descriptors by other means, but we
3435 didn't notice if we accidentally downloaded one anyway. This
3436 behavior became problematic in 0.2.7.2-alpha, when authorities
3437 began pinning Ed25519 keys. Fixes bug 22349; bugfix
3440 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
3441 - Avoid a possible double close of a circuit by the intro point on
3442 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
3443 bugfix on 0.3.0.1-alpha.
3445 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
3446 - Clear the address when node_get_prim_orport() returns early.
3447 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
3449 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
3450 - When running as a Windows service, set the ID of the main thread
3451 correctly. Failure to do so made us fail to send log messages to
3452 the controller in 0.2.1.16-rc, slowed down controller event
3453 delivery in 0.2.7.3-rc and later, and crash with an assertion
3454 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
3455 Patch and diagnosis from "Vort".
3458 Changes in version 0.3.1.8 - 2017-10-25
3459 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
3460 It includes several bugfixes, including a bugfix for a crash issue
3461 that had affected relays under memory pressure. It also adds
3462 a new directory authority, Bastet.
3464 o Directory authority changes:
3465 - Add "Bastet" as a ninth directory authority to the default list.
3466 Closes ticket 23910.
3467 - The directory authority "Longclaw" has changed its IP address.
3468 Closes ticket 23592.
3470 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3471 - Fix a timing-based assertion failure that could occur when the
3472 circuit out-of-memory handler freed a connection's output buffer.
3473 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3475 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3476 - Remove longclaw's IPv6 address, as it will soon change. Authority
3477 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3478 3/8 directory authorities with IPv6 addresses, but there are also
3479 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3481 o Minor features (geoip):
3482 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3485 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
3486 - Fix a compilation warning when building with zstd support on
3487 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
3488 and fixed by Andreas Stieger.
3490 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
3491 - Handle a pathological case when decompressing Zstandard data when
3492 the output buffer size is zero. Fixes bug 23551; bugfix
3495 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
3496 - Remove the length limit on HTTP status lines that authorities can
3497 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
3499 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
3500 - Avoid a possible double close of a circuit by the intro point on
3501 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
3502 bugfix on 0.3.0.1-alpha.
3504 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
3505 - Clear the address when node_get_prim_orport() returns early.
3506 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
3508 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
3509 - Fix additional channelpadding unit test failures by using mocked
3510 time instead of actual time for all tests. Fixes bug 23608; bugfix
3514 Changes in version 0.2.8.15 - 2017-09-18
3515 Tor 0.2.8.15 backports a collection of bugfixes from later
3518 Most significantly, it includes a fix for TROVE-2017-008, a
3519 security bug that affects hidden services running with the
3520 SafeLogging option disabled. For more information, see
3521 https://trac.torproject.org/projects/tor/ticket/23490
3523 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
3524 2018. We suggest that you upgrade to the latest stable release if
3525 possible. If you can't, we recommend that you upgrade at least to
3526 0.2.9, which will be supported until 2020.
3528 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3529 - Avoid an assertion failure bug affecting our implementation of
3530 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3531 handling of "0xx" differs from what we had expected. Fixes bug
3532 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3535 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3538 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3539 - Backport a fix for an "unused variable" warning that appeared
3540 in some versions of mingw. Fixes bug 22838; bugfix on
3543 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3544 - Fix a memset() off the end of an array when packing cells. This
3545 bug should be harmless in practice, since the corrupted bytes are
3546 still in the same structure, and are always padding bytes,
3547 ignored, or immediately overwritten, depending on compiler
3548 behavior. Nevertheless, because the memset()'s purpose is to make
3549 sure that any other cell-handling bugs can't expose bytes to the
3550 network, we need to fix it. Fixes bug 22737; bugfix on
3551 0.2.4.11-alpha. Fixes CID 1401591.
3553 o Build features (backport from 0.3.1.5-alpha):
3554 - Tor's repository now includes a Travis Continuous Integration (CI)
3555 configuration file (.travis.yml). This is meant to help new
3556 developers and contributors who fork Tor to a Github repository be
3557 better able to test their changes, and understand what we expect
3558 to pass. To use this new build feature, you must fork Tor to your
3559 Github account, then go into the "Integrations" menu in the
3560 repository settings for your fork and enable Travis, then push
3561 your changes. Closes ticket 22636.
3564 Changes in version 0.2.9.12 - 2017-09-18
3565 Tor 0.2.9.12 backports a collection of bugfixes from later
3568 Most significantly, it includes a fix for TROVE-2017-008, a
3569 security bug that affects hidden services running with the
3570 SafeLogging option disabled. For more information, see
3571 https://trac.torproject.org/projects/tor/ticket/23490
3573 o Major features (security, backport from 0.3.0.2-alpha):
3574 - Change the algorithm used to decide DNS TTLs on client and server
3575 side, to better resist DNS-based correlation attacks like the
3576 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
3577 Feamster. Now relays only return one of two possible DNS TTL
3578 values, and clients are willing to believe DNS TTL values up to 3
3579 hours long. Closes ticket 19769.
3581 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
3582 - Fix a rare crash when sending a begin cell on a circuit whose
3583 linked directory connection had already been closed. Fixes bug
3584 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
3586 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
3587 - Fix a bug that prevented exit nodes from caching DNS records for
3588 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
3590 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
3591 - Fix a typo that had prevented TPROXY-based transparent proxying
3592 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3593 Patch from "d4fq0fQAgoJ".
3595 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3596 - Avoid an assertion failure bug affecting our implementation of
3597 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3598 handling of "0xx" differs from what we had expected. Fixes bug
3599 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3601 o Minor features (code style, backport from 0.3.1.3-alpha):
3602 - Add "Falls through" comments to our codebase, in order to silence
3603 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3604 Stieger. Closes ticket 22446.
3606 o Minor features (geoip):
3607 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3610 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
3611 - Roll over monthly accounting at the configured hour and minute,
3612 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3613 Found by Andrey Karpov with PVS-Studio.
3615 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
3616 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
3617 bugfix on 0.2.8.1-alpha.
3618 - Fix warnings when building with libscrypt and openssl scrypt support
3619 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3620 - When building with certain versions the mingw C header files, avoid
3621 float-conversion warnings when calling the C functions isfinite(),
3622 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
3624 o Minor bugfixes (compilation, backport from 0.3.1.7):
3625 - Avoid compiler warnings in the unit tests for running tor_sscanf()
3626 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3628 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3629 - Backport a fix for an "unused variable" warning that appeared
3630 in some versions of mingw. Fixes bug 22838; bugfix on
3633 o Minor bugfixes (controller, backport from 0.3.1.7):
3634 - Do not crash when receiving a HSPOST command with an empty body.
3635 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3636 - Do not crash when receiving a POSTDESCRIPTOR command with an
3637 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3639 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
3640 - Avoid Coverity build warnings related to our BUG() macro. By
3641 default, Coverity treats BUG() as the Linux kernel does: an
3642 instant abort(). We need to override that so our BUG() macro
3643 doesn't prevent Coverity from analyzing functions that use it.
3644 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3646 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3647 - Fix a memset() off the end of an array when packing cells. This
3648 bug should be harmless in practice, since the corrupted bytes are
3649 still in the same structure, and are always padding bytes,
3650 ignored, or immediately overwritten, depending on compiler
3651 behavior. Nevertheless, because the memset()'s purpose is to make
3652 sure that any other cell-handling bugs can't expose bytes to the
3653 network, we need to fix it. Fixes bug 22737; bugfix on
3654 0.2.4.11-alpha. Fixes CID 1401591.
3656 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
3657 - When setting the maximum number of connections allowed by the OS,
3658 always allow some extra file descriptors for other files. Fixes
3659 bug 22797; bugfix on 0.2.0.10-alpha.
3661 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
3662 - Avoid a sandbox failure when trying to re-bind to a socket and
3663 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
3665 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
3666 - Permit the fchmod system call, to avoid crashing on startup when
3667 starting with the seccomp2 sandbox and an unexpected set of
3668 permissions on the data directory or its contents. Fixes bug
3669 22516; bugfix on 0.2.5.4-alpha.
3671 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
3672 - Avoid a double-marked-circuit warning that could happen when we
3673 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
3676 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
3677 - Reject version numbers with non-numeric prefixes (such as +, -, or
3678 whitespace). Disallowing whitespace prevents differential version
3679 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3680 and part of 21508; bugfix on 0.0.8pre1.
3682 o Build features (backport from 0.3.1.5-alpha):
3683 - Tor's repository now includes a Travis Continuous Integration (CI)
3684 configuration file (.travis.yml). This is meant to help new
3685 developers and contributors who fork Tor to a Github repository be
3686 better able to test their changes, and understand what we expect
3687 to pass. To use this new build feature, you must fork Tor to your
3688 Github account, then go into the "Integrations" menu in the
3689 repository settings for your fork and enable Travis, then push
3690 your changes. Closes ticket 22636.
3693 Changes in version 0.3.0.11 - 2017-09-18
3694 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
3697 Most significantly, it includes a fix for TROVE-2017-008, a
3698 security bug that affects hidden services running with the
3699 SafeLogging option disabled. For more information, see
3700 https://trac.torproject.org/projects/tor/ticket/23490
3702 o Minor features (code style, backport from 0.3.1.7):
3703 - Add "Falls through" comments to our codebase, in order to silence
3704 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3705 Stieger. Closes ticket 22446.
3708 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3711 o Minor bugfixes (compilation, backport from 0.3.1.7):
3712 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
3713 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3715 o Minor bugfixes (controller, backport from 0.3.1.7):
3716 - Do not crash when receiving a HSPOST command with an empty body.
3717 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3718 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
3719 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3721 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
3722 - When setting the maximum number of connections allowed by the OS,
3723 always allow some extra file descriptors for other files. Fixes
3724 bug 22797; bugfix on 0.2.0.10-alpha.
3726 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
3727 - Remove a forgotten debugging message when an introduction point
3728 successfully establishes a hidden service prop224 circuit with
3730 - Change three other log_warn() for an introduction point to
3731 protocol warnings, because they can be failure from the network
3732 and are not relevant to the operator. Fixes bug 23078; bugfix on
3733 0.3.0.1-alpha and 0.3.0.2-alpha.
3736 Changes in version 0.3.1.7 - 2017-09-18
3737 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
3739 With the 0.3.1 series, Tor now serves and downloads directory
3740 information in more compact formats, to save on bandwidth overhead. It
3741 also contains a new padding system to resist netflow-based traffic
3742 analysis, and experimental support for building parts of Tor in Rust
3743 (though no parts of Tor are in Rust yet). There are also numerous
3744 small features, bugfixes on earlier release series, and groundwork for
3745 the hidden services revamp of 0.3.2.
3747 This release also includes a fix for TROVE-2017-008, a security bug
3748 that affects hidden services running with the SafeLogging option
3749 disabled. For more information, see
3750 https://trac.torproject.org/projects/tor/ticket/23490
3752 Per our stable release policy, we plan to support each stable release
3753 series for at least the next nine months, or for three months after
3754 the first stable release of the next series: whichever is longer. If
3755 you need a release with long-term support, we recommend that you stay
3756 with the 0.2.9 series.
3758 Below is a list of the changes since 0.3.0. For a list of all
3759 changes since 0.3.1.6-rc, see the ChangeLog file.
3762 - To build with zstd and lzma support, Tor now requires the
3763 pkg-config tool at build time.
3765 o Major bugfixes (security, hidden services, loggging):
3766 - Fix a bug where we could log uninitialized stack when a certain
3767 hidden service error occurred while SafeLogging was disabled.
3768 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
3769 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
3771 o Major features (build system, continuous integration):
3772 - Tor's repository now includes a Travis Continuous Integration (CI)
3773 configuration file (.travis.yml). This is meant to help new
3774 developers and contributors who fork Tor to a Github repository be
3775 better able to test their changes, and understand what we expect
3776 to pass. To use this new build feature, you must fork Tor to your
3777 Github account, then go into the "Integrations" menu in the
3778 repository settings for your fork and enable Travis, then push
3779 your changes. Closes ticket 22636.
3781 o Major features (directory protocol):
3782 - Tor relays and authorities can now serve clients an abbreviated
3783 version of the consensus document, containing only the changes
3784 since an older consensus document that the client holds. Clients
3785 now request these documents when available. When both client and
3786 server use this new protocol, they will use far less bandwidth (up
3787 to 94% less) to keep the client's consensus up-to-date. Implements
3788 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
3789 - Tor can now compress directory traffic with lzma or with zstd
3790 compression algorithms, which can deliver better bandwidth
3791 performance. Because lzma is computationally expensive, it's only
3792 used for documents that can be compressed once and served many
3793 times. Support for these algorithms requires that tor is built
3794 with the libzstd and/or liblzma libraries available. Implements
3795 proposal 278; closes ticket 21662.
3796 - Relays now perform the more expensive compression operations, and
3797 consensus diff generation, in worker threads. This separation
3798 avoids delaying the main thread when a new consensus arrives.
3800 o Major features (experimental):
3801 - Tor can now build modules written in Rust. To turn this on, pass
3802 the "--enable-rust" flag to the configure script. It's not time to
3803 get excited yet: currently, there is no actual Rust functionality
3804 beyond some simple glue code, and a notice at startup to tell you
3805 that Rust is running. Still, we hope that programmers and
3806 packagers will try building Tor with Rust support, so that we can
3807 find issues and solve portability problems. Closes ticket 22106.
3809 o Major features (traffic analysis resistance):
3810 - Connections between clients and relays now send a padding cell in
3811 each direction every 1.5 to 9.5 seconds (tunable via consensus
3812 parameters). This padding will not resist specialized
3813 eavesdroppers, but it should be enough to make many ISPs' routine
3814 network flow logging less useful in traffic analysis against
3817 Padding is negotiated using Tor's link protocol, so both relays
3818 and clients must upgrade for this to take effect. Clients may
3819 still send padding despite the relay's version by setting
3820 ConnectionPadding 1 in torrc, and may disable padding by setting
3821 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
3822 users with the torrc option ReducedConnectionPadding. Implements
3823 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
3824 - Relays will publish 24 hour totals of padding and non-padding cell
3825 counts to their extra-info descriptors, unless PaddingStatistics 0
3826 is set in torrc. These 24 hour totals are also rounded to
3829 o Major bugfixes (hidden service, relay, security):
3830 - Fix a remotely triggerable assertion failure when a hidden service
3831 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
3832 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
3833 - Fix a remotely triggerable assertion failure caused by receiving a
3834 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3835 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3838 o Major bugfixes (path selection, security):
3839 - When choosing which guard to use for a circuit, avoid the exit's
3840 family along with the exit itself. Previously, the new guard
3841 selection logic avoided the exit, but did not consider its family.
3842 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
3843 006 and CVE-2017-0377.
3845 o Major bugfixes (connection usage):
3846 - We use NETINFO cells to try to determine if both relays involved
3847 in a connection will agree on the canonical status of that
3848 connection. We prefer the connections where this is the case for
3849 extend cells, and try to close connections where relays disagree
3850 on their canonical status early. Also, we now prefer the oldest
3851 valid connection for extend cells. These two changes should reduce
3852 the number of long-term connections that are kept open between
3853 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
3854 - Relays now log hourly statistics (look for
3855 "channel_check_for_duplicates" lines) on the total number of
3856 connections to other relays. If the number of connections per
3857 relay is unexpectedly large, this log message is at notice level.
3858 Otherwise it is at info.
3860 o Major bugfixes (entry guards):
3861 - When starting with an old consensus, do not add new entry guards
3862 unless the consensus is "reasonably live" (under 1 day old). Fixes
3863 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
3864 - Don't block bootstrapping when a primary bridge is offline and we
3865 can't get its descriptor. Fixes bug 22325; fixes one case of bug
3866 21969; bugfix on 0.3.0.3-alpha.
3868 o Major bugfixes (linux TPROXY support):
3869 - Fix a typo that had prevented TPROXY-based transparent proxying
3870 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3871 Patch from "d4fq0fQAgoJ".
3873 o Major bugfixes (openbsd, denial-of-service):
3874 - Avoid an assertion failure bug affecting our implementation of
3875 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3876 handling of "0xx" differs from what we had expected. Fixes bug
3877 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3879 o Major bugfixes (relay, link handshake):
3880 - When performing the v3 link handshake on a TLS connection, report
3881 that we have the x509 certificate that we actually used on that
3882 connection, even if we have changed certificates since that
3883 connection was first opened. Previously, we would claim to have
3884 used our most recent x509 link certificate, which would sometimes
3885 make the link handshake fail. Fixes one case of bug 22460; bugfix
3888 o Major bugfixes (relays, key management):
3889 - Regenerate link and authentication certificates whenever the key
3890 that signs them changes; also, regenerate link certificates
3891 whenever the signed key changes. Previously, these processes were
3892 only weakly coupled, and we relays could (for minutes to hours)
3893 wind up with an inconsistent set of keys and certificates, which
3894 other relays would not accept. Fixes two cases of bug 22460;
3895 bugfix on 0.3.0.1-alpha.
3896 - When sending an Ed25519 signing->link certificate in a CERTS cell,
3897 send the certificate that matches the x509 certificate that we
3898 used on the TLS connection. Previously, there was a race condition
3899 if the TLS context rotated after we began the TLS handshake but
3900 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
3903 o Minor features (security, windows):
3904 - Enable a couple of pieces of Windows hardening: one
3905 (HeapEnableTerminationOnCorruption) that has been on-by-default
3906 since Windows 8, and unavailable before Windows 7; and one
3907 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
3908 affect us, but shouldn't do any harm. Closes ticket 21953.
3910 o Minor features (bridge authority):
3911 - Add "fingerprint" lines to the networkstatus-bridges file produced
3912 by bridge authorities. Closes ticket 22207.
3914 o Minor features (code style):
3915 - Add "Falls through" comments to our codebase, in order to silence
3916 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3917 Stieger. Closes ticket 22446.
3919 o Minor features (config options):
3920 - Allow "%include" directives in torrc configuration files. These
3921 directives import the settings from other files, or from all the
3922 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
3923 - Make SAVECONF return an error when overwriting a torrc that has
3924 includes. Using SAVECONF with the FORCE option will allow it to
3925 overwrite torrc even if includes are used. Related to ticket 1922.
3926 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
3927 will work without the FORCE option. Related to ticket 1922.
3929 o Minor features (controller):
3930 - Warn the first time that a controller requests data in the long-
3931 deprecated 'GETINFO network-status' format. Closes ticket 21703.
3933 o Minor features (defaults):
3934 - The default value for UseCreateFast is now 0: clients which
3935 haven't yet received a consensus document will now use a proper
3936 ntor handshake to talk to their directory servers whenever they
3937 can. Closes ticket 21407.
3938 - Onion key rotation and expiry intervals are now defined as a
3939 network consensus parameter, per proposal 274. The default
3940 lifetime of an onion key is increased from 7 to 28 days. Old onion
3941 keys will expire after 7 days by default. This change will make
3942 consensus diffs much smaller, and save significant bandwidth.
3943 Closes ticket 21641.
3945 o Minor features (defensive programming):
3946 - Create a pair of consensus parameters, nf_pad_tor2web and
3947 nf_pad_single_onion, to disable netflow padding in the consensus
3948 for non-anonymous connections in case the overhead is high. Closes
3951 o Minor features (diagnostic):
3952 - Add a stack trace to the bug warnings that can be logged when
3953 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
3954 attempt for bug 23105.
3955 - Add logging messages to try to diagnose a rare bug that seems to
3956 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
3957 think this is happening because of incorrect system clocks, but
3958 we'd like to know for certain. Diagnostic for bug 22466.
3959 - Avoid an assertion failure, and log a better error message, when
3960 unable to remove a file from the consensus cache on Windows.
3961 Attempts to mitigate and diagnose bug 22752.
3963 o Minor features (directory authority):
3964 - Improve the message that authorities report to relays that present
3965 RSA/Ed25519 keypairs that conflict with previously pinned keys.
3966 Closes ticket 22348.
3968 o Minor features (directory cache, consensus diff):
3969 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
3970 operators with low-resource environments to adjust the number of
3971 consensuses they'll store and generate diffs from. Most cache
3972 operators should leave it unchanged. Helps to work around
3975 o Minor features (fallback directory list):
3976 - Update the fallback directory mirror whitelist and blacklist based
3977 on operator emails. Closes task 21121.
3978 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3979 December 2016 (of which ~126 were still functional) with a list of
3980 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3981 2017. Resolves ticket 21564.
3983 o Minor features (geoip):
3984 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3987 o Minor features (hidden services, logging):
3988 - Log a message when a hidden service descriptor has fewer
3989 introduction points than specified in
3990 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
3991 - Log a message when a hidden service reaches its introduction point
3992 circuit limit, and when that limit is reset. Follow up to ticket
3993 21594; closes ticket 21622.
3994 - Warn user if multiple entries in EntryNodes and at least one
3995 HiddenService are used together. Pinning EntryNodes along with a
3996 hidden service can be possibly harmful; for instance see ticket
3997 14917 or 21155. Closes ticket 21155.
3999 o Minor features (linux seccomp2 sandbox):
4000 - We now have a document storage backend compatible with the Linux
4001 seccomp2 sandbox. This backend is used for consensus documents and
4002 diffs between them; in the long term, we'd like to use it for
4003 unparseable directory material too. Closes ticket 21645
4004 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
4005 from 1MB to 16MB. This was necessary with the glibc allocator in
4006 order to allow worker threads to allocate more memory -- which in
4007 turn is necessary because of our new use of worker threads for
4008 compression. Closes ticket 22096.
4010 o Minor features (logging):
4011 - Log files are no longer created world-readable by default.
4012 (Previously, most distributors would store the logs in a non-
4013 world-readable location to prevent inappropriate access. This
4014 change is an extra precaution.) Closes ticket 21729; patch
4017 o Minor features (performance):
4018 - Our Keccak (SHA-3) implementation now accesses memory more
4019 efficiently, especially on little-endian systems. Closes
4021 - Add an O(1) implementation of channel_find_by_global_id(), to
4022 speed some controller functions.
4024 o Minor features (relay, configuration):
4025 - The MyFamily option may now be repeated as many times as desired,
4026 for relays that want to configure large families. Closes ticket
4027 4998; patch by Daniel Pinto.
4029 o Minor features (relay, performance):
4030 - Always start relays with at least two worker threads, to prevent
4031 priority inversion on slow tasks. Part of the fix for bug 22883.
4032 - Allow background work to be queued with different priorities, so
4033 that a big pile of slow low-priority jobs will not starve out
4034 higher priority jobs. This lays the groundwork for a fix for
4037 o Minor features (safety):
4038 - Add an explicit check to extrainfo_parse_entry_from_string() for
4039 NULL inputs. We don't believe this can actually happen, but it may
4040 help silence a warning from the Clang analyzer. Closes
4043 o Minor features (testing):
4044 - Add more tests for compression backend initialization. Closes
4046 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
4047 When Tor is compiled with this option, we disable a number of
4048 redundant memory-safety failsafes that are intended to stop bugs
4049 from becoming security issues. This makes it easier to hunt for
4050 bugs that would be security issues without the failsafes turned
4051 on. Closes ticket 21439.
4052 - Add a general event-tracing instrumentation support to Tor. This
4053 subsystem will enable developers and researchers to add fine-
4054 grained instrumentation to their Tor instances, for use when
4055 examining Tor network performance issues. There are no trace
4056 events yet, and event-tracing is off by default unless enabled at
4057 compile time. Implements ticket 13802.
4058 - Improve our version parsing tests: add tests for typical version
4059 components, add tests for invalid versions, including numeric
4060 range and non-numeric prefixes. Unit tests 21278, 21450, and
4061 21507. Partially implements 21470.
4063 o Minor bugfixes (bandwidth accounting):
4064 - Roll over monthly accounting at the configured hour and minute,
4065 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
4066 Found by Andrey Karpov with PVS-Studio.
4068 o Minor bugfixes (code correctness):
4069 - Accurately identify client connections by their lack of peer
4070 authentication. This means that we bail out earlier if asked to
4071 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
4074 o Minor bugfixes (compilation warnings):
4075 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
4076 22915; bugfix on 0.2.8.1-alpha.
4077 - Fix warnings when building with libscrypt and openssl scrypt
4078 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
4079 - When building with certain versions of the mingw C header files,
4080 avoid float-conversion warnings when calling the C functions
4081 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
4084 o Minor bugfixes (compilation):
4085 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
4086 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
4088 o Minor bugfixes (compression):
4089 - When spooling compressed data to an output buffer, don't try to
4090 spool more data when there is no more data to spool and we are not
4091 trying to flush the input. Previously, we would sometimes launch
4092 compression requests with nothing to do, which interferes with our
4093 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
4095 o Minor bugfixes (configuration):
4096 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
4097 bug 22252; bugfix on 0.2.9.3-alpha.
4099 o Minor bugfixes (connection lifespan):
4100 - Allow more control over how long TLS connections are kept open:
4101 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
4102 single option called CircuitsAvailableTimeout. Also, allow the
4103 consensus to control the default values for both this preference
4104 and the lifespan of relay-to-relay connections. Fixes bug 17592;
4105 bugfix on 0.2.5.5-alpha.
4106 - Increase the initial circuit build timeout testing frequency, to
4107 help ensure that ReducedConnectionPadding clients finish learning
4108 a timeout before their orconn would expire. The initial testing
4109 rate was set back in the days of TAP and before the Tor Browser
4110 updater, when we had to be much more careful about new clients
4111 making lots of circuits. With this change, a circuit build timeout
4112 is learned in about 15-20 minutes, instead of 100-120 minutes.
4114 o Minor bugfixes (controller):
4115 - Do not crash when receiving a HSPOST command with an empty body.
4116 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
4117 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
4118 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
4119 - GETINFO onions/current and onions/detached no longer respond with
4120 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
4121 - Trigger HS descriptor events on the control port when the client
4122 fails to pick a hidden service directory for a hidden service.
4123 This can happen if all the hidden service directories are in
4124 ExcludeNodes, or they have all been queried within the last 15
4125 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
4127 o Minor bugfixes (correctness):
4128 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4129 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4131 o Minor bugfixes (coverity build support):
4132 - Avoid Coverity build warnings related to our BUG() macro. By
4133 default, Coverity treats BUG() as the Linux kernel does: an
4134 instant abort(). We need to override that so our BUG() macro
4135 doesn't prevent Coverity from analyzing functions that use it.
4136 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
4138 o Minor bugfixes (defensive programming):
4139 - Detect and break out of infinite loops in our compression code. We
4140 don't think that any such loops exist now, but it's best to be
4141 safe. Closes ticket 22672.
4142 - Fix a memset() off the end of an array when packing cells. This
4143 bug should be harmless in practice, since the corrupted bytes are
4144 still in the same structure, and are always padding bytes,
4145 ignored, or immediately overwritten, depending on compiler
4146 behavior. Nevertheless, because the memset()'s purpose is to make
4147 sure that any other cell-handling bugs can't expose bytes to the
4148 network, we need to fix it. Fixes bug 22737; bugfix on
4149 0.2.4.11-alpha. Fixes CID 1401591.
4151 o Minor bugfixes (directory authority):
4152 - When a directory authority rejects a descriptor or extrainfo with
4153 a given digest, mark that digest as undownloadable, so that we do
4154 not attempt to download it again over and over. We previously
4155 tried to avoid downloading such descriptors by other means, but we
4156 didn't notice if we accidentally downloaded one anyway. This
4157 behavior became problematic in 0.2.7.2-alpha, when authorities
4158 began pinning Ed25519 keys. Fixes bug 22349; bugfix
4160 - When rejecting a router descriptor for running an obsolete version
4161 of Tor without ntor support, warn about the obsolete tor version,
4162 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
4163 - Prevent the shared randomness subsystem from asserting when
4164 initialized by a bridge authority with an incomplete configuration
4165 file. Fixes bug 21586; bugfix on 0.2.9.8.
4167 o Minor bugfixes (error reporting, windows):
4168 - When formatting Windows error messages, use the English format to
4169 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
4172 o Minor bugfixes (exit-side DNS):
4173 - Fix an untriggerable assertion that checked the output of a
4174 libevent DNS error, so that the assertion actually behaves as
4175 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
4176 Karpov using PVS-Studio.
4178 o Minor bugfixes (fallback directories):
4179 - Make the usage example in updateFallbackDirs.py actually work, and
4180 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
4181 - Decrease the guard flag average required to be a fallback. This
4182 allows us to keep relays that have their guard flag removed when
4183 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
4184 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
4185 bugfix on 0.2.8.1-alpha.
4186 - Make sure fallback directory mirrors have the same address, port,
4187 and relay identity key for at least 30 days before they are
4188 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
4190 o Minor bugfixes (file limits, osx):
4191 - When setting the maximum number of connections allowed by the OS,
4192 always allow some extra file descriptors for other files. Fixes
4193 bug 22797; bugfix on 0.2.0.10-alpha.
4195 o Minor bugfixes (hidden services):
4196 - Increase the number of circuits that a service is allowed to
4197 open over a specific period of time. The value was lower than it
4198 should be (8 vs 12) in the normal case of 3 introduction points.
4199 Fixes bug 22159; bugfix on 0.3.0.5-rc.
4200 - Fix a BUG warning during HSv3 descriptor decoding that could be
4201 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
4202 on 0.3.0.1-alpha. Bug found by "haxxpop".
4203 - Stop printing a cryptic warning when a hidden service gets a
4204 request to connect to a virtual port that it hasn't configured.
4205 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
4206 - Simplify hidden service descriptor creation by using an existing
4207 flag to check if an introduction point is established. Fixes bug
4208 21599; bugfix on 0.2.7.2-alpha.
4210 o Minor bugfixes (link handshake):
4211 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
4212 months, and regenerate it when it is within one month of expiring.
4213 Previously, we had generated this certificate at startup with a
4214 ten-year lifetime, but that could lead to weird behavior when Tor
4215 was started with a grossly inaccurate clock. Mitigates bug 22466;
4216 mitigation on 0.3.0.1-alpha.
4218 o Minor bugfixes (linux seccomp2 sandbox):
4219 - Avoid a sandbox failure when trying to re-bind to a socket and
4220 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
4221 - Permit the fchmod system call, to avoid crashing on startup when
4222 starting with the seccomp2 sandbox and an unexpected set of
4223 permissions on the data directory or its contents. Fixes bug
4224 22516; bugfix on 0.2.5.4-alpha.
4226 o Minor bugfixes (logging):
4227 - When decompressing, do not warn if we fail to decompress using a
4228 compression method that we merely guessed. Fixes part of bug
4229 22670; bugfix on 0.1.1.14-alpha.
4230 - When decompressing, treat mismatch between content-encoding and
4231 actual compression type as a protocol warning. Fixes part of bug
4232 22670; bugfix on 0.1.1.9-alpha.
4233 - Downgrade "assigned_to_cpuworker failed" message to info-level
4234 severity. In every case that can reach it, either a better warning
4235 has already been logged, or no warning is warranted. Fixes bug
4236 22356; bugfix on 0.2.6.3-alpha.
4237 - Log a better message when a directory authority replies to an
4238 upload with an unexpected status code. Fixes bug 11121; bugfix
4240 - Downgrade a log statement about unexpected relay cells from "bug"
4241 to "protocol warning", because there is at least one use case
4242 where it can be triggered by a buggy tor implementation. Fixes bug
4243 21293; bugfix on 0.1.1.14-alpha.
4245 o Minor bugfixes (logging, relay):
4246 - Remove a forgotten debugging message when an introduction point
4247 successfully establishes a hidden service prop224 circuit with
4249 - Change three other log_warn() for an introduction point to
4250 protocol warnings, because they can be failure from the network
4251 and are not relevant to the operator. Fixes bug 23078; bugfix on
4252 0.3.0.1-alpha and 0.3.0.2-alpha.
4254 o Minor bugfixes (relay):
4255 - Inform the geoip and rephist modules about all requests, even on
4256 relays that are only fetching microdescriptors. Fixes a bug
4257 related to 21585; bugfix on 0.3.0.1-alpha.
4259 o Minor bugfixes (memory leaks):
4260 - Fix a small memory leak at exit from the backtrace handler code.
4261 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
4262 - When directory authorities reject a router descriptor due to
4263 keypinning, free the router descriptor rather than leaking the
4264 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4265 - Fix a small memory leak when validating a configuration that uses
4266 two or more AF_UNIX sockets for the same port type. Fixes bug
4267 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
4269 o Minor bugfixes (process behavior):
4270 - When exiting because of an error, always exit with a nonzero exit
4271 status. Previously, we would fail to report an error in our exit
4272 status in cases related to __OwningControllerProcess failure,
4273 lockfile contention, and Ed25519 key initialization. Fixes bug
4274 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
4275 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
4278 o Minor bugfixes (robustness, error handling):
4279 - Improve our handling of the cases where OpenSSL encounters a
4280 memory error while encoding keys and certificates. We haven't
4281 observed these errors in the wild, but if they do happen, we now
4282 detect and respond better. Fixes bug 19418; bugfix on all versions
4283 of Tor. Reported by Guido Vranken.
4285 o Minor bugfixes (testing):
4286 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4287 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4288 - Use unbuffered I/O for utility functions around the
4289 process_handle_t type. This fixes unit test failures reported on
4290 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
4291 - Make display of captured unit test log messages consistent. Fixes
4292 bug 21510; bugfix on 0.2.9.3-alpha.
4293 - Make test-network.sh always call chutney's test-network.sh.
4294 Previously, this only worked on systems which had bash installed,
4295 due to some bash-specific code in the script. Fixes bug 19699;
4296 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
4297 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
4298 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
4299 - The unit tests now pass on systems where localhost is misconfigured
4300 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
4303 o Minor bugfixes (voting consistency):
4304 - Reject version numbers with non-numeric prefixes (such as +, -, or
4305 whitespace). Disallowing whitespace prevents differential version
4306 parsing between POSIX-based and Windows platforms. Fixes bug 21507
4307 and part of 21508; bugfix on 0.0.8pre1.
4309 o Minor bugfixes (Windows service):
4310 - When running as a Windows service, set the ID of the main thread
4311 correctly. Failure to do so made us fail to send log messages to
4312 the controller in 0.2.1.16-rc, slowed down controller event
4313 delivery in 0.2.7.3-rc and later, and crash with an assertion
4314 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
4315 Patch and diagnosis from "Vort".
4317 o Minor bugfixes (windows, relay):
4318 - Resolve "Failure from drain_fd: No error" warnings on Windows
4319 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
4321 o Code simplification and refactoring:
4322 - Break up the 630-line function connection_dir_client_reached_eof()
4323 into a dozen smaller functions. This change should help
4324 maintainability and readability of the client directory code.
4325 - Isolate our use of the openssl headers so that they are only
4326 included from our crypto wrapper modules, and from tests that
4327 examine those modules' internals. Closes ticket 21841.
4328 - Simplify our API to launch directory requests, making it more
4329 extensible and less error-prone. Now it's easier to add extra
4330 headers to directory requests. Closes ticket 21646.
4331 - Our base64 decoding functions no longer overestimate the output
4332 space that they need when parsing unpadded inputs. Closes
4334 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
4335 Resolves ticket 22213.
4336 - The logic that directory caches use to spool request to clients,
4337 serving them one part at a time so as not to allocate too much
4338 memory, has been refactored for consistency. Previously there was
4339 a separate spooling implementation per type of spoolable data. Now
4340 there is one common spooling implementation, with extensible data
4341 types. Closes ticket 21651.
4342 - Tor's compression module now supports multiple backends. Part of
4343 the implementation for proposal 278; closes ticket 21663.
4346 - Add a manpage description for the key-pinning-journal file. Closes
4348 - Correctly note that bandwidth accounting values are stored in the
4349 state file, and the bw_accounting file is now obsolete. Closes
4351 - Document more of the files in the Tor data directory, including
4352 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
4353 approved-routers, sr-random, and diff-cache. Found while fixing
4355 - Clarify the manpage for the (deprecated) torify script. Closes
4357 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
4358 Closes ticket 21873.
4359 - Correct documentation about the default DataDirectory value.
4360 Closes ticket 21151.
4361 - Document the default behavior of NumEntryGuards and
4362 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
4364 - Document key=value pluggable transport arguments for Bridge lines
4365 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
4366 - Note that bandwidth-limiting options don't affect TCP headers or
4367 DNS. Closes ticket 17170.
4369 o Removed features (configuration options, all in ticket 22060):
4370 - These configuration options are now marked Obsolete, and no longer
4371 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
4372 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
4373 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
4374 in 0.2.9.2-alpha and have now been removed. The previous default
4375 behavior is now always chosen; the previous (less secure) non-
4376 default behavior is now unavailable.
4377 - CloseHSClientCircuitsImmediatelyOnTimeout and
4378 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
4379 0.2.9.2-alpha and now have been removed. HS circuits never close
4380 on circuit build timeout; they have a longer timeout period.
4381 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
4382 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
4383 (and others) to configure listen-only and advertise-only addresses.
4385 o Removed features (tools):
4386 - We've removed the tor-checkkey tool from src/tools. Long ago, we
4387 used it to help people detect RSA keys that were generated by
4388 versions of Debian affected by CVE-2008-0166. But those keys have
4389 been out of circulation for ages, and this tool is no longer
4390 required. Closes ticket 21842.
4393 Changes in version 0.3.0.10 - 2017-08-02
4394 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
4395 from the current Tor alpha series. OpenBSD users and TPROXY users
4396 should upgrade; others are probably okay sticking with 0.3.0.9.
4398 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
4399 - Tor's repository now includes a Travis Continuous Integration (CI)
4400 configuration file (.travis.yml). This is meant to help new
4401 developers and contributors who fork Tor to a Github repository be
4402 better able to test their changes, and understand what we expect
4403 to pass. To use this new build feature, you must fork Tor to your
4404 Github account, then go into the "Integrations" menu in the
4405 repository settings for your fork and enable Travis, then push
4406 your changes. Closes ticket 22636.
4408 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
4409 - Fix a typo that had prevented TPROXY-based transparent proxying
4410 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
4411 Patch from "d4fq0fQAgoJ".
4413 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
4414 - Avoid an assertion failure bug affecting our implementation of
4415 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
4416 handling of "0xbar" differs from what we had expected. Fixes bug
4417 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
4419 o Minor features (backport from 0.3.1.5-alpha):
4420 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
4423 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
4424 - Roll over monthly accounting at the configured hour and minute,
4425 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
4426 Found by Andrey Karpov with PVS-Studio.
4428 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
4429 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
4430 bugfix on 0.2.8.1-alpha.
4431 - Fix warnings when building with libscrypt and openssl scrypt
4432 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
4433 - When building with certain versions of the mingw C header files,
4434 avoid float-conversion warnings when calling the C functions
4435 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
4438 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
4439 - Backport a fix for an "unused variable" warning that appeared
4440 in some versions of mingw. Fixes bug 22838; bugfix on
4443 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
4444 - Avoid Coverity build warnings related to our BUG() macro. By
4445 default, Coverity treats BUG() as the Linux kernel does: an
4446 instant abort(). We need to override that so our BUG() macro
4447 doesn't prevent Coverity from analyzing functions that use it.
4448 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
4450 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
4451 - When rejecting a router descriptor for running an obsolete version
4452 of Tor without ntor support, warn about the obsolete tor version,
4453 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
4455 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
4456 - Avoid a sandbox failure when trying to re-bind to a socket and
4457 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
4459 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
4460 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
4461 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
4464 Changes in version 0.3.0.9 - 2017-06-29
4465 Tor 0.3.0.9 fixes a path selection bug that would allow a client
4466 to use a guard that was in the same network family as a chosen exit
4467 relay. This is a security regression; all clients running earlier
4468 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
4471 This release also backports several other bugfixes from the 0.3.1.x
4474 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
4475 - When choosing which guard to use for a circuit, avoid the exit's
4476 family along with the exit itself. Previously, the new guard
4477 selection logic avoided the exit, but did not consider its family.
4478 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
4479 006 and CVE-2017-0377.
4481 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
4482 - Don't block bootstrapping when a primary bridge is offline and we
4483 can't get its descriptor. Fixes bug 22325; fixes one case of bug
4484 21969; bugfix on 0.3.0.3-alpha.
4486 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
4487 - When starting with an old consensus, do not add new entry guards
4488 unless the consensus is "reasonably live" (under 1 day old). Fixes
4489 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
4491 o Minor features (geoip):
4492 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
4495 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
4496 - Reject version numbers with non-numeric prefixes (such as +, -, or
4497 whitespace). Disallowing whitespace prevents differential version
4498 parsing between POSIX-based and Windows platforms. Fixes bug 21507
4499 and part of 21508; bugfix on 0.0.8pre1.
4501 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
4502 - Permit the fchmod system call, to avoid crashing on startup when
4503 starting with the seccomp2 sandbox and an unexpected set of
4504 permissions on the data directory or its contents. Fixes bug
4505 22516; bugfix on 0.2.5.4-alpha.
4507 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
4508 - Fix a memset() off the end of an array when packing cells. This
4509 bug should be harmless in practice, since the corrupted bytes are
4510 still in the same structure, and are always padding bytes,
4511 ignored, or immediately overwritten, depending on compiler
4512 behavior. Nevertheless, because the memset()'s purpose is to make
4513 sure that any other cell-handling bugs can't expose bytes to the
4514 network, we need to fix it. Fixes bug 22737; bugfix on
4515 0.2.4.11-alpha. Fixes CID 1401591.
4518 Changes in version 0.3.0.8 - 2017-06-08
4519 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
4520 remotely crash a hidden service with an assertion failure. Anyone
4521 running a hidden service should upgrade to this version, or to some
4522 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
4524 Tor 0.3.0.8 also includes fixes for several key management bugs
4525 that sometimes made relays unreliable, as well as several other
4526 bugfixes described below.
4528 o Major bugfixes (hidden service, relay, security, backport
4529 from 0.3.1.3-alpha):
4530 - Fix a remotely triggerable assertion failure when a hidden service
4531 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
4532 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
4533 - Fix a remotely triggerable assertion failure caused by receiving a
4534 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4535 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4538 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
4539 - When performing the v3 link handshake on a TLS connection, report
4540 that we have the x509 certificate that we actually used on that
4541 connection, even if we have changed certificates since that
4542 connection was first opened. Previously, we would claim to have
4543 used our most recent x509 link certificate, which would sometimes
4544 make the link handshake fail. Fixes one case of bug 22460; bugfix
4547 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
4548 - Regenerate link and authentication certificates whenever the key
4549 that signs them changes; also, regenerate link certificates
4550 whenever the signed key changes. Previously, these processes were
4551 only weakly coupled, and we relays could (for minutes to hours)
4552 wind up with an inconsistent set of keys and certificates, which
4553 other relays would not accept. Fixes two cases of bug 22460;
4554 bugfix on 0.3.0.1-alpha.
4555 - When sending an Ed25519 signing->link certificate in a CERTS cell,
4556 send the certificate that matches the x509 certificate that we
4557 used on the TLS connection. Previously, there was a race condition
4558 if the TLS context rotated after we began the TLS handshake but
4559 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
4562 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
4563 - Stop rejecting v3 hidden service descriptors because their size
4564 did not match an old padding rule. Fixes bug 22447; bugfix on
4567 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4568 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4569 December 2016 (of which ~126 were still functional) with a list of
4570 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4571 2017. Resolves ticket 21564.
4573 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
4574 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
4575 bug 22252; bugfix on 0.2.9.3-alpha.
4577 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
4578 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4579 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4581 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
4582 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
4583 months, and regenerate it when it is within one month of expiring.
4584 Previously, we had generated this certificate at startup with a
4585 ten-year lifetime, but that could lead to weird behavior when Tor
4586 was started with a grossly inaccurate clock. Mitigates bug 22466;
4587 mitigation on 0.3.0.1-alpha.
4589 o Minor bugfixes (memory leak, directory authority, backport from
4591 - When directory authorities reject a router descriptor due to
4592 keypinning, free the router descriptor rather than leaking the
4593 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4596 Changes in version 0.2.9.11 - 2017-06-08
4597 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
4598 remotely crash a hidden service with an assertion failure. Anyone
4599 running a hidden service should upgrade to this version, or to some
4600 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4601 are not affected by TROVE-2017-004.)
4603 Tor 0.2.9.11 also backports fixes for several key management bugs
4604 that sometimes made relays unreliable, as well as several other
4605 bugfixes described below.
4607 o Major bugfixes (hidden service, relay, security, backport
4608 from 0.3.1.3-alpha):
4609 - Fix a remotely triggerable assertion failure caused by receiving a
4610 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4611 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4614 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
4615 - When performing the v3 link handshake on a TLS connection, report
4616 that we have the x509 certificate that we actually used on that
4617 connection, even if we have changed certificates since that
4618 connection was first opened. Previously, we would claim to have
4619 used our most recent x509 link certificate, which would sometimes
4620 make the link handshake fail. Fixes one case of bug 22460; bugfix
4623 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4624 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4625 December 2016 (of which ~126 were still functional) with a list of
4626 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4627 2017. Resolves ticket 21564.
4629 o Minor features (future-proofing, backport from 0.3.0.7):
4630 - Tor no longer refuses to download microdescriptors or descriptors if
4631 they are listed as "published in the future". This change will
4632 eventually allow us to stop listing meaningful "published" dates
4633 in microdescriptor consensuses, and thereby allow us to reduce the
4634 resources required to download consensus diffs by over 50%.
4635 Implements part of ticket 21642; implements part of proposal 275.
4637 o Minor features (directory authorities, backport from 0.3.0.4-rc)
4638 - Directory authorities now reject relays running versions
4639 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
4640 suffer from bug 20499 and don't keep their consensus cache
4641 up-to-date. Resolves ticket 20509.
4643 o Minor features (geoip):
4644 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4647 o Minor bugfixes (control port, backport from 0.3.0.6):
4648 - The GETINFO extra-info/digest/<digest> command was broken because
4649 of a wrong base16 decode return value check, introduced when
4650 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
4652 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
4653 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4654 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4656 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
4657 - The getpid() system call is now permitted under the Linux seccomp2
4658 sandbox, to avoid crashing with versions of OpenSSL (and other
4659 libraries) that attempt to learn the process's PID by using the
4660 syscall rather than the VDSO code. Fixes bug 21943; bugfix
4663 o Minor bugfixes (memory leak, directory authority, backport
4664 from 0.3.1.2-alpha):
4665 - When directory authorities reject a router descriptor due to
4666 keypinning, free the router descriptor rather than leaking the
4667 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4669 Changes in version 0.2.8.14 - 2017-06-08
4670 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4671 remotely crash a hidden service with an assertion failure. Anyone
4672 running a hidden service should upgrade to this version, or to some
4673 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4674 are not affected by TROVE-2017-004.)
4676 o Major bugfixes (hidden service, relay, security):
4677 - Fix a remotely triggerable assertion failure caused by receiving a
4678 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4679 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4682 o Minor features (geoip):
4683 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4686 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4687 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4688 December 2016 (of which ~126 were still functional) with a list of
4689 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4690 2017. Resolves ticket 21564.
4692 o Minor bugfixes (correctness):
4693 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4694 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4696 Changes in version 0.2.7.8 - 2017-06-08
4697 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4698 remotely crash a hidden service with an assertion failure. Anyone
4699 running a hidden service should upgrade to this version, or to some
4700 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4701 are not affected by TROVE-2017-004.)
4703 o Major bugfixes (hidden service, relay, security):
4704 - Fix a remotely triggerable assertion failure caused by receiving a
4705 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4706 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4709 o Minor features (geoip):
4710 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4713 o Minor bugfixes (correctness):
4714 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4715 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4718 Changes in version 0.2.6.12 - 2017-06-08
4719 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
4720 remotely crash a hidden service with an assertion failure. Anyone
4721 running a hidden service should upgrade to this version, or to some
4722 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4723 are not affected by TROVE-2017-004.)
4725 o Major bugfixes (hidden service, relay, security):
4726 - Fix a remotely triggerable assertion failure caused by receiving a
4727 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4728 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4731 o Minor features (geoip):
4732 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4735 o Minor bugfixes (correctness):
4736 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4737 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4739 Changes in version 0.2.5.14 - 2017-06-08
4740 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
4741 remotely crash a hidden service with an assertion failure. Anyone
4742 running a hidden service should upgrade to this version, or to some
4743 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4744 are not affected by TROVE-2017-004.)
4746 o Major bugfixes (hidden service, relay, security):
4747 - Fix a remotely triggerable assertion failure caused by receiving a
4748 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4749 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4752 o Minor features (geoip):
4753 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4756 o Minor bugfixes (correctness):
4757 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4758 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4760 Changes in version 0.2.4.29 - 2017-06-08
4761 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
4762 remotely crash a hidden service with an assertion failure. Anyone
4763 running a hidden service should upgrade to this version, or to some
4764 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4765 are not affected by TROVE-2017-004.)
4767 o Major bugfixes (hidden service, relay, security):
4768 - Fix a remotely triggerable assertion failure caused by receiving a
4769 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4770 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4773 o Minor features (geoip):
4774 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4777 o Minor bugfixes (correctness):
4778 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4779 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4782 Changes in version 0.3.0.7 - 2017-05-15
4783 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
4784 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
4785 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
4786 clients are not affected.
4788 o Major bugfixes (hidden service directory, security):
4789 - Fix an assertion failure in the hidden service directory code, which
4790 could be used by an attacker to remotely cause a Tor relay process to
4791 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
4792 should upgrade. This security issue is tracked as TROVE-2017-002.
4793 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
4796 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4799 o Minor features (future-proofing):
4800 - Tor no longer refuses to download microdescriptors or descriptors
4801 if they are listed as "published in the future". This change will
4802 eventually allow us to stop listing meaningful "published" dates
4803 in microdescriptor consensuses, and thereby allow us to reduce the
4804 resources required to download consensus diffs by over 50%.
4805 Implements part of ticket 21642; implements part of proposal 275.
4807 o Minor bugfixes (Linux seccomp2 sandbox):
4808 - The getpid() system call is now permitted under the Linux seccomp2
4809 sandbox, to avoid crashing with versions of OpenSSL (and other
4810 libraries) that attempt to learn the process's PID by using the
4811 syscall rather than the VDSO code. Fixes bug 21943; bugfix
4815 Changes in version 0.3.0.6 - 2017-04-26
4816 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
4818 With the 0.3.0 series, clients and relays now use Ed25519 keys to
4819 authenticate their link connections to relays, rather than the old
4820 RSA1024 keys that they used before. (Circuit crypto has been
4821 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
4822 the guard selection and replacement algorithm to behave more robustly
4823 in the presence of unreliable networks, and to resist guard-
4826 This series also includes numerous other small features and bugfixes,
4827 along with more groundwork for the upcoming hidden-services revamp.
4829 Per our stable release policy, we plan to support the Tor 0.3.0
4830 release series for at least the next nine months, or for three months
4831 after the first stable release of the 0.3.1 series: whichever is
4832 longer. If you need a release with long-term support, we recommend
4833 that you stay with the 0.2.9 series.
4835 Below are the changes since 0.2.9.10. For a list of only the changes
4836 since 0.3.0.5-rc, see the ChangeLog file.
4838 o Major features (directory authority, security):
4839 - The default for AuthDirPinKeys is now 1: directory authorities
4840 will reject relays where the RSA identity key matches a previously
4841 seen value, but the Ed25519 key has changed. Closes ticket 18319.
4843 o Major features (guard selection algorithm):
4844 - Tor's guard selection algorithm has been redesigned from the
4845 ground up, to better support unreliable networks and restrictive
4846 sets of entry nodes, and to better resist guard-capture attacks by
4847 hostile local networks. Implements proposal 271; closes
4850 o Major features (next-generation hidden services):
4851 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
4852 prop224 aka "Next Generation Hidden Services". Service and clients
4853 don't use this functionality yet. Closes ticket 19043. Based on
4854 initial code by Alec Heifetz.
4855 - Relays now support the HSDir version 3 protocol, so that they can
4856 can store and serve v3 descriptors. This is part of the next-
4857 generation onion service work detailed in proposal 224. Closes
4860 o Major features (protocol, ed25519 identity keys):
4861 - Clients now support including Ed25519 identity keys in the EXTEND2
4862 cells they generate. By default, this is controlled by a consensus
4863 parameter, currently disabled. You can turn this feature on for
4864 testing by setting ExtendByEd25519ID in your configuration. This
4865 might make your traffic appear different than the traffic
4866 generated by other users, however. Implements part of ticket
4867 15056; part of proposal 220.
4868 - Relays now understand requests to extend to other relays by their
4869 Ed25519 identity keys. When an Ed25519 identity key is included in
4870 an EXTEND2 cell, the relay will only extend the circuit if the
4871 other relay can prove ownership of that identity. Implements part
4872 of ticket 15056; part of proposal 220.
4873 - Relays now use Ed25519 to prove their Ed25519 identities and to
4874 one another, and to clients. This algorithm is faster and more
4875 secure than the RSA-based handshake we've been doing until now.
4876 Implements the second big part of proposal 220; Closes
4879 o Major features (security):
4880 - Change the algorithm used to decide DNS TTLs on client and server
4881 side, to better resist DNS-based correlation attacks like the
4882 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
4883 Feamster. Now relays only return one of two possible DNS TTL
4884 values, and clients are willing to believe DNS TTL values up to 3
4885 hours long. Closes ticket 19769.
4887 o Major bugfixes (client, onion service, also in 0.2.9.9):
4888 - Fix a client-side onion service reachability bug, where multiple
4889 socks requests to an onion service (or a single slow request)
4890 could cause us to mistakenly mark some of the service's
4891 introduction points as failed, and we cache that failure so
4892 eventually we run out and can't reach the service. Also resolves a
4893 mysterious "Remote server sent bogus reason code 65021" log
4894 warning. The bug was introduced in ticket 17218, where we tried to
4895 remember the circuit end reason as a uint16_t, which mangled
4896 negative values. Partially fixes bug 21056 and fixes bug 20307;
4897 bugfix on 0.2.8.1-alpha.
4899 o Major bugfixes (crash, directory connections):
4900 - Fix a rare crash when sending a begin cell on a circuit whose
4901 linked directory connection had already been closed. Fixes bug
4902 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
4904 o Major bugfixes (directory authority):
4905 - During voting, when marking a relay as a probable sybil, do not
4906 clear its BadExit flag: sybils can still be bad in other ways
4907 too. (We still clear the other flags.) Fixes bug 21108; bugfix
4910 o Major bugfixes (DNS):
4911 - Fix a bug that prevented exit nodes from caching DNS records for
4912 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
4914 o Major bugfixes (IPv6 Exits):
4915 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
4916 any IPv6 addresses. Instead, only reject a port over IPv6 if the
4917 exit policy rejects that port on more than an IPv6 /16 of
4918 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
4919 which rejected a relay's own IPv6 address by default. Fixes bug
4920 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
4922 o Major bugfixes (parsing):
4923 - Fix an integer underflow bug when comparing malformed Tor
4924 versions. This bug could crash Tor when built with
4925 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4926 0.2.9.8, which were built with -ftrapv by default. In other cases
4927 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4928 on 0.0.8pre1. Found by OSS-Fuzz.
4929 - When parsing a malformed content-length field from an HTTP
4930 message, do not read off the end of the buffer. This bug was a
4931 potential remote denial-of-service attack against Tor clients and
4932 relays. A workaround was released in October 2016, to prevent this
4933 bug from crashing Tor. This is a fix for the underlying issue,
4934 which should no longer matter (if you applied the earlier patch).
4935 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
4936 using AFL (http://lcamtuf.coredump.cx/afl/).
4938 o Major bugfixes (scheduler):
4939 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
4940 caused the channel scheduler to behave more or less randomly,
4941 rather than preferring channels with higher-priority circuits.
4942 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
4944 o Major bugfixes (security, also in 0.2.9.9):
4945 - Downgrade the "-ftrapv" option from "always on" to "only on when
4946 --enable-expensive-hardening is provided." This hardening option,
4947 like others, can turn survivable bugs into crashes--and having it
4948 on by default made a (relatively harmless) integer overflow bug
4949 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
4950 bugfix on 0.2.9.1-alpha.
4952 o Minor feature (client):
4953 - Enable IPv6 traffic on the SocksPort by default. To disable this,
4954 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
4956 o Minor feature (fallback scripts):
4957 - Add a check_existing mode to updateFallbackDirs.py, which checks
4958 if fallbacks in the hard-coded list are working. Closes ticket
4959 20174. Patch by haxxpop.
4961 o Minor feature (protocol versioning):
4962 - Add new protocol version for proposal 224. HSIntro now advertises
4963 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
4965 o Minor features (ciphersuite selection):
4966 - Allow relays to accept a wider range of ciphersuites, including
4967 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
4968 - Clients now advertise a list of ciphersuites closer to the ones
4969 preferred by Firefox. Closes part of ticket 15426.
4971 o Minor features (controller):
4972 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
4973 shared-random values to the controller. Closes ticket 19925.
4974 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
4975 rather than "unrecognized." Closes ticket 20389; patch from
4978 o Minor features (controller, configuration):
4979 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
4980 and so on, now comes with a __*Port variant that will not be saved
4981 to the torrc file by the controller's SAVECONF command. This
4982 change allows TorBrowser to set up a single-use domain socket for
4983 each time it launches Tor. Closes ticket 20956.
4984 - The GETCONF command can now query options that may only be
4985 meaningful in context-sensitive lists. This allows the controller
4986 to query the mixed SocksPort/__SocksPort style options introduced
4987 in feature 20956. Implements ticket 21300.
4989 o Minor features (diagnostic, directory client):
4990 - Warn when we find an unexpected inconsistency in directory
4991 download status objects. Prevents some negative consequences of
4994 o Minor features (directory authorities):
4995 - Directory authorities now reject descriptors that claim to be
4996 malformed versions of Tor. Helps prevent exploitation of
4998 - Reject version numbers with components that exceed INT32_MAX.
4999 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
5000 Fixes bug 21450; bugfix on 0.0.8pre1.
5002 o Minor features (directory authority):
5003 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
5004 default) to control whether authorities should try to probe relays
5005 by their Ed25519 link keys. This option will go away in a few
5006 releases--unless we encounter major trouble in our ed25519 link
5007 protocol rollout, in which case it will serve as a safety option.
5009 o Minor features (directory cache):
5010 - Relays and bridges will now refuse to serve the consensus they
5011 have if they know it is too old for a client to use. Closes
5014 o Minor features (ed25519 link handshake):
5015 - Advertise support for the ed25519 link handshake using the
5016 subprotocol-versions mechanism, so that clients can tell which
5017 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
5019 o Minor features (entry guards):
5020 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
5021 break regression tests.
5022 - Require UseEntryGuards when UseBridges is set, in order to make
5023 sure bridges aren't bypassed. Resolves ticket 20502.
5025 o Minor features (fallback directories):
5026 - Allow 3 fallback relays per operator, which is safe now that we
5027 are choosing 200 fallback relays. Closes ticket 20912.
5028 - Annotate updateFallbackDirs.py with the bandwidth and consensus
5029 weight for each candidate fallback. Closes ticket 20878.
5030 - Display the relay fingerprint when downloading consensuses from
5031 fallbacks. Closes ticket 20908.
5032 - Exclude relays affected by bug 20499 from the fallback list.
5033 Exclude relays from the fallback list if they are running versions
5034 known to be affected by bug 20499, or if in our tests they deliver
5035 a stale consensus (i.e. one that expired more than 24 hours ago).
5036 Closes ticket 20539.
5037 - Make it easier to change the output sort order of fallbacks.
5038 Closes ticket 20822.
5039 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
5041 - Require fallback directories to have the same address and port for
5042 7 days (now that we have enough relays with this stability).
5043 Relays whose OnionOO stability timer is reset on restart by bug
5044 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
5045 this issue. Closes ticket 20880; maintains short-term fix
5047 - Require fallbacks to have flags for 90% of the time (weighted
5048 decaying average), rather than 95%. This allows at least 73% of
5049 clients to bootstrap in the first 5 seconds without contacting an
5050 authority. Part of ticket 18828.
5051 - Select 200 fallback directories for each release. Closes
5054 o Minor features (fingerprinting resistance, authentication):
5055 - Extend the length of RSA keys used for TLS link authentication to
5056 2048 bits. (These weren't used for forward secrecy; for forward
5057 secrecy, we used P256.) Closes ticket 13752.
5059 o Minor features (geoip):
5060 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
5063 o Minor features (geoip, also in 0.2.9.9):
5064 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
5067 o Minor features (infrastructure):
5068 - Implement smartlist_add_strdup() function. Replaces the use of
5069 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
5071 o Minor features (linting):
5072 - Enhance the changes file linter to warn on Tor versions that are
5073 prefixed with "tor-". Closes ticket 21096.
5075 o Minor features (logging):
5076 - In several places, describe unset ed25519 keys as "<unset>",
5077 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
5079 o Minor features (portability, compilation):
5080 - Autoconf now checks to determine if OpenSSL structures are opaque,
5081 instead of explicitly checking for OpenSSL version numbers. Part
5083 - Support building with recent LibreSSL code that uses opaque
5084 structures. Closes ticket 21359.
5086 o Minor features (relay):
5087 - We now allow separation of exit and relay traffic to different
5088 source IP addresses, using the OutboundBindAddressExit and
5089 OutboundBindAddressOR options respectively. Closes ticket 17975.
5090 Written by Michael Sonntag.
5092 o Minor features (reliability, crash):
5093 - Try better to detect problems in buffers where they might grow (or
5094 think they have grown) over 2 GB in size. Diagnostic for
5097 o Minor features (testing):
5098 - During 'make test-network-all', if tor logs any warnings, ask
5099 chutney to output them. Requires a recent version of chutney with
5100 the 21572 patch. Implements 21570.
5102 o Minor bugfix (control protocol):
5103 - The reply to a "GETINFO config/names" request via the control
5104 protocol now spells the type "Dependent" correctly. This is a
5105 breaking change in the control protocol. (The field seems to be
5106 ignored by the most common known controllers.) Fixes bug 18146;
5107 bugfix on 0.1.1.4-alpha.
5108 - The GETINFO extra-info/digest/<digest> command was broken because
5109 of a wrong base16 decode return value check, introduced when
5110 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
5112 o Minor bugfix (logging):
5113 - Don't recommend the use of Tor2web in non-anonymous mode.
5114 Recommending Tor2web is a bad idea because the client loses all
5115 anonymity. Tor2web should only be used in specific cases by users
5116 who *know* and understand the issues. Fixes bug 21294; bugfix
5119 o Minor bugfixes (bug resilience):
5120 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
5121 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
5122 Hans Jerry Illikainen.
5124 o Minor bugfixes (build):
5125 - Replace obsolete Autoconf macros with their modern equivalent and
5126 prevent similar issues in the future. Fixes bug 20990; bugfix
5129 o Minor bugfixes (certificate expiration time):
5130 - Avoid using link certificates that don't become valid till some
5131 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
5133 o Minor bugfixes (client):
5134 - Always recover from failures in extend_info_from_node(), in an
5135 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
5136 bugfix on 0.2.3.1-alpha.
5137 - When clients that use bridges start up with a cached consensus on
5138 disk, they were ignoring it and downloading a new one. Now they
5139 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
5141 o Minor bugfixes (code correctness):
5142 - Repair a couple of (unreachable or harmless) cases of the risky
5143 comparison-by-subtraction pattern that caused bug 21278.
5145 o Minor bugfixes (config):
5146 - Don't assert on startup when trying to get the options list and
5147 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
5148 options so of course they aren't ready yet. Fixes bug 21062;
5149 bugfix on 0.2.9.3-alpha.
5151 o Minor bugfixes (configuration):
5152 - Accept non-space whitespace characters after the severity level in
5153 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
5154 - Support "TByte" and "TBytes" units in options given in bytes.
5155 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
5156 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
5158 o Minor bugfixes (configure, autoconf):
5159 - Rename the configure option --enable-expensive-hardening to
5160 --enable-fragile-hardening. Expensive hardening makes the tor
5161 daemon abort when some kinds of issues are detected. Thus, it
5162 makes tor more at risk of remote crashes but safer against RCE or
5163 heartbleed bug category. We now try to explain this issue in a
5164 message from the configure script. Fixes bug 21290; bugfix
5167 o Minor bugfixes (consensus weight):
5168 - Add new consensus method that initializes bw weights to 1 instead
5169 of 0. This prevents a zero weight from making it all the way to
5170 the end (happens in small testing networks) and causing an error.
5171 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
5173 o Minor bugfixes (crash prevention):
5174 - Fix an (currently untriggerable, but potentially dangerous) crash
5175 bug when base32-encoding inputs whose sizes are not a multiple of
5176 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
5178 o Minor bugfixes (dead code):
5179 - Remove a redundant check for PidFile changes at runtime in
5180 options_transition_allowed(): this check is already performed
5181 regardless of whether the sandbox is active. Fixes bug 21123;
5182 bugfix on 0.2.5.4-alpha.
5184 o Minor bugfixes (descriptors):
5185 - Correctly recognise downloaded full descriptors as valid, even
5186 when using microdescriptors as circuits. This affects clients with
5187 FetchUselessDescriptors set, and may affect directory authorities.
5188 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
5190 o Minor bugfixes (directory mirrors):
5191 - Allow relays to use directory mirrors without a DirPort: these
5192 relays need to be contacted over their ORPorts using a begindir
5193 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
5194 - Clarify the message logged when a remote relay is unexpectedly
5195 missing an ORPort or DirPort: users were confusing this with a
5196 local port. Fixes another case of bug 20711; bugfix
5199 o Minor bugfixes (directory system):
5200 - Bridges and relays now use microdescriptors (like clients do)
5201 rather than old-style router descriptors. Now bridges will blend
5202 in with clients in terms of the circuits they build. Fixes bug
5203 6769; bugfix on 0.2.3.2-alpha.
5204 - Download all consensus flavors, descriptors, and authority
5205 certificates when FetchUselessDescriptors is set, regardless of
5206 whether tor is a directory cache or not. Fixes bug 20667; bugfix
5207 on all recent tor versions.
5209 o Minor bugfixes (documentation):
5210 - Update the tor manual page to document every option that can not
5211 be changed while tor is running. Fixes bug 21122.
5213 o Minor bugfixes (ed25519 certificates):
5214 - Correctly interpret ed25519 certificates that would expire some
5215 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
5217 o Minor bugfixes (fallback directories):
5218 - Avoid checking fallback candidates' DirPorts if they are down in
5219 OnionOO. When a relay operator has multiple relays, this
5220 prioritizes relays that are up over relays that are down. Fixes
5221 bug 20926; bugfix on 0.2.8.3-alpha.
5222 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
5223 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
5224 - Stop failing when a relay has no uptime data in
5225 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
5227 o Minor bugfixes (hidden service):
5228 - Clean up the code for expiring intro points with no associated
5229 circuits. It was causing, rarely, a service with some expiring
5230 introduction points to not open enough additional introduction
5231 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
5232 - Resolve two possible underflows which could lead to creating and
5233 closing a lot of introduction point circuits in a non-stop loop.
5234 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
5235 - Stop setting the torrc option HiddenServiceStatistics to "0" just
5236 because we're not a bridge or relay. Instead, we preserve whatever
5237 value the user set (or didn't set). Fixes bug 21150; bugfix
5240 o Minor bugfixes (hidden services):
5241 - Make hidden services check for failed intro point connections,
5242 even when they have exceeded their intro point creation limit.
5243 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
5244 - Make hidden services with 8 to 10 introduction points check for
5245 failed circuits immediately after startup. Previously, they would
5246 wait for 5 minutes before performing their first checks. Fixes bug
5247 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
5248 - Stop ignoring misconfigured hidden services. Instead, refuse to
5249 start tor until the misconfigurations have been corrected. Fixes
5250 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
5253 o Minor bugfixes (IPv6):
5254 - Make IPv6-using clients try harder to find an IPv6 directory
5255 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
5256 - When IPv6 addresses have not been downloaded yet (microdesc
5257 consensus documents don't list relay IPv6 addresses), use hard-
5258 coded addresses for authorities, fallbacks, and configured
5259 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
5260 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
5262 o Minor bugfixes (memory leak at exit):
5263 - Fix a small harmless memory leak at exit of the previously unused
5264 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
5267 o Minor bugfixes (onion services):
5268 - Allow the number of introduction points to be as low as 0, rather
5269 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
5271 o Minor bugfixes (portability):
5272 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
5273 It is supported by OpenBSD itself, and also by most OpenBSD
5274 variants (such as Bitrig). Fixes bug 20980; bugfix
5277 o Minor bugfixes (portability, also in 0.2.9.9):
5278 - Avoid crashing when Tor is built using headers that contain
5279 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
5280 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
5282 - Fix Libevent detection on platforms without Libevent 1 headers
5283 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
5285 o Minor bugfixes (relay):
5286 - Avoid a double-marked-circuit warning that could happen when we
5287 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
5289 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
5290 initializing the keys would reset the DataDirectory to 0700
5291 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
5292 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
5294 o Minor bugfixes (testing):
5295 - Fix Raspbian build issues related to missing socket errno in
5296 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
5297 - Remove undefined behavior from the backtrace generator by removing
5298 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
5299 - Use bash in src/test/test-network.sh. This ensures we reliably
5300 call chutney's newer tools/test-network.sh when available. Fixes
5301 bug 21562; bugfix on 0.2.9.1-alpha.
5303 o Minor bugfixes (tor-resolve):
5304 - The tor-resolve command line tool now rejects hostnames over 255
5305 characters in length. Previously, it would silently truncate them,
5306 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
5307 Patch by "junglefowl".
5309 o Minor bugfixes (unit tests):
5310 - Allow the unit tests to pass even when DNS lookups of bogus
5311 addresses do not fail as expected. Fixes bug 20862 and 20863;
5312 bugfix on unit tests introduced in 0.2.8.1-alpha
5313 through 0.2.9.4-alpha.
5315 o Minor bugfixes (util):
5316 - When finishing writing a file to disk, if we were about to replace
5317 the file with the temporary file created before and we fail to
5318 replace it, remove the temporary file so it doesn't stay on disk.
5319 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
5321 o Minor bugfixes (Windows services):
5322 - Be sure to initialize the monotonic time subsystem before using
5323 it, even when running as an NT service. Fixes bug 21356; bugfix
5326 o Minor bugfixes (Windows):
5327 - Check for getpagesize before using it to mmap files. This fixes
5328 compilation in some MinGW environments. Fixes bug 20530; bugfix on
5329 0.1.2.1-alpha. Reported by "ice".
5331 o Code simplification and refactoring:
5332 - Abolish all global guard context in entrynodes.c; replace with new
5333 guard_selection_t structure as preparation for proposal 271.
5334 Closes ticket 19858.
5335 - Extract magic numbers in circuituse.c into defined variables.
5336 - Introduce rend_service_is_ephemeral() that tells if given onion
5337 service is ephemeral. Replace unclear NULL-checkings for service
5338 directory with this function. Closes ticket 20526.
5339 - Refactor circuit_is_available_for_use to remove unnecessary check.
5340 - Refactor circuit_predict_and_launch_new for readability and
5341 testability. Closes ticket 18873.
5342 - Refactor code to manipulate global_origin_circuit_list into
5343 separate functions. Closes ticket 20921.
5344 - Refactor large if statement in purpose_needs_anonymity to use
5345 switch statement instead. Closes part of ticket 20077.
5346 - Refactor the hashing API to return negative values for errors, as
5347 is done as throughout the codebase. Closes ticket 20717.
5348 - Remove data structures that were used to index or_connection
5349 objects by their RSA identity digests. These structures are fully
5350 redundant with the similar structures used in the
5351 channel abstraction.
5352 - Remove duplicate code in the channel_write_*cell() functions.
5353 Closes ticket 13827; patch from Pingl.
5354 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
5355 use only purpose_needs_anonymity. Closes part of ticket 20077.
5356 - The code to generate and parse EXTEND and EXTEND2 cells has been
5357 replaced with code automatically generated by the
5360 o Documentation (formatting):
5361 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
5362 blocks were incorrectly appearing. Closes ticket 20885.
5364 o Documentation (man page):
5365 - Clarify many options in tor.1 and add some min/max values for
5366 HiddenService options. Closes ticket 21058.
5369 - Change '1' to 'weight_scale' in consensus bw weights calculation
5370 comments, as that is reality. Closes ticket 20273. Patch
5372 - Clarify that when ClientRejectInternalAddresses is enabled (which
5373 is the default), multicast DNS hostnames for machines on the local
5374 network (of the form *.local) are also rejected. Closes
5376 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
5377 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
5378 - Include the "TBits" unit in Tor's man page. Fixes part of bug
5379 20622; bugfix on 0.2.5.1-alpha.
5380 - Small fixes to the fuzzing documentation. Closes ticket 21472.
5381 - Stop the man page from incorrectly stating that HiddenServiceDir
5382 must already exist. Fixes 20486.
5383 - Update the description of the directory server options in the
5384 manual page, to clarify that a relay no longer needs to set
5385 DirPort in order to be a directory cache. Closes ticket 21720.
5388 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
5389 limit for relays running on a single IP applies to authority IP
5390 addresses as well as to non-authority IP addresses. Closes
5392 - The UseDirectoryGuards torrc option no longer exists: all users
5393 that use entry guards will also use directory guards. Related to
5394 proposal 271; implements part of ticket 20831.
5397 - Add tests for networkstatus_compute_bw_weights_v10.
5398 - Add unit tests circuit_predict_and_launch_new.
5399 - Extract dummy_origin_circuit_new so it can be used by other
5401 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
5402 from "overcaffeinated".
5403 - Perform the coding style checks when running the tests and fail
5404 when coding style violations are found. Closes ticket 5500.
5407 Changes in version 0.2.8.13 - 2017-03-03
5408 Tor 0.2.8.13 backports a security fix from later Tor
5409 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
5410 this release, if for some reason they cannot upgrade to a later
5411 release series, and if they build Tor with the --enable-expensive-hardening
5414 Note that support for Tor 0.2.8.x is ending next year: we will not issue
5415 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
5416 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5418 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5419 - Fix an integer underflow bug when comparing malformed Tor
5420 versions. This bug could crash Tor when built with
5421 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5422 0.2.9.8, which were built with -ftrapv by default. In other cases
5423 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5424 on 0.0.8pre1. Found by OSS-Fuzz.
5426 o Minor features (geoip):
5427 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5431 Changes in version 0.2.7.7 - 2017-03-03
5432 Tor 0.2.7.7 backports a number of security fixes from later Tor
5433 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
5434 this release, if for some reason they cannot upgrade to a later
5437 Note that support for Tor 0.2.7.x is ending this year: we will not issue
5438 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
5439 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5441 o Directory authority changes (backport from 0.2.8.5-rc):
5442 - Urras is no longer a directory authority. Closes ticket 19271.
5444 o Directory authority changes (backport from 0.2.9.2-alpha):
5445 - The "Tonga" bridge authority has been retired; the new bridge
5446 authority is "Bifroest". Closes tickets 19728 and 19690.
5448 o Directory authority key updates (backport from 0.2.8.1-alpha):
5449 - Update the V3 identity key for the dannenberg directory authority:
5450 it was changed on 18 November 2015. Closes task 17906. Patch
5453 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5454 - Fix a bug in parsing that could cause clients to read a single
5455 byte past the end of an allocated region. This bug could be used
5456 to cause hardened clients (built with --enable-expensive-hardening)
5457 to crash if they tried to visit a hostile hidden service. Non-
5458 hardened clients are only affected depending on the details of
5459 their platform's memory allocator. Fixes bug 21018; bugfix on
5460 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5461 2016-12-002 and as CVE-2016-1254.
5463 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5464 - Stop a crash that could occur when a client running with DNSPort
5465 received a query with multiple address types, and the first
5466 address type was not supported. Found and fixed by Scott Dial.
5467 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5468 - Prevent a class of security bugs caused by treating the contents
5469 of a buffer chunk as if they were a NUL-terminated string. At
5470 least one such bug seems to be present in all currently used
5471 versions of Tor, and would allow an attacker to remotely crash
5472 most Tor instances, especially those compiled with extra compiler
5473 hardening. With this defense in place, such bugs can't crash Tor,
5474 though we should still fix them as they occur. Closes ticket
5475 20384 (TROVE-2016-10-001).
5477 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5478 - Avoid a difficult-to-trigger heap corruption attack when extending
5479 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5480 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5481 Reported by Guido Vranken.
5483 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5484 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5485 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5487 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5488 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5489 pointer to the previous (uninitialized) key value. The impact here
5490 should be limited to a difficult-to-trigger crash, if OpenSSL is
5491 running an engine that makes key generation failures possible, or
5492 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5493 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5496 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5497 - Fix an integer underflow bug when comparing malformed Tor
5498 versions. This bug could crash Tor when built with
5499 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5500 0.2.9.8, which were built with -ftrapv by default. In other cases
5501 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5502 on 0.0.8pre1. Found by OSS-Fuzz.
5504 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5505 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5506 zero size. Check size argument to memwipe() for underflow. Fixes
5507 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5510 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5511 - Make Tor survive errors involving connections without a
5512 corresponding event object. Previously we'd fail with an
5513 assertion; now we produce a log message. Related to bug 16248.
5515 o Minor features (geoip):
5516 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5520 Changes in version 0.2.6.11 - 2017-03-03
5521 Tor 0.2.6.11 backports a number of security fixes from later Tor
5522 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
5523 this release, if for some reason they cannot upgrade to a later
5526 Note that support for Tor 0.2.6.x is ending this year: we will not issue
5527 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
5528 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5530 o Directory authority changes (backport from 0.2.8.5-rc):
5531 - Urras is no longer a directory authority. Closes ticket 19271.
5533 o Directory authority changes (backport from 0.2.9.2-alpha):
5534 - The "Tonga" bridge authority has been retired; the new bridge
5535 authority is "Bifroest". Closes tickets 19728 and 19690.
5537 o Directory authority key updates (backport from 0.2.8.1-alpha):
5538 - Update the V3 identity key for the dannenberg directory authority:
5539 it was changed on 18 November 2015. Closes task 17906. Patch
5542 o Major features (security fixes, backport from 0.2.9.4-alpha):
5543 - Prevent a class of security bugs caused by treating the contents
5544 of a buffer chunk as if they were a NUL-terminated string. At
5545 least one such bug seems to be present in all currently used
5546 versions of Tor, and would allow an attacker to remotely crash
5547 most Tor instances, especially those compiled with extra compiler
5548 hardening. With this defense in place, such bugs can't crash Tor,
5549 though we should still fix them as they occur. Closes ticket
5550 20384 (TROVE-2016-10-001).
5552 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5553 - Fix a bug in parsing that could cause clients to read a single
5554 byte past the end of an allocated region. This bug could be used
5555 to cause hardened clients (built with --enable-expensive-hardening)
5556 to crash if they tried to visit a hostile hidden service. Non-
5557 hardened clients are only affected depending on the details of
5558 their platform's memory allocator. Fixes bug 21018; bugfix on
5559 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5560 2016-12-002 and as CVE-2016-1254.
5562 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5563 - Stop a crash that could occur when a client running with DNSPort
5564 received a query with multiple address types, and the first
5565 address type was not supported. Found and fixed by Scott Dial.
5566 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5568 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5569 - Fix an error that could cause us to read 4 bytes before the
5570 beginning of an openssl string. This bug could be used to cause
5571 Tor to crash on systems with unusual malloc implementations, or
5572 systems with unusual hardening installed. Fixes bug 17404; bugfix
5575 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5576 - Avoid a difficult-to-trigger heap corruption attack when extending
5577 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5578 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5579 Reported by Guido Vranken.
5581 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5582 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5583 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5585 o Major bugfixes (guard selection, backport from 0.2.7.6):
5586 - Actually look at the Guard flag when selecting a new directory
5587 guard. When we implemented the directory guard design, we
5588 accidentally started treating all relays as if they have the Guard
5589 flag during guard selection, leading to weaker anonymity and worse
5590 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5593 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5594 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5595 pointer to the previous (uninitialized) key value. The impact here
5596 should be limited to a difficult-to-trigger crash, if OpenSSL is
5597 running an engine that makes key generation failures possible, or
5598 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5599 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5602 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5603 - Fix an integer underflow bug when comparing malformed Tor
5604 versions. This bug could crash Tor when built with
5605 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5606 0.2.9.8, which were built with -ftrapv by default. In other cases
5607 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5608 on 0.0.8pre1. Found by OSS-Fuzz.
5610 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5611 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5612 zero size. Check size argument to memwipe() for underflow. Fixes
5613 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5616 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5617 - Make Tor survive errors involving connections without a
5618 corresponding event object. Previously we'd fail with an
5619 assertion; now we produce a log message. Related to bug 16248.
5621 o Minor features (geoip):
5622 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5625 o Minor bugfixes (compilation, backport from 0.2.7.6):
5626 - Fix a compilation warning with Clang 3.6: Do not check the
5627 presence of an address which can never be NULL. Fixes bug 17781.
5630 Changes in version 0.2.5.13 - 2017-03-03
5631 Tor 0.2.5.13 backports a number of security fixes from later Tor
5632 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
5633 this release, if for some reason they cannot upgrade to a later
5636 Note that support for Tor 0.2.5.x is ending next year: we will not issue
5637 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
5638 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5640 o Directory authority changes (backport from 0.2.8.5-rc):
5641 - Urras is no longer a directory authority. Closes ticket 19271.
5643 o Directory authority changes (backport from 0.2.9.2-alpha):
5644 - The "Tonga" bridge authority has been retired; the new bridge
5645 authority is "Bifroest". Closes tickets 19728 and 19690.
5647 o Directory authority key updates (backport from 0.2.8.1-alpha):
5648 - Update the V3 identity key for the dannenberg directory authority:
5649 it was changed on 18 November 2015. Closes task 17906. Patch
5652 o Major features (security fixes, backport from 0.2.9.4-alpha):
5653 - Prevent a class of security bugs caused by treating the contents
5654 of a buffer chunk as if they were a NUL-terminated string. At
5655 least one such bug seems to be present in all currently used
5656 versions of Tor, and would allow an attacker to remotely crash
5657 most Tor instances, especially those compiled with extra compiler
5658 hardening. With this defense in place, such bugs can't crash Tor,
5659 though we should still fix them as they occur. Closes ticket
5660 20384 (TROVE-2016-10-001).
5662 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5663 - Fix a bug in parsing that could cause clients to read a single
5664 byte past the end of an allocated region. This bug could be used
5665 to cause hardened clients (built with --enable-expensive-hardening)
5666 to crash if they tried to visit a hostile hidden service. Non-
5667 hardened clients are only affected depending on the details of
5668 their platform's memory allocator. Fixes bug 21018; bugfix on
5669 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5670 2016-12-002 and as CVE-2016-1254.
5672 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5673 - Stop a crash that could occur when a client running with DNSPort
5674 received a query with multiple address types, and the first
5675 address type was not supported. Found and fixed by Scott Dial.
5676 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5678 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5679 - Fix an error that could cause us to read 4 bytes before the
5680 beginning of an openssl string. This bug could be used to cause
5681 Tor to crash on systems with unusual malloc implementations, or
5682 systems with unusual hardening installed. Fixes bug 17404; bugfix
5685 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5686 - Avoid a difficult-to-trigger heap corruption attack when extending
5687 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5688 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5689 Reported by Guido Vranken.
5691 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5692 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5693 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5695 o Major bugfixes (guard selection, backport from 0.2.7.6):
5696 - Actually look at the Guard flag when selecting a new directory
5697 guard. When we implemented the directory guard design, we
5698 accidentally started treating all relays as if they have the Guard
5699 flag during guard selection, leading to weaker anonymity and worse
5700 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5703 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5704 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5705 pointer to the previous (uninitialized) key value. The impact here
5706 should be limited to a difficult-to-trigger crash, if OpenSSL is
5707 running an engine that makes key generation failures possible, or
5708 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5709 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5712 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5713 - Fix an integer underflow bug when comparing malformed Tor
5714 versions. This bug could crash Tor when built with
5715 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5716 0.2.9.8, which were built with -ftrapv by default. In other cases
5717 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5718 on 0.0.8pre1. Found by OSS-Fuzz.
5720 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5721 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5722 zero size. Check size argument to memwipe() for underflow. Fixes
5723 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5726 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5727 - Make Tor survive errors involving connections without a
5728 corresponding event object. Previously we'd fail with an
5729 assertion; now we produce a log message. Related to bug 16248.
5731 o Minor features (geoip):
5732 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5735 o Minor bugfixes (compilation, backport from 0.2.7.6):
5736 - Fix a compilation warning with Clang 3.6: Do not check the
5737 presence of an address which can never be NULL. Fixes bug 17781.
5739 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
5740 - Check for failures from crypto_early_init, and refuse to continue.
5741 A previous typo meant that we could keep going with an
5742 uninitialized crypto library, and would have OpenSSL initialize
5743 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
5744 when implementing ticket 4900. Patch by "teor".
5746 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5747 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5748 a client authorized hidden service. Fixes bug 15823; bugfix
5752 Changes in version 0.2.4.28 - 2017-03-03
5753 Tor 0.2.4.28 backports a number of security fixes from later Tor
5754 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
5755 this release, if for some reason they cannot upgrade to a later
5758 Note that support for Tor 0.2.4.x is ending soon: we will not issue
5759 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
5760 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
5762 o Directory authority changes (backport from 0.2.8.5-rc):
5763 - Urras is no longer a directory authority. Closes ticket 19271.
5765 o Directory authority changes (backport from 0.2.9.2-alpha):
5766 - The "Tonga" bridge authority has been retired; the new bridge
5767 authority is "Bifroest". Closes tickets 19728 and 19690.
5769 o Directory authority key updates (backport from 0.2.8.1-alpha):
5770 - Update the V3 identity key for the dannenberg directory authority:
5771 it was changed on 18 November 2015. Closes task 17906. Patch
5774 o Major features (security fixes, backport from 0.2.9.4-alpha):
5775 - Prevent a class of security bugs caused by treating the contents
5776 of a buffer chunk as if they were a NUL-terminated string. At
5777 least one such bug seems to be present in all currently used
5778 versions of Tor, and would allow an attacker to remotely crash
5779 most Tor instances, especially those compiled with extra compiler
5780 hardening. With this defense in place, such bugs can't crash Tor,
5781 though we should still fix them as they occur. Closes ticket
5782 20384 (TROVE-2016-10-001).
5784 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5785 - Fix a bug in parsing that could cause clients to read a single
5786 byte past the end of an allocated region. This bug could be used
5787 to cause hardened clients (built with --enable-expensive-hardening)
5788 to crash if they tried to visit a hostile hidden service. Non-
5789 hardened clients are only affected depending on the details of
5790 their platform's memory allocator. Fixes bug 21018; bugfix on
5791 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5792 2016-12-002 and as CVE-2016-1254.
5794 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5795 - Fix an error that could cause us to read 4 bytes before the
5796 beginning of an openssl string. This bug could be used to cause
5797 Tor to crash on systems with unusual malloc implementations, or
5798 systems with unusual hardening installed. Fixes bug 17404; bugfix
5801 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5802 - Avoid a difficult-to-trigger heap corruption attack when extending
5803 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5804 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5805 Reported by Guido Vranken.
5807 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5808 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5809 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5811 o Major bugfixes (guard selection, backport from 0.2.7.6):
5812 - Actually look at the Guard flag when selecting a new directory
5813 guard. When we implemented the directory guard design, we
5814 accidentally started treating all relays as if they have the Guard
5815 flag during guard selection, leading to weaker anonymity and worse
5816 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5819 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5820 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5821 pointer to the previous (uninitialized) key value. The impact here
5822 should be limited to a difficult-to-trigger crash, if OpenSSL is
5823 running an engine that makes key generation failures possible, or
5824 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5825 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5828 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5829 - Fix an integer underflow bug when comparing malformed Tor
5830 versions. This bug could crash Tor when built with
5831 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5832 0.2.9.8, which were built with -ftrapv by default. In other cases
5833 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5834 on 0.0.8pre1. Found by OSS-Fuzz.
5836 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5837 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5838 zero size. Check size argument to memwipe() for underflow. Fixes
5839 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5842 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5843 - Make Tor survive errors involving connections without a
5844 corresponding event object. Previously we'd fail with an
5845 assertion; now we produce a log message. Related to bug 16248.
5847 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
5848 - Make it harder for attackers to overload hidden services with
5849 introductions, by blocking multiple introduction requests on the
5850 same circuit. Resolves ticket 15515.
5852 o Minor features (geoip):
5853 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5856 o Minor bugfixes (compilation, backport from 0.2.7.6):
5857 - Fix a compilation warning with Clang 3.6: Do not check the
5858 presence of an address which can never be NULL. Fixes bug 17781.
5860 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5861 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5862 a client authorized hidden service. Fixes bug 15823; bugfix
5866 Changes in version 0.2.9.10 - 2017-03-01
5867 Tor 0.2.9.10 backports a security fix from later Tor release. It also
5868 includes fixes for some major issues affecting directory authorities,
5869 LibreSSL compatibility, and IPv6 correctness.
5871 The Tor 0.2.9.x release series is now marked as a long-term-support
5872 series. We intend to backport security fixes to 0.2.9.x until at
5873 least January of 2020.
5875 o Major bugfixes (directory authority, 0.3.0.3-alpha):
5876 - During voting, when marking a relay as a probable sybil, do not
5877 clear its BadExit flag: sybils can still be bad in other ways
5878 too. (We still clear the other flags.) Fixes bug 21108; bugfix
5881 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
5882 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
5883 any IPv6 addresses. Instead, only reject a port over IPv6 if the
5884 exit policy rejects that port on more than an IPv6 /16 of
5885 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
5886 which rejected a relay's own IPv6 address by default. Fixes bug
5887 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
5889 o Major bugfixes (parsing, also in 0.3.0.4-rc):
5890 - Fix an integer underflow bug when comparing malformed Tor
5891 versions. This bug could crash Tor when built with
5892 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5893 0.2.9.8, which were built with -ftrapv by default. In other cases
5894 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5895 on 0.0.8pre1. Found by OSS-Fuzz.
5897 o Minor features (directory authorities, also in 0.3.0.4-rc):
5898 - Directory authorities now reject descriptors that claim to be
5899 malformed versions of Tor. Helps prevent exploitation of
5901 - Reject version numbers with components that exceed INT32_MAX.
5902 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
5903 Fixes bug 21450; bugfix on 0.0.8pre1.
5905 o Minor features (geoip):
5906 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5909 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
5910 - Autoconf now checks to determine if OpenSSL structures are opaque,
5911 instead of explicitly checking for OpenSSL version numbers. Part
5913 - Support building with recent LibreSSL code that uses opaque
5914 structures. Closes ticket 21359.
5916 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
5917 - Repair a couple of (unreachable or harmless) cases of the risky
5918 comparison-by-subtraction pattern that caused bug 21278.
5920 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
5921 - The tor-resolve command line tool now rejects hostnames over 255
5922 characters in length. Previously, it would silently truncate them,
5923 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
5924 Patch by "junglefowl".
5927 Changes in version 0.2.9.9 - 2017-01-23
5928 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
5929 cause relays and clients to crash, even if they were not built with
5930 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
5931 versions, and also affects 0.3.0.1-alpha: all relays running an affected
5932 version should upgrade.
5934 This release also resolves a client-side onion service reachability
5935 bug, and resolves a pair of small portability issues.
5937 o Major bugfixes (security):
5938 - Downgrade the "-ftrapv" option from "always on" to "only on when
5939 --enable-expensive-hardening is provided." This hardening option,
5940 like others, can turn survivable bugs into crashes -- and having
5941 it on by default made a (relatively harmless) integer overflow bug
5942 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
5943 bugfix on 0.2.9.1-alpha.
5945 o Major bugfixes (client, onion service):
5946 - Fix a client-side onion service reachability bug, where multiple
5947 socks requests to an onion service (or a single slow request)
5948 could cause us to mistakenly mark some of the service's
5949 introduction points as failed, and we cache that failure so
5950 eventually we run out and can't reach the service. Also resolves a
5951 mysterious "Remote server sent bogus reason code 65021" log
5952 warning. The bug was introduced in ticket 17218, where we tried to
5953 remember the circuit end reason as a uint16_t, which mangled
5954 negative values. Partially fixes bug 21056 and fixes bug 20307;
5955 bugfix on 0.2.8.1-alpha.
5957 o Minor features (geoip):
5958 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
5961 o Minor bugfixes (portability):
5962 - Avoid crashing when Tor is built using headers that contain
5963 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
5964 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
5966 - Fix Libevent detection on platforms without Libevent 1 headers
5967 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
5970 Changes in version 0.2.8.12 - 2016-12-19
5971 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
5972 below) where Tor clients could crash when attempting to visit a
5973 hostile hidden service. Clients are recommended to upgrade as packages
5974 become available for their systems.
5976 It also includes an updated list of fallback directories, backported
5979 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
5980 backported to 0.2.8 in the future.
5982 o Major bugfixes (parsing, security, backported from 0.2.9.8):
5983 - Fix a bug in parsing that could cause clients to read a single
5984 byte past the end of an allocated region. This bug could be used
5985 to cause hardened clients (built with --enable-expensive-hardening)
5986 to crash if they tried to visit a hostile hidden service. Non-
5987 hardened clients are only affected depending on the details of
5988 their platform's memory allocator. Fixes bug 21018; bugfix on
5989 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5990 2016-12-002 and as CVE-2016-1254.
5992 o Minor features (fallback directory list, backported from 0.2.9.8):
5993 - Replace the 81 remaining fallbacks of the 100 originally
5994 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
5995 fallbacks (123 new, 54 existing, 27 removed) generated in December
5996 2016. Resolves ticket 20170.
5998 o Minor features (geoip, backported from 0.2.9.7-rc):
5999 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
6003 Changes in version 0.2.9.8 - 2016-12-19
6004 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
6006 The Tor 0.2.9 series makes mandatory a number of security features
6007 that were formerly optional. It includes support for a new shared-
6008 randomness protocol that will form the basis for next generation
6009 hidden services, includes a single-hop hidden service mode for
6010 optimizing .onion services that don't actually want to be hidden,
6011 tries harder not to overload the directory authorities with excessive
6012 downloads, and supports a better protocol versioning scheme for
6013 improved compatibility with other implementations of the Tor protocol.
6015 And of course, there are numerous other bugfixes and improvements.
6017 This release also includes a fix for a medium-severity issue (bug
6018 21018 below) where Tor clients could crash when attempting to visit a
6019 hostile hidden service. Clients are recommended to upgrade as packages
6020 become available for their systems.
6022 Below are listed the changes since Tor 0.2.8.11. For a list of
6023 changes since 0.2.9.7-rc, see the ChangeLog file.
6025 o New system requirements:
6026 - When building with OpenSSL, Tor now requires version 1.0.1 or
6027 later. OpenSSL 1.0.0 and earlier are no longer supported by the
6028 OpenSSL team, and should not be used. Closes ticket 20303.
6029 - Tor now requires Libevent version 2.0.10-stable or later. Older
6030 versions of Libevent have less efficient backends for several
6031 platforms, and lack the DNS code that we use for our server-side
6032 DNS support. This implements ticket 19554.
6033 - Tor now requires zlib version 1.2 or later, for security,
6034 efficiency, and (eventually) gzip support. (Back when we started,
6035 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
6036 released in 2003. We recommend the latest version.)
6038 o Deprecated features:
6039 - A number of DNS-cache-related sub-options for client ports are now
6040 deprecated for security reasons, and may be removed in a future
6041 version of Tor. (We believe that client-side DNS caching is a bad
6042 idea for anonymity, and you should not turn it on.) The options
6043 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
6044 UseIPv4Cache, and UseIPv6Cache.
6045 - A number of options are deprecated for security reasons, and may
6046 be removed in a future version of Tor. The options are:
6047 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
6048 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
6049 CloseHSClientCircuitsImmediatelyOnTimeout,
6050 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
6051 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
6052 UseNTorHandshake, and WarnUnsafeSocks.
6053 - The *ListenAddress options are now deprecated as unnecessary: the
6054 corresponding *Port options should be used instead. These options
6055 may someday be removed. The affected options are:
6056 ControlListenAddress, DNSListenAddress, DirListenAddress,
6057 NATDListenAddress, ORListenAddress, SocksListenAddress,
6058 and TransListenAddress.
6060 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
6061 - Fix a bug in parsing that could cause clients to read a single
6062 byte past the end of an allocated region. This bug could be used
6063 to cause hardened clients (built with --enable-expensive-hardening)
6064 to crash if they tried to visit a hostile hidden service. Non-
6065 hardened clients are only affected depending on the details of
6066 their platform's memory allocator. Fixes bug 21018; bugfix on
6067 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
6068 2016-12-002 and as CVE-2016-1254.
6070 o Major features (build, hardening):
6071 - Tor now builds with -ftrapv by default on compilers that support
6072 it. This option detects signed integer overflow (which C forbids),
6073 and turns it into a hard-failure. We do not apply this option to
6074 code that needs to run in constant time to avoid side-channels;
6075 instead, we use -fwrapv in that code. Closes ticket 17983.
6076 - When --enable-expensive-hardening is selected, stop applying the
6077 clang/gcc sanitizers to code that needs to run in constant time.
6078 Although we are aware of no introduced side-channels, we are not
6079 able to prove that there are none. Related to ticket 17983.
6081 o Major features (circuit building, security):
6082 - Authorities, relays, and clients now require ntor keys in all
6083 descriptors, for all hops (except for rare hidden service protocol
6084 cases), for all circuits, and for all other roles. Part of
6086 - Authorities, relays, and clients only use ntor, except for
6087 rare cases in the hidden service protocol. Part of ticket 19163.
6089 o Major features (compilation):
6090 - Our big list of extra GCC warnings is now enabled by default when
6091 building with GCC (or with anything like Clang that claims to be
6092 GCC-compatible). To make all warnings into fatal compilation
6093 errors, pass --enable-fatal-warnings to configure. Closes
6095 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
6096 turn on C and POSIX extensions. (Previously, we attempted to do
6097 this on an ad hoc basis.) Closes ticket 19139.
6099 o Major features (directory authorities, hidden services):
6100 - Directory authorities can now perform the shared randomness
6101 protocol specified by proposal 250. Using this protocol, directory
6102 authorities generate a global fresh random value every day. In the
6103 future, this value will be used by hidden services to select
6104 HSDirs. This release implements the directory authority feature;
6105 the hidden service side will be implemented in the future as part
6106 of proposal 224. Resolves ticket 16943; implements proposal 250.
6108 o Major features (downloading, random exponential backoff):
6109 - When we fail to download an object from a directory service, wait
6110 for an (exponentially increasing) randomized amount of time before
6111 retrying, rather than a fixed interval as we did before. This
6112 prevents a group of Tor instances from becoming too synchronized,
6113 or a single Tor instance from becoming too predictable, in its
6114 download schedule. Closes ticket 15942.
6116 o Major features (resource management):
6117 - Tor can now notice it is about to run out of sockets, and
6118 preemptively close connections of lower priority. (This feature is
6119 off by default for now, since the current prioritizing method is
6120 yet not mature enough. You can enable it by setting
6121 "DisableOOSCheck 0", but watch out: it might close some sockets
6122 you would rather have it keep.) Closes ticket 18640.
6124 o Major features (single-hop "hidden" services):
6125 - Add experimental HiddenServiceSingleHopMode and
6126 HiddenServiceNonAnonymousMode options. When both are set to 1,
6127 every hidden service on that Tor instance becomes a non-anonymous
6128 Single Onion Service. Single Onions make one-hop (direct)
6129 connections to their introduction and rendezvous points. One-hop
6130 circuits make Single Onion servers easily locatable, but clients
6131 remain location-anonymous. This is compatible with the existing
6132 hidden service implementation, and works on the current Tor
6133 network without any changes to older relays or clients. Implements
6134 proposal 260, completes ticket 17178. Patch by teor and asn.
6136 o Major features (subprotocol versions):
6137 - Tor directory authorities now vote on a set of recommended
6138 "subprotocol versions", and on a set of required subprotocol
6139 versions. Clients and relays that lack support for a _required_
6140 subprotocol version will not start; those that lack support for a
6141 _recommended_ subprotocol version will warn the user to upgrade.
6142 This change allows compatible implementations of the Tor protocol(s)
6143 to exist without pretending to be 100% bug-compatible with
6144 particular releases of Tor itself. Closes ticket 19958; implements
6145 part of proposal 264.
6147 o Major bugfixes (circuit building):
6148 - Hidden service client-to-intro-point and service-to-rendezvous-
6149 point circuits use the TAP key supplied by the protocol, to avoid
6150 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
6152 o Major bugfixes (download scheduling):
6153 - Avoid resetting download status for consensuses hourly, since we
6154 already have another, smarter retry mechanism. Fixes bug 8625;
6155 bugfix on 0.2.0.9-alpha.
6156 - If a consensus expires while we are waiting for certificates to
6157 download, stop waiting for certificates.
6158 - If we stop waiting for certificates less than a minute after we
6159 started downloading them, do not consider the certificate download
6160 failure a separate failure. Fixes bug 20533; bugfix
6162 - When using exponential backoff in test networks, use a lower
6163 exponent, so the delays do not vary as much. This helps test
6164 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
6166 o Major bugfixes (exit policies):
6167 - Avoid disclosing exit outbound bind addresses, configured port
6168 bind addresses, and local interface addresses in relay descriptors
6169 by default under ExitPolicyRejectPrivate. Instead, only reject
6170 these (otherwise unlisted) addresses if
6171 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
6172 0.2.7.2-alpha. Patch by teor.
6174 o Major bugfixes (hidden services):
6175 - Allow Tor clients with appropriate controllers to work with
6176 FetchHidServDescriptors set to 0. Previously, this option also
6177 disabled descriptor cache lookup, thus breaking hidden services
6178 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
6179 - Clients now require hidden services to include the TAP keys for
6180 their intro points in the hidden service descriptor. This prevents
6181 an inadvertent upgrade to ntor, which a malicious hidden service
6182 could use to distinguish clients by consensus version. Fixes bug
6183 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
6185 o Major bugfixes (relay, resolver, logging):
6186 - For relays that don't know their own address, avoid attempting a
6187 local hostname resolve for each descriptor we download. This
6188 will cut down on the number of "Success: chose address 'x.x.x.x'"
6189 log lines, and also avoid confusing clock jumps if the resolver
6190 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
6192 o Minor features (port flags):
6193 - Add new flags to the *Port options to give finer control over which
6194 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
6195 and the synthetic flag OnionTrafficOnly, which is equivalent to
6196 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
6197 18693; patch by "teor".
6199 o Minor features (build, hardening):
6200 - Detect and work around a libclang_rt problem that would prevent
6201 clang from finding __mulodi4() on some 32-bit platforms, and thus
6202 keep -ftrapv from linking on those systems. Closes ticket 19079.
6203 - When building on a system without runtime support for the runtime
6204 hardening options, try to log a useful warning at configuration
6205 time, rather than an incomprehensible warning at link time. If
6206 expensive hardening was requested, this warning becomes an error.
6207 Closes ticket 18895.
6209 o Minor features (client, directory):
6210 - Since authorities now omit all routers that lack the Running and
6211 Valid flags, we assume that any relay listed in the consensus must
6212 have those flags. Closes ticket 20001; implements part of
6215 o Minor features (code safety):
6216 - In our integer-parsing functions, ensure that the maximum value we
6217 allow is no smaller than the minimum value. Closes ticket 19063;
6218 patch from "U+039b".
6220 o Minor features (compilation, portability):
6221 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
6224 o Minor features (config):
6225 - Warn users when descriptor and port addresses are inconsistent.
6226 Mitigates bug 13953; patch by teor.
6228 o Minor features (controller):
6229 - Allow controllers to configure basic client authorization on
6230 hidden services when they create them with the ADD_ONION controller
6231 command. Implements ticket 15588. Patch by "special".
6232 - Fire a STATUS_SERVER controller event whenever the hibernation
6233 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
6234 - Implement new GETINFO queries for all downloads that use
6235 download_status_t to schedule retries. This allows controllers to
6236 examine the schedule for pending downloads. Closes ticket 19323.
6238 o Minor features (development tools, etags):
6239 - Teach the "make tags" Makefile target how to correctly find
6240 "MOCK_IMPL" function definitions. Patch from nherring; closes
6243 o Minor features (directory authority):
6244 - After voting, if the authorities decide that a relay is not
6245 "Valid", they no longer include it in the consensus at all. Closes
6246 ticket 20002; implements part of proposal 272.
6247 - Directory authorities now only give the Guard flag to a relay if
6248 they are also giving it the Stable flag. This change allows us to
6249 simplify path selection for clients. It should have minimal effect
6250 in practice, since >99% of Guards already have the Stable flag.
6251 Implements ticket 18624.
6252 - Directory authorities now write their v3-status-votes file out to
6253 disk earlier in the consensus process, so we have a record of the
6254 votes even if we abort the consensus process. Resolves
6257 o Minor features (fallback directory list, new since 0.2.9.7-rc):
6258 - Replace the 81 remaining fallbacks of the 100 originally
6259 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
6260 fallbacks (123 new, 54 existing, 27 removed) generated in December
6261 2016. Resolves ticket 20170.
6263 o Minor features (hidden service):
6264 - Stop being so strict about the payload length of "rendezvous1"
6265 cells. We used to be locked in to the "TAP" handshake length, and
6266 now we can handle better handshakes like "ntor". Resolves
6269 o Minor features (infrastructure, time):
6270 - Tor now includes an improved timer backend, so that we can
6271 efficiently support tens or hundreds of thousands of concurrent
6272 timers, as will be needed for some of our planned anti-traffic-
6273 analysis work. This code is based on William Ahern's "timeout.c"
6274 project, which implements a "tickless hierarchical timing wheel".
6275 Closes ticket 18365.
6276 - Tor now uses the operating system's monotonic timers (where
6277 available) for internal fine-grained timing. Previously we would
6278 look at the system clock, and then attempt to compensate for the
6279 clock running backwards. Closes ticket 18908.
6281 o Minor features (logging):
6282 - Add a set of macros to check nonfatal assertions, for internal
6283 use. Migrating more of our checks to these should help us avoid
6284 needless crash bugs. Closes ticket 18613.
6285 - Provide a more useful warning message when configured with an
6286 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
6287 - When dumping unparseable router descriptors, optionally store them
6288 in separate files, named by digest, up to a configurable size
6289 limit. You can change the size limit by setting the
6290 MaxUnparseableDescSizeToLog option, and disable this feature by
6291 setting that option to 0. Closes ticket 18322.
6293 o Minor features (performance):
6294 - Change the "optimistic data" extension from "off by default" to
6295 "on by default". The default was ordinarily overridden by a
6296 consensus option, but when clients were bootstrapping for the
6297 first time, they would not have a consensus to get the option
6298 from. Changing this default saves a round-trip during startup.
6299 Closes ticket 18815.
6301 o Minor features (relay, usability):
6302 - When the directory authorities refuse a bad relay's descriptor,
6303 encourage the relay operator to contact us. Many relay operators
6304 won't notice this line in their logs, but it's a win if even a few
6305 learn why we don't like what their relay was doing. Resolves
6308 o Minor features (security, TLS):
6309 - Servers no longer support clients that lack AES ciphersuites.
6310 (3DES is no longer considered an acceptable cipher.) We believe
6311 that no such Tor clients currently exist, since Tor has required
6312 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
6314 o Minor features (testing):
6315 - Disable memory protections on OpenBSD when performing our unit
6316 tests for memwipe(). The test deliberately invokes undefined
6317 behavior, and the OpenBSD protections interfere with this. Patch
6318 from "rubiate". Closes ticket 20066.
6319 - Move the test-network.sh script to chutney, and modify tor's test-
6320 network.sh to call the (newer) chutney version when available.
6321 Resolves ticket 19116. Patch by teor.
6322 - Use the lcov convention for marking lines as unreachable, so that
6323 we don't count them when we're generating test coverage data.
6324 Update our coverage tools to understand this convention. Closes
6326 - Our link-handshake unit tests now check that when invalid
6327 handshakes fail, they fail with the error messages we expected.
6328 - Our unit testing code that captures log messages no longer
6329 prevents them from being written out if the user asked for them
6330 (by passing --debug or --info or --notice or --warn to the "test"
6331 binary). This change prevents us from missing unexpected log
6332 messages simply because we were looking for others. Related to
6334 - The unit tests now log all warning messages with the "BUG" flag.
6335 Previously, they only logged errors by default. This change will
6336 help us make our testing code more correct, and make sure that we
6337 only hit this code when we mean to. In the meantime, however,
6338 there will be more warnings in the unit test logs than before.
6339 This is preparatory work for ticket 19999.
6340 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
6341 assertion as a test failure.
6342 - We've done significant work to make the unit tests run faster.
6344 o Minor features (testing, ipv6):
6345 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
6346 tests. Remove bridges+hs, as it's somewhat redundant. This
6347 requires a recent chutney version that supports IPv6 clients,
6348 relays, and authorities. Closes ticket 20069; patch by teor.
6349 - Add the single-onion and single-onion-ipv6 chutney targets to
6350 "make test-network-all". This requires a recent chutney version
6351 with the single onion network flavors (git c72a652 or later).
6352 Closes ticket 20072; patch by teor.
6354 o Minor features (Tor2web):
6355 - Make Tor2web clients respect ReachableAddresses. This feature was
6356 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
6357 0.2.8.7. Implements feature 20034. Patch by teor.
6359 o Minor features (unix domain sockets):
6360 - When configuring a unix domain socket for a SocksPort,
6361 ControlPort, or Hidden service, you can now wrap the address in
6362 quotes, using C-style escapes inside the quotes. This allows unix
6363 domain socket paths to contain spaces. Resolves ticket 18753.
6365 o Minor features (user interface):
6366 - Tor now supports the ability to declare options deprecated, so
6367 that we can recommend that people stop using them. Previously, this
6368 was done in an ad-hoc way. There is a new --list-deprecated-options
6369 command-line option to list all of the deprecated options. Closes
6372 o Minor features (virtual addresses):
6373 - Increase the maximum number of bits for the IPv6 virtual network
6374 prefix from 16 to 104. In this way, the condition for address
6375 allocation is less restrictive. Closes ticket 20151; feature
6378 o Minor bug fixes (circuits):
6379 - Use the CircuitBuildTimeout option whenever
6380 LearnCircuitBuildTimeout is disabled. Previously, we would respect
6381 the option when a user disabled it, but not when it was disabled
6382 because some other option was set. Fixes bug 20073; bugfix on
6383 0.2.4.12-alpha. Patch by teor.
6385 o Minor bugfixes (build):
6386 - The current Git revision when building from a local repository is
6387 now detected correctly when using git worktrees. Fixes bug 20492;
6388 bugfix on 0.2.3.9-alpha.
6390 o Minor bugfixes (relay address discovery):
6391 - Stop reordering IP addresses returned by the OS. This makes it
6392 more likely that Tor will guess the same relay IP address every
6393 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
6394 Reported by René Mayrhofer, patch by "cypherpunks".
6396 o Minor bugfixes (memory allocation):
6397 - Change how we allocate memory for large chunks on buffers, to
6398 avoid a (currently impossible) integer overflow, and to waste less
6399 space when allocating unusually large chunks. Fixes bug 20081;
6400 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
6402 o Minor bugfixes (bootstrap):
6403 - Remember the directory server we fetched the consensus or previous
6404 certificates from, and use it to fetch future authority
6405 certificates. This change improves bootstrapping performance.
6406 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
6408 o Minor bugfixes (circuits):
6409 - Make sure extend_info_from_router() is only called on servers.
6410 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
6412 o Minor bugfixes (client, fascistfirewall):
6413 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
6414 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
6416 o Minor bugfixes (client, unix domain sockets):
6417 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
6418 the client address is meaningless. Fixes bug 20261; bugfix
6421 o Minor bugfixes (code style):
6422 - Fix an integer signedness conversion issue in the case conversion
6423 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
6425 o Minor bugfixes (compilation):
6426 - Build correctly on versions of libevent2 without support for
6427 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
6429 - When building with Clang, use a full set of GCC warnings.
6430 (Previously, we included only a subset, because of the way we
6431 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
6432 - Detect Libevent2 functions correctly on systems that provide
6433 libevent2, but where libevent1 is linked with -levent. Fixes bug
6434 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
6435 - Run correctly when built on Windows build environments that
6436 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
6438 o Minor bugfixes (configuration):
6439 - When parsing quoted configuration values from the torrc file,
6440 handle Windows line endings correctly. Fixes bug 19167; bugfix on
6441 0.2.0.16-alpha. Patch from "Pingl".
6443 o Minor bugfixes (directory authority):
6444 - Authorities now sort the "package" lines in their votes, for ease
6445 of debugging. (They are already sorted in consensus documents.)
6446 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
6447 - Die with a more useful error when the operator forgets to place
6448 the authority_signing_key file into the keys directory. This
6449 avoids an uninformative assert & traceback about having an invalid
6450 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
6451 - When allowing private addresses, mark Exits that only exit to
6452 private locations as such. Fixes bug 20064; bugfix
6454 - When parsing a detached signature, make sure we use the length of
6455 the digest algorithm instead of a hardcoded DIGEST256_LEN in
6456 order to avoid comparing bytes out-of-bounds with a smaller digest
6457 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
6459 o Minor bugfixes (getpass):
6460 - Defensively fix a non-triggerable heap corruption at do_getpass()
6461 to protect ourselves from mistakes in the future. Fixes bug
6462 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
6465 o Minor bugfixes (guard selection):
6466 - Don't mark guards as unreachable if connection_connect() fails.
6467 That function fails for local reasons, so it shouldn't reveal
6468 anything about the status of the guard. Fixes bug 14334; bugfix
6470 - Use a single entry guard even if the NumEntryGuards consensus
6471 parameter is not provided. Fixes bug 17688; bugfix
6474 o Minor bugfixes (hidden services):
6475 - Increase the minimum number of internal circuits we preemptively
6476 build from 2 to 3, so a circuit is available when a client
6477 connects to another onion service. Fixes bug 13239; bugfix
6479 - Allow hidden services to run on IPv6 addresses even when the
6480 IPv6Exit option is not set. Fixes bug 18357; bugfix
6482 - Stop logging intro point details to the client log on certain
6483 error conditions. Fixed as part of bug 20012; bugfix on
6484 0.2.4.8-alpha. Patch by teor.
6485 - When deleting an ephemeral hidden service, close its intro points
6486 even if they are not completely open. Fixes bug 18604; bugfix
6488 - When configuring hidden services, check every hidden service
6489 directory's permissions. Previously, we only checked the last
6490 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
6492 o Minor bugfixes (IPv6, testing):
6493 - Check for IPv6 correctly on Linux when running test networks.
6494 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
6496 o Minor bugfixes (Linux seccomp2 sandbox):
6497 - Add permission to run the sched_yield() and sigaltstack() system
6498 calls, in order to support versions of Tor compiled with asan or
6499 ubsan code that use these calls. Now "sandbox 1" and
6500 "--enable-expensive-hardening" should be compatible on more
6501 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
6503 o Minor bugfixes (logging):
6504 - Downgrade a harmless log message about the
6505 pending_entry_connections list from "warn" to "info". Mitigates
6507 - Log a more accurate message when we fail to dump a microdescriptor.
6508 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
6509 - When logging a directory ownership mismatch, log the owning
6510 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
6511 - When we are unable to remove the bw_accounting file, do not warn
6512 if the reason we couldn't remove it was that it didn't exist.
6513 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
6515 o Minor bugfixes (memory leak):
6516 - Fix a series of slow memory leaks related to parsing torrc files
6517 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
6518 - Avoid a small memory leak when informing worker threads about
6519 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
6520 - Fix a small memory leak when receiving AF_UNIX connections on a
6521 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
6522 - When moving a signed descriptor object from a source to an
6523 existing destination, free the allocated memory inside that
6524 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
6525 - Fix a memory leak and use-after-free error when removing entries
6526 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
6527 0.2.5.5-alpha. Patch from "cypherpunks".
6528 - Fix a small, uncommon memory leak that could occur when reading a
6529 truncated ed25519 key file. Fixes bug 18956; bugfix
6532 o Minor bugfixes (option parsing):
6533 - Count unix sockets when counting client listeners (SOCKS, Trans,
6534 NATD, and DNS). This has no user-visible behavior changes: these
6535 options are set once, and never read. Required for correct
6536 behavior in ticket 17178. Fixes bug 19677; bugfix on
6537 0.2.6.3-alpha. Patch by teor.
6539 o Minor bugfixes (options):
6540 - Check the consistency of UseEntryGuards and EntryNodes more
6541 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
6543 - Stop changing the configured value of UseEntryGuards on
6544 authorities and Tor2web clients. Fixes bug 20074; bugfix on
6545 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
6548 o Minor bugfixes (relay):
6549 - Ensure relays don't make multiple connections during bootstrap.
6550 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
6551 - Do not try to parallelize workers more than 16x without the user
6552 explicitly configuring us to do so, even if we do detect more than
6553 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
6555 o Minor bugfixes (testing):
6556 - The test-stem and test-network makefile targets now depend only on
6557 the tor binary that they are testing. Previously, they depended on
6558 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
6559 patch from "cypherpunks".
6560 - Allow clients to retry HSDirs much faster in test networks. Fixes
6561 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
6562 - Avoid a unit test failure on systems with over 16 detectable CPU
6563 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
6564 - Let backtrace tests work correctly under AddressSanitizer:
6565 disable ASAN's detection of segmentation faults while running
6566 test_bt.sh, so that we can make sure that our own backtrace
6567 generation code works. Fixes bug 18934; bugfix
6568 on 0.2.5.2-alpha. Patch from "cypherpunks".
6569 - Fix the test-network-all target on out-of-tree builds by using the
6570 correct path to the test driver script. Fixes bug 19421; bugfix
6572 - Stop spurious failures in the local interface address discovery
6573 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
6575 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
6576 removed the ECDH ciphers which caused the tests to fail on
6577 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
6578 - The tor_tls_server_info_callback unit test no longer crashes when
6579 debug-level logging is turned on. Fixes bug 20041; bugfix
6582 o Minor bugfixes (time):
6583 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
6584 bugfix on all released tor versions.
6585 - When computing the difference between two times in milliseconds,
6586 we now round to the nearest millisecond correctly. Previously, we
6587 could sometimes round in the wrong direction. Fixes bug 19428;
6588 bugfix on 0.2.2.2-alpha.
6590 o Minor bugfixes (Tor2web):
6591 - Prevent Tor2web clients from running hidden services: these services
6592 are not anonymous due to the one-hop client paths. Fixes bug
6593 19678. Patch by teor.
6595 o Minor bugfixes (user interface):
6596 - Display a more accurate number of suppressed messages in the log
6597 rate-limiter. Previously, there was a potential integer overflow
6598 in the counter. Now, if the number of messages hits a maximum, the
6599 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
6601 - Fix a typo in the passphrase prompt for the ed25519 identity key.
6602 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
6604 o Code simplification and refactoring:
6605 - Remove redundant declarations of the MIN macro. Closes
6607 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
6608 Closes ticket 18462; patch from "icanhasaccount".
6609 - Split the 600-line directory_handle_command_get function into
6610 separate functions for different URL types. Closes ticket 16698.
6613 - Add module-level internal documentation for 36 C files that
6614 previously didn't have a high-level overview. Closes ticket 20385.
6615 - Correct the IPv6 syntax in our documentation for the
6616 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
6617 - Correct the minimum bandwidth value in torrc.sample, and queue a
6618 corresponding change for torrc.minimal. Closes ticket 20085.
6619 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
6620 ticket 19153. Patch from "U+039b".
6621 - Module-level documentation for several more modules. Closes
6622 tickets 19287 and 19290.
6623 - Document the --passphrase-fd option in the tor manpage. Fixes bug
6624 19504; bugfix on 0.2.7.3-rc.
6625 - Document the default PathsNeededToBuildCircuits value that's used
6626 by clients when the directory authorities don't set
6627 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
6628 Patch by teor, reported by Jesse V.
6629 - Fix manual for the User option: it takes a username, not a UID.
6630 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
6632 - Fix the description of the --passphrase-fd option in the
6633 tor-gencert manpage. The option is used to pass the number of a
6634 file descriptor to read the passphrase from, not to read the file
6635 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
6638 - We no longer include the (dead, deprecated) bufferevent code in
6639 Tor. Closes ticket 19450. Based on a patch from "U+039b".
6642 - Remove support for "GET /tor/bytes.txt" DirPort request, and
6643 "GETINFO dir-usage" controller request, which were only available
6644 via a compile-time option in Tor anyway. Feature was added in
6645 0.2.2.1-alpha. Resolves ticket 19035.
6646 - There is no longer a compile-time option to disable support for
6647 TransPort. (If you don't want TransPort, just don't use it.) Patch
6648 from "U+039b". Closes ticket 19449.
6651 - Run more workqueue tests as part of "make check". These had
6652 previously been implemented, but you needed to know special
6653 command-line options to enable them.
6654 - We now have unit tests for our code to reject zlib "compression
6655 bombs". (Fortunately, the code works fine.)
6658 Changes in version 0.2.8.11 - 2016-12-08
6659 Tor 0.2.8.11 backports fixes for additional portability issues that
6660 could prevent Tor from building correctly on OSX Sierra, or with
6661 OpenSSL 1.1. Affected users should upgrade; others can safely stay
6664 o Minor bugfixes (portability):
6665 - Avoid compilation errors when building on OSX Sierra. Sierra began
6666 to support the getentropy() and clock_gettime() APIs, but created
6667 a few problems in doing so. Tor 0.2.9 has a more thorough set of
6668 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
6669 monotonic time interfaces. Fixes bug 20865. Bugfix
6672 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
6673 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
6674 architectures. Closes ticket 20588.
6677 Changes in version 0.2.8.10 - 2016-12-02
6678 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
6679 unusable after they left standby mode. It also backports fixes for
6680 a few portability issues and a small but problematic memory leak.
6682 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
6683 - When Tor leaves standby because of a new application request, open
6684 circuits as needed to serve that request. Previously, we would
6685 potentially wait a very long time. Fixes part of bug 19969; bugfix
6688 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
6689 - Clients now respond to new application stream requests immediately
6690 when they arrive, rather than waiting up to one second before
6691 starting to handle them. Fixes part of bug 19969; bugfix
6694 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
6695 - Work around a bug in the OSX 10.12 SDK that would prevent us from
6696 successfully targeting earlier versions of OSX. Resolves
6699 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
6700 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
6701 20551; bugfix on 0.2.1.1-alpha.
6703 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
6704 - Work around a memory leak in OpenSSL 1.1 when encoding public
6705 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
6707 o Minor features (geoip):
6708 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
6712 Changes in version 0.2.8.9 - 2016-10-17
6713 Tor 0.2.8.9 backports a fix for a security hole in previous versions
6714 of Tor that would allow a remote attacker to crash a Tor client,
6715 hidden service, relay, or authority. All Tor users should upgrade to
6716 this version, or to 0.2.9.4-alpha. Patches will be released for older
6719 o Major features (security fixes, also in 0.2.9.4-alpha):
6720 - Prevent a class of security bugs caused by treating the contents
6721 of a buffer chunk as if they were a NUL-terminated string. At
6722 least one such bug seems to be present in all currently used
6723 versions of Tor, and would allow an attacker to remotely crash
6724 most Tor instances, especially those compiled with extra compiler
6725 hardening. With this defense in place, such bugs can't crash Tor,
6726 though we should still fix them as they occur. Closes ticket
6727 20384 (TROVE-2016-10-001).
6729 o Minor features (geoip):
6730 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
6734 Changes in version 0.2.8.8 - 2016-09-23
6735 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
6736 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
6737 who select public relays as their bridges.
6739 o Major bugfixes (crash):
6740 - Fix a complicated crash bug that could affect Tor clients
6741 configured to use bridges when replacing a networkstatus consensus
6742 in which one of their bridges was mentioned. OpenBSD users saw
6743 more crashes here, but all platforms were potentially affected.
6744 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
6746 o Major bugfixes (relay, OOM handler):
6747 - Fix a timing-dependent assertion failure that could occur when we
6748 tried to flush from a circuit after having freed its cells because
6749 of an out-of-memory condition. Fixes bug 20203; bugfix on
6750 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
6753 o Minor feature (fallback directories):
6754 - Remove broken fallbacks from the hard-coded fallback directory
6755 list. Closes ticket 20190; patch by teor.
6757 o Minor features (geoip):
6758 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
6762 Changes in version 0.2.8.7 - 2016-08-24
6763 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
6764 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
6765 who sets the ReachableAddresses option, and all bridges, are strongly
6766 encouraged to upgrade.
6768 o Directory authority changes:
6769 - The "Tonga" bridge authority has been retired; the new bridge
6770 authority is "Bifroest". Closes tickets 19728 and 19690.
6772 o Major bugfixes (client, security):
6773 - Only use the ReachableAddresses option to restrict the first hop
6774 in a path. In earlier versions of 0.2.8.x, it would apply to
6775 every hop in the path, with a possible degradation in anonymity
6776 for anyone using an uncommon ReachableAddress setting. Fixes bug
6777 19973; bugfix on 0.2.8.2-alpha.
6779 o Minor features (geoip):
6780 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
6783 o Minor bugfixes (compilation):
6784 - Remove an inappropriate "inline" in tortls.c that was causing
6785 warnings on older versions of GCC. Fixes bug 19903; bugfix
6788 o Minor bugfixes (fallback directories):
6789 - Avoid logging a NULL string pointer when loading fallback
6790 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
6791 and 0.2.8.1-alpha. Report and patch by "rubiate".
6794 Changes in version 0.2.8.6 - 2016-08-02
6796 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
6798 The Tor 0.2.8 series improves client bootstrapping performance,
6799 completes the authority-side implementation of improved identity
6800 keys for relays, and includes numerous bugfixes and performance
6801 improvements throughout the program. This release continues to
6802 improve the coverage of Tor's test suite. For a full list of
6803 changes since Tor 0.2.7, see the ReleaseNotes file.
6805 Below is a list of the changes since Tor 0.2.7.
6807 o New system requirements:
6808 - Tor no longer attempts to support platforms where the "time_t"
6809 type is unsigned. (To the best of our knowledge, only OpenVMS does
6810 this, and Tor has never actually built on OpenVMS.) Closes
6812 - Tor no longer supports versions of OpenSSL with a broken
6813 implementation of counter mode. (This bug was present in OpenSSL
6814 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
6815 longer runs with, these versions.
6816 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
6817 later (released in 2008 and 2009 respectively). If you are
6818 building Tor from the git repository instead of from the source
6819 distribution, and your tools are older than this, you will need to
6820 upgrade. Closes ticket 17732.
6822 o Directory authority changes:
6823 - Update the V3 identity key for the dannenberg directory authority:
6824 it was changed on 18 November 2015. Closes task 17906. Patch
6826 - Urras is no longer a directory authority. Closes ticket 19271.
6828 o Major features (directory system):
6829 - Include a trial list of default fallback directories, based on an
6830 opt-in survey of suitable relays. Doing this should make clients
6831 bootstrap more quickly and reliably, and reduce the load on the
6832 directory authorities. Closes ticket 15775. Patch by teor.
6833 Candidates identified using an OnionOO script by weasel, teor,
6834 gsathya, and karsten.
6835 - Previously only relays that explicitly opened a directory port
6836 (DirPort) accepted directory requests from clients. Now all
6837 relays, with and without a DirPort, accept and serve tunneled
6838 directory requests that they receive through their ORPort. You can
6839 disable this behavior using the new DirCache option. Closes
6841 - When bootstrapping multiple consensus downloads at a time, use the
6842 first one that starts downloading, and close the rest. This
6843 reduces failures when authorities or fallback directories are slow
6844 or down. Together with the code for feature 15775, this feature
6845 should reduces failures due to fallback churn. Implements ticket
6846 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
6849 o Major features (security, Linux):
6850 - When Tor starts as root on Linux and is told to switch user ID, it
6851 can now retain the capability to bind to low ports. By default,
6852 Tor will do this only when it's switching user ID and some low
6853 ports have been configured. You can change this behavior with the
6854 new option KeepBindCapabilities. Closes ticket 8195.
6856 o Major bugfixes (client, bootstrapping):
6857 - Check if bootstrap consensus downloads are still needed when the
6858 linked connection attaches. This prevents tor making unnecessary
6859 begindir-style connections, which are the only directory
6860 connections tor clients make since the fix for 18483 was merged.
6861 - Fix some edge cases where consensus download connections may not
6862 have been closed, even though they were not needed. Related to fix
6864 - Make relays retry consensus downloads the correct number of times,
6865 rather than the more aggressive client retry count. Fixes part of
6868 o Major bugfixes (dns proxy mode, crash):
6869 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
6870 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
6872 o Major bugfixes (ed25519, voting):
6873 - Actually enable support for authorities to match routers by their
6874 Ed25519 identities. Previously, the code had been written, but
6875 some debugging code that had accidentally been left in the
6876 codebase made it stay turned off. Fixes bug 17702; bugfix
6878 - When collating votes by Ed25519 identities, authorities now
6879 include a "NoEdConsensus" flag if the ed25519 value (or lack
6880 thereof) for a server does not reflect the majority consensus.
6881 Related to bug 17668; bugfix on 0.2.7.2-alpha.
6882 - When generating a vote with keypinning disabled, never include two
6883 entries for the same ed25519 identity. This bug was causing
6884 authorities to generate votes that they could not parse when a
6885 router violated key pinning by changing its RSA identity but
6886 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
6887 18318. Bugfix on 0.2.7.2-alpha.
6889 o Major bugfixes (key management):
6890 - If OpenSSL fails to generate an RSA key, do not retain a dangling
6891 pointer to the previous (uninitialized) key value. The impact here
6892 should be limited to a difficult-to-trigger crash, if OpenSSL is
6893 running an engine that makes key generation failures possible, or
6894 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
6895 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
6898 o Major bugfixes (security, client, DNS proxy):
6899 - Stop a crash that could occur when a client running with DNSPort
6900 received a query with multiple address types, and the first
6901 address type was not supported. Found and fixed by Scott Dial.
6902 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
6904 o Major bugfixes (security, compilation):
6905 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
6906 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
6907 cause a compiler warning, thereby making other checks fail, and
6908 needlessly disabling compiler-hardening support. Fixes one case of
6909 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
6910 - Repair hardened builds under the clang compiler. Previously, our
6911 use of _FORTIFY_SOURCE would conflict with clang's address
6912 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
6914 o Major bugfixes (security, pointers):
6915 - Avoid a difficult-to-trigger heap corruption attack when extending
6916 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
6917 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
6918 Reported by Guido Vranken.
6920 o Major bugfixes (testing):
6921 - Fix a bug that would block 'make test-network-all' on systems where
6922 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
6924 o Major bugfixes (user interface):
6925 - Correctly give a warning in the cases where a relay is specified
6926 by nickname, and one such relay is found, but it is not officially
6927 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
6929 o Minor features (accounting):
6930 - Added two modes to the AccountingRule option: One for limiting
6931 only the number of bytes sent ("AccountingRule out"), and one for
6932 limiting only the number of bytes received ("AccountingRule in").
6933 Closes ticket 15989; patch from "unixninja92".
6935 o Minor features (bug-resistance):
6936 - Make Tor survive errors involving connections without a
6937 corresponding event object. Previously we'd fail with an
6938 assertion; now we produce a log message. Related to bug 16248.
6939 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
6940 level code, to harden against accidental failures to NUL-
6941 terminate. Part of ticket 17852. Patch from jsturgix. Found
6944 o Minor features (build):
6945 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
6946 as having possible IPFW support. Closes ticket 18448. Patch from
6948 - Since our build process now uses "make distcheck", we no longer
6949 force "make dist" to depend on "make check". Closes ticket 17893;
6950 patch from "cypherpunks".
6951 - Tor now builds once again with the recent OpenSSL 1.1 development
6952 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
6953 tracking OpenSSL 1.1 development as it has progressed, and fixing
6954 numerous compatibility issues as they arose. See tickets
6955 17549, 17921, 17984, 19499, and 18286.
6956 - When building manual pages, set the timezone to "UTC", so that the
6957 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
6958 Patch from intrigeri.
6960 o Minor features (clients):
6961 - Make clients, onion services, and bridge relays always use an
6962 encrypted begindir connection for directory requests. Resolves
6963 ticket 18483. Patch by teor.
6965 o Minor features (controller):
6966 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
6967 controllers can examine the the reject rules added by
6968 ExitPolicyRejectPrivate. This makes it easier for stem to display
6970 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
6971 tickets 16774 and 17817. Patch by George Tankersley.
6972 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
6973 service descriptor from a service's local hidden service
6974 descriptor cache. Closes ticket 14846.
6976 o Minor features (crypto):
6977 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
6978 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
6980 - Improve performance when hashing non-multiple of 8 sized buffers,
6981 based on Andrew Moon's public domain SipHash-2-4 implementation.
6982 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
6983 - Validate the hard-coded Diffie-Hellman parameters and ensure that
6984 p is a safe prime, and g is a suitable generator. Closes
6986 - When allocating a digest state object, allocate no more space than
6987 we actually need. Previously, we would allocate as much space as
6988 the state for the largest algorithm would need. This change saves
6989 up to 672 bytes per circuit. Closes ticket 17796.
6991 o Minor features (directory downloads):
6992 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
6993 directory mirrors. The default is 1; set it to 0 to disable
6994 fallbacks. Implements ticket 17576. Patch by teor.
6995 - Wait for busy authorities and fallback directories to become non-
6996 busy when bootstrapping. (A similar change was made in 6c443e987d
6997 for directory caches chosen from the consensus.) Closes ticket
6998 17864; patch by teor.
7000 o Minor features (geoip):
7001 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
7004 o Minor features (hidden service directory):
7005 - Streamline relay-side hsdir handling: when relays consider whether
7006 to accept an uploaded hidden service descriptor, they no longer
7007 check whether they are one of the relays in the network that is
7008 "supposed" to handle that descriptor. Implements ticket 18332.
7010 o Minor features (IPv6):
7011 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
7012 to 1, tor prefers IPv6 directory addresses.
7013 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
7014 avoids using IPv4 for client OR and directory connections.
7015 - Add address policy assume_action support for IPv6 addresses.
7016 - Add an argument 'ipv6=address:orport' to the DirAuthority and
7017 FallbackDir torrc options, to specify an IPv6 address for an
7018 authority or fallback directory. Add hard-coded ipv6 addresses for
7019 directory authorities that have them. Closes ticket 17327; patch
7020 from Nick Mathewson and teor.
7021 - Allow users to configure directory authorities and fallback
7022 directory servers with IPv6 addresses and ORPorts. Resolves
7024 - Limit IPv6 mask bits to 128.
7025 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
7026 17638; bugfix on 0.0.2pre8. Patch by teor.
7027 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
7028 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
7029 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
7030 - Warn when comparing against an AF_UNSPEC address in a policy, it's
7031 almost always a bug. Closes ticket 17863; patch by teor.
7032 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
7033 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
7035 o Minor features (Linux seccomp2 sandbox):
7036 - Reject attempts to change our Address with "Sandbox 1" enabled.
7037 Changing Address with Sandbox turned on would never actually work,
7038 but previously it would fail in strange and confusing ways. Found
7041 o Minor features (logging):
7042 - When logging to syslog, allow a tag to be added to the syslog
7043 identity (the string prepended to every log message). The tag can
7044 be configured with SyslogIdentityTag and defaults to none. Setting
7045 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
7048 o Minor features (portability):
7049 - Use timingsafe_memcmp() where available. Closes ticket 17944;
7050 patch from <logan@hackers.mu>.
7052 o Minor features (relay, address discovery):
7053 - Add a family argument to get_interface_addresses_raw() and
7054 subfunctions to make network interface address interogation more
7055 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
7056 types of interfaces from the operating system. Resolves
7058 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
7059 fails to enumerate interface addresses using the platform-specific
7060 API, have it rely on the UDP socket fallback technique to try and
7061 find out what IP addresses (both IPv4 and IPv6) our machine has.
7062 Resolves ticket 17951.
7064 o Minor features (replay cache):
7065 - The replay cache now uses SHA256 instead of SHA1. Implements
7066 feature 8961. Patch by teor, issue reported by rransom.
7068 o Minor features (robustness):
7069 - Exit immediately with an error message if the code attempts to use
7070 Libevent without having initialized it. This should resolve some
7071 frequently-made mistakes in our unit tests. Closes ticket 18241.
7073 o Minor features (security, clock):
7074 - Warn when the system clock appears to move back in time (when the
7075 state file was last written in the future). Tor doesn't know that
7076 consensuses have expired if the clock is in the past. Patch by
7077 teor. Implements ticket 17188.
7079 o Minor features (security, exit policies):
7080 - ExitPolicyRejectPrivate now rejects more private addresses by
7081 default. Specifically, it now rejects the relay's outbound bind
7082 addresses (if configured), and the relay's configured port
7083 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
7084 0.2.0.11-alpha. Patch by teor.
7086 o Minor features (security, memory erasure):
7087 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7088 zero size. Check size argument to memwipe() for underflow. Fixes
7089 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7091 - Set the unused entries in a smartlist to NULL. This helped catch
7092 a (harmless) bug, and shouldn't affect performance too much.
7093 Implements ticket 17026.
7094 - Use SecureMemoryWipe() function to securely clean memory on
7095 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
7096 Implements feature 17986.
7097 - Use explicit_bzero or memset_s when present. Previously, we'd use
7098 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
7099 from <logan@hackers.mu> and <selven@hackers.mu>.
7101 o Minor features (security, RNG):
7102 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
7103 positively are not allowed to fail. Previously we depended on
7104 internal details of OpenSSL's behavior. Closes ticket 17686.
7105 - Never use the system entropy output directly for anything besides
7106 seeding the PRNG. When we want to generate important keys, instead
7107 of using system entropy directly, we now hash it with the PRNG
7108 stream. This may help resist certain attacks based on broken OS
7109 entropy implementations. Closes part of ticket 17694.
7110 - Use modern system calls (like getentropy() or getrandom()) to
7111 generate strong entropy on platforms that have them. Closes
7114 o Minor features (security, win32):
7115 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
7116 attack. Fixes bug 18123; bugfix on all tor versions. Patch
7119 o Minor features (unix domain sockets):
7120 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
7121 Unix domain sockets without checking the permissions on the parent
7122 directory. (Tor checks permissions by default because some
7123 operating systems only check permissions on the parent directory.
7124 However, some operating systems do look at permissions on the
7125 socket, and tor's default check is unneeded.) Closes ticket 18458.
7128 o Minor features (unix file permissions):
7129 - Defer creation of Unix sockets until after setuid. This avoids
7130 needing CAP_CHOWN and CAP_FOWNER when using systemd's
7131 CapabilityBoundingSet, or chown and fowner when using SELinux.
7132 Implements part of ticket 17562. Patch from Jamie Nguyen.
7133 - If any directory created by Tor is marked as group readable, the
7134 filesystem group is allowed to be either the default GID or the
7135 root user. Allowing root to read the DataDirectory prevents the
7136 need for CAP_READ_SEARCH when using systemd's
7137 CapabilityBoundingSet, or dac_read_search when using SELinux.
7138 Implements part of ticket 17562. Patch from Jamie Nguyen.
7139 - Introduce a new DataDirectoryGroupReadable option. If it is set to
7140 1, the DataDirectory will be made readable by the default GID.
7141 Implements part of ticket 17562. Patch from Jamie Nguyen.
7143 o Minor bugfixes (accounting):
7144 - The max bandwidth when using 'AccountRule sum' is now correctly
7145 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
7148 o Minor bugfixes (assert, portability):
7149 - Fix an assertion failure in memarea.c on systems where "long" is
7150 shorter than the size of a pointer. Fixes bug 18716; bugfix
7153 o Minor bugfixes (bootstrap):
7154 - Consistently use the consensus download schedule for authority
7155 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
7157 o Minor bugfixes (build):
7158 - Avoid spurious failures from configure files related to calling
7159 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
7160 0.2.0.1-alpha. Patch from "cypherpunks".
7161 - Do not link the unit tests against both the testing and non-
7162 testing versions of the static libraries. Fixes bug 18490; bugfix
7164 - Resolve warnings when building on systems that are concerned with
7165 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
7167 - Silence spurious clang-scan warnings in the ed25519_donna code by
7168 explicitly initializing some objects. Fixes bug 18384; bugfix on
7169 0.2.7.2-alpha. Patch by teor.
7170 - When libscrypt.h is found, but no libscrypt library can be linked,
7171 treat libscrypt as absent. Fixes bug 19161; bugfix
7173 - Cause the unit tests to compile correctly on mingw64 versions that
7174 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
7175 - Don't try to use the pthread_condattr_setclock() function unless
7176 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
7177 17819; bugfix on 0.2.6.3-alpha.
7178 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
7180 - Fix search for libevent libraries on OpenBSD (and other systems
7181 that install libevent 1 and libevent 2 in parallel). Fixes bug
7182 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
7183 - Isolate environment variables meant for tests from the rest of the
7184 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
7185 - Mark all object files that include micro-revision.i as depending
7186 on it, so as to make parallel builds more reliable. Fixes bug
7187 17826; bugfix on 0.2.5.1-alpha.
7188 - Remove config.log only from make distclean, not from make clean.
7189 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
7190 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
7192 - Remove an #endif from configure.ac so that we correctly detect the
7193 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
7196 o Minor bugfixes (client, bootstrap):
7197 - Count receipt of new microdescriptors as progress towards
7198 bootstrapping. Previously, with EntryNodes set, Tor might not
7199 successfully repopulate the guard set on bootstrapping. Fixes bug
7200 16825; bugfix on 0.2.3.1-alpha.
7202 o Minor bugfixes (code correctness):
7203 - Fix a bad memory handling bug that would occur if we had queued a
7204 cell on a channel's incoming queue. Fortunately, we can't actually
7205 queue a cell like that as our code is constructed today, but it's
7206 best to avoid this kind of error, even if there isn't any code
7207 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
7208 - Assert that allocated memory held by the reputation code is freed
7209 according to its internal counters. Fixes bug 17753; bugfix
7211 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
7213 - Update to the latest version of Trunnel, which tries harder to
7214 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
7215 by clang address sanitizer. Fixes bug 18373; bugfix
7217 - When closing an entry connection, generate a warning if we should
7218 have sent an end cell for it but we haven't. Fixes bug 17876;
7219 bugfix on 0.2.3.2-alpha.
7221 o Minor bugfixes (configuration):
7222 - Fix a tiny memory leak when parsing a port configuration ending in
7223 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
7225 o Minor bugfixes (containers):
7226 - If we somehow attempt to construct a heap with more than
7227 1073741822 elements, avoid an integer overflow when maintaining
7228 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
7230 o Minor bugfixes (controller, microdescriptors):
7231 - Make GETINFO dir/status-vote/current/consensus conform to the
7232 control specification by returning "551 Could not open cached
7233 consensus..." when not caching consensuses. Fixes bug 18920;
7234 bugfix on 0.2.2.6-alpha.
7236 o Minor bugfixes (crypto):
7237 - Check the return value of HMAC() and assert on failure. Fixes bug
7238 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
7240 o Minor bugfixes (directories):
7241 - When fetching extrainfo documents, compare their SHA256 digests
7242 and Ed25519 signing key certificates with the routerinfo that led
7243 us to fetch them, rather than with the most recent routerinfo.
7244 Otherwise we generate many spurious warnings about mismatches.
7245 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
7246 - When generating a URL for a directory server on an IPv6 address,
7247 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
7248 on 0.2.3.9-alpha. Patch from Malek.
7250 o Minor bugfixes (downloading):
7251 - Predict more correctly whether we'll be downloading over HTTP when
7252 we determine the maximum length of a URL. This should avoid a
7253 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
7256 o Minor bugfixes (exit policies, security):
7257 - Refresh an exit relay's exit policy when interface addresses
7258 change. Previously, tor only refreshed the exit policy when the
7259 configured external address changed. Fixes bug 18208; bugfix on
7260 0.2.7.3-rc. Patch by teor.
7262 o Minor bugfixes (fallback directories):
7263 - Mark fallbacks as "too busy" when they return a 503 response,
7264 rather than just marking authorities. Fixes bug 17572; bugfix on
7265 0.2.4.7-alpha. Patch by teor.
7266 - When requesting extrainfo descriptors from a trusted directory
7267 server, check whether it is an authority or a fallback directory
7268 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
7269 0.2.4.7-alpha. Reported by atagar, patch by teor.
7271 o Minor bugfixes (hidden service, client):
7272 - Handle the case where the user makes several fast consecutive
7273 requests to the same .onion address. Previously, the first six
7274 requests would each trigger a descriptor fetch, each picking a
7275 directory (there are 6 overall) and the seventh one would fail
7276 because no directories were left, thereby triggering a close on
7277 all current directory connections asking for the hidden service.
7278 The solution here is to not close the connections if we have
7279 pending directory fetches. Fixes bug 15937; bugfix
7282 o Minor bugfixes (hidden service, control port):
7283 - Add the onion address to the HS_DESC event for the UPLOADED action
7284 both on success or failure. It was previously hardcoded with
7285 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
7287 o Minor bugfixes (hidden service, directory):
7288 - Bridges now refuse "rendezvous2" (hidden service descriptor)
7289 publish attempts. Suggested by ticket 18332.
7291 o Minor bugfixes (IPv6):
7292 - Update the limits in max_dl_per_request for IPv6 address length.
7293 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
7295 o Minor bugfixes (Linux seccomp2 sandbox):
7296 - Allow more syscalls when running with "Sandbox 1" enabled:
7297 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
7298 some systems, these are required for Tor to start. Fixes bug
7299 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
7300 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
7301 so that get_interface_address6_via_udp_socket_hack() can work.
7302 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
7303 - Allow the setrlimit syscall, and the prlimit and prlimit64
7304 syscalls, which some libc implementations use under the hood.
7305 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
7306 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
7307 enabled and no DNS resolvers configured. This should help TAILS
7308 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
7309 - Fix a crash when using offline master ed25519 keys with the Linux
7310 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
7311 - Allow statistics to be written to disk when "Sandbox 1" is
7312 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
7313 0.2.6.1-alpha respectively.
7315 o Minor bugfixes (logging):
7316 - In log messages that include a function name, use __FUNCTION__
7317 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
7318 with clang __PRETTY_FUNCTION__ has extra information we don't
7319 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
7321 - Remove needless quotes from a log message about unparseable
7322 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
7323 - Scrub service name in "unrecognized service ID" log messages.
7324 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
7325 - When logging information about an unparsable networkstatus vote or
7326 consensus, do not say "vote" when we mean consensus. Fixes bug
7327 18368; bugfix on 0.2.0.8-alpha.
7328 - When we can't generate a signing key because OfflineMasterKey is
7329 set, do not imply that we should have been able to load it. Fixes
7330 bug 18133; bugfix on 0.2.7.2-alpha.
7331 - When logging a malformed hostname received through socks4, scrub
7332 it if SafeLogging says we should. Fixes bug 17419; bugfix
7335 o Minor bugfixes (memory safety):
7336 - Avoid freeing an uninitialized pointer when opening a socket fails
7337 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
7338 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
7340 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
7341 18672; bugfix on 0.2.5.1-alpha.
7342 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
7345 o Minor bugfixes (pluggable transports):
7346 - Avoid reporting a spurious error when we decide that we don't need
7347 to terminate a pluggable transport because it has already exited.
7348 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
7350 o Minor bugfixes (pointer arithmetic):
7351 - Fix a bug in memarea_alloc() that could have resulted in remote
7352 heap write access, if Tor had ever passed an unchecked size to
7353 memarea_alloc(). Fortunately, all the sizes we pass to
7354 memarea_alloc() are pre-checked to be less than 128 kilobytes.
7355 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
7358 o Minor bugfixes (private directory):
7359 - Prevent a race condition when creating private directories. Fixes
7360 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
7361 Patch from jsturgix. Found with Flawfinder.
7363 o Minor bugfixes (relays):
7364 - Check that both the ORPort and DirPort (if present) are reachable
7365 before publishing a relay descriptor. Otherwise, relays publish a
7366 descriptor with DirPort 0 when the DirPort reachability test takes
7367 longer than the ORPort reachability test. Fixes bug 18050; bugfix
7368 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
7369 - Resolve some edge cases where we might launch an ORPort
7370 reachability check even when DisableNetwork is set. Noticed while
7371 fixing bug 18616; bugfix on 0.2.3.9-alpha.
7373 o Minor bugfixes (relays, hidden services):
7374 - Refuse connection requests to private OR addresses unless
7375 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
7376 then refuse to send any cells to a private address. Fixes bugs
7377 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
7379 o Minor bugfixes (security, hidden services):
7380 - Prevent hidden services connecting to client-supplied rendezvous
7381 addresses that are reserved as internal or multicast. Fixes bug
7382 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
7384 o Minor bugfixes (statistics):
7385 - Consistently check for overflow in round_*_to_next_multiple_of
7386 functions, and add unit tests with additional and maximal values.
7387 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
7388 - Handle edge cases in the laplace functions: avoid division by
7389 zero, avoid taking the log of zero, and silence clang type
7390 conversion warnings using round and trunc. Add unit tests for edge
7391 cases with maximal values. Fixes part of bug 13192; bugfix
7393 - We now include consensus downloads via IPv6 in our directory-
7394 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
7396 o Minor bugfixes (test networks, IPv6):
7397 - Allow internal IPv6 addresses in descriptors in test networks.
7398 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
7401 o Minor bugfixes (testing):
7402 - Check the full results of SHA256 and SHA512 digests in the unit
7403 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
7404 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
7406 - Fix a small memory leak that would occur when the
7407 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
7408 bugfix on 0.2.5.2-alpha.
7409 - Make unit tests pass on IPv6-only systems, and systems without
7410 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
7411 bugfix on 0.2.7.3-rc. Patch by teor.
7412 - The test for log_heartbeat was incorrectly failing in timezones
7413 with non-integer offsets. Instead of comparing the end of the time
7414 string against a constant, compare it to the output of
7415 format_local_iso_time when given the correct input. Fixes bug
7416 18039; bugfix on 0.2.5.4-alpha.
7417 - We no longer disable assertions in the unit tests when coverage is
7418 enabled. Instead, we require you to say --disable-asserts-in-tests
7419 to the configure script if you need assertions disabled in the
7420 unit tests (for example, if you want to perform branch coverage).
7421 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
7423 o Minor bugfixes (time handling):
7424 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
7425 field. Otherwise, our unit tests crash on Windows. Fixes bug
7426 18977; bugfix on 0.2.2.25-alpha.
7427 - Avoid overflow in tor_timegm when parsing dates in and after 2038
7428 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
7429 0.0.2pre14. Patch by teor.
7431 o Minor bugfixes (tor-gencert):
7432 - Correctly handle the case where an authority operator enters a
7433 passphrase but sends an EOF before sending a newline. Fixes bug
7434 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
7436 o Code simplification and refactoring:
7437 - Clean up a little duplicated code in
7438 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
7440 - Decouple the list of streams waiting to be attached to circuits
7441 from the overall connection list. This change makes it possible to
7442 attach streams quickly while simplifying Tor's callgraph and
7443 avoiding O(N) scans of the entire connection list. Closes
7445 - Extract the more complicated parts of circuit_mark_for_close()
7446 into a new function that we run periodically before circuits are
7447 freed. This change removes more than half of the functions
7448 currently in the "blob". Closes ticket 17218.
7449 - Move logging of redundant policy entries in
7450 policies_parse_exit_policy_internal into its own function. Closes
7451 ticket 17608; patch from "juce".
7452 - Quote all the string interpolations in configure.ac -- even those
7453 which we are pretty sure can't contain spaces. Closes ticket
7454 17744. Patch from zerosion.
7455 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
7456 use them. Closes ticket 17926.
7457 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
7458 inplace, so there's no need to have a separate implementation for
7459 the non-inplace code. Closes ticket 18258. Patch from Malek.
7460 - Simplify return types for some crypto functions that can't
7461 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
7462 - When a direct directory request fails immediately on launch,
7463 instead of relaunching that request from inside the code that
7464 launches it, instead mark the connection for teardown. This change
7465 simplifies Tor's callback and prevents the directory-request
7466 launching code from invoking itself recursively. Closes
7470 - Add a description of the correct use of the '--keygen' command-
7471 line option. Closes ticket 17583; based on text by 's7r'.
7472 - Change build messages to refer to "Fedora" instead of "Fedora
7473 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
7474 Patches from "icanhasaccount" and "cypherpunks".
7475 - Document the contents of the 'datadir/keys' subdirectory in the
7476 manual page. Closes ticket 17621.
7477 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
7478 - Explain actual minima for BandwidthRate. Closes ticket 16382.
7479 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
7480 - Mention torspec URL in the manpage and point the reader to it
7481 whenever we mention a document that belongs in torspce. Fixes
7483 - Stop recommending use of nicknames to identify relays in our
7484 MapAddress documentation. Closes ticket 18312.
7487 - Remove client-side support for connecting to Tor relays running
7488 versions of Tor before 0.2.3.6-alpha. These relays didn't support
7489 the v3 TLS handshake protocol, and are no longer allowed on the
7490 Tor network. Implements the client side of ticket 11150. Based on
7491 patches by Tom van der Woerdt.
7492 - We no longer maintain an internal freelist in memarea.c.
7493 Allocators should be good enough to make this code unnecessary,
7494 and it's doubtful that it ever had any performance benefit.
7497 - Add unit tests to check for common RNG failure modes, such as
7498 returning all zeroes, identical values, or incrementing values
7499 (OpenSSL's rand_predictable feature). Patch by teor.
7500 - Always test both ed25519 backends, so that we can be sure that our
7501 batch-open replacement code works. Part of ticket 16794.
7502 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
7503 portion of ticket 16831.
7504 - Fix several warnings from clang's address sanitizer produced in
7506 - Log more information when the backtrace tests fail. Closes ticket
7507 17892. Patch from "cypherpunks."
7508 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
7509 util_format.c, directory.c, and options_validate.c. Closes tickets
7510 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
7512 - Treat backtrace test failures as expected on FreeBSD until we
7513 solve bug 17808. Closes ticket 18204.
7514 - Unit tests for directory_handle_command_get. Closes ticket 17004.
7515 Patch from Reinaldo de Souza Jr.
7518 Changes in version 0.2.7.6 - 2015-12-10
7519 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
7520 well as a minor bug in hidden service reliability.
7522 o Major bugfixes (guard selection):
7523 - Actually look at the Guard flag when selecting a new directory
7524 guard. When we implemented the directory guard design, we
7525 accidentally started treating all relays as if they have the Guard
7526 flag during guard selection, leading to weaker anonymity and worse
7527 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7530 o Minor features (geoip):
7531 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
7534 o Minor bugfixes (compilation):
7535 - When checking for net/pfvar.h, include netinet/in.h if possible.
7536 This fixes transparent proxy detection on OpenBSD. Fixes bug
7537 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
7538 - Fix a compilation warning with Clang 3.6: Do not check the
7539 presence of an address which can never be NULL. Fixes bug 17781.
7541 o Minor bugfixes (correctness):
7542 - When displaying an IPv6 exit policy, include the mask bits
7543 correctly even when the number is greater than 31. Fixes bug
7544 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
7545 - The wrong list was used when looking up expired intro points in a
7546 rend service object, causing what we think could be reachability
7547 issues for hidden services, and triggering a BUG log. Fixes bug
7548 16702; bugfix on 0.2.7.2-alpha.
7549 - Fix undefined behavior in the tor_cert_checksig function. Fixes
7550 bug 17722; bugfix on 0.2.7.2-alpha.
7553 Changes in version 0.2.7.5 - 2015-11-20
7554 The Tor 0.2.7 release series is dedicated to the memory of Tor user
7555 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
7556 tirelessly to advocate human rights regardless of national borders,
7557 and oppose the encroachments of mass surveillance. He opposed national
7558 exceptionalism, he brought clarity to legal and policy debates, he
7559 understood and predicted the impact of mass surveillance on the world,
7560 and he laid the groundwork for resisting it. While serving on the Tor
7561 Project's board of directors, he brought us his uncompromising focus
7562 on technical excellence in the service of humankind. Caspar was an
7563 inimitable force for good and a wonderful friend. He was kind,
7564 humorous, generous, gallant, and believed we should protect one
7565 another without exception. We honor him here for his ideals, his
7566 efforts, and his accomplishments. Please honor his memory with works
7567 that would make him proud.
7569 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
7571 The 0.2.7 series adds a more secure identity key type for relays,
7572 improves cryptography performance, resolves several longstanding
7573 hidden-service performance issues, improves controller support for
7574 hidden services, and includes small bugfixes and performance
7575 improvements throughout the program. This release series also includes
7576 more tests than before, and significant simplifications to which parts
7577 of Tor invoke which others. For a full list of changes, see below.
7579 o New system requirements:
7580 - Tor no longer includes workarounds to support Libevent versions
7581 before 1.3e. Libevent 2.0 or later is recommended. Closes
7583 - Tor no longer supports copies of OpenSSL that are missing support
7584 for Elliptic Curve Cryptography. (We began using ECC when
7585 available in 0.2.4.8-alpha, for more safe and efficient key
7586 negotiation.) In particular, support for at least one of P256 or
7587 P224 is now required, with manual configuration needed if only
7588 P224 is available. Resolves ticket 16140.
7589 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
7590 on an operating system that has not upgraded to OpenSSL 1.0 or
7591 later, and you compile Tor from source, you will need to install a
7592 more recent OpenSSL to link Tor against.) These versions of
7593 OpenSSL are still supported by the OpenSSL, but the numerous
7594 cryptographic improvements in later OpenSSL releases makes them a
7595 clear choice. Resolves ticket 16034.
7597 o Major features (controller):
7598 - Add the ADD_ONION and DEL_ONION commands that allow the creation
7599 and management of hidden services via the controller. Closes
7601 - New "GETINFO onions/current" and "GETINFO onions/detached"
7602 commands to get information about hidden services created via the
7603 controller. Part of ticket 6411.
7604 - New HSFETCH command to launch a request for a hidden service
7605 descriptor. Closes ticket 14847.
7606 - New HSPOST command to upload a hidden service descriptor. Closes
7607 ticket 3523. Patch by "DonnchaC".
7609 o Major features (Ed25519 identity keys, Proposal 220):
7610 - Add support for offline encrypted Ed25519 master keys. To use this
7611 feature on your tor relay, run "tor --keygen" to make a new master
7612 key (or to make a new signing key if you already have a master
7613 key). Closes ticket 13642.
7614 - All relays now maintain a stronger identity key, using the Ed25519
7615 elliptic curve signature format. This master key is designed so
7616 that it can be kept offline. Relays also generate an online
7617 signing key, and a set of other Ed25519 keys and certificates.
7618 These are all automatically regenerated and rotated as needed.
7619 Implements part of ticket 12498.
7620 - Directory authorities now vote on Ed25519 identity keys along with
7621 RSA1024 keys. Implements part of ticket 12498.
7622 - Directory authorities track which Ed25519 identity keys have been
7623 used with which RSA1024 identity keys, and do not allow them to
7624 vary freely. Implements part of ticket 12498.
7625 - Microdescriptors now include Ed25519 identity keys. Implements
7626 part of ticket 12498.
7627 - Add a --newpass option to allow changing or removing the
7628 passphrase of an encrypted key with tor --keygen. Implements part
7630 - Add a new OfflineMasterKey option to tell Tor never to try loading
7631 or generating a secret Ed25519 identity key. You can use this in
7632 combination with tor --keygen to manage offline and/or encrypted
7633 Ed25519 keys. Implements ticket 16944.
7634 - On receiving a HUP signal, check to see whether the Ed25519
7635 signing key has changed, and reload it if so. Closes ticket 16790.
7636 - Significant usability improvements for Ed25519 key management. Log
7637 messages are better, and the code can recover from far more
7638 failure conditions. Thanks to "s7r" for reporting and diagnosing
7641 o Major features (ECC performance):
7642 - Improve the runtime speed of Ed25519 signature verification by
7643 using Ed25519-donna's batch verification support. Implements
7645 - Improve the speed of Ed25519 operations and Curve25519 keypair
7646 generation when built targeting 32 bit x86 platforms with SSE2
7647 available. Implements ticket 16535.
7648 - Improve the runtime speed of Ed25519 operations by using the
7649 public-domain Ed25519-donna by Andrew M. ("floodyberry").
7650 Implements ticket 16467.
7651 - Improve the runtime speed of the ntor handshake by using an
7652 optimized curve25519 basepoint scalarmult implementation from the
7653 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
7654 ideas by Adam Langley. Implements ticket 9663.
7656 o Major features (Hidden services):
7657 - Hidden services, if using the EntryNodes option, are required to
7658 use more than one EntryNode, in order to avoid a guard discovery
7659 attack. (This would only affect people who had configured hidden
7660 services and manually specified the EntryNodes option with a
7661 single entry-node. The impact was that it would be easy to
7662 remotely identify the guard node used by such a hidden service.
7663 See ticket for more information.) Fixes ticket 14917.
7664 - Add the torrc option HiddenServiceNumIntroductionPoints, to
7665 specify a fixed number of introduction points. Its maximum value
7666 is 10 and default is 3. Using this option can increase a hidden
7667 service's reliability under load, at the cost of making it more
7668 visible that the hidden service is facing extra load. Closes
7670 - Remove the adaptive algorithm for choosing the number of
7671 introduction points, which used to change the number of
7672 introduction points (poorly) depending on the number of
7673 connections the HS sees. Closes ticket 4862.
7675 o Major features (onion key cross-certification):
7676 - Relay descriptors now include signatures of their own identity
7677 keys, made using the TAP and ntor onion keys. These signatures
7678 allow relays to prove ownership of their own onion keys. Because
7679 of this change, microdescriptors will no longer need to include
7680 RSA identity keys. Implements proposal 228; closes ticket 12499.
7682 o Major bugfixes (client-side privacy, also in 0.2.6.9):
7683 - Properly separate out each SOCKSPort when applying stream
7684 isolation. The error occurred because each port's session group
7685 was being overwritten by a default value when the listener
7686 connection was initialized. Fixes bug 16247; bugfix on
7687 0.2.6.3-alpha. Patch by "jojelino".
7689 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
7690 - Stop refusing to store updated hidden service descriptors on a
7691 client. This reverts commit 9407040c59218 (which indeed fixed bug
7692 14219, but introduced a major hidden service reachability
7693 regression detailed in bug 16381). This is a temporary fix since
7694 we can live with the minor issue in bug 14219 (it just results in
7695 some load on the network) but the regression of 16381 is too much
7696 of a setback. First-round fix for bug 16381; bugfix
7699 o Major bugfixes (hidden services):
7700 - Revert commit that made directory authorities assign the HSDir
7701 flag to relays without a DirPort; this was bad because such relays
7702 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
7704 - When cannibalizing a circuit for an introduction point, always
7705 extend to the chosen exit node (creating a 4 hop circuit).
7706 Previously Tor would use the current circuit exit node, which
7707 changed the original choice of introduction point, and could cause
7708 the hidden service to skip excluded introduction points or
7709 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
7712 o Major bugfixes (memory leaks):
7713 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
7714 17398; bugfix on 0.2.6.1-alpha.
7716 o Major bugfixes (open file limit):
7717 - The open file limit wasn't checked before calling
7718 tor_accept_socket_nonblocking(), which would make Tor exceed the
7719 limit. Now, before opening a new socket, Tor validates the open
7720 file limit just before, and if the max has been reached, return an
7721 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
7723 o Major bugfixes (security, correctness):
7724 - Fix an error that could cause us to read 4 bytes before the
7725 beginning of an openssl string. This bug could be used to cause
7726 Tor to crash on systems with unusual malloc implementations, or
7727 systems with unusual hardening installed. Fixes bug 17404; bugfix
7730 o Major bugfixes (stability, also in 0.2.6.10):
7731 - Stop crashing with an assertion failure when parsing certain kinds
7732 of malformed or truncated microdescriptors. Fixes bug 16400;
7733 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
7734 by "cypherpunks_backup".
7735 - Stop random client-side assertion failures that could occur when
7736 connecting to a busy hidden service, or connecting to a hidden
7737 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
7740 o Minor features (client, SOCKS):
7741 - Add GroupWritable and WorldWritable options to unix-socket based
7742 SocksPort and ControlPort options. These options apply to a single
7743 socket, and override {Control,Socks}SocketsGroupWritable. Closes
7745 - Relax the validation done to hostnames in SOCKS5 requests, and
7746 allow a single trailing '.' to cope with clients that pass FQDNs
7747 using that syntax to explicitly indicate that the domain name is
7748 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
7749 - Relax the validation of hostnames in SOCKS5 requests, allowing the
7750 character '_' to appear, in order to cope with domains observed in
7751 the wild that are serving non-RFC compliant records. Resolves
7754 o Minor features (client-side privacy):
7755 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
7756 lifespan when IsolateSOCKSAuth and streams with SOCKS
7757 authentication are attached to the circuit. This allows
7758 applications like TorBrowser to manage circuit lifetime on their
7759 own. Implements feature 15482.
7760 - When logging malformed hostnames from SOCKS5 requests, respect
7761 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
7763 o Minor features (clock-jump tolerance):
7764 - Recover better when our clock jumps back many hours, like might
7765 happen for Tails or Whonix users who start with a very wrong
7766 hardware clock, use Tor to discover a more accurate time, and then
7767 fix their clock. Resolves part of ticket 8766.
7769 o Minor features (command-line interface):
7770 - Make --hash-password imply --hush to prevent unnecessary noise.
7771 Closes ticket 15542. Patch from "cypherpunks".
7772 - Print a warning whenever we find a relative file path being used
7773 as torrc option. Resolves issue 14018.
7775 o Minor features (compilation):
7776 - Give a warning as early as possible when trying to build with an
7777 unsupported OpenSSL version. Closes ticket 16901.
7778 - Use C99 variadic macros when the compiler is not GCC. This avoids
7779 failing compilations on MSVC, and fixes a log-file-based race
7780 condition in our old workarounds. Original patch from Gisle Vanem.
7782 o Minor features (control protocol):
7783 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
7784 the control protocol. Resolves ticket 15358.
7786 o Minor features (controller):
7787 - Add DirAuthority lines for default directory authorities to the
7788 output of the "GETINFO config/defaults" command if not already
7789 present. Implements ticket 14840.
7790 - Controllers can now use "GETINFO hs/client/desc/id/..." to
7791 retrieve items from the client's hidden service descriptor cache.
7792 Closes ticket 14845.
7793 - Implement a new controller command "GETINFO status/fresh-relay-
7794 descs" to fetch a descriptor/extrainfo pair that was generated on
7795 demand just for the controller's use. Implements ticket 14784.
7797 o Minor features (directory authorities):
7798 - Directory authorities no longer vote against the "Fast", "Stable",
7799 and "HSDir" flags just because they were going to vote against
7800 "Running": if the consensus turns out to be that the router was
7801 running, then the authority's vote should count. Patch from Peter
7802 Retzlaff; closes issue 8712.
7804 o Minor features (directory authorities, security, also in 0.2.6.9):
7805 - The HSDir flag given by authorities now requires the Stable flag.
7806 For the current network, this results in going from 2887 to 2806
7807 HSDirs. Also, it makes it harder for an attacker to launch a sybil
7808 attack by raising the effort for a relay to become Stable to
7809 require at the very least 7 days, while maintaining the 96 hours
7810 uptime requirement for HSDir. Implements ticket 8243.
7812 o Minor features (DoS-resistance):
7813 - Make it harder for attackers to overload hidden services with
7814 introductions, by blocking multiple introduction requests on the
7815 same circuit. Resolves ticket 15515.
7817 o Minor features (geoip):
7818 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
7821 o Minor features (hidden services):
7822 - Add the new options "HiddenServiceMaxStreams" and
7823 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
7824 limit the maximum number of simultaneous streams per circuit, and
7825 optionally tear down the circuit when the limit is exceeded. Part
7827 - Client now uses an introduction point failure cache to know when
7828 to fetch or keep a descriptor in their cache. Previously, failures
7829 were recorded implicitly, but not explicitly remembered. Closes
7831 - Relays need to have the Fast flag to get the HSDir flag. As this
7832 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
7833 drop. This change should make some attacks against the hidden
7834 service directory system harder. Fixes ticket 15963.
7835 - Turn on hidden service statistics collection by setting the torrc
7836 option HiddenServiceStatistics to "1" by default. (This keeps
7837 track only of the fraction of traffic used by hidden services, and
7838 the total number of hidden services in existence.) Closes
7840 - To avoid leaking HS popularity, don't cycle the introduction point
7841 when we've handled a fixed number of INTRODUCE2 cells but instead
7842 cycle it when a random number of introductions is reached, thus
7843 making it more difficult for an attacker to find out the amount of
7844 clients that have used the introduction point for a specific HS.
7845 Closes ticket 15745.
7847 o Minor features (logging):
7848 - Include the Tor version in all LD_BUG log messages, since people
7849 tend to cut and paste those into the bugtracker. Implements
7852 o Minor features (pluggable transports):
7853 - When launching managed pluggable transports on Linux systems,
7854 attempt to have the kernel deliver a SIGTERM on tor exit if the
7855 pluggable transport process is still running. Resolves
7857 - When launching managed pluggable transports, setup a valid open
7858 stdin in the child process that can be used to detect if tor has
7859 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
7860 can be used by implementations to detect this new behavior.
7861 Resolves ticket 15435.
7863 o Minor bugfixes (torrc exit policies):
7864 - In each instance above, usage advice is provided to avoid the
7865 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
7866 16069; bugfix on 0.2.4.7-alpha.
7867 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
7868 produce IPv6 wildcard addresses. Previously they would produce
7869 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
7870 of bug 16069; bugfix on 0.2.4.7-alpha.
7871 - When parsing torrc ExitPolicies, we now issue an info-level
7872 message when expanding an "accept/reject *" line to include both
7873 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
7874 - When parsing torrc ExitPolicies, we now warn for a number of cases
7875 where the user's intent is likely to differ from Tor's actual
7876 behavior. These include: using an IPv4 address with an accept6 or
7877 reject6 line; using "private" on an accept6 or reject6 line; and
7878 including any ExitPolicy lines after accept *:* or reject *:*.
7879 Related to ticket 16069.
7881 o Minor bugfixes (command-line interface):
7882 - When "--quiet" is provided along with "--validate-config", do not
7883 write anything to stdout on success. Fixes bug 14994; bugfix
7885 - When complaining about bad arguments to "--dump-config", use
7887 - Print usage information for --dump-config when it is used without
7888 an argument. Also, fix the error message to use different wording
7889 and add newline at the end. Fixes bug 15541; bugfix
7892 o Minor bugfixes (compilation):
7893 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
7894 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
7895 - Repair compilation with the most recent (unreleased, alpha)
7896 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
7898 o Minor bugfixes (compilation, also in 0.2.6.9):
7899 - Build with --enable-systemd correctly when libsystemd is
7900 installed, but systemd is not. Fixes bug 16164; bugfix on
7901 0.2.6.3-alpha. Patch from Peter Palfrader.
7903 o Minor bugfixes (configuration, unit tests):
7904 - Only add the default fallback directories when the DirAuthorities,
7905 AlternateDirAuthority, and FallbackDir directory config options
7906 are set to their defaults. The default fallback directory list is
7907 currently empty, this fix will only change tor's behavior when it
7908 has default fallback directories. Includes unit tests for
7909 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
7910 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
7912 o Minor bugfixes (controller):
7913 - Add the descriptor ID in each HS_DESC control event. It was
7914 missing, but specified in control-spec.txt. Fixes bug 15881;
7915 bugfix on 0.2.5.2-alpha.
7917 o Minor bugfixes (correctness):
7918 - For correctness, avoid modifying a constant string in
7919 handle_control_postdescriptor. Fixes bug 15546; bugfix
7921 - Remove side-effects from tor_assert() calls. This was harmless,
7922 because we never disable assertions, but it is bad style and
7923 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
7925 - When calling channel_free_list(), avoid calling smartlist_remove()
7926 while inside a FOREACH loop. This partially reverts commit
7927 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
7928 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
7930 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
7931 - Check for failures from crypto_early_init, and refuse to continue.
7932 A previous typo meant that we could keep going with an
7933 uninitialized crypto library, and would have OpenSSL initialize
7934 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7935 when implementing ticket 4900. Patch by "teor".
7937 o Minor bugfixes (hidden service):
7938 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7939 a client authorized hidden service. Fixes bug 15823; bugfix
7941 - Remove an extraneous newline character from the end of hidden
7942 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
7944 o Minor bugfixes (Linux seccomp2 sandbox):
7945 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
7946 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
7947 - Allow bridge authorities to run correctly under the seccomp2
7948 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
7949 - Add the "hidserv-stats" filename to our sandbox filter for the
7950 HiddenServiceStatistics option to work properly. Fixes bug 17354;
7951 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
7953 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
7954 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
7955 these when eventfd2() support is missing. Fixes bug 16363; bugfix
7956 on 0.2.6.3-alpha. Patch from "teor".
7958 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
7959 - Allow systemd connections to work with the Linux seccomp2 sandbox
7960 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
7962 - Fix sandboxing to work when running as a relay, by allowing the
7963 renaming of secret_id_key, and allowing the eventfd2 and futex
7964 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
7967 o Minor bugfixes (logging):
7968 - When building Tor under Clang, do not include an extra set of
7969 parentheses in log messages that include function names. Fixes bug
7970 15269; bugfix on every released version of Tor when compiled with
7971 recent enough Clang.
7973 o Minor bugfixes (network):
7974 - When attempting to use fallback technique for network interface
7975 lookup, disregard loopback and multicast addresses since they are
7976 unsuitable for public communications.
7978 o Minor bugfixes (open file limit):
7979 - Fix set_max_file_descriptors() to set by default the max open file
7980 limit to the current limit when setrlimit() fails. Fixes bug
7981 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
7983 o Minor bugfixes (portability):
7984 - Check correctly for Windows socket errors in the workqueue
7985 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
7986 - Try harder to normalize the exit status of the Tor process to the
7987 standard-provided range. Fixes bug 16975; bugfix on every version
7989 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
7990 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
7992 o Minor bugfixes (relay):
7993 - Ensure that worker threads actually exit when a fatal error or
7994 shutdown is indicated. This fix doesn't currently affect the
7995 behavior of Tor, because Tor workers never indicates fatal error
7996 or shutdown except in the unit tests. Fixes bug 16868; bugfix
7998 - Fix a rarely-encountered memory leak when failing to initialize
7999 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
8001 - Unblock threads before releasing the work queue mutex to ensure
8002 predictable scheduling behavior. Fixes bug 16644; bugfix
8005 o Minor bugfixes (security, exit policies):
8006 - ExitPolicyRejectPrivate now also rejects the relay's published
8007 IPv6 address (if any), and any publicly routable IPv4 or IPv6
8008 addresses on any local interfaces. ticket 17027. Patch by "teor".
8009 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
8011 o Minor bugfixes (statistics):
8012 - Disregard the ConnDirectionStatistics torrc options when Tor is
8013 not a relay since in that mode of operation no sensible data is
8014 being collected and because Tor might run into measurement hiccups
8015 when running as a client for some time, then becoming a relay.
8016 Fixes bug 15604; bugfix on 0.2.2.35.
8018 o Minor bugfixes (systemd):
8019 - Tor's systemd unit file no longer contains extraneous spaces.
8020 These spaces would sometimes confuse tools like deb-systemd-
8021 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
8023 o Minor bugfixes (test networks):
8024 - When self-testing reachability, use ExtendAllowPrivateAddresses to
8025 determine if local/private addresses imply reachability. The
8026 previous fix used TestingTorNetwork, which implies
8027 ExtendAllowPrivateAddresses, but this excluded rare configurations
8028 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
8029 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
8030 issue discovered by CJ Ess.
8032 o Minor bugfixes (tests, also in 0.2.6.9):
8033 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
8034 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
8036 o Code simplification and refactoring:
8037 - Change the function that's called when we need to retry all
8038 downloads so that it only reschedules the downloads to happen
8039 immediately, rather than launching them all at once itself. This
8040 further simplifies Tor's callgraph.
8041 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
8042 to ensure they remain consistent and visible everywhere.
8043 - Move some format-parsing functions out of crypto.c and
8044 crypto_curve25519.c into crypto_format.c and/or util_format.c.
8045 - Move the client-only parts of init_keys() into a separate
8046 function. Closes ticket 16763.
8047 - Move the hacky fallback code out of get_interface_address6() into
8048 separate function and get it covered with unit-tests. Resolves
8050 - Refactor hidden service client-side cache lookup to intelligently
8051 report its various failure cases, and disentangle failure cases
8052 involving a lack of introduction points. Closes ticket 14391.
8053 - Remove some vestigial workarounds for the MSVC6 compiler. We
8054 haven't supported that in ages.
8055 - Remove the unused "nulterminate" argument from buf_pullup().
8056 - Simplify the microdesc_free() implementation so that it no longer
8057 appears (to code analysis tools) to potentially invoke a huge
8058 suite of other microdesc functions.
8059 - Simply the control graph further by deferring the inner body of
8060 directory_all_unreachable() into a callback. Closes ticket 16762.
8061 - The link authentication code has been refactored for better
8062 testability and reliability. It now uses code generated with the
8063 "trunnel" binary encoding generator, to reduce the risk of bugs
8064 due to programmer error. Done as part of ticket 12498.
8065 - Treat the loss of an owning controller as equivalent to a SIGTERM
8066 signal. This removes a tiny amount of duplicated code, and
8067 simplifies our callgraph. Closes ticket 16788.
8068 - Use our own Base64 encoder instead of OpenSSL's, to allow more
8069 control over the output. Part of ticket 15652.
8070 - When generating an event to send to the controller, we no longer
8071 put the event over the network immediately. Instead, we queue
8072 these events, and use a Libevent callback to deliver them. This
8073 change simplifies Tor's callgraph by reducing the number of
8074 functions from which all other Tor functions are reachable. Closes
8076 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
8077 that try to scan or compile every file on Unix won't decide that
8081 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
8082 - Improve the descriptions of statistics-related torrc options in
8083 the manpage to describe rationale and possible uses cases. Fixes
8085 - Improve the layout and formatting of ./configure --help messages.
8086 Closes ticket 15024. Patch from "cypherpunks".
8087 - Include a specific and (hopefully) accurate documentation of the
8088 torrc file's meta-format in doc/torrc_format.txt. This is mainly
8089 of interest to people writing programs to parse or generate torrc
8090 files. This document is not a commitment to long-term
8091 compatibility; some aspects of the current format are a bit
8092 ridiculous. Closes ticket 2325.
8093 - Include the TUNING document in our source tarball. It is referred
8094 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
8096 - Note that HiddenServicePorts can take a unix domain socket. Closes
8098 - Recommend a 40 GB example AccountingMax in torrc.sample rather
8099 than a 4 GB max. Closes ticket 16742.
8100 - Standardize on the term "server descriptor" in the manual page.
8101 Previously, we had used "router descriptor", "server descriptor",
8102 and "relay descriptor" interchangeably. Part of ticket 14987.
8103 - Advise users on how to configure separate IPv4 and IPv6 exit
8104 policies in the manpage and sample torrcs. Related to ticket 16069.
8105 - Fix an error in the manual page and comments for
8106 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
8107 required "ORPort connectivity". While this is true, it is in no
8108 way unique to the HSDir flag. Of all the flags, only HSDirs need a
8109 DirPort configured in order for the authorities to assign that
8110 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
8112 - Fix the usage message of tor-resolve(1) so that it no longer lists
8113 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
8116 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
8117 and always use the internal Base64 decoder. The internal decoder
8118 has been part of tor since 0.2.0.10-alpha, and no one should
8119 be using the OpenSSL one. Part of ticket 15652.
8120 - Remove the 'tor_strclear()' function; use memwipe() instead.
8121 Closes ticket 14922.
8122 - Remove the code that would try to aggressively flush controller
8123 connections while writing to them. This code was introduced in
8124 0.1.2.7-alpha, in order to keep output buffers from exceeding
8125 their limits. But there is no longer a maximum output buffer size,
8126 and flushing data in this way caused some undesirable recursions
8127 in our call graph. Closes ticket 16480.
8128 - The internal pure-C tor-fw-helper tool is now removed from the Tor
8129 distribution, in favor of the pure-Go clone available from
8130 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
8131 used by the C tor-fw-helper are not, in our opinion, very
8132 confidence- inspiring in their secure-programming techniques.
8133 Closes ticket 13338.
8136 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
8137 fingerprinting we now recommend pluggable transports; for forward-
8138 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
8139 - Remove the HidServDirectoryV2 option. Now all relays offer to
8140 store hidden service descriptors. Related to 16543.
8141 - Remove the VoteOnHidServDirectoriesV2 option, since all
8142 authorities have long set it to 1. Closes ticket 16543.
8143 - Remove the undocumented "--digests" command-line option. It
8144 complicated our build process, caused subtle build issues on
8145 multiple platforms, and is now redundant since we started
8146 including git version identifiers. Closes ticket 14742.
8147 - Tor no longer contains checks for ancient directory cache versions
8148 that didn't know about microdescriptors.
8149 - Tor no longer contains workarounds for stat files generated by
8150 super-old versions of Tor that didn't choose guards sensibly.
8153 - The test-network.sh script now supports performance testing.
8154 Requires corresponding chutney performance testing changes. Patch
8155 by "teor". Closes ticket 14175.
8156 - Add a new set of callgraph analysis scripts that use clang to
8157 produce a list of which Tor functions are reachable from which
8158 other Tor functions. We're planning to use these to help simplify
8159 our code structure by identifying illogical dependencies.
8160 - Add new 'test-full' and 'test-full-online' targets to run all
8161 tests, including integration tests with stem and chutney.
8162 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
8163 by-side in the same parent directory. Closes ticket 16903. Patch
8165 - Document use of coverity, clang static analyzer, and clang dynamic
8166 undefined behavior and address sanitizers in doc/HACKING. Include
8167 detailed usage instructions in the blacklist. Patch by "teor".
8168 Closes ticket 15817.
8169 - Make "bridges+hs" the default test network. This tests almost all
8170 tor functionality during make test-network, while allowing tests
8171 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
8172 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
8173 (chutney). Patches by "teor".
8174 - Make the test-workqueue test work on Windows by initializing the
8175 network before we begin.
8176 - New make target (make test-network-all) to run multiple applicable
8177 chutney test cases. Patch from Teor; closes 16953.
8178 - Now that OpenSSL has its own scrypt implementation, add an unit
8179 test that checks for interoperability between libscrypt_scrypt()
8180 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
8181 and rely on EVP_PBE_scrypt() whenever possible. Resolves
8183 - The link authentication protocol code now has extensive tests.
8184 - The relay descriptor signature testing code now has
8186 - The test_workqueue program now runs faster, and is enabled by
8187 default as a part of "make check".
8188 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
8189 functions in dns.c. Implements a portion of ticket 16831.
8190 - Use environment variables rather than autoconf substitutions to
8191 send variables from the build system to the test scripts. This
8192 change should be easier to maintain, and cause 'make distcheck' to
8193 work better than before. Fixes bug 17148.
8194 - When building Tor with testing coverage enabled, run Chutney tests
8195 (if any) using the 'tor-cov' coverage binary.
8196 - When running test-network or test-stem, check for the absence of
8197 stem/chutney before doing any build operations.
8198 - Add a test to verify that the compiler does not eliminate our
8199 memwipe() implementation. Closes ticket 15377.
8200 - Add make rule `check-changes` to verify the format of changes
8201 files. Closes ticket 15180.
8202 - Add unit tests for control_event_is_interesting(). Add a compile-
8203 time check that the number of events doesn't exceed the capacity
8204 of control_event_t.event_mask. Closes ticket 15431, checks for
8205 bugs similar to 13085. Patch by "teor".
8206 - Command-line argument tests moved to Stem. Resolves ticket 14806.
8207 - Integrate the ntor, backtrace, and zero-length keys tests into the
8208 automake test suite. Closes ticket 15344.
8209 - Remove assertions during builds to determine Tor's test coverage.
8210 We don't want to trigger these even in assertions, so including
8211 them artificially makes our branch coverage look worse than it is.
8212 This patch provides the new test-stem-full and coverage-html-full
8213 configure options. Implements ticket 15400.
8214 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
8215 explicitly manage consensus flags in testing networks. Patch by
8216 "robgjansen", modified by "teor". Implements part of ticket 14882.
8217 - Check for matching value in server response in ntor_ref.py. Fixes
8218 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
8220 - Set the severity correctly when testing
8221 get_interface_addresses_ifaddrs() and
8222 get_interface_addresses_win32(), so that the tests fail gracefully
8223 instead of triggering an assertion. Fixes bug 15759; bugfix on
8224 0.2.6.3-alpha. Reported by Nicolas Derive.
8226 Changes in version 0.2.6.10 - 2015-07-12
8227 Tor version 0.2.6.10 fixes some significant stability and hidden
8228 service client bugs, bulletproofs the cryptography init process, and
8229 fixes a bug when using the sandbox code with some older versions of
8230 Linux. Everyone running an older version, especially an older version
8231 of 0.2.6, should upgrade.
8233 o Major bugfixes (hidden service clients, stability):
8234 - Stop refusing to store updated hidden service descriptors on a
8235 client. This reverts commit 9407040c59218 (which indeed fixed bug
8236 14219, but introduced a major hidden service reachability
8237 regression detailed in bug 16381). This is a temporary fix since
8238 we can live with the minor issue in bug 14219 (it just results in
8239 some load on the network) but the regression of 16381 is too much
8240 of a setback. First-round fix for bug 16381; bugfix
8243 o Major bugfixes (stability):
8244 - Stop crashing with an assertion failure when parsing certain kinds
8245 of malformed or truncated microdescriptors. Fixes bug 16400;
8246 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
8247 by "cypherpunks_backup".
8248 - Stop random client-side assertion failures that could occur when
8249 connecting to a busy hidden service, or connecting to a hidden
8250 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
8253 o Minor features (geoip):
8254 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
8255 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
8257 o Minor bugfixes (crypto error-handling):
8258 - Check for failures from crypto_early_init, and refuse to continue.
8259 A previous typo meant that we could keep going with an
8260 uninitialized crypto library, and would have OpenSSL initialize
8261 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
8262 when implementing ticket 4900. Patch by "teor".
8264 o Minor bugfixes (Linux seccomp2 sandbox):
8265 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
8266 these when eventfd2() support is missing. Fixes bug 16363; bugfix
8267 on 0.2.6.3-alpha. Patch from "teor".
8270 Changes in version 0.2.6.9 - 2015-06-11
8271 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
8272 requirements for receiving an HSDir flag, and addresses some other small
8273 bugs in the systemd and sandbox code. Clients using circuit isolation
8274 should upgrade; all directory authorities should upgrade.
8276 o Major bugfixes (client-side privacy):
8277 - Properly separate out each SOCKSPort when applying stream
8278 isolation. The error occurred because each port's session group was
8279 being overwritten by a default value when the listener connection
8280 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
8283 o Minor feature (directory authorities, security):
8284 - The HSDir flag given by authorities now requires the Stable flag.
8285 For the current network, this results in going from 2887 to 2806
8286 HSDirs. Also, it makes it harder for an attacker to launch a sybil
8287 attack by raising the effort for a relay to become Stable which
8288 takes at the very least 7 days to do so and by keeping the 96
8289 hours uptime requirement for HSDir. Implements ticket 8243.
8291 o Minor bugfixes (compilation):
8292 - Build with --enable-systemd correctly when libsystemd is
8293 installed, but systemd is not. Fixes bug 16164; bugfix on
8294 0.2.6.3-alpha. Patch from Peter Palfrader.
8296 o Minor bugfixes (Linux seccomp2 sandbox):
8297 - Fix sandboxing to work when running as a relaymby renaming of
8298 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
8299 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
8300 - Allow systemd connections to work with the Linux seccomp2 sandbox
8301 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
8304 o Minor bugfixes (tests):
8305 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
8306 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
8309 Changes in version 0.2.6.8 - 2015-05-21
8310 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
8311 fixes an authority-side bug in assigning the HSDir flag. All directory
8312 authorities should upgrade.
8314 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
8315 - Revert commit that made directory authorities assign the HSDir
8316 flag to relays without a DirPort; this was bad because such relays
8317 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
8320 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
8321 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8322 a client authorized hidden service. Fixes bug 15823; bugfix
8325 o Minor features (geoip):
8326 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
8327 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
8331 Changes in version 0.2.6.7 - 2015-04-06
8332 Tor 0.2.6.7 fixes two security issues that could be used by an
8333 attacker to crash hidden services, or crash clients visiting hidden
8334 services. Hidden services should upgrade as soon as possible; clients
8335 should upgrade whenever packages become available.
8337 This release also contains two simple improvements to make hidden
8338 services a bit less vulnerable to denial-of-service attacks.
8340 o Major bugfixes (security, hidden service):
8341 - Fix an issue that would allow a malicious client to trigger an
8342 assertion failure and halt a hidden service. Fixes bug 15600;
8343 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
8344 - Fix a bug that could cause a client to crash with an assertion
8345 failure when parsing a malformed hidden service descriptor. Fixes
8346 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
8348 o Minor features (DoS-resistance, hidden service):
8349 - Introduction points no longer allow multiple INTRODUCE1 cells to
8350 arrive on the same circuit. This should make it more expensive for
8351 attackers to overwhelm hidden services with introductions.
8352 Resolves ticket 15515.
8353 - Decrease the amount of reattempts that a hidden service performs
8354 when its rendezvous circuits fail. This reduces the computational
8355 cost for running a hidden service under heavy load. Resolves
8359 Changes in version 0.2.5.12 - 2015-04-06
8360 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
8361 could be used by an attacker to crash hidden services, or crash clients
8362 visiting hidden services. Hidden services should upgrade as soon as
8363 possible; clients should upgrade whenever packages become available.
8365 This release also backports a simple improvement to make hidden
8366 services a bit less vulnerable to denial-of-service attacks.
8368 o Major bugfixes (security, hidden service):
8369 - Fix an issue that would allow a malicious client to trigger an
8370 assertion failure and halt a hidden service. Fixes bug 15600;
8371 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
8372 - Fix a bug that could cause a client to crash with an assertion
8373 failure when parsing a malformed hidden service descriptor. Fixes
8374 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
8376 o Minor features (DoS-resistance, hidden service):
8377 - Introduction points no longer allow multiple INTRODUCE1 cells to
8378 arrive on the same circuit. This should make it more expensive for
8379 attackers to overwhelm hidden services with introductions.
8380 Resolves ticket 15515.
8383 Changes in version 0.2.4.27 - 2015-04-06
8384 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
8385 could be used by an attacker to crash hidden services, or crash clients
8386 visiting hidden services. Hidden services should upgrade as soon as
8387 possible; clients should upgrade whenever packages become available.
8389 This release also backports a simple improvement to make hidden
8390 services a bit less vulnerable to denial-of-service attacks.
8392 o Major bugfixes (security, hidden service):
8393 - Fix an issue that would allow a malicious client to trigger an
8394 assertion failure and halt a hidden service. Fixes bug 15600;
8395 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
8396 - Fix a bug that could cause a client to crash with an assertion
8397 failure when parsing a malformed hidden service descriptor. Fixes
8398 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
8400 o Minor features (DoS-resistance, hidden service):
8401 - Introduction points no longer allow multiple INTRODUCE1 cells to
8402 arrive on the same circuit. This should make it more expensive for
8403 attackers to overwhelm hidden services with introductions.
8404 Resolves ticket 15515.
8407 Changes in version 0.2.6.6 - 2015-03-24
8408 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
8410 It adds numerous safety, security, correctness, and performance
8411 improvements. Client programs can be configured to use more kinds of
8412 sockets, AutomapHosts works better, the multithreading backend is
8413 improved, cell transmission is refactored, test coverage is much
8414 higher, more denial-of-service attacks are handled, guard selection is
8415 improved to handle long-term guards better, pluggable transports
8416 should work a bit better, and some annoying hidden service performance
8417 bugs should be addressed.
8419 o New compiler and system requirements:
8420 - Tor 0.2.6.x requires that your compiler support more of the C99
8421 language standard than before. The 'configure' script now detects
8422 whether your compiler supports C99 mid-block declarations and
8423 designated initializers. If it does not, Tor will not compile.
8425 We may revisit this requirement if it turns out that a significant
8426 number of people need to build Tor with compilers that don't
8427 bother implementing a 15-year-old standard. Closes ticket 13233.
8428 - Tor no longer supports systems without threading support. When we
8429 began working on Tor, there were several systems that didn't have
8430 threads, or where the thread support wasn't able to run the
8431 threads of a single process on multiple CPUs. That no longer
8432 holds: every system where Tor needs to run well now has threading
8433 support. Resolves ticket 12439.
8435 o Deprecated versions and removed support:
8436 - Tor relays older than 0.2.4.18-rc are no longer allowed to
8437 advertise themselves on the network. Closes ticket 13555.
8438 - Tor clients no longer support connecting to hidden services
8439 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
8440 option has been removed. (There shouldn't be any hidden services
8441 running these versions on the network.) Closes ticket 7803.
8443 o Directory authority changes:
8444 - The directory authority Faravahar has a new IP address. This
8445 closes ticket 14487.
8446 - Remove turtles as a directory authority.
8447 - Add longclaw as a new (v3) directory authority. This implements
8448 ticket 13296. This keeps the directory authority count at 9.
8450 o Major features (bridges):
8451 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
8452 transports if they are configured via the "TOR_PT_PROXY"
8453 environment variable. Implements proposal 232. Resolves
8456 o Major features (changed defaults):
8457 - Prevent relay operators from unintentionally running exits: When a
8458 relay is configured as an exit node, we now warn the user unless
8459 the "ExitRelay" option is set to 1. We warn even more loudly if
8460 the relay is configured with the default exit policy, since this
8461 can indicate accidental misconfiguration. Setting "ExitRelay 0"
8462 stops Tor from running as an exit relay. Closes ticket 10067.
8464 o Major features (client performance, hidden services):
8465 - Allow clients to use optimistic data when connecting to a hidden
8466 service, which should remove a round-trip from hidden service
8467 initialization. See proposal 181 for details. Implements
8470 o Major features (directory system):
8471 - Upon receiving an unparseable directory object, if its digest
8472 matches what we expected, then don't try to download it again.
8473 Previously, when we got a descriptor we didn't like, we would keep
8474 trying to download it over and over. Closes ticket 11243.
8475 - When downloading server- or microdescriptors from a directory
8476 server, we no longer launch multiple simultaneous requests to the
8477 same server. This reduces load on the directory servers,
8478 especially when directory guards are in use. Closes ticket 9969.
8479 - When downloading server- or microdescriptors over a tunneled
8480 connection, do not limit the length of our requests to what the
8481 Squid proxy is willing to handle. Part of ticket 9969.
8482 - Authorities can now vote on the correct digests and latest
8483 versions for different software packages. This allows packages
8484 that include Tor to use the Tor authority system as a way to get
8485 notified of updates and their correct digests. Implements proposal
8486 227. Closes ticket 10395.
8488 o Major features (guards):
8489 - Introduce the Guardfraction feature to improves load balancing on
8490 guard nodes. Specifically, it aims to reduce the traffic gap that
8491 guard nodes experience when they first get the Guard flag. This is
8492 a required step if we want to increase the guard lifetime to 9
8493 months or greater. Closes ticket 9321.
8495 o Major features (hidden services):
8496 - Make HS port scanning more difficult by immediately closing the
8497 circuit when a user attempts to connect to a nonexistent port.
8498 Closes ticket 13667.
8499 - Add a HiddenServiceStatistics option that allows Tor relays to
8500 gather and publish statistics about the overall size and volume of
8501 hidden service usage. Specifically, when this option is turned on,
8502 an HSDir will publish an approximate number of hidden services
8503 that have published descriptors to it the past 24 hours. Also, if
8504 a relay has acted as a hidden service rendezvous point, it will
8505 publish the approximate amount of rendezvous cells it has relayed
8506 the past 24 hours. The statistics themselves are obfuscated so
8507 that the exact values cannot be derived. For more details see
8508 proposal 238, "Better hidden service stats from Tor relays". This
8509 feature is currently disabled by default. Implements feature 13192.
8511 o Major features (performance):
8512 - Make the CPU worker implementation more efficient by avoiding the
8513 kernel and lengthening pipelines. The original implementation used
8514 sockets to transfer data from the main thread to the workers, and
8515 didn't allow any thread to be assigned more than a single piece of
8516 work at once. The new implementation avoids communications
8517 overhead by making requests in shared memory, avoiding kernel IO
8518 where possible, and keeping more requests in flight at once.
8519 Implements ticket 9682.
8521 o Major features (relay):
8522 - Raise the minimum acceptable configured bandwidth rate for bridges
8523 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
8524 20 KiB/sec.) Closes ticket 13822.
8525 - Complete revision of the code that relays use to decide which cell
8526 to send next. Formerly, we selected the best circuit to write on
8527 each channel, but we didn't select among channels in any
8528 sophisticated way. Now, we choose the best circuits globally from
8529 among those whose channels are ready to deliver traffic.
8531 This patch implements a new inter-cmux comparison API, a global
8532 high/low watermark mechanism and a global scheduler loop for
8533 transmission prioritization across all channels as well as among
8534 circuits on one channel. This schedule is currently tuned to
8535 (tolerantly) avoid making changes in network performance, but it
8536 should form the basis for major circuit performance increases in
8537 the future. Code by Andrea; tuning by Rob Jansen; implements
8540 o Major features (sample torrc):
8541 - Add a new, infrequently-changed "torrc.minimal". This file is
8542 similar to torrc.sample, but it will change as infrequently as
8543 possible, for the benefit of users whose systems prompt them for
8544 intervention whenever a default configuration file is changed.
8545 Making this change allows us to update torrc.sample to be a more
8546 generally useful "sample torrc".
8548 o Major features (security, unix domain sockets):
8549 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
8550 applications can reach Tor without having to create AF_INET or
8551 AF_INET6 sockets, meaning they can completely disable their
8552 ability to make non-Tor network connections. To create a socket of
8553 this type, use "SocksPort unix:/path/to/socket". Implements
8555 - Support mapping hidden service virtual ports to AF_UNIX sockets.
8556 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
8557 Implements ticket 11485.
8559 o Major bugfixes (client, automap):
8560 - Repair automapping with IPv6 addresses. This automapping should
8561 have worked previously, but one piece of debugging code that we
8562 inserted to detect a regression actually caused the regression to
8563 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
8564 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
8567 o Major bugfixes (crash, OSX, security):
8568 - Fix a remote denial-of-service opportunity caused by a bug in
8569 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
8572 o Major bugfixes (directory authorities):
8573 - Do not assign the HSDir flag to relays if they are not Valid, or
8574 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
8576 o Major bugfixes (directory bandwidth performance):
8577 - Don't flush the zlib buffer aggressively when compressing
8578 directory information for clients. This should save about 7% of
8579 the bandwidth currently used for compressed descriptors and
8580 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
8582 o Major bugfixes (exit node stability):
8583 - Fix an assertion failure that could occur under high DNS load.
8584 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8585 diagnosed and fixed by "cypherpunks".
8587 o Major bugfixes (FreeBSD IPFW transparent proxy):
8588 - Fix address detection with FreeBSD transparent proxies, when
8589 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
8592 o Major bugfixes (hidden services):
8593 - When closing an introduction circuit that was opened in parallel
8594 with others, don't mark the introduction point as unreachable.
8595 Previously, the first successful connection to an introduction
8596 point would make the other introduction points get marked as
8597 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
8599 o Major bugfixes (Linux seccomp2 sandbox):
8600 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
8601 crash during attempts to call wait4. Fixes bug 15088; bugfix on
8602 0.2.5.1-alpha. Patch from "sanic".
8604 o Major bugfixes (mixed relay-client operation):
8605 - When running as a relay and client at the same time (not
8606 recommended), if we decide not to use a new guard because we want
8607 to retry older guards, only close the locally-originating circuits
8608 passing through that guard. Previously we would close all the
8609 circuits through that guard. Fixes bug 9819; bugfix on
8610 0.2.1.1-alpha. Reported by "skruffy".
8612 o Major bugfixes (pluggable transports):
8613 - Initialize the extended OR Port authentication cookie before
8614 launching pluggable transports. This prevents a race condition
8615 that occurred when server-side pluggable transports would cache the
8616 authentication cookie before it has been (re)generated. Fixes bug
8617 15240; bugfix on 0.2.5.1-alpha.
8619 o Major bugfixes (relay, stability, possible security):
8620 - Fix a bug that could lead to a relay crashing with an assertion
8621 failure if a buffer of exactly the wrong layout is passed to
8622 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8623 0.2.0.10-alpha. Patch from "cypherpunks".
8624 - Do not assert if the 'data' pointer on a buffer is advanced to the
8625 very end of the buffer; log a BUG message instead. Only assert if
8626 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8628 o Minor features (build):
8629 - New --disable-system-torrc compile-time option to prevent Tor from
8630 looking for the system-wide torrc or torrc-defaults files.
8631 Resolves ticket 13037.
8633 o Minor features (client):
8634 - Clients are now willing to send optimistic data (before they
8635 receive a 'connected' cell) to relays of any version. (Relays
8636 without support for optimistic data are no longer supported on the
8637 Tor network.) Resolves ticket 13153.
8639 o Minor features (client):
8640 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
8641 is enabled, reject requests with IP addresses as hostnames.
8642 Resolves ticket 13315.
8644 o Minor features (controller):
8645 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
8646 write an unscheduled heartbeat message to the log. Implements
8648 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
8649 events so controllers can observe circuit isolation inputs. Closes
8651 - ControlPort now supports the unix:/path/to/socket syntax as an
8652 alternative to the ControlSocket option, for consistency with
8653 SocksPort and HiddenServicePort. Closes ticket 14451.
8654 - New "GETINFO bw-event-cache" to get information about recent
8655 bandwidth events. Closes ticket 14128. Useful for controllers to
8656 get recent bandwidth history after the fix for ticket 13988.
8657 - Messages about problems in the bootstrap process now include
8658 information about the server we were trying to connect to when we
8659 noticed the problem. Closes ticket 15006.
8661 o Minor features (Denial of service resistance):
8662 - Count the total number of bytes used storing hidden service
8663 descriptors against the value of MaxMemInQueues. If we're low on
8664 memory, and more than 20% of our memory is used holding hidden
8665 service descriptors, free them until no more than 10% of our
8666 memory holds hidden service descriptors. Free the least recently
8667 fetched descriptors first. Resolves ticket 13806.
8668 - When we have recently been under memory pressure (over 3/4 of
8669 MaxMemInQueues is allocated), then allocate smaller zlib objects
8670 for small requests. Closes ticket 11791.
8672 o Minor features (directory authorities):
8673 - Don't list relays with a bandwidth estimate of 0 in the consensus.
8674 Implements a feature proposed during discussion of bug 13000.
8675 - In tor-gencert, report an error if the user provides the same
8676 argument more than once.
8677 - If a directory authority can't find a best consensus method in the
8678 votes that it holds, it now falls back to its favorite consensus
8679 method. Previously, it fell back to method 1. Neither of these is
8680 likely to get enough signatures, but "fall back to favorite"
8681 doesn't require us to maintain support an obsolete consensus
8682 method. Implements part of proposal 215.
8684 o Minor features (geoip):
8685 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8686 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8689 o Minor features (guard nodes):
8690 - Reduce the time delay before saving guard status to disk from 10
8691 minutes to 30 seconds (or from one hour to 10 minutes if
8692 AvoidDiskWrites is set). Closes ticket 12485.
8694 o Minor features (heartbeat):
8695 - On relays, report how many connections we negotiated using each
8696 version of the Tor link protocols. This information will let us
8697 know if removing support for very old versions of the Tor
8698 protocols is harming the network. Closes ticket 15212.
8700 o Minor features (hidden service):
8701 - Make Sybil attacks against hidden services harder by changing the
8702 minimum time required to get the HSDir flag from 25 hours up to 96
8703 hours. Addresses ticket 14149.
8704 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
8705 services to disable the anti-scanning feature introduced in
8706 0.2.6.2-alpha. With this option not set, a connection to an
8707 unlisted port closes the circuit. With this option set, only a
8708 RELAY_DONE cell is sent. Closes ticket 14084.
8709 - When re-enabling the network, don't try to build introduction
8710 circuits until we have successfully built a circuit. This makes
8711 hidden services come up faster when the network is re-enabled.
8712 Patch from "akwizgran". Closes ticket 13447.
8713 - When we fail to retrieve a hidden service descriptor, send the
8714 controller an "HS_DESC FAILED" controller event. Implements
8716 - New HiddenServiceDirGroupReadable option to cause hidden service
8717 directories and hostname files to be created group-readable. Patch
8718 from "anon", David Stainton, and "meejah". Closes ticket 11291.
8720 o Minor features (interface):
8721 - Implement "-f -" command-line option to read torrc configuration
8722 from standard input, if you don't want to store the torrc file in
8723 the file system. Implements feature 13865.
8725 o Minor features (logging):
8726 - Add a count of unique clients to the bridge heartbeat message.
8727 Resolves ticket 6852.
8728 - Suppress "router info incompatible with extra info" message when
8729 reading extrainfo documents from cache. (This message got loud
8730 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
8732 - Elevate hidden service authorized-client message from DEBUG to
8733 INFO. Closes ticket 14015.
8734 - On Unix-like systems, you can now use named pipes as the target of
8735 the Log option, and other options that try to append to files.
8736 Closes ticket 12061. Patch from "carlo von lynX".
8737 - When opening a log file at startup, send it every log message that
8738 we generated between startup and opening it. Previously, log
8739 messages that were generated before opening the log file were only
8740 logged to stdout. Closes ticket 6938.
8741 - Add a TruncateLogFile option to overwrite logs instead of
8742 appending to them. Closes ticket 5583.
8743 - Quiet some log messages in the heartbeat and at startup. Closes
8746 o Minor features (portability, Solaris):
8747 - Threads are no longer disabled by default on Solaris; we believe
8748 that the versions of Solaris with broken threading support are all
8749 obsolete by now. Resolves ticket 9495.
8751 o Minor features (relay):
8752 - Re-check our address after we detect a changed IP address from
8753 getsockname(). This ensures that the controller command "GETINFO
8754 address" will report the correct value. Resolves ticket 11582.
8756 - A new AccountingRule option lets Relays set whether they'd like
8757 AccountingMax to be applied separately to inbound and outbound
8758 traffic, or applied to the sum of inbound and outbound traffic.
8759 Resolves ticket 961. Patch by "chobe".
8760 - When identity keypair is generated for first time, log a
8761 congratulatory message that links to the new relay lifecycle
8762 document. Implements feature 10427.
8764 o Minor features (security, memory wiping):
8765 - Ensure we securely wipe keys from memory after
8766 crypto_digest_get_digest and init_curve25519_keypair_from_file
8767 have finished using them. Resolves ticket 13477.
8769 o Minor features (security, out-of-memory handling):
8770 - When handling an out-of-memory condition, allocate less memory for
8771 temporary data structures. Fixes issue 10115.
8772 - When handling an out-of-memory condition, consider more types of
8773 buffers, including those on directory connections, and zlib
8774 buffers. Resolves ticket 11792.
8776 o Minor features (stability):
8777 - Add assertions in our hash-table iteration code to check for
8778 corrupted values that could cause infinite loops. Closes
8781 o Minor features (systemd):
8782 - Various improvements and modernizations in systemd hardening
8783 support. Closes ticket 13805. Patch from Craig Andrews.
8784 - Where supported, when running with systemd, report successful
8785 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
8786 - When running with systemd, support systemd watchdog messages. Part
8787 of ticket 11016. Patch by Michael Scherer.
8789 o Minor features (testing networks):
8790 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
8791 the "Exit" flag regardless of their uptime, bandwidth, or exit
8792 policy. TestingTorNetwork must be set for this option to have any
8793 effect. Previously, authorities would take up to 35 minutes to
8794 give nodes the Exit flag in a test network. Partially implements
8796 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
8797 and the default on a testing network to 2 minutes. Drop the
8798 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
8799 keep the default on a testing network at 30 seconds. This reduces
8800 HS bootstrap time to around 25 seconds. Also, change the default
8801 time in test-network.sh to match. Closes ticket 13401. Patch
8803 - Create TestingDirAuthVoteHSDir to correspond to
8804 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
8805 HSDir flag for the listed relays regardless of uptime or ORPort
8806 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
8807 Partial implementation for ticket 14067. Patch by "teor".
8809 o Minor features (tor2web mode):
8810 - Introduce the config option Tor2webRendezvousPoints, which allows
8811 clients in Tor2webMode to select a specific Rendezvous Point to be
8812 used in HS circuits. This might allow better performance for
8813 Tor2Web nodes. Implements ticket 12844.
8815 o Minor features (transparent proxy):
8816 - Update the transparent proxy option checks to allow for both ipfw
8817 and pf on OS X. Closes ticket 14002.
8818 - Use the correct option when using IPv6 with transparent proxy
8819 support on Linux. Resolves 13808. Patch by Francisco Blas
8822 o Minor features (validation):
8823 - Check all date/time values passed to tor_timegm and
8824 parse_rfc1123_time for validity, taking leap years into account.
8825 Improves HTTP header validation. Implemented with bug 13476.
8826 - In correct_tm(), limit the range of values returned by system
8827 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
8828 This means we don't have to deal with negative or too large dates,
8829 even if a clock is wrong. Otherwise we might fail to read a file
8830 written by us which includes such a date. Fixes bug 13476.
8831 - Stop allowing invalid address patterns like "*/24" that contain
8832 both a wildcard address and a bit prefix length. This affects all
8833 our address-range parsing code. Fixes bug 7484; bugfix
8836 o Minor bugfixes (bridge clients):
8837 - When configured to use a bridge without an identity digest (not
8838 recommended), avoid launching an extra channel to it when
8839 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
8841 o Minor bugfixes (bridges):
8842 - When DisableNetwork is set, do not launch pluggable transport
8843 plugins, and if any are running, terminate them. Fixes bug 13213;
8844 bugfix on 0.2.3.6-alpha.
8846 o Minor bugfixes (C correctness):
8847 - Fix several instances of possible integer overflow/underflow/NaN.
8848 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
8850 - In circuit_build_times_calculate_timeout() in circuitstats.c,
8851 avoid dividing by zero in the pareto calculations. This traps
8852 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
8854 - Fix an integer overflow in format_time_interval(). Fixes bug
8855 13393; bugfix on 0.2.0.10-alpha.
8856 - Set the correct day of year value when the system's localtime(_r)
8857 or gmtime(_r) functions fail to set struct tm. Not externally
8858 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
8859 - Avoid unlikely signed integer overflow in tor_timegm on systems
8860 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
8862 o Minor bugfixes (certificate handling):
8863 - If an authority operator accidentally makes a signing certificate
8864 with a future publication time, do not discard its real signing
8865 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
8866 - Remove any old authority certificates that have been superseded
8867 for at least two days. Previously, we would keep superseded
8868 certificates until they expired, if they were published close in
8869 time to the certificate that superseded them. Fixes bug 11454;
8870 bugfix on 0.2.1.8-alpha.
8872 o Minor bugfixes (client):
8873 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
8874 BadExit flag are not considered worthy candidates. Fixes bug
8875 13066; bugfix on 0.1.2.3-alpha.
8876 - Use the consensus schedule for downloading consensuses, and not
8877 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
8878 - Handle unsupported or malformed SOCKS5 requests properly by
8879 responding with the appropriate error message before closing the
8880 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
8882 o Minor bugfixes (client, automapping):
8883 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
8884 no value follows the option. Fixes bug 14142; bugfix on
8885 0.2.4.7-alpha. Patch by "teor".
8886 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
8887 14195; bugfix on 0.1.0.1-rc.
8888 - Prevent changes to other options from removing the wildcard value
8889 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
8891 - Allow MapAddress and AutomapHostsOnResolve to work together when
8892 an address is mapped into another address type (like .onion) that
8893 must be automapped at resolve time. Fixes bug 7555; bugfix
8896 o Minor bugfixes (client, bridges):
8897 - When we are using bridges and we had a network connectivity
8898 problem, only retry connecting to our currently configured
8899 bridges, not all bridges we know about and remember using. Fixes
8900 bug 14216; bugfix on 0.2.2.17-alpha.
8902 o Minor bugfixes (client, DNS):
8903 - Report the correct cached DNS expiration times on SOCKS port or in
8904 DNS replies. Previously, we would report everything as "never
8905 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
8906 - Avoid a small memory leak when we find a cached answer for a
8907 reverse DNS lookup in a client-side DNS cache. (Remember, client-
8908 side DNS caching is off by default, and is not recommended.) Fixes
8909 bug 14259; bugfix on 0.2.0.1-alpha.
8911 o Minor bugfixes (client, IPv6):
8912 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
8913 flag is not set; and not because the NoIPv4Traffic flag was set.
8914 Previously we'd looked at the NoIPv4Traffic flag for both types of
8915 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
8917 o Minor bugfixes (client, microdescriptors):
8918 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
8919 computing which microdescriptors to download. This keeps us from
8920 erroneous download behavior if two microdescriptor digests ever
8921 have the same first 160 bits. Fixes part of bug 13399; bugfix
8923 - Reset a router's status if its microdescriptor digest changes,
8924 even if the first 160 bits remain the same. Fixes part of bug
8925 13399; bugfix on 0.2.3.1-alpha.
8927 o Minor bugfixes (client, torrc):
8928 - Stop modifying the value of our DirReqStatistics torrc option just
8929 because we're not a bridge or relay. This bug was causing Tor
8930 Browser users to write "DirReqStatistics 0" in their torrc files
8931 as if they had chosen to change the config. Fixes bug 4244; bugfix
8933 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
8934 that our options have changed every time we SIGHUP. Fixes bug
8935 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
8937 o Minor bugfixes (compilation):
8938 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
8940 - Silence clang warnings under --enable-expensive-hardening,
8941 including implicit truncation of 64 bit values to 32 bit, const
8942 char assignment to self, tautological compare, and additional
8943 parentheses around equality tests. Fixes bug 13577; bugfix
8945 - Fix a clang warning about checking whether an address in the
8946 middle of a structure is NULL. Fixes bug 14001; bugfix
8948 - The address of an array in the middle of a structure will always
8949 be non-NULL. clang recognises this and complains. Disable the
8950 tautologous and redundant check to silence this warning. Fixes bug
8951 14001; bugfix on 0.2.1.2-alpha.
8952 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
8953 Addresses ticket 14188.
8954 - Build without warnings with the stock OpenSSL srtp.h header, which
8955 has a duplicate declaration of SSL_get_selected_srtp_profile().
8956 Fixes bug 14220; this is OpenSSL's bug, not ours.
8957 - Do not compile any code related to Tor2Web mode when Tor2Web mode
8958 is not enabled at compile time. Previously, this code was included
8959 in a disabled state. See discussion on ticket 12844.
8960 - Allow our configure script to build correctly with autoconf 2.62
8961 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
8962 - Improve the error message from ./configure to make it clear that
8963 when asciidoc has not been found, the user will have to either add
8964 --disable-asciidoc argument or install asciidoc. Resolves
8967 o Minor bugfixes (controller):
8968 - Report "down" in response to the "GETINFO entry-guards" command
8969 when relays are down with an unreachable_since value. Previously,
8970 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
8971 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
8972 14116; bugfix on 0.2.2.9-alpha.
8974 o Minor bugfixes (controller):
8975 - Return an error when the second or later arguments of the
8976 "setevents" controller command are invalid events. Previously we
8977 would return success while silently skipping invalid events. Fixes
8978 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
8980 o Minor bugfixes (directory authority):
8981 - Allow directory authorities to fetch more data from one another if
8982 they find themselves missing lots of votes. Previously, they had
8983 been bumping against the 10 MB queued data limit. Fixes bug 14261;
8984 bugfix on 0.1.2.5-alpha.
8985 - Do not attempt to download extrainfo documents which we will be
8986 unable to validate with a matching server descriptor. Fixes bug
8987 13762; bugfix on 0.2.0.1-alpha.
8988 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
8989 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
8990 - Enlarge the buffer to read bwauth generated files to avoid an
8991 issue when parsing the file in dirserv_read_measured_bandwidths().
8992 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
8993 - When running as a v3 directory authority, advertise that you serve
8994 extra-info documents so that clients who want them can find them
8995 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8997 o Minor bugfixes (directory system):
8998 - Always believe that v3 directory authorities serve extra-info
8999 documents, whether they advertise "caches-extra-info" or not.
9000 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
9001 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
9002 Previously, directories offering BRIDGE_DIRINFO and some other
9003 flag (i.e. microdescriptors or extrainfo) would be ignored when
9004 looking for bridges. Partially fixes bug 13163; bugfix
9007 o Minor bugfixes (file handling):
9008 - Stop failing when key files are zero-length. Instead, generate new
9009 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
9010 on all versions of Tor. Patch by "teor".
9011 - Stop generating a fresh .old RSA onion key file when the .old file
9012 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
9013 - Avoid overwriting .old key files with empty key files.
9014 - Skip loading zero-length extrainfo store, router store, stats,
9015 state, and key files.
9016 - Avoid crashing when trying to reload a torrc specified as a
9017 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
9020 o Minor bugfixes (hidden services):
9021 - Close the introduction circuit when we have no more usable intro
9022 points, instead of waiting for it to time out. This also ensures
9023 that no follow-up HS descriptor fetch is triggered when the
9024 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
9025 - When fetching a hidden service descriptor for a down service that
9026 was recently up, do not keep refetching until we try the same
9027 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
9028 - Correctly send a controller event when we find that a rendezvous
9029 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
9030 - Pre-check directory permissions for new hidden-services to avoid
9031 at least one case of "Bug: Acting on config options left us in a
9032 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
9033 - When fetching hidden service descriptors, we now check not only
9034 for whether we got the hidden service we had in mind, but also
9035 whether we got the particular descriptors we wanted. This prevents
9036 a class of inefficient but annoying DoS attacks by hidden service
9037 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
9040 o Minor bugfixes (Linux seccomp2 sandbox):
9041 - Make transparent proxy support work along with the seccomp2
9042 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
9043 by Francisco Blas Izquierdo Riera.
9044 - Fix a memory leak in tor-resolve when running with the sandbox
9045 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
9046 - Allow glibc fatal errors to be sent to stderr before Tor exits.
9047 Previously, glibc would try to write them to /dev/tty, and the
9048 sandbox would trap the call and make Tor exit prematurely. Fixes
9049 bug 14759; bugfix on 0.2.5.1-alpha.
9051 o Minor bugfixes (logging):
9052 - Avoid crashing when there are more log domains than entries in
9053 domain_list. Bugfix on 0.2.3.1-alpha.
9054 - Downgrade warnings about RSA signature failures to info log level.
9055 Emit a warning when an extra info document is found incompatible
9056 with a corresponding router descriptor. Fixes bug 9812; bugfix
9058 - Make connection_ap_handshake_attach_circuit() log the circuit ID
9059 correctly. Fixes bug 13701; bugfix on 0.0.6.
9061 o Minor bugfixes (networking):
9062 - Check for orconns and use connection_or_close_for_error() rather
9063 than connection_mark_for_close() directly in the getsockopt()
9064 failure case of connection_handle_write_impl(). Fixes bug 11302;
9065 bugfix on 0.2.4.4-alpha.
9067 o Minor bugfixes (parsing):
9068 - Stop accepting milliseconds (or other junk) at the end of
9069 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
9070 - Support two-number and three-number version numbers correctly, in
9071 case we change the Tor versioning system in the future. Fixes bug
9072 13661; bugfix on 0.0.8pre1.
9074 o Minor bugfixes (portability):
9075 - Fix the ioctl()-based network interface lookup code so that it
9076 will work on systems that have variable-length struct ifreq, for
9078 - Use the correct datatype in the SipHash-2-4 function to prevent
9079 compilers from assuming any sort of alignment. Fixes bug 15436;
9080 bugfix on 0.2.5.3-alpha.
9082 o Minor bugfixes (preventative security, C safety):
9083 - When reading a hexadecimal, base-32, or base-64 encoded value from
9084 a string, always overwrite the whole output buffer. This prevents
9085 some bugs where we would look at (but fortunately, not reveal)
9086 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
9088 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
9089 just the part that's used. This makes it harder for data leak bugs
9090 to occur in the event of other programming failures. Resolves
9093 o Minor bugfixes (relay):
9094 - When generating our family list, remove spaces from around the
9095 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
9096 - If our previous bandwidth estimate was 0 bytes, allow publishing a
9097 new relay descriptor immediately. Fixes bug 13000; bugfix
9100 o Minor bugfixes (shutdown):
9101 - When shutting down, always call event_del() on lingering read or
9102 write events before freeing them. Otherwise, we risk double-frees
9103 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
9106 o Minor bugfixes (small memory leaks):
9107 - Avoid leaking memory when using IPv6 virtual address mappings.
9108 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
9111 o Minor bugfixes (statistics):
9112 - Increase period over which bandwidth observations are aggregated
9113 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
9115 o Minor bugfixes (systemd support):
9116 - Run correctly under systemd with the RunAsDaemon option set. Fixes
9117 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
9118 - Inform the systemd supervisor about more changes in the Tor
9119 process status. Implements part of ticket 14141. Patch from
9122 o Minor bugfixes (testing networks):
9123 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
9124 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
9125 - Stop using the default authorities in networks which provide both
9126 AlternateDirAuthority and AlternateBridgeAuthority. Partially
9127 fixes bug 13163; bugfix on 0.2.0.13-alpha.
9129 o Minor bugfixes (testing networks, fast startup):
9130 - Allow Tor to build circuits using a consensus with no exits. If
9131 the consensus has no exits (typical of a bootstrapping test
9132 network), allow Tor to build circuits once enough descriptors have
9133 been downloaded. This assists in bootstrapping a testing Tor
9134 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
9136 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
9137 header to directory servers. This allows us to obtain consensuses
9138 promptly when the consensus interval is very short. This assists
9139 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
9140 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
9141 - Stop assuming that private addresses are local when checking
9142 reachability in a TestingTorNetwork. Instead, when testing, assume
9143 all OR connections are remote. (This is necessary due to many test
9144 scenarios running all relays on localhost.) This assists in
9145 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
9146 0.1.0.1-rc. Patch by "teor".
9147 - Avoid building exit circuits from a consensus with no exits. Now
9148 thanks to our fix for 13718, we accept a no-exit network as not
9149 wholly lost, but we need to remember not to try to build exit
9150 circuits on it. Closes ticket 13814; patch by "teor".
9151 - Stop requiring exits to have non-zero bandwithcapacity in a
9152 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
9153 ignore exit bandwidthcapacity. This assists in bootstrapping a
9154 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
9155 on 0.2.0.3-alpha. Patch by "teor".
9156 - Add "internal" to some bootstrap statuses when no exits are
9157 available. If the consensus does not contain Exits, Tor will only
9158 build internal circuits. In this case, relevant statuses will
9159 contain the word "internal" as indicated in the Tor control-
9160 spec.txt. When bootstrap completes, Tor will be ready to build
9161 internal circuits. If a future consensus contains Exits, exit
9162 circuits may become available. Fixes part of bug 13718; bugfix on
9163 0.2.4.10-alpha. Patch by "teor".
9164 - Decrease minimum consensus interval to 10 seconds when
9165 TestingTorNetwork is set, or 5 seconds for the first consensus.
9166 Fix assumptions throughout the code that assume larger intervals.
9167 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
9169 - Avoid excluding guards from path building in minimal test
9170 networks, when we're in a test network and excluding guards would
9171 exclude all relays. This typically occurs in incredibly small tor
9172 networks, and those using "TestingAuthVoteGuard *". Fixes part of
9173 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
9175 o Minor bugfixes (testing):
9176 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
9177 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
9178 - Stop spawn test failures due to a race condition between the
9179 SIGCHLD handler updating the process status, and the test reading
9180 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
9181 - Avoid passing an extra backslash when creating a temporary
9182 directory for running the unit tests on Windows. Fixes bug 12392;
9183 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
9185 o Minor bugfixes (TLS):
9186 - Check more thoroughly throughout the TLS code for possible
9187 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
9189 o Minor bugfixes (transparent proxy):
9190 - Use getsockname, not getsockopt, to retrieve the address for a
9191 TPROXY-redirected connection. Fixes bug 13796; bugfix
9194 o Minor bugfixes (windows):
9195 - Remove code to special-case handling of NTE_BAD_KEYSET when
9196 acquiring windows CryptoAPI context. This error can't actually
9197 occur for the parameters we're providing. Fixes bug 10816; bugfix
9200 o Minor bugfixes (zlib):
9201 - Avoid truncating a zlib stream when trying to finalize it with an
9202 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
9204 o Code simplification and refactoring:
9205 - Change the entry_is_live() function to take named bitfield
9206 elements instead of an unnamed list of booleans. Closes
9208 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
9209 Resolves ticket 12205.
9210 - Use calloc and reallocarray functions instead of multiply-
9211 then-malloc. This makes it less likely for us to fall victim to an
9212 integer overflow attack when allocating. Resolves ticket 12855.
9213 - Use the standard macro name SIZE_MAX, instead of our
9215 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
9216 functions which take them as arguments. Replace 0 with NO_DIRINFO
9217 in a function call for clarity. Seeks to prevent future issues
9219 - Avoid 4 null pointer errors under clang static analysis by using
9220 tor_assert() to prove that the pointers aren't null. Fixes
9222 - Rework the API of policies_parse_exit_policy() to use a bitmask to
9223 represent parsing options, instead of a confusing mess of
9224 booleans. Resolves ticket 8197.
9225 - Introduce a helper function to parse ExitPolicy in
9226 or_options_t structure.
9227 - Move fields related to isolating and configuring client ports into
9228 a shared structure. Previously, they were duplicated across
9229 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
9230 to copy them correctly had been the cause of at least one bug in
9231 the past. Closes ticket 8546.
9232 - Refactor the get_interface_addresses_raw() doom-function into
9233 multiple smaller and simpler subfunctions. Cover the resulting
9234 subfunctions with unit-tests. Fixes a significant portion of
9236 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
9237 only for version <= 0.2.2.24 which is now deprecated. Closes
9239 - Remove a test for a long-defunct broken version-one
9241 - Refactor main loop to extract the 'loop' part. This makes it
9242 easier to run Tor under Shadow. Closes ticket 15176.
9243 - Stop using can_complete_circuits as a global variable; access it
9244 with a function instead.
9245 - Avoid using operators directly as macro arguments: this lets us
9246 apply coccinelle transformations to our codebase more directly.
9247 Closes ticket 13172.
9248 - Combine the functions used to parse ClientTransportPlugin and
9249 ServerTransportPlugin into a single function. Closes ticket 6456.
9250 - Add inline functions and convenience macros for inspecting channel
9251 state. Refactor the code to use convenience macros instead of
9252 checking channel state directly. Fixes issue 7356.
9253 - Document all members of was_router_added_t and rename
9254 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
9255 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
9256 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
9257 constant instead of hardcoded value. Fixes issue 13840.
9258 - Refactor our generic strmap and digestmap types into a single
9259 implementation, so that we can add a new digest256map
9263 - Add a doc/TUNING document with tips for handling large numbers of
9264 TCP connections when running busy Tor relay. Update the warning
9265 message to point to this file when running out of sockets
9266 operating system is allowing to use simultaneously. Resolves
9268 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
9269 for writing the OpenBSD-specific tips. Resolves ticket 13702.
9270 - Make the tor-resolve documentation match its help string and its
9271 options. Resolves part of ticket 14325.
9272 - Log a more useful error message from tor-resolve when failing to
9273 look up a hidden service address. Resolves part of ticket 14325.
9274 - Document the bridge-authority-only 'networkstatus-bridges' file.
9275 Closes ticket 13713; patch from "tom".
9276 - Fix typo in PredictedPortsRelevanceTime option description in
9277 manpage. Resolves issue 13707.
9278 - Stop suggesting that users specify relays by nickname: it isn't a
9279 good idea. Also, properly cross-reference how to specify relays in
9280 all parts of manual documenting options that take a list of
9281 relays. Closes ticket 13381.
9282 - Clarify the HiddenServiceDir option description in manpage to make
9283 it clear that relative paths are taken with respect to the current
9284 working directory. Also clarify that this behavior is not
9285 guaranteed to remain indefinitely. Fixes issue 13913.
9287 o Distribution (systemd):
9288 - systemd unit file: only allow tor to write to /var/lib/tor and
9289 /var/log/tor. The rest of the filesystem is accessible for reading
9290 only. Patch by intrigeri; resolves ticket 12751.
9291 - systemd unit file: ensure that the process and all its children
9292 can never gain new privileges. Patch by intrigeri; resolves
9294 - systemd unit file: set up /var/run/tor as writable for the Tor
9295 service. Patch by intrigeri; resolves ticket 13196.
9297 o Downgraded warnings:
9298 - Don't warn when we've attempted to contact a relay using the wrong
9299 ntor onion key. Closes ticket 9635.
9302 - Remove some lingering dead code that once supported mempools.
9303 Mempools were disabled by default in 0.2.5, and removed entirely
9304 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
9307 o Removed features (directory authorities):
9308 - Remove code that prevented authorities from listing Tor relays
9309 affected by CVE-2011-2769 as guards. These relays are already
9310 rejected altogether due to the minimum version requirement of
9311 0.2.3.16-alpha. Closes ticket 13152.
9312 - The "AuthDirRejectUnlisted" option no longer has any effect, as
9313 the fingerprints file (approved-routers) has been deprecated.
9314 - Directory authorities do not support being Naming dirauths anymore.
9315 The "NamingAuthoritativeDir" config option is now obsolete.
9316 - Directory authorities do not support giving out the BadDirectory
9318 - Directory authorities no longer advertise or support consensus
9319 methods 1 through 12 inclusive. These consensus methods were
9320 obsolete and/or insecure: maintaining the ability to support them
9321 served no good purpose. Implements part of proposal 215; closes
9325 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
9326 longer silently accepted as an alias for "ExitNodes".
9327 - The --enable-mempool and --enable-buf-freelists options, which
9328 were originally created to work around bad malloc implementations,
9329 no longer exist. They were off-by-default in 0.2.5. Closes
9331 - We no longer remind the user about configuration options that have
9332 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
9333 - Remove our old, non-weighted bandwidth-based node selection code.
9334 Previously, we used it as a fallback when we couldn't perform
9335 weighted bandwidth-based node selection. But that would only
9336 happen in the cases where we had no consensus, or when we had a
9337 consensus generated by buggy or ancient directory authorities. In
9338 either case, it's better to use the more modern, better maintained
9339 algorithm, with reasonable defaults for the weights. Closes
9341 - Remove the --disable-curve25519 configure option. Relays and
9342 clients now are required to support curve25519 and the
9344 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
9345 used to be deprecated synonyms for "StrictNodes", are now marked
9346 obsolete. Resolves ticket 12226.
9347 - Clients don't understand the BadDirectory flag in the consensus
9348 anymore, and ignore it.
9350 o Removed platform support:
9351 - We no longer include special code to build on Windows CE; as far
9352 as we know, nobody has used Tor on Windows CE in a very long time.
9353 Closes ticket 11446.
9355 o Testing (test-network.sh):
9356 - Stop using "echo -n", as some shells' built-in echo doesn't
9357 support "-n". Instead, use "/bin/echo -n". Partially fixes
9359 - Stop an apparent test-network hang when used with make -j2. Fixes
9361 - Add a --delay option to test-network.sh, which configures the
9362 delay before the chutney network tests for data transmission.
9363 Partially implements ticket 13161.
9366 - Test that tor does not fail when key files are zero-length. Check
9367 that tor generates new keys, and overwrites the empty key files.
9368 - Test that tor generates new keys when keys are missing
9369 (existing behavior).
9370 - Test that tor does not overwrite key files that already contain
9371 data (existing behavior). Tests bug 13111. Patch by "teor".
9372 - New "make test-stem" target to run stem integration tests.
9373 Requires that the "STEM_SOURCE_DIR" environment variable be set.
9374 Closes ticket 14107.
9375 - Make the test_cmdline_args.py script work correctly on Windows.
9376 Patch from Gisle Vanem.
9377 - Move the slower unit tests into a new "./src/test/test-slow"
9378 binary that can be run independently of the other tests. Closes
9380 - New tests for many parts of channel, relay, and circuitmux
9381 functionality. Code by Andrea; part of 9262.
9382 - New tests for parse_transport_line(). Part of ticket 6456.
9383 - In the unit tests, use chgrp() to change the group of the unit
9384 test temporary directory to the current user, so that the sticky
9385 bit doesn't interfere with tests that check directory groups.
9387 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
9389 - Refactor the function that chooses guard nodes so that it can more
9390 easily be tested; write some tests for it.
9391 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
9392 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
9393 - Create unit tests for format_time_interval(). With bug 13393.
9394 - Add unit tests for tor_timegm signed overflow, tor_timegm and
9395 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
9396 tests (visible) fixes in bug 13476.
9397 - Add a "coverage-html" make target to generate HTML-visualized
9398 coverage results when building with --enable-coverage. (Requires
9399 lcov.) Patch from Kevin Murray.
9400 - Enable the backtrace handler (where supported) when running the
9402 - Revise all unit tests that used the legacy test_* macros to
9403 instead use the recommended tt_* macros. This patch was generated
9404 with coccinelle, to avoid manual errors. Closes ticket 13119.
9406 Changes in version 0.2.5.11 - 2015-03-17
9407 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
9409 It backports several bugfixes from the 0.2.6 branch, including a
9410 couple of medium-level security fixes for relays and exit nodes.
9411 It also updates the list of directory authorities.
9413 o Directory authority changes:
9414 - Remove turtles as a directory authority.
9415 - Add longclaw as a new (v3) directory authority. This implements
9416 ticket 13296. This keeps the directory authority count at 9.
9417 - The directory authority Faravahar has a new IP address. This
9418 closes ticket 14487.
9420 o Major bugfixes (crash, OSX, security):
9421 - Fix a remote denial-of-service opportunity caused by a bug in
9422 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
9425 o Major bugfixes (relay, stability, possible security):
9426 - Fix a bug that could lead to a relay crashing with an assertion
9427 failure if a buffer of exactly the wrong layout was passed to
9428 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
9429 0.2.0.10-alpha. Patch from 'cypherpunks'.
9430 - Do not assert if the 'data' pointer on a buffer is advanced to the
9431 very end of the buffer; log a BUG message instead. Only assert if
9432 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
9434 o Major bugfixes (exit node stability):
9435 - Fix an assertion failure that could occur under high DNS load.
9436 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
9437 diagnosed and fixed by "cypherpunks".
9439 o Major bugfixes (Linux seccomp2 sandbox):
9440 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
9441 crash during attempts to call wait4. Fixes bug 15088; bugfix on
9442 0.2.5.1-alpha. Patch from "sanic".
9444 o Minor features (controller):
9445 - New "GETINFO bw-event-cache" to get information about recent
9446 bandwidth events. Closes ticket 14128. Useful for controllers to
9447 get recent bandwidth history after the fix for ticket 13988.
9449 o Minor features (geoip):
9450 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
9451 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
9454 o Minor bugfixes (client, automapping):
9455 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
9456 no value follows the option. Fixes bug 14142; bugfix on
9457 0.2.4.7-alpha. Patch by "teor".
9458 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
9459 14195; bugfix on 0.1.0.1-rc.
9461 o Minor bugfixes (compilation):
9462 - Build without warnings with the stock OpenSSL srtp.h header, which
9463 has a duplicate declaration of SSL_get_selected_srtp_profile().
9464 Fixes bug 14220; this is OpenSSL's bug, not ours.
9466 o Minor bugfixes (directory authority):
9467 - Allow directory authorities to fetch more data from one another if
9468 they find themselves missing lots of votes. Previously, they had
9469 been bumping against the 10 MB queued data limit. Fixes bug 14261;
9470 bugfix on 0.1.2.5-alpha.
9471 - Enlarge the buffer to read bwauth generated files to avoid an
9472 issue when parsing the file in dirserv_read_measured_bandwidths().
9473 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
9475 o Minor bugfixes (statistics):
9476 - Increase period over which bandwidth observations are aggregated
9477 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
9479 o Minor bugfixes (preventative security, C safety):
9480 - When reading a hexadecimal, base-32, or base-64 encoded value from
9481 a string, always overwrite the whole output buffer. This prevents
9482 some bugs where we would look at (but fortunately, not reveal)
9483 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
9487 Changes in version 0.2.4.26 - 2015-03-17
9488 Tor 0.2.4.26 includes an updated list of directory authorities. It
9489 also backports a couple of stability and security bugfixes from 0.2.5
9492 o Directory authority changes:
9493 - Remove turtles as a directory authority.
9494 - Add longclaw as a new (v3) directory authority. This implements
9495 ticket 13296. This keeps the directory authority count at 9.
9496 - The directory authority Faravahar has a new IP address. This
9497 closes ticket 14487.
9499 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
9500 - Fix an assertion failure that could occur under high DNS load.
9501 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
9502 diagnosed and fixed by "cypherpunks".
9504 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
9505 - Fix a bug that could lead to a relay crashing with an assertion
9506 failure if a buffer of exactly the wrong layout was passed to
9507 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
9508 0.2.0.10-alpha. Patch from 'cypherpunks'.
9509 - Do not assert if the 'data' pointer on a buffer is advanced to the
9510 very end of the buffer; log a BUG message instead. Only assert if
9511 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
9513 o Minor features (geoip):
9514 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
9515 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
9518 Changes in version 0.2.5.10 - 2014-10-24
9519 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
9521 It adds several new security features, including improved
9522 denial-of-service resistance for relays, new compiler hardening
9523 options, and a system-call sandbox for hardened installations on Linux
9524 (requires seccomp2). The controller protocol has several new features,
9525 resolving IPv6 addresses should work better than before, and relays
9526 should be a little more CPU-efficient. We've added support for more
9527 OpenBSD and FreeBSD transparent proxy types. We've improved the build
9528 system and testing infrastructure to allow unit testing of more parts
9529 of the Tor codebase. Finally, we've addressed several nagging pluggable
9530 transport usability issues, and included numerous other small bugfixes
9531 and features mentioned below.
9533 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
9534 have accumulated many known flaws; everyone should upgrade.
9536 o Major features (security):
9537 - The ntor handshake is now on-by-default, no matter what the
9538 directory authorities recommend. Implements ticket 8561.
9539 - Make the "tor-gencert" tool used by directory authority operators
9540 create 2048-bit signing keys by default (rather than 1024-bit, since
9541 1024-bit is uncomfortably small these days). Addresses ticket 10324.
9542 - Warn about attempts to run hidden services and relays in the same
9543 process: that's probably not a good idea. Closes ticket 12908.
9544 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9545 today support TLS 1.0 or later, so we can safely turn off support
9546 for this old (and insecure) protocol. Fixes bug 13426.
9548 o Major features (relay security, DoS-resistance):
9549 - When deciding whether we have run out of memory and we need to
9550 close circuits, also consider memory allocated in buffers for
9551 streams attached to each circuit.
9553 This change, which extends an anti-DoS feature introduced in
9554 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
9555 better resist more memory-based DoS attacks than before. Since the
9556 MaxMemInCellQueues option now applies to all queues, it is renamed
9557 to MaxMemInQueues. This feature fixes bug 10169.
9558 - Avoid hash-flooding denial-of-service attacks by using the secure
9559 SipHash-2-4 hash function for our hashtables. Without this
9560 feature, an attacker could degrade performance of a targeted
9561 client or server by flooding their data structures with a large
9562 number of entries to be stored at the same hash table position,
9563 thereby slowing down the Tor instance. With this feature, hash
9564 table positions are derived from a randomized cryptographic key,
9565 and an attacker cannot predict which entries will collide. Closes
9567 - If you don't specify MaxMemInQueues yourself, Tor now tries to
9568 pick a good value based on your total system memory. Previously,
9569 the default was always 8 GB. You can still override the default by
9570 setting MaxMemInQueues yourself. Resolves ticket 11396.
9572 o Major features (bridges and pluggable transports):
9573 - Add support for passing arguments to managed pluggable transport
9574 proxies. Implements ticket 3594.
9575 - Bridges now track GeoIP information and the number of their users
9576 even when pluggable transports are in use, and report usage
9577 statistics in their extra-info descriptors. Resolves tickets 4773
9579 - Don't launch pluggable transport proxies if we don't have any
9580 bridges configured that would use them. Now we can list many
9581 pluggable transports, and Tor will dynamically start one when it
9582 hears a bridge address that needs it. Resolves ticket 5018.
9583 - The bridge directory authority now assigns status flags (Stable,
9584 Guard, etc) to bridges based on thresholds calculated over all
9585 Running bridges. Now bridgedb can finally make use of its features
9586 to e.g. include at least one Stable bridge in its answers. Fixes
9589 o Major features (controller):
9590 - Extend ORCONN controller event to include an "ID" parameter,
9591 and add four new controller event types CONN_BW, CIRC_BW,
9592 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
9593 The new events are emitted in private Tor networks only, with the
9594 goal of being able to better track performance and load during
9595 full-network simulations. Implements proposal 218 and ticket 7359.
9597 o Major features (relay performance):
9598 - Speed up server-side lookups of rendezvous and introduction point
9599 circuits by using hashtables instead of linear searches. These
9600 functions previously accounted between 3 and 7% of CPU usage on
9601 some busy relays. Resolves ticket 9841.
9602 - Avoid wasting CPU when extending a circuit over a channel that is
9603 nearly out of circuit IDs. Previously, we would do a linear scan
9604 over possible circuit IDs before finding one or deciding that we
9605 had exhausted our possibilities. Now, we try at most 64 random
9606 circuit IDs before deciding that we probably won't succeed. Fixes
9607 a possible root cause of ticket 11553.
9609 o Major features (seccomp2 sandbox, Linux only):
9610 - Use the seccomp2 syscall filtering facility on Linux to limit
9611 which system calls Tor can invoke. This is an experimental,
9612 Linux-only feature to provide defense-in-depth against unknown
9613 attacks. To try turning it on, set "Sandbox 1" in your torrc
9614 file. Please be ready to report bugs. We hope to add support
9615 for better sandboxing in the future, including more fine-grained
9616 filters, better division of responsibility, and support for more
9617 platforms. This work has been done by Cristian-Matei Toader for
9618 Google Summer of Code. Resolves tickets 11351 and 11465.
9620 o Major features (testing networks):
9621 - Make testing Tor networks bootstrap better: lower directory fetch
9622 retry schedules and maximum interval without directory requests,
9623 and raise maximum download tries. Implements ticket 6752.
9624 - Add make target 'test-network' to run tests on a Chutney network.
9625 Implements ticket 8530.
9627 o Major features (other):
9628 - On some platforms (currently: recent OSX versions, glibc-based
9629 platforms that support the ELF format, and a few other
9630 Unix-like operating systems), Tor can now dump stack traces
9631 when a crash occurs or an assertion fails. By default, traces
9632 are dumped to stderr (if possible) and to any logs that are
9633 reporting errors. Implements ticket 9299.
9635 o Deprecated versions:
9636 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
9637 attention for some while.
9639 o Major bugfixes (security, directory authorities):
9640 - Directory authorities now include a digest of each relay's
9641 identity key as a part of its microdescriptor.
9643 This is a workaround for bug 11743 (reported by "cypherpunks"),
9644 where Tor clients do not support receiving multiple
9645 microdescriptors with the same SHA256 digest in the same
9646 consensus. When clients receive a consensus like this, they only
9647 use one of the relays. Without this fix, a hostile relay could
9648 selectively disable some client use of target relays by
9649 constructing a router descriptor with a different identity and the
9650 same microdescriptor parameters and getting the authorities to
9651 list it in a microdescriptor consensus. This fix prevents an
9652 attacker from causing a microdescriptor collision, because the
9653 router's identity is not forgeable.
9655 o Major bugfixes (openssl bug workaround):
9656 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9657 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
9658 bug 13471. This is a workaround for an OpenSSL bug.
9660 o Major bugfixes (client):
9661 - Perform circuit cleanup operations even when circuit
9662 construction operations are disabled (because the network is
9663 disabled, or because there isn't enough directory information).
9664 Previously, when we were not building predictive circuits, we
9665 were not closing expired circuits either. Fixes bug 8387; bugfix on
9666 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
9667 became more strict about when we have "enough directory information
9670 o Major bugfixes (client, pluggable transports):
9671 - When managing pluggable transports, use OS notification facilities
9672 to learn if they have crashed, and don't attempt to kill any
9673 process that has already exited. Fixes bug 8746; bugfix
9676 o Major bugfixes (relay denial of service):
9677 - Instead of writing destroy cells directly to outgoing connection
9678 buffers, queue them and intersperse them with other outgoing cells.
9679 This can prevent a set of resource starvation conditions where too
9680 many pending destroy cells prevent data cells from actually getting
9681 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
9682 bugfix on 0.2.0.1-alpha.
9684 o Major bugfixes (relay):
9685 - Avoid queuing or sending destroy cells for circuit ID zero when we
9686 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
9687 Found and fixed by "cypherpunks".
9688 - Fix ORPort reachability detection on relays running behind a
9689 proxy, by correctly updating the "local" mark on the controlling
9690 channel when changing the address of an or_connection_t after the
9691 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
9692 - Use a direct dirport connection when uploading non-anonymous
9693 descriptors to the directory authorities. Previously, relays would
9694 incorrectly use tunnel connections under a fairly wide variety of
9695 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
9696 - When a circuit accidentally has the same circuit ID for its
9697 forward and reverse direction, correctly detect the direction of
9698 cells using that circuit. Previously, this bug made roughly one
9699 circuit in a million non-functional. Fixes bug 12195; this is a
9700 bugfix on every version of Tor.
9702 o Minor features (security):
9703 - New --enable-expensive-hardening option to enable security
9704 hardening options that consume nontrivial amounts of CPU and
9705 memory. Right now, this includes AddressSanitizer and UbSan, which
9706 are supported in newer versions of GCC and Clang. Closes ticket
9708 - Authorities now assign the Guard flag to the fastest 25% of the
9709 network (it used to be the fastest 50%). Also raise the consensus
9710 weight that guarantees the Guard flag from 250 to 2000. For the
9711 current network, this results in about 1100 guards, down from 2500.
9712 This step paves the way for moving the number of entry guards
9713 down to 1 (proposal 236) while still providing reasonable expected
9714 performance for most users. Implements ticket 12690.
9716 o Minor features (security, memory management):
9717 - Memory allocation tricks (mempools and buffer freelists) are now
9718 disabled by default. You can turn them back on with
9719 --enable-mempools and --enable-buf-freelists respectively. We're
9720 disabling these features because malloc performance is good enough
9721 on most platforms, and a similar feature in OpenSSL exacerbated
9722 exploitation of the Heartbleed attack. Resolves ticket 11476.
9724 o Minor features (bridge client):
9725 - Report a more useful failure message when we can't connect to a
9726 bridge because we don't have the right pluggable transport
9727 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
9729 o Minor features (bridge):
9730 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
9731 cookie file for the ExtORPort g+r by default.
9733 o Minor features (bridges, pluggable transports):
9734 - Bridges now write the SHA1 digest of their identity key
9735 fingerprint (that is, a hash of a hash of their public key) to
9736 notice-level logs, and to a new hashed-fingerprint file. This
9737 information will help bridge operators look up their bridge in
9738 Globe and similar tools. Resolves ticket 10884.
9739 - Improve the message that Tor displays when running as a bridge
9740 using pluggable transports without an Extended ORPort listener.
9741 Also, log the message in the log file too. Resolves ticket 11043.
9742 - Add threshold cutoffs to the networkstatus document created by
9743 the Bridge Authority. Fixes bug 1117.
9744 - On Windows, spawn background processes using the CREATE_NO_WINDOW
9745 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
9746 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
9747 Vidalia set this option for us.) Implements ticket 10297.
9749 o Minor features (build):
9750 - The configure script has a --disable-seccomp option to turn off
9751 support for libseccomp on systems that have it, in case it (or
9752 Tor's use of it) is broken. Resolves ticket 11628.
9753 - Assume that a user using ./configure --host wants to cross-compile,
9754 and give an error if we cannot find a properly named
9755 tool-chain. Add a --disable-tool-name-check option to proceed
9756 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
9757 - If we run ./configure and the compiler recognizes -fstack-protector
9758 but the linker rejects it, warn the user about a potentially missing
9759 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
9760 - Add support for `--library-versions` flag. Implements ticket 6384.
9761 - Return the "unexpected sendme" warnings to a warn severity, but make
9762 them rate limited, to help diagnose ticket 8093.
9763 - Detect a missing asciidoc, and warn the user about it, during
9764 configure rather than at build time. Fixes issue 6506. Patch from
9767 o Minor features (client):
9768 - Add a new option, PredictedPortsRelevanceTime, to control how long
9769 after having received a request to connect to a given port Tor
9770 will try to keep circuits ready in anticipation of future requests
9771 for that port. Patch from "unixninja92"; implements ticket 9176.
9773 o Minor features (config options and command line):
9774 - Add an --allow-missing-torrc commandline option that tells Tor to
9775 run even if the configuration file specified by -f is not available.
9776 Implements ticket 10060.
9777 - Add support for the TPROXY transparent proxying facility on Linux.
9778 See documentation for the new TransProxyType option for more
9779 details. Implementation by "thomo". Closes ticket 10582.
9781 o Minor features (config options):
9782 - Config (torrc) lines now handle fingerprints which are missing
9783 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
9784 - Support a --dump-config option to print some or all of the
9785 configured options. Mainly useful for debugging the command-line
9786 option parsing code. Helps resolve ticket 4647.
9787 - Raise awareness of safer logging: notify user of potentially
9788 unsafe config options, like logging more verbosely than severity
9789 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
9790 - Add a new configuration option TestingV3AuthVotingStartOffset
9791 that bootstraps a network faster by changing the timing for
9792 consensus votes. Addresses ticket 8532.
9793 - Add a new torrc option "ServerTransportOptions" that allows
9794 bridge operators to pass configuration parameters to their
9795 pluggable transports. Resolves ticket 8929.
9796 - The config (torrc) file now accepts bandwidth and space limits in
9797 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
9798 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
9801 o Minor features (controller):
9802 - Make the entire exit policy available from the control port via
9803 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
9805 - Because of the fix for ticket 11396, the real limit for memory
9806 usage may no longer match the configured MaxMemInQueues value. The
9807 real limit is now exposed via GETINFO limits/max-mem-in-queues.
9808 - Add a new "HS_DESC" controller event that reports activities
9809 related to hidden service descriptors. Resolves ticket 8510.
9810 - New "DROPGUARDS" controller command to forget all current entry
9811 guards. Not recommended for ordinary use, since replacing guards
9812 too frequently makes several attacks easier. Resolves ticket 9934;
9814 - Implement the TRANSPORT_LAUNCHED control port event that
9815 notifies controllers about new launched pluggable
9816 transports. Resolves ticket 5609.
9818 o Minor features (diagnostic):
9819 - When logging a warning because of bug 7164, additionally check the
9820 hash table for consistency (as proposed on ticket 11737). This may
9821 help diagnose bug 7164.
9822 - When we log a heartbeat, log how many one-hop circuits we have
9823 that are at least 30 minutes old, and log status information about
9824 a few of them. This is an attempt to track down bug 8387.
9825 - When encountering an unexpected CR while writing text to a file on
9826 Windows, log the name of the file. Should help diagnosing
9828 - Give more specific warnings when a client notices that an onion
9829 handshake has failed. Fixes ticket 9635.
9830 - Add significant new logging code to attempt to diagnose bug 12184,
9831 where relays seem to run out of available circuit IDs.
9832 - Improve the diagnostic log message for bug 8387 even further to
9833 try to improve our odds of figuring out why one-hop directory
9834 circuits sometimes do not get closed.
9835 - Add more log messages to diagnose bug 7164, which causes
9836 intermittent "microdesc_free() called but md was still referenced"
9837 warnings. We now include more information, to figure out why we
9838 might be cleaning a microdescriptor for being too old if it's
9839 still referenced by a live node_t object.
9840 - Log current accounting state (bytes sent and received + remaining
9841 time for the current accounting period) in the relay's heartbeat
9842 message. Implements ticket 5526; patch from Peter Retzlaff.
9844 o Minor features (geoip):
9845 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9848 o Minor features (interface):
9849 - Generate a warning if any ports are listed in the SocksPolicy,
9850 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
9851 AuthDirBadExit options. (These options only support address
9852 ranges.) Fixes part of ticket 11108.
9854 o Minor features (kernel API usage):
9855 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
9856 sockets in a single system call. Implements ticket 5129.
9858 o Minor features (log messages):
9859 - When ServerTransportPlugin is set on a bridge, Tor can write more
9860 useful statistics about bridge use in its extrainfo descriptors,
9861 but only if the Extended ORPort ("ExtORPort") is set too. Add a
9862 log message to inform the user in this case. Resolves ticket 9651.
9863 - When receiving a new controller connection, log the origin address.
9864 Resolves ticket 9698; patch from "sigpipe".
9865 - When logging OpenSSL engine status at startup, log the status of
9866 more engines. Fixes ticket 10043; patch from Joshua Datko.
9868 o Minor features (log verbosity):
9869 - Demote the message that we give when a flushing connection times
9870 out for too long from NOTICE to INFO. It was usually meaningless.
9871 Resolves ticket 5286.
9872 - Don't log so many notice-level bootstrapping messages at startup
9873 about downloading descriptors. Previously, we'd log a notice
9874 whenever we learned about more routers. Now, we only log a notice
9875 at every 5% of progress. Fixes bug 9963.
9876 - Warn less verbosely when receiving a malformed
9877 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
9879 o Minor features (performance):
9880 - If we're using the pure-C 32-bit curve25519_donna implementation
9881 of curve25519, build it with the -fomit-frame-pointer option to
9882 make it go faster on register-starved hosts. This improves our
9883 handshake performance by about 6% on i386 hosts without nacl.
9886 o Minor features (relay):
9887 - If a circuit timed out for at least 3 minutes, check if we have a
9888 new external IP address, and publish a new descriptor with the new
9889 IP address if it changed. Resolves ticket 2454.
9891 o Minor features (testing):
9892 - If Python is installed, "make check" now runs extra tests beyond
9893 the unit test scripts.
9894 - When bootstrapping a test network, sometimes very few relays get
9895 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
9896 specify a set of relays which should be voted Guard regardless of
9897 their uptime or bandwidth. Addresses ticket 9206.
9899 o Minor features (transparent proxy, *BSD):
9900 - Support FreeBSD's ipfw firewall interface for TransPort ports on
9901 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
9902 10267; patch from "yurivict".
9903 - Support OpenBSD's divert-to rules with the pf firewall for
9904 transparent proxy ports. To enable it, set "TransProxyType
9905 pf-divert". This allows Tor to run a TransPort transparent proxy
9906 port on OpenBSD 4.4 or later without root privileges. See the
9907 pf.conf(5) manual page for information on configuring pf to use
9908 divert-to rules. Closes ticket 10896; patch from Dana Koch.
9910 o Minor bugfixes (bridge client):
9911 - Stop accepting bridge lines containing hostnames. Doing so would
9912 cause clients to perform DNS requests on the hostnames, which was
9913 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
9915 o Minor bugfixes (bridges):
9916 - Avoid potential crashes or bad behavior when launching a
9917 server-side managed proxy with ORPort or ExtORPort temporarily
9918 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
9919 - Fix a bug where the first connection works to a bridge that uses a
9920 pluggable transport with client-side parameters, but we don't send
9921 the client-side parameters on subsequent connections. (We don't
9922 use any pluggable transports with client-side parameters yet,
9923 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
9924 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
9926 o Minor bugfixes (build, auxiliary programs):
9927 - Stop preprocessing the "torify" script with autoconf, since
9928 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
9930 - The tor-fw-helper program now follows the standard convention and
9931 exits with status code "0" on success. Fixes bug 9030; bugfix on
9932 0.2.3.1-alpha. Patch by Arlo Breault.
9933 - Corrected ./configure advice for what openssl dev package you should
9934 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
9936 o Minor bugfixes (client):
9937 - Avoid "Tried to open a socket with DisableNetwork set" warnings
9938 when starting a client with bridges configured and DisableNetwork
9939 set. (Tor launcher starts Tor with DisableNetwork set the first
9940 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
9941 - Improve the log message when we can't connect to a hidden service
9942 because all of the hidden service directory nodes hosting its
9943 descriptor are excluded. Improves on our fix for bug 10722, which
9944 was a bugfix on 0.2.0.10-alpha.
9945 - Raise a control port warning when we fail to connect to all of
9946 our bridges. Previously, we didn't inform the controller, and
9947 the bootstrap process would stall. Fixes bug 11069; bugfix on
9949 - Exit immediately when a process-owning controller exits.
9950 Previously, tor relays would wait for a little while after their
9951 controller exited, as if they had gotten an INT signal -- but this
9952 was problematic, since there was no feedback for the user. To do a
9953 clean shutdown, controllers should send an INT signal and give Tor
9954 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
9955 - Stop attempting to connect to bridges before our pluggable
9956 transports are configured (harmless but resulted in some erroneous
9957 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
9958 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
9959 generating incorrect SOCKS5 responses, and confusing client
9960 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
9962 o Minor bugfixes (client, DNSPort):
9963 - When using DNSPort, try to respond to AAAA requests with AAAA
9964 answers. Previously, we hadn't looked at the request type when
9965 deciding which answer type to prefer. Fixes bug 10468; bugfix on
9967 - When receiving a DNS query for an unsupported record type, reply
9968 with no answer rather than with a NOTIMPL error. This behavior
9969 isn't correct either, but it will break fewer client programs, we
9970 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
9973 o Minor bugfixes (client, logging during bootstrap):
9974 - Only report the first fatal bootstrap error on a given OR
9975 connection. This stops us from telling the controller bogus error
9976 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
9977 - Avoid generating spurious warnings when starting with
9978 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
9981 o Minor bugfixes (closing OR connections):
9982 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
9983 check if it's an or_connection_t and correctly call
9984 connection_or_close_for_error() rather than
9985 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
9987 - When closing all connections on setting DisableNetwork to 1, use
9988 connection_or_close_normally() rather than closing OR connections
9989 out from under the channel layer. Fixes bug 11306; bugfix on
9992 o Minor bugfixes (code correctness):
9993 - Previously we used two temporary files when writing descriptors to
9994 disk; now we only use one. Fixes bug 1376.
9995 - Remove an erroneous (but impossible and thus harmless) pointer
9996 comparison that would have allowed compilers to skip a bounds
9997 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
9998 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
9999 - Fix an always-true assertion in pluggable transports code so it
10000 actually checks what it was trying to check. Fixes bug 10046;
10001 bugfix on 0.2.3.9-alpha. Found by "dcb".
10003 o Minor bugfixes (command line):
10004 - Use a single command-line parser for parsing torrc options on the
10005 command line and for finding special command-line options to avoid
10006 inconsistent behavior for torrc option arguments that have the same
10007 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
10009 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
10010 9573; bugfix on 0.0.9pre5.
10012 o Minor bugfixes (compilation):
10013 - Compile correctly with builds and forks of OpenSSL (such as
10014 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
10015 0.2.1.1-alpha. Patch from "dhill".
10016 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
10017 turned off (that is, without support for v2 link handshakes). Fixes
10018 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
10019 - In routerlist_assert_ok(), don't take the address of a
10020 routerinfo's cache_info member unless that routerinfo is non-NULL.
10021 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
10022 - Fix a large number of false positive warnings from the clang
10023 analyzer static analysis tool. This should make real warnings
10024 easier for clang analyzer to find. Patch from "teor". Closes
10026 - Resolve GCC complaints on OpenBSD about discarding constness in
10027 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
10028 on 0.1.1.23. Patch from Dana Koch.
10029 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
10030 treatment of long and time_t as comparable types. Fixes part of
10031 bug 11633. Patch from Dana Koch.
10032 - When deciding whether to build the 64-bit curve25519
10033 implementation, detect platforms where we can compile 128-bit
10034 arithmetic but cannot link it. Fixes bug 11729; bugfix on
10035 0.2.4.8-alpha. Patch from "conradev".
10036 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
10037 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
10038 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
10040 - Build and run correctly on systems like OpenBSD-current that have
10041 patched OpenSSL to remove get_cipher_by_char and/or its
10042 implementations. Fixes issue 13325.
10044 o Minor bugfixes (controller and command-line):
10045 - If changing a config option via "setconf" fails in a recoverable
10046 way, we used to nonetheless write our new control ports to the
10047 file described by the "ControlPortWriteToFile" option. Now we only
10048 write out that file if we successfully switch to the new config
10049 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
10051 o Minor bugfixes (directory server):
10052 - No longer accept malformed http headers when parsing urls from
10053 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
10054 bugfix on 0.0.6pre1.
10055 - When sending a compressed set of descriptors or microdescriptors,
10056 make sure to finalize the zlib stream. Previously, we would write
10057 all the compressed data, but if the last descriptor we wanted to
10058 send was missing or too old, we would not mark the stream as
10059 finished. This caused problems for decompression tools. Fixes bug
10060 11648; bugfix on 0.1.1.23.
10062 o Minor bugfixes (hidden service):
10063 - Only retry attempts to connect to a chosen rendezvous point 8
10064 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
10066 o Minor bugfixes (interface):
10067 - Reject relative control socket paths and emit a warning. Previously,
10068 single-component control socket paths would be rejected, but Tor
10069 would not log why it could not validate the config. Fixes bug 9258;
10070 bugfix on 0.2.3.16-alpha.
10072 o Minor bugfixes (log messages):
10073 - Fix a bug where clients using bridges would report themselves
10074 as 50% bootstrapped even without a live consensus document.
10075 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
10076 - Suppress a warning where, if there's only one directory authority
10077 in the network, we would complain that votes and signatures cannot
10078 be uploaded to other directory authorities. Fixes bug 10842;
10079 bugfix on 0.2.2.26-beta.
10080 - Report bootstrapping progress correctly when we're downloading
10081 microdescriptors. We had updated our "do we have enough microdescs
10082 to begin building circuits?" logic most recently in 0.2.4.10-alpha
10083 (see bug 5956), but we left the bootstrap status event logic at
10084 "how far through getting 1/4 of them are we?" Fixes bug 9958;
10085 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
10087 o Minor bugfixes (logging):
10088 - Downgrade "Unexpected onionskin length after decryption" warning
10089 to a protocol-warn, since there's nothing relay operators can do
10090 about a client that sends them a malformed create cell. Resolves
10091 bug 12996; bugfix on 0.0.6rc1.
10092 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
10093 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
10094 - When logging information about an EXTEND2 or EXTENDED2 cell, log
10095 their names correctly. Fixes part of bug 12700; bugfix
10097 - When logging information about a relay cell whose command we don't
10098 recognize, log its command as an integer. Fixes part of bug 12700;
10099 bugfix on 0.2.1.10-alpha.
10100 - Escape all strings from the directory connection before logging
10101 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
10102 - Squelch a spurious LD_BUG message "No origin circuit for
10103 successful SOCKS stream" in certain hidden service failure cases;
10105 - Downgrade the severity of the 'unexpected sendme cell from client'
10106 from 'warn' to 'protocol warning'. Closes ticket 8093.
10108 o Minor bugfixes (misc code correctness):
10109 - In munge_extrainfo_into_routerinfo(), check the return value of
10110 memchr(). This would have been a serious issue if we ever passed
10111 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
10113 - On the chance that somebody manages to build Tor on a
10114 platform where time_t is unsigned, correct the way that
10115 microdesc_add_to_cache() handles negative time arguments.
10116 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
10117 - Fix various instances of undefined behavior in channeltls.c,
10118 tor_memmem(), and eventdns.c that would cause us to construct
10119 pointers to memory outside an allocated object. (These invalid
10120 pointers were not accessed, but C does not even allow them to
10121 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
10122 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
10123 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
10124 fix some miscellaneous errors in our tests and codebase. Fixes bug
10125 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
10126 - Always check return values for unlink, munmap, UnmapViewOfFile;
10127 check strftime return values more often. In some cases all we can
10128 do is report a warning, but this may help prevent deeper bugs from
10129 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
10131 - Fix numerous warnings from the clang "scan-build" static analyzer.
10132 Some of these are programming style issues; some of them are false
10133 positives that indicated awkward code; some are undefined behavior
10134 cases related to constructing (but not using) invalid pointers;
10135 some are assumptions about API behavior; some are (harmlessly)
10136 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
10137 correct; and one or two are genuine bugs that weren't reachable
10138 from the rest of the program. Fixes bug 8793; bugfixes on many,
10141 o Minor bugfixes (node selection):
10142 - If ExcludeNodes is set, consider non-excluded hidden service
10143 directory servers before excluded ones. Do not consider excluded
10144 hidden service directory servers at all if StrictNodes is
10145 set. (Previously, we would sometimes decide to connect to those
10146 servers, and then realize before we initiated a connection that
10147 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
10148 Reported by "mr-4".
10149 - If we set the ExitNodes option but it doesn't include any nodes
10150 that have the Exit flag, we would choose not to bootstrap. Now we
10151 bootstrap so long as ExitNodes includes nodes which can exit to
10152 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
10154 o Minor bugfixes (performance):
10155 - Avoid a bug where every successful connection made us recompute
10156 the flag telling us whether we have sufficient information to
10157 build circuits. Previously, we would forget our cached value
10158 whenever we successfully opened a channel (or marked a router as
10159 running or not running for any other reason), regardless of
10160 whether we had previously believed the router to be running. This
10161 forced us to run an expensive update operation far too often.
10162 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
10163 - Avoid using tor_memeq() for checking relay cell integrity. This
10164 removes a possible performance bottleneck. Fixes part of bug
10165 12169; bugfix on 0.2.1.31.
10167 o Minor bugfixes (platform-specific):
10168 - When dumping a malformed directory object to disk, save it in
10169 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
10171 - Don't report failures from make_socket_reuseable() on incoming
10172 sockets on OSX: this can happen when incoming connections close
10173 early. Fixes bug 10081.
10175 o Minor bugfixes (pluggable transports):
10176 - Avoid another 60-second delay when starting Tor in a pluggable-
10177 transport-using configuration when we already have cached
10178 descriptors for our bridges. Fixes bug 11965; bugfix
10181 o Minor bugfixes (protocol correctness):
10182 - When receiving a VERSIONS cell with an odd number of bytes, close
10183 the connection immediately since the cell is malformed. Fixes bug
10184 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
10187 o Minor bugfixes (relay, other):
10188 - We now drop CREATE cells for already-existent circuit IDs and for
10189 zero-valued circuit IDs, regardless of other factors that might
10190 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
10192 - When rejecting DATA cells for stream_id zero, still count them
10193 against the circuit's deliver window so that we don't fail to send
10194 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
10196 o Minor bugfixes (relay, threading):
10197 - Check return code on spawn_func() in cpuworker code, so that we
10198 don't think we've spawned a nonworking cpuworker and write junk to
10199 it forever. Fix related to bug 4345; bugfix on all released Tor
10200 versions. Found by "skruffy".
10201 - Use a pthread_attr to make sure that spawn_func() cannot return an
10202 error while at the same time launching a thread. Fix related to
10203 bug 4345; bugfix on all released Tor versions. Reported
10206 o Minor bugfixes (relays and bridges):
10207 - Avoid crashing on a malformed resolv.conf file when running a
10208 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
10209 - Non-exit relays no longer launch mock DNS requests to check for
10210 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
10211 non-exit relays stopped servicing DNS requests. Fixes bug 965;
10212 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
10213 - Bridges now report complete directory request statistics. Related
10214 to bug 5824; bugfix on 0.2.2.1-alpha.
10215 - Bridges now never collect statistics that were designed for
10216 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
10218 o Minor bugfixes (testing):
10219 - Fix all valgrind warnings produced by the unit tests. There were
10220 over a thousand memory leak warnings previously, mostly produced
10221 by forgetting to free things in the unit test code. Fixes bug
10222 11618, bugfixes on many versions of Tor.
10224 o Minor bugfixes (tor-fw-helper):
10225 - Give a correct log message when tor-fw-helper fails to launch.
10226 (Previously, we would say something like "tor-fw-helper sent us a
10227 string we could not parse".) Fixes bug 9781; bugfix
10230 o Minor bugfixes (trivial memory leaks):
10231 - Fix a small memory leak when signing a directory object. Fixes bug
10232 11275; bugfix on 0.2.4.13-alpha.
10233 - Resolve some memory leaks found by coverity in the unit tests, on
10234 exit in tor-gencert, and on a failure to compute digests for our
10235 own keys when generating a v3 networkstatus vote. These leaks
10236 should never have affected anyone in practice.
10238 o Code simplification and refactoring:
10239 - Remove some old fallback code designed to keep Tor clients working
10240 in a network with only two working relays. Elsewhere in the code we
10241 have long since stopped supporting such networks, so there wasn't
10242 much point in keeping it around. Addresses ticket 9926.
10243 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
10244 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
10245 - Extract the common duplicated code for creating a subdirectory
10246 of the data directory and writing to a file in it. Fixes ticket
10247 4282; patch from Peter Retzlaff.
10248 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
10249 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
10250 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
10251 - Add a set of accessor functions for the circuit timeout data
10252 structure. Fixes ticket 6153; patch from "piet".
10253 - Clean up exit paths from connection_listener_new(). Closes ticket
10254 8789. Patch from Arlo Breault.
10255 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
10256 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
10257 - Use a doubly-linked list to implement the global circuit list.
10258 Resolves ticket 9108. Patch from Marek Majkowski.
10259 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
10260 - Remove constants and tests for PKCS1 padding; it's insecure and
10261 shouldn't be used for anything new. Fixes bug 8792; patch
10263 - Remove instances of strcpy() from the unit tests. They weren't
10264 hurting anything, since they were only in the unit tests, but it's
10265 embarrassing to have strcpy() in the code at all, and some analysis
10266 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
10267 0.2.3.8-alpha. Patch from Arlo Breault.
10268 - Remove is_internal_IP() function. Resolves ticket 4645.
10269 - Remove unused function circuit_dump_by_chan from circuitlist.c.
10270 Closes issue 9107; patch from "marek".
10271 - Change our use of the ENUM_BF macro to avoid declarations that
10273 - Get rid of router->address, since in all cases it was just the
10274 string representation of router->addr. Resolves ticket 5528.
10277 - Adjust the URLs in the README to refer to the new locations of
10278 several documents on the website. Fixes bug 12830. Patch from
10280 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
10282 - Update manpage to describe some of the files you can expect to
10283 find in Tor's DataDirectory. Addresses ticket 9839.
10284 - Clean up several option names in the manpage to match their real
10285 names, add the missing documentation for a couple of testing and
10286 directory authority options, remove the documentation for a
10287 V2-directory fetching option that no longer exists. Resolves
10289 - Correct the documentation so that it lists the correct directory
10290 for the stats files. (They are in a subdirectory called "stats",
10292 - In the manpage, move more authority-only options into the
10293 directory authority section so that operators of regular directory
10294 caches don't get confused.
10295 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
10296 11061; bugfix on 0.2.4.7-alpha.
10297 - Resolve warnings from Doxygen.
10298 - Document in the manpage that "KBytes" may also be written as
10299 "kilobytes" or "KB", that "Kbits" may also be written as
10300 "kilobits", and so forth. Closes ticket 9222.
10301 - Document that the ClientOnly config option overrides ORPort.
10302 Our old explanation made ClientOnly sound as though it did
10303 nothing at all. Resolves bug 9059.
10304 - Explain that SocksPolicy, DirPolicy, and similar options don't
10305 take port arguments. Fixes the other part of ticket 11108.
10306 - Fix a comment about the rend_server_descriptor_t.protocols field
10307 to more accurately describe its range. Also, make that field
10308 unsigned, to more accurately reflect its usage. Fixes bug 9099;
10309 bugfix on 0.2.1.5-alpha.
10310 - Fix the manpage's description of HiddenServiceAuthorizeClient:
10311 the maximum client name length is 16, not 19. Fixes bug 11118;
10312 bugfix on 0.2.1.6-alpha.
10315 - The contrib directory has been sorted and tidied. Before, it was
10316 an unsorted dumping ground for useful and not-so-useful things.
10317 Now, it is divided based on functionality, and the items which
10318 seemed to be nonfunctional or useless have been removed. Resolves
10319 ticket 8966; based on patches from "rl1987".
10321 o Removed code and features:
10322 - Clients now reject any directory authority certificates lacking
10323 a dir-key-crosscert element. These have been included since
10324 0.2.1.9-alpha, so there's no real reason for them to be optional
10325 any longer. Completes proposal 157. Resolves ticket 10162.
10326 - Remove all code that existed to support the v2 directory system,
10327 since there are no longer any v2 directory authorities. Resolves
10329 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
10330 options, which were used for designating authorities as "Hidden
10331 service authorities". There has been no use of hidden service
10332 authorities since 0.2.2.1-alpha, when we stopped uploading or
10333 downloading v0 hidden service descriptors. Fixes bug 10881; also
10334 part of a fix for bug 10841.
10335 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
10336 and MTBF calculations, but that nobody was using. Fixes bug 11742.
10337 - The TunnelDirConns and PreferTunnelledDirConns options no longer
10338 exist; tunneled directory connections have been available since
10339 0.1.2.5-alpha, and turning them off is not a good idea. This is a
10340 brute-force fix for 10849, where "TunnelDirConns 0" would break
10342 - Remove all code for the long unused v1 directory protocol.
10343 Resolves ticket 11070.
10344 - Remove all remaining code related to version-0 hidden service
10345 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
10346 the rest of bug 10841.
10347 - Remove migration code from when we renamed the "cached-routers"
10348 file to "cached-descriptors" back in 0.2.0.8-alpha. This
10349 incidentally resolves ticket 6502 by cleaning up the related code
10350 a bit. Patch from Akshay Hebbar.
10352 o Test infrastructure:
10353 - Tor now builds each source file in two modes: a mode that avoids
10354 exposing identifiers needlessly, and another mode that exposes
10355 more identifiers for testing. This lets the compiler do better at
10356 optimizing the production code, while enabling us to take more
10357 radical measures to let the unit tests test things.
10358 - The production builds no longer include functions used only in
10359 the unit tests; all functions exposed from a module only for
10360 unit-testing are now static in production builds.
10361 - Add an --enable-coverage configuration option to make the unit
10362 tests (and a new src/or/tor-cov target) to build with gcov test
10364 - Update to the latest version of tinytest.
10365 - Improve the tinytest implementation of string operation tests so
10366 that comparisons with NULL strings no longer crash the tests; they
10367 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
10368 - New macros in test.h to simplify writing mock-functions for unit
10369 tests. Part of ticket 11507. Patch from Dana Koch.
10370 - We now have rudimentary function mocking support that our unit
10371 tests can use to test functions in isolation. Function mocking
10372 lets the tests temporarily replace a function's dependencies with
10373 stub functions, so that the tests can check the function without
10374 invoking the other functions it calls.
10377 - Complete tests for the status.c module. Resolves ticket 11507.
10378 Patch from Dana Koch.
10379 - Add more unit tests for the <circid,channel>->circuit map, and
10380 the destroy-cell-tracking code to fix bug 7912.
10381 - Unit tests for failing cases of the TAP onion handshake.
10382 - More unit tests for address-manipulation functions.
10384 o Distribution (systemd):
10385 - Include a tor.service file in contrib/dist for use with systemd.
10386 Some distributions will be able to use this file unmodified;
10387 others will need to tweak it, or write their own. Patch from Jamie
10388 Nguyen; resolves ticket 8368.
10389 - Verify configuration file via ExecStartPre in the systemd unit
10390 file. Patch from intrigeri; resolves ticket 12730.
10391 - Explicitly disable RunAsDaemon in the systemd unit file. Our
10392 current systemd unit uses "Type = simple", so systemd does not
10393 expect tor to fork. If the user has "RunAsDaemon 1" in their
10394 torrc, then things won't work as expected. This is e.g. the case
10395 on Debian (and derivatives), since there we pass "--defaults-torrc
10396 /usr/share/tor/tor-service-defaults-torrc" (that contains
10397 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
10401 Changes in version 0.2.4.25 - 2014-10-20
10402 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
10403 (even though POODLE does not affect Tor). It also works around a crash
10404 bug caused by some operating systems' response to the "POODLE" attack
10405 (which does affect Tor).
10407 o Major security fixes (also in 0.2.5.9-rc):
10408 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
10409 today support TLS 1.0 or later, so we can safely turn off support
10410 for this old (and insecure) protocol. Fixes bug 13426.
10412 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
10413 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
10414 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
10415 13471. This is a workaround for an OpenSSL bug.
10418 Changes in version 0.2.4.24 - 2014-09-22
10419 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
10420 connecting to hidden services, and it updates the location of one of
10421 the directory authorities.
10424 - Clients now send the correct address for their chosen rendezvous
10425 point when trying to access a hidden service. They used to send
10426 the wrong address, which would still work some of the time because
10427 they also sent the identity digest of the rendezvous point, and if
10428 the hidden service happened to try connecting to the rendezvous
10429 point from a relay that already had a connection open to it,
10430 the relay would reuse that connection. Now connections to hidden
10431 services should be more robust and faster. Also, this bug meant
10432 that clients were leaking to the hidden service whether they were
10433 on a little-endian (common) or big-endian (rare) system, which for
10434 some users might have reduced their anonymity. Fixes bug 13151;
10435 bugfix on 0.2.1.5-alpha.
10437 o Directory authority changes:
10438 - Change IP address for gabelmoo (v3 directory authority).
10440 o Minor features (geoip):
10441 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
10445 Changes in version 0.2.4.23 - 2014-07-28
10446 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
10447 guard rotation, and also backports several important fixes from the
10448 Tor 0.2.5 alpha release series.
10451 - Clients now look at the "usecreatefast" consensus parameter to
10452 decide whether to use CREATE_FAST or CREATE cells for the first hop
10453 of their circuit. This approach can improve security on connections
10454 where Tor's circuit handshake is stronger than the available TLS
10455 connection security levels, but the tradeoff is more computational
10456 load on guard relays. Implements proposal 221. Resolves ticket 9386.
10457 - Make the number of entry guards configurable via a new
10458 NumEntryGuards consensus parameter, and the number of directory
10459 guards configurable via a new NumDirectoryGuards consensus
10460 parameter. Implements ticket 12688.
10463 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
10464 implementation that caused incorrect results on 32-bit
10465 implementations when certain malformed inputs were used along with
10466 a small class of private ntor keys. This bug does not currently
10467 appear to allow an attacker to learn private keys or impersonate a
10468 Tor server, but it could provide a means to distinguish 32-bit Tor
10469 implementations from 64-bit Tor implementations. Fixes bug 12694;
10470 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
10474 - Warn and drop the circuit if we receive an inbound 'relay early'
10475 cell. Those used to be normal to receive on hidden service circuits
10476 due to bug 1038, but the buggy Tor versions are long gone from
10477 the network so we can afford to resume watching for them. Resolves
10478 the rest of bug 1038; bugfix on 0.2.1.19.
10479 - Correct a confusing error message when trying to extend a circuit
10480 via the control protocol but we don't know a descriptor or
10481 microdescriptor for one of the specified relays. Fixes bug 12718;
10482 bugfix on 0.2.3.1-alpha.
10483 - Avoid an illegal read from stack when initializing the TLS
10484 module using a version of OpenSSL without all of the ciphers
10485 used by the v2 link handshake. Fixes bug 12227; bugfix on
10486 0.2.4.8-alpha. Found by "starlight".
10489 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
10493 Changes in version 0.2.4.22 - 2014-05-16
10494 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
10495 alpha release series. These include blocking all authority signing
10496 keys that may have been affected by the OpenSSL "heartbleed" bug,
10497 choosing a far more secure set of TLS ciphersuites by default, closing
10498 a couple of memory leaks that could be used to run a target relay out
10499 of RAM, and several others.
10501 o Major features (security, backport from 0.2.5.4-alpha):
10502 - Block authority signing keys that were used on authorities
10503 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
10504 don't have any evidence that these keys _were_ compromised; we're
10505 doing this to be prudent.) Resolves ticket 11464.
10507 o Major bugfixes (security, OOM):
10508 - Fix a memory leak that could occur if a microdescriptor parse
10509 fails during the tokenizing step. This bug could enable a memory
10510 exhaustion attack by directory servers. Fixes bug 11649; bugfix
10513 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
10514 - The relay ciphersuite list is now generated automatically based on
10515 uniform criteria, and includes all OpenSSL ciphersuites with
10516 acceptable strength and forward secrecy. Previously, we had left
10517 some perfectly fine ciphersuites unsupported due to omission or
10518 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
10519 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
10520 - Relays now trust themselves to have a better view than clients of
10521 which TLS ciphersuites are better than others. (Thanks to bug
10522 11513, the relay list is now well-considered, whereas the client
10523 list has been chosen mainly for anti-fingerprinting purposes.)
10524 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
10525 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
10526 AES128. Resolves ticket 11528.
10527 - Clients now try to advertise the same list of ciphersuites as
10528 Firefox 28. This change enables selection of (fast) GCM
10529 ciphersuites, disables some strange old ciphers, and stops
10530 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
10531 Resolves ticket 11438.
10533 o Minor bugfixes (configuration, security):
10534 - When running a hidden service, do not allow TunneledDirConns 0:
10535 trying to set that option together with a hidden service would
10536 otherwise prevent the hidden service from running, and also make
10537 it publish its descriptors directly over HTTP. Fixes bug 10849;
10538 bugfix on 0.2.1.1-alpha.
10540 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
10541 - Avoid sending a garbage value to the controller when a circuit is
10542 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
10544 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
10545 - Stop leaking memory when we successfully resolve a PTR record.
10546 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
10548 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
10549 - Avoid 60-second delays in the bootstrapping process when Tor is
10550 launching for a second time while using bridges. Fixes bug 9229;
10551 bugfix on 0.2.0.3-alpha.
10553 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
10554 - Give the correct URL in the warning message when trying to run a
10555 relay on an ancient version of Windows. Fixes bug 9393.
10557 o Minor bugfixes (compilation):
10558 - Fix a compilation error when compiling with --disable-curve25519.
10559 Fixes bug 9700; bugfix on 0.2.4.17-rc.
10562 - Downgrade the warning severity for the the "md was still
10563 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
10564 for trying to diagnose this bug, and the current warning in
10565 earlier versions of tor achieves nothing useful. Addresses warning
10568 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
10569 - When we run out of usable circuit IDs on a channel, log only one
10570 warning for the whole channel, and describe how many circuits
10571 there were on the channel. Fixes part of ticket 11553.
10573 o Minor features (security, backport from 0.2.5.4-alpha):
10574 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
10575 leave the default at 8GBytes), to better support Raspberry Pi
10576 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
10578 o Documentation (backport from 0.2.5.4-alpha):
10579 - Correctly document that we search for a system torrc file before
10580 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
10584 Changes in version 0.2.4.21 - 2014-02-28
10585 Tor 0.2.4.21 further improves security against potential adversaries who
10586 find breaking 1024-bit crypto doable, and backports several stability
10587 and robustness patches from the 0.2.5 branch.
10589 o Major features (client security):
10590 - When we choose a path for a 3-hop circuit, make sure it contains
10591 at least one relay that supports the NTor circuit extension
10592 handshake. Otherwise, there is a chance that we're building
10593 a circuit that's worth attacking by an adversary who finds
10594 breaking 1024-bit crypto doable, and that chance changes the game
10595 theory. Implements ticket 9777.
10598 - Do not treat streams that fail with reason
10599 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
10600 since it could also indicate an ENETUNREACH connection error. Fixes
10601 part of bug 10777; bugfix on 0.2.4.8-alpha.
10603 o Code simplification and refactoring:
10604 - Remove data structures which were introduced to implement the
10605 CellStatistics option: they are now redundant with the new timestamp
10606 field in the regular packed_cell_t data structure, which we did
10607 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
10610 - Always clear OpenSSL bignums before freeing them -- even bignums
10611 that don't contain secrets. Resolves ticket 10793. Patch by
10613 - Build without warnings under clang 3.4. (We have some macros that
10614 define static functions only some of which will get used later in
10615 the module. Starting with clang 3.4, these give a warning unless the
10616 unused attribute is set on them.) Resolves ticket 10904.
10617 - Update geoip and geoip6 files to the February 7 2014 Maxmind
10618 GeoLite2 Country database.
10621 - Set the listen() backlog limit to the largest actually supported
10622 on the system, not to the value in a header file. Fixes bug 9716;
10623 bugfix on every released Tor.
10624 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
10625 exit node as a NOROUTE error, not an INTERNAL error, since they
10626 can apparently happen when trying to connect to the wrong sort
10627 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
10628 - Fix build warnings about missing "a2x" comment when building the
10629 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
10630 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
10631 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
10632 not entirely remove it from the connection lists. Fixes bug 9602;
10633 bugfix on 0.2.4.4-alpha.
10634 - Fix a segmentation fault in our benchmark code when running with
10635 Fedora's OpenSSL package, or any other OpenSSL that provides
10636 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
10637 - Turn "circuit handshake stats since last time" log messages into a
10638 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
10640 o Documentation fixes:
10641 - Document that all but one DirPort entry must have the NoAdvertise
10642 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
10645 Changes in version 0.2.4.20 - 2013-12-22
10646 Tor 0.2.4.20 fixes potentially poor random number generation for users
10647 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
10648 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
10649 and 4) have no state file in their DataDirectory (as would happen on
10650 first start). Users who generated relay or hidden service identity
10651 keys in such a situation should discard them and generate new ones.
10653 This release also fixes a logic error that caused Tor clients to build
10654 many more preemptive circuits than they actually need.
10657 - Do not allow OpenSSL engines to replace the PRNG, even when
10658 HardwareAccel is set. The only default builtin PRNG engine uses
10659 the Intel RDRAND instruction to replace the entire PRNG, and
10660 ignores all attempts to seed it with more entropy. That's
10661 cryptographically stupid: the right response to a new alleged
10662 entropy source is never to discard all previously used entropy
10663 sources. Fixes bug 10402; works around behavior introduced in
10664 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
10666 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
10667 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
10668 - Avoid launching spurious extra circuits when a stream is pending.
10669 This fixes a bug where any circuit that _wasn't_ unusable for new
10670 streams would be treated as if it were, causing extra circuits to
10671 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
10674 - Avoid a crash bug when starting with a corrupted microdescriptor
10675 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
10676 - If we fail to dump a previously cached microdescriptor to disk, avoid
10677 freeing duplicate data later on. Fixes bug 10423; bugfix on
10678 0.2.4.13-alpha. Spotted by "bobnomnom".
10681 Changes in version 0.2.4.19 - 2013-12-11
10682 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
10683 (1986-2013). Aaron worked on diverse projects including helping to guide
10684 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
10685 transparency to the U.S government's PACER documents, and contributing
10686 design and development for Tor and Tor2Web. Aaron was one of the latest
10687 martyrs in our collective fight for civil liberties and human rights,
10688 and his death is all the more painful because he was one of us.
10690 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
10691 a new circuit handshake and link encryption that use ECC to provide
10692 better security and efficiency; makes relays better manage circuit
10693 creation requests; uses "directory guards" to reduce client enumeration
10694 risks; makes bridges collect and report statistics about the pluggable
10695 transports they support; cleans up and improves our geoip database;
10696 gets much closer to IPv6 support for clients, bridges, and relays; makes
10697 directory authorities use measured bandwidths rather than advertised
10698 ones when computing flags and thresholds; disables client-side DNS
10699 caching to reduce tracking risks; and fixes a big bug in bridge
10700 reachability testing. This release introduces two new design
10701 abstractions in the code: a new "channel" abstraction between circuits
10702 and or_connections to allow for implementing alternate relay-to-relay
10703 transports, and a new "circuitmux" abstraction storing the queue of
10704 circuits for a channel. The release also includes many stability,
10705 security, and privacy fixes.
10707 o Major features (new circuit handshake):
10708 - Tor now supports a new circuit extension handshake designed by Ian
10709 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
10710 circuit extension handshake, later called "TAP", was a bit slow
10711 (especially on the relay side), had a fragile security proof, and
10712 used weaker keys than we'd now prefer. The new circuit handshake
10713 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
10714 function, making it significantly more secure than the older
10715 handshake, and significantly faster. Tor can use one of two built-in
10716 pure-C curve25519-donna implementations by Adam Langley, or it
10717 can link against the "nacl" library for a tuned version if present.
10719 The built-in version is very fast for 64-bit systems when building
10720 with GCC. The built-in 32-bit version is still faster than the
10721 old TAP protocol, but using libnacl is better on most such hosts.
10723 Implements proposal 216; closes ticket 7202.
10725 o Major features (better link encryption):
10726 - Relays can now enable the ECDHE TLS ciphersuites when available
10727 and appropriate. These ciphersuites let us negotiate forward-secure
10728 TLS secret keys more safely and more efficiently than with our
10729 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
10730 public relays prefer the (faster) P224 group, and bridges prefer
10731 the (more common) P256 group; you can override this with the
10734 This feature requires clients running 0.2.3.17-beta or later,
10735 and requires both sides to be running OpenSSL 1.0.0 or later
10736 with ECC support. OpenSSL 1.0.1, with the compile-time option
10737 "enable-ec_nistp_64_gcc_128", is highly recommended.
10739 Implements the relay side of proposal 198; closes ticket 7200.
10741 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
10742 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
10743 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
10744 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
10745 them to solve bug 6033.)
10747 o Major features (relay performance):
10748 - Instead of limiting the number of queued onionskins (aka circuit
10749 create requests) to a fixed, hard-to-configure number, we limit
10750 the size of the queue based on how many we expect to be able to
10751 process in a given amount of time. We estimate the time it will
10752 take to process an onionskin based on average processing time
10753 of previous onionskins. Closes ticket 7291. You'll never have to
10754 configure MaxOnionsPending again.
10755 - Relays process the new "NTor" circuit-level handshake requests
10756 with higher priority than the old "TAP" circuit-level handshake
10757 requests. We still process some TAP requests to not totally starve
10758 0.2.3 clients when NTor becomes popular. A new consensus parameter
10759 "NumNTorsPerTAP" lets us tune the balance later if we need to.
10760 Implements ticket 9574.
10762 o Major features (client bootstrapping resilience):
10763 - Add a new "FallbackDir" torrc option to use when we can't use
10764 a directory mirror from the consensus (either because we lack a
10765 consensus, or because they're all down). Currently, all authorities
10766 are fallbacks by default, and there are no other default fallbacks,
10767 but that will change. This option will allow us to give clients a
10768 longer list of servers to try to get a consensus from when first
10769 connecting to the Tor network, and thereby reduce load on the
10770 directory authorities. Implements proposal 206, "Preconfigured
10771 directory sources for bootstrapping". We also removed the old
10772 "FallbackNetworkstatus" option, since we never got it working well
10773 enough to use it. Closes bug 572.
10774 - If we have no circuits open, use a relaxed timeout (the
10775 95th-percentile cutoff) until a circuit succeeds. This heuristic
10776 should allow Tor to succeed at building circuits even when the
10777 network connection drastically changes. Should help with bug 3443.
10779 o Major features (use of guards):
10780 - Support directory guards (proposal 207): when possible, clients now
10781 use their entry guards for non-anonymous directory requests. This
10782 can help prevent client enumeration. Note that this behavior only
10783 works when we have a usable consensus directory, and when options
10784 about what to download are more or less standard. In the future we
10785 should re-bootstrap from our guards, rather than re-bootstrapping
10786 from the preconfigured list of directory sources that ships with
10787 Tor. Resolves ticket 6526.
10788 - Raise the default time that a client keeps an entry guard from
10789 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
10790 2012 paper. (We would make it even longer, but we need better client
10791 load balancing first.) Also, make the guard lifetime controllable
10792 via a new GuardLifetime torrc option and a GuardLifetime consensus
10793 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
10795 o Major features (bridges with pluggable transports):
10796 - Bridges now report the pluggable transports they support to the
10797 bridge authority, so it can pass the supported transports on to
10798 bridgedb and/or eventually do reachability testing. Implements
10800 - Automatically forward the TCP ports of pluggable transport
10801 proxies using tor-fw-helper if PortForwarding is enabled. Implements
10804 o Major features (geoip database):
10805 - Maxmind began labelling Tor relays as being in country "A1",
10806 which breaks by-country node selection inside Tor. Now we use a
10807 script to replace "A1" ("Anonymous Proxy") entries in our geoip
10808 file with real country codes. This script fixes about 90% of "A1"
10809 entries automatically and uses manual country code assignments to
10810 fix the remaining 10%. See src/config/README.geoip for details.
10812 - Add GeoIP database for IPv6 addresses. The new config option
10814 - Update to the October 2 2013 Maxmind GeoLite Country database.
10816 o Major features (IPv6):
10817 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
10818 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
10819 to happen. Implements ticket 5535.
10820 - All kind of relays, not just bridges, can now advertise an IPv6
10821 OR port. Implements ticket 6362.
10822 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
10823 connectivity, then set the IPv6Exit flag to 1. Also make sure your
10824 exit policy reads as you would like: the address * applies to all
10825 address families, whereas *4 is IPv4 address only, and *6 is IPv6
10826 addresses only. On the client side, you'll need to wait for enough
10827 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
10828 and use Socks5. Closes ticket 5547, implements proposal 117 as
10829 revised in proposal 208.
10830 - Bridge authorities now accept IPv6 bridge addresses and include
10831 them in network status documents. Implements ticket 5534.
10832 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
10834 o Major features (directory authorities):
10835 - Directory authorities now prefer using measured bandwidths to
10836 advertised ones when computing flags and thresholds. Resolves
10838 - Directory authorities that vote measured bandwidths about more
10839 than a threshold number of relays now treat relays with
10840 unmeasured bandwidths as having bandwidth 0 when computing their
10841 flags. Resolves ticket 8435.
10842 - Directory authorities now support a new consensus method (17)
10843 where they cap the published bandwidth of relays for which
10844 insufficient bandwidth measurements exist. Fixes part of bug 2286.
10845 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
10846 serve any v2 directory information. Now we can test disabling the
10847 old deprecated v2 directory format, and see whether doing so has
10848 any effect on network load. Begins to fix bug 6783.
10850 o Major features (build and portability):
10851 - Switch to a nonrecursive Makefile structure. Now instead of each
10852 Makefile.am invoking other Makefile.am's, there is a master
10853 Makefile.am that includes the others. This change makes our build
10854 process slightly more maintainable, and improves parallelism for
10855 building with make -j. Original patch by Stewart Smith; various
10856 fixes by Jim Meyering.
10857 - Where available, we now use automake's "silent" make rules by
10858 default, so that warnings are easier to spot. You can get the old
10859 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
10860 - Resume building correctly with MSVC and Makefile.nmake. This patch
10861 resolves numerous bugs and fixes reported by ultramage, including
10862 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
10864 o Security features:
10865 - Switch to a completely time-invariant approach for picking nodes
10866 weighted by bandwidth. Our old approach would run through the
10867 part of the loop after it had made its choice slightly slower
10868 than it ran through the part of the loop before it had made its
10869 choice. Addresses ticket 6538.
10870 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
10871 by tor2web clients allows hidden services to identify tor2web
10872 clients through their repeated selection of the same rendezvous
10873 and introduction point circuit endpoints (their guards). Resolves
10876 o Major bugfixes (relay denial of service):
10877 - When we have too much memory queued in circuits (according to a new
10878 MaxMemInCellQueues option), close the circuits that have the oldest
10879 queued cells, on the theory that those are most responsible for
10880 us running low on memory. This prevents us from running out of
10881 memory as a relay if circuits fill up faster than they can be
10882 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
10883 Tor. This bug is a further fix beyond bug 6252, whose fix was
10884 merged into 0.2.3.21-rc.
10885 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
10886 ID: these could be used to create unexpected streams and circuits
10887 which would count as "present" to some parts of Tor but "absent"
10888 to others, leading to zombie circuits and streams or to a bandwidth
10889 denial-of-service. Fixes bug 7889; bugfix on every released version
10890 of Tor. Reported by "oftc_must_be_destroyed".
10891 - Avoid a bug where our response to TLS renegotiation under certain
10892 network conditions could lead to a busy-loop, with 100% CPU
10893 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
10895 o Major bugfixes (asserts, crashes, leaks):
10896 - Prevent the get_freelists() function from running off the end of
10897 the list of freelists if it somehow gets an unrecognized
10898 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
10900 - Avoid a memory leak where we would leak a consensus body when we
10901 find that a consensus which we couldn't previously verify due to
10902 missing certificates is now verifiable. Fixes bug 8719; bugfix
10904 - If we are unable to save a microdescriptor to the journal, do not
10905 drop it from memory and then reattempt downloading it. Fixes bug
10906 9645; bugfix on 0.2.2.6-alpha.
10907 - Fix an assertion failure that would occur when disabling the
10908 ORPort setting on a running Tor process while accounting was
10909 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
10910 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
10911 when an exit connection with optimistic data succeeds immediately
10912 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
10914 - Fix a memory leak that would occur whenever a configuration
10915 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
10917 o Major bugfixes (relay rate limiting):
10918 - When a TLS write is partially successful but incomplete, remember
10919 that the flushed part has been flushed, and notice that bytes were
10920 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
10921 bugfix on Tor 0.1.0.5-rc.
10922 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
10923 to 1GB/1GB. The previous defaults were intended to be "basically
10924 infinite", but it turns out they're now limiting our 100mbit+
10925 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
10926 last time we raised it).
10927 - No longer stop reading or writing on cpuworker connections when
10928 our rate limiting buckets go empty. Now we should handle circuit
10929 handshake requests more promptly. Resolves bug 9731.
10931 o Major bugfixes (client-side privacy):
10932 - When we mark a circuit as unusable for new circuits, have it
10933 continue to be unusable for new circuits even if MaxCircuitDirtiness
10934 is increased too much at the wrong time, or the system clock jumps
10935 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
10936 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
10937 which have resolved to internal addresses") is set, apply that
10938 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
10939 - When an exit relay rejects a stream with reason "exit policy", but
10940 we only know an exit policy summary (e.g. from the microdesc
10941 consensus) for it, do not mark the relay as useless for all exiting.
10942 Instead, mark just the circuit as unsuitable for that particular
10943 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
10945 o Major bugfixes (stream isolation):
10946 - Allow applications to get proper stream isolation with
10947 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
10948 username/password authentication also offer "no authentication". Tor
10949 had previously preferred "no authentication", so the applications
10950 never actually sent Tor their auth details. Now Tor selects
10951 username/password authentication if it's offered. You can disable
10952 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
10953 bug 8117; bugfix on 0.2.3.3-alpha.
10954 - Follow the socks5 protocol when offering username/password
10955 authentication. The fix for bug 8117 exposed this bug, and it
10956 turns out real-world applications like Pidgin do care. Bugfix on
10957 0.2.3.2-alpha; fixes bug 8879.
10959 o Major bugfixes (client circuit building):
10960 - Alter circuit build timeout measurement to start at the point
10961 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
10962 initialization). This should make our timeout measurements more
10963 uniform. Previously, we were sometimes including ORconn setup time
10964 in our circuit build time measurements. Should resolve bug 3443.
10965 - If the circuit build timeout logic is disabled (via the consensus,
10966 or because we are an authority), then don't build testing circuits.
10967 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
10969 o Major bugfixes (client-side DNS):
10970 - Turn off the client-side DNS cache by default. Updating and using
10971 the DNS cache is now configurable on a per-client-port
10972 level. SOCKSPort, DNSPort, etc lines may now contain
10973 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
10974 cache these types of DNS answers when we receive them from an
10975 exit node in response to an application request on this port, and
10976 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
10977 cached DNS answers of these types, we shouldn't use them. It's
10978 potentially risky to use cached DNS answers at the client, since
10979 doing so can indicate to one exit what answers we've gotten
10980 for DNS lookups in the past. With IPv6, this becomes especially
10981 problematic. Using cached DNS answers for requests on the same
10982 circuit would present less linkability risk, since all traffic
10983 on a circuit is already linkable, but it would also provide
10984 little performance benefit: the exit node caches DNS replies
10985 too. Implements a simplified version of Proposal 205. Implements
10988 o Major bugfixes (hidden service privacy):
10989 - Limit hidden service descriptors to at most ten introduction
10990 points, to slow one kind of guard enumeration. Fixes bug 9002;
10991 bugfix on 0.1.1.11-alpha.
10993 o Major bugfixes (directory fetching):
10994 - If the time to download the next old-style networkstatus is in
10995 the future, do not decline to consider whether to download the
10996 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
10998 - We used to always request authority certificates by identity digest,
10999 meaning we'd get the newest one even when we wanted one with a
11000 different signing key. Then we would complain about being given
11001 a certificate we already had, and never get the one we really
11002 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
11003 resource to request the one we want. Fixes bug 5595; bugfix on
11006 o Major bugfixes (bridge reachability):
11007 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
11008 previously they did not, which prevented them from receiving
11009 successful connections from relays for self-test or bandwidth
11010 testing. Also, when a relay is extending a circuit to a bridge,
11011 it needs to send a NETINFO cell, even when the bridge hasn't sent
11012 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
11014 o Major bugfixes (control interface):
11015 - When receiving a new configuration file via the control port's
11016 LOADCONF command, do not treat the defaults file as absent.
11017 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
11019 o Major bugfixes (directory authorities):
11020 - Stop marking every relay as having been down for one hour every
11021 time we restart a directory authority. These artificial downtimes
11022 were messing with our Stable and Guard flag calculations. Fixes
11023 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
11024 - When computing directory thresholds, ignore any rejected-as-sybil
11025 nodes during the computation so that they can't influence Fast,
11026 Guard, etc. (We should have done this for proposal 109.) Fixes
11028 - When marking a node as a likely sybil, reset its uptime metrics
11029 to zero, so that it cannot time towards getting marked as Guard,
11030 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
11032 - Fix a bug in the voting algorithm that could yield incorrect results
11033 when a non-naming authority declared too many flags. Fixes bug 9200;
11034 bugfix on 0.2.0.3-alpha.
11036 o Internal abstraction features:
11037 - Introduce new channel_t abstraction between circuits and
11038 or_connection_t to allow for implementing alternate OR-to-OR
11039 transports. A channel_t is an abstract object which can either be a
11040 cell-bearing channel, which is responsible for authenticating and
11041 handshaking with the remote OR and transmitting cells to and from
11042 it, or a listening channel, which spawns new cell-bearing channels
11043 at the request of remote ORs. Implements part of ticket 6465.
11044 - Make a channel_tls_t subclass of channel_t, adapting it to the
11045 existing or_connection_t code. The V2/V3 protocol handshaking
11046 code which formerly resided in command.c has been moved below the
11047 channel_t abstraction layer and may be found in channeltls.c now.
11048 Implements the rest of ticket 6465.
11049 - Introduce new circuitmux_t storing the queue of circuits for
11050 a channel; this encapsulates and abstracts the queue logic and
11051 circuit selection policy, and allows the latter to be overridden
11052 easily by switching out a policy object. The existing EWMA behavior
11053 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
11055 o New build requirements:
11056 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
11057 strongly recommended.
11058 - Tor maintainers now require Automake version 1.9 or later to build
11059 Tor from the Git repository. (Automake is not required when building
11060 from a source distribution.)
11062 o Minor features (protocol):
11063 - No longer include the "opt" prefix when generating routerinfos
11064 or v2 directories: it has been needless since Tor 0.1.2. Closes
11066 - Reject EXTEND cells sent to nonexistent streams. According to the
11067 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
11068 we were only checking for stream IDs that were currently in use.
11069 Found while hunting for more instances of bug 6271. Bugfix on
11070 0.0.2pre8, which introduced incremental circuit construction.
11071 - Tor relays and clients now support a better CREATE/EXTEND cell
11072 format, allowing the sender to specify multiple address, identity,
11073 and handshake types. Implements Robert Ransom's proposal 200;
11074 closes ticket 7199.
11075 - Reject as invalid most directory objects containing a NUL.
11076 Belt-and-suspender fix for bug 8037.
11078 o Minor features (security):
11079 - Clear keys and key-derived material left on the stack in
11080 rendservice.c and rendclient.c. Check return value of
11081 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
11082 These fixes should make us more forward-secure against cold-boot
11083 attacks and the like. Fixes bug 2385.
11084 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
11085 Irix's random() only return 15 bits; Solaris's random() returns more
11086 bits but its RAND_MAX says it only returns 15, and so on. Motivated
11087 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
11089 o Minor features (control protocol):
11090 - Add a "GETINFO signal/names" control port command. Implements
11092 - Provide default values for all options via "GETINFO config/defaults".
11093 Implements ticket 4971.
11094 - Allow an optional $ before the node identity digest in the
11095 controller command GETINFO ns/id/<identity>, for consistency with
11096 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
11097 - Add CACHED keyword to ADDRMAP events in the control protocol
11098 to indicate whether a DNS result will be cached or not. Resolves
11100 - Generate bootstrapping status update events correctly when fetching
11101 microdescriptors. Fixes bug 9927.
11103 o Minor features (path selection):
11104 - When deciding whether we have enough descriptors to build circuits,
11105 instead of looking at raw relay counts, look at which fraction
11106 of (bandwidth-weighted) paths we're able to build. This approach
11107 keeps clients from building circuits if their paths are likely to
11108 stand out statistically. The default fraction of paths needed is
11109 taken from the consensus directory; you can override it with the
11110 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
11111 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
11112 and we have GeoIP information, also exclude all nodes with unknown
11113 countries "??" and "A1". This behavior is controlled by the
11114 new GeoIPExcludeUnknown option: you can make such nodes always
11115 excluded with "GeoIPExcludeUnknown 1", and disable the feature
11116 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
11117 gets you the default behavior. Implements feature 7706.
11119 o Minor features (hidden services):
11120 - Improve circuit build timeout handling for hidden services.
11121 In particular: adjust build timeouts more accurately depending
11122 upon the number of hop-RTTs that a particular circuit type
11123 undergoes. Additionally, launch intro circuits in parallel
11124 if they timeout, and take the first one to reply as valid.
11125 - The Tor client now ignores sub-domain components of a .onion
11126 address. This change makes HTTP "virtual" hosting
11127 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
11128 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
11129 hosted on the same hidden service. Implements proposal 204.
11130 - Enable Tor to read configuration, state, and key information from
11131 a FIFO. Previously Tor would only read from files with a positive
11132 stat.st_size. Code from meejah; fixes bug 6044.
11134 o Minor features (clients):
11135 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
11136 microdescriptor-related dir requests, and only fall back to normal
11137 descriptors if none of their bridges can handle microdescriptors
11138 (as opposed to the fix in ticket 4013, which caused them to fall
11139 back to normal descriptors if *any* of their bridges preferred
11140 them). Resolves ticket 4994.
11141 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
11142 TCP ports to forward. In the past it only accepted two ports:
11143 the ORPort and the DirPort.
11145 o Minor features (protecting client timestamps):
11146 - Clients no longer send timestamps in their NETINFO cells. These were
11147 not used for anything, and they provided one small way for clients
11148 to be distinguished from each other as they moved from network to
11149 network or behind NAT. Implements part of proposal 222.
11150 - Clients now round timestamps in INTRODUCE cells down to the nearest
11151 10 minutes. If a new Support022HiddenServices option is set to 0, or
11152 if it's set to "auto" and the feature is disabled in the consensus,
11153 the timestamp is sent as 0 instead. Implements part of proposal 222.
11154 - Stop sending timestamps in AUTHENTICATE cells. This is not such
11155 a big deal from a security point of view, but it achieves no actual
11156 good purpose, and isn't needed. Implements part of proposal 222.
11157 - Reduce down accuracy of timestamps in hidden service descriptors.
11158 Implements part of proposal 222.
11160 o Minor features (bridges):
11161 - Make bridge relays check once a minute for whether their IP
11162 address has changed, rather than only every 15 minutes. Resolves
11163 bugs 1913 and 1992.
11164 - Bridge statistics now count bridge clients connecting over IPv6:
11165 bridge statistics files now list "bridge-ip-versions" and
11166 extra-info documents list "geoip6-db-digest". The control protocol
11167 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
11168 implementation by "shkoo", addressing ticket 5055.
11169 - Add a new torrc option "ServerTransportListenAddr" to let bridge
11170 operators select the address where their pluggable transports will
11171 listen for connections. Resolves ticket 7013.
11172 - Randomize the lifetime of our SSL link certificate, so censors can't
11173 use the static value for filtering Tor flows. Resolves ticket 8443;
11174 related to ticket 4014 which was included in 0.2.2.33.
11176 o Minor features (relays):
11177 - Option OutboundBindAddress can be specified multiple times and
11178 accepts IPv6 addresses. Resolves ticket 6876.
11180 o Minor features (IPv6, client side):
11181 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
11182 prefer to hand out virtual IPv6 addresses, since there are more of
11183 them and we can't run out. To override this behavior and make IPv4
11184 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
11185 or DNSPort you're using for resolving. Implements ticket 7571.
11186 - AutomapHostsOnResolve responses are now randomized, to avoid
11187 annoying situations where Tor is restarted and applications
11188 connect to the wrong addresses.
11189 - Never try more than 1000 times to pick a new virtual address when
11190 AutomapHostsOnResolve is set. That's good enough so long as we
11191 aren't close to handing out our entire virtual address space;
11192 if you're getting there, it's best to switch to IPv6 virtual
11195 o Minor features (IPv6, relay/authority side):
11196 - New config option "AuthDirHasIPv6Connectivity 1" that directory
11197 authorities should set if they have IPv6 connectivity and want to
11198 do reachability tests for IPv6 relays. Implements feature 5974.
11199 - A relay with an IPv6 OR port now sends that address in NETINFO
11200 cells (in addition to its other address). Implements ticket 6364.
11202 o Minor features (directory authorities):
11203 - Directory authorities no long accept descriptors for any version of
11204 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
11205 These versions are insecure, unsupported, or both. Implements
11207 - When directory authorities are computing thresholds for flags,
11208 never let the threshold for the Fast flag fall below 4096
11209 bytes. Also, do not consider nodes with extremely low bandwidths
11210 when deciding thresholds for various directory flags. This change
11211 should raise our threshold for Fast relays, possibly in turn
11212 improving overall network performance; see ticket 1854. Resolves
11214 - Directory authorities now include inside each vote a statement of
11215 the performance thresholds they used when assigning flags.
11216 Implements ticket 8151.
11217 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
11218 in directory authority votes to describe whether they have enough
11219 measured bandwidths to ignore advertised (relay descriptor)
11220 bandwidth claims. Resolves ticket 8711.
11222 o Minor features (path bias detection):
11223 - Path Use Bias: Perform separate accounting for successful circuit
11224 use. Keep separate statistics on stream attempt rates versus stream
11225 success rates for each guard. Provide configurable thresholds to
11226 determine when to emit log messages or disable use of guards that
11227 fail too many stream attempts. Resolves ticket 7802.
11228 - Create three levels of Path Bias log messages, as opposed to just
11229 two. These are configurable via consensus as well as via the torrc
11230 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
11231 The default values are 0.70, 0.50, and 0.30 respectively.
11232 - Separate the log message levels from the decision to drop guards,
11233 which also is available via torrc option PathBiasDropGuards.
11234 PathBiasDropGuards still defaults to 0 (off).
11235 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
11236 in combination with PathBiasExtremeRate.
11237 - Increase the default values for PathBiasScaleThreshold and
11238 PathBiasCircThreshold from (200, 20) to (300, 150).
11239 - Add in circuit usage accounting to path bias. If we try to use a
11240 built circuit but fail for any reason, it counts as path bias.
11241 Certain classes of circuits where the adversary gets to pick your
11242 destination node are exempt from this accounting. Usage accounting
11243 can be specifically disabled via consensus parameter or torrc.
11244 - Convert all internal path bias state to double-precision floating
11245 point, to avoid roundoff error and other issues.
11246 - Only record path bias information for circuits that have completed
11247 *two* hops. Assuming end-to-end tagging is the attack vector, this
11248 makes us more resilient to ambient circuit failure without any
11249 detection capability loss.
11251 o Minor features (build):
11252 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
11253 dhill. Resolves ticket 6982.
11254 - Compile on win64 using mingw64. Fixes bug 7260; patches from
11256 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
11257 separate error codes; or at least, don't break for that reason.
11258 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
11260 o Build improvements (autotools):
11261 - Warn if building on a platform with an unsigned time_t: there
11262 are too many places where Tor currently assumes that time_t can
11263 hold negative values. We'd like to fix them all, but probably
11265 - Do not report status verbosely from autogen.sh unless the -v flag
11266 is specified. Fixes issue 4664. Patch from Onizuka.
11267 - Detect and reject attempts to build Tor with threading support
11268 when OpenSSL has been compiled without threading support.
11270 - Try to detect if we are ever building on a platform where
11271 memset(...,0,...) does not set the value of a double to 0.0. Such
11272 platforms are permitted by the C standard, though in practice
11273 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
11274 currently support them, but it's better to detect them and fail
11275 than to perform erroneously.
11276 - We no longer warn so much when generating manpages from their
11278 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
11279 the signs of types during autoconf. This is better than our old
11280 approach, which didn't work when cross-compiling.
11282 o Minor features (log messages, warnings):
11283 - Detect when we're running with a version of OpenSSL other than the
11284 one we compiled with. This conflict has occasionally given people
11285 hard-to-track-down errors.
11286 - Warn users who run hidden services on a Tor client with
11287 UseEntryGuards disabled that their hidden services will be
11288 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
11289 attack which motivated Tor to support entry guards in the first
11290 place). Resolves ticket 6889.
11291 - Warn when we are binding low ports when hibernation is enabled;
11292 previously we had warned when we were _advertising_ low ports with
11293 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
11294 - Issue a warning when running with the bufferevents backend enabled.
11295 It's still not stable, and people should know that they're likely
11296 to hit unexpected problems. Closes ticket 9147.
11298 o Minor features (log messages, notices):
11299 - Refactor resolve_my_address() so it returns the method by which we
11300 decided our public IP address (explicitly configured, resolved from
11301 explicit hostname, guessed from interfaces, learned by gethostname).
11302 Now we can provide more helpful log messages when a relay guesses
11303 its IP address incorrectly (e.g. due to unexpected lines in
11304 /etc/hosts). Resolves ticket 2267.
11305 - Track how many "TAP" and "NTor" circuit handshake requests we get,
11306 and how many we complete, and log it every hour to help relay
11307 operators follow trends in network load. Addresses ticket 9658.
11309 o Minor features (log messages, diagnostics):
11310 - If we fail to free a microdescriptor because of bug 7164, log
11311 the filename and line number from which we tried to free it.
11312 - We compute the overhead from passing onionskins back and forth to
11313 cpuworkers, and report it when dumping statistics in response to
11314 SIGUSR1. Supports ticket 7291.
11315 - Add another diagnostic to the heartbeat message: track and log
11316 overhead that TLS is adding to the data we write. If this is
11317 high, we are sending too little data to SSL_write at a time.
11318 Diagnostic for bug 7707.
11319 - Log packaged cell fullness as part of the heartbeat message.
11320 Diagnosis to try to determine the extent of bug 7743.
11321 - Add more detail to a log message about relaxed timeouts, to help
11323 - When learning a fingerprint for a bridge, log its corresponding
11324 transport type. Implements ticket 7896.
11325 - Warn more aggressively when flushing microdescriptors to a
11326 microdescriptor cache fails, in an attempt to mitigate bug 8031,
11327 or at least make it more diagnosable.
11328 - Improve the log message when "Bug/attack: unexpected sendme cell
11329 from client" occurs, to help us track bug 8093.
11330 - Improve debugging output to help track down bug 8185 ("Bug:
11331 outgoing relay cell has n_chan==NULL. Dropping.")
11333 o Minor features (log messages, quieter bootstrapping):
11334 - Log fewer lines at level "notice" about our OpenSSL and Libevent
11335 versions and capabilities when everything is going right. Resolves
11336 part of ticket 6736.
11337 - Omit the first heartbeat log message, because it never has anything
11338 useful to say, and it clutters up the bootstrapping messages.
11339 Resolves ticket 6758.
11340 - Don't log about reloading the microdescriptor cache at startup. Our
11341 bootstrap warnings are supposed to tell the user when there's a
11342 problem, and our bootstrap notices say when there isn't. Resolves
11343 ticket 6759; bugfix on 0.2.2.6-alpha.
11344 - Don't log "I learned some more directory information" when we're
11345 reading cached directory information. Reserve it for when new
11346 directory information arrives in response to a fetch. Resolves
11348 - Don't complain about bootstrapping problems while hibernating.
11349 These complaints reflect a general code problem, but not one
11350 with any problematic effects (no connections are actually
11351 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
11353 o Minor features (testing):
11354 - In our testsuite, create temporary directories with a bit more
11355 entropy in their name to make name collisions less likely. Fixes
11357 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
11358 (P-256) Diffie-Hellman handshakes to src/or/bench.
11359 - Add benchmark functions to test onion handshake performance.
11362 - The DirServer option is now DirAuthority, for consistency with
11363 current naming patterns. You can still use the old DirServer form.
11365 o Minor bugfixes (protocol):
11366 - Fix the handling of a TRUNCATE cell when it arrives while the
11367 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
11368 - When a Tor client gets a "truncated" relay cell, the first byte of
11369 its payload specifies why the circuit was truncated. We were
11370 ignoring this 'reason' byte when tearing down the circuit, resulting
11371 in the controller not being told why the circuit closed. Now we
11372 pass the reason from the truncated cell to the controller. Bugfix
11373 on 0.1.2.3-alpha; fixes bug 7039.
11374 - Fix a misframing issue when reading the version numbers in a
11375 VERSIONS cell. Previously we would recognize [00 01 00 02] as
11376 'version 1, version 2, and version 0x100', when it should have
11377 only included versions 1 and 2. Fixes bug 8059; bugfix on
11378 0.2.0.10-alpha. Reported pseudonymously.
11379 - Make the format and order of STREAM events for DNS lookups
11380 consistent among the various ways to launch DNS lookups. Fixes
11381 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
11383 o Minor bugfixes (syscalls and disk interaction):
11384 - Always check the return values of functions fcntl() and
11385 setsockopt(). We don't believe these are ever actually failing in
11386 practice, but better safe than sorry. Also, checking these return
11387 values should please analysis tools like Coverity. Patch from
11388 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
11389 - Avoid double-closing the listener socket in our socketpair()
11390 replacement (used on Windows) in the case where the addresses on
11391 our opened sockets don't match what we expected. Fixes bug 9400;
11392 bugfix on 0.0.2pre7. Found by Coverity.
11393 - Correctly store microdescriptors and extrainfo descriptors that
11394 include an internal NUL byte. Fixes bug 8037; bugfix on
11395 0.2.0.1-alpha. Bug reported by "cypherpunks".
11396 - If for some reason we fail to write a microdescriptor while
11397 rebuilding the cache, do not let the annotations from that
11398 microdescriptor linger in the cache file, and do not let the
11399 microdescriptor stay recorded as present in its old location.
11400 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
11401 - Use direct writes rather than stdio when building microdescriptor
11402 caches, in an attempt to mitigate bug 8031, or at least make it
11405 o Minor fixes (config options):
11406 - Warn and fail if a server is configured not to advertise any
11407 ORPorts at all. (We need *something* to put in our descriptor,
11408 or we just won't work.)
11409 - Behave correctly when the user disables LearnCircuitBuildTimeout
11410 but doesn't tell us what they would like the timeout to be. Fixes
11411 bug 6304; bugfix on 0.2.2.14-alpha.
11412 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
11413 to start with a triple-underscore so the controller won't touch it.
11414 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
11415 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
11416 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
11417 - When autodetecting the number of CPUs, use the number of available
11418 CPUs in preference to the number of configured CPUs. Inform the
11419 user if this reduces the number of available CPUs. Fixes bug 8002;
11420 bugfix on 0.2.3.1-alpha.
11421 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
11422 - Make it an error when you set EntryNodes but disable UseGuardNodes,
11423 since it will (surprisingly to some users) ignore EntryNodes. Fixes
11424 bug 8180; bugfix on 0.2.3.11-alpha.
11425 - Avoid overflows when the user sets MaxCircuitDirtiness to a
11426 ridiculously high value, by imposing a (ridiculously high) 30-day
11427 maximum on MaxCircuitDirtiness.
11429 o Minor bugfixes (control protocol):
11430 - Stop sending a stray "(null)" in some cases for the server status
11431 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
11433 - The ADDRMAP command can no longer generate an ill-formed error
11434 code on a failed MAPADDRESS. It now says "internal" rather than
11435 an English sentence fragment with spaces in the middle. Bugfix on
11436 Tor 0.2.0.19-alpha.
11438 o Minor bugfixes (clients / edges):
11439 - When we receive a RELAY_END cell with the reason DONE, or with no
11440 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
11441 status as "connection refused". Previously we reported these cases
11442 as success but then immediately closed the connection. Fixes bug
11443 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
11444 - If the guard we choose first doesn't answer, we would try the
11445 second guard, but once we connected to the second guard we would
11446 abandon it and retry the first one, slowing down bootstrapping.
11447 The fix is to treat all our initially chosen guards as acceptable
11448 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
11449 - When choosing which stream on a formerly stalled circuit to wake
11450 first, make better use of the platform's weak RNG. Previously,
11451 we had been using the % ("modulo") operator to try to generate a
11452 1/N chance of picking each stream, but this behaves badly with
11453 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
11456 o Minor bugfixes (path bias detection):
11457 - If the state file's path bias counts are invalid (presumably from a
11458 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
11459 additional checks and log messages to the scaling of Path Bias
11460 counts, in case there still are remaining issues with scaling.
11461 Should help resolve bug 8235.
11462 - Prevent rounding error in path bias counts when scaling
11463 them down, and use the correct scale factor default. Also demote
11464 some path bias related log messages down a level and make others
11465 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
11466 - Remove a source of rounding error during path bias count scaling;
11467 don't count cannibalized circuits as used for path bias until we
11468 actually try to use them; and fix a circuit_package_relay_cell()
11469 warning message about n_chan==NULL. Fixes bug 7802.
11470 - Paste the description for PathBias parameters from the man
11471 page into or.h, so the code documents them too. Fixes bug 7982;
11472 bugfix on 0.2.3.17-beta.
11474 o Minor bugfixes (relays):
11475 - Stop trying to resolve our hostname so often (e.g. every time we
11476 think about doing a directory fetch). Now we reuse the cached
11477 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
11478 and 2410 (bugfix on 0.1.2.2-alpha).
11479 - When examining the list of network interfaces to find our address,
11480 do not consider non-running or disabled network interfaces. Fixes
11481 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
11483 o Minor bugfixes (blocking resistance):
11484 - Only disable TLS session ticket support when running as a TLS
11485 server. Now clients will blend better with regular Firefox
11486 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
11488 o Minor bugfixes (IPv6):
11489 - Use square brackets around IPv6 addresses in numerous places
11490 that needed them, including log messages, HTTPS CONNECT proxy
11491 requests, TransportProxy statefile entries, and pluggable transport
11492 extra-info lines. Fixes bug 7011; patch by David Fifield.
11494 o Minor bugfixes (directory authorities):
11495 - Reject consensus votes with more than 64 known-flags. We aren't even
11496 close to that limit yet, and our code doesn't handle it correctly.
11497 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
11498 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
11499 bugfix on 0.2.0.3-alpha.
11501 o Minor bugfixes (memory leaks):
11502 - Avoid leaking memory if we fail to compute a consensus signature
11503 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
11504 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
11505 on 0.2.1.1-alpha; fixes bug 7816.
11506 - Fix a memory leak during safe-cookie controller authentication.
11507 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
11508 - Free some more still-in-use memory at exit, to make hunting for
11509 memory leaks easier. Resolves bug 7029.
11511 o Minor bugfixes (code correctness):
11512 - Increase the width of the field used to remember a connection's
11513 link protocol version to two bytes. Harmless for now, since the
11514 only currently recognized versions are one byte long. Reported
11515 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
11516 - Fix a crash when debugging unit tests on Windows: deallocate a
11517 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
11518 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
11519 - When detecting the largest possible file descriptor (in order to
11520 close all file descriptors when launching a new program), actually
11521 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
11522 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
11524 - Avoid a crash if we fail to generate an extrainfo descriptor.
11525 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
11526 this is CID 718634.
11527 - Avoid an off-by-one error when checking buffer boundaries when
11528 formatting the exit status of a pluggable transport helper.
11529 This is probably not an exploitable bug, but better safe than
11530 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
11532 - Get rid of a couple of harmless clang warnings, where we compared
11533 enums to ints. These warnings are newly introduced in clang 3.2.
11535 o Minor bugfixes (code cleanliness):
11536 - Avoid use of reserved identifiers in our C code. The C standard
11537 doesn't like us declaring anything that starts with an
11538 underscore, so let's knock it off before we get in trouble. Fix
11539 for bug 1031; bugfix on the first Tor commit.
11540 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
11541 with large values. This situation was untriggered, but nevertheless
11542 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
11543 - Fix an impossible buffer overrun in the AES unit tests. Fixes
11544 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
11545 - Fix handling of rendezvous client authorization types over 8.
11546 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
11547 - Remove a couple of extraneous semicolons that were upsetting the
11548 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
11549 bugfix on 0.2.2.1-alpha.
11550 - When complaining about a client port on a public address, log
11551 which address we're complaining about. Fixes bug 4020; bugfix on
11552 0.2.3.3-alpha. Patch by Tom Fitzhenry.
11554 o Minor bugfixes (log messages, warnings):
11555 - If we encounter a write failure on a SOCKS connection before we
11556 finish our SOCKS handshake, don't warn that we closed the
11557 connection before we could send a SOCKS reply. Fixes bug 8427;
11558 bugfix on 0.1.0.1-rc.
11559 - Fix a directory authority warn caused when we have a large amount
11560 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
11561 - Downgrade "Failed to hand off onionskin" messages to "debug"
11562 severity, since they're typically redundant with the "Your computer
11563 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
11564 - Avoid spurious warnings when configuring multiple client ports of
11565 which only some are nonlocal. Previously, we had claimed that some
11566 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
11569 o Minor bugfixes (log messages, other):
11570 - Fix log messages and comments to avoid saying "GMT" when we mean
11571 "UTC". Fixes bug 6113.
11572 - When rejecting a configuration because we were unable to parse a
11573 quoted string, log an actual error message. Fixes bug 7950; bugfix
11575 - Correctly recognize that [::1] is a loopback address. Fixes
11576 bug 8377; bugfix on 0.2.1.3-alpha.
11577 - Don't log inappropriate heartbeat messages when hibernating: a
11578 hibernating node is _expected_ to drop out of the consensus,
11579 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
11580 bugfix on 0.2.3.1-alpha.
11581 - Eliminate several instances where we use "Nickname=ID" to refer to
11582 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
11583 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
11586 o Minor bugfixes (build):
11587 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
11588 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
11589 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
11591 o Documentation fixes:
11592 - Make the torify manpage no longer refer to tsocks; torify hasn't
11593 supported tsocks since 0.2.3.14-alpha.
11594 - Make the tor manpage no longer reference tsocks.
11595 - Fix the GeoIPExcludeUnknown documentation to refer to
11596 ExcludeExitNodes rather than the currently nonexistent
11597 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
11598 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
11600 - Say "KBytes" rather than "KB" in the man page (for various values
11601 of K), to further reduce confusion about whether Tor counts in
11602 units of memory or fractions of units of memory. Resolves ticket 7054.
11603 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
11604 names match. Fixes bug 7768.
11605 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
11606 message is logged at notice, not at info.
11607 - Clarify the usage and risks of setting the ContactInfo torrc line
11608 for your relay or bridge. Resolves ticket 9854.
11609 - Add anchors to the manpage so we can link to the html version of
11610 the documentation for specific options. Resolves ticket 9866.
11611 - Replace remaining references to DirServer in man page and
11612 log entries. Resolves ticket 10124.
11614 o Removed features:
11615 - Stop exporting estimates of v2 and v3 directory traffic shares
11616 in extrainfo documents. They were unneeded and sometimes inaccurate.
11617 Also stop exporting any v2 directory request statistics. Resolves
11619 - Drop support for detecting and warning about versions of Libevent
11620 before 1.3e. Nothing reasonable ships with them any longer; warning
11621 the user about them shouldn't be needed. Resolves ticket 6826.
11622 - Now that all versions before 0.2.2.x are disallowed, we no longer
11623 need to work around their missing features. Remove a bunch of
11624 compatibility code.
11627 - The tor-tsocks.conf is no longer distributed or installed. We
11628 recommend that tsocks users use torsocks instead. Resolves
11630 - Remove some of the older contents of doc/ as obsolete; move others
11631 to torspec.git. Fixes bug 8965.
11633 o Code simplification:
11634 - Avoid using character buffers when constructing most directory
11635 objects: this approach was unwieldy and error-prone. Instead,
11636 build smartlists of strings, and concatenate them when done.
11637 - Rename "isin" functions to "contains", for grammar. Resolves
11639 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
11640 with the natural logarithm function from the system libm. Resolves
11642 - Start using OpenBSD's implementation of queue.h, so that we don't
11643 need to hand-roll our own pointer and list structures whenever we
11644 need them. (We can't rely on a sys/queue.h, since some operating
11645 systems don't have them, and the ones that do have them don't all
11646 present the same extensions.)
11647 - Start using OpenBSD's implementation of queue.h (originally by
11649 - Enhance our internal sscanf replacement so that we can eliminate
11650 the last remaining uses of the system sscanf. (Though those uses
11651 of sscanf were safe, sscanf itself is generally error prone, so
11652 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
11654 - Replace all calls to snprintf() outside of src/ext with
11655 tor_snprintf(). Also remove the #define to replace snprintf with
11656 _snprintf on Windows; they have different semantics, and all of
11657 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
11660 - Add a wrapper function for the common "log a message with a
11662 - Split the onion.c file into separate modules for the onion queue
11663 and the different handshakes it supports.
11664 - Move the client-side address-map/virtual-address/DNS-cache code
11665 out of connection_edge.c into a new addressmap.c module.
11666 - Move the entry node code from circuitbuild.c to its own file.
11667 - Move the circuit build timeout tracking code from circuitbuild.c
11669 - Source files taken from other packages now reside in src/ext;
11670 previously they were scattered around the rest of Tor.
11671 - Move the generic "config" code into a new file, and have "config.c"
11672 hold only torrc- and state-related code. Resolves ticket 6823.
11673 - Move the core of our "choose a weighted element at random" logic
11674 into its own function, and give it unit tests. Now the logic is
11675 testable, and a little less fragile too.
11676 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
11677 - Move last_reachable and testing_since from routerinfo_t to node_t.
11678 Implements ticket 5529.
11679 - Add replaycache_t structure, functions and unit tests, then refactor
11680 rend_service_introduce() to be more clear to read, improve, debug,
11681 and test. Resolves bug 6177.
11684 - Remove some now-needless code that tried to aggressively flush
11685 OR connections as data was added to them. Since 0.2.0.1-alpha, our
11686 cell queue logic has saved us from the failure mode that this code
11687 was supposed to prevent. Removing this code will limit the number
11688 of baroque control flow paths through Tor's network logic. Reported
11689 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
11690 - Remove unused code for parsing v1 directories and "running routers"
11691 documents. Fixes bug 6887.
11692 - Remove the marshalling/unmarshalling code for sending requests to
11693 cpuworkers over a socket, and instead just send structs. The
11694 recipient will always be the same Tor binary as the sender, so
11695 any encoding is overkill.
11696 - Remove the testing_since field of node_t, which hasn't been used
11697 for anything since 0.2.0.9-alpha.
11698 - Finally remove support for malloc_good_size and malloc_usable_size.
11699 We had hoped that these functions would let us eke a little more
11700 memory out of our malloc implementation. Unfortunately, the only
11701 implementations that provided these functions are also ones that
11702 are already efficient about not overallocation: they never got us
11703 more than 7 or so bytes per allocation. Removing them saves us a
11704 little code complexity and a nontrivial amount of build complexity.
11707 Changes in version 0.2.3.25 - 2012-11-19
11708 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
11709 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
11710 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
11711 programmer, and friend. Unstinting in his dedication to the cause of
11712 freedom, he inspired and helped many of us as we began our work on
11713 anonymity, and inspires us still. Please honor his memory by writing
11714 software to protect people's freedoms, and by helping others to do so.
11716 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
11717 significantly reduced directory overhead (via microdescriptors),
11718 enormous crypto performance improvements for fast relays on new
11719 enough hardware, a new v3 TLS handshake protocol that can better
11720 resist fingerprinting, support for protocol obfuscation plugins (aka
11721 pluggable transports), better scalability for hidden services, IPv6
11722 support for bridges, performance improvements like allowing clients
11723 to skip the first round-trip on the circuit ("optimistic data") and
11724 refilling token buckets more often, a new "stream isolation" design
11725 to isolate different applications on different circuits, and many
11726 stability, security, and privacy fixes.
11728 Major features (v3 directory protocol):
11729 - Clients now use microdescriptors instead of regular descriptors
11730 to build circuits. Microdescriptors are authority-generated
11731 summaries of regular descriptors' contents, designed to change very
11732 rarely (see proposal 158 for details). This feature is designed
11733 to save bandwidth, especially for clients on slow internet
11734 connections. Use "UseMicrodescriptors 0" to disable it.
11735 - Caches now download, cache, and serve microdescriptors, as well
11736 as multiple "flavors" of the consensus, including a flavor that
11737 describes microdescriptors.
11739 o Major features (build hardening):
11740 - Enable gcc and ld hardening by default. Resolves ticket 5210.
11742 o Major features (relay scaling):
11743 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
11744 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
11745 vectorized AES implementations as appropriate. These can be much,
11746 much faster than other AES implementations.
11747 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
11748 implementation. It makes AES_CTR about 7% faster than our old one
11749 (which was about 10% faster than the one OpenSSL used to provide).
11750 Resolves ticket 4526.
11751 - Use OpenSSL's EVP interface for AES encryption, so that all AES
11752 operations can use hardware acceleration (if present). Resolves
11754 - Unconditionally use OpenSSL's AES implementation instead of our
11755 old built-in one. OpenSSL's AES has been better for a while, and
11756 relatively few servers should still be on any version of OpenSSL
11757 that doesn't have good optimized assembly AES.
11759 o Major features (blocking resistance):
11760 - Update TLS cipher list to match Firefox 8 and later. Resolves
11762 - Remove support for clients falsely claiming to support standard
11763 ciphersuites that they can actually provide. As of modern OpenSSL
11764 versions, it's not necessary to fake any standard ciphersuite,
11765 and doing so prevents us from using better ciphersuites in the
11766 future, since servers can't know whether an advertised ciphersuite
11767 is really supported or not. Some hosts -- notably, ones with very
11768 old versions of OpenSSL or where OpenSSL has been built with ECC
11769 disabled -- will stand out because of this change; TBB users should
11770 not be affected. Implements the client side of proposal 198.
11771 - Implement a new handshake protocol (v3) for authenticating Tors to
11772 each other over TLS. It should be more resistant to fingerprinting
11773 than previous protocols, and should require less TLS hacking for
11774 future Tor implementations. Implements proposal 176.
11775 - Allow variable-length padding cells, to disguise the length of
11776 Tor's TLS records. Implements part of proposal 184.
11777 - While we're trying to bootstrap, record how many TLS connections
11778 fail in each state, and report which states saw the most failures
11779 in response to any bootstrap failures. This feature may speed up
11780 diagnosis of censorship events. Implements ticket 3116.
11782 o Major features (pluggable transports):
11783 - Clients and bridges can now be configured to use a separate
11784 "transport" proxy. This approach makes the censorship arms race
11785 easier by allowing bridges to use protocol obfuscation plugins.
11786 Implements proposal 180 (tickets 2841 and 3472).
11788 o Major features (DoS resistance):
11789 - Now that Tor 0.2.0.x is completely deprecated, enable the final
11790 part of "Proposal 110: Avoiding infinite length circuits" by
11791 refusing all circuit-extend requests that do not use a relay_early
11792 cell. This change helps Tor resist a class of denial-of-service
11793 attacks by limiting the maximum circuit length.
11794 - Tear down the circuit if we get an unexpected SENDME cell. Clients
11795 could use this trick to make their circuits receive cells faster
11796 than our flow control would have allowed, or to gum up the network,
11797 or possibly to do targeted memory denial-of-service attacks on
11798 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
11799 from July 2002, before the release of Tor 0.0.0.
11801 o Major features (hidden services):
11802 - Adjust the number of introduction points that a hidden service
11803 will try to maintain based on how long its introduction points
11804 remain in use and how many introductions they handle. Fixes
11806 - Add a "tor2web mode" for clients that want to connect to hidden
11807 services non-anonymously (and possibly more quickly). As a safety
11808 measure to try to keep users from turning this on without knowing
11809 what they are doing, tor2web mode must be explicitly enabled at
11810 compile time, and a copy of Tor compiled to run in tor2web mode
11811 cannot be used as a normal Tor client. Implements feature 2553.
11813 o Major features (IPv6):
11814 - Clients can now connect to private bridges over IPv6. Bridges
11815 still need at least one IPv4 address in order to connect to
11816 other relays. Note that we don't yet handle the case where the
11817 user has two bridge lines for the same bridge (one IPv4, one
11818 IPv6). Implements parts of proposal 186.
11820 o Major features (directory authorities):
11821 - Use a more secure consensus parameter voting algorithm. Now at
11822 least three directory authorities or a majority of them must
11823 vote on a given parameter before it will be included in the
11824 consensus. Implements proposal 178.
11825 - Remove the artificially low cutoff of 20KB to guarantee the Fast
11826 flag. In the past few years the average relay speed has picked
11827 up, and while the "top 7/8 of the network get the Fast flag" and
11828 "all relays with 20KB or more of capacity get the Fast flag" rules
11829 used to have the same result, now the top 7/8 of the network has
11830 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
11832 o Major features (performance):
11833 - Exit nodes now accept and queue data on not-yet-connected streams.
11834 Previously, the client wasn't allowed to send data until the
11835 stream was connected, which slowed down all connections. This
11836 change will enable clients to perform a "fast-start" on streams
11837 and send data without having to wait for a confirmation that the
11838 stream has opened. Patch from Ian Goldberg; implements the server
11839 side of Proposal 174.
11840 - When using an exit relay running 0.2.3.x, clients can now
11841 "optimistically" send data before the exit relay reports that
11842 the stream has opened. This saves a round trip when starting
11843 connections where the client speaks first (such as web browsing).
11844 This behavior is controlled by a consensus parameter (currently
11845 disabled). To turn it on or off manually, use the "OptimisticData"
11846 torrc option. Implements proposal 181; code by Ian Goldberg.
11847 - Add a new TokenBucketRefillInterval option to refill token buckets
11848 more frequently than once per second. This should improve network
11849 performance, alleviate queueing problems, and make traffic less
11850 bursty. Implements proposal 183; closes ticket 3630. Design by
11851 Florian Tschorsch and Björn Scheuermann; implementation by
11853 - Raise the threshold of server descriptors needed (75%) and exit
11854 server descriptors needed (50%) before we will declare ourselves
11855 bootstrapped. This will make clients start building circuits a
11856 little later, but makes the initially constructed circuits less
11857 skewed and less in conflict with further directory fetches. Fixes
11860 o Major features (relays):
11861 - Relays now try regenerating and uploading their descriptor more
11862 frequently if they are not listed in the consensus, or if the
11863 version of their descriptor listed in the consensus is too
11864 old. This fix should prevent situations where a server declines
11865 to re-publish itself because it has done so too recently, even
11866 though the authorities decided not to list its recent-enough
11867 descriptor. Fix for bug 3327.
11869 o Major features (stream isolation):
11870 - You can now configure Tor so that streams from different
11871 applications are isolated on different circuits, to prevent an
11872 attacker who sees your streams as they leave an exit node from
11873 linking your sessions to one another. To do this, choose some way
11874 to distinguish the applications: have them connect to different
11875 SocksPorts, or have one of them use SOCKS4 while the other uses
11876 SOCKS5, or have them pass different authentication strings to the
11877 SOCKS proxy. Then, use the new SocksPort syntax to configure the
11878 degree of isolation you need. This implements Proposal 171.
11879 - There's a new syntax for specifying multiple client ports (such as
11880 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
11881 multiple *Port entries with full addr:port syntax on each.
11882 The old *ListenAddress format is still supported, but you can't
11883 mix it with the new *Port syntax.
11885 o Major features (bufferevents):
11886 - Tor can now optionally build with the "bufferevents" buffered IO
11887 backend provided by Libevent 2. To use this feature, make sure you
11888 have the latest possible version of Libevent, and pass the
11889 --enable-bufferevents flag to configure when building Tor from
11890 source. This feature will make our networking code more flexible,
11891 let us stack layers on each other, and let us use more efficient
11892 zero-copy transports where available.
11893 - Add experimental support for running on Windows with IOCP and no
11894 kernel-space socket buffers. This feature is controlled by a new
11895 "UserspaceIOCPBuffers" config option (off by default), which has
11896 no effect unless Tor has been built with bufferevents enabled,
11897 you're running on Windows, and you've set "DisableIOCP 0". In the
11898 long run, this may help solve or mitigate bug 98.
11900 o Major features (path selection):
11901 - The EntryNodes option can now include country codes like {de} or IP
11902 addresses or network masks. Previously we had disallowed these
11903 options because we didn't have an efficient way to keep the list up
11904 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
11907 o Major features (port forwarding):
11908 - Add support for automatic port mapping on the many home routers
11909 that support NAT-PMP or UPnP. To build the support code, you'll
11910 need to have the libnatpnp library and/or the libminiupnpc library,
11911 and you'll need to enable the feature specifically by passing
11912 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
11913 it on, use the new PortForwarding option.
11915 o Major features (logging):
11916 - Add a new 'Heartbeat' log message type to periodically log a message
11917 describing Tor's status at level Notice. This feature is meant for
11918 operators who log at notice, and want to make sure that their Tor
11919 server is still working. Implementation by George Kadianakis.
11920 - Make logging resolution configurable with a new LogTimeGranularity
11921 option, and change the default from 1 millisecond to 1 second.
11922 Implements enhancement 1668.
11924 o Major features (other):
11925 - New "DisableNetwork" config option to prevent Tor from launching any
11926 connections or accepting any connections except on a control port.
11927 Bundles and controllers can set this option before letting Tor talk
11928 to the rest of the network, for example to prevent any connections
11929 to a non-bridge address. Packages like Orbot can also use this
11930 option to instruct Tor to save power when the network is off.
11931 - Try to use system facilities for enumerating local interface
11932 addresses, before falling back to our old approach (which was
11933 binding a UDP socket, and calling getsockname() on it). That
11934 approach was scaring OS X users whose draconian firewall
11935 software warned about binding to UDP sockets regardless of
11936 whether packets were sent. Now we try to use getifaddrs(),
11937 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
11938 system supports. Resolves ticket 1827.
11939 - Add experimental support for a "defaults" torrc file to be parsed
11940 before the regular torrc. Torrc options override the defaults file's
11941 options in the same way that the command line overrides the torrc.
11942 The SAVECONF controller command saves only those options which
11943 differ between the current configuration and the defaults file. HUP
11944 reloads both files. Implements task 4552.
11946 o New directory authorities:
11947 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
11948 authority. Closes ticket 5749.
11950 o Security/privacy fixes:
11951 - Avoid read-from-freed-memory and double-free bugs that could occur
11952 when a DNS request fails while launching it. Fixes bug 6480;
11953 bugfix on 0.2.0.1-alpha.
11954 - Reject any attempt to extend to an internal address. Without
11955 this fix, a router could be used to probe addresses on an internal
11956 network to see whether they were accepting connections. Fixes bug
11957 6710; bugfix on 0.0.8pre1.
11958 - Close any connection that sends unrecognized junk before the TLS
11959 handshake. Solves an issue noted in bug 4369.
11960 - The advertised platform of a relay now includes only its operating
11961 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
11962 its service pack level (for Windows) or its CPU architecture
11963 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
11964 can insert an extra string in the platform line by setting the
11965 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
11966 - Disable TLS session tickets. OpenSSL's implementation was giving
11967 our TLS session keys the lifetime of our TLS context objects, when
11968 perfect forward secrecy would want us to discard anything that
11969 could decrypt a link connection as soon as the link connection
11970 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
11971 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
11972 - Tor tries to wipe potentially sensitive data after using it, so
11973 that if some subsequent security failure exposes Tor's memory,
11974 the damage will be limited. But we had a bug where the compiler
11975 was eliminating these wipe operations when it decided that the
11976 memory was no longer visible to a (correctly running) program,
11977 hence defeating our attempt at defense in depth. We fix that
11978 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
11979 is unlikely to optimize away. Future versions of Tor may use
11980 a less ridiculously heavy approach for this. Fixes bug 7352.
11981 Reported in an article by Andrey Karpov.
11983 o Major bugfixes (crashes and asserts):
11984 - Avoid a pair of double-free and use-after-mark bugs that can
11985 occur with certain timings in canceled and re-received DNS
11986 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
11987 - Fix a denial of service attack by which any directory authority
11988 could crash all the others, or by which a single v2 directory
11989 authority could crash everybody downloading v2 directory
11990 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
11991 - Fix an assert that directory authorities could trigger on sighup
11992 during some configuration state transitions. We now don't treat
11993 it as a fatal error when the new descriptor we just generated in
11994 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
11995 - Avoid segfault when starting up having run with an extremely old
11996 version of Tor and parsing its state file. Fixes bug 6801; bugfix
11999 o Major bugfixes (clients):
12000 - If we are unable to find any exit that supports our predicted ports,
12001 stop calling them predicted, so that we don't loop and build
12002 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
12003 which introduced predicted ports.
12004 - Check at each new consensus whether our entry guards were picked
12005 long enough ago that we should rotate them. Previously, we only
12006 did this check at startup, which could lead to us holding a guard
12007 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
12008 - When fetching a bridge descriptor from a bridge authority,
12009 always do so anonymously, whether we have been able to open
12010 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
12011 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
12012 but we'll need to wait for bug 6010 before it's actually usable.
12014 o Major bugfixes (directory voting):
12015 - Check more thoroughly to prevent a rogue authority from
12016 double-voting on any consensus directory parameter. Previously,
12017 authorities would crash in this case if the total number of
12018 votes for any parameter exceeded the number of active voters,
12019 but would let it pass otherwise. Partially fixes bug 5786; bugfix
12021 - When computing weight parameters, behave more robustly in the
12022 presence of a bad bwweightscale value. Previously, the authorities
12023 would crash if they agreed on a sufficiently broken weight_scale
12024 value; now, they use a reasonable default and carry on. Fixes the
12025 rest of bug 5786; bugfix on 0.2.2.17-alpha.
12026 - If authorities are unable to get a v2 consensus document from other
12027 directory authorities, they no longer fall back to fetching
12028 them from regular directory caches. Fixes bug 5635; bugfix on
12029 0.2.2.26-beta, where routers stopped downloading v2 consensus
12030 documents entirely.
12032 o Major bugfixes (relays):
12033 - Fix a bug handling SENDME cells on nonexistent streams that could
12034 result in bizarre window values. Report and patch contributed
12035 pseudonymously. Fixes part of bug 6271. This bug was introduced
12036 before the first Tor release, in svn commit r152.
12037 - Don't update the AccountingSoftLimitHitAt state file entry whenever
12038 tor gets started. This prevents a wrong average bandwidth
12039 estimate, which would cause relays to always start a new accounting
12040 interval at the earliest possible moment. Fixes bug 2003; bugfix
12041 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
12042 immensely in tracking this bug down.
12043 - Fix a possible crash bug when checking for deactivated circuits
12044 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
12045 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
12046 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
12047 connections. This change should allow busy exit relays to stop
12048 running out of available sockets as quickly. Fixes bug 4950;
12049 bugfix on 0.2.2.26-beta.
12051 o Major bugfixes (blocking resistance):
12052 - Bridges no longer include their address in NETINFO cells on outgoing
12053 OR connections, to allow them to blend in better with clients.
12054 Removes another avenue for enumerating bridges. Reported by
12055 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
12056 cells were introduced.
12057 - Warn the user when HTTPProxy, but no other proxy type, is
12058 configured. This can cause surprising behavior: it doesn't send
12059 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
12060 directory traffic only. Resolves ticket 4663.
12062 o Major bugfixes (hidden services):
12063 - Improve hidden service robustness: when an attempt to connect to
12064 a hidden service ends, be willing to refetch its hidden service
12065 descriptors from each of the HSDir relays responsible for them
12066 immediately. Previously, we would not consider refetching the
12067 service's descriptors from each HSDir for 15 minutes after the last
12068 fetch, which was inconvenient if the hidden service was not running
12069 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
12070 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
12071 They used to check that the timestamp was within 30 minutes
12072 of their system clock, so they could cap the size of their
12073 replay-detection cache, but that approach unnecessarily refused
12074 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
12075 the v3 intro-point protocol (the first one which sent a timestamp
12076 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
12077 - When one of a hidden service's introduction points appears to be
12078 unreachable, stop trying it. Previously, we would keep trying
12079 to build circuits to the introduction point until we lost the
12080 descriptor, usually because the user gave up and restarted Tor.
12081 Fixes part of bug 3825.
12083 o Changes to default torrc file:
12084 - Stop listing "socksport 9050" in torrc.sample. We open a socks
12085 port on 9050 by default anyway, so this should not change anything
12087 - Stop mentioning the deprecated *ListenAddress options in
12088 torrc.sample. Fixes bug 5438.
12089 - Document unit of bandwidth-related options in sample torrc.
12091 - Fix broken URLs in the sample torrc file, and tell readers about
12092 the OutboundBindAddress, ExitPolicyRejectPrivate, and
12093 PublishServerDescriptor options. Addresses bug 4652.
12095 o Minor features (directory authorities):
12096 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
12097 change when the authority is deciding whether to accept a newly
12098 uploaded descriptor. Implements ticket 6423.
12099 - Directory authorities are now a little more lenient at accepting
12100 older router descriptors, or newer router descriptors that don't
12101 make big changes. This should help ameliorate past and future
12102 issues where routers think they have uploaded valid descriptors,
12103 but the authorities don't think so. Fix for ticket 2479.
12104 - Authority operators can now vote for all relays in a given
12105 set of countries to be BadDir/BadExit/Invalid/Rejected.
12106 - Provide two consensus parameters (FastFlagMinThreshold and
12107 FastFlagMaxThreshold) to control the range of allowable bandwidths
12108 for the Fast directory flag. These allow authorities to run
12109 experiments on appropriate requirements for being a "Fast" node.
12110 The AuthDirFastGuarantee config value still applies. Implements
12113 o Minor features (bridges / bridge authorities):
12114 - Make bridge SSL certificates a bit more stealthy by using random
12115 serial numbers, in the same fashion as OpenSSL when generating
12116 self-signed certificates. Implements ticket 4584.
12117 - Tag a bridge's descriptor as "never to be sent unencrypted".
12118 This shouldn't matter, since bridges don't open non-anonymous
12119 connections to the bridge authority and don't allow unencrypted
12120 directory connections from clients, but we might as well make
12121 sure. Closes bug 5139.
12122 - The Bridge Authority now writes statistics on how many bridge
12123 descriptors it gave out in total, and how many unique descriptors
12124 it gave out. It also lists how often the most and least commonly
12125 fetched descriptors were given out, as well as the median and
12126 25th/75th percentile. Implements tickets 4200 and 4294.
12128 o Minor features (IPv6):
12129 - Make the code that clients use to detect an address change be
12130 IPv6-aware, so that it won't fill clients' logs with error
12131 messages when trying to get the IPv4 address of an IPv6
12132 connection. Implements ticket 5537.
12133 - Relays now understand an IPv6 address when they get one from a
12134 directory server. Resolves ticket 4875.
12136 o Minor features (hidden services):
12137 - Expire old or over-used hidden service introduction points.
12138 Required by fix for bug 3460.
12139 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
12140 public key replay-detection cache from 60 minutes to 5 minutes. This
12141 replay-detection cache is now used only to detect multiple
12142 INTRODUCE2 cells specifying the same rendezvous point, so we can
12143 avoid launching multiple simultaneous attempts to connect to it.
12144 - When a hidden service's introduction point times out, consider
12145 trying it again during the next attempt to connect to the
12146 HS. Previously, we would not try it again unless a newly fetched
12147 descriptor contained it. Required by fixes for bugs 1297 and 3825.
12149 o Minor features (relays):
12150 - Relays now include a reason for regenerating their descriptors
12151 in an HTTP header when uploading to the authorities. This will
12152 make it easier to debug descriptor-upload issues in the future.
12153 - Turn on directory request statistics by default and include them in
12154 extra-info descriptors. Don't break if we have no GeoIP database.
12155 - Replace files in stats/ rather than appending to them. Now that we
12156 include statistics in extra-info descriptors, it makes no sense to
12157 keep old statistics forever. Implements ticket 2930.
12158 - Relays that set "ConnDirectionStatistics 1" write statistics on the
12159 bidirectional use of connections to disk every 24 hours.
12160 - Add a GeoIP file digest to the extra-info descriptor. Implements
12163 o Minor features (new config options):
12164 - New config option "DynamicDHGroups" (disabled by default) provides
12165 each bridge with a unique prime DH modulus to be used during
12166 SSL handshakes. This option attempts to help against censors
12167 who might use the Apache DH modulus as a static identifier for
12168 bridges. Addresses ticket 4548.
12169 - New config option "DisableDebuggerAttachment" (on by default)
12170 to prevent basic debugging attachment attempts by other processes.
12171 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
12172 - Ordinarily, Tor does not count traffic from private addresses (like
12173 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
12174 There is now a new option, CountPrivateBandwidth, to disable this
12175 behavior. Patch from Daniel Cagara.
12177 o Minor features (different behavior for old config options):
12178 - Allow MapAddress directives to specify matches against super-domains,
12179 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
12180 Implements issue 933.
12181 - Don't disable the DirPort when we cannot exceed our AccountingMax
12182 limit during this interval because the effective bandwidthrate is
12183 low enough. This is useful in a situation where AccountMax is only
12184 used as an additional safeguard or to provide statistics.
12185 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
12186 implements ticket 3439.
12187 - When configuring a large set of nodes in EntryNodes, and there are
12188 enough of them listed as Guard so that we don't need to consider
12189 the non-guard entries, prefer the ones listed with the Guard flag.
12190 - If you set the NumCPUs option to 0, Tor will now try to detect how
12191 many CPUs you have. This is the new default behavior.
12192 - The NodeFamily option -- which let you declare that you want to
12193 consider nodes to be part of a family whether they list themselves
12194 that way or not -- now allows IP address ranges and country codes.
12196 o Minor features (new command-line config behavior):
12197 - Slightly change behavior of "list" options (that is, config
12198 options that can appear more than once) when they appear both in
12199 torrc and on the command line. Previously, the command-line options
12200 would be appended to the ones from torrc. Now, the command-line
12201 options override the torrc options entirely. This new behavior
12202 allows the user to override list options (like exit policies and
12203 ports to listen on) from the command line, rather than simply
12204 appending to the list.
12205 - You can get the old (appending) command-line behavior for "list"
12206 options by prefixing the option name with a "+".
12207 - You can remove all the values for a "list" option from the command
12208 line without adding any new ones by prefixing the option name
12211 o Minor features (controller, new events):
12212 - Extend the control protocol to report flags that control a circuit's
12213 path selection in CIRC events and in replies to 'GETINFO
12214 circuit-status'. Implements part of ticket 2411.
12215 - Extend the control protocol to report the hidden service address
12216 and current state of a hidden-service-related circuit in CIRC
12217 events and in replies to 'GETINFO circuit-status'. Implements part
12219 - Include the creation time of a circuit in CIRC and CIRC2
12220 control-port events and the list produced by the 'GETINFO
12221 circuit-status' control-port command.
12222 - Add a new CONF_CHANGED event so that controllers can be notified
12223 of any configuration changes made by other controllers, or by the
12224 user. Implements ticket 1692.
12225 - Add a new SIGNAL event to the controller interface so that
12226 controllers can be notified when Tor handles a signal. Resolves
12227 issue 1955. Patch by John Brooks.
12229 o Minor features (controller, new getinfo options):
12230 - Expose our view of whether we have gone dormant to the controller,
12231 via a new "GETINFO dormant" value. Torbutton and other controllers
12232 can use this to avoid doing periodic requests through Tor while
12233 it's dormant (bug 4718). Resolves ticket 5954.
12234 - Add a new GETINFO option to get total bytes read and written. Patch
12235 from pipe, revised by atagar. Resolves ticket 2345.
12236 - Implement new GETINFO controller fields to provide information about
12237 the Tor process's pid, euid, username, and resource limits.
12239 o Minor features (controller, other):
12240 - Allow controllers to request an event notification whenever a
12241 circuit is cannibalized or its purpose is changed. Implements
12242 part of ticket 3457.
12243 - Use absolute path names when reporting the torrc filename in the
12244 control protocol, so a controller can more easily find the torrc
12245 file. Resolves bug 1101.
12246 - When reporting the path to the cookie file to the controller,
12247 give an absolute path. Resolves ticket 4881.
12249 o Minor features (log messages):
12250 - Add more information to a log statement that might help track down
12251 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
12252 non-IP address" messages (or any Bug messages, for that matter!),
12253 please let us know about it.
12254 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
12255 EntryNodes will have no effect. Resolves issue 2571.
12256 - Try to make the introductory warning message that Tor prints on
12257 startup more useful for actually finding help and information.
12258 Resolves ticket 2474.
12259 - When the system call to create a listener socket fails, log the
12260 error message explaining why. This may help diagnose bug 4027.
12262 o Minor features (other):
12263 - When we fail to initialize Libevent, retry with IOCP disabled so we
12264 don't need to turn on multi-threading support in Libevent, which in
12265 turn requires a working socketpair(). This is a workaround for bug
12266 4457, which affects Libevent versions from 2.0.1-alpha through
12268 - When starting as root and then changing our UID via the User
12269 control option, and we have a ControlSocket configured, make sure
12270 that the ControlSocket is owned by the same account that Tor will
12271 run under. Implements ticket 3421; fix by Jérémy Bobbio.
12272 - Accept attempts to include a password authenticator in the
12273 handshake, as supported by SOCKS5. This handles SOCKS clients that
12274 don't know how to omit a password when authenticating. Resolves
12276 - Check for and recover from inconsistency in the microdescriptor
12277 cache. This will make it harder for us to accidentally free a
12278 microdescriptor without removing it from the appropriate data
12279 structures. Fixes issue 3135; issue noted by "wanoskarnet".
12280 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
12282 o Minor bugfixes (code security):
12283 - Prevent a null-pointer dereference when receiving a data cell
12284 for a nonexistent stream when the circuit in question has an
12285 empty deliver window. We don't believe this is triggerable,
12286 since we don't currently allow deliver windows to become empty,
12287 but the logic is tricky enough that it's better to make the code
12288 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
12289 - Fix a (harmless) integer overflow in cell statistics reported by
12290 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
12291 - Fix our implementation of crypto_random_hostname() so it can't
12292 overflow on ridiculously large inputs. (No Tor version has ever
12293 provided this kind of bad inputs, but let's be correct in depth.)
12294 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
12295 - Add a (probably redundant) memory clear between iterations of
12296 the router status voting loop, to prevent future coding errors
12297 where data might leak between iterations of the loop. Resolves
12300 o Minor bugfixes (wrapper functions):
12301 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
12302 utility function used in the control-port code). This shouldn't
12303 ever happen unless Tor is completely out of memory, but if it did
12304 happen and Tor somehow recovered from it, Tor could have sent a log
12305 message to a control port in the middle of a reply to a controller
12306 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
12307 - Fix some (not actually triggerable) buffer size checks in usage of
12308 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
12310 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
12311 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
12312 - Enforce correct return behavior of tor_vsscanf() when the '%%'
12313 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
12314 - Make our replacement implementation of strtok_r() compatible with
12315 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
12316 bugfix on 0.2.2.1-alpha.
12317 - Find more places in the code that should have been testing for
12318 invalid sockets using the SOCKET_OK macro. Required for a fix
12319 for bug 4533. Bugfix on 0.2.2.28-beta.
12321 o Minor bugfixes (code correctness):
12322 - Check return value of fputs() when writing authority certificate
12323 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
12324 - When building Tor on Windows with -DUNICODE (not default), ensure
12325 that error messages, filenames, and DNS server names are always
12326 NUL-terminated when we convert them to a single-byte encoding.
12327 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
12328 - Fix a memory leak when trying to launch a DNS request when the
12329 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
12331 - Correct file sizes when reading binary files on Cygwin, to avoid
12332 a bug where Tor would fail to read its state file. Fixes bug 6844;
12333 bugfix on 0.1.2.7-alpha.
12334 - Make sure to set *socket_error in all error cases in
12335 connection_connect(), so it can't produce a warning about
12336 errno being zero from errno_to_orconn_end_reason(). Bugfix on
12337 0.2.1.1-alpha; resolves ticket 6028.
12338 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
12339 bug 4532; found by "troll_un".
12341 o Minor bugfixes (clients):
12342 - Allow one-hop directory-fetching circuits the full "circuit build
12343 timeout" period, rather than just half of it, before failing them
12344 and marking the relay down. This fix should help reduce cases where
12345 clients declare relays (or worse, bridges) unreachable because
12346 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
12347 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
12349 - Ensure we don't cannibalize circuits that are longer than three hops
12350 already, so we don't end up making circuits with 5 or more
12351 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
12352 0.1.0.1-rc which introduced cannibalization.
12354 o Minor bugfixes (relays):
12355 - Don't publish a new relay descriptor when we reload our onion key,
12356 unless the onion key has actually changed. Fixes bug 3263 and
12357 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
12358 - When relays refuse a "create" cell because their queue of pending
12359 create cells is too big (typically because their cpu can't keep up
12360 with the arrival rate), send back reason "resource limit" rather
12361 than reason "internal", so network measurement scripts can get a
12362 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
12363 - Exit nodes don't need to fetch certificates for authorities that
12364 they don't recognize; only directory authorities, bridges,
12365 and caches need to do that. Fixes part of bug 2297; bugfix on
12368 o Minor bugfixes (directory authority / mirrors):
12369 - Avoid O(n^2) performance characteristics when parsing a large
12370 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
12371 - Authorities no longer include any router in their microdescriptor
12372 consensuses for which they couldn't generate or agree on a
12373 microdescriptor. Fixes the second piece of bug 6404; fix on
12375 - When checking for requested signatures on the latest consensus
12376 before serving it to a client, make sure to check the right
12377 consensus flavor. Bugfix on 0.2.2.6-alpha.
12378 - Fix an edge case where TestingTorNetwork is set but the authorities
12379 and relays all have an uptime of zero, so the private Tor network
12380 could briefly lack support for hidden services. Fixes bug 3886;
12381 bugfix on 0.2.2.18-alpha.
12382 - Directory caches no longer refuse to clean out descriptors because
12383 of missing v2 networkstatus documents, unless they're configured
12384 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
12385 0.2.2.26-beta. Patch by Daniel Bryg.
12386 - Don't serve or accept v2 hidden service descriptors over a relay's
12387 DirPort. It's never correct to do so, and disabling it might
12388 make it more annoying to exploit any bugs that turn up in the
12389 descriptor-parsing code. Fixes bug 7149.
12391 o Minor bugfixes (hidden services, client-side):
12392 - Assert that hidden-service-related operations are not performed
12393 using single-hop circuits. Previously, Tor would assert that
12394 client-side streams are not attached to single-hop circuits,
12395 but not that other sensitive operations on the client and service
12396 side are not performed using single-hop circuits. Fixes bug 3332;
12398 - Avoid undefined behavior when parsing the list of supported
12399 rendezvous/introduction protocols in a hidden service descriptor.
12400 Previously, Tor would have confused (as-yet-unused) protocol version
12401 numbers greater than 32 with lower ones on many platforms. Fixes
12402 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
12403 - Don't close hidden service client circuits which have almost
12404 finished connecting to their destination when they reach
12405 the normal circuit-build timeout. Previously, we would close
12406 introduction circuits which are waiting for an acknowledgement
12407 from the introduction point, and rendezvous circuits which have
12408 been specified in an INTRODUCE1 cell sent to a hidden service,
12409 after the normal CBT. Now, we mark them as 'timed out', and launch
12410 another rendezvous attempt in parallel. This behavior change can
12411 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
12412 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
12414 o Minor bugfixes (hidden services, service-side):
12415 - Don't close hidden-service-side rendezvous circuits when they
12416 reach the normal circuit-build timeout. This behavior change can
12417 be disabled using the new
12418 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
12419 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
12420 - Don't launch more than 10 service-side introduction-point circuits
12421 for a hidden service in five minutes. Previously, we would consider
12422 launching more introduction-point circuits if at least one second
12423 had passed without any introduction-point circuits failing. Fixes
12424 bug 4607; bugfix on 0.0.7pre1.
12426 o Minor bugfixes (config option behavior):
12427 - If the user tries to set MyFamily on a bridge, refuse to
12428 do so, and warn about the security implications. Fixes bug 4657;
12429 bugfix on 0.2.0.3-alpha.
12430 - The "--quiet" and "--hush" options now apply not only to Tor's
12431 behavior before logs are configured, but also to Tor's behavior in
12432 the absence of configured logs. Fixes bug 3550; bugfix on
12434 - Change the AllowDotExit rules so they should actually work.
12435 We now enforce AllowDotExit only immediately after receiving an
12436 address via SOCKS or DNSPort: other sources are free to provide
12437 .exit addresses after the resolution occurs. Fixes bug 3940;
12438 bugfix on 0.2.2.1-alpha.
12439 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
12440 don't depend on the consensus parameters or compute adaptive
12441 timeouts when it is disabled. Fixes bug 5049; bugfix on
12443 - After we pick a directory mirror, we would refuse to use it if
12444 it's in our ExcludeExitNodes list, resulting in mysterious failures
12445 to bootstrap for people who just wanted to avoid exiting from
12446 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
12447 - When told to add a bridge with the same digest as a preexisting
12448 bridge but a different addr:port, change the addr:port as
12449 requested. Previously we would not notice the change. Fixes half
12450 of bug 5603; fix on 0.2.2.26-beta.
12452 o Minor bugfixes (controller):
12453 - Allow manual 'authenticate' commands to the controller interface
12454 from netcat (nc) as well as telnet. We were rejecting them because
12455 they didn't come with the expected whitespace at the end of the
12456 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
12457 - Report a real bootstrap problem to the controller on router
12458 identity mismatch. Previously we just said "foo", which probably
12459 made a lot of sense at the time. Fixes bug 4169; bugfix on
12461 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
12462 option is set to 0 (which Vidalia version 0.2.16 now does when
12463 a SAVECONF attempt fails), perform other actions that SIGHUP
12464 usually causes (like reopening the logs). Fixes bug 5095; bugfix
12466 - Correctly handle checking the permissions on the parent
12467 directory of a control socket in the root directory. Bug found
12468 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
12470 - End AUTHCHALLENGE error messages (in the control protocol) with
12471 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
12473 o Minor bugfixes (network reading/writing):
12474 - Disable writing on marked-for-close connections when they are
12475 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
12476 bug 5263; bugfix on 0.0.2pre13, where we first added a special
12477 case for flushing marked connections.
12478 - Make sure that there are no unhandled pending TLS errors before
12479 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
12480 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
12481 Bugfix on 0.1.0.5-rc; fixes bug 4528.
12482 - Detect SSL handshake even when the initial attempt to write the
12483 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
12484 - If the client fails to set a reasonable set of ciphersuites
12485 during its v2 handshake renegotiation, allow the renegotiation to
12486 continue nevertheless (i.e. send all the required certificates).
12487 Fixes bug 4591; bugfix on 0.2.0.20-rc.
12489 o Minor bugfixes (other):
12490 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
12491 resource exhaustion, so that clients can adjust their load to
12492 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
12493 started using END_STREAM_REASON_RESOURCELIMIT.
12494 - Don't check for whether the address we're using for outbound
12495 connections has changed until after the outbound connection has
12496 completed. On Windows, getsockname() doesn't succeed until the
12497 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
12498 - Don't hold a Windows file handle open for every file mapping;
12499 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
12501 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
12502 bugfix on 0.2.1.10-alpha.
12503 - If we fail to write a microdescriptor to the disk cache, do not
12504 continue replacing the old microdescriptor file. Fixes bug 2954;
12505 bugfix on 0.2.2.6-alpha.
12507 o Minor bugfixes (log messages, path selection):
12508 - Downgrade "set buildtimeout to low value" messages to "info"
12509 severity; they were never an actual problem, there was never
12510 anything reasonable to do about them, and they tended to spam logs
12511 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
12512 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
12513 more information to it, so that we can track it down in case it
12514 returns again. Mitigates bug 5235.
12515 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
12516 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
12517 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
12518 - Issue a log message if a guard completes less than 40% of your
12519 circuits. Threshold is configurable by torrc option
12520 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
12521 additional, off-by-default code to disable guards which fail too
12522 many circuits. Addresses ticket 5458.
12524 o Minor bugfixes (log messages, client):
12525 - Downgrade "Got a certificate, but we already have it" log messages
12526 from warning to info, except when we're a dirauth. Fixes bug 5238;
12527 bugfix on 0.2.1.7-alpha.
12528 - Fix the log message describing how we work around discovering
12529 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
12530 4837; bugfix on 0.2.2.9-alpha.
12531 - When logging about a disallowed .exit name, do not also call it
12532 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
12533 - Fix a log message suggesting that people contact a non-existent
12534 email address. Fixes bug 3448.
12535 - Rephrase the log message emitted if the TestSocks check is
12536 successful. Patch from Fabian Keil; fixes bug 4094.
12537 - Log (at debug level) whenever a circuit's purpose is changed.
12538 - Log SSL state transitions at log level DEBUG, log domain
12539 HANDSHAKE. This can be useful for debugging censorship events.
12540 Implements ticket 3264.
12541 - We now log which torrc file we're using on startup. Implements
12543 - Rate-limit log messages when asked to connect anonymously to
12544 a private address. When these hit, they tended to hit fast and
12545 often. Also, don't bother trying to connect to addresses that we
12546 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
12547 reply makes us think we have been lied to, even when the address the
12548 client tried to connect to was "localhost." Resolves ticket 2822.
12550 o Minor bugfixes (log messages, non-client):
12551 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
12552 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
12553 - Don't log that we have "decided to publish new relay descriptor"
12554 unless we are actually publishing a descriptor. Fixes bug 3942;
12555 bugfix on 0.2.2.28-beta.
12556 - Log which authority we're missing votes from when we go to fetch
12557 them from the other auths.
12558 - Replace "Sending publish request" log messages with "Launching
12559 upload", so that they no longer confusingly imply that we're
12560 sending something to a directory we might not even be connected
12561 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
12562 - Warn when Tor is configured to use accounting in a way that can
12563 link a hidden service to some other hidden service or public
12564 address. Resolves ticket 6490.
12565 - Fix a minor formatting issue in one of tor-gencert's error messages.
12569 - Update to the latest version of the tinytest unit testing framework.
12570 This includes a couple of bugfixes that can be relevant for
12571 running forked unit tests on Windows, and removes all reserved
12573 - Avoid a false positive in the util/threads unit test by increasing
12574 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
12575 - Make it possible to set the TestingTorNetwork configuration
12576 option using AlternateDirAuthority and AlternateBridgeAuthority
12577 as an alternative to setting DirServer. Addresses ticket 6377.
12578 - Add a unit test for the environment_variable_names_equal() function.
12579 - A wide variety of new unit tests by Esteban Manchado Velázquez.
12580 - Numerous new unit tests for functions in util.c and address.c by
12582 - The long-disabled benchmark tests are now split into their own
12583 ./src/test/bench binary.
12584 - The benchmark tests can now use more accurate timers than
12585 gettimeofday() when such timers are available.
12586 - Use tt_assert(), not tor_assert(), for checking for test failures.
12587 This makes the unit tests more able to go on in the event that
12590 o Build improvements:
12591 - Use the dead_strip option when building Tor on OS X. This reduces
12592 binary size by almost 19% when linking openssl and libevent
12593 statically, which we do for Tor Browser Bundle.
12594 - Provide a better error message about possible OSX Asciidoc failure
12595 reasons. Fixes bug 6436.
12596 - Detect attempts to build Tor on (as yet hypothetical) versions
12597 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
12598 fix for bug 4533. Bugfix on 0.2.2.28-beta.
12599 - On Windows, we now define the _WIN32_WINNT macros only if they
12600 are not already defined. This lets the person building Tor decide,
12601 if they want, to require a later version of Windows.
12602 - Our autogen.sh script now uses autoreconf to launch autoconf,
12603 automake, and so on. This is more robust against some of the failure
12604 modes associated with running the autotools pieces on their own.
12605 - Running "make version" now displays the version of Tor that
12606 we're about to build. Idea from katmagic; resolves issue 4400.
12607 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
12608 on 0.2.2.4-alpha; fixes bug 3427.
12609 - New --enable-static-tor configure option for building Tor as
12610 statically as possible. Idea, general hackery and thoughts from
12611 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
12613 - Limited, experimental support for building with nmake and MSVC.
12615 o Build requirements:
12616 - Building Tor with bufferevent support now requires Libevent
12617 2.0.13-stable or later. Previous versions of Libevent had bugs in
12618 SSL-related bufferevents and related issues that would make Tor
12619 work badly with bufferevents. Requiring 2.0.13-stable also allows
12620 Tor with bufferevents to take advantage of Libevent APIs
12621 introduced after 2.0.8-rc.
12622 - Our build system requires automake 1.6 or later to create the
12623 Makefile.in files. Previously, you could have used 1.4.
12624 This only affects developers and people building Tor from git;
12625 people who build Tor from the source distribution without changing
12626 the Makefile.am files should be fine.
12627 - Detect when we try to build on a platform that doesn't define
12628 AF_UNSPEC to 0. We don't work there, so refuse to compile.
12630 o Build fixes (compile/link):
12631 - Format more doubles with %f, not %lf. Patch from grarpamp to make
12632 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
12634 - When building with --enable-static-tor on OpenBSD, do not
12635 erroneously attempt to link -lrt. Fixes bug 5103.
12636 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
12637 that IPv6 stuff will compile on MSVC, and compilation issues
12638 will be easier to track down. Fixes bug 5861.
12639 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
12640 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
12641 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
12642 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
12644 o Build fixes (other):
12645 - Use the _WIN32 macro throughout our code to detect Windows.
12646 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
12648 - Properly handle the case where the build-tree is not the same
12649 as the source tree when generating src/common/common_sha1.i,
12650 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
12651 bugfix on 0.2.0.1-alpha.
12652 - During configure, search for library containing cos function as
12653 libm lives in libcore on some platforms (BeOS/Haiku). Linking
12654 against libm was hard-coded before. Fixes the first part of bug
12655 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
12657 - Prevent a false positive from the check-spaces script, by disabling
12658 the "whitespace between function name and (" check for functions
12661 o Packaging (RPM) changes:
12662 - Update our default RPM spec files to work with mock and rpmbuild
12663 on RHEL/Fedora. They have an updated set of dependencies and
12664 conflicts, a fix for an ancient typo when creating the "_tor"
12665 user, and better instructions. Thanks to Ondrej Mikle for the
12666 patch series. Fixes bug 6043.
12667 - On OpenSUSE, create the /var/run/tor directory on startup if it
12668 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
12670 o Code refactoring (safety):
12671 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
12672 10 lines. Also, don't nest them. Doing so in the past has
12673 led to hard-to-debug code. The new style is to use the
12674 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
12675 - Use macros to indicate OpenSSL versions, so we don't need to worry
12676 about accidental hexadecimal bit shifts.
12677 - Use tor_sscanf() in place of scanf() in more places through the
12678 code. This makes us a little more locale-independent, and
12679 should help shut up code-analysis tools that can't tell
12680 a safe sscanf string from a dangerous one.
12681 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
12682 - Use the smartlist_add_asprintf() alias more consistently.
12684 o Code refactoring (consolidate):
12685 - A major revision to our internal node-selecting and listing logic.
12686 Tor already had at least two major ways to look at the question of
12687 "which Tor servers do we know about": a list of router descriptors,
12688 and a list of entries in the current consensus. With
12689 microdescriptors, we're adding a third. Having so many systems
12690 without an abstraction layer over them was hurting the codebase.
12691 Now, we have a new "node_t" abstraction that presents a consistent
12692 interface to a client's view of a Tor node, and holds (nearly) all
12693 of the mutable state formerly in routerinfo_t and routerstatus_t.
12694 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
12695 Libevent's notion of cached time when possible.
12696 - Remove duplicate code for invoking getrlimit() from control.c.
12697 - Use OpenSSL's built-in SSL_state_string_long() instead of our
12698 own homebrewed ssl_state_to_string() replacement. Patch from
12699 Emile Snyder. Fixes bug 4653.
12700 - Change the symmetric cipher interface so that creating and
12701 initializing a stream cipher are no longer separate functions.
12703 o Code refactoring (separate):
12704 - Make a new "entry connection" struct as an internal subtype of "edge
12705 connection", to simplify the code and make exit connections smaller.
12706 - Split connection_about_to_close() into separate functions for each
12708 - Rewrite the listener-selection logic so that parsing which ports
12709 we want to listen on is now separate from binding to the ports
12712 o Code refactoring (name changes):
12713 - Rename a handful of old identifiers, mostly related to crypto
12714 structures and crypto functions. By convention, our "create an
12715 object" functions are called "type_new()", our "free an object"
12716 functions are called "type_free()", and our types indicate that
12717 they are types only with a final "_t". But a handful of older
12718 types and functions broke these rules, with function names like
12719 "type_create" or "subsystem_op_type", or with type names like
12721 - Rename Tor functions that turn strings into addresses, so that
12722 "parse" indicates that no hostname resolution occurs, and
12723 "lookup" indicates that hostname resolution may occur. This
12724 should help prevent mistakes in the future. Fixes bug 3512.
12725 - Use the name "CERTS" consistently to refer to the new cell type;
12726 we were calling it CERT in some places and CERTS in others.
12727 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
12728 invalid value, rather than just -1.
12729 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
12730 can pick them up when the tests aren't disabled. Bugfix on
12731 0.2.2.4-alpha which introduced tinytest.
12733 o Code refactoring (other):
12734 - Defensively refactor rend_mid_rendezvous() so that protocol
12735 violations and length checks happen in the beginning. Fixes
12737 - Remove the pure attribute from all functions that used it
12738 previously. In many cases we assigned it incorrectly, because the
12739 functions might assert or call impure functions, and we don't have
12740 evidence that keeping the pure attribute is worthwhile. Implements
12741 changes suggested in ticket 4421.
12742 - Move the replay-detection cache for the RSA-encrypted parts of
12743 INTRODUCE2 cells to the introduction point data structures.
12744 Previously, we would use one replay-detection cache per hidden
12745 service. Required by fix for bug 3460.
12746 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
12747 no longer link against Libevent: they never used it, but
12748 our library structure used to force them to link it.
12750 o Removed features and files:
12751 - Remove all internal support for unpadded RSA. We never used it, and
12752 it would be a bad idea to start.
12753 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
12755 - Remove some redundant #include directives throughout the code.
12756 Patch from Andrea Gelmini.
12757 - Remove some old code to remember statistics about which descriptors
12758 we've served as a directory mirror. The feature wasn't used and
12759 is outdated now that microdescriptors are around.
12760 - Remove some old code to work around even older versions of Tor that
12761 used forked processes to handle DNS requests. Such versions of Tor
12762 are no longer in use as relays.
12763 - The "torify" script no longer supports the "tsocks" socksifier
12764 tool, since tsocks doesn't support DNS and UDP right for Tor.
12765 Everyone should be using torsocks instead. Fixes bugs 3530 and
12766 5180. Based on a patch by "ugh".
12767 - Remove the torrc.bridge file: we don't use it for anything, and
12768 it had become badly desynchronized from torrc.sample. Resolves
12772 - Begin a doc/state-contents.txt file to explain the contents of
12773 the Tor state file. Fixes bug 2987.
12774 - Clarify the documentation for the Alternate*Authority options.
12776 - Document the --defaults-torrc option, and the new semantics for
12777 overriding, extending, and clearing lists of options. Closes
12779 - Add missing man page documentation for consensus and microdesc
12780 files. Resolves ticket 6732.
12781 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
12783 o Documentation fixes:
12784 - Improve the manual's documentation for the NT Service command-line
12785 options. Addresses ticket 3964.
12786 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
12787 - Document the changes to the ORPort and DirPort options, and the
12788 fact that {OR/Dir}ListenAddress is now unnecessary (and
12789 therefore deprecated). Resolves ticket 5597.
12790 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
12791 - Clarify that hidden services are TCP only. Fixes bug 6024.
12794 Changes in version 0.2.2.39 - 2012-09-11
12795 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
12799 - Fix an assertion failure in tor_timegm() that could be triggered
12800 by a badly formatted directory object. Bug found by fuzzing with
12801 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
12802 - Do not crash when comparing an address with port value 0 to an
12803 address policy. This bug could have been used to cause a remote
12804 assertion failure by or against directory authorities, or to
12805 allow some applications to crash clients. Fixes bug 6690; bugfix
12809 Changes in version 0.2.2.38 - 2012-08-12
12810 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
12811 attack that could in theory leak path information.
12814 - Avoid an uninitialized memory read when reading a vote or consensus
12815 document that has an unrecognized flavor name. This read could
12816 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
12817 - Try to leak less information about what relays a client is
12818 choosing to a side-channel attacker. Previously, a Tor client would
12819 stop iterating through the list of available relays as soon as it
12820 had chosen one, thus finishing a little earlier when it picked
12821 a router earlier in the list. If an attacker can recover this
12822 timing information (nontrivial but not proven to be impossible),
12823 they could learn some coarse-grained information about which relays
12824 a client was picking (middle nodes in particular are likelier to
12825 be affected than exits). The timing attack might be mitigated by
12826 other factors (see bug 6537 for some discussion), but it's best
12827 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
12830 Changes in version 0.2.2.37 - 2012-06-06
12831 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
12832 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
12836 - Work around a bug in OpenSSL that broke renegotiation with TLS
12837 1.1 and TLS 1.2. Without this workaround, all attempts to speak
12838 the v2 Tor connection protocol when both sides were using OpenSSL
12839 1.0.1 would fail. Resolves ticket 6033.
12840 - When waiting for a client to renegotiate, don't allow it to add
12841 any bytes to the input buffer. This fixes a potential DoS issue.
12842 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
12843 - Fix an edge case where if we fetch or publish a hidden service
12844 descriptor, we might build a 4-hop circuit and then use that circuit
12845 for exiting afterwards -- even if the new last hop doesn't obey our
12846 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
12849 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
12850 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
12853 - Tell GCC and Clang to check for any errors in format strings passed
12854 to the tor_v*(print|scan)f functions.
12857 Changes in version 0.2.2.36 - 2012-05-24
12858 Tor 0.2.2.36 updates the addresses for two of the eight directory
12859 authorities, fixes some potential anonymity and security issues,
12860 and fixes several crash bugs.
12862 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
12863 known flaws, and nobody should be using them. You should upgrade. If
12864 you're using a Linux or BSD and its packages are obsolete, stop using
12865 those packages and upgrade anyway.
12867 o Directory authority changes:
12868 - Change IP address for maatuska (v3 directory authority).
12869 - Change IP address for ides (v3 directory authority), and rename
12873 - When building or running with any version of OpenSSL earlier
12874 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
12875 versions have a bug (CVE-2011-4576) in which their block cipher
12876 padding includes uninitialized data, potentially leaking sensitive
12877 information to any peer with whom they make a SSLv3 connection. Tor
12878 does not use SSL v3 by default, but a hostile client or server
12879 could force an SSLv3 connection in order to gain information that
12880 they shouldn't have been able to get. The best solution here is to
12881 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
12882 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
12883 to make sure that the bug can't happen.
12884 - Never use a bridge or a controller-supplied node as an exit, even
12885 if its exit policy allows it. Found by wanoskarnet. Fixes bug
12886 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
12887 and 0.2.0.3-alpha (for bridge-purpose descriptors).
12888 - Only build circuits if we have a sufficient threshold of the total
12889 descriptors that are marked in the consensus with the "Exit"
12890 flag. This mitigates an attack proposed by wanoskarnet, in which
12891 all of a client's bridges collude to restrict the exit nodes that
12892 the client knows about. Fixes bug 5343.
12893 - Provide controllers with a safer way to implement the cookie
12894 authentication mechanism. With the old method, if another locally
12895 running program could convince a controller that it was the Tor
12896 process, then that program could trick the controller into telling
12897 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
12898 authentication method uses a challenge-response approach to prevent
12899 this attack. Fixes bug 5185; implements proposal 193.
12902 - Avoid logging uninitialized data when unable to decode a hidden
12903 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
12904 - Avoid a client-side assertion failure when receiving an INTRODUCE2
12905 cell on a general purpose circuit. Fixes bug 5644; bugfix on
12907 - Fix builds when the path to sed, openssl, or sha1sum contains
12908 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
12910 - Correct our replacements for the timeradd() and timersub() functions
12911 on platforms that lack them (for example, Windows). The timersub()
12912 function is used when expiring circuits, while timeradd() is
12913 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
12914 bugfix on 0.2.2.24-alpha.
12915 - Fix the SOCKET_OK test that we use to tell when socket
12916 creation fails so that it works on Win64. Fixes part of bug 4533;
12917 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
12920 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
12921 Fixes bug 5346; bugfix on 0.0.8pre3.
12922 - Make our number-parsing functions always treat too-large values
12923 as an error, even when those values exceed the width of the
12924 underlying type. Previously, if the caller provided these
12925 functions with minima or maxima set to the extreme values of the
12926 underlying integer type, these functions would return those
12927 values on overflow rather than treating overflow as an error.
12928 Fixes part of bug 5786; bugfix on 0.0.9.
12929 - Older Linux kernels erroneously respond to strange nmap behavior
12930 by having accept() return successfully with a zero-length
12931 socket. When this happens, just close the connection. Previously,
12932 we would try harder to learn the remote address: but there was
12933 no such remote address to learn, and our method for trying to
12934 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
12935 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
12936 - Correct parsing of certain date types in parse_http_time().
12937 Without this patch, If-Modified-Since would behave
12938 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
12939 Esteban Manchado Velázques.
12940 - Change the BridgePassword feature (part of the "bridge community"
12941 design, which is not yet implemented) to use a time-independent
12942 comparison. The old behavior might have allowed an adversary
12943 to use timing to guess the BridgePassword value. Fixes bug 5543;
12944 bugfix on 0.2.0.14-alpha.
12945 - Detect and reject certain misformed escape sequences in
12946 configuration values. Previously, these values would cause us
12947 to crash if received in a torrc file or over an authenticated
12948 control port. Bug found by Esteban Manchado Velázquez, and
12949 independently by Robert Connolly from Matta Consulting who further
12950 noted that it allows a post-authentication heap overflow. Patch
12951 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
12952 bugfix on 0.2.0.16-alpha.
12953 - Fix a compile warning when using the --enable-openbsd-malloc
12954 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
12955 - During configure, detect when we're building with clang version
12956 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
12957 CFLAGS. clang doesn't support them yet.
12958 - When sending an HTTP/1.1 proxy request, include a Host header.
12959 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
12960 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
12961 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
12962 - If we hit the error case where routerlist_insert() replaces an
12963 existing (old) server descriptor, make sure to remove that
12964 server descriptor from the old_routers list. Fix related to bug
12965 1776. Bugfix on 0.2.2.18-alpha.
12967 o Minor bugfixes (documentation and log messages):
12968 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
12969 Fixes bug 4856; bugfix on Tor 0.0.6.
12970 - Update "ClientOnly" man page entry to explain that there isn't
12971 really any point to messing with it. Resolves ticket 5005.
12972 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
12973 directory authority option (introduced in Tor 0.2.2.34).
12974 - Downgrade the "We're missing a certificate" message from notice
12975 to info: people kept mistaking it for a real problem, whereas it
12976 is seldom the problem even when we are failing to bootstrap. Fixes
12977 bug 5067; bugfix on 0.2.0.10-alpha.
12978 - Correctly spell "connect" in a log message on failure to create a
12979 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
12980 - Clarify the behavior of MaxCircuitDirtiness with hidden service
12981 circuits. Fixes issue 5259.
12984 - Directory authorities now reject versions of Tor older than
12985 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
12986 inclusive. These versions accounted for only a small fraction of
12987 the Tor network, and have numerous known security issues. Resolves
12989 - Update to the May 1 2012 Maxmind GeoLite Country database.
12992 - When sending or relaying a RELAY_EARLY cell, we used to convert
12993 it to a RELAY cell if the connection was using the v1 link
12994 protocol. This was a workaround for older versions of Tor, which
12995 didn't handle RELAY_EARLY cells properly. Now that all supported
12996 versions can handle RELAY_EARLY cells, and now that we're enforcing
12997 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
12998 remove this workaround. Addresses bug 4786.
13001 Changes in version 0.2.2.35 - 2011-12-16
13002 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
13003 buffers code. Absolutely everybody should upgrade.
13005 The bug relied on an incorrect calculation when making data continuous
13006 in one of our IO buffers, if the first chunk of the buffer was
13007 misaligned by just the wrong amount. The miscalculation would allow an
13008 attacker to overflow a piece of heap-allocated memory. To mount this
13009 attack, the attacker would need to either open a SOCKS connection to
13010 Tor's SocksPort (usually restricted to localhost), or target a Tor
13011 instance configured to make its connections through a SOCKS proxy
13012 (which Tor does not do by default).
13014 Good security practice requires that all heap-overflow bugs should be
13015 presumed to be exploitable until proven otherwise, so we are treating
13016 this as a potential code execution attack. Please upgrade immediately!
13017 This bug does not affect bufferevents-based builds of Tor. Special
13018 thanks to "Vektor" for reporting this issue to us!
13020 Tor 0.2.2.35 also fixes several bugs in previous versions, including
13021 crash bugs for unusual configurations, and a long-term bug that
13022 would prevent Tor from starting on Windows machines with draconian
13025 With this release, we remind everyone that 0.2.0.x has reached its
13026 formal end-of-life. Those Tor versions have many known flaws, and
13027 nobody should be using them. You should upgrade -- ideally to the
13028 0.2.2.x series. If you're using a Linux or BSD and its packages are
13029 obsolete, stop using those packages and upgrade anyway.
13031 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
13032 longer receive support after some time in early 2012.
13035 - Fix a heap overflow bug that could occur when trying to pull
13036 data into the first chunk of a buffer, when that chunk had
13037 already had some data drained from it. Fixes CVE-2011-2778;
13038 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
13039 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
13040 that it doesn't attempt to allocate a socketpair. This could cause
13041 some problems on Windows systems with overzealous firewalls. Fix for
13042 bug 4457; workaround for Libevent versions 2.0.1-alpha through
13044 - If we mark an OR connection for close based on a cell we process,
13045 don't process any further cells on it. We already avoid further
13046 reads on marked-for-close connections, but now we also discard the
13047 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
13048 which was the first version where we might mark a connection for
13049 close based on processing a cell on it.
13050 - Correctly sanity-check that we don't underflow on a memory
13051 allocation (and then assert) for hidden service introduction
13052 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
13053 bugfix on 0.2.1.5-alpha.
13054 - Fix a memory leak when we check whether a hidden service
13055 descriptor has any usable introduction points left. Fixes bug
13056 4424. Bugfix on 0.2.2.25-alpha.
13057 - Don't crash when we're running as a relay and don't have a GeoIP
13058 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
13059 we've had in the 0.2.3.x branch already.
13060 - When running as a client, do not print a misleading (and plain
13061 wrong) log message that we're collecting "directory request"
13062 statistics: clients don't collect statistics. Also don't create a
13063 useless (because empty) stats file in the stats/ directory. Fixes
13064 bug 4353; bugfix on 0.2.2.34.
13067 - Detect failure to initialize Libevent. This fix provides better
13068 detection for future instances of bug 4457.
13069 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
13070 function. This was eating up hideously large amounts of time on some
13071 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
13072 - Resolve an integer overflow bug in smartlist_ensure_capacity().
13073 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
13075 - Don't warn about unused log_mutex in log.c when building with
13076 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
13077 0.1.0.6-rc which introduced --disable-threads.
13078 - When configuring, starting, or stopping an NT service, stop
13079 immediately after the service configuration attempt has succeeded
13080 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
13081 - When sending a NETINFO cell, include the original address
13082 received for the other side, not its canonical address. Found
13083 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
13084 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
13085 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
13086 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
13087 occurred when a client tried to fetch a descriptor for a bridge
13088 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
13089 - Backport fixes for a pair of compilation warnings on Windows.
13090 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
13091 - If we had ever tried to call tor_addr_to_str on an address of
13092 unknown type, we would have done a strdup on an uninitialized
13093 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
13094 Reported by "troll_un".
13095 - Correctly detect and handle transient lookup failures from
13096 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
13097 Reported by "troll_un".
13098 - Fix null-pointer access that could occur if TLS allocation failed.
13099 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
13100 - Use tor_socket_t type for listener argument to accept(). Fixes bug
13101 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
13104 - Add two new config options for directory authorities:
13105 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
13106 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
13107 that is always sufficient to satisfy the bandwidth requirement for
13108 the Guard flag. Now it will be easier for researchers to simulate
13109 Tor networks with different values. Resolves ticket 4484.
13110 - When Tor ignores a hidden service specified in its configuration,
13111 include the hidden service's directory in the warning message.
13112 Previously, we would only tell the user that some hidden service
13113 was ignored. Bugfix on 0.0.6; fixes bug 4426.
13114 - Update to the December 6 2011 Maxmind GeoLite Country database.
13116 o Packaging changes:
13117 - Make it easier to automate expert package builds on Windows,
13118 by removing an absolute path from makensis.exe command.
13121 Changes in version 0.2.1.32 - 2011-12-16
13122 Tor 0.2.1.32 backports important security and privacy fixes for
13123 oldstable. This release is intended only for package maintainers and
13124 others who cannot use the 0.2.2 stable series. All others should be
13125 using Tor 0.2.2.x or newer.
13127 The Tor 0.2.1.x series will reach formal end-of-life some time in
13128 early 2012; we will stop releasing patches for it then.
13130 o Major bugfixes (also included in 0.2.2.x):
13131 - Correctly sanity-check that we don't underflow on a memory
13132 allocation (and then assert) for hidden service introduction
13133 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
13134 bugfix on 0.2.1.5-alpha.
13135 - Fix a heap overflow bug that could occur when trying to pull
13136 data into the first chunk of a buffer, when that chunk had
13137 already had some data drained from it. Fixes CVE-2011-2778;
13138 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
13141 - Update to the December 6 2011 Maxmind GeoLite Country database.
13144 Changes in version 0.2.2.34 - 2011-10-26
13145 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
13146 can deanonymize Tor users. Everybody should upgrade.
13148 The attack relies on four components: 1) Clients reuse their TLS cert
13149 when talking to different relays, so relays can recognize a user by
13150 the identity key in her cert. 2) An attacker who knows the client's
13151 identity key can probe each guard relay to see if that identity key
13152 is connected to that guard relay right now. 3) A variety of active
13153 attacks in the literature (starting from "Low-Cost Traffic Analysis
13154 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
13155 discover the guard relays that a Tor user visiting the website is using.
13156 4) Clients typically pick three guards at random, so the set of guards
13157 for a given user could well be a unique fingerprint for her. This
13158 release fixes components #1 and #2, which is enough to block the attack;
13159 the other two remain as open research problems. Special thanks to
13160 "frosty_un" for reporting the issue to us!
13162 Clients should upgrade so they are no longer recognizable by the TLS
13163 certs they present. Relays should upgrade so they no longer allow a
13164 remote attacker to probe them to test whether unpatched clients are
13165 currently connected to them.
13167 This release also fixes several vulnerabilities that allow an attacker
13168 to enumerate bridge relays. Some bridge enumeration attacks still
13169 remain; see for example proposal 188.
13171 o Privacy/anonymity fixes (clients):
13172 - Clients and bridges no longer send TLS certificate chains on
13173 outgoing OR connections. Previously, each client or bridge would
13174 use the same cert chain for all outgoing OR connections until
13175 its IP address changes, which allowed any relay that the client
13176 or bridge contacted to determine which entry guards it is using.
13177 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
13178 - If a relay receives a CREATE_FAST cell on a TLS connection, it
13179 no longer considers that connection as suitable for satisfying a
13180 circuit EXTEND request. Now relays can protect clients from the
13181 CVE-2011-2768 issue even if the clients haven't upgraded yet.
13182 - Directory authorities no longer assign the Guard flag to relays
13183 that haven't upgraded to the above "refuse EXTEND requests
13184 to client connections" fix. Now directory authorities can
13185 protect clients from the CVE-2011-2768 issue even if neither
13186 the clients nor the relays have upgraded yet. There's a new
13187 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
13188 to let us transition smoothly, else tomorrow there would be no
13191 o Privacy/anonymity fixes (bridge enumeration):
13192 - Bridge relays now do their directory fetches inside Tor TLS
13193 connections, like all the other clients do, rather than connecting
13194 directly to the DirPort like public relays do. Removes another
13195 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
13196 - Bridges relays now build circuits for themselves in a more similar
13197 way to how clients build them. Removes another avenue for
13198 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
13199 when bridges were introduced.
13200 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
13201 that they initiated. Relays could distinguish incoming bridge
13202 connections from client connections, creating another avenue for
13203 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
13204 Found by "frosty_un".
13207 - Fix a crash bug when changing node restrictions while a DNS lookup
13208 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
13210 - Don't launch a useless circuit after failing to use one of a
13211 hidden service's introduction points. Previously, we would
13212 launch a new introduction circuit, but not set the hidden service
13213 which that circuit was intended to connect to, so it would never
13214 actually be used. A different piece of code would then create a
13215 new introduction circuit correctly. Bug reported by katmagic and
13216 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
13219 - Change an integer overflow check in the OpenBSD_Malloc code so
13220 that GCC is less likely to eliminate it as impossible. Patch
13221 from Mansour Moufid. Fixes bug 4059.
13222 - When a hidden service turns an extra service-side introduction
13223 circuit into a general-purpose circuit, free the rend_data and
13224 intro_key fields first, so we won't leak memory if the circuit
13225 is cannibalized for use as another service-side introduction
13226 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
13227 - Bridges now skip DNS self-tests, to act a little more stealthily.
13228 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
13229 bridges. Patch by "warms0x".
13230 - Fix internal bug-checking logic that was supposed to catch
13231 failures in digest generation so that it will fail more robustly
13232 if we ask for a nonexistent algorithm. Found by Coverity Scan.
13233 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
13234 - Report any failure in init_keys() calls launched because our
13235 IP address has changed. Spotted by Coverity Scan. Bugfix on
13236 0.1.1.4-alpha; fixes CID 484.
13238 o Minor bugfixes (log messages and documentation):
13239 - Remove a confusing dollar sign from the example fingerprint in the
13240 man page, and also make the example fingerprint a valid one. Fixes
13241 bug 4309; bugfix on 0.2.1.3-alpha.
13242 - The next version of Windows will be called Windows 8, and it has
13243 a major version of 6, minor version of 2. Correctly identify that
13244 version instead of calling it "Very recent version". Resolves
13245 ticket 4153; reported by funkstar.
13246 - Downgrade log messages about circuit timeout calibration from
13247 "notice" to "info": they don't require or suggest any human
13248 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
13249 bugfix on 0.2.2.14-alpha.
13252 - Turn on directory request statistics by default and include them in
13253 extra-info descriptors. Don't break if we have no GeoIP database.
13254 Backported from 0.2.3.1-alpha; implements ticket 3951.
13255 - Update to the October 4 2011 Maxmind GeoLite Country database.
13258 Changes in version 0.2.1.31 - 2011-10-26
13259 Tor 0.2.1.31 backports important security and privacy fixes for
13260 oldstable. This release is intended only for package maintainers and
13261 others who cannot use the 0.2.2 stable series. All others should be
13262 using Tor 0.2.2.x or newer.
13264 o Security fixes (also included in 0.2.2.x):
13265 - Replace all potentially sensitive memory comparison operations
13266 with versions whose runtime does not depend on the data being
13267 compared. This will help resist a class of attacks where an
13268 adversary can use variations in timing information to learn
13269 sensitive data. Fix for one case of bug 3122. (Safe memcmp
13270 implementation by Robert Ransom based partially on code by DJB.)
13271 - Fix an assert in parsing router descriptors containing IPv6
13272 addresses. This one took down the directory authorities when
13273 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
13275 o Privacy/anonymity fixes (also included in 0.2.2.x):
13276 - Clients and bridges no longer send TLS certificate chains on
13277 outgoing OR connections. Previously, each client or bridge would
13278 use the same cert chain for all outgoing OR connections until
13279 its IP address changes, which allowed any relay that the client
13280 or bridge contacted to determine which entry guards it is using.
13281 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
13282 - If a relay receives a CREATE_FAST cell on a TLS connection, it
13283 no longer considers that connection as suitable for satisfying a
13284 circuit EXTEND request. Now relays can protect clients from the
13285 CVE-2011-2768 issue even if the clients haven't upgraded yet.
13286 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
13287 that they initiated. Relays could distinguish incoming bridge
13288 connections from client connections, creating another avenue for
13289 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
13290 Found by "frosty_un".
13291 - When receiving a hidden service descriptor, check that it is for
13292 the hidden service we wanted. Previously, Tor would store any
13293 hidden service descriptors that a directory gave it, whether it
13294 wanted them or not. This wouldn't have let an attacker impersonate
13295 a hidden service, but it did let directories pre-seed a client
13296 with descriptors that it didn't want. Bugfix on 0.0.6.
13297 - Avoid linkability based on cached hidden service descriptors: forget
13298 all hidden service descriptors cached as a client when processing a
13299 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
13300 - Make the bridge directory authority refuse to answer directory
13301 requests for "all" descriptors. It used to include bridge
13302 descriptors in its answer, which was a major information leak.
13303 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
13304 - Don't attach new streams to old rendezvous circuits after SIGNAL
13305 NEWNYM. Previously, we would keep using an existing rendezvous
13306 circuit if it remained open (i.e. if it were kept open by a
13307 long-lived stream, or if a new stream were attached to it before
13308 Tor could notice that it was old and no longer in use). Bugfix on
13309 0.1.1.15-rc; fixes bug 3375.
13311 o Minor bugfixes (also included in 0.2.2.x):
13312 - When we restart our relay, we might get a successful connection
13313 from the outside before we've started our reachability tests,
13314 triggering a warning: "ORPort found reachable, but I have no
13315 routerinfo yet. Failing to inform controller of success." This
13316 bug was harmless unless Tor is running under a controller
13317 like Vidalia, in which case the controller would never get a
13318 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
13320 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
13321 enabled. Fixes bug 1526.
13322 - Remove undocumented option "-F" from tor-resolve: it hasn't done
13323 anything since 0.2.1.16-rc.
13324 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
13325 None of the cases where we did this before were wrong, but by making
13326 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
13327 - Fix a rare crash bug that could occur when a client was configured
13328 with a large number of bridges. Fixes bug 2629; bugfix on
13329 0.2.1.2-alpha. Bugfix by trac user "shitlei".
13330 - Correct the warning displayed when a rendezvous descriptor exceeds
13331 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
13333 - Fix an uncommon assertion failure when running with DNSPort under
13334 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
13335 - When warning about missing zlib development packages during compile,
13336 give the correct package names. Bugfix on 0.2.0.1-alpha.
13337 - Require that introduction point keys and onion keys have public
13338 exponent 65537. Bugfix on 0.2.0.10-alpha.
13339 - Do not crash when our configuration file becomes unreadable, for
13340 example due to a permissions change, between when we start up
13341 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
13343 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
13345 - Always NUL-terminate the sun_path field of a sockaddr_un before
13346 passing it to the kernel. (Not a security issue: kernels are
13347 smart enough to reject bad sockaddr_uns.) Found by Coverity;
13348 CID #428. Bugfix on Tor 0.2.0.3-alpha.
13349 - Don't stack-allocate the list of supplementary GIDs when we're
13350 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
13351 could take up to 256K, which is way too much stack. Found by
13352 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
13354 o Minor bugfixes (only in 0.2.1.x):
13355 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
13356 rely on them. Bugfix on 0.2.1.30.
13357 - Use git revisions instead of svn revisions when generating our
13358 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
13360 o Minor features (also included in 0.2.2.x):
13361 - Adjust the expiration time on our SSL session certificates to
13362 better match SSL certs seen in the wild. Resolves ticket 4014.
13363 - Allow nameservers with IPv6 address. Resolves bug 2574.
13364 - Update to the October 4 2011 Maxmind GeoLite Country database.
13367 Changes in version 0.2.2.33 - 2011-09-13
13368 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
13369 TLS handshake that makes relays and bridges that run this new version
13370 reachable from Iran again.
13373 - Avoid an assertion failure when reloading a configuration with
13374 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
13375 3923; bugfix on 0.2.2.25-alpha.
13377 o Minor features (security):
13378 - Check for replays of the public-key encrypted portion of an
13379 INTRODUCE1 cell, in addition to the current check for replays of
13380 the g^x value. This prevents a possible class of active attacks
13381 by an attacker who controls both an introduction point and a
13382 rendezvous point, and who uses the malleability of AES-CTR to
13383 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
13384 that these attacks are infeasible (requiring the attacker to send
13385 on the order of zettabytes of altered cells in a short interval),
13386 but we'd rather block them off in case there are any classes of
13387 this attack that we missed. Reported by Willem Pinckaers.
13390 - Adjust the expiration time on our SSL session certificates to
13391 better match SSL certs seen in the wild. Resolves ticket 4014.
13392 - Change the default required uptime for a relay to be accepted as
13393 a HSDir (hidden service directory) from 24 hours to 25 hours.
13394 Improves on 0.2.0.10-alpha; resolves ticket 2649.
13395 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
13396 authorities to abstain from voting on assignment of the HSDir
13397 consensus flag. Related to bug 2649.
13398 - Update to the September 6 2011 Maxmind GeoLite Country database.
13400 o Minor bugfixes (documentation and log messages):
13401 - Correct the man page to explain that HashedControlPassword and
13402 CookieAuthentication can both be set, in which case either method
13403 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
13404 when we decided to allow these config options to both be set. Issue
13405 raised by bug 3898.
13406 - Demote the 'replay detected' log message emitted when a hidden
13407 service receives the same Diffie-Hellman public key in two different
13408 INTRODUCE2 cells to info level. A normal Tor client can cause that
13409 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
13410 fixes part of bug 2442.
13411 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
13412 level. There is nothing that a hidden service's operator can do
13413 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
13415 - Clarify a log message specifying the characters permitted in
13416 HiddenServiceAuthorizeClient client names. Previously, the log
13417 message said that "[A-Za-z0-9+-_]" were permitted; that could have
13418 given the impression that every ASCII character between "+" and "_"
13419 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
13422 - Provide a substitute implementation of lround() for MSVC, which
13423 apparently lacks it. Patch from Gisle Vanem.
13424 - Clean up some code issues that prevented Tor from building on older
13425 BSDs. Fixes bug 3894; reported by "grarpamp".
13426 - Search for a platform-specific version of "ar" when cross-compiling.
13427 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
13430 Changes in version 0.2.2.32 - 2011-08-27
13431 The Tor 0.2.2 release series is dedicated to the memory of Andreas
13432 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
13433 a founder of the PETS community, a leader in our field, a mentor,
13434 and a friend. He left us with these words: "I had the possibility
13435 to contribute to this world that is not as it should be. I hope I
13436 could help in some areas to make the world a better place, and that
13437 I could also encourage other people to be engaged in improving the
13438 world. Please, stay engaged. This world needs you, your love, your
13439 initiative -- now I cannot be part of that anymore."
13441 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
13442 ready. More than two years in the making, this release features improved
13443 client performance and hidden service reliability, better compatibility
13444 for Android, correct behavior for bridges that listen on more than
13445 one address, more extensible and flexible directory object handling,
13446 better reporting of network statistics, improved code security, and
13447 many many other features and bugfixes.
13449 o Major features (client performance):
13450 - When choosing which cells to relay first, relays now favor circuits
13451 that have been quiet recently, to provide lower latency for
13452 low-volume circuits. By default, relays enable or disable this
13453 feature based on a setting in the consensus. They can override
13454 this default by using the new "CircuitPriorityHalflife" config
13455 option. Design and code by Ian Goldberg, Can Tang, and Chris
13457 - Directory authorities now compute consensus weightings that instruct
13458 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
13459 and no flag. Clients use these weightings to distribute network load
13460 more evenly across these different relay types. The weightings are
13461 in the consensus so we can change them globally in the future. Extra
13462 thanks to "outofwords" for finding some nasty security bugs in
13463 the first implementation of this feature.
13465 o Major features (client performance, circuit build timeout):
13466 - Tor now tracks how long it takes to build client-side circuits
13467 over time, and adapts its timeout to local network performance.
13468 Since a circuit that takes a long time to build will also provide
13469 bad performance, we get significant latency improvements by
13470 discarding the slowest 20% of circuits. Specifically, Tor creates
13471 circuits more aggressively than usual until it has enough data
13472 points for a good timeout estimate. Implements proposal 151.
13473 - Circuit build timeout constants can be controlled by consensus
13474 parameters. We set good defaults for these parameters based on
13475 experimentation on broadband and simulated high-latency links.
13476 - Circuit build time learning can be disabled via consensus parameter
13477 or by the client via a LearnCircuitBuildTimeout config option. We
13478 also automatically disable circuit build time calculation if either
13479 AuthoritativeDirectory is set, or if we fail to write our state
13480 file. Implements ticket 1296.
13482 o Major features (relays use their capacity better):
13483 - Set SO_REUSEADDR socket option on all sockets, not just
13484 listeners. This should help busy exit nodes avoid running out of
13485 useable ports just because all the ports have been used in the
13486 near past. Resolves issue 2850.
13487 - Relays now save observed peak bandwidth throughput rates to their
13488 state file (along with total usage, which was already saved),
13489 so that they can determine their correct estimated bandwidth on
13490 restart. Resolves bug 1863, where Tor relays would reset their
13491 estimated bandwidth to 0 after restarting.
13492 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
13493 should give us approximately 40-50% more Guard-flagged nodes,
13494 improving the anonymity the Tor network can provide and also
13495 decreasing the dropoff in throughput that relays experience when
13496 they first get the Guard flag.
13497 - Directory authorities now take changes in router IP address and
13498 ORPort into account when determining router stability. Previously,
13499 if a router changed its IP or ORPort, the authorities would not
13500 treat it as having any downtime for the purposes of stability
13501 calculation, whereas clients would experience downtime since the
13502 change would take a while to propagate to them. Resolves issue 1035.
13503 - New AccelName and AccelDir options add support for dynamic OpenSSL
13504 hardware crypto acceleration engines.
13506 o Major features (relays control their load better):
13507 - Exit relays now try harder to block exit attempts from unknown
13508 relays, to make it harder for people to use them as one-hop proxies
13509 a la tortunnel. Controlled by the refuseunknownexits consensus
13510 parameter (currently enabled), or you can override it on your
13511 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
13512 based on a variant of proposal 163.
13513 - Add separate per-conn write limiting to go with the per-conn read
13514 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
13515 but never per-conn write limits.
13516 - New consensus params "bwconnrate" and "bwconnburst" to let us
13517 rate-limit client connections as they enter the network. It's
13518 controlled in the consensus so we can turn it on and off for
13519 experiments. It's starting out off. Based on proposal 163.
13521 o Major features (controllers):
13522 - Export GeoIP information on bridge usage to controllers even if we
13523 have not yet been running for 24 hours. Now Vidalia bridge operators
13524 can get more accurate and immediate feedback about their
13525 contributions to the network.
13526 - Add an __OwningControllerProcess configuration option and a
13527 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
13528 that when it exits, Tor will shut down. Implements feature 3049.
13530 o Major features (directory authorities):
13531 - Directory authorities now create, vote on, and serve multiple
13532 parallel formats of directory data as part of their voting process.
13533 Partially implements Proposal 162: "Publish the consensus in
13535 - Directory authorities now agree on and publish small summaries
13536 of router information that clients can use in place of regular
13537 server descriptors. This transition will allow Tor 0.2.3 clients
13538 to use far less bandwidth for downloading information about the
13539 network. Begins the implementation of Proposal 158: "Clients
13540 download consensus + microdescriptors".
13541 - The directory voting system is now extensible to use multiple hash
13542 algorithms for signatures and resource selection. Newer formats
13543 are signed with SHA256, with a possibility for moving to a better
13544 hash algorithm in the future.
13545 - Directory authorities can now vote on arbitrary integer values as
13546 part of the consensus process. This is designed to help set
13547 network-wide parameters. Implements proposal 167.
13549 o Major features and bugfixes (node selection):
13550 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
13551 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
13552 options. Previously, we had been ambiguous in describing what
13553 counted as an "exit" node, and what operations exactly "StrictNodes
13554 0" would permit. This created confusion when people saw nodes built
13555 through unexpected circuits, and made it hard to tell real bugs from
13556 surprises. Now the intended behavior is:
13557 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
13558 a node that delivers user traffic outside the Tor network.
13559 . "Entry", in the context of EntryNodes, means a node used as the
13560 first hop of a multihop circuit. It doesn't include direct
13561 connections to directory servers.
13562 . "ExcludeNodes" applies to all nodes.
13563 . "StrictNodes" changes the behavior of ExcludeNodes only. When
13564 StrictNodes is set, Tor should avoid all nodes listed in
13565 ExcludeNodes, even when it will make user requests fail. When
13566 StrictNodes is *not* set, then Tor should follow ExcludeNodes
13567 whenever it can, except when it must use an excluded node to
13568 perform self-tests, connect to a hidden service, provide a
13569 hidden service, fulfill a .exit request, upload directory
13570 information, or fetch directory information.
13571 Collectively, the changes to implement the behavior fix bug 1090.
13572 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
13573 change during a config reload, mark and discard all our origin
13574 circuits. This fix should address edge cases where we change the
13575 config options and but then choose a circuit that we created before
13577 - Make EntryNodes config option much more aggressive even when
13578 StrictNodes is not set. Before it would prepend your requested
13579 entrynodes to your list of guard nodes, but feel free to use others
13580 after that. Now it chooses only from your EntryNodes if any of
13581 those are available, and only falls back to others if a) they're
13582 all down and b) StrictNodes is not set.
13583 - Now we refresh your entry guards from EntryNodes at each consensus
13584 fetch -- rather than just at startup and then they slowly rot as
13585 the network changes.
13586 - Add support for the country code "{??}" in torrc options like
13587 ExcludeNodes, to indicate all routers of unknown country. Closes
13589 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
13590 a node is listed in both, it's treated as excluded.
13591 - ExcludeNodes now applies to directory nodes -- as a preference if
13592 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
13593 Don't exclude all the directory authorities and set StrictNodes to 1
13594 unless you really want your Tor to break.
13595 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
13596 - ExcludeExitNodes now overrides .exit requests.
13597 - We don't use bridges listed in ExcludeNodes.
13598 - When StrictNodes is 1:
13599 . We now apply ExcludeNodes to hidden service introduction points
13600 and to rendezvous points selected by hidden service users. This
13601 can make your hidden service less reliable: use it with caution!
13602 . If we have used ExcludeNodes on ourself, do not try relay
13603 reachability self-tests.
13604 . If we have excluded all the directory authorities, we will not
13605 even try to upload our descriptor if we're a relay.
13606 . Do not honor .exit requests to an excluded node.
13607 - When the set of permitted nodes changes, we now remove any mappings
13608 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
13610 - We never cannibalize a circuit that had excluded nodes on it, even
13611 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
13612 - Improve log messages related to excluded nodes.
13614 o Major features (misc):
13615 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
13616 to help Tor build correctly for Android phones.
13617 - The options SocksPort, ControlPort, and so on now all accept a
13618 value "auto" that opens a socket on an OS-selected port. A
13619 new ControlPortWriteToFile option tells Tor to write its
13620 actual control port or ports to a chosen file. If the option
13621 ControlPortFileGroupReadable is set, the file is created as
13622 group-readable. Now users can run two Tor clients on the same
13623 system without needing to manually mess with parameters. Resolves
13624 part of ticket 3076.
13625 - Tor now supports tunneling all of its outgoing connections over
13626 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
13627 configuration options. Code by Christopher Davis.
13629 o Code security improvements:
13630 - Replace all potentially sensitive memory comparison operations
13631 with versions whose runtime does not depend on the data being
13632 compared. This will help resist a class of attacks where an
13633 adversary can use variations in timing information to learn
13634 sensitive data. Fix for one case of bug 3122. (Safe memcmp
13635 implementation by Robert Ransom based partially on code by DJB.)
13636 - Enable Address Space Layout Randomization (ASLR) and Data Execution
13637 Prevention (DEP) by default on Windows to make it harder for
13638 attackers to exploit vulnerabilities. Patch from John Brooks.
13639 - New "--enable-gcc-hardening" ./configure flag (off by default)
13640 to turn on gcc compile time hardening options. It ensures
13641 that signed ints have defined behavior (-fwrapv), enables
13642 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
13643 with canaries (-fstack-protector-all), turns on ASLR protection if
13644 supported by the kernel (-fPIE, -pie), and adds additional security
13645 related warnings. Verified to work on Mac OS X and Debian Lenny.
13646 - New "--enable-linker-hardening" ./configure flag (off by default)
13647 to turn on ELF specific hardening features (relro, now). This does
13648 not work with Mac OS X or any other non-ELF binary format.
13649 - Always search the Windows system directory for system DLLs, and
13650 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
13651 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
13652 current and future memory pages via mlockall(). On supported
13653 platforms (modern Linux and probably BSD but not Windows or OS X),
13654 this should effectively disable any and all attempts to page out
13655 memory. This option requires that you start your Tor as root --
13656 if you use DisableAllSwap, please consider using the User option
13657 to properly reduce the privileges of your Tor.
13659 o Major bugfixes (crashes):
13660 - Fix crash bug on platforms where gmtime and localtime can return
13661 NULL. Windows 7 users were running into this one. Fixes part of bug
13662 2077. Bugfix on all versions of Tor. Found by boboper.
13663 - Introduce minimum/maximum values that clients will believe
13664 from the consensus. Now we'll have a better chance to avoid crashes
13665 or worse when a consensus param has a weird value.
13666 - Fix a rare crash bug that could occur when a client was configured
13667 with a large number of bridges. Fixes bug 2629; bugfix on
13668 0.2.1.2-alpha. Bugfix by trac user "shitlei".
13669 - Do not crash when our configuration file becomes unreadable, for
13670 example due to a permissions change, between when we start up
13671 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
13673 - If we're in the pathological case where there's no exit bandwidth
13674 but there is non-exit bandwidth, or no guard bandwidth but there
13675 is non-guard bandwidth, don't crash during path selection. Bugfix
13677 - Fix a crash bug when trying to initialize the evdns module in
13678 Libevent 2. Bugfix on 0.2.1.16-rc.
13680 o Major bugfixes (stability):
13681 - Fix an assert in parsing router descriptors containing IPv6
13682 addresses. This one took down the directory authorities when
13683 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
13684 - Fix an uncommon assertion failure when running with DNSPort under
13685 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
13686 - Treat an unset $HOME like an empty $HOME rather than triggering an
13687 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
13688 - More gracefully handle corrupt state files, removing asserts
13689 in favor of saving a backup and resetting state.
13690 - Instead of giving an assertion failure on an internal mismatch
13691 on estimated freelist size, just log a BUG warning and try later.
13692 Mitigates but does not fix bug 1125.
13693 - Fix an assert that got triggered when using the TestingTorNetwork
13694 configuration option and then issuing a GETINFO config-text control
13695 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
13696 - If the cached cert file is unparseable, warn but don't exit.
13698 o Privacy fixes (relays/bridges):
13699 - Don't list Windows capabilities in relay descriptors. We never made
13700 use of them, and maybe it's a bad idea to publish them. Bugfix
13702 - If the Nickname configuration option isn't given, Tor would pick a
13703 nickname based on the local hostname as the nickname for a relay.
13704 Because nicknames are not very important in today's Tor and the
13705 "Unnamed" nickname has been implemented, this is now problematic
13706 behavior: It leaks information about the hostname without being
13707 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
13708 introduced the Unnamed nickname. Reported by tagnaq.
13709 - Maintain separate TLS contexts and certificates for incoming and
13710 outgoing connections in bridge relays. Previously we would use the
13711 same TLS contexts and certs for incoming and outgoing connections.
13712 Bugfix on 0.2.0.3-alpha; addresses bug 988.
13713 - Maintain separate identity keys for incoming and outgoing TLS
13714 contexts in bridge relays. Previously we would use the same
13715 identity keys for incoming and outgoing TLS contexts. Bugfix on
13716 0.2.0.3-alpha; addresses the other half of bug 988.
13717 - Make the bridge directory authority refuse to answer directory
13718 requests for "all descriptors". It used to include bridge
13719 descriptors in its answer, which was a major information leak.
13720 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
13722 o Privacy fixes (clients):
13723 - When receiving a hidden service descriptor, check that it is for
13724 the hidden service we wanted. Previously, Tor would store any
13725 hidden service descriptors that a directory gave it, whether it
13726 wanted them or not. This wouldn't have let an attacker impersonate
13727 a hidden service, but it did let directories pre-seed a client
13728 with descriptors that it didn't want. Bugfix on 0.0.6.
13729 - Start the process of disabling ".exit" address notation, since it
13730 can be used for a variety of esoteric application-level attacks
13731 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
13733 - Reject attempts at the client side to open connections to private
13734 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
13735 a randomly chosen exit node. Attempts to do so are always
13736 ill-defined, generally prevented by exit policies, and usually
13737 in error. This will also help to detect loops in transparent
13738 proxy configurations. You can disable this feature by setting
13739 "ClientRejectInternalAddresses 0" in your torrc.
13740 - Log a notice when we get a new control connection. Now it's easier
13741 for security-conscious users to recognize when a local application
13742 is knocking on their controller door. Suggested by bug 1196.
13744 o Privacy fixes (newnym):
13745 - Avoid linkability based on cached hidden service descriptors: forget
13746 all hidden service descriptors cached as a client when processing a
13747 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
13748 - On SIGHUP, do not clear out all TrackHostExits mappings, client
13749 DNS cache entries, and virtual address mappings: that's what
13750 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
13751 - Don't attach new streams to old rendezvous circuits after SIGNAL
13752 NEWNYM. Previously, we would keep using an existing rendezvous
13753 circuit if it remained open (i.e. if it were kept open by a
13754 long-lived stream, or if a new stream were attached to it before
13755 Tor could notice that it was old and no longer in use). Bugfix on
13756 0.1.1.15-rc; fixes bug 3375.
13758 o Major bugfixes (relay bandwidth accounting):
13759 - Fix a bug that could break accounting on 64-bit systems with large
13760 time_t values, making them hibernate for impossibly long intervals.
13761 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
13762 - Fix a bug in bandwidth accounting that could make us use twice
13763 the intended bandwidth when our interval start changes due to
13764 daylight saving time. Now we tolerate skew in stored vs computed
13765 interval starts: if the start of the period changes by no more than
13766 50% of the period's duration, we remember bytes that we transferred
13767 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
13769 o Major bugfixes (bridges):
13770 - Bridges now use "reject *:*" as their default exit policy. Bugfix
13771 on 0.2.0.3-alpha. Fixes bug 1113.
13772 - If you configure your bridge with a known identity fingerprint,
13773 and the bridge authority is unreachable (as it is in at least
13774 one country now), fall back to directly requesting the descriptor
13775 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
13777 - Fix a bug where bridge users who configure the non-canonical
13778 address of a bridge automatically switch to its canonical
13779 address. If a bridge listens at more than one address, it
13780 should be able to advertise those addresses independently and
13781 any non-blocked addresses should continue to work. Bugfix on Tor
13782 0.2.0.3-alpha. Fixes bug 2510.
13783 - If you configure Tor to use bridge A, and then quit and
13784 configure Tor to use bridge B instead (or if you change Tor
13785 to use bridge B via the controller), it would happily continue
13786 to use bridge A if it's still reachable. While this behavior is
13787 a feature if your goal is connectivity, in some scenarios it's a
13788 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
13789 - When the controller configures a new bridge, don't wait 10 to 60
13790 seconds before trying to fetch its descriptor. Bugfix on
13791 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
13793 o Major bugfixes (directory authorities):
13794 - Many relays have been falling out of the consensus lately because
13795 not enough authorities know about their descriptor for them to get
13796 a majority of votes. When we deprecated the v2 directory protocol,
13797 we got rid of the only way that v3 authorities can hear from each
13798 other about other descriptors. Now authorities examine every v3
13799 vote for new descriptors, and fetch them from that authority. Bugfix
13801 - Authorities could be tricked into giving out the Exit flag to relays
13802 that didn't allow exiting to any ports. This bug could screw
13803 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
13804 1238. Bug discovered by Martin Kowalczyk.
13805 - If all authorities restart at once right before a consensus vote,
13806 nobody will vote about "Running", and clients will get a consensus
13807 with no usable relays. Instead, authorities refuse to build a
13808 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
13810 o Major bugfixes (stream-level fairness):
13811 - When receiving a circuit-level SENDME for a blocked circuit, try
13812 to package cells fairly from all the streams that had previously
13813 been blocked on that circuit. Previously, we had started with the
13814 oldest stream, and allowed each stream to potentially exhaust
13815 the circuit's package window. This gave older streams on any
13816 given circuit priority over newer ones. Fixes bug 1937. Detected
13817 originally by Camilo Viecco. This bug was introduced before the
13818 first Tor release, in svn commit r152: it is the new winner of
13819 the longest-lived bug prize.
13820 - Fix a stream fairness bug that would cause newer streams on a given
13821 circuit to get preference when reading bytes from the origin or
13822 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
13823 introduced before the first Tor release, in svn revision r152.
13824 - When the exit relay got a circuit-level sendme cell, it started
13825 reading on the exit streams, even if had 500 cells queued in the
13826 circuit queue already, so the circuit queue just grew and grew in
13827 some cases. We fix this by not re-enabling reading on receipt of a
13828 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
13829 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
13831 - Newly created streams were allowed to read cells onto circuits,
13832 even if the circuit's cell queue was blocked and waiting to drain.
13833 This created potential unfairness, as older streams would be
13834 blocked, but newer streams would gladly fill the queue completely.
13835 We add code to detect this situation and prevent any stream from
13836 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
13839 o Major bugfixes (hidden services):
13840 - Apply circuit timeouts to opened hidden-service-related circuits
13841 based on the correct start time. Previously, we would apply the
13842 circuit build timeout based on time since the circuit's creation;
13843 it was supposed to be applied based on time since the circuit
13844 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
13845 - Improve hidden service robustness: When we find that we have
13846 extended a hidden service's introduction circuit to a relay not
13847 listed as an introduction point in the HS descriptor we currently
13848 have, retry with an introduction point from the current
13849 descriptor. Previously we would just give up. Fixes bugs 1024 and
13850 1930; bugfix on 0.2.0.10-alpha.
13851 - Directory authorities now use data collected from their own
13852 uptime observations when choosing whether to assign the HSDir flag
13853 to relays, instead of trusting the uptime value the relay reports in
13854 its descriptor. This change helps prevent an attack where a small
13855 set of nodes with frequently-changing identity keys can blackhole
13856 a hidden service. (Only authorities need upgrade; others will be
13857 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
13858 - Stop assigning the HSDir flag to relays that disable their
13859 DirPort (and thus will refuse to answer directory requests). This
13860 fix should dramatically improve the reachability of hidden services:
13861 hidden services and hidden service clients pick six HSDir relays
13862 to store and retrieve the hidden service descriptor, and currently
13863 about half of the HSDir relays will refuse to work. Bugfix on
13864 0.2.0.10-alpha; fixes part of bug 1693.
13866 o Major bugfixes (misc):
13867 - Clients now stop trying to use an exit node associated with a given
13868 destination by TrackHostExits if they fail to reach that exit node.
13869 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
13870 - Fix a regression that caused Tor to rebind its ports if it receives
13871 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
13872 - Remove an extra pair of quotation marks around the error
13873 message in control-port STATUS_GENERAL BUG events. Bugfix on
13874 0.1.2.6-alpha; fixes bug 3732.
13876 o Minor features (relays):
13877 - Ensure that no empty [dirreq-](read|write)-history lines are added
13878 to an extrainfo document. Implements ticket 2497.
13879 - When bandwidth accounting is enabled, be more generous with how
13880 much bandwidth we'll use up before entering "soft hibernation".
13881 Previously, we'd refuse new connections and circuits once we'd
13882 used up 95% of our allotment. Now, we use up 95% of our allotment,
13883 AND make sure that we have no more than 500MB (or 3 hours of
13884 expected traffic, whichever is lower) remaining before we enter
13886 - Relays now log the reason for publishing a new relay descriptor,
13887 so we have a better chance of hunting down instances of bug 1810.
13888 Resolves ticket 3252.
13889 - Log a little more clearly about the times at which we're no longer
13890 accepting new connections (e.g. due to hibernating). Resolves
13892 - When AllowSingleHopExits is set, print a warning to explain to the
13893 relay operator why most clients are avoiding her relay.
13894 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
13895 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
13896 clients are already deprecated because of security bugs.
13898 o Minor features (network statistics):
13899 - Directory mirrors that set "DirReqStatistics 1" write statistics
13900 about directory requests to disk every 24 hours. As compared to the
13901 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
13902 improvements: 1) stats are written to disk exactly every 24 hours;
13903 2) estimated shares of v2 and v3 requests are determined as mean
13904 values, not at the end of a measurement period; 3) unresolved
13905 requests are listed with country code '??'; 4) directories also
13906 measure download times.
13907 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
13908 number of exit streams and transferred bytes per port to disk every
13910 - Relays that set "CellStatistics 1" write statistics on how long
13911 cells spend in their circuit queues to disk every 24 hours.
13912 - Entry nodes that set "EntryStatistics 1" write statistics on the
13913 rough number and origins of connecting clients to disk every 24
13915 - Relays that write any of the above statistics to disk and set
13916 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
13917 their extra-info documents. Implements proposal 166.
13919 o Minor features (GeoIP and statistics):
13920 - Provide a log message stating which geoip file we're parsing
13921 instead of just stating that we're parsing the geoip file.
13922 Implements ticket 2432.
13923 - Make sure every relay writes a state file at least every 12 hours.
13924 Previously, a relay could go for weeks without writing its state
13925 file, and on a crash could lose its bandwidth history, capacity
13926 estimates, client country statistics, and so on. Addresses bug 3012.
13927 - Relays report the number of bytes spent on answering directory
13928 requests in extra-info descriptors similar to {read,write}-history.
13929 Implements enhancement 1790.
13930 - Report only the top 10 ports in exit-port stats in order not to
13931 exceed the maximum extra-info descriptor length of 50 KB. Implements
13933 - If writing the state file to disk fails, wait up to an hour before
13934 retrying again, rather than trying again each second. Fixes bug
13935 2346; bugfix on Tor 0.1.1.3-alpha.
13936 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
13937 when we switch from being a public relay to a bridge. Otherwise
13938 there will still be clients that see the relay in their consensus,
13939 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
13941 - Update to the August 2 2011 Maxmind GeoLite Country database.
13943 o Minor features (clients):
13944 - When expiring circuits, use microsecond timers rather than
13945 one-second timers. This can avoid an unpleasant situation where a
13946 circuit is launched near the end of one second and expired right
13947 near the beginning of the next, and prevent fluctuations in circuit
13949 - If we've configured EntryNodes and our network goes away and/or all
13950 our entrynodes get marked down, optimistically retry them all when
13951 a new socks application request appears. Fixes bug 1882.
13952 - Always perform router selections using weighted relay bandwidth,
13953 even if we don't need a high capacity circuit at the time. Non-fast
13954 circuits now only differ from fast ones in that they can use relays
13955 not marked with the Fast flag. This "feature" could turn out to
13956 be a horrible bug; we should investigate more before it goes into
13958 - When we run out of directory information such that we can't build
13959 circuits, but then get enough that we can build circuits, log when
13960 we actually construct a circuit, so the user has a better chance of
13961 knowing what's going on. Fixes bug 1362.
13962 - Log SSL state transitions at debug level during handshake, and
13963 include SSL states in error messages. This may help debug future
13964 SSL handshake issues.
13966 o Minor features (directory authorities):
13967 - When a router changes IP address or port, authorities now launch
13968 a new reachability test for it. Implements ticket 1899.
13969 - Directory authorities now reject relays running any versions of
13970 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
13971 known bugs that keep RELAY_EARLY cells from working on rendezvous
13972 circuits. Followup to fix for bug 2081.
13973 - Directory authorities now reject relays running any version of Tor
13974 older than 0.2.0.26-rc. That version is the earliest that fetches
13975 current directory information correctly. Fixes bug 2156.
13976 - Directory authorities now do an immediate reachability check as soon
13977 as they hear about a new relay. This change should slightly reduce
13978 the time between setting up a relay and getting listed as running
13979 in the consensus. It should also improve the time between setting
13980 up a bridge and seeing use by bridge users.
13981 - Directory authorities no longer launch a TLS connection to every
13982 relay as they startup. Now that we have 2k+ descriptors cached,
13983 the resulting network hiccup is becoming a burden. Besides,
13984 authorities already avoid voting about Running for the first half
13985 hour of their uptime.
13986 - Directory authorities now log the source of a rejected POSTed v3
13987 networkstatus vote, so we can track failures better.
13988 - Backport code from 0.2.3.x that allows directory authorities to
13989 clean their microdescriptor caches. Needed to resolve bug 2230.
13991 o Minor features (hidden services):
13992 - Use computed circuit-build timeouts to decide when to launch
13993 parallel introduction circuits for hidden services. (Previously,
13994 we would retry after 15 seconds.)
13995 - Don't allow v0 hidden service authorities to act as clients.
13996 Required by fix for bug 3000.
13997 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
13998 by fix for bug 3000.
13999 - Make hidden services work better in private Tor networks by not
14000 requiring any uptime to join the hidden service descriptor
14001 DHT. Implements ticket 2088.
14002 - Log (at info level) when purging pieces of hidden-service-client
14003 state because of SIGNAL NEWNYM.
14005 o Minor features (controller interface):
14006 - New "GETINFO net/listeners/(type)" controller command to return
14007 a list of addresses and ports that are bound for listeners for a
14008 given connection type. This is useful when the user has configured
14009 "SocksPort auto" and the controller needs to know which port got
14010 chosen. Resolves another part of ticket 3076.
14011 - Have the controller interface give a more useful message than
14012 "Internal Error" in response to failed GETINFO requests.
14013 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
14014 event, to give information on the current rate of circuit timeouts
14015 over our stored history.
14016 - The 'EXTENDCIRCUIT' control port command can now be used with
14017 a circ id of 0 and no path. This feature will cause Tor to build
14018 a new 'fast' general purpose circuit using its own path selection
14020 - Added a BUILDTIMEOUT_SET controller event to describe changes
14021 to the circuit build timeout.
14022 - New controller command "getinfo config-text". It returns the
14023 contents that Tor would write if you send it a SAVECONF command,
14024 so the controller can write the file to disk itself.
14026 o Minor features (controller protocol):
14027 - Add a new ControlSocketsGroupWritable configuration option: when
14028 it is turned on, ControlSockets are group-writeable by the default
14029 group of the current user. Patch by Jérémy Bobbio; implements
14031 - Tor now refuses to create a ControlSocket in a directory that is
14032 world-readable (or group-readable if ControlSocketsGroupWritable
14033 is 0). This is necessary because some operating systems do not
14034 enforce permissions on an AF_UNIX sockets. Permissions on the
14035 directory holding the socket, however, seems to work everywhere.
14036 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
14037 not. This would lead to a cookie that is still not group readable.
14038 Closes bug 1843. Suggested by katmagic.
14039 - Future-proof the controller protocol a bit by ignoring keyword
14040 arguments we do not recognize.
14042 o Minor features (more useful logging):
14043 - Revise most log messages that refer to nodes by nickname to
14044 instead use the "$key=nickname at address" format. This should be
14045 more useful, especially since nicknames are less and less likely
14046 to be unique. Resolves ticket 3045.
14047 - When an HTTPS proxy reports "403 Forbidden", we now explain
14048 what it means rather than calling it an unexpected status code.
14049 Closes bug 2503. Patch from Michael Yakubovich.
14050 - Rate-limit a warning about failures to download v2 networkstatus
14051 documents. Resolves part of bug 1352.
14052 - Rate-limit the "your application is giving Tor only an IP address"
14053 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
14054 - Rate-limit "Failed to hand off onionskin" warnings.
14055 - When logging a rate-limited warning, we now mention how many messages
14056 got suppressed since the last warning.
14057 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
14058 2 no signature, 4 required" messages about consensus signatures
14059 easier to read, and make sure they get logged at the same severity
14060 as the messages explaining which keys are which. Fixes bug 1290.
14061 - Don't warn when we have a consensus that we can't verify because
14062 of missing certificates, unless those certificates are ones
14063 that we have been trying and failing to download. Fixes bug 1145.
14065 o Minor features (log domains):
14066 - Add documentation for configuring logging at different severities in
14067 different log domains. We've had this feature since 0.2.1.1-alpha,
14068 but for some reason it never made it into the manpage. Fixes
14070 - Make it simpler to specify "All log domains except for A and B".
14071 Previously you needed to say "[*,~A,~B]". Now you can just say
14073 - Add a "LogMessageDomains 1" option to include the domains of log
14074 messages along with the messages. Without this, there's no way
14075 to use log domains without reading the source or doing a lot
14077 - Add a new "Handshake" log domain for activities that happen
14078 during the TLS handshake.
14080 o Minor features (build process):
14081 - Make compilation with clang possible when using
14082 "--enable-gcc-warnings" by removing two warning options that clang
14083 hasn't implemented yet and by fixing a few warnings. Resolves
14085 - Detect platforms that brokenly use a signed size_t, and refuse to
14086 build there. Found and analyzed by doorss and rransom.
14087 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
14089 - Add support for statically linking zlib by specifying
14090 "--enable-static-zlib", to go with our support for statically
14091 linking openssl and libevent. Resolves bug 1358.
14092 - Instead of adding the svn revision to the Tor version string, report
14093 the git commit (when we're building from a git checkout).
14094 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
14096 - New --digests command-line switch to output the digests of the
14097 source files Tor was built with.
14098 - Generate our manpage and HTML documentation using Asciidoc. This
14099 change should make it easier to maintain the documentation, and
14100 produce nicer HTML. The build process fails if asciidoc cannot
14101 be found and building with asciidoc isn't disabled (via the
14102 "--disable-asciidoc" argument to ./configure. Skipping the manpage
14103 speeds up the build considerably.
14105 o Minor features (options / torrc):
14106 - Warn when the same option is provided more than once in a torrc
14107 file, on the command line, or in a single SETCONF statement, and
14108 the option is one that only accepts a single line. Closes bug 1384.
14109 - Warn when the user configures two HiddenServiceDir lines that point
14110 to the same directory. Bugfix on 0.0.6 (the version introducing
14111 HiddenServiceDir); fixes bug 3289.
14112 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
14113 do individual connection-level rate limiting of clients. The torrc
14114 config options with the same names trump the consensus params, if
14115 both are present. Replaces the old "bwconnrate" and "bwconnburst"
14116 consensus params which were broken from 0.2.2.7-alpha through
14117 0.2.2.14-alpha. Closes bug 1947.
14118 - New config option "WarnUnsafeSocks 0" disables the warning that
14119 occurs whenever Tor receives a socks handshake using a version of
14120 the socks protocol that can only provide an IP address (rather
14121 than a hostname). Setups that do DNS locally over Tor are fine,
14122 and we shouldn't spam the logs in that case.
14123 - New config option "CircuitStreamTimeout" to override our internal
14124 timeout schedule for how many seconds until we detach a stream from
14125 a circuit and try a new circuit. If your network is particularly
14126 slow, you might want to set this to a number like 60.
14127 - New options for SafeLogging to allow scrubbing only log messages
14128 generated while acting as a relay. Specify "SafeLogging relay" if
14129 you want to ensure that only messages known to originate from
14130 client use of the Tor process will be logged unsafely.
14131 - Time and memory units in the configuration file can now be set to
14132 fractional units. For example, "2.5 GB" is now a valid value for
14134 - Support line continuations in the torrc config file. If a line
14135 ends with a single backslash character, the newline is ignored, and
14136 the configuration value is treated as continuing on the next line.
14139 o Minor features (unit tests):
14140 - Revise our unit tests to use the "tinytest" framework, so we
14141 can run tests in their own processes, have smarter setup/teardown
14142 code, and so on. The unit test code has moved to its own
14143 subdirectory, and has been split into multiple modules.
14144 - Add a unit test for cross-platform directory-listing code.
14145 - Add some forgotten return value checks during unit tests. Found
14147 - Use GetTempDir to find the proper temporary directory location on
14148 Windows when generating temporary files for the unit tests. Patch
14151 o Minor features (misc):
14152 - The "torify" script now uses torsocks where available.
14153 - Make Libevent log messages get delivered to controllers later,
14154 and not from inside the Libevent log handler. This prevents unsafe
14155 reentrant Libevent calls while still letting the log messages
14157 - Certain Tor clients (such as those behind check.torproject.org) may
14158 want to fetch the consensus in an extra early manner. To enable this
14159 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
14160 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
14161 as only certain clients who must have this information sooner should
14163 - Expand homedirs passed to tor-checkkey. This should silence a
14164 coverity complaint about passing a user-supplied string into
14165 open() without checking it.
14166 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
14167 used on bridges, and it makes bridge scanning somewhat easier.
14168 - Create the /var/run/tor directory on startup on OpenSUSE if it is
14169 not already created. Patch from Andreas Stieger. Fixes bug 2573.
14171 o Minor bugfixes (relays):
14172 - When a relay decides that its DNS is too broken for it to serve
14173 as an exit server, it advertised itself as a non-exit, but
14174 continued to act as an exit. This could create accidental
14175 partitioning opportunities for users. Instead, if a relay is
14176 going to advertise reject *:* as its exit policy, it should
14177 really act with exit policy "reject *:*". Fixes bug 2366.
14178 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
14179 - Publish a router descriptor even if generating an extra-info
14180 descriptor fails. Previously we would not publish a router
14181 descriptor without an extra-info descriptor; this can cause fast
14182 exit relays collecting exit-port statistics to drop from the
14183 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
14184 - When we're trying to guess whether we know our IP address as
14185 a relay, we would log various ways that we failed to guess
14186 our address, but never log that we ended up guessing it
14187 successfully. Now add a log line to help confused and anxious
14188 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
14189 - For bandwidth accounting, calculate our expected bandwidth rate
14190 based on the time during which we were active and not in
14191 soft-hibernation during the last interval. Previously, we were
14192 also considering the time spent in soft-hibernation. If this
14193 was a long time, we would wind up underestimating our bandwidth
14194 by a lot, and skewing our wakeup time towards the start of the
14195 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
14196 - Demote a confusing TLS warning that relay operators might get when
14197 someone tries to talk to their ORPort. It is not the operator's
14198 fault, nor can they do anything about it. Fixes bug 1364; bugfix
14200 - Change "Application request when we're believed to be offline."
14201 notice to "Application request when we haven't used client
14202 functionality lately.", to clarify that it's not an error. Bugfix
14203 on 0.0.9.3; fixes bug 1222.
14205 o Minor bugfixes (bridges):
14206 - When a client starts or stops using bridges, never use a circuit
14207 that was built before the configuration change. This behavior could
14208 put at risk a user who uses bridges to ensure that her traffic
14209 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
14211 - Do not reset the bridge descriptor download status every time we
14212 re-parse our configuration or get a configuration change. Fixes
14213 bug 3019; bugfix on 0.2.0.3-alpha.
14214 - Users couldn't configure a regular relay to be their bridge. It
14215 didn't work because when Tor fetched the bridge descriptor, it found
14216 that it already had it, and didn't realize that the purpose of the
14217 descriptor had changed. Now we replace routers with a purpose other
14218 than bridge with bridge descriptors when fetching them. Bugfix on
14219 0.1.1.9-alpha. Fixes bug 1776.
14220 - In the special case where you configure a public exit relay as your
14221 bridge, Tor would be willing to use that exit relay as the last
14222 hop in your circuit as well. Now we fail that circuit instead.
14223 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
14225 o Minor bugfixes (clients):
14226 - We now ask the other side of a stream (the client or the exit)
14227 for more data on that stream when the amount of queued data on
14228 that stream dips low enough. Previously, we wouldn't ask the
14229 other side for more data until either it sent us more data (which
14230 it wasn't supposed to do if it had exhausted its window!) or we
14231 had completely flushed all our queued data. This flow control fix
14232 should improve throughput. Fixes bug 2756; bugfix on the earliest
14233 released versions of Tor (svn commit r152).
14234 - When a client finds that an origin circuit has run out of 16-bit
14235 stream IDs, we now mark it as unusable for new streams. Previously,
14236 we would try to close the entire circuit. Bugfix on 0.0.6.
14237 - Make it explicit that we don't cannibalize one-hop circuits. This
14238 happens in the wild, but doesn't turn out to be a problem because
14239 we fortunately don't use those circuits. Many thanks to outofwords
14240 for the initial analysis and to swissknife who confirmed that
14241 two-hop circuits are actually created.
14242 - Resolve an edge case in path weighting that could make us misweight
14243 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
14244 - Make the DNSPort option work with libevent 2.x. Don't alter the
14245 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
14247 o Minor bugfixes (directory authorities):
14248 - Make directory authorities more accurate at recording when
14249 relays that have failed several reachability tests became
14250 unreachable, so we can provide more accuracy at assigning Stable,
14251 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
14252 - Directory authorities are now more robust to hops back in time
14253 when calculating router stability. Previously, if a run of uptime
14254 or downtime appeared to be negative, the calculation could give
14255 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
14257 - Directory authorities will now attempt to download consensuses
14258 if their own efforts to make a live consensus have failed. This
14259 change means authorities that restart will fetch a valid
14260 consensus, and it means authorities that didn't agree with the
14261 current consensus will still fetch and serve it if it has enough
14262 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
14263 - Never vote for a server as "Running" if we have a descriptor for
14264 it claiming to be hibernating, and that descriptor was published
14265 more recently than our last contact with the server. Bugfix on
14266 0.2.0.3-alpha; fixes bug 911.
14267 - Directory authorities no longer change their opinion of, or vote on,
14268 whether a router is Running, unless they have themselves been
14269 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
14272 o Minor bugfixes (hidden services):
14273 - Log malformed requests for rendezvous descriptors as protocol
14274 warnings, not warnings. Also, use a more informative log message
14275 in case someone sees it at log level warning without prior
14276 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
14277 - Accept hidden service descriptors if we think we might be a hidden
14278 service directory, regardless of what our consensus says. This
14279 helps robustness, since clients and hidden services can sometimes
14280 have a more up-to-date view of the network consensus than we do,
14281 and if they think that the directory authorities list us a HSDir,
14282 we might actually be one. Related to bug 2732; bugfix on
14284 - Correct the warning displayed when a rendezvous descriptor exceeds
14285 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
14287 - Clients and hidden services now use HSDir-flagged relays for hidden
14288 service descriptor downloads and uploads even if the relays have no
14289 DirPort set and the client has disabled TunnelDirConns. This will
14290 eventually allow us to give the HSDir flag to relays with no
14291 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
14292 - Only limit the lengths of single HS descriptors, even when multiple
14293 HS descriptors are published to an HSDir relay in a single POST
14294 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
14296 o Minor bugfixes (controllers):
14297 - Allow GETINFO fingerprint to return a fingerprint even when
14298 we have not yet built a router descriptor. Fixes bug 3577;
14299 bugfix on 0.2.0.1-alpha.
14300 - Send a SUCCEEDED stream event to the controller when a reverse
14301 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
14302 discovered by katmagic.
14303 - Remove a trailing asterisk from "exit-policy/default" in the
14304 output of the control port command "GETINFO info/names". Bugfix
14306 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
14307 2917. Bugfix on 0.1.1.1-alpha.
14308 - When we restart our relay, we might get a successful connection
14309 from the outside before we've started our reachability tests,
14310 triggering a warning: "ORPort found reachable, but I have no
14311 routerinfo yet. Failing to inform controller of success." This
14312 bug was harmless unless Tor is running under a controller
14313 like Vidalia, in which case the controller would never get a
14314 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
14316 - When a controller changes TrackHostExits, remove mappings for
14317 hosts that should no longer have their exits tracked. Bugfix on
14319 - When a controller changes VirtualAddrNetwork, remove any mappings
14320 for hosts that were automapped to the old network. Bugfix on
14322 - When a controller changes one of the AutomapHosts* options, remove
14323 any mappings for hosts that should no longer be automapped. Bugfix
14325 - Fix an off-by-one error in calculating some controller command
14326 argument lengths. Fortunately, this mistake is harmless since
14327 the controller code does redundant NUL termination too. Found by
14328 boboper. Bugfix on 0.1.1.1-alpha.
14329 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
14330 would return "551 Internal error" rather than "552 Unrecognized key
14331 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
14332 - Don't spam the controller with events when we have no file
14333 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
14334 for log messages was already solved from bug 748.)
14335 - Emit a GUARD DROPPED controller event for a case we missed.
14336 - Ensure DNS requests launched by "RESOLVE" commands from the
14337 controller respect the __LeaveStreamsUnattached setconf options. The
14338 same goes for requests launched via DNSPort or transparent
14339 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
14341 o Minor bugfixes (config options):
14342 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
14343 Change the limit to 512 characters by removing base64 newlines.
14344 Fixes bug 2752. Fix by Michael Yakubovich.
14345 - Complain if PublishServerDescriptor is given multiple arguments that
14346 include 0 or 1. This configuration will be rejected in the future.
14347 Bugfix on 0.2.0.1-alpha; closes bug 1107.
14348 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
14349 Bugfix on 0.2.0.13-alpha; closes bug 928.
14351 o Minor bugfixes (log subsystem fixes):
14352 - When unable to format an address as a string, report its value
14353 as "???" rather than reusing the last formatted address. Bugfix
14355 - Be more consistent in our treatment of file system paths. "~" should
14356 get expanded to the user's home directory in the Log config option.
14357 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
14358 feature for the -f and --DataDirectory options.
14360 o Minor bugfixes (memory management):
14361 - Don't stack-allocate the list of supplementary GIDs when we're
14362 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
14363 could take up to 256K, which is way too much stack. Found by
14364 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
14365 - Save a couple bytes in memory allocation every time we escape
14366 certain characters in a string. Patch from Florian Zumbiehl.
14368 o Minor bugfixes (protocol correctness):
14369 - When checking for 1024-bit keys, check for 1024 bits, not 128
14370 bytes. This allows Tor to correctly discard keys of length 1017
14371 through 1023. Bugfix on 0.0.9pre5.
14372 - Require that introduction point keys and onion handshake keys
14373 have a public exponent of 65537. Starts to fix bug 3207; bugfix
14375 - Handle SOCKS messages longer than 128 bytes long correctly, rather
14376 than waiting forever for them to finish. Fixes bug 2330; bugfix
14377 on 0.2.0.16-alpha. Found by doorss.
14378 - Never relay a cell for a circuit we have already destroyed.
14379 Between marking a circuit as closeable and finally closing it,
14380 it may have been possible for a few queued cells to get relayed,
14381 even though they would have been immediately dropped by the next
14382 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
14383 - Never queue a cell for a circuit that's already been marked
14385 - Fix a spec conformance issue: the network-status-version token
14386 must be the first token in a v3 consensus or vote. Discovered by
14387 "parakeep". Bugfix on 0.2.0.3-alpha.
14388 - A networkstatus vote must contain exactly one signature. Spec
14389 conformance issue. Bugfix on 0.2.0.3-alpha.
14390 - When asked about a DNS record type we don't support via a
14391 client DNSPort, reply with NOTIMPL rather than an empty
14392 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
14393 - Make more fields in the controller protocol case-insensitive, since
14394 control-spec.txt said they were.
14396 o Minor bugfixes (log messages):
14397 - Fix a log message that said "bits" while displaying a value in
14398 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
14400 - Downgrade "no current certificates known for authority" message from
14401 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
14402 - Correctly describe errors that occur when generating a TLS object.
14403 Previously we would attribute them to a failure while generating a
14404 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
14406 - Fix an instance where a Tor directory mirror might accidentally
14407 log the IP address of a misbehaving Tor client. Bugfix on
14409 - Stop logging at severity 'warn' when some other Tor client tries
14410 to establish a circuit with us using weak DH keys. It's a protocol
14411 violation, but that doesn't mean ordinary users need to hear about
14412 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
14413 - If your relay can't keep up with the number of incoming create
14414 cells, it would log one warning per failure into your logs. Limit
14415 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
14417 o Minor bugfixes (build fixes):
14418 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
14419 - When warning about missing zlib development packages during compile,
14420 give the correct package names. Bugfix on 0.2.0.1-alpha.
14421 - Fix warnings that newer versions of autoconf produce during
14422 ./autogen.sh. These warnings appear to be harmless in our case,
14423 but they were extremely verbose. Fixes bug 2020.
14424 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
14427 o Minor bugfixes (portability):
14428 - Write several files in text mode, on OSes that distinguish text
14429 mode from binary mode (namely, Windows). These files are:
14430 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
14431 that collect those statistics; 'client_keys' and 'hostname' for
14432 hidden services that use authentication; and (in the tor-gencert
14433 utility) newly generated identity and signing keys. Previously,
14434 we wouldn't specify text mode or binary mode, leading to an
14435 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
14436 the DirRecordUsageByCountry option which would have triggered
14437 the assertion failure was added), although this assertion failure
14438 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
14439 - Selectively disable deprecation warnings on OS X because Lion
14440 started deprecating the shipped copy of openssl. Fixes bug 3643.
14441 - Use a wide type to hold sockets when built for 64-bit Windows.
14443 - Fix an issue that prevented static linking of libevent on
14444 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
14445 where we introduced the "--with-static-libevent" configure option.
14446 - Fix a bug with our locking implementation on Windows that couldn't
14447 correctly detect when a file was already locked. Fixes bug 2504,
14448 bugfix on 0.2.1.6-alpha.
14449 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
14451 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
14452 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
14455 o Minor bugfixes (code correctness):
14456 - Always NUL-terminate the sun_path field of a sockaddr_un before
14457 passing it to the kernel. (Not a security issue: kernels are
14458 smart enough to reject bad sockaddr_uns.) Found by Coverity;
14459 CID #428. Bugfix on Tor 0.2.0.3-alpha.
14460 - Make connection_printf_to_buf()'s behavior sane. Its callers
14461 expect it to emit a CRLF iff the format string ends with CRLF;
14462 it actually emitted a CRLF iff (a) the format string ended with
14463 CRLF or (b) the resulting string was over 1023 characters long or
14464 (c) the format string did not end with CRLF *and* the resulting
14465 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
14466 fixes part of bug 3407.
14467 - Make send_control_event_impl()'s behavior sane. Its callers
14468 expect it to always emit a CRLF at the end of the string; it
14469 might have emitted extra control characters as well. Bugfix on
14470 0.1.1.9-alpha; fixes another part of bug 3407.
14471 - Make crypto_rand_int() check the value of its input correctly.
14472 Previously, it accepted values up to UINT_MAX, but could return a
14473 negative number if given a value above INT_MAX+1. Found by George
14474 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
14475 - Fix a potential null-pointer dereference while computing a
14476 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
14478 - If we fail to compute the identity digest of a v3 legacy keypair,
14479 warn, and don't use a buffer-full of junk instead. Bugfix on
14480 0.2.1.1-alpha; fixes bug 3106.
14481 - Resolve an untriggerable issue in smartlist_string_num_isin(),
14482 where if the function had ever in the future been used to check
14483 for the presence of a too-large number, it would have given an
14484 incorrect result. (Fortunately, we only used it for 16-bit
14485 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
14486 - Be more careful about reporting the correct error from a failed
14487 connect() system call. Under some circumstances, it was possible to
14488 look at an incorrect value for errno when sending the end reason.
14489 Bugfix on 0.1.0.1-rc.
14490 - Correctly handle an "impossible" overflow cases in connection byte
14491 counting, where we write or read more than 4GB on an edge connection
14492 in a single second. Bugfix on 0.1.2.8-beta.
14493 - Avoid a double mark-for-free warning when failing to attach a
14494 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
14496 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
14497 found by "cypherpunks". This bug was introduced before the first
14498 Tor release, in svn commit r110.
14499 - Fix a bug in bandwidth history state parsing that could have been
14500 triggered if a future version of Tor ever changed the timing
14501 granularity at which bandwidth history is measured. Bugfix on
14502 Tor 0.1.1.11-alpha.
14503 - Add assertions to check for overflow in arguments to
14504 base32_encode() and base32_decode(); fix a signed-unsigned
14505 comparison there too. These bugs are not actually reachable in Tor,
14506 but it's good to prevent future errors too. Found by doorss.
14507 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
14509 - Set target port in get_interface_address6() correctly. Bugfix
14510 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
14511 - Fix an impossible-to-actually-trigger buffer overflow in relay
14512 descriptor generation. Bugfix on 0.1.0.15.
14513 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
14515 o Minor bugfixes (code improvements):
14516 - After we free an internal connection structure, overwrite it
14517 with a different memory value than we use for overwriting a freed
14518 internal circuit structure. Should help with debugging. Suggested
14520 - If OpenSSL fails to make a duplicate of a private or public key, log
14521 an error message and try to exit cleanly. May help with debugging
14522 if bug 1209 ever remanifests.
14523 - Some options used different conventions for uppercasing of acronyms
14524 when comparing manpage and source. Fix those in favor of the
14525 manpage, as it makes sense to capitalize acronyms.
14526 - Take a first step towards making or.h smaller by splitting out
14527 function definitions for all source files in src/or/. Leave
14528 structures and defines in or.h for now.
14529 - Remove a few dead assignments during router parsing. Found by
14531 - Don't use 1-bit wide signed bit fields. Found by coverity.
14532 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
14533 None of the cases where we did this before were wrong, but by making
14534 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
14535 - The memarea code now uses a sentinel value at the end of each area
14536 to make sure nothing writes beyond the end of an area. This might
14537 help debug some conceivable causes of bug 930.
14538 - Always treat failure to allocate an RSA key as an unrecoverable
14540 - Add some more defensive programming for architectures that can't
14541 handle unaligned integer accesses. We don't know of any actual bugs
14542 right now, but that's the best time to fix them. Fixes bug 1943.
14544 o Minor bugfixes (misc):
14545 - Fix a rare bug in rend_fn unit tests: we would fail a test when
14546 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
14547 on 0.2.0.10-alpha; fixes bug 1808.
14548 - Where available, use Libevent 2.0's periodic timers so that our
14549 once-per-second cleanup code gets called even more closely to
14550 once per second than it would otherwise. Fixes bug 943.
14551 - Ignore OutboundBindAddress when connecting to localhost.
14552 Connections to localhost need to come _from_ localhost, or else
14553 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
14555 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
14557 - If any of the v3 certs we download are unparseable, we should
14558 actually notice the failure so we don't retry indefinitely. Bugfix
14559 on 0.2.0.x; reported by "rotator".
14560 - When Tor fails to parse a descriptor of any kind, dump it to disk.
14561 Might help diagnosing bug 1051.
14562 - Make our 'torify' script more portable; if we have only one of
14563 'torsocks' or 'tsocks' installed, don't complain to the user;
14564 and explain our warning about tsocks better.
14565 - Fix some urls in the exit notice file and make it XHTML1.1 strict
14566 compliant. Based on a patch from Christian Kujau.
14568 o Documentation changes:
14569 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
14570 - Resolve all doxygen warnings except those for missing documentation.
14572 - Add doxygen documentation for more functions, fields, and types.
14573 - Convert the HACKING file to asciidoc, and add a few new sections
14574 to it, explaining how we use Git, how we make changelogs, and
14575 what should go in a patch.
14576 - Document the default socks host and port (127.0.0.1:9050) for
14578 - Removed some unnecessary files from the source distribution. The
14579 AUTHORS file has now been merged into the people page on the
14580 website. The roadmaps and design doc can now be found in the
14581 projects directory in svn.
14583 o Deprecated and removed features (config):
14584 - Remove the torrc.complete file. It hasn't been kept up to date
14585 and users will have better luck checking out the manpage.
14586 - Remove the HSAuthorityRecordStats option that version 0 hidden
14587 service authorities could use to track statistics of overall v0
14588 hidden service usage.
14589 - Remove the obsolete "NoPublish" option; it has been flagged
14590 as obsolete and has produced a warning since 0.1.1.18-rc.
14591 - Caches no longer download and serve v2 networkstatus documents
14592 unless FetchV2Networkstatus flag is set: these documents haven't
14593 haven't been used by clients or relays since 0.2.0.x. Resolves
14596 o Deprecated and removed features (controller):
14597 - The controller no longer accepts the old obsolete "addr-mappings/"
14598 or "unregistered-servers-" GETINFO values.
14599 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
14600 always on; using them is necessary for correct forward-compatible
14603 o Deprecated and removed features (misc):
14604 - Hidden services no longer publish version 0 descriptors, and clients
14605 do not request or use version 0 descriptors. However, the old hidden
14606 service authorities still accept and serve version 0 descriptors
14607 when contacted by older hidden services/clients.
14608 - Remove undocumented option "-F" from tor-resolve: it hasn't done
14609 anything since 0.2.1.16-rc.
14610 - Remove everything related to building the expert bundle for OS X.
14611 It has confused many users, doesn't work right on OS X 10.6,
14612 and is hard to get rid of once installed. Resolves bug 1274.
14613 - Remove support for .noconnect style addresses. Nobody was using
14614 them, and they provided another avenue for detecting Tor users
14615 via application-level web tricks.
14616 - When we fixed bug 1038 we had to put in a restriction not to send
14617 RELAY_EARLY cells on rend circuits. This was necessary as long
14618 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
14619 active. Now remove this obsolete check. Resolves bug 2081.
14620 - Remove workaround code to handle directory responses from servers
14621 that had bug 539 (they would send HTTP status 503 responses _and_
14622 send a body too). Since only server versions before
14623 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
14624 keep the workaround in place.
14625 - Remove the old 'fuzzy time' logic. It was supposed to be used for
14626 handling calculations where we have a known amount of clock skew and
14627 an allowed amount of unknown skew. But we only used it in three
14628 places, and we never adjusted the known/unknown skew values. This is
14629 still something we might want to do someday, but if we do, we'll
14630 want to do it differently.
14631 - Remove the "--enable-iphone" option to ./configure. According to
14632 reports from Marco Bonetti, Tor builds fine without any special
14633 tweaking on recent iPhone SDK versions.
14636 Changes in version 0.2.1.30 - 2011-02-23
14637 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
14638 change is a slight tweak to Tor's TLS handshake that makes relays
14639 and bridges that run this new version reachable from Iran again.
14640 We don't expect this tweak will win the arms race long-term, but it
14641 buys us time until we roll out a better solution.
14644 - Stop sending a CLOCK_SKEW controller status event whenever
14645 we fetch directory information from a relay that has a wrong clock.
14646 Instead, only inform the controller when it's a trusted authority
14647 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
14648 the rest of bug 1074.
14649 - Fix a bounds-checking error that could allow an attacker to
14650 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
14651 Found by "piebeer".
14652 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
14653 Tor would ignore their RelayBandwidthBurst setting,
14654 potentially using more bandwidth than expected. Bugfix on
14655 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
14656 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
14657 hidserv" in her torrc. The 'hidserv' argument never controlled
14658 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
14661 - Adjust our TLS Diffie-Hellman parameters to match those used by
14663 - Update to the February 1 2011 Maxmind GeoLite Country database.
14666 - Check for and reject overly long directory certificates and
14667 directory tokens before they have a chance to hit any assertions.
14668 Bugfix on 0.2.1.28. Found by "doorss".
14669 - Bring the logic that gathers routerinfos and assesses the
14670 acceptability of circuits into line. This prevents a Tor OP from
14671 getting locked in a cycle of choosing its local OR as an exit for a
14672 path (due to a .exit request) and then rejecting the circuit because
14673 its OR is not listed yet. It also prevents Tor clients from using an
14674 OR running in the same instance as an exit (due to a .exit request)
14675 if the OR does not meet the same requirements expected of an OR
14676 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
14678 o Packaging changes:
14679 - Stop shipping the Tor specs files and development proposal documents
14680 in the tarball. They are now in a separate git repository at
14681 git://git.torproject.org/torspec.git
14682 - Do not include Git version tags as though they are SVN tags when
14683 generating a tarball from inside a repository that has switched
14684 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
14687 Changes in version 0.2.1.29 - 2011-01-15
14688 Tor 0.2.1.29 continues our recent code security audit work. The main
14689 fix resolves a remote heap overflow vulnerability that can allow remote
14690 code execution. Other fixes address a variety of assert and crash bugs,
14691 most of which we think are hard to exploit remotely.
14693 o Major bugfixes (security):
14694 - Fix a heap overflow bug where an adversary could cause heap
14695 corruption. This bug probably allows remote code execution
14696 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
14698 - Prevent a denial-of-service attack by disallowing any
14699 zlib-compressed data whose compression factor is implausibly
14700 high. Fixes part of bug 2324; reported by "doorss".
14701 - Zero out a few more keys in memory before freeing them. Fixes
14702 bug 2384 and part of bug 2385. These key instances found by
14703 "cypherpunks", based on Andrew Case's report about being able
14704 to find sensitive data in Tor's memory space if you have enough
14705 permissions. Bugfix on 0.0.2pre9.
14707 o Major bugfixes (crashes):
14708 - Prevent calls to Libevent from inside Libevent log handlers.
14709 This had potential to cause a nasty set of crashes, especially
14710 if running Libevent with debug logging enabled, and running
14711 Tor with a controller watching for low-severity log messages.
14712 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
14713 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
14714 underflow errors there too. Fixes the other part of bug 2324.
14715 - Fix a bug where we would assert if we ever had a
14716 cached-descriptors.new file (or another file read directly into
14717 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
14718 on 0.2.1.25. Found by doorss.
14719 - Fix some potential asserts and parsing issues with grossly
14720 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
14723 o Minor bugfixes (other):
14724 - Fix a bug with handling misformed replies to reverse DNS lookup
14725 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
14726 bug reported by doorss.
14727 - Fix compilation on mingw when a pthreads compatibility library
14728 has been installed. (We don't want to use it, so we shouldn't
14729 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
14730 - Fix a bug where we would declare that we had run out of virtual
14731 addresses when the address space was only half-exhausted. Bugfix
14733 - Correctly handle the case where AutomapHostsOnResolve is set but
14734 no virtual addresses are available. Fixes bug 2328; bugfix on
14735 0.1.2.1-alpha. Bug found by doorss.
14736 - Correctly handle wrapping around when we run out of virtual
14737 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
14740 - Update to the January 1 2011 Maxmind GeoLite Country database.
14741 - Introduce output size checks on all of our decryption functions.
14744 - Tor does not build packages correctly with Automake 1.6 and earlier;
14745 added a check to Makefile.am to make sure that we're building with
14746 Automake 1.7 or later.
14747 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
14748 because we built it with a too-old version of automake. Thus that
14749 release broke ./configure --enable-openbsd-malloc, which is popular
14750 among really fast exit relays on Linux.
14753 Changes in version 0.2.1.28 - 2010-12-17
14754 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
14755 exploitable bugs. We also took this opportunity to change the IP address
14756 for one of our directory authorities, and to update the geoip database
14760 - Fix a remotely exploitable bug that could be used to crash instances
14761 of Tor remotely by overflowing on the heap. Remote-code execution
14762 hasn't been confirmed, but can't be ruled out. Everyone should
14763 upgrade. Bugfix on the 0.1.1 series and later.
14765 o Directory authority changes:
14766 - Change IP address and ports for gabelmoo (v3 directory authority).
14769 - Update to the December 1 2010 Maxmind GeoLite Country database.
14772 Changes in version 0.2.1.27 - 2010-11-23
14773 Yet another OpenSSL security patch broke its compatibility with Tor:
14774 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
14775 also took this opportunity to fix several crash bugs, integrate a new
14776 directory authority, and update the bundled GeoIP database.
14779 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
14780 No longer set the tlsext_host_name extension on server SSL objects;
14781 but continue to set it on client SSL objects. Our goal in setting
14782 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
14783 bugfix on 0.2.1.1-alpha.
14784 - Do not log messages to the controller while shrinking buffer
14785 freelists. Doing so would sometimes make the controller connection
14786 try to allocate a buffer chunk, which would mess up the internals
14787 of the freelist and cause an assertion failure. Fixes bug 1125;
14788 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
14789 - Learn our external IP address when we're a relay or bridge, even if
14790 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
14791 where we introduced bridge relays that don't need to publish to
14792 be useful. Fixes bug 2050.
14793 - Do even more to reject (and not just ignore) annotations on
14794 router descriptors received anywhere but from the cache. Previously
14795 we would ignore such annotations at first, but cache them to disk
14796 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
14797 - When you're using bridges and your network goes away and your
14798 bridges get marked as down, recover when you attempt a new socks
14799 connection (if the network is back), rather than waiting up to an
14800 hour to try fetching new descriptors for your bridges. Bugfix on
14801 0.2.0.3-alpha; fixes bug 1981.
14804 - Move to the November 2010 Maxmind GeoLite country db (rather
14805 than the June 2009 ip-to-country GeoIP db) for our statistics that
14806 count how many users relays are seeing from each country. Now we'll
14807 have more accurate data, especially for many African countries.
14809 o New directory authorities:
14810 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
14814 - Fix an assertion failure that could occur in directory caches or
14815 bridge users when using a very short voting interval on a testing
14816 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
14818 - Enforce multiplicity rules when parsing annotations. Bugfix on
14819 0.2.0.8-alpha. Found by piebeer.
14820 - Allow handshaking OR connections to take a full KeepalivePeriod
14821 seconds to handshake. Previously, we would close them after
14822 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
14823 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
14825 - When building with --enable-gcc-warnings on OpenBSD, disable
14826 warnings in system headers. This makes --enable-gcc-warnings
14827 pass on OpenBSD 4.8.
14830 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
14831 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
14832 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
14833 Servers can start sending this code when enough clients recognize
14834 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
14835 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
14836 Patch from mingw-san.
14839 - Remove the old debian/ directory from the main Tor distribution.
14840 The official Tor-for-debian git repository lives at the URL
14841 https://git.torproject.org/debian/tor.git
14842 - Stop shipping the old doc/website/ directory in the tarball. We
14843 changed the website format in late 2010, and what we shipped in
14844 0.2.1.26 really wasn't that useful anyway.
14847 Changes in version 0.2.1.26 - 2010-05-02
14848 Tor 0.2.1.26 addresses the recent connection and memory overload
14849 problems we've been seeing on relays, especially relays with their
14850 DirPort open. If your relay has been crashing, or you turned it off
14851 because it used too many resources, give this release a try.
14853 This release also fixes yet another instance of broken OpenSSL libraries
14854 that was causing some relays to drop out of the consensus.
14857 - Teach relays to defend themselves from connection overload. Relays
14858 now close idle circuits early if it looks like they were intended
14859 for directory fetches. Relays are also more aggressive about closing
14860 TLS connections that have no circuits on them. Such circuits are
14861 unlikely to be re-used, and tens of thousands of them were piling
14862 up at the fast relays, causing the relays to run out of sockets
14863 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
14864 their directory fetches over TLS).
14865 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
14866 that claim to be earlier than 0.9.8m, but which have in reality
14867 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
14868 behavior. Possible fix for some cases of bug 1346.
14869 - Directory mirrors were fetching relay descriptors only from v2
14870 directory authorities, rather than v3 authorities like they should.
14871 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
14872 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
14875 - Finally get rid of the deprecated and now harmful notion of "clique
14876 mode", where directory authorities maintain TLS connections to
14880 - In the util/threads test, no longer free the test_mutex before all
14881 worker threads have finished. Bugfix on 0.2.1.6-alpha.
14882 - The master thread could starve the worker threads quite badly on
14883 certain systems, causing them to run only partially in the allowed
14884 window. This resulted in test failures. Now the master thread sleeps
14885 occasionally for a few microseconds while the two worker-threads
14886 compete for the mutex. Bugfix on 0.2.0.1-alpha.
14889 Changes in version 0.2.1.25 - 2010-03-16
14890 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
14891 prevent relays from guessing their IP address correctly. It also fixes
14892 several minor potential security bugs.
14895 - Fix a regression from our patch for bug 1244 that caused relays
14896 to guess their IP address incorrectly if they didn't set Address
14897 in their torrc and/or their address fails to resolve. Bugfix on
14898 0.2.1.23; fixes bug 1269.
14899 - When freeing a session key, zero it out completely. We only zeroed
14900 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
14901 patched by ekir. Fixes bug 1254.
14904 - Fix a dereference-then-NULL-check sequence when publishing
14905 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
14907 - Fix another dereference-then-NULL-check sequence. Bugfix on
14908 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
14909 - Make sure we treat potentially not NUL-terminated strings correctly.
14910 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
14913 Changes in version 0.2.1.24 - 2010-02-21
14914 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
14918 - Work correctly out-of-the-box with even more vendor-patched versions
14919 of OpenSSL. In particular, make it so Debian and OS X don't need
14920 customized patches to run/build.
14923 Changes in version 0.2.1.23 - 2010-02-13
14924 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
14925 again on the latest OS X, and updates the location of a directory
14928 o Major bugfixes (performance):
14929 - We were selecting our guards uniformly at random, and then weighting
14930 which of our guards we'd use uniformly at random. This imbalance
14931 meant that Tor clients were severely limited on throughput (and
14932 probably latency too) by the first hop in their circuit. Now we
14933 select guards weighted by currently advertised bandwidth. We also
14934 automatically discard guards picked using the old algorithm. Fixes
14935 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
14938 - Make Tor work again on the latest OS X: when deciding whether to
14939 use strange flags to turn TLS renegotiation on, detect the OpenSSL
14940 version at run-time, not compile time. We need to do this because
14941 Apple doesn't update its dev-tools headers when it updates its
14942 libraries in a security patch.
14943 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
14944 that could happen on 32-bit platforms with 64-bit time_t. Also fix
14945 a memory leak when requesting a hidden service descriptor we've
14946 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
14950 - Refactor resolve_my_address() to not use gethostbyname() anymore.
14951 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
14954 - Avoid a mad rush at the beginning of each month when each client
14955 rotates half of its guards. Instead we spread the rotation out
14956 throughout the month, but we still avoid leaving a precise timestamp
14957 in the state file about when we first picked the guard. Improves
14958 over the behavior introduced in 0.1.2.17.
14961 Changes in version 0.2.1.22 - 2010-01-19
14962 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
14963 authorities -- it would tell you its whole history of bridge descriptors
14964 if you make the right directory request. This stable update also
14965 rotates two of the seven v3 directory authority keys and locations.
14967 o Directory authority changes:
14968 - Rotate keys (both v3 identity and relay identity) for moria1
14972 - Stop bridge directory authorities from answering dbg-stability.txt
14973 directory queries, which would let people fetch a list of all
14974 bridge identities they track. Bugfix on 0.2.1.6-alpha.
14977 Changes in version 0.2.1.21 - 2009-12-21
14978 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
14979 library. If you use Tor on Linux / Unix and you're getting SSL
14980 renegotiation errors, upgrading should help. We also recommend an
14981 upgrade if you're an exit relay.
14984 - Work around a security feature in OpenSSL 0.9.8l that prevents our
14985 handshake from working unless we explicitly tell OpenSSL that we
14986 are using SSL renegotiation safely. We are, of course, but OpenSSL
14987 0.9.8l won't work unless we say we are.
14988 - Avoid crashing if the client is trying to upload many bytes and the
14989 circuit gets torn down at the same time, or if the flip side
14990 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
14993 - Do not refuse to learn about authority certs and v2 networkstatus
14994 documents that are older than the latest consensus. This bug might
14995 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
14996 Spotted and fixed by xmux.
14997 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
14998 trigger platform-specific option misparsing case found by Coverity
15000 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
15001 trigger assert. Fixes bug 1173.
15004 Changes in version 0.2.1.20 - 2009-10-15
15005 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
15006 services at once, prepares for more performance improvements, and
15007 fixes a bunch of smaller bugs.
15009 The Windows and OS X bundles also include a more recent Vidalia,
15010 and switch from Privoxy to Polipo.
15012 The OS X installers are now drag and drop. It's best to un-install
15013 Tor/Vidalia and then install this new bundle, rather than upgrade. If
15014 you want to upgrade, you'll need to update the paths for Tor and Polipo
15015 in the Vidalia Settings window.
15018 - Send circuit or stream sendme cells when our window has decreased
15019 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
15020 by Karsten when testing the "reduce circuit window" performance
15021 patch. Bugfix on the 54th commit on Tor -- from July 2002,
15022 before the release of Tor 0.0.0. This is the new winner of the
15024 - Fix a remotely triggerable memory leak when a consensus document
15025 contains more than one signature from the same voter. Bugfix on
15027 - Avoid segfault in rare cases when finishing an introduction circuit
15028 as a client and finding out that we don't have an introduction key
15029 for it. Fixes bug 1073. Reported by Aaron Swartz.
15032 - Tor now reads the "circwindow" parameter out of the consensus,
15033 and uses that value for its circuit package window rather than the
15034 default of 1000 cells. Begins the implementation of proposal 168.
15036 o New directory authorities:
15037 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
15039 - Move moria1 and tonga to alternate IP addresses.
15042 - Fix a signed/unsigned compile warning in 0.2.1.19.
15043 - Fix possible segmentation fault on directory authorities. Bugfix on
15045 - Fix an extremely rare infinite recursion bug that could occur if
15046 we tried to log a message after shutting down the log subsystem.
15047 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
15048 - Fix an obscure bug where hidden services on 64-bit big-endian
15049 systems might mis-read the timestamp in v3 introduce cells, and
15050 refuse to connect back to the client. Discovered by "rotor".
15051 Bugfix on 0.2.1.6-alpha.
15052 - We were triggering a CLOCK_SKEW controller status event whenever
15053 we connect via the v2 connection protocol to any relay that has
15054 a wrong clock. Instead, we should only inform the controller when
15055 it's a trusted authority that claims our clock is wrong. Bugfix
15056 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
15057 - We were telling the controller about CHECKING_REACHABILITY and
15058 REACHABILITY_FAILED status events whenever we launch a testing
15059 circuit or notice that one has failed. Instead, only tell the
15060 controller when we want to inform the user of overall success or
15061 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
15063 - Don't warn when we're using a circuit that ends with a node
15064 excluded in ExcludeExitNodes, but the circuit is not used to access
15065 the outside world. This should help fix bug 1090. Bugfix on
15067 - Work around a small memory leak in some versions of OpenSSL that
15068 stopped the memory used by the hostname TLS extension from being
15072 - Add a "getinfo status/accepted-server-descriptor" controller
15073 command, which is the recommended way for controllers to learn
15074 whether our server descriptor has been successfully received by at
15075 least on directory authority. Un-recommend good-server-descriptor
15076 getinfo and status events until we have a better design for them.
15079 Changes in version 0.2.1.19 - 2009-07-28
15080 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
15084 - Make accessing hidden services on 0.2.1.x work right again.
15085 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
15086 part of patch provided by "optimist".
15089 - When a relay/bridge is writing out its identity key fingerprint to
15090 the "fingerprint" file and to its logs, write it without spaces. Now
15091 it will look like the fingerprints in our bridges documentation,
15092 and confuse fewer users.
15095 - Relays no longer publish a new server descriptor if they change
15096 their MaxAdvertisedBandwidth config option but it doesn't end up
15097 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
15098 fixes bug 1026. Patch from Sebastian.
15099 - Avoid leaking memory every time we get a create cell but we have
15100 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
15101 fixes bug 1034. Reported by BarkerJr.
15104 Changes in version 0.2.1.18 - 2009-07-24
15105 Tor 0.2.1.18 lays the foundations for performance improvements,
15106 adds status events to help users diagnose bootstrap problems, adds
15107 optional authentication/authorization for hidden services, fixes a
15108 variety of potential anonymity problems, and includes a huge pile of
15109 other features and bug fixes.
15111 o Major features (clients):
15112 - Start sending "bootstrap phase" status events to the controller,
15113 so it can keep the user informed of progress fetching directory
15114 information and establishing circuits. Also inform the controller
15115 if we think we're stuck at a particular bootstrap phase. Implements
15117 - Clients replace entry guards that were chosen more than a few months
15118 ago. This change should significantly improve client performance,
15119 especially once more people upgrade, since relays that have been
15120 a guard for a long time are currently overloaded.
15121 - Network status consensus documents and votes now contain bandwidth
15122 information for each relay. Clients use the bandwidth values
15123 in the consensus, rather than the bandwidth values in each
15124 relay descriptor. This approach opens the door to more accurate
15125 bandwidth estimates once the directory authorities start doing
15126 active measurements. Implements part of proposal 141.
15128 o Major features (relays):
15129 - Disable and refactor some debugging checks that forced a linear scan
15130 over the whole server-side DNS cache. These accounted for over 50%
15131 of CPU time on a relatively busy exit node's gprof profile. Also,
15132 disable some debugging checks that appeared in exit node profile
15133 data. Found by Jacob.
15134 - New DirPortFrontPage option that takes an html file and publishes
15135 it as "/" on the DirPort. Now relay operators can provide a
15136 disclaimer without needing to set up a separate webserver. There's
15137 a sample disclaimer in contrib/tor-exit-notice.html.
15139 o Major features (hidden services):
15140 - Make it possible to build hidden services that only certain clients
15141 are allowed to connect to. This is enforced at several points,
15142 so that unauthorized clients are unable to send INTRODUCE cells
15143 to the service, or even (depending on the type of authentication)
15144 to learn introduction points. This feature raises the bar for
15145 certain kinds of active attacks against hidden services. Design
15146 and code by Karsten Loesing. Implements proposal 121.
15147 - Relays now store and serve v2 hidden service descriptors by default,
15148 i.e., the new default value for HidServDirectoryV2 is 1. This is
15149 the last step in proposal 114, which aims to make hidden service
15150 lookups more reliable.
15152 o Major features (path selection):
15153 - ExitNodes and Exclude*Nodes config options now allow you to restrict
15154 by country code ("{US}") or IP address or address pattern
15155 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
15156 refinement to decide what config options should take priority if
15157 you ask to both use a particular node and exclude it.
15159 o Major features (misc):
15160 - When building a consensus, do not include routers that are down.
15161 This cuts down 30% to 40% on consensus size. Implements proposal
15163 - New TestingTorNetwork config option to allow adjustment of
15164 previously constant values that could slow bootstrapping. Implements
15165 proposal 135. Patch from Karsten.
15166 - Convert many internal address representations to optionally hold
15167 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
15168 elements. Make resolver code handle nameservers located at IPv6
15170 - More work on making our TLS handshake blend in: modify the list
15171 of ciphers advertised by OpenSSL in client mode to even more
15172 closely resemble a common web browser. We cheat a little so that
15173 we can advertise ciphers that the locally installed OpenSSL doesn't
15175 - Use the TLS1 hostname extension to more closely resemble browser
15178 o Security fixes (anonymity/entropy):
15179 - Never use a connection with a mismatched address to extend a
15180 circuit, unless that connection is canonical. A canonical
15181 connection is one whose address is authenticated by the router's
15182 identity key, either in a NETINFO cell or in a router descriptor.
15183 - Implement most of proposal 110: The first K cells to be sent
15184 along a circuit are marked as special "early" cells; only K "early"
15185 cells will be allowed. Once this code is universal, we can block
15186 certain kinds of denial-of-service attack by requiring that EXTEND
15187 commands must be sent using an "early" cell.
15188 - Resume using OpenSSL's RAND_poll() for better (and more portable)
15189 cross-platform entropy collection again. We used to use it, then
15190 stopped using it because of a bug that could crash systems that
15191 called RAND_poll when they had a lot of fds open. It looks like the
15192 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
15193 at startup, and to call RAND_poll() when we reseed later only if
15194 we have a non-buggy OpenSSL version.
15195 - When the client is choosing entry guards, now it selects at most
15196 one guard from a given relay family. Otherwise we could end up with
15197 all of our entry points into the network run by the same operator.
15198 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
15199 - Do not use or believe expired v3 authority certificates. Patch
15200 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
15201 - Drop begin cells to a hidden service if they come from the middle
15202 of a circuit. Patch from lark.
15203 - When we erroneously receive two EXTEND cells for the same circuit
15204 ID on the same connection, drop the second. Patch from lark.
15205 - Authorities now vote for the Stable flag for any router whose
15206 weighted MTBF is at least 5 days, regardless of the mean MTBF.
15207 - Clients now never report any stream end reason except 'MISC'.
15208 Implements proposal 148.
15210 o Major bugfixes (crashes):
15211 - Parse dates and IPv4 addresses in a locale- and libc-independent
15212 manner, to avoid platform-dependent behavior on malformed input.
15213 - Fix a crash that occurs on exit nodes when a nameserver request
15214 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
15215 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
15217 - Do not assume that a stack-allocated character array will be
15218 64-bit aligned on platforms that demand that uint64_t access is
15219 aligned. Possible fix for bug 604.
15220 - Resolve a very rare crash bug that could occur when the user forced
15221 a nameserver reconfiguration during the middle of a nameserver
15222 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
15223 - Avoid a "0 divided by 0" calculation when calculating router uptime
15224 at directory authorities. Bugfix on 0.2.0.8-alpha.
15225 - Fix an assertion bug in parsing policy-related options; possible fix
15227 - Rate-limit too-many-sockets messages: when they happen, they happen
15228 a lot and end up filling up the disk. Resolves bug 748.
15229 - Fix a race condition that could cause crashes or memory corruption
15230 when running as a server with a controller listening for log
15232 - Avoid crashing when we have a policy specified in a DirPolicy or
15233 SocksPolicy or ReachableAddresses option with ports set on it,
15234 and we re-load the policy. May fix bug 996.
15235 - Fix an assertion failure on 64-bit platforms when we allocated
15236 memory right up to the end of a memarea, then realigned the memory
15237 one step beyond the end. Fixes a possible cause of bug 930.
15238 - Protect the count of open sockets with a mutex, so we can't
15239 corrupt it when two threads are closing or opening sockets at once.
15240 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
15242 o Major bugfixes (clients):
15243 - Discard router descriptors as we load them if they are more than
15244 five days old. Otherwise if Tor is off for a long time and then
15245 starts with cached descriptors, it will try to use the onion keys
15246 in those obsolete descriptors when building circuits. Fixes bug 887.
15247 - When we choose to abandon a new entry guard because we think our
15248 older ones might be better, close any circuits pending on that
15249 new entry guard connection. This fix should make us recover much
15250 faster when our network is down and then comes back. Bugfix on
15251 0.1.2.8-beta; found by lodger.
15252 - When Tor clients restart after 1-5 days, they discard all their
15253 cached descriptors as too old, but they still use the cached
15254 consensus document. This approach is good for robustness, but
15255 bad for performance: since they don't know any bandwidths, they
15256 end up choosing at random rather than weighting their choice by
15257 speed. Fixed by the above feature of putting bandwidths in the
15260 o Major bugfixes (relays):
15261 - Relays were falling out of the networkstatus consensus for
15262 part of a day if they changed their local config but the
15263 authorities discarded their new descriptor as "not sufficiently
15264 different". Now directory authorities accept a descriptor as changed
15265 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
15266 patch by Sebastian.
15267 - Ensure that two circuits can never exist on the same connection
15268 with the same circuit ID, even if one is marked for close. This
15269 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
15270 - Directory authorities were neglecting to mark relays down in their
15271 internal histories if the relays fall off the routerlist without
15272 ever being found unreachable. So there were relays in the histories
15273 that haven't been seen for eight months, and are listed as being
15274 up for eight months. This wreaked havoc on the "median wfu" and
15275 "median mtbf" calculations, in turn making Guard and Stable flags
15276 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
15279 o Major bugfixes (hidden services):
15280 - When establishing a hidden service, introduction points that
15281 originate from cannibalized circuits were completely ignored
15282 and not included in rendezvous service descriptors. This might
15283 have been another reason for delay in making a hidden service
15284 available. Bugfix from long ago (0.0.9.x?)
15286 o Major bugfixes (memory and resource management):
15287 - Fixed some memory leaks -- some quite frequent, some almost
15288 impossible to trigger -- based on results from Coverity.
15289 - Speed up parsing and cut down on memory fragmentation by using
15290 stack-style allocations for parsing directory objects. Previously,
15291 this accounted for over 40% of allocations from within Tor's code
15292 on a typical directory cache.
15293 - Use a Bloom filter rather than a digest-based set to track which
15294 descriptors we need to keep around when we're cleaning out old
15295 router descriptors. This speeds up the computation significantly,
15296 and may reduce fragmentation.
15298 o New/changed config options:
15299 - Now NodeFamily and MyFamily config options allow spaces in
15300 identity fingerprints, so it's easier to paste them in.
15301 Suggested by Lucky Green.
15302 - Allow ports 465 and 587 in the default exit policy again. We had
15303 rejected them in 0.1.0.15, because back in 2005 they were commonly
15304 misconfigured and ended up as spam targets. We hear they are better
15305 locked down these days.
15306 - Make TrackHostExit mappings expire a while after their last use, not
15307 after their creation. Patch from Robert Hogan.
15308 - Add an ExcludeExitNodes option so users can list a set of nodes
15309 that should be be excluded from the exit node position, but
15310 allowed elsewhere. Implements proposal 151.
15311 - New --hush command-line option similar to --quiet. While --quiet
15312 disables all logging to the console on startup, --hush limits the
15313 output to messages of warning and error severity.
15314 - New configure/torrc options (--enable-geoip-stats,
15315 DirRecordUsageByCountry) to record how many IPs we've served
15316 directory info to in each country code, how many status documents
15317 total we've sent to each country code, and what share of the total
15318 directory requests we should expect to see.
15319 - Make outbound DNS packets respect the OutboundBindAddress setting.
15320 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
15321 - Allow separate log levels to be configured for different logging
15322 domains. For example, this allows one to log all notices, warnings,
15323 or errors, plus all memory management messages of level debug or
15324 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
15325 - Update to the "June 3 2009" ip-to-country file.
15327 o Minor features (relays):
15328 - Raise the minimum rate limiting to be a relay from 20000 bytes
15329 to 20480 bytes (aka 20KB/s), to match our documentation. Also
15330 update directory authorities so they always assign the Fast flag
15331 to relays with 20KB/s of capacity. Now people running relays won't
15332 suddenly find themselves not seeing any use, if the network gets
15334 - If we're a relay and we change our IP address, be more verbose
15335 about the reason that made us change. Should help track down
15336 further bugs for relays on dynamic IP addresses.
15337 - Exit servers can now answer resolve requests for ip6.arpa addresses.
15338 - Implement most of Proposal 152: allow specialized servers to permit
15339 single-hop circuits, and clients to use those servers to build
15340 single-hop circuits when using a specialized controller. Patch
15341 from Josh Albrecht. Resolves feature request 768.
15342 - When relays do their initial bandwidth measurement, don't limit
15343 to just our entry guards for the test circuits. Otherwise we tend
15344 to have multiple test circuits going through a single entry guard,
15345 which makes our bandwidth test less accurate. Fixes part of bug 654;
15346 patch contributed by Josh Albrecht.
15348 o Minor features (directory authorities):
15349 - Try not to open more than one descriptor-downloading connection
15350 to an authority at once. This should reduce load on directory
15351 authorities. Fixes bug 366.
15352 - Add cross-certification to newly generated certificates, so that
15353 a signing key is enough information to look up a certificate. Start
15354 serving certificates by <identity digest, signing key digest>
15355 pairs. Implements proposal 157.
15356 - When a directory authority downloads a descriptor that it then
15357 immediately rejects, do not retry downloading it right away. Should
15358 save some bandwidth on authorities. Fix for bug 888. Patch by
15360 - Directory authorities now serve a /tor/dbg-stability.txt URL to
15361 help debug WFU and MTBF calculations.
15362 - In directory authorities' approved-routers files, allow
15363 fingerprints with or without space.
15365 o Minor features (directory mirrors):
15366 - When a download gets us zero good descriptors, do not notify
15367 Tor that new directory information has arrived.
15368 - Servers support a new URL scheme for consensus downloads that
15369 allows the client to specify which authorities are trusted.
15370 The server then only sends the consensus if the client will trust
15371 it. Otherwise a 404 error is sent back. Clients use this
15372 new scheme when the server supports it (meaning it's running
15373 0.2.1.1-alpha or later). Implements proposal 134.
15375 o Minor features (bridges):
15376 - If the bridge config line doesn't specify a port, assume 443.
15377 This makes bridge lines a bit smaller and easier for users to
15379 - If we're using bridges and our network goes away, be more willing
15380 to forgive our bridges and try again when we get an application
15383 o Minor features (hidden services):
15384 - When the client launches an introduction circuit, retry with a
15385 new circuit after 30 seconds rather than 60 seconds.
15386 - Launch a second client-side introduction circuit in parallel
15387 after a delay of 15 seconds (based on work by Christian Wilms).
15388 - Hidden services start out building five intro circuits rather
15389 than three, and when the first three finish they publish a service
15390 descriptor using those. Now we publish our service descriptor much
15391 faster after restart.
15392 - Drop the requirement to have an open dir port for storing and
15393 serving v2 hidden service descriptors.
15395 o Minor features (build and packaging):
15396 - On Linux, use the prctl call to re-enable core dumps when the User
15398 - Try to make sure that the version of Libevent we're running with
15399 is binary-compatible with the one we built with. May address bug
15401 - Add a new --enable-local-appdata configuration switch to change
15402 the default location of the datadir on win32 from APPDATA to
15403 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
15404 entirely. Patch from coderman.
15405 - Build correctly against versions of OpenSSL 0.9.8 or later that
15406 are built without support for deprecated functions.
15407 - On platforms with a maximum syslog string length, truncate syslog
15408 messages to that length ourselves, rather than relying on the
15409 system to do it for us.
15410 - Automatically detect MacOSX versions earlier than 10.4.0, and
15411 disable kqueue from inside Tor when running with these versions.
15412 We previously did this from the startup script, but that was no
15413 help to people who didn't use the startup script. Resolves bug 863.
15414 - Build correctly when configured to build outside the main source
15415 path. Patch from Michael Gold.
15416 - Disable GCC's strict alias optimization by default, to avoid the
15417 likelihood of its introducing subtle bugs whenever our code violates
15418 the letter of C99's alias rules.
15419 - Change the contrib/tor.logrotate script so it makes the new
15420 logs as "_tor:_tor" rather than the default, which is generally
15421 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
15422 - Change our header file guard macros to be less likely to conflict
15423 with system headers. Adam Langley noticed that we were conflicting
15424 with log.h on Android.
15425 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
15426 and stop using a warning that had become unfixably verbose under
15428 - Use a lockfile to make sure that two Tor processes are not
15429 simultaneously running with the same datadir.
15430 - Allow OpenSSL to use dynamic locks if it wants.
15431 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
15433 o Minor features (controllers):
15434 - When generating circuit events with verbose nicknames for
15435 controllers, try harder to look up nicknames for routers on a
15436 circuit. (Previously, we would look in the router descriptors we had
15437 for nicknames, but not in the consensus.) Partial fix for bug 941.
15438 - New controller event NEWCONSENSUS that lists the networkstatus
15439 lines for every recommended relay. Now controllers like Torflow
15440 can keep up-to-date on which relays they should be using.
15441 - New controller event "clients_seen" to report a geoip-based summary
15442 of which countries we've seen clients from recently. Now controllers
15443 like Vidalia can show bridge operators that they're actually making
15445 - Add a 'getinfo status/clients-seen' controller command, in case
15446 controllers want to hear clients_seen events but connect late.
15447 - New CONSENSUS_ARRIVED event to note when a new consensus has
15448 been fetched and validated.
15449 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
15450 controllers to prevent SIGHUP from reloading the configuration.
15452 - Return circuit purposes in response to GETINFO circuit-status.
15454 - Serve the latest v3 networkstatus consensus via the control
15455 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
15456 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
15457 controller can query our current bootstrap state in case it attaches
15458 partway through and wants to catch up.
15459 - Provide circuit purposes along with circuit events to the controller.
15461 o Minor features (tools):
15462 - Do not have tor-resolve automatically refuse all .onion addresses;
15463 if AutomapHostsOnResolve is set in your torrc, this will work fine.
15464 - Add a -p option to tor-resolve for specifying the SOCKS port: some
15465 people find host:port too confusing.
15466 - Print the SOCKS5 error message string as well as the error code
15467 when a tor-resolve request fails. Patch from Jacob.
15469 o Minor bugfixes (memory and resource management):
15470 - Clients no longer cache certificates for authorities they do not
15471 recognize. Bugfix on 0.2.0.9-alpha.
15472 - Do not use C's stdio library for writing to log files. This will
15473 improve logging performance by a minute amount, and will stop
15474 leaking fds when our disk is full. Fixes bug 861.
15475 - Stop erroneous use of O_APPEND in cases where we did not in fact
15476 want to re-seek to the end of a file before every last write().
15477 - Fix a small alignment and memory-wasting bug on buffer chunks.
15479 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
15480 to avoid unused RAM in buffer chunks and memory pools.
15481 - Reduce the default smartlist size from 32 to 16; it turns out that
15482 most smartlists hold around 8-12 elements tops.
15483 - Make dumpstats() log the fullness and size of openssl-internal
15485 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
15486 patch to their OpenSSL, turn it on to save memory on servers. This
15487 patch will (with any luck) get included in a mainline distribution
15489 - Fix a memory leak when v3 directory authorities load their keys
15490 and cert from disk. Bugfix on 0.2.0.1-alpha.
15491 - Stop using malloc_usable_size() to use more area than we had
15492 actually allocated: it was safe, but made valgrind really unhappy.
15493 - Make the assert_circuit_ok() function work correctly on circuits that
15494 have already been marked for close.
15495 - Fix uninitialized size field for memory area allocation: may improve
15496 memory performance during directory parsing.
15498 o Minor bugfixes (clients):
15499 - Stop reloading the router list from disk for no reason when we
15500 run out of reachable directory mirrors. Once upon a time reloading
15501 it would set the 'is_running' flag back to 1 for them. It hasn't
15502 done that for a long time.
15503 - When we had picked an exit node for a connection, but marked it as
15504 "optional", and it turned out we had no onion key for the exit,
15505 stop wanting that exit and try again. This situation may not
15506 be possible now, but will probably become feasible with proposal
15507 158. Spotted by rovv. Fixes another case of bug 752.
15508 - Fix a bug in address parsing that was preventing bridges or hidden
15509 service targets from being at IPv6 addresses.
15510 - Do not remove routers as too old if we do not have any consensus
15511 document. Bugfix on 0.2.0.7-alpha.
15512 - When an exit relay resolves a stream address to a local IP address,
15513 do not just keep retrying that same exit relay over and
15514 over. Instead, just close the stream. Addresses bug 872. Bugfix
15515 on 0.2.0.32. Patch from rovv.
15516 - Made Tor a little less aggressive about deleting expired
15517 certificates. Partial fix for bug 854.
15518 - Treat duplicate certificate fetches as failures, so that we do
15519 not try to re-fetch an expired certificate over and over and over.
15520 - Do not say we're fetching a certificate when we'll in fact skip it
15521 because of a pending download.
15522 - If we have correct permissions on $datadir, we complain to stdout
15523 and fail to start. But dangerous permissions on
15524 $datadir/cached-status/ would cause us to open a log and complain
15525 there. Now complain to stdout and fail to start in both cases. Fixes
15526 bug 820, reported by seeess.
15528 o Minor bugfixes (bridges):
15529 - When we made bridge authorities stop serving bridge descriptors over
15530 unencrypted links, we also broke DirPort reachability testing for
15531 bridges. So bridges with a non-zero DirPort were printing spurious
15532 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
15533 - Don't allow a bridge to publish its router descriptor to a
15534 non-bridge directory authority. Fixes part of bug 932.
15535 - When we change to or from being a bridge, reset our counts of
15536 client usage by country. Fixes bug 932.
15538 o Minor bugfixes (relays):
15539 - Log correct error messages for DNS-related network errors on
15541 - Actually return -1 in the error case for read_bandwidth_usage().
15542 Harmless bug, since we currently don't care about the return value
15543 anywhere. Bugfix on 0.2.0.9-alpha.
15544 - Provide a more useful log message if bug 977 (related to buffer
15545 freelists) ever reappears, and do not crash right away.
15546 - We were already rejecting relay begin cells with destination port
15547 of 0. Now also reject extend cells with destination port or address
15548 of 0. Suggested by lark.
15549 - When we can't transmit a DNS request due to a network error, retry
15550 it after a while, and eventually transmit a failing response to
15551 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
15552 - Solve a bug that kept hardware crypto acceleration from getting
15553 enabled when accounting was turned on. Fixes bug 907. Bugfix on
15555 - When a canonical connection appears later in our internal list
15556 than a noncanonical one for a given OR ID, always use the
15557 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
15559 - Avoid some nasty corner cases in the logic for marking connections
15560 as too old or obsolete or noncanonical for circuits. Partial
15562 - Fix another interesting corner-case of bug 891 spotted by rovv:
15563 Previously, if two hosts had different amounts of clock drift, and
15564 one of them created a new connection with just the wrong timing,
15565 the other might decide to deprecate the new connection erroneously.
15566 Bugfix on 0.1.1.13-alpha.
15567 - If one win32 nameserver fails to get added, continue adding the
15568 rest, and don't automatically fail.
15569 - Fix a bug where an unreachable relay would establish enough
15570 reachability testing circuits to do a bandwidth test -- if
15571 we already have a connection to the middle hop of the testing
15572 circuit, then it could establish the last hop by using the existing
15573 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
15574 circuits no longer use entry guards in 0.2.1.3-alpha.
15576 o Minor bugfixes (directory authorities):
15577 - Limit uploaded directory documents to be 16M rather than 500K.
15578 The directory authorities were refusing v3 consensus votes from
15579 other authorities, since the votes are now 504K. Fixes bug 959;
15580 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
15581 - Directory authorities should never send a 503 "busy" response to
15582 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
15584 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
15585 headers. Bugfix on 0.2.0.10-alpha.
15587 o Minor bugfixes (hidden services):
15588 - When we can't find an intro key for a v2 hidden service descriptor,
15589 fall back to the v0 hidden service descriptor and log a bug message.
15590 Workaround for bug 1024.
15591 - In very rare situations new hidden service descriptors were
15592 published earlier than 30 seconds after the last change to the
15593 service. (We currently think that a hidden service descriptor
15594 that's been stable for 30 seconds is worth publishing.)
15595 - If a hidden service sends us an END cell, do not consider
15596 retrying the connection; just close it. Patch from rovv.
15597 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
15598 service directories if they have no advertised dir port. Bugfix
15601 o Minor bugfixes (tools):
15602 - In the torify(1) manpage, mention that tsocks will leak your
15605 o Minor bugfixes (controllers):
15606 - If the controller claimed responsibility for a stream, but that
15607 stream never finished making its connection, it would live
15608 forever in circuit_wait state. Now we close it after SocksTimeout
15609 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
15610 - Make DNS resolved controller events into "CLOSED", not
15611 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
15613 - The control port would close the connection before flushing long
15614 replies, such as the network consensus, if a QUIT command was issued
15615 before the reply had completed. Now, the control port flushes all
15616 pending replies before closing the connection. Also fix a spurious
15617 warning when a QUIT command is issued after a malformed or rejected
15618 AUTHENTICATE command, but before the connection was closed. Patch
15619 by Marcus Griep. Fixes bugs 1015 and 1016.
15620 - Fix a bug that made stream bandwidth get misreported to the
15623 o Deprecated and removed features:
15624 - The old "tor --version --version" command, which would print out
15625 the subversion "Id" of most of the source files, is now removed. It
15626 turned out to be less useful than we'd expected, and harder to
15628 - RedirectExits has been removed. It was deprecated since
15630 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
15631 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
15632 - Cell pools are now always enabled; --disable-cell-pools is ignored.
15633 - Directory mirrors no longer fetch the v1 directory or
15634 running-routers files. They are obsolete, and nobody asks for them
15635 anymore. This is the first step to making v1 authorities obsolete.
15636 - Take out the TestVia config option, since it was a workaround for
15637 a bug that was fixed in Tor 0.1.1.21.
15638 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
15639 HiddenServiceExcludeNodes as obsolete: they never worked properly,
15640 and nobody seems to be using them. Fixes bug 754. Bugfix on
15641 0.1.0.1-rc. Patch from Christian Wilms.
15642 - Remove all backward-compatibility code for relays running
15643 versions of Tor so old that they no longer work at all on the
15646 o Code simplifications and refactoring:
15647 - Tool-assisted documentation cleanup. Nearly every function or
15648 static variable in Tor should have its own documentation now.
15649 - Rename the confusing or_is_obsolete field to the more appropriate
15650 is_bad_for_new_circs, and move it to or_connection_t where it
15652 - Move edge-only flags from connection_t to edge_connection_t: not
15653 only is this better coding, but on machines of plausible alignment,
15654 it should save 4-8 bytes per connection_t. "Every little bit helps."
15655 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
15656 for consistency; keep old option working for backward compatibility.
15657 - Simplify the code for finding connections to use for a circuit.
15658 - Revise the connection_new functions so that a more typesafe variant
15659 exists. This will work better with Coverity, and let us find any
15660 actual mistakes we're making here.
15661 - Refactor unit testing logic so that dmalloc can be used sensibly
15662 with unit tests to check for memory leaks.
15663 - Move all hidden-service related fields from connection and circuit
15664 structure to substructures: this way they won't eat so much memory.
15665 - Squeeze 2-5% out of client performance (according to oprofile) by
15666 improving the implementation of some policy-manipulation functions.
15667 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
15668 be more efficient. Formerly it was quadratic in the number of
15669 servers; now it should be linear. Fixes bug 509.
15670 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
15671 and n_conn_id_digest fields into a separate structure that's
15672 only needed when the circuit has not yet attached to an n_conn.
15673 - Optimize out calls to time(NULL) that occur for every IO operation,
15674 or for every cell. On systems like Windows where time() is a
15675 slow syscall, this fix will be slightly helpful.
15678 Changes in version 0.2.0.35 - 2009-06-24
15680 - Avoid crashing in the presence of certain malformed descriptors.
15681 Found by lark, and by automated fuzzing.
15682 - Fix an edge case where a malicious exit relay could convince a
15683 controller that the client's DNS question resolves to an internal IP
15684 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
15687 - Finally fix the bug where dynamic-IP relays disappear when their
15688 IP address changes: directory mirrors were mistakenly telling
15689 them their old address if they asked via begin_dir, so they
15690 never got an accurate answer about their new address, so they
15691 just vanished after a day. For belt-and-suspenders, relays that
15692 don't set Address in their config now avoid using begin_dir for
15693 all direct connections. Should fix bugs 827, 883, and 900.
15694 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
15695 that would occur on some exit nodes when DNS failures and timeouts
15696 occurred in certain patterns. Fix for bug 957.
15699 - When starting with a cache over a few days old, do not leak
15700 memory for the obsolete router descriptors in it. Bugfix on
15701 0.2.0.33; fixes bug 672.
15702 - Hidden service clients didn't use a cached service descriptor that
15703 was older than 15 minutes, but wouldn't fetch a new one either,
15704 because there was already one in the cache. Now, fetch a v2
15705 descriptor unless the same descriptor was added to the cache within
15706 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
15709 Changes in version 0.2.0.34 - 2009-02-08
15710 Tor 0.2.0.34 features several more security-related fixes. You should
15711 upgrade, especially if you run an exit relay (remote crash) or a
15712 directory authority (remote infinite loop), or you're on an older
15713 (pre-XP) or not-recently-patched Windows (remote exploit).
15715 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
15716 have many known flaws, and nobody should be using them. You should
15717 upgrade. If you're using a Linux or BSD and its packages are obsolete,
15718 stop using those packages and upgrade anyway.
15721 - Fix an infinite-loop bug on handling corrupt votes under certain
15722 circumstances. Bugfix on 0.2.0.8-alpha.
15723 - Fix a temporary DoS vulnerability that could be performed by
15724 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
15725 - Avoid a potential crash on exit nodes when processing malformed
15726 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
15727 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
15728 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
15731 - Fix compilation on systems where time_t is a 64-bit integer.
15732 Patch from Matthias Drochner.
15733 - Don't consider expiring already-closed client connections. Fixes
15734 bug 893. Bugfix on 0.0.2pre20.
15737 Changes in version 0.2.0.33 - 2009-01-21
15738 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
15739 useful to users. It also finally fixes a bug where a relay or client
15740 that's been off for many days would take a long time to bootstrap.
15742 This update also fixes an important security-related bug reported by
15743 Ilja van Sprundel. You should upgrade. (We'll send out more details
15744 about the bug once people have had some time to upgrade.)
15747 - Fix a heap-corruption bug that may be remotely triggerable on
15748 some platforms. Reported by Ilja van Sprundel.
15751 - When a stream at an exit relay is in state "resolving" or
15752 "connecting" and it receives an "end" relay cell, the exit relay
15753 would silently ignore the end cell and not close the stream. If
15754 the client never closes the circuit, then the exit relay never
15755 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
15756 reported by "wood".
15757 - When sending CREATED cells back for a given circuit, use a 64-bit
15758 connection ID to find the right connection, rather than an addr:port
15759 combination. Now that we can have multiple OR connections between
15760 the same ORs, it is no longer possible to use addr:port to uniquely
15761 identify a connection.
15762 - Bridge relays that had DirPort set to 0 would stop fetching
15763 descriptors shortly after startup, and then briefly resume
15764 after a new bandwidth test and/or after publishing a new bridge
15765 descriptor. Bridge users that try to bootstrap from them would
15766 get a recent networkstatus but would get descriptors from up to
15767 18 hours earlier, meaning most of the descriptors were obsolete
15768 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
15769 - Prevent bridge relays from serving their 'extrainfo' document
15770 to anybody who asks, now that extrainfo docs include potentially
15771 sensitive aggregated client geoip summaries. Bugfix on
15773 - If the cached networkstatus consensus is more than five days old,
15774 discard it rather than trying to use it. In theory it could be
15775 useful because it lists alternate directory mirrors, but in practice
15776 it just means we spend many minutes trying directory mirrors that
15777 are long gone from the network. Also discard router descriptors as
15778 we load them if they are more than five days old, since the onion
15779 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
15782 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
15783 could make gcc generate non-functional binary search code. Bugfix
15785 - Build correctly on platforms without socklen_t.
15786 - Compile without warnings on solaris.
15787 - Avoid potential crash on internal error during signature collection.
15788 Fixes bug 864. Patch from rovv.
15789 - Correct handling of possible malformed authority signing key
15790 certificates with internal signature types. Fixes bug 880.
15791 Bugfix on 0.2.0.3-alpha.
15792 - Fix a hard-to-trigger resource leak when logging credential status.
15794 - When we can't initialize DNS because the network is down, do not
15795 automatically stop Tor from starting. Instead, we retry failed
15796 dns_init() every 10 minutes, and change the exit policy to reject
15797 *:* until one succeeds. Fixes bug 691.
15798 - Use 64 bits instead of 32 bits for connection identifiers used with
15799 the controller protocol, to greatly reduce risk of identifier reuse.
15800 - When we're choosing an exit node for a circuit, and we have
15801 no pending streams, choose a good general exit rather than one that
15802 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
15803 - Fix another case of assuming, when a specific exit is requested,
15804 that we know more than the user about what hosts it allows.
15805 Fixes one case of bug 752. Patch from rovv.
15806 - Clip the MaxCircuitDirtiness config option to a minimum of 10
15807 seconds. Warn the user if lower values are given in the
15808 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
15809 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
15810 user if lower values are given in the configuration. Bugfix on
15811 0.1.1.17-rc. Patch by Sebastian.
15812 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
15813 the cache because we already had a v0 descriptor with the same ID.
15814 Bugfix on 0.2.0.18-alpha.
15815 - Fix a race condition when freeing keys shared between main thread
15816 and CPU workers that could result in a memory leak. Bugfix on
15817 0.1.0.1-rc. Fixes bug 889.
15818 - Send a valid END cell back when a client tries to connect to a
15819 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
15820 840. Patch from rovv.
15821 - Check which hops rendezvous stream cells are associated with to
15822 prevent possible guess-the-streamid injection attacks from
15823 intermediate hops. Fixes another case of bug 446. Based on patch
15825 - If a broken client asks a non-exit router to connect somewhere,
15826 do not even do the DNS lookup before rejecting the connection.
15827 Fixes another case of bug 619. Patch from rovv.
15828 - When a relay gets a create cell it can't decrypt (e.g. because it's
15829 using the wrong onion key), we were dropping it and letting the
15830 client time out. Now actually answer with a destroy cell. Fixes
15831 bug 904. Bugfix on 0.0.2pre8.
15833 o Minor bugfixes (hidden services):
15834 - Do not throw away existing introduction points on SIGHUP. Bugfix on
15835 0.0.6pre1. Patch by Karsten. Fixes bug 874.
15838 - Report the case where all signatures in a detached set are rejected
15839 differently than the case where there is an error handling the
15841 - When we realize that another process has modified our cached
15842 descriptors, print out a more useful error message rather than
15843 triggering an assertion. Fixes bug 885. Patch from Karsten.
15844 - Implement the 0x20 hack to better resist DNS poisoning: set the
15845 case on outgoing DNS requests randomly, and reject responses that do
15846 not match the case correctly. This logic can be disabled with the
15847 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
15848 of servers that do not reliably preserve case in replies. See
15849 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
15851 - Check DNS replies for more matching fields to better resist DNS
15853 - Never use OpenSSL compression: it wastes RAM and CPU trying to
15854 compress cells, which are basically all encrypted, compressed, or
15858 Changes in version 0.2.0.32 - 2008-11-20
15859 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
15860 packages (and maybe other packages) noticed by Theo de Raadt, fixes
15861 a smaller security flaw that might allow an attacker to access local
15862 services, further improves hidden service performance, and fixes a
15863 variety of other issues.
15866 - The "User" and "Group" config options did not clear the
15867 supplementary group entries for the Tor process. The "User" option
15868 is now more robust, and we now set the groups to the specified
15869 user's primary group. The "Group" option is now ignored. For more
15870 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
15871 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
15872 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
15873 - The "ClientDNSRejectInternalAddresses" config option wasn't being
15874 consistently obeyed: if an exit relay refuses a stream because its
15875 exit policy doesn't allow it, we would remember what IP address
15876 the relay said the destination address resolves to, even if it's
15877 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
15880 - Fix a DOS opportunity during the voting signature collection process
15881 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
15883 o Major bugfixes (hidden services):
15884 - When fetching v0 and v2 rendezvous service descriptors in parallel,
15885 we were failing the whole hidden service request when the v0
15886 descriptor fetch fails, even if the v2 fetch is still pending and
15887 might succeed. Similarly, if the last v2 fetch fails, we were
15888 failing the whole hidden service request even if a v0 fetch is
15889 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
15890 - When extending a circuit to a hidden service directory to upload a
15891 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
15892 requests failed, because the router descriptor has not been
15893 downloaded yet. In these cases, do not attempt to upload the
15894 rendezvous descriptor, but wait until the router descriptor is
15895 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
15896 descriptor from a hidden service directory for which the router
15897 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
15901 - Fix several infrequent memory leaks spotted by Coverity.
15902 - When testing for libevent functions, set the LDFLAGS variable
15903 correctly. Found by Riastradh.
15904 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
15905 bootstrapping with tunneled directory connections. Bugfix on
15906 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
15907 - When asked to connect to A.B.exit:80, if we don't know the IP for A
15908 and we know that server B rejects most-but-not all connections to
15909 port 80, we would previously reject the connection. Now, we assume
15910 the user knows what they were asking for. Fixes bug 752. Bugfix
15911 on 0.0.9rc5. Diagnosed by BarkerJr.
15912 - If we overrun our per-second write limits a little, count this as
15913 having used up our write allocation for the second, and choke
15914 outgoing directory writes. Previously, we had only counted this when
15915 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
15916 Bugfix on 0.2.0.x (??).
15917 - Remove the old v2 directory authority 'lefkada' from the default
15918 list. It has been gone for many months.
15919 - Stop doing unaligned memory access that generated bus errors on
15920 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
15921 - Make USR2 log-level switch take effect immediately. Bugfix on
15924 o Minor bugfixes (controller):
15925 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
15926 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
15929 Changes in version 0.2.0.31 - 2008-09-03
15930 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
15931 a big bug we're seeing where in rare cases traffic from one Tor stream
15932 gets mixed into another stream, and fixes a variety of smaller issues.
15935 - Make sure that two circuits can never exist on the same connection
15936 with the same circuit ID, even if one is marked for close. This
15937 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
15938 - Relays now reject risky extend cells: if the extend cell includes
15939 a digest of all zeroes, or asks to extend back to the relay that
15940 sent the extend cell, tear down the circuit. Ideas suggested
15942 - If not enough of our entry guards are available so we add a new
15943 one, we might use the new one even if it overlapped with the
15944 current circuit's exit relay (or its family). Anonymity bugfix
15945 pointed out by rovv.
15948 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
15949 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
15950 - Correctly detect the presence of the linux/netfilter_ipv4.h header
15951 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
15952 - Pick size of default geoip filename string correctly on windows.
15953 Fixes bug 806. Bugfix on 0.2.0.30.
15954 - Make the autoconf script accept the obsolete --with-ssl-dir
15955 option as an alias for the actually-working --with-openssl-dir
15956 option. Fix the help documentation to recommend --with-openssl-dir.
15957 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
15958 - When using the TransPort option on OpenBSD, and using the User
15959 option to change UID and drop privileges, make sure to open
15960 /dev/pf before dropping privileges. Fixes bug 782. Patch from
15961 Christopher Davis. Bugfix on 0.1.2.1-alpha.
15962 - Try to attach connections immediately upon receiving a RENDEZVOUS2
15963 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
15964 on the client side when connecting to a hidden service. Bugfix
15965 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
15966 - When closing an application-side connection because its circuit is
15967 getting torn down, generate the stream event correctly. Bugfix on
15968 0.1.2.x. Anonymous patch.
15971 Changes in version 0.2.0.30 - 2008-07-15
15972 This new stable release switches to a more efficient directory
15973 distribution design, adds features to make connections to the Tor
15974 network harder to block, allows Tor to act as a DNS proxy, adds separate
15975 rate limiting for relayed traffic to make it easier for clients to
15976 become relays, fixes a variety of potential anonymity problems, and
15977 includes the usual huge pile of other features and bug fixes.
15979 o New v3 directory design:
15980 - Tor now uses a new way to learn about and distribute information
15981 about the network: the directory authorities vote on a common
15982 network status document rather than each publishing their own
15983 opinion. Now clients and caches download only one networkstatus
15984 document to bootstrap, rather than downloading one for each
15985 authority. Clients only download router descriptors listed in
15986 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
15988 - Set up moria1, tor26, and dizum as v3 directory authorities
15989 in addition to being v2 authorities. Also add three new ones:
15990 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
15991 dannenberg (run by CCC).
15992 - Switch to multi-level keys for directory authorities: now their
15993 long-term identity key can be kept offline, and they periodically
15994 generate a new signing key. Clients fetch the "key certificates"
15995 to keep up to date on the right keys. Add a standalone tool
15996 "tor-gencert" to generate key certificates. Implements proposal 103.
15997 - Add a new V3AuthUseLegacyKey config option to make it easier for
15998 v3 authorities to change their identity keys if another bug like
15999 Debian's OpenSSL RNG flaw appears.
16000 - Authorities and caches fetch the v2 networkstatus documents
16001 less often, now that v3 is recommended.
16003 o Make Tor connections stand out less on the wire:
16004 - Use an improved TLS handshake designed by Steven Murdoch in proposal
16005 124, as revised in proposal 130. The new handshake is meant to
16006 be harder for censors to fingerprint, and it adds the ability
16007 to detect certain kinds of man-in-the-middle traffic analysis
16008 attacks. The new handshake format includes version negotiation for
16009 OR connections as described in proposal 105, which will allow us
16010 to improve Tor's link protocol more safely in the future.
16011 - Enable encrypted directory connections by default for non-relays,
16012 so censor tools that block Tor directory connections based on their
16013 plaintext patterns will no longer work. This means Tor works in
16014 certain censored countries by default again.
16015 - Stop including recognizeable strings in the commonname part of
16016 Tor's x509 certificates.
16018 o Implement bridge relays:
16019 - Bridge relays (or "bridges" for short) are Tor relays that aren't
16020 listed in the main Tor directory. Since there is no complete public
16021 list of them, even an ISP that is filtering connections to all the
16022 known Tor relays probably won't be able to block all the bridges.
16023 See doc/design-paper/blocking.pdf and proposal 125 for details.
16024 - New config option BridgeRelay that specifies you want to be a
16025 bridge relay rather than a normal relay. When BridgeRelay is set
16026 to 1, then a) you cache dir info even if your DirPort ins't on,
16027 and b) the default for PublishServerDescriptor is now "bridge"
16028 rather than "v2,v3".
16029 - New config option "UseBridges 1" for clients that want to use bridge
16030 relays instead of ordinary entry guards. Clients then specify
16031 bridge relays by adding "Bridge" lines to their config file. Users
16032 can learn about a bridge relay either manually through word of
16033 mouth, or by one of our rate-limited mechanisms for giving out
16034 bridge addresses without letting an attacker easily enumerate them
16035 all. See https://www.torproject.org/bridges for details.
16036 - Bridge relays behave like clients with respect to time intervals
16037 for downloading new v3 consensus documents -- otherwise they
16038 stand out. Bridge users now wait until the end of the interval,
16039 so their bridge relay will be sure to have a new consensus document.
16041 o Implement bridge directory authorities:
16042 - Bridge authorities are like normal directory authorities, except
16043 they don't serve a list of known bridges. Therefore users that know
16044 a bridge's fingerprint can fetch a relay descriptor for that bridge,
16045 including fetching updates e.g. if the bridge changes IP address,
16046 yet an attacker can't just fetch a list of all the bridges.
16047 - Set up Tonga as the default bridge directory authority.
16048 - Bridge authorities refuse to serve bridge descriptors or other
16049 bridge information over unencrypted connections (that is, when
16050 responding to direct DirPort requests rather than begin_dir cells.)
16051 - Bridge directory authorities do reachability testing on the
16052 bridges they know. They provide router status summaries to the
16053 controller via "getinfo ns/purpose/bridge", and also dump summaries
16054 to a file periodically, so we can keep internal stats about which
16055 bridges are functioning.
16056 - If bridge users set the UpdateBridgesFromAuthority config option,
16057 but the digest they ask for is a 404 on the bridge authority,
16058 they fall back to contacting the bridge directly.
16059 - Bridges always use begin_dir to publish their server descriptor to
16060 the bridge authority using an anonymous encrypted tunnel.
16061 - Early work on a "bridge community" design: if bridge authorities set
16062 the BridgePassword config option, they will serve a snapshot of
16063 known bridge routerstatuses from their DirPort to anybody who
16064 knows that password. Unset by default.
16065 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
16066 report sanitized aggregated summaries in their extra-info documents
16067 privately to the bridge authority, listing which countries are
16068 able to reach them. We hope this mechanism will let us learn when
16069 certain countries start trying to block bridges.
16070 - Bridge authorities write bridge descriptors to disk, so they can
16071 reload them after a reboot. They can also export the descriptors
16072 to other programs, so we can distribute them to blocked users via
16073 the BridgeDB interface, e.g. via https://bridges.torproject.org/
16074 and bridges@torproject.org.
16076 o Tor can be a DNS proxy:
16077 - The new client-side DNS proxy feature replaces the need for
16078 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
16079 for DNS requests on port 9999, use the Tor network to resolve them
16080 anonymously, and send the reply back like a regular DNS server.
16081 The code still only implements a subset of DNS.
16082 - Add a new AutomapHostsOnResolve option: when it is enabled, any
16083 resolve request for hosts matching a given pattern causes Tor to
16084 generate an internal virtual address mapping for that host. This
16085 allows DNSPort to work sensibly with hidden service users. By
16086 default, .exit and .onion addresses are remapped; the list of
16087 patterns can be reconfigured with AutomapHostsSuffixes.
16088 - Add an "-F" option to tor-resolve to force a resolve for a .onion
16089 address. Thanks to the AutomapHostsOnResolve option, this is no
16090 longer a completely silly thing to do.
16092 o Major features (relay usability):
16093 - New config options RelayBandwidthRate and RelayBandwidthBurst:
16094 a separate set of token buckets for relayed traffic. Right now
16095 relayed traffic is defined as answers to directory requests, and
16096 OR connections that don't have any local circuits on them. See
16097 proposal 111 for details.
16098 - Create listener connections before we setuid to the configured
16099 User and Group. Now non-Windows users can choose port values
16100 under 1024, start Tor as root, and have Tor bind those ports
16101 before it changes to another UID. (Windows users could already
16103 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
16104 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
16105 on "vserver" accounts. Patch from coderman.
16107 o Major features (directory authorities):
16108 - Directory authorities track weighted fractional uptime and weighted
16109 mean-time-between failures for relays. WFU is suitable for deciding
16110 whether a node is "usually up", while MTBF is suitable for deciding
16111 whether a node is "likely to stay up." We need both, because
16112 "usually up" is a good requirement for guards, while "likely to
16113 stay up" is a good requirement for long-lived connections.
16114 - Directory authorities use a new formula for selecting which relays
16115 to advertise as Guards: they must be in the top 7/8 in terms of
16116 how long we have known about them, and above the median of those
16117 nodes in terms of weighted fractional uptime.
16118 - Directory authorities use a new formula for selecting which relays
16119 to advertise as Stable: when we have 4 or more days of data, use
16120 median measured MTBF rather than median declared uptime. Implements
16122 - Directory authorities accept and serve "extra info" documents for
16123 routers. Routers now publish their bandwidth-history lines in the
16124 extra-info docs rather than the main descriptor. This step saves
16125 60% (!) on compressed router descriptor downloads. Servers upload
16126 extra-info docs to any authority that accepts them; directory
16127 authorities now allow multiple router descriptors and/or extra
16128 info documents to be uploaded in a single go. Authorities, and
16129 caches that have been configured to download extra-info documents,
16130 download them as needed. Implements proposal 104.
16131 - Authorities now list relays who have the same nickname as
16132 a different named relay, but list them with a new flag:
16133 "Unnamed". Now we can make use of relays that happen to pick the
16134 same nickname as a server that registered two years ago and then
16135 disappeared. Implements proposal 122.
16136 - Store routers in a file called cached-descriptors instead of in
16137 cached-routers. Initialize cached-descriptors from cached-routers
16138 if the old format is around. The new format allows us to store
16139 annotations along with descriptors, to record the time we received
16140 each descriptor, its source, and its purpose: currently one of
16141 general, controller, or bridge.
16143 o Major features (other):
16144 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
16145 Tor can warn and/or refuse connections to ports commonly used with
16146 vulnerable-plaintext protocols. Currently we warn on ports 23,
16147 109, 110, and 143, but we don't reject any. Based on proposal 129
16148 by Kevin Bauer and Damon McCoy.
16149 - Integrate Karsten Loesing's Google Summer of Code project to publish
16150 hidden service descriptors on a set of redundant relays that are a
16151 function of the hidden service address. Now we don't have to rely
16152 on three central hidden service authorities for publishing and
16153 fetching every hidden service descriptor. Implements proposal 114.
16154 - Allow tunnelled directory connections to ask for an encrypted
16155 "begin_dir" connection or an anonymized "uses a full Tor circuit"
16156 connection independently. Now we can make anonymized begin_dir
16157 connections for (e.g.) more secure hidden service posting and
16160 o Major bugfixes (crashes and assert failures):
16161 - Stop imposing an arbitrary maximum on the number of file descriptors
16162 used for busy servers. Bug reported by Olaf Selke; patch from
16164 - Avoid possible failures when generating a directory with routers
16165 with over-long versions strings, or too many flags set.
16166 - Fix a rare assert error when we're closing one of our threads:
16167 use a mutex to protect the list of logs, so we never write to the
16168 list as it's being freed. Fixes the very rare bug 575, which is
16169 kind of the revenge of bug 222.
16170 - Avoid segfault in the case where a badly behaved v2 versioning
16171 directory sends a signed networkstatus with missing client-versions.
16172 - When we hit an EOF on a log (probably because we're shutting down),
16173 don't try to remove the log from the list: just mark it as
16174 unusable. (Bulletproofs against bug 222.)
16176 o Major bugfixes (code security fixes):
16177 - Detect size overflow in zlib code. Reported by Justin Ferguson and
16179 - Rewrite directory tokenization code to never run off the end of
16180 a string. Fixes bug 455. Patch from croup.
16181 - Be more paranoid about overwriting sensitive memory on free(),
16182 as a defensive programming tactic to ensure forward secrecy.
16184 o Major bugfixes (anonymity fixes):
16185 - Reject requests for reverse-dns lookup of names that are in
16186 a private address space. Patch from lodger.
16187 - Never report that we've used more bandwidth than we're willing to
16188 relay: it leaks how much non-relay traffic we're using. Resolves
16190 - As a client, do not believe any server that tells us that an
16191 address maps to an internal address space.
16192 - Warn about unsafe ControlPort configurations.
16193 - Directory authorities now call routers Fast if their bandwidth is
16194 at least 100KB/s, and consider their bandwidth adequate to be a
16195 Guard if it is at least 250KB/s, no matter the medians. This fix
16196 complements proposal 107.
16197 - Directory authorities now never mark more than 2 servers per IP as
16198 Valid and Running (or 5 on addresses shared by authorities).
16199 Implements proposal 109, by Kevin Bauer and Damon McCoy.
16200 - If we're a relay, avoid picking ourselves as an introduction point,
16201 a rendezvous point, or as the final hop for internal circuits. Bug
16202 reported by taranis and lodger.
16203 - Exit relays that are used as a client can now reach themselves
16204 using the .exit notation, rather than just launching an infinite
16205 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
16206 - Fix a bug where, when we were choosing the 'end stream reason' to
16207 put in our relay end cell that we send to the exit relay, Tor
16208 clients on Windows were sometimes sending the wrong 'reason'. The
16209 anonymity problem is that exit relays may be able to guess whether
16210 the client is running Windows, thus helping partition the anonymity
16211 set. Down the road we should stop sending reasons to exit relays,
16212 or otherwise prevent future versions of this bug.
16213 - Only update guard status (usable / not usable) once we have
16214 enough directory information. This was causing us to discard all our
16215 guards on startup if we hadn't been running for a few weeks. Fixes
16217 - When our directory information has been expired for a while, stop
16218 being willing to build circuits using it. Fixes bug 401.
16220 o Major bugfixes (peace of mind for relay operators)
16221 - Non-exit relays no longer answer "resolve" relay cells, so they
16222 can't be induced to do arbitrary DNS requests. (Tor clients already
16223 avoid using non-exit relays for resolve cells, but now servers
16224 enforce this too.) Fixes bug 619. Patch from lodger.
16225 - When we setconf ClientOnly to 1, close any current OR and Dir
16226 listeners. Reported by mwenge.
16228 o Major bugfixes (other):
16229 - If we only ever used Tor for hidden service lookups or posts, we
16230 would stop building circuits and start refusing connections after
16231 24 hours, since we falsely believed that Tor was dormant. Reported
16233 - Add a new __HashedControlSessionPassword option for controllers
16234 to use for one-off session password hashes that shouldn't get
16235 saved to disk by SAVECONF --- Vidalia users were accumulating a
16236 pile of HashedControlPassword lines in their torrc files, one for
16237 each time they had restarted Tor and then clicked Save. Make Tor
16238 automatically convert "HashedControlPassword" to this new option but
16239 only when it's given on the command line. Partial fix for bug 586.
16240 - Patch from "Andrew S. Lists" to catch when we contact a directory
16241 mirror at IP address X and he says we look like we're coming from
16242 IP address X. Otherwise this would screw up our address detection.
16243 - Reject uploaded descriptors and extrainfo documents if they're
16244 huge. Otherwise we'll cache them all over the network and it'll
16245 clog everything up. Suggested by Aljosha Judmayer.
16246 - When a hidden service was trying to establish an introduction point,
16247 and Tor *did* manage to reuse one of the preemptively built
16248 circuits, it didn't correctly remember which one it used,
16249 so it asked for another one soon after, until there were no
16250 more preemptive circuits, at which point it launched one from
16251 scratch. Bugfix on 0.0.9.x.
16253 o Rate limiting and load balancing improvements:
16254 - When we add data to a write buffer in response to the data on that
16255 write buffer getting low because of a flush, do not consider the
16256 newly added data as a candidate for immediate flushing, but rather
16257 make it wait until the next round of writing. Otherwise, we flush
16258 and refill recursively, and a single greedy TLS connection can
16259 eat all of our bandwidth.
16260 - When counting the number of bytes written on a TLS connection,
16261 look at the BIO actually used for writing to the network, not
16262 at the BIO used (sometimes) to buffer data for the network.
16263 Looking at different BIOs could result in write counts on the
16264 order of ULONG_MAX. Fixes bug 614.
16265 - If we change our MaxAdvertisedBandwidth and then reload torrc,
16266 Tor won't realize it should publish a new relay descriptor. Fixes
16267 bug 688, reported by mfr.
16268 - Avoid using too little bandwidth when our clock skips a few seconds.
16269 - Choose which bridge to use proportional to its advertised bandwidth,
16270 rather than uniformly at random. This should speed up Tor for
16271 bridge users. Also do this for people who set StrictEntryNodes.
16273 o Bootstrapping faster and building circuits more intelligently:
16274 - Fix bug 660 that was preventing us from knowing that we should
16275 preemptively build circuits to handle expected directory requests.
16276 - When we're checking if we have enough dir info for each relay
16277 to begin establishing circuits, make sure that we actually have
16278 the descriptor listed in the consensus, not just any descriptor.
16279 - Correctly notify one-hop connections when a circuit build has
16280 failed. Possible fix for bug 669. Found by lodger.
16281 - Clients now hold circuitless TLS connections open for 1.5 times
16282 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
16283 rebuild a new circuit over them within that timeframe. Previously,
16284 they held them open only for KeepalivePeriod (5 minutes).
16286 o Performance improvements (memory):
16287 - Add OpenBSD malloc code from "phk" as an optional malloc
16288 replacement on Linux: some glibc libraries do very poorly with
16289 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
16290 ./configure to get the replacement malloc code.
16291 - Switch our old ring buffer implementation for one more like that
16292 used by free Unix kernels. The wasted space in a buffer with 1mb
16293 of data will now be more like 8k than 1mb. The new implementation
16294 also avoids realloc();realloc(); patterns that can contribute to
16295 memory fragmentation.
16296 - Change the way that Tor buffers data that it is waiting to write.
16297 Instead of queueing data cells in an enormous ring buffer for each
16298 client->OR or OR->OR connection, we now queue cells on a separate
16299 queue for each circuit. This lets us use less slack memory, and
16300 will eventually let us be smarter about prioritizing different kinds
16302 - Reference-count and share copies of address policy entries; only 5%
16303 of them were actually distinct.
16304 - Tune parameters for cell pool allocation to minimize amount of
16306 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
16307 for every single inactive connection_t. Free items from the
16308 4k/16k-buffer free lists when they haven't been used for a while.
16309 - Make memory debugging information describe more about history
16310 of cell allocation, so we can help reduce our memory use.
16311 - Be even more aggressive about releasing RAM from small
16312 empty buffers. Thanks to our free-list code, this shouldn't be too
16313 performance-intensive.
16314 - Log malloc statistics from mallinfo() on platforms where it exists.
16315 - Use memory pools to allocate cells with better speed and memory
16316 efficiency, especially on platforms where malloc() is inefficient.
16317 - Add a --with-tcmalloc option to the configure script to link
16318 against tcmalloc (if present). Does not yet search for non-system
16321 o Performance improvements (socket management):
16322 - Count the number of open sockets separately from the number of
16323 active connection_t objects. This will let us avoid underusing
16324 our allocated connection limit.
16325 - We no longer use socket pairs to link an edge connection to an
16326 anonymous directory connection or a DirPort test connection.
16327 Instead, we track the link internally and transfer the data
16328 in-process. This saves two sockets per "linked" connection (at the
16329 client and at the server), and avoids the nasty Windows socketpair()
16331 - We were leaking a file descriptor if Tor started with a zero-length
16332 cached-descriptors file. Patch by "freddy77".
16334 o Performance improvements (CPU use):
16335 - Never walk through the list of logs if we know that no log target
16336 is interested in a given message.
16337 - Call routerlist_remove_old_routers() much less often. This should
16338 speed startup, especially on directory caches.
16339 - Base64 decoding was actually showing up on our profile when parsing
16340 the initial descriptor file; switch to an in-process all-at-once
16341 implementation that's about 3.5x times faster than calling out to
16343 - Use a slightly simpler string hashing algorithm (copying Python's
16344 instead of Java's) and optimize our digest hashing algorithm to take
16345 advantage of 64-bit platforms and to remove some possibly-costly
16347 - When implementing AES counter mode, update only the portions of the
16348 counter buffer that need to change, and don't keep separate
16349 network-order and host-order counters on big-endian hosts (where
16350 they are the same).
16351 - Add an in-place version of aes_crypt() so that we can avoid doing a
16352 needless memcpy() call on each cell payload.
16353 - Use Critical Sections rather than Mutexes for synchronizing threads
16354 on win32; Mutexes are heavier-weight, and designed for synchronizing
16357 o Performance improvements (bandwidth use):
16358 - Don't try to launch new descriptor downloads quite so often when we
16359 already have enough directory information to build circuits.
16360 - Version 1 directories are no longer generated in full. Instead,
16361 authorities generate and serve "stub" v1 directories that list
16362 no servers. This will stop Tor versions 0.1.0.x and earlier from
16363 working, but (for security reasons) nobody should be running those
16365 - Avoid going directly to the directory authorities even if you're a
16366 relay, if you haven't found yourself reachable yet or if you've
16367 decided not to advertise your dirport yet. Addresses bug 556.
16368 - If we've gone 12 hours since our last bandwidth check, and we
16369 estimate we have less than 50KB bandwidth capacity but we could
16370 handle more, do another bandwidth test.
16371 - Support "If-Modified-Since" when answering HTTP requests for
16372 directories, running-routers documents, and v2 and v3 networkstatus
16373 documents. (There's no need to support it for router descriptors,
16374 since those are downloaded by descriptor digest.)
16375 - Stop fetching directory info so aggressively if your DirPort is
16376 on but your ORPort is off; stop fetching v2 dir info entirely.
16377 You can override these choices with the new FetchDirInfoEarly
16380 o Changed config option behavior (features):
16381 - Configuration files now accept C-style strings as values. This
16382 helps encode characters not allowed in the current configuration
16383 file format, such as newline or #. Addresses bug 557.
16384 - Add hidden services and DNSPorts to the list of things that make
16385 Tor accept that it has running ports. Change starting Tor with no
16386 ports from a fatal error to a warning; we might change it back if
16387 this turns out to confuse anybody. Fixes bug 579.
16388 - Make PublishServerDescriptor default to 1, so the default doesn't
16389 have to change as we invent new directory protocol versions.
16390 - Allow people to say PreferTunnelledDirConns rather than
16391 PreferTunneledDirConns, for those alternate-spellers out there.
16392 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
16393 accommodate the growing number of servers that use the default
16394 and are reaching it.
16395 - Make it possible to enable HashedControlPassword and
16396 CookieAuthentication at the same time.
16397 - When a TrackHostExits-chosen exit fails too many times in a row,
16398 stop using it. Fixes bug 437.
16400 o Changed config option behavior (bugfixes):
16401 - Do not read the configuration file when we've only been told to
16402 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
16403 based on patch from Sebastian Hahn.
16404 - Actually validate the options passed to AuthDirReject,
16405 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
16406 - Make "ClientOnly 1" config option disable directory ports too.
16407 - Don't stop fetching descriptors when FetchUselessDescriptors is
16408 set, even if we stop asking for circuits. Bug reported by tup
16410 - Servers used to decline to publish their DirPort if their
16411 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
16412 they look only at BandwidthRate and RelayBandwidthRate.
16413 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
16414 minus 1 byte: the actual maximum declared bandwidth.
16415 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
16416 - Make the NodeFamilies config option work. (Reported by
16417 lodger -- it has never actually worked, even though we added it
16419 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
16420 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
16422 o New config options:
16423 - New configuration options AuthDirMaxServersPerAddr and
16424 AuthDirMaxServersperAuthAddr to override default maximum number
16425 of servers allowed on a single IP address. This is important for
16426 running a test network on a single host.
16427 - Three new config options (AlternateDirAuthority,
16428 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
16429 user selectively replace the default directory authorities by type,
16430 rather than the all-or-nothing replacement that DirServer offers.
16431 - New config options AuthDirBadDir and AuthDirListBadDirs for
16432 authorities to mark certain relays as "bad directories" in the
16433 networkstatus documents. Also supports the "!baddir" directive in
16434 the approved-routers file.
16435 - New config option V2AuthoritativeDirectory that all v2 directory
16436 authorities must set. This lets v3 authorities choose not to serve
16437 v2 directory information.
16439 o Minor features (other):
16440 - When we're not serving v2 directory information, there is no reason
16441 to actually keep any around. Remove the obsolete files and directory
16442 on startup if they are very old and we aren't going to serve them.
16443 - When we negotiate a v2 link-layer connection (not yet implemented),
16444 accept RELAY_EARLY cells and turn them into RELAY cells if we've
16445 negotiated a v1 connection for their next step. Initial steps for
16447 - When we have no consensus, check FallbackNetworkstatusFile (defaults
16448 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
16449 we can start out knowing some directory caches. We don't ship with
16450 a fallback consensus by default though, because it was making
16451 bootstrapping take too long while we tried many down relays.
16452 - Authorities send back an X-Descriptor-Not-New header in response to
16453 an accepted-but-discarded descriptor upload. Partially implements
16455 - If we find a cached-routers file that's been sitting around for more
16456 than 28 days unmodified, then most likely it's a leftover from
16457 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
16459 - When we (as a cache) download a descriptor because it was listed
16460 in a consensus, remember when the consensus was supposed to expire,
16461 and don't expire the descriptor until then.
16462 - Optionally (if built with -DEXPORTMALLINFO) export the output
16463 of mallinfo via http, as tor/mallinfo.txt. Only accessible
16465 - Tag every guard node in our state file with the version that
16466 we believe added it, or with our own version if we add it. This way,
16467 if a user temporarily runs an old version of Tor and then switches
16468 back to a new one, she doesn't automatically lose her guards.
16469 - When somebody requests a list of statuses or servers, and we have
16470 none of those, return a 404 rather than an empty 200.
16471 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
16473 - Add an HSAuthorityRecordStats option that hidden service authorities
16474 can use to track statistics of overall hidden service usage without
16475 logging information that would be as useful to an attacker.
16476 - Allow multiple HiddenServicePort directives with the same virtual
16477 port; when they occur, the user is sent round-robin to one
16478 of the target ports chosen at random. Partially fixes bug 393 by
16479 adding limited ad-hoc round-robining.
16480 - Revamp file-writing logic so we don't need to have the entire
16481 contents of a file in memory at once before we write to disk. Tor,
16484 o Minor bugfixes (other):
16485 - Alter the code that tries to recover from unhandled write
16486 errors, to not try to flush onto a socket that's given us
16488 - Directory mirrors no longer include a guess at the client's IP
16489 address if the connection appears to be coming from the same /24
16490 network; it was producing too many wrong guesses.
16491 - If we're trying to flush the last bytes on a connection (for
16492 example, when answering a directory request), reset the
16493 time-to-give-up timeout every time we manage to write something
16495 - Reject router descriptors with out-of-range bandwidthcapacity or
16496 bandwidthburst values.
16497 - If we can't expand our list of entry guards (e.g. because we're
16498 using bridges or we have StrictEntryNodes set), don't mark relays
16499 down when they fail a directory request. Otherwise we're too quick
16500 to mark all our entry points down.
16501 - Authorities no longer send back "400 you're unreachable please fix
16502 it" errors to Tor servers that aren't online all the time. We're
16503 supposed to tolerate these servers now.
16504 - Let directory authorities startup even when they can't generate
16505 a descriptor immediately, e.g. because they don't know their
16507 - Correctly enforce that elements of directory objects do not appear
16508 more often than they are allowed to appear.
16509 - Stop allowing hibernating servers to be "stable" or "fast".
16510 - On Windows, we were preventing other processes from reading
16511 cached-routers while Tor was running. (Reported by janbar)
16512 - Check return values from pthread_mutex functions.
16513 - When opening /dev/null in finish_daemonize(), do not pass the
16514 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
16515 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
16517 o Controller features:
16518 - The GETCONF command now escapes and quotes configuration values
16519 that don't otherwise fit into the torrc file.
16520 - The SETCONF command now handles quoted values correctly.
16521 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
16522 ask about source, timestamp of arrival, purpose, etc. We need
16523 something like this to help Vidalia not do GeoIP lookups on bridge
16525 - Allow multiple HashedControlPassword config lines, to support
16526 multiple controller passwords.
16527 - Accept LF instead of CRLF on controller, since some software has a
16528 hard time generating real Internet newlines.
16529 - Add GETINFO values for the server status events
16530 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
16532 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
16533 GETINFO for Torstat to use until it can switch to using extrainfos.
16534 - New config option CookieAuthFile to choose a new location for the
16535 cookie authentication file, and config option
16536 CookieAuthFileGroupReadable to make it group-readable.
16537 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
16538 match requests to applications. Patch from Robert Hogan.
16539 - Add a RESOLVE command to launch hostname lookups. Original patch
16541 - Add GETINFO status/enough-dir-info to let controllers tell whether
16542 Tor has downloaded sufficient directory information. Patch from Tup.
16543 - You can now use the ControlSocket option to tell Tor to listen for
16544 controller connections on Unix domain sockets on systems that
16545 support them. Patch from Peter Palfrader.
16546 - New "GETINFO address-mappings/*" command to get address mappings
16547 with expiry information. "addr-mappings/*" is now deprecated.
16549 - Add a new config option __DisablePredictedCircuits designed for
16550 use by the controller, when we don't want Tor to build any circuits
16552 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
16553 so we can exit from the middle of the circuit.
16554 - Implement "getinfo status/circuit-established".
16555 - Implement "getinfo status/version/..." so a controller can tell
16556 whether the current version is recommended, and whether any versions
16557 are good, and how many authorities agree. Patch from "shibz".
16558 - Controllers should now specify cache=no or cache=yes when using
16559 the +POSTDESCRIPTOR command.
16560 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
16561 Robert Hogan. Fixes the first part of bug 681.
16562 - When reporting clock skew, and we know that the clock is _at least
16563 as skewed_ as some value, but we don't know the actual value,
16564 report the value as a "minimum skew."
16566 o Controller bugfixes:
16567 - Generate "STATUS_SERVER" events rather than misspelled
16568 "STATUS_SEVER" events. Caught by mwenge.
16569 - Reject controller commands over 1MB in length, so rogue
16570 processes can't run us out of memory.
16571 - Change the behavior of "getinfo status/good-server-descriptor"
16572 so it doesn't return failure when any authority disappears.
16573 - Send NAMESERVER_STATUS messages for a single failed nameserver
16575 - When the DANGEROUS_VERSION controller status event told us we're
16576 running an obsolete version, it used the string "OLD" to describe
16577 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
16578 "OBSOLETE" in both cases.
16579 - Respond to INT and TERM SIGNAL commands before we execute the
16580 signal, in case the signal shuts us down. We had a patch in
16581 0.1.2.1-alpha that tried to do this by queueing the response on
16582 the connection's buffer before shutting down, but that really
16583 isn't the same thing at all. Bug located by Matt Edman.
16584 - Provide DNS expiry times in GMT, not in local time. For backward
16585 compatibility, ADDRMAP events only provide GMT expiry in an extended
16586 field. "GETINFO address-mappings" always does the right thing.
16587 - Use CRLF line endings properly in NS events.
16588 - Make 'getinfo fingerprint' return a 551 error if we're not a
16589 server, so we match what the control spec claims we do. Reported
16591 - Fix a typo in an error message when extendcircuit fails that
16592 caused us to not follow the \r\n-based delimiter protocol. Reported
16594 - When tunneling an encrypted directory connection, and its first
16595 circuit fails, do not leave it unattached and ask the controller
16596 to deal. Fixes the second part of bug 681.
16597 - Treat some 403 responses from directory servers as INFO rather than
16598 WARN-severity events.
16600 o Portability / building / compiling:
16601 - When building with --enable-gcc-warnings, check for whether Apple's
16602 warning "-Wshorten-64-to-32" is available.
16603 - Support compilation to target iPhone; patch from cjacker huang.
16604 To build for iPhone, pass the --enable-iphone option to configure.
16605 - Port Tor to build and run correctly on Windows CE systems, using
16606 the wcecompat library. Contributed by Valerio Lupi.
16607 - Detect non-ASCII platforms (if any still exist) and refuse to
16608 build there: some of our code assumes that 'A' is 65 and so on.
16609 - Clear up some MIPSPro compiler warnings.
16610 - Make autoconf search for libevent, openssl, and zlib consistently.
16611 - Update deprecated macros in configure.in.
16612 - When warning about missing headers, tell the user to let us
16613 know if the compile succeeds anyway, so we can downgrade the
16615 - Include the current subversion revision as part of the version
16616 string: either fetch it directly if we're in an SVN checkout, do
16617 some magic to guess it if we're in an SVK checkout, or use
16618 the last-detected version if we're building from a .tar.gz.
16619 Use this version consistently in log messages.
16620 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
16621 - Read resolv.conf files correctly on platforms where read() returns
16622 partial results on small file reads.
16623 - Build without verbose warnings even on gcc 4.2 and 4.3.
16624 - On Windows, correctly detect errors when listing the contents of
16625 a directory. Fix from lodger.
16626 - Run 'make test' as part of 'make dist', so we stop releasing so
16627 many development snapshots that fail their unit tests.
16628 - Add support to detect Libevent versions in the 1.4.x series
16630 - Add command-line arguments to unit-test executable so that we can
16631 invoke any chosen test from the command line rather than having
16632 to run the whole test suite at once; and so that we can turn on
16633 logging for the unit tests.
16634 - Do not automatically run configure from autogen.sh. This
16635 non-standard behavior tended to annoy people who have built other
16637 - Fix a macro/CPP interaction that was confusing some compilers:
16638 some GCCs don't like #if/#endif pairs inside macro arguments.
16640 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
16641 Fixes bug 704; fix from Steven Murdoch.
16642 - Correctly detect transparent proxy support on Linux hosts that
16643 require in.h to be included before netfilter_ipv4.h. Patch
16646 o Logging improvements:
16647 - When we haven't had any application requests lately, don't bother
16648 logging that we have expired a bunch of descriptors.
16649 - When attempting to open a logfile fails, tell us why.
16650 - Only log guard node status when guard node status has changed.
16651 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
16652 make "INFO" 75% less verbose.
16653 - When SafeLogging is disabled, log addresses along with all TLS
16655 - Report TLS "zero return" case as a "clean close" and "IO error"
16656 as a "close". Stop calling closes "unexpected closes": existing
16657 Tors don't use SSL_close(), so having a connection close without
16658 the TLS shutdown handshake is hardly unexpected.
16659 - When we receive a consensus from the future, warn about skew.
16660 - Make "not enough dir info yet" warnings describe *why* Tor feels
16661 it doesn't have enough directory info yet.
16662 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
16663 consumers. (We already do this on HUP.)
16664 - Give more descriptive well-formedness errors for out-of-range
16665 hidden service descriptor/protocol versions.
16666 - Stop recommending that every server operator send mail to tor-ops.
16667 Resolves bug 597. Bugfix on 0.1.2.x.
16668 - Improve skew reporting: try to give the user a better log message
16669 about how skewed they are, and how much this matters.
16670 - New --quiet command-line option to suppress the default console log.
16671 Good in combination with --hash-password.
16672 - Don't complain that "your server has not managed to confirm that its
16673 ports are reachable" if we haven't been able to build any circuits
16675 - Detect the reason for failing to mmap a descriptor file we just
16676 wrote, and give a more useful log message. Fixes bug 533.
16677 - Always prepend "Bug: " to any log message about a bug.
16678 - When dumping memory usage, list bytes used in buffer memory
16680 - When running with dmalloc, dump more stats on hup and on exit.
16681 - Put a platform string (e.g. "Linux i686") in the startup log
16682 message, so when people paste just their logs, we know if it's
16683 OpenBSD or Windows or what.
16684 - When logging memory usage, break down memory used in buffers by
16686 - When we are reporting the DirServer line we just parsed, we were
16687 logging the second stanza of the key fingerprint, not the first.
16688 - Even though Windows is equally happy with / and \ as path separators,
16689 try to use \ consistently on Windows and / consistently on Unix: it
16690 makes the log messages nicer.
16691 - On OSX, stop warning the user that kqueue support in libevent is
16692 "experimental", since it seems to have worked fine for ages.
16694 o Contributed scripts and tools:
16695 - Update linux-tor-prio.sh script to allow QoS based on the uid of
16696 the Tor process. Patch from Marco Bonetti with tweaks from Mike
16698 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
16699 Unix users an easy way to script their Tor process (e.g. by
16700 adjusting bandwidth based on the time of the day).
16701 - In the exitlist script, only consider the most recently published
16702 server descriptor for each server. Also, when the user requests
16703 a list of servers that _reject_ connections to a given address,
16704 explicitly exclude the IPs that also have servers that accept
16705 connections to that address. Resolves bug 405.
16706 - Include a new contrib/tor-exit-notice.html file that exit relay
16707 operators can put on their website to help reduce abuse queries.
16709 o Newly deprecated features:
16710 - The status/version/num-versioning and status/version/num-concurring
16711 GETINFO controller options are no longer useful in the v3 directory
16712 protocol: treat them as deprecated, and warn when they're used.
16713 - The RedirectExits config option is now deprecated.
16715 o Removed features:
16716 - Drop the old code to choke directory connections when the
16717 corresponding OR connections got full: thanks to the cell queue
16718 feature, OR conns don't get full any more.
16719 - Remove the old "dns worker" server DNS code: it hasn't been default
16720 since 0.1.2.2-alpha, and all the servers are using the new
16722 - Remove the code to generate the oldest (v1) directory format.
16723 - Remove support for the old bw_accounting file: we've been storing
16724 bandwidth accounting information in the state file since
16725 0.1.2.5-alpha. This may result in bandwidth accounting errors
16726 if you try to upgrade from 0.1.1.x or earlier, or if you try to
16727 downgrade to 0.1.1.x or earlier.
16728 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
16729 it, it had no AES, and it hasn't seen any security patches since
16731 - Stop overloading the circuit_t.onionskin field for both "onionskin
16732 from a CREATE cell that we are waiting for a cpuworker to be
16733 assigned" and "onionskin from an EXTEND cell that we are going to
16734 send to an OR as soon as we are connected". Might help with bug 600.
16735 - Remove the tor_strpartition() function: its logic was confused,
16736 and it was only used for one thing that could be implemented far
16738 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
16739 and TorControl.py, as they use the old v0 controller protocol,
16740 and are obsoleted by TorFlow anyway.
16741 - Drop support for v1 rendezvous descriptors, since we never used
16742 them anyway, and the code has probably rotted by now. Based on
16743 patch from Karsten Loesing.
16744 - Stop allowing address masks that do not correspond to bit prefixes.
16745 We have warned about these for a really long time; now it's time
16746 to reject them. (Patch from croup.)
16747 - Remove an optimization in the AES counter-mode code that assumed
16748 that the counter never exceeded 2^68. When the counter can be set
16749 arbitrarily as an IV (as it is by Karsten's new hidden services
16750 code), this assumption no longer holds.
16751 - Disable the SETROUTERPURPOSE controller command: it is now
16755 Changes in version 0.1.2.19 - 2008-01-17
16756 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
16757 exit policy a little bit more conservative so it's safer to run an
16758 exit relay on a home system, and fixes a variety of smaller issues.
16761 - Exit policies now reject connections that are addressed to a
16762 relay's public (external) IP address too, unless
16763 ExitPolicyRejectPrivate is turned off. We do this because too
16764 many relays are running nearby to services that trust them based
16765 on network address.
16768 - When the clock jumps forward a lot, do not allow the bandwidth
16769 buckets to become negative. Fixes bug 544.
16770 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
16771 on every successful resolve. Reported by Mike Perry.
16772 - Purge old entries from the "rephist" database and the hidden
16773 service descriptor database even when DirPort is zero.
16774 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
16775 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
16776 crashing or mis-answering these requests.
16777 - When we decide to send a 503 response to a request for servers, do
16778 not then also send the server descriptors: this defeats the whole
16779 purpose. Fixes bug 539.
16782 - Changing the ExitPolicyRejectPrivate setting should cause us to
16783 rebuild our server descriptor.
16784 - Fix handling of hex nicknames when answering controller requests for
16785 networkstatus by name, or when deciding whether to warn about
16786 unknown routers in a config option. (Patch from mwenge.)
16787 - Fix a couple of hard-to-trigger autoconf problems that could result
16788 in really weird results on platforms whose sys/types.h files define
16789 nonstandard integer types.
16790 - Don't try to create the datadir when running --verify-config or
16791 --hash-password. Resolves bug 540.
16792 - If we were having problems getting a particular descriptor from the
16793 directory caches, and then we learned about a new descriptor for
16794 that router, we weren't resetting our failure count. Reported
16796 - Although we fixed bug 539 (where servers would send HTTP status 503
16797 responses _and_ send a body too), there are still servers out there
16798 that haven't upgraded. Therefore, make clients parse such bodies
16799 when they receive them.
16800 - Run correctly on systems where rlim_t is larger than unsigned long.
16801 This includes some 64-bit systems.
16802 - Run correctly on platforms (like some versions of OS X 10.5) where
16803 the real limit for number of open files is OPEN_FILES, not rlim_max
16804 from getrlimit(RLIMIT_NOFILES).
16805 - Avoid a spurious free on base64 failure.
16806 - Avoid segfaults on certain complex invocations of
16807 router_get_by_hexdigest().
16808 - Fix rare bug on REDIRECTSTREAM control command when called with no
16809 port set: it could erroneously report an error when none had
16813 Changes in version 0.1.2.18 - 2007-10-28
16814 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
16815 hidden service introduction that were causing huge delays, and a big
16816 bug that was causing some servers to disappear from the network status
16817 lists for a few hours each day.
16819 o Major bugfixes (crashes):
16820 - If a connection is shut down abruptly because of something that
16821 happened inside connection_flushed_some(), do not call
16822 connection_finished_flushing(). Should fix bug 451:
16823 "connection_stop_writing: Assertion conn->write_event failed"
16824 Bugfix on 0.1.2.7-alpha.
16825 - Fix possible segfaults in functions called from
16826 rend_process_relay_cell().
16828 o Major bugfixes (hidden services):
16829 - Hidden services were choosing introduction points uniquely by
16830 hexdigest, but when constructing the hidden service descriptor
16831 they merely wrote the (potentially ambiguous) nickname.
16832 - Clients now use the v2 intro format for hidden service
16833 connections: they specify their chosen rendezvous point by identity
16834 digest rather than by (potentially ambiguous) nickname. These
16835 changes could speed up hidden service connections dramatically.
16837 o Major bugfixes (other):
16838 - Stop publishing a new server descriptor just because we get a
16839 HUP signal. This led (in a roundabout way) to some servers getting
16840 dropped from the networkstatus lists for a few hours each day.
16841 - When looking for a circuit to cannibalize, consider family as well
16842 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
16843 circuit cannibalization).
16844 - When a router wasn't listed in a new networkstatus, we were leaving
16845 the flags for that router alone -- meaning it remained Named,
16846 Running, etc -- even though absence from the networkstatus means
16847 that it shouldn't be considered to exist at all anymore. Now we
16848 clear all the flags for routers that fall out of the networkstatus
16849 consensus. Fixes bug 529.
16852 - Don't try to access (or alter) the state file when running
16853 --list-fingerprint or --verify-config or --hash-password. Resolves
16855 - When generating information telling us how to extend to a given
16856 router, do not try to include the nickname if it is
16857 absent. Resolves bug 467.
16858 - Fix a user-triggerable segfault in expand_filename(). (There isn't
16859 a way to trigger this remotely.)
16860 - When sending a status event to the controller telling it that an
16861 OR address is reachable, set the port correctly. (Previously we
16862 were reporting the dir port.)
16863 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
16864 command. Bugfix on 0.1.2.17.
16865 - When loading bandwidth history, do not believe any information in
16866 the future. Fixes bug 434.
16867 - When loading entry guard information, do not believe any information
16869 - When we have our clock set far in the future and generate an
16870 onion key, then re-set our clock to be correct, we should not stop
16871 the onion key from getting rotated.
16872 - On some platforms, accept() can return a broken address. Detect
16873 this more quietly, and deal accordingly. Fixes bug 483.
16874 - It's not actually an error to find a non-pending entry in the DNS
16875 cache when canceling a pending resolve. Don't log unless stuff
16876 is fishy. Resolves bug 463.
16877 - Don't reset trusted dir server list when we set a configuration
16878 option. Patch from Robert Hogan.
16881 Changes in version 0.1.2.17 - 2007-08-30
16882 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
16883 X bundles. Vidalia 0.0.14 makes authentication required for the
16884 ControlPort in the default configuration, which addresses important
16885 security risks. Everybody who uses Vidalia (or another controller)
16888 In addition, this Tor update fixes major load balancing problems with
16889 path selection, which should speed things up a lot once many people
16892 o Major bugfixes (security):
16893 - We removed support for the old (v0) control protocol. It has been
16894 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
16895 become more of a headache than it's worth.
16897 o Major bugfixes (load balancing):
16898 - When choosing nodes for non-guard positions, weight guards
16899 proportionally less, since they already have enough load. Patch
16901 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
16902 will allow fast Tor servers to get more attention.
16903 - When we're upgrading from an old Tor version, forget our current
16904 guards and pick new ones according to the new weightings. These
16905 three load balancing patches could raise effective network capacity
16906 by a factor of four. Thanks to Mike Perry for measurements.
16908 o Major bugfixes (stream expiration):
16909 - Expire not-yet-successful application streams in all cases if
16910 they've been around longer than SocksTimeout. Right now there are
16911 some cases where the stream will live forever, demanding a new
16912 circuit every 15 seconds. Fixes bug 454; reported by lodger.
16914 o Minor features (controller):
16915 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
16916 is valid before any authentication has been received. It tells
16917 a controller what kind of authentication is expected, and what
16918 protocol is spoken. Implements proposal 119.
16920 o Minor bugfixes (performance):
16921 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
16922 greatly speeding up loading cached-routers from disk on startup.
16923 - Disable sentinel-based debugging for buffer code: we squashed all
16924 the bugs that this was supposed to detect a long time ago, and now
16925 its only effect is to change our buffer sizes from nice powers of
16926 two (which platform mallocs tend to like) to values slightly over
16927 powers of two (which make some platform mallocs sad).
16929 o Minor bugfixes (misc):
16930 - If exit bandwidth ever exceeds one third of total bandwidth, then
16931 use the correct formula to weight exit nodes when choosing paths.
16932 Based on patch from Mike Perry.
16933 - Choose perfectly fairly among routers when choosing by bandwidth and
16934 weighting by fraction of bandwidth provided by exits. Previously, we
16935 would choose with only approximate fairness, and correct ourselves
16936 if we ran off the end of the list.
16937 - If we require CookieAuthentication but we fail to write the
16938 cookie file, we would warn but not exit, and end up in a state
16939 where no controller could authenticate. Now we exit.
16940 - If we require CookieAuthentication, stop generating a new cookie
16941 every time we change any piece of our config.
16942 - Refuse to start with certain directory authority keys, and
16943 encourage people using them to stop.
16944 - Terminate multi-line control events properly. Original patch
16946 - Fix a minor memory leak when we fail to find enough suitable
16947 servers to choose a circuit.
16948 - Stop leaking part of the descriptor when we run into a particularly
16949 unparseable piece of it.
16952 Changes in version 0.1.2.16 - 2007-08-01
16953 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
16954 remote attacker in certain situations to rewrite the user's torrc
16955 configuration file. This can completely compromise anonymity of users
16956 in most configurations, including those running the Vidalia bundles,
16957 TorK, etc. Or worse.
16959 o Major security fixes:
16960 - Close immediately after missing authentication on control port;
16961 do not allow multiple authentication attempts.
16964 Changes in version 0.1.2.15 - 2007-07-17
16965 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
16966 problems, fixes compilation on BSD, and fixes a variety of other
16967 bugs. Everybody should upgrade.
16969 o Major bugfixes (compilation):
16970 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
16972 o Major bugfixes (crashes):
16973 - Try even harder not to dereference the first character after
16974 an mmap(). Reported by lodger.
16975 - Fix a crash bug in directory authorities when we re-number the
16976 routerlist while inserting a new router.
16977 - When the cached-routers file is an even multiple of the page size,
16978 don't run off the end and crash. (Fixes bug 455; based on idea
16980 - Fix eventdns.c behavior on Solaris: It is critical to include
16981 orconfig.h _before_ sys/types.h, so that we can get the expected
16982 definition of _FILE_OFFSET_BITS.
16984 o Major bugfixes (security):
16985 - Fix a possible buffer overrun when using BSD natd support. Bug
16987 - When sending destroy cells from a circuit's origin, don't include
16988 the reason for tearing down the circuit. The spec says we didn't,
16989 and now we actually don't. Reported by lodger.
16990 - Keep streamids from different exits on a circuit separate. This
16991 bug may have allowed other routers on a given circuit to inject
16992 cells into streams. Reported by lodger; fixes bug 446.
16993 - If there's a never-before-connected-to guard node in our list,
16994 never choose any guards past it. This way we don't expand our
16995 guard list unless we need to.
16997 o Minor bugfixes (guard nodes):
16998 - Weight guard selection by bandwidth, so that low-bandwidth nodes
16999 don't get overused as guards.
17001 o Minor bugfixes (directory):
17002 - Correctly count the number of authorities that recommend each
17003 version. Previously, we were under-counting by 1.
17004 - Fix a potential crash bug when we load many server descriptors at
17005 once and some of them make others of them obsolete. Fixes bug 458.
17007 o Minor bugfixes (hidden services):
17008 - Stop tearing down the whole circuit when the user asks for a
17009 connection to a port that the hidden service didn't configure.
17012 o Minor bugfixes (misc):
17013 - On Windows, we were preventing other processes from reading
17014 cached-routers while Tor was running. Reported by janbar.
17015 - Fix a possible (but very unlikely) bug in picking routers by
17016 bandwidth. Add a log message to confirm that it is in fact
17017 unlikely. Patch from lodger.
17018 - Backport a couple of memory leak fixes.
17019 - Backport miscellaneous cosmetic bugfixes.
17022 Changes in version 0.1.2.14 - 2007-05-25
17023 Tor 0.1.2.14 changes the addresses of two directory authorities (this
17024 change especially affects those who serve or use hidden services),
17025 and fixes several other crash- and security-related bugs.
17027 o Directory authority changes:
17028 - Two directory authorities (moria1 and moria2) just moved to new
17029 IP addresses. This change will particularly affect those who serve
17030 or use hidden services.
17032 o Major bugfixes (crashes):
17033 - If a directory server runs out of space in the connection table
17034 as it's processing a begin_dir request, it will free the exit stream
17035 but leave it attached to the circuit, leading to unpredictable
17036 behavior. (Reported by seeess, fixes bug 425.)
17037 - Fix a bug in dirserv_remove_invalid() that would cause authorities
17038 to corrupt memory under some really unlikely scenarios.
17039 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
17040 - Avoid segfaults when reading from mmaped descriptor file. (Reported
17043 o Major bugfixes (security):
17044 - When choosing an entry guard for a circuit, avoid using guards
17045 that are in the same family as the chosen exit -- not just guards
17046 that are exactly the chosen exit. (Reported by lodger.)
17048 o Major bugfixes (resource management):
17049 - If a directory authority is down, skip it when deciding where to get
17050 networkstatus objects or descriptors. Otherwise we keep asking
17051 every 10 seconds forever. Fixes bug 384.
17052 - Count it as a failure if we fetch a valid network-status but we
17053 don't want to keep it. Otherwise we'll keep fetching it and keep
17054 not wanting to keep it. Fixes part of bug 422.
17055 - If all of our dirservers have given us bad or no networkstatuses
17056 lately, then stop hammering them once per minute even when we
17057 think they're failed. Fixes another part of bug 422.
17060 - Actually set the purpose correctly for descriptors inserted with
17061 purpose=controller.
17062 - When we have k non-v2 authorities in our DirServer config,
17063 we ignored the last k authorities in the list when updating our
17065 - Correctly back-off from requesting router descriptors that we are
17066 having a hard time downloading.
17067 - Read resolv.conf files correctly on platforms where read() returns
17068 partial results on small file reads.
17069 - Don't rebuild the entire router store every time we get 32K of
17070 routers: rebuild it when the journal gets very large, or when
17071 the gaps in the store get very large.
17074 - When routers publish SVN revisions in their router descriptors,
17075 authorities now include those versions correctly in networkstatus
17077 - Warn when using a version of libevent before 1.3b to run a server on
17078 OSX or BSD: these versions interact badly with userspace threads.
17081 Changes in version 0.1.2.13 - 2007-04-24
17082 This release features some major anonymity fixes, such as safer path
17083 selection; better client performance; faster bootstrapping, better
17084 address detection, and better DNS support for servers; write limiting as
17085 well as read limiting to make servers easier to run; and a huge pile of
17086 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
17088 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
17089 of the Freenode IRC network, remembering his patience and vision for
17090 free speech on the Internet.
17092 o Major features, client performance:
17093 - Weight directory requests by advertised bandwidth. Now we can
17094 let servers enable write limiting but still allow most clients to
17095 succeed at their directory requests. (We still ignore weights when
17096 choosing a directory authority; I hope this is a feature.)
17097 - Stop overloading exit nodes -- avoid choosing them for entry or
17098 middle hops when the total bandwidth available from non-exit nodes
17099 is much higher than the total bandwidth available from exit nodes.
17100 - Rather than waiting a fixed amount of time between retrying
17101 application connections, we wait only 10 seconds for the first,
17102 10 seconds for the second, and 15 seconds for each retry after
17103 that. Hopefully this will improve the expected user experience.
17104 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
17105 to open a stream fails; now we do in more cases. This should
17106 make clients able to find a good exit faster in some cases, since
17107 unhandleable requests will now get an error rather than timing out.
17109 o Major features, client functionality:
17110 - Implement BEGIN_DIR cells, so we can connect to a directory
17111 server via TLS to do encrypted directory requests rather than
17112 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
17113 config options if you like. For now, this feature only works if
17114 you already have a descriptor for the destination dirserver.
17115 - Add support for transparent application connections: this basically
17116 bundles the functionality of trans-proxy-tor into the Tor
17117 mainline. Now hosts with compliant pf/netfilter implementations
17118 can redirect TCP connections straight to Tor without diverting
17119 through SOCKS. (Based on patch from tup.)
17120 - Add support for using natd; this allows FreeBSDs earlier than
17121 5.1.2 to have ipfw send connections through Tor without using
17122 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
17124 o Major features, servers:
17125 - Setting up a dyndns name for your server is now optional: servers
17126 with no hostname or IP address will learn their IP address by
17127 asking the directory authorities. This code only kicks in when you
17128 would normally have exited with a "no address" error. Nothing's
17129 authenticated, so use with care.
17130 - Directory servers now spool server descriptors, v1 directories,
17131 and v2 networkstatus objects to buffers as needed rather than en
17132 masse. They also mmap the cached-routers files. These steps save
17134 - Stop requiring clients to have well-formed certificates, and stop
17135 checking nicknames in certificates. (Clients have certificates so
17136 that they can look like Tor servers, but in the future we might want
17137 to allow them to look like regular TLS clients instead. Nicknames
17138 in certificates serve no purpose other than making our protocol
17139 easier to recognize on the wire.) Implements proposal 106.
17141 o Improvements on DNS support:
17142 - Add "eventdns" asynchronous dns library originally based on code
17143 from Adam Langley. Now we can discard the old rickety dnsworker
17144 concept, and support a wider variety of DNS functions. Allows
17145 multithreaded builds on NetBSD and OpenBSD again.
17146 - Add server-side support for "reverse" DNS lookups (using PTR
17147 records so clients can determine the canonical hostname for a given
17148 IPv4 address). Only supported by servers using eventdns; servers
17149 now announce in their descriptors if they don't support eventdns.
17150 - Workaround for name servers (like Earthlink's) that hijack failing
17151 DNS requests and replace the no-such-server answer with a "helpful"
17152 redirect to an advertising-driven search portal. Also work around
17153 DNS hijackers who "helpfully" decline to hijack known-invalid
17154 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
17155 lets you turn it off.
17156 - Servers now check for the case when common DNS requests are going to
17157 wildcarded addresses (i.e. all getting the same answer), and change
17158 their exit policy to reject *:* if it's happening.
17159 - When asked to resolve a hostname, don't use non-exit servers unless
17160 requested to do so. This allows servers with broken DNS to be
17161 useful to the network.
17162 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
17163 useless IPv6 DNS resolves.
17164 - Specify and implement client-side SOCKS5 interface for reverse DNS
17165 lookups (see doc/socks-extensions.txt). Also cache them.
17166 - When we change nameservers or IP addresses, reset and re-launch
17167 our tests for DNS hijacking.
17169 o Improvements on reachability testing:
17170 - Servers send out a burst of long-range padding cells once they've
17171 established that they're reachable. Spread them over 4 circuits,
17172 so hopefully a few will be fast. This exercises bandwidth and
17173 bootstraps them into the directory more quickly.
17174 - When we find our DirPort to be reachable, publish a new descriptor
17175 so we'll tell the world (reported by pnx).
17176 - Directory authorities now only decide that routers are reachable
17177 if their identity keys are as expected.
17178 - Do DirPort reachability tests less often, since a single test
17179 chews through many circuits before giving up.
17180 - Avoid some false positives during reachability testing: don't try
17181 to test via a server that's on the same /24 network as us.
17182 - Start publishing one minute or so after we find our ORPort
17183 to be reachable. This will help reduce the number of descriptors
17184 we have for ourselves floating around, since it's quite likely
17185 other things (e.g. DirPort) will change during that minute too.
17186 - Routers no longer try to rebuild long-term connections to directory
17187 authorities, and directory authorities no longer try to rebuild
17188 long-term connections to all servers. We still don't hang up
17189 connections in these two cases though -- we need to look at it
17190 more carefully to avoid flapping, and we likely need to wait til
17191 0.1.1.x is obsolete.
17193 o Improvements on rate limiting:
17194 - Enable write limiting as well as read limiting. Now we sacrifice
17195 capacity if we're pushing out lots of directory traffic, rather
17196 than overrunning the user's intended bandwidth limits.
17197 - Include TLS overhead when counting bandwidth usage; previously, we
17198 would count only the bytes sent over TLS, but not the bytes used
17200 - Servers decline directory requests much more aggressively when
17201 they're low on bandwidth. Otherwise they end up queueing more and
17202 more directory responses, which can't be good for latency.
17203 - But never refuse directory requests from local addresses.
17204 - Be willing to read or write on local connections (e.g. controller
17205 connections) even when the global rate limiting buckets are empty.
17206 - Flush local controller connection buffers periodically as we're
17207 writing to them, so we avoid queueing 4+ megabytes of data before
17209 - Revise and clean up the torrc.sample that we ship with; add
17210 a section for BandwidthRate and BandwidthBurst.
17212 o Major features, NT services:
17213 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
17214 command-line flag so that admins can override the default by saying
17215 "tor --service install --user "SomeUser"". This will not affect
17216 existing installed services. Also, warn the user that the service
17217 will look for its configuration file in the service user's
17218 %appdata% directory. (We can't do the "hardwire the user's appdata
17219 directory" trick any more, since we may not have read access to that
17221 - Support running the Tor service with a torrc not in the same
17222 directory as tor.exe and default to using the torrc located in
17223 the %appdata%\Tor\ of the user who installed the service. Patch
17225 - Add an --ignore-missing-torrc command-line option so that we can
17226 get the "use sensible defaults if the configuration file doesn't
17227 exist" behavior even when specifying a torrc location on the
17229 - When stopping an NT service, wait up to 10 sec for it to actually
17230 stop. (Patch from Matt Edman; resolves bug 295.)
17232 o Directory authority improvements:
17233 - Stop letting hibernating or obsolete servers affect uptime and
17235 - Stop listing hibernating servers in the v1 directory.
17236 - Authorities no longer recommend exits as guards if this would shift
17237 too much load to the exit nodes.
17238 - Authorities now specify server versions in networkstatus. This adds
17239 about 2% to the size of compressed networkstatus docs, and allows
17240 clients to tell which servers support BEGIN_DIR and which don't.
17241 The implementation is forward-compatible with a proposed future
17242 protocol version scheme not tied to Tor versions.
17243 - DirServer configuration lines now have an orport= option so
17244 clients can open encrypted tunnels to the authorities without
17245 having downloaded their descriptors yet. Enabled for moria1,
17246 moria2, tor26, and lefkada now in the default configuration.
17247 - Add a BadDirectory flag to network status docs so that authorities
17248 can (eventually) tell clients about caches they believe to be
17249 broken. Not used yet.
17250 - Allow authorities to list nodes as bad exits in their
17251 approved-routers file by fingerprint or by address. If most
17252 authorities set a BadExit flag for a server, clients don't think
17253 of it as a general-purpose exit. Clients only consider authorities
17254 that advertise themselves as listing bad exits.
17255 - Patch from Steve Hildrey: Generate network status correctly on
17256 non-versioning dirservers.
17257 - Have directory authorities allow larger amounts of drift in uptime
17258 without replacing the server descriptor: previously, a server that
17259 restarted every 30 minutes could have 48 "interesting" descriptors
17261 - Reserve the nickname "Unnamed" for routers that can't pick
17262 a hostname: any router can call itself Unnamed; directory
17263 authorities will never allocate Unnamed to any particular router;
17264 clients won't believe that any router is the canonical Unnamed.
17266 o Directory mirrors and clients:
17267 - Discard any v1 directory info that's over 1 month old (for
17268 directories) or over 1 week old (for running-routers lists).
17269 - Clients track responses with status 503 from dirservers. After a
17270 dirserver has given us a 503, we try not to use it until an hour has
17271 gone by, or until we have no dirservers that haven't given us a 503.
17272 - When we get a 503 from a directory, and we're not a server, we no
17273 longer count the failure against the total number of failures
17274 allowed for the object we're trying to download.
17275 - Prepare for servers to publish descriptors less often: never
17276 discard a descriptor simply for being too old until either it is
17277 recommended by no authorities, or until we get a better one for
17278 the same router. Make caches consider retaining old recommended
17279 routers for even longer.
17280 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
17281 headers for content, so that we can work better in the presence of
17282 caching HTTP proxies.
17283 - Stop fetching descriptors if you're not a dir mirror and you
17284 haven't tried to establish any circuits lately. (This currently
17285 causes some dangerous behavior, because when you start up again
17286 you'll use your ancient server descriptors.)
17288 o Major fixes, crashes:
17289 - Stop crashing when the controller asks us to resetconf more than
17290 one config option at once. (Vidalia 0.0.11 does this.)
17291 - Fix a longstanding obscure crash bug that could occur when we run
17292 out of DNS worker processes, if we're not using eventdns. (Resolves
17294 - Fix an assert that could trigger if a controller quickly set then
17295 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
17296 - Avoid crash when telling controller about stream-status and a
17297 stream is detached.
17298 - Avoid sending junk to controllers or segfaulting when a controller
17299 uses EVENT_NEW_DESC with verbose nicknames.
17300 - Stop triggering asserts if the controller tries to extend hidden
17301 service circuits (reported by mwenge).
17302 - If we start a server with ClientOnly 1, then set ClientOnly to 0
17303 and hup, stop triggering an assert based on an empty onion_key.
17304 - Mask out all signals in sub-threads; only the libevent signal
17305 handler should be processing them. This should prevent some crashes
17306 on some machines using pthreads. (Patch from coderman.)
17307 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
17309 o Major fixes, anonymity/security:
17310 - Automatically avoid picking more than one node from the same
17311 /16 network when constructing a circuit. Add an
17312 "EnforceDistinctSubnets" option to let people disable it if they
17313 want to operate private test networks on a single subnet.
17314 - When generating bandwidth history, round down to the nearest
17315 1k. When storing accounting data, round up to the nearest 1k.
17316 - When we're running as a server, remember when we last rotated onion
17317 keys, so that we will rotate keys once they're a week old even if
17318 we never stay up for a week ourselves.
17319 - If a client asked for a server by name, and there's a named server
17320 in our network-status but we don't have its descriptor yet, we
17321 could return an unnamed server instead.
17322 - Reject (most) attempts to use Tor circuits with length one. (If
17323 many people start using Tor as a one-hop proxy, exit nodes become
17324 a more attractive target for compromise.)
17325 - Just because your DirPort is open doesn't mean people should be
17326 able to remotely teach you about hidden service descriptors. Now
17327 only accept rendezvous posts if you've got HSAuthoritativeDir set.
17328 - Fix a potential race condition in the rpm installer. Found by
17330 - Do not log IPs with TLS failures for incoming TLS
17331 connections. (Fixes bug 382.)
17333 o Major fixes, other:
17334 - If our system clock jumps back in time, don't publish a negative
17335 uptime in the descriptor.
17336 - When we start during an accounting interval before it's time to wake
17337 up, remember to wake up at the correct time. (May fix bug 342.)
17338 - Previously, we would cache up to 16 old networkstatus documents
17339 indefinitely, if they came from nontrusted authorities. Now we
17340 discard them if they are more than 10 days old.
17341 - When we have a state file we cannot parse, tell the user and
17342 move it aside. Now we avoid situations where the user starts
17343 Tor in 1904, Tor writes a state file with that timestamp in it,
17344 the user fixes her clock, and Tor refuses to start.
17345 - Publish a new descriptor after we hup/reload. This is important
17346 if our config has changed such that we'll want to start advertising
17347 our DirPort now, etc.
17348 - If we are using an exit enclave and we can't connect, e.g. because
17349 its webserver is misconfigured to not listen on localhost, then
17350 back off and try connecting from somewhere else before we fail.
17352 o New config options or behaviors:
17353 - When EntryNodes are configured, rebuild the guard list to contain,
17354 in order: the EntryNodes that were guards before; the rest of the
17355 EntryNodes; the nodes that were guards before.
17356 - Do not warn when individual nodes in the configuration's EntryNodes,
17357 ExitNodes, etc are down: warn only when all possible nodes
17358 are down. (Fixes bug 348.)
17359 - Put a lower-bound on MaxAdvertisedBandwidth.
17360 - Start using the state file to store bandwidth accounting data:
17361 the bw_accounting file is now obsolete. We'll keep generating it
17362 for a while for people who are still using 0.1.2.4-alpha.
17363 - Try to batch changes to the state file so that we do as few
17364 disk writes as possible while still storing important things in
17366 - The state file and the bw_accounting file get saved less often when
17367 the AvoidDiskWrites config option is set.
17368 - Make PIDFile work on Windows.
17369 - Add internal descriptions for a bunch of configuration options:
17370 accessible via controller interface and in comments in saved
17372 - Reject *:563 (NNTPS) in the default exit policy. We already reject
17373 NNTP by default, so this seems like a sensible addition.
17374 - Clients now reject hostnames with invalid characters. This should
17375 avoid some inadvertent info leaks. Add an option
17376 AllowNonRFC953Hostnames to disable this behavior, in case somebody
17377 is running a private network with hosts called @, !, and #.
17378 - Check for addresses with invalid characters at the exit as well,
17379 and warn less verbosely when they fail. You can override this by
17380 setting ServerDNSAllowNonRFC953Addresses to 1.
17381 - Remove some options that have been deprecated since at least
17382 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
17383 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
17384 to set log options. Mark PathlenCoinWeight as obsolete.
17385 - Stop accepting certain malformed ports in configured exit policies.
17386 - When the user uses bad syntax in the Log config line, stop
17387 suggesting other bad syntax as a replacement.
17388 - Add new config option "ResolvConf" to let the server operator
17389 choose an alternate resolve.conf file when using eventdns.
17390 - If one of our entry guards is on the ExcludeNodes list, or the
17391 directory authorities don't think it's a good guard, treat it as
17392 if it were unlisted: stop using it as a guard, and throw it off
17393 the guards list if it stays that way for a long time.
17394 - Allow directory authorities to be marked separately as authorities
17395 for the v1 directory protocol, the v2 directory protocol, and
17396 as hidden service directories, to make it easier to retire old
17397 authorities. V1 authorities should set "HSAuthoritativeDir 1"
17398 to continue being hidden service authorities too.
17399 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
17400 - Make TrackExitHosts case-insensitive, and fix the behavior of
17401 ".suffix" TrackExitHosts items to avoid matching in the middle of
17403 - New DirPort behavior: if you have your dirport set, you download
17404 descriptors aggressively like a directory mirror, whether or not
17405 your ORPort is set.
17408 - Create a new file ReleaseNotes which was the old ChangeLog. The
17409 new ChangeLog file now includes the notes for all development
17411 - Add a new address-spec.txt document to describe our special-case
17412 addresses: .exit, .onion, and .noconnnect.
17413 - Fork the v1 directory protocol into its own spec document,
17414 and mark dir-spec.txt as the currently correct (v2) spec.
17416 o Packaging, porting, and contrib
17417 - "tor --verify-config" now exits with -1(255) or 0 depending on
17418 whether the config options are bad or good.
17419 - The Debian package now uses --verify-config when (re)starting,
17420 to distinguish configuration errors from other errors.
17421 - Adapt a patch from goodell to let the contrib/exitlist script
17422 take arguments rather than require direct editing.
17423 - Prevent the contrib/exitlist script from printing the same
17424 result more than once.
17425 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
17426 - In the hidden service example in torrc.sample, stop recommending
17427 esoteric and discouraged hidden service options.
17428 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
17429 values before failing, and always enables eventdns.
17430 - Try to detect Windows correctly when cross-compiling.
17431 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
17432 Try to fix this in configure.in by checking for most functions
17433 before we check for libevent.
17434 - Update RPMs to require libevent 1.2.
17435 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
17436 or later. Log when we are doing this, so we can diagnose it when
17437 it fails. (Also, recommend libevent 1.1b for kqueue and
17438 win32 methods; deprecate libevent 1.0b harder; make libevent
17439 recommendation system saner.)
17440 - Build with recent (1.3+) libevents on platforms that do not
17441 define the nonstandard types "u_int8_t" and friends.
17442 - Remove architecture from OS X builds. The official builds are
17443 now universal binaries.
17444 - Run correctly on OS X platforms with case-sensitive filesystems.
17445 - Correctly set maximum connection limit on Cygwin. (This time
17447 - Start compiling on MinGW on Windows (patches from Mike Chiussi
17449 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
17450 - Finally fix the openssl warnings from newer gccs that believe that
17451 ignoring a return value is okay, but casting a return value and
17452 then ignoring it is a sign of madness.
17453 - On architectures where sizeof(int)>4, still clamp declarable
17454 bandwidth to INT32_MAX.
17456 o Minor features, controller:
17457 - Warn the user when an application uses the obsolete binary v0
17458 control protocol. We're planning to remove support for it during
17459 the next development series, so it's good to give people some
17461 - Add STREAM_BW events to report per-entry-stream bandwidth
17462 use. (Patch from Robert Hogan.)
17463 - Rate-limit SIGNEWNYM signals in response to controllers that
17464 impolitely generate them for every single stream. (Patch from
17465 mwenge; closes bug 394.)
17466 - Add a REMAP status to stream events to note that a stream's
17467 address has changed because of a cached address or a MapAddress
17469 - Make REMAP stream events have a SOURCE (cache or exit), and
17470 make them generated in every case where we get a successful
17471 connected or resolved cell.
17472 - Track reasons for OR connection failure; make these reasons
17473 available via the controller interface. (Patch from Mike Perry.)
17474 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
17475 can learn when clients are sending malformed hostnames to Tor.
17476 - Specify and implement some of the controller status events.
17477 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
17478 - Reimplement GETINFO so that info/names stays in sync with the
17480 - Implement "GETINFO fingerprint".
17481 - Implement "SETEVENTS GUARD" so controllers can get updates on
17482 entry guard status as it changes.
17483 - Make all connections to addresses of the form ".noconnect"
17484 immediately get closed. This lets application/controller combos
17485 successfully test whether they're talking to the same Tor by
17486 watching for STREAM events.
17487 - Add a REASON field to CIRC events; for backward compatibility, this
17488 field is sent only to controllers that have enabled the extended
17489 event format. Also, add additional reason codes to explain why
17490 a given circuit has been destroyed or truncated. (Patches from
17492 - Add a REMOTE_REASON field to extended CIRC events to tell the
17493 controller why a remote OR told us to close a circuit.
17494 - Stream events also now have REASON and REMOTE_REASON fields,
17495 working much like those for circuit events.
17496 - There's now a GETINFO ns/... field so that controllers can ask Tor
17497 about the current status of a router.
17498 - A new event type "NS" to inform a controller when our opinion of
17499 a router's status has changed.
17500 - Add a GETINFO events/names and GETINFO features/names so controllers
17501 can tell which events and features are supported.
17502 - A new CLEARDNSCACHE signal to allow controllers to clear the
17503 client-side DNS cache without expiring circuits.
17504 - Fix CIRC controller events so that controllers can learn the
17505 identity digests of non-Named servers used in circuit paths.
17506 - Let controllers ask for more useful identifiers for servers. Instead
17507 of learning identity digests for un-Named servers and nicknames
17508 for Named servers, the new identifiers include digest, nickname,
17509 and indication of Named status. Off by default; see control-spec.txt
17510 for more information.
17511 - Add a "getinfo address" controller command so it can display Tor's
17512 best guess to the user.
17513 - New controller event to alert the controller when our server
17514 descriptor has changed.
17515 - Give more meaningful errors on controller authentication failure.
17516 - Export the default exit policy via the control port, so controllers
17517 don't need to guess what it is / will be later.
17519 o Minor bugfixes, controller:
17520 - When creating a circuit via the controller, send a 'launched'
17521 event when we're done, so we follow the spec better.
17522 - Correct the control spec to match how the code actually responds
17523 to 'getinfo addr-mappings/*'. Reported by daejees.
17524 - The control spec described a GUARDS event, but the code
17525 implemented a GUARD event. Standardize on GUARD, but let people
17526 ask for GUARDS too. Reported by daejees.
17527 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
17528 clear the corresponding on_circuit variable, and remember later
17529 that we don't need to send a redundant CLOSED event. (Resolves part
17531 - Report events where a resolve succeeded or where we got a socks
17532 protocol error correctly, rather than calling both of them
17534 - Change reported stream target addresses to IP consistently when
17535 we finally get the IP from an exit node.
17536 - Send log messages to the controller even if they happen to be very
17538 - Flush ERR-level controller status events just like we currently
17539 flush ERR-level log events, so that a Tor shutdown doesn't prevent
17540 the controller from learning about current events.
17541 - Report the circuit number correctly in STREAM CLOSED events. Bug
17542 reported by Mike Perry.
17543 - Do not report bizarre values for results of accounting GETINFOs
17544 when the last second's write or read exceeds the allotted bandwidth.
17545 - Report "unrecognized key" rather than an empty string when the
17546 controller tries to fetch a networkstatus that doesn't exist.
17547 - When the controller does a "GETINFO network-status", tell it
17548 about even those routers whose descriptors are very old, and use
17549 long nicknames where appropriate.
17550 - Fix handling of verbose nicknames with ORCONN controller events:
17551 make them show up exactly when requested, rather than exactly when
17553 - Controller signals now work on non-Unix platforms that don't define
17554 SIGUSR1 and SIGUSR2 the way we expect.
17555 - Respond to SIGNAL command before we execute the signal, in case
17556 the signal shuts us down. Suggested by Karsten Loesing.
17557 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
17559 o Minor features, code performance:
17560 - Major performance improvement on inserting descriptors: change
17561 algorithm from O(n^2) to O(n).
17562 - Do not rotate onion key immediately after setting it for the first
17564 - Call router_have_min_dir_info half as often. (This is showing up in
17565 some profiles, but not others.)
17566 - When using GCC, make log_debug never get called at all, and its
17567 arguments never get evaluated, when no debug logs are configured.
17568 (This is showing up in some profiles, but not others.)
17569 - Statistics dumped by -USR2 now include a breakdown of public key
17570 operations, for profiling.
17571 - Make the common memory allocation path faster on machines where
17572 malloc(0) returns a pointer.
17573 - Split circuit_t into origin_circuit_t and or_circuit_t, and
17574 split connection_t into edge, or, dir, control, and base structs.
17575 These will save quite a bit of memory on busy servers, and they'll
17576 also help us track down bugs in the code and bugs in the spec.
17577 - Use OpenSSL's AES implementation on platforms where it's faster.
17578 This could save us as much as 10% CPU usage.
17580 o Minor features, descriptors and descriptor handling:
17581 - Avoid duplicate entries on MyFamily line in server descriptor.
17582 - When Tor receives a router descriptor that it asked for, but
17583 no longer wants (because it has received fresh networkstatuses
17584 in the meantime), do not warn the user. Cache the descriptor if
17585 we're a cache; drop it if we aren't.
17586 - Servers no longer ever list themselves in their "family" line,
17587 even if configured to do so. This makes it easier to configure
17588 family lists conveniently.
17590 o Minor fixes, confusing/misleading log messages:
17591 - Display correct results when reporting which versions are
17592 recommended, and how recommended they are. (Resolves bug 383.)
17593 - Inform the server operator when we decide not to advertise a
17594 DirPort due to AccountingMax enabled or a low BandwidthRate.
17595 - Only include function names in log messages for info/debug messages.
17596 For notice/warn/err, the content of the message should be clear on
17597 its own, and printing the function name only confuses users.
17598 - Remove even more protocol-related warnings from Tor server logs,
17599 such as bad TLS handshakes and malformed begin cells.
17600 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
17601 when the IP address is mapped through MapAddress to a hostname.
17602 - Fix misleading log messages: an entry guard that is "unlisted",
17603 as well as not known to be "down" (because we've never heard
17604 of it), is not therefore "up".
17606 o Minor fixes, old/obsolete behavior:
17607 - Start assuming we can use a create_fast cell if we don't know
17608 what version a router is running.
17609 - We no longer look for identity and onion keys in "identity.key" and
17610 "onion.key" -- these were replaced by secret_id_key and
17611 secret_onion_key in 0.0.8pre1.
17612 - We no longer require unrecognized directory entries to be
17614 - Drop compatibility with obsolete Tors that permit create cells
17615 to have the wrong circ_id_type.
17616 - Remove code to special-case "-cvs" ending, since it has not
17617 actually mattered since 0.0.9.
17618 - Don't re-write the fingerprint file every restart, unless it has
17621 o Minor fixes, misc client-side behavior:
17622 - Always remove expired routers and networkstatus docs before checking
17623 whether we have enough information to build circuits. (Fixes
17625 - When computing clock skew from directory HTTP headers, consider what
17626 time it was when we finished asking for the directory, not what
17628 - Make our socks5 handling more robust to broken socks clients:
17629 throw out everything waiting on the buffer in between socks
17630 handshake phases, since they can't possibly (so the theory
17631 goes) have predicted what we plan to respond to them.
17632 - Expire socks connections if they spend too long waiting for the
17633 handshake to finish. Previously we would let them sit around for
17634 days, if the connecting application didn't close them either.
17635 - And if the socks handshake hasn't started, don't send a
17636 "DNS resolve socks failed" handshake reply; just close it.
17637 - If the user asks to use invalid exit nodes, be willing to use
17639 - Track unreachable entry guards correctly: don't conflate
17640 'unreachable by us right now' with 'listed as down by the directory
17641 authorities'. With the old code, if a guard was unreachable by us
17642 but listed as running, it would clog our guard list forever.
17643 - Behave correctly in case we ever have a network with more than
17644 2GB/s total advertised capacity.
17645 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
17646 - Fix a memory leak when we ask for "all" networkstatuses and we
17647 get one we don't recognize.
17650 Changes in version 0.1.1.26 - 2006-12-14
17651 o Security bugfixes:
17652 - Stop sending the HttpProxyAuthenticator string to directory
17653 servers when directory connections are tunnelled through Tor.
17654 - Clients no longer store bandwidth history in the state file.
17655 - Do not log introduction points for hidden services if SafeLogging
17659 - Fix an assert failure when a directory authority sets
17660 AuthDirRejectUnlisted and then receives a descriptor from an
17661 unlisted router (reported by seeess).
17664 Changes in version 0.1.1.25 - 2006-11-04
17666 - When a client asks us to resolve (rather than connect to)
17667 an address, and we have a cached answer, give them the cached
17668 answer. Previously, we would give them no answer at all.
17669 - We were building exactly the wrong circuits when we predict
17670 hidden service requirements, meaning Tor would have to build all
17671 its circuits on demand.
17672 - If none of our live entry guards have a high uptime, but we
17673 require a guard with a high uptime, try adding a new guard before
17674 we give up on the requirement. This patch should make long-lived
17675 connections more stable on average.
17676 - When testing reachability of our DirPort, don't launch new
17677 tests when there's already one in progress -- unreachable
17678 servers were stacking up dozens of testing streams.
17680 o Security bugfixes:
17681 - When the user sends a NEWNYM signal, clear the client-side DNS
17682 cache too. Otherwise we continue to act on previous information.
17685 - Avoid a memory corruption bug when creating a hash table for
17687 - Avoid possibility of controller-triggered crash when misusing
17688 certain commands from a v0 controller on platforms that do not
17689 handle printf("%s",NULL) gracefully.
17690 - Avoid infinite loop on unexpected controller input.
17691 - Don't log spurious warnings when we see a circuit close reason we
17692 don't recognize; it's probably just from a newer version of Tor.
17693 - Add Vidalia to the OS X uninstaller script, so when we uninstall
17694 Tor/Privoxy we also uninstall Vidalia.
17697 Changes in version 0.1.1.24 - 2006-09-29
17699 - Allow really slow clients to not hang up five minutes into their
17700 directory downloads (suggested by Adam J. Richter).
17701 - Fix major performance regression from 0.1.0.x: instead of checking
17702 whether we have enough directory information every time we want to
17703 do something, only check when the directory information has changed.
17704 This should improve client CPU usage by 25-50%.
17705 - Don't crash if, after a server has been running for a while,
17706 it can't resolve its hostname.
17707 - When a client asks us to resolve (not connect to) an address,
17708 and we have a cached answer, give them the cached answer.
17709 Previously, we would give them no answer at all.
17712 - Allow Tor to start when RunAsDaemon is set but no logs are set.
17713 - Don't crash when the controller receives a third argument to an
17714 "extendcircuit" request.
17715 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
17716 response; fix error code when "getinfo dir/status/" fails.
17717 - Fix configure.in to not produce broken configure files with
17718 more recent versions of autoconf. Thanks to Clint for his auto*
17720 - Fix security bug on NetBSD that could allow someone to force
17721 uninitialized RAM to be sent to a server's DNS resolver. This
17722 only affects NetBSD and other platforms that do not bounds-check
17724 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
17725 methods: these are known to be buggy.
17726 - If we're a directory mirror and we ask for "all" network status
17727 documents, we would discard status documents from authorities
17728 we don't recognize.
17731 Changes in version 0.1.1.23 - 2006-07-30
17733 - Fast Tor servers, especially exit nodes, were triggering asserts
17734 due to a bug in handling the list of pending DNS resolves. Some
17735 bugs still remain here; we're hunting them.
17736 - Entry guards could crash clients by sending unexpected input.
17737 - More fixes on reachability testing: if you find yourself reachable,
17738 then don't ever make any client requests (so you stop predicting
17739 circuits), then hup or have your clock jump, then later your IP
17740 changes, you won't think circuits are working, so you won't try to
17741 test reachability, so you won't publish.
17744 - Avoid a crash if the controller does a resetconf firewallports
17745 and then a setconf fascistfirewall=1.
17746 - Avoid an integer underflow when the dir authority decides whether
17747 a router is stable: we might wrongly label it stable, and compute
17748 a slightly wrong median stability, when a descriptor is published
17750 - Fix a place where we might trigger an assert if we can't build our
17751 own server descriptor yet.
17754 Changes in version 0.1.1.22 - 2006-07-05
17756 - Fix a big bug that was causing servers to not find themselves
17757 reachable if they changed IP addresses. Since only 0.1.1.22+
17758 servers can do reachability testing correctly, now we automatically
17759 make sure to test via one of these.
17760 - Fix to allow clients and mirrors to learn directory info from
17761 descriptor downloads that get cut off partway through.
17762 - Directory authorities had a bug in deciding if a newly published
17763 descriptor was novel enough to make everybody want a copy -- a few
17764 servers seem to be publishing new descriptors many times a minute.
17766 - Fix a rare bug that was causing some servers to complain about
17767 "closing wedged cpuworkers" and skip some circuit create requests.
17768 - Make the Exit flag in directory status documents actually work.
17771 Changes in version 0.1.1.21 - 2006-06-10
17772 o Crash and assert fixes from 0.1.1.20:
17773 - Fix a rare crash on Tor servers that have enabled hibernation.
17774 - Fix a seg fault on startup for Tor networks that use only one
17775 directory authority.
17776 - Fix an assert from a race condition that occurs on Tor servers
17777 while exiting, where various threads are trying to log that they're
17778 exiting, and delete the logs, at the same time.
17779 - Make our unit tests pass again on certain obscure platforms.
17782 - Add support for building SUSE RPM packages.
17783 - Speed up initial bootstrapping for clients: if we are making our
17784 first ever connection to any entry guard, then don't mark it down
17786 - When only one Tor server in the network is labelled as a guard,
17787 and we've already picked him, we would cycle endlessly picking him
17788 again, being unhappy about it, etc. Now we specifically exclude
17789 current guards when picking a new guard.
17790 - Servers send create cells more reliably after the TLS connection
17791 is established: we were sometimes forgetting to send half of them
17792 when we had more than one pending.
17793 - If we get a create cell that asks us to extend somewhere, but the
17794 Tor server there doesn't match the expected digest, we now send
17795 a destroy cell back, rather than silently doing nothing.
17796 - Make options->RedirectExit work again.
17797 - Make cookie authentication for the controller work again.
17798 - Stop being picky about unusual characters in the arguments to
17799 mapaddress. It's none of our business.
17800 - Add a new config option "TestVia" that lets you specify preferred
17801 middle hops to use for test circuits. Perhaps this will let me
17802 debug the reachability problems better.
17804 o Log / documentation fixes:
17805 - If we're a server and some peer has a broken TLS certificate, don't
17806 log about it unless ProtocolWarnings is set, i.e., we want to hear
17807 about protocol violations by others.
17808 - Fix spelling of VirtualAddrNetwork in man page.
17809 - Add a better explanation at the top of the autogenerated torrc file
17810 about what happened to our old torrc.
17813 Changes in version 0.1.1.20 - 2006-05-23
17814 o Crash and assert fixes from 0.1.0.17:
17815 - Fix assert bug in close_logs() on exit: when we close and delete
17816 logs, remove them all from the global "logfiles" list.
17817 - Fix an assert error when we're out of space in the connection_list
17818 and we try to post a hidden service descriptor (reported by Peter
17820 - Fix a rare assert error when we've tried all intro points for
17821 a hidden service and we try fetching the service descriptor again:
17822 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
17823 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
17824 out and refuse the setconf if it would fail.
17825 - If you specify a relative torrc path and you set RunAsDaemon in
17826 your torrc, then it chdir()'s to the new directory. If you then
17827 HUP, it tries to load the new torrc location, fails, and exits.
17828 The fix: no longer allow a relative path to torrc when using -f.
17829 - Check for integer overflows in more places, when adding elements
17830 to smartlists. This could possibly prevent a buffer overflow
17831 on malicious huge inputs.
17833 o Security fixes, major:
17834 - When we're printing strings from the network, don't try to print
17835 non-printable characters. Now we're safer against shell escape
17836 sequence exploits, and also against attacks to fool users into
17837 misreading their logs.
17838 - Implement entry guards: automatically choose a handful of entry
17839 nodes and stick with them for all circuits. Only pick new guards
17840 when the ones you have are unsuitable, and if the old guards
17841 become suitable again, switch back. This will increase security
17842 dramatically against certain end-point attacks. The EntryNodes
17843 config option now provides some hints about which entry guards you
17844 want to use most; and StrictEntryNodes means to only use those.
17845 Fixes CVE-2006-0414.
17846 - Implement exit enclaves: if we know an IP address for the
17847 destination, and there's a running Tor server at that address
17848 which allows exit to the destination, then extend the circuit to
17849 that exit first. This provides end-to-end encryption and end-to-end
17850 authentication. Also, if the user wants a .exit address or enclave,
17851 use 4 hops rather than 3, and cannibalize a general circ for it
17853 - Obey our firewall options more faithfully:
17854 . If we can't get to a dirserver directly, try going via Tor.
17855 . Don't ever try to connect (as a client) to a place our
17856 firewall options forbid.
17857 . If we specify a proxy and also firewall options, obey the
17858 firewall options even when we're using the proxy: some proxies
17859 can only proxy to certain destinations.
17860 - Make clients regenerate their keys when their IP address changes.
17861 - For the OS X package's modified privoxy config file, comment
17862 out the "logfile" line so we don't log everything passed
17864 - Our TLS handshakes were generating a single public/private
17865 keypair for the TLS context, rather than making a new one for
17866 each new connection. Oops. (But we were still rotating them
17867 periodically, so it's not so bad.)
17868 - When we were cannibalizing a circuit with a particular exit
17869 node in mind, we weren't checking to see if that exit node was
17870 already present earlier in the circuit. Now we are.
17871 - Require server descriptors to list IPv4 addresses -- hostnames
17872 are no longer allowed. This also fixes potential vulnerabilities
17873 to servers providing hostnames as their address and then
17874 preferentially resolving them so they can partition users.
17875 - Our logic to decide if the OR we connected to was the right guy
17876 was brittle and maybe open to a mitm for invalid routers.
17878 o Security fixes, minor:
17879 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
17880 Ian Goldberg can prove things about our handshake protocol more
17882 - Make directory authorities generate a separate "guard" flag to
17883 mean "would make a good entry guard". Clients now honor the
17884 is_guard flag rather than looking at is_fast or is_stable.
17885 - Try to list MyFamily elements by key, not by nickname, and warn
17886 if we've not heard of a server.
17887 - Start using RAND_bytes rather than RAND_pseudo_bytes from
17888 OpenSSL. Also, reseed our entropy every hour, not just at
17889 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
17890 - Refuse server descriptors where the fingerprint line doesn't match
17891 the included identity key. Tor doesn't care, but other apps (and
17892 humans) might actually be trusting the fingerprint line.
17893 - We used to kill the circuit when we receive a relay command we
17894 don't recognize. Now we just drop that cell.
17895 - Fix a bug found by Lasse Overlier: when we were making internal
17896 circuits (intended to be cannibalized later for rendezvous and
17897 introduction circuits), we were picking them so that they had
17898 useful exit nodes. There was no need for this, and it actually
17899 aids some statistical attacks.
17900 - Start treating internal circuits and exit circuits separately.
17901 It's important to keep them separate because internal circuits
17902 have their last hops picked like middle hops, rather than like
17903 exit hops. So exiting on them will break the user's expectations.
17904 - Fix a possible way to DoS dirservers.
17905 - When the client asked for a rendezvous port that the hidden
17906 service didn't want to provide, we were sending an IP address
17907 back along with the end cell. Fortunately, it was zero. But stop
17910 o Packaging improvements:
17911 - Implement --with-libevent-dir option to ./configure. Improve
17912 search techniques to find libevent, and use those for openssl too.
17913 - Fix a couple of bugs in OpenSSL detection. Deal better when
17914 there are multiple SSLs installed with different versions.
17915 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
17916 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
17918 - Make unit tests (and other invocations that aren't the real Tor)
17919 run without launching listeners, creating subdirectories, and so on.
17920 - The OS X installer was adding a symlink for tor_resolve but
17921 the binary was called tor-resolve (reported by Thomas Hardly).
17922 - Now we can target arch and OS in rpm builds (contributed by
17923 Phobos). Also make the resulting dist-rpm filename match the
17925 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
17926 if you log to syslog and want something other than LOG_DAEMON.
17927 - Fix the torify (tsocks) config file to not use Tor for localhost
17929 - Start shipping socks-extensions.txt, tor-doc-unix.html,
17930 tor-doc-server.html, and stylesheet.css in the tarball.
17931 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
17932 They are useless now.
17933 - Add Peter Palfrader's contributed check-tor script. It lets you
17934 easily check whether a given server (referenced by nickname)
17935 is reachable by you.
17936 - Add BSD-style contributed startup script "rc.subr" from Peter
17939 o Directory improvements -- new directory protocol:
17940 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
17941 - Authorities and caches publish individual descriptors (by
17942 digest, by fingerprint, by "all", and by "tell me yours").
17943 - Clients don't download or use the old directory anymore. Now they
17944 download network-statuses from the directory authorities, and
17945 fetch individual server descriptors as needed from mirrors.
17946 - Clients don't download descriptors of non-running servers.
17947 - Download descriptors by digest, not by fingerprint. Caches try to
17948 download all listed digests from authorities; clients try to
17949 download "best" digests from caches. This avoids partitioning
17950 and isolating attacks better.
17951 - Only upload a new server descriptor when options change, 18
17952 hours have passed, uptime is reset, or bandwidth changes a lot.
17953 - Directory authorities silently throw away new descriptors that
17954 haven't changed much if the timestamps are similar. We do this to
17955 tolerate older Tor servers that upload a new descriptor every 15
17956 minutes. (It seemed like a good idea at the time.)
17957 - Clients choose directory servers from the network status lists,
17958 not from their internal list of router descriptors. Now they can
17959 go to caches directly rather than needing to go to authorities
17960 to bootstrap the first set of descriptors.
17961 - When picking a random directory, prefer non-authorities if any
17963 - Add a new flag to network-status indicating whether the server
17964 can answer v2 directory requests too.
17965 - Directory mirrors now cache up to 16 unrecognized network-status
17966 docs, so new directory authorities will be cached too.
17967 - Stop parsing, storing, or using running-routers output (but
17968 mirrors still cache and serve it).
17969 - Clients consider a threshold of "versioning" directory authorities
17970 before deciding whether to warn the user that he's obsolete.
17971 - Authorities publish separate sorted lists of recommended versions
17972 for clients and for servers.
17973 - Change DirServers config line to note which dirs are v1 authorities.
17974 - Put nicknames on the DirServer line, so we can refer to them
17975 without requiring all our users to memorize their IP addresses.
17976 - Remove option when getting directory cache to see whether they
17977 support running-routers; they all do now. Replace it with one
17978 to see whether caches support v2 stuff.
17979 - Stop listing down or invalid nodes in the v1 directory. This
17980 reduces its bulk by about 1/3, and reduces load on mirrors.
17981 - Mirrors no longer cache the v1 directory as often.
17982 - If we as a directory mirror don't know of any v1 directory
17983 authorities, then don't try to cache any v1 directories.
17985 o Other directory improvements:
17986 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
17987 fifth authoritative directory servers.
17988 - Directory authorities no longer require an open connection from
17989 a server to consider him "reachable". We need this change because
17990 when we add new directory authorities, old servers won't know not
17991 to hang up on them.
17992 - Dir authorities now do their own external reachability testing
17993 of each server, and only list as running the ones they found to
17994 be reachable. We also send back warnings to the server's logs if
17995 it uploads a descriptor that we already believe is unreachable.
17996 - Spread the directory authorities' reachability testing over the
17997 entire testing interval, so we don't try to do 500 TLS's at once
17999 - Make the "stable" router flag in network-status be the median of
18000 the uptimes of running valid servers, and make clients pay
18001 attention to the network-status flags. Thus the cutoff adapts
18002 to the stability of the network as a whole, making IRC, IM, etc
18003 connections more reliable.
18004 - Make the v2 dir's "Fast" flag based on relative capacity, just
18005 like "Stable" is based on median uptime. Name everything in the
18006 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
18007 - Retry directory requests if we fail to get an answer we like
18008 from a given dirserver (we were retrying before, but only if
18009 we fail to connect).
18010 - Return a robots.txt on our dirport to discourage google indexing.
18012 o Controller protocol improvements:
18013 - Revised controller protocol (version 1) that uses ascii rather
18014 than binary: tor/doc/control-spec.txt. Add supporting libraries
18015 in python and java and c# so you can use the controller from your
18016 applications without caring how our protocol works.
18017 - Allow the DEBUG controller event to work again. Mark certain log
18018 entries as "don't tell this to controllers", so we avoid cycles.
18019 - New controller function "getinfo accounting", to ask how
18020 many bytes we've used in this time period.
18021 - Add a "resetconf" command so you can set config options like
18022 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
18023 a config option in the torrc with no value, then it clears it
18024 entirely (rather than setting it to its default).
18025 - Add a "getinfo config-file" to tell us where torrc is. Also
18026 expose guard nodes, config options/names.
18027 - Add a "quit" command (when when using the controller manually).
18028 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
18029 stop using any currently-dirty circuits for new streams, so we
18030 don't link new actions to old actions. This also occurs on HUP
18031 or "signal reload".
18032 - If we would close a stream early (e.g. it asks for a .exit that
18033 we know would refuse it) but the LeaveStreamsUnattached config
18034 option is set by the controller, then don't close it.
18035 - Add a new controller event type "authdir_newdescs" that allows
18036 controllers to get all server descriptors that were uploaded to
18037 a router in its role as directory authority.
18038 - New controller option "getinfo desc/all-recent" to fetch the
18039 latest server descriptor for every router that Tor knows about.
18040 - Fix the controller's "attachstream 0" command to treat conn like
18041 it just connected, doing address remapping, handling .exit and
18042 .onion idioms, and so on. Now we're more uniform in making sure
18043 that the controller hears about new and closing connections.
18044 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
18045 the controller. Also, rotate dns and cpu workers if the controller
18046 changes options that will affect them; and initialize the dns
18047 worker cache tree whether or not we start out as a server.
18048 - Add a new circuit purpose 'controller' to let the controller ask
18049 for a circuit that Tor won't try to use. Extend the "extendcircuit"
18050 controller command to let you specify the purpose if you're starting
18051 a new circuit. Add a new "setcircuitpurpose" controller command to
18052 let you change a circuit's purpose after it's been created.
18053 - Let the controller ask for "getinfo dir/server/foo" so it can ask
18054 directly rather than connecting to the dir port. "getinfo
18055 dir/status/foo" also works, but currently only if your DirPort
18057 - Let the controller tell us about certain router descriptors
18058 that it doesn't want Tor to use in circuits. Implement
18059 "setrouterpurpose" and modify "+postdescriptor" to do this.
18060 - If the controller's *setconf commands fail, collect an error
18061 message in a string and hand it back to the controller -- don't
18062 just tell them to go read their logs.
18064 o Scalability, resource management, and performance:
18065 - Fix a major load balance bug: we were round-robin reading in 16 KB
18066 chunks, and servers with bandwidthrate of 20 KB, while downloading
18067 a 600 KB directory, would starve their other connections. Now we
18068 try to be a bit more fair.
18069 - Be more conservative about whether to advertise our DirPort.
18070 The main change is to not advertise if we're running at capacity
18071 and either a) we could hibernate ever or b) our capacity is low
18072 and we're using a default DirPort.
18073 - We weren't cannibalizing circuits correctly for
18074 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
18075 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
18076 build those from scratch. This should make hidden services faster.
18077 - Predict required circuits better, with an eye toward making hidden
18078 services faster on the service end.
18079 - Compress exit policies even more: look for duplicate lines and
18081 - Generate 18.0.0.0/8 address policy format in descs when we can;
18082 warn when the mask is not reducible to a bit-prefix.
18083 - There used to be two ways to specify your listening ports in a
18084 server descriptor: on the "router" line and with a separate "ports"
18085 line. Remove support for the "ports" line.
18086 - Reduce memory requirements in our structs by changing the order
18087 of fields. Replace balanced trees with hash tables. Inline
18088 bottleneck smartlist functions. Add a "Map from digest to void*"
18089 abstraction so we can do less hex encoding/decoding, and use it
18090 in router_get_by_digest(). Many other CPU and memory improvements.
18091 - Allow tor_gzip_uncompress to extract as much as possible from
18092 truncated compressed data. Try to extract as many
18093 descriptors as possible from truncated http responses (when
18094 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
18095 - Make circ->onionskin a pointer, not a static array. moria2 was using
18096 125000 circuit_t's after it had been up for a few weeks, which
18097 translates to 20+ megs of wasted space.
18098 - The private half of our EDH handshake keys are now chosen out
18099 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
18100 - Stop doing the complex voodoo overkill checking for insecure
18101 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
18102 - Do round-robin writes for TLS of at most 16 kB per write. This
18103 might be more fair on loaded Tor servers.
18104 - Do not use unaligned memory access on alpha, mips, or mipsel.
18105 It *works*, but is very slow, so we treat them as if it doesn't.
18107 o Other bugfixes and improvements:
18108 - Start storing useful information to $DATADIR/state, so we can
18109 remember things across invocations of Tor. Retain unrecognized
18110 lines so we can be forward-compatible, and write a TorVersion line
18111 so we can be backward-compatible.
18112 - If ORPort is set, Address is not explicitly set, and our hostname
18113 resolves to a private IP address, try to use an interface address
18114 if it has a public address. Now Windows machines that think of
18115 themselves as localhost can guess their address.
18116 - Regenerate our local descriptor if it's dirty and we try to use
18117 it locally (e.g. if it changes during reachability detection).
18118 This was causing some Tor servers to keep publishing the same
18119 initial descriptor forever.
18120 - Tor servers with dynamic IP addresses were needing to wait 18
18121 hours before they could start doing reachability testing using
18122 the new IP address and ports. This is because they were using
18123 the internal descriptor to learn what to test, yet they were only
18124 rebuilding the descriptor once they decided they were reachable.
18125 - It turns out we couldn't bootstrap a network since we added
18126 reachability detection in 0.1.0.1-rc. Good thing the Tor network
18127 has never gone down. Add an AssumeReachable config option to let
18128 servers and authorities bootstrap. When we're trying to build a
18129 high-uptime or high-bandwidth circuit but there aren't enough
18130 suitable servers, try being less picky rather than simply failing.
18131 - Newly bootstrapped Tor networks couldn't establish hidden service
18132 circuits until they had nodes with high uptime. Be more tolerant.
18133 - Really busy servers were keeping enough circuits open on stable
18134 connections that they were wrapping around the circuit_id
18135 space. (It's only two bytes.) This exposed a bug where we would
18136 feel free to reuse a circuit_id even if it still exists but has
18137 been marked for close. Try to fix this bug. Some bug remains.
18138 - When we fail to bind or listen on an incoming or outgoing
18139 socket, we now close it before refusing, rather than just
18140 leaking it. (Thanks to Peter Palfrader for finding.)
18141 - Fix a file descriptor leak in start_daemon().
18142 - On Windows, you can't always reopen a port right after you've
18143 closed it. So change retry_listeners() to only close and re-open
18144 ports that have changed.
18145 - Workaround a problem with some http proxies that refuse GET
18146 requests that specify "Content-Length: 0". Reported by Adrian.
18147 - Recover better from TCP connections to Tor servers that are
18148 broken but don't tell you (it happens!); and rotate TLS
18149 connections once a week.
18150 - Fix a scary-looking but apparently harmless bug where circuits
18151 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
18152 servers, and never switch to state CIRCUIT_STATE_OPEN.
18153 - Check for even more Windows version flags when writing the platform
18154 string in server descriptors, and note any we don't recognize.
18155 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
18156 get a better idea of why their circuits failed. Not used yet.
18157 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
18158 We don't use them yet, but maybe one day our DNS resolver will be
18159 able to discover them.
18160 - Let people type "tor --install" as well as "tor -install" when they
18161 want to make it an NT service.
18162 - Looks like we were never delivering deflated (i.e. compressed)
18163 running-routers lists, even when asked. Oops.
18164 - We were leaking some memory every time the client changed IPs.
18165 - Clean up more of the OpenSSL memory when exiting, so we can detect
18166 memory leaks better.
18167 - Never call free() on tor_malloc()d memory. This will help us
18168 use dmalloc to detect memory leaks.
18169 - Some Tor servers process billions of cells per day. These
18170 statistics are now uint64_t's.
18171 - Check [X-]Forwarded-For headers in HTTP requests when generating
18172 log messages. This lets people run dirservers (and caches) behind
18173 Apache but still know which IP addresses are causing warnings.
18174 - Fix minor integer overflow in calculating when we expect to use up
18175 our bandwidth allocation before hibernating.
18176 - Lower the minimum required number of file descriptors to 1000,
18177 so we can have some overhead for Valgrind on Linux, where the
18178 default ulimit -n is 1024.
18179 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
18180 and its existence is confusing some users.
18182 o Config option fixes:
18183 - Add a new config option ExitPolicyRejectPrivate which defaults
18184 to on. Now all exit policies will begin with rejecting private
18185 addresses, unless the server operator explicitly turns it off.
18186 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
18187 - Add new ReachableORAddresses and ReachableDirAddresses options
18188 that understand address policies. FascistFirewall is now a synonym
18189 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
18190 - Start calling it FooListenAddress rather than FooBindAddress,
18191 since few of our users know what it means to bind an address
18193 - If the user gave Tor an odd number of command-line arguments,
18194 we were silently ignoring the last one. Now we complain and fail.
18195 This wins the oldest-bug prize -- this bug has been present since
18196 November 2002, as released in Tor 0.0.0.
18197 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
18198 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
18199 it would silently ignore the 6668.
18200 - If we get a linelist or linelist_s config option from the torrc,
18201 e.g. ExitPolicy, and it has no value, warn and skip rather than
18202 silently resetting it to its default.
18203 - Setconf was appending items to linelists, not clearing them.
18204 - Add MyFamily to torrc.sample in the server section, so operators
18205 will be more likely to learn that it exists.
18206 - Make ContactInfo mandatory for authoritative directory servers.
18207 - MaxConn has been obsolete for a while now. Document the ConnLimit
18208 config option, which is a *minimum* number of file descriptors
18209 that must be available else Tor refuses to start.
18210 - Get rid of IgnoreVersion undocumented config option, and make us
18211 only warn, never exit, when we're running an obsolete version.
18212 - Make MonthlyAccountingStart config option truly obsolete now.
18213 - Correct the man page entry on TrackHostExitsExpire.
18214 - Let directory authorities start even if they don't specify an
18215 Address config option.
18216 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
18217 reflect the updated flags in our v2 dir protocol.
18219 o Config option features:
18220 - Add a new config option FastFirstHopPK (on by default) so clients
18221 do a trivial crypto handshake for their first hop, since TLS has
18222 already taken care of confidentiality and authentication.
18223 - Let the user set ControlListenAddress in the torrc. This can be
18224 dangerous, but there are some cases (like a secured LAN) where it
18226 - New config options to help controllers: FetchServerDescriptors
18227 and FetchHidServDescriptors for whether to fetch server
18228 info and hidserv info or let the controller do it, and
18229 PublishServerDescriptor and PublishHidServDescriptors.
18230 - Also let the controller set the __AllDirActionsPrivate config
18231 option if you want all directory fetches/publishes to happen via
18232 Tor (it assumes your controller bootstraps your circuits).
18233 - Add "HardwareAccel" config option: support for crypto hardware
18234 accelerators via OpenSSL. Off by default, until we find somebody
18235 smart who can test it for us. (It appears to produce seg faults
18236 in at least some cases.)
18237 - New config option "AuthDirRejectUnlisted" for directory authorities
18238 as a panic button: if we get flooded with unusable servers we can
18239 revert to only listing servers in the approved-routers file.
18240 - Directory authorities can now reject/invalidate by key and IP,
18241 with the config options "AuthDirInvalid" and "AuthDirReject", or
18242 by marking a fingerprint as "!reject" or "!invalid" (as its
18243 nickname) in the approved-routers file. This is useful since
18244 currently we automatically list servers as running and usable
18245 even if we know they're jerks.
18246 - Add a new config option TestSocks so people can see whether their
18247 applications are using socks4, socks4a, socks5-with-ip, or
18248 socks5-with-fqdn. This way they don't have to keep mucking
18249 with tcpdump and wondering if something got cached somewhere.
18250 - Add "private:*" as an alias in configuration for policies. Now
18251 you can simplify your exit policy rather than needing to list
18252 every single internal or nonroutable network space.
18253 - Accept "private:*" in routerdesc exit policies; not generated yet
18254 because older Tors do not understand it.
18255 - Add configuration option "V1AuthoritativeDirectory 1" which
18256 moria1, moria2, and tor26 have set.
18257 - Implement an option, VirtualAddrMask, to set which addresses
18258 get handed out in response to mapaddress requests. This works
18259 around a bug in tsocks where 127.0.0.0/8 is never socksified.
18260 - Add a new config option FetchUselessDescriptors, off by default,
18261 for when you plan to run "exitlist" on your client and you want
18262 to know about even the non-running descriptors.
18263 - SocksTimeout: How long do we let a socks connection wait
18264 unattached before we fail it?
18265 - CircuitBuildTimeout: Cull non-open circuits that were born
18266 at least this many seconds ago.
18267 - CircuitIdleTimeout: Cull open clean circuits that were born
18268 at least this many seconds ago.
18269 - New config option SafeSocks to reject all application connections
18270 using unsafe socks protocols. Defaults to off.
18272 o Improved and clearer log messages:
18273 - Reduce clutter in server logs. We're going to try to make
18274 them actually usable now. New config option ProtocolWarnings that
18275 lets you hear about how _other Tors_ are breaking the protocol. Off
18277 - Divide log messages into logging domains. Once we put some sort
18278 of interface on this, it will let people looking at more verbose
18279 log levels specify the topics they want to hear more about.
18280 - Log server fingerprint on startup, so new server operators don't
18281 have to go hunting around their filesystem for it.
18282 - Provide dire warnings to any users who set DirServer manually;
18283 move it out of torrc.sample and into torrc.complete.
18284 - Make the log message less scary when all the dirservers are
18285 temporarily unreachable.
18286 - When tor_socketpair() fails in Windows, give a reasonable
18287 Windows-style errno back.
18288 - Improve tor_gettimeofday() granularity on windows.
18289 - We were printing the number of idle dns workers incorrectly when
18291 - Handle duplicate lines in approved-routers files without warning.
18292 - We were whining about using socks4 or socks5-with-local-lookup
18293 even when it's an IP address in the "virtual" range we designed
18294 exactly for this case.
18295 - Check for named servers when looking them up by nickname;
18296 warn when we're calling a non-named server by its nickname;
18297 don't warn twice about the same name.
18298 - Downgrade the dirserver log messages when whining about
18300 - Correct "your server is reachable" log entries to indicate that
18301 it was self-testing that told us so.
18302 - If we're trying to be a Tor server and running Windows 95/98/ME
18303 as a server, explain that we'll likely crash.
18304 - Provide a more useful warn message when our onion queue gets full:
18305 the CPU is too slow or the exit policy is too liberal.
18306 - Don't warn when we receive a 503 from a dirserver/cache -- this
18307 will pave the way for them being able to refuse if they're busy.
18308 - When we fail to bind a listener, try to provide a more useful
18309 log message: e.g., "Is Tor already running?"
18310 - Only start testing reachability once we've established a
18311 circuit. This will make startup on dir authorities less noisy.
18312 - Don't try to upload hidden service descriptors until we have
18313 established a circuit.
18314 - Tor didn't warn when it failed to open a log file.
18315 - Warn when listening on a public address for socks. We suspect a
18316 lot of people are setting themselves up as open socks proxies,
18317 and they have no idea that jerks on the Internet are using them,
18318 since they simply proxy the traffic into the Tor network.
18319 - Give a useful message when people run Tor as the wrong user,
18320 rather than telling them to start chowning random directories.
18321 - Fix a harmless bug that was causing Tor servers to log
18322 "Got an end because of misc error, but we're not an AP. Closing."
18323 - Fix wrong log message when you add a "HiddenServiceNodes" config
18324 line without any HiddenServiceDir line (reported by Chris Thomas).
18325 - Directory authorities now stop whining so loudly about bad
18326 descriptors that they fetch from other dirservers. So when there's
18327 a log complaint, it's for sure from a freshly uploaded descriptor.
18328 - When logging via syslog, include the pid whenever we provide
18329 a log entry. Suggested by Todd Fries.
18330 - When we're shutting down and we do something like try to post a
18331 server descriptor or rendezvous descriptor, don't complain that
18332 we seem to be unreachable. Of course we are, we're shutting down.
18333 - Change log line for unreachability to explicitly suggest /etc/hosts
18334 as the culprit. Also make it clearer what IP address and ports we're
18335 testing for reachability.
18336 - Put quotes around user-supplied strings when logging so users are
18337 more likely to realize if they add bad characters (like quotes)
18339 - NT service patch from Matt Edman to improve error messages on Win32.
18342 Changes in version 0.1.0.17 - 2006-02-17
18343 o Crash bugfixes on 0.1.0.x:
18344 - When servers with a non-zero DirPort came out of hibernation,
18345 sometimes they would trigger an assert.
18347 o Other important bugfixes:
18348 - On platforms that don't have getrlimit (like Windows), we were
18349 artificially constraining ourselves to a max of 1024
18350 connections. Now just assume that we can handle as many as 15000
18351 connections. Hopefully this won't cause other problems.
18353 o Backported features:
18354 - When we're a server, a client asks for an old-style directory,
18355 and our write bucket is empty, don't give it to him. This way
18356 small servers can continue to serve the directory *sometimes*,
18357 without getting overloaded.
18358 - Whenever you get a 503 in response to a directory fetch, try
18359 once more. This will become important once servers start sending
18360 503's whenever they feel busy.
18361 - Fetch a new directory every 120 minutes, not every 40 minutes.
18362 Now that we have hundreds of thousands of users running the old
18363 directory algorithm, it's starting to hurt a lot.
18364 - Bump up the period for forcing a hidden service descriptor upload
18365 from 20 minutes to 1 hour.
18368 Changes in version 0.1.0.16 - 2006-01-02
18369 o Crash bugfixes on 0.1.0.x:
18370 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
18371 corrupting the heap, losing FDs, or crashing when we need to resize
18372 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
18373 - It turns out sparc64 platforms crash on unaligned memory access
18374 too -- so detect and avoid this.
18375 - Handle truncated compressed data correctly (by detecting it and
18377 - Fix possible-but-unlikely free(NULL) in control.c.
18378 - When we were closing connections, there was a rare case that
18379 stomped on memory, triggering seg faults and asserts.
18380 - Avoid potential infinite recursion when building a descriptor. (We
18381 don't know that it ever happened, but better to fix it anyway.)
18382 - We were neglecting to unlink marked circuits from soon-to-close OR
18383 connections, which caused some rare scribbling on freed memory.
18384 - Fix a memory stomping race bug when closing the joining point of two
18385 rendezvous circuits.
18386 - Fix an assert in time parsing found by Steven Murdoch.
18388 o Other bugfixes on 0.1.0.x:
18389 - When we're doing reachability testing, provide more useful log
18390 messages so the operator knows what to expect.
18391 - Do not check whether DirPort is reachable when we are suppressing
18392 advertising it because of hibernation.
18393 - When building with -static or on Solaris, we sometimes needed -ldl.
18394 - One of the dirservers (tor26) changed its IP address.
18395 - When we're deciding whether a stream has enough circuits around
18396 that can handle it, count the freshly dirty ones and not the ones
18397 that are so dirty they won't be able to handle it.
18398 - When we're expiring old circuits, we had a logic error that caused
18399 us to close new rendezvous circuits rather than old ones.
18400 - Give a more helpful log message when you try to change ORPort via
18401 the controller: you should upgrade Tor if you want that to work.
18402 - We were failing to parse Tor versions that start with "Tor ".
18403 - Tolerate faulty streams better: when a stream fails for reason
18404 exitpolicy, stop assuming that the router is lying about his exit
18405 policy. When a stream fails for reason misc, allow it to retry just
18406 as if it was resolvefailed. When a stream has failed three times,
18407 reset its failure count so we can try again and get all three tries.
18410 Changes in version 0.1.0.15 - 2005-09-23
18411 o Bugfixes on 0.1.0.x:
18412 - Reject ports 465 and 587 (spam targets) in default exit policy.
18413 - Don't crash when we don't have any spare file descriptors and we
18414 try to spawn a dns or cpu worker.
18415 - Get rid of IgnoreVersion undocumented config option, and make us
18416 only warn, never exit, when we're running an obsolete version.
18417 - Don't try to print a null string when your server finds itself to
18418 be unreachable and the Address config option is empty.
18419 - Make the numbers in read-history and write-history into uint64s,
18420 so they don't overflow and publish negatives in the descriptor.
18421 - Fix a minor memory leak in smartlist_string_remove().
18422 - We were only allowing ourselves to upload a server descriptor at
18423 most every 20 minutes, even if it changed earlier than that.
18424 - Clean up log entries that pointed to old URLs.
18427 Changes in version 0.1.0.14 - 2005-08-08
18428 o Bugfixes on 0.1.0.x:
18429 - Fix the other half of the bug with crypto handshakes
18431 - Fix an assert trigger if you send a 'signal term' via the
18432 controller when it's listening for 'event info' messages.
18435 Changes in version 0.1.0.13 - 2005-08-04
18436 o Bugfixes on 0.1.0.x:
18437 - Fix a critical bug in the security of our crypto handshakes.
18438 - Fix a size_t underflow in smartlist_join_strings2() that made
18439 it do bad things when you hand it an empty smartlist.
18440 - Fix Windows installer to ship Tor license (thanks to Aphex for
18441 pointing out this oversight) and put a link to the doc directory
18443 - Explicitly set no-unaligned-access for sparc: it turns out the
18444 new gcc's let you compile broken code, but that doesn't make it
18448 Changes in version 0.1.0.12 - 2005-07-18
18449 o New directory servers:
18450 - tor26 has changed IP address.
18452 o Bugfixes on 0.1.0.x:
18453 - Fix a possible double-free in tor_gzip_uncompress().
18454 - When --disable-threads is set, do not search for or link against
18455 pthreads libraries.
18456 - Don't trigger an assert if an authoritative directory server
18457 claims its dirport is 0.
18458 - Fix bug with removing Tor as an NT service: some people were
18459 getting "The service did not return an error." Thanks to Matt
18463 Changes in version 0.1.0.11 - 2005-06-30
18464 o Bugfixes on 0.1.0.x:
18465 - Fix major security bug: servers were disregarding their
18466 exit policies if clients behaved unexpectedly.
18467 - Make OS X init script check for missing argument, so we don't
18468 confuse users who invoke it incorrectly.
18469 - Fix a seg fault in "tor --hash-password foo".
18470 - The MAPADDRESS control command was broken.
18473 Changes in version 0.1.0.10 - 2005-06-14
18475 - Make NT services work and start on startup on Win32 (based on
18476 patch by Matt Edman). See the FAQ entry for details.
18477 - Make 'platform' string in descriptor more accurate for Win32
18478 servers, so it's not just "unknown platform".
18479 - REUSEADDR on normal platforms means you can rebind to the port
18480 right after somebody else has let it go. But REUSEADDR on Win32
18481 means you can bind to the port _even when somebody else already
18482 has it bound_! So, don't do that on Win32.
18483 - Clean up the log messages when starting on Win32 with no config
18485 - Allow seeding the RNG on Win32 even when you're not running as
18486 Administrator. If seeding the RNG on Win32 fails, quit.
18488 o Assert / crash bugs:
18489 - Refuse relay cells that claim to have a length larger than the
18490 maximum allowed. This prevents a potential attack that could read
18491 arbitrary memory (e.g. keys) from an exit server's process
18493 - If unofficial Tor clients connect and send weird TLS certs, our
18494 Tor server triggers an assert. Stop asserting, and start handling
18495 TLS errors better in other situations too.
18496 - Fix a race condition that can trigger an assert when we have a
18497 pending create cell and an OR connection attempt fails.
18500 - Use pthreads for worker processes rather than forking. This was
18501 forced because when we forked, we ended up wasting a lot of
18502 duplicate ram over time.
18503 - Also switch to foo_r versions of some library calls to allow
18504 reentry and threadsafeness.
18505 - Implement --disable-threads configure option. Disable threads on
18506 netbsd and openbsd by default, because they have no reentrant
18507 resolver functions (!), and on solaris since it has other
18509 - Fix possible bug on threading platforms (e.g. win32) which was
18510 leaking a file descriptor whenever a cpuworker or dnsworker died.
18511 - Fix a minor memory leak when somebody establishes an introduction
18512 point at your Tor server.
18513 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
18515 - Add ./configure --with-dmalloc option, to track memory leaks.
18516 - And try to free all memory on closing, so we can detect what
18519 o Protocol correctness:
18520 - When we've connected to an OR and handshaked but didn't like
18521 the result, we were closing the conn without sending destroy
18522 cells back for pending circuits. Now send those destroys.
18523 - Start sending 'truncated' cells back rather than destroy cells
18524 if the circuit closes in front of you. This means we won't have
18525 to abandon partially built circuits.
18526 - Handle changed router status correctly when dirserver reloads
18527 fingerprint file. We used to be dropping all unverified descriptors
18528 right then. The bug was hidden because we would immediately
18529 fetch a directory from another dirserver, which would include the
18530 descriptors we just dropped.
18531 - Revise tor-spec to add more/better stream end reasons.
18532 - Revise all calls to connection_edge_end to avoid sending 'misc',
18533 and to take errno into account where possible.
18534 - Client now retries when streams end early for 'hibernating' or
18535 'resource limit' reasons, rather than failing them.
18536 - Try to be more zealous about calling connection_edge_end when
18537 things go bad with edge conns in connection.c.
18539 o Robustness improvements:
18540 - Better handling for heterogeneous / unreliable nodes:
18541 - Annotate circuits with whether they aim to contain high uptime
18542 nodes and/or high capacity nodes. When building circuits, choose
18544 - This means that every single node in an intro rend circuit,
18545 not just the last one, will have a minimum uptime.
18546 - New config option LongLivedPorts to indicate application streams
18547 that will want high uptime circuits.
18548 - Servers reset uptime when a dir fetch entirely fails. This
18549 hopefully reflects stability of the server's network connectivity.
18550 - If somebody starts his tor server in Jan 2004 and then fixes his
18551 clock, don't make his published uptime be a year.
18552 - Reset published uptime when we wake up from hibernation.
18553 - Introduce a notion of 'internal' circs, which are chosen without
18554 regard to the exit policy of the last hop. Intro and rendezvous
18555 circs must be internal circs, to avoid leaking information. Resolve
18556 and connect streams can use internal circs if they want.
18557 - New circuit pooling algorithm: keep track of what destination ports
18558 we've used recently (start out assuming we'll want to use 80), and
18559 make sure to have enough circs around to satisfy these ports. Also
18560 make sure to have 2 internal circs around if we've required internal
18561 circs lately (and with high uptime if we've seen that lately too).
18562 - Turn addr_policy_compare from a tristate to a quadstate; this should
18563 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
18564 for google.com" problem.
18565 - When a client asks us for a dir mirror and we don't have one,
18566 launch an attempt to get a fresh one.
18567 - First cut at support for "create-fast" cells. Clients can use
18568 these when extending to their first hop, since the TLS already
18569 provides forward secrecy and authentication. Not enabled on
18572 o Reachability testing.
18573 - Your Tor server will automatically try to see if its ORPort and
18574 DirPort are reachable from the outside, and it won't upload its
18575 descriptor until it decides at least ORPort is reachable (when
18576 DirPort is not yet found reachable, publish it as zero).
18577 - When building testing circs for ORPort testing, use only
18578 high-bandwidth nodes, so fewer circuits fail.
18579 - Notice when our IP changes, and reset stats/uptime/reachability.
18580 - Authdirservers don't do ORPort reachability detection, since
18581 they're in clique mode, so it will be rare to find a server not
18582 already connected to them.
18583 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
18587 - Now we allow two unverified servers with the same nickname
18588 but different keys. But if a nickname is verified, only that
18589 nickname+key are allowed.
18590 - If you're an authdirserver connecting to an address:port,
18591 and it's not the OR you were expecting, forget about that
18592 descriptor. If he *was* the one you were expecting, then forget
18593 about all other descriptors for that address:port.
18594 - Allow servers to publish descriptors from 12 hours in the future.
18595 Corollary: only whine about clock skew from the dirserver if
18596 he's a trusted dirserver (since now even verified servers could
18597 have quite wrong clocks).
18598 - Require servers that use the default dirservers to have public IP
18599 addresses. We have too many servers that are configured with private
18600 IPs and their admins never notice the log entries complaining that
18601 their descriptors are being rejected.
18603 o Efficiency improvements:
18604 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
18605 and /dev/poll), and hopefully work better on Windows too.
18606 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
18607 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
18608 - Find libevent even if it's hiding in /usr/local/ and your
18609 CFLAGS and LDFLAGS don't tell you to look there.
18610 - Be able to link with libevent as a shared library (the default
18611 after 1.0d), even if it's hiding in /usr/local/lib and even
18612 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
18613 assuming you're running gcc. Otherwise fail and give a useful
18615 - Switch to a new buffer management algorithm, which tries to avoid
18616 reallocing and copying quite as much. In first tests it looks like
18617 it uses *more* memory on average, but less cpu.
18618 - Switch our internal buffers implementation to use a ring buffer,
18619 to hopefully improve performance for fast servers a lot.
18620 - Reenable the part of the code that tries to flush as soon as an
18621 OR outbuf has a full TLS record available. Perhaps this will make
18622 OR outbufs not grow as huge except in rare cases, thus saving lots
18623 of CPU time plus memory.
18624 - Improve performance for dirservers: stop re-parsing the whole
18625 directory every time you regenerate it.
18626 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
18627 it much faster to look up a circuit for each relay cell.
18628 - Remove most calls to assert_all_pending_dns_resolves_ok(),
18629 since they're eating our cpu on exit nodes.
18630 - Stop wasting time doing a case insensitive comparison for every
18631 dns name every time we do any lookup. Canonicalize the names to
18632 lowercase when you first see them.
18635 - Handle unavailable hidden services better. Handle slow or busy
18636 hidden services better.
18637 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
18638 circ as necessary, if there are any completed ones lying around
18639 when we try to launch one.
18640 - Make hidden services try to establish a rendezvous for 30 seconds
18641 after fetching the descriptor, rather than for n (where n=3)
18642 attempts to build a circuit.
18643 - Adjust maximum skew and age for rendezvous descriptors: let skew
18644 be 48 hours rather than 90 minutes.
18645 - Reject malformed .onion addresses rather then passing them on as
18646 normal web requests.
18649 - More Tor controller support. See
18650 http://tor.eff.org/doc/control-spec.txt for all the new features,
18651 including signals to emulate unix signals from any platform;
18652 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
18653 closestream; closecircuit; etc.
18654 - Encode hashed controller passwords in hex instead of base64,
18655 to make it easier to write controllers.
18656 - Revise control spec and implementation to allow all log messages to
18657 be sent to controller with their severities intact (suggested by
18658 Matt Edman). Disable debug-level logs while delivering a debug-level
18659 log to the controller, to prevent loop. Update TorControl to handle
18660 new log event types.
18662 o New config options/defaults:
18663 - Begin scrubbing sensitive strings from logs by default. Turn off
18664 the config option SafeLogging if you need to do debugging.
18665 - New exit policy: accept most low-numbered ports, rather than
18666 rejecting most low-numbered ports.
18667 - Put a note in the torrc about abuse potential with the default
18669 - Add support for CONNECTing through https proxies, with "HttpsProxy"
18671 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
18672 based on patch from Adam Langley (basic auth only).
18673 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
18674 the fast servers that have been joining lately. (Clients are now
18675 willing to load balance over up to 2 MB of advertised bandwidth
18677 - New config option MaxAdvertisedBandwidth which lets you advertise
18678 a low bandwidthrate (to not attract as many circuits) while still
18679 allowing a higher bandwidthrate in reality.
18680 - Require BandwidthRate to be at least 20kB/s for servers.
18681 - Add a NoPublish config option, so you can be a server (e.g. for
18682 testing running Tor servers in other Tor networks) without
18683 publishing your descriptor to the primary dirservers.
18684 - Add a new AddressMap config directive to rewrite incoming socks
18685 addresses. This lets you, for example, declare an implicit
18686 required exit node for certain sites.
18687 - Add a new TrackHostExits config directive to trigger addressmaps
18688 for certain incoming socks addresses -- for sites that break when
18689 your exit keeps changing (based on patch from Mike Perry).
18690 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
18691 which describes how often we retry making new circuits if current
18692 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
18693 how long we're willing to make use of an already-dirty circuit.
18694 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
18695 a config option "ShutdownWaitLength" (when using kill -INT on
18697 - Fix an edge case in parsing config options: if they say "--"
18698 on the commandline, it's not a config option (thanks weasel).
18699 - New config option DirAllowPrivateAddresses for authdirservers.
18700 Now by default they refuse router descriptors that have non-IP or
18701 private-IP addresses.
18702 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
18703 smart" default value: low for servers and high for clients.
18704 - Some people were putting "Address " in their torrc, and they had
18705 a buggy resolver that resolved " " to 0.0.0.0. Oops.
18706 - If DataDir is ~/.tor, and that expands to /.tor, then default to
18707 LOCALSTATEDIR/tor instead.
18708 - Implement --verify-config command-line option to check if your torrc
18709 is valid without actually launching Tor.
18711 o Logging improvements:
18712 - When dirservers refuse a server descriptor, we now log its
18713 contactinfo, platform, and the poster's IP address.
18714 - Only warn once per nickname from add_nickname_list_to_smartlist()
18715 per failure, so an entrynode or exitnode choice that's down won't
18717 - When we're connecting to an OR and he's got a different nickname/key
18718 than we were expecting, only complain loudly if we're an OP or a
18719 dirserver. Complaining loudly to the OR admins just confuses them.
18720 - Whine at you if you're a server and you don't set your contactinfo.
18721 - Warn when exit policy implicitly allows local addresses.
18722 - Give a better warning when some other server advertises an
18723 ORPort that is actually an apache running ssl.
18724 - If we get an incredibly skewed timestamp from a dirserver mirror
18725 that isn't a verified OR, don't warn -- it's probably him that's
18727 - When a dirserver causes you to give a warn, mention which dirserver
18729 - Initialize libevent later in the startup process, so the logs are
18730 already established by the time we start logging libevent warns.
18731 - Use correct errno on win32 if libevent fails.
18732 - Check and warn about known-bad/slow libevent versions.
18733 - Stop warning about sigpipes in the logs. We're going to
18734 pretend that getting these occasionally is normal and fine.
18736 o New contrib scripts:
18737 - New experimental script tor/contrib/exitlist: a simple python
18738 script to parse directories and find Tor nodes that exit to listed
18740 - New experimental script tor/contrib/ExerciseServer.py (needs more
18741 work) that uses the controller interface to build circuits and
18742 fetch pages over them. This will help us bootstrap servers that
18743 have lots of capacity but haven't noticed it yet.
18744 - New experimental script tor/contrib/PathDemo.py (needs more work)
18745 that uses the controller interface to let you choose whole paths
18747 "<hostname>.<path,separated by dots>.<length of path>.path"
18748 - New contributed script "privoxy-tor-toggle" to toggle whether
18749 Privoxy uses Tor. Seems to be configured for Debian by default.
18750 - Have torctl.in/tor.sh.in check for location of su binary (needed
18754 - chdir() to your datadirectory at the *end* of the daemonize process,
18755 not the beginning. This was a problem because the first time you
18756 run tor, if your datadir isn't there, and you have runasdaemon set
18757 to 1, it will try to chdir to it before it tries to create it. Oops.
18758 - Fix several double-mark-for-close bugs, e.g. where we were finding
18759 a conn for a cell even if that conn is already marked for close.
18760 - Stop most cases of hanging up on a socks connection without sending
18762 - Fix a bug in the RPM package: set home directory for _tor to
18763 something more reasonable when first installing.
18764 - Stop putting nodename in the Platform string in server descriptors.
18765 It doesn't actually help, and it is confusing/upsetting some people.
18766 - When using preferred entry or exit nodes, ignore whether the
18767 circuit wants uptime or capacity. They asked for the nodes, they
18769 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
18770 artificially capped at 500kB.
18771 - Cache local dns resolves correctly even when they're .exit
18773 - If we're hibernating and we get a SIGINT, exit immediately.
18774 - tor-resolve requests were ignoring .exit if there was a working circuit
18775 they could use instead.
18776 - Pay more attention to the ClientOnly config option.
18777 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
18778 installer screens; and don't put stuff into StartupItems unless
18779 the user asks you to.
18782 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
18783 rather than just rejecting it.
18784 - If our clock jumps forward by 100 seconds or more, assume something
18785 has gone wrong with our network and abandon all not-yet-used circs.
18786 - When an application is using socks5, give him the whole variety of
18787 potential socks5 responses (connect refused, host unreachable, etc),
18788 rather than just "success" or "failure".
18789 - A more sane version numbering system. See
18790 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
18791 - Change version parsing logic: a version is "obsolete" if it is not
18792 recommended and (1) there is a newer recommended version in the
18793 same series, or (2) there are no recommended versions in the same
18794 series, but there are some recommended versions in a newer series.
18795 A version is "new" if it is newer than any recommended version in
18797 - Report HTTP reasons to client when getting a response from directory
18798 servers -- so you can actually know what went wrong.
18799 - Reject odd-looking addresses at the client (e.g. addresses that
18800 contain a colon), rather than having the server drop them because
18802 - Stop publishing socksport in the directory, since it's not
18803 actually meant to be public. For compatibility, publish a 0 there
18805 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
18806 cookies to disk and doesn't log each web request to disk. (Thanks
18807 to Brett Carrington for pointing this out.)
18808 - Add OSX uninstall instructions. An actual uninstall script will
18810 - Add "opt hibernating 1" to server descriptor to make it clearer
18811 whether the server is hibernating.
18814 Changes in version 0.0.9.10 - 2005-06-16
18815 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
18816 - Refuse relay cells that claim to have a length larger than the
18817 maximum allowed. This prevents a potential attack that could read
18818 arbitrary memory (e.g. keys) from an exit server's process
18822 Changes in version 0.0.9.9 - 2005-04-23
18823 o Bugfixes on 0.0.9.x:
18824 - If unofficial Tor clients connect and send weird TLS certs, our
18825 Tor server triggers an assert. This release contains a minimal
18826 backport from the broader fix that we put into 0.1.0.4-rc.
18829 Changes in version 0.0.9.8 - 2005-04-07
18830 o Bugfixes on 0.0.9.x:
18831 - We have a bug that I haven't found yet. Sometimes, very rarely,
18832 cpuworkers get stuck in the 'busy' state, even though the cpuworker
18833 thinks of itself as idle. This meant that no new circuits ever got
18834 established. Here's a workaround to kill any cpuworker that's been
18835 busy for more than 100 seconds.
18838 Changes in version 0.0.9.7 - 2005-04-01
18839 o Bugfixes on 0.0.9.x:
18840 - Fix another race crash bug (thanks to Glenn Fink for reporting).
18841 - Compare identity to identity, not to nickname, when extending to
18842 a router not already in the directory. This was preventing us from
18843 extending to unknown routers. Oops.
18844 - Make sure to create OS X Tor user in <500 range, so we aren't
18845 creating actual system users.
18846 - Note where connection-that-hasn't-sent-end was marked, and fix
18847 a few really loud instances of this harmless bug (it's fixed more
18851 Changes in version 0.0.9.6 - 2005-03-24
18852 o Bugfixes on 0.0.9.x (crashes and asserts):
18853 - Add new end stream reasons to maintenance branch. Fix bug where
18854 reason (8) could trigger an assert. Prevent bug from recurring.
18855 - Apparently win32 stat wants paths to not end with a slash.
18856 - Fix assert triggers in assert_cpath_layer_ok(), where we were
18857 blowing away the circuit that conn->cpath_layer points to, then
18858 checking to see if the circ is well-formed. Backport check to make
18859 sure we dont use the cpath on a closed connection.
18860 - Prevent circuit_resume_edge_reading_helper() from trying to package
18861 inbufs for marked-for-close streams.
18862 - Don't crash on hup if your options->address has become unresolvable.
18863 - Some systems (like OS X) sometimes accept() a connection and tell
18864 you the remote host is 0.0.0.0:0. If this happens, due to some
18865 other mis-features, we get confused; so refuse the conn for now.
18867 o Bugfixes on 0.0.9.x (other):
18868 - Fix harmless but scary "Unrecognized content encoding" warn message.
18869 - Add new stream error reason: TORPROTOCOL reason means "you are not
18870 speaking a version of Tor I understand; say bye-bye to your stream."
18871 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
18872 into the future, now that we are more tolerant of skew. This
18873 resolves a bug where a Tor server would refuse to cache a directory
18874 because all the directories it gets are too far in the future;
18875 yet the Tor server never logs any complaints about clock skew.
18876 - Mac packaging magic: make man pages useable, and do not overwrite
18877 existing torrc files.
18878 - Make OS X log happily to /var/log/tor/tor.log
18881 Changes in version 0.0.9.5 - 2005-02-22
18882 o Bugfixes on 0.0.9.x:
18883 - Fix an assert race at exit nodes when resolve requests fail.
18884 - Stop picking unverified dir mirrors--it only leads to misery.
18885 - Patch from Matt Edman to make NT services work better. Service
18886 support is still not compiled into the executable by default.
18887 - Patch from Dmitri Bely so the Tor service runs better under
18888 the win32 SYSTEM account.
18889 - Make tor-resolve actually work (?) on Win32.
18890 - Fix a sign bug when getrlimit claims to have 4+ billion
18891 file descriptors available.
18892 - Stop refusing to start when bandwidthburst == bandwidthrate.
18893 - When create cells have been on the onion queue more than five
18894 seconds, just send back a destroy and take them off the list.
18897 Changes in version 0.0.9.4 - 2005-02-03
18898 o Bugfixes on 0.0.9:
18899 - Fix an assert bug that took down most of our servers: when
18900 a server claims to have 1 GB of bandwidthburst, don't
18902 - Don't crash as badly if we have spawned the max allowed number
18903 of dnsworkers, or we're out of file descriptors.
18904 - Block more file-sharing ports in the default exit policy.
18905 - MaxConn is now automatically set to the hard limit of max
18906 file descriptors we're allowed (ulimit -n), minus a few for
18908 - Give a clearer message when servers need to raise their
18909 ulimit -n when they start running out of file descriptors.
18910 - SGI Compatibility patches from Jan Schaumann.
18911 - Tolerate a corrupt cached directory better.
18912 - When a dirserver hasn't approved your server, list which one.
18913 - Go into soft hibernation after 95% of the bandwidth is used,
18914 not 99%. This is especially important for daily hibernators who
18915 have a small accounting max. Hopefully it will result in fewer
18916 cut connections when the hard hibernation starts.
18917 - Load-balance better when using servers that claim more than
18918 800kB/s of capacity.
18919 - Make NT services work (experimental, only used if compiled in).
18922 Changes in version 0.0.9.3 - 2005-01-21
18923 o Bugfixes on 0.0.9:
18924 - Backport the cpu use fixes from main branch, so busy servers won't
18925 need as much processor time.
18926 - Work better when we go offline and then come back, or when we
18927 run Tor at boot before the network is up. We do this by
18928 optimistically trying to fetch a new directory whenever an
18929 application request comes in and we think we're offline -- the
18930 human is hopefully a good measure of when the network is back.
18931 - Backport some minimal hidserv bugfixes: keep rend circuits open as
18932 long as you keep using them; actually publish hidserv descriptors
18933 shortly after they change, rather than waiting 20-40 minutes.
18934 - Enable Mac startup script by default.
18935 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
18936 - When you update AllowUnverifiedNodes or FirewallPorts via the
18937 controller's setconf feature, we were always appending, never
18939 - When you update HiddenServiceDir via setconf, it was screwing up
18940 the order of reading the lines, making it fail.
18941 - Do not rewrite a cached directory back to the cache; otherwise we
18942 will think it is recent and not fetch a newer one on startup.
18943 - Workaround for webservers that lie about Content-Encoding: Tor
18944 now tries to autodetect compressed directories and compression
18945 itself. This lets us Proxypass dir fetches through apache.
18948 Changes in version 0.0.9.2 - 2005-01-04
18949 o Bugfixes on 0.0.9 (crashes and asserts):
18950 - Fix an assert on startup when the disk is full and you're logging
18952 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
18953 style address, then we'd crash.
18954 - Fix an assert trigger when the running-routers string we get from
18955 a dirserver is broken.
18956 - Make worker threads start and run on win32. Now win32 servers
18958 - Bandaid (not actually fix, but now it doesn't crash) an assert
18959 where the dns worker dies mysteriously and the main Tor process
18960 doesn't remember anything about the address it was resolving.
18962 o Bugfixes on 0.0.9 (Win32):
18963 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
18964 name out of the warning/assert messages.
18965 - Fix a superficial "unhandled error on read" bug on win32.
18966 - The win32 installer no longer requires a click-through for our
18967 license, since our Free Software license grants rights but does not
18969 - Win32: When connecting to a dirserver fails, try another one
18970 immediately. (This was already working for non-win32 Tors.)
18971 - Stop trying to parse $HOME on win32 when hunting for default
18973 - Make tor-resolve.c work on win32 by calling network_init().
18975 o Bugfixes on 0.0.9 (other):
18976 - Make 0.0.9.x build on Solaris again.
18977 - Due to a fencepost error, we were blowing away the \n when reporting
18978 confvalue items in the controller. So asking for multiple config
18979 values at once couldn't work.
18980 - When listing circuits that are pending on an opening OR connection,
18981 if we're an OR we were listing circuits that *end* at us as
18982 being pending on every listener, dns/cpu worker, etc. Stop that.
18983 - Dirservers were failing to create 'running-routers' or 'directory'
18984 strings if we had more than some threshold of routers. Fix them so
18985 they can handle any number of routers.
18986 - Fix a superficial "Duplicate mark for close" bug.
18987 - Stop checking for clock skew for OR connections, even for servers.
18988 - Fix a fencepost error that was chopping off the last letter of any
18989 nickname that is the maximum allowed nickname length.
18990 - Update URLs in log messages so they point to the new website.
18991 - Fix a potential problem in mangling server private keys while
18992 writing to disk (not triggered yet, as far as we know).
18993 - Include the licenses for other free software we include in Tor,
18994 now that we're shipping binary distributions more regularly.
18997 Changes in version 0.0.9.1 - 2004-12-15
18998 o Bugfixes on 0.0.9:
18999 - Make hibernation actually work.
19000 - Make HashedControlPassword config option work.
19001 - When we're reporting event circuit status to a controller,
19002 don't use the stream status code.
19005 Changes in version 0.0.9 - 2004-12-12
19006 o Bugfixes on 0.0.8.1 (Crashes and asserts):
19007 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
19008 write() call will fail and we handle it there.
19009 - When we run out of disk space, or other log writing error, don't
19010 crash. Just stop logging to that log and continue.
19011 - Fix isspace() and friends so they still make Solaris happy
19012 but also so they don't trigger asserts on win32.
19013 - Fix assert failure on malformed socks4a requests.
19014 - Fix an assert bug where a hidden service provider would fail if
19015 the first hop of his rendezvous circuit was down.
19016 - Better handling of size_t vs int, so we're more robust on 64
19019 o Bugfixes on 0.0.8.1 (Win32):
19020 - Make windows sockets actually non-blocking (oops), and handle
19021 win32 socket errors better.
19022 - Fix parse_iso_time on platforms without strptime (eg win32).
19023 - win32: when being multithreaded, leave parent fdarray open.
19024 - Better handling of winsock includes on non-MSV win32 compilers.
19025 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
19027 - Make unit tests work on win32.
19029 o Bugfixes on 0.0.8.1 (Path selection and streams):
19030 - Calculate timeout for waiting for a connected cell from the time
19031 we sent the begin cell, not from the time the stream started. If
19032 it took a long time to establish the circuit, we would time out
19033 right after sending the begin cell.
19034 - Fix router_compare_addr_to_addr_policy: it was not treating a port
19035 of * as always matching, so we were picking reject *:* nodes as
19036 exit nodes too. Oops.
19037 - When read() failed on a stream, we would close it without sending
19038 back an end. So 'connection refused' would simply be ignored and
19039 the user would get no response.
19040 - Stop a sigpipe: when an 'end' cell races with eof from the app,
19041 we shouldn't hold-open-until-flush if the eof arrived first.
19042 - Let resolve conns retry/expire also, rather than sticking around
19044 - Fix more dns related bugs: send back resolve_failed and end cells
19045 more reliably when the resolve fails, rather than closing the
19046 circuit and then trying to send the cell. Also attach dummy resolve
19047 connections to a circuit *before* calling dns_resolve(), to fix
19048 a bug where cached answers would never be sent in RESOLVED cells.
19050 o Bugfixes on 0.0.8.1 (Circuits):
19051 - Finally fix a bug that's been plaguing us for a year:
19052 With high load, circuit package window was reaching 0. Whenever
19053 we got a circuit-level sendme, we were reading a lot on each
19054 socket, but only writing out a bit. So we would eventually reach
19055 eof. This would be noticed and acted on even when there were still
19056 bytes sitting in the inbuf.
19057 - Use identity comparison, not nickname comparison, to choose which
19058 half of circuit-ID-space each side gets to use. This is needed
19059 because sometimes we think of a router as a nickname, and sometimes
19060 as a hex ID, and we can't predict what the other side will do.
19062 o Bugfixes on 0.0.8.1 (Other):
19063 - Fix a whole slew of memory leaks.
19064 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
19065 - If we are using select, make sure we stay within FD_SETSIZE.
19066 - When poll() is interrupted, we shouldn't believe the revents values.
19067 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
19068 and smartlist_len, which are two major profiling offenders.
19069 - If do_hup fails, actually notice.
19070 - Flush the log file descriptor after we print "Tor opening log file",
19071 so we don't see those messages days later.
19072 - Hidden service operators now correctly handle version 1 style
19073 INTRODUCE1 cells (nobody generates them still, so not a critical
19075 - Handle more errnos from accept() without closing the listener.
19076 Some OpenBSD machines were closing their listeners because
19077 they ran out of file descriptors.
19078 - Some people had wrapped their tor client/server in a script
19079 that would restart it whenever it died. This did not play well
19080 with our "shut down if your version is obsolete" code. Now people
19081 don't fetch a new directory if their local cached version is
19083 - Make our autogen.sh work on ksh as well as bash.
19084 - Better torrc example lines for dirbindaddress and orbindaddress.
19085 - Improved bounds checking on parsed ints (e.g. config options and
19086 the ones we find in directories.)
19087 - Stop using separate defaults for no-config-file and
19088 empty-config-file. Now you have to explicitly turn off SocksPort,
19089 if you don't want it open.
19090 - We were starting to daemonize before we opened our logs, so if
19091 there were any problems opening logs, we would complain to stderr,
19092 which wouldn't work, and then mysteriously exit.
19093 - If a verified OR connects to us before he's uploaded his descriptor,
19094 or we verify him and hup but he still has the original TLS
19095 connection, then conn->nickname is still set like he's unverified.
19097 o Code security improvements, inspired by Ilja:
19098 - tor_snprintf wrapper over snprintf with consistent (though not C99)
19100 - Replace sprintf with tor_snprintf. (I think they were all safe, but
19102 - Replace strcpy/strncpy with strlcpy in more places.
19103 - Avoid strcat; use tor_snprintf or strlcat instead.
19105 o Features (circuits and streams):
19106 - New circuit building strategy: keep a list of ports that we've
19107 used in the past 6 hours, and always try to have 2 circuits open
19108 or on the way that will handle each such port. Seed us with port
19109 80 so web users won't complain that Tor is "slow to start up".
19110 - Make kill -USR1 dump more useful stats about circuits.
19111 - When warning about retrying or giving up, print the address, so
19112 the user knows which one it's talking about.
19113 - If you haven't used a clean circuit in an hour, throw it away,
19114 just to be on the safe side. (This means after 6 hours a totally
19115 unused Tor client will have no circuits open.)
19116 - Support "foo.nickname.exit" addresses, to let Alice request the
19117 address "foo" as viewed by exit node "nickname". Based on a patch
19118 from Geoff Goodell.
19119 - If your requested entry or exit node has advertised bandwidth 0,
19121 - Be more greedy about filling up relay cells -- we try reading again
19122 once we've processed the stuff we read, in case enough has arrived
19123 to fill the last cell completely.
19124 - Refuse application socks connections to port 0.
19125 - Use only 0.0.9pre1 and later servers for resolve cells.
19127 o Features (bandwidth):
19128 - Hibernation: New config option "AccountingMax" lets you
19129 set how many bytes per month (in each direction) you want to
19130 allow your server to consume. Rather than spreading those
19131 bytes out evenly over the month, we instead hibernate for some
19132 of the month and pop up at a deterministic time, work until
19133 the bytes are consumed, then hibernate again. Config option
19134 "MonthlyAccountingStart" lets you specify which day of the month
19135 your billing cycle starts on.
19136 - Implement weekly/monthly/daily accounting: now you specify your
19137 hibernation properties by
19138 AccountingMax N bytes|KB|MB|GB|TB
19139 AccountingStart day|week|month [day] HH:MM
19140 Defaults to "month 1 0:00".
19141 - Let bandwidth and interval config options be specified as 5 bytes,
19142 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
19144 o Features (directories):
19145 - New "router-status" line in directory, to better bind each verified
19146 nickname to its identity key.
19147 - Clients can ask dirservers for /dir.z to get a compressed version
19148 of the directory. Only works for servers running 0.0.9, of course.
19149 - Make clients cache directories and use them to seed their router
19150 lists at startup. This means clients have a datadir again.
19151 - Respond to content-encoding headers by trying to uncompress as
19153 - Clients and servers now fetch running-routers; cache
19154 running-routers; compress running-routers; serve compressed
19156 - Make moria2 advertise a dirport of 80, so people behind firewalls
19157 will be able to get a directory.
19158 - Http proxy support
19159 - Dirservers translate requests for http://%s:%d/x to /x
19160 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
19161 be routed through this host.
19162 - Clients ask for /tor/x rather than /x for new enough dirservers.
19163 This way we can one day coexist peacefully with apache.
19164 - Clients specify a "Host: %s%d" http header, to be compatible
19165 with more proxies, and so running squid on an exit node can work.
19166 - Protect dirservers from overzealous descriptor uploading -- wait
19167 10 seconds after directory gets dirty, before regenerating.
19169 o Features (packages and install):
19170 - Add NSI installer contributed by J Doe.
19171 - Apply NT service patch from Osamu Fujino. Still needs more work.
19172 - Commit VC6 and VC7 workspace/project files.
19173 - Commit a tor.spec for making RPM files, with help from jbash.
19174 - Add contrib/torctl.in contributed by Glenn Fink.
19175 - Make expand_filename handle ~ and ~username.
19176 - Use autoconf to enable largefile support where necessary. Use
19177 ftello where available, since ftell can fail at 2GB.
19178 - Ship src/win32/ in the tarball, so people can use it to build.
19179 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
19182 o Features (ui controller):
19183 - Control interface: a separate program can now talk to your
19184 client/server over a socket, and get/set config options, receive
19185 notifications of circuits and streams starting/finishing/dying,
19186 bandwidth used, etc. The next step is to get some GUIs working.
19187 Let us know if you want to help out. See doc/control-spec.txt .
19188 - Ship a contrib/tor-control.py as an example script to interact
19189 with the control port.
19190 - "tor --hash-password zzyxz" will output a salted password for
19191 use in authenticating to the control interface.
19192 - Implement the control-spec's SAVECONF command, to write your
19193 configuration to torrc.
19194 - Get cookie authentication for the controller closer to working.
19195 - When set_conf changes our server descriptor, upload a new copy.
19196 But don't upload it too often if there are frequent changes.
19198 o Features (config and command-line):
19199 - Deprecate unofficial config option abbreviations, and abbreviations
19200 not on the command line.
19201 - Configuration infrastructure support for warning on obsolete
19203 - Give a slightly more useful output for "tor -h".
19204 - Break DirFetchPostPeriod into:
19205 - DirFetchPeriod for fetching full directory,
19206 - StatusFetchPeriod for fetching running-routers,
19207 - DirPostPeriod for posting server descriptor,
19208 - RendPostPeriod for posting hidden service descriptors.
19209 - New log format in config:
19210 "Log minsev[-maxsev] stdout|stderr|syslog" or
19211 "Log minsev[-maxsev] file /var/foo"
19212 - DirPolicy config option, to let people reject incoming addresses
19213 from their dirserver.
19214 - "tor --list-fingerprint" will list your identity key fingerprint
19216 - Make tor --version --version dump the cvs Id of every file.
19217 - New 'MyFamily nick1,...' config option for a server to
19218 specify other servers that shouldn't be used in the same circuit
19219 with it. Only believed if nick1 also specifies us.
19220 - New 'NodeFamily nick1,nick2,...' config option for a client to
19221 specify nodes that it doesn't want to use in the same circuit.
19222 - New 'Redirectexit pattern address:port' config option for a
19223 server to redirect exit connections, e.g. to a local squid.
19224 - Add "pass" target for RedirectExit, to make it easier to break
19225 out of a sequence of RedirectExit rules.
19226 - Make the dirservers file obsolete.
19227 - Include a dir-signing-key token in directories to tell the
19228 parsing entity which key is being used to sign.
19229 - Remove the built-in bulky default dirservers string.
19230 - New config option "Dirserver %s:%d [fingerprint]", which can be
19231 repeated as many times as needed. If no dirservers specified,
19232 default to moria1,moria2,tor26.
19233 - Make 'Routerfile' config option obsolete.
19234 - Discourage people from setting their dirfetchpostperiod more often
19235 than once per minute.
19237 o Features (other):
19238 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
19239 get back to normal.)
19240 - Accept *:706 (silc) in default exit policy.
19241 - Implement new versioning format for post 0.1.
19242 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
19243 log more informatively.
19244 - Check clock skew for verified servers, but allow unverified
19245 servers and clients to have any clock skew.
19246 - Make sure the hidden service descriptors are at a random offset
19247 from each other, to hinder linkability.
19248 - Clients now generate a TLS cert too, in preparation for having
19249 them act more like real nodes.
19250 - Add a pure-C tor-resolve implementation.
19251 - Use getrlimit and friends to ensure we can reach MaxConn (currently
19252 1024) file descriptors.
19253 - Raise the max dns workers from 50 to 100.
19256 Changes in version 0.0.8.1 - 2004-10-13
19258 - Fix a seg fault that can be triggered remotely for Tor
19259 clients/servers with an open dirport.
19260 - Fix a rare assert trigger, where routerinfos for entries in
19261 our cpath would expire while we're building the path.
19262 - Fix a bug in OutboundBindAddress so it (hopefully) works.
19263 - Fix a rare seg fault for people running hidden services on
19264 intermittent connections.
19265 - Fix a bug in parsing opt keywords with objects.
19266 - Fix a stale pointer assert bug when a stream detaches and
19268 - Fix a string format vulnerability (probably not exploitable)
19269 in reporting stats locally.
19270 - Fix an assert trigger: sometimes launching circuits can fail
19271 immediately, e.g. because too many circuits have failed recently.
19272 - Fix a compile warning on 64 bit platforms.
19275 Changes in version 0.0.8 - 2004-08-25
19277 - Made our unit tests compile again on OpenBSD 3.5, and tor
19278 itself compile again on OpenBSD on a sparc64.
19279 - We were neglecting milliseconds when logging on win32, so
19280 everything appeared to happen at the beginning of each second.
19281 - Check directory signature _before_ you decide whether you're
19282 you're running an obsolete version and should exit.
19283 - Check directory signature _before_ you parse the running-routers
19284 list to decide who's running.
19285 - Check return value of fclose while writing to disk, so we don't
19286 end up with broken files when servers run out of disk space.
19287 - Port it to SunOS 5.9 / Athena
19288 - Fix two bugs in saving onion keys to disk when rotating, so
19289 hopefully we'll get fewer people using old onion keys.
19290 - Remove our mostly unused -- and broken -- hex_encode()
19291 function. Use base16_encode() instead. (Thanks to Timo Lindfors
19292 for pointing out this bug.)
19293 - Only pick and establish intro points after we've gotten a
19295 - Fix assert triggers: if the other side returns an address 0.0.0.0,
19296 don't put it into the client dns cache.
19297 - If a begin failed due to exit policy, but we believe the IP
19298 address should have been allowed, switch that router to exitpolicy
19299 reject *:* until we get our next directory.
19301 o Protocol changes:
19302 - 'Extend' relay cell payloads now include the digest of the
19303 intended next hop's identity key. Now we can verify that we're
19304 extending to the right router, and also extend to routers we
19305 hadn't heard of before.
19308 - Tor nodes can now act as relays (with an advertised ORPort)
19309 without being manually verified by the dirserver operators.
19310 - Uploaded descriptors of unverified routers are now accepted
19311 by the dirservers, and included in the directory.
19312 - Verified routers are listed by nickname in the running-routers
19313 list; unverified routers are listed as "$<fingerprint>".
19314 - We now use hash-of-identity-key in most places rather than
19315 nickname or addr:port, for improved security/flexibility.
19316 - AllowUnverifiedNodes config option to let circuits choose no-name
19317 routers in entry,middle,exit,introduction,rendezvous positions.
19318 Allow middle and rendezvous positions by default.
19319 - When picking unverified routers, skip those with low uptime and/or
19320 low bandwidth, depending on what properties you care about.
19321 - ClientOnly option for nodes that never want to become servers.
19322 - Directory caching.
19323 - "AuthoritativeDir 1" option for the official dirservers.
19324 - Now other nodes (clients and servers) will cache the latest
19325 directory they've pulled down.
19326 - They can enable their DirPort to serve it to others.
19327 - Clients will pull down a directory from any node with an open
19328 DirPort, and check the signature/timestamp correctly.
19329 - Authoritative dirservers now fetch directories from other
19330 authdirservers, to stay better synced.
19331 - Running-routers list tells who's down also, along with noting
19332 if they're verified (listed by nickname) or unverified (listed
19334 - Allow dirservers to serve running-router list separately.
19335 This isn't used yet.
19336 - You can now fetch $DIRURL/running-routers to get just the
19337 running-routers line, not the whole descriptor list. (But
19338 clients don't use this yet.)
19339 - Clients choose nodes proportional to advertised bandwidth.
19340 - Clients avoid using nodes with low uptime as introduction points.
19341 - Handle servers with dynamic IP addresses: don't just replace
19342 options->Address with the resolved one at startup, and
19343 detect our address right before we make a routerinfo each time.
19344 - 'FascistFirewall' option to pick dirservers and ORs on specific
19345 ports; plus 'FirewallPorts' config option to tell FascistFirewall
19346 which ports are open. (Defaults to 80,443)
19347 - Try other dirservers immediately if the one you try is down. This
19348 should tolerate down dirservers better now.
19349 - ORs connect-on-demand to other ORs
19350 - If you get an extend cell to an OR you're not connected to,
19351 connect, handshake, and forward the create cell.
19352 - The authoritative dirservers stay connected to everybody,
19353 and everybody stays connected to 0.0.7 servers, but otherwise
19354 clients/servers expire unused connections after 5 minutes.
19355 - When servers get a sigint, they delay 30 seconds (refusing new
19356 connections) then exit. A second sigint causes immediate exit.
19357 - File and name management:
19358 - Look for .torrc if no CONFDIR "torrc" is found.
19359 - If no datadir is defined, then choose, make, and secure ~/.tor
19361 - If torrc not found, exitpolicy reject *:*.
19362 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
19363 - If no nickname is defined, derive default from hostname.
19364 - Rename secret key files, e.g. identity.key -> secret_id_key,
19365 to discourage people from mailing their identity key to tor-ops.
19366 - Refuse to build a circuit before the directory has arrived --
19367 it won't work anyway, since you won't know the right onion keys
19369 - Parse tor version numbers so we can do an is-newer-than check
19370 rather than an is-in-the-list check.
19371 - New socks command 'resolve', to let us shim gethostbyname()
19373 - A 'tor_resolve' script to access the socks resolve functionality.
19374 - A new socks-extensions.txt doc file to describe our
19375 interpretation and extensions to the socks protocols.
19376 - Add a ContactInfo option, which gets published in descriptor.
19377 - Write tor version at the top of each log file
19378 - New docs in the tarball:
19380 - Document that you should proxy your SSL traffic too.
19381 - Log a warning if the user uses an unsafe socks variant, so people
19382 are more likely to learn about privoxy or socat.
19383 - Log a warning if you're running an unverified server, to let you
19384 know you might want to get it verified.
19385 - Change the default exit policy to reject the default edonkey,
19386 kazaa, gnutella ports.
19387 - Add replace_file() to util.[ch] to handle win32's rename().
19388 - Publish OR uptime in descriptor (and thus in directory) too.
19389 - Remember used bandwidth (both in and out), and publish 15-minute
19390 snapshots for the past day into our descriptor.
19391 - Be more aggressive about trying to make circuits when the network
19392 has changed (e.g. when you unsuspend your laptop).
19393 - Check for time skew on http headers; report date in response to
19395 - If the entrynode config line has only one node, don't pick it as
19397 - Add strict{entry|exit}nodes config options. If set to 1, then
19398 we refuse to build circuits that don't include the specified entry
19400 - OutboundBindAddress config option, to bind to a specific
19401 IP address for outgoing connect()s.
19402 - End truncated log entries (e.g. directories) with "[truncated]".
19405 Changes in version 0.0.7.3 - 2004-08-12
19406 o Stop dnsworkers from triggering an assert failure when you
19407 ask them to resolve the host "".
19410 Changes in version 0.0.7.2 - 2004-07-07
19411 o A better fix for the 0.0.0.0 problem, that will hopefully
19412 eliminate the remaining related assertion failures.
19415 Changes in version 0.0.7.1 - 2004-07-04
19416 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
19417 since internally we use 0.0.0.0 to signify "not yet resolved".
19420 Changes in version 0.0.7 - 2004-06-07
19421 o Fixes for crashes and other obnoxious bugs:
19422 - Fix an epipe bug: sometimes when directory connections failed
19423 to connect, we would give them a chance to flush before closing
19425 - When we detached from a circuit because of resolvefailed, we
19426 would immediately try the same circuit twice more, and then
19427 give up on the resolve thinking we'd tried three different
19429 - Limit the number of intro circuits we'll attempt to build for a
19430 hidden service per 15-minute period.
19431 - Check recommended-software string *early*, before actually parsing
19432 the directory. Thus we can detect an obsolete version and exit,
19433 even if the new directory format doesn't parse.
19434 o Fixes for security bugs:
19435 - Remember which nodes are dirservers when you startup, and if a
19436 random OR enables his dirport, don't automatically assume he's
19437 a trusted dirserver.
19439 - Directory connections were asking the wrong poll socket to
19440 start writing, and not asking themselves to start writing.
19441 - When we detached from a circuit because we sent a begin but
19442 didn't get a connected, we would use it again the first time;
19443 but after that we would correctly switch to a different one.
19444 - Stop warning when the first onion decrypt attempt fails; they
19445 will sometimes legitimately fail now that we rotate keys.
19446 - Override unaligned-access-ok check when $host_cpu is ia64 or
19447 arm. Apparently they allow it but the kernel whines.
19448 - Dirservers try to reconnect periodically too, in case connections
19450 - Fix some memory leaks in directory servers.
19451 - Allow backslash in Win32 filenames.
19452 - Made Tor build complain-free on FreeBSD, hopefully without
19453 breaking other BSD builds. We'll see.
19454 - Check directory signatures based on name of signer, not on whom
19455 we got the directory from. This will let us cache directories more
19457 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
19460 - Doxygen markup on all functions and global variables.
19461 - Make directory functions update routerlist, not replace it. So
19462 now directory disagreements are not so critical a problem.
19463 - Remove the upper limit on number of descriptors in a dirserver's
19464 directory (not that we were anywhere close).
19465 - Allow multiple logfiles at different severity ranges.
19466 - Allow *BindAddress to specify ":port" rather than setting *Port
19467 separately. Allow multiple instances of each BindAddress config
19468 option, so you can bind to multiple interfaces if you want.
19469 - Allow multiple exit policy lines, which are processed in order.
19470 Now we don't need that huge line with all the commas in it.
19471 - Enable accept/reject policies on SOCKS connections, so you can bind
19472 to 0.0.0.0 but still control who can use your OP.
19473 - Updated the man page to reflect these features.
19476 Changes in version 0.0.6.2 - 2004-05-16
19477 o Our integrity-checking digest was checking only the most recent cell,
19478 not the previous cells like we'd thought.
19479 Thanks to Stefan Mark for finding the flaw!
19482 Changes in version 0.0.6.1 - 2004-05-06
19483 o Fix two bugs in our AES counter-mode implementation (this affected
19484 onion-level stream encryption, but not TLS-level). It turns
19485 out we were doing something much more akin to a 16-character
19486 polyalphabetic cipher. Oops.
19487 Thanks to Stefan Mark for finding the flaw!
19488 o Retire moria3 as a directory server, and add tor26 as a directory
19492 Changes in version 0.0.6 - 2004-05-02
19494 - Hidden services and rendezvous points are implemented. Go to
19495 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
19496 hidden services. (This only works via a socks4a proxy such as
19497 Privoxy, and currently it's quite slow.)
19498 - We now rotate link (tls context) keys and onion keys.
19499 - CREATE cells now include oaep padding, so you can tell
19500 if you decrypted them correctly.
19501 - Retry stream correctly when we fail to connect because of
19502 exit-policy-reject (should try another) or can't-resolve-address.
19503 - When we hup a dirserver and we've *removed* a server from the
19504 approved-routers list, now we remove that server from the
19505 in-memory directories too.
19506 - Add bandwidthburst to server descriptor.
19507 - Directories now say which dirserver signed them.
19508 - Use a tor_assert macro that logs failed assertions too.
19509 - Since we don't support truncateds much, don't bother sending them;
19510 just close the circ.
19511 - Fetch randomness from /dev/urandom better (not via fopen/fread)
19512 - Better debugging for tls errors
19513 - Set Content-Type on the directory and hidserv descriptor.
19514 - Remove IVs from cipher code, since AES-ctr has none.
19516 - Fix an assert trigger for exit nodes that's been plaguing us since
19517 the days of 0.0.2prexx (thanks weasel!)
19518 - Fix a bug where we were closing tls connections intermittently.
19519 It turns out openssl keeps its errors around -- so if an error
19520 happens, and you don't ask about it, and then another openssl
19521 operation happens and succeeds, and you ask if there was an error,
19522 it tells you about the first error.
19523 - Fix a bug that's been lurking since 27 may 03 (!)
19524 When passing back a destroy cell, we would use the wrong circ id.
19525 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
19526 - Some versions of openssl have an SSL_pending function that erroneously
19527 returns bytes when there is a non-application record pending.
19528 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
19529 o We were using an array of length zero in a few places.
19530 o Win32's gethostbyname can't resolve an IP to an IP.
19531 o Win32's close can't close a socket.
19532 o Handle windows socket errors correctly.
19534 - check for <sys/limits.h> so we build on FreeBSD again, and
19535 <machine/limits.h> for NetBSD.
19538 Changes in version 0.0.5 - 2004-03-30
19539 o Install torrc as torrc.sample -- we no longer clobber your
19541 o Fix mangled-state bug in directory fetching (was causing sigpipes).
19542 o Only build circuits after we've fetched the directory: clients were
19543 using only the directory servers before they'd fetched a directory.
19544 This also means longer startup time; so it goes.
19545 o Fix an assert trigger where an OP would fail to handshake, and we'd
19546 expect it to have a nickname.
19547 o Work around a tsocks bug: do a socks reject when AP connection dies
19548 early, else tsocks goes into an infinite loop.
19549 o Hold socks connection open until reply is flushed (if possible)
19550 o Make exit nodes resolve IPs to IPs immediately, rather than asking
19551 the dns farm to do it.
19552 o Fix c99 aliasing warnings in rephist.c
19553 o Don't include server descriptors that are older than 24 hours in the
19555 o Give socks 'reject' replies their whole 15s to attempt to flush,
19556 rather than seeing the 60s timeout and assuming the flush had failed.
19557 o Clean automake droppings from the cvs repository
19558 o Add in a 'notice' log level for things the operator should hear
19559 but that aren't warnings
19562 Changes in version 0.0.4 - 2004-03-26
19563 o When connecting to a dirserver or OR and the network is down,
19567 Changes in version 0.0.3 - 2004-03-26
19568 o Warn and fail if server chose a nickname with illegal characters
19569 o Port to Solaris and Sparc:
19570 - include missing header fcntl.h
19571 - have autoconf find -lsocket -lnsl automatically
19572 - deal with hardware word alignment
19573 - make uname() work (solaris has a different return convention)
19574 - switch from using signal() to sigaction()
19575 o Preliminary work on reputation system:
19576 - Keep statistics on success/fail of connect attempts; they're published
19577 by kill -USR1 currently.
19578 - Add a RunTesting option to try to learn link state by creating test
19579 circuits, even when SocksPort is off.
19580 - Remove unused open circuits when there are too many.
19583 Changes in version 0.0.2 - 2004-03-19
19584 - Include strlcpy and strlcat for safer string ops
19585 - define INADDR_NONE so we compile (but still not run) on solaris
19588 Changes in version 0.0.2pre27 - 2004-03-14
19590 - Allow internal tor networks (we were rejecting internal IPs,
19591 now we allow them if they're set explicitly).
19592 - And fix a few endian issues.
19595 Changes in version 0.0.2pre26 - 2004-03-14
19597 - If a stream times out after 15s without a connected cell, don't
19598 try that circuit again: try a new one.
19599 - Retry streams at most 4 times. Then give up.
19600 - When a dirserver gets a descriptor from an unknown router, it
19601 logs its fingerprint (so the dirserver operator can choose to
19602 accept it even without mail from the server operator).
19603 - Inform unapproved servers when we reject their descriptors.
19604 - Make tor build on Windows again. It works as a client, who knows
19606 - Clearer instructions in the torrc for how to set up a server.
19607 - Be more efficient about reading fd's when our global token bucket
19608 (used for rate limiting) becomes empty.
19610 - Stop asserting that computers always go forward in time. It's
19612 - When we sent a cell (e.g. destroy) and then marked an OR connection
19613 expired, we might close it before finishing a flush if the other
19614 side isn't reading right then.
19615 - Don't allow dirservers to start if they haven't defined
19616 RecommendedVersions
19617 - We were caching transient dns failures. Oops.
19618 - Prevent servers from publishing an internal IP as their address.
19619 - Address a strcat vulnerability in circuit.c
19622 Changes in version 0.0.2pre25 - 2004-03-04
19624 - Put the OR's IP in its router descriptor, not its fqdn. That way
19625 we'll stop being stalled by gethostbyname for nodes with flaky dns,
19628 - If the user typed in an address that didn't resolve, the server
19632 Changes in version 0.0.2pre24 - 2004-03-03
19634 - Fix an assertion failure in dns.c, where we were trying to dequeue
19635 a pending dns resolve even if it wasn't pending
19636 - Fix a spurious socks5 warning about still trying to write after the
19637 connection is finished.
19638 - Hold certain marked_for_close connections open until they're finished
19639 flushing, rather than losing bytes by closing them too early.
19640 - Correctly report the reason for ending a stream
19641 - Remove some duplicate calls to connection_mark_for_close
19642 - Put switch_id and start_daemon earlier in the boot sequence, so it
19643 will actually try to chdir() to options.DataDirectory
19644 - Make 'make test' exit(1) if a test fails; fix some unit tests
19645 - Make tor fail when you use a config option it doesn't know about,
19646 rather than warn and continue.
19647 - Make --version work
19648 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
19651 Changes in version 0.0.2pre23 - 2004-02-29
19653 - Print a statement when the first circ is finished, so the user
19654 knows it's working.
19655 - If a relay cell is unrecognized at the end of the circuit,
19656 send back a destroy. (So attacks to mutate cells are more
19658 - New config option 'excludenodes' to avoid certain nodes for circuits.
19659 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
19660 so you can collect coredumps there.
19662 - Fix a bug in tls flushing where sometimes data got wedged and
19663 didn't flush until more data got sent. Hopefully this bug was
19664 a big factor in the random delays we were seeing.
19665 - Make 'connected' cells include the resolved IP, so the client
19666 dns cache actually gets populated.
19667 - Disallow changing from ORPort=0 to ORPort>0 on hup.
19668 - When we time-out on a stream and detach from the circuit, send an
19669 end cell down it first.
19670 - Only warn about an unknown router (in exitnodes, entrynodes,
19671 excludenodes) after we've fetched a directory.
19674 Changes in version 0.0.2pre22 - 2004-02-26
19676 - Servers publish less revealing uname information in descriptors.
19677 - More memory tracking and assertions, to crash more usefully when
19679 - If the default torrc isn't there, just use some default defaults.
19680 Plus provide an internal dirservers file if they don't have one.
19681 - When the user tries to use Tor as an http proxy, give them an http
19682 501 failure explaining that we're a socks proxy.
19683 - Dump a new router.desc on hup, to help confused people who change
19684 their exit policies and then wonder why router.desc doesn't reflect
19686 - Clean up the generic tor.sh init script that we ship with.
19688 - If the exit stream is pending on the resolve, and a destroy arrives,
19689 then the stream wasn't getting removed from the pending list. I
19690 think this was the one causing recent server crashes.
19691 - Use a more robust poll on OSX 10.3, since their poll is flaky.
19692 - When it couldn't resolve any dirservers, it was useless from then on.
19693 Now it reloads the RouterFile (or default dirservers) if it has no
19695 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
19696 many users don't even *have* a /usr/local/sbin/.
19699 Changes in version 0.0.2pre21 - 2004-02-18
19701 - There's a ChangeLog file that actually reflects the changelog.
19702 - There's a 'torify' wrapper script, with an accompanying
19703 tor-tsocks.conf, that simplifies the process of using tsocks for
19704 tor. It even has a man page.
19705 - The tor binary gets installed to sbin rather than bin now.
19706 - Retry streams where the connected cell hasn't arrived in 15 seconds
19707 - Clean up exit policy handling -- get the default out of the torrc,
19708 so we can update it without forcing each server operator to fix
19710 - Allow imaps and pop3s in default exit policy
19712 - Prevent picking middleman nodes as the last node in the circuit
19715 Changes in version 0.0.2pre20 - 2004-01-30
19717 - We now have a deb package, and it's in debian unstable. Go to
19718 it, apt-getters. :)
19719 - I've split the TotalBandwidth option into BandwidthRate (how many
19720 bytes per second you want to allow, long-term) and
19721 BandwidthBurst (how many bytes you will allow at once before the cap
19722 kicks in). This better token bucket approach lets you, say, set
19723 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
19724 performance while not exceeding your monthly bandwidth quota.
19725 - Push out a tls record's worth of data once you've got it, rather
19726 than waiting until you've read everything waiting to be read. This
19727 may improve performance by pipelining better. We'll see.
19728 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
19729 from failed circuits (if they haven't been connected yet) and attach
19731 - Expire old streams that haven't managed to connect. Some day we'll
19732 have them reattach to new circuits instead.
19735 - Fix several memory leaks that were causing servers to become bloated
19737 - Fix a few very rare assert triggers. A few more remain.
19738 - Setuid to User _before_ complaining about running as root.
19741 Changes in version 0.0.2pre19 - 2004-01-07
19743 - Fix deadlock condition in dns farm. We were telling a child to die by
19744 closing the parent's file descriptor to him. But newer children were
19745 inheriting the open file descriptor from the parent, and since they
19746 weren't closing it, the socket never closed, so the child never read
19747 eof, so he never knew to exit. Similarly, dns workers were holding
19748 open other sockets, leading to all sorts of chaos.
19749 - New cleaner daemon() code for forking and backgrounding.
19750 - If you log to a file, it now prints an entry at the top of the
19751 logfile so you know it's working.
19752 - The onionskin challenge length was 30 bytes longer than necessary.
19753 - Started to patch up the spec so it's not quite so out of date.
19756 Changes in version 0.0.2pre18 - 2004-01-02
19758 - Fix endian issues with the 'integrity' field in the relay header.
19759 - Fix a potential bug where connections in state
19760 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
19763 Changes in version 0.0.2pre17 - 2003-12-30
19765 - Made --debuglogfile (or any second log file, actually) work.
19766 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
19767 adversary could force us into an infinite loop.
19770 - Each onionskin handshake now includes a hash of the computed key,
19771 to prove the server's identity and help perfect forward secrecy.
19772 - Changed cell size from 256 to 512 bytes (working toward compatibility
19774 - Changed cell length to 2 bytes, and moved it to the relay header.
19775 - Implemented end-to-end integrity checking for the payloads of
19777 - Separated streamid from 'recognized' (otherwise circuits will get
19778 messed up when we try to have streams exit from the middle). We
19779 use the integrity-checking to confirm that a cell is addressed to
19781 - Randomize the initial circid and streamid values, so an adversary who
19782 breaks into a node can't learn how many circuits or streams have
19786 Changes in version 0.0.2pre16 - 2003-12-14
19788 - Fixed a bug that made HUP trigger an assert
19789 - Fixed a bug where a circuit that immediately failed wasn't being
19790 counted as a failed circuit in counting retries.
19793 - Now we close the circuit when we get a truncated cell: otherwise we're
19794 open to an anonymity attack where a bad node in the path truncates
19795 the circuit and then we open streams at him.
19796 - Add port ranges to exit policies
19797 - Add a conservative default exit policy
19798 - Warn if you're running tor as root
19799 - on HUP, retry OR connections and close/rebind listeners
19800 - options.EntryNodes: try these nodes first when picking the first node
19801 - options.ExitNodes: if your best choices happen to include any of
19802 your preferred exit nodes, you choose among just those preferred
19804 - options.ExcludedNodes: nodes that are never picked in path building
19807 Changes in version 0.0.2pre15 - 2003-12-03
19808 o Robustness and bugfixes:
19809 - Sometimes clients would cache incorrect DNS resolves, which would
19810 really screw things up.
19811 - An OP that goes offline would slowly leak all its sockets and stop
19813 - A wide variety of bugfixes in exit node selection, exit policy
19814 handling, and processing pending streams when a new circuit is
19816 - Pick nodes for a path only from those the directory says are up
19817 - Choose randomly from all running dirservers, not always the first one
19818 - Increase allowed http header size for directory fetch.
19819 - Stop writing to stderr (if we're daemonized it will be closed).
19820 - Enable -g always, so cores will be more useful to me.
19821 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
19824 - Wrote a man page. It lists commonly used options.
19827 - Change default loglevel to warn.
19828 - Make PidFile default to null rather than littering in your CWD.
19829 - OnionRouter config option is now obsolete. Instead it just checks
19831 - Moved to a single unified torrc file for both clients and servers.
19834 Changes in version 0.0.2pre14 - 2003-11-29
19835 o Robustness and bugfixes:
19836 - Force the admin to make the DataDirectory himself
19837 - to get ownership/permissions right
19838 - so clients no longer make a DataDirectory and then never use it
19839 - fix bug where a client who was offline for 45 minutes would never
19840 pull down a directory again
19841 - fix (or at least hide really well) the dns assert bug that was
19842 causing server crashes
19843 - warnings and improved robustness wrt clockskew for certs
19844 - use the native daemon(3) to daemonize, when available
19845 - exit if bind() fails
19846 - exit if neither socksport nor orport is defined
19847 - include our own tor_timegm (Win32 doesn't have its own)
19848 - bugfix for win32 with lots of connections
19849 - fix minor bias in PRNG
19850 - make dirserver more robust to corrupt cached directory
19853 - Wrote the design document (woo)
19855 o Circuit building and exit policies:
19856 - Circuits no longer try to use nodes that the directory has told them
19858 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
19859 bitcounts (18.0.0.0/8).
19860 - Make AP connections standby for a circuit if no suitable circuit
19861 exists, rather than failing
19862 - Circuits choose exit node based on addr/port, exit policies, and
19863 which AP connections are standing by
19864 - Bump min pathlen from 2 to 3
19865 - Relay end cells have a payload to describe why the stream ended.
19866 - If the stream failed because of exit policy, try again with a new
19868 - Clients have a dns cache to remember resolved addresses.
19869 - Notice more quickly when we have no working circuits
19872 - APPort is now called SocksPort
19873 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
19875 - RecommendedVersions is now a config variable rather than
19876 hardcoded (for dirservers)
19877 - Reloads config on HUP
19878 - Usage info on -h or --help
19879 - If you set User and Group config vars, it'll setu/gid to them.
19881 Changes in version 0.0.2pre13 - 2003-10-19
19882 o General stability:
19883 - SSL_write no longer fails when it returns WANTWRITE and the number
19884 of bytes in the buf has changed by the next SSL_write call.
19885 - Fix segfault fetching directory when network is down
19886 - Fix a variety of minor memory leaks
19887 - Dirservers reload the fingerprints file on HUP, so I don't have
19888 to take down the network when I approve a new router
19889 - Default server config file has explicit Address line to specify fqdn
19892 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
19893 - Make listener connections not ever alloc bufs
19895 o Autoconf improvements:
19896 - don't clobber an external CFLAGS in ./configure
19897 - Make install now works
19898 - create var/lib/tor on make install
19899 - autocreate a tor.sh initscript to help distribs
19900 - autocreate the torrc and sample-server-torrc with correct paths
19902 o Log files and Daemonizing now work:
19903 - If --DebugLogFile is specified, log to it at -l debug
19904 - If --LogFile is specified, use it instead of commandline
19905 - If --RunAsDaemon is set, tor forks and backgrounds on startup