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.3.9 - 2018-07-13
6 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
7 bridge relays should upgrade.
9 o Directory authority changes:
10 - The "Bifroest" bridge authority has been retired; the new bridge
11 authority is "Serge", and it is operated by George from the
12 TorBSD project. Closes ticket 26771.
15 Changes in version 0.3.2.11 - 2018-07-13
16 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
17 bridge relays should upgrade. We also take this opportunity to backport
20 o Directory authority changes:
21 - The "Bifroest" bridge authority has been retired; the new bridge
22 authority is "Serge", and it is operated by George from the
23 TorBSD project. Closes ticket 26771.
25 o Directory authority changes (backport from 0.3.3.7):
26 - Add an IPv6 address for the "dannenberg" directory authority.
29 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
30 - When directory authorities read a zero-byte bandwidth file, they
31 would previously log a warning with the contents of an
32 uninitialised buffer. They now log a warning about the empty file
33 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
35 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
36 - Correctly detect when onion services get disabled after HUP. Fixes
37 bug 25761; bugfix on 0.3.2.1.
39 o Minor features (sandbox, backport from 0.3.3.4-alpha):
40 - Explicitly permit the poll() system call when the Linux
41 seccomp2-based sandbox is enabled: apparently, some versions of
42 libc use poll() when calling getpwnam(). Closes ticket 25313.
44 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
45 - Update the Travis CI configuration to use the stable Rust channel,
46 now that we have decided to require that. Closes ticket 25714.
48 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
49 - Our .travis.yml configuration now includes support for testing the
50 results of "make distcheck". (It's not uncommon for "make check"
51 to pass but "make distcheck" to fail.) Closes ticket 25814.
52 - Our Travis CI configuration now integrates with the Coveralls
53 coverage analysis tool. Closes ticket 25818.
55 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
56 - Add several checks to detect whether Tor relays are uploading
57 their descriptors without specifying why they regenerated them.
58 Diagnostic for ticket 25686.
60 o Minor features (compilation, backport from 0.3.4.4-rc):
61 - When building Tor, prefer to use Python 3 over Python 2, and more
62 recent (contemplated) versions over older ones. Closes
65 o Minor features (geoip):
66 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
67 Country database. Closes ticket 26674.
69 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
70 - Upon receiving a malformed connected cell, stop processing the
71 cell immediately. Previously we would mark the connection for
72 close, but continue processing the cell as if the connection were
73 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
75 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
76 - Allow the nanosleep() system call, which glibc uses to implement
77 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
79 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
80 - When running the hs_ntor_ref.py test, make sure only to pass
81 strings (rather than "bytes" objects) to the Python subprocess
82 module. Python 3 on Windows seems to require this. Fixes bug
83 26535; bugfix on 0.3.1.1-alpha.
84 - When running the ntor_ref.py test, make sure only to pass strings
85 (rather than "bytes" objects) to the Python subprocess module.
86 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
89 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
90 - Work around a change in OpenSSL 1.1.1 where return values that
91 would previously indicate "no password" now indicate an empty
92 password. Without this workaround, Tor instances running with
93 OpenSSL 1.1.1 would accept descriptors that other Tor instances
94 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
96 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
97 - Document that the PerConnBW{Rate,Burst} options will fall back to
98 their corresponding consensus parameters only if those parameters
99 are set. Previously we had claimed that these values would always
100 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
102 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
103 - Fix a compilation warning on some versions of GCC when building
104 code that calls routerinfo_get_my_routerinfo() twice, assuming
105 that the second call will succeed if the first one did. Fixes bug
106 26269; bugfix on 0.2.8.2-alpha.
108 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
109 - Don't consider Tor running as a client if the ControlPort is open,
110 but no actual client ports are open. Fixes bug 26062; bugfix
113 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
114 - Prevent a possible out-of-bounds smartlist read in
115 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
117 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
118 - Fix a very unlikely (impossible, we believe) null pointer
119 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
120 Coverity; this is CID 1430932.
122 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
123 - Fix a memory leak when a v3 onion service is configured and gets a
124 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
125 - When parsing the descriptor signature, look for the token plus an
126 extra white-space at the end. This is more correct but also will
127 allow us to support new fields that might start with "signature".
128 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
130 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
131 - Relays now correctly block attempts to re-extend to the previous
132 relay by Ed25519 identity. Previously they would warn in this
133 case, but not actually reject the attempt. Fixes bug 26158; bugfix
136 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
137 - Avoid a crash when running with DirPort set but ORPort turned off.
138 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
140 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
141 - Silence unused-const-variable warnings in zstd.h with some GCC
142 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
144 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
145 - Avoid intermittent test failures due to a test that had relied on
146 onion service introduction point creation finishing within 5
147 seconds of real clock time. Fixes bug 25450; bugfix
150 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
151 - Fix a C99 compliance issue in our configuration script that caused
152 compilation issues when compiling Tor with certain versions of
153 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
155 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
156 - Fix a number of small memory leaks identified by coverity. Fixes
157 bug 26467; bugfix on numerous Tor versions.
159 o Code simplification and refactoring (backport from 0.3.3.5-rc):
160 - Move the list of default directory authorities to its own file.
161 Closes ticket 24854. Patch by "beastr0".
164 Changes in version 0.2.9.16 - 2018-07-13
165 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
166 bridge relays should upgrade. We also take this opportunity to backport
169 o Directory authority changes:
170 - The "Bifroest" bridge authority has been retired; the new bridge
171 authority is "Serge", and it is operated by George from the
172 TorBSD project. Closes ticket 26771.
174 o Directory authority changes (backport from 0.3.3.7):
175 - Add an IPv6 address for the "dannenberg" directory authority.
178 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
179 - When directory authorities read a zero-byte bandwidth file, they
180 would previously log a warning with the contents of an
181 uninitialised buffer. They now log a warning about the empty file
182 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
184 o Minor features (sandbox, backport from 0.3.3.4-alpha):
185 - Explicitly permit the poll() system call when the Linux
186 seccomp2-based sandbox is enabled: apparently, some versions of
187 libc use poll() when calling getpwnam(). Closes ticket 25313.
189 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
190 - Our .travis.yml configuration now includes support for testing the
191 results of "make distcheck". (It's not uncommon for "make check"
192 to pass but "make distcheck" to fail.) Closes ticket 25814.
193 - Our Travis CI configuration now integrates with the Coveralls
194 coverage analysis tool. Closes ticket 25818.
196 o Minor features (compilation, backport from 0.3.4.4-rc):
197 - When building Tor, prefer to use Python 3 over Python 2, and more
198 recent (contemplated) versions over older ones. Closes
201 o Minor features (geoip):
202 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
203 Country database. Closes ticket 26674.
205 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
206 - Upon receiving a malformed connected cell, stop processing the
207 cell immediately. Previously we would mark the connection for
208 close, but continue processing the cell as if the connection were
209 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
211 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
212 - Allow the nanosleep() system call, which glibc uses to implement
213 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
215 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
216 - When running the ntor_ref.py test, make sure only to pass strings
217 (rather than "bytes" objects) to the Python subprocess module.
218 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
221 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
222 - Work around a change in OpenSSL 1.1.1 where return values that
223 would previously indicate "no password" now indicate an empty
224 password. Without this workaround, Tor instances running with
225 OpenSSL 1.1.1 would accept descriptors that other Tor instances
226 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
228 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
229 - Fix a compilation warning on some versions of GCC when building
230 code that calls routerinfo_get_my_routerinfo() twice, assuming
231 that the second call will succeed if the first one did. Fixes bug
232 26269; bugfix on 0.2.8.2-alpha.
234 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
235 - Don't consider Tor running as a client if the ControlPort is open,
236 but no actual client ports are open. Fixes bug 26062; bugfix
239 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
240 - Prevent a possible out-of-bounds smartlist read in
241 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
243 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
244 - Fix a very unlikely (impossible, we believe) null pointer
245 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
246 Coverity; this is CID 1430932.
248 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
249 - Fix a number of small memory leaks identified by coverity. Fixes
250 bug 26467; bugfix on numerous Tor versions.
252 o Code simplification and refactoring (backport from 0.3.3.5-rc):
253 - Move the list of default directory authorities to its own file.
254 Closes ticket 24854. Patch by "beastr0".
257 Changes in version 0.3.3.8 - 2018-07-09
258 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
259 fixes for a memory leak affecting directory authorities.
261 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
262 - Stop leaking memory on directory authorities when planning to
263 vote. This bug was crashing authorities by exhausting their
264 memory. Fixes bug 26435; bugfix on 0.3.3.6.
266 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
267 - Make sure that failing tests in Rust will actually cause the build
268 to fail: previously, they were ignored. Fixes bug 26258; bugfix
271 o Minor features (compilation, backport from 0.3.4.4-rc):
272 - When building Tor, prefer to use Python 3 over Python 2, and more
273 recent (contemplated) versions over older ones. Closes
276 o Minor features (geoip):
277 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
278 Country database. Closes ticket 26674.
280 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
281 - Add several checks to detect whether Tor relays are uploading
282 their descriptors without specifying why they regenerated them.
283 Diagnostic for ticket 25686.
285 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
286 - Don't count path selection failures as circuit build failures.
287 This change should eliminate cases where Tor blames its guard or
288 the network for situations like insufficient microdescriptors
289 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
292 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
293 - Fix a compilation warning on some versions of GCC when building
294 code that calls routerinfo_get_my_routerinfo() twice, assuming
295 that the second call will succeed if the first one did. Fixes bug
296 26269; bugfix on 0.2.8.2-alpha.
298 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
299 - Handle the HSADDRESS= argument to the HSPOST command properly.
300 (Previously, this argument was misparsed and thus ignored.) Fixes
301 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
303 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
304 - Fix a number of small memory leaks identified by coverity. Fixes
305 bug 26467; bugfix on numerous Tor versions.
307 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
308 - Relays now correctly block attempts to re-extend to the previous
309 relay by Ed25519 identity. Previously they would warn in this
310 case, but not actually reject the attempt. Fixes bug 26158; bugfix
313 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
314 - When shutting down, Tor now clears all the flags in the control.c
315 module. This should prevent a bug where authentication cookies are
316 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
318 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
319 - When running the hs_ntor_ref.py test, make sure only to pass
320 strings (rather than "bytes" objects) to the Python subprocess
321 module. Python 3 on Windows seems to require this. Fixes bug
322 26535; bugfix on 0.3.1.1-alpha.
323 - When running the ntor_ref.py test, make sure only to pass strings
324 (rather than "bytes" objects) to the Python subprocess module.
325 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
329 Changes in version 0.3.3.7 - 2018-06-12
330 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
331 fixes for bugs affecting compatibility and stability.
333 o Directory authority changes:
334 - Add an IPv6 address for the "dannenberg" directory authority.
337 o Minor features (geoip):
338 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
339 Country database. Closes ticket 26351.
341 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
342 - Work around a change in OpenSSL 1.1.1 where return values that
343 would previously indicate "no password" now indicate an empty
344 password. Without this workaround, Tor instances running with
345 OpenSSL 1.1.1 would accept descriptors that other Tor instances
346 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
348 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
349 - Silence unused-const-variable warnings in zstd.h with some GCC
350 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
352 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
353 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
354 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
355 miscounting the total number of circuits for these field values.)
356 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
358 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
359 - Prevent a possible out-of-bounds smartlist read in
360 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
362 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
363 - Only select relays when they have the descriptors we prefer to use
364 for them. This change fixes a bug where we could select a relay
365 because it had _some_ descriptor, but reject it later with a
366 nonfatal assertion error because it didn't have the exact one we
367 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
370 Changes in version 0.3.3.6 - 2018-05-22
371 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
372 backports several important fixes from the 0.3.4.1-alpha.
374 The Tor 0.3.3 series includes controller support and other
375 improvements for v3 onion services, official support for embedding Tor
376 within other applications, and our first non-trivial module written in
377 the Rust programming language. (Rust is still not enabled by default
378 when building Tor.) And as usual, there are numerous other smaller
379 bugfixes, features, and improvements.
381 Below are the changes since 0.3.2.10. For a list of only the changes
382 since 0.3.3.5-rc, see the ChangeLog file.
384 o New system requirements:
385 - When built with Rust, Tor now depends on version 0.2.39 of the
386 libc crate. Closes tickets 25310 and 25664.
388 o Major features (embedding):
389 - There is now a documented stable API for programs that need to
390 embed Tor. See tor_api.h for full documentation and known bugs.
392 - Tor now has support for restarting in the same process.
393 Controllers that run Tor using the "tor_api.h" interface can now
394 restart Tor after Tor has exited. This support is incomplete,
395 however: we fixed crash bugs that prevented it from working at
396 all, but many bugs probably remain, including a possibility of
397 security issues. Implements ticket 24581.
399 o Major features (IPv6, directory documents):
400 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
401 consensus. This information makes it easier for IPv6 clients to
402 bootstrap and choose reachable entry guards. Implements
404 - Add consensus method 28, which removes IPv6 ORPorts from
405 microdescriptors. Now that the consensus contains IPv6 ORPorts,
406 they are redundant in microdescs. This change will be used by Tor
407 clients on 0.2.8.x and later. (That is to say, with all Tor
408 clients that have IPv6 bootstrap and guard support.) Implements
410 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
411 set by different numbers of authorities. Fixes 23870
414 o Major features (onion service v3, control port):
415 - The control port now supports commands and events for v3 onion
416 services. It is now possible to create ephemeral v3 services using
417 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
418 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
419 DEL_ONION) have been extended to support v3 onion services. Closes
420 ticket 20699; implements proposal 284.
422 o Major features (onion services):
423 - Provide torrc options to pin the second and third hops of onion
424 service circuits to a list of nodes. The option HSLayer2Guards
425 pins the second hop, and the option HSLayer3Guards pins the third
426 hop. These options are for use in conjunction with experiments
427 with "vanguards" for preventing guard enumeration attacks. Closes
429 - When v3 onion service clients send introduce cells, they now
430 include the IPv6 address of the rendezvous point, if it has one.
431 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
432 in future Tor versions, IPv6-only v3 single onion services will be
433 able to use IPv6 addresses to connect directly to the rendezvous
434 point. Closes ticket 23577. Patch by Neel Chauhan.
436 o Major features (relay):
437 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
438 operator to use a more reasonable ("reduced") exit policy, rather
439 than the default one. If you want to run an exit node without
440 thinking too hard about which ports to allow, this one is for you.
441 Closes ticket 13605. Patch from Neel Chauhan.
443 o Major features (rust, portability, experimental):
444 - Tor now ships with an optional implementation of one of its
445 smaller modules (protover.c) in the Rust programming language. To
446 try it out, install a Rust build environment, and configure Tor
447 with "--enable-rust --enable-cargo-online-mode". This should not
448 cause any user-visible changes, but should help us gain more
449 experience with Rust, and plan future Rust integration work.
450 Implementation by Chelsea Komlo. Closes ticket 22840.
452 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
453 - When directory authorities read a zero-byte bandwidth file, they
454 would previously log a warning with the contents of an
455 uninitialised buffer. They now log a warning about the empty file
456 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
458 o Major bugfixes (security, directory authority, denial-of-service):
459 - Fix a bug that could have allowed an attacker to force a directory
460 authority to use up all its RAM by passing it a maliciously
461 crafted protocol versions string. Fixes bug 25517; bugfix on
462 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
464 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
465 - Avoid a rare assertion failure in the circuit build timeout code
466 if we fail to allow any circuits to actually complete. Fixes bug
467 25733; bugfix on 0.2.2.2-alpha.
469 o Major bugfixes (netflow padding):
470 - Stop adding unneeded channel padding right after we finish
471 flushing to a connection that has been trying to flush for many
472 seconds. Instead, treat all partial or complete flushes as
473 activity on the channel, which will defer the time until we need
474 to add padding. This fix should resolve confusing and scary log
475 messages like "Channel padding timeout scheduled 221453ms in the
476 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
478 o Major bugfixes (networking):
479 - Tor will no longer reject IPv6 address strings from Tor Browser
480 when they are passed as hostnames in SOCKS5 requests. Fixes bug
481 25036, bugfix on Tor 0.3.1.2.
483 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
484 - Correctly detect when onion services get disabled after HUP. Fixes
485 bug 25761; bugfix on 0.3.2.1.
487 o Major bugfixes (performance, load balancing):
488 - Directory authorities no longer vote in favor of the Guard flag
489 for relays without directory support. Starting in Tor
490 0.3.0.1-alpha, clients have been avoiding using such relays in the
491 Guard position, leading to increasingly broken load balancing for
492 the 5%-or-so of Guards that don't advertise directory support.
493 Fixes bug 22310; bugfix on 0.3.0.6.
495 o Major bugfixes (relay):
496 - If we have failed to connect to a relay and received a connection
497 refused, timeout, or similar error (at the TCP level), do not try
498 that same address/port again for 60 seconds after the failure has
499 occurred. Fixes bug 24767; bugfix on 0.0.6.
501 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
502 - Impose a limit on circuit cell queue size. The limit can be
503 controlled by a consensus parameter. Fixes bug 25226; bugfix
506 o Minor features (cleanup):
507 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
508 when it stops. Closes ticket 23271.
510 o Minor features (compatibility, backport from 0.3.4.1-alpha):
511 - Avoid some compilation warnings with recent versions of LibreSSL.
514 o Minor features (config options):
515 - Change the way the default value for MaxMemInQueues is calculated.
516 We now use 40% of the hardware RAM if the system has 8 GB RAM or
517 more. Otherwise we use the former value of 75%. Closes
520 o Minor features (continuous integration):
521 - Update the Travis CI configuration to use the stable Rust channel,
522 now that we have decided to require that. Closes ticket 25714.
524 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
525 - Our .travis.yml configuration now includes support for testing the
526 results of "make distcheck". (It's not uncommon for "make check"
527 to pass but "make distcheck" to fail.) Closes ticket 25814.
528 - Our Travis CI configuration now integrates with the Coveralls
529 coverage analysis tool. Closes ticket 25818.
531 o Minor features (defensive programming):
532 - Most of the functions in Tor that free objects have been replaced
533 with macros that free the objects and set the corresponding
534 pointers to NULL. This change should help prevent a large class of
535 dangling pointer bugs. Closes ticket 24337.
536 - Where possible, the tor_free() macro now only evaluates its input
537 once. Part of ticket 24337.
538 - Check that microdesc ed25519 ids are non-zero in
539 node_get_ed25519_id() before returning them. Implements ticket
540 24001, patch by "aruna1234".
542 o Minor features (directory authority):
543 - When directory authorities are unable to add signatures to a
544 pending consensus, log the reason why. Closes ticket 24849.
546 o Minor features (embedding):
547 - Tor can now start with a preauthenticated control connection
548 created by the process that launched it. This feature is meant for
549 use by programs that want to launch and manage a Tor process
550 without allowing other programs to manage it as well. For more
551 information, see the __OwningControllerFD option documented in
552 control-spec.txt. Closes ticket 23900.
553 - On most errors that would cause Tor to exit, it now tries to
554 return from the tor_main() function, rather than calling the
555 system exit() function. Most users won't notice a difference here,
556 but it should be significant for programs that run Tor inside a
557 separate thread: they should now be able to survive Tor's exit
558 conditions rather than having Tor shut down the entire process.
560 - Applications that want to embed Tor can now tell Tor not to
561 register any of its own POSIX signal handlers, using the
562 __DisableSignalHandlers option. Closes ticket 24588.
564 o Minor features (fallback directory list):
565 - Avoid selecting fallbacks that change their IP addresses too
566 often. Select more fallbacks by ignoring the Guard flag, and
567 allowing lower cutoffs for the Running and V2Dir flags. Also allow
568 a lower bandwidth, and a higher number of fallbacks per operator
569 (5% of the list). Implements ticket 24785.
570 - Update the fallback whitelist and blacklist based on opt-ins and
571 relay changes. Closes tickets 22321, 24678, 22527, 24135,
574 o Minor features (fallback directory mirror configuration):
575 - Add a nickname to each fallback in a C comment. This makes it
576 easier for operators to find their relays, and allows stem to use
577 nicknames to identify fallbacks. Implements ticket 24600.
578 - Add a type and version header to the fallback directory mirror
579 file. Also add a delimiter to the end of each fallback entry. This
580 helps external parsers like stem and Relay Search. Implements
582 - Add an extrainfo cache flag for each fallback in a C comment. This
583 allows stem to use fallbacks to fetch extra-info documents, rather
584 than using authorities. Implements ticket 22759.
585 - Add the generateFallbackDirLine.py script for automatically
586 generating fallback directory mirror lines from relay fingerprints.
587 No more typos! Add the lookupFallbackDirContact.py script for
588 automatically looking up operator contact info from relay
589 fingerprints. Implements ticket 24706, patch by teor and atagar.
590 - Reject any fallback directory mirror that serves an expired
591 consensus. Implements ticket 20942, patch by "minik".
592 - Remove commas and equals signs from external string inputs to the
593 fallback list. This avoids format confusion attacks. Implements
595 - Remove the "weight=10" line from fallback directory mirror
596 entries. Ticket 24681 will maintain the current fallback weights
597 by changing Tor's default fallback weight to 10. Implements
599 - Stop logging excessive information about fallback netblocks.
600 Implements ticket 24791.
602 o Minor features (forward-compatibility):
603 - If a relay supports some link authentication protocol that we do
604 not recognize, then include that relay's ed25519 key when telling
605 other relays to extend to it. Previously, we treated future
606 versions as if they were too old to support ed25519 link
607 authentication. Closes ticket 20895.
609 o Minor features (geoip):
610 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
611 database. Closes ticket 26104.
613 o Minor features (heartbeat):
614 - Add onion service information to our heartbeat logs, displaying
615 stats about the activity of configured onion services. Closes
618 o Minor features (instrumentation, development):
619 - Add the MainloopStats option to allow developers to get
620 instrumentation information from the main event loop via the
621 heartbeat messages. We hope to use this to improve Tor's behavior
622 when it's trying to sleep. Closes ticket 24605.
624 o Minor features (IPv6):
625 - Make IPv6-only clients wait for microdescs for relays, even if we
626 were previously using descriptors (or were using them as a bridge)
627 and have a cached descriptor for them. Implements ticket 23827.
628 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
629 them, rather than waiting to download microdescriptors. Implements
632 o Minor features (log messages):
633 - Improve log message in the out-of-memory handler to include
634 information about memory usage from the different compression
635 backends. Closes ticket 25372.
636 - Improve a warning message that happens when we fail to re-parse an
637 old router because of an expired certificate. Closes ticket 20020.
638 - Make the log more quantitative when we hit MaxMemInQueues
639 threshold exposing some values. Closes ticket 24501.
641 o Minor features (logging):
642 - Clarify the log messages produced when getrandom() or a related
643 entropy-generation mechanism gives an error. Closes ticket 25120.
644 - Added support for the Android logging subsystem. Closes
647 o Minor features (performance):
648 - Support predictive circuit building for onion service circuits
649 with multiple layers of guards. Closes ticket 23101.
650 - Use stdatomic.h where available, rather than mutexes, to implement
651 atomic_counter_t. Closes ticket 23953.
653 o Minor features (performance, 32-bit):
654 - Improve performance on 32-bit systems by avoiding 64-bit division
655 when calculating the timestamp in milliseconds for channel padding
656 computations. Implements ticket 24613.
657 - Improve performance on 32-bit systems by avoiding 64-bit division
658 when timestamping cells and buffer chunks for OOM calculations.
659 Implements ticket 24374.
661 o Minor features (performance, OSX, iOS):
662 - Use the mach_approximate_time() function (when available) to
663 implement coarse monotonic time. Having a coarse time function
664 should avoid a large number of system calls, and improve
665 performance slightly, especially under load. Closes ticket 24427.
667 o Minor features (performance, windows):
668 - Improve performance on Windows Vista and Windows 7 by adjusting
669 TCP send window size according to the recommendation from
670 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
673 o Minor features (sandbox):
674 - Explicitly permit the poll() system call when the Linux
675 seccomp2-based sandbox is enabled: apparently, some versions of
676 libc use poll() when calling getpwnam(). Closes ticket 25313.
678 o Minor features (storage, configuration):
679 - Users can store cached directory documents somewhere other than
680 the DataDirectory by using the CacheDirectory option. Similarly,
681 the storage location for relay's keys can be overridden with the
682 KeyDirectory option. Closes ticket 22703.
684 o Minor features (testing):
685 - Add a "make test-rust" target to run the rust tests only. Closes
688 o Minor features (testing, debugging, embedding):
689 - For development purposes, Tor now has a mode in which it runs for
690 a few seconds, then stops, and starts again without exiting the
691 process. This mode is meant to help us debug various issues with
692 ticket 23847. To use this feature, compile with
693 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
694 environment variable. This is expected to crash a lot, and is
695 really meant for developers only. It will likely be removed in a
696 future release. Implements ticket 24583.
698 o Minor bugfixes (build, rust):
699 - Fix output of autoconf checks to display success messages for Rust
700 dependencies and a suitable rustc compiler version. Fixes bug
701 24612; bugfix on 0.3.1.3-alpha.
702 - Don't pass the --quiet option to cargo: it seems to suppress some
703 errors, which is not what we want to do when building. Fixes bug
704 24518; bugfix on 0.3.1.7.
705 - Build correctly when building from outside Tor's source tree with
706 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
709 o Minor bugfixes (C correctness):
710 - Fix a very unlikely (impossible, we believe) null pointer
711 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
712 Coverity; this is CID 1430932.
714 o Minor bugfixes (channel, client):
715 - Better identify client connection when reporting to the geoip
716 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
718 o Minor bugfixes (circuit, cannibalization):
719 - Don't cannibalize preemptively-built circuits if we no longer
720 recognize their first hop. This situation can happen if our Guard
721 relay went off the consensus after the circuit was created. Fixes
722 bug 24469; bugfix on 0.0.6.
724 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
725 - Don't consider Tor running as a client if the ControlPort is open,
726 but no actual client ports are open. Fixes bug 26062; bugfix
729 o Minor bugfixes (compilation):
730 - Fix a C99 compliance issue in our configuration script that caused
731 compilation issues when compiling Tor with certain versions of
732 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
734 o Minor bugfixes (controller):
735 - Restore the correct operation of the RESOLVE command, which had
736 been broken since we added the ability to enable/disable DNS on
737 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
738 - Avoid a (nonfatal) assertion failure when extending a one-hop
739 circuit from the controller to become a multihop circuit. Fixes
740 bug 24903; bugfix on 0.2.5.2-alpha.
742 o Minor bugfixes (correctness):
743 - Remove a nonworking, unnecessary check to see whether a circuit
744 hop's identity digest was set when the circuit failed. Fixes bug
745 24927; bugfix on 0.2.4.4-alpha.
747 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
748 - Upon receiving a malformed connected cell, stop processing the
749 cell immediately. Previously we would mark the connection for
750 close, but continue processing the cell as if the connection were
751 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
753 o Minor bugfixes (directory authorities, IPv6):
754 - When creating a routerstatus (vote) from a routerinfo (descriptor),
755 set the IPv6 address to the unspecified IPv6 address, and
756 explicitly initialize the port to zero. Fixes bug 24488; bugfix
759 o Minor bugfixes (documentation):
760 - Document that the PerConnBW{Rate,Burst} options will fall back to
761 their corresponding consensus parameters only if those parameters
762 are set. Previously we had claimed that these values would always
763 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
765 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
766 - Stop saying in the manual that clients cache ipv4 dns answers from
767 exit relays. We haven't used them since 0.2.6.3-alpha, and in
768 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
769 we forgot to say so in the man page. Fixes bug 26052; bugfix
772 o Minor bugfixes (exit relay DNS retries):
773 - Re-attempt timed-out DNS queries 3 times before failure, since our
774 timeout is 5 seconds for them, but clients wait 10-15. Also allow
775 slightly more timeouts per resolver when an exit has multiple
776 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
778 o Minor bugfixes (fallback directory mirrors):
779 - Make updateFallbackDirs.py search harder for python. (Some OSs
780 don't put it in /usr/bin.) Fixes bug 24708; bugfix
783 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
784 - When hibernating, close connections normally and allow them to
785 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
787 - Do not attempt to launch self-reachability tests when entering
788 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
789 - Resolve several bugs related to descriptor fetching on bridge
790 clients with bandwidth accounting enabled. (This combination is
791 not recommended!) Fixes a case of bug 12062; bugfix
793 - When hibernating, do not attempt to launch DNS checks. Fixes a
794 case of bug 12062; bugfix on 0.1.2.2-alpha.
795 - When hibernating, do not try to upload or download descriptors.
796 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
798 o Minor bugfixes (IPv6, bridges):
799 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
800 bugfix on 0.2.8.2-alpha.
801 - Tor now sets IPv6 address in the routerstatus as well as in the
802 router descriptors when updating addresses for a bridge. Closes
803 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
805 o Minor bugfixes (Linux seccomp2 sandbox):
806 - When running with the sandbox enabled, reload configuration files
807 correctly even when %include was used. Previously we would crash.
808 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
810 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
811 - Allow the nanosleep() system call, which glibc uses to implement
812 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
814 o Minor bugfixes (logging):
815 - Fix a (mostly harmless) race condition when invoking
816 LOG_PROTOCOL_WARN message from a subthread while the torrc options
817 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
819 o Minor bugfixes (man page, SocksPort):
820 - Remove dead code from the old "SocksSocket" option, and rename
821 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old
822 option still works, but is deprecated. Fixes bug 24343; bugfix
825 o Minor bugfixes (memory leaks):
826 - Avoid possible at-exit memory leaks related to use of Libevent's
827 event_base_once() function. (This function tends to leak memory if
828 the event_base is closed before the event fires.) Fixes bug 24584;
829 bugfix on 0.2.8.1-alpha.
830 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
833 o Minor bugfixes (network IPv6 test):
834 - Tor's test scripts now check if "ping -6 ::1" works when the user
835 runs "make test-network-all". Fixes bug 24677; bugfix on
836 0.2.9.3-alpha. Patch by "ffmancera".
838 o Minor bugfixes (networking):
839 - string_is_valid_hostname() will not consider IP strings to be
840 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
842 o Minor bugfixes (onion service v3):
843 - Avoid an assertion failure when the next onion service descriptor
844 rotation type is out of sync with the consensus's valid-after
845 time. Instead, log a warning message with extra information, so we
846 can better hunt down the cause of this assertion. Fixes bug 25306;
847 bugfix on 0.3.2.1-alpha.
849 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
850 - Fix a memory leak when a v3 onion service is configured and gets a
851 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
852 - When parsing the descriptor signature, look for the token plus an
853 extra white-space at the end. This is more correct but also will
854 allow us to support new fields that might start with "signature".
855 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
857 o Minor bugfixes (onion services):
858 - If we are configured to offer a single onion service, don't log
859 long-term established one hop rendezvous points in the heartbeat.
860 Fixes bug 25116; bugfix on 0.2.9.6-rc.
862 o Minor bugfixes (performance):
863 - Reduce the number of circuits that will be opened at once during
864 the circuit build timeout phase. This is done by increasing the
865 idle timeout to 3 minutes, and lowering the maximum number of
866 concurrent learning circuits to 10. Fixes bug 24769; bugfix
868 - Avoid calling protocol_list_supports_protocol() from inside tight
869 loops when running with cached routerinfo_t objects. Instead,
870 summarize the relevant protocols as flags in the routerinfo_t, as
871 we do for routerstatus_t objects. This change simplifies our code
872 a little, and saves a large amount of short-term memory allocation
873 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
875 o Minor bugfixes (performance, timeouts):
876 - Consider circuits for timeout as soon as they complete a hop. This
877 is more accurate than applying the timeout in
878 circuit_expire_building() because that function is only called
879 once per second, which is now too slow for typical timeouts on the
880 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
881 - Use onion service circuits (and other circuits longer than 3 hops)
882 to calculate a circuit build timeout. Previously, Tor only
883 calculated its build timeout based on circuits that planned to be
884 exactly 3 hops long. With this change, we include measurements
885 from all circuits at the point where they complete their third
886 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
888 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
889 - Avoid a crash when running with DirPort set but ORPort turned off.
890 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
892 o Minor bugfixes (Rust FFI):
893 - Fix a minor memory leak which would happen whenever the C code
894 would call the Rust implementation of
895 protover_get_supported_protocols(). This was due to the C version
896 returning a static string, whereas the Rust version newly allocated
897 a CString to pass across the FFI boundary. Consequently, the C
898 code was not expecting to need to free() what it was given. Fixes
899 bug 25127; bugfix on 0.3.2.1-alpha.
901 o Minor bugfixes (spelling):
902 - Use the "misspell" tool to detect and fix typos throughout the
903 source code. Fixes bug 23650; bugfix on various versions of Tor.
904 Patch from Deepesh Pathak.
906 o Minor bugfixes (testing):
907 - Avoid intermittent test failures due to a test that had relied on
908 onion service introduction point creation finishing within 5
909 seconds of real clock time. Fixes bug 25450; bugfix
911 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
912 bugfix on 0.2.3.1-alpha.
914 o Minor bugfixes (unit test, monotonic time):
915 - Increase a constant (1msec to 10msec) in the monotonic time test
916 that makes sure the nsec/usec/msec times read are synchronized.
917 This change was needed to accommodate slow systems like armel or
918 when the clock_gettime() is not a VDSO on the running kernel.
919 Fixes bug 25113; bugfix on 0.2.9.1.
921 o Code simplification and refactoring:
922 - Move the list of default directory authorities to its own file.
923 Closes ticket 24854. Patch by "beastr0".
924 - Remove the old (deterministic) directory retry logic entirely:
925 We've used exponential backoff exclusively for some time. Closes
927 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
929 - Remove a series of counters used to track circuit extend attempts
930 and connection status but that in reality we aren't using for
931 anything other than stats logged by a SIGUSR1 signal. Closes
933 - Remove /usr/athena from search path in configure.ac. Closes
935 - Remove duplicate code in node_has_curve25519_onion_key() and
936 node_get_curve25519_onion_key(), and add a check for a zero
937 microdesc curve25519 onion key. Closes ticket 23966, patch by
938 "aruna1234" and teor.
939 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
940 memory allocations with large numbers of OR connections (e.g.
941 relays). Closes ticket 24119.
942 - Separate the function that deletes ephemeral files when Tor
944 - Small changes to Tor's buf_t API to make it suitable for use as a
945 general-purpose safe string constructor. Closes ticket 22342.
946 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
947 avoid source code identifier confusion. Closes ticket 24467.
948 - The tor_git_revision[] constant no longer needs to be redeclared
949 by everything that links against the rest of Tor. Done as part of
950 ticket 23845, to simplify our external API.
951 - We make extend_info_from_node() use node_get_curve25519_onion_key()
952 introduced in ticket 23577 to access the curve25519 public keys
953 rather than accessing it directly. Closes ticket 23760. Patch by
955 - Add a function to log channels' scheduler state changes to aid
956 debugging efforts. Closes ticket 24531.
959 - Improved the documentation of AccountingStart parameter. Closes
961 - Update the documentation for "Log" to include the current list of
962 logging domains. Closes ticket 25378.
963 - Add documentation on how to build tor with Rust dependencies
964 without having to be online. Closes ticket 22907; bugfix
966 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
967 traffic. Closes ticket 24318.
968 - Document that OutboundBindAddress doesn't apply to DNS requests.
969 Closes ticket 22145. Patch from Aruna Maurya.
971 o Code simplification and refactoring (channels):
972 - Remove the incoming and outgoing channel queues. These were never
973 used, but still took up a step in our fast path.
974 - The majority of the channel unit tests have been rewritten and the
975 code coverage has now been raised to 83.6% for channel.c. Closes
977 - Remove other dead code from the channel subsystem: All together,
978 this cleanup has removed more than 1500 lines of code overall and
979 adding very little except for unit test.
981 o Code simplification and refactoring (circuit rendezvous):
982 - Split the client-side rendezvous circuit lookup into two
983 functions: one that returns only established circuits and another
984 that returns all kinds of circuits. Closes ticket 23459.
986 o Code simplification and refactoring (controller):
987 - Make most of the variables in networkstatus_getinfo_by_purpose()
988 const. Implements ticket 24489.
990 o Documentation (backport from 0.3.4.1-alpha):
991 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
992 ticket 25857. Patch from "CTassisF".
994 o Documentation (man page):
995 - The HiddenServiceVersion torrc option accepts only one number:
996 either version 2 or 3. Closes ticket 25026; bugfix
999 o Documentation (manpage, denial of service):
1000 - Provide more detail about the denial-of-service options, by
1001 listing each mitigation and explaining how they relate. Closes
1005 Changes in version 0.3.1.10 - 2018-03-03
1006 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
1009 It includes an important security fix for a remote crash attack
1010 against directory authorities, tracked as TROVE-2018-001.
1012 This release also backports our new system for improved resistance to
1013 denial-of-service attacks against relays.
1015 This release also fixes several minor bugs and annoyances from
1018 All directory authorities should upgrade to one of the versions
1019 released today. Relays running 0.3.1.x may wish to update to one of
1020 the versions released today, for the DoS mitigations.
1022 Please note: according to our release calendar, Tor 0.3.1 will no
1023 longer be supported after 1 July 2018. If you will be running Tor
1024 after that date, you should make sure to plan to upgrade to the latest
1025 stable version, or downgrade to 0.2.9 (which will receive long-term
1028 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1029 - Fix a protocol-list handling bug that could be used to remotely crash
1030 directory authorities with a null-pointer exception. Fixes bug 25074;
1031 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1034 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
1035 - Give relays some defenses against the recent network overload. We
1036 start with three defenses (default parameters in parentheses).
1037 First: if a single client address makes too many concurrent
1038 connections (>100), hang up on further connections. Second: if a
1039 single client address makes circuits too quickly (more than 3 per
1040 second, with an allowed burst of 90) while also having too many
1041 connections open (3), refuse new create cells for the next while
1042 (1-2 hours). Third: if a client asks to establish a rendezvous
1043 point to you directly, ignore the request. These defenses can be
1044 manually controlled by new torrc options, but relays will also
1045 take guidance from consensus parameters, so there's no need to
1046 configure anything manually. Implements ticket 24902.
1048 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
1049 - Update the sandbox rules so that they should now work correctly
1050 with Glibc 2.26. Closes ticket 24315.
1052 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
1053 - Fix an "off by 2" error in counting rendezvous failures on the
1054 onion service side. While we thought we would stop the rendezvous
1055 attempt after one failed circuit, we were actually making three
1056 circuit attempts before giving up. Now switch to a default of 2,
1057 and allow the consensus parameter "hs_service_max_rdv_failures" to
1058 override. Fixes bug 24895; bugfix on 0.0.6.
1060 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
1061 - Add Link protocol version 5 to the supported protocols list. Fixes
1062 bug 25070; bugfix on 0.3.1.1-alpha.
1064 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
1065 - Fix a set of false positives where relays would consider
1066 connections to other relays as being client-only connections (and
1067 thus e.g. deserving different link padding schemes) if those
1068 relays fell out of the consensus briefly. Now we look only at the
1069 initial handshake and whether the connection authenticated as a
1070 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1072 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
1073 - Make our OOM handler aware of the geoip client history cache so it
1074 doesn't fill up the memory. This check is important for IPv6 and
1075 our DoS mitigation subsystem. Closes ticket 25122.
1077 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
1078 - Change relay bandwidth reporting stats interval from 4 hours to 24
1079 hours in order to reduce the efficiency of guard discovery
1080 attacks. Fixes ticket 23856.
1082 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
1083 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1084 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1085 since they neither disabled TLS 1.3 nor enabled any of the
1086 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1087 Closes ticket 24978.
1089 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
1090 - The fallback directory list has been re-generated based on the
1091 current status of the network. Tor uses fallback directories to
1092 bootstrap when it doesn't yet have up-to-date directory
1093 information. Closes ticket 24801.
1094 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1095 prefer to bootstrap from fallback directory mirrors. This is a
1096 follow-up to 24679, which removed weights from the default
1097 fallbacks. Implements ticket 24681.
1099 o Minor features (geoip):
1100 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1103 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
1104 - Use the actual observed address of an incoming relay connection,
1105 not the canonical address of the relay from its descriptor, when
1106 making decisions about how to handle the incoming connection.
1107 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1109 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
1110 - Directory authorities, when refusing a descriptor from a rejected
1111 relay, now explicitly tell the relay (in its logs) to set a valid
1112 ContactInfo address and contact the bad-relays@ mailing list.
1113 Fixes bug 25170; bugfix on 0.2.9.1.
1115 o Minor bugfixes (address selection, backport from 0.3.2.9):
1116 - When the fascist_firewall_choose_address_ functions don't find a
1117 reachable address, set the returned address to the null address
1118 and port. This is a precautionary measure, because some callers do
1119 not check the return value. Fixes bug 24736; bugfix
1122 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
1123 - Fetch descriptors aggressively whenever we lack enough to build
1124 circuits, regardless of how many descriptors we are missing.
1125 Previously, we would delay launching the fetch when we had fewer
1126 than 15 missing descriptors, even if some of those descriptors
1127 were blocking circuits from building. Fixes bug 23985; bugfix on
1128 0.1.1.11-alpha. The effects of this bug became worse in
1129 0.3.0.3-alpha, when we began treating missing descriptors from our
1130 primary guards as a reason to delay circuits.
1131 - Don't try fetching microdescriptors from relays that have failed
1132 to deliver them in the past. Fixes bug 23817; bugfix
1135 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
1136 - Fix a signed/unsigned comparison warning introduced by our fix to
1137 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1139 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
1140 - Avoid a crash when attempting to use the seccomp2 sandbox together
1141 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1144 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1145 - Fix a possible crash on malformed consensus. If a consensus had
1146 contained an unparseable protocol line, it could have made clients
1147 and relays crash with a null-pointer exception. To exploit this
1148 issue, however, an attacker would need to be able to subvert the
1149 directory authority system. Fixes bug 25251; bugfix on
1150 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1152 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
1153 - Recover better from empty or corrupt files in the consensus cache
1154 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
1155 - When a consensus diff calculation is only partially successful,
1156 only record the successful parts as having succeeded. Partial
1157 success can happen if (for example) one compression method fails
1158 but the others succeed. Previously we misrecorded all the
1159 calculations as having succeeded, which would later cause a
1160 nonfatal assertion failure. Fixes bug 24086; bugfix
1163 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
1164 - Tor now updates its guard state when it reads a consensus
1165 regardless of whether it's missing descriptors. That makes tor use
1166 its primary guards to fetch descriptors in some edge cases where
1167 it would previously have used fallback directories. Fixes bug
1168 23862; bugfix on 0.3.0.1-alpha.
1170 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
1171 - Don't treat inability to store a cached consensus object as a bug:
1172 it can happen normally when we are out of disk space. Fixes bug
1173 24859; bugfix on 0.3.1.1-alpha.
1175 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
1176 - When queuing DESTROY cells on a channel, only queue the circuit-id
1177 and reason fields: not the entire 514-byte cell. This fix should
1178 help mitigate any bugs or attacks that fill up these queues, and
1179 free more RAM for other uses. Fixes bug 24666; bugfix
1182 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
1183 - When closing a connection via close_connection_immediately(), we
1184 mark it as "not blocked on bandwidth", to prevent later calls from
1185 trying to unblock it, and give it permission to read. This fixes a
1186 backtrace warning that can happen on relays under various
1187 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1189 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
1190 - When selecting relays by bandwidth, avoid a rounding error that
1191 could sometimes cause load to be imbalanced incorrectly.
1192 Previously, we would always round upwards; now, we round towards
1193 the nearest integer. This had the biggest effect when a relay's
1194 weight adjustments should have given it weight 0, but it got
1195 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1196 - When calculating the fraction of nodes that have descriptors, and
1197 all nodes in the network have zero bandwidths, count the number of
1198 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1199 - Actually log the total bandwidth in compute_weighted_bandwidths().
1200 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1202 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
1203 - Improve the performance of our consensus-diff application code
1204 when Tor is built with the --enable-fragile-hardening option set.
1205 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1207 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
1208 - Don't exit the Tor process if setrlimit() fails to change the file
1209 limit (which can happen sometimes on some versions of OSX). Fixes
1210 bug 21074; bugfix on 0.0.9pre5.
1212 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
1213 - Fix a bug in the bit-counting parts of our timing-wheel code on
1214 MSVC. (Note that MSVC is still not a supported build platform, due
1215 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
1218 o Minor bugfixes (relay, partial backport):
1219 - Make the internal channel_is_client() function look at what sort
1220 of connection handshake the other side used, rather than whether
1221 the other side ever sent a create_fast cell to us. Backports part
1222 of the fixes from bugs 22805 and 24898.
1224 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1225 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1227 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1228 bugfix on 0.2.9.4-alpha.
1230 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
1231 - Update the "rust dependencies" submodule to be a project-level
1232 repository, rather than a user repository. Closes ticket 25323.
1235 Changes in version 0.2.9.15 - 2018-03-03
1236 Tor 0.2.9.15 backports important security and stability bugfixes from
1239 It includes an important security fix for a remote crash attack
1240 against directory authorities, tracked as TROVE-2018-001.
1242 This release also backports our new system for improved resistance to
1243 denial-of-service attacks against relays.
1245 This release also fixes several minor bugs and annoyances from
1248 All directory authorities should upgrade to one of the versions
1249 released today. Relays running 0.2.9.x may wish to update to one of
1250 the versions released today, for the DoS mitigations.
1252 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1253 - Fix a protocol-list handling bug that could be used to remotely crash
1254 directory authorities with a null-pointer exception. Fixes bug 25074;
1255 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1258 o Major features (denial-of-service mitigation):
1259 - Give relays some defenses against the recent network overload. We
1260 start with three defenses (default parameters in parentheses).
1261 First: if a single client address makes too many concurrent
1262 connections (>100), hang up on further connections. Second: if a
1263 single client address makes circuits too quickly (more than 3 per
1264 second, with an allowed burst of 90) while also having too many
1265 connections open (3), refuse new create cells for the next while
1266 (1-2 hours). Third: if a client asks to establish a rendezvous
1267 point to you directly, ignore the request. These defenses can be
1268 manually controlled by new torrc options, but relays will also
1269 take guidance from consensus parameters, so there's no need to
1270 configure anything manually. Implements ticket 24902.
1272 o Major bugfixes (bootstrapping):
1273 - Fetch descriptors aggressively whenever we lack enough to build
1274 circuits, regardless of how many descriptors we are missing.
1275 Previously, we would delay launching the fetch when we had fewer
1276 than 15 missing descriptors, even if some of those descriptors
1277 were blocking circuits from building. Fixes bug 23985; bugfix on
1278 0.1.1.11-alpha. The effects of this bug became worse in
1279 0.3.0.3-alpha, when we began treating missing descriptors from our
1280 primary guards as a reason to delay circuits.
1282 o Major bugfixes (onion services, retry behavior):
1283 - Fix an "off by 2" error in counting rendezvous failures on the
1284 onion service side. While we thought we would stop the rendezvous
1285 attempt after one failed circuit, we were actually making three
1286 circuit attempts before giving up. Now switch to a default of 2,
1287 and allow the consensus parameter "hs_service_max_rdv_failures" to
1288 override. Fixes bug 24895; bugfix on 0.0.6.
1290 o Minor feature (relay statistics):
1291 - Change relay bandwidth reporting stats interval from 4 hours to 24
1292 hours in order to reduce the efficiency of guard discovery
1293 attacks. Fixes ticket 23856.
1295 o Minor features (compatibility, OpenSSL):
1296 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1297 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1298 since they neither disabled TLS 1.3 nor enabled any of the
1299 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1300 Closes ticket 24978.
1302 o Minor features (denial-of-service avoidance):
1303 - Make our OOM handler aware of the geoip client history cache so it
1304 doesn't fill up the memory. This check is important for IPv6 and
1305 our DoS mitigation subsystem. Closes ticket 25122.
1307 o Minor features (fallback directory mirrors):
1308 - The fallback directory list has been re-generated based on the
1309 current status of the network. Tor uses fallback directories to
1310 bootstrap when it doesn't yet have up-to-date directory
1311 information. Closes ticket 24801.
1312 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1313 prefer to bootstrap from fallback directory mirrors. This is a
1314 follow-up to 24679, which removed weights from the default
1315 fallbacks. Implements ticket 24681.
1317 o Minor features (geoip):
1318 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1321 o Minor features (linux seccomp2 sandbox):
1322 - Update the sandbox rules so that they should now work correctly
1323 with Glibc 2.26. Closes ticket 24315.
1325 o Minor bugfix (channel connection):
1326 - Use the actual observed address of an incoming relay connection,
1327 not the canonical address of the relay from its descriptor, when
1328 making decisions about how to handle the incoming connection.
1329 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1331 o Minor bugfix (directory authority):
1332 - Directory authorities, when refusing a descriptor from a rejected
1333 relay, now explicitly tell the relay (in its logs) to set a valid
1334 ContactInfo address and contact the bad-relays@ mailing list.
1335 Fixes bug 25170; bugfix on 0.2.9.1.
1337 o Minor bugfixes (address selection):
1338 - When the fascist_firewall_choose_address_ functions don't find a
1339 reachable address, set the returned address to the null address
1340 and port. This is a precautionary measure, because some callers do
1341 not check the return value. Fixes bug 24736; bugfix
1344 o Minor bugfixes (compilation):
1345 - Fix a signed/unsigned comparison warning introduced by our fix to
1346 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1348 o Minor bugfixes (control port, linux seccomp2 sandbox):
1349 - Avoid a crash when attempting to use the seccomp2 sandbox together
1350 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1353 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1354 - Fix a possible crash on malformed consensus. If a consensus had
1355 contained an unparseable protocol line, it could have made clients
1356 and relays crash with a null-pointer exception. To exploit this
1357 issue, however, an attacker would need to be able to subvert the
1358 directory authority system. Fixes bug 25251; bugfix on
1359 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1361 o Minor bugfixes (memory usage):
1362 - When queuing DESTROY cells on a channel, only queue the circuit-id
1363 and reason fields: not the entire 514-byte cell. This fix should
1364 help mitigate any bugs or attacks that fill up these queues, and
1365 free more RAM for other uses. Fixes bug 24666; bugfix
1368 o Minor bugfixes (network layer):
1369 - When closing a connection via close_connection_immediately(), we
1370 mark it as "not blocked on bandwidth", to prevent later calls from
1371 trying to unblock it, and give it permission to read. This fixes a
1372 backtrace warning that can happen on relays under various
1373 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1375 o Minor bugfixes (OSX):
1376 - Don't exit the Tor process if setrlimit() fails to change the file
1377 limit (which can happen sometimes on some versions of OSX). Fixes
1378 bug 21074; bugfix on 0.0.9pre5.
1380 o Minor bugfixes (path selection):
1381 - When selecting relays by bandwidth, avoid a rounding error that
1382 could sometimes cause load to be imbalanced incorrectly.
1383 Previously, we would always round upwards; now, we round towards
1384 the nearest integer. This had the biggest effect when a relay's
1385 weight adjustments should have given it weight 0, but it got
1386 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1387 - When calculating the fraction of nodes that have descriptors, and
1388 all nodes in the network have zero bandwidths, count the number of
1389 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1390 - Actually log the total bandwidth in compute_weighted_bandwidths().
1391 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1393 o Minor bugfixes (portability, msvc):
1394 - Fix a bug in the bit-counting parts of our timing-wheel code on
1395 MSVC. (Note that MSVC is still not a supported build platform, due
1396 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
1399 o Minor bugfixes (relay):
1400 - Make the internal channel_is_client() function look at what sort
1401 of connection handshake the other side used, rather than whether
1402 the other side ever sent a create_fast cell to us. Backports part
1403 of the fixes from bugs 22805 and 24898.
1405 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1406 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1408 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1409 bugfix on 0.2.9.4-alpha.
1412 Changes in version 0.3.2.10 - 2018-03-03
1413 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
1414 backports a number of bugfixes, including important fixes for security
1417 It includes an important security fix for a remote crash attack
1418 against directory authorities, tracked as TROVE-2018-001.
1420 Additionally, it backports a fix for a bug whose severity we have
1421 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
1422 triggered in order to crash relays with a use-after-free pattern. As
1423 such, we are now tracking that bug as TROVE-2018-002 and
1424 CVE-2018-0491, and backporting it to earlier releases. This bug
1425 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
1428 This release also backports our new system for improved resistance to
1429 denial-of-service attacks against relays.
1431 This release also fixes several minor bugs and annoyances from
1434 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
1435 today, for the fix to TROVE-2018-002. Directory authorities should
1436 also upgrade. (Relays on earlier versions might want to update too for
1437 the DoS mitigations.)
1439 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1440 - Fix a protocol-list handling bug that could be used to remotely crash
1441 directory authorities with a null-pointer exception. Fixes bug 25074;
1442 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1445 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
1446 - Avoid adding the same channel twice in the KIST scheduler pending
1447 list, which could lead to remote denial-of-service use-after-free
1448 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
1450 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
1451 - Give relays some defenses against the recent network overload. We
1452 start with three defenses (default parameters in parentheses).
1453 First: if a single client address makes too many concurrent
1454 connections (>100), hang up on further connections. Second: if a
1455 single client address makes circuits too quickly (more than 3 per
1456 second, with an allowed burst of 90) while also having too many
1457 connections open (3), refuse new create cells for the next while
1458 (1-2 hours). Third: if a client asks to establish a rendezvous
1459 point to you directly, ignore the request. These defenses can be
1460 manually controlled by new torrc options, but relays will also
1461 take guidance from consensus parameters, so there's no need to
1462 configure anything manually. Implements ticket 24902.
1464 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
1465 - Fix an "off by 2" error in counting rendezvous failures on the
1466 onion service side. While we thought we would stop the rendezvous
1467 attempt after one failed circuit, we were actually making three
1468 circuit attempts before giving up. Now switch to a default of 2,
1469 and allow the consensus parameter "hs_service_max_rdv_failures" to
1470 override. Fixes bug 24895; bugfix on 0.0.6.
1471 - New-style (v3) onion services now obey the "max rendezvous circuit
1472 attempts" logic. Previously they would make as many rendezvous
1473 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
1474 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
1476 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
1477 - Add Link protocol version 5 to the supported protocols list. Fixes
1478 bug 25070; bugfix on 0.3.1.1-alpha.
1480 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
1481 - Fix a set of false positives where relays would consider
1482 connections to other relays as being client-only connections (and
1483 thus e.g. deserving different link padding schemes) if those
1484 relays fell out of the consensus briefly. Now we look only at the
1485 initial handshake and whether the connection authenticated as a
1486 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1488 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
1489 - The scheduler subsystem was failing to promptly notice changes in
1490 consensus parameters, making it harder to switch schedulers
1491 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
1493 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
1494 - Make our OOM handler aware of the geoip client history cache so it
1495 doesn't fill up the memory. This check is important for IPv6 and
1496 our DoS mitigation subsystem. Closes ticket 25122.
1498 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
1499 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1500 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1501 since they neither disabled TLS 1.3 nor enabled any of the
1502 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1503 Closes ticket 24978.
1505 o Minor features (geoip):
1506 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1509 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
1510 - When logging a failure to create an onion service's descriptor,
1511 also log what the problem with the descriptor was. Diagnostic
1514 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
1515 - Use the actual observed address of an incoming relay connection,
1516 not the canonical address of the relay from its descriptor, when
1517 making decisions about how to handle the incoming connection.
1518 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1520 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1521 - Fix a possible crash on malformed consensus. If a consensus had
1522 contained an unparseable protocol line, it could have made clients
1523 and relays crash with a null-pointer exception. To exploit this
1524 issue, however, an attacker would need to be able to subvert the
1525 directory authority system. Fixes bug 25251; bugfix on
1526 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1528 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
1529 - Directory authorities, when refusing a descriptor from a rejected
1530 relay, now explicitly tell the relay (in its logs) to set a valid
1531 ContactInfo address and contact the bad-relays@ mailing list.
1532 Fixes bug 25170; bugfix on 0.2.9.1.
1534 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
1535 - When building with Rust on OSX, link against libresolv, to work
1536 around the issue at https://github.com/rust-lang/rust/issues/46797.
1537 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
1539 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
1540 - Remove a BUG() statement when a client fetches an onion descriptor
1541 that has a lower revision counter than the one in its cache. This
1542 can happen in normal circumstances due to HSDir desync. Fixes bug
1543 24976; bugfix on 0.3.2.1-alpha.
1545 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
1546 - Don't treat inability to store a cached consensus object as a bug:
1547 it can happen normally when we are out of disk space. Fixes bug
1548 24859; bugfix on 0.3.1.1-alpha.
1550 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
1551 - Improve the performance of our consensus-diff application code
1552 when Tor is built with the --enable-fragile-hardening option set.
1553 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1555 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
1556 - Don't exit the Tor process if setrlimit() fails to change the file
1557 limit (which can happen sometimes on some versions of OSX). Fixes
1558 bug 21074; bugfix on 0.0.9pre5.
1560 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1561 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1563 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1564 bugfix on 0.2.9.4-alpha.
1566 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
1567 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
1568 25005; bugfix on 0.3.2.7-rc.
1570 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
1571 - Look at the "HSRend" protocol version, not the "HSDir" protocol
1572 version, when deciding whether a consensus entry can support the
1573 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
1574 bugfix on 0.3.2.1-alpha.
1576 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
1577 - Update the "rust dependencies" submodule to be a project-level
1578 repository, rather than a user repository. Closes ticket 25323.
1580 o Documentation (backport from 0.3.3.1-alpha)
1581 - Document that operators who run more than one relay or bridge are
1582 expected to set MyFamily and ContactInfo correctly. Closes
1586 Changes in version 0.3.2.9 - 2018-01-09
1587 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
1589 The 0.3.2 series includes our long-anticipated new onion service
1590 design, with numerous security features. (For more information, see
1591 our blog post at https://blog.torproject.org/fall-harvest.) We also
1592 have a new circuit scheduler algorithm for improved performance on
1593 relays everywhere (see https://blog.torproject.org/kist-and-tell),
1594 along with many smaller features and bugfixes.
1596 Per our stable release policy, we plan to support each stable release
1597 series for at least the next nine months, or for three months after
1598 the first stable release of the next series: whichever is longer. If
1599 you need a release with long-term support, we recommend that you stay
1600 with the 0.2.9 series.
1602 Below is a list of the changes since 0.3.1.7. For a list of all
1603 changes since 0.3.2.8-rc, see the ChangeLog file.
1605 o Directory authority changes:
1606 - Add "Bastet" as a ninth directory authority to the default list.
1607 Closes ticket 23910.
1608 - The directory authority "Longclaw" has changed its IP address.
1609 Closes ticket 23592.
1610 - Remove longclaw's IPv6 address, as it will soon change. Authority
1611 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1612 3/8 directory authorities with IPv6 addresses, but there are also
1613 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1614 - Add an IPv6 address for the "bastet" directory authority. Closes
1617 o Major features (next-generation onion services):
1618 - Tor now supports the next-generation onion services protocol for
1619 clients and services! As part of this release, the core of
1620 proposal 224 has been implemented and is available for
1621 experimentation and testing by our users. This newer version of
1622 onion services ("v3") features many improvements over the legacy
1625 a) Better crypto (replaced SHA1/DH/RSA1024
1626 with SHA3/ed25519/curve25519)
1628 b) Improved directory protocol, leaking much less information to
1631 c) Improved directory protocol, with smaller surface for
1634 d) Better onion address security against impersonation.
1636 e) More extensible introduction/rendezvous protocol.
1638 f) A cleaner and more modular codebase.
1640 You can identify a next-generation onion address by its length:
1641 they are 56 characters long, as in
1642 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
1644 In the future, we will release more options and features for v3
1645 onion services, but we first need a testing period, so that the
1646 current codebase matures and becomes more robust. Planned features
1647 include: offline keys, advanced client authorization, improved
1648 guard algorithms, and statistics. For full details, see
1651 Legacy ("v2") onion services will still work for the foreseeable
1652 future, and will remain the default until this new codebase gets
1653 tested and hardened. Service operators who want to experiment with
1654 the new system can use the 'HiddenServiceVersion 3' torrc
1655 directive along with the regular onion service configuration
1656 options. For more information, see our blog post at
1657 "https://blog.torproject.org/fall-harvest". Enjoy!
1659 o Major feature (scheduler, channel):
1660 - Tor now uses new schedulers to decide which circuits should
1661 deliver cells first, in order to improve congestion at relays. The
1662 first type is called "KIST" ("Kernel Informed Socket Transport"),
1663 and is only available on Linux-like systems: it uses feedback from
1664 the kernel to prevent the kernel's TCP buffers from growing too
1665 full. The second new scheduler type is called "KISTLite": it
1666 behaves the same as KIST, but runs on systems without kernel
1667 support for inspecting TCP implementation details. The old
1668 scheduler is still available, under the name "Vanilla". To change
1669 the default scheduler preference order, use the new "Schedulers"
1670 option. (The default preference order is "KIST,KISTLite,Vanilla".)
1672 Matt Traudt implemented KIST, based on research by Rob Jansen,
1673 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
1674 more information, see the design paper at
1675 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
1676 followup implementation paper at https://arxiv.org/abs/1709.01044.
1677 Closes ticket 12541. For more information, see our blog post at
1678 "https://blog.torproject.org/kist-and-tell".
1680 o Major bugfixes (security, general):
1681 - Fix a denial of service bug where an attacker could use a
1682 malformed directory object to cause a Tor instance to pause while
1683 OpenSSL would try to read a passphrase from the terminal. (Tor
1684 instances run without a terminal, which is the case for most Tor
1685 packages, are not impacted.) Fixes bug 24246; bugfix on every
1686 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1687 Found by OSS-Fuzz as testcase 6360145429790720.
1689 o Major bugfixes (security, directory authority):
1690 - Fix a denial of service issue where an attacker could crash a
1691 directory authority using a malformed router descriptor. Fixes bug
1692 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
1695 o Major bugfixes (security, onion service v2):
1696 - Fix a use-after-free error that could crash v2 Tor onion services
1697 when they failed to open circuits while expiring introduction
1698 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1699 also tracked as TROVE-2017-013 and CVE-2017-8823.
1700 - When checking for replays in the INTRODUCE1 cell data for a
1701 (legacy) onion service, correctly detect replays in the RSA-
1702 encrypted part of the cell. We were previously checking for
1703 replays on the entire cell, but those can be circumvented due to
1704 the malleability of Tor's legacy hybrid encryption. This fix helps
1705 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1706 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1709 o Major bugfixes (security, relay):
1710 - When running as a relay, make sure that we never build a path
1711 through ourselves, even in the case where we have somehow lost the
1712 version of our descriptor appearing in the consensus. Fixes part
1713 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1714 as TROVE-2017-012 and CVE-2017-8822.
1715 - When running as a relay, make sure that we never choose ourselves
1716 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
1717 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
1719 o Major bugfixes (bootstrapping):
1720 - Fetch descriptors aggressively whenever we lack enough to build
1721 circuits, regardless of how many descriptors we are missing.
1722 Previously, we would delay launching the fetch when we had fewer
1723 than 15 missing descriptors, even if some of those descriptors
1724 were blocking circuits from building. Fixes bug 23985; bugfix on
1725 0.1.1.11-alpha. The effects of this bug became worse in
1726 0.3.0.3-alpha, when we began treating missing descriptors from our
1727 primary guards as a reason to delay circuits.
1728 - Don't try fetching microdescriptors from relays that have failed
1729 to deliver them in the past. Fixes bug 23817; bugfix
1732 o Major bugfixes (circuit prediction):
1733 - Fix circuit prediction logic so that a client doesn't treat a port
1734 as being "handled" by a circuit if that circuit already has
1735 isolation settings on it. This change should make Tor clients more
1736 responsive by improving their chances of having a pre-created
1737 circuit ready for use when a request arrives. Fixes bug 18859;
1738 bugfix on 0.2.3.3-alpha.
1740 o Major bugfixes (exit relays, DNS):
1741 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
1742 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
1743 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
1744 identifying and finding a workaround to this bug and to Moritz,
1745 Arthur Edelstein, and Roger for helping to track it down and
1748 o Major bugfixes (relay, crash, assertion failure):
1749 - Fix a timing-based assertion failure that could occur when the
1750 circuit out-of-memory handler freed a connection's output buffer.
1751 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1753 o Major bugfixes (usability, control port):
1754 - Report trusted clock skew indications as bootstrap errors, so
1755 controllers can more easily alert users when their clocks are
1756 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
1758 o Minor features (bridge):
1759 - Bridge relays can now set the BridgeDistribution config option to
1760 add a "bridge-distribution-request" line to their bridge
1761 descriptor, which tells BridgeDB how they'd like their bridge
1762 address to be given out. (Note that as of Oct 2017, BridgeDB does
1763 not yet implement this feature.) As a side benefit, this feature
1764 provides a way to distinguish bridge descriptors from non-bridge
1765 descriptors. Implements tickets 18329.
1766 - When handling the USERADDR command on an ExtOrPort, warn when the
1767 transports provides a USERADDR with no port. In a future version,
1768 USERADDR commands of this format may be rejected. Detects problems
1769 related to ticket 23080.
1771 o Minor features (bug detection):
1772 - Log a warning message with a stack trace for any attempt to call
1773 get_options() during option validation. This pattern has caused
1774 subtle bugs in the past. Closes ticket 22281.
1776 o Minor features (build, compilation):
1777 - The "check-changes" feature is now part of the "make check" tests;
1778 we'll use it to try to prevent misformed changes files from
1779 accumulating. Closes ticket 23564.
1780 - Tor builds should now fail if there are any mismatches between the
1781 C type representing a configuration variable and the C type the
1782 data-driven parser uses to store a value there. Previously, we
1783 needed to check these by hand, which sometimes led to mistakes.
1784 Closes ticket 23643.
1786 o Minor features (client):
1787 - You can now use Tor as a tunneled HTTP proxy: use the new
1788 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
1789 requests. Closes ticket 22407.
1790 - Add an extra check to make sure that we always use the newer guard
1791 selection code for picking our guards. Closes ticket 22779.
1792 - When downloading (micro)descriptors, don't split the list into
1793 multiple requests unless we want at least 32 descriptors.
1794 Previously, we split at 4, not 32, which led to significant
1795 overhead in HTTP request size and degradation in compression
1796 performance. Closes ticket 23220.
1797 - Improve log messages when missing descriptors for primary guards.
1798 Resolves ticket 23670.
1800 o Minor features (command line):
1801 - Add a new commandline option, --key-expiration, which prints when
1802 the current signing key is going to expire. Implements ticket
1803 17639; patch by Isis Lovecruft.
1805 o Minor features (control port):
1806 - If an application tries to use the control port as an HTTP proxy,
1807 respond with a meaningful "This is the Tor control port" message,
1808 and log the event. Closes ticket 1667. Patch from Ravi
1810 - Provide better error message for GETINFO desc/(id|name) when not
1811 fetching router descriptors. Closes ticket 5847. Patch by
1813 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
1814 whether Tor will try to download router descriptors and
1815 microdescriptors respectively. Closes ticket 22684.
1816 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
1817 so controllers can tell whether the geoip databases are loaded.
1818 Closes ticket 23237.
1819 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
1820 events. Closes ticket 19254. Patch by "DonnchaC".
1822 o Minor features (development support):
1823 - Developers can now generate a call-graph for Tor using the
1824 "calltool" python program, which post-processes object dumps. It
1825 should work okay on many Linux and OSX platforms, and might work
1826 elsewhere too. To run it, install calltool from
1827 https://gitweb.torproject.org/user/nickm/calltool.git and run
1828 "make callgraph". Closes ticket 19307.
1830 o Minor features (directory authority):
1831 - Make the "Exit" flag assignment only depend on whether the exit
1832 policy allows connections to ports 80 and 443. Previously relays
1833 would get the Exit flag if they allowed connections to one of
1834 these ports and also port 6667. Resolves ticket 23637.
1836 o Minor features (ed25519):
1837 - Add validation function to checks for torsion components in
1838 ed25519 public keys, used by prop224 client-side code. Closes
1839 ticket 22006. Math help by Ian Goldberg.
1841 o Minor features (exit relay, DNS):
1842 - Improve the clarity and safety of the log message from evdns when
1843 receiving an apparently spoofed DNS reply. Closes ticket 3056.
1845 o Minor features (fallback directory mirrors):
1846 - The fallback directory list has been re-generated based on the
1847 current status of the network. Tor uses fallback directories to
1848 bootstrap when it doesn't yet have up-to-date directory
1849 information. Closes ticket 24801.
1850 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1851 prefer to bootstrap from fallback directory mirrors. This is a
1852 follow-up to 24679, which removed weights from the default
1853 fallbacks. Implements ticket 24681.
1855 o Minor features (geoip):
1856 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
1859 o Minor features (integration, hardening):
1860 - Add a new NoExec option to prevent Tor from running other
1861 programs. When this option is set to 1, Tor will never try to run
1862 another program, regardless of the settings of
1863 PortForwardingHelper, ClientTransportPlugin, or
1864 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
1865 without restarting Tor. Closes ticket 22976.
1867 o Minor features (linux seccomp2 sandbox):
1868 - Update the sandbox rules so that they should now work correctly
1869 with Glibc 2.26. Closes ticket 24315.
1871 o Minor features (logging):
1872 - Provide better warnings when the getrandom() syscall fails. Closes
1874 - Downgrade a pair of log messages that could occur when an exit's
1875 resolver gave us an unusual (but not forbidden) response. Closes
1877 - Improve the message we log when re-enabling circuit build timeouts
1878 after having received a consensus. Closes ticket 20963.
1879 - Log more circuit information whenever we are about to try to
1880 package a relay cell on a circuit with a nonexistent n_chan.
1881 Attempt to diagnose ticket 8185.
1882 - Improve info-level log identification of particular circuits, to
1883 help with debugging. Closes ticket 23645.
1884 - Improve the warning message for specifying a relay by nickname.
1885 The previous message implied that nickname registration was still
1886 part of the Tor network design, which it isn't. Closes
1888 - If the sandbox filter fails to load, suggest to the user that
1889 their kernel might not support seccomp2. Closes ticket 23090.
1891 o Minor features (onion service, circuit, logging):
1892 - Improve logging of many callsite in the circuit subsystem to print
1893 the circuit identifier(s).
1894 - Log when we cleanup an intro point from a service so we know when
1895 and for what reason it happened. Closes ticket 23604.
1897 o Minor features (portability):
1898 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
1899 (It doesn't yet work with the sandbox enabled.) Closes
1901 - Check at configure time whether uint8_t is the same type as
1902 unsigned char. Lots of existing code already makes this
1903 assumption, and there could be strict aliasing issues if the
1904 assumption is violated. Closes ticket 22410.
1906 o Minor features (relay):
1907 - When choosing which circuits can be expired as unused, consider
1908 circuits from clients even if those clients used regular CREATE
1909 cells to make them; and do not consider circuits from relays even
1910 if they were made with CREATE_FAST. Part of ticket 22805.
1911 - Reject attempts to use relative file paths when RunAsDaemon is
1912 set. Previously, Tor would accept these, but the directory-
1913 changing step of RunAsDaemon would give strange and/or confusing
1914 results. Closes ticket 22731.
1916 o Minor features (relay statistics):
1917 - Change relay bandwidth reporting stats interval from 4 hours to 24
1918 hours in order to reduce the efficiency of guard discovery
1919 attacks. Fixes ticket 23856.
1921 o Minor features (reverted deprecations):
1922 - The ClientDNSRejectInternalAddresses flag can once again be set in
1923 non-testing Tor networks, so long as they do not use the default
1924 directory authorities. This change also removes the deprecation of
1925 this flag from 0.2.9.2-alpha. Closes ticket 21031.
1927 o Minor features (robustness):
1928 - Change several fatal assertions when flushing buffers into non-
1929 fatal assertions, to prevent any recurrence of 23690.
1931 o Minor features (startup, safety):
1932 - When configured to write a PID file, Tor now exits if it is unable
1933 to do so. Previously, it would warn and continue. Closes
1936 o Minor features (static analysis):
1937 - The BUG() macro has been changed slightly so that Coverity no
1938 longer complains about dead code if the bug is impossible. Closes
1941 o Minor features (testing):
1942 - Our fuzzing tests now test the encrypted portions of v3 onion
1943 service descriptors. Implements more of 21509.
1944 - Add a unit test to make sure that our own generated platform
1945 string will be accepted by directory authorities. Closes
1947 - The default chutney network tests now include tests for the v3
1948 onion service design. Make sure you have the latest version of
1949 chutney if you want to run these. Closes ticket 22437.
1950 - Add a unit test to verify that we can parse a hardcoded v2 onion
1951 service descriptor. Closes ticket 15554.
1953 o Minor bugfixes (address selection):
1954 - When the fascist_firewall_choose_address_ functions don't find a
1955 reachable address, set the returned address to the null address
1956 and port. This is a precautionary measure, because some callers do
1957 not check the return value. Fixes bug 24736; bugfix
1960 o Minor bugfixes (bootstrapping):
1961 - When warning about state file clock skew, report the correct
1962 direction for the detected skew. Fixes bug 23606; bugfix
1965 o Minor bugfixes (bridge clients, bootstrap):
1966 - Retry directory downloads when we get our first bridge descriptor
1967 during bootstrap or while reconnecting to the network. Keep
1968 retrying every time we get a bridge descriptor, until we have a
1969 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
1970 - Stop delaying bridge descriptor fetches when we have cached bridge
1971 descriptors. Instead, only delay bridge descriptor fetches when we
1972 have at least one reachable bridge. Fixes part of bug 24367;
1973 bugfix on 0.2.0.3-alpha.
1974 - Stop delaying directory fetches when we have cached bridge
1975 descriptors. Instead, only delay bridge descriptor fetches when
1976 all our bridges are definitely unreachable. Fixes part of bug
1977 24367; bugfix on 0.2.0.3-alpha.
1979 o Minor bugfixes (bridge):
1980 - Overwrite the bridge address earlier in the process of retrieving
1981 its descriptor, to make sure we reach it on the configured
1982 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
1984 o Minor bugfixes (build, compilation):
1985 - Fix a compilation warning when building with zstd support on
1986 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
1987 and fixed by Andreas Stieger.
1988 - When searching for OpenSSL, don't accept any OpenSSL library that
1989 lacks TLSv1_1_method(): Tor doesn't build with those versions.
1990 Additionally, look in /usr/local/opt/openssl, if it's present.
1991 These changes together repair the default build on OSX systems
1992 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
1993 - Fix a signed/unsigned comparison warning introduced by our fix to
1994 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1995 - Fix a memory leak warning in one of the libevent-related
1996 configuration tests that could occur when manually specifying
1997 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
1998 Found and patched by Alex Xu.
1999 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
2000 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2002 o Minor bugfixes (certificate handling):
2003 - Fix a time handling bug in Tor certificates set to expire after
2004 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
2005 Coverity as CID 1415728.
2007 o Minor bugfixes (client):
2008 - By default, do not enable storage of client-side DNS values. These
2009 values were unused by default previously, but they should not have
2010 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
2012 o Minor bugfixes (client, usability):
2013 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
2014 SOCKS4a requests that contain IP address strings, even when
2015 SafeSocks in enabled, as this prevents user from connecting to
2016 known IP addresses without relying on DNS for resolving. SafeSocks
2017 still rejects SOCKS connections that connect to IP addresses when
2018 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
2019 bugfix on Tor 0.2.6.2-alpha.
2021 o Minor bugfixes (code correctness):
2022 - Call htons() in extend_cell_format() for encoding a 16-bit value.
2023 Previously we used ntohs(), which happens to behave the same on
2024 all the platforms we support, but which isn't really correct.
2025 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
2026 - For defense-in-depth, make the controller's write_escaped_data()
2027 function robust to extremely long inputs. Fixes bug 19281; bugfix
2028 on 0.1.1.1-alpha. Reported by Guido Vranken.
2029 - Fix several places in our codebase where a C compiler would be
2030 likely to eliminate a check, based on assuming that undefined
2031 behavior had not happened elsewhere in the code. These cases are
2032 usually a sign of redundant checking or dubious arithmetic. Found
2033 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
2034 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
2037 o Minor bugfixes (compression):
2038 - Handle a pathological case when decompressing Zstandard data when
2039 the output buffer size is zero. Fixes bug 23551; bugfix
2042 o Minor bugfixes (consensus expiry):
2043 - Check for adequate directory information correctly. Previously, Tor
2044 would reconsider whether it had sufficient directory information
2045 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
2047 o Minor bugfixes (control port, linux seccomp2 sandbox):
2048 - Avoid a crash when attempting to use the seccomp2 sandbox together
2049 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
2052 o Minor bugfixes (control port, onion services):
2053 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
2054 HS_DESC event when a service is not able to upload a descriptor.
2055 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
2057 o Minor bugfixes (directory cache):
2058 - Recover better from empty or corrupt files in the consensus cache
2059 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
2060 - When a consensus diff calculation is only partially successful,
2061 only record the successful parts as having succeeded. Partial
2062 success can happen if (for example) one compression method fails
2063 but the others succeed. Previously we misrecorded all the
2064 calculations as having succeeded, which would later cause a
2065 nonfatal assertion failure. Fixes bug 24086; bugfix
2068 o Minor bugfixes (directory client):
2069 - On failure to download directory information, delay retry attempts
2070 by a random amount based on the "decorrelated jitter" algorithm.
2071 Our previous delay algorithm tended to produce extra-long delays
2072 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
2074 o Minor bugfixes (directory protocol):
2075 - Directory servers now include a "Date:" http header for response
2076 codes other than 200. Clients starting with a skewed clock and a
2077 recent consensus were getting "304 Not modified" responses from
2078 directory authorities, so without the Date header, the client
2079 would never hear about a wrong clock. Fixes bug 23499; bugfix
2081 - Make clients wait for 6 seconds before trying to download a
2082 consensus from an authority. Fixes bug 17750; bugfix
2085 o Minor bugfixes (documentation):
2086 - Document better how to read gcov, and what our gcov postprocessing
2087 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
2088 - Fix manpage to not refer to the obsolete (and misspelled)
2089 UseEntryGuardsAsDirectoryGuards parameter in the description of
2090 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
2092 o Minor bugfixes (DoS-resistance):
2093 - If future code asks if there are any running bridges, without
2094 checking if bridges are enabled, log a BUG warning rather than
2095 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
2097 o Minor bugfixes (entry guards):
2098 - Tor now updates its guard state when it reads a consensus
2099 regardless of whether it's missing descriptors. That makes tor use
2100 its primary guards to fetch descriptors in some edge cases where
2101 it would previously have used fallback directories. Fixes bug
2102 23862; bugfix on 0.3.0.1-alpha.
2104 o Minor bugfixes (format strictness):
2105 - Restrict several data formats to decimal. Previously, the
2106 BuildTimeHistogram entries in the state file, the "bw=" entries in
2107 the bandwidth authority file, and the process IDs passed to the
2108 __OwningControllerProcess option could all be specified in hex or
2109 octal as well as in decimal. This was not an intentional feature.
2110 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
2113 o Minor bugfixes (heartbeat):
2114 - If we fail to write a heartbeat message, schedule a retry for the
2115 minimum heartbeat interval number of seconds in the future. Fixes
2116 bug 19476; bugfix on 0.2.3.1-alpha.
2118 o Minor bugfixes (logging):
2119 - Suppress a log notice when relay descriptors arrive. We already
2120 have a bootstrap progress for this so no need to log notice
2121 everytime tor receives relay descriptors. Microdescriptors behave
2122 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
2123 - Remove duplicate log messages regarding opening non-local
2124 SocksPorts upon parsing config and opening listeners at startup.
2125 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
2126 - Use a more comprehensible log message when telling the user
2127 they've excluded every running exit node. Fixes bug 7890; bugfix
2129 - When logging the number of descriptors we intend to download per
2130 directory request, do not log a number higher than then the number
2131 of descriptors we're fetching in total. Fixes bug 19648; bugfix
2133 - When warning about a directory owned by the wrong user, log the
2134 actual name of the user owning the directory. Previously, we'd log
2135 the name of the process owner twice. Fixes bug 23487; bugfix
2137 - Fix some messages on unexpected errors from the seccomp2 library.
2138 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
2139 - The tor specification says hop counts are 1-based, so fix two log
2140 messages that mistakenly logged 0-based hop counts. Fixes bug
2141 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
2142 Credit to Xiaofan Li for reporting this issue.
2144 o Minor bugfixes (logging, relay shutdown, annoyance):
2145 - When a circuit is marked for close, do not attempt to package any
2146 cells for channels on that circuit. Previously, we would detect
2147 this condition lower in the call stack, when we noticed that the
2148 circuit had no attached channel, and log an annoying message.
2149 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2151 o Minor bugfixes (memory safety, defensive programming):
2152 - Clear the target address when node_get_prim_orport() returns
2153 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2155 o Minor bugfixes (memory usage):
2156 - When queuing DESTROY cells on a channel, only queue the circuit-id
2157 and reason fields: not the entire 514-byte cell. This fix should
2158 help mitigate any bugs or attacks that fill up these queues, and
2159 free more RAM for other uses. Fixes bug 24666; bugfix
2162 o Minor bugfixes (network layer):
2163 - When closing a connection via close_connection_immediately(), we
2164 mark it as "not blocked on bandwidth", to prevent later calls from
2165 trying to unblock it, and give it permission to read. This fixes a
2166 backtrace warning that can happen on relays under various
2167 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
2169 o Minor bugfixes (onion services):
2170 - The introduction circuit was being timed out too quickly while
2171 waiting for the rendezvous circuit to complete. Keep the intro
2172 circuit around longer instead of timing out and reopening new ones
2173 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
2174 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2175 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2177 - When handling multiple SOCKS request for the same .onion address,
2178 only fetch the service descriptor once.
2179 - Avoid a possible double close of a circuit by the intro point on
2180 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2181 bugfix on 0.3.0.1-alpha.
2182 - When reloading configured onion services, copy all information
2183 from the old service object. Previously, some data was omitted,
2184 causing delays in descriptor upload, and other bugs. Fixes bug
2185 23790; bugfix on 0.2.1.9-alpha.
2187 o Minor bugfixes (path selection):
2188 - When selecting relays by bandwidth, avoid a rounding error that
2189 could sometimes cause load to be imbalanced incorrectly.
2190 Previously, we would always round upwards; now, we round towards
2191 the nearest integer. This had the biggest effect when a relay's
2192 weight adjustments should have given it weight 0, but it got
2193 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
2194 - When calculating the fraction of nodes that have descriptors, and
2195 all nodes in the network have zero bandwidths, count the number of
2196 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
2197 - Actually log the total bandwidth in compute_weighted_bandwidths().
2198 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
2200 o Minor bugfixes (portability):
2201 - Stop using the PATH_MAX variable, which is not defined on GNU
2202 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
2203 - Fix a bug in the bit-counting parts of our timing-wheel code on
2204 MSVC. (Note that MSVC is still not a supported build platform, due
2205 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
2208 o Minor bugfixes (relay):
2209 - When uploading our descriptor for the first time after startup,
2210 report the reason for uploading as "Tor just started" rather than
2211 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
2212 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2213 relays, to prevent spurious address resolutions and descriptor
2214 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2215 bugfix on in 0.2.8.1-alpha.
2216 - Avoid a crash when transitioning from client mode to bridge mode.
2217 Previously, we would launch the worker threads whenever our
2218 "public server" mode changed, but not when our "server" mode
2219 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2221 o Minor bugfixes (testing):
2222 - Fix a spurious fuzzing-only use of an uninitialized value. Found
2223 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
2224 - Test that IPv6-only clients can use microdescriptors when running
2225 "make test-network-all". Requires chutney master 61c28b9 or later.
2226 Closes ticket 24109.
2227 - Prevent scripts/test/coverage from attempting to move gcov output
2228 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
2229 - Capture and detect several "Result does not fit" warnings in unit
2230 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
2232 - Fix additional channelpadding unit test failures by using mocked
2233 time instead of actual time for all tests. Fixes bug 23608; bugfix
2235 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
2236 to correctly handle cases where a caller gives it an RSA key of
2237 under 160 bits. (This is not actually a bug in Tor itself, but
2238 rather in our fuzzing code.) Fixes bug 24247; bugfix on
2239 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
2240 - Fix a broken unit test for the OutboundAddress option: the parsing
2241 function was never returning an error on failure. Fixes bug 23366;
2242 bugfix on 0.3.0.3-alpha.
2243 - Fix a signed-integer overflow in the unit tests for
2244 dir/download_status_random_backoff, which was untriggered until we
2245 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
2247 o Minor bugfixes (usability, control port):
2248 - Stop making an unnecessary routerlist check in NETINFO clock skew
2249 detection; this was preventing clients from reporting NETINFO clock
2250 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
2252 o Code simplification and refactoring:
2253 - Remove various ways of testing circuits and connections for
2254 "clientness"; instead, favor channel_is_client(). Part of
2256 - Extract the code for handling newly-open channels into a separate
2257 function from the general code to handle channel state
2258 transitions. This change simplifies our callgraph, reducing the
2259 size of the largest strongly connected component by roughly a
2260 factor of two. Closes ticket 22608.
2261 - Remove dead code for largely unused statistics on the number of
2262 times we've attempted various public key operations. Fixes bug
2263 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
2264 - Remove several now-obsolete functions for asking about old
2265 variants directory authority status. Closes ticket 22311; patch
2267 - Remove some of the code that once supported "Named" and "Unnamed"
2268 routers. Authorities no longer vote for these flags. Closes
2270 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
2271 and old hidden services, to indicate that they aren't suitable for
2272 new protocols or formats. Closes ticket 23026.
2273 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
2274 22521. Patch from Neel Chauhan.
2275 - Split the enormous circuit_send_next_onion_skin() function into
2276 multiple subfunctions. Closes ticket 22804.
2277 - Split the portions of the buffer.c module that handle particular
2278 protocols into separate modules. Part of ticket 23149.
2279 - Use our test macros more consistently, to produce more useful
2280 error messages when our unit tests fail. Add coccinelle patches to
2281 allow us to re-check for test macro uses. Closes ticket 22497.
2283 o Deprecated features:
2284 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
2285 now deprecated; they do not apply to relays, and they have had no
2286 effect on clients since 0.2.8.x. Closes ticket 19704.
2287 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
2288 only applies to direct unencrypted HTTP connections to your
2289 directory server, which your Tor probably isn't using. Closes
2293 - Add notes in man page regarding OS support for the various
2294 scheduler types. Attempt to use less jargon in the scheduler
2295 section. Closes ticket 24254.
2296 - Clarify that the Address option is entirely about setting an
2297 advertised IPv4 address. Closes ticket 18891.
2298 - Clarify the manpage's use of the term "address" to clarify what
2299 kind of address is intended. Closes ticket 21405.
2300 - Document that onion service subdomains are allowed, and ignored.
2301 Closes ticket 18736.
2302 - Clarify in the manual that "Sandbox 1" is only supported on Linux
2303 kernels. Closes ticket 22677.
2304 - Document all values of PublishServerDescriptor in the manpage.
2305 Closes ticket 15645.
2306 - Improve the documentation for the directory port part of the
2307 DirAuthority line. Closes ticket 20152.
2308 - Restore documentation for the authorities' "approved-routers"
2309 file. Closes ticket 21148.
2312 - The AllowDotExit option has been removed as unsafe. It has been
2313 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
2314 - The ClientDNSRejectInternalAddresses flag can no longer be set on
2315 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
2316 Closes ticket 21031.
2317 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
2318 nobody was using it any longer. Closes ticket 22377.
2321 Changes in version 0.3.1.9 - 2017-12-01:
2322 Tor 0.3.1.9 backports important security and stability fixes from the
2323 0.3.2 development series. All Tor users should upgrade to this
2324 release, or to another of the releases coming out today.
2326 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2327 - Fix a denial of service bug where an attacker could use a
2328 malformed directory object to cause a Tor instance to pause while
2329 OpenSSL would try to read a passphrase from the terminal. (Tor
2330 instances run without a terminal, which is the case for most Tor
2331 packages, are not impacted.) Fixes bug 24246; bugfix on every
2332 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2333 Found by OSS-Fuzz as testcase 6360145429790720.
2334 - Fix a denial of service issue where an attacker could crash a
2335 directory authority using a malformed router descriptor. Fixes bug
2336 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2338 - When checking for replays in the INTRODUCE1 cell data for a
2339 (legacy) onion service, correctly detect replays in the RSA-
2340 encrypted part of the cell. We were previously checking for
2341 replays on the entire cell, but those can be circumvented due to
2342 the malleability of Tor's legacy hybrid encryption. This fix helps
2343 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2344 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2347 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2348 - Fix a use-after-free error that could crash v2 Tor onion services
2349 when they failed to open circuits while expiring introduction
2350 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2351 also tracked as TROVE-2017-013 and CVE-2017-8823.
2353 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2354 - When running as a relay, make sure that we never build a path
2355 through ourselves, even in the case where we have somehow lost the
2356 version of our descriptor appearing in the consensus. Fixes part
2357 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2358 as TROVE-2017-012 and CVE-2017-8822.
2359 - When running as a relay, make sure that we never choose ourselves
2360 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2361 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2363 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2364 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2365 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2366 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2367 identifying and finding a workaround to this bug and to Moritz,
2368 Arthur Edelstein, and Roger for helping to track it down and
2371 o Minor features (bridge):
2372 - Bridges now include notice in their descriptors that they are
2373 bridges, and notice of their distribution status, based on their
2374 publication settings. Implements ticket 18329. For more fine-
2375 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2378 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2379 - Add an IPv6 address for the "bastet" directory authority. Closes
2382 o Minor features (geoip):
2383 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2386 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2387 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2388 relays, to prevent spurious address resolutions and descriptor
2389 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2390 bugfix on in 0.2.8.1-alpha.
2392 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2393 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2394 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2396 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2397 - When a circuit is marked for close, do not attempt to package any
2398 cells for channels on that circuit. Previously, we would detect
2399 this condition lower in the call stack, when we noticed that the
2400 circuit had no attached channel, and log an annoying message.
2401 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2403 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
2404 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2405 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2408 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2409 - Avoid a crash when transitioning from client mode to bridge mode.
2410 Previously, we would launch the worker threads whenever our
2411 "public server" mode changed, but not when our "server" mode
2412 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2415 Changes in version 0.3.0.13 - 2017-12-01
2416 Tor 0.3.0.13 backports important security and stability bugfixes from
2417 later Tor releases. All Tor users should upgrade to this release, or
2418 to another of the releases coming out today.
2420 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
2421 2018. If you need a release with long-term support, please stick with
2422 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2424 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2425 - Fix a denial of service bug where an attacker could use a
2426 malformed directory object to cause a Tor instance to pause while
2427 OpenSSL would try to read a passphrase from the terminal. (Tor
2428 instances run without a terminal, which is the case for most Tor
2429 packages, are not impacted.) Fixes bug 24246; bugfix on every
2430 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2431 Found by OSS-Fuzz as testcase 6360145429790720.
2432 - Fix a denial of service issue where an attacker could crash a
2433 directory authority using a malformed router descriptor. Fixes bug
2434 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2436 - When checking for replays in the INTRODUCE1 cell data for a
2437 (legacy) onion service, correctly detect replays in the RSA-
2438 encrypted part of the cell. We were previously checking for
2439 replays on the entire cell, but those can be circumvented due to
2440 the malleability of Tor's legacy hybrid encryption. This fix helps
2441 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2442 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2445 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2446 - Fix a use-after-free error that could crash v2 Tor onion services
2447 when they failed to open circuits while expiring introduction
2448 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2449 also tracked as TROVE-2017-013 and CVE-2017-8823.
2451 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2452 - When running as a relay, make sure that we never build a path
2453 through ourselves, even in the case where we have somehow lost the
2454 version of our descriptor appearing in the consensus. Fixes part
2455 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2456 as TROVE-2017-012 and CVE-2017-8822.
2457 - When running as a relay, make sure that we never choose ourselves
2458 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2459 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2461 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2462 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2463 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2464 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2465 identifying and finding a workaround to this bug and to Moritz,
2466 Arthur Edelstein, and Roger for helping to track it down and
2469 o Minor features (security, windows, backport from 0.3.1.1-alpha):
2470 - Enable a couple of pieces of Windows hardening: one
2471 (HeapEnableTerminationOnCorruption) that has been on-by-default
2472 since Windows 8, and unavailable before Windows 7; and one
2473 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2474 affect us, but shouldn't do any harm. Closes ticket 21953.
2476 o Minor features (bridge, backport from 0.3.1.9):
2477 - Bridges now include notice in their descriptors that they are
2478 bridges, and notice of their distribution status, based on their
2479 publication settings. Implements ticket 18329. For more fine-
2480 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2483 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2484 - Add an IPv6 address for the "bastet" directory authority. Closes
2487 o Minor features (geoip):
2488 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2491 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2492 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2493 relays, to prevent spurious address resolutions and descriptor
2494 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2495 bugfix on in 0.2.8.1-alpha.
2497 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2498 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2499 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2501 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2502 - When a circuit is marked for close, do not attempt to package any
2503 cells for channels on that circuit. Previously, we would detect
2504 this condition lower in the call stack, when we noticed that the
2505 circuit had no attached channel, and log an annoying message.
2506 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2508 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2509 - Avoid a crash when transitioning from client mode to bridge mode.
2510 Previously, we would launch the worker threads whenever our
2511 "public server" mode changed, but not when our "server" mode
2512 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2514 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2515 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2516 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2519 Changes in version 0.2.9.14 - 2017-12-01
2520 Tor 0.3.0.13 backports important security and stability bugfixes from
2521 later Tor releases. All Tor users should upgrade to this release, or
2522 to another of the releases coming out today.
2524 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2525 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2526 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2527 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2528 identifying and finding a workaround to this bug and to Moritz,
2529 Arthur Edelstein, and Roger for helping to track it down and
2532 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2533 - Fix a denial of service bug where an attacker could use a
2534 malformed directory object to cause a Tor instance to pause while
2535 OpenSSL would try to read a passphrase from the terminal. (Tor
2536 instances run without a terminal, which is the case for most Tor
2537 packages, are not impacted.) Fixes bug 24246; bugfix on every
2538 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2539 Found by OSS-Fuzz as testcase 6360145429790720.
2540 - Fix a denial of service issue where an attacker could crash a
2541 directory authority using a malformed router descriptor. Fixes bug
2542 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2544 - When checking for replays in the INTRODUCE1 cell data for a
2545 (legacy) onion service, correctly detect replays in the RSA-
2546 encrypted part of the cell. We were previously checking for
2547 replays on the entire cell, but those can be circumvented due to
2548 the malleability of Tor's legacy hybrid encryption. This fix helps
2549 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2550 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2553 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2554 - Fix a use-after-free error that could crash v2 Tor onion services
2555 when they failed to open circuits while expiring introduction
2556 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2557 also tracked as TROVE-2017-013 and CVE-2017-8823.
2559 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2560 - When running as a relay, make sure that we never build a path
2561 through ourselves, even in the case where we have somehow lost the
2562 version of our descriptor appearing in the consensus. Fixes part
2563 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2564 as TROVE-2017-012 and CVE-2017-8822.
2566 o Minor features (bridge, backport from 0.3.1.9):
2567 - Bridges now include notice in their descriptors that they are
2568 bridges, and notice of their distribution status, based on their
2569 publication settings. Implements ticket 18329. For more fine-
2570 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2573 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2574 - Add an IPv6 address for the "bastet" directory authority. Closes
2577 o Minor features (geoip):
2578 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2581 o Minor features (security, windows, backport from 0.3.1.1-alpha):
2582 - Enable a couple of pieces of Windows hardening: one
2583 (HeapEnableTerminationOnCorruption) that has been on-by-default
2584 since Windows 8, and unavailable before Windows 7; and one
2585 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2586 affect us, but shouldn't do any harm. Closes ticket 21953.
2588 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2589 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2590 relays, to prevent spurious address resolutions and descriptor
2591 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2592 bugfix on in 0.2.8.1-alpha.
2594 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2595 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2596 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2598 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2599 - When a circuit is marked for close, do not attempt to package any
2600 cells for channels on that circuit. Previously, we would detect
2601 this condition lower in the call stack, when we noticed that the
2602 circuit had no attached channel, and log an annoying message.
2603 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2605 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2606 - Avoid a crash when transitioning from client mode to bridge mode.
2607 Previously, we would launch the worker threads whenever our
2608 "public server" mode changed, but not when our "server" mode
2609 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2611 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2612 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2613 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2616 Changes in version 0.2.8.17 - 2017-12-01
2617 Tor 0.2.8.17 backports important security and stability bugfixes from
2618 later Tor releases. All Tor users should upgrade to this release, or
2619 to another of the releases coming out today.
2621 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
2622 2018. If you need a release with long-term support, please upgrade with
2623 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2625 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2626 - Fix a denial of service bug where an attacker could use a
2627 malformed directory object to cause a Tor instance to pause while
2628 OpenSSL would try to read a passphrase from the terminal. (Tor
2629 instances run without a terminal, which is the case for most Tor
2630 packages, are not impacted.) Fixes bug 24246; bugfix on every
2631 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2632 Found by OSS-Fuzz as testcase 6360145429790720.
2633 - When checking for replays in the INTRODUCE1 cell data for a
2634 (legacy) onion service, correctly detect replays in the RSA-
2635 encrypted part of the cell. We were previously checking for
2636 replays on the entire cell, but those can be circumvented due to
2637 the malleability of Tor's legacy hybrid encryption. This fix helps
2638 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2639 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2642 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2643 - Fix a use-after-free error that could crash v2 Tor onion services
2644 when they failed to open circuits while expiring introduction
2645 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2646 also tracked as TROVE-2017-013 and CVE-2017-8823.
2648 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2649 - When running as a relay, make sure that we never build a path through
2650 ourselves, even in the case where we have somehow lost the version of
2651 our descriptor appearing in the consensus. Fixes part of bug 21534;
2652 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
2655 o Minor features (bridge, backport from 0.3.1.9):
2656 - Bridges now include notice in their descriptors that they are
2657 bridges, and notice of their distribution status, based on their
2658 publication settings. Implements ticket 18329. For more fine-
2659 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2662 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2663 - Add an IPv6 address for the "bastet" directory authority. Closes
2666 o Minor features (geoip):
2667 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2670 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2671 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2672 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2675 Changes in version 0.2.5.16 - 2017-12-01
2676 Tor 0.2.5.13 backports important security and stability bugfixes from
2677 later Tor releases. All Tor users should upgrade to this release, or
2678 to another of the releases coming out today.
2680 Note: the Tor 0.2.5 series will no longer be supported after 1 May
2681 2018. If you need a release with long-term support, please upgrade to
2682 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2684 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2685 - Fix a denial of service bug where an attacker could use a
2686 malformed directory object to cause a Tor instance to pause while
2687 OpenSSL would try to read a passphrase from the terminal. (Tor
2688 instances run without a terminal, which is the case for most Tor
2689 packages, are not impacted.) Fixes bug 24246; bugfix on every
2690 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2691 Found by OSS-Fuzz as testcase 6360145429790720.
2692 - When checking for replays in the INTRODUCE1 cell data for a
2693 (legacy) onion service, correctly detect replays in the RSA-
2694 encrypted part of the cell. We were previously checking for
2695 replays on the entire cell, but those can be circumvented due to
2696 the malleability of Tor's legacy hybrid encryption. This fix helps
2697 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2698 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2701 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2702 - When running as a relay, make sure that we never build a path
2703 through ourselves, even in the case where we have somehow lost the
2704 version of our descriptor appearing in the consensus. Fixes part
2705 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2706 as TROVE-2017-012 and CVE-2017-8822.
2708 o Minor features (bridge, backport from 0.3.1.9):
2709 - Bridges now include notice in their descriptors that they are
2710 bridges, and notice of their distribution status, based on their
2711 publication settings. Implements ticket 18329. For more fine-
2712 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2715 o Minor features (geoip):
2716 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2720 Changes in version 0.2.5.15 - 2017-10-25
2721 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
2722 series. It also adds a new directory authority, Bastet.
2724 Note: the Tor 0.2.5 series will no longer be supported after 1 May
2725 2018. If you need a release with long-term support, please upgrade to
2726 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2728 o Directory authority changes:
2729 - Add "Bastet" as a ninth directory authority to the default list.
2730 Closes ticket 23910.
2731 - The directory authority "Longclaw" has changed its IP address.
2732 Closes ticket 23592.
2734 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2735 - Avoid an assertion failure bug affecting our implementation of
2736 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2737 handling of "0xx" differs from what we had expected. Fixes bug
2738 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2740 o Minor features (geoip):
2741 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2744 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2745 - Fix a memset() off the end of an array when packing cells. This
2746 bug should be harmless in practice, since the corrupted bytes are
2747 still in the same structure, and are always padding bytes,
2748 ignored, or immediately overwritten, depending on compiler
2749 behavior. Nevertheless, because the memset()'s purpose is to make
2750 sure that any other cell-handling bugs can't expose bytes to the
2751 network, we need to fix it. Fixes bug 22737; bugfix on
2752 0.2.4.11-alpha. Fixes CID 1401591.
2754 o Build features (backport from 0.3.1.5-alpha):
2755 - Tor's repository now includes a Travis Continuous Integration (CI)
2756 configuration file (.travis.yml). This is meant to help new
2757 developers and contributors who fork Tor to a Github repository be
2758 better able to test their changes, and understand what we expect
2759 to pass. To use this new build feature, you must fork Tor to your
2760 Github account, then go into the "Integrations" menu in the
2761 repository settings for your fork and enable Travis, then push
2762 your changes. Closes ticket 22636.
2765 Changes in version 0.2.8.16 - 2017-10-25
2766 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
2767 series, including a bugfix for a crash issue that had affected relays
2768 under memory pressure. It also adds a new directory authority, Bastet.
2770 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
2771 2018. If you need a release with long-term support, please stick with
2772 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2774 o Directory authority changes:
2775 - Add "Bastet" as a ninth directory authority to the default list.
2776 Closes ticket 23910.
2777 - The directory authority "Longclaw" has changed its IP address.
2778 Closes ticket 23592.
2780 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2781 - Fix a timing-based assertion failure that could occur when the
2782 circuit out-of-memory handler freed a connection's output buffer.
2783 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2785 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2786 - Remove longclaw's IPv6 address, as it will soon change. Authority
2787 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2788 3/8 directory authorities with IPv6 addresses, but there are also
2789 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2791 o Minor features (geoip):
2792 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2796 Changes in version 0.2.9.13 - 2017-10-25
2797 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
2798 series, including a bugfix for a crash issue that had affected relays
2799 under memory pressure. It also adds a new directory authority, Bastet.
2801 o Directory authority changes:
2802 - Add "Bastet" as a ninth directory authority to the default list.
2803 Closes ticket 23910.
2804 - The directory authority "Longclaw" has changed its IP address.
2805 Closes ticket 23592.
2807 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2808 - Fix a timing-based assertion failure that could occur when the
2809 circuit out-of-memory handler freed a connection's output buffer.
2810 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2812 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2813 - Remove longclaw's IPv6 address, as it will soon change. Authority
2814 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2815 3/8 directory authorities with IPv6 addresses, but there are also
2816 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2818 o Minor features (geoip):
2819 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2822 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
2823 - When a directory authority rejects a descriptor or extrainfo with
2824 a given digest, mark that digest as undownloadable, so that we do
2825 not attempt to download it again over and over. We previously
2826 tried to avoid downloading such descriptors by other means, but we
2827 didn't notice if we accidentally downloaded one anyway. This
2828 behavior became problematic in 0.2.7.2-alpha, when authorities
2829 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2832 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2833 - Clear the address when node_get_prim_orport() returns early.
2834 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2836 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
2837 - When running as a Windows service, set the ID of the main thread
2838 correctly. Failure to do so made us fail to send log messages to
2839 the controller in 0.2.1.16-rc, slowed down controller event
2840 delivery in 0.2.7.3-rc and later, and crash with an assertion
2841 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2842 Patch and diagnosis from "Vort".
2845 Changes in version 0.3.0.12 - 2017-10-25
2846 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
2847 series, including a bugfix for a crash issue that had affected relays
2848 under memory pressure. It also adds a new directory authority, Bastet.
2850 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
2851 2018. If you need a release with long-term support, please stick with
2852 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2854 o Directory authority changes:
2855 - Add "Bastet" as a ninth directory authority to the default list.
2856 Closes ticket 23910.
2857 - The directory authority "Longclaw" has changed its IP address.
2858 Closes ticket 23592.
2860 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2861 - Fix a timing-based assertion failure that could occur when the
2862 circuit out-of-memory handler freed a connection's output buffer.
2863 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2865 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2866 - Remove longclaw's IPv6 address, as it will soon change. Authority
2867 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2868 3/8 directory authorities with IPv6 addresses, but there are also
2869 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2871 o Minor features (geoip):
2872 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2875 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
2876 - When a directory authority rejects a descriptor or extrainfo with
2877 a given digest, mark that digest as undownloadable, so that we do
2878 not attempt to download it again over and over. We previously
2879 tried to avoid downloading such descriptors by other means, but we
2880 didn't notice if we accidentally downloaded one anyway. This
2881 behavior became problematic in 0.2.7.2-alpha, when authorities
2882 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2885 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
2886 - Avoid a possible double close of a circuit by the intro point on
2887 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2888 bugfix on 0.3.0.1-alpha.
2890 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2891 - Clear the address when node_get_prim_orport() returns early.
2892 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2894 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
2895 - When running as a Windows service, set the ID of the main thread
2896 correctly. Failure to do so made us fail to send log messages to
2897 the controller in 0.2.1.16-rc, slowed down controller event
2898 delivery in 0.2.7.3-rc and later, and crash with an assertion
2899 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2900 Patch and diagnosis from "Vort".
2903 Changes in version 0.3.1.8 - 2017-10-25
2904 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
2905 It includes several bugfixes, including a bugfix for a crash issue
2906 that had affected relays under memory pressure. It also adds
2907 a new directory authority, Bastet.
2909 o Directory authority changes:
2910 - Add "Bastet" as a ninth directory authority to the default list.
2911 Closes ticket 23910.
2912 - The directory authority "Longclaw" has changed its IP address.
2913 Closes ticket 23592.
2915 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2916 - Fix a timing-based assertion failure that could occur when the
2917 circuit out-of-memory handler freed a connection's output buffer.
2918 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2920 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2921 - Remove longclaw's IPv6 address, as it will soon change. Authority
2922 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2923 3/8 directory authorities with IPv6 addresses, but there are also
2924 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2926 o Minor features (geoip):
2927 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2930 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
2931 - Fix a compilation warning when building with zstd support on
2932 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
2933 and fixed by Andreas Stieger.
2935 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
2936 - Handle a pathological case when decompressing Zstandard data when
2937 the output buffer size is zero. Fixes bug 23551; bugfix
2940 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
2941 - Remove the length limit on HTTP status lines that authorities can
2942 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
2944 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
2945 - Avoid a possible double close of a circuit by the intro point on
2946 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2947 bugfix on 0.3.0.1-alpha.
2949 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2950 - Clear the address when node_get_prim_orport() returns early.
2951 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2953 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
2954 - Fix additional channelpadding unit test failures by using mocked
2955 time instead of actual time for all tests. Fixes bug 23608; bugfix
2959 Changes in version 0.2.8.15 - 2017-09-18
2960 Tor 0.2.8.15 backports a collection of bugfixes from later
2963 Most significantly, it includes a fix for TROVE-2017-008, a
2964 security bug that affects hidden services running with the
2965 SafeLogging option disabled. For more information, see
2966 https://trac.torproject.org/projects/tor/ticket/23490
2968 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
2969 2018. We suggest that you upgrade to the latest stable release if
2970 possible. If you can't, we recommend that you upgrade at least to
2971 0.2.9, which will be supported until 2020.
2973 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2974 - Avoid an assertion failure bug affecting our implementation of
2975 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2976 handling of "0xx" differs from what we had expected. Fixes bug
2977 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2980 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
2983 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2984 - Backport a fix for an "unused variable" warning that appeared
2985 in some versions of mingw. Fixes bug 22838; bugfix on
2988 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2989 - Fix a memset() off the end of an array when packing cells. This
2990 bug should be harmless in practice, since the corrupted bytes are
2991 still in the same structure, and are always padding bytes,
2992 ignored, or immediately overwritten, depending on compiler
2993 behavior. Nevertheless, because the memset()'s purpose is to make
2994 sure that any other cell-handling bugs can't expose bytes to the
2995 network, we need to fix it. Fixes bug 22737; bugfix on
2996 0.2.4.11-alpha. Fixes CID 1401591.
2998 o Build features (backport from 0.3.1.5-alpha):
2999 - Tor's repository now includes a Travis Continuous Integration (CI)
3000 configuration file (.travis.yml). This is meant to help new
3001 developers and contributors who fork Tor to a Github repository be
3002 better able to test their changes, and understand what we expect
3003 to pass. To use this new build feature, you must fork Tor to your
3004 Github account, then go into the "Integrations" menu in the
3005 repository settings for your fork and enable Travis, then push
3006 your changes. Closes ticket 22636.
3009 Changes in version 0.2.9.12 - 2017-09-18
3010 Tor 0.2.9.12 backports a collection of bugfixes from later
3013 Most significantly, it includes a fix for TROVE-2017-008, a
3014 security bug that affects hidden services running with the
3015 SafeLogging option disabled. For more information, see
3016 https://trac.torproject.org/projects/tor/ticket/23490
3018 o Major features (security, backport from 0.3.0.2-alpha):
3019 - Change the algorithm used to decide DNS TTLs on client and server
3020 side, to better resist DNS-based correlation attacks like the
3021 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
3022 Feamster. Now relays only return one of two possible DNS TTL
3023 values, and clients are willing to believe DNS TTL values up to 3
3024 hours long. Closes ticket 19769.
3026 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
3027 - Fix a rare crash when sending a begin cell on a circuit whose
3028 linked directory connection had already been closed. Fixes bug
3029 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
3031 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
3032 - Fix a bug that prevented exit nodes from caching DNS records for
3033 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
3035 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
3036 - Fix a typo that had prevented TPROXY-based transparent proxying
3037 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3038 Patch from "d4fq0fQAgoJ".
3040 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3041 - Avoid an assertion failure bug affecting our implementation of
3042 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3043 handling of "0xx" differs from what we had expected. Fixes bug
3044 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3046 o Minor features (code style, backport from 0.3.1.3-alpha):
3047 - Add "Falls through" comments to our codebase, in order to silence
3048 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3049 Stieger. Closes ticket 22446.
3051 o Minor features (geoip):
3052 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3055 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
3056 - Roll over monthly accounting at the configured hour and minute,
3057 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3058 Found by Andrey Karpov with PVS-Studio.
3060 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
3061 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
3062 bugfix on 0.2.8.1-alpha.
3063 - Fix warnings when building with libscrypt and openssl scrypt support
3064 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3065 - When building with certain versions the mingw C header files, avoid
3066 float-conversion warnings when calling the C functions isfinite(),
3067 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
3069 o Minor bugfixes (compilation, backport from 0.3.1.7):
3070 - Avoid compiler warnings in the unit tests for running tor_sscanf()
3071 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3073 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3074 - Backport a fix for an "unused variable" warning that appeared
3075 in some versions of mingw. Fixes bug 22838; bugfix on
3078 o Minor bugfixes (controller, backport from 0.3.1.7):
3079 - Do not crash when receiving a HSPOST command with an empty body.
3080 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3081 - Do not crash when receiving a POSTDESCRIPTOR command with an
3082 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3084 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
3085 - Avoid Coverity build warnings related to our BUG() macro. By
3086 default, Coverity treats BUG() as the Linux kernel does: an
3087 instant abort(). We need to override that so our BUG() macro
3088 doesn't prevent Coverity from analyzing functions that use it.
3089 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3091 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3092 - Fix a memset() off the end of an array when packing cells. This
3093 bug should be harmless in practice, since the corrupted bytes are
3094 still in the same structure, and are always padding bytes,
3095 ignored, or immediately overwritten, depending on compiler
3096 behavior. Nevertheless, because the memset()'s purpose is to make
3097 sure that any other cell-handling bugs can't expose bytes to the
3098 network, we need to fix it. Fixes bug 22737; bugfix on
3099 0.2.4.11-alpha. Fixes CID 1401591.
3101 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
3102 - When setting the maximum number of connections allowed by the OS,
3103 always allow some extra file descriptors for other files. Fixes
3104 bug 22797; bugfix on 0.2.0.10-alpha.
3106 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
3107 - Avoid a sandbox failure when trying to re-bind to a socket and
3108 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
3110 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
3111 - Permit the fchmod system call, to avoid crashing on startup when
3112 starting with the seccomp2 sandbox and an unexpected set of
3113 permissions on the data directory or its contents. Fixes bug
3114 22516; bugfix on 0.2.5.4-alpha.
3116 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
3117 - Avoid a double-marked-circuit warning that could happen when we
3118 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
3121 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
3122 - Reject version numbers with non-numeric prefixes (such as +, -, or
3123 whitespace). Disallowing whitespace prevents differential version
3124 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3125 and part of 21508; bugfix on 0.0.8pre1.
3127 o Build features (backport from 0.3.1.5-alpha):
3128 - Tor's repository now includes a Travis Continuous Integration (CI)
3129 configuration file (.travis.yml). This is meant to help new
3130 developers and contributors who fork Tor to a Github repository be
3131 better able to test their changes, and understand what we expect
3132 to pass. To use this new build feature, you must fork Tor to your
3133 Github account, then go into the "Integrations" menu in the
3134 repository settings for your fork and enable Travis, then push
3135 your changes. Closes ticket 22636.
3138 Changes in version 0.3.0.11 - 2017-09-18
3139 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
3142 Most significantly, it includes a fix for TROVE-2017-008, a
3143 security bug that affects hidden services running with the
3144 SafeLogging option disabled. For more information, see
3145 https://trac.torproject.org/projects/tor/ticket/23490
3147 o Minor features (code style, backport from 0.3.1.7):
3148 - Add "Falls through" comments to our codebase, in order to silence
3149 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3150 Stieger. Closes ticket 22446.
3153 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3156 o Minor bugfixes (compilation, backport from 0.3.1.7):
3157 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
3158 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3160 o Minor bugfixes (controller, backport from 0.3.1.7):
3161 - Do not crash when receiving a HSPOST command with an empty body.
3162 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3163 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
3164 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3166 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
3167 - When setting the maximum number of connections allowed by the OS,
3168 always allow some extra file descriptors for other files. Fixes
3169 bug 22797; bugfix on 0.2.0.10-alpha.
3171 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
3172 - Remove a forgotten debugging message when an introduction point
3173 successfully establishes a hidden service prop224 circuit with
3175 - Change three other log_warn() for an introduction point to
3176 protocol warnings, because they can be failure from the network
3177 and are not relevant to the operator. Fixes bug 23078; bugfix on
3178 0.3.0.1-alpha and 0.3.0.2-alpha.
3181 Changes in version 0.3.1.7 - 2017-09-18
3182 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
3184 With the 0.3.1 series, Tor now serves and downloads directory
3185 information in more compact formats, to save on bandwidth overhead. It
3186 also contains a new padding system to resist netflow-based traffic
3187 analysis, and experimental support for building parts of Tor in Rust
3188 (though no parts of Tor are in Rust yet). There are also numerous
3189 small features, bugfixes on earlier release series, and groundwork for
3190 the hidden services revamp of 0.3.2.
3192 This release also includes a fix for TROVE-2017-008, a security bug
3193 that affects hidden services running with the SafeLogging option
3194 disabled. For more information, see
3195 https://trac.torproject.org/projects/tor/ticket/23490
3197 Per our stable release policy, we plan to support each stable release
3198 series for at least the next nine months, or for three months after
3199 the first stable release of the next series: whichever is longer. If
3200 you need a release with long-term support, we recommend that you stay
3201 with the 0.2.9 series.
3203 Below is a list of the changes since 0.3.0. For a list of all
3204 changes since 0.3.1.6-rc, see the ChangeLog file.
3207 - To build with zstd and lzma support, Tor now requires the
3208 pkg-config tool at build time.
3210 o Major bugfixes (security, hidden services, loggging):
3211 - Fix a bug where we could log uninitialized stack when a certain
3212 hidden service error occurred while SafeLogging was disabled.
3213 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
3214 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
3216 o Major features (build system, continuous integration):
3217 - Tor's repository now includes a Travis Continuous Integration (CI)
3218 configuration file (.travis.yml). This is meant to help new
3219 developers and contributors who fork Tor to a Github repository be
3220 better able to test their changes, and understand what we expect
3221 to pass. To use this new build feature, you must fork Tor to your
3222 Github account, then go into the "Integrations" menu in the
3223 repository settings for your fork and enable Travis, then push
3224 your changes. Closes ticket 22636.
3226 o Major features (directory protocol):
3227 - Tor relays and authorities can now serve clients an abbreviated
3228 version of the consensus document, containing only the changes
3229 since an older consensus document that the client holds. Clients
3230 now request these documents when available. When both client and
3231 server use this new protocol, they will use far less bandwidth (up
3232 to 94% less) to keep the client's consensus up-to-date. Implements
3233 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
3234 - Tor can now compress directory traffic with lzma or with zstd
3235 compression algorithms, which can deliver better bandwidth
3236 performance. Because lzma is computationally expensive, it's only
3237 used for documents that can be compressed once and served many
3238 times. Support for these algorithms requires that tor is built
3239 with the libzstd and/or liblzma libraries available. Implements
3240 proposal 278; closes ticket 21662.
3241 - Relays now perform the more expensive compression operations, and
3242 consensus diff generation, in worker threads. This separation
3243 avoids delaying the main thread when a new consensus arrives.
3245 o Major features (experimental):
3246 - Tor can now build modules written in Rust. To turn this on, pass
3247 the "--enable-rust" flag to the configure script. It's not time to
3248 get excited yet: currently, there is no actual Rust functionality
3249 beyond some simple glue code, and a notice at startup to tell you
3250 that Rust is running. Still, we hope that programmers and
3251 packagers will try building Tor with Rust support, so that we can
3252 find issues and solve portability problems. Closes ticket 22106.
3254 o Major features (traffic analysis resistance):
3255 - Connections between clients and relays now send a padding cell in
3256 each direction every 1.5 to 9.5 seconds (tunable via consensus
3257 parameters). This padding will not resist specialized
3258 eavesdroppers, but it should be enough to make many ISPs' routine
3259 network flow logging less useful in traffic analysis against
3262 Padding is negotiated using Tor's link protocol, so both relays
3263 and clients must upgrade for this to take effect. Clients may
3264 still send padding despite the relay's version by setting
3265 ConnectionPadding 1 in torrc, and may disable padding by setting
3266 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
3267 users with the torrc option ReducedConnectionPadding. Implements
3268 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
3269 - Relays will publish 24 hour totals of padding and non-padding cell
3270 counts to their extra-info descriptors, unless PaddingStatistics 0
3271 is set in torrc. These 24 hour totals are also rounded to
3274 o Major bugfixes (hidden service, relay, security):
3275 - Fix a remotely triggerable assertion failure when a hidden service
3276 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
3277 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
3278 - Fix a remotely triggerable assertion failure caused by receiving a
3279 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3280 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3283 o Major bugfixes (path selection, security):
3284 - When choosing which guard to use for a circuit, avoid the exit's
3285 family along with the exit itself. Previously, the new guard
3286 selection logic avoided the exit, but did not consider its family.
3287 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
3288 006 and CVE-2017-0377.
3290 o Major bugfixes (connection usage):
3291 - We use NETINFO cells to try to determine if both relays involved
3292 in a connection will agree on the canonical status of that
3293 connection. We prefer the connections where this is the case for
3294 extend cells, and try to close connections where relays disagree
3295 on their canonical status early. Also, we now prefer the oldest
3296 valid connection for extend cells. These two changes should reduce
3297 the number of long-term connections that are kept open between
3298 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
3299 - Relays now log hourly statistics (look for
3300 "channel_check_for_duplicates" lines) on the total number of
3301 connections to other relays. If the number of connections per
3302 relay is unexpectedly large, this log message is at notice level.
3303 Otherwise it is at info.
3305 o Major bugfixes (entry guards):
3306 - When starting with an old consensus, do not add new entry guards
3307 unless the consensus is "reasonably live" (under 1 day old). Fixes
3308 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
3309 - Don't block bootstrapping when a primary bridge is offline and we
3310 can't get its descriptor. Fixes bug 22325; fixes one case of bug
3311 21969; bugfix on 0.3.0.3-alpha.
3313 o Major bugfixes (linux TPROXY support):
3314 - Fix a typo that had prevented TPROXY-based transparent proxying
3315 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3316 Patch from "d4fq0fQAgoJ".
3318 o Major bugfixes (openbsd, denial-of-service):
3319 - Avoid an assertion failure bug affecting our implementation of
3320 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3321 handling of "0xx" differs from what we had expected. Fixes bug
3322 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3324 o Major bugfixes (relay, link handshake):
3325 - When performing the v3 link handshake on a TLS connection, report
3326 that we have the x509 certificate that we actually used on that
3327 connection, even if we have changed certificates since that
3328 connection was first opened. Previously, we would claim to have
3329 used our most recent x509 link certificate, which would sometimes
3330 make the link handshake fail. Fixes one case of bug 22460; bugfix
3333 o Major bugfixes (relays, key management):
3334 - Regenerate link and authentication certificates whenever the key
3335 that signs them changes; also, regenerate link certificates
3336 whenever the signed key changes. Previously, these processes were
3337 only weakly coupled, and we relays could (for minutes to hours)
3338 wind up with an inconsistent set of keys and certificates, which
3339 other relays would not accept. Fixes two cases of bug 22460;
3340 bugfix on 0.3.0.1-alpha.
3341 - When sending an Ed25519 signing->link certificate in a CERTS cell,
3342 send the certificate that matches the x509 certificate that we
3343 used on the TLS connection. Previously, there was a race condition
3344 if the TLS context rotated after we began the TLS handshake but
3345 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
3348 o Minor features (security, windows):
3349 - Enable a couple of pieces of Windows hardening: one
3350 (HeapEnableTerminationOnCorruption) that has been on-by-default
3351 since Windows 8, and unavailable before Windows 7; and one
3352 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
3353 affect us, but shouldn't do any harm. Closes ticket 21953.
3355 o Minor features (bridge authority):
3356 - Add "fingerprint" lines to the networkstatus-bridges file produced
3357 by bridge authorities. Closes ticket 22207.
3359 o Minor features (code style):
3360 - Add "Falls through" comments to our codebase, in order to silence
3361 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3362 Stieger. Closes ticket 22446.
3364 o Minor features (config options):
3365 - Allow "%include" directives in torrc configuration files. These
3366 directives import the settings from other files, or from all the
3367 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
3368 - Make SAVECONF return an error when overwriting a torrc that has
3369 includes. Using SAVECONF with the FORCE option will allow it to
3370 overwrite torrc even if includes are used. Related to ticket 1922.
3371 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
3372 will work without the FORCE option. Related to ticket 1922.
3374 o Minor features (controller):
3375 - Warn the first time that a controller requests data in the long-
3376 deprecated 'GETINFO network-status' format. Closes ticket 21703.
3378 o Minor features (defaults):
3379 - The default value for UseCreateFast is now 0: clients which
3380 haven't yet received a consensus document will now use a proper
3381 ntor handshake to talk to their directory servers whenever they
3382 can. Closes ticket 21407.
3383 - Onion key rotation and expiry intervals are now defined as a
3384 network consensus parameter, per proposal 274. The default
3385 lifetime of an onion key is increased from 7 to 28 days. Old onion
3386 keys will expire after 7 days by default. This change will make
3387 consensus diffs much smaller, and save significant bandwidth.
3388 Closes ticket 21641.
3390 o Minor features (defensive programming):
3391 - Create a pair of consensus parameters, nf_pad_tor2web and
3392 nf_pad_single_onion, to disable netflow padding in the consensus
3393 for non-anonymous connections in case the overhead is high. Closes
3396 o Minor features (diagnostic):
3397 - Add a stack trace to the bug warnings that can be logged when
3398 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
3399 attempt for bug 23105.
3400 - Add logging messages to try to diagnose a rare bug that seems to
3401 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
3402 think this is happening because of incorrect system clocks, but
3403 we'd like to know for certain. Diagnostic for bug 22466.
3404 - Avoid an assertion failure, and log a better error message, when
3405 unable to remove a file from the consensus cache on Windows.
3406 Attempts to mitigate and diagnose bug 22752.
3408 o Minor features (directory authority):
3409 - Improve the message that authorities report to relays that present
3410 RSA/Ed25519 keypairs that conflict with previously pinned keys.
3411 Closes ticket 22348.
3413 o Minor features (directory cache, consensus diff):
3414 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
3415 operators with low-resource environments to adjust the number of
3416 consensuses they'll store and generate diffs from. Most cache
3417 operators should leave it unchanged. Helps to work around
3420 o Minor features (fallback directory list):
3421 - Update the fallback directory mirror whitelist and blacklist based
3422 on operator emails. Closes task 21121.
3423 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
3424 December 2016 (of which ~126 were still functional) with a list of
3425 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
3426 2017. Resolves ticket 21564.
3428 o Minor features (geoip):
3429 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3432 o Minor features (hidden services, logging):
3433 - Log a message when a hidden service descriptor has fewer
3434 introduction points than specified in
3435 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
3436 - Log a message when a hidden service reaches its introduction point
3437 circuit limit, and when that limit is reset. Follow up to ticket
3438 21594; closes ticket 21622.
3439 - Warn user if multiple entries in EntryNodes and at least one
3440 HiddenService are used together. Pinning EntryNodes along with a
3441 hidden service can be possibly harmful; for instance see ticket
3442 14917 or 21155. Closes ticket 21155.
3444 o Minor features (linux seccomp2 sandbox):
3445 - We now have a document storage backend compatible with the Linux
3446 seccomp2 sandbox. This backend is used for consensus documents and
3447 diffs between them; in the long term, we'd like to use it for
3448 unparseable directory material too. Closes ticket 21645
3449 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
3450 from 1MB to 16MB. This was necessary with the glibc allocator in
3451 order to allow worker threads to allocate more memory -- which in
3452 turn is necessary because of our new use of worker threads for
3453 compression. Closes ticket 22096.
3455 o Minor features (logging):
3456 - Log files are no longer created world-readable by default.
3457 (Previously, most distributors would store the logs in a non-
3458 world-readable location to prevent inappropriate access. This
3459 change is an extra precaution.) Closes ticket 21729; patch
3462 o Minor features (performance):
3463 - Our Keccak (SHA-3) implementation now accesses memory more
3464 efficiently, especially on little-endian systems. Closes
3466 - Add an O(1) implementation of channel_find_by_global_id(), to
3467 speed some controller functions.
3469 o Minor features (relay, configuration):
3470 - The MyFamily option may now be repeated as many times as desired,
3471 for relays that want to configure large families. Closes ticket
3472 4998; patch by Daniel Pinto.
3474 o Minor features (relay, performance):
3475 - Always start relays with at least two worker threads, to prevent
3476 priority inversion on slow tasks. Part of the fix for bug 22883.
3477 - Allow background work to be queued with different priorities, so
3478 that a big pile of slow low-priority jobs will not starve out
3479 higher priority jobs. This lays the groundwork for a fix for
3482 o Minor features (safety):
3483 - Add an explicit check to extrainfo_parse_entry_from_string() for
3484 NULL inputs. We don't believe this can actually happen, but it may
3485 help silence a warning from the Clang analyzer. Closes
3488 o Minor features (testing):
3489 - Add more tests for compression backend initialization. Closes
3491 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
3492 When Tor is compiled with this option, we disable a number of
3493 redundant memory-safety failsafes that are intended to stop bugs
3494 from becoming security issues. This makes it easier to hunt for
3495 bugs that would be security issues without the failsafes turned
3496 on. Closes ticket 21439.
3497 - Add a general event-tracing instrumentation support to Tor. This
3498 subsystem will enable developers and researchers to add fine-
3499 grained instrumentation to their Tor instances, for use when
3500 examining Tor network performance issues. There are no trace
3501 events yet, and event-tracing is off by default unless enabled at
3502 compile time. Implements ticket 13802.
3503 - Improve our version parsing tests: add tests for typical version
3504 components, add tests for invalid versions, including numeric
3505 range and non-numeric prefixes. Unit tests 21278, 21450, and
3506 21507. Partially implements 21470.
3508 o Minor bugfixes (bandwidth accounting):
3509 - Roll over monthly accounting at the configured hour and minute,
3510 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3511 Found by Andrey Karpov with PVS-Studio.
3513 o Minor bugfixes (code correctness):
3514 - Accurately identify client connections by their lack of peer
3515 authentication. This means that we bail out earlier if asked to
3516 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
3519 o Minor bugfixes (compilation warnings):
3520 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
3521 22915; bugfix on 0.2.8.1-alpha.
3522 - Fix warnings when building with libscrypt and openssl scrypt
3523 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3524 - When building with certain versions of the mingw C header files,
3525 avoid float-conversion warnings when calling the C functions
3526 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
3529 o Minor bugfixes (compilation):
3530 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
3531 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3533 o Minor bugfixes (compression):
3534 - When spooling compressed data to an output buffer, don't try to
3535 spool more data when there is no more data to spool and we are not
3536 trying to flush the input. Previously, we would sometimes launch
3537 compression requests with nothing to do, which interferes with our
3538 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
3540 o Minor bugfixes (configuration):
3541 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
3542 bug 22252; bugfix on 0.2.9.3-alpha.
3544 o Minor bugfixes (connection lifespan):
3545 - Allow more control over how long TLS connections are kept open:
3546 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
3547 single option called CircuitsAvailableTimeout. Also, allow the
3548 consensus to control the default values for both this preference
3549 and the lifespan of relay-to-relay connections. Fixes bug 17592;
3550 bugfix on 0.2.5.5-alpha.
3551 - Increase the initial circuit build timeout testing frequency, to
3552 help ensure that ReducedConnectionPadding clients finish learning
3553 a timeout before their orconn would expire. The initial testing
3554 rate was set back in the days of TAP and before the Tor Browser
3555 updater, when we had to be much more careful about new clients
3556 making lots of circuits. With this change, a circuit build timeout
3557 is learned in about 15-20 minutes, instead of 100-120 minutes.
3559 o Minor bugfixes (controller):
3560 - Do not crash when receiving a HSPOST command with an empty body.
3561 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3562 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
3563 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3564 - GETINFO onions/current and onions/detached no longer respond with
3565 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
3566 - Trigger HS descriptor events on the control port when the client
3567 fails to pick a hidden service directory for a hidden service.
3568 This can happen if all the hidden service directories are in
3569 ExcludeNodes, or they have all been queried within the last 15
3570 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
3572 o Minor bugfixes (correctness):
3573 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
3574 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
3576 o Minor bugfixes (coverity build support):
3577 - Avoid Coverity build warnings related to our BUG() macro. By
3578 default, Coverity treats BUG() as the Linux kernel does: an
3579 instant abort(). We need to override that so our BUG() macro
3580 doesn't prevent Coverity from analyzing functions that use it.
3581 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3583 o Minor bugfixes (defensive programming):
3584 - Detect and break out of infinite loops in our compression code. We
3585 don't think that any such loops exist now, but it's best to be
3586 safe. Closes ticket 22672.
3587 - Fix a memset() off the end of an array when packing cells. This
3588 bug should be harmless in practice, since the corrupted bytes are
3589 still in the same structure, and are always padding bytes,
3590 ignored, or immediately overwritten, depending on compiler
3591 behavior. Nevertheless, because the memset()'s purpose is to make
3592 sure that any other cell-handling bugs can't expose bytes to the
3593 network, we need to fix it. Fixes bug 22737; bugfix on
3594 0.2.4.11-alpha. Fixes CID 1401591.
3596 o Minor bugfixes (directory authority):
3597 - When a directory authority rejects a descriptor or extrainfo with
3598 a given digest, mark that digest as undownloadable, so that we do
3599 not attempt to download it again over and over. We previously
3600 tried to avoid downloading such descriptors by other means, but we
3601 didn't notice if we accidentally downloaded one anyway. This
3602 behavior became problematic in 0.2.7.2-alpha, when authorities
3603 began pinning Ed25519 keys. Fixes bug 22349; bugfix
3605 - When rejecting a router descriptor for running an obsolete version
3606 of Tor without ntor support, warn about the obsolete tor version,
3607 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
3608 - Prevent the shared randomness subsystem from asserting when
3609 initialized by a bridge authority with an incomplete configuration
3610 file. Fixes bug 21586; bugfix on 0.2.9.8.
3612 o Minor bugfixes (error reporting, windows):
3613 - When formatting Windows error messages, use the English format to
3614 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
3617 o Minor bugfixes (exit-side DNS):
3618 - Fix an untriggerable assertion that checked the output of a
3619 libevent DNS error, so that the assertion actually behaves as
3620 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
3621 Karpov using PVS-Studio.
3623 o Minor bugfixes (fallback directories):
3624 - Make the usage example in updateFallbackDirs.py actually work, and
3625 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
3626 - Decrease the guard flag average required to be a fallback. This
3627 allows us to keep relays that have their guard flag removed when
3628 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
3629 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
3630 bugfix on 0.2.8.1-alpha.
3631 - Make sure fallback directory mirrors have the same address, port,
3632 and relay identity key for at least 30 days before they are
3633 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
3635 o Minor bugfixes (file limits, osx):
3636 - When setting the maximum number of connections allowed by the OS,
3637 always allow some extra file descriptors for other files. Fixes
3638 bug 22797; bugfix on 0.2.0.10-alpha.
3640 o Minor bugfixes (hidden services):
3641 - Increase the number of circuits that a service is allowed to
3642 open over a specific period of time. The value was lower than it
3643 should be (8 vs 12) in the normal case of 3 introduction points.
3644 Fixes bug 22159; bugfix on 0.3.0.5-rc.
3645 - Fix a BUG warning during HSv3 descriptor decoding that could be
3646 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
3647 on 0.3.0.1-alpha. Bug found by "haxxpop".
3648 - Stop printing a cryptic warning when a hidden service gets a
3649 request to connect to a virtual port that it hasn't configured.
3650 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
3651 - Simplify hidden service descriptor creation by using an existing
3652 flag to check if an introduction point is established. Fixes bug
3653 21599; bugfix on 0.2.7.2-alpha.
3655 o Minor bugfixes (link handshake):
3656 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
3657 months, and regenerate it when it is within one month of expiring.
3658 Previously, we had generated this certificate at startup with a
3659 ten-year lifetime, but that could lead to weird behavior when Tor
3660 was started with a grossly inaccurate clock. Mitigates bug 22466;
3661 mitigation on 0.3.0.1-alpha.
3663 o Minor bugfixes (linux seccomp2 sandbox):
3664 - Avoid a sandbox failure when trying to re-bind to a socket and
3665 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-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 (logging):
3672 - When decompressing, do not warn if we fail to decompress using a
3673 compression method that we merely guessed. Fixes part of bug
3674 22670; bugfix on 0.1.1.14-alpha.
3675 - When decompressing, treat mismatch between content-encoding and
3676 actual compression type as a protocol warning. Fixes part of bug
3677 22670; bugfix on 0.1.1.9-alpha.
3678 - Downgrade "assigned_to_cpuworker failed" message to info-level
3679 severity. In every case that can reach it, either a better warning
3680 has already been logged, or no warning is warranted. Fixes bug
3681 22356; bugfix on 0.2.6.3-alpha.
3682 - Log a better message when a directory authority replies to an
3683 upload with an unexpected status code. Fixes bug 11121; bugfix
3685 - Downgrade a log statement about unexpected relay cells from "bug"
3686 to "protocol warning", because there is at least one use case
3687 where it can be triggered by a buggy tor implementation. Fixes bug
3688 21293; bugfix on 0.1.1.14-alpha.
3690 o Minor bugfixes (logging, relay):
3691 - Remove a forgotten debugging message when an introduction point
3692 successfully establishes a hidden service prop224 circuit with
3694 - Change three other log_warn() for an introduction point to
3695 protocol warnings, because they can be failure from the network
3696 and are not relevant to the operator. Fixes bug 23078; bugfix on
3697 0.3.0.1-alpha and 0.3.0.2-alpha.
3699 o Minor bugfixes (relay):
3700 - Inform the geoip and rephist modules about all requests, even on
3701 relays that are only fetching microdescriptors. Fixes a bug
3702 related to 21585; bugfix on 0.3.0.1-alpha.
3704 o Minor bugfixes (memory leaks):
3705 - Fix a small memory leak at exit from the backtrace handler code.
3706 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
3707 - When directory authorities reject a router descriptor due to
3708 keypinning, free the router descriptor rather than leaking the
3709 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
3710 - Fix a small memory leak when validating a configuration that uses
3711 two or more AF_UNIX sockets for the same port type. Fixes bug
3712 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
3714 o Minor bugfixes (process behavior):
3715 - When exiting because of an error, always exit with a nonzero exit
3716 status. Previously, we would fail to report an error in our exit
3717 status in cases related to __OwningControllerProcess failure,
3718 lockfile contention, and Ed25519 key initialization. Fixes bug
3719 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
3720 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
3723 o Minor bugfixes (robustness, error handling):
3724 - Improve our handling of the cases where OpenSSL encounters a
3725 memory error while encoding keys and certificates. We haven't
3726 observed these errors in the wild, but if they do happen, we now
3727 detect and respond better. Fixes bug 19418; bugfix on all versions
3728 of Tor. Reported by Guido Vranken.
3730 o Minor bugfixes (testing):
3731 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
3732 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
3733 - Use unbuffered I/O for utility functions around the
3734 process_handle_t type. This fixes unit test failures reported on
3735 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
3736 - Make display of captured unit test log messages consistent. Fixes
3737 bug 21510; bugfix on 0.2.9.3-alpha.
3738 - Make test-network.sh always call chutney's test-network.sh.
3739 Previously, this only worked on systems which had bash installed,
3740 due to some bash-specific code in the script. Fixes bug 19699;
3741 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
3742 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
3743 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
3744 - The unit tests now pass on systems where localhost is misconfigured
3745 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
3748 o Minor bugfixes (voting consistency):
3749 - Reject version numbers with non-numeric prefixes (such as +, -, or
3750 whitespace). Disallowing whitespace prevents differential version
3751 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3752 and part of 21508; bugfix on 0.0.8pre1.
3754 o Minor bugfixes (Windows service):
3755 - When running as a Windows service, set the ID of the main thread
3756 correctly. Failure to do so made us fail to send log messages to
3757 the controller in 0.2.1.16-rc, slowed down controller event
3758 delivery in 0.2.7.3-rc and later, and crash with an assertion
3759 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
3760 Patch and diagnosis from "Vort".
3762 o Minor bugfixes (windows, relay):
3763 - Resolve "Failure from drain_fd: No error" warnings on Windows
3764 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
3766 o Code simplification and refactoring:
3767 - Break up the 630-line function connection_dir_client_reached_eof()
3768 into a dozen smaller functions. This change should help
3769 maintainability and readability of the client directory code.
3770 - Isolate our use of the openssl headers so that they are only
3771 included from our crypto wrapper modules, and from tests that
3772 examine those modules' internals. Closes ticket 21841.
3773 - Simplify our API to launch directory requests, making it more
3774 extensible and less error-prone. Now it's easier to add extra
3775 headers to directory requests. Closes ticket 21646.
3776 - Our base64 decoding functions no longer overestimate the output
3777 space that they need when parsing unpadded inputs. Closes
3779 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
3780 Resolves ticket 22213.
3781 - The logic that directory caches use to spool request to clients,
3782 serving them one part at a time so as not to allocate too much
3783 memory, has been refactored for consistency. Previously there was
3784 a separate spooling implementation per type of spoolable data. Now
3785 there is one common spooling implementation, with extensible data
3786 types. Closes ticket 21651.
3787 - Tor's compression module now supports multiple backends. Part of
3788 the implementation for proposal 278; closes ticket 21663.
3791 - Add a manpage description for the key-pinning-journal file. Closes
3793 - Correctly note that bandwidth accounting values are stored in the
3794 state file, and the bw_accounting file is now obsolete. Closes
3796 - Document more of the files in the Tor data directory, including
3797 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
3798 approved-routers, sr-random, and diff-cache. Found while fixing
3800 - Clarify the manpage for the (deprecated) torify script. Closes
3802 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
3803 Closes ticket 21873.
3804 - Correct documentation about the default DataDirectory value.
3805 Closes ticket 21151.
3806 - Document the default behavior of NumEntryGuards and
3807 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
3809 - Document key=value pluggable transport arguments for Bridge lines
3810 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
3811 - Note that bandwidth-limiting options don't affect TCP headers or
3812 DNS. Closes ticket 17170.
3814 o Removed features (configuration options, all in ticket 22060):
3815 - These configuration options are now marked Obsolete, and no longer
3816 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
3817 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
3818 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
3819 in 0.2.9.2-alpha and have now been removed. The previous default
3820 behavior is now always chosen; the previous (less secure) non-
3821 default behavior is now unavailable.
3822 - CloseHSClientCircuitsImmediatelyOnTimeout and
3823 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
3824 0.2.9.2-alpha and now have been removed. HS circuits never close
3825 on circuit build timeout; they have a longer timeout period.
3826 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
3827 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
3828 (and others) to configure listen-only and advertise-only addresses.
3830 o Removed features (tools):
3831 - We've removed the tor-checkkey tool from src/tools. Long ago, we
3832 used it to help people detect RSA keys that were generated by
3833 versions of Debian affected by CVE-2008-0166. But those keys have
3834 been out of circulation for ages, and this tool is no longer
3835 required. Closes ticket 21842.
3838 Changes in version 0.3.0.10 - 2017-08-02
3839 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
3840 from the current Tor alpha series. OpenBSD users and TPROXY users
3841 should upgrade; others are probably okay sticking with 0.3.0.9.
3843 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
3844 - Tor's repository now includes a Travis Continuous Integration (CI)
3845 configuration file (.travis.yml). This is meant to help new
3846 developers and contributors who fork Tor to a Github repository be
3847 better able to test their changes, and understand what we expect
3848 to pass. To use this new build feature, you must fork Tor to your
3849 Github account, then go into the "Integrations" menu in the
3850 repository settings for your fork and enable Travis, then push
3851 your changes. Closes ticket 22636.
3853 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
3854 - Fix a typo that had prevented TPROXY-based transparent proxying
3855 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3856 Patch from "d4fq0fQAgoJ".
3858 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3859 - Avoid an assertion failure bug affecting our implementation of
3860 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3861 handling of "0xbar" differs from what we had expected. Fixes bug
3862 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3864 o Minor features (backport from 0.3.1.5-alpha):
3865 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
3868 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
3869 - Roll over monthly accounting at the configured hour and minute,
3870 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3871 Found by Andrey Karpov with PVS-Studio.
3873 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
3874 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
3875 bugfix on 0.2.8.1-alpha.
3876 - Fix warnings when building with libscrypt and openssl scrypt
3877 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3878 - When building with certain versions of the mingw C header files,
3879 avoid float-conversion warnings when calling the C functions
3880 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
3883 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3884 - Backport a fix for an "unused variable" warning that appeared
3885 in some versions of mingw. Fixes bug 22838; bugfix on
3888 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
3889 - Avoid Coverity build warnings related to our BUG() macro. By
3890 default, Coverity treats BUG() as the Linux kernel does: an
3891 instant abort(). We need to override that so our BUG() macro
3892 doesn't prevent Coverity from analyzing functions that use it.
3893 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3895 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
3896 - When rejecting a router descriptor for running an obsolete version
3897 of Tor without ntor support, warn about the obsolete tor version,
3898 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
3900 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
3901 - Avoid a sandbox failure when trying to re-bind to a socket and
3902 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
3904 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
3905 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
3906 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
3909 Changes in version 0.3.0.9 - 2017-06-29
3910 Tor 0.3.0.9 fixes a path selection bug that would allow a client
3911 to use a guard that was in the same network family as a chosen exit
3912 relay. This is a security regression; all clients running earlier
3913 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
3916 This release also backports several other bugfixes from the 0.3.1.x
3919 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
3920 - When choosing which guard to use for a circuit, avoid the exit's
3921 family along with the exit itself. Previously, the new guard
3922 selection logic avoided the exit, but did not consider its family.
3923 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
3924 006 and CVE-2017-0377.
3926 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
3927 - Don't block bootstrapping when a primary bridge is offline and we
3928 can't get its descriptor. Fixes bug 22325; fixes one case of bug
3929 21969; bugfix on 0.3.0.3-alpha.
3931 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
3932 - When starting with an old consensus, do not add new entry guards
3933 unless the consensus is "reasonably live" (under 1 day old). Fixes
3934 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
3936 o Minor features (geoip):
3937 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
3940 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
3941 - Reject version numbers with non-numeric prefixes (such as +, -, or
3942 whitespace). Disallowing whitespace prevents differential version
3943 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3944 and part of 21508; bugfix on 0.0.8pre1.
3946 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
3947 - Permit the fchmod system call, to avoid crashing on startup when
3948 starting with the seccomp2 sandbox and an unexpected set of
3949 permissions on the data directory or its contents. Fixes bug
3950 22516; bugfix on 0.2.5.4-alpha.
3952 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
3953 - Fix a memset() off the end of an array when packing cells. This
3954 bug should be harmless in practice, since the corrupted bytes are
3955 still in the same structure, and are always padding bytes,
3956 ignored, or immediately overwritten, depending on compiler
3957 behavior. Nevertheless, because the memset()'s purpose is to make
3958 sure that any other cell-handling bugs can't expose bytes to the
3959 network, we need to fix it. Fixes bug 22737; bugfix on
3960 0.2.4.11-alpha. Fixes CID 1401591.
3963 Changes in version 0.3.0.8 - 2017-06-08
3964 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
3965 remotely crash a hidden service with an assertion failure. Anyone
3966 running a hidden service should upgrade to this version, or to some
3967 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
3969 Tor 0.3.0.8 also includes fixes for several key management bugs
3970 that sometimes made relays unreliable, as well as several other
3971 bugfixes described below.
3973 o Major bugfixes (hidden service, relay, security, backport
3974 from 0.3.1.3-alpha):
3975 - Fix a remotely triggerable assertion failure when a hidden service
3976 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
3977 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
3978 - Fix a remotely triggerable assertion failure caused by receiving a
3979 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
3980 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
3983 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
3984 - When performing the v3 link handshake on a TLS connection, report
3985 that we have the x509 certificate that we actually used on that
3986 connection, even if we have changed certificates since that
3987 connection was first opened. Previously, we would claim to have
3988 used our most recent x509 link certificate, which would sometimes
3989 make the link handshake fail. Fixes one case of bug 22460; bugfix
3992 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
3993 - Regenerate link and authentication certificates whenever the key
3994 that signs them changes; also, regenerate link certificates
3995 whenever the signed key changes. Previously, these processes were
3996 only weakly coupled, and we relays could (for minutes to hours)
3997 wind up with an inconsistent set of keys and certificates, which
3998 other relays would not accept. Fixes two cases of bug 22460;
3999 bugfix on 0.3.0.1-alpha.
4000 - When sending an Ed25519 signing->link certificate in a CERTS cell,
4001 send the certificate that matches the x509 certificate that we
4002 used on the TLS connection. Previously, there was a race condition
4003 if the TLS context rotated after we began the TLS handshake but
4004 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
4007 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
4008 - Stop rejecting v3 hidden service descriptors because their size
4009 did not match an old padding rule. Fixes bug 22447; bugfix on
4012 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4013 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4014 December 2016 (of which ~126 were still functional) with a list of
4015 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4016 2017. Resolves ticket 21564.
4018 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
4019 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
4020 bug 22252; bugfix on 0.2.9.3-alpha.
4022 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
4023 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4024 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4026 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
4027 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
4028 months, and regenerate it when it is within one month of expiring.
4029 Previously, we had generated this certificate at startup with a
4030 ten-year lifetime, but that could lead to weird behavior when Tor
4031 was started with a grossly inaccurate clock. Mitigates bug 22466;
4032 mitigation on 0.3.0.1-alpha.
4034 o Minor bugfixes (memory leak, directory authority, backport from
4036 - When directory authorities reject a router descriptor due to
4037 keypinning, free the router descriptor rather than leaking the
4038 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4041 Changes in version 0.2.9.11 - 2017-06-08
4042 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
4043 remotely crash a hidden service with an assertion failure. Anyone
4044 running a hidden service should upgrade to this version, or to some
4045 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4046 are not affected by TROVE-2017-004.)
4048 Tor 0.2.9.11 also backports fixes for several key management bugs
4049 that sometimes made relays unreliable, as well as several other
4050 bugfixes described below.
4052 o Major bugfixes (hidden service, relay, security, backport
4053 from 0.3.1.3-alpha):
4054 - Fix a remotely triggerable assertion failure caused by receiving a
4055 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4056 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4059 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
4060 - When performing the v3 link handshake on a TLS connection, report
4061 that we have the x509 certificate that we actually used on that
4062 connection, even if we have changed certificates since that
4063 connection was first opened. Previously, we would claim to have
4064 used our most recent x509 link certificate, which would sometimes
4065 make the link handshake fail. Fixes one case of bug 22460; bugfix
4068 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4069 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4070 December 2016 (of which ~126 were still functional) with a list of
4071 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4072 2017. Resolves ticket 21564.
4074 o Minor features (future-proofing, backport from 0.3.0.7):
4075 - Tor no longer refuses to download microdescriptors or descriptors if
4076 they are listed as "published in the future". This change will
4077 eventually allow us to stop listing meaningful "published" dates
4078 in microdescriptor consensuses, and thereby allow us to reduce the
4079 resources required to download consensus diffs by over 50%.
4080 Implements part of ticket 21642; implements part of proposal 275.
4082 o Minor features (directory authorities, backport from 0.3.0.4-rc)
4083 - Directory authorities now reject relays running versions
4084 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
4085 suffer from bug 20499 and don't keep their consensus cache
4086 up-to-date. Resolves ticket 20509.
4088 o Minor features (geoip):
4089 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4092 o Minor bugfixes (control port, backport from 0.3.0.6):
4093 - The GETINFO extra-info/digest/<digest> command was broken because
4094 of a wrong base16 decode return value check, introduced when
4095 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
4097 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
4098 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4099 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4101 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
4102 - The getpid() system call is now permitted under the Linux seccomp2
4103 sandbox, to avoid crashing with versions of OpenSSL (and other
4104 libraries) that attempt to learn the process's PID by using the
4105 syscall rather than the VDSO code. Fixes bug 21943; bugfix
4108 o Minor bugfixes (memory leak, directory authority, backport
4109 from 0.3.1.2-alpha):
4110 - When directory authorities reject a router descriptor due to
4111 keypinning, free the router descriptor rather than leaking the
4112 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4114 Changes in version 0.2.8.14 - 2017-06-08
4115 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4116 remotely crash a hidden service with an assertion failure. Anyone
4117 running a hidden service should upgrade to this version, or to some
4118 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4119 are not affected by TROVE-2017-004.)
4121 o Major bugfixes (hidden service, relay, security):
4122 - Fix a remotely triggerable assertion failure caused by receiving a
4123 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4124 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4127 o Minor features (geoip):
4128 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4131 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4132 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4133 December 2016 (of which ~126 were still functional) with a list of
4134 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4135 2017. Resolves ticket 21564.
4137 o Minor bugfixes (correctness):
4138 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4139 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4141 Changes in version 0.2.7.8 - 2017-06-08
4142 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4143 remotely crash a hidden service with an assertion failure. Anyone
4144 running a hidden service should upgrade to this version, or to some
4145 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4146 are not affected by TROVE-2017-004.)
4148 o Major bugfixes (hidden service, relay, security):
4149 - Fix a remotely triggerable assertion failure caused by receiving a
4150 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4151 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4154 o Minor features (geoip):
4155 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4158 o Minor bugfixes (correctness):
4159 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4160 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4163 Changes in version 0.2.6.12 - 2017-06-08
4164 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
4165 remotely crash a hidden service with an assertion failure. Anyone
4166 running a hidden service should upgrade to this version, or to some
4167 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4168 are not affected by TROVE-2017-004.)
4170 o Major bugfixes (hidden service, relay, security):
4171 - Fix a remotely triggerable assertion failure caused by receiving a
4172 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4173 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4176 o Minor features (geoip):
4177 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4180 o Minor bugfixes (correctness):
4181 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4182 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4184 Changes in version 0.2.5.14 - 2017-06-08
4185 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
4186 remotely crash a hidden service with an assertion failure. Anyone
4187 running a hidden service should upgrade to this version, or to some
4188 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4189 are not affected by TROVE-2017-004.)
4191 o Major bugfixes (hidden service, relay, security):
4192 - Fix a remotely triggerable assertion failure caused by receiving a
4193 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4194 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4197 o Minor features (geoip):
4198 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4201 o Minor bugfixes (correctness):
4202 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4203 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4205 Changes in version 0.2.4.29 - 2017-06-08
4206 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
4207 remotely crash a hidden service with an assertion failure. Anyone
4208 running a hidden service should upgrade to this version, or to some
4209 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4210 are not affected by TROVE-2017-004.)
4212 o Major bugfixes (hidden service, relay, security):
4213 - Fix a remotely triggerable assertion failure caused by receiving a
4214 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4215 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4218 o Minor features (geoip):
4219 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4222 o Minor bugfixes (correctness):
4223 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4224 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4227 Changes in version 0.3.0.7 - 2017-05-15
4228 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
4229 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
4230 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
4231 clients are not affected.
4233 o Major bugfixes (hidden service directory, security):
4234 - Fix an assertion failure in the hidden service directory code, which
4235 could be used by an attacker to remotely cause a Tor relay process to
4236 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
4237 should upgrade. This security issue is tracked as TROVE-2017-002.
4238 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
4241 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4244 o Minor features (future-proofing):
4245 - Tor no longer refuses to download microdescriptors or descriptors
4246 if they are listed as "published in the future". This change will
4247 eventually allow us to stop listing meaningful "published" dates
4248 in microdescriptor consensuses, and thereby allow us to reduce the
4249 resources required to download consensus diffs by over 50%.
4250 Implements part of ticket 21642; implements part of proposal 275.
4252 o Minor bugfixes (Linux seccomp2 sandbox):
4253 - The getpid() system call is now permitted under the Linux seccomp2
4254 sandbox, to avoid crashing with versions of OpenSSL (and other
4255 libraries) that attempt to learn the process's PID by using the
4256 syscall rather than the VDSO code. Fixes bug 21943; bugfix
4260 Changes in version 0.3.0.6 - 2017-04-26
4261 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
4263 With the 0.3.0 series, clients and relays now use Ed25519 keys to
4264 authenticate their link connections to relays, rather than the old
4265 RSA1024 keys that they used before. (Circuit crypto has been
4266 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
4267 the guard selection and replacement algorithm to behave more robustly
4268 in the presence of unreliable networks, and to resist guard-
4271 This series also includes numerous other small features and bugfixes,
4272 along with more groundwork for the upcoming hidden-services revamp.
4274 Per our stable release policy, we plan to support the Tor 0.3.0
4275 release series for at least the next nine months, or for three months
4276 after the first stable release of the 0.3.1 series: whichever is
4277 longer. If you need a release with long-term support, we recommend
4278 that you stay with the 0.2.9 series.
4280 Below are the changes since 0.2.9.10. For a list of only the changes
4281 since 0.3.0.5-rc, see the ChangeLog file.
4283 o Major features (directory authority, security):
4284 - The default for AuthDirPinKeys is now 1: directory authorities
4285 will reject relays where the RSA identity key matches a previously
4286 seen value, but the Ed25519 key has changed. Closes ticket 18319.
4288 o Major features (guard selection algorithm):
4289 - Tor's guard selection algorithm has been redesigned from the
4290 ground up, to better support unreliable networks and restrictive
4291 sets of entry nodes, and to better resist guard-capture attacks by
4292 hostile local networks. Implements proposal 271; closes
4295 o Major features (next-generation hidden services):
4296 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
4297 prop224 aka "Next Generation Hidden Services". Service and clients
4298 don't use this functionality yet. Closes ticket 19043. Based on
4299 initial code by Alec Heifetz.
4300 - Relays now support the HSDir version 3 protocol, so that they can
4301 can store and serve v3 descriptors. This is part of the next-
4302 generation onion service work detailed in proposal 224. Closes
4305 o Major features (protocol, ed25519 identity keys):
4306 - Clients now support including Ed25519 identity keys in the EXTEND2
4307 cells they generate. By default, this is controlled by a consensus
4308 parameter, currently disabled. You can turn this feature on for
4309 testing by setting ExtendByEd25519ID in your configuration. This
4310 might make your traffic appear different than the traffic
4311 generated by other users, however. Implements part of ticket
4312 15056; part of proposal 220.
4313 - Relays now understand requests to extend to other relays by their
4314 Ed25519 identity keys. When an Ed25519 identity key is included in
4315 an EXTEND2 cell, the relay will only extend the circuit if the
4316 other relay can prove ownership of that identity. Implements part
4317 of ticket 15056; part of proposal 220.
4318 - Relays now use Ed25519 to prove their Ed25519 identities and to
4319 one another, and to clients. This algorithm is faster and more
4320 secure than the RSA-based handshake we've been doing until now.
4321 Implements the second big part of proposal 220; Closes
4324 o Major features (security):
4325 - Change the algorithm used to decide DNS TTLs on client and server
4326 side, to better resist DNS-based correlation attacks like the
4327 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
4328 Feamster. Now relays only return one of two possible DNS TTL
4329 values, and clients are willing to believe DNS TTL values up to 3
4330 hours long. Closes ticket 19769.
4332 o Major bugfixes (client, onion service, also in 0.2.9.9):
4333 - Fix a client-side onion service reachability bug, where multiple
4334 socks requests to an onion service (or a single slow request)
4335 could cause us to mistakenly mark some of the service's
4336 introduction points as failed, and we cache that failure so
4337 eventually we run out and can't reach the service. Also resolves a
4338 mysterious "Remote server sent bogus reason code 65021" log
4339 warning. The bug was introduced in ticket 17218, where we tried to
4340 remember the circuit end reason as a uint16_t, which mangled
4341 negative values. Partially fixes bug 21056 and fixes bug 20307;
4342 bugfix on 0.2.8.1-alpha.
4344 o Major bugfixes (crash, directory connections):
4345 - Fix a rare crash when sending a begin cell on a circuit whose
4346 linked directory connection had already been closed. Fixes bug
4347 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
4349 o Major bugfixes (directory authority):
4350 - During voting, when marking a relay as a probable sybil, do not
4351 clear its BadExit flag: sybils can still be bad in other ways
4352 too. (We still clear the other flags.) Fixes bug 21108; bugfix
4355 o Major bugfixes (DNS):
4356 - Fix a bug that prevented exit nodes from caching DNS records for
4357 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
4359 o Major bugfixes (IPv6 Exits):
4360 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
4361 any IPv6 addresses. Instead, only reject a port over IPv6 if the
4362 exit policy rejects that port on more than an IPv6 /16 of
4363 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
4364 which rejected a relay's own IPv6 address by default. Fixes bug
4365 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
4367 o Major bugfixes (parsing):
4368 - Fix an integer underflow bug when comparing malformed Tor
4369 versions. This bug could crash Tor when built with
4370 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4371 0.2.9.8, which were built with -ftrapv by default. In other cases
4372 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4373 on 0.0.8pre1. Found by OSS-Fuzz.
4374 - When parsing a malformed content-length field from an HTTP
4375 message, do not read off the end of the buffer. This bug was a
4376 potential remote denial-of-service attack against Tor clients and
4377 relays. A workaround was released in October 2016, to prevent this
4378 bug from crashing Tor. This is a fix for the underlying issue,
4379 which should no longer matter (if you applied the earlier patch).
4380 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
4381 using AFL (http://lcamtuf.coredump.cx/afl/).
4383 o Major bugfixes (scheduler):
4384 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
4385 caused the channel scheduler to behave more or less randomly,
4386 rather than preferring channels with higher-priority circuits.
4387 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
4389 o Major bugfixes (security, also in 0.2.9.9):
4390 - Downgrade the "-ftrapv" option from "always on" to "only on when
4391 --enable-expensive-hardening is provided." This hardening option,
4392 like others, can turn survivable bugs into crashes--and having it
4393 on by default made a (relatively harmless) integer overflow bug
4394 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
4395 bugfix on 0.2.9.1-alpha.
4397 o Minor feature (client):
4398 - Enable IPv6 traffic on the SocksPort by default. To disable this,
4399 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
4401 o Minor feature (fallback scripts):
4402 - Add a check_existing mode to updateFallbackDirs.py, which checks
4403 if fallbacks in the hard-coded list are working. Closes ticket
4404 20174. Patch by haxxpop.
4406 o Minor feature (protocol versioning):
4407 - Add new protocol version for proposal 224. HSIntro now advertises
4408 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
4410 o Minor features (ciphersuite selection):
4411 - Allow relays to accept a wider range of ciphersuites, including
4412 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
4413 - Clients now advertise a list of ciphersuites closer to the ones
4414 preferred by Firefox. Closes part of ticket 15426.
4416 o Minor features (controller):
4417 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
4418 shared-random values to the controller. Closes ticket 19925.
4419 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
4420 rather than "unrecognized." Closes ticket 20389; patch from
4423 o Minor features (controller, configuration):
4424 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
4425 and so on, now comes with a __*Port variant that will not be saved
4426 to the torrc file by the controller's SAVECONF command. This
4427 change allows TorBrowser to set up a single-use domain socket for
4428 each time it launches Tor. Closes ticket 20956.
4429 - The GETCONF command can now query options that may only be
4430 meaningful in context-sensitive lists. This allows the controller
4431 to query the mixed SocksPort/__SocksPort style options introduced
4432 in feature 20956. Implements ticket 21300.
4434 o Minor features (diagnostic, directory client):
4435 - Warn when we find an unexpected inconsistency in directory
4436 download status objects. Prevents some negative consequences of
4439 o Minor features (directory authorities):
4440 - Directory authorities now reject descriptors that claim to be
4441 malformed versions of Tor. Helps prevent exploitation of
4443 - Reject version numbers with components that exceed INT32_MAX.
4444 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
4445 Fixes bug 21450; bugfix on 0.0.8pre1.
4447 o Minor features (directory authority):
4448 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
4449 default) to control whether authorities should try to probe relays
4450 by their Ed25519 link keys. This option will go away in a few
4451 releases--unless we encounter major trouble in our ed25519 link
4452 protocol rollout, in which case it will serve as a safety option.
4454 o Minor features (directory cache):
4455 - Relays and bridges will now refuse to serve the consensus they
4456 have if they know it is too old for a client to use. Closes
4459 o Minor features (ed25519 link handshake):
4460 - Advertise support for the ed25519 link handshake using the
4461 subprotocol-versions mechanism, so that clients can tell which
4462 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
4464 o Minor features (entry guards):
4465 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
4466 break regression tests.
4467 - Require UseEntryGuards when UseBridges is set, in order to make
4468 sure bridges aren't bypassed. Resolves ticket 20502.
4470 o Minor features (fallback directories):
4471 - Allow 3 fallback relays per operator, which is safe now that we
4472 are choosing 200 fallback relays. Closes ticket 20912.
4473 - Annotate updateFallbackDirs.py with the bandwidth and consensus
4474 weight for each candidate fallback. Closes ticket 20878.
4475 - Display the relay fingerprint when downloading consensuses from
4476 fallbacks. Closes ticket 20908.
4477 - Exclude relays affected by bug 20499 from the fallback list.
4478 Exclude relays from the fallback list if they are running versions
4479 known to be affected by bug 20499, or if in our tests they deliver
4480 a stale consensus (i.e. one that expired more than 24 hours ago).
4481 Closes ticket 20539.
4482 - Make it easier to change the output sort order of fallbacks.
4483 Closes ticket 20822.
4484 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
4486 - Require fallback directories to have the same address and port for
4487 7 days (now that we have enough relays with this stability).
4488 Relays whose OnionOO stability timer is reset on restart by bug
4489 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
4490 this issue. Closes ticket 20880; maintains short-term fix
4492 - Require fallbacks to have flags for 90% of the time (weighted
4493 decaying average), rather than 95%. This allows at least 73% of
4494 clients to bootstrap in the first 5 seconds without contacting an
4495 authority. Part of ticket 18828.
4496 - Select 200 fallback directories for each release. Closes
4499 o Minor features (fingerprinting resistance, authentication):
4500 - Extend the length of RSA keys used for TLS link authentication to
4501 2048 bits. (These weren't used for forward secrecy; for forward
4502 secrecy, we used P256.) Closes ticket 13752.
4504 o Minor features (geoip):
4505 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
4508 o Minor features (geoip, also in 0.2.9.9):
4509 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
4512 o Minor features (infrastructure):
4513 - Implement smartlist_add_strdup() function. Replaces the use of
4514 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
4516 o Minor features (linting):
4517 - Enhance the changes file linter to warn on Tor versions that are
4518 prefixed with "tor-". Closes ticket 21096.
4520 o Minor features (logging):
4521 - In several places, describe unset ed25519 keys as "<unset>",
4522 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
4524 o Minor features (portability, compilation):
4525 - Autoconf now checks to determine if OpenSSL structures are opaque,
4526 instead of explicitly checking for OpenSSL version numbers. Part
4528 - Support building with recent LibreSSL code that uses opaque
4529 structures. Closes ticket 21359.
4531 o Minor features (relay):
4532 - We now allow separation of exit and relay traffic to different
4533 source IP addresses, using the OutboundBindAddressExit and
4534 OutboundBindAddressOR options respectively. Closes ticket 17975.
4535 Written by Michael Sonntag.
4537 o Minor features (reliability, crash):
4538 - Try better to detect problems in buffers where they might grow (or
4539 think they have grown) over 2 GB in size. Diagnostic for
4542 o Minor features (testing):
4543 - During 'make test-network-all', if tor logs any warnings, ask
4544 chutney to output them. Requires a recent version of chutney with
4545 the 21572 patch. Implements 21570.
4547 o Minor bugfix (control protocol):
4548 - The reply to a "GETINFO config/names" request via the control
4549 protocol now spells the type "Dependent" correctly. This is a
4550 breaking change in the control protocol. (The field seems to be
4551 ignored by the most common known controllers.) Fixes bug 18146;
4552 bugfix on 0.1.1.4-alpha.
4553 - The GETINFO extra-info/digest/<digest> command was broken because
4554 of a wrong base16 decode return value check, introduced when
4555 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
4557 o Minor bugfix (logging):
4558 - Don't recommend the use of Tor2web in non-anonymous mode.
4559 Recommending Tor2web is a bad idea because the client loses all
4560 anonymity. Tor2web should only be used in specific cases by users
4561 who *know* and understand the issues. Fixes bug 21294; bugfix
4564 o Minor bugfixes (bug resilience):
4565 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
4566 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
4567 Hans Jerry Illikainen.
4569 o Minor bugfixes (build):
4570 - Replace obsolete Autoconf macros with their modern equivalent and
4571 prevent similar issues in the future. Fixes bug 20990; bugfix
4574 o Minor bugfixes (certificate expiration time):
4575 - Avoid using link certificates that don't become valid till some
4576 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
4578 o Minor bugfixes (client):
4579 - Always recover from failures in extend_info_from_node(), in an
4580 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
4581 bugfix on 0.2.3.1-alpha.
4582 - When clients that use bridges start up with a cached consensus on
4583 disk, they were ignoring it and downloading a new one. Now they
4584 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
4586 o Minor bugfixes (code correctness):
4587 - Repair a couple of (unreachable or harmless) cases of the risky
4588 comparison-by-subtraction pattern that caused bug 21278.
4590 o Minor bugfixes (config):
4591 - Don't assert on startup when trying to get the options list and
4592 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
4593 options so of course they aren't ready yet. Fixes bug 21062;
4594 bugfix on 0.2.9.3-alpha.
4596 o Minor bugfixes (configuration):
4597 - Accept non-space whitespace characters after the severity level in
4598 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
4599 - Support "TByte" and "TBytes" units in options given in bytes.
4600 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
4601 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
4603 o Minor bugfixes (configure, autoconf):
4604 - Rename the configure option --enable-expensive-hardening to
4605 --enable-fragile-hardening. Expensive hardening makes the tor
4606 daemon abort when some kinds of issues are detected. Thus, it
4607 makes tor more at risk of remote crashes but safer against RCE or
4608 heartbleed bug category. We now try to explain this issue in a
4609 message from the configure script. Fixes bug 21290; bugfix
4612 o Minor bugfixes (consensus weight):
4613 - Add new consensus method that initializes bw weights to 1 instead
4614 of 0. This prevents a zero weight from making it all the way to
4615 the end (happens in small testing networks) and causing an error.
4616 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
4618 o Minor bugfixes (crash prevention):
4619 - Fix an (currently untriggerable, but potentially dangerous) crash
4620 bug when base32-encoding inputs whose sizes are not a multiple of
4621 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
4623 o Minor bugfixes (dead code):
4624 - Remove a redundant check for PidFile changes at runtime in
4625 options_transition_allowed(): this check is already performed
4626 regardless of whether the sandbox is active. Fixes bug 21123;
4627 bugfix on 0.2.5.4-alpha.
4629 o Minor bugfixes (descriptors):
4630 - Correctly recognise downloaded full descriptors as valid, even
4631 when using microdescriptors as circuits. This affects clients with
4632 FetchUselessDescriptors set, and may affect directory authorities.
4633 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
4635 o Minor bugfixes (directory mirrors):
4636 - Allow relays to use directory mirrors without a DirPort: these
4637 relays need to be contacted over their ORPorts using a begindir
4638 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
4639 - Clarify the message logged when a remote relay is unexpectedly
4640 missing an ORPort or DirPort: users were confusing this with a
4641 local port. Fixes another case of bug 20711; bugfix
4644 o Minor bugfixes (directory system):
4645 - Bridges and relays now use microdescriptors (like clients do)
4646 rather than old-style router descriptors. Now bridges will blend
4647 in with clients in terms of the circuits they build. Fixes bug
4648 6769; bugfix on 0.2.3.2-alpha.
4649 - Download all consensus flavors, descriptors, and authority
4650 certificates when FetchUselessDescriptors is set, regardless of
4651 whether tor is a directory cache or not. Fixes bug 20667; bugfix
4652 on all recent tor versions.
4654 o Minor bugfixes (documentation):
4655 - Update the tor manual page to document every option that can not
4656 be changed while tor is running. Fixes bug 21122.
4658 o Minor bugfixes (ed25519 certificates):
4659 - Correctly interpret ed25519 certificates that would expire some
4660 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
4662 o Minor bugfixes (fallback directories):
4663 - Avoid checking fallback candidates' DirPorts if they are down in
4664 OnionOO. When a relay operator has multiple relays, this
4665 prioritizes relays that are up over relays that are down. Fixes
4666 bug 20926; bugfix on 0.2.8.3-alpha.
4667 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
4668 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
4669 - Stop failing when a relay has no uptime data in
4670 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
4672 o Minor bugfixes (hidden service):
4673 - Clean up the code for expiring intro points with no associated
4674 circuits. It was causing, rarely, a service with some expiring
4675 introduction points to not open enough additional introduction
4676 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
4677 - Resolve two possible underflows which could lead to creating and
4678 closing a lot of introduction point circuits in a non-stop loop.
4679 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
4680 - Stop setting the torrc option HiddenServiceStatistics to "0" just
4681 because we're not a bridge or relay. Instead, we preserve whatever
4682 value the user set (or didn't set). Fixes bug 21150; bugfix
4685 o Minor bugfixes (hidden services):
4686 - Make hidden services check for failed intro point connections,
4687 even when they have exceeded their intro point creation limit.
4688 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
4689 - Make hidden services with 8 to 10 introduction points check for
4690 failed circuits immediately after startup. Previously, they would
4691 wait for 5 minutes before performing their first checks. Fixes bug
4692 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
4693 - Stop ignoring misconfigured hidden services. Instead, refuse to
4694 start tor until the misconfigurations have been corrected. Fixes
4695 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
4698 o Minor bugfixes (IPv6):
4699 - Make IPv6-using clients try harder to find an IPv6 directory
4700 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
4701 - When IPv6 addresses have not been downloaded yet (microdesc
4702 consensus documents don't list relay IPv6 addresses), use hard-
4703 coded addresses for authorities, fallbacks, and configured
4704 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
4705 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
4707 o Minor bugfixes (memory leak at exit):
4708 - Fix a small harmless memory leak at exit of the previously unused
4709 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
4712 o Minor bugfixes (onion services):
4713 - Allow the number of introduction points to be as low as 0, rather
4714 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
4716 o Minor bugfixes (portability):
4717 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
4718 It is supported by OpenBSD itself, and also by most OpenBSD
4719 variants (such as Bitrig). Fixes bug 20980; bugfix
4722 o Minor bugfixes (portability, also in 0.2.9.9):
4723 - Avoid crashing when Tor is built using headers that contain
4724 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
4725 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
4727 - Fix Libevent detection on platforms without Libevent 1 headers
4728 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
4730 o Minor bugfixes (relay):
4731 - Avoid a double-marked-circuit warning that could happen when we
4732 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
4734 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
4735 initializing the keys would reset the DataDirectory to 0700
4736 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
4737 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
4739 o Minor bugfixes (testing):
4740 - Fix Raspbian build issues related to missing socket errno in
4741 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
4742 - Remove undefined behavior from the backtrace generator by removing
4743 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
4744 - Use bash in src/test/test-network.sh. This ensures we reliably
4745 call chutney's newer tools/test-network.sh when available. Fixes
4746 bug 21562; bugfix on 0.2.9.1-alpha.
4748 o Minor bugfixes (tor-resolve):
4749 - The tor-resolve command line tool now rejects hostnames over 255
4750 characters in length. Previously, it would silently truncate them,
4751 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
4752 Patch by "junglefowl".
4754 o Minor bugfixes (unit tests):
4755 - Allow the unit tests to pass even when DNS lookups of bogus
4756 addresses do not fail as expected. Fixes bug 20862 and 20863;
4757 bugfix on unit tests introduced in 0.2.8.1-alpha
4758 through 0.2.9.4-alpha.
4760 o Minor bugfixes (util):
4761 - When finishing writing a file to disk, if we were about to replace
4762 the file with the temporary file created before and we fail to
4763 replace it, remove the temporary file so it doesn't stay on disk.
4764 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
4766 o Minor bugfixes (Windows services):
4767 - Be sure to initialize the monotonic time subsystem before using
4768 it, even when running as an NT service. Fixes bug 21356; bugfix
4771 o Minor bugfixes (Windows):
4772 - Check for getpagesize before using it to mmap files. This fixes
4773 compilation in some MinGW environments. Fixes bug 20530; bugfix on
4774 0.1.2.1-alpha. Reported by "ice".
4776 o Code simplification and refactoring:
4777 - Abolish all global guard context in entrynodes.c; replace with new
4778 guard_selection_t structure as preparation for proposal 271.
4779 Closes ticket 19858.
4780 - Extract magic numbers in circuituse.c into defined variables.
4781 - Introduce rend_service_is_ephemeral() that tells if given onion
4782 service is ephemeral. Replace unclear NULL-checkings for service
4783 directory with this function. Closes ticket 20526.
4784 - Refactor circuit_is_available_for_use to remove unnecessary check.
4785 - Refactor circuit_predict_and_launch_new for readability and
4786 testability. Closes ticket 18873.
4787 - Refactor code to manipulate global_origin_circuit_list into
4788 separate functions. Closes ticket 20921.
4789 - Refactor large if statement in purpose_needs_anonymity to use
4790 switch statement instead. Closes part of ticket 20077.
4791 - Refactor the hashing API to return negative values for errors, as
4792 is done as throughout the codebase. Closes ticket 20717.
4793 - Remove data structures that were used to index or_connection
4794 objects by their RSA identity digests. These structures are fully
4795 redundant with the similar structures used in the
4796 channel abstraction.
4797 - Remove duplicate code in the channel_write_*cell() functions.
4798 Closes ticket 13827; patch from Pingl.
4799 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
4800 use only purpose_needs_anonymity. Closes part of ticket 20077.
4801 - The code to generate and parse EXTEND and EXTEND2 cells has been
4802 replaced with code automatically generated by the
4805 o Documentation (formatting):
4806 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
4807 blocks were incorrectly appearing. Closes ticket 20885.
4809 o Documentation (man page):
4810 - Clarify many options in tor.1 and add some min/max values for
4811 HiddenService options. Closes ticket 21058.
4814 - Change '1' to 'weight_scale' in consensus bw weights calculation
4815 comments, as that is reality. Closes ticket 20273. Patch
4817 - Clarify that when ClientRejectInternalAddresses is enabled (which
4818 is the default), multicast DNS hostnames for machines on the local
4819 network (of the form *.local) are also rejected. Closes
4821 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
4822 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
4823 - Include the "TBits" unit in Tor's man page. Fixes part of bug
4824 20622; bugfix on 0.2.5.1-alpha.
4825 - Small fixes to the fuzzing documentation. Closes ticket 21472.
4826 - Stop the man page from incorrectly stating that HiddenServiceDir
4827 must already exist. Fixes 20486.
4828 - Update the description of the directory server options in the
4829 manual page, to clarify that a relay no longer needs to set
4830 DirPort in order to be a directory cache. Closes ticket 21720.
4833 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
4834 limit for relays running on a single IP applies to authority IP
4835 addresses as well as to non-authority IP addresses. Closes
4837 - The UseDirectoryGuards torrc option no longer exists: all users
4838 that use entry guards will also use directory guards. Related to
4839 proposal 271; implements part of ticket 20831.
4842 - Add tests for networkstatus_compute_bw_weights_v10.
4843 - Add unit tests circuit_predict_and_launch_new.
4844 - Extract dummy_origin_circuit_new so it can be used by other
4846 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
4847 from "overcaffeinated".
4848 - Perform the coding style checks when running the tests and fail
4849 when coding style violations are found. Closes ticket 5500.
4852 Changes in version 0.2.8.13 - 2017-03-03
4853 Tor 0.2.8.13 backports a security fix from later Tor
4854 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
4855 this release, if for some reason they cannot upgrade to a later
4856 release series, and if they build Tor with the --enable-expensive-hardening
4859 Note that support for Tor 0.2.8.x is ending next year: we will not issue
4860 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
4861 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4863 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4864 - Fix an integer underflow bug when comparing malformed Tor
4865 versions. This bug could crash Tor when built with
4866 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4867 0.2.9.8, which were built with -ftrapv by default. In other cases
4868 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4869 on 0.0.8pre1. Found by OSS-Fuzz.
4871 o Minor features (geoip):
4872 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4876 Changes in version 0.2.7.7 - 2017-03-03
4877 Tor 0.2.7.7 backports a number of security fixes from later Tor
4878 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
4879 this release, if for some reason they cannot upgrade to a later
4882 Note that support for Tor 0.2.7.x is ending this year: we will not issue
4883 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
4884 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4886 o Directory authority changes (backport from 0.2.8.5-rc):
4887 - Urras is no longer a directory authority. Closes ticket 19271.
4889 o Directory authority changes (backport from 0.2.9.2-alpha):
4890 - The "Tonga" bridge authority has been retired; the new bridge
4891 authority is "Bifroest". Closes tickets 19728 and 19690.
4893 o Directory authority key updates (backport from 0.2.8.1-alpha):
4894 - Update the V3 identity key for the dannenberg directory authority:
4895 it was changed on 18 November 2015. Closes task 17906. Patch
4898 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4899 - Fix a bug in parsing that could cause clients to read a single
4900 byte past the end of an allocated region. This bug could be used
4901 to cause hardened clients (built with --enable-expensive-hardening)
4902 to crash if they tried to visit a hostile hidden service. Non-
4903 hardened clients are only affected depending on the details of
4904 their platform's memory allocator. Fixes bug 21018; bugfix on
4905 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
4906 2016-12-002 and as CVE-2016-1254.
4908 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
4909 - Stop a crash that could occur when a client running with DNSPort
4910 received a query with multiple address types, and the first
4911 address type was not supported. Found and fixed by Scott Dial.
4912 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4913 - Prevent a class of security bugs caused by treating the contents
4914 of a buffer chunk as if they were a NUL-terminated string. At
4915 least one such bug seems to be present in all currently used
4916 versions of Tor, and would allow an attacker to remotely crash
4917 most Tor instances, especially those compiled with extra compiler
4918 hardening. With this defense in place, such bugs can't crash Tor,
4919 though we should still fix them as they occur. Closes ticket
4920 20384 (TROVE-2016-10-001).
4922 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
4923 - Avoid a difficult-to-trigger heap corruption attack when extending
4924 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4925 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4926 Reported by Guido Vranken.
4928 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
4929 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4930 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4932 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
4933 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4934 pointer to the previous (uninitialized) key value. The impact here
4935 should be limited to a difficult-to-trigger crash, if OpenSSL is
4936 running an engine that makes key generation failures possible, or
4937 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4938 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4941 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
4942 - Fix an integer underflow bug when comparing malformed Tor
4943 versions. This bug could crash Tor when built with
4944 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
4945 0.2.9.8, which were built with -ftrapv by default. In other cases
4946 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
4947 on 0.0.8pre1. Found by OSS-Fuzz.
4949 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
4950 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4951 zero size. Check size argument to memwipe() for underflow. Fixes
4952 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4955 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
4956 - Make Tor survive errors involving connections without a
4957 corresponding event object. Previously we'd fail with an
4958 assertion; now we produce a log message. Related to bug 16248.
4960 o Minor features (geoip):
4961 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
4965 Changes in version 0.2.6.11 - 2017-03-03
4966 Tor 0.2.6.11 backports a number of security fixes from later Tor
4967 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
4968 this release, if for some reason they cannot upgrade to a later
4971 Note that support for Tor 0.2.6.x is ending this year: we will not issue
4972 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
4973 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
4975 o Directory authority changes (backport from 0.2.8.5-rc):
4976 - Urras is no longer a directory authority. Closes ticket 19271.
4978 o Directory authority changes (backport from 0.2.9.2-alpha):
4979 - The "Tonga" bridge authority has been retired; the new bridge
4980 authority is "Bifroest". Closes tickets 19728 and 19690.
4982 o Directory authority key updates (backport from 0.2.8.1-alpha):
4983 - Update the V3 identity key for the dannenberg directory authority:
4984 it was changed on 18 November 2015. Closes task 17906. Patch
4987 o Major features (security fixes, backport from 0.2.9.4-alpha):
4988 - Prevent a class of security bugs caused by treating the contents
4989 of a buffer chunk as if they were a NUL-terminated string. At
4990 least one such bug seems to be present in all currently used
4991 versions of Tor, and would allow an attacker to remotely crash
4992 most Tor instances, especially those compiled with extra compiler
4993 hardening. With this defense in place, such bugs can't crash Tor,
4994 though we should still fix them as they occur. Closes ticket
4995 20384 (TROVE-2016-10-001).
4997 o Major bugfixes (parsing, security, backport from 0.2.9.8):
4998 - Fix a bug in parsing that could cause clients to read a single
4999 byte past the end of an allocated region. This bug could be used
5000 to cause hardened clients (built with --enable-expensive-hardening)
5001 to crash if they tried to visit a hostile hidden service. Non-
5002 hardened clients are only affected depending on the details of
5003 their platform's memory allocator. Fixes bug 21018; bugfix on
5004 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5005 2016-12-002 and as CVE-2016-1254.
5007 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5008 - Stop a crash that could occur when a client running with DNSPort
5009 received a query with multiple address types, and the first
5010 address type was not supported. Found and fixed by Scott Dial.
5011 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5013 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5014 - Fix an error that could cause us to read 4 bytes before the
5015 beginning of an openssl string. This bug could be used to cause
5016 Tor to crash on systems with unusual malloc implementations, or
5017 systems with unusual hardening installed. Fixes bug 17404; bugfix
5020 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5021 - Avoid a difficult-to-trigger heap corruption attack when extending
5022 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5023 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5024 Reported by Guido Vranken.
5026 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5027 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5028 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5030 o Major bugfixes (guard selection, backport from 0.2.7.6):
5031 - Actually look at the Guard flag when selecting a new directory
5032 guard. When we implemented the directory guard design, we
5033 accidentally started treating all relays as if they have the Guard
5034 flag during guard selection, leading to weaker anonymity and worse
5035 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5038 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5039 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5040 pointer to the previous (uninitialized) key value. The impact here
5041 should be limited to a difficult-to-trigger crash, if OpenSSL is
5042 running an engine that makes key generation failures possible, or
5043 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5044 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5047 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5048 - Fix an integer underflow bug when comparing malformed Tor
5049 versions. This bug could crash Tor when built with
5050 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5051 0.2.9.8, which were built with -ftrapv by default. In other cases
5052 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5053 on 0.0.8pre1. Found by OSS-Fuzz.
5055 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5056 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5057 zero size. Check size argument to memwipe() for underflow. Fixes
5058 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5061 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5062 - Make Tor survive errors involving connections without a
5063 corresponding event object. Previously we'd fail with an
5064 assertion; now we produce a log message. Related to bug 16248.
5066 o Minor features (geoip):
5067 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5070 o Minor bugfixes (compilation, backport from 0.2.7.6):
5071 - Fix a compilation warning with Clang 3.6: Do not check the
5072 presence of an address which can never be NULL. Fixes bug 17781.
5075 Changes in version 0.2.5.13 - 2017-03-03
5076 Tor 0.2.5.13 backports a number of security fixes from later Tor
5077 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
5078 this release, if for some reason they cannot upgrade to a later
5081 Note that support for Tor 0.2.5.x is ending next year: we will not issue
5082 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
5083 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5085 o Directory authority changes (backport from 0.2.8.5-rc):
5086 - Urras is no longer a directory authority. Closes ticket 19271.
5088 o Directory authority changes (backport from 0.2.9.2-alpha):
5089 - The "Tonga" bridge authority has been retired; the new bridge
5090 authority is "Bifroest". Closes tickets 19728 and 19690.
5092 o Directory authority key updates (backport from 0.2.8.1-alpha):
5093 - Update the V3 identity key for the dannenberg directory authority:
5094 it was changed on 18 November 2015. Closes task 17906. Patch
5097 o Major features (security fixes, backport from 0.2.9.4-alpha):
5098 - Prevent a class of security bugs caused by treating the contents
5099 of a buffer chunk as if they were a NUL-terminated string. At
5100 least one such bug seems to be present in all currently used
5101 versions of Tor, and would allow an attacker to remotely crash
5102 most Tor instances, especially those compiled with extra compiler
5103 hardening. With this defense in place, such bugs can't crash Tor,
5104 though we should still fix them as they occur. Closes ticket
5105 20384 (TROVE-2016-10-001).
5107 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5108 - Fix a bug in parsing that could cause clients to read a single
5109 byte past the end of an allocated region. This bug could be used
5110 to cause hardened clients (built with --enable-expensive-hardening)
5111 to crash if they tried to visit a hostile hidden service. Non-
5112 hardened clients are only affected depending on the details of
5113 their platform's memory allocator. Fixes bug 21018; bugfix on
5114 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5115 2016-12-002 and as CVE-2016-1254.
5117 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5118 - Stop a crash that could occur when a client running with DNSPort
5119 received a query with multiple address types, and the first
5120 address type was not supported. Found and fixed by Scott Dial.
5121 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5123 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5124 - Fix an error that could cause us to read 4 bytes before the
5125 beginning of an openssl string. This bug could be used to cause
5126 Tor to crash on systems with unusual malloc implementations, or
5127 systems with unusual hardening installed. Fixes bug 17404; bugfix
5130 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5131 - Avoid a difficult-to-trigger heap corruption attack when extending
5132 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5133 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5134 Reported by Guido Vranken.
5136 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5137 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5138 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5140 o Major bugfixes (guard selection, backport from 0.2.7.6):
5141 - Actually look at the Guard flag when selecting a new directory
5142 guard. When we implemented the directory guard design, we
5143 accidentally started treating all relays as if they have the Guard
5144 flag during guard selection, leading to weaker anonymity and worse
5145 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5148 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5149 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5150 pointer to the previous (uninitialized) key value. The impact here
5151 should be limited to a difficult-to-trigger crash, if OpenSSL is
5152 running an engine that makes key generation failures possible, or
5153 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5154 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5157 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5158 - Fix an integer underflow bug when comparing malformed Tor
5159 versions. This bug could crash Tor when built with
5160 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5161 0.2.9.8, which were built with -ftrapv by default. In other cases
5162 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5163 on 0.0.8pre1. Found by OSS-Fuzz.
5165 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5166 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5167 zero size. Check size argument to memwipe() for underflow. Fixes
5168 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5171 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5172 - Make Tor survive errors involving connections without a
5173 corresponding event object. Previously we'd fail with an
5174 assertion; now we produce a log message. Related to bug 16248.
5176 o Minor features (geoip):
5177 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5180 o Minor bugfixes (compilation, backport from 0.2.7.6):
5181 - Fix a compilation warning with Clang 3.6: Do not check the
5182 presence of an address which can never be NULL. Fixes bug 17781.
5184 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
5185 - Check for failures from crypto_early_init, and refuse to continue.
5186 A previous typo meant that we could keep going with an
5187 uninitialized crypto library, and would have OpenSSL initialize
5188 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
5189 when implementing ticket 4900. Patch by "teor".
5191 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5192 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5193 a client authorized hidden service. Fixes bug 15823; bugfix
5197 Changes in version 0.2.4.28 - 2017-03-03
5198 Tor 0.2.4.28 backports a number of security fixes from later Tor
5199 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
5200 this release, if for some reason they cannot upgrade to a later
5203 Note that support for Tor 0.2.4.x is ending soon: we will not issue
5204 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
5205 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
5207 o Directory authority changes (backport from 0.2.8.5-rc):
5208 - Urras is no longer a directory authority. Closes ticket 19271.
5210 o Directory authority changes (backport from 0.2.9.2-alpha):
5211 - The "Tonga" bridge authority has been retired; the new bridge
5212 authority is "Bifroest". Closes tickets 19728 and 19690.
5214 o Directory authority key updates (backport from 0.2.8.1-alpha):
5215 - Update the V3 identity key for the dannenberg directory authority:
5216 it was changed on 18 November 2015. Closes task 17906. Patch
5219 o Major features (security fixes, backport from 0.2.9.4-alpha):
5220 - Prevent a class of security bugs caused by treating the contents
5221 of a buffer chunk as if they were a NUL-terminated string. At
5222 least one such bug seems to be present in all currently used
5223 versions of Tor, and would allow an attacker to remotely crash
5224 most Tor instances, especially those compiled with extra compiler
5225 hardening. With this defense in place, such bugs can't crash Tor,
5226 though we should still fix them as they occur. Closes ticket
5227 20384 (TROVE-2016-10-001).
5229 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5230 - Fix a bug in parsing that could cause clients to read a single
5231 byte past the end of an allocated region. This bug could be used
5232 to cause hardened clients (built with --enable-expensive-hardening)
5233 to crash if they tried to visit a hostile hidden service. Non-
5234 hardened clients are only affected depending on the details of
5235 their platform's memory allocator. Fixes bug 21018; bugfix on
5236 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5237 2016-12-002 and as CVE-2016-1254.
5239 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5240 - Fix an error that could cause us to read 4 bytes before the
5241 beginning of an openssl string. This bug could be used to cause
5242 Tor to crash on systems with unusual malloc implementations, or
5243 systems with unusual hardening installed. Fixes bug 17404; bugfix
5246 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5247 - Avoid a difficult-to-trigger heap corruption attack when extending
5248 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5249 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5250 Reported by Guido Vranken.
5252 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5253 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5254 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5256 o Major bugfixes (guard selection, backport from 0.2.7.6):
5257 - Actually look at the Guard flag when selecting a new directory
5258 guard. When we implemented the directory guard design, we
5259 accidentally started treating all relays as if they have the Guard
5260 flag during guard selection, leading to weaker anonymity and worse
5261 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5264 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5265 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5266 pointer to the previous (uninitialized) key value. The impact here
5267 should be limited to a difficult-to-trigger crash, if OpenSSL is
5268 running an engine that makes key generation failures possible, or
5269 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5270 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5273 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5274 - Fix an integer underflow bug when comparing malformed Tor
5275 versions. This bug could crash Tor when built with
5276 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5277 0.2.9.8, which were built with -ftrapv by default. In other cases
5278 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5279 on 0.0.8pre1. Found by OSS-Fuzz.
5281 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5282 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5283 zero size. Check size argument to memwipe() for underflow. Fixes
5284 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5287 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5288 - Make Tor survive errors involving connections without a
5289 corresponding event object. Previously we'd fail with an
5290 assertion; now we produce a log message. Related to bug 16248.
5292 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
5293 - Make it harder for attackers to overload hidden services with
5294 introductions, by blocking multiple introduction requests on the
5295 same circuit. Resolves ticket 15515.
5297 o Minor features (geoip):
5298 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5301 o Minor bugfixes (compilation, backport from 0.2.7.6):
5302 - Fix a compilation warning with Clang 3.6: Do not check the
5303 presence of an address which can never be NULL. Fixes bug 17781.
5305 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5306 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5307 a client authorized hidden service. Fixes bug 15823; bugfix
5311 Changes in version 0.2.9.10 - 2017-03-01
5312 Tor 0.2.9.10 backports a security fix from later Tor release. It also
5313 includes fixes for some major issues affecting directory authorities,
5314 LibreSSL compatibility, and IPv6 correctness.
5316 The Tor 0.2.9.x release series is now marked as a long-term-support
5317 series. We intend to backport security fixes to 0.2.9.x until at
5318 least January of 2020.
5320 o Major bugfixes (directory authority, 0.3.0.3-alpha):
5321 - During voting, when marking a relay as a probable sybil, do not
5322 clear its BadExit flag: sybils can still be bad in other ways
5323 too. (We still clear the other flags.) Fixes bug 21108; bugfix
5326 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
5327 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
5328 any IPv6 addresses. Instead, only reject a port over IPv6 if the
5329 exit policy rejects that port on more than an IPv6 /16 of
5330 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
5331 which rejected a relay's own IPv6 address by default. Fixes bug
5332 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
5334 o Major bugfixes (parsing, also in 0.3.0.4-rc):
5335 - Fix an integer underflow bug when comparing malformed Tor
5336 versions. This bug could crash Tor when built with
5337 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5338 0.2.9.8, which were built with -ftrapv by default. In other cases
5339 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5340 on 0.0.8pre1. Found by OSS-Fuzz.
5342 o Minor features (directory authorities, also in 0.3.0.4-rc):
5343 - Directory authorities now reject descriptors that claim to be
5344 malformed versions of Tor. Helps prevent exploitation of
5346 - Reject version numbers with components that exceed INT32_MAX.
5347 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
5348 Fixes bug 21450; bugfix on 0.0.8pre1.
5350 o Minor features (geoip):
5351 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5354 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
5355 - Autoconf now checks to determine if OpenSSL structures are opaque,
5356 instead of explicitly checking for OpenSSL version numbers. Part
5358 - Support building with recent LibreSSL code that uses opaque
5359 structures. Closes ticket 21359.
5361 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
5362 - Repair a couple of (unreachable or harmless) cases of the risky
5363 comparison-by-subtraction pattern that caused bug 21278.
5365 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
5366 - The tor-resolve command line tool now rejects hostnames over 255
5367 characters in length. Previously, it would silently truncate them,
5368 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
5369 Patch by "junglefowl".
5372 Changes in version 0.2.9.9 - 2017-01-23
5373 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
5374 cause relays and clients to crash, even if they were not built with
5375 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
5376 versions, and also affects 0.3.0.1-alpha: all relays running an affected
5377 version should upgrade.
5379 This release also resolves a client-side onion service reachability
5380 bug, and resolves a pair of small portability issues.
5382 o Major bugfixes (security):
5383 - Downgrade the "-ftrapv" option from "always on" to "only on when
5384 --enable-expensive-hardening is provided." This hardening option,
5385 like others, can turn survivable bugs into crashes -- and having
5386 it on by default made a (relatively harmless) integer overflow bug
5387 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
5388 bugfix on 0.2.9.1-alpha.
5390 o Major bugfixes (client, onion service):
5391 - Fix a client-side onion service reachability bug, where multiple
5392 socks requests to an onion service (or a single slow request)
5393 could cause us to mistakenly mark some of the service's
5394 introduction points as failed, and we cache that failure so
5395 eventually we run out and can't reach the service. Also resolves a
5396 mysterious "Remote server sent bogus reason code 65021" log
5397 warning. The bug was introduced in ticket 17218, where we tried to
5398 remember the circuit end reason as a uint16_t, which mangled
5399 negative values. Partially fixes bug 21056 and fixes bug 20307;
5400 bugfix on 0.2.8.1-alpha.
5402 o Minor features (geoip):
5403 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
5406 o Minor bugfixes (portability):
5407 - Avoid crashing when Tor is built using headers that contain
5408 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
5409 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
5411 - Fix Libevent detection on platforms without Libevent 1 headers
5412 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
5415 Changes in version 0.2.8.12 - 2016-12-19
5416 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
5417 below) where Tor clients could crash when attempting to visit a
5418 hostile hidden service. Clients are recommended to upgrade as packages
5419 become available for their systems.
5421 It also includes an updated list of fallback directories, backported
5424 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
5425 backported to 0.2.8 in the future.
5427 o Major bugfixes (parsing, security, backported from 0.2.9.8):
5428 - Fix a bug in parsing that could cause clients to read a single
5429 byte past the end of an allocated region. This bug could be used
5430 to cause hardened clients (built with --enable-expensive-hardening)
5431 to crash if they tried to visit a hostile hidden service. Non-
5432 hardened clients are only affected depending on the details of
5433 their platform's memory allocator. Fixes bug 21018; bugfix on
5434 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5435 2016-12-002 and as CVE-2016-1254.
5437 o Minor features (fallback directory list, backported from 0.2.9.8):
5438 - Replace the 81 remaining fallbacks of the 100 originally
5439 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
5440 fallbacks (123 new, 54 existing, 27 removed) generated in December
5441 2016. Resolves ticket 20170.
5443 o Minor features (geoip, backported from 0.2.9.7-rc):
5444 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
5448 Changes in version 0.2.9.8 - 2016-12-19
5449 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
5451 The Tor 0.2.9 series makes mandatory a number of security features
5452 that were formerly optional. It includes support for a new shared-
5453 randomness protocol that will form the basis for next generation
5454 hidden services, includes a single-hop hidden service mode for
5455 optimizing .onion services that don't actually want to be hidden,
5456 tries harder not to overload the directory authorities with excessive
5457 downloads, and supports a better protocol versioning scheme for
5458 improved compatibility with other implementations of the Tor protocol.
5460 And of course, there are numerous other bugfixes and improvements.
5462 This release also includes a fix for a medium-severity issue (bug
5463 21018 below) where Tor clients could crash when attempting to visit a
5464 hostile hidden service. Clients are recommended to upgrade as packages
5465 become available for their systems.
5467 Below are listed the changes since Tor 0.2.8.11. For a list of
5468 changes since 0.2.9.7-rc, see the ChangeLog file.
5470 o New system requirements:
5471 - When building with OpenSSL, Tor now requires version 1.0.1 or
5472 later. OpenSSL 1.0.0 and earlier are no longer supported by the
5473 OpenSSL team, and should not be used. Closes ticket 20303.
5474 - Tor now requires Libevent version 2.0.10-stable or later. Older
5475 versions of Libevent have less efficient backends for several
5476 platforms, and lack the DNS code that we use for our server-side
5477 DNS support. This implements ticket 19554.
5478 - Tor now requires zlib version 1.2 or later, for security,
5479 efficiency, and (eventually) gzip support. (Back when we started,
5480 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
5481 released in 2003. We recommend the latest version.)
5483 o Deprecated features:
5484 - A number of DNS-cache-related sub-options for client ports are now
5485 deprecated for security reasons, and may be removed in a future
5486 version of Tor. (We believe that client-side DNS caching is a bad
5487 idea for anonymity, and you should not turn it on.) The options
5488 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
5489 UseIPv4Cache, and UseIPv6Cache.
5490 - A number of options are deprecated for security reasons, and may
5491 be removed in a future version of Tor. The options are:
5492 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
5493 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
5494 CloseHSClientCircuitsImmediatelyOnTimeout,
5495 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
5496 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
5497 UseNTorHandshake, and WarnUnsafeSocks.
5498 - The *ListenAddress options are now deprecated as unnecessary: the
5499 corresponding *Port options should be used instead. These options
5500 may someday be removed. The affected options are:
5501 ControlListenAddress, DNSListenAddress, DirListenAddress,
5502 NATDListenAddress, ORListenAddress, SocksListenAddress,
5503 and TransListenAddress.
5505 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
5506 - Fix a bug in parsing that could cause clients to read a single
5507 byte past the end of an allocated region. This bug could be used
5508 to cause hardened clients (built with --enable-expensive-hardening)
5509 to crash if they tried to visit a hostile hidden service. Non-
5510 hardened clients are only affected depending on the details of
5511 their platform's memory allocator. Fixes bug 21018; bugfix on
5512 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5513 2016-12-002 and as CVE-2016-1254.
5515 o Major features (build, hardening):
5516 - Tor now builds with -ftrapv by default on compilers that support
5517 it. This option detects signed integer overflow (which C forbids),
5518 and turns it into a hard-failure. We do not apply this option to
5519 code that needs to run in constant time to avoid side-channels;
5520 instead, we use -fwrapv in that code. Closes ticket 17983.
5521 - When --enable-expensive-hardening is selected, stop applying the
5522 clang/gcc sanitizers to code that needs to run in constant time.
5523 Although we are aware of no introduced side-channels, we are not
5524 able to prove that there are none. Related to ticket 17983.
5526 o Major features (circuit building, security):
5527 - Authorities, relays, and clients now require ntor keys in all
5528 descriptors, for all hops (except for rare hidden service protocol
5529 cases), for all circuits, and for all other roles. Part of
5531 - Authorities, relays, and clients only use ntor, except for
5532 rare cases in the hidden service protocol. Part of ticket 19163.
5534 o Major features (compilation):
5535 - Our big list of extra GCC warnings is now enabled by default when
5536 building with GCC (or with anything like Clang that claims to be
5537 GCC-compatible). To make all warnings into fatal compilation
5538 errors, pass --enable-fatal-warnings to configure. Closes
5540 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
5541 turn on C and POSIX extensions. (Previously, we attempted to do
5542 this on an ad hoc basis.) Closes ticket 19139.
5544 o Major features (directory authorities, hidden services):
5545 - Directory authorities can now perform the shared randomness
5546 protocol specified by proposal 250. Using this protocol, directory
5547 authorities generate a global fresh random value every day. In the
5548 future, this value will be used by hidden services to select
5549 HSDirs. This release implements the directory authority feature;
5550 the hidden service side will be implemented in the future as part
5551 of proposal 224. Resolves ticket 16943; implements proposal 250.
5553 o Major features (downloading, random exponential backoff):
5554 - When we fail to download an object from a directory service, wait
5555 for an (exponentially increasing) randomized amount of time before
5556 retrying, rather than a fixed interval as we did before. This
5557 prevents a group of Tor instances from becoming too synchronized,
5558 or a single Tor instance from becoming too predictable, in its
5559 download schedule. Closes ticket 15942.
5561 o Major features (resource management):
5562 - Tor can now notice it is about to run out of sockets, and
5563 preemptively close connections of lower priority. (This feature is
5564 off by default for now, since the current prioritizing method is
5565 yet not mature enough. You can enable it by setting
5566 "DisableOOSCheck 0", but watch out: it might close some sockets
5567 you would rather have it keep.) Closes ticket 18640.
5569 o Major features (single-hop "hidden" services):
5570 - Add experimental HiddenServiceSingleHopMode and
5571 HiddenServiceNonAnonymousMode options. When both are set to 1,
5572 every hidden service on that Tor instance becomes a non-anonymous
5573 Single Onion Service. Single Onions make one-hop (direct)
5574 connections to their introduction and rendezvous points. One-hop
5575 circuits make Single Onion servers easily locatable, but clients
5576 remain location-anonymous. This is compatible with the existing
5577 hidden service implementation, and works on the current Tor
5578 network without any changes to older relays or clients. Implements
5579 proposal 260, completes ticket 17178. Patch by teor and asn.
5581 o Major features (subprotocol versions):
5582 - Tor directory authorities now vote on a set of recommended
5583 "subprotocol versions", and on a set of required subprotocol
5584 versions. Clients and relays that lack support for a _required_
5585 subprotocol version will not start; those that lack support for a
5586 _recommended_ subprotocol version will warn the user to upgrade.
5587 This change allows compatible implementations of the Tor protocol(s)
5588 to exist without pretending to be 100% bug-compatible with
5589 particular releases of Tor itself. Closes ticket 19958; implements
5590 part of proposal 264.
5592 o Major bugfixes (circuit building):
5593 - Hidden service client-to-intro-point and service-to-rendezvous-
5594 point circuits use the TAP key supplied by the protocol, to avoid
5595 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
5597 o Major bugfixes (download scheduling):
5598 - Avoid resetting download status for consensuses hourly, since we
5599 already have another, smarter retry mechanism. Fixes bug 8625;
5600 bugfix on 0.2.0.9-alpha.
5601 - If a consensus expires while we are waiting for certificates to
5602 download, stop waiting for certificates.
5603 - If we stop waiting for certificates less than a minute after we
5604 started downloading them, do not consider the certificate download
5605 failure a separate failure. Fixes bug 20533; bugfix
5607 - When using exponential backoff in test networks, use a lower
5608 exponent, so the delays do not vary as much. This helps test
5609 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
5611 o Major bugfixes (exit policies):
5612 - Avoid disclosing exit outbound bind addresses, configured port
5613 bind addresses, and local interface addresses in relay descriptors
5614 by default under ExitPolicyRejectPrivate. Instead, only reject
5615 these (otherwise unlisted) addresses if
5616 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
5617 0.2.7.2-alpha. Patch by teor.
5619 o Major bugfixes (hidden services):
5620 - Allow Tor clients with appropriate controllers to work with
5621 FetchHidServDescriptors set to 0. Previously, this option also
5622 disabled descriptor cache lookup, thus breaking hidden services
5623 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
5624 - Clients now require hidden services to include the TAP keys for
5625 their intro points in the hidden service descriptor. This prevents
5626 an inadvertent upgrade to ntor, which a malicious hidden service
5627 could use to distinguish clients by consensus version. Fixes bug
5628 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
5630 o Major bugfixes (relay, resolver, logging):
5631 - For relays that don't know their own address, avoid attempting a
5632 local hostname resolve for each descriptor we download. This
5633 will cut down on the number of "Success: chose address 'x.x.x.x'"
5634 log lines, and also avoid confusing clock jumps if the resolver
5635 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
5637 o Minor features (port flags):
5638 - Add new flags to the *Port options to give finer control over which
5639 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
5640 and the synthetic flag OnionTrafficOnly, which is equivalent to
5641 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
5642 18693; patch by "teor".
5644 o Minor features (build, hardening):
5645 - Detect and work around a libclang_rt problem that would prevent
5646 clang from finding __mulodi4() on some 32-bit platforms, and thus
5647 keep -ftrapv from linking on those systems. Closes ticket 19079.
5648 - When building on a system without runtime support for the runtime
5649 hardening options, try to log a useful warning at configuration
5650 time, rather than an incomprehensible warning at link time. If
5651 expensive hardening was requested, this warning becomes an error.
5652 Closes ticket 18895.
5654 o Minor features (client, directory):
5655 - Since authorities now omit all routers that lack the Running and
5656 Valid flags, we assume that any relay listed in the consensus must
5657 have those flags. Closes ticket 20001; implements part of
5660 o Minor features (code safety):
5661 - In our integer-parsing functions, ensure that the maximum value we
5662 allow is no smaller than the minimum value. Closes ticket 19063;
5663 patch from "U+039b".
5665 o Minor features (compilation, portability):
5666 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
5669 o Minor features (config):
5670 - Warn users when descriptor and port addresses are inconsistent.
5671 Mitigates bug 13953; patch by teor.
5673 o Minor features (controller):
5674 - Allow controllers to configure basic client authorization on
5675 hidden services when they create them with the ADD_ONION controller
5676 command. Implements ticket 15588. Patch by "special".
5677 - Fire a STATUS_SERVER controller event whenever the hibernation
5678 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
5679 - Implement new GETINFO queries for all downloads that use
5680 download_status_t to schedule retries. This allows controllers to
5681 examine the schedule for pending downloads. Closes ticket 19323.
5683 o Minor features (development tools, etags):
5684 - Teach the "make tags" Makefile target how to correctly find
5685 "MOCK_IMPL" function definitions. Patch from nherring; closes
5688 o Minor features (directory authority):
5689 - After voting, if the authorities decide that a relay is not
5690 "Valid", they no longer include it in the consensus at all. Closes
5691 ticket 20002; implements part of proposal 272.
5692 - Directory authorities now only give the Guard flag to a relay if
5693 they are also giving it the Stable flag. This change allows us to
5694 simplify path selection for clients. It should have minimal effect
5695 in practice, since >99% of Guards already have the Stable flag.
5696 Implements ticket 18624.
5697 - Directory authorities now write their v3-status-votes file out to
5698 disk earlier in the consensus process, so we have a record of the
5699 votes even if we abort the consensus process. Resolves
5702 o Minor features (fallback directory list, new since 0.2.9.7-rc):
5703 - Replace the 81 remaining fallbacks of the 100 originally
5704 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
5705 fallbacks (123 new, 54 existing, 27 removed) generated in December
5706 2016. Resolves ticket 20170.
5708 o Minor features (hidden service):
5709 - Stop being so strict about the payload length of "rendezvous1"
5710 cells. We used to be locked in to the "TAP" handshake length, and
5711 now we can handle better handshakes like "ntor". Resolves
5714 o Minor features (infrastructure, time):
5715 - Tor now includes an improved timer backend, so that we can
5716 efficiently support tens or hundreds of thousands of concurrent
5717 timers, as will be needed for some of our planned anti-traffic-
5718 analysis work. This code is based on William Ahern's "timeout.c"
5719 project, which implements a "tickless hierarchical timing wheel".
5720 Closes ticket 18365.
5721 - Tor now uses the operating system's monotonic timers (where
5722 available) for internal fine-grained timing. Previously we would
5723 look at the system clock, and then attempt to compensate for the
5724 clock running backwards. Closes ticket 18908.
5726 o Minor features (logging):
5727 - Add a set of macros to check nonfatal assertions, for internal
5728 use. Migrating more of our checks to these should help us avoid
5729 needless crash bugs. Closes ticket 18613.
5730 - Provide a more useful warning message when configured with an
5731 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
5732 - When dumping unparseable router descriptors, optionally store them
5733 in separate files, named by digest, up to a configurable size
5734 limit. You can change the size limit by setting the
5735 MaxUnparseableDescSizeToLog option, and disable this feature by
5736 setting that option to 0. Closes ticket 18322.
5738 o Minor features (performance):
5739 - Change the "optimistic data" extension from "off by default" to
5740 "on by default". The default was ordinarily overridden by a
5741 consensus option, but when clients were bootstrapping for the
5742 first time, they would not have a consensus to get the option
5743 from. Changing this default saves a round-trip during startup.
5744 Closes ticket 18815.
5746 o Minor features (relay, usability):
5747 - When the directory authorities refuse a bad relay's descriptor,
5748 encourage the relay operator to contact us. Many relay operators
5749 won't notice this line in their logs, but it's a win if even a few
5750 learn why we don't like what their relay was doing. Resolves
5753 o Minor features (security, TLS):
5754 - Servers no longer support clients that lack AES ciphersuites.
5755 (3DES is no longer considered an acceptable cipher.) We believe
5756 that no such Tor clients currently exist, since Tor has required
5757 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
5759 o Minor features (testing):
5760 - Disable memory protections on OpenBSD when performing our unit
5761 tests for memwipe(). The test deliberately invokes undefined
5762 behavior, and the OpenBSD protections interfere with this. Patch
5763 from "rubiate". Closes ticket 20066.
5764 - Move the test-network.sh script to chutney, and modify tor's test-
5765 network.sh to call the (newer) chutney version when available.
5766 Resolves ticket 19116. Patch by teor.
5767 - Use the lcov convention for marking lines as unreachable, so that
5768 we don't count them when we're generating test coverage data.
5769 Update our coverage tools to understand this convention. Closes
5771 - Our link-handshake unit tests now check that when invalid
5772 handshakes fail, they fail with the error messages we expected.
5773 - Our unit testing code that captures log messages no longer
5774 prevents them from being written out if the user asked for them
5775 (by passing --debug or --info or --notice or --warn to the "test"
5776 binary). This change prevents us from missing unexpected log
5777 messages simply because we were looking for others. Related to
5779 - The unit tests now log all warning messages with the "BUG" flag.
5780 Previously, they only logged errors by default. This change will
5781 help us make our testing code more correct, and make sure that we
5782 only hit this code when we mean to. In the meantime, however,
5783 there will be more warnings in the unit test logs than before.
5784 This is preparatory work for ticket 19999.
5785 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
5786 assertion as a test failure.
5787 - We've done significant work to make the unit tests run faster.
5789 o Minor features (testing, ipv6):
5790 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
5791 tests. Remove bridges+hs, as it's somewhat redundant. This
5792 requires a recent chutney version that supports IPv6 clients,
5793 relays, and authorities. Closes ticket 20069; patch by teor.
5794 - Add the single-onion and single-onion-ipv6 chutney targets to
5795 "make test-network-all". This requires a recent chutney version
5796 with the single onion network flavors (git c72a652 or later).
5797 Closes ticket 20072; patch by teor.
5799 o Minor features (Tor2web):
5800 - Make Tor2web clients respect ReachableAddresses. This feature was
5801 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
5802 0.2.8.7. Implements feature 20034. Patch by teor.
5804 o Minor features (unix domain sockets):
5805 - When configuring a unix domain socket for a SocksPort,
5806 ControlPort, or Hidden service, you can now wrap the address in
5807 quotes, using C-style escapes inside the quotes. This allows unix
5808 domain socket paths to contain spaces. Resolves ticket 18753.
5810 o Minor features (user interface):
5811 - Tor now supports the ability to declare options deprecated, so
5812 that we can recommend that people stop using them. Previously, this
5813 was done in an ad-hoc way. There is a new --list-deprecated-options
5814 command-line option to list all of the deprecated options. Closes
5817 o Minor features (virtual addresses):
5818 - Increase the maximum number of bits for the IPv6 virtual network
5819 prefix from 16 to 104. In this way, the condition for address
5820 allocation is less restrictive. Closes ticket 20151; feature
5823 o Minor bug fixes (circuits):
5824 - Use the CircuitBuildTimeout option whenever
5825 LearnCircuitBuildTimeout is disabled. Previously, we would respect
5826 the option when a user disabled it, but not when it was disabled
5827 because some other option was set. Fixes bug 20073; bugfix on
5828 0.2.4.12-alpha. Patch by teor.
5830 o Minor bugfixes (build):
5831 - The current Git revision when building from a local repository is
5832 now detected correctly when using git worktrees. Fixes bug 20492;
5833 bugfix on 0.2.3.9-alpha.
5835 o Minor bugfixes (relay address discovery):
5836 - Stop reordering IP addresses returned by the OS. This makes it
5837 more likely that Tor will guess the same relay IP address every
5838 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
5839 Reported by René Mayrhofer, patch by "cypherpunks".
5841 o Minor bugfixes (memory allocation):
5842 - Change how we allocate memory for large chunks on buffers, to
5843 avoid a (currently impossible) integer overflow, and to waste less
5844 space when allocating unusually large chunks. Fixes bug 20081;
5845 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
5847 o Minor bugfixes (bootstrap):
5848 - Remember the directory server we fetched the consensus or previous
5849 certificates from, and use it to fetch future authority
5850 certificates. This change improves bootstrapping performance.
5851 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
5853 o Minor bugfixes (circuits):
5854 - Make sure extend_info_from_router() is only called on servers.
5855 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
5857 o Minor bugfixes (client, fascistfirewall):
5858 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
5859 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
5861 o Minor bugfixes (client, unix domain sockets):
5862 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
5863 the client address is meaningless. Fixes bug 20261; bugfix
5866 o Minor bugfixes (code style):
5867 - Fix an integer signedness conversion issue in the case conversion
5868 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
5870 o Minor bugfixes (compilation):
5871 - Build correctly on versions of libevent2 without support for
5872 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
5874 - When building with Clang, use a full set of GCC warnings.
5875 (Previously, we included only a subset, because of the way we
5876 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
5877 - Detect Libevent2 functions correctly on systems that provide
5878 libevent2, but where libevent1 is linked with -levent. Fixes bug
5879 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
5880 - Run correctly when built on Windows build environments that
5881 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
5883 o Minor bugfixes (configuration):
5884 - When parsing quoted configuration values from the torrc file,
5885 handle Windows line endings correctly. Fixes bug 19167; bugfix on
5886 0.2.0.16-alpha. Patch from "Pingl".
5888 o Minor bugfixes (directory authority):
5889 - Authorities now sort the "package" lines in their votes, for ease
5890 of debugging. (They are already sorted in consensus documents.)
5891 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
5892 - Die with a more useful error when the operator forgets to place
5893 the authority_signing_key file into the keys directory. This
5894 avoids an uninformative assert & traceback about having an invalid
5895 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
5896 - When allowing private addresses, mark Exits that only exit to
5897 private locations as such. Fixes bug 20064; bugfix
5899 - When parsing a detached signature, make sure we use the length of
5900 the digest algorithm instead of a hardcoded DIGEST256_LEN in
5901 order to avoid comparing bytes out-of-bounds with a smaller digest
5902 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
5904 o Minor bugfixes (getpass):
5905 - Defensively fix a non-triggerable heap corruption at do_getpass()
5906 to protect ourselves from mistakes in the future. Fixes bug
5907 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
5910 o Minor bugfixes (guard selection):
5911 - Don't mark guards as unreachable if connection_connect() fails.
5912 That function fails for local reasons, so it shouldn't reveal
5913 anything about the status of the guard. Fixes bug 14334; bugfix
5915 - Use a single entry guard even if the NumEntryGuards consensus
5916 parameter is not provided. Fixes bug 17688; bugfix
5919 o Minor bugfixes (hidden services):
5920 - Increase the minimum number of internal circuits we preemptively
5921 build from 2 to 3, so a circuit is available when a client
5922 connects to another onion service. Fixes bug 13239; bugfix
5924 - Allow hidden services to run on IPv6 addresses even when the
5925 IPv6Exit option is not set. Fixes bug 18357; bugfix
5927 - Stop logging intro point details to the client log on certain
5928 error conditions. Fixed as part of bug 20012; bugfix on
5929 0.2.4.8-alpha. Patch by teor.
5930 - When deleting an ephemeral hidden service, close its intro points
5931 even if they are not completely open. Fixes bug 18604; bugfix
5933 - When configuring hidden services, check every hidden service
5934 directory's permissions. Previously, we only checked the last
5935 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
5937 o Minor bugfixes (IPv6, testing):
5938 - Check for IPv6 correctly on Linux when running test networks.
5939 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
5941 o Minor bugfixes (Linux seccomp2 sandbox):
5942 - Add permission to run the sched_yield() and sigaltstack() system
5943 calls, in order to support versions of Tor compiled with asan or
5944 ubsan code that use these calls. Now "sandbox 1" and
5945 "--enable-expensive-hardening" should be compatible on more
5946 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
5948 o Minor bugfixes (logging):
5949 - Downgrade a harmless log message about the
5950 pending_entry_connections list from "warn" to "info". Mitigates
5952 - Log a more accurate message when we fail to dump a microdescriptor.
5953 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
5954 - When logging a directory ownership mismatch, log the owning
5955 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
5956 - When we are unable to remove the bw_accounting file, do not warn
5957 if the reason we couldn't remove it was that it didn't exist.
5958 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
5960 o Minor bugfixes (memory leak):
5961 - Fix a series of slow memory leaks related to parsing torrc files
5962 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
5963 - Avoid a small memory leak when informing worker threads about
5964 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
5965 - Fix a small memory leak when receiving AF_UNIX connections on a
5966 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
5967 - When moving a signed descriptor object from a source to an
5968 existing destination, free the allocated memory inside that
5969 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
5970 - Fix a memory leak and use-after-free error when removing entries
5971 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
5972 0.2.5.5-alpha. Patch from "cypherpunks".
5973 - Fix a small, uncommon memory leak that could occur when reading a
5974 truncated ed25519 key file. Fixes bug 18956; bugfix
5977 o Minor bugfixes (option parsing):
5978 - Count unix sockets when counting client listeners (SOCKS, Trans,
5979 NATD, and DNS). This has no user-visible behavior changes: these
5980 options are set once, and never read. Required for correct
5981 behavior in ticket 17178. Fixes bug 19677; bugfix on
5982 0.2.6.3-alpha. Patch by teor.
5984 o Minor bugfixes (options):
5985 - Check the consistency of UseEntryGuards and EntryNodes more
5986 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
5988 - Stop changing the configured value of UseEntryGuards on
5989 authorities and Tor2web clients. Fixes bug 20074; bugfix on
5990 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
5993 o Minor bugfixes (relay):
5994 - Ensure relays don't make multiple connections during bootstrap.
5995 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
5996 - Do not try to parallelize workers more than 16x without the user
5997 explicitly configuring us to do so, even if we do detect more than
5998 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
6000 o Minor bugfixes (testing):
6001 - The test-stem and test-network makefile targets now depend only on
6002 the tor binary that they are testing. Previously, they depended on
6003 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
6004 patch from "cypherpunks".
6005 - Allow clients to retry HSDirs much faster in test networks. Fixes
6006 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
6007 - Avoid a unit test failure on systems with over 16 detectable CPU
6008 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
6009 - Let backtrace tests work correctly under AddressSanitizer:
6010 disable ASAN's detection of segmentation faults while running
6011 test_bt.sh, so that we can make sure that our own backtrace
6012 generation code works. Fixes bug 18934; bugfix
6013 on 0.2.5.2-alpha. Patch from "cypherpunks".
6014 - Fix the test-network-all target on out-of-tree builds by using the
6015 correct path to the test driver script. Fixes bug 19421; bugfix
6017 - Stop spurious failures in the local interface address discovery
6018 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
6020 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
6021 removed the ECDH ciphers which caused the tests to fail on
6022 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
6023 - The tor_tls_server_info_callback unit test no longer crashes when
6024 debug-level logging is turned on. Fixes bug 20041; bugfix
6027 o Minor bugfixes (time):
6028 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
6029 bugfix on all released tor versions.
6030 - When computing the difference between two times in milliseconds,
6031 we now round to the nearest millisecond correctly. Previously, we
6032 could sometimes round in the wrong direction. Fixes bug 19428;
6033 bugfix on 0.2.2.2-alpha.
6035 o Minor bugfixes (Tor2web):
6036 - Prevent Tor2web clients from running hidden services: these services
6037 are not anonymous due to the one-hop client paths. Fixes bug
6038 19678. Patch by teor.
6040 o Minor bugfixes (user interface):
6041 - Display a more accurate number of suppressed messages in the log
6042 rate-limiter. Previously, there was a potential integer overflow
6043 in the counter. Now, if the number of messages hits a maximum, the
6044 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
6046 - Fix a typo in the passphrase prompt for the ed25519 identity key.
6047 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
6049 o Code simplification and refactoring:
6050 - Remove redundant declarations of the MIN macro. Closes
6052 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
6053 Closes ticket 18462; patch from "icanhasaccount".
6054 - Split the 600-line directory_handle_command_get function into
6055 separate functions for different URL types. Closes ticket 16698.
6058 - Add module-level internal documentation for 36 C files that
6059 previously didn't have a high-level overview. Closes ticket 20385.
6060 - Correct the IPv6 syntax in our documentation for the
6061 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
6062 - Correct the minimum bandwidth value in torrc.sample, and queue a
6063 corresponding change for torrc.minimal. Closes ticket 20085.
6064 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
6065 ticket 19153. Patch from "U+039b".
6066 - Module-level documentation for several more modules. Closes
6067 tickets 19287 and 19290.
6068 - Document the --passphrase-fd option in the tor manpage. Fixes bug
6069 19504; bugfix on 0.2.7.3-rc.
6070 - Document the default PathsNeededToBuildCircuits value that's used
6071 by clients when the directory authorities don't set
6072 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
6073 Patch by teor, reported by Jesse V.
6074 - Fix manual for the User option: it takes a username, not a UID.
6075 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
6077 - Fix the description of the --passphrase-fd option in the
6078 tor-gencert manpage. The option is used to pass the number of a
6079 file descriptor to read the passphrase from, not to read the file
6080 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
6083 - We no longer include the (dead, deprecated) bufferevent code in
6084 Tor. Closes ticket 19450. Based on a patch from "U+039b".
6087 - Remove support for "GET /tor/bytes.txt" DirPort request, and
6088 "GETINFO dir-usage" controller request, which were only available
6089 via a compile-time option in Tor anyway. Feature was added in
6090 0.2.2.1-alpha. Resolves ticket 19035.
6091 - There is no longer a compile-time option to disable support for
6092 TransPort. (If you don't want TransPort, just don't use it.) Patch
6093 from "U+039b". Closes ticket 19449.
6096 - Run more workqueue tests as part of "make check". These had
6097 previously been implemented, but you needed to know special
6098 command-line options to enable them.
6099 - We now have unit tests for our code to reject zlib "compression
6100 bombs". (Fortunately, the code works fine.)
6103 Changes in version 0.2.8.11 - 2016-12-08
6104 Tor 0.2.8.11 backports fixes for additional portability issues that
6105 could prevent Tor from building correctly on OSX Sierra, or with
6106 OpenSSL 1.1. Affected users should upgrade; others can safely stay
6109 o Minor bugfixes (portability):
6110 - Avoid compilation errors when building on OSX Sierra. Sierra began
6111 to support the getentropy() and clock_gettime() APIs, but created
6112 a few problems in doing so. Tor 0.2.9 has a more thorough set of
6113 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
6114 monotonic time interfaces. Fixes bug 20865. Bugfix
6117 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
6118 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
6119 architectures. Closes ticket 20588.
6122 Changes in version 0.2.8.10 - 2016-12-02
6123 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
6124 unusable after they left standby mode. It also backports fixes for
6125 a few portability issues and a small but problematic memory leak.
6127 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
6128 - When Tor leaves standby because of a new application request, open
6129 circuits as needed to serve that request. Previously, we would
6130 potentially wait a very long time. Fixes part of bug 19969; bugfix
6133 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
6134 - Clients now respond to new application stream requests immediately
6135 when they arrive, rather than waiting up to one second before
6136 starting to handle them. Fixes part of bug 19969; bugfix
6139 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
6140 - Work around a bug in the OSX 10.12 SDK that would prevent us from
6141 successfully targeting earlier versions of OSX. Resolves
6144 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
6145 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
6146 20551; bugfix on 0.2.1.1-alpha.
6148 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
6149 - Work around a memory leak in OpenSSL 1.1 when encoding public
6150 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
6152 o Minor features (geoip):
6153 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
6157 Changes in version 0.2.8.9 - 2016-10-17
6158 Tor 0.2.8.9 backports a fix for a security hole in previous versions
6159 of Tor that would allow a remote attacker to crash a Tor client,
6160 hidden service, relay, or authority. All Tor users should upgrade to
6161 this version, or to 0.2.9.4-alpha. Patches will be released for older
6164 o Major features (security fixes, also in 0.2.9.4-alpha):
6165 - Prevent a class of security bugs caused by treating the contents
6166 of a buffer chunk as if they were a NUL-terminated string. At
6167 least one such bug seems to be present in all currently used
6168 versions of Tor, and would allow an attacker to remotely crash
6169 most Tor instances, especially those compiled with extra compiler
6170 hardening. With this defense in place, such bugs can't crash Tor,
6171 though we should still fix them as they occur. Closes ticket
6172 20384 (TROVE-2016-10-001).
6174 o Minor features (geoip):
6175 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
6179 Changes in version 0.2.8.8 - 2016-09-23
6180 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
6181 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
6182 who select public relays as their bridges.
6184 o Major bugfixes (crash):
6185 - Fix a complicated crash bug that could affect Tor clients
6186 configured to use bridges when replacing a networkstatus consensus
6187 in which one of their bridges was mentioned. OpenBSD users saw
6188 more crashes here, but all platforms were potentially affected.
6189 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
6191 o Major bugfixes (relay, OOM handler):
6192 - Fix a timing-dependent assertion failure that could occur when we
6193 tried to flush from a circuit after having freed its cells because
6194 of an out-of-memory condition. Fixes bug 20203; bugfix on
6195 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
6198 o Minor feature (fallback directories):
6199 - Remove broken fallbacks from the hard-coded fallback directory
6200 list. Closes ticket 20190; patch by teor.
6202 o Minor features (geoip):
6203 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
6207 Changes in version 0.2.8.7 - 2016-08-24
6208 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
6209 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
6210 who sets the ReachableAddresses option, and all bridges, are strongly
6211 encouraged to upgrade.
6213 o Directory authority changes:
6214 - The "Tonga" bridge authority has been retired; the new bridge
6215 authority is "Bifroest". Closes tickets 19728 and 19690.
6217 o Major bugfixes (client, security):
6218 - Only use the ReachableAddresses option to restrict the first hop
6219 in a path. In earlier versions of 0.2.8.x, it would apply to
6220 every hop in the path, with a possible degradation in anonymity
6221 for anyone using an uncommon ReachableAddress setting. Fixes bug
6222 19973; bugfix on 0.2.8.2-alpha.
6224 o Minor features (geoip):
6225 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
6228 o Minor bugfixes (compilation):
6229 - Remove an inappropriate "inline" in tortls.c that was causing
6230 warnings on older versions of GCC. Fixes bug 19903; bugfix
6233 o Minor bugfixes (fallback directories):
6234 - Avoid logging a NULL string pointer when loading fallback
6235 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
6236 and 0.2.8.1-alpha. Report and patch by "rubiate".
6239 Changes in version 0.2.8.6 - 2016-08-02
6241 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
6243 The Tor 0.2.8 series improves client bootstrapping performance,
6244 completes the authority-side implementation of improved identity
6245 keys for relays, and includes numerous bugfixes and performance
6246 improvements throughout the program. This release continues to
6247 improve the coverage of Tor's test suite. For a full list of
6248 changes since Tor 0.2.7, see the ReleaseNotes file.
6250 Below is a list of the changes since Tor 0.2.7.
6252 o New system requirements:
6253 - Tor no longer attempts to support platforms where the "time_t"
6254 type is unsigned. (To the best of our knowledge, only OpenVMS does
6255 this, and Tor has never actually built on OpenVMS.) Closes
6257 - Tor no longer supports versions of OpenSSL with a broken
6258 implementation of counter mode. (This bug was present in OpenSSL
6259 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
6260 longer runs with, these versions.
6261 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
6262 later (released in 2008 and 2009 respectively). If you are
6263 building Tor from the git repository instead of from the source
6264 distribution, and your tools are older than this, you will need to
6265 upgrade. Closes ticket 17732.
6267 o Directory authority changes:
6268 - Update the V3 identity key for the dannenberg directory authority:
6269 it was changed on 18 November 2015. Closes task 17906. Patch
6271 - Urras is no longer a directory authority. Closes ticket 19271.
6273 o Major features (directory system):
6274 - Include a trial list of default fallback directories, based on an
6275 opt-in survey of suitable relays. Doing this should make clients
6276 bootstrap more quickly and reliably, and reduce the load on the
6277 directory authorities. Closes ticket 15775. Patch by teor.
6278 Candidates identified using an OnionOO script by weasel, teor,
6279 gsathya, and karsten.
6280 - Previously only relays that explicitly opened a directory port
6281 (DirPort) accepted directory requests from clients. Now all
6282 relays, with and without a DirPort, accept and serve tunneled
6283 directory requests that they receive through their ORPort. You can
6284 disable this behavior using the new DirCache option. Closes
6286 - When bootstrapping multiple consensus downloads at a time, use the
6287 first one that starts downloading, and close the rest. This
6288 reduces failures when authorities or fallback directories are slow
6289 or down. Together with the code for feature 15775, this feature
6290 should reduces failures due to fallback churn. Implements ticket
6291 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
6294 o Major features (security, Linux):
6295 - When Tor starts as root on Linux and is told to switch user ID, it
6296 can now retain the capability to bind to low ports. By default,
6297 Tor will do this only when it's switching user ID and some low
6298 ports have been configured. You can change this behavior with the
6299 new option KeepBindCapabilities. Closes ticket 8195.
6301 o Major bugfixes (client, bootstrapping):
6302 - Check if bootstrap consensus downloads are still needed when the
6303 linked connection attaches. This prevents tor making unnecessary
6304 begindir-style connections, which are the only directory
6305 connections tor clients make since the fix for 18483 was merged.
6306 - Fix some edge cases where consensus download connections may not
6307 have been closed, even though they were not needed. Related to fix
6309 - Make relays retry consensus downloads the correct number of times,
6310 rather than the more aggressive client retry count. Fixes part of
6313 o Major bugfixes (dns proxy mode, crash):
6314 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
6315 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
6317 o Major bugfixes (ed25519, voting):
6318 - Actually enable support for authorities to match routers by their
6319 Ed25519 identities. Previously, the code had been written, but
6320 some debugging code that had accidentally been left in the
6321 codebase made it stay turned off. Fixes bug 17702; bugfix
6323 - When collating votes by Ed25519 identities, authorities now
6324 include a "NoEdConsensus" flag if the ed25519 value (or lack
6325 thereof) for a server does not reflect the majority consensus.
6326 Related to bug 17668; bugfix on 0.2.7.2-alpha.
6327 - When generating a vote with keypinning disabled, never include two
6328 entries for the same ed25519 identity. This bug was causing
6329 authorities to generate votes that they could not parse when a
6330 router violated key pinning by changing its RSA identity but
6331 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
6332 18318. Bugfix on 0.2.7.2-alpha.
6334 o Major bugfixes (key management):
6335 - If OpenSSL fails to generate an RSA key, do not retain a dangling
6336 pointer to the previous (uninitialized) key value. The impact here
6337 should be limited to a difficult-to-trigger crash, if OpenSSL is
6338 running an engine that makes key generation failures possible, or
6339 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
6340 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
6343 o Major bugfixes (security, client, DNS proxy):
6344 - Stop a crash that could occur when a client running with DNSPort
6345 received a query with multiple address types, and the first
6346 address type was not supported. Found and fixed by Scott Dial.
6347 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
6349 o Major bugfixes (security, compilation):
6350 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
6351 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
6352 cause a compiler warning, thereby making other checks fail, and
6353 needlessly disabling compiler-hardening support. Fixes one case of
6354 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
6355 - Repair hardened builds under the clang compiler. Previously, our
6356 use of _FORTIFY_SOURCE would conflict with clang's address
6357 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
6359 o Major bugfixes (security, pointers):
6360 - Avoid a difficult-to-trigger heap corruption attack when extending
6361 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
6362 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
6363 Reported by Guido Vranken.
6365 o Major bugfixes (testing):
6366 - Fix a bug that would block 'make test-network-all' on systems where
6367 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
6369 o Major bugfixes (user interface):
6370 - Correctly give a warning in the cases where a relay is specified
6371 by nickname, and one such relay is found, but it is not officially
6372 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
6374 o Minor features (accounting):
6375 - Added two modes to the AccountingRule option: One for limiting
6376 only the number of bytes sent ("AccountingRule out"), and one for
6377 limiting only the number of bytes received ("AccountingRule in").
6378 Closes ticket 15989; patch from "unixninja92".
6380 o Minor features (bug-resistance):
6381 - Make Tor survive errors involving connections without a
6382 corresponding event object. Previously we'd fail with an
6383 assertion; now we produce a log message. Related to bug 16248.
6384 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
6385 level code, to harden against accidental failures to NUL-
6386 terminate. Part of ticket 17852. Patch from jsturgix. Found
6389 o Minor features (build):
6390 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
6391 as having possible IPFW support. Closes ticket 18448. Patch from
6393 - Since our build process now uses "make distcheck", we no longer
6394 force "make dist" to depend on "make check". Closes ticket 17893;
6395 patch from "cypherpunks".
6396 - Tor now builds once again with the recent OpenSSL 1.1 development
6397 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
6398 tracking OpenSSL 1.1 development as it has progressed, and fixing
6399 numerous compatibility issues as they arose. See tickets
6400 17549, 17921, 17984, 19499, and 18286.
6401 - When building manual pages, set the timezone to "UTC", so that the
6402 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
6403 Patch from intrigeri.
6405 o Minor features (clients):
6406 - Make clients, onion services, and bridge relays always use an
6407 encrypted begindir connection for directory requests. Resolves
6408 ticket 18483. Patch by teor.
6410 o Minor features (controller):
6411 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
6412 controllers can examine the the reject rules added by
6413 ExitPolicyRejectPrivate. This makes it easier for stem to display
6415 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
6416 tickets 16774 and 17817. Patch by George Tankersley.
6417 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
6418 service descriptor from a service's local hidden service
6419 descriptor cache. Closes ticket 14846.
6421 o Minor features (crypto):
6422 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
6423 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
6425 - Improve performance when hashing non-multiple of 8 sized buffers,
6426 based on Andrew Moon's public domain SipHash-2-4 implementation.
6427 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
6428 - Validate the hard-coded Diffie-Hellman parameters and ensure that
6429 p is a safe prime, and g is a suitable generator. Closes
6431 - When allocating a digest state object, allocate no more space than
6432 we actually need. Previously, we would allocate as much space as
6433 the state for the largest algorithm would need. This change saves
6434 up to 672 bytes per circuit. Closes ticket 17796.
6436 o Minor features (directory downloads):
6437 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
6438 directory mirrors. The default is 1; set it to 0 to disable
6439 fallbacks. Implements ticket 17576. Patch by teor.
6440 - Wait for busy authorities and fallback directories to become non-
6441 busy when bootstrapping. (A similar change was made in 6c443e987d
6442 for directory caches chosen from the consensus.) Closes ticket
6443 17864; patch by teor.
6445 o Minor features (geoip):
6446 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
6449 o Minor features (hidden service directory):
6450 - Streamline relay-side hsdir handling: when relays consider whether
6451 to accept an uploaded hidden service descriptor, they no longer
6452 check whether they are one of the relays in the network that is
6453 "supposed" to handle that descriptor. Implements ticket 18332.
6455 o Minor features (IPv6):
6456 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
6457 to 1, tor prefers IPv6 directory addresses.
6458 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
6459 avoids using IPv4 for client OR and directory connections.
6460 - Add address policy assume_action support for IPv6 addresses.
6461 - Add an argument 'ipv6=address:orport' to the DirAuthority and
6462 FallbackDir torrc options, to specify an IPv6 address for an
6463 authority or fallback directory. Add hard-coded ipv6 addresses for
6464 directory authorities that have them. Closes ticket 17327; patch
6465 from Nick Mathewson and teor.
6466 - Allow users to configure directory authorities and fallback
6467 directory servers with IPv6 addresses and ORPorts. Resolves
6469 - Limit IPv6 mask bits to 128.
6470 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
6471 17638; bugfix on 0.0.2pre8. Patch by teor.
6472 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
6473 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
6474 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
6475 - Warn when comparing against an AF_UNSPEC address in a policy, it's
6476 almost always a bug. Closes ticket 17863; patch by teor.
6477 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
6478 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
6480 o Minor features (Linux seccomp2 sandbox):
6481 - Reject attempts to change our Address with "Sandbox 1" enabled.
6482 Changing Address with Sandbox turned on would never actually work,
6483 but previously it would fail in strange and confusing ways. Found
6486 o Minor features (logging):
6487 - When logging to syslog, allow a tag to be added to the syslog
6488 identity (the string prepended to every log message). The tag can
6489 be configured with SyslogIdentityTag and defaults to none. Setting
6490 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
6493 o Minor features (portability):
6494 - Use timingsafe_memcmp() where available. Closes ticket 17944;
6495 patch from <logan@hackers.mu>.
6497 o Minor features (relay, address discovery):
6498 - Add a family argument to get_interface_addresses_raw() and
6499 subfunctions to make network interface address interogation more
6500 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
6501 types of interfaces from the operating system. Resolves
6503 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
6504 fails to enumerate interface addresses using the platform-specific
6505 API, have it rely on the UDP socket fallback technique to try and
6506 find out what IP addresses (both IPv4 and IPv6) our machine has.
6507 Resolves ticket 17951.
6509 o Minor features (replay cache):
6510 - The replay cache now uses SHA256 instead of SHA1. Implements
6511 feature 8961. Patch by teor, issue reported by rransom.
6513 o Minor features (robustness):
6514 - Exit immediately with an error message if the code attempts to use
6515 Libevent without having initialized it. This should resolve some
6516 frequently-made mistakes in our unit tests. Closes ticket 18241.
6518 o Minor features (security, clock):
6519 - Warn when the system clock appears to move back in time (when the
6520 state file was last written in the future). Tor doesn't know that
6521 consensuses have expired if the clock is in the past. Patch by
6522 teor. Implements ticket 17188.
6524 o Minor features (security, exit policies):
6525 - ExitPolicyRejectPrivate now rejects more private addresses by
6526 default. Specifically, it now rejects the relay's outbound bind
6527 addresses (if configured), and the relay's configured port
6528 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
6529 0.2.0.11-alpha. Patch by teor.
6531 o Minor features (security, memory erasure):
6532 - Make memwipe() do nothing when passed a NULL pointer or buffer of
6533 zero size. Check size argument to memwipe() for underflow. Fixes
6534 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
6536 - Set the unused entries in a smartlist to NULL. This helped catch
6537 a (harmless) bug, and shouldn't affect performance too much.
6538 Implements ticket 17026.
6539 - Use SecureMemoryWipe() function to securely clean memory on
6540 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
6541 Implements feature 17986.
6542 - Use explicit_bzero or memset_s when present. Previously, we'd use
6543 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
6544 from <logan@hackers.mu> and <selven@hackers.mu>.
6546 o Minor features (security, RNG):
6547 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
6548 positively are not allowed to fail. Previously we depended on
6549 internal details of OpenSSL's behavior. Closes ticket 17686.
6550 - Never use the system entropy output directly for anything besides
6551 seeding the PRNG. When we want to generate important keys, instead
6552 of using system entropy directly, we now hash it with the PRNG
6553 stream. This may help resist certain attacks based on broken OS
6554 entropy implementations. Closes part of ticket 17694.
6555 - Use modern system calls (like getentropy() or getrandom()) to
6556 generate strong entropy on platforms that have them. Closes
6559 o Minor features (security, win32):
6560 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
6561 attack. Fixes bug 18123; bugfix on all tor versions. Patch
6564 o Minor features (unix domain sockets):
6565 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
6566 Unix domain sockets without checking the permissions on the parent
6567 directory. (Tor checks permissions by default because some
6568 operating systems only check permissions on the parent directory.
6569 However, some operating systems do look at permissions on the
6570 socket, and tor's default check is unneeded.) Closes ticket 18458.
6573 o Minor features (unix file permissions):
6574 - Defer creation of Unix sockets until after setuid. This avoids
6575 needing CAP_CHOWN and CAP_FOWNER when using systemd's
6576 CapabilityBoundingSet, or chown and fowner when using SELinux.
6577 Implements part of ticket 17562. Patch from Jamie Nguyen.
6578 - If any directory created by Tor is marked as group readable, the
6579 filesystem group is allowed to be either the default GID or the
6580 root user. Allowing root to read the DataDirectory prevents the
6581 need for CAP_READ_SEARCH when using systemd's
6582 CapabilityBoundingSet, or dac_read_search when using SELinux.
6583 Implements part of ticket 17562. Patch from Jamie Nguyen.
6584 - Introduce a new DataDirectoryGroupReadable option. If it is set to
6585 1, the DataDirectory will be made readable by the default GID.
6586 Implements part of ticket 17562. Patch from Jamie Nguyen.
6588 o Minor bugfixes (accounting):
6589 - The max bandwidth when using 'AccountRule sum' is now correctly
6590 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
6593 o Minor bugfixes (assert, portability):
6594 - Fix an assertion failure in memarea.c on systems where "long" is
6595 shorter than the size of a pointer. Fixes bug 18716; bugfix
6598 o Minor bugfixes (bootstrap):
6599 - Consistently use the consensus download schedule for authority
6600 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
6602 o Minor bugfixes (build):
6603 - Avoid spurious failures from configure files related to calling
6604 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
6605 0.2.0.1-alpha. Patch from "cypherpunks".
6606 - Do not link the unit tests against both the testing and non-
6607 testing versions of the static libraries. Fixes bug 18490; bugfix
6609 - Resolve warnings when building on systems that are concerned with
6610 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
6612 - Silence spurious clang-scan warnings in the ed25519_donna code by
6613 explicitly initializing some objects. Fixes bug 18384; bugfix on
6614 0.2.7.2-alpha. Patch by teor.
6615 - When libscrypt.h is found, but no libscrypt library can be linked,
6616 treat libscrypt as absent. Fixes bug 19161; bugfix
6618 - Cause the unit tests to compile correctly on mingw64 versions that
6619 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
6620 - Don't try to use the pthread_condattr_setclock() function unless
6621 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
6622 17819; bugfix on 0.2.6.3-alpha.
6623 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
6625 - Fix search for libevent libraries on OpenBSD (and other systems
6626 that install libevent 1 and libevent 2 in parallel). Fixes bug
6627 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
6628 - Isolate environment variables meant for tests from the rest of the
6629 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
6630 - Mark all object files that include micro-revision.i as depending
6631 on it, so as to make parallel builds more reliable. Fixes bug
6632 17826; bugfix on 0.2.5.1-alpha.
6633 - Remove config.log only from make distclean, not from make clean.
6634 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
6635 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
6637 - Remove an #endif from configure.ac so that we correctly detect the
6638 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
6641 o Minor bugfixes (client, bootstrap):
6642 - Count receipt of new microdescriptors as progress towards
6643 bootstrapping. Previously, with EntryNodes set, Tor might not
6644 successfully repopulate the guard set on bootstrapping. Fixes bug
6645 16825; bugfix on 0.2.3.1-alpha.
6647 o Minor bugfixes (code correctness):
6648 - Fix a bad memory handling bug that would occur if we had queued a
6649 cell on a channel's incoming queue. Fortunately, we can't actually
6650 queue a cell like that as our code is constructed today, but it's
6651 best to avoid this kind of error, even if there isn't any code
6652 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
6653 - Assert that allocated memory held by the reputation code is freed
6654 according to its internal counters. Fixes bug 17753; bugfix
6656 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
6658 - Update to the latest version of Trunnel, which tries harder to
6659 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
6660 by clang address sanitizer. Fixes bug 18373; bugfix
6662 - When closing an entry connection, generate a warning if we should
6663 have sent an end cell for it but we haven't. Fixes bug 17876;
6664 bugfix on 0.2.3.2-alpha.
6666 o Minor bugfixes (configuration):
6667 - Fix a tiny memory leak when parsing a port configuration ending in
6668 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
6670 o Minor bugfixes (containers):
6671 - If we somehow attempt to construct a heap with more than
6672 1073741822 elements, avoid an integer overflow when maintaining
6673 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
6675 o Minor bugfixes (controller, microdescriptors):
6676 - Make GETINFO dir/status-vote/current/consensus conform to the
6677 control specification by returning "551 Could not open cached
6678 consensus..." when not caching consensuses. Fixes bug 18920;
6679 bugfix on 0.2.2.6-alpha.
6681 o Minor bugfixes (crypto):
6682 - Check the return value of HMAC() and assert on failure. Fixes bug
6683 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
6685 o Minor bugfixes (directories):
6686 - When fetching extrainfo documents, compare their SHA256 digests
6687 and Ed25519 signing key certificates with the routerinfo that led
6688 us to fetch them, rather than with the most recent routerinfo.
6689 Otherwise we generate many spurious warnings about mismatches.
6690 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
6691 - When generating a URL for a directory server on an IPv6 address,
6692 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
6693 on 0.2.3.9-alpha. Patch from Malek.
6695 o Minor bugfixes (downloading):
6696 - Predict more correctly whether we'll be downloading over HTTP when
6697 we determine the maximum length of a URL. This should avoid a
6698 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
6701 o Minor bugfixes (exit policies, security):
6702 - Refresh an exit relay's exit policy when interface addresses
6703 change. Previously, tor only refreshed the exit policy when the
6704 configured external address changed. Fixes bug 18208; bugfix on
6705 0.2.7.3-rc. Patch by teor.
6707 o Minor bugfixes (fallback directories):
6708 - Mark fallbacks as "too busy" when they return a 503 response,
6709 rather than just marking authorities. Fixes bug 17572; bugfix on
6710 0.2.4.7-alpha. Patch by teor.
6711 - When requesting extrainfo descriptors from a trusted directory
6712 server, check whether it is an authority or a fallback directory
6713 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
6714 0.2.4.7-alpha. Reported by atagar, patch by teor.
6716 o Minor bugfixes (hidden service, client):
6717 - Handle the case where the user makes several fast consecutive
6718 requests to the same .onion address. Previously, the first six
6719 requests would each trigger a descriptor fetch, each picking a
6720 directory (there are 6 overall) and the seventh one would fail
6721 because no directories were left, thereby triggering a close on
6722 all current directory connections asking for the hidden service.
6723 The solution here is to not close the connections if we have
6724 pending directory fetches. Fixes bug 15937; bugfix
6727 o Minor bugfixes (hidden service, control port):
6728 - Add the onion address to the HS_DESC event for the UPLOADED action
6729 both on success or failure. It was previously hardcoded with
6730 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
6732 o Minor bugfixes (hidden service, directory):
6733 - Bridges now refuse "rendezvous2" (hidden service descriptor)
6734 publish attempts. Suggested by ticket 18332.
6736 o Minor bugfixes (IPv6):
6737 - Update the limits in max_dl_per_request for IPv6 address length.
6738 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
6740 o Minor bugfixes (Linux seccomp2 sandbox):
6741 - Allow more syscalls when running with "Sandbox 1" enabled:
6742 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
6743 some systems, these are required for Tor to start. Fixes bug
6744 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
6745 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
6746 so that get_interface_address6_via_udp_socket_hack() can work.
6747 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
6748 - Allow the setrlimit syscall, and the prlimit and prlimit64
6749 syscalls, which some libc implementations use under the hood.
6750 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
6751 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
6752 enabled and no DNS resolvers configured. This should help TAILS
6753 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
6754 - Fix a crash when using offline master ed25519 keys with the Linux
6755 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
6756 - Allow statistics to be written to disk when "Sandbox 1" is
6757 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
6758 0.2.6.1-alpha respectively.
6760 o Minor bugfixes (logging):
6761 - In log messages that include a function name, use __FUNCTION__
6762 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
6763 with clang __PRETTY_FUNCTION__ has extra information we don't
6764 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
6766 - Remove needless quotes from a log message about unparseable
6767 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
6768 - Scrub service name in "unrecognized service ID" log messages.
6769 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
6770 - When logging information about an unparsable networkstatus vote or
6771 consensus, do not say "vote" when we mean consensus. Fixes bug
6772 18368; bugfix on 0.2.0.8-alpha.
6773 - When we can't generate a signing key because OfflineMasterKey is
6774 set, do not imply that we should have been able to load it. Fixes
6775 bug 18133; bugfix on 0.2.7.2-alpha.
6776 - When logging a malformed hostname received through socks4, scrub
6777 it if SafeLogging says we should. Fixes bug 17419; bugfix
6780 o Minor bugfixes (memory safety):
6781 - Avoid freeing an uninitialized pointer when opening a socket fails
6782 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
6783 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
6785 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
6786 18672; bugfix on 0.2.5.1-alpha.
6787 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
6790 o Minor bugfixes (pluggable transports):
6791 - Avoid reporting a spurious error when we decide that we don't need
6792 to terminate a pluggable transport because it has already exited.
6793 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
6795 o Minor bugfixes (pointer arithmetic):
6796 - Fix a bug in memarea_alloc() that could have resulted in remote
6797 heap write access, if Tor had ever passed an unchecked size to
6798 memarea_alloc(). Fortunately, all the sizes we pass to
6799 memarea_alloc() are pre-checked to be less than 128 kilobytes.
6800 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
6803 o Minor bugfixes (private directory):
6804 - Prevent a race condition when creating private directories. Fixes
6805 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
6806 Patch from jsturgix. Found with Flawfinder.
6808 o Minor bugfixes (relays):
6809 - Check that both the ORPort and DirPort (if present) are reachable
6810 before publishing a relay descriptor. Otherwise, relays publish a
6811 descriptor with DirPort 0 when the DirPort reachability test takes
6812 longer than the ORPort reachability test. Fixes bug 18050; bugfix
6813 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
6814 - Resolve some edge cases where we might launch an ORPort
6815 reachability check even when DisableNetwork is set. Noticed while
6816 fixing bug 18616; bugfix on 0.2.3.9-alpha.
6818 o Minor bugfixes (relays, hidden services):
6819 - Refuse connection requests to private OR addresses unless
6820 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
6821 then refuse to send any cells to a private address. Fixes bugs
6822 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
6824 o Minor bugfixes (security, hidden services):
6825 - Prevent hidden services connecting to client-supplied rendezvous
6826 addresses that are reserved as internal or multicast. Fixes bug
6827 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
6829 o Minor bugfixes (statistics):
6830 - Consistently check for overflow in round_*_to_next_multiple_of
6831 functions, and add unit tests with additional and maximal values.
6832 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
6833 - Handle edge cases in the laplace functions: avoid division by
6834 zero, avoid taking the log of zero, and silence clang type
6835 conversion warnings using round and trunc. Add unit tests for edge
6836 cases with maximal values. Fixes part of bug 13192; bugfix
6838 - We now include consensus downloads via IPv6 in our directory-
6839 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
6841 o Minor bugfixes (test networks, IPv6):
6842 - Allow internal IPv6 addresses in descriptors in test networks.
6843 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
6846 o Minor bugfixes (testing):
6847 - Check the full results of SHA256 and SHA512 digests in the unit
6848 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
6849 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
6851 - Fix a small memory leak that would occur when the
6852 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
6853 bugfix on 0.2.5.2-alpha.
6854 - Make unit tests pass on IPv6-only systems, and systems without
6855 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
6856 bugfix on 0.2.7.3-rc. Patch by teor.
6857 - The test for log_heartbeat was incorrectly failing in timezones
6858 with non-integer offsets. Instead of comparing the end of the time
6859 string against a constant, compare it to the output of
6860 format_local_iso_time when given the correct input. Fixes bug
6861 18039; bugfix on 0.2.5.4-alpha.
6862 - We no longer disable assertions in the unit tests when coverage is
6863 enabled. Instead, we require you to say --disable-asserts-in-tests
6864 to the configure script if you need assertions disabled in the
6865 unit tests (for example, if you want to perform branch coverage).
6866 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
6868 o Minor bugfixes (time handling):
6869 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
6870 field. Otherwise, our unit tests crash on Windows. Fixes bug
6871 18977; bugfix on 0.2.2.25-alpha.
6872 - Avoid overflow in tor_timegm when parsing dates in and after 2038
6873 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
6874 0.0.2pre14. Patch by teor.
6876 o Minor bugfixes (tor-gencert):
6877 - Correctly handle the case where an authority operator enters a
6878 passphrase but sends an EOF before sending a newline. Fixes bug
6879 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
6881 o Code simplification and refactoring:
6882 - Clean up a little duplicated code in
6883 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
6885 - Decouple the list of streams waiting to be attached to circuits
6886 from the overall connection list. This change makes it possible to
6887 attach streams quickly while simplifying Tor's callgraph and
6888 avoiding O(N) scans of the entire connection list. Closes
6890 - Extract the more complicated parts of circuit_mark_for_close()
6891 into a new function that we run periodically before circuits are
6892 freed. This change removes more than half of the functions
6893 currently in the "blob". Closes ticket 17218.
6894 - Move logging of redundant policy entries in
6895 policies_parse_exit_policy_internal into its own function. Closes
6896 ticket 17608; patch from "juce".
6897 - Quote all the string interpolations in configure.ac -- even those
6898 which we are pretty sure can't contain spaces. Closes ticket
6899 17744. Patch from zerosion.
6900 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
6901 use them. Closes ticket 17926.
6902 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
6903 inplace, so there's no need to have a separate implementation for
6904 the non-inplace code. Closes ticket 18258. Patch from Malek.
6905 - Simplify return types for some crypto functions that can't
6906 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
6907 - When a direct directory request fails immediately on launch,
6908 instead of relaunching that request from inside the code that
6909 launches it, instead mark the connection for teardown. This change
6910 simplifies Tor's callback and prevents the directory-request
6911 launching code from invoking itself recursively. Closes
6915 - Add a description of the correct use of the '--keygen' command-
6916 line option. Closes ticket 17583; based on text by 's7r'.
6917 - Change build messages to refer to "Fedora" instead of "Fedora
6918 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
6919 Patches from "icanhasaccount" and "cypherpunks".
6920 - Document the contents of the 'datadir/keys' subdirectory in the
6921 manual page. Closes ticket 17621.
6922 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
6923 - Explain actual minima for BandwidthRate. Closes ticket 16382.
6924 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
6925 - Mention torspec URL in the manpage and point the reader to it
6926 whenever we mention a document that belongs in torspce. Fixes
6928 - Stop recommending use of nicknames to identify relays in our
6929 MapAddress documentation. Closes ticket 18312.
6932 - Remove client-side support for connecting to Tor relays running
6933 versions of Tor before 0.2.3.6-alpha. These relays didn't support
6934 the v3 TLS handshake protocol, and are no longer allowed on the
6935 Tor network. Implements the client side of ticket 11150. Based on
6936 patches by Tom van der Woerdt.
6937 - We no longer maintain an internal freelist in memarea.c.
6938 Allocators should be good enough to make this code unnecessary,
6939 and it's doubtful that it ever had any performance benefit.
6942 - Add unit tests to check for common RNG failure modes, such as
6943 returning all zeroes, identical values, or incrementing values
6944 (OpenSSL's rand_predictable feature). Patch by teor.
6945 - Always test both ed25519 backends, so that we can be sure that our
6946 batch-open replacement code works. Part of ticket 16794.
6947 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
6948 portion of ticket 16831.
6949 - Fix several warnings from clang's address sanitizer produced in
6951 - Log more information when the backtrace tests fail. Closes ticket
6952 17892. Patch from "cypherpunks."
6953 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
6954 util_format.c, directory.c, and options_validate.c. Closes tickets
6955 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
6957 - Treat backtrace test failures as expected on FreeBSD until we
6958 solve bug 17808. Closes ticket 18204.
6959 - Unit tests for directory_handle_command_get. Closes ticket 17004.
6960 Patch from Reinaldo de Souza Jr.
6963 Changes in version 0.2.7.6 - 2015-12-10
6964 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
6965 well as a minor bug in hidden service reliability.
6967 o Major bugfixes (guard selection):
6968 - Actually look at the Guard flag when selecting a new directory
6969 guard. When we implemented the directory guard design, we
6970 accidentally started treating all relays as if they have the Guard
6971 flag during guard selection, leading to weaker anonymity and worse
6972 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
6975 o Minor features (geoip):
6976 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
6979 o Minor bugfixes (compilation):
6980 - When checking for net/pfvar.h, include netinet/in.h if possible.
6981 This fixes transparent proxy detection on OpenBSD. Fixes bug
6982 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
6983 - Fix a compilation warning with Clang 3.6: Do not check the
6984 presence of an address which can never be NULL. Fixes bug 17781.
6986 o Minor bugfixes (correctness):
6987 - When displaying an IPv6 exit policy, include the mask bits
6988 correctly even when the number is greater than 31. Fixes bug
6989 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
6990 - The wrong list was used when looking up expired intro points in a
6991 rend service object, causing what we think could be reachability
6992 issues for hidden services, and triggering a BUG log. Fixes bug
6993 16702; bugfix on 0.2.7.2-alpha.
6994 - Fix undefined behavior in the tor_cert_checksig function. Fixes
6995 bug 17722; bugfix on 0.2.7.2-alpha.
6998 Changes in version 0.2.7.5 - 2015-11-20
6999 The Tor 0.2.7 release series is dedicated to the memory of Tor user
7000 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
7001 tirelessly to advocate human rights regardless of national borders,
7002 and oppose the encroachments of mass surveillance. He opposed national
7003 exceptionalism, he brought clarity to legal and policy debates, he
7004 understood and predicted the impact of mass surveillance on the world,
7005 and he laid the groundwork for resisting it. While serving on the Tor
7006 Project's board of directors, he brought us his uncompromising focus
7007 on technical excellence in the service of humankind. Caspar was an
7008 inimitable force for good and a wonderful friend. He was kind,
7009 humorous, generous, gallant, and believed we should protect one
7010 another without exception. We honor him here for his ideals, his
7011 efforts, and his accomplishments. Please honor his memory with works
7012 that would make him proud.
7014 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
7016 The 0.2.7 series adds a more secure identity key type for relays,
7017 improves cryptography performance, resolves several longstanding
7018 hidden-service performance issues, improves controller support for
7019 hidden services, and includes small bugfixes and performance
7020 improvements throughout the program. This release series also includes
7021 more tests than before, and significant simplifications to which parts
7022 of Tor invoke which others. For a full list of changes, see below.
7024 o New system requirements:
7025 - Tor no longer includes workarounds to support Libevent versions
7026 before 1.3e. Libevent 2.0 or later is recommended. Closes
7028 - Tor no longer supports copies of OpenSSL that are missing support
7029 for Elliptic Curve Cryptography. (We began using ECC when
7030 available in 0.2.4.8-alpha, for more safe and efficient key
7031 negotiation.) In particular, support for at least one of P256 or
7032 P224 is now required, with manual configuration needed if only
7033 P224 is available. Resolves ticket 16140.
7034 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
7035 on an operating system that has not upgraded to OpenSSL 1.0 or
7036 later, and you compile Tor from source, you will need to install a
7037 more recent OpenSSL to link Tor against.) These versions of
7038 OpenSSL are still supported by the OpenSSL, but the numerous
7039 cryptographic improvements in later OpenSSL releases makes them a
7040 clear choice. Resolves ticket 16034.
7042 o Major features (controller):
7043 - Add the ADD_ONION and DEL_ONION commands that allow the creation
7044 and management of hidden services via the controller. Closes
7046 - New "GETINFO onions/current" and "GETINFO onions/detached"
7047 commands to get information about hidden services created via the
7048 controller. Part of ticket 6411.
7049 - New HSFETCH command to launch a request for a hidden service
7050 descriptor. Closes ticket 14847.
7051 - New HSPOST command to upload a hidden service descriptor. Closes
7052 ticket 3523. Patch by "DonnchaC".
7054 o Major features (Ed25519 identity keys, Proposal 220):
7055 - Add support for offline encrypted Ed25519 master keys. To use this
7056 feature on your tor relay, run "tor --keygen" to make a new master
7057 key (or to make a new signing key if you already have a master
7058 key). Closes ticket 13642.
7059 - All relays now maintain a stronger identity key, using the Ed25519
7060 elliptic curve signature format. This master key is designed so
7061 that it can be kept offline. Relays also generate an online
7062 signing key, and a set of other Ed25519 keys and certificates.
7063 These are all automatically regenerated and rotated as needed.
7064 Implements part of ticket 12498.
7065 - Directory authorities now vote on Ed25519 identity keys along with
7066 RSA1024 keys. Implements part of ticket 12498.
7067 - Directory authorities track which Ed25519 identity keys have been
7068 used with which RSA1024 identity keys, and do not allow them to
7069 vary freely. Implements part of ticket 12498.
7070 - Microdescriptors now include Ed25519 identity keys. Implements
7071 part of ticket 12498.
7072 - Add a --newpass option to allow changing or removing the
7073 passphrase of an encrypted key with tor --keygen. Implements part
7075 - Add a new OfflineMasterKey option to tell Tor never to try loading
7076 or generating a secret Ed25519 identity key. You can use this in
7077 combination with tor --keygen to manage offline and/or encrypted
7078 Ed25519 keys. Implements ticket 16944.
7079 - On receiving a HUP signal, check to see whether the Ed25519
7080 signing key has changed, and reload it if so. Closes ticket 16790.
7081 - Significant usability improvements for Ed25519 key management. Log
7082 messages are better, and the code can recover from far more
7083 failure conditions. Thanks to "s7r" for reporting and diagnosing
7086 o Major features (ECC performance):
7087 - Improve the runtime speed of Ed25519 signature verification by
7088 using Ed25519-donna's batch verification support. Implements
7090 - Improve the speed of Ed25519 operations and Curve25519 keypair
7091 generation when built targeting 32 bit x86 platforms with SSE2
7092 available. Implements ticket 16535.
7093 - Improve the runtime speed of Ed25519 operations by using the
7094 public-domain Ed25519-donna by Andrew M. ("floodyberry").
7095 Implements ticket 16467.
7096 - Improve the runtime speed of the ntor handshake by using an
7097 optimized curve25519 basepoint scalarmult implementation from the
7098 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
7099 ideas by Adam Langley. Implements ticket 9663.
7101 o Major features (Hidden services):
7102 - Hidden services, if using the EntryNodes option, are required to
7103 use more than one EntryNode, in order to avoid a guard discovery
7104 attack. (This would only affect people who had configured hidden
7105 services and manually specified the EntryNodes option with a
7106 single entry-node. The impact was that it would be easy to
7107 remotely identify the guard node used by such a hidden service.
7108 See ticket for more information.) Fixes ticket 14917.
7109 - Add the torrc option HiddenServiceNumIntroductionPoints, to
7110 specify a fixed number of introduction points. Its maximum value
7111 is 10 and default is 3. Using this option can increase a hidden
7112 service's reliability under load, at the cost of making it more
7113 visible that the hidden service is facing extra load. Closes
7115 - Remove the adaptive algorithm for choosing the number of
7116 introduction points, which used to change the number of
7117 introduction points (poorly) depending on the number of
7118 connections the HS sees. Closes ticket 4862.
7120 o Major features (onion key cross-certification):
7121 - Relay descriptors now include signatures of their own identity
7122 keys, made using the TAP and ntor onion keys. These signatures
7123 allow relays to prove ownership of their own onion keys. Because
7124 of this change, microdescriptors will no longer need to include
7125 RSA identity keys. Implements proposal 228; closes ticket 12499.
7127 o Major bugfixes (client-side privacy, also in 0.2.6.9):
7128 - Properly separate out each SOCKSPort when applying stream
7129 isolation. The error occurred because each port's session group
7130 was being overwritten by a default value when the listener
7131 connection was initialized. Fixes bug 16247; bugfix on
7132 0.2.6.3-alpha. Patch by "jojelino".
7134 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
7135 - Stop refusing to store updated hidden service descriptors on a
7136 client. This reverts commit 9407040c59218 (which indeed fixed bug
7137 14219, but introduced a major hidden service reachability
7138 regression detailed in bug 16381). This is a temporary fix since
7139 we can live with the minor issue in bug 14219 (it just results in
7140 some load on the network) but the regression of 16381 is too much
7141 of a setback. First-round fix for bug 16381; bugfix
7144 o Major bugfixes (hidden services):
7145 - Revert commit that made directory authorities assign the HSDir
7146 flag to relays without a DirPort; this was bad because such relays
7147 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
7149 - When cannibalizing a circuit for an introduction point, always
7150 extend to the chosen exit node (creating a 4 hop circuit).
7151 Previously Tor would use the current circuit exit node, which
7152 changed the original choice of introduction point, and could cause
7153 the hidden service to skip excluded introduction points or
7154 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
7157 o Major bugfixes (memory leaks):
7158 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
7159 17398; bugfix on 0.2.6.1-alpha.
7161 o Major bugfixes (open file limit):
7162 - The open file limit wasn't checked before calling
7163 tor_accept_socket_nonblocking(), which would make Tor exceed the
7164 limit. Now, before opening a new socket, Tor validates the open
7165 file limit just before, and if the max has been reached, return an
7166 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
7168 o Major bugfixes (security, correctness):
7169 - Fix an error that could cause us to read 4 bytes before the
7170 beginning of an openssl string. This bug could be used to cause
7171 Tor to crash on systems with unusual malloc implementations, or
7172 systems with unusual hardening installed. Fixes bug 17404; bugfix
7175 o Major bugfixes (stability, also in 0.2.6.10):
7176 - Stop crashing with an assertion failure when parsing certain kinds
7177 of malformed or truncated microdescriptors. Fixes bug 16400;
7178 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
7179 by "cypherpunks_backup".
7180 - Stop random client-side assertion failures that could occur when
7181 connecting to a busy hidden service, or connecting to a hidden
7182 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
7185 o Minor features (client, SOCKS):
7186 - Add GroupWritable and WorldWritable options to unix-socket based
7187 SocksPort and ControlPort options. These options apply to a single
7188 socket, and override {Control,Socks}SocketsGroupWritable. Closes
7190 - Relax the validation done to hostnames in SOCKS5 requests, and
7191 allow a single trailing '.' to cope with clients that pass FQDNs
7192 using that syntax to explicitly indicate that the domain name is
7193 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
7194 - Relax the validation of hostnames in SOCKS5 requests, allowing the
7195 character '_' to appear, in order to cope with domains observed in
7196 the wild that are serving non-RFC compliant records. Resolves
7199 o Minor features (client-side privacy):
7200 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
7201 lifespan when IsolateSOCKSAuth and streams with SOCKS
7202 authentication are attached to the circuit. This allows
7203 applications like TorBrowser to manage circuit lifetime on their
7204 own. Implements feature 15482.
7205 - When logging malformed hostnames from SOCKS5 requests, respect
7206 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
7208 o Minor features (clock-jump tolerance):
7209 - Recover better when our clock jumps back many hours, like might
7210 happen for Tails or Whonix users who start with a very wrong
7211 hardware clock, use Tor to discover a more accurate time, and then
7212 fix their clock. Resolves part of ticket 8766.
7214 o Minor features (command-line interface):
7215 - Make --hash-password imply --hush to prevent unnecessary noise.
7216 Closes ticket 15542. Patch from "cypherpunks".
7217 - Print a warning whenever we find a relative file path being used
7218 as torrc option. Resolves issue 14018.
7220 o Minor features (compilation):
7221 - Give a warning as early as possible when trying to build with an
7222 unsupported OpenSSL version. Closes ticket 16901.
7223 - Use C99 variadic macros when the compiler is not GCC. This avoids
7224 failing compilations on MSVC, and fixes a log-file-based race
7225 condition in our old workarounds. Original patch from Gisle Vanem.
7227 o Minor features (control protocol):
7228 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
7229 the control protocol. Resolves ticket 15358.
7231 o Minor features (controller):
7232 - Add DirAuthority lines for default directory authorities to the
7233 output of the "GETINFO config/defaults" command if not already
7234 present. Implements ticket 14840.
7235 - Controllers can now use "GETINFO hs/client/desc/id/..." to
7236 retrieve items from the client's hidden service descriptor cache.
7237 Closes ticket 14845.
7238 - Implement a new controller command "GETINFO status/fresh-relay-
7239 descs" to fetch a descriptor/extrainfo pair that was generated on
7240 demand just for the controller's use. Implements ticket 14784.
7242 o Minor features (directory authorities):
7243 - Directory authorities no longer vote against the "Fast", "Stable",
7244 and "HSDir" flags just because they were going to vote against
7245 "Running": if the consensus turns out to be that the router was
7246 running, then the authority's vote should count. Patch from Peter
7247 Retzlaff; closes issue 8712.
7249 o Minor features (directory authorities, security, also in 0.2.6.9):
7250 - The HSDir flag given by authorities now requires the Stable flag.
7251 For the current network, this results in going from 2887 to 2806
7252 HSDirs. Also, it makes it harder for an attacker to launch a sybil
7253 attack by raising the effort for a relay to become Stable to
7254 require at the very least 7 days, while maintaining the 96 hours
7255 uptime requirement for HSDir. Implements ticket 8243.
7257 o Minor features (DoS-resistance):
7258 - Make it harder for attackers to overload hidden services with
7259 introductions, by blocking multiple introduction requests on the
7260 same circuit. Resolves ticket 15515.
7262 o Minor features (geoip):
7263 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
7266 o Minor features (hidden services):
7267 - Add the new options "HiddenServiceMaxStreams" and
7268 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
7269 limit the maximum number of simultaneous streams per circuit, and
7270 optionally tear down the circuit when the limit is exceeded. Part
7272 - Client now uses an introduction point failure cache to know when
7273 to fetch or keep a descriptor in their cache. Previously, failures
7274 were recorded implicitly, but not explicitly remembered. Closes
7276 - Relays need to have the Fast flag to get the HSDir flag. As this
7277 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
7278 drop. This change should make some attacks against the hidden
7279 service directory system harder. Fixes ticket 15963.
7280 - Turn on hidden service statistics collection by setting the torrc
7281 option HiddenServiceStatistics to "1" by default. (This keeps
7282 track only of the fraction of traffic used by hidden services, and
7283 the total number of hidden services in existence.) Closes
7285 - To avoid leaking HS popularity, don't cycle the introduction point
7286 when we've handled a fixed number of INTRODUCE2 cells but instead
7287 cycle it when a random number of introductions is reached, thus
7288 making it more difficult for an attacker to find out the amount of
7289 clients that have used the introduction point for a specific HS.
7290 Closes ticket 15745.
7292 o Minor features (logging):
7293 - Include the Tor version in all LD_BUG log messages, since people
7294 tend to cut and paste those into the bugtracker. Implements
7297 o Minor features (pluggable transports):
7298 - When launching managed pluggable transports on Linux systems,
7299 attempt to have the kernel deliver a SIGTERM on tor exit if the
7300 pluggable transport process is still running. Resolves
7302 - When launching managed pluggable transports, setup a valid open
7303 stdin in the child process that can be used to detect if tor has
7304 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
7305 can be used by implementations to detect this new behavior.
7306 Resolves ticket 15435.
7308 o Minor bugfixes (torrc exit policies):
7309 - In each instance above, usage advice is provided to avoid the
7310 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
7311 16069; bugfix on 0.2.4.7-alpha.
7312 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
7313 produce IPv6 wildcard addresses. Previously they would produce
7314 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
7315 of bug 16069; bugfix on 0.2.4.7-alpha.
7316 - When parsing torrc ExitPolicies, we now issue an info-level
7317 message when expanding an "accept/reject *" line to include both
7318 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
7319 - When parsing torrc ExitPolicies, we now warn for a number of cases
7320 where the user's intent is likely to differ from Tor's actual
7321 behavior. These include: using an IPv4 address with an accept6 or
7322 reject6 line; using "private" on an accept6 or reject6 line; and
7323 including any ExitPolicy lines after accept *:* or reject *:*.
7324 Related to ticket 16069.
7326 o Minor bugfixes (command-line interface):
7327 - When "--quiet" is provided along with "--validate-config", do not
7328 write anything to stdout on success. Fixes bug 14994; bugfix
7330 - When complaining about bad arguments to "--dump-config", use
7332 - Print usage information for --dump-config when it is used without
7333 an argument. Also, fix the error message to use different wording
7334 and add newline at the end. Fixes bug 15541; bugfix
7337 o Minor bugfixes (compilation):
7338 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
7339 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
7340 - Repair compilation with the most recent (unreleased, alpha)
7341 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
7343 o Minor bugfixes (compilation, also in 0.2.6.9):
7344 - Build with --enable-systemd correctly when libsystemd is
7345 installed, but systemd is not. Fixes bug 16164; bugfix on
7346 0.2.6.3-alpha. Patch from Peter Palfrader.
7348 o Minor bugfixes (configuration, unit tests):
7349 - Only add the default fallback directories when the DirAuthorities,
7350 AlternateDirAuthority, and FallbackDir directory config options
7351 are set to their defaults. The default fallback directory list is
7352 currently empty, this fix will only change tor's behavior when it
7353 has default fallback directories. Includes unit tests for
7354 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
7355 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
7357 o Minor bugfixes (controller):
7358 - Add the descriptor ID in each HS_DESC control event. It was
7359 missing, but specified in control-spec.txt. Fixes bug 15881;
7360 bugfix on 0.2.5.2-alpha.
7362 o Minor bugfixes (correctness):
7363 - For correctness, avoid modifying a constant string in
7364 handle_control_postdescriptor. Fixes bug 15546; bugfix
7366 - Remove side-effects from tor_assert() calls. This was harmless,
7367 because we never disable assertions, but it is bad style and
7368 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
7370 - When calling channel_free_list(), avoid calling smartlist_remove()
7371 while inside a FOREACH loop. This partially reverts commit
7372 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
7373 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
7375 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
7376 - Check for failures from crypto_early_init, and refuse to continue.
7377 A previous typo meant that we could keep going with an
7378 uninitialized crypto library, and would have OpenSSL initialize
7379 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7380 when implementing ticket 4900. Patch by "teor".
7382 o Minor bugfixes (hidden service):
7383 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7384 a client authorized hidden service. Fixes bug 15823; bugfix
7386 - Remove an extraneous newline character from the end of hidden
7387 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
7389 o Minor bugfixes (Linux seccomp2 sandbox):
7390 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
7391 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
7392 - Allow bridge authorities to run correctly under the seccomp2
7393 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
7394 - Add the "hidserv-stats" filename to our sandbox filter for the
7395 HiddenServiceStatistics option to work properly. Fixes bug 17354;
7396 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
7398 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
7399 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
7400 these when eventfd2() support is missing. Fixes bug 16363; bugfix
7401 on 0.2.6.3-alpha. Patch from "teor".
7403 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
7404 - Allow systemd connections to work with the Linux seccomp2 sandbox
7405 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
7407 - Fix sandboxing to work when running as a relay, by allowing the
7408 renaming of secret_id_key, and allowing the eventfd2 and futex
7409 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
7412 o Minor bugfixes (logging):
7413 - When building Tor under Clang, do not include an extra set of
7414 parentheses in log messages that include function names. Fixes bug
7415 15269; bugfix on every released version of Tor when compiled with
7416 recent enough Clang.
7418 o Minor bugfixes (network):
7419 - When attempting to use fallback technique for network interface
7420 lookup, disregard loopback and multicast addresses since they are
7421 unsuitable for public communications.
7423 o Minor bugfixes (open file limit):
7424 - Fix set_max_file_descriptors() to set by default the max open file
7425 limit to the current limit when setrlimit() fails. Fixes bug
7426 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
7428 o Minor bugfixes (portability):
7429 - Check correctly for Windows socket errors in the workqueue
7430 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
7431 - Try harder to normalize the exit status of the Tor process to the
7432 standard-provided range. Fixes bug 16975; bugfix on every version
7434 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
7435 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
7437 o Minor bugfixes (relay):
7438 - Ensure that worker threads actually exit when a fatal error or
7439 shutdown is indicated. This fix doesn't currently affect the
7440 behavior of Tor, because Tor workers never indicates fatal error
7441 or shutdown except in the unit tests. Fixes bug 16868; bugfix
7443 - Fix a rarely-encountered memory leak when failing to initialize
7444 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
7446 - Unblock threads before releasing the work queue mutex to ensure
7447 predictable scheduling behavior. Fixes bug 16644; bugfix
7450 o Minor bugfixes (security, exit policies):
7451 - ExitPolicyRejectPrivate now also rejects the relay's published
7452 IPv6 address (if any), and any publicly routable IPv4 or IPv6
7453 addresses on any local interfaces. ticket 17027. Patch by "teor".
7454 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
7456 o Minor bugfixes (statistics):
7457 - Disregard the ConnDirectionStatistics torrc options when Tor is
7458 not a relay since in that mode of operation no sensible data is
7459 being collected and because Tor might run into measurement hiccups
7460 when running as a client for some time, then becoming a relay.
7461 Fixes bug 15604; bugfix on 0.2.2.35.
7463 o Minor bugfixes (systemd):
7464 - Tor's systemd unit file no longer contains extraneous spaces.
7465 These spaces would sometimes confuse tools like deb-systemd-
7466 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
7468 o Minor bugfixes (test networks):
7469 - When self-testing reachability, use ExtendAllowPrivateAddresses to
7470 determine if local/private addresses imply reachability. The
7471 previous fix used TestingTorNetwork, which implies
7472 ExtendAllowPrivateAddresses, but this excluded rare configurations
7473 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
7474 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
7475 issue discovered by CJ Ess.
7477 o Minor bugfixes (tests, also in 0.2.6.9):
7478 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
7479 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
7481 o Code simplification and refactoring:
7482 - Change the function that's called when we need to retry all
7483 downloads so that it only reschedules the downloads to happen
7484 immediately, rather than launching them all at once itself. This
7485 further simplifies Tor's callgraph.
7486 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
7487 to ensure they remain consistent and visible everywhere.
7488 - Move some format-parsing functions out of crypto.c and
7489 crypto_curve25519.c into crypto_format.c and/or util_format.c.
7490 - Move the client-only parts of init_keys() into a separate
7491 function. Closes ticket 16763.
7492 - Move the hacky fallback code out of get_interface_address6() into
7493 separate function and get it covered with unit-tests. Resolves
7495 - Refactor hidden service client-side cache lookup to intelligently
7496 report its various failure cases, and disentangle failure cases
7497 involving a lack of introduction points. Closes ticket 14391.
7498 - Remove some vestigial workarounds for the MSVC6 compiler. We
7499 haven't supported that in ages.
7500 - Remove the unused "nulterminate" argument from buf_pullup().
7501 - Simplify the microdesc_free() implementation so that it no longer
7502 appears (to code analysis tools) to potentially invoke a huge
7503 suite of other microdesc functions.
7504 - Simply the control graph further by deferring the inner body of
7505 directory_all_unreachable() into a callback. Closes ticket 16762.
7506 - The link authentication code has been refactored for better
7507 testability and reliability. It now uses code generated with the
7508 "trunnel" binary encoding generator, to reduce the risk of bugs
7509 due to programmer error. Done as part of ticket 12498.
7510 - Treat the loss of an owning controller as equivalent to a SIGTERM
7511 signal. This removes a tiny amount of duplicated code, and
7512 simplifies our callgraph. Closes ticket 16788.
7513 - Use our own Base64 encoder instead of OpenSSL's, to allow more
7514 control over the output. Part of ticket 15652.
7515 - When generating an event to send to the controller, we no longer
7516 put the event over the network immediately. Instead, we queue
7517 these events, and use a Libevent callback to deliver them. This
7518 change simplifies Tor's callgraph by reducing the number of
7519 functions from which all other Tor functions are reachable. Closes
7521 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
7522 that try to scan or compile every file on Unix won't decide that
7526 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
7527 - Improve the descriptions of statistics-related torrc options in
7528 the manpage to describe rationale and possible uses cases. Fixes
7530 - Improve the layout and formatting of ./configure --help messages.
7531 Closes ticket 15024. Patch from "cypherpunks".
7532 - Include a specific and (hopefully) accurate documentation of the
7533 torrc file's meta-format in doc/torrc_format.txt. This is mainly
7534 of interest to people writing programs to parse or generate torrc
7535 files. This document is not a commitment to long-term
7536 compatibility; some aspects of the current format are a bit
7537 ridiculous. Closes ticket 2325.
7538 - Include the TUNING document in our source tarball. It is referred
7539 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
7541 - Note that HiddenServicePorts can take a unix domain socket. Closes
7543 - Recommend a 40 GB example AccountingMax in torrc.sample rather
7544 than a 4 GB max. Closes ticket 16742.
7545 - Standardize on the term "server descriptor" in the manual page.
7546 Previously, we had used "router descriptor", "server descriptor",
7547 and "relay descriptor" interchangeably. Part of ticket 14987.
7548 - Advise users on how to configure separate IPv4 and IPv6 exit
7549 policies in the manpage and sample torrcs. Related to ticket 16069.
7550 - Fix an error in the manual page and comments for
7551 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
7552 required "ORPort connectivity". While this is true, it is in no
7553 way unique to the HSDir flag. Of all the flags, only HSDirs need a
7554 DirPort configured in order for the authorities to assign that
7555 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
7557 - Fix the usage message of tor-resolve(1) so that it no longer lists
7558 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
7561 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
7562 and always use the internal Base64 decoder. The internal decoder
7563 has been part of tor since 0.2.0.10-alpha, and no one should
7564 be using the OpenSSL one. Part of ticket 15652.
7565 - Remove the 'tor_strclear()' function; use memwipe() instead.
7566 Closes ticket 14922.
7567 - Remove the code that would try to aggressively flush controller
7568 connections while writing to them. This code was introduced in
7569 0.1.2.7-alpha, in order to keep output buffers from exceeding
7570 their limits. But there is no longer a maximum output buffer size,
7571 and flushing data in this way caused some undesirable recursions
7572 in our call graph. Closes ticket 16480.
7573 - The internal pure-C tor-fw-helper tool is now removed from the Tor
7574 distribution, in favor of the pure-Go clone available from
7575 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
7576 used by the C tor-fw-helper are not, in our opinion, very
7577 confidence- inspiring in their secure-programming techniques.
7578 Closes ticket 13338.
7581 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
7582 fingerprinting we now recommend pluggable transports; for forward-
7583 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
7584 - Remove the HidServDirectoryV2 option. Now all relays offer to
7585 store hidden service descriptors. Related to 16543.
7586 - Remove the VoteOnHidServDirectoriesV2 option, since all
7587 authorities have long set it to 1. Closes ticket 16543.
7588 - Remove the undocumented "--digests" command-line option. It
7589 complicated our build process, caused subtle build issues on
7590 multiple platforms, and is now redundant since we started
7591 including git version identifiers. Closes ticket 14742.
7592 - Tor no longer contains checks for ancient directory cache versions
7593 that didn't know about microdescriptors.
7594 - Tor no longer contains workarounds for stat files generated by
7595 super-old versions of Tor that didn't choose guards sensibly.
7598 - The test-network.sh script now supports performance testing.
7599 Requires corresponding chutney performance testing changes. Patch
7600 by "teor". Closes ticket 14175.
7601 - Add a new set of callgraph analysis scripts that use clang to
7602 produce a list of which Tor functions are reachable from which
7603 other Tor functions. We're planning to use these to help simplify
7604 our code structure by identifying illogical dependencies.
7605 - Add new 'test-full' and 'test-full-online' targets to run all
7606 tests, including integration tests with stem and chutney.
7607 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
7608 by-side in the same parent directory. Closes ticket 16903. Patch
7610 - Document use of coverity, clang static analyzer, and clang dynamic
7611 undefined behavior and address sanitizers in doc/HACKING. Include
7612 detailed usage instructions in the blacklist. Patch by "teor".
7613 Closes ticket 15817.
7614 - Make "bridges+hs" the default test network. This tests almost all
7615 tor functionality during make test-network, while allowing tests
7616 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
7617 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
7618 (chutney). Patches by "teor".
7619 - Make the test-workqueue test work on Windows by initializing the
7620 network before we begin.
7621 - New make target (make test-network-all) to run multiple applicable
7622 chutney test cases. Patch from Teor; closes 16953.
7623 - Now that OpenSSL has its own scrypt implementation, add an unit
7624 test that checks for interoperability between libscrypt_scrypt()
7625 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
7626 and rely on EVP_PBE_scrypt() whenever possible. Resolves
7628 - The link authentication protocol code now has extensive tests.
7629 - The relay descriptor signature testing code now has
7631 - The test_workqueue program now runs faster, and is enabled by
7632 default as a part of "make check".
7633 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
7634 functions in dns.c. Implements a portion of ticket 16831.
7635 - Use environment variables rather than autoconf substitutions to
7636 send variables from the build system to the test scripts. This
7637 change should be easier to maintain, and cause 'make distcheck' to
7638 work better than before. Fixes bug 17148.
7639 - When building Tor with testing coverage enabled, run Chutney tests
7640 (if any) using the 'tor-cov' coverage binary.
7641 - When running test-network or test-stem, check for the absence of
7642 stem/chutney before doing any build operations.
7643 - Add a test to verify that the compiler does not eliminate our
7644 memwipe() implementation. Closes ticket 15377.
7645 - Add make rule `check-changes` to verify the format of changes
7646 files. Closes ticket 15180.
7647 - Add unit tests for control_event_is_interesting(). Add a compile-
7648 time check that the number of events doesn't exceed the capacity
7649 of control_event_t.event_mask. Closes ticket 15431, checks for
7650 bugs similar to 13085. Patch by "teor".
7651 - Command-line argument tests moved to Stem. Resolves ticket 14806.
7652 - Integrate the ntor, backtrace, and zero-length keys tests into the
7653 automake test suite. Closes ticket 15344.
7654 - Remove assertions during builds to determine Tor's test coverage.
7655 We don't want to trigger these even in assertions, so including
7656 them artificially makes our branch coverage look worse than it is.
7657 This patch provides the new test-stem-full and coverage-html-full
7658 configure options. Implements ticket 15400.
7659 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
7660 explicitly manage consensus flags in testing networks. Patch by
7661 "robgjansen", modified by "teor". Implements part of ticket 14882.
7662 - Check for matching value in server response in ntor_ref.py. Fixes
7663 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
7665 - Set the severity correctly when testing
7666 get_interface_addresses_ifaddrs() and
7667 get_interface_addresses_win32(), so that the tests fail gracefully
7668 instead of triggering an assertion. Fixes bug 15759; bugfix on
7669 0.2.6.3-alpha. Reported by Nicolas Derive.
7671 Changes in version 0.2.6.10 - 2015-07-12
7672 Tor version 0.2.6.10 fixes some significant stability and hidden
7673 service client bugs, bulletproofs the cryptography init process, and
7674 fixes a bug when using the sandbox code with some older versions of
7675 Linux. Everyone running an older version, especially an older version
7676 of 0.2.6, should upgrade.
7678 o Major bugfixes (hidden service clients, stability):
7679 - Stop refusing to store updated hidden service descriptors on a
7680 client. This reverts commit 9407040c59218 (which indeed fixed bug
7681 14219, but introduced a major hidden service reachability
7682 regression detailed in bug 16381). This is a temporary fix since
7683 we can live with the minor issue in bug 14219 (it just results in
7684 some load on the network) but the regression of 16381 is too much
7685 of a setback. First-round fix for bug 16381; bugfix
7688 o Major bugfixes (stability):
7689 - Stop crashing with an assertion failure when parsing certain kinds
7690 of malformed or truncated microdescriptors. Fixes bug 16400;
7691 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
7692 by "cypherpunks_backup".
7693 - Stop random client-side assertion failures that could occur when
7694 connecting to a busy hidden service, or connecting to a hidden
7695 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
7698 o Minor features (geoip):
7699 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
7700 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
7702 o Minor bugfixes (crypto error-handling):
7703 - Check for failures from crypto_early_init, and refuse to continue.
7704 A previous typo meant that we could keep going with an
7705 uninitialized crypto library, and would have OpenSSL initialize
7706 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7707 when implementing ticket 4900. Patch by "teor".
7709 o Minor bugfixes (Linux seccomp2 sandbox):
7710 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
7711 these when eventfd2() support is missing. Fixes bug 16363; bugfix
7712 on 0.2.6.3-alpha. Patch from "teor".
7715 Changes in version 0.2.6.9 - 2015-06-11
7716 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
7717 requirements for receiving an HSDir flag, and addresses some other small
7718 bugs in the systemd and sandbox code. Clients using circuit isolation
7719 should upgrade; all directory authorities should upgrade.
7721 o Major bugfixes (client-side privacy):
7722 - Properly separate out each SOCKSPort when applying stream
7723 isolation. The error occurred because each port's session group was
7724 being overwritten by a default value when the listener connection
7725 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
7728 o Minor feature (directory authorities, security):
7729 - The HSDir flag given by authorities now requires the Stable flag.
7730 For the current network, this results in going from 2887 to 2806
7731 HSDirs. Also, it makes it harder for an attacker to launch a sybil
7732 attack by raising the effort for a relay to become Stable which
7733 takes at the very least 7 days to do so and by keeping the 96
7734 hours uptime requirement for HSDir. Implements ticket 8243.
7736 o Minor bugfixes (compilation):
7737 - Build with --enable-systemd correctly when libsystemd is
7738 installed, but systemd is not. Fixes bug 16164; bugfix on
7739 0.2.6.3-alpha. Patch from Peter Palfrader.
7741 o Minor bugfixes (Linux seccomp2 sandbox):
7742 - Fix sandboxing to work when running as a relaymby renaming of
7743 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
7744 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
7745 - Allow systemd connections to work with the Linux seccomp2 sandbox
7746 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
7749 o Minor bugfixes (tests):
7750 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
7751 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
7754 Changes in version 0.2.6.8 - 2015-05-21
7755 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
7756 fixes an authority-side bug in assigning the HSDir flag. All directory
7757 authorities should upgrade.
7759 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
7760 - Revert commit that made directory authorities assign the HSDir
7761 flag to relays without a DirPort; this was bad because such relays
7762 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
7765 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7766 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7767 a client authorized hidden service. Fixes bug 15823; bugfix
7770 o Minor features (geoip):
7771 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
7772 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
7776 Changes in version 0.2.6.7 - 2015-04-06
7777 Tor 0.2.6.7 fixes two security issues that could be used by an
7778 attacker to crash hidden services, or crash clients visiting hidden
7779 services. Hidden services should upgrade as soon as possible; clients
7780 should upgrade whenever packages become available.
7782 This release also contains two simple improvements to make hidden
7783 services a bit less vulnerable to denial-of-service attacks.
7785 o Major bugfixes (security, hidden service):
7786 - Fix an issue that would allow a malicious client to trigger an
7787 assertion failure and halt a hidden service. Fixes bug 15600;
7788 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7789 - Fix a bug that could cause a client to crash with an assertion
7790 failure when parsing a malformed hidden service descriptor. Fixes
7791 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7793 o Minor features (DoS-resistance, hidden service):
7794 - Introduction points no longer allow multiple INTRODUCE1 cells to
7795 arrive on the same circuit. This should make it more expensive for
7796 attackers to overwhelm hidden services with introductions.
7797 Resolves ticket 15515.
7798 - Decrease the amount of reattempts that a hidden service performs
7799 when its rendezvous circuits fail. This reduces the computational
7800 cost for running a hidden service under heavy load. Resolves
7804 Changes in version 0.2.5.12 - 2015-04-06
7805 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
7806 could be used by an attacker to crash hidden services, or crash clients
7807 visiting hidden services. Hidden services should upgrade as soon as
7808 possible; clients should upgrade whenever packages become available.
7810 This release also backports a simple improvement to make hidden
7811 services a bit less vulnerable to denial-of-service attacks.
7813 o Major bugfixes (security, hidden service):
7814 - Fix an issue that would allow a malicious client to trigger an
7815 assertion failure and halt a hidden service. Fixes bug 15600;
7816 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7817 - Fix a bug that could cause a client to crash with an assertion
7818 failure when parsing a malformed hidden service descriptor. Fixes
7819 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7821 o Minor features (DoS-resistance, hidden service):
7822 - Introduction points no longer allow multiple INTRODUCE1 cells to
7823 arrive on the same circuit. This should make it more expensive for
7824 attackers to overwhelm hidden services with introductions.
7825 Resolves ticket 15515.
7828 Changes in version 0.2.4.27 - 2015-04-06
7829 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
7830 could be used by an attacker to crash hidden services, or crash clients
7831 visiting hidden services. Hidden services should upgrade as soon as
7832 possible; clients should upgrade whenever packages become available.
7834 This release also backports a simple improvement to make hidden
7835 services a bit less vulnerable to denial-of-service attacks.
7837 o Major bugfixes (security, hidden service):
7838 - Fix an issue that would allow a malicious client to trigger an
7839 assertion failure and halt a hidden service. Fixes bug 15600;
7840 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
7841 - Fix a bug that could cause a client to crash with an assertion
7842 failure when parsing a malformed hidden service descriptor. Fixes
7843 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
7845 o Minor features (DoS-resistance, hidden service):
7846 - Introduction points no longer allow multiple INTRODUCE1 cells to
7847 arrive on the same circuit. This should make it more expensive for
7848 attackers to overwhelm hidden services with introductions.
7849 Resolves ticket 15515.
7852 Changes in version 0.2.6.6 - 2015-03-24
7853 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
7855 It adds numerous safety, security, correctness, and performance
7856 improvements. Client programs can be configured to use more kinds of
7857 sockets, AutomapHosts works better, the multithreading backend is
7858 improved, cell transmission is refactored, test coverage is much
7859 higher, more denial-of-service attacks are handled, guard selection is
7860 improved to handle long-term guards better, pluggable transports
7861 should work a bit better, and some annoying hidden service performance
7862 bugs should be addressed.
7864 o New compiler and system requirements:
7865 - Tor 0.2.6.x requires that your compiler support more of the C99
7866 language standard than before. The 'configure' script now detects
7867 whether your compiler supports C99 mid-block declarations and
7868 designated initializers. If it does not, Tor will not compile.
7870 We may revisit this requirement if it turns out that a significant
7871 number of people need to build Tor with compilers that don't
7872 bother implementing a 15-year-old standard. Closes ticket 13233.
7873 - Tor no longer supports systems without threading support. When we
7874 began working on Tor, there were several systems that didn't have
7875 threads, or where the thread support wasn't able to run the
7876 threads of a single process on multiple CPUs. That no longer
7877 holds: every system where Tor needs to run well now has threading
7878 support. Resolves ticket 12439.
7880 o Deprecated versions and removed support:
7881 - Tor relays older than 0.2.4.18-rc are no longer allowed to
7882 advertise themselves on the network. Closes ticket 13555.
7883 - Tor clients no longer support connecting to hidden services
7884 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
7885 option has been removed. (There shouldn't be any hidden services
7886 running these versions on the network.) Closes ticket 7803.
7888 o Directory authority changes:
7889 - The directory authority Faravahar has a new IP address. This
7890 closes ticket 14487.
7891 - Remove turtles as a directory authority.
7892 - Add longclaw as a new (v3) directory authority. This implements
7893 ticket 13296. This keeps the directory authority count at 9.
7895 o Major features (bridges):
7896 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
7897 transports if they are configured via the "TOR_PT_PROXY"
7898 environment variable. Implements proposal 232. Resolves
7901 o Major features (changed defaults):
7902 - Prevent relay operators from unintentionally running exits: When a
7903 relay is configured as an exit node, we now warn the user unless
7904 the "ExitRelay" option is set to 1. We warn even more loudly if
7905 the relay is configured with the default exit policy, since this
7906 can indicate accidental misconfiguration. Setting "ExitRelay 0"
7907 stops Tor from running as an exit relay. Closes ticket 10067.
7909 o Major features (client performance, hidden services):
7910 - Allow clients to use optimistic data when connecting to a hidden
7911 service, which should remove a round-trip from hidden service
7912 initialization. See proposal 181 for details. Implements
7915 o Major features (directory system):
7916 - Upon receiving an unparseable directory object, if its digest
7917 matches what we expected, then don't try to download it again.
7918 Previously, when we got a descriptor we didn't like, we would keep
7919 trying to download it over and over. Closes ticket 11243.
7920 - When downloading server- or microdescriptors from a directory
7921 server, we no longer launch multiple simultaneous requests to the
7922 same server. This reduces load on the directory servers,
7923 especially when directory guards are in use. Closes ticket 9969.
7924 - When downloading server- or microdescriptors over a tunneled
7925 connection, do not limit the length of our requests to what the
7926 Squid proxy is willing to handle. Part of ticket 9969.
7927 - Authorities can now vote on the correct digests and latest
7928 versions for different software packages. This allows packages
7929 that include Tor to use the Tor authority system as a way to get
7930 notified of updates and their correct digests. Implements proposal
7931 227. Closes ticket 10395.
7933 o Major features (guards):
7934 - Introduce the Guardfraction feature to improves load balancing on
7935 guard nodes. Specifically, it aims to reduce the traffic gap that
7936 guard nodes experience when they first get the Guard flag. This is
7937 a required step if we want to increase the guard lifetime to 9
7938 months or greater. Closes ticket 9321.
7940 o Major features (hidden services):
7941 - Make HS port scanning more difficult by immediately closing the
7942 circuit when a user attempts to connect to a nonexistent port.
7943 Closes ticket 13667.
7944 - Add a HiddenServiceStatistics option that allows Tor relays to
7945 gather and publish statistics about the overall size and volume of
7946 hidden service usage. Specifically, when this option is turned on,
7947 an HSDir will publish an approximate number of hidden services
7948 that have published descriptors to it the past 24 hours. Also, if
7949 a relay has acted as a hidden service rendezvous point, it will
7950 publish the approximate amount of rendezvous cells it has relayed
7951 the past 24 hours. The statistics themselves are obfuscated so
7952 that the exact values cannot be derived. For more details see
7953 proposal 238, "Better hidden service stats from Tor relays". This
7954 feature is currently disabled by default. Implements feature 13192.
7956 o Major features (performance):
7957 - Make the CPU worker implementation more efficient by avoiding the
7958 kernel and lengthening pipelines. The original implementation used
7959 sockets to transfer data from the main thread to the workers, and
7960 didn't allow any thread to be assigned more than a single piece of
7961 work at once. The new implementation avoids communications
7962 overhead by making requests in shared memory, avoiding kernel IO
7963 where possible, and keeping more requests in flight at once.
7964 Implements ticket 9682.
7966 o Major features (relay):
7967 - Raise the minimum acceptable configured bandwidth rate for bridges
7968 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
7969 20 KiB/sec.) Closes ticket 13822.
7970 - Complete revision of the code that relays use to decide which cell
7971 to send next. Formerly, we selected the best circuit to write on
7972 each channel, but we didn't select among channels in any
7973 sophisticated way. Now, we choose the best circuits globally from
7974 among those whose channels are ready to deliver traffic.
7976 This patch implements a new inter-cmux comparison API, a global
7977 high/low watermark mechanism and a global scheduler loop for
7978 transmission prioritization across all channels as well as among
7979 circuits on one channel. This schedule is currently tuned to
7980 (tolerantly) avoid making changes in network performance, but it
7981 should form the basis for major circuit performance increases in
7982 the future. Code by Andrea; tuning by Rob Jansen; implements
7985 o Major features (sample torrc):
7986 - Add a new, infrequently-changed "torrc.minimal". This file is
7987 similar to torrc.sample, but it will change as infrequently as
7988 possible, for the benefit of users whose systems prompt them for
7989 intervention whenever a default configuration file is changed.
7990 Making this change allows us to update torrc.sample to be a more
7991 generally useful "sample torrc".
7993 o Major features (security, unix domain sockets):
7994 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
7995 applications can reach Tor without having to create AF_INET or
7996 AF_INET6 sockets, meaning they can completely disable their
7997 ability to make non-Tor network connections. To create a socket of
7998 this type, use "SocksPort unix:/path/to/socket". Implements
8000 - Support mapping hidden service virtual ports to AF_UNIX sockets.
8001 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
8002 Implements ticket 11485.
8004 o Major bugfixes (client, automap):
8005 - Repair automapping with IPv6 addresses. This automapping should
8006 have worked previously, but one piece of debugging code that we
8007 inserted to detect a regression actually caused the regression to
8008 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
8009 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
8012 o Major bugfixes (crash, OSX, security):
8013 - Fix a remote denial-of-service opportunity caused by a bug in
8014 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
8017 o Major bugfixes (directory authorities):
8018 - Do not assign the HSDir flag to relays if they are not Valid, or
8019 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
8021 o Major bugfixes (directory bandwidth performance):
8022 - Don't flush the zlib buffer aggressively when compressing
8023 directory information for clients. This should save about 7% of
8024 the bandwidth currently used for compressed descriptors and
8025 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
8027 o Major bugfixes (exit node stability):
8028 - Fix an assertion failure that could occur under high DNS load.
8029 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8030 diagnosed and fixed by "cypherpunks".
8032 o Major bugfixes (FreeBSD IPFW transparent proxy):
8033 - Fix address detection with FreeBSD transparent proxies, when
8034 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
8037 o Major bugfixes (hidden services):
8038 - When closing an introduction circuit that was opened in parallel
8039 with others, don't mark the introduction point as unreachable.
8040 Previously, the first successful connection to an introduction
8041 point would make the other introduction points get marked as
8042 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
8044 o Major bugfixes (Linux seccomp2 sandbox):
8045 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
8046 crash during attempts to call wait4. Fixes bug 15088; bugfix on
8047 0.2.5.1-alpha. Patch from "sanic".
8049 o Major bugfixes (mixed relay-client operation):
8050 - When running as a relay and client at the same time (not
8051 recommended), if we decide not to use a new guard because we want
8052 to retry older guards, only close the locally-originating circuits
8053 passing through that guard. Previously we would close all the
8054 circuits through that guard. Fixes bug 9819; bugfix on
8055 0.2.1.1-alpha. Reported by "skruffy".
8057 o Major bugfixes (pluggable transports):
8058 - Initialize the extended OR Port authentication cookie before
8059 launching pluggable transports. This prevents a race condition
8060 that occurred when server-side pluggable transports would cache the
8061 authentication cookie before it has been (re)generated. Fixes bug
8062 15240; bugfix on 0.2.5.1-alpha.
8064 o Major bugfixes (relay, stability, possible security):
8065 - Fix a bug that could lead to a relay crashing with an assertion
8066 failure if a buffer of exactly the wrong layout is passed to
8067 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8068 0.2.0.10-alpha. Patch from "cypherpunks".
8069 - Do not assert if the 'data' pointer on a buffer is advanced to the
8070 very end of the buffer; log a BUG message instead. Only assert if
8071 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8073 o Minor features (build):
8074 - New --disable-system-torrc compile-time option to prevent Tor from
8075 looking for the system-wide torrc or torrc-defaults files.
8076 Resolves ticket 13037.
8078 o Minor features (client):
8079 - Clients are now willing to send optimistic data (before they
8080 receive a 'connected' cell) to relays of any version. (Relays
8081 without support for optimistic data are no longer supported on the
8082 Tor network.) Resolves ticket 13153.
8084 o Minor features (client):
8085 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
8086 is enabled, reject requests with IP addresses as hostnames.
8087 Resolves ticket 13315.
8089 o Minor features (controller):
8090 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
8091 write an unscheduled heartbeat message to the log. Implements
8093 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
8094 events so controllers can observe circuit isolation inputs. Closes
8096 - ControlPort now supports the unix:/path/to/socket syntax as an
8097 alternative to the ControlSocket option, for consistency with
8098 SocksPort and HiddenServicePort. Closes ticket 14451.
8099 - New "GETINFO bw-event-cache" to get information about recent
8100 bandwidth events. Closes ticket 14128. Useful for controllers to
8101 get recent bandwidth history after the fix for ticket 13988.
8102 - Messages about problems in the bootstrap process now include
8103 information about the server we were trying to connect to when we
8104 noticed the problem. Closes ticket 15006.
8106 o Minor features (Denial of service resistance):
8107 - Count the total number of bytes used storing hidden service
8108 descriptors against the value of MaxMemInQueues. If we're low on
8109 memory, and more than 20% of our memory is used holding hidden
8110 service descriptors, free them until no more than 10% of our
8111 memory holds hidden service descriptors. Free the least recently
8112 fetched descriptors first. Resolves ticket 13806.
8113 - When we have recently been under memory pressure (over 3/4 of
8114 MaxMemInQueues is allocated), then allocate smaller zlib objects
8115 for small requests. Closes ticket 11791.
8117 o Minor features (directory authorities):
8118 - Don't list relays with a bandwidth estimate of 0 in the consensus.
8119 Implements a feature proposed during discussion of bug 13000.
8120 - In tor-gencert, report an error if the user provides the same
8121 argument more than once.
8122 - If a directory authority can't find a best consensus method in the
8123 votes that it holds, it now falls back to its favorite consensus
8124 method. Previously, it fell back to method 1. Neither of these is
8125 likely to get enough signatures, but "fall back to favorite"
8126 doesn't require us to maintain support an obsolete consensus
8127 method. Implements part of proposal 215.
8129 o Minor features (geoip):
8130 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8131 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8134 o Minor features (guard nodes):
8135 - Reduce the time delay before saving guard status to disk from 10
8136 minutes to 30 seconds (or from one hour to 10 minutes if
8137 AvoidDiskWrites is set). Closes ticket 12485.
8139 o Minor features (heartbeat):
8140 - On relays, report how many connections we negotiated using each
8141 version of the Tor link protocols. This information will let us
8142 know if removing support for very old versions of the Tor
8143 protocols is harming the network. Closes ticket 15212.
8145 o Minor features (hidden service):
8146 - Make Sybil attacks against hidden services harder by changing the
8147 minimum time required to get the HSDir flag from 25 hours up to 96
8148 hours. Addresses ticket 14149.
8149 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
8150 services to disable the anti-scanning feature introduced in
8151 0.2.6.2-alpha. With this option not set, a connection to an
8152 unlisted port closes the circuit. With this option set, only a
8153 RELAY_DONE cell is sent. Closes ticket 14084.
8154 - When re-enabling the network, don't try to build introduction
8155 circuits until we have successfully built a circuit. This makes
8156 hidden services come up faster when the network is re-enabled.
8157 Patch from "akwizgran". Closes ticket 13447.
8158 - When we fail to retrieve a hidden service descriptor, send the
8159 controller an "HS_DESC FAILED" controller event. Implements
8161 - New HiddenServiceDirGroupReadable option to cause hidden service
8162 directories and hostname files to be created group-readable. Patch
8163 from "anon", David Stainton, and "meejah". Closes ticket 11291.
8165 o Minor features (interface):
8166 - Implement "-f -" command-line option to read torrc configuration
8167 from standard input, if you don't want to store the torrc file in
8168 the file system. Implements feature 13865.
8170 o Minor features (logging):
8171 - Add a count of unique clients to the bridge heartbeat message.
8172 Resolves ticket 6852.
8173 - Suppress "router info incompatible with extra info" message when
8174 reading extrainfo documents from cache. (This message got loud
8175 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
8177 - Elevate hidden service authorized-client message from DEBUG to
8178 INFO. Closes ticket 14015.
8179 - On Unix-like systems, you can now use named pipes as the target of
8180 the Log option, and other options that try to append to files.
8181 Closes ticket 12061. Patch from "carlo von lynX".
8182 - When opening a log file at startup, send it every log message that
8183 we generated between startup and opening it. Previously, log
8184 messages that were generated before opening the log file were only
8185 logged to stdout. Closes ticket 6938.
8186 - Add a TruncateLogFile option to overwrite logs instead of
8187 appending to them. Closes ticket 5583.
8188 - Quiet some log messages in the heartbeat and at startup. Closes
8191 o Minor features (portability, Solaris):
8192 - Threads are no longer disabled by default on Solaris; we believe
8193 that the versions of Solaris with broken threading support are all
8194 obsolete by now. Resolves ticket 9495.
8196 o Minor features (relay):
8197 - Re-check our address after we detect a changed IP address from
8198 getsockname(). This ensures that the controller command "GETINFO
8199 address" will report the correct value. Resolves ticket 11582.
8201 - A new AccountingRule option lets Relays set whether they'd like
8202 AccountingMax to be applied separately to inbound and outbound
8203 traffic, or applied to the sum of inbound and outbound traffic.
8204 Resolves ticket 961. Patch by "chobe".
8205 - When identity keypair is generated for first time, log a
8206 congratulatory message that links to the new relay lifecycle
8207 document. Implements feature 10427.
8209 o Minor features (security, memory wiping):
8210 - Ensure we securely wipe keys from memory after
8211 crypto_digest_get_digest and init_curve25519_keypair_from_file
8212 have finished using them. Resolves ticket 13477.
8214 o Minor features (security, out-of-memory handling):
8215 - When handling an out-of-memory condition, allocate less memory for
8216 temporary data structures. Fixes issue 10115.
8217 - When handling an out-of-memory condition, consider more types of
8218 buffers, including those on directory connections, and zlib
8219 buffers. Resolves ticket 11792.
8221 o Minor features (stability):
8222 - Add assertions in our hash-table iteration code to check for
8223 corrupted values that could cause infinite loops. Closes
8226 o Minor features (systemd):
8227 - Various improvements and modernizations in systemd hardening
8228 support. Closes ticket 13805. Patch from Craig Andrews.
8229 - Where supported, when running with systemd, report successful
8230 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
8231 - When running with systemd, support systemd watchdog messages. Part
8232 of ticket 11016. Patch by Michael Scherer.
8234 o Minor features (testing networks):
8235 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
8236 the "Exit" flag regardless of their uptime, bandwidth, or exit
8237 policy. TestingTorNetwork must be set for this option to have any
8238 effect. Previously, authorities would take up to 35 minutes to
8239 give nodes the Exit flag in a test network. Partially implements
8241 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
8242 and the default on a testing network to 2 minutes. Drop the
8243 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
8244 keep the default on a testing network at 30 seconds. This reduces
8245 HS bootstrap time to around 25 seconds. Also, change the default
8246 time in test-network.sh to match. Closes ticket 13401. Patch
8248 - Create TestingDirAuthVoteHSDir to correspond to
8249 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
8250 HSDir flag for the listed relays regardless of uptime or ORPort
8251 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
8252 Partial implementation for ticket 14067. Patch by "teor".
8254 o Minor features (tor2web mode):
8255 - Introduce the config option Tor2webRendezvousPoints, which allows
8256 clients in Tor2webMode to select a specific Rendezvous Point to be
8257 used in HS circuits. This might allow better performance for
8258 Tor2Web nodes. Implements ticket 12844.
8260 o Minor features (transparent proxy):
8261 - Update the transparent proxy option checks to allow for both ipfw
8262 and pf on OS X. Closes ticket 14002.
8263 - Use the correct option when using IPv6 with transparent proxy
8264 support on Linux. Resolves 13808. Patch by Francisco Blas
8267 o Minor features (validation):
8268 - Check all date/time values passed to tor_timegm and
8269 parse_rfc1123_time for validity, taking leap years into account.
8270 Improves HTTP header validation. Implemented with bug 13476.
8271 - In correct_tm(), limit the range of values returned by system
8272 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
8273 This means we don't have to deal with negative or too large dates,
8274 even if a clock is wrong. Otherwise we might fail to read a file
8275 written by us which includes such a date. Fixes bug 13476.
8276 - Stop allowing invalid address patterns like "*/24" that contain
8277 both a wildcard address and a bit prefix length. This affects all
8278 our address-range parsing code. Fixes bug 7484; bugfix
8281 o Minor bugfixes (bridge clients):
8282 - When configured to use a bridge without an identity digest (not
8283 recommended), avoid launching an extra channel to it when
8284 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
8286 o Minor bugfixes (bridges):
8287 - When DisableNetwork is set, do not launch pluggable transport
8288 plugins, and if any are running, terminate them. Fixes bug 13213;
8289 bugfix on 0.2.3.6-alpha.
8291 o Minor bugfixes (C correctness):
8292 - Fix several instances of possible integer overflow/underflow/NaN.
8293 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
8295 - In circuit_build_times_calculate_timeout() in circuitstats.c,
8296 avoid dividing by zero in the pareto calculations. This traps
8297 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
8299 - Fix an integer overflow in format_time_interval(). Fixes bug
8300 13393; bugfix on 0.2.0.10-alpha.
8301 - Set the correct day of year value when the system's localtime(_r)
8302 or gmtime(_r) functions fail to set struct tm. Not externally
8303 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
8304 - Avoid unlikely signed integer overflow in tor_timegm on systems
8305 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
8307 o Minor bugfixes (certificate handling):
8308 - If an authority operator accidentally makes a signing certificate
8309 with a future publication time, do not discard its real signing
8310 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
8311 - Remove any old authority certificates that have been superseded
8312 for at least two days. Previously, we would keep superseded
8313 certificates until they expired, if they were published close in
8314 time to the certificate that superseded them. Fixes bug 11454;
8315 bugfix on 0.2.1.8-alpha.
8317 o Minor bugfixes (client):
8318 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
8319 BadExit flag are not considered worthy candidates. Fixes bug
8320 13066; bugfix on 0.1.2.3-alpha.
8321 - Use the consensus schedule for downloading consensuses, and not
8322 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
8323 - Handle unsupported or malformed SOCKS5 requests properly by
8324 responding with the appropriate error message before closing the
8325 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
8327 o Minor bugfixes (client, automapping):
8328 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
8329 no value follows the option. Fixes bug 14142; bugfix on
8330 0.2.4.7-alpha. Patch by "teor".
8331 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
8332 14195; bugfix on 0.1.0.1-rc.
8333 - Prevent changes to other options from removing the wildcard value
8334 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
8336 - Allow MapAddress and AutomapHostsOnResolve to work together when
8337 an address is mapped into another address type (like .onion) that
8338 must be automapped at resolve time. Fixes bug 7555; bugfix
8341 o Minor bugfixes (client, bridges):
8342 - When we are using bridges and we had a network connectivity
8343 problem, only retry connecting to our currently configured
8344 bridges, not all bridges we know about and remember using. Fixes
8345 bug 14216; bugfix on 0.2.2.17-alpha.
8347 o Minor bugfixes (client, DNS):
8348 - Report the correct cached DNS expiration times on SOCKS port or in
8349 DNS replies. Previously, we would report everything as "never
8350 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
8351 - Avoid a small memory leak when we find a cached answer for a
8352 reverse DNS lookup in a client-side DNS cache. (Remember, client-
8353 side DNS caching is off by default, and is not recommended.) Fixes
8354 bug 14259; bugfix on 0.2.0.1-alpha.
8356 o Minor bugfixes (client, IPv6):
8357 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
8358 flag is not set; and not because the NoIPv4Traffic flag was set.
8359 Previously we'd looked at the NoIPv4Traffic flag for both types of
8360 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
8362 o Minor bugfixes (client, microdescriptors):
8363 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
8364 computing which microdescriptors to download. This keeps us from
8365 erroneous download behavior if two microdescriptor digests ever
8366 have the same first 160 bits. Fixes part of bug 13399; bugfix
8368 - Reset a router's status if its microdescriptor digest changes,
8369 even if the first 160 bits remain the same. Fixes part of bug
8370 13399; bugfix on 0.2.3.1-alpha.
8372 o Minor bugfixes (client, torrc):
8373 - Stop modifying the value of our DirReqStatistics torrc option just
8374 because we're not a bridge or relay. This bug was causing Tor
8375 Browser users to write "DirReqStatistics 0" in their torrc files
8376 as if they had chosen to change the config. Fixes bug 4244; bugfix
8378 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
8379 that our options have changed every time we SIGHUP. Fixes bug
8380 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
8382 o Minor bugfixes (compilation):
8383 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
8385 - Silence clang warnings under --enable-expensive-hardening,
8386 including implicit truncation of 64 bit values to 32 bit, const
8387 char assignment to self, tautological compare, and additional
8388 parentheses around equality tests. Fixes bug 13577; bugfix
8390 - Fix a clang warning about checking whether an address in the
8391 middle of a structure is NULL. Fixes bug 14001; bugfix
8393 - The address of an array in the middle of a structure will always
8394 be non-NULL. clang recognises this and complains. Disable the
8395 tautologous and redundant check to silence this warning. Fixes bug
8396 14001; bugfix on 0.2.1.2-alpha.
8397 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
8398 Addresses ticket 14188.
8399 - Build without warnings with the stock OpenSSL srtp.h header, which
8400 has a duplicate declaration of SSL_get_selected_srtp_profile().
8401 Fixes bug 14220; this is OpenSSL's bug, not ours.
8402 - Do not compile any code related to Tor2Web mode when Tor2Web mode
8403 is not enabled at compile time. Previously, this code was included
8404 in a disabled state. See discussion on ticket 12844.
8405 - Allow our configure script to build correctly with autoconf 2.62
8406 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
8407 - Improve the error message from ./configure to make it clear that
8408 when asciidoc has not been found, the user will have to either add
8409 --disable-asciidoc argument or install asciidoc. Resolves
8412 o Minor bugfixes (controller):
8413 - Report "down" in response to the "GETINFO entry-guards" command
8414 when relays are down with an unreachable_since value. Previously,
8415 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
8416 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
8417 14116; bugfix on 0.2.2.9-alpha.
8419 o Minor bugfixes (controller):
8420 - Return an error when the second or later arguments of the
8421 "setevents" controller command are invalid events. Previously we
8422 would return success while silently skipping invalid events. Fixes
8423 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
8425 o Minor bugfixes (directory authority):
8426 - Allow directory authorities to fetch more data from one another if
8427 they find themselves missing lots of votes. Previously, they had
8428 been bumping against the 10 MB queued data limit. Fixes bug 14261;
8429 bugfix on 0.1.2.5-alpha.
8430 - Do not attempt to download extrainfo documents which we will be
8431 unable to validate with a matching server descriptor. Fixes bug
8432 13762; bugfix on 0.2.0.1-alpha.
8433 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
8434 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
8435 - Enlarge the buffer to read bwauth generated files to avoid an
8436 issue when parsing the file in dirserv_read_measured_bandwidths().
8437 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
8438 - When running as a v3 directory authority, advertise that you serve
8439 extra-info documents so that clients who want them can find them
8440 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8442 o Minor bugfixes (directory system):
8443 - Always believe that v3 directory authorities serve extra-info
8444 documents, whether they advertise "caches-extra-info" or not.
8445 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
8446 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
8447 Previously, directories offering BRIDGE_DIRINFO and some other
8448 flag (i.e. microdescriptors or extrainfo) would be ignored when
8449 looking for bridges. Partially fixes bug 13163; bugfix
8452 o Minor bugfixes (file handling):
8453 - Stop failing when key files are zero-length. Instead, generate new
8454 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
8455 on all versions of Tor. Patch by "teor".
8456 - Stop generating a fresh .old RSA onion key file when the .old file
8457 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
8458 - Avoid overwriting .old key files with empty key files.
8459 - Skip loading zero-length extrainfo store, router store, stats,
8460 state, and key files.
8461 - Avoid crashing when trying to reload a torrc specified as a
8462 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
8465 o Minor bugfixes (hidden services):
8466 - Close the introduction circuit when we have no more usable intro
8467 points, instead of waiting for it to time out. This also ensures
8468 that no follow-up HS descriptor fetch is triggered when the
8469 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
8470 - When fetching a hidden service descriptor for a down service that
8471 was recently up, do not keep refetching until we try the same
8472 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
8473 - Correctly send a controller event when we find that a rendezvous
8474 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
8475 - Pre-check directory permissions for new hidden-services to avoid
8476 at least one case of "Bug: Acting on config options left us in a
8477 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
8478 - When fetching hidden service descriptors, we now check not only
8479 for whether we got the hidden service we had in mind, but also
8480 whether we got the particular descriptors we wanted. This prevents
8481 a class of inefficient but annoying DoS attacks by hidden service
8482 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
8485 o Minor bugfixes (Linux seccomp2 sandbox):
8486 - Make transparent proxy support work along with the seccomp2
8487 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
8488 by Francisco Blas Izquierdo Riera.
8489 - Fix a memory leak in tor-resolve when running with the sandbox
8490 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
8491 - Allow glibc fatal errors to be sent to stderr before Tor exits.
8492 Previously, glibc would try to write them to /dev/tty, and the
8493 sandbox would trap the call and make Tor exit prematurely. Fixes
8494 bug 14759; bugfix on 0.2.5.1-alpha.
8496 o Minor bugfixes (logging):
8497 - Avoid crashing when there are more log domains than entries in
8498 domain_list. Bugfix on 0.2.3.1-alpha.
8499 - Downgrade warnings about RSA signature failures to info log level.
8500 Emit a warning when an extra info document is found incompatible
8501 with a corresponding router descriptor. Fixes bug 9812; bugfix
8503 - Make connection_ap_handshake_attach_circuit() log the circuit ID
8504 correctly. Fixes bug 13701; bugfix on 0.0.6.
8506 o Minor bugfixes (networking):
8507 - Check for orconns and use connection_or_close_for_error() rather
8508 than connection_mark_for_close() directly in the getsockopt()
8509 failure case of connection_handle_write_impl(). Fixes bug 11302;
8510 bugfix on 0.2.4.4-alpha.
8512 o Minor bugfixes (parsing):
8513 - Stop accepting milliseconds (or other junk) at the end of
8514 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
8515 - Support two-number and three-number version numbers correctly, in
8516 case we change the Tor versioning system in the future. Fixes bug
8517 13661; bugfix on 0.0.8pre1.
8519 o Minor bugfixes (portability):
8520 - Fix the ioctl()-based network interface lookup code so that it
8521 will work on systems that have variable-length struct ifreq, for
8523 - Use the correct datatype in the SipHash-2-4 function to prevent
8524 compilers from assuming any sort of alignment. Fixes bug 15436;
8525 bugfix on 0.2.5.3-alpha.
8527 o Minor bugfixes (preventative security, C safety):
8528 - When reading a hexadecimal, base-32, or base-64 encoded value from
8529 a string, always overwrite the whole output buffer. This prevents
8530 some bugs where we would look at (but fortunately, not reveal)
8531 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
8533 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
8534 just the part that's used. This makes it harder for data leak bugs
8535 to occur in the event of other programming failures. Resolves
8538 o Minor bugfixes (relay):
8539 - When generating our family list, remove spaces from around the
8540 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
8541 - If our previous bandwidth estimate was 0 bytes, allow publishing a
8542 new relay descriptor immediately. Fixes bug 13000; bugfix
8545 o Minor bugfixes (shutdown):
8546 - When shutting down, always call event_del() on lingering read or
8547 write events before freeing them. Otherwise, we risk double-frees
8548 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
8551 o Minor bugfixes (small memory leaks):
8552 - Avoid leaking memory when using IPv6 virtual address mappings.
8553 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
8556 o Minor bugfixes (statistics):
8557 - Increase period over which bandwidth observations are aggregated
8558 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
8560 o Minor bugfixes (systemd support):
8561 - Run correctly under systemd with the RunAsDaemon option set. Fixes
8562 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
8563 - Inform the systemd supervisor about more changes in the Tor
8564 process status. Implements part of ticket 14141. Patch from
8567 o Minor bugfixes (testing networks):
8568 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
8569 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
8570 - Stop using the default authorities in networks which provide both
8571 AlternateDirAuthority and AlternateBridgeAuthority. Partially
8572 fixes bug 13163; bugfix on 0.2.0.13-alpha.
8574 o Minor bugfixes (testing networks, fast startup):
8575 - Allow Tor to build circuits using a consensus with no exits. If
8576 the consensus has no exits (typical of a bootstrapping test
8577 network), allow Tor to build circuits once enough descriptors have
8578 been downloaded. This assists in bootstrapping a testing Tor
8579 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
8581 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
8582 header to directory servers. This allows us to obtain consensuses
8583 promptly when the consensus interval is very short. This assists
8584 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
8585 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
8586 - Stop assuming that private addresses are local when checking
8587 reachability in a TestingTorNetwork. Instead, when testing, assume
8588 all OR connections are remote. (This is necessary due to many test
8589 scenarios running all relays on localhost.) This assists in
8590 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
8591 0.1.0.1-rc. Patch by "teor".
8592 - Avoid building exit circuits from a consensus with no exits. Now
8593 thanks to our fix for 13718, we accept a no-exit network as not
8594 wholly lost, but we need to remember not to try to build exit
8595 circuits on it. Closes ticket 13814; patch by "teor".
8596 - Stop requiring exits to have non-zero bandwithcapacity in a
8597 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
8598 ignore exit bandwidthcapacity. This assists in bootstrapping a
8599 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
8600 on 0.2.0.3-alpha. Patch by "teor".
8601 - Add "internal" to some bootstrap statuses when no exits are
8602 available. If the consensus does not contain Exits, Tor will only
8603 build internal circuits. In this case, relevant statuses will
8604 contain the word "internal" as indicated in the Tor control-
8605 spec.txt. When bootstrap completes, Tor will be ready to build
8606 internal circuits. If a future consensus contains Exits, exit
8607 circuits may become available. Fixes part of bug 13718; bugfix on
8608 0.2.4.10-alpha. Patch by "teor".
8609 - Decrease minimum consensus interval to 10 seconds when
8610 TestingTorNetwork is set, or 5 seconds for the first consensus.
8611 Fix assumptions throughout the code that assume larger intervals.
8612 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
8614 - Avoid excluding guards from path building in minimal test
8615 networks, when we're in a test network and excluding guards would
8616 exclude all relays. This typically occurs in incredibly small tor
8617 networks, and those using "TestingAuthVoteGuard *". Fixes part of
8618 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
8620 o Minor bugfixes (testing):
8621 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
8622 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
8623 - Stop spawn test failures due to a race condition between the
8624 SIGCHLD handler updating the process status, and the test reading
8625 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
8626 - Avoid passing an extra backslash when creating a temporary
8627 directory for running the unit tests on Windows. Fixes bug 12392;
8628 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
8630 o Minor bugfixes (TLS):
8631 - Check more thoroughly throughout the TLS code for possible
8632 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
8634 o Minor bugfixes (transparent proxy):
8635 - Use getsockname, not getsockopt, to retrieve the address for a
8636 TPROXY-redirected connection. Fixes bug 13796; bugfix
8639 o Minor bugfixes (windows):
8640 - Remove code to special-case handling of NTE_BAD_KEYSET when
8641 acquiring windows CryptoAPI context. This error can't actually
8642 occur for the parameters we're providing. Fixes bug 10816; bugfix
8645 o Minor bugfixes (zlib):
8646 - Avoid truncating a zlib stream when trying to finalize it with an
8647 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
8649 o Code simplification and refactoring:
8650 - Change the entry_is_live() function to take named bitfield
8651 elements instead of an unnamed list of booleans. Closes
8653 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
8654 Resolves ticket 12205.
8655 - Use calloc and reallocarray functions instead of multiply-
8656 then-malloc. This makes it less likely for us to fall victim to an
8657 integer overflow attack when allocating. Resolves ticket 12855.
8658 - Use the standard macro name SIZE_MAX, instead of our
8660 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
8661 functions which take them as arguments. Replace 0 with NO_DIRINFO
8662 in a function call for clarity. Seeks to prevent future issues
8664 - Avoid 4 null pointer errors under clang static analysis by using
8665 tor_assert() to prove that the pointers aren't null. Fixes
8667 - Rework the API of policies_parse_exit_policy() to use a bitmask to
8668 represent parsing options, instead of a confusing mess of
8669 booleans. Resolves ticket 8197.
8670 - Introduce a helper function to parse ExitPolicy in
8671 or_options_t structure.
8672 - Move fields related to isolating and configuring client ports into
8673 a shared structure. Previously, they were duplicated across
8674 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
8675 to copy them correctly had been the cause of at least one bug in
8676 the past. Closes ticket 8546.
8677 - Refactor the get_interface_addresses_raw() doom-function into
8678 multiple smaller and simpler subfunctions. Cover the resulting
8679 subfunctions with unit-tests. Fixes a significant portion of
8681 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
8682 only for version <= 0.2.2.24 which is now deprecated. Closes
8684 - Remove a test for a long-defunct broken version-one
8686 - Refactor main loop to extract the 'loop' part. This makes it
8687 easier to run Tor under Shadow. Closes ticket 15176.
8688 - Stop using can_complete_circuits as a global variable; access it
8689 with a function instead.
8690 - Avoid using operators directly as macro arguments: this lets us
8691 apply coccinelle transformations to our codebase more directly.
8692 Closes ticket 13172.
8693 - Combine the functions used to parse ClientTransportPlugin and
8694 ServerTransportPlugin into a single function. Closes ticket 6456.
8695 - Add inline functions and convenience macros for inspecting channel
8696 state. Refactor the code to use convenience macros instead of
8697 checking channel state directly. Fixes issue 7356.
8698 - Document all members of was_router_added_t and rename
8699 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
8700 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
8701 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
8702 constant instead of hardcoded value. Fixes issue 13840.
8703 - Refactor our generic strmap and digestmap types into a single
8704 implementation, so that we can add a new digest256map
8708 - Add a doc/TUNING document with tips for handling large numbers of
8709 TCP connections when running busy Tor relay. Update the warning
8710 message to point to this file when running out of sockets
8711 operating system is allowing to use simultaneously. Resolves
8713 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
8714 for writing the OpenBSD-specific tips. Resolves ticket 13702.
8715 - Make the tor-resolve documentation match its help string and its
8716 options. Resolves part of ticket 14325.
8717 - Log a more useful error message from tor-resolve when failing to
8718 look up a hidden service address. Resolves part of ticket 14325.
8719 - Document the bridge-authority-only 'networkstatus-bridges' file.
8720 Closes ticket 13713; patch from "tom".
8721 - Fix typo in PredictedPortsRelevanceTime option description in
8722 manpage. Resolves issue 13707.
8723 - Stop suggesting that users specify relays by nickname: it isn't a
8724 good idea. Also, properly cross-reference how to specify relays in
8725 all parts of manual documenting options that take a list of
8726 relays. Closes ticket 13381.
8727 - Clarify the HiddenServiceDir option description in manpage to make
8728 it clear that relative paths are taken with respect to the current
8729 working directory. Also clarify that this behavior is not
8730 guaranteed to remain indefinitely. Fixes issue 13913.
8732 o Distribution (systemd):
8733 - systemd unit file: only allow tor to write to /var/lib/tor and
8734 /var/log/tor. The rest of the filesystem is accessible for reading
8735 only. Patch by intrigeri; resolves ticket 12751.
8736 - systemd unit file: ensure that the process and all its children
8737 can never gain new privileges. Patch by intrigeri; resolves
8739 - systemd unit file: set up /var/run/tor as writable for the Tor
8740 service. Patch by intrigeri; resolves ticket 13196.
8742 o Downgraded warnings:
8743 - Don't warn when we've attempted to contact a relay using the wrong
8744 ntor onion key. Closes ticket 9635.
8747 - Remove some lingering dead code that once supported mempools.
8748 Mempools were disabled by default in 0.2.5, and removed entirely
8749 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
8752 o Removed features (directory authorities):
8753 - Remove code that prevented authorities from listing Tor relays
8754 affected by CVE-2011-2769 as guards. These relays are already
8755 rejected altogether due to the minimum version requirement of
8756 0.2.3.16-alpha. Closes ticket 13152.
8757 - The "AuthDirRejectUnlisted" option no longer has any effect, as
8758 the fingerprints file (approved-routers) has been deprecated.
8759 - Directory authorities do not support being Naming dirauths anymore.
8760 The "NamingAuthoritativeDir" config option is now obsolete.
8761 - Directory authorities do not support giving out the BadDirectory
8763 - Directory authorities no longer advertise or support consensus
8764 methods 1 through 12 inclusive. These consensus methods were
8765 obsolete and/or insecure: maintaining the ability to support them
8766 served no good purpose. Implements part of proposal 215; closes
8770 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
8771 longer silently accepted as an alias for "ExitNodes".
8772 - The --enable-mempool and --enable-buf-freelists options, which
8773 were originally created to work around bad malloc implementations,
8774 no longer exist. They were off-by-default in 0.2.5. Closes
8776 - We no longer remind the user about configuration options that have
8777 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
8778 - Remove our old, non-weighted bandwidth-based node selection code.
8779 Previously, we used it as a fallback when we couldn't perform
8780 weighted bandwidth-based node selection. But that would only
8781 happen in the cases where we had no consensus, or when we had a
8782 consensus generated by buggy or ancient directory authorities. In
8783 either case, it's better to use the more modern, better maintained
8784 algorithm, with reasonable defaults for the weights. Closes
8786 - Remove the --disable-curve25519 configure option. Relays and
8787 clients now are required to support curve25519 and the
8789 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
8790 used to be deprecated synonyms for "StrictNodes", are now marked
8791 obsolete. Resolves ticket 12226.
8792 - Clients don't understand the BadDirectory flag in the consensus
8793 anymore, and ignore it.
8795 o Removed platform support:
8796 - We no longer include special code to build on Windows CE; as far
8797 as we know, nobody has used Tor on Windows CE in a very long time.
8798 Closes ticket 11446.
8800 o Testing (test-network.sh):
8801 - Stop using "echo -n", as some shells' built-in echo doesn't
8802 support "-n". Instead, use "/bin/echo -n". Partially fixes
8804 - Stop an apparent test-network hang when used with make -j2. Fixes
8806 - Add a --delay option to test-network.sh, which configures the
8807 delay before the chutney network tests for data transmission.
8808 Partially implements ticket 13161.
8811 - Test that tor does not fail when key files are zero-length. Check
8812 that tor generates new keys, and overwrites the empty key files.
8813 - Test that tor generates new keys when keys are missing
8814 (existing behavior).
8815 - Test that tor does not overwrite key files that already contain
8816 data (existing behavior). Tests bug 13111. Patch by "teor".
8817 - New "make test-stem" target to run stem integration tests.
8818 Requires that the "STEM_SOURCE_DIR" environment variable be set.
8819 Closes ticket 14107.
8820 - Make the test_cmdline_args.py script work correctly on Windows.
8821 Patch from Gisle Vanem.
8822 - Move the slower unit tests into a new "./src/test/test-slow"
8823 binary that can be run independently of the other tests. Closes
8825 - New tests for many parts of channel, relay, and circuitmux
8826 functionality. Code by Andrea; part of 9262.
8827 - New tests for parse_transport_line(). Part of ticket 6456.
8828 - In the unit tests, use chgrp() to change the group of the unit
8829 test temporary directory to the current user, so that the sticky
8830 bit doesn't interfere with tests that check directory groups.
8832 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
8834 - Refactor the function that chooses guard nodes so that it can more
8835 easily be tested; write some tests for it.
8836 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
8837 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
8838 - Create unit tests for format_time_interval(). With bug 13393.
8839 - Add unit tests for tor_timegm signed overflow, tor_timegm and
8840 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
8841 tests (visible) fixes in bug 13476.
8842 - Add a "coverage-html" make target to generate HTML-visualized
8843 coverage results when building with --enable-coverage. (Requires
8844 lcov.) Patch from Kevin Murray.
8845 - Enable the backtrace handler (where supported) when running the
8847 - Revise all unit tests that used the legacy test_* macros to
8848 instead use the recommended tt_* macros. This patch was generated
8849 with coccinelle, to avoid manual errors. Closes ticket 13119.
8851 Changes in version 0.2.5.11 - 2015-03-17
8852 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
8854 It backports several bugfixes from the 0.2.6 branch, including a
8855 couple of medium-level security fixes for relays and exit nodes.
8856 It also updates the list of directory authorities.
8858 o Directory authority changes:
8859 - Remove turtles as a directory authority.
8860 - Add longclaw as a new (v3) directory authority. This implements
8861 ticket 13296. This keeps the directory authority count at 9.
8862 - The directory authority Faravahar has a new IP address. This
8863 closes ticket 14487.
8865 o Major bugfixes (crash, OSX, security):
8866 - Fix a remote denial-of-service opportunity caused by a bug in
8867 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
8870 o Major bugfixes (relay, stability, possible security):
8871 - Fix a bug that could lead to a relay crashing with an assertion
8872 failure if a buffer of exactly the wrong layout was passed to
8873 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8874 0.2.0.10-alpha. Patch from 'cypherpunks'.
8875 - Do not assert if the 'data' pointer on a buffer is advanced to the
8876 very end of the buffer; log a BUG message instead. Only assert if
8877 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8879 o Major bugfixes (exit node stability):
8880 - Fix an assertion failure that could occur under high DNS load.
8881 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8882 diagnosed and fixed by "cypherpunks".
8884 o Major bugfixes (Linux seccomp2 sandbox):
8885 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
8886 crash during attempts to call wait4. Fixes bug 15088; bugfix on
8887 0.2.5.1-alpha. Patch from "sanic".
8889 o Minor features (controller):
8890 - New "GETINFO bw-event-cache" to get information about recent
8891 bandwidth events. Closes ticket 14128. Useful for controllers to
8892 get recent bandwidth history after the fix for ticket 13988.
8894 o Minor features (geoip):
8895 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8896 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8899 o Minor bugfixes (client, automapping):
8900 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
8901 no value follows the option. Fixes bug 14142; bugfix on
8902 0.2.4.7-alpha. Patch by "teor".
8903 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
8904 14195; bugfix on 0.1.0.1-rc.
8906 o Minor bugfixes (compilation):
8907 - Build without warnings with the stock OpenSSL srtp.h header, which
8908 has a duplicate declaration of SSL_get_selected_srtp_profile().
8909 Fixes bug 14220; this is OpenSSL's bug, not ours.
8911 o Minor bugfixes (directory authority):
8912 - Allow directory authorities to fetch more data from one another if
8913 they find themselves missing lots of votes. Previously, they had
8914 been bumping against the 10 MB queued data limit. Fixes bug 14261;
8915 bugfix on 0.1.2.5-alpha.
8916 - Enlarge the buffer to read bwauth generated files to avoid an
8917 issue when parsing the file in dirserv_read_measured_bandwidths().
8918 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
8920 o Minor bugfixes (statistics):
8921 - Increase period over which bandwidth observations are aggregated
8922 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
8924 o Minor bugfixes (preventative security, C safety):
8925 - When reading a hexadecimal, base-32, or base-64 encoded value from
8926 a string, always overwrite the whole output buffer. This prevents
8927 some bugs where we would look at (but fortunately, not reveal)
8928 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
8932 Changes in version 0.2.4.26 - 2015-03-17
8933 Tor 0.2.4.26 includes an updated list of directory authorities. It
8934 also backports a couple of stability and security bugfixes from 0.2.5
8937 o Directory authority changes:
8938 - Remove turtles as a directory authority.
8939 - Add longclaw as a new (v3) directory authority. This implements
8940 ticket 13296. This keeps the directory authority count at 9.
8941 - The directory authority Faravahar has a new IP address. This
8942 closes ticket 14487.
8944 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
8945 - Fix an assertion failure that could occur under high DNS load.
8946 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
8947 diagnosed and fixed by "cypherpunks".
8949 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
8950 - Fix a bug that could lead to a relay crashing with an assertion
8951 failure if a buffer of exactly the wrong layout was passed to
8952 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
8953 0.2.0.10-alpha. Patch from 'cypherpunks'.
8954 - Do not assert if the 'data' pointer on a buffer is advanced to the
8955 very end of the buffer; log a BUG message instead. Only assert if
8956 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
8958 o Minor features (geoip):
8959 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
8960 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
8963 Changes in version 0.2.5.10 - 2014-10-24
8964 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
8966 It adds several new security features, including improved
8967 denial-of-service resistance for relays, new compiler hardening
8968 options, and a system-call sandbox for hardened installations on Linux
8969 (requires seccomp2). The controller protocol has several new features,
8970 resolving IPv6 addresses should work better than before, and relays
8971 should be a little more CPU-efficient. We've added support for more
8972 OpenBSD and FreeBSD transparent proxy types. We've improved the build
8973 system and testing infrastructure to allow unit testing of more parts
8974 of the Tor codebase. Finally, we've addressed several nagging pluggable
8975 transport usability issues, and included numerous other small bugfixes
8976 and features mentioned below.
8978 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
8979 have accumulated many known flaws; everyone should upgrade.
8981 o Major features (security):
8982 - The ntor handshake is now on-by-default, no matter what the
8983 directory authorities recommend. Implements ticket 8561.
8984 - Make the "tor-gencert" tool used by directory authority operators
8985 create 2048-bit signing keys by default (rather than 1024-bit, since
8986 1024-bit is uncomfortably small these days). Addresses ticket 10324.
8987 - Warn about attempts to run hidden services and relays in the same
8988 process: that's probably not a good idea. Closes ticket 12908.
8989 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
8990 today support TLS 1.0 or later, so we can safely turn off support
8991 for this old (and insecure) protocol. Fixes bug 13426.
8993 o Major features (relay security, DoS-resistance):
8994 - When deciding whether we have run out of memory and we need to
8995 close circuits, also consider memory allocated in buffers for
8996 streams attached to each circuit.
8998 This change, which extends an anti-DoS feature introduced in
8999 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
9000 better resist more memory-based DoS attacks than before. Since the
9001 MaxMemInCellQueues option now applies to all queues, it is renamed
9002 to MaxMemInQueues. This feature fixes bug 10169.
9003 - Avoid hash-flooding denial-of-service attacks by using the secure
9004 SipHash-2-4 hash function for our hashtables. Without this
9005 feature, an attacker could degrade performance of a targeted
9006 client or server by flooding their data structures with a large
9007 number of entries to be stored at the same hash table position,
9008 thereby slowing down the Tor instance. With this feature, hash
9009 table positions are derived from a randomized cryptographic key,
9010 and an attacker cannot predict which entries will collide. Closes
9012 - If you don't specify MaxMemInQueues yourself, Tor now tries to
9013 pick a good value based on your total system memory. Previously,
9014 the default was always 8 GB. You can still override the default by
9015 setting MaxMemInQueues yourself. Resolves ticket 11396.
9017 o Major features (bridges and pluggable transports):
9018 - Add support for passing arguments to managed pluggable transport
9019 proxies. Implements ticket 3594.
9020 - Bridges now track GeoIP information and the number of their users
9021 even when pluggable transports are in use, and report usage
9022 statistics in their extra-info descriptors. Resolves tickets 4773
9024 - Don't launch pluggable transport proxies if we don't have any
9025 bridges configured that would use them. Now we can list many
9026 pluggable transports, and Tor will dynamically start one when it
9027 hears a bridge address that needs it. Resolves ticket 5018.
9028 - The bridge directory authority now assigns status flags (Stable,
9029 Guard, etc) to bridges based on thresholds calculated over all
9030 Running bridges. Now bridgedb can finally make use of its features
9031 to e.g. include at least one Stable bridge in its answers. Fixes
9034 o Major features (controller):
9035 - Extend ORCONN controller event to include an "ID" parameter,
9036 and add four new controller event types CONN_BW, CIRC_BW,
9037 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
9038 The new events are emitted in private Tor networks only, with the
9039 goal of being able to better track performance and load during
9040 full-network simulations. Implements proposal 218 and ticket 7359.
9042 o Major features (relay performance):
9043 - Speed up server-side lookups of rendezvous and introduction point
9044 circuits by using hashtables instead of linear searches. These
9045 functions previously accounted between 3 and 7% of CPU usage on
9046 some busy relays. Resolves ticket 9841.
9047 - Avoid wasting CPU when extending a circuit over a channel that is
9048 nearly out of circuit IDs. Previously, we would do a linear scan
9049 over possible circuit IDs before finding one or deciding that we
9050 had exhausted our possibilities. Now, we try at most 64 random
9051 circuit IDs before deciding that we probably won't succeed. Fixes
9052 a possible root cause of ticket 11553.
9054 o Major features (seccomp2 sandbox, Linux only):
9055 - Use the seccomp2 syscall filtering facility on Linux to limit
9056 which system calls Tor can invoke. This is an experimental,
9057 Linux-only feature to provide defense-in-depth against unknown
9058 attacks. To try turning it on, set "Sandbox 1" in your torrc
9059 file. Please be ready to report bugs. We hope to add support
9060 for better sandboxing in the future, including more fine-grained
9061 filters, better division of responsibility, and support for more
9062 platforms. This work has been done by Cristian-Matei Toader for
9063 Google Summer of Code. Resolves tickets 11351 and 11465.
9065 o Major features (testing networks):
9066 - Make testing Tor networks bootstrap better: lower directory fetch
9067 retry schedules and maximum interval without directory requests,
9068 and raise maximum download tries. Implements ticket 6752.
9069 - Add make target 'test-network' to run tests on a Chutney network.
9070 Implements ticket 8530.
9072 o Major features (other):
9073 - On some platforms (currently: recent OSX versions, glibc-based
9074 platforms that support the ELF format, and a few other
9075 Unix-like operating systems), Tor can now dump stack traces
9076 when a crash occurs or an assertion fails. By default, traces
9077 are dumped to stderr (if possible) and to any logs that are
9078 reporting errors. Implements ticket 9299.
9080 o Deprecated versions:
9081 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
9082 attention for some while.
9084 o Major bugfixes (security, directory authorities):
9085 - Directory authorities now include a digest of each relay's
9086 identity key as a part of its microdescriptor.
9088 This is a workaround for bug 11743 (reported by "cypherpunks"),
9089 where Tor clients do not support receiving multiple
9090 microdescriptors with the same SHA256 digest in the same
9091 consensus. When clients receive a consensus like this, they only
9092 use one of the relays. Without this fix, a hostile relay could
9093 selectively disable some client use of target relays by
9094 constructing a router descriptor with a different identity and the
9095 same microdescriptor parameters and getting the authorities to
9096 list it in a microdescriptor consensus. This fix prevents an
9097 attacker from causing a microdescriptor collision, because the
9098 router's identity is not forgeable.
9100 o Major bugfixes (openssl bug workaround):
9101 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9102 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
9103 bug 13471. This is a workaround for an OpenSSL bug.
9105 o Major bugfixes (client):
9106 - Perform circuit cleanup operations even when circuit
9107 construction operations are disabled (because the network is
9108 disabled, or because there isn't enough directory information).
9109 Previously, when we were not building predictive circuits, we
9110 were not closing expired circuits either. Fixes bug 8387; bugfix on
9111 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
9112 became more strict about when we have "enough directory information
9115 o Major bugfixes (client, pluggable transports):
9116 - When managing pluggable transports, use OS notification facilities
9117 to learn if they have crashed, and don't attempt to kill any
9118 process that has already exited. Fixes bug 8746; bugfix
9121 o Major bugfixes (relay denial of service):
9122 - Instead of writing destroy cells directly to outgoing connection
9123 buffers, queue them and intersperse them with other outgoing cells.
9124 This can prevent a set of resource starvation conditions where too
9125 many pending destroy cells prevent data cells from actually getting
9126 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
9127 bugfix on 0.2.0.1-alpha.
9129 o Major bugfixes (relay):
9130 - Avoid queuing or sending destroy cells for circuit ID zero when we
9131 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
9132 Found and fixed by "cypherpunks".
9133 - Fix ORPort reachability detection on relays running behind a
9134 proxy, by correctly updating the "local" mark on the controlling
9135 channel when changing the address of an or_connection_t after the
9136 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
9137 - Use a direct dirport connection when uploading non-anonymous
9138 descriptors to the directory authorities. Previously, relays would
9139 incorrectly use tunnel connections under a fairly wide variety of
9140 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
9141 - When a circuit accidentally has the same circuit ID for its
9142 forward and reverse direction, correctly detect the direction of
9143 cells using that circuit. Previously, this bug made roughly one
9144 circuit in a million non-functional. Fixes bug 12195; this is a
9145 bugfix on every version of Tor.
9147 o Minor features (security):
9148 - New --enable-expensive-hardening option to enable security
9149 hardening options that consume nontrivial amounts of CPU and
9150 memory. Right now, this includes AddressSanitizer and UbSan, which
9151 are supported in newer versions of GCC and Clang. Closes ticket
9153 - Authorities now assign the Guard flag to the fastest 25% of the
9154 network (it used to be the fastest 50%). Also raise the consensus
9155 weight that guarantees the Guard flag from 250 to 2000. For the
9156 current network, this results in about 1100 guards, down from 2500.
9157 This step paves the way for moving the number of entry guards
9158 down to 1 (proposal 236) while still providing reasonable expected
9159 performance for most users. Implements ticket 12690.
9161 o Minor features (security, memory management):
9162 - Memory allocation tricks (mempools and buffer freelists) are now
9163 disabled by default. You can turn them back on with
9164 --enable-mempools and --enable-buf-freelists respectively. We're
9165 disabling these features because malloc performance is good enough
9166 on most platforms, and a similar feature in OpenSSL exacerbated
9167 exploitation of the Heartbleed attack. Resolves ticket 11476.
9169 o Minor features (bridge client):
9170 - Report a more useful failure message when we can't connect to a
9171 bridge because we don't have the right pluggable transport
9172 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
9174 o Minor features (bridge):
9175 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
9176 cookie file for the ExtORPort g+r by default.
9178 o Minor features (bridges, pluggable transports):
9179 - Bridges now write the SHA1 digest of their identity key
9180 fingerprint (that is, a hash of a hash of their public key) to
9181 notice-level logs, and to a new hashed-fingerprint file. This
9182 information will help bridge operators look up their bridge in
9183 Globe and similar tools. Resolves ticket 10884.
9184 - Improve the message that Tor displays when running as a bridge
9185 using pluggable transports without an Extended ORPort listener.
9186 Also, log the message in the log file too. Resolves ticket 11043.
9187 - Add threshold cutoffs to the networkstatus document created by
9188 the Bridge Authority. Fixes bug 1117.
9189 - On Windows, spawn background processes using the CREATE_NO_WINDOW
9190 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
9191 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
9192 Vidalia set this option for us.) Implements ticket 10297.
9194 o Minor features (build):
9195 - The configure script has a --disable-seccomp option to turn off
9196 support for libseccomp on systems that have it, in case it (or
9197 Tor's use of it) is broken. Resolves ticket 11628.
9198 - Assume that a user using ./configure --host wants to cross-compile,
9199 and give an error if we cannot find a properly named
9200 tool-chain. Add a --disable-tool-name-check option to proceed
9201 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
9202 - If we run ./configure and the compiler recognizes -fstack-protector
9203 but the linker rejects it, warn the user about a potentially missing
9204 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
9205 - Add support for `--library-versions` flag. Implements ticket 6384.
9206 - Return the "unexpected sendme" warnings to a warn severity, but make
9207 them rate limited, to help diagnose ticket 8093.
9208 - Detect a missing asciidoc, and warn the user about it, during
9209 configure rather than at build time. Fixes issue 6506. Patch from
9212 o Minor features (client):
9213 - Add a new option, PredictedPortsRelevanceTime, to control how long
9214 after having received a request to connect to a given port Tor
9215 will try to keep circuits ready in anticipation of future requests
9216 for that port. Patch from "unixninja92"; implements ticket 9176.
9218 o Minor features (config options and command line):
9219 - Add an --allow-missing-torrc commandline option that tells Tor to
9220 run even if the configuration file specified by -f is not available.
9221 Implements ticket 10060.
9222 - Add support for the TPROXY transparent proxying facility on Linux.
9223 See documentation for the new TransProxyType option for more
9224 details. Implementation by "thomo". Closes ticket 10582.
9226 o Minor features (config options):
9227 - Config (torrc) lines now handle fingerprints which are missing
9228 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
9229 - Support a --dump-config option to print some or all of the
9230 configured options. Mainly useful for debugging the command-line
9231 option parsing code. Helps resolve ticket 4647.
9232 - Raise awareness of safer logging: notify user of potentially
9233 unsafe config options, like logging more verbosely than severity
9234 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
9235 - Add a new configuration option TestingV3AuthVotingStartOffset
9236 that bootstraps a network faster by changing the timing for
9237 consensus votes. Addresses ticket 8532.
9238 - Add a new torrc option "ServerTransportOptions" that allows
9239 bridge operators to pass configuration parameters to their
9240 pluggable transports. Resolves ticket 8929.
9241 - The config (torrc) file now accepts bandwidth and space limits in
9242 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
9243 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
9246 o Minor features (controller):
9247 - Make the entire exit policy available from the control port via
9248 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
9250 - Because of the fix for ticket 11396, the real limit for memory
9251 usage may no longer match the configured MaxMemInQueues value. The
9252 real limit is now exposed via GETINFO limits/max-mem-in-queues.
9253 - Add a new "HS_DESC" controller event that reports activities
9254 related to hidden service descriptors. Resolves ticket 8510.
9255 - New "DROPGUARDS" controller command to forget all current entry
9256 guards. Not recommended for ordinary use, since replacing guards
9257 too frequently makes several attacks easier. Resolves ticket 9934;
9259 - Implement the TRANSPORT_LAUNCHED control port event that
9260 notifies controllers about new launched pluggable
9261 transports. Resolves ticket 5609.
9263 o Minor features (diagnostic):
9264 - When logging a warning because of bug 7164, additionally check the
9265 hash table for consistency (as proposed on ticket 11737). This may
9266 help diagnose bug 7164.
9267 - When we log a heartbeat, log how many one-hop circuits we have
9268 that are at least 30 minutes old, and log status information about
9269 a few of them. This is an attempt to track down bug 8387.
9270 - When encountering an unexpected CR while writing text to a file on
9271 Windows, log the name of the file. Should help diagnosing
9273 - Give more specific warnings when a client notices that an onion
9274 handshake has failed. Fixes ticket 9635.
9275 - Add significant new logging code to attempt to diagnose bug 12184,
9276 where relays seem to run out of available circuit IDs.
9277 - Improve the diagnostic log message for bug 8387 even further to
9278 try to improve our odds of figuring out why one-hop directory
9279 circuits sometimes do not get closed.
9280 - Add more log messages to diagnose bug 7164, which causes
9281 intermittent "microdesc_free() called but md was still referenced"
9282 warnings. We now include more information, to figure out why we
9283 might be cleaning a microdescriptor for being too old if it's
9284 still referenced by a live node_t object.
9285 - Log current accounting state (bytes sent and received + remaining
9286 time for the current accounting period) in the relay's heartbeat
9287 message. Implements ticket 5526; patch from Peter Retzlaff.
9289 o Minor features (geoip):
9290 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9293 o Minor features (interface):
9294 - Generate a warning if any ports are listed in the SocksPolicy,
9295 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
9296 AuthDirBadExit options. (These options only support address
9297 ranges.) Fixes part of ticket 11108.
9299 o Minor features (kernel API usage):
9300 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
9301 sockets in a single system call. Implements ticket 5129.
9303 o Minor features (log messages):
9304 - When ServerTransportPlugin is set on a bridge, Tor can write more
9305 useful statistics about bridge use in its extrainfo descriptors,
9306 but only if the Extended ORPort ("ExtORPort") is set too. Add a
9307 log message to inform the user in this case. Resolves ticket 9651.
9308 - When receiving a new controller connection, log the origin address.
9309 Resolves ticket 9698; patch from "sigpipe".
9310 - When logging OpenSSL engine status at startup, log the status of
9311 more engines. Fixes ticket 10043; patch from Joshua Datko.
9313 o Minor features (log verbosity):
9314 - Demote the message that we give when a flushing connection times
9315 out for too long from NOTICE to INFO. It was usually meaningless.
9316 Resolves ticket 5286.
9317 - Don't log so many notice-level bootstrapping messages at startup
9318 about downloading descriptors. Previously, we'd log a notice
9319 whenever we learned about more routers. Now, we only log a notice
9320 at every 5% of progress. Fixes bug 9963.
9321 - Warn less verbosely when receiving a malformed
9322 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
9324 o Minor features (performance):
9325 - If we're using the pure-C 32-bit curve25519_donna implementation
9326 of curve25519, build it with the -fomit-frame-pointer option to
9327 make it go faster on register-starved hosts. This improves our
9328 handshake performance by about 6% on i386 hosts without nacl.
9331 o Minor features (relay):
9332 - If a circuit timed out for at least 3 minutes, check if we have a
9333 new external IP address, and publish a new descriptor with the new
9334 IP address if it changed. Resolves ticket 2454.
9336 o Minor features (testing):
9337 - If Python is installed, "make check" now runs extra tests beyond
9338 the unit test scripts.
9339 - When bootstrapping a test network, sometimes very few relays get
9340 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
9341 specify a set of relays which should be voted Guard regardless of
9342 their uptime or bandwidth. Addresses ticket 9206.
9344 o Minor features (transparent proxy, *BSD):
9345 - Support FreeBSD's ipfw firewall interface for TransPort ports on
9346 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
9347 10267; patch from "yurivict".
9348 - Support OpenBSD's divert-to rules with the pf firewall for
9349 transparent proxy ports. To enable it, set "TransProxyType
9350 pf-divert". This allows Tor to run a TransPort transparent proxy
9351 port on OpenBSD 4.4 or later without root privileges. See the
9352 pf.conf(5) manual page for information on configuring pf to use
9353 divert-to rules. Closes ticket 10896; patch from Dana Koch.
9355 o Minor bugfixes (bridge client):
9356 - Stop accepting bridge lines containing hostnames. Doing so would
9357 cause clients to perform DNS requests on the hostnames, which was
9358 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
9360 o Minor bugfixes (bridges):
9361 - Avoid potential crashes or bad behavior when launching a
9362 server-side managed proxy with ORPort or ExtORPort temporarily
9363 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
9364 - Fix a bug where the first connection works to a bridge that uses a
9365 pluggable transport with client-side parameters, but we don't send
9366 the client-side parameters on subsequent connections. (We don't
9367 use any pluggable transports with client-side parameters yet,
9368 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
9369 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
9371 o Minor bugfixes (build, auxiliary programs):
9372 - Stop preprocessing the "torify" script with autoconf, since
9373 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
9375 - The tor-fw-helper program now follows the standard convention and
9376 exits with status code "0" on success. Fixes bug 9030; bugfix on
9377 0.2.3.1-alpha. Patch by Arlo Breault.
9378 - Corrected ./configure advice for what openssl dev package you should
9379 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
9381 o Minor bugfixes (client):
9382 - Avoid "Tried to open a socket with DisableNetwork set" warnings
9383 when starting a client with bridges configured and DisableNetwork
9384 set. (Tor launcher starts Tor with DisableNetwork set the first
9385 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
9386 - Improve the log message when we can't connect to a hidden service
9387 because all of the hidden service directory nodes hosting its
9388 descriptor are excluded. Improves on our fix for bug 10722, which
9389 was a bugfix on 0.2.0.10-alpha.
9390 - Raise a control port warning when we fail to connect to all of
9391 our bridges. Previously, we didn't inform the controller, and
9392 the bootstrap process would stall. Fixes bug 11069; bugfix on
9394 - Exit immediately when a process-owning controller exits.
9395 Previously, tor relays would wait for a little while after their
9396 controller exited, as if they had gotten an INT signal -- but this
9397 was problematic, since there was no feedback for the user. To do a
9398 clean shutdown, controllers should send an INT signal and give Tor
9399 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
9400 - Stop attempting to connect to bridges before our pluggable
9401 transports are configured (harmless but resulted in some erroneous
9402 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
9403 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
9404 generating incorrect SOCKS5 responses, and confusing client
9405 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
9407 o Minor bugfixes (client, DNSPort):
9408 - When using DNSPort, try to respond to AAAA requests with AAAA
9409 answers. Previously, we hadn't looked at the request type when
9410 deciding which answer type to prefer. Fixes bug 10468; bugfix on
9412 - When receiving a DNS query for an unsupported record type, reply
9413 with no answer rather than with a NOTIMPL error. This behavior
9414 isn't correct either, but it will break fewer client programs, we
9415 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
9418 o Minor bugfixes (client, logging during bootstrap):
9419 - Only report the first fatal bootstrap error on a given OR
9420 connection. This stops us from telling the controller bogus error
9421 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
9422 - Avoid generating spurious warnings when starting with
9423 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
9426 o Minor bugfixes (closing OR connections):
9427 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
9428 check if it's an or_connection_t and correctly call
9429 connection_or_close_for_error() rather than
9430 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
9432 - When closing all connections on setting DisableNetwork to 1, use
9433 connection_or_close_normally() rather than closing OR connections
9434 out from under the channel layer. Fixes bug 11306; bugfix on
9437 o Minor bugfixes (code correctness):
9438 - Previously we used two temporary files when writing descriptors to
9439 disk; now we only use one. Fixes bug 1376.
9440 - Remove an erroneous (but impossible and thus harmless) pointer
9441 comparison that would have allowed compilers to skip a bounds
9442 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
9443 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
9444 - Fix an always-true assertion in pluggable transports code so it
9445 actually checks what it was trying to check. Fixes bug 10046;
9446 bugfix on 0.2.3.9-alpha. Found by "dcb".
9448 o Minor bugfixes (command line):
9449 - Use a single command-line parser for parsing torrc options on the
9450 command line and for finding special command-line options to avoid
9451 inconsistent behavior for torrc option arguments that have the same
9452 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
9454 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
9455 9573; bugfix on 0.0.9pre5.
9457 o Minor bugfixes (compilation):
9458 - Compile correctly with builds and forks of OpenSSL (such as
9459 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
9460 0.2.1.1-alpha. Patch from "dhill".
9461 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
9462 turned off (that is, without support for v2 link handshakes). Fixes
9463 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
9464 - In routerlist_assert_ok(), don't take the address of a
9465 routerinfo's cache_info member unless that routerinfo is non-NULL.
9466 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
9467 - Fix a large number of false positive warnings from the clang
9468 analyzer static analysis tool. This should make real warnings
9469 easier for clang analyzer to find. Patch from "teor". Closes
9471 - Resolve GCC complaints on OpenBSD about discarding constness in
9472 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
9473 on 0.1.1.23. Patch from Dana Koch.
9474 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
9475 treatment of long and time_t as comparable types. Fixes part of
9476 bug 11633. Patch from Dana Koch.
9477 - When deciding whether to build the 64-bit curve25519
9478 implementation, detect platforms where we can compile 128-bit
9479 arithmetic but cannot link it. Fixes bug 11729; bugfix on
9480 0.2.4.8-alpha. Patch from "conradev".
9481 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
9482 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
9483 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
9485 - Build and run correctly on systems like OpenBSD-current that have
9486 patched OpenSSL to remove get_cipher_by_char and/or its
9487 implementations. Fixes issue 13325.
9489 o Minor bugfixes (controller and command-line):
9490 - If changing a config option via "setconf" fails in a recoverable
9491 way, we used to nonetheless write our new control ports to the
9492 file described by the "ControlPortWriteToFile" option. Now we only
9493 write out that file if we successfully switch to the new config
9494 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
9496 o Minor bugfixes (directory server):
9497 - No longer accept malformed http headers when parsing urls from
9498 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
9499 bugfix on 0.0.6pre1.
9500 - When sending a compressed set of descriptors or microdescriptors,
9501 make sure to finalize the zlib stream. Previously, we would write
9502 all the compressed data, but if the last descriptor we wanted to
9503 send was missing or too old, we would not mark the stream as
9504 finished. This caused problems for decompression tools. Fixes bug
9505 11648; bugfix on 0.1.1.23.
9507 o Minor bugfixes (hidden service):
9508 - Only retry attempts to connect to a chosen rendezvous point 8
9509 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
9511 o Minor bugfixes (interface):
9512 - Reject relative control socket paths and emit a warning. Previously,
9513 single-component control socket paths would be rejected, but Tor
9514 would not log why it could not validate the config. Fixes bug 9258;
9515 bugfix on 0.2.3.16-alpha.
9517 o Minor bugfixes (log messages):
9518 - Fix a bug where clients using bridges would report themselves
9519 as 50% bootstrapped even without a live consensus document.
9520 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
9521 - Suppress a warning where, if there's only one directory authority
9522 in the network, we would complain that votes and signatures cannot
9523 be uploaded to other directory authorities. Fixes bug 10842;
9524 bugfix on 0.2.2.26-beta.
9525 - Report bootstrapping progress correctly when we're downloading
9526 microdescriptors. We had updated our "do we have enough microdescs
9527 to begin building circuits?" logic most recently in 0.2.4.10-alpha
9528 (see bug 5956), but we left the bootstrap status event logic at
9529 "how far through getting 1/4 of them are we?" Fixes bug 9958;
9530 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
9532 o Minor bugfixes (logging):
9533 - Downgrade "Unexpected onionskin length after decryption" warning
9534 to a protocol-warn, since there's nothing relay operators can do
9535 about a client that sends them a malformed create cell. Resolves
9536 bug 12996; bugfix on 0.0.6rc1.
9537 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
9538 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
9539 - When logging information about an EXTEND2 or EXTENDED2 cell, log
9540 their names correctly. Fixes part of bug 12700; bugfix
9542 - When logging information about a relay cell whose command we don't
9543 recognize, log its command as an integer. Fixes part of bug 12700;
9544 bugfix on 0.2.1.10-alpha.
9545 - Escape all strings from the directory connection before logging
9546 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
9547 - Squelch a spurious LD_BUG message "No origin circuit for
9548 successful SOCKS stream" in certain hidden service failure cases;
9550 - Downgrade the severity of the 'unexpected sendme cell from client'
9551 from 'warn' to 'protocol warning'. Closes ticket 8093.
9553 o Minor bugfixes (misc code correctness):
9554 - In munge_extrainfo_into_routerinfo(), check the return value of
9555 memchr(). This would have been a serious issue if we ever passed
9556 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
9558 - On the chance that somebody manages to build Tor on a
9559 platform where time_t is unsigned, correct the way that
9560 microdesc_add_to_cache() handles negative time arguments.
9561 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
9562 - Fix various instances of undefined behavior in channeltls.c,
9563 tor_memmem(), and eventdns.c that would cause us to construct
9564 pointers to memory outside an allocated object. (These invalid
9565 pointers were not accessed, but C does not even allow them to
9566 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
9567 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
9568 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
9569 fix some miscellaneous errors in our tests and codebase. Fixes bug
9570 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
9571 - Always check return values for unlink, munmap, UnmapViewOfFile;
9572 check strftime return values more often. In some cases all we can
9573 do is report a warning, but this may help prevent deeper bugs from
9574 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
9576 - Fix numerous warnings from the clang "scan-build" static analyzer.
9577 Some of these are programming style issues; some of them are false
9578 positives that indicated awkward code; some are undefined behavior
9579 cases related to constructing (but not using) invalid pointers;
9580 some are assumptions about API behavior; some are (harmlessly)
9581 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
9582 correct; and one or two are genuine bugs that weren't reachable
9583 from the rest of the program. Fixes bug 8793; bugfixes on many,
9586 o Minor bugfixes (node selection):
9587 - If ExcludeNodes is set, consider non-excluded hidden service
9588 directory servers before excluded ones. Do not consider excluded
9589 hidden service directory servers at all if StrictNodes is
9590 set. (Previously, we would sometimes decide to connect to those
9591 servers, and then realize before we initiated a connection that
9592 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
9594 - If we set the ExitNodes option but it doesn't include any nodes
9595 that have the Exit flag, we would choose not to bootstrap. Now we
9596 bootstrap so long as ExitNodes includes nodes which can exit to
9597 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
9599 o Minor bugfixes (performance):
9600 - Avoid a bug where every successful connection made us recompute
9601 the flag telling us whether we have sufficient information to
9602 build circuits. Previously, we would forget our cached value
9603 whenever we successfully opened a channel (or marked a router as
9604 running or not running for any other reason), regardless of
9605 whether we had previously believed the router to be running. This
9606 forced us to run an expensive update operation far too often.
9607 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
9608 - Avoid using tor_memeq() for checking relay cell integrity. This
9609 removes a possible performance bottleneck. Fixes part of bug
9610 12169; bugfix on 0.2.1.31.
9612 o Minor bugfixes (platform-specific):
9613 - When dumping a malformed directory object to disk, save it in
9614 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
9616 - Don't report failures from make_socket_reuseable() on incoming
9617 sockets on OSX: this can happen when incoming connections close
9618 early. Fixes bug 10081.
9620 o Minor bugfixes (pluggable transports):
9621 - Avoid another 60-second delay when starting Tor in a pluggable-
9622 transport-using configuration when we already have cached
9623 descriptors for our bridges. Fixes bug 11965; bugfix
9626 o Minor bugfixes (protocol correctness):
9627 - When receiving a VERSIONS cell with an odd number of bytes, close
9628 the connection immediately since the cell is malformed. Fixes bug
9629 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
9632 o Minor bugfixes (relay, other):
9633 - We now drop CREATE cells for already-existent circuit IDs and for
9634 zero-valued circuit IDs, regardless of other factors that might
9635 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
9637 - When rejecting DATA cells for stream_id zero, still count them
9638 against the circuit's deliver window so that we don't fail to send
9639 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
9641 o Minor bugfixes (relay, threading):
9642 - Check return code on spawn_func() in cpuworker code, so that we
9643 don't think we've spawned a nonworking cpuworker and write junk to
9644 it forever. Fix related to bug 4345; bugfix on all released Tor
9645 versions. Found by "skruffy".
9646 - Use a pthread_attr to make sure that spawn_func() cannot return an
9647 error while at the same time launching a thread. Fix related to
9648 bug 4345; bugfix on all released Tor versions. Reported
9651 o Minor bugfixes (relays and bridges):
9652 - Avoid crashing on a malformed resolv.conf file when running a
9653 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
9654 - Non-exit relays no longer launch mock DNS requests to check for
9655 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
9656 non-exit relays stopped servicing DNS requests. Fixes bug 965;
9657 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
9658 - Bridges now report complete directory request statistics. Related
9659 to bug 5824; bugfix on 0.2.2.1-alpha.
9660 - Bridges now never collect statistics that were designed for
9661 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
9663 o Minor bugfixes (testing):
9664 - Fix all valgrind warnings produced by the unit tests. There were
9665 over a thousand memory leak warnings previously, mostly produced
9666 by forgetting to free things in the unit test code. Fixes bug
9667 11618, bugfixes on many versions of Tor.
9669 o Minor bugfixes (tor-fw-helper):
9670 - Give a correct log message when tor-fw-helper fails to launch.
9671 (Previously, we would say something like "tor-fw-helper sent us a
9672 string we could not parse".) Fixes bug 9781; bugfix
9675 o Minor bugfixes (trivial memory leaks):
9676 - Fix a small memory leak when signing a directory object. Fixes bug
9677 11275; bugfix on 0.2.4.13-alpha.
9678 - Resolve some memory leaks found by coverity in the unit tests, on
9679 exit in tor-gencert, and on a failure to compute digests for our
9680 own keys when generating a v3 networkstatus vote. These leaks
9681 should never have affected anyone in practice.
9683 o Code simplification and refactoring:
9684 - Remove some old fallback code designed to keep Tor clients working
9685 in a network with only two working relays. Elsewhere in the code we
9686 have long since stopped supporting such networks, so there wasn't
9687 much point in keeping it around. Addresses ticket 9926.
9688 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
9689 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
9690 - Extract the common duplicated code for creating a subdirectory
9691 of the data directory and writing to a file in it. Fixes ticket
9692 4282; patch from Peter Retzlaff.
9693 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
9694 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
9695 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
9696 - Add a set of accessor functions for the circuit timeout data
9697 structure. Fixes ticket 6153; patch from "piet".
9698 - Clean up exit paths from connection_listener_new(). Closes ticket
9699 8789. Patch from Arlo Breault.
9700 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
9701 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
9702 - Use a doubly-linked list to implement the global circuit list.
9703 Resolves ticket 9108. Patch from Marek Majkowski.
9704 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
9705 - Remove constants and tests for PKCS1 padding; it's insecure and
9706 shouldn't be used for anything new. Fixes bug 8792; patch
9708 - Remove instances of strcpy() from the unit tests. They weren't
9709 hurting anything, since they were only in the unit tests, but it's
9710 embarrassing to have strcpy() in the code at all, and some analysis
9711 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
9712 0.2.3.8-alpha. Patch from Arlo Breault.
9713 - Remove is_internal_IP() function. Resolves ticket 4645.
9714 - Remove unused function circuit_dump_by_chan from circuitlist.c.
9715 Closes issue 9107; patch from "marek".
9716 - Change our use of the ENUM_BF macro to avoid declarations that
9718 - Get rid of router->address, since in all cases it was just the
9719 string representation of router->addr. Resolves ticket 5528.
9722 - Adjust the URLs in the README to refer to the new locations of
9723 several documents on the website. Fixes bug 12830. Patch from
9725 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
9727 - Update manpage to describe some of the files you can expect to
9728 find in Tor's DataDirectory. Addresses ticket 9839.
9729 - Clean up several option names in the manpage to match their real
9730 names, add the missing documentation for a couple of testing and
9731 directory authority options, remove the documentation for a
9732 V2-directory fetching option that no longer exists. Resolves
9734 - Correct the documentation so that it lists the correct directory
9735 for the stats files. (They are in a subdirectory called "stats",
9737 - In the manpage, move more authority-only options into the
9738 directory authority section so that operators of regular directory
9739 caches don't get confused.
9740 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
9741 11061; bugfix on 0.2.4.7-alpha.
9742 - Resolve warnings from Doxygen.
9743 - Document in the manpage that "KBytes" may also be written as
9744 "kilobytes" or "KB", that "Kbits" may also be written as
9745 "kilobits", and so forth. Closes ticket 9222.
9746 - Document that the ClientOnly config option overrides ORPort.
9747 Our old explanation made ClientOnly sound as though it did
9748 nothing at all. Resolves bug 9059.
9749 - Explain that SocksPolicy, DirPolicy, and similar options don't
9750 take port arguments. Fixes the other part of ticket 11108.
9751 - Fix a comment about the rend_server_descriptor_t.protocols field
9752 to more accurately describe its range. Also, make that field
9753 unsigned, to more accurately reflect its usage. Fixes bug 9099;
9754 bugfix on 0.2.1.5-alpha.
9755 - Fix the manpage's description of HiddenServiceAuthorizeClient:
9756 the maximum client name length is 16, not 19. Fixes bug 11118;
9757 bugfix on 0.2.1.6-alpha.
9760 - The contrib directory has been sorted and tidied. Before, it was
9761 an unsorted dumping ground for useful and not-so-useful things.
9762 Now, it is divided based on functionality, and the items which
9763 seemed to be nonfunctional or useless have been removed. Resolves
9764 ticket 8966; based on patches from "rl1987".
9766 o Removed code and features:
9767 - Clients now reject any directory authority certificates lacking
9768 a dir-key-crosscert element. These have been included since
9769 0.2.1.9-alpha, so there's no real reason for them to be optional
9770 any longer. Completes proposal 157. Resolves ticket 10162.
9771 - Remove all code that existed to support the v2 directory system,
9772 since there are no longer any v2 directory authorities. Resolves
9774 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
9775 options, which were used for designating authorities as "Hidden
9776 service authorities". There has been no use of hidden service
9777 authorities since 0.2.2.1-alpha, when we stopped uploading or
9778 downloading v0 hidden service descriptors. Fixes bug 10881; also
9779 part of a fix for bug 10841.
9780 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
9781 and MTBF calculations, but that nobody was using. Fixes bug 11742.
9782 - The TunnelDirConns and PreferTunnelledDirConns options no longer
9783 exist; tunneled directory connections have been available since
9784 0.1.2.5-alpha, and turning them off is not a good idea. This is a
9785 brute-force fix for 10849, where "TunnelDirConns 0" would break
9787 - Remove all code for the long unused v1 directory protocol.
9788 Resolves ticket 11070.
9789 - Remove all remaining code related to version-0 hidden service
9790 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
9791 the rest of bug 10841.
9792 - Remove migration code from when we renamed the "cached-routers"
9793 file to "cached-descriptors" back in 0.2.0.8-alpha. This
9794 incidentally resolves ticket 6502 by cleaning up the related code
9795 a bit. Patch from Akshay Hebbar.
9797 o Test infrastructure:
9798 - Tor now builds each source file in two modes: a mode that avoids
9799 exposing identifiers needlessly, and another mode that exposes
9800 more identifiers for testing. This lets the compiler do better at
9801 optimizing the production code, while enabling us to take more
9802 radical measures to let the unit tests test things.
9803 - The production builds no longer include functions used only in
9804 the unit tests; all functions exposed from a module only for
9805 unit-testing are now static in production builds.
9806 - Add an --enable-coverage configuration option to make the unit
9807 tests (and a new src/or/tor-cov target) to build with gcov test
9809 - Update to the latest version of tinytest.
9810 - Improve the tinytest implementation of string operation tests so
9811 that comparisons with NULL strings no longer crash the tests; they
9812 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
9813 - New macros in test.h to simplify writing mock-functions for unit
9814 tests. Part of ticket 11507. Patch from Dana Koch.
9815 - We now have rudimentary function mocking support that our unit
9816 tests can use to test functions in isolation. Function mocking
9817 lets the tests temporarily replace a function's dependencies with
9818 stub functions, so that the tests can check the function without
9819 invoking the other functions it calls.
9822 - Complete tests for the status.c module. Resolves ticket 11507.
9823 Patch from Dana Koch.
9824 - Add more unit tests for the <circid,channel>->circuit map, and
9825 the destroy-cell-tracking code to fix bug 7912.
9826 - Unit tests for failing cases of the TAP onion handshake.
9827 - More unit tests for address-manipulation functions.
9829 o Distribution (systemd):
9830 - Include a tor.service file in contrib/dist for use with systemd.
9831 Some distributions will be able to use this file unmodified;
9832 others will need to tweak it, or write their own. Patch from Jamie
9833 Nguyen; resolves ticket 8368.
9834 - Verify configuration file via ExecStartPre in the systemd unit
9835 file. Patch from intrigeri; resolves ticket 12730.
9836 - Explicitly disable RunAsDaemon in the systemd unit file. Our
9837 current systemd unit uses "Type = simple", so systemd does not
9838 expect tor to fork. If the user has "RunAsDaemon 1" in their
9839 torrc, then things won't work as expected. This is e.g. the case
9840 on Debian (and derivatives), since there we pass "--defaults-torrc
9841 /usr/share/tor/tor-service-defaults-torrc" (that contains
9842 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
9846 Changes in version 0.2.4.25 - 2014-10-20
9847 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
9848 (even though POODLE does not affect Tor). It also works around a crash
9849 bug caused by some operating systems' response to the "POODLE" attack
9850 (which does affect Tor).
9852 o Major security fixes (also in 0.2.5.9-rc):
9853 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
9854 today support TLS 1.0 or later, so we can safely turn off support
9855 for this old (and insecure) protocol. Fixes bug 13426.
9857 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
9858 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
9859 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
9860 13471. This is a workaround for an OpenSSL bug.
9863 Changes in version 0.2.4.24 - 2014-09-22
9864 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
9865 connecting to hidden services, and it updates the location of one of
9866 the directory authorities.
9869 - Clients now send the correct address for their chosen rendezvous
9870 point when trying to access a hidden service. They used to send
9871 the wrong address, which would still work some of the time because
9872 they also sent the identity digest of the rendezvous point, and if
9873 the hidden service happened to try connecting to the rendezvous
9874 point from a relay that already had a connection open to it,
9875 the relay would reuse that connection. Now connections to hidden
9876 services should be more robust and faster. Also, this bug meant
9877 that clients were leaking to the hidden service whether they were
9878 on a little-endian (common) or big-endian (rare) system, which for
9879 some users might have reduced their anonymity. Fixes bug 13151;
9880 bugfix on 0.2.1.5-alpha.
9882 o Directory authority changes:
9883 - Change IP address for gabelmoo (v3 directory authority).
9885 o Minor features (geoip):
9886 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
9890 Changes in version 0.2.4.23 - 2014-07-28
9891 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
9892 guard rotation, and also backports several important fixes from the
9893 Tor 0.2.5 alpha release series.
9896 - Clients now look at the "usecreatefast" consensus parameter to
9897 decide whether to use CREATE_FAST or CREATE cells for the first hop
9898 of their circuit. This approach can improve security on connections
9899 where Tor's circuit handshake is stronger than the available TLS
9900 connection security levels, but the tradeoff is more computational
9901 load on guard relays. Implements proposal 221. Resolves ticket 9386.
9902 - Make the number of entry guards configurable via a new
9903 NumEntryGuards consensus parameter, and the number of directory
9904 guards configurable via a new NumDirectoryGuards consensus
9905 parameter. Implements ticket 12688.
9908 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
9909 implementation that caused incorrect results on 32-bit
9910 implementations when certain malformed inputs were used along with
9911 a small class of private ntor keys. This bug does not currently
9912 appear to allow an attacker to learn private keys or impersonate a
9913 Tor server, but it could provide a means to distinguish 32-bit Tor
9914 implementations from 64-bit Tor implementations. Fixes bug 12694;
9915 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
9919 - Warn and drop the circuit if we receive an inbound 'relay early'
9920 cell. Those used to be normal to receive on hidden service circuits
9921 due to bug 1038, but the buggy Tor versions are long gone from
9922 the network so we can afford to resume watching for them. Resolves
9923 the rest of bug 1038; bugfix on 0.2.1.19.
9924 - Correct a confusing error message when trying to extend a circuit
9925 via the control protocol but we don't know a descriptor or
9926 microdescriptor for one of the specified relays. Fixes bug 12718;
9927 bugfix on 0.2.3.1-alpha.
9928 - Avoid an illegal read from stack when initializing the TLS
9929 module using a version of OpenSSL without all of the ciphers
9930 used by the v2 link handshake. Fixes bug 12227; bugfix on
9931 0.2.4.8-alpha. Found by "starlight".
9934 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
9938 Changes in version 0.2.4.22 - 2014-05-16
9939 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
9940 alpha release series. These include blocking all authority signing
9941 keys that may have been affected by the OpenSSL "heartbleed" bug,
9942 choosing a far more secure set of TLS ciphersuites by default, closing
9943 a couple of memory leaks that could be used to run a target relay out
9944 of RAM, and several others.
9946 o Major features (security, backport from 0.2.5.4-alpha):
9947 - Block authority signing keys that were used on authorities
9948 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
9949 don't have any evidence that these keys _were_ compromised; we're
9950 doing this to be prudent.) Resolves ticket 11464.
9952 o Major bugfixes (security, OOM):
9953 - Fix a memory leak that could occur if a microdescriptor parse
9954 fails during the tokenizing step. This bug could enable a memory
9955 exhaustion attack by directory servers. Fixes bug 11649; bugfix
9958 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
9959 - The relay ciphersuite list is now generated automatically based on
9960 uniform criteria, and includes all OpenSSL ciphersuites with
9961 acceptable strength and forward secrecy. Previously, we had left
9962 some perfectly fine ciphersuites unsupported due to omission or
9963 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
9964 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
9965 - Relays now trust themselves to have a better view than clients of
9966 which TLS ciphersuites are better than others. (Thanks to bug
9967 11513, the relay list is now well-considered, whereas the client
9968 list has been chosen mainly for anti-fingerprinting purposes.)
9969 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
9970 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
9971 AES128. Resolves ticket 11528.
9972 - Clients now try to advertise the same list of ciphersuites as
9973 Firefox 28. This change enables selection of (fast) GCM
9974 ciphersuites, disables some strange old ciphers, and stops
9975 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
9976 Resolves ticket 11438.
9978 o Minor bugfixes (configuration, security):
9979 - When running a hidden service, do not allow TunneledDirConns 0:
9980 trying to set that option together with a hidden service would
9981 otherwise prevent the hidden service from running, and also make
9982 it publish its descriptors directly over HTTP. Fixes bug 10849;
9983 bugfix on 0.2.1.1-alpha.
9985 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
9986 - Avoid sending a garbage value to the controller when a circuit is
9987 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
9989 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
9990 - Stop leaking memory when we successfully resolve a PTR record.
9991 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
9993 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
9994 - Avoid 60-second delays in the bootstrapping process when Tor is
9995 launching for a second time while using bridges. Fixes bug 9229;
9996 bugfix on 0.2.0.3-alpha.
9998 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
9999 - Give the correct URL in the warning message when trying to run a
10000 relay on an ancient version of Windows. Fixes bug 9393.
10002 o Minor bugfixes (compilation):
10003 - Fix a compilation error when compiling with --disable-curve25519.
10004 Fixes bug 9700; bugfix on 0.2.4.17-rc.
10007 - Downgrade the warning severity for the the "md was still
10008 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
10009 for trying to diagnose this bug, and the current warning in
10010 earlier versions of tor achieves nothing useful. Addresses warning
10013 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
10014 - When we run out of usable circuit IDs on a channel, log only one
10015 warning for the whole channel, and describe how many circuits
10016 there were on the channel. Fixes part of ticket 11553.
10018 o Minor features (security, backport from 0.2.5.4-alpha):
10019 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
10020 leave the default at 8GBytes), to better support Raspberry Pi
10021 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
10023 o Documentation (backport from 0.2.5.4-alpha):
10024 - Correctly document that we search for a system torrc file before
10025 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
10029 Changes in version 0.2.4.21 - 2014-02-28
10030 Tor 0.2.4.21 further improves security against potential adversaries who
10031 find breaking 1024-bit crypto doable, and backports several stability
10032 and robustness patches from the 0.2.5 branch.
10034 o Major features (client security):
10035 - When we choose a path for a 3-hop circuit, make sure it contains
10036 at least one relay that supports the NTor circuit extension
10037 handshake. Otherwise, there is a chance that we're building
10038 a circuit that's worth attacking by an adversary who finds
10039 breaking 1024-bit crypto doable, and that chance changes the game
10040 theory. Implements ticket 9777.
10043 - Do not treat streams that fail with reason
10044 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
10045 since it could also indicate an ENETUNREACH connection error. Fixes
10046 part of bug 10777; bugfix on 0.2.4.8-alpha.
10048 o Code simplification and refactoring:
10049 - Remove data structures which were introduced to implement the
10050 CellStatistics option: they are now redundant with the new timestamp
10051 field in the regular packed_cell_t data structure, which we did
10052 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
10055 - Always clear OpenSSL bignums before freeing them -- even bignums
10056 that don't contain secrets. Resolves ticket 10793. Patch by
10058 - Build without warnings under clang 3.4. (We have some macros that
10059 define static functions only some of which will get used later in
10060 the module. Starting with clang 3.4, these give a warning unless the
10061 unused attribute is set on them.) Resolves ticket 10904.
10062 - Update geoip and geoip6 files to the February 7 2014 Maxmind
10063 GeoLite2 Country database.
10066 - Set the listen() backlog limit to the largest actually supported
10067 on the system, not to the value in a header file. Fixes bug 9716;
10068 bugfix on every released Tor.
10069 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
10070 exit node as a NOROUTE error, not an INTERNAL error, since they
10071 can apparently happen when trying to connect to the wrong sort
10072 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
10073 - Fix build warnings about missing "a2x" comment when building the
10074 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
10075 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
10076 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
10077 not entirely remove it from the connection lists. Fixes bug 9602;
10078 bugfix on 0.2.4.4-alpha.
10079 - Fix a segmentation fault in our benchmark code when running with
10080 Fedora's OpenSSL package, or any other OpenSSL that provides
10081 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
10082 - Turn "circuit handshake stats since last time" log messages into a
10083 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
10085 o Documentation fixes:
10086 - Document that all but one DirPort entry must have the NoAdvertise
10087 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
10090 Changes in version 0.2.4.20 - 2013-12-22
10091 Tor 0.2.4.20 fixes potentially poor random number generation for users
10092 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
10093 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
10094 and 4) have no state file in their DataDirectory (as would happen on
10095 first start). Users who generated relay or hidden service identity
10096 keys in such a situation should discard them and generate new ones.
10098 This release also fixes a logic error that caused Tor clients to build
10099 many more preemptive circuits than they actually need.
10102 - Do not allow OpenSSL engines to replace the PRNG, even when
10103 HardwareAccel is set. The only default builtin PRNG engine uses
10104 the Intel RDRAND instruction to replace the entire PRNG, and
10105 ignores all attempts to seed it with more entropy. That's
10106 cryptographically stupid: the right response to a new alleged
10107 entropy source is never to discard all previously used entropy
10108 sources. Fixes bug 10402; works around behavior introduced in
10109 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
10111 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
10112 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
10113 - Avoid launching spurious extra circuits when a stream is pending.
10114 This fixes a bug where any circuit that _wasn't_ unusable for new
10115 streams would be treated as if it were, causing extra circuits to
10116 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
10119 - Avoid a crash bug when starting with a corrupted microdescriptor
10120 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
10121 - If we fail to dump a previously cached microdescriptor to disk, avoid
10122 freeing duplicate data later on. Fixes bug 10423; bugfix on
10123 0.2.4.13-alpha. Spotted by "bobnomnom".
10126 Changes in version 0.2.4.19 - 2013-12-11
10127 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
10128 (1986-2013). Aaron worked on diverse projects including helping to guide
10129 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
10130 transparency to the U.S government's PACER documents, and contributing
10131 design and development for Tor and Tor2Web. Aaron was one of the latest
10132 martyrs in our collective fight for civil liberties and human rights,
10133 and his death is all the more painful because he was one of us.
10135 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
10136 a new circuit handshake and link encryption that use ECC to provide
10137 better security and efficiency; makes relays better manage circuit
10138 creation requests; uses "directory guards" to reduce client enumeration
10139 risks; makes bridges collect and report statistics about the pluggable
10140 transports they support; cleans up and improves our geoip database;
10141 gets much closer to IPv6 support for clients, bridges, and relays; makes
10142 directory authorities use measured bandwidths rather than advertised
10143 ones when computing flags and thresholds; disables client-side DNS
10144 caching to reduce tracking risks; and fixes a big bug in bridge
10145 reachability testing. This release introduces two new design
10146 abstractions in the code: a new "channel" abstraction between circuits
10147 and or_connections to allow for implementing alternate relay-to-relay
10148 transports, and a new "circuitmux" abstraction storing the queue of
10149 circuits for a channel. The release also includes many stability,
10150 security, and privacy fixes.
10152 o Major features (new circuit handshake):
10153 - Tor now supports a new circuit extension handshake designed by Ian
10154 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
10155 circuit extension handshake, later called "TAP", was a bit slow
10156 (especially on the relay side), had a fragile security proof, and
10157 used weaker keys than we'd now prefer. The new circuit handshake
10158 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
10159 function, making it significantly more secure than the older
10160 handshake, and significantly faster. Tor can use one of two built-in
10161 pure-C curve25519-donna implementations by Adam Langley, or it
10162 can link against the "nacl" library for a tuned version if present.
10164 The built-in version is very fast for 64-bit systems when building
10165 with GCC. The built-in 32-bit version is still faster than the
10166 old TAP protocol, but using libnacl is better on most such hosts.
10168 Implements proposal 216; closes ticket 7202.
10170 o Major features (better link encryption):
10171 - Relays can now enable the ECDHE TLS ciphersuites when available
10172 and appropriate. These ciphersuites let us negotiate forward-secure
10173 TLS secret keys more safely and more efficiently than with our
10174 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
10175 public relays prefer the (faster) P224 group, and bridges prefer
10176 the (more common) P256 group; you can override this with the
10179 This feature requires clients running 0.2.3.17-beta or later,
10180 and requires both sides to be running OpenSSL 1.0.0 or later
10181 with ECC support. OpenSSL 1.0.1, with the compile-time option
10182 "enable-ec_nistp_64_gcc_128", is highly recommended.
10184 Implements the relay side of proposal 198; closes ticket 7200.
10186 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
10187 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
10188 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
10189 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
10190 them to solve bug 6033.)
10192 o Major features (relay performance):
10193 - Instead of limiting the number of queued onionskins (aka circuit
10194 create requests) to a fixed, hard-to-configure number, we limit
10195 the size of the queue based on how many we expect to be able to
10196 process in a given amount of time. We estimate the time it will
10197 take to process an onionskin based on average processing time
10198 of previous onionskins. Closes ticket 7291. You'll never have to
10199 configure MaxOnionsPending again.
10200 - Relays process the new "NTor" circuit-level handshake requests
10201 with higher priority than the old "TAP" circuit-level handshake
10202 requests. We still process some TAP requests to not totally starve
10203 0.2.3 clients when NTor becomes popular. A new consensus parameter
10204 "NumNTorsPerTAP" lets us tune the balance later if we need to.
10205 Implements ticket 9574.
10207 o Major features (client bootstrapping resilience):
10208 - Add a new "FallbackDir" torrc option to use when we can't use
10209 a directory mirror from the consensus (either because we lack a
10210 consensus, or because they're all down). Currently, all authorities
10211 are fallbacks by default, and there are no other default fallbacks,
10212 but that will change. This option will allow us to give clients a
10213 longer list of servers to try to get a consensus from when first
10214 connecting to the Tor network, and thereby reduce load on the
10215 directory authorities. Implements proposal 206, "Preconfigured
10216 directory sources for bootstrapping". We also removed the old
10217 "FallbackNetworkstatus" option, since we never got it working well
10218 enough to use it. Closes bug 572.
10219 - If we have no circuits open, use a relaxed timeout (the
10220 95th-percentile cutoff) until a circuit succeeds. This heuristic
10221 should allow Tor to succeed at building circuits even when the
10222 network connection drastically changes. Should help with bug 3443.
10224 o Major features (use of guards):
10225 - Support directory guards (proposal 207): when possible, clients now
10226 use their entry guards for non-anonymous directory requests. This
10227 can help prevent client enumeration. Note that this behavior only
10228 works when we have a usable consensus directory, and when options
10229 about what to download are more or less standard. In the future we
10230 should re-bootstrap from our guards, rather than re-bootstrapping
10231 from the preconfigured list of directory sources that ships with
10232 Tor. Resolves ticket 6526.
10233 - Raise the default time that a client keeps an entry guard from
10234 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
10235 2012 paper. (We would make it even longer, but we need better client
10236 load balancing first.) Also, make the guard lifetime controllable
10237 via a new GuardLifetime torrc option and a GuardLifetime consensus
10238 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
10240 o Major features (bridges with pluggable transports):
10241 - Bridges now report the pluggable transports they support to the
10242 bridge authority, so it can pass the supported transports on to
10243 bridgedb and/or eventually do reachability testing. Implements
10245 - Automatically forward the TCP ports of pluggable transport
10246 proxies using tor-fw-helper if PortForwarding is enabled. Implements
10249 o Major features (geoip database):
10250 - Maxmind began labelling Tor relays as being in country "A1",
10251 which breaks by-country node selection inside Tor. Now we use a
10252 script to replace "A1" ("Anonymous Proxy") entries in our geoip
10253 file with real country codes. This script fixes about 90% of "A1"
10254 entries automatically and uses manual country code assignments to
10255 fix the remaining 10%. See src/config/README.geoip for details.
10257 - Add GeoIP database for IPv6 addresses. The new config option
10259 - Update to the October 2 2013 Maxmind GeoLite Country database.
10261 o Major features (IPv6):
10262 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
10263 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
10264 to happen. Implements ticket 5535.
10265 - All kind of relays, not just bridges, can now advertise an IPv6
10266 OR port. Implements ticket 6362.
10267 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
10268 connectivity, then set the IPv6Exit flag to 1. Also make sure your
10269 exit policy reads as you would like: the address * applies to all
10270 address families, whereas *4 is IPv4 address only, and *6 is IPv6
10271 addresses only. On the client side, you'll need to wait for enough
10272 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
10273 and use Socks5. Closes ticket 5547, implements proposal 117 as
10274 revised in proposal 208.
10275 - Bridge authorities now accept IPv6 bridge addresses and include
10276 them in network status documents. Implements ticket 5534.
10277 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
10279 o Major features (directory authorities):
10280 - Directory authorities now prefer using measured bandwidths to
10281 advertised ones when computing flags and thresholds. Resolves
10283 - Directory authorities that vote measured bandwidths about more
10284 than a threshold number of relays now treat relays with
10285 unmeasured bandwidths as having bandwidth 0 when computing their
10286 flags. Resolves ticket 8435.
10287 - Directory authorities now support a new consensus method (17)
10288 where they cap the published bandwidth of relays for which
10289 insufficient bandwidth measurements exist. Fixes part of bug 2286.
10290 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
10291 serve any v2 directory information. Now we can test disabling the
10292 old deprecated v2 directory format, and see whether doing so has
10293 any effect on network load. Begins to fix bug 6783.
10295 o Major features (build and portability):
10296 - Switch to a nonrecursive Makefile structure. Now instead of each
10297 Makefile.am invoking other Makefile.am's, there is a master
10298 Makefile.am that includes the others. This change makes our build
10299 process slightly more maintainable, and improves parallelism for
10300 building with make -j. Original patch by Stewart Smith; various
10301 fixes by Jim Meyering.
10302 - Where available, we now use automake's "silent" make rules by
10303 default, so that warnings are easier to spot. You can get the old
10304 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
10305 - Resume building correctly with MSVC and Makefile.nmake. This patch
10306 resolves numerous bugs and fixes reported by ultramage, including
10307 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
10309 o Security features:
10310 - Switch to a completely time-invariant approach for picking nodes
10311 weighted by bandwidth. Our old approach would run through the
10312 part of the loop after it had made its choice slightly slower
10313 than it ran through the part of the loop before it had made its
10314 choice. Addresses ticket 6538.
10315 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
10316 by tor2web clients allows hidden services to identify tor2web
10317 clients through their repeated selection of the same rendezvous
10318 and introduction point circuit endpoints (their guards). Resolves
10321 o Major bugfixes (relay denial of service):
10322 - When we have too much memory queued in circuits (according to a new
10323 MaxMemInCellQueues option), close the circuits that have the oldest
10324 queued cells, on the theory that those are most responsible for
10325 us running low on memory. This prevents us from running out of
10326 memory as a relay if circuits fill up faster than they can be
10327 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
10328 Tor. This bug is a further fix beyond bug 6252, whose fix was
10329 merged into 0.2.3.21-rc.
10330 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
10331 ID: these could be used to create unexpected streams and circuits
10332 which would count as "present" to some parts of Tor but "absent"
10333 to others, leading to zombie circuits and streams or to a bandwidth
10334 denial-of-service. Fixes bug 7889; bugfix on every released version
10335 of Tor. Reported by "oftc_must_be_destroyed".
10336 - Avoid a bug where our response to TLS renegotiation under certain
10337 network conditions could lead to a busy-loop, with 100% CPU
10338 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
10340 o Major bugfixes (asserts, crashes, leaks):
10341 - Prevent the get_freelists() function from running off the end of
10342 the list of freelists if it somehow gets an unrecognized
10343 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
10345 - Avoid a memory leak where we would leak a consensus body when we
10346 find that a consensus which we couldn't previously verify due to
10347 missing certificates is now verifiable. Fixes bug 8719; bugfix
10349 - If we are unable to save a microdescriptor to the journal, do not
10350 drop it from memory and then reattempt downloading it. Fixes bug
10351 9645; bugfix on 0.2.2.6-alpha.
10352 - Fix an assertion failure that would occur when disabling the
10353 ORPort setting on a running Tor process while accounting was
10354 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
10355 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
10356 when an exit connection with optimistic data succeeds immediately
10357 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
10359 - Fix a memory leak that would occur whenever a configuration
10360 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
10362 o Major bugfixes (relay rate limiting):
10363 - When a TLS write is partially successful but incomplete, remember
10364 that the flushed part has been flushed, and notice that bytes were
10365 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
10366 bugfix on Tor 0.1.0.5-rc.
10367 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
10368 to 1GB/1GB. The previous defaults were intended to be "basically
10369 infinite", but it turns out they're now limiting our 100mbit+
10370 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
10371 last time we raised it).
10372 - No longer stop reading or writing on cpuworker connections when
10373 our rate limiting buckets go empty. Now we should handle circuit
10374 handshake requests more promptly. Resolves bug 9731.
10376 o Major bugfixes (client-side privacy):
10377 - When we mark a circuit as unusable for new circuits, have it
10378 continue to be unusable for new circuits even if MaxCircuitDirtiness
10379 is increased too much at the wrong time, or the system clock jumps
10380 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
10381 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
10382 which have resolved to internal addresses") is set, apply that
10383 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
10384 - When an exit relay rejects a stream with reason "exit policy", but
10385 we only know an exit policy summary (e.g. from the microdesc
10386 consensus) for it, do not mark the relay as useless for all exiting.
10387 Instead, mark just the circuit as unsuitable for that particular
10388 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
10390 o Major bugfixes (stream isolation):
10391 - Allow applications to get proper stream isolation with
10392 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
10393 username/password authentication also offer "no authentication". Tor
10394 had previously preferred "no authentication", so the applications
10395 never actually sent Tor their auth details. Now Tor selects
10396 username/password authentication if it's offered. You can disable
10397 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
10398 bug 8117; bugfix on 0.2.3.3-alpha.
10399 - Follow the socks5 protocol when offering username/password
10400 authentication. The fix for bug 8117 exposed this bug, and it
10401 turns out real-world applications like Pidgin do care. Bugfix on
10402 0.2.3.2-alpha; fixes bug 8879.
10404 o Major bugfixes (client circuit building):
10405 - Alter circuit build timeout measurement to start at the point
10406 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
10407 initialization). This should make our timeout measurements more
10408 uniform. Previously, we were sometimes including ORconn setup time
10409 in our circuit build time measurements. Should resolve bug 3443.
10410 - If the circuit build timeout logic is disabled (via the consensus,
10411 or because we are an authority), then don't build testing circuits.
10412 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
10414 o Major bugfixes (client-side DNS):
10415 - Turn off the client-side DNS cache by default. Updating and using
10416 the DNS cache is now configurable on a per-client-port
10417 level. SOCKSPort, DNSPort, etc lines may now contain
10418 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
10419 cache these types of DNS answers when we receive them from an
10420 exit node in response to an application request on this port, and
10421 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
10422 cached DNS answers of these types, we shouldn't use them. It's
10423 potentially risky to use cached DNS answers at the client, since
10424 doing so can indicate to one exit what answers we've gotten
10425 for DNS lookups in the past. With IPv6, this becomes especially
10426 problematic. Using cached DNS answers for requests on the same
10427 circuit would present less linkability risk, since all traffic
10428 on a circuit is already linkable, but it would also provide
10429 little performance benefit: the exit node caches DNS replies
10430 too. Implements a simplified version of Proposal 205. Implements
10433 o Major bugfixes (hidden service privacy):
10434 - Limit hidden service descriptors to at most ten introduction
10435 points, to slow one kind of guard enumeration. Fixes bug 9002;
10436 bugfix on 0.1.1.11-alpha.
10438 o Major bugfixes (directory fetching):
10439 - If the time to download the next old-style networkstatus is in
10440 the future, do not decline to consider whether to download the
10441 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
10443 - We used to always request authority certificates by identity digest,
10444 meaning we'd get the newest one even when we wanted one with a
10445 different signing key. Then we would complain about being given
10446 a certificate we already had, and never get the one we really
10447 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
10448 resource to request the one we want. Fixes bug 5595; bugfix on
10451 o Major bugfixes (bridge reachability):
10452 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
10453 previously they did not, which prevented them from receiving
10454 successful connections from relays for self-test or bandwidth
10455 testing. Also, when a relay is extending a circuit to a bridge,
10456 it needs to send a NETINFO cell, even when the bridge hasn't sent
10457 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
10459 o Major bugfixes (control interface):
10460 - When receiving a new configuration file via the control port's
10461 LOADCONF command, do not treat the defaults file as absent.
10462 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
10464 o Major bugfixes (directory authorities):
10465 - Stop marking every relay as having been down for one hour every
10466 time we restart a directory authority. These artificial downtimes
10467 were messing with our Stable and Guard flag calculations. Fixes
10468 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
10469 - When computing directory thresholds, ignore any rejected-as-sybil
10470 nodes during the computation so that they can't influence Fast,
10471 Guard, etc. (We should have done this for proposal 109.) Fixes
10473 - When marking a node as a likely sybil, reset its uptime metrics
10474 to zero, so that it cannot time towards getting marked as Guard,
10475 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
10477 - Fix a bug in the voting algorithm that could yield incorrect results
10478 when a non-naming authority declared too many flags. Fixes bug 9200;
10479 bugfix on 0.2.0.3-alpha.
10481 o Internal abstraction features:
10482 - Introduce new channel_t abstraction between circuits and
10483 or_connection_t to allow for implementing alternate OR-to-OR
10484 transports. A channel_t is an abstract object which can either be a
10485 cell-bearing channel, which is responsible for authenticating and
10486 handshaking with the remote OR and transmitting cells to and from
10487 it, or a listening channel, which spawns new cell-bearing channels
10488 at the request of remote ORs. Implements part of ticket 6465.
10489 - Make a channel_tls_t subclass of channel_t, adapting it to the
10490 existing or_connection_t code. The V2/V3 protocol handshaking
10491 code which formerly resided in command.c has been moved below the
10492 channel_t abstraction layer and may be found in channeltls.c now.
10493 Implements the rest of ticket 6465.
10494 - Introduce new circuitmux_t storing the queue of circuits for
10495 a channel; this encapsulates and abstracts the queue logic and
10496 circuit selection policy, and allows the latter to be overridden
10497 easily by switching out a policy object. The existing EWMA behavior
10498 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
10500 o New build requirements:
10501 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
10502 strongly recommended.
10503 - Tor maintainers now require Automake version 1.9 or later to build
10504 Tor from the Git repository. (Automake is not required when building
10505 from a source distribution.)
10507 o Minor features (protocol):
10508 - No longer include the "opt" prefix when generating routerinfos
10509 or v2 directories: it has been needless since Tor 0.1.2. Closes
10511 - Reject EXTEND cells sent to nonexistent streams. According to the
10512 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
10513 we were only checking for stream IDs that were currently in use.
10514 Found while hunting for more instances of bug 6271. Bugfix on
10515 0.0.2pre8, which introduced incremental circuit construction.
10516 - Tor relays and clients now support a better CREATE/EXTEND cell
10517 format, allowing the sender to specify multiple address, identity,
10518 and handshake types. Implements Robert Ransom's proposal 200;
10519 closes ticket 7199.
10520 - Reject as invalid most directory objects containing a NUL.
10521 Belt-and-suspender fix for bug 8037.
10523 o Minor features (security):
10524 - Clear keys and key-derived material left on the stack in
10525 rendservice.c and rendclient.c. Check return value of
10526 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
10527 These fixes should make us more forward-secure against cold-boot
10528 attacks and the like. Fixes bug 2385.
10529 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
10530 Irix's random() only return 15 bits; Solaris's random() returns more
10531 bits but its RAND_MAX says it only returns 15, and so on. Motivated
10532 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
10534 o Minor features (control protocol):
10535 - Add a "GETINFO signal/names" control port command. Implements
10537 - Provide default values for all options via "GETINFO config/defaults".
10538 Implements ticket 4971.
10539 - Allow an optional $ before the node identity digest in the
10540 controller command GETINFO ns/id/<identity>, for consistency with
10541 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
10542 - Add CACHED keyword to ADDRMAP events in the control protocol
10543 to indicate whether a DNS result will be cached or not. Resolves
10545 - Generate bootstrapping status update events correctly when fetching
10546 microdescriptors. Fixes bug 9927.
10548 o Minor features (path selection):
10549 - When deciding whether we have enough descriptors to build circuits,
10550 instead of looking at raw relay counts, look at which fraction
10551 of (bandwidth-weighted) paths we're able to build. This approach
10552 keeps clients from building circuits if their paths are likely to
10553 stand out statistically. The default fraction of paths needed is
10554 taken from the consensus directory; you can override it with the
10555 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
10556 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
10557 and we have GeoIP information, also exclude all nodes with unknown
10558 countries "??" and "A1". This behavior is controlled by the
10559 new GeoIPExcludeUnknown option: you can make such nodes always
10560 excluded with "GeoIPExcludeUnknown 1", and disable the feature
10561 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
10562 gets you the default behavior. Implements feature 7706.
10564 o Minor features (hidden services):
10565 - Improve circuit build timeout handling for hidden services.
10566 In particular: adjust build timeouts more accurately depending
10567 upon the number of hop-RTTs that a particular circuit type
10568 undergoes. Additionally, launch intro circuits in parallel
10569 if they timeout, and take the first one to reply as valid.
10570 - The Tor client now ignores sub-domain components of a .onion
10571 address. This change makes HTTP "virtual" hosting
10572 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
10573 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
10574 hosted on the same hidden service. Implements proposal 204.
10575 - Enable Tor to read configuration, state, and key information from
10576 a FIFO. Previously Tor would only read from files with a positive
10577 stat.st_size. Code from meejah; fixes bug 6044.
10579 o Minor features (clients):
10580 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
10581 microdescriptor-related dir requests, and only fall back to normal
10582 descriptors if none of their bridges can handle microdescriptors
10583 (as opposed to the fix in ticket 4013, which caused them to fall
10584 back to normal descriptors if *any* of their bridges preferred
10585 them). Resolves ticket 4994.
10586 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
10587 TCP ports to forward. In the past it only accepted two ports:
10588 the ORPort and the DirPort.
10590 o Minor features (protecting client timestamps):
10591 - Clients no longer send timestamps in their NETINFO cells. These were
10592 not used for anything, and they provided one small way for clients
10593 to be distinguished from each other as they moved from network to
10594 network or behind NAT. Implements part of proposal 222.
10595 - Clients now round timestamps in INTRODUCE cells down to the nearest
10596 10 minutes. If a new Support022HiddenServices option is set to 0, or
10597 if it's set to "auto" and the feature is disabled in the consensus,
10598 the timestamp is sent as 0 instead. Implements part of proposal 222.
10599 - Stop sending timestamps in AUTHENTICATE cells. This is not such
10600 a big deal from a security point of view, but it achieves no actual
10601 good purpose, and isn't needed. Implements part of proposal 222.
10602 - Reduce down accuracy of timestamps in hidden service descriptors.
10603 Implements part of proposal 222.
10605 o Minor features (bridges):
10606 - Make bridge relays check once a minute for whether their IP
10607 address has changed, rather than only every 15 minutes. Resolves
10608 bugs 1913 and 1992.
10609 - Bridge statistics now count bridge clients connecting over IPv6:
10610 bridge statistics files now list "bridge-ip-versions" and
10611 extra-info documents list "geoip6-db-digest". The control protocol
10612 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
10613 implementation by "shkoo", addressing ticket 5055.
10614 - Add a new torrc option "ServerTransportListenAddr" to let bridge
10615 operators select the address where their pluggable transports will
10616 listen for connections. Resolves ticket 7013.
10617 - Randomize the lifetime of our SSL link certificate, so censors can't
10618 use the static value for filtering Tor flows. Resolves ticket 8443;
10619 related to ticket 4014 which was included in 0.2.2.33.
10621 o Minor features (relays):
10622 - Option OutboundBindAddress can be specified multiple times and
10623 accepts IPv6 addresses. Resolves ticket 6876.
10625 o Minor features (IPv6, client side):
10626 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
10627 prefer to hand out virtual IPv6 addresses, since there are more of
10628 them and we can't run out. To override this behavior and make IPv4
10629 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
10630 or DNSPort you're using for resolving. Implements ticket 7571.
10631 - AutomapHostsOnResolve responses are now randomized, to avoid
10632 annoying situations where Tor is restarted and applications
10633 connect to the wrong addresses.
10634 - Never try more than 1000 times to pick a new virtual address when
10635 AutomapHostsOnResolve is set. That's good enough so long as we
10636 aren't close to handing out our entire virtual address space;
10637 if you're getting there, it's best to switch to IPv6 virtual
10640 o Minor features (IPv6, relay/authority side):
10641 - New config option "AuthDirHasIPv6Connectivity 1" that directory
10642 authorities should set if they have IPv6 connectivity and want to
10643 do reachability tests for IPv6 relays. Implements feature 5974.
10644 - A relay with an IPv6 OR port now sends that address in NETINFO
10645 cells (in addition to its other address). Implements ticket 6364.
10647 o Minor features (directory authorities):
10648 - Directory authorities no long accept descriptors for any version of
10649 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
10650 These versions are insecure, unsupported, or both. Implements
10652 - When directory authorities are computing thresholds for flags,
10653 never let the threshold for the Fast flag fall below 4096
10654 bytes. Also, do not consider nodes with extremely low bandwidths
10655 when deciding thresholds for various directory flags. This change
10656 should raise our threshold for Fast relays, possibly in turn
10657 improving overall network performance; see ticket 1854. Resolves
10659 - Directory authorities now include inside each vote a statement of
10660 the performance thresholds they used when assigning flags.
10661 Implements ticket 8151.
10662 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
10663 in directory authority votes to describe whether they have enough
10664 measured bandwidths to ignore advertised (relay descriptor)
10665 bandwidth claims. Resolves ticket 8711.
10667 o Minor features (path bias detection):
10668 - Path Use Bias: Perform separate accounting for successful circuit
10669 use. Keep separate statistics on stream attempt rates versus stream
10670 success rates for each guard. Provide configurable thresholds to
10671 determine when to emit log messages or disable use of guards that
10672 fail too many stream attempts. Resolves ticket 7802.
10673 - Create three levels of Path Bias log messages, as opposed to just
10674 two. These are configurable via consensus as well as via the torrc
10675 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
10676 The default values are 0.70, 0.50, and 0.30 respectively.
10677 - Separate the log message levels from the decision to drop guards,
10678 which also is available via torrc option PathBiasDropGuards.
10679 PathBiasDropGuards still defaults to 0 (off).
10680 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
10681 in combination with PathBiasExtremeRate.
10682 - Increase the default values for PathBiasScaleThreshold and
10683 PathBiasCircThreshold from (200, 20) to (300, 150).
10684 - Add in circuit usage accounting to path bias. If we try to use a
10685 built circuit but fail for any reason, it counts as path bias.
10686 Certain classes of circuits where the adversary gets to pick your
10687 destination node are exempt from this accounting. Usage accounting
10688 can be specifically disabled via consensus parameter or torrc.
10689 - Convert all internal path bias state to double-precision floating
10690 point, to avoid roundoff error and other issues.
10691 - Only record path bias information for circuits that have completed
10692 *two* hops. Assuming end-to-end tagging is the attack vector, this
10693 makes us more resilient to ambient circuit failure without any
10694 detection capability loss.
10696 o Minor features (build):
10697 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
10698 dhill. Resolves ticket 6982.
10699 - Compile on win64 using mingw64. Fixes bug 7260; patches from
10701 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
10702 separate error codes; or at least, don't break for that reason.
10703 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
10705 o Build improvements (autotools):
10706 - Warn if building on a platform with an unsigned time_t: there
10707 are too many places where Tor currently assumes that time_t can
10708 hold negative values. We'd like to fix them all, but probably
10710 - Do not report status verbosely from autogen.sh unless the -v flag
10711 is specified. Fixes issue 4664. Patch from Onizuka.
10712 - Detect and reject attempts to build Tor with threading support
10713 when OpenSSL has been compiled without threading support.
10715 - Try to detect if we are ever building on a platform where
10716 memset(...,0,...) does not set the value of a double to 0.0. Such
10717 platforms are permitted by the C standard, though in practice
10718 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
10719 currently support them, but it's better to detect them and fail
10720 than to perform erroneously.
10721 - We no longer warn so much when generating manpages from their
10723 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
10724 the signs of types during autoconf. This is better than our old
10725 approach, which didn't work when cross-compiling.
10727 o Minor features (log messages, warnings):
10728 - Detect when we're running with a version of OpenSSL other than the
10729 one we compiled with. This conflict has occasionally given people
10730 hard-to-track-down errors.
10731 - Warn users who run hidden services on a Tor client with
10732 UseEntryGuards disabled that their hidden services will be
10733 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
10734 attack which motivated Tor to support entry guards in the first
10735 place). Resolves ticket 6889.
10736 - Warn when we are binding low ports when hibernation is enabled;
10737 previously we had warned when we were _advertising_ low ports with
10738 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
10739 - Issue a warning when running with the bufferevents backend enabled.
10740 It's still not stable, and people should know that they're likely
10741 to hit unexpected problems. Closes ticket 9147.
10743 o Minor features (log messages, notices):
10744 - Refactor resolve_my_address() so it returns the method by which we
10745 decided our public IP address (explicitly configured, resolved from
10746 explicit hostname, guessed from interfaces, learned by gethostname).
10747 Now we can provide more helpful log messages when a relay guesses
10748 its IP address incorrectly (e.g. due to unexpected lines in
10749 /etc/hosts). Resolves ticket 2267.
10750 - Track how many "TAP" and "NTor" circuit handshake requests we get,
10751 and how many we complete, and log it every hour to help relay
10752 operators follow trends in network load. Addresses ticket 9658.
10754 o Minor features (log messages, diagnostics):
10755 - If we fail to free a microdescriptor because of bug 7164, log
10756 the filename and line number from which we tried to free it.
10757 - We compute the overhead from passing onionskins back and forth to
10758 cpuworkers, and report it when dumping statistics in response to
10759 SIGUSR1. Supports ticket 7291.
10760 - Add another diagnostic to the heartbeat message: track and log
10761 overhead that TLS is adding to the data we write. If this is
10762 high, we are sending too little data to SSL_write at a time.
10763 Diagnostic for bug 7707.
10764 - Log packaged cell fullness as part of the heartbeat message.
10765 Diagnosis to try to determine the extent of bug 7743.
10766 - Add more detail to a log message about relaxed timeouts, to help
10768 - When learning a fingerprint for a bridge, log its corresponding
10769 transport type. Implements ticket 7896.
10770 - Warn more aggressively when flushing microdescriptors to a
10771 microdescriptor cache fails, in an attempt to mitigate bug 8031,
10772 or at least make it more diagnosable.
10773 - Improve the log message when "Bug/attack: unexpected sendme cell
10774 from client" occurs, to help us track bug 8093.
10775 - Improve debugging output to help track down bug 8185 ("Bug:
10776 outgoing relay cell has n_chan==NULL. Dropping.")
10778 o Minor features (log messages, quieter bootstrapping):
10779 - Log fewer lines at level "notice" about our OpenSSL and Libevent
10780 versions and capabilities when everything is going right. Resolves
10781 part of ticket 6736.
10782 - Omit the first heartbeat log message, because it never has anything
10783 useful to say, and it clutters up the bootstrapping messages.
10784 Resolves ticket 6758.
10785 - Don't log about reloading the microdescriptor cache at startup. Our
10786 bootstrap warnings are supposed to tell the user when there's a
10787 problem, and our bootstrap notices say when there isn't. Resolves
10788 ticket 6759; bugfix on 0.2.2.6-alpha.
10789 - Don't log "I learned some more directory information" when we're
10790 reading cached directory information. Reserve it for when new
10791 directory information arrives in response to a fetch. Resolves
10793 - Don't complain about bootstrapping problems while hibernating.
10794 These complaints reflect a general code problem, but not one
10795 with any problematic effects (no connections are actually
10796 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
10798 o Minor features (testing):
10799 - In our testsuite, create temporary directories with a bit more
10800 entropy in their name to make name collisions less likely. Fixes
10802 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
10803 (P-256) Diffie-Hellman handshakes to src/or/bench.
10804 - Add benchmark functions to test onion handshake performance.
10807 - The DirServer option is now DirAuthority, for consistency with
10808 current naming patterns. You can still use the old DirServer form.
10810 o Minor bugfixes (protocol):
10811 - Fix the handling of a TRUNCATE cell when it arrives while the
10812 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
10813 - When a Tor client gets a "truncated" relay cell, the first byte of
10814 its payload specifies why the circuit was truncated. We were
10815 ignoring this 'reason' byte when tearing down the circuit, resulting
10816 in the controller not being told why the circuit closed. Now we
10817 pass the reason from the truncated cell to the controller. Bugfix
10818 on 0.1.2.3-alpha; fixes bug 7039.
10819 - Fix a misframing issue when reading the version numbers in a
10820 VERSIONS cell. Previously we would recognize [00 01 00 02] as
10821 'version 1, version 2, and version 0x100', when it should have
10822 only included versions 1 and 2. Fixes bug 8059; bugfix on
10823 0.2.0.10-alpha. Reported pseudonymously.
10824 - Make the format and order of STREAM events for DNS lookups
10825 consistent among the various ways to launch DNS lookups. Fixes
10826 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
10828 o Minor bugfixes (syscalls and disk interaction):
10829 - Always check the return values of functions fcntl() and
10830 setsockopt(). We don't believe these are ever actually failing in
10831 practice, but better safe than sorry. Also, checking these return
10832 values should please analysis tools like Coverity. Patch from
10833 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
10834 - Avoid double-closing the listener socket in our socketpair()
10835 replacement (used on Windows) in the case where the addresses on
10836 our opened sockets don't match what we expected. Fixes bug 9400;
10837 bugfix on 0.0.2pre7. Found by Coverity.
10838 - Correctly store microdescriptors and extrainfo descriptors that
10839 include an internal NUL byte. Fixes bug 8037; bugfix on
10840 0.2.0.1-alpha. Bug reported by "cypherpunks".
10841 - If for some reason we fail to write a microdescriptor while
10842 rebuilding the cache, do not let the annotations from that
10843 microdescriptor linger in the cache file, and do not let the
10844 microdescriptor stay recorded as present in its old location.
10845 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
10846 - Use direct writes rather than stdio when building microdescriptor
10847 caches, in an attempt to mitigate bug 8031, or at least make it
10850 o Minor fixes (config options):
10851 - Warn and fail if a server is configured not to advertise any
10852 ORPorts at all. (We need *something* to put in our descriptor,
10853 or we just won't work.)
10854 - Behave correctly when the user disables LearnCircuitBuildTimeout
10855 but doesn't tell us what they would like the timeout to be. Fixes
10856 bug 6304; bugfix on 0.2.2.14-alpha.
10857 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
10858 to start with a triple-underscore so the controller won't touch it.
10859 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
10860 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
10861 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
10862 - When autodetecting the number of CPUs, use the number of available
10863 CPUs in preference to the number of configured CPUs. Inform the
10864 user if this reduces the number of available CPUs. Fixes bug 8002;
10865 bugfix on 0.2.3.1-alpha.
10866 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
10867 - Make it an error when you set EntryNodes but disable UseGuardNodes,
10868 since it will (surprisingly to some users) ignore EntryNodes. Fixes
10869 bug 8180; bugfix on 0.2.3.11-alpha.
10870 - Avoid overflows when the user sets MaxCircuitDirtiness to a
10871 ridiculously high value, by imposing a (ridiculously high) 30-day
10872 maximum on MaxCircuitDirtiness.
10874 o Minor bugfixes (control protocol):
10875 - Stop sending a stray "(null)" in some cases for the server status
10876 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
10878 - The ADDRMAP command can no longer generate an ill-formed error
10879 code on a failed MAPADDRESS. It now says "internal" rather than
10880 an English sentence fragment with spaces in the middle. Bugfix on
10881 Tor 0.2.0.19-alpha.
10883 o Minor bugfixes (clients / edges):
10884 - When we receive a RELAY_END cell with the reason DONE, or with no
10885 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
10886 status as "connection refused". Previously we reported these cases
10887 as success but then immediately closed the connection. Fixes bug
10888 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
10889 - If the guard we choose first doesn't answer, we would try the
10890 second guard, but once we connected to the second guard we would
10891 abandon it and retry the first one, slowing down bootstrapping.
10892 The fix is to treat all our initially chosen guards as acceptable
10893 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
10894 - When choosing which stream on a formerly stalled circuit to wake
10895 first, make better use of the platform's weak RNG. Previously,
10896 we had been using the % ("modulo") operator to try to generate a
10897 1/N chance of picking each stream, but this behaves badly with
10898 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
10901 o Minor bugfixes (path bias detection):
10902 - If the state file's path bias counts are invalid (presumably from a
10903 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
10904 additional checks and log messages to the scaling of Path Bias
10905 counts, in case there still are remaining issues with scaling.
10906 Should help resolve bug 8235.
10907 - Prevent rounding error in path bias counts when scaling
10908 them down, and use the correct scale factor default. Also demote
10909 some path bias related log messages down a level and make others
10910 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
10911 - Remove a source of rounding error during path bias count scaling;
10912 don't count cannibalized circuits as used for path bias until we
10913 actually try to use them; and fix a circuit_package_relay_cell()
10914 warning message about n_chan==NULL. Fixes bug 7802.
10915 - Paste the description for PathBias parameters from the man
10916 page into or.h, so the code documents them too. Fixes bug 7982;
10917 bugfix on 0.2.3.17-beta.
10919 o Minor bugfixes (relays):
10920 - Stop trying to resolve our hostname so often (e.g. every time we
10921 think about doing a directory fetch). Now we reuse the cached
10922 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
10923 and 2410 (bugfix on 0.1.2.2-alpha).
10924 - When examining the list of network interfaces to find our address,
10925 do not consider non-running or disabled network interfaces. Fixes
10926 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
10928 o Minor bugfixes (blocking resistance):
10929 - Only disable TLS session ticket support when running as a TLS
10930 server. Now clients will blend better with regular Firefox
10931 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
10933 o Minor bugfixes (IPv6):
10934 - Use square brackets around IPv6 addresses in numerous places
10935 that needed them, including log messages, HTTPS CONNECT proxy
10936 requests, TransportProxy statefile entries, and pluggable transport
10937 extra-info lines. Fixes bug 7011; patch by David Fifield.
10939 o Minor bugfixes (directory authorities):
10940 - Reject consensus votes with more than 64 known-flags. We aren't even
10941 close to that limit yet, and our code doesn't handle it correctly.
10942 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
10943 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
10944 bugfix on 0.2.0.3-alpha.
10946 o Minor bugfixes (memory leaks):
10947 - Avoid leaking memory if we fail to compute a consensus signature
10948 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
10949 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
10950 on 0.2.1.1-alpha; fixes bug 7816.
10951 - Fix a memory leak during safe-cookie controller authentication.
10952 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
10953 - Free some more still-in-use memory at exit, to make hunting for
10954 memory leaks easier. Resolves bug 7029.
10956 o Minor bugfixes (code correctness):
10957 - Increase the width of the field used to remember a connection's
10958 link protocol version to two bytes. Harmless for now, since the
10959 only currently recognized versions are one byte long. Reported
10960 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
10961 - Fix a crash when debugging unit tests on Windows: deallocate a
10962 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
10963 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
10964 - When detecting the largest possible file descriptor (in order to
10965 close all file descriptors when launching a new program), actually
10966 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
10967 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
10969 - Avoid a crash if we fail to generate an extrainfo descriptor.
10970 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
10971 this is CID 718634.
10972 - Avoid an off-by-one error when checking buffer boundaries when
10973 formatting the exit status of a pluggable transport helper.
10974 This is probably not an exploitable bug, but better safe than
10975 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
10977 - Get rid of a couple of harmless clang warnings, where we compared
10978 enums to ints. These warnings are newly introduced in clang 3.2.
10980 o Minor bugfixes (code cleanliness):
10981 - Avoid use of reserved identifiers in our C code. The C standard
10982 doesn't like us declaring anything that starts with an
10983 underscore, so let's knock it off before we get in trouble. Fix
10984 for bug 1031; bugfix on the first Tor commit.
10985 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
10986 with large values. This situation was untriggered, but nevertheless
10987 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
10988 - Fix an impossible buffer overrun in the AES unit tests. Fixes
10989 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
10990 - Fix handling of rendezvous client authorization types over 8.
10991 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
10992 - Remove a couple of extraneous semicolons that were upsetting the
10993 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
10994 bugfix on 0.2.2.1-alpha.
10995 - When complaining about a client port on a public address, log
10996 which address we're complaining about. Fixes bug 4020; bugfix on
10997 0.2.3.3-alpha. Patch by Tom Fitzhenry.
10999 o Minor bugfixes (log messages, warnings):
11000 - If we encounter a write failure on a SOCKS connection before we
11001 finish our SOCKS handshake, don't warn that we closed the
11002 connection before we could send a SOCKS reply. Fixes bug 8427;
11003 bugfix on 0.1.0.1-rc.
11004 - Fix a directory authority warn caused when we have a large amount
11005 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
11006 - Downgrade "Failed to hand off onionskin" messages to "debug"
11007 severity, since they're typically redundant with the "Your computer
11008 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
11009 - Avoid spurious warnings when configuring multiple client ports of
11010 which only some are nonlocal. Previously, we had claimed that some
11011 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
11014 o Minor bugfixes (log messages, other):
11015 - Fix log messages and comments to avoid saying "GMT" when we mean
11016 "UTC". Fixes bug 6113.
11017 - When rejecting a configuration because we were unable to parse a
11018 quoted string, log an actual error message. Fixes bug 7950; bugfix
11020 - Correctly recognize that [::1] is a loopback address. Fixes
11021 bug 8377; bugfix on 0.2.1.3-alpha.
11022 - Don't log inappropriate heartbeat messages when hibernating: a
11023 hibernating node is _expected_ to drop out of the consensus,
11024 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
11025 bugfix on 0.2.3.1-alpha.
11026 - Eliminate several instances where we use "Nickname=ID" to refer to
11027 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
11028 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
11031 o Minor bugfixes (build):
11032 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
11033 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
11034 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
11036 o Documentation fixes:
11037 - Make the torify manpage no longer refer to tsocks; torify hasn't
11038 supported tsocks since 0.2.3.14-alpha.
11039 - Make the tor manpage no longer reference tsocks.
11040 - Fix the GeoIPExcludeUnknown documentation to refer to
11041 ExcludeExitNodes rather than the currently nonexistent
11042 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
11043 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
11045 - Say "KBytes" rather than "KB" in the man page (for various values
11046 of K), to further reduce confusion about whether Tor counts in
11047 units of memory or fractions of units of memory. Resolves ticket 7054.
11048 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
11049 names match. Fixes bug 7768.
11050 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
11051 message is logged at notice, not at info.
11052 - Clarify the usage and risks of setting the ContactInfo torrc line
11053 for your relay or bridge. Resolves ticket 9854.
11054 - Add anchors to the manpage so we can link to the html version of
11055 the documentation for specific options. Resolves ticket 9866.
11056 - Replace remaining references to DirServer in man page and
11057 log entries. Resolves ticket 10124.
11059 o Removed features:
11060 - Stop exporting estimates of v2 and v3 directory traffic shares
11061 in extrainfo documents. They were unneeded and sometimes inaccurate.
11062 Also stop exporting any v2 directory request statistics. Resolves
11064 - Drop support for detecting and warning about versions of Libevent
11065 before 1.3e. Nothing reasonable ships with them any longer; warning
11066 the user about them shouldn't be needed. Resolves ticket 6826.
11067 - Now that all versions before 0.2.2.x are disallowed, we no longer
11068 need to work around their missing features. Remove a bunch of
11069 compatibility code.
11072 - The tor-tsocks.conf is no longer distributed or installed. We
11073 recommend that tsocks users use torsocks instead. Resolves
11075 - Remove some of the older contents of doc/ as obsolete; move others
11076 to torspec.git. Fixes bug 8965.
11078 o Code simplification:
11079 - Avoid using character buffers when constructing most directory
11080 objects: this approach was unwieldy and error-prone. Instead,
11081 build smartlists of strings, and concatenate them when done.
11082 - Rename "isin" functions to "contains", for grammar. Resolves
11084 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
11085 with the natural logarithm function from the system libm. Resolves
11087 - Start using OpenBSD's implementation of queue.h, so that we don't
11088 need to hand-roll our own pointer and list structures whenever we
11089 need them. (We can't rely on a sys/queue.h, since some operating
11090 systems don't have them, and the ones that do have them don't all
11091 present the same extensions.)
11092 - Start using OpenBSD's implementation of queue.h (originally by
11094 - Enhance our internal sscanf replacement so that we can eliminate
11095 the last remaining uses of the system sscanf. (Though those uses
11096 of sscanf were safe, sscanf itself is generally error prone, so
11097 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
11099 - Replace all calls to snprintf() outside of src/ext with
11100 tor_snprintf(). Also remove the #define to replace snprintf with
11101 _snprintf on Windows; they have different semantics, and all of
11102 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
11105 - Add a wrapper function for the common "log a message with a
11107 - Split the onion.c file into separate modules for the onion queue
11108 and the different handshakes it supports.
11109 - Move the client-side address-map/virtual-address/DNS-cache code
11110 out of connection_edge.c into a new addressmap.c module.
11111 - Move the entry node code from circuitbuild.c to its own file.
11112 - Move the circuit build timeout tracking code from circuitbuild.c
11114 - Source files taken from other packages now reside in src/ext;
11115 previously they were scattered around the rest of Tor.
11116 - Move the generic "config" code into a new file, and have "config.c"
11117 hold only torrc- and state-related code. Resolves ticket 6823.
11118 - Move the core of our "choose a weighted element at random" logic
11119 into its own function, and give it unit tests. Now the logic is
11120 testable, and a little less fragile too.
11121 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
11122 - Move last_reachable and testing_since from routerinfo_t to node_t.
11123 Implements ticket 5529.
11124 - Add replaycache_t structure, functions and unit tests, then refactor
11125 rend_service_introduce() to be more clear to read, improve, debug,
11126 and test. Resolves bug 6177.
11129 - Remove some now-needless code that tried to aggressively flush
11130 OR connections as data was added to them. Since 0.2.0.1-alpha, our
11131 cell queue logic has saved us from the failure mode that this code
11132 was supposed to prevent. Removing this code will limit the number
11133 of baroque control flow paths through Tor's network logic. Reported
11134 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
11135 - Remove unused code for parsing v1 directories and "running routers"
11136 documents. Fixes bug 6887.
11137 - Remove the marshalling/unmarshalling code for sending requests to
11138 cpuworkers over a socket, and instead just send structs. The
11139 recipient will always be the same Tor binary as the sender, so
11140 any encoding is overkill.
11141 - Remove the testing_since field of node_t, which hasn't been used
11142 for anything since 0.2.0.9-alpha.
11143 - Finally remove support for malloc_good_size and malloc_usable_size.
11144 We had hoped that these functions would let us eke a little more
11145 memory out of our malloc implementation. Unfortunately, the only
11146 implementations that provided these functions are also ones that
11147 are already efficient about not overallocation: they never got us
11148 more than 7 or so bytes per allocation. Removing them saves us a
11149 little code complexity and a nontrivial amount of build complexity.
11152 Changes in version 0.2.3.25 - 2012-11-19
11153 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
11154 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
11155 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
11156 programmer, and friend. Unstinting in his dedication to the cause of
11157 freedom, he inspired and helped many of us as we began our work on
11158 anonymity, and inspires us still. Please honor his memory by writing
11159 software to protect people's freedoms, and by helping others to do so.
11161 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
11162 significantly reduced directory overhead (via microdescriptors),
11163 enormous crypto performance improvements for fast relays on new
11164 enough hardware, a new v3 TLS handshake protocol that can better
11165 resist fingerprinting, support for protocol obfuscation plugins (aka
11166 pluggable transports), better scalability for hidden services, IPv6
11167 support for bridges, performance improvements like allowing clients
11168 to skip the first round-trip on the circuit ("optimistic data") and
11169 refilling token buckets more often, a new "stream isolation" design
11170 to isolate different applications on different circuits, and many
11171 stability, security, and privacy fixes.
11173 Major features (v3 directory protocol):
11174 - Clients now use microdescriptors instead of regular descriptors
11175 to build circuits. Microdescriptors are authority-generated
11176 summaries of regular descriptors' contents, designed to change very
11177 rarely (see proposal 158 for details). This feature is designed
11178 to save bandwidth, especially for clients on slow internet
11179 connections. Use "UseMicrodescriptors 0" to disable it.
11180 - Caches now download, cache, and serve microdescriptors, as well
11181 as multiple "flavors" of the consensus, including a flavor that
11182 describes microdescriptors.
11184 o Major features (build hardening):
11185 - Enable gcc and ld hardening by default. Resolves ticket 5210.
11187 o Major features (relay scaling):
11188 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
11189 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
11190 vectorized AES implementations as appropriate. These can be much,
11191 much faster than other AES implementations.
11192 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
11193 implementation. It makes AES_CTR about 7% faster than our old one
11194 (which was about 10% faster than the one OpenSSL used to provide).
11195 Resolves ticket 4526.
11196 - Use OpenSSL's EVP interface for AES encryption, so that all AES
11197 operations can use hardware acceleration (if present). Resolves
11199 - Unconditionally use OpenSSL's AES implementation instead of our
11200 old built-in one. OpenSSL's AES has been better for a while, and
11201 relatively few servers should still be on any version of OpenSSL
11202 that doesn't have good optimized assembly AES.
11204 o Major features (blocking resistance):
11205 - Update TLS cipher list to match Firefox 8 and later. Resolves
11207 - Remove support for clients falsely claiming to support standard
11208 ciphersuites that they can actually provide. As of modern OpenSSL
11209 versions, it's not necessary to fake any standard ciphersuite,
11210 and doing so prevents us from using better ciphersuites in the
11211 future, since servers can't know whether an advertised ciphersuite
11212 is really supported or not. Some hosts -- notably, ones with very
11213 old versions of OpenSSL or where OpenSSL has been built with ECC
11214 disabled -- will stand out because of this change; TBB users should
11215 not be affected. Implements the client side of proposal 198.
11216 - Implement a new handshake protocol (v3) for authenticating Tors to
11217 each other over TLS. It should be more resistant to fingerprinting
11218 than previous protocols, and should require less TLS hacking for
11219 future Tor implementations. Implements proposal 176.
11220 - Allow variable-length padding cells, to disguise the length of
11221 Tor's TLS records. Implements part of proposal 184.
11222 - While we're trying to bootstrap, record how many TLS connections
11223 fail in each state, and report which states saw the most failures
11224 in response to any bootstrap failures. This feature may speed up
11225 diagnosis of censorship events. Implements ticket 3116.
11227 o Major features (pluggable transports):
11228 - Clients and bridges can now be configured to use a separate
11229 "transport" proxy. This approach makes the censorship arms race
11230 easier by allowing bridges to use protocol obfuscation plugins.
11231 Implements proposal 180 (tickets 2841 and 3472).
11233 o Major features (DoS resistance):
11234 - Now that Tor 0.2.0.x is completely deprecated, enable the final
11235 part of "Proposal 110: Avoiding infinite length circuits" by
11236 refusing all circuit-extend requests that do not use a relay_early
11237 cell. This change helps Tor resist a class of denial-of-service
11238 attacks by limiting the maximum circuit length.
11239 - Tear down the circuit if we get an unexpected SENDME cell. Clients
11240 could use this trick to make their circuits receive cells faster
11241 than our flow control would have allowed, or to gum up the network,
11242 or possibly to do targeted memory denial-of-service attacks on
11243 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
11244 from July 2002, before the release of Tor 0.0.0.
11246 o Major features (hidden services):
11247 - Adjust the number of introduction points that a hidden service
11248 will try to maintain based on how long its introduction points
11249 remain in use and how many introductions they handle. Fixes
11251 - Add a "tor2web mode" for clients that want to connect to hidden
11252 services non-anonymously (and possibly more quickly). As a safety
11253 measure to try to keep users from turning this on without knowing
11254 what they are doing, tor2web mode must be explicitly enabled at
11255 compile time, and a copy of Tor compiled to run in tor2web mode
11256 cannot be used as a normal Tor client. Implements feature 2553.
11258 o Major features (IPv6):
11259 - Clients can now connect to private bridges over IPv6. Bridges
11260 still need at least one IPv4 address in order to connect to
11261 other relays. Note that we don't yet handle the case where the
11262 user has two bridge lines for the same bridge (one IPv4, one
11263 IPv6). Implements parts of proposal 186.
11265 o Major features (directory authorities):
11266 - Use a more secure consensus parameter voting algorithm. Now at
11267 least three directory authorities or a majority of them must
11268 vote on a given parameter before it will be included in the
11269 consensus. Implements proposal 178.
11270 - Remove the artificially low cutoff of 20KB to guarantee the Fast
11271 flag. In the past few years the average relay speed has picked
11272 up, and while the "top 7/8 of the network get the Fast flag" and
11273 "all relays with 20KB or more of capacity get the Fast flag" rules
11274 used to have the same result, now the top 7/8 of the network has
11275 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
11277 o Major features (performance):
11278 - Exit nodes now accept and queue data on not-yet-connected streams.
11279 Previously, the client wasn't allowed to send data until the
11280 stream was connected, which slowed down all connections. This
11281 change will enable clients to perform a "fast-start" on streams
11282 and send data without having to wait for a confirmation that the
11283 stream has opened. Patch from Ian Goldberg; implements the server
11284 side of Proposal 174.
11285 - When using an exit relay running 0.2.3.x, clients can now
11286 "optimistically" send data before the exit relay reports that
11287 the stream has opened. This saves a round trip when starting
11288 connections where the client speaks first (such as web browsing).
11289 This behavior is controlled by a consensus parameter (currently
11290 disabled). To turn it on or off manually, use the "OptimisticData"
11291 torrc option. Implements proposal 181; code by Ian Goldberg.
11292 - Add a new TokenBucketRefillInterval option to refill token buckets
11293 more frequently than once per second. This should improve network
11294 performance, alleviate queueing problems, and make traffic less
11295 bursty. Implements proposal 183; closes ticket 3630. Design by
11296 Florian Tschorsch and Björn Scheuermann; implementation by
11298 - Raise the threshold of server descriptors needed (75%) and exit
11299 server descriptors needed (50%) before we will declare ourselves
11300 bootstrapped. This will make clients start building circuits a
11301 little later, but makes the initially constructed circuits less
11302 skewed and less in conflict with further directory fetches. Fixes
11305 o Major features (relays):
11306 - Relays now try regenerating and uploading their descriptor more
11307 frequently if they are not listed in the consensus, or if the
11308 version of their descriptor listed in the consensus is too
11309 old. This fix should prevent situations where a server declines
11310 to re-publish itself because it has done so too recently, even
11311 though the authorities decided not to list its recent-enough
11312 descriptor. Fix for bug 3327.
11314 o Major features (stream isolation):
11315 - You can now configure Tor so that streams from different
11316 applications are isolated on different circuits, to prevent an
11317 attacker who sees your streams as they leave an exit node from
11318 linking your sessions to one another. To do this, choose some way
11319 to distinguish the applications: have them connect to different
11320 SocksPorts, or have one of them use SOCKS4 while the other uses
11321 SOCKS5, or have them pass different authentication strings to the
11322 SOCKS proxy. Then, use the new SocksPort syntax to configure the
11323 degree of isolation you need. This implements Proposal 171.
11324 - There's a new syntax for specifying multiple client ports (such as
11325 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
11326 multiple *Port entries with full addr:port syntax on each.
11327 The old *ListenAddress format is still supported, but you can't
11328 mix it with the new *Port syntax.
11330 o Major features (bufferevents):
11331 - Tor can now optionally build with the "bufferevents" buffered IO
11332 backend provided by Libevent 2. To use this feature, make sure you
11333 have the latest possible version of Libevent, and pass the
11334 --enable-bufferevents flag to configure when building Tor from
11335 source. This feature will make our networking code more flexible,
11336 let us stack layers on each other, and let us use more efficient
11337 zero-copy transports where available.
11338 - Add experimental support for running on Windows with IOCP and no
11339 kernel-space socket buffers. This feature is controlled by a new
11340 "UserspaceIOCPBuffers" config option (off by default), which has
11341 no effect unless Tor has been built with bufferevents enabled,
11342 you're running on Windows, and you've set "DisableIOCP 0". In the
11343 long run, this may help solve or mitigate bug 98.
11345 o Major features (path selection):
11346 - The EntryNodes option can now include country codes like {de} or IP
11347 addresses or network masks. Previously we had disallowed these
11348 options because we didn't have an efficient way to keep the list up
11349 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
11352 o Major features (port forwarding):
11353 - Add support for automatic port mapping on the many home routers
11354 that support NAT-PMP or UPnP. To build the support code, you'll
11355 need to have the libnatpnp library and/or the libminiupnpc library,
11356 and you'll need to enable the feature specifically by passing
11357 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
11358 it on, use the new PortForwarding option.
11360 o Major features (logging):
11361 - Add a new 'Heartbeat' log message type to periodically log a message
11362 describing Tor's status at level Notice. This feature is meant for
11363 operators who log at notice, and want to make sure that their Tor
11364 server is still working. Implementation by George Kadianakis.
11365 - Make logging resolution configurable with a new LogTimeGranularity
11366 option, and change the default from 1 millisecond to 1 second.
11367 Implements enhancement 1668.
11369 o Major features (other):
11370 - New "DisableNetwork" config option to prevent Tor from launching any
11371 connections or accepting any connections except on a control port.
11372 Bundles and controllers can set this option before letting Tor talk
11373 to the rest of the network, for example to prevent any connections
11374 to a non-bridge address. Packages like Orbot can also use this
11375 option to instruct Tor to save power when the network is off.
11376 - Try to use system facilities for enumerating local interface
11377 addresses, before falling back to our old approach (which was
11378 binding a UDP socket, and calling getsockname() on it). That
11379 approach was scaring OS X users whose draconian firewall
11380 software warned about binding to UDP sockets regardless of
11381 whether packets were sent. Now we try to use getifaddrs(),
11382 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
11383 system supports. Resolves ticket 1827.
11384 - Add experimental support for a "defaults" torrc file to be parsed
11385 before the regular torrc. Torrc options override the defaults file's
11386 options in the same way that the command line overrides the torrc.
11387 The SAVECONF controller command saves only those options which
11388 differ between the current configuration and the defaults file. HUP
11389 reloads both files. Implements task 4552.
11391 o New directory authorities:
11392 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
11393 authority. Closes ticket 5749.
11395 o Security/privacy fixes:
11396 - Avoid read-from-freed-memory and double-free bugs that could occur
11397 when a DNS request fails while launching it. Fixes bug 6480;
11398 bugfix on 0.2.0.1-alpha.
11399 - Reject any attempt to extend to an internal address. Without
11400 this fix, a router could be used to probe addresses on an internal
11401 network to see whether they were accepting connections. Fixes bug
11402 6710; bugfix on 0.0.8pre1.
11403 - Close any connection that sends unrecognized junk before the TLS
11404 handshake. Solves an issue noted in bug 4369.
11405 - The advertised platform of a relay now includes only its operating
11406 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
11407 its service pack level (for Windows) or its CPU architecture
11408 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
11409 can insert an extra string in the platform line by setting the
11410 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
11411 - Disable TLS session tickets. OpenSSL's implementation was giving
11412 our TLS session keys the lifetime of our TLS context objects, when
11413 perfect forward secrecy would want us to discard anything that
11414 could decrypt a link connection as soon as the link connection
11415 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
11416 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
11417 - Tor tries to wipe potentially sensitive data after using it, so
11418 that if some subsequent security failure exposes Tor's memory,
11419 the damage will be limited. But we had a bug where the compiler
11420 was eliminating these wipe operations when it decided that the
11421 memory was no longer visible to a (correctly running) program,
11422 hence defeating our attempt at defense in depth. We fix that
11423 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
11424 is unlikely to optimize away. Future versions of Tor may use
11425 a less ridiculously heavy approach for this. Fixes bug 7352.
11426 Reported in an article by Andrey Karpov.
11428 o Major bugfixes (crashes and asserts):
11429 - Avoid a pair of double-free and use-after-mark bugs that can
11430 occur with certain timings in canceled and re-received DNS
11431 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
11432 - Fix a denial of service attack by which any directory authority
11433 could crash all the others, or by which a single v2 directory
11434 authority could crash everybody downloading v2 directory
11435 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
11436 - Fix an assert that directory authorities could trigger on sighup
11437 during some configuration state transitions. We now don't treat
11438 it as a fatal error when the new descriptor we just generated in
11439 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
11440 - Avoid segfault when starting up having run with an extremely old
11441 version of Tor and parsing its state file. Fixes bug 6801; bugfix
11444 o Major bugfixes (clients):
11445 - If we are unable to find any exit that supports our predicted ports,
11446 stop calling them predicted, so that we don't loop and build
11447 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
11448 which introduced predicted ports.
11449 - Check at each new consensus whether our entry guards were picked
11450 long enough ago that we should rotate them. Previously, we only
11451 did this check at startup, which could lead to us holding a guard
11452 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
11453 - When fetching a bridge descriptor from a bridge authority,
11454 always do so anonymously, whether we have been able to open
11455 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
11456 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
11457 but we'll need to wait for bug 6010 before it's actually usable.
11459 o Major bugfixes (directory voting):
11460 - Check more thoroughly to prevent a rogue authority from
11461 double-voting on any consensus directory parameter. Previously,
11462 authorities would crash in this case if the total number of
11463 votes for any parameter exceeded the number of active voters,
11464 but would let it pass otherwise. Partially fixes bug 5786; bugfix
11466 - When computing weight parameters, behave more robustly in the
11467 presence of a bad bwweightscale value. Previously, the authorities
11468 would crash if they agreed on a sufficiently broken weight_scale
11469 value; now, they use a reasonable default and carry on. Fixes the
11470 rest of bug 5786; bugfix on 0.2.2.17-alpha.
11471 - If authorities are unable to get a v2 consensus document from other
11472 directory authorities, they no longer fall back to fetching
11473 them from regular directory caches. Fixes bug 5635; bugfix on
11474 0.2.2.26-beta, where routers stopped downloading v2 consensus
11475 documents entirely.
11477 o Major bugfixes (relays):
11478 - Fix a bug handling SENDME cells on nonexistent streams that could
11479 result in bizarre window values. Report and patch contributed
11480 pseudonymously. Fixes part of bug 6271. This bug was introduced
11481 before the first Tor release, in svn commit r152.
11482 - Don't update the AccountingSoftLimitHitAt state file entry whenever
11483 tor gets started. This prevents a wrong average bandwidth
11484 estimate, which would cause relays to always start a new accounting
11485 interval at the earliest possible moment. Fixes bug 2003; bugfix
11486 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
11487 immensely in tracking this bug down.
11488 - Fix a possible crash bug when checking for deactivated circuits
11489 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
11490 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
11491 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
11492 connections. This change should allow busy exit relays to stop
11493 running out of available sockets as quickly. Fixes bug 4950;
11494 bugfix on 0.2.2.26-beta.
11496 o Major bugfixes (blocking resistance):
11497 - Bridges no longer include their address in NETINFO cells on outgoing
11498 OR connections, to allow them to blend in better with clients.
11499 Removes another avenue for enumerating bridges. Reported by
11500 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
11501 cells were introduced.
11502 - Warn the user when HTTPProxy, but no other proxy type, is
11503 configured. This can cause surprising behavior: it doesn't send
11504 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
11505 directory traffic only. Resolves ticket 4663.
11507 o Major bugfixes (hidden services):
11508 - Improve hidden service robustness: when an attempt to connect to
11509 a hidden service ends, be willing to refetch its hidden service
11510 descriptors from each of the HSDir relays responsible for them
11511 immediately. Previously, we would not consider refetching the
11512 service's descriptors from each HSDir for 15 minutes after the last
11513 fetch, which was inconvenient if the hidden service was not running
11514 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
11515 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
11516 They used to check that the timestamp was within 30 minutes
11517 of their system clock, so they could cap the size of their
11518 replay-detection cache, but that approach unnecessarily refused
11519 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
11520 the v3 intro-point protocol (the first one which sent a timestamp
11521 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
11522 - When one of a hidden service's introduction points appears to be
11523 unreachable, stop trying it. Previously, we would keep trying
11524 to build circuits to the introduction point until we lost the
11525 descriptor, usually because the user gave up and restarted Tor.
11526 Fixes part of bug 3825.
11528 o Changes to default torrc file:
11529 - Stop listing "socksport 9050" in torrc.sample. We open a socks
11530 port on 9050 by default anyway, so this should not change anything
11532 - Stop mentioning the deprecated *ListenAddress options in
11533 torrc.sample. Fixes bug 5438.
11534 - Document unit of bandwidth-related options in sample torrc.
11536 - Fix broken URLs in the sample torrc file, and tell readers about
11537 the OutboundBindAddress, ExitPolicyRejectPrivate, and
11538 PublishServerDescriptor options. Addresses bug 4652.
11540 o Minor features (directory authorities):
11541 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
11542 change when the authority is deciding whether to accept a newly
11543 uploaded descriptor. Implements ticket 6423.
11544 - Directory authorities are now a little more lenient at accepting
11545 older router descriptors, or newer router descriptors that don't
11546 make big changes. This should help ameliorate past and future
11547 issues where routers think they have uploaded valid descriptors,
11548 but the authorities don't think so. Fix for ticket 2479.
11549 - Authority operators can now vote for all relays in a given
11550 set of countries to be BadDir/BadExit/Invalid/Rejected.
11551 - Provide two consensus parameters (FastFlagMinThreshold and
11552 FastFlagMaxThreshold) to control the range of allowable bandwidths
11553 for the Fast directory flag. These allow authorities to run
11554 experiments on appropriate requirements for being a "Fast" node.
11555 The AuthDirFastGuarantee config value still applies. Implements
11558 o Minor features (bridges / bridge authorities):
11559 - Make bridge SSL certificates a bit more stealthy by using random
11560 serial numbers, in the same fashion as OpenSSL when generating
11561 self-signed certificates. Implements ticket 4584.
11562 - Tag a bridge's descriptor as "never to be sent unencrypted".
11563 This shouldn't matter, since bridges don't open non-anonymous
11564 connections to the bridge authority and don't allow unencrypted
11565 directory connections from clients, but we might as well make
11566 sure. Closes bug 5139.
11567 - The Bridge Authority now writes statistics on how many bridge
11568 descriptors it gave out in total, and how many unique descriptors
11569 it gave out. It also lists how often the most and least commonly
11570 fetched descriptors were given out, as well as the median and
11571 25th/75th percentile. Implements tickets 4200 and 4294.
11573 o Minor features (IPv6):
11574 - Make the code that clients use to detect an address change be
11575 IPv6-aware, so that it won't fill clients' logs with error
11576 messages when trying to get the IPv4 address of an IPv6
11577 connection. Implements ticket 5537.
11578 - Relays now understand an IPv6 address when they get one from a
11579 directory server. Resolves ticket 4875.
11581 o Minor features (hidden services):
11582 - Expire old or over-used hidden service introduction points.
11583 Required by fix for bug 3460.
11584 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
11585 public key replay-detection cache from 60 minutes to 5 minutes. This
11586 replay-detection cache is now used only to detect multiple
11587 INTRODUCE2 cells specifying the same rendezvous point, so we can
11588 avoid launching multiple simultaneous attempts to connect to it.
11589 - When a hidden service's introduction point times out, consider
11590 trying it again during the next attempt to connect to the
11591 HS. Previously, we would not try it again unless a newly fetched
11592 descriptor contained it. Required by fixes for bugs 1297 and 3825.
11594 o Minor features (relays):
11595 - Relays now include a reason for regenerating their descriptors
11596 in an HTTP header when uploading to the authorities. This will
11597 make it easier to debug descriptor-upload issues in the future.
11598 - Turn on directory request statistics by default and include them in
11599 extra-info descriptors. Don't break if we have no GeoIP database.
11600 - Replace files in stats/ rather than appending to them. Now that we
11601 include statistics in extra-info descriptors, it makes no sense to
11602 keep old statistics forever. Implements ticket 2930.
11603 - Relays that set "ConnDirectionStatistics 1" write statistics on the
11604 bidirectional use of connections to disk every 24 hours.
11605 - Add a GeoIP file digest to the extra-info descriptor. Implements
11608 o Minor features (new config options):
11609 - New config option "DynamicDHGroups" (disabled by default) provides
11610 each bridge with a unique prime DH modulus to be used during
11611 SSL handshakes. This option attempts to help against censors
11612 who might use the Apache DH modulus as a static identifier for
11613 bridges. Addresses ticket 4548.
11614 - New config option "DisableDebuggerAttachment" (on by default)
11615 to prevent basic debugging attachment attempts by other processes.
11616 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
11617 - Ordinarily, Tor does not count traffic from private addresses (like
11618 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
11619 There is now a new option, CountPrivateBandwidth, to disable this
11620 behavior. Patch from Daniel Cagara.
11622 o Minor features (different behavior for old config options):
11623 - Allow MapAddress directives to specify matches against super-domains,
11624 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
11625 Implements issue 933.
11626 - Don't disable the DirPort when we cannot exceed our AccountingMax
11627 limit during this interval because the effective bandwidthrate is
11628 low enough. This is useful in a situation where AccountMax is only
11629 used as an additional safeguard or to provide statistics.
11630 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
11631 implements ticket 3439.
11632 - When configuring a large set of nodes in EntryNodes, and there are
11633 enough of them listed as Guard so that we don't need to consider
11634 the non-guard entries, prefer the ones listed with the Guard flag.
11635 - If you set the NumCPUs option to 0, Tor will now try to detect how
11636 many CPUs you have. This is the new default behavior.
11637 - The NodeFamily option -- which let you declare that you want to
11638 consider nodes to be part of a family whether they list themselves
11639 that way or not -- now allows IP address ranges and country codes.
11641 o Minor features (new command-line config behavior):
11642 - Slightly change behavior of "list" options (that is, config
11643 options that can appear more than once) when they appear both in
11644 torrc and on the command line. Previously, the command-line options
11645 would be appended to the ones from torrc. Now, the command-line
11646 options override the torrc options entirely. This new behavior
11647 allows the user to override list options (like exit policies and
11648 ports to listen on) from the command line, rather than simply
11649 appending to the list.
11650 - You can get the old (appending) command-line behavior for "list"
11651 options by prefixing the option name with a "+".
11652 - You can remove all the values for a "list" option from the command
11653 line without adding any new ones by prefixing the option name
11656 o Minor features (controller, new events):
11657 - Extend the control protocol to report flags that control a circuit's
11658 path selection in CIRC events and in replies to 'GETINFO
11659 circuit-status'. Implements part of ticket 2411.
11660 - Extend the control protocol to report the hidden service address
11661 and current state of a hidden-service-related circuit in CIRC
11662 events and in replies to 'GETINFO circuit-status'. Implements part
11664 - Include the creation time of a circuit in CIRC and CIRC2
11665 control-port events and the list produced by the 'GETINFO
11666 circuit-status' control-port command.
11667 - Add a new CONF_CHANGED event so that controllers can be notified
11668 of any configuration changes made by other controllers, or by the
11669 user. Implements ticket 1692.
11670 - Add a new SIGNAL event to the controller interface so that
11671 controllers can be notified when Tor handles a signal. Resolves
11672 issue 1955. Patch by John Brooks.
11674 o Minor features (controller, new getinfo options):
11675 - Expose our view of whether we have gone dormant to the controller,
11676 via a new "GETINFO dormant" value. Torbutton and other controllers
11677 can use this to avoid doing periodic requests through Tor while
11678 it's dormant (bug 4718). Resolves ticket 5954.
11679 - Add a new GETINFO option to get total bytes read and written. Patch
11680 from pipe, revised by atagar. Resolves ticket 2345.
11681 - Implement new GETINFO controller fields to provide information about
11682 the Tor process's pid, euid, username, and resource limits.
11684 o Minor features (controller, other):
11685 - Allow controllers to request an event notification whenever a
11686 circuit is cannibalized or its purpose is changed. Implements
11687 part of ticket 3457.
11688 - Use absolute path names when reporting the torrc filename in the
11689 control protocol, so a controller can more easily find the torrc
11690 file. Resolves bug 1101.
11691 - When reporting the path to the cookie file to the controller,
11692 give an absolute path. Resolves ticket 4881.
11694 o Minor features (log messages):
11695 - Add more information to a log statement that might help track down
11696 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
11697 non-IP address" messages (or any Bug messages, for that matter!),
11698 please let us know about it.
11699 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
11700 EntryNodes will have no effect. Resolves issue 2571.
11701 - Try to make the introductory warning message that Tor prints on
11702 startup more useful for actually finding help and information.
11703 Resolves ticket 2474.
11704 - When the system call to create a listener socket fails, log the
11705 error message explaining why. This may help diagnose bug 4027.
11707 o Minor features (other):
11708 - When we fail to initialize Libevent, retry with IOCP disabled so we
11709 don't need to turn on multi-threading support in Libevent, which in
11710 turn requires a working socketpair(). This is a workaround for bug
11711 4457, which affects Libevent versions from 2.0.1-alpha through
11713 - When starting as root and then changing our UID via the User
11714 control option, and we have a ControlSocket configured, make sure
11715 that the ControlSocket is owned by the same account that Tor will
11716 run under. Implements ticket 3421; fix by Jérémy Bobbio.
11717 - Accept attempts to include a password authenticator in the
11718 handshake, as supported by SOCKS5. This handles SOCKS clients that
11719 don't know how to omit a password when authenticating. Resolves
11721 - Check for and recover from inconsistency in the microdescriptor
11722 cache. This will make it harder for us to accidentally free a
11723 microdescriptor without removing it from the appropriate data
11724 structures. Fixes issue 3135; issue noted by "wanoskarnet".
11725 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
11727 o Minor bugfixes (code security):
11728 - Prevent a null-pointer dereference when receiving a data cell
11729 for a nonexistent stream when the circuit in question has an
11730 empty deliver window. We don't believe this is triggerable,
11731 since we don't currently allow deliver windows to become empty,
11732 but the logic is tricky enough that it's better to make the code
11733 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
11734 - Fix a (harmless) integer overflow in cell statistics reported by
11735 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
11736 - Fix our implementation of crypto_random_hostname() so it can't
11737 overflow on ridiculously large inputs. (No Tor version has ever
11738 provided this kind of bad inputs, but let's be correct in depth.)
11739 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
11740 - Add a (probably redundant) memory clear between iterations of
11741 the router status voting loop, to prevent future coding errors
11742 where data might leak between iterations of the loop. Resolves
11745 o Minor bugfixes (wrapper functions):
11746 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
11747 utility function used in the control-port code). This shouldn't
11748 ever happen unless Tor is completely out of memory, but if it did
11749 happen and Tor somehow recovered from it, Tor could have sent a log
11750 message to a control port in the middle of a reply to a controller
11751 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
11752 - Fix some (not actually triggerable) buffer size checks in usage of
11753 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
11755 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
11756 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
11757 - Enforce correct return behavior of tor_vsscanf() when the '%%'
11758 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
11759 - Make our replacement implementation of strtok_r() compatible with
11760 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
11761 bugfix on 0.2.2.1-alpha.
11762 - Find more places in the code that should have been testing for
11763 invalid sockets using the SOCKET_OK macro. Required for a fix
11764 for bug 4533. Bugfix on 0.2.2.28-beta.
11766 o Minor bugfixes (code correctness):
11767 - Check return value of fputs() when writing authority certificate
11768 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
11769 - When building Tor on Windows with -DUNICODE (not default), ensure
11770 that error messages, filenames, and DNS server names are always
11771 NUL-terminated when we convert them to a single-byte encoding.
11772 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
11773 - Fix a memory leak when trying to launch a DNS request when the
11774 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
11776 - Correct file sizes when reading binary files on Cygwin, to avoid
11777 a bug where Tor would fail to read its state file. Fixes bug 6844;
11778 bugfix on 0.1.2.7-alpha.
11779 - Make sure to set *socket_error in all error cases in
11780 connection_connect(), so it can't produce a warning about
11781 errno being zero from errno_to_orconn_end_reason(). Bugfix on
11782 0.2.1.1-alpha; resolves ticket 6028.
11783 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
11784 bug 4532; found by "troll_un".
11786 o Minor bugfixes (clients):
11787 - Allow one-hop directory-fetching circuits the full "circuit build
11788 timeout" period, rather than just half of it, before failing them
11789 and marking the relay down. This fix should help reduce cases where
11790 clients declare relays (or worse, bridges) unreachable because
11791 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
11792 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
11794 - Ensure we don't cannibalize circuits that are longer than three hops
11795 already, so we don't end up making circuits with 5 or more
11796 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
11797 0.1.0.1-rc which introduced cannibalization.
11799 o Minor bugfixes (relays):
11800 - Don't publish a new relay descriptor when we reload our onion key,
11801 unless the onion key has actually changed. Fixes bug 3263 and
11802 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
11803 - When relays refuse a "create" cell because their queue of pending
11804 create cells is too big (typically because their cpu can't keep up
11805 with the arrival rate), send back reason "resource limit" rather
11806 than reason "internal", so network measurement scripts can get a
11807 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
11808 - Exit nodes don't need to fetch certificates for authorities that
11809 they don't recognize; only directory authorities, bridges,
11810 and caches need to do that. Fixes part of bug 2297; bugfix on
11813 o Minor bugfixes (directory authority / mirrors):
11814 - Avoid O(n^2) performance characteristics when parsing a large
11815 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
11816 - Authorities no longer include any router in their microdescriptor
11817 consensuses for which they couldn't generate or agree on a
11818 microdescriptor. Fixes the second piece of bug 6404; fix on
11820 - When checking for requested signatures on the latest consensus
11821 before serving it to a client, make sure to check the right
11822 consensus flavor. Bugfix on 0.2.2.6-alpha.
11823 - Fix an edge case where TestingTorNetwork is set but the authorities
11824 and relays all have an uptime of zero, so the private Tor network
11825 could briefly lack support for hidden services. Fixes bug 3886;
11826 bugfix on 0.2.2.18-alpha.
11827 - Directory caches no longer refuse to clean out descriptors because
11828 of missing v2 networkstatus documents, unless they're configured
11829 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
11830 0.2.2.26-beta. Patch by Daniel Bryg.
11831 - Don't serve or accept v2 hidden service descriptors over a relay's
11832 DirPort. It's never correct to do so, and disabling it might
11833 make it more annoying to exploit any bugs that turn up in the
11834 descriptor-parsing code. Fixes bug 7149.
11836 o Minor bugfixes (hidden services, client-side):
11837 - Assert that hidden-service-related operations are not performed
11838 using single-hop circuits. Previously, Tor would assert that
11839 client-side streams are not attached to single-hop circuits,
11840 but not that other sensitive operations on the client and service
11841 side are not performed using single-hop circuits. Fixes bug 3332;
11843 - Avoid undefined behavior when parsing the list of supported
11844 rendezvous/introduction protocols in a hidden service descriptor.
11845 Previously, Tor would have confused (as-yet-unused) protocol version
11846 numbers greater than 32 with lower ones on many platforms. Fixes
11847 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
11848 - Don't close hidden service client circuits which have almost
11849 finished connecting to their destination when they reach
11850 the normal circuit-build timeout. Previously, we would close
11851 introduction circuits which are waiting for an acknowledgement
11852 from the introduction point, and rendezvous circuits which have
11853 been specified in an INTRODUCE1 cell sent to a hidden service,
11854 after the normal CBT. Now, we mark them as 'timed out', and launch
11855 another rendezvous attempt in parallel. This behavior change can
11856 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
11857 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
11859 o Minor bugfixes (hidden services, service-side):
11860 - Don't close hidden-service-side rendezvous circuits when they
11861 reach the normal circuit-build timeout. This behavior change can
11862 be disabled using the new
11863 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
11864 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
11865 - Don't launch more than 10 service-side introduction-point circuits
11866 for a hidden service in five minutes. Previously, we would consider
11867 launching more introduction-point circuits if at least one second
11868 had passed without any introduction-point circuits failing. Fixes
11869 bug 4607; bugfix on 0.0.7pre1.
11871 o Minor bugfixes (config option behavior):
11872 - If the user tries to set MyFamily on a bridge, refuse to
11873 do so, and warn about the security implications. Fixes bug 4657;
11874 bugfix on 0.2.0.3-alpha.
11875 - The "--quiet" and "--hush" options now apply not only to Tor's
11876 behavior before logs are configured, but also to Tor's behavior in
11877 the absence of configured logs. Fixes bug 3550; bugfix on
11879 - Change the AllowDotExit rules so they should actually work.
11880 We now enforce AllowDotExit only immediately after receiving an
11881 address via SOCKS or DNSPort: other sources are free to provide
11882 .exit addresses after the resolution occurs. Fixes bug 3940;
11883 bugfix on 0.2.2.1-alpha.
11884 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
11885 don't depend on the consensus parameters or compute adaptive
11886 timeouts when it is disabled. Fixes bug 5049; bugfix on
11888 - After we pick a directory mirror, we would refuse to use it if
11889 it's in our ExcludeExitNodes list, resulting in mysterious failures
11890 to bootstrap for people who just wanted to avoid exiting from
11891 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
11892 - When told to add a bridge with the same digest as a preexisting
11893 bridge but a different addr:port, change the addr:port as
11894 requested. Previously we would not notice the change. Fixes half
11895 of bug 5603; fix on 0.2.2.26-beta.
11897 o Minor bugfixes (controller):
11898 - Allow manual 'authenticate' commands to the controller interface
11899 from netcat (nc) as well as telnet. We were rejecting them because
11900 they didn't come with the expected whitespace at the end of the
11901 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
11902 - Report a real bootstrap problem to the controller on router
11903 identity mismatch. Previously we just said "foo", which probably
11904 made a lot of sense at the time. Fixes bug 4169; bugfix on
11906 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
11907 option is set to 0 (which Vidalia version 0.2.16 now does when
11908 a SAVECONF attempt fails), perform other actions that SIGHUP
11909 usually causes (like reopening the logs). Fixes bug 5095; bugfix
11911 - Correctly handle checking the permissions on the parent
11912 directory of a control socket in the root directory. Bug found
11913 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
11915 - End AUTHCHALLENGE error messages (in the control protocol) with
11916 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
11918 o Minor bugfixes (network reading/writing):
11919 - Disable writing on marked-for-close connections when they are
11920 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
11921 bug 5263; bugfix on 0.0.2pre13, where we first added a special
11922 case for flushing marked connections.
11923 - Make sure that there are no unhandled pending TLS errors before
11924 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
11925 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
11926 Bugfix on 0.1.0.5-rc; fixes bug 4528.
11927 - Detect SSL handshake even when the initial attempt to write the
11928 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
11929 - If the client fails to set a reasonable set of ciphersuites
11930 during its v2 handshake renegotiation, allow the renegotiation to
11931 continue nevertheless (i.e. send all the required certificates).
11932 Fixes bug 4591; bugfix on 0.2.0.20-rc.
11934 o Minor bugfixes (other):
11935 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
11936 resource exhaustion, so that clients can adjust their load to
11937 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
11938 started using END_STREAM_REASON_RESOURCELIMIT.
11939 - Don't check for whether the address we're using for outbound
11940 connections has changed until after the outbound connection has
11941 completed. On Windows, getsockname() doesn't succeed until the
11942 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
11943 - Don't hold a Windows file handle open for every file mapping;
11944 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
11946 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
11947 bugfix on 0.2.1.10-alpha.
11948 - If we fail to write a microdescriptor to the disk cache, do not
11949 continue replacing the old microdescriptor file. Fixes bug 2954;
11950 bugfix on 0.2.2.6-alpha.
11952 o Minor bugfixes (log messages, path selection):
11953 - Downgrade "set buildtimeout to low value" messages to "info"
11954 severity; they were never an actual problem, there was never
11955 anything reasonable to do about them, and they tended to spam logs
11956 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
11957 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
11958 more information to it, so that we can track it down in case it
11959 returns again. Mitigates bug 5235.
11960 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
11961 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
11962 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
11963 - Issue a log message if a guard completes less than 40% of your
11964 circuits. Threshold is configurable by torrc option
11965 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
11966 additional, off-by-default code to disable guards which fail too
11967 many circuits. Addresses ticket 5458.
11969 o Minor bugfixes (log messages, client):
11970 - Downgrade "Got a certificate, but we already have it" log messages
11971 from warning to info, except when we're a dirauth. Fixes bug 5238;
11972 bugfix on 0.2.1.7-alpha.
11973 - Fix the log message describing how we work around discovering
11974 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
11975 4837; bugfix on 0.2.2.9-alpha.
11976 - When logging about a disallowed .exit name, do not also call it
11977 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
11978 - Fix a log message suggesting that people contact a non-existent
11979 email address. Fixes bug 3448.
11980 - Rephrase the log message emitted if the TestSocks check is
11981 successful. Patch from Fabian Keil; fixes bug 4094.
11982 - Log (at debug level) whenever a circuit's purpose is changed.
11983 - Log SSL state transitions at log level DEBUG, log domain
11984 HANDSHAKE. This can be useful for debugging censorship events.
11985 Implements ticket 3264.
11986 - We now log which torrc file we're using on startup. Implements
11988 - Rate-limit log messages when asked to connect anonymously to
11989 a private address. When these hit, they tended to hit fast and
11990 often. Also, don't bother trying to connect to addresses that we
11991 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
11992 reply makes us think we have been lied to, even when the address the
11993 client tried to connect to was "localhost." Resolves ticket 2822.
11995 o Minor bugfixes (log messages, non-client):
11996 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
11997 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
11998 - Don't log that we have "decided to publish new relay descriptor"
11999 unless we are actually publishing a descriptor. Fixes bug 3942;
12000 bugfix on 0.2.2.28-beta.
12001 - Log which authority we're missing votes from when we go to fetch
12002 them from the other auths.
12003 - Replace "Sending publish request" log messages with "Launching
12004 upload", so that they no longer confusingly imply that we're
12005 sending something to a directory we might not even be connected
12006 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
12007 - Warn when Tor is configured to use accounting in a way that can
12008 link a hidden service to some other hidden service or public
12009 address. Resolves ticket 6490.
12010 - Fix a minor formatting issue in one of tor-gencert's error messages.
12014 - Update to the latest version of the tinytest unit testing framework.
12015 This includes a couple of bugfixes that can be relevant for
12016 running forked unit tests on Windows, and removes all reserved
12018 - Avoid a false positive in the util/threads unit test by increasing
12019 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
12020 - Make it possible to set the TestingTorNetwork configuration
12021 option using AlternateDirAuthority and AlternateBridgeAuthority
12022 as an alternative to setting DirServer. Addresses ticket 6377.
12023 - Add a unit test for the environment_variable_names_equal() function.
12024 - A wide variety of new unit tests by Esteban Manchado Velázquez.
12025 - Numerous new unit tests for functions in util.c and address.c by
12027 - The long-disabled benchmark tests are now split into their own
12028 ./src/test/bench binary.
12029 - The benchmark tests can now use more accurate timers than
12030 gettimeofday() when such timers are available.
12031 - Use tt_assert(), not tor_assert(), for checking for test failures.
12032 This makes the unit tests more able to go on in the event that
12035 o Build improvements:
12036 - Use the dead_strip option when building Tor on OS X. This reduces
12037 binary size by almost 19% when linking openssl and libevent
12038 statically, which we do for Tor Browser Bundle.
12039 - Provide a better error message about possible OSX Asciidoc failure
12040 reasons. Fixes bug 6436.
12041 - Detect attempts to build Tor on (as yet hypothetical) versions
12042 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
12043 fix for bug 4533. Bugfix on 0.2.2.28-beta.
12044 - On Windows, we now define the _WIN32_WINNT macros only if they
12045 are not already defined. This lets the person building Tor decide,
12046 if they want, to require a later version of Windows.
12047 - Our autogen.sh script now uses autoreconf to launch autoconf,
12048 automake, and so on. This is more robust against some of the failure
12049 modes associated with running the autotools pieces on their own.
12050 - Running "make version" now displays the version of Tor that
12051 we're about to build. Idea from katmagic; resolves issue 4400.
12052 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
12053 on 0.2.2.4-alpha; fixes bug 3427.
12054 - New --enable-static-tor configure option for building Tor as
12055 statically as possible. Idea, general hackery and thoughts from
12056 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
12058 - Limited, experimental support for building with nmake and MSVC.
12060 o Build requirements:
12061 - Building Tor with bufferevent support now requires Libevent
12062 2.0.13-stable or later. Previous versions of Libevent had bugs in
12063 SSL-related bufferevents and related issues that would make Tor
12064 work badly with bufferevents. Requiring 2.0.13-stable also allows
12065 Tor with bufferevents to take advantage of Libevent APIs
12066 introduced after 2.0.8-rc.
12067 - Our build system requires automake 1.6 or later to create the
12068 Makefile.in files. Previously, you could have used 1.4.
12069 This only affects developers and people building Tor from git;
12070 people who build Tor from the source distribution without changing
12071 the Makefile.am files should be fine.
12072 - Detect when we try to build on a platform that doesn't define
12073 AF_UNSPEC to 0. We don't work there, so refuse to compile.
12075 o Build fixes (compile/link):
12076 - Format more doubles with %f, not %lf. Patch from grarpamp to make
12077 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
12079 - When building with --enable-static-tor on OpenBSD, do not
12080 erroneously attempt to link -lrt. Fixes bug 5103.
12081 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
12082 that IPv6 stuff will compile on MSVC, and compilation issues
12083 will be easier to track down. Fixes bug 5861.
12084 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
12085 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
12086 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
12087 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
12089 o Build fixes (other):
12090 - Use the _WIN32 macro throughout our code to detect Windows.
12091 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
12093 - Properly handle the case where the build-tree is not the same
12094 as the source tree when generating src/common/common_sha1.i,
12095 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
12096 bugfix on 0.2.0.1-alpha.
12097 - During configure, search for library containing cos function as
12098 libm lives in libcore on some platforms (BeOS/Haiku). Linking
12099 against libm was hard-coded before. Fixes the first part of bug
12100 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
12102 - Prevent a false positive from the check-spaces script, by disabling
12103 the "whitespace between function name and (" check for functions
12106 o Packaging (RPM) changes:
12107 - Update our default RPM spec files to work with mock and rpmbuild
12108 on RHEL/Fedora. They have an updated set of dependencies and
12109 conflicts, a fix for an ancient typo when creating the "_tor"
12110 user, and better instructions. Thanks to Ondrej Mikle for the
12111 patch series. Fixes bug 6043.
12112 - On OpenSUSE, create the /var/run/tor directory on startup if it
12113 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
12115 o Code refactoring (safety):
12116 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
12117 10 lines. Also, don't nest them. Doing so in the past has
12118 led to hard-to-debug code. The new style is to use the
12119 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
12120 - Use macros to indicate OpenSSL versions, so we don't need to worry
12121 about accidental hexadecimal bit shifts.
12122 - Use tor_sscanf() in place of scanf() in more places through the
12123 code. This makes us a little more locale-independent, and
12124 should help shut up code-analysis tools that can't tell
12125 a safe sscanf string from a dangerous one.
12126 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
12127 - Use the smartlist_add_asprintf() alias more consistently.
12129 o Code refactoring (consolidate):
12130 - A major revision to our internal node-selecting and listing logic.
12131 Tor already had at least two major ways to look at the question of
12132 "which Tor servers do we know about": a list of router descriptors,
12133 and a list of entries in the current consensus. With
12134 microdescriptors, we're adding a third. Having so many systems
12135 without an abstraction layer over them was hurting the codebase.
12136 Now, we have a new "node_t" abstraction that presents a consistent
12137 interface to a client's view of a Tor node, and holds (nearly) all
12138 of the mutable state formerly in routerinfo_t and routerstatus_t.
12139 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
12140 Libevent's notion of cached time when possible.
12141 - Remove duplicate code for invoking getrlimit() from control.c.
12142 - Use OpenSSL's built-in SSL_state_string_long() instead of our
12143 own homebrewed ssl_state_to_string() replacement. Patch from
12144 Emile Snyder. Fixes bug 4653.
12145 - Change the symmetric cipher interface so that creating and
12146 initializing a stream cipher are no longer separate functions.
12148 o Code refactoring (separate):
12149 - Make a new "entry connection" struct as an internal subtype of "edge
12150 connection", to simplify the code and make exit connections smaller.
12151 - Split connection_about_to_close() into separate functions for each
12153 - Rewrite the listener-selection logic so that parsing which ports
12154 we want to listen on is now separate from binding to the ports
12157 o Code refactoring (name changes):
12158 - Rename a handful of old identifiers, mostly related to crypto
12159 structures and crypto functions. By convention, our "create an
12160 object" functions are called "type_new()", our "free an object"
12161 functions are called "type_free()", and our types indicate that
12162 they are types only with a final "_t". But a handful of older
12163 types and functions broke these rules, with function names like
12164 "type_create" or "subsystem_op_type", or with type names like
12166 - Rename Tor functions that turn strings into addresses, so that
12167 "parse" indicates that no hostname resolution occurs, and
12168 "lookup" indicates that hostname resolution may occur. This
12169 should help prevent mistakes in the future. Fixes bug 3512.
12170 - Use the name "CERTS" consistently to refer to the new cell type;
12171 we were calling it CERT in some places and CERTS in others.
12172 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
12173 invalid value, rather than just -1.
12174 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
12175 can pick them up when the tests aren't disabled. Bugfix on
12176 0.2.2.4-alpha which introduced tinytest.
12178 o Code refactoring (other):
12179 - Defensively refactor rend_mid_rendezvous() so that protocol
12180 violations and length checks happen in the beginning. Fixes
12182 - Remove the pure attribute from all functions that used it
12183 previously. In many cases we assigned it incorrectly, because the
12184 functions might assert or call impure functions, and we don't have
12185 evidence that keeping the pure attribute is worthwhile. Implements
12186 changes suggested in ticket 4421.
12187 - Move the replay-detection cache for the RSA-encrypted parts of
12188 INTRODUCE2 cells to the introduction point data structures.
12189 Previously, we would use one replay-detection cache per hidden
12190 service. Required by fix for bug 3460.
12191 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
12192 no longer link against Libevent: they never used it, but
12193 our library structure used to force them to link it.
12195 o Removed features and files:
12196 - Remove all internal support for unpadded RSA. We never used it, and
12197 it would be a bad idea to start.
12198 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
12200 - Remove some redundant #include directives throughout the code.
12201 Patch from Andrea Gelmini.
12202 - Remove some old code to remember statistics about which descriptors
12203 we've served as a directory mirror. The feature wasn't used and
12204 is outdated now that microdescriptors are around.
12205 - Remove some old code to work around even older versions of Tor that
12206 used forked processes to handle DNS requests. Such versions of Tor
12207 are no longer in use as relays.
12208 - The "torify" script no longer supports the "tsocks" socksifier
12209 tool, since tsocks doesn't support DNS and UDP right for Tor.
12210 Everyone should be using torsocks instead. Fixes bugs 3530 and
12211 5180. Based on a patch by "ugh".
12212 - Remove the torrc.bridge file: we don't use it for anything, and
12213 it had become badly desynchronized from torrc.sample. Resolves
12217 - Begin a doc/state-contents.txt file to explain the contents of
12218 the Tor state file. Fixes bug 2987.
12219 - Clarify the documentation for the Alternate*Authority options.
12221 - Document the --defaults-torrc option, and the new semantics for
12222 overriding, extending, and clearing lists of options. Closes
12224 - Add missing man page documentation for consensus and microdesc
12225 files. Resolves ticket 6732.
12226 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
12228 o Documentation fixes:
12229 - Improve the manual's documentation for the NT Service command-line
12230 options. Addresses ticket 3964.
12231 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
12232 - Document the changes to the ORPort and DirPort options, and the
12233 fact that {OR/Dir}ListenAddress is now unnecessary (and
12234 therefore deprecated). Resolves ticket 5597.
12235 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
12236 - Clarify that hidden services are TCP only. Fixes bug 6024.
12239 Changes in version 0.2.2.39 - 2012-09-11
12240 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
12244 - Fix an assertion failure in tor_timegm() that could be triggered
12245 by a badly formatted directory object. Bug found by fuzzing with
12246 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
12247 - Do not crash when comparing an address with port value 0 to an
12248 address policy. This bug could have been used to cause a remote
12249 assertion failure by or against directory authorities, or to
12250 allow some applications to crash clients. Fixes bug 6690; bugfix
12254 Changes in version 0.2.2.38 - 2012-08-12
12255 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
12256 attack that could in theory leak path information.
12259 - Avoid an uninitialized memory read when reading a vote or consensus
12260 document that has an unrecognized flavor name. This read could
12261 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
12262 - Try to leak less information about what relays a client is
12263 choosing to a side-channel attacker. Previously, a Tor client would
12264 stop iterating through the list of available relays as soon as it
12265 had chosen one, thus finishing a little earlier when it picked
12266 a router earlier in the list. If an attacker can recover this
12267 timing information (nontrivial but not proven to be impossible),
12268 they could learn some coarse-grained information about which relays
12269 a client was picking (middle nodes in particular are likelier to
12270 be affected than exits). The timing attack might be mitigated by
12271 other factors (see bug 6537 for some discussion), but it's best
12272 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
12275 Changes in version 0.2.2.37 - 2012-06-06
12276 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
12277 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
12281 - Work around a bug in OpenSSL that broke renegotiation with TLS
12282 1.1 and TLS 1.2. Without this workaround, all attempts to speak
12283 the v2 Tor connection protocol when both sides were using OpenSSL
12284 1.0.1 would fail. Resolves ticket 6033.
12285 - When waiting for a client to renegotiate, don't allow it to add
12286 any bytes to the input buffer. This fixes a potential DoS issue.
12287 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
12288 - Fix an edge case where if we fetch or publish a hidden service
12289 descriptor, we might build a 4-hop circuit and then use that circuit
12290 for exiting afterwards -- even if the new last hop doesn't obey our
12291 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
12294 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
12295 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
12298 - Tell GCC and Clang to check for any errors in format strings passed
12299 to the tor_v*(print|scan)f functions.
12302 Changes in version 0.2.2.36 - 2012-05-24
12303 Tor 0.2.2.36 updates the addresses for two of the eight directory
12304 authorities, fixes some potential anonymity and security issues,
12305 and fixes several crash bugs.
12307 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
12308 known flaws, and nobody should be using them. You should upgrade. If
12309 you're using a Linux or BSD and its packages are obsolete, stop using
12310 those packages and upgrade anyway.
12312 o Directory authority changes:
12313 - Change IP address for maatuska (v3 directory authority).
12314 - Change IP address for ides (v3 directory authority), and rename
12318 - When building or running with any version of OpenSSL earlier
12319 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
12320 versions have a bug (CVE-2011-4576) in which their block cipher
12321 padding includes uninitialized data, potentially leaking sensitive
12322 information to any peer with whom they make a SSLv3 connection. Tor
12323 does not use SSL v3 by default, but a hostile client or server
12324 could force an SSLv3 connection in order to gain information that
12325 they shouldn't have been able to get. The best solution here is to
12326 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
12327 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
12328 to make sure that the bug can't happen.
12329 - Never use a bridge or a controller-supplied node as an exit, even
12330 if its exit policy allows it. Found by wanoskarnet. Fixes bug
12331 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
12332 and 0.2.0.3-alpha (for bridge-purpose descriptors).
12333 - Only build circuits if we have a sufficient threshold of the total
12334 descriptors that are marked in the consensus with the "Exit"
12335 flag. This mitigates an attack proposed by wanoskarnet, in which
12336 all of a client's bridges collude to restrict the exit nodes that
12337 the client knows about. Fixes bug 5343.
12338 - Provide controllers with a safer way to implement the cookie
12339 authentication mechanism. With the old method, if another locally
12340 running program could convince a controller that it was the Tor
12341 process, then that program could trick the controller into telling
12342 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
12343 authentication method uses a challenge-response approach to prevent
12344 this attack. Fixes bug 5185; implements proposal 193.
12347 - Avoid logging uninitialized data when unable to decode a hidden
12348 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
12349 - Avoid a client-side assertion failure when receiving an INTRODUCE2
12350 cell on a general purpose circuit. Fixes bug 5644; bugfix on
12352 - Fix builds when the path to sed, openssl, or sha1sum contains
12353 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
12355 - Correct our replacements for the timeradd() and timersub() functions
12356 on platforms that lack them (for example, Windows). The timersub()
12357 function is used when expiring circuits, while timeradd() is
12358 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
12359 bugfix on 0.2.2.24-alpha.
12360 - Fix the SOCKET_OK test that we use to tell when socket
12361 creation fails so that it works on Win64. Fixes part of bug 4533;
12362 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
12365 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
12366 Fixes bug 5346; bugfix on 0.0.8pre3.
12367 - Make our number-parsing functions always treat too-large values
12368 as an error, even when those values exceed the width of the
12369 underlying type. Previously, if the caller provided these
12370 functions with minima or maxima set to the extreme values of the
12371 underlying integer type, these functions would return those
12372 values on overflow rather than treating overflow as an error.
12373 Fixes part of bug 5786; bugfix on 0.0.9.
12374 - Older Linux kernels erroneously respond to strange nmap behavior
12375 by having accept() return successfully with a zero-length
12376 socket. When this happens, just close the connection. Previously,
12377 we would try harder to learn the remote address: but there was
12378 no such remote address to learn, and our method for trying to
12379 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
12380 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
12381 - Correct parsing of certain date types in parse_http_time().
12382 Without this patch, If-Modified-Since would behave
12383 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
12384 Esteban Manchado Velázques.
12385 - Change the BridgePassword feature (part of the "bridge community"
12386 design, which is not yet implemented) to use a time-independent
12387 comparison. The old behavior might have allowed an adversary
12388 to use timing to guess the BridgePassword value. Fixes bug 5543;
12389 bugfix on 0.2.0.14-alpha.
12390 - Detect and reject certain misformed escape sequences in
12391 configuration values. Previously, these values would cause us
12392 to crash if received in a torrc file or over an authenticated
12393 control port. Bug found by Esteban Manchado Velázquez, and
12394 independently by Robert Connolly from Matta Consulting who further
12395 noted that it allows a post-authentication heap overflow. Patch
12396 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
12397 bugfix on 0.2.0.16-alpha.
12398 - Fix a compile warning when using the --enable-openbsd-malloc
12399 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
12400 - During configure, detect when we're building with clang version
12401 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
12402 CFLAGS. clang doesn't support them yet.
12403 - When sending an HTTP/1.1 proxy request, include a Host header.
12404 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
12405 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
12406 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
12407 - If we hit the error case where routerlist_insert() replaces an
12408 existing (old) server descriptor, make sure to remove that
12409 server descriptor from the old_routers list. Fix related to bug
12410 1776. Bugfix on 0.2.2.18-alpha.
12412 o Minor bugfixes (documentation and log messages):
12413 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
12414 Fixes bug 4856; bugfix on Tor 0.0.6.
12415 - Update "ClientOnly" man page entry to explain that there isn't
12416 really any point to messing with it. Resolves ticket 5005.
12417 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
12418 directory authority option (introduced in Tor 0.2.2.34).
12419 - Downgrade the "We're missing a certificate" message from notice
12420 to info: people kept mistaking it for a real problem, whereas it
12421 is seldom the problem even when we are failing to bootstrap. Fixes
12422 bug 5067; bugfix on 0.2.0.10-alpha.
12423 - Correctly spell "connect" in a log message on failure to create a
12424 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
12425 - Clarify the behavior of MaxCircuitDirtiness with hidden service
12426 circuits. Fixes issue 5259.
12429 - Directory authorities now reject versions of Tor older than
12430 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
12431 inclusive. These versions accounted for only a small fraction of
12432 the Tor network, and have numerous known security issues. Resolves
12434 - Update to the May 1 2012 Maxmind GeoLite Country database.
12437 - When sending or relaying a RELAY_EARLY cell, we used to convert
12438 it to a RELAY cell if the connection was using the v1 link
12439 protocol. This was a workaround for older versions of Tor, which
12440 didn't handle RELAY_EARLY cells properly. Now that all supported
12441 versions can handle RELAY_EARLY cells, and now that we're enforcing
12442 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
12443 remove this workaround. Addresses bug 4786.
12446 Changes in version 0.2.2.35 - 2011-12-16
12447 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
12448 buffers code. Absolutely everybody should upgrade.
12450 The bug relied on an incorrect calculation when making data continuous
12451 in one of our IO buffers, if the first chunk of the buffer was
12452 misaligned by just the wrong amount. The miscalculation would allow an
12453 attacker to overflow a piece of heap-allocated memory. To mount this
12454 attack, the attacker would need to either open a SOCKS connection to
12455 Tor's SocksPort (usually restricted to localhost), or target a Tor
12456 instance configured to make its connections through a SOCKS proxy
12457 (which Tor does not do by default).
12459 Good security practice requires that all heap-overflow bugs should be
12460 presumed to be exploitable until proven otherwise, so we are treating
12461 this as a potential code execution attack. Please upgrade immediately!
12462 This bug does not affect bufferevents-based builds of Tor. Special
12463 thanks to "Vektor" for reporting this issue to us!
12465 Tor 0.2.2.35 also fixes several bugs in previous versions, including
12466 crash bugs for unusual configurations, and a long-term bug that
12467 would prevent Tor from starting on Windows machines with draconian
12470 With this release, we remind everyone that 0.2.0.x has reached its
12471 formal end-of-life. Those Tor versions have many known flaws, and
12472 nobody should be using them. You should upgrade -- ideally to the
12473 0.2.2.x series. If you're using a Linux or BSD and its packages are
12474 obsolete, stop using those packages and upgrade anyway.
12476 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
12477 longer receive support after some time in early 2012.
12480 - Fix a heap overflow bug that could occur when trying to pull
12481 data into the first chunk of a buffer, when that chunk had
12482 already had some data drained from it. Fixes CVE-2011-2778;
12483 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
12484 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
12485 that it doesn't attempt to allocate a socketpair. This could cause
12486 some problems on Windows systems with overzealous firewalls. Fix for
12487 bug 4457; workaround for Libevent versions 2.0.1-alpha through
12489 - If we mark an OR connection for close based on a cell we process,
12490 don't process any further cells on it. We already avoid further
12491 reads on marked-for-close connections, but now we also discard the
12492 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
12493 which was the first version where we might mark a connection for
12494 close based on processing a cell on it.
12495 - Correctly sanity-check that we don't underflow on a memory
12496 allocation (and then assert) for hidden service introduction
12497 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
12498 bugfix on 0.2.1.5-alpha.
12499 - Fix a memory leak when we check whether a hidden service
12500 descriptor has any usable introduction points left. Fixes bug
12501 4424. Bugfix on 0.2.2.25-alpha.
12502 - Don't crash when we're running as a relay and don't have a GeoIP
12503 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
12504 we've had in the 0.2.3.x branch already.
12505 - When running as a client, do not print a misleading (and plain
12506 wrong) log message that we're collecting "directory request"
12507 statistics: clients don't collect statistics. Also don't create a
12508 useless (because empty) stats file in the stats/ directory. Fixes
12509 bug 4353; bugfix on 0.2.2.34.
12512 - Detect failure to initialize Libevent. This fix provides better
12513 detection for future instances of bug 4457.
12514 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
12515 function. This was eating up hideously large amounts of time on some
12516 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
12517 - Resolve an integer overflow bug in smartlist_ensure_capacity().
12518 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
12520 - Don't warn about unused log_mutex in log.c when building with
12521 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
12522 0.1.0.6-rc which introduced --disable-threads.
12523 - When configuring, starting, or stopping an NT service, stop
12524 immediately after the service configuration attempt has succeeded
12525 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
12526 - When sending a NETINFO cell, include the original address
12527 received for the other side, not its canonical address. Found
12528 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
12529 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
12530 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
12531 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
12532 occurred when a client tried to fetch a descriptor for a bridge
12533 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
12534 - Backport fixes for a pair of compilation warnings on Windows.
12535 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
12536 - If we had ever tried to call tor_addr_to_str on an address of
12537 unknown type, we would have done a strdup on an uninitialized
12538 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
12539 Reported by "troll_un".
12540 - Correctly detect and handle transient lookup failures from
12541 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
12542 Reported by "troll_un".
12543 - Fix null-pointer access that could occur if TLS allocation failed.
12544 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
12545 - Use tor_socket_t type for listener argument to accept(). Fixes bug
12546 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
12549 - Add two new config options for directory authorities:
12550 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
12551 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
12552 that is always sufficient to satisfy the bandwidth requirement for
12553 the Guard flag. Now it will be easier for researchers to simulate
12554 Tor networks with different values. Resolves ticket 4484.
12555 - When Tor ignores a hidden service specified in its configuration,
12556 include the hidden service's directory in the warning message.
12557 Previously, we would only tell the user that some hidden service
12558 was ignored. Bugfix on 0.0.6; fixes bug 4426.
12559 - Update to the December 6 2011 Maxmind GeoLite Country database.
12561 o Packaging changes:
12562 - Make it easier to automate expert package builds on Windows,
12563 by removing an absolute path from makensis.exe command.
12566 Changes in version 0.2.1.32 - 2011-12-16
12567 Tor 0.2.1.32 backports important security and privacy fixes for
12568 oldstable. This release is intended only for package maintainers and
12569 others who cannot use the 0.2.2 stable series. All others should be
12570 using Tor 0.2.2.x or newer.
12572 The Tor 0.2.1.x series will reach formal end-of-life some time in
12573 early 2012; we will stop releasing patches for it then.
12575 o Major bugfixes (also included in 0.2.2.x):
12576 - Correctly sanity-check that we don't underflow on a memory
12577 allocation (and then assert) for hidden service introduction
12578 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
12579 bugfix on 0.2.1.5-alpha.
12580 - Fix a heap overflow bug that could occur when trying to pull
12581 data into the first chunk of a buffer, when that chunk had
12582 already had some data drained from it. Fixes CVE-2011-2778;
12583 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
12586 - Update to the December 6 2011 Maxmind GeoLite Country database.
12589 Changes in version 0.2.2.34 - 2011-10-26
12590 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
12591 can deanonymize Tor users. Everybody should upgrade.
12593 The attack relies on four components: 1) Clients reuse their TLS cert
12594 when talking to different relays, so relays can recognize a user by
12595 the identity key in her cert. 2) An attacker who knows the client's
12596 identity key can probe each guard relay to see if that identity key
12597 is connected to that guard relay right now. 3) A variety of active
12598 attacks in the literature (starting from "Low-Cost Traffic Analysis
12599 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
12600 discover the guard relays that a Tor user visiting the website is using.
12601 4) Clients typically pick three guards at random, so the set of guards
12602 for a given user could well be a unique fingerprint for her. This
12603 release fixes components #1 and #2, which is enough to block the attack;
12604 the other two remain as open research problems. Special thanks to
12605 "frosty_un" for reporting the issue to us!
12607 Clients should upgrade so they are no longer recognizable by the TLS
12608 certs they present. Relays should upgrade so they no longer allow a
12609 remote attacker to probe them to test whether unpatched clients are
12610 currently connected to them.
12612 This release also fixes several vulnerabilities that allow an attacker
12613 to enumerate bridge relays. Some bridge enumeration attacks still
12614 remain; see for example proposal 188.
12616 o Privacy/anonymity fixes (clients):
12617 - Clients and bridges no longer send TLS certificate chains on
12618 outgoing OR connections. Previously, each client or bridge would
12619 use the same cert chain for all outgoing OR connections until
12620 its IP address changes, which allowed any relay that the client
12621 or bridge contacted to determine which entry guards it is using.
12622 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
12623 - If a relay receives a CREATE_FAST cell on a TLS connection, it
12624 no longer considers that connection as suitable for satisfying a
12625 circuit EXTEND request. Now relays can protect clients from the
12626 CVE-2011-2768 issue even if the clients haven't upgraded yet.
12627 - Directory authorities no longer assign the Guard flag to relays
12628 that haven't upgraded to the above "refuse EXTEND requests
12629 to client connections" fix. Now directory authorities can
12630 protect clients from the CVE-2011-2768 issue even if neither
12631 the clients nor the relays have upgraded yet. There's a new
12632 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
12633 to let us transition smoothly, else tomorrow there would be no
12636 o Privacy/anonymity fixes (bridge enumeration):
12637 - Bridge relays now do their directory fetches inside Tor TLS
12638 connections, like all the other clients do, rather than connecting
12639 directly to the DirPort like public relays do. Removes another
12640 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
12641 - Bridges relays now build circuits for themselves in a more similar
12642 way to how clients build them. Removes another avenue for
12643 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
12644 when bridges were introduced.
12645 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
12646 that they initiated. Relays could distinguish incoming bridge
12647 connections from client connections, creating another avenue for
12648 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
12649 Found by "frosty_un".
12652 - Fix a crash bug when changing node restrictions while a DNS lookup
12653 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
12655 - Don't launch a useless circuit after failing to use one of a
12656 hidden service's introduction points. Previously, we would
12657 launch a new introduction circuit, but not set the hidden service
12658 which that circuit was intended to connect to, so it would never
12659 actually be used. A different piece of code would then create a
12660 new introduction circuit correctly. Bug reported by katmagic and
12661 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
12664 - Change an integer overflow check in the OpenBSD_Malloc code so
12665 that GCC is less likely to eliminate it as impossible. Patch
12666 from Mansour Moufid. Fixes bug 4059.
12667 - When a hidden service turns an extra service-side introduction
12668 circuit into a general-purpose circuit, free the rend_data and
12669 intro_key fields first, so we won't leak memory if the circuit
12670 is cannibalized for use as another service-side introduction
12671 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
12672 - Bridges now skip DNS self-tests, to act a little more stealthily.
12673 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
12674 bridges. Patch by "warms0x".
12675 - Fix internal bug-checking logic that was supposed to catch
12676 failures in digest generation so that it will fail more robustly
12677 if we ask for a nonexistent algorithm. Found by Coverity Scan.
12678 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
12679 - Report any failure in init_keys() calls launched because our
12680 IP address has changed. Spotted by Coverity Scan. Bugfix on
12681 0.1.1.4-alpha; fixes CID 484.
12683 o Minor bugfixes (log messages and documentation):
12684 - Remove a confusing dollar sign from the example fingerprint in the
12685 man page, and also make the example fingerprint a valid one. Fixes
12686 bug 4309; bugfix on 0.2.1.3-alpha.
12687 - The next version of Windows will be called Windows 8, and it has
12688 a major version of 6, minor version of 2. Correctly identify that
12689 version instead of calling it "Very recent version". Resolves
12690 ticket 4153; reported by funkstar.
12691 - Downgrade log messages about circuit timeout calibration from
12692 "notice" to "info": they don't require or suggest any human
12693 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
12694 bugfix on 0.2.2.14-alpha.
12697 - Turn on directory request statistics by default and include them in
12698 extra-info descriptors. Don't break if we have no GeoIP database.
12699 Backported from 0.2.3.1-alpha; implements ticket 3951.
12700 - Update to the October 4 2011 Maxmind GeoLite Country database.
12703 Changes in version 0.2.1.31 - 2011-10-26
12704 Tor 0.2.1.31 backports important security and privacy fixes for
12705 oldstable. This release is intended only for package maintainers and
12706 others who cannot use the 0.2.2 stable series. All others should be
12707 using Tor 0.2.2.x or newer.
12709 o Security fixes (also included in 0.2.2.x):
12710 - Replace all potentially sensitive memory comparison operations
12711 with versions whose runtime does not depend on the data being
12712 compared. This will help resist a class of attacks where an
12713 adversary can use variations in timing information to learn
12714 sensitive data. Fix for one case of bug 3122. (Safe memcmp
12715 implementation by Robert Ransom based partially on code by DJB.)
12716 - Fix an assert in parsing router descriptors containing IPv6
12717 addresses. This one took down the directory authorities when
12718 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
12720 o Privacy/anonymity fixes (also included in 0.2.2.x):
12721 - Clients and bridges no longer send TLS certificate chains on
12722 outgoing OR connections. Previously, each client or bridge would
12723 use the same cert chain for all outgoing OR connections until
12724 its IP address changes, which allowed any relay that the client
12725 or bridge contacted to determine which entry guards it is using.
12726 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
12727 - If a relay receives a CREATE_FAST cell on a TLS connection, it
12728 no longer considers that connection as suitable for satisfying a
12729 circuit EXTEND request. Now relays can protect clients from the
12730 CVE-2011-2768 issue even if the clients haven't upgraded yet.
12731 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
12732 that they initiated. Relays could distinguish incoming bridge
12733 connections from client connections, creating another avenue for
12734 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
12735 Found by "frosty_un".
12736 - When receiving a hidden service descriptor, check that it is for
12737 the hidden service we wanted. Previously, Tor would store any
12738 hidden service descriptors that a directory gave it, whether it
12739 wanted them or not. This wouldn't have let an attacker impersonate
12740 a hidden service, but it did let directories pre-seed a client
12741 with descriptors that it didn't want. Bugfix on 0.0.6.
12742 - Avoid linkability based on cached hidden service descriptors: forget
12743 all hidden service descriptors cached as a client when processing a
12744 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
12745 - Make the bridge directory authority refuse to answer directory
12746 requests for "all" descriptors. It used to include bridge
12747 descriptors in its answer, which was a major information leak.
12748 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
12749 - Don't attach new streams to old rendezvous circuits after SIGNAL
12750 NEWNYM. Previously, we would keep using an existing rendezvous
12751 circuit if it remained open (i.e. if it were kept open by a
12752 long-lived stream, or if a new stream were attached to it before
12753 Tor could notice that it was old and no longer in use). Bugfix on
12754 0.1.1.15-rc; fixes bug 3375.
12756 o Minor bugfixes (also included in 0.2.2.x):
12757 - When we restart our relay, we might get a successful connection
12758 from the outside before we've started our reachability tests,
12759 triggering a warning: "ORPort found reachable, but I have no
12760 routerinfo yet. Failing to inform controller of success." This
12761 bug was harmless unless Tor is running under a controller
12762 like Vidalia, in which case the controller would never get a
12763 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
12765 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
12766 enabled. Fixes bug 1526.
12767 - Remove undocumented option "-F" from tor-resolve: it hasn't done
12768 anything since 0.2.1.16-rc.
12769 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
12770 None of the cases where we did this before were wrong, but by making
12771 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
12772 - Fix a rare crash bug that could occur when a client was configured
12773 with a large number of bridges. Fixes bug 2629; bugfix on
12774 0.2.1.2-alpha. Bugfix by trac user "shitlei".
12775 - Correct the warning displayed when a rendezvous descriptor exceeds
12776 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
12778 - Fix an uncommon assertion failure when running with DNSPort under
12779 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
12780 - When warning about missing zlib development packages during compile,
12781 give the correct package names. Bugfix on 0.2.0.1-alpha.
12782 - Require that introduction point keys and onion keys have public
12783 exponent 65537. Bugfix on 0.2.0.10-alpha.
12784 - Do not crash when our configuration file becomes unreadable, for
12785 example due to a permissions change, between when we start up
12786 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
12788 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
12790 - Always NUL-terminate the sun_path field of a sockaddr_un before
12791 passing it to the kernel. (Not a security issue: kernels are
12792 smart enough to reject bad sockaddr_uns.) Found by Coverity;
12793 CID #428. Bugfix on Tor 0.2.0.3-alpha.
12794 - Don't stack-allocate the list of supplementary GIDs when we're
12795 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
12796 could take up to 256K, which is way too much stack. Found by
12797 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
12799 o Minor bugfixes (only in 0.2.1.x):
12800 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
12801 rely on them. Bugfix on 0.2.1.30.
12802 - Use git revisions instead of svn revisions when generating our
12803 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
12805 o Minor features (also included in 0.2.2.x):
12806 - Adjust the expiration time on our SSL session certificates to
12807 better match SSL certs seen in the wild. Resolves ticket 4014.
12808 - Allow nameservers with IPv6 address. Resolves bug 2574.
12809 - Update to the October 4 2011 Maxmind GeoLite Country database.
12812 Changes in version 0.2.2.33 - 2011-09-13
12813 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
12814 TLS handshake that makes relays and bridges that run this new version
12815 reachable from Iran again.
12818 - Avoid an assertion failure when reloading a configuration with
12819 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
12820 3923; bugfix on 0.2.2.25-alpha.
12822 o Minor features (security):
12823 - Check for replays of the public-key encrypted portion of an
12824 INTRODUCE1 cell, in addition to the current check for replays of
12825 the g^x value. This prevents a possible class of active attacks
12826 by an attacker who controls both an introduction point and a
12827 rendezvous point, and who uses the malleability of AES-CTR to
12828 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
12829 that these attacks are infeasible (requiring the attacker to send
12830 on the order of zettabytes of altered cells in a short interval),
12831 but we'd rather block them off in case there are any classes of
12832 this attack that we missed. Reported by Willem Pinckaers.
12835 - Adjust the expiration time on our SSL session certificates to
12836 better match SSL certs seen in the wild. Resolves ticket 4014.
12837 - Change the default required uptime for a relay to be accepted as
12838 a HSDir (hidden service directory) from 24 hours to 25 hours.
12839 Improves on 0.2.0.10-alpha; resolves ticket 2649.
12840 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
12841 authorities to abstain from voting on assignment of the HSDir
12842 consensus flag. Related to bug 2649.
12843 - Update to the September 6 2011 Maxmind GeoLite Country database.
12845 o Minor bugfixes (documentation and log messages):
12846 - Correct the man page to explain that HashedControlPassword and
12847 CookieAuthentication can both be set, in which case either method
12848 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
12849 when we decided to allow these config options to both be set. Issue
12850 raised by bug 3898.
12851 - Demote the 'replay detected' log message emitted when a hidden
12852 service receives the same Diffie-Hellman public key in two different
12853 INTRODUCE2 cells to info level. A normal Tor client can cause that
12854 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
12855 fixes part of bug 2442.
12856 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
12857 level. There is nothing that a hidden service's operator can do
12858 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
12860 - Clarify a log message specifying the characters permitted in
12861 HiddenServiceAuthorizeClient client names. Previously, the log
12862 message said that "[A-Za-z0-9+-_]" were permitted; that could have
12863 given the impression that every ASCII character between "+" and "_"
12864 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
12867 - Provide a substitute implementation of lround() for MSVC, which
12868 apparently lacks it. Patch from Gisle Vanem.
12869 - Clean up some code issues that prevented Tor from building on older
12870 BSDs. Fixes bug 3894; reported by "grarpamp".
12871 - Search for a platform-specific version of "ar" when cross-compiling.
12872 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
12875 Changes in version 0.2.2.32 - 2011-08-27
12876 The Tor 0.2.2 release series is dedicated to the memory of Andreas
12877 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
12878 a founder of the PETS community, a leader in our field, a mentor,
12879 and a friend. He left us with these words: "I had the possibility
12880 to contribute to this world that is not as it should be. I hope I
12881 could help in some areas to make the world a better place, and that
12882 I could also encourage other people to be engaged in improving the
12883 world. Please, stay engaged. This world needs you, your love, your
12884 initiative -- now I cannot be part of that anymore."
12886 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
12887 ready. More than two years in the making, this release features improved
12888 client performance and hidden service reliability, better compatibility
12889 for Android, correct behavior for bridges that listen on more than
12890 one address, more extensible and flexible directory object handling,
12891 better reporting of network statistics, improved code security, and
12892 many many other features and bugfixes.
12894 o Major features (client performance):
12895 - When choosing which cells to relay first, relays now favor circuits
12896 that have been quiet recently, to provide lower latency for
12897 low-volume circuits. By default, relays enable or disable this
12898 feature based on a setting in the consensus. They can override
12899 this default by using the new "CircuitPriorityHalflife" config
12900 option. Design and code by Ian Goldberg, Can Tang, and Chris
12902 - Directory authorities now compute consensus weightings that instruct
12903 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
12904 and no flag. Clients use these weightings to distribute network load
12905 more evenly across these different relay types. The weightings are
12906 in the consensus so we can change them globally in the future. Extra
12907 thanks to "outofwords" for finding some nasty security bugs in
12908 the first implementation of this feature.
12910 o Major features (client performance, circuit build timeout):
12911 - Tor now tracks how long it takes to build client-side circuits
12912 over time, and adapts its timeout to local network performance.
12913 Since a circuit that takes a long time to build will also provide
12914 bad performance, we get significant latency improvements by
12915 discarding the slowest 20% of circuits. Specifically, Tor creates
12916 circuits more aggressively than usual until it has enough data
12917 points for a good timeout estimate. Implements proposal 151.
12918 - Circuit build timeout constants can be controlled by consensus
12919 parameters. We set good defaults for these parameters based on
12920 experimentation on broadband and simulated high-latency links.
12921 - Circuit build time learning can be disabled via consensus parameter
12922 or by the client via a LearnCircuitBuildTimeout config option. We
12923 also automatically disable circuit build time calculation if either
12924 AuthoritativeDirectory is set, or if we fail to write our state
12925 file. Implements ticket 1296.
12927 o Major features (relays use their capacity better):
12928 - Set SO_REUSEADDR socket option on all sockets, not just
12929 listeners. This should help busy exit nodes avoid running out of
12930 useable ports just because all the ports have been used in the
12931 near past. Resolves issue 2850.
12932 - Relays now save observed peak bandwidth throughput rates to their
12933 state file (along with total usage, which was already saved),
12934 so that they can determine their correct estimated bandwidth on
12935 restart. Resolves bug 1863, where Tor relays would reset their
12936 estimated bandwidth to 0 after restarting.
12937 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
12938 should give us approximately 40-50% more Guard-flagged nodes,
12939 improving the anonymity the Tor network can provide and also
12940 decreasing the dropoff in throughput that relays experience when
12941 they first get the Guard flag.
12942 - Directory authorities now take changes in router IP address and
12943 ORPort into account when determining router stability. Previously,
12944 if a router changed its IP or ORPort, the authorities would not
12945 treat it as having any downtime for the purposes of stability
12946 calculation, whereas clients would experience downtime since the
12947 change would take a while to propagate to them. Resolves issue 1035.
12948 - New AccelName and AccelDir options add support for dynamic OpenSSL
12949 hardware crypto acceleration engines.
12951 o Major features (relays control their load better):
12952 - Exit relays now try harder to block exit attempts from unknown
12953 relays, to make it harder for people to use them as one-hop proxies
12954 a la tortunnel. Controlled by the refuseunknownexits consensus
12955 parameter (currently enabled), or you can override it on your
12956 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
12957 based on a variant of proposal 163.
12958 - Add separate per-conn write limiting to go with the per-conn read
12959 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
12960 but never per-conn write limits.
12961 - New consensus params "bwconnrate" and "bwconnburst" to let us
12962 rate-limit client connections as they enter the network. It's
12963 controlled in the consensus so we can turn it on and off for
12964 experiments. It's starting out off. Based on proposal 163.
12966 o Major features (controllers):
12967 - Export GeoIP information on bridge usage to controllers even if we
12968 have not yet been running for 24 hours. Now Vidalia bridge operators
12969 can get more accurate and immediate feedback about their
12970 contributions to the network.
12971 - Add an __OwningControllerProcess configuration option and a
12972 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
12973 that when it exits, Tor will shut down. Implements feature 3049.
12975 o Major features (directory authorities):
12976 - Directory authorities now create, vote on, and serve multiple
12977 parallel formats of directory data as part of their voting process.
12978 Partially implements Proposal 162: "Publish the consensus in
12980 - Directory authorities now agree on and publish small summaries
12981 of router information that clients can use in place of regular
12982 server descriptors. This transition will allow Tor 0.2.3 clients
12983 to use far less bandwidth for downloading information about the
12984 network. Begins the implementation of Proposal 158: "Clients
12985 download consensus + microdescriptors".
12986 - The directory voting system is now extensible to use multiple hash
12987 algorithms for signatures and resource selection. Newer formats
12988 are signed with SHA256, with a possibility for moving to a better
12989 hash algorithm in the future.
12990 - Directory authorities can now vote on arbitrary integer values as
12991 part of the consensus process. This is designed to help set
12992 network-wide parameters. Implements proposal 167.
12994 o Major features and bugfixes (node selection):
12995 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
12996 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
12997 options. Previously, we had been ambiguous in describing what
12998 counted as an "exit" node, and what operations exactly "StrictNodes
12999 0" would permit. This created confusion when people saw nodes built
13000 through unexpected circuits, and made it hard to tell real bugs from
13001 surprises. Now the intended behavior is:
13002 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
13003 a node that delivers user traffic outside the Tor network.
13004 . "Entry", in the context of EntryNodes, means a node used as the
13005 first hop of a multihop circuit. It doesn't include direct
13006 connections to directory servers.
13007 . "ExcludeNodes" applies to all nodes.
13008 . "StrictNodes" changes the behavior of ExcludeNodes only. When
13009 StrictNodes is set, Tor should avoid all nodes listed in
13010 ExcludeNodes, even when it will make user requests fail. When
13011 StrictNodes is *not* set, then Tor should follow ExcludeNodes
13012 whenever it can, except when it must use an excluded node to
13013 perform self-tests, connect to a hidden service, provide a
13014 hidden service, fulfill a .exit request, upload directory
13015 information, or fetch directory information.
13016 Collectively, the changes to implement the behavior fix bug 1090.
13017 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
13018 change during a config reload, mark and discard all our origin
13019 circuits. This fix should address edge cases where we change the
13020 config options and but then choose a circuit that we created before
13022 - Make EntryNodes config option much more aggressive even when
13023 StrictNodes is not set. Before it would prepend your requested
13024 entrynodes to your list of guard nodes, but feel free to use others
13025 after that. Now it chooses only from your EntryNodes if any of
13026 those are available, and only falls back to others if a) they're
13027 all down and b) StrictNodes is not set.
13028 - Now we refresh your entry guards from EntryNodes at each consensus
13029 fetch -- rather than just at startup and then they slowly rot as
13030 the network changes.
13031 - Add support for the country code "{??}" in torrc options like
13032 ExcludeNodes, to indicate all routers of unknown country. Closes
13034 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
13035 a node is listed in both, it's treated as excluded.
13036 - ExcludeNodes now applies to directory nodes -- as a preference if
13037 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
13038 Don't exclude all the directory authorities and set StrictNodes to 1
13039 unless you really want your Tor to break.
13040 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
13041 - ExcludeExitNodes now overrides .exit requests.
13042 - We don't use bridges listed in ExcludeNodes.
13043 - When StrictNodes is 1:
13044 . We now apply ExcludeNodes to hidden service introduction points
13045 and to rendezvous points selected by hidden service users. This
13046 can make your hidden service less reliable: use it with caution!
13047 . If we have used ExcludeNodes on ourself, do not try relay
13048 reachability self-tests.
13049 . If we have excluded all the directory authorities, we will not
13050 even try to upload our descriptor if we're a relay.
13051 . Do not honor .exit requests to an excluded node.
13052 - When the set of permitted nodes changes, we now remove any mappings
13053 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
13055 - We never cannibalize a circuit that had excluded nodes on it, even
13056 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
13057 - Improve log messages related to excluded nodes.
13059 o Major features (misc):
13060 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
13061 to help Tor build correctly for Android phones.
13062 - The options SocksPort, ControlPort, and so on now all accept a
13063 value "auto" that opens a socket on an OS-selected port. A
13064 new ControlPortWriteToFile option tells Tor to write its
13065 actual control port or ports to a chosen file. If the option
13066 ControlPortFileGroupReadable is set, the file is created as
13067 group-readable. Now users can run two Tor clients on the same
13068 system without needing to manually mess with parameters. Resolves
13069 part of ticket 3076.
13070 - Tor now supports tunneling all of its outgoing connections over
13071 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
13072 configuration options. Code by Christopher Davis.
13074 o Code security improvements:
13075 - Replace all potentially sensitive memory comparison operations
13076 with versions whose runtime does not depend on the data being
13077 compared. This will help resist a class of attacks where an
13078 adversary can use variations in timing information to learn
13079 sensitive data. Fix for one case of bug 3122. (Safe memcmp
13080 implementation by Robert Ransom based partially on code by DJB.)
13081 - Enable Address Space Layout Randomization (ASLR) and Data Execution
13082 Prevention (DEP) by default on Windows to make it harder for
13083 attackers to exploit vulnerabilities. Patch from John Brooks.
13084 - New "--enable-gcc-hardening" ./configure flag (off by default)
13085 to turn on gcc compile time hardening options. It ensures
13086 that signed ints have defined behavior (-fwrapv), enables
13087 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
13088 with canaries (-fstack-protector-all), turns on ASLR protection if
13089 supported by the kernel (-fPIE, -pie), and adds additional security
13090 related warnings. Verified to work on Mac OS X and Debian Lenny.
13091 - New "--enable-linker-hardening" ./configure flag (off by default)
13092 to turn on ELF specific hardening features (relro, now). This does
13093 not work with Mac OS X or any other non-ELF binary format.
13094 - Always search the Windows system directory for system DLLs, and
13095 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
13096 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
13097 current and future memory pages via mlockall(). On supported
13098 platforms (modern Linux and probably BSD but not Windows or OS X),
13099 this should effectively disable any and all attempts to page out
13100 memory. This option requires that you start your Tor as root --
13101 if you use DisableAllSwap, please consider using the User option
13102 to properly reduce the privileges of your Tor.
13104 o Major bugfixes (crashes):
13105 - Fix crash bug on platforms where gmtime and localtime can return
13106 NULL. Windows 7 users were running into this one. Fixes part of bug
13107 2077. Bugfix on all versions of Tor. Found by boboper.
13108 - Introduce minimum/maximum values that clients will believe
13109 from the consensus. Now we'll have a better chance to avoid crashes
13110 or worse when a consensus param has a weird value.
13111 - Fix a rare crash bug that could occur when a client was configured
13112 with a large number of bridges. Fixes bug 2629; bugfix on
13113 0.2.1.2-alpha. Bugfix by trac user "shitlei".
13114 - Do not crash when our configuration file becomes unreadable, for
13115 example due to a permissions change, between when we start up
13116 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
13118 - If we're in the pathological case where there's no exit bandwidth
13119 but there is non-exit bandwidth, or no guard bandwidth but there
13120 is non-guard bandwidth, don't crash during path selection. Bugfix
13122 - Fix a crash bug when trying to initialize the evdns module in
13123 Libevent 2. Bugfix on 0.2.1.16-rc.
13125 o Major bugfixes (stability):
13126 - Fix an assert in parsing router descriptors containing IPv6
13127 addresses. This one took down the directory authorities when
13128 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
13129 - Fix an uncommon assertion failure when running with DNSPort under
13130 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
13131 - Treat an unset $HOME like an empty $HOME rather than triggering an
13132 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
13133 - More gracefully handle corrupt state files, removing asserts
13134 in favor of saving a backup and resetting state.
13135 - Instead of giving an assertion failure on an internal mismatch
13136 on estimated freelist size, just log a BUG warning and try later.
13137 Mitigates but does not fix bug 1125.
13138 - Fix an assert that got triggered when using the TestingTorNetwork
13139 configuration option and then issuing a GETINFO config-text control
13140 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
13141 - If the cached cert file is unparseable, warn but don't exit.
13143 o Privacy fixes (relays/bridges):
13144 - Don't list Windows capabilities in relay descriptors. We never made
13145 use of them, and maybe it's a bad idea to publish them. Bugfix
13147 - If the Nickname configuration option isn't given, Tor would pick a
13148 nickname based on the local hostname as the nickname for a relay.
13149 Because nicknames are not very important in today's Tor and the
13150 "Unnamed" nickname has been implemented, this is now problematic
13151 behavior: It leaks information about the hostname without being
13152 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
13153 introduced the Unnamed nickname. Reported by tagnaq.
13154 - Maintain separate TLS contexts and certificates for incoming and
13155 outgoing connections in bridge relays. Previously we would use the
13156 same TLS contexts and certs for incoming and outgoing connections.
13157 Bugfix on 0.2.0.3-alpha; addresses bug 988.
13158 - Maintain separate identity keys for incoming and outgoing TLS
13159 contexts in bridge relays. Previously we would use the same
13160 identity keys for incoming and outgoing TLS contexts. Bugfix on
13161 0.2.0.3-alpha; addresses the other half of bug 988.
13162 - Make the bridge directory authority refuse to answer directory
13163 requests for "all descriptors". It used to include bridge
13164 descriptors in its answer, which was a major information leak.
13165 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
13167 o Privacy fixes (clients):
13168 - When receiving a hidden service descriptor, check that it is for
13169 the hidden service we wanted. Previously, Tor would store any
13170 hidden service descriptors that a directory gave it, whether it
13171 wanted them or not. This wouldn't have let an attacker impersonate
13172 a hidden service, but it did let directories pre-seed a client
13173 with descriptors that it didn't want. Bugfix on 0.0.6.
13174 - Start the process of disabling ".exit" address notation, since it
13175 can be used for a variety of esoteric application-level attacks
13176 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
13178 - Reject attempts at the client side to open connections to private
13179 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
13180 a randomly chosen exit node. Attempts to do so are always
13181 ill-defined, generally prevented by exit policies, and usually
13182 in error. This will also help to detect loops in transparent
13183 proxy configurations. You can disable this feature by setting
13184 "ClientRejectInternalAddresses 0" in your torrc.
13185 - Log a notice when we get a new control connection. Now it's easier
13186 for security-conscious users to recognize when a local application
13187 is knocking on their controller door. Suggested by bug 1196.
13189 o Privacy fixes (newnym):
13190 - Avoid linkability based on cached hidden service descriptors: forget
13191 all hidden service descriptors cached as a client when processing a
13192 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
13193 - On SIGHUP, do not clear out all TrackHostExits mappings, client
13194 DNS cache entries, and virtual address mappings: that's what
13195 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
13196 - Don't attach new streams to old rendezvous circuits after SIGNAL
13197 NEWNYM. Previously, we would keep using an existing rendezvous
13198 circuit if it remained open (i.e. if it were kept open by a
13199 long-lived stream, or if a new stream were attached to it before
13200 Tor could notice that it was old and no longer in use). Bugfix on
13201 0.1.1.15-rc; fixes bug 3375.
13203 o Major bugfixes (relay bandwidth accounting):
13204 - Fix a bug that could break accounting on 64-bit systems with large
13205 time_t values, making them hibernate for impossibly long intervals.
13206 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
13207 - Fix a bug in bandwidth accounting that could make us use twice
13208 the intended bandwidth when our interval start changes due to
13209 daylight saving time. Now we tolerate skew in stored vs computed
13210 interval starts: if the start of the period changes by no more than
13211 50% of the period's duration, we remember bytes that we transferred
13212 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
13214 o Major bugfixes (bridges):
13215 - Bridges now use "reject *:*" as their default exit policy. Bugfix
13216 on 0.2.0.3-alpha. Fixes bug 1113.
13217 - If you configure your bridge with a known identity fingerprint,
13218 and the bridge authority is unreachable (as it is in at least
13219 one country now), fall back to directly requesting the descriptor
13220 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
13222 - Fix a bug where bridge users who configure the non-canonical
13223 address of a bridge automatically switch to its canonical
13224 address. If a bridge listens at more than one address, it
13225 should be able to advertise those addresses independently and
13226 any non-blocked addresses should continue to work. Bugfix on Tor
13227 0.2.0.3-alpha. Fixes bug 2510.
13228 - If you configure Tor to use bridge A, and then quit and
13229 configure Tor to use bridge B instead (or if you change Tor
13230 to use bridge B via the controller), it would happily continue
13231 to use bridge A if it's still reachable. While this behavior is
13232 a feature if your goal is connectivity, in some scenarios it's a
13233 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
13234 - When the controller configures a new bridge, don't wait 10 to 60
13235 seconds before trying to fetch its descriptor. Bugfix on
13236 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
13238 o Major bugfixes (directory authorities):
13239 - Many relays have been falling out of the consensus lately because
13240 not enough authorities know about their descriptor for them to get
13241 a majority of votes. When we deprecated the v2 directory protocol,
13242 we got rid of the only way that v3 authorities can hear from each
13243 other about other descriptors. Now authorities examine every v3
13244 vote for new descriptors, and fetch them from that authority. Bugfix
13246 - Authorities could be tricked into giving out the Exit flag to relays
13247 that didn't allow exiting to any ports. This bug could screw
13248 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
13249 1238. Bug discovered by Martin Kowalczyk.
13250 - If all authorities restart at once right before a consensus vote,
13251 nobody will vote about "Running", and clients will get a consensus
13252 with no usable relays. Instead, authorities refuse to build a
13253 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
13255 o Major bugfixes (stream-level fairness):
13256 - When receiving a circuit-level SENDME for a blocked circuit, try
13257 to package cells fairly from all the streams that had previously
13258 been blocked on that circuit. Previously, we had started with the
13259 oldest stream, and allowed each stream to potentially exhaust
13260 the circuit's package window. This gave older streams on any
13261 given circuit priority over newer ones. Fixes bug 1937. Detected
13262 originally by Camilo Viecco. This bug was introduced before the
13263 first Tor release, in svn commit r152: it is the new winner of
13264 the longest-lived bug prize.
13265 - Fix a stream fairness bug that would cause newer streams on a given
13266 circuit to get preference when reading bytes from the origin or
13267 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
13268 introduced before the first Tor release, in svn revision r152.
13269 - When the exit relay got a circuit-level sendme cell, it started
13270 reading on the exit streams, even if had 500 cells queued in the
13271 circuit queue already, so the circuit queue just grew and grew in
13272 some cases. We fix this by not re-enabling reading on receipt of a
13273 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
13274 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
13276 - Newly created streams were allowed to read cells onto circuits,
13277 even if the circuit's cell queue was blocked and waiting to drain.
13278 This created potential unfairness, as older streams would be
13279 blocked, but newer streams would gladly fill the queue completely.
13280 We add code to detect this situation and prevent any stream from
13281 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
13284 o Major bugfixes (hidden services):
13285 - Apply circuit timeouts to opened hidden-service-related circuits
13286 based on the correct start time. Previously, we would apply the
13287 circuit build timeout based on time since the circuit's creation;
13288 it was supposed to be applied based on time since the circuit
13289 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
13290 - Improve hidden service robustness: When we find that we have
13291 extended a hidden service's introduction circuit to a relay not
13292 listed as an introduction point in the HS descriptor we currently
13293 have, retry with an introduction point from the current
13294 descriptor. Previously we would just give up. Fixes bugs 1024 and
13295 1930; bugfix on 0.2.0.10-alpha.
13296 - Directory authorities now use data collected from their own
13297 uptime observations when choosing whether to assign the HSDir flag
13298 to relays, instead of trusting the uptime value the relay reports in
13299 its descriptor. This change helps prevent an attack where a small
13300 set of nodes with frequently-changing identity keys can blackhole
13301 a hidden service. (Only authorities need upgrade; others will be
13302 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
13303 - Stop assigning the HSDir flag to relays that disable their
13304 DirPort (and thus will refuse to answer directory requests). This
13305 fix should dramatically improve the reachability of hidden services:
13306 hidden services and hidden service clients pick six HSDir relays
13307 to store and retrieve the hidden service descriptor, and currently
13308 about half of the HSDir relays will refuse to work. Bugfix on
13309 0.2.0.10-alpha; fixes part of bug 1693.
13311 o Major bugfixes (misc):
13312 - Clients now stop trying to use an exit node associated with a given
13313 destination by TrackHostExits if they fail to reach that exit node.
13314 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
13315 - Fix a regression that caused Tor to rebind its ports if it receives
13316 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
13317 - Remove an extra pair of quotation marks around the error
13318 message in control-port STATUS_GENERAL BUG events. Bugfix on
13319 0.1.2.6-alpha; fixes bug 3732.
13321 o Minor features (relays):
13322 - Ensure that no empty [dirreq-](read|write)-history lines are added
13323 to an extrainfo document. Implements ticket 2497.
13324 - When bandwidth accounting is enabled, be more generous with how
13325 much bandwidth we'll use up before entering "soft hibernation".
13326 Previously, we'd refuse new connections and circuits once we'd
13327 used up 95% of our allotment. Now, we use up 95% of our allotment,
13328 AND make sure that we have no more than 500MB (or 3 hours of
13329 expected traffic, whichever is lower) remaining before we enter
13331 - Relays now log the reason for publishing a new relay descriptor,
13332 so we have a better chance of hunting down instances of bug 1810.
13333 Resolves ticket 3252.
13334 - Log a little more clearly about the times at which we're no longer
13335 accepting new connections (e.g. due to hibernating). Resolves
13337 - When AllowSingleHopExits is set, print a warning to explain to the
13338 relay operator why most clients are avoiding her relay.
13339 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
13340 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
13341 clients are already deprecated because of security bugs.
13343 o Minor features (network statistics):
13344 - Directory mirrors that set "DirReqStatistics 1" write statistics
13345 about directory requests to disk every 24 hours. As compared to the
13346 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
13347 improvements: 1) stats are written to disk exactly every 24 hours;
13348 2) estimated shares of v2 and v3 requests are determined as mean
13349 values, not at the end of a measurement period; 3) unresolved
13350 requests are listed with country code '??'; 4) directories also
13351 measure download times.
13352 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
13353 number of exit streams and transferred bytes per port to disk every
13355 - Relays that set "CellStatistics 1" write statistics on how long
13356 cells spend in their circuit queues to disk every 24 hours.
13357 - Entry nodes that set "EntryStatistics 1" write statistics on the
13358 rough number and origins of connecting clients to disk every 24
13360 - Relays that write any of the above statistics to disk and set
13361 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
13362 their extra-info documents. Implements proposal 166.
13364 o Minor features (GeoIP and statistics):
13365 - Provide a log message stating which geoip file we're parsing
13366 instead of just stating that we're parsing the geoip file.
13367 Implements ticket 2432.
13368 - Make sure every relay writes a state file at least every 12 hours.
13369 Previously, a relay could go for weeks without writing its state
13370 file, and on a crash could lose its bandwidth history, capacity
13371 estimates, client country statistics, and so on. Addresses bug 3012.
13372 - Relays report the number of bytes spent on answering directory
13373 requests in extra-info descriptors similar to {read,write}-history.
13374 Implements enhancement 1790.
13375 - Report only the top 10 ports in exit-port stats in order not to
13376 exceed the maximum extra-info descriptor length of 50 KB. Implements
13378 - If writing the state file to disk fails, wait up to an hour before
13379 retrying again, rather than trying again each second. Fixes bug
13380 2346; bugfix on Tor 0.1.1.3-alpha.
13381 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
13382 when we switch from being a public relay to a bridge. Otherwise
13383 there will still be clients that see the relay in their consensus,
13384 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
13386 - Update to the August 2 2011 Maxmind GeoLite Country database.
13388 o Minor features (clients):
13389 - When expiring circuits, use microsecond timers rather than
13390 one-second timers. This can avoid an unpleasant situation where a
13391 circuit is launched near the end of one second and expired right
13392 near the beginning of the next, and prevent fluctuations in circuit
13394 - If we've configured EntryNodes and our network goes away and/or all
13395 our entrynodes get marked down, optimistically retry them all when
13396 a new socks application request appears. Fixes bug 1882.
13397 - Always perform router selections using weighted relay bandwidth,
13398 even if we don't need a high capacity circuit at the time. Non-fast
13399 circuits now only differ from fast ones in that they can use relays
13400 not marked with the Fast flag. This "feature" could turn out to
13401 be a horrible bug; we should investigate more before it goes into
13403 - When we run out of directory information such that we can't build
13404 circuits, but then get enough that we can build circuits, log when
13405 we actually construct a circuit, so the user has a better chance of
13406 knowing what's going on. Fixes bug 1362.
13407 - Log SSL state transitions at debug level during handshake, and
13408 include SSL states in error messages. This may help debug future
13409 SSL handshake issues.
13411 o Minor features (directory authorities):
13412 - When a router changes IP address or port, authorities now launch
13413 a new reachability test for it. Implements ticket 1899.
13414 - Directory authorities now reject relays running any versions of
13415 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
13416 known bugs that keep RELAY_EARLY cells from working on rendezvous
13417 circuits. Followup to fix for bug 2081.
13418 - Directory authorities now reject relays running any version of Tor
13419 older than 0.2.0.26-rc. That version is the earliest that fetches
13420 current directory information correctly. Fixes bug 2156.
13421 - Directory authorities now do an immediate reachability check as soon
13422 as they hear about a new relay. This change should slightly reduce
13423 the time between setting up a relay and getting listed as running
13424 in the consensus. It should also improve the time between setting
13425 up a bridge and seeing use by bridge users.
13426 - Directory authorities no longer launch a TLS connection to every
13427 relay as they startup. Now that we have 2k+ descriptors cached,
13428 the resulting network hiccup is becoming a burden. Besides,
13429 authorities already avoid voting about Running for the first half
13430 hour of their uptime.
13431 - Directory authorities now log the source of a rejected POSTed v3
13432 networkstatus vote, so we can track failures better.
13433 - Backport code from 0.2.3.x that allows directory authorities to
13434 clean their microdescriptor caches. Needed to resolve bug 2230.
13436 o Minor features (hidden services):
13437 - Use computed circuit-build timeouts to decide when to launch
13438 parallel introduction circuits for hidden services. (Previously,
13439 we would retry after 15 seconds.)
13440 - Don't allow v0 hidden service authorities to act as clients.
13441 Required by fix for bug 3000.
13442 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
13443 by fix for bug 3000.
13444 - Make hidden services work better in private Tor networks by not
13445 requiring any uptime to join the hidden service descriptor
13446 DHT. Implements ticket 2088.
13447 - Log (at info level) when purging pieces of hidden-service-client
13448 state because of SIGNAL NEWNYM.
13450 o Minor features (controller interface):
13451 - New "GETINFO net/listeners/(type)" controller command to return
13452 a list of addresses and ports that are bound for listeners for a
13453 given connection type. This is useful when the user has configured
13454 "SocksPort auto" and the controller needs to know which port got
13455 chosen. Resolves another part of ticket 3076.
13456 - Have the controller interface give a more useful message than
13457 "Internal Error" in response to failed GETINFO requests.
13458 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
13459 event, to give information on the current rate of circuit timeouts
13460 over our stored history.
13461 - The 'EXTENDCIRCUIT' control port command can now be used with
13462 a circ id of 0 and no path. This feature will cause Tor to build
13463 a new 'fast' general purpose circuit using its own path selection
13465 - Added a BUILDTIMEOUT_SET controller event to describe changes
13466 to the circuit build timeout.
13467 - New controller command "getinfo config-text". It returns the
13468 contents that Tor would write if you send it a SAVECONF command,
13469 so the controller can write the file to disk itself.
13471 o Minor features (controller protocol):
13472 - Add a new ControlSocketsGroupWritable configuration option: when
13473 it is turned on, ControlSockets are group-writeable by the default
13474 group of the current user. Patch by Jérémy Bobbio; implements
13476 - Tor now refuses to create a ControlSocket in a directory that is
13477 world-readable (or group-readable if ControlSocketsGroupWritable
13478 is 0). This is necessary because some operating systems do not
13479 enforce permissions on an AF_UNIX sockets. Permissions on the
13480 directory holding the socket, however, seems to work everywhere.
13481 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
13482 not. This would lead to a cookie that is still not group readable.
13483 Closes bug 1843. Suggested by katmagic.
13484 - Future-proof the controller protocol a bit by ignoring keyword
13485 arguments we do not recognize.
13487 o Minor features (more useful logging):
13488 - Revise most log messages that refer to nodes by nickname to
13489 instead use the "$key=nickname at address" format. This should be
13490 more useful, especially since nicknames are less and less likely
13491 to be unique. Resolves ticket 3045.
13492 - When an HTTPS proxy reports "403 Forbidden", we now explain
13493 what it means rather than calling it an unexpected status code.
13494 Closes bug 2503. Patch from Michael Yakubovich.
13495 - Rate-limit a warning about failures to download v2 networkstatus
13496 documents. Resolves part of bug 1352.
13497 - Rate-limit the "your application is giving Tor only an IP address"
13498 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
13499 - Rate-limit "Failed to hand off onionskin" warnings.
13500 - When logging a rate-limited warning, we now mention how many messages
13501 got suppressed since the last warning.
13502 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
13503 2 no signature, 4 required" messages about consensus signatures
13504 easier to read, and make sure they get logged at the same severity
13505 as the messages explaining which keys are which. Fixes bug 1290.
13506 - Don't warn when we have a consensus that we can't verify because
13507 of missing certificates, unless those certificates are ones
13508 that we have been trying and failing to download. Fixes bug 1145.
13510 o Minor features (log domains):
13511 - Add documentation for configuring logging at different severities in
13512 different log domains. We've had this feature since 0.2.1.1-alpha,
13513 but for some reason it never made it into the manpage. Fixes
13515 - Make it simpler to specify "All log domains except for A and B".
13516 Previously you needed to say "[*,~A,~B]". Now you can just say
13518 - Add a "LogMessageDomains 1" option to include the domains of log
13519 messages along with the messages. Without this, there's no way
13520 to use log domains without reading the source or doing a lot
13522 - Add a new "Handshake" log domain for activities that happen
13523 during the TLS handshake.
13525 o Minor features (build process):
13526 - Make compilation with clang possible when using
13527 "--enable-gcc-warnings" by removing two warning options that clang
13528 hasn't implemented yet and by fixing a few warnings. Resolves
13530 - Detect platforms that brokenly use a signed size_t, and refuse to
13531 build there. Found and analyzed by doorss and rransom.
13532 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
13534 - Add support for statically linking zlib by specifying
13535 "--enable-static-zlib", to go with our support for statically
13536 linking openssl and libevent. Resolves bug 1358.
13537 - Instead of adding the svn revision to the Tor version string, report
13538 the git commit (when we're building from a git checkout).
13539 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
13541 - New --digests command-line switch to output the digests of the
13542 source files Tor was built with.
13543 - Generate our manpage and HTML documentation using Asciidoc. This
13544 change should make it easier to maintain the documentation, and
13545 produce nicer HTML. The build process fails if asciidoc cannot
13546 be found and building with asciidoc isn't disabled (via the
13547 "--disable-asciidoc" argument to ./configure. Skipping the manpage
13548 speeds up the build considerably.
13550 o Minor features (options / torrc):
13551 - Warn when the same option is provided more than once in a torrc
13552 file, on the command line, or in a single SETCONF statement, and
13553 the option is one that only accepts a single line. Closes bug 1384.
13554 - Warn when the user configures two HiddenServiceDir lines that point
13555 to the same directory. Bugfix on 0.0.6 (the version introducing
13556 HiddenServiceDir); fixes bug 3289.
13557 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
13558 do individual connection-level rate limiting of clients. The torrc
13559 config options with the same names trump the consensus params, if
13560 both are present. Replaces the old "bwconnrate" and "bwconnburst"
13561 consensus params which were broken from 0.2.2.7-alpha through
13562 0.2.2.14-alpha. Closes bug 1947.
13563 - New config option "WarnUnsafeSocks 0" disables the warning that
13564 occurs whenever Tor receives a socks handshake using a version of
13565 the socks protocol that can only provide an IP address (rather
13566 than a hostname). Setups that do DNS locally over Tor are fine,
13567 and we shouldn't spam the logs in that case.
13568 - New config option "CircuitStreamTimeout" to override our internal
13569 timeout schedule for how many seconds until we detach a stream from
13570 a circuit and try a new circuit. If your network is particularly
13571 slow, you might want to set this to a number like 60.
13572 - New options for SafeLogging to allow scrubbing only log messages
13573 generated while acting as a relay. Specify "SafeLogging relay" if
13574 you want to ensure that only messages known to originate from
13575 client use of the Tor process will be logged unsafely.
13576 - Time and memory units in the configuration file can now be set to
13577 fractional units. For example, "2.5 GB" is now a valid value for
13579 - Support line continuations in the torrc config file. If a line
13580 ends with a single backslash character, the newline is ignored, and
13581 the configuration value is treated as continuing on the next line.
13584 o Minor features (unit tests):
13585 - Revise our unit tests to use the "tinytest" framework, so we
13586 can run tests in their own processes, have smarter setup/teardown
13587 code, and so on. The unit test code has moved to its own
13588 subdirectory, and has been split into multiple modules.
13589 - Add a unit test for cross-platform directory-listing code.
13590 - Add some forgotten return value checks during unit tests. Found
13592 - Use GetTempDir to find the proper temporary directory location on
13593 Windows when generating temporary files for the unit tests. Patch
13596 o Minor features (misc):
13597 - The "torify" script now uses torsocks where available.
13598 - Make Libevent log messages get delivered to controllers later,
13599 and not from inside the Libevent log handler. This prevents unsafe
13600 reentrant Libevent calls while still letting the log messages
13602 - Certain Tor clients (such as those behind check.torproject.org) may
13603 want to fetch the consensus in an extra early manner. To enable this
13604 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
13605 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
13606 as only certain clients who must have this information sooner should
13608 - Expand homedirs passed to tor-checkkey. This should silence a
13609 coverity complaint about passing a user-supplied string into
13610 open() without checking it.
13611 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
13612 used on bridges, and it makes bridge scanning somewhat easier.
13613 - Create the /var/run/tor directory on startup on OpenSUSE if it is
13614 not already created. Patch from Andreas Stieger. Fixes bug 2573.
13616 o Minor bugfixes (relays):
13617 - When a relay decides that its DNS is too broken for it to serve
13618 as an exit server, it advertised itself as a non-exit, but
13619 continued to act as an exit. This could create accidental
13620 partitioning opportunities for users. Instead, if a relay is
13621 going to advertise reject *:* as its exit policy, it should
13622 really act with exit policy "reject *:*". Fixes bug 2366.
13623 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
13624 - Publish a router descriptor even if generating an extra-info
13625 descriptor fails. Previously we would not publish a router
13626 descriptor without an extra-info descriptor; this can cause fast
13627 exit relays collecting exit-port statistics to drop from the
13628 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
13629 - When we're trying to guess whether we know our IP address as
13630 a relay, we would log various ways that we failed to guess
13631 our address, but never log that we ended up guessing it
13632 successfully. Now add a log line to help confused and anxious
13633 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
13634 - For bandwidth accounting, calculate our expected bandwidth rate
13635 based on the time during which we were active and not in
13636 soft-hibernation during the last interval. Previously, we were
13637 also considering the time spent in soft-hibernation. If this
13638 was a long time, we would wind up underestimating our bandwidth
13639 by a lot, and skewing our wakeup time towards the start of the
13640 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
13641 - Demote a confusing TLS warning that relay operators might get when
13642 someone tries to talk to their ORPort. It is not the operator's
13643 fault, nor can they do anything about it. Fixes bug 1364; bugfix
13645 - Change "Application request when we're believed to be offline."
13646 notice to "Application request when we haven't used client
13647 functionality lately.", to clarify that it's not an error. Bugfix
13648 on 0.0.9.3; fixes bug 1222.
13650 o Minor bugfixes (bridges):
13651 - When a client starts or stops using bridges, never use a circuit
13652 that was built before the configuration change. This behavior could
13653 put at risk a user who uses bridges to ensure that her traffic
13654 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
13656 - Do not reset the bridge descriptor download status every time we
13657 re-parse our configuration or get a configuration change. Fixes
13658 bug 3019; bugfix on 0.2.0.3-alpha.
13659 - Users couldn't configure a regular relay to be their bridge. It
13660 didn't work because when Tor fetched the bridge descriptor, it found
13661 that it already had it, and didn't realize that the purpose of the
13662 descriptor had changed. Now we replace routers with a purpose other
13663 than bridge with bridge descriptors when fetching them. Bugfix on
13664 0.1.1.9-alpha. Fixes bug 1776.
13665 - In the special case where you configure a public exit relay as your
13666 bridge, Tor would be willing to use that exit relay as the last
13667 hop in your circuit as well. Now we fail that circuit instead.
13668 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
13670 o Minor bugfixes (clients):
13671 - We now ask the other side of a stream (the client or the exit)
13672 for more data on that stream when the amount of queued data on
13673 that stream dips low enough. Previously, we wouldn't ask the
13674 other side for more data until either it sent us more data (which
13675 it wasn't supposed to do if it had exhausted its window!) or we
13676 had completely flushed all our queued data. This flow control fix
13677 should improve throughput. Fixes bug 2756; bugfix on the earliest
13678 released versions of Tor (svn commit r152).
13679 - When a client finds that an origin circuit has run out of 16-bit
13680 stream IDs, we now mark it as unusable for new streams. Previously,
13681 we would try to close the entire circuit. Bugfix on 0.0.6.
13682 - Make it explicit that we don't cannibalize one-hop circuits. This
13683 happens in the wild, but doesn't turn out to be a problem because
13684 we fortunately don't use those circuits. Many thanks to outofwords
13685 for the initial analysis and to swissknife who confirmed that
13686 two-hop circuits are actually created.
13687 - Resolve an edge case in path weighting that could make us misweight
13688 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
13689 - Make the DNSPort option work with libevent 2.x. Don't alter the
13690 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
13692 o Minor bugfixes (directory authorities):
13693 - Make directory authorities more accurate at recording when
13694 relays that have failed several reachability tests became
13695 unreachable, so we can provide more accuracy at assigning Stable,
13696 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
13697 - Directory authorities are now more robust to hops back in time
13698 when calculating router stability. Previously, if a run of uptime
13699 or downtime appeared to be negative, the calculation could give
13700 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
13702 - Directory authorities will now attempt to download consensuses
13703 if their own efforts to make a live consensus have failed. This
13704 change means authorities that restart will fetch a valid
13705 consensus, and it means authorities that didn't agree with the
13706 current consensus will still fetch and serve it if it has enough
13707 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
13708 - Never vote for a server as "Running" if we have a descriptor for
13709 it claiming to be hibernating, and that descriptor was published
13710 more recently than our last contact with the server. Bugfix on
13711 0.2.0.3-alpha; fixes bug 911.
13712 - Directory authorities no longer change their opinion of, or vote on,
13713 whether a router is Running, unless they have themselves been
13714 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
13717 o Minor bugfixes (hidden services):
13718 - Log malformed requests for rendezvous descriptors as protocol
13719 warnings, not warnings. Also, use a more informative log message
13720 in case someone sees it at log level warning without prior
13721 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
13722 - Accept hidden service descriptors if we think we might be a hidden
13723 service directory, regardless of what our consensus says. This
13724 helps robustness, since clients and hidden services can sometimes
13725 have a more up-to-date view of the network consensus than we do,
13726 and if they think that the directory authorities list us a HSDir,
13727 we might actually be one. Related to bug 2732; bugfix on
13729 - Correct the warning displayed when a rendezvous descriptor exceeds
13730 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
13732 - Clients and hidden services now use HSDir-flagged relays for hidden
13733 service descriptor downloads and uploads even if the relays have no
13734 DirPort set and the client has disabled TunnelDirConns. This will
13735 eventually allow us to give the HSDir flag to relays with no
13736 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
13737 - Only limit the lengths of single HS descriptors, even when multiple
13738 HS descriptors are published to an HSDir relay in a single POST
13739 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
13741 o Minor bugfixes (controllers):
13742 - Allow GETINFO fingerprint to return a fingerprint even when
13743 we have not yet built a router descriptor. Fixes bug 3577;
13744 bugfix on 0.2.0.1-alpha.
13745 - Send a SUCCEEDED stream event to the controller when a reverse
13746 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
13747 discovered by katmagic.
13748 - Remove a trailing asterisk from "exit-policy/default" in the
13749 output of the control port command "GETINFO info/names". Bugfix
13751 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
13752 2917. Bugfix on 0.1.1.1-alpha.
13753 - When we restart our relay, we might get a successful connection
13754 from the outside before we've started our reachability tests,
13755 triggering a warning: "ORPort found reachable, but I have no
13756 routerinfo yet. Failing to inform controller of success." This
13757 bug was harmless unless Tor is running under a controller
13758 like Vidalia, in which case the controller would never get a
13759 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
13761 - When a controller changes TrackHostExits, remove mappings for
13762 hosts that should no longer have their exits tracked. Bugfix on
13764 - When a controller changes VirtualAddrNetwork, remove any mappings
13765 for hosts that were automapped to the old network. Bugfix on
13767 - When a controller changes one of the AutomapHosts* options, remove
13768 any mappings for hosts that should no longer be automapped. Bugfix
13770 - Fix an off-by-one error in calculating some controller command
13771 argument lengths. Fortunately, this mistake is harmless since
13772 the controller code does redundant NUL termination too. Found by
13773 boboper. Bugfix on 0.1.1.1-alpha.
13774 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
13775 would return "551 Internal error" rather than "552 Unrecognized key
13776 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
13777 - Don't spam the controller with events when we have no file
13778 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
13779 for log messages was already solved from bug 748.)
13780 - Emit a GUARD DROPPED controller event for a case we missed.
13781 - Ensure DNS requests launched by "RESOLVE" commands from the
13782 controller respect the __LeaveStreamsUnattached setconf options. The
13783 same goes for requests launched via DNSPort or transparent
13784 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
13786 o Minor bugfixes (config options):
13787 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
13788 Change the limit to 512 characters by removing base64 newlines.
13789 Fixes bug 2752. Fix by Michael Yakubovich.
13790 - Complain if PublishServerDescriptor is given multiple arguments that
13791 include 0 or 1. This configuration will be rejected in the future.
13792 Bugfix on 0.2.0.1-alpha; closes bug 1107.
13793 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
13794 Bugfix on 0.2.0.13-alpha; closes bug 928.
13796 o Minor bugfixes (log subsystem fixes):
13797 - When unable to format an address as a string, report its value
13798 as "???" rather than reusing the last formatted address. Bugfix
13800 - Be more consistent in our treatment of file system paths. "~" should
13801 get expanded to the user's home directory in the Log config option.
13802 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
13803 feature for the -f and --DataDirectory options.
13805 o Minor bugfixes (memory management):
13806 - Don't stack-allocate the list of supplementary GIDs when we're
13807 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
13808 could take up to 256K, which is way too much stack. Found by
13809 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
13810 - Save a couple bytes in memory allocation every time we escape
13811 certain characters in a string. Patch from Florian Zumbiehl.
13813 o Minor bugfixes (protocol correctness):
13814 - When checking for 1024-bit keys, check for 1024 bits, not 128
13815 bytes. This allows Tor to correctly discard keys of length 1017
13816 through 1023. Bugfix on 0.0.9pre5.
13817 - Require that introduction point keys and onion handshake keys
13818 have a public exponent of 65537. Starts to fix bug 3207; bugfix
13820 - Handle SOCKS messages longer than 128 bytes long correctly, rather
13821 than waiting forever for them to finish. Fixes bug 2330; bugfix
13822 on 0.2.0.16-alpha. Found by doorss.
13823 - Never relay a cell for a circuit we have already destroyed.
13824 Between marking a circuit as closeable and finally closing it,
13825 it may have been possible for a few queued cells to get relayed,
13826 even though they would have been immediately dropped by the next
13827 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
13828 - Never queue a cell for a circuit that's already been marked
13830 - Fix a spec conformance issue: the network-status-version token
13831 must be the first token in a v3 consensus or vote. Discovered by
13832 "parakeep". Bugfix on 0.2.0.3-alpha.
13833 - A networkstatus vote must contain exactly one signature. Spec
13834 conformance issue. Bugfix on 0.2.0.3-alpha.
13835 - When asked about a DNS record type we don't support via a
13836 client DNSPort, reply with NOTIMPL rather than an empty
13837 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
13838 - Make more fields in the controller protocol case-insensitive, since
13839 control-spec.txt said they were.
13841 o Minor bugfixes (log messages):
13842 - Fix a log message that said "bits" while displaying a value in
13843 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
13845 - Downgrade "no current certificates known for authority" message from
13846 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
13847 - Correctly describe errors that occur when generating a TLS object.
13848 Previously we would attribute them to a failure while generating a
13849 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
13851 - Fix an instance where a Tor directory mirror might accidentally
13852 log the IP address of a misbehaving Tor client. Bugfix on
13854 - Stop logging at severity 'warn' when some other Tor client tries
13855 to establish a circuit with us using weak DH keys. It's a protocol
13856 violation, but that doesn't mean ordinary users need to hear about
13857 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
13858 - If your relay can't keep up with the number of incoming create
13859 cells, it would log one warning per failure into your logs. Limit
13860 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
13862 o Minor bugfixes (build fixes):
13863 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
13864 - When warning about missing zlib development packages during compile,
13865 give the correct package names. Bugfix on 0.2.0.1-alpha.
13866 - Fix warnings that newer versions of autoconf produce during
13867 ./autogen.sh. These warnings appear to be harmless in our case,
13868 but they were extremely verbose. Fixes bug 2020.
13869 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
13872 o Minor bugfixes (portability):
13873 - Write several files in text mode, on OSes that distinguish text
13874 mode from binary mode (namely, Windows). These files are:
13875 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
13876 that collect those statistics; 'client_keys' and 'hostname' for
13877 hidden services that use authentication; and (in the tor-gencert
13878 utility) newly generated identity and signing keys. Previously,
13879 we wouldn't specify text mode or binary mode, leading to an
13880 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
13881 the DirRecordUsageByCountry option which would have triggered
13882 the assertion failure was added), although this assertion failure
13883 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
13884 - Selectively disable deprecation warnings on OS X because Lion
13885 started deprecating the shipped copy of openssl. Fixes bug 3643.
13886 - Use a wide type to hold sockets when built for 64-bit Windows.
13888 - Fix an issue that prevented static linking of libevent on
13889 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
13890 where we introduced the "--with-static-libevent" configure option.
13891 - Fix a bug with our locking implementation on Windows that couldn't
13892 correctly detect when a file was already locked. Fixes bug 2504,
13893 bugfix on 0.2.1.6-alpha.
13894 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
13896 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
13897 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
13900 o Minor bugfixes (code correctness):
13901 - Always NUL-terminate the sun_path field of a sockaddr_un before
13902 passing it to the kernel. (Not a security issue: kernels are
13903 smart enough to reject bad sockaddr_uns.) Found by Coverity;
13904 CID #428. Bugfix on Tor 0.2.0.3-alpha.
13905 - Make connection_printf_to_buf()'s behavior sane. Its callers
13906 expect it to emit a CRLF iff the format string ends with CRLF;
13907 it actually emitted a CRLF iff (a) the format string ended with
13908 CRLF or (b) the resulting string was over 1023 characters long or
13909 (c) the format string did not end with CRLF *and* the resulting
13910 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
13911 fixes part of bug 3407.
13912 - Make send_control_event_impl()'s behavior sane. Its callers
13913 expect it to always emit a CRLF at the end of the string; it
13914 might have emitted extra control characters as well. Bugfix on
13915 0.1.1.9-alpha; fixes another part of bug 3407.
13916 - Make crypto_rand_int() check the value of its input correctly.
13917 Previously, it accepted values up to UINT_MAX, but could return a
13918 negative number if given a value above INT_MAX+1. Found by George
13919 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
13920 - Fix a potential null-pointer dereference while computing a
13921 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
13923 - If we fail to compute the identity digest of a v3 legacy keypair,
13924 warn, and don't use a buffer-full of junk instead. Bugfix on
13925 0.2.1.1-alpha; fixes bug 3106.
13926 - Resolve an untriggerable issue in smartlist_string_num_isin(),
13927 where if the function had ever in the future been used to check
13928 for the presence of a too-large number, it would have given an
13929 incorrect result. (Fortunately, we only used it for 16-bit
13930 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
13931 - Be more careful about reporting the correct error from a failed
13932 connect() system call. Under some circumstances, it was possible to
13933 look at an incorrect value for errno when sending the end reason.
13934 Bugfix on 0.1.0.1-rc.
13935 - Correctly handle an "impossible" overflow cases in connection byte
13936 counting, where we write or read more than 4GB on an edge connection
13937 in a single second. Bugfix on 0.1.2.8-beta.
13938 - Avoid a double mark-for-free warning when failing to attach a
13939 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
13941 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
13942 found by "cypherpunks". This bug was introduced before the first
13943 Tor release, in svn commit r110.
13944 - Fix a bug in bandwidth history state parsing that could have been
13945 triggered if a future version of Tor ever changed the timing
13946 granularity at which bandwidth history is measured. Bugfix on
13947 Tor 0.1.1.11-alpha.
13948 - Add assertions to check for overflow in arguments to
13949 base32_encode() and base32_decode(); fix a signed-unsigned
13950 comparison there too. These bugs are not actually reachable in Tor,
13951 but it's good to prevent future errors too. Found by doorss.
13952 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
13954 - Set target port in get_interface_address6() correctly. Bugfix
13955 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
13956 - Fix an impossible-to-actually-trigger buffer overflow in relay
13957 descriptor generation. Bugfix on 0.1.0.15.
13958 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
13960 o Minor bugfixes (code improvements):
13961 - After we free an internal connection structure, overwrite it
13962 with a different memory value than we use for overwriting a freed
13963 internal circuit structure. Should help with debugging. Suggested
13965 - If OpenSSL fails to make a duplicate of a private or public key, log
13966 an error message and try to exit cleanly. May help with debugging
13967 if bug 1209 ever remanifests.
13968 - Some options used different conventions for uppercasing of acronyms
13969 when comparing manpage and source. Fix those in favor of the
13970 manpage, as it makes sense to capitalize acronyms.
13971 - Take a first step towards making or.h smaller by splitting out
13972 function definitions for all source files in src/or/. Leave
13973 structures and defines in or.h for now.
13974 - Remove a few dead assignments during router parsing. Found by
13976 - Don't use 1-bit wide signed bit fields. Found by coverity.
13977 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
13978 None of the cases where we did this before were wrong, but by making
13979 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
13980 - The memarea code now uses a sentinel value at the end of each area
13981 to make sure nothing writes beyond the end of an area. This might
13982 help debug some conceivable causes of bug 930.
13983 - Always treat failure to allocate an RSA key as an unrecoverable
13985 - Add some more defensive programming for architectures that can't
13986 handle unaligned integer accesses. We don't know of any actual bugs
13987 right now, but that's the best time to fix them. Fixes bug 1943.
13989 o Minor bugfixes (misc):
13990 - Fix a rare bug in rend_fn unit tests: we would fail a test when
13991 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
13992 on 0.2.0.10-alpha; fixes bug 1808.
13993 - Where available, use Libevent 2.0's periodic timers so that our
13994 once-per-second cleanup code gets called even more closely to
13995 once per second than it would otherwise. Fixes bug 943.
13996 - Ignore OutboundBindAddress when connecting to localhost.
13997 Connections to localhost need to come _from_ localhost, or else
13998 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
14000 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
14002 - If any of the v3 certs we download are unparseable, we should
14003 actually notice the failure so we don't retry indefinitely. Bugfix
14004 on 0.2.0.x; reported by "rotator".
14005 - When Tor fails to parse a descriptor of any kind, dump it to disk.
14006 Might help diagnosing bug 1051.
14007 - Make our 'torify' script more portable; if we have only one of
14008 'torsocks' or 'tsocks' installed, don't complain to the user;
14009 and explain our warning about tsocks better.
14010 - Fix some urls in the exit notice file and make it XHTML1.1 strict
14011 compliant. Based on a patch from Christian Kujau.
14013 o Documentation changes:
14014 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
14015 - Resolve all doxygen warnings except those for missing documentation.
14017 - Add doxygen documentation for more functions, fields, and types.
14018 - Convert the HACKING file to asciidoc, and add a few new sections
14019 to it, explaining how we use Git, how we make changelogs, and
14020 what should go in a patch.
14021 - Document the default socks host and port (127.0.0.1:9050) for
14023 - Removed some unnecessary files from the source distribution. The
14024 AUTHORS file has now been merged into the people page on the
14025 website. The roadmaps and design doc can now be found in the
14026 projects directory in svn.
14028 o Deprecated and removed features (config):
14029 - Remove the torrc.complete file. It hasn't been kept up to date
14030 and users will have better luck checking out the manpage.
14031 - Remove the HSAuthorityRecordStats option that version 0 hidden
14032 service authorities could use to track statistics of overall v0
14033 hidden service usage.
14034 - Remove the obsolete "NoPublish" option; it has been flagged
14035 as obsolete and has produced a warning since 0.1.1.18-rc.
14036 - Caches no longer download and serve v2 networkstatus documents
14037 unless FetchV2Networkstatus flag is set: these documents haven't
14038 haven't been used by clients or relays since 0.2.0.x. Resolves
14041 o Deprecated and removed features (controller):
14042 - The controller no longer accepts the old obsolete "addr-mappings/"
14043 or "unregistered-servers-" GETINFO values.
14044 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
14045 always on; using them is necessary for correct forward-compatible
14048 o Deprecated and removed features (misc):
14049 - Hidden services no longer publish version 0 descriptors, and clients
14050 do not request or use version 0 descriptors. However, the old hidden
14051 service authorities still accept and serve version 0 descriptors
14052 when contacted by older hidden services/clients.
14053 - Remove undocumented option "-F" from tor-resolve: it hasn't done
14054 anything since 0.2.1.16-rc.
14055 - Remove everything related to building the expert bundle for OS X.
14056 It has confused many users, doesn't work right on OS X 10.6,
14057 and is hard to get rid of once installed. Resolves bug 1274.
14058 - Remove support for .noconnect style addresses. Nobody was using
14059 them, and they provided another avenue for detecting Tor users
14060 via application-level web tricks.
14061 - When we fixed bug 1038 we had to put in a restriction not to send
14062 RELAY_EARLY cells on rend circuits. This was necessary as long
14063 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
14064 active. Now remove this obsolete check. Resolves bug 2081.
14065 - Remove workaround code to handle directory responses from servers
14066 that had bug 539 (they would send HTTP status 503 responses _and_
14067 send a body too). Since only server versions before
14068 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
14069 keep the workaround in place.
14070 - Remove the old 'fuzzy time' logic. It was supposed to be used for
14071 handling calculations where we have a known amount of clock skew and
14072 an allowed amount of unknown skew. But we only used it in three
14073 places, and we never adjusted the known/unknown skew values. This is
14074 still something we might want to do someday, but if we do, we'll
14075 want to do it differently.
14076 - Remove the "--enable-iphone" option to ./configure. According to
14077 reports from Marco Bonetti, Tor builds fine without any special
14078 tweaking on recent iPhone SDK versions.
14081 Changes in version 0.2.1.30 - 2011-02-23
14082 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
14083 change is a slight tweak to Tor's TLS handshake that makes relays
14084 and bridges that run this new version reachable from Iran again.
14085 We don't expect this tweak will win the arms race long-term, but it
14086 buys us time until we roll out a better solution.
14089 - Stop sending a CLOCK_SKEW controller status event whenever
14090 we fetch directory information from a relay that has a wrong clock.
14091 Instead, only inform the controller when it's a trusted authority
14092 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
14093 the rest of bug 1074.
14094 - Fix a bounds-checking error that could allow an attacker to
14095 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
14096 Found by "piebeer".
14097 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
14098 Tor would ignore their RelayBandwidthBurst setting,
14099 potentially using more bandwidth than expected. Bugfix on
14100 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
14101 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
14102 hidserv" in her torrc. The 'hidserv' argument never controlled
14103 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
14106 - Adjust our TLS Diffie-Hellman parameters to match those used by
14108 - Update to the February 1 2011 Maxmind GeoLite Country database.
14111 - Check for and reject overly long directory certificates and
14112 directory tokens before they have a chance to hit any assertions.
14113 Bugfix on 0.2.1.28. Found by "doorss".
14114 - Bring the logic that gathers routerinfos and assesses the
14115 acceptability of circuits into line. This prevents a Tor OP from
14116 getting locked in a cycle of choosing its local OR as an exit for a
14117 path (due to a .exit request) and then rejecting the circuit because
14118 its OR is not listed yet. It also prevents Tor clients from using an
14119 OR running in the same instance as an exit (due to a .exit request)
14120 if the OR does not meet the same requirements expected of an OR
14121 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
14123 o Packaging changes:
14124 - Stop shipping the Tor specs files and development proposal documents
14125 in the tarball. They are now in a separate git repository at
14126 git://git.torproject.org/torspec.git
14127 - Do not include Git version tags as though they are SVN tags when
14128 generating a tarball from inside a repository that has switched
14129 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
14132 Changes in version 0.2.1.29 - 2011-01-15
14133 Tor 0.2.1.29 continues our recent code security audit work. The main
14134 fix resolves a remote heap overflow vulnerability that can allow remote
14135 code execution. Other fixes address a variety of assert and crash bugs,
14136 most of which we think are hard to exploit remotely.
14138 o Major bugfixes (security):
14139 - Fix a heap overflow bug where an adversary could cause heap
14140 corruption. This bug probably allows remote code execution
14141 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
14143 - Prevent a denial-of-service attack by disallowing any
14144 zlib-compressed data whose compression factor is implausibly
14145 high. Fixes part of bug 2324; reported by "doorss".
14146 - Zero out a few more keys in memory before freeing them. Fixes
14147 bug 2384 and part of bug 2385. These key instances found by
14148 "cypherpunks", based on Andrew Case's report about being able
14149 to find sensitive data in Tor's memory space if you have enough
14150 permissions. Bugfix on 0.0.2pre9.
14152 o Major bugfixes (crashes):
14153 - Prevent calls to Libevent from inside Libevent log handlers.
14154 This had potential to cause a nasty set of crashes, especially
14155 if running Libevent with debug logging enabled, and running
14156 Tor with a controller watching for low-severity log messages.
14157 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
14158 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
14159 underflow errors there too. Fixes the other part of bug 2324.
14160 - Fix a bug where we would assert if we ever had a
14161 cached-descriptors.new file (or another file read directly into
14162 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
14163 on 0.2.1.25. Found by doorss.
14164 - Fix some potential asserts and parsing issues with grossly
14165 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
14168 o Minor bugfixes (other):
14169 - Fix a bug with handling misformed replies to reverse DNS lookup
14170 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
14171 bug reported by doorss.
14172 - Fix compilation on mingw when a pthreads compatibility library
14173 has been installed. (We don't want to use it, so we shouldn't
14174 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
14175 - Fix a bug where we would declare that we had run out of virtual
14176 addresses when the address space was only half-exhausted. Bugfix
14178 - Correctly handle the case where AutomapHostsOnResolve is set but
14179 no virtual addresses are available. Fixes bug 2328; bugfix on
14180 0.1.2.1-alpha. Bug found by doorss.
14181 - Correctly handle wrapping around when we run out of virtual
14182 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
14185 - Update to the January 1 2011 Maxmind GeoLite Country database.
14186 - Introduce output size checks on all of our decryption functions.
14189 - Tor does not build packages correctly with Automake 1.6 and earlier;
14190 added a check to Makefile.am to make sure that we're building with
14191 Automake 1.7 or later.
14192 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
14193 because we built it with a too-old version of automake. Thus that
14194 release broke ./configure --enable-openbsd-malloc, which is popular
14195 among really fast exit relays on Linux.
14198 Changes in version 0.2.1.28 - 2010-12-17
14199 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
14200 exploitable bugs. We also took this opportunity to change the IP address
14201 for one of our directory authorities, and to update the geoip database
14205 - Fix a remotely exploitable bug that could be used to crash instances
14206 of Tor remotely by overflowing on the heap. Remote-code execution
14207 hasn't been confirmed, but can't be ruled out. Everyone should
14208 upgrade. Bugfix on the 0.1.1 series and later.
14210 o Directory authority changes:
14211 - Change IP address and ports for gabelmoo (v3 directory authority).
14214 - Update to the December 1 2010 Maxmind GeoLite Country database.
14217 Changes in version 0.2.1.27 - 2010-11-23
14218 Yet another OpenSSL security patch broke its compatibility with Tor:
14219 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
14220 also took this opportunity to fix several crash bugs, integrate a new
14221 directory authority, and update the bundled GeoIP database.
14224 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
14225 No longer set the tlsext_host_name extension on server SSL objects;
14226 but continue to set it on client SSL objects. Our goal in setting
14227 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
14228 bugfix on 0.2.1.1-alpha.
14229 - Do not log messages to the controller while shrinking buffer
14230 freelists. Doing so would sometimes make the controller connection
14231 try to allocate a buffer chunk, which would mess up the internals
14232 of the freelist and cause an assertion failure. Fixes bug 1125;
14233 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
14234 - Learn our external IP address when we're a relay or bridge, even if
14235 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
14236 where we introduced bridge relays that don't need to publish to
14237 be useful. Fixes bug 2050.
14238 - Do even more to reject (and not just ignore) annotations on
14239 router descriptors received anywhere but from the cache. Previously
14240 we would ignore such annotations at first, but cache them to disk
14241 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
14242 - When you're using bridges and your network goes away and your
14243 bridges get marked as down, recover when you attempt a new socks
14244 connection (if the network is back), rather than waiting up to an
14245 hour to try fetching new descriptors for your bridges. Bugfix on
14246 0.2.0.3-alpha; fixes bug 1981.
14249 - Move to the November 2010 Maxmind GeoLite country db (rather
14250 than the June 2009 ip-to-country GeoIP db) for our statistics that
14251 count how many users relays are seeing from each country. Now we'll
14252 have more accurate data, especially for many African countries.
14254 o New directory authorities:
14255 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
14259 - Fix an assertion failure that could occur in directory caches or
14260 bridge users when using a very short voting interval on a testing
14261 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
14263 - Enforce multiplicity rules when parsing annotations. Bugfix on
14264 0.2.0.8-alpha. Found by piebeer.
14265 - Allow handshaking OR connections to take a full KeepalivePeriod
14266 seconds to handshake. Previously, we would close them after
14267 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
14268 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
14270 - When building with --enable-gcc-warnings on OpenBSD, disable
14271 warnings in system headers. This makes --enable-gcc-warnings
14272 pass on OpenBSD 4.8.
14275 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
14276 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
14277 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
14278 Servers can start sending this code when enough clients recognize
14279 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
14280 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
14281 Patch from mingw-san.
14284 - Remove the old debian/ directory from the main Tor distribution.
14285 The official Tor-for-debian git repository lives at the URL
14286 https://git.torproject.org/debian/tor.git
14287 - Stop shipping the old doc/website/ directory in the tarball. We
14288 changed the website format in late 2010, and what we shipped in
14289 0.2.1.26 really wasn't that useful anyway.
14292 Changes in version 0.2.1.26 - 2010-05-02
14293 Tor 0.2.1.26 addresses the recent connection and memory overload
14294 problems we've been seeing on relays, especially relays with their
14295 DirPort open. If your relay has been crashing, or you turned it off
14296 because it used too many resources, give this release a try.
14298 This release also fixes yet another instance of broken OpenSSL libraries
14299 that was causing some relays to drop out of the consensus.
14302 - Teach relays to defend themselves from connection overload. Relays
14303 now close idle circuits early if it looks like they were intended
14304 for directory fetches. Relays are also more aggressive about closing
14305 TLS connections that have no circuits on them. Such circuits are
14306 unlikely to be re-used, and tens of thousands of them were piling
14307 up at the fast relays, causing the relays to run out of sockets
14308 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
14309 their directory fetches over TLS).
14310 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
14311 that claim to be earlier than 0.9.8m, but which have in reality
14312 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
14313 behavior. Possible fix for some cases of bug 1346.
14314 - Directory mirrors were fetching relay descriptors only from v2
14315 directory authorities, rather than v3 authorities like they should.
14316 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
14317 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
14320 - Finally get rid of the deprecated and now harmful notion of "clique
14321 mode", where directory authorities maintain TLS connections to
14325 - In the util/threads test, no longer free the test_mutex before all
14326 worker threads have finished. Bugfix on 0.2.1.6-alpha.
14327 - The master thread could starve the worker threads quite badly on
14328 certain systems, causing them to run only partially in the allowed
14329 window. This resulted in test failures. Now the master thread sleeps
14330 occasionally for a few microseconds while the two worker-threads
14331 compete for the mutex. Bugfix on 0.2.0.1-alpha.
14334 Changes in version 0.2.1.25 - 2010-03-16
14335 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
14336 prevent relays from guessing their IP address correctly. It also fixes
14337 several minor potential security bugs.
14340 - Fix a regression from our patch for bug 1244 that caused relays
14341 to guess their IP address incorrectly if they didn't set Address
14342 in their torrc and/or their address fails to resolve. Bugfix on
14343 0.2.1.23; fixes bug 1269.
14344 - When freeing a session key, zero it out completely. We only zeroed
14345 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
14346 patched by ekir. Fixes bug 1254.
14349 - Fix a dereference-then-NULL-check sequence when publishing
14350 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
14352 - Fix another dereference-then-NULL-check sequence. Bugfix on
14353 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
14354 - Make sure we treat potentially not NUL-terminated strings correctly.
14355 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
14358 Changes in version 0.2.1.24 - 2010-02-21
14359 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
14363 - Work correctly out-of-the-box with even more vendor-patched versions
14364 of OpenSSL. In particular, make it so Debian and OS X don't need
14365 customized patches to run/build.
14368 Changes in version 0.2.1.23 - 2010-02-13
14369 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
14370 again on the latest OS X, and updates the location of a directory
14373 o Major bugfixes (performance):
14374 - We were selecting our guards uniformly at random, and then weighting
14375 which of our guards we'd use uniformly at random. This imbalance
14376 meant that Tor clients were severely limited on throughput (and
14377 probably latency too) by the first hop in their circuit. Now we
14378 select guards weighted by currently advertised bandwidth. We also
14379 automatically discard guards picked using the old algorithm. Fixes
14380 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
14383 - Make Tor work again on the latest OS X: when deciding whether to
14384 use strange flags to turn TLS renegotiation on, detect the OpenSSL
14385 version at run-time, not compile time. We need to do this because
14386 Apple doesn't update its dev-tools headers when it updates its
14387 libraries in a security patch.
14388 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
14389 that could happen on 32-bit platforms with 64-bit time_t. Also fix
14390 a memory leak when requesting a hidden service descriptor we've
14391 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
14395 - Refactor resolve_my_address() to not use gethostbyname() anymore.
14396 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
14399 - Avoid a mad rush at the beginning of each month when each client
14400 rotates half of its guards. Instead we spread the rotation out
14401 throughout the month, but we still avoid leaving a precise timestamp
14402 in the state file about when we first picked the guard. Improves
14403 over the behavior introduced in 0.1.2.17.
14406 Changes in version 0.2.1.22 - 2010-01-19
14407 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
14408 authorities -- it would tell you its whole history of bridge descriptors
14409 if you make the right directory request. This stable update also
14410 rotates two of the seven v3 directory authority keys and locations.
14412 o Directory authority changes:
14413 - Rotate keys (both v3 identity and relay identity) for moria1
14417 - Stop bridge directory authorities from answering dbg-stability.txt
14418 directory queries, which would let people fetch a list of all
14419 bridge identities they track. Bugfix on 0.2.1.6-alpha.
14422 Changes in version 0.2.1.21 - 2009-12-21
14423 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
14424 library. If you use Tor on Linux / Unix and you're getting SSL
14425 renegotiation errors, upgrading should help. We also recommend an
14426 upgrade if you're an exit relay.
14429 - Work around a security feature in OpenSSL 0.9.8l that prevents our
14430 handshake from working unless we explicitly tell OpenSSL that we
14431 are using SSL renegotiation safely. We are, of course, but OpenSSL
14432 0.9.8l won't work unless we say we are.
14433 - Avoid crashing if the client is trying to upload many bytes and the
14434 circuit gets torn down at the same time, or if the flip side
14435 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
14438 - Do not refuse to learn about authority certs and v2 networkstatus
14439 documents that are older than the latest consensus. This bug might
14440 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
14441 Spotted and fixed by xmux.
14442 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
14443 trigger platform-specific option misparsing case found by Coverity
14445 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
14446 trigger assert. Fixes bug 1173.
14449 Changes in version 0.2.1.20 - 2009-10-15
14450 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
14451 services at once, prepares for more performance improvements, and
14452 fixes a bunch of smaller bugs.
14454 The Windows and OS X bundles also include a more recent Vidalia,
14455 and switch from Privoxy to Polipo.
14457 The OS X installers are now drag and drop. It's best to un-install
14458 Tor/Vidalia and then install this new bundle, rather than upgrade. If
14459 you want to upgrade, you'll need to update the paths for Tor and Polipo
14460 in the Vidalia Settings window.
14463 - Send circuit or stream sendme cells when our window has decreased
14464 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
14465 by Karsten when testing the "reduce circuit window" performance
14466 patch. Bugfix on the 54th commit on Tor -- from July 2002,
14467 before the release of Tor 0.0.0. This is the new winner of the
14469 - Fix a remotely triggerable memory leak when a consensus document
14470 contains more than one signature from the same voter. Bugfix on
14472 - Avoid segfault in rare cases when finishing an introduction circuit
14473 as a client and finding out that we don't have an introduction key
14474 for it. Fixes bug 1073. Reported by Aaron Swartz.
14477 - Tor now reads the "circwindow" parameter out of the consensus,
14478 and uses that value for its circuit package window rather than the
14479 default of 1000 cells. Begins the implementation of proposal 168.
14481 o New directory authorities:
14482 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
14484 - Move moria1 and tonga to alternate IP addresses.
14487 - Fix a signed/unsigned compile warning in 0.2.1.19.
14488 - Fix possible segmentation fault on directory authorities. Bugfix on
14490 - Fix an extremely rare infinite recursion bug that could occur if
14491 we tried to log a message after shutting down the log subsystem.
14492 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
14493 - Fix an obscure bug where hidden services on 64-bit big-endian
14494 systems might mis-read the timestamp in v3 introduce cells, and
14495 refuse to connect back to the client. Discovered by "rotor".
14496 Bugfix on 0.2.1.6-alpha.
14497 - We were triggering a CLOCK_SKEW controller status event whenever
14498 we connect via the v2 connection protocol to any relay that has
14499 a wrong clock. Instead, we should only inform the controller when
14500 it's a trusted authority that claims our clock is wrong. Bugfix
14501 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
14502 - We were telling the controller about CHECKING_REACHABILITY and
14503 REACHABILITY_FAILED status events whenever we launch a testing
14504 circuit or notice that one has failed. Instead, only tell the
14505 controller when we want to inform the user of overall success or
14506 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
14508 - Don't warn when we're using a circuit that ends with a node
14509 excluded in ExcludeExitNodes, but the circuit is not used to access
14510 the outside world. This should help fix bug 1090. Bugfix on
14512 - Work around a small memory leak in some versions of OpenSSL that
14513 stopped the memory used by the hostname TLS extension from being
14517 - Add a "getinfo status/accepted-server-descriptor" controller
14518 command, which is the recommended way for controllers to learn
14519 whether our server descriptor has been successfully received by at
14520 least on directory authority. Un-recommend good-server-descriptor
14521 getinfo and status events until we have a better design for them.
14524 Changes in version 0.2.1.19 - 2009-07-28
14525 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
14529 - Make accessing hidden services on 0.2.1.x work right again.
14530 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
14531 part of patch provided by "optimist".
14534 - When a relay/bridge is writing out its identity key fingerprint to
14535 the "fingerprint" file and to its logs, write it without spaces. Now
14536 it will look like the fingerprints in our bridges documentation,
14537 and confuse fewer users.
14540 - Relays no longer publish a new server descriptor if they change
14541 their MaxAdvertisedBandwidth config option but it doesn't end up
14542 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
14543 fixes bug 1026. Patch from Sebastian.
14544 - Avoid leaking memory every time we get a create cell but we have
14545 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
14546 fixes bug 1034. Reported by BarkerJr.
14549 Changes in version 0.2.1.18 - 2009-07-24
14550 Tor 0.2.1.18 lays the foundations for performance improvements,
14551 adds status events to help users diagnose bootstrap problems, adds
14552 optional authentication/authorization for hidden services, fixes a
14553 variety of potential anonymity problems, and includes a huge pile of
14554 other features and bug fixes.
14556 o Major features (clients):
14557 - Start sending "bootstrap phase" status events to the controller,
14558 so it can keep the user informed of progress fetching directory
14559 information and establishing circuits. Also inform the controller
14560 if we think we're stuck at a particular bootstrap phase. Implements
14562 - Clients replace entry guards that were chosen more than a few months
14563 ago. This change should significantly improve client performance,
14564 especially once more people upgrade, since relays that have been
14565 a guard for a long time are currently overloaded.
14566 - Network status consensus documents and votes now contain bandwidth
14567 information for each relay. Clients use the bandwidth values
14568 in the consensus, rather than the bandwidth values in each
14569 relay descriptor. This approach opens the door to more accurate
14570 bandwidth estimates once the directory authorities start doing
14571 active measurements. Implements part of proposal 141.
14573 o Major features (relays):
14574 - Disable and refactor some debugging checks that forced a linear scan
14575 over the whole server-side DNS cache. These accounted for over 50%
14576 of CPU time on a relatively busy exit node's gprof profile. Also,
14577 disable some debugging checks that appeared in exit node profile
14578 data. Found by Jacob.
14579 - New DirPortFrontPage option that takes an html file and publishes
14580 it as "/" on the DirPort. Now relay operators can provide a
14581 disclaimer without needing to set up a separate webserver. There's
14582 a sample disclaimer in contrib/tor-exit-notice.html.
14584 o Major features (hidden services):
14585 - Make it possible to build hidden services that only certain clients
14586 are allowed to connect to. This is enforced at several points,
14587 so that unauthorized clients are unable to send INTRODUCE cells
14588 to the service, or even (depending on the type of authentication)
14589 to learn introduction points. This feature raises the bar for
14590 certain kinds of active attacks against hidden services. Design
14591 and code by Karsten Loesing. Implements proposal 121.
14592 - Relays now store and serve v2 hidden service descriptors by default,
14593 i.e., the new default value for HidServDirectoryV2 is 1. This is
14594 the last step in proposal 114, which aims to make hidden service
14595 lookups more reliable.
14597 o Major features (path selection):
14598 - ExitNodes and Exclude*Nodes config options now allow you to restrict
14599 by country code ("{US}") or IP address or address pattern
14600 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
14601 refinement to decide what config options should take priority if
14602 you ask to both use a particular node and exclude it.
14604 o Major features (misc):
14605 - When building a consensus, do not include routers that are down.
14606 This cuts down 30% to 40% on consensus size. Implements proposal
14608 - New TestingTorNetwork config option to allow adjustment of
14609 previously constant values that could slow bootstrapping. Implements
14610 proposal 135. Patch from Karsten.
14611 - Convert many internal address representations to optionally hold
14612 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
14613 elements. Make resolver code handle nameservers located at IPv6
14615 - More work on making our TLS handshake blend in: modify the list
14616 of ciphers advertised by OpenSSL in client mode to even more
14617 closely resemble a common web browser. We cheat a little so that
14618 we can advertise ciphers that the locally installed OpenSSL doesn't
14620 - Use the TLS1 hostname extension to more closely resemble browser
14623 o Security fixes (anonymity/entropy):
14624 - Never use a connection with a mismatched address to extend a
14625 circuit, unless that connection is canonical. A canonical
14626 connection is one whose address is authenticated by the router's
14627 identity key, either in a NETINFO cell or in a router descriptor.
14628 - Implement most of proposal 110: The first K cells to be sent
14629 along a circuit are marked as special "early" cells; only K "early"
14630 cells will be allowed. Once this code is universal, we can block
14631 certain kinds of denial-of-service attack by requiring that EXTEND
14632 commands must be sent using an "early" cell.
14633 - Resume using OpenSSL's RAND_poll() for better (and more portable)
14634 cross-platform entropy collection again. We used to use it, then
14635 stopped using it because of a bug that could crash systems that
14636 called RAND_poll when they had a lot of fds open. It looks like the
14637 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
14638 at startup, and to call RAND_poll() when we reseed later only if
14639 we have a non-buggy OpenSSL version.
14640 - When the client is choosing entry guards, now it selects at most
14641 one guard from a given relay family. Otherwise we could end up with
14642 all of our entry points into the network run by the same operator.
14643 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
14644 - Do not use or believe expired v3 authority certificates. Patch
14645 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
14646 - Drop begin cells to a hidden service if they come from the middle
14647 of a circuit. Patch from lark.
14648 - When we erroneously receive two EXTEND cells for the same circuit
14649 ID on the same connection, drop the second. Patch from lark.
14650 - Authorities now vote for the Stable flag for any router whose
14651 weighted MTBF is at least 5 days, regardless of the mean MTBF.
14652 - Clients now never report any stream end reason except 'MISC'.
14653 Implements proposal 148.
14655 o Major bugfixes (crashes):
14656 - Parse dates and IPv4 addresses in a locale- and libc-independent
14657 manner, to avoid platform-dependent behavior on malformed input.
14658 - Fix a crash that occurs on exit nodes when a nameserver request
14659 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
14660 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
14662 - Do not assume that a stack-allocated character array will be
14663 64-bit aligned on platforms that demand that uint64_t access is
14664 aligned. Possible fix for bug 604.
14665 - Resolve a very rare crash bug that could occur when the user forced
14666 a nameserver reconfiguration during the middle of a nameserver
14667 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
14668 - Avoid a "0 divided by 0" calculation when calculating router uptime
14669 at directory authorities. Bugfix on 0.2.0.8-alpha.
14670 - Fix an assertion bug in parsing policy-related options; possible fix
14672 - Rate-limit too-many-sockets messages: when they happen, they happen
14673 a lot and end up filling up the disk. Resolves bug 748.
14674 - Fix a race condition that could cause crashes or memory corruption
14675 when running as a server with a controller listening for log
14677 - Avoid crashing when we have a policy specified in a DirPolicy or
14678 SocksPolicy or ReachableAddresses option with ports set on it,
14679 and we re-load the policy. May fix bug 996.
14680 - Fix an assertion failure on 64-bit platforms when we allocated
14681 memory right up to the end of a memarea, then realigned the memory
14682 one step beyond the end. Fixes a possible cause of bug 930.
14683 - Protect the count of open sockets with a mutex, so we can't
14684 corrupt it when two threads are closing or opening sockets at once.
14685 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
14687 o Major bugfixes (clients):
14688 - Discard router descriptors as we load them if they are more than
14689 five days old. Otherwise if Tor is off for a long time and then
14690 starts with cached descriptors, it will try to use the onion keys
14691 in those obsolete descriptors when building circuits. Fixes bug 887.
14692 - When we choose to abandon a new entry guard because we think our
14693 older ones might be better, close any circuits pending on that
14694 new entry guard connection. This fix should make us recover much
14695 faster when our network is down and then comes back. Bugfix on
14696 0.1.2.8-beta; found by lodger.
14697 - When Tor clients restart after 1-5 days, they discard all their
14698 cached descriptors as too old, but they still use the cached
14699 consensus document. This approach is good for robustness, but
14700 bad for performance: since they don't know any bandwidths, they
14701 end up choosing at random rather than weighting their choice by
14702 speed. Fixed by the above feature of putting bandwidths in the
14705 o Major bugfixes (relays):
14706 - Relays were falling out of the networkstatus consensus for
14707 part of a day if they changed their local config but the
14708 authorities discarded their new descriptor as "not sufficiently
14709 different". Now directory authorities accept a descriptor as changed
14710 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
14711 patch by Sebastian.
14712 - Ensure that two circuits can never exist on the same connection
14713 with the same circuit ID, even if one is marked for close. This
14714 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
14715 - Directory authorities were neglecting to mark relays down in their
14716 internal histories if the relays fall off the routerlist without
14717 ever being found unreachable. So there were relays in the histories
14718 that haven't been seen for eight months, and are listed as being
14719 up for eight months. This wreaked havoc on the "median wfu" and
14720 "median mtbf" calculations, in turn making Guard and Stable flags
14721 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
14724 o Major bugfixes (hidden services):
14725 - When establishing a hidden service, introduction points that
14726 originate from cannibalized circuits were completely ignored
14727 and not included in rendezvous service descriptors. This might
14728 have been another reason for delay in making a hidden service
14729 available. Bugfix from long ago (0.0.9.x?)
14731 o Major bugfixes (memory and resource management):
14732 - Fixed some memory leaks -- some quite frequent, some almost
14733 impossible to trigger -- based on results from Coverity.
14734 - Speed up parsing and cut down on memory fragmentation by using
14735 stack-style allocations for parsing directory objects. Previously,
14736 this accounted for over 40% of allocations from within Tor's code
14737 on a typical directory cache.
14738 - Use a Bloom filter rather than a digest-based set to track which
14739 descriptors we need to keep around when we're cleaning out old
14740 router descriptors. This speeds up the computation significantly,
14741 and may reduce fragmentation.
14743 o New/changed config options:
14744 - Now NodeFamily and MyFamily config options allow spaces in
14745 identity fingerprints, so it's easier to paste them in.
14746 Suggested by Lucky Green.
14747 - Allow ports 465 and 587 in the default exit policy again. We had
14748 rejected them in 0.1.0.15, because back in 2005 they were commonly
14749 misconfigured and ended up as spam targets. We hear they are better
14750 locked down these days.
14751 - Make TrackHostExit mappings expire a while after their last use, not
14752 after their creation. Patch from Robert Hogan.
14753 - Add an ExcludeExitNodes option so users can list a set of nodes
14754 that should be be excluded from the exit node position, but
14755 allowed elsewhere. Implements proposal 151.
14756 - New --hush command-line option similar to --quiet. While --quiet
14757 disables all logging to the console on startup, --hush limits the
14758 output to messages of warning and error severity.
14759 - New configure/torrc options (--enable-geoip-stats,
14760 DirRecordUsageByCountry) to record how many IPs we've served
14761 directory info to in each country code, how many status documents
14762 total we've sent to each country code, and what share of the total
14763 directory requests we should expect to see.
14764 - Make outbound DNS packets respect the OutboundBindAddress setting.
14765 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
14766 - Allow separate log levels to be configured for different logging
14767 domains. For example, this allows one to log all notices, warnings,
14768 or errors, plus all memory management messages of level debug or
14769 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
14770 - Update to the "June 3 2009" ip-to-country file.
14772 o Minor features (relays):
14773 - Raise the minimum rate limiting to be a relay from 20000 bytes
14774 to 20480 bytes (aka 20KB/s), to match our documentation. Also
14775 update directory authorities so they always assign the Fast flag
14776 to relays with 20KB/s of capacity. Now people running relays won't
14777 suddenly find themselves not seeing any use, if the network gets
14779 - If we're a relay and we change our IP address, be more verbose
14780 about the reason that made us change. Should help track down
14781 further bugs for relays on dynamic IP addresses.
14782 - Exit servers can now answer resolve requests for ip6.arpa addresses.
14783 - Implement most of Proposal 152: allow specialized servers to permit
14784 single-hop circuits, and clients to use those servers to build
14785 single-hop circuits when using a specialized controller. Patch
14786 from Josh Albrecht. Resolves feature request 768.
14787 - When relays do their initial bandwidth measurement, don't limit
14788 to just our entry guards for the test circuits. Otherwise we tend
14789 to have multiple test circuits going through a single entry guard,
14790 which makes our bandwidth test less accurate. Fixes part of bug 654;
14791 patch contributed by Josh Albrecht.
14793 o Minor features (directory authorities):
14794 - Try not to open more than one descriptor-downloading connection
14795 to an authority at once. This should reduce load on directory
14796 authorities. Fixes bug 366.
14797 - Add cross-certification to newly generated certificates, so that
14798 a signing key is enough information to look up a certificate. Start
14799 serving certificates by <identity digest, signing key digest>
14800 pairs. Implements proposal 157.
14801 - When a directory authority downloads a descriptor that it then
14802 immediately rejects, do not retry downloading it right away. Should
14803 save some bandwidth on authorities. Fix for bug 888. Patch by
14805 - Directory authorities now serve a /tor/dbg-stability.txt URL to
14806 help debug WFU and MTBF calculations.
14807 - In directory authorities' approved-routers files, allow
14808 fingerprints with or without space.
14810 o Minor features (directory mirrors):
14811 - When a download gets us zero good descriptors, do not notify
14812 Tor that new directory information has arrived.
14813 - Servers support a new URL scheme for consensus downloads that
14814 allows the client to specify which authorities are trusted.
14815 The server then only sends the consensus if the client will trust
14816 it. Otherwise a 404 error is sent back. Clients use this
14817 new scheme when the server supports it (meaning it's running
14818 0.2.1.1-alpha or later). Implements proposal 134.
14820 o Minor features (bridges):
14821 - If the bridge config line doesn't specify a port, assume 443.
14822 This makes bridge lines a bit smaller and easier for users to
14824 - If we're using bridges and our network goes away, be more willing
14825 to forgive our bridges and try again when we get an application
14828 o Minor features (hidden services):
14829 - When the client launches an introduction circuit, retry with a
14830 new circuit after 30 seconds rather than 60 seconds.
14831 - Launch a second client-side introduction circuit in parallel
14832 after a delay of 15 seconds (based on work by Christian Wilms).
14833 - Hidden services start out building five intro circuits rather
14834 than three, and when the first three finish they publish a service
14835 descriptor using those. Now we publish our service descriptor much
14836 faster after restart.
14837 - Drop the requirement to have an open dir port for storing and
14838 serving v2 hidden service descriptors.
14840 o Minor features (build and packaging):
14841 - On Linux, use the prctl call to re-enable core dumps when the User
14843 - Try to make sure that the version of Libevent we're running with
14844 is binary-compatible with the one we built with. May address bug
14846 - Add a new --enable-local-appdata configuration switch to change
14847 the default location of the datadir on win32 from APPDATA to
14848 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
14849 entirely. Patch from coderman.
14850 - Build correctly against versions of OpenSSL 0.9.8 or later that
14851 are built without support for deprecated functions.
14852 - On platforms with a maximum syslog string length, truncate syslog
14853 messages to that length ourselves, rather than relying on the
14854 system to do it for us.
14855 - Automatically detect MacOSX versions earlier than 10.4.0, and
14856 disable kqueue from inside Tor when running with these versions.
14857 We previously did this from the startup script, but that was no
14858 help to people who didn't use the startup script. Resolves bug 863.
14859 - Build correctly when configured to build outside the main source
14860 path. Patch from Michael Gold.
14861 - Disable GCC's strict alias optimization by default, to avoid the
14862 likelihood of its introducing subtle bugs whenever our code violates
14863 the letter of C99's alias rules.
14864 - Change the contrib/tor.logrotate script so it makes the new
14865 logs as "_tor:_tor" rather than the default, which is generally
14866 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
14867 - Change our header file guard macros to be less likely to conflict
14868 with system headers. Adam Langley noticed that we were conflicting
14869 with log.h on Android.
14870 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
14871 and stop using a warning that had become unfixably verbose under
14873 - Use a lockfile to make sure that two Tor processes are not
14874 simultaneously running with the same datadir.
14875 - Allow OpenSSL to use dynamic locks if it wants.
14876 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
14878 o Minor features (controllers):
14879 - When generating circuit events with verbose nicknames for
14880 controllers, try harder to look up nicknames for routers on a
14881 circuit. (Previously, we would look in the router descriptors we had
14882 for nicknames, but not in the consensus.) Partial fix for bug 941.
14883 - New controller event NEWCONSENSUS that lists the networkstatus
14884 lines for every recommended relay. Now controllers like Torflow
14885 can keep up-to-date on which relays they should be using.
14886 - New controller event "clients_seen" to report a geoip-based summary
14887 of which countries we've seen clients from recently. Now controllers
14888 like Vidalia can show bridge operators that they're actually making
14890 - Add a 'getinfo status/clients-seen' controller command, in case
14891 controllers want to hear clients_seen events but connect late.
14892 - New CONSENSUS_ARRIVED event to note when a new consensus has
14893 been fetched and validated.
14894 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
14895 controllers to prevent SIGHUP from reloading the configuration.
14897 - Return circuit purposes in response to GETINFO circuit-status.
14899 - Serve the latest v3 networkstatus consensus via the control
14900 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
14901 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
14902 controller can query our current bootstrap state in case it attaches
14903 partway through and wants to catch up.
14904 - Provide circuit purposes along with circuit events to the controller.
14906 o Minor features (tools):
14907 - Do not have tor-resolve automatically refuse all .onion addresses;
14908 if AutomapHostsOnResolve is set in your torrc, this will work fine.
14909 - Add a -p option to tor-resolve for specifying the SOCKS port: some
14910 people find host:port too confusing.
14911 - Print the SOCKS5 error message string as well as the error code
14912 when a tor-resolve request fails. Patch from Jacob.
14914 o Minor bugfixes (memory and resource management):
14915 - Clients no longer cache certificates for authorities they do not
14916 recognize. Bugfix on 0.2.0.9-alpha.
14917 - Do not use C's stdio library for writing to log files. This will
14918 improve logging performance by a minute amount, and will stop
14919 leaking fds when our disk is full. Fixes bug 861.
14920 - Stop erroneous use of O_APPEND in cases where we did not in fact
14921 want to re-seek to the end of a file before every last write().
14922 - Fix a small alignment and memory-wasting bug on buffer chunks.
14924 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
14925 to avoid unused RAM in buffer chunks and memory pools.
14926 - Reduce the default smartlist size from 32 to 16; it turns out that
14927 most smartlists hold around 8-12 elements tops.
14928 - Make dumpstats() log the fullness and size of openssl-internal
14930 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
14931 patch to their OpenSSL, turn it on to save memory on servers. This
14932 patch will (with any luck) get included in a mainline distribution
14934 - Fix a memory leak when v3 directory authorities load their keys
14935 and cert from disk. Bugfix on 0.2.0.1-alpha.
14936 - Stop using malloc_usable_size() to use more area than we had
14937 actually allocated: it was safe, but made valgrind really unhappy.
14938 - Make the assert_circuit_ok() function work correctly on circuits that
14939 have already been marked for close.
14940 - Fix uninitialized size field for memory area allocation: may improve
14941 memory performance during directory parsing.
14943 o Minor bugfixes (clients):
14944 - Stop reloading the router list from disk for no reason when we
14945 run out of reachable directory mirrors. Once upon a time reloading
14946 it would set the 'is_running' flag back to 1 for them. It hasn't
14947 done that for a long time.
14948 - When we had picked an exit node for a connection, but marked it as
14949 "optional", and it turned out we had no onion key for the exit,
14950 stop wanting that exit and try again. This situation may not
14951 be possible now, but will probably become feasible with proposal
14952 158. Spotted by rovv. Fixes another case of bug 752.
14953 - Fix a bug in address parsing that was preventing bridges or hidden
14954 service targets from being at IPv6 addresses.
14955 - Do not remove routers as too old if we do not have any consensus
14956 document. Bugfix on 0.2.0.7-alpha.
14957 - When an exit relay resolves a stream address to a local IP address,
14958 do not just keep retrying that same exit relay over and
14959 over. Instead, just close the stream. Addresses bug 872. Bugfix
14960 on 0.2.0.32. Patch from rovv.
14961 - Made Tor a little less aggressive about deleting expired
14962 certificates. Partial fix for bug 854.
14963 - Treat duplicate certificate fetches as failures, so that we do
14964 not try to re-fetch an expired certificate over and over and over.
14965 - Do not say we're fetching a certificate when we'll in fact skip it
14966 because of a pending download.
14967 - If we have correct permissions on $datadir, we complain to stdout
14968 and fail to start. But dangerous permissions on
14969 $datadir/cached-status/ would cause us to open a log and complain
14970 there. Now complain to stdout and fail to start in both cases. Fixes
14971 bug 820, reported by seeess.
14973 o Minor bugfixes (bridges):
14974 - When we made bridge authorities stop serving bridge descriptors over
14975 unencrypted links, we also broke DirPort reachability testing for
14976 bridges. So bridges with a non-zero DirPort were printing spurious
14977 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
14978 - Don't allow a bridge to publish its router descriptor to a
14979 non-bridge directory authority. Fixes part of bug 932.
14980 - When we change to or from being a bridge, reset our counts of
14981 client usage by country. Fixes bug 932.
14983 o Minor bugfixes (relays):
14984 - Log correct error messages for DNS-related network errors on
14986 - Actually return -1 in the error case for read_bandwidth_usage().
14987 Harmless bug, since we currently don't care about the return value
14988 anywhere. Bugfix on 0.2.0.9-alpha.
14989 - Provide a more useful log message if bug 977 (related to buffer
14990 freelists) ever reappears, and do not crash right away.
14991 - We were already rejecting relay begin cells with destination port
14992 of 0. Now also reject extend cells with destination port or address
14993 of 0. Suggested by lark.
14994 - When we can't transmit a DNS request due to a network error, retry
14995 it after a while, and eventually transmit a failing response to
14996 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
14997 - Solve a bug that kept hardware crypto acceleration from getting
14998 enabled when accounting was turned on. Fixes bug 907. Bugfix on
15000 - When a canonical connection appears later in our internal list
15001 than a noncanonical one for a given OR ID, always use the
15002 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
15004 - Avoid some nasty corner cases in the logic for marking connections
15005 as too old or obsolete or noncanonical for circuits. Partial
15007 - Fix another interesting corner-case of bug 891 spotted by rovv:
15008 Previously, if two hosts had different amounts of clock drift, and
15009 one of them created a new connection with just the wrong timing,
15010 the other might decide to deprecate the new connection erroneously.
15011 Bugfix on 0.1.1.13-alpha.
15012 - If one win32 nameserver fails to get added, continue adding the
15013 rest, and don't automatically fail.
15014 - Fix a bug where an unreachable relay would establish enough
15015 reachability testing circuits to do a bandwidth test -- if
15016 we already have a connection to the middle hop of the testing
15017 circuit, then it could establish the last hop by using the existing
15018 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
15019 circuits no longer use entry guards in 0.2.1.3-alpha.
15021 o Minor bugfixes (directory authorities):
15022 - Limit uploaded directory documents to be 16M rather than 500K.
15023 The directory authorities were refusing v3 consensus votes from
15024 other authorities, since the votes are now 504K. Fixes bug 959;
15025 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
15026 - Directory authorities should never send a 503 "busy" response to
15027 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
15029 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
15030 headers. Bugfix on 0.2.0.10-alpha.
15032 o Minor bugfixes (hidden services):
15033 - When we can't find an intro key for a v2 hidden service descriptor,
15034 fall back to the v0 hidden service descriptor and log a bug message.
15035 Workaround for bug 1024.
15036 - In very rare situations new hidden service descriptors were
15037 published earlier than 30 seconds after the last change to the
15038 service. (We currently think that a hidden service descriptor
15039 that's been stable for 30 seconds is worth publishing.)
15040 - If a hidden service sends us an END cell, do not consider
15041 retrying the connection; just close it. Patch from rovv.
15042 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
15043 service directories if they have no advertised dir port. Bugfix
15046 o Minor bugfixes (tools):
15047 - In the torify(1) manpage, mention that tsocks will leak your
15050 o Minor bugfixes (controllers):
15051 - If the controller claimed responsibility for a stream, but that
15052 stream never finished making its connection, it would live
15053 forever in circuit_wait state. Now we close it after SocksTimeout
15054 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
15055 - Make DNS resolved controller events into "CLOSED", not
15056 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
15058 - The control port would close the connection before flushing long
15059 replies, such as the network consensus, if a QUIT command was issued
15060 before the reply had completed. Now, the control port flushes all
15061 pending replies before closing the connection. Also fix a spurious
15062 warning when a QUIT command is issued after a malformed or rejected
15063 AUTHENTICATE command, but before the connection was closed. Patch
15064 by Marcus Griep. Fixes bugs 1015 and 1016.
15065 - Fix a bug that made stream bandwidth get misreported to the
15068 o Deprecated and removed features:
15069 - The old "tor --version --version" command, which would print out
15070 the subversion "Id" of most of the source files, is now removed. It
15071 turned out to be less useful than we'd expected, and harder to
15073 - RedirectExits has been removed. It was deprecated since
15075 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
15076 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
15077 - Cell pools are now always enabled; --disable-cell-pools is ignored.
15078 - Directory mirrors no longer fetch the v1 directory or
15079 running-routers files. They are obsolete, and nobody asks for them
15080 anymore. This is the first step to making v1 authorities obsolete.
15081 - Take out the TestVia config option, since it was a workaround for
15082 a bug that was fixed in Tor 0.1.1.21.
15083 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
15084 HiddenServiceExcludeNodes as obsolete: they never worked properly,
15085 and nobody seems to be using them. Fixes bug 754. Bugfix on
15086 0.1.0.1-rc. Patch from Christian Wilms.
15087 - Remove all backward-compatibility code for relays running
15088 versions of Tor so old that they no longer work at all on the
15091 o Code simplifications and refactoring:
15092 - Tool-assisted documentation cleanup. Nearly every function or
15093 static variable in Tor should have its own documentation now.
15094 - Rename the confusing or_is_obsolete field to the more appropriate
15095 is_bad_for_new_circs, and move it to or_connection_t where it
15097 - Move edge-only flags from connection_t to edge_connection_t: not
15098 only is this better coding, but on machines of plausible alignment,
15099 it should save 4-8 bytes per connection_t. "Every little bit helps."
15100 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
15101 for consistency; keep old option working for backward compatibility.
15102 - Simplify the code for finding connections to use for a circuit.
15103 - Revise the connection_new functions so that a more typesafe variant
15104 exists. This will work better with Coverity, and let us find any
15105 actual mistakes we're making here.
15106 - Refactor unit testing logic so that dmalloc can be used sensibly
15107 with unit tests to check for memory leaks.
15108 - Move all hidden-service related fields from connection and circuit
15109 structure to substructures: this way they won't eat so much memory.
15110 - Squeeze 2-5% out of client performance (according to oprofile) by
15111 improving the implementation of some policy-manipulation functions.
15112 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
15113 be more efficient. Formerly it was quadratic in the number of
15114 servers; now it should be linear. Fixes bug 509.
15115 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
15116 and n_conn_id_digest fields into a separate structure that's
15117 only needed when the circuit has not yet attached to an n_conn.
15118 - Optimize out calls to time(NULL) that occur for every IO operation,
15119 or for every cell. On systems like Windows where time() is a
15120 slow syscall, this fix will be slightly helpful.
15123 Changes in version 0.2.0.35 - 2009-06-24
15125 - Avoid crashing in the presence of certain malformed descriptors.
15126 Found by lark, and by automated fuzzing.
15127 - Fix an edge case where a malicious exit relay could convince a
15128 controller that the client's DNS question resolves to an internal IP
15129 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
15132 - Finally fix the bug where dynamic-IP relays disappear when their
15133 IP address changes: directory mirrors were mistakenly telling
15134 them their old address if they asked via begin_dir, so they
15135 never got an accurate answer about their new address, so they
15136 just vanished after a day. For belt-and-suspenders, relays that
15137 don't set Address in their config now avoid using begin_dir for
15138 all direct connections. Should fix bugs 827, 883, and 900.
15139 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
15140 that would occur on some exit nodes when DNS failures and timeouts
15141 occurred in certain patterns. Fix for bug 957.
15144 - When starting with a cache over a few days old, do not leak
15145 memory for the obsolete router descriptors in it. Bugfix on
15146 0.2.0.33; fixes bug 672.
15147 - Hidden service clients didn't use a cached service descriptor that
15148 was older than 15 minutes, but wouldn't fetch a new one either,
15149 because there was already one in the cache. Now, fetch a v2
15150 descriptor unless the same descriptor was added to the cache within
15151 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
15154 Changes in version 0.2.0.34 - 2009-02-08
15155 Tor 0.2.0.34 features several more security-related fixes. You should
15156 upgrade, especially if you run an exit relay (remote crash) or a
15157 directory authority (remote infinite loop), or you're on an older
15158 (pre-XP) or not-recently-patched Windows (remote exploit).
15160 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
15161 have many known flaws, and nobody should be using them. You should
15162 upgrade. If you're using a Linux or BSD and its packages are obsolete,
15163 stop using those packages and upgrade anyway.
15166 - Fix an infinite-loop bug on handling corrupt votes under certain
15167 circumstances. Bugfix on 0.2.0.8-alpha.
15168 - Fix a temporary DoS vulnerability that could be performed by
15169 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
15170 - Avoid a potential crash on exit nodes when processing malformed
15171 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
15172 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
15173 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
15176 - Fix compilation on systems where time_t is a 64-bit integer.
15177 Patch from Matthias Drochner.
15178 - Don't consider expiring already-closed client connections. Fixes
15179 bug 893. Bugfix on 0.0.2pre20.
15182 Changes in version 0.2.0.33 - 2009-01-21
15183 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
15184 useful to users. It also finally fixes a bug where a relay or client
15185 that's been off for many days would take a long time to bootstrap.
15187 This update also fixes an important security-related bug reported by
15188 Ilja van Sprundel. You should upgrade. (We'll send out more details
15189 about the bug once people have had some time to upgrade.)
15192 - Fix a heap-corruption bug that may be remotely triggerable on
15193 some platforms. Reported by Ilja van Sprundel.
15196 - When a stream at an exit relay is in state "resolving" or
15197 "connecting" and it receives an "end" relay cell, the exit relay
15198 would silently ignore the end cell and not close the stream. If
15199 the client never closes the circuit, then the exit relay never
15200 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
15201 reported by "wood".
15202 - When sending CREATED cells back for a given circuit, use a 64-bit
15203 connection ID to find the right connection, rather than an addr:port
15204 combination. Now that we can have multiple OR connections between
15205 the same ORs, it is no longer possible to use addr:port to uniquely
15206 identify a connection.
15207 - Bridge relays that had DirPort set to 0 would stop fetching
15208 descriptors shortly after startup, and then briefly resume
15209 after a new bandwidth test and/or after publishing a new bridge
15210 descriptor. Bridge users that try to bootstrap from them would
15211 get a recent networkstatus but would get descriptors from up to
15212 18 hours earlier, meaning most of the descriptors were obsolete
15213 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
15214 - Prevent bridge relays from serving their 'extrainfo' document
15215 to anybody who asks, now that extrainfo docs include potentially
15216 sensitive aggregated client geoip summaries. Bugfix on
15218 - If the cached networkstatus consensus is more than five days old,
15219 discard it rather than trying to use it. In theory it could be
15220 useful because it lists alternate directory mirrors, but in practice
15221 it just means we spend many minutes trying directory mirrors that
15222 are long gone from the network. Also discard router descriptors as
15223 we load them if they are more than five days old, since the onion
15224 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
15227 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
15228 could make gcc generate non-functional binary search code. Bugfix
15230 - Build correctly on platforms without socklen_t.
15231 - Compile without warnings on solaris.
15232 - Avoid potential crash on internal error during signature collection.
15233 Fixes bug 864. Patch from rovv.
15234 - Correct handling of possible malformed authority signing key
15235 certificates with internal signature types. Fixes bug 880.
15236 Bugfix on 0.2.0.3-alpha.
15237 - Fix a hard-to-trigger resource leak when logging credential status.
15239 - When we can't initialize DNS because the network is down, do not
15240 automatically stop Tor from starting. Instead, we retry failed
15241 dns_init() every 10 minutes, and change the exit policy to reject
15242 *:* until one succeeds. Fixes bug 691.
15243 - Use 64 bits instead of 32 bits for connection identifiers used with
15244 the controller protocol, to greatly reduce risk of identifier reuse.
15245 - When we're choosing an exit node for a circuit, and we have
15246 no pending streams, choose a good general exit rather than one that
15247 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
15248 - Fix another case of assuming, when a specific exit is requested,
15249 that we know more than the user about what hosts it allows.
15250 Fixes one case of bug 752. Patch from rovv.
15251 - Clip the MaxCircuitDirtiness config option to a minimum of 10
15252 seconds. Warn the user if lower values are given in the
15253 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
15254 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
15255 user if lower values are given in the configuration. Bugfix on
15256 0.1.1.17-rc. Patch by Sebastian.
15257 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
15258 the cache because we already had a v0 descriptor with the same ID.
15259 Bugfix on 0.2.0.18-alpha.
15260 - Fix a race condition when freeing keys shared between main thread
15261 and CPU workers that could result in a memory leak. Bugfix on
15262 0.1.0.1-rc. Fixes bug 889.
15263 - Send a valid END cell back when a client tries to connect to a
15264 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
15265 840. Patch from rovv.
15266 - Check which hops rendezvous stream cells are associated with to
15267 prevent possible guess-the-streamid injection attacks from
15268 intermediate hops. Fixes another case of bug 446. Based on patch
15270 - If a broken client asks a non-exit router to connect somewhere,
15271 do not even do the DNS lookup before rejecting the connection.
15272 Fixes another case of bug 619. Patch from rovv.
15273 - When a relay gets a create cell it can't decrypt (e.g. because it's
15274 using the wrong onion key), we were dropping it and letting the
15275 client time out. Now actually answer with a destroy cell. Fixes
15276 bug 904. Bugfix on 0.0.2pre8.
15278 o Minor bugfixes (hidden services):
15279 - Do not throw away existing introduction points on SIGHUP. Bugfix on
15280 0.0.6pre1. Patch by Karsten. Fixes bug 874.
15283 - Report the case where all signatures in a detached set are rejected
15284 differently than the case where there is an error handling the
15286 - When we realize that another process has modified our cached
15287 descriptors, print out a more useful error message rather than
15288 triggering an assertion. Fixes bug 885. Patch from Karsten.
15289 - Implement the 0x20 hack to better resist DNS poisoning: set the
15290 case on outgoing DNS requests randomly, and reject responses that do
15291 not match the case correctly. This logic can be disabled with the
15292 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
15293 of servers that do not reliably preserve case in replies. See
15294 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
15296 - Check DNS replies for more matching fields to better resist DNS
15298 - Never use OpenSSL compression: it wastes RAM and CPU trying to
15299 compress cells, which are basically all encrypted, compressed, or
15303 Changes in version 0.2.0.32 - 2008-11-20
15304 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
15305 packages (and maybe other packages) noticed by Theo de Raadt, fixes
15306 a smaller security flaw that might allow an attacker to access local
15307 services, further improves hidden service performance, and fixes a
15308 variety of other issues.
15311 - The "User" and "Group" config options did not clear the
15312 supplementary group entries for the Tor process. The "User" option
15313 is now more robust, and we now set the groups to the specified
15314 user's primary group. The "Group" option is now ignored. For more
15315 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
15316 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
15317 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
15318 - The "ClientDNSRejectInternalAddresses" config option wasn't being
15319 consistently obeyed: if an exit relay refuses a stream because its
15320 exit policy doesn't allow it, we would remember what IP address
15321 the relay said the destination address resolves to, even if it's
15322 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
15325 - Fix a DOS opportunity during the voting signature collection process
15326 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
15328 o Major bugfixes (hidden services):
15329 - When fetching v0 and v2 rendezvous service descriptors in parallel,
15330 we were failing the whole hidden service request when the v0
15331 descriptor fetch fails, even if the v2 fetch is still pending and
15332 might succeed. Similarly, if the last v2 fetch fails, we were
15333 failing the whole hidden service request even if a v0 fetch is
15334 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
15335 - When extending a circuit to a hidden service directory to upload a
15336 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
15337 requests failed, because the router descriptor has not been
15338 downloaded yet. In these cases, do not attempt to upload the
15339 rendezvous descriptor, but wait until the router descriptor is
15340 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
15341 descriptor from a hidden service directory for which the router
15342 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
15346 - Fix several infrequent memory leaks spotted by Coverity.
15347 - When testing for libevent functions, set the LDFLAGS variable
15348 correctly. Found by Riastradh.
15349 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
15350 bootstrapping with tunneled directory connections. Bugfix on
15351 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
15352 - When asked to connect to A.B.exit:80, if we don't know the IP for A
15353 and we know that server B rejects most-but-not all connections to
15354 port 80, we would previously reject the connection. Now, we assume
15355 the user knows what they were asking for. Fixes bug 752. Bugfix
15356 on 0.0.9rc5. Diagnosed by BarkerJr.
15357 - If we overrun our per-second write limits a little, count this as
15358 having used up our write allocation for the second, and choke
15359 outgoing directory writes. Previously, we had only counted this when
15360 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
15361 Bugfix on 0.2.0.x (??).
15362 - Remove the old v2 directory authority 'lefkada' from the default
15363 list. It has been gone for many months.
15364 - Stop doing unaligned memory access that generated bus errors on
15365 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
15366 - Make USR2 log-level switch take effect immediately. Bugfix on
15369 o Minor bugfixes (controller):
15370 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
15371 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
15374 Changes in version 0.2.0.31 - 2008-09-03
15375 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
15376 a big bug we're seeing where in rare cases traffic from one Tor stream
15377 gets mixed into another stream, and fixes a variety of smaller issues.
15380 - Make sure that two circuits can never exist on the same connection
15381 with the same circuit ID, even if one is marked for close. This
15382 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
15383 - Relays now reject risky extend cells: if the extend cell includes
15384 a digest of all zeroes, or asks to extend back to the relay that
15385 sent the extend cell, tear down the circuit. Ideas suggested
15387 - If not enough of our entry guards are available so we add a new
15388 one, we might use the new one even if it overlapped with the
15389 current circuit's exit relay (or its family). Anonymity bugfix
15390 pointed out by rovv.
15393 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
15394 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
15395 - Correctly detect the presence of the linux/netfilter_ipv4.h header
15396 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
15397 - Pick size of default geoip filename string correctly on windows.
15398 Fixes bug 806. Bugfix on 0.2.0.30.
15399 - Make the autoconf script accept the obsolete --with-ssl-dir
15400 option as an alias for the actually-working --with-openssl-dir
15401 option. Fix the help documentation to recommend --with-openssl-dir.
15402 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
15403 - When using the TransPort option on OpenBSD, and using the User
15404 option to change UID and drop privileges, make sure to open
15405 /dev/pf before dropping privileges. Fixes bug 782. Patch from
15406 Christopher Davis. Bugfix on 0.1.2.1-alpha.
15407 - Try to attach connections immediately upon receiving a RENDEZVOUS2
15408 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
15409 on the client side when connecting to a hidden service. Bugfix
15410 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
15411 - When closing an application-side connection because its circuit is
15412 getting torn down, generate the stream event correctly. Bugfix on
15413 0.1.2.x. Anonymous patch.
15416 Changes in version 0.2.0.30 - 2008-07-15
15417 This new stable release switches to a more efficient directory
15418 distribution design, adds features to make connections to the Tor
15419 network harder to block, allows Tor to act as a DNS proxy, adds separate
15420 rate limiting for relayed traffic to make it easier for clients to
15421 become relays, fixes a variety of potential anonymity problems, and
15422 includes the usual huge pile of other features and bug fixes.
15424 o New v3 directory design:
15425 - Tor now uses a new way to learn about and distribute information
15426 about the network: the directory authorities vote on a common
15427 network status document rather than each publishing their own
15428 opinion. Now clients and caches download only one networkstatus
15429 document to bootstrap, rather than downloading one for each
15430 authority. Clients only download router descriptors listed in
15431 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
15433 - Set up moria1, tor26, and dizum as v3 directory authorities
15434 in addition to being v2 authorities. Also add three new ones:
15435 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
15436 dannenberg (run by CCC).
15437 - Switch to multi-level keys for directory authorities: now their
15438 long-term identity key can be kept offline, and they periodically
15439 generate a new signing key. Clients fetch the "key certificates"
15440 to keep up to date on the right keys. Add a standalone tool
15441 "tor-gencert" to generate key certificates. Implements proposal 103.
15442 - Add a new V3AuthUseLegacyKey config option to make it easier for
15443 v3 authorities to change their identity keys if another bug like
15444 Debian's OpenSSL RNG flaw appears.
15445 - Authorities and caches fetch the v2 networkstatus documents
15446 less often, now that v3 is recommended.
15448 o Make Tor connections stand out less on the wire:
15449 - Use an improved TLS handshake designed by Steven Murdoch in proposal
15450 124, as revised in proposal 130. The new handshake is meant to
15451 be harder for censors to fingerprint, and it adds the ability
15452 to detect certain kinds of man-in-the-middle traffic analysis
15453 attacks. The new handshake format includes version negotiation for
15454 OR connections as described in proposal 105, which will allow us
15455 to improve Tor's link protocol more safely in the future.
15456 - Enable encrypted directory connections by default for non-relays,
15457 so censor tools that block Tor directory connections based on their
15458 plaintext patterns will no longer work. This means Tor works in
15459 certain censored countries by default again.
15460 - Stop including recognizeable strings in the commonname part of
15461 Tor's x509 certificates.
15463 o Implement bridge relays:
15464 - Bridge relays (or "bridges" for short) are Tor relays that aren't
15465 listed in the main Tor directory. Since there is no complete public
15466 list of them, even an ISP that is filtering connections to all the
15467 known Tor relays probably won't be able to block all the bridges.
15468 See doc/design-paper/blocking.pdf and proposal 125 for details.
15469 - New config option BridgeRelay that specifies you want to be a
15470 bridge relay rather than a normal relay. When BridgeRelay is set
15471 to 1, then a) you cache dir info even if your DirPort ins't on,
15472 and b) the default for PublishServerDescriptor is now "bridge"
15473 rather than "v2,v3".
15474 - New config option "UseBridges 1" for clients that want to use bridge
15475 relays instead of ordinary entry guards. Clients then specify
15476 bridge relays by adding "Bridge" lines to their config file. Users
15477 can learn about a bridge relay either manually through word of
15478 mouth, or by one of our rate-limited mechanisms for giving out
15479 bridge addresses without letting an attacker easily enumerate them
15480 all. See https://www.torproject.org/bridges for details.
15481 - Bridge relays behave like clients with respect to time intervals
15482 for downloading new v3 consensus documents -- otherwise they
15483 stand out. Bridge users now wait until the end of the interval,
15484 so their bridge relay will be sure to have a new consensus document.
15486 o Implement bridge directory authorities:
15487 - Bridge authorities are like normal directory authorities, except
15488 they don't serve a list of known bridges. Therefore users that know
15489 a bridge's fingerprint can fetch a relay descriptor for that bridge,
15490 including fetching updates e.g. if the bridge changes IP address,
15491 yet an attacker can't just fetch a list of all the bridges.
15492 - Set up Tonga as the default bridge directory authority.
15493 - Bridge authorities refuse to serve bridge descriptors or other
15494 bridge information over unencrypted connections (that is, when
15495 responding to direct DirPort requests rather than begin_dir cells.)
15496 - Bridge directory authorities do reachability testing on the
15497 bridges they know. They provide router status summaries to the
15498 controller via "getinfo ns/purpose/bridge", and also dump summaries
15499 to a file periodically, so we can keep internal stats about which
15500 bridges are functioning.
15501 - If bridge users set the UpdateBridgesFromAuthority config option,
15502 but the digest they ask for is a 404 on the bridge authority,
15503 they fall back to contacting the bridge directly.
15504 - Bridges always use begin_dir to publish their server descriptor to
15505 the bridge authority using an anonymous encrypted tunnel.
15506 - Early work on a "bridge community" design: if bridge authorities set
15507 the BridgePassword config option, they will serve a snapshot of
15508 known bridge routerstatuses from their DirPort to anybody who
15509 knows that password. Unset by default.
15510 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
15511 report sanitized aggregated summaries in their extra-info documents
15512 privately to the bridge authority, listing which countries are
15513 able to reach them. We hope this mechanism will let us learn when
15514 certain countries start trying to block bridges.
15515 - Bridge authorities write bridge descriptors to disk, so they can
15516 reload them after a reboot. They can also export the descriptors
15517 to other programs, so we can distribute them to blocked users via
15518 the BridgeDB interface, e.g. via https://bridges.torproject.org/
15519 and bridges@torproject.org.
15521 o Tor can be a DNS proxy:
15522 - The new client-side DNS proxy feature replaces the need for
15523 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
15524 for DNS requests on port 9999, use the Tor network to resolve them
15525 anonymously, and send the reply back like a regular DNS server.
15526 The code still only implements a subset of DNS.
15527 - Add a new AutomapHostsOnResolve option: when it is enabled, any
15528 resolve request for hosts matching a given pattern causes Tor to
15529 generate an internal virtual address mapping for that host. This
15530 allows DNSPort to work sensibly with hidden service users. By
15531 default, .exit and .onion addresses are remapped; the list of
15532 patterns can be reconfigured with AutomapHostsSuffixes.
15533 - Add an "-F" option to tor-resolve to force a resolve for a .onion
15534 address. Thanks to the AutomapHostsOnResolve option, this is no
15535 longer a completely silly thing to do.
15537 o Major features (relay usability):
15538 - New config options RelayBandwidthRate and RelayBandwidthBurst:
15539 a separate set of token buckets for relayed traffic. Right now
15540 relayed traffic is defined as answers to directory requests, and
15541 OR connections that don't have any local circuits on them. See
15542 proposal 111 for details.
15543 - Create listener connections before we setuid to the configured
15544 User and Group. Now non-Windows users can choose port values
15545 under 1024, start Tor as root, and have Tor bind those ports
15546 before it changes to another UID. (Windows users could already
15548 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
15549 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
15550 on "vserver" accounts. Patch from coderman.
15552 o Major features (directory authorities):
15553 - Directory authorities track weighted fractional uptime and weighted
15554 mean-time-between failures for relays. WFU is suitable for deciding
15555 whether a node is "usually up", while MTBF is suitable for deciding
15556 whether a node is "likely to stay up." We need both, because
15557 "usually up" is a good requirement for guards, while "likely to
15558 stay up" is a good requirement for long-lived connections.
15559 - Directory authorities use a new formula for selecting which relays
15560 to advertise as Guards: they must be in the top 7/8 in terms of
15561 how long we have known about them, and above the median of those
15562 nodes in terms of weighted fractional uptime.
15563 - Directory authorities use a new formula for selecting which relays
15564 to advertise as Stable: when we have 4 or more days of data, use
15565 median measured MTBF rather than median declared uptime. Implements
15567 - Directory authorities accept and serve "extra info" documents for
15568 routers. Routers now publish their bandwidth-history lines in the
15569 extra-info docs rather than the main descriptor. This step saves
15570 60% (!) on compressed router descriptor downloads. Servers upload
15571 extra-info docs to any authority that accepts them; directory
15572 authorities now allow multiple router descriptors and/or extra
15573 info documents to be uploaded in a single go. Authorities, and
15574 caches that have been configured to download extra-info documents,
15575 download them as needed. Implements proposal 104.
15576 - Authorities now list relays who have the same nickname as
15577 a different named relay, but list them with a new flag:
15578 "Unnamed". Now we can make use of relays that happen to pick the
15579 same nickname as a server that registered two years ago and then
15580 disappeared. Implements proposal 122.
15581 - Store routers in a file called cached-descriptors instead of in
15582 cached-routers. Initialize cached-descriptors from cached-routers
15583 if the old format is around. The new format allows us to store
15584 annotations along with descriptors, to record the time we received
15585 each descriptor, its source, and its purpose: currently one of
15586 general, controller, or bridge.
15588 o Major features (other):
15589 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
15590 Tor can warn and/or refuse connections to ports commonly used with
15591 vulnerable-plaintext protocols. Currently we warn on ports 23,
15592 109, 110, and 143, but we don't reject any. Based on proposal 129
15593 by Kevin Bauer and Damon McCoy.
15594 - Integrate Karsten Loesing's Google Summer of Code project to publish
15595 hidden service descriptors on a set of redundant relays that are a
15596 function of the hidden service address. Now we don't have to rely
15597 on three central hidden service authorities for publishing and
15598 fetching every hidden service descriptor. Implements proposal 114.
15599 - Allow tunnelled directory connections to ask for an encrypted
15600 "begin_dir" connection or an anonymized "uses a full Tor circuit"
15601 connection independently. Now we can make anonymized begin_dir
15602 connections for (e.g.) more secure hidden service posting and
15605 o Major bugfixes (crashes and assert failures):
15606 - Stop imposing an arbitrary maximum on the number of file descriptors
15607 used for busy servers. Bug reported by Olaf Selke; patch from
15609 - Avoid possible failures when generating a directory with routers
15610 with over-long versions strings, or too many flags set.
15611 - Fix a rare assert error when we're closing one of our threads:
15612 use a mutex to protect the list of logs, so we never write to the
15613 list as it's being freed. Fixes the very rare bug 575, which is
15614 kind of the revenge of bug 222.
15615 - Avoid segfault in the case where a badly behaved v2 versioning
15616 directory sends a signed networkstatus with missing client-versions.
15617 - When we hit an EOF on a log (probably because we're shutting down),
15618 don't try to remove the log from the list: just mark it as
15619 unusable. (Bulletproofs against bug 222.)
15621 o Major bugfixes (code security fixes):
15622 - Detect size overflow in zlib code. Reported by Justin Ferguson and
15624 - Rewrite directory tokenization code to never run off the end of
15625 a string. Fixes bug 455. Patch from croup.
15626 - Be more paranoid about overwriting sensitive memory on free(),
15627 as a defensive programming tactic to ensure forward secrecy.
15629 o Major bugfixes (anonymity fixes):
15630 - Reject requests for reverse-dns lookup of names that are in
15631 a private address space. Patch from lodger.
15632 - Never report that we've used more bandwidth than we're willing to
15633 relay: it leaks how much non-relay traffic we're using. Resolves
15635 - As a client, do not believe any server that tells us that an
15636 address maps to an internal address space.
15637 - Warn about unsafe ControlPort configurations.
15638 - Directory authorities now call routers Fast if their bandwidth is
15639 at least 100KB/s, and consider their bandwidth adequate to be a
15640 Guard if it is at least 250KB/s, no matter the medians. This fix
15641 complements proposal 107.
15642 - Directory authorities now never mark more than 2 servers per IP as
15643 Valid and Running (or 5 on addresses shared by authorities).
15644 Implements proposal 109, by Kevin Bauer and Damon McCoy.
15645 - If we're a relay, avoid picking ourselves as an introduction point,
15646 a rendezvous point, or as the final hop for internal circuits. Bug
15647 reported by taranis and lodger.
15648 - Exit relays that are used as a client can now reach themselves
15649 using the .exit notation, rather than just launching an infinite
15650 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
15651 - Fix a bug where, when we were choosing the 'end stream reason' to
15652 put in our relay end cell that we send to the exit relay, Tor
15653 clients on Windows were sometimes sending the wrong 'reason'. The
15654 anonymity problem is that exit relays may be able to guess whether
15655 the client is running Windows, thus helping partition the anonymity
15656 set. Down the road we should stop sending reasons to exit relays,
15657 or otherwise prevent future versions of this bug.
15658 - Only update guard status (usable / not usable) once we have
15659 enough directory information. This was causing us to discard all our
15660 guards on startup if we hadn't been running for a few weeks. Fixes
15662 - When our directory information has been expired for a while, stop
15663 being willing to build circuits using it. Fixes bug 401.
15665 o Major bugfixes (peace of mind for relay operators)
15666 - Non-exit relays no longer answer "resolve" relay cells, so they
15667 can't be induced to do arbitrary DNS requests. (Tor clients already
15668 avoid using non-exit relays for resolve cells, but now servers
15669 enforce this too.) Fixes bug 619. Patch from lodger.
15670 - When we setconf ClientOnly to 1, close any current OR and Dir
15671 listeners. Reported by mwenge.
15673 o Major bugfixes (other):
15674 - If we only ever used Tor for hidden service lookups or posts, we
15675 would stop building circuits and start refusing connections after
15676 24 hours, since we falsely believed that Tor was dormant. Reported
15678 - Add a new __HashedControlSessionPassword option for controllers
15679 to use for one-off session password hashes that shouldn't get
15680 saved to disk by SAVECONF --- Vidalia users were accumulating a
15681 pile of HashedControlPassword lines in their torrc files, one for
15682 each time they had restarted Tor and then clicked Save. Make Tor
15683 automatically convert "HashedControlPassword" to this new option but
15684 only when it's given on the command line. Partial fix for bug 586.
15685 - Patch from "Andrew S. Lists" to catch when we contact a directory
15686 mirror at IP address X and he says we look like we're coming from
15687 IP address X. Otherwise this would screw up our address detection.
15688 - Reject uploaded descriptors and extrainfo documents if they're
15689 huge. Otherwise we'll cache them all over the network and it'll
15690 clog everything up. Suggested by Aljosha Judmayer.
15691 - When a hidden service was trying to establish an introduction point,
15692 and Tor *did* manage to reuse one of the preemptively built
15693 circuits, it didn't correctly remember which one it used,
15694 so it asked for another one soon after, until there were no
15695 more preemptive circuits, at which point it launched one from
15696 scratch. Bugfix on 0.0.9.x.
15698 o Rate limiting and load balancing improvements:
15699 - When we add data to a write buffer in response to the data on that
15700 write buffer getting low because of a flush, do not consider the
15701 newly added data as a candidate for immediate flushing, but rather
15702 make it wait until the next round of writing. Otherwise, we flush
15703 and refill recursively, and a single greedy TLS connection can
15704 eat all of our bandwidth.
15705 - When counting the number of bytes written on a TLS connection,
15706 look at the BIO actually used for writing to the network, not
15707 at the BIO used (sometimes) to buffer data for the network.
15708 Looking at different BIOs could result in write counts on the
15709 order of ULONG_MAX. Fixes bug 614.
15710 - If we change our MaxAdvertisedBandwidth and then reload torrc,
15711 Tor won't realize it should publish a new relay descriptor. Fixes
15712 bug 688, reported by mfr.
15713 - Avoid using too little bandwidth when our clock skips a few seconds.
15714 - Choose which bridge to use proportional to its advertised bandwidth,
15715 rather than uniformly at random. This should speed up Tor for
15716 bridge users. Also do this for people who set StrictEntryNodes.
15718 o Bootstrapping faster and building circuits more intelligently:
15719 - Fix bug 660 that was preventing us from knowing that we should
15720 preemptively build circuits to handle expected directory requests.
15721 - When we're checking if we have enough dir info for each relay
15722 to begin establishing circuits, make sure that we actually have
15723 the descriptor listed in the consensus, not just any descriptor.
15724 - Correctly notify one-hop connections when a circuit build has
15725 failed. Possible fix for bug 669. Found by lodger.
15726 - Clients now hold circuitless TLS connections open for 1.5 times
15727 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
15728 rebuild a new circuit over them within that timeframe. Previously,
15729 they held them open only for KeepalivePeriod (5 minutes).
15731 o Performance improvements (memory):
15732 - Add OpenBSD malloc code from "phk" as an optional malloc
15733 replacement on Linux: some glibc libraries do very poorly with
15734 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
15735 ./configure to get the replacement malloc code.
15736 - Switch our old ring buffer implementation for one more like that
15737 used by free Unix kernels. The wasted space in a buffer with 1mb
15738 of data will now be more like 8k than 1mb. The new implementation
15739 also avoids realloc();realloc(); patterns that can contribute to
15740 memory fragmentation.
15741 - Change the way that Tor buffers data that it is waiting to write.
15742 Instead of queueing data cells in an enormous ring buffer for each
15743 client->OR or OR->OR connection, we now queue cells on a separate
15744 queue for each circuit. This lets us use less slack memory, and
15745 will eventually let us be smarter about prioritizing different kinds
15747 - Reference-count and share copies of address policy entries; only 5%
15748 of them were actually distinct.
15749 - Tune parameters for cell pool allocation to minimize amount of
15751 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
15752 for every single inactive connection_t. Free items from the
15753 4k/16k-buffer free lists when they haven't been used for a while.
15754 - Make memory debugging information describe more about history
15755 of cell allocation, so we can help reduce our memory use.
15756 - Be even more aggressive about releasing RAM from small
15757 empty buffers. Thanks to our free-list code, this shouldn't be too
15758 performance-intensive.
15759 - Log malloc statistics from mallinfo() on platforms where it exists.
15760 - Use memory pools to allocate cells with better speed and memory
15761 efficiency, especially on platforms where malloc() is inefficient.
15762 - Add a --with-tcmalloc option to the configure script to link
15763 against tcmalloc (if present). Does not yet search for non-system
15766 o Performance improvements (socket management):
15767 - Count the number of open sockets separately from the number of
15768 active connection_t objects. This will let us avoid underusing
15769 our allocated connection limit.
15770 - We no longer use socket pairs to link an edge connection to an
15771 anonymous directory connection or a DirPort test connection.
15772 Instead, we track the link internally and transfer the data
15773 in-process. This saves two sockets per "linked" connection (at the
15774 client and at the server), and avoids the nasty Windows socketpair()
15776 - We were leaking a file descriptor if Tor started with a zero-length
15777 cached-descriptors file. Patch by "freddy77".
15779 o Performance improvements (CPU use):
15780 - Never walk through the list of logs if we know that no log target
15781 is interested in a given message.
15782 - Call routerlist_remove_old_routers() much less often. This should
15783 speed startup, especially on directory caches.
15784 - Base64 decoding was actually showing up on our profile when parsing
15785 the initial descriptor file; switch to an in-process all-at-once
15786 implementation that's about 3.5x times faster than calling out to
15788 - Use a slightly simpler string hashing algorithm (copying Python's
15789 instead of Java's) and optimize our digest hashing algorithm to take
15790 advantage of 64-bit platforms and to remove some possibly-costly
15792 - When implementing AES counter mode, update only the portions of the
15793 counter buffer that need to change, and don't keep separate
15794 network-order and host-order counters on big-endian hosts (where
15795 they are the same).
15796 - Add an in-place version of aes_crypt() so that we can avoid doing a
15797 needless memcpy() call on each cell payload.
15798 - Use Critical Sections rather than Mutexes for synchronizing threads
15799 on win32; Mutexes are heavier-weight, and designed for synchronizing
15802 o Performance improvements (bandwidth use):
15803 - Don't try to launch new descriptor downloads quite so often when we
15804 already have enough directory information to build circuits.
15805 - Version 1 directories are no longer generated in full. Instead,
15806 authorities generate and serve "stub" v1 directories that list
15807 no servers. This will stop Tor versions 0.1.0.x and earlier from
15808 working, but (for security reasons) nobody should be running those
15810 - Avoid going directly to the directory authorities even if you're a
15811 relay, if you haven't found yourself reachable yet or if you've
15812 decided not to advertise your dirport yet. Addresses bug 556.
15813 - If we've gone 12 hours since our last bandwidth check, and we
15814 estimate we have less than 50KB bandwidth capacity but we could
15815 handle more, do another bandwidth test.
15816 - Support "If-Modified-Since" when answering HTTP requests for
15817 directories, running-routers documents, and v2 and v3 networkstatus
15818 documents. (There's no need to support it for router descriptors,
15819 since those are downloaded by descriptor digest.)
15820 - Stop fetching directory info so aggressively if your DirPort is
15821 on but your ORPort is off; stop fetching v2 dir info entirely.
15822 You can override these choices with the new FetchDirInfoEarly
15825 o Changed config option behavior (features):
15826 - Configuration files now accept C-style strings as values. This
15827 helps encode characters not allowed in the current configuration
15828 file format, such as newline or #. Addresses bug 557.
15829 - Add hidden services and DNSPorts to the list of things that make
15830 Tor accept that it has running ports. Change starting Tor with no
15831 ports from a fatal error to a warning; we might change it back if
15832 this turns out to confuse anybody. Fixes bug 579.
15833 - Make PublishServerDescriptor default to 1, so the default doesn't
15834 have to change as we invent new directory protocol versions.
15835 - Allow people to say PreferTunnelledDirConns rather than
15836 PreferTunneledDirConns, for those alternate-spellers out there.
15837 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
15838 accommodate the growing number of servers that use the default
15839 and are reaching it.
15840 - Make it possible to enable HashedControlPassword and
15841 CookieAuthentication at the same time.
15842 - When a TrackHostExits-chosen exit fails too many times in a row,
15843 stop using it. Fixes bug 437.
15845 o Changed config option behavior (bugfixes):
15846 - Do not read the configuration file when we've only been told to
15847 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
15848 based on patch from Sebastian Hahn.
15849 - Actually validate the options passed to AuthDirReject,
15850 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
15851 - Make "ClientOnly 1" config option disable directory ports too.
15852 - Don't stop fetching descriptors when FetchUselessDescriptors is
15853 set, even if we stop asking for circuits. Bug reported by tup
15855 - Servers used to decline to publish their DirPort if their
15856 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
15857 they look only at BandwidthRate and RelayBandwidthRate.
15858 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
15859 minus 1 byte: the actual maximum declared bandwidth.
15860 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
15861 - Make the NodeFamilies config option work. (Reported by
15862 lodger -- it has never actually worked, even though we added it
15864 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
15865 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
15867 o New config options:
15868 - New configuration options AuthDirMaxServersPerAddr and
15869 AuthDirMaxServersperAuthAddr to override default maximum number
15870 of servers allowed on a single IP address. This is important for
15871 running a test network on a single host.
15872 - Three new config options (AlternateDirAuthority,
15873 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
15874 user selectively replace the default directory authorities by type,
15875 rather than the all-or-nothing replacement that DirServer offers.
15876 - New config options AuthDirBadDir and AuthDirListBadDirs for
15877 authorities to mark certain relays as "bad directories" in the
15878 networkstatus documents. Also supports the "!baddir" directive in
15879 the approved-routers file.
15880 - New config option V2AuthoritativeDirectory that all v2 directory
15881 authorities must set. This lets v3 authorities choose not to serve
15882 v2 directory information.
15884 o Minor features (other):
15885 - When we're not serving v2 directory information, there is no reason
15886 to actually keep any around. Remove the obsolete files and directory
15887 on startup if they are very old and we aren't going to serve them.
15888 - When we negotiate a v2 link-layer connection (not yet implemented),
15889 accept RELAY_EARLY cells and turn them into RELAY cells if we've
15890 negotiated a v1 connection for their next step. Initial steps for
15892 - When we have no consensus, check FallbackNetworkstatusFile (defaults
15893 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
15894 we can start out knowing some directory caches. We don't ship with
15895 a fallback consensus by default though, because it was making
15896 bootstrapping take too long while we tried many down relays.
15897 - Authorities send back an X-Descriptor-Not-New header in response to
15898 an accepted-but-discarded descriptor upload. Partially implements
15900 - If we find a cached-routers file that's been sitting around for more
15901 than 28 days unmodified, then most likely it's a leftover from
15902 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
15904 - When we (as a cache) download a descriptor because it was listed
15905 in a consensus, remember when the consensus was supposed to expire,
15906 and don't expire the descriptor until then.
15907 - Optionally (if built with -DEXPORTMALLINFO) export the output
15908 of mallinfo via http, as tor/mallinfo.txt. Only accessible
15910 - Tag every guard node in our state file with the version that
15911 we believe added it, or with our own version if we add it. This way,
15912 if a user temporarily runs an old version of Tor and then switches
15913 back to a new one, she doesn't automatically lose her guards.
15914 - When somebody requests a list of statuses or servers, and we have
15915 none of those, return a 404 rather than an empty 200.
15916 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
15918 - Add an HSAuthorityRecordStats option that hidden service authorities
15919 can use to track statistics of overall hidden service usage without
15920 logging information that would be as useful to an attacker.
15921 - Allow multiple HiddenServicePort directives with the same virtual
15922 port; when they occur, the user is sent round-robin to one
15923 of the target ports chosen at random. Partially fixes bug 393 by
15924 adding limited ad-hoc round-robining.
15925 - Revamp file-writing logic so we don't need to have the entire
15926 contents of a file in memory at once before we write to disk. Tor,
15929 o Minor bugfixes (other):
15930 - Alter the code that tries to recover from unhandled write
15931 errors, to not try to flush onto a socket that's given us
15933 - Directory mirrors no longer include a guess at the client's IP
15934 address if the connection appears to be coming from the same /24
15935 network; it was producing too many wrong guesses.
15936 - If we're trying to flush the last bytes on a connection (for
15937 example, when answering a directory request), reset the
15938 time-to-give-up timeout every time we manage to write something
15940 - Reject router descriptors with out-of-range bandwidthcapacity or
15941 bandwidthburst values.
15942 - If we can't expand our list of entry guards (e.g. because we're
15943 using bridges or we have StrictEntryNodes set), don't mark relays
15944 down when they fail a directory request. Otherwise we're too quick
15945 to mark all our entry points down.
15946 - Authorities no longer send back "400 you're unreachable please fix
15947 it" errors to Tor servers that aren't online all the time. We're
15948 supposed to tolerate these servers now.
15949 - Let directory authorities startup even when they can't generate
15950 a descriptor immediately, e.g. because they don't know their
15952 - Correctly enforce that elements of directory objects do not appear
15953 more often than they are allowed to appear.
15954 - Stop allowing hibernating servers to be "stable" or "fast".
15955 - On Windows, we were preventing other processes from reading
15956 cached-routers while Tor was running. (Reported by janbar)
15957 - Check return values from pthread_mutex functions.
15958 - When opening /dev/null in finish_daemonize(), do not pass the
15959 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
15960 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
15962 o Controller features:
15963 - The GETCONF command now escapes and quotes configuration values
15964 that don't otherwise fit into the torrc file.
15965 - The SETCONF command now handles quoted values correctly.
15966 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
15967 ask about source, timestamp of arrival, purpose, etc. We need
15968 something like this to help Vidalia not do GeoIP lookups on bridge
15970 - Allow multiple HashedControlPassword config lines, to support
15971 multiple controller passwords.
15972 - Accept LF instead of CRLF on controller, since some software has a
15973 hard time generating real Internet newlines.
15974 - Add GETINFO values for the server status events
15975 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
15977 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
15978 GETINFO for Torstat to use until it can switch to using extrainfos.
15979 - New config option CookieAuthFile to choose a new location for the
15980 cookie authentication file, and config option
15981 CookieAuthFileGroupReadable to make it group-readable.
15982 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
15983 match requests to applications. Patch from Robert Hogan.
15984 - Add a RESOLVE command to launch hostname lookups. Original patch
15986 - Add GETINFO status/enough-dir-info to let controllers tell whether
15987 Tor has downloaded sufficient directory information. Patch from Tup.
15988 - You can now use the ControlSocket option to tell Tor to listen for
15989 controller connections on Unix domain sockets on systems that
15990 support them. Patch from Peter Palfrader.
15991 - New "GETINFO address-mappings/*" command to get address mappings
15992 with expiry information. "addr-mappings/*" is now deprecated.
15994 - Add a new config option __DisablePredictedCircuits designed for
15995 use by the controller, when we don't want Tor to build any circuits
15997 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
15998 so we can exit from the middle of the circuit.
15999 - Implement "getinfo status/circuit-established".
16000 - Implement "getinfo status/version/..." so a controller can tell
16001 whether the current version is recommended, and whether any versions
16002 are good, and how many authorities agree. Patch from "shibz".
16003 - Controllers should now specify cache=no or cache=yes when using
16004 the +POSTDESCRIPTOR command.
16005 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
16006 Robert Hogan. Fixes the first part of bug 681.
16007 - When reporting clock skew, and we know that the clock is _at least
16008 as skewed_ as some value, but we don't know the actual value,
16009 report the value as a "minimum skew."
16011 o Controller bugfixes:
16012 - Generate "STATUS_SERVER" events rather than misspelled
16013 "STATUS_SEVER" events. Caught by mwenge.
16014 - Reject controller commands over 1MB in length, so rogue
16015 processes can't run us out of memory.
16016 - Change the behavior of "getinfo status/good-server-descriptor"
16017 so it doesn't return failure when any authority disappears.
16018 - Send NAMESERVER_STATUS messages for a single failed nameserver
16020 - When the DANGEROUS_VERSION controller status event told us we're
16021 running an obsolete version, it used the string "OLD" to describe
16022 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
16023 "OBSOLETE" in both cases.
16024 - Respond to INT and TERM SIGNAL commands before we execute the
16025 signal, in case the signal shuts us down. We had a patch in
16026 0.1.2.1-alpha that tried to do this by queueing the response on
16027 the connection's buffer before shutting down, but that really
16028 isn't the same thing at all. Bug located by Matt Edman.
16029 - Provide DNS expiry times in GMT, not in local time. For backward
16030 compatibility, ADDRMAP events only provide GMT expiry in an extended
16031 field. "GETINFO address-mappings" always does the right thing.
16032 - Use CRLF line endings properly in NS events.
16033 - Make 'getinfo fingerprint' return a 551 error if we're not a
16034 server, so we match what the control spec claims we do. Reported
16036 - Fix a typo in an error message when extendcircuit fails that
16037 caused us to not follow the \r\n-based delimiter protocol. Reported
16039 - When tunneling an encrypted directory connection, and its first
16040 circuit fails, do not leave it unattached and ask the controller
16041 to deal. Fixes the second part of bug 681.
16042 - Treat some 403 responses from directory servers as INFO rather than
16043 WARN-severity events.
16045 o Portability / building / compiling:
16046 - When building with --enable-gcc-warnings, check for whether Apple's
16047 warning "-Wshorten-64-to-32" is available.
16048 - Support compilation to target iPhone; patch from cjacker huang.
16049 To build for iPhone, pass the --enable-iphone option to configure.
16050 - Port Tor to build and run correctly on Windows CE systems, using
16051 the wcecompat library. Contributed by Valerio Lupi.
16052 - Detect non-ASCII platforms (if any still exist) and refuse to
16053 build there: some of our code assumes that 'A' is 65 and so on.
16054 - Clear up some MIPSPro compiler warnings.
16055 - Make autoconf search for libevent, openssl, and zlib consistently.
16056 - Update deprecated macros in configure.in.
16057 - When warning about missing headers, tell the user to let us
16058 know if the compile succeeds anyway, so we can downgrade the
16060 - Include the current subversion revision as part of the version
16061 string: either fetch it directly if we're in an SVN checkout, do
16062 some magic to guess it if we're in an SVK checkout, or use
16063 the last-detected version if we're building from a .tar.gz.
16064 Use this version consistently in log messages.
16065 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
16066 - Read resolv.conf files correctly on platforms where read() returns
16067 partial results on small file reads.
16068 - Build without verbose warnings even on gcc 4.2 and 4.3.
16069 - On Windows, correctly detect errors when listing the contents of
16070 a directory. Fix from lodger.
16071 - Run 'make test' as part of 'make dist', so we stop releasing so
16072 many development snapshots that fail their unit tests.
16073 - Add support to detect Libevent versions in the 1.4.x series
16075 - Add command-line arguments to unit-test executable so that we can
16076 invoke any chosen test from the command line rather than having
16077 to run the whole test suite at once; and so that we can turn on
16078 logging for the unit tests.
16079 - Do not automatically run configure from autogen.sh. This
16080 non-standard behavior tended to annoy people who have built other
16082 - Fix a macro/CPP interaction that was confusing some compilers:
16083 some GCCs don't like #if/#endif pairs inside macro arguments.
16085 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
16086 Fixes bug 704; fix from Steven Murdoch.
16087 - Correctly detect transparent proxy support on Linux hosts that
16088 require in.h to be included before netfilter_ipv4.h. Patch
16091 o Logging improvements:
16092 - When we haven't had any application requests lately, don't bother
16093 logging that we have expired a bunch of descriptors.
16094 - When attempting to open a logfile fails, tell us why.
16095 - Only log guard node status when guard node status has changed.
16096 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
16097 make "INFO" 75% less verbose.
16098 - When SafeLogging is disabled, log addresses along with all TLS
16100 - Report TLS "zero return" case as a "clean close" and "IO error"
16101 as a "close". Stop calling closes "unexpected closes": existing
16102 Tors don't use SSL_close(), so having a connection close without
16103 the TLS shutdown handshake is hardly unexpected.
16104 - When we receive a consensus from the future, warn about skew.
16105 - Make "not enough dir info yet" warnings describe *why* Tor feels
16106 it doesn't have enough directory info yet.
16107 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
16108 consumers. (We already do this on HUP.)
16109 - Give more descriptive well-formedness errors for out-of-range
16110 hidden service descriptor/protocol versions.
16111 - Stop recommending that every server operator send mail to tor-ops.
16112 Resolves bug 597. Bugfix on 0.1.2.x.
16113 - Improve skew reporting: try to give the user a better log message
16114 about how skewed they are, and how much this matters.
16115 - New --quiet command-line option to suppress the default console log.
16116 Good in combination with --hash-password.
16117 - Don't complain that "your server has not managed to confirm that its
16118 ports are reachable" if we haven't been able to build any circuits
16120 - Detect the reason for failing to mmap a descriptor file we just
16121 wrote, and give a more useful log message. Fixes bug 533.
16122 - Always prepend "Bug: " to any log message about a bug.
16123 - When dumping memory usage, list bytes used in buffer memory
16125 - When running with dmalloc, dump more stats on hup and on exit.
16126 - Put a platform string (e.g. "Linux i686") in the startup log
16127 message, so when people paste just their logs, we know if it's
16128 OpenBSD or Windows or what.
16129 - When logging memory usage, break down memory used in buffers by
16131 - When we are reporting the DirServer line we just parsed, we were
16132 logging the second stanza of the key fingerprint, not the first.
16133 - Even though Windows is equally happy with / and \ as path separators,
16134 try to use \ consistently on Windows and / consistently on Unix: it
16135 makes the log messages nicer.
16136 - On OSX, stop warning the user that kqueue support in libevent is
16137 "experimental", since it seems to have worked fine for ages.
16139 o Contributed scripts and tools:
16140 - Update linux-tor-prio.sh script to allow QoS based on the uid of
16141 the Tor process. Patch from Marco Bonetti with tweaks from Mike
16143 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
16144 Unix users an easy way to script their Tor process (e.g. by
16145 adjusting bandwidth based on the time of the day).
16146 - In the exitlist script, only consider the most recently published
16147 server descriptor for each server. Also, when the user requests
16148 a list of servers that _reject_ connections to a given address,
16149 explicitly exclude the IPs that also have servers that accept
16150 connections to that address. Resolves bug 405.
16151 - Include a new contrib/tor-exit-notice.html file that exit relay
16152 operators can put on their website to help reduce abuse queries.
16154 o Newly deprecated features:
16155 - The status/version/num-versioning and status/version/num-concurring
16156 GETINFO controller options are no longer useful in the v3 directory
16157 protocol: treat them as deprecated, and warn when they're used.
16158 - The RedirectExits config option is now deprecated.
16160 o Removed features:
16161 - Drop the old code to choke directory connections when the
16162 corresponding OR connections got full: thanks to the cell queue
16163 feature, OR conns don't get full any more.
16164 - Remove the old "dns worker" server DNS code: it hasn't been default
16165 since 0.1.2.2-alpha, and all the servers are using the new
16167 - Remove the code to generate the oldest (v1) directory format.
16168 - Remove support for the old bw_accounting file: we've been storing
16169 bandwidth accounting information in the state file since
16170 0.1.2.5-alpha. This may result in bandwidth accounting errors
16171 if you try to upgrade from 0.1.1.x or earlier, or if you try to
16172 downgrade to 0.1.1.x or earlier.
16173 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
16174 it, it had no AES, and it hasn't seen any security patches since
16176 - Stop overloading the circuit_t.onionskin field for both "onionskin
16177 from a CREATE cell that we are waiting for a cpuworker to be
16178 assigned" and "onionskin from an EXTEND cell that we are going to
16179 send to an OR as soon as we are connected". Might help with bug 600.
16180 - Remove the tor_strpartition() function: its logic was confused,
16181 and it was only used for one thing that could be implemented far
16183 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
16184 and TorControl.py, as they use the old v0 controller protocol,
16185 and are obsoleted by TorFlow anyway.
16186 - Drop support for v1 rendezvous descriptors, since we never used
16187 them anyway, and the code has probably rotted by now. Based on
16188 patch from Karsten Loesing.
16189 - Stop allowing address masks that do not correspond to bit prefixes.
16190 We have warned about these for a really long time; now it's time
16191 to reject them. (Patch from croup.)
16192 - Remove an optimization in the AES counter-mode code that assumed
16193 that the counter never exceeded 2^68. When the counter can be set
16194 arbitrarily as an IV (as it is by Karsten's new hidden services
16195 code), this assumption no longer holds.
16196 - Disable the SETROUTERPURPOSE controller command: it is now
16200 Changes in version 0.1.2.19 - 2008-01-17
16201 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
16202 exit policy a little bit more conservative so it's safer to run an
16203 exit relay on a home system, and fixes a variety of smaller issues.
16206 - Exit policies now reject connections that are addressed to a
16207 relay's public (external) IP address too, unless
16208 ExitPolicyRejectPrivate is turned off. We do this because too
16209 many relays are running nearby to services that trust them based
16210 on network address.
16213 - When the clock jumps forward a lot, do not allow the bandwidth
16214 buckets to become negative. Fixes bug 544.
16215 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
16216 on every successful resolve. Reported by Mike Perry.
16217 - Purge old entries from the "rephist" database and the hidden
16218 service descriptor database even when DirPort is zero.
16219 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
16220 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
16221 crashing or mis-answering these requests.
16222 - When we decide to send a 503 response to a request for servers, do
16223 not then also send the server descriptors: this defeats the whole
16224 purpose. Fixes bug 539.
16227 - Changing the ExitPolicyRejectPrivate setting should cause us to
16228 rebuild our server descriptor.
16229 - Fix handling of hex nicknames when answering controller requests for
16230 networkstatus by name, or when deciding whether to warn about
16231 unknown routers in a config option. (Patch from mwenge.)
16232 - Fix a couple of hard-to-trigger autoconf problems that could result
16233 in really weird results on platforms whose sys/types.h files define
16234 nonstandard integer types.
16235 - Don't try to create the datadir when running --verify-config or
16236 --hash-password. Resolves bug 540.
16237 - If we were having problems getting a particular descriptor from the
16238 directory caches, and then we learned about a new descriptor for
16239 that router, we weren't resetting our failure count. Reported
16241 - Although we fixed bug 539 (where servers would send HTTP status 503
16242 responses _and_ send a body too), there are still servers out there
16243 that haven't upgraded. Therefore, make clients parse such bodies
16244 when they receive them.
16245 - Run correctly on systems where rlim_t is larger than unsigned long.
16246 This includes some 64-bit systems.
16247 - Run correctly on platforms (like some versions of OS X 10.5) where
16248 the real limit for number of open files is OPEN_FILES, not rlim_max
16249 from getrlimit(RLIMIT_NOFILES).
16250 - Avoid a spurious free on base64 failure.
16251 - Avoid segfaults on certain complex invocations of
16252 router_get_by_hexdigest().
16253 - Fix rare bug on REDIRECTSTREAM control command when called with no
16254 port set: it could erroneously report an error when none had
16258 Changes in version 0.1.2.18 - 2007-10-28
16259 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
16260 hidden service introduction that were causing huge delays, and a big
16261 bug that was causing some servers to disappear from the network status
16262 lists for a few hours each day.
16264 o Major bugfixes (crashes):
16265 - If a connection is shut down abruptly because of something that
16266 happened inside connection_flushed_some(), do not call
16267 connection_finished_flushing(). Should fix bug 451:
16268 "connection_stop_writing: Assertion conn->write_event failed"
16269 Bugfix on 0.1.2.7-alpha.
16270 - Fix possible segfaults in functions called from
16271 rend_process_relay_cell().
16273 o Major bugfixes (hidden services):
16274 - Hidden services were choosing introduction points uniquely by
16275 hexdigest, but when constructing the hidden service descriptor
16276 they merely wrote the (potentially ambiguous) nickname.
16277 - Clients now use the v2 intro format for hidden service
16278 connections: they specify their chosen rendezvous point by identity
16279 digest rather than by (potentially ambiguous) nickname. These
16280 changes could speed up hidden service connections dramatically.
16282 o Major bugfixes (other):
16283 - Stop publishing a new server descriptor just because we get a
16284 HUP signal. This led (in a roundabout way) to some servers getting
16285 dropped from the networkstatus lists for a few hours each day.
16286 - When looking for a circuit to cannibalize, consider family as well
16287 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
16288 circuit cannibalization).
16289 - When a router wasn't listed in a new networkstatus, we were leaving
16290 the flags for that router alone -- meaning it remained Named,
16291 Running, etc -- even though absence from the networkstatus means
16292 that it shouldn't be considered to exist at all anymore. Now we
16293 clear all the flags for routers that fall out of the networkstatus
16294 consensus. Fixes bug 529.
16297 - Don't try to access (or alter) the state file when running
16298 --list-fingerprint or --verify-config or --hash-password. Resolves
16300 - When generating information telling us how to extend to a given
16301 router, do not try to include the nickname if it is
16302 absent. Resolves bug 467.
16303 - Fix a user-triggerable segfault in expand_filename(). (There isn't
16304 a way to trigger this remotely.)
16305 - When sending a status event to the controller telling it that an
16306 OR address is reachable, set the port correctly. (Previously we
16307 were reporting the dir port.)
16308 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
16309 command. Bugfix on 0.1.2.17.
16310 - When loading bandwidth history, do not believe any information in
16311 the future. Fixes bug 434.
16312 - When loading entry guard information, do not believe any information
16314 - When we have our clock set far in the future and generate an
16315 onion key, then re-set our clock to be correct, we should not stop
16316 the onion key from getting rotated.
16317 - On some platforms, accept() can return a broken address. Detect
16318 this more quietly, and deal accordingly. Fixes bug 483.
16319 - It's not actually an error to find a non-pending entry in the DNS
16320 cache when canceling a pending resolve. Don't log unless stuff
16321 is fishy. Resolves bug 463.
16322 - Don't reset trusted dir server list when we set a configuration
16323 option. Patch from Robert Hogan.
16326 Changes in version 0.1.2.17 - 2007-08-30
16327 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
16328 X bundles. Vidalia 0.0.14 makes authentication required for the
16329 ControlPort in the default configuration, which addresses important
16330 security risks. Everybody who uses Vidalia (or another controller)
16333 In addition, this Tor update fixes major load balancing problems with
16334 path selection, which should speed things up a lot once many people
16337 o Major bugfixes (security):
16338 - We removed support for the old (v0) control protocol. It has been
16339 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
16340 become more of a headache than it's worth.
16342 o Major bugfixes (load balancing):
16343 - When choosing nodes for non-guard positions, weight guards
16344 proportionally less, since they already have enough load. Patch
16346 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
16347 will allow fast Tor servers to get more attention.
16348 - When we're upgrading from an old Tor version, forget our current
16349 guards and pick new ones according to the new weightings. These
16350 three load balancing patches could raise effective network capacity
16351 by a factor of four. Thanks to Mike Perry for measurements.
16353 o Major bugfixes (stream expiration):
16354 - Expire not-yet-successful application streams in all cases if
16355 they've been around longer than SocksTimeout. Right now there are
16356 some cases where the stream will live forever, demanding a new
16357 circuit every 15 seconds. Fixes bug 454; reported by lodger.
16359 o Minor features (controller):
16360 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
16361 is valid before any authentication has been received. It tells
16362 a controller what kind of authentication is expected, and what
16363 protocol is spoken. Implements proposal 119.
16365 o Minor bugfixes (performance):
16366 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
16367 greatly speeding up loading cached-routers from disk on startup.
16368 - Disable sentinel-based debugging for buffer code: we squashed all
16369 the bugs that this was supposed to detect a long time ago, and now
16370 its only effect is to change our buffer sizes from nice powers of
16371 two (which platform mallocs tend to like) to values slightly over
16372 powers of two (which make some platform mallocs sad).
16374 o Minor bugfixes (misc):
16375 - If exit bandwidth ever exceeds one third of total bandwidth, then
16376 use the correct formula to weight exit nodes when choosing paths.
16377 Based on patch from Mike Perry.
16378 - Choose perfectly fairly among routers when choosing by bandwidth and
16379 weighting by fraction of bandwidth provided by exits. Previously, we
16380 would choose with only approximate fairness, and correct ourselves
16381 if we ran off the end of the list.
16382 - If we require CookieAuthentication but we fail to write the
16383 cookie file, we would warn but not exit, and end up in a state
16384 where no controller could authenticate. Now we exit.
16385 - If we require CookieAuthentication, stop generating a new cookie
16386 every time we change any piece of our config.
16387 - Refuse to start with certain directory authority keys, and
16388 encourage people using them to stop.
16389 - Terminate multi-line control events properly. Original patch
16391 - Fix a minor memory leak when we fail to find enough suitable
16392 servers to choose a circuit.
16393 - Stop leaking part of the descriptor when we run into a particularly
16394 unparseable piece of it.
16397 Changes in version 0.1.2.16 - 2007-08-01
16398 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
16399 remote attacker in certain situations to rewrite the user's torrc
16400 configuration file. This can completely compromise anonymity of users
16401 in most configurations, including those running the Vidalia bundles,
16402 TorK, etc. Or worse.
16404 o Major security fixes:
16405 - Close immediately after missing authentication on control port;
16406 do not allow multiple authentication attempts.
16409 Changes in version 0.1.2.15 - 2007-07-17
16410 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
16411 problems, fixes compilation on BSD, and fixes a variety of other
16412 bugs. Everybody should upgrade.
16414 o Major bugfixes (compilation):
16415 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
16417 o Major bugfixes (crashes):
16418 - Try even harder not to dereference the first character after
16419 an mmap(). Reported by lodger.
16420 - Fix a crash bug in directory authorities when we re-number the
16421 routerlist while inserting a new router.
16422 - When the cached-routers file is an even multiple of the page size,
16423 don't run off the end and crash. (Fixes bug 455; based on idea
16425 - Fix eventdns.c behavior on Solaris: It is critical to include
16426 orconfig.h _before_ sys/types.h, so that we can get the expected
16427 definition of _FILE_OFFSET_BITS.
16429 o Major bugfixes (security):
16430 - Fix a possible buffer overrun when using BSD natd support. Bug
16432 - When sending destroy cells from a circuit's origin, don't include
16433 the reason for tearing down the circuit. The spec says we didn't,
16434 and now we actually don't. Reported by lodger.
16435 - Keep streamids from different exits on a circuit separate. This
16436 bug may have allowed other routers on a given circuit to inject
16437 cells into streams. Reported by lodger; fixes bug 446.
16438 - If there's a never-before-connected-to guard node in our list,
16439 never choose any guards past it. This way we don't expand our
16440 guard list unless we need to.
16442 o Minor bugfixes (guard nodes):
16443 - Weight guard selection by bandwidth, so that low-bandwidth nodes
16444 don't get overused as guards.
16446 o Minor bugfixes (directory):
16447 - Correctly count the number of authorities that recommend each
16448 version. Previously, we were under-counting by 1.
16449 - Fix a potential crash bug when we load many server descriptors at
16450 once and some of them make others of them obsolete. Fixes bug 458.
16452 o Minor bugfixes (hidden services):
16453 - Stop tearing down the whole circuit when the user asks for a
16454 connection to a port that the hidden service didn't configure.
16457 o Minor bugfixes (misc):
16458 - On Windows, we were preventing other processes from reading
16459 cached-routers while Tor was running. Reported by janbar.
16460 - Fix a possible (but very unlikely) bug in picking routers by
16461 bandwidth. Add a log message to confirm that it is in fact
16462 unlikely. Patch from lodger.
16463 - Backport a couple of memory leak fixes.
16464 - Backport miscellaneous cosmetic bugfixes.
16467 Changes in version 0.1.2.14 - 2007-05-25
16468 Tor 0.1.2.14 changes the addresses of two directory authorities (this
16469 change especially affects those who serve or use hidden services),
16470 and fixes several other crash- and security-related bugs.
16472 o Directory authority changes:
16473 - Two directory authorities (moria1 and moria2) just moved to new
16474 IP addresses. This change will particularly affect those who serve
16475 or use hidden services.
16477 o Major bugfixes (crashes):
16478 - If a directory server runs out of space in the connection table
16479 as it's processing a begin_dir request, it will free the exit stream
16480 but leave it attached to the circuit, leading to unpredictable
16481 behavior. (Reported by seeess, fixes bug 425.)
16482 - Fix a bug in dirserv_remove_invalid() that would cause authorities
16483 to corrupt memory under some really unlikely scenarios.
16484 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
16485 - Avoid segfaults when reading from mmaped descriptor file. (Reported
16488 o Major bugfixes (security):
16489 - When choosing an entry guard for a circuit, avoid using guards
16490 that are in the same family as the chosen exit -- not just guards
16491 that are exactly the chosen exit. (Reported by lodger.)
16493 o Major bugfixes (resource management):
16494 - If a directory authority is down, skip it when deciding where to get
16495 networkstatus objects or descriptors. Otherwise we keep asking
16496 every 10 seconds forever. Fixes bug 384.
16497 - Count it as a failure if we fetch a valid network-status but we
16498 don't want to keep it. Otherwise we'll keep fetching it and keep
16499 not wanting to keep it. Fixes part of bug 422.
16500 - If all of our dirservers have given us bad or no networkstatuses
16501 lately, then stop hammering them once per minute even when we
16502 think they're failed. Fixes another part of bug 422.
16505 - Actually set the purpose correctly for descriptors inserted with
16506 purpose=controller.
16507 - When we have k non-v2 authorities in our DirServer config,
16508 we ignored the last k authorities in the list when updating our
16510 - Correctly back-off from requesting router descriptors that we are
16511 having a hard time downloading.
16512 - Read resolv.conf files correctly on platforms where read() returns
16513 partial results on small file reads.
16514 - Don't rebuild the entire router store every time we get 32K of
16515 routers: rebuild it when the journal gets very large, or when
16516 the gaps in the store get very large.
16519 - When routers publish SVN revisions in their router descriptors,
16520 authorities now include those versions correctly in networkstatus
16522 - Warn when using a version of libevent before 1.3b to run a server on
16523 OSX or BSD: these versions interact badly with userspace threads.
16526 Changes in version 0.1.2.13 - 2007-04-24
16527 This release features some major anonymity fixes, such as safer path
16528 selection; better client performance; faster bootstrapping, better
16529 address detection, and better DNS support for servers; write limiting as
16530 well as read limiting to make servers easier to run; and a huge pile of
16531 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
16533 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
16534 of the Freenode IRC network, remembering his patience and vision for
16535 free speech on the Internet.
16537 o Major features, client performance:
16538 - Weight directory requests by advertised bandwidth. Now we can
16539 let servers enable write limiting but still allow most clients to
16540 succeed at their directory requests. (We still ignore weights when
16541 choosing a directory authority; I hope this is a feature.)
16542 - Stop overloading exit nodes -- avoid choosing them for entry or
16543 middle hops when the total bandwidth available from non-exit nodes
16544 is much higher than the total bandwidth available from exit nodes.
16545 - Rather than waiting a fixed amount of time between retrying
16546 application connections, we wait only 10 seconds for the first,
16547 10 seconds for the second, and 15 seconds for each retry after
16548 that. Hopefully this will improve the expected user experience.
16549 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
16550 to open a stream fails; now we do in more cases. This should
16551 make clients able to find a good exit faster in some cases, since
16552 unhandleable requests will now get an error rather than timing out.
16554 o Major features, client functionality:
16555 - Implement BEGIN_DIR cells, so we can connect to a directory
16556 server via TLS to do encrypted directory requests rather than
16557 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
16558 config options if you like. For now, this feature only works if
16559 you already have a descriptor for the destination dirserver.
16560 - Add support for transparent application connections: this basically
16561 bundles the functionality of trans-proxy-tor into the Tor
16562 mainline. Now hosts with compliant pf/netfilter implementations
16563 can redirect TCP connections straight to Tor without diverting
16564 through SOCKS. (Based on patch from tup.)
16565 - Add support for using natd; this allows FreeBSDs earlier than
16566 5.1.2 to have ipfw send connections through Tor without using
16567 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
16569 o Major features, servers:
16570 - Setting up a dyndns name for your server is now optional: servers
16571 with no hostname or IP address will learn their IP address by
16572 asking the directory authorities. This code only kicks in when you
16573 would normally have exited with a "no address" error. Nothing's
16574 authenticated, so use with care.
16575 - Directory servers now spool server descriptors, v1 directories,
16576 and v2 networkstatus objects to buffers as needed rather than en
16577 masse. They also mmap the cached-routers files. These steps save
16579 - Stop requiring clients to have well-formed certificates, and stop
16580 checking nicknames in certificates. (Clients have certificates so
16581 that they can look like Tor servers, but in the future we might want
16582 to allow them to look like regular TLS clients instead. Nicknames
16583 in certificates serve no purpose other than making our protocol
16584 easier to recognize on the wire.) Implements proposal 106.
16586 o Improvements on DNS support:
16587 - Add "eventdns" asynchronous dns library originally based on code
16588 from Adam Langley. Now we can discard the old rickety dnsworker
16589 concept, and support a wider variety of DNS functions. Allows
16590 multithreaded builds on NetBSD and OpenBSD again.
16591 - Add server-side support for "reverse" DNS lookups (using PTR
16592 records so clients can determine the canonical hostname for a given
16593 IPv4 address). Only supported by servers using eventdns; servers
16594 now announce in their descriptors if they don't support eventdns.
16595 - Workaround for name servers (like Earthlink's) that hijack failing
16596 DNS requests and replace the no-such-server answer with a "helpful"
16597 redirect to an advertising-driven search portal. Also work around
16598 DNS hijackers who "helpfully" decline to hijack known-invalid
16599 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
16600 lets you turn it off.
16601 - Servers now check for the case when common DNS requests are going to
16602 wildcarded addresses (i.e. all getting the same answer), and change
16603 their exit policy to reject *:* if it's happening.
16604 - When asked to resolve a hostname, don't use non-exit servers unless
16605 requested to do so. This allows servers with broken DNS to be
16606 useful to the network.
16607 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
16608 useless IPv6 DNS resolves.
16609 - Specify and implement client-side SOCKS5 interface for reverse DNS
16610 lookups (see doc/socks-extensions.txt). Also cache them.
16611 - When we change nameservers or IP addresses, reset and re-launch
16612 our tests for DNS hijacking.
16614 o Improvements on reachability testing:
16615 - Servers send out a burst of long-range padding cells once they've
16616 established that they're reachable. Spread them over 4 circuits,
16617 so hopefully a few will be fast. This exercises bandwidth and
16618 bootstraps them into the directory more quickly.
16619 - When we find our DirPort to be reachable, publish a new descriptor
16620 so we'll tell the world (reported by pnx).
16621 - Directory authorities now only decide that routers are reachable
16622 if their identity keys are as expected.
16623 - Do DirPort reachability tests less often, since a single test
16624 chews through many circuits before giving up.
16625 - Avoid some false positives during reachability testing: don't try
16626 to test via a server that's on the same /24 network as us.
16627 - Start publishing one minute or so after we find our ORPort
16628 to be reachable. This will help reduce the number of descriptors
16629 we have for ourselves floating around, since it's quite likely
16630 other things (e.g. DirPort) will change during that minute too.
16631 - Routers no longer try to rebuild long-term connections to directory
16632 authorities, and directory authorities no longer try to rebuild
16633 long-term connections to all servers. We still don't hang up
16634 connections in these two cases though -- we need to look at it
16635 more carefully to avoid flapping, and we likely need to wait til
16636 0.1.1.x is obsolete.
16638 o Improvements on rate limiting:
16639 - Enable write limiting as well as read limiting. Now we sacrifice
16640 capacity if we're pushing out lots of directory traffic, rather
16641 than overrunning the user's intended bandwidth limits.
16642 - Include TLS overhead when counting bandwidth usage; previously, we
16643 would count only the bytes sent over TLS, but not the bytes used
16645 - Servers decline directory requests much more aggressively when
16646 they're low on bandwidth. Otherwise they end up queueing more and
16647 more directory responses, which can't be good for latency.
16648 - But never refuse directory requests from local addresses.
16649 - Be willing to read or write on local connections (e.g. controller
16650 connections) even when the global rate limiting buckets are empty.
16651 - Flush local controller connection buffers periodically as we're
16652 writing to them, so we avoid queueing 4+ megabytes of data before
16654 - Revise and clean up the torrc.sample that we ship with; add
16655 a section for BandwidthRate and BandwidthBurst.
16657 o Major features, NT services:
16658 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
16659 command-line flag so that admins can override the default by saying
16660 "tor --service install --user "SomeUser"". This will not affect
16661 existing installed services. Also, warn the user that the service
16662 will look for its configuration file in the service user's
16663 %appdata% directory. (We can't do the "hardwire the user's appdata
16664 directory" trick any more, since we may not have read access to that
16666 - Support running the Tor service with a torrc not in the same
16667 directory as tor.exe and default to using the torrc located in
16668 the %appdata%\Tor\ of the user who installed the service. Patch
16670 - Add an --ignore-missing-torrc command-line option so that we can
16671 get the "use sensible defaults if the configuration file doesn't
16672 exist" behavior even when specifying a torrc location on the
16674 - When stopping an NT service, wait up to 10 sec for it to actually
16675 stop. (Patch from Matt Edman; resolves bug 295.)
16677 o Directory authority improvements:
16678 - Stop letting hibernating or obsolete servers affect uptime and
16680 - Stop listing hibernating servers in the v1 directory.
16681 - Authorities no longer recommend exits as guards if this would shift
16682 too much load to the exit nodes.
16683 - Authorities now specify server versions in networkstatus. This adds
16684 about 2% to the size of compressed networkstatus docs, and allows
16685 clients to tell which servers support BEGIN_DIR and which don't.
16686 The implementation is forward-compatible with a proposed future
16687 protocol version scheme not tied to Tor versions.
16688 - DirServer configuration lines now have an orport= option so
16689 clients can open encrypted tunnels to the authorities without
16690 having downloaded their descriptors yet. Enabled for moria1,
16691 moria2, tor26, and lefkada now in the default configuration.
16692 - Add a BadDirectory flag to network status docs so that authorities
16693 can (eventually) tell clients about caches they believe to be
16694 broken. Not used yet.
16695 - Allow authorities to list nodes as bad exits in their
16696 approved-routers file by fingerprint or by address. If most
16697 authorities set a BadExit flag for a server, clients don't think
16698 of it as a general-purpose exit. Clients only consider authorities
16699 that advertise themselves as listing bad exits.
16700 - Patch from Steve Hildrey: Generate network status correctly on
16701 non-versioning dirservers.
16702 - Have directory authorities allow larger amounts of drift in uptime
16703 without replacing the server descriptor: previously, a server that
16704 restarted every 30 minutes could have 48 "interesting" descriptors
16706 - Reserve the nickname "Unnamed" for routers that can't pick
16707 a hostname: any router can call itself Unnamed; directory
16708 authorities will never allocate Unnamed to any particular router;
16709 clients won't believe that any router is the canonical Unnamed.
16711 o Directory mirrors and clients:
16712 - Discard any v1 directory info that's over 1 month old (for
16713 directories) or over 1 week old (for running-routers lists).
16714 - Clients track responses with status 503 from dirservers. After a
16715 dirserver has given us a 503, we try not to use it until an hour has
16716 gone by, or until we have no dirservers that haven't given us a 503.
16717 - When we get a 503 from a directory, and we're not a server, we no
16718 longer count the failure against the total number of failures
16719 allowed for the object we're trying to download.
16720 - Prepare for servers to publish descriptors less often: never
16721 discard a descriptor simply for being too old until either it is
16722 recommended by no authorities, or until we get a better one for
16723 the same router. Make caches consider retaining old recommended
16724 routers for even longer.
16725 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
16726 headers for content, so that we can work better in the presence of
16727 caching HTTP proxies.
16728 - Stop fetching descriptors if you're not a dir mirror and you
16729 haven't tried to establish any circuits lately. (This currently
16730 causes some dangerous behavior, because when you start up again
16731 you'll use your ancient server descriptors.)
16733 o Major fixes, crashes:
16734 - Stop crashing when the controller asks us to resetconf more than
16735 one config option at once. (Vidalia 0.0.11 does this.)
16736 - Fix a longstanding obscure crash bug that could occur when we run
16737 out of DNS worker processes, if we're not using eventdns. (Resolves
16739 - Fix an assert that could trigger if a controller quickly set then
16740 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
16741 - Avoid crash when telling controller about stream-status and a
16742 stream is detached.
16743 - Avoid sending junk to controllers or segfaulting when a controller
16744 uses EVENT_NEW_DESC with verbose nicknames.
16745 - Stop triggering asserts if the controller tries to extend hidden
16746 service circuits (reported by mwenge).
16747 - If we start a server with ClientOnly 1, then set ClientOnly to 0
16748 and hup, stop triggering an assert based on an empty onion_key.
16749 - Mask out all signals in sub-threads; only the libevent signal
16750 handler should be processing them. This should prevent some crashes
16751 on some machines using pthreads. (Patch from coderman.)
16752 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
16754 o Major fixes, anonymity/security:
16755 - Automatically avoid picking more than one node from the same
16756 /16 network when constructing a circuit. Add an
16757 "EnforceDistinctSubnets" option to let people disable it if they
16758 want to operate private test networks on a single subnet.
16759 - When generating bandwidth history, round down to the nearest
16760 1k. When storing accounting data, round up to the nearest 1k.
16761 - When we're running as a server, remember when we last rotated onion
16762 keys, so that we will rotate keys once they're a week old even if
16763 we never stay up for a week ourselves.
16764 - If a client asked for a server by name, and there's a named server
16765 in our network-status but we don't have its descriptor yet, we
16766 could return an unnamed server instead.
16767 - Reject (most) attempts to use Tor circuits with length one. (If
16768 many people start using Tor as a one-hop proxy, exit nodes become
16769 a more attractive target for compromise.)
16770 - Just because your DirPort is open doesn't mean people should be
16771 able to remotely teach you about hidden service descriptors. Now
16772 only accept rendezvous posts if you've got HSAuthoritativeDir set.
16773 - Fix a potential race condition in the rpm installer. Found by
16775 - Do not log IPs with TLS failures for incoming TLS
16776 connections. (Fixes bug 382.)
16778 o Major fixes, other:
16779 - If our system clock jumps back in time, don't publish a negative
16780 uptime in the descriptor.
16781 - When we start during an accounting interval before it's time to wake
16782 up, remember to wake up at the correct time. (May fix bug 342.)
16783 - Previously, we would cache up to 16 old networkstatus documents
16784 indefinitely, if they came from nontrusted authorities. Now we
16785 discard them if they are more than 10 days old.
16786 - When we have a state file we cannot parse, tell the user and
16787 move it aside. Now we avoid situations where the user starts
16788 Tor in 1904, Tor writes a state file with that timestamp in it,
16789 the user fixes her clock, and Tor refuses to start.
16790 - Publish a new descriptor after we hup/reload. This is important
16791 if our config has changed such that we'll want to start advertising
16792 our DirPort now, etc.
16793 - If we are using an exit enclave and we can't connect, e.g. because
16794 its webserver is misconfigured to not listen on localhost, then
16795 back off and try connecting from somewhere else before we fail.
16797 o New config options or behaviors:
16798 - When EntryNodes are configured, rebuild the guard list to contain,
16799 in order: the EntryNodes that were guards before; the rest of the
16800 EntryNodes; the nodes that were guards before.
16801 - Do not warn when individual nodes in the configuration's EntryNodes,
16802 ExitNodes, etc are down: warn only when all possible nodes
16803 are down. (Fixes bug 348.)
16804 - Put a lower-bound on MaxAdvertisedBandwidth.
16805 - Start using the state file to store bandwidth accounting data:
16806 the bw_accounting file is now obsolete. We'll keep generating it
16807 for a while for people who are still using 0.1.2.4-alpha.
16808 - Try to batch changes to the state file so that we do as few
16809 disk writes as possible while still storing important things in
16811 - The state file and the bw_accounting file get saved less often when
16812 the AvoidDiskWrites config option is set.
16813 - Make PIDFile work on Windows.
16814 - Add internal descriptions for a bunch of configuration options:
16815 accessible via controller interface and in comments in saved
16817 - Reject *:563 (NNTPS) in the default exit policy. We already reject
16818 NNTP by default, so this seems like a sensible addition.
16819 - Clients now reject hostnames with invalid characters. This should
16820 avoid some inadvertent info leaks. Add an option
16821 AllowNonRFC953Hostnames to disable this behavior, in case somebody
16822 is running a private network with hosts called @, !, and #.
16823 - Check for addresses with invalid characters at the exit as well,
16824 and warn less verbosely when they fail. You can override this by
16825 setting ServerDNSAllowNonRFC953Addresses to 1.
16826 - Remove some options that have been deprecated since at least
16827 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
16828 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
16829 to set log options. Mark PathlenCoinWeight as obsolete.
16830 - Stop accepting certain malformed ports in configured exit policies.
16831 - When the user uses bad syntax in the Log config line, stop
16832 suggesting other bad syntax as a replacement.
16833 - Add new config option "ResolvConf" to let the server operator
16834 choose an alternate resolve.conf file when using eventdns.
16835 - If one of our entry guards is on the ExcludeNodes list, or the
16836 directory authorities don't think it's a good guard, treat it as
16837 if it were unlisted: stop using it as a guard, and throw it off
16838 the guards list if it stays that way for a long time.
16839 - Allow directory authorities to be marked separately as authorities
16840 for the v1 directory protocol, the v2 directory protocol, and
16841 as hidden service directories, to make it easier to retire old
16842 authorities. V1 authorities should set "HSAuthoritativeDir 1"
16843 to continue being hidden service authorities too.
16844 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
16845 - Make TrackExitHosts case-insensitive, and fix the behavior of
16846 ".suffix" TrackExitHosts items to avoid matching in the middle of
16848 - New DirPort behavior: if you have your dirport set, you download
16849 descriptors aggressively like a directory mirror, whether or not
16850 your ORPort is set.
16853 - Create a new file ReleaseNotes which was the old ChangeLog. The
16854 new ChangeLog file now includes the notes for all development
16856 - Add a new address-spec.txt document to describe our special-case
16857 addresses: .exit, .onion, and .noconnnect.
16858 - Fork the v1 directory protocol into its own spec document,
16859 and mark dir-spec.txt as the currently correct (v2) spec.
16861 o Packaging, porting, and contrib
16862 - "tor --verify-config" now exits with -1(255) or 0 depending on
16863 whether the config options are bad or good.
16864 - The Debian package now uses --verify-config when (re)starting,
16865 to distinguish configuration errors from other errors.
16866 - Adapt a patch from goodell to let the contrib/exitlist script
16867 take arguments rather than require direct editing.
16868 - Prevent the contrib/exitlist script from printing the same
16869 result more than once.
16870 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
16871 - In the hidden service example in torrc.sample, stop recommending
16872 esoteric and discouraged hidden service options.
16873 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
16874 values before failing, and always enables eventdns.
16875 - Try to detect Windows correctly when cross-compiling.
16876 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
16877 Try to fix this in configure.in by checking for most functions
16878 before we check for libevent.
16879 - Update RPMs to require libevent 1.2.
16880 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
16881 or later. Log when we are doing this, so we can diagnose it when
16882 it fails. (Also, recommend libevent 1.1b for kqueue and
16883 win32 methods; deprecate libevent 1.0b harder; make libevent
16884 recommendation system saner.)
16885 - Build with recent (1.3+) libevents on platforms that do not
16886 define the nonstandard types "u_int8_t" and friends.
16887 - Remove architecture from OS X builds. The official builds are
16888 now universal binaries.
16889 - Run correctly on OS X platforms with case-sensitive filesystems.
16890 - Correctly set maximum connection limit on Cygwin. (This time
16892 - Start compiling on MinGW on Windows (patches from Mike Chiussi
16894 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
16895 - Finally fix the openssl warnings from newer gccs that believe that
16896 ignoring a return value is okay, but casting a return value and
16897 then ignoring it is a sign of madness.
16898 - On architectures where sizeof(int)>4, still clamp declarable
16899 bandwidth to INT32_MAX.
16901 o Minor features, controller:
16902 - Warn the user when an application uses the obsolete binary v0
16903 control protocol. We're planning to remove support for it during
16904 the next development series, so it's good to give people some
16906 - Add STREAM_BW events to report per-entry-stream bandwidth
16907 use. (Patch from Robert Hogan.)
16908 - Rate-limit SIGNEWNYM signals in response to controllers that
16909 impolitely generate them for every single stream. (Patch from
16910 mwenge; closes bug 394.)
16911 - Add a REMAP status to stream events to note that a stream's
16912 address has changed because of a cached address or a MapAddress
16914 - Make REMAP stream events have a SOURCE (cache or exit), and
16915 make them generated in every case where we get a successful
16916 connected or resolved cell.
16917 - Track reasons for OR connection failure; make these reasons
16918 available via the controller interface. (Patch from Mike Perry.)
16919 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
16920 can learn when clients are sending malformed hostnames to Tor.
16921 - Specify and implement some of the controller status events.
16922 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
16923 - Reimplement GETINFO so that info/names stays in sync with the
16925 - Implement "GETINFO fingerprint".
16926 - Implement "SETEVENTS GUARD" so controllers can get updates on
16927 entry guard status as it changes.
16928 - Make all connections to addresses of the form ".noconnect"
16929 immediately get closed. This lets application/controller combos
16930 successfully test whether they're talking to the same Tor by
16931 watching for STREAM events.
16932 - Add a REASON field to CIRC events; for backward compatibility, this
16933 field is sent only to controllers that have enabled the extended
16934 event format. Also, add additional reason codes to explain why
16935 a given circuit has been destroyed or truncated. (Patches from
16937 - Add a REMOTE_REASON field to extended CIRC events to tell the
16938 controller why a remote OR told us to close a circuit.
16939 - Stream events also now have REASON and REMOTE_REASON fields,
16940 working much like those for circuit events.
16941 - There's now a GETINFO ns/... field so that controllers can ask Tor
16942 about the current status of a router.
16943 - A new event type "NS" to inform a controller when our opinion of
16944 a router's status has changed.
16945 - Add a GETINFO events/names and GETINFO features/names so controllers
16946 can tell which events and features are supported.
16947 - A new CLEARDNSCACHE signal to allow controllers to clear the
16948 client-side DNS cache without expiring circuits.
16949 - Fix CIRC controller events so that controllers can learn the
16950 identity digests of non-Named servers used in circuit paths.
16951 - Let controllers ask for more useful identifiers for servers. Instead
16952 of learning identity digests for un-Named servers and nicknames
16953 for Named servers, the new identifiers include digest, nickname,
16954 and indication of Named status. Off by default; see control-spec.txt
16955 for more information.
16956 - Add a "getinfo address" controller command so it can display Tor's
16957 best guess to the user.
16958 - New controller event to alert the controller when our server
16959 descriptor has changed.
16960 - Give more meaningful errors on controller authentication failure.
16961 - Export the default exit policy via the control port, so controllers
16962 don't need to guess what it is / will be later.
16964 o Minor bugfixes, controller:
16965 - When creating a circuit via the controller, send a 'launched'
16966 event when we're done, so we follow the spec better.
16967 - Correct the control spec to match how the code actually responds
16968 to 'getinfo addr-mappings/*'. Reported by daejees.
16969 - The control spec described a GUARDS event, but the code
16970 implemented a GUARD event. Standardize on GUARD, but let people
16971 ask for GUARDS too. Reported by daejees.
16972 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
16973 clear the corresponding on_circuit variable, and remember later
16974 that we don't need to send a redundant CLOSED event. (Resolves part
16976 - Report events where a resolve succeeded or where we got a socks
16977 protocol error correctly, rather than calling both of them
16979 - Change reported stream target addresses to IP consistently when
16980 we finally get the IP from an exit node.
16981 - Send log messages to the controller even if they happen to be very
16983 - Flush ERR-level controller status events just like we currently
16984 flush ERR-level log events, so that a Tor shutdown doesn't prevent
16985 the controller from learning about current events.
16986 - Report the circuit number correctly in STREAM CLOSED events. Bug
16987 reported by Mike Perry.
16988 - Do not report bizarre values for results of accounting GETINFOs
16989 when the last second's write or read exceeds the allotted bandwidth.
16990 - Report "unrecognized key" rather than an empty string when the
16991 controller tries to fetch a networkstatus that doesn't exist.
16992 - When the controller does a "GETINFO network-status", tell it
16993 about even those routers whose descriptors are very old, and use
16994 long nicknames where appropriate.
16995 - Fix handling of verbose nicknames with ORCONN controller events:
16996 make them show up exactly when requested, rather than exactly when
16998 - Controller signals now work on non-Unix platforms that don't define
16999 SIGUSR1 and SIGUSR2 the way we expect.
17000 - Respond to SIGNAL command before we execute the signal, in case
17001 the signal shuts us down. Suggested by Karsten Loesing.
17002 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
17004 o Minor features, code performance:
17005 - Major performance improvement on inserting descriptors: change
17006 algorithm from O(n^2) to O(n).
17007 - Do not rotate onion key immediately after setting it for the first
17009 - Call router_have_min_dir_info half as often. (This is showing up in
17010 some profiles, but not others.)
17011 - When using GCC, make log_debug never get called at all, and its
17012 arguments never get evaluated, when no debug logs are configured.
17013 (This is showing up in some profiles, but not others.)
17014 - Statistics dumped by -USR2 now include a breakdown of public key
17015 operations, for profiling.
17016 - Make the common memory allocation path faster on machines where
17017 malloc(0) returns a pointer.
17018 - Split circuit_t into origin_circuit_t and or_circuit_t, and
17019 split connection_t into edge, or, dir, control, and base structs.
17020 These will save quite a bit of memory on busy servers, and they'll
17021 also help us track down bugs in the code and bugs in the spec.
17022 - Use OpenSSL's AES implementation on platforms where it's faster.
17023 This could save us as much as 10% CPU usage.
17025 o Minor features, descriptors and descriptor handling:
17026 - Avoid duplicate entries on MyFamily line in server descriptor.
17027 - When Tor receives a router descriptor that it asked for, but
17028 no longer wants (because it has received fresh networkstatuses
17029 in the meantime), do not warn the user. Cache the descriptor if
17030 we're a cache; drop it if we aren't.
17031 - Servers no longer ever list themselves in their "family" line,
17032 even if configured to do so. This makes it easier to configure
17033 family lists conveniently.
17035 o Minor fixes, confusing/misleading log messages:
17036 - Display correct results when reporting which versions are
17037 recommended, and how recommended they are. (Resolves bug 383.)
17038 - Inform the server operator when we decide not to advertise a
17039 DirPort due to AccountingMax enabled or a low BandwidthRate.
17040 - Only include function names in log messages for info/debug messages.
17041 For notice/warn/err, the content of the message should be clear on
17042 its own, and printing the function name only confuses users.
17043 - Remove even more protocol-related warnings from Tor server logs,
17044 such as bad TLS handshakes and malformed begin cells.
17045 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
17046 when the IP address is mapped through MapAddress to a hostname.
17047 - Fix misleading log messages: an entry guard that is "unlisted",
17048 as well as not known to be "down" (because we've never heard
17049 of it), is not therefore "up".
17051 o Minor fixes, old/obsolete behavior:
17052 - Start assuming we can use a create_fast cell if we don't know
17053 what version a router is running.
17054 - We no longer look for identity and onion keys in "identity.key" and
17055 "onion.key" -- these were replaced by secret_id_key and
17056 secret_onion_key in 0.0.8pre1.
17057 - We no longer require unrecognized directory entries to be
17059 - Drop compatibility with obsolete Tors that permit create cells
17060 to have the wrong circ_id_type.
17061 - Remove code to special-case "-cvs" ending, since it has not
17062 actually mattered since 0.0.9.
17063 - Don't re-write the fingerprint file every restart, unless it has
17066 o Minor fixes, misc client-side behavior:
17067 - Always remove expired routers and networkstatus docs before checking
17068 whether we have enough information to build circuits. (Fixes
17070 - When computing clock skew from directory HTTP headers, consider what
17071 time it was when we finished asking for the directory, not what
17073 - Make our socks5 handling more robust to broken socks clients:
17074 throw out everything waiting on the buffer in between socks
17075 handshake phases, since they can't possibly (so the theory
17076 goes) have predicted what we plan to respond to them.
17077 - Expire socks connections if they spend too long waiting for the
17078 handshake to finish. Previously we would let them sit around for
17079 days, if the connecting application didn't close them either.
17080 - And if the socks handshake hasn't started, don't send a
17081 "DNS resolve socks failed" handshake reply; just close it.
17082 - If the user asks to use invalid exit nodes, be willing to use
17084 - Track unreachable entry guards correctly: don't conflate
17085 'unreachable by us right now' with 'listed as down by the directory
17086 authorities'. With the old code, if a guard was unreachable by us
17087 but listed as running, it would clog our guard list forever.
17088 - Behave correctly in case we ever have a network with more than
17089 2GB/s total advertised capacity.
17090 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
17091 - Fix a memory leak when we ask for "all" networkstatuses and we
17092 get one we don't recognize.
17095 Changes in version 0.1.1.26 - 2006-12-14
17096 o Security bugfixes:
17097 - Stop sending the HttpProxyAuthenticator string to directory
17098 servers when directory connections are tunnelled through Tor.
17099 - Clients no longer store bandwidth history in the state file.
17100 - Do not log introduction points for hidden services if SafeLogging
17104 - Fix an assert failure when a directory authority sets
17105 AuthDirRejectUnlisted and then receives a descriptor from an
17106 unlisted router (reported by seeess).
17109 Changes in version 0.1.1.25 - 2006-11-04
17111 - When a client asks us to resolve (rather than connect to)
17112 an address, and we have a cached answer, give them the cached
17113 answer. Previously, we would give them no answer at all.
17114 - We were building exactly the wrong circuits when we predict
17115 hidden service requirements, meaning Tor would have to build all
17116 its circuits on demand.
17117 - If none of our live entry guards have a high uptime, but we
17118 require a guard with a high uptime, try adding a new guard before
17119 we give up on the requirement. This patch should make long-lived
17120 connections more stable on average.
17121 - When testing reachability of our DirPort, don't launch new
17122 tests when there's already one in progress -- unreachable
17123 servers were stacking up dozens of testing streams.
17125 o Security bugfixes:
17126 - When the user sends a NEWNYM signal, clear the client-side DNS
17127 cache too. Otherwise we continue to act on previous information.
17130 - Avoid a memory corruption bug when creating a hash table for
17132 - Avoid possibility of controller-triggered crash when misusing
17133 certain commands from a v0 controller on platforms that do not
17134 handle printf("%s",NULL) gracefully.
17135 - Avoid infinite loop on unexpected controller input.
17136 - Don't log spurious warnings when we see a circuit close reason we
17137 don't recognize; it's probably just from a newer version of Tor.
17138 - Add Vidalia to the OS X uninstaller script, so when we uninstall
17139 Tor/Privoxy we also uninstall Vidalia.
17142 Changes in version 0.1.1.24 - 2006-09-29
17144 - Allow really slow clients to not hang up five minutes into their
17145 directory downloads (suggested by Adam J. Richter).
17146 - Fix major performance regression from 0.1.0.x: instead of checking
17147 whether we have enough directory information every time we want to
17148 do something, only check when the directory information has changed.
17149 This should improve client CPU usage by 25-50%.
17150 - Don't crash if, after a server has been running for a while,
17151 it can't resolve its hostname.
17152 - When a client asks us to resolve (not connect to) an address,
17153 and we have a cached answer, give them the cached answer.
17154 Previously, we would give them no answer at all.
17157 - Allow Tor to start when RunAsDaemon is set but no logs are set.
17158 - Don't crash when the controller receives a third argument to an
17159 "extendcircuit" request.
17160 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
17161 response; fix error code when "getinfo dir/status/" fails.
17162 - Fix configure.in to not produce broken configure files with
17163 more recent versions of autoconf. Thanks to Clint for his auto*
17165 - Fix security bug on NetBSD that could allow someone to force
17166 uninitialized RAM to be sent to a server's DNS resolver. This
17167 only affects NetBSD and other platforms that do not bounds-check
17169 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
17170 methods: these are known to be buggy.
17171 - If we're a directory mirror and we ask for "all" network status
17172 documents, we would discard status documents from authorities
17173 we don't recognize.
17176 Changes in version 0.1.1.23 - 2006-07-30
17178 - Fast Tor servers, especially exit nodes, were triggering asserts
17179 due to a bug in handling the list of pending DNS resolves. Some
17180 bugs still remain here; we're hunting them.
17181 - Entry guards could crash clients by sending unexpected input.
17182 - More fixes on reachability testing: if you find yourself reachable,
17183 then don't ever make any client requests (so you stop predicting
17184 circuits), then hup or have your clock jump, then later your IP
17185 changes, you won't think circuits are working, so you won't try to
17186 test reachability, so you won't publish.
17189 - Avoid a crash if the controller does a resetconf firewallports
17190 and then a setconf fascistfirewall=1.
17191 - Avoid an integer underflow when the dir authority decides whether
17192 a router is stable: we might wrongly label it stable, and compute
17193 a slightly wrong median stability, when a descriptor is published
17195 - Fix a place where we might trigger an assert if we can't build our
17196 own server descriptor yet.
17199 Changes in version 0.1.1.22 - 2006-07-05
17201 - Fix a big bug that was causing servers to not find themselves
17202 reachable if they changed IP addresses. Since only 0.1.1.22+
17203 servers can do reachability testing correctly, now we automatically
17204 make sure to test via one of these.
17205 - Fix to allow clients and mirrors to learn directory info from
17206 descriptor downloads that get cut off partway through.
17207 - Directory authorities had a bug in deciding if a newly published
17208 descriptor was novel enough to make everybody want a copy -- a few
17209 servers seem to be publishing new descriptors many times a minute.
17211 - Fix a rare bug that was causing some servers to complain about
17212 "closing wedged cpuworkers" and skip some circuit create requests.
17213 - Make the Exit flag in directory status documents actually work.
17216 Changes in version 0.1.1.21 - 2006-06-10
17217 o Crash and assert fixes from 0.1.1.20:
17218 - Fix a rare crash on Tor servers that have enabled hibernation.
17219 - Fix a seg fault on startup for Tor networks that use only one
17220 directory authority.
17221 - Fix an assert from a race condition that occurs on Tor servers
17222 while exiting, where various threads are trying to log that they're
17223 exiting, and delete the logs, at the same time.
17224 - Make our unit tests pass again on certain obscure platforms.
17227 - Add support for building SUSE RPM packages.
17228 - Speed up initial bootstrapping for clients: if we are making our
17229 first ever connection to any entry guard, then don't mark it down
17231 - When only one Tor server in the network is labelled as a guard,
17232 and we've already picked him, we would cycle endlessly picking him
17233 again, being unhappy about it, etc. Now we specifically exclude
17234 current guards when picking a new guard.
17235 - Servers send create cells more reliably after the TLS connection
17236 is established: we were sometimes forgetting to send half of them
17237 when we had more than one pending.
17238 - If we get a create cell that asks us to extend somewhere, but the
17239 Tor server there doesn't match the expected digest, we now send
17240 a destroy cell back, rather than silently doing nothing.
17241 - Make options->RedirectExit work again.
17242 - Make cookie authentication for the controller work again.
17243 - Stop being picky about unusual characters in the arguments to
17244 mapaddress. It's none of our business.
17245 - Add a new config option "TestVia" that lets you specify preferred
17246 middle hops to use for test circuits. Perhaps this will let me
17247 debug the reachability problems better.
17249 o Log / documentation fixes:
17250 - If we're a server and some peer has a broken TLS certificate, don't
17251 log about it unless ProtocolWarnings is set, i.e., we want to hear
17252 about protocol violations by others.
17253 - Fix spelling of VirtualAddrNetwork in man page.
17254 - Add a better explanation at the top of the autogenerated torrc file
17255 about what happened to our old torrc.
17258 Changes in version 0.1.1.20 - 2006-05-23
17259 o Crash and assert fixes from 0.1.0.17:
17260 - Fix assert bug in close_logs() on exit: when we close and delete
17261 logs, remove them all from the global "logfiles" list.
17262 - Fix an assert error when we're out of space in the connection_list
17263 and we try to post a hidden service descriptor (reported by Peter
17265 - Fix a rare assert error when we've tried all intro points for
17266 a hidden service and we try fetching the service descriptor again:
17267 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
17268 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
17269 out and refuse the setconf if it would fail.
17270 - If you specify a relative torrc path and you set RunAsDaemon in
17271 your torrc, then it chdir()'s to the new directory. If you then
17272 HUP, it tries to load the new torrc location, fails, and exits.
17273 The fix: no longer allow a relative path to torrc when using -f.
17274 - Check for integer overflows in more places, when adding elements
17275 to smartlists. This could possibly prevent a buffer overflow
17276 on malicious huge inputs.
17278 o Security fixes, major:
17279 - When we're printing strings from the network, don't try to print
17280 non-printable characters. Now we're safer against shell escape
17281 sequence exploits, and also against attacks to fool users into
17282 misreading their logs.
17283 - Implement entry guards: automatically choose a handful of entry
17284 nodes and stick with them for all circuits. Only pick new guards
17285 when the ones you have are unsuitable, and if the old guards
17286 become suitable again, switch back. This will increase security
17287 dramatically against certain end-point attacks. The EntryNodes
17288 config option now provides some hints about which entry guards you
17289 want to use most; and StrictEntryNodes means to only use those.
17290 Fixes CVE-2006-0414.
17291 - Implement exit enclaves: if we know an IP address for the
17292 destination, and there's a running Tor server at that address
17293 which allows exit to the destination, then extend the circuit to
17294 that exit first. This provides end-to-end encryption and end-to-end
17295 authentication. Also, if the user wants a .exit address or enclave,
17296 use 4 hops rather than 3, and cannibalize a general circ for it
17298 - Obey our firewall options more faithfully:
17299 . If we can't get to a dirserver directly, try going via Tor.
17300 . Don't ever try to connect (as a client) to a place our
17301 firewall options forbid.
17302 . If we specify a proxy and also firewall options, obey the
17303 firewall options even when we're using the proxy: some proxies
17304 can only proxy to certain destinations.
17305 - Make clients regenerate their keys when their IP address changes.
17306 - For the OS X package's modified privoxy config file, comment
17307 out the "logfile" line so we don't log everything passed
17309 - Our TLS handshakes were generating a single public/private
17310 keypair for the TLS context, rather than making a new one for
17311 each new connection. Oops. (But we were still rotating them
17312 periodically, so it's not so bad.)
17313 - When we were cannibalizing a circuit with a particular exit
17314 node in mind, we weren't checking to see if that exit node was
17315 already present earlier in the circuit. Now we are.
17316 - Require server descriptors to list IPv4 addresses -- hostnames
17317 are no longer allowed. This also fixes potential vulnerabilities
17318 to servers providing hostnames as their address and then
17319 preferentially resolving them so they can partition users.
17320 - Our logic to decide if the OR we connected to was the right guy
17321 was brittle and maybe open to a mitm for invalid routers.
17323 o Security fixes, minor:
17324 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
17325 Ian Goldberg can prove things about our handshake protocol more
17327 - Make directory authorities generate a separate "guard" flag to
17328 mean "would make a good entry guard". Clients now honor the
17329 is_guard flag rather than looking at is_fast or is_stable.
17330 - Try to list MyFamily elements by key, not by nickname, and warn
17331 if we've not heard of a server.
17332 - Start using RAND_bytes rather than RAND_pseudo_bytes from
17333 OpenSSL. Also, reseed our entropy every hour, not just at
17334 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
17335 - Refuse server descriptors where the fingerprint line doesn't match
17336 the included identity key. Tor doesn't care, but other apps (and
17337 humans) might actually be trusting the fingerprint line.
17338 - We used to kill the circuit when we receive a relay command we
17339 don't recognize. Now we just drop that cell.
17340 - Fix a bug found by Lasse Overlier: when we were making internal
17341 circuits (intended to be cannibalized later for rendezvous and
17342 introduction circuits), we were picking them so that they had
17343 useful exit nodes. There was no need for this, and it actually
17344 aids some statistical attacks.
17345 - Start treating internal circuits and exit circuits separately.
17346 It's important to keep them separate because internal circuits
17347 have their last hops picked like middle hops, rather than like
17348 exit hops. So exiting on them will break the user's expectations.
17349 - Fix a possible way to DoS dirservers.
17350 - When the client asked for a rendezvous port that the hidden
17351 service didn't want to provide, we were sending an IP address
17352 back along with the end cell. Fortunately, it was zero. But stop
17355 o Packaging improvements:
17356 - Implement --with-libevent-dir option to ./configure. Improve
17357 search techniques to find libevent, and use those for openssl too.
17358 - Fix a couple of bugs in OpenSSL detection. Deal better when
17359 there are multiple SSLs installed with different versions.
17360 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
17361 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
17363 - Make unit tests (and other invocations that aren't the real Tor)
17364 run without launching listeners, creating subdirectories, and so on.
17365 - The OS X installer was adding a symlink for tor_resolve but
17366 the binary was called tor-resolve (reported by Thomas Hardly).
17367 - Now we can target arch and OS in rpm builds (contributed by
17368 Phobos). Also make the resulting dist-rpm filename match the
17370 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
17371 if you log to syslog and want something other than LOG_DAEMON.
17372 - Fix the torify (tsocks) config file to not use Tor for localhost
17374 - Start shipping socks-extensions.txt, tor-doc-unix.html,
17375 tor-doc-server.html, and stylesheet.css in the tarball.
17376 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
17377 They are useless now.
17378 - Add Peter Palfrader's contributed check-tor script. It lets you
17379 easily check whether a given server (referenced by nickname)
17380 is reachable by you.
17381 - Add BSD-style contributed startup script "rc.subr" from Peter
17384 o Directory improvements -- new directory protocol:
17385 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
17386 - Authorities and caches publish individual descriptors (by
17387 digest, by fingerprint, by "all", and by "tell me yours").
17388 - Clients don't download or use the old directory anymore. Now they
17389 download network-statuses from the directory authorities, and
17390 fetch individual server descriptors as needed from mirrors.
17391 - Clients don't download descriptors of non-running servers.
17392 - Download descriptors by digest, not by fingerprint. Caches try to
17393 download all listed digests from authorities; clients try to
17394 download "best" digests from caches. This avoids partitioning
17395 and isolating attacks better.
17396 - Only upload a new server descriptor when options change, 18
17397 hours have passed, uptime is reset, or bandwidth changes a lot.
17398 - Directory authorities silently throw away new descriptors that
17399 haven't changed much if the timestamps are similar. We do this to
17400 tolerate older Tor servers that upload a new descriptor every 15
17401 minutes. (It seemed like a good idea at the time.)
17402 - Clients choose directory servers from the network status lists,
17403 not from their internal list of router descriptors. Now they can
17404 go to caches directly rather than needing to go to authorities
17405 to bootstrap the first set of descriptors.
17406 - When picking a random directory, prefer non-authorities if any
17408 - Add a new flag to network-status indicating whether the server
17409 can answer v2 directory requests too.
17410 - Directory mirrors now cache up to 16 unrecognized network-status
17411 docs, so new directory authorities will be cached too.
17412 - Stop parsing, storing, or using running-routers output (but
17413 mirrors still cache and serve it).
17414 - Clients consider a threshold of "versioning" directory authorities
17415 before deciding whether to warn the user that he's obsolete.
17416 - Authorities publish separate sorted lists of recommended versions
17417 for clients and for servers.
17418 - Change DirServers config line to note which dirs are v1 authorities.
17419 - Put nicknames on the DirServer line, so we can refer to them
17420 without requiring all our users to memorize their IP addresses.
17421 - Remove option when getting directory cache to see whether they
17422 support running-routers; they all do now. Replace it with one
17423 to see whether caches support v2 stuff.
17424 - Stop listing down or invalid nodes in the v1 directory. This
17425 reduces its bulk by about 1/3, and reduces load on mirrors.
17426 - Mirrors no longer cache the v1 directory as often.
17427 - If we as a directory mirror don't know of any v1 directory
17428 authorities, then don't try to cache any v1 directories.
17430 o Other directory improvements:
17431 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
17432 fifth authoritative directory servers.
17433 - Directory authorities no longer require an open connection from
17434 a server to consider him "reachable". We need this change because
17435 when we add new directory authorities, old servers won't know not
17436 to hang up on them.
17437 - Dir authorities now do their own external reachability testing
17438 of each server, and only list as running the ones they found to
17439 be reachable. We also send back warnings to the server's logs if
17440 it uploads a descriptor that we already believe is unreachable.
17441 - Spread the directory authorities' reachability testing over the
17442 entire testing interval, so we don't try to do 500 TLS's at once
17444 - Make the "stable" router flag in network-status be the median of
17445 the uptimes of running valid servers, and make clients pay
17446 attention to the network-status flags. Thus the cutoff adapts
17447 to the stability of the network as a whole, making IRC, IM, etc
17448 connections more reliable.
17449 - Make the v2 dir's "Fast" flag based on relative capacity, just
17450 like "Stable" is based on median uptime. Name everything in the
17451 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
17452 - Retry directory requests if we fail to get an answer we like
17453 from a given dirserver (we were retrying before, but only if
17454 we fail to connect).
17455 - Return a robots.txt on our dirport to discourage google indexing.
17457 o Controller protocol improvements:
17458 - Revised controller protocol (version 1) that uses ascii rather
17459 than binary: tor/doc/control-spec.txt. Add supporting libraries
17460 in python and java and c# so you can use the controller from your
17461 applications without caring how our protocol works.
17462 - Allow the DEBUG controller event to work again. Mark certain log
17463 entries as "don't tell this to controllers", so we avoid cycles.
17464 - New controller function "getinfo accounting", to ask how
17465 many bytes we've used in this time period.
17466 - Add a "resetconf" command so you can set config options like
17467 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
17468 a config option in the torrc with no value, then it clears it
17469 entirely (rather than setting it to its default).
17470 - Add a "getinfo config-file" to tell us where torrc is. Also
17471 expose guard nodes, config options/names.
17472 - Add a "quit" command (when when using the controller manually).
17473 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
17474 stop using any currently-dirty circuits for new streams, so we
17475 don't link new actions to old actions. This also occurs on HUP
17476 or "signal reload".
17477 - If we would close a stream early (e.g. it asks for a .exit that
17478 we know would refuse it) but the LeaveStreamsUnattached config
17479 option is set by the controller, then don't close it.
17480 - Add a new controller event type "authdir_newdescs" that allows
17481 controllers to get all server descriptors that were uploaded to
17482 a router in its role as directory authority.
17483 - New controller option "getinfo desc/all-recent" to fetch the
17484 latest server descriptor for every router that Tor knows about.
17485 - Fix the controller's "attachstream 0" command to treat conn like
17486 it just connected, doing address remapping, handling .exit and
17487 .onion idioms, and so on. Now we're more uniform in making sure
17488 that the controller hears about new and closing connections.
17489 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
17490 the controller. Also, rotate dns and cpu workers if the controller
17491 changes options that will affect them; and initialize the dns
17492 worker cache tree whether or not we start out as a server.
17493 - Add a new circuit purpose 'controller' to let the controller ask
17494 for a circuit that Tor won't try to use. Extend the "extendcircuit"
17495 controller command to let you specify the purpose if you're starting
17496 a new circuit. Add a new "setcircuitpurpose" controller command to
17497 let you change a circuit's purpose after it's been created.
17498 - Let the controller ask for "getinfo dir/server/foo" so it can ask
17499 directly rather than connecting to the dir port. "getinfo
17500 dir/status/foo" also works, but currently only if your DirPort
17502 - Let the controller tell us about certain router descriptors
17503 that it doesn't want Tor to use in circuits. Implement
17504 "setrouterpurpose" and modify "+postdescriptor" to do this.
17505 - If the controller's *setconf commands fail, collect an error
17506 message in a string and hand it back to the controller -- don't
17507 just tell them to go read their logs.
17509 o Scalability, resource management, and performance:
17510 - Fix a major load balance bug: we were round-robin reading in 16 KB
17511 chunks, and servers with bandwidthrate of 20 KB, while downloading
17512 a 600 KB directory, would starve their other connections. Now we
17513 try to be a bit more fair.
17514 - Be more conservative about whether to advertise our DirPort.
17515 The main change is to not advertise if we're running at capacity
17516 and either a) we could hibernate ever or b) our capacity is low
17517 and we're using a default DirPort.
17518 - We weren't cannibalizing circuits correctly for
17519 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
17520 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
17521 build those from scratch. This should make hidden services faster.
17522 - Predict required circuits better, with an eye toward making hidden
17523 services faster on the service end.
17524 - Compress exit policies even more: look for duplicate lines and
17526 - Generate 18.0.0.0/8 address policy format in descs when we can;
17527 warn when the mask is not reducible to a bit-prefix.
17528 - There used to be two ways to specify your listening ports in a
17529 server descriptor: on the "router" line and with a separate "ports"
17530 line. Remove support for the "ports" line.
17531 - Reduce memory requirements in our structs by changing the order
17532 of fields. Replace balanced trees with hash tables. Inline
17533 bottleneck smartlist functions. Add a "Map from digest to void*"
17534 abstraction so we can do less hex encoding/decoding, and use it
17535 in router_get_by_digest(). Many other CPU and memory improvements.
17536 - Allow tor_gzip_uncompress to extract as much as possible from
17537 truncated compressed data. Try to extract as many
17538 descriptors as possible from truncated http responses (when
17539 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
17540 - Make circ->onionskin a pointer, not a static array. moria2 was using
17541 125000 circuit_t's after it had been up for a few weeks, which
17542 translates to 20+ megs of wasted space.
17543 - The private half of our EDH handshake keys are now chosen out
17544 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
17545 - Stop doing the complex voodoo overkill checking for insecure
17546 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
17547 - Do round-robin writes for TLS of at most 16 kB per write. This
17548 might be more fair on loaded Tor servers.
17549 - Do not use unaligned memory access on alpha, mips, or mipsel.
17550 It *works*, but is very slow, so we treat them as if it doesn't.
17552 o Other bugfixes and improvements:
17553 - Start storing useful information to $DATADIR/state, so we can
17554 remember things across invocations of Tor. Retain unrecognized
17555 lines so we can be forward-compatible, and write a TorVersion line
17556 so we can be backward-compatible.
17557 - If ORPort is set, Address is not explicitly set, and our hostname
17558 resolves to a private IP address, try to use an interface address
17559 if it has a public address. Now Windows machines that think of
17560 themselves as localhost can guess their address.
17561 - Regenerate our local descriptor if it's dirty and we try to use
17562 it locally (e.g. if it changes during reachability detection).
17563 This was causing some Tor servers to keep publishing the same
17564 initial descriptor forever.
17565 - Tor servers with dynamic IP addresses were needing to wait 18
17566 hours before they could start doing reachability testing using
17567 the new IP address and ports. This is because they were using
17568 the internal descriptor to learn what to test, yet they were only
17569 rebuilding the descriptor once they decided they were reachable.
17570 - It turns out we couldn't bootstrap a network since we added
17571 reachability detection in 0.1.0.1-rc. Good thing the Tor network
17572 has never gone down. Add an AssumeReachable config option to let
17573 servers and authorities bootstrap. When we're trying to build a
17574 high-uptime or high-bandwidth circuit but there aren't enough
17575 suitable servers, try being less picky rather than simply failing.
17576 - Newly bootstrapped Tor networks couldn't establish hidden service
17577 circuits until they had nodes with high uptime. Be more tolerant.
17578 - Really busy servers were keeping enough circuits open on stable
17579 connections that they were wrapping around the circuit_id
17580 space. (It's only two bytes.) This exposed a bug where we would
17581 feel free to reuse a circuit_id even if it still exists but has
17582 been marked for close. Try to fix this bug. Some bug remains.
17583 - When we fail to bind or listen on an incoming or outgoing
17584 socket, we now close it before refusing, rather than just
17585 leaking it. (Thanks to Peter Palfrader for finding.)
17586 - Fix a file descriptor leak in start_daemon().
17587 - On Windows, you can't always reopen a port right after you've
17588 closed it. So change retry_listeners() to only close and re-open
17589 ports that have changed.
17590 - Workaround a problem with some http proxies that refuse GET
17591 requests that specify "Content-Length: 0". Reported by Adrian.
17592 - Recover better from TCP connections to Tor servers that are
17593 broken but don't tell you (it happens!); and rotate TLS
17594 connections once a week.
17595 - Fix a scary-looking but apparently harmless bug where circuits
17596 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
17597 servers, and never switch to state CIRCUIT_STATE_OPEN.
17598 - Check for even more Windows version flags when writing the platform
17599 string in server descriptors, and note any we don't recognize.
17600 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
17601 get a better idea of why their circuits failed. Not used yet.
17602 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
17603 We don't use them yet, but maybe one day our DNS resolver will be
17604 able to discover them.
17605 - Let people type "tor --install" as well as "tor -install" when they
17606 want to make it an NT service.
17607 - Looks like we were never delivering deflated (i.e. compressed)
17608 running-routers lists, even when asked. Oops.
17609 - We were leaking some memory every time the client changed IPs.
17610 - Clean up more of the OpenSSL memory when exiting, so we can detect
17611 memory leaks better.
17612 - Never call free() on tor_malloc()d memory. This will help us
17613 use dmalloc to detect memory leaks.
17614 - Some Tor servers process billions of cells per day. These
17615 statistics are now uint64_t's.
17616 - Check [X-]Forwarded-For headers in HTTP requests when generating
17617 log messages. This lets people run dirservers (and caches) behind
17618 Apache but still know which IP addresses are causing warnings.
17619 - Fix minor integer overflow in calculating when we expect to use up
17620 our bandwidth allocation before hibernating.
17621 - Lower the minimum required number of file descriptors to 1000,
17622 so we can have some overhead for Valgrind on Linux, where the
17623 default ulimit -n is 1024.
17624 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
17625 and its existence is confusing some users.
17627 o Config option fixes:
17628 - Add a new config option ExitPolicyRejectPrivate which defaults
17629 to on. Now all exit policies will begin with rejecting private
17630 addresses, unless the server operator explicitly turns it off.
17631 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
17632 - Add new ReachableORAddresses and ReachableDirAddresses options
17633 that understand address policies. FascistFirewall is now a synonym
17634 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
17635 - Start calling it FooListenAddress rather than FooBindAddress,
17636 since few of our users know what it means to bind an address
17638 - If the user gave Tor an odd number of command-line arguments,
17639 we were silently ignoring the last one. Now we complain and fail.
17640 This wins the oldest-bug prize -- this bug has been present since
17641 November 2002, as released in Tor 0.0.0.
17642 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
17643 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
17644 it would silently ignore the 6668.
17645 - If we get a linelist or linelist_s config option from the torrc,
17646 e.g. ExitPolicy, and it has no value, warn and skip rather than
17647 silently resetting it to its default.
17648 - Setconf was appending items to linelists, not clearing them.
17649 - Add MyFamily to torrc.sample in the server section, so operators
17650 will be more likely to learn that it exists.
17651 - Make ContactInfo mandatory for authoritative directory servers.
17652 - MaxConn has been obsolete for a while now. Document the ConnLimit
17653 config option, which is a *minimum* number of file descriptors
17654 that must be available else Tor refuses to start.
17655 - Get rid of IgnoreVersion undocumented config option, and make us
17656 only warn, never exit, when we're running an obsolete version.
17657 - Make MonthlyAccountingStart config option truly obsolete now.
17658 - Correct the man page entry on TrackHostExitsExpire.
17659 - Let directory authorities start even if they don't specify an
17660 Address config option.
17661 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
17662 reflect the updated flags in our v2 dir protocol.
17664 o Config option features:
17665 - Add a new config option FastFirstHopPK (on by default) so clients
17666 do a trivial crypto handshake for their first hop, since TLS has
17667 already taken care of confidentiality and authentication.
17668 - Let the user set ControlListenAddress in the torrc. This can be
17669 dangerous, but there are some cases (like a secured LAN) where it
17671 - New config options to help controllers: FetchServerDescriptors
17672 and FetchHidServDescriptors for whether to fetch server
17673 info and hidserv info or let the controller do it, and
17674 PublishServerDescriptor and PublishHidServDescriptors.
17675 - Also let the controller set the __AllDirActionsPrivate config
17676 option if you want all directory fetches/publishes to happen via
17677 Tor (it assumes your controller bootstraps your circuits).
17678 - Add "HardwareAccel" config option: support for crypto hardware
17679 accelerators via OpenSSL. Off by default, until we find somebody
17680 smart who can test it for us. (It appears to produce seg faults
17681 in at least some cases.)
17682 - New config option "AuthDirRejectUnlisted" for directory authorities
17683 as a panic button: if we get flooded with unusable servers we can
17684 revert to only listing servers in the approved-routers file.
17685 - Directory authorities can now reject/invalidate by key and IP,
17686 with the config options "AuthDirInvalid" and "AuthDirReject", or
17687 by marking a fingerprint as "!reject" or "!invalid" (as its
17688 nickname) in the approved-routers file. This is useful since
17689 currently we automatically list servers as running and usable
17690 even if we know they're jerks.
17691 - Add a new config option TestSocks so people can see whether their
17692 applications are using socks4, socks4a, socks5-with-ip, or
17693 socks5-with-fqdn. This way they don't have to keep mucking
17694 with tcpdump and wondering if something got cached somewhere.
17695 - Add "private:*" as an alias in configuration for policies. Now
17696 you can simplify your exit policy rather than needing to list
17697 every single internal or nonroutable network space.
17698 - Accept "private:*" in routerdesc exit policies; not generated yet
17699 because older Tors do not understand it.
17700 - Add configuration option "V1AuthoritativeDirectory 1" which
17701 moria1, moria2, and tor26 have set.
17702 - Implement an option, VirtualAddrMask, to set which addresses
17703 get handed out in response to mapaddress requests. This works
17704 around a bug in tsocks where 127.0.0.0/8 is never socksified.
17705 - Add a new config option FetchUselessDescriptors, off by default,
17706 for when you plan to run "exitlist" on your client and you want
17707 to know about even the non-running descriptors.
17708 - SocksTimeout: How long do we let a socks connection wait
17709 unattached before we fail it?
17710 - CircuitBuildTimeout: Cull non-open circuits that were born
17711 at least this many seconds ago.
17712 - CircuitIdleTimeout: Cull open clean circuits that were born
17713 at least this many seconds ago.
17714 - New config option SafeSocks to reject all application connections
17715 using unsafe socks protocols. Defaults to off.
17717 o Improved and clearer log messages:
17718 - Reduce clutter in server logs. We're going to try to make
17719 them actually usable now. New config option ProtocolWarnings that
17720 lets you hear about how _other Tors_ are breaking the protocol. Off
17722 - Divide log messages into logging domains. Once we put some sort
17723 of interface on this, it will let people looking at more verbose
17724 log levels specify the topics they want to hear more about.
17725 - Log server fingerprint on startup, so new server operators don't
17726 have to go hunting around their filesystem for it.
17727 - Provide dire warnings to any users who set DirServer manually;
17728 move it out of torrc.sample and into torrc.complete.
17729 - Make the log message less scary when all the dirservers are
17730 temporarily unreachable.
17731 - When tor_socketpair() fails in Windows, give a reasonable
17732 Windows-style errno back.
17733 - Improve tor_gettimeofday() granularity on windows.
17734 - We were printing the number of idle dns workers incorrectly when
17736 - Handle duplicate lines in approved-routers files without warning.
17737 - We were whining about using socks4 or socks5-with-local-lookup
17738 even when it's an IP address in the "virtual" range we designed
17739 exactly for this case.
17740 - Check for named servers when looking them up by nickname;
17741 warn when we're calling a non-named server by its nickname;
17742 don't warn twice about the same name.
17743 - Downgrade the dirserver log messages when whining about
17745 - Correct "your server is reachable" log entries to indicate that
17746 it was self-testing that told us so.
17747 - If we're trying to be a Tor server and running Windows 95/98/ME
17748 as a server, explain that we'll likely crash.
17749 - Provide a more useful warn message when our onion queue gets full:
17750 the CPU is too slow or the exit policy is too liberal.
17751 - Don't warn when we receive a 503 from a dirserver/cache -- this
17752 will pave the way for them being able to refuse if they're busy.
17753 - When we fail to bind a listener, try to provide a more useful
17754 log message: e.g., "Is Tor already running?"
17755 - Only start testing reachability once we've established a
17756 circuit. This will make startup on dir authorities less noisy.
17757 - Don't try to upload hidden service descriptors until we have
17758 established a circuit.
17759 - Tor didn't warn when it failed to open a log file.
17760 - Warn when listening on a public address for socks. We suspect a
17761 lot of people are setting themselves up as open socks proxies,
17762 and they have no idea that jerks on the Internet are using them,
17763 since they simply proxy the traffic into the Tor network.
17764 - Give a useful message when people run Tor as the wrong user,
17765 rather than telling them to start chowning random directories.
17766 - Fix a harmless bug that was causing Tor servers to log
17767 "Got an end because of misc error, but we're not an AP. Closing."
17768 - Fix wrong log message when you add a "HiddenServiceNodes" config
17769 line without any HiddenServiceDir line (reported by Chris Thomas).
17770 - Directory authorities now stop whining so loudly about bad
17771 descriptors that they fetch from other dirservers. So when there's
17772 a log complaint, it's for sure from a freshly uploaded descriptor.
17773 - When logging via syslog, include the pid whenever we provide
17774 a log entry. Suggested by Todd Fries.
17775 - When we're shutting down and we do something like try to post a
17776 server descriptor or rendezvous descriptor, don't complain that
17777 we seem to be unreachable. Of course we are, we're shutting down.
17778 - Change log line for unreachability to explicitly suggest /etc/hosts
17779 as the culprit. Also make it clearer what IP address and ports we're
17780 testing for reachability.
17781 - Put quotes around user-supplied strings when logging so users are
17782 more likely to realize if they add bad characters (like quotes)
17784 - NT service patch from Matt Edman to improve error messages on Win32.
17787 Changes in version 0.1.0.17 - 2006-02-17
17788 o Crash bugfixes on 0.1.0.x:
17789 - When servers with a non-zero DirPort came out of hibernation,
17790 sometimes they would trigger an assert.
17792 o Other important bugfixes:
17793 - On platforms that don't have getrlimit (like Windows), we were
17794 artificially constraining ourselves to a max of 1024
17795 connections. Now just assume that we can handle as many as 15000
17796 connections. Hopefully this won't cause other problems.
17798 o Backported features:
17799 - When we're a server, a client asks for an old-style directory,
17800 and our write bucket is empty, don't give it to him. This way
17801 small servers can continue to serve the directory *sometimes*,
17802 without getting overloaded.
17803 - Whenever you get a 503 in response to a directory fetch, try
17804 once more. This will become important once servers start sending
17805 503's whenever they feel busy.
17806 - Fetch a new directory every 120 minutes, not every 40 minutes.
17807 Now that we have hundreds of thousands of users running the old
17808 directory algorithm, it's starting to hurt a lot.
17809 - Bump up the period for forcing a hidden service descriptor upload
17810 from 20 minutes to 1 hour.
17813 Changes in version 0.1.0.16 - 2006-01-02
17814 o Crash bugfixes on 0.1.0.x:
17815 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
17816 corrupting the heap, losing FDs, or crashing when we need to resize
17817 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
17818 - It turns out sparc64 platforms crash on unaligned memory access
17819 too -- so detect and avoid this.
17820 - Handle truncated compressed data correctly (by detecting it and
17822 - Fix possible-but-unlikely free(NULL) in control.c.
17823 - When we were closing connections, there was a rare case that
17824 stomped on memory, triggering seg faults and asserts.
17825 - Avoid potential infinite recursion when building a descriptor. (We
17826 don't know that it ever happened, but better to fix it anyway.)
17827 - We were neglecting to unlink marked circuits from soon-to-close OR
17828 connections, which caused some rare scribbling on freed memory.
17829 - Fix a memory stomping race bug when closing the joining point of two
17830 rendezvous circuits.
17831 - Fix an assert in time parsing found by Steven Murdoch.
17833 o Other bugfixes on 0.1.0.x:
17834 - When we're doing reachability testing, provide more useful log
17835 messages so the operator knows what to expect.
17836 - Do not check whether DirPort is reachable when we are suppressing
17837 advertising it because of hibernation.
17838 - When building with -static or on Solaris, we sometimes needed -ldl.
17839 - One of the dirservers (tor26) changed its IP address.
17840 - When we're deciding whether a stream has enough circuits around
17841 that can handle it, count the freshly dirty ones and not the ones
17842 that are so dirty they won't be able to handle it.
17843 - When we're expiring old circuits, we had a logic error that caused
17844 us to close new rendezvous circuits rather than old ones.
17845 - Give a more helpful log message when you try to change ORPort via
17846 the controller: you should upgrade Tor if you want that to work.
17847 - We were failing to parse Tor versions that start with "Tor ".
17848 - Tolerate faulty streams better: when a stream fails for reason
17849 exitpolicy, stop assuming that the router is lying about his exit
17850 policy. When a stream fails for reason misc, allow it to retry just
17851 as if it was resolvefailed. When a stream has failed three times,
17852 reset its failure count so we can try again and get all three tries.
17855 Changes in version 0.1.0.15 - 2005-09-23
17856 o Bugfixes on 0.1.0.x:
17857 - Reject ports 465 and 587 (spam targets) in default exit policy.
17858 - Don't crash when we don't have any spare file descriptors and we
17859 try to spawn a dns or cpu worker.
17860 - Get rid of IgnoreVersion undocumented config option, and make us
17861 only warn, never exit, when we're running an obsolete version.
17862 - Don't try to print a null string when your server finds itself to
17863 be unreachable and the Address config option is empty.
17864 - Make the numbers in read-history and write-history into uint64s,
17865 so they don't overflow and publish negatives in the descriptor.
17866 - Fix a minor memory leak in smartlist_string_remove().
17867 - We were only allowing ourselves to upload a server descriptor at
17868 most every 20 minutes, even if it changed earlier than that.
17869 - Clean up log entries that pointed to old URLs.
17872 Changes in version 0.1.0.14 - 2005-08-08
17873 o Bugfixes on 0.1.0.x:
17874 - Fix the other half of the bug with crypto handshakes
17876 - Fix an assert trigger if you send a 'signal term' via the
17877 controller when it's listening for 'event info' messages.
17880 Changes in version 0.1.0.13 - 2005-08-04
17881 o Bugfixes on 0.1.0.x:
17882 - Fix a critical bug in the security of our crypto handshakes.
17883 - Fix a size_t underflow in smartlist_join_strings2() that made
17884 it do bad things when you hand it an empty smartlist.
17885 - Fix Windows installer to ship Tor license (thanks to Aphex for
17886 pointing out this oversight) and put a link to the doc directory
17888 - Explicitly set no-unaligned-access for sparc: it turns out the
17889 new gcc's let you compile broken code, but that doesn't make it
17893 Changes in version 0.1.0.12 - 2005-07-18
17894 o New directory servers:
17895 - tor26 has changed IP address.
17897 o Bugfixes on 0.1.0.x:
17898 - Fix a possible double-free in tor_gzip_uncompress().
17899 - When --disable-threads is set, do not search for or link against
17900 pthreads libraries.
17901 - Don't trigger an assert if an authoritative directory server
17902 claims its dirport is 0.
17903 - Fix bug with removing Tor as an NT service: some people were
17904 getting "The service did not return an error." Thanks to Matt
17908 Changes in version 0.1.0.11 - 2005-06-30
17909 o Bugfixes on 0.1.0.x:
17910 - Fix major security bug: servers were disregarding their
17911 exit policies if clients behaved unexpectedly.
17912 - Make OS X init script check for missing argument, so we don't
17913 confuse users who invoke it incorrectly.
17914 - Fix a seg fault in "tor --hash-password foo".
17915 - The MAPADDRESS control command was broken.
17918 Changes in version 0.1.0.10 - 2005-06-14
17920 - Make NT services work and start on startup on Win32 (based on
17921 patch by Matt Edman). See the FAQ entry for details.
17922 - Make 'platform' string in descriptor more accurate for Win32
17923 servers, so it's not just "unknown platform".
17924 - REUSEADDR on normal platforms means you can rebind to the port
17925 right after somebody else has let it go. But REUSEADDR on Win32
17926 means you can bind to the port _even when somebody else already
17927 has it bound_! So, don't do that on Win32.
17928 - Clean up the log messages when starting on Win32 with no config
17930 - Allow seeding the RNG on Win32 even when you're not running as
17931 Administrator. If seeding the RNG on Win32 fails, quit.
17933 o Assert / crash bugs:
17934 - Refuse relay cells that claim to have a length larger than the
17935 maximum allowed. This prevents a potential attack that could read
17936 arbitrary memory (e.g. keys) from an exit server's process
17938 - If unofficial Tor clients connect and send weird TLS certs, our
17939 Tor server triggers an assert. Stop asserting, and start handling
17940 TLS errors better in other situations too.
17941 - Fix a race condition that can trigger an assert when we have a
17942 pending create cell and an OR connection attempt fails.
17945 - Use pthreads for worker processes rather than forking. This was
17946 forced because when we forked, we ended up wasting a lot of
17947 duplicate ram over time.
17948 - Also switch to foo_r versions of some library calls to allow
17949 reentry and threadsafeness.
17950 - Implement --disable-threads configure option. Disable threads on
17951 netbsd and openbsd by default, because they have no reentrant
17952 resolver functions (!), and on solaris since it has other
17954 - Fix possible bug on threading platforms (e.g. win32) which was
17955 leaking a file descriptor whenever a cpuworker or dnsworker died.
17956 - Fix a minor memory leak when somebody establishes an introduction
17957 point at your Tor server.
17958 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
17960 - Add ./configure --with-dmalloc option, to track memory leaks.
17961 - And try to free all memory on closing, so we can detect what
17964 o Protocol correctness:
17965 - When we've connected to an OR and handshaked but didn't like
17966 the result, we were closing the conn without sending destroy
17967 cells back for pending circuits. Now send those destroys.
17968 - Start sending 'truncated' cells back rather than destroy cells
17969 if the circuit closes in front of you. This means we won't have
17970 to abandon partially built circuits.
17971 - Handle changed router status correctly when dirserver reloads
17972 fingerprint file. We used to be dropping all unverified descriptors
17973 right then. The bug was hidden because we would immediately
17974 fetch a directory from another dirserver, which would include the
17975 descriptors we just dropped.
17976 - Revise tor-spec to add more/better stream end reasons.
17977 - Revise all calls to connection_edge_end to avoid sending 'misc',
17978 and to take errno into account where possible.
17979 - Client now retries when streams end early for 'hibernating' or
17980 'resource limit' reasons, rather than failing them.
17981 - Try to be more zealous about calling connection_edge_end when
17982 things go bad with edge conns in connection.c.
17984 o Robustness improvements:
17985 - Better handling for heterogeneous / unreliable nodes:
17986 - Annotate circuits with whether they aim to contain high uptime
17987 nodes and/or high capacity nodes. When building circuits, choose
17989 - This means that every single node in an intro rend circuit,
17990 not just the last one, will have a minimum uptime.
17991 - New config option LongLivedPorts to indicate application streams
17992 that will want high uptime circuits.
17993 - Servers reset uptime when a dir fetch entirely fails. This
17994 hopefully reflects stability of the server's network connectivity.
17995 - If somebody starts his tor server in Jan 2004 and then fixes his
17996 clock, don't make his published uptime be a year.
17997 - Reset published uptime when we wake up from hibernation.
17998 - Introduce a notion of 'internal' circs, which are chosen without
17999 regard to the exit policy of the last hop. Intro and rendezvous
18000 circs must be internal circs, to avoid leaking information. Resolve
18001 and connect streams can use internal circs if they want.
18002 - New circuit pooling algorithm: keep track of what destination ports
18003 we've used recently (start out assuming we'll want to use 80), and
18004 make sure to have enough circs around to satisfy these ports. Also
18005 make sure to have 2 internal circs around if we've required internal
18006 circs lately (and with high uptime if we've seen that lately too).
18007 - Turn addr_policy_compare from a tristate to a quadstate; this should
18008 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
18009 for google.com" problem.
18010 - When a client asks us for a dir mirror and we don't have one,
18011 launch an attempt to get a fresh one.
18012 - First cut at support for "create-fast" cells. Clients can use
18013 these when extending to their first hop, since the TLS already
18014 provides forward secrecy and authentication. Not enabled on
18017 o Reachability testing.
18018 - Your Tor server will automatically try to see if its ORPort and
18019 DirPort are reachable from the outside, and it won't upload its
18020 descriptor until it decides at least ORPort is reachable (when
18021 DirPort is not yet found reachable, publish it as zero).
18022 - When building testing circs for ORPort testing, use only
18023 high-bandwidth nodes, so fewer circuits fail.
18024 - Notice when our IP changes, and reset stats/uptime/reachability.
18025 - Authdirservers don't do ORPort reachability detection, since
18026 they're in clique mode, so it will be rare to find a server not
18027 already connected to them.
18028 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
18032 - Now we allow two unverified servers with the same nickname
18033 but different keys. But if a nickname is verified, only that
18034 nickname+key are allowed.
18035 - If you're an authdirserver connecting to an address:port,
18036 and it's not the OR you were expecting, forget about that
18037 descriptor. If he *was* the one you were expecting, then forget
18038 about all other descriptors for that address:port.
18039 - Allow servers to publish descriptors from 12 hours in the future.
18040 Corollary: only whine about clock skew from the dirserver if
18041 he's a trusted dirserver (since now even verified servers could
18042 have quite wrong clocks).
18043 - Require servers that use the default dirservers to have public IP
18044 addresses. We have too many servers that are configured with private
18045 IPs and their admins never notice the log entries complaining that
18046 their descriptors are being rejected.
18048 o Efficiency improvements:
18049 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
18050 and /dev/poll), and hopefully work better on Windows too.
18051 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
18052 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
18053 - Find libevent even if it's hiding in /usr/local/ and your
18054 CFLAGS and LDFLAGS don't tell you to look there.
18055 - Be able to link with libevent as a shared library (the default
18056 after 1.0d), even if it's hiding in /usr/local/lib and even
18057 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
18058 assuming you're running gcc. Otherwise fail and give a useful
18060 - Switch to a new buffer management algorithm, which tries to avoid
18061 reallocing and copying quite as much. In first tests it looks like
18062 it uses *more* memory on average, but less cpu.
18063 - Switch our internal buffers implementation to use a ring buffer,
18064 to hopefully improve performance for fast servers a lot.
18065 - Reenable the part of the code that tries to flush as soon as an
18066 OR outbuf has a full TLS record available. Perhaps this will make
18067 OR outbufs not grow as huge except in rare cases, thus saving lots
18068 of CPU time plus memory.
18069 - Improve performance for dirservers: stop re-parsing the whole
18070 directory every time you regenerate it.
18071 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
18072 it much faster to look up a circuit for each relay cell.
18073 - Remove most calls to assert_all_pending_dns_resolves_ok(),
18074 since they're eating our cpu on exit nodes.
18075 - Stop wasting time doing a case insensitive comparison for every
18076 dns name every time we do any lookup. Canonicalize the names to
18077 lowercase when you first see them.
18080 - Handle unavailable hidden services better. Handle slow or busy
18081 hidden services better.
18082 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
18083 circ as necessary, if there are any completed ones lying around
18084 when we try to launch one.
18085 - Make hidden services try to establish a rendezvous for 30 seconds
18086 after fetching the descriptor, rather than for n (where n=3)
18087 attempts to build a circuit.
18088 - Adjust maximum skew and age for rendezvous descriptors: let skew
18089 be 48 hours rather than 90 minutes.
18090 - Reject malformed .onion addresses rather then passing them on as
18091 normal web requests.
18094 - More Tor controller support. See
18095 http://tor.eff.org/doc/control-spec.txt for all the new features,
18096 including signals to emulate unix signals from any platform;
18097 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
18098 closestream; closecircuit; etc.
18099 - Encode hashed controller passwords in hex instead of base64,
18100 to make it easier to write controllers.
18101 - Revise control spec and implementation to allow all log messages to
18102 be sent to controller with their severities intact (suggested by
18103 Matt Edman). Disable debug-level logs while delivering a debug-level
18104 log to the controller, to prevent loop. Update TorControl to handle
18105 new log event types.
18107 o New config options/defaults:
18108 - Begin scrubbing sensitive strings from logs by default. Turn off
18109 the config option SafeLogging if you need to do debugging.
18110 - New exit policy: accept most low-numbered ports, rather than
18111 rejecting most low-numbered ports.
18112 - Put a note in the torrc about abuse potential with the default
18114 - Add support for CONNECTing through https proxies, with "HttpsProxy"
18116 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
18117 based on patch from Adam Langley (basic auth only).
18118 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
18119 the fast servers that have been joining lately. (Clients are now
18120 willing to load balance over up to 2 MB of advertised bandwidth
18122 - New config option MaxAdvertisedBandwidth which lets you advertise
18123 a low bandwidthrate (to not attract as many circuits) while still
18124 allowing a higher bandwidthrate in reality.
18125 - Require BandwidthRate to be at least 20kB/s for servers.
18126 - Add a NoPublish config option, so you can be a server (e.g. for
18127 testing running Tor servers in other Tor networks) without
18128 publishing your descriptor to the primary dirservers.
18129 - Add a new AddressMap config directive to rewrite incoming socks
18130 addresses. This lets you, for example, declare an implicit
18131 required exit node for certain sites.
18132 - Add a new TrackHostExits config directive to trigger addressmaps
18133 for certain incoming socks addresses -- for sites that break when
18134 your exit keeps changing (based on patch from Mike Perry).
18135 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
18136 which describes how often we retry making new circuits if current
18137 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
18138 how long we're willing to make use of an already-dirty circuit.
18139 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
18140 a config option "ShutdownWaitLength" (when using kill -INT on
18142 - Fix an edge case in parsing config options: if they say "--"
18143 on the commandline, it's not a config option (thanks weasel).
18144 - New config option DirAllowPrivateAddresses for authdirservers.
18145 Now by default they refuse router descriptors that have non-IP or
18146 private-IP addresses.
18147 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
18148 smart" default value: low for servers and high for clients.
18149 - Some people were putting "Address " in their torrc, and they had
18150 a buggy resolver that resolved " " to 0.0.0.0. Oops.
18151 - If DataDir is ~/.tor, and that expands to /.tor, then default to
18152 LOCALSTATEDIR/tor instead.
18153 - Implement --verify-config command-line option to check if your torrc
18154 is valid without actually launching Tor.
18156 o Logging improvements:
18157 - When dirservers refuse a server descriptor, we now log its
18158 contactinfo, platform, and the poster's IP address.
18159 - Only warn once per nickname from add_nickname_list_to_smartlist()
18160 per failure, so an entrynode or exitnode choice that's down won't
18162 - When we're connecting to an OR and he's got a different nickname/key
18163 than we were expecting, only complain loudly if we're an OP or a
18164 dirserver. Complaining loudly to the OR admins just confuses them.
18165 - Whine at you if you're a server and you don't set your contactinfo.
18166 - Warn when exit policy implicitly allows local addresses.
18167 - Give a better warning when some other server advertises an
18168 ORPort that is actually an apache running ssl.
18169 - If we get an incredibly skewed timestamp from a dirserver mirror
18170 that isn't a verified OR, don't warn -- it's probably him that's
18172 - When a dirserver causes you to give a warn, mention which dirserver
18174 - Initialize libevent later in the startup process, so the logs are
18175 already established by the time we start logging libevent warns.
18176 - Use correct errno on win32 if libevent fails.
18177 - Check and warn about known-bad/slow libevent versions.
18178 - Stop warning about sigpipes in the logs. We're going to
18179 pretend that getting these occasionally is normal and fine.
18181 o New contrib scripts:
18182 - New experimental script tor/contrib/exitlist: a simple python
18183 script to parse directories and find Tor nodes that exit to listed
18185 - New experimental script tor/contrib/ExerciseServer.py (needs more
18186 work) that uses the controller interface to build circuits and
18187 fetch pages over them. This will help us bootstrap servers that
18188 have lots of capacity but haven't noticed it yet.
18189 - New experimental script tor/contrib/PathDemo.py (needs more work)
18190 that uses the controller interface to let you choose whole paths
18192 "<hostname>.<path,separated by dots>.<length of path>.path"
18193 - New contributed script "privoxy-tor-toggle" to toggle whether
18194 Privoxy uses Tor. Seems to be configured for Debian by default.
18195 - Have torctl.in/tor.sh.in check for location of su binary (needed
18199 - chdir() to your datadirectory at the *end* of the daemonize process,
18200 not the beginning. This was a problem because the first time you
18201 run tor, if your datadir isn't there, and you have runasdaemon set
18202 to 1, it will try to chdir to it before it tries to create it. Oops.
18203 - Fix several double-mark-for-close bugs, e.g. where we were finding
18204 a conn for a cell even if that conn is already marked for close.
18205 - Stop most cases of hanging up on a socks connection without sending
18207 - Fix a bug in the RPM package: set home directory for _tor to
18208 something more reasonable when first installing.
18209 - Stop putting nodename in the Platform string in server descriptors.
18210 It doesn't actually help, and it is confusing/upsetting some people.
18211 - When using preferred entry or exit nodes, ignore whether the
18212 circuit wants uptime or capacity. They asked for the nodes, they
18214 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
18215 artificially capped at 500kB.
18216 - Cache local dns resolves correctly even when they're .exit
18218 - If we're hibernating and we get a SIGINT, exit immediately.
18219 - tor-resolve requests were ignoring .exit if there was a working circuit
18220 they could use instead.
18221 - Pay more attention to the ClientOnly config option.
18222 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
18223 installer screens; and don't put stuff into StartupItems unless
18224 the user asks you to.
18227 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
18228 rather than just rejecting it.
18229 - If our clock jumps forward by 100 seconds or more, assume something
18230 has gone wrong with our network and abandon all not-yet-used circs.
18231 - When an application is using socks5, give him the whole variety of
18232 potential socks5 responses (connect refused, host unreachable, etc),
18233 rather than just "success" or "failure".
18234 - A more sane version numbering system. See
18235 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
18236 - Change version parsing logic: a version is "obsolete" if it is not
18237 recommended and (1) there is a newer recommended version in the
18238 same series, or (2) there are no recommended versions in the same
18239 series, but there are some recommended versions in a newer series.
18240 A version is "new" if it is newer than any recommended version in
18242 - Report HTTP reasons to client when getting a response from directory
18243 servers -- so you can actually know what went wrong.
18244 - Reject odd-looking addresses at the client (e.g. addresses that
18245 contain a colon), rather than having the server drop them because
18247 - Stop publishing socksport in the directory, since it's not
18248 actually meant to be public. For compatibility, publish a 0 there
18250 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
18251 cookies to disk and doesn't log each web request to disk. (Thanks
18252 to Brett Carrington for pointing this out.)
18253 - Add OSX uninstall instructions. An actual uninstall script will
18255 - Add "opt hibernating 1" to server descriptor to make it clearer
18256 whether the server is hibernating.
18259 Changes in version 0.0.9.10 - 2005-06-16
18260 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
18261 - Refuse relay cells that claim to have a length larger than the
18262 maximum allowed. This prevents a potential attack that could read
18263 arbitrary memory (e.g. keys) from an exit server's process
18267 Changes in version 0.0.9.9 - 2005-04-23
18268 o Bugfixes on 0.0.9.x:
18269 - If unofficial Tor clients connect and send weird TLS certs, our
18270 Tor server triggers an assert. This release contains a minimal
18271 backport from the broader fix that we put into 0.1.0.4-rc.
18274 Changes in version 0.0.9.8 - 2005-04-07
18275 o Bugfixes on 0.0.9.x:
18276 - We have a bug that I haven't found yet. Sometimes, very rarely,
18277 cpuworkers get stuck in the 'busy' state, even though the cpuworker
18278 thinks of itself as idle. This meant that no new circuits ever got
18279 established. Here's a workaround to kill any cpuworker that's been
18280 busy for more than 100 seconds.
18283 Changes in version 0.0.9.7 - 2005-04-01
18284 o Bugfixes on 0.0.9.x:
18285 - Fix another race crash bug (thanks to Glenn Fink for reporting).
18286 - Compare identity to identity, not to nickname, when extending to
18287 a router not already in the directory. This was preventing us from
18288 extending to unknown routers. Oops.
18289 - Make sure to create OS X Tor user in <500 range, so we aren't
18290 creating actual system users.
18291 - Note where connection-that-hasn't-sent-end was marked, and fix
18292 a few really loud instances of this harmless bug (it's fixed more
18296 Changes in version 0.0.9.6 - 2005-03-24
18297 o Bugfixes on 0.0.9.x (crashes and asserts):
18298 - Add new end stream reasons to maintenance branch. Fix bug where
18299 reason (8) could trigger an assert. Prevent bug from recurring.
18300 - Apparently win32 stat wants paths to not end with a slash.
18301 - Fix assert triggers in assert_cpath_layer_ok(), where we were
18302 blowing away the circuit that conn->cpath_layer points to, then
18303 checking to see if the circ is well-formed. Backport check to make
18304 sure we dont use the cpath on a closed connection.
18305 - Prevent circuit_resume_edge_reading_helper() from trying to package
18306 inbufs for marked-for-close streams.
18307 - Don't crash on hup if your options->address has become unresolvable.
18308 - Some systems (like OS X) sometimes accept() a connection and tell
18309 you the remote host is 0.0.0.0:0. If this happens, due to some
18310 other mis-features, we get confused; so refuse the conn for now.
18312 o Bugfixes on 0.0.9.x (other):
18313 - Fix harmless but scary "Unrecognized content encoding" warn message.
18314 - Add new stream error reason: TORPROTOCOL reason means "you are not
18315 speaking a version of Tor I understand; say bye-bye to your stream."
18316 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
18317 into the future, now that we are more tolerant of skew. This
18318 resolves a bug where a Tor server would refuse to cache a directory
18319 because all the directories it gets are too far in the future;
18320 yet the Tor server never logs any complaints about clock skew.
18321 - Mac packaging magic: make man pages useable, and do not overwrite
18322 existing torrc files.
18323 - Make OS X log happily to /var/log/tor/tor.log
18326 Changes in version 0.0.9.5 - 2005-02-22
18327 o Bugfixes on 0.0.9.x:
18328 - Fix an assert race at exit nodes when resolve requests fail.
18329 - Stop picking unverified dir mirrors--it only leads to misery.
18330 - Patch from Matt Edman to make NT services work better. Service
18331 support is still not compiled into the executable by default.
18332 - Patch from Dmitri Bely so the Tor service runs better under
18333 the win32 SYSTEM account.
18334 - Make tor-resolve actually work (?) on Win32.
18335 - Fix a sign bug when getrlimit claims to have 4+ billion
18336 file descriptors available.
18337 - Stop refusing to start when bandwidthburst == bandwidthrate.
18338 - When create cells have been on the onion queue more than five
18339 seconds, just send back a destroy and take them off the list.
18342 Changes in version 0.0.9.4 - 2005-02-03
18343 o Bugfixes on 0.0.9:
18344 - Fix an assert bug that took down most of our servers: when
18345 a server claims to have 1 GB of bandwidthburst, don't
18347 - Don't crash as badly if we have spawned the max allowed number
18348 of dnsworkers, or we're out of file descriptors.
18349 - Block more file-sharing ports in the default exit policy.
18350 - MaxConn is now automatically set to the hard limit of max
18351 file descriptors we're allowed (ulimit -n), minus a few for
18353 - Give a clearer message when servers need to raise their
18354 ulimit -n when they start running out of file descriptors.
18355 - SGI Compatibility patches from Jan Schaumann.
18356 - Tolerate a corrupt cached directory better.
18357 - When a dirserver hasn't approved your server, list which one.
18358 - Go into soft hibernation after 95% of the bandwidth is used,
18359 not 99%. This is especially important for daily hibernators who
18360 have a small accounting max. Hopefully it will result in fewer
18361 cut connections when the hard hibernation starts.
18362 - Load-balance better when using servers that claim more than
18363 800kB/s of capacity.
18364 - Make NT services work (experimental, only used if compiled in).
18367 Changes in version 0.0.9.3 - 2005-01-21
18368 o Bugfixes on 0.0.9:
18369 - Backport the cpu use fixes from main branch, so busy servers won't
18370 need as much processor time.
18371 - Work better when we go offline and then come back, or when we
18372 run Tor at boot before the network is up. We do this by
18373 optimistically trying to fetch a new directory whenever an
18374 application request comes in and we think we're offline -- the
18375 human is hopefully a good measure of when the network is back.
18376 - Backport some minimal hidserv bugfixes: keep rend circuits open as
18377 long as you keep using them; actually publish hidserv descriptors
18378 shortly after they change, rather than waiting 20-40 minutes.
18379 - Enable Mac startup script by default.
18380 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
18381 - When you update AllowUnverifiedNodes or FirewallPorts via the
18382 controller's setconf feature, we were always appending, never
18384 - When you update HiddenServiceDir via setconf, it was screwing up
18385 the order of reading the lines, making it fail.
18386 - Do not rewrite a cached directory back to the cache; otherwise we
18387 will think it is recent and not fetch a newer one on startup.
18388 - Workaround for webservers that lie about Content-Encoding: Tor
18389 now tries to autodetect compressed directories and compression
18390 itself. This lets us Proxypass dir fetches through apache.
18393 Changes in version 0.0.9.2 - 2005-01-04
18394 o Bugfixes on 0.0.9 (crashes and asserts):
18395 - Fix an assert on startup when the disk is full and you're logging
18397 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
18398 style address, then we'd crash.
18399 - Fix an assert trigger when the running-routers string we get from
18400 a dirserver is broken.
18401 - Make worker threads start and run on win32. Now win32 servers
18403 - Bandaid (not actually fix, but now it doesn't crash) an assert
18404 where the dns worker dies mysteriously and the main Tor process
18405 doesn't remember anything about the address it was resolving.
18407 o Bugfixes on 0.0.9 (Win32):
18408 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
18409 name out of the warning/assert messages.
18410 - Fix a superficial "unhandled error on read" bug on win32.
18411 - The win32 installer no longer requires a click-through for our
18412 license, since our Free Software license grants rights but does not
18414 - Win32: When connecting to a dirserver fails, try another one
18415 immediately. (This was already working for non-win32 Tors.)
18416 - Stop trying to parse $HOME on win32 when hunting for default
18418 - Make tor-resolve.c work on win32 by calling network_init().
18420 o Bugfixes on 0.0.9 (other):
18421 - Make 0.0.9.x build on Solaris again.
18422 - Due to a fencepost error, we were blowing away the \n when reporting
18423 confvalue items in the controller. So asking for multiple config
18424 values at once couldn't work.
18425 - When listing circuits that are pending on an opening OR connection,
18426 if we're an OR we were listing circuits that *end* at us as
18427 being pending on every listener, dns/cpu worker, etc. Stop that.
18428 - Dirservers were failing to create 'running-routers' or 'directory'
18429 strings if we had more than some threshold of routers. Fix them so
18430 they can handle any number of routers.
18431 - Fix a superficial "Duplicate mark for close" bug.
18432 - Stop checking for clock skew for OR connections, even for servers.
18433 - Fix a fencepost error that was chopping off the last letter of any
18434 nickname that is the maximum allowed nickname length.
18435 - Update URLs in log messages so they point to the new website.
18436 - Fix a potential problem in mangling server private keys while
18437 writing to disk (not triggered yet, as far as we know).
18438 - Include the licenses for other free software we include in Tor,
18439 now that we're shipping binary distributions more regularly.
18442 Changes in version 0.0.9.1 - 2004-12-15
18443 o Bugfixes on 0.0.9:
18444 - Make hibernation actually work.
18445 - Make HashedControlPassword config option work.
18446 - When we're reporting event circuit status to a controller,
18447 don't use the stream status code.
18450 Changes in version 0.0.9 - 2004-12-12
18451 o Bugfixes on 0.0.8.1 (Crashes and asserts):
18452 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
18453 write() call will fail and we handle it there.
18454 - When we run out of disk space, or other log writing error, don't
18455 crash. Just stop logging to that log and continue.
18456 - Fix isspace() and friends so they still make Solaris happy
18457 but also so they don't trigger asserts on win32.
18458 - Fix assert failure on malformed socks4a requests.
18459 - Fix an assert bug where a hidden service provider would fail if
18460 the first hop of his rendezvous circuit was down.
18461 - Better handling of size_t vs int, so we're more robust on 64
18464 o Bugfixes on 0.0.8.1 (Win32):
18465 - Make windows sockets actually non-blocking (oops), and handle
18466 win32 socket errors better.
18467 - Fix parse_iso_time on platforms without strptime (eg win32).
18468 - win32: when being multithreaded, leave parent fdarray open.
18469 - Better handling of winsock includes on non-MSV win32 compilers.
18470 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
18472 - Make unit tests work on win32.
18474 o Bugfixes on 0.0.8.1 (Path selection and streams):
18475 - Calculate timeout for waiting for a connected cell from the time
18476 we sent the begin cell, not from the time the stream started. If
18477 it took a long time to establish the circuit, we would time out
18478 right after sending the begin cell.
18479 - Fix router_compare_addr_to_addr_policy: it was not treating a port
18480 of * as always matching, so we were picking reject *:* nodes as
18481 exit nodes too. Oops.
18482 - When read() failed on a stream, we would close it without sending
18483 back an end. So 'connection refused' would simply be ignored and
18484 the user would get no response.
18485 - Stop a sigpipe: when an 'end' cell races with eof from the app,
18486 we shouldn't hold-open-until-flush if the eof arrived first.
18487 - Let resolve conns retry/expire also, rather than sticking around
18489 - Fix more dns related bugs: send back resolve_failed and end cells
18490 more reliably when the resolve fails, rather than closing the
18491 circuit and then trying to send the cell. Also attach dummy resolve
18492 connections to a circuit *before* calling dns_resolve(), to fix
18493 a bug where cached answers would never be sent in RESOLVED cells.
18495 o Bugfixes on 0.0.8.1 (Circuits):
18496 - Finally fix a bug that's been plaguing us for a year:
18497 With high load, circuit package window was reaching 0. Whenever
18498 we got a circuit-level sendme, we were reading a lot on each
18499 socket, but only writing out a bit. So we would eventually reach
18500 eof. This would be noticed and acted on even when there were still
18501 bytes sitting in the inbuf.
18502 - Use identity comparison, not nickname comparison, to choose which
18503 half of circuit-ID-space each side gets to use. This is needed
18504 because sometimes we think of a router as a nickname, and sometimes
18505 as a hex ID, and we can't predict what the other side will do.
18507 o Bugfixes on 0.0.8.1 (Other):
18508 - Fix a whole slew of memory leaks.
18509 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
18510 - If we are using select, make sure we stay within FD_SETSIZE.
18511 - When poll() is interrupted, we shouldn't believe the revents values.
18512 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
18513 and smartlist_len, which are two major profiling offenders.
18514 - If do_hup fails, actually notice.
18515 - Flush the log file descriptor after we print "Tor opening log file",
18516 so we don't see those messages days later.
18517 - Hidden service operators now correctly handle version 1 style
18518 INTRODUCE1 cells (nobody generates them still, so not a critical
18520 - Handle more errnos from accept() without closing the listener.
18521 Some OpenBSD machines were closing their listeners because
18522 they ran out of file descriptors.
18523 - Some people had wrapped their tor client/server in a script
18524 that would restart it whenever it died. This did not play well
18525 with our "shut down if your version is obsolete" code. Now people
18526 don't fetch a new directory if their local cached version is
18528 - Make our autogen.sh work on ksh as well as bash.
18529 - Better torrc example lines for dirbindaddress and orbindaddress.
18530 - Improved bounds checking on parsed ints (e.g. config options and
18531 the ones we find in directories.)
18532 - Stop using separate defaults for no-config-file and
18533 empty-config-file. Now you have to explicitly turn off SocksPort,
18534 if you don't want it open.
18535 - We were starting to daemonize before we opened our logs, so if
18536 there were any problems opening logs, we would complain to stderr,
18537 which wouldn't work, and then mysteriously exit.
18538 - If a verified OR connects to us before he's uploaded his descriptor,
18539 or we verify him and hup but he still has the original TLS
18540 connection, then conn->nickname is still set like he's unverified.
18542 o Code security improvements, inspired by Ilja:
18543 - tor_snprintf wrapper over snprintf with consistent (though not C99)
18545 - Replace sprintf with tor_snprintf. (I think they were all safe, but
18547 - Replace strcpy/strncpy with strlcpy in more places.
18548 - Avoid strcat; use tor_snprintf or strlcat instead.
18550 o Features (circuits and streams):
18551 - New circuit building strategy: keep a list of ports that we've
18552 used in the past 6 hours, and always try to have 2 circuits open
18553 or on the way that will handle each such port. Seed us with port
18554 80 so web users won't complain that Tor is "slow to start up".
18555 - Make kill -USR1 dump more useful stats about circuits.
18556 - When warning about retrying or giving up, print the address, so
18557 the user knows which one it's talking about.
18558 - If you haven't used a clean circuit in an hour, throw it away,
18559 just to be on the safe side. (This means after 6 hours a totally
18560 unused Tor client will have no circuits open.)
18561 - Support "foo.nickname.exit" addresses, to let Alice request the
18562 address "foo" as viewed by exit node "nickname". Based on a patch
18563 from Geoff Goodell.
18564 - If your requested entry or exit node has advertised bandwidth 0,
18566 - Be more greedy about filling up relay cells -- we try reading again
18567 once we've processed the stuff we read, in case enough has arrived
18568 to fill the last cell completely.
18569 - Refuse application socks connections to port 0.
18570 - Use only 0.0.9pre1 and later servers for resolve cells.
18572 o Features (bandwidth):
18573 - Hibernation: New config option "AccountingMax" lets you
18574 set how many bytes per month (in each direction) you want to
18575 allow your server to consume. Rather than spreading those
18576 bytes out evenly over the month, we instead hibernate for some
18577 of the month and pop up at a deterministic time, work until
18578 the bytes are consumed, then hibernate again. Config option
18579 "MonthlyAccountingStart" lets you specify which day of the month
18580 your billing cycle starts on.
18581 - Implement weekly/monthly/daily accounting: now you specify your
18582 hibernation properties by
18583 AccountingMax N bytes|KB|MB|GB|TB
18584 AccountingStart day|week|month [day] HH:MM
18585 Defaults to "month 1 0:00".
18586 - Let bandwidth and interval config options be specified as 5 bytes,
18587 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
18589 o Features (directories):
18590 - New "router-status" line in directory, to better bind each verified
18591 nickname to its identity key.
18592 - Clients can ask dirservers for /dir.z to get a compressed version
18593 of the directory. Only works for servers running 0.0.9, of course.
18594 - Make clients cache directories and use them to seed their router
18595 lists at startup. This means clients have a datadir again.
18596 - Respond to content-encoding headers by trying to uncompress as
18598 - Clients and servers now fetch running-routers; cache
18599 running-routers; compress running-routers; serve compressed
18601 - Make moria2 advertise a dirport of 80, so people behind firewalls
18602 will be able to get a directory.
18603 - Http proxy support
18604 - Dirservers translate requests for http://%s:%d/x to /x
18605 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
18606 be routed through this host.
18607 - Clients ask for /tor/x rather than /x for new enough dirservers.
18608 This way we can one day coexist peacefully with apache.
18609 - Clients specify a "Host: %s%d" http header, to be compatible
18610 with more proxies, and so running squid on an exit node can work.
18611 - Protect dirservers from overzealous descriptor uploading -- wait
18612 10 seconds after directory gets dirty, before regenerating.
18614 o Features (packages and install):
18615 - Add NSI installer contributed by J Doe.
18616 - Apply NT service patch from Osamu Fujino. Still needs more work.
18617 - Commit VC6 and VC7 workspace/project files.
18618 - Commit a tor.spec for making RPM files, with help from jbash.
18619 - Add contrib/torctl.in contributed by Glenn Fink.
18620 - Make expand_filename handle ~ and ~username.
18621 - Use autoconf to enable largefile support where necessary. Use
18622 ftello where available, since ftell can fail at 2GB.
18623 - Ship src/win32/ in the tarball, so people can use it to build.
18624 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
18627 o Features (ui controller):
18628 - Control interface: a separate program can now talk to your
18629 client/server over a socket, and get/set config options, receive
18630 notifications of circuits and streams starting/finishing/dying,
18631 bandwidth used, etc. The next step is to get some GUIs working.
18632 Let us know if you want to help out. See doc/control-spec.txt .
18633 - Ship a contrib/tor-control.py as an example script to interact
18634 with the control port.
18635 - "tor --hash-password zzyxz" will output a salted password for
18636 use in authenticating to the control interface.
18637 - Implement the control-spec's SAVECONF command, to write your
18638 configuration to torrc.
18639 - Get cookie authentication for the controller closer to working.
18640 - When set_conf changes our server descriptor, upload a new copy.
18641 But don't upload it too often if there are frequent changes.
18643 o Features (config and command-line):
18644 - Deprecate unofficial config option abbreviations, and abbreviations
18645 not on the command line.
18646 - Configuration infrastructure support for warning on obsolete
18648 - Give a slightly more useful output for "tor -h".
18649 - Break DirFetchPostPeriod into:
18650 - DirFetchPeriod for fetching full directory,
18651 - StatusFetchPeriod for fetching running-routers,
18652 - DirPostPeriod for posting server descriptor,
18653 - RendPostPeriod for posting hidden service descriptors.
18654 - New log format in config:
18655 "Log minsev[-maxsev] stdout|stderr|syslog" or
18656 "Log minsev[-maxsev] file /var/foo"
18657 - DirPolicy config option, to let people reject incoming addresses
18658 from their dirserver.
18659 - "tor --list-fingerprint" will list your identity key fingerprint
18661 - Make tor --version --version dump the cvs Id of every file.
18662 - New 'MyFamily nick1,...' config option for a server to
18663 specify other servers that shouldn't be used in the same circuit
18664 with it. Only believed if nick1 also specifies us.
18665 - New 'NodeFamily nick1,nick2,...' config option for a client to
18666 specify nodes that it doesn't want to use in the same circuit.
18667 - New 'Redirectexit pattern address:port' config option for a
18668 server to redirect exit connections, e.g. to a local squid.
18669 - Add "pass" target for RedirectExit, to make it easier to break
18670 out of a sequence of RedirectExit rules.
18671 - Make the dirservers file obsolete.
18672 - Include a dir-signing-key token in directories to tell the
18673 parsing entity which key is being used to sign.
18674 - Remove the built-in bulky default dirservers string.
18675 - New config option "Dirserver %s:%d [fingerprint]", which can be
18676 repeated as many times as needed. If no dirservers specified,
18677 default to moria1,moria2,tor26.
18678 - Make 'Routerfile' config option obsolete.
18679 - Discourage people from setting their dirfetchpostperiod more often
18680 than once per minute.
18682 o Features (other):
18683 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
18684 get back to normal.)
18685 - Accept *:706 (silc) in default exit policy.
18686 - Implement new versioning format for post 0.1.
18687 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
18688 log more informatively.
18689 - Check clock skew for verified servers, but allow unverified
18690 servers and clients to have any clock skew.
18691 - Make sure the hidden service descriptors are at a random offset
18692 from each other, to hinder linkability.
18693 - Clients now generate a TLS cert too, in preparation for having
18694 them act more like real nodes.
18695 - Add a pure-C tor-resolve implementation.
18696 - Use getrlimit and friends to ensure we can reach MaxConn (currently
18697 1024) file descriptors.
18698 - Raise the max dns workers from 50 to 100.
18701 Changes in version 0.0.8.1 - 2004-10-13
18703 - Fix a seg fault that can be triggered remotely for Tor
18704 clients/servers with an open dirport.
18705 - Fix a rare assert trigger, where routerinfos for entries in
18706 our cpath would expire while we're building the path.
18707 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18708 - Fix a rare seg fault for people running hidden services on
18709 intermittent connections.
18710 - Fix a bug in parsing opt keywords with objects.
18711 - Fix a stale pointer assert bug when a stream detaches and
18713 - Fix a string format vulnerability (probably not exploitable)
18714 in reporting stats locally.
18715 - Fix an assert trigger: sometimes launching circuits can fail
18716 immediately, e.g. because too many circuits have failed recently.
18717 - Fix a compile warning on 64 bit platforms.
18720 Changes in version 0.0.8 - 2004-08-25
18722 - Made our unit tests compile again on OpenBSD 3.5, and tor
18723 itself compile again on OpenBSD on a sparc64.
18724 - We were neglecting milliseconds when logging on win32, so
18725 everything appeared to happen at the beginning of each second.
18726 - Check directory signature _before_ you decide whether you're
18727 you're running an obsolete version and should exit.
18728 - Check directory signature _before_ you parse the running-routers
18729 list to decide who's running.
18730 - Check return value of fclose while writing to disk, so we don't
18731 end up with broken files when servers run out of disk space.
18732 - Port it to SunOS 5.9 / Athena
18733 - Fix two bugs in saving onion keys to disk when rotating, so
18734 hopefully we'll get fewer people using old onion keys.
18735 - Remove our mostly unused -- and broken -- hex_encode()
18736 function. Use base16_encode() instead. (Thanks to Timo Lindfors
18737 for pointing out this bug.)
18738 - Only pick and establish intro points after we've gotten a
18740 - Fix assert triggers: if the other side returns an address 0.0.0.0,
18741 don't put it into the client dns cache.
18742 - If a begin failed due to exit policy, but we believe the IP
18743 address should have been allowed, switch that router to exitpolicy
18744 reject *:* until we get our next directory.
18746 o Protocol changes:
18747 - 'Extend' relay cell payloads now include the digest of the
18748 intended next hop's identity key. Now we can verify that we're
18749 extending to the right router, and also extend to routers we
18750 hadn't heard of before.
18753 - Tor nodes can now act as relays (with an advertised ORPort)
18754 without being manually verified by the dirserver operators.
18755 - Uploaded descriptors of unverified routers are now accepted
18756 by the dirservers, and included in the directory.
18757 - Verified routers are listed by nickname in the running-routers
18758 list; unverified routers are listed as "$<fingerprint>".
18759 - We now use hash-of-identity-key in most places rather than
18760 nickname or addr:port, for improved security/flexibility.
18761 - AllowUnverifiedNodes config option to let circuits choose no-name
18762 routers in entry,middle,exit,introduction,rendezvous positions.
18763 Allow middle and rendezvous positions by default.
18764 - When picking unverified routers, skip those with low uptime and/or
18765 low bandwidth, depending on what properties you care about.
18766 - ClientOnly option for nodes that never want to become servers.
18767 - Directory caching.
18768 - "AuthoritativeDir 1" option for the official dirservers.
18769 - Now other nodes (clients and servers) will cache the latest
18770 directory they've pulled down.
18771 - They can enable their DirPort to serve it to others.
18772 - Clients will pull down a directory from any node with an open
18773 DirPort, and check the signature/timestamp correctly.
18774 - Authoritative dirservers now fetch directories from other
18775 authdirservers, to stay better synced.
18776 - Running-routers list tells who's down also, along with noting
18777 if they're verified (listed by nickname) or unverified (listed
18779 - Allow dirservers to serve running-router list separately.
18780 This isn't used yet.
18781 - You can now fetch $DIRURL/running-routers to get just the
18782 running-routers line, not the whole descriptor list. (But
18783 clients don't use this yet.)
18784 - Clients choose nodes proportional to advertised bandwidth.
18785 - Clients avoid using nodes with low uptime as introduction points.
18786 - Handle servers with dynamic IP addresses: don't just replace
18787 options->Address with the resolved one at startup, and
18788 detect our address right before we make a routerinfo each time.
18789 - 'FascistFirewall' option to pick dirservers and ORs on specific
18790 ports; plus 'FirewallPorts' config option to tell FascistFirewall
18791 which ports are open. (Defaults to 80,443)
18792 - Try other dirservers immediately if the one you try is down. This
18793 should tolerate down dirservers better now.
18794 - ORs connect-on-demand to other ORs
18795 - If you get an extend cell to an OR you're not connected to,
18796 connect, handshake, and forward the create cell.
18797 - The authoritative dirservers stay connected to everybody,
18798 and everybody stays connected to 0.0.7 servers, but otherwise
18799 clients/servers expire unused connections after 5 minutes.
18800 - When servers get a sigint, they delay 30 seconds (refusing new
18801 connections) then exit. A second sigint causes immediate exit.
18802 - File and name management:
18803 - Look for .torrc if no CONFDIR "torrc" is found.
18804 - If no datadir is defined, then choose, make, and secure ~/.tor
18806 - If torrc not found, exitpolicy reject *:*.
18807 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
18808 - If no nickname is defined, derive default from hostname.
18809 - Rename secret key files, e.g. identity.key -> secret_id_key,
18810 to discourage people from mailing their identity key to tor-ops.
18811 - Refuse to build a circuit before the directory has arrived --
18812 it won't work anyway, since you won't know the right onion keys
18814 - Parse tor version numbers so we can do an is-newer-than check
18815 rather than an is-in-the-list check.
18816 - New socks command 'resolve', to let us shim gethostbyname()
18818 - A 'tor_resolve' script to access the socks resolve functionality.
18819 - A new socks-extensions.txt doc file to describe our
18820 interpretation and extensions to the socks protocols.
18821 - Add a ContactInfo option, which gets published in descriptor.
18822 - Write tor version at the top of each log file
18823 - New docs in the tarball:
18825 - Document that you should proxy your SSL traffic too.
18826 - Log a warning if the user uses an unsafe socks variant, so people
18827 are more likely to learn about privoxy or socat.
18828 - Log a warning if you're running an unverified server, to let you
18829 know you might want to get it verified.
18830 - Change the default exit policy to reject the default edonkey,
18831 kazaa, gnutella ports.
18832 - Add replace_file() to util.[ch] to handle win32's rename().
18833 - Publish OR uptime in descriptor (and thus in directory) too.
18834 - Remember used bandwidth (both in and out), and publish 15-minute
18835 snapshots for the past day into our descriptor.
18836 - Be more aggressive about trying to make circuits when the network
18837 has changed (e.g. when you unsuspend your laptop).
18838 - Check for time skew on http headers; report date in response to
18840 - If the entrynode config line has only one node, don't pick it as
18842 - Add strict{entry|exit}nodes config options. If set to 1, then
18843 we refuse to build circuits that don't include the specified entry
18845 - OutboundBindAddress config option, to bind to a specific
18846 IP address for outgoing connect()s.
18847 - End truncated log entries (e.g. directories) with "[truncated]".
18850 Changes in version 0.0.7.3 - 2004-08-12
18851 o Stop dnsworkers from triggering an assert failure when you
18852 ask them to resolve the host "".
18855 Changes in version 0.0.7.2 - 2004-07-07
18856 o A better fix for the 0.0.0.0 problem, that will hopefully
18857 eliminate the remaining related assertion failures.
18860 Changes in version 0.0.7.1 - 2004-07-04
18861 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
18862 since internally we use 0.0.0.0 to signify "not yet resolved".
18865 Changes in version 0.0.7 - 2004-06-07
18866 o Fixes for crashes and other obnoxious bugs:
18867 - Fix an epipe bug: sometimes when directory connections failed
18868 to connect, we would give them a chance to flush before closing
18870 - When we detached from a circuit because of resolvefailed, we
18871 would immediately try the same circuit twice more, and then
18872 give up on the resolve thinking we'd tried three different
18874 - Limit the number of intro circuits we'll attempt to build for a
18875 hidden service per 15-minute period.
18876 - Check recommended-software string *early*, before actually parsing
18877 the directory. Thus we can detect an obsolete version and exit,
18878 even if the new directory format doesn't parse.
18879 o Fixes for security bugs:
18880 - Remember which nodes are dirservers when you startup, and if a
18881 random OR enables his dirport, don't automatically assume he's
18882 a trusted dirserver.
18884 - Directory connections were asking the wrong poll socket to
18885 start writing, and not asking themselves to start writing.
18886 - When we detached from a circuit because we sent a begin but
18887 didn't get a connected, we would use it again the first time;
18888 but after that we would correctly switch to a different one.
18889 - Stop warning when the first onion decrypt attempt fails; they
18890 will sometimes legitimately fail now that we rotate keys.
18891 - Override unaligned-access-ok check when $host_cpu is ia64 or
18892 arm. Apparently they allow it but the kernel whines.
18893 - Dirservers try to reconnect periodically too, in case connections
18895 - Fix some memory leaks in directory servers.
18896 - Allow backslash in Win32 filenames.
18897 - Made Tor build complain-free on FreeBSD, hopefully without
18898 breaking other BSD builds. We'll see.
18899 - Check directory signatures based on name of signer, not on whom
18900 we got the directory from. This will let us cache directories more
18902 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
18905 - Doxygen markup on all functions and global variables.
18906 - Make directory functions update routerlist, not replace it. So
18907 now directory disagreements are not so critical a problem.
18908 - Remove the upper limit on number of descriptors in a dirserver's
18909 directory (not that we were anywhere close).
18910 - Allow multiple logfiles at different severity ranges.
18911 - Allow *BindAddress to specify ":port" rather than setting *Port
18912 separately. Allow multiple instances of each BindAddress config
18913 option, so you can bind to multiple interfaces if you want.
18914 - Allow multiple exit policy lines, which are processed in order.
18915 Now we don't need that huge line with all the commas in it.
18916 - Enable accept/reject policies on SOCKS connections, so you can bind
18917 to 0.0.0.0 but still control who can use your OP.
18918 - Updated the man page to reflect these features.
18921 Changes in version 0.0.6.2 - 2004-05-16
18922 o Our integrity-checking digest was checking only the most recent cell,
18923 not the previous cells like we'd thought.
18924 Thanks to Stefan Mark for finding the flaw!
18927 Changes in version 0.0.6.1 - 2004-05-06
18928 o Fix two bugs in our AES counter-mode implementation (this affected
18929 onion-level stream encryption, but not TLS-level). It turns
18930 out we were doing something much more akin to a 16-character
18931 polyalphabetic cipher. Oops.
18932 Thanks to Stefan Mark for finding the flaw!
18933 o Retire moria3 as a directory server, and add tor26 as a directory
18937 Changes in version 0.0.6 - 2004-05-02
18939 - Hidden services and rendezvous points are implemented. Go to
18940 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
18941 hidden services. (This only works via a socks4a proxy such as
18942 Privoxy, and currently it's quite slow.)
18943 - We now rotate link (tls context) keys and onion keys.
18944 - CREATE cells now include oaep padding, so you can tell
18945 if you decrypted them correctly.
18946 - Retry stream correctly when we fail to connect because of
18947 exit-policy-reject (should try another) or can't-resolve-address.
18948 - When we hup a dirserver and we've *removed* a server from the
18949 approved-routers list, now we remove that server from the
18950 in-memory directories too.
18951 - Add bandwidthburst to server descriptor.
18952 - Directories now say which dirserver signed them.
18953 - Use a tor_assert macro that logs failed assertions too.
18954 - Since we don't support truncateds much, don't bother sending them;
18955 just close the circ.
18956 - Fetch randomness from /dev/urandom better (not via fopen/fread)
18957 - Better debugging for tls errors
18958 - Set Content-Type on the directory and hidserv descriptor.
18959 - Remove IVs from cipher code, since AES-ctr has none.
18961 - Fix an assert trigger for exit nodes that's been plaguing us since
18962 the days of 0.0.2prexx (thanks weasel!)
18963 - Fix a bug where we were closing tls connections intermittently.
18964 It turns out openssl keeps its errors around -- so if an error
18965 happens, and you don't ask about it, and then another openssl
18966 operation happens and succeeds, and you ask if there was an error,
18967 it tells you about the first error.
18968 - Fix a bug that's been lurking since 27 may 03 (!)
18969 When passing back a destroy cell, we would use the wrong circ id.
18970 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
18971 - Some versions of openssl have an SSL_pending function that erroneously
18972 returns bytes when there is a non-application record pending.
18973 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
18974 o We were using an array of length zero in a few places.
18975 o Win32's gethostbyname can't resolve an IP to an IP.
18976 o Win32's close can't close a socket.
18977 o Handle windows socket errors correctly.
18979 - check for <sys/limits.h> so we build on FreeBSD again, and
18980 <machine/limits.h> for NetBSD.
18983 Changes in version 0.0.5 - 2004-03-30
18984 o Install torrc as torrc.sample -- we no longer clobber your
18986 o Fix mangled-state bug in directory fetching (was causing sigpipes).
18987 o Only build circuits after we've fetched the directory: clients were
18988 using only the directory servers before they'd fetched a directory.
18989 This also means longer startup time; so it goes.
18990 o Fix an assert trigger where an OP would fail to handshake, and we'd
18991 expect it to have a nickname.
18992 o Work around a tsocks bug: do a socks reject when AP connection dies
18993 early, else tsocks goes into an infinite loop.
18994 o Hold socks connection open until reply is flushed (if possible)
18995 o Make exit nodes resolve IPs to IPs immediately, rather than asking
18996 the dns farm to do it.
18997 o Fix c99 aliasing warnings in rephist.c
18998 o Don't include server descriptors that are older than 24 hours in the
19000 o Give socks 'reject' replies their whole 15s to attempt to flush,
19001 rather than seeing the 60s timeout and assuming the flush had failed.
19002 o Clean automake droppings from the cvs repository
19003 o Add in a 'notice' log level for things the operator should hear
19004 but that aren't warnings
19007 Changes in version 0.0.4 - 2004-03-26
19008 o When connecting to a dirserver or OR and the network is down,
19012 Changes in version 0.0.3 - 2004-03-26
19013 o Warn and fail if server chose a nickname with illegal characters
19014 o Port to Solaris and Sparc:
19015 - include missing header fcntl.h
19016 - have autoconf find -lsocket -lnsl automatically
19017 - deal with hardware word alignment
19018 - make uname() work (solaris has a different return convention)
19019 - switch from using signal() to sigaction()
19020 o Preliminary work on reputation system:
19021 - Keep statistics on success/fail of connect attempts; they're published
19022 by kill -USR1 currently.
19023 - Add a RunTesting option to try to learn link state by creating test
19024 circuits, even when SocksPort is off.
19025 - Remove unused open circuits when there are too many.
19028 Changes in version 0.0.2 - 2004-03-19
19029 - Include strlcpy and strlcat for safer string ops
19030 - define INADDR_NONE so we compile (but still not run) on solaris
19033 Changes in version 0.0.2pre27 - 2004-03-14
19035 - Allow internal tor networks (we were rejecting internal IPs,
19036 now we allow them if they're set explicitly).
19037 - And fix a few endian issues.
19040 Changes in version 0.0.2pre26 - 2004-03-14
19042 - If a stream times out after 15s without a connected cell, don't
19043 try that circuit again: try a new one.
19044 - Retry streams at most 4 times. Then give up.
19045 - When a dirserver gets a descriptor from an unknown router, it
19046 logs its fingerprint (so the dirserver operator can choose to
19047 accept it even without mail from the server operator).
19048 - Inform unapproved servers when we reject their descriptors.
19049 - Make tor build on Windows again. It works as a client, who knows
19051 - Clearer instructions in the torrc for how to set up a server.
19052 - Be more efficient about reading fd's when our global token bucket
19053 (used for rate limiting) becomes empty.
19055 - Stop asserting that computers always go forward in time. It's
19057 - When we sent a cell (e.g. destroy) and then marked an OR connection
19058 expired, we might close it before finishing a flush if the other
19059 side isn't reading right then.
19060 - Don't allow dirservers to start if they haven't defined
19061 RecommendedVersions
19062 - We were caching transient dns failures. Oops.
19063 - Prevent servers from publishing an internal IP as their address.
19064 - Address a strcat vulnerability in circuit.c
19067 Changes in version 0.0.2pre25 - 2004-03-04
19069 - Put the OR's IP in its router descriptor, not its fqdn. That way
19070 we'll stop being stalled by gethostbyname for nodes with flaky dns,
19073 - If the user typed in an address that didn't resolve, the server
19077 Changes in version 0.0.2pre24 - 2004-03-03
19079 - Fix an assertion failure in dns.c, where we were trying to dequeue
19080 a pending dns resolve even if it wasn't pending
19081 - Fix a spurious socks5 warning about still trying to write after the
19082 connection is finished.
19083 - Hold certain marked_for_close connections open until they're finished
19084 flushing, rather than losing bytes by closing them too early.
19085 - Correctly report the reason for ending a stream
19086 - Remove some duplicate calls to connection_mark_for_close
19087 - Put switch_id and start_daemon earlier in the boot sequence, so it
19088 will actually try to chdir() to options.DataDirectory
19089 - Make 'make test' exit(1) if a test fails; fix some unit tests
19090 - Make tor fail when you use a config option it doesn't know about,
19091 rather than warn and continue.
19092 - Make --version work
19093 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
19096 Changes in version 0.0.2pre23 - 2004-02-29
19098 - Print a statement when the first circ is finished, so the user
19099 knows it's working.
19100 - If a relay cell is unrecognized at the end of the circuit,
19101 send back a destroy. (So attacks to mutate cells are more
19103 - New config option 'excludenodes' to avoid certain nodes for circuits.
19104 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
19105 so you can collect coredumps there.
19107 - Fix a bug in tls flushing where sometimes data got wedged and
19108 didn't flush until more data got sent. Hopefully this bug was
19109 a big factor in the random delays we were seeing.
19110 - Make 'connected' cells include the resolved IP, so the client
19111 dns cache actually gets populated.
19112 - Disallow changing from ORPort=0 to ORPort>0 on hup.
19113 - When we time-out on a stream and detach from the circuit, send an
19114 end cell down it first.
19115 - Only warn about an unknown router (in exitnodes, entrynodes,
19116 excludenodes) after we've fetched a directory.
19119 Changes in version 0.0.2pre22 - 2004-02-26
19121 - Servers publish less revealing uname information in descriptors.
19122 - More memory tracking and assertions, to crash more usefully when
19124 - If the default torrc isn't there, just use some default defaults.
19125 Plus provide an internal dirservers file if they don't have one.
19126 - When the user tries to use Tor as an http proxy, give them an http
19127 501 failure explaining that we're a socks proxy.
19128 - Dump a new router.desc on hup, to help confused people who change
19129 their exit policies and then wonder why router.desc doesn't reflect
19131 - Clean up the generic tor.sh init script that we ship with.
19133 - If the exit stream is pending on the resolve, and a destroy arrives,
19134 then the stream wasn't getting removed from the pending list. I
19135 think this was the one causing recent server crashes.
19136 - Use a more robust poll on OSX 10.3, since their poll is flaky.
19137 - When it couldn't resolve any dirservers, it was useless from then on.
19138 Now it reloads the RouterFile (or default dirservers) if it has no
19140 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
19141 many users don't even *have* a /usr/local/sbin/.
19144 Changes in version 0.0.2pre21 - 2004-02-18
19146 - There's a ChangeLog file that actually reflects the changelog.
19147 - There's a 'torify' wrapper script, with an accompanying
19148 tor-tsocks.conf, that simplifies the process of using tsocks for
19149 tor. It even has a man page.
19150 - The tor binary gets installed to sbin rather than bin now.
19151 - Retry streams where the connected cell hasn't arrived in 15 seconds
19152 - Clean up exit policy handling -- get the default out of the torrc,
19153 so we can update it without forcing each server operator to fix
19155 - Allow imaps and pop3s in default exit policy
19157 - Prevent picking middleman nodes as the last node in the circuit
19160 Changes in version 0.0.2pre20 - 2004-01-30
19162 - We now have a deb package, and it's in debian unstable. Go to
19163 it, apt-getters. :)
19164 - I've split the TotalBandwidth option into BandwidthRate (how many
19165 bytes per second you want to allow, long-term) and
19166 BandwidthBurst (how many bytes you will allow at once before the cap
19167 kicks in). This better token bucket approach lets you, say, set
19168 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
19169 performance while not exceeding your monthly bandwidth quota.
19170 - Push out a tls record's worth of data once you've got it, rather
19171 than waiting until you've read everything waiting to be read. This
19172 may improve performance by pipelining better. We'll see.
19173 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
19174 from failed circuits (if they haven't been connected yet) and attach
19176 - Expire old streams that haven't managed to connect. Some day we'll
19177 have them reattach to new circuits instead.
19180 - Fix several memory leaks that were causing servers to become bloated
19182 - Fix a few very rare assert triggers. A few more remain.
19183 - Setuid to User _before_ complaining about running as root.
19186 Changes in version 0.0.2pre19 - 2004-01-07
19188 - Fix deadlock condition in dns farm. We were telling a child to die by
19189 closing the parent's file descriptor to him. But newer children were
19190 inheriting the open file descriptor from the parent, and since they
19191 weren't closing it, the socket never closed, so the child never read
19192 eof, so he never knew to exit. Similarly, dns workers were holding
19193 open other sockets, leading to all sorts of chaos.
19194 - New cleaner daemon() code for forking and backgrounding.
19195 - If you log to a file, it now prints an entry at the top of the
19196 logfile so you know it's working.
19197 - The onionskin challenge length was 30 bytes longer than necessary.
19198 - Started to patch up the spec so it's not quite so out of date.
19201 Changes in version 0.0.2pre18 - 2004-01-02
19203 - Fix endian issues with the 'integrity' field in the relay header.
19204 - Fix a potential bug where connections in state
19205 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
19208 Changes in version 0.0.2pre17 - 2003-12-30
19210 - Made --debuglogfile (or any second log file, actually) work.
19211 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
19212 adversary could force us into an infinite loop.
19215 - Each onionskin handshake now includes a hash of the computed key,
19216 to prove the server's identity and help perfect forward secrecy.
19217 - Changed cell size from 256 to 512 bytes (working toward compatibility
19219 - Changed cell length to 2 bytes, and moved it to the relay header.
19220 - Implemented end-to-end integrity checking for the payloads of
19222 - Separated streamid from 'recognized' (otherwise circuits will get
19223 messed up when we try to have streams exit from the middle). We
19224 use the integrity-checking to confirm that a cell is addressed to
19226 - Randomize the initial circid and streamid values, so an adversary who
19227 breaks into a node can't learn how many circuits or streams have
19231 Changes in version 0.0.2pre16 - 2003-12-14
19233 - Fixed a bug that made HUP trigger an assert
19234 - Fixed a bug where a circuit that immediately failed wasn't being
19235 counted as a failed circuit in counting retries.
19238 - Now we close the circuit when we get a truncated cell: otherwise we're
19239 open to an anonymity attack where a bad node in the path truncates
19240 the circuit and then we open streams at him.
19241 - Add port ranges to exit policies
19242 - Add a conservative default exit policy
19243 - Warn if you're running tor as root
19244 - on HUP, retry OR connections and close/rebind listeners
19245 - options.EntryNodes: try these nodes first when picking the first node
19246 - options.ExitNodes: if your best choices happen to include any of
19247 your preferred exit nodes, you choose among just those preferred
19249 - options.ExcludedNodes: nodes that are never picked in path building
19252 Changes in version 0.0.2pre15 - 2003-12-03
19253 o Robustness and bugfixes:
19254 - Sometimes clients would cache incorrect DNS resolves, which would
19255 really screw things up.
19256 - An OP that goes offline would slowly leak all its sockets and stop
19258 - A wide variety of bugfixes in exit node selection, exit policy
19259 handling, and processing pending streams when a new circuit is
19261 - Pick nodes for a path only from those the directory says are up
19262 - Choose randomly from all running dirservers, not always the first one
19263 - Increase allowed http header size for directory fetch.
19264 - Stop writing to stderr (if we're daemonized it will be closed).
19265 - Enable -g always, so cores will be more useful to me.
19266 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
19269 - Wrote a man page. It lists commonly used options.
19272 - Change default loglevel to warn.
19273 - Make PidFile default to null rather than littering in your CWD.
19274 - OnionRouter config option is now obsolete. Instead it just checks
19276 - Moved to a single unified torrc file for both clients and servers.
19279 Changes in version 0.0.2pre14 - 2003-11-29
19280 o Robustness and bugfixes:
19281 - Force the admin to make the DataDirectory himself
19282 - to get ownership/permissions right
19283 - so clients no longer make a DataDirectory and then never use it
19284 - fix bug where a client who was offline for 45 minutes would never
19285 pull down a directory again
19286 - fix (or at least hide really well) the dns assert bug that was
19287 causing server crashes
19288 - warnings and improved robustness wrt clockskew for certs
19289 - use the native daemon(3) to daemonize, when available
19290 - exit if bind() fails
19291 - exit if neither socksport nor orport is defined
19292 - include our own tor_timegm (Win32 doesn't have its own)
19293 - bugfix for win32 with lots of connections
19294 - fix minor bias in PRNG
19295 - make dirserver more robust to corrupt cached directory
19298 - Wrote the design document (woo)
19300 o Circuit building and exit policies:
19301 - Circuits no longer try to use nodes that the directory has told them
19303 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
19304 bitcounts (18.0.0.0/8).
19305 - Make AP connections standby for a circuit if no suitable circuit
19306 exists, rather than failing
19307 - Circuits choose exit node based on addr/port, exit policies, and
19308 which AP connections are standing by
19309 - Bump min pathlen from 2 to 3
19310 - Relay end cells have a payload to describe why the stream ended.
19311 - If the stream failed because of exit policy, try again with a new
19313 - Clients have a dns cache to remember resolved addresses.
19314 - Notice more quickly when we have no working circuits
19317 - APPort is now called SocksPort
19318 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
19320 - RecommendedVersions is now a config variable rather than
19321 hardcoded (for dirservers)
19322 - Reloads config on HUP
19323 - Usage info on -h or --help
19324 - If you set User and Group config vars, it'll setu/gid to them.
19326 Changes in version 0.0.2pre13 - 2003-10-19
19327 o General stability:
19328 - SSL_write no longer fails when it returns WANTWRITE and the number
19329 of bytes in the buf has changed by the next SSL_write call.
19330 - Fix segfault fetching directory when network is down
19331 - Fix a variety of minor memory leaks
19332 - Dirservers reload the fingerprints file on HUP, so I don't have
19333 to take down the network when I approve a new router
19334 - Default server config file has explicit Address line to specify fqdn
19337 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
19338 - Make listener connections not ever alloc bufs
19340 o Autoconf improvements:
19341 - don't clobber an external CFLAGS in ./configure
19342 - Make install now works
19343 - create var/lib/tor on make install
19344 - autocreate a tor.sh initscript to help distribs
19345 - autocreate the torrc and sample-server-torrc with correct paths
19347 o Log files and Daemonizing now work:
19348 - If --DebugLogFile is specified, log to it at -l debug
19349 - If --LogFile is specified, use it instead of commandline
19350 - If --RunAsDaemon is set, tor forks and backgrounds on startup