1 Changes in version 0.3.3.9 - 2018-07-13
2 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
3 bridge relays should upgrade.
5 o Directory authority changes:
6 - The "Bifroest" bridge authority has been retired; the new bridge
7 authority is "Serge", and it is operated by George from the
8 TorBSD project. Closes ticket 26771.
11 Changes in version 0.3.2.11 - 2018-07-13
12 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
13 bridge relays should upgrade. We also take this opportunity to backport
16 o Directory authority changes:
17 - The "Bifroest" bridge authority has been retired; the new bridge
18 authority is "Serge", and it is operated by George from the
19 TorBSD project. Closes ticket 26771.
21 o Directory authority changes (backport from 0.3.3.7):
22 - Add an IPv6 address for the "dannenberg" directory authority.
25 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
26 - When directory authorities read a zero-byte bandwidth file, they
27 would previously log a warning with the contents of an
28 uninitialised buffer. They now log a warning about the empty file
29 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
31 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
32 - Correctly detect when onion services get disabled after HUP. Fixes
33 bug 25761; bugfix on 0.3.2.1.
35 o Minor features (sandbox, backport from 0.3.3.4-alpha):
36 - Explicitly permit the poll() system call when the Linux
37 seccomp2-based sandbox is enabled: apparently, some versions of
38 libc use poll() when calling getpwnam(). Closes ticket 25313.
40 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
41 - Update the Travis CI configuration to use the stable Rust channel,
42 now that we have decided to require that. Closes ticket 25714.
44 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
45 - Our .travis.yml configuration now includes support for testing the
46 results of "make distcheck". (It's not uncommon for "make check"
47 to pass but "make distcheck" to fail.) Closes ticket 25814.
48 - Our Travis CI configuration now integrates with the Coveralls
49 coverage analysis tool. Closes ticket 25818.
51 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
52 - Add several checks to detect whether Tor relays are uploading
53 their descriptors without specifying why they regenerated them.
54 Diagnostic for ticket 25686.
56 o Minor features (compilation, backport from 0.3.4.4-rc):
57 - When building Tor, prefer to use Python 3 over Python 2, and more
58 recent (contemplated) versions over older ones. Closes
61 o Minor features (geoip):
62 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
63 Country database. Closes ticket 26674.
65 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
66 - Upon receiving a malformed connected cell, stop processing the
67 cell immediately. Previously we would mark the connection for
68 close, but continue processing the cell as if the connection were
69 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
71 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
72 - Allow the nanosleep() system call, which glibc uses to implement
73 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
75 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
76 - When running the hs_ntor_ref.py test, make sure only to pass
77 strings (rather than "bytes" objects) to the Python subprocess
78 module. Python 3 on Windows seems to require this. Fixes bug
79 26535; bugfix on 0.3.1.1-alpha.
80 - When running the ntor_ref.py test, make sure only to pass strings
81 (rather than "bytes" objects) to the Python subprocess module.
82 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
85 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
86 - Work around a change in OpenSSL 1.1.1 where return values that
87 would previously indicate "no password" now indicate an empty
88 password. Without this workaround, Tor instances running with
89 OpenSSL 1.1.1 would accept descriptors that other Tor instances
90 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
92 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
93 - Document that the PerConnBW{Rate,Burst} options will fall back to
94 their corresponding consensus parameters only if those parameters
95 are set. Previously we had claimed that these values would always
96 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
98 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
99 - Fix a compilation warning on some versions of GCC when building
100 code that calls routerinfo_get_my_routerinfo() twice, assuming
101 that the second call will succeed if the first one did. Fixes bug
102 26269; bugfix on 0.2.8.2-alpha.
104 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
105 - Don't consider Tor running as a client if the ControlPort is open,
106 but no actual client ports are open. Fixes bug 26062; bugfix
109 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
110 - Prevent a possible out-of-bounds smartlist read in
111 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
113 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
114 - Fix a very unlikely (impossible, we believe) null pointer
115 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
116 Coverity; this is CID 1430932.
118 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
119 - Fix a memory leak when a v3 onion service is configured and gets a
120 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
121 - When parsing the descriptor signature, look for the token plus an
122 extra white-space at the end. This is more correct but also will
123 allow us to support new fields that might start with "signature".
124 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
126 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
127 - Relays now correctly block attempts to re-extend to the previous
128 relay by Ed25519 identity. Previously they would warn in this
129 case, but not actually reject the attempt. Fixes bug 26158; bugfix
132 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
133 - Avoid a crash when running with DirPort set but ORPort turned off.
134 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
136 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
137 - Silence unused-const-variable warnings in zstd.h with some GCC
138 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
140 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
141 - Avoid intermittent test failures due to a test that had relied on
142 onion service introduction point creation finishing within 5
143 seconds of real clock time. Fixes bug 25450; bugfix
146 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
147 - Fix a C99 compliance issue in our configuration script that caused
148 compilation issues when compiling Tor with certain versions of
149 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
151 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
152 - Fix a number of small memory leaks identified by coverity. Fixes
153 bug 26467; bugfix on numerous Tor versions.
155 o Code simplification and refactoring (backport from 0.3.3.5-rc):
156 - Move the list of default directory authorities to its own file.
157 Closes ticket 24854. Patch by "beastr0".
160 Changes in version 0.2.9.16 - 2018-07-13
161 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
162 bridge relays should upgrade. We also take this opportunity to backport
165 o Directory authority changes:
166 - The "Bifroest" bridge authority has been retired; the new bridge
167 authority is "Serge", and it is operated by George from the
168 TorBSD project. Closes ticket 26771.
170 o Directory authority changes (backport from 0.3.3.7):
171 - Add an IPv6 address for the "dannenberg" directory authority.
174 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
175 - When directory authorities read a zero-byte bandwidth file, they
176 would previously log a warning with the contents of an
177 uninitialised buffer. They now log a warning about the empty file
178 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
180 o Minor features (sandbox, backport from 0.3.3.4-alpha):
181 - Explicitly permit the poll() system call when the Linux
182 seccomp2-based sandbox is enabled: apparently, some versions of
183 libc use poll() when calling getpwnam(). Closes ticket 25313.
185 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
186 - Our .travis.yml configuration now includes support for testing the
187 results of "make distcheck". (It's not uncommon for "make check"
188 to pass but "make distcheck" to fail.) Closes ticket 25814.
189 - Our Travis CI configuration now integrates with the Coveralls
190 coverage analysis tool. Closes ticket 25818.
192 o Minor features (compilation, backport from 0.3.4.4-rc):
193 - When building Tor, prefer to use Python 3 over Python 2, and more
194 recent (contemplated) versions over older ones. Closes
197 o Minor features (geoip):
198 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
199 Country database. Closes ticket 26674.
201 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
202 - Upon receiving a malformed connected cell, stop processing the
203 cell immediately. Previously we would mark the connection for
204 close, but continue processing the cell as if the connection were
205 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
207 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
208 - Allow the nanosleep() system call, which glibc uses to implement
209 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
211 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
212 - When running the ntor_ref.py test, make sure only to pass strings
213 (rather than "bytes" objects) to the Python subprocess module.
214 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
217 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
218 - Work around a change in OpenSSL 1.1.1 where return values that
219 would previously indicate "no password" now indicate an empty
220 password. Without this workaround, Tor instances running with
221 OpenSSL 1.1.1 would accept descriptors that other Tor instances
222 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
224 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
225 - Fix a compilation warning on some versions of GCC when building
226 code that calls routerinfo_get_my_routerinfo() twice, assuming
227 that the second call will succeed if the first one did. Fixes bug
228 26269; bugfix on 0.2.8.2-alpha.
230 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
231 - Don't consider Tor running as a client if the ControlPort is open,
232 but no actual client ports are open. Fixes bug 26062; bugfix
235 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
236 - Prevent a possible out-of-bounds smartlist read in
237 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
239 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
240 - Fix a very unlikely (impossible, we believe) null pointer
241 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
242 Coverity; this is CID 1430932.
244 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
245 - Fix a number of small memory leaks identified by coverity. Fixes
246 bug 26467; bugfix on numerous Tor versions.
248 o Code simplification and refactoring (backport from 0.3.3.5-rc):
249 - Move the list of default directory authorities to its own file.
250 Closes ticket 24854. Patch by "beastr0".
253 Changes in version 0.3.3.8 - 2018-07-09
254 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
255 fixes for a memory leak affecting directory authorities.
257 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
258 - Stop leaking memory on directory authorities when planning to
259 vote. This bug was crashing authorities by exhausting their
260 memory. Fixes bug 26435; bugfix on 0.3.3.6.
262 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
263 - Make sure that failing tests in Rust will actually cause the build
264 to fail: previously, they were ignored. Fixes bug 26258; bugfix
267 o Minor features (compilation, backport from 0.3.4.4-rc):
268 - When building Tor, prefer to use Python 3 over Python 2, and more
269 recent (contemplated) versions over older ones. Closes
272 o Minor features (geoip):
273 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
274 Country database. Closes ticket 26674.
276 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
277 - Add several checks to detect whether Tor relays are uploading
278 their descriptors without specifying why they regenerated them.
279 Diagnostic for ticket 25686.
281 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
282 - Don't count path selection failures as circuit build failures.
283 This change should eliminate cases where Tor blames its guard or
284 the network for situations like insufficient microdescriptors
285 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
288 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
289 - Fix a compilation warning on some versions of GCC when building
290 code that calls routerinfo_get_my_routerinfo() twice, assuming
291 that the second call will succeed if the first one did. Fixes bug
292 26269; bugfix on 0.2.8.2-alpha.
294 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
295 - Handle the HSADDRESS= argument to the HSPOST command properly.
296 (Previously, this argument was misparsed and thus ignored.) Fixes
297 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
299 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
300 - Fix a number of small memory leaks identified by coverity. Fixes
301 bug 26467; bugfix on numerous Tor versions.
303 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
304 - Relays now correctly block attempts to re-extend to the previous
305 relay by Ed25519 identity. Previously they would warn in this
306 case, but not actually reject the attempt. Fixes bug 26158; bugfix
309 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
310 - When shutting down, Tor now clears all the flags in the control.c
311 module. This should prevent a bug where authentication cookies are
312 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
314 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
315 - When running the hs_ntor_ref.py test, make sure only to pass
316 strings (rather than "bytes" objects) to the Python subprocess
317 module. Python 3 on Windows seems to require this. Fixes bug
318 26535; bugfix on 0.3.1.1-alpha.
319 - When running the ntor_ref.py test, make sure only to pass strings
320 (rather than "bytes" objects) to the Python subprocess module.
321 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
325 Changes in version 0.3.3.7 - 2018-06-12
326 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
327 fixes for bugs affecting compatibility and stability.
329 o Directory authority changes:
330 - Add an IPv6 address for the "dannenberg" directory authority.
333 o Minor features (geoip):
334 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
335 Country database. Closes ticket 26351.
337 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
338 - Work around a change in OpenSSL 1.1.1 where return values that
339 would previously indicate "no password" now indicate an empty
340 password. Without this workaround, Tor instances running with
341 OpenSSL 1.1.1 would accept descriptors that other Tor instances
342 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
344 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
345 - Silence unused-const-variable warnings in zstd.h with some GCC
346 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
348 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
349 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
350 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
351 miscounting the total number of circuits for these field values.)
352 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
354 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
355 - Prevent a possible out-of-bounds smartlist read in
356 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
358 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
359 - Only select relays when they have the descriptors we prefer to use
360 for them. This change fixes a bug where we could select a relay
361 because it had _some_ descriptor, but reject it later with a
362 nonfatal assertion error because it didn't have the exact one we
363 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
366 Changes in version 0.3.3.6 - 2018-05-22
367 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
368 backports several important fixes from the 0.3.4.1-alpha.
370 The Tor 0.3.3 series includes controller support and other
371 improvements for v3 onion services, official support for embedding Tor
372 within other applications, and our first non-trivial module written in
373 the Rust programming language. (Rust is still not enabled by default
374 when building Tor.) And as usual, there are numerous other smaller
375 bugfixes, features, and improvements.
377 Below are the changes since 0.3.3.5-rc. For a list of all changes
378 since 0.3.2.10, see the ReleaseNotes file.
380 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
381 - When directory authorities read a zero-byte bandwidth file, they
382 would previously log a warning with the contents of an
383 uninitialised buffer. They now log a warning about the empty file
384 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
386 o Major bugfixes (security, directory authority, denial-of-service):
387 - Fix a bug that could have allowed an attacker to force a directory
388 authority to use up all its RAM by passing it a maliciously
389 crafted protocol versions string. Fixes bug 25517; bugfix on
390 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
392 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
393 - Avoid a rare assertion failure in the circuit build timeout code
394 if we fail to allow any circuits to actually complete. Fixes bug
395 25733; bugfix on 0.2.2.2-alpha.
397 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
398 - Avoid a crash when testing router reachability on a router that
399 could have an ed25519 ID, but which does not. Fixes bug 25415;
400 bugfix on 0.3.3.2-alpha.
402 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
403 - Correctly detect when onion services get disabled after HUP. Fixes
404 bug 25761; bugfix on 0.3.2.1.
406 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
407 - Impose a limit on circuit cell queue size. The limit can be
408 controlled by a consensus parameter. Fixes bug 25226; bugfix
411 o Minor features (compatibility, backport from 0.3.4.1-alpha):
412 - Avoid some compilation warnings with recent versions of LibreSSL.
415 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
416 - Our .travis.yml configuration now includes support for testing the
417 results of "make distcheck". (It's not uncommon for "make check"
418 to pass but "make distcheck" to fail.) Closes ticket 25814.
419 - Our Travis CI configuration now integrates with the Coveralls
420 coverage analysis tool. Closes ticket 25818.
422 o Minor features (geoip):
423 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
424 database. Closes ticket 26104.
426 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
427 - Don't consider Tor running as a client if the ControlPort is open,
428 but no actual client ports are open. Fixes bug 26062; bugfix
431 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
432 - Upon receiving a malformed connected cell, stop processing the
433 cell immediately. Previously we would mark the connection for
434 close, but continue processing the cell as if the connection were
435 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
437 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
438 - Stop saying in the manual that clients cache ipv4 dns answers from
439 exit relays. We haven't used them since 0.2.6.3-alpha, and in
440 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
441 we forgot to say so in the man page. Fixes bug 26052; bugfix
444 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
445 - Allow the nanosleep() system call, which glibc uses to implement
446 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
448 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
449 - Fix a memory leak when a v3 onion service is configured and gets a
450 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
451 - When parsing the descriptor signature, look for the token plus an
452 extra white-space at the end. This is more correct but also will
453 allow us to support new fields that might start with "signature".
454 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
456 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
457 - Avoid a crash when running with DirPort set but ORPort tuned off.
458 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
460 o Documentation (backport from 0.3.4.1-alpha):
461 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
462 ticket 25857. Patch from "CTassisF".
465 Changes in version 0.3.3.5-rc - 2018-04-15
466 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
467 including some that could affect reliability or correctness.
469 This is the first release candidate in the 0.3.3 series. If we find no
470 new bugs or regression here, then the first stable 0.3.3 release will
471 be nearly identical to this one.
473 o Major bugfixes (security, protover, voting):
474 - Revise Rust implementation of protover to use a more memory-
475 efficient voting algorithm and corresponding data structures, thus
476 avoiding a potential memory-based DoS attack where specially
477 crafted protocol strings would expand to fill available memory.
478 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
480 o Major bugfixes (performance, load balancing):
481 - Directory authorities no longer vote in favor of the Guard flag
482 for relays without directory support. Starting in Tor
483 0.3.0.1-alpha, clients have been avoiding using such relays in the
484 Guard position, leading to increasingly broken load balancing for
485 the 5%-or-so of Guards that don't advertise directory support.
486 Fixes bug 22310; bugfix on 0.3.0.6.
488 o Minor feature (continuous integration):
489 - Update the Travis CI configuration to use the stable Rust channel,
490 now that we have decided to require that. Closes ticket 25714.
492 o Minor features (config options):
493 - Change the way the default value for MaxMemInQueues is calculated.
494 We now use 40% of the hardware RAM if the system has 8 GB RAM or
495 more. Otherwise we use the former value of 75%. Closes
498 o Minor features (geoip):
499 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
500 Country database. Closes ticket 25718.
502 o Minor bugfixes (client):
503 - When using a listed relay as a bridge, and also using
504 microdescriptors, and considering that relay as a non-bridge in a
505 circuit, treat its microdescriptor as a valid source of
506 information about that relay. This change should prevent a non-
507 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
509 o Minor bugfixes (controller):
510 - Restore the correct operation of the RESOLVE command, which had
511 been broken since we added the ability to enable/disable DNS on
512 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
514 o Minor bugfixes (distribution, compilation, rust):
515 - Build correctly when the rust dependencies submodule is loaded,
516 but the TOR_RUST_DEPENDENCIES environment variable is not set.
517 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
518 - Actually include all of our Rust source in our source
519 distributions. (Previously, a few of the files were accidentally
520 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
522 o Minor bugfixes (documentation):
523 - Document that the PerConnBW{Rate,Burst} options will fall back to
524 their corresponding consensus parameters only if those parameters
525 are set. Previously we had claimed that these values would always
526 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
527 - Revert a misformatting issue in the ExitPolicy documentation.
528 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
530 o Minor bugfixes (exit relay DNS retries):
531 - Re-attempt timed-out DNS queries 3 times before failure, since our
532 timeout is 5 seconds for them, but clients wait 10-15. Also allow
533 slightly more timeouts per resolver when an exit has multiple
534 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
536 o Minor bugfixes (onion services):
537 - Re-instate counting the client HSDir fetch circuits against the
538 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
540 - Remove underscores from the _HSLayer{2,3}Nodes options. This
541 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
542 Fixes bug 25581; bugfix on 0.3.3.1-alpha
544 o Code simplification and refactoring:
545 - Move the list of default directory authorities to its own file.
546 Closes ticket 24854. Patch by "beastr0".
548 o Documentation (manpage, denial of service):
549 - Provide more detail about the denial-of-service options, by
550 listing each mitigation and explaining how they relate. Closes
554 Changes in version 0.3.3.4-alpha - 2018-03-29
555 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
556 the alpha testing of earlier releases in its series. We are
557 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
559 o New system requirements:
560 - When built with Rust, Tor now depends on version 0.2.39 of the
561 libc crate. Closes tickets 25310 and 25664.
563 o Major bugfixes (relay, connection):
564 - If we have failed to connect to a relay and received a connection
565 refused, timeout, or similar error (at the TCP level), do not try
566 that same address/port again for 60 seconds after the failure has
567 occurred. Fixes bug 24767; bugfix on 0.0.6.
569 o Minor features (geoip):
570 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
571 Country database. Closes ticket 25469.
573 o Minor features (log messages):
574 - Improve log message in the out-of-memory handler to include
575 information about memory usage from the different compression
576 backends. Closes ticket 25372.
578 o Minor features (sandbox):
579 - Explicitly permit the poll() system call when the Linux
580 seccomp2-based sandbox is enabled: apparently, some versions of
581 libc use poll() when calling getpwnam(). Closes ticket 25313.
583 o Minor bugfixes (C correctness):
584 - Fix a very unlikely (impossible, we believe) null pointer
585 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
586 Coverity; this is CID 1430932.
588 o Minor bugfixes (channel, client):
589 - Better identify client connection when reporting to the geoip
590 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
592 o Minor bugfixes (compilation):
593 - Fix a C99 compliance issue in our configuration script that caused
594 compilation issues when compiling Tor with certain versions of
595 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
597 o Minor bugfixes (controller, reliability):
598 - Avoid a (nonfatal) assertion failure when extending a one-hop
599 circuit from the controller to become a multihop circuit. Fixes
600 bug 24903; bugfix on 0.2.5.2-alpha.
602 o Major bugfixes (networking):
603 - Tor will no longer reject IPv6 address strings from Tor Browser
604 when they are passed as hostnames in SOCKS5 requests. Fixes bug
605 25036, bugfix on Tor 0.3.1.2.
607 o Minor bugfixes (networking):
608 - string_is_valid_hostname() will not consider IP strings to be
609 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
611 o Minor bugfixes (onion service v3):
612 - Avoid an assertion failure when the next onion service
613 descriptor rotation type is out of sync with the consensus's
614 valid-after time. Instead, log a warning message with extra
615 information, so we can better hunt down the cause of this
616 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
618 o Minor bugfixes (testing):
619 - Avoid intermittent test failures due to a test that had relied on
620 onion service introduction point creation finishing within 5
621 seconds of real clock time. Fixes bug 25450; bugfix
623 - Rust crates are now automatically detected and tested. Previously,
624 some crates were not tested by `make test-rust` due to a static
625 string in the `src/test/test_rust.sh` script specifying which
626 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
628 o Minor bugfixes (testing, benchmarks):
629 - Fix a crash when running benchmark tests on win32 systems. The
630 crash was due to a mutex that wasn't initialized before logging
631 and options were initialized. Fixes bug 25479; bugfix
634 o Minor bugfixes (warnings, ipv6):
635 - Avoid a bug warning that could occur when trying to connect to a
636 relay over IPv6. This warning would occur on a Tor instance that
637 downloads router descriptors, but prefers to use microdescriptors.
638 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
640 o Code simplification and refactoring:
641 - Remove the old (deterministic) directory retry logic entirely:
642 We've used exponential backoff exclusively for some time. Closes
646 - Improved the documentation of AccountingStart parameter. Closes
648 - Update the documentation for "Log" to include the current list of
649 logging domains. Closes ticket 25378.
652 Changes in version 0.3.1.10 - 2018-03-03
653 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
656 It includes an important security fix for a remote crash attack
657 against directory authorities, tracked as TROVE-2018-001.
659 This release also backports our new system for improved resistance to
660 denial-of-service attacks against relays.
662 This release also fixes several minor bugs and annoyances from
665 All directory authorities should upgrade to one of the versions
666 released today. Relays running 0.3.1.x may wish to update to one of
667 the versions released today, for the DoS mitigations.
669 Please note: according to our release calendar, Tor 0.3.1 will no
670 longer be supported after 1 July 2018. If you will be running Tor
671 after that date, you should make sure to plan to upgrade to the latest
672 stable version, or downgrade to 0.2.9 (which will receive long-term
675 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
676 - Fix a protocol-list handling bug that could be used to remotely crash
677 directory authorities with a null-pointer exception. Fixes bug 25074;
678 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
681 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
682 - Give relays some defenses against the recent network overload. We
683 start with three defenses (default parameters in parentheses).
684 First: if a single client address makes too many concurrent
685 connections (>100), hang up on further connections. Second: if a
686 single client address makes circuits too quickly (more than 3 per
687 second, with an allowed burst of 90) while also having too many
688 connections open (3), refuse new create cells for the next while
689 (1-2 hours). Third: if a client asks to establish a rendezvous
690 point to you directly, ignore the request. These defenses can be
691 manually controlled by new torrc options, but relays will also
692 take guidance from consensus parameters, so there's no need to
693 configure anything manually. Implements ticket 24902.
695 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
696 - Update the sandbox rules so that they should now work correctly
697 with Glibc 2.26. Closes ticket 24315.
699 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
700 - Fix an "off by 2" error in counting rendezvous failures on the
701 onion service side. While we thought we would stop the rendezvous
702 attempt after one failed circuit, we were actually making three
703 circuit attempts before giving up. Now switch to a default of 2,
704 and allow the consensus parameter "hs_service_max_rdv_failures" to
705 override. Fixes bug 24895; bugfix on 0.0.6.
707 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
708 - Add Link protocol version 5 to the supported protocols list. Fixes
709 bug 25070; bugfix on 0.3.1.1-alpha.
711 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
712 - Fix a set of false positives where relays would consider
713 connections to other relays as being client-only connections (and
714 thus e.g. deserving different link padding schemes) if those
715 relays fell out of the consensus briefly. Now we look only at the
716 initial handshake and whether the connection authenticated as a
717 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
719 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
720 - Make our OOM handler aware of the geoip client history cache so it
721 doesn't fill up the memory. This check is important for IPv6 and
722 our DoS mitigation subsystem. Closes ticket 25122.
724 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
725 - Change relay bandwidth reporting stats interval from 4 hours to 24
726 hours in order to reduce the efficiency of guard discovery
727 attacks. Fixes ticket 23856.
729 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
730 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
731 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
732 since they neither disabled TLS 1.3 nor enabled any of the
733 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
736 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
737 - The fallback directory list has been re-generated based on the
738 current status of the network. Tor uses fallback directories to
739 bootstrap when it doesn't yet have up-to-date directory
740 information. Closes ticket 24801.
741 - Make the default DirAuthorityFallbackRate 0.1, so that clients
742 prefer to bootstrap from fallback directory mirrors. This is a
743 follow-up to 24679, which removed weights from the default
744 fallbacks. Implements ticket 24681.
746 o Minor features (geoip):
747 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
750 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
751 - Use the actual observed address of an incoming relay connection,
752 not the canonical address of the relay from its descriptor, when
753 making decisions about how to handle the incoming connection.
754 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
756 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
757 - Directory authorities, when refusing a descriptor from a rejected
758 relay, now explicitly tell the relay (in its logs) to set a valid
759 ContactInfo address and contact the bad-relays@ mailing list.
760 Fixes bug 25170; bugfix on 0.2.9.1.
762 o Minor bugfixes (address selection, backport from 0.3.2.9):
763 - When the fascist_firewall_choose_address_ functions don't find a
764 reachable address, set the returned address to the null address
765 and port. This is a precautionary measure, because some callers do
766 not check the return value. Fixes bug 24736; bugfix
769 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
770 - Fetch descriptors aggressively whenever we lack enough to build
771 circuits, regardless of how many descriptors we are missing.
772 Previously, we would delay launching the fetch when we had fewer
773 than 15 missing descriptors, even if some of those descriptors
774 were blocking circuits from building. Fixes bug 23985; bugfix on
775 0.1.1.11-alpha. The effects of this bug became worse in
776 0.3.0.3-alpha, when we began treating missing descriptors from our
777 primary guards as a reason to delay circuits.
778 - Don't try fetching microdescriptors from relays that have failed
779 to deliver them in the past. Fixes bug 23817; bugfix
782 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
783 - Fix a signed/unsigned comparison warning introduced by our fix to
784 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
786 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
787 - Avoid a crash when attempting to use the seccomp2 sandbox together
788 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
791 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
792 - Fix a possible crash on malformed consensus. If a consensus had
793 contained an unparseable protocol line, it could have made clients
794 and relays crash with a null-pointer exception. To exploit this
795 issue, however, an attacker would need to be able to subvert the
796 directory authority system. Fixes bug 25251; bugfix on
797 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
799 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
800 - Recover better from empty or corrupt files in the consensus cache
801 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
802 - When a consensus diff calculation is only partially successful,
803 only record the successful parts as having succeeded. Partial
804 success can happen if (for example) one compression method fails
805 but the others succeed. Previously we misrecorded all the
806 calculations as having succeeded, which would later cause a
807 nonfatal assertion failure. Fixes bug 24086; bugfix
810 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
811 - Tor now updates its guard state when it reads a consensus
812 regardless of whether it's missing descriptors. That makes tor use
813 its primary guards to fetch descriptors in some edge cases where
814 it would previously have used fallback directories. Fixes bug
815 23862; bugfix on 0.3.0.1-alpha.
817 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
818 - Don't treat inability to store a cached consensus object as a bug:
819 it can happen normally when we are out of disk space. Fixes bug
820 24859; bugfix on 0.3.1.1-alpha.
822 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
823 - When queuing DESTROY cells on a channel, only queue the circuit-id
824 and reason fields: not the entire 514-byte cell. This fix should
825 help mitigate any bugs or attacks that fill up these queues, and
826 free more RAM for other uses. Fixes bug 24666; bugfix
829 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
830 - When closing a connection via close_connection_immediately(), we
831 mark it as "not blocked on bandwidth", to prevent later calls from
832 trying to unblock it, and give it permission to read. This fixes a
833 backtrace warning that can happen on relays under various
834 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
836 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
837 - When selecting relays by bandwidth, avoid a rounding error that
838 could sometimes cause load to be imbalanced incorrectly.
839 Previously, we would always round upwards; now, we round towards
840 the nearest integer. This had the biggest effect when a relay's
841 weight adjustments should have given it weight 0, but it got
842 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
843 - When calculating the fraction of nodes that have descriptors, and
844 all nodes in the network have zero bandwidths, count the number of
845 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
846 - Actually log the total bandwidth in compute_weighted_bandwidths().
847 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
849 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
850 - Improve the performance of our consensus-diff application code
851 when Tor is built with the --enable-fragile-hardening option set.
852 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
854 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
855 - Don't exit the Tor process if setrlimit() fails to change the file
856 limit (which can happen sometimes on some versions of OSX). Fixes
857 bug 21074; bugfix on 0.0.9pre5.
859 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
860 - Fix a bug in the bit-counting parts of our timing-wheel code on
861 MSVC. (Note that MSVC is still not a supported build platform, due
862 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
865 o Minor bugfixes (relay, partial backport):
866 - Make the internal channel_is_client() function look at what sort
867 of connection handshake the other side used, rather than whether
868 the other side ever sent a create_fast cell to us. Backports part
869 of the fixes from bugs 22805 and 24898.
871 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
872 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
874 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
875 bugfix on 0.2.9.4-alpha.
877 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
878 - Update the "rust dependencies" submodule to be a project-level
879 repository, rather than a user repository. Closes ticket 25323.
882 Changes in version 0.2.9.15 - 2018-03-03
883 Tor 0.2.9.15 backports important security and stability bugfixes from
886 It includes an important security fix for a remote crash attack
887 against directory authorities, tracked as TROVE-2018-001.
889 This release also backports our new system for improved resistance to
890 denial-of-service attacks against relays.
892 This release also fixes several minor bugs and annoyances from
895 All directory authorities should upgrade to one of the versions
896 released today. Relays running 0.2.9.x may wish to update to one of
897 the versions released today, for the DoS mitigations.
899 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
900 - Fix a protocol-list handling bug that could be used to remotely crash
901 directory authorities with a null-pointer exception. Fixes bug 25074;
902 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
905 o Major features (denial-of-service mitigation):
906 - Give relays some defenses against the recent network overload. We
907 start with three defenses (default parameters in parentheses).
908 First: if a single client address makes too many concurrent
909 connections (>100), hang up on further connections. Second: if a
910 single client address makes circuits too quickly (more than 3 per
911 second, with an allowed burst of 90) while also having too many
912 connections open (3), refuse new create cells for the next while
913 (1-2 hours). Third: if a client asks to establish a rendezvous
914 point to you directly, ignore the request. These defenses can be
915 manually controlled by new torrc options, but relays will also
916 take guidance from consensus parameters, so there's no need to
917 configure anything manually. Implements ticket 24902.
919 o Major bugfixes (bootstrapping):
920 - Fetch descriptors aggressively whenever we lack enough to build
921 circuits, regardless of how many descriptors we are missing.
922 Previously, we would delay launching the fetch when we had fewer
923 than 15 missing descriptors, even if some of those descriptors
924 were blocking circuits from building. Fixes bug 23985; bugfix on
925 0.1.1.11-alpha. The effects of this bug became worse in
926 0.3.0.3-alpha, when we began treating missing descriptors from our
927 primary guards as a reason to delay circuits.
929 o Major bugfixes (onion services, retry behavior):
930 - Fix an "off by 2" error in counting rendezvous failures on the
931 onion service side. While we thought we would stop the rendezvous
932 attempt after one failed circuit, we were actually making three
933 circuit attempts before giving up. Now switch to a default of 2,
934 and allow the consensus parameter "hs_service_max_rdv_failures" to
935 override. Fixes bug 24895; bugfix on 0.0.6.
937 o Minor feature (relay statistics):
938 - Change relay bandwidth reporting stats interval from 4 hours to 24
939 hours in order to reduce the efficiency of guard discovery
940 attacks. Fixes ticket 23856.
942 o Minor features (compatibility, OpenSSL):
943 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
944 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
945 since they neither disabled TLS 1.3 nor enabled any of the
946 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
949 o Minor features (denial-of-service avoidance):
950 - Make our OOM handler aware of the geoip client history cache so it
951 doesn't fill up the memory. This check is important for IPv6 and
952 our DoS mitigation subsystem. Closes ticket 25122.
954 o Minor features (fallback directory mirrors):
955 - The fallback directory list has been re-generated based on the
956 current status of the network. Tor uses fallback directories to
957 bootstrap when it doesn't yet have up-to-date directory
958 information. Closes ticket 24801.
959 - Make the default DirAuthorityFallbackRate 0.1, so that clients
960 prefer to bootstrap from fallback directory mirrors. This is a
961 follow-up to 24679, which removed weights from the default
962 fallbacks. Implements ticket 24681.
964 o Minor features (geoip):
965 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
968 o Minor features (linux seccomp2 sandbox):
969 - Update the sandbox rules so that they should now work correctly
970 with Glibc 2.26. Closes ticket 24315.
972 o Minor bugfix (channel connection):
973 - Use the actual observed address of an incoming relay connection,
974 not the canonical address of the relay from its descriptor, when
975 making decisions about how to handle the incoming connection.
976 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
978 o Minor bugfix (directory authority):
979 - Directory authorities, when refusing a descriptor from a rejected
980 relay, now explicitly tell the relay (in its logs) to set a valid
981 ContactInfo address and contact the bad-relays@ mailing list.
982 Fixes bug 25170; bugfix on 0.2.9.1.
984 o Minor bugfixes (address selection):
985 - When the fascist_firewall_choose_address_ functions don't find a
986 reachable address, set the returned address to the null address
987 and port. This is a precautionary measure, because some callers do
988 not check the return value. Fixes bug 24736; bugfix
991 o Minor bugfixes (compilation):
992 - Fix a signed/unsigned comparison warning introduced by our fix to
993 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
995 o Minor bugfixes (control port, linux seccomp2 sandbox):
996 - Avoid a crash when attempting to use the seccomp2 sandbox together
997 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1000 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1001 - Fix a possible crash on malformed consensus. If a consensus had
1002 contained an unparseable protocol line, it could have made clients
1003 and relays crash with a null-pointer exception. To exploit this
1004 issue, however, an attacker would need to be able to subvert the
1005 directory authority system. Fixes bug 25251; bugfix on
1006 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1008 o Minor bugfixes (memory usage):
1009 - When queuing DESTROY cells on a channel, only queue the circuit-id
1010 and reason fields: not the entire 514-byte cell. This fix should
1011 help mitigate any bugs or attacks that fill up these queues, and
1012 free more RAM for other uses. Fixes bug 24666; bugfix
1015 o Minor bugfixes (network layer):
1016 - When closing a connection via close_connection_immediately(), we
1017 mark it as "not blocked on bandwidth", to prevent later calls from
1018 trying to unblock it, and give it permission to read. This fixes a
1019 backtrace warning that can happen on relays under various
1020 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1022 o Minor bugfixes (OSX):
1023 - Don't exit the Tor process if setrlimit() fails to change the file
1024 limit (which can happen sometimes on some versions of OSX). Fixes
1025 bug 21074; bugfix on 0.0.9pre5.
1027 o Minor bugfixes (path selection):
1028 - When selecting relays by bandwidth, avoid a rounding error that
1029 could sometimes cause load to be imbalanced incorrectly.
1030 Previously, we would always round upwards; now, we round towards
1031 the nearest integer. This had the biggest effect when a relay's
1032 weight adjustments should have given it weight 0, but it got
1033 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1034 - When calculating the fraction of nodes that have descriptors, and
1035 all nodes in the network have zero bandwidths, count the number of
1036 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1037 - Actually log the total bandwidth in compute_weighted_bandwidths().
1038 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1040 o Minor bugfixes (portability, msvc):
1041 - Fix a bug in the bit-counting parts of our timing-wheel code on
1042 MSVC. (Note that MSVC is still not a supported build platform, due
1043 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
1046 o Minor bugfixes (relay):
1047 - Make the internal channel_is_client() function look at what sort
1048 of connection handshake the other side used, rather than whether
1049 the other side ever sent a create_fast cell to us. Backports part
1050 of the fixes from bugs 22805 and 24898.
1052 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1053 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1055 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1056 bugfix on 0.2.9.4-alpha.
1059 Changes in version 0.3.2.10 - 2018-03-03
1060 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
1061 backports a number of bugfixes, including important fixes for security
1064 It includes an important security fix for a remote crash attack
1065 against directory authorities, tracked as TROVE-2018-001.
1067 Additionally, it backports a fix for a bug whose severity we have
1068 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
1069 triggered in order to crash relays with a use-after-free pattern. As
1070 such, we are now tracking that bug as TROVE-2018-002 and
1071 CVE-2018-0491, and backporting it to earlier releases. This bug
1072 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
1075 This release also backports our new system for improved resistance to
1076 denial-of-service attacks against relays.
1078 This release also fixes several minor bugs and annoyances from
1081 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
1082 today, for the fix to TROVE-2018-002. Directory authorities should
1083 also upgrade. (Relays on earlier versions might want to update too for
1084 the DoS mitigations.)
1086 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1087 - Fix a protocol-list handling bug that could be used to remotely crash
1088 directory authorities with a null-pointer exception. Fixes bug 25074;
1089 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1092 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
1093 - Avoid adding the same channel twice in the KIST scheduler pending
1094 list, which could lead to remote denial-of-service use-after-free
1095 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
1097 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
1098 - Give relays some defenses against the recent network overload. We
1099 start with three defenses (default parameters in parentheses).
1100 First: if a single client address makes too many concurrent
1101 connections (>100), hang up on further connections. Second: if a
1102 single client address makes circuits too quickly (more than 3 per
1103 second, with an allowed burst of 90) while also having too many
1104 connections open (3), refuse new create cells for the next while
1105 (1-2 hours). Third: if a client asks to establish a rendezvous
1106 point to you directly, ignore the request. These defenses can be
1107 manually controlled by new torrc options, but relays will also
1108 take guidance from consensus parameters, so there's no need to
1109 configure anything manually. Implements ticket 24902.
1111 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
1112 - Fix an "off by 2" error in counting rendezvous failures on the
1113 onion service side. While we thought we would stop the rendezvous
1114 attempt after one failed circuit, we were actually making three
1115 circuit attempts before giving up. Now switch to a default of 2,
1116 and allow the consensus parameter "hs_service_max_rdv_failures" to
1117 override. Fixes bug 24895; bugfix on 0.0.6.
1118 - New-style (v3) onion services now obey the "max rendezvous circuit
1119 attempts" logic. Previously they would make as many rendezvous
1120 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
1121 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
1123 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
1124 - Add Link protocol version 5 to the supported protocols list. Fixes
1125 bug 25070; bugfix on 0.3.1.1-alpha.
1127 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
1128 - Fix a set of false positives where relays would consider
1129 connections to other relays as being client-only connections (and
1130 thus e.g. deserving different link padding schemes) if those
1131 relays fell out of the consensus briefly. Now we look only at the
1132 initial handshake and whether the connection authenticated as a
1133 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1135 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
1136 - The scheduler subsystem was failing to promptly notice changes in
1137 consensus parameters, making it harder to switch schedulers
1138 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
1140 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
1141 - Make our OOM handler aware of the geoip client history cache so it
1142 doesn't fill up the memory. This check is important for IPv6 and
1143 our DoS mitigation subsystem. Closes ticket 25122.
1145 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
1146 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1147 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1148 since they neither disabled TLS 1.3 nor enabled any of the
1149 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1150 Closes ticket 24978.
1152 o Minor features (geoip):
1153 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1156 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
1157 - When logging a failure to create an onion service's descriptor,
1158 also log what the problem with the descriptor was. Diagnostic
1161 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
1162 - Use the actual observed address of an incoming relay connection,
1163 not the canonical address of the relay from its descriptor, when
1164 making decisions about how to handle the incoming connection.
1165 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1167 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1168 - Fix a possible crash on malformed consensus. If a consensus had
1169 contained an unparseable protocol line, it could have made clients
1170 and relays crash with a null-pointer exception. To exploit this
1171 issue, however, an attacker would need to be able to subvert the
1172 directory authority system. Fixes bug 25251; bugfix on
1173 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1175 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
1176 - Directory authorities, when refusing a descriptor from a rejected
1177 relay, now explicitly tell the relay (in its logs) to set a valid
1178 ContactInfo address and contact the bad-relays@ mailing list.
1179 Fixes bug 25170; bugfix on 0.2.9.1.
1181 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
1182 - When building with Rust on OSX, link against libresolv, to work
1183 around the issue at https://github.com/rust-lang/rust/issues/46797.
1184 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
1186 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
1187 - Remove a BUG() statement when a client fetches an onion descriptor
1188 that has a lower revision counter than the one in its cache. This
1189 can happen in normal circumstances due to HSDir desync. Fixes bug
1190 24976; bugfix on 0.3.2.1-alpha.
1192 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
1193 - Don't treat inability to store a cached consensus object as a bug:
1194 it can happen normally when we are out of disk space. Fixes bug
1195 24859; bugfix on 0.3.1.1-alpha.
1197 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
1198 - Improve the performance of our consensus-diff application code
1199 when Tor is built with the --enable-fragile-hardening option set.
1200 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1202 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
1203 - Don't exit the Tor process if setrlimit() fails to change the file
1204 limit (which can happen sometimes on some versions of OSX). Fixes
1205 bug 21074; bugfix on 0.0.9pre5.
1207 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1208 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1210 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1211 bugfix on 0.2.9.4-alpha.
1213 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
1214 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
1215 25005; bugfix on 0.3.2.7-rc.
1217 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
1218 - Look at the "HSRend" protocol version, not the "HSDir" protocol
1219 version, when deciding whether a consensus entry can support the
1220 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
1221 bugfix on 0.3.2.1-alpha.
1223 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
1224 - Update the "rust dependencies" submodule to be a project-level
1225 repository, rather than a user repository. Closes ticket 25323.
1227 o Documentation (backport from 0.3.3.1-alpha)
1228 - Document that operators who run more than one relay or bridge are
1229 expected to set MyFamily and ContactInfo correctly. Closes
1233 Changes in version 0.3.3.3-alpha - 2018-03-03
1234 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
1235 It includes an important security fix for a remote crash attack
1236 against directory authorities tracked as TROVE-2018-001.
1238 Additionally, with this release, we are upgrading the severity of a
1239 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
1240 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
1241 a use-after-free pattern. As such, we are now tracking that bug as
1242 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
1243 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
1245 This release also fixes several minor bugs and annoyances from
1248 Relays running 0.3.2.x should upgrade to one of the versions released
1249 today, for the fix to TROVE-2018-002. Directory authorities should
1250 also upgrade. (Relays on earlier versions might want to update too for
1251 the DoS mitigations.)
1253 o Major bugfixes (denial-of-service, directory authority):
1254 - Fix a protocol-list handling bug that could be used to remotely crash
1255 directory authorities with a null-pointer exception. Fixes bug 25074;
1256 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1259 o Minor features (compatibility, OpenSSL):
1260 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1261 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1262 since they neither disabled TLS 1.3 nor enabled any of the
1263 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1264 Closes ticket 24978.
1266 o Minor features (logging):
1267 - Clarify the log messages produced when getrandom() or a related
1268 entropy-generation mechanism gives an error. Closes ticket 25120.
1270 o Minor features (testing):
1271 - Add a "make test-rust" target to run the rust tests only. Closes
1274 o Minor bugfixes (denial-of-service):
1275 - Fix a possible crash on malformed consensus. If a consensus had
1276 contained an unparseable protocol line, it could have made clients
1277 and relays crash with a null-pointer exception. To exploit this
1278 issue, however, an attacker would need to be able to subvert the
1279 directory authority system. Fixes bug 25251; bugfix on
1280 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1282 o Minor bugfixes (DoS mitigation):
1283 - Add extra safety checks when refilling the circuit creation bucket
1284 to ensure we never set a value above the allowed maximum burst.
1285 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
1286 - When a new consensus arrives, don't update our DoS-mitigation
1287 parameters if we aren't a public relay. Fixes bug 25223; bugfix
1290 o Minor bugfixes (man page, SocksPort):
1291 - Remove dead code from the old "SocksSocket" option, and rename
1292 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
1293 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
1295 o Minor bugfixes (performance):
1296 - Reduce the number of circuits that will be opened at once during
1297 the circuit build timeout phase. This is done by increasing the
1298 idle timeout to 3 minutes, and lowering the maximum number of
1299 concurrent learning circuits to 10. Fixes bug 24769; bugfix
1302 o Minor bugfixes (spec conformance):
1303 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1305 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1306 bugfix on 0.2.9.4-alpha.
1308 o Minor bugfixes (spec conformance, rust):
1309 - Resolve a denial-of-service issue caused by an infinite loop in
1310 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
1311 Also tracked as TROVE-2018-003.
1313 o Code simplification and refactoring:
1314 - Update the "rust dependencies" submodule to be a project-level
1315 repository, rather than a user repository. Closes ticket 25323.
1318 Changes in version 0.3.3.2-alpha - 2018-02-10
1319 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
1320 introduces a mechanism to handle the high loads that many relay
1321 operators have been reporting recently. It also fixes several bugs in
1322 older releases. If this new code proves reliable, we plan to backport
1323 it to older supported release series.
1325 o Major features (denial-of-service mitigation):
1326 - Give relays some defenses against the recent network overload. We
1327 start with three defenses (default parameters in parentheses).
1328 First: if a single client address makes too many concurrent
1329 connections (>100), hang up on further connections. Second: if a
1330 single client address makes circuits too quickly (more than 3 per
1331 second, with an allowed burst of 90) while also having too many
1332 connections open (3), refuse new create cells for the next while
1333 (1-2 hours). Third: if a client asks to establish a rendezvous
1334 point to you directly, ignore the request. These defenses can be
1335 manually controlled by new torrc options, but relays will also
1336 take guidance from consensus parameters, so there's no need to
1337 configure anything manually. Implements ticket 24902.
1339 o Major bugfixes (netflow padding):
1340 - Stop adding unneeded channel padding right after we finish
1341 flushing to a connection that has been trying to flush for many
1342 seconds. Instead, treat all partial or complete flushes as
1343 activity on the channel, which will defer the time until we need
1344 to add padding. This fix should resolve confusing and scary log
1345 messages like "Channel padding timeout scheduled 221453ms in the
1346 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
1348 o Major bugfixes (protocol versions):
1349 - Add Link protocol version 5 to the supported protocols list. Fixes
1350 bug 25070; bugfix on 0.3.1.1-alpha.
1352 o Major bugfixes (scheduler, consensus):
1353 - The scheduler subsystem was failing to promptly notice changes in
1354 consensus parameters, making it harder to switch schedulers
1355 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
1357 o Minor features (denial-of-service avoidance):
1358 - Make our OOM handler aware of the geoip client history cache so it
1359 doesn't fill up the memory. This check is important for IPv6 and
1360 our DoS mitigation subsystem. Closes ticket 25122.
1362 o Minor features (directory authority):
1363 - When directory authorities are unable to add signatures to a
1364 pending consensus, log the reason why. Closes ticket 24849.
1366 o Minor features (geoip):
1367 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1370 o Minor features (logging, diagnostic):
1371 - When logging a failure to create an onion service's descriptor,
1372 also log what the problem with the descriptor was. Diagnostic for
1375 o Minor bugfix (channel connection):
1376 - Use the actual observed address of an incoming relay connection,
1377 not the canonical address of the relay from its descriptor, when
1378 making decisions about how to handle the incoming connection.
1379 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1381 o Minor bugfix (directory authority):
1382 - Directory authorities, when refusing a descriptor from a rejected
1383 relay, now explicitly tell the relay (in its logs) to set a valid
1384 ContactInfo address and contact the bad-relays@ mailing list.
1385 Fixes bug 25170; bugfix on 0.2.9.1.
1387 o Minor bugfixes (all versions of Tor):
1388 - Use the "misspell" tool to detect and fix typos throughout the
1389 source code. Fixes bug 23650; bugfix on various versions of Tor.
1390 Patch from Deepesh Pathak.
1392 o Minor bugfixes (circuit, cannibalization):
1393 - Don't cannibalize preemptively-built circuits if we no longer
1394 recognize their first hop. This situation can happen if our Guard
1395 relay went off the consensus after the circuit was created. Fixes
1396 bug 24469; bugfix on 0.0.6.
1398 o Minor bugfixes (correctness):
1399 - Remove a nonworking, unnecessary check to see whether a circuit
1400 hop's identity digest was set when the circuit failed. Fixes bug
1401 24927; bugfix on 0.2.4.4-alpha.
1403 o Minor bugfixes (logging):
1404 - Don't treat inability to store a cached consensus object as a bug:
1405 it can happen normally when we are out of disk space. Fixes bug
1406 24859; bugfix on 0.3.1.1-alpha.
1407 - Fix a (mostly harmless) race condition when invoking
1408 LOG_PROTOCOL_WARN message from a subthread while the torrc options
1409 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
1411 o Minor bugfixes (onion services):
1412 - Remove a BUG() statement when a client fetches an onion descriptor
1413 that has a lower revision counter than the one in its cache. This
1414 can happen in normal circumstances due to HSDir desync. Fixes bug
1415 24976; bugfix on 0.3.2.1-alpha.
1416 - If we are configured to offer a single onion service, don't log
1417 long-term established one hop rendezvous points in the heartbeat.
1418 Fixes bug 25116; bugfix on 0.2.9.6-rc.
1420 o Minor bugfixes (performance):
1421 - Avoid calling protocol_list_supports_protocol() from inside tight
1422 loops when running with cached routerinfo_t objects. Instead,
1423 summarize the relevant protocols as flags in the routerinfo_t, as
1424 we do for routerstatus_t objects. This change simplifies our code
1425 a little, and saves a large amount of short-term memory allocation
1426 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
1428 o Minor bugfixes (Rust FFI):
1429 - Fix a minor memory leak which would happen whenever the C code
1430 would call the Rust implementation of
1431 protover_get_supported_protocols(). This was due to the C version
1432 returning a static string, whereas the Rust version newly allocated
1433 a CString to pass across the FFI boundary. Consequently, the C
1434 code was not expecting to need to free() what it was given. Fixes
1435 bug 25127; bugfix on 0.3.2.1-alpha.
1437 o Minor bugfixes (scheduler, KIST):
1438 - Avoid adding the same channel twice in the KIST scheduler pending
1439 list, which would waste CPU cycles. Fixes bug 24700; bugfix
1442 o Minor bugfixes (unit test, monotonic time):
1443 - Increase a constant (1msec to 10msec) in the monotonic time test
1444 that makes sure the nsec/usec/msec times read are synchronized.
1445 This change was needed to accommodate slow systems like armel or
1446 when the clock_gettime() is not a VDSO on the running kernel.
1447 Fixes bug 25113; bugfix on 0.2.9.1.
1449 o Minor bugfixes (v3 onion services):
1450 - Look at the "HSRend" protocol version, not the "HSDir" protocol
1451 version, when deciding whether a consensus entry can support the
1452 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
1453 bugfix on 0.3.2.1-alpha.
1455 o Code simplification and refactoring:
1456 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
1458 - Remove a series of counters used to track circuit extend attempts
1459 and connection status but that in reality we aren't using for
1460 anything other than stats logged by a SIGUSR1 signal. Closes
1463 o Documentation (man page):
1464 - The HiddenServiceVersion torrc option accepts only one number:
1465 either version 2 or 3. Closes ticket 25026; bugfix
1469 Changes in version 0.3.3.1-alpha - 2018-01-25
1470 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
1471 several new features to Tor, including several improvements to
1472 bootstrapping, and support for an experimental "vanguards" feature to
1473 resist guard discovery attacks. This series also includes better
1474 support for applications that need to embed Tor or manage v3
1477 o Major features (embedding):
1478 - There is now a documented stable API for programs that need to
1479 embed Tor. See tor_api.h for full documentation and known bugs.
1480 Closes ticket 23684.
1481 - Tor now has support for restarting in the same process.
1482 Controllers that run Tor using the "tor_api.h" interface can now
1483 restart Tor after Tor has exited. This support is incomplete,
1484 however: we fixed crash bugs that prevented it from working at
1485 all, but many bugs probably remain, including a possibility of
1486 security issues. Implements ticket 24581.
1488 o Major features (IPv6, directory documents):
1489 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
1490 consensus. This information makes it easier for IPv6 clients to
1491 bootstrap and choose reachable entry guards. Implements ticket 23826.
1492 - Add consensus method 28, which removes IPv6 ORPorts from
1493 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
1494 are redundant in microdescs. This change will be used by Tor clients
1495 on 0.2.8.x and later. (That is to say, with all Tor clients that
1496 have IPv6 bootstrap and guard support.) Implements ticket 23828.
1497 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
1498 set by different numbers of authorities. Fixes 23870
1501 o Major features (onion service v3, control port):
1502 - The control port now supports commands and events for v3 onion
1503 services. It is now possible to create ephemeral v3 services using
1504 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
1505 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
1506 DEL_ONION) have been extended to support v3 onion services. Closes
1507 ticket 20699; implements proposal 284.
1509 o Major features (onion services):
1510 - Provide torrc options to pin the second and third hops of onion
1511 service circuits to a list of nodes. The option HSLayer2Guards
1512 pins the second hop, and the option HSLayer3Guards pins the third
1513 hop. These options are for use in conjunction with experiments
1514 with "vanguards" for preventing guard enumeration attacks. Closes
1517 o Major features (rust, portability, experimental):
1518 - Tor now ships with an optional implementation of one of its
1519 smaller modules (protover.c) in the Rust programming language. To
1520 try it out, install a Rust build environment, and configure Tor
1521 with "--enable-rust --enable-cargo-online-mode". This should not
1522 cause any user-visible changes, but should help us gain more
1523 experience with Rust, and plan future Rust integration work.
1524 Implementation by Chelsea Komlo. Closes ticket 22840.
1526 o Minor features (storage, configuration):
1527 - Users can store cached directory documents somewhere other than
1528 the DataDirectory by using the CacheDirectory option. Similarly,
1529 the storage location for relay's keys can be overridden with the
1530 KeyDirectory option. Closes ticket 22703.
1532 o Major features (v3 onion services, ipv6):
1533 - When v3 onion service clients send introduce cells, they now
1534 include the IPv6 address of the rendezvous point, if it has one.
1535 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
1536 in future Tor versions, IPv6-only v3 single onion services will be
1537 able to use IPv6 addresses to connect directly to the rendezvous
1538 point. Closes ticket 23577. Patch by Neel Chauhan.
1540 o Major bugfixes (onion services, retry behavior):
1541 - Fix an "off by 2" error in counting rendezvous failures on the
1542 onion service side. While we thought we would stop the rendezvous
1543 attempt after one failed circuit, we were actually making three
1544 circuit attempts before giving up. Now switch to a default of 2,
1545 and allow the consensus parameter "hs_service_max_rdv_failures" to
1546 override. Fixes bug 24895; bugfix on 0.0.6.
1547 - New-style (v3) onion services now obey the "max rendezvous circuit
1548 attempts" logic. Previously they would make as many rendezvous
1549 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
1550 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
1552 o Major bugfixes (relays):
1553 - Fix a set of false positives where relays would consider
1554 connections to other relays as being client-only connections (and
1555 thus e.g. deserving different link padding schemes) if those
1556 relays fell out of the consensus briefly. Now we look only at the
1557 initial handshake and whether the connection authenticated as a
1558 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1560 o Minor feature (IPv6):
1561 - Make IPv6-only clients wait for microdescs for relays, even if we
1562 were previously using descriptors (or were using them as a bridge)
1563 and have a cached descriptor for them. Implements ticket 23827.
1564 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
1565 them, rather than waiting to download microdescriptors.
1566 Implements ticket 23827.
1568 o Minor features (cleanup):
1569 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
1570 when it stops. Closes ticket 23271.
1572 o Minor features (defensive programming):
1573 - Most of the functions in Tor that free objects have been replaced
1574 with macros that free the objects and set the corresponding
1575 pointers to NULL. This change should help prevent a large class of
1576 dangling pointer bugs. Closes ticket 24337.
1577 - Where possible, the tor_free() macro now only evaluates its input
1578 once. Part of ticket 24337.
1579 - Check that microdesc ed25519 ids are non-zero in
1580 node_get_ed25519_id() before returning them. Implements ticket
1581 24001, patch by "aruna1234".
1583 o Minor features (embedding):
1584 - Tor can now start with a preauthenticated control connection
1585 created by the process that launched it. This feature is meant for
1586 use by programs that want to launch and manage a Tor process
1587 without allowing other programs to manage it as well. For more
1588 information, see the __OwningControllerFD option documented in
1589 control-spec.txt. Closes ticket 23900.
1590 - On most errors that would cause Tor to exit, it now tries to
1591 return from the tor_main() function, rather than calling the
1592 system exit() function. Most users won't notice a difference here,
1593 but it should be significant for programs that run Tor inside
1594 a separate thread: they should now be able to survive Tor's exit
1595 conditions rather than having Tor shut down the entire process.
1596 Closes ticket 23848.
1597 - Applications that want to embed Tor can now tell Tor not to
1598 register any of its own POSIX signal handlers, using the
1599 __DisableSignalHandlers option. Closes ticket 24588.
1601 o Minor features (fallback directory list):
1602 - Avoid selecting fallbacks that change their IP addresses too
1603 often. Select more fallbacks by ignoring the Guard flag, and
1604 allowing lower cutoffs for the Running and V2Dir flags. Also allow
1605 a lower bandwidth, and a higher number of fallbacks per operator
1606 (5% of the list). Implements ticket 24785.
1607 - Update the fallback whitelist and blacklist based on opt-ins and
1608 relay changes. Closes tickets 22321, 24678, 22527, 24135,
1611 o Minor features (fallback directory mirror configuration):
1612 - Add a nickname to each fallback in a C comment. This makes it
1613 easier for operators to find their relays, and allows stem to use
1614 nicknames to identify fallbacks. Implements ticket 24600.
1615 - Add a type and version header to the fallback directory mirror
1616 file. Also add a delimiter to the end of each fallback entry. This
1617 helps external parsers like stem and Relay Search. Implements
1619 - Add an extrainfo cache flag for each fallback in a C comment. This
1620 allows stem to use fallbacks to fetch extra-info documents, rather
1621 than using authorities. Implements ticket 22759.
1622 - Add the generateFallbackDirLine.py script for automatically
1623 generating fallback directory mirror lines from relay fingerprints.
1624 No more typos! Add the lookupFallbackDirContact.py script for
1625 automatically looking up operator contact info from relay
1626 fingerprints. Implements ticket 24706, patch by teor and atagar.
1627 - Reject any fallback directory mirror that serves an expired
1628 consensus. Implements ticket 20942, patch by "minik".
1629 - Remove commas and equals signs from external string inputs to the
1630 fallback list. This avoids format confusion attacks. Implements
1632 - Remove the "weight=10" line from fallback directory mirror
1633 entries. Ticket 24681 will maintain the current fallback weights
1634 by changing Tor's default fallback weight to 10. Implements
1636 - Stop logging excessive information about fallback netblocks.
1637 Implements ticket 24791.
1639 o Minor features (forward-compatibility):
1640 - If a relay supports some link authentication protocol that we do
1641 not recognize, then include that relay's ed25519 key when telling
1642 other relays to extend to it. Previously, we treated future
1643 versions as if they were too old to support ed25519 link
1644 authentication. Closes ticket 20895.
1646 o Minor features (heartbeat):
1647 - Add onion service information to our heartbeat logs, displaying
1648 stats about the activity of configured onion services. Closes
1651 o Minor features (instrumentation, development):
1652 - Add the MainloopStats option to allow developers to get
1653 instrumentation information from the main event loop via the
1654 heartbeat messages. We hope to use this to improve Tor's behavior
1655 when it's trying to sleep. Closes ticket 24605.
1657 o Minor features (log messages):
1658 - Improve a warning message that happens when we fail to re-parse an
1659 old router because of an expired certificate. Closes ticket 20020.
1660 - Make the log more quantitative when we hit MaxMemInQueues
1661 threshold exposing some values. Closes ticket 24501.
1663 o Minor features (logging, android):
1664 - Added support for the Android logging subsystem. Closes
1667 o Minor features (performance):
1668 - Support predictive circuit building for onion service circuits
1669 with multiple layers of guards. Closes ticket 23101.
1670 - Use stdatomic.h where available, rather than mutexes, to implement
1671 atomic_counter_t. Closes ticket 23953.
1673 o Minor features (performance, 32-bit):
1674 - Improve performance on 32-bit systems by avoiding 64-bit division
1675 when calculating the timestamp in milliseconds for channel padding
1676 computations. Implements ticket 24613.
1677 - Improve performance on 32-bit systems by avoiding 64-bit division
1678 when timestamping cells and buffer chunks for OOM calculations.
1679 Implements ticket 24374.
1681 o Minor features (performance, OSX, iOS):
1682 - Use the mach_approximate_time() function (when available) to
1683 implement coarse monotonic time. Having a coarse time function
1684 should avoid a large number of system calls, and improve
1685 performance slightly, especially under load. Closes ticket 24427.
1687 o Minor features (performance, windows):
1688 - Improve performance on Windows Vista and Windows 7 by adjusting
1689 TCP send window size according to the recommendation from
1690 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
1693 o Major features (relay):
1694 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
1695 operator to use a more reasonable ("reduced") exit policy, rather
1696 than the default one. If you want to run an exit node without
1697 thinking too hard about which ports to allow, this one is for you.
1698 Closes ticket 13605. Patch from Neel Chauhan.
1700 o Minor features (testing, debugging, embedding):
1701 - For development purposes, Tor now has a mode in which it runs for
1702 a few seconds, then stops, and starts again without exiting the
1703 process. This mode is meant to help us debug various issues with
1704 ticket 23847. To use this feature, compile with
1705 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
1706 environment variable. This is expected to crash a lot, and is
1707 really meant for developers only. It will likely be removed in a
1708 future release. Implements ticket 24583.
1710 o Minor bugfix (network IPv6 test):
1711 - Tor's test scripts now check if "ping -6 ::1" works when the user
1712 runs "make test-network-all". Fixes bug 24677; bugfix on
1713 0.2.9.3-alpha. Patch by "ffmancera".
1715 o Minor bugfixes (build, rust):
1716 - Fix output of autoconf checks to display success messages for Rust
1717 dependencies and a suitable rustc compiler version. Fixes bug
1718 24612; bugfix on 0.3.1.3-alpha.
1719 - When building with Rust on OSX, link against libresolv, to work
1720 around the issue at https://github.com/rust-lang/rust/issues/46797.
1721 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
1722 - Don't pass the --quiet option to cargo: it seems to suppress some
1723 errors, which is not what we want to do when building. Fixes bug
1724 24518; bugfix on 0.3.1.7.
1725 - Build correctly when building from outside Tor's source tree with
1726 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
1729 o Minor bugfixes (directory authorities, IPv6):
1730 - When creating a routerstatus (vote) from a routerinfo (descriptor),
1731 set the IPv6 address to the unspecified IPv6 address, and
1732 explicitly initialize the port to zero. Fixes bug 24488; bugfix
1735 o Minor bugfixes (fallback directory mirrors):
1736 - Make updateFallbackDirs.py search harder for python. (Some OSs
1737 don't put it in /usr/bin.) Fixes bug 24708; bugfix
1740 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
1741 - When hibernating, close connections normally and allow them to
1742 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
1744 - Do not attempt to launch self-reachability tests when entering
1745 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
1746 - Resolve several bugs related to descriptor fetching on bridge
1747 clients with bandwidth accounting enabled. (This combination is
1748 not recommended!) Fixes a case of bug 12062; bugfix
1750 - When hibernating, do not attempt to launch DNS checks. Fixes a
1751 case of bug 12062; bugfix on 0.1.2.2-alpha.
1752 - When hibernating, do not try to upload or download descriptors.
1753 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
1755 o Minor bugfixes (IPv6, bridges):
1756 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
1757 bugfix on 0.2.8.2-alpha.
1758 - Tor now sets IPv6 address in the routerstatus as well as in the
1759 router descriptors when updating addresses for a bridge. Closes
1760 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
1762 o Minor bugfixes (linux seccomp2 sandbox):
1763 - When running with the sandbox enabled, reload configuration files
1764 correctly even when %include was used. Previously we would crash.
1765 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
1767 o Minor bugfixes (memory leaks):
1768 - Avoid possible at-exit memory leaks related to use of Libevent's
1769 event_base_once() function. (This function tends to leak memory if
1770 the event_base is closed before the event fires.) Fixes bug 24584;
1771 bugfix on 0.2.8.1-alpha.
1772 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
1775 o Minor bugfixes (OSX):
1776 - Don't exit the Tor process if setrlimit() fails to change the file
1777 limit (which can happen sometimes on some versions of OSX). Fixes
1778 bug 21074; bugfix on 0.0.9pre5.
1780 o Minor bugfixes (performance, fragile-hardening):
1781 - Improve the performance of our consensus-diff application code
1782 when Tor is built with the --enable-fragile-hardening option set.
1783 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1785 o Minor bugfixes (performance, timeouts):
1786 - Consider circuits for timeout as soon as they complete a hop. This
1787 is more accurate than applying the timeout in
1788 circuit_expire_building() because that function is only called
1789 once per second, which is now too slow for typical timeouts on the
1790 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
1791 - Use onion service circuits (and other circuits longer than 3 hops)
1792 to calculate a circuit build timeout. Previously, Tor only
1793 calculated its build timeout based on circuits that planned to be
1794 exactly 3 hops long. With this change, we include measurements
1795 from all circuits at the point where they complete their third
1796 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
1798 o Minor bugfixes (testing):
1799 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
1800 bugfix on 0.2.3.1-alpha.
1801 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
1802 25005; bugfix on 0.3.2.7-rc.
1804 o Code simplification and refactoring:
1805 - Remove /usr/athena from search path in configure.ac. Closes
1807 - Remove duplicate code in node_has_curve25519_onion_key() and
1808 node_get_curve25519_onion_key(), and add a check for a zero
1809 microdesc curve25519 onion key. Closes ticket 23966, patch by
1810 "aruna1234" and teor.
1811 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
1812 memory allocations with large numbers of OR connections (e.g.
1813 relays). Closes ticket 24119.
1814 - Separate the function that deletes ephemeral files when Tor
1816 - Small changes to Tor's buf_t API to make it suitable for use as a
1817 general-purpose safe string constructor. Closes ticket 22342.
1818 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
1819 avoid source code identifier confusion. Closes ticket 24467.
1820 - The tor_git_revision[] constant no longer needs to be redeclared
1821 by everything that links against the rest of Tor. Done as part of
1822 ticket 23845, to simplify our external API.
1823 - We make extend_info_from_node() use node_get_curve25519_onion_key()
1824 introduced in ticket 23577 to access the curve25519 public keys
1825 rather than accessing it directly. Closes ticket 23760. Patch by
1827 - Add a function to log channels' scheduler state changes to aid
1828 debugging efforts. Closes ticket 24531.
1831 - Add documentation on how to build tor with Rust dependencies
1832 without having to be online. Closes ticket 22907; bugfix
1834 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
1835 traffic. Closes ticket 24318.
1836 - Document that OutboundBindAddress doesn't apply to DNS requests.
1837 Closes ticket 22145. Patch from Aruna Maurya.
1838 - Document that operators who run more than one relay or bridge are
1839 expected to set MyFamily and ContactInfo correctly. Closes
1842 o Code simplification and refactoring (channels):
1843 - Remove the incoming and outgoing channel queues. These were never
1844 used, but still took up a step in our fast path.
1845 - The majority of the channel unit tests have been rewritten and the
1846 code coverage has now been raised to 83.6% for channel.c. Closes
1848 - Remove other dead code from the channel subsystem: All together,
1849 this cleanup has removed more than 1500 lines of code overall and
1850 adding very little except for unit test.
1852 o Code simplification and refactoring (circuit rendezvous):
1853 - Split the client-side rendezvous circuit lookup into two
1854 functions: one that returns only established circuits and another
1855 that returns all kinds of circuits. Closes ticket 23459.
1857 o Code simplification and refactoring (controller):
1858 - Make most of the variables in networkstatus_getinfo_by_purpose()
1859 const. Implements ticket 24489.
1862 Changes in version 0.3.2.9 - 2018-01-09
1863 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
1865 The 0.3.2 series includes our long-anticipated new onion service
1866 design, with numerous security features. (For more information, see
1867 our blog post at https://blog.torproject.org/fall-harvest.) We also
1868 have a new circuit scheduler algorithm for improved performance on
1869 relays everywhere (see https://blog.torproject.org/kist-and-tell),
1870 along with many smaller features and bugfixes.
1872 Per our stable release policy, we plan to support each stable release
1873 series for at least the next nine months, or for three months after
1874 the first stable release of the next series: whichever is longer. If
1875 you need a release with long-term support, we recommend that you stay
1876 with the 0.2.9 series.
1878 Below is a list of the changes since 0.3.2.8-rc. For a list of all
1879 changes since 0.3.1, see the ReleaseNotes file.
1881 o Minor features (fallback directory mirrors):
1882 - The fallback directory list has been re-generated based on the
1883 current status of the network. Tor uses fallback directories to
1884 bootstrap when it doesn't yet have up-to-date directory
1885 information. Closes ticket 24801.
1886 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1887 prefer to bootstrap from fallback directory mirrors. This is a
1888 follow-up to 24679, which removed weights from the default
1889 fallbacks. Implements ticket 24681.
1891 o Minor features (geoip):
1892 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
1895 o Minor bugfixes (address selection):
1896 - When the fascist_firewall_choose_address_ functions don't find a
1897 reachable address, set the returned address to the null address
1898 and port. This is a precautionary measure, because some callers do
1899 not check the return value. Fixes bug 24736; bugfix
1902 o Minor bugfixes (compilation):
1903 - Resolve a few shadowed-variable warnings in the onion service
1904 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
1906 o Minor bugfixes (portability, msvc):
1907 - Fix a bug in the bit-counting parts of our timing-wheel code on
1908 MSVC. (Note that MSVC is still not a supported build platform, due
1909 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
1913 Changes in version 0.3.2.8-rc - 2017-12-21
1914 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
1915 schedulers that had led servers under heavy load to overload their
1916 outgoing connections. All relay operators running earlier 0.3.2.x
1917 versions should upgrade. This version also includes a mitigation for
1918 over-full DESTROY queues leading to out-of-memory conditions: if it
1919 works, we will soon backport it to earlier release series.
1921 This is the second release candidate in the 0.3.2 series. If we find
1922 no new bugs or regression here, then the first stable 0.3.2 release
1923 will be nearly identical to this.
1925 o Major bugfixes (KIST, scheduler):
1926 - The KIST scheduler did not correctly account for data already
1927 enqueued in each connection's send socket buffer, particularly in
1928 cases when the TCP/IP congestion window was reduced between
1929 scheduler calls. This situation lead to excessive per-connection
1930 buffering in the kernel, and a potential memory DoS. Fixes bug
1931 24665; bugfix on 0.3.2.1-alpha.
1933 o Minor features (geoip):
1934 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
1937 o Minor bugfixes (hidden service v3):
1938 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
1939 the probability of reaching a service for a client missing
1940 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
1942 o Minor bugfixes (memory usage):
1943 - When queuing DESTROY cells on a channel, only queue the circuit-id
1944 and reason fields: not the entire 514-byte cell. This fix should
1945 help mitigate any bugs or attacks that fill up these queues, and
1946 free more RAM for other uses. Fixes bug 24666; bugfix
1949 o Minor bugfixes (scheduler, KIST):
1950 - Use a sane write limit for KISTLite when writing onto a connection
1951 buffer instead of using INT_MAX and shoving as much as it can.
1952 Because the OOM handler cleans up circuit queues, we are better
1953 off at keeping them in that queue instead of the connection's
1954 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
1957 Changes in version 0.3.2.7-rc - 2017-12-14
1958 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
1959 including some that could affect reliability or correctness.
1961 This is the first release candidate in the 0.3.2 series. If we find no
1962 new bugs or regression here, then the first stable 0.3.2. release will
1963 be nearly identical to this.
1965 o Major bugfixes (circuit prediction):
1966 - Fix circuit prediction logic so that a client doesn't treat a port
1967 as being "handled" by a circuit if that circuit already has
1968 isolation settings on it. This change should make Tor clients more
1969 responsive by improving their chances of having a pre-created
1970 circuit ready for use when a request arrives. Fixes bug 18859;
1971 bugfix on 0.2.3.3-alpha.
1973 o Minor features (logging):
1974 - Provide better warnings when the getrandom() syscall fails. Closes
1977 o Minor features (portability):
1978 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
1979 (It doesn't yet work with the sandbox enabled.) Closes
1982 o Minor bugfixes (bridge clients, bootstrap):
1983 - Retry directory downloads when we get our first bridge descriptor
1984 during bootstrap or while reconnecting to the network. Keep
1985 retrying every time we get a bridge descriptor, until we have a
1986 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
1987 - Stop delaying bridge descriptor fetches when we have cached bridge
1988 descriptors. Instead, only delay bridge descriptor fetches when we
1989 have at least one reachable bridge. Fixes part of bug 24367;
1990 bugfix on 0.2.0.3-alpha.
1991 - Stop delaying directory fetches when we have cached bridge
1992 descriptors. Instead, only delay bridge descriptor fetches when
1993 all our bridges are definitely unreachable. Fixes part of bug
1994 24367; bugfix on 0.2.0.3-alpha.
1996 o Minor bugfixes (compilation):
1997 - Fix a signed/unsigned comparison warning introduced by our fix to
1998 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
2000 o Minor bugfixes (correctness):
2001 - Fix several places in our codebase where a C compiler would be
2002 likely to eliminate a check, based on assuming that undefined
2003 behavior had not happened elsewhere in the code. These cases are
2004 usually a sign of redundant checking or dubious arithmetic. Found
2005 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
2006 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
2009 o Minor bugfixes (onion service v3):
2010 - Fix a race where an onion service would launch a new intro circuit
2011 after closing an old one, but fail to register it before freeing
2012 the previously closed circuit. This bug was making the service
2013 unable to find the established intro circuit and thus not upload
2014 its descriptor, thus making a service unavailable for up to 24
2015 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
2017 o Minor bugfixes (scheduler, KIST):
2018 - Properly set the scheduler state of an unopened channel in the
2019 KIST scheduler main loop. This prevents a harmless but annoying
2020 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
2021 - Avoid a possible integer overflow when computing the available
2022 space on the TCP buffer of a channel. This had no security
2023 implications; but could make KIST allow too many cells on a
2024 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
2025 - Downgrade to "info" a harmless warning about the monotonic time
2026 moving backwards: This can happen on platform not supporting
2027 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
2030 Changes in version 0.3.2.6-alpha - 2017-12-01
2031 This version of Tor is the latest in the 0.3.2 alpha series. It
2032 includes fixes for several important security issues. All Tor users
2033 should upgrade to this release, or to one of the other releases coming
2036 o Major bugfixes (security):
2037 - Fix a denial of service bug where an attacker could use a
2038 malformed directory object to cause a Tor instance to pause while
2039 OpenSSL would try to read a passphrase from the terminal. (Tor
2040 instances run without a terminal, which is the case for most Tor
2041 packages, are not impacted.) Fixes bug 24246; bugfix on every
2042 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2043 Found by OSS-Fuzz as testcase 6360145429790720.
2044 - Fix a denial of service issue where an attacker could crash a
2045 directory authority using a malformed router descriptor. Fixes bug
2046 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2048 - When checking for replays in the INTRODUCE1 cell data for a
2049 (legacy) onion service, correctly detect replays in the RSA-
2050 encrypted part of the cell. We were previously checking for
2051 replays on the entire cell, but those can be circumvented due to
2052 the malleability of Tor's legacy hybrid encryption. This fix helps
2053 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2054 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2057 o Major bugfixes (security, onion service v2):
2058 - Fix a use-after-free error that could crash v2 Tor onion services
2059 when they failed to open circuits while expiring introduction
2060 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2061 also tracked as TROVE-2017-013 and CVE-2017-8823.
2063 o Major bugfixes (security, relay):
2064 - When running as a relay, make sure that we never build a path
2065 through ourselves, even in the case where we have somehow lost the
2066 version of our descriptor appearing in the consensus. Fixes part
2067 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2068 as TROVE-2017-012 and CVE-2017-8822.
2069 - When running as a relay, make sure that we never choose ourselves
2070 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2071 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2073 o Minor feature (relay statistics):
2074 - Change relay bandwidth reporting stats interval from 4 hours to 24
2075 hours in order to reduce the efficiency of guard discovery
2076 attacks. Fixes ticket 23856.
2078 o Minor features (directory authority):
2079 - Add an IPv6 address for the "bastet" directory authority. Closes
2082 o Minor bugfixes (client):
2083 - By default, do not enable storage of client-side DNS values. These
2084 values were unused by default previously, but they should not have
2085 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
2088 Changes in version 0.3.1.9 - 2017-12-01:
2089 Tor 0.3.1.9 backports important security and stability fixes from the
2090 0.3.2 development series. All Tor users should upgrade to this
2091 release, or to another of the releases coming out today.
2093 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2094 - Fix a denial of service bug where an attacker could use a
2095 malformed directory object to cause a Tor instance to pause while
2096 OpenSSL would try to read a passphrase from the terminal. (Tor
2097 instances run without a terminal, which is the case for most Tor
2098 packages, are not impacted.) Fixes bug 24246; bugfix on every
2099 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2100 Found by OSS-Fuzz as testcase 6360145429790720.
2101 - Fix a denial of service issue where an attacker could crash a
2102 directory authority using a malformed router descriptor. Fixes bug
2103 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2105 - When checking for replays in the INTRODUCE1 cell data for a
2106 (legacy) onion service, correctly detect replays in the RSA-
2107 encrypted part of the cell. We were previously checking for
2108 replays on the entire cell, but those can be circumvented due to
2109 the malleability of Tor's legacy hybrid encryption. This fix helps
2110 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2111 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2114 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2115 - Fix a use-after-free error that could crash v2 Tor onion services
2116 when they failed to open circuits while expiring introduction
2117 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2118 also tracked as TROVE-2017-013 and CVE-2017-8823.
2120 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2121 - When running as a relay, make sure that we never build a path
2122 through ourselves, even in the case where we have somehow lost the
2123 version of our descriptor appearing in the consensus. Fixes part
2124 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2125 as TROVE-2017-012 and CVE-2017-8822.
2126 - When running as a relay, make sure that we never choose ourselves
2127 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2128 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2130 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2131 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2132 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2133 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2134 identifying and finding a workaround to this bug and to Moritz,
2135 Arthur Edelstein, and Roger for helping to track it down and
2138 o Minor features (bridge):
2139 - Bridges now include notice in their descriptors that they are
2140 bridges, and notice of their distribution status, based on their
2141 publication settings. Implements ticket 18329. For more fine-
2142 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2145 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2146 - Add an IPv6 address for the "bastet" directory authority. Closes
2149 o Minor features (geoip):
2150 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2153 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2154 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2155 relays, to prevent spurious address resolutions and descriptor
2156 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2157 bugfix on in 0.2.8.1-alpha.
2159 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2160 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2161 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2163 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2164 - When a circuit is marked for close, do not attempt to package any
2165 cells for channels on that circuit. Previously, we would detect
2166 this condition lower in the call stack, when we noticed that the
2167 circuit had no attached channel, and log an annoying message.
2168 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2170 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
2171 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2172 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2175 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2176 - Avoid a crash when transitioning from client mode to bridge mode.
2177 Previously, we would launch the worker threads whenever our
2178 "public server" mode changed, but not when our "server" mode
2179 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2182 Changes in version 0.3.0.13 - 2017-12-01
2183 Tor 0.3.0.13 backports important security and stability bugfixes from
2184 later Tor releases. All Tor users should upgrade to this release, or
2185 to another of the releases coming out today.
2187 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
2188 2018. If you need a release with long-term support, please stick with
2189 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2191 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2192 - Fix a denial of service bug where an attacker could use a
2193 malformed directory object to cause a Tor instance to pause while
2194 OpenSSL would try to read a passphrase from the terminal. (Tor
2195 instances run without a terminal, which is the case for most Tor
2196 packages, are not impacted.) Fixes bug 24246; bugfix on every
2197 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2198 Found by OSS-Fuzz as testcase 6360145429790720.
2199 - Fix a denial of service issue where an attacker could crash a
2200 directory authority using a malformed router descriptor. Fixes bug
2201 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2203 - When checking for replays in the INTRODUCE1 cell data for a
2204 (legacy) onion service, correctly detect replays in the RSA-
2205 encrypted part of the cell. We were previously checking for
2206 replays on the entire cell, but those can be circumvented due to
2207 the malleability of Tor's legacy hybrid encryption. This fix helps
2208 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2209 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2212 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2213 - Fix a use-after-free error that could crash v2 Tor onion services
2214 when they failed to open circuits while expiring introduction
2215 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2216 also tracked as TROVE-2017-013 and CVE-2017-8823.
2218 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2219 - When running as a relay, make sure that we never build a path
2220 through ourselves, even in the case where we have somehow lost the
2221 version of our descriptor appearing in the consensus. Fixes part
2222 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2223 as TROVE-2017-012 and CVE-2017-8822.
2224 - When running as a relay, make sure that we never choose ourselves
2225 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2226 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2228 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2229 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2230 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2231 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2232 identifying and finding a workaround to this bug and to Moritz,
2233 Arthur Edelstein, and Roger for helping to track it down and
2236 o Minor features (security, windows, backport from 0.3.1.1-alpha):
2237 - Enable a couple of pieces of Windows hardening: one
2238 (HeapEnableTerminationOnCorruption) that has been on-by-default
2239 since Windows 8, and unavailable before Windows 7; and one
2240 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2241 affect us, but shouldn't do any harm. Closes ticket 21953.
2243 o Minor features (bridge, backport from 0.3.1.9):
2244 - Bridges now include notice in their descriptors that they are
2245 bridges, and notice of their distribution status, based on their
2246 publication settings. Implements ticket 18329. For more fine-
2247 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2250 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2251 - Add an IPv6 address for the "bastet" directory authority. Closes
2254 o Minor features (geoip):
2255 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2258 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2259 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2260 relays, to prevent spurious address resolutions and descriptor
2261 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2262 bugfix on in 0.2.8.1-alpha.
2264 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2265 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2266 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2268 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2269 - When a circuit is marked for close, do not attempt to package any
2270 cells for channels on that circuit. Previously, we would detect
2271 this condition lower in the call stack, when we noticed that the
2272 circuit had no attached channel, and log an annoying message.
2273 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2275 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2276 - Avoid a crash when transitioning from client mode to bridge mode.
2277 Previously, we would launch the worker threads whenever our
2278 "public server" mode changed, but not when our "server" mode
2279 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2281 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2282 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2283 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2286 Changes in version 0.2.9.14 - 2017-12-01
2287 Tor 0.3.0.13 backports important security and stability bugfixes from
2288 later Tor releases. All Tor users should upgrade to this release, or
2289 to another of the releases coming out today.
2291 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2292 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2293 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2294 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2295 identifying and finding a workaround to this bug and to Moritz,
2296 Arthur Edelstein, and Roger for helping to track it down and
2299 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2300 - Fix a denial of service bug where an attacker could use a
2301 malformed directory object to cause a Tor instance to pause while
2302 OpenSSL would try to read a passphrase from the terminal. (Tor
2303 instances run without a terminal, which is the case for most Tor
2304 packages, are not impacted.) Fixes bug 24246; bugfix on every
2305 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2306 Found by OSS-Fuzz as testcase 6360145429790720.
2307 - Fix a denial of service issue where an attacker could crash a
2308 directory authority using a malformed router descriptor. Fixes bug
2309 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2311 - When checking for replays in the INTRODUCE1 cell data for a
2312 (legacy) onion service, correctly detect replays in the RSA-
2313 encrypted part of the cell. We were previously checking for
2314 replays on the entire cell, but those can be circumvented due to
2315 the malleability of Tor's legacy hybrid encryption. This fix helps
2316 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2317 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2320 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2321 - Fix a use-after-free error that could crash v2 Tor onion services
2322 when they failed to open circuits while expiring introduction
2323 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2324 also tracked as TROVE-2017-013 and CVE-2017-8823.
2326 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2327 - When running as a relay, make sure that we never build a path
2328 through ourselves, even in the case where we have somehow lost the
2329 version of our descriptor appearing in the consensus. Fixes part
2330 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2331 as TROVE-2017-012 and CVE-2017-8822.
2333 o Minor features (bridge, backport from 0.3.1.9):
2334 - Bridges now include notice in their descriptors that they are
2335 bridges, and notice of their distribution status, based on their
2336 publication settings. Implements ticket 18329. For more fine-
2337 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2340 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2341 - Add an IPv6 address for the "bastet" directory authority. Closes
2344 o Minor features (geoip):
2345 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2348 o Minor features (security, windows, backport from 0.3.1.1-alpha):
2349 - Enable a couple of pieces of Windows hardening: one
2350 (HeapEnableTerminationOnCorruption) that has been on-by-default
2351 since Windows 8, and unavailable before Windows 7; and one
2352 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2353 affect us, but shouldn't do any harm. Closes ticket 21953.
2355 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2356 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2357 relays, to prevent spurious address resolutions and descriptor
2358 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2359 bugfix on in 0.2.8.1-alpha.
2361 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2362 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2363 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2365 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2366 - When a circuit is marked for close, do not attempt to package any
2367 cells for channels on that circuit. Previously, we would detect
2368 this condition lower in the call stack, when we noticed that the
2369 circuit had no attached channel, and log an annoying message.
2370 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2372 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2373 - Avoid a crash when transitioning from client mode to bridge mode.
2374 Previously, we would launch the worker threads whenever our
2375 "public server" mode changed, but not when our "server" mode
2376 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2378 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2379 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2380 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2383 Changes in version 0.2.8.17 - 2017-12-01
2384 Tor 0.2.8.17 backports important security and stability bugfixes from
2385 later Tor releases. All Tor users should upgrade to this release, or
2386 to another of the releases coming out today.
2388 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
2389 2018. If you need a release with long-term support, please upgrade with
2390 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2392 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2393 - Fix a denial of service bug where an attacker could use a
2394 malformed directory object to cause a Tor instance to pause while
2395 OpenSSL would try to read a passphrase from the terminal. (Tor
2396 instances run without a terminal, which is the case for most Tor
2397 packages, are not impacted.) Fixes bug 24246; bugfix on every
2398 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2399 Found by OSS-Fuzz as testcase 6360145429790720.
2400 - When checking for replays in the INTRODUCE1 cell data for a
2401 (legacy) onion service, correctly detect replays in the RSA-
2402 encrypted part of the cell. We were previously checking for
2403 replays on the entire cell, but those can be circumvented due to
2404 the malleability of Tor's legacy hybrid encryption. This fix helps
2405 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2406 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2409 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2410 - Fix a use-after-free error that could crash v2 Tor onion services
2411 when they failed to open circuits while expiring introduction
2412 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2413 also tracked as TROVE-2017-013 and CVE-2017-8823.
2415 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2416 - When running as a relay, make sure that we never build a path through
2417 ourselves, even in the case where we have somehow lost the version of
2418 our descriptor appearing in the consensus. Fixes part of bug 21534;
2419 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
2422 o Minor features (bridge, backport from 0.3.1.9):
2423 - Bridges now include notice in their descriptors that they are
2424 bridges, and notice of their distribution status, based on their
2425 publication settings. Implements ticket 18329. For more fine-
2426 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2429 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2430 - Add an IPv6 address for the "bastet" directory authority. Closes
2433 o Minor features (geoip):
2434 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2437 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2438 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2439 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2442 Changes in version 0.2.5.16 - 2017-12-01
2443 Tor 0.2.5.13 backports important security and stability bugfixes from
2444 later Tor releases. All Tor users should upgrade to this release, or
2445 to another of the releases coming out today.
2447 Note: the Tor 0.2.5 series will no longer be supported after 1 May
2448 2018. If you need a release with long-term support, please upgrade to
2449 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2451 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2452 - Fix a denial of service bug where an attacker could use a
2453 malformed directory object to cause a Tor instance to pause while
2454 OpenSSL would try to read a passphrase from the terminal. (Tor
2455 instances run without a terminal, which is the case for most Tor
2456 packages, are not impacted.) Fixes bug 24246; bugfix on every
2457 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2458 Found by OSS-Fuzz as testcase 6360145429790720.
2459 - When checking for replays in the INTRODUCE1 cell data for a
2460 (legacy) onion service, correctly detect replays in the RSA-
2461 encrypted part of the cell. We were previously checking for
2462 replays on the entire cell, but those can be circumvented due to
2463 the malleability of Tor's legacy hybrid encryption. This fix helps
2464 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2465 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2468 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2469 - When running as a relay, make sure that we never build a path
2470 through ourselves, even in the case where we have somehow lost the
2471 version of our descriptor appearing in the consensus. Fixes part
2472 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2473 as TROVE-2017-012 and CVE-2017-8822.
2475 o Minor features (bridge, backport from 0.3.1.9):
2476 - Bridges now include notice in their descriptors that they are
2477 bridges, and notice of their distribution status, based on their
2478 publication settings. Implements ticket 18329. For more fine-
2479 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2482 o Minor features (geoip):
2483 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2487 Changes in version 0.3.2.5-alpha - 2017-11-22
2488 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
2489 fixes several stability and reliability bugs, including a fix for
2490 intermittent bootstrapping failures that some people have been seeing
2491 since the 0.3.0.x series.
2493 Please test this alpha out -- many of these fixes will soon be
2494 backported to stable Tor versions if no additional bugs are found
2497 o Major bugfixes (bootstrapping):
2498 - Fetch descriptors aggressively whenever we lack enough to build
2499 circuits, regardless of how many descriptors we are missing.
2500 Previously, we would delay launching the fetch when we had fewer
2501 than 15 missing descriptors, even if some of those descriptors
2502 were blocking circuits from building. Fixes bug 23985; bugfix on
2503 0.1.1.11-alpha. The effects of this bug became worse in
2504 0.3.0.3-alpha, when we began treating missing descriptors from our
2505 primary guards as a reason to delay circuits.
2506 - Don't try fetching microdescriptors from relays that have failed
2507 to deliver them in the past. Fixes bug 23817; bugfix
2510 o Minor features (directory authority):
2511 - Make the "Exit" flag assignment only depend on whether the exit
2512 policy allows connections to ports 80 and 443. Previously relays
2513 would get the Exit flag if they allowed connections to one of
2514 these ports and also port 6667. Resolves ticket 23637.
2516 o Minor features (geoip):
2517 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2520 o Minor features (linux seccomp2 sandbox):
2521 - Update the sandbox rules so that they should now work correctly
2522 with Glibc 2.26. Closes ticket 24315.
2524 o Minor features (logging):
2525 - Downgrade a pair of log messages that could occur when an exit's
2526 resolver gave us an unusual (but not forbidden) response. Closes
2528 - Improve the message we log when re-enabling circuit build timeouts
2529 after having received a consensus. Closes ticket 20963.
2531 o Minor bugfixes (compilation):
2532 - Fix a memory leak warning in one of the libevent-related
2533 configuration tests that could occur when manually specifying
2534 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
2535 Found and patched by Alex Xu.
2536 - When detecting OpenSSL on Windows from our configure script, make
2537 sure to try linking with the ws2_32 library. Fixes bug 23783;
2538 bugfix on 0.3.2.2-alpha.
2540 o Minor bugfixes (control port, linux seccomp2 sandbox):
2541 - Avoid a crash when attempting to use the seccomp2 sandbox together
2542 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
2545 o Minor bugfixes (control port, onion services):
2546 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
2547 HS_DESC event when a service is not able to upload a descriptor.
2548 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
2550 o Minor bugfixes (directory cache):
2551 - Recover better from empty or corrupt files in the consensus cache
2552 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
2553 - When a consensus diff calculation is only partially successful,
2554 only record the successful parts as having succeeded. Partial
2555 success can happen if (for example) one compression method fails
2556 but the others succeed. Previously we misrecorded all the
2557 calculations as having succeeded, which would later cause a
2558 nonfatal assertion failure. Fixes bug 24086; bugfix
2561 o Minor bugfixes (logging):
2562 - Only log once if we notice that KIST support is gone. Fixes bug
2563 24158; bugfix on 0.3.2.1-alpha.
2564 - Suppress a log notice when relay descriptors arrive. We already
2565 have a bootstrap progress for this so no need to log notice
2566 everytime tor receives relay descriptors. Microdescriptors behave
2567 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
2569 o Minor bugfixes (network layer):
2570 - When closing a connection via close_connection_immediately(), we
2571 mark it as "not blocked on bandwidth", to prevent later calls from
2572 trying to unblock it, and give it permission to read. This fixes a
2573 backtrace warning that can happen on relays under various
2574 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
2576 o Minor bugfixes (onion services):
2577 - The introduction circuit was being timed out too quickly while
2578 waiting for the rendezvous circuit to complete. Keep the intro
2579 circuit around longer instead of timing out and reopening new ones
2580 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
2581 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2582 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2584 - Silence a warning about failed v3 onion descriptor uploads that
2585 can happen naturally under certain edge cases. Fixes part of bug
2586 23662; bugfix on 0.3.2.1-alpha.
2588 o Minor bugfixes (tests):
2589 - Fix a memory leak in one of the bridge-distribution test cases.
2590 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
2591 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
2592 to correctly handle cases where a caller gives it an RSA key of
2593 under 160 bits. (This is not actually a bug in Tor itself, but
2594 rather in our fuzzing code.) Fixes bug 24247; bugfix on
2595 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
2598 - Add notes in man page regarding OS support for the various
2599 scheduler types. Attempt to use less jargon in the scheduler
2600 section. Closes ticket 24254.
2603 Changes in version 0.3.2.4-alpha - 2017-11-08
2604 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
2605 It fixes several stability and reliability bugs, especially including
2606 a major reliability issue that has been plaguing fast exit relays in
2609 o Major bugfixes (exit relays, DNS):
2610 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2611 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2612 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2613 identifying and finding a workaround to this bug and to Moritz,
2614 Arthur Edelstein, and Roger for helping to track it down and
2617 o Major bugfixes (scheduler, channel):
2618 - Stop processing scheduled channels if they closed while flushing
2619 cells. This can happen if the write on the connection fails
2620 leading to the channel being closed while in the scheduler loop.
2621 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
2623 o Minor features (logging, scheduler):
2624 - Introduce a SCHED_BUG() function to log extra information about
2625 the scheduler state if we ever catch a bug in the scheduler.
2626 Closes ticket 23753.
2628 o Minor features (removed deprecations):
2629 - The ClientDNSRejectInternalAddresses flag can once again be set in
2630 non-testing Tor networks, so long as they do not use the default
2631 directory authorities. This change also removes the deprecation of
2632 this flag from 0.2.9.2-alpha. Closes ticket 21031.
2634 o Minor features (testing):
2635 - Our fuzzing tests now test the encrypted portions of v3 onion
2636 service descriptors. Implements more of 21509.
2638 o Minor bugfixes (directory client):
2639 - On failure to download directory information, delay retry attempts
2640 by a random amount based on the "decorrelated jitter" algorithm.
2641 Our previous delay algorithm tended to produce extra-long delays
2642 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
2644 o Minor bugfixes (IPv6, v3 single onion services):
2645 - Remove buggy code for IPv6-only v3 single onion services, and
2646 reject attempts to configure them. This release supports IPv4,
2647 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
2648 stack v3 single onion services. Fixes bug 23820; bugfix
2651 o Minor bugfixes (logging, relay):
2652 - Give only a protocol warning when the ed25519 key is not
2653 consistent between the descriptor and microdescriptor of a relay.
2654 This can happen, for instance, if the relay has been flagged
2655 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
2657 o Minor bugfixes (manpage, onion service):
2658 - Document that the HiddenServiceNumIntroductionPoints option is
2659 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
2660 bugfix on 0.3.2.1-alpha.
2662 o Minor bugfixes (memory leaks):
2663 - Fix a minor memory leak at exit in the KIST scheduler. This bug
2664 should have no user-visible impact. Fixes bug 23774; bugfix
2666 - Fix a memory leak when decrypting a badly formatted v3 onion
2667 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
2668 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
2670 o Minor bugfixes (onion services):
2671 - Cache some needed onion service client information instead of
2672 constantly computing it over and over again. Fixes bug 23623;
2673 bugfix on 0.3.2.1-alpha.
2674 - Properly retry HSv3 descriptor fetches when missing required
2675 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
2677 o Minor bugfixes (path selection):
2678 - When selecting relays by bandwidth, avoid a rounding error that
2679 could sometimes cause load to be imbalanced incorrectly.
2680 Previously, we would always round upwards; now, we round towards
2681 the nearest integer. This had the biggest effect when a relay's
2682 weight adjustments should have given it weight 0, but it got
2683 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
2684 - When calculating the fraction of nodes that have descriptors, and
2685 all nodes in the network have zero bandwidths, count the number of
2686 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
2687 - Actually log the total bandwidth in compute_weighted_bandwidths().
2688 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
2690 o Minor bugfixes (relay, crash):
2691 - Avoid a crash when transitioning from client mode to bridge mode.
2692 Previously, we would launch the worker threads whenever our
2693 "public server" mode changed, but not when our "server" mode
2694 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2696 o Minor bugfixes (testing):
2697 - Fix a spurious fuzzing-only use of an uninitialized value. Found
2698 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
2699 - Test that IPv6-only clients can use microdescriptors when running
2700 "make test-network-all". Requires chutney master 61c28b9 or later.
2701 Closes ticket 24109.
2704 Changes in version 0.3.2.3-alpha - 2017-10-27
2705 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
2706 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
2707 directory authority, Bastet.
2709 o Directory authority changes:
2710 - Add "Bastet" as a ninth directory authority to the default list.
2711 Closes ticket 23910.
2712 - The directory authority "Longclaw" has changed its IP address.
2713 Closes ticket 23592.
2715 o Minor features (bridge):
2716 - Bridge relays can now set the BridgeDistribution config option to
2717 add a "bridge-distribution-request" line to their bridge
2718 descriptor, which tells BridgeDB how they'd like their bridge
2719 address to be given out. (Note that as of Oct 2017, BridgeDB does
2720 not yet implement this feature.) As a side benefit, this feature
2721 provides a way to distinguish bridge descriptors from non-bridge
2722 descriptors. Implements tickets 18329.
2724 o Minor features (client, entry guards):
2725 - Improve log messages when missing descriptors for primary guards.
2726 Resolves ticket 23670.
2728 o Minor features (geoip):
2729 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2732 o Minor bugfixes (bridge):
2733 - Overwrite the bridge address earlier in the process of retrieving
2734 its descriptor, to make sure we reach it on the configured
2735 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
2737 o Minor bugfixes (documentation):
2738 - Document better how to read gcov, and what our gcov postprocessing
2739 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
2741 o Minor bugfixes (entry guards):
2742 - Tor now updates its guard state when it reads a consensus
2743 regardless of whether it's missing descriptors. That makes tor use
2744 its primary guards to fetch descriptors in some edge cases where
2745 it would previously have used fallback directories. Fixes bug
2746 23862; bugfix on 0.3.0.1-alpha.
2748 o Minor bugfixes (hidden service client):
2749 - When handling multiple SOCKS request for the same .onion address,
2750 only fetch the service descriptor once.
2751 - When a descriptor fetch fails with a non-recoverable error, close
2752 all pending SOCKS requests for that .onion. Fixes bug 23653;
2753 bugfix on 0.3.2.1-alpha.
2755 o Minor bugfixes (hidden service):
2756 - Always regenerate missing hidden service public key files. Prior
2757 to this, if the public key was deleted from disk, it wouldn't get
2758 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
2760 - Make sure that we have a usable ed25519 key when the intro point
2761 relay supports ed25519 link authentication. Fixes bug 24002;
2762 bugfix on 0.3.2.1-alpha.
2764 o Minor bugfixes (hidden service, v2):
2765 - When reloading configured hidden services, copy all information
2766 from the old service object. Previously, some data was omitted,
2767 causing delays in descriptor upload, and other bugs. Fixes bug
2768 23790; bugfix on 0.2.1.9-alpha.
2770 o Minor bugfixes (memory safety, defensive programming):
2771 - Clear the target address when node_get_prim_orport() returns
2772 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2774 o Minor bugfixes (relay):
2775 - Avoid a BUG warning when receiving a dubious CREATE cell while an
2776 option transition is in progress. Fixes bug 23952; bugfix
2779 o Minor bugfixes (testing):
2780 - Adjust the GitLab CI configuration to more closely match that of
2781 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
2782 - Prevent scripts/test/coverage from attempting to move gcov output
2783 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
2784 - When running unit tests as root, skip a test that would fail
2785 because it expects a permissions error. This affects some
2786 continuous integration setups. Fixes bug 23758; bugfix
2788 - Stop unconditionally mirroring the tor repository in GitLab CI.
2789 This prevented developers from enabling GitLab CI on master. Fixes
2790 bug 23755; bugfix on 0.3.2.2-alpha.
2791 - Fix the hidden service v3 descriptor decoding fuzzing to use the
2792 latest decoding API correctly. Fixes bug 21509; bugfix
2795 o Minor bugfixes (warnings):
2796 - When we get an HTTP request on a SOCKS port, tell the user about
2797 the new HTTPTunnelPort option. Previously, we would give a "Tor is
2798 not an HTTP Proxy" message, which stopped being true when
2799 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
2803 Changes in version 0.2.5.15 - 2017-10-25
2804 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
2805 series. It also adds a new directory authority, Bastet.
2807 Note: the Tor 0.2.5 series will no longer be supported after 1 May
2808 2018. If you need a release with long-term support, please upgrade to
2809 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2811 o Directory authority changes:
2812 - Add "Bastet" as a ninth directory authority to the default list.
2813 Closes ticket 23910.
2814 - The directory authority "Longclaw" has changed its IP address.
2815 Closes ticket 23592.
2817 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2818 - Avoid an assertion failure bug affecting our implementation of
2819 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2820 handling of "0xx" differs from what we had expected. Fixes bug
2821 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2823 o Minor features (geoip):
2824 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2827 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
2828 - Fix a memset() off the end of an array when packing cells. This
2829 bug should be harmless in practice, since the corrupted bytes are
2830 still in the same structure, and are always padding bytes,
2831 ignored, or immediately overwritten, depending on compiler
2832 behavior. Nevertheless, because the memset()'s purpose is to make
2833 sure that any other cell-handling bugs can't expose bytes to the
2834 network, we need to fix it. Fixes bug 22737; bugfix on
2835 0.2.4.11-alpha. Fixes CID 1401591.
2837 o Build features (backport from 0.3.1.5-alpha):
2838 - Tor's repository now includes a Travis Continuous Integration (CI)
2839 configuration file (.travis.yml). This is meant to help new
2840 developers and contributors who fork Tor to a Github repository be
2841 better able to test their changes, and understand what we expect
2842 to pass. To use this new build feature, you must fork Tor to your
2843 Github account, then go into the "Integrations" menu in the
2844 repository settings for your fork and enable Travis, then push
2845 your changes. Closes ticket 22636.
2848 Changes in version 0.2.8.16 - 2017-10-25
2849 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
2850 series, including a bugfix for a crash issue that had affected relays
2851 under memory pressure. It also adds a new directory authority, Bastet.
2853 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
2854 2018. If you need a release with long-term support, please stick with
2855 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2857 o Directory authority changes:
2858 - Add "Bastet" as a ninth directory authority to the default list.
2859 Closes ticket 23910.
2860 - The directory authority "Longclaw" has changed its IP address.
2861 Closes ticket 23592.
2863 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2864 - Fix a timing-based assertion failure that could occur when the
2865 circuit out-of-memory handler freed a connection's output buffer.
2866 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2868 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2869 - Remove longclaw's IPv6 address, as it will soon change. Authority
2870 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2871 3/8 directory authorities with IPv6 addresses, but there are also
2872 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2874 o Minor features (geoip):
2875 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2879 Changes in version 0.2.9.13 - 2017-10-25
2880 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
2881 series, including a bugfix for a crash issue that had affected relays
2882 under memory pressure. It also adds a new directory authority, Bastet.
2884 o Directory authority changes:
2885 - Add "Bastet" as a ninth directory authority to the default list.
2886 Closes ticket 23910.
2887 - The directory authority "Longclaw" has changed its IP address.
2888 Closes ticket 23592.
2890 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2891 - Fix a timing-based assertion failure that could occur when the
2892 circuit out-of-memory handler freed a connection's output buffer.
2893 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2895 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2896 - Remove longclaw's IPv6 address, as it will soon change. Authority
2897 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2898 3/8 directory authorities with IPv6 addresses, but there are also
2899 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2901 o Minor features (geoip):
2902 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2905 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
2906 - When a directory authority rejects a descriptor or extrainfo with
2907 a given digest, mark that digest as undownloadable, so that we do
2908 not attempt to download it again over and over. We previously
2909 tried to avoid downloading such descriptors by other means, but we
2910 didn't notice if we accidentally downloaded one anyway. This
2911 behavior became problematic in 0.2.7.2-alpha, when authorities
2912 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2915 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2916 - Clear the address when node_get_prim_orport() returns early.
2917 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2919 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
2920 - When running as a Windows service, set the ID of the main thread
2921 correctly. Failure to do so made us fail to send log messages to
2922 the controller in 0.2.1.16-rc, slowed down controller event
2923 delivery in 0.2.7.3-rc and later, and crash with an assertion
2924 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2925 Patch and diagnosis from "Vort".
2928 Changes in version 0.3.0.12 - 2017-10-25
2929 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
2930 series, including a bugfix for a crash issue that had affected relays
2931 under memory pressure. It also adds a new directory authority, Bastet.
2933 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
2934 2018. If you need a release with long-term support, please stick with
2935 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2937 o Directory authority changes:
2938 - Add "Bastet" as a ninth directory authority to the default list.
2939 Closes ticket 23910.
2940 - The directory authority "Longclaw" has changed its IP address.
2941 Closes ticket 23592.
2943 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2944 - Fix a timing-based assertion failure that could occur when the
2945 circuit out-of-memory handler freed a connection's output buffer.
2946 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
2948 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
2949 - Remove longclaw's IPv6 address, as it will soon change. Authority
2950 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
2951 3/8 directory authorities with IPv6 addresses, but there are also
2952 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
2954 o Minor features (geoip):
2955 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2958 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
2959 - When a directory authority rejects a descriptor or extrainfo with
2960 a given digest, mark that digest as undownloadable, so that we do
2961 not attempt to download it again over and over. We previously
2962 tried to avoid downloading such descriptors by other means, but we
2963 didn't notice if we accidentally downloaded one anyway. This
2964 behavior became problematic in 0.2.7.2-alpha, when authorities
2965 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2968 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
2969 - Avoid a possible double close of a circuit by the intro point on
2970 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
2971 bugfix on 0.3.0.1-alpha.
2973 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
2974 - Clear the address when node_get_prim_orport() returns early.
2975 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2977 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
2978 - When running as a Windows service, set the ID of the main thread
2979 correctly. Failure to do so made us fail to send log messages to
2980 the controller in 0.2.1.16-rc, slowed down controller event
2981 delivery in 0.2.7.3-rc and later, and crash with an assertion
2982 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2983 Patch and diagnosis from "Vort".
2986 Changes in version 0.3.1.8 - 2017-10-25
2987 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
2988 It includes several bugfixes, including a bugfix for a crash issue
2989 that had affected relays under memory pressure. It also adds
2990 a new directory authority, Bastet.
2992 o Directory authority changes:
2993 - Add "Bastet" as a ninth directory authority to the default list.
2994 Closes ticket 23910.
2995 - The directory authority "Longclaw" has changed its IP address.
2996 Closes ticket 23592.
2998 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
2999 - Fix a timing-based assertion failure that could occur when the
3000 circuit out-of-memory handler freed a connection's output buffer.
3001 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3003 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3004 - Remove longclaw's IPv6 address, as it will soon change. Authority
3005 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3006 3/8 directory authorities with IPv6 addresses, but there are also
3007 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3009 o Minor features (geoip):
3010 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3013 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
3014 - Fix a compilation warning when building with zstd support on
3015 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
3016 and fixed by Andreas Stieger.
3018 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
3019 - Handle a pathological case when decompressing Zstandard data when
3020 the output buffer size is zero. Fixes bug 23551; bugfix
3023 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
3024 - Remove the length limit on HTTP status lines that authorities can
3025 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
3027 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
3028 - Avoid a possible double close of a circuit by the intro point on
3029 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
3030 bugfix on 0.3.0.1-alpha.
3032 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
3033 - Clear the address when node_get_prim_orport() returns early.
3034 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
3036 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
3037 - Fix additional channelpadding unit test failures by using mocked
3038 time instead of actual time for all tests. Fixes bug 23608; bugfix
3042 Changes in version 0.3.2.2-alpha - 2017-09-29
3043 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
3044 release fixes several minor bugs in the new scheduler and next-
3045 generation onion services; both features were newly added in the 0.3.2
3046 series. Other fixes in this alpha include several fixes for non-fatal
3047 tracebacks which would appear in logs.
3049 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
3050 alpha does not contain any substantial new features. Minor features
3051 include better testing and logging.
3053 The following comprises the complete list of changes included
3056 o Major bugfixes (relay, crash, assertion failure):
3057 - Fix a timing-based assertion failure that could occur when the
3058 circuit out-of-memory handler freed a connection's output buffer.
3059 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3061 o Major bugfixes (scheduler):
3062 - If a channel is put into the scheduler's pending list, then it
3063 starts closing, and then if the scheduler runs before it finishes
3064 closing, the scheduler will get stuck trying to flush its cells
3065 while the lower layers refuse to cooperate. Fix that race
3066 condition by giving the scheduler an escape method. Fixes bug
3067 23676; bugfix on 0.3.2.1-alpha.
3069 o Minor features (build, compilation):
3070 - The "check-changes" feature is now part of the "make check" tests;
3071 we'll use it to try to prevent misformed changes files from
3072 accumulating. Closes ticket 23564.
3073 - Tor builds should now fail if there are any mismatches between the
3074 C type representing a configuration variable and the C type the
3075 data-driven parser uses to store a value there. Previously, we
3076 needed to check these by hand, which sometimes led to mistakes.
3077 Closes ticket 23643.
3079 o Minor features (directory authorities):
3080 - Remove longclaw's IPv6 address, as it will soon change. Authority
3081 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3082 3/8 directory authorities with IPv6 addresses, but there are also
3083 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3085 o Minor features (hidden service, circuit, logging):
3086 - Improve logging of many callsite in the circuit subsystem to print
3087 the circuit identifier(s).
3088 - Log when we cleanup an intro point from a service so we know when
3089 and for what reason it happened. Closes ticket 23604.
3091 o Minor features (logging):
3092 - Log more circuit information whenever we are about to try to
3093 package a relay cell on a circuit with a nonexistent n_chan.
3094 Attempt to diagnose ticket 8185.
3095 - Improve info-level log identification of particular circuits, to
3096 help with debugging. Closes ticket 23645.
3098 o Minor features (relay):
3099 - When choosing which circuits can be expired as unused, consider
3100 circuits from clients even if those clients used regular CREATE
3101 cells to make them; and do not consider circuits from relays even
3102 if they were made with CREATE_FAST. Part of ticket 22805.
3104 o Minor features (robustness):
3105 - Change several fatal assertions when flushing buffers into non-
3106 fatal assertions, to prevent any recurrence of 23690.
3108 o Minor features (spec conformance, bridge, diagnostic):
3109 - When handling the USERADDR command on an ExtOrPort, warn when the
3110 transports provides a USERADDR with no port. In a future version,
3111 USERADDR commands of this format may be rejected. Detects problems
3112 related to ticket 23080.
3114 o Minor features (testing):
3115 - Add a unit test to make sure that our own generated platform
3116 string will be accepted by directory authorities. Closes
3119 o Minor bugfixes (bootstrapping):
3120 - When warning about state file clock skew, report the correct
3121 direction for the detected skew. Fixes bug 23606; bugfix
3123 - Avoid an assertion failure when logging a state file clock skew
3124 very early in bootstrapping. Fixes bug 23607; bugfix
3127 o Minor bugfixes (build, compilation):
3128 - Fix a compilation warning when building with zstd support on
3129 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
3130 and fixed by Andreas Stieger.
3131 - When searching for OpenSSL, don't accept any OpenSSL library that
3132 lacks TLSv1_1_method(): Tor doesn't build with those versions.
3133 Additionally, look in /usr/local/opt/openssl, if it's present.
3134 These changes together repair the default build on OSX systems
3135 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
3137 o Minor bugfixes (compression):
3138 - Handle a pathological case when decompressing Zstandard data when
3139 the output buffer size is zero. Fixes bug 23551; bugfix
3142 o Minor bugfixes (documentation):
3143 - Fix manpage to not refer to the obsolete (and misspelled)
3144 UseEntryGuardsAsDirectoryGuards parameter in the description of
3145 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
3147 o Minor bugfixes (hidden service v3):
3148 - Don't log an assertion failure when we can't find the right
3149 information to extend to an introduction point. In rare cases,
3150 this could happen, causing a warning, even though tor would
3151 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
3152 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
3153 much bigger so the rendezvous point can't distinguish which hidden
3154 service protocol is being used. Fixes bug 23420; bugfix
3157 o Minor bugfixes (hidden service, relay):
3158 - Avoid a possible double close of a circuit by the intro point on
3159 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
3160 bugfix on 0.3.0.1-alpha.
3162 o Minor bugfixes (logging, relay shutdown, annoyance):
3163 - When a circuit is marked for close, do not attempt to package any
3164 cells for channels on that circuit. Previously, we would detect
3165 this condition lower in the call stack, when we noticed that the
3166 circuit had no attached channel, and log an annoying message.
3167 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
3169 o Minor bugfixes (scheduler):
3170 - When switching schedulers due to a consensus change, we didn't
3171 give the new scheduler a chance to react to the consensus. Fix
3172 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
3173 - Make the KISTSchedRunInterval option a non negative value. With
3174 this, the way to disable KIST through the consensus is to set it
3175 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
3176 - Only notice log the selected scheduler when we switch scheduler
3177 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
3178 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
3179 by a different tv_usec data type. Fixes bug 23575; bugfix
3181 - Make a hard exit if tor is unable to pick a scheduler which can
3182 happen if the user specifies a scheduler type that is not
3183 supported and not other types in Schedulers. Fixes bug 23581;
3184 bugfix on 0.3.2.1-alpha.
3185 - Properly initialize the scheduler last run time counter so it is
3186 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
3188 o Minor bugfixes (testing):
3189 - Capture and detect several "Result does not fit" warnings in unit
3190 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
3192 - Fix additional channelpadding unit test failures by using mocked
3193 time instead of actual time for all tests. Fixes bug 23608; bugfix
3195 - The removal of some old scheduler options caused some tests to
3196 fail on BSD systems. Assume current behavior is correct and make
3197 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
3199 o Code simplification and refactoring:
3200 - Remove various ways of testing circuits and connections for
3201 "clientness"; instead, favor channel_is_client(). Part of
3204 o Deprecated features:
3205 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
3206 now deprecated; they do not apply to relays, and they have had no
3207 effect on clients since 0.2.8.x. Closes ticket 19704.
3210 - HiddenServiceVersion man page entry wasn't mentioning the now
3211 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
3212 - Clarify that the Address option is entirely about setting an
3213 advertised IPv4 address. Closes ticket 18891.
3214 - Clarify the manpage's use of the term "address" to clarify what
3215 kind of address is intended. Closes ticket 21405.
3216 - Document that onion service subdomains are allowed, and ignored.
3217 Closes ticket 18736.
3220 Changes in version 0.3.2.1-alpha - 2017-09-18
3221 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
3222 includes support for our next-generation ("v3") onion service
3223 protocol, and adds a new circuit scheduler for more responsive
3224 forwarding decisions from relays. There are also numerous other small
3225 features and bugfixes here.
3227 Below are the changes since Tor 0.3.1.7.
3229 o Major feature (scheduler, channel):
3230 - Tor now uses new schedulers to decide which circuits should
3231 deliver cells first, in order to improve congestion at relays. The
3232 first type is called "KIST" ("Kernel Informed Socket Transport"),
3233 and is only available on Linux-like systems: it uses feedback from
3234 the kernel to prevent the kernel's TCP buffers from growing too
3235 full. The second new scheduler type is called "KISTLite": it
3236 behaves the same as KIST, but runs on systems without kernel
3237 support for inspecting TCP implementation details. The old
3238 scheduler is still available, under the name "Vanilla". To change
3239 the default scheduler preference order, use the new "Schedulers"
3240 option. (The default preference order is "KIST,KISTLite,Vanilla".)
3242 Matt Traudt implemented KIST, based on research by Rob Jansen,
3243 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
3244 more information, see the design paper at
3245 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
3246 followup implementation paper at https://arxiv.org/abs/1709.01044.
3247 Closes ticket 12541.
3249 o Major features (next-generation onion services):
3250 - Tor now supports the next-generation onion services protocol for
3251 clients and services! As part of this release, the core of
3252 proposal 224 has been implemented and is available for
3253 experimentation and testing by our users. This newer version of
3254 onion services ("v3") features many improvements over the legacy
3257 a) Better crypto (replaced SHA1/DH/RSA1024
3258 with SHA3/ed25519/curve25519)
3260 b) Improved directory protocol, leaking much less information to
3263 c) Improved directory protocol, with smaller surface for
3266 d) Better onion address security against impersonation.
3268 e) More extensible introduction/rendezvous protocol.
3270 f) A cleaner and more modular codebase.
3272 You can identify a next-generation onion address by its length:
3273 they are 56 characters long, as in
3274 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
3276 In the future, we will release more options and features for v3
3277 onion services, but we first need a testing period, so that the
3278 current codebase matures and becomes more robust. Planned features
3279 include: offline keys, advanced client authorization, improved
3280 guard algorithms, and statistics. For full details, see
3283 Legacy ("v2") onion services will still work for the foreseeable
3284 future, and will remain the default until this new codebase gets
3285 tested and hardened. Service operators who want to experiment with
3286 the new system can use the 'HiddenServiceVersion 3' torrc
3287 directive along with the regular onion service configuration
3288 options. We will publish a blog post about this new feature
3291 o Major bugfixes (usability, control port):
3292 - Report trusted clock skew indications as bootstrap errors, so
3293 controllers can more easily alert users when their clocks are
3294 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
3296 o Minor features (bug detection):
3297 - Log a warning message with a stack trace for any attempt to call
3298 get_options() during option validation. This pattern has caused
3299 subtle bugs in the past. Closes ticket 22281.
3301 o Minor features (client):
3302 - You can now use Tor as a tunneled HTTP proxy: use the new
3303 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
3304 requests. Closes ticket 22407.
3305 - Add an extra check to make sure that we always use the newer guard
3306 selection code for picking our guards. Closes ticket 22779.
3307 - When downloading (micro)descriptors, don't split the list into
3308 multiple requests unless we want at least 32 descriptors.
3309 Previously, we split at 4, not 32, which led to significant
3310 overhead in HTTP request size and degradation in compression
3311 performance. Closes ticket 23220.
3313 o Minor features (command line):
3314 - Add a new commandline option, --key-expiration, which prints when
3315 the current signing key is going to expire. Implements ticket
3316 17639; patch by Isis Lovecruft.
3318 o Minor features (control port):
3319 - If an application tries to use the control port as an HTTP proxy,
3320 respond with a meaningful "This is the Tor control port" message,
3321 and log the event. Closes ticket 1667. Patch from Ravi
3323 - Provide better error message for GETINFO desc/(id|name) when not
3324 fetching router descriptors. Closes ticket 5847. Patch by
3326 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
3327 whether Tor will try to download router descriptors and
3328 microdescriptors respectively. Closes ticket 22684.
3329 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
3330 so controllers can tell whether the geoip databases are loaded.
3331 Closes ticket 23237.
3332 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
3333 events. Closes ticket 19254. Patch by "DonnchaC".
3335 o Minor features (development support):
3336 - Developers can now generate a call-graph for Tor using the
3337 "calltool" python program, which post-processes object dumps. It
3338 should work okay on many Linux and OSX platforms, and might work
3339 elsewhere too. To run it, install calltool from
3340 https://gitweb.torproject.org/user/nickm/calltool.git and run
3341 "make callgraph". Closes ticket 19307.
3343 o Minor features (ed25519):
3344 - Add validation function to checks for torsion components in
3345 ed25519 public keys, used by prop224 client-side code. Closes
3346 ticket 22006. Math help by Ian Goldberg.
3348 o Minor features (exit relay, DNS):
3349 - Improve the clarity and safety of the log message from evdns when
3350 receiving an apparently spoofed DNS reply. Closes ticket 3056.
3352 o Minor features (integration, hardening):
3353 - Add a new NoExec option to prevent Tor from running other
3354 programs. When this option is set to 1, Tor will never try to run
3355 another program, regardless of the settings of
3356 PortForwardingHelper, ClientTransportPlugin, or
3357 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
3358 without restarting Tor. Closes ticket 22976.
3360 o Minor features (logging):
3361 - Improve the warning message for specifying a relay by nickname.
3362 The previous message implied that nickname registration was still
3363 part of the Tor network design, which it isn't. Closes
3365 - If the sandbox filter fails to load, suggest to the user that
3366 their kernel might not support seccomp2. Closes ticket 23090.
3368 o Minor features (portability):
3369 - Check at configure time whether uint8_t is the same type as
3370 unsigned char. Lots of existing code already makes this
3371 assumption, and there could be strict aliasing issues if the
3372 assumption is violated. Closes ticket 22410.
3374 o Minor features (relay, configuration):
3375 - Reject attempts to use relative file paths when RunAsDaemon is
3376 set. Previously, Tor would accept these, but the directory-
3377 changing step of RunAsDaemon would give strange and/or confusing
3378 results. Closes ticket 22731.
3380 o Minor features (startup, safety):
3381 - When configured to write a PID file, Tor now exits if it is unable
3382 to do so. Previously, it would warn and continue. Closes
3385 o Minor features (static analysis):
3386 - The BUG() macro has been changed slightly so that Coverity no
3387 longer complains about dead code if the bug is impossible. Closes
3390 o Minor features (testing):
3391 - The default chutney network tests now include tests for the v3
3392 hidden service design. Make sure you have the latest version of
3393 chutney if you want to run these. Closes ticket 22437.
3394 - Add a unit test to verify that we can parse a hardcoded v2 hidden
3395 service descriptor. Closes ticket 15554.
3397 o Minor bugfixes (certificate handling):
3398 - Fix a time handling bug in Tor certificates set to expire after
3399 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
3400 Coverity as CID 1415728.
3402 o Minor bugfixes (client, usability):
3403 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
3404 SOCKS4a requests that contain IP address strings, even when
3405 SafeSocks in enabled, as this prevents user from connecting to
3406 known IP addresses without relying on DNS for resolving. SafeSocks
3407 still rejects SOCKS connections that connect to IP addresses when
3408 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
3409 bugfix on Tor 0.2.6.2-alpha.
3411 o Minor bugfixes (code correctness):
3412 - Call htons() in extend_cell_format() for encoding a 16-bit value.
3413 Previously we used ntohs(), which happens to behave the same on
3414 all the platforms we support, but which isn't really correct.
3415 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
3416 - For defense-in-depth, make the controller's write_escaped_data()
3417 function robust to extremely long inputs. Fixes bug 19281; bugfix
3418 on 0.1.1.1-alpha. Reported by Guido Vranken.
3420 o Minor bugfixes (compilation):
3421 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
3422 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
3424 o Minor bugfixes (consensus expiry):
3425 - Check for adequate directory information correctly. Previously, Tor
3426 would reconsider whether it had sufficient directory information
3427 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
3429 o Minor bugfixes (directory protocol):
3430 - Directory servers now include a "Date:" http header for response
3431 codes other than 200. Clients starting with a skewed clock and a
3432 recent consensus were getting "304 Not modified" responses from
3433 directory authorities, so without the Date header, the client
3434 would never hear about a wrong clock. Fixes bug 23499; bugfix
3436 - Make clients wait for 6 seconds before trying to download a
3437 consensus from an authority. Fixes bug 17750; bugfix
3440 o Minor bugfixes (DoS-resistance):
3441 - If future code asks if there are any running bridges, without
3442 checking if bridges are enabled, log a BUG warning rather than
3443 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
3445 o Minor bugfixes (format strictness):
3446 - Restrict several data formats to decimal. Previously, the
3447 BuildTimeHistogram entries in the state file, the "bw=" entries in
3448 the bandwidth authority file, and the process IDs passed to the
3449 __OwningControllerProcess option could all be specified in hex or
3450 octal as well as in decimal. This was not an intentional feature.
3451 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
3454 o Minor bugfixes (heartbeat):
3455 - If we fail to write a heartbeat message, schedule a retry for the
3456 minimum heartbeat interval number of seconds in the future. Fixes
3457 bug 19476; bugfix on 0.2.3.1-alpha.
3459 o Minor bugfixes (linux seccomp2 sandbox, logging):
3460 - Fix some messages on unexpected errors from the seccomp2 library.
3461 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
3463 o Minor bugfixes (logging):
3464 - Remove duplicate log messages regarding opening non-local
3465 SocksPorts upon parsing config and opening listeners at startup.
3466 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
3467 - Use a more comprehensible log message when telling the user
3468 they've excluded every running exit node. Fixes bug 7890; bugfix
3470 - When logging the number of descriptors we intend to download per
3471 directory request, do not log a number higher than then the number
3472 of descriptors we're fetching in total. Fixes bug 19648; bugfix
3474 - When warning about a directory owned by the wrong user, log the
3475 actual name of the user owning the directory. Previously, we'd log
3476 the name of the process owner twice. Fixes bug 23487; bugfix
3478 - The tor specification says hop counts are 1-based, so fix two log
3479 messages that mistakenly logged 0-based hop counts. Fixes bug
3480 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
3481 Credit to Xiaofan Li for reporting this issue.
3483 o Minor bugfixes (portability):
3484 - Stop using the PATH_MAX variable, which is not defined on GNU
3485 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
3487 o Minor bugfixes (relay):
3488 - When uploading our descriptor for the first time after startup,
3489 report the reason for uploading as "Tor just started" rather than
3490 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
3491 - Avoid unnecessary calls to directory_fetches_from_authorities() on
3492 relays, to prevent spurious address resolutions and descriptor
3493 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
3494 bugfix on in 0.2.8.1-alpha.
3496 o Minor bugfixes (tests):
3497 - Fix a broken unit test for the OutboundAddress option: the parsing
3498 function was never returning an error on failure. Fixes bug 23366;
3499 bugfix on 0.3.0.3-alpha.
3500 - Fix a signed-integer overflow in the unit tests for
3501 dir/download_status_random_backoff, which was untriggered until we
3502 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
3504 o Minor bugfixes (usability, control port):
3505 - Stop making an unnecessary routerlist check in NETINFO clock skew
3506 detection; this was preventing clients from reporting NETINFO clock
3507 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
3509 o Code simplification and refactoring:
3510 - Extract the code for handling newly-open channels into a separate
3511 function from the general code to handle channel state
3512 transitions. This change simplifies our callgraph, reducing the
3513 size of the largest strongly connected component by roughly a
3514 factor of two. Closes ticket 22608.
3515 - Remove dead code for largely unused statistics on the number of
3516 times we've attempted various public key operations. Fixes bug
3517 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
3518 - Remove several now-obsolete functions for asking about old
3519 variants directory authority status. Closes ticket 22311; patch
3521 - Remove some of the code that once supported "Named" and "Unnamed"
3522 routers. Authorities no longer vote for these flags. Closes
3524 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
3525 and old hidden services, to indicate that they aren't suitable for
3526 new protocols or formats. Closes ticket 23026.
3527 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
3528 22521. Patch from Neel Chauhan.
3529 - Split the enormous circuit_send_next_onion_skin() function into
3530 multiple subfunctions. Closes ticket 22804.
3531 - Split the portions of the buffer.c module that handle particular
3532 protocols into separate modules. Part of ticket 23149.
3533 - Use our test macros more consistently, to produce more useful
3534 error messages when our unit tests fail. Add coccinelle patches to
3535 allow us to re-check for test macro uses. Closes ticket 22497.
3537 o Deprecated features:
3538 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
3539 only applies to direct unencrypted HTTP connections to your
3540 directory server, which your Tor probably isn't using. Closes
3544 - Clarify in the manual that "Sandbox 1" is only supported on Linux
3545 kernels. Closes ticket 22677.
3546 - Document all values of PublishServerDescriptor in the manpage.
3547 Closes ticket 15645.
3548 - Improve the documentation for the directory port part of the
3549 DirAuthority line. Closes ticket 20152.
3550 - Restore documentation for the authorities' "approved-routers"
3551 file. Closes ticket 21148.
3554 - The AllowDotExit option has been removed as unsafe. It has been
3555 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
3556 - The ClientDNSRejectInternalAddresses flag can no longer be set on
3557 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
3558 Closes ticket 21031.
3559 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
3560 nobody was using it any longer. Closes ticket 22377.
3563 Changes in version 0.2.8.15 - 2017-09-18
3564 Tor 0.2.8.15 backports a collection of bugfixes from later
3567 Most significantly, it includes a fix for TROVE-2017-008, a
3568 security bug that affects hidden services running with the
3569 SafeLogging option disabled. For more information, see
3570 https://trac.torproject.org/projects/tor/ticket/23490
3572 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
3573 2018. We suggest that you upgrade to the latest stable release if
3574 possible. If you can't, we recommend that you upgrade at least to
3575 0.2.9, which will be supported until 2020.
3577 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3578 - Avoid an assertion failure bug affecting our implementation of
3579 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3580 handling of "0xx" differs from what we had expected. Fixes bug
3581 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3584 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3587 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3588 - Backport a fix for an "unused variable" warning that appeared
3589 in some versions of mingw. Fixes bug 22838; bugfix on
3592 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3593 - Fix a memset() off the end of an array when packing cells. This
3594 bug should be harmless in practice, since the corrupted bytes are
3595 still in the same structure, and are always padding bytes,
3596 ignored, or immediately overwritten, depending on compiler
3597 behavior. Nevertheless, because the memset()'s purpose is to make
3598 sure that any other cell-handling bugs can't expose bytes to the
3599 network, we need to fix it. Fixes bug 22737; bugfix on
3600 0.2.4.11-alpha. Fixes CID 1401591.
3602 o Build features (backport from 0.3.1.5-alpha):
3603 - Tor's repository now includes a Travis Continuous Integration (CI)
3604 configuration file (.travis.yml). This is meant to help new
3605 developers and contributors who fork Tor to a Github repository be
3606 better able to test their changes, and understand what we expect
3607 to pass. To use this new build feature, you must fork Tor to your
3608 Github account, then go into the "Integrations" menu in the
3609 repository settings for your fork and enable Travis, then push
3610 your changes. Closes ticket 22636.
3613 Changes in version 0.2.9.12 - 2017-09-18
3614 Tor 0.2.9.12 backports a collection of bugfixes from later
3617 Most significantly, it includes a fix for TROVE-2017-008, a
3618 security bug that affects hidden services running with the
3619 SafeLogging option disabled. For more information, see
3620 https://trac.torproject.org/projects/tor/ticket/23490
3622 o Major features (security, backport from 0.3.0.2-alpha):
3623 - Change the algorithm used to decide DNS TTLs on client and server
3624 side, to better resist DNS-based correlation attacks like the
3625 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
3626 Feamster. Now relays only return one of two possible DNS TTL
3627 values, and clients are willing to believe DNS TTL values up to 3
3628 hours long. Closes ticket 19769.
3630 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
3631 - Fix a rare crash when sending a begin cell on a circuit whose
3632 linked directory connection had already been closed. Fixes bug
3633 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
3635 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
3636 - Fix a bug that prevented exit nodes from caching DNS records for
3637 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
3639 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
3640 - Fix a typo that had prevented TPROXY-based transparent proxying
3641 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3642 Patch from "d4fq0fQAgoJ".
3644 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3645 - Avoid an assertion failure bug affecting our implementation of
3646 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3647 handling of "0xx" differs from what we had expected. Fixes bug
3648 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3650 o Minor features (code style, backport from 0.3.1.3-alpha):
3651 - Add "Falls through" comments to our codebase, in order to silence
3652 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3653 Stieger. Closes ticket 22446.
3655 o Minor features (geoip):
3656 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3659 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
3660 - Roll over monthly accounting at the configured hour and minute,
3661 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3662 Found by Andrey Karpov with PVS-Studio.
3664 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
3665 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
3666 bugfix on 0.2.8.1-alpha.
3667 - Fix warnings when building with libscrypt and openssl scrypt support
3668 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3669 - When building with certain versions the mingw C header files, avoid
3670 float-conversion warnings when calling the C functions isfinite(),
3671 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
3673 o Minor bugfixes (compilation, backport from 0.3.1.7):
3674 - Avoid compiler warnings in the unit tests for running tor_sscanf()
3675 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3677 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3678 - Backport a fix for an "unused variable" warning that appeared
3679 in some versions of mingw. Fixes bug 22838; bugfix on
3682 o Minor bugfixes (controller, backport from 0.3.1.7):
3683 - Do not crash when receiving a HSPOST command with an empty body.
3684 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3685 - Do not crash when receiving a POSTDESCRIPTOR command with an
3686 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3688 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
3689 - Avoid Coverity build warnings related to our BUG() macro. By
3690 default, Coverity treats BUG() as the Linux kernel does: an
3691 instant abort(). We need to override that so our BUG() macro
3692 doesn't prevent Coverity from analyzing functions that use it.
3693 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3695 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3696 - Fix a memset() off the end of an array when packing cells. This
3697 bug should be harmless in practice, since the corrupted bytes are
3698 still in the same structure, and are always padding bytes,
3699 ignored, or immediately overwritten, depending on compiler
3700 behavior. Nevertheless, because the memset()'s purpose is to make
3701 sure that any other cell-handling bugs can't expose bytes to the
3702 network, we need to fix it. Fixes bug 22737; bugfix on
3703 0.2.4.11-alpha. Fixes CID 1401591.
3705 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
3706 - When setting the maximum number of connections allowed by the OS,
3707 always allow some extra file descriptors for other files. Fixes
3708 bug 22797; bugfix on 0.2.0.10-alpha.
3710 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
3711 - Avoid a sandbox failure when trying to re-bind to a socket and
3712 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
3714 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
3715 - Permit the fchmod system call, to avoid crashing on startup when
3716 starting with the seccomp2 sandbox and an unexpected set of
3717 permissions on the data directory or its contents. Fixes bug
3718 22516; bugfix on 0.2.5.4-alpha.
3720 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
3721 - Avoid a double-marked-circuit warning that could happen when we
3722 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
3725 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
3726 - Reject version numbers with non-numeric prefixes (such as +, -, or
3727 whitespace). Disallowing whitespace prevents differential version
3728 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3729 and part of 21508; bugfix on 0.0.8pre1.
3731 o Build features (backport from 0.3.1.5-alpha):
3732 - Tor's repository now includes a Travis Continuous Integration (CI)
3733 configuration file (.travis.yml). This is meant to help new
3734 developers and contributors who fork Tor to a Github repository be
3735 better able to test their changes, and understand what we expect
3736 to pass. To use this new build feature, you must fork Tor to your
3737 Github account, then go into the "Integrations" menu in the
3738 repository settings for your fork and enable Travis, then push
3739 your changes. Closes ticket 22636.
3742 Changes in version 0.3.0.11 - 2017-09-18
3743 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
3746 Most significantly, it includes a fix for TROVE-2017-008, a
3747 security bug that affects hidden services running with the
3748 SafeLogging option disabled. For more information, see
3749 https://trac.torproject.org/projects/tor/ticket/23490
3751 o Minor features (code style, backport from 0.3.1.7):
3752 - Add "Falls through" comments to our codebase, in order to silence
3753 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3754 Stieger. Closes ticket 22446.
3757 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3760 o Minor bugfixes (compilation, backport from 0.3.1.7):
3761 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
3762 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3764 o Minor bugfixes (controller, backport from 0.3.1.7):
3765 - Do not crash when receiving a HSPOST command with an empty body.
3766 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3767 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
3768 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3770 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
3771 - When setting the maximum number of connections allowed by the OS,
3772 always allow some extra file descriptors for other files. Fixes
3773 bug 22797; bugfix on 0.2.0.10-alpha.
3775 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
3776 - Remove a forgotten debugging message when an introduction point
3777 successfully establishes a hidden service prop224 circuit with
3779 - Change three other log_warn() for an introduction point to
3780 protocol warnings, because they can be failure from the network
3781 and are not relevant to the operator. Fixes bug 23078; bugfix on
3782 0.3.0.1-alpha and 0.3.0.2-alpha.
3785 Changes in version 0.3.1.7 - 2017-09-18
3786 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
3788 With the 0.3.1 series, Tor now serves and downloads directory
3789 information in more compact formats, to save on bandwidth overhead. It
3790 also contains a new padding system to resist netflow-based traffic
3791 analysis, and experimental support for building parts of Tor in Rust
3792 (though no parts of Tor are in Rust yet). There are also numerous
3793 small features, bugfixes on earlier release series, and groundwork for
3794 the hidden services revamp of 0.3.2.
3796 This release also includes a fix for TROVE-2017-008, a security bug
3797 that affects hidden services running with the SafeLogging option
3798 disabled. For more information, see
3799 https://trac.torproject.org/projects/tor/ticket/23490
3801 Per our stable release policy, we plan to support each stable release
3802 series for at least the next nine months, or for three months after
3803 the first stable release of the next series: whichever is longer. If
3804 you need a release with long-term support, we recommend that you stay
3805 with the 0.2.9 series.
3807 Below is a list of the changes since 0.3.1.6-rc. For a list of all
3808 changes since 0.3.0, see the ReleaseNotes file.
3810 o Major bugfixes (security, hidden services, loggging):
3811 - Fix a bug where we could log uninitialized stack when a certain
3812 hidden service error occurred while SafeLogging was disabled.
3813 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
3814 TROVE-2017-008 and CVE-2017-0380.
3816 o Minor features (defensive programming):
3817 - Create a pair of consensus parameters, nf_pad_tor2web and
3818 nf_pad_single_onion, to disable netflow padding in the consensus
3819 for non-anonymous connections in case the overhead is high. Closes
3822 o Minor features (diagnostic):
3823 - Add a stack trace to the bug warnings that can be logged when
3824 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
3825 attempt for bug 23105.
3827 o Minor features (geoip):
3828 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3831 o Minor bugfixes (compilation):
3832 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
3833 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3835 o Minor bugfixes (controller):
3836 - Do not crash when receiving a HSPOST command with an empty body.
3837 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3838 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
3839 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3841 o Minor bugfixes (relay):
3842 - Inform the geoip and rephist modules about all requests, even on
3843 relays that are only fetching microdescriptors. Fixes a bug
3844 related to 21585; bugfix on 0.3.0.1-alpha.
3846 o Minor bugfixes (unit tests):
3847 - Fix a channelpadding unit test failure on slow systems by using
3848 mocked time instead of actual time. Fixes bug 23077; bugfix
3852 Changes in version 0.3.1.6-rc - 2017-09-05
3853 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
3854 release series, including a bug that produced weird behavior on
3855 Windows directory caches.
3857 This is the first release candidate in the Tor 0.3.1 series. If we
3858 find no new bugs or regressions here, the first stable 0.3.1 release
3859 will be nearly identical to it.
3861 o Major bugfixes (windows, directory cache):
3862 - On Windows, do not try to delete cached consensus documents and
3863 diffs before they are unmapped from memory--Windows won't allow
3864 that. Instead, allow the consensus cache directory to grow larger,
3865 to hold files that might need to stay around longer. Fixes bug
3866 22752; bugfix on 0.3.1.1-alpha.
3868 o Minor features (directory authority):
3869 - Improve the message that authorities report to relays that present
3870 RSA/Ed25519 keypairs that conflict with previously pinned keys.
3871 Closes ticket 22348.
3873 o Minor features (geoip):
3874 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
3877 o Minor features (testing):
3878 - Add more tests for compression backend initialization. Closes
3881 o Minor bugfixes (directory cache):
3882 - Fix a memory leak when recovering space in the consensus cache.
3883 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
3885 o Minor bugfixes (hidden service):
3886 - Increase the number of circuits that a service is allowed to
3887 open over a specific period of time. The value was lower than it
3888 should be (8 vs 12) in the normal case of 3 introduction points.
3889 Fixes bug 22159; bugfix on 0.3.0.5-rc.
3890 - Fix a BUG warning during HSv3 descriptor decoding that could be
3891 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
3892 on 0.3.0.1-alpha. Bug found by "haxxpop".
3893 - Rate-limit the log messages if we exceed the maximum number of
3894 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
3896 o Minor bugfixes (logging, relay):
3897 - Remove a forgotten debugging message when an introduction point
3898 successfully establishes a hidden service prop224 circuit with
3900 - Change three other log_warn() for an introduction point to
3901 protocol warnings, because they can be failure from the network
3902 and are not relevant to the operator. Fixes bug 23078; bugfix on
3903 0.3.0.1-alpha and 0.3.0.2-alpha.
3905 o Minor bugfixes (relay):
3906 - When a relay is not running as a directory cache, it will no
3907 longer generate compressed consensuses and consensus diff
3908 information. Previously, this was a waste of disk and CPU. Fixes
3909 bug 23275; bugfix on 0.3.1.1-alpha.
3911 o Minor bugfixes (robustness, error handling):
3912 - Improve our handling of the cases where OpenSSL encounters a
3913 memory error while encoding keys and certificates. We haven't
3914 observed these errors in the wild, but if they do happen, we now
3915 detect and respond better. Fixes bug 19418; bugfix on all versions
3916 of Tor. Reported by Guido Vranken.
3918 o Minor bugfixes (stability):
3919 - Avoid crashing on a double-free when unable to load or process an
3920 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
3921 with the clang static analyzer.
3923 o Minor bugfixes (testing):
3924 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
3925 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
3926 - Port the hs_ntor handshake test to work correctly with recent
3927 versions of the pysha3 module. Fixes bug 23071; bugfix
3930 o Minor bugfixes (Windows service):
3931 - When running as a Windows service, set the ID of the main thread
3932 correctly. Failure to do so made us fail to send log messages to
3933 the controller in 0.2.1.16-rc, slowed down controller event
3934 delivery in 0.2.7.3-rc and later, and crash with an assertion
3935 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
3936 Patch and diagnosis from "Vort".
3939 Changes in version 0.3.0.10 - 2017-08-02
3940 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
3941 from the current Tor alpha series. OpenBSD users and TPROXY users
3942 should upgrade; others are probably okay sticking with 0.3.0.9.
3944 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
3945 - Tor's repository now includes a Travis Continuous Integration (CI)
3946 configuration file (.travis.yml). This is meant to help new
3947 developers and contributors who fork Tor to a Github repository be
3948 better able to test their changes, and understand what we expect
3949 to pass. To use this new build feature, you must fork Tor to your
3950 Github account, then go into the "Integrations" menu in the
3951 repository settings for your fork and enable Travis, then push
3952 your changes. Closes ticket 22636.
3954 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
3955 - Fix a typo that had prevented TPROXY-based transparent proxying
3956 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3957 Patch from "d4fq0fQAgoJ".
3959 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3960 - Avoid an assertion failure bug affecting our implementation of
3961 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3962 handling of "0xbar" differs from what we had expected. Fixes bug
3963 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3965 o Minor features (backport from 0.3.1.5-alpha):
3966 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
3969 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
3970 - Roll over monthly accounting at the configured hour and minute,
3971 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3972 Found by Andrey Karpov with PVS-Studio.
3974 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
3975 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
3976 bugfix on 0.2.8.1-alpha.
3977 - Fix warnings when building with libscrypt and openssl scrypt
3978 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3979 - When building with certain versions of the mingw C header files,
3980 avoid float-conversion warnings when calling the C functions
3981 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
3984 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3985 - Backport a fix for an "unused variable" warning that appeared
3986 in some versions of mingw. Fixes bug 22838; bugfix on
3989 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
3990 - Avoid Coverity build warnings related to our BUG() macro. By
3991 default, Coverity treats BUG() as the Linux kernel does: an
3992 instant abort(). We need to override that so our BUG() macro
3993 doesn't prevent Coverity from analyzing functions that use it.
3994 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3996 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
3997 - When rejecting a router descriptor for running an obsolete version
3998 of Tor without ntor support, warn about the obsolete tor version,
3999 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
4001 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
4002 - Avoid a sandbox failure when trying to re-bind to a socket and
4003 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
4005 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
4006 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
4007 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
4010 Changes in version 0.3.1.5-alpha - 2017-08-01
4011 Tor 0.3.1.5-alpha improves the performance of consensus diff
4012 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
4013 several other bugs. If no serious bugs are found in this version, the
4014 next version will be a release candidate.
4016 This release also marks the end of support for the Tor 0.2.4.x,
4017 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
4018 further bug or security fixes. Anyone still running or distributing
4019 one of those versions should upgrade.
4021 o Major features (build system, continuous integration):
4022 - Tor's repository now includes a Travis Continuous Integration (CI)
4023 configuration file (.travis.yml). This is meant to help new
4024 developers and contributors who fork Tor to a Github repository be
4025 better able to test their changes, and understand what we expect
4026 to pass. To use this new build feature, you must fork Tor to your
4027 Github account, then go into the "Integrations" menu in the
4028 repository settings for your fork and enable Travis, then push
4029 your changes. Closes ticket 22636.
4031 o Major bugfixes (openbsd, denial-of-service):
4032 - Avoid an assertion failure bug affecting our implementation of
4033 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
4034 handling of "0xbar" differs from what we had expected. Fixes bug
4035 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
4037 o Major bugfixes (relay, performance):
4038 - Perform circuit handshake operations at a higher priority than we
4039 use for consensus diff creation and compression. This should
4040 prevent circuits from starving when a relay or bridge receives a
4041 new consensus, especially on lower-powered machines. Fixes bug
4042 22883; bugfix on 0.3.1.1-alpha.
4044 o Minor features (bridge authority):
4045 - Add "fingerprint" lines to the networkstatus-bridges file produced
4046 by bridge authorities. Closes ticket 22207.
4048 o Minor features (directory cache, consensus diff):
4049 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
4050 operators with low-resource environments to adjust the number of
4051 consensuses they'll store and generate diffs from. Most cache
4052 operators should leave it unchanged. Helps to work around
4055 o Minor features (geoip):
4056 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
4059 o Minor features (relay, performance):
4060 - Always start relays with at least two worker threads, to prevent
4061 priority inversion on slow tasks. Part of the fix for bug 22883.
4062 - Allow background work to be queued with different priorities, so
4063 that a big pile of slow low-priority jobs will not starve out
4064 higher priority jobs. This lays the groundwork for a fix for
4067 o Minor bugfixes (build system, rust):
4068 - Fix a problem where Rust toolchains were not being found when
4069 building without --enable-cargo-online-mode, due to setting the
4070 $HOME environment variable instead of $CARGO_HOME. Fixes bug
4071 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
4073 o Minor bugfixes (compatibility, zstd):
4074 - Write zstd epilogues correctly when the epilogue requires
4075 reallocation of the output buffer, even with zstd 1.3.0.
4076 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
4077 22927; bugfix on 0.3.1.1-alpha.
4079 o Minor bugfixes (compilation warnings):
4080 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
4081 22915; bugfix on 0.2.8.1-alpha.
4082 - Fix warnings when building with libscrypt and openssl scrypt
4083 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
4084 - Compile correctly when both openssl 1.1.0 and libscrypt are
4085 detected. Previously this would cause an error. Fixes bug 22892;
4086 bugfix on 0.3.1.1-alpha.
4087 - When building with certain versions of the mingw C header files,
4088 avoid float-conversion warnings when calling the C functions
4089 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
4092 o Minor bugfixes (coverity build support):
4093 - Avoid Coverity build warnings related to our BUG() macro. By
4094 default, Coverity treats BUG() as the Linux kernel does: an
4095 instant abort(). We need to override that so our BUG() macro
4096 doesn't prevent Coverity from analyzing functions that use it.
4097 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
4099 o Minor bugfixes (directory authority):
4100 - When a directory authority rejects a descriptor or extrainfo with
4101 a given digest, mark that digest as undownloadable, so that we do
4102 not attempt to download it again over and over. We previously
4103 tried to avoid downloading such descriptors by other means, but we
4104 didn't notice if we accidentally downloaded one anyway. This
4105 behavior became problematic in 0.2.7.2-alpha, when authorities
4106 began pinning Ed25519 keys. Fixes bug 22349; bugfix
4109 o Minor bugfixes (error reporting, windows):
4110 - When formatting Windows error messages, use the English format to
4111 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
4114 o Minor bugfixes (file limits, osx):
4115 - When setting the maximum number of connections allowed by the OS,
4116 always allow some extra file descriptors for other files. Fixes
4117 bug 22797; bugfix on 0.2.0.10-alpha.
4119 o Minor bugfixes (linux seccomp2 sandbox):
4120 - Avoid a sandbox failure when trying to re-bind to a socket and
4121 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
4123 o Minor bugfixes (memory leaks):
4124 - Fix a small memory leak when validating a configuration that uses
4125 two or more AF_UNIX sockets for the same port type. Fixes bug
4126 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
4128 o Minor bugfixes (unit tests):
4129 - test_consdiff_base64cmp would fail on OS X because while OS X
4130 follows the standard of (less than zero/zero/greater than zero),
4131 it doesn't follow the convention of (-1/0/+1). Make the test
4132 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
4133 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
4134 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
4137 Changes in version 0.3.1.4-alpha - 2017-06-29
4138 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
4139 to use a guard that was in the same network family as a chosen exit
4140 relay. This is a security regression; all clients running earlier
4141 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
4144 This release also fixes several other bugs introduced in 0.3.0.x
4145 and 0.3.1.x, including others that can affect bandwidth usage
4149 - To build with zstd and lzma support, Tor now requires the
4150 pkg-config tool at build time. (This requirement was new in
4151 0.3.1.1-alpha, but was not noted at the time. Noting it here to
4152 close ticket 22623.)
4154 o Major bugfixes (path selection, security):
4155 - When choosing which guard to use for a circuit, avoid the exit's
4156 family along with the exit itself. Previously, the new guard
4157 selection logic avoided the exit, but did not consider its family.
4158 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
4159 006 and CVE-2017-0377.
4161 o Major bugfixes (compression, zstd):
4162 - Correctly detect a full buffer when decompressing a large zstd-
4163 compressed input. Previously, we would sometimes treat a full
4164 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
4166 o Major bugfixes (directory protocol):
4167 - Ensure that we send "304 Not modified" as HTTP status code when a
4168 client is attempting to fetch a consensus or consensus diff, and
4169 the best one we can send them is one they already have. Fixes bug
4170 22702; bugfix on 0.3.1.1-alpha.
4172 o Major bugfixes (entry guards):
4173 - When starting with an old consensus, do not add new entry guards
4174 unless the consensus is "reasonably live" (under 1 day old). Fixes
4175 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
4177 o Minor features (bug mitigation, diagnostics, logging):
4178 - Avoid an assertion failure, and log a better error message, when
4179 unable to remove a file from the consensus cache on Windows.
4180 Attempts to mitigate and diagnose bug 22752.
4182 o Minor features (geoip):
4183 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
4186 o Minor bugfixes (compression):
4187 - When compressing or decompressing a buffer, check for a failure to
4188 create a compression object. Fixes bug 22626; bugfix
4190 - When decompressing a buffer, check for extra data after the end of
4191 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
4192 - When decompressing an object received over an anonymous directory
4193 connection, if we have already decompressed it using an acceptable
4194 compression method, do not reject it for looking like an
4195 unacceptable compression method. Fixes part of bug 22670; bugfix
4197 - When serving directory votes compressed with zlib, do not claim to
4198 have compressed them with zstd. Fixes bug 22669; bugfix
4200 - When spooling compressed data to an output buffer, don't try to
4201 spool more data when there is no more data to spool and we are not
4202 trying to flush the input. Previously, we would sometimes launch
4203 compression requests with nothing to do, which interferes with our
4204 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
4206 o Minor bugfixes (defensive programming):
4207 - Detect and break out of infinite loops in our compression code. We
4208 don't think that any such loops exist now, but it's best to be
4209 safe. Closes ticket 22672.
4210 - Fix a memset() off the end of an array when packing cells. This
4211 bug should be harmless in practice, since the corrupted bytes are
4212 still in the same structure, and are always padding bytes,
4213 ignored, or immediately overwritten, depending on compiler
4214 behavior. Nevertheless, because the memset()'s purpose is to make
4215 sure that any other cell-handling bugs can't expose bytes to the
4216 network, we need to fix it. Fixes bug 22737; bugfix on
4217 0.2.4.11-alpha. Fixes CID 1401591.
4219 o Minor bugfixes (linux seccomp2 sandbox):
4220 - Permit the fchmod system call, to avoid crashing on startup when
4221 starting with the seccomp2 sandbox and an unexpected set of
4222 permissions on the data directory or its contents. Fixes bug
4223 22516; bugfix on 0.2.5.4-alpha.
4224 - Fix a crash in the LZMA module, when the sandbox was enabled, and
4225 liblzma would allocate more than 16 MB of memory. We solve this by
4226 bumping the mprotect() limit in the sandbox module from 16 MB to
4227 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
4229 o Minor bugfixes (logging):
4230 - When decompressing, do not warn if we fail to decompress using a
4231 compression method that we merely guessed. Fixes part of bug
4232 22670; bugfix on 0.1.1.14-alpha.
4233 - When decompressing, treat mismatch between content-encoding and
4234 actual compression type as a protocol warning. Fixes part of bug
4235 22670; bugfix on 0.1.1.9-alpha.
4236 - Downgrade "assigned_to_cpuworker failed" message to info-level
4237 severity. In every case that can reach it, either a better warning
4238 has already been logged, or no warning is warranted. Fixes bug
4239 22356; bugfix on 0.2.6.3-alpha.
4240 - Demote a warn that was caused by libevent delays to info if
4241 netflow padding is less than 4.5 seconds late, or to notice
4242 if it is more (4.5 seconds is the amount of time that a netflow
4243 record might be emitted after, if we chose the maximum timeout).
4244 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
4246 o Minor bugfixes (process behavior):
4247 - When exiting because of an error, always exit with a nonzero exit
4248 status. Previously, we would fail to report an error in our exit
4249 status in cases related to __OwningControllerProcess failure,
4250 lockfile contention, and Ed25519 key initialization. Fixes bug
4251 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
4252 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
4256 - Add a manpage description for the key-pinning-journal file. Closes
4258 - Correctly note that bandwidth accounting values are stored in the
4259 state file, and the bw_accounting file is now obsolete. Closes
4261 - Document more of the files in the Tor data directory, including
4262 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
4263 approved-routers, sr-random, and diff-cache. Found while fixing
4267 Changes in version 0.3.0.9 - 2017-06-29
4268 Tor 0.3.0.9 fixes a path selection bug that would allow a client
4269 to use a guard that was in the same network family as a chosen exit
4270 relay. This is a security regression; all clients running earlier
4271 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
4274 This release also backports several other bugfixes from the 0.3.1.x
4277 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
4278 - When choosing which guard to use for a circuit, avoid the exit's
4279 family along with the exit itself. Previously, the new guard
4280 selection logic avoided the exit, but did not consider its family.
4281 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
4282 006 and CVE-2017-0377.
4284 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
4285 - Don't block bootstrapping when a primary bridge is offline and we
4286 can't get its descriptor. Fixes bug 22325; fixes one case of bug
4287 21969; bugfix on 0.3.0.3-alpha.
4289 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
4290 - When starting with an old consensus, do not add new entry guards
4291 unless the consensus is "reasonably live" (under 1 day old). Fixes
4292 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
4294 o Minor features (geoip):
4295 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
4298 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
4299 - Reject version numbers with non-numeric prefixes (such as +, -, or
4300 whitespace). Disallowing whitespace prevents differential version
4301 parsing between POSIX-based and Windows platforms. Fixes bug 21507
4302 and part of 21508; bugfix on 0.0.8pre1.
4304 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
4305 - Permit the fchmod system call, to avoid crashing on startup when
4306 starting with the seccomp2 sandbox and an unexpected set of
4307 permissions on the data directory or its contents. Fixes bug
4308 22516; bugfix on 0.2.5.4-alpha.
4310 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
4311 - Fix a memset() off the end of an array when packing cells. This
4312 bug should be harmless in practice, since the corrupted bytes are
4313 still in the same structure, and are always padding bytes,
4314 ignored, or immediately overwritten, depending on compiler
4315 behavior. Nevertheless, because the memset()'s purpose is to make
4316 sure that any other cell-handling bugs can't expose bytes to the
4317 network, we need to fix it. Fixes bug 22737; bugfix on
4318 0.2.4.11-alpha. Fixes CID 1401591.
4321 Changes in version 0.3.1.3-alpha - 2017-06-08
4322 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
4323 remotely crash a hidden service with an assertion failure. Anyone
4324 running a hidden service should upgrade to this version, or to some
4325 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
4327 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
4328 that sometimes made relays unreliable, as well as several other
4329 bugfixes described below.
4331 o Major bugfixes (hidden service, relay, security):
4332 - Fix a remotely triggerable assertion failure when a hidden service
4333 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
4334 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
4335 - Fix a remotely triggerable assertion failure caused by receiving a
4336 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4337 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4340 o Major bugfixes (relay, link handshake):
4341 - When performing the v3 link handshake on a TLS connection, report
4342 that we have the x509 certificate that we actually used on that
4343 connection, even if we have changed certificates since that
4344 connection was first opened. Previously, we would claim to have
4345 used our most recent x509 link certificate, which would sometimes
4346 make the link handshake fail. Fixes one case of bug 22460; bugfix
4349 o Major bugfixes (relays, key management):
4350 - Regenerate link and authentication certificates whenever the key
4351 that signs them changes; also, regenerate link certificates
4352 whenever the signed key changes. Previously, these processes were
4353 only weakly coupled, and we relays could (for minutes to hours)
4354 wind up with an inconsistent set of keys and certificates, which
4355 other relays would not accept. Fixes two cases of bug 22460;
4356 bugfix on 0.3.0.1-alpha.
4357 - When sending an Ed25519 signing->link certificate in a CERTS cell,
4358 send the certificate that matches the x509 certificate that we
4359 used on the TLS connection. Previously, there was a race condition
4360 if the TLS context rotated after we began the TLS handshake but
4361 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
4364 o Major bugfixes (torrc, crash):
4365 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
4366 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
4368 o Minor features (code style):
4369 - Add "Falls through" comments to our codebase, in order to silence
4370 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
4371 Stieger. Closes ticket 22446.
4373 o Minor features (diagnostic):
4374 - Add logging messages to try to diagnose a rare bug that seems to
4375 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
4376 think this is happening because of incorrect system clocks, but
4377 we'd like to know for certain. Diagnostic for bug 22466.
4379 o Minor bugfixes (correctness):
4380 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4381 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4383 o Minor bugfixes (directory protocol):
4384 - Check for libzstd >= 1.1, because older versions lack the
4385 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
4387 o Minor bugfixes (link handshake):
4388 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
4389 months, and regenerate it when it is within one month of expiring.
4390 Previously, we had generated this certificate at startup with a
4391 ten-year lifetime, but that could lead to weird behavior when Tor
4392 was started with a grossly inaccurate clock. Mitigates bug 22466;
4393 mitigation on 0.3.0.1-alpha.
4395 o Minor bugfixes (storage directories):
4396 - Always check for underflows in the cached storage directory usage.
4397 If the usage does underflow, re-calculate it. Also, avoid a
4398 separate underflow when the usage is not known. Fixes bug 22424;
4399 bugfix on 0.3.1.1-alpha.
4401 o Minor bugfixes (unit tests):
4402 - The unit tests now pass on systems where localhost is misconfigured
4403 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
4407 - Clarify the manpage for the (deprecated) torify script. Closes
4410 Changes in version 0.3.0.8 - 2017-06-08
4411 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
4412 remotely crash a hidden service with an assertion failure. Anyone
4413 running a hidden service should upgrade to this version, or to some
4414 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
4416 Tor 0.3.0.8 also includes fixes for several key management bugs
4417 that sometimes made relays unreliable, as well as several other
4418 bugfixes described below.
4420 o Major bugfixes (hidden service, relay, security, backport
4421 from 0.3.1.3-alpha):
4422 - Fix a remotely triggerable assertion failure when a hidden service
4423 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
4424 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
4425 - Fix a remotely triggerable assertion failure caused by receiving a
4426 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4427 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4430 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
4431 - When performing the v3 link handshake on a TLS connection, report
4432 that we have the x509 certificate that we actually used on that
4433 connection, even if we have changed certificates since that
4434 connection was first opened. Previously, we would claim to have
4435 used our most recent x509 link certificate, which would sometimes
4436 make the link handshake fail. Fixes one case of bug 22460; bugfix
4439 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
4440 - Regenerate link and authentication certificates whenever the key
4441 that signs them changes; also, regenerate link certificates
4442 whenever the signed key changes. Previously, these processes were
4443 only weakly coupled, and we relays could (for minutes to hours)
4444 wind up with an inconsistent set of keys and certificates, which
4445 other relays would not accept. Fixes two cases of bug 22460;
4446 bugfix on 0.3.0.1-alpha.
4447 - When sending an Ed25519 signing->link certificate in a CERTS cell,
4448 send the certificate that matches the x509 certificate that we
4449 used on the TLS connection. Previously, there was a race condition
4450 if the TLS context rotated after we began the TLS handshake but
4451 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
4454 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
4455 - Stop rejecting v3 hidden service descriptors because their size
4456 did not match an old padding rule. Fixes bug 22447; bugfix on
4459 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4460 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4461 December 2016 (of which ~126 were still functional) with a list of
4462 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4463 2017. Resolves ticket 21564.
4465 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
4466 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
4467 bug 22252; bugfix on 0.2.9.3-alpha.
4469 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
4470 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4471 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4473 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
4474 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
4475 months, and regenerate it when it is within one month of expiring.
4476 Previously, we had generated this certificate at startup with a
4477 ten-year lifetime, but that could lead to weird behavior when Tor
4478 was started with a grossly inaccurate clock. Mitigates bug 22466;
4479 mitigation on 0.3.0.1-alpha.
4481 o Minor bugfixes (memory leak, directory authority, backport from
4483 - When directory authorities reject a router descriptor due to
4484 keypinning, free the router descriptor rather than leaking the
4485 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4488 Changes in version 0.2.9.11 - 2017-06-08
4489 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
4490 remotely crash a hidden service with an assertion failure. Anyone
4491 running a hidden service should upgrade to this version, or to some
4492 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4493 are not affected by TROVE-2017-004.)
4495 Tor 0.2.9.11 also backports fixes for several key management bugs
4496 that sometimes made relays unreliable, as well as several other
4497 bugfixes described below.
4499 o Major bugfixes (hidden service, relay, security, backport
4500 from 0.3.1.3-alpha):
4501 - Fix a remotely triggerable assertion failure caused by receiving a
4502 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4503 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4506 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
4507 - When performing the v3 link handshake on a TLS connection, report
4508 that we have the x509 certificate that we actually used on that
4509 connection, even if we have changed certificates since that
4510 connection was first opened. Previously, we would claim to have
4511 used our most recent x509 link certificate, which would sometimes
4512 make the link handshake fail. Fixes one case of bug 22460; bugfix
4515 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4516 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4517 December 2016 (of which ~126 were still functional) with a list of
4518 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4519 2017. Resolves ticket 21564.
4521 o Minor features (future-proofing, backport from 0.3.0.7):
4522 - Tor no longer refuses to download microdescriptors or descriptors if
4523 they are listed as "published in the future". This change will
4524 eventually allow us to stop listing meaningful "published" dates
4525 in microdescriptor consensuses, and thereby allow us to reduce the
4526 resources required to download consensus diffs by over 50%.
4527 Implements part of ticket 21642; implements part of proposal 275.
4529 o Minor features (directory authorities, backport from 0.3.0.4-rc)
4530 - Directory authorities now reject relays running versions
4531 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
4532 suffer from bug 20499 and don't keep their consensus cache
4533 up-to-date. Resolves ticket 20509.
4535 o Minor features (geoip):
4536 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4539 o Minor bugfixes (control port, backport from 0.3.0.6):
4540 - The GETINFO extra-info/digest/<digest> command was broken because
4541 of a wrong base16 decode return value check, introduced when
4542 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
4544 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
4545 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4546 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4548 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
4549 - The getpid() system call is now permitted under the Linux seccomp2
4550 sandbox, to avoid crashing with versions of OpenSSL (and other
4551 libraries) that attempt to learn the process's PID by using the
4552 syscall rather than the VDSO code. Fixes bug 21943; bugfix
4555 o Minor bugfixes (memory leak, directory authority, backport
4556 from 0.3.1.2-alpha):
4557 - When directory authorities reject a router descriptor due to
4558 keypinning, free the router descriptor rather than leaking the
4559 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4561 Changes in version 0.2.8.14 - 2017-06-08
4562 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4563 remotely crash a hidden service with an assertion failure. Anyone
4564 running a hidden service should upgrade to this version, or to some
4565 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4566 are not affected by TROVE-2017-004.)
4568 o Major bugfixes (hidden service, relay, security):
4569 - Fix a remotely triggerable assertion failure caused by receiving a
4570 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4571 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4574 o Minor features (geoip):
4575 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4578 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4579 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4580 December 2016 (of which ~126 were still functional) with a list of
4581 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4582 2017. Resolves ticket 21564.
4584 o Minor bugfixes (correctness):
4585 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4586 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4588 Changes in version 0.2.7.8 - 2017-06-08
4589 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4590 remotely crash a hidden service with an assertion failure. Anyone
4591 running a hidden service should upgrade to this version, or to some
4592 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4593 are not affected by TROVE-2017-004.)
4595 o Major bugfixes (hidden service, relay, security):
4596 - Fix a remotely triggerable assertion failure caused by receiving a
4597 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4598 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4601 o Minor features (geoip):
4602 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4605 o Minor bugfixes (correctness):
4606 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4607 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4610 Changes in version 0.2.6.12 - 2017-06-08
4611 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
4612 remotely crash a hidden service with an assertion failure. Anyone
4613 running a hidden service should upgrade to this version, or to some
4614 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4615 are not affected by TROVE-2017-004.)
4617 o Major bugfixes (hidden service, relay, security):
4618 - Fix a remotely triggerable assertion failure caused by receiving a
4619 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4620 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4623 o Minor features (geoip):
4624 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4627 o Minor bugfixes (correctness):
4628 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4629 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4631 Changes in version 0.2.5.14 - 2017-06-08
4632 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
4633 remotely crash a hidden service with an assertion failure. Anyone
4634 running a hidden service should upgrade to this version, or to some
4635 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4636 are not affected by TROVE-2017-004.)
4638 o Major bugfixes (hidden service, relay, security):
4639 - Fix a remotely triggerable assertion failure caused by receiving a
4640 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4641 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4644 o Minor features (geoip):
4645 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4648 o Minor bugfixes (correctness):
4649 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4650 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4652 Changes in version 0.2.4.29 - 2017-06-08
4653 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
4654 remotely crash a hidden service with an assertion failure. Anyone
4655 running a hidden service should upgrade to this version, or to some
4656 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4657 are not affected by TROVE-2017-004.)
4659 o Major bugfixes (hidden service, relay, security):
4660 - Fix a remotely triggerable assertion failure caused by receiving a
4661 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4662 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4665 o Minor features (geoip):
4666 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4669 o Minor bugfixes (correctness):
4670 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4671 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4674 Changes in version 0.3.1.2-alpha - 2017-05-26
4675 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
4676 fixes a few bugs found while testing 0.3.1.1-alpha, including a
4677 memory corruption bug that affected relay stability.
4679 o Major bugfixes (crash, relay):
4680 - Fix a memory-corruption bug in relays that set MyFamily.
4681 Previously, they would double-free MyFamily elements when making
4682 the next descriptor or when changing their configuration. Fixes
4683 bug 22368; bugfix on 0.3.1.1-alpha.
4685 o Minor bugfixes (logging):
4686 - Log a better message when a directory authority replies to an
4687 upload with an unexpected status code. Fixes bug 11121; bugfix
4690 o Minor bugfixes (memory leak, directory authority):
4691 - When directory authorities reject a router descriptor due to
4692 keypinning, free the router descriptor rather than leaking the
4693 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4696 Changes in version 0.3.1.1-alpha - 2017-05-22
4697 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
4698 reduces the bandwidth usage for Tor's directory protocol, adds some
4699 basic padding to resist netflow-based traffic analysis and to serve as
4700 the basis of other padding in the future, and adds rust support to the
4703 It also contains numerous other small features and improvements to
4704 security, correctness, and performance.
4706 Below are the changes since 0.3.0.7.
4708 o Major features (directory protocol):
4709 - Tor relays and authorities can now serve clients an abbreviated
4710 version of the consensus document, containing only the changes
4711 since an older consensus document that the client holds. Clients
4712 now request these documents when available. When both client and
4713 server use this new protocol, they will use far less bandwidth (up
4714 to 94% less) to keep the client's consensus up-to-date. Implements
4715 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
4716 - Tor can now compress directory traffic with lzma or with zstd
4717 compression algorithms, which can deliver better bandwidth
4718 performance. Because lzma is computationally expensive, it's only
4719 used for documents that can be compressed once and served many
4720 times. Support for these algorithms requires that tor is built
4721 with the libzstd and/or liblzma libraries available. Implements
4722 proposal 278; closes ticket 21662.
4723 - Relays now perform the more expensive compression operations, and
4724 consensus diff generation, in worker threads. This separation
4725 avoids delaying the main thread when a new consensus arrives.
4727 o Major features (experimental):
4728 - Tor can now build modules written in Rust. To turn this on, pass
4729 the "--enable-rust" flag to the configure script. It's not time to
4730 get excited yet: currently, there is no actual Rust functionality
4731 beyond some simple glue code, and a notice at startup to tell you
4732 that Rust is running. Still, we hope that programmers and
4733 packagers will try building Tor with Rust support, so that we can
4734 find issues and solve portability problems. Closes ticket 22106.
4736 o Major features (traffic analysis resistance):
4737 - Connections between clients and relays now send a padding cell in
4738 each direction every 1.5 to 9.5 seconds (tunable via consensus
4739 parameters). This padding will not resist specialized
4740 eavesdroppers, but it should be enough to make many ISPs' routine
4741 network flow logging less useful in traffic analysis against
4744 Padding is negotiated using Tor's link protocol, so both relays
4745 and clients must upgrade for this to take effect. Clients may
4746 still send padding despite the relay's version by setting
4747 ConnectionPadding 1 in torrc, and may disable padding by setting
4748 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
4749 users with the torrc option ReducedConnectionPadding. Implements
4750 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
4751 - Relays will publish 24 hour totals of padding and non-padding cell
4752 counts to their extra-info descriptors, unless PaddingStatistics 0
4753 is set in torrc. These 24 hour totals are also rounded to
4756 o Major bugfixes (connection usage):
4757 - We use NETINFO cells to try to determine if both relays involved
4758 in a connection will agree on the canonical status of that
4759 connection. We prefer the connections where this is the case for
4760 extend cells, and try to close connections where relays disagree
4761 on their canonical status early. Also, we now prefer the oldest
4762 valid connection for extend cells. These two changes should reduce
4763 the number of long-term connections that are kept open between
4764 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
4765 - Relays now log hourly statistics (look for
4766 "channel_check_for_duplicates" lines) on the total number of
4767 connections to other relays. If the number of connections per
4768 relay is unexpectedly large, this log message is at notice level.
4769 Otherwise it is at info.
4771 o Major bugfixes (entry guards):
4772 - Don't block bootstrapping when a primary bridge is offline and we
4773 can't get its descriptor. Fixes bug 22325; fixes one case of bug
4774 21969; bugfix on 0.3.0.3-alpha.
4776 o Major bugfixes (linux TPROXY support):
4777 - Fix a typo that had prevented TPROXY-based transparent proxying
4778 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
4779 Patch from "d4fq0fQAgoJ".
4781 o Minor features (security, windows):
4782 - Enable a couple of pieces of Windows hardening: one
4783 (HeapEnableTerminationOnCorruption) that has been on-by-default
4784 since Windows 8, and unavailable before Windows 7; and one
4785 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
4786 affect us, but shouldn't do any harm. Closes ticket 21953.
4788 o Minor features (config options):
4789 - Allow "%include" directives in torrc configuration files. These
4790 directives import the settings from other files, or from all the
4791 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
4792 - Make SAVECONF return an error when overwriting a torrc that has
4793 includes. Using SAVECONF with the FORCE option will allow it to
4794 overwrite torrc even if includes are used. Related to ticket 1922.
4795 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
4796 will work without the FORCE option. Related to ticket 1922.
4798 o Minor features (controller):
4799 - Warn the first time that a controller requests data in the long-
4800 deprecated 'GETINFO network-status' format. Closes ticket 21703.
4802 o Minor features (defaults):
4803 - The default value for UseCreateFast is now 0: clients which
4804 haven't yet received a consensus document will now use a proper
4805 ntor handshake to talk to their directory servers whenever they
4806 can. Closes ticket 21407.
4807 - Onion key rotation and expiry intervals are now defined as a
4808 network consensus parameter, per proposal 274. The default
4809 lifetime of an onion key is increased from 7 to 28 days. Old onion
4810 keys will expire after 7 days by default. This change will make
4811 consensus diffs much smaller, and save significant bandwidth.
4812 Closes ticket 21641.
4814 o Minor features (fallback directory list):
4815 - Update the fallback directory mirror whitelist and blacklist based
4816 on operator emails. Closes task 21121.
4817 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4818 December 2016 (of which ~126 were still functional) with a list of
4819 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4820 2017. Resolves ticket 21564.
4822 o Minor features (hidden services, logging):
4823 - Log a message when a hidden service descriptor has fewer
4824 introduction points than specified in
4825 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
4826 - Log a message when a hidden service reaches its introduction point
4827 circuit limit, and when that limit is reset. Follow up to ticket
4828 21594; closes ticket 21622.
4829 - Warn user if multiple entries in EntryNodes and at least one
4830 HiddenService are used together. Pinning EntryNodes along with a
4831 hidden service can be possibly harmful; for instance see ticket
4832 14917 or 21155. Closes ticket 21155.
4834 o Minor features (linux seccomp2 sandbox):
4835 - We now have a document storage backend compatible with the Linux
4836 seccomp2 sandbox. This backend is used for consensus documents and
4837 diffs between them; in the long term, we'd like to use it for
4838 unparseable directory material too. Closes ticket 21645
4839 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
4840 from 1MB to 16MB. This was necessary with the glibc allocator in
4841 order to allow worker threads to allocate more memory -- which in
4842 turn is necessary because of our new use of worker threads for
4843 compression. Closes ticket 22096.
4845 o Minor features (logging):
4846 - Log files are no longer created world-readable by default.
4847 (Previously, most distributors would store the logs in a non-
4848 world-readable location to prevent inappropriate access. This
4849 change is an extra precaution.) Closes ticket 21729; patch
4852 o Minor features (performance):
4853 - Our Keccak (SHA-3) implementation now accesses memory more
4854 efficiently, especially on little-endian systems. Closes
4856 - Add an O(1) implementation of channel_find_by_global_id(), to
4857 speed some controller functions.
4859 o Minor features (relay, configuration):
4860 - The MyFamily option may now be repeated as many times as desired,
4861 for relays that want to configure large families. Closes ticket
4862 4998; patch by Daniel Pinto.
4864 o Minor features (safety):
4865 - Add an explicit check to extrainfo_parse_entry_from_string() for
4866 NULL inputs. We don't believe this can actually happen, but it may
4867 help silence a warning from the Clang analyzer. Closes
4870 o Minor features (testing):
4871 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
4872 When Tor is compiled with this option, we disable a number of
4873 redundant memory-safety failsafes that are intended to stop bugs
4874 from becoming security issues. This makes it easier to hunt for
4875 bugs that would be security issues without the failsafes turned
4876 on. Closes ticket 21439.
4877 - Add a general event-tracing instrumentation support to Tor. This
4878 subsystem will enable developers and researchers to add fine-
4879 grained instrumentation to their Tor instances, for use when
4880 examining Tor network performance issues. There are no trace
4881 events yet, and event-tracing is off by default unless enabled at
4882 compile time. Implements ticket 13802.
4883 - Improve our version parsing tests: add tests for typical version
4884 components, add tests for invalid versions, including numeric
4885 range and non-numeric prefixes. Unit tests 21278, 21450, and
4886 21507. Partially implements 21470.
4888 o Minor bugfixes (bandwidth accounting):
4889 - Roll over monthly accounting at the configured hour and minute,
4890 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
4891 Found by Andrey Karpov with PVS-Studio.
4893 o Minor bugfixes (code correctness):
4894 - Accurately identify client connections by their lack of peer
4895 authentication. This means that we bail out earlier if asked to
4896 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
4899 o Minor bugfixes (configuration):
4900 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
4901 bug 22252; bugfix on 0.2.9.3-alpha.
4903 o Minor bugfixes (connection lifespan):
4904 - Allow more control over how long TLS connections are kept open:
4905 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
4906 single option called CircuitsAvailableTimeout. Also, allow the
4907 consensus to control the default values for both this preference
4908 and the lifespan of relay-to-relay connections. Fixes bug 17592;
4909 bugfix on 0.2.5.5-alpha.
4910 - Increase the initial circuit build timeout testing frequency, to
4911 help ensure that ReducedConnectionPadding clients finish learning
4912 a timeout before their orconn would expire. The initial testing
4913 rate was set back in the days of TAP and before the Tor Browser
4914 updater, when we had to be much more careful about new clients
4915 making lots of circuits. With this change, a circuit build timeout
4916 is learned in about 15-20 minutes, instead of 100-120 minutes.
4918 o Minor bugfixes (controller):
4919 - GETINFO onions/current and onions/detached no longer respond with
4920 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
4921 - Trigger HS descriptor events on the control port when the client
4922 fails to pick a hidden service directory for a hidden service.
4923 This can happen if all the hidden service directories are in
4924 ExcludeNodes, or they have all been queried within the last 15
4925 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
4927 o Minor bugfixes (directory authority):
4928 - When rejecting a router descriptor for running an obsolete version
4929 of Tor without ntor support, warn about the obsolete tor version,
4930 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
4931 - Prevent the shared randomness subsystem from asserting when
4932 initialized by a bridge authority with an incomplete configuration
4933 file. Fixes bug 21586; bugfix on 0.2.9.8.
4935 o Minor bugfixes (exit-side DNS):
4936 - Fix an untriggerable assertion that checked the output of a
4937 libevent DNS error, so that the assertion actually behaves as
4938 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
4939 Karpov using PVS-Studio.
4941 o Minor bugfixes (fallback directories):
4942 - Make the usage example in updateFallbackDirs.py actually work, and
4943 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
4944 - Decrease the guard flag average required to be a fallback. This
4945 allows us to keep relays that have their guard flag removed when
4946 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
4947 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
4948 bugfix on 0.2.8.1-alpha.
4949 - Make sure fallback directory mirrors have the same address, port,
4950 and relay identity key for at least 30 days before they are
4951 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
4953 o Minor bugfixes (hidden services):
4954 - Stop printing a cryptic warning when a hidden service gets a
4955 request to connect to a virtual port that it hasn't configured.
4956 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
4957 - Simplify hidden service descriptor creation by using an existing
4958 flag to check if an introduction point is established. Fixes bug
4959 21599; bugfix on 0.2.7.2-alpha.
4961 o Minor bugfixes (memory leak):
4962 - Fix a small memory leak at exit from the backtrace handler code.
4963 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
4965 o Minor bugfixes (protocol, logging):
4966 - Downgrade a log statement about unexpected relay cells from "bug"
4967 to "protocol warning", because there is at least one use case
4968 where it can be triggered by a buggy tor implementation. Fixes bug
4969 21293; bugfix on 0.1.1.14-alpha.
4971 o Minor bugfixes (testing):
4972 - Use unbuffered I/O for utility functions around the
4973 process_handle_t type. This fixes unit test failures reported on
4974 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
4975 - Make display of captured unit test log messages consistent. Fixes
4976 bug 21510; bugfix on 0.2.9.3-alpha.
4977 - Make test-network.sh always call chutney's test-network.sh.
4978 Previously, this only worked on systems which had bash installed,
4979 due to some bash-specific code in the script. Fixes bug 19699;
4980 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
4982 o Minor bugfixes (voting consistency):
4983 - Reject version numbers with non-numeric prefixes (such as +, -, or
4984 whitespace). Disallowing whitespace prevents differential version
4985 parsing between POSIX-based and Windows platforms. Fixes bug 21507
4986 and part of 21508; bugfix on 0.0.8pre1.
4988 o Minor bugfixes (windows, relay):
4989 - Resolve "Failure from drain_fd: No error" warnings on Windows
4990 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
4992 o Code simplification and refactoring:
4993 - Break up the 630-line function connection_dir_client_reached_eof()
4994 into a dozen smaller functions. This change should help
4995 maintainability and readability of the client directory code.
4996 - Isolate our use of the openssl headers so that they are only
4997 included from our crypto wrapper modules, and from tests that
4998 examine those modules' internals. Closes ticket 21841.
4999 - Simplify our API to launch directory requests, making it more
5000 extensible and less error-prone. Now it's easier to add extra
5001 headers to directory requests. Closes ticket 21646.
5002 - Our base64 decoding functions no longer overestimate the output
5003 space that they need when parsing unpadded inputs. Closes
5005 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
5006 Resolves ticket 22213.
5007 - The logic that directory caches use to spool request to clients,
5008 serving them one part at a time so as not to allocate too much
5009 memory, has been refactored for consistency. Previously there was
5010 a separate spooling implementation per type of spoolable data. Now
5011 there is one common spooling implementation, with extensible data
5012 types. Closes ticket 21651.
5013 - Tor's compression module now supports multiple backends. Part of
5014 the implementation for proposal 278; closes ticket 21663.
5017 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
5018 Closes ticket 21873.
5019 - Correct documentation about the default DataDirectory value.
5020 Closes ticket 21151.
5021 - Document the default behavior of NumEntryGuards and
5022 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
5024 - Document key=value pluggable transport arguments for Bridge lines
5025 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
5026 - Note that bandwidth-limiting options don't affect TCP headers or
5027 DNS. Closes ticket 17170.
5029 o Removed features (configuration options, all in ticket 22060):
5030 - These configuration options are now marked Obsolete, and no longer
5031 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
5032 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
5033 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
5034 in 0.2.9.2-alpha and have now been removed. The previous default
5035 behavior is now always chosen; the previous (less secure) non-
5036 default behavior is now unavailable.
5037 - CloseHSClientCircuitsImmediatelyOnTimeout and
5038 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
5039 0.2.9.2-alpha and now have been removed. HS circuits never close
5040 on circuit build timeout; they have a longer timeout period.
5041 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
5042 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
5043 (and others) to configure listen-only and advertise-only addresses.
5045 o Removed features (tools):
5046 - We've removed the tor-checkkey tool from src/tools. Long ago, we
5047 used it to help people detect RSA keys that were generated by
5048 versions of Debian affected by CVE-2008-0166. But those keys have
5049 been out of circulation for ages, and this tool is no longer
5050 required. Closes ticket 21842.
5053 Changes in version 0.3.0.7 - 2017-05-15
5054 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
5055 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
5056 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
5057 clients are not affected.
5059 o Major bugfixes (hidden service directory, security):
5060 - Fix an assertion failure in the hidden service directory code, which
5061 could be used by an attacker to remotely cause a Tor relay process to
5062 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
5063 should upgrade. This security issue is tracked as TROVE-2017-002.
5064 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
5067 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
5070 o Minor features (future-proofing):
5071 - Tor no longer refuses to download microdescriptors or descriptors
5072 if they are listed as "published in the future". This change will
5073 eventually allow us to stop listing meaningful "published" dates
5074 in microdescriptor consensuses, and thereby allow us to reduce the
5075 resources required to download consensus diffs by over 50%.
5076 Implements part of ticket 21642; implements part of proposal 275.
5078 o Minor bugfixes (Linux seccomp2 sandbox):
5079 - The getpid() system call is now permitted under the Linux seccomp2
5080 sandbox, to avoid crashing with versions of OpenSSL (and other
5081 libraries) that attempt to learn the process's PID by using the
5082 syscall rather than the VDSO code. Fixes bug 21943; bugfix
5086 Changes in version 0.3.0.6 - 2017-04-26
5087 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
5089 With the 0.3.0 series, clients and relays now use Ed25519 keys to
5090 authenticate their link connections to relays, rather than the old
5091 RSA1024 keys that they used before. (Circuit crypto has been
5092 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
5093 the guard selection and replacement algorithm to behave more robustly
5094 in the presence of unreliable networks, and to resist guard-
5097 This series also includes numerous other small features and bugfixes,
5098 along with more groundwork for the upcoming hidden-services revamp.
5100 Per our stable release policy, we plan to support the Tor 0.3.0
5101 release series for at least the next nine months, or for three months
5102 after the first stable release of the 0.3.1 series: whichever is
5103 longer. If you need a release with long-term support, we recommend
5104 that you stay with the 0.2.9 series.
5106 Below are the changes since 0.3.0.5-rc. For a list of all changes
5107 since 0.2.9, see the ReleaseNotes file.
5109 o Minor features (geoip):
5110 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
5113 o Minor bugfixes (control port):
5114 - The GETINFO extra-info/digest/<digest> command was broken because
5115 of a wrong base16 decode return value check, introduced when
5116 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
5118 o Minor bugfixes (crash prevention):
5119 - Fix a (currently untriggerable, but potentially dangerous) crash
5120 bug when base32-encoding inputs whose sizes are not a multiple of
5121 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
5124 Changes in version 0.3.0.5-rc - 2017-04-05
5125 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
5126 0.3.0 release series.
5128 This is the second release candidate in the Tor 0.3.0 series, and has
5129 much fewer changes than the first. If we find no new bugs or
5130 regressions here, the first stable 0.3.0 release will be nearly
5133 o Major bugfixes (crash, directory connections):
5134 - Fix a rare crash when sending a begin cell on a circuit whose
5135 linked directory connection had already been closed. Fixes bug
5136 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
5138 o Major bugfixes (guard selection):
5139 - Fix a guard selection bug where Tor would refuse to bootstrap in
5140 some cases if the user swapped a bridge for another bridge in
5141 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
5142 Reported by "torvlnt33r".
5144 o Minor features (geoip):
5145 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
5148 o Minor bugfix (compilation):
5149 - Fix a warning when compiling hs_service.c. Previously, it had no
5150 exported symbols when compiled for libor.a, resulting in a
5151 compilation warning from clang. Fixes bug 21825; bugfix
5154 o Minor bugfixes (hidden services):
5155 - Make hidden services check for failed intro point connections,
5156 even when they have exceeded their intro point creation limit.
5157 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
5158 - Make hidden services with 8 to 10 introduction points check for
5159 failed circuits immediately after startup. Previously, they would
5160 wait for 5 minutes before performing their first checks. Fixes bug
5161 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
5163 o Minor bugfixes (memory leaks):
5164 - Fix a memory leak when using GETCONF on a port option. Fixes bug
5165 21682; bugfix on 0.3.0.3-alpha.
5167 o Minor bugfixes (relay):
5168 - Avoid a double-marked-circuit warning that could happen when we
5169 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
5172 o Minor bugfixes (tests):
5173 - Run the entry_guard_parse_from_state_full() test with the time set
5174 to a specific date. (The guard state that this test was parsing
5175 contained guards that had expired since the test was first
5176 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
5179 - Update the description of the directory server options in the
5180 manual page, to clarify that a relay no longer needs to set
5181 DirPort in order to be a directory cache. Closes ticket 21720.
5185 Changes in version 0.2.8.13 - 2017-03-03
5186 Tor 0.2.8.13 backports a security fix from later Tor
5187 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
5188 this release, if for some reason they cannot upgrade to a later
5189 release series, and if they build Tor with the --enable-expensive-hardening
5192 Note that support for Tor 0.2.8.x is ending next year: we will not issue
5193 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
5194 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5196 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5197 - Fix an integer underflow bug when comparing malformed Tor
5198 versions. This bug could crash Tor when built with
5199 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5200 0.2.9.8, which were built with -ftrapv by default. In other cases
5201 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5202 on 0.0.8pre1. Found by OSS-Fuzz.
5204 o Minor features (geoip):
5205 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5209 Changes in version 0.2.7.7 - 2017-03-03
5210 Tor 0.2.7.7 backports a number of security fixes from later Tor
5211 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
5212 this release, if for some reason they cannot upgrade to a later
5215 Note that support for Tor 0.2.7.x is ending this year: we will not issue
5216 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
5217 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5219 o Directory authority changes (backport from 0.2.8.5-rc):
5220 - Urras is no longer a directory authority. Closes ticket 19271.
5222 o Directory authority changes (backport from 0.2.9.2-alpha):
5223 - The "Tonga" bridge authority has been retired; the new bridge
5224 authority is "Bifroest". Closes tickets 19728 and 19690.
5226 o Directory authority key updates (backport from 0.2.8.1-alpha):
5227 - Update the V3 identity key for the dannenberg directory authority:
5228 it was changed on 18 November 2015. Closes task 17906. Patch
5231 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5232 - Fix a bug in parsing that could cause clients to read a single
5233 byte past the end of an allocated region. This bug could be used
5234 to cause hardened clients (built with --enable-expensive-hardening)
5235 to crash if they tried to visit a hostile hidden service. Non-
5236 hardened clients are only affected depending on the details of
5237 their platform's memory allocator. Fixes bug 21018; bugfix on
5238 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5239 2016-12-002 and as CVE-2016-1254.
5241 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5242 - Stop a crash that could occur when a client running with DNSPort
5243 received a query with multiple address types, and the first
5244 address type was not supported. Found and fixed by Scott Dial.
5245 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5246 - Prevent a class of security bugs caused by treating the contents
5247 of a buffer chunk as if they were a NUL-terminated string. At
5248 least one such bug seems to be present in all currently used
5249 versions of Tor, and would allow an attacker to remotely crash
5250 most Tor instances, especially those compiled with extra compiler
5251 hardening. With this defense in place, such bugs can't crash Tor,
5252 though we should still fix them as they occur. Closes ticket
5253 20384 (TROVE-2016-10-001).
5255 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5256 - Avoid a difficult-to-trigger heap corruption attack when extending
5257 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5258 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5259 Reported by Guido Vranken.
5261 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5262 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5263 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5265 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5266 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5267 pointer to the previous (uninitialized) key value. The impact here
5268 should be limited to a difficult-to-trigger crash, if OpenSSL is
5269 running an engine that makes key generation failures possible, or
5270 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5271 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5274 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5275 - Fix an integer underflow bug when comparing malformed Tor
5276 versions. This bug could crash Tor when built with
5277 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5278 0.2.9.8, which were built with -ftrapv by default. In other cases
5279 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5280 on 0.0.8pre1. Found by OSS-Fuzz.
5282 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5283 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5284 zero size. Check size argument to memwipe() for underflow. Fixes
5285 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5288 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5289 - Make Tor survive errors involving connections without a
5290 corresponding event object. Previously we'd fail with an
5291 assertion; now we produce a log message. Related to bug 16248.
5293 o Minor features (geoip):
5294 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5298 Changes in version 0.2.6.11 - 2017-03-03
5299 Tor 0.2.6.11 backports a number of security fixes from later Tor
5300 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
5301 this release, if for some reason they cannot upgrade to a later
5304 Note that support for Tor 0.2.6.x is ending this year: we will not issue
5305 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
5306 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5308 o Directory authority changes (backport from 0.2.8.5-rc):
5309 - Urras is no longer a directory authority. Closes ticket 19271.
5311 o Directory authority changes (backport from 0.2.9.2-alpha):
5312 - The "Tonga" bridge authority has been retired; the new bridge
5313 authority is "Bifroest". Closes tickets 19728 and 19690.
5315 o Directory authority key updates (backport from 0.2.8.1-alpha):
5316 - Update the V3 identity key for the dannenberg directory authority:
5317 it was changed on 18 November 2015. Closes task 17906. Patch
5320 o Major features (security fixes, backport from 0.2.9.4-alpha):
5321 - Prevent a class of security bugs caused by treating the contents
5322 of a buffer chunk as if they were a NUL-terminated string. At
5323 least one such bug seems to be present in all currently used
5324 versions of Tor, and would allow an attacker to remotely crash
5325 most Tor instances, especially those compiled with extra compiler
5326 hardening. With this defense in place, such bugs can't crash Tor,
5327 though we should still fix them as they occur. Closes ticket
5328 20384 (TROVE-2016-10-001).
5330 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5331 - Fix a bug in parsing that could cause clients to read a single
5332 byte past the end of an allocated region. This bug could be used
5333 to cause hardened clients (built with --enable-expensive-hardening)
5334 to crash if they tried to visit a hostile hidden service. Non-
5335 hardened clients are only affected depending on the details of
5336 their platform's memory allocator. Fixes bug 21018; bugfix on
5337 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5338 2016-12-002 and as CVE-2016-1254.
5340 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5341 - Stop a crash that could occur when a client running with DNSPort
5342 received a query with multiple address types, and the first
5343 address type was not supported. Found and fixed by Scott Dial.
5344 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5346 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5347 - Fix an error that could cause us to read 4 bytes before the
5348 beginning of an openssl string. This bug could be used to cause
5349 Tor to crash on systems with unusual malloc implementations, or
5350 systems with unusual hardening installed. Fixes bug 17404; bugfix
5353 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5354 - Avoid a difficult-to-trigger heap corruption attack when extending
5355 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5356 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5357 Reported by Guido Vranken.
5359 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5360 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5361 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5363 o Major bugfixes (guard selection, backport from 0.2.7.6):
5364 - Actually look at the Guard flag when selecting a new directory
5365 guard. When we implemented the directory guard design, we
5366 accidentally started treating all relays as if they have the Guard
5367 flag during guard selection, leading to weaker anonymity and worse
5368 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5371 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5372 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5373 pointer to the previous (uninitialized) key value. The impact here
5374 should be limited to a difficult-to-trigger crash, if OpenSSL is
5375 running an engine that makes key generation failures possible, or
5376 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5377 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5380 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5381 - Fix an integer underflow bug when comparing malformed Tor
5382 versions. This bug could crash Tor when built with
5383 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5384 0.2.9.8, which were built with -ftrapv by default. In other cases
5385 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5386 on 0.0.8pre1. Found by OSS-Fuzz.
5388 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5389 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5390 zero size. Check size argument to memwipe() for underflow. Fixes
5391 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5394 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5395 - Make Tor survive errors involving connections without a
5396 corresponding event object. Previously we'd fail with an
5397 assertion; now we produce a log message. Related to bug 16248.
5399 o Minor features (geoip):
5400 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5403 o Minor bugfixes (compilation, backport from 0.2.7.6):
5404 - Fix a compilation warning with Clang 3.6: Do not check the
5405 presence of an address which can never be NULL. Fixes bug 17781.
5408 Changes in version 0.2.5.13 - 2017-03-03
5409 Tor 0.2.5.13 backports a number of security fixes from later Tor
5410 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
5411 this release, if for some reason they cannot upgrade to a later
5414 Note that support for Tor 0.2.5.x is ending next year: we will not issue
5415 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
5416 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5418 o Directory authority changes (backport from 0.2.8.5-rc):
5419 - Urras is no longer a directory authority. Closes ticket 19271.
5421 o Directory authority changes (backport from 0.2.9.2-alpha):
5422 - The "Tonga" bridge authority has been retired; the new bridge
5423 authority is "Bifroest". Closes tickets 19728 and 19690.
5425 o Directory authority key updates (backport from 0.2.8.1-alpha):
5426 - Update the V3 identity key for the dannenberg directory authority:
5427 it was changed on 18 November 2015. Closes task 17906. Patch
5430 o Major features (security fixes, backport from 0.2.9.4-alpha):
5431 - Prevent a class of security bugs caused by treating the contents
5432 of a buffer chunk as if they were a NUL-terminated string. At
5433 least one such bug seems to be present in all currently used
5434 versions of Tor, and would allow an attacker to remotely crash
5435 most Tor instances, especially those compiled with extra compiler
5436 hardening. With this defense in place, such bugs can't crash Tor,
5437 though we should still fix them as they occur. Closes ticket
5438 20384 (TROVE-2016-10-001).
5440 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5441 - Fix a bug in parsing that could cause clients to read a single
5442 byte past the end of an allocated region. This bug could be used
5443 to cause hardened clients (built with --enable-expensive-hardening)
5444 to crash if they tried to visit a hostile hidden service. Non-
5445 hardened clients are only affected depending on the details of
5446 their platform's memory allocator. Fixes bug 21018; bugfix on
5447 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5448 2016-12-002 and as CVE-2016-1254.
5450 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5451 - Stop a crash that could occur when a client running with DNSPort
5452 received a query with multiple address types, and the first
5453 address type was not supported. Found and fixed by Scott Dial.
5454 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5456 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5457 - Fix an error that could cause us to read 4 bytes before the
5458 beginning of an openssl string. This bug could be used to cause
5459 Tor to crash on systems with unusual malloc implementations, or
5460 systems with unusual hardening installed. Fixes bug 17404; bugfix
5463 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5464 - Avoid a difficult-to-trigger heap corruption attack when extending
5465 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5466 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5467 Reported by Guido Vranken.
5469 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5470 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5471 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5473 o Major bugfixes (guard selection, backport from 0.2.7.6):
5474 - Actually look at the Guard flag when selecting a new directory
5475 guard. When we implemented the directory guard design, we
5476 accidentally started treating all relays as if they have the Guard
5477 flag during guard selection, leading to weaker anonymity and worse
5478 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5481 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5482 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5483 pointer to the previous (uninitialized) key value. The impact here
5484 should be limited to a difficult-to-trigger crash, if OpenSSL is
5485 running an engine that makes key generation failures possible, or
5486 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5487 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5490 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5491 - Fix an integer underflow bug when comparing malformed Tor
5492 versions. This bug could crash Tor when built with
5493 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5494 0.2.9.8, which were built with -ftrapv by default. In other cases
5495 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5496 on 0.0.8pre1. Found by OSS-Fuzz.
5498 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5499 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5500 zero size. Check size argument to memwipe() for underflow. Fixes
5501 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5504 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5505 - Make Tor survive errors involving connections without a
5506 corresponding event object. Previously we'd fail with an
5507 assertion; now we produce a log message. Related to bug 16248.
5509 o Minor features (geoip):
5510 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5513 o Minor bugfixes (compilation, backport from 0.2.7.6):
5514 - Fix a compilation warning with Clang 3.6: Do not check the
5515 presence of an address which can never be NULL. Fixes bug 17781.
5517 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
5518 - Check for failures from crypto_early_init, and refuse to continue.
5519 A previous typo meant that we could keep going with an
5520 uninitialized crypto library, and would have OpenSSL initialize
5521 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
5522 when implementing ticket 4900. Patch by "teor".
5524 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5525 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5526 a client authorized hidden service. Fixes bug 15823; bugfix
5530 Changes in version 0.2.4.28 - 2017-03-03
5531 Tor 0.2.4.28 backports a number of security fixes from later Tor
5532 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
5533 this release, if for some reason they cannot upgrade to a later
5536 Note that support for Tor 0.2.4.x is ending soon: we will not issue
5537 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
5538 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
5540 o Directory authority changes (backport from 0.2.8.5-rc):
5541 - Urras is no longer a directory authority. Closes ticket 19271.
5543 o Directory authority changes (backport from 0.2.9.2-alpha):
5544 - The "Tonga" bridge authority has been retired; the new bridge
5545 authority is "Bifroest". Closes tickets 19728 and 19690.
5547 o Directory authority key updates (backport from 0.2.8.1-alpha):
5548 - Update the V3 identity key for the dannenberg directory authority:
5549 it was changed on 18 November 2015. Closes task 17906. Patch
5552 o Major features (security fixes, backport from 0.2.9.4-alpha):
5553 - Prevent a class of security bugs caused by treating the contents
5554 of a buffer chunk as if they were a NUL-terminated string. At
5555 least one such bug seems to be present in all currently used
5556 versions of Tor, and would allow an attacker to remotely crash
5557 most Tor instances, especially those compiled with extra compiler
5558 hardening. With this defense in place, such bugs can't crash Tor,
5559 though we should still fix them as they occur. Closes ticket
5560 20384 (TROVE-2016-10-001).
5562 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5563 - Fix a bug in parsing that could cause clients to read a single
5564 byte past the end of an allocated region. This bug could be used
5565 to cause hardened clients (built with --enable-expensive-hardening)
5566 to crash if they tried to visit a hostile hidden service. Non-
5567 hardened clients are only affected depending on the details of
5568 their platform's memory allocator. Fixes bug 21018; bugfix on
5569 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5570 2016-12-002 and as CVE-2016-1254.
5572 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5573 - Fix an error that could cause us to read 4 bytes before the
5574 beginning of an openssl string. This bug could be used to cause
5575 Tor to crash on systems with unusual malloc implementations, or
5576 systems with unusual hardening installed. Fixes bug 17404; bugfix
5579 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5580 - Avoid a difficult-to-trigger heap corruption attack when extending
5581 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5582 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5583 Reported by Guido Vranken.
5585 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5586 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5587 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5589 o Major bugfixes (guard selection, backport from 0.2.7.6):
5590 - Actually look at the Guard flag when selecting a new directory
5591 guard. When we implemented the directory guard design, we
5592 accidentally started treating all relays as if they have the Guard
5593 flag during guard selection, leading to weaker anonymity and worse
5594 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5597 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5598 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5599 pointer to the previous (uninitialized) key value. The impact here
5600 should be limited to a difficult-to-trigger crash, if OpenSSL is
5601 running an engine that makes key generation failures possible, or
5602 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5603 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5606 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5607 - Fix an integer underflow bug when comparing malformed Tor
5608 versions. This bug could crash Tor when built with
5609 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5610 0.2.9.8, which were built with -ftrapv by default. In other cases
5611 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5612 on 0.0.8pre1. Found by OSS-Fuzz.
5614 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5615 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5616 zero size. Check size argument to memwipe() for underflow. Fixes
5617 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5620 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5621 - Make Tor survive errors involving connections without a
5622 corresponding event object. Previously we'd fail with an
5623 assertion; now we produce a log message. Related to bug 16248.
5625 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
5626 - Make it harder for attackers to overload hidden services with
5627 introductions, by blocking multiple introduction requests on the
5628 same circuit. Resolves ticket 15515.
5630 o Minor features (geoip):
5631 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5634 o Minor bugfixes (compilation, backport from 0.2.7.6):
5635 - Fix a compilation warning with Clang 3.6: Do not check the
5636 presence of an address which can never be NULL. Fixes bug 17781.
5638 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5639 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5640 a client authorized hidden service. Fixes bug 15823; bugfix
5644 Changes in version 0.3.0.4-rc - 2017-03-01
5645 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
5646 0.3.0 release series, and introduces a few reliability features to
5647 keep them from coming back.
5649 This is the first release candidate in the Tor 0.3.0 series. If we
5650 find no new bugs or regressions here, the first stable 0.3.0 release
5651 will be nearly identical to it.
5653 o Major bugfixes (bridges):
5654 - When the same bridge is configured multiple times with the same
5655 identity, but at different address:port combinations, treat those
5656 bridge instances as separate guards. This fix restores the ability
5657 of clients to configure the same bridge with multiple pluggable
5658 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
5660 o Major bugfixes (hidden service directory v3):
5661 - Stop crashing on a failed v3 hidden service descriptor lookup
5662 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
5664 o Major bugfixes (parsing):
5665 - When parsing a malformed content-length field from an HTTP
5666 message, do not read off the end of the buffer. This bug was a
5667 potential remote denial-of-service attack against Tor clients and
5668 relays. A workaround was released in October 2016, to prevent this
5669 bug from crashing Tor. This is a fix for the underlying issue,
5670 which should no longer matter (if you applied the earlier patch).
5671 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
5672 using AFL (http://lcamtuf.coredump.cx/afl/).
5673 - Fix an integer underflow bug when comparing malformed Tor
5674 versions. This bug could crash Tor when built with
5675 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5676 0.2.9.8, which were built with -ftrapv by default. In other cases
5677 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5678 on 0.0.8pre1. Found by OSS-Fuzz.
5680 o Minor feature (protocol versioning):
5681 - Add new protocol version for proposal 224. HSIntro now advertises
5682 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
5684 o Minor features (directory authorities):
5685 - Directory authorities now reject descriptors that claim to be
5686 malformed versions of Tor. Helps prevent exploitation of
5688 - Reject version numbers with components that exceed INT32_MAX.
5689 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
5690 Fixes bug 21450; bugfix on 0.0.8pre1.
5691 - Directory authorities now reject relays running versions
5692 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
5693 suffer from bug 20499 and don't keep their consensus cache
5694 up-to-date. Resolves ticket 20509.
5696 o Minor features (geoip):
5697 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5700 o Minor features (reliability, crash):
5701 - Try better to detect problems in buffers where they might grow (or
5702 think they have grown) over 2 GB in size. Diagnostic for
5705 o Minor features (testing):
5706 - During 'make test-network-all', if tor logs any warnings, ask
5707 chutney to output them. Requires a recent version of chutney with
5708 the 21572 patch. Implements 21570.
5710 o Minor bugfixes (certificate expiration time):
5711 - Avoid using link certificates that don't become valid till some
5712 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
5714 o Minor bugfixes (code correctness):
5715 - Repair a couple of (unreachable or harmless) cases of the risky
5716 comparison-by-subtraction pattern that caused bug 21278.
5717 - Remove a redundant check for the UseEntryGuards option from the
5718 options_transition_affects_guards() function. Fixes bug 21492;
5719 bugfix on 0.3.0.1-alpha.
5721 o Minor bugfixes (directory mirrors):
5722 - Allow relays to use directory mirrors without a DirPort: these
5723 relays need to be contacted over their ORPorts using a begindir
5724 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
5725 - Clarify the message logged when a remote relay is unexpectedly
5726 missing an ORPort or DirPort: users were confusing this with a
5727 local port. Fixes another case of bug 20711; bugfix
5730 o Minor bugfixes (guards):
5731 - Don't warn about a missing guard state on timeout-measurement
5732 circuits: they aren't supposed to be using guards. Fixes an
5733 instance of bug 21007; bugfix on 0.3.0.1-alpha.
5734 - Silence a BUG() warning when attempting to use a guard whose
5735 descriptor we don't know, and make this scenario less likely to
5736 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
5738 o Minor bugfixes (hidden service):
5739 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
5740 cells. Previously, we were using sizeof() on a pointer, instead of
5741 the real destination buffer. Fortunately, that value was only used
5742 to double-check that there was enough room--which was already
5743 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
5745 o Minor bugfixes (testing):
5746 - Fix Raspbian build issues related to missing socket errno in
5747 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
5749 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
5750 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
5751 - Use bash in src/test/test-network.sh. This ensures we reliably
5752 call chutney's newer tools/test-network.sh when available. Fixes
5753 bug 21562; bugfix on 0.2.9.1-alpha.
5756 - Small fixes to the fuzzing documentation. Closes ticket 21472.
5759 Changes in version 0.2.9.10 - 2017-03-01
5760 Tor 0.2.9.10 backports a security fix from later Tor release. It also
5761 includes fixes for some major issues affecting directory authorities,
5762 LibreSSL compatibility, and IPv6 correctness.
5764 The Tor 0.2.9.x release series is now marked as a long-term-support
5765 series. We intend to backport security fixes to 0.2.9.x until at
5766 least January of 2020.
5768 o Major bugfixes (directory authority, 0.3.0.3-alpha):
5769 - During voting, when marking a relay as a probable sybil, do not
5770 clear its BadExit flag: sybils can still be bad in other ways
5771 too. (We still clear the other flags.) Fixes bug 21108; bugfix
5774 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
5775 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
5776 any IPv6 addresses. Instead, only reject a port over IPv6 if the
5777 exit policy rejects that port on more than an IPv6 /16 of
5778 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
5779 which rejected a relay's own IPv6 address by default. Fixes bug
5780 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
5782 o Major bugfixes (parsing, also in 0.3.0.4-rc):
5783 - Fix an integer underflow bug when comparing malformed Tor
5784 versions. This bug could crash Tor when built with
5785 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5786 0.2.9.8, which were built with -ftrapv by default. In other cases
5787 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5788 on 0.0.8pre1. Found by OSS-Fuzz.
5790 o Minor features (directory authorities, also in 0.3.0.4-rc):
5791 - Directory authorities now reject descriptors that claim to be
5792 malformed versions of Tor. Helps prevent exploitation of
5794 - Reject version numbers with components that exceed INT32_MAX.
5795 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
5796 Fixes bug 21450; bugfix on 0.0.8pre1.
5798 o Minor features (geoip):
5799 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5802 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
5803 - Autoconf now checks to determine if OpenSSL structures are opaque,
5804 instead of explicitly checking for OpenSSL version numbers. Part
5806 - Support building with recent LibreSSL code that uses opaque
5807 structures. Closes ticket 21359.
5809 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
5810 - Repair a couple of (unreachable or harmless) cases of the risky
5811 comparison-by-subtraction pattern that caused bug 21278.
5813 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
5814 - The tor-resolve command line tool now rejects hostnames over 255
5815 characters in length. Previously, it would silently truncate them,
5816 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
5817 Patch by "junglefowl".
5820 Changes in version 0.3.0.3-alpha - 2017-02-03
5821 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
5822 0.3.0.x development series, including some that could cause
5823 authorities to behave badly. There is also a fix for a longstanding
5824 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
5825 includes some smaller features and bugfixes.
5827 The Tor 0.3.0.x release series is now in patch-freeze: no additional
5828 features will be considered for inclusion in 0.3.0.x. We suspect that
5829 some bugs will probably remain, however, and we encourage people to
5832 o Major bugfixes (directory authority):
5833 - During voting, when marking a relay as a probable sybil, do not
5834 clear its BadExit flag: sybils can still be bad in other ways
5835 too. (We still clear the other flags.) Fixes bug 21108; bugfix
5837 - When deciding whether we have just found a router to be reachable,
5838 do not penalize it for not having performed an Ed25519 link
5839 handshake if it does not claim to support an Ed25519 handshake.
5840 Previously, we would treat such relays as non-running. Fixes bug
5841 21107; bugfix on 0.3.0.1-alpha.
5843 o Major bugfixes (entry guards):
5844 - Stop trying to build circuits through entry guards for which we
5845 have no descriptor. Also, stop crashing in the case that we *do*
5846 accidentally try to build a circuit in such a state. Fixes bug
5847 21242; bugfix on 0.3.0.1-alpha.
5849 o Major bugfixes (IPv6 Exits):
5850 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
5851 any IPv6 addresses. Instead, only reject a port over IPv6 if the
5852 exit policy rejects that port on more than an IPv6 /16 of
5853 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
5854 which rejected a relay's own IPv6 address by default. Fixes bug
5855 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
5857 o Minor feature (client):
5858 - Enable IPv6 traffic on the SocksPort by default. To disable this,
5859 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
5861 o Minor feature (fallback scripts):
5862 - Add a check_existing mode to updateFallbackDirs.py, which checks
5863 if fallbacks in the hard-coded list are working. Closes ticket
5864 20174. Patch by haxxpop.
5866 o Minor features (ciphersuite selection):
5867 - Clients now advertise a list of ciphersuites closer to the ones
5868 preferred by Firefox. Closes part of ticket 15426.
5869 - Allow relays to accept a wider range of ciphersuites, including
5870 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
5872 o Minor features (controller, configuration):
5873 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
5874 and so on, now comes with a __*Port variant that will not be saved
5875 to the torrc file by the controller's SAVECONF command. This
5876 change allows TorBrowser to set up a single-use domain socket for
5877 each time it launches Tor. Closes ticket 20956.
5878 - The GETCONF command can now query options that may only be
5879 meaningful in context-sensitive lists. This allows the controller
5880 to query the mixed SocksPort/__SocksPort style options introduced
5881 in feature 20956. Implements ticket 21300.
5883 o Minor features (portability, compilation):
5884 - Autoconf now checks to determine if OpenSSL structures are opaque,
5885 instead of explicitly checking for OpenSSL version numbers. Part
5887 - Support building with recent LibreSSL code that uses opaque
5888 structures. Closes ticket 21359.
5890 o Minor features (relay):
5891 - We now allow separation of exit and relay traffic to different
5892 source IP addresses, using the OutboundBindAddressExit and
5893 OutboundBindAddressOR options respectively. Closes ticket 17975.
5894 Written by Michael Sonntag.
5896 o Minor bugfix (logging):
5897 - Don't recommend the use of Tor2web in non-anonymous mode.
5898 Recommending Tor2web is a bad idea because the client loses all
5899 anonymity. Tor2web should only be used in specific cases by users
5900 who *know* and understand the issues. Fixes bug 21294; bugfix
5903 o Minor bugfixes (client):
5904 - Always recover from failures in extend_info_from_node(), in an
5905 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
5906 bugfix on 0.2.3.1-alpha.
5908 o Minor bugfixes (client, entry guards):
5909 - Fix a bug warning (with backtrace) when we fail a channel that
5910 circuits to fallback directories on it. Fixes bug 21128; bugfix
5912 - Fix a spurious bug warning (with backtrace) when removing an
5913 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
5914 - Fix a bug of the new guard algorithm where tor could stall for up
5915 to 10 minutes before retrying a guard after a long period of no
5916 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
5917 - Do not try to build circuits until we have descriptors for our
5918 primary entry guards. Related to fix for bug 21242.
5920 o Minor bugfixes (configure, autoconf):
5921 - Rename the configure option --enable-expensive-hardening to
5922 --enable-fragile-hardening. Expensive hardening makes the tor
5923 daemon abort when some kinds of issues are detected. Thus, it
5924 makes tor more at risk of remote crashes but safer against RCE or
5925 heartbleed bug category. We now try to explain this issue in a
5926 message from the configure script. Fixes bug 21290; bugfix
5929 o Minor bugfixes (controller):
5930 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
5931 20824; bugfix on 0.3.0.1-alpha.
5933 o Minor bugfixes (hidden service):
5934 - Clean up the code for expiring intro points with no associated
5935 circuits. It was causing, rarely, a service with some expiring
5936 introduction points to not open enough additional introduction
5937 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
5938 - Stop setting the torrc option HiddenServiceStatistics to "0" just
5939 because we're not a bridge or relay. Instead, we preserve whatever
5940 value the user set (or didn't set). Fixes bug 21150; bugfix
5942 - Resolve two possible underflows which could lead to creating and
5943 closing a lot of introduction point circuits in a non-stop loop.
5944 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
5946 o Minor bugfixes (portability):
5947 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
5948 It is supported by OpenBSD itself, and also by most OpenBSD
5949 variants (such as Bitrig). Fixes bug 20980; bugfix
5951 - When mapping a file of length greater than SIZE_MAX, do not
5952 silently truncate its contents. This issue could occur on 32 bit
5953 systems with large file support and files which are larger than 4
5954 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
5956 o Minor bugfixes (tor-resolve):
5957 - The tor-resolve command line tool now rejects hostnames over 255
5958 characters in length. Previously, it would silently truncate them,
5959 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
5960 Patch by "junglefowl".
5962 o Minor bugfixes (Windows services):
5963 - Be sure to initialize the monotonic time subsystem before using
5964 it, even when running as an NT service. Fixes bug 21356; bugfix
5968 Changes in version 0.3.0.2-alpha - 2017-01-23
5969 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
5970 cause relays and clients to crash, even if they were not built with
5971 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
5972 versions, and also affects 0.3.0.1-alpha: all relays running an affected
5973 version should upgrade.
5975 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
5976 time-to-live values, makes directory authorities enforce the 1-to-1
5977 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
5978 client-side onion service reachability bug, does better at selecting
5979 the set of fallback directories, and more.
5981 o Major bugfixes (security, also in 0.2.9.9):
5982 - Downgrade the "-ftrapv" option from "always on" to "only on when
5983 --enable-expensive-hardening is provided." This hardening option, like
5984 others, can turn survivable bugs into crashes--and having it on by
5985 default made a (relatively harmless) integer overflow bug into a
5986 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
5989 o Major features (security):
5990 - Change the algorithm used to decide DNS TTLs on client and server
5991 side, to better resist DNS-based correlation attacks like the
5992 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
5993 Feamster. Now relays only return one of two possible DNS TTL
5994 values, and clients are willing to believe DNS TTL values up to 3
5995 hours long. Closes ticket 19769.
5997 o Major features (directory authority, security):
5998 - The default for AuthDirPinKeys is now 1: directory authorities
5999 will reject relays where the RSA identity key matches a previously
6000 seen value, but the Ed25519 key has changed. Closes ticket 18319.
6002 o Major bugfixes (client, guard, crash):
6003 - In circuit_get_global_origin_list(), return the actual list of
6004 origin circuits. The previous version of this code returned the
6005 list of all the circuits, and could have caused strange bugs,
6006 including possible crashes. Fixes bug 21118; bugfix
6009 o Major bugfixes (client, onion service, also in 0.2.9.9):
6010 - Fix a client-side onion service reachability bug, where multiple
6011 socks requests to an onion service (or a single slow request)
6012 could cause us to mistakenly mark some of the service's
6013 introduction points as failed, and we cache that failure so
6014 eventually we run out and can't reach the service. Also resolves a
6015 mysterious "Remote server sent bogus reason code 65021" log
6016 warning. The bug was introduced in ticket 17218, where we tried to
6017 remember the circuit end reason as a uint16_t, which mangled
6018 negative values. Partially fixes bug 21056 and fixes bug 20307;
6019 bugfix on 0.2.8.1-alpha.
6021 o Major bugfixes (DNS):
6022 - Fix a bug that prevented exit nodes from caching DNS records for
6023 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
6025 o Minor features (controller):
6026 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
6027 shared-random values to the controller. Closes ticket 19925.
6029 o Minor features (entry guards):
6030 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
6031 break regression tests.
6032 - Require UseEntryGuards when UseBridges is set, in order to make
6033 sure bridges aren't bypassed. Resolves ticket 20502.
6035 o Minor features (fallback directories):
6036 - Select 200 fallback directories for each release. Closes
6038 - Allow 3 fallback relays per operator, which is safe now that we
6039 are choosing 200 fallback relays. Closes ticket 20912.
6040 - Exclude relays affected by bug 20499 from the fallback list.
6041 Exclude relays from the fallback list if they are running versions
6042 known to be affected by bug 20499, or if in our tests they deliver
6043 a stale consensus (i.e. one that expired more than 24 hours ago).
6044 Closes ticket 20539.
6045 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
6047 - Require fallback directories to have the same address and port for
6048 7 days (now that we have enough relays with this stability).
6049 Relays whose OnionOO stability timer is reset on restart by bug
6050 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
6051 this issue. Closes ticket 20880; maintains short-term fix
6053 - Require fallbacks to have flags for 90% of the time (weighted
6054 decaying average), rather than 95%. This allows at least 73% of
6055 clients to bootstrap in the first 5 seconds without contacting an
6056 authority. Part of ticket 18828.
6057 - Annotate updateFallbackDirs.py with the bandwidth and consensus
6058 weight for each candidate fallback. Closes ticket 20878.
6059 - Make it easier to change the output sort order of fallbacks.
6060 Closes ticket 20822.
6061 - Display the relay fingerprint when downloading consensuses from
6062 fallbacks. Closes ticket 20908.
6064 o Minor features (geoip, also in 0.2.9.9):
6065 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
6068 o Minor features (next-gen onion service directories):
6069 - Remove the "EnableOnionServicesV3" consensus parameter that we
6070 introduced in 0.3.0.1-alpha: relays are now always willing to act
6071 as v3 onion service directories. Resolves ticket 19899.
6073 o Minor features (linting):
6074 - Enhance the changes file linter to warn on Tor versions that are
6075 prefixed with "tor-". Closes ticket 21096.
6077 o Minor features (logging):
6078 - In several places, describe unset ed25519 keys as "<unset>",
6079 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
6081 o Minor bugfix (control protocol):
6082 - The reply to a "GETINFO config/names" request via the control
6083 protocol now spells the type "Dependent" correctly. This is a
6084 breaking change in the control protocol. (The field seems to be
6085 ignored by the most common known controllers.) Fixes bug 18146;
6086 bugfix on 0.1.1.4-alpha.
6088 o Minor bugfixes (bug resilience):
6089 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
6090 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
6091 Hans Jerry Illikainen.
6093 o Minor bugfixes (build):
6094 - Replace obsolete Autoconf macros with their modern equivalent and
6095 prevent similar issues in the future. Fixes bug 20990; bugfix
6098 o Minor bugfixes (client, guards):
6099 - Fix bug where Tor would think that there are circuits waiting for
6100 better guards even though those circuits have been freed. Fixes
6101 bug 21142; bugfix on 0.3.0.1-alpha.
6103 o Minor bugfixes (config):
6104 - Don't assert on startup when trying to get the options list and
6105 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
6106 options so of course they aren't ready yet. Fixes bug 21062;
6107 bugfix on 0.2.9.3-alpha.
6109 o Minor bugfixes (controller):
6110 - Make the GETINFO interface for inquiring about entry guards
6111 support the new guards backend. Fixes bug 20823; bugfix
6114 o Minor bugfixes (dead code):
6115 - Remove a redundant check for PidFile changes at runtime in
6116 options_transition_allowed(): this check is already performed
6117 regardless of whether the sandbox is active. Fixes bug 21123;
6118 bugfix on 0.2.5.4-alpha.
6120 o Minor bugfixes (documentation):
6121 - Update the tor manual page to document every option that can not
6122 be changed while tor is running. Fixes bug 21122.
6124 o Minor bugfixes (fallback directories):
6125 - Stop failing when a relay has no uptime data in
6126 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
6127 - Avoid checking fallback candidates' DirPorts if they are down in
6128 OnionOO. When a relay operator has multiple relays, this
6129 prioritizes relays that are up over relays that are down. Fixes
6130 bug 20926; bugfix on 0.2.8.3-alpha.
6131 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
6132 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
6134 o Minor bugfixes (guards, bootstrapping):
6135 - When connecting to a directory guard during bootstrap, do not mark
6136 the guard as successful until we receive a good-looking directory
6137 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
6139 o Minor bugfixes (onion services):
6140 - Fix the config reload pruning of old vs new services so it
6141 actually works when both ephemeral and non-ephemeral services are
6142 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
6143 - Allow the number of introduction points to be as low as 0, rather
6144 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
6146 o Minor bugfixes (IPv6):
6147 - Make IPv6-using clients try harder to find an IPv6 directory
6148 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
6149 - When IPv6 addresses have not been downloaded yet (microdesc
6150 consensus documents don't list relay IPv6 addresses), use hard-
6151 coded addresses for authorities, fallbacks, and configured
6152 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
6153 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
6155 o Minor bugfixes (memory leaks):
6156 - Fix a memory leak when configuring hidden services. Fixes bug
6157 20987; bugfix on 0.3.0.1-alpha.
6159 o Minor bugfixes (portability, also in 0.2.9.9):
6160 - Avoid crashing when Tor is built using headers that contain
6161 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
6162 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
6164 - Fix Libevent detection on platforms without Libevent 1 headers
6165 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
6167 o Minor bugfixes (relay):
6168 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
6169 initializing the keys would reset the DataDirectory to 0700
6170 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
6171 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
6173 o Minor bugfixes (testing):
6174 - Remove undefined behavior from the backtrace generator by removing
6175 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
6177 o Minor bugfixes (unit tests):
6178 - Allow the unit tests to pass even when DNS lookups of bogus
6179 addresses do not fail as expected. Fixes bug 20862 and 20863;
6180 bugfix on unit tests introduced in 0.2.8.1-alpha
6181 through 0.2.9.4-alpha.
6183 o Code simplification and refactoring:
6184 - Refactor code to manipulate global_origin_circuit_list into
6185 separate functions. Closes ticket 20921.
6187 o Documentation (formatting):
6188 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
6189 blocks were incorrectly appearing. Closes ticket 20885.
6191 o Documentation (man page):
6192 - Clarify many options in tor.1 and add some min/max values for
6193 HiddenService options. Closes ticket 21058.
6196 Changes in version 0.2.9.9 - 2017-01-23
6197 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
6198 cause relays and clients to crash, even if they were not built with
6199 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
6200 versions, and also affects 0.3.0.1-alpha: all relays running an affected
6201 version should upgrade.
6203 This release also resolves a client-side onion service reachability
6204 bug, and resolves a pair of small portability issues.
6206 o Major bugfixes (security):
6207 - Downgrade the "-ftrapv" option from "always on" to "only on when
6208 --enable-expensive-hardening is provided." This hardening option,
6209 like others, can turn survivable bugs into crashes -- and having
6210 it on by default made a (relatively harmless) integer overflow bug
6211 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
6212 bugfix on 0.2.9.1-alpha.
6214 o Major bugfixes (client, onion service):
6215 - Fix a client-side onion service reachability bug, where multiple
6216 socks requests to an onion service (or a single slow request)
6217 could cause us to mistakenly mark some of the service's
6218 introduction points as failed, and we cache that failure so
6219 eventually we run out and can't reach the service. Also resolves a
6220 mysterious "Remote server sent bogus reason code 65021" log
6221 warning. The bug was introduced in ticket 17218, where we tried to
6222 remember the circuit end reason as a uint16_t, which mangled
6223 negative values. Partially fixes bug 21056 and fixes bug 20307;
6224 bugfix on 0.2.8.1-alpha.
6226 o Minor features (geoip):
6227 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
6230 o Minor bugfixes (portability):
6231 - Avoid crashing when Tor is built using headers that contain
6232 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
6233 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
6235 - Fix Libevent detection on platforms without Libevent 1 headers
6236 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
6239 Changes in version 0.3.0.1-alpha - 2016-12-19
6240 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
6241 series. It strengthens Tor's link and circuit handshakes by
6242 identifying relays by their Ed25519 keys, improves the algorithm that
6243 clients use to choose and maintain their list of guards, and includes
6244 additional backend support for the next-generation hidden service
6245 design. It also contains numerous other small features and
6246 improvements to security, correctness, and performance.
6248 Below are the changes since 0.2.9.8.
6250 o Major features (guard selection algorithm):
6251 - Tor's guard selection algorithm has been redesigned from the
6252 ground up, to better support unreliable networks and restrictive
6253 sets of entry nodes, and to better resist guard-capture attacks by
6254 hostile local networks. Implements proposal 271; closes
6257 o Major features (next-generation hidden services):
6258 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
6259 prop224 aka "Next Generation Hidden Services". Service and clients
6260 don't use this functionality yet. Closes ticket 19043. Based on
6261 initial code by Alec Heifetz.
6262 - Relays now support the HSDir version 3 protocol, so that they can
6263 can store and serve v3 descriptors. This is part of the next-
6264 generation onion service work detailed in proposal 224. Closes
6267 o Major features (protocol, ed25519 identity keys):
6268 - Relays now use Ed25519 to prove their Ed25519 identities and to
6269 one another, and to clients. This algorithm is faster and more
6270 secure than the RSA-based handshake we've been doing until now.
6271 Implements the second big part of proposal 220; Closes
6273 - Clients now support including Ed25519 identity keys in the EXTEND2
6274 cells they generate. By default, this is controlled by a consensus
6275 parameter, currently disabled. You can turn this feature on for
6276 testing by setting ExtendByEd25519ID in your configuration. This
6277 might make your traffic appear different than the traffic
6278 generated by other users, however. Implements part of ticket
6279 15056; part of proposal 220.
6280 - Relays now understand requests to extend to other relays by their
6281 Ed25519 identity keys. When an Ed25519 identity key is included in
6282 an EXTEND2 cell, the relay will only extend the circuit if the
6283 other relay can prove ownership of that identity. Implements part
6284 of ticket 15056; part of proposal 220.
6286 o Major bugfixes (scheduler):
6287 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
6288 caused the channel scheduler to behave more or less randomly,
6289 rather than preferring channels with higher-priority circuits.
6290 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
6292 o Minor features (controller):
6293 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
6294 rather than "unrecognized." Closes ticket 20389; patch from
6297 o Minor features (diagnostic, directory client):
6298 - Warn when we find an unexpected inconsistency in directory
6299 download status objects. Prevents some negative consequences of
6302 o Minor features (directory authority):
6303 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
6304 default) to control whether authorities should try to probe relays
6305 by their Ed25519 link keys. This option will go away in a few
6306 releases--unless we encounter major trouble in our ed25519 link
6307 protocol rollout, in which case it will serve as a safety option.
6309 o Minor features (directory cache):
6310 - Relays and bridges will now refuse to serve the consensus they
6311 have if they know it is too old for a client to use. Closes
6314 o Minor features (ed25519 link handshake):
6315 - Advertise support for the ed25519 link handshake using the
6316 subprotocol-versions mechanism, so that clients can tell which
6317 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
6319 o Minor features (fingerprinting resistance, authentication):
6320 - Extend the length of RSA keys used for TLS link authentication to
6321 2048 bits. (These weren't used for forward secrecy; for forward
6322 secrecy, we used P256.) Closes ticket 13752.
6324 o Minor features (infrastructure):
6325 - Implement smartlist_add_strdup() function. Replaces the use of
6326 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
6328 o Minor bugfixes (client):
6329 - When clients that use bridges start up with a cached consensus on
6330 disk, they were ignoring it and downloading a new one. Now they
6331 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
6333 o Minor bugfixes (configuration):
6334 - Accept non-space whitespace characters after the severity level in
6335 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
6336 - Support "TByte" and "TBytes" units in options given in bytes.
6337 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
6338 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
6340 o Minor bugfixes (consensus weight):
6341 - Add new consensus method that initializes bw weights to 1 instead
6342 of 0. This prevents a zero weight from making it all the way to
6343 the end (happens in small testing networks) and causing an error.
6344 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
6346 o Minor bugfixes (descriptors):
6347 - Correctly recognise downloaded full descriptors as valid, even
6348 when using microdescriptors as circuits. This affects clients with
6349 FetchUselessDescriptors set, and may affect directory authorities.
6350 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
6352 o Minor bugfixes (directory system):
6353 - Download all consensus flavors, descriptors, and authority
6354 certificates when FetchUselessDescriptors is set, regardless of
6355 whether tor is a directory cache or not. Fixes bug 20667; bugfix
6356 on all recent tor versions.
6357 - Bridges and relays now use microdescriptors (like clients do)
6358 rather than old-style router descriptors. Now bridges will blend
6359 in with clients in terms of the circuits they build. Fixes bug
6360 6769; bugfix on 0.2.3.2-alpha.
6362 o Minor bugfixes (ed25519 certificates):
6363 - Correctly interpret ed25519 certificates that would expire some
6364 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
6366 o Minor bugfixes (hidden services):
6367 - Stop ignoring misconfigured hidden services. Instead, refuse to
6368 start tor until the misconfigurations have been corrected. Fixes
6369 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
6372 o Minor bugfixes (memory leak at exit):
6373 - Fix a small harmless memory leak at exit of the previously unused
6374 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
6377 o Minor bugfixes (util):
6378 - When finishing writing a file to disk, if we were about to replace
6379 the file with the temporary file created before and we fail to
6380 replace it, remove the temporary file so it doesn't stay on disk.
6381 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
6383 o Minor bugfixes (Windows):
6384 - Check for getpagesize before using it to mmap files. This fixes
6385 compilation in some MinGW environments. Fixes bug 20530; bugfix on
6386 0.1.2.1-alpha. Reported by "ice".
6388 o Code simplification and refactoring:
6389 - Abolish all global guard context in entrynodes.c; replace with new
6390 guard_selection_t structure as preparation for proposal 271.
6391 Closes ticket 19858.
6392 - Introduce rend_service_is_ephemeral() that tells if given onion
6393 service is ephemeral. Replace unclear NULL-checkings for service
6394 directory with this function. Closes ticket 20526.
6395 - Extract magic numbers in circuituse.c into defined variables.
6396 - Refactor circuit_is_available_for_use to remove unnecessary check.
6397 - Refactor circuit_predict_and_launch_new for readability and
6398 testability. Closes ticket 18873.
6399 - Refactor large if statement in purpose_needs_anonymity to use
6400 switch statement instead. Closes part of ticket 20077.
6401 - Refactor the hashing API to return negative values for errors, as
6402 is done as throughout the codebase. Closes ticket 20717.
6403 - Remove data structures that were used to index or_connection
6404 objects by their RSA identity digests. These structures are fully
6405 redundant with the similar structures used in the
6406 channel abstraction.
6407 - Remove duplicate code in the channel_write_*cell() functions.
6408 Closes ticket 13827; patch from Pingl.
6409 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
6410 use only purpose_needs_anonymity. Closes part of ticket 20077.
6411 - The code to generate and parse EXTEND and EXTEND2 cells has been
6412 replaced with code automatically generated by the
6416 - Include the "TBits" unit in Tor's man page. Fixes part of bug
6417 20622; bugfix on 0.2.5.1-alpha.
6418 - Change '1' to 'weight_scale' in consensus bw weights calculation
6419 comments, as that is reality. Closes ticket 20273. Patch
6421 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
6422 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
6424 - Stop the man page from incorrectly stating that HiddenServiceDir
6425 must already exist. Fixes 20486.
6426 - Clarify that when ClientRejectInternalAddresses is enabled (which
6427 is the default), multicast DNS hostnames for machines on the local
6428 network (of the form *.local) are also rejected. Closes
6432 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
6433 limit for relays running on a single IP applies to authority IP
6434 addresses as well as to non-authority IP addresses. Closes
6436 - The UseDirectoryGuards torrc option no longer exists: all users
6437 that use entry guards will also use directory guards. Related to
6438 proposal 271; implements part of ticket 20831.
6441 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
6442 from "overcaffeinated".
6443 - Perform the coding style checks when running the tests and fail
6444 when coding style violations are found. Closes ticket 5500.
6445 - Add tests for networkstatus_compute_bw_weights_v10.
6446 - Add unit tests circuit_predict_and_launch_new.
6447 - Extract dummy_origin_circuit_new so it can be used by other
6451 Changes in version 0.2.8.12 - 2016-12-19
6452 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
6453 below) where Tor clients could crash when attempting to visit a
6454 hostile hidden service. Clients are recommended to upgrade as packages
6455 become available for their systems.
6457 It also includes an updated list of fallback directories, backported
6460 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
6461 backported to 0.2.8 in the future.
6463 o Major bugfixes (parsing, security, backported from 0.2.9.8):
6464 - Fix a bug in parsing that could cause clients to read a single
6465 byte past the end of an allocated region. This bug could be used
6466 to cause hardened clients (built with --enable-expensive-hardening)
6467 to crash if they tried to visit a hostile hidden service. Non-
6468 hardened clients are only affected depending on the details of
6469 their platform's memory allocator. Fixes bug 21018; bugfix on
6470 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
6471 2016-12-002 and as CVE-2016-1254.
6473 o Minor features (fallback directory list, backported from 0.2.9.8):
6474 - Replace the 81 remaining fallbacks of the 100 originally
6475 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
6476 fallbacks (123 new, 54 existing, 27 removed) generated in December
6477 2016. Resolves ticket 20170.
6479 o Minor features (geoip, backported from 0.2.9.7-rc):
6480 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
6484 Changes in version 0.2.9.8 - 2016-12-19
6485 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
6487 The Tor 0.2.9 series makes mandatory a number of security features
6488 that were formerly optional. It includes support for a new shared-
6489 randomness protocol that will form the basis for next generation
6490 hidden services, includes a single-hop hidden service mode for
6491 optimizing .onion services that don't actually want to be hidden,
6492 tries harder not to overload the directory authorities with excessive
6493 downloads, and supports a better protocol versioning scheme for
6494 improved compatibility with other implementations of the Tor protocol.
6496 And of course, there are numerous other bugfixes and improvements.
6498 This release also includes a fix for a medium-severity issue (bug
6499 21018 below) where Tor clients could crash when attempting to visit a
6500 hostile hidden service. Clients are recommended to upgrade as packages
6501 become available for their systems.
6503 Below are the changes since 0.2.9.7-rc. For a list of all changes
6504 since 0.2.8, see the ReleaseNotes file.
6506 o Major bugfixes (parsing, security):
6507 - Fix a bug in parsing that could cause clients to read a single
6508 byte past the end of an allocated region. This bug could be used
6509 to cause hardened clients (built with --enable-expensive-hardening)
6510 to crash if they tried to visit a hostile hidden service. Non-
6511 hardened clients are only affected depending on the details of
6512 their platform's memory allocator. Fixes bug 21018; bugfix on
6513 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
6514 2016-12-002 and as CVE-2016-1254.
6516 o Minor features (fallback directory list):
6517 - Replace the 81 remaining fallbacks of the 100 originally
6518 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
6519 fallbacks (123 new, 54 existing, 27 removed) generated in December
6520 2016. Resolves ticket 20170.
6523 Changes in version 0.2.9.7-rc - 2016-12-12
6524 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
6525 including a few that had prevented tests from passing on
6528 o Minor features (geoip):
6529 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
6532 o Minor bugfix (build):
6533 - The current Git revision when building from a local repository is
6534 now detected correctly when using git worktrees. Fixes bug 20492;
6535 bugfix on 0.2.3.9-alpha.
6537 o Minor bugfixes (directory authority):
6538 - When computing old Tor protocol line version in protover, we were
6539 looking at 0.2.7.5 twice instead of a specific case for
6540 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
6542 o Minor bugfixes (download scheduling):
6543 - Resolve a "bug" warning when considering a download schedule whose
6544 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
6546 o Minor bugfixes (logging):
6547 - Downgrade a harmless log message about the
6548 pending_entry_connections list from "warn" to "info". Mitigates
6551 o Minor bugfixes (memory leak):
6552 - Fix a small memory leak when receiving AF_UNIX connections on a
6553 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
6554 - When moving a signed descriptor object from a source to an
6555 existing destination, free the allocated memory inside that
6556 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
6558 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
6559 - Fix a memory leak and use-after-free error when removing entries
6560 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
6561 0.2.5.5-alpha. Patch from "cypherpunks".
6563 o Minor bugfixes (portability):
6564 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
6565 Fixes bug 20935; bugfix on 0.2.9.6-rc.
6567 o Minor bugfixes (unit tests):
6568 - Stop expecting NetBSD unit tests to report success for ipfw. Part
6569 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
6570 - Fix tolerances in unit tests for monotonic time comparisons
6571 between nanoseconds and microseconds. Previously, we accepted a 10
6572 us difference only, which is not realistic on every platform's
6573 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
6574 - Remove a double-free in the single onion service unit test. Stop
6575 ignoring a return value. Make future changes less error-prone.
6576 Fixes bug 20864; bugfix on 0.2.9.6-rc.
6579 Changes in version 0.2.8.11 - 2016-12-08
6580 Tor 0.2.8.11 backports fixes for additional portability issues that
6581 could prevent Tor from building correctly on OSX Sierra, or with
6582 OpenSSL 1.1. Affected users should upgrade; others can safely stay
6585 o Minor bugfixes (portability):
6586 - Avoid compilation errors when building on OSX Sierra. Sierra began
6587 to support the getentropy() and clock_gettime() APIs, but created
6588 a few problems in doing so. Tor 0.2.9 has a more thorough set of
6589 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
6590 monotonic time interfaces. Fixes bug 20865. Bugfix
6593 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
6594 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
6595 architectures. Closes ticket 20588.
6598 Changes in version 0.2.8.10 - 2016-12-02
6599 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
6600 unusable after they left standby mode. It also backports fixes for
6601 a few portability issues and a small but problematic memory leak.
6603 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
6604 - When Tor leaves standby because of a new application request, open
6605 circuits as needed to serve that request. Previously, we would
6606 potentially wait a very long time. Fixes part of bug 19969; bugfix
6609 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
6610 - Clients now respond to new application stream requests immediately
6611 when they arrive, rather than waiting up to one second before
6612 starting to handle them. Fixes part of bug 19969; bugfix
6615 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
6616 - Work around a bug in the OSX 10.12 SDK that would prevent us from
6617 successfully targeting earlier versions of OSX. Resolves
6620 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
6621 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
6622 20551; bugfix on 0.2.1.1-alpha.
6624 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
6625 - Work around a memory leak in OpenSSL 1.1 when encoding public
6626 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
6628 o Minor features (geoip):
6629 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
6632 Changes in version 0.2.9.6-rc - 2016-12-02
6633 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
6634 version. We hope that it will be ready to become stable soon, and we
6635 encourage everyone to test this release. If no showstopper bugs are
6636 found here, the next 0.2.9 release will be stable.
6638 o Major bugfixes (relay, resolver, logging):
6639 - For relays that don't know their own address, avoid attempting a
6640 local hostname resolve for each descriptor we download. This
6641 will cut down on the number of "Success: chose address 'x.x.x.x'"
6642 log lines, and also avoid confusing clock jumps if the resolver
6643 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
6645 o Minor bugfixes (client, fascistfirewall):
6646 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
6647 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
6649 o Minor bugfixes (hidden services):
6650 - Stop ignoring the anonymity status of saved keys for hidden
6651 services and single onion services when first starting tor.
6652 Instead, refuse to start tor if any hidden service key has been
6653 used in a different hidden service anonymity mode. Fixes bug
6654 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
6656 o Minor bugfixes (portability):
6657 - Work around a bug in the OSX 10.12 SDK that would prevent us from
6658 successfully targeting earlier versions of OSX. Resolves
6660 - Run correctly when built on Windows build environments that
6661 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
6663 o Minor bugfixes (single onion services, Tor2web):
6664 - Stop complaining about long-term one-hop circuits deliberately
6665 created by single onion services and Tor2web. These log messages
6666 are intended to diagnose issue 8387, which relates to circuits
6667 hanging around forever for no reason. Fixes bug 20613; bugfix on
6668 0.2.9.1-alpha. Reported by "pastly".
6670 o Minor bugfixes (unit tests):
6671 - Stop spurious failures in the local interface address discovery
6672 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
6676 - Correct the minimum bandwidth value in torrc.sample, and queue a
6677 corresponding change for torrc.minimal. Closes ticket 20085.
6680 Changes in version 0.2.9.5-alpha - 2016-11-08
6681 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
6682 version. We believe one or two probably remain, and we encourage
6683 everyone to test this release.
6685 o Major bugfixes (client performance):
6686 - Clients now respond to new application stream requests immediately
6687 when they arrive, rather than waiting up to one second before
6688 starting to handle them. Fixes part of bug 19969; bugfix
6691 o Major bugfixes (client reliability):
6692 - When Tor leaves standby because of a new application request, open
6693 circuits as needed to serve that request. Previously, we would
6694 potentially wait a very long time. Fixes part of bug 19969; bugfix
6697 o Major bugfixes (download scheduling):
6698 - When using an exponential backoff schedule, do not give up on
6699 downloading just because we have failed a bunch of times. Since
6700 each delay is longer than the last, retrying indefinitely won't
6701 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
6702 - If a consensus expires while we are waiting for certificates to
6703 download, stop waiting for certificates.
6704 - If we stop waiting for certificates less than a minute after we
6705 started downloading them, do not consider the certificate download
6706 failure a separate failure. Fixes bug 20533; bugfix
6708 - Remove the maximum delay on exponential-backoff scheduling. Since
6709 we now allow an infinite number of failures (see ticket 20536), we
6710 must now allow the time to grow longer on each failure. Fixes part
6711 of bug 20534; bugfix on 0.2.9.1-alpha.
6712 - Make our initial download delays closer to those from 0.2.8. Fixes
6713 another part of bug 20534; bugfix on 0.2.9.1-alpha.
6714 - When determining when to download a directory object, handle times
6715 after 2038 if the operating system supports them. (Someday this
6716 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
6717 - When using exponential backoff in test networks, use a lower
6718 exponent, so the delays do not vary as much. This helps test
6719 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
6721 o Minor features (geoip):
6722 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
6725 o Minor bugfixes (client directory scheduling):
6726 - Treat "relay too busy to answer request" as a failed request and a
6727 reason to back off on our retry frequency. This is safe now that
6728 exponential backoffs retry indefinitely, and avoids a bug where we
6729 would reset our download schedule erroneously. Fixes bug 20593;
6730 bugfix on 0.2.9.1-alpha.
6732 o Minor bugfixes (client, logging):
6733 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
6734 assume all nodes support EXTEND2. Use ntor whenever a key is
6735 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
6736 - On DNSPort, stop logging a BUG warning on a failed hostname
6737 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
6739 o Minor bugfixes (hidden services):
6740 - When configuring hidden services, check every hidden service
6741 directory's permissions. Previously, we only checked the last
6742 hidden service. Fixes bug 20529; bugfix the work to fix 13942
6745 o Minor bugfixes (portability):
6746 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
6747 architectures. Closes ticket 20588.
6748 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
6749 removed the ECDH ciphers which caused the tests to fail on
6750 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
6751 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
6752 20551; bugfix on 0.2.1.1-alpha.
6754 o Minor bugfixes (relay bootstrap):
6755 - Ensure relays don't make multiple connections during bootstrap.
6756 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
6758 o Minor bugfixes (relay):
6759 - Work around a memory leak in OpenSSL 1.1 when encoding public
6760 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
6761 - Avoid a small memory leak when informing worker threads about
6762 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
6763 - Do not try to parallelize workers more than 16x without the user
6764 explicitly configuring us to do so, even if we do detect more than
6765 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
6767 o Minor bugfixes (single onion services):
6768 - Start correctly when creating a single onion service in a
6769 directory that did not previously exist. Fixes bug 20484; bugfix
6772 o Minor bugfixes (testing):
6773 - Avoid a unit test failure on systems with over 16 detectable CPU
6774 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
6777 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
6778 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
6779 - Module-level documentation for several more modules. Closes
6780 tickets 19287 and 19290.
6783 Changes in version 0.2.8.9 - 2016-10-17
6784 Tor 0.2.8.9 backports a fix for a security hole in previous versions
6785 of Tor that would allow a remote attacker to crash a Tor client,
6786 hidden service, relay, or authority. All Tor users should upgrade to
6787 this version, or to 0.2.9.4-alpha. Patches will be released for older
6790 o Major features (security fixes, also in 0.2.9.4-alpha):
6791 - Prevent a class of security bugs caused by treating the contents
6792 of a buffer chunk as if they were a NUL-terminated string. At
6793 least one such bug seems to be present in all currently used
6794 versions of Tor, and would allow an attacker to remotely crash
6795 most Tor instances, especially those compiled with extra compiler
6796 hardening. With this defense in place, such bugs can't crash Tor,
6797 though we should still fix them as they occur. Closes ticket
6798 20384 (TROVE-2016-10-001).
6800 o Minor features (geoip):
6801 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
6805 Changes in version 0.2.9.4-alpha - 2016-10-17
6806 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
6807 that would allow a remote attacker to crash a Tor client, hidden
6808 service, relay, or authority. All Tor users should upgrade to this
6809 version, or to 0.2.8.9. Patches will be released for older versions
6812 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
6813 previous versions of Tor, including the implementation of a feature to
6814 future- proof the Tor ecosystem against protocol changes, some bug
6815 fixes necessary for Tor Browser to use unix domain sockets correctly,
6816 and several portability improvements. We anticipate that this will be
6817 the last alpha in the Tor 0.2.9 series, and that the next release will
6818 be a release candidate.
6820 o Major features (security fixes):
6821 - Prevent a class of security bugs caused by treating the contents
6822 of a buffer chunk as if they were a NUL-terminated string. At
6823 least one such bug seems to be present in all currently used
6824 versions of Tor, and would allow an attacker to remotely crash
6825 most Tor instances, especially those compiled with extra compiler
6826 hardening. With this defense in place, such bugs can't crash Tor,
6827 though we should still fix them as they occur. Closes ticket
6828 20384 (TROVE-2016-10-001).
6830 o Major features (subprotocol versions):
6831 - Tor directory authorities now vote on a set of recommended
6832 subprotocol versions, and on a set of required subprotocol
6833 versions. Clients and relays that lack support for a _required_
6834 subprotocol version will not start; those that lack support for a
6835 _recommended_ subprotocol version will warn the user to upgrade.
6836 Closes ticket 19958; implements part of proposal 264.
6837 - Tor now uses "subprotocol versions" to indicate compatibility.
6838 Previously, versions of Tor looked at the declared Tor version of
6839 a relay to tell whether they could use a given feature. Now, they
6840 should be able to rely on its declared subprotocol versions. This
6841 change allows compatible implementations of the Tor protocol(s) to
6842 exist without pretending to be 100% bug-compatible with particular
6843 releases of Tor itself. Closes ticket 19958; implements part of
6846 o Minor feature (fallback directories):
6847 - Remove broken fallbacks from the hard-coded fallback directory
6848 list. Closes ticket 20190; patch by teor.
6850 o Minor features (client, directory):
6851 - Since authorities now omit all routers that lack the Running and
6852 Valid flags, we assume that any relay listed in the consensus must
6853 have those flags. Closes ticket 20001; implements part of
6856 o Minor features (compilation, portability):
6857 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
6860 o Minor features (development tools, etags):
6861 - Teach the "make tags" Makefile target how to correctly find
6862 "MOCK_IMPL" function definitions. Patch from nherring; closes
6865 o Minor features (geoip):
6866 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
6869 o Minor features (unix domain sockets):
6870 - When configuring a unix domain socket for a SocksPort,
6871 ControlPort, or Hidden service, you can now wrap the address in
6872 quotes, using C-style escapes inside the quotes. This allows unix
6873 domain socket paths to contain spaces.
6875 o Minor features (virtual addresses):
6876 - Increase the maximum number of bits for the IPv6 virtual network
6877 prefix from 16 to 104. In this way, the condition for address
6878 allocation is less restrictive. Closes ticket 20151; feature
6881 o Minor bugfixes (address discovery):
6882 - Stop reordering IP addresses returned by the OS. This makes it
6883 more likely that Tor will guess the same relay IP address every
6884 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
6885 Reported by René Mayrhofer, patch by "cypherpunks".
6887 o Minor bugfixes (client, unix domain sockets):
6888 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
6889 the client address is meaningless. Fixes bug 20261; bugfix
6892 o Minor bugfixes (compilation, OpenBSD):
6893 - Detect Libevent2 functions correctly on systems that provide
6894 libevent2, but where libevent1 is linked with -levent. Fixes bug
6895 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
6897 o Minor bugfixes (configuration):
6898 - When parsing quoted configuration values from the torrc file,
6899 handle windows line endings correctly. Fixes bug 19167; bugfix on
6900 0.2.0.16-alpha. Patch from "Pingl".
6902 o Minor bugfixes (getpass):
6903 - Defensively fix a non-triggerable heap corruption at do_getpass()
6904 to protect ourselves from mistakes in the future. Fixes bug
6905 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
6908 o Minor bugfixes (hidden service):
6909 - Allow hidden services to run on IPv6 addresses even when the
6910 IPv6Exit option is not set. Fixes bug 18357; bugfix
6914 - Add module-level internal documentation for 36 C files that
6915 previously didn't have a high-level overview. Closes ticket #20385.
6917 o Required libraries:
6918 - When building with OpenSSL, Tor now requires version 1.0.1 or
6919 later. OpenSSL 1.0.0 and earlier are no longer supported by the
6920 OpenSSL team, and should not be used. Closes ticket 20303.
6923 Changes in version 0.2.9.3-alpha - 2016-09-23
6924 Tor 0.2.9.3-alpha adds improved support for entities that want to make
6925 high-performance services available through the Tor .onion mechanism
6926 without themselves receiving anonymity as they host those services. It
6927 also tries harder to ensure that all steps on a circuit are using the
6928 strongest crypto possible, strengthens some TLS properties, and
6929 resolves several bugs -- including a pair of crash bugs from the 0.2.8
6930 series. Anybody running an earlier version of 0.2.9.x should upgrade.
6932 o Major bugfixes (crash, also in 0.2.8.8):
6933 - Fix a complicated crash bug that could affect Tor clients
6934 configured to use bridges when replacing a networkstatus consensus
6935 in which one of their bridges was mentioned. OpenBSD users saw
6936 more crashes here, but all platforms were potentially affected.
6937 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
6939 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
6940 - Fix a timing-dependent assertion failure that could occur when we
6941 tried to flush from a circuit after having freed its cells because
6942 of an out-of-memory condition. Fixes bug 20203; bugfix on
6943 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
6946 o Major features (circuit building, security):
6947 - Authorities, relays and clients now require ntor keys in all
6948 descriptors, for all hops (except for rare hidden service protocol
6949 cases), for all circuits, and for all other roles. Part of
6951 - Tor authorities, relays, and clients only use ntor, except for
6952 rare cases in the hidden service protocol. Part of ticket 19163.
6954 o Major features (single-hop "hidden" services):
6955 - Add experimental HiddenServiceSingleHopMode and
6956 HiddenServiceNonAnonymousMode options. When both are set to 1,
6957 every hidden service on a Tor instance becomes a non-anonymous
6958 Single Onion Service. Single Onions make one-hop (direct)
6959 connections to their introduction and renzedvous points. One-hop
6960 circuits make Single Onion servers easily locatable, but clients
6961 remain location-anonymous. This is compatible with the existing
6962 hidden service implementation, and works on the current tor
6963 network without any changes to older relays or clients. Implements
6964 proposal 260, completes ticket 17178. Patch by teor and asn.
6966 o Major features (resource management):
6967 - Tor can now notice it is about to run out of sockets, and
6968 preemptively close connections of lower priority. (This feature is
6969 off by default for now, since the current prioritizing method is
6970 yet not mature enough. You can enable it by setting
6971 "DisableOOSCheck 0", but watch out: it might close some sockets
6972 you would rather have it keep.) Closes ticket 18640.
6974 o Major bugfixes (circuit building):
6975 - Hidden service client-to-intro-point and service-to-rendezvous-
6976 point circuits use the TAP key supplied by the protocol, to avoid
6977 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
6979 o Major bugfixes (compilation, OpenBSD):
6980 - Fix a Libevent-detection bug in our autoconf script that would
6981 prevent Tor from linking successfully on OpenBSD. Patch from
6982 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
6984 o Major bugfixes (hidden services):
6985 - Clients now require hidden services to include the TAP keys for
6986 their intro points in the hidden service descriptor. This prevents
6987 an inadvertent upgrade to ntor, which a malicious hidden service
6988 could use to distinguish clients by consensus version. Fixes bug
6989 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
6991 o Minor features (security, TLS):
6992 - Servers no longer support clients that without AES ciphersuites.
6993 (3DES is no longer considered an acceptable cipher.) We believe
6994 that no such Tor clients currently exist, since Tor has required
6995 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
6997 o Minor feature (fallback directories):
6998 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
6999 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
7000 2016. Closes ticket 20190; patch by teor.
7002 o Minor features (geoip, also in 0.2.8.8):
7003 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
7006 o Minor feature (port flags):
7007 - Add new flags to the *Port options to finer control over which
7008 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
7009 and the synthetic flag OnionTrafficOnly, which is equivalent to
7010 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
7011 18693; patch by "teor".
7013 o Minor features (directory authority):
7014 - After voting, if the authorities decide that a relay is not
7015 "Valid", they no longer include it in the consensus at all. Closes
7016 ticket 20002; implements part of proposal 272.
7018 o Minor features (testing):
7019 - Disable memory protections on OpenBSD when performing our unit
7020 tests for memwipe(). The test deliberately invokes undefined
7021 behavior, and the OpenBSD protections interfere with this. Patch
7022 from "rubiate". Closes ticket 20066.
7024 o Minor features (testing, ipv6):
7025 - Add the single-onion and single-onion-ipv6 chutney targets to
7026 "make test-network-all". This requires a recent chutney version
7027 with the single onion network flavours (git c72a652 or later).
7028 Closes ticket 20072; patch by teor.
7029 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
7030 tests. Remove bridges+hs, as it's somewhat redundant. This
7031 requires a recent chutney version that supports IPv6 clients,
7032 relays, and authorities. Closes ticket 20069; patch by teor.
7034 o Minor features (Tor2web):
7035 - Make Tor2web clients respect ReachableAddresses. This feature was
7036 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
7037 0.2.8.7. Implements feature 20034. Patch by teor.
7039 o Minor features (unit tests):
7040 - We've done significant work to make the unit tests run faster.
7041 - Our link-handshake unit tests now check that when invalid
7042 handshakes fail, they fail with the error messages we expected.
7043 - Our unit testing code that captures log messages no longer
7044 prevents them from being written out if the user asked for them
7045 (by passing --debug or --info or or --notice --warn to the "test"
7046 binary). This change prevents us from missing unexpected log
7047 messages simply because we were looking for others. Related to
7049 - The unit tests now log all warning messages with the "BUG" flag.
7050 Previously, they only logged errors by default. This change will
7051 help us make our testing code more correct, and make sure that we
7052 only hit this code when we mean to. In the meantime, however,
7053 there will be more warnings in the unit test logs than before.
7054 This is preparatory work for ticket 19999.
7055 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
7056 assertion as a test failure.
7058 o Minor bug fixes (circuits):
7059 - Use the CircuitBuildTimeout option whenever
7060 LearnCircuitBuildTimeout is disabled. Previously, we would respect
7061 the option when a user disabled it, but not when it was disabled
7062 because some other option was set. Fixes bug 20073; bugfix on
7063 0.2.4.12-alpha. Patch by teor.
7065 o Minor bugfixes (allocation):
7066 - Change how we allocate memory for large chunks on buffers, to
7067 avoid a (currently impossible) integer overflow, and to waste less
7068 space when allocating unusually large chunks. Fixes bug 20081;
7069 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
7070 - Always include orconfig.h before including any other C headers.
7071 Sometimes, it includes macros that affect the behavior of the
7072 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
7073 first version to use AC_USE_SYSTEM_EXTENSIONS).
7074 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
7075 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
7076 Patch from Gisle Vanem.
7077 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
7078 They apparently require a set of annotations that we aren't
7079 currently using, and they create false positives in our pthreads
7080 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
7082 o Minor bugfixes (directory authority):
7083 - Die with a more useful error when the operator forgets to place
7084 the authority_signing_key file into the keys directory. This
7085 avoids an uninformative assert & traceback about having an invalid
7086 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
7087 - When allowing private addresses, mark Exits that only exit to
7088 private locations as such. Fixes bug 20064; bugfix
7091 o Minor bugfixes (documentation):
7092 - Document the default PathsNeededToBuildCircuits value that's used
7093 by clients when the directory authorities don't set
7094 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
7095 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
7096 - Fix manual for the User option: it takes a username, not a UID.
7097 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
7100 o Minor bugfixes (hidden services):
7101 - Stop logging intro point details to the client log on certain
7102 error conditions. Fixed as part of bug 20012; bugfix on
7103 0.2.4.8-alpha. Patch by teor.
7105 o Minor bugfixes (IPv6, testing):
7106 - Check for IPv6 correctly on Linux when running test networks.
7107 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
7109 o Minor bugfixes (Linux seccomp2 sandbox):
7110 - Add permission to run the sched_yield() and sigaltstack() system
7111 calls, in order to support versions of Tor compiled with asan or
7112 ubsan code that use these calls. Now "sandbox 1" and
7113 "--enable-expensive-hardening" should be compatible on more
7114 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
7116 o Minor bugfixes (logging):
7117 - When logging a message from the BUG() macro, be explicit about
7118 what we were asserting. Previously we were confusing what we were
7119 asserting with what the bug was. Fixes bug 20093; bugfix
7121 - When we are unable to remove the bw_accounting file, do not warn
7122 if the reason we couldn't remove it was that it didn't exist.
7123 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
7125 o Minor bugfixes (option parsing):
7126 - Count unix sockets when counting client listeners (SOCKS, Trans,
7127 NATD, and DNS). This has no user-visible behaviour changes: these
7128 options are set once, and never read. Required for correct
7129 behaviour in ticket 17178. Fixes bug 19677; bugfix on
7130 0.2.6.3-alpha. Patch by teor.
7132 o Minor bugfixes (options):
7133 - Check the consistency of UseEntryGuards and EntryNodes more
7134 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
7136 - Stop changing the configured value of UseEntryGuards on
7137 authorities and Tor2web clients. Fixes bug 20074; bugfix on
7138 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
7141 o Minor bugfixes (Tor2web):
7142 - Prevent Tor2web clients running hidden services, these services
7143 are not anonymous due to the one-hop client paths. Fixes bug
7144 19678. Patch by teor.
7146 o Minor bugfixes (unit tests):
7147 - Fix a shared-random unit test that was failing on big endian
7148 architectures due to internal representation of a integer copied
7149 to a buffer. The test is changed to take a full 32 bytes of data
7150 and use the output of a python script that make the COMMIT and
7151 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
7153 - The tor_tls_server_info_callback unit test no longer crashes when
7154 debug-level logging is turned on. Fixes bug 20041; bugfix
7158 Changes in version 0.2.8.8 - 2016-09-23
7159 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
7160 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
7161 who select public relays as their bridges.
7163 o Major bugfixes (crash):
7164 - Fix a complicated crash bug that could affect Tor clients
7165 configured to use bridges when replacing a networkstatus consensus
7166 in which one of their bridges was mentioned. OpenBSD users saw
7167 more crashes here, but all platforms were potentially affected.
7168 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
7170 o Major bugfixes (relay, OOM handler):
7171 - Fix a timing-dependent assertion failure that could occur when we
7172 tried to flush from a circuit after having freed its cells because
7173 of an out-of-memory condition. Fixes bug 20203; bugfix on
7174 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
7177 o Minor feature (fallback directories):
7178 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
7179 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
7180 2016. Closes ticket 20190; patch by teor.
7182 o Minor features (geoip):
7183 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
7187 Changes in version 0.2.9.2-alpha - 2016-08-24
7188 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
7189 several new features and bugfixes. It also includes an important
7190 authority update and an important bugfix from 0.2.8.7. Everyone who
7191 sets the ReachableAddresses option, and all bridges, are strongly
7192 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
7194 o Directory authority changes (also in 0.2.8.7):
7195 - The "Tonga" bridge authority has been retired; the new bridge
7196 authority is "Bifroest". Closes tickets 19728 and 19690.
7198 o Major bugfixes (client, security, also in 0.2.8.7):
7199 - Only use the ReachableAddresses option to restrict the first hop
7200 in a path. In earlier versions of 0.2.8.x, it would apply to
7201 every hop in the path, with a possible degradation in anonymity
7202 for anyone using an uncommon ReachableAddress setting. Fixes bug
7203 19973; bugfix on 0.2.8.2-alpha.
7205 o Major features (user interface):
7206 - Tor now supports the ability to declare options deprecated, so
7207 that we can recommend that people stop using them. Previously,
7208 this was done in an ad-hoc way. Closes ticket 19820.
7210 o Major bugfixes (directory downloads):
7211 - Avoid resetting download status for consensuses hourly, since we
7212 already have another, smarter retry mechanism. Fixes bug 8625;
7213 bugfix on 0.2.0.9-alpha.
7215 o Minor features (config):
7216 - Warn users when descriptor and port addresses are inconsistent.
7217 Mitigates bug 13953; patch by teor.
7219 o Minor features (geoip):
7220 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
7223 o Minor features (user interface):
7224 - There is a new --list-deprecated-options command-line option to
7225 list all of the deprecated options. Implemented as part of
7228 o Minor bugfixes (code style):
7229 - Fix an integer signedness conversion issue in the case conversion
7230 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
7232 o Minor bugfixes (compilation):
7233 - Build correctly on versions of libevent2 without support for
7234 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
7236 - Fix a compilation warning on GCC versions before 4.6. Our
7237 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
7238 when it is also required as an argument to the compiler pragma.
7239 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
7241 o Minor bugfixes (compilation, also in 0.2.8.7):
7242 - Remove an inappropriate "inline" in tortls.c that was causing
7243 warnings on older versions of GCC. Fixes bug 19903; bugfix
7246 o Minor bugfixes (fallback directories, also in 0.2.8.7):
7247 - Avoid logging a NULL string pointer when loading fallback
7248 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
7249 and 0.2.8.1-alpha. Report and patch by "rubiate".
7251 o Minor bugfixes (logging):
7252 - Log a more accurate message when we fail to dump a microdescriptor.
7253 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
7255 o Minor bugfixes (memory leak):
7256 - Fix a series of slow memory leaks related to parsing torrc files
7257 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
7259 o Deprecated features:
7260 - A number of DNS-cache-related sub-options for client ports are now
7261 deprecated for security reasons, and may be removed in a future
7262 version of Tor. (We believe that client-side DNS caching is a bad
7263 idea for anonymity, and you should not turn it on.) The options
7264 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
7265 UseIPv4Cache, and UseIPv6Cache.
7266 - A number of options are deprecated for security reasons, and may
7267 be removed in a future version of Tor. The options are:
7268 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
7269 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
7270 CloseHSClientCircuitsImmediatelyOnTimeout,
7271 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
7272 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
7273 UseNTorHandshake, and WarnUnsafeSocks.
7274 - The *ListenAddress options are now deprecated as unnecessary: the
7275 corresponding *Port options should be used instead. These options
7276 may someday be removed. The affected options are:
7277 ControlListenAddress, DNSListenAddress, DirListenAddress,
7278 NATDListenAddress, ORListenAddress, SocksListenAddress,
7279 and TransListenAddress.
7282 - Correct the IPv6 syntax in our documentation for the
7283 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
7286 - We no longer include the (dead, deprecated) bufferevent code in
7287 Tor. Closes ticket 19450. Based on a patch from U+039b.
7290 Changes in version 0.2.8.7 - 2016-08-24
7291 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
7292 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
7293 who sets the ReachableAddresses option, and all bridges, are strongly
7294 encouraged to upgrade.
7296 o Directory authority changes:
7297 - The "Tonga" bridge authority has been retired; the new bridge
7298 authority is "Bifroest". Closes tickets 19728 and 19690.
7300 o Major bugfixes (client, security):
7301 - Only use the ReachableAddresses option to restrict the first hop
7302 in a path. In earlier versions of 0.2.8.x, it would apply to
7303 every hop in the path, with a possible degradation in anonymity
7304 for anyone using an uncommon ReachableAddress setting. Fixes bug
7305 19973; bugfix on 0.2.8.2-alpha.
7307 o Minor features (geoip):
7308 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
7311 o Minor bugfixes (compilation):
7312 - Remove an inappropriate "inline" in tortls.c that was causing
7313 warnings on older versions of GCC. Fixes bug 19903; bugfix
7316 o Minor bugfixes (fallback directories):
7317 - Avoid logging a NULL string pointer when loading fallback
7318 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
7319 and 0.2.8.1-alpha. Report and patch by "rubiate".
7322 Changes in version 0.2.9.1-alpha - 2016-08-08
7323 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
7324 series. It improves our support for hardened builds and compiler
7325 warnings, deploys some critical infrastructure for improvements to
7326 hidden services, includes a new timing backend that we hope to use for
7327 better support for traffic padding, makes it easier for programmers to
7328 log unexpected events, and contains other small improvements to
7329 security, correctness, and performance.
7331 Below are the changes since 0.2.8.6.
7333 o New system requirements:
7334 - Tor now requires Libevent version 2.0.10-stable or later. Older
7335 versions of Libevent have less efficient backends for several
7336 platforms, and lack the DNS code that we use for our server-side
7337 DNS support. This implements ticket 19554.
7338 - Tor now requires zlib version 1.2 or later, for security,
7339 efficiency, and (eventually) gzip support. (Back when we started,
7340 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
7341 released in 2003. We recommend the latest version.)
7343 o Major features (build, hardening):
7344 - Tor now builds with -ftrapv by default on compilers that support
7345 it. This option detects signed integer overflow (which C forbids),
7346 and turns it into a hard-failure. We do not apply this option to
7347 code that needs to run in constant time to avoid side-channels;
7348 instead, we use -fwrapv in that code. Closes ticket 17983.
7349 - When --enable-expensive-hardening is selected, stop applying the
7350 clang/gcc sanitizers to code that needs to run in constant time.
7351 Although we are aware of no introduced side-channels, we are not
7352 able to prove that there are none. Related to ticket 17983.
7354 o Major features (compilation):
7355 - Our big list of extra GCC warnings is now enabled by default when
7356 building with GCC (or with anything like Clang that claims to be
7357 GCC-compatible). To make all warnings into fatal compilation
7358 errors, pass --enable-fatal-warnings to configure. Closes
7360 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
7361 turn on C and POSIX extensions. (Previously, we attempted to do
7362 this on an ad hoc basis.) Closes ticket 19139.
7364 o Major features (directory authorities, hidden services):
7365 - Directory authorities can now perform the shared randomness
7366 protocol specified by proposal 250. Using this protocol, directory
7367 authorities generate a global fresh random value every day. In the
7368 future, this value will be used by hidden services to select
7369 HSDirs. This release implements the directory authority feature;
7370 the hidden service side will be implemented in the future as part
7371 of proposal 224. Resolves ticket 16943; implements proposal 250.
7373 o Major features (downloading, random exponential backoff):
7374 - When we fail to download an object from a directory service, wait
7375 for an (exponentially increasing) randomized amount of time before
7376 retrying, rather than a fixed interval as we did before. This
7377 prevents a group of Tor instances from becoming too synchronized,
7378 or a single Tor instance from becoming too predictable, in its
7379 download schedule. Closes ticket 15942.
7381 o Major bugfixes (exit policies):
7382 - Avoid disclosing exit outbound bind addresses, configured port
7383 bind addresses, and local interface addresses in relay descriptors
7384 by default under ExitPolicyRejectPrivate. Instead, only reject
7385 these (otherwise unlisted) addresses if
7386 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
7387 0.2.7.2-alpha. Patch by teor.
7389 o Major bugfixes (hidden service client):
7390 - Allow Tor clients with appropriate controllers to work with
7391 FetchHidServDescriptors set to 0. Previously, this option also
7392 disabled descriptor cache lookup, thus breaking hidden services
7393 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
7395 o Minor features (build, hardening):
7396 - Detect and work around a libclang_rt problem that would prevent
7397 clang from finding __mulodi4() on some 32-bit platforms, and thus
7398 keep -ftrapv from linking on those systems. Closes ticket 19079.
7399 - When building on a system without runtime support for the runtime
7400 hardening options, try to log a useful warning at configuration
7401 time, rather than an incomprehensible warning at link time. If
7402 expensive hardening was requested, this warning becomes an error.
7403 Closes ticket 18895.
7405 o Minor features (code safety):
7406 - In our integer-parsing functions, ensure that maxiumum value we
7407 give is no smaller than the minimum value. Closes ticket 19063;
7410 o Minor features (controller):
7411 - Implement new GETINFO queries for all downloads that use
7412 download_status_t to schedule retries. This allows controllers to
7413 examine the schedule for pending downloads. Closes ticket 19323.
7414 - Allow controllers to configure basic client authorization on
7415 hidden services when they create them with the ADD_ONION control
7416 command. Implements ticket 15588. Patch by "special".
7417 - Fire a STATUS_SERVER controller event whenever the hibernation
7418 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
7420 o Minor features (directory authority):
7421 - Directory authorities now only give the Guard flag to a relay if
7422 they are also giving it the Stable flag. This change allows us to
7423 simplify path selection for clients. It should have minimal effect
7424 in practice, since >99% of Guards already have the Stable flag.
7425 Implements ticket 18624.
7426 - Directory authorities now write their v3-status-votes file out to
7427 disk earlier in the consensus process, so we have a record of the
7428 votes even if we abort the consensus process. Resolves
7431 o Minor features (hidden service):
7432 - Stop being so strict about the payload length of "rendezvous1"
7433 cells. We used to be locked in to the "TAP" handshake length, and
7434 now we can handle better handshakes like "ntor". Resolves
7437 o Minor features (infrastructure, time):
7438 - Tor now uses the operating system's monotonic timers (where
7439 available) for internal fine-grained timing. Previously we would
7440 look at the system clock, and then attempt to compensate for the
7441 clock running backwards. Closes ticket 18908.
7442 - Tor now includes an improved timer backend, so that we can
7443 efficiently support tens or hundreds of thousands of concurrent
7444 timers, as will be needed for some of our planned anti-traffic-
7445 analysis work. This code is based on William Ahern's "timeout.c"
7446 project, which implements a "tickless hierarchical timing wheel".
7447 Closes ticket 18365.
7449 o Minor features (logging):
7450 - Provide a more useful warning message when configured with an
7451 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
7452 - When dumping unparseable router descriptors, optionally store them
7453 in separate files, named by digest, up to a configurable size
7454 limit. You can change the size limit by setting the
7455 MaxUnparseableDescSizeToLog option, and disable this feature by
7456 setting that option to 0. Closes ticket 18322.
7457 - Add a set of macros to check nonfatal assertions, for internal
7458 use. Migrating more of our checks to these should help us avoid
7459 needless crash bugs. Closes ticket 18613.
7461 o Minor features (performance):
7462 - Changer the "optimistic data" extension from "off by default" to
7463 "on by default". The default was ordinarily overridden by a
7464 consensus option, but when clients were bootstrapping for the
7465 first time, they would not have a consensus to get the option
7466 from. Changing this default When fetching a consensus for the
7467 first time, use optimistic data. This saves a round-trip during
7468 startup. Closes ticket 18815.
7470 o Minor features (relay, usability):
7471 - When the directory authorities refuse a bad relay's descriptor,
7472 encourage the relay operator to contact us. Many relay operators
7473 won't notice this line in their logs, but it's a win if even a few
7474 learn why we don't like what their relay was doing. Resolves
7477 o Minor features (testing):
7478 - Let backtrace tests work correctly under AddressSanitizer. Fixes
7479 part of bug 18934; bugfix on 0.2.5.2-alpha.
7480 - Move the test-network.sh script to chutney, and modify tor's test-
7481 network.sh to call the (newer) chutney version when available.
7482 Resolves ticket 19116. Patch by teor.
7483 - Use the lcov convention for marking lines as unreachable, so that
7484 we don't count them when we're generating test coverage data.
7485 Update our coverage tools to understand this convention. Closes
7488 o Minor bugfixes (bootstrap):
7489 - Remember the directory we fetched the consensus or previous
7490 certificates from, and use it to fetch future authority
7491 certificates. This change improves bootstrapping performance.
7492 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
7494 o Minor bugfixes (build):
7495 - The test-stem and test-network makefile targets now depend only on
7496 the tor binary that they are testing. Previously, they depended on
7497 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
7498 patch from "cypherpunks".
7500 o Minor bugfixes (circuits):
7501 - Make sure extend_info_from_router() is only called on servers.
7502 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
7504 o Minor bugfixes (compilation):
7505 - When building with Clang, use a full set of GCC warnings.
7506 (Previously, we included only a subset, because of the way we
7507 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
7509 o Minor bugfixes (directory authority):
7510 - Authorities now sort the "package" lines in their votes, for ease
7511 of debugging. (They are already sorted in consensus documents.)
7512 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
7513 - When parsing a detached signature, make sure we use the length of
7514 the digest algorithm instead of an hardcoded DIGEST256_LEN in
7515 order to avoid comparing bytes out-of-bounds with a smaller digest
7516 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
7518 o Minor bugfixes (documentation):
7519 - Document the --passphrase-fd option in the tor manpage. Fixes bug
7520 19504; bugfix on 0.2.7.3-rc.
7521 - Fix the description of the --passphrase-fd option in the
7522 tor-gencert manpage. The option is used to pass the number of a
7523 file descriptor to read the passphrase from, not to read the file
7524 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
7526 o Minor bugfixes (ephemeral hidden service):
7527 - When deleting an ephemeral hidden service, close its intro points
7528 even if they are not completely open. Fixes bug 18604; bugfix
7531 o Minor bugfixes (guard selection):
7532 - Use a single entry guard even if the NumEntryGuards consensus
7533 parameter is not provided. Fixes bug 17688; bugfix
7535 - Don't mark guards as unreachable if connection_connect() fails.
7536 That function fails for local reasons, so it shouldn't reveal
7537 anything about the status of the guard. Fixes bug 14334; bugfix
7540 o Minor bugfixes (hidden service client):
7541 - Increase the minimum number of internal circuits we preemptively
7542 build from 2 to 3, so a circuit is available when a client
7543 connects to another onion service. Fixes bug 13239; bugfix
7546 o Minor bugfixes (logging):
7547 - When logging a directory ownership mismatch, log the owning
7548 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
7550 o Minor bugfixes (memory leaks):
7551 - Fix a small, uncommon memory leak that could occur when reading a
7552 truncated ed25519 key file. Fixes bug 18956; bugfix
7555 o Minor bugfixes (testing):
7556 - Allow clients to retry HSDirs much faster in test networks. Fixes
7557 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
7558 - Disable ASAN's detection of segmentation faults while running
7559 test_bt.sh, so that we can make sure that our own backtrace
7560 generation code works. Fixes another aspect of bug 18934; bugfix
7561 on 0.2.5.2-alpha. Patch from "cypherpunks".
7562 - Fix the test-network-all target on out-of-tree builds by using the
7563 correct path to the test driver script. Fixes bug 19421; bugfix
7566 o Minor bugfixes (time):
7567 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
7568 bugfix on all released tor versions.
7569 - When computing the difference between two times in milliseconds,
7570 we now round to the nearest millisecond correctly. Previously, we
7571 could sometimes round in the wrong direction. Fixes bug 19428;
7572 bugfix on 0.2.2.2-alpha.
7574 o Minor bugfixes (user interface):
7575 - Display a more accurate number of suppressed messages in the log
7576 rate-limiter. Previously, there was a potential integer overflow
7577 in the counter. Now, if the number of messages hits a maximum, the
7578 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
7580 - Fix a typo in the passphrase prompt for the ed25519 identity key.
7581 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
7583 o Code simplification and refactoring:
7584 - Remove redundant declarations of the MIN macro. Closes
7586 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
7587 Closes ticket 18462; patch from "icanhasaccount".
7588 - Split the 600-line directory_handle_command_get function into
7589 separate functions for different URL types. Closes ticket 16698.
7592 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
7593 ticket 19153. Patch from "U+039b".
7596 - Remove support for "GET /tor/bytes.txt" DirPort request, and
7597 "GETINFO dir-usage" controller request, which were only available
7598 via a compile-time option in Tor anyway. Feature was added in
7599 0.2.2.1-alpha. Resolves ticket 19035.
7600 - There is no longer a compile-time option to disable support for
7601 TransPort. (If you don't want TransPort; just don't use it.) Patch
7602 from "U+039b". Closes ticket 19449.
7605 - Run more workqueue tests as part of "make check". These had
7606 previously been implemented, but you needed to know special
7607 command-line options to enable them.
7608 - We now have unit tests for our code to reject zlib "compression
7609 bombs". (Fortunately, the code works fine.)
7612 Changes in version 0.2.8.6 - 2016-08-02
7614 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
7616 The Tor 0.2.8 series improves client bootstrapping performance,
7617 completes the authority-side implementation of improved identity
7618 keys for relays, and includes numerous bugfixes and performance
7619 improvements throughout the program. This release continues to
7620 improve the coverage of Tor's test suite. For a full list of
7621 changes since Tor 0.2.7, see the ReleaseNotes file.
7623 Changes since 0.2.8.5-rc:
7625 o Minor features (geoip):
7626 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
7629 o Minor bugfixes (compilation):
7630 - Fix a compilation warning in the unit tests on systems where char
7631 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
7633 o Minor bugfixes (fallback directories):
7634 - Remove 1 fallback that was on the hardcoded list, then opted-out,
7635 leaving 89 of the 100 fallbacks originally introduced in Tor
7636 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
7638 o Minor bugfixes (Linux seccomp2 sandbox):
7639 - Allow more syscalls when running with "Sandbox 1" enabled:
7640 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
7641 some systems, these are required for Tor to start. Fixes bug
7642 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
7643 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
7644 so that get_interface_address6_via_udp_socket_hack() can work.
7645 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
7648 Changes in version 0.2.8.5-rc - 2016-07-07
7649 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
7650 series. If we find no new bugs or regressions here, the first stable
7651 0.2.8 release will be identical to it. It has a few small bugfixes
7652 against previous versions.
7654 o Directory authority changes:
7655 - Urras is no longer a directory authority. Closes ticket 19271.
7657 o Major bugfixes (heartbeat):
7658 - Fix a regression that would crash Tor when the periodic
7659 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
7660 0.2.8.1-alpha. Reported by "kubaku".
7662 o Minor features (build):
7663 - Tor now again builds with the recent OpenSSL 1.1 development
7664 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
7665 - When building manual pages, set the timezone to "UTC", so that the
7666 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
7667 Patch from intrigeri.
7669 o Minor bugfixes (fallback directory selection):
7670 - Avoid errors during fallback selection if there are no eligible
7671 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
7674 o Minor bugfixes (IPv6, microdescriptors):
7675 - Don't check node addresses when we only have a routerstatus. This
7676 allows IPv6-only clients to bootstrap by fetching microdescriptors
7677 from fallback directory mirrors. (The microdescriptor consensus
7678 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
7681 o Minor bugfixes (logging):
7682 - Reduce pointlessly verbose log messages when directory servers
7683 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
7684 0.2.8.1-alpha. Patch by teor.
7685 - When a fallback directory changes its fingerprint from the hard-
7686 coded fingerprint, log a less severe, more explanatory log
7687 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
7689 o Minor bugfixes (Linux seccomp2 sandboxing):
7690 - Allow statistics to be written to disk when "Sandbox 1" is
7691 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
7692 0.2.6.1-alpha respectively.
7694 o Minor bugfixes (user interface):
7695 - Remove a warning message "Service [scrubbed] not found after
7696 descriptor upload". This message appears when one uses HSPOST
7697 control command to upload a service descriptor. Since there is
7698 only a descriptor and no service, showing this message is
7699 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
7701 o Fallback directory list:
7702 - Add a comment to the generated fallback directory list that
7703 explains how to comment out unsuitable fallbacks in a way that's
7704 compatible with the stem fallback parser.
7705 - Update fallback whitelist and blacklist based on relay operator
7706 emails. Blacklist unsuitable (non-working, over-volatile)
7707 fallbacks. Resolves ticket 19071. Patch by teor.
7708 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
7709 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
7710 ticket 19071; patch by teor.
7713 Changes in version 0.2.8.4-rc - 2016-06-15
7714 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
7715 If we find no new bugs or regressions here, the first stable 0.2.8
7716 release will be identical to it. It has a few small bugfixes against
7719 o Major bugfixes (user interface):
7720 - Correctly give a warning in the cases where a relay is specified
7721 by nickname, and one such relay is found, but it is not officially
7722 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
7724 o Minor features (build):
7725 - Tor now builds once again with the recent OpenSSL 1.1 development
7726 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
7728 o Minor features (geoip):
7729 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
7732 o Minor bugfixes (compilation):
7733 - Cause the unit tests to compile correctly on mingw64 versions that
7734 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
7736 o Minor bugfixes (downloading):
7737 - Predict more correctly whether we'll be downloading over HTTP when
7738 we determine the maximum length of a URL. This should avoid a
7739 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
7743 Changes in version 0.2.8.3-alpha - 2016-05-26
7744 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
7745 the course of the 0.2.8 development cycle. It improves the behavior of
7746 directory clients, fixes several crash bugs, fixes a gap in compiler
7747 hardening, and allows the full integration test suite to run on
7750 o Major bugfixes (security, client, DNS proxy):
7751 - Stop a crash that could occur when a client running with DNSPort
7752 received a query with multiple address types, and the first
7753 address type was not supported. Found and fixed by Scott Dial.
7754 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7756 o Major bugfixes (security, compilation):
7757 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
7758 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
7759 cause a compiler warning, thereby making other checks fail, and
7760 needlessly disabling compiler-hardening support. Fixes one case of
7761 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
7763 o Major bugfixes (security, directory authorities):
7764 - Fix a crash and out-of-bounds write during authority voting, when
7765 the list of relays includes duplicate ed25519 identity keys. Fixes
7766 bug 19032; bugfix on 0.2.8.2-alpha.
7768 o Major bugfixes (client, bootstrapping):
7769 - Check if bootstrap consensus downloads are still needed when the
7770 linked connection attaches. This prevents tor making unnecessary
7771 begindir-style connections, which are the only directory
7772 connections tor clients make since the fix for 18483 was merged.
7773 - Fix some edge cases where consensus download connections may not
7774 have been closed, even though they were not needed. Related to fix
7776 - Make relays retry consensus downloads the correct number of times,
7777 rather than the more aggressive client retry count. Fixes part of
7779 - Stop downloading consensuses when we have a consensus, even if we
7780 don't have all the certificates for it yet. Fixes bug 18809;
7781 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
7783 o Major bugfixes (directory mirrors):
7784 - Decide whether to advertise begindir support in the the same way
7785 we decide whether to advertise our DirPort. Allowing these
7786 decisions to become out-of-sync led to surprising behavior like
7787 advertising begindir support when hibernation made us not
7788 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
7791 o Major bugfixes (IPv6 bridges, client):
7792 - Actually use IPv6 addresses when selecting directory addresses for
7793 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
7796 o Major bugfixes (key management):
7797 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7798 pointer to the previous (uninitialized) key value. The impact here
7799 should be limited to a difficult-to-trigger crash, if OpenSSL is
7800 running an engine that makes key generation failures possible, or
7801 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7802 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7805 o Major bugfixes (testing):
7806 - Fix a bug that would block 'make test-network-all' on systems where
7807 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
7808 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
7809 bugfix on 0.2.8.1-alpha.
7811 o Minor features (clients):
7812 - Make clients, onion services, and bridge relays always use an
7813 encrypted begindir connection for directory requests. Resolves
7814 ticket 18483. Patch by "teor".
7816 o Minor features (fallback directory mirrors):
7817 - Give each fallback the same weight for client selection; restrict
7818 fallbacks to one per operator; report fallback directory detail
7819 changes when rebuilding list; add new fallback directory mirrors
7820 to the whitelist; and many other minor simplifications and fixes.
7821 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
7822 0.2.8.1-alpha; patch by "teor".
7823 - Replace the 21 fallbacks generated in January 2016 and included in
7824 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
7825 2016. Closes task 17158; patch by "teor".
7827 o Minor features (geoip):
7828 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
7831 o Minor bugfixes (assert, portability):
7832 - Fix an assertion failure in memarea.c on systems where "long" is
7833 shorter than the size of a pointer. Fixes bug 18716; bugfix
7836 o Minor bugfixes (bootstrap):
7837 - Consistently use the consensus download schedule for authority
7838 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
7840 o Minor bugfixes (build):
7841 - Remove a pair of redundant AM_CONDITIONAL declarations from
7842 configure.ac. Fixes one final case of bug 17744; bugfix
7844 - Resolve warnings when building on systems that are concerned with
7845 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
7847 - When libscrypt.h is found, but no libscrypt library can be linked,
7848 treat libscrypt as absent. Fixes bug 19161; bugfix
7851 o Minor bugfixes (client):
7852 - Turn all TestingClientBootstrap* into non-testing torrc options.
7853 This changes simply renames them by removing "Testing" in front of
7854 them and they do not require TestingTorNetwork to be enabled
7855 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
7856 - Make directory node selection more reliable, mainly for IPv6-only
7857 clients and clients with few reachable addresses. Fixes bug 18929;
7858 bugfix on 0.2.8.1-alpha. Patch by "teor".
7860 o Minor bugfixes (controller, microdescriptors):
7861 - Make GETINFO dir/status-vote/current/consensus conform to the
7862 control specification by returning "551 Could not open cached
7863 consensus..." when not caching consensuses. Fixes bug 18920;
7864 bugfix on 0.2.2.6-alpha.
7866 o Minor bugfixes (crypto, portability):
7867 - The SHA3 and SHAKE routines now produce the correct output on Big
7868 Endian systems. No code calls either algorithm yet, so this is
7869 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
7870 - Tor now builds again with the recent OpenSSL 1.1 development
7871 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
7874 o Minor bugfixes (directories):
7875 - When fetching extrainfo documents, compare their SHA256 digests
7876 and Ed25519 signing key certificates with the routerinfo that led
7877 us to fetch them, rather than with the most recent routerinfo.
7878 Otherwise we generate many spurious warnings about mismatches.
7879 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
7881 o Minor bugfixes (logging):
7882 - When we can't generate a signing key because OfflineMasterKey is
7883 set, do not imply that we should have been able to load it. Fixes
7884 bug 18133; bugfix on 0.2.7.2-alpha.
7885 - Stop periodic_event_dispatch() from blasting twelve lines per
7886 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
7887 - When rejecting a misformed INTRODUCE2 cell, only log at
7888 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
7890 o Minor bugfixes (pluggable transports):
7891 - Avoid reporting a spurious error when we decide that we don't need
7892 to terminate a pluggable transport because it has already exited.
7893 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
7895 o Minor bugfixes (pointer arithmetic):
7896 - Fix a bug in memarea_alloc() that could have resulted in remote
7897 heap write access, if Tor had ever passed an unchecked size to
7898 memarea_alloc(). Fortunately, all the sizes we pass to
7899 memarea_alloc() are pre-checked to be less than 128 kilobytes.
7900 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
7903 o Minor bugfixes (relays):
7904 - Consider more config options when relays decide whether to
7905 regenerate their descriptor. Fixes more of bug 12538; bugfix
7907 - Resolve some edge cases where we might launch an ORPort
7908 reachability check even when DisableNetwork is set. Noticed while
7909 fixing bug 18616; bugfix on 0.2.3.9-alpha.
7911 o Minor bugfixes (statistics):
7912 - We now include consensus downloads via IPv6 in our directory-
7913 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
7915 o Minor bugfixes (testing):
7916 - Allow directories in small networks to bootstrap by skipping
7917 DirPort checks when the consensus has no exits. Fixes bug 19003;
7918 bugfix on 0.2.8.1-alpha. Patch by teor.
7919 - Fix a small memory leak that would occur when the
7920 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
7921 bugfix on 0.2.5.2-alpha.
7923 o Minor bugfixes (time handling):
7924 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
7925 field. Otherwise, our unit tests crash on Windows. Fixes bug
7926 18977; bugfix on 0.2.2.25-alpha.
7929 - Document the contents of the 'datadir/keys' subdirectory in the
7930 manual page. Closes ticket 17621.
7931 - Stop recommending use of nicknames to identify relays in our
7932 MapAddress documentation. Closes ticket 18312.
7935 Changes in version 0.2.8.2-alpha - 2016-03-28
7936 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
7937 bugs in earlier versions of Tor, including some that prevented
7938 authorities using Tor 0.2.7.x from running correctly. IPv6 and
7939 directory support should also be much improved.
7941 o New system requirements:
7942 - Tor no longer supports versions of OpenSSL with a broken
7943 implementation of counter mode. (This bug was present in OpenSSL
7944 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
7945 longer runs with, these versions.
7946 - Tor no longer attempts to support platforms where the "time_t"
7947 type is unsigned. (To the best of our knowledge, only OpenVMS does
7948 this, and Tor has never actually built on OpenVMS.) Closes
7950 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
7951 later (released in 2008 and 2009 respectively). If you are
7952 building Tor from the git repository instead of from the source
7953 distribution, and your tools are older than this, you will need to
7954 upgrade. Closes ticket 17732.
7956 o Major bugfixes (security, pointers):
7957 - Avoid a difficult-to-trigger heap corruption attack when extending
7958 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7959 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7960 Reported by Guido Vranken.
7962 o Major bugfixes (bridges, pluggable transports):
7963 - Modify the check for OR connections to private addresses. Allow
7964 bridges on private addresses, including pluggable transports that
7965 ignore the (potentially private) address in the bridge line. Fixes
7966 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
7968 o Major bugfixes (compilation):
7969 - Repair hardened builds under the clang compiler. Previously, our
7970 use of _FORTIFY_SOURCE would conflict with clang's address
7971 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
7973 o Major bugfixes (crash on shutdown):
7974 - Correctly handle detaching circuits from muxes when shutting down.
7975 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
7976 - Fix an assert-on-exit bug related to counting memory usage in
7977 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
7979 o Major bugfixes (crash on startup):
7980 - Fix a segfault during startup: If a Unix domain socket was
7981 configured as listener (such as a ControlSocket or a SocksPort
7982 "unix:" socket), and tor was started as root but not configured to
7983 switch to another user, tor would segfault while trying to string
7984 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
7987 o Major bugfixes (dns proxy mode, crash):
7988 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7989 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7991 o Major bugfixes (relays, bridge clients):
7992 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
7993 bridge clients use the address configured in the bridge line.
7994 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
7997 o Major bugfixes (voting):
7998 - Actually enable support for authorities to match routers by their
7999 Ed25519 identities. Previously, the code had been written, but
8000 some debugging code that had accidentally been left in the
8001 codebase made it stay turned off. Fixes bug 17702; bugfix
8003 - When collating votes by Ed25519 identities, authorities now
8004 include a "NoEdConsensus" flag if the ed25519 value (or lack
8005 thereof) for a server does not reflect the majority consensus.
8006 Related to bug 17668; bugfix on 0.2.7.2-alpha.
8007 - When generating a vote with keypinning disabled, never include two
8008 entries for the same ed25519 identity. This bug was causing
8009 authorities to generate votes that they could not parse when a
8010 router violated key pinning by changing its RSA identity but
8011 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
8012 18318. Bugfix on 0.2.7.2-alpha.
8014 o Minor features (security, win32):
8015 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
8016 attack. Fixes bug 18123; bugfix on all tor versions. Patch
8019 o Minor features (bug-resistance):
8020 - Make Tor survive errors involving connections without a
8021 corresponding event object. Previously we'd fail with an
8022 assertion; now we produce a log message. Related to bug 16248.
8024 o Minor features (build):
8025 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
8026 as having possible IPFW support. Closes ticket 18448. Patch from
8029 o Minor features (code hardening):
8030 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
8031 level code, to harden against accidental failures to NUL-
8032 terminate. Part of ticket 17852. Patch from jsturgix. Found
8035 o Minor features (crypto):
8036 - Validate the hard-coded Diffie-Hellman parameters and ensure that
8037 p is a safe prime, and g is a suitable generator. Closes
8040 o Minor features (geoip):
8041 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
8044 o Minor features (hidden service directory):
8045 - Streamline relay-side hsdir handling: when relays consider whether
8046 to accept an uploaded hidden service descriptor, they no longer
8047 check whether they are one of the relays in the network that is
8048 "supposed" to handle that descriptor. Implements ticket 18332.
8050 o Minor features (IPv6):
8051 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
8052 to 1, tor prefers IPv6 directory addresses.
8053 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
8054 avoids using IPv4 for client OR and directory connections.
8055 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
8056 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
8057 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
8059 o Minor features (linux seccomp2 sandbox):
8060 - Reject attempts to change our Address with "Sandbox 1" enabled.
8061 Changing Address with Sandbox turned on would never actually work,
8062 but previously it would fail in strange and confusing ways. Found
8065 o Minor features (robustness):
8066 - Exit immediately with an error message if the code attempts to use
8067 Libevent without having initialized it. This should resolve some
8068 frequently-made mistakes in our unit tests. Closes ticket 18241.
8070 o Minor features (unix domain sockets):
8071 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
8072 Unix domain sockets without checking the permissions on the parent
8073 directory. (Tor checks permissions by default because some
8074 operating systems only check permissions on the parent directory.
8075 However, some operating systems do look at permissions on the
8076 socket, and tor's default check is unneeded.) Closes ticket 18458.
8079 o Minor bugfixes (exit policies, security):
8080 - Refresh an exit relay's exit policy when interface addresses
8081 change. Previously, tor only refreshed the exit policy when the
8082 configured external address changed. Fixes bug 18208; bugfix on
8083 0.2.7.3-rc. Patch by teor.
8085 o Minor bugfixes (security, hidden services):
8086 - Prevent hidden services connecting to client-supplied rendezvous
8087 addresses that are reserved as internal or multicast. Fixes bug
8088 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
8090 o Minor bugfixes (build):
8091 - Do not link the unit tests against both the testing and non-
8092 testing versions of the static libraries. Fixes bug 18490; bugfix
8094 - Avoid spurious failures from configure files related to calling
8095 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
8096 0.2.0.1-alpha. Patch from "cypherpunks".
8097 - Silence spurious clang-scan warnings in the ed25519_donna code by
8098 explicitly initializing some objects. Fixes bug 18384; bugfix on
8099 0.2.7.2-alpha. Patch by teor.
8101 o Minor bugfixes (client, bootstrap):
8102 - Count receipt of new microdescriptors as progress towards
8103 bootstrapping. Previously, with EntryNodes set, Tor might not
8104 successfully repopulate the guard set on bootstrapping. Fixes bug
8105 16825; bugfix on 0.2.3.1-alpha.
8107 o Minor bugfixes (code correctness):
8108 - Update to the latest version of Trunnel, which tries harder to
8109 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
8110 by clang address sanitizer. Fixes bug 18373; bugfix
8113 o Minor bugfixes (configuration):
8114 - Fix a tiny memory leak when parsing a port configuration ending in
8115 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
8117 o Minor bugfixes (containers):
8118 - If we somehow attempt to construct a heap with more than
8119 1073741822 elements, avoid an integer overflow when maintaining
8120 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
8122 o Minor bugfixes (correctness):
8123 - Fix a bad memory handling bug that would occur if we had queued a
8124 cell on a channel's incoming queue. Fortunately, we can't actually
8125 queue a cell like that as our code is constructed today, but it's
8126 best to avoid this kind of error, even if there isn't any code
8127 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
8129 o Minor bugfixes (directory):
8130 - When generating a URL for a directory server on an IPv6 address,
8131 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
8132 on 0.2.3.9-alpha. Patch from Malek.
8134 o Minor bugfixes (fallback directory mirrors):
8135 - When requesting extrainfo descriptors from a trusted directory
8136 server, check whether it is an authority or a fallback directory
8137 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
8138 0.2.4.7-alpha. Reported by atagar, patch by teor.
8140 o Minor bugfixes (hidden service, client):
8141 - Handle the case where the user makes several fast consecutive
8142 requests to the same .onion address. Previously, the first six
8143 requests would each trigger a descriptor fetch, each picking a
8144 directory (there are 6 overall) and the seventh one would fail
8145 because no directories were left, thereby triggering a close on
8146 all current directory connections asking for the hidden service.
8147 The solution here is to not close the connections if we have
8148 pending directory fetches. Fixes bug 15937; bugfix
8151 o Minor bugfixes (hidden service, control port):
8152 - Add the onion address to the HS_DESC event for the UPLOADED action
8153 both on success or failure. It was previously hardcoded with
8154 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
8156 o Minor bugfixes (hidden service, directory):
8157 - Bridges now refuse "rendezvous2" (hidden service descriptor)
8158 publish attempts. Suggested by ticket 18332.
8160 o Minor bugfixes (linux seccomp2 sandbox):
8161 - Allow the setrlimit syscall, and the prlimit and prlimit64
8162 syscalls, which some libc implementations use under the hood.
8163 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
8164 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
8165 enabled and no DNS resolvers configured. This should help TAILS
8166 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
8167 - Fix the sandbox's interoperability with unix domain sockets under
8168 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
8170 o Minor bugfixes (logging):
8171 - When logging information about an unparsable networkstatus vote or
8172 consensus, do not say "vote" when we mean consensus. Fixes bug
8173 18368; bugfix on 0.2.0.8-alpha.
8174 - Scrub service name in "unrecognized service ID" log messages.
8175 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
8176 - Downgrade logs and backtraces about IP versions to info-level.
8177 Only log backtraces once each time tor runs. Assists in diagnosing
8178 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
8179 Christian, patch by teor.
8181 o Minor bugfixes (memory safety):
8182 - Avoid freeing an uninitialized pointer when opening a socket fails
8183 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
8184 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
8186 - Correctly duplicate addresses in get_interface_address6_list().
8187 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
8188 patch by "cypherpunks".
8189 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
8191 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
8192 18672; bugfix on 0.2.5.1-alpha.
8194 o Minor bugfixes (private directory):
8195 - Prevent a race condition when creating private directories. Fixes
8196 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
8197 Patch from jsturgix. Found with Flawfinder.
8199 o Minor bugfixes (test networks, IPv6):
8200 - Allow internal IPv6 addresses in descriptors in test networks.
8201 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
8204 o Minor bugfixes (testing):
8205 - We no longer disable assertions in the unit tests when coverage is
8206 enabled. Instead, we require you to say --disable-asserts-in-tests
8207 to the configure script if you need assertions disabled in the
8208 unit tests (for example, if you want to perform branch coverage).
8209 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
8211 o Minor bugfixes (time parsing):
8212 - Avoid overflow in tor_timegm when parsing dates in and after 2038
8213 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
8214 0.0.2pre14. Patch by teor.
8216 o Minor bugfixes (tor-gencert):
8217 - Correctly handle the case where an authority operator enters a
8218 passphrase but sends an EOF before sending a newline. Fixes bug
8219 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
8221 o Code simplification and refactoring:
8222 - Quote all the string interpolations in configure.ac -- even those
8223 which we are pretty sure can't contain spaces. Closes ticket
8224 17744. Patch from zerosion.
8225 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
8226 inplace, so there's no need to have a separate implementation for
8227 the non-inplace code. Closes ticket 18258. Patch from Malek.
8228 - Simplify return types for some crypto functions that can't
8229 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
8232 - Change build messages to refer to "Fedora" instead of "Fedora
8233 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
8234 Patches from "icanhasaccount" and "cypherpunks".
8237 - We no longer maintain an internal freelist in memarea.c.
8238 Allocators should be good enough to make this code unnecessary,
8239 and it's doubtful that it ever had any performance benefit.
8242 - Fix several warnings from clang's address sanitizer produced in
8244 - Treat backtrace test failures as expected on FreeBSD until we
8245 solve bug 17808. Closes ticket 18204.
8248 Changes in version 0.2.8.1-alpha - 2016-02-04
8249 Tor 0.2.8.1-alpha is the first alpha release in its series. It
8250 includes numerous small features and bugfixes against previous Tor
8251 versions, and numerous small infrastructure improvements. The most
8252 notable features are a set of improvements to the directory subsystem.
8254 o Major features (security, Linux):
8255 - When Tor starts as root on Linux and is told to switch user ID, it
8256 can now retain the capability to bind to low ports. By default,
8257 Tor will do this only when it's switching user ID and some low
8258 ports have been configured. You can change this behavior with the
8259 new option KeepBindCapabilities. Closes ticket 8195.
8261 o Major features (directory system):
8262 - When bootstrapping multiple consensus downloads at a time, use the
8263 first one that starts downloading, and close the rest. This
8264 reduces failures when authorities or fallback directories are slow
8265 or down. Together with the code for feature 15775, this feature
8266 should reduces failures due to fallback churn. Implements ticket
8267 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
8268 "mikeperry" and "teor".
8269 - Include a trial list of 21 default fallback directories, generated
8270 in January 2016, based on an opt-in survey of suitable relays.
8271 Doing this should make clients bootstrap more quickly and reliably,
8272 and reduce the load on the directory authorities. Closes ticket
8273 15775. Patch by "teor".
8274 Candidates identified using an OnionOO script by "weasel", "teor",
8275 "gsathya", and "karsten".
8276 - Previously only relays that explicitly opened a directory port
8277 (DirPort) accepted directory requests from clients. Now all
8278 relays, with and without a DirPort, accept and serve tunneled
8279 directory requests that they receive through their ORPort. You can
8280 disable this behavior using the new DirCache option. Closes
8283 o Major key updates:
8284 - Update the V3 identity key for the dannenberg directory authority:
8285 it was changed on 18 November 2015. Closes task 17906. Patch
8288 o Minor features (security, clock):
8289 - Warn when the system clock appears to move back in time (when the
8290 state file was last written in the future). Tor doesn't know that
8291 consensuses have expired if the clock is in the past. Patch by
8292 "teor". Implements ticket 17188.
8294 o Minor features (security, exit policies):
8295 - ExitPolicyRejectPrivate now rejects more private addresses by
8296 default. Specifically, it now rejects the relay's outbound bind
8297 addresses (if configured), and the relay's configured port
8298 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
8299 0.2.0.11-alpha. Patch by "teor".
8301 o Minor features (security, memory erasure):
8302 - Set the unused entries in a smartlist to NULL. This helped catch
8303 a (harmless) bug, and shouldn't affect performance too much.
8304 Implements ticket 17026.
8305 - Use SecureMemoryWipe() function to securely clean memory on
8306 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
8307 Implements feature 17986.
8308 - Use explicit_bzero or memset_s when present. Previously, we'd use
8309 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
8310 from <logan@hackers.mu> and <selven@hackers.mu>.
8311 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8312 zero size. Check size argument to memwipe() for underflow. Fixes
8313 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8316 o Minor features (security, RNG):
8317 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
8318 positively are not allowed to fail. Previously we depended on
8319 internal details of OpenSSL's behavior. Closes ticket 17686.
8320 - Never use the system entropy output directly for anything besides
8321 seeding the PRNG. When we want to generate important keys, instead
8322 of using system entropy directly, we now hash it with the PRNG
8323 stream. This may help resist certain attacks based on broken OS
8324 entropy implementations. Closes part of ticket 17694.
8325 - Use modern system calls (like getentropy() or getrandom()) to
8326 generate strong entropy on platforms that have them. Closes
8329 o Minor features (accounting):
8330 - Added two modes to the AccountingRule option: One for limiting
8331 only the number of bytes sent ("AccountingRule out"), and one for
8332 limiting only the number of bytes received ("AccountingRule in").
8333 Closes ticket 15989; patch from "unixninja92".
8335 o Minor features (build):
8336 - Since our build process now uses "make distcheck", we no longer
8337 force "make dist" to depend on "make check". Closes ticket 17893;
8338 patch from "cypherpunks."
8339 - Tor now builds successfully with the recent OpenSSL 1.1
8340 development branch, and with the latest LibreSSL. Closes tickets
8341 17549, 17921, and 17984.
8343 o Minor features (controller):
8344 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
8345 tickets 16774 and 17817. Patch by George Tankersley.
8346 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
8347 service descriptor from a service's local hidden service
8348 descriptor cache. Closes ticket 14846.
8349 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
8350 controllers can examine the the reject rules added by
8351 ExitPolicyRejectPrivate. This makes it easier for stem to display
8354 o Minor features (crypto):
8355 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
8357 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
8358 - When allocating a digest state object, allocate no more space than
8359 we actually need. Previously, we would allocate as much space as
8360 the state for the largest algorithm would need. This change saves
8361 up to 672 bytes per circuit. Closes ticket 17796.
8362 - Improve performance when hashing non-multiple of 8 sized buffers,
8363 based on Andrew Moon's public domain SipHash-2-4 implementation.
8364 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
8366 o Minor features (directory downloads):
8367 - Wait for busy authorities and fallback directories to become non-
8368 busy when bootstrapping. (A similar change was made in 6c443e987d
8369 for directory caches chosen from the consensus.) Closes ticket
8370 17864; patch by "teor".
8371 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
8372 directory mirrors. The default is 1; set it to 0 to disable
8373 fallbacks. Implements ticket 17576. Patch by "teor".
8375 o Minor features (geoip):
8376 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
8379 o Minor features (IPv6):
8380 - Add an argument 'ipv6=address:orport' to the DirAuthority and
8381 FallbackDir torrc options, to specify an IPv6 address for an
8382 authority or fallback directory. Add hard-coded ipv6 addresses for
8383 directory authorities that have them. Closes ticket 17327; patch
8384 from Nick Mathewson and "teor".
8385 - Add address policy assume_action support for IPv6 addresses.
8386 - Limit IPv6 mask bits to 128.
8387 - Warn when comparing against an AF_UNSPEC address in a policy, it's
8388 almost always a bug. Closes ticket 17863; patch by "teor".
8389 - Allow users to configure directory authorities and fallback
8390 directory servers with IPv6 addresses and ORPorts. Resolves
8392 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
8393 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
8394 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
8395 17638; bugfix on 0.0.2pre8. Patch by "teor".
8397 o Minor features (logging):
8398 - When logging to syslog, allow a tag to be added to the syslog
8399 identity (the string prepended to every log message). The tag can
8400 be configured with SyslogIdentityTag and defaults to none. Setting
8401 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
8404 o Minor features (portability):
8405 - Use timingsafe_memcmp() where available. Closes ticket 17944;
8406 patch from <logan@hackers.mu>.
8408 o Minor features (relay, address discovery):
8409 - Add a family argument to get_interface_addresses_raw() and
8410 subfunctions to make network interface address interogation more
8411 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
8412 types of interfaces from the operating system. Resolves
8414 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
8415 fails to enumerate interface addresses using the platform-specific
8416 API, have it rely on the UDP socket fallback technique to try and
8417 find out what IP addresses (both IPv4 and IPv6) our machine has.
8418 Resolves ticket 17951.
8420 o Minor features (replay cache):
8421 - The replay cache now uses SHA256 instead of SHA1. Implements
8422 feature 8961. Patch by "teor", issue reported by "rransom".
8424 o Minor features (unix file permissions):
8425 - Defer creation of Unix sockets until after setuid. This avoids
8426 needing CAP_CHOWN and CAP_FOWNER when using systemd's
8427 CapabilityBoundingSet, or chown and fowner when using SELinux.
8428 Implements part of ticket 17562. Patch from Jamie Nguyen.
8429 - If any directory created by Tor is marked as group readable, the
8430 filesystem group is allowed to be either the default GID or the
8431 root user. Allowing root to read the DataDirectory prevents the
8432 need for CAP_READ_SEARCH when using systemd's
8433 CapabilityBoundingSet, or dac_read_search when using SELinux.
8434 Implements part of ticket 17562. Patch from Jamie Nguyen.
8435 - Introduce a new DataDirectoryGroupReadable option. If it is set to
8436 1, the DataDirectory will be made readable by the default GID.
8437 Implements part of ticket 17562. Patch from Jamie Nguyen.
8439 o Minor bugfixes (accounting):
8440 - The max bandwidth when using 'AccountRule sum' is now correctly
8441 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
8444 o Minor bugfixes (code correctness):
8445 - When closing an entry connection, generate a warning if we should
8446 have sent an end cell for it but we haven't. Fixes bug 17876;
8447 bugfix on 0.2.3.2-alpha.
8448 - Assert that allocated memory held by the reputation code is freed
8449 according to its internal counters. Fixes bug 17753; bugfix
8451 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
8454 o Minor bugfixes (compilation):
8455 - Mark all object files that include micro-revision.i as depending
8456 on it, so as to make parallel builds more reliable. Fixes bug
8457 17826; bugfix on 0.2.5.1-alpha.
8458 - Don't try to use the pthread_condattr_setclock() function unless
8459 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
8460 17819; bugfix on 0.2.6.3-alpha.
8461 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
8463 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
8464 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
8465 - Fix search for libevent libraries on OpenBSD (and other systems
8466 that install libevent 1 and libevent 2 in parallel). Fixes bug
8467 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
8468 - Isolate environment variables meant for tests from the rest of the
8469 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
8470 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
8472 - Remove config.log only from make distclean, not from make clean.
8473 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
8475 o Minor bugfixes (crypto):
8476 - Check the return value of HMAC() and assert on failure. Fixes bug
8477 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
8479 o Minor bugfixes (fallback directories):
8480 - Mark fallbacks as "too busy" when they return a 503 response,
8481 rather than just marking authorities. Fixes bug 17572; bugfix on
8482 0.2.4.7-alpha. Patch by "teor".
8484 o Minor bugfixes (IPv6):
8485 - Update the limits in max_dl_per_request for IPv6 address length.
8486 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
8488 o Minor bugfixes (linux seccomp2 sandbox):
8489 - Fix a crash when using offline master ed25519 keys with the Linux
8490 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
8492 o Minor bugfixes (logging):
8493 - In log messages that include a function name, use __FUNCTION__
8494 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
8495 with clang __PRETTY_FUNCTION__ has extra information we don't
8496 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
8498 - Remove needless quotes from a log message about unparseable
8499 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
8501 o Minor bugfixes (portability):
8502 - Remove an #endif from configure.ac so that we correctly detect the
8503 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
8506 o Minor bugfixes (relays):
8507 - Check that both the ORPort and DirPort (if present) are reachable
8508 before publishing a relay descriptor. Otherwise, relays publish a
8509 descriptor with DirPort 0 when the DirPort reachability test takes
8510 longer than the ORPort reachability test. Fixes bug 18050; bugfix
8511 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
8513 o Minor bugfixes (relays, hidden services):
8514 - Refuse connection requests to private OR addresses unless
8515 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
8516 then refuse to send any cells to a private address. Fixes bugs
8517 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
8519 o Minor bugfixes (safe logging):
8520 - When logging a malformed hostname received through socks4, scrub
8521 it if SafeLogging says we should. Fixes bug 17419; bugfix
8524 o Minor bugfixes (statistics code):
8525 - Consistently check for overflow in round_*_to_next_multiple_of
8526 functions, and add unit tests with additional and maximal values.
8527 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
8528 - Handle edge cases in the laplace functions: avoid division by
8529 zero, avoid taking the log of zero, and silence clang type
8530 conversion warnings using round and trunc. Add unit tests for edge
8531 cases with maximal values. Fixes part of bug 13192; bugfix
8534 o Minor bugfixes (testing):
8535 - The test for log_heartbeat was incorrectly failing in timezones
8536 with non-integer offsets. Instead of comparing the end of the time
8537 string against a constant, compare it to the output of
8538 format_local_iso_time when given the correct input. Fixes bug
8539 18039; bugfix on 0.2.5.4-alpha.
8540 - Make unit tests pass on IPv6-only systems, and systems without
8541 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
8542 bugfix on 0.2.7.3-rc. Patch by "teor".
8543 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
8545 - Check the full results of SHA256 and SHA512 digests in the unit
8546 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
8548 o Code simplification and refactoring:
8549 - Move logging of redundant policy entries in
8550 policies_parse_exit_policy_internal into its own function. Closes
8551 ticket 17608; patch from "juce".
8552 - Extract the more complicated parts of circuit_mark_for_close()
8553 into a new function that we run periodically before circuits are
8554 freed. This change removes more than half of the functions
8555 currently in the "blob". Closes ticket 17218.
8556 - Clean up a little duplicated code in
8557 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
8559 - Decouple the list of streams waiting to be attached to circuits
8560 from the overall connection list. This change makes it possible to
8561 attach streams quickly while simplifying Tor's callgraph and
8562 avoiding O(N) scans of the entire connection list. Closes
8564 - When a direct directory request fails immediately on launch,
8565 instead of relaunching that request from inside the code that
8566 launches it, instead mark the connection for teardown. This change
8567 simplifies Tor's callback and prevents the directory-request
8568 launching code from invoking itself recursively. Closes
8570 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
8571 use them. Closes ticket 17926.
8574 - Add a description of the correct use of the '--keygen' command-
8575 line option. Closes ticket 17583; based on text by 's7r'.
8576 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
8577 - Explain actual minima for BandwidthRate. Closes ticket 16382.
8578 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
8579 - Mention torspec URL in the manpage and point the reader to it
8580 whenever we mention a document that belongs in torspce. Fixes
8584 - Remove client-side support for connecting to Tor relays running
8585 versions of Tor before 0.2.3.6-alpha. These relays didn't support
8586 the v3 TLS handshake protocol, and are no longer allowed on the
8587 Tor network. Implements the client side of ticket 11150. Based on
8588 patches by Tom van der Woerdt.
8591 - Add unit tests to check for common RNG failure modes, such as
8592 returning all zeroes, identical values, or incrementing values
8593 (OpenSSL's rand_predictable feature). Patch by "teor".
8594 - Log more information when the backtrace tests fail. Closes ticket
8595 17892. Patch from "cypherpunks."
8596 - Always test both ed25519 backends, so that we can be sure that our
8597 batch-open replacement code works. Part of ticket 16794.
8598 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
8599 portion of ticket 16831.
8600 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
8601 util_format.c, directory.c, and options_validate.c. Closes tickets
8602 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
8604 - Unit tests for directory_handle_command_get. Closes ticket 17004.
8605 Patch from Reinaldo de Souza Jr.
8608 Changes in version 0.2.7.6 - 2015-12-10
8609 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
8610 well as a minor bug in hidden service reliability.
8612 o Major bugfixes (guard selection):
8613 - Actually look at the Guard flag when selecting a new directory
8614 guard. When we implemented the directory guard design, we
8615 accidentally started treating all relays as if they have the Guard
8616 flag during guard selection, leading to weaker anonymity and worse
8617 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8620 o Minor features (geoip):
8621 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
8624 o Minor bugfixes (compilation):
8625 - When checking for net/pfvar.h, include netinet/in.h if possible.
8626 This fixes transparent proxy detection on OpenBSD. Fixes bug
8627 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
8628 - Fix a compilation warning with Clang 3.6: Do not check the
8629 presence of an address which can never be NULL. Fixes bug 17781.
8631 o Minor bugfixes (correctness):
8632 - When displaying an IPv6 exit policy, include the mask bits
8633 correctly even when the number is greater than 31. Fixes bug
8634 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
8635 - The wrong list was used when looking up expired intro points in a
8636 rend service object, causing what we think could be reachability
8637 issues for hidden services, and triggering a BUG log. Fixes bug
8638 16702; bugfix on 0.2.7.2-alpha.
8639 - Fix undefined behavior in the tor_cert_checksig function. Fixes
8640 bug 17722; bugfix on 0.2.7.2-alpha.
8643 Changes in version 0.2.7.5 - 2015-11-20
8644 The Tor 0.2.7 release series is dedicated to the memory of Tor user
8645 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
8646 tirelessly to advocate human rights regardless of national borders,
8647 and oppose the encroachments of mass surveillance. He opposed national
8648 exceptionalism, he brought clarity to legal and policy debates, he
8649 understood and predicted the impact of mass surveillance on the world,
8650 and he laid the groundwork for resisting it. While serving on the Tor
8651 Project's board of directors, he brought us his uncompromising focus
8652 on technical excellence in the service of humankind. Caspar was an
8653 inimitable force for good and a wonderful friend. He was kind,
8654 humorous, generous, gallant, and believed we should protect one
8655 another without exception. We honor him here for his ideals, his
8656 efforts, and his accomplishments. Please honor his memory with works
8657 that would make him proud.
8659 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
8661 The 0.2.7 series adds a more secure identity key type for relays,
8662 improves cryptography performance, resolves several longstanding
8663 hidden-service performance issues, improves controller support for
8664 hidden services, and includes small bugfixes and performance
8665 improvements throughout the program. This release series also includes
8666 more tests than before, and significant simplifications to which parts
8667 of Tor invoke which others.
8669 (This release contains no code changes since 0.2.7.4-rc.)
8672 Changes in version 0.2.7.4-rc - 2015-10-21
8673 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
8674 fixes some important memory leaks, and a scary-looking (but mostly
8675 harmless in practice) invalid-read bug. It also has a few small
8676 bugfixes, notably fixes for compilation and portability on different
8677 platforms. If no further significant bounds are found, the next
8678 release will the the official stable release.
8680 o Major bugfixes (security, correctness):
8681 - Fix an error that could cause us to read 4 bytes before the
8682 beginning of an openssl string. This bug could be used to cause
8683 Tor to crash on systems with unusual malloc implementations, or
8684 systems with unusual hardening installed. Fixes bug 17404; bugfix
8687 o Major bugfixes (correctness):
8688 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
8689 bug 17401; bugfix on 0.2.7.3-rc.
8691 o Major bugfixes (memory leaks):
8692 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
8693 17398; bugfix on 0.2.6.1-alpha.
8694 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
8695 17402; bugfix on 0.2.7.3-rc.
8696 - Fix a memory leak when reading an expired signing key from disk.
8697 Fixes bug 17403; bugfix on 0.2.7.2-rc.
8699 o Minor features (geoIP):
8700 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
8703 o Minor bugfixes (compilation):
8704 - Repair compilation with the most recent (unreleased, alpha)
8705 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
8706 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
8707 17251; bugfix on 0.2.7.2-alpha.
8708 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
8709 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
8711 o Minor bugfixes (portability):
8712 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
8713 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
8716 o Minor bugfixes (sandbox):
8717 - Add the "hidserv-stats" filename to our sandbox filter for the
8718 HiddenServiceStatistics option to work properly. Fixes bug 17354;
8719 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
8721 o Minor bugfixes (testing):
8722 - Add unit tests for get_interface_address* failure cases. Fixes bug
8723 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
8724 - Fix breakage when running 'make check' with BSD make. Fixes bug
8725 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
8726 - Make the get_ifaddrs_* unit tests more tolerant of different
8727 network configurations. (Don't assume every test box has an IPv4
8728 address, and don't assume every test box has a non-localhost
8729 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
8730 - Skip backtrace tests when backtrace support is not compiled in.
8731 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
8735 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
8736 - Note that HiddenServicePorts can take a unix domain socket. Closes
8740 Changes in version 0.2.7.3-rc - 2015-09-25
8741 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
8742 contains numerous usability fixes for Ed25519 keys, safeguards against
8743 several misconfiguration problems, significant simplifications to
8744 Tor's callgraph, and numerous bugfixes and small features.
8746 This is the most tested release of Tor to date. The unit tests cover
8747 39.40% of the code, and the integration tests (accessible with "make
8748 test-full-online", requiring stem and chutney and a network
8749 connection) raise the coverage to 64.49%.
8751 o Major features (security, hidden services):
8752 - Hidden services, if using the EntryNodes option, are required to
8753 use more than one EntryNode, in order to avoid a guard discovery
8754 attack. (This would only affect people who had configured hidden
8755 services and manually specified the EntryNodes option with a
8756 single entry-node. The impact was that it would be easy to
8757 remotely identify the guard node used by such a hidden service.
8758 See ticket for more information.) Fixes ticket 14917.
8760 o Major features (Ed25519 keys, keypinning):
8761 - The key-pinning option on directory authorities is now advisory-
8762 only by default. In a future version, or when the AuthDirPinKeys
8763 option is set, pins are enforced again. Disabling key-pinning
8764 seemed like a good idea so that we can survive the fallout of any
8765 usability problems associated with Ed25519 keys. Closes
8768 o Major features (Ed25519 performance):
8769 - Improve the speed of Ed25519 operations and Curve25519 keypair
8770 generation when built targeting 32 bit x86 platforms with SSE2
8771 available. Implements ticket 16535.
8772 - Improve the runtime speed of Ed25519 signature verification by
8773 using Ed25519-donna's batch verification support. Implements
8776 o Major features (performance testing):
8777 - The test-network.sh script now supports performance testing.
8778 Requires corresponding chutney performance testing changes. Patch
8779 by "teor". Closes ticket 14175.
8781 o Major features (relay, Ed25519):
8782 - Significant usability improvements for Ed25519 key management. Log
8783 messages are better, and the code can recover from far more
8784 failure conditions. Thanks to "s7r" for reporting and diagnosing
8786 - Add a new OfflineMasterKey option to tell Tor never to try loading
8787 or generating a secret Ed25519 identity key. You can use this in
8788 combination with tor --keygen to manage offline and/or encrypted
8789 Ed25519 keys. Implements ticket 16944.
8790 - Add a --newpass option to allow changing or removing the
8791 passphrase of an encrypted key with tor --keygen. Implements part
8793 - On receiving a HUP signal, check to see whether the Ed25519
8794 signing key has changed, and reload it if so. Closes ticket 16790.
8796 o Major bugfixes (relay, Ed25519):
8797 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
8798 0.2.7.2-alpha. Reported by "s7r".
8799 - Improve handling of expired signing keys with offline master keys.
8800 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
8802 o Minor features (client-side privacy):
8803 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
8804 lifespan when IsolateSOCKSAuth and streams with SOCKS
8805 authentication are attached to the circuit. This allows
8806 applications like TorBrowser to manage circuit lifetime on their
8807 own. Implements feature 15482.
8808 - When logging malformed hostnames from SOCKS5 requests, respect
8809 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
8811 o Minor features (compilation):
8812 - Give a warning as early as possible when trying to build with an
8813 unsupported OpenSSL version. Closes ticket 16901.
8814 - Fail during configure if we're trying to build against an OpenSSL
8815 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
8816 which started requiring ECC.
8818 o Minor features (geoip):
8819 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
8822 o Minor features (hidden services):
8823 - Relays need to have the Fast flag to get the HSDir flag. As this
8824 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
8825 drop. This change should make some attacks against the hidden
8826 service directory system harder. Fixes ticket 15963.
8827 - Turn on hidden service statistics collection by setting the torrc
8828 option HiddenServiceStatistics to "1" by default. (This keeps
8829 track only of the fraction of traffic used by hidden services, and
8830 the total number of hidden services in existence.) Closes
8832 - Client now uses an introduction point failure cache to know when
8833 to fetch or keep a descriptor in their cache. Previously, failures
8834 were recorded implicitly, but not explicitly remembered. Closes
8837 o Minor features (testing, authorities, documentation):
8838 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
8839 explicitly manage consensus flags in testing networks. Patch by
8840 "robgjansen", modified by "teor". Implements part of ticket 14882.
8842 o Minor bugfixes (security, exit policies):
8843 - ExitPolicyRejectPrivate now also rejects the relay's published
8844 IPv6 address (if any), and any publicly routable IPv4 or IPv6
8845 addresses on any local interfaces. ticket 17027. Patch by "teor".
8846 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
8848 o Minor bug fixes (torrc exit policies):
8849 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
8850 produce IPv6 wildcard addresses. Previously they would produce
8851 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
8852 of bug 16069; bugfix on 0.2.4.7-alpha.
8853 - When parsing torrc ExitPolicies, we now warn for a number of cases
8854 where the user's intent is likely to differ from Tor's actual
8855 behavior. These include: using an IPv4 address with an accept6 or
8856 reject6 line; using "private" on an accept6 or reject6 line; and
8857 including any ExitPolicy lines after accept *:* or reject *:*.
8858 Related to ticket 16069.
8859 - When parsing torrc ExitPolicies, we now issue an info-level
8860 message when expanding an "accept/reject *" line to include both
8861 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
8862 - In each instance above, usage advice is provided to avoid the
8863 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
8864 16069; bugfix on 0.2.4.7-alpha.
8866 o Minor bugfixes (authority):
8867 - Don't assign "HSDir" to a router if it isn't Valid and Running.
8868 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
8869 - Downgrade log messages about Ed25519 key issues if they are in old
8870 cached router descriptors. Fixes part of bug 16286; bugfix
8872 - When we find an Ed25519 key issue in a cached descriptor, stop
8873 saying the descriptor was just "uploaded". Fixes another part of
8874 bug 16286; bugfix on 0.2.7.2-alpha.
8876 o Minor bugfixes (control port):
8877 - Repair a warning and a spurious result when getting the maximum
8878 number of file descriptors from the controller. Fixes bug 16697;
8879 bugfix on 0.2.7.2-alpha.
8881 o Minor bugfixes (correctness):
8882 - When calling channel_free_list(), avoid calling smartlist_remove()
8883 while inside a FOREACH loop. This partially reverts commit
8884 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
8885 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
8887 o Minor bugfixes (documentation):
8888 - Advise users on how to configure separate IPv4 and IPv6 exit
8889 policies in the manpage and sample torrcs. Related to ticket 16069.
8890 - Fix the usage message of tor-resolve(1) so that it no longer lists
8891 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
8892 - Fix an error in the manual page and comments for
8893 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
8894 required "ORPort connectivity". While this is true, it is in no
8895 way unique to the HSDir flag. Of all the flags, only HSDirs need a
8896 DirPort configured in order for the authorities to assign that
8897 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
8900 o Minor bugfixes (Ed25519):
8901 - Fix a memory leak when reading router descriptors with expired
8902 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
8904 o Minor bugfixes (linux seccomp2 sandbox):
8905 - Allow bridge authorities to run correctly under the seccomp2
8906 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
8907 - Allow routers with ed25519 keys to run correctly under the
8908 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
8910 o Minor bugfixes (open file limit):
8911 - Fix set_max_file_descriptors() to set by default the max open file
8912 limit to the current limit when setrlimit() fails. Fixes bug
8913 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
8915 o Minor bugfixes (portability):
8916 - Try harder to normalize the exit status of the Tor process to the
8917 standard-provided range. Fixes bug 16975; bugfix on every version
8919 - Check correctly for Windows socket errors in the workqueue
8920 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
8921 - Fix the behavior of crypto_rand_time_range() when told to consider
8922 times before 1970. (These times were possible when running in a
8923 simulated network environment where time()'s output starts at
8924 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
8925 - Restore correct operation of TLS client-cipher detection on
8926 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
8928 o Minor bugfixes (relay):
8929 - Ensure that worker threads actually exit when a fatal error or
8930 shutdown is indicated. This fix doesn't currently affect the
8931 behavior of Tor, because Tor workers never indicates fatal error
8932 or shutdown except in the unit tests. Fixes bug 16868; bugfix
8934 - Unblock threads before releasing the work queue mutex to ensure
8935 predictable scheduling behavior. Fixes bug 16644; bugfix
8938 o Code simplification and refactoring:
8939 - Change the function that's called when we need to retry all
8940 downloads so that it only reschedules the downloads to happen
8941 immediately, rather than launching them all at once itself. This
8942 further simplifies Tor's callgraph.
8943 - Move some format-parsing functions out of crypto.c and
8944 crypto_curve25519.c into crypto_format.c and/or util_format.c.
8945 - Move the client-only parts of init_keys() into a separate
8946 function. Closes ticket 16763.
8947 - Simplify the microdesc_free() implementation so that it no longer
8948 appears (to code analysis tools) to potentially invoke a huge
8949 suite of other microdesc functions.
8950 - Simply the control graph further by deferring the inner body of
8951 directory_all_unreachable() into a callback. Closes ticket 16762.
8952 - Treat the loss of an owning controller as equivalent to a SIGTERM
8953 signal. This removes a tiny amount of duplicated code, and
8954 simplifies our callgraph. Closes ticket 16788.
8955 - When generating an event to send to the controller, we no longer
8956 put the event over the network immediately. Instead, we queue
8957 these events, and use a Libevent callback to deliver them. This
8958 change simplifies Tor's callgraph by reducing the number of
8959 functions from which all other Tor functions are reachable. Closes
8961 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
8962 that try to scan or compile every file on Unix won't decide that
8964 - Remove the unused "nulterminate" argument from buf_pullup().
8967 - Recommend a 40 GB example AccountingMax in torrc.sample rather
8968 than a 4 GB max. Closes ticket 16742.
8969 - Include the TUNING document in our source tarball. It is referred
8970 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
8974 - The internal pure-C tor-fw-helper tool is now removed from the Tor
8975 distribution, in favor of the pure-Go clone available from
8976 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
8977 used by the C tor-fw-helper are not, in our opinion, very
8978 confidence- inspiring in their secure-programming techniques.
8979 Closes ticket 13338.
8980 - Remove the code that would try to aggressively flush controller
8981 connections while writing to them. This code was introduced in
8982 0.1.2.7-alpha, in order to keep output buffers from exceeding
8983 their limits. But there is no longer a maximum output buffer size,
8984 and flushing data in this way caused some undesirable recursions
8985 in our call graph. Closes ticket 16480.
8988 - Make "bridges+hs" the default test network. This tests almost all
8989 tor functionality during make test-network, while allowing tests
8990 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
8991 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
8992 (chutney). Patches by "teor".
8993 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
8994 by-side in the same parent directory. Closes ticket 16903. Patch
8996 - Use environment variables rather than autoconf substitutions to
8997 send variables from the build system to the test scripts. This
8998 change should be easier to maintain, and cause 'make distcheck' to
8999 work better than before. Fixes bug 17148.
9000 - Add a new set of callgraph analysis scripts that use clang to
9001 produce a list of which Tor functions are reachable from which
9002 other Tor functions. We're planning to use these to help simplify
9003 our code structure by identifying illogical dependencies.
9004 - Add new 'test-full' and 'test-full-online' targets to run all
9005 tests, including integration tests with stem and chutney.
9006 - Make the test-workqueue test work on Windows by initializing the
9007 network before we begin.
9008 - New make target (make test-network-all) to run multiple applicable
9009 chutney test cases. Patch from Teor; closes 16953.
9010 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
9011 functions in dns.c. Implements a portion of ticket 16831.
9012 - When building Tor with testing coverage enabled, run Chutney tests
9013 (if any) using the 'tor-cov' coverage binary.
9014 - When running test-network or test-stem, check for the absence of
9015 stem/chutney before doing any build operations.
9018 Changes in version 0.2.7.2-alpha - 2015-07-27
9019 This, the second alpha in the Tor 0.2.7 series, has a number of new
9020 features, including a way to manually pick the number of introduction
9021 points for hidden services, and the much stronger Ed25519 signing key
9022 algorithm for regular Tor relays (including support for encrypted
9023 offline identity keys in the new algorithm).
9025 Support for Ed25519 on relays is currently limited to signing router
9026 descriptors; later alphas in this series will extend Ed25519 key
9027 support to more parts of the Tor protocol.
9029 o Major features (Ed25519 identity keys, Proposal 220):
9030 - All relays now maintain a stronger identity key, using the Ed25519
9031 elliptic curve signature format. This master key is designed so
9032 that it can be kept offline. Relays also generate an online
9033 signing key, and a set of other Ed25519 keys and certificates.
9034 These are all automatically regenerated and rotated as needed.
9035 Implements part of ticket 12498.
9036 - Directory authorities now vote on Ed25519 identity keys along with
9037 RSA1024 keys. Implements part of ticket 12498.
9038 - Directory authorities track which Ed25519 identity keys have been
9039 used with which RSA1024 identity keys, and do not allow them to
9040 vary freely. Implements part of ticket 12498.
9041 - Microdescriptors now include Ed25519 identity keys. Implements
9042 part of ticket 12498.
9043 - Add support for offline encrypted Ed25519 master keys. To use this
9044 feature on your tor relay, run "tor --keygen" to make a new master
9045 key (or to make a new signing key if you already have a master
9046 key). Closes ticket 13642.
9048 o Major features (Hidden services):
9049 - Add the torrc option HiddenServiceNumIntroductionPoints, to
9050 specify a fixed number of introduction points. Its maximum value
9051 is 10 and default is 3. Using this option can increase a hidden
9052 service's reliability under load, at the cost of making it more
9053 visible that the hidden service is facing extra load. Closes
9055 - Remove the adaptive algorithm for choosing the number of
9056 introduction points, which used to change the number of
9057 introduction points (poorly) depending on the number of
9058 connections the HS sees. Closes ticket 4862.
9060 o Major features (onion key cross-certification):
9061 - Relay descriptors now include signatures of their own identity
9062 keys, made using the TAP and ntor onion keys. These signatures
9063 allow relays to prove ownership of their own onion keys. Because
9064 of this change, microdescriptors will no longer need to include
9065 RSA identity keys. Implements proposal 228; closes ticket 12499.
9067 o Major features (performance):
9068 - Improve the runtime speed of Ed25519 operations by using the
9069 public-domain Ed25519-donna by Andrew M. ("floodyberry").
9070 Implements ticket 16467.
9071 - Improve the runtime speed of the ntor handshake by using an
9072 optimized curve25519 basepoint scalarmult implementation from the
9073 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
9074 ideas by Adam Langley. Implements ticket 9663.
9076 o Major bugfixes (client-side privacy, also in 0.2.6.9):
9077 - Properly separate out each SOCKSPort when applying stream
9078 isolation. The error occurred because each port's session group
9079 was being overwritten by a default value when the listener
9080 connection was initialized. Fixes bug 16247; bugfix on
9081 0.2.6.3-alpha. Patch by "jojelino".
9083 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
9084 - Stop refusing to store updated hidden service descriptors on a
9085 client. This reverts commit 9407040c59218 (which indeed fixed bug
9086 14219, but introduced a major hidden service reachability
9087 regression detailed in bug 16381). This is a temporary fix since
9088 we can live with the minor issue in bug 14219 (it just results in
9089 some load on the network) but the regression of 16381 is too much
9090 of a setback. First-round fix for bug 16381; bugfix
9093 o Major bugfixes (hidden services):
9094 - When cannibalizing a circuit for an introduction point, always
9095 extend to the chosen exit node (creating a 4 hop circuit).
9096 Previously Tor would use the current circuit exit node, which
9097 changed the original choice of introduction point, and could cause
9098 the hidden service to skip excluded introduction points or
9099 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
9102 o Major bugfixes (open file limit):
9103 - The open file limit wasn't checked before calling
9104 tor_accept_socket_nonblocking(), which would make Tor exceed the
9105 limit. Now, before opening a new socket, Tor validates the open
9106 file limit just before, and if the max has been reached, return an
9107 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
9109 o Major bugfixes (stability, also in 0.2.6.10):
9110 - Stop crashing with an assertion failure when parsing certain kinds
9111 of malformed or truncated microdescriptors. Fixes bug 16400;
9112 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
9113 by "cypherpunks_backup".
9114 - Stop random client-side assertion failures that could occur when
9115 connecting to a busy hidden service, or connecting to a hidden
9116 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
9119 o Minor features (directory authorities, security, also in 0.2.6.9):
9120 - The HSDir flag given by authorities now requires the Stable flag.
9121 For the current network, this results in going from 2887 to 2806
9122 HSDirs. Also, it makes it harder for an attacker to launch a sybil
9123 attack by raising the effort for a relay to become Stable to
9124 require at the very least 7 days, while maintaining the 96 hours
9125 uptime requirement for HSDir. Implements ticket 8243.
9127 o Minor features (client):
9128 - Relax the validation of hostnames in SOCKS5 requests, allowing the
9129 character '_' to appear, in order to cope with domains observed in
9130 the wild that are serving non-RFC compliant records. Resolves
9132 - Relax the validation done to hostnames in SOCKS5 requests, and
9133 allow a single trailing '.' to cope with clients that pass FQDNs
9134 using that syntax to explicitly indicate that the domain name is
9135 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
9136 - Add GroupWritable and WorldWritable options to unix-socket based
9137 SocksPort and ControlPort options. These options apply to a single
9138 socket, and override {Control,Socks}SocketsGroupWritable. Closes
9141 o Minor features (control protocol):
9142 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
9143 the control protocol. Resolves ticket 15358.
9145 o Minor features (directory authorities):
9146 - Directory authorities no longer vote against the "Fast", "Stable",
9147 and "HSDir" flags just because they were going to vote against
9148 "Running": if the consensus turns out to be that the router was
9149 running, then the authority's vote should count. Patch from Peter
9150 Retzlaff; closes issue 8712.
9152 o Minor features (geoip, also in 0.2.6.10):
9153 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
9154 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
9156 o Minor features (hidden services):
9157 - Add the new options "HiddenServiceMaxStreams" and
9158 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
9159 limit the maximum number of simultaneous streams per circuit, and
9160 optionally tear down the circuit when the limit is exceeded. Part
9163 o Minor features (portability):
9164 - Use C99 variadic macros when the compiler is not GCC. This avoids
9165 failing compilations on MSVC, and fixes a log-file-based race
9166 condition in our old workarounds. Original patch from Gisle Vanem.
9168 o Minor bugfixes (compilation, also in 0.2.6.9):
9169 - Build with --enable-systemd correctly when libsystemd is
9170 installed, but systemd is not. Fixes bug 16164; bugfix on
9171 0.2.6.3-alpha. Patch from Peter Palfrader.
9173 o Minor bugfixes (controller):
9174 - Add the descriptor ID in each HS_DESC control event. It was
9175 missing, but specified in control-spec.txt. Fixes bug 15881;
9176 bugfix on 0.2.5.2-alpha.
9178 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
9179 - Check for failures from crypto_early_init, and refuse to continue.
9180 A previous typo meant that we could keep going with an
9181 uninitialized crypto library, and would have OpenSSL initialize
9182 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9183 when implementing ticket 4900. Patch by "teor".
9185 o Minor bugfixes (hidden services):
9186 - Fix a crash when reloading configuration while at least one
9187 configured and one ephemeral hidden service exists. Fixes bug
9188 16060; bugfix on 0.2.7.1-alpha.
9189 - Avoid crashing with a double-free bug when we create an ephemeral
9190 hidden service but adding it fails for some reason. Fixes bug
9191 16228; bugfix on 0.2.7.1-alpha.
9193 o Minor bugfixes (Linux seccomp2 sandbox):
9194 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
9195 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
9197 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
9198 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
9199 these when eventfd2() support is missing. Fixes bug 16363; bugfix
9200 on 0.2.6.3-alpha. Patch from "teor".
9202 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
9203 - Fix sandboxing to work when running as a relay, by allowing the
9204 renaming of secret_id_key, and allowing the eventfd2 and futex
9205 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
9207 - Allow systemd connections to work with the Linux seccomp2 sandbox
9208 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
9211 o Minor bugfixes (relay):
9212 - Fix a rarely-encountered memory leak when failing to initialize
9213 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
9216 o Minor bugfixes (systemd):
9217 - Fix an accidental formatting error that broke the systemd
9218 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
9219 - Tor's systemd unit file no longer contains extraneous spaces.
9220 These spaces would sometimes confuse tools like deb-systemd-
9221 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
9223 o Minor bugfixes (tests):
9224 - Use the configured Python executable when running test-stem-full.
9225 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
9227 o Minor bugfixes (tests, also in 0.2.6.9):
9228 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
9229 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
9231 o Minor bugfixes (threads, comments):
9232 - Always initialize return value in compute_desc_id in rendcommon.c
9233 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
9234 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
9235 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
9236 - Remove undefined directive-in-macro in test_util_writepid clang
9237 3.7 complains that using a preprocessor directive inside a macro
9238 invocation in test_util_writepid in test_util.c is undefined.
9239 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
9241 o Code simplification and refactoring:
9242 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
9243 to ensure they remain consistent and visible everywhere.
9244 - Remove some vestigial workarounds for the MSVC6 compiler. We
9245 haven't supported that in ages.
9246 - The link authentication code has been refactored for better
9247 testability and reliability. It now uses code generated with the
9248 "trunnel" binary encoding generator, to reduce the risk of bugs
9249 due to programmer error. Done as part of ticket 12498.
9252 - Include a specific and (hopefully) accurate documentation of the
9253 torrc file's meta-format in doc/torrc_format.txt. This is mainly
9254 of interest to people writing programs to parse or generate torrc
9255 files. This document is not a commitment to long-term
9256 compatibility; some aspects of the current format are a bit
9257 ridiculous. Closes ticket 2325.
9260 - Tor no longer supports copies of OpenSSL that are missing support
9261 for Elliptic Curve Cryptography. (We began using ECC when
9262 available in 0.2.4.8-alpha, for more safe and efficient key
9263 negotiation.) In particular, support for at least one of P256 or
9264 P224 is now required, with manual configuration needed if only
9265 P224 is available. Resolves ticket 16140.
9266 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
9267 on an operating system that has not upgraded to OpenSSL 1.0 or
9268 later, and you compile Tor from source, you will need to install a
9269 more recent OpenSSL to link Tor against.) These versions of
9270 OpenSSL are still supported by the OpenSSL, but the numerous
9271 cryptographic improvements in later OpenSSL releases makes them a
9272 clear choice. Resolves ticket 16034.
9273 - Remove the HidServDirectoryV2 option. Now all relays offer to
9274 store hidden service descriptors. Related to 16543.
9275 - Remove the VoteOnHidServDirectoriesV2 option, since all
9276 authorities have long set it to 1. Closes ticket 16543.
9279 - Document use of coverity, clang static analyzer, and clang dynamic
9280 undefined behavior and address sanitizers in doc/HACKING. Include
9281 detailed usage instructions in the blacklist. Patch by "teor".
9282 Closes ticket 15817.
9283 - The link authentication protocol code now has extensive tests.
9284 - The relay descriptor signature testing code now has
9286 - The test_workqueue program now runs faster, and is enabled by
9287 default as a part of "make check".
9288 - Now that OpenSSL has its own scrypt implementation, add an unit
9289 test that checks for interoperability between libscrypt_scrypt()
9290 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
9291 and rely on EVP_PBE_scrypt() whenever possible. Resolves
9295 Changes in version 0.2.6.10 - 2015-07-12
9296 Tor version 0.2.6.10 fixes some significant stability and hidden
9297 service client bugs, bulletproofs the cryptography init process, and
9298 fixes a bug when using the sandbox code with some older versions of
9299 Linux. Everyone running an older version, especially an older version
9300 of 0.2.6, should upgrade.
9302 o Major bugfixes (hidden service clients, stability):
9303 - Stop refusing to store updated hidden service descriptors on a
9304 client. This reverts commit 9407040c59218 (which indeed fixed bug
9305 14219, but introduced a major hidden service reachability
9306 regression detailed in bug 16381). This is a temporary fix since
9307 we can live with the minor issue in bug 14219 (it just results in
9308 some load on the network) but the regression of 16381 is too much
9309 of a setback. First-round fix for bug 16381; bugfix
9312 o Major bugfixes (stability):
9313 - Stop crashing with an assertion failure when parsing certain kinds
9314 of malformed or truncated microdescriptors. Fixes bug 16400;
9315 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
9316 by "cypherpunks_backup".
9317 - Stop random client-side assertion failures that could occur when
9318 connecting to a busy hidden service, or connecting to a hidden
9319 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
9322 o Minor features (geoip):
9323 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
9324 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
9326 o Minor bugfixes (crypto error-handling):
9327 - Check for failures from crypto_early_init, and refuse to continue.
9328 A previous typo meant that we could keep going with an
9329 uninitialized crypto library, and would have OpenSSL initialize
9330 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9331 when implementing ticket 4900. Patch by "teor".
9333 o Minor bugfixes (Linux seccomp2 sandbox):
9334 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
9335 these when eventfd2() support is missing. Fixes bug 16363; bugfix
9336 on 0.2.6.3-alpha. Patch from "teor".
9339 Changes in version 0.2.6.9 - 2015-06-11
9340 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
9341 requirements for receiving an HSDir flag, and addresses some other small
9342 bugs in the systemd and sandbox code. Clients using circuit isolation
9343 should upgrade; all directory authorities should upgrade.
9345 o Major bugfixes (client-side privacy):
9346 - Properly separate out each SOCKSPort when applying stream
9347 isolation. The error occurred because each port's session group was
9348 being overwritten by a default value when the listener connection
9349 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
9352 o Minor feature (directory authorities, security):
9353 - The HSDir flag given by authorities now requires the Stable flag.
9354 For the current network, this results in going from 2887 to 2806
9355 HSDirs. Also, it makes it harder for an attacker to launch a sybil
9356 attack by raising the effort for a relay to become Stable which
9357 takes at the very least 7 days to do so and by keeping the 96
9358 hours uptime requirement for HSDir. Implements ticket 8243.
9360 o Minor bugfixes (compilation):
9361 - Build with --enable-systemd correctly when libsystemd is
9362 installed, but systemd is not. Fixes bug 16164; bugfix on
9363 0.2.6.3-alpha. Patch from Peter Palfrader.
9365 o Minor bugfixes (Linux seccomp2 sandbox):
9366 - Fix sandboxing to work when running as a relaymby renaming of
9367 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
9368 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
9369 - Allow systemd connections to work with the Linux seccomp2 sandbox
9370 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
9373 o Minor bugfixes (tests):
9374 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
9375 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
9378 Changes in version 0.2.6.8 - 2015-05-21
9379 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
9380 fixes an authority-side bug in assigning the HSDir flag. All directory
9381 authorities should upgrade.
9383 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
9384 - Revert commit that made directory authorities assign the HSDir
9385 flag to relays without a DirPort; this was bad because such relays
9386 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
9389 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9390 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9391 a client authorized hidden service. Fixes bug 15823; bugfix
9394 o Minor features (geoip):
9395 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
9396 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
9400 Changes in version 0.2.7.1-alpha - 2015-05-12
9401 Tor 0.2.7.1-alpha is the first alpha release in its series. It
9402 includes numerous small features and bugfixes against previous Tor
9403 versions, and numerous small infrastructure improvements. The most
9404 notable features are several new ways for controllers to interact with
9405 the hidden services subsystem.
9407 o New system requirements:
9408 - Tor no longer includes workarounds to support Libevent versions
9409 before 1.3e. Libevent 2.0 or later is recommended. Closes
9412 o Major features (controller):
9413 - Add the ADD_ONION and DEL_ONION commands that allow the creation
9414 and management of hidden services via the controller. Closes
9416 - New "GETINFO onions/current" and "GETINFO onions/detached"
9417 commands to get information about hidden services created via the
9418 controller. Part of ticket 6411.
9419 - New HSFETCH command to launch a request for a hidden service
9420 descriptor. Closes ticket 14847.
9421 - New HSPOST command to upload a hidden service descriptor. Closes
9422 ticket 3523. Patch by "DonnchaC".
9424 o Major bugfixes (hidden services):
9425 - Revert commit that made directory authorities assign the HSDir
9426 flag to relays without a DirPort; this was bad because such relays
9427 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
9430 o Minor features (clock-jump tolerance):
9431 - Recover better when our clock jumps back many hours, like might
9432 happen for Tails or Whonix users who start with a very wrong
9433 hardware clock, use Tor to discover a more accurate time, and then
9434 fix their clock. Resolves part of ticket 8766.
9436 o Minor features (command-line interface):
9437 - Make --hash-password imply --hush to prevent unnecessary noise.
9438 Closes ticket 15542. Patch from "cypherpunks".
9439 - Print a warning whenever we find a relative file path being used
9440 as torrc option. Resolves issue 14018.
9442 o Minor features (controller):
9443 - Add DirAuthority lines for default directory authorities to the
9444 output of the "GETINFO config/defaults" command if not already
9445 present. Implements ticket 14840.
9446 - Controllers can now use "GETINFO hs/client/desc/id/..." to
9447 retrieve items from the client's hidden service descriptor cache.
9448 Closes ticket 14845.
9449 - Implement a new controller command "GETINFO status/fresh-relay-
9450 descs" to fetch a descriptor/extrainfo pair that was generated on
9451 demand just for the controller's use. Implements ticket 14784.
9453 o Minor features (DoS-resistance):
9454 - Make it harder for attackers to overload hidden services with
9455 introductions, by blocking multiple introduction requests on the
9456 same circuit. Resolves ticket 15515.
9458 o Minor features (geoip):
9459 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
9460 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
9463 o Minor features (HS popularity countermeasure):
9464 - To avoid leaking HS popularity, don't cycle the introduction point
9465 when we've handled a fixed number of INTRODUCE2 cells but instead
9466 cycle it when a random number of introductions is reached, thus
9467 making it more difficult for an attacker to find out the amount of
9468 clients that have used the introduction point for a specific HS.
9469 Closes ticket 15745.
9471 o Minor features (logging):
9472 - Include the Tor version in all LD_BUG log messages, since people
9473 tend to cut and paste those into the bugtracker. Implements
9476 o Minor features (pluggable transports):
9477 - When launching managed pluggable transports on Linux systems,
9478 attempt to have the kernel deliver a SIGTERM on tor exit if the
9479 pluggable transport process is still running. Resolves
9481 - When launching managed pluggable transports, setup a valid open
9482 stdin in the child process that can be used to detect if tor has
9483 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
9484 can be used by implementations to detect this new behavior.
9485 Resolves ticket 15435.
9487 o Minor features (testing):
9488 - Add a test to verify that the compiler does not eliminate our
9489 memwipe() implementation. Closes ticket 15377.
9490 - Add make rule `check-changes` to verify the format of changes
9491 files. Closes ticket 15180.
9492 - Add unit tests for control_event_is_interesting(). Add a compile-
9493 time check that the number of events doesn't exceed the capacity
9494 of control_event_t.event_mask. Closes ticket 15431, checks for
9495 bugs similar to 13085. Patch by "teor".
9496 - Command-line argument tests moved to Stem. Resolves ticket 14806.
9497 - Integrate the ntor, backtrace, and zero-length keys tests into the
9498 automake test suite. Closes ticket 15344.
9499 - Remove assertions during builds to determine Tor's test coverage.
9500 We don't want to trigger these even in assertions, so including
9501 them artificially makes our branch coverage look worse than it is.
9502 This patch provides the new test-stem-full and coverage-html-full
9503 configure options. Implements ticket 15400.
9505 o Minor bugfixes (build):
9506 - Improve out-of-tree builds by making non-standard rules work and
9507 clean up additional files and directories. Fixes bug 15053; bugfix
9510 o Minor bugfixes (command-line interface):
9511 - When "--quiet" is provided along with "--validate-config", do not
9512 write anything to stdout on success. Fixes bug 14994; bugfix
9514 - When complaining about bad arguments to "--dump-config", use
9517 o Minor bugfixes (configuration, unit tests):
9518 - Only add the default fallback directories when the DirAuthorities,
9519 AlternateDirAuthority, and FallbackDir directory config options
9520 are set to their defaults. The default fallback directory list is
9521 currently empty, this fix will only change tor's behavior when it
9522 has default fallback directories. Includes unit tests for
9523 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
9524 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
9526 o Minor bugfixes (correctness):
9527 - For correctness, avoid modifying a constant string in
9528 handle_control_postdescriptor. Fixes bug 15546; bugfix
9530 - Remove side-effects from tor_assert() calls. This was harmless,
9531 because we never disable assertions, but it is bad style and
9532 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
9535 o Minor bugfixes (hidden service):
9536 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9537 a client authorized hidden service. Fixes bug 15823; bugfix
9539 - Remove an extraneous newline character from the end of hidden
9540 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
9542 o Minor bugfixes (interface):
9543 - Print usage information for --dump-config when it is used without
9544 an argument. Also, fix the error message to use different wording
9545 and add newline at the end. Fixes bug 15541; bugfix
9548 o Minor bugfixes (logs):
9549 - When building Tor under Clang, do not include an extra set of
9550 parentheses in log messages that include function names. Fixes bug
9551 15269; bugfix on every released version of Tor when compiled with
9552 recent enough Clang.
9554 o Minor bugfixes (network):
9555 - When attempting to use fallback technique for network interface
9556 lookup, disregard loopback and multicast addresses since they are
9557 unsuitable for public communications.
9559 o Minor bugfixes (statistics):
9560 - Disregard the ConnDirectionStatistics torrc options when Tor is
9561 not a relay since in that mode of operation no sensible data is
9562 being collected and because Tor might run into measurement hiccups
9563 when running as a client for some time, then becoming a relay.
9564 Fixes bug 15604; bugfix on 0.2.2.35.
9566 o Minor bugfixes (test networks):
9567 - When self-testing reachability, use ExtendAllowPrivateAddresses to
9568 determine if local/private addresses imply reachability. The
9569 previous fix used TestingTorNetwork, which implies
9570 ExtendAllowPrivateAddresses, but this excluded rare configurations
9571 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
9572 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
9573 issue discovered by CJ Ess.
9575 o Minor bugfixes (testing):
9576 - Check for matching value in server response in ntor_ref.py. Fixes
9577 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
9579 - Set the severity correctly when testing
9580 get_interface_addresses_ifaddrs() and
9581 get_interface_addresses_win32(), so that the tests fail gracefully
9582 instead of triggering an assertion. Fixes bug 15759; bugfix on
9583 0.2.6.3-alpha. Reported by Nicolas Derive.
9585 o Code simplification and refactoring:
9586 - Move the hacky fallback code out of get_interface_address6() into
9587 separate function and get it covered with unit-tests. Resolves
9589 - Refactor hidden service client-side cache lookup to intelligently
9590 report its various failure cases, and disentangle failure cases
9591 involving a lack of introduction points. Closes ticket 14391.
9592 - Use our own Base64 encoder instead of OpenSSL's, to allow more
9593 control over the output. Part of ticket 15652.
9596 - Improve the descriptions of statistics-related torrc options in
9597 the manpage to describe rationale and possible uses cases. Fixes
9599 - Improve the layout and formatting of ./configure --help messages.
9600 Closes ticket 15024. Patch from "cypherpunks".
9601 - Standardize on the term "server descriptor" in the manual page.
9602 Previously, we had used "router descriptor", "server descriptor",
9603 and "relay descriptor" interchangeably. Part of ticket 14987.
9606 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
9607 and always use the internal Base64 decoder. The internal decoder
9608 has been part of tor since 0.2.0.10-alpha, and no one should
9609 be using the OpenSSL one. Part of ticket 15652.
9610 - Remove the 'tor_strclear()' function; use memwipe() instead.
9611 Closes ticket 14922.
9614 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
9615 fingerprinting we now recommend pluggable transports; for forward-
9616 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
9617 - Remove the undocumented "--digests" command-line option. It
9618 complicated our build process, caused subtle build issues on
9619 multiple platforms, and is now redundant since we started
9620 including git version identifiers. Closes ticket 14742.
9621 - Tor no longer contains checks for ancient directory cache versions
9622 that didn't know about microdescriptors.
9623 - Tor no longer contains workarounds for stat files generated by
9624 super-old versions of Tor that didn't choose guards sensibly.
9627 Changes in version 0.2.4.27 - 2015-04-06
9628 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
9629 could be used by an attacker to crash hidden services, or crash clients
9630 visiting hidden services. Hidden services should upgrade as soon as
9631 possible; clients should upgrade whenever packages become available.
9633 This release also backports a simple improvement to make hidden
9634 services a bit less vulnerable to denial-of-service attacks.
9636 o Major bugfixes (security, hidden service):
9637 - Fix an issue that would allow a malicious client to trigger an
9638 assertion failure and halt a hidden service. Fixes bug 15600;
9639 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
9640 - Fix a bug that could cause a client to crash with an assertion
9641 failure when parsing a malformed hidden service descriptor. Fixes
9642 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
9644 o Minor features (DoS-resistance, hidden service):
9645 - Introduction points no longer allow multiple INTRODUCE1 cells to
9646 arrive on the same circuit. This should make it more expensive for
9647 attackers to overwhelm hidden services with introductions.
9648 Resolves ticket 15515.
9651 Changes in version 0.2.5.12 - 2015-04-06
9652 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
9653 could be used by an attacker to crash hidden services, or crash clients
9654 visiting hidden services. Hidden services should upgrade as soon as
9655 possible; clients should upgrade whenever packages become available.
9657 This release also backports a simple improvement to make hidden
9658 services a bit less vulnerable to denial-of-service attacks.
9660 o Major bugfixes (security, hidden service):
9661 - Fix an issue that would allow a malicious client to trigger an
9662 assertion failure and halt a hidden service. Fixes bug 15600;
9663 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
9664 - Fix a bug that could cause a client to crash with an assertion
9665 failure when parsing a malformed hidden service descriptor. Fixes
9666 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
9668 o Minor features (DoS-resistance, hidden service):
9669 - Introduction points no longer allow multiple INTRODUCE1 cells to
9670 arrive on the same circuit. This should make it more expensive for
9671 attackers to overwhelm hidden services with introductions.
9672 Resolves ticket 15515.
9675 Changes in version 0.2.6.7 - 2015-04-06
9676 Tor 0.2.6.7 fixes two security issues that could be used by an
9677 attacker to crash hidden services, or crash clients visiting hidden
9678 services. Hidden services should upgrade as soon as possible; clients
9679 should upgrade whenever packages become available.
9681 This release also contains two simple improvements to make hidden
9682 services a bit less vulnerable to denial-of-service attacks.
9684 o Major bugfixes (security, hidden service):
9685 - Fix an issue that would allow a malicious client to trigger an
9686 assertion failure and halt a hidden service. Fixes bug 15600;
9687 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
9688 - Fix a bug that could cause a client to crash with an assertion
9689 failure when parsing a malformed hidden service descriptor. Fixes
9690 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
9692 o Minor features (DoS-resistance, hidden service):
9693 - Introduction points no longer allow multiple INTRODUCE1 cells to
9694 arrive on the same circuit. This should make it more expensive for
9695 attackers to overwhelm hidden services with introductions.
9696 Resolves ticket 15515.
9697 - Decrease the amount of reattempts that a hidden service performs
9698 when its rendezvous circuits fail. This reduces the computational
9699 cost for running a hidden service under heavy load. Resolves
9703 Changes in version 0.2.6.6 - 2015-03-24
9704 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
9706 It adds numerous safety, security, correctness, and performance
9707 improvements. Client programs can be configured to use more kinds of
9708 sockets, AutomapHosts works better, the multithreading backend is
9709 improved, cell transmission is refactored, test coverage is much
9710 higher, more denial-of-service attacks are handled, guard selection is
9711 improved to handle long-term guards better, pluggable transports
9712 should work a bit better, and some annoying hidden service performance
9713 bugs should be addressed.
9715 o Minor bugfixes (portability):
9716 - Use the correct datatype in the SipHash-2-4 function to prevent
9717 compilers from assuming any sort of alignment. Fixes bug 15436;
9718 bugfix on 0.2.5.3-alpha.
9720 Changes in version 0.2.6.5-rc - 2015-03-18
9721 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
9722 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
9724 o Major bugfixes (client):
9725 - Avoid crashing when making certain configuration option changes on
9726 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
9729 o Major bugfixes (pluggable transports):
9730 - Initialize the extended OR Port authentication cookie before
9731 launching pluggable transports. This prevents a race condition
9732 that occurred when server-side pluggable transports would cache the
9733 authentication cookie before it has been (re)generated. Fixes bug
9734 15240; bugfix on 0.2.5.1-alpha.
9736 o Major bugfixes (portability):
9737 - Do not crash on startup when running on Solaris. Fixes a bug
9738 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
9741 o Minor features (heartbeat):
9742 - On relays, report how many connections we negotiated using each
9743 version of the Tor link protocols. This information will let us
9744 know if removing support for very old versions of the Tor
9745 protocols is harming the network. Closes ticket 15212.
9747 o Code simplification and refactoring:
9748 - Refactor main loop to extract the 'loop' part. This makes it
9749 easier to run Tor under Shadow. Closes ticket 15176.
9752 Changes in version 0.2.5.11 - 2015-03-17
9753 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
9755 It backports several bugfixes from the 0.2.6 branch, including a
9756 couple of medium-level security fixes for relays and exit nodes.
9757 It also updates the list of directory authorities.
9759 o Directory authority changes:
9760 - Remove turtles as a directory authority.
9761 - Add longclaw as a new (v3) directory authority. This implements
9762 ticket 13296. This keeps the directory authority count at 9.
9763 - The directory authority Faravahar has a new IP address. This
9764 closes ticket 14487.
9766 o Major bugfixes (crash, OSX, security):
9767 - Fix a remote denial-of-service opportunity caused by a bug in
9768 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
9771 o Major bugfixes (relay, stability, possible security):
9772 - Fix a bug that could lead to a relay crashing with an assertion
9773 failure if a buffer of exactly the wrong layout was passed to
9774 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
9775 0.2.0.10-alpha. Patch from 'cypherpunks'.
9776 - Do not assert if the 'data' pointer on a buffer is advanced to the
9777 very end of the buffer; log a BUG message instead. Only assert if
9778 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
9780 o Major bugfixes (exit node stability):
9781 - Fix an assertion failure that could occur under high DNS load.
9782 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
9783 diagnosed and fixed by "cypherpunks".
9785 o Major bugfixes (Linux seccomp2 sandbox):
9786 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
9787 crash during attempts to call wait4. Fixes bug 15088; bugfix on
9788 0.2.5.1-alpha. Patch from "sanic".
9790 o Minor features (controller):
9791 - New "GETINFO bw-event-cache" to get information about recent
9792 bandwidth events. Closes ticket 14128. Useful for controllers to
9793 get recent bandwidth history after the fix for ticket 13988.
9795 o Minor features (geoip):
9796 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
9797 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
9800 o Minor bugfixes (client, automapping):
9801 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
9802 no value follows the option. Fixes bug 14142; bugfix on
9803 0.2.4.7-alpha. Patch by "teor".
9804 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
9805 14195; bugfix on 0.1.0.1-rc.
9807 o Minor bugfixes (compilation):
9808 - Build without warnings with the stock OpenSSL srtp.h header, which
9809 has a duplicate declaration of SSL_get_selected_srtp_profile().
9810 Fixes bug 14220; this is OpenSSL's bug, not ours.
9812 o Minor bugfixes (directory authority):
9813 - Allow directory authorities to fetch more data from one another if
9814 they find themselves missing lots of votes. Previously, they had
9815 been bumping against the 10 MB queued data limit. Fixes bug 14261;
9816 bugfix on 0.1.2.5-alpha.
9817 - Enlarge the buffer to read bwauth generated files to avoid an
9818 issue when parsing the file in dirserv_read_measured_bandwidths().
9819 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
9821 o Minor bugfixes (statistics):
9822 - Increase period over which bandwidth observations are aggregated
9823 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
9825 o Minor bugfixes (preventative security, C safety):
9826 - When reading a hexadecimal, base-32, or base-64 encoded value from
9827 a string, always overwrite the whole output buffer. This prevents
9828 some bugs where we would look at (but fortunately, not reveal)
9829 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
9833 Changes in version 0.2.4.26 - 2015-03-17
9834 Tor 0.2.4.26 includes an updated list of directory authorities. It
9835 also backports a couple of stability and security bugfixes from 0.2.5
9838 o Directory authority changes:
9839 - Remove turtles as a directory authority.
9840 - Add longclaw as a new (v3) directory authority. This implements
9841 ticket 13296. This keeps the directory authority count at 9.
9842 - The directory authority Faravahar has a new IP address. This
9843 closes ticket 14487.
9845 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
9846 - Fix an assertion failure that could occur under high DNS load.
9847 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
9848 diagnosed and fixed by "cypherpunks".
9850 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
9851 - Fix a bug that could lead to a relay crashing with an assertion
9852 failure if a buffer of exactly the wrong layout was passed to
9853 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
9854 0.2.0.10-alpha. Patch from 'cypherpunks'.
9855 - Do not assert if the 'data' pointer on a buffer is advanced to the
9856 very end of the buffer; log a BUG message instead. Only assert if
9857 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
9859 o Minor features (geoip):
9860 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
9861 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
9864 Changes in version 0.2.6.4-rc - 2015-03-09
9865 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
9866 attacker might be able to use in order to crash certain Tor
9867 directories. It also resolves some minor issues left over from, or
9868 introduced in, Tor 0.2.6.3-alpha or earlier.
9870 o Major bugfixes (crash, OSX, security):
9871 - Fix a remote denial-of-service opportunity caused by a bug in
9872 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
9875 o Major bugfixes (relay, stability, possible security):
9876 - Fix a bug that could lead to a relay crashing with an assertion
9877 failure if a buffer of exactly the wrong layout is passed to
9878 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
9879 0.2.0.10-alpha. Patch from "cypherpunks".
9880 - Do not assert if the 'data' pointer on a buffer is advanced to the
9881 very end of the buffer; log a BUG message instead. Only assert if
9882 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
9884 o Major bugfixes (FreeBSD IPFW transparent proxy):
9885 - Fix address detection with FreeBSD transparent proxies, when
9886 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
9889 o Major bugfixes (Linux seccomp2 sandbox):
9890 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
9891 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
9893 - Allow AF_UNIX hidden services to be used with the seccomp2
9894 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
9895 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
9896 crash during attempts to call wait4. Fixes bug 15088; bugfix on
9897 0.2.5.1-alpha. Patch from "sanic".
9899 o Minor features (controller):
9900 - Messages about problems in the bootstrap process now include
9901 information about the server we were trying to connect to when we
9902 noticed the problem. Closes ticket 15006.
9904 o Minor features (geoip):
9905 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
9906 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
9909 o Minor features (logs):
9910 - Quiet some log messages in the heartbeat and at startup. Closes
9913 o Minor bugfixes (certificate handling):
9914 - If an authority operator accidentally makes a signing certificate
9915 with a future publication time, do not discard its real signing
9916 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
9917 - Remove any old authority certificates that have been superseded
9918 for at least two days. Previously, we would keep superseded
9919 certificates until they expired, if they were published close in
9920 time to the certificate that superseded them. Fixes bug 11454;
9921 bugfix on 0.2.1.8-alpha.
9923 o Minor bugfixes (compilation):
9924 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
9926 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
9929 o Minor bugfixes (testing):
9930 - Fix endianness issues in unit test for resolve_my_address() to
9931 have it pass on big endian systems. Fixes bug 14980; bugfix on
9933 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
9934 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
9935 - When running the new 'make test-stem' target, use the configured
9936 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
9938 - When running the zero-length-keys tests, do not use the default
9939 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
9942 o Directory authority IP change:
9943 - The directory authority Faravahar has a new IP address. This
9944 closes ticket 14487.
9947 - Remove some lingering dead code that once supported mempools.
9948 Mempools were disabled by default in 0.2.5, and removed entirely
9949 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
9953 Changes in version 0.2.6.3-alpha - 2015-02-19
9954 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
9955 the 0.2.6.x series. It introduces support for more kinds of sockets,
9956 makes it harder to accidentally run an exit, improves our
9957 multithreading backend, incorporates several fixes for the
9958 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
9960 If no major regressions or security holes are found in this version,
9961 the next version will be a release candidate.
9963 o Deprecated versions:
9964 - Tor relays older than 0.2.4.18-rc are no longer allowed to
9965 advertise themselves on the network. Closes ticket 13555.
9967 o Major features (security, unix domain sockets):
9968 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
9969 applications can reach Tor without having to create AF_INET or
9970 AF_INET6 sockets, meaning they can completely disable their
9971 ability to make non-Tor network connections. To create a socket of
9972 this type, use "SocksPort unix:/path/to/socket". Implements
9974 - Support mapping hidden service virtual ports to AF_UNIX sockets.
9975 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
9976 Implements ticket 11485.
9978 o Major features (changed defaults):
9979 - Prevent relay operators from unintentionally running exits: When a
9980 relay is configured as an exit node, we now warn the user unless
9981 the "ExitRelay" option is set to 1. We warn even more loudly if
9982 the relay is configured with the default exit policy, since this
9983 can indicate accidental misconfiguration. Setting "ExitRelay 0"
9984 stops Tor from running as an exit relay. Closes ticket 10067.
9986 o Major features (directory system):
9987 - When downloading server- or microdescriptors from a directory
9988 server, we no longer launch multiple simultaneous requests to the
9989 same server. This reduces load on the directory servers,
9990 especially when directory guards are in use. Closes ticket 9969.
9991 - When downloading server- or microdescriptors over a tunneled
9992 connection, do not limit the length of our requests to what the
9993 Squid proxy is willing to handle. Part of ticket 9969.
9994 - Authorities can now vote on the correct digests and latest
9995 versions for different software packages. This allows packages
9996 that include Tor to use the Tor authority system as a way to get
9997 notified of updates and their correct digests. Implements proposal
9998 227. Closes ticket 10395.
10000 o Major features (guards):
10001 - Introduce the Guardfraction feature to improves load balancing on
10002 guard nodes. Specifically, it aims to reduce the traffic gap that
10003 guard nodes experience when they first get the Guard flag. This is
10004 a required step if we want to increase the guard lifetime to 9
10005 months or greater. Closes ticket 9321.
10007 o Major features (performance):
10008 - Make the CPU worker implementation more efficient by avoiding the
10009 kernel and lengthening pipelines. The original implementation used
10010 sockets to transfer data from the main thread to the workers, and
10011 didn't allow any thread to be assigned more than a single piece of
10012 work at once. The new implementation avoids communications
10013 overhead by making requests in shared memory, avoiding kernel IO
10014 where possible, and keeping more requests in flight at once.
10015 Implements ticket 9682.
10017 o Major features (relay):
10018 - Raise the minimum acceptable configured bandwidth rate for bridges
10019 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
10020 20 KiB/sec.) Closes ticket 13822.
10022 o Major bugfixes (exit node stability):
10023 - Fix an assertion failure that could occur under high DNS load.
10024 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
10025 diagnosed and fixed by "cypherpunks".
10027 o Major bugfixes (mixed relay-client operation):
10028 - When running as a relay and client at the same time (not
10029 recommended), if we decide not to use a new guard because we want
10030 to retry older guards, only close the locally-originating circuits
10031 passing through that guard. Previously we would close all the
10032 circuits through that guard. Fixes bug 9819; bugfix on
10033 0.2.1.1-alpha. Reported by "skruffy".
10035 o Minor features (build):
10036 - New --disable-system-torrc compile-time option to prevent Tor from
10037 looking for the system-wide torrc or torrc-defaults files.
10038 Resolves ticket 13037.
10040 o Minor features (controller):
10041 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
10042 events so controllers can observe circuit isolation inputs. Closes
10044 - ControlPort now supports the unix:/path/to/socket syntax as an
10045 alternative to the ControlSocket option, for consistency with
10046 SocksPort and HiddenServicePort. Closes ticket 14451.
10047 - New "GETINFO bw-event-cache" to get information about recent
10048 bandwidth events. Closes ticket 14128. Useful for controllers to
10049 get recent bandwidth history after the fix for ticket 13988.
10051 o Minor features (Denial of service resistance):
10052 - Count the total number of bytes used storing hidden service
10053 descriptors against the value of MaxMemInQueues. If we're low on
10054 memory, and more than 20% of our memory is used holding hidden
10055 service descriptors, free them until no more than 10% of our
10056 memory holds hidden service descriptors. Free the least recently
10057 fetched descriptors first. Resolves ticket 13806.
10058 - When we have recently been under memory pressure (over 3/4 of
10059 MaxMemInQueues is allocated), then allocate smaller zlib objects
10060 for small requests. Closes ticket 11791.
10062 o Minor features (geoip):
10063 - Update geoip and geoip6 files to the January 7 2015 Maxmind
10064 GeoLite2 Country database.
10066 o Minor features (guard nodes):
10067 - Reduce the time delay before saving guard status to disk from 10
10068 minutes to 30 seconds (or from one hour to 10 minutes if
10069 AvoidDiskWrites is set). Closes ticket 12485.
10071 o Minor features (hidden service):
10072 - Make Sybil attacks against hidden services harder by changing the
10073 minimum time required to get the HSDir flag from 25 hours up to 96
10074 hours. Addresses ticket 14149.
10075 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
10076 services to disable the anti-scanning feature introduced in
10077 0.2.6.2-alpha. With this option not set, a connection to an
10078 unlisted port closes the circuit. With this option set, only a
10079 RELAY_DONE cell is sent. Closes ticket 14084.
10081 o Minor features (interface):
10082 - Implement "-f -" command-line option to read torrc configuration
10083 from standard input, if you don't want to store the torrc file in
10084 the file system. Implements feature 13865.
10086 o Minor features (logging):
10087 - Add a count of unique clients to the bridge heartbeat message.
10088 Resolves ticket 6852.
10089 - Suppress "router info incompatible with extra info" message when
10090 reading extrainfo documents from cache. (This message got loud
10091 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
10093 - Elevate hidden service authorized-client message from DEBUG to
10094 INFO. Closes ticket 14015.
10096 o Minor features (stability):
10097 - Add assertions in our hash-table iteration code to check for
10098 corrupted values that could cause infinite loops. Closes
10101 o Minor features (systemd):
10102 - Various improvements and modernizations in systemd hardening
10103 support. Closes ticket 13805. Patch from Craig Andrews.
10105 o Minor features (testing networks):
10106 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
10107 and the default on a testing network to 2 minutes. Drop the
10108 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
10109 keep the default on a testing network at 30 seconds. This reduces
10110 HS bootstrap time to around 25 seconds. Also, change the default
10111 time in test-network.sh to match. Closes ticket 13401. Patch
10113 - Create TestingDirAuthVoteHSDir to correspond to
10114 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
10115 HSDir flag for the listed relays regardless of uptime or ORPort
10116 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
10117 Partial implementation for ticket 14067. Patch by "teor".
10119 o Minor features (tor2web mode):
10120 - Introduce the config option Tor2webRendezvousPoints, which allows
10121 clients in Tor2webMode to select a specific Rendezvous Point to be
10122 used in HS circuits. This might allow better performance for
10123 Tor2Web nodes. Implements ticket 12844.
10125 o Minor bugfixes (client DNS):
10126 - Report the correct cached DNS expiration times on SOCKS port or in
10127 DNS replies. Previously, we would report everything as "never
10128 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
10129 - Avoid a small memory leak when we find a cached answer for a
10130 reverse DNS lookup in a client-side DNS cache. (Remember, client-
10131 side DNS caching is off by default, and is not recommended.) Fixes
10132 bug 14259; bugfix on 0.2.0.1-alpha.
10134 o Minor bugfixes (client, automapping):
10135 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
10136 no value follows the option. Fixes bug 14142; bugfix on
10137 0.2.4.7-alpha. Patch by "teor".
10138 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
10139 14195; bugfix on 0.1.0.1-rc.
10140 - Prevent changes to other options from removing the wildcard value
10141 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
10143 - Allow MapAddress and AutomapHostsOnResolve to work together when
10144 an address is mapped into another address type (like .onion) that
10145 must be automapped at resolve time. Fixes bug 7555; bugfix
10148 o Minor bugfixes (client, bridges):
10149 - When we are using bridges and we had a network connectivity
10150 problem, only retry connecting to our currently configured
10151 bridges, not all bridges we know about and remember using. Fixes
10152 bug 14216; bugfix on 0.2.2.17-alpha.
10154 o Minor bugfixes (client, IPv6):
10155 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
10156 flag is not set; and not because the NoIPv4Traffic flag was set.
10157 Previously we'd looked at the NoIPv4Traffic flag for both types of
10158 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
10160 o Minor bugfixes (compilation):
10161 - The address of an array in the middle of a structure will always
10162 be non-NULL. clang recognises this and complains. Disable the
10163 tautologous and redundant check to silence this warning. Fixes bug
10164 14001; bugfix on 0.2.1.2-alpha.
10165 - Avoid warnings when building with systemd 209 or later. Fixes bug
10166 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
10167 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
10168 Addresses ticket 14188.
10169 - Build without warnings with the stock OpenSSL srtp.h header, which
10170 has a duplicate declaration of SSL_get_selected_srtp_profile().
10171 Fixes bug 14220; this is OpenSSL's bug, not ours.
10172 - Do not compile any code related to Tor2Web mode when Tor2Web mode
10173 is not enabled at compile time. Previously, this code was included
10174 in a disabled state. See discussion on ticket 12844.
10175 - Remove the --disable-threads configure option again. It was
10176 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
10177 14819; bugfix on 0.2.6.2-alpha.
10179 o Minor bugfixes (controller):
10180 - Report "down" in response to the "GETINFO entry-guards" command
10181 when relays are down with an unreachable_since value. Previously,
10182 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
10183 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
10184 14116; bugfix on 0.2.2.9-alpha.
10185 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
10186 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
10188 o Minor bugfixes (directory authority):
10189 - Allow directory authorities to fetch more data from one another if
10190 they find themselves missing lots of votes. Previously, they had
10191 been bumping against the 10 MB queued data limit. Fixes bug 14261;
10192 bugfix on 0.1.2.5-alpha.
10193 - Do not attempt to download extrainfo documents which we will be
10194 unable to validate with a matching server descriptor. Fixes bug
10195 13762; bugfix on 0.2.0.1-alpha.
10196 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
10197 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
10198 - Enlarge the buffer to read bwauth generated files to avoid an
10199 issue when parsing the file in dirserv_read_measured_bandwidths().
10200 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
10202 o Minor bugfixes (file handling):
10203 - Stop failing when key files are zero-length. Instead, generate new
10204 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
10205 on all versions of Tor. Patch by "teor".
10206 - Stop generating a fresh .old RSA onion key file when the .old file
10207 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
10208 - Avoid overwriting .old key files with empty key files.
10209 - Skip loading zero-length extrainfo store, router store, stats,
10210 state, and key files.
10211 - Avoid crashing when trying to reload a torrc specified as a
10212 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
10215 o Minor bugfixes (hidden services):
10216 - Close the introduction circuit when we have no more usable intro
10217 points, instead of waiting for it to time out. This also ensures
10218 that no follow-up HS descriptor fetch is triggered when the
10219 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
10220 - When fetching a hidden service descriptor for a down service that
10221 was recently up, do not keep refetching until we try the same
10222 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
10223 - Successfully launch Tor with a nonexistent hidden service
10224 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
10225 14106; bugfix on 0.2.6.2-alpha.
10227 o Minor bugfixes (logging):
10228 - Avoid crashing when there are more log domains than entries in
10229 domain_list. Bugfix on 0.2.3.1-alpha.
10230 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
10232 - Don't log messages to stdout twice when starting up. Fixes bug
10233 13993; bugfix on 0.2.6.1-alpha.
10235 o Minor bugfixes (parsing):
10236 - Stop accepting milliseconds (or other junk) at the end of
10237 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
10238 - Support two-number and three-number version numbers correctly, in
10239 case we change the Tor versioning system in the future. Fixes bug
10240 13661; bugfix on 0.0.8pre1.
10242 o Minor bugfixes (path counting):
10243 - When deciding whether the consensus lists any exit nodes, count
10244 the number listed in the consensus, not the number we have
10245 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
10246 - When deciding whether we have any exit nodes, only examine
10247 ExitNodes when the ExitNodes option is actually set. Fixes part of
10248 bug 14918; bugfix on 0.2.6.2-alpha.
10249 - Get rid of redundant and possibly scary warnings that we are
10250 missing directory information while we bootstrap. Fixes part of
10251 bug 14918; bugfix on 0.2.6.2-alpha.
10253 o Minor bugfixes (portability):
10254 - Fix the ioctl()-based network interface lookup code so that it
10255 will work on systems that have variable-length struct ifreq, for
10257 - Fix scheduler compilation on targets where char is unsigned. Fixes
10258 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
10260 o Minor bugfixes (sandbox):
10261 - Allow glibc fatal errors to be sent to stderr before Tor exits.
10262 Previously, glibc would try to write them to /dev/tty, and the
10263 sandbox would trap the call and make Tor exit prematurely. Fixes
10264 bug 14759; bugfix on 0.2.5.1-alpha.
10266 o Minor bugfixes (shutdown):
10267 - When shutting down, always call event_del() on lingering read or
10268 write events before freeing them. Otherwise, we risk double-frees
10269 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
10272 o Minor bugfixes (small memory leaks):
10273 - Avoid leaking memory when using IPv6 virtual address mappings.
10274 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
10277 o Minor bugfixes (statistics):
10278 - Increase period over which bandwidth observations are aggregated
10279 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
10281 o Minor bugfixes (systemd support):
10282 - Fix detection and operation of systemd watchdog. Fixes part of bug
10283 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
10284 - Run correctly under systemd with the RunAsDaemon option set. Fixes
10285 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
10286 - Inform the systemd supervisor about more changes in the Tor
10287 process status. Implements part of ticket 14141. Patch from
10289 - Cause the "--disable-systemd" option to actually disable systemd
10290 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
10293 o Minor bugfixes (TLS):
10294 - Check more thoroughly throughout the TLS code for possible
10295 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
10297 o Minor bugfixes (transparent proxy):
10298 - Use getsockname, not getsockopt, to retrieve the address for a
10299 TPROXY-redirected connection. Fixes bug 13796; bugfix
10302 o Code simplification and refactoring:
10303 - Move fields related to isolating and configuring client ports into
10304 a shared structure. Previously, they were duplicated across
10305 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
10306 to copy them correctly had been the cause of at least one bug in
10307 the past. Closes ticket 8546.
10308 - Refactor the get_interface_addresses_raw() doom-function into
10309 multiple smaller and simpler subfunctions. Cover the resulting
10310 subfunctions with unit-tests. Fixes a significant portion of
10312 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
10313 only for version <= 0.2.2.24 which is now deprecated. Closes
10315 - Remove a test for a long-defunct broken version-one
10319 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
10320 for writing the OpenBSD-specific tips. Resolves ticket 13702.
10321 - Make the tor-resolve documentation match its help string and its
10322 options. Resolves part of ticket 14325.
10323 - Log a more useful error message from tor-resolve when failing to
10324 look up a hidden service address. Resolves part of ticket 14325.
10326 o Downgraded warnings:
10327 - Don't warn when we've attempted to contact a relay using the wrong
10328 ntor onion key. Closes ticket 9635.
10330 o Removed features:
10331 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
10332 longer silently accepted as an alias for "ExitNodes".
10333 - The --enable-mempool and --enable-buf-freelists options, which
10334 were originally created to work around bad malloc implementations,
10335 no longer exist. They were off-by-default in 0.2.5. Closes
10339 - Make the checkdir/perms test complete successfully even if the
10340 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
10341 - Test that tor does not fail when key files are zero-length. Check
10342 that tor generates new keys, and overwrites the empty key files.
10343 - Test that tor generates new keys when keys are missing
10344 (existing behavior).
10345 - Test that tor does not overwrite key files that already contain
10346 data (existing behavior). Tests bug 13111. Patch by "teor".
10347 - New "make test-stem" target to run stem integration tests.
10348 Requires that the "STEM_SOURCE_DIR" environment variable be set.
10349 Closes ticket 14107.
10350 - Make the test_cmdline_args.py script work correctly on Windows.
10351 Patch from Gisle Vanem.
10352 - Move the slower unit tests into a new "./src/test/test-slow"
10353 binary that can be run independently of the other tests. Closes
10355 - Avoid undefined behavior when sampling huge values from the
10356 Laplace distribution. This made unittests fail on Raspberry Pi.
10357 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
10360 Changes in version 0.2.6.2-alpha - 2014-12-31
10361 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
10362 It introduces a major new backend for deciding when to send cells on
10363 channels, which should lead down the road to big performance
10364 increases. It contains security and statistics features for better
10365 work on hidden services, and numerous bugfixes.
10367 This release contains many new unit tests, along with major
10368 performance improvements for running testing networks using Chutney.
10369 Thanks to a series of patches contributed by "teor", testing networks
10370 should now bootstrap in seconds, rather than minutes.
10372 o Major features (relay, infrastructure):
10373 - Complete revision of the code that relays use to decide which cell
10374 to send next. Formerly, we selected the best circuit to write on
10375 each channel, but we didn't select among channels in any
10376 sophisticated way. Now, we choose the best circuits globally from
10377 among those whose channels are ready to deliver traffic.
10379 This patch implements a new inter-cmux comparison API, a global
10380 high/low watermark mechanism and a global scheduler loop for
10381 transmission prioritization across all channels as well as among
10382 circuits on one channel. This schedule is currently tuned to
10383 (tolerantly) avoid making changes in network performance, but it
10384 should form the basis for major circuit performance increases in
10385 the future. Code by Andrea; tuning by Rob Jansen; implements
10388 o Major features (hidden services):
10389 - Make HS port scanning more difficult by immediately closing the
10390 circuit when a user attempts to connect to a nonexistent port.
10391 Closes ticket 13667.
10392 - Add a HiddenServiceStatistics option that allows Tor relays to
10393 gather and publish statistics about the overall size and volume of
10394 hidden service usage. Specifically, when this option is turned on,
10395 an HSDir will publish an approximate number of hidden services
10396 that have published descriptors to it the past 24 hours. Also, if
10397 a relay has acted as a hidden service rendezvous point, it will
10398 publish the approximate amount of rendezvous cells it has relayed
10399 the past 24 hours. The statistics themselves are obfuscated so
10400 that the exact values cannot be derived. For more details see
10401 proposal 238, "Better hidden service stats from Tor relays". This
10402 feature is currently disabled by default. Implements feature 13192.
10404 o Major bugfixes (client, automap):
10405 - Repair automapping with IPv6 addresses. This automapping should
10406 have worked previously, but one piece of debugging code that we
10407 inserted to detect a regression actually caused the regression to
10408 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
10409 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
10412 o Major bugfixes (hidden services):
10413 - When closing an introduction circuit that was opened in parallel
10414 with others, don't mark the introduction point as unreachable.
10415 Previously, the first successful connection to an introduction
10416 point would make the other introduction points get marked as
10417 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
10419 o Directory authority changes:
10420 - Remove turtles as a directory authority.
10421 - Add longclaw as a new (v3) directory authority. This implements
10422 ticket 13296. This keeps the directory authority count at 9.
10424 o Major removed features:
10425 - Tor clients no longer support connecting to hidden services
10426 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
10427 option has been removed. (There shouldn't be any hidden services
10428 running these versions on the network.) Closes ticket 7803.
10430 o Minor features (client):
10431 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
10432 is enabled, reject requests with IP addresses as hostnames.
10433 Resolves ticket 13315.
10435 o Minor features (controller):
10436 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
10437 write an unscheduled heartbeat message to the log. Implements
10440 o Minor features (geoip):
10441 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
10444 o Minor features (hidden services):
10445 - When re-enabling the network, don't try to build introduction
10446 circuits until we have successfully built a circuit. This makes
10447 hidden services come up faster when the network is re-enabled.
10448 Patch from "akwizgran". Closes ticket 13447.
10449 - When we fail to retrieve a hidden service descriptor, send the
10450 controller an "HS_DESC FAILED" controller event. Implements
10452 - New HiddenServiceDirGroupReadable option to cause hidden service
10453 directories and hostname files to be created group-readable. Patch
10454 from "anon", David Stainton, and "meejah". Closes ticket 11291.
10456 o Minor features (systemd):
10457 - Where supported, when running with systemd, report successful
10458 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
10459 - When running with systemd, support systemd watchdog messages. Part
10460 of ticket 11016. Patch by Michael Scherer.
10462 o Minor features (transparent proxy):
10463 - Update the transparent proxy option checks to allow for both ipfw
10464 and pf on OS X. Closes ticket 14002.
10465 - Use the correct option when using IPv6 with transparent proxy
10466 support on Linux. Resolves 13808. Patch by Francisco Blas
10469 o Minor bugfixes (preventative security, C safety):
10470 - When reading a hexadecimal, base-32, or base-64 encoded value from
10471 a string, always overwrite the whole output buffer. This prevents
10472 some bugs where we would look at (but fortunately, not reveal)
10473 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
10475 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
10476 just the part that's used. This makes it harder for data leak bugs
10477 to occur in the event of other programming failures. Resolves
10480 o Minor bugfixes (client, microdescriptors):
10481 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
10482 computing which microdescriptors to download. This keeps us from
10483 erroneous download behavior if two microdescriptor digests ever
10484 have the same first 160 bits. Fixes part of bug 13399; bugfix
10486 - Reset a router's status if its microdescriptor digest changes,
10487 even if the first 160 bits remain the same. Fixes part of bug
10488 13399; bugfix on 0.2.3.1-alpha.
10490 o Minor bugfixes (compilation):
10491 - Silence clang warnings under --enable-expensive-hardening,
10492 including implicit truncation of 64 bit values to 32 bit, const
10493 char assignment to self, tautological compare, and additional
10494 parentheses around equality tests. Fixes bug 13577; bugfix
10496 - Fix a clang warning about checking whether an address in the
10497 middle of a structure is NULL. Fixes bug 14001; bugfix
10500 o Minor bugfixes (hidden services):
10501 - Correctly send a controller event when we find that a rendezvous
10502 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
10503 - Pre-check directory permissions for new hidden-services to avoid
10504 at least one case of "Bug: Acting on config options left us in a
10505 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
10506 - When adding a new hidden service (for example, via SETCONF), Tor
10507 no longer congratulates the user for running a relay. Fixes bug
10508 13941; bugfix on 0.2.6.1-alpha.
10509 - When fetching hidden service descriptors, we now check not only
10510 for whether we got the hidden service we had in mind, but also
10511 whether we got the particular descriptors we wanted. This prevents
10512 a class of inefficient but annoying DoS attacks by hidden service
10513 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
10516 o Minor bugfixes (Linux seccomp2 sandbox):
10517 - Make transparent proxy support work along with the seccomp2
10518 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
10519 by Francisco Blas Izquierdo Riera.
10520 - Fix a memory leak in tor-resolve when running with the sandbox
10521 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
10523 o Minor bugfixes (logging):
10524 - Downgrade warnings about RSA signature failures to info log level.
10525 Emit a warning when an extra info document is found incompatible
10526 with a corresponding router descriptor. Fixes bug 9812; bugfix
10528 - Make connection_ap_handshake_attach_circuit() log the circuit ID
10529 correctly. Fixes bug 13701; bugfix on 0.0.6.
10531 o Minor bugfixes (misc):
10532 - Stop allowing invalid address patterns like "*/24" that contain
10533 both a wildcard address and a bit prefix length. This affects all
10534 our address-range parsing code. Fixes bug 7484; bugfix
10537 o Minor bugfixes (testing networks, fast startup):
10538 - Allow Tor to build circuits using a consensus with no exits. If
10539 the consensus has no exits (typical of a bootstrapping test
10540 network), allow Tor to build circuits once enough descriptors have
10541 been downloaded. This assists in bootstrapping a testing Tor
10542 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
10544 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
10545 header to directory servers. This allows us to obtain consensuses
10546 promptly when the consensus interval is very short. This assists
10547 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
10548 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
10549 - Stop assuming that private addresses are local when checking
10550 reachability in a TestingTorNetwork. Instead, when testing, assume
10551 all OR connections are remote. (This is necessary due to many test
10552 scenarios running all relays on localhost.) This assists in
10553 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
10554 0.1.0.1-rc. Patch by "teor".
10555 - Avoid building exit circuits from a consensus with no exits. Now
10556 thanks to our fix for 13718, we accept a no-exit network as not
10557 wholly lost, but we need to remember not to try to build exit
10558 circuits on it. Closes ticket 13814; patch by "teor".
10559 - Stop requiring exits to have non-zero bandwithcapacity in a
10560 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
10561 ignore exit bandwidthcapacity. This assists in bootstrapping a
10562 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
10563 on 0.2.0.3-alpha. Patch by "teor".
10564 - Add "internal" to some bootstrap statuses when no exits are
10565 available. If the consensus does not contain Exits, Tor will only
10566 build internal circuits. In this case, relevant statuses will
10567 contain the word "internal" as indicated in the Tor control-
10568 spec.txt. When bootstrap completes, Tor will be ready to build
10569 internal circuits. If a future consensus contains Exits, exit
10570 circuits may become available. Fixes part of bug 13718; bugfix on
10571 0.2.4.10-alpha. Patch by "teor".
10572 - Decrease minimum consensus interval to 10 seconds when
10573 TestingTorNetwork is set, or 5 seconds for the first consensus.
10574 Fix assumptions throughout the code that assume larger intervals.
10575 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
10577 - Avoid excluding guards from path building in minimal test
10578 networks, when we're in a test network and excluding guards would
10579 exclude all relays. This typically occurs in incredibly small tor
10580 networks, and those using "TestingAuthVoteGuard *". Fixes part of
10581 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
10583 o Code simplification and refactoring:
10584 - Stop using can_complete_circuits as a global variable; access it
10585 with a function instead.
10586 - Avoid using operators directly as macro arguments: this lets us
10587 apply coccinelle transformations to our codebase more directly.
10588 Closes ticket 13172.
10589 - Combine the functions used to parse ClientTransportPlugin and
10590 ServerTransportPlugin into a single function. Closes ticket 6456.
10591 - Add inline functions and convenience macros for inspecting channel
10592 state. Refactor the code to use convenience macros instead of
10593 checking channel state directly. Fixes issue 7356.
10594 - Document all members of was_router_added_t and rename
10595 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
10596 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
10597 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
10598 constant instead of hardcoded value. Fixes issue 13840.
10599 - Refactor our generic strmap and digestmap types into a single
10600 implementation, so that we can add a new digest256map
10604 - Document the bridge-authority-only 'networkstatus-bridges' file.
10605 Closes ticket 13713; patch from "tom".
10606 - Fix typo in PredictedPortsRelevanceTime option description in
10607 manpage. Resolves issue 13707.
10608 - Stop suggesting that users specify relays by nickname: it isn't a
10609 good idea. Also, properly cross-reference how to specify relays in
10610 all parts of manual documenting options that take a list of
10611 relays. Closes ticket 13381.
10612 - Clarify the HiddenServiceDir option description in manpage to make
10613 it clear that relative paths are taken with respect to the current
10614 working directory. Also clarify that this behavior is not
10615 guaranteed to remain indefinitely. Fixes issue 13913.
10618 - New tests for many parts of channel, relay, and circuitmux
10619 functionality. Code by Andrea; part of 9262.
10620 - New tests for parse_transport_line(). Part of ticket 6456.
10621 - In the unit tests, use chgrp() to change the group of the unit
10622 test temporary directory to the current user, so that the sticky
10623 bit doesn't interfere with tests that check directory groups.
10625 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
10629 Changes in version 0.2.6.1-alpha - 2014-10-30
10630 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
10631 includes numerous code cleanups and new tests, and fixes a large
10632 number of annoying bugs. Out-of-memory conditions are handled better
10633 than in 0.2.5, pluggable transports have improved proxy support, and
10634 clients now use optimistic data for contacting hidden services. Also,
10635 we are now more robust to changes in what we consider a parseable
10636 directory object, so that tightening restrictions does not have a risk
10637 of introducing infinite download loops.
10639 This is the first alpha release in a new series, so expect there to be
10640 bugs. Users who would rather test out a more stable branch should stay
10641 with 0.2.5.x for now.
10643 o New compiler and system requirements:
10644 - Tor 0.2.6.x requires that your compiler support more of the C99
10645 language standard than before. The 'configure' script now detects
10646 whether your compiler supports C99 mid-block declarations and
10647 designated initializers. If it does not, Tor will not compile.
10649 We may revisit this requirement if it turns out that a significant
10650 number of people need to build Tor with compilers that don't
10651 bother implementing a 15-year-old standard. Closes ticket 13233.
10652 - Tor no longer supports systems without threading support. When we
10653 began working on Tor, there were several systems that didn't have
10654 threads, or where the thread support wasn't able to run the
10655 threads of a single process on multiple CPUs. That no longer
10656 holds: every system where Tor needs to run well now has threading
10657 support. Resolves ticket 12439.
10659 o Removed platform support:
10660 - We no longer include special code to build on Windows CE; as far
10661 as we know, nobody has used Tor on Windows CE in a very long time.
10662 Closes ticket 11446.
10664 o Major features (bridges):
10665 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
10666 transports if they are configured via the "TOR_PT_PROXY"
10667 environment variable. Implements proposal 232. Resolves
10670 o Major features (client performance, hidden services):
10671 - Allow clients to use optimistic data when connecting to a hidden
10672 service, which should remove a round-trip from hidden service
10673 initialization. See proposal 181 for details. Implements
10676 o Major features (directory system):
10677 - Upon receiving an unparseable directory object, if its digest
10678 matches what we expected, then don't try to download it again.
10679 Previously, when we got a descriptor we didn't like, we would keep
10680 trying to download it over and over. Closes ticket 11243.
10682 o Major features (sample torrc):
10683 - Add a new, infrequently-changed "torrc.minimal". This file is
10684 similar to torrc.sample, but it will change as infrequently as
10685 possible, for the benefit of users whose systems prompt them for
10686 intervention whenever a default configuration file is changed.
10687 Making this change allows us to update torrc.sample to be a more
10688 generally useful "sample torrc".
10690 o Major bugfixes (directory authorities):
10691 - Do not assign the HSDir flag to relays if they are not Valid, or
10692 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
10694 o Major bugfixes (directory bandwidth performance):
10695 - Don't flush the zlib buffer aggressively when compressing
10696 directory information for clients. This should save about 7% of
10697 the bandwidth currently used for compressed descriptors and
10698 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
10700 o Minor features (security, memory wiping):
10701 - Ensure we securely wipe keys from memory after
10702 crypto_digest_get_digest and init_curve25519_keypair_from_file
10703 have finished using them. Resolves ticket 13477.
10705 o Minor features (security, out-of-memory handling):
10706 - When handling an out-of-memory condition, allocate less memory for
10707 temporary data structures. Fixes issue 10115.
10708 - When handling an out-of-memory condition, consider more types of
10709 buffers, including those on directory connections, and zlib
10710 buffers. Resolves ticket 11792.
10713 - When identity keypair is generated for first time, log a
10714 congratulatory message that links to the new relay lifecycle
10715 document. Implements feature 10427.
10717 o Minor features (client):
10718 - Clients are now willing to send optimistic data (before they
10719 receive a 'connected' cell) to relays of any version. (Relays
10720 without support for optimistic data are no longer supported on the
10721 Tor network.) Resolves ticket 13153.
10723 o Minor features (directory authorities):
10724 - Don't list relays with a bandwidth estimate of 0 in the consensus.
10725 Implements a feature proposed during discussion of bug 13000.
10726 - In tor-gencert, report an error if the user provides the same
10727 argument more than once.
10728 - If a directory authority can't find a best consensus method in the
10729 votes that it holds, it now falls back to its favorite consensus
10730 method. Previously, it fell back to method 1. Neither of these is
10731 likely to get enough signatures, but "fall back to favorite"
10732 doesn't require us to maintain support an obsolete consensus
10733 method. Implements part of proposal 215.
10735 o Minor features (logging):
10736 - On Unix-like systems, you can now use named pipes as the target of
10737 the Log option, and other options that try to append to files.
10738 Closes ticket 12061. Patch from "carlo von lynX".
10739 - When opening a log file at startup, send it every log message that
10740 we generated between startup and opening it. Previously, log
10741 messages that were generated before opening the log file were only
10742 logged to stdout. Closes ticket 6938.
10743 - Add a TruncateLogFile option to overwrite logs instead of
10744 appending to them. Closes ticket 5583.
10746 o Minor features (portability, Solaris):
10747 - Threads are no longer disabled by default on Solaris; we believe
10748 that the versions of Solaris with broken threading support are all
10749 obsolete by now. Resolves ticket 9495.
10751 o Minor features (relay):
10752 - Re-check our address after we detect a changed IP address from
10753 getsockname(). This ensures that the controller command "GETINFO
10754 address" will report the correct value. Resolves ticket 11582.
10756 - A new AccountingRule option lets Relays set whether they'd like
10757 AccountingMax to be applied separately to inbound and outbound
10758 traffic, or applied to the sum of inbound and outbound traffic.
10759 Resolves ticket 961. Patch by "chobe".
10761 o Minor features (testing networks):
10762 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
10763 the "Exit" flag regardless of their uptime, bandwidth, or exit
10764 policy. TestingTorNetwork must be set for this option to have any
10765 effect. Previously, authorities would take up to 35 minutes to
10766 give nodes the Exit flag in a test network. Partially implements
10769 o Minor features (validation):
10770 - Check all date/time values passed to tor_timegm and
10771 parse_rfc1123_time for validity, taking leap years into account.
10772 Improves HTTP header validation. Implemented with bug 13476.
10773 - In correct_tm(), limit the range of values returned by system
10774 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
10775 This means we don't have to deal with negative or too large dates,
10776 even if a clock is wrong. Otherwise we might fail to read a file
10777 written by us which includes such a date. Fixes bug 13476.
10779 o Minor bugfixes (bridge clients):
10780 - When configured to use a bridge without an identity digest (not
10781 recommended), avoid launching an extra channel to it when
10782 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
10784 o Minor bugfixes (bridges):
10785 - When DisableNetwork is set, do not launch pluggable transport
10786 plugins, and if any are running, terminate them. Fixes bug 13213;
10787 bugfix on 0.2.3.6-alpha.
10789 o Minor bugfixes (C correctness):
10790 - Fix several instances of possible integer overflow/underflow/NaN.
10791 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
10793 - In circuit_build_times_calculate_timeout() in circuitstats.c,
10794 avoid dividing by zero in the pareto calculations. This traps
10795 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
10797 - Fix an integer overflow in format_time_interval(). Fixes bug
10798 13393; bugfix on 0.2.0.10-alpha.
10799 - Set the correct day of year value when the system's localtime(_r)
10800 or gmtime(_r) functions fail to set struct tm. Not externally
10801 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
10802 - Avoid unlikely signed integer overflow in tor_timegm on systems
10803 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
10805 o Minor bugfixes (client):
10806 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
10807 BadExit flag are not considered worthy candidates. Fixes bug
10808 13066; bugfix on 0.1.2.3-alpha.
10809 - Use the consensus schedule for downloading consensuses, and not
10810 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
10811 - Handle unsupported or malformed SOCKS5 requests properly by
10812 responding with the appropriate error message before closing the
10813 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
10815 o Minor bugfixes (client, torrc):
10816 - Stop modifying the value of our DirReqStatistics torrc option just
10817 because we're not a bridge or relay. This bug was causing Tor
10818 Browser users to write "DirReqStatistics 0" in their torrc files
10819 as if they had chosen to change the config. Fixes bug 4244; bugfix
10821 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
10822 that our options have changed every time we SIGHUP. Fixes bug
10823 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
10825 o Minor bugfixes (controller):
10826 - Return an error when the second or later arguments of the
10827 "setevents" controller command are invalid events. Previously we
10828 would return success while silently skipping invalid events. Fixes
10829 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
10831 o Minor bugfixes (directory system):
10832 - Always believe that v3 directory authorities serve extra-info
10833 documents, whether they advertise "caches-extra-info" or not.
10834 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
10835 - When running as a v3 directory authority, advertise that you serve
10836 extra-info documents so that clients who want them can find them
10837 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
10838 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
10839 Previously, directories offering BRIDGE_DIRINFO and some other
10840 flag (i.e. microdescriptors or extrainfo) would be ignored when
10841 looking for bridges. Partially fixes bug 13163; bugfix
10844 o Minor bugfixes (networking):
10845 - Check for orconns and use connection_or_close_for_error() rather
10846 than connection_mark_for_close() directly in the getsockopt()
10847 failure case of connection_handle_write_impl(). Fixes bug 11302;
10848 bugfix on 0.2.4.4-alpha.
10850 o Minor bugfixes (relay):
10851 - When generating our family list, remove spaces from around the
10852 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
10853 - If our previous bandwidth estimate was 0 bytes, allow publishing a
10854 new relay descriptor immediately. Fixes bug 13000; bugfix
10857 o Minor bugfixes (testing networks):
10858 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
10859 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
10860 - Stop using the default authorities in networks which provide both
10861 AlternateDirAuthority and AlternateBridgeAuthority. Partially
10862 fixes bug 13163; bugfix on 0.2.0.13-alpha.
10864 o Minor bugfixes (testing):
10865 - Stop spawn test failures due to a race condition between the
10866 SIGCHLD handler updating the process status, and the test reading
10867 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
10869 o Minor bugfixes (testing, Windows):
10870 - Avoid passing an extra backslash when creating a temporary
10871 directory for running the unit tests on Windows. Fixes bug 12392;
10872 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
10874 o Minor bugfixes (windows):
10875 - Remove code to special-case handling of NTE_BAD_KEYSET when
10876 acquiring windows CryptoAPI context. This error can't actually
10877 occur for the parameters we're providing. Fixes bug 10816; bugfix
10880 o Minor bugfixes (zlib):
10881 - Avoid truncating a zlib stream when trying to finalize it with an
10882 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
10885 - Allow our configure script to build correctly with autoconf 2.62
10886 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
10887 - Improve the error message from ./configure to make it clear that
10888 when asciidoc has not been found, the user will have to either add
10889 --disable-asciidoc argument or install asciidoc. Resolves
10892 o Code simplification and refactoring:
10893 - Change the entry_is_live() function to take named bitfield
10894 elements instead of an unnamed list of booleans. Closes
10896 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
10897 Resolves ticket 12205.
10898 - Use calloc and reallocarray functions instead of multiply-
10899 then-malloc. This makes it less likely for us to fall victim to an
10900 integer overflow attack when allocating. Resolves ticket 12855.
10901 - Use the standard macro name SIZE_MAX, instead of our
10903 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
10904 functions which take them as arguments. Replace 0 with NO_DIRINFO
10905 in a function call for clarity. Seeks to prevent future issues
10907 - Avoid 4 null pointer errors under clang static analysis by using
10908 tor_assert() to prove that the pointers aren't null. Fixes
10910 - Rework the API of policies_parse_exit_policy() to use a bitmask to
10911 represent parsing options, instead of a confusing mess of
10912 booleans. Resolves ticket 8197.
10913 - Introduce a helper function to parse ExitPolicy in
10914 or_options_t structure.
10917 - Add a doc/TUNING document with tips for handling large numbers of
10918 TCP connections when running busy Tor relay. Update the warning
10919 message to point to this file when running out of sockets
10920 operating system is allowing to use simultaneously. Resolves
10923 o Removed features:
10924 - We no longer remind the user about configuration options that have
10925 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
10926 - Remove our old, non-weighted bandwidth-based node selection code.
10927 Previously, we used it as a fallback when we couldn't perform
10928 weighted bandwidth-based node selection. But that would only
10929 happen in the cases where we had no consensus, or when we had a
10930 consensus generated by buggy or ancient directory authorities. In
10931 either case, it's better to use the more modern, better maintained
10932 algorithm, with reasonable defaults for the weights. Closes
10934 - Remove the --disable-curve25519 configure option. Relays and
10935 clients now are required to support curve25519 and the
10937 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
10938 used to be deprecated synonyms for "StrictNodes", are now marked
10939 obsolete. Resolves ticket 12226.
10940 - Clients don't understand the BadDirectory flag in the consensus
10941 anymore, and ignore it.
10944 - Refactor the function that chooses guard nodes so that it can more
10945 easily be tested; write some tests for it.
10946 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
10947 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
10948 - Create unit tests for format_time_interval(). With bug 13393.
10949 - Add unit tests for tor_timegm signed overflow, tor_timegm and
10950 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
10951 tests (visible) fixes in bug 13476.
10952 - Add a "coverage-html" make target to generate HTML-visualized
10953 coverage results when building with --enable-coverage. (Requires
10954 lcov.) Patch from Kevin Murray.
10955 - Enable the backtrace handler (where supported) when running the
10957 - Revise all unit tests that used the legacy test_* macros to
10958 instead use the recommended tt_* macros. This patch was generated
10959 with coccinelle, to avoid manual errors. Closes ticket 13119.
10961 o Distribution (systemd):
10962 - systemd unit file: only allow tor to write to /var/lib/tor and
10963 /var/log/tor. The rest of the filesystem is accessible for reading
10964 only. Patch by intrigeri; resolves ticket 12751.
10965 - systemd unit file: ensure that the process and all its children
10966 can never gain new privileges. Patch by intrigeri; resolves
10968 - systemd unit file: set up /var/run/tor as writable for the Tor
10969 service. Patch by intrigeri; resolves ticket 13196.
10971 o Removed features (directory authorities):
10972 - Remove code that prevented authorities from listing Tor relays
10973 affected by CVE-2011-2769 as guards. These relays are already
10974 rejected altogether due to the minimum version requirement of
10975 0.2.3.16-alpha. Closes ticket 13152.
10976 - The "AuthDirRejectUnlisted" option no longer has any effect, as
10977 the fingerprints file (approved-routers) has been deprecated.
10978 - Directory authorities do not support being Naming dirauths anymore.
10979 The "NamingAuthoritativeDir" config option is now obsolete.
10980 - Directory authorities do not support giving out the BadDirectory
10982 - Directory authorities no longer advertise or support consensus
10983 methods 1 through 12 inclusive. These consensus methods were
10984 obsolete and/or insecure: maintaining the ability to support them
10985 served no good purpose. Implements part of proposal 215; closes
10988 o Testing (test-network.sh):
10989 - Stop using "echo -n", as some shells' built-in echo doesn't
10990 support "-n". Instead, use "/bin/echo -n". Partially fixes
10992 - Stop an apparent test-network hang when used with make -j2. Fixes
10994 - Add a --delay option to test-network.sh, which configures the
10995 delay before the chutney network tests for data transmission.
10996 Partially implements ticket 13161.
10999 Changes in version 0.2.5.10 - 2014-10-24
11000 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
11002 It adds several new security features, including improved
11003 denial-of-service resistance for relays, new compiler hardening
11004 options, and a system-call sandbox for hardened installations on Linux
11005 (requires seccomp2). The controller protocol has several new features,
11006 resolving IPv6 addresses should work better than before, and relays
11007 should be a little more CPU-efficient. We've added support for more
11008 OpenBSD and FreeBSD transparent proxy types. We've improved the build
11009 system and testing infrastructure to allow unit testing of more parts
11010 of the Tor codebase. Finally, we've addressed several nagging pluggable
11011 transport usability issues, and included numerous other small bugfixes
11012 and features mentioned below.
11014 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
11015 have accumulated many known flaws; everyone should upgrade.
11017 o Deprecated versions:
11018 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
11019 attention for some while.
11022 Changes in version 0.2.5.9-rc - 2014-10-20
11023 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
11024 series. It disables SSL3 in response to the recent "POODLE" attack
11025 (even though POODLE does not affect Tor). It also works around a crash
11026 bug caused by some operating systems' response to the "POODLE" attack
11027 (which does affect Tor). It also contains a few miscellaneous fixes.
11029 o Major security fixes:
11030 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
11031 today support TLS 1.0 or later, so we can safely turn off support
11032 for this old (and insecure) protocol. Fixes bug 13426.
11034 o Major bugfixes (openssl bug workaround):
11035 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
11036 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
11037 13471. This is a workaround for an OpenSSL bug.
11040 - Disable the sandbox name resolver cache when running tor-resolve:
11041 tor-resolve doesn't use the sandbox code, and turning it on was
11042 breaking attempts to do tor-resolve on a non-default server on
11043 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
11045 o Compilation fixes:
11046 - Build and run correctly on systems like OpenBSD-current that have
11047 patched OpenSSL to remove get_cipher_by_char and/or its
11048 implementations. Fixes issue 13325.
11050 o Downgraded warnings:
11051 - Downgrade the severity of the 'unexpected sendme cell from client'
11052 from 'warn' to 'protocol warning'. Closes ticket 8093.
11055 Changes in version 0.2.4.25 - 2014-10-20
11056 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
11057 (even though POODLE does not affect Tor). It also works around a crash
11058 bug caused by some operating systems' response to the "POODLE" attack
11059 (which does affect Tor).
11061 o Major security fixes (also in 0.2.5.9-rc):
11062 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
11063 today support TLS 1.0 or later, so we can safely turn off support
11064 for this old (and insecure) protocol. Fixes bug 13426.
11066 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
11067 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
11068 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
11069 13471. This is a workaround for an OpenSSL bug.
11072 Changes in version 0.2.5.8-rc - 2014-09-22
11073 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
11074 series. It fixes a bug that affects consistency and speed when
11075 connecting to hidden services, and it updates the location of one of
11076 the directory authorities.
11079 - Clients now send the correct address for their chosen rendezvous
11080 point when trying to access a hidden service. They used to send
11081 the wrong address, which would still work some of the time because
11082 they also sent the identity digest of the rendezvous point, and if
11083 the hidden service happened to try connecting to the rendezvous
11084 point from a relay that already had a connection open to it,
11085 the relay would reuse that connection. Now connections to hidden
11086 services should be more robust and faster. Also, this bug meant
11087 that clients were leaking to the hidden service whether they were
11088 on a little-endian (common) or big-endian (rare) system, which for
11089 some users might have reduced their anonymity. Fixes bug 13151;
11090 bugfix on 0.2.1.5-alpha.
11092 o Directory authority changes:
11093 - Change IP address for gabelmoo (v3 directory authority).
11096 Changes in version 0.2.4.24 - 2014-09-22
11097 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
11098 connecting to hidden services, and it updates the location of one of
11099 the directory authorities.
11102 - Clients now send the correct address for their chosen rendezvous
11103 point when trying to access a hidden service. They used to send
11104 the wrong address, which would still work some of the time because
11105 they also sent the identity digest of the rendezvous point, and if
11106 the hidden service happened to try connecting to the rendezvous
11107 point from a relay that already had a connection open to it,
11108 the relay would reuse that connection. Now connections to hidden
11109 services should be more robust and faster. Also, this bug meant
11110 that clients were leaking to the hidden service whether they were
11111 on a little-endian (common) or big-endian (rare) system, which for
11112 some users might have reduced their anonymity. Fixes bug 13151;
11113 bugfix on 0.2.1.5-alpha.
11115 o Directory authority changes:
11116 - Change IP address for gabelmoo (v3 directory authority).
11118 o Minor features (geoip):
11119 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
11123 Changes in version 0.2.5.7-rc - 2014-09-11
11124 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
11125 release series, and some long-standing bugs related to ORPort reachability
11126 testing and failure to send CREATE cells. It is the first release
11127 candidate for the Tor 0.2.5.x series.
11129 o Major bugfixes (client, startup):
11130 - Start making circuits as soon as DisabledNetwork is turned off.
11131 When Tor started with DisabledNetwork set, it would correctly
11132 conclude that it shouldn't build circuits, but it would mistakenly
11133 cache this conclusion, and continue believing it even when
11134 DisableNetwork is set to 0. Fixes the bug introduced by the fix
11135 for bug 11200; bugfix on 0.2.5.4-alpha.
11136 - Resume expanding abbreviations for command-line options. The fix
11137 for bug 4647 accidentally removed our hack from bug 586 that
11138 rewrote HashedControlPassword to __HashedControlSessionPassword
11139 when it appears on the commandline (which allowed the user to set
11140 her own HashedControlPassword in the torrc file while the
11141 controller generates a fresh session password for each run). Fixes
11142 bug 12948; bugfix on 0.2.5.1-alpha.
11143 - Warn about attempts to run hidden services and relays in the same
11144 process: that's probably not a good idea. Closes ticket 12908.
11146 o Major bugfixes (relay):
11147 - Avoid queuing or sending destroy cells for circuit ID zero when we
11148 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
11149 Found and fixed by "cypherpunks".
11150 - Fix ORPort reachability detection on relays running behind a
11151 proxy, by correctly updating the "local" mark on the controlling
11152 channel when changing the address of an or_connection_t after the
11153 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
11155 o Minor features (bridge):
11156 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
11157 cookie file for the ExtORPort g+r by default.
11159 o Minor features (geoip):
11160 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
11163 o Minor bugfixes (logging):
11164 - Reduce the log severity of the "Pluggable transport proxy does not
11165 provide any needed transports and will not be launched." message,
11166 since Tor Browser includes several ClientTransportPlugin lines in
11167 its torrc-defaults file, leading every Tor Browser user who looks
11168 at her logs to see these notices and wonder if they're dangerous.
11169 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
11170 - Downgrade "Unexpected onionskin length after decryption" warning
11171 to a protocol-warn, since there's nothing relay operators can do
11172 about a client that sends them a malformed create cell. Resolves
11173 bug 12996; bugfix on 0.0.6rc1.
11174 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
11175 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
11176 - When logging information about an EXTEND2 or EXTENDED2 cell, log
11177 their names correctly. Fixes part of bug 12700; bugfix
11179 - When logging information about a relay cell whose command we don't
11180 recognize, log its command as an integer. Fixes part of bug 12700;
11181 bugfix on 0.2.1.10-alpha.
11182 - Escape all strings from the directory connection before logging
11183 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
11185 o Minor bugfixes (controller):
11186 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
11187 bug 12864; bugfix on 0.2.5.1-alpha.
11188 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
11189 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
11192 o Minor bugfixes (compilation):
11193 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
11194 bugfix on 0.2.5.5-alpha.
11195 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
11196 0.2.5.1-alpha. Patch from "NewEraCracker".
11197 - In routerlist_assert_ok(), don't take the address of a
11198 routerinfo's cache_info member unless that routerinfo is non-NULL.
11199 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
11200 - Fix a large number of false positive warnings from the clang
11201 analyzer static analysis tool. This should make real warnings
11202 easier for clang analyzer to find. Patch from "teor". Closes
11205 o Distribution (systemd):
11206 - Verify configuration file via ExecStartPre in the systemd unit
11207 file. Patch from intrigeri; resolves ticket 12730.
11208 - Explicitly disable RunAsDaemon in the systemd unit file. Our
11209 current systemd unit uses "Type = simple", so systemd does not
11210 expect tor to fork. If the user has "RunAsDaemon 1" in their
11211 torrc, then things won't work as expected. This is e.g. the case
11212 on Debian (and derivatives), since there we pass "--defaults-torrc
11213 /usr/share/tor/tor-service-defaults-torrc" (that contains
11214 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
11218 - Adjust the URLs in the README to refer to the new locations of
11219 several documents on the website. Fixes bug 12830. Patch from
11221 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
11225 Changes in version 0.2.5.6-alpha - 2014-07-28
11226 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
11227 risk from guard rotation, and fixes a variety of other issues to get
11228 us closer to a release candidate.
11230 o Major features (also in 0.2.4.23):
11231 - Make the number of entry guards configurable via a new
11232 NumEntryGuards consensus parameter, and the number of directory
11233 guards configurable via a new NumDirectoryGuards consensus
11234 parameter. Implements ticket 12688.
11236 o Major bugfixes (also in 0.2.4.23):
11237 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
11238 implementation that caused incorrect results on 32-bit
11239 implementations when certain malformed inputs were used along with
11240 a small class of private ntor keys. This bug does not currently
11241 appear to allow an attacker to learn private keys or impersonate a
11242 Tor server, but it could provide a means to distinguish 32-bit Tor
11243 implementations from 64-bit Tor implementations. Fixes bug 12694;
11244 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
11248 - Perform circuit cleanup operations even when circuit
11249 construction operations are disabled (because the network is
11250 disabled, or because there isn't enough directory information).
11251 Previously, when we were not building predictive circuits, we
11252 were not closing expired circuits either. Fixes bug 8387; bugfix on
11253 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
11254 became more strict about when we have "enough directory information
11255 to build circuits".
11258 - Authorities now assign the Guard flag to the fastest 25% of the
11259 network (it used to be the fastest 50%). Also raise the consensus
11260 weight that guarantees the Guard flag from 250 to 2000. For the
11261 current network, this results in about 1100 guards, down from 2500.
11262 This step paves the way for moving the number of entry guards
11263 down to 1 (proposal 236) while still providing reasonable expected
11264 performance for most users. Implements ticket 12690.
11265 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
11267 - Slightly enhance the diagnostic message for bug 12184.
11269 o Minor bugfixes (also in 0.2.4.23):
11270 - Warn and drop the circuit if we receive an inbound 'relay early'
11271 cell. Those used to be normal to receive on hidden service circuits
11272 due to bug 1038, but the buggy Tor versions are long gone from
11273 the network so we can afford to resume watching for them. Resolves
11274 the rest of bug 1038; bugfix on 0.2.1.19.
11275 - Correct a confusing error message when trying to extend a circuit
11276 via the control protocol but we don't know a descriptor or
11277 microdescriptor for one of the specified relays. Fixes bug 12718;
11278 bugfix on 0.2.3.1-alpha.
11281 - Fix compilation when building with bufferevents enabled. (This
11282 configuration is still not expected to work, however.)
11283 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
11284 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
11286 - Compile correctly with builds and forks of OpenSSL (such as
11287 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
11288 0.2.1.1-alpha. Patch from "dhill".
11291 Changes in version 0.2.4.23 - 2014-07-28
11292 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
11293 guard rotation, and also backports several important fixes from the
11294 Tor 0.2.5 alpha release series.
11297 - Clients now look at the "usecreatefast" consensus parameter to
11298 decide whether to use CREATE_FAST or CREATE cells for the first hop
11299 of their circuit. This approach can improve security on connections
11300 where Tor's circuit handshake is stronger than the available TLS
11301 connection security levels, but the tradeoff is more computational
11302 load on guard relays. Implements proposal 221. Resolves ticket 9386.
11303 - Make the number of entry guards configurable via a new
11304 NumEntryGuards consensus parameter, and the number of directory
11305 guards configurable via a new NumDirectoryGuards consensus
11306 parameter. Implements ticket 12688.
11309 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
11310 implementation that caused incorrect results on 32-bit
11311 implementations when certain malformed inputs were used along with
11312 a small class of private ntor keys. This bug does not currently
11313 appear to allow an attacker to learn private keys or impersonate a
11314 Tor server, but it could provide a means to distinguish 32-bit Tor
11315 implementations from 64-bit Tor implementations. Fixes bug 12694;
11316 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
11320 - Warn and drop the circuit if we receive an inbound 'relay early'
11321 cell. Those used to be normal to receive on hidden service circuits
11322 due to bug 1038, but the buggy Tor versions are long gone from
11323 the network so we can afford to resume watching for them. Resolves
11324 the rest of bug 1038; bugfix on 0.2.1.19.
11325 - Correct a confusing error message when trying to extend a circuit
11326 via the control protocol but we don't know a descriptor or
11327 microdescriptor for one of the specified relays. Fixes bug 12718;
11328 bugfix on 0.2.3.1-alpha.
11329 - Avoid an illegal read from stack when initializing the TLS
11330 module using a version of OpenSSL without all of the ciphers
11331 used by the v2 link handshake. Fixes bug 12227; bugfix on
11332 0.2.4.8-alpha. Found by "starlight".
11335 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
11339 Changes in version 0.2.5.5-alpha - 2014-06-18
11340 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
11341 0.2.5.x release series, including a couple of DoS issues, some
11342 performance regressions, a large number of bugs affecting the Linux
11343 seccomp2 sandbox code, and various other bugfixes. It also adds
11344 diagnostic bugfixes for a few tricky issues that we're trying to
11347 o Major features (security, traffic analysis resistance):
11348 - Several major improvements to the algorithm used to decide when to
11349 close TLS connections. Previous versions of Tor closed connections
11350 at a fixed interval after the last time a non-padding cell was
11351 sent over the connection, regardless of the target of the
11352 connection. Now, we randomize the intervals by adding up to 50% of
11353 their base value, we measure the length of time since connection
11354 last had at least one circuit, and we allow connections to known
11355 ORs to remain open a little longer (15 minutes instead of 3
11356 minutes minimum). These changes should improve Tor's resistance
11357 against some kinds of traffic analysis, and lower some overhead
11358 from needlessly closed connections. Fixes ticket 6799.
11359 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
11361 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
11362 - Fix a memory leak that could occur if a microdescriptor parse
11363 fails during the tokenizing step. This bug could enable a memory
11364 exhaustion attack by directory servers. Fixes bug 11649; bugfix
11367 o Major bugfixes (security, directory authorities):
11368 - Directory authorities now include a digest of each relay's
11369 identity key as a part of its microdescriptor.
11371 This is a workaround for bug 11743 (reported by "cypherpunks"),
11372 where Tor clients do not support receiving multiple
11373 microdescriptors with the same SHA256 digest in the same
11374 consensus. When clients receive a consensus like this, they only
11375 use one of the relays. Without this fix, a hostile relay could
11376 selectively disable some client use of target relays by
11377 constructing a router descriptor with a different identity and the
11378 same microdescriptor parameters and getting the authorities to
11379 list it in a microdescriptor consensus. This fix prevents an
11380 attacker from causing a microdescriptor collision, because the
11381 router's identity is not forgeable.
11383 o Major bugfixes (relay):
11384 - Use a direct dirport connection when uploading non-anonymous
11385 descriptors to the directory authorities. Previously, relays would
11386 incorrectly use tunnel connections under a fairly wide variety of
11387 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
11388 - When a circuit accidentally has the same circuit ID for its
11389 forward and reverse direction, correctly detect the direction of
11390 cells using that circuit. Previously, this bug made roughly one
11391 circuit in a million non-functional. Fixes bug 12195; this is a
11392 bugfix on every version of Tor.
11394 o Major bugfixes (client, pluggable transports):
11395 - When managing pluggable transports, use OS notification facilities
11396 to learn if they have crashed, and don't attempt to kill any
11397 process that has already exited. Fixes bug 8746; bugfix
11400 o Minor features (diagnostic):
11401 - When logging a warning because of bug 7164, additionally check the
11402 hash table for consistency (as proposed on ticket 11737). This may
11403 help diagnose bug 7164.
11404 - When we log a heartbeat, log how many one-hop circuits we have
11405 that are at least 30 minutes old, and log status information about
11406 a few of them. This is an attempt to track down bug 8387.
11407 - When encountering an unexpected CR while writing text to a file on
11408 Windows, log the name of the file. Should help diagnosing
11410 - Give more specific warnings when a client notices that an onion
11411 handshake has failed. Fixes ticket 9635.
11412 - Add significant new logging code to attempt to diagnose bug 12184,
11413 where relays seem to run out of available circuit IDs.
11414 - Improve the diagnostic log message for bug 8387 even further to
11415 try to improve our odds of figuring out why one-hop directory
11416 circuits sometimes do not get closed.
11418 o Minor features (security, memory management):
11419 - Memory allocation tricks (mempools and buffer freelists) are now
11420 disabled by default. You can turn them back on with
11421 --enable-mempools and --enable-buf-freelists respectively. We're
11422 disabling these features because malloc performance is good enough
11423 on most platforms, and a similar feature in OpenSSL exacerbated
11424 exploitation of the Heartbleed attack. Resolves ticket 11476.
11426 o Minor features (security):
11427 - Apply the secure SipHash-2-4 function to the hash table mapping
11428 circuit IDs and channels to circuits. We missed this one when we
11429 were converting all the other hash functions to use SipHash back
11430 in 0.2.5.3-alpha. Resolves ticket 11750.
11432 o Minor features (build):
11433 - The configure script has a --disable-seccomp option to turn off
11434 support for libseccomp on systems that have it, in case it (or
11435 Tor's use of it) is broken. Resolves ticket 11628.
11437 o Minor features (other):
11438 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
11441 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
11442 - When running a hidden service, do not allow TunneledDirConns 0;
11443 this will keep the hidden service from running, and also
11444 make it publish its descriptors directly over HTTP. Fixes bug 10849;
11445 bugfix on 0.2.1.1-alpha.
11447 o Minor bugfixes (performance):
11448 - Avoid a bug where every successful connection made us recompute
11449 the flag telling us whether we have sufficient information to
11450 build circuits. Previously, we would forget our cached value
11451 whenever we successfully opened a channel (or marked a router as
11452 running or not running for any other reason), regardless of
11453 whether we had previously believed the router to be running. This
11454 forced us to run an expensive update operation far too often.
11455 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
11456 - Avoid using tor_memeq() for checking relay cell integrity. This
11457 removes a possible performance bottleneck. Fixes part of bug
11458 12169; bugfix on 0.2.1.31.
11460 o Minor bugfixes (compilation):
11461 - Fix compilation of test_status.c when building with MVSC. Bugfix
11462 on 0.2.5.4-alpha. Patch from Gisle Vanem.
11463 - Resolve GCC complaints on OpenBSD about discarding constness in
11464 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
11465 on 0.1.1.23. Patch from Dana Koch.
11466 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
11467 treatment of long and time_t as comparable types. Fixes part of
11468 bug 11633. Patch from Dana Koch.
11469 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
11470 11623; bugfix on 0.2.5.3-alpha.
11471 - When deciding whether to build the 64-bit curve25519
11472 implementation, detect platforms where we can compile 128-bit
11473 arithmetic but cannot link it. Fixes bug 11729; bugfix on
11474 0.2.4.8-alpha. Patch from "conradev".
11475 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
11476 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
11477 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
11480 o Minor bugfixes (Directory server):
11481 - When sending a compressed set of descriptors or microdescriptors,
11482 make sure to finalize the zlib stream. Previously, we would write
11483 all the compressed data, but if the last descriptor we wanted to
11484 send was missing or too old, we would not mark the stream as
11485 finished. This caused problems for decompression tools. Fixes bug
11486 11648; bugfix on 0.1.1.23.
11488 o Minor bugfixes (Linux seccomp sandbox):
11489 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
11490 11622; bugfix on 0.2.5.1-alpha.
11491 - Avoid crashing when re-opening listener ports with the seccomp
11492 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
11493 - Avoid crashing with the seccomp sandbox enabled along with
11494 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
11495 - When we receive a SIGHUP with the sandbox enabled, correctly
11496 support rotating our log files. Fixes bug 12032; bugfix
11498 - Avoid crash when running with sandboxing enabled and
11499 DirReqStatistics not disabled. Fixes bug 12035; bugfix
11501 - Fix a "BUG" warning when trying to write bridge-stats files with
11502 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
11504 - Prevent the sandbox from crashing on startup when run with the
11505 --enable-expensive-hardening configuration option. Fixes bug
11506 11477; bugfix on 0.2.5.4-alpha.
11507 - When running with DirPortFrontPage and sandboxing both enabled,
11508 reload the DirPortFrontPage correctly when restarting. Fixes bug
11509 12028; bugfix on 0.2.5.1-alpha.
11510 - Don't try to enable the sandbox when using the Tor binary to check
11511 its configuration, hash a passphrase, or so on. Doing so was
11512 crashing on startup for some users. Fixes bug 11609; bugfix
11514 - Avoid warnings when running with sandboxing and node statistics
11515 enabled at the same time. Fixes part of 12064; bugfix on
11516 0.2.5.1-alpha. Patch from Michael Wolf.
11517 - Avoid warnings when running with sandboxing enabled at the same
11518 time as cookie authentication, hidden services, or directory
11519 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
11520 - Do not allow options that require calls to exec to be enabled
11521 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
11522 bug 12043; bugfix on 0.2.5.1-alpha.
11523 - Handle failures in getpwnam()/getpwuid() when running with the
11524 User option set and the Linux syscall sandbox enabled. Fixes bug
11525 11946; bugfix on 0.2.5.1-alpha.
11526 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
11527 to avoid calling getaddrinfo() after installing the sandbox
11528 filters. Previously, it preloaded a cache with the IPv4 address
11529 for our hostname, and nothing else. Now, it loads the cache with
11530 every address that it used to initialize the Tor process. Fixes
11531 bug 11970; bugfix on 0.2.5.1-alpha.
11533 o Minor bugfixes (pluggable transports):
11534 - Enable the ExtORPortCookieAuthFile option, to allow changing the
11535 default location of the authentication token for the extended OR
11536 Port as used by sever-side pluggable transports. We had
11537 implemented this option before, but the code to make it settable
11538 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
11539 - Avoid another 60-second delay when starting Tor in a pluggable-
11540 transport-using configuration when we already have cached
11541 descriptors for our bridges. Fixes bug 11965; bugfix
11544 o Minor bugfixes (client):
11545 - Avoid "Tried to open a socket with DisableNetwork set" warnings
11546 when starting a client with bridges configured and DisableNetwork
11547 set. (Tor launcher starts Tor with DisableNetwork set the first
11548 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
11550 o Minor bugfixes (testing):
11551 - The Python parts of the test scripts now work on Python 3 as well
11552 as Python 2, so systems where '/usr/bin/python' is Python 3 will
11553 no longer have the tests break. Fixes bug 11608; bugfix
11555 - When looking for versions of python that we could run the tests
11556 with, check for "python2.7" and "python3.3"; previously we were
11557 only looking for "python", "python2", and "python3". Patch from
11558 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
11559 - Fix all valgrind warnings produced by the unit tests. There were
11560 over a thousand memory leak warnings previously, mostly produced
11561 by forgetting to free things in the unit test code. Fixes bug
11562 11618, bugfixes on many versions of Tor.
11564 o Minor bugfixes (tor-fw-helper):
11565 - Give a correct log message when tor-fw-helper fails to launch.
11566 (Previously, we would say something like "tor-fw-helper sent us a
11567 string we could not parse".) Fixes bug 9781; bugfix
11570 o Minor bugfixes (relay, threading):
11571 - Check return code on spawn_func() in cpuworker code, so that we
11572 don't think we've spawned a nonworking cpuworker and write junk to
11573 it forever. Fix related to bug 4345; bugfix on all released Tor
11574 versions. Found by "skruffy".
11575 - Use a pthread_attr to make sure that spawn_func() cannot return an
11576 error while at the same time launching a thread. Fix related to
11577 bug 4345; bugfix on all released Tor versions. Reported
11580 o Minor bugfixes (relay, oom prevention):
11581 - Correctly detect the total available system memory. We tried to do
11582 this in 0.2.5.4-alpha, but the code was set up to always return an
11583 error value, even on success. Fixes bug 11805; bugfix
11586 o Minor bugfixes (relay, other):
11587 - We now drop CREATE cells for already-existent circuit IDs and for
11588 zero-valued circuit IDs, regardless of other factors that might
11589 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
11591 - Avoid an illegal read from stack when initializing the TLS module
11592 using a version of OpenSSL without all of the ciphers used by the
11593 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
11595 - When rejecting DATA cells for stream_id zero, still count them
11596 against the circuit's deliver window so that we don't fail to send
11597 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
11599 o Minor bugfixes (logging):
11600 - Fix a misformatted log message about delayed directory fetches.
11601 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
11602 - Squelch a spurious LD_BUG message "No origin circuit for
11603 successful SOCKS stream" in certain hidden service failure cases;
11607 - Include a tor.service file in contrib/dist for use with systemd.
11608 Some distributions will be able to use this file unmodified;
11609 others will need to tweak it, or write their own. Patch from Jamie
11610 Nguyen; resolves ticket 8368.
11613 - Clean up several option names in the manpage to match their real
11614 names, add the missing documentation for a couple of testing and
11615 directory authority options, remove the documentation for a
11616 V2-directory fetching option that no longer exists. Resolves
11618 - Correct the documentation so that it lists the correct directory
11619 for the stats files. (They are in a subdirectory called "stats",
11621 - In the manpage, move more authority-only options into the
11622 directory authority section so that operators of regular directory
11623 caches don't get confused.
11626 - The contrib directory has been sorted and tidied. Before, it was
11627 an unsorted dumping ground for useful and not-so-useful things.
11628 Now, it is divided based on functionality, and the items which
11629 seemed to be nonfunctional or useless have been removed. Resolves
11630 ticket 8966; based on patches from "rl1987".
11633 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
11634 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
11635 - The TunnelDirConns and PreferTunnelledDirConns options no longer
11636 exist; tunneled directory connections have been available since
11637 0.1.2.5-alpha, and turning them off is not a good idea. This is a
11638 brute-force fix for 10849, where "TunnelDirConns 0" would break
11642 Changes in version 0.2.4.22 - 2014-05-16
11643 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
11644 alpha release series. These include blocking all authority signing
11645 keys that may have been affected by the OpenSSL "heartbleed" bug,
11646 choosing a far more secure set of TLS ciphersuites by default, closing
11647 a couple of memory leaks that could be used to run a target relay out
11648 of RAM, and several others.
11650 o Major features (security, backport from 0.2.5.4-alpha):
11651 - Block authority signing keys that were used on authorities
11652 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
11653 don't have any evidence that these keys _were_ compromised; we're
11654 doing this to be prudent.) Resolves ticket 11464.
11656 o Major bugfixes (security, OOM):
11657 - Fix a memory leak that could occur if a microdescriptor parse
11658 fails during the tokenizing step. This bug could enable a memory
11659 exhaustion attack by directory servers. Fixes bug 11649; bugfix
11662 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
11663 - The relay ciphersuite list is now generated automatically based on
11664 uniform criteria, and includes all OpenSSL ciphersuites with
11665 acceptable strength and forward secrecy. Previously, we had left
11666 some perfectly fine ciphersuites unsupported due to omission or
11667 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
11668 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
11669 - Relays now trust themselves to have a better view than clients of
11670 which TLS ciphersuites are better than others. (Thanks to bug
11671 11513, the relay list is now well-considered, whereas the client
11672 list has been chosen mainly for anti-fingerprinting purposes.)
11673 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
11674 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
11675 AES128. Resolves ticket 11528.
11676 - Clients now try to advertise the same list of ciphersuites as
11677 Firefox 28. This change enables selection of (fast) GCM
11678 ciphersuites, disables some strange old ciphers, and stops
11679 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
11680 Resolves ticket 11438.
11682 o Minor bugfixes (configuration, security):
11683 - When running a hidden service, do not allow TunneledDirConns 0:
11684 trying to set that option together with a hidden service would
11685 otherwise prevent the hidden service from running, and also make
11686 it publish its descriptors directly over HTTP. Fixes bug 10849;
11687 bugfix on 0.2.1.1-alpha.
11689 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
11690 - Avoid sending a garbage value to the controller when a circuit is
11691 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
11693 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
11694 - Stop leaking memory when we successfully resolve a PTR record.
11695 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
11697 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
11698 - Avoid 60-second delays in the bootstrapping process when Tor is
11699 launching for a second time while using bridges. Fixes bug 9229;
11700 bugfix on 0.2.0.3-alpha.
11702 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
11703 - Give the correct URL in the warning message when trying to run a
11704 relay on an ancient version of Windows. Fixes bug 9393.
11706 o Minor bugfixes (compilation):
11707 - Fix a compilation error when compiling with --disable-curve25519.
11708 Fixes bug 9700; bugfix on 0.2.4.17-rc.
11711 - Downgrade the warning severity for the the "md was still
11712 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
11713 for trying to diagnose this bug, and the current warning in
11714 earlier versions of tor achieves nothing useful. Addresses warning
11717 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
11718 - When we run out of usable circuit IDs on a channel, log only one
11719 warning for the whole channel, and describe how many circuits
11720 there were on the channel. Fixes part of ticket 11553.
11722 o Minor features (security, backport from 0.2.5.4-alpha):
11723 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
11724 leave the default at 8GBytes), to better support Raspberry Pi
11725 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
11727 o Documentation (backport from 0.2.5.4-alpha):
11728 - Correctly document that we search for a system torrc file before
11729 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
11733 Changes in version 0.2.5.4-alpha - 2014-04-25
11734 Tor 0.2.5.4-alpha includes several security and performance
11735 improvements for clients and relays, including blacklisting authority
11736 signing keys that were used while susceptible to the OpenSSL
11737 "heartbleed" bug, fixing two expensive functions on busy relays,
11738 improved TLS ciphersuite preference lists, support for run-time
11739 hardening on compilers that support AddressSanitizer, and more work on
11740 the Linux sandbox code.
11742 There are also several usability fixes for clients (especially clients
11743 that use bridges), two new TransPort protocols supported (one on
11744 OpenBSD, one on FreeBSD), and various other bugfixes.
11746 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
11747 have accumulated many known flaws; everyone should upgrade.
11749 o Major features (security):
11750 - If you don't specify MaxMemInQueues yourself, Tor now tries to
11751 pick a good value based on your total system memory. Previously,
11752 the default was always 8 GB. You can still override the default by
11753 setting MaxMemInQueues yourself. Resolves ticket 11396.
11754 - Block authority signing keys that were used on authorities
11755 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
11756 don't have any evidence that these keys _were_ compromised; we're
11757 doing this to be prudent.) Resolves ticket 11464.
11759 o Major features (relay performance):
11760 - Speed up server-side lookups of rendezvous and introduction point
11761 circuits by using hashtables instead of linear searches. These
11762 functions previously accounted between 3 and 7% of CPU usage on
11763 some busy relays. Resolves ticket 9841.
11764 - Avoid wasting CPU when extending a circuit over a channel that is
11765 nearly out of circuit IDs. Previously, we would do a linear scan
11766 over possible circuit IDs before finding one or deciding that we
11767 had exhausted our possibilities. Now, we try at most 64 random
11768 circuit IDs before deciding that we probably won't succeed. Fixes
11769 a possible root cause of ticket 11553.
11771 o Major features (seccomp2 sandbox, Linux only):
11772 - The seccomp2 sandbox can now run a test network for multiple hours
11773 without crashing. The sandbox is still experimental, and more bugs
11774 will probably turn up. To try it, enable "Sandbox 1" on a Linux
11775 host. Resolves ticket 11351.
11776 - Strengthen sandbox code: the sandbox can now test the arguments
11777 for rename(), and blocks _sysctl() entirely. Resolves another part
11779 - When the sandbox blocks a system call, it now tries to log a stack
11780 trace before exiting. Resolves ticket 11465.
11782 o Major bugfixes (TLS cipher selection):
11783 - The relay ciphersuite list is now generated automatically based on
11784 uniform criteria, and includes all OpenSSL ciphersuites with
11785 acceptable strength and forward secrecy. Previously, we had left
11786 some perfectly fine ciphersuites unsupported due to omission or
11787 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
11788 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
11789 - Relays now trust themselves to have a better view than clients of
11790 which TLS ciphersuites are better than others. (Thanks to bug
11791 11513, the relay list is now well-considered, whereas the client
11792 list has been chosen mainly for anti-fingerprinting purposes.)
11793 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
11794 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
11795 AES128. Resolves ticket 11528.
11796 - Clients now try to advertise the same list of ciphersuites as
11797 Firefox 28. This change enables selection of (fast) GCM
11798 ciphersuites, disables some strange old ciphers, and stops
11799 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
11800 Resolves ticket 11438.
11802 o Major bugfixes (bridge client):
11803 - Avoid 60-second delays in the bootstrapping process when Tor is
11804 launching for a second time while using bridges. Fixes bug 9229;
11805 bugfix on 0.2.0.3-alpha.
11807 o Minor features (transparent proxy, *BSD):
11808 - Support FreeBSD's ipfw firewall interface for TransPort ports on
11809 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
11810 10267; patch from "yurivict".
11811 - Support OpenBSD's divert-to rules with the pf firewall for
11812 transparent proxy ports. To enable it, set "TransProxyType
11813 pf-divert". This allows Tor to run a TransPort transparent proxy
11814 port on OpenBSD 4.4 or later without root privileges. See the
11815 pf.conf(5) manual page for information on configuring pf to use
11816 divert-to rules. Closes ticket 10896; patch from Dana Koch.
11818 o Minor features (security):
11819 - New --enable-expensive-hardening option to enable security
11820 hardening options that consume nontrivial amounts of CPU and
11821 memory. Right now, this includes AddressSanitizer and UbSan, which
11822 are supported in newer versions of GCC and Clang. Closes ticket
11825 o Minor features (log verbosity):
11826 - Demote the message that we give when a flushing connection times
11827 out for too long from NOTICE to INFO. It was usually meaningless.
11828 Resolves ticket 5286.
11829 - Don't log so many notice-level bootstrapping messages at startup
11830 about downloading descriptors. Previously, we'd log a notice
11831 whenever we learned about more routers. Now, we only log a notice
11832 at every 5% of progress. Fixes bug 9963.
11833 - Warn less verbosely when receiving a malformed
11834 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
11835 - When we run out of usable circuit IDs on a channel, log only one
11836 warning for the whole channel, and describe how many circuits
11837 there were on the channel. Fixes part of ticket 11553.
11839 o Minor features (relay):
11840 - If a circuit timed out for at least 3 minutes, check if we have a
11841 new external IP address, and publish a new descriptor with the new
11842 IP address if it changed. Resolves ticket 2454.
11844 o Minor features (controller):
11845 - Make the entire exit policy available from the control port via
11846 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
11848 - Because of the fix for ticket 11396, the real limit for memory
11849 usage may no longer match the configured MaxMemInQueues value. The
11850 real limit is now exposed via GETINFO limits/max-mem-in-queues.
11852 o Minor features (bridge client):
11853 - Report a more useful failure message when we can't connect to a
11854 bridge because we don't have the right pluggable transport
11855 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
11857 o Minor features (diagnostic):
11858 - Add more log messages to diagnose bug 7164, which causes
11859 intermittent "microdesc_free() called but md was still referenced"
11860 warnings. We now include more information, to figure out why we
11861 might be cleaning a microdescriptor for being too old if it's
11862 still referenced by a live node_t object.
11864 o Minor bugfixes (client, DNSPort):
11865 - When using DNSPort, try to respond to AAAA requests with AAAA
11866 answers. Previously, we hadn't looked at the request type when
11867 deciding which answer type to prefer. Fixes bug 10468; bugfix on
11869 - When receiving a DNS query for an unsupported record type, reply
11870 with no answer rather than with a NOTIMPL error. This behavior
11871 isn't correct either, but it will break fewer client programs, we
11872 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
11875 o Minor bugfixes (exit relay):
11876 - Stop leaking memory when we successfully resolve a PTR record.
11877 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
11879 o Minor bugfixes (bridge client):
11880 - Stop accepting bridge lines containing hostnames. Doing so would
11881 cause clients to perform DNS requests on the hostnames, which was
11882 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
11883 - Avoid a 60-second delay in the bootstrapping process when a Tor
11884 client with pluggable transports re-reads its configuration at
11885 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
11887 o Minor bugfixes (client, logging during bootstrap):
11888 - Warn only once if we start logging in an unsafe way. Previously,
11889 we complain as many times as we had problems. Fixes bug 9870;
11890 bugfix on 0.2.5.1-alpha.
11891 - Only report the first fatal bootstrap error on a given OR
11892 connection. This stops us from telling the controller bogus error
11893 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
11894 - Be more helpful when trying to run sandboxed on Linux without
11895 libseccomp. Instead of saying "Sandbox is not implemented on this
11896 platform", we now explain that we need to be built with
11897 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
11898 - Avoid generating spurious warnings when starting with
11899 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
11902 o Minor bugfixes (closing OR connections):
11903 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
11904 check if it's an or_connection_t and correctly call
11905 connection_or_close_for_error() rather than
11906 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
11908 - When closing all connections on setting DisableNetwork to 1, use
11909 connection_or_close_normally() rather than closing OR connections
11910 out from under the channel layer. Fixes bug 11306; bugfix on
11913 o Minor bugfixes (controller):
11914 - Avoid sending a garbage value to the controller when a circuit is
11915 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
11917 o Minor bugfixes (tor-fw-helper):
11918 - Allow tor-fw-helper to build again by adding src/ext to its
11919 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
11921 o Minor bugfixes (bridges):
11922 - Avoid potential crashes or bad behavior when launching a
11923 server-side managed proxy with ORPort or ExtORPort temporarily
11924 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
11926 o Minor bugfixes (platform-specific):
11927 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
11928 bug 11426; bugfix on 0.2.5.3-alpha.
11929 - When dumping a malformed directory object to disk, save it in
11930 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
11932 - Don't report failures from make_socket_reuseable() on incoming
11933 sockets on OSX: this can happen when incoming connections close
11934 early. Fixes bug 10081.
11936 o Minor bugfixes (trivial memory leaks):
11937 - Fix a small memory leak when signing a directory object. Fixes bug
11938 11275; bugfix on 0.2.4.13-alpha.
11939 - Free placeholder entries in our circuit table at exit; fixes a
11940 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
11941 - Don't re-initialize a second set of OpenSSL mutexes when starting
11942 up. Previously, we'd make one set of mutexes, and then immediately
11943 replace them with another. Fixes bug 11726; bugfix on
11945 - Resolve some memory leaks found by coverity in the unit tests, on
11946 exit in tor-gencert, and on a failure to compute digests for our
11947 own keys when generating a v3 networkstatus vote. These leaks
11948 should never have affected anyone in practice.
11950 o Minor bugfixes (hidden service):
11951 - Only retry attempts to connect to a chosen rendezvous point 8
11952 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
11954 o Minor bugfixes (misc code correctness):
11955 - Fix various instances of undefined behavior in channeltls.c,
11956 tor_memmem(), and eventdns.c that would cause us to construct
11957 pointers to memory outside an allocated object. (These invalid
11958 pointers were not accessed, but C does not even allow them to
11959 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
11960 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
11961 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
11962 fix some miscellaneous errors in our tests and codebase. Fixes bug
11963 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
11964 - Always check return values for unlink, munmap, UnmapViewOfFile;
11965 check strftime return values more often. In some cases all we can
11966 do is report a warning, but this may help prevent deeper bugs from
11967 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
11969 - Fix numerous warnings from the clang "scan-build" static analyzer.
11970 Some of these are programming style issues; some of them are false
11971 positives that indicated awkward code; some are undefined behavior
11972 cases related to constructing (but not using) invalid pointers;
11973 some are assumptions about API behavior; some are (harmlessly)
11974 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
11975 correct; and one or two are genuine bugs that weren't reachable
11976 from the rest of the program. Fixes bug 8793; bugfixes on many,
11980 - Build the torify.1 manpage again. Previously, we were only trying
11981 to build it when also building tor-fw-helper. That's why we didn't
11982 notice that we'd broken the ability to build it. Fixes bug 11321;
11983 bugfix on 0.2.5.1-alpha.
11984 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
11985 11061; bugfix on 0.2.4.7-alpha.
11986 - Correctly document that we search for a system torrc file before
11987 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
11989 - Resolve warnings from Doxygen.
11991 o Code simplifications and refactoring:
11992 - Remove is_internal_IP() function. Resolves ticket 4645.
11993 - Remove unused function circuit_dump_by_chan from circuitlist.c.
11994 Closes issue 9107; patch from "marek".
11995 - Change our use of the ENUM_BF macro to avoid declarations that
11998 o Deprecated versions:
11999 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
12000 attention for some while. Directory authorities no longer accept
12001 descriptors from relays running any version of Tor prior to Tor
12002 0.2.3.16-alpha. Resolves ticket 11149.
12005 - New macros in test.h to simplify writing mock-functions for unit
12006 tests. Part of ticket 11507. Patch from Dana Koch.
12007 - Complete tests for the status.c module. Resolves ticket 11507.
12008 Patch from Dana Koch.
12011 - Remove all code for the long unused v1 directory protocol.
12012 Resolves ticket 11070.
12015 Changes in version 0.2.5.3-alpha - 2014-03-22
12016 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
12017 two new anti-DoS features for Tor relays, resolves a bug that kept
12018 SOCKS5 support for IPv6 from working, fixes several annoying usability
12019 issues for bridge users, and removes more old code for unused
12022 The Tor 0.2.5.x release series is now in patch-freeze: no feature
12023 patches not already written will be considered for inclusion in 0.2.5.x.
12025 o Major features (relay security, DoS-resistance):
12026 - When deciding whether we have run out of memory and we need to
12027 close circuits, also consider memory allocated in buffers for
12028 streams attached to each circuit.
12030 This change, which extends an anti-DoS feature introduced in
12031 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
12032 better resist more memory-based DoS attacks than before. Since the
12033 MaxMemInCellQueues option now applies to all queues, it is renamed
12034 to MaxMemInQueues. This feature fixes bug 10169.
12035 - Avoid hash-flooding denial-of-service attacks by using the secure
12036 SipHash-2-4 hash function for our hashtables. Without this
12037 feature, an attacker could degrade performance of a targeted
12038 client or server by flooding their data structures with a large
12039 number of entries to be stored at the same hash table position,
12040 thereby slowing down the Tor instance. With this feature, hash
12041 table positions are derived from a randomized cryptographic key,
12042 and an attacker cannot predict which entries will collide. Closes
12044 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
12045 the default at 8GBytes), to better support Raspberry Pi users. Fixes
12046 bug 9686; bugfix on 0.2.4.14-alpha.
12048 o Minor features (bridges, pluggable transports):
12049 - Bridges now write the SHA1 digest of their identity key
12050 fingerprint (that is, a hash of a hash of their public key) to
12051 notice-level logs, and to a new hashed-fingerprint file. This
12052 information will help bridge operators look up their bridge in
12053 Globe and similar tools. Resolves ticket 10884.
12054 - Improve the message that Tor displays when running as a bridge
12055 using pluggable transports without an Extended ORPort listener.
12056 Also, log the message in the log file too. Resolves ticket 11043.
12058 o Minor features (other):
12059 - Add a new option, PredictedPortsRelevanceTime, to control how long
12060 after having received a request to connect to a given port Tor
12061 will try to keep circuits ready in anticipation of future requests
12062 for that port. Patch from "unixninja92"; implements ticket 9176.
12063 - Generate a warning if any ports are listed in the SocksPolicy,
12064 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
12065 AuthDirBadExit options. (These options only support address
12066 ranges.) Fixes part of ticket 11108.
12067 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
12070 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
12071 - Build without warnings under clang 3.4. (We have some macros that
12072 define static functions only some of which will get used later in
12073 the module. Starting with clang 3.4, these give a warning unless the
12074 unused attribute is set on them.) Resolves ticket 10904.
12075 - Fix build warnings about missing "a2x" comment when building the
12076 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
12077 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
12079 o Minor bugfixes (client):
12080 - Improve the log message when we can't connect to a hidden service
12081 because all of the hidden service directory nodes hosting its
12082 descriptor are excluded. Improves on our fix for bug 10722, which
12083 was a bugfix on 0.2.0.10-alpha.
12084 - Raise a control port warning when we fail to connect to all of
12085 our bridges. Previously, we didn't inform the controller, and
12086 the bootstrap process would stall. Fixes bug 11069; bugfix on
12088 - Exit immediately when a process-owning controller exits.
12089 Previously, tor relays would wait for a little while after their
12090 controller exited, as if they had gotten an INT signal -- but this
12091 was problematic, since there was no feedback for the user. To do a
12092 clean shutdown, controllers should send an INT signal and give Tor
12093 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
12094 - Stop attempting to connect to bridges before our pluggable
12095 transports are configured (harmless but resulted in some erroneous
12096 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
12097 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
12098 generating incorrect SOCKS5 responses, and confusing client
12099 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
12101 o Minor bugfixes (relays and bridges):
12102 - Avoid crashing on a malformed resolv.conf file when running a
12103 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
12104 - Non-exit relays no longer launch mock DNS requests to check for
12105 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
12106 non-exit relays stopped servicing DNS requests. Fixes bug 965;
12107 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
12108 - Bridges now report complete directory request statistics. Related
12109 to bug 5824; bugfix on 0.2.2.1-alpha.
12110 - Bridges now never collect statistics that were designed for
12111 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
12112 - Stop giving annoying warning messages when we decide not to launch
12113 a pluggable transport proxy that we don't need (because there are
12114 no bridges configured to use it). Resolves ticket 5018; bugfix
12116 - Give the correct URL in the warning message when trying to run a
12117 relay on an ancient version of Windows. Fixes bug 9393.
12119 o Minor bugfixes (backtrace support):
12120 - Support automatic backtraces on more platforms by using the
12121 "-fasynchronous-unwind-tables" compiler option. This option is
12122 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
12123 is on by default and table generation is not. This doesn't yet
12124 add Windows support; only Linux, OSX, and some BSDs are affected.
12125 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
12126 - Avoid strange behavior if two threads hit failed assertions at the
12127 same time and both try to log backtraces at once. (Previously, if
12128 this had happened, both threads would have stored their intermediate
12129 results in the same buffer, and generated junk outputs.) Reported by
12130 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
12131 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
12132 0.2.5.2-alpha; patch from Nick Hopper.
12134 o Minor bugfixes (unit tests):
12135 - Fix a small bug in the unit tests that might have made the tests
12136 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
12137 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
12140 - Remove all remaining code related to version-0 hidden service
12141 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
12142 the rest of bug 10841.
12145 - Document in the manpage that "KBytes" may also be written as
12146 "kilobytes" or "KB", that "Kbits" may also be written as
12147 "kilobits", and so forth. Closes ticket 9222.
12148 - Document that the ClientOnly config option overrides ORPort.
12149 Our old explanation made ClientOnly sound as though it did
12150 nothing at all. Resolves bug 9059.
12151 - Explain that SocksPolicy, DirPolicy, and similar options don't
12152 take port arguments. Fixes the other part of ticket 11108.
12153 - Fix a comment about the rend_server_descriptor_t.protocols field
12154 to more accurately describe its range. Also, make that field
12155 unsigned, to more accurately reflect its usage. Fixes bug 9099;
12156 bugfix on 0.2.1.5-alpha.
12157 - Fix the manpage's description of HiddenServiceAuthorizeClient:
12158 the maximum client name length is 16, not 19. Fixes bug 11118;
12159 bugfix on 0.2.1.6-alpha.
12161 o Code simplifications and refactoring:
12162 - Get rid of router->address, since in all cases it was just the
12163 string representation of router->addr. Resolves ticket 5528.
12165 o Test infrastructure:
12166 - Update to the latest version of tinytest.
12167 - Improve the tinytest implementation of string operation tests so
12168 that comparisons with NULL strings no longer crash the tests; they
12169 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
12172 Changes in version 0.2.4.21 - 2014-02-28
12173 Tor 0.2.4.21 further improves security against potential adversaries who
12174 find breaking 1024-bit crypto doable, and backports several stability
12175 and robustness patches from the 0.2.5 branch.
12177 o Major features (client security):
12178 - When we choose a path for a 3-hop circuit, make sure it contains
12179 at least one relay that supports the NTor circuit extension
12180 handshake. Otherwise, there is a chance that we're building
12181 a circuit that's worth attacking by an adversary who finds
12182 breaking 1024-bit crypto doable, and that chance changes the game
12183 theory. Implements ticket 9777.
12186 - Do not treat streams that fail with reason
12187 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
12188 since it could also indicate an ENETUNREACH connection error. Fixes
12189 part of bug 10777; bugfix on 0.2.4.8-alpha.
12191 o Code simplification and refactoring:
12192 - Remove data structures which were introduced to implement the
12193 CellStatistics option: they are now redundant with the new timestamp
12194 field in the regular packed_cell_t data structure, which we did
12195 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
12198 - Always clear OpenSSL bignums before freeing them -- even bignums
12199 that don't contain secrets. Resolves ticket 10793. Patch by
12201 - Build without warnings under clang 3.4. (We have some macros that
12202 define static functions only some of which will get used later in
12203 the module. Starting with clang 3.4, these give a warning unless the
12204 unused attribute is set on them.) Resolves ticket 10904.
12205 - Update geoip and geoip6 files to the February 7 2014 Maxmind
12206 GeoLite2 Country database.
12209 - Set the listen() backlog limit to the largest actually supported
12210 on the system, not to the value in a header file. Fixes bug 9716;
12211 bugfix on every released Tor.
12212 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
12213 exit node as a NOROUTE error, not an INTERNAL error, since they
12214 can apparently happen when trying to connect to the wrong sort
12215 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
12216 - Fix build warnings about missing "a2x" comment when building the
12217 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
12218 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
12219 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
12220 not entirely remove it from the connection lists. Fixes bug 9602;
12221 bugfix on 0.2.4.4-alpha.
12222 - Fix a segmentation fault in our benchmark code when running with
12223 Fedora's OpenSSL package, or any other OpenSSL that provides
12224 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
12225 - Turn "circuit handshake stats since last time" log messages into a
12226 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
12228 o Documentation fixes:
12229 - Document that all but one DirPort entry must have the NoAdvertise
12230 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
12233 Changes in version 0.2.5.2-alpha - 2014-02-13
12234 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
12235 like the "poor random number generation" fix and the "building too many
12236 circuits" fix. It also further improves security against potential
12237 adversaries who find breaking 1024-bit crypto doable, and launches
12238 pluggable transports on demand (which gets us closer to integrating
12239 pluggable transport support by default -- not to be confused with Tor
12240 bundles enabling pluggable transports and bridges by default).
12242 o Major features (client security):
12243 - When we choose a path for a 3-hop circuit, make sure it contains
12244 at least one relay that supports the NTor circuit extension
12245 handshake. Otherwise, there is a chance that we're building
12246 a circuit that's worth attacking by an adversary who finds
12247 breaking 1024-bit crypto doable, and that chance changes the game
12248 theory. Implements ticket 9777.
12249 - Clients now look at the "usecreatefast" consensus parameter to
12250 decide whether to use CREATE_FAST or CREATE cells for the first hop
12251 of their circuit. This approach can improve security on connections
12252 where Tor's circuit handshake is stronger than the available TLS
12253 connection security levels, but the tradeoff is more computational
12254 load on guard relays. Implements proposal 221. Resolves ticket 9386.
12256 o Major features (bridges):
12257 - Don't launch pluggable transport proxies if we don't have any
12258 bridges configured that would use them. Now we can list many
12259 pluggable transports, and Tor will dynamically start one when it
12260 hears a bridge address that needs it. Resolves ticket 5018.
12261 - The bridge directory authority now assigns status flags (Stable,
12262 Guard, etc) to bridges based on thresholds calculated over all
12263 Running bridges. Now bridgedb can finally make use of its features
12264 to e.g. include at least one Stable bridge in its answers. Fixes
12267 o Major features (other):
12268 - Extend ORCONN controller event to include an "ID" parameter,
12269 and add four new controller event types CONN_BW, CIRC_BW,
12270 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
12271 The new events are emitted in private Tor networks only, with the
12272 goal of being able to better track performance and load during
12273 full-network simulations. Implements proposal 218 and ticket 7359.
12274 - On some platforms (currently: recent OSX versions, glibc-based
12275 platforms that support the ELF format, and a few other
12276 Unix-like operating systems), Tor can now dump stack traces
12277 when a crash occurs or an assertion fails. By default, traces
12278 are dumped to stderr (if possible) and to any logs that are
12279 reporting errors. Implements ticket 9299.
12282 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
12283 not entirely remove it from the connection lists. Fixes bug 9602;
12284 bugfix on 0.2.4.4-alpha.
12285 - Do not treat streams that fail with reason
12286 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
12287 since it could also indicate an ENETUNREACH connection error. Fixes
12288 part of bug 10777; bugfix on 0.2.4.8-alpha.
12290 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
12291 - Do not allow OpenSSL engines to replace the PRNG, even when
12292 HardwareAccel is set. The only default builtin PRNG engine uses
12293 the Intel RDRAND instruction to replace the entire PRNG, and
12294 ignores all attempts to seed it with more entropy. That's
12295 cryptographically stupid: the right response to a new alleged
12296 entropy source is never to discard all previously used entropy
12297 sources. Fixes bug 10402; works around behavior introduced in
12298 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
12300 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
12301 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
12302 - Avoid launching spurious extra circuits when a stream is pending.
12303 This fixes a bug where any circuit that _wasn't_ unusable for new
12304 streams would be treated as if it were, causing extra circuits to
12305 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
12307 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12308 - No longer stop reading or writing on cpuworker connections when
12309 our rate limiting buckets go empty. Now we should handle circuit
12310 handshake requests more promptly. Resolves bug 9731.
12311 - Stop trying to bootstrap all our directory information from
12312 only our first guard. Discovered while fixing bug 9946; bugfix
12315 o Minor features (bridges, pluggable transports):
12316 - Add threshold cutoffs to the networkstatus document created by
12317 the Bridge Authority. Fixes bug 1117.
12318 - On Windows, spawn background processes using the CREATE_NO_WINDOW
12319 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
12320 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
12321 Vidalia set this option for us.) Implements ticket 10297.
12323 o Minor features (security):
12324 - Always clear OpenSSL bignums before freeing them -- even bignums
12325 that don't contain secrets. Resolves ticket 10793. Patch by
12326 Florent Daignière.
12328 o Minor features (config options and command line):
12329 - Add an --allow-missing-torrc commandline option that tells Tor to
12330 run even if the configuration file specified by -f is not available.
12331 Implements ticket 10060.
12332 - Add support for the TPROXY transparent proxying facility on Linux.
12333 See documentation for the new TransProxyType option for more
12334 details. Implementation by "thomo". Closes ticket 10582.
12336 o Minor features (controller):
12337 - Add a new "HS_DESC" controller event that reports activities
12338 related to hidden service descriptors. Resolves ticket 8510.
12339 - New "DROPGUARDS" controller command to forget all current entry
12340 guards. Not recommended for ordinary use, since replacing guards
12341 too frequently makes several attacks easier. Resolves ticket 9934;
12344 o Minor features (build):
12345 - Assume that a user using ./configure --host wants to cross-compile,
12346 and give an error if we cannot find a properly named
12347 tool-chain. Add a --disable-tool-name-check option to proceed
12348 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
12349 - If we run ./configure and the compiler recognizes -fstack-protector
12350 but the linker rejects it, warn the user about a potentially missing
12351 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
12353 o Minor features (testing):
12354 - If Python is installed, "make check" now runs extra tests beyond
12355 the unit test scripts.
12356 - When bootstrapping a test network, sometimes very few relays get
12357 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
12358 specify a set of relays which should be voted Guard regardless of
12359 their uptime or bandwidth. Addresses ticket 9206.
12361 o Minor features (log messages):
12362 - When ServerTransportPlugin is set on a bridge, Tor can write more
12363 useful statistics about bridge use in its extrainfo descriptors,
12364 but only if the Extended ORPort ("ExtORPort") is set too. Add a
12365 log message to inform the user in this case. Resolves ticket 9651.
12366 - When receiving a new controller connection, log the origin address.
12367 Resolves ticket 9698; patch from "sigpipe".
12368 - When logging OpenSSL engine status at startup, log the status of
12369 more engines. Fixes ticket 10043; patch from Joshua Datko.
12370 - Turn "circuit handshake stats since last time" log messages into a
12371 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
12373 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12374 - Improve the circuit queue out-of-memory handler. Previously, when
12375 we ran low on memory, we'd close whichever circuits had the most
12376 queued cells. Now, we close those that have the *oldest* queued
12377 cells, on the theory that those are most responsible for us
12378 running low on memory. Based on analysis from a forthcoming paper
12379 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
12380 - Generate bootstrapping status update events correctly when fetching
12381 microdescriptors. Fixes bug 9927.
12382 - Update to the October 2 2013 Maxmind GeoLite Country database.
12384 o Minor bugfixes (clients):
12385 - When closing a channel that has already been open, do not close
12386 pending circuits that were waiting to connect to the same relay.
12387 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
12390 o Minor bugfixes (relays):
12391 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
12392 exit node as a NOROUTE error, not an INTERNAL error, since they
12393 can apparently happen when trying to connect to the wrong sort
12394 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
12396 o Minor bugfixes (bridges):
12397 - Fix a bug where the first connection works to a bridge that uses a
12398 pluggable transport with client-side parameters, but we don't send
12399 the client-side parameters on subsequent connections. (We don't
12400 use any pluggable transports with client-side parameters yet,
12401 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
12402 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
12404 o Minor bugfixes (node selection):
12405 - If ExcludeNodes is set, consider non-excluded hidden service
12406 directory servers before excluded ones. Do not consider excluded
12407 hidden service directory servers at all if StrictNodes is
12408 set. (Previously, we would sometimes decide to connect to those
12409 servers, and then realize before we initiated a connection that
12410 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
12411 Reported by "mr-4".
12412 - If we set the ExitNodes option but it doesn't include any nodes
12413 that have the Exit flag, we would choose not to bootstrap. Now we
12414 bootstrap so long as ExitNodes includes nodes which can exit to
12415 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
12417 o Minor bugfixes (controller and command-line):
12418 - If changing a config option via "setconf" fails in a recoverable
12419 way, we used to nonetheless write our new control ports to the
12420 file described by the "ControlPortWriteToFile" option. Now we only
12421 write out that file if we successfully switch to the new config
12422 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
12423 - When a command-line option such as --version or --help that
12424 ordinarily implies --hush appears on the command line along with
12425 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
12426 only if it appeared later on the command line. Fixes bug 9578;
12427 bugfix on 0.2.5.1-alpha.
12429 o Minor bugfixes (code correctness):
12430 - Previously we used two temporary files when writing descriptors to
12431 disk; now we only use one. Fixes bug 1376.
12432 - Remove an erroneous (but impossible and thus harmless) pointer
12433 comparison that would have allowed compilers to skip a bounds
12434 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
12435 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
12436 - Fix an always-true assertion in pluggable transports code so it
12437 actually checks what it was trying to check. Fixes bug 10046;
12438 bugfix on 0.2.3.9-alpha. Found by "dcb".
12440 o Minor bugfixes (protocol correctness):
12441 - When receiving a VERSIONS cell with an odd number of bytes, close
12442 the connection immediately since the cell is malformed. Fixes bug
12443 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
12446 o Minor bugfixes (build):
12447 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
12448 turned off (that is, without support for v2 link handshakes). Fixes
12449 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
12450 - Fix compilation warnings and startup issues when running with
12451 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
12453 - Fix compilation on Solaris 9, which didn't like us having an
12454 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
12456 o Minor bugfixes (testing):
12457 - Fix a segmentation fault in our benchmark code when running with
12458 Fedora's OpenSSL package, or any other OpenSSL that provides
12459 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
12461 o Minor bugfixes (log messages):
12462 - Fix a bug where clients using bridges would report themselves
12463 as 50% bootstrapped even without a live consensus document.
12464 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
12465 - Suppress a warning where, if there's only one directory authority
12466 in the network, we would complain that votes and signatures cannot
12467 be uploaded to other directory authorities. Fixes bug 10842;
12468 bugfix on 0.2.2.26-beta.
12469 - Report bootstrapping progress correctly when we're downloading
12470 microdescriptors. We had updated our "do we have enough microdescs
12471 to begin building circuits?" logic most recently in 0.2.4.10-alpha
12472 (see bug 5956), but we left the bootstrap status event logic at
12473 "how far through getting 1/4 of them are we?" Fixes bug 9958;
12474 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
12476 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
12477 - Avoid a crash bug when starting with a corrupted microdescriptor
12478 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
12479 - If we fail to dump a previously cached microdescriptor to disk, avoid
12480 freeing duplicate data later on. Fixes bug 10423; bugfix on
12481 0.2.4.13-alpha. Spotted by "bobnomnom".
12483 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12484 - Correctly log long IPv6 exit policies, instead of truncating them
12485 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
12486 - Our default TLS ecdhe groups were backwards: we meant to be using
12487 P224 for relays (for performance win) and P256 for bridges (since
12488 it is more common in the wild). Instead we had it backwards. After
12489 reconsideration, we decided that the default should be P256 on all
12490 hosts, since its security is probably better, and since P224 is
12491 reportedly used quite little in the wild. Found by "skruffy" on
12492 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
12493 - Free directory authority certificate download statuses on exit
12494 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
12496 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12497 - If the guard we choose first doesn't answer, we would try the
12498 second guard, but once we connected to the second guard we would
12499 abandon it and retry the first one, slowing down bootstrapping.
12500 The fix is to treat all our initially chosen guards as acceptable
12501 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
12502 - Fix an assertion failure that would occur when disabling the
12503 ORPort setting on a running Tor process while accounting was
12504 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
12505 - When examining the list of network interfaces to find our address,
12506 do not consider non-running or disabled network interfaces. Fixes
12507 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
12508 - Avoid an off-by-one error when checking buffer boundaries when
12509 formatting the exit status of a pluggable transport helper.
12510 This is probably not an exploitable bug, but better safe than
12511 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
12514 o Removed code and features:
12515 - Clients now reject any directory authority certificates lacking
12516 a dir-key-crosscert element. These have been included since
12517 0.2.1.9-alpha, so there's no real reason for them to be optional
12518 any longer. Completes proposal 157. Resolves ticket 10162.
12519 - Remove all code that existed to support the v2 directory system,
12520 since there are no longer any v2 directory authorities. Resolves
12522 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
12523 options, which were used for designating authorities as "Hidden
12524 service authorities". There has been no use of hidden service
12525 authorities since 0.2.2.1-alpha, when we stopped uploading or
12526 downloading v0 hidden service descriptors. Fixes bug 10881; also
12527 part of a fix for bug 10841.
12529 o Code simplification and refactoring:
12530 - Remove some old fallback code designed to keep Tor clients working
12531 in a network with only two working relays. Elsewhere in the code we
12532 have long since stopped supporting such networks, so there wasn't
12533 much point in keeping it around. Addresses ticket 9926.
12534 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
12535 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
12536 - Remove data structures which were introduced to implement the
12537 CellStatistics option: they are now redundant with the addition
12538 of a timestamp to the regular packed_cell_t data structure, which
12539 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
12542 o Documentation (man page) fixes:
12543 - Update manpage to describe some of the files you can expect to
12544 find in Tor's DataDirectory. Addresses ticket 9839.
12545 - Document that all but one DirPort entry must have the NoAdvertise
12546 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
12548 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12549 - Clarify the usage and risks of setting the ContactInfo torrc line
12550 for your relay or bridge. Resolves ticket 9854.
12551 - Add anchors to the manpage so we can link to the html version of
12552 the documentation for specific options. Resolves ticket 9866.
12553 - Replace remaining references to DirServer in man page and
12554 log entries. Resolves ticket 10124.
12557 - Make the "tor-gencert" tool used by directory authority operators
12558 create 2048-bit signing keys by default (rather than 1024-bit, since
12559 1024-bit is uncomfortably small these days). Addresses ticket 10324.
12562 Changes in version 0.2.4.20 - 2013-12-22
12563 Tor 0.2.4.20 fixes potentially poor random number generation for users
12564 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
12565 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
12566 and 4) have no state file in their DataDirectory (as would happen on
12567 first start). Users who generated relay or hidden service identity
12568 keys in such a situation should discard them and generate new ones.
12570 This release also fixes a logic error that caused Tor clients to build
12571 many more preemptive circuits than they actually need.
12574 - Do not allow OpenSSL engines to replace the PRNG, even when
12575 HardwareAccel is set. The only default builtin PRNG engine uses
12576 the Intel RDRAND instruction to replace the entire PRNG, and
12577 ignores all attempts to seed it with more entropy. That's
12578 cryptographically stupid: the right response to a new alleged
12579 entropy source is never to discard all previously used entropy
12580 sources. Fixes bug 10402; works around behavior introduced in
12581 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
12583 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
12584 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
12585 - Avoid launching spurious extra circuits when a stream is pending.
12586 This fixes a bug where any circuit that _wasn't_ unusable for new
12587 streams would be treated as if it were, causing extra circuits to
12588 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
12591 - Avoid a crash bug when starting with a corrupted microdescriptor
12592 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
12593 - If we fail to dump a previously cached microdescriptor to disk, avoid
12594 freeing duplicate data later on. Fixes bug 10423; bugfix on
12595 0.2.4.13-alpha. Spotted by "bobnomnom".
12598 Changes in version 0.2.4.19 - 2013-12-11
12599 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
12600 (1986-2013). Aaron worked on diverse projects including helping to guide
12601 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
12602 transparency to the U.S government's PACER documents, and contributing
12603 design and development for Tor and Tor2Web. Aaron was one of the latest
12604 martyrs in our collective fight for civil liberties and human rights,
12605 and his death is all the more painful because he was one of us.
12607 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
12608 a new circuit handshake and link encryption that use ECC to provide
12609 better security and efficiency; makes relays better manage circuit
12610 creation requests; uses "directory guards" to reduce client enumeration
12611 risks; makes bridges collect and report statistics about the pluggable
12612 transports they support; cleans up and improves our geoip database;
12613 gets much closer to IPv6 support for clients, bridges, and relays; makes
12614 directory authorities use measured bandwidths rather than advertised
12615 ones when computing flags and thresholds; disables client-side DNS
12616 caching to reduce tracking risks; and fixes a big bug in bridge
12617 reachability testing. This release introduces two new design
12618 abstractions in the code: a new "channel" abstraction between circuits
12619 and or_connections to allow for implementing alternate relay-to-relay
12620 transports, and a new "circuitmux" abstraction storing the queue of
12621 circuits for a channel. The release also includes many stability,
12622 security, and privacy fixes.
12625 Changes in version 0.2.4.18-rc - 2013-11-16
12626 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
12627 series. It takes a variety of fixes from the 0.2.5.x branch to improve
12628 stability, performance, and better handling of edge cases.
12631 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
12632 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
12633 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
12634 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
12635 them to solve bug 6033.)
12638 - No longer stop reading or writing on cpuworker connections when
12639 our rate limiting buckets go empty. Now we should handle circuit
12640 handshake requests more promptly. Resolves bug 9731.
12641 - If we are unable to save a microdescriptor to the journal, do not
12642 drop it from memory and then reattempt downloading it. Fixes bug
12643 9645; bugfix on 0.2.2.6-alpha.
12644 - Stop trying to bootstrap all our directory information from
12645 only our first guard. Discovered while fixing bug 9946; bugfix
12647 - The new channel code sometimes lost track of in-progress circuits,
12648 causing long-running clients to stop building new circuits. The
12649 fix is to always call circuit_n_chan_done(chan, 0) from
12650 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
12652 o Minor bugfixes (on 0.2.4.x):
12653 - Correctly log long IPv6 exit policies, instead of truncating them
12654 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
12655 - Our default TLS ecdhe groups were backwards: we meant to be using
12656 P224 for relays (for performance win) and P256 for bridges (since
12657 it is more common in the wild). Instead we had it backwards. After
12658 reconsideration, we decided that the default should be P256 on all
12659 hosts, since its security is probably better, and since P224 is
12660 reportedly used quite little in the wild. Found by "skruffy" on
12661 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
12662 - Free directory authority certificate download statuses on exit
12663 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
12665 o Minor bugfixes (on 0.2.3.x and earlier):
12666 - If the guard we choose first doesn't answer, we would try the
12667 second guard, but once we connected to the second guard we would
12668 abandon it and retry the first one, slowing down bootstrapping.
12669 The fix is to treat all our initially chosen guards as acceptable
12670 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
12671 - Fix an assertion failure that would occur when disabling the
12672 ORPort setting on a running Tor process while accounting was
12673 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
12674 - When examining the list of network interfaces to find our address,
12675 do not consider non-running or disabled network interfaces. Fixes
12676 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
12677 - Avoid an off-by-one error when checking buffer boundaries when
12678 formatting the exit status of a pluggable transport helper.
12679 This is probably not an exploitable bug, but better safe than
12680 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
12683 o Minor features (protecting client timestamps):
12684 - Clients no longer send timestamps in their NETINFO cells. These were
12685 not used for anything, and they provided one small way for clients
12686 to be distinguished from each other as they moved from network to
12687 network or behind NAT. Implements part of proposal 222.
12688 - Clients now round timestamps in INTRODUCE cells down to the nearest
12689 10 minutes. If a new Support022HiddenServices option is set to 0, or
12690 if it's set to "auto" and the feature is disabled in the consensus,
12691 the timestamp is sent as 0 instead. Implements part of proposal 222.
12692 - Stop sending timestamps in AUTHENTICATE cells. This is not such
12693 a big deal from a security point of view, but it achieves no actual
12694 good purpose, and isn't needed. Implements part of proposal 222.
12695 - Reduce down accuracy of timestamps in hidden service descriptors.
12696 Implements part of proposal 222.
12698 o Minor features (other):
12699 - Improve the circuit queue out-of-memory handler. Previously, when
12700 we ran low on memory, we'd close whichever circuits had the most
12701 queued cells. Now, we close those that have the *oldest* queued
12702 cells, on the theory that those are most responsible for us
12703 running low on memory. Based on analysis from a forthcoming paper
12704 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
12705 - Generate bootstrapping status update events correctly when fetching
12706 microdescriptors. Fixes bug 9927.
12707 - Update to the October 2 2013 Maxmind GeoLite Country database.
12709 o Documentation fixes:
12710 - Clarify the usage and risks of setting the ContactInfo torrc line
12711 for your relay or bridge. Resolves ticket 9854.
12712 - Add anchors to the manpage so we can link to the html version of
12713 the documentation for specific options. Resolves ticket 9866.
12714 - Replace remaining references to DirServer in man page and
12715 log entries. Resolves ticket 10124.
12718 Changes in version 0.2.5.1-alpha - 2013-10-02
12719 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
12720 on Linux, allows bridges that offer pluggable transports to report usage
12721 statistics, fixes many issues to make testing easier, and provides
12722 a pile of minor features and bugfixes that have been waiting for a
12723 release of the new branch.
12725 This is the first alpha release in a new series, so expect there to
12726 be bugs. Users who would rather test out a more stable branch should
12727 stay with 0.2.4.x for now.
12729 o Major features (security):
12730 - Use the seccomp2 syscall filtering facility on Linux to limit
12731 which system calls Tor can invoke. This is an experimental,
12732 Linux-only feature to provide defense-in-depth against unknown
12733 attacks. To try turning it on, set "Sandbox 1" in your torrc
12734 file. Please be ready to report bugs. We hope to add support
12735 for better sandboxing in the future, including more fine-grained
12736 filters, better division of responsibility, and support for more
12737 platforms. This work has been done by Cristian-Matei Toader for
12738 Google Summer of Code.
12739 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
12740 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
12741 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
12742 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
12743 them to solve bug 6033.)
12745 o Major features (other):
12746 - Add support for passing arguments to managed pluggable transport
12747 proxies. Implements ticket 3594.
12748 - Bridges now track GeoIP information and the number of their users
12749 even when pluggable transports are in use, and report usage
12750 statistics in their extra-info descriptors. Resolves tickets 4773
12752 - Make testing Tor networks bootstrap better: lower directory fetch
12753 retry schedules and maximum interval without directory requests,
12754 and raise maximum download tries. Implements ticket 6752.
12755 - Add make target 'test-network' to run tests on a Chutney network.
12756 Implements ticket 8530.
12757 - The ntor handshake is now on-by-default, no matter what the
12758 directory authorities recommend. Implements ticket 8561.
12761 - Instead of writing destroy cells directly to outgoing connection
12762 buffers, queue them and intersperse them with other outgoing cells.
12763 This can prevent a set of resource starvation conditions where too
12764 many pending destroy cells prevent data cells from actually getting
12765 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
12766 bugfix on 0.2.0.1-alpha.
12767 - If we are unable to save a microdescriptor to the journal, do not
12768 drop it from memory and then reattempt downloading it. Fixes bug
12769 9645; bugfix on 0.2.2.6-alpha.
12770 - The new channel code sometimes lost track of in-progress circuits,
12771 causing long-running clients to stop building new circuits. The
12772 fix is to always call circuit_n_chan_done(chan, 0) from
12773 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
12776 - Tor now builds each source file in two modes: a mode that avoids
12777 exposing identifiers needlessly, and another mode that exposes
12778 more identifiers for testing. This lets the compiler do better at
12779 optimizing the production code, while enabling us to take more
12780 radical measures to let the unit tests test things.
12781 - The production builds no longer include functions used only in
12782 the unit tests; all functions exposed from a module only for
12783 unit-testing are now static in production builds.
12784 - Add an --enable-coverage configuration option to make the unit
12785 tests (and a new src/or/tor-cov target) to build with gcov test
12789 - We now have rudimentary function mocking support that our unit
12790 tests can use to test functions in isolation. Function mocking
12791 lets the tests temporarily replace a function's dependencies with
12792 stub functions, so that the tests can check the function without
12793 invoking the other functions it calls.
12794 - Add more unit tests for the <circid,channel>->circuit map, and
12795 the destroy-cell-tracking code to fix bug 7912.
12796 - Unit tests for failing cases of the TAP onion handshake.
12797 - More unit tests for address-manipulation functions.
12799 o Minor features (protecting client timestamps):
12800 - Clients no longer send timestamps in their NETINFO cells. These were
12801 not used for anything, and they provided one small way for clients
12802 to be distinguished from each other as they moved from network to
12803 network or behind NAT. Implements part of proposal 222.
12804 - Clients now round timestamps in INTRODUCE cells down to the nearest
12805 10 minutes. If a new Support022HiddenServices option is set to 0, or
12806 if it's set to "auto" and the feature is disabled in the consensus,
12807 the timestamp is sent as 0 instead. Implements part of proposal 222.
12808 - Stop sending timestamps in AUTHENTICATE cells. This is not such
12809 a big deal from a security point of view, but it achieves no actual
12810 good purpose, and isn't needed. Implements part of proposal 222.
12811 - Reduce down accuracy of timestamps in hidden service descriptors.
12812 Implements part of proposal 222.
12814 o Minor features (config options):
12815 - Config (torrc) lines now handle fingerprints which are missing
12816 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
12817 - Support a --dump-config option to print some or all of the
12818 configured options. Mainly useful for debugging the command-line
12819 option parsing code. Helps resolve ticket 4647.
12820 - Raise awareness of safer logging: notify user of potentially
12821 unsafe config options, like logging more verbosely than severity
12822 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
12823 - Add a new configuration option TestingV3AuthVotingStartOffset
12824 that bootstraps a network faster by changing the timing for
12825 consensus votes. Addresses ticket 8532.
12826 - Add a new torrc option "ServerTransportOptions" that allows
12827 bridge operators to pass configuration parameters to their
12828 pluggable transports. Resolves ticket 8929.
12829 - The config (torrc) file now accepts bandwidth and space limits in
12830 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
12831 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
12834 o Minor features (build):
12835 - Add support for `--library-versions` flag. Implements ticket 6384.
12836 - Return the "unexpected sendme" warnings to a warn severity, but make
12837 them rate limited, to help diagnose ticket 8093.
12838 - Detect a missing asciidoc, and warn the user about it, during
12839 configure rather than at build time. Fixes issue 6506. Patch from
12842 o Minor features (other):
12843 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
12844 sockets in a single system call. Implements ticket 5129.
12845 - Log current accounting state (bytes sent and received + remaining
12846 time for the current accounting period) in the relay's heartbeat
12847 message. Implements ticket 5526; patch from Peter Retzlaff.
12848 - Implement the TRANSPORT_LAUNCHED control port event that
12849 notifies controllers about new launched pluggable
12850 transports. Resolves ticket 5609.
12851 - If we're using the pure-C 32-bit curve25519_donna implementation
12852 of curve25519, build it with the -fomit-frame-pointer option to
12853 make it go faster on register-starved hosts. This improves our
12854 handshake performance by about 6% on i386 hosts without nacl.
12855 Closes ticket 8109.
12856 - Update to the September 4 2013 Maxmind GeoLite Country database.
12859 - Set the listen() backlog limit to the largest actually supported
12860 on the system, not to the value in a header file. Fixes bug 9716;
12861 bugfix on every released Tor.
12862 - No longer accept malformed http headers when parsing urls from
12863 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
12864 bugfix on 0.0.6pre1.
12865 - In munge_extrainfo_into_routerinfo(), check the return value of
12866 memchr(). This would have been a serious issue if we ever passed
12867 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
12869 - On the chance that somebody manages to build Tor on a
12870 platform where time_t is unsigned, correct the way that
12871 microdesc_add_to_cache() handles negative time arguments.
12872 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
12873 - Reject relative control socket paths and emit a warning. Previously,
12874 single-component control socket paths would be rejected, but Tor
12875 would not log why it could not validate the config. Fixes bug 9258;
12876 bugfix on 0.2.3.16-alpha.
12878 o Minor bugfixes (command line):
12879 - Use a single command-line parser for parsing torrc options on the
12880 command line and for finding special command-line options to avoid
12881 inconsistent behavior for torrc option arguments that have the same
12882 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
12884 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
12885 9573; bugfix on 0.0.9pre5.
12887 o Minor fixes (build, auxiliary programs):
12888 - Stop preprocessing the "torify" script with autoconf, since
12889 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
12891 - The tor-fw-helper program now follows the standard convention and
12892 exits with status code "0" on success. Fixes bug 9030; bugfix on
12893 0.2.3.1-alpha. Patch by Arlo Breault.
12894 - Corrected ./configure advice for what openssl dev package you should
12895 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
12897 o Minor code improvements:
12898 - Remove constants and tests for PKCS1 padding; it's insecure and
12899 shouldn't be used for anything new. Fixes bug 8792; patch
12901 - Remove instances of strcpy() from the unit tests. They weren't
12902 hurting anything, since they were only in the unit tests, but it's
12903 embarrassing to have strcpy() in the code at all, and some analysis
12904 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
12905 0.2.3.8-alpha. Patch from Arlo Breault.
12907 o Removed features:
12908 - Remove migration code from when we renamed the "cached-routers"
12909 file to "cached-descriptors" back in 0.2.0.8-alpha. This
12910 incidentally resolves ticket 6502 by cleaning up the related code
12911 a bit. Patch from Akshay Hebbar.
12913 o Code simplification and refactoring:
12914 - Extract the common duplicated code for creating a subdirectory
12915 of the data directory and writing to a file in it. Fixes ticket
12916 4282; patch from Peter Retzlaff.
12917 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
12918 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
12919 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
12920 - Add a set of accessor functions for the circuit timeout data
12921 structure. Fixes ticket 6153; patch from "piet".
12922 - Clean up exit paths from connection_listener_new(). Closes ticket
12923 8789. Patch from Arlo Breault.
12924 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
12925 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
12926 - Use a doubly-linked list to implement the global circuit list.
12927 Resolves ticket 9108. Patch from Marek Majkowski.
12928 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
12931 Changes in version 0.2.4.17-rc - 2013-09-05
12932 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
12933 series. It adds an emergency step to help us tolerate the massive
12934 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
12935 circuit-level handshakes now effectively jump the queue compared to
12936 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
12937 big bug hindering bridge reachability tests.
12940 - Relays now process the new "NTor" circuit-level handshake requests
12941 with higher priority than the old "TAP" circuit-level handshake
12942 requests. We still process some TAP requests to not totally starve
12943 0.2.3 clients when NTor becomes popular. A new consensus parameter
12944 "NumNTorsPerTAP" lets us tune the balance later if we need to.
12945 Implements ticket 9574.
12948 - If the circuit build timeout logic is disabled (via the consensus,
12949 or because we are an authority), then don't build testing circuits.
12950 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
12951 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
12952 previously they did not, which prevented them from receiving
12953 successful connections from relays for self-test or bandwidth
12954 testing. Also, when a relay is extending a circuit to a bridge,
12955 it needs to send a NETINFO cell, even when the bridge hasn't sent
12956 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
12957 - If the time to download the next old-style networkstatus is in
12958 the future, do not decline to consider whether to download the
12959 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
12963 - Avoid double-closing the listener socket in our socketpair()
12964 replacement (used on Windows) in the case where the addresses on
12965 our opened sockets don't match what we expected. Fixes bug 9400;
12966 bugfix on 0.0.2pre7. Found by Coverity.
12968 o Minor fixes (config options):
12969 - Avoid overflows when the user sets MaxCircuitDirtiness to a
12970 ridiculously high value, by imposing a (ridiculously high) 30-day
12971 maximum on MaxCircuitDirtiness.
12972 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
12973 message is logged at notice, not at info.
12974 - Warn and fail if a server is configured not to advertise any
12975 ORPorts at all. (We need *something* to put in our descriptor,
12976 or we just won't work.)
12979 - Track how many "TAP" and "NTor" circuit handshake requests we get,
12980 and how many we complete, and log it every hour to help relay
12981 operators follow trends in network load. Addresses ticket 9658.
12982 - Update to the August 7 2013 Maxmind GeoLite Country database.
12985 Changes in version 0.2.4.16-rc - 2013-08-10
12986 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
12987 series. It fixes several crash bugs in the 0.2.4 branch.
12990 - Fix a bug in the voting algorithm that could yield incorrect results
12991 when a non-naming authority declared too many flags. Fixes bug 9200;
12992 bugfix on 0.2.0.3-alpha.
12993 - Fix an uninitialized read that could in some cases lead to a remote
12994 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
12995 Anybody running a hidden service on the experimental 0.2.4.x
12996 branch should upgrade. (This is, so far as we know, unrelated to
12998 - Avoid an assertion failure when processing DNS replies without the
12999 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
13000 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
13001 0.2.4.15-rc. Found by stem integration tests.
13004 - Fix an invalid memory read that occurred when a pluggable
13005 transport proxy failed its configuration protocol.
13006 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
13007 - When evaluating whether to use a connection that we haven't
13008 decided is canonical using a recent link protocol version,
13009 decide that it's canonical only if it used address _does_
13010 match the desired address. Fixes bug 9309; bugfix on
13011 0.2.4.4-alpha. Reported by skruffy.
13012 - Make the default behavior of NumDirectoryGuards be to track
13013 NumEntryGuards. Now a user who changes only NumEntryGuards will get
13014 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
13015 - Fix a spurious compilation warning with some older versions of
13016 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
13019 - Update to the July 3 2013 Maxmind GeoLite Country database.
13022 Changes in version 0.2.4.15-rc - 2013-07-01
13023 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
13024 series. It fixes a few smaller bugs, but generally appears stable.
13025 Please test it and let us know whether it is!
13028 - When receiving a new configuration file via the control port's
13029 LOADCONF command, do not treat the defaults file as absent.
13030 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
13033 - Issue a warning when running with the bufferevents backend enabled.
13034 It's still not stable, and people should know that they're likely
13035 to hit unexpected problems. Closes ticket 9147.
13038 Changes in version 0.2.4.14-alpha - 2013-06-18
13039 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
13040 present in 0.2.4.13-alpha.
13043 - When we have too much memory queued in circuits (according to a new
13044 MaxMemInCellQueues option), close the circuits consuming the most
13045 memory. This prevents us from running out of memory as a relay if
13046 circuits fill up faster than they can be drained. Fixes bug 9063;
13047 bugfix on the 54th commit of Tor. This bug is a further fix beyond
13048 bug 6252, whose fix was merged into 0.2.3.21-rc.
13050 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
13051 where we tried to solve this issue simply by imposing an upper limit
13052 on the number of queued cells for a single circuit. That approach
13053 proved to be problematic, since there are ways to provoke clients to
13054 send a number of cells in excess of any such reasonable limit. Fixes
13055 bug 9072; bugfix on 0.2.4.13-alpha.
13057 - Limit hidden service descriptors to at most ten introduction
13058 points, to slow one kind of guard enumeration. Fixes bug 9002;
13059 bugfix on 0.1.1.11-alpha.
13062 Changes in version 0.2.4.13-alpha - 2013-06-14
13063 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
13064 vulnerabilities, makes socks5 username/password circuit isolation
13065 actually actually work (this time for sure!), and cleans up a bunch
13066 of other issues in preparation for a release candidate.
13068 o Major bugfixes (robustness):
13069 - Close any circuit that has too many cells queued on it. Fixes
13070 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
13071 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
13072 - Prevent the get_freelists() function from running off the end of
13073 the list of freelists if it somehow gets an unrecognized
13074 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
13076 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
13077 when an exit connection with optimistic data succeeds immediately
13078 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
13080 - Fix a directory authority crash bug when building a consensus
13081 using an older consensus as its basis. Fixes bug 8833. Bugfix
13085 - Avoid a memory leak where we would leak a consensus body when we
13086 find that a consensus which we couldn't previously verify due to
13087 missing certificates is now verifiable. Fixes bug 8719; bugfix
13089 - We used to always request authority certificates by identity digest,
13090 meaning we'd get the newest one even when we wanted one with a
13091 different signing key. Then we would complain about being given
13092 a certificate we already had, and never get the one we really
13093 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
13094 resource to request the one we want. Fixes bug 5595; bugfix on
13096 - Follow the socks5 protocol when offering username/password
13097 authentication. The fix for bug 8117 exposed this bug, and it
13098 turns out real-world applications like Pidgin do care. Bugfix on
13099 0.2.3.2-alpha; fixes bug 8879.
13100 - Prevent failures on Windows Vista and later when rebuilding the
13101 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
13102 bugfix on 0.2.4.12-alpha.
13105 - Fix an impossible buffer overrun in the AES unit tests. Fixes
13106 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
13107 - If for some reason we fail to write a microdescriptor while
13108 rebuilding the cache, do not let the annotations from that
13109 microdescriptor linger in the cache file, and do not let the
13110 microdescriptor stay recorded as present in its old location.
13111 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
13112 - Fix a memory leak that would occur whenever a configuration
13113 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
13114 - Paste the description for PathBias parameters from the man
13115 page into or.h, so the code documents them too. Fixes bug 7982;
13116 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
13117 - Relays now treat a changed IPv6 ORPort as sufficient reason to
13118 publish an updated descriptor. Fixes bug 6026; bugfix on
13120 - When launching a resolve request on behalf of an AF_UNIX control
13121 socket, omit the address field of the new entry connection, used in
13122 subsequent controller events, rather than letting tor_dup_addr()
13123 set it to "<unknown address type>". Fixes bug 8639; bugfix on
13126 o Minor bugfixes (log messages):
13127 - Fix a scaling issue in the path bias accounting code that
13128 resulted in "Bug:" log messages from either
13129 pathbias_scale_close_rates() or pathbias_count_build_success().
13130 This represents a bugfix on a previous bugfix: the original fix
13131 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
13133 - Give a less useless error message when the user asks for an IPv4
13134 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
13138 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
13139 to tolerate bug 8093 for now.
13140 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
13141 in directory authority votes to describe whether they have enough
13142 measured bandwidths to ignore advertised (relay descriptor)
13143 bandwidth claims. Resolves ticket 8711.
13144 - Update to the June 5 2013 Maxmind GeoLite Country database.
13146 o Removed documentation:
13147 - Remove some of the older contents of doc/ as obsolete; move others
13148 to torspec.git. Fixes bug 8965.
13150 o Code simplification and refactoring:
13151 - Avoid using character buffers when constructing most directory
13152 objects: this approach was unwieldy and error-prone. Instead,
13153 build smartlists of strings, and concatenate them when done.
13156 Changes in version 0.2.4.12-alpha - 2013-04-18
13157 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
13158 process for lengthening the guard rotation period, makes directory
13159 authority opinions in the consensus a bit less gameable, makes socks5
13160 username/password circuit isolation actually work, and fixes a wide
13161 variety of other issues.
13164 - Raise the default time that a client keeps an entry guard from
13165 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
13166 2012 paper. (We would make it even longer, but we need better client
13167 load balancing first.) Also, make the guard lifetime controllable
13168 via a new GuardLifetime torrc option and a GuardLifetime consensus
13169 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
13170 - Directory authorities now prefer using measured bandwidths to
13171 advertised ones when computing flags and thresholds. Resolves
13173 - Directory authorities that have more than a threshold number
13174 of relays with measured bandwidths now treat relays with unmeasured
13175 bandwidths as having bandwidth 0. Resolves ticket 8435.
13177 o Major bugfixes (assert / resource use):
13178 - Avoid a bug where our response to TLS renegotiation under certain
13179 network conditions could lead to a busy-loop, with 100% CPU
13180 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
13181 - Avoid an assertion when we discover that we'd like to write a cell
13182 onto a closing connection: just discard the cell. Fixes another
13183 case of bug 7350; bugfix on 0.2.4.4-alpha.
13185 o Major bugfixes (client-side privacy):
13186 - When we mark a circuit as unusable for new circuits, have it
13187 continue to be unusable for new circuits even if MaxCircuitDirtiness
13188 is increased too much at the wrong time, or the system clock jumps
13189 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
13190 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
13191 which have resolved to internal addresses") is set, apply that
13192 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
13193 - When an exit relay rejects a stream with reason "exit policy", but
13194 we only know an exit policy summary (e.g. from the microdesc
13195 consensus) for it, do not mark the relay as useless for all exiting.
13196 Instead, mark just the circuit as unsuitable for that particular
13197 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
13198 - Allow applications to get proper stream isolation with
13199 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
13200 username/password authentication also offer "no authentication". Tor
13201 had previously preferred "no authentication", so the applications
13202 never actually sent Tor their auth details. Now Tor selects
13203 username/password authentication if it's offered. You can disable
13204 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
13205 bug 8117; bugfix on 0.2.3.3-alpha.
13207 o Major bugfixes (other):
13208 - When unable to find any working directory nodes to use as a
13209 directory guard, give up rather than adding the same non-working
13210 nodes to the directory guard list over and over. Fixes bug 8231;
13211 bugfix on 0.2.4.8-alpha.
13214 - Reject as invalid most directory objects containing a NUL.
13215 Belt-and-suspender fix for bug 8037.
13216 - In our testsuite, create temporary directories with a bit more
13217 entropy in their name to make name collisions less likely. Fixes
13219 - Add CACHED keyword to ADDRMAP events in the control protocol
13220 to indicate whether a DNS result will be cached or not. Resolves
13222 - Update to the April 3 2013 Maxmind GeoLite Country database.
13224 o Minor features (build):
13225 - Detect and reject attempts to build Tor with threading support
13226 when OpenSSL has been compiled without threading support.
13228 - Clarify that when autoconf is checking for nacl, it is checking
13229 specifically for nacl with a fast curve25519 implementation.
13231 - Warn if building on a platform with an unsigned time_t: there
13232 are too many places where Tor currently assumes that time_t can
13233 hold negative values. We'd like to fix them all, but probably
13236 o Minor bugfixes (build):
13237 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
13238 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
13239 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
13240 - Add the old src/or/micro-revision.i filename to CLEANFILES.
13241 On the off chance that somebody has one, it will go away as soon
13242 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
13243 - Build Tor correctly on 32-bit platforms where the compiler can build
13244 but not run code using the "uint128_t" construction. Fixes bug 8587;
13245 bugfix on 0.2.4.8-alpha.
13246 - Fix compilation warning with some versions of clang that would
13247 prefer the -Wswitch-enum compiler flag to warn about switch
13248 statements with missing enum values, even if those switch
13249 statements have a "default:" statement. Fixes bug 8598; bugfix
13252 o Minor bugfixes (protocol):
13253 - Fix the handling of a TRUNCATE cell when it arrives while the
13254 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
13255 - Fix a misframing issue when reading the version numbers in a
13256 VERSIONS cell. Previously we would recognize [00 01 00 02] as
13257 'version 1, version 2, and version 0x100', when it should have
13258 only included versions 1 and 2. Fixes bug 8059; bugfix on
13259 0.2.0.10-alpha. Reported pseudonymously.
13260 - Make the format and order of STREAM events for DNS lookups
13261 consistent among the various ways to launch DNS lookups. Fixes
13262 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
13263 - Correct our check for which versions of Tor support the EXTEND2
13264 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
13265 later, when support was really added in version 0.2.4.8-alpha.
13266 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
13268 o Minor bugfixes (other):
13269 - Correctly store microdescriptors and extrainfo descriptors with
13270 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
13271 Bug reported by "cypherpunks".
13272 - Increase the width of the field used to remember a connection's
13273 link protocol version to two bytes. Harmless for now, since the
13274 only currently recognized versions are one byte long. Reported
13275 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
13276 - If the state file's path bias counts are invalid (presumably from a
13277 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
13278 additional checks and log messages to the scaling of Path Bias
13279 counts, in case there still are remaining issues with scaling.
13280 Should help resolve bug 8235.
13281 - Eliminate several instances where we use "Nickname=ID" to refer to
13282 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
13283 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
13284 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
13286 o Minor bugfixes (syscalls):
13287 - Always check the return values of functions fcntl() and
13288 setsockopt(). We don't believe these are ever actually failing in
13289 practice, but better safe than sorry. Also, checking these return
13290 values should please analysis tools like Coverity. Patch from
13291 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
13292 - Use direct writes rather than stdio when building microdescriptor
13293 caches, in an attempt to mitigate bug 8031, or at least make it
13296 o Minor bugfixes (config):
13297 - When rejecting a configuration because we were unable to parse a
13298 quoted string, log an actual error message. Fixes bug 7950; bugfix
13300 - Behave correctly when the user disables LearnCircuitBuildTimeout
13301 but doesn't tell us what they would like the timeout to be. Fixes
13302 bug 6304; bugfix on 0.2.2.14-alpha.
13303 - When autodetecting the number of CPUs, use the number of available
13304 CPUs in preference to the number of configured CPUs. Inform the
13305 user if this reduces the number of available CPUs. Fixes bug 8002;
13306 bugfix on 0.2.3.1-alpha.
13307 - Make it an error when you set EntryNodes but disable UseGuardNodes,
13308 since it will (surprisingly to some users) ignore EntryNodes. Fixes
13309 bug 8180; bugfix on 0.2.3.11-alpha.
13310 - Allow TestingTorNetworks to override the 4096-byte minimum for
13311 the Fast threshold. Otherwise they can't bootstrap until they've
13312 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
13313 - Fix some logic errors when the user manually overrides the
13314 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
13317 o Minor bugfixes (log messages to help diagnose bugs):
13318 - If we fail to free a microdescriptor because of bug 7164, log
13319 the filename and line number from which we tried to free it.
13320 - Add another diagnostic to the heartbeat message: track and log
13321 overhead that TLS is adding to the data we write. If this is
13322 high, we are sending too little data to SSL_write at a time.
13323 Diagnostic for bug 7707.
13324 - Add more detail to a log message about relaxed timeouts, to help
13326 - Warn more aggressively when flushing microdescriptors to a
13327 microdescriptor cache fails, in an attempt to mitigate bug 8031,
13328 or at least make it more diagnosable.
13329 - Improve debugging output to help track down bug 8185 ("Bug:
13330 outgoing relay cell has n_chan==NULL. Dropping.")
13331 - Log the purpose of a path-bias testing circuit correctly.
13332 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
13334 o Minor bugfixes (0.2.4.x log messages that were too noisy):
13335 - Don't attempt to relax the timeout of already opened 1-hop circuits.
13336 They might never timeout. This should eliminate some/all cases of
13337 the relaxed timeout log message.
13338 - Use circuit creation time for network liveness evaluation. This
13339 should eliminate warning log messages about liveness caused
13340 by changes in timeout evaluation. Fixes bug 6572; bugfix on
13342 - Reduce a path bias length check from notice to info. The message
13343 is triggered when creating controller circuits. Fixes bug 8196;
13344 bugfix on 0.2.4.8-alpha.
13345 - Fix a path state issue that triggered a notice during relay startup.
13346 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
13347 - Reduce occurrences of warns about circuit purpose in
13348 connection_ap_expire_building(). Fixes bug 8477; bugfix on
13351 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
13352 - If we encounter a write failure on a SOCKS connection before we
13353 finish our SOCKS handshake, don't warn that we closed the
13354 connection before we could send a SOCKS reply. Fixes bug 8427;
13355 bugfix on 0.1.0.1-rc.
13356 - Correctly recognize that [::1] is a loopback address. Fixes
13357 bug 8377; bugfix on 0.2.1.3-alpha.
13358 - Fix a directory authority warn caused when we have a large amount
13359 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
13360 - Don't log inappropriate heartbeat messages when hibernating: a
13361 hibernating node is _expected_ to drop out of the consensus,
13362 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
13363 bugfix on 0.2.3.1-alpha.
13364 - Don't complain about bootstrapping problems while hibernating.
13365 These complaints reflect a general code problem, but not one
13366 with any problematic effects (no connections are actually
13367 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
13369 o Documentation fixes:
13370 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
13371 names match. Fixes bug 7768.
13372 - Make the torify manpage no longer refer to tsocks; torify hasn't
13373 supported tsocks since 0.2.3.14-alpha.
13374 - Make the tor manpage no longer reference tsocks.
13375 - Fix the GeoIPExcludeUnknown documentation to refer to
13376 ExcludeExitNodes rather than the currently nonexistent
13377 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
13380 - The tor-tsocks.conf is no longer distributed or installed. We
13381 recommend that tsocks users use torsocks instead. Resolves
13385 Changes in version 0.2.4.11-alpha - 2013-03-11
13386 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
13387 more robust, makes hidden service authentication work again, and
13388 resolves a DPI fingerprint for Tor's SSL transport.
13390 o Major features (directory authorities):
13391 - Directory authorities now support a new consensus method (17)
13392 where they cap the published bandwidth of servers for which
13393 insufficient bandwidth measurements exist. Fixes part of bug 2286.
13394 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
13395 serve any v2 directory information. Now we can test disabling the
13396 old deprecated v2 directory format, and see whether doing so has
13397 any effect on network load. Begins to fix bug 6783.
13398 - Directory authorities now include inside each vote a statement of
13399 the performance thresholds they used when assigning flags.
13400 Implements ticket 8151.
13402 o Major bugfixes (directory authorities):
13403 - Stop marking every relay as having been down for one hour every
13404 time we restart a directory authority. These artificial downtimes
13405 were messing with our Stable and Guard flag calculations. Fixes
13406 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
13408 o Major bugfixes (hidden services):
13409 - Allow hidden service authentication to succeed again. When we
13410 refactored the hidden service introduction code back
13411 in 0.2.4.1-alpha, we didn't update the code that checks
13412 whether authentication information is present, causing all
13413 authentication checks to return "false". Fix for bug 8207; bugfix
13414 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
13416 o Minor features (relays, bridges):
13417 - Make bridge relays check once a minute for whether their IP
13418 address has changed, rather than only every 15 minutes. Resolves
13419 bugs 1913 and 1992.
13420 - Refactor resolve_my_address() so it returns the method by which we
13421 decided our public IP address (explicitly configured, resolved from
13422 explicit hostname, guessed from interfaces, learned by gethostname).
13423 Now we can provide more helpful log messages when a relay guesses
13424 its IP address incorrectly (e.g. due to unexpected lines in
13425 /etc/hosts). Resolves ticket 2267.
13426 - Teach bridge-using clients to avoid 0.2.2 bridges when making
13427 microdescriptor-related dir requests, and only fall back to normal
13428 descriptors if none of their bridges can handle microdescriptors
13429 (as opposed to the fix in ticket 4013, which caused them to fall
13430 back to normal descriptors if *any* of their bridges preferred
13431 them). Resolves ticket 4994.
13432 - Randomize the lifetime of our SSL link certificate, so censors can't
13433 use the static value for filtering Tor flows. Resolves ticket 8443;
13434 related to ticket 4014 which was included in 0.2.2.33.
13435 - Support a new version of the link protocol that allows 4-byte circuit
13436 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
13437 a possible resource exhaustion issue. Closes ticket 7351; implements
13440 o Minor features (portability):
13441 - Tweak the curve25519-donna*.c implementations to tolerate systems
13442 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
13443 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
13444 the signs of types during autoconf. This is better than our old
13445 approach, which didn't work when cross-compiling.
13446 - Detect the sign of enum values, rather than assuming that MSC is the
13447 only compiler where enum types are all signed. Fixes bug 7727;
13448 bugfix on 0.2.4.10-alpha.
13450 o Minor features (other):
13451 - Say "KBytes" rather than "KB" in the man page (for various values
13452 of K), to further reduce confusion about whether Tor counts in
13453 units of memory or fractions of units of memory. Resolves ticket 7054.
13454 - Clear the high bit on curve25519 public keys before passing them to
13455 our backend, in case we ever wind up using a backend that doesn't do
13456 so itself. If we used such a backend, and *didn't* clear the high bit,
13457 we could wind up in a situation where users with such backends would
13458 be distinguishable from users without. Fixes bug 8121; bugfix on
13460 - Update to the March 6 2013 Maxmind GeoLite Country database.
13462 o Minor bugfixes (clients):
13463 - When we receive a RELAY_END cell with the reason DONE, or with no
13464 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
13465 status as "connection refused". Previously we reported these cases
13466 as success but then immediately closed the connection. Fixes bug
13467 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
13468 - Downgrade an assertion in connection_ap_expire_beginning to an
13469 LD_BUG message. The fix for bug 8024 should prevent this message
13470 from displaying, but just in case, a warn that we can diagnose
13471 is better than more assert crashes. Fixes bug 8065; bugfix on
13473 - Lower path use bias thresholds to .80 for notice and .60 for warn.
13474 Also make the rate limiting flags for the path use bias log messages
13475 independent from the original path bias flags. Fixes bug 8161;
13476 bugfix on 0.2.4.10-alpha.
13478 o Minor bugfixes (relays):
13479 - Stop trying to resolve our hostname so often (e.g. every time we
13480 think about doing a directory fetch). Now we reuse the cached
13481 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
13482 and 2410 (bugfix on 0.1.2.2-alpha).
13483 - Stop sending a stray "(null)" in some cases for the server status
13484 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
13486 - When choosing which stream on a formerly stalled circuit to wake
13487 first, make better use of the platform's weak RNG. Previously,
13488 we had been using the % ("modulo") operator to try to generate a
13489 1/N chance of picking each stream, but this behaves badly with
13490 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
13492 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
13493 Irix's random() only return 15 bits; Solaris's random() returns more
13494 bits but its RAND_MAX says it only returns 15, and so on. Motivated
13495 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
13497 o Minor bugfixes (directory authorities):
13498 - Directory authorities now use less space when formatting identical
13499 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
13502 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
13503 - Avoid leaking memory if we fail to compute a consensus signature
13504 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
13505 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
13507 - Fix a memory leak during safe-cookie controller authentication.
13508 Bugfix on 0.2.3.13-alpha.
13509 - Avoid memory leak of IPv6 policy content if we fail to format it into
13510 a router descriptor. Bugfix on 0.2.4.7-alpha.
13512 o Minor bugfixes (other code correctness issues):
13513 - Avoid a crash if we fail to generate an extrainfo descriptor.
13514 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
13515 this is CID 718634.
13516 - When detecting the largest possible file descriptor (in order to
13517 close all file descriptors when launching a new program), actually
13518 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
13519 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
13521 - Fix a copy-and-paste error when adding a missing A1 to a routerset
13522 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
13523 Bugfix on 0.2.4.10-alpha.
13524 - Fix an impossible-to-trigger integer overflow when estimating how
13525 long our onionskin queue would take. (This overflow would require us
13526 to accept 4 million onionskins before processing 100 of them.) Fixes
13527 bug 8210; bugfix on 0.2.4.10-alpha.
13529 o Code simplification and refactoring:
13530 - Add a wrapper function for the common "log a message with a
13534 Changes in version 0.2.4.10-alpha - 2013-02-04
13535 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
13536 certain attacks that flood the network with relays; changes the queue
13537 for circuit create requests from a sized-based limit to a time-based
13538 limit; resumes building with MSVC on Windows; and fixes a wide variety
13541 o Major bugfixes (directory authority):
13542 - When computing directory thresholds, ignore any rejected-as-sybil
13543 nodes during the computation so that they can't influence Fast,
13544 Guard, etc. (We should have done this for proposal 109.) Fixes
13546 - When marking a node as a likely sybil, reset its uptime metrics
13547 to zero, so that it cannot time towards getting marked as Guard,
13548 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
13552 - When a TLS write is partially successful but incomplete, remember
13553 that the flushed part has been flushed, and notice that bytes were
13554 actually written. Reported and fixed pseudonymously. Fixes bug
13555 7708; bugfix on Tor 0.1.0.5-rc.
13556 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
13557 ID: these could be used to create unexpected streams and circuits
13558 which would count as "present" to some parts of Tor but "absent"
13559 to others, leading to zombie circuits and streams or to a bandwidth
13560 denial-of-service. Fixes bug 7889; bugfix on every released version
13561 of Tor. Reported by "oftc_must_be_destroyed".
13562 - Rename all macros in our local copy of queue.h to begin with "TOR_".
13563 This change seems the only good way to permanently prevent conflicts
13564 with queue.h on various operating systems. Fixes bug 8107; bugfix
13567 o Major features (relay):
13568 - Instead of limiting the number of queued onionskins (aka circuit
13569 create requests) to a fixed, hard-to-configure number, we limit
13570 the size of the queue based on how many we expect to be able to
13571 process in a given amount of time. We estimate the time it will
13572 take to process an onionskin based on average processing time
13573 of previous onionskins. Closes ticket 7291. You'll never have to
13574 configure MaxOnionsPending again.
13576 o Major features (portability):
13577 - Resume building correctly with MSVC and Makefile.nmake. This patch
13578 resolves numerous bugs and fixes reported by ultramage, including
13579 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
13580 - Make the ntor and curve25519 code build correctly with MSVC.
13581 Fix on 0.2.4.8-alpha.
13584 - When directory authorities are computing thresholds for flags,
13585 never let the threshold for the Fast flag fall below 4096
13586 bytes. Also, do not consider nodes with extremely low bandwidths
13587 when deciding thresholds for various directory flags. This change
13588 should raise our threshold for Fast relays, possibly in turn
13589 improving overall network performance; see ticket 1854. Resolves
13591 - The Tor client now ignores sub-domain components of a .onion
13592 address. This change makes HTTP "virtual" hosting
13593 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
13594 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
13595 hosted on the same hidden service. Implements proposal 204.
13596 - We compute the overhead from passing onionskins back and forth to
13597 cpuworkers, and report it when dumping statistics in response to
13598 SIGUSR1. Supports ticket 7291.
13600 o Minor features (path selection):
13601 - When deciding whether we have enough descriptors to build circuits,
13602 instead of looking at raw relay counts, look at which fraction
13603 of (bandwidth-weighted) paths we're able to build. This approach
13604 keeps clients from building circuits if their paths are likely to
13605 stand out statistically. The default fraction of paths needed is
13606 taken from the consensus directory; you can override it with the
13607 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
13608 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
13609 and we have GeoIP information, also exclude all nodes with unknown
13610 countries "??" and "A1". This behavior is controlled by the
13611 new GeoIPExcludeUnknown option: you can make such nodes always
13612 excluded with "GeoIPExcludeUnknown 1", and disable the feature
13613 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
13614 gets you the default behavior. Implements feature 7706.
13615 - Path Use Bias: Perform separate accounting for successful circuit
13616 use. Keep separate statistics on stream attempt rates versus stream
13617 success rates for each guard. Provide configurable thresholds to
13618 determine when to emit log messages or disable use of guards that
13619 fail too many stream attempts. Resolves ticket 7802.
13621 o Minor features (log messages):
13622 - When learning a fingerprint for a bridge, log its corresponding
13623 transport type. Implements ticket 7896.
13624 - Improve the log message when "Bug/attack: unexpected sendme cell
13625 from client" occurs, to help us track bug 8093.
13628 - Remove a couple of extraneous semicolons that were upsetting the
13629 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
13630 bugfix on 0.2.2.1-alpha.
13631 - Remove a source of rounding error during path bias count scaling;
13632 don't count cannibalized circuits as used for path bias until we
13633 actually try to use them; and fix a circuit_package_relay_cell()
13634 warning message about n_chan==NULL. Fixes bug 7802.
13635 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
13636 actually link against nacl when we're configured to use it. Fixes
13637 bug 7972; bugfix on 0.2.4.8-alpha.
13638 - Compile correctly with the --disable-curve25519 option. Fixes
13639 bug 8153; bugfix on 0.2.4.8-alpha.
13641 o Build improvements:
13642 - Do not report status verbosely from autogen.sh unless the -v flag
13643 is specified. Fixes issue 4664. Patch from Onizuka.
13644 - Replace all calls to snprintf() outside of src/ext with
13645 tor_snprintf(). Also remove the #define to replace snprintf with
13646 _snprintf on Windows; they have different semantics, and all of
13647 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
13648 - Try to detect if we are ever building on a platform where
13649 memset(...,0,...) does not set the value of a double to 0.0. Such
13650 platforms are permitted by the C standard, though in practice
13651 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
13652 currently support them, but it's better to detect them and fail
13653 than to perform erroneously.
13655 o Removed features:
13656 - Stop exporting estimates of v2 and v3 directory traffic shares
13657 in extrainfo documents. They were unneeded and sometimes inaccurate.
13658 Also stop exporting any v2 directory request statistics. Resolves
13660 - Drop support for detecting and warning about versions of Libevent
13661 before 1.3e. Nothing reasonable ships with them any longer;
13662 warning the user about them shouldn't be needed. Resolves ticket
13665 o Code simplifications and refactoring:
13666 - Rename "isin" functions to "contains", for grammar. Resolves
13668 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
13669 with the natural logarithm function from the system libm. Resolves
13673 Changes in version 0.2.4.9-alpha - 2013-01-15
13674 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
13675 work more robustly.
13678 - Fix backward compatibility logic when receiving an embedded ntor
13679 handshake tunneled in a CREATE cell. This clears up the "Bug:
13680 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
13684 Changes in version 0.2.4.8-alpha - 2013-01-14
13685 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
13686 risks, adds a new stronger and faster circuit handshake, and offers
13687 stronger and faster link encryption when both sides support it.
13690 - Preliminary support for directory guards (proposal 207): when
13691 possible, clients now use their entry guards for non-anonymous
13692 directory requests. This can help prevent client enumeration. Note
13693 that this behavior only works when we have a usable consensus
13694 directory, and when options about what to download are more or less
13695 standard. In the future we should re-bootstrap from our guards,
13696 rather than re-bootstrapping from the preconfigured list of
13697 directory sources that ships with Tor. Resolves ticket 6526.
13698 - Tor relays and clients now support a better CREATE/EXTEND cell
13699 format, allowing the sender to specify multiple address, identity,
13700 and handshake types. Implements Robert Ransom's proposal 200;
13701 closes ticket 7199.
13703 o Major features (new circuit handshake):
13704 - Tor now supports a new circuit extension handshake designed by Ian
13705 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
13706 circuit extension handshake, later called "TAP", was a bit slow
13707 (especially on the relay side), had a fragile security proof, and
13708 used weaker keys than we'd now prefer. The new circuit handshake
13709 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
13710 function, making it significantly more secure than the older
13711 handshake, and significantly faster. Tor can use one of two built-in
13712 pure-C curve25519-donna implementations by Adam Langley, or it
13713 can link against the "nacl" library for a tuned version if present.
13715 The built-in version is very fast for 64-bit systems when building
13716 with GCC. The built-in 32-bit version is still faster than the
13717 old TAP protocol, but using libnacl is better on most such hosts.
13719 Clients don't currently use this protocol by default, since
13720 comparatively few clients support it so far. To try it, set
13721 UseNTorHandshake to 1.
13723 Implements proposal 216; closes ticket 7202.
13725 o Major features (better link encryption):
13726 - Relays can now enable the ECDHE TLS ciphersuites when available
13727 and appropriate. These ciphersuites let us negotiate forward-secure
13728 TLS secret keys more safely and more efficiently than with our
13729 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
13730 public relays prefer the (faster) P224 group, and bridges prefer
13731 the (more common) P256 group; you can override this with the
13734 Enabling these ciphers was a little tricky, since for a long time,
13735 clients had been claiming to support them without actually doing
13736 so, in order to foil fingerprinting. But with the client-side
13737 implementation of proposal 198 in 0.2.3.17-beta, clients can now
13738 match the ciphers from recent Firefox versions *and* list the
13739 ciphers they actually mean, so relays can believe such clients
13740 when they advertise ECDHE support in their TLS ClientHello messages.
13742 This feature requires clients running 0.2.3.17-beta or later,
13743 and requires both sides to be running OpenSSL 1.0.0 or later
13744 with ECC support. OpenSSL 1.0.1, with the compile-time option
13745 "enable-ec_nistp_64_gcc_128", is highly recommended.
13747 Implements the relay side of proposal 198; closes ticket 7200.
13750 - Avoid crashing when, as a relay without IPv6-exit support, a
13751 client insists on getting an IPv6 address or nothing. Fixes bug
13752 7814; bugfix on 0.2.4.7-alpha.
13755 - Improve circuit build timeout handling for hidden services.
13756 In particular: adjust build timeouts more accurately depending
13757 upon the number of hop-RTTs that a particular circuit type
13758 undergoes. Additionally, launch intro circuits in parallel
13759 if they timeout, and take the first one to reply as valid.
13760 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
13761 separate error codes; or at least, don't break for that reason.
13762 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
13763 - Update to the January 2 2013 Maxmind GeoLite Country database.
13765 o Minor features (testing):
13766 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
13767 (P-256) Diffie-Hellman handshakes to src/or/bench.
13768 - Add benchmark functions to test onion handshake performance.
13770 o Minor features (path bias detection):
13771 - Alter the Path Bias log messages to be more descriptive in terms
13772 of reporting timeouts and other statistics.
13773 - Create three levels of Path Bias log messages, as opposed to just
13774 two. These are configurable via consensus as well as via the torrc
13775 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
13776 The default values are 0.70, 0.50, and 0.30 respectively.
13777 - Separate the log message levels from the decision to drop guards,
13778 which also is available via torrc option PathBiasDropGuards.
13779 PathBiasDropGuards still defaults to 0 (off).
13780 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
13781 in combination with PathBiasExtremeRate.
13782 - Increase the default values for PathBiasScaleThreshold and
13783 PathBiasCircThreshold from (200, 20) to (300, 150).
13784 - Add in circuit usage accounting to path bias. If we try to use a
13785 built circuit but fail for any reason, it counts as path bias.
13786 Certain classes of circuits where the adversary gets to pick your
13787 destination node are exempt from this accounting. Usage accounting
13788 can be specifically disabled via consensus parameter or torrc.
13789 - Convert all internal path bias state to double-precision floating
13790 point, to avoid roundoff error and other issues.
13791 - Only record path bias information for circuits that have completed
13792 *two* hops. Assuming end-to-end tagging is the attack vector, this
13793 makes us more resilient to ambient circuit failure without any
13794 detection capability loss.
13796 o Minor bugfixes (log messages):
13797 - Rate-limit the "No circuits are opened. Relaxed timeout for a
13798 circuit with channel state open..." message to once per hour to
13799 keep it from filling the notice logs. Mitigates bug 7799 but does
13800 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
13801 - Avoid spurious warnings when configuring multiple client ports of
13802 which only some are nonlocal. Previously, we had claimed that some
13803 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
13806 o Code simplifications and refactoring:
13807 - Get rid of a couple of harmless clang warnings, where we compared
13808 enums to ints. These warnings are newly introduced in clang 3.2.
13809 - Split the onion.c file into separate modules for the onion queue
13810 and the different handshakes it supports.
13811 - Remove the marshalling/unmarshalling code for sending requests to
13812 cpuworkers over a socket, and instead just send structs. The
13813 recipient will always be the same Tor binary as the sender, so
13814 any encoding is overkill.
13817 Changes in version 0.2.4.7-alpha - 2012-12-24
13818 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
13819 directory mirrors for more robust bootstrapping; fixes more issues where
13820 clients with changing network conditions refuse to make any circuits;
13821 adds initial support for exiting to IPv6 addresses; resumes being able
13822 to update our GeoIP database, and includes the geoip6 file this time;
13823 turns off the client-side DNS cache by default due to privacy risks;
13824 and fixes a variety of other issues.
13826 o Major features (client resilience):
13827 - Add a new "FallbackDir" torrc option to use when we can't use
13828 a directory mirror from the consensus (either because we lack a
13829 consensus, or because they're all down). Currently, all authorities
13830 are fallbacks by default, and there are no other default fallbacks,
13831 but that will change. This option will allow us to give clients a
13832 longer list of servers to try to get a consensus from when first
13833 connecting to the Tor network, and thereby reduce load on the
13834 directory authorities. Implements proposal 206, "Preconfigured
13835 directory sources for bootstrapping". We also removed the old
13836 "FallbackNetworkstatus" option, since we never got it working well
13837 enough to use it. Closes bug 572.
13838 - If we have no circuits open, use a relaxed timeout (the
13839 95-percentile cutoff) until a circuit succeeds. This heuristic
13840 should allow Tor to succeed at building circuits even when the
13841 network connection drastically changes. Should help with bug 3443.
13843 o Major features (IPv6):
13844 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
13845 connectivity, then set the IPv6Exit flag to 1. Also make sure your
13846 exit policy reads as you would like: the address * applies to all
13847 address families, whereas *4 is IPv4 address only, and *6 is IPv6
13848 addresses only. On the client side, you'll need to wait until the
13849 authorities have upgraded, wait for enough exits to support IPv6,
13850 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
13851 ticket 5547, implements proposal 117 as revised in proposal 208.
13853 We DO NOT recommend that clients with actual anonymity needs start
13854 using IPv6 over Tor yet, since not enough exits support it yet.
13856 o Major features (geoip database):
13857 - Maxmind began labelling Tor relays as being in country "A1",
13858 which breaks by-country node selection inside Tor. Now we use a
13859 script to replace "A1" ("Anonymous Proxy") entries in our geoip
13860 file with real country codes. This script fixes about 90% of "A1"
13861 entries automatically and uses manual country code assignments to
13862 fix the remaining 10%. See src/config/README.geoip for details.
13863 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
13864 Country database, as modified above.
13866 o Major bugfixes (client-side DNS):
13867 - Turn off the client-side DNS cache by default. Updating and using
13868 the DNS cache is now configurable on a per-client-port
13869 level. SOCKSPort, DNSPort, etc lines may now contain
13870 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
13871 cache these types of DNS answers when we receive them from an
13872 exit node in response to an application request on this port, and
13873 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
13874 cached DNS answers of these types, we shouldn't use them. It's
13875 potentially risky to use cached DNS answers at the client, since
13876 doing so can indicate to one exit what answers we've gotten
13877 for DNS lookups in the past. With IPv6, this becomes especially
13878 problematic. Using cached DNS answers for requests on the same
13879 circuit would present less linkability risk, since all traffic
13880 on a circuit is already linkable, but it would also provide
13881 little performance benefit: the exit node caches DNS replies
13882 too. Implements a simplified version of Proposal 205. Implements
13885 o Major bugfixes (other):
13886 - Alter circuit build timeout measurement to start at the point
13887 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
13888 initialization). This should make our timeout measurements more
13889 uniform. Previously, we were sometimes including ORconn setup time
13890 in our circuit build time measurements. Should resolve bug 3443.
13891 - Fix an assertion that could trigger in hibernate_go_dormant() when
13892 closing an or_connection_t: call channel_mark_for_close() rather
13893 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
13895 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
13896 7655; bugfix on 0.2.4.6-alpha.
13899 - Add a new torrc option "ServerTransportListenAddr" to let bridge
13900 operators select the address where their pluggable transports will
13901 listen for connections. Resolves ticket 7013.
13902 - Allow an optional $ before the node identity digest in the
13903 controller command GETINFO ns/id/<identity>, for consistency with
13904 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
13905 - Log packaged cell fullness as part of the heartbeat message.
13906 Diagnosis to try to determine the extent of bug 7743.
13908 o Minor features (IPv6):
13909 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
13910 prefer to hand out virtual IPv6 addresses, since there are more of
13911 them and we can't run out. To override this behavior and make IPv4
13912 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
13913 or DNSPort you're using for resolving. Implements ticket 7571.
13914 - AutomapHostsOnResolve responses are now randomized, to avoid
13915 annoying situations where Tor is restarted and applications
13916 connect to the wrong addresses.
13917 - Never try more than 1000 times to pick a new virtual address when
13918 AutomapHostsOnResolve is set. That's good enough so long as we
13919 aren't close to handing out our entire virtual address space;
13920 if you're getting there, it's best to switch to IPv6 virtual
13924 - The ADDRMAP command can no longer generate an ill-formed error
13925 code on a failed MAPADDRESS. It now says "internal" rather than
13926 an English sentence fragment with spaces in the middle. Bugfix on
13927 Tor 0.2.0.19-alpha.
13928 - Fix log messages and comments to avoid saying "GMT" when we mean
13929 "UTC". Fixes bug 6113.
13930 - Compile on win64 using mingw64. Fixes bug 7260; patches from
13932 - Fix a crash when debugging unit tests on Windows: deallocate a
13933 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
13934 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
13937 - The DirServer option is now DirAuthority, for consistency with
13938 current naming patterns. You can still use the old DirServer form.
13940 o Code simplification and refactoring:
13941 - Move the client-side address-map/virtual-address/DNS-cache code
13942 out of connection_edge.c into a new addressmap.c module.
13943 - Remove unused code for parsing v1 directories and "running routers"
13944 documents. Fixes bug 6887.
13947 Changes in version 0.2.3.25 - 2012-11-19
13948 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
13949 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
13950 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
13951 programmer, and friend. Unstinting in his dedication to the cause of
13952 freedom, he inspired and helped many of us as we began our work on
13953 anonymity, and inspires us still. Please honor his memory by writing
13954 software to protect people's freedoms, and by helping others to do so.
13956 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
13957 significantly reduced directory overhead (via microdescriptors),
13958 enormous crypto performance improvements for fast relays on new
13959 enough hardware, a new v3 TLS handshake protocol that can better
13960 resist fingerprinting, support for protocol obfuscation plugins (aka
13961 pluggable transports), better scalability for hidden services, IPv6
13962 support for bridges, performance improvements like allowing clients
13963 to skip the first round-trip on the circuit ("optimistic data") and
13964 refilling token buckets more often, a new "stream isolation" design
13965 to isolate different applications on different circuits, and many
13966 stability, security, and privacy fixes.
13969 - Tor tries to wipe potentially sensitive data after using it, so
13970 that if some subsequent security failure exposes Tor's memory,
13971 the damage will be limited. But we had a bug where the compiler
13972 was eliminating these wipe operations when it decided that the
13973 memory was no longer visible to a (correctly running) program,
13974 hence defeating our attempt at defense in depth. We fix that
13975 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
13976 is unlikely to optimize away. Future versions of Tor may use
13977 a less ridiculously heavy approach for this. Fixes bug 7352.
13978 Reported in an article by Andrey Karpov.
13981 - Fix a harmless bug when opting against publishing a relay descriptor
13982 because DisableNetwork is set. Fixes bug 7464; bugfix on
13986 Changes in version 0.2.4.6-alpha - 2012-11-13
13987 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
13988 makes our defense-in-depth memory wiping more reliable, and begins to
13989 count IPv6 addresses in bridge statistics,
13992 - Fix an assertion failure that could occur when closing a connection
13993 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
13995 - Tor tries to wipe potentially sensitive data after using it, so
13996 that if some subsequent security failure exposes Tor's memory,
13997 the damage will be limited. But we had a bug where the compiler
13998 was eliminating these wipe operations when it decided that the
13999 memory was no longer visible to a (correctly running) program,
14000 hence defeating our attempt at defense in depth. We fix that
14001 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
14002 is unlikely to optimize away. Future versions of Tor may use
14003 a less ridiculously heavy approach for this. Fixes bug 7352.
14004 Reported in an article by Andrey Karpov.
14007 - Add GeoIP database for IPv6 addresses. The new config option
14009 - Bridge statistics now count bridge clients connecting over IPv6:
14010 bridge statistics files now list "bridge-ip-versions" and
14011 extra-info documents list "geoip6-db-digest". The control protocol
14012 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
14013 implementation by "shkoo", addressing ticket 5055.
14016 - Warn when we are binding low ports when hibernation is enabled;
14017 previously we had warned when we were _advertising_ low ports with
14018 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
14019 - Fix a harmless bug when opting against publishing a relay descriptor
14020 because DisableNetwork is set. Fixes bug 7464; bugfix on
14022 - Add warning message when a managed proxy dies during configuration.
14023 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
14024 - Fix a linking error when building tor-fw-helper without miniupnp.
14025 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
14026 - Check for closing an or_connection_t without going through correct
14027 channel functions; emit a warning and then call
14028 connection_or_close_for_error() so we don't assert as in bugs 7212
14030 - Compile correctly on compilers without C99 designated initializer
14031 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
14032 - Avoid a possible assert that can occur when channel_send_destroy() is
14033 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
14034 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
14035 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
14036 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
14037 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
14039 o Code simplification and refactoring:
14040 - Start using OpenBSD's implementation of queue.h, so that we don't
14041 need to hand-roll our own pointer and list structures whenever we
14042 need them. (We can't rely on a sys/queue.h, since some operating
14043 systems don't have them, and the ones that do have them don't all
14044 present the same extensions.)
14047 Changes in version 0.2.4.5-alpha - 2012-10-25
14048 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
14049 two important security vulnerabilities that could lead to remotely
14050 triggerable relay crashes, fix a major bug that was preventing clients
14051 from choosing suitable exit nodes, and refactor some of our code.
14053 o Major bugfixes (security, also in 0.2.3.24-rc):
14054 - Fix a group of remotely triggerable assertion failures related to
14055 incorrect link protocol negotiation. Found, diagnosed, and fixed
14056 by "some guy from France". Fix for CVE-2012-2250; bugfix on
14058 - Fix a denial of service attack by which any directory authority
14059 could crash all the others, or by which a single v2 directory
14060 authority could crash everybody downloading v2 directory
14061 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
14063 o Major bugfixes (also in 0.2.3.24-rc):
14064 - When parsing exit policy summaries from microdescriptors, we had
14065 previously been ignoring the last character in each one, so that
14066 "accept 80,443,8080" would be treated by clients as indicating
14067 a node that allows access to ports 80, 443, and 808. That would
14068 lead to clients attempting connections that could never work,
14069 and ignoring exit nodes that would support their connections. Now
14070 clients parse these exit policy summaries correctly. Fixes bug 7192;
14071 bugfix on 0.2.3.1-alpha.
14073 o Minor bugfixes (also in 0.2.3.24-rc):
14074 - Clients now consider the ClientRejectInternalAddresses config option
14075 when using a microdescriptor consensus stanza to decide whether
14076 an exit relay would allow exiting to an internal address. Fixes
14077 bug 7190; bugfix on 0.2.3.1-alpha.
14080 - Only disable TLS session ticket support when running as a TLS
14081 server. Now clients will blend better with regular Firefox
14082 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
14084 o Code simplification and refactoring:
14085 - Start using OpenBSD's implementation of queue.h (originally by
14087 - Move the entry node code from circuitbuild.c to its own file.
14088 - Move the circuit build timeout tracking code from circuitbuild.c
14092 Changes in version 0.2.3.24-rc - 2012-10-25
14093 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
14094 could lead to remotely triggerable relay crashes, and fixes
14095 a major bug that was preventing clients from choosing suitable exit
14098 o Major bugfixes (security):
14099 - Fix a group of remotely triggerable assertion failures related to
14100 incorrect link protocol negotiation. Found, diagnosed, and fixed
14101 by "some guy from France". Fix for CVE-2012-2250; bugfix on
14103 - Fix a denial of service attack by which any directory authority
14104 could crash all the others, or by which a single v2 directory
14105 authority could crash everybody downloading v2 directory
14106 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
14109 - When parsing exit policy summaries from microdescriptors, we had
14110 previously been ignoring the last character in each one, so that
14111 "accept 80,443,8080" would be treated by clients as indicating
14112 a node that allows access to ports 80, 443, and 808. That would
14113 lead to clients attempting connections that could never work,
14114 and ignoring exit nodes that would support their connections. Now
14115 clients parse these exit policy summaries correctly. Fixes bug 7192;
14116 bugfix on 0.2.3.1-alpha.
14119 - Clients now consider the ClientRejectInternalAddresses config option
14120 when using a microdescriptor consensus stanza to decide whether
14121 an exit relay would allow exiting to an internal address. Fixes
14122 bug 7190; bugfix on 0.2.3.1-alpha.
14125 Changes in version 0.2.4.4-alpha - 2012-10-20
14126 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
14127 vulnerability introduced by a change in OpenSSL, fixes a remotely
14128 triggerable assert, and adds new channel_t and circuitmux_t abstractions
14129 that will make it easier to test new connection transport and cell
14130 scheduling algorithms.
14132 o New directory authorities (also in 0.2.3.23-rc):
14133 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
14134 authority. Closes ticket 5749.
14136 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
14137 - Disable TLS session tickets. OpenSSL's implementation was giving
14138 our TLS session keys the lifetime of our TLS context objects, when
14139 perfect forward secrecy would want us to discard anything that
14140 could decrypt a link connection as soon as the link connection
14141 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
14142 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
14143 - Discard extraneous renegotiation attempts once the V3 link
14144 protocol has been initiated. Failure to do so left us open to
14145 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
14146 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
14148 o Internal abstraction features:
14149 - Introduce new channel_t abstraction between circuits and
14150 or_connection_t to allow for implementing alternate OR-to-OR
14151 transports. A channel_t is an abstract object which can either be a
14152 cell-bearing channel, which is responsible for authenticating and
14153 handshaking with the remote OR and transmitting cells to and from
14154 it, or a listening channel, which spawns new cell-bearing channels
14155 at the request of remote ORs. Implements part of ticket 6465.
14156 - Also new is the channel_tls_t subclass of channel_t, adapting it
14157 to the existing or_connection_t code. The V2/V3 protocol handshaking
14158 code which formerly resided in command.c has been moved below the
14159 channel_t abstraction layer and may be found in channeltls.c now.
14160 Implements the rest of ticket 6465.
14161 - Introduce new circuitmux_t storing the queue of circuits for
14162 a channel; this encapsulates and abstracts the queue logic and
14163 circuit selection policy, and allows the latter to be overridden
14164 easily by switching out a policy object. The existing EWMA behavior
14165 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
14167 o Required libraries:
14168 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
14169 strongly recommended.
14172 - Warn users who run hidden services on a Tor client with
14173 UseEntryGuards disabled that their hidden services will be
14174 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
14175 attack which motivated Tor to support entry guards in the first
14176 place). Resolves ticket 6889.
14177 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
14178 dhill. Resolves ticket 6982.
14179 - Option OutboundBindAddress can be specified multiple times and
14180 accepts IPv6 addresses. Resolves ticket 6876.
14182 o Minor bugfixes (also in 0.2.3.23-rc):
14183 - Don't serve or accept v2 hidden service descriptors over a
14184 relay's DirPort. It's never correct to do so, and disabling it
14185 might make it more annoying to exploit any bugs that turn up in the
14186 descriptor-parsing code. Fixes bug 7149.
14187 - Fix two cases in src/or/transports.c where we were calling
14188 fmt_addr() twice in a parameter list. Bug found by David
14189 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
14190 - Fix memory leaks whenever we logged any message about the "path
14191 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
14192 - When relays refuse a "create" cell because their queue of pending
14193 create cells is too big (typically because their cpu can't keep up
14194 with the arrival rate), send back reason "resource limit" rather
14195 than reason "internal", so network measurement scripts can get a
14196 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
14199 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
14200 - Free some more still-in-use memory at exit, to make hunting for
14201 memory leaks easier. Resolves bug 7029.
14202 - When a Tor client gets a "truncated" relay cell, the first byte of
14203 its payload specifies why the circuit was truncated. We were
14204 ignoring this 'reason' byte when tearing down the circuit, resulting
14205 in the controller not being told why the circuit closed. Now we
14206 pass the reason from the truncated cell to the controller. Bugfix
14207 on 0.1.2.3-alpha; fixes bug 7039.
14208 - Downgrade "Failed to hand off onionskin" messages to "debug"
14209 severity, since they're typically redundant with the "Your computer
14210 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
14211 - Make clients running with IPv6 bridges connect over IPv6 again,
14212 even without setting new config options ClientUseIPv6 and
14213 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
14214 - Use square brackets around IPv6 addresses in numerous places
14215 that needed them, including log messages, HTTPS CONNECT proxy
14216 requests, TransportProxy statefile entries, and pluggable transport
14217 extra-info lines. Fixes bug 7011; patch by David Fifield.
14219 o Code refactoring and cleanup:
14220 - Source files taken from other packages now reside in src/ext;
14221 previously they were scattered around the rest of Tor.
14222 - Avoid use of reserved identifiers in our C code. The C standard
14223 doesn't like us declaring anything that starts with an
14224 underscore, so let's knock it off before we get in trouble. Fix
14225 for bug 1031; bugfix on the first Tor commit.
14228 Changes in version 0.2.3.23-rc - 2012-10-20
14229 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
14230 vulnerability introduced by a change in OpenSSL, and fixes a variety
14231 of smaller bugs in preparation for the release.
14233 o New directory authorities:
14234 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
14235 authority. Closes ticket 5749.
14237 o Major bugfixes (security/privacy):
14238 - Disable TLS session tickets. OpenSSL's implementation was giving
14239 our TLS session keys the lifetime of our TLS context objects, when
14240 perfect forward secrecy would want us to discard anything that
14241 could decrypt a link connection as soon as the link connection
14242 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
14243 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
14244 - Discard extraneous renegotiation attempts once the V3 link
14245 protocol has been initiated. Failure to do so left us open to
14246 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
14247 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
14250 - Fix a possible crash bug when checking for deactivated circuits
14251 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
14252 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
14254 o Minor bugfixes (on 0.2.3.x):
14255 - Fix two cases in src/or/transports.c where we were calling
14256 fmt_addr() twice in a parameter list. Bug found by David
14257 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
14258 - Convert an assert in the pathbias code to a log message. The assert
14259 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
14260 bugfix on 0.2.3.17-beta.
14261 - Fix memory leaks whenever we logged any message about the "path
14262 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
14264 o Minor bugfixes (on 0.2.2.x and earlier):
14265 - Don't serve or accept v2 hidden service descriptors over a relay's
14266 DirPort. It's never correct to do so, and disabling it might
14267 make it more annoying to exploit any bugs that turn up in the
14268 descriptor-parsing code. Fixes bug 7149.
14269 - When relays refuse a "create" cell because their queue of pending
14270 create cells is too big (typically because their cpu can't keep up
14271 with the arrival rate), send back reason "resource limit" rather
14272 than reason "internal", so network measurement scripts can get a
14273 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
14274 - Correct file sizes when reading binary files on Cygwin, to avoid
14275 a bug where Tor would fail to read its state file. Fixes bug 6844;
14276 bugfix on 0.1.2.7-alpha.
14277 - Avoid undefined behavior when parsing the list of supported
14278 rendezvous/introduction protocols in a hidden service descriptor.
14279 Previously, Tor would have confused (as-yet-unused) protocol version
14280 numbers greater than 32 with lower ones on many platforms. Fixes
14281 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
14283 o Documentation fixes:
14284 - Clarify that hidden services are TCP only. Fixes bug 6024.
14287 Changes in version 0.2.4.3-alpha - 2012-09-22
14288 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
14289 assertion, resumes letting relays test reachability of their DirPort,
14290 and cleans up a bunch of smaller bugs.
14293 - Fix an assertion failure in tor_timegm() that could be triggered
14294 by a badly formatted directory object. Bug found by fuzzing with
14295 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
14298 - Fix a possible crash bug when checking for deactivated circuits
14299 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
14300 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
14301 - Allow routers to detect that their own DirPorts are running. When
14302 we removed support for versions_supports_begindir, we also
14303 accidentally removed the mechanism we used to self-test our
14304 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
14305 bugfix on 0.2.4.2-alpha.
14307 o Security features:
14308 - Switch to a completely time-invariant approach for picking nodes
14309 weighted by bandwidth. Our old approach would run through the
14310 part of the loop after it had made its choice slightly slower
14311 than it ran through the part of the loop before it had made its
14312 choice. Addresses ticket 6538.
14313 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
14314 by tor2web clients allows hidden services to identify tor2web
14315 clients through their repeated selection of the same rendezvous
14316 and introduction point circuit endpoints (their guards). Resolves
14320 - Enable Tor to read configuration, state, and key information from
14321 a FIFO. Previously Tor would only read from files with a positive
14322 stat.st_size. Code from meejah; fixes bug 6044.
14325 - Correct file sizes when reading binary files on Cygwin, to avoid
14326 a bug where Tor would fail to read its state file. Fixes bug 6844;
14327 bugfix on 0.1.2.7-alpha.
14328 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
14329 bugfix on 0.2.0.3-alpha.
14330 - When complaining about a client port on a public address, log
14331 which address we're complaining about. Fixes bug 4020; bugfix on
14332 0.2.3.3-alpha. Patch by Tom Fitzhenry.
14333 - Convert an assert in the pathbias code to a log message. The assert
14334 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
14335 bugfix on 0.2.3.17-beta.
14336 - Our new buildsystem was overzealous about rebuilding manpages: it
14337 would rebuild them all whenever any one of them changed. Now our
14338 dependency checking should be correct. Fixes bug 6843; bugfix on
14340 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
14341 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
14342 - Correct log printout about which address family is preferred
14343 when connecting to a bridge with both an IPv4 and IPv6 OR port.
14344 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
14346 o Minor bugfixes (code cleanliness):
14347 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
14348 with large values. This situation was untriggered, but nevertheless
14349 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
14350 - Reject consensus votes with more than 64 known-flags. We aren't even
14351 close to that limit yet, and our code doesn't handle it correctly.
14352 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
14353 - Avoid undefined behavior when parsing the list of supported
14354 rendezvous/introduction protocols in a hidden service descriptor.
14355 Previously, Tor would have confused (as-yet-unused) protocol version
14356 numbers greater than 32 with lower ones on many platforms. Fixes
14357 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
14358 - Fix handling of rendezvous client authorization types over 8.
14359 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
14360 - Fix building with older versions of GCC (2.95, for one) that don't
14361 like preprocessor directives inside macro arguments. Found by
14362 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
14363 - Switch weighted node selection rule from using a list of doubles
14364 to using a list of int64_t. This change should make the process
14365 slightly easier to debug and maintain. Needed to finish ticket 6538.
14367 o Code simplification and refactoring:
14368 - Move the generic "config" code into a new file, and have "config.c"
14369 hold only torrc- and state-related code. Resolves ticket 6823.
14370 - Move the core of our "choose a weighted element at random" logic
14371 into its own function, and give it unit tests. Now the logic is
14372 testable, and a little less fragile too.
14373 - Removed the testing_since field of node_t, which hasn't been used
14374 for anything since 0.2.0.9-alpha.
14376 o Documentation fixes:
14377 - Clarify that hidden services are TCP only. Fixes bug 6024.
14378 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
14382 Changes in version 0.2.3.22-rc - 2012-09-11
14383 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
14387 - Fix an assertion failure in tor_timegm() that could be triggered
14388 by a badly formatted directory object. Bug found by fuzzing with
14389 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
14392 - Avoid segfault when starting up having run with an extremely old
14393 version of Tor and parsing its state file. Fixes bug 6801; bugfix
14397 Changes in version 0.2.2.39 - 2012-09-11
14398 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
14402 - Fix an assertion failure in tor_timegm() that could be triggered
14403 by a badly formatted directory object. Bug found by fuzzing with
14404 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
14405 - Do not crash when comparing an address with port value 0 to an
14406 address policy. This bug could have been used to cause a remote
14407 assertion failure by or against directory authorities, or to
14408 allow some applications to crash clients. Fixes bug 6690; bugfix
14412 Changes in version 0.2.4.2-alpha - 2012-09-10
14413 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
14414 raises the default rate limiting even more, and makes the bootstrapping
14415 log messages less noisy.
14418 - Automatically forward the TCP ports of pluggable transport
14419 proxies using tor-fw-helper if PortForwarding is enabled. Implements
14423 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
14424 to 1GB/1GB. The previous defaults were intended to be "basically
14425 infinite", but it turns out they're now limiting our 100mbit+
14426 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
14427 last time we raised it).
14430 - Detect when we're running with a version of OpenSSL other than the
14431 one we compiled with. This has occasionally given people hard-to-
14433 - Log fewer lines at level "notice" about our OpenSSL and Libevent
14434 versions and capabilities when everything is going right. Resolves
14435 part of ticket 6736.
14436 - Directory authorities no long accept descriptors for any version of
14437 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
14438 These versions are insecure, unsupported, or both. Implements
14442 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
14443 to start with a triple-underscore so the controller won't touch it.
14444 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
14445 - Avoid segfault when starting up having run with an extremely old
14446 version of Tor and parsing its state file. Fixes bug 6801; bugfix
14448 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
14449 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
14450 - Don't follow the NULL pointer if microdescriptor generation fails.
14451 (This does not appear to be triggerable, but it's best to be safe.)
14452 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
14453 - Fix mis-declared dependencies on src/common/crypto.c and
14454 src/or/tor_main.c that could break out-of-tree builds under some
14455 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
14456 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
14457 6778; bugfix on 0.2.4.1-alpha.
14458 - Fix a harmless (in this case) build warning for implicitly
14459 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
14461 o Removed features:
14462 - Now that all versions before 0.2.2.x are disallowed, we no longer
14463 need to work around their missing features. Thus we can remove a
14464 bunch of compatibility code.
14466 o Code refactoring:
14467 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
14468 TCP ports to forward. In the past it only accepted two ports:
14469 the ORPort and the DirPort.
14472 Changes in version 0.2.4.1-alpha - 2012-09-05
14473 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
14474 bridgedb; lets relays use IPv6 addresses and directory authorities
14475 advertise them; and switches to a cleaner build interface.
14477 This is the first alpha release in a new series, so expect there to
14478 be bugs. Users who would rather test out a more stable branch should
14479 stay with 0.2.3.x for now.
14481 o Major features (bridges):
14482 - Bridges now report the pluggable transports they support to the
14483 bridge authority, so it can pass the supported transports on to
14484 bridgedb and/or eventually do reachability testing. Implements
14487 o Major features (IPv6):
14488 - Bridge authorities now accept IPv6 bridge addresses and include
14489 them in network status documents. Implements ticket 5534.
14490 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
14491 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
14492 to happen. Implements ticket 5535.
14493 - All kind of relays, not just bridges, can now advertise an IPv6
14494 OR port. Implements ticket 6362.
14495 - Directory authorities vote on IPv6 OR ports using the new consensus
14496 method 14. Implements ticket 6363.
14498 o Major features (build):
14499 - Switch to a nonrecursive Makefile structure. Now instead of each
14500 Makefile.am invoking other Makefile.am's, there is a master
14501 Makefile.am that includes the others. This change makes our build
14502 process slightly more maintainable, and improves parallelism for
14503 building with make -j. Original patch by Stewart Smith; various
14504 fixes by Jim Meyering.
14505 - Where available, we now use automake's "silent" make rules by
14506 default, so that warnings are easier to spot. You can get the old
14507 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
14509 o Minor features (code security and spec conformance):
14510 - Clear keys and key-derived material left on the stack in
14511 rendservice.c and rendclient.c. Check return value of
14512 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
14513 These fixes should make us more forward-secure against cold-boot
14514 attacks and the like. Fixes bug 2385.
14515 - Reject EXTEND cells sent to nonexistent streams. According to the
14516 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
14517 we were only checking for stream IDs that were currently in use.
14518 Found while hunting for more instances of bug 6271. Bugfix on
14519 0.0.2pre8, which introduced incremental circuit construction.
14521 o Minor features (streamlining);
14522 - No longer include the "opt" prefix when generating routerinfos
14523 or v2 directories: it has been needless since Tor 0.1.2. Closes
14525 - Remove some now-needless code that tried to aggressively flush
14526 OR connections as data was added to them. Since 0.2.0.1-alpha, our
14527 cell queue logic has saved us from the failure mode that this code
14528 was supposed to prevent. Removing this code will limit the number
14529 of baroque control flow paths through Tor's network logic. Reported
14530 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
14532 o Minor features (controller):
14533 - Add a "GETINFO signal/names" control port command. Implements
14535 - Provide default values for all options via "GETINFO config/defaults".
14536 Implements ticket 4971.
14538 o Minor features (IPv6):
14539 - New config option "AuthDirHasIPv6Connectivity 1" that directory
14540 authorities should set if they have IPv6 connectivity and want to
14541 do reachability tests for IPv6 relays. Implements feature 5974.
14542 - A relay with an IPv6 OR port now sends that address in NETINFO
14543 cells (in addition to its other address). Implements ticket 6364.
14545 o Minor features (log messages):
14546 - Omit the first heartbeat log message, because it never has anything
14547 useful to say, and it clutters up the bootstrapping messages.
14548 Resolves ticket 6758.
14549 - Don't log about reloading the microdescriptor cache at startup. Our
14550 bootstrap warnings are supposed to tell the user when there's a
14551 problem, and our bootstrap notices say when there isn't. Resolves
14552 ticket 6759; bugfix on 0.2.2.6-alpha.
14553 - Don't log "I learned some more directory information" when we're
14554 reading cached directory information. Reserve it for when new
14555 directory information arrives in response to a fetch. Resolves
14557 - Prevent rounding error in path bias counts when scaling
14558 them down, and use the correct scale factor default. Also demote
14559 some path bias related log messages down a level and make others
14560 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
14561 - We no longer warn so much when generating manpages from their
14564 o Code simplifications and refactoring:
14565 - Enhance our internal sscanf replacement so that we can eliminate
14566 the last remaining uses of the system sscanf. (Though those uses
14567 of sscanf were safe, sscanf itself is generally error prone, so
14568 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
14570 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
14571 - Move last_reachable and testing_since from routerinfo_t to node_t.
14572 Implements ticket 5529.
14573 - Add replaycache_t structure, functions and unit tests, then refactor
14574 rend_service_introduce() to be more clear to read, improve, debug,
14575 and test. Resolves bug 6177.
14576 - Finally remove support for malloc_good_size and malloc_usable_size.
14577 We had hoped that these functions would let us eke a little more
14578 memory out of our malloc implementation. Unfortunately, the only
14579 implementations that provided these functions are also ones that
14580 are already efficient about not overallocation: they never got us
14581 more than 7 or so bytes per allocation. Removing them saves us a
14582 little code complexity and a nontrivial amount of build complexity.
14584 o New requirements:
14585 - Tor maintainers now require Automake version 1.9 or later to build
14586 Tor from the Git repository. (Automake is not required when building
14587 from a source distribution.)
14590 Changes in version 0.2.3.21-rc - 2012-09-05
14591 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
14592 series. It fixes a trio of potential security bugs, fixes a bug where
14593 we were leaving some of the fast relays out of the microdescriptor
14594 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
14595 and cleans up other smaller issues.
14597 o Major bugfixes (security):
14598 - Tear down the circuit if we get an unexpected SENDME cell. Clients
14599 could use this trick to make their circuits receive cells faster
14600 than our flow control would have allowed, or to gum up the network,
14601 or possibly to do targeted memory denial-of-service attacks on
14602 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
14603 from July 2002, before the release of Tor 0.0.0. We had committed
14604 this patch previously, but we had to revert it because of bug 6271.
14605 Now that 6271 is fixed, this patch appears to work.
14606 - Reject any attempt to extend to an internal address. Without
14607 this fix, a router could be used to probe addresses on an internal
14608 network to see whether they were accepting connections. Fixes bug
14609 6710; bugfix on 0.0.8pre1.
14610 - Do not crash when comparing an address with port value 0 to an
14611 address policy. This bug could have been used to cause a remote
14612 assertion failure by or against directory authorities, or to
14613 allow some applications to crash clients. Fixes bug 6690; bugfix
14617 - Remove the upper bound on microdescriptor length. We were hitting
14618 the limit for routers with complex exit policies or family
14619 declarations, causing clients to not use them. Fixes the first
14620 piece of bug 6404; fix on 0.2.2.6-alpha.
14621 - Detect "ORPort 0" as meaning, uniformly, that we're not running
14622 as a relay. Previously, some of our code would treat the presence
14623 of any ORPort line as meaning that we should act like a relay,
14624 even though our new listener code would correctly not open any
14625 ORPorts for ORPort 0. Similar bugs in other Port options are also
14626 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
14629 - Avoid a pair of double-free and use-after-mark bugs that can
14630 occur with certain timings in canceled and re-received DNS
14631 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
14632 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
14633 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
14634 - Allow one-hop directory fetching circuits the full "circuit build
14635 timeout" period, rather than just half of it, before failing them
14636 and marking the relay down. This fix should help reduce cases where
14637 clients declare relays (or worse, bridges) unreachable because
14638 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
14639 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
14641 - Authorities no longer include any router in their microdescriptor
14642 consensuses for which they couldn't generate or agree on a
14643 microdescriptor. Fixes the second piece of bug 6404; fix on
14645 - Detect and reject attempts to specify both "FooPort" and
14646 "FooPort 0" in the same configuration domain. (It's still okay
14647 to have a FooPort in your configuration file, and use "FooPort 0"
14648 on the command line to disable it.) Fixes the second half of bug
14649 6507; bugfix on 0.2.3.3-alpha.
14650 - Make wildcarded addresses (that is, ones beginning with "*.") work
14651 when provided via the controller's MapAddress command. Previously,
14652 they were accepted, but we never actually noticed that they were
14653 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
14654 - Avoid crashing on a malformed state file where EntryGuardPathBias
14655 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
14656 - Add a (probably redundant) memory clear between iterations of
14657 the router status voting loop, to prevent future coding errors
14658 where data might leak between iterations of the loop. Resolves
14661 o Minor bugfixes (log messages):
14662 - Downgrade "set buildtimeout to low value" messages to "info"
14663 severity; they were never an actual problem, there was never
14664 anything reasonable to do about them, and they tended to spam logs
14665 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
14666 - Downgrade path-bias warning messages to "info". We'll try to get
14667 them working better in 0.2.4. Add internal circuit construction
14668 state to protect against the noisy warn message "Unexpectedly high
14669 circuit_successes". Also add some additional rate-limited notice
14670 messages to help determine the root cause of the warn. Fixes bug
14671 6475. Bugfix against 0.2.3.17-beta.
14672 - Move log message when unable to find a microdesc in a routerstatus
14673 entry to parse time. Previously we'd spam this warning every time
14674 we tried to figure out which microdescriptors to download. Fixes
14675 the third piece of bug 6404; fix on 0.2.3.18-rc.
14678 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
14679 change when the authority is deciding whether to accept a newly
14680 uploaded descriptor. Implements ticket 6423.
14681 - Add missing documentation for consensus and microdesc files.
14682 Resolves ticket 6732.
14685 Changes in version 0.2.2.38 - 2012-08-12
14686 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
14687 attack that could in theory leak path information.
14690 - Avoid an uninitialized memory read when reading a vote or consensus
14691 document that has an unrecognized flavor name. This read could
14692 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
14693 - Try to leak less information about what relays a client is
14694 choosing to a side-channel attacker. Previously, a Tor client would
14695 stop iterating through the list of available relays as soon as it
14696 had chosen one, thus finishing a little earlier when it picked
14697 a router earlier in the list. If an attacker can recover this
14698 timing information (nontrivial but not proven to be impossible),
14699 they could learn some coarse-grained information about which relays
14700 a client was picking (middle nodes in particular are likelier to
14701 be affected than exits). The timing attack might be mitigated by
14702 other factors (see bug 6537 for some discussion), but it's best
14703 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
14706 Changes in version 0.2.3.20-rc - 2012-08-05
14707 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
14708 series. It fixes a pair of code security bugs and a potential anonymity
14709 issue, updates our RPM spec files, and cleans up other smaller issues.
14712 - Avoid read-from-freed-memory and double-free bugs that could occur
14713 when a DNS request fails while launching it. Fixes bug 6480;
14714 bugfix on 0.2.0.1-alpha.
14715 - Avoid an uninitialized memory read when reading a vote or consensus
14716 document that has an unrecognized flavor name. This read could
14717 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
14718 - Try to leak less information about what relays a client is
14719 choosing to a side-channel attacker. Previously, a Tor client would
14720 stop iterating through the list of available relays as soon as it
14721 had chosen one, thus finishing a little earlier when it picked
14722 a router earlier in the list. If an attacker can recover this
14723 timing information (nontrivial but not proven to be impossible),
14724 they could learn some coarse-grained information about which relays
14725 a client was picking (middle nodes in particular are likelier to
14726 be affected than exits). The timing attack might be mitigated by
14727 other factors (see bug 6537 for some discussion), but it's best
14728 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
14731 - Try to make the warning when giving an obsolete SOCKSListenAddress
14732 a little more useful.
14733 - Terminate active server managed proxies if Tor stops being a
14734 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
14735 - Provide a better error message about possible OSX Asciidoc failure
14736 reasons. Fixes bug 6436.
14737 - Warn when Tor is configured to use accounting in a way that can
14738 link a hidden service to some other hidden service or public
14739 address. Resolves ticket 6490.
14742 - Check return value of fputs() when writing authority certificate
14743 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
14744 - Ignore ServerTransportPlugin lines when Tor is not configured as
14745 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
14746 - When disabling guards for having too high a proportion of failed
14747 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
14751 - Update our default RPM spec files to work with mock and rpmbuild
14752 on RHEL/Fedora. They have an updated set of dependencies and
14753 conflicts, a fix for an ancient typo when creating the "_tor"
14754 user, and better instructions. Thanks to Ondrej Mikle for the
14755 patch series. Fixes bug 6043.
14758 - Make it possible to set the TestingTorNetwork configuration
14759 option using AlternateDirAuthority and AlternateBridgeAuthority
14760 as an alternative to setting DirServer. Addresses ticket 6377.
14763 - Clarify the documentation for the Alternate*Authority options.
14765 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
14767 o Code simplification and refactoring:
14768 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
14769 10 lines. Also, don't nest them. Doing so in the past has
14770 led to hard-to-debug code. The new style is to use the
14771 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
14774 Changes in version 0.2.3.19-rc - 2012-07-06
14775 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
14776 series. It fixes the compile on Windows, reverts to a GeoIP database
14777 that isn't as broken, and fixes a flow control bug that has been around
14778 since the beginning of Tor.
14781 - Fix a bug handling SENDME cells on nonexistent streams that could
14782 result in bizarre window values. Report and patch contributed
14783 pseudonymously. Fixes part of bug 6271. This bug was introduced
14784 before the first Tor release, in svn commit r152.
14785 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
14786 June 2012 database, Maxmind marked many Tor relays as country "A1",
14787 which will cause risky behavior for clients that set EntryNodes
14788 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
14789 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
14790 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
14793 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
14794 bugfix on 0.2.1.10-alpha.
14797 Changes in version 0.2.3.18-rc - 2012-06-28
14798 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
14799 series. It fixes a few smaller bugs, but generally appears stable.
14800 Please test it and let us know whether it is!
14803 - Allow wildcarded mapaddress targets to be specified on the
14804 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
14805 - Make our linker option detection code more robust against linkers
14806 such as on FreeBSD 8, where a bad combination of options completes
14807 successfully but makes an unrunnable binary. Fixes bug 6173;
14808 bugfix on 0.2.3.17-beta.
14810 o Minor bugfixes (on 0.2.2.x and earlier):
14811 - Avoid a false positive in the util/threads unit test by increasing
14812 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
14813 - Replace "Sending publish request" log messages with "Launching
14814 upload", so that they no longer confusingly imply that we're
14815 sending something to a directory we might not even be connected
14816 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
14817 - Make sure to set *socket_error in all error cases in
14818 connection_connect(), so it can't produce a warning about
14819 errno being zero from errno_to_orconn_end_reason(). Bugfix on
14820 0.2.1.1-alpha; resolves ticket 6028.
14821 - Downgrade "Got a certificate, but we already have it" log messages
14822 from warning to info, except when we're a dirauth. Fixes bug 5238;
14823 bugfix on 0.2.1.7-alpha.
14824 - When checking for requested signatures on the latest consensus
14825 before serving it to a client, make sure to check the right
14826 consensus flavor. Bugfix on 0.2.2.6-alpha.
14827 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
14828 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
14830 o Minor bugfixes (on 0.2.3.x):
14831 - Make format_helper_exit_status() avoid unnecessary space padding
14832 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
14834 - Downgrade a message about cleaning the microdescriptor cache to
14835 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
14836 - Log a BUG message at severity INFO if we have a networkstatus with
14837 a missing entry for some microdescriptor. Continues on a patch
14839 - Improve the log message when a managed proxy fails to launch. Fixes
14840 bug 5099; bugfix on 0.2.3.6-alpha.
14841 - Don't do DNS lookups when parsing corrupted managed proxy protocol
14842 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
14843 - When formatting wildcarded address mappings for the controller,
14844 be sure to include "*." as appropriate. Partially fixes bug 6244;
14845 bugfix on 0.2.3.9-alpha.
14846 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
14847 Bugfix on 0.2.3.13-alpha.
14848 - Stop logging messages about running with circuit timeout learning
14849 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
14850 - Disable a spurious warning about reading on a marked and flushing
14851 connection. We shouldn't be doing that, but apparently we
14852 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
14853 - Fix a bug that stopped AllowDotExit from working on addresses
14854 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
14857 o Code simplification, refactoring, unit tests:
14858 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
14859 Libevent's notion of cached time when possible.
14860 - Remove duplicate code for invoking getrlimit() from control.c.
14861 - Add a unit test for the environment_variable_names_equal function.
14864 - Document the --defaults-torrc option, and the new (in 0.2.3)
14865 semantics for overriding, extending, and clearing lists of
14866 options. Closes bug 4748.
14869 Changes in version 0.2.3.17-beta - 2012-06-15
14870 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
14871 gets our TLS handshake back on track for being able to blend in with
14872 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
14873 with Vidalia, and otherwise continues to get us closer to a release
14877 - Enable gcc and ld hardening by default. Resolves ticket 5210.
14878 - Update TLS cipher list to match Firefox 8 and later. Resolves
14880 - Implement the client side of proposal 198: remove support for
14881 clients falsely claiming to support standard ciphersuites that
14882 they can actually provide. As of modern OpenSSL versions, it's not
14883 necessary to fake any standard ciphersuite, and doing so prevents
14884 us from using better ciphersuites in the future, since servers
14885 can't know whether an advertised ciphersuite is really supported or
14886 not. Some hosts -- notably, ones with very old versions of OpenSSL
14887 or where OpenSSL has been built with ECC disabled -- will stand
14888 out because of this change; TBB users should not be affected.
14891 - Change the default value for DynamicDHGroups (introduced in
14892 0.2.3.9-alpha) to 0. This feature can make Tor relays less
14893 identifiable by their use of the mod_ssl DH group, but at
14894 the cost of some usability (#4721) and bridge tracing (#6087)
14895 regressions. Resolves ticket 5598.
14896 - Send a CRLF at the end of each STATUS_* control protocol event. This
14897 bug tickled a bug in Vidalia which would make it freeze. Fixes
14898 bug 6094; bugfix on 0.2.3.16-alpha.
14901 - Disable writing on marked-for-close connections when they are
14902 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
14903 bug 5263; bugfix on 0.0.2pre13, where we first added a special
14904 case for flushing marked connections.
14905 - Detect SSL handshake even when the initial attempt to write the
14906 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
14907 - Change the AllowDotExit rules so they should actually work.
14908 We now enforce AllowDotExit only immediately after receiving an
14909 address via SOCKS or DNSPort: other sources are free to provide
14910 .exit addresses after the resolution occurs. Fixes bug 3940;
14911 bugfix on 0.2.2.1-alpha.
14912 - Fix a (harmless) integer overflow in cell statistics reported by
14913 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
14914 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
14915 right places and never depends on the consensus parameters or
14916 computes adaptive timeouts when it is disabled. Fixes bug 5049;
14917 bugfix on 0.2.2.14-alpha.
14918 - When building Tor on Windows with -DUNICODE (not default), ensure
14919 that error messages, filenames, and DNS server names are always
14920 NUL-terminated when we convert them to a single-byte encoding.
14921 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
14922 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
14923 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
14924 - Fix an edge case where TestingTorNetwork is set but the authorities
14925 and relays all have an uptime of zero, where the private Tor network
14926 could briefly lack support for hidden services. Fixes bug 3886;
14927 bugfix on 0.2.2.18-alpha.
14928 - Correct the manpage's descriptions for the default values of
14929 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
14931 - Fix the documentation for the --hush and --quiet command line
14932 options, which changed their behavior back in 0.2.3.3-alpha.
14933 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
14937 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
14938 more information to it, so that we can track it down in case it
14939 returns again. Mitigates bug 5235.
14940 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
14941 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
14942 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
14943 - Warn the user when HTTPProxy, but no other proxy type, is
14944 configured. This can cause surprising behavior: it doesn't send
14945 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
14946 directory traffic only. Resolves ticket 4663.
14947 - Issue a notice if a guard completes less than 40% of your circuits.
14948 Threshold is configurable by torrc option PathBiasNoticeRate and
14949 consensus parameter pb_noticepct. There is additional, off-by-
14950 default code to disable guards which fail too many circuits.
14951 Addresses ticket 5458.
14952 - Update to the June 6 2012 Maxmind GeoLite Country database.
14954 o Code simplifications and refactoring:
14955 - Remove validate_pluggable_transports_config(): its warning
14956 message is now handled by connection_or_connect().
14959 Changes in version 0.2.2.37 - 2012-06-06
14960 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
14961 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
14965 - Work around a bug in OpenSSL that broke renegotiation with TLS
14966 1.1 and TLS 1.2. Without this workaround, all attempts to speak
14967 the v2 Tor connection protocol when both sides were using OpenSSL
14968 1.0.1 would fail. Resolves ticket 6033.
14969 - When waiting for a client to renegotiate, don't allow it to add
14970 any bytes to the input buffer. This fixes a potential DoS issue.
14971 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
14972 - Fix an edge case where if we fetch or publish a hidden service
14973 descriptor, we might build a 4-hop circuit and then use that circuit
14974 for exiting afterwards -- even if the new last hop doesn't obey our
14975 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
14978 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
14979 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
14982 - Tell GCC and Clang to check for any errors in format strings passed
14983 to the tor_v*(print|scan)f functions.
14986 Changes in version 0.2.3.16-alpha - 2012-06-05
14987 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
14988 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
14989 currently). It also fixes a variety of smaller bugs and other cleanups
14990 that get us closer to a release candidate.
14992 o Major bugfixes (general):
14993 - Work around a bug in OpenSSL that broke renegotiation with TLS
14994 1.1 and TLS 1.2. Without this workaround, all attempts to speak
14995 the v2 Tor connection protocol when both sides were using OpenSSL
14996 1.0.1 would fail. Resolves ticket 6033.
14997 - When waiting for a client to renegotiate, don't allow it to add
14998 any bytes to the input buffer. This fixes a potential DoS issue.
14999 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
15000 - Pass correct OR address to managed proxies (like obfsproxy),
15001 even when ORListenAddress is used. Fixes bug 4865; bugfix on
15003 - The advertised platform of a router now includes only its operating
15004 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
15005 service pack level (for Windows) or its CPU architecture (for Unix).
15006 We also no longer include the "git-XYZ" tag in the version. Resolves
15009 o Major bugfixes (clients):
15010 - If we are unable to find any exit that supports our predicted ports,
15011 stop calling them predicted, so that we don't loop and build
15012 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
15013 which introduced predicted ports.
15014 - Fix an edge case where if we fetch or publish a hidden service
15015 descriptor, we might build a 4-hop circuit and then use that circuit
15016 for exiting afterwards -- even if the new last hop doesn't obey our
15017 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
15018 - Check at each new consensus whether our entry guards were picked
15019 long enough ago that we should rotate them. Previously, we only
15020 did this check at startup, which could lead to us holding a guard
15021 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
15022 - When fetching a bridge descriptor from a bridge authority,
15023 always do so anonymously, whether we have been able to open
15024 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
15025 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
15026 but we'll need to wait for bug 6010 before it's actually usable.
15028 o Major bugfixes (directory authorities):
15029 - When computing weight parameters, behave more robustly in the
15030 presence of a bad bwweightscale value. Previously, the authorities
15031 would crash if they agreed on a sufficiently broken weight_scale
15032 value: now, they use a reasonable default and carry on. Partial
15033 fix for 5786; bugfix on 0.2.2.17-alpha.
15034 - Check more thoroughly to prevent a rogue authority from
15035 double-voting on any consensus directory parameter. Previously,
15036 authorities would crash in this case if the total number of
15037 votes for any parameter exceeded the number of active voters,
15038 but would let it pass otherwise. Partial fix for bug 5786; bugfix
15042 - Rate-limit log messages when asked to connect anonymously to
15043 a private address. When these hit, they tended to hit fast and
15044 often. Also, don't bother trying to connect to addresses that we
15045 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
15046 reply makes us think we have been lied to, even when the address the
15047 client tried to connect to was "localhost." Resolves ticket 2822.
15048 - Allow packagers to insert an extra string in server descriptor
15049 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
15050 Resolves the rest of ticket 2988.
15051 - Raise the threshold of server descriptors needed (75%) and exit
15052 server descriptors needed (50%) before we will declare ourselves
15053 bootstrapped. This will make clients start building circuits a
15054 little later, but makes the initially constructed circuits less
15055 skewed and less in conflict with further directory fetches. Fixes
15057 - Close any connection that sends unrecognized junk before the
15058 handshake. Solves an issue noted in bug 4369.
15059 - Improve log messages about managed transports. Resolves ticket 5070.
15060 - Tag a bridge's descriptor as "never to be sent unencrypted".
15061 This shouldn't matter, since bridges don't open non-anonymous
15062 connections to the bridge authority and don't allow unencrypted
15063 directory connections from clients, but we might as well make
15064 sure. Closes bug 5139.
15065 - Expose our view of whether we have gone dormant to the controller,
15066 via a new "GETINFO dormant" value. Torbutton and other controllers
15067 can use this to avoid doing periodic requests through Tor while
15068 it's dormant (bug 4718). Fixes bug 5954.
15069 - Tell GCC and Clang to check for any errors in format strings passed
15070 to the tor_v*(print|scan)f functions.
15071 - Update to the May 1 2012 Maxmind GeoLite Country database.
15073 o Minor bugfixes (already included in 0.2.2.36):
15074 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
15075 Fixes bug 5346; bugfix on 0.0.8pre3.
15076 - Correct parsing of certain date types in parse_http_time().
15077 Without this patch, If-Modified-Since would behave
15078 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
15079 Esteban Manchado Velázques.
15080 - Make our number-parsing functions always treat too-large values
15081 as an error, even when those values exceed the width of the
15082 underlying type. Previously, if the caller provided these
15083 functions with minima or maxima set to the extreme values of the
15084 underlying integer type, these functions would return those
15085 values on overflow rather than treating overflow as an error.
15086 Fixes part of bug 5786; bugfix on 0.0.9.
15087 - If we hit the error case where routerlist_insert() replaces an
15088 existing (old) server descriptor, make sure to remove that
15089 server descriptor from the old_routers list. Fix related to bug
15090 1776. Bugfix on 0.2.2.18-alpha.
15091 - Clarify the behavior of MaxCircuitDirtiness with hidden service
15092 circuits. Fixes issue 5259.
15094 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
15095 - Prevent a null-pointer dereference when receiving a data cell
15096 for a nonexistent stream when the circuit in question has an
15097 empty deliver window. We don't believe this is triggerable,
15098 since we don't currently allow deliver windows to become empty,
15099 but the logic is tricky enough that it's better to make the code
15100 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
15101 - Fix a memory leak when trying to launch a DNS request when the
15102 network is disabled or the nameservers are unconfigurable. Fixes
15103 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
15104 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
15105 - Don't hold a Windows file handle open for every file mapping;
15106 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
15108 - Avoid O(n^2) performance characteristics when parsing a large
15109 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
15110 - Format more doubles with %f, not %lf. Patch from grarpamp to make
15111 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
15113 - Make our replacement implementation of strtok_r() compatible with
15114 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
15115 bugfix on 0.2.2.1-alpha.
15116 - Fix a NULL-pointer dereference on a badly formed
15117 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
15118 bugfix on 0.2.2.9-alpha.
15119 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
15120 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
15121 - Defensively refactor rend_mid_rendezvous() so that protocol
15122 violations and length checks happen in the beginning. Fixes
15124 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
15125 that IPv6 stuff will compile on MSVC, and compilation issues
15126 will be easier to track down. Fixes bug 5861.
15128 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
15129 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
15130 resource exhaustion, so that clients can adjust their load to
15131 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
15132 started using END_STREAM_REASON_RESOURCELIMIT.
15133 - Don't check for whether the address we're using for outbound
15134 connections has changed until after the outbound connection has
15135 completed. On Windows, getsockname() doesn't succeed until the
15136 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
15137 - If the configuration tries to set MyFamily on a bridge, refuse to
15138 do so, and warn about the security implications. Fixes bug 4657;
15139 bugfix on 0.2.0.3-alpha.
15140 - If the client fails to set a reasonable set of ciphersuites
15141 during its v2 handshake renegotiation, allow the renegotiation to
15142 continue nevertheless (i.e. send all the required certificates).
15143 Fixes bug 4591; bugfix on 0.2.0.20-rc.
15144 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
15145 option is set to 0 (which Vidalia version 0.2.16 now does when
15146 a SAVECONF attempt fails), perform other actions that SIGHUP
15147 usually causes (like reopening the logs). Fixes bug 5095; bugfix
15149 - If we fail to write a microdescriptor to the disk cache, do not
15150 continue replacing the old microdescriptor file. Fixes bug 2954;
15151 bugfix on 0.2.2.6-alpha.
15152 - Exit nodes don't need to fetch certificates for authorities that
15153 they don't recognize; only directory authorities, bridges,
15154 and caches need to do that. Fixes part of bug 2297; bugfix on
15156 - Correctly handle checking the permissions on the parent
15157 directory of a control socket in the root directory. Bug found
15158 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
15160 - When told to add a bridge with the same digest as a preexisting
15161 bridge but a different addr:port, change the addr:port as
15162 requested. Previously we would not notice the change. Fixes half
15163 of bug 5603; fix on 0.2.2.26-beta.
15164 - End AUTHCHALLENGE error messages (in the control protocol) with
15165 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
15167 o Minor bugfixes (on 0.2.3.x):
15168 - Turn an assertion (that the number of handshakes received as a
15169 server is not < 1) into a warning. Fixes bug 4873; bugfix on
15171 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
15172 we had reversed them when the answer was cached.) Fixes bug
15173 5723; bugfix on 0.2.3.1-alpha.
15174 - Work correctly on Linux systems with accept4 support advertised in
15175 their headers, but without accept4 support in the kernel. Fix
15176 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
15177 - When told to add a bridge with the same addr:port as a preexisting
15178 bridge but a different transport, change the transport as
15179 requested. Previously we would not notice the change. Fixes half
15180 of bug 5603; fix on 0.2.3.2-alpha.
15181 - Avoid a "double-reply" warning when replying to a SOCKS request
15182 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
15183 bugfix on 0.2.3.4-alpha.
15184 - Fix a bug where a bridge authority crashes if it has seen no
15185 directory requests when it's time to write statistics to disk.
15186 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
15188 - Don't try to open non-control listeners when DisableNetwork is set.
15189 Previously, we'd open all listeners, then immediately close them.
15190 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
15191 - Don't abort the managed proxy protocol if the managed proxy
15192 sends us an unrecognized line; ignore it instead. Fixes bug
15193 5910; bugfix on 0.2.3.9-alpha.
15194 - Fix a compile warning in crypto.c when compiling with clang 3.1.
15195 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
15196 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
15197 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
15198 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
15199 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
15200 - Resolve numerous small warnings and build issues with MSVC. Resolves
15203 o Documentation fixes:
15204 - Improve the manual's documentation for the NT Service command-line
15205 options. Addresses ticket 3964.
15206 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
15207 - Document the changes to the ORPort and DirPort options, and the
15208 fact that {OR/Dir}ListenAddress is now unnecessary (and
15209 therefore deprecated). Resolves ticket 5597.
15212 - Remove the torrc.bridge file: we don't use it for anything, and
15213 it had become badly desynchronized from torrc.sample. Resolves
15217 Changes in version 0.2.2.36 - 2012-05-24
15218 Tor 0.2.2.36 updates the addresses for two of the eight directory
15219 authorities, fixes some potential anonymity and security issues,
15220 and fixes several crash bugs.
15222 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
15223 known flaws, and nobody should be using them. You should upgrade. If
15224 you're using a Linux or BSD and its packages are obsolete, stop using
15225 those packages and upgrade anyway.
15227 o Directory authority changes:
15228 - Change IP address for maatuska (v3 directory authority).
15229 - Change IP address for ides (v3 directory authority), and rename
15233 - When building or running with any version of OpenSSL earlier
15234 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
15235 versions have a bug (CVE-2011-4576) in which their block cipher
15236 padding includes uninitialized data, potentially leaking sensitive
15237 information to any peer with whom they make a SSLv3 connection. Tor
15238 does not use SSL v3 by default, but a hostile client or server
15239 could force an SSLv3 connection in order to gain information that
15240 they shouldn't have been able to get. The best solution here is to
15241 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
15242 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
15243 to make sure that the bug can't happen.
15244 - Never use a bridge or a controller-supplied node as an exit, even
15245 if its exit policy allows it. Found by wanoskarnet. Fixes bug
15246 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
15247 and 0.2.0.3-alpha (for bridge-purpose descriptors).
15248 - Only build circuits if we have a sufficient threshold of the total
15249 descriptors that are marked in the consensus with the "Exit"
15250 flag. This mitigates an attack proposed by wanoskarnet, in which
15251 all of a client's bridges collude to restrict the exit nodes that
15252 the client knows about. Fixes bug 5343.
15253 - Provide controllers with a safer way to implement the cookie
15254 authentication mechanism. With the old method, if another locally
15255 running program could convince a controller that it was the Tor
15256 process, then that program could trick the controller into telling
15257 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
15258 authentication method uses a challenge-response approach to prevent
15259 this attack. Fixes bug 5185; implements proposal 193.
15262 - Avoid logging uninitialized data when unable to decode a hidden
15263 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
15264 - Avoid a client-side assertion failure when receiving an INTRODUCE2
15265 cell on a general purpose circuit. Fixes bug 5644; bugfix on
15267 - Fix builds when the path to sed, openssl, or sha1sum contains
15268 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
15270 - Correct our replacements for the timeradd() and timersub() functions
15271 on platforms that lack them (for example, Windows). The timersub()
15272 function is used when expiring circuits, while timeradd() is
15273 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
15274 bugfix on 0.2.2.24-alpha.
15275 - Fix the SOCKET_OK test that we use to tell when socket
15276 creation fails so that it works on Win64. Fixes part of bug 4533;
15277 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
15280 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
15281 Fixes bug 5346; bugfix on 0.0.8pre3.
15282 - Make our number-parsing functions always treat too-large values
15283 as an error, even when those values exceed the width of the
15284 underlying type. Previously, if the caller provided these
15285 functions with minima or maxima set to the extreme values of the
15286 underlying integer type, these functions would return those
15287 values on overflow rather than treating overflow as an error.
15288 Fixes part of bug 5786; bugfix on 0.0.9.
15289 - Older Linux kernels erroneously respond to strange nmap behavior
15290 by having accept() return successfully with a zero-length
15291 socket. When this happens, just close the connection. Previously,
15292 we would try harder to learn the remote address: but there was
15293 no such remote address to learn, and our method for trying to
15294 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
15295 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
15296 - Correct parsing of certain date types in parse_http_time().
15297 Without this patch, If-Modified-Since would behave
15298 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
15299 Esteban Manchado Velázques.
15300 - Change the BridgePassword feature (part of the "bridge community"
15301 design, which is not yet implemented) to use a time-independent
15302 comparison. The old behavior might have allowed an adversary
15303 to use timing to guess the BridgePassword value. Fixes bug 5543;
15304 bugfix on 0.2.0.14-alpha.
15305 - Detect and reject certain misformed escape sequences in
15306 configuration values. Previously, these values would cause us
15307 to crash if received in a torrc file or over an authenticated
15308 control port. Bug found by Esteban Manchado Velázquez, and
15309 independently by Robert Connolly from Matta Consulting who further
15310 noted that it allows a post-authentication heap overflow. Patch
15311 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
15312 bugfix on 0.2.0.16-alpha.
15313 - Fix a compile warning when using the --enable-openbsd-malloc
15314 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
15315 - During configure, detect when we're building with clang version
15316 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
15317 CFLAGS. clang doesn't support them yet.
15318 - When sending an HTTP/1.1 proxy request, include a Host header.
15319 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
15320 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
15321 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
15322 - If we hit the error case where routerlist_insert() replaces an
15323 existing (old) server descriptor, make sure to remove that
15324 server descriptor from the old_routers list. Fix related to bug
15325 1776. Bugfix on 0.2.2.18-alpha.
15327 o Minor bugfixes (documentation and log messages):
15328 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
15329 Fixes bug 4856; bugfix on Tor 0.0.6.
15330 - Update "ClientOnly" man page entry to explain that there isn't
15331 really any point to messing with it. Resolves ticket 5005.
15332 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
15333 directory authority option (introduced in Tor 0.2.2.34).
15334 - Downgrade the "We're missing a certificate" message from notice
15335 to info: people kept mistaking it for a real problem, whereas it
15336 is seldom the problem even when we are failing to bootstrap. Fixes
15337 bug 5067; bugfix on 0.2.0.10-alpha.
15338 - Correctly spell "connect" in a log message on failure to create a
15339 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
15340 - Clarify the behavior of MaxCircuitDirtiness with hidden service
15341 circuits. Fixes issue 5259.
15344 - Directory authorities now reject versions of Tor older than
15345 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
15346 inclusive. These versions accounted for only a small fraction of
15347 the Tor network, and have numerous known security issues. Resolves
15349 - Update to the May 1 2012 Maxmind GeoLite Country database.
15352 - When sending or relaying a RELAY_EARLY cell, we used to convert
15353 it to a RELAY cell if the connection was using the v1 link
15354 protocol. This was a workaround for older versions of Tor, which
15355 didn't handle RELAY_EARLY cells properly. Now that all supported
15356 versions can handle RELAY_EARLY cells, and now that we're enforcing
15357 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
15358 remove this workaround. Addresses bug 4786.
15361 Changes in version 0.2.3.15-alpha - 2012-04-30
15362 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
15363 the development branch build on Windows again.
15365 o Minor bugfixes (on 0.2.2.x and earlier):
15366 - Make sure that there are no unhandled pending TLS errors before
15367 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
15368 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
15369 Bugfix on 0.1.0.5-rc; fixes bug 4528.
15370 - Fix an assert that directory authorities could trigger on sighup
15371 during some configuration state transitions. We now don't treat
15372 it as a fatal error when the new descriptor we just generated in
15373 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
15374 - After we pick a directory mirror, we would refuse to use it if
15375 it's in our ExcludeExitNodes list, resulting in mysterious failures
15376 to bootstrap for people who just wanted to avoid exiting from
15377 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
15378 - When building with --enable-static-tor on OpenBSD, do not
15379 erroneously attempt to link -lrt. Fixes bug 5103.
15381 o Minor bugfixes (on 0.2.3.x):
15382 - When Tor is built with kernel headers from a recent (last few
15383 years) Linux kernel, do not fail to run on older (pre-2.6.28
15384 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
15385 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
15386 and 0.2.3.12-alpha.
15387 - Fix compilation with miniupnpc version 1.6; patch from
15388 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
15389 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
15390 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
15391 - Fix compilation on platforms without unistd.h, or where environ
15392 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
15395 - Directory authorities are now a little more lenient at accepting
15396 older router descriptors, or newer router descriptors that don't
15397 make big changes. This should help ameliorate past and future
15398 issues where routers think they have uploaded valid descriptors,
15399 but the authorities don't think so. Fix for ticket 2479.
15400 - Make the code that clients use to detect an address change be
15401 IPv6-aware, so that it won't fill clients' logs with error
15402 messages when trying to get the IPv4 address of an IPv6
15403 connection. Implements ticket 5537.
15405 o Removed features:
15406 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
15407 authorities needed to use it for a while to keep the network working
15408 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
15409 that was six months ago. As of now, it should no longer be needed
15413 Changes in version 0.2.3.14-alpha - 2012-04-23
15414 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
15415 candidate. It also dramatically speeds up AES: fast relays should
15416 consider switching to the newer OpenSSL library.
15418 o Directory authority changes:
15419 - Change IP address for ides (v3 directory authority), and rename
15423 - Avoid logging uninitialized data when unable to decode a hidden
15424 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
15425 - Avoid a client-side assertion failure when receiving an INTRODUCE2
15426 cell on a general purpose circuit. Fixes bug 5644; bugfix on
15428 - If authorities are unable to get a v2 consensus document from other
15429 directory authorities, they no longer fall back to fetching
15430 them from regular directory caches. Fixes bug 5635; bugfix on
15431 0.2.2.26-beta, where routers stopped downloading v2 consensus
15432 documents entirely.
15433 - When we start a Tor client with a normal consensus already cached,
15434 be willing to download a microdescriptor consensus. Fixes bug 4011;
15435 fix on 0.2.3.1-alpha.
15437 o Major features (performance):
15438 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
15439 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
15440 vectorized AES implementations as appropriate. These can be much,
15441 much faster than other AES implementations.
15443 o Minor bugfixes (0.2.2.x and earlier):
15444 - Don't launch more than 10 service-side introduction-point circuits
15445 for a hidden service in five minutes. Previously, we would consider
15446 launching more introduction-point circuits if at least one second
15447 had passed without any introduction-point circuits failing. Fixes
15448 bug 4607; bugfix on 0.0.7pre1.
15449 - Change the BridgePassword feature (part of the "bridge community"
15450 design, which is not yet implemented) to use a time-independent
15451 comparison. The old behavior might have allowed an adversary
15452 to use timing to guess the BridgePassword value. Fixes bug 5543;
15453 bugfix on 0.2.0.14-alpha.
15454 - Enforce correct return behavior of tor_vsscanf() when the '%%'
15455 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
15456 - When sending an HTTP/1.1 proxy request, include a Host header.
15457 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
15458 - Don't log that we have "decided to publish new relay descriptor"
15459 unless we are actually publishing a descriptor. Fixes bug 3942;
15460 bugfix on 0.2.2.28-beta.
15462 o Minor bugfixes (0.2.3.x):
15463 - Fix a bug where a bridge authority crashes (on a failed assert)
15464 if it has seen no directory requests when it's time to write
15465 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
15466 - Fix bug stomping on ORPort option NoListen and ignoring option
15467 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
15468 - In the testsuite, provide a large enough buffer in the tor_sscanf
15469 unit test. Otherwise we'd overrun that buffer and crash during
15470 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
15472 - Make sure we create the keys directory if it doesn't exist and we're
15473 about to store the dynamic Diffie-Hellman parameters. Fixes bug
15474 5572; bugfix on 0.2.3.13-alpha.
15475 - Fix a small memory leak when trying to decode incorrect base16
15476 authenticator during SAFECOOKIE authentication. Found by
15477 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
15480 - Add more information to a log statement that might help track down
15481 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
15482 non-IP address" messages (or any Bug messages, for that matter!),
15483 please let us know about it.
15484 - Relays now understand an IPv6 address when they get one from a
15485 directory server. Resolves ticket 4875.
15486 - Resolve IPv6 addresses in bridge and entry statistics to country
15487 code "??" which means we at least count them. Resolves ticket 5053;
15488 improves on 0.2.3.9-alpha.
15489 - Update to the April 3 2012 Maxmind GeoLite Country database.
15490 - Begin a doc/state-contents.txt file to explain the contents of
15491 the Tor state file. Fixes bug 2987.
15493 o Default torrc changes:
15494 - Stop listing "socksport 9050" in torrc.sample. We open a socks
15495 port on 9050 by default anyway, so this should not change anything
15497 - Stop mentioning the deprecated *ListenAddress options in
15498 torrc.sample. Fixes bug 5438.
15499 - Document unit of bandwidth related options in sample torrc.
15502 o Removed features:
15503 - The "torify" script no longer supports the "tsocks" socksifier
15504 tool, since tsocks doesn't support DNS and UDP right for Tor.
15505 Everyone should be using torsocks instead. Fixes bugs 3530 and
15506 5180. Based on a patch by "ugh".
15508 o Code refactoring:
15509 - Change the symmetric cipher interface so that creating and
15510 initializing a stream cipher are no longer separate functions.
15511 - Remove all internal support for unpadded RSA. We never used it, and
15512 it would be a bad idea to start.
15515 Changes in version 0.2.3.13-alpha - 2012-03-26
15516 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
15517 in managed pluggable transports, as well as providing other cleanups
15518 that get us closer to a release candidate.
15520 o Directory authority changes:
15521 - Change IP address for maatuska (v3 directory authority).
15524 - Provide controllers with a safer way to implement the cookie
15525 authentication mechanism. With the old method, if another locally
15526 running program could convince a controller that it was the Tor
15527 process, then that program could trick the controller into telling
15528 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
15529 authentication method uses a challenge-response approach to prevent
15530 this attack. Fixes bug 5185, implements proposal 193.
15531 - Never use a bridge or a controller-supplied node as an exit, even
15532 if its exit policy allows it. Found by wanoskarnet. Fixes bug
15533 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
15534 and 0.2.0.3-alpha (for bridge-purpose descriptors).
15535 - Only build circuits if we have a sufficient threshold of the total
15536 descriptors that are marked in the consensus with the "Exit"
15537 flag. This mitigates an attack proposed by wanoskarnet, in which
15538 all of a client's bridges collude to restrict the exit nodes that
15539 the client knows about. Fixes bug 5343.
15541 o Major bugfixes (on Tor 0.2.3.x):
15542 - Avoid an assert when managed proxies like obfsproxy are configured,
15543 and we receive HUP signals or setconf attempts too rapidly. This
15544 situation happens most commonly when Vidalia tries to attach to
15545 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
15546 bugfix on 0.2.3.6-alpha.
15547 - Fix a relay-side pluggable transports bug where managed proxies were
15548 unreachable from the Internet, because Tor asked them to bind on
15549 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
15550 - Stop discarding command-line arguments when TestingTorNetwork
15551 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
15552 0.2.3.9-alpha, where task 4552 added support for two layers of
15554 - Resume allowing the unit tests to run in gdb. This was accidentally
15555 made impossible when the DisableDebuggerAttachment option was
15556 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
15557 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
15558 0.2.3.11-alpha. Reported by Anthony G. Basile.
15560 o Minor bugfixes (on 0.2.2.x and earlier):
15561 - Ensure we don't cannibalize circuits that are longer than three hops
15562 already, so we don't end up making circuits with 5 or more
15563 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
15564 0.1.0.1-rc which introduced cannibalization.
15565 - Detect and reject certain misformed escape sequences in
15566 configuration values. Previously, these values would cause us
15567 to crash if received in a torrc file or over an authenticated
15568 control port. Bug found by Esteban Manchado Velázquez, and
15569 independently by Robert Connolly from Matta Consulting who further
15570 noted that it allows a post-authentication heap overflow. Patch
15571 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
15572 bugfix on 0.2.0.16-alpha.
15573 - Fix a compile warning when using the --enable-openbsd-malloc
15574 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
15575 - Directory caches no longer refuse to clean out descriptors because
15576 of missing v2 networkstatus documents, unless they're configured
15577 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
15578 0.2.2.26-beta. Patch by Daniel Bryg.
15579 - Update to the latest version of the tinytest unit testing framework.
15580 This includes a couple of bugfixes that can be relevant for
15581 running forked unit tests on Windows, and removes all reserved
15584 o Minor bugfixes (on 0.2.3.x):
15585 - On a failed pipe() call, don't leak file descriptors. Fixes bug
15586 4296; bugfix on 0.2.3.1-alpha.
15587 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
15588 until after we have received a CERTS cell. Fixes bug 4361; bugfix
15589 on 0.2.3.6-alpha. Patch by "frosty".
15590 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
15591 option, so that the IP stack doesn't decide to use it for IPv4
15592 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
15593 - Ensure that variables set in Tor's environment cannot override
15594 environment variables that Tor passes to a managed
15595 pluggable-transport proxy. Previously, Tor would pass every
15596 variable in its environment to managed proxies along with the new
15597 ones, in such a way that on many operating systems, the inherited
15598 environment variables would override those which Tor tried to
15599 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
15600 bugfix on 0.2.3.9-alpha for Windows.
15603 - A wide variety of new unit tests by Esteban Manchado Velázquez.
15604 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
15605 - Update to the March 6 2012 Maxmind GeoLite Country database.
15608 Changes in version 0.2.3.12-alpha - 2012-02-13
15609 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
15610 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
15611 when Tor is configured to use a pluggable transport like obfsproxy.
15614 - Fix builds when the path to sed, openssl, or sha1sum contains
15615 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
15617 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
15618 connections. This change should allow busy exit relays to stop
15619 running out of available sockets as quickly. Fixes bug 4950;
15620 bugfix on 0.2.2.26-beta.
15621 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
15622 would ask the bridge for microdescriptors, which are only supported
15623 in 0.2.3.x, and then fail to bootstrap when it didn't get the
15624 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
15625 - Properly set up obfsproxy's environment when in managed mode. The
15626 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
15627 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
15628 5076 and 5082; bugfix on 0.2.3.6-alpha.
15631 - Use the dead_strip option when building Tor on OS X. This reduces
15632 binary size by almost 19% when linking openssl and libevent
15633 statically, which we do for Tor Browser Bundle.
15634 - Fix broken URLs in the sample torrc file, and tell readers about
15635 the OutboundBindAddress, ExitPolicyRejectPrivate, and
15636 PublishServerDescriptor options. Addresses bug 4652.
15637 - Update to the February 7 2012 Maxmind GeoLite Country database.
15640 - Downgrade the "We're missing a certificate" message from notice
15641 to info: people kept mistaking it for a real problem, whereas it
15642 is seldom the problem even when we are failing to bootstrap. Fixes
15643 bug 5067; bugfix on 0.2.0.10-alpha.
15644 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
15645 managed pluggable transport server proxy's environment.
15646 Previously, we would put it there, even though Tor doesn't
15647 implement an 'extended server port' yet, and even though Tor
15648 almost certainly isn't listening at that address. For now, we set
15649 it to an empty string to avoid crashing older obfsproxies. Bugfix
15651 - Log the heartbeat message every HeartbeatPeriod seconds, not every
15652 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
15653 0.2.3.1-alpha. Bug reported by Scott Bennett.
15654 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
15655 bugfix on 0.2.3.11-alpha.
15656 - Update "ClientOnly" man page entry to explain that there isn't
15657 really any point to messing with it. Resolves ticket 5005.
15658 - Use the correct CVE number for CVE-2011-4576 in our comments and
15659 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
15662 o Code simplifications and refactoring:
15663 - Use the _WIN32 macro throughout our code to detect Windows.
15664 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
15668 Changes in version 0.2.3.11-alpha - 2012-01-22
15669 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
15670 the last step of the plan to limit maximum circuit length, includes
15671 a wide variety of hidden service performance and correctness fixes,
15672 works around an OpenSSL security flaw if your distro is too stubborn
15673 to upgrade, and fixes a bunch of smaller issues.
15676 - Now that Tor 0.2.0.x is completely deprecated, enable the final
15677 part of "Proposal 110: Avoiding infinite length circuits" by
15678 refusing all circuit-extend requests that do not use a relay_early
15679 cell. This change helps Tor resist a class of denial-of-service
15680 attacks by limiting the maximum circuit length.
15681 - Adjust the number of introduction points that a hidden service
15682 will try to maintain based on how long its introduction points
15683 remain in use and how many introductions they handle. Fixes
15685 - Try to use system facilities for enumerating local interface
15686 addresses, before falling back to our old approach (which was
15687 binding a UDP socket, and calling getsockname() on it). That
15688 approach was scaring OS X users whose draconian firewall
15689 software warned about binding to UDP sockets, regardless of
15690 whether packets were sent. Now we try to use getifaddrs(),
15691 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
15692 system supports. Resolves ticket 1827.
15694 o Major security workaround:
15695 - When building or running with any version of OpenSSL earlier
15696 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
15697 versions have a bug (CVE-2011-4576) in which their block cipher
15698 padding includes uninitialized data, potentially leaking sensitive
15699 information to any peer with whom they make a SSLv3 connection. Tor
15700 does not use SSL v3 by default, but a hostile client or server
15701 could force an SSLv3 connection in order to gain information that
15702 they shouldn't have been able to get. The best solution here is to
15703 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
15704 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
15705 to make sure that the bug can't happen.
15708 - Fix the SOCKET_OK test that we use to tell when socket
15709 creation fails so that it works on Win64. Fixes part of bug 4533;
15710 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
15711 - Correct our replacements for the timeradd() and timersub() functions
15712 on platforms that lack them (for example, Windows). The timersub()
15713 function is used when expiring circuits, while timeradd() is
15714 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
15715 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
15716 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
15717 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
15718 bug at runtime, not compile time, because some distributions hack
15719 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
15720 on 0.2.3.9-alpha. Found by Pascal.
15722 o Minor features (controller):
15723 - Use absolute path names when reporting the torrc filename in the
15724 control protocol, so a controller can more easily find the torrc
15725 file. Resolves bug 1101.
15726 - Extend the control protocol to report flags that control a circuit's
15727 path selection in CIRC events and in replies to 'GETINFO
15728 circuit-status'. Implements part of ticket 2411.
15729 - Extend the control protocol to report the hidden service address
15730 and current state of a hidden-service-related circuit in CIRC
15731 events and in replies to 'GETINFO circuit-status'. Implements part
15733 - When reporting the path to the cookie file to the controller,
15734 give an absolute path. Resolves ticket 4881.
15735 - Allow controllers to request an event notification whenever a
15736 circuit is cannibalized or its purpose is changed. Implements
15737 part of ticket 3457.
15738 - Include the creation time of a circuit in CIRC and CIRC2
15739 control-port events and the list produced by the 'GETINFO
15740 circuit-status' control-port command.
15742 o Minor features (directory authorities):
15743 - Directory authorities now reject versions of Tor older than
15744 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
15745 inclusive. These versions accounted for only a small fraction of
15746 the Tor network, and have numerous known security issues. Resolves
15748 - Authority operators can now vote for all relays in a given
15749 set of countries to be BadDir/BadExit/Invalid/Rejected.
15750 - Provide two consensus parameters (FastFlagMinThreshold and
15751 FastFlagMaxThreshold) to control the range of allowable bandwidths
15752 for the Fast directory flag. These allow authorities to run
15753 experiments on appropriate requirements for being a "Fast" node.
15754 The AuthDirFastGuarantee config value still applies. Implements
15756 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
15757 directory authority option (introduced in Tor 0.2.2.34).
15759 o Minor features (other):
15760 - Don't disable the DirPort when we cannot exceed our AccountingMax
15761 limit during this interval because the effective bandwidthrate is
15762 low enough. This is useful in a situation where AccountMax is only
15763 used as an additional safeguard or to provide statistics.
15764 - Prepend an informative header to generated dynamic_dh_params files.
15765 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
15766 EntryNodes will have no effect. Resolves issue 2571.
15767 - Log more useful messages when we fail to disable debugger
15769 - Log which authority we're missing votes from when we go to fetch
15770 them from the other auths.
15771 - Log (at debug level) whenever a circuit's purpose is changed.
15772 - Add missing documentation for the MaxClientCircuitsPending,
15773 UseMicrodescriptors, UserspaceIOCPBuffers, and
15774 _UseFilteringSSLBufferevents options, all introduced during
15775 the 0.2.3.x series.
15776 - Update to the January 3 2012 Maxmind GeoLite Country database.
15778 o Minor bugfixes (hidden services):
15779 - Don't close hidden service client circuits which have almost
15780 finished connecting to their destination when they reach
15781 the normal circuit-build timeout. Previously, we would close
15782 introduction circuits which are waiting for an acknowledgement
15783 from the introduction point, and rendezvous circuits which have
15784 been specified in an INTRODUCE1 cell sent to a hidden service,
15785 after the normal CBT. Now, we mark them as 'timed out', and launch
15786 another rendezvous attempt in parallel. This behavior change can
15787 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
15788 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
15789 - Don't close hidden-service-side rendezvous circuits when they
15790 reach the normal circuit-build timeout. This behavior change can
15791 be disabled using the new
15792 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
15793 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
15794 - Make sure we never mark the wrong rendezvous circuit as having
15795 had its introduction cell acknowledged by the introduction-point
15796 relay. Previously, when we received an INTRODUCE_ACK cell on a
15797 client-side hidden-service introduction circuit, we might have
15798 marked a rendezvous circuit other than the one we specified in
15799 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
15800 a warning message and interfered with the hidden service
15801 connection-establishment process. Fixes bug 4759; bugfix on
15802 0.2.3.3-alpha, when we added the stream-isolation feature which
15803 might cause Tor to open multiple rendezvous circuits for the same
15805 - Don't trigger an assertion failure when we mark a new client-side
15806 hidden-service introduction circuit for close during the process
15807 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
15810 o Minor bugfixes (log messages):
15811 - Correctly spell "connect" in a log message on failure to create a
15812 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
15814 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
15815 Fixes bug 4856; bugfix on Tor 0.0.6.
15816 - Fix the log message describing how we work around discovering
15817 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
15818 4837; bugfix on 0.2.2.9-alpha.
15819 - When logging about a disallowed .exit name, do not also call it
15820 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
15822 o Minor bugfixes (build fixes):
15823 - During configure, detect when we're building with clang version
15824 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
15825 CFLAGS. clang doesn't support them yet.
15826 - During configure, search for library containing cos function as
15827 libm lives in libcore on some platforms (BeOS/Haiku). Linking
15828 against libm was hard-coded before. Fixes the first part of bug
15829 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
15831 - Detect attempts to build Tor on (as yet hypothetical) versions
15832 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
15833 fix for bug 4533. Bugfix on 0.2.2.28-beta.
15834 - Preprocessor directives should not be put inside the arguments
15835 of a macro. This would break compilation with GCC releases prior
15836 to version 3.3. We would never recommend such an old GCC version,
15837 but it is apparently required for binary compatibility on some
15838 platforms (namely, certain builds of Haiku). Fixes the other part
15839 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
15842 o Minor bugfixes (other):
15843 - Older Linux kernels erroneously respond to strange nmap behavior
15844 by having accept() return successfully with a zero-length
15845 socket. When this happens, just close the connection. Previously,
15846 we would try harder to learn the remote address: but there was
15847 no such remote address to learn, and our method for trying to
15848 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
15849 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
15850 - Fix null-pointer access that could occur if TLS allocation failed.
15851 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
15852 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
15853 accidentally been reverted.
15854 - Fix our implementation of crypto_random_hostname() so it can't
15855 overflow on ridiculously large inputs. (No Tor version has ever
15856 provided this kind of bad inputs, but let's be correct in depth.)
15857 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
15858 - Find more places in the code that should have been testing for
15859 invalid sockets using the SOCKET_OK macro. Required for a fix
15860 for bug 4533. Bugfix on 0.2.2.28-beta.
15861 - Fix an assertion failure when, while running with bufferevents, a
15862 connection finishes connecting after it is marked for close, but
15863 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
15864 - test_util_spawn_background_ok() hardcoded the expected value
15865 for ENOENT to 2. This isn't portable as error numbers are
15866 platform specific, and particularly the hurd has ENOENT at
15867 0x40000002. Construct expected string at runtime, using the correct
15868 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
15869 - Reject attempts to disable DisableDebuggerAttachment while Tor is
15870 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
15871 - Use an appropriate-width type for sockets in tor-fw-helper on
15872 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
15875 - When sending or relaying a RELAY_EARLY cell, we used to convert
15876 it to a RELAY cell if the connection was using the v1 link
15877 protocol. This was a workaround for older versions of Tor, which
15878 didn't handle RELAY_EARLY cells properly. Now that all supported
15879 versions can handle RELAY_EARLY cells, and now that we're enforcing
15880 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
15881 remove this workaround. Addresses bug 4786.
15883 o Code simplifications and refactoring:
15884 - Use OpenSSL's built-in SSL_state_string_long() instead of our
15885 own homebrewed ssl_state_to_string() replacement. Patch from
15886 Emile Snyder. Fixes bug 4653.
15887 - Use macros to indicate OpenSSL versions, so we don't need to worry
15888 about accidental hexadecimal bit shifts.
15889 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
15891 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
15892 - Use the smartlist_add_asprintf() alias more consistently.
15893 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
15894 invalid value, rather than just -1.
15895 - Rename a handful of old identifiers, mostly related to crypto
15896 structures and crypto functions. By convention, our "create an
15897 object" functions are called "type_new()", our "free an object"
15898 functions are called "type_free()", and our types indicate that
15899 they are types only with a final "_t". But a handful of older
15900 types and functions broke these rules, with function names like
15901 "type_create" or "subsystem_op_type", or with type names like
15905 Changes in version 0.2.3.10-alpha - 2011-12-16
15906 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
15907 Tor's buffers code. Absolutely everybody should upgrade.
15909 The bug relied on an incorrect calculation when making data continuous
15910 in one of our IO buffers, if the first chunk of the buffer was
15911 misaligned by just the wrong amount. The miscalculation would allow an
15912 attacker to overflow a piece of heap-allocated memory. To mount this
15913 attack, the attacker would need to either open a SOCKS connection to
15914 Tor's SocksPort (usually restricted to localhost), or target a Tor
15915 instance configured to make its connections through a SOCKS proxy
15916 (which Tor does not do by default).
15918 Good security practice requires that all heap-overflow bugs should be
15919 presumed to be exploitable until proven otherwise, so we are treating
15920 this as a potential code execution attack. Please upgrade immediately!
15921 This bug does not affect bufferevents-based builds of Tor. Special
15922 thanks to "Vektor" for reporting this issue to us!
15924 This release also contains a few minor bugfixes for issues discovered
15928 - Fix a heap overflow bug that could occur when trying to pull
15929 data into the first chunk of a buffer, when that chunk had
15930 already had some data drained from it. Fixes CVE-2011-2778;
15931 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
15934 - If we can't attach streams to a rendezvous circuit when we
15935 finish connecting to a hidden service, clear the rendezvous
15936 circuit's stream-isolation state and try to attach streams
15937 again. Previously, we cleared rendezvous circuits' isolation
15938 state either too early (if they were freshly built) or not at all
15939 (if they had been built earlier and were cannibalized). Bugfix on
15940 0.2.3.3-alpha; fixes bug 4655.
15941 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
15942 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
15943 - Fix an assertion failure when a relay with accounting enabled
15944 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
15947 - Update to the December 6 2011 Maxmind GeoLite Country database.
15950 Changes in version 0.2.2.35 - 2011-12-16
15951 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
15952 buffers code. Absolutely everybody should upgrade.
15954 The bug relied on an incorrect calculation when making data continuous
15955 in one of our IO buffers, if the first chunk of the buffer was
15956 misaligned by just the wrong amount. The miscalculation would allow an
15957 attacker to overflow a piece of heap-allocated memory. To mount this
15958 attack, the attacker would need to either open a SOCKS connection to
15959 Tor's SocksPort (usually restricted to localhost), or target a Tor
15960 instance configured to make its connections through a SOCKS proxy
15961 (which Tor does not do by default).
15963 Good security practice requires that all heap-overflow bugs should be
15964 presumed to be exploitable until proven otherwise, so we are treating
15965 this as a potential code execution attack. Please upgrade immediately!
15966 This bug does not affect bufferevents-based builds of Tor. Special
15967 thanks to "Vektor" for reporting this issue to us!
15969 Tor 0.2.2.35 also fixes several bugs in previous versions, including
15970 crash bugs for unusual configurations, and a long-term bug that
15971 would prevent Tor from starting on Windows machines with draconian
15974 With this release, we remind everyone that 0.2.0.x has reached its
15975 formal end-of-life. Those Tor versions have many known flaws, and
15976 nobody should be using them. You should upgrade -- ideally to the
15977 0.2.2.x series. If you're using a Linux or BSD and its packages are
15978 obsolete, stop using those packages and upgrade anyway.
15980 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
15981 longer receive support after some time in early 2012.
15984 - Fix a heap overflow bug that could occur when trying to pull
15985 data into the first chunk of a buffer, when that chunk had
15986 already had some data drained from it. Fixes CVE-2011-2778;
15987 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
15988 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
15989 that it doesn't attempt to allocate a socketpair. This could cause
15990 some problems on Windows systems with overzealous firewalls. Fix for
15991 bug 4457; workaround for Libevent versions 2.0.1-alpha through
15993 - If we mark an OR connection for close based on a cell we process,
15994 don't process any further cells on it. We already avoid further
15995 reads on marked-for-close connections, but now we also discard the
15996 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
15997 which was the first version where we might mark a connection for
15998 close based on processing a cell on it.
15999 - Correctly sanity-check that we don't underflow on a memory
16000 allocation (and then assert) for hidden service introduction
16001 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
16002 bugfix on 0.2.1.5-alpha.
16003 - Fix a memory leak when we check whether a hidden service
16004 descriptor has any usable introduction points left. Fixes bug
16005 4424. Bugfix on 0.2.2.25-alpha.
16006 - Don't crash when we're running as a relay and don't have a GeoIP
16007 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
16008 we've had in the 0.2.3.x branch already.
16009 - When running as a client, do not print a misleading (and plain
16010 wrong) log message that we're collecting "directory request"
16011 statistics: clients don't collect statistics. Also don't create a
16012 useless (because empty) stats file in the stats/ directory. Fixes
16013 bug 4353; bugfix on 0.2.2.34.
16016 - Detect failure to initialize Libevent. This fix provides better
16017 detection for future instances of bug 4457.
16018 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
16019 function. This was eating up hideously large amounts of time on some
16020 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
16021 - Resolve an integer overflow bug in smartlist_ensure_capacity().
16022 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
16024 - Don't warn about unused log_mutex in log.c when building with
16025 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
16026 0.1.0.6-rc which introduced --disable-threads.
16027 - When configuring, starting, or stopping an NT service, stop
16028 immediately after the service configuration attempt has succeeded
16029 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
16030 - When sending a NETINFO cell, include the original address
16031 received for the other side, not its canonical address. Found
16032 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
16033 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
16034 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
16035 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
16036 occurred when a client tried to fetch a descriptor for a bridge
16037 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
16038 - Backport fixes for a pair of compilation warnings on Windows.
16039 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
16040 - If we had ever tried to call tor_addr_to_str on an address of
16041 unknown type, we would have done a strdup on an uninitialized
16042 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
16043 Reported by "troll_un".
16044 - Correctly detect and handle transient lookup failures from
16045 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
16046 Reported by "troll_un".
16047 - Fix null-pointer access that could occur if TLS allocation failed.
16048 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
16049 - Use tor_socket_t type for listener argument to accept(). Fixes bug
16050 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
16053 - Add two new config options for directory authorities:
16054 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
16055 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
16056 that is always sufficient to satisfy the bandwidth requirement for
16057 the Guard flag. Now it will be easier for researchers to simulate
16058 Tor networks with different values. Resolves ticket 4484.
16059 - When Tor ignores a hidden service specified in its configuration,
16060 include the hidden service's directory in the warning message.
16061 Previously, we would only tell the user that some hidden service
16062 was ignored. Bugfix on 0.0.6; fixes bug 4426.
16063 - Update to the December 6 2011 Maxmind GeoLite Country database.
16065 o Packaging changes:
16066 - Make it easier to automate expert package builds on Windows,
16067 by removing an absolute path from makensis.exe command.
16070 Changes in version 0.2.1.32 - 2011-12-16
16071 Tor 0.2.1.32 backports important security and privacy fixes for
16072 oldstable. This release is intended only for package maintainers and
16073 others who cannot use the 0.2.2 stable series. All others should be
16074 using Tor 0.2.2.x or newer.
16076 The Tor 0.2.1.x series will reach formal end-of-life some time in
16077 early 2012; we will stop releasing patches for it then.
16079 o Major bugfixes (also included in 0.2.2.x):
16080 - Correctly sanity-check that we don't underflow on a memory
16081 allocation (and then assert) for hidden service introduction
16082 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
16083 bugfix on 0.2.1.5-alpha.
16084 - Fix a heap overflow bug that could occur when trying to pull
16085 data into the first chunk of a buffer, when that chunk had
16086 already had some data drained from it. Fixes CVE-2011-2778;
16087 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
16090 - Update to the December 6 2011 Maxmind GeoLite Country database.
16093 Changes in version 0.2.3.9-alpha - 2011-12-08
16094 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
16095 a "DisableNetwork" security feature that bundles can use to avoid
16096 touching the network until bridges are configured, moves forward on
16097 the pluggable transport design, fixes a flaw in the hidden service
16098 design that unnecessarily prevented clients with wrong clocks from
16099 reaching hidden services, and fixes a wide variety of other issues.
16102 - Clients can now connect to private bridges over IPv6. Bridges
16103 still need at least one IPv4 address in order to connect to
16104 other relays. Note that we don't yet handle the case where the
16105 user has two bridge lines for the same bridge (one IPv4, one
16106 IPv6). Implements parts of proposal 186.
16107 - New "DisableNetwork" config option to prevent Tor from launching any
16108 connections or accepting any connections except on a control port.
16109 Bundles and controllers can set this option before letting Tor talk
16110 to the rest of the network, for example to prevent any connections
16111 to a non-bridge address. Packages like Orbot can also use this
16112 option to instruct Tor to save power when the network is off.
16113 - Clients and bridges can now be configured to use a separate
16114 "transport" proxy. This approach makes the censorship arms race
16115 easier by allowing bridges to use protocol obfuscation plugins. It
16116 implements the "managed proxy" part of proposal 180 (ticket 3472).
16117 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
16118 implementation. It makes AES_CTR about 7% faster than our old one
16119 (which was about 10% faster than the one OpenSSL used to provide).
16120 Resolves ticket 4526.
16121 - Add a "tor2web mode" for clients that want to connect to hidden
16122 services non-anonymously (and possibly more quickly). As a safety
16123 measure to try to keep users from turning this on without knowing
16124 what they are doing, tor2web mode must be explicitly enabled at
16125 compile time, and a copy of Tor compiled to run in tor2web mode
16126 cannot be used as a normal Tor client. Implements feature 2553.
16127 - Add experimental support for running on Windows with IOCP and no
16128 kernel-space socket buffers. This feature is controlled by a new
16129 "UserspaceIOCPBuffers" config option (off by default), which has
16130 no effect unless Tor has been built with support for bufferevents,
16131 is running on Windows, and has enabled IOCP. This may, in the long
16132 run, help solve or mitigate bug 98.
16133 - Use a more secure consensus parameter voting algorithm. Now at
16134 least three directory authorities or a majority of them must
16135 vote on a given parameter before it will be included in the
16136 consensus. Implements proposal 178.
16139 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
16140 They used to check that the timestamp was within 30 minutes
16141 of their system clock, so they could cap the size of their
16142 replay-detection cache, but that approach unnecessarily refused
16143 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
16144 the v3 intro-point protocol (the first one which sent a timestamp
16145 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
16146 - Only use the EVP interface when AES acceleration is enabled,
16147 to avoid a 5-7% performance regression. Resolves issue 4525;
16148 bugfix on 0.2.3.8-alpha.
16150 o Privacy/anonymity features (bridge detection):
16151 - Make bridge SSL certificates a bit more stealthy by using random
16152 serial numbers, in the same fashion as OpenSSL when generating
16153 self-signed certificates. Implements ticket 4584.
16154 - Introduce a new config option "DynamicDHGroups", enabled by
16155 default, which provides each bridge with a unique prime DH modulus
16156 to be used during SSL handshakes. This option attempts to help
16157 against censors who might use the Apache DH modulus as a static
16158 identifier for bridges. Addresses ticket 4548.
16160 o Minor features (new/different config options):
16161 - New configuration option "DisableDebuggerAttachment" (on by default)
16162 to prevent basic debugging attachment attempts by other processes.
16163 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
16164 - Allow MapAddress directives to specify matches against super-domains,
16165 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
16166 Implements issue 933.
16167 - Slightly change behavior of "list" options (that is, config
16168 options that can appear more than once) when they appear both in
16169 torrc and on the command line. Previously, the command-line options
16170 would be appended to the ones from torrc. Now, the command-line
16171 options override the torrc options entirely. This new behavior
16172 allows the user to override list options (like exit policies and
16173 ports to listen on) from the command line, rather than simply
16174 appending to the list.
16175 - You can get the old (appending) command-line behavior for "list"
16176 options by prefixing the option name with a "+".
16177 - You can remove all the values for a "list" option from the command
16178 line without adding any new ones by prefixing the option name
16180 - Add experimental support for a "defaults" torrc file to be parsed
16181 before the regular torrc. Torrc options override the defaults file's
16182 options in the same way that the command line overrides the torrc.
16183 The SAVECONF controller command saves only those options which
16184 differ between the current configuration and the defaults file. HUP
16185 reloads both files. (Note: This is an experimental feature; its
16186 behavior will probably be refined in future 0.2.3.x-alpha versions
16187 to better meet packagers' needs.) Implements task 4552.
16190 - Try to make the introductory warning message that Tor prints on
16191 startup more useful for actually finding help and information.
16192 Resolves ticket 2474.
16193 - Running "make version" now displays the version of Tor that
16194 we're about to build. Idea from katmagic; resolves issue 4400.
16195 - Expire old or over-used hidden service introduction points.
16196 Required by fix for bug 3460.
16197 - Move the replay-detection cache for the RSA-encrypted parts of
16198 INTRODUCE2 cells to the introduction point data structures.
16199 Previously, we would use one replay-detection cache per hidden
16200 service. Required by fix for bug 3460.
16201 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
16202 public key replay-detection cache from 60 minutes to 5 minutes. This
16203 replay-detection cache is now used only to detect multiple
16204 INTRODUCE2 cells specifying the same rendezvous point, so we can
16205 avoid launching multiple simultaneous attempts to connect to it.
16207 o Minor bugfixes (on Tor 0.2.2.x and earlier):
16208 - Resolve an integer overflow bug in smartlist_ensure_capacity().
16209 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
16211 - Fix a minor formatting issue in one of tor-gencert's error messages.
16213 - Prevent a false positive from the check-spaces script, by disabling
16214 the "whitespace between function name and (" check for functions
16216 - Fix a log message suggesting that people contact a non-existent
16217 email address. Fixes bug 3448.
16218 - Fix null-pointer access that could occur if TLS allocation failed.
16219 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
16220 - Report a real bootstrap problem to the controller on router
16221 identity mismatch. Previously we just said "foo", which probably
16222 made a lot of sense at the time. Fixes bug 4169; bugfix on
16224 - If we had ever tried to call tor_addr_to_str() on an address of
16225 unknown type, we would have done a strdup() on an uninitialized
16226 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
16227 Reported by "troll_un".
16228 - Correctly detect and handle transient lookup failures from
16229 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
16230 Reported by "troll_un".
16231 - Use tor_socket_t type for listener argument to accept(). Fixes bug
16232 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
16233 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
16234 bug 4532; found by "troll_un".
16236 o Minor bugfixes (on Tor 0.2.3.x):
16237 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
16239 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
16240 circuit for use as a hidden service client's rendezvous point.
16241 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
16242 with help from wanoskarnet.
16243 - Restore behavior of overriding SocksPort, ORPort, and similar
16244 options from the command line. Bugfix on 0.2.3.3-alpha.
16247 - Properly handle the case where the build-tree is not the same
16248 as the source tree when generating src/common/common_sha1.i,
16249 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
16250 bugfix on 0.2.0.1-alpha.
16252 o Code simplifications, cleanups, and refactorings:
16253 - Remove the pure attribute from all functions that used it
16254 previously. In many cases we assigned it incorrectly, because the
16255 functions might assert or call impure functions, and we don't have
16256 evidence that keeping the pure attribute is worthwhile. Implements
16257 changes suggested in ticket 4421.
16258 - Remove some dead code spotted by coverity. Fixes cid 432.
16259 Bugfix on 0.2.3.1-alpha, closes bug 4637.
16262 Changes in version 0.2.3.8-alpha - 2011-11-22
16263 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
16264 socketpair-related bug that has been bothering Windows users. It adds
16265 support to serve microdescriptors to controllers, so Vidalia's network
16266 map can resume listing relays (once Vidalia implements its side),
16267 and adds better support for hardware AES acceleration. Finally, it
16268 starts the process of adjusting the bandwidth cutoff for getting the
16269 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
16270 that tiny relays harm performance more than they help network capacity.
16273 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
16274 that it doesn't attempt to allocate a socketpair. This could cause
16275 some problems on Windows systems with overzealous firewalls. Fix for
16276 bug 4457; workaround for Libevent versions 2.0.1-alpha through
16278 - Correctly sanity-check that we don't underflow on a memory
16279 allocation (and then assert) for hidden service introduction
16280 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
16281 bugfix on 0.2.1.5-alpha.
16282 - Remove the artificially low cutoff of 20KB to guarantee the Fast
16283 flag. In the past few years the average relay speed has picked
16284 up, and while the "top 7/8 of the network get the Fast flag" and
16285 "all relays with 20KB or more of capacity get the Fast flag" rules
16286 used to have the same result, now the top 7/8 of the network has
16287 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
16288 - Fix a rare assertion failure when checking whether a v0 hidden
16289 service descriptor has any usable introduction points left, and
16290 we don't have enough information to build a circuit to the first
16291 intro point named in the descriptor. The HS client code in
16292 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
16293 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
16294 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
16295 - Make bridge authorities not crash when they are asked for their own
16296 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
16297 - When running as a client, do not print a misleading (and plain
16298 wrong) log message that we're collecting "directory request"
16299 statistics: clients don't collect statistics. Also don't create a
16300 useless (because empty) stats file in the stats/ directory. Fixes
16301 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
16304 - Allow Tor controllers like Vidalia to obtain the microdescriptor
16305 for a relay by identity digest or nickname. Previously,
16306 microdescriptors were only available by their own digests, so a
16307 controller would have to ask for and parse the whole microdescriptor
16308 consensus in order to look up a single relay's microdesc. Fixes
16309 bug 3832; bugfix on 0.2.3.1-alpha.
16310 - Use OpenSSL's EVP interface for AES encryption, so that all AES
16311 operations can use hardware acceleration (if present). Resolves
16314 o Minor bugfixes (on 0.2.2.x and earlier):
16315 - Detect failure to initialize Libevent. This fix provides better
16316 detection for future instances of bug 4457.
16317 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
16318 function. This was eating up hideously large amounts of time on some
16319 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
16320 - Don't warn about unused log_mutex in log.c when building with
16321 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
16322 0.1.0.6-rc which introduced --disable-threads.
16323 - Allow manual 'authenticate' commands to the controller interface
16324 from netcat (nc) as well as telnet. We were rejecting them because
16325 they didn't come with the expected whitespace at the end of the
16326 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
16327 - Fix some (not actually triggerable) buffer size checks in usage of
16328 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
16330 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
16331 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
16332 - When configuring, starting, or stopping an NT service, stop
16333 immediately after the service configuration attempt has succeeded
16334 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
16335 - When sending a NETINFO cell, include the original address
16336 received for the other side, not its canonical address. Found
16337 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
16338 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
16339 can pick them up when the tests aren't disabled. Bugfix on
16340 0.2.2.4-alpha which introduced tinytest.
16341 - Fix a memory leak when we check whether a hidden service
16342 descriptor has any usable introduction points left. Fixes bug
16343 4424. Bugfix on 0.2.2.25-alpha.
16344 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
16345 occurred when a client tried to fetch a descriptor for a bridge
16346 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
16348 o Minor bugfixes (on 0.2.3.x):
16349 - Make util unit tests build correctly with MSVC. Bugfix on
16350 0.2.3.3-alpha. Patch by Gisle Vanem.
16351 - Successfully detect AUTH_CHALLENGE cells with no recognized
16352 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
16353 Found by frosty_un.
16354 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
16355 it should still send a NETINFO cell to allow the connection to
16356 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
16358 - Log less loudly when we get an invalid authentication certificate
16359 from a source other than a directory authority: it's not unusual
16360 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
16362 - Tolerate servers with more clock skew in their authentication
16363 certificates than previously. Fixes bug 4371; bugfix on
16365 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
16366 on 0.2.3.4-alpha and 0.2.3.6-alpha.
16369 - Add two new config options for directory authorities:
16370 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
16371 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
16372 that is always sufficient to satisfy the bandwidth requirement for
16373 the Guard flag. Now it will be easier for researchers to simulate
16374 Tor networks with different values. Resolves ticket 4484.
16375 - When Tor ignores a hidden service specified in its configuration,
16376 include the hidden service's directory in the warning message.
16377 Previously, we would only tell the user that some hidden service
16378 was ignored. Bugfix on 0.0.6; fixes bug 4426.
16379 - When we fail to initialize Libevent, retry with IOCP disabled so we
16380 don't need to turn on multi-threading support in Libevent, which in
16381 turn requires a working socketpair(). This is a workaround for bug
16382 4457, which affects Libevent versions from 2.0.1-alpha through
16384 - Detect when we try to build on a platform that doesn't define
16385 AF_UNSPEC to 0. We don't work there, so refuse to compile.
16386 - Update to the November 1 2011 Maxmind GeoLite Country database.
16388 o Packaging changes:
16389 - Make it easier to automate expert package builds on Windows,
16390 by removing an absolute path from makensis.exe command.
16392 o Code simplifications and refactoring:
16393 - Remove some redundant #include directives throughout the code.
16394 Patch from Andrea Gelmini.
16395 - Unconditionally use OpenSSL's AES implementation instead of our
16396 old built-in one. OpenSSL's AES has been better for a while, and
16397 relatively few servers should still be on any version of OpenSSL
16398 that doesn't have good optimized assembly AES.
16399 - Use the name "CERTS" consistently to refer to the new cell type;
16400 we were calling it CERT in some places and CERTS in others.
16403 - Numerous new unit tests for functions in util.c and address.c by
16405 - The long-disabled benchmark tests are now split into their own
16406 ./src/test/bench binary.
16407 - The benchmark tests can now use more accurate timers than
16408 gettimeofday() when such timers are available.
16411 Changes in version 0.2.3.7-alpha - 2011-10-30
16412 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
16413 the new v3 handshake. It also resolves yet another bridge address
16417 - If we mark an OR connection for close based on a cell we process,
16418 don't process any further cells on it. We already avoid further
16419 reads on marked-for-close connections, but now we also discard the
16420 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
16421 which was the first version where we might mark a connection for
16422 close based on processing a cell on it.
16423 - Fix a double-free bug that would occur when we received an invalid
16424 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
16425 bugfix on 0.2.3.6-alpha.
16426 - Bridges no longer include their address in NETINFO cells on outgoing
16427 OR connections, to allow them to blend in better with clients.
16428 Removes another avenue for enumerating bridges. Reported by
16429 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
16430 cells were introduced.
16433 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
16434 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
16437 Changes in version 0.2.3.6-alpha - 2011-10-26
16438 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
16439 anonymity vulnerability where an attacker can deanonymize Tor
16440 users. Everybody should upgrade.
16442 This release also features support for a new v3 connection handshake
16443 protocol, and fixes to make hidden service connections more robust.
16446 - Implement a new handshake protocol (v3) for authenticating Tors to
16447 each other over TLS. It should be more resistant to fingerprinting
16448 than previous protocols, and should require less TLS hacking for
16449 future Tor implementations. Implements proposal 176.
16450 - Allow variable-length padding cells to disguise the length of
16451 Tor's TLS records. Implements part of proposal 184.
16453 o Privacy/anonymity fixes (clients):
16454 - Clients and bridges no longer send TLS certificate chains on
16455 outgoing OR connections. Previously, each client or bridge would
16456 use the same cert chain for all outgoing OR connections until
16457 its IP address changes, which allowed any relay that the client
16458 or bridge contacted to determine which entry guards it is using.
16459 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16460 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16461 no longer considers that connection as suitable for satisfying a
16462 circuit EXTEND request. Now relays can protect clients from the
16463 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16464 - Directory authorities no longer assign the Guard flag to relays
16465 that haven't upgraded to the above "refuse EXTEND requests
16466 to client connections" fix. Now directory authorities can
16467 protect clients from the CVE-2011-2768 issue even if neither
16468 the clients nor the relays have upgraded yet. There's a new
16469 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
16470 to let us transition smoothly, else tomorrow there would be no
16473 o Major bugfixes (hidden services):
16474 - Improve hidden service robustness: when an attempt to connect to
16475 a hidden service ends, be willing to refetch its hidden service
16476 descriptors from each of the HSDir relays responsible for them
16477 immediately. Previously, we would not consider refetching the
16478 service's descriptors from each HSDir for 15 minutes after the last
16479 fetch, which was inconvenient if the hidden service was not running
16480 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
16481 - When one of a hidden service's introduction points appears to be
16482 unreachable, stop trying it. Previously, we would keep trying
16483 to build circuits to the introduction point until we lost the
16484 descriptor, usually because the user gave up and restarted Tor.
16485 Partly fixes bug 3825.
16486 - Don't launch a useless circuit after failing to use one of a
16487 hidden service's introduction points. Previously, we would
16488 launch a new introduction circuit, but not set the hidden service
16489 which that circuit was intended to connect to, so it would never
16490 actually be used. A different piece of code would then create a
16491 new introduction circuit correctly. Bug reported by katmagic and
16492 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
16494 o Major bugfixes (other):
16495 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
16496 that they initiated. Relays could distinguish incoming bridge
16497 connections from client connections, creating another avenue for
16498 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
16499 Found by "frosty_un".
16500 - Don't update the AccountingSoftLimitHitAt state file entry whenever
16501 tor gets started. This prevents a wrong average bandwidth
16502 estimate, which would cause relays to always start a new accounting
16503 interval at the earliest possible moment. Fixes bug 2003; bugfix
16504 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
16505 immensely in tracking this bug down.
16506 - Fix a crash bug when changing node restrictions while a DNS lookup
16507 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
16510 o Minor bugfixes (on 0.2.2.x and earlier):
16511 - When a hidden service turns an extra service-side introduction
16512 circuit into a general-purpose circuit, free the rend_data and
16513 intro_key fields first, so we won't leak memory if the circuit
16514 is cannibalized for use as another service-side introduction
16515 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
16516 - Rephrase the log message emitted if the TestSocks check is
16517 successful. Patch from Fabian Keil; fixes bug 4094.
16518 - Bridges now skip DNS self-tests, to act a little more stealthily.
16519 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
16520 bridges. Patch by "warms0x".
16521 - Remove a confusing dollar sign from the example fingerprint in the
16522 man page, and also make the example fingerprint a valid one. Fixes
16523 bug 4309; bugfix on 0.2.1.3-alpha.
16524 - Fix internal bug-checking logic that was supposed to catch
16525 failures in digest generation so that it will fail more robustly
16526 if we ask for a nonexistent algorithm. Found by Coverity Scan.
16527 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
16528 - Report any failure in init_keys() calls launched because our
16529 IP address has changed. Spotted by Coverity Scan. Bugfix on
16530 0.1.1.4-alpha; fixes CID 484.
16532 o Minor bugfixes (on 0.2.3.x):
16533 - Fix a bug in configure.in that kept it from building a configure
16534 script with autoconf versions earlier than 2.61. Fixes bug 2430;
16535 bugfix on 0.2.3.1-alpha.
16536 - Don't warn users that they are exposing a client port to the
16537 Internet if they have specified an RFC1918 address. Previously,
16538 we would warn if the user had specified any non-loopback
16539 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
16540 - Fix memory leaks in the failing cases of the new SocksPort and
16541 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
16542 fixes coverity CIDs 485, 486, and 487.
16545 - When a hidden service's introduction point times out, consider
16546 trying it again during the next attempt to connect to the
16547 HS. Previously, we would not try it again unless a newly fetched
16548 descriptor contained it. Required by fixes for bugs 1297 and 3825.
16549 - The next version of Windows will be called Windows 8, and it has
16550 a major version of 6, minor version of 2. Correctly identify that
16551 version instead of calling it "Very recent version". Resolves
16552 ticket 4153; reported by funkstar.
16553 - The Bridge Authority now writes statistics on how many bridge
16554 descriptors it gave out in total, and how many unique descriptors
16555 it gave out. It also lists how often the most and least commonly
16556 fetched descriptors were given out, as well as the median and
16557 25th/75th percentile. Implements tickets 4200 and 4294.
16558 - Update to the October 4 2011 Maxmind GeoLite Country database.
16560 o Code simplifications and refactoring:
16561 - Remove some old code to remember statistics about which descriptors
16562 we've served as a directory mirror. The feature wasn't used and
16563 is outdated now that microdescriptors are around.
16564 - Rename Tor functions that turn strings into addresses, so that
16565 "parse" indicates that no hostname resolution occurs, and
16566 "lookup" indicates that hostname resolution may occur. This
16567 should help prevent mistakes in the future. Fixes bug 3512.
16570 Changes in version 0.2.2.34 - 2011-10-26
16571 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
16572 can deanonymize Tor users. Everybody should upgrade.
16574 The attack relies on four components: 1) Clients reuse their TLS cert
16575 when talking to different relays, so relays can recognize a user by
16576 the identity key in her cert. 2) An attacker who knows the client's
16577 identity key can probe each guard relay to see if that identity key
16578 is connected to that guard relay right now. 3) A variety of active
16579 attacks in the literature (starting from "Low-Cost Traffic Analysis
16580 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
16581 discover the guard relays that a Tor user visiting the website is using.
16582 4) Clients typically pick three guards at random, so the set of guards
16583 for a given user could well be a unique fingerprint for her. This
16584 release fixes components #1 and #2, which is enough to block the attack;
16585 the other two remain as open research problems. Special thanks to
16586 "frosty_un" for reporting the issue to us!
16588 Clients should upgrade so they are no longer recognizable by the TLS
16589 certs they present. Relays should upgrade so they no longer allow a
16590 remote attacker to probe them to test whether unpatched clients are
16591 currently connected to them.
16593 This release also fixes several vulnerabilities that allow an attacker
16594 to enumerate bridge relays. Some bridge enumeration attacks still
16595 remain; see for example proposal 188.
16597 o Privacy/anonymity fixes (clients):
16598 - Clients and bridges no longer send TLS certificate chains on
16599 outgoing OR connections. Previously, each client or bridge would
16600 use the same cert chain for all outgoing OR connections until
16601 its IP address changes, which allowed any relay that the client
16602 or bridge contacted to determine which entry guards it is using.
16603 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16604 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16605 no longer considers that connection as suitable for satisfying a
16606 circuit EXTEND request. Now relays can protect clients from the
16607 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16608 - Directory authorities no longer assign the Guard flag to relays
16609 that haven't upgraded to the above "refuse EXTEND requests
16610 to client connections" fix. Now directory authorities can
16611 protect clients from the CVE-2011-2768 issue even if neither
16612 the clients nor the relays have upgraded yet. There's a new
16613 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
16614 to let us transition smoothly, else tomorrow there would be no
16617 o Privacy/anonymity fixes (bridge enumeration):
16618 - Bridge relays now do their directory fetches inside Tor TLS
16619 connections, like all the other clients do, rather than connecting
16620 directly to the DirPort like public relays do. Removes another
16621 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
16622 - Bridges relays now build circuits for themselves in a more similar
16623 way to how clients build them. Removes another avenue for
16624 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
16625 when bridges were introduced.
16626 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
16627 that they initiated. Relays could distinguish incoming bridge
16628 connections from client connections, creating another avenue for
16629 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
16630 Found by "frosty_un".
16633 - Fix a crash bug when changing node restrictions while a DNS lookup
16634 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
16636 - Don't launch a useless circuit after failing to use one of a
16637 hidden service's introduction points. Previously, we would
16638 launch a new introduction circuit, but not set the hidden service
16639 which that circuit was intended to connect to, so it would never
16640 actually be used. A different piece of code would then create a
16641 new introduction circuit correctly. Bug reported by katmagic and
16642 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
16645 - Change an integer overflow check in the OpenBSD_Malloc code so
16646 that GCC is less likely to eliminate it as impossible. Patch
16647 from Mansour Moufid. Fixes bug 4059.
16648 - When a hidden service turns an extra service-side introduction
16649 circuit into a general-purpose circuit, free the rend_data and
16650 intro_key fields first, so we won't leak memory if the circuit
16651 is cannibalized for use as another service-side introduction
16652 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
16653 - Bridges now skip DNS self-tests, to act a little more stealthily.
16654 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
16655 bridges. Patch by "warms0x".
16656 - Fix internal bug-checking logic that was supposed to catch
16657 failures in digest generation so that it will fail more robustly
16658 if we ask for a nonexistent algorithm. Found by Coverity Scan.
16659 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
16660 - Report any failure in init_keys() calls launched because our
16661 IP address has changed. Spotted by Coverity Scan. Bugfix on
16662 0.1.1.4-alpha; fixes CID 484.
16664 o Minor bugfixes (log messages and documentation):
16665 - Remove a confusing dollar sign from the example fingerprint in the
16666 man page, and also make the example fingerprint a valid one. Fixes
16667 bug 4309; bugfix on 0.2.1.3-alpha.
16668 - The next version of Windows will be called Windows 8, and it has
16669 a major version of 6, minor version of 2. Correctly identify that
16670 version instead of calling it "Very recent version". Resolves
16671 ticket 4153; reported by funkstar.
16672 - Downgrade log messages about circuit timeout calibration from
16673 "notice" to "info": they don't require or suggest any human
16674 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
16675 bugfix on 0.2.2.14-alpha.
16678 - Turn on directory request statistics by default and include them in
16679 extra-info descriptors. Don't break if we have no GeoIP database.
16680 Backported from 0.2.3.1-alpha; implements ticket 3951.
16681 - Update to the October 4 2011 Maxmind GeoLite Country database.
16684 Changes in version 0.2.1.31 - 2011-10-26
16685 Tor 0.2.1.31 backports important security and privacy fixes for
16686 oldstable. This release is intended only for package maintainers and
16687 others who cannot use the 0.2.2 stable series. All others should be
16688 using Tor 0.2.2.x or newer.
16690 o Security fixes (also included in 0.2.2.x):
16691 - Replace all potentially sensitive memory comparison operations
16692 with versions whose runtime does not depend on the data being
16693 compared. This will help resist a class of attacks where an
16694 adversary can use variations in timing information to learn
16695 sensitive data. Fix for one case of bug 3122. (Safe memcmp
16696 implementation by Robert Ransom based partially on code by DJB.)
16697 - Fix an assert in parsing router descriptors containing IPv6
16698 addresses. This one took down the directory authorities when
16699 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
16701 o Privacy/anonymity fixes (also included in 0.2.2.x):
16702 - Clients and bridges no longer send TLS certificate chains on
16703 outgoing OR connections. Previously, each client or bridge would
16704 use the same cert chain for all outgoing OR connections until
16705 its IP address changes, which allowed any relay that the client
16706 or bridge contacted to determine which entry guards it is using.
16707 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16708 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16709 no longer considers that connection as suitable for satisfying a
16710 circuit EXTEND request. Now relays can protect clients from the
16711 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16712 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
16713 that they initiated. Relays could distinguish incoming bridge
16714 connections from client connections, creating another avenue for
16715 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
16716 Found by "frosty_un".
16717 - When receiving a hidden service descriptor, check that it is for
16718 the hidden service we wanted. Previously, Tor would store any
16719 hidden service descriptors that a directory gave it, whether it
16720 wanted them or not. This wouldn't have let an attacker impersonate
16721 a hidden service, but it did let directories pre-seed a client
16722 with descriptors that it didn't want. Bugfix on 0.0.6.
16723 - Avoid linkability based on cached hidden service descriptors: forget
16724 all hidden service descriptors cached as a client when processing a
16725 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
16726 - Make the bridge directory authority refuse to answer directory
16727 requests for "all" descriptors. It used to include bridge
16728 descriptors in its answer, which was a major information leak.
16729 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
16730 - Don't attach new streams to old rendezvous circuits after SIGNAL
16731 NEWNYM. Previously, we would keep using an existing rendezvous
16732 circuit if it remained open (i.e. if it were kept open by a
16733 long-lived stream, or if a new stream were attached to it before
16734 Tor could notice that it was old and no longer in use). Bugfix on
16735 0.1.1.15-rc; fixes bug 3375.
16737 o Minor bugfixes (also included in 0.2.2.x):
16738 - When we restart our relay, we might get a successful connection
16739 from the outside before we've started our reachability tests,
16740 triggering a warning: "ORPort found reachable, but I have no
16741 routerinfo yet. Failing to inform controller of success." This
16742 bug was harmless unless Tor is running under a controller
16743 like Vidalia, in which case the controller would never get a
16744 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
16746 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
16747 enabled. Fixes bug 1526.
16748 - Remove undocumented option "-F" from tor-resolve: it hasn't done
16749 anything since 0.2.1.16-rc.
16750 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
16751 None of the cases where we did this before were wrong, but by making
16752 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
16753 - Fix a rare crash bug that could occur when a client was configured
16754 with a large number of bridges. Fixes bug 2629; bugfix on
16755 0.2.1.2-alpha. Bugfix by trac user "shitlei".
16756 - Correct the warning displayed when a rendezvous descriptor exceeds
16757 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
16759 - Fix an uncommon assertion failure when running with DNSPort under
16760 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
16761 - When warning about missing zlib development packages during compile,
16762 give the correct package names. Bugfix on 0.2.0.1-alpha.
16763 - Require that introduction point keys and onion keys have public
16764 exponent 65537. Bugfix on 0.2.0.10-alpha.
16765 - Do not crash when our configuration file becomes unreadable, for
16766 example due to a permissions change, between when we start up
16767 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
16769 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
16771 - Always NUL-terminate the sun_path field of a sockaddr_un before
16772 passing it to the kernel. (Not a security issue: kernels are
16773 smart enough to reject bad sockaddr_uns.) Found by Coverity;
16774 CID #428. Bugfix on Tor 0.2.0.3-alpha.
16775 - Don't stack-allocate the list of supplementary GIDs when we're
16776 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
16777 could take up to 256K, which is way too much stack. Found by
16778 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
16780 o Minor bugfixes (only in 0.2.1.x):
16781 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
16782 rely on them. Bugfix on 0.2.1.30.
16783 - Use git revisions instead of svn revisions when generating our
16784 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
16786 o Minor features (also included in 0.2.2.x):
16787 - Adjust the expiration time on our SSL session certificates to
16788 better match SSL certs seen in the wild. Resolves ticket 4014.
16789 - Allow nameservers with IPv6 address. Resolves bug 2574.
16790 - Update to the October 4 2011 Maxmind GeoLite Country database.
16793 Changes in version 0.2.3.5-alpha - 2011-09-28
16794 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
16795 bridge relays; fixes an assertion error that many users started hitting
16796 today; and adds the ability to refill token buckets more often than
16797 once per second, allowing significant performance improvements.
16800 - Bridge relays now do their directory fetches inside Tor TLS
16801 connections, like all the other clients do, rather than connecting
16802 directly to the DirPort like public relays do. Removes another
16803 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
16804 - Bridges relays now build circuits for themselves in a more similar
16805 way to how clients build them. Removes another avenue for
16806 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
16807 when bridges were introduced.
16810 - Fix an "Assertion md->held_by_node == 1 failed" error that could
16811 occur when the same microdescriptor was referenced by two node_t
16812 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
16814 o Major features (networking):
16815 - Add a new TokenBucketRefillInterval option to refill token buckets
16816 more frequently than once per second. This should improve network
16817 performance, alleviate queueing problems, and make traffic less
16818 bursty. Implements proposal 183; closes ticket 3630. Design by
16819 Florian Tschorsch and Björn Scheuermann; implementation by
16823 - Change an integer overflow check in the OpenBSD_Malloc code so
16824 that GCC is less likely to eliminate it as impossible. Patch
16825 from Mansour Moufid. Fixes bug 4059.
16827 o Minor bugfixes (usability):
16828 - Downgrade log messages about circuit timeout calibration from
16829 "notice" to "info": they don't require or suggest any human
16830 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
16831 bugfix on 0.2.2.14-alpha.
16833 o Minor features (diagnostics):
16834 - When the system call to create a listener socket fails, log the
16835 error message explaining why. This may help diagnose bug 4027.
16838 Changes in version 0.2.3.4-alpha - 2011-09-13
16839 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
16840 tweak to Tor's TLS handshake that makes relays and bridges that run
16841 this new version reachable from Iran again. It also fixes a few new
16842 bugs in 0.2.3.x, and teaches relays to recognize when they're not
16843 listed in the network consensus and republish.
16845 o Major bugfixes (also part of 0.2.2.33):
16846 - Avoid an assertion failure when reloading a configuration with
16847 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
16848 3923; bugfix on 0.2.2.25-alpha.
16850 o Minor features (security, also part of 0.2.2.33):
16851 - Check for replays of the public-key encrypted portion of an
16852 INTRODUCE1 cell, in addition to the current check for replays of
16853 the g^x value. This prevents a possible class of active attacks
16854 by an attacker who controls both an introduction point and a
16855 rendezvous point, and who uses the malleability of AES-CTR to
16856 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
16857 that these attacks are infeasible (requiring the attacker to send
16858 on the order of zettabytes of altered cells in a short interval),
16859 but we'd rather block them off in case there are any classes of
16860 this attack that we missed. Reported by Willem Pinckaers.
16862 o Minor features (also part of 0.2.2.33):
16863 - Adjust the expiration time on our SSL session certificates to
16864 better match SSL certs seen in the wild. Resolves ticket 4014.
16865 - Change the default required uptime for a relay to be accepted as
16866 a HSDir (hidden service directory) from 24 hours to 25 hours.
16867 Improves on 0.2.0.10-alpha; resolves ticket 2649.
16868 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
16869 authorities to abstain from voting on assignment of the HSDir
16870 consensus flag. Related to bug 2649.
16871 - Update to the September 6 2011 Maxmind GeoLite Country database.
16873 o Minor bugfixes (also part of 0.2.2.33):
16874 - Demote the 'replay detected' log message emitted when a hidden
16875 service receives the same Diffie-Hellman public key in two different
16876 INTRODUCE2 cells to info level. A normal Tor client can cause that
16877 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
16878 fixes part of bug 2442.
16879 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
16880 level. There is nothing that a hidden service's operator can do
16881 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
16883 - Clarify a log message specifying the characters permitted in
16884 HiddenServiceAuthorizeClient client names. Previously, the log
16885 message said that "[A-Za-z0-9+-_]" were permitted; that could have
16886 given the impression that every ASCII character between "+" and "_"
16887 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
16889 o Build fixes (also part of 0.2.2.33):
16890 - Clean up some code issues that prevented Tor from building on older
16891 BSDs. Fixes bug 3894; reported by "grarpamp".
16892 - Search for a platform-specific version of "ar" when cross-compiling.
16893 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
16896 - Fix a bug where the SocksPort option (for example) would get
16897 ignored and replaced by the default if a SocksListenAddress
16898 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
16902 - Relays now try regenerating and uploading their descriptor more
16903 frequently if they are not listed in the consensus, or if the
16904 version of their descriptor listed in the consensus is too
16905 old. This fix should prevent situations where a server declines
16906 to re-publish itself because it has done so too recently, even
16907 though the authorities decided not to list its recent-enough
16908 descriptor. Fix for bug 3327.
16911 - Relays now include a reason for regenerating their descriptors
16912 in an HTTP header when uploading to the authorities. This will
16913 make it easier to debug descriptor-upload issues in the future.
16914 - When starting as root and then changing our UID via the User
16915 control option, and we have a ControlSocket configured, make sure
16916 that the ControlSocket is owned by the same account that Tor will
16917 run under. Implements ticket 3421; fix by Jérémy Bobbio.
16920 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
16921 utility function used in the control-port code). This shouldn't
16922 ever happen unless Tor is completely out of memory, but if it did
16923 happen and Tor somehow recovered from it, Tor could have sent a log
16924 message to a control port in the middle of a reply to a controller
16925 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
16926 - Make 'FetchUselessDescriptors' cause all descriptor types and
16927 all consensus types (including microdescriptors) to get fetched.
16928 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
16930 o Code refactoring:
16931 - Make a new "entry connection" struct as an internal subtype of "edge
16932 connection", to simplify the code and make exit connections smaller.
16935 Changes in version 0.2.2.33 - 2011-09-13
16936 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
16937 TLS handshake that makes relays and bridges that run this new version
16938 reachable from Iran again.
16941 - Avoid an assertion failure when reloading a configuration with
16942 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
16943 3923; bugfix on 0.2.2.25-alpha.
16945 o Minor features (security):
16946 - Check for replays of the public-key encrypted portion of an
16947 INTRODUCE1 cell, in addition to the current check for replays of
16948 the g^x value. This prevents a possible class of active attacks
16949 by an attacker who controls both an introduction point and a
16950 rendezvous point, and who uses the malleability of AES-CTR to
16951 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
16952 that these attacks are infeasible (requiring the attacker to send
16953 on the order of zettabytes of altered cells in a short interval),
16954 but we'd rather block them off in case there are any classes of
16955 this attack that we missed. Reported by Willem Pinckaers.
16958 - Adjust the expiration time on our SSL session certificates to
16959 better match SSL certs seen in the wild. Resolves ticket 4014.
16960 - Change the default required uptime for a relay to be accepted as
16961 a HSDir (hidden service directory) from 24 hours to 25 hours.
16962 Improves on 0.2.0.10-alpha; resolves ticket 2649.
16963 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
16964 authorities to abstain from voting on assignment of the HSDir
16965 consensus flag. Related to bug 2649.
16966 - Update to the September 6 2011 Maxmind GeoLite Country database.
16968 o Minor bugfixes (documentation and log messages):
16969 - Correct the man page to explain that HashedControlPassword and
16970 CookieAuthentication can both be set, in which case either method
16971 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
16972 when we decided to allow these config options to both be set. Issue
16973 raised by bug 3898.
16974 - Demote the 'replay detected' log message emitted when a hidden
16975 service receives the same Diffie-Hellman public key in two different
16976 INTRODUCE2 cells to info level. A normal Tor client can cause that
16977 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
16978 fixes part of bug 2442.
16979 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
16980 level. There is nothing that a hidden service's operator can do
16981 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
16983 - Clarify a log message specifying the characters permitted in
16984 HiddenServiceAuthorizeClient client names. Previously, the log
16985 message said that "[A-Za-z0-9+-_]" were permitted; that could have
16986 given the impression that every ASCII character between "+" and "_"
16987 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
16990 - Provide a substitute implementation of lround() for MSVC, which
16991 apparently lacks it. Patch from Gisle Vanem.
16992 - Clean up some code issues that prevented Tor from building on older
16993 BSDs. Fixes bug 3894; reported by "grarpamp".
16994 - Search for a platform-specific version of "ar" when cross-compiling.
16995 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
16998 Changes in version 0.2.3.3-alpha - 2011-09-01
16999 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
17000 security, and provides client-side support for the microdescriptor
17001 and optimistic data features introduced earlier in the 0.2.3.x
17002 series. It also includes numerous critical bugfixes in the (optional)
17003 bufferevent-based networking backend.
17005 o Major features (stream isolation):
17006 - You can now configure Tor so that streams from different
17007 applications are isolated on different circuits, to prevent an
17008 attacker who sees your streams as they leave an exit node from
17009 linking your sessions to one another. To do this, choose some way
17010 to distinguish the applications: have them connect to different
17011 SocksPorts, or have one of them use SOCKS4 while the other uses
17012 SOCKS5, or have them pass different authentication strings to the
17013 SOCKS proxy. Then, use the new SocksPort syntax to configure the
17014 degree of isolation you need. This implements Proposal 171.
17015 - There's a new syntax for specifying multiple client ports (such as
17016 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
17017 multiple *Port entries with full addr:port syntax on each.
17018 The old *ListenAddress format is still supported, but you can't
17019 mix it with the new *Port syntax.
17021 o Major features (other):
17022 - Enable microdescriptor fetching by default for clients. This allows
17023 clients to download a much smaller amount of directory information.
17024 To disable it (and go back to the old-style consensus and
17025 descriptors), set "UseMicrodescriptors 0" in your torrc file.
17026 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
17027 "PortForwarding" config option), now supports Windows.
17028 - When using an exit relay running 0.2.3.x, clients can now
17029 "optimistically" send data before the exit relay reports that
17030 the stream has opened. This saves a round trip when starting
17031 connections where the client speaks first (such as web browsing).
17032 This behavior is controlled by a consensus parameter (currently
17033 disabled). To turn it on or off manually, use the "OptimisticData"
17034 torrc option. Implements proposal 181; code by Ian Goldberg.
17036 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
17037 - When using IOCP on Windows, we need to enable Libevent windows
17039 - The IOCP backend now works even when the user has not specified
17040 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
17041 Fixes part of bug 3752.
17042 - Correctly record the bytes we've read and written when using
17043 bufferevents, so that we can include them in our bandwidth history
17044 and advertised bandwidth. Fixes bug 3803.
17045 - Apply rate-limiting only at the bottom of a chain of filtering
17046 bufferevents. This prevents us from filling up internal read
17047 buffers and violating rate-limits when filtering bufferevents
17048 are enabled. Fixes part of bug 3804.
17049 - Add high-watermarks to the output buffers for filtered
17050 bufferevents. This prevents us from filling up internal write
17051 buffers and wasting CPU cycles when filtering bufferevents are
17052 enabled. Fixes part of bug 3804.
17053 - Correctly notice when data has been written from a bufferevent
17054 without flushing it completely. Fixes bug 3805.
17055 - Fix a bug where server-side tunneled bufferevent-based directory
17056 streams would get closed prematurely. Fixes bug 3814.
17057 - Fix a use-after-free error with per-connection rate-limiting
17058 buckets. Fixes bug 3888.
17060 o Major bugfixes (also part of 0.2.2.31-rc):
17061 - If we're configured to write our ControlPorts to disk, only write
17062 them after switching UID and creating the data directory. This way,
17063 we don't fail when starting up with a nonexistent DataDirectory
17064 and a ControlPortWriteToFile setting based on that directory. Fixes
17065 bug 3747; bugfix on Tor 0.2.2.26-beta.
17068 - Added a new CONF_CHANGED event so that controllers can be notified
17069 of any configuration changes made by other controllers, or by the
17070 user. Implements ticket 1692.
17071 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
17072 leak when using bufferevents, and lets Libevent worry about how to
17073 best copy data out of a buffer.
17074 - Replace files in stats/ rather than appending to them. Now that we
17075 include statistics in extra-info descriptors, it makes no sense to
17076 keep old statistics forever. Implements ticket 2930.
17078 o Minor features (build compatibility):
17079 - Limited, experimental support for building with nmake and MSVC.
17080 - Provide a substitute implementation of lround() for MSVC, which
17081 apparently lacks it. Patch from Gisle Vanem.
17083 o Minor features (also part of 0.2.2.31-rc):
17084 - Update to the August 2 2011 Maxmind GeoLite Country database.
17086 o Minor bugfixes (on 0.2.3.x-alpha):
17087 - Fix a spurious warning when parsing SOCKS requests with
17088 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
17089 - Get rid of a harmless warning that could happen on relays running
17090 with bufferevents. The warning was caused by someone doing an http
17091 request to a relay's orport. Also don't warn for a few related
17092 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
17094 o Minor bugfixes (on 2.2.x and earlier):
17095 - Correct the man page to explain that HashedControlPassword and
17096 CookieAuthentication can both be set, in which case either method
17097 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
17098 when we decided to allow these config options to both be set. Issue
17099 raised by bug 3898.
17100 - The "--quiet" and "--hush" options now apply not only to Tor's
17101 behavior before logs are configured, but also to Tor's behavior in
17102 the absence of configured logs. Fixes bug 3550; bugfix on
17105 o Minor bugfixes (also part of 0.2.2.31-rc):
17106 - Write several files in text mode, on OSes that distinguish text
17107 mode from binary mode (namely, Windows). These files are:
17108 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
17109 that collect those statistics; 'client_keys' and 'hostname' for
17110 hidden services that use authentication; and (in the tor-gencert
17111 utility) newly generated identity and signing keys. Previously,
17112 we wouldn't specify text mode or binary mode, leading to an
17113 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
17114 the DirRecordUsageByCountry option which would have triggered
17115 the assertion failure was added), although this assertion failure
17116 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
17117 - Selectively disable deprecation warnings on OS X because Lion
17118 started deprecating the shipped copy of openssl. Fixes bug 3643.
17119 - Remove an extra pair of quotation marks around the error
17120 message in control-port STATUS_GENERAL BUG events. Bugfix on
17121 0.1.2.6-alpha; fixes bug 3732.
17122 - When unable to format an address as a string, report its value
17123 as "???" rather than reusing the last formatted address. Bugfix
17126 o Code simplifications and refactoring:
17127 - Rewrite the listener-selection logic so that parsing which ports
17128 we want to listen on is now separate from binding to the ports
17132 - Building Tor with bufferevent support now requires Libevent
17133 2.0.13-stable or later. Previous versions of Libevent had bugs in
17134 SSL-related bufferevents and related issues that would make Tor
17135 work badly with bufferevents. Requiring 2.0.13-stable also allows
17136 Tor with bufferevents to take advantage of Libevent APIs
17137 introduced after 2.0.8-rc.
17140 Changes in version 0.2.2.32 - 2011-08-27
17141 The Tor 0.2.2 release series is dedicated to the memory of Andreas
17142 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
17143 a founder of the PETS community, a leader in our field, a mentor,
17144 and a friend. He left us with these words: "I had the possibility
17145 to contribute to this world that is not as it should be. I hope I
17146 could help in some areas to make the world a better place, and that
17147 I could also encourage other people to be engaged in improving the
17148 world. Please, stay engaged. This world needs you, your love, your
17149 initiative -- now I cannot be part of that anymore."
17151 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
17152 ready. More than two years in the making, this release features improved
17153 client performance and hidden service reliability, better compatibility
17154 for Android, correct behavior for bridges that listen on more than
17155 one address, more extensible and flexible directory object handling,
17156 better reporting of network statistics, improved code security, and
17157 many many other features and bugfixes.
17160 Changes in version 0.2.2.31-rc - 2011-08-17
17161 Tor 0.2.2.31-rc is the second and hopefully final release candidate
17162 for the Tor 0.2.2.x series.
17165 - Remove an extra pair of quotation marks around the error
17166 message in control-port STATUS_GENERAL BUG events. Bugfix on
17167 0.1.2.6-alpha; fixes bug 3732.
17168 - If we're configured to write our ControlPorts to disk, only write
17169 them after switching UID and creating the data directory. This way,
17170 we don't fail when starting up with a nonexistent DataDirectory
17171 and a ControlPortWriteToFile setting based on that directory. Fixes
17172 bug 3747; bugfix on Tor 0.2.2.26-beta.
17175 - Update to the August 2 2011 Maxmind GeoLite Country database.
17178 - Allow GETINFO fingerprint to return a fingerprint even when
17179 we have not yet built a router descriptor. Fixes bug 3577;
17180 bugfix on 0.2.0.1-alpha.
17181 - Write several files in text mode, on OSes that distinguish text
17182 mode from binary mode (namely, Windows). These files are:
17183 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
17184 that collect those statistics; 'client_keys' and 'hostname' for
17185 hidden services that use authentication; and (in the tor-gencert
17186 utility) newly generated identity and signing keys. Previously,
17187 we wouldn't specify text mode or binary mode, leading to an
17188 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
17189 the DirRecordUsageByCountry option which would have triggered
17190 the assertion failure was added), although this assertion failure
17191 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
17192 - Selectively disable deprecation warnings on OS X because Lion
17193 started deprecating the shipped copy of openssl. Fixes bug 3643.
17194 - When unable to format an address as a string, report its value
17195 as "???" rather than reusing the last formatted address. Bugfix
17199 Changes in version 0.2.3.2-alpha - 2011-07-18
17200 Tor 0.2.3.2-alpha introduces two new experimental features:
17201 microdescriptors and pluggable transports. It also continues cleaning
17202 up a variety of recently introduced features.
17205 - Clients can now use microdescriptors instead of regular descriptors
17206 to build circuits. Microdescriptors are authority-generated
17207 summaries of regular descriptors' contents, designed to change
17208 very rarely (see proposal 158 for details). This feature is
17209 designed to save bandwidth, especially for clients on slow internet
17210 connections. It's off by default for now, since nearly no caches
17211 support it, but it will be on-by-default for clients in a future
17212 version. You can use the UseMicrodescriptors option to turn it on.
17213 - Tor clients using bridges can now be configured to use a separate
17214 'transport' proxy for each bridge. This approach helps to resist
17215 censorship by allowing bridges to use protocol obfuscation
17216 plugins. It implements part of proposal 180. Implements ticket 2841.
17217 - While we're trying to bootstrap, record how many TLS connections
17218 fail in each state, and report which states saw the most failures
17219 in response to any bootstrap failures. This feature may speed up
17220 diagnosis of censorship events. Implements ticket 3116.
17222 o Major bugfixes (on 0.2.3.1-alpha):
17223 - When configuring a large set of nodes in EntryNodes (as with
17224 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
17225 random subset to be guards, and choose them in random
17226 order. Fixes bug 2798.
17227 - Tor could crash when remembering a consensus in a non-used consensus
17228 flavor without having a current consensus set. Fixes bug 3361.
17229 - Comparing an unknown address to a microdescriptor's shortened exit
17230 policy would always give a "rejected" result. Fixes bug 3599.
17231 - Using microdescriptors as a client no longer prevents Tor from
17232 uploading and downloading hidden service descriptors. Fixes
17236 - Allow nameservers with IPv6 address. Resolves bug 2574.
17237 - Accept attempts to include a password authenticator in the
17238 handshake, as supported by SOCKS5. This handles SOCKS clients that
17239 don't know how to omit a password when authenticating. Resolves
17241 - When configuring a large set of nodes in EntryNodes, and there are
17242 enough of them listed as Guard so that we don't need to consider
17243 the non-guard entries, prefer the ones listed with the Guard flag.
17244 - Check for and recover from inconsistency in the microdescriptor
17245 cache. This will make it harder for us to accidentally free a
17246 microdescriptor without removing it from the appropriate data
17247 structures. Fixes issue 3135; issue noted by "wanoskarnet".
17248 - Log SSL state transitions at log level DEBUG, log domain
17249 HANDSHAKE. This can be useful for debugging censorship events.
17250 Implements ticket 3264.
17251 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
17252 implements ticket 3439.
17254 o Minor bugfixes (on 0.2.3.1-alpha):
17255 - Do not free all general-purpose regular descriptors just
17256 because microdescriptor use is enabled. Fixes bug 3113.
17257 - Correctly link libevent_openssl when --enable-static-libevent
17258 is passed to configure. Fixes bug 3118.
17259 - Bridges should not complain during their heartbeat log messages that
17260 they are unlisted in the consensus: that's more or less the point
17261 of being a bridge. Fixes bug 3183.
17262 - Report a SIGNAL event to controllers when acting on a delayed
17263 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
17264 event to the controller if we acted on a SIGNAL NEWNYM command
17265 immediately, and otherwise not report a SIGNAL event for the
17266 command at all. Fixes bug 3349.
17267 - Fix a crash when handling the SIGNAL controller command or
17268 reporting ERR-level status events with bufferevents enabled. Found
17269 by Robert Ransom. Fixes bug 3367.
17270 - Always ship the tor-fw-helper manpage in our release tarballs.
17271 Fixes bug 3389. Reported by Stephen Walker.
17272 - Fix a class of double-mark-for-close bugs when bufferevents
17273 are enabled. Fixes bug 3403.
17274 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
17275 - Add SIGNAL to the list returned by the 'GETINFO events/names'
17276 control-port command. Fixes part of bug 3465.
17277 - Prevent using negative indices during unit test runs when read_all()
17278 fails. Spotted by coverity.
17279 - Fix a rare memory leak when checking the nodelist without it being
17280 present. Found by coverity.
17281 - Only try to download a microdescriptor-flavored consensus from
17282 a directory cache that provides them.
17284 o Minor bugfixes (on 0.2.2.x and earlier):
17285 - Assert that hidden-service-related operations are not performed
17286 using single-hop circuits. Previously, Tor would assert that
17287 client-side streams are not attached to single-hop circuits,
17288 but not that other sensitive operations on the client and service
17289 side are not performed using single-hop circuits. Fixes bug 3332;
17291 - Don't publish a new relay descriptor when we reload our onion key,
17292 unless the onion key has actually changed. Fixes bug 3263 and
17293 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
17294 - Allow GETINFO fingerprint to return a fingerprint even when
17295 we have not yet built a router descriptor. Fixes bug 3577;
17296 bugfix on 0.2.0.1-alpha.
17297 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
17298 on 0.2.2.4-alpha; fixes bug 3427.
17300 o Code simplification and refactoring:
17301 - Use tor_sscanf() in place of scanf() in more places through the
17302 code. This makes us a little more locale-independent, and
17303 should help shut up code-analysis tools that can't tell
17304 a safe sscanf string from a dangerous one.
17305 - Use tt_assert(), not tor_assert(), for checking for test failures.
17306 This makes the unit tests more able to go on in the event that
17308 - Split connection_about_to_close() into separate functions for each
17312 - On Windows, we now define the _WIN32_WINNT macros only if they
17313 are not already defined. This lets the person building Tor decide,
17314 if they want, to require a later version of Windows.
17317 Changes in version 0.2.2.30-rc - 2011-07-07
17318 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
17319 series. It fixes a few smaller bugs, but generally appears stable.
17320 Please test it and let us know whether it is!
17323 - Send a SUCCEEDED stream event to the controller when a reverse
17324 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
17325 discovered by katmagic.
17326 - Always NUL-terminate the sun_path field of a sockaddr_un before
17327 passing it to the kernel. (Not a security issue: kernels are
17328 smart enough to reject bad sockaddr_uns.) Found by Coverity;
17329 CID #428. Bugfix on Tor 0.2.0.3-alpha.
17330 - Don't stack-allocate the list of supplementary GIDs when we're
17331 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
17332 could take up to 256K, which is way too much stack. Found by
17333 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
17334 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
17335 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
17336 fixes part of bug 3465.
17337 - Fix a memory leak when receiving a descriptor for a hidden
17338 service we didn't ask for. Found by Coverity; CID #30. Bugfix
17342 - Update to the July 1 2011 Maxmind GeoLite Country database.
17345 Changes in version 0.2.2.29-beta - 2011-06-20
17346 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
17347 have bridge lines in their torrc but don't want to use them; gets
17348 us closer to having the control socket feature working on Debian;
17349 and fixes a variety of smaller bugs.
17352 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
17353 When we changed the default behavior to "use bridges if any
17354 are listed in the torrc", we surprised users who had bridges
17355 in their torrc files but who didn't actually want to use them.
17356 Partial resolution for bug 3354.
17359 - Don't attach new streams to old rendezvous circuits after SIGNAL
17360 NEWNYM. Previously, we would keep using an existing rendezvous
17361 circuit if it remained open (i.e. if it were kept open by a
17362 long-lived stream, or if a new stream were attached to it before
17363 Tor could notice that it was old and no longer in use). Bugfix on
17364 0.1.1.15-rc; fixes bug 3375.
17367 - Fix a bug when using ControlSocketsGroupWritable with User. The
17368 directory's group would be checked against the current group, not
17369 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
17370 bugfix on 0.2.2.26-beta.
17371 - Make connection_printf_to_buf()'s behavior sane. Its callers
17372 expect it to emit a CRLF iff the format string ends with CRLF;
17373 it actually emitted a CRLF iff (a) the format string ended with
17374 CRLF or (b) the resulting string was over 1023 characters long or
17375 (c) the format string did not end with CRLF *and* the resulting
17376 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
17377 fixes part of bug 3407.
17378 - Make send_control_event_impl()'s behavior sane. Its callers
17379 expect it to always emit a CRLF at the end of the string; it
17380 might have emitted extra control characters as well. Bugfix on
17381 0.1.1.9-alpha; fixes another part of bug 3407.
17382 - Make crypto_rand_int() check the value of its input correctly.
17383 Previously, it accepted values up to UINT_MAX, but could return a
17384 negative number if given a value above INT_MAX+1. Found by George
17385 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
17386 - Avoid a segfault when reading a malformed circuit build state
17387 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
17389 - When asked about a DNS record type we don't support via a
17390 client DNSPort, reply with NOTIMPL rather than an empty
17391 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
17392 - Fix a rare memory leak during stats writing. Found by coverity.
17395 - Update to the June 1 2011 Maxmind GeoLite Country database.
17397 o Code simplifications and refactoring:
17398 - Remove some dead code as indicated by coverity.
17399 - Remove a few dead assignments during router parsing. Found by
17401 - Add some forgotten return value checks during unit tests. Found
17403 - Don't use 1-bit wide signed bit fields. Found by coverity.
17406 Changes in version 0.2.2.28-beta - 2011-06-04
17407 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
17408 fixed a big bug in whether relays stay in the consensus consistently,
17409 we moved closer to handling bridges and hidden services correctly,
17410 and we started the process of better handling the dreaded "my Vidalia
17411 died, and now my Tor demands a password when I try to reconnect to it"
17415 - Don't decide to make a new descriptor when receiving a HUP signal.
17416 This bug has caused a lot of 0.2.2.x relays to disappear from the
17417 consensus periodically. Fixes the most common case of triggering
17418 bug 1810; bugfix on 0.2.2.7-alpha.
17419 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
17420 - Don't try to build descriptors if "ORPort auto" is set and we
17421 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
17423 - Resolve a crash that occurred when setting BridgeRelay to 1 with
17424 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
17425 - Apply circuit timeouts to opened hidden-service-related circuits
17426 based on the correct start time. Previously, we would apply the
17427 circuit build timeout based on time since the circuit's creation;
17428 it was supposed to be applied based on time since the circuit
17429 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
17430 - Use the same circuit timeout for client-side introduction
17431 circuits as for other four-hop circuits, rather than the timeout
17432 for single-hop directory-fetch circuits; the shorter timeout may
17433 have been appropriate with the static circuit build timeout in
17434 0.2.1.x and earlier, but caused many hidden service access attempts
17435 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
17436 on 0.2.2.2-alpha; fixes another part of bug 1297.
17437 - In ticket 2511 we fixed a case where you could use an unconfigured
17438 bridge if you had configured it as a bridge the last time you ran
17439 Tor. Now fix another edge case: if you had configured it as a bridge
17440 but then switched to a different bridge via the controller, you
17441 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
17445 - Add an __OwningControllerProcess configuration option and a
17446 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
17447 that when it exits, Tor will shut down. Implements feature 3049.
17448 - If "UseBridges 1" is set and no bridges are configured, Tor will
17449 now refuse to build any circuits until some bridges are set.
17450 If "UseBridges auto" is set, Tor will use bridges if they are
17451 configured and we are not running as a server, but otherwise will
17452 make circuits as usual. The new default is "auto". Patch by anonym,
17453 so the Tails LiveCD can stop automatically revealing you as a Tor
17457 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
17458 - Remove a trailing asterisk from "exit-policy/default" in the
17459 output of the control port command "GETINFO info/names". Bugfix
17461 - Use a wide type to hold sockets when built for 64-bit Windows builds.
17463 - Warn when the user configures two HiddenServiceDir lines that point
17464 to the same directory. Bugfix on 0.0.6 (the version introducing
17465 HiddenServiceDir); fixes bug 3289.
17466 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
17467 part of bug 2748; bugfix on 0.2.0.10-alpha.
17468 - Log malformed requests for rendezvous descriptors as protocol
17469 warnings, not warnings. Also, use a more informative log message
17470 in case someone sees it at log level warning without prior
17471 info-level messages. Fixes the other part of bug 2748; bugfix
17473 - Clear the table recording the time of the last request for each
17474 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
17475 Previously, we would clear our HS descriptor cache on SIGNAL
17476 NEWNYM, but if we had previously retrieved a descriptor (or tried
17477 to) from every directory responsible for it, we would refuse to
17478 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
17480 - Fix a log message that said "bits" while displaying a value in
17481 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
17483 - When checking for 1024-bit keys, check for 1024 bits, not 128
17484 bytes. This allows Tor to correctly discard keys of length 1017
17485 through 1023. Bugfix on 0.0.9pre5.
17488 - Relays now log the reason for publishing a new relay descriptor,
17489 so we have a better chance of hunting down instances of bug 1810.
17490 Resolves ticket 3252.
17491 - Revise most log messages that refer to nodes by nickname to
17492 instead use the "$key=nickname at address" format. This should be
17493 more useful, especially since nicknames are less and less likely
17494 to be unique. Resolves ticket 3045.
17495 - Log (at info level) when purging pieces of hidden-service-client
17496 state because of SIGNAL NEWNYM.
17499 - Remove undocumented option "-F" from tor-resolve: it hasn't done
17500 anything since 0.2.1.16-rc.
17503 Changes in version 0.2.2.27-beta - 2011-05-18
17504 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
17505 release, and also adds a few more general bugfixes.
17508 - Fix a crash bug when changing bridges in a running Tor process.
17509 Fixes bug 3213; bugfix on 0.2.2.26-beta.
17510 - When the controller configures a new bridge, don't wait 10 to 60
17511 seconds before trying to fetch its descriptor. Bugfix on
17512 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
17515 - Require that onion keys have exponent 65537 in microdescriptors too.
17516 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
17517 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
17518 Changed the limit to 512 characters by removing base64 newlines.
17519 Fixes bug 2752. Fix by Michael Yakubovich.
17520 - When a client starts or stops using bridges, never use a circuit
17521 that was built before the configuration change. This behavior could
17522 put at risk a user who uses bridges to ensure that her traffic
17523 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
17527 Changes in version 0.2.2.26-beta - 2011-05-17
17528 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
17529 also introduces a new "socksport auto" approach that should make it
17530 easier to run multiple Tors on the same system, and does a lot of
17531 cleanup to get us closer to a release candidate.
17533 o Security/privacy fixes:
17534 - Replace all potentially sensitive memory comparison operations
17535 with versions whose runtime does not depend on the data being
17536 compared. This will help resist a class of attacks where an
17537 adversary can use variations in timing information to learn
17538 sensitive data. Fix for one case of bug 3122. (Safe memcmp
17539 implementation by Robert Ransom based partially on code by DJB.)
17540 - When receiving a hidden service descriptor, check that it is for
17541 the hidden service we wanted. Previously, Tor would store any
17542 hidden service descriptors that a directory gave it, whether it
17543 wanted them or not. This wouldn't have let an attacker impersonate
17544 a hidden service, but it did let directories pre-seed a client
17545 with descriptors that it didn't want. Bugfix on 0.0.6.
17546 - On SIGHUP, do not clear out all TrackHostExits mappings, client
17547 DNS cache entries, and virtual address mappings: that's what
17548 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
17551 - The options SocksPort, ControlPort, and so on now all accept a
17552 value "auto" that opens a socket on an OS-selected port. A
17553 new ControlPortWriteToFile option tells Tor to write its
17554 actual control port or ports to a chosen file. If the option
17555 ControlPortFileGroupReadable is set, the file is created as
17556 group-readable. Now users can run two Tor clients on the same
17557 system without needing to manually mess with parameters. Resolves
17558 part of ticket 3076.
17559 - Set SO_REUSEADDR on all sockets, not just listeners. This should
17560 help busy exit nodes avoid running out of useable ports just
17561 because all the ports have been used in the near past. Resolves
17565 - New "GETINFO net/listeners/(type)" controller command to return
17566 a list of addresses and ports that are bound for listeners for a
17567 given connection type. This is useful when the user has configured
17568 "SocksPort auto" and the controller needs to know which port got
17569 chosen. Resolves another part of ticket 3076.
17570 - Add a new ControlSocketsGroupWritable configuration option: when
17571 it is turned on, ControlSockets are group-writeable by the default
17572 group of the current user. Patch by Jérémy Bobbio; implements
17574 - Tor now refuses to create a ControlSocket in a directory that is
17575 world-readable (or group-readable if ControlSocketsGroupWritable
17576 is 0). This is necessary because some operating systems do not
17577 enforce permissions on an AF_UNIX sockets. Permissions on the
17578 directory holding the socket, however, seems to work everywhere.
17579 - Rate-limit a warning about failures to download v2 networkstatus
17580 documents. Resolves part of bug 1352.
17581 - Backport code from 0.2.3.x that allows directory authorities to
17582 clean their microdescriptor caches. Needed to resolve bug 2230.
17583 - When an HTTPS proxy reports "403 Forbidden", we now explain
17584 what it means rather than calling it an unexpected status code.
17585 Closes bug 2503. Patch from Michael Yakubovich.
17586 - Update to the May 1 2011 Maxmind GeoLite Country database.
17589 - Authorities now clean their microdesc cache periodically and when
17590 reading from disk initially, not only when adding new descriptors.
17591 This prevents a bug where we could lose microdescriptors. Bugfix
17592 on 0.2.2.6-alpha. Fixes bug 2230.
17593 - Do not crash when our configuration file becomes unreadable, for
17594 example due to a permissions change, between when we start up
17595 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
17597 - Avoid a bug that would keep us from replacing a microdescriptor
17598 cache on Windows. (We would try to replace the file while still
17599 holding it open. That's fine on Unix, but Windows doesn't let us
17600 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
17601 - Add missing explanations for the authority-related torrc options
17602 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
17603 man page. Resolves issue 2379.
17604 - As an authority, do not upload our own vote or signature set to
17605 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
17606 it would get flagged as a duplicate. Resolves bug 3026.
17607 - Accept hidden service descriptors if we think we might be a hidden
17608 service directory, regardless of what our consensus says. This
17609 helps robustness, since clients and hidden services can sometimes
17610 have a more up-to-date view of the network consensus than we do,
17611 and if they think that the directory authorities list us a HSDir,
17612 we might actually be one. Related to bug 2732; bugfix on
17614 - When a controller changes TrackHostExits, remove mappings for
17615 hosts that should no longer have their exits tracked. Bugfix on
17617 - When a controller changes VirtualAddrNetwork, remove any mappings
17618 for hosts that were automapped to the old network. Bugfix on
17620 - When a controller changes one of the AutomapHosts* options, remove
17621 any mappings for hosts that should no longer be automapped. Bugfix
17623 - Do not reset the bridge descriptor download status every time we
17624 re-parse our configuration or get a configuration change. Fixes
17625 bug 3019; bugfix on 0.2.0.3-alpha.
17627 o Minor bugfixes (code cleanup):
17628 - When loading the microdesc journal, remember its current size.
17629 In 0.2.2, this helps prevent the microdesc journal from growing
17630 without limit on authorities (who are the only ones to use it in
17631 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
17632 Fix posted by "cypherpunks."
17633 - The microdesc journal is supposed to get rebuilt only if it is
17634 at least _half_ the length of the store, not _twice_ the length
17635 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
17636 - Fix a potential null-pointer dereference while computing a
17637 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
17639 - Avoid a possible null-pointer dereference when rebuilding the mdesc
17640 cache without actually having any descriptors to cache. Bugfix on
17641 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
17642 - If we fail to compute the identity digest of a v3 legacy keypair,
17643 warn, and don't use a buffer-full of junk instead. Bugfix on
17644 0.2.1.1-alpha; fixes bug 3106.
17645 - Resolve an untriggerable issue in smartlist_string_num_isin(),
17646 where if the function had ever in the future been used to check
17647 for the presence of a too-large number, it would have given an
17648 incorrect result. (Fortunately, we only used it for 16-bit
17649 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
17650 - Require that introduction point keys and onion handshake keys
17651 have a public exponent of 65537. Starts to fix bug 3207; bugfix
17654 o Removed features:
17655 - Caches no longer download and serve v2 networkstatus documents
17656 unless FetchV2Networkstatus flag is set: these documents haven't
17657 haven't been used by clients or relays since 0.2.0.x. Resolves
17661 Changes in version 0.2.3.1-alpha - 2011-05-05
17662 Tor 0.2.3.1-alpha adds some new experimental features, including support
17663 for an improved network IO backend, IOCP networking on Windows,
17664 microdescriptor caching, "fast-start" support for streams, and automatic
17665 home router configuration. There are also numerous internal improvements
17666 to try to make the code easier for developers to work with.
17668 This is the first alpha release in a new series, so expect there to be
17669 bugs. Users who would rather test out a more stable branch should
17670 stay with 0.2.2.x for now.
17673 - Tor can now optionally build with the "bufferevents" buffered IO
17674 backend provided by Libevent 2. To use this feature, make sure you
17675 have the latest possible version of Libevent, and pass the
17676 --enable-bufferevents flag to configure when building Tor from
17677 source. This feature will make our networking code more flexible,
17678 let us stack layers on each other, and let us use more efficient
17679 zero-copy transports where available.
17680 - As an experimental feature, Tor can use IOCP for networking on Windows.
17681 Once this code is tuned and optimized, it promises much better
17682 performance than the select-based backend we've used in the past. To
17683 try this feature, you must build Tor with Libevent 2, configure Tor
17684 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
17685 your torrc. There are known bugs here: only try this if you can help
17686 debug it as it breaks.
17687 - The EntryNodes option can now include country codes like {de} or IP
17688 addresses or network masks. Previously we had disallowed these options
17689 because we didn't have an efficient way to keep the list up to
17690 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
17691 - Exit nodes now accept and queue data on not-yet-connected streams.
17692 Previously, the client wasn't allowed to send data until the stream was
17693 connected, which slowed down all connections. This change will enable
17694 clients to perform a "fast-start" on streams and send data without
17695 having to wait for a confirmation that the stream has opened. (Patch
17696 from Ian Goldberg; implements the server side of Proposal 174.)
17697 - Tor now has initial support for automatic port mapping on the many
17698 home routers that support NAT-PMP or UPnP. (Not yet supported on
17699 Windows). To build the support code, you'll need to have libnatpnp
17700 library and/or the libminiupnpc library, and you'll need to enable the
17701 feature specifically by passing "--enable-upnp" and/or
17702 "--enable-natpnp" to configure. To turn it on, use the new
17703 PortForwarding option.
17704 - Caches now download, cache, and serve multiple "flavors" of the
17705 consensus, including a flavor that describes microdescriptors.
17706 - Caches now download, cache, and serve microdescriptors -- small
17707 summaries of router descriptors that are authenticated by all of the
17708 directory authorities. Once enough caches are running this code,
17709 clients will be able to save significant amounts of directory bandwidth
17710 by downloading microdescriptors instead of router descriptors.
17713 - Make logging resolution configurable with a new LogTimeGranularity
17714 option, and change the default from 1 millisecond to 1 second.
17715 Implements enhancement 1668.
17716 - We log which torrc file we're using on startup. Implements ticket
17718 - Ordinarily, Tor does not count traffic from private addresses (like
17719 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
17720 There is now a new option, CountPrivateBandwidth, to disable this
17721 behavior. Patch from Daniel Cagara.
17722 - New --enable-static-tor configure option for building Tor as
17723 statically as possible. Idea, general hackery and thoughts from
17724 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
17726 - If you set the NumCPUs option to 0, Tor will now try to detect how
17727 many CPUs you have. This is the new default behavior.
17728 - Turn on directory request statistics by default and include them in
17729 extra-info descriptors. Don't break if we have no GeoIP database.
17730 - Relays that set "ConnDirectionStatistics 1" write statistics on the
17731 bidirectional use of connections to disk every 24 hours.
17732 - Add a GeoIP file digest to the extra-info descriptor. Implements
17734 - The NodeFamily option -- which let you declare that you want to
17735 consider nodes to be part of a family whether they list themselves
17736 that way or not -- now allows IP address ranges and country codes.
17737 - Add a new 'Heartbeat' log message type to periodically log a message
17738 describing Tor's status at level Notice. This feature is meant for
17739 operators who log at notice, and want to make sure that their Tor
17740 server is still working. Implementation by George Kadianakis.
17742 o Minor bugfixes (on 0.2.2.25-alpha):
17743 - When loading the microdesc journal, remember its current size.
17744 In 0.2.2, this helps prevent the microdesc journal from growing
17745 without limit on authorities (who are the only ones to use it in
17746 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
17747 Fix posted by "cypherpunks."
17748 - The microdesc journal is supposed to get rebuilt only if it is
17749 at least _half_ the length of the store, not _twice_ the length
17750 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
17751 - If as an authority we fail to compute the identity digest of a v3
17752 legacy keypair, warn, and don't use a buffer-full of junk instead.
17753 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
17754 - Authorities now clean their microdesc cache periodically and when
17755 reading from disk initially, not only when adding new descriptors.
17756 This prevents a bug where we could lose microdescriptors. Bugfix
17759 o Minor features (controller):
17760 - Add a new SIGNAL event to the controller interface so that
17761 controllers can be notified when Tor handles a signal. Resolves
17762 issue 1955. Patch by John Brooks.
17763 - Add a new GETINFO option to get total bytes read and written. Patch
17764 from pipe, revised by atagar. Resolves ticket 2345.
17765 - Implement some GETINFO controller fields to provide information about
17766 the Tor process's pid, euid, username, and resource limits.
17769 - Our build system requires automake 1.6 or later to create the
17770 Makefile.in files. Previously, you could have used 1.4.
17771 This only affects developers and people building Tor from git;
17772 people who build Tor from the source distribution without changing
17773 the Makefile.am files should be fine.
17774 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
17775 so on. This is more robust against some of the failure modes
17776 associated with running the autotools pieces on their own.
17778 o Minor packaging issues:
17779 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
17780 already created. Patch from Andreas Stieger. Fixes bug 2573.
17782 o Code simplifications and refactoring:
17783 - A major revision to our internal node-selecting and listing logic.
17784 Tor already had at least two major ways to look at the question of
17785 "which Tor servers do we know about": a list of router descriptors,
17786 and a list of entries in the current consensus. With
17787 microdescriptors, we're adding a third. Having so many systems
17788 without an abstraction layer over them was hurting the codebase.
17789 Now, we have a new "node_t" abstraction that presents a consistent
17790 interface to a client's view of a Tor node, and holds (nearly) all
17791 of the mutable state formerly in routerinfo_t and routerstatus_t.
17792 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
17793 no longer link against Libevent: they never used it, but
17794 our library structure used to force them to link it.
17796 o Removed features:
17797 - Remove some old code to work around even older versions of Tor that
17798 used forked processes to handle DNS requests. Such versions of Tor
17799 are no longer in use as servers.
17801 o Documentation fixes:
17802 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
17803 - Add missing documentation for the authority-related torrc options
17804 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
17808 Changes in version 0.2.2.25-alpha - 2011-04-29
17809 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
17810 robust, routers no longer overreport their bandwidth, Win7 should crash
17811 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
17812 now prevents hidden service-related activity from being linkable. It
17813 provides more information to Vidalia so you can see if your bridge is
17814 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
17815 StrictNodes configuration options to make them more reliable, more
17816 understandable, and more regularly applied. If you use those options,
17817 please see the revised documentation for them in the manual page.
17820 - Relays were publishing grossly inflated bandwidth values because
17821 they were writing their state files wrong--now they write the
17822 correct value. Also, resume reading bandwidth history from the
17823 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
17824 - Improve hidden service robustness: When we find that we have
17825 extended a hidden service's introduction circuit to a relay not
17826 listed as an introduction point in the HS descriptor we currently
17827 have, retry with an introduction point from the current
17828 descriptor. Previously we would just give up. Fixes bugs 1024 and
17829 1930; bugfix on 0.2.0.10-alpha.
17830 - Clients now stop trying to use an exit node associated with a given
17831 destination by TrackHostExits if they fail to reach that exit node.
17832 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
17833 - Fix crash bug on platforms where gmtime and localtime can return
17834 NULL. Windows 7 users were running into this one. Fixes part of bug
17835 2077. Bugfix on all versions of Tor. Found by boboper.
17837 o Security and stability fixes:
17838 - Don't double-free a parsable, but invalid, microdescriptor, even if
17839 it is followed in the blob we're parsing by an unparsable
17840 microdescriptor. Fixes an issue reported in a comment on bug 2954.
17841 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
17842 - If the Nickname configuration option isn't given, Tor would pick a
17843 nickname based on the local hostname as the nickname for a relay.
17844 Because nicknames are not very important in today's Tor and the
17845 "Unnamed" nickname has been implemented, this is now problematic
17846 behavior: It leaks information about the hostname without being
17847 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
17848 introduced the Unnamed nickname. Reported by tagnaq.
17849 - Fix an uncommon assertion failure when running with DNSPort under
17850 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
17851 - Avoid linkability based on cached hidden service descriptors: forget
17852 all hidden service descriptors cached as a client when processing a
17853 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
17856 - Export GeoIP information on bridge usage to controllers even if we
17857 have not yet been running for 24 hours. Now Vidalia bridge operators
17858 can get more accurate and immediate feedback about their
17859 contributions to the network.
17861 o Major features and bugfixes (node selection):
17862 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
17863 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
17864 options. Previously, we had been ambiguous in describing what
17865 counted as an "exit" node, and what operations exactly "StrictNodes
17866 0" would permit. This created confusion when people saw nodes built
17867 through unexpected circuits, and made it hard to tell real bugs from
17868 surprises. Now the intended behavior is:
17869 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
17870 a node that delivers user traffic outside the Tor network.
17871 . "Entry", in the context of EntryNodes, means a node used as the
17872 first hop of a multihop circuit. It doesn't include direct
17873 connections to directory servers.
17874 . "ExcludeNodes" applies to all nodes.
17875 . "StrictNodes" changes the behavior of ExcludeNodes only. When
17876 StrictNodes is set, Tor should avoid all nodes listed in
17877 ExcludeNodes, even when it will make user requests fail. When
17878 StrictNodes is *not* set, then Tor should follow ExcludeNodes
17879 whenever it can, except when it must use an excluded node to
17880 perform self-tests, connect to a hidden service, provide a
17881 hidden service, fulfill a .exit request, upload directory
17882 information, or fetch directory information.
17883 Collectively, the changes to implement the behavior fix bug 1090.
17884 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
17885 a node is listed in both, it's treated as excluded.
17886 - ExcludeNodes now applies to directory nodes -- as a preference if
17887 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
17888 Don't exclude all the directory authorities and set StrictNodes to 1
17889 unless you really want your Tor to break.
17890 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
17891 - ExcludeExitNodes now overrides .exit requests.
17892 - We don't use bridges listed in ExcludeNodes.
17893 - When StrictNodes is 1:
17894 . We now apply ExcludeNodes to hidden service introduction points
17895 and to rendezvous points selected by hidden service users. This
17896 can make your hidden service less reliable: use it with caution!
17897 . If we have used ExcludeNodes on ourself, do not try relay
17898 reachability self-tests.
17899 . If we have excluded all the directory authorities, we will not
17900 even try to upload our descriptor if we're a relay.
17901 . Do not honor .exit requests to an excluded node.
17902 - Remove a misfeature that caused us to ignore the Fast/Stable flags
17903 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
17904 - When the set of permitted nodes changes, we now remove any mappings
17905 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
17907 - We never cannibalize a circuit that had excluded nodes on it, even
17908 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
17909 - Revert a change where we would be laxer about attaching streams to
17910 circuits than when building the circuits. This was meant to prevent
17911 a set of bugs where streams were never attachable, but our improved
17912 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
17913 - Keep track of how many times we launch a new circuit to handle a
17914 given stream. Too many launches could indicate an inconsistency
17915 between our "launch a circuit to handle this stream" logic and our
17916 "attach this stream to one of the available circuits" logic.
17917 - Improve log messages related to excluded nodes.
17920 - Fix a spurious warning when moving from a short month to a long
17921 month on relays with month-based BandwidthAccounting. Bugfix on
17922 0.2.2.17-alpha; fixes bug 3020.
17923 - When a client finds that an origin circuit has run out of 16-bit
17924 stream IDs, we now mark it as unusable for new streams. Previously,
17925 we would try to close the entire circuit. Bugfix on 0.0.6.
17926 - Add a forgotten cast that caused a compile warning on OS X 10.6.
17927 Bugfix on 0.2.2.24-alpha.
17928 - Be more careful about reporting the correct error from a failed
17929 connect() system call. Under some circumstances, it was possible to
17930 look at an incorrect value for errno when sending the end reason.
17931 Bugfix on 0.1.0.1-rc.
17932 - Correctly handle an "impossible" overflow cases in connection byte
17933 counting, where we write or read more than 4GB on an edge connection
17934 in a single second. Bugfix on 0.1.2.8-beta.
17935 - Correct the warning displayed when a rendezvous descriptor exceeds
17936 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
17938 - Clients and hidden services now use HSDir-flagged relays for hidden
17939 service descriptor downloads and uploads even if the relays have no
17940 DirPort set and the client has disabled TunnelDirConns. This will
17941 eventually allow us to give the HSDir flag to relays with no
17942 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
17943 - Downgrade "no current certificates known for authority" message from
17944 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
17945 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
17946 2917. Bugfix on 0.1.1.1-alpha.
17947 - Only limit the lengths of single HS descriptors, even when multiple
17948 HS descriptors are published to an HSDir relay in a single POST
17949 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
17950 - Write the current time into the LastWritten line in our state file,
17951 rather than the time from the previous write attempt. Also, stop
17952 trying to use a time of -1 in our log statements. Fixes bug 3039;
17953 bugfix on 0.2.2.14-alpha.
17954 - Be more consistent in our treatment of file system paths. "~" should
17955 get expanded to the user's home directory in the Log config option.
17956 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
17957 feature for the -f and --DataDirectory options.
17960 - Make sure every relay writes a state file at least every 12 hours.
17961 Previously, a relay could go for weeks without writing its state
17962 file, and on a crash could lose its bandwidth history, capacity
17963 estimates, client country statistics, and so on. Addresses bug 3012.
17964 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
17965 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
17966 clients are already deprecated because of security bugs.
17967 - Don't allow v0 hidden service authorities to act as clients.
17968 Required by fix for bug 3000.
17969 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
17970 by fix for bug 3000.
17971 - Ensure that no empty [dirreq-](read|write)-history lines are added
17972 to an extrainfo document. Implements ticket 2497.
17974 o Code simplification and refactoring:
17975 - Remove workaround code to handle directory responses from servers
17976 that had bug 539 (they would send HTTP status 503 responses _and_
17977 send a body too). Since only server versions before
17978 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
17979 keep the workaround in place.
17980 - Remove the old 'fuzzy time' logic. It was supposed to be used for
17981 handling calculations where we have a known amount of clock skew and
17982 an allowed amount of unknown skew. But we only used it in three
17983 places, and we never adjusted the known/unknown skew values. This is
17984 still something we might want to do someday, but if we do, we'll
17985 want to do it differently.
17986 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
17987 None of the cases where we did this before were wrong, but by making
17988 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
17989 - Use GetTempDir to find the proper temporary directory location on
17990 Windows when generating temporary files for the unit tests. Patch by
17994 Changes in version 0.2.2.24-alpha - 2011-04-08
17995 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
17996 prevented Tor clients from effectively using "multihomed" bridges,
17997 that is, bridges that listen on multiple ports or IP addresses so users
17998 can continue to use some of their addresses even if others get blocked.
18001 - Fix a bug where bridge users who configure the non-canonical
18002 address of a bridge automatically switch to its canonical
18003 address. If a bridge listens at more than one address, it should be
18004 able to advertise those addresses independently and any non-blocked
18005 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
18007 - If you configured Tor to use bridge A, and then quit and
18008 configured Tor to use bridge B instead, it would happily continue
18009 to use bridge A if it's still reachable. While this behavior is
18010 a feature if your goal is connectivity, in some scenarios it's a
18011 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
18012 - Directory authorities now use data collected from their own
18013 uptime observations when choosing whether to assign the HSDir flag
18014 to relays, instead of trusting the uptime value the relay reports in
18015 its descriptor. This change helps prevent an attack where a small
18016 set of nodes with frequently-changing identity keys can blackhole
18017 a hidden service. (Only authorities need upgrade; others will be
18018 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
18021 - When we restart our relay, we might get a successful connection
18022 from the outside before we've started our reachability tests,
18023 triggering a warning: "ORPort found reachable, but I have no
18024 routerinfo yet. Failing to inform controller of success." This
18025 bug was harmless unless Tor is running under a controller
18026 like Vidalia, in which case the controller would never get a
18027 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
18029 - Make directory authorities more accurate at recording when
18030 relays that have failed several reachability tests became
18031 unreachable, so we can provide more accuracy at assigning Stable,
18032 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
18033 - Fix an issue that prevented static linking of libevent on
18034 some platforms (notably Linux). Fixes bug 2698; bugfix on
18035 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
18036 the --with-static-libevent configure option).
18037 - We now ask the other side of a stream (the client or the exit)
18038 for more data on that stream when the amount of queued data on
18039 that stream dips low enough. Previously, we wouldn't ask the
18040 other side for more data until either it sent us more data (which
18041 it wasn't supposed to do if it had exhausted its window!) or we
18042 had completely flushed all our queued data. This flow control fix
18043 should improve throughput. Fixes bug 2756; bugfix on the earliest
18044 released versions of Tor (svn commit r152).
18045 - Avoid a double-mark-for-free warning when failing to attach a
18046 transparent proxy connection. (We thought we had fixed this in
18047 0.2.2.23-alpha, but it turns out our fix was checking the wrong
18048 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
18049 bug) and 0.2.2.23-alpha (the incorrect fix).
18050 - When warning about missing zlib development packages during compile,
18051 give the correct package names. Bugfix on 0.2.0.1-alpha.
18054 - Directory authorities now log the source of a rejected POSTed v3
18055 networkstatus vote.
18056 - Make compilation with clang possible when using
18057 --enable-gcc-warnings by removing two warning options that clang
18058 hasn't implemented yet and by fixing a few warnings. Implements
18060 - When expiring circuits, use microsecond timers rather than
18061 one-second timers. This can avoid an unpleasant situation where a
18062 circuit is launched near the end of one second and expired right
18063 near the beginning of the next, and prevent fluctuations in circuit
18065 - Use computed circuit-build timeouts to decide when to launch
18066 parallel introduction circuits for hidden services. (Previously,
18067 we would retry after 15 seconds.)
18068 - Update to the April 1 2011 Maxmind GeoLite Country database.
18071 - Create the /var/run/tor directory on startup on OpenSUSE if it is
18072 not already created. Patch from Andreas Stieger. Fixes bug 2573.
18074 o Documentation changes:
18075 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
18076 - Resolve all doxygen warnings except those for missing documentation.
18078 - Add doxygen documentation for more functions, fields, and types.
18081 Changes in version 0.2.2.23-alpha - 2011-03-08
18082 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
18083 they restart they don't lose their bandwidth capacity estimate. This
18084 release also fixes a diverse set of user-facing bugs, ranging from
18085 relays overrunning their rate limiting to clients falsely warning about
18086 clock skew to bridge descriptor leaks by our bridge directory authority.
18089 - Stop sending a CLOCK_SKEW controller status event whenever
18090 we fetch directory information from a relay that has a wrong clock.
18091 Instead, only inform the controller when it's a trusted authority
18092 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
18093 the rest of bug 1074.
18094 - Fix an assert in parsing router descriptors containing IPv6
18095 addresses. This one took down the directory authorities when
18096 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
18097 - Make the bridge directory authority refuse to answer directory
18098 requests for "all" descriptors. It used to include bridge
18099 descriptors in its answer, which was a major information leak.
18100 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
18101 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
18102 Tor would ignore their RelayBandwidthBurst setting,
18103 potentially using more bandwidth than expected. Bugfix on
18104 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
18105 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
18106 hidserv" in her torrc. The 'hidserv' argument never controlled
18107 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
18110 - Relays now save observed peak bandwidth throughput rates to their
18111 state file (along with total usage, which was already saved)
18112 so that they can determine their correct estimated bandwidth on
18113 restart. Resolves bug 1863, where Tor relays would reset their
18114 estimated bandwidth to 0 after restarting.
18115 - Directory authorities now take changes in router IP address and
18116 ORPort into account when determining router stability. Previously,
18117 if a router changed its IP or ORPort, the authorities would not
18118 treat it as having any downtime for the purposes of stability
18119 calculation, whereas clients would experience downtime since the
18120 change could take a while to propagate to them. Resolves issue 1035.
18121 - Enable Address Space Layout Randomization (ASLR) and Data Execution
18122 Prevention (DEP) by default on Windows to make it harder for
18123 attackers to exploit vulnerabilities. Patch from John Brooks.
18125 o Minor bugfixes (on 0.2.1.x and earlier):
18126 - Fix a rare crash bug that could occur when a client was configured
18127 with a large number of bridges. Fixes bug 2629; bugfix on
18128 0.2.1.2-alpha. Bugfix by trac user "shitlei".
18129 - Avoid a double mark-for-free warning when failing to attach a
18130 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
18132 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
18133 found by "cypherpunks". This bug was introduced before the first
18134 Tor release, in svn commit r110.
18135 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
18136 don't mention them in the manpage. Fixes bug 2450; issue
18137 spotted by keb and G-Lo.
18138 - Fix a bug in bandwidth history state parsing that could have been
18139 triggered if a future version of Tor ever changed the timing
18140 granularity at which bandwidth history is measured. Bugfix on
18141 Tor 0.1.1.11-alpha.
18142 - When a relay decides that its DNS is too broken for it to serve
18143 as an exit server, it advertised itself as a non-exit, but
18144 continued to act as an exit. This could create accidental
18145 partitioning opportunities for users. Instead, if a relay is
18146 going to advertise reject *:* as its exit policy, it should
18147 really act with exit policy "reject *:*". Fixes bug 2366.
18148 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
18149 - In the special case where you configure a public exit relay as your
18150 bridge, Tor would be willing to use that exit relay as the last
18151 hop in your circuit as well. Now we fail that circuit instead.
18152 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
18153 - Fix a bug with our locking implementation on Windows that couldn't
18154 correctly detect when a file was already locked. Fixes bug 2504,
18155 bugfix on 0.2.1.6-alpha.
18156 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
18157 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
18159 - Set target port in get_interface_address6() correctly. Bugfix
18160 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
18161 - Directory authorities are now more robust to hops back in time
18162 when calculating router stability. Previously, if a run of uptime
18163 or downtime appeared to be negative, the calculation could give
18164 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
18166 - Fix an assert that got triggered when using the TestingTorNetwork
18167 configuration option and then issuing a GETINFO config-text control
18168 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
18170 o Minor bugfixes (on 0.2.2.x):
18171 - Clients should not weight BadExit nodes as Exits in their node
18172 selection. Similarly, directory authorities should not count BadExit
18173 bandwidth as Exit bandwidth when computing bandwidth-weights.
18174 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
18175 - Correctly clear our dir_read/dir_write history when there is an
18176 error parsing any bw history value from the state file. Bugfix on
18177 Tor 0.2.2.15-alpha.
18178 - Resolve a bug in verifying signatures of directory objects
18179 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
18180 Fixes bug 2409. Found by "piebeer".
18181 - Bridge authorities no longer crash on SIGHUP when they try to
18182 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
18186 - Log less aggressively about circuit timeout changes, and improve
18187 some other circuit timeout messages. Resolves bug 2004.
18188 - Log a little more clearly about the times at which we're no longer
18189 accepting new connections. Resolves bug 2181.
18190 - Reject attempts at the client side to open connections to private
18191 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
18192 a randomly chosen exit node. Attempts to do so are always
18193 ill-defined, generally prevented by exit policies, and usually
18194 in error. This will also help to detect loops in transparent
18195 proxy configurations. You can disable this feature by setting
18196 "ClientRejectInternalAddresses 0" in your torrc.
18197 - Always treat failure to allocate an RSA key as an unrecoverable
18199 - Update to the March 1 2011 Maxmind GeoLite Country database.
18201 o Minor features (log subsystem):
18202 - Add documentation for configuring logging at different severities in
18203 different log domains. We've had this feature since 0.2.1.1-alpha,
18204 but for some reason it never made it into the manpage. Fixes
18206 - Make it simpler to specify "All log domains except for A and B".
18207 Previously you needed to say "[*,~A,~B]". Now you can just say
18209 - Add a "LogMessageDomains 1" option to include the domains of log
18210 messages along with the messages. Without this, there's no way
18211 to use log domains without reading the source or doing a lot
18214 o Packaging changes:
18215 - Stop shipping the Tor specs files and development proposal documents
18216 in the tarball. They are now in a separate git repository at
18217 git://git.torproject.org/torspec.git
18220 Changes in version 0.2.1.30 - 2011-02-23
18221 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
18222 change is a slight tweak to Tor's TLS handshake that makes relays
18223 and bridges that run this new version reachable from Iran again.
18224 We don't expect this tweak will win the arms race long-term, but it
18225 buys us time until we roll out a better solution.
18228 - Stop sending a CLOCK_SKEW controller status event whenever
18229 we fetch directory information from a relay that has a wrong clock.
18230 Instead, only inform the controller when it's a trusted authority
18231 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
18232 the rest of bug 1074.
18233 - Fix a bounds-checking error that could allow an attacker to
18234 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
18235 Found by "piebeer".
18236 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
18237 Tor would ignore their RelayBandwidthBurst setting,
18238 potentially using more bandwidth than expected. Bugfix on
18239 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
18240 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
18241 hidserv" in her torrc. The 'hidserv' argument never controlled
18242 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
18245 - Adjust our TLS Diffie-Hellman parameters to match those used by
18247 - Update to the February 1 2011 Maxmind GeoLite Country database.
18250 - Check for and reject overly long directory certificates and
18251 directory tokens before they have a chance to hit any assertions.
18252 Bugfix on 0.2.1.28. Found by "doorss".
18253 - Bring the logic that gathers routerinfos and assesses the
18254 acceptability of circuits into line. This prevents a Tor OP from
18255 getting locked in a cycle of choosing its local OR as an exit for a
18256 path (due to a .exit request) and then rejecting the circuit because
18257 its OR is not listed yet. It also prevents Tor clients from using an
18258 OR running in the same instance as an exit (due to a .exit request)
18259 if the OR does not meet the same requirements expected of an OR
18260 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
18262 o Packaging changes:
18263 - Stop shipping the Tor specs files and development proposal documents
18264 in the tarball. They are now in a separate git repository at
18265 git://git.torproject.org/torspec.git
18266 - Do not include Git version tags as though they are SVN tags when
18267 generating a tarball from inside a repository that has switched
18268 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
18271 Changes in version 0.2.2.22-alpha - 2011-01-25
18272 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
18273 main other change is a slight tweak to Tor's TLS handshake that makes
18274 relays and bridges that run this new version reachable from Iran again.
18275 We don't expect this tweak will win the arms race long-term, but it
18276 will buy us a bit more time until we roll out a better solution.
18279 - Fix a bounds-checking error that could allow an attacker to
18280 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
18281 Found by "piebeer".
18282 - Don't assert when changing from bridge to relay or vice versa
18283 via the controller. The assert happened because we didn't properly
18284 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
18285 bug 2433. Reported by bastik.
18288 - Adjust our TLS Diffie-Hellman parameters to match those used by
18290 - Provide a log message stating which geoip file we're parsing
18291 instead of just stating that we're parsing the geoip file.
18292 Implements ticket 2432.
18295 - Check for and reject overly long directory certificates and
18296 directory tokens before they have a chance to hit any assertions.
18297 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
18300 Changes in version 0.2.2.21-alpha - 2011-01-15
18301 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
18302 continues our recent code security audit work. The main fix resolves
18303 a remote heap overflow vulnerability that can allow remote code
18304 execution (CVE-2011-0427). Other fixes address a variety of assert
18305 and crash bugs, most of which we think are hard to exploit remotely.
18307 o Major bugfixes (security), also included in 0.2.1.29:
18308 - Fix a heap overflow bug where an adversary could cause heap
18309 corruption. This bug probably allows remote code execution
18310 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
18312 - Prevent a denial-of-service attack by disallowing any
18313 zlib-compressed data whose compression factor is implausibly
18314 high. Fixes part of bug 2324; reported by "doorss".
18315 - Zero out a few more keys in memory before freeing them. Fixes
18316 bug 2384 and part of bug 2385. These key instances found by
18317 "cypherpunks", based on Andrew Case's report about being able
18318 to find sensitive data in Tor's memory space if you have enough
18319 permissions. Bugfix on 0.0.2pre9.
18321 o Major bugfixes (crashes), also included in 0.2.1.29:
18322 - Prevent calls to Libevent from inside Libevent log handlers.
18323 This had potential to cause a nasty set of crashes, especially
18324 if running Libevent with debug logging enabled, and running
18325 Tor with a controller watching for low-severity log messages.
18326 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
18327 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
18328 underflow errors there too. Fixes the other part of bug 2324.
18329 - Fix a bug where we would assert if we ever had a
18330 cached-descriptors.new file (or another file read directly into
18331 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
18332 on 0.2.1.25. Found by doorss.
18333 - Fix some potential asserts and parsing issues with grossly
18334 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
18337 o Minor bugfixes (other), also included in 0.2.1.29:
18338 - Fix a bug with handling misformed replies to reverse DNS lookup
18339 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
18340 bug reported by doorss.
18341 - Fix compilation on mingw when a pthreads compatibility library
18342 has been installed. (We don't want to use it, so we shouldn't
18343 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
18344 - Fix a bug where we would declare that we had run out of virtual
18345 addresses when the address space was only half-exhausted. Bugfix
18347 - Correctly handle the case where AutomapHostsOnResolve is set but
18348 no virtual addresses are available. Fixes bug 2328; bugfix on
18349 0.1.2.1-alpha. Bug found by doorss.
18350 - Correctly handle wrapping around when we run out of virtual
18351 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
18353 o Minor features, also included in 0.2.1.29:
18354 - Update to the January 1 2011 Maxmind GeoLite Country database.
18355 - Introduce output size checks on all of our decryption functions.
18357 o Build changes, also included in 0.2.1.29:
18358 - Tor does not build packages correctly with Automake 1.6 and earlier;
18359 added a check to Makefile.am to make sure that we're building with
18360 Automake 1.7 or later.
18361 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
18362 because we built it with a too-old version of automake. Thus that
18363 release broke ./configure --enable-openbsd-malloc, which is popular
18364 among really fast exit relays on Linux.
18366 o Major bugfixes, new in 0.2.2.21-alpha:
18367 - Prevent crash/heap corruption when the cbtnummodes consensus
18368 parameter is set to 0 or large values. Fixes bug 2317; bugfix
18371 o Major features, new in 0.2.2.21-alpha:
18372 - Introduce minimum/maximum values that clients will believe
18373 from the consensus. Now we'll have a better chance to avoid crashes
18374 or worse when a consensus param has a weird value.
18376 o Minor features, new in 0.2.2.21-alpha:
18377 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
18378 used on bridges, and it makes bridge scanning somewhat easier.
18379 - If writing the state file to disk fails, wait up to an hour before
18380 retrying again, rather than trying again each second. Fixes bug
18381 2346; bugfix on Tor 0.1.1.3-alpha.
18382 - Make Libevent log messages get delivered to controllers later,
18383 and not from inside the Libevent log handler. This prevents unsafe
18384 reentrant Libevent calls while still letting the log messages
18386 - Detect platforms that brokenly use a signed size_t, and refuse to
18387 build there. Found and analyzed by doorss and rransom.
18388 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
18391 o Minor bugfixes, new in 0.2.2.21-alpha:
18392 - Handle SOCKS messages longer than 128 bytes long correctly, rather
18393 than waiting forever for them to finish. Fixes bug 2330; bugfix
18394 on 0.2.0.16-alpha. Found by doorss.
18395 - Add assertions to check for overflow in arguments to
18396 base32_encode() and base32_decode(); fix a signed-unsigned
18397 comparison there too. These bugs are not actually reachable in Tor,
18398 but it's good to prevent future errors too. Found by doorss.
18399 - Correctly detect failures to create DNS requests when using Libevent
18400 versions before v2. (Before Libevent 2, we used our own evdns
18401 implementation. Its return values for Libevent's evdns_resolve_*()
18402 functions are not consistent with those from Libevent.) Fixes bug
18403 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
18405 o Documentation, new in 0.2.2.21-alpha:
18406 - Document the default socks host and port (127.0.0.1:9050) for
18410 Changes in version 0.2.1.29 - 2011-01-15
18411 Tor 0.2.1.29 continues our recent code security audit work. The main
18412 fix resolves a remote heap overflow vulnerability that can allow remote
18413 code execution. Other fixes address a variety of assert and crash bugs,
18414 most of which we think are hard to exploit remotely.
18416 o Major bugfixes (security):
18417 - Fix a heap overflow bug where an adversary could cause heap
18418 corruption. This bug probably allows remote code execution
18419 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
18421 - Prevent a denial-of-service attack by disallowing any
18422 zlib-compressed data whose compression factor is implausibly
18423 high. Fixes part of bug 2324; reported by "doorss".
18424 - Zero out a few more keys in memory before freeing them. Fixes
18425 bug 2384 and part of bug 2385. These key instances found by
18426 "cypherpunks", based on Andrew Case's report about being able
18427 to find sensitive data in Tor's memory space if you have enough
18428 permissions. Bugfix on 0.0.2pre9.
18430 o Major bugfixes (crashes):
18431 - Prevent calls to Libevent from inside Libevent log handlers.
18432 This had potential to cause a nasty set of crashes, especially
18433 if running Libevent with debug logging enabled, and running
18434 Tor with a controller watching for low-severity log messages.
18435 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
18436 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
18437 underflow errors there too. Fixes the other part of bug 2324.
18438 - Fix a bug where we would assert if we ever had a
18439 cached-descriptors.new file (or another file read directly into
18440 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
18441 on 0.2.1.25. Found by doorss.
18442 - Fix some potential asserts and parsing issues with grossly
18443 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
18446 o Minor bugfixes (other):
18447 - Fix a bug with handling misformed replies to reverse DNS lookup
18448 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
18449 bug reported by doorss.
18450 - Fix compilation on mingw when a pthreads compatibility library
18451 has been installed. (We don't want to use it, so we shouldn't
18452 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
18453 - Fix a bug where we would declare that we had run out of virtual
18454 addresses when the address space was only half-exhausted. Bugfix
18456 - Correctly handle the case where AutomapHostsOnResolve is set but
18457 no virtual addresses are available. Fixes bug 2328; bugfix on
18458 0.1.2.1-alpha. Bug found by doorss.
18459 - Correctly handle wrapping around to when we run out of virtual
18460 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
18461 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
18462 because we built it with a too-old version of automake. Thus that
18463 release broke ./configure --enable-openbsd-malloc, which is popular
18464 among really fast exit relays on Linux.
18467 - Update to the January 1 2011 Maxmind GeoLite Country database.
18468 - Introduce output size checks on all of our decryption functions.
18471 - Tor does not build packages correctly with Automake 1.6 and earlier;
18472 added a check to Makefile.am to make sure that we're building with
18473 Automake 1.7 or later.
18476 Changes in version 0.2.2.20-alpha - 2010-12-17
18477 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
18478 exploitable bugs. We also fix a variety of other significant bugs,
18479 change the IP address for one of our directory authorities, and update
18480 the minimum version that Tor relays must run to join the network.
18483 - Fix a remotely exploitable bug that could be used to crash instances
18484 of Tor remotely by overflowing on the heap. Remote-code execution
18485 hasn't been confirmed, but can't be ruled out. Everyone should
18486 upgrade. Bugfix on the 0.1.1 series and later.
18487 - Fix a bug that could break accounting on 64-bit systems with large
18488 time_t values, making them hibernate for impossibly long intervals.
18489 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
18490 - Fix a logic error in directory_fetches_from_authorities() that
18491 would cause all _non_-exits refusing single-hop-like circuits
18492 to fetch from authorities, when we wanted to have _exits_ fetch
18493 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
18495 - Fix a stream fairness bug that would cause newer streams on a given
18496 circuit to get preference when reading bytes from the origin or
18497 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
18498 introduced before the first Tor release, in svn revision r152.
18500 o Directory authority changes:
18501 - Change IP address and ports for gabelmoo (v3 directory authority).
18504 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
18505 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
18506 - Fix an off-by-one error in calculating some controller command
18507 argument lengths. Fortunately, this mistake is harmless since
18508 the controller code does redundant NUL termination too. Found by
18509 boboper. Bugfix on 0.1.1.1-alpha.
18510 - Do not dereference NULL if a bridge fails to build its
18511 extra-info descriptor. Found by an anonymous commenter on
18512 Trac. Bugfix on 0.2.2.19-alpha.
18515 - Update to the December 1 2010 Maxmind GeoLite Country database.
18516 - Directory authorities now reject relays running any versions of
18517 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
18518 known bugs that keep RELAY_EARLY cells from working on rendezvous
18519 circuits. Followup to fix for bug 2081.
18520 - Directory authorities now reject relays running any version of Tor
18521 older than 0.2.0.26-rc. That version is the earliest that fetches
18522 current directory information correctly. Fixes bug 2156.
18523 - Report only the top 10 ports in exit-port stats in order not to
18524 exceed the maximum extra-info descriptor length of 50 KB. Implements
18528 Changes in version 0.2.1.28 - 2010-12-17
18529 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
18530 exploitable bugs. We also took this opportunity to change the IP address
18531 for one of our directory authorities, and to update the geoip database
18535 - Fix a remotely exploitable bug that could be used to crash instances
18536 of Tor remotely by overflowing on the heap. Remote-code execution
18537 hasn't been confirmed, but can't be ruled out. Everyone should
18538 upgrade. Bugfix on the 0.1.1 series and later.
18540 o Directory authority changes:
18541 - Change IP address and ports for gabelmoo (v3 directory authority).
18544 - Update to the December 1 2010 Maxmind GeoLite Country database.
18547 Changes in version 0.2.1.27 - 2010-11-23
18548 Yet another OpenSSL security patch broke its compatibility with Tor:
18549 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
18550 also took this opportunity to fix several crash bugs, integrate a new
18551 directory authority, and update the bundled GeoIP database.
18554 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
18555 No longer set the tlsext_host_name extension on server SSL objects;
18556 but continue to set it on client SSL objects. Our goal in setting
18557 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
18558 bugfix on 0.2.1.1-alpha.
18559 - Do not log messages to the controller while shrinking buffer
18560 freelists. Doing so would sometimes make the controller connection
18561 try to allocate a buffer chunk, which would mess up the internals
18562 of the freelist and cause an assertion failure. Fixes bug 1125;
18563 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
18564 - Learn our external IP address when we're a relay or bridge, even if
18565 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
18566 where we introduced bridge relays that don't need to publish to
18567 be useful. Fixes bug 2050.
18568 - Do even more to reject (and not just ignore) annotations on
18569 router descriptors received anywhere but from the cache. Previously
18570 we would ignore such annotations at first, but cache them to disk
18571 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
18572 - When you're using bridges and your network goes away and your
18573 bridges get marked as down, recover when you attempt a new socks
18574 connection (if the network is back), rather than waiting up to an
18575 hour to try fetching new descriptors for your bridges. Bugfix on
18576 0.2.0.3-alpha; fixes bug 1981.
18579 - Move to the November 2010 Maxmind GeoLite country db (rather
18580 than the June 2009 ip-to-country GeoIP db) for our statistics that
18581 count how many users relays are seeing from each country. Now we'll
18582 have more accurate data, especially for many African countries.
18584 o New directory authorities:
18585 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
18589 - Fix an assertion failure that could occur in directory caches or
18590 bridge users when using a very short voting interval on a testing
18591 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
18593 - Enforce multiplicity rules when parsing annotations. Bugfix on
18594 0.2.0.8-alpha. Found by piebeer.
18595 - Allow handshaking OR connections to take a full KeepalivePeriod
18596 seconds to handshake. Previously, we would close them after
18597 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
18598 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
18600 - When building with --enable-gcc-warnings on OpenBSD, disable
18601 warnings in system headers. This makes --enable-gcc-warnings
18602 pass on OpenBSD 4.8.
18605 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
18606 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
18607 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
18608 Servers can start sending this code when enough clients recognize
18609 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
18610 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
18611 Patch from mingw-san.
18614 - Remove the old debian/ directory from the main Tor distribution.
18615 The official Tor-for-debian git repository lives at the URL
18616 https://git.torproject.org/debian/tor.git
18617 - Stop shipping the old doc/website/ directory in the tarball. We
18618 changed the website format in late 2010, and what we shipped in
18619 0.2.1.26 really wasn't that useful anyway.
18622 Changes in version 0.2.2.19-alpha - 2010-11-22
18623 Yet another OpenSSL security patch broke its compatibility with Tor:
18624 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
18627 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
18628 No longer set the tlsext_host_name extension on server SSL objects;
18629 but continue to set it on client SSL objects. Our goal in setting
18630 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
18631 bugfix on 0.2.1.1-alpha.
18634 - Try harder not to exceed the maximum length of 50 KB when writing
18635 statistics to extra-info descriptors. This bug was triggered by very
18636 fast relays reporting exit-port, entry, and dirreq statistics.
18637 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
18638 - Publish a router descriptor even if generating an extra-info
18639 descriptor fails. Previously we would not publish a router
18640 descriptor without an extra-info descriptor; this can cause fast
18641 exit relays collecting exit-port statistics to drop from the
18642 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
18645 Changes in version 0.2.2.18-alpha - 2010-11-16
18646 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
18647 us lately, makes unpublished bridge relays able to detect their IP
18648 address, and fixes a wide variety of other bugs to get us much closer
18649 to a stable release.
18652 - Do even more to reject (and not just ignore) annotations on
18653 router descriptors received anywhere but from the cache. Previously
18654 we would ignore such annotations at first, but cache them to disk
18655 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
18656 - Do not log messages to the controller while shrinking buffer
18657 freelists. Doing so would sometimes make the controller connection
18658 try to allocate a buffer chunk, which would mess up the internals
18659 of the freelist and cause an assertion failure. Fixes bug 1125;
18660 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
18661 - Learn our external IP address when we're a relay or bridge, even if
18662 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
18663 where we introduced bridge relays that don't need to publish to
18664 be useful. Fixes bug 2050.
18665 - Maintain separate TLS contexts and certificates for incoming and
18666 outgoing connections in bridge relays. Previously we would use the
18667 same TLS contexts and certs for incoming and outgoing connections.
18668 Bugfix on 0.2.0.3-alpha; addresses bug 988.
18669 - Maintain separate identity keys for incoming and outgoing TLS
18670 contexts in bridge relays. Previously we would use the same
18671 identity keys for incoming and outgoing TLS contexts. Bugfix on
18672 0.2.0.3-alpha; addresses the other half of bug 988.
18673 - Avoid an assertion failure when we as an authority receive a
18674 duplicate upload of a router descriptor that we already have,
18675 but which we previously considered an obsolete descriptor.
18676 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
18677 - Avoid a crash bug triggered by looking at a dangling pointer while
18678 setting the network status consensus. Found by Robert Ransom.
18679 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
18680 - Fix a logic error where servers that _didn't_ act as exits would
18681 try to keep their server lists more aggressively up to date than
18682 exits, when it was supposed to be the other way around. Bugfix
18685 o Minor bugfixes (on Tor 0.2.1.x and earlier):
18686 - When we're trying to guess whether we know our IP address as
18687 a relay, we would log various ways that we failed to guess
18688 our address, but never log that we ended up guessing it
18689 successfully. Now add a log line to help confused and anxious
18690 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
18691 - Bring the logic that gathers routerinfos and assesses the
18692 acceptability of circuits into line. This prevents a Tor OP from
18693 getting locked in a cycle of choosing its local OR as an exit for a
18694 path (due to a .exit request) and then rejecting the circuit because
18695 its OR is not listed yet. It also prevents Tor clients from using an
18696 OR running in the same instance as an exit (due to a .exit request)
18697 if the OR does not meet the same requirements expected of an OR
18698 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
18699 - Correctly describe errors that occur when generating a TLS object.
18700 Previously we would attribute them to a failure while generating a
18701 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
18703 - Enforce multiplicity rules when parsing annotations. Bugfix on
18704 0.2.0.8-alpha. Found by piebeer.
18705 - Fix warnings that newer versions of autoconf produced during
18706 ./autogen.sh. These warnings appear to be harmless in our case,
18707 but they were extremely verbose. Fixes bug 2020.
18709 o Minor bugfixes (on Tor 0.2.2.x):
18710 - Enable protection of small arrays whenever we build with gcc
18711 hardening features, not only when also building with warnings
18712 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
18715 - Make hidden services work better in private Tor networks by not
18716 requiring any uptime to join the hidden service descriptor
18717 DHT. Implements ticket 2088.
18718 - Rate-limit the "your application is giving Tor only an IP address"
18719 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
18720 - When AllowSingleHopExits is set, print a warning to explain to the
18721 relay operator why most clients are avoiding her relay.
18722 - Update to the November 1 2010 Maxmind GeoLite Country database.
18724 o Code simplifications and refactoring:
18725 - When we fixed bug 1038 we had to put in a restriction not to send
18726 RELAY_EARLY cells on rend circuits. This was necessary as long
18727 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
18728 active. Now remove this obsolete check. Resolves bug 2081.
18729 - Some options used different conventions for uppercasing of acronyms
18730 when comparing manpage and source. Fix those in favor of the
18731 manpage, as it makes sense to capitalize acronyms.
18732 - Remove the torrc.complete file. It hasn't been kept up to date
18733 and users will have better luck checking out the manpage.
18734 - Remove the obsolete "NoPublish" option; it has been flagged
18735 as obsolete and has produced a warning since 0.1.1.18-rc.
18736 - Remove everything related to building the expert bundle for OS X.
18737 It has confused many users, doesn't work right on OS X 10.6,
18738 and is hard to get rid of once installed. Resolves bug 1274.
18741 Changes in version 0.2.2.17-alpha - 2010-09-30
18742 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
18743 to use one-hop circuits (which can put the exit relays at higher risk,
18744 plus unbalance the network); fixes a big bug in bandwidth accounting
18745 for relays that want to limit their monthly bandwidth use; fixes a
18746 big pile of bugs in how clients tolerate temporary network failure;
18747 and makes our adaptive circuit build timeout feature (which improves
18748 client performance if your network is fast while not breaking things
18749 if your network is slow) better handle bad networks.
18752 - Exit relays now try harder to block exit attempts from unknown
18753 relays, to make it harder for people to use them as one-hop proxies
18754 a la tortunnel. Controlled by the refuseunknownexits consensus
18755 parameter (currently enabled), or you can override it on your
18756 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
18758 o Major bugfixes (0.2.1.x and earlier):
18759 - Fix a bug in bandwidth accounting that could make us use twice
18760 the intended bandwidth when our interval start changes due to
18761 daylight saving time. Now we tolerate skew in stored vs computed
18762 interval starts: if the start of the period changes by no more than
18763 50% of the period's duration, we remember bytes that we transferred
18764 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
18765 - Always search the Windows system directory for system DLLs, and
18766 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
18767 - When you're using bridges and your network goes away and your
18768 bridges get marked as down, recover when you attempt a new socks
18769 connection (if the network is back), rather than waiting up to an
18770 hour to try fetching new descriptors for your bridges. Bugfix on
18771 0.2.0.3-alpha; fixes bug 1981.
18773 o Major bugfixes (on 0.2.2.x):
18774 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
18776 - Fix a segfault that could happen when operating a bridge relay with
18777 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
18778 - The consensus bandwidth-weights (used by clients to choose fast
18779 relays) entered an unexpected edge case in September where
18780 Exits were much scarcer than Guards, resulting in bad weight
18781 recommendations. Now we compute them using new constraints that
18782 should succeed in all cases. Also alter directory authorities to
18783 not include the bandwidth-weights line if they fail to produce
18784 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
18785 - When weighting bridges during path selection, we used to trust
18786 the bandwidths they provided in their descriptor, only capping them
18787 at 10MB/s. This turned out to be problematic for two reasons:
18788 Bridges could claim to handle a lot more traffic then they
18789 actually would, thus making more clients pick them and have a
18790 pretty effective DoS attack. The other issue is that new bridges
18791 that might not have a good estimate for their bw capacity yet
18792 would not get used at all unless no other bridges are available
18793 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
18795 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
18796 - Ignore cannibalized circuits when recording circuit build times.
18797 This should provide for a minor performance improvement for hidden
18798 service users using 0.2.2.14-alpha, and should remove two spurious
18799 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
18800 - Simplify the logic that causes us to decide if the network is
18801 unavailable for purposes of recording circuit build times. If we
18802 receive no cells whatsoever for the entire duration of a circuit's
18803 full measured lifetime, the network is probably down. Also ignore
18804 one-hop directory fetching circuit timeouts when calculating our
18805 circuit build times. These changes should hopefully reduce the
18806 cases where we see ridiculous circuit build timeouts for people
18807 with spotty wireless connections. Fixes part of bug 1772; bugfix
18809 - Prevent the circuit build timeout from becoming larger than
18810 the maximum build time we have ever seen. Also, prevent the time
18811 period for measurement circuits from becoming larger than twice that
18812 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
18815 - When we run out of directory information such that we can't build
18816 circuits, but then get enough that we can build circuits, log when
18817 we actually construct a circuit, so the user has a better chance of
18818 knowing what's going on. Fixes bug 1362.
18819 - Be more generous with how much bandwidth we'd use up (with
18820 accounting enabled) before entering "soft hibernation". Previously,
18821 we'd refuse new connections and circuits once we'd used up 95% of
18822 our allotment. Now, we use up 95% of our allotment, AND make sure
18823 that we have no more than 500MB (or 3 hours of expected traffic,
18824 whichever is lower) remaining before we enter soft hibernation.
18825 - If we've configured EntryNodes and our network goes away and/or all
18826 our entrynodes get marked down, optimistically retry them all when
18827 a new socks application request appears. Fixes bug 1882.
18828 - Add some more defensive programming for architectures that can't
18829 handle unaligned integer accesses. We don't know of any actual bugs
18830 right now, but that's the best time to fix them. Fixes bug 1943.
18831 - Support line continuations in the torrc config file. If a line
18832 ends with a single backslash character, the newline is ignored, and
18833 the configuration value is treated as continuing on the next line.
18836 o Minor bugfixes (on 0.2.1.x and earlier):
18837 - For bandwidth accounting, calculate our expected bandwidth rate
18838 based on the time during which we were active and not in
18839 soft-hibernation during the last interval. Previously, we were
18840 also considering the time spent in soft-hibernation. If this
18841 was a long time, we would wind up underestimating our bandwidth
18842 by a lot, and skewing our wakeup time towards the start of the
18843 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
18845 o Minor bugfixes (on 0.2.2.x):
18846 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
18847 which were disabled by the circuit build timeout changes in
18848 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
18849 - Make sure we don't warn about missing bandwidth weights when
18850 choosing bridges or other relays not in the consensus. Bugfix on
18851 0.2.2.10-alpha; fixes bug 1805.
18852 - In our logs, do not double-report signatures from unrecognized
18853 authorities both as "from unknown authority" and "not
18854 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
18857 Changes in version 0.2.2.16-alpha - 2010-09-17
18858 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
18859 evident at exit relays), and also continues to resolve all the little
18860 bugs that have been filling up trac lately.
18862 o Major bugfixes (stream-level fairness):
18863 - When receiving a circuit-level SENDME for a blocked circuit, try
18864 to package cells fairly from all the streams that had previously
18865 been blocked on that circuit. Previously, we had started with the
18866 oldest stream, and allowed each stream to potentially exhaust
18867 the circuit's package window. This gave older streams on any
18868 given circuit priority over newer ones. Fixes bug 1937. Detected
18869 originally by Camilo Viecco. This bug was introduced before the
18870 first Tor release, in svn commit r152: it is the new winner of
18871 the longest-lived bug prize.
18872 - When the exit relay got a circuit-level sendme cell, it started
18873 reading on the exit streams, even if had 500 cells queued in the
18874 circuit queue already, so the circuit queue just grew and grew in
18875 some cases. We fix this by not re-enabling reading on receipt of a
18876 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
18877 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
18879 - Newly created streams were allowed to read cells onto circuits,
18880 even if the circuit's cell queue was blocked and waiting to drain.
18881 This created potential unfairness, as older streams would be
18882 blocked, but newer streams would gladly fill the queue completely.
18883 We add code to detect this situation and prevent any stream from
18884 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
18888 - Update to the September 1 2010 Maxmind GeoLite Country database.
18889 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
18890 not. This would lead to a cookie that is still not group readable.
18891 Closes bug 1843. Suggested by katmagic.
18892 - When logging a rate-limited warning, we now mention how many messages
18893 got suppressed since the last warning.
18894 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
18895 do individual connection-level rate limiting of clients. The torrc
18896 config options with the same names trump the consensus params, if
18897 both are present. Replaces the old "bwconnrate" and "bwconnburst"
18898 consensus params which were broken from 0.2.2.7-alpha through
18899 0.2.2.14-alpha. Closes bug 1947.
18900 - When a router changes IP address or port, authorities now launch
18901 a new reachability test for it. Implements ticket 1899.
18902 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
18903 2 no signature, 4 required" messages about consensus signatures
18904 easier to read, and make sure they get logged at the same severity
18905 as the messages explaining which keys are which. Fixes bug 1290.
18906 - Don't warn when we have a consensus that we can't verify because
18907 of missing certificates, unless those certificates are ones
18908 that we have been trying and failing to download. Fixes bug 1145.
18909 - If you configure your bridge with a known identity fingerprint,
18910 and the bridge authority is unreachable (as it is in at least
18911 one country now), fall back to directly requesting the descriptor
18912 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
18914 - When building with --enable-gcc-warnings on OpenBSD, disable
18915 warnings in system headers. This makes --enable-gcc-warnings
18916 pass on OpenBSD 4.8.
18918 o Minor bugfixes (on 0.2.1.x and earlier):
18919 - Authorities will now attempt to download consensuses if their
18920 own efforts to make a live consensus have failed. This change
18921 means authorities that restart will fetch a valid consensus, and
18922 it means authorities that didn't agree with the current consensus
18923 will still fetch and serve it if it has enough signatures. Bugfix
18924 on 0.2.0.9-alpha; fixes bug 1300.
18925 - Ensure DNS requests launched by "RESOLVE" commands from the
18926 controller respect the __LeaveStreamsUnattached setconf options. The
18927 same goes for requests launched via DNSPort or transparent
18928 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
18929 - Allow handshaking OR connections to take a full KeepalivePeriod
18930 seconds to handshake. Previously, we would close them after
18931 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
18932 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
18934 - Rate-limit "Failed to hand off onionskin" warnings.
18935 - Never relay a cell for a circuit we have already destroyed.
18936 Between marking a circuit as closeable and finally closing it,
18937 it may have been possible for a few queued cells to get relayed,
18938 even though they would have been immediately dropped by the next
18939 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
18940 - Never queue a cell for a circuit that's already been marked
18942 - Never vote for a server as "Running" if we have a descriptor for
18943 it claiming to be hibernating, and that descriptor was published
18944 more recently than our last contact with the server. Bugfix on
18945 0.2.0.3-alpha; fixes bug 911.
18946 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
18949 o Minor bugfixes (on 0.2.2.x):
18950 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
18951 down if a directory fetch fails and you've configured either
18952 bridges or EntryNodes. The intent was to mark the relay as down
18953 _unless_ you're using bridges or EntryNodes, since if you are
18954 then you could quickly run out of entry points.
18955 - Fix the Windows directory-listing code. A bug introduced in
18956 0.2.2.14-alpha could make Windows directory servers forget to load
18957 some of their cached v2 networkstatus files.
18958 - Really allow clients to use relays as bridges. Fixes bug 1776;
18959 bugfix on 0.2.2.15-alpha.
18960 - Demote a warn to info that happens when the CellStatistics option
18961 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
18962 Reported by Moritz Bartl.
18963 - On Windows, build correctly either with or without Unicode support.
18964 This is necessary so that Tor can support fringe platforms like
18965 Windows 98 (which has no Unicode), or Windows CE (which has no
18966 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
18969 - Add a unit test for cross-platform directory-listing code.
18972 Changes in version 0.2.2.15-alpha - 2010-08-18
18973 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
18974 fixes a variety of other bugs that were preventing performance
18975 experiments from moving forward, fixes several bothersome memory leaks,
18976 and generally closes a lot of smaller bugs that have been filling up
18980 - Stop assigning the HSDir flag to relays that disable their
18981 DirPort (and thus will refuse to answer directory requests). This
18982 fix should dramatically improve the reachability of hidden services:
18983 hidden services and hidden service clients pick six HSDir relays
18984 to store and retrieve the hidden service descriptor, and currently
18985 about half of the HSDir relays will refuse to work. Bugfix on
18986 0.2.0.10-alpha; fixes part of bug 1693.
18987 - The PerConnBWRate and Burst config options, along with the
18988 bwconnrate and bwconnburst consensus params, initialized each conn's
18989 token bucket values only when the connection is established. Now we
18990 update them if the config options change, and update them every time
18991 we get a new consensus. Otherwise we can encounter an ugly edge
18992 case where we initialize an OR conn to client-level bandwidth,
18993 but then later the relay joins the consensus and we leave it
18994 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
18995 - Fix a regression that caused Tor to rebind its ports if it receives
18996 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
18999 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
19000 should give us approximately 40-50% more Guard-flagged nodes,
19001 improving the anonymity the Tor network can provide and also
19002 decreasing the dropoff in throughput that relays experience when
19003 they first get the Guard flag.
19004 - Allow enabling or disabling the *Statistics config options while
19008 - Update to the August 1 2010 Maxmind GeoLite Country database.
19009 - Have the controller interface give a more useful message than
19010 "Internal Error" in response to failed GETINFO requests.
19011 - Warn when the same option is provided more than once in a torrc
19012 file, on the command line, or in a single SETCONF statement, and
19013 the option is one that only accepts a single line. Closes bug 1384.
19014 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
19015 Patch from mingw-san.
19016 - Add support for the country code "{??}" in torrc options like
19017 ExcludeNodes, to indicate all routers of unknown country. Closes
19019 - Relays report the number of bytes spent on answering directory
19020 requests in extra-info descriptors similar to {read,write}-history.
19021 Implements enhancement 1790.
19023 o Minor bugfixes (on 0.2.1.x and earlier):
19024 - Complain if PublishServerDescriptor is given multiple arguments that
19025 include 0 or 1. This configuration will be rejected in the future.
19026 Bugfix on 0.2.0.1-alpha; closes bug 1107.
19027 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
19028 Bugfix on 0.2.0.13-alpha; closes bug 928.
19029 - Change "Application request when we're believed to be offline."
19030 notice to "Application request when we haven't used client
19031 functionality lately.", to clarify that it's not an error. Bugfix
19032 on 0.0.9.3; fixes bug 1222.
19033 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
19034 would return "551 Internal error" rather than "552 Unrecognized key
19035 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
19036 - Users can't configure a regular relay to be their bridge. It didn't
19037 work because when Tor fetched the bridge descriptor, it found
19038 that it already had it, and didn't realize that the purpose of the
19039 descriptor had changed. Now we replace routers with a purpose other
19040 than bridge with bridge descriptors when fetching them. Bugfix on
19041 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
19042 refetch the descriptor with router purpose 'general', disabling
19044 - Fix a rare bug in rend_fn unit tests: we would fail a test when
19045 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
19046 on 0.2.0.10-alpha; fixes bug 1808.
19047 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
19048 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
19049 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
19050 Servers can start sending this code when enough clients recognize
19051 it. Also update the spec to reflect this new reason. Bugfix on
19052 0.1.0.1-rc; fixes part of bug 1793.
19053 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
19054 when we switch from being a public relay to a bridge. Otherwise
19055 there will still be clients that see the relay in their consensus,
19056 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
19058 - Instead of giving an assertion failure on an internal mismatch
19059 on estimated freelist size, just log a BUG warning and try later.
19060 Mitigates but does not fix bug 1125.
19061 - Fix an assertion failure that could occur in caches or bridge users
19062 when using a very short voting interval on a testing network.
19063 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
19065 o Minor bugfixes (on 0.2.2.x):
19066 - Alter directory authorities to always consider Exit-flagged nodes
19067 as potential Guard nodes in their votes. The actual decision to
19068 use Exits as Guards is done in the consensus bandwidth weights.
19069 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
19070 - When the controller is reporting the purpose of circuits that
19071 didn't finish building before the circuit build timeout, it was
19072 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
19073 - Our libevent version parsing code couldn't handle versions like
19074 1.4.14b-stable and incorrectly warned the user about using an
19075 old and broken version of libevent. Treat 1.4.14b-stable like
19076 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
19078 - Don't use substitution references like $(VAR:MOD) when
19079 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
19080 '$(:x)' to 'x' rather than the empty string. This bites us in
19081 doc/ when configured with --disable-asciidoc. Bugfix on
19082 0.2.2.9-alpha; fixes bug 1773.
19083 - Remove a spurious hidden service server-side log notice about
19084 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
19086 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
19088 - Correctly report written bytes on linked connections. Found while
19089 implementing 1790. Bugfix on 0.2.2.4-alpha.
19090 - Fix three memory leaks: one in circuit_build_times_parse_state(),
19091 one in dirvote_add_signatures_to_pending_consensus(), and one every
19092 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
19093 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
19095 o Code simplifications and refactoring:
19096 - Take a first step towards making or.h smaller by splitting out
19097 function definitions for all source files in src/or/. Leave
19098 structures and defines in or.h for now.
19099 - Remove a bunch of unused function declarations as well as a block of
19100 #if 0'd code from the unit tests. Closes bug 1824.
19101 - New unit tests for exit-port history statistics; refactored exit
19102 statistics code to be more easily tested.
19103 - Remove the old debian/ directory from the main Tor distribution.
19104 The official Tor-for-debian git repository lives at the URL
19105 https://git.torproject.org/debian/tor.git
19108 Changes in version 0.2.2.14-alpha - 2010-07-12
19109 Tor 0.2.2.14-alpha greatly improves client-side handling of
19110 circuit build timeouts, which are used to estimate speed and improve
19111 performance. We also move to a much better GeoIP database, port Tor to
19112 Windows CE, introduce new compile flags that improve code security,
19113 add an eighth v3 directory authority, and address a lot of more
19117 - Tor directory authorities no longer crash when started with a
19118 cached-microdesc-consensus file in their data directory. Bugfix
19119 on 0.2.2.6-alpha; fixes bug 1532.
19120 - Treat an unset $HOME like an empty $HOME rather than triggering an
19121 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
19122 - Ignore negative and large circuit build timeout values that can
19123 happen during a suspend or hibernate. These values caused various
19124 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
19125 - Alter calculation of Pareto distribution parameter 'Xm' for
19126 Circuit Build Timeout learning to use the weighted average of the
19127 top N=3 modes (because we have three entry guards). Considering
19128 multiple modes should improve the timeout calculation in some cases,
19129 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
19131 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
19132 right censored distribution model. This approach improves over the
19133 synthetic timeout generation approach that was producing insanely
19134 high timeout values. Now we calculate build timeouts using truncated
19135 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
19136 - Do not close circuits that are under construction when they reach
19137 the circuit build timeout. Instead, leave them building (but do not
19138 use them) for up until the time corresponding to the 95th percentile
19139 on the Pareto CDF or 60 seconds, whichever is greater. This is done
19140 to provide better data for the new Pareto model. This percentile
19141 can be controlled by the consensus.
19144 - Move to the June 2010 Maxmind GeoLite country db (rather than the
19145 June 2009 ip-to-country GeoIP db) for our statistics that count
19146 how many users relays are seeing from each country. Now we have
19147 more accurate data for many African countries.
19148 - Port Tor to build and run correctly on Windows CE systems, using
19149 the wcecompat library. Contributed by Valerio Lupi.
19150 - New "--enable-gcc-hardening" ./configure flag (off by default)
19151 to turn on gcc compile time hardening options. It ensures
19152 that signed ints have defined behavior (-fwrapv), enables
19153 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
19154 with canaries (-fstack-protector-all), turns on ASLR protection if
19155 supported by the kernel (-fPIE, -pie), and adds additional security
19156 related warnings. Verified to work on Mac OS X and Debian Lenny.
19157 - New "--enable-linker-hardening" ./configure flag (off by default)
19158 to turn on ELF specific hardening features (relro, now). This does
19159 not work with Mac OS X or any other non-ELF binary format.
19161 o New directory authorities:
19162 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
19166 - New config option "WarnUnsafeSocks 0" disables the warning that
19167 occurs whenever Tor receives a socks handshake using a version of
19168 the socks protocol that can only provide an IP address (rather
19169 than a hostname). Setups that do DNS locally over Tor are fine,
19170 and we shouldn't spam the logs in that case.
19171 - Convert the HACKING file to asciidoc, and add a few new sections
19172 to it, explaining how we use Git, how we make changelogs, and
19173 what should go in a patch.
19174 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
19175 event, to give information on the current rate of circuit timeouts
19176 over our stored history.
19177 - Add ability to disable circuit build time learning via consensus
19178 parameter and via a LearnCircuitBuildTimeout config option. Also
19179 automatically disable circuit build time calculation if we are
19180 either a AuthoritativeDirectory, or if we fail to write our state
19181 file. Fixes bug 1296.
19182 - More gracefully handle corrupt state files, removing asserts
19183 in favor of saving a backup and resetting state.
19184 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
19188 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
19190 - When a2x fails, mention that the user could disable manpages instead
19191 of trying to fix their asciidoc installation.
19192 - Where available, use Libevent 2.0's periodic timers so that our
19193 once-per-second cleanup code gets called even more closely to
19194 once per second than it would otherwise. Fixes bug 943.
19195 - If you run a bridge that listens on multiple IP addresses, and
19196 some user configures a bridge address that uses a different IP
19197 address than your bridge writes in its router descriptor, and the
19198 user doesn't specify an identity key, their Tor would discard the
19199 descriptor because "it isn't one of our configured bridges", and
19200 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
19201 Bugfix on 0.2.0.3-alpha.
19202 - If OpenSSL fails to make a duplicate of a private or public key, log
19203 an error message and try to exit cleanly. May help with debugging
19204 if bug 1209 ever remanifests.
19205 - Save a couple bytes in memory allocation every time we escape
19206 certain characters in a string. Patch from Florian Zumbiehl.
19207 - Make it explicit that we don't cannibalize one-hop circuits. This
19208 happens in the wild, but doesn't turn out to be a problem because
19209 we fortunately don't use those circuits. Many thanks to outofwords
19210 for the initial analysis and to swissknife who confirmed that
19211 two-hop circuits are actually created.
19212 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
19213 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
19214 - Eliminate a case where a circuit build time warning was displayed
19215 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
19218 Changes in version 0.2.1.26 - 2010-05-02
19219 Tor 0.2.1.26 addresses the recent connection and memory overload
19220 problems we've been seeing on relays, especially relays with their
19221 DirPort open. If your relay has been crashing, or you turned it off
19222 because it used too many resources, give this release a try.
19224 This release also fixes yet another instance of broken OpenSSL libraries
19225 that was causing some relays to drop out of the consensus.
19228 - Teach relays to defend themselves from connection overload. Relays
19229 now close idle circuits early if it looks like they were intended
19230 for directory fetches. Relays are also more aggressive about closing
19231 TLS connections that have no circuits on them. Such circuits are
19232 unlikely to be re-used, and tens of thousands of them were piling
19233 up at the fast relays, causing the relays to run out of sockets
19234 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
19235 their directory fetches over TLS).
19236 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
19237 that claim to be earlier than 0.9.8m, but which have in reality
19238 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
19239 behavior. Possible fix for some cases of bug 1346.
19240 - Directory mirrors were fetching relay descriptors only from v2
19241 directory authorities, rather than v3 authorities like they should.
19242 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
19243 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
19246 - Finally get rid of the deprecated and now harmful notion of "clique
19247 mode", where directory authorities maintain TLS connections to
19251 - In the util/threads test, no longer free the test_mutex before all
19252 worker threads have finished. Bugfix on 0.2.1.6-alpha.
19253 - The master thread could starve the worker threads quite badly on
19254 certain systems, causing them to run only partially in the allowed
19255 window. This resulted in test failures. Now the master thread sleeps
19256 occasionally for a few microseconds while the two worker-threads
19257 compete for the mutex. Bugfix on 0.2.0.1-alpha.
19260 Changes in version 0.2.2.13-alpha - 2010-04-24
19261 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
19262 problems we've been seeing on relays, especially relays with their
19263 DirPort open. If your relay has been crashing, or you turned it off
19264 because it used too many resources, give this release a try.
19267 - Teach relays to defend themselves from connection overload. Relays
19268 now close idle circuits early if it looks like they were intended
19269 for directory fetches. Relays are also more aggressive about closing
19270 TLS connections that have no circuits on them. Such circuits are
19271 unlikely to be re-used, and tens of thousands of them were piling
19272 up at the fast relays, causing the relays to run out of sockets
19273 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
19274 their directory fetches over TLS).
19277 - Finally get rid of the deprecated and now harmful notion of "clique
19278 mode", where directory authorities maintain TLS connections to
19280 - Directory authorities now do an immediate reachability check as soon
19281 as they hear about a new relay. This change should slightly reduce
19282 the time between setting up a relay and getting listed as running
19283 in the consensus. It should also improve the time between setting
19284 up a bridge and seeing use by bridge users.
19285 - Directory authorities no longer launch a TLS connection to every
19286 relay as they startup. Now that we have 2k+ descriptors cached,
19287 the resulting network hiccup is becoming a burden. Besides,
19288 authorities already avoid voting about Running for the first half
19289 hour of their uptime.
19292 Changes in version 0.2.2.12-alpha - 2010-04-20
19293 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
19294 handle and vote on descriptors. It was causing relays to drop out of
19298 - Many relays have been falling out of the consensus lately because
19299 not enough authorities know about their descriptor for them to get
19300 a majority of votes. When we deprecated the v2 directory protocol,
19301 we got rid of the only way that v3 authorities can hear from each
19302 other about other descriptors. Now authorities examine every v3
19303 vote for new descriptors, and fetch them from that authority. Bugfix
19305 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
19306 and a warning in or.h related to bandwidth_weight_rule_t that
19307 prevented clean compile on OS X. Fixes bug 1363; bugfix on
19309 - Fix a segfault on relays when DirReqStatistics is enabled
19310 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
19314 - Demote a confusing TLS warning that relay operators might get when
19315 someone tries to talk to their OrPort. It is neither the operator's
19316 fault nor can they do anything about it. Fixes bug 1364; bugfix
19320 Changes in version 0.2.2.11-alpha - 2010-04-15
19321 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
19322 libraries that was causing some relays to drop out of the consensus.
19325 - Directory mirrors were fetching relay descriptors only from v2
19326 directory authorities, rather than v3 authorities like they should.
19327 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
19328 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
19329 - Fix a parsing error that made every possible value of
19330 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
19331 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
19332 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
19333 about the option without breaking older ones.
19334 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
19335 that claim to be earlier than 0.9.8m, but which have in reality
19336 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
19337 behavior. Possible fix for some cases of bug 1346.
19340 - Experiment with a more aggressive approach to preventing clients
19341 from making one-hop exit streams. Exit relays who want to try it
19342 out can set "RefuseUnknownExits 1" in their torrc, and then look
19343 for "Attempt by %s to open a stream" log messages. Let us know
19345 - Add support for statically linking zlib by specifying
19346 --enable-static-zlib, to go with our support for statically linking
19347 openssl and libevent. Resolves bug 1358.
19350 - Fix a segfault that happens whenever a Tor client that is using
19351 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
19353 - When we cleaned up the contrib/tor-exit-notice.html file, we left
19354 out the first line. Fixes bug 1295.
19355 - When building the manpage from a tarball, we required asciidoc, but
19356 the asciidoc -> roff/html conversion was already done for the
19357 tarball. Make 'make' complain only when we need asciidoc (either
19358 because we're compiling directly from git, or because we altered
19359 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
19360 - When none of the directory authorities vote on any params, Tor
19361 segfaulted when trying to make the consensus from the votes. We
19362 didn't trigger the bug in practice, because authorities do include
19363 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
19366 - In the util/threads test, no longer free the test_mutex before all
19367 worker threads have finished. Bugfix on 0.2.1.6-alpha.
19368 - The master thread could starve the worker threads quite badly on
19369 certain systems, causing them to run only partially in the allowed
19370 window. This resulted in test failures. Now the master thread sleeps
19371 occasionally for a few microseconds while the two worker-threads
19372 compete for the mutex. Bugfix on 0.2.0.1-alpha.
19375 Changes in version 0.2.2.10-alpha - 2010-03-07
19376 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
19377 could prevent relays from guessing their IP address correctly. It also
19378 starts the groundwork for another client-side performance boost, since
19379 currently we're not making efficient use of relays that have both the
19380 Guard flag and the Exit flag.
19383 - Fix a regression from our patch for bug 1244 that caused relays
19384 to guess their IP address incorrectly if they didn't set Address
19385 in their torrc and/or their address fails to resolve. Bugfix on
19386 0.2.2.9-alpha; fixes bug 1269.
19388 o Major features (performance):
19389 - Directory authorities now compute consensus weightings that instruct
19390 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
19391 and no flag. Clients that use these weightings will distribute
19392 network load more evenly across these different relay types. The
19393 weightings are in the consensus so we can change them globally in
19394 the future. Extra thanks to "outofwords" for finding some nasty
19395 security bugs in the first implementation of this feature.
19397 o Minor features (performance):
19398 - Always perform router selections using weighted relay bandwidth,
19399 even if we don't need a high capacity circuit at the time. Non-fast
19400 circuits now only differ from fast ones in that they can use relays
19401 not marked with the Fast flag. This "feature" could turn out to
19402 be a horrible bug; we should investigate more before it goes into
19406 - Allow disabling building of the manpages. Skipping the manpage
19407 speeds up the build considerably.
19409 o Minor bugfixes (on 0.2.2.x):
19410 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
19411 Bugfix on 0.2.2.9-alpha.
19412 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
19413 config option. Bugfix on 0.2.2.7-alpha.
19414 - Ship the asciidoc-helper file in the tarball, so that people can
19415 build from source if they want to, and touching the .1.txt files
19416 doesn't break the build. Bugfix on 0.2.2.9-alpha.
19418 o Minor bugfixes (on 0.2.1.x or earlier):
19419 - Fix a dereference-then-NULL-check sequence when publishing
19420 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
19422 - Fix another dereference-then-NULL-check sequence. Bugfix on
19423 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
19424 - Make sure we treat potentially not NUL-terminated strings correctly.
19425 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
19427 o Code simplifications and refactoring:
19428 - Fix some urls in the exit notice file and make it XHTML1.1 strict
19429 compliant. Based on a patch from Christian Kujau.
19430 - Don't use sed in asciidoc-helper anymore.
19431 - Make the build process fail if asciidoc cannot be found and
19432 building with asciidoc isn't disabled.
19435 Changes in version 0.2.2.9-alpha - 2010-02-22
19436 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
19437 location of a directory authority, and cleans up a bunch of small bugs.
19439 o Directory authority changes:
19440 - Change IP address for dannenberg (v3 directory authority), and
19441 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
19442 service directory authority) from the list.
19445 - Make Tor work again on the latest OS X: when deciding whether to
19446 use strange flags to turn TLS renegotiation on, detect the OpenSSL
19447 version at run-time, not compile time. We need to do this because
19448 Apple doesn't update its dev-tools headers when it updates its
19449 libraries in a security patch.
19450 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
19451 that could happen on 32-bit platforms with 64-bit time_t. Also fix
19452 a memory leak when requesting a hidden service descriptor we've
19453 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
19455 - Authorities could be tricked into giving out the Exit flag to relays
19456 that didn't allow exiting to any ports. This bug could screw
19457 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
19458 1238. Bug discovered by Martin Kowalczyk.
19459 - When freeing a session key, zero it out completely. We only zeroed
19460 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
19461 patched by ekir. Fixes bug 1254.
19464 - Fix static compilation by listing the openssl libraries in the right
19465 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
19466 - Resume handling .exit hostnames in a special way: originally we
19467 stripped the .exit part and used the requested exit relay. In
19468 0.2.2.1-alpha we stopped treating them in any special way, meaning
19469 if you use a .exit address then Tor will pass it on to the exit
19470 relay. Now we reject the .exit stream outright, since that behavior
19471 might be more expected by the user. Found and diagnosed by Scott
19472 Bennett and Downie on or-talk.
19473 - Don't spam the controller with events when we have no file
19474 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
19475 for log messages was already solved from bug 748.)
19476 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
19478 - Make the DNSPort option work with libevent 2.x. Don't alter the
19479 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
19480 - Emit a GUARD DROPPED controller event for a case we missed.
19481 - Make more fields in the controller protocol case-insensitive, since
19482 control-spec.txt said they were.
19483 - Refactor resolve_my_address() to not use gethostbyname() anymore.
19484 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
19485 - Fix a spec conformance issue: the network-status-version token
19486 must be the first token in a v3 consensus or vote. Discovered by
19487 parakeep. Bugfix on 0.2.0.3-alpha.
19489 o Code simplifications and refactoring:
19490 - Generate our manpage and HTML documentation using Asciidoc. This
19491 change should make it easier to maintain the documentation, and
19492 produce nicer HTML.
19493 - Remove the --enable-iphone option. According to reports from Marco
19494 Bonetti, Tor builds fine without any special tweaking on recent
19495 iPhone SDK versions.
19496 - Removed some unnecessary files from the source distribution. The
19497 AUTHORS file has now been merged into the people page on the
19498 website. The roadmaps and design doc can now be found in the
19499 projects directory in svn.
19500 - Enabled various circuit build timeout constants to be controlled
19501 by consensus parameters. Also set better defaults for these
19502 parameters based on experimentation on broadband and simulated
19503 high latency links.
19506 - The 'EXTENDCIRCUIT' control port command can now be used with
19507 a circ id of 0 and no path. This feature will cause Tor to build
19508 a new 'fast' general purpose circuit using its own path selection
19510 - Added a BUILDTIMEOUT_SET controller event to describe changes
19511 to the circuit build timeout.
19512 - Future-proof the controller protocol a bit by ignoring keyword
19513 arguments we do not recognize.
19514 - Expand homedirs passed to tor-checkkey. This should silence a
19515 coverity complaint about passing a user-supplied string into
19516 open() without checking it.
19519 Changes in version 0.2.1.25 - 2010-03-16
19520 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
19521 prevent relays from guessing their IP address correctly. It also fixes
19522 several minor potential security bugs.
19525 - Fix a regression from our patch for bug 1244 that caused relays
19526 to guess their IP address incorrectly if they didn't set Address
19527 in their torrc and/or their address fails to resolve. Bugfix on
19528 0.2.1.23; fixes bug 1269.
19529 - When freeing a session key, zero it out completely. We only zeroed
19530 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
19531 patched by ekir. Fixes bug 1254.
19534 - Fix a dereference-then-NULL-check sequence when publishing
19535 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
19537 - Fix another dereference-then-NULL-check sequence. Bugfix on
19538 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
19539 - Make sure we treat potentially not NUL-terminated strings correctly.
19540 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
19544 Changes in version 0.2.1.24 - 2010-02-21
19545 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
19549 - Work correctly out-of-the-box with even more vendor-patched versions
19550 of OpenSSL. In particular, make it so Debian and OS X don't need
19551 customized patches to run/build.
19554 Changes in version 0.2.1.23 - 2010-02-13
19555 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
19556 again on the latest OS X, and updates the location of a directory
19559 o Major bugfixes (performance):
19560 - We were selecting our guards uniformly at random, and then weighting
19561 which of our guards we'd use uniformly at random. This imbalance
19562 meant that Tor clients were severely limited on throughput (and
19563 probably latency too) by the first hop in their circuit. Now we
19564 select guards weighted by currently advertised bandwidth. We also
19565 automatically discard guards picked using the old algorithm. Fixes
19566 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
19569 - Make Tor work again on the latest OS X: when deciding whether to
19570 use strange flags to turn TLS renegotiation on, detect the OpenSSL
19571 version at run-time, not compile time. We need to do this because
19572 Apple doesn't update its dev-tools headers when it updates its
19573 libraries in a security patch.
19574 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
19575 that could happen on 32-bit platforms with 64-bit time_t. Also fix
19576 a memory leak when requesting a hidden service descriptor we've
19577 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
19580 o Directory authority changes:
19581 - Change IP address for dannenberg (v3 directory authority), and
19582 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
19583 service directory authority) from the list.
19586 - Refactor resolve_my_address() to not use gethostbyname() anymore.
19587 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
19590 - Avoid a mad rush at the beginning of each month when each client
19591 rotates half of its guards. Instead we spread the rotation out
19592 throughout the month, but we still avoid leaving a precise timestamp
19593 in the state file about when we first picked the guard. Improves
19594 over the behavior introduced in 0.1.2.17.
19597 Changes in version 0.2.2.8-alpha - 2010-01-26
19598 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
19599 causing bridge relays to disappear. If you're running a bridge,
19603 - Fix a memory corruption bug on bridges that occurred during the
19604 inclusion of stats data in extra-info descriptors. Also fix the
19605 interface for geoip_get_bridge_stats* to prevent similar bugs in
19606 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
19607 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
19610 - Ignore OutboundBindAddress when connecting to localhost.
19611 Connections to localhost need to come _from_ localhost, or else
19612 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
19616 Changes in version 0.2.2.7-alpha - 2010-01-19
19617 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
19618 as laying the groundwork for further relay-side performance fixes. It
19619 also starts cleaning up client behavior with respect to the EntryNodes,
19620 ExitNodes, and StrictNodes config options.
19622 This release also rotates two directory authority keys, due to a
19623 security breach of some of the Torproject servers.
19625 o Directory authority changes:
19626 - Rotate keys (both v3 identity and relay identity) for moria1
19629 o Major features (performance):
19630 - We were selecting our guards uniformly at random, and then weighting
19631 which of our guards we'd use uniformly at random. This imbalance
19632 meant that Tor clients were severely limited on throughput (and
19633 probably latency too) by the first hop in their circuit. Now we
19634 select guards weighted by currently advertised bandwidth. We also
19635 automatically discard guards picked using the old algorithm. Fixes
19636 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
19637 - When choosing which cells to relay first, relays can now favor
19638 circuits that have been quiet recently, to provide lower latency
19639 for low-volume circuits. By default, relays enable or disable this
19640 feature based on a setting in the consensus. You can override
19641 this default by using the new "CircuitPriorityHalflife" config
19642 option. Design and code by Ian Goldberg, Can Tang, and Chris
19644 - Add separate per-conn write limiting to go with the per-conn read
19645 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
19646 but never per-conn write limits.
19647 - New consensus params "bwconnrate" and "bwconnburst" to let us
19648 rate-limit client connections as they enter the network. It's
19649 controlled in the consensus so we can turn it on and off for
19650 experiments. It's starting out off. Based on proposal 163.
19652 o Major features (relay selection options):
19653 - Switch to a StrictNodes config option, rather than the previous
19654 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
19655 "StrictExcludeNodes" option.
19656 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
19657 change during a config reload, mark and discard all our origin
19658 circuits. This fix should address edge cases where we change the
19659 config options and but then choose a circuit that we created before
19661 - If EntryNodes or ExitNodes are set, be more willing to use an
19662 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
19664 - Make EntryNodes config option much more aggressive even when
19665 StrictNodes is not set. Before it would prepend your requested
19666 entrynodes to your list of guard nodes, but feel free to use others
19667 after that. Now it chooses only from your EntryNodes if any of
19668 those are available, and only falls back to others if a) they're
19669 all down and b) StrictNodes is not set.
19670 - Now we refresh your entry guards from EntryNodes at each consensus
19671 fetch -- rather than just at startup and then they slowly rot as
19672 the network changes.
19675 - Stop bridge directory authorities from answering dbg-stability.txt
19676 directory queries, which would let people fetch a list of all
19677 bridge identities they track. Bugfix on 0.2.1.6-alpha.
19680 - Log a notice when we get a new control connection. Now it's easier
19681 for security-conscious users to recognize when a local application
19682 is knocking on their controller door. Suggested by bug 1196.
19683 - New config option "CircuitStreamTimeout" to override our internal
19684 timeout schedule for how many seconds until we detach a stream from
19685 a circuit and try a new circuit. If your network is particularly
19686 slow, you might want to set this to a number like 60.
19687 - New controller command "getinfo config-text". It returns the
19688 contents that Tor would write if you send it a SAVECONF command,
19689 so the controller can write the file to disk itself.
19690 - New options for SafeLogging to allow scrubbing only log messages
19691 generated while acting as a relay.
19692 - Ship the bridges spec file in the tarball too.
19693 - Avoid a mad rush at the beginning of each month when each client
19694 rotates half of its guards. Instead we spread the rotation out
19695 throughout the month, but we still avoid leaving a precise timestamp
19696 in the state file about when we first picked the guard. Improves
19697 over the behavior introduced in 0.1.2.17.
19699 o Minor bugfixes (compiling):
19700 - Fix compilation on OS X 10.3, which has a stub mlockall() but
19701 hides it. Bugfix on 0.2.2.6-alpha.
19702 - Fix compilation on Solaris by removing support for the
19703 DisableAllSwap config option. Solaris doesn't have an rlimit for
19704 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
19707 o Minor bugfixes (crashes):
19708 - Do not segfault when writing buffer stats when we haven't observed
19709 a single circuit to report about. Found by Fabian Lanze. Bugfix on
19711 - If we're in the pathological case where there's no exit bandwidth
19712 but there is non-exit bandwidth, or no guard bandwidth but there
19713 is non-guard bandwidth, don't crash during path selection. Bugfix
19715 - Fix an impossible-to-actually-trigger buffer overflow in relay
19716 descriptor generation. Bugfix on 0.1.0.15.
19718 o Minor bugfixes (privacy):
19719 - Fix an instance where a Tor directory mirror might accidentally
19720 log the IP address of a misbehaving Tor client. Bugfix on
19722 - Don't list Windows capabilities in relay descriptors. We never made
19723 use of them, and maybe it's a bad idea to publish them. Bugfix
19726 o Minor bugfixes (other):
19727 - Resolve an edge case in path weighting that could make us misweight
19728 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
19729 - Fix statistics on client numbers by country as seen by bridges that
19730 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
19731 intervals instead of variable 12-to-48-hour intervals.
19732 - After we free an internal connection structure, overwrite it
19733 with a different memory value than we use for overwriting a freed
19734 internal circuit structure. Should help with debugging. Suggested
19736 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
19739 o Removed features:
19740 - Remove the HSAuthorityRecordStats option that version 0 hidden
19741 service authorities could have used to track statistics of overall
19742 hidden service usage.
19745 Changes in version 0.2.1.22 - 2010-01-19
19746 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
19747 authorities -- it would tell you its whole history of bridge descriptors
19748 if you make the right directory request. This stable update also
19749 rotates two of the seven v3 directory authority keys and locations.
19751 o Directory authority changes:
19752 - Rotate keys (both v3 identity and relay identity) for moria1
19756 - Stop bridge directory authorities from answering dbg-stability.txt
19757 directory queries, which would let people fetch a list of all
19758 bridge identities they track. Bugfix on 0.2.1.6-alpha.
19761 Changes in version 0.2.1.21 - 2009-12-21
19762 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
19763 library. If you use Tor on Linux / Unix and you're getting SSL
19764 renegotiation errors, upgrading should help. We also recommend an
19765 upgrade if you're an exit relay.
19768 - Work around a security feature in OpenSSL 0.9.8l that prevents our
19769 handshake from working unless we explicitly tell OpenSSL that we
19770 are using SSL renegotiation safely. We are, of course, but OpenSSL
19771 0.9.8l won't work unless we say we are.
19772 - Avoid crashing if the client is trying to upload many bytes and the
19773 circuit gets torn down at the same time, or if the flip side
19774 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
19777 - Do not refuse to learn about authority certs and v2 networkstatus
19778 documents that are older than the latest consensus. This bug might
19779 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
19780 Spotted and fixed by xmux.
19781 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
19782 trigger platform-specific option misparsing case found by Coverity
19784 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
19785 trigger assert. Fixes bug 1173.
19788 Changes in version 0.2.2.6-alpha - 2009-11-19
19789 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
19790 support for the new lower-footprint "microdescriptor" directory design,
19791 future-proofing our consensus format against new hash functions or
19792 other changes, and an Android port. It also makes Tor compatible with
19793 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
19796 - Directory authorities can now create, vote on, and serve multiple
19797 parallel formats of directory data as part of their voting process.
19798 Partially implements Proposal 162: "Publish the consensus in
19800 - Directory authorities can now agree on and publish small summaries
19801 of router information that clients can use in place of regular
19802 server descriptors. This transition will eventually allow clients
19803 to use far less bandwidth for downloading information about the
19804 network. Begins the implementation of Proposal 158: "Clients
19805 download consensus + microdescriptors".
19806 - The directory voting system is now extensible to use multiple hash
19807 algorithms for signatures and resource selection. Newer formats
19808 are signed with SHA256, with a possibility for moving to a better
19809 hash algorithm in the future.
19810 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
19811 current and future memory pages via mlockall(). On supported
19812 platforms (modern Linux and probably BSD but not Windows or OS X),
19813 this should effectively disable any and all attempts to page out
19814 memory. This option requires that you start your Tor as root --
19815 if you use DisableAllSwap, please consider using the User option
19816 to properly reduce the privileges of your Tor.
19817 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
19818 to help Tor build correctly for Android phones.
19821 - Work around a security feature in OpenSSL 0.9.8l that prevents our
19822 handshake from working unless we explicitly tell OpenSSL that we
19823 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
19824 won't work unless we say we are.
19827 - Fix a crash bug when trying to initialize the evdns module in
19828 Libevent 2. Bugfix on 0.2.1.16-rc.
19829 - Stop logging at severity 'warn' when some other Tor client tries
19830 to establish a circuit with us using weak DH keys. It's a protocol
19831 violation, but that doesn't mean ordinary users need to hear about
19832 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
19833 - Do not refuse to learn about authority certs and v2 networkstatus
19834 documents that are older than the latest consensus. This bug might
19835 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
19836 Spotted and fixed by xmux.
19837 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
19838 - If all authorities restart at once right before a consensus vote,
19839 nobody will vote about "Running", and clients will get a consensus
19840 with no usable relays. Instead, authorities refuse to build a
19841 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
19842 - If your relay can't keep up with the number of incoming create
19843 cells, it would log one warning per failure into your logs. Limit
19844 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
19845 - Bridges now use "reject *:*" as their default exit policy. Bugfix
19846 on 0.2.0.3-alpha; fixes bug 1113.
19847 - Fix a memory leak on directory authorities during voting that was
19848 introduced in 0.2.2.1-alpha. Found via valgrind.
19851 Changes in version 0.2.1.20 - 2009-10-15
19852 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
19853 services at once, prepares for more performance improvements, and
19854 fixes a bunch of smaller bugs.
19856 The Windows and OS X bundles also include a more recent Vidalia,
19857 and switch from Privoxy to Polipo.
19859 The OS X installers are now drag and drop. It's best to un-install
19860 Tor/Vidalia and then install this new bundle, rather than upgrade. If
19861 you want to upgrade, you'll need to update the paths for Tor and Polipo
19862 in the Vidalia Settings window.
19865 - Send circuit or stream sendme cells when our window has decreased
19866 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
19867 by Karsten when testing the "reduce circuit window" performance
19868 patch. Bugfix on the 54th commit on Tor -- from July 2002,
19869 before the release of Tor 0.0.0. This is the new winner of the
19871 - Fix a remotely triggerable memory leak when a consensus document
19872 contains more than one signature from the same voter. Bugfix on
19874 - Avoid segfault in rare cases when finishing an introduction circuit
19875 as a client and finding out that we don't have an introduction key
19876 for it. Fixes bug 1073. Reported by Aaron Swartz.
19879 - Tor now reads the "circwindow" parameter out of the consensus,
19880 and uses that value for its circuit package window rather than the
19881 default of 1000 cells. Begins the implementation of proposal 168.
19883 o New directory authorities:
19884 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
19886 - Move moria1 and tonga to alternate IP addresses.
19889 - Fix a signed/unsigned compile warning in 0.2.1.19.
19890 - Fix possible segmentation fault on directory authorities. Bugfix on
19892 - Fix an extremely rare infinite recursion bug that could occur if
19893 we tried to log a message after shutting down the log subsystem.
19894 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
19895 - Fix an obscure bug where hidden services on 64-bit big-endian
19896 systems might mis-read the timestamp in v3 introduce cells, and
19897 refuse to connect back to the client. Discovered by "rotor".
19898 Bugfix on 0.2.1.6-alpha.
19899 - We were triggering a CLOCK_SKEW controller status event whenever
19900 we connect via the v2 connection protocol to any relay that has
19901 a wrong clock. Instead, we should only inform the controller when
19902 it's a trusted authority that claims our clock is wrong. Bugfix
19903 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
19904 - We were telling the controller about CHECKING_REACHABILITY and
19905 REACHABILITY_FAILED status events whenever we launch a testing
19906 circuit or notice that one has failed. Instead, only tell the
19907 controller when we want to inform the user of overall success or
19908 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
19910 - Don't warn when we're using a circuit that ends with a node
19911 excluded in ExcludeExitNodes, but the circuit is not used to access
19912 the outside world. This should help fix bug 1090. Bugfix on
19914 - Work around a small memory leak in some versions of OpenSSL that
19915 stopped the memory used by the hostname TLS extension from being
19919 - Add a "getinfo status/accepted-server-descriptor" controller
19920 command, which is the recommended way for controllers to learn
19921 whether our server descriptor has been successfully received by at
19922 least on directory authority. Un-recommend good-server-descriptor
19923 getinfo and status events until we have a better design for them.
19926 Changes in version 0.2.2.5-alpha - 2009-10-11
19927 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
19930 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
19932 o Directory authorities:
19933 - Temporarily (just for this release) move dizum to an alternate
19937 Changes in version 0.2.2.4-alpha - 2009-10-10
19938 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
19939 introduces a new unit test framework, shifts directry authority
19940 addresses around to reduce the impact from recent blocking events,
19941 and fixes a few smaller bugs.
19944 - Fix several more asserts in the circuit_build_times code, for
19945 example one that causes Tor to fail to start once we have
19946 accumulated 5000 build times in the state file. Bugfixes on
19947 0.2.2.2-alpha; fixes bug 1108.
19949 o New directory authorities:
19950 - Move moria1 and Tonga to alternate IP addresses.
19953 - Log SSL state transitions at debug level during handshake, and
19954 include SSL states in error messages. This may help debug future
19955 SSL handshake issues.
19956 - Add a new "Handshake" log domain for activities that happen
19957 during the TLS handshake.
19958 - Revert to the "June 3 2009" ip-to-country file. The September one
19959 seems to have removed most US IP addresses.
19960 - Directory authorities now reject Tor relays with versions less than
19961 0.1.2.14. This step cuts out four relays from the current network,
19962 none of which are very big.
19965 - Fix a couple of smaller issues with gathering statistics. Bugfixes
19967 - Fix two memory leaks in the error case of
19968 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
19969 - Don't count one-hop circuits when we're estimating how long it
19970 takes circuits to build on average. Otherwise we'll set our circuit
19971 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
19972 - Directory authorities no longer change their opinion of, or vote on,
19973 whether a router is Running, unless they have themselves been
19974 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
19977 o Code simplifications and refactoring:
19978 - Revise our unit tests to use the "tinytest" framework, so we
19979 can run tests in their own processes, have smarter setup/teardown
19980 code, and so on. The unit test code has moved to its own
19981 subdirectory, and has been split into multiple modules.
19984 Changes in version 0.2.2.3-alpha - 2009-09-23
19985 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
19988 - Fix an overzealous assert in our new circuit build timeout code.
19989 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
19992 - If the networkstatus consensus tells us that we should use a
19993 negative circuit package window, ignore it. Otherwise we'll
19994 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
19997 Changes in version 0.2.2.2-alpha - 2009-09-21
19998 Tor 0.2.2.2-alpha introduces our latest performance improvement for
19999 clients: Tor tracks the average time it takes to build a circuit, and
20000 avoids using circuits that take too long to build. For fast connections,
20001 this feature can cut your expected latency in half. For slow or flaky
20002 connections, it could ruin your Tor experience. Let us know if it does!
20005 - Tor now tracks how long it takes to build client-side circuits
20006 over time, and adapts its timeout to local network performance.
20007 Since a circuit that takes a long time to build will also provide
20008 bad performance, we get significant latency improvements by
20009 discarding the slowest 20% of circuits. Specifically, Tor creates
20010 circuits more aggressively than usual until it has enough data
20011 points for a good timeout estimate. Implements proposal 151.
20012 We are especially looking for reports (good and bad) from users with
20013 both EDGE and broadband connections that can move from broadband
20014 to EDGE and find out if the build-time data in the .tor/state gets
20015 reset without loss of Tor usability. You should also see a notice
20016 log message telling you that Tor has reset its timeout.
20017 - Directory authorities can now vote on arbitrary integer values as
20018 part of the consensus process. This is designed to help set
20019 network-wide parameters. Implements proposal 167.
20020 - Tor now reads the "circwindow" parameter out of the consensus,
20021 and uses that value for its circuit package window rather than the
20022 default of 1000 cells. Begins the implementation of proposal 168.
20025 - Fix a remotely triggerable memory leak when a consensus document
20026 contains more than one signature from the same voter. Bugfix on
20030 - Fix an extremely rare infinite recursion bug that could occur if
20031 we tried to log a message after shutting down the log subsystem.
20032 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
20033 - Fix parsing for memory or time units given without a space between
20034 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
20035 - A networkstatus vote must contain exactly one signature. Spec
20036 conformance issue. Bugfix on 0.2.0.3-alpha.
20037 - Fix an obscure bug where hidden services on 64-bit big-endian
20038 systems might mis-read the timestamp in v3 introduce cells, and
20039 refuse to connect back to the client. Discovered by "rotor".
20040 Bugfix on 0.2.1.6-alpha.
20041 - We were triggering a CLOCK_SKEW controller status event whenever
20042 we connect via the v2 connection protocol to any relay that has
20043 a wrong clock. Instead, we should only inform the controller when
20044 it's a trusted authority that claims our clock is wrong. Bugfix
20045 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
20046 - We were telling the controller about CHECKING_REACHABILITY and
20047 REACHABILITY_FAILED status events whenever we launch a testing
20048 circuit or notice that one has failed. Instead, only tell the
20049 controller when we want to inform the user of overall success or
20050 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
20052 - Don't warn when we're using a circuit that ends with a node
20053 excluded in ExcludeExitNodes, but the circuit is not used to access
20054 the outside world. This should help fix bug 1090, but more problems
20055 remain. Bugfix on 0.2.1.6-alpha.
20056 - Work around a small memory leak in some versions of OpenSSL that
20057 stopped the memory used by the hostname TLS extension from being
20059 - Make our 'torify' script more portable; if we have only one of
20060 'torsocks' or 'tsocks' installed, don't complain to the user;
20061 and explain our warning about tsocks better.
20064 - Add a "getinfo status/accepted-server-descriptor" controller
20065 command, which is the recommended way for controllers to learn
20066 whether our server descriptor has been successfully received by at
20067 least on directory authority. Un-recommend good-server-descriptor
20068 getinfo and status events until we have a better design for them.
20069 - Update to the "September 4 2009" ip-to-country file.
20072 Changes in version 0.2.2.1-alpha - 2009-08-26
20073 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
20074 Tor clients to bootstrap on networks where only port 80 is reachable,
20075 makes it more straightforward to support hardware crypto accelerators,
20076 and starts the groundwork for gathering stats safely at relays.
20079 - Start the process of disabling ".exit" address notation, since it
20080 can be used for a variety of esoteric application-level attacks
20081 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
20084 o New directory authorities:
20085 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
20089 - New AccelName and AccelDir options add support for dynamic OpenSSL
20090 hardware crypto acceleration engines.
20091 - Tor now supports tunneling all of its outgoing connections over
20092 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
20093 configuration options. Code by Christopher Davis.
20096 - Send circuit or stream sendme cells when our window has decreased
20097 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
20098 by Karsten when testing the "reduce circuit window" performance
20099 patch. Bugfix on the 54th commit on Tor -- from July 2002,
20100 before the release of Tor 0.0.0. This is the new winner of the
20103 o New options for gathering stats safely:
20104 - Directory mirrors that set "DirReqStatistics 1" write statistics
20105 about directory requests to disk every 24 hours. As compared to the
20106 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
20107 1) stats are written to disk exactly every 24 hours; 2) estimated
20108 shares of v2 and v3 requests are determined as mean values, not at
20109 the end of a measurement period; 3) unresolved requests are listed
20110 with country code '??'; 4) directories also measure download times.
20111 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
20112 number of exit streams and transferred bytes per port to disk every
20114 - Relays that set "CellStatistics 1" write statistics on how long
20115 cells spend in their circuit queues to disk every 24 hours.
20116 - Entry nodes that set "EntryStatistics 1" write statistics on the
20117 rough number and origins of connecting clients to disk every 24
20119 - Relays that write any of the above statistics to disk and set
20120 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
20121 their extra-info documents.
20124 - New --digests command-line switch to output the digests of the
20125 source files Tor was built with.
20126 - The "torify" script now uses torsocks where available.
20127 - The memarea code now uses a sentinel value at the end of each area
20128 to make sure nothing writes beyond the end of an area. This might
20129 help debug some conceivable causes of bug 930.
20130 - Time and memory units in the configuration file can now be set to
20131 fractional units. For example, "2.5 GB" is now a valid value for
20133 - Certain Tor clients (such as those behind check.torproject.org) may
20134 want to fetch the consensus in an extra early manner. To enable this
20135 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
20136 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
20137 as only certain clients who must have this information sooner should
20139 - Instead of adding the svn revision to the Tor version string, report
20140 the git commit (when we're building from a git checkout).
20143 - If any of the v3 certs we download are unparseable, we should
20144 actually notice the failure so we don't retry indefinitely. Bugfix
20145 on 0.2.0.x; reported by "rotator".
20146 - If the cached cert file is unparseable, warn but don't exit.
20147 - Fix possible segmentation fault on directory authorities. Bugfix on
20149 - When Tor fails to parse a descriptor of any kind, dump it to disk.
20150 Might help diagnosing bug 1051.
20152 o Deprecated and removed features:
20153 - The controller no longer accepts the old obsolete "addr-mappings/"
20154 or "unregistered-servers-" GETINFO values.
20155 - Hidden services no longer publish version 0 descriptors, and clients
20156 do not request or use version 0 descriptors. However, the old hidden
20157 service authorities still accept and serve version 0 descriptors
20158 when contacted by older hidden services/clients.
20159 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
20160 always on; using them is necessary for correct forward-compatible
20162 - Remove support for .noconnect style addresses. Nobody was using
20163 them, and they provided another avenue for detecting Tor users
20164 via application-level web tricks.
20166 o Packaging changes:
20167 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
20168 installer bundles. See
20169 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
20170 for details of what's new in Vidalia 0.2.3.
20171 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
20172 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
20173 configuration file, rather than the old Privoxy.
20174 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
20175 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
20176 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
20177 better compatibility with OS X 10.6, aka Snow Leopard.
20178 - OS X Vidalia Bundle: The multi-package installer is now replaced
20179 by a simple drag and drop to the /Applications folder. This change
20180 occurred with the upgrade to Vidalia 0.2.3.
20183 Changes in version 0.2.1.19 - 2009-07-28
20184 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
20185 services on Tor 0.2.1.3-alpha through 0.2.1.18.
20188 - Make accessing hidden services on 0.2.1.x work right again.
20189 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
20190 part of patch provided by "optimist".
20193 - When a relay/bridge is writing out its identity key fingerprint to
20194 the "fingerprint" file and to its logs, write it without spaces. Now
20195 it will look like the fingerprints in our bridges documentation,
20196 and confuse fewer users.
20199 - Relays no longer publish a new server descriptor if they change
20200 their MaxAdvertisedBandwidth config option but it doesn't end up
20201 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
20202 fixes bug 1026. Patch from Sebastian.
20203 - Avoid leaking memory every time we get a create cell but we have
20204 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
20205 fixes bug 1034. Reported by BarkerJr.
20208 Changes in version 0.2.1.18 - 2009-07-24
20209 Tor 0.2.1.18 lays the foundations for performance improvements,
20210 adds status events to help users diagnose bootstrap problems, adds
20211 optional authentication/authorization for hidden services, fixes a
20212 variety of potential anonymity problems, and includes a huge pile of
20213 other features and bug fixes.
20216 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
20219 Changes in version 0.2.1.17-rc - 2009-07-07
20220 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
20221 candidate for the 0.2.1.x series. It lays the groundwork for further
20222 client performance improvements, and also fixes a big bug with directory
20223 authorities that were causing them to assign Guard and Stable flags
20226 The Windows bundles also finally include the geoip database that we
20227 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
20228 should actually install Torbutton rather than giving you a cryptic
20229 failure message (oops).
20232 - Clients now use the bandwidth values in the consensus, rather than
20233 the bandwidth values in each relay descriptor. This approach opens
20234 the door to more accurate bandwidth estimates once the directory
20235 authorities start doing active measurements. Implements more of
20239 - When Tor clients restart after 1-5 days, they discard all their
20240 cached descriptors as too old, but they still use the cached
20241 consensus document. This approach is good for robustness, but
20242 bad for performance: since they don't know any bandwidths, they
20243 end up choosing at random rather than weighting their choice by
20244 speed. Fixed by the above feature of putting bandwidths in the
20245 consensus. Bugfix on 0.2.0.x.
20246 - Directory authorities were neglecting to mark relays down in their
20247 internal histories if the relays fall off the routerlist without
20248 ever being found unreachable. So there were relays in the histories
20249 that haven't been seen for eight months, and are listed as being
20250 up for eight months. This wreaked havoc on the "median wfu"
20251 and "median mtbf" calculations, in turn making Guard and Stable
20252 flags very wrong, hurting network performance. Fixes bugs 696 and
20253 969. Bugfix on 0.2.0.6-alpha.
20256 - Serve the DirPortFrontPage page even when we have been approaching
20257 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
20258 - The control port would close the connection before flushing long
20259 replies, such as the network consensus, if a QUIT command was issued
20260 before the reply had completed. Now, the control port flushes all
20261 pending replies before closing the connection. Also fixed a spurious
20262 warning when a QUIT command is issued after a malformed or rejected
20263 AUTHENTICATE command, but before the connection was closed. Patch
20264 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
20265 - When we can't find an intro key for a v2 hidden service descriptor,
20266 fall back to the v0 hidden service descriptor and log a bug message.
20267 Workaround for bug 1024.
20268 - Fix a log message that did not respect the SafeLogging option.
20272 - If we're a relay and we change our IP address, be more verbose
20273 about the reason that made us change. Should help track down
20274 further bugs for relays on dynamic IP addresses.
20277 Changes in version 0.2.0.35 - 2009-06-24
20279 - Avoid crashing in the presence of certain malformed descriptors.
20280 Found by lark, and by automated fuzzing.
20281 - Fix an edge case where a malicious exit relay could convince a
20282 controller that the client's DNS question resolves to an internal IP
20283 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
20286 - Finally fix the bug where dynamic-IP relays disappear when their
20287 IP address changes: directory mirrors were mistakenly telling
20288 them their old address if they asked via begin_dir, so they
20289 never got an accurate answer about their new address, so they
20290 just vanished after a day. For belt-and-suspenders, relays that
20291 don't set Address in their config now avoid using begin_dir for
20292 all direct connections. Should fix bugs 827, 883, and 900.
20293 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
20294 that would occur on some exit nodes when DNS failures and timeouts
20295 occurred in certain patterns. Fix for bug 957.
20298 - When starting with a cache over a few days old, do not leak
20299 memory for the obsolete router descriptors in it. Bugfix on
20300 0.2.0.33; fixes bug 672.
20301 - Hidden service clients didn't use a cached service descriptor that
20302 was older than 15 minutes, but wouldn't fetch a new one either,
20303 because there was already one in the cache. Now, fetch a v2
20304 descriptor unless the same descriptor was added to the cache within
20305 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
20308 Changes in version 0.2.1.16-rc - 2009-06-20
20309 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
20310 a bunch of minor bugs.
20313 - Fix an edge case where a malicious exit relay could convince a
20314 controller that the client's DNS question resolves to an internal IP
20315 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
20317 o Major performance improvements (on 0.2.0.x):
20318 - Disable and refactor some debugging checks that forced a linear scan
20319 over the whole server-side DNS cache. These accounted for over 50%
20320 of CPU time on a relatively busy exit node's gprof profile. Found
20322 - Disable some debugging checks that appeared in exit node profile
20326 - Update to the "June 3 2009" ip-to-country file.
20327 - Do not have tor-resolve automatically refuse all .onion addresses;
20328 if AutomapHostsOnResolve is set in your torrc, this will work fine.
20330 o Minor bugfixes (on 0.2.0.x):
20331 - Log correct error messages for DNS-related network errors on
20333 - Fix a race condition that could cause crashes or memory corruption
20334 when running as a server with a controller listening for log
20336 - Avoid crashing when we have a policy specified in a DirPolicy or
20337 SocksPolicy or ReachableAddresses option with ports set on it,
20338 and we re-load the policy. May fix bug 996.
20339 - Hidden service clients didn't use a cached service descriptor that
20340 was older than 15 minutes, but wouldn't fetch a new one either,
20341 because there was already one in the cache. Now, fetch a v2
20342 descriptor unless the same descriptor was added to the cache within
20343 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
20345 o Minor bugfixes (on 0.2.1.x):
20346 - Don't warn users about low port and hibernation mix when they
20347 provide a *ListenAddress directive to fix that. Bugfix on
20349 - When switching back and forth between bridge mode, do not start
20350 gathering GeoIP data until two hours have passed.
20351 - Do not complain that the user has requested an excluded node as
20352 an exit when the node is not really an exit. This could happen
20353 because the circuit was for testing, or an introduction point.
20357 Changes in version 0.2.1.15-rc - 2009-05-25
20358 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
20359 series. It fixes a major bug on fast exit relays, as well as a variety
20360 of more minor bugs.
20362 o Major bugfixes (on 0.2.0.x):
20363 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
20364 that would occur on some exit nodes when DNS failures and timeouts
20365 occurred in certain patterns. Fix for bug 957.
20367 o Minor bugfixes (on 0.2.0.x):
20368 - Actually return -1 in the error case for read_bandwidth_usage().
20369 Harmless bug, since we currently don't care about the return value
20370 anywhere. Bugfix on 0.2.0.9-alpha.
20371 - Provide a more useful log message if bug 977 (related to buffer
20372 freelists) ever reappears, and do not crash right away.
20373 - Fix an assertion failure on 64-bit platforms when we allocated
20374 memory right up to the end of a memarea, then realigned the memory
20375 one step beyond the end. Fixes a possible cause of bug 930.
20376 - Protect the count of open sockets with a mutex, so we can't
20377 corrupt it when two threads are closing or opening sockets at once.
20378 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
20379 - Don't allow a bridge to publish its router descriptor to a
20380 non-bridge directory authority. Fixes part of bug 932.
20381 - When we change to or from being a bridge, reset our counts of
20382 client usage by country. Fixes bug 932.
20383 - Fix a bug that made stream bandwidth get misreported to the
20385 - Stop using malloc_usable_size() to use more area than we had
20386 actually allocated: it was safe, but made valgrind really unhappy.
20387 - Fix a memory leak when v3 directory authorities load their keys
20388 and cert from disk. Bugfix on 0.2.0.1-alpha.
20390 o Minor bugfixes (on 0.2.1.x):
20391 - Fix use of freed memory when deciding to mark a non-addable
20392 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
20395 Changes in version 0.2.1.14-rc - 2009-04-12
20396 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
20397 series. It begins fixing some major performance problems, and also
20398 finally addresses the bug that was causing relays on dynamic IP
20399 addresses to fall out of the directory.
20402 - Clients replace entry guards that were chosen more than a few months
20403 ago. This change should significantly improve client performance,
20404 especially once more people upgrade, since relays that have been
20405 a guard for a long time are currently overloaded.
20407 o Major bugfixes (on 0.2.0):
20408 - Finally fix the bug where dynamic-IP relays disappear when their
20409 IP address changes: directory mirrors were mistakenly telling
20410 them their old address if they asked via begin_dir, so they
20411 never got an accurate answer about their new address, so they
20412 just vanished after a day. For belt-and-suspenders, relays that
20413 don't set Address in their config now avoid using begin_dir for
20414 all direct connections. Should fix bugs 827, 883, and 900.
20415 - Relays were falling out of the networkstatus consensus for
20416 part of a day if they changed their local config but the
20417 authorities discarded their new descriptor as "not sufficiently
20418 different". Now directory authorities accept a descriptor as changed
20419 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
20420 patch by Sebastian.
20421 - Avoid crashing in the presence of certain malformed descriptors.
20422 Found by lark, and by automated fuzzing.
20425 - When generating circuit events with verbose nicknames for
20426 controllers, try harder to look up nicknames for routers on a
20427 circuit. (Previously, we would look in the router descriptors we had
20428 for nicknames, but not in the consensus.) Partial fix for bug 941.
20429 - If the bridge config line doesn't specify a port, assume 443.
20430 This makes bridge lines a bit smaller and easier for users to
20432 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
20433 bytes (aka 20KB/s), to match our documentation. Also update
20434 directory authorities so they always assign the Fast flag to relays
20435 with 20KB/s of capacity. Now people running relays won't suddenly
20436 find themselves not seeing any use, if the network gets faster
20438 - Update to the "April 3 2009" ip-to-country file.
20441 - Avoid trying to print raw memory to the logs when we decide to
20442 give up on downloading a given relay descriptor. Bugfix on
20444 - In tor-resolve, when the Tor client to use is specified by
20445 <hostname>:<port>, actually use the specified port rather than
20446 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
20447 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
20448 - When starting with a cache over a few days old, do not leak
20449 memory for the obsolete router descriptors in it. Bugfix on
20451 - Avoid double-free on list of successfully uploaded hidden
20452 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
20453 - Change memarea_strndup() implementation to work even when
20454 duplicating a string at the end of a page. This bug was
20455 harmless for now, but could have meant crashes later. Fix by
20456 lark. Bugfix on 0.2.1.1-alpha.
20457 - Limit uploaded directory documents to be 16M rather than 500K.
20458 The directory authorities were refusing v3 consensus votes from
20459 other authorities, since the votes are now 504K. Fixes bug 959;
20460 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
20461 - Directory authorities should never send a 503 "busy" response to
20462 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
20466 Changes in version 0.2.1.13-alpha - 2009-03-09
20467 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
20468 cleanups. We're finally getting close to a release candidate.
20471 - Correctly update the list of which countries we exclude as
20472 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
20473 lark. Bugfix on 0.2.1.6-alpha.
20475 o Minor bugfixes (on 0.2.0.x and earlier):
20476 - Automatically detect MacOSX versions earlier than 10.4.0, and
20477 disable kqueue from inside Tor when running with these versions.
20478 We previously did this from the startup script, but that was no
20479 help to people who didn't use the startup script. Resolves bug 863.
20480 - When we had picked an exit node for a connection, but marked it as
20481 "optional", and it turned out we had no onion key for the exit,
20482 stop wanting that exit and try again. This situation may not
20483 be possible now, but will probably become feasible with proposal
20484 158. Spotted by rovv. Fixes another case of bug 752.
20485 - Clients no longer cache certificates for authorities they do not
20486 recognize. Bugfix on 0.2.0.9-alpha.
20487 - When we can't transmit a DNS request due to a network error, retry
20488 it after a while, and eventually transmit a failing response to
20489 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
20490 - If the controller claimed responsibility for a stream, but that
20491 stream never finished making its connection, it would live
20492 forever in circuit_wait state. Now we close it after SocksTimeout
20493 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
20494 - Drop begin cells to a hidden service if they come from the middle
20495 of a circuit. Patch from lark.
20496 - When we erroneously receive two EXTEND cells for the same circuit
20497 ID on the same connection, drop the second. Patch from lark.
20498 - Fix a crash that occurs on exit nodes when a nameserver request
20499 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
20500 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
20502 - Do not assume that a stack-allocated character array will be
20503 64-bit aligned on platforms that demand that uint64_t access is
20504 aligned. Possible fix for bug 604.
20505 - Parse dates and IPv4 addresses in a locale- and libc-independent
20506 manner, to avoid platform-dependent behavior on malformed input.
20507 - Build correctly when configured to build outside the main source
20508 path. Patch from Michael Gold.
20509 - We were already rejecting relay begin cells with destination port
20510 of 0. Now also reject extend cells with destination port or address
20511 of 0. Suggested by lark.
20513 o Minor bugfixes (on 0.2.1.x):
20514 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
20515 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
20516 - If we're an exit node, scrub the IP address to which we are exiting
20517 in the logs. Bugfix on 0.2.1.8-alpha.
20520 - On Linux, use the prctl call to re-enable core dumps when the user
20522 - New controller event NEWCONSENSUS that lists the networkstatus
20523 lines for every recommended relay. Now controllers like Torflow
20524 can keep up-to-date on which relays they should be using.
20525 - Update to the "February 26 2009" ip-to-country file.
20528 Changes in version 0.2.0.34 - 2009-02-08
20529 Tor 0.2.0.34 features several more security-related fixes. You should
20530 upgrade, especially if you run an exit relay (remote crash) or a
20531 directory authority (remote infinite loop), or you're on an older
20532 (pre-XP) or not-recently-patched Windows (remote exploit).
20534 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
20535 have many known flaws, and nobody should be using them. You should
20536 upgrade. If you're using a Linux or BSD and its packages are obsolete,
20537 stop using those packages and upgrade anyway.
20540 - Fix an infinite-loop bug on handling corrupt votes under certain
20541 circumstances. Bugfix on 0.2.0.8-alpha.
20542 - Fix a temporary DoS vulnerability that could be performed by
20543 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
20544 - Avoid a potential crash on exit nodes when processing malformed
20545 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
20546 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
20547 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
20550 - Fix compilation on systems where time_t is a 64-bit integer.
20551 Patch from Matthias Drochner.
20552 - Don't consider expiring already-closed client connections. Fixes
20553 bug 893. Bugfix on 0.0.2pre20.
20556 Changes in version 0.2.1.12-alpha - 2009-02-08
20557 Tor 0.2.1.12-alpha features several more security-related fixes. You
20558 should upgrade, especially if you run an exit relay (remote crash) or
20559 a directory authority (remote infinite loop), or you're on an older
20560 (pre-XP) or not-recently-patched Windows (remote exploit). It also
20561 includes a big pile of minor bugfixes and cleanups.
20564 - Fix an infinite-loop bug on handling corrupt votes under certain
20565 circumstances. Bugfix on 0.2.0.8-alpha.
20566 - Fix a temporary DoS vulnerability that could be performed by
20567 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
20568 - Avoid a potential crash on exit nodes when processing malformed
20569 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
20572 - Let controllers actually ask for the "clients_seen" event for
20573 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
20574 reported by Matt Edman.
20575 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
20577 - Fix a bug in address parsing that was preventing bridges or hidden
20578 service targets from being at IPv6 addresses.
20579 - Solve a bug that kept hardware crypto acceleration from getting
20580 enabled when accounting was turned on. Fixes bug 907. Bugfix on
20582 - Remove a bash-ism from configure.in to build properly on non-Linux
20583 platforms. Bugfix on 0.2.1.1-alpha.
20584 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
20585 headers. Bugfix on 0.2.0.10-alpha.
20586 - Don't consider expiring already-closed client connections. Fixes
20587 bug 893. Bugfix on 0.0.2pre20.
20588 - Fix another interesting corner-case of bug 891 spotted by rovv:
20589 Previously, if two hosts had different amounts of clock drift, and
20590 one of them created a new connection with just the wrong timing,
20591 the other might decide to deprecate the new connection erroneously.
20592 Bugfix on 0.1.1.13-alpha.
20593 - Resolve a very rare crash bug that could occur when the user forced
20594 a nameserver reconfiguration during the middle of a nameserver
20595 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
20596 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
20597 Bugfix on 0.2.1.7-alpha.
20598 - If we're using bridges and our network goes away, be more willing
20599 to forgive our bridges and try again when we get an application
20600 request. Bugfix on 0.2.0.x.
20603 - Support platforms where time_t is 64 bits long. (Congratulations,
20604 NetBSD!) Patch from Matthias Drochner.
20605 - Add a 'getinfo status/clients-seen' controller command, in case
20606 controllers want to hear clients_seen events but connect late.
20609 - Disable GCC's strict alias optimization by default, to avoid the
20610 likelihood of its introducing subtle bugs whenever our code violates
20611 the letter of C99's alias rules.
20614 Changes in version 0.2.0.33 - 2009-01-21
20615 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
20616 useful to users. It also finally fixes a bug where a relay or client
20617 that's been off for many days would take a long time to bootstrap.
20619 This update also fixes an important security-related bug reported by
20620 Ilja van Sprundel. You should upgrade. (We'll send out more details
20621 about the bug once people have had some time to upgrade.)
20624 - Fix a heap-corruption bug that may be remotely triggerable on
20625 some platforms. Reported by Ilja van Sprundel.
20628 - When a stream at an exit relay is in state "resolving" or
20629 "connecting" and it receives an "end" relay cell, the exit relay
20630 would silently ignore the end cell and not close the stream. If
20631 the client never closes the circuit, then the exit relay never
20632 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
20633 reported by "wood".
20634 - When sending CREATED cells back for a given circuit, use a 64-bit
20635 connection ID to find the right connection, rather than an addr:port
20636 combination. Now that we can have multiple OR connections between
20637 the same ORs, it is no longer possible to use addr:port to uniquely
20638 identify a connection.
20639 - Bridge relays that had DirPort set to 0 would stop fetching
20640 descriptors shortly after startup, and then briefly resume
20641 after a new bandwidth test and/or after publishing a new bridge
20642 descriptor. Bridge users that try to bootstrap from them would
20643 get a recent networkstatus but would get descriptors from up to
20644 18 hours earlier, meaning most of the descriptors were obsolete
20645 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
20646 - Prevent bridge relays from serving their 'extrainfo' document
20647 to anybody who asks, now that extrainfo docs include potentially
20648 sensitive aggregated client geoip summaries. Bugfix on
20650 - If the cached networkstatus consensus is more than five days old,
20651 discard it rather than trying to use it. In theory it could be
20652 useful because it lists alternate directory mirrors, but in practice
20653 it just means we spend many minutes trying directory mirrors that
20654 are long gone from the network. Also discard router descriptors as
20655 we load them if they are more than five days old, since the onion
20656 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
20659 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
20660 could make gcc generate non-functional binary search code. Bugfix
20662 - Build correctly on platforms without socklen_t.
20663 - Compile without warnings on solaris.
20664 - Avoid potential crash on internal error during signature collection.
20665 Fixes bug 864. Patch from rovv.
20666 - Correct handling of possible malformed authority signing key
20667 certificates with internal signature types. Fixes bug 880.
20668 Bugfix on 0.2.0.3-alpha.
20669 - Fix a hard-to-trigger resource leak when logging credential status.
20671 - When we can't initialize DNS because the network is down, do not
20672 automatically stop Tor from starting. Instead, we retry failed
20673 dns_init() every 10 minutes, and change the exit policy to reject
20674 *:* until one succeeds. Fixes bug 691.
20675 - Use 64 bits instead of 32 bits for connection identifiers used with
20676 the controller protocol, to greatly reduce risk of identifier reuse.
20677 - When we're choosing an exit node for a circuit, and we have
20678 no pending streams, choose a good general exit rather than one that
20679 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
20680 - Fix another case of assuming, when a specific exit is requested,
20681 that we know more than the user about what hosts it allows.
20682 Fixes one case of bug 752. Patch from rovv.
20683 - Clip the MaxCircuitDirtiness config option to a minimum of 10
20684 seconds. Warn the user if lower values are given in the
20685 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
20686 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
20687 user if lower values are given in the configuration. Bugfix on
20688 0.1.1.17-rc. Patch by Sebastian.
20689 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
20690 the cache because we already had a v0 descriptor with the same ID.
20691 Bugfix on 0.2.0.18-alpha.
20692 - Fix a race condition when freeing keys shared between main thread
20693 and CPU workers that could result in a memory leak. Bugfix on
20694 0.1.0.1-rc. Fixes bug 889.
20695 - Send a valid END cell back when a client tries to connect to a
20696 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
20697 840. Patch from rovv.
20698 - Check which hops rendezvous stream cells are associated with to
20699 prevent possible guess-the-streamid injection attacks from
20700 intermediate hops. Fixes another case of bug 446. Based on patch
20702 - If a broken client asks a non-exit router to connect somewhere,
20703 do not even do the DNS lookup before rejecting the connection.
20704 Fixes another case of bug 619. Patch from rovv.
20705 - When a relay gets a create cell it can't decrypt (e.g. because it's
20706 using the wrong onion key), we were dropping it and letting the
20707 client time out. Now actually answer with a destroy cell. Fixes
20708 bug 904. Bugfix on 0.0.2pre8.
20710 o Minor bugfixes (hidden services):
20711 - Do not throw away existing introduction points on SIGHUP. Bugfix on
20712 0.0.6pre1. Patch by Karsten. Fixes bug 874.
20715 - Report the case where all signatures in a detached set are rejected
20716 differently than the case where there is an error handling the
20718 - When we realize that another process has modified our cached
20719 descriptors, print out a more useful error message rather than
20720 triggering an assertion. Fixes bug 885. Patch from Karsten.
20721 - Implement the 0x20 hack to better resist DNS poisoning: set the
20722 case on outgoing DNS requests randomly, and reject responses that do
20723 not match the case correctly. This logic can be disabled with the
20724 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
20725 of servers that do not reliably preserve case in replies. See
20726 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
20728 - Check DNS replies for more matching fields to better resist DNS
20730 - Never use OpenSSL compression: it wastes RAM and CPU trying to
20731 compress cells, which are basically all encrypted, compressed, or
20735 Changes in version 0.2.1.11-alpha - 2009-01-20
20736 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
20737 week it will take a long time to bootstrap again" bug. It also fixes
20738 an important security-related bug reported by Ilja van Sprundel. You
20739 should upgrade. (We'll send out more details about the bug once people
20740 have had some time to upgrade.)
20743 - Fix a heap-corruption bug that may be remotely triggerable on
20744 some platforms. Reported by Ilja van Sprundel.
20747 - Discard router descriptors as we load them if they are more than
20748 five days old. Otherwise if Tor is off for a long time and then
20749 starts with cached descriptors, it will try to use the onion
20750 keys in those obsolete descriptors when building circuits. Bugfix
20751 on 0.2.0.x. Fixes bug 887.
20754 - Try to make sure that the version of Libevent we're running with
20755 is binary-compatible with the one we built with. May address bug
20757 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
20758 for bug 905. Bugfix on 0.2.1.7-alpha.
20759 - Add a new --enable-local-appdata configuration switch to change
20760 the default location of the datadir on win32 from APPDATA to
20761 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
20762 entirely. Patch from coderman.
20765 - Make outbound DNS packets respect the OutboundBindAddress setting.
20766 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
20767 - When our circuit fails at the first hop (e.g. we get a destroy
20768 cell back), avoid using that OR connection anymore, and also
20769 tell all the one-hop directory requests waiting for it that they
20770 should fail. Bugfix on 0.2.1.3-alpha.
20771 - In the torify(1) manpage, mention that tsocks will leak your
20775 Changes in version 0.2.1.10-alpha - 2009-01-06
20776 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
20777 would make the bridge relay not so useful if it had DirPort set to 0,
20778 and one that could let an attacker learn a little bit of information
20779 about the bridge's users), and a bug that would cause your Tor relay
20780 to ignore a circuit create request it can't decrypt (rather than reply
20781 with an error). It also fixes a wide variety of other bugs.
20784 - If the cached networkstatus consensus is more than five days old,
20785 discard it rather than trying to use it. In theory it could
20786 be useful because it lists alternate directory mirrors, but in
20787 practice it just means we spend many minutes trying directory
20788 mirrors that are long gone from the network. Helps bug 887 a bit;
20790 - Bridge relays that had DirPort set to 0 would stop fetching
20791 descriptors shortly after startup, and then briefly resume
20792 after a new bandwidth test and/or after publishing a new bridge
20793 descriptor. Bridge users that try to bootstrap from them would
20794 get a recent networkstatus but would get descriptors from up to
20795 18 hours earlier, meaning most of the descriptors were obsolete
20796 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
20797 - Prevent bridge relays from serving their 'extrainfo' document
20798 to anybody who asks, now that extrainfo docs include potentially
20799 sensitive aggregated client geoip summaries. Bugfix on
20803 - New controller event "clients_seen" to report a geoip-based summary
20804 of which countries we've seen clients from recently. Now controllers
20805 like Vidalia can show bridge operators that they're actually making
20807 - Build correctly against versions of OpenSSL 0.9.8 or later built
20808 without support for deprecated functions.
20809 - Update to the "December 19 2008" ip-to-country file.
20811 o Minor bugfixes (on 0.2.0.x):
20812 - Authorities now vote for the Stable flag for any router whose
20813 weighted MTBF is at least 5 days, regardless of the mean MTBF.
20814 - Do not remove routers as too old if we do not have any consensus
20815 document. Bugfix on 0.2.0.7-alpha.
20816 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
20817 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
20818 - When an exit relay resolves a stream address to a local IP address,
20819 do not just keep retrying that same exit relay over and
20820 over. Instead, just close the stream. Addresses bug 872. Bugfix
20821 on 0.2.0.32. Patch from rovv.
20822 - If a hidden service sends us an END cell, do not consider
20823 retrying the connection; just close it. Patch from rovv.
20824 - When we made bridge authorities stop serving bridge descriptors over
20825 unencrypted links, we also broke DirPort reachability testing for
20826 bridges. So bridges with a non-zero DirPort were printing spurious
20827 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
20828 - When a relay gets a create cell it can't decrypt (e.g. because it's
20829 using the wrong onion key), we were dropping it and letting the
20830 client time out. Now actually answer with a destroy cell. Fixes
20831 bug 904. Bugfix on 0.0.2pre8.
20832 - Squeeze 2-5% out of client performance (according to oprofile) by
20833 improving the implementation of some policy-manipulation functions.
20835 o Minor bugfixes (on 0.2.1.x):
20836 - Make get_interface_address() function work properly again; stop
20837 guessing the wrong parts of our address as our address.
20838 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
20839 send on that circuit. Otherwise we might violate the proposal-110
20840 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
20842 - When we're sending non-EXTEND cells to the first hop in a circuit,
20843 for example to use an encrypted directory connection, we don't need
20844 to use RELAY_EARLY cells: the first hop knows what kind of cell
20845 it is, and nobody else can even see the cell type. Conserving
20846 RELAY_EARLY cells makes it easier to cannibalize circuits like
20848 - Stop logging nameserver addresses in reverse order.
20849 - If we are retrying a directory download slowly over and over, do
20850 not automatically give up after the 254th failure. Bugfix on
20852 - Resume reporting accurate "stream end" reasons to the local control
20853 port. They were lost in the changes for Proposal 148. Bugfix on
20856 o Deprecated and removed features:
20857 - The old "tor --version --version" command, which would print out
20858 the subversion "Id" of most of the source files, is now removed. It
20859 turned out to be less useful than we'd expected, and harder to
20862 o Code simplifications and refactoring:
20863 - Change our header file guard macros to be less likely to conflict
20864 with system headers. Adam Langley noticed that we were conflicting
20865 with log.h on Android.
20866 - Tool-assisted documentation cleanup. Nearly every function or
20867 static variable in Tor should have its own documentation now.
20870 Changes in version 0.2.1.9-alpha - 2008-12-25
20871 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
20873 o New directory authorities:
20874 - gabelmoo (the authority run by Karsten Loesing) now has a new
20878 - Never use a connection with a mismatched address to extend a
20879 circuit, unless that connection is canonical. A canonical
20880 connection is one whose address is authenticated by the router's
20881 identity key, either in a NETINFO cell or in a router descriptor.
20882 - Avoid a possible memory corruption bug when receiving hidden service
20883 descriptors. Bugfix on 0.2.1.6-alpha.
20886 - Fix a logic error that would automatically reject all but the first
20887 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
20888 part of bug 813/868. Bug spotted by coderman.
20889 - When a stream at an exit relay is in state "resolving" or
20890 "connecting" and it receives an "end" relay cell, the exit relay
20891 would silently ignore the end cell and not close the stream. If
20892 the client never closes the circuit, then the exit relay never
20893 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
20894 reported by "wood".
20895 - When we can't initialize DNS because the network is down, do not
20896 automatically stop Tor from starting. Instead, retry failed
20897 dns_init() every 10 minutes, and change the exit policy to reject
20898 *:* until one succeeds. Fixes bug 691.
20901 - Give a better error message when an overzealous init script says
20902 "sudo -u username tor --user username". Makes Bug 882 easier for
20904 - When a directory authority gives us a new guess for our IP address,
20905 log which authority we used. Hopefully this will help us debug
20906 the recent complaints about bad IP address guesses.
20907 - Detect svn revision properly when we're using git-svn.
20908 - Try not to open more than one descriptor-downloading connection
20909 to an authority at once. This should reduce load on directory
20910 authorities. Fixes bug 366.
20911 - Add cross-certification to newly generated certificates, so that
20912 a signing key is enough information to look up a certificate.
20913 Partial implementation of proposal 157.
20914 - Start serving certificates by <identity digest, signing key digest>
20915 pairs. Partial implementation of proposal 157.
20916 - Clients now never report any stream end reason except 'MISC'.
20917 Implements proposal 148.
20918 - On platforms with a maximum syslog string length, truncate syslog
20919 messages to that length ourselves, rather than relying on the
20920 system to do it for us.
20921 - Optimize out calls to time(NULL) that occur for every IO operation,
20922 or for every cell. On systems where time() is a slow syscall,
20923 this fix will be slightly helpful.
20924 - Exit servers can now answer resolve requests for ip6.arpa addresses.
20925 - When we download a descriptor that we then immediately (as
20926 a directory authority) reject, do not retry downloading it right
20927 away. Should save some bandwidth on authorities. Fix for bug
20928 888. Patch by Sebastian Hahn.
20929 - When a download gets us zero good descriptors, do not notify
20930 Tor that new directory information has arrived.
20931 - Avoid some nasty corner cases in the logic for marking connections
20932 as too old or obsolete or noncanonical for circuits. Partial
20935 o Minor features (controller):
20936 - New CONSENSUS_ARRIVED event to note when a new consensus has
20937 been fetched and validated.
20938 - When we realize that another process has modified our cached
20939 descriptors file, print out a more useful error message rather
20940 than triggering an assertion. Fixes bug 885. Patch from Karsten.
20941 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
20942 controllers to prevent SIGHUP from reloading the
20943 configuration. Fixes bug 856.
20946 - Resume using the correct "REASON=" stream when telling the
20947 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
20948 - When a canonical connection appears later in our internal list
20949 than a noncanonical one for a given OR ID, always use the
20950 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
20952 - Clip the MaxCircuitDirtiness config option to a minimum of 10
20953 seconds. Warn the user if lower values are given in the
20954 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
20955 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
20956 user if lower values are given in the configuration. Bugfix on
20957 0.1.1.17-rc. Patch by Sebastian.
20958 - Fix a race condition when freeing keys shared between main thread
20959 and CPU workers that could result in a memory leak. Bugfix on
20960 0.1.0.1-rc. Fixes bug 889.
20962 o Minor bugfixes (hidden services):
20963 - Do not throw away existing introduction points on SIGHUP (bugfix on
20964 0.0.6pre1); also, do not stall hidden services because we're
20965 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
20966 by John Brooks. Patch by Karsten. Fixes bug 874.
20967 - Fix a memory leak when we decline to add a v2 rendezvous
20968 descriptor to the cache because we already had a v0 descriptor
20969 with the same ID. Bugfix on 0.2.0.18-alpha.
20971 o Deprecated and removed features:
20972 - RedirectExits has been removed. It was deprecated since
20974 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
20975 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
20976 - Cell pools are now always enabled; --disable-cell-pools is ignored.
20978 o Code simplifications and refactoring:
20979 - Rename the confusing or_is_obsolete field to the more appropriate
20980 is_bad_for_new_circs, and move it to or_connection_t where it
20982 - Move edge-only flags from connection_t to edge_connection_t: not
20983 only is this better coding, but on machines of plausible alignment,
20984 it should save 4-8 bytes per connection_t. "Every little bit helps."
20985 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
20986 for consistency; keep old option working for backward compatibility.
20987 - Simplify the code for finding connections to use for a circuit.
20990 Changes in version 0.2.1.8-alpha - 2008-12-08
20991 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
20992 builds better on unusual platforms like Solaris and old OS X, and
20993 fixes a variety of other issues.
20996 - New DirPortFrontPage option that takes an html file and publishes
20997 it as "/" on the DirPort. Now relay operators can provide a
20998 disclaimer without needing to set up a separate webserver. There's
20999 a sample disclaimer in contrib/tor-exit-notice.html.
21002 - When the client is choosing entry guards, now it selects at most
21003 one guard from a given relay family. Otherwise we could end up with
21004 all of our entry points into the network run by the same operator.
21005 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
21008 - Fix a DOS opportunity during the voting signature collection process
21009 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
21010 - Fix a possible segfault when establishing an exit connection. Bugfix
21014 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
21016 - Made Tor a little less aggressive about deleting expired
21017 certificates. Partial fix for bug 854.
21018 - Stop doing unaligned memory access that generated bus errors on
21019 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
21020 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
21021 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
21022 - Make USR2 log-level switch take effect immediately. Bugfix on
21024 - If one win32 nameserver fails to get added, continue adding the
21025 rest, and don't automatically fail.
21026 - Use fcntl() for locking when flock() is not available. Should fix
21027 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
21028 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
21029 could make gcc generate non-functional binary search code. Bugfix
21031 - Build correctly on platforms without socklen_t.
21032 - Avoid potential crash on internal error during signature collection.
21033 Fixes bug 864. Patch from rovv.
21034 - Do not use C's stdio library for writing to log files. This will
21035 improve logging performance by a minute amount, and will stop
21036 leaking fds when our disk is full. Fixes bug 861.
21037 - Stop erroneous use of O_APPEND in cases where we did not in fact
21038 want to re-seek to the end of a file before every last write().
21039 - Correct handling of possible malformed authority signing key
21040 certificates with internal signature types. Fixes bug 880. Bugfix
21042 - Fix a hard-to-trigger resource leak when logging credential status.
21046 - Directory mirrors no longer fetch the v1 directory or
21047 running-routers files. They are obsolete, and nobody asks for them
21048 anymore. This is the first step to making v1 authorities obsolete.
21050 o Minor features (controller):
21051 - Return circuit purposes in response to GETINFO circuit-status. Fixes
21055 Changes in version 0.2.0.32 - 2008-11-20
21056 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
21057 packages (and maybe other packages) noticed by Theo de Raadt, fixes
21058 a smaller security flaw that might allow an attacker to access local
21059 services, further improves hidden service performance, and fixes a
21060 variety of other issues.
21063 - The "User" and "Group" config options did not clear the
21064 supplementary group entries for the Tor process. The "User" option
21065 is now more robust, and we now set the groups to the specified
21066 user's primary group. The "Group" option is now ignored. For more
21067 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
21068 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
21069 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
21070 - The "ClientDNSRejectInternalAddresses" config option wasn't being
21071 consistently obeyed: if an exit relay refuses a stream because its
21072 exit policy doesn't allow it, we would remember what IP address
21073 the relay said the destination address resolves to, even if it's
21074 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
21077 - Fix a DOS opportunity during the voting signature collection process
21078 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
21080 o Major bugfixes (hidden services):
21081 - When fetching v0 and v2 rendezvous service descriptors in parallel,
21082 we were failing the whole hidden service request when the v0
21083 descriptor fetch fails, even if the v2 fetch is still pending and
21084 might succeed. Similarly, if the last v2 fetch fails, we were
21085 failing the whole hidden service request even if a v0 fetch is
21086 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
21087 - When extending a circuit to a hidden service directory to upload a
21088 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
21089 requests failed, because the router descriptor has not been
21090 downloaded yet. In these cases, do not attempt to upload the
21091 rendezvous descriptor, but wait until the router descriptor is
21092 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
21093 descriptor from a hidden service directory for which the router
21094 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
21098 - Fix several infrequent memory leaks spotted by Coverity.
21099 - When testing for libevent functions, set the LDFLAGS variable
21100 correctly. Found by Riastradh.
21101 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
21102 bootstrapping with tunneled directory connections. Bugfix on
21103 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
21104 - When asked to connect to A.B.exit:80, if we don't know the IP for A
21105 and we know that server B rejects most-but-not all connections to
21106 port 80, we would previously reject the connection. Now, we assume
21107 the user knows what they were asking for. Fixes bug 752. Bugfix
21108 on 0.0.9rc5. Diagnosed by BarkerJr.
21109 - If we overrun our per-second write limits a little, count this as
21110 having used up our write allocation for the second, and choke
21111 outgoing directory writes. Previously, we had only counted this when
21112 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
21113 Bugfix on 0.2.0.x (??).
21114 - Remove the old v2 directory authority 'lefkada' from the default
21115 list. It has been gone for many months.
21116 - Stop doing unaligned memory access that generated bus errors on
21117 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
21118 - Make USR2 log-level switch take effect immediately. Bugfix on
21121 o Minor bugfixes (controller):
21122 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
21123 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
21126 Changes in version 0.2.1.7-alpha - 2008-11-08
21127 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
21128 packages (and maybe other packages) noticed by Theo de Raadt, fixes
21129 a smaller security flaw that might allow an attacker to access local
21130 services, adds better defense against DNS poisoning attacks on exit
21131 relays, further improves hidden service performance, and fixes a
21132 variety of other issues.
21135 - The "ClientDNSRejectInternalAddresses" config option wasn't being
21136 consistently obeyed: if an exit relay refuses a stream because its
21137 exit policy doesn't allow it, we would remember what IP address
21138 the relay said the destination address resolves to, even if it's
21139 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
21140 - The "User" and "Group" config options did not clear the
21141 supplementary group entries for the Tor process. The "User" option
21142 is now more robust, and we now set the groups to the specified
21143 user's primary group. The "Group" option is now ignored. For more
21144 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
21145 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
21146 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
21147 - Do not use or believe expired v3 authority certificates. Patch
21148 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
21151 - Now NodeFamily and MyFamily config options allow spaces in
21152 identity fingerprints, so it's easier to paste them in.
21153 Suggested by Lucky Green.
21154 - Implement the 0x20 hack to better resist DNS poisoning: set the
21155 case on outgoing DNS requests randomly, and reject responses that do
21156 not match the case correctly. This logic can be disabled with the
21157 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
21158 of servers that do not reliably preserve case in replies. See
21159 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
21161 - Preserve case in replies to DNSPort requests in order to support
21162 the 0x20 hack for resisting DNS poisoning attacks.
21164 o Hidden service performance improvements:
21165 - When the client launches an introduction circuit, retry with a
21166 new circuit after 30 seconds rather than 60 seconds.
21167 - Launch a second client-side introduction circuit in parallel
21168 after a delay of 15 seconds (based on work by Christian Wilms).
21169 - Hidden services start out building five intro circuits rather
21170 than three, and when the first three finish they publish a service
21171 descriptor using those. Now we publish our service descriptor much
21172 faster after restart.
21175 - Minor fix in the warning messages when you're having problems
21176 bootstrapping; also, be more forgiving of bootstrap problems when
21177 we're still making incremental progress on a given bootstrap phase.
21178 - When we're choosing an exit node for a circuit, and we have
21179 no pending streams, choose a good general exit rather than one that
21180 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
21181 - Send a valid END cell back when a client tries to connect to a
21182 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
21183 840. Patch from rovv.
21184 - If a broken client asks a non-exit router to connect somewhere,
21185 do not even do the DNS lookup before rejecting the connection.
21186 Fixes another case of bug 619. Patch from rovv.
21187 - Fix another case of assuming, when a specific exit is requested,
21188 that we know more than the user about what hosts it allows.
21189 Fixes another case of bug 752. Patch from rovv.
21190 - Check which hops rendezvous stream cells are associated with to
21191 prevent possible guess-the-streamid injection attacks from
21192 intermediate hops. Fixes another case of bug 446. Based on patch
21194 - Avoid using a negative right-shift when comparing 32-bit
21195 addresses. Possible fix for bug 845 and bug 811.
21196 - Make the assert_circuit_ok() function work correctly on circuits that
21197 have already been marked for close.
21198 - Fix read-off-the-end-of-string error in unit tests when decoding
21199 introduction points.
21200 - Fix uninitialized size field for memory area allocation: may improve
21201 memory performance during directory parsing.
21202 - Treat duplicate certificate fetches as failures, so that we do
21203 not try to re-fetch an expired certificate over and over and over.
21204 - Do not say we're fetching a certificate when we'll in fact skip it
21205 because of a pending download.
21208 Changes in version 0.2.1.6-alpha - 2008-09-30
21209 Tor 0.2.1.6-alpha further improves performance and robustness of
21210 hidden services, starts work on supporting per-country relay selection,
21211 and fixes a variety of smaller issues.
21214 - Implement proposal 121: make it possible to build hidden services
21215 that only certain clients are allowed to connect to. This is
21216 enforced at several points, so that unauthorized clients are unable
21217 to send INTRODUCE cells to the service, or even (depending on the
21218 type of authentication) to learn introduction points. This feature
21219 raises the bar for certain kinds of active attacks against hidden
21220 services. Code by Karsten Loesing.
21221 - Relays now store and serve v2 hidden service descriptors by default,
21222 i.e., the new default value for HidServDirectoryV2 is 1. This is
21223 the last step in proposal 114, which aims to make hidden service
21224 lookups more reliable.
21225 - Start work to allow node restrictions to include country codes. The
21226 syntax to exclude nodes in a country with country code XX is
21227 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
21228 refinement to decide what config options should take priority if
21229 you ask to both use a particular node and exclude it.
21230 - Allow ExitNodes list to include IP ranges and country codes, just
21231 like the Exclude*Nodes lists. Patch from Robert Hogan.
21234 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
21235 Tor to fail to start if you had it configured to use a bridge
21236 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
21237 - When extending a circuit to a hidden service directory to upload a
21238 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
21239 requests failed, because the router descriptor had not been
21240 downloaded yet. In these cases, we now wait until the router
21241 descriptor is downloaded, and then retry. Likewise, clients
21242 now skip over a hidden service directory if they don't yet have
21243 its router descriptor, rather than futilely requesting it and
21244 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
21246 - When fetching v0 and v2 rendezvous service descriptors in parallel,
21247 we were failing the whole hidden service request when the v0
21248 descriptor fetch fails, even if the v2 fetch is still pending and
21249 might succeed. Similarly, if the last v2 fetch fails, we were
21250 failing the whole hidden service request even if a v0 fetch is
21251 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
21252 - DNS replies need to have names matching their requests, but
21253 these names should be in the questions section, not necessarily
21254 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
21257 - Update to the "September 1 2008" ip-to-country file.
21258 - Allow ports 465 and 587 in the default exit policy again. We had
21259 rejected them in 0.1.0.15, because back in 2005 they were commonly
21260 misconfigured and ended up as spam targets. We hear they are better
21261 locked down these days.
21262 - Use a lockfile to make sure that two Tor processes are not
21263 simultaneously running with the same datadir.
21264 - Serve the latest v3 networkstatus consensus via the control
21265 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
21266 - Better logging about stability/reliability calculations on directory
21268 - Drop the requirement to have an open dir port for storing and
21269 serving v2 hidden service descriptors.
21270 - Directory authorities now serve a /tor/dbg-stability.txt URL to
21271 help debug WFU and MTBF calculations.
21272 - Implement most of Proposal 152: allow specialized servers to permit
21273 single-hop circuits, and clients to use those servers to build
21274 single-hop circuits when using a specialized controller. Patch
21275 from Josh Albrecht. Resolves feature request 768.
21276 - Add a -p option to tor-resolve for specifying the SOCKS port: some
21277 people find host:port too confusing.
21278 - Make TrackHostExit mappings expire a while after their last use, not
21279 after their creation. Patch from Robert Hogan.
21280 - Provide circuit purposes along with circuit events to the controller.
21283 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
21285 - Fixed some memory leaks -- some quite frequent, some almost
21286 impossible to trigger -- based on results from Coverity.
21287 - When testing for libevent functions, set the LDFLAGS variable
21288 correctly. Found by Riastradh.
21289 - Fix an assertion bug in parsing policy-related options; possible fix
21291 - Catch and report a few more bootstrapping failure cases when Tor
21292 fails to establish a TCP connection. Cleanup on 0.2.1.x.
21293 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
21294 bootstrapping with tunneled directory connections. Bugfix on
21295 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
21296 - When asked to connect to A.B.exit:80, if we don't know the IP for A
21297 and we know that server B rejects most-but-not all connections to
21298 port 80, we would previously reject the connection. Now, we assume
21299 the user knows what they were asking for. Fixes bug 752. Bugfix
21300 on 0.0.9rc5. Diagnosed by BarkerJr.
21301 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
21302 service directories if they have no advertised dir port. Bugfix
21304 - If we overrun our per-second write limits a little, count this as
21305 having used up our write allocation for the second, and choke
21306 outgoing directory writes. Previously, we had only counted this when
21307 we had met our limits precisely. Fixes bug 824. Patch by rovv.
21308 Bugfix on 0.2.0.x (??).
21309 - Avoid a "0 divided by 0" calculation when calculating router uptime
21310 at directory authorities. Bugfix on 0.2.0.8-alpha.
21311 - Make DNS resolved controller events into "CLOSED", not
21312 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
21314 - Fix a bug where an unreachable relay would establish enough
21315 reachability testing circuits to do a bandwidth test -- if
21316 we already have a connection to the middle hop of the testing
21317 circuit, then it could establish the last hop by using the existing
21318 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
21319 circuits no longer use entry guards in 0.2.1.3-alpha.
21320 - If we have correct permissions on $datadir, we complain to stdout
21321 and fail to start. But dangerous permissions on
21322 $datadir/cached-status/ would cause us to open a log and complain
21323 there. Now complain to stdout and fail to start in both cases. Fixes
21324 bug 820, reported by seeess.
21325 - Remove the old v2 directory authority 'lefkada' from the default
21326 list. It has been gone for many months.
21328 o Code simplifications and refactoring:
21329 - Revise the connection_new functions so that a more typesafe variant
21330 exists. This will work better with Coverity, and let us find any
21331 actual mistakes we're making here.
21332 - Refactor unit testing logic so that dmalloc can be used sensibly
21333 with unit tests to check for memory leaks.
21334 - Move all hidden-service related fields from connection and circuit
21335 structure to substructures: this way they won't eat so much memory.
21338 Changes in version 0.2.0.31 - 2008-09-03
21339 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
21340 a big bug we're seeing where in rare cases traffic from one Tor stream
21341 gets mixed into another stream, and fixes a variety of smaller issues.
21344 - Make sure that two circuits can never exist on the same connection
21345 with the same circuit ID, even if one is marked for close. This
21346 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
21347 - Relays now reject risky extend cells: if the extend cell includes
21348 a digest of all zeroes, or asks to extend back to the relay that
21349 sent the extend cell, tear down the circuit. Ideas suggested
21351 - If not enough of our entry guards are available so we add a new
21352 one, we might use the new one even if it overlapped with the
21353 current circuit's exit relay (or its family). Anonymity bugfix
21354 pointed out by rovv.
21357 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
21358 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
21359 - Correctly detect the presence of the linux/netfilter_ipv4.h header
21360 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
21361 - Pick size of default geoip filename string correctly on windows.
21362 Fixes bug 806. Bugfix on 0.2.0.30.
21363 - Make the autoconf script accept the obsolete --with-ssl-dir
21364 option as an alias for the actually-working --with-openssl-dir
21365 option. Fix the help documentation to recommend --with-openssl-dir.
21366 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
21367 - When using the TransPort option on OpenBSD, and using the User
21368 option to change UID and drop privileges, make sure to open
21369 /dev/pf before dropping privileges. Fixes bug 782. Patch from
21370 Christopher Davis. Bugfix on 0.1.2.1-alpha.
21371 - Try to attach connections immediately upon receiving a RENDEZVOUS2
21372 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
21373 on the client side when connecting to a hidden service. Bugfix
21374 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
21375 - When closing an application-side connection because its circuit is
21376 getting torn down, generate the stream event correctly. Bugfix on
21377 0.1.2.x. Anonymous patch.
21380 Changes in version 0.2.1.5-alpha - 2008-08-31
21381 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
21382 in a lot of the infrastructure for adding authorization to hidden
21383 services, lays the groundwork for having clients read their load
21384 balancing information out of the networkstatus consensus rather than
21385 the individual router descriptors, addresses two potential anonymity
21386 issues, and fixes a variety of smaller issues.
21389 - Convert many internal address representations to optionally hold
21391 - Generate and accept IPv6 addresses in many protocol elements.
21392 - Make resolver code handle nameservers located at ipv6 addresses.
21393 - Begin implementation of proposal 121 ("Client authorization for
21394 hidden services"): configure hidden services with client
21395 authorization, publish descriptors for them, and configure
21396 authorization data for hidden services at clients. The next
21397 step is to actually access hidden services that perform client
21399 - More progress toward proposal 141: Network status consensus
21400 documents and votes now contain bandwidth information for each
21401 router and a summary of that router's exit policy. Eventually this
21402 will be used by clients so that they do not have to download every
21403 known descriptor before building circuits.
21405 o Major bugfixes (on 0.2.0.x and before):
21406 - When sending CREATED cells back for a given circuit, use a 64-bit
21407 connection ID to find the right connection, rather than an addr:port
21408 combination. Now that we can have multiple OR connections between
21409 the same ORs, it is no longer possible to use addr:port to uniquely
21410 identify a connection.
21411 - Relays now reject risky extend cells: if the extend cell includes
21412 a digest of all zeroes, or asks to extend back to the relay that
21413 sent the extend cell, tear down the circuit. Ideas suggested
21415 - If not enough of our entry guards are available so we add a new
21416 one, we might use the new one even if it overlapped with the
21417 current circuit's exit relay (or its family). Anonymity bugfix
21418 pointed out by rovv.
21421 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
21422 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
21423 - When using the TransPort option on OpenBSD, and using the User
21424 option to change UID and drop privileges, make sure to open /dev/pf
21425 before dropping privileges. Fixes bug 782. Patch from Christopher
21426 Davis. Bugfix on 0.1.2.1-alpha.
21427 - Correctly detect the presence of the linux/netfilter_ipv4.h header
21428 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
21429 - Add a missing safe_str() call for a debug log message.
21430 - Use 64 bits instead of 32 bits for connection identifiers used with
21431 the controller protocol, to greatly reduce risk of identifier reuse.
21432 - Make the autoconf script accept the obsolete --with-ssl-dir
21433 option as an alias for the actually-working --with-openssl-dir
21434 option. Fix the help documentation to recommend --with-openssl-dir.
21435 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
21438 - Rate-limit too-many-sockets messages: when they happen, they happen
21439 a lot. Resolves bug 748.
21440 - Resist DNS poisoning a little better by making sure that names in
21441 answer sections match.
21442 - Print the SOCKS5 error message string as well as the error code
21443 when a tor-resolve request fails. Patch from Jacob.
21446 Changes in version 0.2.1.4-alpha - 2008-08-04
21447 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
21450 - The address part of exit policies was not correctly written
21451 to router descriptors. This generated router descriptors that failed
21452 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
21454 - Tor triggered a false assert when extending a circuit to a relay
21455 but we already have a connection open to that relay. Noticed by
21456 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
21459 - Fix a hidden service logging bug: in some edge cases, the router
21460 descriptor of a previously picked introduction point becomes
21461 obsolete and we need to give up on it rather than continually
21462 complaining that it has become obsolete. Observed by xiando. Bugfix
21465 o Removed features:
21466 - Take out the TestVia config option, since it was a workaround for
21467 a bug that was fixed in Tor 0.1.1.21.
21470 Changes in version 0.2.1.3-alpha - 2008-08-03
21471 Tor 0.2.1.3-alpha implements most of the pieces to prevent
21472 infinite-length circuit attacks (see proposal 110); fixes a bug that
21473 might cause exit relays to corrupt streams they send back; allows
21474 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
21475 ExcludeExitNodes config options; and fixes a big pile of bugs.
21477 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
21478 - Send a bootstrap problem "warn" event on the first problem if the
21479 reason is NO_ROUTE (that is, our network is down).
21482 - Implement most of proposal 110: The first K cells to be sent
21483 along a circuit are marked as special "early" cells; only K "early"
21484 cells will be allowed. Once this code is universal, we can block
21485 certain kinds of DOS attack by requiring that EXTEND commands must
21486 be sent using an "early" cell.
21489 - Try to attach connections immediately upon receiving a RENDEZVOUS2
21490 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
21491 on the client side when connecting to a hidden service. Bugfix
21492 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
21493 - Ensure that two circuits can never exist on the same connection
21494 with the same circuit ID, even if one is marked for close. This
21495 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
21498 - When relays do their initial bandwidth measurement, don't limit
21499 to just our entry guards for the test circuits. Otherwise we tend
21500 to have multiple test circuits going through a single entry guard,
21501 which makes our bandwidth test less accurate. Fixes part of bug 654;
21502 patch contributed by Josh Albrecht.
21503 - Add an ExcludeExitNodes option so users can list a set of nodes
21504 that should be be excluded from the exit node position, but
21505 allowed elsewhere. Implements proposal 151.
21506 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
21507 ExcludeNodes and ExcludeExitNodes lists.
21508 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
21509 be more efficient. Formerly it was quadratic in the number of
21510 servers; now it should be linear. Fixes bug 509.
21511 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
21512 and n_conn_id_digest fields into a separate structure that's
21513 only needed when the circuit has not yet attached to an n_conn.
21516 - Change the contrib/tor.logrotate script so it makes the new
21517 logs as "_tor:_tor" rather than the default, which is generally
21518 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
21519 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
21520 warnings (occasionally), but it can also cause the compiler to
21521 eliminate error-checking code. Suggested by Peter Gutmann.
21522 - When a hidden service is giving up on an introduction point candidate
21523 that was not included in the last published rendezvous descriptor,
21524 don't reschedule publication of the next descriptor. Fixes bug 763.
21526 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
21527 HiddenServiceExcludeNodes as obsolete: they never worked properly,
21528 and nobody claims to be using them. Fixes bug 754. Bugfix on
21529 0.1.0.1-rc. Patch from Christian Wilms.
21530 - Fix a small alignment and memory-wasting bug on buffer chunks.
21533 o Minor bugfixes (controller):
21534 - When closing an application-side connection because its circuit
21535 is getting torn down, generate the stream event correctly.
21536 Bugfix on 0.1.2.x. Anonymous patch.
21538 o Removed features:
21539 - Remove all backward-compatibility code to support relays running
21540 versions of Tor so old that they no longer work at all on the
21544 Changes in version 0.2.0.30 - 2008-07-15
21546 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
21547 warnings (occasionally), but it can also cause the compiler to
21548 eliminate error-checking code. Suggested by Peter Gutmann.
21551 Changes in version 0.2.0.29-rc - 2008-07-08
21552 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
21553 hidden-service performance bugs, and fixes a bunch of smaller bugs.
21556 - If you have more than one bridge but don't know their keys,
21557 you would only launch a request for the descriptor of the first one
21558 on your list. (Tor considered launching requests for the others, but
21559 found that it already had a connection on the way for $0000...0000
21560 so it didn't open another.) Bugfix on 0.2.0.x.
21561 - If you have more than one bridge but don't know their keys, and the
21562 connection to one of the bridges failed, you would cancel all
21563 pending bridge connections. (After all, they all have the same
21564 digest.) Bugfix on 0.2.0.x.
21565 - When a hidden service was trying to establish an introduction point,
21566 and Tor had built circuits preemptively for such purposes, we
21567 were ignoring all the preemptive circuits and launching a new one
21568 instead. Bugfix on 0.2.0.14-alpha.
21569 - When a hidden service was trying to establish an introduction point,
21570 and Tor *did* manage to reuse one of the preemptively built
21571 circuits, it didn't correctly remember which one it used,
21572 so it asked for another one soon after, until there were no
21573 more preemptive circuits, at which point it launched one from
21574 scratch. Bugfix on 0.0.9.x.
21575 - Make directory servers include the X-Your-Address-Is: http header in
21576 their responses even for begin_dir conns. Now clients who only
21577 ever use begin_dir connections still have a way to learn their IP
21578 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
21581 - Fix a macro/CPP interaction that was confusing some compilers:
21582 some GCCs don't like #if/#endif pairs inside macro arguments.
21584 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
21585 Fixes bug 704; fix from Steven Murdoch.
21586 - When opening /dev/null in finish_daemonize(), do not pass the
21587 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
21588 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
21589 - Correctly detect transparent proxy support on Linux hosts that
21590 require in.h to be included before netfilter_ipv4.h. Patch
21592 - Disallow session resumption attempts during the renegotiation
21593 stage of the v2 handshake protocol. Clients should never be trying
21594 session resumption at this point, but apparently some did, in
21595 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
21596 found by Geoff Goodell.
21599 Changes in version 0.2.1.2-alpha - 2008-06-20
21600 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
21601 make it easier to set up your own private Tor network; fixes several
21602 big bugs with using more than one bridge relay; fixes a big bug with
21603 offering hidden services quickly after Tor starts; and uses a better
21604 API for reporting potential bootstrapping problems to the controller.
21607 - New TestingTorNetwork config option to allow adjustment of
21608 previously constant values that, while reasonable, could slow
21609 bootstrapping. Implements proposal 135. Patch from Karsten.
21612 - If you have more than one bridge but don't know their digests,
21613 you would only learn a request for the descriptor of the first one
21614 on your list. (Tor considered launching requests for the others, but
21615 found that it already had a connection on the way for $0000...0000
21616 so it didn't open another.) Bugfix on 0.2.0.x.
21617 - If you have more than one bridge but don't know their digests,
21618 and the connection to one of the bridges failed, you would cancel
21619 all pending bridge connections. (After all, they all have the
21620 same digest.) Bugfix on 0.2.0.x.
21621 - When establishing a hidden service, introduction points that
21622 originate from cannibalized circuits are completely ignored and not
21623 included in rendezvous service descriptors. This might be another
21624 reason for delay in making a hidden service available. Bugfix
21625 from long ago (0.0.9.x?)
21628 - Allow OpenSSL to use dynamic locks if it wants.
21629 - When building a consensus, do not include routers that are down.
21630 This will cut down 30% to 40% on consensus size. Implements
21632 - In directory authorities' approved-routers files, allow
21633 fingerprints with or without space.
21634 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
21635 controller can query our current bootstrap state in case it attaches
21636 partway through and wants to catch up.
21637 - Send an initial "Starting" bootstrap status event, so we have a
21638 state to start out in.
21641 - Asking for a conditional consensus at .../consensus/<fingerprints>
21642 would crash a dirserver if it did not already have a
21643 consensus. Bugfix on 0.2.1.1-alpha.
21644 - Clean up some macro/CPP interactions: some GCC versions don't like
21645 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
21648 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
21649 - Directory authorities shouldn't complain about bootstrapping
21650 problems just because they do a lot of reachability testing and
21651 some of the connection attempts fail.
21652 - Start sending "count" and "recommendation" key/value pairs in
21653 bootstrap problem status events, so the controller can hear about
21654 problems even before Tor decides they're worth reporting for sure.
21655 - If you're using bridges, generate "bootstrap problem" warnings
21656 as soon as you run out of working bridges, rather than waiting
21657 for ten failures -- which will never happen if you have less than
21659 - If we close our OR connection because there's been a circuit
21660 pending on it for too long, we were telling our bootstrap status
21661 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
21664 Changes in version 0.2.1.1-alpha - 2008-06-13
21665 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
21666 were making the Tor process bloat especially on Linux; makes our TLS
21667 handshake blend in better; sends "bootstrap phase" status events to
21668 the controller, so it can keep the user informed of progress (and
21669 problems) fetching directory information and establishing circuits;
21670 and adds a variety of smaller features.
21673 - More work on making our TLS handshake blend in: modify the list
21674 of ciphers advertised by OpenSSL in client mode to even more
21675 closely resemble a common web browser. We cheat a little so that
21676 we can advertise ciphers that the locally installed OpenSSL doesn't
21678 - Start sending "bootstrap phase" status events to the controller,
21679 so it can keep the user informed of progress fetching directory
21680 information and establishing circuits. Also inform the controller
21681 if we think we're stuck at a particular bootstrap phase. Implements
21683 - Resume using OpenSSL's RAND_poll() for better (and more portable)
21684 cross-platform entropy collection again. We used to use it, then
21685 stopped using it because of a bug that could crash systems that
21686 called RAND_poll when they had a lot of fds open. It looks like the
21687 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
21688 at startup, and to call RAND_poll() when we reseed later only if
21689 we have a non-buggy OpenSSL version.
21692 - When we choose to abandon a new entry guard because we think our
21693 older ones might be better, close any circuits pending on that
21694 new entry guard connection. This fix should make us recover much
21695 faster when our network is down and then comes back. Bugfix on
21696 0.1.2.8-beta; found by lodger.
21698 o Memory fixes and improvements:
21699 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
21700 to avoid unused RAM in buffer chunks and memory pools.
21701 - Speed up parsing and cut down on memory fragmentation by using
21702 stack-style allocations for parsing directory objects. Previously,
21703 this accounted for over 40% of allocations from within Tor's code
21704 on a typical directory cache.
21705 - Use a Bloom filter rather than a digest-based set to track which
21706 descriptors we need to keep around when we're cleaning out old
21707 router descriptors. This speeds up the computation significantly,
21708 and may reduce fragmentation.
21709 - Reduce the default smartlist size from 32 to 16; it turns out that
21710 most smartlists hold around 8-12 elements tops.
21711 - Make dumpstats() log the fullness and size of openssl-internal
21713 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
21714 patch to their OpenSSL, turn it on to save memory on servers. This
21715 patch will (with any luck) get included in a mainline distribution
21717 - Never use OpenSSL compression: it wastes RAM and CPU trying to
21718 compress cells, which are basically all encrypted, compressed,
21722 - Stop reloading the router list from disk for no reason when we
21723 run out of reachable directory mirrors. Once upon a time reloading
21724 it would set the 'is_running' flag back to 1 for them. It hasn't
21725 done that for a long time.
21726 - In very rare situations new hidden service descriptors were
21727 published earlier than 30 seconds after the last change to the
21728 service. (We currently think that a hidden service descriptor
21729 that's been stable for 30 seconds is worth publishing.)
21732 - Allow separate log levels to be configured for different logging
21733 domains. For example, this allows one to log all notices, warnings,
21734 or errors, plus all memory management messages of level debug or
21735 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
21736 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
21737 and stop using a warning that had become unfixably verbose under
21739 - New --hush command-line option similar to --quiet. While --quiet
21740 disables all logging to the console on startup, --hush limits the
21741 output to messages of warning and error severity.
21742 - Servers support a new URL scheme for consensus downloads that
21743 allows the client to specify which authorities are trusted.
21744 The server then only sends the consensus if the client will trust
21745 it. Otherwise a 404 error is sent back. Clients use this
21746 new scheme when the server supports it (meaning it's running
21747 0.2.1.1-alpha or later). Implements proposal 134.
21748 - New configure/torrc options (--enable-geoip-stats,
21749 DirRecordUsageByCountry) to record how many IPs we've served
21750 directory info to in each country code, how many status documents
21751 total we've sent to each country code, and what share of the total
21752 directory requests we should expect to see.
21753 - Use the TLS1 hostname extension to more closely resemble browser
21755 - Lots of new unit tests.
21756 - Add a macro to implement the common pattern of iterating through
21757 two parallel lists in lockstep.
21760 Changes in version 0.2.0.28-rc - 2008-06-13
21761 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
21762 performance bug, and fixes a bunch of smaller bugs.
21765 - Fix a bug where, when we were choosing the 'end stream reason' to
21766 put in our relay end cell that we send to the exit relay, Tor
21767 clients on Windows were sometimes sending the wrong 'reason'. The
21768 anonymity problem is that exit relays may be able to guess whether
21769 the client is running Windows, thus helping partition the anonymity
21770 set. Down the road we should stop sending reasons to exit relays,
21771 or otherwise prevent future versions of this bug.
21774 - While setting up a hidden service, some valid introduction circuits
21775 were overlooked and abandoned. This might be the reason for
21776 the long delay in making a hidden service available. Bugfix on
21780 - Update to the "June 9 2008" ip-to-country file.
21781 - Run 'make test' as part of 'make dist', so we stop releasing so
21782 many development snapshots that fail their unit tests.
21785 - When we're checking if we have enough dir info for each relay
21786 to begin establishing circuits, make sure that we actually have
21787 the descriptor listed in the consensus, not just any descriptor.
21789 - Bridge relays no longer print "xx=0" in their extrainfo document
21790 for every single country code in the geoip db. Bugfix on
21792 - Only warn when we fail to load the geoip file if we were planning to
21793 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
21794 - If we change our MaxAdvertisedBandwidth and then reload torrc,
21795 Tor won't realize it should publish a new relay descriptor. Fixes
21796 bug 688, reported by mfr. Bugfix on 0.1.2.x.
21797 - When we haven't had any application requests lately, don't bother
21798 logging that we have expired a bunch of descriptors. Bugfix
21800 - Make relay cells written on a connection count as non-padding when
21801 tracking how long a connection has been in use. Bugfix on
21802 0.2.0.1-alpha. Spotted by lodger.
21803 - Fix unit tests in 0.2.0.27-rc.
21804 - Fix compile on Windows.
21807 Changes in version 0.2.0.27-rc - 2008-06-03
21808 Tor 0.2.0.27-rc adds a few features we left out of the earlier
21809 release candidates. In particular, we now include an IP-to-country
21810 GeoIP database, so controllers can easily look up what country a
21811 given relay is in, and so bridge relays can give us some sanitized
21812 summaries about which countries are making use of bridges. (See proposal
21813 126-geoip-fetching.txt for details.)
21816 - Include an IP-to-country GeoIP file in the tarball, so bridge
21817 relays can report sanitized summaries of the usage they're seeing.
21820 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
21821 Robert Hogan. Fixes the first part of bug 681.
21822 - Make bridge authorities never serve extrainfo docs.
21823 - Add support to detect Libevent versions in the 1.4.x series
21825 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
21826 - Include a new contrib/tor-exit-notice.html file that exit relay
21827 operators can put on their website to help reduce abuse queries.
21830 - When tunneling an encrypted directory connection, and its first
21831 circuit fails, do not leave it unattached and ask the controller
21832 to deal. Fixes the second part of bug 681.
21833 - Make bridge authorities correctly expire old extrainfo documents
21837 Changes in version 0.2.0.26-rc - 2008-05-13
21838 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
21839 in Debian's OpenSSL packages. All users running any 0.2.0.x version
21840 should upgrade, whether they're running Debian or not.
21842 o Major security fixes:
21843 - Use new V3 directory authority keys on the tor26, gabelmoo, and
21844 moria1 V3 directory authorities. The old keys were generated with
21845 a vulnerable version of Debian's OpenSSL package, and must be
21846 considered compromised. Other authorities' keys were not generated
21847 with an affected version of OpenSSL.
21850 - List authority signatures as "unrecognized" based on DirServer
21851 lines, not on cert cache. Bugfix on 0.2.0.x.
21854 - Add a new V3AuthUseLegacyKey option to make it easier for
21855 authorities to change their identity keys if they have to.
21858 Changes in version 0.2.0.25-rc - 2008-04-23
21859 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
21862 - Remember to initialize threading before initializing logging.
21863 Otherwise, many BSD-family implementations will crash hard on
21864 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
21867 - Authorities correctly free policies on bad servers on
21868 exit. Fixes bug 672. Bugfix on 0.2.0.x.
21871 Changes in version 0.2.0.24-rc - 2008-04-22
21872 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
21873 v3 directory authority, makes relays with dynamic IP addresses and no
21874 DirPort notice more quickly when their IP address changes, fixes a few
21875 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
21877 o New directory authorities:
21878 - Take lefkada out of the list of v3 directory authorities, since
21879 it has been down for months.
21880 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
21884 - Detect address changes more quickly on non-directory mirror
21885 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
21887 o Minor features (security):
21888 - Reject requests for reverse-dns lookup of names that are in
21889 a private address space. Patch from lodger.
21890 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
21893 o Minor bugfixes (crashes):
21894 - Avoid a rare assert that can trigger when Tor doesn't have much
21895 directory information yet and it tries to fetch a v2 hidden
21896 service descriptor. Fixes bug 651, reported by nwf.
21897 - Initialize log mutex before initializing dmalloc. Otherwise,
21898 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
21899 - Use recursive pthread mutexes in order to avoid deadlock when
21900 logging debug-level messages to a controller. Bug spotted by nwf,
21901 bugfix on 0.2.0.16-alpha.
21903 o Minor bugfixes (resource management):
21904 - Keep address policies from leaking memory: start their refcount
21905 at 1, not 2. Bugfix on 0.2.0.16-alpha.
21906 - Free authority certificates on exit, so they don't look like memory
21907 leaks. Bugfix on 0.2.0.19-alpha.
21908 - Free static hashtables for policy maps and for TLS connections on
21909 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
21910 - Avoid allocating extra space when computing consensuses on 64-bit
21911 platforms. Bug spotted by aakova.
21913 o Minor bugfixes (misc):
21914 - Do not read the configuration file when we've only been told to
21915 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
21916 based on patch from Sebastian Hahn.
21917 - Exit relays that are used as a client can now reach themselves
21918 using the .exit notation, rather than just launching an infinite
21919 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
21920 - When attempting to open a logfile fails, tell us why.
21921 - Fix a dumb bug that was preventing us from knowing that we should
21922 preemptively build circuits to handle expected directory requests.
21923 Fixes bug 660. Bugfix on 0.1.2.x.
21924 - Warn less verbosely about clock skew from netinfo cells from
21925 untrusted sources. Fixes bug 663.
21926 - Make controller stream events for DNS requests more consistent,
21927 by adding "new stream" events for DNS requests, and removing
21928 spurious "stream closed" events" for cached reverse resolves.
21929 Patch from mwenge. Fixes bug 646.
21930 - Correctly notify one-hop connections when a circuit build has
21931 failed. Possible fix for bug 669. Found by lodger.
21934 Changes in version 0.2.0.23-rc - 2008-03-24
21935 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
21936 makes bootstrapping faster if the first directory mirror you contact
21937 is down. The bundles also include the new Vidalia 0.1.2 release.
21940 - When a tunneled directory request is made to a directory server
21941 that's down, notice after 30 seconds rather than 120 seconds. Also,
21942 fail any begindir streams that are pending on it, so they can
21943 retry elsewhere. This was causing multi-minute delays on bootstrap.
21946 Changes in version 0.2.0.22-rc - 2008-03-18
21947 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
21948 enables encrypted directory connections by default for non-relays, fixes
21949 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
21950 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
21953 - Enable encrypted directory connections by default for non-relays,
21954 so censor tools that block Tor directory connections based on their
21955 plaintext patterns will no longer work. This means Tor works in
21956 certain censored countries by default again.
21959 - Make sure servers always request certificates from clients during
21960 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
21961 - Do not enter a CPU-eating loop when a connection is closed in
21962 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
21963 diagnosed by lodger; bugfix on 0.2.0.20-rc.
21964 - Fix assertion failure that could occur when a blocked circuit
21965 became unblocked, and it had pending client DNS requests. Bugfix
21966 on 0.2.0.1-alpha. Fixes bug 632.
21968 o Minor bugfixes (on 0.1.2.x):
21969 - Generate "STATUS_SERVER" events rather than misspelled
21970 "STATUS_SEVER" events. Caught by mwenge.
21971 - When counting the number of bytes written on a TLS connection,
21972 look at the BIO actually used for writing to the network, not
21973 at the BIO used (sometimes) to buffer data for the network.
21974 Looking at different BIOs could result in write counts on the
21975 order of ULONG_MAX. Fixes bug 614.
21976 - On Windows, correctly detect errors when listing the contents of
21977 a directory. Fix from lodger.
21979 o Minor bugfixes (on 0.2.0.x):
21980 - Downgrade "sslv3 alert handshake failure" message to INFO.
21981 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
21982 left BandwidthRate and BandwidthBurst at the default, we would be
21983 silently limited by those defaults. Now raise them to match the
21984 RelayBandwidth* values.
21985 - Fix the SVK version detection logic to work correctly on a branch.
21986 - Make --enable-openbsd-malloc work correctly on Linux with alpha
21987 CPUs. Fixes bug 625.
21988 - Logging functions now check that the passed severity is sane.
21989 - Use proper log levels in the testsuite call of
21990 get_interface_address6().
21991 - When using a nonstandard malloc, do not use the platform values for
21992 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
21993 - Make the openbsd malloc code use 8k pages on alpha CPUs and
21995 - Detect mismatched page sizes when using --enable-openbsd-malloc.
21996 - Avoid double-marked-for-close warning when certain kinds of invalid
21997 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
21998 for bug 617. Bugfix on 0.2.0.1-alpha.
21999 - Make sure that the "NULL-means-reject *:*" convention is followed by
22000 all the policy manipulation functions, avoiding some possible crash
22001 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
22002 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
22003 actually works, and doesn't warn about every single reverse lookup.
22004 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
22007 - Only log guard node status when guard node status has changed.
22008 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
22009 make "INFO" 75% less verbose.
22012 Changes in version 0.2.0.21-rc - 2008-03-02
22013 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
22014 makes Tor work well with Vidalia again, fixes a rare assert bug,
22015 and fixes a pair of more minor bugs. The bundles also include Vidalia
22016 0.1.0 and Torbutton 1.1.16.
22019 - The control port should declare that it requires password auth
22020 when HashedControlSessionPassword is set too. Patch from Matt Edman;
22021 bugfix on 0.2.0.20-rc. Fixes bug 615.
22022 - Downgrade assert in connection_buckets_decrement() to a log message.
22023 This may help us solve bug 614, and in any case will make its
22024 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
22025 - We were sometimes miscounting the number of bytes read from the
22026 network, causing our rate limiting to not be followed exactly.
22027 Bugfix on 0.2.0.16-alpha. Reported by lodger.
22030 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
22031 OpenSSL versions should have been working fine. Diagnosis and patch
22032 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
22033 Bugfix on 0.2.0.20-rc.
22036 Changes in version 0.2.0.20-rc - 2008-02-24
22037 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
22038 makes more progress towards normalizing Tor's TLS handshake, makes
22039 hidden services work better again, helps relays bootstrap if they don't
22040 know their IP address, adds optional support for linking in openbsd's
22041 allocator or tcmalloc, allows really fast relays to scale past 15000
22042 sockets, and fixes a bunch of minor bugs reported by Veracode.
22045 - Enable the revised TLS handshake based on the one designed by
22046 Steven Murdoch in proposal 124, as revised in proposal 130. It
22047 includes version negotiation for OR connections as described in
22048 proposal 105. The new handshake is meant to be harder for censors
22049 to fingerprint, and it adds the ability to detect certain kinds of
22050 man-in-the-middle traffic analysis attacks. The version negotiation
22051 feature will allow us to improve Tor's link protocol more safely
22053 - Choose which bridge to use proportional to its advertised bandwidth,
22054 rather than uniformly at random. This should speed up Tor for
22055 bridge users. Also do this for people who set StrictEntryNodes.
22056 - When a TrackHostExits-chosen exit fails too many times in a row,
22057 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
22060 - Resolved problems with (re-)fetching hidden service descriptors.
22061 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
22062 and 0.2.0.19-alpha.
22063 - If we only ever used Tor for hidden service lookups or posts, we
22064 would stop building circuits and start refusing connections after
22065 24 hours, since we falsely believed that Tor was dormant. Reported
22066 by nwf; bugfix on 0.1.2.x.
22067 - Servers that don't know their own IP address should go to the
22068 authorities for their first directory fetch, even if their DirPort
22069 is off or if they don't know they're reachable yet. This will help
22070 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
22071 - When counting the number of open sockets, count not only the number
22072 of sockets we have received from the socket() call, but also
22073 the number we've gotten from accept() and socketpair(). This bug
22074 made us fail to count all sockets that we were using for incoming
22075 connections. Bugfix on 0.2.0.x.
22076 - Fix code used to find strings within buffers, when those strings
22077 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
22078 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
22079 - Add a new __HashedControlSessionPassword option for controllers
22080 to use for one-off session password hashes that shouldn't get
22081 saved to disk by SAVECONF --- Vidalia users were accumulating a
22082 pile of HashedControlPassword lines in their torrc files, one for
22083 each time they had restarted Tor and then clicked Save. Make Tor
22084 automatically convert "HashedControlPassword" to this new option but
22085 only when it's given on the command line. Partial fix for bug 586.
22087 o Minor features (performance):
22088 - Tune parameters for cell pool allocation to minimize amount of
22090 - Add OpenBSD malloc code from phk as an optional malloc
22091 replacement on Linux: some glibc libraries do very poorly
22092 with Tor's memory allocation patterns. Pass
22093 --enable-openbsd-malloc to get the replacement malloc code.
22094 - Add a --with-tcmalloc option to the configure script to link
22095 against tcmalloc (if present). Does not yet search for
22096 non-system include paths.
22097 - Stop imposing an arbitrary maximum on the number of file descriptors
22098 used for busy servers. Bug reported by Olaf Selke; patch from
22101 o Minor features (other):
22102 - When SafeLogging is disabled, log addresses along with all TLS
22104 - When building with --enable-gcc-warnings, check for whether Apple's
22105 warning "-Wshorten-64-to-32" is available.
22106 - Add a --passphrase-fd argument to the tor-gencert command for
22109 o Minor bugfixes (memory leaks and code problems):
22110 - We were leaking a file descriptor if Tor started with a zero-length
22111 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
22112 - Detect size overflow in zlib code. Reported by Justin Ferguson and
22114 - We were comparing the raw BridgePassword entry with a base64'ed
22115 version of it, when handling a "/tor/networkstatus-bridges"
22116 directory request. Now compare correctly. Noticed by Veracode.
22117 - Recover from bad tracked-since value in MTBF-history file.
22118 Should fix bug 537.
22119 - Alter the code that tries to recover from unhandled write
22120 errors, to not try to flush onto a socket that's given us
22121 unhandled errors. Bugfix on 0.1.2.x.
22122 - Make Unix controlsockets work correctly on OpenBSD. Patch from
22123 tup. Bugfix on 0.2.0.3-alpha.
22125 o Minor bugfixes (other):
22126 - If we have an extra-info document for our server, always make
22127 it available on the control port, even if we haven't gotten
22128 a copy of it from an authority yet. Patch from mwenge.
22129 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
22130 - Directory mirrors no longer include a guess at the client's IP
22131 address if the connection appears to be coming from the same /24
22132 network; it was producing too many wrong guesses.
22133 - Make the new hidden service code respect the SafeLogging setting.
22134 Bugfix on 0.2.0.x. Patch from Karsten.
22135 - When starting as an authority, do not overwrite all certificates
22136 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
22137 - If we're trying to flush the last bytes on a connection (for
22138 example, when answering a directory request), reset the
22139 time-to-give-up timeout every time we manage to write something
22140 on the socket. Bugfix on 0.1.2.x.
22141 - Change the behavior of "getinfo status/good-server-descriptor"
22142 so it doesn't return failure when any authority disappears.
22143 - Even though the man page said that "TrackHostExits ." should
22144 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
22145 - Report TLS "zero return" case as a "clean close" and "IO error"
22146 as a "close". Stop calling closes "unexpected closes": existing
22147 Tors don't use SSL_close(), so having a connection close without
22148 the TLS shutdown handshake is hardly unexpected.
22149 - Send NAMESERVER_STATUS messages for a single failed nameserver
22152 o Code simplifications and refactoring:
22153 - Remove the tor_strpartition function: its logic was confused,
22154 and it was only used for one thing that could be implemented far
22158 Changes in version 0.2.0.19-alpha - 2008-02-09
22159 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
22160 handshake, makes path selection for relays more secure and IP address
22161 guessing more robust, and generally fixes a lot of bugs in preparation
22162 for calling the 0.2.0 branch stable.
22165 - Do not include recognizeable strings in the commonname part of
22166 Tor's x509 certificates.
22169 - If we're a relay, avoid picking ourselves as an introduction point,
22170 a rendezvous point, or as the final hop for internal circuits. Bug
22171 reported by taranis and lodger. Bugfix on 0.1.2.x.
22172 - Patch from "Andrew S. Lists" to catch when we contact a directory
22173 mirror at IP address X and he says we look like we're coming from
22174 IP address X. Bugfix on 0.1.2.x.
22176 o Minor features (security):
22177 - Be more paranoid about overwriting sensitive memory on free(),
22178 as a defensive programming tactic to ensure forward secrecy.
22180 o Minor features (directory authority):
22181 - Actually validate the options passed to AuthDirReject,
22182 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
22183 - Reject router descriptors with out-of-range bandwidthcapacity or
22184 bandwidthburst values.
22186 o Minor features (controller):
22187 - Reject controller commands over 1MB in length. This keeps rogue
22188 processes from running us out of memory.
22190 o Minor features (misc):
22191 - Give more descriptive well-formedness errors for out-of-range
22192 hidden service descriptor/protocol versions.
22193 - Make memory debugging information describe more about history
22194 of cell allocation, so we can help reduce our memory use.
22196 o Deprecated features (controller):
22197 - The status/version/num-versioning and status/version/num-concurring
22198 GETINFO options are no longer useful in the v3 directory protocol:
22199 treat them as deprecated, and warn when they're used.
22202 - When our consensus networkstatus has been expired for a while, stop
22203 being willing to build circuits using it. Fixes bug 401. Bugfix
22205 - Directory caches now fetch certificates from all authorities
22206 listed in a networkstatus consensus, even when they do not
22207 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
22208 - When connecting to a bridge without specifying its key, insert
22209 the connection into the identity-to-connection map as soon as
22210 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
22211 - Detect versions of OS X where malloc_good_size() is present in the
22212 library but never actually declared. Resolves bug 587. Bugfix
22214 - Stop incorrectly truncating zlib responses to directory authority
22215 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
22216 - Stop recommending that every server operator send mail to tor-ops.
22217 Resolves bug 597. Bugfix on 0.1.2.x.
22218 - Don't trigger an assert if we start a directory authority with a
22219 private IP address (like 127.0.0.1).
22220 - Avoid possible failures when generating a directory with routers
22221 with over-long versions strings, or too many flags set. Bugfix
22223 - If an attempt to launch a DNS resolve request over the control
22224 port fails because we have overrun the limit on the number of
22225 connections, tell the controller that the request has failed.
22226 - Avoid using too little bandwidth when our clock skips a few
22227 seconds. Bugfix on 0.1.2.x.
22228 - Fix shell error when warning about missing packages in configure
22229 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
22230 - Do not become confused when receiving a spurious VERSIONS-like
22231 cell from a confused v1 client. Bugfix on 0.2.0.x.
22232 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
22233 introduction points for a hidden service have failed. Patch from
22234 Karsten Loesing. Bugfix on 0.2.0.x.
22236 o Code simplifications and refactoring:
22237 - Remove some needless generality from cpuworker code, for improved
22239 - Stop overloading the circuit_t.onionskin field for both "onionskin
22240 from a CREATE cell that we are waiting for a cpuworker to be
22241 assigned" and "onionskin from an EXTEND cell that we are going to
22242 send to an OR as soon as we are connected". Might help with bug 600.
22243 - Add an in-place version of aes_crypt() so that we can avoid doing a
22244 needless memcpy() call on each cell payload.
22247 Changes in version 0.2.0.18-alpha - 2008-01-25
22248 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
22249 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
22250 that can warn or reject connections to ports generally associated with
22251 vulnerable-plaintext protocols.
22253 o New directory authorities:
22254 - Set up dannenberg (run by CCC) as the sixth v3 directory
22258 - Fix a major memory leak when attempting to use the v2 TLS
22259 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
22260 - We accidentally enabled the under-development v2 TLS handshake
22261 code, which was causing log entries like "TLS error while
22262 renegotiating handshake". Disable it again. Resolves bug 590.
22263 - We were computing the wrong Content-Length: header for directory
22264 responses that need to be compressed on the fly, causing clients
22265 asking for those items to always fail. Bugfix on 0.2.0.x; partially
22269 - Avoid going directly to the directory authorities even if you're a
22270 relay, if you haven't found yourself reachable yet or if you've
22271 decided not to advertise your dirport yet. Addresses bug 556.
22272 - If we've gone 12 hours since our last bandwidth check, and we
22273 estimate we have less than 50KB bandwidth capacity but we could
22274 handle more, do another bandwidth test.
22275 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
22276 Tor can warn and/or refuse connections to ports commonly used with
22277 vulnerable-plaintext protocols. Currently we warn on ports 23,
22278 109, 110, and 143, but we don't reject any.
22281 - When we setconf ClientOnly to 1, close any current OR and Dir
22282 listeners. Reported by mwenge.
22283 - When we get a consensus that's been signed by more people than
22284 we expect, don't log about it; it's not a big deal. Reported
22288 - Don't answer "/tor/networkstatus-bridges" directory requests if
22289 the request isn't encrypted.
22290 - Make "ClientOnly 1" config option disable directory ports too.
22291 - Patches from Karsten Loesing to make v2 hidden services more
22292 robust: work even when there aren't enough HSDir relays available;
22293 retry when a v2 rend desc fetch fails; but don't retry if we
22294 already have a usable v0 rend desc.
22297 Changes in version 0.2.0.17-alpha - 2008-01-17
22298 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
22301 - Make the tor-gencert man page get included correctly in the tarball.
22304 Changes in version 0.2.0.16-alpha - 2008-01-17
22305 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
22306 Loesing, and generally cleans up a lot of features and minor bugs.
22308 o New directory authorities:
22309 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
22312 o Major performance improvements:
22313 - Switch our old ring buffer implementation for one more like that
22314 used by free Unix kernels. The wasted space in a buffer with 1mb
22315 of data will now be more like 8k than 1mb. The new implementation
22316 also avoids realloc();realloc(); patterns that can contribute to
22317 memory fragmentation.
22320 - Configuration files now accept C-style strings as values. This
22321 helps encode characters not allowed in the current configuration
22322 file format, such as newline or #. Addresses bug 557.
22323 - Although we fixed bug 539 (where servers would send HTTP status 503
22324 responses _and_ send a body too), there are still servers out
22325 there that haven't upgraded. Therefore, make clients parse such
22326 bodies when they receive them.
22327 - When we're not serving v2 directory information, there is no reason
22328 to actually keep any around. Remove the obsolete files and directory
22329 on startup if they are very old and we aren't going to serve them.
22331 o Minor performance improvements:
22332 - Reference-count and share copies of address policy entries; only 5%
22333 of them were actually distinct.
22334 - Never walk through the list of logs if we know that no log is
22335 interested in a given message.
22338 - When an authority has not signed a consensus, do not try to
22339 download a nonexistent "certificate with key 00000000". Bugfix
22340 on 0.2.0.x. Fixes bug 569.
22341 - Fix a rare assert error when we're closing one of our threads:
22342 use a mutex to protect the list of logs, so we never write to the
22343 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
22344 bug 575, which is kind of the revenge of bug 222.
22345 - Patch from Karsten Loesing to complain less at both the client
22346 and the relay when a relay used to have the HSDir flag but doesn't
22347 anymore, and we try to upload a hidden service descriptor.
22348 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
22350 - Do not try to download missing certificates until we have tried
22351 to check our fallback consensus. Fixes bug 583.
22352 - Make bridges round reported GeoIP stats info up to the nearest
22353 estimate, not down. Now we can distinguish between "0 people from
22354 this country" and "1 person from this country".
22355 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
22356 - Avoid possible segfault if key generation fails in
22357 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
22358 - Avoid segfault in the case where a badly behaved v2 versioning
22359 directory sends a signed networkstatus with missing client-versions.
22361 - Avoid segfaults on certain complex invocations of
22362 router_get_by_hexdigest(). Bugfix on 0.1.2.
22363 - Correct bad index on array access in parse_http_time(). Bugfix
22365 - Fix possible bug in vote generation when server versions are present
22366 but client versions are not.
22367 - Fix rare bug on REDIRECTSTREAM control command when called with no
22368 port set: it could erroneously report an error when none had
22370 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
22371 compressing large objects and find ourselves with more than 4k
22372 left over. Bugfix on 0.2.0.
22373 - Fix a small memory leak when setting up a hidden service.
22374 - Fix a few memory leaks that could in theory happen under bizarre
22376 - Fix an assert if we post a general-purpose descriptor via the
22377 control port but that descriptor isn't mentioned in our current
22378 network consensus. Bug reported by Jon McLachlan; bugfix on
22381 o Minor features (controller):
22382 - Get NS events working again. Patch from tup.
22383 - The GETCONF command now escapes and quotes configuration values
22384 that don't otherwise fit into the torrc file.
22385 - The SETCONF command now handles quoted values correctly.
22387 o Minor features (directory authorities):
22388 - New configuration options to override default maximum number of
22389 servers allowed on a single IP address. This is important for
22390 running a test network on a single host.
22391 - Actually implement the -s option to tor-gencert.
22392 - Add a manual page for tor-gencert.
22394 o Minor features (bridges):
22395 - Bridge authorities no longer serve bridge descriptors over
22396 unencrypted connections.
22398 o Minor features (other):
22399 - Add hidden services and DNSPorts to the list of things that make
22400 Tor accept that it has running ports. Change starting Tor with no
22401 ports from a fatal error to a warning; we might change it back if
22402 this turns out to confuse anybody. Fixes bug 579.
22405 Changes in version 0.1.2.19 - 2008-01-17
22406 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
22407 exit policy a little bit more conservative so it's safer to run an
22408 exit relay on a home system, and fixes a variety of smaller issues.
22411 - Exit policies now reject connections that are addressed to a
22412 relay's public (external) IP address too, unless
22413 ExitPolicyRejectPrivate is turned off. We do this because too
22414 many relays are running nearby to services that trust them based
22415 on network address.
22418 - When the clock jumps forward a lot, do not allow the bandwidth
22419 buckets to become negative. Fixes bug 544.
22420 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
22421 on every successful resolve. Reported by Mike Perry.
22422 - Purge old entries from the "rephist" database and the hidden
22423 service descriptor database even when DirPort is zero.
22424 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
22425 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
22426 crashing or mis-answering these requests.
22427 - When we decide to send a 503 response to a request for servers, do
22428 not then also send the server descriptors: this defeats the whole
22429 purpose. Fixes bug 539.
22432 - Changing the ExitPolicyRejectPrivate setting should cause us to
22433 rebuild our server descriptor.
22434 - Fix handling of hex nicknames when answering controller requests for
22435 networkstatus by name, or when deciding whether to warn about
22436 unknown routers in a config option. (Patch from mwenge.)
22437 - Fix a couple of hard-to-trigger autoconf problems that could result
22438 in really weird results on platforms whose sys/types.h files define
22439 nonstandard integer types.
22440 - Don't try to create the datadir when running --verify-config or
22441 --hash-password. Resolves bug 540.
22442 - If we were having problems getting a particular descriptor from the
22443 directory caches, and then we learned about a new descriptor for
22444 that router, we weren't resetting our failure count. Reported
22446 - Although we fixed bug 539 (where servers would send HTTP status 503
22447 responses _and_ send a body too), there are still servers out there
22448 that haven't upgraded. Therefore, make clients parse such bodies
22449 when they receive them.
22450 - Run correctly on systems where rlim_t is larger than unsigned long.
22451 This includes some 64-bit systems.
22452 - Run correctly on platforms (like some versions of OS X 10.5) where
22453 the real limit for number of open files is OPEN_FILES, not rlim_max
22454 from getrlimit(RLIMIT_NOFILES).
22455 - Avoid a spurious free on base64 failure.
22456 - Avoid segfaults on certain complex invocations of
22457 router_get_by_hexdigest().
22458 - Fix rare bug on REDIRECTSTREAM control command when called with no
22459 port set: it could erroneously report an error when none had
22463 Changes in version 0.2.0.15-alpha - 2007-12-25
22464 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
22465 features added in 0.2.0.13-alpha.
22468 - Fix several remotely triggerable asserts based on DirPort requests
22469 for a v2 or v3 networkstatus object before we were prepared. This
22470 was particularly bad for 0.2.0.13 and later bridge relays, who
22471 would never have a v2 networkstatus and would thus always crash
22472 when used. Bugfixes on 0.2.0.x.
22473 - Estimate the v3 networkstatus size more accurately, rather than
22474 estimating it at zero bytes and giving it artificially high priority
22475 compared to other directory requests. Bugfix on 0.2.0.x.
22478 - Fix configure.in logic for cross-compilation.
22479 - When we load a bridge descriptor from the cache, and it was
22480 previously unreachable, mark it as retriable so we won't just
22481 ignore it. Also, try fetching a new copy immediately. Bugfixes
22483 - The bridge GeoIP stats were counting other relays, for example
22484 self-reachability and authority-reachability tests.
22487 - Support compilation to target iPhone; patch from cjacker huang.
22488 To build for iPhone, pass the --enable-iphone option to configure.
22491 Changes in version 0.2.0.14-alpha - 2007-12-23
22493 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
22494 without a datadirectory from a previous Tor install. Reported
22496 - Fix a crash when we fetch a descriptor that turns out to be
22497 unexpected (it used to be in our networkstatus when we started
22498 fetching it, but it isn't in our current networkstatus), and we
22499 aren't using bridges. Bugfix on 0.2.0.x.
22500 - Fix a crash when accessing hidden services: it would work the first
22501 time you use a given introduction point for your service, but
22502 on subsequent requests we'd be using garbage memory. Fixed by
22503 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
22504 - Fix a crash when we load a bridge descriptor from disk but we don't
22505 currently have a Bridge line for it in our torrc. Bugfix on
22509 - If bridge authorities set BridgePassword, they will serve a
22510 snapshot of known bridge routerstatuses from their DirPort to
22511 anybody who knows that password. Unset by default.
22514 - Make the unit tests build again.
22515 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
22516 - Make PublishServerDescriptor default to 1, so the default doesn't
22517 have to change as we invent new directory protocol versions.
22518 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
22519 be included unless sys/time.h is already included. Fixes
22520 bug 553. Bugfix on 0.2.0.x.
22521 - If we receive a general-purpose descriptor and then receive an
22522 identical bridge-purpose descriptor soon after, don't discard
22523 the next one as a duplicate.
22526 - If BridgeRelay is set to 1, then the default for
22527 PublishServerDescriptor is now "bridge" rather than "v2,v3".
22528 - If the user sets RelayBandwidthRate but doesn't set
22529 RelayBandwidthBurst, then make them equal rather than erroring out.
22532 Changes in version 0.2.0.13-alpha - 2007-12-21
22533 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
22534 Goodell, fixes many more bugs, and adds a lot of infrastructure for
22537 o New directory authorities:
22538 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
22542 - Only update guard status (usable / not usable) once we have
22543 enough directory information. This was causing us to always pick
22544 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
22545 causing us to discard all our guards on startup if we hadn't been
22546 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
22547 - Purge old entries from the "rephist" database and the hidden
22548 service descriptor databases even when DirPort is zero. Bugfix
22550 - We were ignoring our RelayBandwidthRate for the first 30 seconds
22551 after opening a circuit -- even a relayed circuit. Bugfix on
22553 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
22554 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
22555 crashing or mis-answering these types of requests.
22556 - Relays were publishing their server descriptor to v1 and v2
22557 directory authorities, but they didn't try publishing to v3-only
22558 authorities. Fix this; and also stop publishing to v1 authorities.
22560 - When we were reading router descriptors from cache, we were ignoring
22561 the annotations -- so for example we were reading in bridge-purpose
22562 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
22563 - When we decided to send a 503 response to a request for servers, we
22564 were then also sending the server descriptors: this defeats the
22565 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
22568 - Bridge relays now behave like clients with respect to time
22569 intervals for downloading new consensus documents -- otherwise they
22570 stand out. Bridge users now wait until the end of the interval,
22571 so their bridge relay will be sure to have a new consensus document.
22572 - Three new config options (AlternateDirAuthority,
22573 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
22574 user selectively replace the default directory authorities by type,
22575 rather than the all-or-nothing replacement that DirServer offers.
22576 - Tor can now be configured to read a GeoIP file from disk in one
22577 of two formats. This can be used by controllers to map IP addresses
22578 to countries. Eventually, it may support exit-by-country.
22579 - When possible, bridge relays remember which countries users
22580 are coming from, and report aggregate information in their
22581 extra-info documents, so that the bridge authorities can learn
22582 where Tor is blocked.
22583 - Bridge directory authorities now do reachability testing on the
22584 bridges they know. They provide router status summaries to the
22585 controller via "getinfo ns/purpose/bridge", and also dump summaries
22586 to a file periodically.
22587 - Stop fetching directory info so aggressively if your DirPort is
22588 on but your ORPort is off; stop fetching v2 dir info entirely.
22589 You can override these choices with the new FetchDirInfoEarly
22593 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
22594 consensus documents when there are too many relays at a single
22595 IP address. Now clear it in v2 network status documents too, and
22596 also clear it in routerinfo_t when the relay is no longer listed
22597 in the relevant networkstatus document.
22598 - Don't crash if we get an unexpected value for the
22599 PublishServerDescriptor config option. Reported by Matt Edman;
22600 bugfix on 0.2.0.9-alpha.
22601 - Our new v2 hidden service descriptor format allows descriptors
22602 that have no introduction points. But Tor crashed when we tried
22603 to build a descriptor with no intro points (and it would have
22604 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
22605 by Karsten Loesing.
22606 - Fix building with dmalloc 5.5.2 with glibc.
22607 - Reject uploaded descriptors and extrainfo documents if they're
22608 huge. Otherwise we'll cache them all over the network and it'll
22609 clog everything up. Reported by Aljosha Judmayer.
22610 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
22611 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
22612 - When the DANGEROUS_VERSION controller status event told us we're
22613 running an obsolete version, it used the string "OLD" to describe
22614 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
22615 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
22616 - If we can't expand our list of entry guards (e.g. because we're
22617 using bridges or we have StrictEntryNodes set), don't mark relays
22618 down when they fail a directory request. Otherwise we're too quick
22619 to mark all our entry points down. Bugfix on 0.1.2.x.
22620 - Fix handling of hex nicknames when answering controller requests for
22621 networkstatus by name, or when deciding whether to warn about unknown
22622 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
22623 - Fix a couple of hard-to-trigger autoconf problems that could result
22624 in really weird results on platforms whose sys/types.h files define
22625 nonstandard integer types. Bugfix on 0.1.2.x.
22626 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
22627 - Don't crash on name lookup when we have no current consensus. Fixes
22628 bug 538; bugfix on 0.2.0.x.
22629 - Only Tors that want to mirror the v2 directory info should
22630 create the "cached-status" directory in their datadir. (All Tors
22631 used to create it.) Bugfix on 0.2.0.9-alpha.
22632 - Directory authorities should only automatically download Extra Info
22633 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
22636 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
22637 consumers. (We already do this on HUP.)
22638 - Authorities and caches fetch the v2 networkstatus documents
22639 less often, now that v3 is encouraged.
22640 - Add a new config option BridgeRelay that specifies you want to
22641 be a bridge relay. Right now the only difference is that it makes
22642 you answer begin_dir requests, and it makes you cache dir info,
22643 even if your DirPort isn't on.
22644 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
22645 ask about source, timestamp of arrival, purpose, etc. We need
22646 something like this to help Vidalia not do GeoIP lookups on bridge
22648 - Allow multiple HashedControlPassword config lines, to support
22649 multiple controller passwords.
22650 - Authorities now decide whether they're authoritative for a given
22651 router based on the router's purpose.
22652 - New config options AuthDirBadDir and AuthDirListBadDirs for
22653 authorities to mark certain relays as "bad directories" in the
22654 networkstatus documents. Also supports the "!baddir" directive in
22655 the approved-routers file.
22658 Changes in version 0.2.0.12-alpha - 2007-11-16
22659 This twelfth development snapshot fixes some more build problems as
22660 well as a few minor bugs.
22663 - Make it build on OpenBSD again. Patch from tup.
22664 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
22665 package-building for Red Hat, OS X, etc.
22667 o Minor bugfixes (on 0.1.2.x):
22668 - Changing the ExitPolicyRejectPrivate setting should cause us to
22669 rebuild our server descriptor.
22671 o Minor bugfixes (on 0.2.0.x):
22672 - When we're lacking a consensus, don't try to perform rendezvous
22673 operations. Reported by Karsten Loesing.
22674 - Fix a small memory leak whenever we decide against using a
22675 newly picked entry guard. Reported by Mike Perry.
22676 - When authorities detected more than two relays running on the same
22677 IP address, they were clearing all the status flags but forgetting
22678 to clear the "hsdir" flag. So clients were being told that a
22679 given relay was the right choice for a v2 hsdir lookup, yet they
22680 never had its descriptor because it was marked as 'not running'
22682 - If we're trying to fetch a bridge descriptor and there's no way
22683 the bridge authority could help us (for example, we don't know
22684 a digest, or there is no bridge authority), don't be so eager to
22685 fall back to asking the bridge authority.
22686 - If we're using bridges or have strictentrynodes set, and our
22687 chosen exit is in the same family as all our bridges/entry guards,
22688 then be flexible about families.
22691 - When we negotiate a v2 link-layer connection (not yet implemented),
22692 accept RELAY_EARLY cells and turn them into RELAY cells if we've
22693 negotiated a v1 connection for their next step. Initial code for
22697 Changes in version 0.2.0.11-alpha - 2007-11-12
22698 This eleventh development snapshot fixes some build problems with
22699 the previous snapshot. It also includes a more secure-by-default exit
22700 policy for relays, fixes an enormous memory leak for exit relays, and
22701 fixes another bug where servers were falling out of the directory list.
22704 - Exit policies now reject connections that are addressed to a
22705 relay's public (external) IP address too, unless
22706 ExitPolicyRejectPrivate is turned off. We do this because too
22707 many relays are running nearby to services that trust them based
22708 on network address. Bugfix on 0.1.2.x.
22711 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
22712 on every successful resolve. Reported by Mike Perry; bugfix
22714 - On authorities, never downgrade to old router descriptors simply
22715 because they're listed in the consensus. This created a catch-22
22716 where we wouldn't list a new descriptor because there was an
22717 old one in the consensus, and we couldn't get the new one in the
22718 consensus because we wouldn't list it. Possible fix for bug 548.
22719 Also, this might cause bug 543 to appear on authorities; if so,
22720 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
22722 o Packaging fixes on 0.2.0.10-alpha:
22723 - We were including instructions about what to do with the
22724 src/config/fallback-consensus file, but we weren't actually
22725 including it in the tarball. Disable all of that for now.
22728 - Allow people to say PreferTunnelledDirConns rather than
22729 PreferTunneledDirConns, for those alternate-spellers out there.
22732 - Don't reevaluate all the information from our consensus document
22733 just because we've downloaded a v2 networkstatus that we intend
22734 to cache. Fixes bug 545; bugfix on 0.2.0.x.
22737 Changes in version 0.2.0.10-alpha - 2007-11-10
22738 This tenth development snapshot adds a third v3 directory authority
22739 run by Mike Perry, adds most of Karsten Loesing's new hidden service
22740 descriptor format, fixes a bad crash bug and new bridge bugs introduced
22741 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
22742 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
22743 addresses many more minor issues.
22745 o New directory authorities:
22746 - Set up ides (run by Mike Perry) as the third v3 directory authority.
22749 - Allow tunnelled directory connections to ask for an encrypted
22750 "begin_dir" connection or an anonymized "uses a full Tor circuit"
22751 connection independently. Now we can make anonymized begin_dir
22752 connections for (e.g.) more secure hidden service posting and
22754 - More progress on proposal 114: code from Karsten Loesing to
22755 implement new hidden service descriptor format.
22756 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
22757 accommodate the growing number of servers that use the default
22758 and are reaching it.
22759 - Directory authorities use a new formula for selecting which nodes
22760 to advertise as Guards: they must be in the top 7/8 in terms of
22761 how long we have known about them, and above the median of those
22762 nodes in terms of weighted fractional uptime.
22763 - Make "not enough dir info yet" warnings describe *why* Tor feels
22764 it doesn't have enough directory info yet.
22767 - Stop servers from crashing if they set a Family option (or
22768 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
22770 - Make bridge users work again -- the move to v3 directories in
22771 0.2.0.9-alpha had introduced a number of bugs that made bridges
22772 no longer work for clients.
22773 - When the clock jumps forward a lot, do not allow the bandwidth
22774 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
22776 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
22777 - When the consensus lists a router descriptor that we previously were
22778 mirroring, but that we considered non-canonical, reload the
22779 descriptor as canonical. This fixes bug 543 where Tor servers
22780 would start complaining after a few days that they don't have
22781 enough directory information to build a circuit.
22782 - Consider replacing the current consensus when certificates arrive
22783 that make the pending consensus valid. Previously, we were only
22784 considering replacement when the new certs _didn't_ help.
22785 - Fix an assert error on startup if we didn't already have the
22786 consensus and certs cached in our datadirectory: we were caching
22787 the consensus in consensus_waiting_for_certs but then free'ing it
22789 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
22790 Request) if we need more v3 certs but we've already got pending
22791 requests for all of them.
22792 - Correctly back off from failing certificate downloads. Fixes
22794 - Authorities don't vote on the Running flag if they have been running
22795 for less than 30 minutes themselves. Fixes bug 547, where a newly
22796 started authority would vote that everyone was down.
22798 o New requirements:
22799 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
22800 it, it had no AES, and it hasn't seen any security patches since
22804 - Clients now hold circuitless TLS connections open for 1.5 times
22805 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
22806 rebuild a new circuit over them within that timeframe. Previously,
22807 they held them open only for KeepalivePeriod (5 minutes).
22808 - Use "If-Modified-Since" to avoid retrieving consensus
22809 networkstatuses that we already have.
22810 - When we have no consensus, check FallbackNetworkstatusFile (defaults
22811 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
22812 we start knowing some directory caches.
22813 - When we receive a consensus from the future, warn about skew.
22814 - Improve skew reporting: try to give the user a better log message
22815 about how skewed they are, and how much this matters.
22816 - When we have a certificate for an authority, believe that
22817 certificate's claims about the authority's IP address.
22818 - New --quiet command-line option to suppress the default console log.
22819 Good in combination with --hash-password.
22820 - Authorities send back an X-Descriptor-Not-New header in response to
22821 an accepted-but-discarded descriptor upload. Partially implements
22823 - Make the log message for "tls error. breaking." more useful.
22824 - Better log messages about certificate downloads, to attempt to
22825 track down the second incarnation of bug 546.
22827 o Minor features (bridges):
22828 - If bridge users set UpdateBridgesFromAuthority, but the digest
22829 they ask for is a 404 from the bridge authority, they now fall
22830 back to trying the bridge directly.
22831 - Bridges now use begin_dir to publish their server descriptor to
22832 the bridge authority, even when they haven't set TunnelDirConns.
22834 o Minor features (controller):
22835 - When reporting clock skew, and we know that the clock is _at least
22836 as skewed_ as some value, but we don't know the actual value,
22837 report the value as a "minimum skew."
22840 - Update linux-tor-prio.sh script to allow QoS based on the uid of
22841 the Tor process. Patch from Marco Bonetti with tweaks from Mike
22845 - Refuse to start if both ORPort and UseBridges are set. Bugfix
22846 on 0.2.0.x, suggested by Matt Edman.
22847 - Don't stop fetching descriptors when FetchUselessDescriptors is
22848 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
22849 reported by tup and ioerror.
22850 - Better log message on vote from unknown authority.
22851 - Don't log "Launching 0 request for 0 router" message.
22853 o Minor bugfixes (memory leaks):
22854 - Stop leaking memory every time we parse a v3 certificate. Bugfix
22856 - Stop leaking memory every time we load a v3 certificate. Bugfix
22857 on 0.2.0.1-alpha. Fixes bug 536.
22858 - Stop leaking a cached networkstatus on exit. Bugfix on
22860 - Stop leaking voter information every time we free a consensus.
22861 Bugfix on 0.2.0.3-alpha.
22862 - Stop leaking signed data every time we check a voter signature.
22863 Bugfix on 0.2.0.3-alpha.
22864 - Stop leaking a signature every time we fail to parse a consensus or
22865 a vote. Bugfix on 0.2.0.3-alpha.
22866 - Stop leaking v2_download_status_map on shutdown. Bugfix on
22868 - Stop leaking conn->nickname every time we make a connection to a
22869 Tor relay without knowing its expected identity digest (e.g. when
22870 using bridges). Bugfix on 0.2.0.3-alpha.
22872 - Minor bugfixes (portability):
22873 - Run correctly on platforms where rlim_t is larger than unsigned
22874 long, and/or where the real limit for number of open files is
22875 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
22876 particular, these may be needed for OS X 10.5.
22879 Changes in version 0.1.2.18 - 2007-10-28
22880 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
22881 hidden service introduction that were causing huge delays, and a big
22882 bug that was causing some servers to disappear from the network status
22883 lists for a few hours each day.
22885 o Major bugfixes (crashes):
22886 - If a connection is shut down abruptly because of something that
22887 happened inside connection_flushed_some(), do not call
22888 connection_finished_flushing(). Should fix bug 451:
22889 "connection_stop_writing: Assertion conn->write_event failed"
22890 Bugfix on 0.1.2.7-alpha.
22891 - Fix possible segfaults in functions called from
22892 rend_process_relay_cell().
22894 o Major bugfixes (hidden services):
22895 - Hidden services were choosing introduction points uniquely by
22896 hexdigest, but when constructing the hidden service descriptor
22897 they merely wrote the (potentially ambiguous) nickname.
22898 - Clients now use the v2 intro format for hidden service
22899 connections: they specify their chosen rendezvous point by identity
22900 digest rather than by (potentially ambiguous) nickname. These
22901 changes could speed up hidden service connections dramatically.
22903 o Major bugfixes (other):
22904 - Stop publishing a new server descriptor just because we get a
22905 HUP signal. This led (in a roundabout way) to some servers getting
22906 dropped from the networkstatus lists for a few hours each day.
22907 - When looking for a circuit to cannibalize, consider family as well
22908 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
22909 circuit cannibalization).
22910 - When a router wasn't listed in a new networkstatus, we were leaving
22911 the flags for that router alone -- meaning it remained Named,
22912 Running, etc -- even though absence from the networkstatus means
22913 that it shouldn't be considered to exist at all anymore. Now we
22914 clear all the flags for routers that fall out of the networkstatus
22915 consensus. Fixes bug 529.
22918 - Don't try to access (or alter) the state file when running
22919 --list-fingerprint or --verify-config or --hash-password. Resolves
22921 - When generating information telling us how to extend to a given
22922 router, do not try to include the nickname if it is
22923 absent. Resolves bug 467.
22924 - Fix a user-triggerable segfault in expand_filename(). (There isn't
22925 a way to trigger this remotely.)
22926 - When sending a status event to the controller telling it that an
22927 OR address is reachable, set the port correctly. (Previously we
22928 were reporting the dir port.)
22929 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
22930 command. Bugfix on 0.1.2.17.
22931 - When loading bandwidth history, do not believe any information in
22932 the future. Fixes bug 434.
22933 - When loading entry guard information, do not believe any information
22935 - When we have our clock set far in the future and generate an
22936 onion key, then re-set our clock to be correct, we should not stop
22937 the onion key from getting rotated.
22938 - On some platforms, accept() can return a broken address. Detect
22939 this more quietly, and deal accordingly. Fixes bug 483.
22940 - It's not actually an error to find a non-pending entry in the DNS
22941 cache when canceling a pending resolve. Don't log unless stuff
22942 is fishy. Resolves bug 463.
22943 - Don't reset trusted dir server list when we set a configuration
22944 option. Patch from Robert Hogan.
22945 - Don't try to create the datadir when running --verify-config or
22946 --hash-password. Resolves bug 540.
22949 Changes in version 0.2.0.9-alpha - 2007-10-24
22950 This ninth development snapshot switches clients to the new v3 directory
22951 system; allows servers to be listed in the network status even when they
22952 have the same nickname as a registered server; and fixes many other
22953 bugs including a big one that was causing some servers to disappear
22954 from the network status lists for a few hours each day.
22956 o Major features (directory system):
22957 - Clients now download v3 consensus networkstatus documents instead
22958 of v2 networkstatus documents. Clients and caches now base their
22959 opinions about routers on these consensus documents. Clients only
22960 download router descriptors listed in the consensus.
22961 - Authorities now list servers who have the same nickname as
22962 a different named server, but list them with a new flag,
22963 "Unnamed". Now we can list servers that happen to pick the same
22964 nickname as a server that registered two years ago and then
22965 disappeared. Partially implements proposal 122.
22966 - If the consensus lists a router as "Unnamed", the name is assigned
22967 to a different router: do not identify the router by that name.
22968 Partially implements proposal 122.
22969 - Authorities can now come to a consensus on which method to use to
22970 compute the consensus. This gives us forward compatibility.
22973 - Stop publishing a new server descriptor just because we HUP or
22974 when we find our DirPort to be reachable but won't actually publish
22975 it. New descriptors without any real changes are dropped by the
22976 authorities, and can screw up our "publish every 18 hours" schedule.
22978 - When a router wasn't listed in a new networkstatus, we were leaving
22979 the flags for that router alone -- meaning it remained Named,
22980 Running, etc -- even though absence from the networkstatus means
22981 that it shouldn't be considered to exist at all anymore. Now we
22982 clear all the flags for routers that fall out of the networkstatus
22983 consensus. Fixes bug 529; bugfix on 0.1.2.x.
22984 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
22985 extrainfo documents and then discard them immediately for not
22986 matching the latest router. Bugfix on 0.2.0.1-alpha.
22988 o Minor features (v3 directory protocol):
22989 - Allow tor-gencert to generate a new certificate without replacing
22991 - Allow certificates to include an address.
22992 - When we change our directory-cache settings, reschedule all voting
22993 and download operations.
22994 - Reattempt certificate downloads immediately on failure, as long as
22995 we haven't failed a threshold number of times yet.
22996 - Delay retrying consensus downloads while we're downloading
22997 certificates to verify the one we just got. Also, count getting a
22998 consensus that we already have (or one that isn't valid) as a failure,
22999 and count failing to get the certificates after 20 minutes as a
23001 - Build circuits and download descriptors even if our consensus is a
23002 little expired. (This feature will go away once authorities are
23005 o Minor features (router descriptor cache):
23006 - If we find a cached-routers file that's been sitting around for more
23007 than 28 days unmodified, then most likely it's a leftover from
23008 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
23010 - When we (as a cache) download a descriptor because it was listed
23011 in a consensus, remember when the consensus was supposed to expire,
23012 and don't expire the descriptor until then.
23014 o Minor features (performance):
23015 - Call routerlist_remove_old_routers() much less often. This should
23016 speed startup, especially on directory caches.
23017 - Don't try to launch new descriptor downloads quite so often when we
23018 already have enough directory information to build circuits.
23019 - Base64 decoding was actually showing up on our profile when parsing
23020 the initial descriptor file; switch to an in-process all-at-once
23021 implementation that's about 3.5x times faster than calling out to
23024 o Minor features (compilation):
23025 - Detect non-ASCII platforms (if any still exist) and refuse to
23026 build there: some of our code assumes that 'A' is 65 and so on.
23028 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
23029 - Make the "next period" votes into "current period" votes immediately
23030 after publishing the consensus; avoid a heisenbug that made them
23031 stick around indefinitely.
23032 - When we discard a vote as a duplicate, do not report this as
23034 - Treat missing v3 keys or certificates as an error when running as a
23035 v3 directory authority.
23036 - When we're configured to be a v3 authority, but we're only listed
23037 as a non-v3 authority in our DirServer line for ourself, correct
23039 - If an authority doesn't have a qualified hostname, just put
23040 its address in the vote. This fixes the problem where we referred to
23041 "moria on moria:9031."
23042 - Distinguish between detached signatures for the wrong period, and
23043 detached signatures for a divergent vote.
23044 - Fix a small memory leak when computing a consensus.
23045 - When there's no consensus, we were forming a vote every 30
23046 minutes, but writing the "valid-after" line in our vote based
23047 on our configured V3AuthVotingInterval: so unless the intervals
23048 matched up, we immediately rejected our own vote because it didn't
23049 start at the voting interval that caused us to construct a vote.
23051 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
23052 - Delete unverified-consensus when the real consensus is set.
23053 - Consider retrying a consensus networkstatus fetch immediately
23054 after one fails: don't wait 60 seconds to notice.
23055 - When fetching a consensus as a cache, wait until a newer consensus
23056 should exist before trying to replace the current one.
23057 - Use a more forgiving schedule for retrying failed consensus
23058 downloads than for other types.
23060 o Minor bugfixes (other directory issues):
23061 - Correct the implementation of "download votes by digest." Bugfix on
23063 - Authorities no longer send back "400 you're unreachable please fix
23064 it" errors to Tor servers that aren't online all the time. We're
23065 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
23067 o Minor bugfixes (controller):
23068 - Don't reset trusted dir server list when we set a configuration
23069 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
23070 - Respond to INT and TERM SIGNAL commands before we execute the
23071 signal, in case the signal shuts us down. We had a patch in
23072 0.1.2.1-alpha that tried to do this by queueing the response on
23073 the connection's buffer before shutting down, but that really
23074 isn't the same thing at all. Bug located by Matt Edman.
23076 o Minor bugfixes (misc):
23077 - Correctly check for bad options to the "PublishServerDescriptor"
23078 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
23079 - Stop leaking memory on failing case of base32_decode, and make
23080 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
23081 - Don't try to download extrainfo documents when we're trying to
23082 fetch enough directory info to build a circuit: having enough
23083 info should get priority. Bugfix on 0.2.0.x.
23084 - Don't complain that "your server has not managed to confirm that its
23085 ports are reachable" if we haven't been able to build any circuits
23086 yet. Bug found by spending four hours without a v3 consensus. Bugfix
23088 - Detect the reason for failing to mmap a descriptor file we just
23089 wrote, and give a more useful log message. Fixes bug 533. Bugfix
23092 o Code simplifications and refactoring:
23093 - Remove support for the old bw_accounting file: we've been storing
23094 bandwidth accounting information in the state file since
23095 0.1.2.5-alpha. This may result in bandwidth accounting errors
23096 if you try to upgrade from 0.1.1.x or earlier, or if you try to
23097 downgrade to 0.1.1.x or earlier.
23098 - New convenience code to locate a file within the DataDirectory.
23099 - Move non-authority functionality out of dirvote.c.
23100 - Refactor the arguments for router_pick_{directory_|trusteddir}server
23101 so that they all take the same named flags.
23104 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
23105 Unix users an easy way to script their Tor process (e.g. by
23106 adjusting bandwidth based on the time of the day).
23109 Changes in version 0.2.0.8-alpha - 2007-10-12
23110 This eighth development snapshot fixes a crash bug that's been bothering
23111 us since February 2007, lets bridge authorities store a list of bridge
23112 descriptors they've seen, gets v3 directory voting closer to working,
23113 starts caching v3 directory consensus documents on directory mirrors,
23114 and fixes a variety of smaller issues including some minor memory leaks.
23116 o Major features (router descriptor cache):
23117 - Store routers in a file called cached-descriptors instead of in
23118 cached-routers. Initialize cached-descriptors from cached-routers
23119 if the old format is around. The new format allows us to store
23120 annotations along with descriptors.
23121 - Use annotations to record the time we received each descriptor, its
23122 source, and its purpose.
23123 - Disable the SETROUTERPURPOSE controller command: it is now
23125 - Controllers should now specify cache=no or cache=yes when using
23126 the +POSTDESCRIPTOR command.
23127 - Bridge authorities now write bridge descriptors to disk, meaning
23128 we can export them to other programs and begin distributing them
23131 o Major features (directory authorities):
23132 - When a v3 authority is missing votes or signatures, it now tries
23134 - Directory authorities track weighted fractional uptime as well as
23135 weighted mean-time-between failures. WFU is suitable for deciding
23136 whether a node is "usually up", while MTBF is suitable for deciding
23137 whether a node is "likely to stay up." We need both, because
23138 "usually up" is a good requirement for guards, while "likely to
23139 stay up" is a good requirement for long-lived connections.
23141 o Major features (v3 directory system):
23142 - Caches now download v3 network status documents as needed,
23143 and download the descriptors listed in them.
23144 - All hosts now attempt to download and keep fresh v3 authority
23145 certificates, and re-attempt after failures.
23146 - More internal-consistency checks for vote parsing.
23148 o Major bugfixes (crashes):
23149 - If a connection is shut down abruptly because of something that
23150 happened inside connection_flushed_some(), do not call
23151 connection_finished_flushing(). Should fix bug 451. Bugfix on
23154 o Major bugfixes (performance):
23155 - Fix really bad O(n^2) performance when parsing a long list of
23156 routers: Instead of searching the entire list for an "extra-info "
23157 string which usually wasn't there, once for every routerinfo
23158 we read, just scan lines forward until we find one we like.
23160 - When we add data to a write buffer in response to the data on that
23161 write buffer getting low because of a flush, do not consider the
23162 newly added data as a candidate for immediate flushing, but rather
23163 make it wait until the next round of writing. Otherwise, we flush
23164 and refill recursively, and a single greedy TLS connection can
23165 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
23167 o Minor features (v3 authority system):
23168 - Add more ways for tools to download the votes that lead to the
23170 - Send a 503 when low on bandwidth and a vote, consensus, or
23171 certificate is requested.
23172 - If-modified-since is now implemented properly for all kinds of
23173 certificate requests.
23175 o Minor bugfixes (network statuses):
23176 - Tweak the implementation of proposal 109 slightly: allow at most
23177 two Tor servers on the same IP address, except if it's the location
23178 of a directory authority, in which case allow five. Bugfix on
23181 o Minor bugfixes (controller):
23182 - When sending a status event to the controller telling it that an
23183 OR address is reachable, set the port correctly. (Previously we
23184 were reporting the dir port.) Bugfix on 0.1.2.x.
23186 o Minor bugfixes (v3 directory system):
23187 - Fix logic to look up a cert by its signing key digest. Bugfix on
23189 - Only change the reply to a vote to "OK" if it's not already
23190 set. This gets rid of annoying "400 OK" log messages, which may
23191 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
23192 - When we get a valid consensus, recompute the voting schedule.
23193 - Base the valid-after time of a vote on the consensus voting
23194 schedule, not on our preferred schedule.
23195 - Make the return values and messages from signature uploads and
23196 downloads more sensible.
23197 - Fix a memory leak when serving votes and consensus documents, and
23198 another when serving certificates.
23200 o Minor bugfixes (performance):
23201 - Use a slightly simpler string hashing algorithm (copying Python's
23202 instead of Java's) and optimize our digest hashing algorithm to take
23203 advantage of 64-bit platforms and to remove some possibly-costly
23205 - Fix a minor memory leak whenever we parse guards from our state
23206 file. Bugfix on 0.2.0.7-alpha.
23207 - Fix a minor memory leak whenever we write out a file. Bugfix on
23209 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
23210 command. Bugfix on 0.2.0.5-alpha.
23212 o Minor bugfixes (portability):
23213 - On some platforms, accept() can return a broken address. Detect
23214 this more quietly, and deal accordingly. Fixes bug 483.
23215 - Stop calling tor_strlower() on uninitialized memory in some cases.
23216 Bugfix in 0.2.0.7-alpha.
23218 o Minor bugfixes (usability):
23219 - Treat some 403 responses from directory servers as INFO rather than
23220 WARN-severity events.
23221 - It's not actually an error to find a non-pending entry in the DNS
23222 cache when canceling a pending resolve. Don't log unless stuff is
23223 fishy. Resolves bug 463.
23225 o Minor bugfixes (anonymity):
23226 - Never report that we've used more bandwidth than we're willing to
23227 relay: it leaks how much non-relay traffic we're using. Resolves
23229 - When looking for a circuit to cannibalize, consider family as well
23230 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
23231 circuit cannibalization).
23233 o Code simplifications and refactoring:
23234 - Make a bunch of functions static. Remove some dead code.
23235 - Pull out about a third of the really big routerlist.c; put it in a
23236 new module, networkstatus.c.
23237 - Merge the extra fields in local_routerstatus_t back into
23238 routerstatus_t: we used to need one routerstatus_t for each
23239 authority's opinion, plus a local_routerstatus_t for the locally
23240 computed consensus opinion. To save space, we put the locally
23241 modified fields into local_routerstatus_t, and only the common
23242 stuff into routerstatus_t. But once v3 directories are in use,
23243 clients and caches will no longer need to hold authority opinions;
23244 thus, the rationale for keeping the types separate is now gone.
23245 - Make the code used to reschedule and reattempt downloads more
23247 - Turn all 'Are we a directory server/mirror?' logic into a call to
23249 - Remove the code to generate the oldest (v1) directory format.
23250 The code has been disabled since 0.2.0.5-alpha.
23253 Changes in version 0.2.0.7-alpha - 2007-09-21
23254 This seventh development snapshot makes bridges work again, makes bridge
23255 authorities work for the first time, fixes two huge performance flaws
23256 in hidden services, and fixes a variety of minor issues.
23258 o New directory authorities:
23259 - Set up moria1 and tor26 as the first v3 directory authorities. See
23260 doc/spec/dir-spec.txt for details on the new directory design.
23262 o Major bugfixes (crashes):
23263 - Fix possible segfaults in functions called from
23264 rend_process_relay_cell(). Bugfix on 0.1.2.x.
23266 o Major bugfixes (bridges):
23267 - Fix a bug that made servers send a "404 Not found" in response to
23268 attempts to fetch their server descriptor. This caused Tor servers
23269 to take many minutes to establish reachability for their DirPort,
23270 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
23271 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
23272 users configure that and specify a bridge with an identity
23273 fingerprint, now they will lookup the bridge descriptor at the
23274 default bridge authority via a one-hop tunnel, but once circuits
23275 are established they will switch to a three-hop tunnel for later
23276 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
23278 o Major bugfixes (hidden services):
23279 - Hidden services were choosing introduction points uniquely by
23280 hexdigest, but when constructing the hidden service descriptor
23281 they merely wrote the (potentially ambiguous) nickname.
23282 - Clients now use the v2 intro format for hidden service
23283 connections: they specify their chosen rendezvous point by identity
23284 digest rather than by (potentially ambiguous) nickname. Both
23285 are bugfixes on 0.1.2.x, and they could speed up hidden service
23286 connections dramatically. Thanks to Karsten Loesing.
23288 o Minor features (security):
23289 - As a client, do not believe any server that tells us that an
23290 address maps to an internal address space.
23291 - Make it possible to enable HashedControlPassword and
23292 CookieAuthentication at the same time.
23294 o Minor features (guard nodes):
23295 - Tag every guard node in our state file with the version that
23296 we believe added it, or with our own version if we add it. This way,
23297 if a user temporarily runs an old version of Tor and then switches
23298 back to a new one, she doesn't automatically lose her guards.
23300 o Minor features (speed):
23301 - When implementing AES counter mode, update only the portions of the
23302 counter buffer that need to change, and don't keep separate
23303 network-order and host-order counters when they are the same (i.e.,
23304 on big-endian hosts.)
23306 o Minor features (controller):
23307 - Accept LF instead of CRLF on controller, since some software has a
23308 hard time generating real Internet newlines.
23309 - Add GETINFO values for the server status events
23310 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
23313 o Removed features:
23314 - Routers no longer include bandwidth-history lines in their
23315 descriptors; this information is already available in extra-info
23316 documents, and including it in router descriptors took up 60%
23317 (!) of compressed router descriptor downloads. Completes
23318 implementation of proposal 104.
23319 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
23320 and TorControl.py, as they use the old v0 controller protocol,
23321 and are obsoleted by TorFlow anyway.
23322 - Drop support for v1 rendezvous descriptors, since we never used
23323 them anyway, and the code has probably rotted by now. Based on
23324 patch from Karsten Loesing.
23325 - On OSX, stop warning the user that kqueue support in libevent is
23326 "experimental", since it seems to have worked fine for ages.
23329 - When generating information telling us how to extend to a given
23330 router, do not try to include the nickname if it is absent. Fixes
23331 bug 467. Bugfix on 0.2.0.3-alpha.
23332 - Fix a user-triggerable (but not remotely-triggerable) segfault
23333 in expand_filename(). Bugfix on 0.1.2.x.
23334 - Fix a memory leak when freeing incomplete requests from DNSPort.
23335 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
23336 - Don't try to access (or alter) the state file when running
23337 --list-fingerprint or --verify-config or --hash-password. (Resolves
23338 bug 499.) Bugfix on 0.1.2.x.
23339 - Servers used to decline to publish their DirPort if their
23340 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
23341 were below a threshold. Now they only look at BandwidthRate and
23342 RelayBandwidthRate. Bugfix on 0.1.2.x.
23343 - Remove an optimization in the AES counter-mode code that assumed
23344 that the counter never exceeded 2^68. When the counter can be set
23345 arbitrarily as an IV (as it is by Karsten's new hidden services
23346 code), this assumption no longer holds. Bugfix on 0.1.2.x.
23347 - Resume listing "AUTHORITY" flag for authorities in network status.
23348 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
23350 o Code simplifications and refactoring:
23351 - Revamp file-writing logic so we don't need to have the entire
23352 contents of a file in memory at once before we write to disk. Tor,
23354 - Turn "descriptor store" into a full-fledged type.
23355 - Move all NT services code into a separate source file.
23356 - Unify all code that computes medians, percentile elements, etc.
23357 - Get rid of a needless malloc when parsing address policies.
23360 Changes in version 0.1.2.17 - 2007-08-30
23361 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
23362 X bundles. Vidalia 0.0.14 makes authentication required for the
23363 ControlPort in the default configuration, which addresses important
23364 security risks. Everybody who uses Vidalia (or another controller)
23367 In addition, this Tor update fixes major load balancing problems with
23368 path selection, which should speed things up a lot once many people
23371 o Major bugfixes (security):
23372 - We removed support for the old (v0) control protocol. It has been
23373 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
23374 become more of a headache than it's worth.
23376 o Major bugfixes (load balancing):
23377 - When choosing nodes for non-guard positions, weight guards
23378 proportionally less, since they already have enough load. Patch
23380 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
23381 will allow fast Tor servers to get more attention.
23382 - When we're upgrading from an old Tor version, forget our current
23383 guards and pick new ones according to the new weightings. These
23384 three load balancing patches could raise effective network capacity
23385 by a factor of four. Thanks to Mike Perry for measurements.
23387 o Major bugfixes (stream expiration):
23388 - Expire not-yet-successful application streams in all cases if
23389 they've been around longer than SocksTimeout. Right now there are
23390 some cases where the stream will live forever, demanding a new
23391 circuit every 15 seconds. Fixes bug 454; reported by lodger.
23393 o Minor features (controller):
23394 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
23395 is valid before any authentication has been received. It tells
23396 a controller what kind of authentication is expected, and what
23397 protocol is spoken. Implements proposal 119.
23399 o Minor bugfixes (performance):
23400 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
23401 greatly speeding up loading cached-routers from disk on startup.
23402 - Disable sentinel-based debugging for buffer code: we squashed all
23403 the bugs that this was supposed to detect a long time ago, and now
23404 its only effect is to change our buffer sizes from nice powers of
23405 two (which platform mallocs tend to like) to values slightly over
23406 powers of two (which make some platform mallocs sad).
23408 o Minor bugfixes (misc):
23409 - If exit bandwidth ever exceeds one third of total bandwidth, then
23410 use the correct formula to weight exit nodes when choosing paths.
23411 Based on patch from Mike Perry.
23412 - Choose perfectly fairly among routers when choosing by bandwidth and
23413 weighting by fraction of bandwidth provided by exits. Previously, we
23414 would choose with only approximate fairness, and correct ourselves
23415 if we ran off the end of the list.
23416 - If we require CookieAuthentication but we fail to write the
23417 cookie file, we would warn but not exit, and end up in a state
23418 where no controller could authenticate. Now we exit.
23419 - If we require CookieAuthentication, stop generating a new cookie
23420 every time we change any piece of our config.
23421 - Refuse to start with certain directory authority keys, and
23422 encourage people using them to stop.
23423 - Terminate multi-line control events properly. Original patch
23425 - Fix a minor memory leak when we fail to find enough suitable
23426 servers to choose a circuit.
23427 - Stop leaking part of the descriptor when we run into a particularly
23428 unparseable piece of it.
23431 Changes in version 0.2.0.6-alpha - 2007-08-26
23432 This sixth development snapshot features a new Vidalia version in the
23433 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
23434 the ControlPort in the default configuration, which addresses important
23437 In addition, this snapshot fixes major load balancing problems
23438 with path selection, which should speed things up a lot once many
23439 people have upgraded. The directory authorities also use a new
23440 mean-time-between-failure approach to tracking which servers are stable,
23441 rather than just looking at the most recent uptime.
23443 o New directory authorities:
23444 - Set up Tonga as the default bridge directory authority.
23447 - Directory authorities now track servers by weighted
23448 mean-times-between-failures. When we have 4 or more days of data,
23449 use measured MTBF rather than declared uptime to decide whether
23450 to call a router Stable. Implements proposal 108.
23452 o Major bugfixes (load balancing):
23453 - When choosing nodes for non-guard positions, weight guards
23454 proportionally less, since they already have enough load. Patch
23456 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
23457 will allow fast Tor servers to get more attention.
23458 - When we're upgrading from an old Tor version, forget our current
23459 guards and pick new ones according to the new weightings. These
23460 three load balancing patches could raise effective network capacity
23461 by a factor of four. Thanks to Mike Perry for measurements.
23463 o Major bugfixes (descriptor parsing):
23464 - Handle unexpected whitespace better in malformed descriptors. Bug
23465 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
23468 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
23469 GETINFO for Torstat to use until it can switch to using extrainfos.
23470 - Optionally (if built with -DEXPORTMALLINFO) export the output
23471 of mallinfo via http, as tor/mallinfo.txt. Only accessible
23475 - Do not intermix bridge routers with controller-added
23476 routers. (Bugfix on 0.2.0.x)
23477 - Do not fail with an assert when accept() returns an unexpected
23478 address family. Addresses but does not wholly fix bug 483. (Bugfix
23480 - Let directory authorities startup even when they can't generate
23481 a descriptor immediately, e.g. because they don't know their
23483 - Stop putting the authentication cookie in a file called "0"
23484 in your working directory if you don't specify anything for the
23485 new CookieAuthFile option. Reported by Matt Edman.
23486 - Make it possible to read the PROTOCOLINFO response in a way that
23487 conforms to our control-spec. Reported by Matt Edman.
23488 - Fix a minor memory leak when we fail to find enough suitable
23489 servers to choose a circuit. Bugfix on 0.1.2.x.
23490 - Stop leaking part of the descriptor when we run into a particularly
23491 unparseable piece of it. Bugfix on 0.1.2.x.
23492 - Unmap the extrainfo cache file on exit.
23495 Changes in version 0.2.0.5-alpha - 2007-08-19
23496 This fifth development snapshot fixes compilation on Windows again;
23497 fixes an obnoxious client-side bug that slowed things down and put
23498 extra load on the network; gets us closer to using the v3 directory
23499 voting scheme; makes it easier for Tor controllers to use cookie-based
23500 authentication; and fixes a variety of other bugs.
23502 o Removed features:
23503 - Version 1 directories are no longer generated in full. Instead,
23504 authorities generate and serve "stub" v1 directories that list
23505 no servers. This will stop Tor versions 0.1.0.x and earlier from
23506 working, but (for security reasons) nobody should be running those
23509 o Major bugfixes (compilation, 0.2.0.x):
23510 - Try to fix Win32 compilation again: improve checking for IPv6 types.
23511 - Try to fix MSVC compilation: build correctly on platforms that do
23512 not define s6_addr16 or s6_addr32.
23513 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
23516 o Major bugfixes (stream expiration):
23517 - Expire not-yet-successful application streams in all cases if
23518 they've been around longer than SocksTimeout. Right now there are
23519 some cases where the stream will live forever, demanding a new
23520 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
23521 reported by lodger.
23523 o Minor features (directory servers):
23524 - When somebody requests a list of statuses or servers, and we have
23525 none of those, return a 404 rather than an empty 200.
23527 o Minor features (directory voting):
23528 - Store v3 consensus status consensuses on disk, and reload them
23531 o Minor features (security):
23532 - Warn about unsafe ControlPort configurations.
23533 - Refuse to start with certain directory authority keys, and
23534 encourage people using them to stop.
23536 o Minor features (controller):
23537 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
23538 is valid before any authentication has been received. It tells
23539 a controller what kind of authentication is expected, and what
23540 protocol is spoken. Implements proposal 119.
23541 - New config option CookieAuthFile to choose a new location for the
23542 cookie authentication file, and config option
23543 CookieAuthFileGroupReadable to make it group-readable.
23545 o Minor features (unit testing):
23546 - Add command-line arguments to unit-test executable so that we can
23547 invoke any chosen test from the command line rather than having
23548 to run the whole test suite at once; and so that we can turn on
23549 logging for the unit tests.
23551 o Minor bugfixes (on 0.1.2.x):
23552 - If we require CookieAuthentication but we fail to write the
23553 cookie file, we would warn but not exit, and end up in a state
23554 where no controller could authenticate. Now we exit.
23555 - If we require CookieAuthentication, stop generating a new cookie
23556 every time we change any piece of our config.
23557 - When loading bandwidth history, do not believe any information in
23558 the future. Fixes bug 434.
23559 - When loading entry guard information, do not believe any information
23561 - When we have our clock set far in the future and generate an
23562 onion key, then re-set our clock to be correct, we should not stop
23563 the onion key from getting rotated.
23564 - Clean up torrc sample config file.
23565 - Do not automatically run configure from autogen.sh. This
23566 non-standard behavior tended to annoy people who have built other
23569 o Minor bugfixes (on 0.2.0.x):
23570 - Fix a bug with AutomapHostsOnResolve that would always cause
23571 the second request to fail. Bug reported by Kate. Bugfix on
23573 - Fix a bug in ADDRMAP controller replies that would sometimes
23574 try to print a NULL. Patch from tup.
23575 - Read v3 directory authority keys from the right location.
23576 - Numerous bugfixes to directory voting code.
23579 Changes in version 0.1.2.16 - 2007-08-01
23580 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
23581 remote attacker in certain situations to rewrite the user's torrc
23582 configuration file. This can completely compromise anonymity of users
23583 in most configurations, including those running the Vidalia bundles,
23584 TorK, etc. Or worse.
23586 o Major security fixes:
23587 - Close immediately after missing authentication on control port;
23588 do not allow multiple authentication attempts.
23591 Changes in version 0.2.0.4-alpha - 2007-08-01
23592 This fourth development snapshot fixes a critical security vulnerability
23593 for most users, specifically those running Vidalia, TorK, etc. Everybody
23594 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
23596 o Major security fixes:
23597 - Close immediately after missing authentication on control port;
23598 do not allow multiple authentication attempts.
23600 o Major bugfixes (compilation):
23601 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
23604 o Minor features (performance):
23605 - Be even more aggressive about releasing RAM from small
23606 empty buffers. Thanks to our free-list code, this shouldn't be too
23607 performance-intensive.
23608 - Disable sentinel-based debugging for buffer code: we squashed all
23609 the bugs that this was supposed to detect a long time ago, and
23610 now its only effect is to change our buffer sizes from nice
23611 powers of two (which platform mallocs tend to like) to values
23612 slightly over powers of two (which make some platform mallocs sad).
23613 - Log malloc statistics from mallinfo() on platforms where it
23617 Changes in version 0.2.0.3-alpha - 2007-07-29
23618 This third development snapshot introduces new experimental
23619 blocking-resistance features and a preliminary version of the v3
23620 directory voting design, and includes many other smaller features
23624 - The first pieces of our "bridge" design for blocking-resistance
23625 are implemented. People can run bridge directory authorities;
23626 people can run bridges; and people can configure their Tor clients
23627 with a set of bridges to use as the first hop into the Tor network.
23628 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
23630 - Create listener connections before we setuid to the configured
23631 User and Group. Now non-Windows users can choose port values
23632 under 1024, start Tor as root, and have Tor bind those ports
23633 before it changes to another UID. (Windows users could already
23635 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
23636 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
23637 on "vserver" accounts. (Patch from coderman.)
23638 - Be even more aggressive about separating local traffic from relayed
23639 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
23641 o Major features (experimental):
23642 - First cut of code for "v3 dir voting": directory authorities will
23643 vote on a common network status document rather than each publishing
23644 their own opinion. This code needs more testing and more corner-case
23645 handling before it's ready for use.
23648 - Directory authorities now call routers Fast if their bandwidth is
23649 at least 100KB/s, and consider their bandwidth adequate to be a
23650 Guard if it is at least 250KB/s, no matter the medians. This fix
23651 complements proposal 107. [Bugfix on 0.1.2.x]
23652 - Directory authorities now never mark more than 3 servers per IP as
23653 Valid and Running. (Implements proposal 109, by Kevin Bauer and
23655 - Minor change to organizationName and commonName generation
23656 procedures in TLS certificates during Tor handshakes, to invalidate
23657 some earlier censorware approaches. This is not a long-term
23658 solution, but applying it will give us a bit of time to look into
23659 the epidemiology of countermeasures as they spread.
23661 o Major bugfixes (directory):
23662 - Rewrite directory tokenization code to never run off the end of
23663 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
23665 o Minor features (controller):
23666 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
23667 match requests to applications. (Patch from Robert Hogan.)
23668 - Report address and port correctly on connections to DNSPort. (Patch
23669 from Robert Hogan.)
23670 - Add a RESOLVE command to launch hostname lookups. (Original patch
23671 from Robert Hogan.)
23672 - Add GETINFO status/enough-dir-info to let controllers tell whether
23673 Tor has downloaded sufficient directory information. (Patch
23675 - You can now use the ControlSocket option to tell Tor to listen for
23676 controller connections on Unix domain sockets on systems that
23677 support them. (Patch from Peter Palfrader.)
23678 - STREAM NEW events are generated for DNSPort requests and for
23679 tunneled directory connections. (Patch from Robert Hogan.)
23680 - New "GETINFO address-mappings/*" command to get address mappings
23681 with expiry information. "addr-mappings/*" is now deprecated.
23684 o Minor features (misc):
23685 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
23687 - The tor-gencert tool for v3 directory authorities now creates all
23688 files as readable to the file creator only, and write-protects
23689 the authority identity key.
23690 - When dumping memory usage, list bytes used in buffer memory
23692 - When running with dmalloc, dump more stats on hup and on exit.
23693 - Directory authorities now fail quickly and (relatively) harmlessly
23694 if they generate a network status document that is somehow
23697 o Traffic load balancing improvements:
23698 - If exit bandwidth ever exceeds one third of total bandwidth, then
23699 use the correct formula to weight exit nodes when choosing paths.
23700 (Based on patch from Mike Perry.)
23701 - Choose perfectly fairly among routers when choosing by bandwidth and
23702 weighting by fraction of bandwidth provided by exits. Previously, we
23703 would choose with only approximate fairness, and correct ourselves
23704 if we ran off the end of the list. [Bugfix on 0.1.2.x]
23706 o Performance improvements:
23707 - Be more aggressive with freeing buffer RAM or putting it on the
23709 - Use Critical Sections rather than Mutexes for synchronizing threads
23710 on win32; Mutexes are heavier-weight, and designed for synchronizing
23713 o Deprecated and removed features:
23714 - RedirectExits is now deprecated.
23715 - Stop allowing address masks that do not correspond to bit prefixes.
23716 We have warned about these for a really long time; now it's time
23717 to reject them. (Patch from croup.)
23719 o Minor bugfixes (directory):
23720 - Fix another crash bug related to extra-info caching. (Bug found by
23721 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
23722 - Directories no longer return a "304 not modified" when they don't
23723 have the networkstatus the client asked for. Also fix a memory
23724 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
23725 - We had accidentally labelled 0.1.2.x directory servers as not
23726 suitable for begin_dir requests, and had labelled no directory
23727 servers as suitable for uploading extra-info documents. [Bugfix
23730 o Minor bugfixes (dns):
23731 - Fix a crash when DNSPort is set more than once. (Patch from Robert
23732 Hogan.) [Bugfix on 0.2.0.2-alpha]
23733 - Add DNSPort connections to the global connection list, so that we
23734 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
23736 - Fix a dangling reference that could lead to a crash when DNSPort is
23737 changed or closed (Patch from Robert Hogan.) [Bugfix on
23740 o Minor bugfixes (controller):
23741 - Provide DNS expiry times in GMT, not in local time. For backward
23742 compatibility, ADDRMAP events only provide GMT expiry in an extended
23743 field. "GETINFO address-mappings" always does the right thing.
23744 - Use CRLF line endings properly in NS events.
23745 - Terminate multi-line control events properly. (Original patch
23746 from tup.) [Bugfix on 0.1.2.x-alpha]
23747 - Do not include spaces in SOURCE_ADDR fields in STREAM
23748 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
23751 Changes in version 0.1.2.15 - 2007-07-17
23752 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
23753 problems, fixes compilation on BSD, and fixes a variety of other
23754 bugs. Everybody should upgrade.
23756 o Major bugfixes (compilation):
23757 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
23759 o Major bugfixes (crashes):
23760 - Try even harder not to dereference the first character after
23761 an mmap(). Reported by lodger.
23762 - Fix a crash bug in directory authorities when we re-number the
23763 routerlist while inserting a new router.
23764 - When the cached-routers file is an even multiple of the page size,
23765 don't run off the end and crash. (Fixes bug 455; based on idea
23767 - Fix eventdns.c behavior on Solaris: It is critical to include
23768 orconfig.h _before_ sys/types.h, so that we can get the expected
23769 definition of _FILE_OFFSET_BITS.
23771 o Major bugfixes (security):
23772 - Fix a possible buffer overrun when using BSD natd support. Bug
23774 - When sending destroy cells from a circuit's origin, don't include
23775 the reason for tearing down the circuit. The spec says we didn't,
23776 and now we actually don't. Reported by lodger.
23777 - Keep streamids from different exits on a circuit separate. This
23778 bug may have allowed other routers on a given circuit to inject
23779 cells into streams. Reported by lodger; fixes bug 446.
23780 - If there's a never-before-connected-to guard node in our list,
23781 never choose any guards past it. This way we don't expand our
23782 guard list unless we need to.
23784 o Minor bugfixes (guard nodes):
23785 - Weight guard selection by bandwidth, so that low-bandwidth nodes
23786 don't get overused as guards.
23788 o Minor bugfixes (directory):
23789 - Correctly count the number of authorities that recommend each
23790 version. Previously, we were under-counting by 1.
23791 - Fix a potential crash bug when we load many server descriptors at
23792 once and some of them make others of them obsolete. Fixes bug 458.
23794 o Minor bugfixes (hidden services):
23795 - Stop tearing down the whole circuit when the user asks for a
23796 connection to a port that the hidden service didn't configure.
23799 o Minor bugfixes (misc):
23800 - On Windows, we were preventing other processes from reading
23801 cached-routers while Tor was running. Reported by janbar.
23802 - Fix a possible (but very unlikely) bug in picking routers by
23803 bandwidth. Add a log message to confirm that it is in fact
23804 unlikely. Patch from lodger.
23805 - Backport a couple of memory leak fixes.
23806 - Backport miscellaneous cosmetic bugfixes.
23809 Changes in version 0.2.0.2-alpha - 2007-06-02
23810 o Major bugfixes on 0.2.0.1-alpha:
23811 - Fix an assertion failure related to servers without extra-info digests.
23812 Resolves bugs 441 and 442.
23814 o Minor features (directory):
23815 - Support "If-Modified-Since" when answering HTTP requests for
23816 directories, running-routers documents, and network-status documents.
23817 (There's no need to support it for router descriptors, since those
23818 are downloaded by descriptor digest.)
23820 o Minor build issues:
23821 - Clear up some MIPSPro compiler warnings.
23822 - When building from a tarball on a machine that happens to have SVK
23823 installed, report the micro-revision as whatever version existed
23824 in the tarball, not as "x".
23827 Changes in version 0.2.0.1-alpha - 2007-06-01
23828 This early development snapshot provides new features for people running
23829 Tor as both a client and a server (check out the new RelayBandwidth
23830 config options); lets Tor run as a DNS proxy; and generally moves us
23831 forward on a lot of fronts.
23833 o Major features, server usability:
23834 - New config options RelayBandwidthRate and RelayBandwidthBurst:
23835 a separate set of token buckets for relayed traffic. Right now
23836 relayed traffic is defined as answers to directory requests, and
23837 OR connections that don't have any local circuits on them.
23839 o Major features, client usability:
23840 - A client-side DNS proxy feature to replace the need for
23841 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
23842 for DNS requests on port 9999, use the Tor network to resolve them
23843 anonymously, and send the reply back like a regular DNS server.
23844 The code still only implements a subset of DNS.
23845 - Make PreferTunneledDirConns and TunnelDirConns work even when
23846 we have no cached directory info. This means Tor clients can now
23847 do all of their connections protected by TLS.
23849 o Major features, performance and efficiency:
23850 - Directory authorities accept and serve "extra info" documents for
23851 routers. These documents contain fields from router descriptors
23852 that aren't usually needed, and that use a lot of excess
23853 bandwidth. Once these fields are removed from router descriptors,
23854 the bandwidth savings should be about 60%. [Partially implements
23856 - Servers upload extra-info documents to any authority that accepts
23857 them. Authorities (and caches that have been configured to download
23858 extra-info documents) download them as needed. [Partially implements
23860 - Change the way that Tor buffers data that it is waiting to write.
23861 Instead of queueing data cells in an enormous ring buffer for each
23862 client->OR or OR->OR connection, we now queue cells on a separate
23863 queue for each circuit. This lets us use less slack memory, and
23864 will eventually let us be smarter about prioritizing different kinds
23866 - Use memory pools to allocate cells with better speed and memory
23867 efficiency, especially on platforms where malloc() is inefficient.
23868 - Stop reading on edge connections when their corresponding circuit
23869 buffers are full; start again as the circuits empty out.
23871 o Major features, other:
23872 - Add an HSAuthorityRecordStats option that hidden service authorities
23873 can use to track statistics of overall hidden service usage without
23874 logging information that would be very useful to an attacker.
23875 - Start work implementing multi-level keys for directory authorities:
23876 Add a standalone tool to generate key certificates. (Proposal 103.)
23879 - Directory authorities now call routers Stable if they have an
23880 uptime of at least 30 days, even if that's not the median uptime
23881 in the network. Implements proposal 107, suggested by Kevin Bauer
23884 o Minor fixes (resource management):
23885 - Count the number of open sockets separately from the number
23886 of active connection_t objects. This will let us avoid underusing
23887 our allocated connection limit.
23888 - We no longer use socket pairs to link an edge connection to an
23889 anonymous directory connection or a DirPort test connection.
23890 Instead, we track the link internally and transfer the data
23891 in-process. This saves two sockets per "linked" connection (at the
23892 client and at the server), and avoids the nasty Windows socketpair()
23894 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
23895 for every single inactive connection_t. Free items from the
23896 4k/16k-buffer free lists when they haven't been used for a while.
23898 o Minor features (build):
23899 - Make autoconf search for libevent, openssl, and zlib consistently.
23900 - Update deprecated macros in configure.in.
23901 - When warning about missing headers, tell the user to let us
23902 know if the compile succeeds anyway, so we can downgrade the
23904 - Include the current subversion revision as part of the version
23905 string: either fetch it directly if we're in an SVN checkout, do
23906 some magic to guess it if we're in an SVK checkout, or use
23907 the last-detected version if we're building from a .tar.gz.
23908 Use this version consistently in log messages.
23910 o Minor features (logging):
23911 - Always prepend "Bug: " to any log message about a bug.
23912 - Put a platform string (e.g. "Linux i686") in the startup log
23913 message, so when people paste just their logs, we know if it's
23914 OpenBSD or Windows or what.
23915 - When logging memory usage, break down memory used in buffers by
23918 o Minor features (directory system):
23919 - New config option V2AuthoritativeDirectory that all directory
23920 authorities should set. This will let future authorities choose
23921 not to serve V2 directory information.
23922 - Directory authorities allow multiple router descriptors and/or extra
23923 info documents to be uploaded in a single go. This will make
23924 implementing proposal 104 simpler.
23926 o Minor features (controller):
23927 - Add a new config option __DisablePredictedCircuits designed for
23928 use by the controller, when we don't want Tor to build any circuits
23930 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
23931 so we can exit from the middle of the circuit.
23932 - Implement "getinfo status/circuit-established".
23933 - Implement "getinfo status/version/..." so a controller can tell
23934 whether the current version is recommended, and whether any versions
23935 are good, and how many authorities agree. (Patch from shibz.)
23937 o Minor features (hidden services):
23938 - Allow multiple HiddenServicePort directives with the same virtual
23939 port; when they occur, the user is sent round-robin to one
23940 of the target ports chosen at random. Partially fixes bug 393 by
23941 adding limited ad-hoc round-robining.
23943 o Minor features (other):
23945 - Add a new AutomapHostsOnResolve option: when it is enabled, any
23946 resolve request for hosts matching a given pattern causes Tor to
23947 generate an internal virtual address mapping for that host. This
23948 allows DNSPort to work sensibly with hidden service users. By
23949 default, .exit and .onion addresses are remapped; the list of
23950 patterns can be reconfigured with AutomapHostsSuffixes.
23951 - Add an "-F" option to tor-resolve to force a resolve for a .onion
23952 address. Thanks to the AutomapHostsOnResolve option, this is no
23953 longer a completely silly thing to do.
23954 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
23955 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
23956 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
23957 minus 1 byte: the actual maximum declared bandwidth.
23959 o Removed features:
23960 - Removed support for the old binary "version 0" controller protocol.
23961 This has been deprecated since 0.1.1, and warnings have been issued
23962 since 0.1.2. When we encounter a v0 control message, we now send
23963 back an error and close the connection.
23964 - Remove the old "dns worker" server DNS code: it hasn't been default
23965 since 0.1.2.2-alpha, and all the servers seem to be using the new
23968 o Minor bugfixes (portability):
23969 - Even though Windows is equally happy with / and \ as path separators,
23970 try to use \ consistently on Windows and / consistently on Unix: it
23971 makes the log messages nicer.
23972 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
23973 - Read resolv.conf files correctly on platforms where read() returns
23974 partial results on small file reads.
23976 o Minor bugfixes (directory):
23977 - Correctly enforce that elements of directory objects do not appear
23978 more often than they are allowed to appear.
23979 - When we are reporting the DirServer line we just parsed, we were
23980 logging the second stanza of the key fingerprint, not the first.
23982 o Minor bugfixes (logging):
23983 - When we hit an EOF on a log (probably because we're shutting down),
23984 don't try to remove the log from the list: just mark it as
23985 unusable. (Bulletproofs against bug 222.)
23987 o Minor bugfixes (other):
23988 - In the exitlist script, only consider the most recently published
23989 server descriptor for each server. Also, when the user requests
23990 a list of servers that _reject_ connections to a given address,
23991 explicitly exclude the IPs that also have servers that accept
23992 connections to that address. (Resolves bug 405.)
23993 - Stop allowing hibernating servers to be "stable" or "fast".
23994 - On Windows, we were preventing other processes from reading
23995 cached-routers while Tor was running. (Reported by janbar)
23996 - Make the NodeFamilies config option work. (Reported by
23997 lodger -- it has never actually worked, even though we added it
23999 - Check return values from pthread_mutex functions.
24000 - Don't save non-general-purpose router descriptors to the disk cache,
24001 because we have no way of remembering what their purpose was when
24003 - Add even more asserts to hunt down bug 417.
24004 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
24005 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
24006 Add a log message to confirm that it is in fact unlikely.
24008 o Minor bugfixes (controller):
24009 - Make 'getinfo fingerprint' return a 551 error if we're not a
24010 server, so we match what the control spec claims we do. Reported
24012 - Fix a typo in an error message when extendcircuit fails that
24013 caused us to not follow the \r\n-based delimiter protocol. Reported
24016 o Code simplifications and refactoring:
24017 - Stop passing around circuit_t and crypt_path_t pointers that are
24018 implicit in other procedure arguments.
24019 - Drop the old code to choke directory connections when the
24020 corresponding OR connections got full: thanks to the cell queue
24021 feature, OR conns don't get full any more.
24022 - Make dns_resolve() handle attaching connections to circuits
24023 properly, so the caller doesn't have to.
24024 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
24025 - Keep the connection array as a dynamic smartlist_t, rather than as
24026 a fixed-sized array. This is important, as the number of connections
24027 is becoming increasingly decoupled from the number of sockets.
24030 Changes in version 0.1.2.14 - 2007-05-25
24031 Tor 0.1.2.14 changes the addresses of two directory authorities (this
24032 change especially affects those who serve or use hidden services),
24033 and fixes several other crash- and security-related bugs.
24035 o Directory authority changes:
24036 - Two directory authorities (moria1 and moria2) just moved to new
24037 IP addresses. This change will particularly affect those who serve
24038 or use hidden services.
24040 o Major bugfixes (crashes):
24041 - If a directory server runs out of space in the connection table
24042 as it's processing a begin_dir request, it will free the exit stream
24043 but leave it attached to the circuit, leading to unpredictable
24044 behavior. (Reported by seeess, fixes bug 425.)
24045 - Fix a bug in dirserv_remove_invalid() that would cause authorities
24046 to corrupt memory under some really unlikely scenarios.
24047 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
24048 - Avoid segfaults when reading from mmaped descriptor file. (Reported
24051 o Major bugfixes (security):
24052 - When choosing an entry guard for a circuit, avoid using guards
24053 that are in the same family as the chosen exit -- not just guards
24054 that are exactly the chosen exit. (Reported by lodger.)
24056 o Major bugfixes (resource management):
24057 - If a directory authority is down, skip it when deciding where to get
24058 networkstatus objects or descriptors. Otherwise we keep asking
24059 every 10 seconds forever. Fixes bug 384.
24060 - Count it as a failure if we fetch a valid network-status but we
24061 don't want to keep it. Otherwise we'll keep fetching it and keep
24062 not wanting to keep it. Fixes part of bug 422.
24063 - If all of our dirservers have given us bad or no networkstatuses
24064 lately, then stop hammering them once per minute even when we
24065 think they're failed. Fixes another part of bug 422.
24068 - Actually set the purpose correctly for descriptors inserted with
24069 purpose=controller.
24070 - When we have k non-v2 authorities in our DirServer config,
24071 we ignored the last k authorities in the list when updating our
24073 - Correctly back-off from requesting router descriptors that we are
24074 having a hard time downloading.
24075 - Read resolv.conf files correctly on platforms where read() returns
24076 partial results on small file reads.
24077 - Don't rebuild the entire router store every time we get 32K of
24078 routers: rebuild it when the journal gets very large, or when
24079 the gaps in the store get very large.
24082 - When routers publish SVN revisions in their router descriptors,
24083 authorities now include those versions correctly in networkstatus
24085 - Warn when using a version of libevent before 1.3b to run a server on
24086 OSX or BSD: these versions interact badly with userspace threads.
24089 Changes in version 0.1.2.13 - 2007-04-24
24090 This release features some major anonymity fixes, such as safer path
24091 selection; better client performance; faster bootstrapping, better
24092 address detection, and better DNS support for servers; write limiting as
24093 well as read limiting to make servers easier to run; and a huge pile of
24094 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
24096 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
24097 of the Freenode IRC network, remembering his patience and vision for
24098 free speech on the Internet.
24101 - Fix a memory leak when we ask for "all" networkstatuses and we
24102 get one we don't recognize.
24103 - Add more asserts to hunt down bug 417.
24104 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
24107 Changes in version 0.1.2.12-rc - 2007-03-16
24109 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
24110 directory information requested inside Tor connections (i.e. via
24111 begin_dir cells). It only triggered when the same connection was
24112 serving other data at the same time. Reported by seeess.
24115 - When creating a circuit via the controller, send a 'launched'
24116 event when we're done, so we follow the spec better.
24119 Changes in version 0.1.2.11-rc - 2007-03-15
24120 o Minor bugfixes (controller), reported by daejees:
24121 - Correct the control spec to match how the code actually responds
24122 to 'getinfo addr-mappings/*'.
24123 - The control spec described a GUARDS event, but the code
24124 implemented a GUARD event. Standardize on GUARD, but let people
24125 ask for GUARDS too.
24128 Changes in version 0.1.2.10-rc - 2007-03-07
24129 o Major bugfixes (Windows):
24130 - Do not load the NT services library functions (which may not exist)
24131 just to detect if we're a service trying to shut down. Now we run
24132 on Win98 and friends again.
24134 o Minor bugfixes (other):
24135 - Clarify a couple of log messages.
24136 - Fix a misleading socks5 error number.
24139 Changes in version 0.1.2.9-rc - 2007-03-02
24140 o Major bugfixes (Windows):
24141 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
24142 of the usual GCC "%llu". This prevents a bug when saving 64-bit
24143 int configuration values: the high-order 32 bits would get
24144 truncated. In particular, we were being bitten by the default
24145 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
24146 and maybe also bug 397.)
24148 o Minor bugfixes (performance):
24149 - Use OpenSSL's AES implementation on platforms where it's faster.
24150 This could save us as much as 10% CPU usage.
24152 o Minor bugfixes (server):
24153 - Do not rotate onion key immediately after setting it for the first
24156 o Minor bugfixes (directory authorities):
24157 - Stop calling servers that have been hibernating for a long time
24158 "stable". Also, stop letting hibernating or obsolete servers affect
24159 uptime and bandwidth cutoffs.
24160 - Stop listing hibernating servers in the v1 directory.
24162 o Minor bugfixes (hidden services):
24163 - Upload hidden service descriptors slightly less often, to reduce
24164 load on authorities.
24166 o Minor bugfixes (other):
24167 - Fix an assert that could trigger if a controller quickly set then
24168 cleared EntryNodes. Bug found by Udo van den Heuvel.
24169 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
24171 - Fix a potential race condition in the rpm installer. Found by
24173 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
24174 of 2 as indicating that the server is completely bad; it sometimes
24175 means that the server is just bad for the request in question. (may fix
24176 the last of bug 326.)
24177 - Disable encrypted directory connections when we don't have a server
24178 descriptor for the destination. We'll get this working again in
24182 Changes in version 0.1.2.8-beta - 2007-02-26
24183 o Major bugfixes (crashes):
24184 - Stop crashing when the controller asks us to resetconf more than
24185 one config option at once. (Vidalia 0.0.11 does this.)
24186 - Fix a crash that happened on Win98 when we're given command-line
24187 arguments: don't try to load NT service functions from advapi32.dll
24188 except when we need them. (Bug introduced in 0.1.2.7-alpha;
24190 - Fix a longstanding obscure crash bug that could occur when
24191 we run out of DNS worker processes. (Resolves bug 390.)
24193 o Major bugfixes (hidden services):
24194 - Correctly detect whether hidden service descriptor downloads are
24195 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
24197 o Major bugfixes (accounting):
24198 - When we start during an accounting interval before it's time to wake
24199 up, remember to wake up at the correct time. (May fix bug 342.)
24201 o Minor bugfixes (controller):
24202 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
24203 clear the corresponding on_circuit variable, and remember later
24204 that we don't need to send a redundant CLOSED event. Resolves part
24206 - Report events where a resolve succeeded or where we got a socks
24207 protocol error correctly, rather than calling both of them
24209 - Change reported stream target addresses to IP consistently when
24210 we finally get the IP from an exit node.
24211 - Send log messages to the controller even if they happen to be very
24214 o Minor bugfixes (other):
24215 - Display correct results when reporting which versions are
24216 recommended, and how recommended they are. (Resolves bug 383.)
24217 - Improve our estimates for directory bandwidth to be less random:
24218 guess that an unrecognized directory will have the average bandwidth
24219 from all known directories, not that it will have the average
24220 bandwidth from those directories earlier than it on the list.
24221 - If we start a server with ClientOnly 1, then set ClientOnly to 0
24222 and hup, stop triggering an assert based on an empty onion_key.
24223 - On platforms with no working mmap() equivalent, don't warn the
24224 user when cached-routers doesn't exist.
24225 - Warn the user when mmap() [or its equivalent] fails for some reason
24226 other than file-not-found.
24227 - Don't warn the user when cached-routers.new doesn't exist: that's
24228 perfectly fine when starting up for the first time.
24229 - When EntryNodes are configured, rebuild the guard list to contain,
24230 in order: the EntryNodes that were guards before; the rest of the
24231 EntryNodes; the nodes that were guards before.
24232 - Mask out all signals in sub-threads; only the libevent signal
24233 handler should be processing them. This should prevent some crashes
24234 on some machines using pthreads. (Patch from coderman.)
24235 - Fix switched arguments on memset in the implementation of
24236 tor_munmap() for systems with no mmap() call.
24237 - When Tor receives a router descriptor that it asked for, but
24238 no longer wants (because it has received fresh networkstatuses
24239 in the meantime), do not warn the user. Cache the descriptor if
24240 we're a cache; drop it if we aren't.
24241 - Make earlier entry guards _really_ get retried when the network
24243 - On a malformed DNS reply, always give an error to the corresponding
24245 - Build with recent libevents on platforms that do not define the
24246 nonstandard types "u_int8_t" and friends.
24248 o Minor features (controller):
24249 - Warn the user when an application uses the obsolete binary v0
24250 control protocol. We're planning to remove support for it during
24251 the next development series, so it's good to give people some
24253 - Add STREAM_BW events to report per-entry-stream bandwidth
24254 use. (Patch from Robert Hogan.)
24255 - Rate-limit SIGNEWNYM signals in response to controllers that
24256 impolitely generate them for every single stream. (Patch from
24257 mwenge; closes bug 394.)
24258 - Make REMAP stream events have a SOURCE (cache or exit), and
24259 make them generated in every case where we get a successful
24260 connected or resolved cell.
24262 o Minor bugfixes (performance):
24263 - Call router_have_min_dir_info half as often. (This is showing up in
24264 some profiles, but not others.)
24265 - When using GCC, make log_debug never get called at all, and its
24266 arguments never get evaluated, when no debug logs are configured.
24267 (This is showing up in some profiles, but not others.)
24270 - Remove some never-implemented options. Mark PathlenCoinWeight as
24272 - Implement proposal 106: Stop requiring clients to have well-formed
24273 certificates; stop checking nicknames in certificates. (Clients
24274 have certificates so that they can look like Tor servers, but in
24275 the future we might want to allow them to look like regular TLS
24276 clients instead. Nicknames in certificates serve no purpose other
24277 than making our protocol easier to recognize on the wire.)
24278 - Revise messages on handshake failure again to be even more clear about
24279 which are incoming connections and which are outgoing.
24280 - Discard any v1 directory info that's over 1 month old (for
24281 directories) or over 1 week old (for running-routers lists).
24282 - Do not warn when individual nodes in the configuration's EntryNodes,
24283 ExitNodes, etc are down: warn only when all possible nodes
24284 are down. (Fixes bug 348.)
24285 - Always remove expired routers and networkstatus docs before checking
24286 whether we have enough information to build circuits. (Fixes
24288 - Put a lower-bound on MaxAdvertisedBandwidth.
24291 Changes in version 0.1.2.7-alpha - 2007-02-06
24292 o Major bugfixes (rate limiting):
24293 - Servers decline directory requests much more aggressively when
24294 they're low on bandwidth. Otherwise they end up queueing more and
24295 more directory responses, which can't be good for latency.
24296 - But never refuse directory requests from local addresses.
24297 - Fix a memory leak when sending a 503 response for a networkstatus
24299 - Be willing to read or write on local connections (e.g. controller
24300 connections) even when the global rate limiting buckets are empty.
24301 - If our system clock jumps back in time, don't publish a negative
24302 uptime in the descriptor. Also, don't let the global rate limiting
24303 buckets go absurdly negative.
24304 - Flush local controller connection buffers periodically as we're
24305 writing to them, so we avoid queueing 4+ megabytes of data before
24308 o Major bugfixes (NT services):
24309 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
24310 command-line flag so that admins can override the default by saying
24311 "tor --service install --user "SomeUser"". This will not affect
24312 existing installed services. Also, warn the user that the service
24313 will look for its configuration file in the service user's
24314 %appdata% directory. (We can't do the 'hardwire the user's appdata
24315 directory' trick any more, since we may not have read access to that
24318 o Major bugfixes (other):
24319 - Previously, we would cache up to 16 old networkstatus documents
24320 indefinitely, if they came from nontrusted authorities. Now we
24321 discard them if they are more than 10 days old.
24322 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
24324 - Detect and reject malformed DNS responses containing circular
24326 - If exits are rare enough that we're not marking exits as guards,
24327 ignore exit bandwidth when we're deciding the required bandwidth
24329 - When we're handling a directory connection tunneled over Tor,
24330 don't fill up internal memory buffers with all the data we want
24331 to tunnel; instead, only add it if the OR connection that will
24332 eventually receive it has some room for it. (This can lead to
24333 slowdowns in tunneled dir connections; a better solution will have
24334 to wait for 0.2.0.)
24336 o Minor bugfixes (dns):
24337 - Add some defensive programming to eventdns.c in an attempt to catch
24338 possible memory-stomping bugs.
24339 - Detect and reject DNS replies containing IPv4 or IPv6 records with
24340 an incorrect number of bytes. (Previously, we would ignore the
24342 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
24343 in the correct order, and doesn't crash.
24344 - Free memory held in recently-completed DNS lookup attempts on exit.
24345 This was not a memory leak, but may have been hiding memory leaks.
24346 - Handle TTL values correctly on reverse DNS lookups.
24347 - Treat failure to parse resolv.conf as an error.
24349 o Minor bugfixes (other):
24350 - Fix crash with "tor --list-fingerprint" (reported by seeess).
24351 - When computing clock skew from directory HTTP headers, consider what
24352 time it was when we finished asking for the directory, not what
24354 - Expire socks connections if they spend too long waiting for the
24355 handshake to finish. Previously we would let them sit around for
24356 days, if the connecting application didn't close them either.
24357 - And if the socks handshake hasn't started, don't send a
24358 "DNS resolve socks failed" handshake reply; just close it.
24359 - Stop using C functions that OpenBSD's linker doesn't like.
24360 - Don't launch requests for descriptors unless we have networkstatuses
24361 from at least half of the authorities. This delays the first
24362 download slightly under pathological circumstances, but can prevent
24363 us from downloading a bunch of descriptors we don't need.
24364 - Do not log IPs with TLS failures for incoming TLS
24365 connections. (Fixes bug 382.)
24366 - If the user asks to use invalid exit nodes, be willing to use
24368 - Stop using the reserved ac_cv namespace in our configure script.
24369 - Call stat() slightly less often; use fstat() when possible.
24370 - Refactor the way we handle pending circuits when an OR connection
24371 completes or fails, in an attempt to fix a rare crash bug.
24372 - Only rewrite a conn's address based on X-Forwarded-For: headers
24373 if it's a parseable public IP address; and stop adding extra quotes
24374 to the resulting address.
24377 - Weight directory requests by advertised bandwidth. Now we can
24378 let servers enable write limiting but still allow most clients to
24379 succeed at their directory requests. (We still ignore weights when
24380 choosing a directory authority; I hope this is a feature.)
24383 - Create a new file ReleaseNotes which was the old ChangeLog. The
24384 new ChangeLog file now includes the summaries for all development
24386 - Check for addresses with invalid characters at the exit as well
24387 as at the client, and warn less verbosely when they fail. You can
24388 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
24389 - Adapt a patch from goodell to let the contrib/exitlist script
24390 take arguments rather than require direct editing.
24391 - Inform the server operator when we decide not to advertise a
24392 DirPort due to AccountingMax enabled or a low BandwidthRate. It
24393 was confusing Zax, so now we're hopefully more helpful.
24394 - Bring us one step closer to being able to establish an encrypted
24395 directory tunnel without knowing a descriptor first. Still not
24396 ready yet. As part of the change, now assume we can use a
24397 create_fast cell if we don't know anything about a router.
24398 - Allow exit nodes to use nameservers running on ports other than 53.
24399 - Servers now cache reverse DNS replies.
24400 - Add an --ignore-missing-torrc command-line option so that we can
24401 get the "use sensible defaults if the configuration file doesn't
24402 exist" behavior even when specifying a torrc location on the command
24405 o Minor features (controller):
24406 - Track reasons for OR connection failure; make these reasons
24407 available via the controller interface. (Patch from Mike Perry.)
24408 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
24409 can learn when clients are sending malformed hostnames to Tor.
24410 - Clean up documentation for controller status events.
24411 - Add a REMAP status to stream events to note that a stream's
24412 address has changed because of a cached address or a MapAddress
24416 Changes in version 0.1.2.6-alpha - 2007-01-09
24418 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
24419 connection handles more than 4 gigs in either direction, we crash.
24420 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
24421 advertised exit node, somebody might try to exit from us when
24422 we're bootstrapping and before we've built our descriptor yet.
24423 Refuse the connection rather than crashing.
24426 - Warn if we (as a server) find that we've resolved an address that we
24427 weren't planning to resolve.
24428 - Warn that using select() on any libevent version before 1.1 will be
24429 unnecessarily slow (even for select()).
24430 - Flush ERR-level controller status events just like we currently
24431 flush ERR-level log events, so that a Tor shutdown doesn't prevent
24432 the controller from learning about current events.
24434 o Minor features (more controller status events):
24435 - Implement EXTERNAL_ADDRESS server status event so controllers can
24436 learn when our address changes.
24437 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
24438 can learn when directories reject our descriptor.
24439 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
24440 can learn when a client application is speaking a non-socks protocol
24442 - Implement DANGEROUS_SOCKS client status event so controllers
24443 can learn when a client application is leaking DNS addresses.
24444 - Implement BUG general status event so controllers can learn when
24445 Tor is unhappy about its internal invariants.
24446 - Implement CLOCK_SKEW general status event so controllers can learn
24447 when Tor thinks the system clock is set incorrectly.
24448 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
24449 server status events so controllers can learn when their descriptors
24450 are accepted by a directory.
24451 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
24452 server status events so controllers can learn about Tor's progress in
24453 deciding whether it's reachable from the outside.
24454 - Implement BAD_LIBEVENT general status event so controllers can learn
24455 when we have a version/method combination in libevent that needs to
24457 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
24458 and DNS_USELESS server status events so controllers can learn
24459 about changes to DNS server status.
24461 o Minor features (directory):
24462 - Authorities no longer recommend exits as guards if this would shift
24463 too much load to the exit nodes.
24466 Changes in version 0.1.2.5-alpha - 2007-01-06
24468 - Enable write limiting as well as read limiting. Now we sacrifice
24469 capacity if we're pushing out lots of directory traffic, rather
24470 than overrunning the user's intended bandwidth limits.
24471 - Include TLS overhead when counting bandwidth usage; previously, we
24472 would count only the bytes sent over TLS, but not the bytes used
24474 - Support running the Tor service with a torrc not in the same
24475 directory as tor.exe and default to using the torrc located in
24476 the %appdata%\Tor\ of the user who installed the service. Patch
24478 - Servers now check for the case when common DNS requests are going to
24479 wildcarded addresses (i.e. all getting the same answer), and change
24480 their exit policy to reject *:* if it's happening.
24481 - Implement BEGIN_DIR cells, so we can connect to the directory
24482 server via TLS to do encrypted directory requests rather than
24483 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
24484 config options if you like.
24486 o Minor features (config and docs):
24487 - Start using the state file to store bandwidth accounting data:
24488 the bw_accounting file is now obsolete. We'll keep generating it
24489 for a while for people who are still using 0.1.2.4-alpha.
24490 - Try to batch changes to the state file so that we do as few
24491 disk writes as possible while still storing important things in
24493 - The state file and the bw_accounting file get saved less often when
24494 the AvoidDiskWrites config option is set.
24495 - Make PIDFile work on Windows (untested).
24496 - Add internal descriptions for a bunch of configuration options:
24497 accessible via controller interface and in comments in saved
24499 - Reject *:563 (NNTPS) in the default exit policy. We already reject
24500 NNTP by default, so this seems like a sensible addition.
24501 - Clients now reject hostnames with invalid characters. This should
24502 avoid some inadvertent info leaks. Add an option
24503 AllowNonRFC953Hostnames to disable this behavior, in case somebody
24504 is running a private network with hosts called @, !, and #.
24505 - Add a maintainer script to tell us which options are missing
24506 documentation: "make check-docs".
24507 - Add a new address-spec.txt document to describe our special-case
24508 addresses: .exit, .onion, and .noconnnect.
24510 o Minor features (DNS):
24511 - Ongoing work on eventdns infrastructure: now it has dns server
24512 and ipv6 support. One day Tor will make use of it.
24513 - Add client-side caching for reverse DNS lookups.
24514 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
24515 - When we change nameservers or IP addresses, reset and re-launch
24516 our tests for DNS hijacking.
24518 o Minor features (directory):
24519 - Authorities now specify server versions in networkstatus. This adds
24520 about 2% to the size of compressed networkstatus docs, and allows
24521 clients to tell which servers support BEGIN_DIR and which don't.
24522 The implementation is forward-compatible with a proposed future
24523 protocol version scheme not tied to Tor versions.
24524 - DirServer configuration lines now have an orport= option so
24525 clients can open encrypted tunnels to the authorities without
24526 having downloaded their descriptors yet. Enabled for moria1,
24527 moria2, tor26, and lefkada now in the default configuration.
24528 - Directory servers are more willing to send a 503 "busy" if they
24529 are near their write limit, especially for v1 directory requests.
24530 Now they can use their limited bandwidth for actual Tor traffic.
24531 - Clients track responses with status 503 from dirservers. After a
24532 dirserver has given us a 503, we try not to use it until an hour has
24533 gone by, or until we have no dirservers that haven't given us a 503.
24534 - When we get a 503 from a directory, and we're not a server, we don't
24535 count the failure against the total number of failures allowed
24536 for the thing we're trying to download.
24537 - Report X-Your-Address-Is correctly from tunneled directory
24538 connections; don't report X-Your-Address-Is when it's an internal
24539 address; and never believe reported remote addresses when they're
24541 - Protect against an unlikely DoS attack on directory servers.
24542 - Add a BadDirectory flag to network status docs so that authorities
24543 can (eventually) tell clients about caches they believe to be
24546 o Minor features (controller):
24547 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
24548 - Reimplement GETINFO so that info/names stays in sync with the
24550 - Implement "GETINFO fingerprint".
24551 - Implement "SETEVENTS GUARD" so controllers can get updates on
24552 entry guard status as it changes.
24554 o Minor features (clean up obsolete pieces):
24555 - Remove some options that have been deprecated since at least
24556 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
24557 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
24558 to set log options.
24559 - We no longer look for identity and onion keys in "identity.key" and
24560 "onion.key" -- these were replaced by secret_id_key and
24561 secret_onion_key in 0.0.8pre1.
24562 - We no longer require unrecognized directory entries to be
24565 o Major bugfixes (security):
24566 - Stop sending the HttpProxyAuthenticator string to directory
24567 servers when directory connections are tunnelled through Tor.
24568 - Clients no longer store bandwidth history in the state file.
24569 - Do not log introduction points for hidden services if SafeLogging
24571 - When generating bandwidth history, round down to the nearest
24572 1k. When storing accounting data, round up to the nearest 1k.
24573 - When we're running as a server, remember when we last rotated onion
24574 keys, so that we will rotate keys once they're a week old even if
24575 we never stay up for a week ourselves.
24577 o Major bugfixes (other):
24578 - Fix a longstanding bug in eventdns that prevented the count of
24579 timed-out resolves from ever being reset. This bug caused us to
24580 give up on a nameserver the third time it timed out, and try it
24581 10 seconds later... and to give up on it every time it timed out
24583 - Take out the '5 second' timeout from the connection retry
24584 schedule. Now the first connect attempt will wait a full 10
24585 seconds before switching to a new circuit. Perhaps this will help
24586 a lot. Based on observations from Mike Perry.
24587 - Fix a bug on the Windows implementation of tor_mmap_file() that
24588 would prevent the cached-routers file from ever loading. Reported
24592 - Fix an assert failure when a directory authority sets
24593 AuthDirRejectUnlisted and then receives a descriptor from an
24594 unlisted router. Reported by seeess.
24595 - Avoid a double-free when parsing malformed DirServer lines.
24596 - Fix a bug when a BSD-style PF socket is first used. Patch from
24598 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
24599 to resolve an address at a given exit node even when they ask for
24601 - Servers no longer ever list themselves in their "family" line,
24602 even if configured to do so. This makes it easier to configure
24603 family lists conveniently.
24604 - When running as a server, don't fall back to 127.0.0.1 when no
24605 nameservers are configured in /etc/resolv.conf; instead, make the
24606 user fix resolv.conf or specify nameservers explicitly. (Resolves
24608 - Stop accepting certain malformed ports in configured exit policies.
24609 - Don't re-write the fingerprint file every restart, unless it has
24611 - Stop warning when a single nameserver fails: only warn when _all_ of
24612 our nameservers have failed. Also, when we only have one nameserver,
24613 raise the threshold for deciding that the nameserver is dead.
24614 - Directory authorities now only decide that routers are reachable
24615 if their identity keys are as expected.
24616 - When the user uses bad syntax in the Log config line, stop
24617 suggesting other bad syntax as a replacement.
24618 - Correctly detect ipv6 DNS capability on OpenBSD.
24620 o Minor bugfixes (controller):
24621 - Report the circuit number correctly in STREAM CLOSED events. Bug
24622 reported by Mike Perry.
24623 - Do not report bizarre values for results of accounting GETINFOs
24624 when the last second's write or read exceeds the allotted bandwidth.
24625 - Report "unrecognized key" rather than an empty string when the
24626 controller tries to fetch a networkstatus that doesn't exist.
24629 Changes in version 0.1.1.26 - 2006-12-14
24630 o Security bugfixes:
24631 - Stop sending the HttpProxyAuthenticator string to directory
24632 servers when directory connections are tunnelled through Tor.
24633 - Clients no longer store bandwidth history in the state file.
24634 - Do not log introduction points for hidden services if SafeLogging
24638 - Fix an assert failure when a directory authority sets
24639 AuthDirRejectUnlisted and then receives a descriptor from an
24640 unlisted router (reported by seeess).
24643 Changes in version 0.1.2.4-alpha - 2006-12-03
24645 - Add support for using natd; this allows FreeBSDs earlier than
24646 5.1.2 to have ipfw send connections through Tor without using
24647 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
24650 - Make all connections to addresses of the form ".noconnect"
24651 immediately get closed. This lets application/controller combos
24652 successfully test whether they're talking to the same Tor by
24653 watching for STREAM events.
24654 - Make cross.sh cross-compilation script work even when autogen.sh
24655 hasn't been run. (Patch from Michael Mohr.)
24656 - Statistics dumped by -USR2 now include a breakdown of public key
24657 operations, for profiling.
24660 - Fix a major leak when directory authorities parse their
24661 approved-routers list, a minor memory leak when we fail to pick
24662 an exit node, and a few rare leaks on errors.
24663 - Handle TransPort connections even when the server sends data before
24664 the client sends data. Previously, the connection would just hang
24665 until the client sent data. (Patch from tup based on patch from
24667 - Avoid assert failure when our cached-routers file is empty on
24671 - Don't log spurious warnings when we see a circuit close reason we
24672 don't recognize; it's probably just from a newer version of Tor.
24673 - Have directory authorities allow larger amounts of drift in uptime
24674 without replacing the server descriptor: previously, a server that
24675 restarted every 30 minutes could have 48 "interesting" descriptors
24677 - Start linking to the Tor specification and Tor reference manual
24678 correctly in the Windows installer.
24679 - Add Vidalia to the OS X uninstaller script, so when we uninstall
24680 Tor/Privoxy we also uninstall Vidalia.
24681 - Resume building on Irix64, and fix a lot of warnings from its
24682 MIPSpro C compiler.
24683 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
24684 when we're running as a client.
24687 Changes in version 0.1.1.25 - 2006-11-04
24689 - When a client asks us to resolve (rather than connect to)
24690 an address, and we have a cached answer, give them the cached
24691 answer. Previously, we would give them no answer at all.
24692 - We were building exactly the wrong circuits when we predict
24693 hidden service requirements, meaning Tor would have to build all
24694 its circuits on demand.
24695 - If none of our live entry guards have a high uptime, but we
24696 require a guard with a high uptime, try adding a new guard before
24697 we give up on the requirement. This patch should make long-lived
24698 connections more stable on average.
24699 - When testing reachability of our DirPort, don't launch new
24700 tests when there's already one in progress -- unreachable
24701 servers were stacking up dozens of testing streams.
24703 o Security bugfixes:
24704 - When the user sends a NEWNYM signal, clear the client-side DNS
24705 cache too. Otherwise we continue to act on previous information.
24708 - Avoid a memory corruption bug when creating a hash table for
24710 - Avoid possibility of controller-triggered crash when misusing
24711 certain commands from a v0 controller on platforms that do not
24712 handle printf("%s",NULL) gracefully.
24713 - Avoid infinite loop on unexpected controller input.
24714 - Don't log spurious warnings when we see a circuit close reason we
24715 don't recognize; it's probably just from a newer version of Tor.
24716 - Add Vidalia to the OS X uninstaller script, so when we uninstall
24717 Tor/Privoxy we also uninstall Vidalia.
24720 Changes in version 0.1.2.3-alpha - 2006-10-29
24722 - Prepare for servers to publish descriptors less often: never
24723 discard a descriptor simply for being too old until either it is
24724 recommended by no authorities, or until we get a better one for
24725 the same router. Make caches consider retaining old recommended
24726 routers for even longer.
24727 - If most authorities set a BadExit flag for a server, clients
24728 don't think of it as a general-purpose exit. Clients only consider
24729 authorities that advertise themselves as listing bad exits.
24730 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
24731 headers for content, so that we can work better in the presence of
24732 caching HTTP proxies.
24733 - Allow authorities to list nodes as bad exits by fingerprint or by
24736 o Minor features, controller:
24737 - Add a REASON field to CIRC events; for backward compatibility, this
24738 field is sent only to controllers that have enabled the extended
24739 event format. Also, add additional reason codes to explain why
24740 a given circuit has been destroyed or truncated. (Patches from
24742 - Add a REMOTE_REASON field to extended CIRC events to tell the
24743 controller about why a remote OR told us to close a circuit.
24744 - Stream events also now have REASON and REMOTE_REASON fields,
24745 working much like those for circuit events.
24746 - There's now a GETINFO ns/... field so that controllers can ask Tor
24747 about the current status of a router.
24748 - A new event type "NS" to inform a controller when our opinion of
24749 a router's status has changed.
24750 - Add a GETINFO events/names and GETINFO features/names so controllers
24751 can tell which events and features are supported.
24752 - A new CLEARDNSCACHE signal to allow controllers to clear the
24753 client-side DNS cache without expiring circuits.
24755 o Security bugfixes:
24756 - When the user sends a NEWNYM signal, clear the client-side DNS
24757 cache too. Otherwise we continue to act on previous information.
24760 - Avoid sending junk to controllers or segfaulting when a controller
24761 uses EVENT_NEW_DESC with verbose nicknames.
24762 - Stop triggering asserts if the controller tries to extend hidden
24763 service circuits (reported by mwenge).
24764 - Avoid infinite loop on unexpected controller input.
24765 - When the controller does a "GETINFO network-status", tell it
24766 about even those routers whose descriptors are very old, and use
24767 long nicknames where appropriate.
24768 - Change NT service functions to be loaded on demand. This lets us
24769 build with MinGW without breaking Tor for Windows 98 users.
24770 - Do DirPort reachability tests less often, since a single test
24771 chews through many circuits before giving up.
24772 - In the hidden service example in torrc.sample, stop recommending
24773 esoteric and discouraged hidden service options.
24774 - When stopping an NT service, wait up to 10 sec for it to actually
24775 stop. Patch from Matt Edman; resolves bug 295.
24776 - Fix handling of verbose nicknames with ORCONN controller events:
24777 make them show up exactly when requested, rather than exactly when
24779 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
24780 printing a duplicate "$" in the keys we send (reported by mwenge).
24781 - Correctly set maximum connection limit on Cygwin. (This time
24783 - Try to detect Windows correctly when cross-compiling.
24784 - Detect the size of the routers file correctly even if it is
24785 corrupted (on systems without mmap) or not page-aligned (on systems
24786 with mmap). This bug was harmless.
24787 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
24788 to open a stream fails; now we do in more cases. This should
24789 make clients able to find a good exit faster in some cases, since
24790 unhandleable requests will now get an error rather than timing out.
24791 - Resolve two memory leaks when rebuilding the on-disk router cache
24792 (reported by fookoowa).
24793 - Clean up minor code warnings suggested by the MIPSpro C compiler,
24794 and reported by some Centos users.
24795 - Controller signals now work on non-Unix platforms that don't define
24796 SIGUSR1 and SIGUSR2 the way we expect.
24797 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
24798 values before failing, and always enables eventdns.
24799 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
24800 Try to fix this in configure.in by checking for most functions
24801 before we check for libevent.
24804 Changes in version 0.1.2.2-alpha - 2006-10-07
24806 - Make our async eventdns library on-by-default for Tor servers,
24807 and plan to deprecate the separate dnsworker threads.
24808 - Add server-side support for "reverse" DNS lookups (using PTR
24809 records so clients can determine the canonical hostname for a given
24810 IPv4 address). Only supported by servers using eventdns; servers
24811 now announce in their descriptors whether they support eventdns.
24812 - Specify and implement client-side SOCKS5 interface for reverse DNS
24813 lookups (see doc/socks-extensions.txt).
24814 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
24815 connect to directory servers through Tor. Previously, clients needed
24816 to find Tor exits to make private connections to directory servers.
24817 - Avoid choosing Exit nodes for entry or middle hops when the
24818 total bandwidth available from non-Exit nodes is much higher than
24819 the total bandwidth available from Exit nodes.
24820 - Workaround for name servers (like Earthlink's) that hijack failing
24821 DNS requests and replace the no-such-server answer with a "helpful"
24822 redirect to an advertising-driven search portal. Also work around
24823 DNS hijackers who "helpfully" decline to hijack known-invalid
24824 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
24825 lets you turn it off.
24826 - Send out a burst of long-range padding cells once we've established
24827 that we're reachable. Spread them over 4 circuits, so hopefully
24828 a few will be fast. This exercises our bandwidth and bootstraps
24829 us into the directory more quickly.
24831 o New/improved config options:
24832 - Add new config option "ResolvConf" to let the server operator
24833 choose an alternate resolve.conf file when using eventdns.
24834 - Add an "EnforceDistinctSubnets" option to control our "exclude
24835 servers on the same /16" behavior. It's still on by default; this
24836 is mostly for people who want to operate private test networks with
24837 all the machines on the same subnet.
24838 - If one of our entry guards is on the ExcludeNodes list, or the
24839 directory authorities don't think it's a good guard, treat it as
24840 if it were unlisted: stop using it as a guard, and throw it off
24841 the guards list if it stays that way for a long time.
24842 - Allow directory authorities to be marked separately as authorities
24843 for the v1 directory protocol, the v2 directory protocol, and
24844 as hidden service directories, to make it easier to retire old
24845 authorities. V1 authorities should set "HSAuthoritativeDir 1"
24846 to continue being hidden service authorities too.
24847 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
24849 o Minor features, controller:
24850 - Fix CIRC controller events so that controllers can learn the
24851 identity digests of non-Named servers used in circuit paths.
24852 - Let controllers ask for more useful identifiers for servers. Instead
24853 of learning identity digests for un-Named servers and nicknames
24854 for Named servers, the new identifiers include digest, nickname,
24855 and indication of Named status. Off by default; see control-spec.txt
24856 for more information.
24857 - Add a "getinfo address" controller command so it can display Tor's
24858 best guess to the user.
24859 - New controller event to alert the controller when our server
24860 descriptor has changed.
24861 - Give more meaningful errors on controller authentication failure.
24863 o Minor features, other:
24864 - When asked to resolve a hostname, don't use non-exit servers unless
24865 requested to do so. This allows servers with broken DNS to be
24866 useful to the network.
24867 - Divide eventdns log messages into warn and info messages.
24868 - Reserve the nickname "Unnamed" for routers that can't pick
24869 a hostname: any router can call itself Unnamed; directory
24870 authorities will never allocate Unnamed to any particular router;
24871 clients won't believe that any router is the canonical Unnamed.
24872 - Only include function names in log messages for info/debug messages.
24873 For notice/warn/err, the content of the message should be clear on
24874 its own, and printing the function name only confuses users.
24875 - Avoid some false positives during reachability testing: don't try
24876 to test via a server that's on the same /24 as us.
24877 - If we fail to build a circuit to an intended enclave, and it's
24878 not mandatory that we use that enclave, stop wanting it.
24879 - When eventdns is enabled, allow multithreaded builds on NetBSD and
24880 OpenBSD. (We had previously disabled threads on these platforms
24881 because they didn't have working thread-safe resolver functions.)
24883 o Major bugfixes, anonymity/security:
24884 - If a client asked for a server by name, and there's a named server
24885 in our network-status but we don't have its descriptor yet, we
24886 could return an unnamed server instead.
24887 - Fix NetBSD bug that could allow someone to force uninitialized RAM
24888 to be sent to a server's DNS resolver. This only affects NetBSD
24889 and other platforms that do not bounds-check tolower().
24890 - Reject (most) attempts to use Tor circuits with length one. (If
24891 many people start using Tor as a one-hop proxy, exit nodes become
24892 a more attractive target for compromise.)
24893 - Just because your DirPort is open doesn't mean people should be
24894 able to remotely teach you about hidden service descriptors. Now
24895 only accept rendezvous posts if you've got HSAuthoritativeDir set.
24897 o Major bugfixes, other:
24898 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
24899 - When a client asks the server to resolve (not connect to)
24900 an address, and it has a cached answer, give them the cached answer.
24901 Previously, the server would give them no answer at all.
24902 - Allow really slow clients to not hang up five minutes into their
24903 directory downloads (suggested by Adam J. Richter).
24904 - We were building exactly the wrong circuits when we anticipated
24905 hidden service requirements, meaning Tor would have to build all
24906 its circuits on demand.
24907 - Avoid crashing when we mmap a router cache file of size 0.
24908 - When testing reachability of our DirPort, don't launch new
24909 tests when there's already one in progress -- unreachable
24910 servers were stacking up dozens of testing streams.
24912 o Minor bugfixes, correctness:
24913 - If we're a directory mirror and we ask for "all" network status
24914 documents, we would discard status documents from authorities
24915 we don't recognize.
24916 - Avoid a memory corruption bug when creating a hash table for
24918 - Avoid controller-triggered crash when misusing certain commands
24919 from a v0 controller on platforms that do not handle
24920 printf("%s",NULL) gracefully.
24921 - Don't crash when a controller sends a third argument to an
24922 "extendcircuit" request.
24923 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
24924 response; fix error code when "getinfo dir/status/" fails.
24925 - Avoid crash when telling controller stream-status and a stream
24927 - Patch from Adam Langley to fix assert() in eventdns.c.
24928 - Fix a debug log message in eventdns to say "X resolved to Y"
24929 instead of "X resolved to X".
24930 - Make eventdns give strings for DNS errors, not just error numbers.
24931 - Track unreachable entry guards correctly: don't conflate
24932 'unreachable by us right now' with 'listed as down by the directory
24933 authorities'. With the old code, if a guard was unreachable by
24934 us but listed as running, it would clog our guard list forever.
24935 - Behave correctly in case we ever have a network with more than
24936 2GB/s total advertised capacity.
24937 - Make TrackExitHosts case-insensitive, and fix the behavior of
24938 ".suffix" TrackExitHosts items to avoid matching in the middle of
24940 - Finally fix the openssl warnings from newer gccs that believe that
24941 ignoring a return value is okay, but casting a return value and
24942 then ignoring it is a sign of madness.
24943 - Prevent the contrib/exitlist script from printing the same
24944 result more than once.
24945 - Patch from Steve Hildrey: Generate network status correctly on
24946 non-versioning dirservers.
24947 - Don't listen to the X-Your-Address-Is hint if you did the lookup
24948 via Tor; otherwise you'll think you're the exit node's IP address.
24950 o Minor bugfixes, performance:
24951 - Two small performance improvements on parsing descriptors.
24952 - Major performance improvement on inserting descriptors: change
24953 algorithm from O(n^2) to O(n).
24954 - Make the common memory allocation path faster on machines where
24955 malloc(0) returns a pointer.
24956 - Start remembering X-Your-Address-Is directory hints even if you're
24957 a client, so you can become a server more smoothly.
24958 - Avoid duplicate entries on MyFamily line in server descriptor.
24960 o Packaging, features:
24961 - Remove architecture from OS X builds. The official builds are
24962 now universal binaries.
24963 - The Debian package now uses --verify-config when (re)starting,
24964 to distinguish configuration errors from other errors.
24965 - Update RPMs to require libevent 1.1b.
24967 o Packaging, bugfixes:
24968 - Patches so Tor builds with MinGW on Windows.
24969 - Patches so Tor might run on Cygwin again.
24970 - Resume building on non-gcc compilers and ancient gcc. Resume
24971 building with the -O0 compile flag. Resume building cleanly on
24973 - Run correctly on OS X platforms with case-sensitive filesystems.
24974 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
24975 - Add autoconf checks so Tor can build on Solaris x86 again.
24978 - Documented (and renamed) ServerDNSSearchDomains and
24979 ServerDNSResolvConfFile options.
24980 - Be clearer that the *ListenAddress directives can be repeated
24984 Changes in version 0.1.1.24 - 2006-09-29
24986 - Allow really slow clients to not hang up five minutes into their
24987 directory downloads (suggested by Adam J. Richter).
24988 - Fix major performance regression from 0.1.0.x: instead of checking
24989 whether we have enough directory information every time we want to
24990 do something, only check when the directory information has changed.
24991 This should improve client CPU usage by 25-50%.
24992 - Don't crash if, after a server has been running for a while,
24993 it can't resolve its hostname.
24996 - Allow Tor to start when RunAsDaemon is set but no logs are set.
24997 - Don't crash when the controller receives a third argument to an
24998 "extendcircuit" request.
24999 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
25000 response; fix error code when "getinfo dir/status/" fails.
25001 - Fix configure.in to not produce broken configure files with
25002 more recent versions of autoconf. Thanks to Clint for his auto*
25004 - Fix security bug on NetBSD that could allow someone to force
25005 uninitialized RAM to be sent to a server's DNS resolver. This
25006 only affects NetBSD and other platforms that do not bounds-check
25008 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
25009 methods: these are known to be buggy.
25010 - If we're a directory mirror and we ask for "all" network status
25011 documents, we would discard status documents from authorities
25012 we don't recognize.
25015 Changes in version 0.1.2.1-alpha - 2006-08-27
25017 - Add "eventdns" async dns library from Adam Langley, tweaked to
25018 build on OSX and Windows. Only enabled if you pass the
25019 --enable-eventdns argument to configure.
25020 - Allow servers with no hostname or IP address to learn their
25021 IP address by asking the directory authorities. This code only
25022 kicks in when you would normally have exited with a "no address"
25023 error. Nothing's authenticated, so use with care.
25024 - Rather than waiting a fixed amount of time between retrying
25025 application connections, we wait only 5 seconds for the first,
25026 10 seconds for the second, and 15 seconds for each retry after
25027 that. Hopefully this will improve the expected user experience.
25028 - Patch from Tup to add support for transparent AP connections:
25029 this basically bundles the functionality of trans-proxy-tor
25030 into the Tor mainline. Now hosts with compliant pf/netfilter
25031 implementations can redirect TCP connections straight to Tor
25032 without diverting through SOCKS. Needs docs.
25033 - Busy directory servers save lots of memory by spooling server
25034 descriptors, v1 directories, and v2 networkstatus docs to buffers
25035 as needed rather than en masse. Also mmap the cached-routers
25036 files, so we don't need to keep the whole thing in memory too.
25037 - Automatically avoid picking more than one node from the same
25038 /16 network when constructing a circuit.
25039 - Revise and clean up the torrc.sample that we ship with; add
25040 a section for BandwidthRate and BandwidthBurst.
25043 - Split circuit_t into origin_circuit_t and or_circuit_t, and
25044 split connection_t into edge, or, dir, control, and base structs.
25045 These will save quite a bit of memory on busy servers, and they'll
25046 also help us track down bugs in the code and bugs in the spec.
25047 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
25048 or later. Log when we are doing this, so we can diagnose it when
25049 it fails. (Also, recommend libevent 1.1b for kqueue and
25050 win32 methods; deprecate libevent 1.0b harder; make libevent
25051 recommendation system saner.)
25052 - Start being able to build universal binaries on OS X (thanks
25054 - Export the default exit policy via the control port, so controllers
25055 don't need to guess what it is / will be later.
25056 - Add a man page entry for ProtocolWarnings.
25057 - Add TestVia config option to the man page.
25058 - Remove even more protocol-related warnings from Tor server logs,
25059 such as bad TLS handshakes and malformed begin cells.
25060 - Stop fetching descriptors if you're not a dir mirror and you
25061 haven't tried to establish any circuits lately. [This currently
25062 causes some dangerous behavior, because when you start up again
25063 you'll use your ancient server descriptors.]
25064 - New DirPort behavior: if you have your dirport set, you download
25065 descriptors aggressively like a directory mirror, whether or not
25066 your ORPort is set.
25067 - Get rid of the router_retry_connections notion. Now routers
25068 no longer try to rebuild long-term connections to directory
25069 authorities, and directory authorities no longer try to rebuild
25070 long-term connections to all servers. We still don't hang up
25071 connections in these two cases though -- we need to look at it
25072 more carefully to avoid flapping, and we likely need to wait til
25073 0.1.1.x is obsolete.
25074 - Drop compatibility with obsolete Tors that permit create cells
25075 to have the wrong circ_id_type.
25076 - Re-enable per-connection rate limiting. Get rid of the "OP
25077 bandwidth" concept. Lay groundwork for "bandwidth classes" --
25078 separate global buckets that apply depending on what sort of conn
25080 - Start publishing one minute or so after we find our ORPort
25081 to be reachable. This will help reduce the number of descriptors
25082 we have for ourselves floating around, since it's quite likely
25083 other things (e.g. DirPort) will change during that minute too.
25084 - Fork the v1 directory protocol into its own spec document,
25085 and mark dir-spec.txt as the currently correct (v2) spec.
25088 - When we find our DirPort to be reachable, publish a new descriptor
25089 so we'll tell the world (reported by pnx).
25090 - Publish a new descriptor after we hup/reload. This is important
25091 if our config has changed such that we'll want to start advertising
25092 our DirPort now, etc.
25093 - Allow Tor to start when RunAsDaemon is set but no logs are set.
25094 - When we have a state file we cannot parse, tell the user and
25095 move it aside. Now we avoid situations where the user starts
25096 Tor in 1904, Tor writes a state file with that timestamp in it,
25097 the user fixes her clock, and Tor refuses to start.
25098 - Fix configure.in to not produce broken configure files with
25099 more recent versions of autoconf. Thanks to Clint for his auto*
25101 - "tor --verify-config" now exits with -1(255) or 0 depending on
25102 whether the config options are bad or good.
25103 - Resolve bug 321 when using dnsworkers: append a period to every
25104 address we resolve at the exit node, so that we do not accidentally
25105 pick up local addresses, and so that failing searches are retried
25106 in the resolver search domains. (This is already solved for
25107 eventdns.) (This breaks Blossom servers for now.)
25108 - If we are using an exit enclave and we can't connect, e.g. because
25109 its webserver is misconfigured to not listen on localhost, then
25110 back off and try connecting from somewhere else before we fail.
25113 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
25114 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
25115 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
25116 when the IP address is mapped through MapAddress to a hostname.
25117 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
25118 useless IPv6 DNS resolves.
25119 - Patch suggested by Karsten Loesing: respond to SIGNAL command
25120 before we execute the signal, in case the signal shuts us down.
25121 - Clean up AllowInvalidNodes man page entry.
25122 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
25123 - Add more asserts to track down an assert error on a windows Tor
25124 server with connection_add being called with socket == -1.
25125 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
25126 - Fix misleading log messages: an entry guard that is "unlisted",
25127 as well as not known to be "down" (because we've never heard
25128 of it), is not therefore "up".
25129 - Remove code to special-case "-cvs" ending, since it has not
25130 actually mattered since 0.0.9.
25131 - Make our socks5 handling more robust to broken socks clients:
25132 throw out everything waiting on the buffer in between socks
25133 handshake phases, since they can't possibly (so the theory
25134 goes) have predicted what we plan to respond to them.
25137 Changes in version 0.1.1.23 - 2006-07-30
25139 - Fast Tor servers, especially exit nodes, were triggering asserts
25140 due to a bug in handling the list of pending DNS resolves. Some
25141 bugs still remain here; we're hunting them.
25142 - Entry guards could crash clients by sending unexpected input.
25143 - More fixes on reachability testing: if you find yourself reachable,
25144 then don't ever make any client requests (so you stop predicting
25145 circuits), then hup or have your clock jump, then later your IP
25146 changes, you won't think circuits are working, so you won't try to
25147 test reachability, so you won't publish.
25150 - Avoid a crash if the controller does a resetconf firewallports
25151 and then a setconf fascistfirewall=1.
25152 - Avoid an integer underflow when the dir authority decides whether
25153 a router is stable: we might wrongly label it stable, and compute
25154 a slightly wrong median stability, when a descriptor is published
25156 - Fix a place where we might trigger an assert if we can't build our
25157 own server descriptor yet.
25160 Changes in version 0.1.1.22 - 2006-07-05
25162 - Fix a big bug that was causing servers to not find themselves
25163 reachable if they changed IP addresses. Since only 0.1.1.22+
25164 servers can do reachability testing correctly, now we automatically
25165 make sure to test via one of these.
25166 - Fix to allow clients and mirrors to learn directory info from
25167 descriptor downloads that get cut off partway through.
25168 - Directory authorities had a bug in deciding if a newly published
25169 descriptor was novel enough to make everybody want a copy -- a few
25170 servers seem to be publishing new descriptors many times a minute.
25172 - Fix a rare bug that was causing some servers to complain about
25173 "closing wedged cpuworkers" and skip some circuit create requests.
25174 - Make the Exit flag in directory status documents actually work.
25177 Changes in version 0.1.1.21 - 2006-06-10
25178 o Crash and assert fixes from 0.1.1.20:
25179 - Fix a rare crash on Tor servers that have enabled hibernation.
25180 - Fix a seg fault on startup for Tor networks that use only one
25181 directory authority.
25182 - Fix an assert from a race condition that occurs on Tor servers
25183 while exiting, where various threads are trying to log that they're
25184 exiting, and delete the logs, at the same time.
25185 - Make our unit tests pass again on certain obscure platforms.
25188 - Add support for building SUSE RPM packages.
25189 - Speed up initial bootstrapping for clients: if we are making our
25190 first ever connection to any entry guard, then don't mark it down
25192 - When only one Tor server in the network is labelled as a guard,
25193 and we've already picked him, we would cycle endlessly picking him
25194 again, being unhappy about it, etc. Now we specifically exclude
25195 current guards when picking a new guard.
25196 - Servers send create cells more reliably after the TLS connection
25197 is established: we were sometimes forgetting to send half of them
25198 when we had more than one pending.
25199 - If we get a create cell that asks us to extend somewhere, but the
25200 Tor server there doesn't match the expected digest, we now send
25201 a destroy cell back, rather than silently doing nothing.
25202 - Make options->RedirectExit work again.
25203 - Make cookie authentication for the controller work again.
25204 - Stop being picky about unusual characters in the arguments to
25205 mapaddress. It's none of our business.
25206 - Add a new config option "TestVia" that lets you specify preferred
25207 middle hops to use for test circuits. Perhaps this will let me
25208 debug the reachability problems better.
25210 o Log / documentation fixes:
25211 - If we're a server and some peer has a broken TLS certificate, don't
25212 log about it unless ProtocolWarnings is set, i.e., we want to hear
25213 about protocol violations by others.
25214 - Fix spelling of VirtualAddrNetwork in man page.
25215 - Add a better explanation at the top of the autogenerated torrc file
25216 about what happened to our old torrc.
25219 Changes in version 0.1.1.20 - 2006-05-23
25221 - Downgrade a log severity where servers complain that they're
25223 - Avoid a compile warning on FreeBSD.
25224 - Remove string size limit on NEWDESC messages; solve bug 291.
25225 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
25226 more thoroughly when we're running on windows.
25229 Changes in version 0.1.1.19-rc - 2006-05-03
25231 - Regenerate our local descriptor if it's dirty and we try to use
25232 it locally (e.g. if it changes during reachability detection).
25233 - If we setconf our ORPort to 0, we continued to listen on the
25234 old ORPort and receive connections.
25235 - Avoid a second warning about machine/limits.h on Debian
25237 - Be willing to add our own routerinfo into the routerlist.
25238 Now authorities will include themselves in their directories
25239 and network-statuses.
25240 - Stop trying to upload rendezvous descriptors to every
25241 directory authority: only try the v1 authorities.
25242 - Servers no longer complain when they think they're not
25243 registered with the directory authorities. There were too many
25245 - Backport dist-rpm changes so rpms can be built without errors.
25248 - Implement an option, VirtualAddrMask, to set which addresses
25249 get handed out in response to mapaddress requests. This works
25250 around a bug in tsocks where 127.0.0.0/8 is never socksified.
25253 Changes in version 0.1.1.18-rc - 2006-04-10
25255 - Work harder to download live network-statuses from all the
25256 directory authorities we know about. Improve the threshold
25257 decision logic so we're more robust to edge cases.
25258 - When fetching rendezvous descriptors, we were willing to ask
25259 v2 authorities too, which would always return 404.
25262 - Stop listing down or invalid nodes in the v1 directory. This will
25263 reduce its bulk by about 1/3, and reduce load on directory
25265 - When deciding whether a router is Fast or Guard-worthy, consider
25266 his advertised BandwidthRate and not just the BandwidthCapacity.
25267 - No longer ship INSTALL and README files -- they are useless now.
25268 - Force rpmbuild to behave and honor target_cpu.
25269 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
25270 - Start to include translated versions of the tor-doc-*.html
25271 files, along with the screenshots. Still needs more work.
25272 - Start sending back 512 and 451 errors if mapaddress fails,
25273 rather than not sending anything back at all.
25274 - When we fail to bind or listen on an incoming or outgoing
25275 socket, we should close it before failing. otherwise we just
25276 leak it. (thanks to weasel for finding.)
25277 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
25278 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
25279 - Make NoPublish (even though deprecated) work again.
25280 - Fix a minor security flaw where a versioning auth dirserver
25281 could list a recommended version many times in a row to make
25282 clients more convinced that it's recommended.
25283 - Fix crash bug if there are two unregistered servers running
25284 with the same nickname, one of them is down, and you ask for
25285 them by nickname in your EntryNodes or ExitNodes. Also, try
25286 to pick the one that's running rather than an arbitrary one.
25287 - Fix an infinite loop we could hit if we go offline for too long.
25288 - Complain when we hit WSAENOBUFS on recv() or write() too.
25289 Perhaps this will help us hunt the bug.
25290 - If you're not a versioning dirserver, don't put the string
25291 "client-versions \nserver-versions \n" in your network-status.
25292 - Lower the minimum required number of file descriptors to 1000,
25293 so we can have some overhead for Valgrind on Linux, where the
25294 default ulimit -n is 1024.
25297 - Add tor.dizum.com as the fifth authoritative directory server.
25298 - Add a new config option FetchUselessDescriptors, off by default,
25299 for when you plan to run "exitlist" on your client and you want
25300 to know about even the non-running descriptors.
25303 Changes in version 0.1.1.17-rc - 2006-03-28
25305 - Clients and servers since 0.1.1.10-alpha have been expiring
25306 connections whenever they are idle for 5 minutes and they *do*
25307 have circuits on them. Oops. With this new version, clients will
25308 discard their previous entry guard choices and avoid choosing
25309 entry guards running these flawed versions.
25310 - Fix memory leak when uncompressing concatenated zlib streams. This
25311 was causing substantial leaks over time on Tor servers.
25312 - The v1 directory was including servers as much as 48 hours old,
25313 because that's how the new routerlist->routers works. Now only
25314 include them if they're 20 hours old or less.
25317 - Resume building on irix64, netbsd 2.0, etc.
25318 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
25320 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
25321 and it is confusing some users.
25322 - Mirrors stop caching the v1 directory so often.
25323 - Make the max number of old descriptors that a cache will hold
25324 rise with the number of directory authorities, so we can scale.
25325 - Change our win32 uname() hack to be more forgiving about what
25326 win32 versions it thinks it's found.
25329 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
25331 - When the controller's *setconf commands fail, collect an error
25332 message in a string and hand it back to the controller.
25333 - Make the v2 dir's "Fast" flag based on relative capacity, just
25334 like "Stable" is based on median uptime. Name everything in the
25335 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
25336 - Log server fingerprint on startup, so new server operators don't
25337 have to go hunting around their filesystem for it.
25338 - Return a robots.txt on our dirport to discourage google indexing.
25339 - Let the controller ask for GETINFO dir/status/foo so it can ask
25340 directly rather than connecting to the dir port. Only works when
25341 dirport is set for now.
25343 o New config options rather than constants in the code:
25344 - SocksTimeout: How long do we let a socks connection wait
25345 unattached before we fail it?
25346 - CircuitBuildTimeout: Cull non-open circuits that were born
25347 at least this many seconds ago.
25348 - CircuitIdleTimeout: Cull open clean circuits that were born
25349 at least this many seconds ago.
25352 Changes in version 0.1.1.16-rc - 2006-03-18
25353 o Bugfixes on 0.1.1.15-rc:
25354 - Fix assert when the controller asks to attachstream a connect-wait
25355 or resolve-wait stream.
25356 - Now do address rewriting when the controller asks us to attach
25357 to a particular circuit too. This will let Blossom specify
25358 "moria2.exit" without having to learn what moria2's IP address is.
25359 - Make the "tor --verify-config" command-line work again, so people
25360 can automatically check if their torrc will parse.
25361 - Authoritative dirservers no longer require an open connection from
25362 a server to consider him "reachable". We need this change because
25363 when we add new auth dirservers, old servers won't know not to
25365 - Let Tor build on Sun CC again.
25366 - Fix an off-by-one buffer size in dirserv.c that magically never
25367 hit our three authorities but broke sjmurdoch's own tor network.
25368 - If we as a directory mirror don't know of any v1 directory
25369 authorities, then don't try to cache any v1 directories.
25370 - Stop warning about unknown servers in our family when they are
25371 given as hex digests.
25372 - Stop complaining as quickly to the server operator that he
25373 hasn't registered his nickname/key binding.
25374 - Various cleanups so we can add new V2 Auth Dirservers.
25375 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
25376 reflect the updated flags in our v2 dir protocol.
25377 - Resume allowing non-printable characters for exit streams (both
25378 for connecting and for resolving). Now we tolerate applications
25379 that don't follow the RFCs. But continue to block malformed names
25382 o Bugfixes on 0.1.0.x:
25383 - Fix assert bug in close_logs(): when we close and delete logs,
25384 remove them all from the global "logfiles" list.
25385 - Fix minor integer overflow in calculating when we expect to use up
25386 our bandwidth allocation before hibernating.
25387 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
25388 there are multiple SSLs installed with different versions.
25389 - When we try to be a server and Address is not explicitly set and
25390 our hostname resolves to a private IP address, try to use an
25391 interface address if it has a public address. Now Windows machines
25392 that think of themselves as localhost can work by default.
25395 - Let the controller ask for GETINFO dir/server/foo so it can ask
25396 directly rather than connecting to the dir port.
25397 - Let the controller tell us about certain router descriptors
25398 that it doesn't want Tor to use in circuits. Implement
25399 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
25400 - New config option SafeSocks to reject all application connections
25401 using unsafe socks protocols. Defaults to off.
25404 Changes in version 0.1.1.15-rc - 2006-03-11
25405 o Bugfixes and cleanups:
25406 - When we're printing strings from the network, don't try to print
25407 non-printable characters. This protects us against shell escape
25408 sequence exploits, and also against attacks to fool humans into
25409 misreading their logs.
25410 - Fix a bug where Tor would fail to establish any connections if you
25411 left it off for 24 hours and then started it: we were happy with
25412 the obsolete network statuses, but they all referred to router
25413 descriptors that were too old to fetch, so we ended up with no
25414 valid router descriptors.
25415 - Fix a seg fault in the controller's "getinfo orconn-status"
25416 command while listing status on incoming handshaking connections.
25417 Introduce a status name "NEW" for these connections.
25418 - If we get a linelist or linelist_s config option from the torrc
25419 (e.g. ExitPolicy) and it has no value, warn and skip rather than
25420 silently resetting it to its default.
25421 - Don't abandon entry guards until they've been down or gone for
25423 - Cleaner and quieter log messages.
25426 - New controller signal NEWNYM that makes new application requests
25427 use clean circuits.
25428 - Add a new circuit purpose 'controller' to let the controller ask
25429 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
25430 controller command to let you specify the purpose if you're
25431 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
25432 command to let you change a circuit's purpose after it's been
25434 - Accept "private:*" in routerdesc exit policies; not generated yet
25435 because older Tors do not understand it.
25436 - Add BSD-style contributed startup script "rc.subr" from Peter
25440 Changes in version 0.1.1.14-alpha - 2006-02-20
25441 o Bugfixes on 0.1.1.x:
25442 - Don't die if we ask for a stdout or stderr log (even implicitly)
25443 and we're set to RunAsDaemon -- just warn.
25444 - We still had a few bugs in the OR connection rotation code that
25445 caused directory servers to slowly aggregate connections to other
25446 fast Tor servers. This time for sure!
25447 - Make log entries on Win32 include the name of the function again.
25448 - We were treating a pair of exit policies if they were equal even
25449 if one said accept and the other said reject -- causing us to
25450 not always publish a new descriptor since we thought nothing
25452 - Retry pending server downloads as well as pending networkstatus
25453 downloads when we unexpectedly get a socks request.
25454 - We were ignoring the IS_FAST flag in the directory status,
25455 meaning we were willing to pick trivial-bandwidth nodes for "fast"
25457 - If the controller's SAVECONF command fails (e.g. due to file
25458 permissions), let the controller know that it failed.
25461 - If we're trying to be a Tor server and running Windows 95/98/ME
25462 as a server, explain that we'll likely crash.
25463 - When we're a server, a client asks for an old-style directory,
25464 and our write bucket is empty, don't give it to him. This way
25465 small servers can continue to serve the directory *sometimes*,
25466 without getting overloaded.
25467 - Compress exit policies even more -- look for duplicate lines
25469 - Clients now honor the "guard" flag in the router status when
25470 picking entry guards, rather than looking at is_fast or is_stable.
25471 - Retain unrecognized lines in $DATADIR/state file, so that we can
25472 be forward-compatible.
25473 - Generate 18.0.0.0/8 address policy format in descs when we can;
25474 warn when the mask is not reducible to a bit-prefix.
25475 - Let the user set ControlListenAddress in the torrc. This can be
25476 dangerous, but there are some cases (like a secured LAN) where it
25478 - Split ReachableAddresses into ReachableDirAddresses and
25479 ReachableORAddresses, so we can restrict Dir conns to port 80
25480 and OR conns to port 443.
25481 - Now we can target arch and OS in rpm builds (contributed by
25482 Phobos). Also make the resulting dist-rpm filename match the
25484 - New config options to help controllers: FetchServerDescriptors
25485 and FetchHidServDescriptors for whether to fetch server
25486 info and hidserv info or let the controller do it, and
25487 PublishServerDescriptor and PublishHidServDescriptors.
25488 - Also let the controller set the __AllDirActionsPrivate config
25489 option if you want all directory fetches/publishes to happen via
25490 Tor (it assumes your controller bootstraps your circuits).
25493 Changes in version 0.1.0.17 - 2006-02-17
25494 o Crash bugfixes on 0.1.0.x:
25495 - When servers with a non-zero DirPort came out of hibernation,
25496 sometimes they would trigger an assert.
25498 o Other important bugfixes:
25499 - On platforms that don't have getrlimit (like Windows), we were
25500 artificially constraining ourselves to a max of 1024
25501 connections. Now just assume that we can handle as many as 15000
25502 connections. Hopefully this won't cause other problems.
25504 o Backported features:
25505 - When we're a server, a client asks for an old-style directory,
25506 and our write bucket is empty, don't give it to him. This way
25507 small servers can continue to serve the directory *sometimes*,
25508 without getting overloaded.
25509 - Whenever you get a 503 in response to a directory fetch, try
25510 once more. This will become important once servers start sending
25511 503's whenever they feel busy.
25512 - Fetch a new directory every 120 minutes, not every 40 minutes.
25513 Now that we have hundreds of thousands of users running the old
25514 directory algorithm, it's starting to hurt a lot.
25515 - Bump up the period for forcing a hidden service descriptor upload
25516 from 20 minutes to 1 hour.
25519 Changes in version 0.1.1.13-alpha - 2006-02-09
25520 o Crashes in 0.1.1.x:
25521 - When you tried to setconf ORPort via the controller, Tor would
25522 crash. So people using TorCP to become a server were sad.
25523 - Solve (I hope) the stack-smashing bug that we were seeing on fast
25524 servers. The problem appears to be something do with OpenSSL's
25525 random number generation, or how we call it, or something. Let me
25526 know if the crashes continue.
25527 - Turn crypto hardware acceleration off by default, until we find
25528 somebody smart who can test it for us. (It appears to produce
25529 seg faults in at least some cases.)
25530 - Fix a rare assert error when we've tried all intro points for
25531 a hidden service and we try fetching the service descriptor again:
25532 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
25535 - Fix a major load balance bug: we were round-robining in 16 KB
25536 chunks, and servers with bandwidthrate of 20 KB, while downloading
25537 a 600 KB directory, would starve their other connections. Now we
25538 try to be a bit more fair.
25539 - Dir authorities and mirrors were never expiring the newest
25540 descriptor for each server, causing memory and directory bloat.
25541 - Fix memory-bloating and connection-bloating bug on servers: We
25542 were never closing any connection that had ever had a circuit on
25543 it, because we were checking conn->n_circuits == 0, yet we had a
25544 bug that let it go negative.
25545 - Make Tor work using squid as your http proxy again -- squid
25546 returns an error if you ask for a URL that's too long, and it uses
25547 a really generic error message. Plus, many people are behind a
25548 transparent squid so they don't even realize it.
25549 - On platforms that don't have getrlimit (like Windows), we were
25550 artificially constraining ourselves to a max of 1024
25551 connections. Now just assume that we can handle as many as 15000
25552 connections. Hopefully this won't cause other problems.
25553 - Add a new config option ExitPolicyRejectPrivate which defaults to
25554 1. This means all exit policies will begin with rejecting private
25555 addresses, unless the server operator explicitly turns it off.
25558 - Clients no longer download descriptors for non-running
25560 - Before we add new directory authorities, we should make it
25561 clear that only v1 authorities should receive/publish hidden
25562 service descriptors.
25565 - As soon as we've fetched some more directory info, immediately
25566 try to download more server descriptors. This way we don't have
25567 a 10 second pause during initial bootstrapping.
25568 - Remove even more loud log messages that the server operator can't
25570 - When we're running an obsolete or un-recommended version, make
25571 the log message more clear about what the problem is and what
25572 versions *are* still recommended.
25573 - Provide a more useful warn message when our onion queue gets full:
25574 the CPU is too slow or the exit policy is too liberal.
25575 - Don't warn when we receive a 503 from a dirserver/cache -- this
25576 will pave the way for them being able to refuse if they're busy.
25577 - When we fail to bind a listener, try to provide a more useful
25578 log message: e.g., "Is Tor already running?"
25579 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
25580 Goldberg can prove things about our handshake protocol more
25582 - MaxConn has been obsolete for a while now. Document the ConnLimit
25583 config option, which is a *minimum* number of file descriptors
25584 that must be available else Tor refuses to start.
25585 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
25586 if you log to syslog and want something other than LOG_DAEMON.
25587 - Make dirservers generate a separate "guard" flag to mean,
25588 "would make a good entry guard". Make clients parse it and vote
25589 on it. Not used by clients yet.
25590 - Implement --with-libevent-dir option to ./configure. Also, improve
25591 search techniques to find libevent, and use those for openssl too.
25592 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
25593 - Only start testing reachability once we've established a
25594 circuit. This will make startup on dirservers less noisy.
25595 - Don't try to upload hidden service descriptors until we have
25596 established a circuit.
25597 - Fix the controller's "attachstream 0" command to treat conn like
25598 it just connected, doing address remapping, handling .exit and
25599 .onion idioms, and so on. Now we're more uniform in making sure
25600 that the controller hears about new and closing connections.
25603 Changes in version 0.1.1.12-alpha - 2006-01-11
25604 o Bugfixes on 0.1.1.x:
25605 - The fix to close duplicate server connections was closing all
25606 Tor client connections if they didn't establish a circuit
25607 quickly enough. Oops.
25608 - Fix minor memory issue (double-free) that happened on exit.
25610 o Bugfixes on 0.1.0.x:
25611 - Tor didn't warn when it failed to open a log file.
25614 Changes in version 0.1.1.11-alpha - 2006-01-10
25615 o Crashes in 0.1.1.x:
25616 - Include all the assert/crash fixes from 0.1.0.16.
25617 - If you start Tor and then quit very quickly, there were some
25618 races that tried to free things that weren't allocated yet.
25619 - Fix a rare memory stomp if you're running hidden services.
25620 - Fix segfault when specifying DirServer in config without nickname.
25621 - Fix a seg fault when you finish connecting to a server but at
25622 that moment you dump his server descriptor.
25623 - Extendcircuit and Attachstream controller commands would
25624 assert/crash if you don't give them enough arguments.
25625 - Fix an assert error when we're out of space in the connection_list
25626 and we try to post a hidden service descriptor (reported by weasel).
25627 - If you specify a relative torrc path and you set RunAsDaemon in
25628 your torrc, then it chdir()'s to the new directory. If you HUP,
25629 it tries to load the new torrc location, fails, and exits.
25630 The fix: no longer allow a relative path to torrc using -f.
25633 - Implement "entry guards": automatically choose a handful of entry
25634 nodes and stick with them for all circuits. Only pick new guards
25635 when the ones you have are unsuitable, and if the old guards
25636 become suitable again, switch back. This will increase security
25637 dramatically against certain end-point attacks. The EntryNodes
25638 config option now provides some hints about which entry guards you
25639 want to use most; and StrictEntryNodes means to only use those.
25640 - New directory logic: download by descriptor digest, not by
25641 fingerprint. Caches try to download all listed digests from
25642 authorities; clients try to download "best" digests from caches.
25643 This avoids partitioning and isolating attacks better.
25644 - Make the "stable" router flag in network-status be the median of
25645 the uptimes of running valid servers, and make clients pay
25646 attention to the network-status flags. Thus the cutoff adapts
25647 to the stability of the network as a whole, making IRC, IM, etc
25648 connections more reliable.
25651 - Tor servers with dynamic IP addresses were needing to wait 18
25652 hours before they could start doing reachability testing using
25653 the new IP address and ports. This is because they were using
25654 the internal descriptor to learn what to test, yet they were only
25655 rebuilding the descriptor once they decided they were reachable.
25656 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
25657 to download certain server descriptors, throw them away, and then
25658 fetch them again after 30 minutes. Now mirrors throw away these
25659 server descriptors so clients can't get them.
25660 - We were leaving duplicate connections to other ORs open for a week,
25661 rather than closing them once we detect a duplicate. This only
25662 really affected authdirservers, but it affected them a lot.
25663 - Spread the authdirservers' reachability testing over the entire
25664 testing interval, so we don't try to do 500 TLS's at once every
25668 - If the network is down, and we try to connect to a conn because
25669 we have a circuit in mind, and we timeout (30 seconds) because the
25670 network never answers, we were expiring the circuit, but we weren't
25671 obsoleting the connection or telling the entry_guards functions.
25672 - Some Tor servers process billions of cells per day. These statistics
25673 need to be uint64_t's.
25674 - Check for integer overflows in more places, when adding elements
25675 to smartlists. This could possibly prevent a buffer overflow
25676 on malicious huge inputs. I don't see any, but I haven't looked
25678 - ReachableAddresses kept growing new "reject *:*" lines on every
25680 - When you "setconf log" via the controller, it should remove all
25681 logs. We were automatically adding back in a "log notice stdout".
25682 - Newly bootstrapped Tor networks couldn't establish hidden service
25683 circuits until they had nodes with high uptime. Be more tolerant.
25684 - We were marking servers down when they could not answer every piece
25685 of the directory request we sent them. This was far too harsh.
25686 - Fix the torify (tsocks) config file to not use Tor for localhost
25688 - Directory authorities now go to the proper authority when asking for
25689 a networkstatus, even when they want a compressed one.
25690 - Fix a harmless bug that was causing Tor servers to log
25691 "Got an end because of misc error, but we're not an AP. Closing."
25692 - Authorities were treating their own descriptor changes as cosmetic,
25693 meaning the descriptor available in the network-status and the
25694 descriptor that clients downloaded were different.
25695 - The OS X installer was adding a symlink for tor_resolve but
25696 the binary was called tor-resolve (reported by Thomas Hardly).
25697 - Workaround a problem with some http proxies where they refuse GET
25698 requests that specify "Content-Length: 0" (reported by Adrian).
25699 - Fix wrong log message when you add a "HiddenServiceNodes" config
25700 line without any HiddenServiceDir line (reported by Chris Thomas).
25703 - Write the TorVersion into the state file so we have a prayer of
25704 keeping forward and backward compatibility.
25705 - Revive the FascistFirewall config option rather than eliminating it:
25706 now it's a synonym for ReachableAddresses *:80,*:443.
25707 - Clients choose directory servers from the network status lists,
25708 not from their internal list of router descriptors. Now they can
25709 go to caches directly rather than needing to go to authorities
25711 - Directory authorities ignore router descriptors that have only
25712 cosmetic differences: do this for 0.1.0.x servers now too.
25713 - Add a new flag to network-status indicating whether the server
25714 can answer v2 directory requests too.
25715 - Authdirs now stop whining so loudly about bad descriptors that
25716 they fetch from other dirservers. So when there's a log complaint,
25717 it's for sure from a freshly uploaded descriptor.
25718 - Reduce memory requirements in our structs by changing the order
25720 - There used to be two ways to specify your listening ports in a
25721 server descriptor: on the "router" line and with a separate "ports"
25722 line. Remove support for the "ports" line.
25723 - New config option "AuthDirRejectUnlisted" for auth dirservers as
25724 a panic button: if we get flooded with unusable servers we can
25725 revert to only listing servers in the approved-routers file.
25726 - Auth dir servers can now mark a fingerprint as "!reject" or
25727 "!invalid" in the approved-routers file (as its nickname), to
25728 refuse descriptors outright or include them but marked as invalid.
25729 - Servers store bandwidth history across restarts/crashes.
25730 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
25731 get a better idea of why their circuits failed. Not used yet.
25732 - Directory mirrors now cache up to 16 unrecognized network-status
25733 docs. Now we can add new authdirservers and they'll be cached too.
25734 - When picking a random directory, prefer non-authorities if any
25736 - New controller option "getinfo desc/all-recent" to fetch the
25737 latest server descriptor for every router that Tor knows about.
25740 Changes in version 0.1.0.16 - 2006-01-02
25741 o Crash bugfixes on 0.1.0.x:
25742 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
25743 corrupting the heap, losing FDs, or crashing when we need to resize
25744 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
25745 - It turns out sparc64 platforms crash on unaligned memory access
25746 too -- so detect and avoid this.
25747 - Handle truncated compressed data correctly (by detecting it and
25749 - Fix possible-but-unlikely free(NULL) in control.c.
25750 - When we were closing connections, there was a rare case that
25751 stomped on memory, triggering seg faults and asserts.
25752 - Avoid potential infinite recursion when building a descriptor. (We
25753 don't know that it ever happened, but better to fix it anyway.)
25754 - We were neglecting to unlink marked circuits from soon-to-close OR
25755 connections, which caused some rare scribbling on freed memory.
25756 - Fix a memory stomping race bug when closing the joining point of two
25757 rendezvous circuits.
25758 - Fix an assert in time parsing found by Steven Murdoch.
25760 o Other bugfixes on 0.1.0.x:
25761 - When we're doing reachability testing, provide more useful log
25762 messages so the operator knows what to expect.
25763 - Do not check whether DirPort is reachable when we are suppressing
25764 advertising it because of hibernation.
25765 - When building with -static or on Solaris, we sometimes needed -ldl.
25766 - When we're deciding whether a stream has enough circuits around
25767 that can handle it, count the freshly dirty ones and not the ones
25768 that are so dirty they won't be able to handle it.
25769 - When we're expiring old circuits, we had a logic error that caused
25770 us to close new rendezvous circuits rather than old ones.
25771 - Give a more helpful log message when you try to change ORPort via
25772 the controller: you should upgrade Tor if you want that to work.
25773 - We were failing to parse Tor versions that start with "Tor ".
25774 - Tolerate faulty streams better: when a stream fails for reason
25775 exitpolicy, stop assuming that the router is lying about his exit
25776 policy. When a stream fails for reason misc, allow it to retry just
25777 as if it was resolvefailed. When a stream has failed three times,
25778 reset its failure count so we can try again and get all three tries.
25781 Changes in version 0.1.1.10-alpha - 2005-12-11
25782 o Correctness bugfixes on 0.1.0.x:
25783 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
25784 corrupting the heap, losing FDs, or crashing when we need to resize
25785 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
25786 - Stop doing the complex voodoo overkill checking for insecure
25787 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
25788 - When we were closing connections, there was a rare case that
25789 stomped on memory, triggering seg faults and asserts.
25790 - We were neglecting to unlink marked circuits from soon-to-close OR
25791 connections, which caused some rare scribbling on freed memory.
25792 - When we're deciding whether a stream has enough circuits around
25793 that can handle it, count the freshly dirty ones and not the ones
25794 that are so dirty they won't be able to handle it.
25795 - Recover better from TCP connections to Tor servers that are
25796 broken but don't tell you (it happens!); and rotate TLS
25797 connections once a week.
25798 - When we're expiring old circuits, we had a logic error that caused
25799 us to close new rendezvous circuits rather than old ones.
25800 - Fix a scary-looking but apparently harmless bug where circuits
25801 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
25802 servers, and never switch to state CIRCUIT_STATE_OPEN.
25803 - When building with -static or on Solaris, we sometimes needed to
25805 - Give a useful message when people run Tor as the wrong user,
25806 rather than telling them to start chowning random directories.
25807 - We were failing to inform the controller about new .onion streams.
25809 o Security bugfixes on 0.1.0.x:
25810 - Refuse server descriptors if the fingerprint line doesn't match
25811 the included identity key. Tor doesn't care, but other apps (and
25812 humans) might actually be trusting the fingerprint line.
25813 - We used to kill the circuit when we receive a relay command we
25814 don't recognize. Now we just drop it.
25815 - Start obeying our firewall options more rigorously:
25816 . If we can't get to a dirserver directly, try going via Tor.
25817 . Don't ever try to connect (as a client) to a place our
25818 firewall options forbid.
25819 . If we specify a proxy and also firewall options, obey the
25820 firewall options even when we're using the proxy: some proxies
25821 can only proxy to certain destinations.
25822 - Fix a bug found by Lasse Overlier: when we were making internal
25823 circuits (intended to be cannibalized later for rendezvous and
25824 introduction circuits), we were picking them so that they had
25825 useful exit nodes. There was no need for this, and it actually
25826 aids some statistical attacks.
25827 - Start treating internal circuits and exit circuits separately.
25828 It's important to keep them separate because internal circuits
25829 have their last hops picked like middle hops, rather than like
25830 exit hops. So exiting on them will break the user's expectations.
25832 o Bugfixes on 0.1.1.x:
25833 - Take out the mis-feature where we tried to detect IP address
25834 flapping for people with DynDNS, and chose not to upload a new
25835 server descriptor sometimes.
25836 - Try to be compatible with OpenSSL 0.9.6 again.
25837 - Log fix: when the controller is logging about .onion addresses,
25838 sometimes it didn't include the ".onion" part of the address.
25839 - Don't try to modify options->DirServers internally -- if the
25840 user didn't specify any, just add the default ones directly to
25841 the trusted dirserver list. This fixes a bug where people running
25842 controllers would use SETCONF on some totally unrelated config
25843 option, and Tor would start yelling at them about changing their
25845 - Let the controller's redirectstream command specify a port, in
25846 case the controller wants to change that too.
25847 - When we requested a pile of server descriptors, we sometimes
25848 accidentally launched a duplicate request for the first one.
25849 - Bugfix for trackhostexits: write down the fingerprint of the
25850 chosen exit, not its nickname, because the chosen exit might not
25852 - When parsing foo.exit, if foo is unknown, and we are leaving
25853 circuits unattached, set the chosen_exit field and leave the
25854 address empty. This matters because controllers got confused
25856 - Directory authorities no longer try to download server
25857 descriptors that they know they will reject.
25859 o Features and updates:
25860 - Replace balanced trees with hash tables: this should make stuff
25861 significantly faster.
25862 - Resume using the AES counter-mode implementation that we ship,
25863 rather than OpenSSL's. Ours is significantly faster.
25864 - Many other CPU and memory improvements.
25865 - Add a new config option FastFirstHopPK (on by default) so clients
25866 do a trivial crypto handshake for their first hop, since TLS has
25867 already taken care of confidentiality and authentication.
25868 - Add a new config option TestSocks so people can see if their
25869 applications are using socks4, socks4a, socks5-with-ip, or
25870 socks5-with-hostname. This way they don't have to keep mucking
25871 with tcpdump and wondering if something got cached somewhere.
25872 - Warn when listening on a public address for socks. I suspect a
25873 lot of people are setting themselves up as open socks proxies,
25874 and they have no idea that jerks on the Internet are using them,
25875 since they simply proxy the traffic into the Tor network.
25876 - Add "private:*" as an alias in configuration for policies. Now
25877 you can simplify your exit policy rather than needing to list
25878 every single internal or nonroutable network space.
25879 - Add a new controller event type that allows controllers to get
25880 all server descriptors that were uploaded to a router in its role
25881 as authoritative dirserver.
25882 - Start shipping socks-extensions.txt, tor-doc-unix.html,
25883 tor-doc-server.html, and stylesheet.css in the tarball.
25884 - Stop shipping tor-doc.html in the tarball.
25887 Changes in version 0.1.1.9-alpha - 2005-11-15
25888 o Usability improvements:
25889 - Start calling it FooListenAddress rather than FooBindAddress,
25890 since few of our users know what it means to bind an address
25892 - Reduce clutter in server logs. We're going to try to make
25893 them actually usable now. New config option ProtocolWarnings that
25894 lets you hear about how _other Tors_ are breaking the protocol. Off
25896 - Divide log messages into logging domains. Once we put some sort
25897 of interface on this, it will let people looking at more verbose
25898 log levels specify the topics they want to hear more about.
25899 - Make directory servers return better http 404 error messages
25900 instead of a generic "Servers unavailable".
25901 - Check for even more Windows version flags when writing the platform
25902 string in server descriptors, and note any we don't recognize.
25903 - Clean up more of the OpenSSL memory when exiting, so we can detect
25904 memory leaks better.
25905 - Make directory authorities be non-versioning, non-naming by
25906 default. Now we can add new directory servers without requiring
25907 their operators to pay close attention.
25908 - When logging via syslog, include the pid whenever we provide
25909 a log entry. Suggested by Todd Fries.
25911 o Performance improvements:
25912 - Directory servers now silently throw away new descriptors that
25913 haven't changed much if the timestamps are similar. We do this to
25914 tolerate older Tor servers that upload a new descriptor every 15
25915 minutes. (It seemed like a good idea at the time.)
25916 - Inline bottleneck smartlist functions; use fast versions by default.
25917 - Add a "Map from digest to void*" abstraction digestmap_t so we
25918 can do less hex encoding/decoding. Use it in router_get_by_digest()
25919 to resolve a performance bottleneck.
25920 - Allow tor_gzip_uncompress to extract as much as possible from
25921 truncated compressed data. Try to extract as many
25922 descriptors as possible from truncated http responses (when
25923 DIR_PURPOSE_FETCH_ROUTERDESC).
25924 - Make circ->onionskin a pointer, not a static array. moria2 was using
25925 125000 circuit_t's after it had been up for a few weeks, which
25926 translates to 20+ megs of wasted space.
25927 - The private half of our EDH handshake keys are now chosen out
25928 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
25930 o Security improvements:
25931 - Start making directory caches retain old routerinfos, so soon
25932 clients can start asking by digest of descriptor rather than by
25933 fingerprint of server.
25934 - Add half our entropy from RAND_poll in OpenSSL. This knows how
25935 to use egd (if present), openbsd weirdness (if present), vms/os2
25936 weirdness (if we ever port there), and more in the future.
25938 o Bugfixes on 0.1.0.x:
25939 - Do round-robin writes of at most 16 kB per write. This might be
25940 more fair on loaded Tor servers, and it might resolve our Windows
25941 crash bug. It might also slow things down.
25942 - Our TLS handshakes were generating a single public/private
25943 keypair for the TLS context, rather than making a new one for
25944 each new connections. Oops. (But we were still rotating them
25945 periodically, so it's not so bad.)
25946 - When we were cannibalizing a circuit with a particular exit
25947 node in mind, we weren't checking to see if that exit node was
25948 already present earlier in the circuit. Oops.
25949 - When a Tor server's IP changes (e.g. from a dyndns address),
25950 upload a new descriptor so clients will learn too.
25951 - Really busy servers were keeping enough circuits open on stable
25952 connections that they were wrapping around the circuit_id
25953 space. (It's only two bytes.) This exposed a bug where we would
25954 feel free to reuse a circuit_id even if it still exists but has
25955 been marked for close. Try to fix this bug. Some bug remains.
25956 - If we would close a stream early (e.g. it asks for a .exit that
25957 we know would refuse it) but the LeaveStreamsUnattached config
25958 option is set by the controller, then don't close it.
25960 o Bugfixes on 0.1.1.8-alpha:
25961 - Fix a big pile of memory leaks, some of them serious.
25962 - Do not try to download a routerdesc if we would immediately reject
25964 - Resume inserting a newline between all router descriptors when
25965 generating (old style) signed directories, since our spec says
25967 - When providing content-type application/octet-stream for
25968 server descriptors using .z, we were leaving out the
25969 content-encoding header. Oops. (Everything tolerated this just
25970 fine, but that doesn't mean we need to be part of the problem.)
25971 - Fix a potential seg fault in getconf and getinfo using version 1
25972 of the controller protocol.
25973 - Avoid crash: do not check whether DirPort is reachable when we
25974 are suppressing it because of hibernation.
25975 - Make --hash-password not crash on exit.
25978 Changes in version 0.1.1.8-alpha - 2005-10-07
25979 o New features (major):
25980 - Clients don't download or use the directory anymore. Now they
25981 download and use network-statuses from the trusted dirservers,
25982 and fetch individual server descriptors as needed from mirrors.
25983 See dir-spec.txt for all the gory details.
25984 - Be more conservative about whether to advertise our DirPort.
25985 The main change is to not advertise if we're running at capacity
25986 and either a) we could hibernate or b) our capacity is low and
25987 we're using a default DirPort.
25988 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
25990 o New features (minor):
25991 - Try to be smart about when to retry network-status and
25992 server-descriptor fetches. Still needs some tuning.
25993 - Stop parsing, storing, or using running-routers output (but
25994 mirrors still cache and serve it).
25995 - Consider a threshold of versioning dirservers (dirservers who have
25996 an opinion about which Tor versions are still recommended) before
25997 deciding whether to warn the user that he's obsolete.
25998 - Dirservers can now reject/invalidate by key and IP, with the
25999 config options "AuthDirInvalid" and "AuthDirReject". This is
26000 useful since currently we automatically list servers as running
26001 and usable even if we know they're jerks.
26002 - Provide dire warnings to any users who set DirServer; move it out
26003 of torrc.sample and into torrc.complete.
26004 - Add MyFamily to torrc.sample in the server section.
26005 - Add nicknames to the DirServer line, so we can refer to them
26006 without requiring all our users to memorize their IP addresses.
26007 - When we get an EOF or a timeout on a directory connection, note
26008 how many bytes of serverdesc we are dropping. This will help
26009 us determine whether it is smart to parse incomplete serverdesc
26011 - Add a new function to "change pseudonyms" -- that is, to stop
26012 using any currently-dirty circuits for new streams, so we don't
26013 link new actions to old actions. Currently it's only called on
26014 HUP (or SIGNAL RELOAD).
26015 - On sighup, if UseHelperNodes changed to 1, use new circuits.
26016 - Start using RAND_bytes rather than RAND_pseudo_bytes from
26017 OpenSSL. Also, reseed our entropy every hour, not just at
26018 startup. And entropy in 512-bit chunks, not 160-bit chunks.
26020 o Fixes on 0.1.1.7-alpha:
26021 - Nobody ever implemented EVENT_ADDRMAP for control protocol
26022 version 0, so don't let version 0 controllers ask for it.
26023 - If you requested something with too many newlines via the
26024 v1 controller protocol, you could crash tor.
26025 - Fix a number of memory leaks, including some pretty serious ones.
26026 - Re-enable DirPort testing again, so Tor servers will be willing
26027 to advertise their DirPort if it's reachable.
26028 - On TLS handshake, only check the other router's nickname against
26029 its expected nickname if is_named is set.
26031 o Fixes forward-ported from 0.1.0.15:
26032 - Don't crash when we don't have any spare file descriptors and we
26033 try to spawn a dns or cpu worker.
26034 - Make the numbers in read-history and write-history into uint64s,
26035 so they don't overflow and publish negatives in the descriptor.
26037 o Fixes on 0.1.0.x:
26038 - For the OS X package's modified privoxy config file, comment
26039 out the "logfile" line so we don't log everything passed
26041 - We were whining about using socks4 or socks5-with-local-lookup
26042 even when it's an IP in the "virtual" range we designed exactly
26044 - We were leaking some memory every time the client changes IPs.
26045 - Never call free() on tor_malloc()d memory. This will help us
26046 use dmalloc to detect memory leaks.
26047 - Check for named servers when looking them up by nickname;
26048 warn when we'recalling a non-named server by its nickname;
26049 don't warn twice about the same name.
26050 - Try to list MyFamily elements by key, not by nickname, and warn
26051 if we've not heard of the server.
26052 - Make windows platform detection (uname equivalent) smarter.
26053 - It turns out sparc64 doesn't like unaligned access either.
26056 Changes in version 0.1.0.15 - 2005-09-23
26057 o Bugfixes on 0.1.0.x:
26058 - Reject ports 465 and 587 (spam targets) in default exit policy.
26059 - Don't crash when we don't have any spare file descriptors and we
26060 try to spawn a dns or cpu worker.
26061 - Get rid of IgnoreVersion undocumented config option, and make us
26062 only warn, never exit, when we're running an obsolete version.
26063 - Don't try to print a null string when your server finds itself to
26064 be unreachable and the Address config option is empty.
26065 - Make the numbers in read-history and write-history into uint64s,
26066 so they don't overflow and publish negatives in the descriptor.
26067 - Fix a minor memory leak in smartlist_string_remove().
26068 - We were only allowing ourselves to upload a server descriptor at
26069 most every 20 minutes, even if it changed earlier than that.
26070 - Clean up log entries that pointed to old URLs.
26073 Changes in version 0.1.1.7-alpha - 2005-09-14
26074 o Fixes on 0.1.1.6-alpha:
26075 - Exit servers were crashing when people asked them to make a
26076 connection to an address not in their exit policy.
26077 - Looking up a non-existent stream for a v1 control connection would
26079 - Fix a seg fault if we ask a dirserver for a descriptor by
26080 fingerprint but he doesn't know about him.
26081 - SETCONF was appending items to linelists, not clearing them.
26082 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
26083 out and refuse the setconf if it would fail.
26084 - Downgrade the dirserver log messages when whining about
26088 - Add Peter Palfrader's check-tor script to tor/contrib/
26089 It lets you easily check whether a given server (referenced by
26090 nickname) is reachable by you.
26091 - Numerous changes to move towards client-side v2 directories. Not
26094 o Fixes on 0.1.0.x:
26095 - If the user gave tor an odd number of command-line arguments,
26096 we were silently ignoring the last one. Now we complain and fail.
26097 [This wins the oldest-bug prize -- this bug has been present since
26098 November 2002, as released in Tor 0.0.0.]
26099 - Do not use unaligned memory access on alpha, mips, or mipsel.
26100 It *works*, but is very slow, so we treat them as if it doesn't.
26101 - Retry directory requests if we fail to get an answer we like
26102 from a given dirserver (we were retrying before, but only if
26103 we fail to connect).
26104 - When writing the RecommendedVersions line, sort them first.
26105 - When the client asked for a rendezvous port that the hidden
26106 service didn't want to provide, we were sending an IP address
26107 back along with the end cell. Fortunately, it was zero. But stop
26109 - Correct "your server is reachable" log entries to indicate that
26110 it was self-testing that told us so.
26113 Changes in version 0.1.1.6-alpha - 2005-09-09
26114 o Fixes on 0.1.1.5-alpha:
26115 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
26116 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
26117 - Fix bug with tor_memmem finding a match at the end of the string.
26118 - Make unit tests run without segfaulting.
26119 - Resolve some solaris x86 compile warnings.
26120 - Handle duplicate lines in approved-routers files without warning.
26121 - Fix bug where as soon as a server refused any requests due to his
26122 exit policy (e.g. when we ask for localhost and he tells us that's
26123 127.0.0.1 and he won't do it), we decided he wasn't obeying his
26124 exit policy using him for any exits.
26125 - Only do openssl hardware accelerator stuff if openssl version is
26128 o New controller features/fixes:
26129 - Add a "RESETCONF" command so you can set config options like
26130 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
26131 a config option in the torrc with no value, then it clears it
26132 entirely (rather than setting it to its default).
26133 - Add a "GETINFO config-file" to tell us where torrc is.
26134 - Avoid sending blank lines when GETINFO replies should be empty.
26135 - Add a QUIT command for the controller (for using it manually).
26136 - Fix a bug in SAVECONF that was adding default dirservers and
26137 other redundant entries to the torrc file.
26139 o Start on the new directory design:
26140 - Generate, publish, cache, serve new network-status format.
26141 - Publish individual descriptors (by fingerprint, by "all", and by
26143 - Publish client and server recommended versions separately.
26144 - Allow tor_gzip_uncompress() to handle multiple concatenated
26145 compressed strings. Serve compressed groups of router
26146 descriptors. The compression logic here could be more
26148 - Distinguish v1 authorities (all currently trusted directories)
26149 from v2 authorities (all trusted directories).
26150 - Change DirServers config line to note which dirs are v1 authorities.
26151 - Add configuration option "V1AuthoritativeDirectory 1" which
26152 moria1, moria2, and tor26 should set.
26153 - Remove option when getting directory cache to see whether they
26154 support running-routers; they all do now. Replace it with one
26155 to see whether caches support v2 stuff.
26158 - Dirservers now do their own external reachability testing of each
26159 Tor server, and only list them as running if they've been found to
26160 be reachable. We also send back warnings to the server's logs if
26161 it uploads a descriptor that we already believe is unreachable.
26162 - Implement exit enclaves: if we know an IP address for the
26163 destination, and there's a running Tor server at that address
26164 which allows exit to the destination, then extend the circuit to
26165 that exit first. This provides end-to-end encryption and end-to-end
26166 authentication. Also, if the user wants a .exit address or enclave,
26167 use 4 hops rather than 3, and cannibalize a general circ for it
26169 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
26170 controller. Also, rotate dns and cpu workers if the controller
26171 changes options that will affect them; and initialize the dns
26172 worker cache tree whether or not we start out as a server.
26173 - Only upload a new server descriptor when options change, 18
26174 hours have passed, uptime is reset, or bandwidth changes a lot.
26175 - Check [X-]Forwarded-For headers in HTTP requests when generating
26176 log messages. This lets people run dirservers (and caches) behind
26177 Apache but still know which IP addresses are causing warnings.
26179 o Config option changes:
26180 - Replace (Fascist)Firewall* config options with a new
26181 ReachableAddresses option that understands address policies.
26182 For example, "ReachableAddresses *:80,*:443"
26183 - Get rid of IgnoreVersion undocumented config option, and make us
26184 only warn, never exit, when we're running an obsolete version.
26185 - Make MonthlyAccountingStart config option truly obsolete now.
26187 o Fixes on 0.1.0.x:
26188 - Reject ports 465 and 587 in the default exit policy, since
26189 people have started using them for spam too.
26190 - It turns out we couldn't bootstrap a network since we added
26191 reachability detection in 0.1.0.1-rc. Good thing the Tor network
26192 has never gone down. Add an AssumeReachable config option to let
26193 servers and dirservers bootstrap. When we're trying to build a
26194 high-uptime or high-bandwidth circuit but there aren't enough
26195 suitable servers, try being less picky rather than simply failing.
26196 - Our logic to decide if the OR we connected to was the right guy
26197 was brittle and maybe open to a mitm for unverified routers.
26198 - We weren't cannibalizing circuits correctly for
26199 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
26200 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
26201 build those from scratch. This should make hidden services faster.
26202 - Predict required circuits better, with an eye toward making hidden
26203 services faster on the service end.
26204 - Retry streams if the exit node sends back a 'misc' failure. This
26205 should result in fewer random failures. Also, after failing
26206 from resolve failed or misc, reset the num failures, so we give
26207 it a fair shake next time we try.
26208 - Clean up the rendezvous warn log msgs, and downgrade some to info.
26209 - Reduce severity on logs about dns worker spawning and culling.
26210 - When we're shutting down and we do something like try to post a
26211 server descriptor or rendezvous descriptor, don't complain that
26212 we seem to be unreachable. Of course we are, we're shutting down.
26213 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
26214 We don't use them yet, but maybe one day our DNS resolver will be
26215 able to discover them.
26216 - Make ContactInfo mandatory for authoritative directory servers.
26217 - Require server descriptors to list IPv4 addresses -- hostnames
26218 are no longer allowed. This also fixes some potential security
26219 problems with people providing hostnames as their address and then
26220 preferentially resolving them to partition users.
26221 - Change log line for unreachability to explicitly suggest /etc/hosts
26222 as the culprit. Also make it clearer what IP address and ports we're
26223 testing for reachability.
26224 - Put quotes around user-supplied strings when logging so users are
26225 more likely to realize if they add bad characters (like quotes)
26227 - Let auth dir servers start without specifying an Address config
26229 - Make unit tests (and other invocations that aren't the real Tor)
26230 run without launching listeners, creating subdirectories, and so on.
26233 Changes in version 0.1.1.5-alpha - 2005-08-08
26234 o Bugfixes included in 0.1.0.14.
26236 o Bugfixes on 0.1.0.x:
26237 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
26238 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
26239 it would silently using ignore the 6668.
26242 Changes in version 0.1.0.14 - 2005-08-08
26243 o Bugfixes on 0.1.0.x:
26244 - Fix the other half of the bug with crypto handshakes
26246 - Fix an assert trigger if you send a 'signal term' via the
26247 controller when it's listening for 'event info' messages.
26250 Changes in version 0.1.1.4-alpha - 2005-08-04
26251 o Bugfixes included in 0.1.0.13.
26254 - Improve tor_gettimeofday() granularity on windows.
26255 - Make clients regenerate their keys when their IP address changes.
26256 - Implement some more GETINFO goodness: expose helper nodes, config
26257 options, getinfo keys.
26260 Changes in version 0.1.0.13 - 2005-08-04
26261 o Bugfixes on 0.1.0.x:
26262 - Fix a critical bug in the security of our crypto handshakes.
26263 - Fix a size_t underflow in smartlist_join_strings2() that made
26264 it do bad things when you hand it an empty smartlist.
26265 - Fix Windows installer to ship Tor license (thanks to Aphex for
26266 pointing out this oversight) and put a link to the doc directory
26268 - Explicitly set no-unaligned-access for sparc: it turns out the
26269 new gcc's let you compile broken code, but that doesn't make it
26273 Changes in version 0.1.1.3-alpha - 2005-07-23
26274 o Bugfixes on 0.1.1.2-alpha:
26275 - Fix a bug in handling the controller's "post descriptor"
26277 - Fix several bugs in handling the controller's "extend circuit"
26279 - Fix a bug in handling the controller's "stream status" event.
26280 - Fix an assert failure if we have a controller listening for
26281 circuit events and we go offline.
26282 - Re-allow hidden service descriptors to publish 0 intro points.
26283 - Fix a crash when generating your hidden service descriptor if
26284 you don't have enough intro points already.
26286 o New features on 0.1.1.2-alpha:
26287 - New controller function "getinfo accounting", to ask how
26288 many bytes we've used in this time period.
26289 - Experimental support for helper nodes: a lot of the risk from
26290 a small static adversary comes because users pick new random
26291 nodes every time they rebuild a circuit. Now users will try to
26292 stick to the same small set of entry nodes if they can. Not
26293 enabled by default yet.
26295 o Bugfixes on 0.1.0.12:
26296 - If you're an auth dir server, always publish your dirport,
26297 even if you haven't yet found yourself to be reachable.
26298 - Fix a size_t underflow in smartlist_join_strings2() that made
26299 it do bad things when you hand it an empty smartlist.
26302 Changes in version 0.1.0.12 - 2005-07-18
26303 o New directory servers:
26304 - tor26 has changed IP address.
26306 o Bugfixes on 0.1.0.x:
26307 - Fix a possible double-free in tor_gzip_uncompress().
26308 - When --disable-threads is set, do not search for or link against
26309 pthreads libraries.
26310 - Don't trigger an assert if an authoritative directory server
26311 claims its dirport is 0.
26312 - Fix bug with removing Tor as an NT service: some people were
26313 getting "The service did not return an error." Thanks to Matt
26317 Changes in version 0.1.1.2-alpha - 2005-07-15
26318 o New directory servers:
26319 - tor26 has changed IP address.
26321 o Bugfixes on 0.1.0.x, crashes/leaks:
26322 - Port the servers-not-obeying-their-exit-policies fix from
26324 - Fix an fd leak in start_daemon().
26325 - On Windows, you can't always reopen a port right after you've
26326 closed it. So change retry_listeners() to only close and re-open
26327 ports that have changed.
26328 - Fix a possible double-free in tor_gzip_uncompress().
26330 o Bugfixes on 0.1.0.x, usability:
26331 - When tor_socketpair() fails in Windows, give a reasonable
26332 Windows-style errno back.
26333 - Let people type "tor --install" as well as "tor -install" when
26335 want to make it an NT service.
26336 - NT service patch from Matt Edman to improve error messages.
26337 - When the controller asks for a config option with an abbreviated
26338 name, give the full name in our response.
26339 - Correct the man page entry on TrackHostExitsExpire.
26340 - Looks like we were never delivering deflated (i.e. compressed)
26341 running-routers lists, even when asked. Oops.
26342 - When --disable-threads is set, do not search for or link against
26343 pthreads libraries.
26345 o Bugfixes on 0.1.1.x:
26346 - Fix a seg fault with autodetecting which controller version is
26350 - New hidden service descriptor format: put a version in it, and
26351 let people specify introduction/rendezvous points that aren't
26352 in "the directory" (which is subjective anyway).
26353 - Allow the DEBUG controller event to work again. Mark certain log
26354 entries as "don't tell this to controllers", so we avoid cycles.
26357 Changes in version 0.1.0.11 - 2005-06-30
26358 o Bugfixes on 0.1.0.x:
26359 - Fix major security bug: servers were disregarding their
26360 exit policies if clients behaved unexpectedly.
26361 - Make OS X init script check for missing argument, so we don't
26362 confuse users who invoke it incorrectly.
26363 - Fix a seg fault in "tor --hash-password foo".
26364 - The MAPADDRESS control command was broken.
26367 Changes in version 0.1.1.1-alpha - 2005-06-29
26369 - Make OS X init script check for missing argument, so we don't
26370 confuse users who invoke it incorrectly.
26371 - Fix a seg fault in "tor --hash-password foo".
26372 - Fix a possible way to DoS dirservers.
26373 - When we complain that your exit policy implicitly allows local or
26374 private address spaces, name them explicitly so operators can
26376 - Make the log message less scary when all the dirservers are
26377 temporarily unreachable.
26378 - We were printing the number of idle dns workers incorrectly when
26382 - Revised controller protocol (version 1) that uses ascii rather
26383 than binary. Add supporting libraries in python and java so you
26384 can use the controller from your applications without caring how
26385 our protocol works.
26386 - Spiffy new support for crypto hardware accelerators. Can somebody
26390 Changes in version 0.0.9.10 - 2005-06-16
26391 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
26392 - Refuse relay cells that claim to have a length larger than the
26393 maximum allowed. This prevents a potential attack that could read
26394 arbitrary memory (e.g. keys) from an exit server's process
26398 Changes in version 0.1.0.10 - 2005-06-14
26399 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
26400 libevent before 1.1a.
26403 Changes in version 0.1.0.9-rc - 2005-06-09
26405 - Reset buf->highwater every time buf_shrink() is called, not just on
26406 a successful shrink. This was causing significant memory bloat.
26407 - Fix buffer overflow when checking hashed passwords.
26408 - Security fix: if seeding the RNG on Win32 fails, quit.
26409 - Allow seeding the RNG on Win32 even when you're not running as
26411 - Disable threading on Solaris too. Something is wonky with it,
26412 cpuworkers, and reentrant libs.
26413 - Reenable the part of the code that tries to flush as soon as an
26414 OR outbuf has a full TLS record available. Perhaps this will make
26415 OR outbufs not grow as huge except in rare cases, thus saving lots
26416 of CPU time plus memory.
26417 - Reject malformed .onion addresses rather then passing them on as
26418 normal web requests.
26419 - Adapt patch from Adam Langley: fix possible memory leak in
26420 tor_lookup_hostname().
26421 - Initialize libevent later in the startup process, so the logs are
26422 already established by the time we start logging libevent warns.
26423 - Use correct errno on win32 if libevent fails.
26424 - Check and warn about known-bad/slow libevent versions.
26425 - Pay more attention to the ClientOnly config option.
26426 - Have torctl.in/tor.sh.in check for location of su binary (needed
26428 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
26429 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
26430 HttpProxyAuthenticator
26431 - Stop warning about sigpipes in the logs. We're going to
26432 pretend that getting these occasionally is normal and fine.
26433 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
26435 installer screens; and don't put stuff into StartupItems unless
26436 the user asks you to.
26437 - Require servers that use the default dirservers to have public IP
26438 addresses. We have too many servers that are configured with private
26439 IPs and their admins never notice the log entries complaining that
26440 their descriptors are being rejected.
26441 - Add OSX uninstall instructions. An actual uninstall script will
26445 Changes in version 0.1.0.8-rc - 2005-05-23
26447 - It turns out that kqueue on OS X 10.3.9 was causing kernel
26448 panics. Disable kqueue on all OS X Tors.
26449 - Fix RPM: remove duplicate line accidentally added to the rpm
26451 - Disable threads on openbsd too, since its gethostaddr is not
26453 - Tolerate libevent 0.8 since it still works, even though it's
26455 - Enable building on Red Hat 9.0 again.
26456 - Allow the middle hop of the testing circuit to be running any
26457 version, now that most of them have the bugfix to let them connect
26458 to unknown servers. This will allow reachability testing to work
26459 even when 0.0.9.7-0.0.9.9 become obsolete.
26460 - Handle relay cells with rh.length too large. This prevents
26461 a potential attack that could read arbitrary memory (maybe even
26462 keys) from the exit server's process.
26463 - We screwed up the dirport reachability testing when we don't yet
26464 have a cached version of the directory. Hopefully now fixed.
26465 - Clean up router_load_single_router() (used by the controller),
26466 so it doesn't seg fault on error.
26467 - Fix a minor memory leak when somebody establishes an introduction
26468 point at your Tor server.
26469 - If a socks connection ends because read fails, don't warn that
26470 you're not sending a socks reply back.
26473 - Add HttpProxyAuthenticator config option too, that works like
26474 the HttpsProxyAuthenticator config option.
26475 - Encode hashed controller passwords in hex instead of base64,
26476 to make it easier to write controllers.
26479 Changes in version 0.1.0.7-rc - 2005-05-17
26481 - Fix a bug in the OS X package installer that prevented it from
26482 installing on Tiger.
26483 - Fix a script bug in the OS X package installer that made it
26484 complain during installation.
26485 - Find libevent even if it's hiding in /usr/local/ and your
26486 CFLAGS and LDFLAGS don't tell you to look there.
26487 - Be able to link with libevent as a shared library (the default
26488 after 1.0d), even if it's hiding in /usr/local/lib and even
26489 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
26490 assuming you're running gcc. Otherwise fail and give a useful
26492 - Fix a bug in the RPM packager: set home directory for _tor to
26493 something more reasonable when first installing.
26494 - Free a minor amount of memory that is still reachable on exit.
26497 Changes in version 0.1.0.6-rc - 2005-05-14
26499 - Implement --disable-threads configure option. Disable threads on
26500 netbsd by default, because it appears to have no reentrant resolver
26502 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
26503 release (1.1) detects and disables kqueue if it's broken.
26504 - Append default exit policy before checking for implicit internal
26505 addresses. Now we don't log a bunch of complaints on startup
26506 when using the default exit policy.
26507 - Some people were putting "Address " in their torrc, and they had
26508 a buggy resolver that resolved " " to 0.0.0.0. Oops.
26509 - If DataDir is ~/.tor, and that expands to /.tor, then default to
26510 LOCALSTATEDIR/tor instead.
26511 - Fix fragmented-message bug in TorControl.py.
26512 - Resolve a minor bug which would prevent unreachable dirports
26513 from getting suppressed in the published descriptor.
26514 - When the controller gave us a new descriptor, we weren't resolving
26515 it immediately, so Tor would think its address was 0.0.0.0 until
26516 we fetched a new directory.
26517 - Fix an uppercase/lowercase case error in suppressing a bogus
26518 libevent warning on some Linuxes.
26521 - Begin scrubbing sensitive strings from logs by default. Turn off
26522 the config option SafeLogging if you need to do debugging.
26523 - Switch to a new buffer management algorithm, which tries to avoid
26524 reallocing and copying quite as much. In first tests it looks like
26525 it uses *more* memory on average, but less cpu.
26526 - First cut at support for "create-fast" cells. Clients can use
26527 these when extending to their first hop, since the TLS already
26528 provides forward secrecy and authentication. Not enabled on
26530 - When dirservers refuse a router descriptor, we now log its
26531 contactinfo, platform, and the poster's IP address.
26532 - Call tor_free_all instead of connections_free_all after forking, to
26533 save memory on systems that need to fork.
26534 - Whine at you if you're a server and you don't set your contactinfo.
26535 - Implement --verify-config command-line option to check if your torrc
26536 is valid without actually launching Tor.
26537 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
26538 rather than just rejecting it.
26541 Changes in version 0.1.0.5-rc - 2005-04-27
26543 - Stop trying to print a null pointer if an OR conn fails because
26544 we didn't like its cert.
26546 - Switch our internal buffers implementation to use a ring buffer,
26547 to hopefully improve performance for fast servers a lot.
26548 - Add HttpsProxyAuthenticator support (basic auth only), based
26549 on patch from Adam Langley.
26550 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
26551 the fast servers that have been joining lately.
26552 - Give hidden service accesses extra time on the first attempt,
26553 since 60 seconds is often only barely enough. This might improve
26555 - Improve performance for dirservers: stop re-parsing the whole
26556 directory every time you regenerate it.
26557 - Add more debugging info to help us find the weird dns freebsd
26558 pthreads bug; cleaner debug messages to help track future issues.
26561 Changes in version 0.0.9.9 - 2005-04-23
26562 o Bugfixes on 0.0.9.x:
26563 - If unofficial Tor clients connect and send weird TLS certs, our
26564 Tor server triggers an assert. This release contains a minimal
26565 backport from the broader fix that we put into 0.1.0.4-rc.
26568 Changes in version 0.1.0.4-rc - 2005-04-23
26570 - If unofficial Tor clients connect and send weird TLS certs, our
26571 Tor server triggers an assert. Stop asserting, and start handling
26572 TLS errors better in other situations too.
26573 - When the controller asks us to tell it about all the debug-level
26574 logs, it turns out we were generating debug-level logs while
26575 telling it about them, which turns into a bad loop. Now keep
26576 track of whether you're sending a debug log to the controller,
26577 and don't log when you are.
26578 - Fix the "postdescriptor" feature of the controller interface: on
26579 non-complete success, only say "done" once.
26581 - Clients are now willing to load balance over up to 2mB, not 1mB,
26582 of advertised bandwidth capacity.
26583 - Add a NoPublish config option, so you can be a server (e.g. for
26584 testing running Tor servers in other Tor networks) without
26585 publishing your descriptor to the primary dirservers.
26588 Changes in version 0.1.0.3-rc - 2005-04-08
26589 o Improvements on 0.1.0.2-rc:
26590 - Client now retries when streams end early for 'hibernating' or
26591 'resource limit' reasons, rather than failing them.
26592 - More automated handling for dirserver operators:
26593 - Automatically approve nodes running 0.1.0.2-rc or later,
26594 now that the the reachability detection stuff is working.
26595 - Now we allow two unverified servers with the same nickname
26596 but different keys. But if a nickname is verified, only that
26597 nickname+key are allowed.
26598 - If you're an authdirserver connecting to an address:port,
26599 and it's not the OR you were expecting, forget about that
26600 descriptor. If he *was* the one you were expecting, then forget
26601 about all other descriptors for that address:port.
26602 - Allow servers to publish descriptors from 12 hours in the future.
26603 Corollary: only whine about clock skew from the dirserver if
26604 he's a trusted dirserver (since now even verified servers could
26605 have quite wrong clocks).
26606 - Adjust maximum skew and age for rendezvous descriptors: let skew
26607 be 48 hours rather than 90 minutes.
26608 - Efficiency improvements:
26609 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
26610 it much faster to look up a circuit for each relay cell.
26611 - Remove most calls to assert_all_pending_dns_resolves_ok(),
26612 since they're eating our cpu on exit nodes.
26613 - Stop wasting time doing a case insensitive comparison for every
26614 dns name every time we do any lookup. Canonicalize the names to
26615 lowercase and be done with it.
26616 - Start sending 'truncated' cells back rather than destroy cells,
26617 if the circuit closes in front of you. This means we won't have
26618 to abandon partially built circuits.
26619 - Only warn once per nickname from add_nickname_list_to_smartlist
26620 per failure, so an entrynode or exitnode choice that's down won't
26622 - Put a note in the torrc about abuse potential with the default
26624 - Revise control spec and implementation to allow all log messages to
26625 be sent to controller with their severities intact (suggested by
26626 Matt Edman). Update TorControl to handle new log event types.
26627 - Provide better explanation messages when controller's POSTDESCRIPTOR
26629 - Stop putting nodename in the Platform string in server descriptors.
26630 It doesn't actually help, and it is confusing/upsetting some people.
26632 o Bugfixes on 0.1.0.2-rc:
26633 - We were printing the host mask wrong in exit policies in server
26634 descriptors. This isn't a critical bug though, since we were still
26635 obeying the exit policy internally.
26636 - Fix Tor when compiled with libevent but without pthreads: move
26637 connection_unregister() from _connection_free() to
26639 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
26640 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
26641 when we look through the connection array, we'll find any of the
26642 cpu/dnsworkers. This is no good.
26644 o Bugfixes on 0.0.9.8:
26645 - Fix possible bug on threading platforms (e.g. win32) which was
26646 leaking a file descriptor whenever a cpuworker or dnsworker died.
26647 - When using preferred entry or exit nodes, ignore whether the
26648 circuit wants uptime or capacity. They asked for the nodes, they
26650 - chdir() to your datadirectory at the *end* of the daemonize process,
26651 not the beginning. This was a problem because the first time you
26652 run tor, if your datadir isn't there, and you have runasdaemon set
26653 to 1, it will try to chdir to it before it tries to create it. Oops.
26654 - Handle changed router status correctly when dirserver reloads
26655 fingerprint file. We used to be dropping all unverified descriptors
26656 right then. The bug was hidden because we would immediately
26657 fetch a directory from another dirserver, which would include the
26658 descriptors we just dropped.
26659 - When we're connecting to an OR and he's got a different nickname/key
26660 than we were expecting, only complain loudly if we're an OP or a
26661 dirserver. Complaining loudly to the OR admins just confuses them.
26662 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
26663 artificially capped at 500kB.
26666 Changes in version 0.0.9.8 - 2005-04-07
26667 o Bugfixes on 0.0.9.x:
26668 - We have a bug that I haven't found yet. Sometimes, very rarely,
26669 cpuworkers get stuck in the 'busy' state, even though the cpuworker
26670 thinks of itself as idle. This meant that no new circuits ever got
26671 established. Here's a workaround to kill any cpuworker that's been
26672 busy for more than 100 seconds.
26675 Changes in version 0.1.0.2-rc - 2005-04-01
26676 o Bugfixes on 0.1.0.1-rc:
26677 - Fixes on reachability detection:
26678 - Don't check for reachability while hibernating.
26679 - If ORPort is reachable but DirPort isn't, still publish the
26680 descriptor, but zero out DirPort until it's found reachable.
26681 - When building testing circs for ORPort testing, use only
26682 high-bandwidth nodes, so fewer circuits fail.
26683 - Complain about unreachable ORPort separately from unreachable
26684 DirPort, so the user knows what's going on.
26685 - Make sure we only conclude ORPort reachability if we didn't
26686 initiate the conn. Otherwise we could falsely conclude that
26687 we're reachable just because we connected to the guy earlier
26688 and he used that same pipe to extend to us.
26689 - Authdirservers shouldn't do ORPort reachability detection,
26690 since they're in clique mode, so it will be rare to find a
26691 server not already connected to them.
26692 - When building testing circuits, always pick middle hops running
26693 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
26694 bug. (This is a kludge; it will go away when 0.0.9.x becomes
26696 - When we decide we're reachable, actually publish our descriptor
26698 - Fix bug in redirectstream in the controller.
26699 - Fix the state descriptor strings so logs don't claim edge streams
26700 are in a different state than they actually are.
26701 - Use recent libevent features when possible (this only really affects
26702 win32 and osx right now, because the new libevent with these
26703 features hasn't been released yet). Add code to suppress spurious
26705 - Prevent possible segfault in connection_close_unattached_ap().
26706 - Fix newlines on torrc in win32.
26707 - Improve error msgs when tor-resolve fails.
26709 o Improvements on 0.0.9.x:
26710 - New experimental script tor/contrib/ExerciseServer.py (needs more
26711 work) that uses the controller interface to build circuits and
26712 fetch pages over them. This will help us bootstrap servers that
26713 have lots of capacity but haven't noticed it yet.
26714 - New experimental script tor/contrib/PathDemo.py (needs more work)
26715 that uses the controller interface to let you choose whole paths
26717 "<hostname>.<path,separated by dots>.<length of path>.path"
26718 - When we've connected to an OR and handshaked but didn't like
26719 the result, we were closing the conn without sending destroy
26720 cells back for pending circuits. Now send those destroys.
26723 Changes in version 0.0.9.7 - 2005-04-01
26724 o Bugfixes on 0.0.9.x:
26725 - Fix another race crash bug (thanks to Glenn Fink for reporting).
26726 - Compare identity to identity, not to nickname, when extending to
26727 a router not already in the directory. This was preventing us from
26728 extending to unknown routers. Oops.
26729 - Make sure to create OS X Tor user in <500 range, so we aren't
26730 creating actual system users.
26731 - Note where connection-that-hasn't-sent-end was marked, and fix
26732 a few really loud instances of this harmless bug (it's fixed more
26736 Changes in version 0.1.0.1-rc - 2005-03-28
26738 - Add reachability testing. Your Tor server will automatically try
26739 to see if its ORPort and DirPort are reachable from the outside,
26740 and it won't upload its descriptor until it decides they are.
26741 - Handle unavailable hidden services better. Handle slow or busy
26742 hidden services better.
26743 - Add support for CONNECTing through https proxies, with "HttpsProxy"
26745 - New exit policy: accept most low-numbered ports, rather than
26746 rejecting most low-numbered ports.
26747 - More Tor controller support (still experimental). See
26748 http://tor.eff.org/doc/control-spec.txt for all the new features,
26749 including signals to emulate unix signals from any platform;
26750 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
26751 closestream; closecircuit; etc.
26752 - Make nt services work and start on startup on win32 (based on
26753 patch by Matt Edman).
26754 - Add a new AddressMap config directive to rewrite incoming socks
26755 addresses. This lets you, for example, declare an implicit
26756 required exit node for certain sites.
26757 - Add a new TrackHostExits config directive to trigger addressmaps
26758 for certain incoming socks addresses -- for sites that break when
26759 your exit keeps changing (based on patch by Mike Perry).
26760 - Redo the client-side dns cache so it's just an addressmap too.
26761 - Notice when our IP changes, and reset stats/uptime/reachability.
26762 - When an application is using socks5, give him the whole variety of
26763 potential socks5 responses (connect refused, host unreachable, etc),
26764 rather than just "success" or "failure".
26765 - A more sane version numbering system. See
26766 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
26767 - New contributed script "exitlist": a simple python script to
26768 parse directories and find Tor nodes that exit to listed
26770 - New contributed script "privoxy-tor-toggle" to toggle whether
26771 Privoxy uses Tor. Seems to be configured for Debian by default.
26772 - Report HTTP reasons to client when getting a response from directory
26773 servers -- so you can actually know what went wrong.
26774 - New config option MaxAdvertisedBandwidth which lets you advertise
26775 a low bandwidthrate (to not attract as many circuits) while still
26776 allowing a higher bandwidthrate in reality.
26778 o Robustness/stability fixes:
26779 - Make Tor use Niels Provos's libevent instead of its current
26780 poll-but-sometimes-select mess. This will let us use faster async
26781 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
26783 - pthread support now too. This was forced because when we forked,
26784 we ended up wasting a lot of duplicate ram over time. Also switch
26785 to foo_r versions of some library calls to allow reentry and
26787 - Better handling for heterogeneous / unreliable nodes:
26788 - Annotate circuits w/ whether they aim to contain high uptime nodes
26789 and/or high capacity nodes. When building circuits, choose
26791 - This means that every single node in an intro rend circuit,
26792 not just the last one, will have a minimum uptime.
26793 - New config option LongLivedPorts to indicate application streams
26794 that will want high uptime circuits.
26795 - Servers reset uptime when a dir fetch entirely fails. This
26796 hopefully reflects stability of the server's network connectivity.
26797 - If somebody starts his tor server in Jan 2004 and then fixes his
26798 clock, don't make his published uptime be a year.
26799 - Reset published uptime when you wake up from hibernation.
26800 - Introduce a notion of 'internal' circs, which are chosen without
26801 regard to the exit policy of the last hop. Intro and rendezvous
26802 circs must be internal circs, to avoid leaking information. Resolve
26803 and connect streams can use internal circs if they want.
26804 - New circuit pooling algorithm: make sure to have enough circs around
26805 to satisfy any predicted ports, and also make sure to have 2 internal
26806 circs around if we've required internal circs lately (and with high
26807 uptime if we've seen that lately too).
26808 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
26809 which describes how often we retry making new circuits if current
26810 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
26811 how long we're willing to make use of an already-dirty circuit.
26812 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
26813 circ as necessary, if there are any completed ones lying around
26814 when we try to launch one.
26815 - Make hidden services try to establish a rendezvous for 30 seconds,
26816 rather than for n (where n=3) attempts to build a circuit.
26817 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
26818 "ShutdownWaitLength".
26819 - Try to be more zealous about calling connection_edge_end when
26820 things go bad with edge conns in connection.c.
26821 - Revise tor-spec to add more/better stream end reasons.
26822 - Revise all calls to connection_edge_end to avoid sending "misc",
26823 and to take errno into account where possible.
26826 - Fix a race condition that can trigger an assert, when we have a
26827 pending create cell and an OR connection fails right then.
26828 - Fix several double-mark-for-close bugs, e.g. where we were finding
26829 a conn for a cell even if that conn is already marked for close.
26830 - Make sequence of log messages when starting on win32 with no config
26831 file more reasonable.
26832 - When choosing an exit node for a new non-internal circ, don't take
26833 into account whether it'll be useful for any pending x.onion
26834 addresses -- it won't.
26835 - Turn addr_policy_compare from a tristate to a quadstate; this should
26836 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
26837 for google.com" problem.
26838 - Make "platform" string in descriptor more accurate for Win32 servers,
26839 so it's not just "unknown platform".
26840 - Fix an edge case in parsing config options (thanks weasel).
26841 If they say "--" on the commandline, it's not an option.
26842 - Reject odd-looking addresses at the client (e.g. addresses that
26843 contain a colon), rather than having the server drop them because
26845 - tor-resolve requests were ignoring .exit if there was a working circuit
26846 they could use instead.
26847 - REUSEADDR on normal platforms means you can rebind to the port
26848 right after somebody else has let it go. But REUSEADDR on win32
26849 means to let you bind to the port _even when somebody else
26850 already has it bound_! So, don't do that on Win32.
26851 - Change version parsing logic: a version is "obsolete" if it is not
26852 recommended and (1) there is a newer recommended version in the
26853 same series, or (2) there are no recommended versions in the same
26854 series, but there are some recommended versions in a newer series.
26855 A version is "new" if it is newer than any recommended version in
26857 - Stop most cases of hanging up on a socks connection without sending
26861 - Require BandwidthRate to be at least 20kB/s for servers.
26862 - When a dirserver causes you to give a warn, mention which dirserver
26864 - New config option DirAllowPrivateAddresses for authdirservers.
26865 Now by default they refuse router descriptors that have non-IP or
26866 private-IP addresses.
26867 - Stop publishing socksport in the directory, since it's not
26868 actually meant to be public. For compatibility, publish a 0 there
26870 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
26871 smart" value, that is low for servers and high for clients.
26872 - If our clock jumps forward by 100 seconds or more, assume something
26873 has gone wrong with our network and abandon all not-yet-used circs.
26874 - Warn when exit policy implicitly allows local addresses.
26875 - If we get an incredibly skewed timestamp from a dirserver mirror
26876 that isn't a verified OR, don't warn -- it's probably him that's
26878 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
26879 cookies to disk and doesn't log each web request to disk. (Thanks
26880 to Brett Carrington for pointing this out.)
26881 - When a client asks us for a dir mirror and we don't have one,
26882 launch an attempt to get a fresh one.
26883 - If we're hibernating and we get a SIGINT, exit immediately.
26884 - Add --with-dmalloc ./configure option, to track memory leaks.
26885 - And try to free all memory on closing, so we can detect what
26887 - Cache local dns resolves correctly even when they're .exit
26889 - Give a better warning when some other server advertises an
26890 ORPort that is actually an apache running ssl.
26891 - Add "opt hibernating 1" to server descriptor to make it clearer
26892 whether the server is hibernating.
26895 Changes in version 0.0.9.6 - 2005-03-24
26896 o Bugfixes on 0.0.9.x (crashes and asserts):
26897 - Add new end stream reasons to maintenance branch. Fix bug where
26898 reason (8) could trigger an assert. Prevent bug from recurring.
26899 - Apparently win32 stat wants paths to not end with a slash.
26900 - Fix assert triggers in assert_cpath_layer_ok(), where we were
26901 blowing away the circuit that conn->cpath_layer points to, then
26902 checking to see if the circ is well-formed. Backport check to make
26903 sure we dont use the cpath on a closed connection.
26904 - Prevent circuit_resume_edge_reading_helper() from trying to package
26905 inbufs for marked-for-close streams.
26906 - Don't crash on hup if your options->address has become unresolvable.
26907 - Some systems (like OS X) sometimes accept() a connection and tell
26908 you the remote host is 0.0.0.0:0. If this happens, due to some
26909 other mis-features, we get confused; so refuse the conn for now.
26911 o Bugfixes on 0.0.9.x (other):
26912 - Fix harmless but scary "Unrecognized content encoding" warn message.
26913 - Add new stream error reason: TORPROTOCOL reason means "you are not
26914 speaking a version of Tor I understand; say bye-bye to your stream."
26915 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
26916 into the future, now that we are more tolerant of skew. This
26917 resolves a bug where a Tor server would refuse to cache a directory
26918 because all the directories it gets are too far in the future;
26919 yet the Tor server never logs any complaints about clock skew.
26920 - Mac packaging magic: make man pages useable, and do not overwrite
26921 existing torrc files.
26922 - Make OS X log happily to /var/log/tor/tor.log
26925 Changes in version 0.0.9.5 - 2005-02-22
26926 o Bugfixes on 0.0.9.x:
26927 - Fix an assert race at exit nodes when resolve requests fail.
26928 - Stop picking unverified dir mirrors--it only leads to misery.
26929 - Patch from Matt Edman to make NT services work better. Service
26930 support is still not compiled into the executable by default.
26931 - Patch from Dmitri Bely so the Tor service runs better under
26932 the win32 SYSTEM account.
26933 - Make tor-resolve actually work (?) on Win32.
26934 - Fix a sign bug when getrlimit claims to have 4+ billion
26935 file descriptors available.
26936 - Stop refusing to start when bandwidthburst == bandwidthrate.
26937 - When create cells have been on the onion queue more than five
26938 seconds, just send back a destroy and take them off the list.
26941 Changes in version 0.0.9.4 - 2005-02-03
26942 o Bugfixes on 0.0.9:
26943 - Fix an assert bug that took down most of our servers: when
26944 a server claims to have 1 GB of bandwidthburst, don't
26946 - Don't crash as badly if we have spawned the max allowed number
26947 of dnsworkers, or we're out of file descriptors.
26948 - Block more file-sharing ports in the default exit policy.
26949 - MaxConn is now automatically set to the hard limit of max
26950 file descriptors we're allowed (ulimit -n), minus a few for
26952 - Give a clearer message when servers need to raise their
26953 ulimit -n when they start running out of file descriptors.
26954 - SGI Compatibility patches from Jan Schaumann.
26955 - Tolerate a corrupt cached directory better.
26956 - When a dirserver hasn't approved your server, list which one.
26957 - Go into soft hibernation after 95% of the bandwidth is used,
26958 not 99%. This is especially important for daily hibernators who
26959 have a small accounting max. Hopefully it will result in fewer
26960 cut connections when the hard hibernation starts.
26961 - Load-balance better when using servers that claim more than
26962 800kB/s of capacity.
26963 - Make NT services work (experimental, only used if compiled in).
26966 Changes in version 0.0.9.3 - 2005-01-21
26967 o Bugfixes on 0.0.9:
26968 - Backport the cpu use fixes from main branch, so busy servers won't
26969 need as much processor time.
26970 - Work better when we go offline and then come back, or when we
26971 run Tor at boot before the network is up. We do this by
26972 optimistically trying to fetch a new directory whenever an
26973 application request comes in and we think we're offline -- the
26974 human is hopefully a good measure of when the network is back.
26975 - Backport some minimal hidserv bugfixes: keep rend circuits open as
26976 long as you keep using them; actually publish hidserv descriptors
26977 shortly after they change, rather than waiting 20-40 minutes.
26978 - Enable Mac startup script by default.
26979 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
26980 - When you update AllowUnverifiedNodes or FirewallPorts via the
26981 controller's setconf feature, we were always appending, never
26983 - When you update HiddenServiceDir via setconf, it was screwing up
26984 the order of reading the lines, making it fail.
26985 - Do not rewrite a cached directory back to the cache; otherwise we
26986 will think it is recent and not fetch a newer one on startup.
26987 - Workaround for webservers that lie about Content-Encoding: Tor
26988 now tries to autodetect compressed directories and compression
26989 itself. This lets us Proxypass dir fetches through apache.
26992 Changes in version 0.0.9.2 - 2005-01-04
26993 o Bugfixes on 0.0.9 (crashes and asserts):
26994 - Fix an assert on startup when the disk is full and you're logging
26996 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
26997 style address, then we'd crash.
26998 - Fix an assert trigger when the running-routers string we get from
26999 a dirserver is broken.
27000 - Make worker threads start and run on win32. Now win32 servers
27002 - Bandaid (not actually fix, but now it doesn't crash) an assert
27003 where the dns worker dies mysteriously and the main Tor process
27004 doesn't remember anything about the address it was resolving.
27006 o Bugfixes on 0.0.9 (Win32):
27007 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
27008 name out of the warning/assert messages.
27009 - Fix a superficial "unhandled error on read" bug on win32.
27010 - The win32 installer no longer requires a click-through for our
27011 license, since our Free Software license grants rights but does not
27013 - Win32: When connecting to a dirserver fails, try another one
27014 immediately. (This was already working for non-win32 Tors.)
27015 - Stop trying to parse $HOME on win32 when hunting for default
27017 - Make tor-resolve.c work on win32 by calling network_init().
27019 o Bugfixes on 0.0.9 (other):
27020 - Make 0.0.9.x build on Solaris again.
27021 - Due to a fencepost error, we were blowing away the \n when reporting
27022 confvalue items in the controller. So asking for multiple config
27023 values at once couldn't work.
27024 - When listing circuits that are pending on an opening OR connection,
27025 if we're an OR we were listing circuits that *end* at us as
27026 being pending on every listener, dns/cpu worker, etc. Stop that.
27027 - Dirservers were failing to create 'running-routers' or 'directory'
27028 strings if we had more than some threshold of routers. Fix them so
27029 they can handle any number of routers.
27030 - Fix a superficial "Duplicate mark for close" bug.
27031 - Stop checking for clock skew for OR connections, even for servers.
27032 - Fix a fencepost error that was chopping off the last letter of any
27033 nickname that is the maximum allowed nickname length.
27034 - Update URLs in log messages so they point to the new website.
27035 - Fix a potential problem in mangling server private keys while
27036 writing to disk (not triggered yet, as far as we know).
27037 - Include the licenses for other free software we include in Tor,
27038 now that we're shipping binary distributions more regularly.
27041 Changes in version 0.0.9.1 - 2004-12-15
27042 o Bugfixes on 0.0.9:
27043 - Make hibernation actually work.
27044 - Make HashedControlPassword config option work.
27045 - When we're reporting event circuit status to a controller,
27046 don't use the stream status code.
27049 Changes in version 0.0.9 - 2004-12-12
27051 - Clean up manpage and torrc.sample file.
27052 - Clean up severities and text of log warnings.
27054 - Make servers trigger an assert when they enter hibernation.
27057 Changes in version 0.0.9rc7 - 2004-12-08
27058 o Bugfixes on 0.0.9rc:
27059 - Fix a stack-trashing crash when an exit node begins hibernating.
27060 - Avoid looking at unallocated memory while considering which
27061 ports we need to build circuits to cover.
27062 - Stop a sigpipe: when an 'end' cell races with eof from the app,
27063 we shouldn't hold-open-until-flush if the eof arrived first.
27064 - Fix a bug with init_cookie_authentication() in the controller.
27065 - When recommending new-format log lines, if the upper bound is
27066 LOG_ERR, leave it implicit.
27068 o Bugfixes on 0.0.8.1:
27069 - Fix a whole slew of memory leaks.
27070 - Fix isspace() and friends so they still make Solaris happy
27071 but also so they don't trigger asserts on win32.
27072 - Fix parse_iso_time on platforms without strptime (eg win32).
27073 - win32: tolerate extra "readable" events better.
27074 - win32: when being multithreaded, leave parent fdarray open.
27075 - Make unit tests work on win32.
27078 Changes in version 0.0.9rc6 - 2004-12-06
27079 o Bugfixes on 0.0.9pre:
27080 - Clean up some more integer underflow opportunities (not exploitable
27082 - While hibernating, hup should not regrow our listeners.
27083 - Send an end to the streams we close when we hibernate, rather
27084 than just chopping them off.
27085 - React to eof immediately on non-open edge connections.
27087 o Bugfixes on 0.0.8.1:
27088 - Calculate timeout for waiting for a connected cell from the time
27089 we sent the begin cell, not from the time the stream started. If
27090 it took a long time to establish the circuit, we would time out
27091 right after sending the begin cell.
27092 - Fix router_compare_addr_to_addr_policy: it was not treating a port
27093 of * as always matching, so we were picking reject *:* nodes as
27094 exit nodes too. Oops.
27097 - New circuit building strategy: keep a list of ports that we've
27098 used in the past 6 hours, and always try to have 2 circuits open
27099 or on the way that will handle each such port. Seed us with port
27100 80 so web users won't complain that Tor is "slow to start up".
27101 - Make kill -USR1 dump more useful stats about circuits.
27102 - When warning about retrying or giving up, print the address, so
27103 the user knows which one it's talking about.
27104 - If you haven't used a clean circuit in an hour, throw it away,
27105 just to be on the safe side. (This means after 6 hours a totally
27106 unused Tor client will have no circuits open.)
27109 Changes in version 0.0.9rc5 - 2004-12-01
27110 o Bugfixes on 0.0.8.1:
27111 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
27112 - Let resolve conns retry/expire also, rather than sticking around
27114 - If we are using select, make sure we stay within FD_SETSIZE.
27116 o Bugfixes on 0.0.9pre:
27117 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
27118 but doesn't seem to be currently; thanks to Ilja van Sprundel for
27120 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
27121 instead. Impose minima and maxima for all *Period options; impose
27122 even tighter maxima for fetching if we are a caching dirserver.
27123 Clip rather than rejecting.
27124 - Fetch cached running-routers from servers that serve it (that is,
27125 authdirservers and servers running 0.0.9rc5-cvs or later.)
27128 - Accept *:706 (silc) in default exit policy.
27129 - Implement new versioning format for post 0.1.
27130 - Support "foo.nickname.exit" addresses, to let Alice request the
27131 address "foo" as viewed by exit node "nickname". Based on a patch
27133 - Make tor --version --version dump the cvs Id of every file.
27136 Changes in version 0.0.9rc4 - 2004-11-28
27137 o Bugfixes on 0.0.8.1:
27138 - Make windows sockets actually non-blocking (oops), and handle
27139 win32 socket errors better.
27141 o Bugfixes on 0.0.9rc1:
27142 - Actually catch the -USR2 signal.
27145 Changes in version 0.0.9rc3 - 2004-11-25
27146 o Bugfixes on 0.0.8.1:
27147 - Flush the log file descriptor after we print "Tor opening log file",
27148 so we don't see those messages days later.
27150 o Bugfixes on 0.0.9rc1:
27151 - Make tor-resolve work again.
27152 - Avoid infinite loop in tor-resolve if tor hangs up on it.
27153 - Fix an assert trigger for clients/servers handling resolves.
27156 Changes in version 0.0.9rc2 - 2004-11-24
27157 o Bugfixes on 0.0.9rc1:
27158 - I broke socks5 support while fixing the eof bug.
27159 - Allow unitless bandwidths and intervals; they default to bytes
27161 - New servers don't start out hibernating; they are active until
27162 they run out of bytes, so they have a better estimate of how
27163 long it takes, and so their operators can know they're working.
27166 Changes in version 0.0.9rc1 - 2004-11-23
27167 o Bugfixes on 0.0.8.1:
27168 - Finally fix a bug that's been plaguing us for a year:
27169 With high load, circuit package window was reaching 0. Whenever
27170 we got a circuit-level sendme, we were reading a lot on each
27171 socket, but only writing out a bit. So we would eventually reach
27172 eof. This would be noticed and acted on even when there were still
27173 bytes sitting in the inbuf.
27174 - When poll() is interrupted, we shouldn't believe the revents values.
27176 o Bugfixes on 0.0.9pre6:
27177 - Fix hibernate bug that caused pre6 to be broken.
27178 - Don't keep rephist info for routers that haven't had activity for
27179 24 hours. (This matters now that clients have keys, since we track
27181 - Never call close_temp_logs while validating log options.
27182 - Fix backslash-escaping on tor.sh.in and torctl.in.
27185 - Implement weekly/monthly/daily accounting: now you specify your
27186 hibernation properties by
27187 AccountingMax N bytes|KB|MB|GB|TB
27188 AccountingStart day|week|month [day] HH:MM
27189 Defaults to "month 1 0:00".
27190 - Let bandwidth and interval config options be specified as 5 bytes,
27191 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
27192 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
27193 get back to normal.)
27194 - If your requested entry or exit node has advertised bandwidth 0,
27196 - Be more greedy about filling up relay cells -- we try reading again
27197 once we've processed the stuff we read, in case enough has arrived
27198 to fill the last cell completely.
27199 - Apply NT service patch from Osamu Fujino. Still needs more work.
27202 Changes in version 0.0.9pre6 - 2004-11-15
27203 o Bugfixes on 0.0.8.1:
27204 - Fix assert failure on malformed socks4a requests.
27205 - Use identity comparison, not nickname comparison, to choose which
27206 half of circuit-ID-space each side gets to use. This is needed
27207 because sometimes we think of a router as a nickname, and sometimes
27208 as a hex ID, and we can't predict what the other side will do.
27209 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
27210 write() call will fail and we handle it there.
27211 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
27212 and smartlist_len, which are two major profiling offenders.
27214 o Bugfixes on 0.0.9pre5:
27215 - Fix a bug in read_all that was corrupting config files on windows.
27216 - When we're raising the max number of open file descriptors to
27217 'unlimited', don't log that we just raised it to '-1'.
27218 - Include event code with events, as required by control-spec.txt.
27219 - Don't give a fingerprint when clients do --list-fingerprint:
27220 it's misleading, because it will never be the same again.
27221 - Stop using strlcpy in tor_strndup, since it was slowing us
27223 - Remove warn on startup about missing cached-directory file.
27224 - Make kill -USR1 work again.
27225 - Hibernate if we start tor during the "wait for wakeup-time" phase
27226 of an accounting interval. Log our hibernation plans better.
27227 - Authoritative dirservers now also cache their directory, so they
27228 have it on start-up.
27231 - Fetch running-routers; cache running-routers; compress
27232 running-routers; serve compressed running-routers.z
27233 - Add NSI installer script contributed by J Doe.
27234 - Commit VC6 and VC7 workspace/project files.
27235 - Commit a tor.spec for making RPM files, with help from jbash.
27236 - Add contrib/torctl.in contributed by Glenn Fink.
27237 - Implement the control-spec's SAVECONF command, to write your
27238 configuration to torrc.
27239 - Get cookie authentication for the controller closer to working.
27240 - Include control-spec.txt in the tarball.
27241 - When set_conf changes our server descriptor, upload a new copy.
27242 But don't upload it too often if there are frequent changes.
27243 - Document authentication config in man page, and document signals
27245 - Clean up confusing parts of man page and torrc.sample.
27246 - Make expand_filename handle ~ and ~username.
27247 - Use autoconf to enable largefile support where necessary. Use
27248 ftello where available, since ftell can fail at 2GB.
27249 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
27250 log more informatively.
27251 - Give a slightly more useful output for "tor -h".
27252 - Refuse application socks connections to port 0.
27253 - Check clock skew for verified servers, but allow unverified
27254 servers and clients to have any clock skew.
27255 - Break DirFetchPostPeriod into:
27256 - DirFetchPeriod for fetching full directory,
27257 - StatusFetchPeriod for fetching running-routers,
27258 - DirPostPeriod for posting server descriptor,
27259 - RendPostPeriod for posting hidden service descriptors.
27260 - Make sure the hidden service descriptors are at a random offset
27261 from each other, to hinder linkability.
27264 Changes in version 0.0.9pre5 - 2004-11-09
27265 o Bugfixes on 0.0.9pre4:
27266 - Fix a seg fault in unit tests (doesn't affect main program).
27267 - Fix an assert bug where a hidden service provider would fail if
27268 the first hop of his rendezvous circuit was down.
27269 - Hidden service operators now correctly handle version 1 style
27270 INTRODUCE1 cells (nobody generates them still, so not a critical
27272 - If do_hup fails, actually notice.
27273 - Handle more errnos from accept() without closing the listener.
27274 Some OpenBSD machines were closing their listeners because
27275 they ran out of file descriptors.
27276 - Send resolve cells to exit routers that are running a new
27277 enough version of the resolve code to work right.
27278 - Better handling of winsock includes on non-MSV win32 compilers.
27279 - Some people had wrapped their tor client/server in a script
27280 that would restart it whenever it died. This did not play well
27281 with our "shut down if your version is obsolete" code. Now people
27282 don't fetch a new directory if their local cached version is
27284 - Make our autogen.sh work on ksh as well as bash.
27287 - Hibernation: New config option "AccountingMaxKB" lets you
27288 set how many KBytes per month you want to allow your server to
27289 consume. Rather than spreading those bytes out evenly over the
27290 month, we instead hibernate for some of the month and pop up
27291 at a deterministic time, work until the bytes are consumed, then
27292 hibernate again. Config option "MonthlyAccountingStart" lets you
27293 specify which day of the month your billing cycle starts on.
27294 - Control interface: a separate program can now talk to your
27295 client/server over a socket, and get/set config options, receive
27296 notifications of circuits and streams starting/finishing/dying,
27297 bandwidth used, etc. The next step is to get some GUIs working.
27298 Let us know if you want to help out. See doc/control-spec.txt .
27299 - Ship a contrib/tor-control.py as an example script to interact
27300 with the control port.
27301 - "tor --hash-password zzyxz" will output a salted password for
27302 use in authenticating to the control interface.
27303 - New log format in config:
27304 "Log minsev[-maxsev] stdout|stderr|syslog" or
27305 "Log minsev[-maxsev] file /var/foo"
27308 - DirPolicy config option, to let people reject incoming addresses
27309 from their dirserver.
27310 - "tor --list-fingerprint" will list your identity key fingerprint
27312 - Add "pass" target for RedirectExit, to make it easier to break
27313 out of a sequence of RedirectExit rules.
27314 - Clients now generate a TLS cert too, in preparation for having
27315 them act more like real nodes.
27316 - Ship src/win32/ in the tarball, so people can use it to build.
27317 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
27319 - New "router-status" line in directory, to better bind each verified
27320 nickname to its identity key.
27321 - Deprecate unofficial config option abbreviations, and abbreviations
27322 not on the command line.
27323 - Add a pure-C tor-resolve implementation.
27324 - Use getrlimit and friends to ensure we can reach MaxConn (currently
27325 1024) file descriptors.
27327 o Code security improvements, inspired by Ilja:
27328 - Replace sprintf with snprintf. (I think they were all safe, but
27330 - Replace strcpy/strncpy with strlcpy in more places.
27331 - Avoid strcat; use snprintf or strlcat instead.
27332 - snprintf wrapper with consistent (though not C99) overflow behavior.
27335 Changes in version 0.0.9pre4 - 2004-10-17
27336 o Bugfixes on 0.0.9pre3:
27337 - If the server doesn't specify an exit policy, use the real default
27338 exit policy, not reject *:*.
27339 - Ignore fascistfirewall when uploading/downloading hidden service
27340 descriptors, since we go through Tor for those; and when using
27341 an HttpProxy, since we assume it can reach them all.
27342 - When looking for an authoritative dirserver, use only the ones
27343 configured at boot. Don't bother looking in the directory.
27344 - The rest of the fix for get_default_conf_file() on older win32.
27345 - Make 'Routerfile' config option obsolete.
27348 - New 'MyFamily nick1,...' config option for a server to
27349 specify other servers that shouldn't be used in the same circuit
27350 with it. Only believed if nick1 also specifies us.
27351 - New 'NodeFamily nick1,nick2,...' config option for a client to
27352 specify nodes that it doesn't want to use in the same circuit.
27353 - New 'Redirectexit pattern address:port' config option for a
27354 server to redirect exit connections, e.g. to a local squid.
27357 Changes in version 0.0.9pre3 - 2004-10-13
27358 o Bugfixes on 0.0.8.1:
27359 - Better torrc example lines for dirbindaddress and orbindaddress.
27360 - Improved bounds checking on parsed ints (e.g. config options and
27361 the ones we find in directories.)
27362 - Better handling of size_t vs int, so we're more robust on 64
27364 - Fix the rest of the bug where a newly started OR would appear
27365 as unverified even after we've added his fingerprint and hupped
27367 - Fix a bug from 0.0.7: when read() failed on a stream, we would
27368 close it without sending back an end. So 'connection refused'
27369 would simply be ignored and the user would get no response.
27371 o Bugfixes on 0.0.9pre2:
27372 - Serving the cached-on-disk directory to people is bad. We now
27373 provide no directory until we've fetched a fresh one.
27374 - Workaround for bug on windows where cached-directories get crlf
27376 - Make get_default_conf_file() work on older windows too.
27377 - If we write a *:* exit policy line in the descriptor, don't write
27378 any more exit policy lines.
27381 - Use only 0.0.9pre1 and later servers for resolve cells.
27382 - Make the dirservers file obsolete.
27383 - Include a dir-signing-key token in directories to tell the
27384 parsing entity which key is being used to sign.
27385 - Remove the built-in bulky default dirservers string.
27386 - New config option "Dirserver %s:%d [fingerprint]", which can be
27387 repeated as many times as needed. If no dirservers specified,
27388 default to moria1,moria2,tor26.
27389 - Make moria2 advertise a dirport of 80, so people behind firewalls
27390 will be able to get a directory.
27391 - Http proxy support
27392 - Dirservers translate requests for http://%s:%d/x to /x
27393 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
27394 be routed through this host.
27395 - Clients ask for /tor/x rather than /x for new enough dirservers.
27396 This way we can one day coexist peacefully with apache.
27397 - Clients specify a "Host: %s%d" http header, to be compatible
27398 with more proxies, and so running squid on an exit node can work.
27401 Changes in version 0.0.8.1 - 2004-10-13
27403 - Fix a seg fault that can be triggered remotely for Tor
27404 clients/servers with an open dirport.
27405 - Fix a rare assert trigger, where routerinfos for entries in
27406 our cpath would expire while we're building the path.
27407 - Fix a bug in OutboundBindAddress so it (hopefully) works.
27408 - Fix a rare seg fault for people running hidden services on
27409 intermittent connections.
27410 - Fix a bug in parsing opt keywords with objects.
27411 - Fix a stale pointer assert bug when a stream detaches and
27413 - Fix a string format vulnerability (probably not exploitable)
27414 in reporting stats locally.
27415 - Fix an assert trigger: sometimes launching circuits can fail
27416 immediately, e.g. because too many circuits have failed recently.
27417 - Fix a compile warning on 64 bit platforms.
27420 Changes in version 0.0.9pre2 - 2004-10-03
27422 - Make fetching a cached directory work for 64-bit platforms too.
27423 - Make zlib.h a required header, not an optional header.
27426 Changes in version 0.0.9pre1 - 2004-10-01
27428 - Stop using separate defaults for no-config-file and
27429 empty-config-file. Now you have to explicitly turn off SocksPort,
27430 if you don't want it open.
27431 - Fix a bug in OutboundBindAddress so it (hopefully) works.
27432 - Improve man page to mention more of the 0.0.8 features.
27433 - Fix a rare seg fault for people running hidden services on
27434 intermittent connections.
27435 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
27437 - Fix more dns related bugs: send back resolve_failed and end cells
27438 more reliably when the resolve fails, rather than closing the
27439 circuit and then trying to send the cell. Also attach dummy resolve
27440 connections to a circuit *before* calling dns_resolve(), to fix
27441 a bug where cached answers would never be sent in RESOLVED cells.
27442 - When we run out of disk space, or other log writing error, don't
27443 crash. Just stop logging to that log and continue.
27444 - We were starting to daemonize before we opened our logs, so if
27445 there were any problems opening logs, we would complain to stderr,
27446 which wouldn't work, and then mysteriously exit.
27447 - Fix a rare bug where sometimes a verified OR would connect to us
27448 before he'd uploaded his descriptor, which would cause us to
27449 assign conn->nickname as though he's unverified. Now we look through
27450 the fingerprint list to see if he's there.
27451 - Fix a rare assert trigger, where routerinfos for entries in
27452 our cpath would expire while we're building the path.
27455 - Clients can ask dirservers for /dir.z to get a compressed version
27456 of the directory. Only works for servers running 0.0.9, of course.
27457 - Make clients cache directories and use them to seed their router
27458 lists at startup. This means clients have a datadir again.
27459 - Configuration infrastructure support for warning on obsolete
27461 - Respond to content-encoding headers by trying to uncompress as
27463 - Reply with a deflated directory when a client asks for "dir.z".
27464 We could use allow-encodings instead, but allow-encodings isn't
27465 specified in HTTP 1.0.
27466 - Raise the max dns workers from 50 to 100.
27467 - Discourage people from setting their dirfetchpostperiod more often
27468 than once per minute.
27469 - Protect dirservers from overzealous descriptor uploading -- wait
27470 10 seconds after directory gets dirty, before regenerating.
27473 Changes in version 0.0.8 - 2004-08-25
27474 o Port it to SunOS 5.9 / Athena
27477 Changes in version 0.0.8rc2 - 2004-08-20
27478 o Make it compile on cygwin again.
27479 o When picking unverified routers, skip those with low uptime and/or
27480 low bandwidth, depending on what properties you care about.
27483 Changes in version 0.0.8rc1 - 2004-08-18
27484 o Changes from 0.0.7.3:
27486 - Fix assert triggers: if the other side returns an address 0.0.0.0,
27487 don't put it into the client dns cache.
27488 - If a begin failed due to exit policy, but we believe the IP address
27489 should have been allowed, switch that router to exitpolicy reject *:*
27490 until we get our next directory.
27492 - Clients choose nodes proportional to advertised bandwidth.
27493 - Avoid using nodes with low uptime as introduction points.
27494 - Handle servers with dynamic IP addresses: don't replace
27495 options->Address with the resolved one at startup, and
27496 detect our address right before we make a routerinfo each time.
27497 - 'FascistFirewall' option to pick dirservers and ORs on specific
27498 ports; plus 'FirewallPorts' config option to tell FascistFirewall
27499 which ports are open. (Defaults to 80,443)
27500 - Be more aggressive about trying to make circuits when the network
27501 has changed (e.g. when you unsuspend your laptop).
27502 - Check for time skew on http headers; report date in response to
27504 - If the entrynode config line has only one node, don't pick it as
27506 - Add strict{entry|exit}nodes config options. If set to 1, then
27507 we refuse to build circuits that don't include the specified entry
27509 - OutboundBindAddress config option, to bind to a specific
27510 IP address for outgoing connect()s.
27511 - End truncated log entries (e.g. directories) with "[truncated]".
27513 o Patches to 0.0.8preX:
27515 - Patches to compile and run on win32 again (maybe)?
27516 - Fix crash when looking for ~/.torrc with no $HOME set.
27517 - Fix a race bug in the unit tests.
27518 - Handle verified/unverified name collisions better when new
27519 routerinfo's arrive in a directory.
27520 - Sometimes routers were getting entered into the stats before
27521 we'd assigned their identity_digest. Oops.
27522 - Only pick and establish intro points after we've gotten a
27525 - AllowUnverifiedNodes config option to let circuits choose no-name
27526 routers in entry,middle,exit,introduction,rendezvous positions.
27527 Allow middle and rendezvous positions by default.
27528 - Add a man page for tor-resolve.
27531 Changes in version 0.0.7.3 - 2004-08-12
27532 o Stop dnsworkers from triggering an assert failure when you
27533 ask them to resolve the host "".
27536 Changes in version 0.0.8pre3 - 2004-08-09
27537 o Changes from 0.0.7.2:
27538 - Allow multiple ORs with same nickname in routerlist -- now when
27539 people give us one identity key for a nickname, then later
27540 another, we don't constantly complain until the first expires.
27541 - Remember used bandwidth (both in and out), and publish 15-minute
27542 snapshots for the past day into our descriptor.
27543 - You can now fetch $DIRURL/running-routers to get just the
27544 running-routers line, not the whole descriptor list. (But
27545 clients don't use this yet.)
27546 - When people mistakenly use Tor as an http proxy, point them
27547 at the tor-doc.html rather than the INSTALL.
27548 - Remove our mostly unused -- and broken -- hex_encode()
27549 function. Use base16_encode() instead. (Thanks to Timo Lindfors
27550 for pointing out this bug.)
27551 - Rotate onion keys every 12 hours, not every 2 hours, so we have
27552 fewer problems with people using the wrong key.
27553 - Change the default exit policy to reject the default edonkey,
27554 kazaa, gnutella ports.
27555 - Add replace_file() to util.[ch] to handle win32's rename().
27557 o Changes from 0.0.8preX:
27558 - Fix two bugs in saving onion keys to disk when rotating, so
27559 hopefully we'll get fewer people using old onion keys.
27560 - Fix an assert error that was making SocksPolicy not work.
27561 - Be willing to expire routers that have an open dirport -- it's
27562 just the authoritative dirservers we want to not forget.
27563 - Reject tor-resolve requests for .onion addresses early, so we
27564 don't build a whole rendezvous circuit and then fail.
27565 - When you're warning a server that he's unverified, don't cry
27566 wolf unpredictably.
27567 - Fix a race condition: don't try to extend onto a connection
27568 that's still handshaking.
27569 - For servers in clique mode, require the conn to be open before
27570 you'll choose it for your path.
27571 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
27572 end relay cell, etc.
27573 - Measure bandwidth capacity over the last 24 hours, not just 12
27574 - Bugfix: authoritative dirservers were making and signing a new
27575 directory for each client, rather than reusing the cached one.
27578 Changes in version 0.0.8pre2 - 2004-08-04
27579 o Changes from 0.0.7.2:
27581 - Check directory signature _before_ you decide whether you're
27582 you're running an obsolete version and should exit.
27583 - Check directory signature _before_ you parse the running-routers
27584 list to decide who's running or verified.
27585 - Bugfixes and features:
27586 - Check return value of fclose while writing to disk, so we don't
27587 end up with broken files when servers run out of disk space.
27588 - Log a warning if the user uses an unsafe socks variant, so people
27589 are more likely to learn about privoxy or socat.
27590 - Dirservers now include RFC1123-style dates in the HTTP headers,
27591 which one day we will use to better detect clock skew.
27593 o Changes from 0.0.8pre1:
27594 - Make it compile without warnings again on win32.
27595 - Log a warning if you're running an unverified server, to let you
27596 know you might want to get it verified.
27597 - Only pick a default nickname if you plan to be a server.
27600 Changes in version 0.0.8pre1 - 2004-07-23
27602 - Made our unit tests compile again on OpenBSD 3.5, and tor
27603 itself compile again on OpenBSD on a sparc64.
27604 - We were neglecting milliseconds when logging on win32, so
27605 everything appeared to happen at the beginning of each second.
27607 o Protocol changes:
27608 - 'Extend' relay cell payloads now include the digest of the
27609 intended next hop's identity key. Now we can verify that we're
27610 extending to the right router, and also extend to routers we
27611 hadn't heard of before.
27614 - Tor nodes can now act as relays (with an advertised ORPort)
27615 without being manually verified by the dirserver operators.
27616 - Uploaded descriptors of unverified routers are now accepted
27617 by the dirservers, and included in the directory.
27618 - Verified routers are listed by nickname in the running-routers
27619 list; unverified routers are listed as "$<fingerprint>".
27620 - We now use hash-of-identity-key in most places rather than
27621 nickname or addr:port, for improved security/flexibility.
27622 - To avoid Sybil attacks, paths still use only verified servers.
27623 But now we have a chance to play around with hybrid approaches.
27624 - Nodes track bandwidth usage to estimate capacity (not used yet).
27625 - ClientOnly option for nodes that never want to become servers.
27626 - Directory caching.
27627 - "AuthoritativeDir 1" option for the official dirservers.
27628 - Now other nodes (clients and servers) will cache the latest
27629 directory they've pulled down.
27630 - They can enable their DirPort to serve it to others.
27631 - Clients will pull down a directory from any node with an open
27632 DirPort, and check the signature/timestamp correctly.
27633 - Authoritative dirservers now fetch directories from other
27634 authdirservers, to stay better synced.
27635 - Running-routers list tells who's down also, along with noting
27636 if they're verified (listed by nickname) or unverified (listed
27638 - Allow dirservers to serve running-router list separately.
27639 This isn't used yet.
27640 - ORs connect-on-demand to other ORs
27641 - If you get an extend cell to an OR you're not connected to,
27642 connect, handshake, and forward the create cell.
27643 - The authoritative dirservers stay connected to everybody,
27644 and everybody stays connected to 0.0.7 servers, but otherwise
27645 clients/servers expire unused connections after 5 minutes.
27646 - When servers get a sigint, they delay 30 seconds (refusing new
27647 connections) then exit. A second sigint causes immediate exit.
27648 - File and name management:
27649 - Look for .torrc if no CONFDIR "torrc" is found.
27650 - If no datadir is defined, then choose, make, and secure ~/.tor
27652 - If torrc not found, exitpolicy reject *:*.
27653 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
27654 - If no nickname is defined, derive default from hostname.
27655 - Rename secret key files, e.g. identity.key -> secret_id_key,
27656 to discourage people from mailing their identity key to tor-ops.
27657 - Refuse to build a circuit before the directory has arrived --
27658 it won't work anyway, since you won't know the right onion keys
27660 - Try other dirservers immediately if the one you try is down. This
27661 should tolerate down dirservers better now.
27662 - Parse tor version numbers so we can do an is-newer-than check
27663 rather than an is-in-the-list check.
27664 - New socks command 'resolve', to let us shim gethostbyname()
27666 - A 'tor_resolve' script to access the socks resolve functionality.
27667 - A new socks-extensions.txt doc file to describe our
27668 interpretation and extensions to the socks protocols.
27669 - Add a ContactInfo option, which gets published in descriptor.
27670 - Publish OR uptime in descriptor (and thus in directory) too.
27671 - Write tor version at the top of each log file
27672 - New docs in the tarball:
27674 - Document that you should proxy your SSL traffic too.
27677 Changes in version 0.0.7.2 - 2004-07-07
27678 o A better fix for the 0.0.0.0 problem, that will hopefully
27679 eliminate the remaining related assertion failures.
27682 Changes in version 0.0.7.1 - 2004-07-04
27683 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
27684 since internally we use 0.0.0.0 to signify "not yet resolved".
27687 Changes in version 0.0.7 - 2004-06-07
27688 o Updated the man page to reflect the new features.
27691 Changes in version 0.0.7rc2 - 2004-06-06
27692 o Changes from 0.0.7rc1:
27693 - Make it build on Win32 again.
27694 o Changes from 0.0.6.2:
27695 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
27699 Changes in version 0.0.7rc1 - 2004-06-02
27701 - On sighup, we were adding another log without removing the first
27702 one. So log messages would get duplicated n times for n sighups.
27703 - Several cases of using a connection after we'd freed it. The
27704 problem was that connections that are pending resolve are in both
27705 the pending_resolve tree, and also the circuit's resolving_streams
27706 list. When you want to remove one, you must remove it from both.
27707 - Fix a double-mark-for-close where an end cell arrived for a
27708 resolving stream, and then the resolve failed.
27709 - Check directory signatures based on name of signer, not on whom
27710 we got the directory from. This will let us cache directories more
27713 - Crank up some of our constants to handle more users.
27716 Changes in version 0.0.7pre1 - 2004-06-02
27717 o Fixes for crashes and other obnoxious bugs:
27718 - Fix an epipe bug: sometimes when directory connections failed
27719 to connect, we would give them a chance to flush before closing
27721 - When we detached from a circuit because of resolvefailed, we
27722 would immediately try the same circuit twice more, and then
27723 give up on the resolve thinking we'd tried three different
27725 - Limit the number of intro circuits we'll attempt to build for a
27726 hidden service per 15-minute period.
27727 - Check recommended-software string *early*, before actually parsing
27728 the directory. Thus we can detect an obsolete version and exit,
27729 even if the new directory format doesn't parse.
27730 o Fixes for security bugs:
27731 - Remember which nodes are dirservers when you startup, and if a
27732 random OR enables his dirport, don't automatically assume he's
27733 a trusted dirserver.
27735 - Directory connections were asking the wrong poll socket to
27736 start writing, and not asking themselves to start writing.
27737 - When we detached from a circuit because we sent a begin but
27738 didn't get a connected, we would use it again the first time;
27739 but after that we would correctly switch to a different one.
27740 - Stop warning when the first onion decrypt attempt fails; they
27741 will sometimes legitimately fail now that we rotate keys.
27742 - Override unaligned-access-ok check when $host_cpu is ia64 or
27743 arm. Apparently they allow it but the kernel whines.
27744 - Dirservers try to reconnect periodically too, in case connections
27746 - Fix some memory leaks in directory servers.
27747 - Allow backslash in Win32 filenames.
27748 - Made Tor build complain-free on FreeBSD, hopefully without
27749 breaking other BSD builds. We'll see.
27751 - Doxygen markup on all functions and global variables.
27752 - Make directory functions update routerlist, not replace it. So
27753 now directory disagreements are not so critical a problem.
27754 - Remove the upper limit on number of descriptors in a dirserver's
27755 directory (not that we were anywhere close).
27756 - Allow multiple logfiles at different severity ranges.
27757 - Allow *BindAddress to specify ":port" rather than setting *Port
27758 separately. Allow multiple instances of each BindAddress config
27759 option, so you can bind to multiple interfaces if you want.
27760 - Allow multiple exit policy lines, which are processed in order.
27761 Now we don't need that huge line with all the commas in it.
27762 - Enable accept/reject policies on SOCKS connections, so you can bind
27763 to 0.0.0.0 but still control who can use your OP.
27766 Changes in version 0.0.6.2 - 2004-05-16
27767 o Our integrity-checking digest was checking only the most recent cell,
27768 not the previous cells like we'd thought.
27769 Thanks to Stefan Mark for finding the flaw!
27772 Changes in version 0.0.6.1 - 2004-05-06
27773 o Fix two bugs in our AES counter-mode implementation (this affected
27774 onion-level stream encryption, but not TLS-level). It turns
27775 out we were doing something much more akin to a 16-character
27776 polyalphabetic cipher. Oops.
27777 Thanks to Stefan Mark for finding the flaw!
27778 o Retire moria3 as a directory server, and add tor26 as a directory
27782 Changes in version 0.0.6 - 2004-05-02
27783 [version bump only]
27786 Changes in version 0.0.6rc4 - 2004-05-01
27787 o Update the built-in dirservers list to use the new directory format
27788 o Fix a rare seg fault: if a node offering a hidden service attempts
27789 to build a circuit to Alice's rendezvous point and fails before it
27790 reaches the last hop, it retries with a different circuit, but
27792 o Handle windows socket errors correctly.
27795 Changes in version 0.0.6rc3 - 2004-04-28
27796 o Don't expire non-general excess circuits (if we had enough
27797 circuits open, we were expiring rendezvous circuits -- even
27798 when they had a stream attached. oops.)
27799 o Fetch randomness from /dev/urandom better (not via fopen/fread)
27800 o Better debugging for tls errors
27801 o Some versions of openssl have an SSL_pending function that erroneously
27802 returns bytes when there is a non-application record pending.
27803 o Set Content-Type on the directory and hidserv descriptor.
27804 o Remove IVs from cipher code, since AES-ctr has none.
27805 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
27806 o We were using an array of length zero in a few places.
27807 o win32's gethostbyname can't resolve an IP to an IP.
27808 o win32's close can't close a socket.
27811 Changes in version 0.0.6rc2 - 2004-04-26
27812 o Fix a bug where we were closing tls connections intermittently.
27813 It turns out openssl keeps its errors around -- so if an error
27814 happens, and you don't ask about it, and then another openssl
27815 operation happens and succeeds, and you ask if there was an error,
27816 it tells you about the first error. Fun fun.
27817 o Fix a bug that's been lurking since 27 may 03 (!)
27818 When passing back a destroy cell, we would use the wrong circ id.
27819 'Mostly harmless', but still worth fixing.
27820 o Since we don't support truncateds much, don't bother sending them;
27821 just close the circ.
27822 o check for <machine/limits.h> so we build on NetBSD again (I hope).
27823 o don't crash if a conn that sent a begin has suddenly lost its circuit
27824 (this was quite rare).
27827 Changes in version 0.0.6rc1 - 2004-04-25
27828 o We now rotate link (tls context) keys and onion keys.
27829 o CREATE cells now include oaep padding, so you can tell
27830 if you decrypted them correctly.
27831 o Add bandwidthburst to server descriptor.
27832 o Directories now say which dirserver signed them.
27833 o Use a tor_assert macro that logs failed assertions too.
27836 Changes in version 0.0.6pre5 - 2004-04-18
27837 o changes from 0.0.6pre4:
27838 - make tor build on broken freebsd 5.2 installs
27839 - fix a failed assert when you try an intro point, get a nack, and try
27840 a second one and it works.
27841 - when alice uses a port that the hidden service doesn't accept,
27842 it now sends back an end cell (denied by exit policy). otherwise
27843 alice would just have to wait to time out.
27844 - fix another rare bug: when we had tried all the intro
27845 points for a hidden service, we fetched the descriptor
27846 again, but we left our introcirc thinking it had already
27847 sent an intro, so it kept waiting for a response...
27848 - bugfix: when you sleep your hidden-service laptop, as soon
27849 as it wakes up it tries to upload a service descriptor, but
27850 socketpair fails for some reason (localhost not up yet?).
27851 now we simply give up on that upload, and we'll try again later.
27852 i'd still like to find the bug though.
27853 - if an intro circ waiting for an ack dies before getting one, then
27855 - we were reusing stale service descriptors and refetching usable
27859 Changes in version 0.0.6pre4 - 2004-04-14
27860 o changes from 0.0.6pre3:
27861 - when bob fails to connect to the rendezvous point, and his
27862 circ didn't fail because of the rendezvous point itself, then
27863 he retries a couple of times
27864 - we expire introduction and rendezvous circs more thoroughly
27865 (sometimes they were hanging around forever)
27866 - we expire unattached rendezvous streams that have been around
27867 too long (they were sticking around forever).
27868 - fix a measly fencepost error that was crashing everybody with
27872 Changes in version 0.0.6pre3 - 2004-04-14
27873 o changes from 0.0.6pre2:
27874 - make hup work again
27875 - fix some memory leaks for dirservers
27876 - allow more skew in rendezvous descriptor timestamps, to help
27877 handle people like blanu who don't know what time it is
27878 - normal circs are 3 hops, but some rend/intro circs are 4, if
27879 the initiator doesn't get to choose the last hop
27880 - send acks for introductions, so alice can know whether to try
27882 - bob publishes intro points more correctly
27883 o changes from 0.0.5:
27884 - fix an assert trigger that's been plaguing us since the days
27885 of 0.0.2prexx (thanks weasel!)
27886 - retry stream correctly when we fail to connect because of
27887 exit-policy-reject (should try another) or can't-resolve-address
27888 (also should try another, because dns on random internet servers
27890 - when we hup a dirserver and we've *removed* a server from the
27891 approved-routers list, now we remove that server from the
27892 in-memory directories too
27895 Changes in version 0.0.6pre2 - 2004-04-08
27896 o We fixed our base32 implementation. Now it works on all architectures.
27899 Changes in version 0.0.6pre1 - 2004-04-08
27901 - Hidden services and rendezvous points are implemented. Go to
27902 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
27903 hidden services. (This only works via a socks4a proxy such as
27904 Privoxy, and currently it's quite slow.)
27907 Changes in version 0.0.5 - 2004-03-30
27908 [version bump only]
27911 Changes in version 0.0.5rc3 - 2004-03-29
27912 o Install torrc as torrc.sample -- we no longer clobber your
27914 o Re-enable recommendedversion checking (we broke it in rc2, oops)
27915 o Add in a 'notice' log level for things the operator should hear
27916 but that aren't warnings
27919 Changes in version 0.0.5rc2 - 2004-03-29
27920 o Hold socks connection open until reply is flushed (if possible)
27921 o Make exit nodes resolve IPs to IPs immediately, rather than asking
27922 the dns farm to do it.
27923 o Fix c99 aliasing warnings in rephist.c
27924 o Don't include server descriptors that are older than 24 hours in the
27926 o Give socks 'reject' replies their whole 15s to attempt to flush,
27927 rather than seeing the 60s timeout and assuming the flush had failed.
27928 o Clean automake droppings from the cvs repository
27931 Changes in version 0.0.5rc1 - 2004-03-28
27932 o Fix mangled-state bug in directory fetching (was causing sigpipes).
27933 o Only build circuits after we've fetched the directory: clients were
27934 using only the directory servers before they'd fetched a directory.
27935 This also means longer startup time; so it goes.
27936 o Fix an assert trigger where an OP would fail to handshake, and we'd
27937 expect it to have a nickname.
27938 o Work around a tsocks bug: do a socks reject when AP connection dies
27939 early, else tsocks goes into an infinite loop.
27942 Changes in version 0.0.4 - 2004-03-26
27943 o When connecting to a dirserver or OR and the network is down,
27947 Changes in version 0.0.3 - 2004-03-26
27948 o Warn and fail if server chose a nickname with illegal characters
27949 o Port to Solaris and Sparc:
27950 - include missing header fcntl.h
27951 - have autoconf find -lsocket -lnsl automatically
27952 - deal with hardware word alignment
27953 - make uname() work (solaris has a different return convention)
27954 - switch from using signal() to sigaction()
27955 o Preliminary work on reputation system:
27956 - Keep statistics on success/fail of connect attempts; they're published
27957 by kill -USR1 currently.
27958 - Add a RunTesting option to try to learn link state by creating test
27959 circuits, even when SocksPort is off.
27960 - Remove unused open circuits when there are too many.
27963 Changes in version 0.0.2 - 2004-03-19
27964 - Include strlcpy and strlcat for safer string ops
27965 - define INADDR_NONE so we compile (but still not run) on solaris
27968 Changes in version 0.0.2pre27 - 2004-03-14
27970 - Allow internal tor networks (we were rejecting internal IPs,
27971 now we allow them if they're set explicitly).
27972 - And fix a few endian issues.
27975 Changes in version 0.0.2pre26 - 2004-03-14
27977 - If a stream times out after 15s without a connected cell, don't
27978 try that circuit again: try a new one.
27979 - Retry streams at most 4 times. Then give up.
27980 - When a dirserver gets a descriptor from an unknown router, it
27981 logs its fingerprint (so the dirserver operator can choose to
27982 accept it even without mail from the server operator).
27983 - Inform unapproved servers when we reject their descriptors.
27984 - Make tor build on Windows again. It works as a client, who knows
27986 - Clearer instructions in the torrc for how to set up a server.
27987 - Be more efficient about reading fd's when our global token bucket
27988 (used for rate limiting) becomes empty.
27990 - Stop asserting that computers always go forward in time. It's
27992 - When we sent a cell (e.g. destroy) and then marked an OR connection
27993 expired, we might close it before finishing a flush if the other
27994 side isn't reading right then.
27995 - Don't allow dirservers to start if they haven't defined
27996 RecommendedVersions
27997 - We were caching transient dns failures. Oops.
27998 - Prevent servers from publishing an internal IP as their address.
27999 - Address a strcat vulnerability in circuit.c
28002 Changes in version 0.0.2pre25 - 2004-03-04
28004 - Put the OR's IP in its router descriptor, not its fqdn. That way
28005 we'll stop being stalled by gethostbyname for nodes with flaky dns,
28008 - If the user typed in an address that didn't resolve, the server
28012 Changes in version 0.0.2pre24 - 2004-03-03
28014 - Fix an assertion failure in dns.c, where we were trying to dequeue
28015 a pending dns resolve even if it wasn't pending
28016 - Fix a spurious socks5 warning about still trying to write after the
28017 connection is finished.
28018 - Hold certain marked_for_close connections open until they're finished
28019 flushing, rather than losing bytes by closing them too early.
28020 - Correctly report the reason for ending a stream
28021 - Remove some duplicate calls to connection_mark_for_close
28022 - Put switch_id and start_daemon earlier in the boot sequence, so it
28023 will actually try to chdir() to options.DataDirectory
28024 - Make 'make test' exit(1) if a test fails; fix some unit tests
28025 - Make tor fail when you use a config option it doesn't know about,
28026 rather than warn and continue.
28027 - Make --version work
28028 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
28031 Changes in version 0.0.2pre23 - 2004-02-29
28033 - Print a statement when the first circ is finished, so the user
28034 knows it's working.
28035 - If a relay cell is unrecognized at the end of the circuit,
28036 send back a destroy. (So attacks to mutate cells are more
28038 - New config option 'excludenodes' to avoid certain nodes for circuits.
28039 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
28040 so you can collect coredumps there.
28042 - Fix a bug in tls flushing where sometimes data got wedged and
28043 didn't flush until more data got sent. Hopefully this bug was
28044 a big factor in the random delays we were seeing.
28045 - Make 'connected' cells include the resolved IP, so the client
28046 dns cache actually gets populated.
28047 - Disallow changing from ORPort=0 to ORPort>0 on hup.
28048 - When we time-out on a stream and detach from the circuit, send an
28049 end cell down it first.
28050 - Only warn about an unknown router (in exitnodes, entrynodes,
28051 excludenodes) after we've fetched a directory.
28054 Changes in version 0.0.2pre22 - 2004-02-26
28056 - Servers publish less revealing uname information in descriptors.
28057 - More memory tracking and assertions, to crash more usefully when
28059 - If the default torrc isn't there, just use some default defaults.
28060 Plus provide an internal dirservers file if they don't have one.
28061 - When the user tries to use Tor as an http proxy, give them an http
28062 501 failure explaining that we're a socks proxy.
28063 - Dump a new router.desc on hup, to help confused people who change
28064 their exit policies and then wonder why router.desc doesn't reflect
28066 - Clean up the generic tor.sh init script that we ship with.
28068 - If the exit stream is pending on the resolve, and a destroy arrives,
28069 then the stream wasn't getting removed from the pending list. I
28070 think this was the one causing recent server crashes.
28071 - Use a more robust poll on OSX 10.3, since their poll is flaky.
28072 - When it couldn't resolve any dirservers, it was useless from then on.
28073 Now it reloads the RouterFile (or default dirservers) if it has no
28075 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
28076 many users don't even *have* a /usr/local/sbin/.
28079 Changes in version 0.0.2pre21 - 2004-02-18
28081 - There's a ChangeLog file that actually reflects the changelog.
28082 - There's a 'torify' wrapper script, with an accompanying
28083 tor-tsocks.conf, that simplifies the process of using tsocks for
28084 tor. It even has a man page.
28085 - The tor binary gets installed to sbin rather than bin now.
28086 - Retry streams where the connected cell hasn't arrived in 15 seconds
28087 - Clean up exit policy handling -- get the default out of the torrc,
28088 so we can update it without forcing each server operator to fix
28090 - Allow imaps and pop3s in default exit policy
28092 - Prevent picking middleman nodes as the last node in the circuit
28095 Changes in version 0.0.2pre20 - 2004-01-30
28097 - We now have a deb package, and it's in debian unstable. Go to
28098 it, apt-getters. :)
28099 - I've split the TotalBandwidth option into BandwidthRate (how many
28100 bytes per second you want to allow, long-term) and
28101 BandwidthBurst (how many bytes you will allow at once before the cap
28102 kicks in). This better token bucket approach lets you, say, set
28103 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
28104 performance while not exceeding your monthly bandwidth quota.
28105 - Push out a tls record's worth of data once you've got it, rather
28106 than waiting until you've read everything waiting to be read. This
28107 may improve performance by pipelining better. We'll see.
28108 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
28109 from failed circuits (if they haven't been connected yet) and attach
28111 - Expire old streams that haven't managed to connect. Some day we'll
28112 have them reattach to new circuits instead.
28115 - Fix several memory leaks that were causing servers to become bloated
28117 - Fix a few very rare assert triggers. A few more remain.
28118 - Setuid to User _before_ complaining about running as root.
28121 Changes in version 0.0.2pre19 - 2004-01-07
28123 - Fix deadlock condition in dns farm. We were telling a child to die by
28124 closing the parent's file descriptor to him. But newer children were
28125 inheriting the open file descriptor from the parent, and since they
28126 weren't closing it, the socket never closed, so the child never read
28127 eof, so he never knew to exit. Similarly, dns workers were holding
28128 open other sockets, leading to all sorts of chaos.
28129 - New cleaner daemon() code for forking and backgrounding.
28130 - If you log to a file, it now prints an entry at the top of the
28131 logfile so you know it's working.
28132 - The onionskin challenge length was 30 bytes longer than necessary.
28133 - Started to patch up the spec so it's not quite so out of date.
28136 Changes in version 0.0.2pre18 - 2004-01-02
28138 - Fix endian issues with the 'integrity' field in the relay header.
28139 - Fix a potential bug where connections in state
28140 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
28143 Changes in version 0.0.2pre17 - 2003-12-30
28145 - Made --debuglogfile (or any second log file, actually) work.
28146 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
28147 adversary could force us into an infinite loop.
28150 - Each onionskin handshake now includes a hash of the computed key,
28151 to prove the server's identity and help perfect forward secrecy.
28152 - Changed cell size from 256 to 512 bytes (working toward compatibility
28154 - Changed cell length to 2 bytes, and moved it to the relay header.
28155 - Implemented end-to-end integrity checking for the payloads of
28157 - Separated streamid from 'recognized' (otherwise circuits will get
28158 messed up when we try to have streams exit from the middle). We
28159 use the integrity-checking to confirm that a cell is addressed to
28161 - Randomize the initial circid and streamid values, so an adversary who
28162 breaks into a node can't learn how many circuits or streams have
28166 Changes in version 0.0.2pre16 - 2003-12-14
28168 - Fixed a bug that made HUP trigger an assert
28169 - Fixed a bug where a circuit that immediately failed wasn't being
28170 counted as a failed circuit in counting retries.
28173 - Now we close the circuit when we get a truncated cell: otherwise we're
28174 open to an anonymity attack where a bad node in the path truncates
28175 the circuit and then we open streams at him.
28176 - Add port ranges to exit policies
28177 - Add a conservative default exit policy
28178 - Warn if you're running tor as root
28179 - on HUP, retry OR connections and close/rebind listeners
28180 - options.EntryNodes: try these nodes first when picking the first node
28181 - options.ExitNodes: if your best choices happen to include any of
28182 your preferred exit nodes, you choose among just those preferred
28184 - options.ExcludedNodes: nodes that are never picked in path building
28187 Changes in version 0.0.2pre15 - 2003-12-03
28188 o Robustness and bugfixes:
28189 - Sometimes clients would cache incorrect DNS resolves, which would
28190 really screw things up.
28191 - An OP that goes offline would slowly leak all its sockets and stop
28193 - A wide variety of bugfixes in exit node selection, exit policy
28194 handling, and processing pending streams when a new circuit is
28196 - Pick nodes for a path only from those the directory says are up
28197 - Choose randomly from all running dirservers, not always the first one
28198 - Increase allowed http header size for directory fetch.
28199 - Stop writing to stderr (if we're daemonized it will be closed).
28200 - Enable -g always, so cores will be more useful to me.
28201 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
28204 - Wrote a man page. It lists commonly used options.
28207 - Change default loglevel to warn.
28208 - Make PidFile default to null rather than littering in your CWD.
28209 - OnionRouter config option is now obsolete. Instead it just checks
28211 - Moved to a single unified torrc file for both clients and servers.
28214 Changes in version 0.0.2pre14 - 2003-11-29
28215 o Robustness and bugfixes:
28216 - Force the admin to make the DataDirectory himself
28217 - to get ownership/permissions right
28218 - so clients no longer make a DataDirectory and then never use it
28219 - fix bug where a client who was offline for 45 minutes would never
28220 pull down a directory again
28221 - fix (or at least hide really well) the dns assert bug that was
28222 causing server crashes
28223 - warnings and improved robustness wrt clockskew for certs
28224 - use the native daemon(3) to daemonize, when available
28225 - exit if bind() fails
28226 - exit if neither socksport nor orport is defined
28227 - include our own tor_timegm (Win32 doesn't have its own)
28228 - bugfix for win32 with lots of connections
28229 - fix minor bias in PRNG
28230 - make dirserver more robust to corrupt cached directory
28233 - Wrote the design document (woo)
28235 o Circuit building and exit policies:
28236 - Circuits no longer try to use nodes that the directory has told them
28238 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
28239 bitcounts (18.0.0.0/8).
28240 - Make AP connections standby for a circuit if no suitable circuit
28241 exists, rather than failing
28242 - Circuits choose exit node based on addr/port, exit policies, and
28243 which AP connections are standing by
28244 - Bump min pathlen from 2 to 3
28245 - Relay end cells have a payload to describe why the stream ended.
28246 - If the stream failed because of exit policy, try again with a new
28248 - Clients have a dns cache to remember resolved addresses.
28249 - Notice more quickly when we have no working circuits
28252 - APPort is now called SocksPort
28253 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
28255 - RecommendedVersions is now a config variable rather than
28256 hardcoded (for dirservers)
28257 - Reloads config on HUP
28258 - Usage info on -h or --help
28259 - If you set User and Group config vars, it'll setu/gid to them.
28262 Changes in version 0.0.2pre13 - 2003-10-19
28263 o General stability:
28264 - SSL_write no longer fails when it returns WANTWRITE and the number
28265 of bytes in the buf has changed by the next SSL_write call.
28266 - Fix segfault fetching directory when network is down
28267 - Fix a variety of minor memory leaks
28268 - Dirservers reload the fingerprints file on HUP, so I don't have
28269 to take down the network when I approve a new router
28270 - Default server config file has explicit Address line to specify fqdn
28273 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
28274 - Make listener connections not ever alloc bufs
28276 o Autoconf improvements:
28277 - don't clobber an external CFLAGS in ./configure
28278 - Make install now works
28279 - create var/lib/tor on make install
28280 - autocreate a tor.sh initscript to help distribs
28281 - autocreate the torrc and sample-server-torrc with correct paths
28283 o Log files and Daemonizing now work:
28284 - If --DebugLogFile is specified, log to it at -l debug
28285 - If --LogFile is specified, use it instead of commandline
28286 - If --RunAsDaemon is set, tor forks and backgrounds on startup