1 Changes in version 0.3.3.10 - 2018-09-10
2 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
4 o Minor features (bug workaround, backport from 0.3.4.7-rc):
5 - Compile correctly on systems that provide the C11 stdatomic.h
6 header, but where C11 atomic functions don't actually compile.
7 Closes ticket 26779; workaround for Debian issue 903709.
9 o Minor features (compatibility, backport from 0.3.4.8):
10 - Tell OpenSSL to maintain backward compatibility with previous
11 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
12 ciphers are disabled by default. Closes ticket 27344.
14 o Minor features (continuous integration, backport from 0.3.4.7-rc):
15 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
16 - Enable macOS builds in our Travis CI configuration. Closes
18 - Install libcap-dev and libseccomp2-dev so these optional
19 dependencies get tested on Travis CI. Closes ticket 26560.
20 - Run asciidoc during Travis CI. Implements ticket 27087.
21 - Use ccache in our Travis CI configuration. Closes ticket 26952.
23 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
24 - Use cargo cache in our Travis CI configuration. Closes
27 o Minor features (controller, backport from 0.3.4.6-rc):
28 - The control port now exposes the list of HTTPTunnelPorts and
29 ExtOrPorts via GETINFO net/listeners/httptunnel and
30 net/listeners/extor respectively. Closes ticket 26647.
32 o Minor features (directory authorities, backport from 0.3.4.7-rc):
33 - Authorities no longer vote to make the subprotocol version
34 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
35 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
37 o Minor features (geoip):
38 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
39 Country database. Closes ticket 27089.
41 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
42 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
43 tell the compiler not to include the system malloc implementation.
44 Fixes bug 20424; bugfix on 0.2.0.20-rc.
45 - Don't try to use a pragma to temporarily disable the
46 -Wunused-const-variable warning if the compiler doesn't support
47 it. Fixes bug 26785; bugfix on 0.3.2.11.
49 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
50 - Silence a spurious compiler warning on the GetAdaptersAddresses
51 function pointer cast. This issue is already fixed by 26481 in
52 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
53 bugfix on 0.2.3.11-alpha.
54 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
55 supported, and always fails. Some compilers warn about the
56 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
59 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
60 - Don't link or search for pthreads when building for Windows, even
61 if we are using build environment (like mingw) that provides a
62 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
64 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
65 - Skip a pair of unreliable key generation tests on Windows, until
66 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
67 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
69 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
70 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
71 - Pass the module flags to distcheck configure, and log the flags
72 before running configure. (Backported to 0.2.9 and later as a
73 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
75 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
76 - When a Travis build fails, and showing a log fails, keep trying to
77 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
78 - When we use echo in Travis, don't pass a --flag as the first
79 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
81 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
82 - When voting for recommended versions, make sure that all of the
83 versions are well-formed and parsable. Fixes bug 26485; bugfix
86 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
87 - Always call tor_free_all() when leaving tor_run_main(). When we
88 did not, restarting tor in-process would cause an assertion
89 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
91 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
92 - Fix a bug in our sandboxing rules for the openat() syscall.
93 Previously, no openat() call would be permitted, which would break
94 filesystem operations on recent glibc versions. Fixes bug 25440;
95 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
97 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
98 - Improve the log message when connection initiators fail to
99 authenticate direct connections to relays. Fixes bug 26927; bugfix
102 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
103 - Fix bug that causes services to not ever rotate their descriptors
104 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
107 o Minor bugfixes (onion services, backport from 0.3.4.8):
108 - Silence a spurious compiler warning in
109 rend_client_send_introduction(). Fixes bug 27463; bugfix
112 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
113 - Work around two different bugs in the OS X 10.10 and later SDKs
114 that would prevent us from successfully targeting earlier versions
115 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
117 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
118 - Fix compilation of the unit tests on GNU/Hurd, which does not
119 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
122 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
123 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
125 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
126 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
127 - Protover parsing was accepting the presence of whitespace in
128 version strings, which the C implementation would choke on, e.g.
129 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
130 - Protover parsing was ignoring a 2nd hyphen and everything after
131 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
133 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
134 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
135 - cd to ${abs_top_builddir}/src/rust before running cargo in
136 src/test/test_rust.sh. This makes the working directory consistent
137 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
139 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
140 - Log a protocol warning when single onion services or Tor2web clients
141 fail to authenticate direct connections to relays.
142 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
144 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
145 - Disable core dumps in test_bt.sh, to avoid failures in "make
146 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
148 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
149 - When running make test-network-all, use the mixed+hs-v2 network.
150 (A previous fix to chutney removed v3 onion services from the
151 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
152 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
153 - Before running make test-network-all, delete old logs and test
154 result files, to avoid spurious failures. Fixes bug 27295; bugfix
157 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
158 - Our "tortls/cert_matches_key" unit test no longer relies on
159 OpenSSL internals. Previously, it relied on unsupported OpenSSL
160 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
161 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
163 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
164 - Stop sending ed25519 link specifiers in v3 onion service introduce
165 cells and descriptors, when the rendezvous or introduction point
166 doesn't support ed25519 link authentication. Fixes bug 26627;
167 bugfix on 0.3.2.4-alpha.
169 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
170 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
171 27185; bugfix on 0.2.2.2-alpha.
174 Changes in version 0.3.3.9 - 2018-07-13
175 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
176 bridge relays should upgrade.
178 o Directory authority changes:
179 - The "Bifroest" bridge authority has been retired; the new bridge
180 authority is "Serge", and it is operated by George from the
181 TorBSD project. Closes ticket 26771.
184 Changes in version 0.3.2.11 - 2018-07-13
185 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
186 bridge relays should upgrade. We also take this opportunity to backport
189 o Directory authority changes:
190 - The "Bifroest" bridge authority has been retired; the new bridge
191 authority is "Serge", and it is operated by George from the
192 TorBSD project. Closes ticket 26771.
194 o Directory authority changes (backport from 0.3.3.7):
195 - Add an IPv6 address for the "dannenberg" directory authority.
198 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
199 - When directory authorities read a zero-byte bandwidth file, they
200 would previously log a warning with the contents of an
201 uninitialised buffer. They now log a warning about the empty file
202 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
204 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
205 - Correctly detect when onion services get disabled after HUP. Fixes
206 bug 25761; bugfix on 0.3.2.1.
208 o Minor features (sandbox, backport from 0.3.3.4-alpha):
209 - Explicitly permit the poll() system call when the Linux
210 seccomp2-based sandbox is enabled: apparently, some versions of
211 libc use poll() when calling getpwnam(). Closes ticket 25313.
213 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
214 - Update the Travis CI configuration to use the stable Rust channel,
215 now that we have decided to require that. Closes ticket 25714.
217 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
218 - Our .travis.yml configuration now includes support for testing the
219 results of "make distcheck". (It's not uncommon for "make check"
220 to pass but "make distcheck" to fail.) Closes ticket 25814.
221 - Our Travis CI configuration now integrates with the Coveralls
222 coverage analysis tool. Closes ticket 25818.
224 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
225 - Add several checks to detect whether Tor relays are uploading
226 their descriptors without specifying why they regenerated them.
227 Diagnostic for ticket 25686.
229 o Minor features (compilation, backport from 0.3.4.4-rc):
230 - When building Tor, prefer to use Python 3 over Python 2, and more
231 recent (contemplated) versions over older ones. Closes
234 o Minor features (geoip):
235 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
236 Country database. Closes ticket 26674.
238 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
239 - Upon receiving a malformed connected cell, stop processing the
240 cell immediately. Previously we would mark the connection for
241 close, but continue processing the cell as if the connection were
242 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
244 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
245 - Allow the nanosleep() system call, which glibc uses to implement
246 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
248 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
249 - When running the hs_ntor_ref.py test, make sure only to pass
250 strings (rather than "bytes" objects) to the Python subprocess
251 module. Python 3 on Windows seems to require this. Fixes bug
252 26535; bugfix on 0.3.1.1-alpha.
253 - When running the ntor_ref.py test, make sure only to pass strings
254 (rather than "bytes" objects) to the Python subprocess module.
255 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
258 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
259 - Work around a change in OpenSSL 1.1.1 where return values that
260 would previously indicate "no password" now indicate an empty
261 password. Without this workaround, Tor instances running with
262 OpenSSL 1.1.1 would accept descriptors that other Tor instances
263 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
265 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
266 - Document that the PerConnBW{Rate,Burst} options will fall back to
267 their corresponding consensus parameters only if those parameters
268 are set. Previously we had claimed that these values would always
269 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
271 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
272 - Fix a compilation warning on some versions of GCC when building
273 code that calls routerinfo_get_my_routerinfo() twice, assuming
274 that the second call will succeed if the first one did. Fixes bug
275 26269; bugfix on 0.2.8.2-alpha.
277 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
278 - Don't consider Tor running as a client if the ControlPort is open,
279 but no actual client ports are open. Fixes bug 26062; bugfix
282 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
283 - Prevent a possible out-of-bounds smartlist read in
284 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
286 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
287 - Fix a very unlikely (impossible, we believe) null pointer
288 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
289 Coverity; this is CID 1430932.
291 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
292 - Fix a memory leak when a v3 onion service is configured and gets a
293 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
294 - When parsing the descriptor signature, look for the token plus an
295 extra white-space at the end. This is more correct but also will
296 allow us to support new fields that might start with "signature".
297 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
299 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
300 - Relays now correctly block attempts to re-extend to the previous
301 relay by Ed25519 identity. Previously they would warn in this
302 case, but not actually reject the attempt. Fixes bug 26158; bugfix
305 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
306 - Avoid a crash when running with DirPort set but ORPort turned off.
307 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
309 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
310 - Silence unused-const-variable warnings in zstd.h with some GCC
311 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
313 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
314 - Avoid intermittent test failures due to a test that had relied on
315 onion service introduction point creation finishing within 5
316 seconds of real clock time. Fixes bug 25450; bugfix
319 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
320 - Fix a C99 compliance issue in our configuration script that caused
321 compilation issues when compiling Tor with certain versions of
322 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
324 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
325 - Fix a number of small memory leaks identified by coverity. Fixes
326 bug 26467; bugfix on numerous Tor versions.
328 o Code simplification and refactoring (backport from 0.3.3.5-rc):
329 - Move the list of default directory authorities to its own file.
330 Closes ticket 24854. Patch by "beastr0".
333 Changes in version 0.2.9.16 - 2018-07-13
334 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
335 bridge relays should upgrade. We also take this opportunity to backport
338 o Directory authority changes:
339 - The "Bifroest" bridge authority has been retired; the new bridge
340 authority is "Serge", and it is operated by George from the
341 TorBSD project. Closes ticket 26771.
343 o Directory authority changes (backport from 0.3.3.7):
344 - Add an IPv6 address for the "dannenberg" directory authority.
347 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
348 - When directory authorities read a zero-byte bandwidth file, they
349 would previously log a warning with the contents of an
350 uninitialised buffer. They now log a warning about the empty file
351 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
353 o Minor features (sandbox, backport from 0.3.3.4-alpha):
354 - Explicitly permit the poll() system call when the Linux
355 seccomp2-based sandbox is enabled: apparently, some versions of
356 libc use poll() when calling getpwnam(). Closes ticket 25313.
358 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
359 - Our .travis.yml configuration now includes support for testing the
360 results of "make distcheck". (It's not uncommon for "make check"
361 to pass but "make distcheck" to fail.) Closes ticket 25814.
362 - Our Travis CI configuration now integrates with the Coveralls
363 coverage analysis tool. Closes ticket 25818.
365 o Minor features (compilation, backport from 0.3.4.4-rc):
366 - When building Tor, prefer to use Python 3 over Python 2, and more
367 recent (contemplated) versions over older ones. Closes
370 o Minor features (geoip):
371 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
372 Country database. Closes ticket 26674.
374 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
375 - Upon receiving a malformed connected cell, stop processing the
376 cell immediately. Previously we would mark the connection for
377 close, but continue processing the cell as if the connection were
378 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
380 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
381 - Allow the nanosleep() system call, which glibc uses to implement
382 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
384 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
385 - When running the ntor_ref.py test, make sure only to pass strings
386 (rather than "bytes" objects) to the Python subprocess module.
387 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
390 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
391 - Work around a change in OpenSSL 1.1.1 where return values that
392 would previously indicate "no password" now indicate an empty
393 password. Without this workaround, Tor instances running with
394 OpenSSL 1.1.1 would accept descriptors that other Tor instances
395 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
397 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
398 - Fix a compilation warning on some versions of GCC when building
399 code that calls routerinfo_get_my_routerinfo() twice, assuming
400 that the second call will succeed if the first one did. Fixes bug
401 26269; bugfix on 0.2.8.2-alpha.
403 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
404 - Don't consider Tor running as a client if the ControlPort is open,
405 but no actual client ports are open. Fixes bug 26062; bugfix
408 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
409 - Prevent a possible out-of-bounds smartlist read in
410 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
412 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
413 - Fix a very unlikely (impossible, we believe) null pointer
414 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
415 Coverity; this is CID 1430932.
417 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
418 - Fix a number of small memory leaks identified by coverity. Fixes
419 bug 26467; bugfix on numerous Tor versions.
421 o Code simplification and refactoring (backport from 0.3.3.5-rc):
422 - Move the list of default directory authorities to its own file.
423 Closes ticket 24854. Patch by "beastr0".
426 Changes in version 0.3.3.8 - 2018-07-09
427 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
428 fixes for a memory leak affecting directory authorities.
430 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
431 - Stop leaking memory on directory authorities when planning to
432 vote. This bug was crashing authorities by exhausting their
433 memory. Fixes bug 26435; bugfix on 0.3.3.6.
435 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
436 - Make sure that failing tests in Rust will actually cause the build
437 to fail: previously, they were ignored. Fixes bug 26258; bugfix
440 o Minor features (compilation, backport from 0.3.4.4-rc):
441 - When building Tor, prefer to use Python 3 over Python 2, and more
442 recent (contemplated) versions over older ones. Closes
445 o Minor features (geoip):
446 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
447 Country database. Closes ticket 26674.
449 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
450 - Add several checks to detect whether Tor relays are uploading
451 their descriptors without specifying why they regenerated them.
452 Diagnostic for ticket 25686.
454 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
455 - Don't count path selection failures as circuit build failures.
456 This change should eliminate cases where Tor blames its guard or
457 the network for situations like insufficient microdescriptors
458 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
461 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
462 - Fix a compilation warning on some versions of GCC when building
463 code that calls routerinfo_get_my_routerinfo() twice, assuming
464 that the second call will succeed if the first one did. Fixes bug
465 26269; bugfix on 0.2.8.2-alpha.
467 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
468 - Handle the HSADDRESS= argument to the HSPOST command properly.
469 (Previously, this argument was misparsed and thus ignored.) Fixes
470 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
472 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
473 - Fix a number of small memory leaks identified by coverity. Fixes
474 bug 26467; bugfix on numerous Tor versions.
476 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
477 - Relays now correctly block attempts to re-extend to the previous
478 relay by Ed25519 identity. Previously they would warn in this
479 case, but not actually reject the attempt. Fixes bug 26158; bugfix
482 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
483 - When shutting down, Tor now clears all the flags in the control.c
484 module. This should prevent a bug where authentication cookies are
485 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
487 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
488 - When running the hs_ntor_ref.py test, make sure only to pass
489 strings (rather than "bytes" objects) to the Python subprocess
490 module. Python 3 on Windows seems to require this. Fixes bug
491 26535; bugfix on 0.3.1.1-alpha.
492 - When running the ntor_ref.py test, make sure only to pass strings
493 (rather than "bytes" objects) to the Python subprocess module.
494 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
498 Changes in version 0.3.3.7 - 2018-06-12
499 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
500 fixes for bugs affecting compatibility and stability.
502 o Directory authority changes:
503 - Add an IPv6 address for the "dannenberg" directory authority.
506 o Minor features (geoip):
507 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
508 Country database. Closes ticket 26351.
510 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
511 - Work around a change in OpenSSL 1.1.1 where return values that
512 would previously indicate "no password" now indicate an empty
513 password. Without this workaround, Tor instances running with
514 OpenSSL 1.1.1 would accept descriptors that other Tor instances
515 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
517 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
518 - Silence unused-const-variable warnings in zstd.h with some GCC
519 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
521 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
522 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
523 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
524 miscounting the total number of circuits for these field values.)
525 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
527 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
528 - Prevent a possible out-of-bounds smartlist read in
529 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
531 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
532 - Only select relays when they have the descriptors we prefer to use
533 for them. This change fixes a bug where we could select a relay
534 because it had _some_ descriptor, but reject it later with a
535 nonfatal assertion error because it didn't have the exact one we
536 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
539 Changes in version 0.3.3.6 - 2018-05-22
540 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
541 backports several important fixes from the 0.3.4.1-alpha.
543 The Tor 0.3.3 series includes controller support and other
544 improvements for v3 onion services, official support for embedding Tor
545 within other applications, and our first non-trivial module written in
546 the Rust programming language. (Rust is still not enabled by default
547 when building Tor.) And as usual, there are numerous other smaller
548 bugfixes, features, and improvements.
550 Below are the changes since 0.3.3.5-rc. For a list of all changes
551 since 0.3.2.10, see the ReleaseNotes file.
553 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
554 - When directory authorities read a zero-byte bandwidth file, they
555 would previously log a warning with the contents of an
556 uninitialised buffer. They now log a warning about the empty file
557 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
559 o Major bugfixes (security, directory authority, denial-of-service):
560 - Fix a bug that could have allowed an attacker to force a directory
561 authority to use up all its RAM by passing it a maliciously
562 crafted protocol versions string. Fixes bug 25517; bugfix on
563 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
565 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
566 - Avoid a rare assertion failure in the circuit build timeout code
567 if we fail to allow any circuits to actually complete. Fixes bug
568 25733; bugfix on 0.2.2.2-alpha.
570 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
571 - Avoid a crash when testing router reachability on a router that
572 could have an ed25519 ID, but which does not. Fixes bug 25415;
573 bugfix on 0.3.3.2-alpha.
575 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
576 - Correctly detect when onion services get disabled after HUP. Fixes
577 bug 25761; bugfix on 0.3.2.1.
579 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
580 - Impose a limit on circuit cell queue size. The limit can be
581 controlled by a consensus parameter. Fixes bug 25226; bugfix
584 o Minor features (compatibility, backport from 0.3.4.1-alpha):
585 - Avoid some compilation warnings with recent versions of LibreSSL.
588 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
589 - Our .travis.yml configuration now includes support for testing the
590 results of "make distcheck". (It's not uncommon for "make check"
591 to pass but "make distcheck" to fail.) Closes ticket 25814.
592 - Our Travis CI configuration now integrates with the Coveralls
593 coverage analysis tool. Closes ticket 25818.
595 o Minor features (geoip):
596 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
597 database. Closes ticket 26104.
599 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
600 - Don't consider Tor running as a client if the ControlPort is open,
601 but no actual client ports are open. Fixes bug 26062; bugfix
604 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
605 - Upon receiving a malformed connected cell, stop processing the
606 cell immediately. Previously we would mark the connection for
607 close, but continue processing the cell as if the connection were
608 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
610 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
611 - Stop saying in the manual that clients cache ipv4 dns answers from
612 exit relays. We haven't used them since 0.2.6.3-alpha, and in
613 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
614 we forgot to say so in the man page. Fixes bug 26052; bugfix
617 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
618 - Allow the nanosleep() system call, which glibc uses to implement
619 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
621 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
622 - Fix a memory leak when a v3 onion service is configured and gets a
623 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
624 - When parsing the descriptor signature, look for the token plus an
625 extra white-space at the end. This is more correct but also will
626 allow us to support new fields that might start with "signature".
627 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
629 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
630 - Avoid a crash when running with DirPort set but ORPort tuned off.
631 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
633 o Documentation (backport from 0.3.4.1-alpha):
634 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
635 ticket 25857. Patch from "CTassisF".
638 Changes in version 0.3.3.5-rc - 2018-04-15
639 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
640 including some that could affect reliability or correctness.
642 This is the first release candidate in the 0.3.3 series. If we find no
643 new bugs or regression here, then the first stable 0.3.3 release will
644 be nearly identical to this one.
646 o Major bugfixes (security, protover, voting):
647 - Revise Rust implementation of protover to use a more memory-
648 efficient voting algorithm and corresponding data structures, thus
649 avoiding a potential memory-based DoS attack where specially
650 crafted protocol strings would expand to fill available memory.
651 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
653 o Major bugfixes (performance, load balancing):
654 - Directory authorities no longer vote in favor of the Guard flag
655 for relays without directory support. Starting in Tor
656 0.3.0.1-alpha, clients have been avoiding using such relays in the
657 Guard position, leading to increasingly broken load balancing for
658 the 5%-or-so of Guards that don't advertise directory support.
659 Fixes bug 22310; bugfix on 0.3.0.6.
661 o Minor feature (continuous integration):
662 - Update the Travis CI configuration to use the stable Rust channel,
663 now that we have decided to require that. Closes ticket 25714.
665 o Minor features (config options):
666 - Change the way the default value for MaxMemInQueues is calculated.
667 We now use 40% of the hardware RAM if the system has 8 GB RAM or
668 more. Otherwise we use the former value of 75%. Closes
671 o Minor features (geoip):
672 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
673 Country database. Closes ticket 25718.
675 o Minor bugfixes (client):
676 - When using a listed relay as a bridge, and also using
677 microdescriptors, and considering that relay as a non-bridge in a
678 circuit, treat its microdescriptor as a valid source of
679 information about that relay. This change should prevent a non-
680 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
682 o Minor bugfixes (controller):
683 - Restore the correct operation of the RESOLVE command, which had
684 been broken since we added the ability to enable/disable DNS on
685 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
687 o Minor bugfixes (distribution, compilation, rust):
688 - Build correctly when the rust dependencies submodule is loaded,
689 but the TOR_RUST_DEPENDENCIES environment variable is not set.
690 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
691 - Actually include all of our Rust source in our source
692 distributions. (Previously, a few of the files were accidentally
693 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
695 o Minor bugfixes (documentation):
696 - Document that the PerConnBW{Rate,Burst} options will fall back to
697 their corresponding consensus parameters only if those parameters
698 are set. Previously we had claimed that these values would always
699 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
700 - Revert a misformatting issue in the ExitPolicy documentation.
701 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
703 o Minor bugfixes (exit relay DNS retries):
704 - Re-attempt timed-out DNS queries 3 times before failure, since our
705 timeout is 5 seconds for them, but clients wait 10-15. Also allow
706 slightly more timeouts per resolver when an exit has multiple
707 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
709 o Minor bugfixes (onion services):
710 - Re-instate counting the client HSDir fetch circuits against the
711 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
713 - Remove underscores from the _HSLayer{2,3}Nodes options. This
714 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
715 Fixes bug 25581; bugfix on 0.3.3.1-alpha
717 o Code simplification and refactoring:
718 - Move the list of default directory authorities to its own file.
719 Closes ticket 24854. Patch by "beastr0".
721 o Documentation (manpage, denial of service):
722 - Provide more detail about the denial-of-service options, by
723 listing each mitigation and explaining how they relate. Closes
727 Changes in version 0.3.3.4-alpha - 2018-03-29
728 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
729 the alpha testing of earlier releases in its series. We are
730 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
732 o New system requirements:
733 - When built with Rust, Tor now depends on version 0.2.39 of the
734 libc crate. Closes tickets 25310 and 25664.
736 o Major bugfixes (relay, connection):
737 - If we have failed to connect to a relay and received a connection
738 refused, timeout, or similar error (at the TCP level), do not try
739 that same address/port again for 60 seconds after the failure has
740 occurred. Fixes bug 24767; bugfix on 0.0.6.
742 o Minor features (geoip):
743 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
744 Country database. Closes ticket 25469.
746 o Minor features (log messages):
747 - Improve log message in the out-of-memory handler to include
748 information about memory usage from the different compression
749 backends. Closes ticket 25372.
751 o Minor features (sandbox):
752 - Explicitly permit the poll() system call when the Linux
753 seccomp2-based sandbox is enabled: apparently, some versions of
754 libc use poll() when calling getpwnam(). Closes ticket 25313.
756 o Minor bugfixes (C correctness):
757 - Fix a very unlikely (impossible, we believe) null pointer
758 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
759 Coverity; this is CID 1430932.
761 o Minor bugfixes (channel, client):
762 - Better identify client connection when reporting to the geoip
763 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
765 o Minor bugfixes (compilation):
766 - Fix a C99 compliance issue in our configuration script that caused
767 compilation issues when compiling Tor with certain versions of
768 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
770 o Minor bugfixes (controller, reliability):
771 - Avoid a (nonfatal) assertion failure when extending a one-hop
772 circuit from the controller to become a multihop circuit. Fixes
773 bug 24903; bugfix on 0.2.5.2-alpha.
775 o Major bugfixes (networking):
776 - Tor will no longer reject IPv6 address strings from Tor Browser
777 when they are passed as hostnames in SOCKS5 requests. Fixes bug
778 25036, bugfix on Tor 0.3.1.2.
780 o Minor bugfixes (networking):
781 - string_is_valid_hostname() will not consider IP strings to be
782 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
784 o Minor bugfixes (onion service v3):
785 - Avoid an assertion failure when the next onion service
786 descriptor rotation type is out of sync with the consensus's
787 valid-after time. Instead, log a warning message with extra
788 information, so we can better hunt down the cause of this
789 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
791 o Minor bugfixes (testing):
792 - Avoid intermittent test failures due to a test that had relied on
793 onion service introduction point creation finishing within 5
794 seconds of real clock time. Fixes bug 25450; bugfix
796 - Rust crates are now automatically detected and tested. Previously,
797 some crates were not tested by `make test-rust` due to a static
798 string in the `src/test/test_rust.sh` script specifying which
799 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
801 o Minor bugfixes (testing, benchmarks):
802 - Fix a crash when running benchmark tests on win32 systems. The
803 crash was due to a mutex that wasn't initialized before logging
804 and options were initialized. Fixes bug 25479; bugfix
807 o Minor bugfixes (warnings, ipv6):
808 - Avoid a bug warning that could occur when trying to connect to a
809 relay over IPv6. This warning would occur on a Tor instance that
810 downloads router descriptors, but prefers to use microdescriptors.
811 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
813 o Code simplification and refactoring:
814 - Remove the old (deterministic) directory retry logic entirely:
815 We've used exponential backoff exclusively for some time. Closes
819 - Improved the documentation of AccountingStart parameter. Closes
821 - Update the documentation for "Log" to include the current list of
822 logging domains. Closes ticket 25378.
825 Changes in version 0.3.1.10 - 2018-03-03
826 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
829 It includes an important security fix for a remote crash attack
830 against directory authorities, tracked as TROVE-2018-001.
832 This release also backports our new system for improved resistance to
833 denial-of-service attacks against relays.
835 This release also fixes several minor bugs and annoyances from
838 All directory authorities should upgrade to one of the versions
839 released today. Relays running 0.3.1.x may wish to update to one of
840 the versions released today, for the DoS mitigations.
842 Please note: according to our release calendar, Tor 0.3.1 will no
843 longer be supported after 1 July 2018. If you will be running Tor
844 after that date, you should make sure to plan to upgrade to the latest
845 stable version, or downgrade to 0.2.9 (which will receive long-term
848 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
849 - Fix a protocol-list handling bug that could be used to remotely crash
850 directory authorities with a null-pointer exception. Fixes bug 25074;
851 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
854 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
855 - Give relays some defenses against the recent network overload. We
856 start with three defenses (default parameters in parentheses).
857 First: if a single client address makes too many concurrent
858 connections (>100), hang up on further connections. Second: if a
859 single client address makes circuits too quickly (more than 3 per
860 second, with an allowed burst of 90) while also having too many
861 connections open (3), refuse new create cells for the next while
862 (1-2 hours). Third: if a client asks to establish a rendezvous
863 point to you directly, ignore the request. These defenses can be
864 manually controlled by new torrc options, but relays will also
865 take guidance from consensus parameters, so there's no need to
866 configure anything manually. Implements ticket 24902.
868 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
869 - Update the sandbox rules so that they should now work correctly
870 with Glibc 2.26. Closes ticket 24315.
872 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
873 - Fix an "off by 2" error in counting rendezvous failures on the
874 onion service side. While we thought we would stop the rendezvous
875 attempt after one failed circuit, we were actually making three
876 circuit attempts before giving up. Now switch to a default of 2,
877 and allow the consensus parameter "hs_service_max_rdv_failures" to
878 override. Fixes bug 24895; bugfix on 0.0.6.
880 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
881 - Add Link protocol version 5 to the supported protocols list. Fixes
882 bug 25070; bugfix on 0.3.1.1-alpha.
884 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
885 - Fix a set of false positives where relays would consider
886 connections to other relays as being client-only connections (and
887 thus e.g. deserving different link padding schemes) if those
888 relays fell out of the consensus briefly. Now we look only at the
889 initial handshake and whether the connection authenticated as a
890 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
892 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
893 - Make our OOM handler aware of the geoip client history cache so it
894 doesn't fill up the memory. This check is important for IPv6 and
895 our DoS mitigation subsystem. Closes ticket 25122.
897 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
898 - Change relay bandwidth reporting stats interval from 4 hours to 24
899 hours in order to reduce the efficiency of guard discovery
900 attacks. Fixes ticket 23856.
902 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
903 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
904 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
905 since they neither disabled TLS 1.3 nor enabled any of the
906 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
909 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
910 - The fallback directory list has been re-generated based on the
911 current status of the network. Tor uses fallback directories to
912 bootstrap when it doesn't yet have up-to-date directory
913 information. Closes ticket 24801.
914 - Make the default DirAuthorityFallbackRate 0.1, so that clients
915 prefer to bootstrap from fallback directory mirrors. This is a
916 follow-up to 24679, which removed weights from the default
917 fallbacks. Implements ticket 24681.
919 o Minor features (geoip):
920 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
923 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
924 - Use the actual observed address of an incoming relay connection,
925 not the canonical address of the relay from its descriptor, when
926 making decisions about how to handle the incoming connection.
927 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
929 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
930 - Directory authorities, when refusing a descriptor from a rejected
931 relay, now explicitly tell the relay (in its logs) to set a valid
932 ContactInfo address and contact the bad-relays@ mailing list.
933 Fixes bug 25170; bugfix on 0.2.9.1.
935 o Minor bugfixes (address selection, backport from 0.3.2.9):
936 - When the fascist_firewall_choose_address_ functions don't find a
937 reachable address, set the returned address to the null address
938 and port. This is a precautionary measure, because some callers do
939 not check the return value. Fixes bug 24736; bugfix
942 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
943 - Fetch descriptors aggressively whenever we lack enough to build
944 circuits, regardless of how many descriptors we are missing.
945 Previously, we would delay launching the fetch when we had fewer
946 than 15 missing descriptors, even if some of those descriptors
947 were blocking circuits from building. Fixes bug 23985; bugfix on
948 0.1.1.11-alpha. The effects of this bug became worse in
949 0.3.0.3-alpha, when we began treating missing descriptors from our
950 primary guards as a reason to delay circuits.
951 - Don't try fetching microdescriptors from relays that have failed
952 to deliver them in the past. Fixes bug 23817; bugfix
955 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
956 - Fix a signed/unsigned comparison warning introduced by our fix to
957 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
959 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
960 - Avoid a crash when attempting to use the seccomp2 sandbox together
961 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
964 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
965 - Fix a possible crash on malformed consensus. If a consensus had
966 contained an unparseable protocol line, it could have made clients
967 and relays crash with a null-pointer exception. To exploit this
968 issue, however, an attacker would need to be able to subvert the
969 directory authority system. Fixes bug 25251; bugfix on
970 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
972 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
973 - Recover better from empty or corrupt files in the consensus cache
974 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
975 - When a consensus diff calculation is only partially successful,
976 only record the successful parts as having succeeded. Partial
977 success can happen if (for example) one compression method fails
978 but the others succeed. Previously we misrecorded all the
979 calculations as having succeeded, which would later cause a
980 nonfatal assertion failure. Fixes bug 24086; bugfix
983 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
984 - Tor now updates its guard state when it reads a consensus
985 regardless of whether it's missing descriptors. That makes tor use
986 its primary guards to fetch descriptors in some edge cases where
987 it would previously have used fallback directories. Fixes bug
988 23862; bugfix on 0.3.0.1-alpha.
990 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
991 - Don't treat inability to store a cached consensus object as a bug:
992 it can happen normally when we are out of disk space. Fixes bug
993 24859; bugfix on 0.3.1.1-alpha.
995 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
996 - When queuing DESTROY cells on a channel, only queue the circuit-id
997 and reason fields: not the entire 514-byte cell. This fix should
998 help mitigate any bugs or attacks that fill up these queues, and
999 free more RAM for other uses. Fixes bug 24666; bugfix
1002 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
1003 - When closing a connection via close_connection_immediately(), we
1004 mark it as "not blocked on bandwidth", to prevent later calls from
1005 trying to unblock it, and give it permission to read. This fixes a
1006 backtrace warning that can happen on relays under various
1007 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1009 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
1010 - When selecting relays by bandwidth, avoid a rounding error that
1011 could sometimes cause load to be imbalanced incorrectly.
1012 Previously, we would always round upwards; now, we round towards
1013 the nearest integer. This had the biggest effect when a relay's
1014 weight adjustments should have given it weight 0, but it got
1015 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1016 - When calculating the fraction of nodes that have descriptors, and
1017 all nodes in the network have zero bandwidths, count the number of
1018 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1019 - Actually log the total bandwidth in compute_weighted_bandwidths().
1020 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1022 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
1023 - Improve the performance of our consensus-diff application code
1024 when Tor is built with the --enable-fragile-hardening option set.
1025 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1027 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
1028 - Don't exit the Tor process if setrlimit() fails to change the file
1029 limit (which can happen sometimes on some versions of OSX). Fixes
1030 bug 21074; bugfix on 0.0.9pre5.
1032 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
1033 - Fix a bug in the bit-counting parts of our timing-wheel code on
1034 MSVC. (Note that MSVC is still not a supported build platform, due
1035 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
1038 o Minor bugfixes (relay, partial backport):
1039 - Make the internal channel_is_client() function look at what sort
1040 of connection handshake the other side used, rather than whether
1041 the other side ever sent a create_fast cell to us. Backports part
1042 of the fixes from bugs 22805 and 24898.
1044 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1045 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1047 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1048 bugfix on 0.2.9.4-alpha.
1050 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
1051 - Update the "rust dependencies" submodule to be a project-level
1052 repository, rather than a user repository. Closes ticket 25323.
1055 Changes in version 0.2.9.15 - 2018-03-03
1056 Tor 0.2.9.15 backports important security and stability bugfixes from
1059 It includes an important security fix for a remote crash attack
1060 against directory authorities, tracked as TROVE-2018-001.
1062 This release also backports our new system for improved resistance to
1063 denial-of-service attacks against relays.
1065 This release also fixes several minor bugs and annoyances from
1068 All directory authorities should upgrade to one of the versions
1069 released today. Relays running 0.2.9.x may wish to update to one of
1070 the versions released today, for the DoS mitigations.
1072 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1073 - Fix a protocol-list handling bug that could be used to remotely crash
1074 directory authorities with a null-pointer exception. Fixes bug 25074;
1075 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1078 o Major features (denial-of-service mitigation):
1079 - Give relays some defenses against the recent network overload. We
1080 start with three defenses (default parameters in parentheses).
1081 First: if a single client address makes too many concurrent
1082 connections (>100), hang up on further connections. Second: if a
1083 single client address makes circuits too quickly (more than 3 per
1084 second, with an allowed burst of 90) while also having too many
1085 connections open (3), refuse new create cells for the next while
1086 (1-2 hours). Third: if a client asks to establish a rendezvous
1087 point to you directly, ignore the request. These defenses can be
1088 manually controlled by new torrc options, but relays will also
1089 take guidance from consensus parameters, so there's no need to
1090 configure anything manually. Implements ticket 24902.
1092 o Major bugfixes (bootstrapping):
1093 - Fetch descriptors aggressively whenever we lack enough to build
1094 circuits, regardless of how many descriptors we are missing.
1095 Previously, we would delay launching the fetch when we had fewer
1096 than 15 missing descriptors, even if some of those descriptors
1097 were blocking circuits from building. Fixes bug 23985; bugfix on
1098 0.1.1.11-alpha. The effects of this bug became worse in
1099 0.3.0.3-alpha, when we began treating missing descriptors from our
1100 primary guards as a reason to delay circuits.
1102 o Major bugfixes (onion services, retry behavior):
1103 - Fix an "off by 2" error in counting rendezvous failures on the
1104 onion service side. While we thought we would stop the rendezvous
1105 attempt after one failed circuit, we were actually making three
1106 circuit attempts before giving up. Now switch to a default of 2,
1107 and allow the consensus parameter "hs_service_max_rdv_failures" to
1108 override. Fixes bug 24895; bugfix on 0.0.6.
1110 o Minor feature (relay statistics):
1111 - Change relay bandwidth reporting stats interval from 4 hours to 24
1112 hours in order to reduce the efficiency of guard discovery
1113 attacks. Fixes ticket 23856.
1115 o Minor features (compatibility, OpenSSL):
1116 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1117 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1118 since they neither disabled TLS 1.3 nor enabled any of the
1119 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1120 Closes ticket 24978.
1122 o Minor features (denial-of-service avoidance):
1123 - Make our OOM handler aware of the geoip client history cache so it
1124 doesn't fill up the memory. This check is important for IPv6 and
1125 our DoS mitigation subsystem. Closes ticket 25122.
1127 o Minor features (fallback directory mirrors):
1128 - The fallback directory list has been re-generated based on the
1129 current status of the network. Tor uses fallback directories to
1130 bootstrap when it doesn't yet have up-to-date directory
1131 information. Closes ticket 24801.
1132 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1133 prefer to bootstrap from fallback directory mirrors. This is a
1134 follow-up to 24679, which removed weights from the default
1135 fallbacks. Implements ticket 24681.
1137 o Minor features (geoip):
1138 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1141 o Minor features (linux seccomp2 sandbox):
1142 - Update the sandbox rules so that they should now work correctly
1143 with Glibc 2.26. Closes ticket 24315.
1145 o Minor bugfix (channel connection):
1146 - Use the actual observed address of an incoming relay connection,
1147 not the canonical address of the relay from its descriptor, when
1148 making decisions about how to handle the incoming connection.
1149 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1151 o Minor bugfix (directory authority):
1152 - Directory authorities, when refusing a descriptor from a rejected
1153 relay, now explicitly tell the relay (in its logs) to set a valid
1154 ContactInfo address and contact the bad-relays@ mailing list.
1155 Fixes bug 25170; bugfix on 0.2.9.1.
1157 o Minor bugfixes (address selection):
1158 - When the fascist_firewall_choose_address_ functions don't find a
1159 reachable address, set the returned address to the null address
1160 and port. This is a precautionary measure, because some callers do
1161 not check the return value. Fixes bug 24736; bugfix
1164 o Minor bugfixes (compilation):
1165 - Fix a signed/unsigned comparison warning introduced by our fix to
1166 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1168 o Minor bugfixes (control port, linux seccomp2 sandbox):
1169 - Avoid a crash when attempting to use the seccomp2 sandbox together
1170 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1173 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1174 - Fix a possible crash on malformed consensus. If a consensus had
1175 contained an unparseable protocol line, it could have made clients
1176 and relays crash with a null-pointer exception. To exploit this
1177 issue, however, an attacker would need to be able to subvert the
1178 directory authority system. Fixes bug 25251; bugfix on
1179 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1181 o Minor bugfixes (memory usage):
1182 - When queuing DESTROY cells on a channel, only queue the circuit-id
1183 and reason fields: not the entire 514-byte cell. This fix should
1184 help mitigate any bugs or attacks that fill up these queues, and
1185 free more RAM for other uses. Fixes bug 24666; bugfix
1188 o Minor bugfixes (network layer):
1189 - When closing a connection via close_connection_immediately(), we
1190 mark it as "not blocked on bandwidth", to prevent later calls from
1191 trying to unblock it, and give it permission to read. This fixes a
1192 backtrace warning that can happen on relays under various
1193 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1195 o Minor bugfixes (OSX):
1196 - Don't exit the Tor process if setrlimit() fails to change the file
1197 limit (which can happen sometimes on some versions of OSX). Fixes
1198 bug 21074; bugfix on 0.0.9pre5.
1200 o Minor bugfixes (path selection):
1201 - When selecting relays by bandwidth, avoid a rounding error that
1202 could sometimes cause load to be imbalanced incorrectly.
1203 Previously, we would always round upwards; now, we round towards
1204 the nearest integer. This had the biggest effect when a relay's
1205 weight adjustments should have given it weight 0, but it got
1206 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1207 - When calculating the fraction of nodes that have descriptors, and
1208 all nodes in the network have zero bandwidths, count the number of
1209 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1210 - Actually log the total bandwidth in compute_weighted_bandwidths().
1211 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1213 o Minor bugfixes (portability, msvc):
1214 - Fix a bug in the bit-counting parts of our timing-wheel code on
1215 MSVC. (Note that MSVC is still not a supported build platform, due
1216 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
1219 o Minor bugfixes (relay):
1220 - Make the internal channel_is_client() function look at what sort
1221 of connection handshake the other side used, rather than whether
1222 the other side ever sent a create_fast cell to us. Backports part
1223 of the fixes from bugs 22805 and 24898.
1225 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1226 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1228 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1229 bugfix on 0.2.9.4-alpha.
1232 Changes in version 0.3.2.10 - 2018-03-03
1233 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
1234 backports a number of bugfixes, including important fixes for security
1237 It includes an important security fix for a remote crash attack
1238 against directory authorities, tracked as TROVE-2018-001.
1240 Additionally, it backports a fix for a bug whose severity we have
1241 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
1242 triggered in order to crash relays with a use-after-free pattern. As
1243 such, we are now tracking that bug as TROVE-2018-002 and
1244 CVE-2018-0491, and backporting it to earlier releases. This bug
1245 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
1248 This release also backports our new system for improved resistance to
1249 denial-of-service attacks against relays.
1251 This release also fixes several minor bugs and annoyances from
1254 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
1255 today, for the fix to TROVE-2018-002. Directory authorities should
1256 also upgrade. (Relays on earlier versions might want to update too for
1257 the DoS mitigations.)
1259 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1260 - Fix a protocol-list handling bug that could be used to remotely crash
1261 directory authorities with a null-pointer exception. Fixes bug 25074;
1262 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1265 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
1266 - Avoid adding the same channel twice in the KIST scheduler pending
1267 list, which could lead to remote denial-of-service use-after-free
1268 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
1270 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
1271 - Give relays some defenses against the recent network overload. We
1272 start with three defenses (default parameters in parentheses).
1273 First: if a single client address makes too many concurrent
1274 connections (>100), hang up on further connections. Second: if a
1275 single client address makes circuits too quickly (more than 3 per
1276 second, with an allowed burst of 90) while also having too many
1277 connections open (3), refuse new create cells for the next while
1278 (1-2 hours). Third: if a client asks to establish a rendezvous
1279 point to you directly, ignore the request. These defenses can be
1280 manually controlled by new torrc options, but relays will also
1281 take guidance from consensus parameters, so there's no need to
1282 configure anything manually. Implements ticket 24902.
1284 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
1285 - Fix an "off by 2" error in counting rendezvous failures on the
1286 onion service side. While we thought we would stop the rendezvous
1287 attempt after one failed circuit, we were actually making three
1288 circuit attempts before giving up. Now switch to a default of 2,
1289 and allow the consensus parameter "hs_service_max_rdv_failures" to
1290 override. Fixes bug 24895; bugfix on 0.0.6.
1291 - New-style (v3) onion services now obey the "max rendezvous circuit
1292 attempts" logic. Previously they would make as many rendezvous
1293 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
1294 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
1296 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
1297 - Add Link protocol version 5 to the supported protocols list. Fixes
1298 bug 25070; bugfix on 0.3.1.1-alpha.
1300 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
1301 - Fix a set of false positives where relays would consider
1302 connections to other relays as being client-only connections (and
1303 thus e.g. deserving different link padding schemes) if those
1304 relays fell out of the consensus briefly. Now we look only at the
1305 initial handshake and whether the connection authenticated as a
1306 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1308 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
1309 - The scheduler subsystem was failing to promptly notice changes in
1310 consensus parameters, making it harder to switch schedulers
1311 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
1313 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
1314 - Make our OOM handler aware of the geoip client history cache so it
1315 doesn't fill up the memory. This check is important for IPv6 and
1316 our DoS mitigation subsystem. Closes ticket 25122.
1318 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
1319 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1320 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1321 since they neither disabled TLS 1.3 nor enabled any of the
1322 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1323 Closes ticket 24978.
1325 o Minor features (geoip):
1326 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1329 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
1330 - When logging a failure to create an onion service's descriptor,
1331 also log what the problem with the descriptor was. Diagnostic
1334 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
1335 - Use the actual observed address of an incoming relay connection,
1336 not the canonical address of the relay from its descriptor, when
1337 making decisions about how to handle the incoming connection.
1338 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1340 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1341 - Fix a possible crash on malformed consensus. If a consensus had
1342 contained an unparseable protocol line, it could have made clients
1343 and relays crash with a null-pointer exception. To exploit this
1344 issue, however, an attacker would need to be able to subvert the
1345 directory authority system. Fixes bug 25251; bugfix on
1346 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1348 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
1349 - Directory authorities, when refusing a descriptor from a rejected
1350 relay, now explicitly tell the relay (in its logs) to set a valid
1351 ContactInfo address and contact the bad-relays@ mailing list.
1352 Fixes bug 25170; bugfix on 0.2.9.1.
1354 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
1355 - When building with Rust on OSX, link against libresolv, to work
1356 around the issue at https://github.com/rust-lang/rust/issues/46797.
1357 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
1359 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
1360 - Remove a BUG() statement when a client fetches an onion descriptor
1361 that has a lower revision counter than the one in its cache. This
1362 can happen in normal circumstances due to HSDir desync. Fixes bug
1363 24976; bugfix on 0.3.2.1-alpha.
1365 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
1366 - Don't treat inability to store a cached consensus object as a bug:
1367 it can happen normally when we are out of disk space. Fixes bug
1368 24859; bugfix on 0.3.1.1-alpha.
1370 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
1371 - Improve the performance of our consensus-diff application code
1372 when Tor is built with the --enable-fragile-hardening option set.
1373 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1375 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
1376 - Don't exit the Tor process if setrlimit() fails to change the file
1377 limit (which can happen sometimes on some versions of OSX). Fixes
1378 bug 21074; bugfix on 0.0.9pre5.
1380 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1381 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1383 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1384 bugfix on 0.2.9.4-alpha.
1386 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
1387 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
1388 25005; bugfix on 0.3.2.7-rc.
1390 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
1391 - Look at the "HSRend" protocol version, not the "HSDir" protocol
1392 version, when deciding whether a consensus entry can support the
1393 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
1394 bugfix on 0.3.2.1-alpha.
1396 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
1397 - Update the "rust dependencies" submodule to be a project-level
1398 repository, rather than a user repository. Closes ticket 25323.
1400 o Documentation (backport from 0.3.3.1-alpha)
1401 - Document that operators who run more than one relay or bridge are
1402 expected to set MyFamily and ContactInfo correctly. Closes
1406 Changes in version 0.3.3.3-alpha - 2018-03-03
1407 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
1408 It includes an important security fix for a remote crash attack
1409 against directory authorities tracked as TROVE-2018-001.
1411 Additionally, with this release, we are upgrading the severity of a
1412 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
1413 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
1414 a use-after-free pattern. As such, we are now tracking that bug as
1415 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
1416 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
1418 This release also fixes several minor bugs and annoyances from
1421 Relays running 0.3.2.x should upgrade to one of the versions released
1422 today, for the fix to TROVE-2018-002. Directory authorities should
1423 also upgrade. (Relays on earlier versions might want to update too for
1424 the DoS mitigations.)
1426 o Major bugfixes (denial-of-service, directory authority):
1427 - Fix a protocol-list handling bug that could be used to remotely crash
1428 directory authorities with a null-pointer exception. Fixes bug 25074;
1429 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1432 o Minor features (compatibility, OpenSSL):
1433 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1434 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1435 since they neither disabled TLS 1.3 nor enabled any of the
1436 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1437 Closes ticket 24978.
1439 o Minor features (logging):
1440 - Clarify the log messages produced when getrandom() or a related
1441 entropy-generation mechanism gives an error. Closes ticket 25120.
1443 o Minor features (testing):
1444 - Add a "make test-rust" target to run the rust tests only. Closes
1447 o Minor bugfixes (denial-of-service):
1448 - Fix a possible crash on malformed consensus. If a consensus had
1449 contained an unparseable protocol line, it could have made clients
1450 and relays crash with a null-pointer exception. To exploit this
1451 issue, however, an attacker would need to be able to subvert the
1452 directory authority system. Fixes bug 25251; bugfix on
1453 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1455 o Minor bugfixes (DoS mitigation):
1456 - Add extra safety checks when refilling the circuit creation bucket
1457 to ensure we never set a value above the allowed maximum burst.
1458 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
1459 - When a new consensus arrives, don't update our DoS-mitigation
1460 parameters if we aren't a public relay. Fixes bug 25223; bugfix
1463 o Minor bugfixes (man page, SocksPort):
1464 - Remove dead code from the old "SocksSocket" option, and rename
1465 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
1466 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
1468 o Minor bugfixes (performance):
1469 - Reduce the number of circuits that will be opened at once during
1470 the circuit build timeout phase. This is done by increasing the
1471 idle timeout to 3 minutes, and lowering the maximum number of
1472 concurrent learning circuits to 10. Fixes bug 24769; bugfix
1475 o Minor bugfixes (spec conformance):
1476 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1478 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1479 bugfix on 0.2.9.4-alpha.
1481 o Minor bugfixes (spec conformance, rust):
1482 - Resolve a denial-of-service issue caused by an infinite loop in
1483 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
1484 Also tracked as TROVE-2018-003.
1486 o Code simplification and refactoring:
1487 - Update the "rust dependencies" submodule to be a project-level
1488 repository, rather than a user repository. Closes ticket 25323.
1491 Changes in version 0.3.3.2-alpha - 2018-02-10
1492 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
1493 introduces a mechanism to handle the high loads that many relay
1494 operators have been reporting recently. It also fixes several bugs in
1495 older releases. If this new code proves reliable, we plan to backport
1496 it to older supported release series.
1498 o Major features (denial-of-service mitigation):
1499 - Give relays some defenses against the recent network overload. We
1500 start with three defenses (default parameters in parentheses).
1501 First: if a single client address makes too many concurrent
1502 connections (>100), hang up on further connections. Second: if a
1503 single client address makes circuits too quickly (more than 3 per
1504 second, with an allowed burst of 90) while also having too many
1505 connections open (3), refuse new create cells for the next while
1506 (1-2 hours). Third: if a client asks to establish a rendezvous
1507 point to you directly, ignore the request. These defenses can be
1508 manually controlled by new torrc options, but relays will also
1509 take guidance from consensus parameters, so there's no need to
1510 configure anything manually. Implements ticket 24902.
1512 o Major bugfixes (netflow padding):
1513 - Stop adding unneeded channel padding right after we finish
1514 flushing to a connection that has been trying to flush for many
1515 seconds. Instead, treat all partial or complete flushes as
1516 activity on the channel, which will defer the time until we need
1517 to add padding. This fix should resolve confusing and scary log
1518 messages like "Channel padding timeout scheduled 221453ms in the
1519 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
1521 o Major bugfixes (protocol versions):
1522 - Add Link protocol version 5 to the supported protocols list. Fixes
1523 bug 25070; bugfix on 0.3.1.1-alpha.
1525 o Major bugfixes (scheduler, consensus):
1526 - The scheduler subsystem was failing to promptly notice changes in
1527 consensus parameters, making it harder to switch schedulers
1528 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
1530 o Minor features (denial-of-service avoidance):
1531 - Make our OOM handler aware of the geoip client history cache so it
1532 doesn't fill up the memory. This check is important for IPv6 and
1533 our DoS mitigation subsystem. Closes ticket 25122.
1535 o Minor features (directory authority):
1536 - When directory authorities are unable to add signatures to a
1537 pending consensus, log the reason why. Closes ticket 24849.
1539 o Minor features (geoip):
1540 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1543 o Minor features (logging, diagnostic):
1544 - When logging a failure to create an onion service's descriptor,
1545 also log what the problem with the descriptor was. Diagnostic for
1548 o Minor bugfix (channel connection):
1549 - Use the actual observed address of an incoming relay connection,
1550 not the canonical address of the relay from its descriptor, when
1551 making decisions about how to handle the incoming connection.
1552 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1554 o Minor bugfix (directory authority):
1555 - Directory authorities, when refusing a descriptor from a rejected
1556 relay, now explicitly tell the relay (in its logs) to set a valid
1557 ContactInfo address and contact the bad-relays@ mailing list.
1558 Fixes bug 25170; bugfix on 0.2.9.1.
1560 o Minor bugfixes (all versions of Tor):
1561 - Use the "misspell" tool to detect and fix typos throughout the
1562 source code. Fixes bug 23650; bugfix on various versions of Tor.
1563 Patch from Deepesh Pathak.
1565 o Minor bugfixes (circuit, cannibalization):
1566 - Don't cannibalize preemptively-built circuits if we no longer
1567 recognize their first hop. This situation can happen if our Guard
1568 relay went off the consensus after the circuit was created. Fixes
1569 bug 24469; bugfix on 0.0.6.
1571 o Minor bugfixes (correctness):
1572 - Remove a nonworking, unnecessary check to see whether a circuit
1573 hop's identity digest was set when the circuit failed. Fixes bug
1574 24927; bugfix on 0.2.4.4-alpha.
1576 o Minor bugfixes (logging):
1577 - Don't treat inability to store a cached consensus object as a bug:
1578 it can happen normally when we are out of disk space. Fixes bug
1579 24859; bugfix on 0.3.1.1-alpha.
1580 - Fix a (mostly harmless) race condition when invoking
1581 LOG_PROTOCOL_WARN message from a subthread while the torrc options
1582 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
1584 o Minor bugfixes (onion services):
1585 - Remove a BUG() statement when a client fetches an onion descriptor
1586 that has a lower revision counter than the one in its cache. This
1587 can happen in normal circumstances due to HSDir desync. Fixes bug
1588 24976; bugfix on 0.3.2.1-alpha.
1589 - If we are configured to offer a single onion service, don't log
1590 long-term established one hop rendezvous points in the heartbeat.
1591 Fixes bug 25116; bugfix on 0.2.9.6-rc.
1593 o Minor bugfixes (performance):
1594 - Avoid calling protocol_list_supports_protocol() from inside tight
1595 loops when running with cached routerinfo_t objects. Instead,
1596 summarize the relevant protocols as flags in the routerinfo_t, as
1597 we do for routerstatus_t objects. This change simplifies our code
1598 a little, and saves a large amount of short-term memory allocation
1599 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
1601 o Minor bugfixes (Rust FFI):
1602 - Fix a minor memory leak which would happen whenever the C code
1603 would call the Rust implementation of
1604 protover_get_supported_protocols(). This was due to the C version
1605 returning a static string, whereas the Rust version newly allocated
1606 a CString to pass across the FFI boundary. Consequently, the C
1607 code was not expecting to need to free() what it was given. Fixes
1608 bug 25127; bugfix on 0.3.2.1-alpha.
1610 o Minor bugfixes (scheduler, KIST):
1611 - Avoid adding the same channel twice in the KIST scheduler pending
1612 list, which would waste CPU cycles. Fixes bug 24700; bugfix
1615 o Minor bugfixes (unit test, monotonic time):
1616 - Increase a constant (1msec to 10msec) in the monotonic time test
1617 that makes sure the nsec/usec/msec times read are synchronized.
1618 This change was needed to accommodate slow systems like armel or
1619 when the clock_gettime() is not a VDSO on the running kernel.
1620 Fixes bug 25113; bugfix on 0.2.9.1.
1622 o Minor bugfixes (v3 onion services):
1623 - Look at the "HSRend" protocol version, not the "HSDir" protocol
1624 version, when deciding whether a consensus entry can support the
1625 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
1626 bugfix on 0.3.2.1-alpha.
1628 o Code simplification and refactoring:
1629 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
1631 - Remove a series of counters used to track circuit extend attempts
1632 and connection status but that in reality we aren't using for
1633 anything other than stats logged by a SIGUSR1 signal. Closes
1636 o Documentation (man page):
1637 - The HiddenServiceVersion torrc option accepts only one number:
1638 either version 2 or 3. Closes ticket 25026; bugfix
1642 Changes in version 0.3.3.1-alpha - 2018-01-25
1643 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
1644 several new features to Tor, including several improvements to
1645 bootstrapping, and support for an experimental "vanguards" feature to
1646 resist guard discovery attacks. This series also includes better
1647 support for applications that need to embed Tor or manage v3
1650 o Major features (embedding):
1651 - There is now a documented stable API for programs that need to
1652 embed Tor. See tor_api.h for full documentation and known bugs.
1653 Closes ticket 23684.
1654 - Tor now has support for restarting in the same process.
1655 Controllers that run Tor using the "tor_api.h" interface can now
1656 restart Tor after Tor has exited. This support is incomplete,
1657 however: we fixed crash bugs that prevented it from working at
1658 all, but many bugs probably remain, including a possibility of
1659 security issues. Implements ticket 24581.
1661 o Major features (IPv6, directory documents):
1662 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
1663 consensus. This information makes it easier for IPv6 clients to
1664 bootstrap and choose reachable entry guards. Implements ticket 23826.
1665 - Add consensus method 28, which removes IPv6 ORPorts from
1666 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
1667 are redundant in microdescs. This change will be used by Tor clients
1668 on 0.2.8.x and later. (That is to say, with all Tor clients that
1669 have IPv6 bootstrap and guard support.) Implements ticket 23828.
1670 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
1671 set by different numbers of authorities. Fixes 23870
1674 o Major features (onion service v3, control port):
1675 - The control port now supports commands and events for v3 onion
1676 services. It is now possible to create ephemeral v3 services using
1677 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
1678 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
1679 DEL_ONION) have been extended to support v3 onion services. Closes
1680 ticket 20699; implements proposal 284.
1682 o Major features (onion services):
1683 - Provide torrc options to pin the second and third hops of onion
1684 service circuits to a list of nodes. The option HSLayer2Guards
1685 pins the second hop, and the option HSLayer3Guards pins the third
1686 hop. These options are for use in conjunction with experiments
1687 with "vanguards" for preventing guard enumeration attacks. Closes
1690 o Major features (rust, portability, experimental):
1691 - Tor now ships with an optional implementation of one of its
1692 smaller modules (protover.c) in the Rust programming language. To
1693 try it out, install a Rust build environment, and configure Tor
1694 with "--enable-rust --enable-cargo-online-mode". This should not
1695 cause any user-visible changes, but should help us gain more
1696 experience with Rust, and plan future Rust integration work.
1697 Implementation by Chelsea Komlo. Closes ticket 22840.
1699 o Minor features (storage, configuration):
1700 - Users can store cached directory documents somewhere other than
1701 the DataDirectory by using the CacheDirectory option. Similarly,
1702 the storage location for relay's keys can be overridden with the
1703 KeyDirectory option. Closes ticket 22703.
1705 o Major features (v3 onion services, ipv6):
1706 - When v3 onion service clients send introduce cells, they now
1707 include the IPv6 address of the rendezvous point, if it has one.
1708 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
1709 in future Tor versions, IPv6-only v3 single onion services will be
1710 able to use IPv6 addresses to connect directly to the rendezvous
1711 point. Closes ticket 23577. Patch by Neel Chauhan.
1713 o Major bugfixes (onion services, retry behavior):
1714 - Fix an "off by 2" error in counting rendezvous failures on the
1715 onion service side. While we thought we would stop the rendezvous
1716 attempt after one failed circuit, we were actually making three
1717 circuit attempts before giving up. Now switch to a default of 2,
1718 and allow the consensus parameter "hs_service_max_rdv_failures" to
1719 override. Fixes bug 24895; bugfix on 0.0.6.
1720 - New-style (v3) onion services now obey the "max rendezvous circuit
1721 attempts" logic. Previously they would make as many rendezvous
1722 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
1723 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
1725 o Major bugfixes (relays):
1726 - Fix a set of false positives where relays would consider
1727 connections to other relays as being client-only connections (and
1728 thus e.g. deserving different link padding schemes) if those
1729 relays fell out of the consensus briefly. Now we look only at the
1730 initial handshake and whether the connection authenticated as a
1731 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1733 o Minor feature (IPv6):
1734 - Make IPv6-only clients wait for microdescs for relays, even if we
1735 were previously using descriptors (or were using them as a bridge)
1736 and have a cached descriptor for them. Implements ticket 23827.
1737 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
1738 them, rather than waiting to download microdescriptors.
1739 Implements ticket 23827.
1741 o Minor features (cleanup):
1742 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
1743 when it stops. Closes ticket 23271.
1745 o Minor features (defensive programming):
1746 - Most of the functions in Tor that free objects have been replaced
1747 with macros that free the objects and set the corresponding
1748 pointers to NULL. This change should help prevent a large class of
1749 dangling pointer bugs. Closes ticket 24337.
1750 - Where possible, the tor_free() macro now only evaluates its input
1751 once. Part of ticket 24337.
1752 - Check that microdesc ed25519 ids are non-zero in
1753 node_get_ed25519_id() before returning them. Implements ticket
1754 24001, patch by "aruna1234".
1756 o Minor features (embedding):
1757 - Tor can now start with a preauthenticated control connection
1758 created by the process that launched it. This feature is meant for
1759 use by programs that want to launch and manage a Tor process
1760 without allowing other programs to manage it as well. For more
1761 information, see the __OwningControllerFD option documented in
1762 control-spec.txt. Closes ticket 23900.
1763 - On most errors that would cause Tor to exit, it now tries to
1764 return from the tor_main() function, rather than calling the
1765 system exit() function. Most users won't notice a difference here,
1766 but it should be significant for programs that run Tor inside
1767 a separate thread: they should now be able to survive Tor's exit
1768 conditions rather than having Tor shut down the entire process.
1769 Closes ticket 23848.
1770 - Applications that want to embed Tor can now tell Tor not to
1771 register any of its own POSIX signal handlers, using the
1772 __DisableSignalHandlers option. Closes ticket 24588.
1774 o Minor features (fallback directory list):
1775 - Avoid selecting fallbacks that change their IP addresses too
1776 often. Select more fallbacks by ignoring the Guard flag, and
1777 allowing lower cutoffs for the Running and V2Dir flags. Also allow
1778 a lower bandwidth, and a higher number of fallbacks per operator
1779 (5% of the list). Implements ticket 24785.
1780 - Update the fallback whitelist and blacklist based on opt-ins and
1781 relay changes. Closes tickets 22321, 24678, 22527, 24135,
1784 o Minor features (fallback directory mirror configuration):
1785 - Add a nickname to each fallback in a C comment. This makes it
1786 easier for operators to find their relays, and allows stem to use
1787 nicknames to identify fallbacks. Implements ticket 24600.
1788 - Add a type and version header to the fallback directory mirror
1789 file. Also add a delimiter to the end of each fallback entry. This
1790 helps external parsers like stem and Relay Search. Implements
1792 - Add an extrainfo cache flag for each fallback in a C comment. This
1793 allows stem to use fallbacks to fetch extra-info documents, rather
1794 than using authorities. Implements ticket 22759.
1795 - Add the generateFallbackDirLine.py script for automatically
1796 generating fallback directory mirror lines from relay fingerprints.
1797 No more typos! Add the lookupFallbackDirContact.py script for
1798 automatically looking up operator contact info from relay
1799 fingerprints. Implements ticket 24706, patch by teor and atagar.
1800 - Reject any fallback directory mirror that serves an expired
1801 consensus. Implements ticket 20942, patch by "minik".
1802 - Remove commas and equals signs from external string inputs to the
1803 fallback list. This avoids format confusion attacks. Implements
1805 - Remove the "weight=10" line from fallback directory mirror
1806 entries. Ticket 24681 will maintain the current fallback weights
1807 by changing Tor's default fallback weight to 10. Implements
1809 - Stop logging excessive information about fallback netblocks.
1810 Implements ticket 24791.
1812 o Minor features (forward-compatibility):
1813 - If a relay supports some link authentication protocol that we do
1814 not recognize, then include that relay's ed25519 key when telling
1815 other relays to extend to it. Previously, we treated future
1816 versions as if they were too old to support ed25519 link
1817 authentication. Closes ticket 20895.
1819 o Minor features (heartbeat):
1820 - Add onion service information to our heartbeat logs, displaying
1821 stats about the activity of configured onion services. Closes
1824 o Minor features (instrumentation, development):
1825 - Add the MainloopStats option to allow developers to get
1826 instrumentation information from the main event loop via the
1827 heartbeat messages. We hope to use this to improve Tor's behavior
1828 when it's trying to sleep. Closes ticket 24605.
1830 o Minor features (log messages):
1831 - Improve a warning message that happens when we fail to re-parse an
1832 old router because of an expired certificate. Closes ticket 20020.
1833 - Make the log more quantitative when we hit MaxMemInQueues
1834 threshold exposing some values. Closes ticket 24501.
1836 o Minor features (logging, android):
1837 - Added support for the Android logging subsystem. Closes
1840 o Minor features (performance):
1841 - Support predictive circuit building for onion service circuits
1842 with multiple layers of guards. Closes ticket 23101.
1843 - Use stdatomic.h where available, rather than mutexes, to implement
1844 atomic_counter_t. Closes ticket 23953.
1846 o Minor features (performance, 32-bit):
1847 - Improve performance on 32-bit systems by avoiding 64-bit division
1848 when calculating the timestamp in milliseconds for channel padding
1849 computations. Implements ticket 24613.
1850 - Improve performance on 32-bit systems by avoiding 64-bit division
1851 when timestamping cells and buffer chunks for OOM calculations.
1852 Implements ticket 24374.
1854 o Minor features (performance, OSX, iOS):
1855 - Use the mach_approximate_time() function (when available) to
1856 implement coarse monotonic time. Having a coarse time function
1857 should avoid a large number of system calls, and improve
1858 performance slightly, especially under load. Closes ticket 24427.
1860 o Minor features (performance, windows):
1861 - Improve performance on Windows Vista and Windows 7 by adjusting
1862 TCP send window size according to the recommendation from
1863 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
1866 o Major features (relay):
1867 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
1868 operator to use a more reasonable ("reduced") exit policy, rather
1869 than the default one. If you want to run an exit node without
1870 thinking too hard about which ports to allow, this one is for you.
1871 Closes ticket 13605. Patch from Neel Chauhan.
1873 o Minor features (testing, debugging, embedding):
1874 - For development purposes, Tor now has a mode in which it runs for
1875 a few seconds, then stops, and starts again without exiting the
1876 process. This mode is meant to help us debug various issues with
1877 ticket 23847. To use this feature, compile with
1878 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
1879 environment variable. This is expected to crash a lot, and is
1880 really meant for developers only. It will likely be removed in a
1881 future release. Implements ticket 24583.
1883 o Minor bugfix (network IPv6 test):
1884 - Tor's test scripts now check if "ping -6 ::1" works when the user
1885 runs "make test-network-all". Fixes bug 24677; bugfix on
1886 0.2.9.3-alpha. Patch by "ffmancera".
1888 o Minor bugfixes (build, rust):
1889 - Fix output of autoconf checks to display success messages for Rust
1890 dependencies and a suitable rustc compiler version. Fixes bug
1891 24612; bugfix on 0.3.1.3-alpha.
1892 - When building with Rust on OSX, link against libresolv, to work
1893 around the issue at https://github.com/rust-lang/rust/issues/46797.
1894 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
1895 - Don't pass the --quiet option to cargo: it seems to suppress some
1896 errors, which is not what we want to do when building. Fixes bug
1897 24518; bugfix on 0.3.1.7.
1898 - Build correctly when building from outside Tor's source tree with
1899 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
1902 o Minor bugfixes (directory authorities, IPv6):
1903 - When creating a routerstatus (vote) from a routerinfo (descriptor),
1904 set the IPv6 address to the unspecified IPv6 address, and
1905 explicitly initialize the port to zero. Fixes bug 24488; bugfix
1908 o Minor bugfixes (fallback directory mirrors):
1909 - Make updateFallbackDirs.py search harder for python. (Some OSs
1910 don't put it in /usr/bin.) Fixes bug 24708; bugfix
1913 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
1914 - When hibernating, close connections normally and allow them to
1915 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
1917 - Do not attempt to launch self-reachability tests when entering
1918 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
1919 - Resolve several bugs related to descriptor fetching on bridge
1920 clients with bandwidth accounting enabled. (This combination is
1921 not recommended!) Fixes a case of bug 12062; bugfix
1923 - When hibernating, do not attempt to launch DNS checks. Fixes a
1924 case of bug 12062; bugfix on 0.1.2.2-alpha.
1925 - When hibernating, do not try to upload or download descriptors.
1926 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
1928 o Minor bugfixes (IPv6, bridges):
1929 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
1930 bugfix on 0.2.8.2-alpha.
1931 - Tor now sets IPv6 address in the routerstatus as well as in the
1932 router descriptors when updating addresses for a bridge. Closes
1933 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
1935 o Minor bugfixes (linux seccomp2 sandbox):
1936 - When running with the sandbox enabled, reload configuration files
1937 correctly even when %include was used. Previously we would crash.
1938 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
1940 o Minor bugfixes (memory leaks):
1941 - Avoid possible at-exit memory leaks related to use of Libevent's
1942 event_base_once() function. (This function tends to leak memory if
1943 the event_base is closed before the event fires.) Fixes bug 24584;
1944 bugfix on 0.2.8.1-alpha.
1945 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
1948 o Minor bugfixes (OSX):
1949 - Don't exit the Tor process if setrlimit() fails to change the file
1950 limit (which can happen sometimes on some versions of OSX). Fixes
1951 bug 21074; bugfix on 0.0.9pre5.
1953 o Minor bugfixes (performance, fragile-hardening):
1954 - Improve the performance of our consensus-diff application code
1955 when Tor is built with the --enable-fragile-hardening option set.
1956 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1958 o Minor bugfixes (performance, timeouts):
1959 - Consider circuits for timeout as soon as they complete a hop. This
1960 is more accurate than applying the timeout in
1961 circuit_expire_building() because that function is only called
1962 once per second, which is now too slow for typical timeouts on the
1963 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
1964 - Use onion service circuits (and other circuits longer than 3 hops)
1965 to calculate a circuit build timeout. Previously, Tor only
1966 calculated its build timeout based on circuits that planned to be
1967 exactly 3 hops long. With this change, we include measurements
1968 from all circuits at the point where they complete their third
1969 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
1971 o Minor bugfixes (testing):
1972 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
1973 bugfix on 0.2.3.1-alpha.
1974 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
1975 25005; bugfix on 0.3.2.7-rc.
1977 o Code simplification and refactoring:
1978 - Remove /usr/athena from search path in configure.ac. Closes
1980 - Remove duplicate code in node_has_curve25519_onion_key() and
1981 node_get_curve25519_onion_key(), and add a check for a zero
1982 microdesc curve25519 onion key. Closes ticket 23966, patch by
1983 "aruna1234" and teor.
1984 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
1985 memory allocations with large numbers of OR connections (e.g.
1986 relays). Closes ticket 24119.
1987 - Separate the function that deletes ephemeral files when Tor
1989 - Small changes to Tor's buf_t API to make it suitable for use as a
1990 general-purpose safe string constructor. Closes ticket 22342.
1991 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
1992 avoid source code identifier confusion. Closes ticket 24467.
1993 - The tor_git_revision[] constant no longer needs to be redeclared
1994 by everything that links against the rest of Tor. Done as part of
1995 ticket 23845, to simplify our external API.
1996 - We make extend_info_from_node() use node_get_curve25519_onion_key()
1997 introduced in ticket 23577 to access the curve25519 public keys
1998 rather than accessing it directly. Closes ticket 23760. Patch by
2000 - Add a function to log channels' scheduler state changes to aid
2001 debugging efforts. Closes ticket 24531.
2004 - Add documentation on how to build tor with Rust dependencies
2005 without having to be online. Closes ticket 22907; bugfix
2007 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
2008 traffic. Closes ticket 24318.
2009 - Document that OutboundBindAddress doesn't apply to DNS requests.
2010 Closes ticket 22145. Patch from Aruna Maurya.
2011 - Document that operators who run more than one relay or bridge are
2012 expected to set MyFamily and ContactInfo correctly. Closes
2015 o Code simplification and refactoring (channels):
2016 - Remove the incoming and outgoing channel queues. These were never
2017 used, but still took up a step in our fast path.
2018 - The majority of the channel unit tests have been rewritten and the
2019 code coverage has now been raised to 83.6% for channel.c. Closes
2021 - Remove other dead code from the channel subsystem: All together,
2022 this cleanup has removed more than 1500 lines of code overall and
2023 adding very little except for unit test.
2025 o Code simplification and refactoring (circuit rendezvous):
2026 - Split the client-side rendezvous circuit lookup into two
2027 functions: one that returns only established circuits and another
2028 that returns all kinds of circuits. Closes ticket 23459.
2030 o Code simplification and refactoring (controller):
2031 - Make most of the variables in networkstatus_getinfo_by_purpose()
2032 const. Implements ticket 24489.
2035 Changes in version 0.3.2.9 - 2018-01-09
2036 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
2038 The 0.3.2 series includes our long-anticipated new onion service
2039 design, with numerous security features. (For more information, see
2040 our blog post at https://blog.torproject.org/fall-harvest.) We also
2041 have a new circuit scheduler algorithm for improved performance on
2042 relays everywhere (see https://blog.torproject.org/kist-and-tell),
2043 along with many smaller features and bugfixes.
2045 Per our stable release policy, we plan to support each stable release
2046 series for at least the next nine months, or for three months after
2047 the first stable release of the next series: whichever is longer. If
2048 you need a release with long-term support, we recommend that you stay
2049 with the 0.2.9 series.
2051 Below is a list of the changes since 0.3.2.8-rc. For a list of all
2052 changes since 0.3.1, see the ReleaseNotes file.
2054 o Minor features (fallback directory mirrors):
2055 - The fallback directory list has been re-generated based on the
2056 current status of the network. Tor uses fallback directories to
2057 bootstrap when it doesn't yet have up-to-date directory
2058 information. Closes ticket 24801.
2059 - Make the default DirAuthorityFallbackRate 0.1, so that clients
2060 prefer to bootstrap from fallback directory mirrors. This is a
2061 follow-up to 24679, which removed weights from the default
2062 fallbacks. Implements ticket 24681.
2064 o Minor features (geoip):
2065 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
2068 o Minor bugfixes (address selection):
2069 - When the fascist_firewall_choose_address_ functions don't find a
2070 reachable address, set the returned address to the null address
2071 and port. This is a precautionary measure, because some callers do
2072 not check the return value. Fixes bug 24736; bugfix
2075 o Minor bugfixes (compilation):
2076 - Resolve a few shadowed-variable warnings in the onion service
2077 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
2079 o Minor bugfixes (portability, msvc):
2080 - Fix a bug in the bit-counting parts of our timing-wheel code on
2081 MSVC. (Note that MSVC is still not a supported build platform, due
2082 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
2086 Changes in version 0.3.2.8-rc - 2017-12-21
2087 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
2088 schedulers that had led servers under heavy load to overload their
2089 outgoing connections. All relay operators running earlier 0.3.2.x
2090 versions should upgrade. This version also includes a mitigation for
2091 over-full DESTROY queues leading to out-of-memory conditions: if it
2092 works, we will soon backport it to earlier release series.
2094 This is the second release candidate in the 0.3.2 series. If we find
2095 no new bugs or regression here, then the first stable 0.3.2 release
2096 will be nearly identical to this.
2098 o Major bugfixes (KIST, scheduler):
2099 - The KIST scheduler did not correctly account for data already
2100 enqueued in each connection's send socket buffer, particularly in
2101 cases when the TCP/IP congestion window was reduced between
2102 scheduler calls. This situation lead to excessive per-connection
2103 buffering in the kernel, and a potential memory DoS. Fixes bug
2104 24665; bugfix on 0.3.2.1-alpha.
2106 o Minor features (geoip):
2107 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
2110 o Minor bugfixes (hidden service v3):
2111 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
2112 the probability of reaching a service for a client missing
2113 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
2115 o Minor bugfixes (memory usage):
2116 - When queuing DESTROY cells on a channel, only queue the circuit-id
2117 and reason fields: not the entire 514-byte cell. This fix should
2118 help mitigate any bugs or attacks that fill up these queues, and
2119 free more RAM for other uses. Fixes bug 24666; bugfix
2122 o Minor bugfixes (scheduler, KIST):
2123 - Use a sane write limit for KISTLite when writing onto a connection
2124 buffer instead of using INT_MAX and shoving as much as it can.
2125 Because the OOM handler cleans up circuit queues, we are better
2126 off at keeping them in that queue instead of the connection's
2127 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
2130 Changes in version 0.3.2.7-rc - 2017-12-14
2131 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
2132 including some that could affect reliability or correctness.
2134 This is the first release candidate in the 0.3.2 series. If we find no
2135 new bugs or regression here, then the first stable 0.3.2. release will
2136 be nearly identical to this.
2138 o Major bugfixes (circuit prediction):
2139 - Fix circuit prediction logic so that a client doesn't treat a port
2140 as being "handled" by a circuit if that circuit already has
2141 isolation settings on it. This change should make Tor clients more
2142 responsive by improving their chances of having a pre-created
2143 circuit ready for use when a request arrives. Fixes bug 18859;
2144 bugfix on 0.2.3.3-alpha.
2146 o Minor features (logging):
2147 - Provide better warnings when the getrandom() syscall fails. Closes
2150 o Minor features (portability):
2151 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
2152 (It doesn't yet work with the sandbox enabled.) Closes
2155 o Minor bugfixes (bridge clients, bootstrap):
2156 - Retry directory downloads when we get our first bridge descriptor
2157 during bootstrap or while reconnecting to the network. Keep
2158 retrying every time we get a bridge descriptor, until we have a
2159 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
2160 - Stop delaying bridge descriptor fetches when we have cached bridge
2161 descriptors. Instead, only delay bridge descriptor fetches when we
2162 have at least one reachable bridge. Fixes part of bug 24367;
2163 bugfix on 0.2.0.3-alpha.
2164 - Stop delaying directory fetches when we have cached bridge
2165 descriptors. Instead, only delay bridge descriptor fetches when
2166 all our bridges are definitely unreachable. Fixes part of bug
2167 24367; bugfix on 0.2.0.3-alpha.
2169 o Minor bugfixes (compilation):
2170 - Fix a signed/unsigned comparison warning introduced by our fix to
2171 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
2173 o Minor bugfixes (correctness):
2174 - Fix several places in our codebase where a C compiler would be
2175 likely to eliminate a check, based on assuming that undefined
2176 behavior had not happened elsewhere in the code. These cases are
2177 usually a sign of redundant checking or dubious arithmetic. Found
2178 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
2179 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
2182 o Minor bugfixes (onion service v3):
2183 - Fix a race where an onion service would launch a new intro circuit
2184 after closing an old one, but fail to register it before freeing
2185 the previously closed circuit. This bug was making the service
2186 unable to find the established intro circuit and thus not upload
2187 its descriptor, thus making a service unavailable for up to 24
2188 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
2190 o Minor bugfixes (scheduler, KIST):
2191 - Properly set the scheduler state of an unopened channel in the
2192 KIST scheduler main loop. This prevents a harmless but annoying
2193 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
2194 - Avoid a possible integer overflow when computing the available
2195 space on the TCP buffer of a channel. This had no security
2196 implications; but could make KIST allow too many cells on a
2197 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
2198 - Downgrade to "info" a harmless warning about the monotonic time
2199 moving backwards: This can happen on platform not supporting
2200 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
2203 Changes in version 0.3.2.6-alpha - 2017-12-01
2204 This version of Tor is the latest in the 0.3.2 alpha series. It
2205 includes fixes for several important security issues. All Tor users
2206 should upgrade to this release, or to one of the other releases coming
2209 o Major bugfixes (security):
2210 - Fix a denial of service bug where an attacker could use a
2211 malformed directory object to cause a Tor instance to pause while
2212 OpenSSL would try to read a passphrase from the terminal. (Tor
2213 instances run without a terminal, which is the case for most Tor
2214 packages, are not impacted.) Fixes bug 24246; bugfix on every
2215 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2216 Found by OSS-Fuzz as testcase 6360145429790720.
2217 - Fix a denial of service issue where an attacker could crash a
2218 directory authority using a malformed router descriptor. Fixes bug
2219 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2221 - When checking for replays in the INTRODUCE1 cell data for a
2222 (legacy) onion service, correctly detect replays in the RSA-
2223 encrypted part of the cell. We were previously checking for
2224 replays on the entire cell, but those can be circumvented due to
2225 the malleability of Tor's legacy hybrid encryption. This fix helps
2226 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2227 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2230 o Major bugfixes (security, onion service v2):
2231 - Fix a use-after-free error that could crash v2 Tor onion services
2232 when they failed to open circuits while expiring introduction
2233 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2234 also tracked as TROVE-2017-013 and CVE-2017-8823.
2236 o Major bugfixes (security, relay):
2237 - When running as a relay, make sure that we never build a path
2238 through ourselves, even in the case where we have somehow lost the
2239 version of our descriptor appearing in the consensus. Fixes part
2240 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2241 as TROVE-2017-012 and CVE-2017-8822.
2242 - When running as a relay, make sure that we never choose ourselves
2243 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2244 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2246 o Minor feature (relay statistics):
2247 - Change relay bandwidth reporting stats interval from 4 hours to 24
2248 hours in order to reduce the efficiency of guard discovery
2249 attacks. Fixes ticket 23856.
2251 o Minor features (directory authority):
2252 - Add an IPv6 address for the "bastet" directory authority. Closes
2255 o Minor bugfixes (client):
2256 - By default, do not enable storage of client-side DNS values. These
2257 values were unused by default previously, but they should not have
2258 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
2261 Changes in version 0.3.1.9 - 2017-12-01:
2262 Tor 0.3.1.9 backports important security and stability fixes from the
2263 0.3.2 development series. All Tor users should upgrade to this
2264 release, or to another of the releases coming out today.
2266 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2267 - Fix a denial of service bug where an attacker could use a
2268 malformed directory object to cause a Tor instance to pause while
2269 OpenSSL would try to read a passphrase from the terminal. (Tor
2270 instances run without a terminal, which is the case for most Tor
2271 packages, are not impacted.) Fixes bug 24246; bugfix on every
2272 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2273 Found by OSS-Fuzz as testcase 6360145429790720.
2274 - Fix a denial of service issue where an attacker could crash a
2275 directory authority using a malformed router descriptor. Fixes bug
2276 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2278 - When checking for replays in the INTRODUCE1 cell data for a
2279 (legacy) onion service, correctly detect replays in the RSA-
2280 encrypted part of the cell. We were previously checking for
2281 replays on the entire cell, but those can be circumvented due to
2282 the malleability of Tor's legacy hybrid encryption. This fix helps
2283 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2284 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2287 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2288 - Fix a use-after-free error that could crash v2 Tor onion services
2289 when they failed to open circuits while expiring introduction
2290 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2291 also tracked as TROVE-2017-013 and CVE-2017-8823.
2293 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2294 - When running as a relay, make sure that we never build a path
2295 through ourselves, even in the case where we have somehow lost the
2296 version of our descriptor appearing in the consensus. Fixes part
2297 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2298 as TROVE-2017-012 and CVE-2017-8822.
2299 - When running as a relay, make sure that we never choose ourselves
2300 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2301 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2303 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2304 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2305 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2306 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2307 identifying and finding a workaround to this bug and to Moritz,
2308 Arthur Edelstein, and Roger for helping to track it down and
2311 o Minor features (bridge):
2312 - Bridges now include notice in their descriptors that they are
2313 bridges, and notice of their distribution status, based on their
2314 publication settings. Implements ticket 18329. For more fine-
2315 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2318 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2319 - Add an IPv6 address for the "bastet" directory authority. Closes
2322 o Minor features (geoip):
2323 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2326 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2327 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2328 relays, to prevent spurious address resolutions and descriptor
2329 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2330 bugfix on in 0.2.8.1-alpha.
2332 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2333 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2334 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2336 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2337 - When a circuit is marked for close, do not attempt to package any
2338 cells for channels on that circuit. Previously, we would detect
2339 this condition lower in the call stack, when we noticed that the
2340 circuit had no attached channel, and log an annoying message.
2341 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2343 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
2344 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2345 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2348 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2349 - Avoid a crash when transitioning from client mode to bridge mode.
2350 Previously, we would launch the worker threads whenever our
2351 "public server" mode changed, but not when our "server" mode
2352 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2355 Changes in version 0.3.0.13 - 2017-12-01
2356 Tor 0.3.0.13 backports important security and stability bugfixes from
2357 later Tor releases. All Tor users should upgrade to this release, or
2358 to another of the releases coming out today.
2360 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
2361 2018. If you need a release with long-term support, please stick with
2362 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2364 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2365 - Fix a denial of service bug where an attacker could use a
2366 malformed directory object to cause a Tor instance to pause while
2367 OpenSSL would try to read a passphrase from the terminal. (Tor
2368 instances run without a terminal, which is the case for most Tor
2369 packages, are not impacted.) Fixes bug 24246; bugfix on every
2370 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2371 Found by OSS-Fuzz as testcase 6360145429790720.
2372 - Fix a denial of service issue where an attacker could crash a
2373 directory authority using a malformed router descriptor. Fixes bug
2374 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2376 - When checking for replays in the INTRODUCE1 cell data for a
2377 (legacy) onion service, correctly detect replays in the RSA-
2378 encrypted part of the cell. We were previously checking for
2379 replays on the entire cell, but those can be circumvented due to
2380 the malleability of Tor's legacy hybrid encryption. This fix helps
2381 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2382 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2385 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2386 - Fix a use-after-free error that could crash v2 Tor onion services
2387 when they failed to open circuits while expiring introduction
2388 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2389 also tracked as TROVE-2017-013 and CVE-2017-8823.
2391 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2392 - When running as a relay, make sure that we never build a path
2393 through ourselves, even in the case where we have somehow lost the
2394 version of our descriptor appearing in the consensus. Fixes part
2395 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2396 as TROVE-2017-012 and CVE-2017-8822.
2397 - When running as a relay, make sure that we never choose ourselves
2398 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2399 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2401 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2402 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2403 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2404 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2405 identifying and finding a workaround to this bug and to Moritz,
2406 Arthur Edelstein, and Roger for helping to track it down and
2409 o Minor features (security, windows, backport from 0.3.1.1-alpha):
2410 - Enable a couple of pieces of Windows hardening: one
2411 (HeapEnableTerminationOnCorruption) that has been on-by-default
2412 since Windows 8, and unavailable before Windows 7; and one
2413 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2414 affect us, but shouldn't do any harm. Closes ticket 21953.
2416 o Minor features (bridge, backport from 0.3.1.9):
2417 - Bridges now include notice in their descriptors that they are
2418 bridges, and notice of their distribution status, based on their
2419 publication settings. Implements ticket 18329. For more fine-
2420 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2423 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2424 - Add an IPv6 address for the "bastet" directory authority. Closes
2427 o Minor features (geoip):
2428 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2431 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2432 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2433 relays, to prevent spurious address resolutions and descriptor
2434 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2435 bugfix on in 0.2.8.1-alpha.
2437 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2438 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2439 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2441 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2442 - When a circuit is marked for close, do not attempt to package any
2443 cells for channels on that circuit. Previously, we would detect
2444 this condition lower in the call stack, when we noticed that the
2445 circuit had no attached channel, and log an annoying message.
2446 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2448 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2449 - Avoid a crash when transitioning from client mode to bridge mode.
2450 Previously, we would launch the worker threads whenever our
2451 "public server" mode changed, but not when our "server" mode
2452 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2454 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2455 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2456 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2459 Changes in version 0.2.9.14 - 2017-12-01
2460 Tor 0.3.0.13 backports important security and stability bugfixes from
2461 later Tor releases. All Tor users should upgrade to this release, or
2462 to another of the releases coming out today.
2464 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2465 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2466 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2467 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2468 identifying and finding a workaround to this bug and to Moritz,
2469 Arthur Edelstein, and Roger for helping to track it down and
2472 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2473 - Fix a denial of service bug where an attacker could use a
2474 malformed directory object to cause a Tor instance to pause while
2475 OpenSSL would try to read a passphrase from the terminal. (Tor
2476 instances run without a terminal, which is the case for most Tor
2477 packages, are not impacted.) Fixes bug 24246; bugfix on every
2478 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2479 Found by OSS-Fuzz as testcase 6360145429790720.
2480 - Fix a denial of service issue where an attacker could crash a
2481 directory authority using a malformed router descriptor. Fixes bug
2482 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2484 - When checking for replays in the INTRODUCE1 cell data for a
2485 (legacy) onion service, correctly detect replays in the RSA-
2486 encrypted part of the cell. We were previously checking for
2487 replays on the entire cell, but those can be circumvented due to
2488 the malleability of Tor's legacy hybrid encryption. This fix helps
2489 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2490 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2493 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2494 - Fix a use-after-free error that could crash v2 Tor onion services
2495 when they failed to open circuits while expiring introduction
2496 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2497 also tracked as TROVE-2017-013 and CVE-2017-8823.
2499 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2500 - When running as a relay, make sure that we never build a path
2501 through ourselves, even in the case where we have somehow lost the
2502 version of our descriptor appearing in the consensus. Fixes part
2503 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2504 as TROVE-2017-012 and CVE-2017-8822.
2506 o Minor features (bridge, backport from 0.3.1.9):
2507 - Bridges now include notice in their descriptors that they are
2508 bridges, and notice of their distribution status, based on their
2509 publication settings. Implements ticket 18329. For more fine-
2510 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2513 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2514 - Add an IPv6 address for the "bastet" directory authority. Closes
2517 o Minor features (geoip):
2518 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2521 o Minor features (security, windows, backport from 0.3.1.1-alpha):
2522 - Enable a couple of pieces of Windows hardening: one
2523 (HeapEnableTerminationOnCorruption) that has been on-by-default
2524 since Windows 8, and unavailable before Windows 7; and one
2525 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2526 affect us, but shouldn't do any harm. Closes ticket 21953.
2528 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2529 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2530 relays, to prevent spurious address resolutions and descriptor
2531 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2532 bugfix on in 0.2.8.1-alpha.
2534 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2535 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2536 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2538 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2539 - When a circuit is marked for close, do not attempt to package any
2540 cells for channels on that circuit. Previously, we would detect
2541 this condition lower in the call stack, when we noticed that the
2542 circuit had no attached channel, and log an annoying message.
2543 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2545 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2546 - Avoid a crash when transitioning from client mode to bridge mode.
2547 Previously, we would launch the worker threads whenever our
2548 "public server" mode changed, but not when our "server" mode
2549 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2551 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2552 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2553 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2556 Changes in version 0.2.8.17 - 2017-12-01
2557 Tor 0.2.8.17 backports important security and stability bugfixes from
2558 later Tor releases. All Tor users should upgrade to this release, or
2559 to another of the releases coming out today.
2561 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
2562 2018. If you need a release with long-term support, please upgrade with
2563 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2565 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2566 - Fix a denial of service bug where an attacker could use a
2567 malformed directory object to cause a Tor instance to pause while
2568 OpenSSL would try to read a passphrase from the terminal. (Tor
2569 instances run without a terminal, which is the case for most Tor
2570 packages, are not impacted.) Fixes bug 24246; bugfix on every
2571 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2572 Found by OSS-Fuzz as testcase 6360145429790720.
2573 - When checking for replays in the INTRODUCE1 cell data for a
2574 (legacy) onion service, correctly detect replays in the RSA-
2575 encrypted part of the cell. We were previously checking for
2576 replays on the entire cell, but those can be circumvented due to
2577 the malleability of Tor's legacy hybrid encryption. This fix helps
2578 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2579 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2582 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2583 - Fix a use-after-free error that could crash v2 Tor onion services
2584 when they failed to open circuits while expiring introduction
2585 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2586 also tracked as TROVE-2017-013 and CVE-2017-8823.
2588 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2589 - When running as a relay, make sure that we never build a path through
2590 ourselves, even in the case where we have somehow lost the version of
2591 our descriptor appearing in the consensus. Fixes part of bug 21534;
2592 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
2595 o Minor features (bridge, backport from 0.3.1.9):
2596 - Bridges now include notice in their descriptors that they are
2597 bridges, and notice of their distribution status, based on their
2598 publication settings. Implements ticket 18329. For more fine-
2599 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2602 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2603 - Add an IPv6 address for the "bastet" directory authority. Closes
2606 o Minor features (geoip):
2607 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2610 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2611 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2612 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2615 Changes in version 0.2.5.16 - 2017-12-01
2616 Tor 0.2.5.13 backports important security and stability bugfixes from
2617 later Tor releases. All Tor users should upgrade to this release, or
2618 to another of the releases coming out today.
2620 Note: the Tor 0.2.5 series will no longer be supported after 1 May
2621 2018. If you need a release with long-term support, please upgrade to
2622 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2624 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2625 - Fix a denial of service bug where an attacker could use a
2626 malformed directory object to cause a Tor instance to pause while
2627 OpenSSL would try to read a passphrase from the terminal. (Tor
2628 instances run without a terminal, which is the case for most Tor
2629 packages, are not impacted.) Fixes bug 24246; bugfix on every
2630 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2631 Found by OSS-Fuzz as testcase 6360145429790720.
2632 - When checking for replays in the INTRODUCE1 cell data for a
2633 (legacy) onion service, correctly detect replays in the RSA-
2634 encrypted part of the cell. We were previously checking for
2635 replays on the entire cell, but those can be circumvented due to
2636 the malleability of Tor's legacy hybrid encryption. This fix helps
2637 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2638 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2641 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2642 - When running as a relay, make sure that we never build a path
2643 through ourselves, even in the case where we have somehow lost the
2644 version of our descriptor appearing in the consensus. Fixes part
2645 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2646 as TROVE-2017-012 and CVE-2017-8822.
2648 o Minor features (bridge, backport from 0.3.1.9):
2649 - Bridges now include notice in their descriptors that they are
2650 bridges, and notice of their distribution status, based on their
2651 publication settings. Implements ticket 18329. For more fine-
2652 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2655 o Minor features (geoip):
2656 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2660 Changes in version 0.3.2.5-alpha - 2017-11-22
2661 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
2662 fixes several stability and reliability bugs, including a fix for
2663 intermittent bootstrapping failures that some people have been seeing
2664 since the 0.3.0.x series.
2666 Please test this alpha out -- many of these fixes will soon be
2667 backported to stable Tor versions if no additional bugs are found
2670 o Major bugfixes (bootstrapping):
2671 - Fetch descriptors aggressively whenever we lack enough to build
2672 circuits, regardless of how many descriptors we are missing.
2673 Previously, we would delay launching the fetch when we had fewer
2674 than 15 missing descriptors, even if some of those descriptors
2675 were blocking circuits from building. Fixes bug 23985; bugfix on
2676 0.1.1.11-alpha. The effects of this bug became worse in
2677 0.3.0.3-alpha, when we began treating missing descriptors from our
2678 primary guards as a reason to delay circuits.
2679 - Don't try fetching microdescriptors from relays that have failed
2680 to deliver them in the past. Fixes bug 23817; bugfix
2683 o Minor features (directory authority):
2684 - Make the "Exit" flag assignment only depend on whether the exit
2685 policy allows connections to ports 80 and 443. Previously relays
2686 would get the Exit flag if they allowed connections to one of
2687 these ports and also port 6667. Resolves ticket 23637.
2689 o Minor features (geoip):
2690 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2693 o Minor features (linux seccomp2 sandbox):
2694 - Update the sandbox rules so that they should now work correctly
2695 with Glibc 2.26. Closes ticket 24315.
2697 o Minor features (logging):
2698 - Downgrade a pair of log messages that could occur when an exit's
2699 resolver gave us an unusual (but not forbidden) response. Closes
2701 - Improve the message we log when re-enabling circuit build timeouts
2702 after having received a consensus. Closes ticket 20963.
2704 o Minor bugfixes (compilation):
2705 - Fix a memory leak warning in one of the libevent-related
2706 configuration tests that could occur when manually specifying
2707 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
2708 Found and patched by Alex Xu.
2709 - When detecting OpenSSL on Windows from our configure script, make
2710 sure to try linking with the ws2_32 library. Fixes bug 23783;
2711 bugfix on 0.3.2.2-alpha.
2713 o Minor bugfixes (control port, linux seccomp2 sandbox):
2714 - Avoid a crash when attempting to use the seccomp2 sandbox together
2715 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
2718 o Minor bugfixes (control port, onion services):
2719 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
2720 HS_DESC event when a service is not able to upload a descriptor.
2721 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
2723 o Minor bugfixes (directory cache):
2724 - Recover better from empty or corrupt files in the consensus cache
2725 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
2726 - When a consensus diff calculation is only partially successful,
2727 only record the successful parts as having succeeded. Partial
2728 success can happen if (for example) one compression method fails
2729 but the others succeed. Previously we misrecorded all the
2730 calculations as having succeeded, which would later cause a
2731 nonfatal assertion failure. Fixes bug 24086; bugfix
2734 o Minor bugfixes (logging):
2735 - Only log once if we notice that KIST support is gone. Fixes bug
2736 24158; bugfix on 0.3.2.1-alpha.
2737 - Suppress a log notice when relay descriptors arrive. We already
2738 have a bootstrap progress for this so no need to log notice
2739 everytime tor receives relay descriptors. Microdescriptors behave
2740 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
2742 o Minor bugfixes (network layer):
2743 - When closing a connection via close_connection_immediately(), we
2744 mark it as "not blocked on bandwidth", to prevent later calls from
2745 trying to unblock it, and give it permission to read. This fixes a
2746 backtrace warning that can happen on relays under various
2747 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
2749 o Minor bugfixes (onion services):
2750 - The introduction circuit was being timed out too quickly while
2751 waiting for the rendezvous circuit to complete. Keep the intro
2752 circuit around longer instead of timing out and reopening new ones
2753 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
2754 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2755 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2757 - Silence a warning about failed v3 onion descriptor uploads that
2758 can happen naturally under certain edge cases. Fixes part of bug
2759 23662; bugfix on 0.3.2.1-alpha.
2761 o Minor bugfixes (tests):
2762 - Fix a memory leak in one of the bridge-distribution test cases.
2763 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
2764 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
2765 to correctly handle cases where a caller gives it an RSA key of
2766 under 160 bits. (This is not actually a bug in Tor itself, but
2767 rather in our fuzzing code.) Fixes bug 24247; bugfix on
2768 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
2771 - Add notes in man page regarding OS support for the various
2772 scheduler types. Attempt to use less jargon in the scheduler
2773 section. Closes ticket 24254.
2776 Changes in version 0.3.2.4-alpha - 2017-11-08
2777 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
2778 It fixes several stability and reliability bugs, especially including
2779 a major reliability issue that has been plaguing fast exit relays in
2782 o Major bugfixes (exit relays, DNS):
2783 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2784 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2785 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2786 identifying and finding a workaround to this bug and to Moritz,
2787 Arthur Edelstein, and Roger for helping to track it down and
2790 o Major bugfixes (scheduler, channel):
2791 - Stop processing scheduled channels if they closed while flushing
2792 cells. This can happen if the write on the connection fails
2793 leading to the channel being closed while in the scheduler loop.
2794 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
2796 o Minor features (logging, scheduler):
2797 - Introduce a SCHED_BUG() function to log extra information about
2798 the scheduler state if we ever catch a bug in the scheduler.
2799 Closes ticket 23753.
2801 o Minor features (removed deprecations):
2802 - The ClientDNSRejectInternalAddresses flag can once again be set in
2803 non-testing Tor networks, so long as they do not use the default
2804 directory authorities. This change also removes the deprecation of
2805 this flag from 0.2.9.2-alpha. Closes ticket 21031.
2807 o Minor features (testing):
2808 - Our fuzzing tests now test the encrypted portions of v3 onion
2809 service descriptors. Implements more of 21509.
2811 o Minor bugfixes (directory client):
2812 - On failure to download directory information, delay retry attempts
2813 by a random amount based on the "decorrelated jitter" algorithm.
2814 Our previous delay algorithm tended to produce extra-long delays
2815 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
2817 o Minor bugfixes (IPv6, v3 single onion services):
2818 - Remove buggy code for IPv6-only v3 single onion services, and
2819 reject attempts to configure them. This release supports IPv4,
2820 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
2821 stack v3 single onion services. Fixes bug 23820; bugfix
2824 o Minor bugfixes (logging, relay):
2825 - Give only a protocol warning when the ed25519 key is not
2826 consistent between the descriptor and microdescriptor of a relay.
2827 This can happen, for instance, if the relay has been flagged
2828 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
2830 o Minor bugfixes (manpage, onion service):
2831 - Document that the HiddenServiceNumIntroductionPoints option is
2832 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
2833 bugfix on 0.3.2.1-alpha.
2835 o Minor bugfixes (memory leaks):
2836 - Fix a minor memory leak at exit in the KIST scheduler. This bug
2837 should have no user-visible impact. Fixes bug 23774; bugfix
2839 - Fix a memory leak when decrypting a badly formatted v3 onion
2840 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
2841 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
2843 o Minor bugfixes (onion services):
2844 - Cache some needed onion service client information instead of
2845 constantly computing it over and over again. Fixes bug 23623;
2846 bugfix on 0.3.2.1-alpha.
2847 - Properly retry HSv3 descriptor fetches when missing required
2848 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
2850 o Minor bugfixes (path selection):
2851 - When selecting relays by bandwidth, avoid a rounding error that
2852 could sometimes cause load to be imbalanced incorrectly.
2853 Previously, we would always round upwards; now, we round towards
2854 the nearest integer. This had the biggest effect when a relay's
2855 weight adjustments should have given it weight 0, but it got
2856 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
2857 - When calculating the fraction of nodes that have descriptors, and
2858 all nodes in the network have zero bandwidths, count the number of
2859 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
2860 - Actually log the total bandwidth in compute_weighted_bandwidths().
2861 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
2863 o Minor bugfixes (relay, crash):
2864 - Avoid a crash when transitioning from client mode to bridge mode.
2865 Previously, we would launch the worker threads whenever our
2866 "public server" mode changed, but not when our "server" mode
2867 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2869 o Minor bugfixes (testing):
2870 - Fix a spurious fuzzing-only use of an uninitialized value. Found
2871 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
2872 - Test that IPv6-only clients can use microdescriptors when running
2873 "make test-network-all". Requires chutney master 61c28b9 or later.
2874 Closes ticket 24109.
2877 Changes in version 0.3.2.3-alpha - 2017-10-27
2878 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
2879 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
2880 directory authority, Bastet.
2882 o Directory authority changes:
2883 - Add "Bastet" as a ninth directory authority to the default list.
2884 Closes ticket 23910.
2885 - The directory authority "Longclaw" has changed its IP address.
2886 Closes ticket 23592.
2888 o Minor features (bridge):
2889 - Bridge relays can now set the BridgeDistribution config option to
2890 add a "bridge-distribution-request" line to their bridge
2891 descriptor, which tells BridgeDB how they'd like their bridge
2892 address to be given out. (Note that as of Oct 2017, BridgeDB does
2893 not yet implement this feature.) As a side benefit, this feature
2894 provides a way to distinguish bridge descriptors from non-bridge
2895 descriptors. Implements tickets 18329.
2897 o Minor features (client, entry guards):
2898 - Improve log messages when missing descriptors for primary guards.
2899 Resolves ticket 23670.
2901 o Minor features (geoip):
2902 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
2905 o Minor bugfixes (bridge):
2906 - Overwrite the bridge address earlier in the process of retrieving
2907 its descriptor, to make sure we reach it on the configured
2908 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
2910 o Minor bugfixes (documentation):
2911 - Document better how to read gcov, and what our gcov postprocessing
2912 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
2914 o Minor bugfixes (entry guards):
2915 - Tor now updates its guard state when it reads a consensus
2916 regardless of whether it's missing descriptors. That makes tor use
2917 its primary guards to fetch descriptors in some edge cases where
2918 it would previously have used fallback directories. Fixes bug
2919 23862; bugfix on 0.3.0.1-alpha.
2921 o Minor bugfixes (hidden service client):
2922 - When handling multiple SOCKS request for the same .onion address,
2923 only fetch the service descriptor once.
2924 - When a descriptor fetch fails with a non-recoverable error, close
2925 all pending SOCKS requests for that .onion. Fixes bug 23653;
2926 bugfix on 0.3.2.1-alpha.
2928 o Minor bugfixes (hidden service):
2929 - Always regenerate missing hidden service public key files. Prior
2930 to this, if the public key was deleted from disk, it wouldn't get
2931 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
2933 - Make sure that we have a usable ed25519 key when the intro point
2934 relay supports ed25519 link authentication. Fixes bug 24002;
2935 bugfix on 0.3.2.1-alpha.
2937 o Minor bugfixes (hidden service, v2):
2938 - When reloading configured hidden services, copy all information
2939 from the old service object. Previously, some data was omitted,
2940 causing delays in descriptor upload, and other bugs. Fixes bug
2941 23790; bugfix on 0.2.1.9-alpha.
2943 o Minor bugfixes (memory safety, defensive programming):
2944 - Clear the target address when node_get_prim_orport() returns
2945 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
2947 o Minor bugfixes (relay):
2948 - Avoid a BUG warning when receiving a dubious CREATE cell while an
2949 option transition is in progress. Fixes bug 23952; bugfix
2952 o Minor bugfixes (testing):
2953 - Adjust the GitLab CI configuration to more closely match that of
2954 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
2955 - Prevent scripts/test/coverage from attempting to move gcov output
2956 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
2957 - When running unit tests as root, skip a test that would fail
2958 because it expects a permissions error. This affects some
2959 continuous integration setups. Fixes bug 23758; bugfix
2961 - Stop unconditionally mirroring the tor repository in GitLab CI.
2962 This prevented developers from enabling GitLab CI on master. Fixes
2963 bug 23755; bugfix on 0.3.2.2-alpha.
2964 - Fix the hidden service v3 descriptor decoding fuzzing to use the
2965 latest decoding API correctly. Fixes bug 21509; bugfix
2968 o Minor bugfixes (warnings):
2969 - When we get an HTTP request on a SOCKS port, tell the user about
2970 the new HTTPTunnelPort option. Previously, we would give a "Tor is
2971 not an HTTP Proxy" message, which stopped being true when
2972 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
2976 Changes in version 0.2.5.15 - 2017-10-25
2977 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
2978 series. It also adds a new directory authority, Bastet.
2980 Note: the Tor 0.2.5 series will no longer be supported after 1 May
2981 2018. If you need a release with long-term support, please upgrade to
2982 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2984 o Directory authority changes:
2985 - Add "Bastet" as a ninth directory authority to the default list.
2986 Closes ticket 23910.
2987 - The directory authority "Longclaw" has changed its IP address.
2988 Closes ticket 23592.
2990 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2991 - Avoid an assertion failure bug affecting our implementation of
2992 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2993 handling of "0xx" differs from what we had expected. Fixes bug
2994 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2996 o Minor features (geoip):
2997 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3000 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3001 - Fix a memset() off the end of an array when packing cells. This
3002 bug should be harmless in practice, since the corrupted bytes are
3003 still in the same structure, and are always padding bytes,
3004 ignored, or immediately overwritten, depending on compiler
3005 behavior. Nevertheless, because the memset()'s purpose is to make
3006 sure that any other cell-handling bugs can't expose bytes to the
3007 network, we need to fix it. Fixes bug 22737; bugfix on
3008 0.2.4.11-alpha. Fixes CID 1401591.
3010 o Build features (backport from 0.3.1.5-alpha):
3011 - Tor's repository now includes a Travis Continuous Integration (CI)
3012 configuration file (.travis.yml). This is meant to help new
3013 developers and contributors who fork Tor to a Github repository be
3014 better able to test their changes, and understand what we expect
3015 to pass. To use this new build feature, you must fork Tor to your
3016 Github account, then go into the "Integrations" menu in the
3017 repository settings for your fork and enable Travis, then push
3018 your changes. Closes ticket 22636.
3021 Changes in version 0.2.8.16 - 2017-10-25
3022 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
3023 series, including a bugfix for a crash issue that had affected relays
3024 under memory pressure. It also adds a new directory authority, Bastet.
3026 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
3027 2018. If you need a release with long-term support, please stick with
3028 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3030 o Directory authority changes:
3031 - Add "Bastet" as a ninth directory authority to the default list.
3032 Closes ticket 23910.
3033 - The directory authority "Longclaw" has changed its IP address.
3034 Closes ticket 23592.
3036 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3037 - Fix a timing-based assertion failure that could occur when the
3038 circuit out-of-memory handler freed a connection's output buffer.
3039 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3041 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3042 - Remove longclaw's IPv6 address, as it will soon change. Authority
3043 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3044 3/8 directory authorities with IPv6 addresses, but there are also
3045 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3047 o Minor features (geoip):
3048 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3052 Changes in version 0.2.9.13 - 2017-10-25
3053 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
3054 series, including a bugfix for a crash issue that had affected relays
3055 under memory pressure. It also adds a new directory authority, Bastet.
3057 o Directory authority changes:
3058 - Add "Bastet" as a ninth directory authority to the default list.
3059 Closes ticket 23910.
3060 - The directory authority "Longclaw" has changed its IP address.
3061 Closes ticket 23592.
3063 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3064 - Fix a timing-based assertion failure that could occur when the
3065 circuit out-of-memory handler freed a connection's output buffer.
3066 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3068 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3069 - Remove longclaw's IPv6 address, as it will soon change. Authority
3070 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3071 3/8 directory authorities with IPv6 addresses, but there are also
3072 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3074 o Minor features (geoip):
3075 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3078 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
3079 - When a directory authority rejects a descriptor or extrainfo with
3080 a given digest, mark that digest as undownloadable, so that we do
3081 not attempt to download it again over and over. We previously
3082 tried to avoid downloading such descriptors by other means, but we
3083 didn't notice if we accidentally downloaded one anyway. This
3084 behavior became problematic in 0.2.7.2-alpha, when authorities
3085 began pinning Ed25519 keys. Fixes bug 22349; bugfix
3088 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
3089 - Clear the address when node_get_prim_orport() returns early.
3090 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
3092 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
3093 - When running as a Windows service, set the ID of the main thread
3094 correctly. Failure to do so made us fail to send log messages to
3095 the controller in 0.2.1.16-rc, slowed down controller event
3096 delivery in 0.2.7.3-rc and later, and crash with an assertion
3097 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
3098 Patch and diagnosis from "Vort".
3101 Changes in version 0.3.0.12 - 2017-10-25
3102 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
3103 series, including a bugfix for a crash issue that had affected relays
3104 under memory pressure. It also adds a new directory authority, Bastet.
3106 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
3107 2018. If you need a release with long-term support, please stick with
3108 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3110 o Directory authority changes:
3111 - Add "Bastet" as a ninth directory authority to the default list.
3112 Closes ticket 23910.
3113 - The directory authority "Longclaw" has changed its IP address.
3114 Closes ticket 23592.
3116 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3117 - Fix a timing-based assertion failure that could occur when the
3118 circuit out-of-memory handler freed a connection's output buffer.
3119 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3121 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3122 - Remove longclaw's IPv6 address, as it will soon change. Authority
3123 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3124 3/8 directory authorities with IPv6 addresses, but there are also
3125 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3127 o Minor features (geoip):
3128 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3131 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
3132 - When a directory authority rejects a descriptor or extrainfo with
3133 a given digest, mark that digest as undownloadable, so that we do
3134 not attempt to download it again over and over. We previously
3135 tried to avoid downloading such descriptors by other means, but we
3136 didn't notice if we accidentally downloaded one anyway. This
3137 behavior became problematic in 0.2.7.2-alpha, when authorities
3138 began pinning Ed25519 keys. Fixes bug 22349; bugfix
3141 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
3142 - Avoid a possible double close of a circuit by the intro point on
3143 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
3144 bugfix on 0.3.0.1-alpha.
3146 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
3147 - Clear the address when node_get_prim_orport() returns early.
3148 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
3150 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
3151 - When running as a Windows service, set the ID of the main thread
3152 correctly. Failure to do so made us fail to send log messages to
3153 the controller in 0.2.1.16-rc, slowed down controller event
3154 delivery in 0.2.7.3-rc and later, and crash with an assertion
3155 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
3156 Patch and diagnosis from "Vort".
3159 Changes in version 0.3.1.8 - 2017-10-25
3160 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
3161 It includes several bugfixes, including a bugfix for a crash issue
3162 that had affected relays under memory pressure. It also adds
3163 a new directory authority, Bastet.
3165 o Directory authority changes:
3166 - Add "Bastet" as a ninth directory authority to the default list.
3167 Closes ticket 23910.
3168 - The directory authority "Longclaw" has changed its IP address.
3169 Closes ticket 23592.
3171 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3172 - Fix a timing-based assertion failure that could occur when the
3173 circuit out-of-memory handler freed a connection's output buffer.
3174 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3176 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3177 - Remove longclaw's IPv6 address, as it will soon change. Authority
3178 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3179 3/8 directory authorities with IPv6 addresses, but there are also
3180 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3182 o Minor features (geoip):
3183 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3186 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
3187 - Fix a compilation warning when building with zstd support on
3188 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
3189 and fixed by Andreas Stieger.
3191 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
3192 - Handle a pathological case when decompressing Zstandard data when
3193 the output buffer size is zero. Fixes bug 23551; bugfix
3196 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
3197 - Remove the length limit on HTTP status lines that authorities can
3198 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
3200 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
3201 - Avoid a possible double close of a circuit by the intro point on
3202 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
3203 bugfix on 0.3.0.1-alpha.
3205 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
3206 - Clear the address when node_get_prim_orport() returns early.
3207 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
3209 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
3210 - Fix additional channelpadding unit test failures by using mocked
3211 time instead of actual time for all tests. Fixes bug 23608; bugfix
3215 Changes in version 0.3.2.2-alpha - 2017-09-29
3216 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
3217 release fixes several minor bugs in the new scheduler and next-
3218 generation onion services; both features were newly added in the 0.3.2
3219 series. Other fixes in this alpha include several fixes for non-fatal
3220 tracebacks which would appear in logs.
3222 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
3223 alpha does not contain any substantial new features. Minor features
3224 include better testing and logging.
3226 The following comprises the complete list of changes included
3229 o Major bugfixes (relay, crash, assertion failure):
3230 - Fix a timing-based assertion failure that could occur when the
3231 circuit out-of-memory handler freed a connection's output buffer.
3232 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3234 o Major bugfixes (scheduler):
3235 - If a channel is put into the scheduler's pending list, then it
3236 starts closing, and then if the scheduler runs before it finishes
3237 closing, the scheduler will get stuck trying to flush its cells
3238 while the lower layers refuse to cooperate. Fix that race
3239 condition by giving the scheduler an escape method. Fixes bug
3240 23676; bugfix on 0.3.2.1-alpha.
3242 o Minor features (build, compilation):
3243 - The "check-changes" feature is now part of the "make check" tests;
3244 we'll use it to try to prevent misformed changes files from
3245 accumulating. Closes ticket 23564.
3246 - Tor builds should now fail if there are any mismatches between the
3247 C type representing a configuration variable and the C type the
3248 data-driven parser uses to store a value there. Previously, we
3249 needed to check these by hand, which sometimes led to mistakes.
3250 Closes ticket 23643.
3252 o Minor features (directory authorities):
3253 - Remove longclaw's IPv6 address, as it will soon change. Authority
3254 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3255 3/8 directory authorities with IPv6 addresses, but there are also
3256 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3258 o Minor features (hidden service, circuit, logging):
3259 - Improve logging of many callsite in the circuit subsystem to print
3260 the circuit identifier(s).
3261 - Log when we cleanup an intro point from a service so we know when
3262 and for what reason it happened. Closes ticket 23604.
3264 o Minor features (logging):
3265 - Log more circuit information whenever we are about to try to
3266 package a relay cell on a circuit with a nonexistent n_chan.
3267 Attempt to diagnose ticket 8185.
3268 - Improve info-level log identification of particular circuits, to
3269 help with debugging. Closes ticket 23645.
3271 o Minor features (relay):
3272 - When choosing which circuits can be expired as unused, consider
3273 circuits from clients even if those clients used regular CREATE
3274 cells to make them; and do not consider circuits from relays even
3275 if they were made with CREATE_FAST. Part of ticket 22805.
3277 o Minor features (robustness):
3278 - Change several fatal assertions when flushing buffers into non-
3279 fatal assertions, to prevent any recurrence of 23690.
3281 o Minor features (spec conformance, bridge, diagnostic):
3282 - When handling the USERADDR command on an ExtOrPort, warn when the
3283 transports provides a USERADDR with no port. In a future version,
3284 USERADDR commands of this format may be rejected. Detects problems
3285 related to ticket 23080.
3287 o Minor features (testing):
3288 - Add a unit test to make sure that our own generated platform
3289 string will be accepted by directory authorities. Closes
3292 o Minor bugfixes (bootstrapping):
3293 - When warning about state file clock skew, report the correct
3294 direction for the detected skew. Fixes bug 23606; bugfix
3296 - Avoid an assertion failure when logging a state file clock skew
3297 very early in bootstrapping. Fixes bug 23607; bugfix
3300 o Minor bugfixes (build, compilation):
3301 - Fix a compilation warning when building with zstd support on
3302 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
3303 and fixed by Andreas Stieger.
3304 - When searching for OpenSSL, don't accept any OpenSSL library that
3305 lacks TLSv1_1_method(): Tor doesn't build with those versions.
3306 Additionally, look in /usr/local/opt/openssl, if it's present.
3307 These changes together repair the default build on OSX systems
3308 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
3310 o Minor bugfixes (compression):
3311 - Handle a pathological case when decompressing Zstandard data when
3312 the output buffer size is zero. Fixes bug 23551; bugfix
3315 o Minor bugfixes (documentation):
3316 - Fix manpage to not refer to the obsolete (and misspelled)
3317 UseEntryGuardsAsDirectoryGuards parameter in the description of
3318 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
3320 o Minor bugfixes (hidden service v3):
3321 - Don't log an assertion failure when we can't find the right
3322 information to extend to an introduction point. In rare cases,
3323 this could happen, causing a warning, even though tor would
3324 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
3325 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
3326 much bigger so the rendezvous point can't distinguish which hidden
3327 service protocol is being used. Fixes bug 23420; bugfix
3330 o Minor bugfixes (hidden service, relay):
3331 - Avoid a possible double close of a circuit by the intro point on
3332 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
3333 bugfix on 0.3.0.1-alpha.
3335 o Minor bugfixes (logging, relay shutdown, annoyance):
3336 - When a circuit is marked for close, do not attempt to package any
3337 cells for channels on that circuit. Previously, we would detect
3338 this condition lower in the call stack, when we noticed that the
3339 circuit had no attached channel, and log an annoying message.
3340 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
3342 o Minor bugfixes (scheduler):
3343 - When switching schedulers due to a consensus change, we didn't
3344 give the new scheduler a chance to react to the consensus. Fix
3345 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
3346 - Make the KISTSchedRunInterval option a non negative value. With
3347 this, the way to disable KIST through the consensus is to set it
3348 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
3349 - Only notice log the selected scheduler when we switch scheduler
3350 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
3351 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
3352 by a different tv_usec data type. Fixes bug 23575; bugfix
3354 - Make a hard exit if tor is unable to pick a scheduler which can
3355 happen if the user specifies a scheduler type that is not
3356 supported and not other types in Schedulers. Fixes bug 23581;
3357 bugfix on 0.3.2.1-alpha.
3358 - Properly initialize the scheduler last run time counter so it is
3359 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
3361 o Minor bugfixes (testing):
3362 - Capture and detect several "Result does not fit" warnings in unit
3363 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
3365 - Fix additional channelpadding unit test failures by using mocked
3366 time instead of actual time for all tests. Fixes bug 23608; bugfix
3368 - The removal of some old scheduler options caused some tests to
3369 fail on BSD systems. Assume current behavior is correct and make
3370 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
3372 o Code simplification and refactoring:
3373 - Remove various ways of testing circuits and connections for
3374 "clientness"; instead, favor channel_is_client(). Part of
3377 o Deprecated features:
3378 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
3379 now deprecated; they do not apply to relays, and they have had no
3380 effect on clients since 0.2.8.x. Closes ticket 19704.
3383 - HiddenServiceVersion man page entry wasn't mentioning the now
3384 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
3385 - Clarify that the Address option is entirely about setting an
3386 advertised IPv4 address. Closes ticket 18891.
3387 - Clarify the manpage's use of the term "address" to clarify what
3388 kind of address is intended. Closes ticket 21405.
3389 - Document that onion service subdomains are allowed, and ignored.
3390 Closes ticket 18736.
3393 Changes in version 0.3.2.1-alpha - 2017-09-18
3394 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
3395 includes support for our next-generation ("v3") onion service
3396 protocol, and adds a new circuit scheduler for more responsive
3397 forwarding decisions from relays. There are also numerous other small
3398 features and bugfixes here.
3400 Below are the changes since Tor 0.3.1.7.
3402 o Major feature (scheduler, channel):
3403 - Tor now uses new schedulers to decide which circuits should
3404 deliver cells first, in order to improve congestion at relays. The
3405 first type is called "KIST" ("Kernel Informed Socket Transport"),
3406 and is only available on Linux-like systems: it uses feedback from
3407 the kernel to prevent the kernel's TCP buffers from growing too
3408 full. The second new scheduler type is called "KISTLite": it
3409 behaves the same as KIST, but runs on systems without kernel
3410 support for inspecting TCP implementation details. The old
3411 scheduler is still available, under the name "Vanilla". To change
3412 the default scheduler preference order, use the new "Schedulers"
3413 option. (The default preference order is "KIST,KISTLite,Vanilla".)
3415 Matt Traudt implemented KIST, based on research by Rob Jansen,
3416 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
3417 more information, see the design paper at
3418 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
3419 followup implementation paper at https://arxiv.org/abs/1709.01044.
3420 Closes ticket 12541.
3422 o Major features (next-generation onion services):
3423 - Tor now supports the next-generation onion services protocol for
3424 clients and services! As part of this release, the core of
3425 proposal 224 has been implemented and is available for
3426 experimentation and testing by our users. This newer version of
3427 onion services ("v3") features many improvements over the legacy
3430 a) Better crypto (replaced SHA1/DH/RSA1024
3431 with SHA3/ed25519/curve25519)
3433 b) Improved directory protocol, leaking much less information to
3436 c) Improved directory protocol, with smaller surface for
3439 d) Better onion address security against impersonation.
3441 e) More extensible introduction/rendezvous protocol.
3443 f) A cleaner and more modular codebase.
3445 You can identify a next-generation onion address by its length:
3446 they are 56 characters long, as in
3447 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
3449 In the future, we will release more options and features for v3
3450 onion services, but we first need a testing period, so that the
3451 current codebase matures and becomes more robust. Planned features
3452 include: offline keys, advanced client authorization, improved
3453 guard algorithms, and statistics. For full details, see
3456 Legacy ("v2") onion services will still work for the foreseeable
3457 future, and will remain the default until this new codebase gets
3458 tested and hardened. Service operators who want to experiment with
3459 the new system can use the 'HiddenServiceVersion 3' torrc
3460 directive along with the regular onion service configuration
3461 options. We will publish a blog post about this new feature
3464 o Major bugfixes (usability, control port):
3465 - Report trusted clock skew indications as bootstrap errors, so
3466 controllers can more easily alert users when their clocks are
3467 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
3469 o Minor features (bug detection):
3470 - Log a warning message with a stack trace for any attempt to call
3471 get_options() during option validation. This pattern has caused
3472 subtle bugs in the past. Closes ticket 22281.
3474 o Minor features (client):
3475 - You can now use Tor as a tunneled HTTP proxy: use the new
3476 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
3477 requests. Closes ticket 22407.
3478 - Add an extra check to make sure that we always use the newer guard
3479 selection code for picking our guards. Closes ticket 22779.
3480 - When downloading (micro)descriptors, don't split the list into
3481 multiple requests unless we want at least 32 descriptors.
3482 Previously, we split at 4, not 32, which led to significant
3483 overhead in HTTP request size and degradation in compression
3484 performance. Closes ticket 23220.
3486 o Minor features (command line):
3487 - Add a new commandline option, --key-expiration, which prints when
3488 the current signing key is going to expire. Implements ticket
3489 17639; patch by Isis Lovecruft.
3491 o Minor features (control port):
3492 - If an application tries to use the control port as an HTTP proxy,
3493 respond with a meaningful "This is the Tor control port" message,
3494 and log the event. Closes ticket 1667. Patch from Ravi
3496 - Provide better error message for GETINFO desc/(id|name) when not
3497 fetching router descriptors. Closes ticket 5847. Patch by
3499 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
3500 whether Tor will try to download router descriptors and
3501 microdescriptors respectively. Closes ticket 22684.
3502 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
3503 so controllers can tell whether the geoip databases are loaded.
3504 Closes ticket 23237.
3505 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
3506 events. Closes ticket 19254. Patch by "DonnchaC".
3508 o Minor features (development support):
3509 - Developers can now generate a call-graph for Tor using the
3510 "calltool" python program, which post-processes object dumps. It
3511 should work okay on many Linux and OSX platforms, and might work
3512 elsewhere too. To run it, install calltool from
3513 https://gitweb.torproject.org/user/nickm/calltool.git and run
3514 "make callgraph". Closes ticket 19307.
3516 o Minor features (ed25519):
3517 - Add validation function to checks for torsion components in
3518 ed25519 public keys, used by prop224 client-side code. Closes
3519 ticket 22006. Math help by Ian Goldberg.
3521 o Minor features (exit relay, DNS):
3522 - Improve the clarity and safety of the log message from evdns when
3523 receiving an apparently spoofed DNS reply. Closes ticket 3056.
3525 o Minor features (integration, hardening):
3526 - Add a new NoExec option to prevent Tor from running other
3527 programs. When this option is set to 1, Tor will never try to run
3528 another program, regardless of the settings of
3529 PortForwardingHelper, ClientTransportPlugin, or
3530 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
3531 without restarting Tor. Closes ticket 22976.
3533 o Minor features (logging):
3534 - Improve the warning message for specifying a relay by nickname.
3535 The previous message implied that nickname registration was still
3536 part of the Tor network design, which it isn't. Closes
3538 - If the sandbox filter fails to load, suggest to the user that
3539 their kernel might not support seccomp2. Closes ticket 23090.
3541 o Minor features (portability):
3542 - Check at configure time whether uint8_t is the same type as
3543 unsigned char. Lots of existing code already makes this
3544 assumption, and there could be strict aliasing issues if the
3545 assumption is violated. Closes ticket 22410.
3547 o Minor features (relay, configuration):
3548 - Reject attempts to use relative file paths when RunAsDaemon is
3549 set. Previously, Tor would accept these, but the directory-
3550 changing step of RunAsDaemon would give strange and/or confusing
3551 results. Closes ticket 22731.
3553 o Minor features (startup, safety):
3554 - When configured to write a PID file, Tor now exits if it is unable
3555 to do so. Previously, it would warn and continue. Closes
3558 o Minor features (static analysis):
3559 - The BUG() macro has been changed slightly so that Coverity no
3560 longer complains about dead code if the bug is impossible. Closes
3563 o Minor features (testing):
3564 - The default chutney network tests now include tests for the v3
3565 hidden service design. Make sure you have the latest version of
3566 chutney if you want to run these. Closes ticket 22437.
3567 - Add a unit test to verify that we can parse a hardcoded v2 hidden
3568 service descriptor. Closes ticket 15554.
3570 o Minor bugfixes (certificate handling):
3571 - Fix a time handling bug in Tor certificates set to expire after
3572 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
3573 Coverity as CID 1415728.
3575 o Minor bugfixes (client, usability):
3576 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
3577 SOCKS4a requests that contain IP address strings, even when
3578 SafeSocks in enabled, as this prevents user from connecting to
3579 known IP addresses without relying on DNS for resolving. SafeSocks
3580 still rejects SOCKS connections that connect to IP addresses when
3581 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
3582 bugfix on Tor 0.2.6.2-alpha.
3584 o Minor bugfixes (code correctness):
3585 - Call htons() in extend_cell_format() for encoding a 16-bit value.
3586 Previously we used ntohs(), which happens to behave the same on
3587 all the platforms we support, but which isn't really correct.
3588 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
3589 - For defense-in-depth, make the controller's write_escaped_data()
3590 function robust to extremely long inputs. Fixes bug 19281; bugfix
3591 on 0.1.1.1-alpha. Reported by Guido Vranken.
3593 o Minor bugfixes (compilation):
3594 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
3595 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
3597 o Minor bugfixes (consensus expiry):
3598 - Check for adequate directory information correctly. Previously, Tor
3599 would reconsider whether it had sufficient directory information
3600 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
3602 o Minor bugfixes (directory protocol):
3603 - Directory servers now include a "Date:" http header for response
3604 codes other than 200. Clients starting with a skewed clock and a
3605 recent consensus were getting "304 Not modified" responses from
3606 directory authorities, so without the Date header, the client
3607 would never hear about a wrong clock. Fixes bug 23499; bugfix
3609 - Make clients wait for 6 seconds before trying to download a
3610 consensus from an authority. Fixes bug 17750; bugfix
3613 o Minor bugfixes (DoS-resistance):
3614 - If future code asks if there are any running bridges, without
3615 checking if bridges are enabled, log a BUG warning rather than
3616 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
3618 o Minor bugfixes (format strictness):
3619 - Restrict several data formats to decimal. Previously, the
3620 BuildTimeHistogram entries in the state file, the "bw=" entries in
3621 the bandwidth authority file, and the process IDs passed to the
3622 __OwningControllerProcess option could all be specified in hex or
3623 octal as well as in decimal. This was not an intentional feature.
3624 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
3627 o Minor bugfixes (heartbeat):
3628 - If we fail to write a heartbeat message, schedule a retry for the
3629 minimum heartbeat interval number of seconds in the future. Fixes
3630 bug 19476; bugfix on 0.2.3.1-alpha.
3632 o Minor bugfixes (linux seccomp2 sandbox, logging):
3633 - Fix some messages on unexpected errors from the seccomp2 library.
3634 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
3636 o Minor bugfixes (logging):
3637 - Remove duplicate log messages regarding opening non-local
3638 SocksPorts upon parsing config and opening listeners at startup.
3639 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
3640 - Use a more comprehensible log message when telling the user
3641 they've excluded every running exit node. Fixes bug 7890; bugfix
3643 - When logging the number of descriptors we intend to download per
3644 directory request, do not log a number higher than then the number
3645 of descriptors we're fetching in total. Fixes bug 19648; bugfix
3647 - When warning about a directory owned by the wrong user, log the
3648 actual name of the user owning the directory. Previously, we'd log
3649 the name of the process owner twice. Fixes bug 23487; bugfix
3651 - The tor specification says hop counts are 1-based, so fix two log
3652 messages that mistakenly logged 0-based hop counts. Fixes bug
3653 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
3654 Credit to Xiaofan Li for reporting this issue.
3656 o Minor bugfixes (portability):
3657 - Stop using the PATH_MAX variable, which is not defined on GNU
3658 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
3660 o Minor bugfixes (relay):
3661 - When uploading our descriptor for the first time after startup,
3662 report the reason for uploading as "Tor just started" rather than
3663 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
3664 - Avoid unnecessary calls to directory_fetches_from_authorities() on
3665 relays, to prevent spurious address resolutions and descriptor
3666 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
3667 bugfix on in 0.2.8.1-alpha.
3669 o Minor bugfixes (tests):
3670 - Fix a broken unit test for the OutboundAddress option: the parsing
3671 function was never returning an error on failure. Fixes bug 23366;
3672 bugfix on 0.3.0.3-alpha.
3673 - Fix a signed-integer overflow in the unit tests for
3674 dir/download_status_random_backoff, which was untriggered until we
3675 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
3677 o Minor bugfixes (usability, control port):
3678 - Stop making an unnecessary routerlist check in NETINFO clock skew
3679 detection; this was preventing clients from reporting NETINFO clock
3680 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
3682 o Code simplification and refactoring:
3683 - Extract the code for handling newly-open channels into a separate
3684 function from the general code to handle channel state
3685 transitions. This change simplifies our callgraph, reducing the
3686 size of the largest strongly connected component by roughly a
3687 factor of two. Closes ticket 22608.
3688 - Remove dead code for largely unused statistics on the number of
3689 times we've attempted various public key operations. Fixes bug
3690 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
3691 - Remove several now-obsolete functions for asking about old
3692 variants directory authority status. Closes ticket 22311; patch
3694 - Remove some of the code that once supported "Named" and "Unnamed"
3695 routers. Authorities no longer vote for these flags. Closes
3697 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
3698 and old hidden services, to indicate that they aren't suitable for
3699 new protocols or formats. Closes ticket 23026.
3700 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
3701 22521. Patch from Neel Chauhan.
3702 - Split the enormous circuit_send_next_onion_skin() function into
3703 multiple subfunctions. Closes ticket 22804.
3704 - Split the portions of the buffer.c module that handle particular
3705 protocols into separate modules. Part of ticket 23149.
3706 - Use our test macros more consistently, to produce more useful
3707 error messages when our unit tests fail. Add coccinelle patches to
3708 allow us to re-check for test macro uses. Closes ticket 22497.
3710 o Deprecated features:
3711 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
3712 only applies to direct unencrypted HTTP connections to your
3713 directory server, which your Tor probably isn't using. Closes
3717 - Clarify in the manual that "Sandbox 1" is only supported on Linux
3718 kernels. Closes ticket 22677.
3719 - Document all values of PublishServerDescriptor in the manpage.
3720 Closes ticket 15645.
3721 - Improve the documentation for the directory port part of the
3722 DirAuthority line. Closes ticket 20152.
3723 - Restore documentation for the authorities' "approved-routers"
3724 file. Closes ticket 21148.
3727 - The AllowDotExit option has been removed as unsafe. It has been
3728 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
3729 - The ClientDNSRejectInternalAddresses flag can no longer be set on
3730 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
3731 Closes ticket 21031.
3732 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
3733 nobody was using it any longer. Closes ticket 22377.
3736 Changes in version 0.2.8.15 - 2017-09-18
3737 Tor 0.2.8.15 backports a collection of bugfixes from later
3740 Most significantly, it includes a fix for TROVE-2017-008, a
3741 security bug that affects hidden services running with the
3742 SafeLogging option disabled. For more information, see
3743 https://trac.torproject.org/projects/tor/ticket/23490
3745 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
3746 2018. We suggest that you upgrade to the latest stable release if
3747 possible. If you can't, we recommend that you upgrade at least to
3748 0.2.9, which will be supported until 2020.
3750 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3751 - Avoid an assertion failure bug affecting our implementation of
3752 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3753 handling of "0xx" differs from what we had expected. Fixes bug
3754 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3757 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3760 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3761 - Backport a fix for an "unused variable" warning that appeared
3762 in some versions of mingw. Fixes bug 22838; bugfix on
3765 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3766 - Fix a memset() off the end of an array when packing cells. This
3767 bug should be harmless in practice, since the corrupted bytes are
3768 still in the same structure, and are always padding bytes,
3769 ignored, or immediately overwritten, depending on compiler
3770 behavior. Nevertheless, because the memset()'s purpose is to make
3771 sure that any other cell-handling bugs can't expose bytes to the
3772 network, we need to fix it. Fixes bug 22737; bugfix on
3773 0.2.4.11-alpha. Fixes CID 1401591.
3775 o Build features (backport from 0.3.1.5-alpha):
3776 - Tor's repository now includes a Travis Continuous Integration (CI)
3777 configuration file (.travis.yml). This is meant to help new
3778 developers and contributors who fork Tor to a Github repository be
3779 better able to test their changes, and understand what we expect
3780 to pass. To use this new build feature, you must fork Tor to your
3781 Github account, then go into the "Integrations" menu in the
3782 repository settings for your fork and enable Travis, then push
3783 your changes. Closes ticket 22636.
3786 Changes in version 0.2.9.12 - 2017-09-18
3787 Tor 0.2.9.12 backports a collection of bugfixes from later
3790 Most significantly, it includes a fix for TROVE-2017-008, a
3791 security bug that affects hidden services running with the
3792 SafeLogging option disabled. For more information, see
3793 https://trac.torproject.org/projects/tor/ticket/23490
3795 o Major features (security, backport from 0.3.0.2-alpha):
3796 - Change the algorithm used to decide DNS TTLs on client and server
3797 side, to better resist DNS-based correlation attacks like the
3798 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
3799 Feamster. Now relays only return one of two possible DNS TTL
3800 values, and clients are willing to believe DNS TTL values up to 3
3801 hours long. Closes ticket 19769.
3803 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
3804 - Fix a rare crash when sending a begin cell on a circuit whose
3805 linked directory connection had already been closed. Fixes bug
3806 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
3808 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
3809 - Fix a bug that prevented exit nodes from caching DNS records for
3810 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
3812 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
3813 - Fix a typo that had prevented TPROXY-based transparent proxying
3814 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
3815 Patch from "d4fq0fQAgoJ".
3817 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3818 - Avoid an assertion failure bug affecting our implementation of
3819 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3820 handling of "0xx" differs from what we had expected. Fixes bug
3821 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3823 o Minor features (code style, backport from 0.3.1.3-alpha):
3824 - Add "Falls through" comments to our codebase, in order to silence
3825 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3826 Stieger. Closes ticket 22446.
3828 o Minor features (geoip):
3829 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3832 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
3833 - Roll over monthly accounting at the configured hour and minute,
3834 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
3835 Found by Andrey Karpov with PVS-Studio.
3837 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
3838 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
3839 bugfix on 0.2.8.1-alpha.
3840 - Fix warnings when building with libscrypt and openssl scrypt support
3841 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
3842 - When building with certain versions the mingw C header files, avoid
3843 float-conversion warnings when calling the C functions isfinite(),
3844 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
3846 o Minor bugfixes (compilation, backport from 0.3.1.7):
3847 - Avoid compiler warnings in the unit tests for running tor_sscanf()
3848 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3850 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3851 - Backport a fix for an "unused variable" warning that appeared
3852 in some versions of mingw. Fixes bug 22838; bugfix on
3855 o Minor bugfixes (controller, backport from 0.3.1.7):
3856 - Do not crash when receiving a HSPOST command with an empty body.
3857 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3858 - Do not crash when receiving a POSTDESCRIPTOR command with an
3859 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3861 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
3862 - Avoid Coverity build warnings related to our BUG() macro. By
3863 default, Coverity treats BUG() as the Linux kernel does: an
3864 instant abort(). We need to override that so our BUG() macro
3865 doesn't prevent Coverity from analyzing functions that use it.
3866 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
3868 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3869 - Fix a memset() off the end of an array when packing cells. This
3870 bug should be harmless in practice, since the corrupted bytes are
3871 still in the same structure, and are always padding bytes,
3872 ignored, or immediately overwritten, depending on compiler
3873 behavior. Nevertheless, because the memset()'s purpose is to make
3874 sure that any other cell-handling bugs can't expose bytes to the
3875 network, we need to fix it. Fixes bug 22737; bugfix on
3876 0.2.4.11-alpha. Fixes CID 1401591.
3878 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
3879 - When setting the maximum number of connections allowed by the OS,
3880 always allow some extra file descriptors for other files. Fixes
3881 bug 22797; bugfix on 0.2.0.10-alpha.
3883 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
3884 - Avoid a sandbox failure when trying to re-bind to a socket and
3885 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
3887 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
3888 - Permit the fchmod system call, to avoid crashing on startup when
3889 starting with the seccomp2 sandbox and an unexpected set of
3890 permissions on the data directory or its contents. Fixes bug
3891 22516; bugfix on 0.2.5.4-alpha.
3893 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
3894 - Avoid a double-marked-circuit warning that could happen when we
3895 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
3898 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
3899 - Reject version numbers with non-numeric prefixes (such as +, -, or
3900 whitespace). Disallowing whitespace prevents differential version
3901 parsing between POSIX-based and Windows platforms. Fixes bug 21507
3902 and part of 21508; bugfix on 0.0.8pre1.
3904 o Build features (backport from 0.3.1.5-alpha):
3905 - Tor's repository now includes a Travis Continuous Integration (CI)
3906 configuration file (.travis.yml). This is meant to help new
3907 developers and contributors who fork Tor to a Github repository be
3908 better able to test their changes, and understand what we expect
3909 to pass. To use this new build feature, you must fork Tor to your
3910 Github account, then go into the "Integrations" menu in the
3911 repository settings for your fork and enable Travis, then push
3912 your changes. Closes ticket 22636.
3915 Changes in version 0.3.0.11 - 2017-09-18
3916 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
3919 Most significantly, it includes a fix for TROVE-2017-008, a
3920 security bug that affects hidden services running with the
3921 SafeLogging option disabled. For more information, see
3922 https://trac.torproject.org/projects/tor/ticket/23490
3924 o Minor features (code style, backport from 0.3.1.7):
3925 - Add "Falls through" comments to our codebase, in order to silence
3926 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
3927 Stieger. Closes ticket 22446.
3930 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3933 o Minor bugfixes (compilation, backport from 0.3.1.7):
3934 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
3935 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
3937 o Minor bugfixes (controller, backport from 0.3.1.7):
3938 - Do not crash when receiving a HSPOST command with an empty body.
3939 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
3940 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
3941 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
3943 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
3944 - When setting the maximum number of connections allowed by the OS,
3945 always allow some extra file descriptors for other files. Fixes
3946 bug 22797; bugfix on 0.2.0.10-alpha.
3948 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
3949 - Remove a forgotten debugging message when an introduction point
3950 successfully establishes a hidden service prop224 circuit with
3952 - Change three other log_warn() for an introduction point to
3953 protocol warnings, because they can be failure from the network
3954 and are not relevant to the operator. Fixes bug 23078; bugfix on
3955 0.3.0.1-alpha and 0.3.0.2-alpha.
3958 Changes in version 0.3.1.7 - 2017-09-18
3959 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
3961 With the 0.3.1 series, Tor now serves and downloads directory
3962 information in more compact formats, to save on bandwidth overhead. It
3963 also contains a new padding system to resist netflow-based traffic
3964 analysis, and experimental support for building parts of Tor in Rust
3965 (though no parts of Tor are in Rust yet). There are also numerous
3966 small features, bugfixes on earlier release series, and groundwork for
3967 the hidden services revamp of 0.3.2.
3969 This release also includes a fix for TROVE-2017-008, a security bug
3970 that affects hidden services running with the SafeLogging option
3971 disabled. For more information, see
3972 https://trac.torproject.org/projects/tor/ticket/23490
3974 Per our stable release policy, we plan to support each stable release
3975 series for at least the next nine months, or for three months after
3976 the first stable release of the next series: whichever is longer. If
3977 you need a release with long-term support, we recommend that you stay
3978 with the 0.2.9 series.
3980 Below is a list of the changes since 0.3.1.6-rc. For a list of all
3981 changes since 0.3.0, see the ReleaseNotes file.
3983 o Major bugfixes (security, hidden services, loggging):
3984 - Fix a bug where we could log uninitialized stack when a certain
3985 hidden service error occurred while SafeLogging was disabled.
3986 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
3987 TROVE-2017-008 and CVE-2017-0380.
3989 o Minor features (defensive programming):
3990 - Create a pair of consensus parameters, nf_pad_tor2web and
3991 nf_pad_single_onion, to disable netflow padding in the consensus
3992 for non-anonymous connections in case the overhead is high. Closes
3995 o Minor features (diagnostic):
3996 - Add a stack trace to the bug warnings that can be logged when
3997 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
3998 attempt for bug 23105.
4000 o Minor features (geoip):
4001 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
4004 o Minor bugfixes (compilation):
4005 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
4006 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
4008 o Minor bugfixes (controller):
4009 - Do not crash when receiving a HSPOST command with an empty body.
4010 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
4011 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
4012 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
4014 o Minor bugfixes (relay):
4015 - Inform the geoip and rephist modules about all requests, even on
4016 relays that are only fetching microdescriptors. Fixes a bug
4017 related to 21585; bugfix on 0.3.0.1-alpha.
4019 o Minor bugfixes (unit tests):
4020 - Fix a channelpadding unit test failure on slow systems by using
4021 mocked time instead of actual time. Fixes bug 23077; bugfix
4025 Changes in version 0.3.1.6-rc - 2017-09-05
4026 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
4027 release series, including a bug that produced weird behavior on
4028 Windows directory caches.
4030 This is the first release candidate in the Tor 0.3.1 series. If we
4031 find no new bugs or regressions here, the first stable 0.3.1 release
4032 will be nearly identical to it.
4034 o Major bugfixes (windows, directory cache):
4035 - On Windows, do not try to delete cached consensus documents and
4036 diffs before they are unmapped from memory--Windows won't allow
4037 that. Instead, allow the consensus cache directory to grow larger,
4038 to hold files that might need to stay around longer. Fixes bug
4039 22752; bugfix on 0.3.1.1-alpha.
4041 o Minor features (directory authority):
4042 - Improve the message that authorities report to relays that present
4043 RSA/Ed25519 keypairs that conflict with previously pinned keys.
4044 Closes ticket 22348.
4046 o Minor features (geoip):
4047 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
4050 o Minor features (testing):
4051 - Add more tests for compression backend initialization. Closes
4054 o Minor bugfixes (directory cache):
4055 - Fix a memory leak when recovering space in the consensus cache.
4056 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
4058 o Minor bugfixes (hidden service):
4059 - Increase the number of circuits that a service is allowed to
4060 open over a specific period of time. The value was lower than it
4061 should be (8 vs 12) in the normal case of 3 introduction points.
4062 Fixes bug 22159; bugfix on 0.3.0.5-rc.
4063 - Fix a BUG warning during HSv3 descriptor decoding that could be
4064 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
4065 on 0.3.0.1-alpha. Bug found by "haxxpop".
4066 - Rate-limit the log messages if we exceed the maximum number of
4067 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
4069 o Minor bugfixes (logging, relay):
4070 - Remove a forgotten debugging message when an introduction point
4071 successfully establishes a hidden service prop224 circuit with
4073 - Change three other log_warn() for an introduction point to
4074 protocol warnings, because they can be failure from the network
4075 and are not relevant to the operator. Fixes bug 23078; bugfix on
4076 0.3.0.1-alpha and 0.3.0.2-alpha.
4078 o Minor bugfixes (relay):
4079 - When a relay is not running as a directory cache, it will no
4080 longer generate compressed consensuses and consensus diff
4081 information. Previously, this was a waste of disk and CPU. Fixes
4082 bug 23275; bugfix on 0.3.1.1-alpha.
4084 o Minor bugfixes (robustness, error handling):
4085 - Improve our handling of the cases where OpenSSL encounters a
4086 memory error while encoding keys and certificates. We haven't
4087 observed these errors in the wild, but if they do happen, we now
4088 detect and respond better. Fixes bug 19418; bugfix on all versions
4089 of Tor. Reported by Guido Vranken.
4091 o Minor bugfixes (stability):
4092 - Avoid crashing on a double-free when unable to load or process an
4093 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
4094 with the clang static analyzer.
4096 o Minor bugfixes (testing):
4097 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4098 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4099 - Port the hs_ntor handshake test to work correctly with recent
4100 versions of the pysha3 module. Fixes bug 23071; bugfix
4103 o Minor bugfixes (Windows service):
4104 - When running as a Windows service, set the ID of the main thread
4105 correctly. Failure to do so made us fail to send log messages to
4106 the controller in 0.2.1.16-rc, slowed down controller event
4107 delivery in 0.2.7.3-rc and later, and crash with an assertion
4108 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
4109 Patch and diagnosis from "Vort".
4112 Changes in version 0.3.0.10 - 2017-08-02
4113 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
4114 from the current Tor alpha series. OpenBSD users and TPROXY users
4115 should upgrade; others are probably okay sticking with 0.3.0.9.
4117 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
4118 - Tor's repository now includes a Travis Continuous Integration (CI)
4119 configuration file (.travis.yml). This is meant to help new
4120 developers and contributors who fork Tor to a Github repository be
4121 better able to test their changes, and understand what we expect
4122 to pass. To use this new build feature, you must fork Tor to your
4123 Github account, then go into the "Integrations" menu in the
4124 repository settings for your fork and enable Travis, then push
4125 your changes. Closes ticket 22636.
4127 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
4128 - Fix a typo that had prevented TPROXY-based transparent proxying
4129 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
4130 Patch from "d4fq0fQAgoJ".
4132 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
4133 - Avoid an assertion failure bug affecting our implementation of
4134 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
4135 handling of "0xbar" differs from what we had expected. Fixes bug
4136 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
4138 o Minor features (backport from 0.3.1.5-alpha):
4139 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
4142 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
4143 - Roll over monthly accounting at the configured hour and minute,
4144 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
4145 Found by Andrey Karpov with PVS-Studio.
4147 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
4148 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
4149 bugfix on 0.2.8.1-alpha.
4150 - Fix warnings when building with libscrypt and openssl scrypt
4151 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
4152 - When building with certain versions of the mingw C header files,
4153 avoid float-conversion warnings when calling the C functions
4154 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
4157 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
4158 - Backport a fix for an "unused variable" warning that appeared
4159 in some versions of mingw. Fixes bug 22838; bugfix on
4162 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
4163 - Avoid Coverity build warnings related to our BUG() macro. By
4164 default, Coverity treats BUG() as the Linux kernel does: an
4165 instant abort(). We need to override that so our BUG() macro
4166 doesn't prevent Coverity from analyzing functions that use it.
4167 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
4169 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
4170 - When rejecting a router descriptor for running an obsolete version
4171 of Tor without ntor support, warn about the obsolete tor version,
4172 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
4174 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
4175 - Avoid a sandbox failure when trying to re-bind to a socket and
4176 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
4178 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
4179 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
4180 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
4183 Changes in version 0.3.1.5-alpha - 2017-08-01
4184 Tor 0.3.1.5-alpha improves the performance of consensus diff
4185 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
4186 several other bugs. If no serious bugs are found in this version, the
4187 next version will be a release candidate.
4189 This release also marks the end of support for the Tor 0.2.4.x,
4190 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
4191 further bug or security fixes. Anyone still running or distributing
4192 one of those versions should upgrade.
4194 o Major features (build system, continuous integration):
4195 - Tor's repository now includes a Travis Continuous Integration (CI)
4196 configuration file (.travis.yml). This is meant to help new
4197 developers and contributors who fork Tor to a Github repository be
4198 better able to test their changes, and understand what we expect
4199 to pass. To use this new build feature, you must fork Tor to your
4200 Github account, then go into the "Integrations" menu in the
4201 repository settings for your fork and enable Travis, then push
4202 your changes. Closes ticket 22636.
4204 o Major bugfixes (openbsd, denial-of-service):
4205 - Avoid an assertion failure bug affecting our implementation of
4206 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
4207 handling of "0xbar" differs from what we had expected. Fixes bug
4208 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
4210 o Major bugfixes (relay, performance):
4211 - Perform circuit handshake operations at a higher priority than we
4212 use for consensus diff creation and compression. This should
4213 prevent circuits from starving when a relay or bridge receives a
4214 new consensus, especially on lower-powered machines. Fixes bug
4215 22883; bugfix on 0.3.1.1-alpha.
4217 o Minor features (bridge authority):
4218 - Add "fingerprint" lines to the networkstatus-bridges file produced
4219 by bridge authorities. Closes ticket 22207.
4221 o Minor features (directory cache, consensus diff):
4222 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
4223 operators with low-resource environments to adjust the number of
4224 consensuses they'll store and generate diffs from. Most cache
4225 operators should leave it unchanged. Helps to work around
4228 o Minor features (geoip):
4229 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
4232 o Minor features (relay, performance):
4233 - Always start relays with at least two worker threads, to prevent
4234 priority inversion on slow tasks. Part of the fix for bug 22883.
4235 - Allow background work to be queued with different priorities, so
4236 that a big pile of slow low-priority jobs will not starve out
4237 higher priority jobs. This lays the groundwork for a fix for
4240 o Minor bugfixes (build system, rust):
4241 - Fix a problem where Rust toolchains were not being found when
4242 building without --enable-cargo-online-mode, due to setting the
4243 $HOME environment variable instead of $CARGO_HOME. Fixes bug
4244 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
4246 o Minor bugfixes (compatibility, zstd):
4247 - Write zstd epilogues correctly when the epilogue requires
4248 reallocation of the output buffer, even with zstd 1.3.0.
4249 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
4250 22927; bugfix on 0.3.1.1-alpha.
4252 o Minor bugfixes (compilation warnings):
4253 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
4254 22915; bugfix on 0.2.8.1-alpha.
4255 - Fix warnings when building with libscrypt and openssl scrypt
4256 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
4257 - Compile correctly when both openssl 1.1.0 and libscrypt are
4258 detected. Previously this would cause an error. Fixes bug 22892;
4259 bugfix on 0.3.1.1-alpha.
4260 - When building with certain versions of the mingw C header files,
4261 avoid float-conversion warnings when calling the C functions
4262 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
4265 o Minor bugfixes (coverity build support):
4266 - Avoid Coverity build warnings related to our BUG() macro. By
4267 default, Coverity treats BUG() as the Linux kernel does: an
4268 instant abort(). We need to override that so our BUG() macro
4269 doesn't prevent Coverity from analyzing functions that use it.
4270 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
4272 o Minor bugfixes (directory authority):
4273 - When a directory authority rejects a descriptor or extrainfo with
4274 a given digest, mark that digest as undownloadable, so that we do
4275 not attempt to download it again over and over. We previously
4276 tried to avoid downloading such descriptors by other means, but we
4277 didn't notice if we accidentally downloaded one anyway. This
4278 behavior became problematic in 0.2.7.2-alpha, when authorities
4279 began pinning Ed25519 keys. Fixes bug 22349; bugfix
4282 o Minor bugfixes (error reporting, windows):
4283 - When formatting Windows error messages, use the English format to
4284 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
4287 o Minor bugfixes (file limits, osx):
4288 - When setting the maximum number of connections allowed by the OS,
4289 always allow some extra file descriptors for other files. Fixes
4290 bug 22797; bugfix on 0.2.0.10-alpha.
4292 o Minor bugfixes (linux seccomp2 sandbox):
4293 - Avoid a sandbox failure when trying to re-bind to a socket and
4294 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
4296 o Minor bugfixes (memory leaks):
4297 - Fix a small memory leak when validating a configuration that uses
4298 two or more AF_UNIX sockets for the same port type. Fixes bug
4299 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
4301 o Minor bugfixes (unit tests):
4302 - test_consdiff_base64cmp would fail on OS X because while OS X
4303 follows the standard of (less than zero/zero/greater than zero),
4304 it doesn't follow the convention of (-1/0/+1). Make the test
4305 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
4306 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
4307 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
4310 Changes in version 0.3.1.4-alpha - 2017-06-29
4311 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
4312 to use a guard that was in the same network family as a chosen exit
4313 relay. This is a security regression; all clients running earlier
4314 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
4317 This release also fixes several other bugs introduced in 0.3.0.x
4318 and 0.3.1.x, including others that can affect bandwidth usage
4322 - To build with zstd and lzma support, Tor now requires the
4323 pkg-config tool at build time. (This requirement was new in
4324 0.3.1.1-alpha, but was not noted at the time. Noting it here to
4325 close ticket 22623.)
4327 o Major bugfixes (path selection, security):
4328 - When choosing which guard to use for a circuit, avoid the exit's
4329 family along with the exit itself. Previously, the new guard
4330 selection logic avoided the exit, but did not consider its family.
4331 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
4332 006 and CVE-2017-0377.
4334 o Major bugfixes (compression, zstd):
4335 - Correctly detect a full buffer when decompressing a large zstd-
4336 compressed input. Previously, we would sometimes treat a full
4337 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
4339 o Major bugfixes (directory protocol):
4340 - Ensure that we send "304 Not modified" as HTTP status code when a
4341 client is attempting to fetch a consensus or consensus diff, and
4342 the best one we can send them is one they already have. Fixes bug
4343 22702; bugfix on 0.3.1.1-alpha.
4345 o Major bugfixes (entry guards):
4346 - When starting with an old consensus, do not add new entry guards
4347 unless the consensus is "reasonably live" (under 1 day old). Fixes
4348 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
4350 o Minor features (bug mitigation, diagnostics, logging):
4351 - Avoid an assertion failure, and log a better error message, when
4352 unable to remove a file from the consensus cache on Windows.
4353 Attempts to mitigate and diagnose bug 22752.
4355 o Minor features (geoip):
4356 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
4359 o Minor bugfixes (compression):
4360 - When compressing or decompressing a buffer, check for a failure to
4361 create a compression object. Fixes bug 22626; bugfix
4363 - When decompressing a buffer, check for extra data after the end of
4364 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
4365 - When decompressing an object received over an anonymous directory
4366 connection, if we have already decompressed it using an acceptable
4367 compression method, do not reject it for looking like an
4368 unacceptable compression method. Fixes part of bug 22670; bugfix
4370 - When serving directory votes compressed with zlib, do not claim to
4371 have compressed them with zstd. Fixes bug 22669; bugfix
4373 - When spooling compressed data to an output buffer, don't try to
4374 spool more data when there is no more data to spool and we are not
4375 trying to flush the input. Previously, we would sometimes launch
4376 compression requests with nothing to do, which interferes with our
4377 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
4379 o Minor bugfixes (defensive programming):
4380 - Detect and break out of infinite loops in our compression code. We
4381 don't think that any such loops exist now, but it's best to be
4382 safe. Closes ticket 22672.
4383 - Fix a memset() off the end of an array when packing cells. This
4384 bug should be harmless in practice, since the corrupted bytes are
4385 still in the same structure, and are always padding bytes,
4386 ignored, or immediately overwritten, depending on compiler
4387 behavior. Nevertheless, because the memset()'s purpose is to make
4388 sure that any other cell-handling bugs can't expose bytes to the
4389 network, we need to fix it. Fixes bug 22737; bugfix on
4390 0.2.4.11-alpha. Fixes CID 1401591.
4392 o Minor bugfixes (linux seccomp2 sandbox):
4393 - Permit the fchmod system call, to avoid crashing on startup when
4394 starting with the seccomp2 sandbox and an unexpected set of
4395 permissions on the data directory or its contents. Fixes bug
4396 22516; bugfix on 0.2.5.4-alpha.
4397 - Fix a crash in the LZMA module, when the sandbox was enabled, and
4398 liblzma would allocate more than 16 MB of memory. We solve this by
4399 bumping the mprotect() limit in the sandbox module from 16 MB to
4400 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
4402 o Minor bugfixes (logging):
4403 - When decompressing, do not warn if we fail to decompress using a
4404 compression method that we merely guessed. Fixes part of bug
4405 22670; bugfix on 0.1.1.14-alpha.
4406 - When decompressing, treat mismatch between content-encoding and
4407 actual compression type as a protocol warning. Fixes part of bug
4408 22670; bugfix on 0.1.1.9-alpha.
4409 - Downgrade "assigned_to_cpuworker failed" message to info-level
4410 severity. In every case that can reach it, either a better warning
4411 has already been logged, or no warning is warranted. Fixes bug
4412 22356; bugfix on 0.2.6.3-alpha.
4413 - Demote a warn that was caused by libevent delays to info if
4414 netflow padding is less than 4.5 seconds late, or to notice
4415 if it is more (4.5 seconds is the amount of time that a netflow
4416 record might be emitted after, if we chose the maximum timeout).
4417 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
4419 o Minor bugfixes (process behavior):
4420 - When exiting because of an error, always exit with a nonzero exit
4421 status. Previously, we would fail to report an error in our exit
4422 status in cases related to __OwningControllerProcess failure,
4423 lockfile contention, and Ed25519 key initialization. Fixes bug
4424 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
4425 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
4429 - Add a manpage description for the key-pinning-journal file. Closes
4431 - Correctly note that bandwidth accounting values are stored in the
4432 state file, and the bw_accounting file is now obsolete. Closes
4434 - Document more of the files in the Tor data directory, including
4435 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
4436 approved-routers, sr-random, and diff-cache. Found while fixing
4440 Changes in version 0.3.0.9 - 2017-06-29
4441 Tor 0.3.0.9 fixes a path selection bug that would allow a client
4442 to use a guard that was in the same network family as a chosen exit
4443 relay. This is a security regression; all clients running earlier
4444 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
4447 This release also backports several other bugfixes from the 0.3.1.x
4450 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
4451 - When choosing which guard to use for a circuit, avoid the exit's
4452 family along with the exit itself. Previously, the new guard
4453 selection logic avoided the exit, but did not consider its family.
4454 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
4455 006 and CVE-2017-0377.
4457 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
4458 - Don't block bootstrapping when a primary bridge is offline and we
4459 can't get its descriptor. Fixes bug 22325; fixes one case of bug
4460 21969; bugfix on 0.3.0.3-alpha.
4462 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
4463 - When starting with an old consensus, do not add new entry guards
4464 unless the consensus is "reasonably live" (under 1 day old). Fixes
4465 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
4467 o Minor features (geoip):
4468 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
4471 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
4472 - Reject version numbers with non-numeric prefixes (such as +, -, or
4473 whitespace). Disallowing whitespace prevents differential version
4474 parsing between POSIX-based and Windows platforms. Fixes bug 21507
4475 and part of 21508; bugfix on 0.0.8pre1.
4477 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
4478 - Permit the fchmod system call, to avoid crashing on startup when
4479 starting with the seccomp2 sandbox and an unexpected set of
4480 permissions on the data directory or its contents. Fixes bug
4481 22516; bugfix on 0.2.5.4-alpha.
4483 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
4484 - Fix a memset() off the end of an array when packing cells. This
4485 bug should be harmless in practice, since the corrupted bytes are
4486 still in the same structure, and are always padding bytes,
4487 ignored, or immediately overwritten, depending on compiler
4488 behavior. Nevertheless, because the memset()'s purpose is to make
4489 sure that any other cell-handling bugs can't expose bytes to the
4490 network, we need to fix it. Fixes bug 22737; bugfix on
4491 0.2.4.11-alpha. Fixes CID 1401591.
4494 Changes in version 0.3.1.3-alpha - 2017-06-08
4495 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
4496 remotely crash a hidden service with an assertion failure. Anyone
4497 running a hidden service should upgrade to this version, or to some
4498 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
4500 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
4501 that sometimes made relays unreliable, as well as several other
4502 bugfixes described below.
4504 o Major bugfixes (hidden service, relay, security):
4505 - Fix a remotely triggerable assertion failure when a hidden service
4506 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
4507 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
4508 - Fix a remotely triggerable assertion failure caused by receiving a
4509 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4510 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4513 o Major bugfixes (relay, link handshake):
4514 - When performing the v3 link handshake on a TLS connection, report
4515 that we have the x509 certificate that we actually used on that
4516 connection, even if we have changed certificates since that
4517 connection was first opened. Previously, we would claim to have
4518 used our most recent x509 link certificate, which would sometimes
4519 make the link handshake fail. Fixes one case of bug 22460; bugfix
4522 o Major bugfixes (relays, key management):
4523 - Regenerate link and authentication certificates whenever the key
4524 that signs them changes; also, regenerate link certificates
4525 whenever the signed key changes. Previously, these processes were
4526 only weakly coupled, and we relays could (for minutes to hours)
4527 wind up with an inconsistent set of keys and certificates, which
4528 other relays would not accept. Fixes two cases of bug 22460;
4529 bugfix on 0.3.0.1-alpha.
4530 - When sending an Ed25519 signing->link certificate in a CERTS cell,
4531 send the certificate that matches the x509 certificate that we
4532 used on the TLS connection. Previously, there was a race condition
4533 if the TLS context rotated after we began the TLS handshake but
4534 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
4537 o Major bugfixes (torrc, crash):
4538 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
4539 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
4541 o Minor features (code style):
4542 - Add "Falls through" comments to our codebase, in order to silence
4543 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
4544 Stieger. Closes ticket 22446.
4546 o Minor features (diagnostic):
4547 - Add logging messages to try to diagnose a rare bug that seems to
4548 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
4549 think this is happening because of incorrect system clocks, but
4550 we'd like to know for certain. Diagnostic for bug 22466.
4552 o Minor bugfixes (correctness):
4553 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4554 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4556 o Minor bugfixes (directory protocol):
4557 - Check for libzstd >= 1.1, because older versions lack the
4558 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
4560 o Minor bugfixes (link handshake):
4561 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
4562 months, and regenerate it when it is within one month of expiring.
4563 Previously, we had generated this certificate at startup with a
4564 ten-year lifetime, but that could lead to weird behavior when Tor
4565 was started with a grossly inaccurate clock. Mitigates bug 22466;
4566 mitigation on 0.3.0.1-alpha.
4568 o Minor bugfixes (storage directories):
4569 - Always check for underflows in the cached storage directory usage.
4570 If the usage does underflow, re-calculate it. Also, avoid a
4571 separate underflow when the usage is not known. Fixes bug 22424;
4572 bugfix on 0.3.1.1-alpha.
4574 o Minor bugfixes (unit tests):
4575 - The unit tests now pass on systems where localhost is misconfigured
4576 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
4580 - Clarify the manpage for the (deprecated) torify script. Closes
4583 Changes in version 0.3.0.8 - 2017-06-08
4584 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
4585 remotely crash a hidden service with an assertion failure. Anyone
4586 running a hidden service should upgrade to this version, or to some
4587 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
4589 Tor 0.3.0.8 also includes fixes for several key management bugs
4590 that sometimes made relays unreliable, as well as several other
4591 bugfixes described below.
4593 o Major bugfixes (hidden service, relay, security, backport
4594 from 0.3.1.3-alpha):
4595 - Fix a remotely triggerable assertion failure when a hidden service
4596 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
4597 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
4598 - Fix a remotely triggerable assertion failure caused by receiving a
4599 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4600 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4603 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
4604 - When performing the v3 link handshake on a TLS connection, report
4605 that we have the x509 certificate that we actually used on that
4606 connection, even if we have changed certificates since that
4607 connection was first opened. Previously, we would claim to have
4608 used our most recent x509 link certificate, which would sometimes
4609 make the link handshake fail. Fixes one case of bug 22460; bugfix
4612 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
4613 - Regenerate link and authentication certificates whenever the key
4614 that signs them changes; also, regenerate link certificates
4615 whenever the signed key changes. Previously, these processes were
4616 only weakly coupled, and we relays could (for minutes to hours)
4617 wind up with an inconsistent set of keys and certificates, which
4618 other relays would not accept. Fixes two cases of bug 22460;
4619 bugfix on 0.3.0.1-alpha.
4620 - When sending an Ed25519 signing->link certificate in a CERTS cell,
4621 send the certificate that matches the x509 certificate that we
4622 used on the TLS connection. Previously, there was a race condition
4623 if the TLS context rotated after we began the TLS handshake but
4624 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
4627 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
4628 - Stop rejecting v3 hidden service descriptors because their size
4629 did not match an old padding rule. Fixes bug 22447; bugfix on
4632 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4633 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4634 December 2016 (of which ~126 were still functional) with a list of
4635 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4636 2017. Resolves ticket 21564.
4638 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
4639 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
4640 bug 22252; bugfix on 0.2.9.3-alpha.
4642 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
4643 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4644 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4646 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
4647 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
4648 months, and regenerate it when it is within one month of expiring.
4649 Previously, we had generated this certificate at startup with a
4650 ten-year lifetime, but that could lead to weird behavior when Tor
4651 was started with a grossly inaccurate clock. Mitigates bug 22466;
4652 mitigation on 0.3.0.1-alpha.
4654 o Minor bugfixes (memory leak, directory authority, backport from
4656 - When directory authorities reject a router descriptor due to
4657 keypinning, free the router descriptor rather than leaking the
4658 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4661 Changes in version 0.2.9.11 - 2017-06-08
4662 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
4663 remotely crash a hidden service with an assertion failure. Anyone
4664 running a hidden service should upgrade to this version, or to some
4665 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4666 are not affected by TROVE-2017-004.)
4668 Tor 0.2.9.11 also backports fixes for several key management bugs
4669 that sometimes made relays unreliable, as well as several other
4670 bugfixes described below.
4672 o Major bugfixes (hidden service, relay, security, backport
4673 from 0.3.1.3-alpha):
4674 - Fix a remotely triggerable assertion failure caused by receiving a
4675 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4676 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4679 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
4680 - When performing the v3 link handshake on a TLS connection, report
4681 that we have the x509 certificate that we actually used on that
4682 connection, even if we have changed certificates since that
4683 connection was first opened. Previously, we would claim to have
4684 used our most recent x509 link certificate, which would sometimes
4685 make the link handshake fail. Fixes one case of bug 22460; bugfix
4688 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4689 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4690 December 2016 (of which ~126 were still functional) with a list of
4691 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4692 2017. Resolves ticket 21564.
4694 o Minor features (future-proofing, backport from 0.3.0.7):
4695 - Tor no longer refuses to download microdescriptors or descriptors if
4696 they are listed as "published in the future". This change will
4697 eventually allow us to stop listing meaningful "published" dates
4698 in microdescriptor consensuses, and thereby allow us to reduce the
4699 resources required to download consensus diffs by over 50%.
4700 Implements part of ticket 21642; implements part of proposal 275.
4702 o Minor features (directory authorities, backport from 0.3.0.4-rc)
4703 - Directory authorities now reject relays running versions
4704 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
4705 suffer from bug 20499 and don't keep their consensus cache
4706 up-to-date. Resolves ticket 20509.
4708 o Minor features (geoip):
4709 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4712 o Minor bugfixes (control port, backport from 0.3.0.6):
4713 - The GETINFO extra-info/digest/<digest> command was broken because
4714 of a wrong base16 decode return value check, introduced when
4715 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
4717 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
4718 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4719 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4721 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
4722 - The getpid() system call is now permitted under the Linux seccomp2
4723 sandbox, to avoid crashing with versions of OpenSSL (and other
4724 libraries) that attempt to learn the process's PID by using the
4725 syscall rather than the VDSO code. Fixes bug 21943; bugfix
4728 o Minor bugfixes (memory leak, directory authority, backport
4729 from 0.3.1.2-alpha):
4730 - When directory authorities reject a router descriptor due to
4731 keypinning, free the router descriptor rather than leaking the
4732 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4734 Changes in version 0.2.8.14 - 2017-06-08
4735 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4736 remotely crash a hidden service with an assertion failure. Anyone
4737 running a hidden service should upgrade to this version, or to some
4738 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4739 are not affected by TROVE-2017-004.)
4741 o Major bugfixes (hidden service, relay, security):
4742 - Fix a remotely triggerable assertion failure caused by receiving a
4743 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4744 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4747 o Minor features (geoip):
4748 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4751 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4752 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4753 December 2016 (of which ~126 were still functional) with a list of
4754 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4755 2017. Resolves ticket 21564.
4757 o Minor bugfixes (correctness):
4758 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4759 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4761 Changes in version 0.2.7.8 - 2017-06-08
4762 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4763 remotely crash a hidden service with an assertion failure. Anyone
4764 running a hidden service should upgrade to this version, or to some
4765 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4766 are not affected by TROVE-2017-004.)
4768 o Major bugfixes (hidden service, relay, security):
4769 - Fix a remotely triggerable assertion failure caused by receiving a
4770 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4771 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4774 o Minor features (geoip):
4775 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4778 o Minor bugfixes (correctness):
4779 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4780 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4783 Changes in version 0.2.6.12 - 2017-06-08
4784 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
4785 remotely crash a hidden service with an assertion failure. Anyone
4786 running a hidden service should upgrade to this version, or to some
4787 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4788 are not affected by TROVE-2017-004.)
4790 o Major bugfixes (hidden service, relay, security):
4791 - Fix a remotely triggerable assertion failure caused by receiving a
4792 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4793 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4796 o Minor features (geoip):
4797 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4800 o Minor bugfixes (correctness):
4801 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4802 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4804 Changes in version 0.2.5.14 - 2017-06-08
4805 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
4806 remotely crash a hidden service with an assertion failure. Anyone
4807 running a hidden service should upgrade to this version, or to some
4808 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4809 are not affected by TROVE-2017-004.)
4811 o Major bugfixes (hidden service, relay, security):
4812 - Fix a remotely triggerable assertion failure caused by receiving a
4813 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4814 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4817 o Minor features (geoip):
4818 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4821 o Minor bugfixes (correctness):
4822 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4823 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4825 Changes in version 0.2.4.29 - 2017-06-08
4826 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
4827 remotely crash a hidden service with an assertion failure. Anyone
4828 running a hidden service should upgrade to this version, or to some
4829 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4830 are not affected by TROVE-2017-004.)
4832 o Major bugfixes (hidden service, relay, security):
4833 - Fix a remotely triggerable assertion failure caused by receiving a
4834 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4835 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4838 o Minor features (geoip):
4839 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4842 o Minor bugfixes (correctness):
4843 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4844 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4847 Changes in version 0.3.1.2-alpha - 2017-05-26
4848 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
4849 fixes a few bugs found while testing 0.3.1.1-alpha, including a
4850 memory corruption bug that affected relay stability.
4852 o Major bugfixes (crash, relay):
4853 - Fix a memory-corruption bug in relays that set MyFamily.
4854 Previously, they would double-free MyFamily elements when making
4855 the next descriptor or when changing their configuration. Fixes
4856 bug 22368; bugfix on 0.3.1.1-alpha.
4858 o Minor bugfixes (logging):
4859 - Log a better message when a directory authority replies to an
4860 upload with an unexpected status code. Fixes bug 11121; bugfix
4863 o Minor bugfixes (memory leak, directory authority):
4864 - When directory authorities reject a router descriptor due to
4865 keypinning, free the router descriptor rather than leaking the
4866 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4869 Changes in version 0.3.1.1-alpha - 2017-05-22
4870 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
4871 reduces the bandwidth usage for Tor's directory protocol, adds some
4872 basic padding to resist netflow-based traffic analysis and to serve as
4873 the basis of other padding in the future, and adds rust support to the
4876 It also contains numerous other small features and improvements to
4877 security, correctness, and performance.
4879 Below are the changes since 0.3.0.7.
4881 o Major features (directory protocol):
4882 - Tor relays and authorities can now serve clients an abbreviated
4883 version of the consensus document, containing only the changes
4884 since an older consensus document that the client holds. Clients
4885 now request these documents when available. When both client and
4886 server use this new protocol, they will use far less bandwidth (up
4887 to 94% less) to keep the client's consensus up-to-date. Implements
4888 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
4889 - Tor can now compress directory traffic with lzma or with zstd
4890 compression algorithms, which can deliver better bandwidth
4891 performance. Because lzma is computationally expensive, it's only
4892 used for documents that can be compressed once and served many
4893 times. Support for these algorithms requires that tor is built
4894 with the libzstd and/or liblzma libraries available. Implements
4895 proposal 278; closes ticket 21662.
4896 - Relays now perform the more expensive compression operations, and
4897 consensus diff generation, in worker threads. This separation
4898 avoids delaying the main thread when a new consensus arrives.
4900 o Major features (experimental):
4901 - Tor can now build modules written in Rust. To turn this on, pass
4902 the "--enable-rust" flag to the configure script. It's not time to
4903 get excited yet: currently, there is no actual Rust functionality
4904 beyond some simple glue code, and a notice at startup to tell you
4905 that Rust is running. Still, we hope that programmers and
4906 packagers will try building Tor with Rust support, so that we can
4907 find issues and solve portability problems. Closes ticket 22106.
4909 o Major features (traffic analysis resistance):
4910 - Connections between clients and relays now send a padding cell in
4911 each direction every 1.5 to 9.5 seconds (tunable via consensus
4912 parameters). This padding will not resist specialized
4913 eavesdroppers, but it should be enough to make many ISPs' routine
4914 network flow logging less useful in traffic analysis against
4917 Padding is negotiated using Tor's link protocol, so both relays
4918 and clients must upgrade for this to take effect. Clients may
4919 still send padding despite the relay's version by setting
4920 ConnectionPadding 1 in torrc, and may disable padding by setting
4921 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
4922 users with the torrc option ReducedConnectionPadding. Implements
4923 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
4924 - Relays will publish 24 hour totals of padding and non-padding cell
4925 counts to their extra-info descriptors, unless PaddingStatistics 0
4926 is set in torrc. These 24 hour totals are also rounded to
4929 o Major bugfixes (connection usage):
4930 - We use NETINFO cells to try to determine if both relays involved
4931 in a connection will agree on the canonical status of that
4932 connection. We prefer the connections where this is the case for
4933 extend cells, and try to close connections where relays disagree
4934 on their canonical status early. Also, we now prefer the oldest
4935 valid connection for extend cells. These two changes should reduce
4936 the number of long-term connections that are kept open between
4937 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
4938 - Relays now log hourly statistics (look for
4939 "channel_check_for_duplicates" lines) on the total number of
4940 connections to other relays. If the number of connections per
4941 relay is unexpectedly large, this log message is at notice level.
4942 Otherwise it is at info.
4944 o Major bugfixes (entry guards):
4945 - Don't block bootstrapping when a primary bridge is offline and we
4946 can't get its descriptor. Fixes bug 22325; fixes one case of bug
4947 21969; bugfix on 0.3.0.3-alpha.
4949 o Major bugfixes (linux TPROXY support):
4950 - Fix a typo that had prevented TPROXY-based transparent proxying
4951 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
4952 Patch from "d4fq0fQAgoJ".
4954 o Minor features (security, windows):
4955 - Enable a couple of pieces of Windows hardening: one
4956 (HeapEnableTerminationOnCorruption) that has been on-by-default
4957 since Windows 8, and unavailable before Windows 7; and one
4958 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
4959 affect us, but shouldn't do any harm. Closes ticket 21953.
4961 o Minor features (config options):
4962 - Allow "%include" directives in torrc configuration files. These
4963 directives import the settings from other files, or from all the
4964 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
4965 - Make SAVECONF return an error when overwriting a torrc that has
4966 includes. Using SAVECONF with the FORCE option will allow it to
4967 overwrite torrc even if includes are used. Related to ticket 1922.
4968 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
4969 will work without the FORCE option. Related to ticket 1922.
4971 o Minor features (controller):
4972 - Warn the first time that a controller requests data in the long-
4973 deprecated 'GETINFO network-status' format. Closes ticket 21703.
4975 o Minor features (defaults):
4976 - The default value for UseCreateFast is now 0: clients which
4977 haven't yet received a consensus document will now use a proper
4978 ntor handshake to talk to their directory servers whenever they
4979 can. Closes ticket 21407.
4980 - Onion key rotation and expiry intervals are now defined as a
4981 network consensus parameter, per proposal 274. The default
4982 lifetime of an onion key is increased from 7 to 28 days. Old onion
4983 keys will expire after 7 days by default. This change will make
4984 consensus diffs much smaller, and save significant bandwidth.
4985 Closes ticket 21641.
4987 o Minor features (fallback directory list):
4988 - Update the fallback directory mirror whitelist and blacklist based
4989 on operator emails. Closes task 21121.
4990 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4991 December 2016 (of which ~126 were still functional) with a list of
4992 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4993 2017. Resolves ticket 21564.
4995 o Minor features (hidden services, logging):
4996 - Log a message when a hidden service descriptor has fewer
4997 introduction points than specified in
4998 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
4999 - Log a message when a hidden service reaches its introduction point
5000 circuit limit, and when that limit is reset. Follow up to ticket
5001 21594; closes ticket 21622.
5002 - Warn user if multiple entries in EntryNodes and at least one
5003 HiddenService are used together. Pinning EntryNodes along with a
5004 hidden service can be possibly harmful; for instance see ticket
5005 14917 or 21155. Closes ticket 21155.
5007 o Minor features (linux seccomp2 sandbox):
5008 - We now have a document storage backend compatible with the Linux
5009 seccomp2 sandbox. This backend is used for consensus documents and
5010 diffs between them; in the long term, we'd like to use it for
5011 unparseable directory material too. Closes ticket 21645
5012 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
5013 from 1MB to 16MB. This was necessary with the glibc allocator in
5014 order to allow worker threads to allocate more memory -- which in
5015 turn is necessary because of our new use of worker threads for
5016 compression. Closes ticket 22096.
5018 o Minor features (logging):
5019 - Log files are no longer created world-readable by default.
5020 (Previously, most distributors would store the logs in a non-
5021 world-readable location to prevent inappropriate access. This
5022 change is an extra precaution.) Closes ticket 21729; patch
5025 o Minor features (performance):
5026 - Our Keccak (SHA-3) implementation now accesses memory more
5027 efficiently, especially on little-endian systems. Closes
5029 - Add an O(1) implementation of channel_find_by_global_id(), to
5030 speed some controller functions.
5032 o Minor features (relay, configuration):
5033 - The MyFamily option may now be repeated as many times as desired,
5034 for relays that want to configure large families. Closes ticket
5035 4998; patch by Daniel Pinto.
5037 o Minor features (safety):
5038 - Add an explicit check to extrainfo_parse_entry_from_string() for
5039 NULL inputs. We don't believe this can actually happen, but it may
5040 help silence a warning from the Clang analyzer. Closes
5043 o Minor features (testing):
5044 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
5045 When Tor is compiled with this option, we disable a number of
5046 redundant memory-safety failsafes that are intended to stop bugs
5047 from becoming security issues. This makes it easier to hunt for
5048 bugs that would be security issues without the failsafes turned
5049 on. Closes ticket 21439.
5050 - Add a general event-tracing instrumentation support to Tor. This
5051 subsystem will enable developers and researchers to add fine-
5052 grained instrumentation to their Tor instances, for use when
5053 examining Tor network performance issues. There are no trace
5054 events yet, and event-tracing is off by default unless enabled at
5055 compile time. Implements ticket 13802.
5056 - Improve our version parsing tests: add tests for typical version
5057 components, add tests for invalid versions, including numeric
5058 range and non-numeric prefixes. Unit tests 21278, 21450, and
5059 21507. Partially implements 21470.
5061 o Minor bugfixes (bandwidth accounting):
5062 - Roll over monthly accounting at the configured hour and minute,
5063 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
5064 Found by Andrey Karpov with PVS-Studio.
5066 o Minor bugfixes (code correctness):
5067 - Accurately identify client connections by their lack of peer
5068 authentication. This means that we bail out earlier if asked to
5069 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
5072 o Minor bugfixes (configuration):
5073 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
5074 bug 22252; bugfix on 0.2.9.3-alpha.
5076 o Minor bugfixes (connection lifespan):
5077 - Allow more control over how long TLS connections are kept open:
5078 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
5079 single option called CircuitsAvailableTimeout. Also, allow the
5080 consensus to control the default values for both this preference
5081 and the lifespan of relay-to-relay connections. Fixes bug 17592;
5082 bugfix on 0.2.5.5-alpha.
5083 - Increase the initial circuit build timeout testing frequency, to
5084 help ensure that ReducedConnectionPadding clients finish learning
5085 a timeout before their orconn would expire. The initial testing
5086 rate was set back in the days of TAP and before the Tor Browser
5087 updater, when we had to be much more careful about new clients
5088 making lots of circuits. With this change, a circuit build timeout
5089 is learned in about 15-20 minutes, instead of 100-120 minutes.
5091 o Minor bugfixes (controller):
5092 - GETINFO onions/current and onions/detached no longer respond with
5093 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
5094 - Trigger HS descriptor events on the control port when the client
5095 fails to pick a hidden service directory for a hidden service.
5096 This can happen if all the hidden service directories are in
5097 ExcludeNodes, or they have all been queried within the last 15
5098 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
5100 o Minor bugfixes (directory authority):
5101 - When rejecting a router descriptor for running an obsolete version
5102 of Tor without ntor support, warn about the obsolete tor version,
5103 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
5104 - Prevent the shared randomness subsystem from asserting when
5105 initialized by a bridge authority with an incomplete configuration
5106 file. Fixes bug 21586; bugfix on 0.2.9.8.
5108 o Minor bugfixes (exit-side DNS):
5109 - Fix an untriggerable assertion that checked the output of a
5110 libevent DNS error, so that the assertion actually behaves as
5111 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
5112 Karpov using PVS-Studio.
5114 o Minor bugfixes (fallback directories):
5115 - Make the usage example in updateFallbackDirs.py actually work, and
5116 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
5117 - Decrease the guard flag average required to be a fallback. This
5118 allows us to keep relays that have their guard flag removed when
5119 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
5120 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
5121 bugfix on 0.2.8.1-alpha.
5122 - Make sure fallback directory mirrors have the same address, port,
5123 and relay identity key for at least 30 days before they are
5124 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
5126 o Minor bugfixes (hidden services):
5127 - Stop printing a cryptic warning when a hidden service gets a
5128 request to connect to a virtual port that it hasn't configured.
5129 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
5130 - Simplify hidden service descriptor creation by using an existing
5131 flag to check if an introduction point is established. Fixes bug
5132 21599; bugfix on 0.2.7.2-alpha.
5134 o Minor bugfixes (memory leak):
5135 - Fix a small memory leak at exit from the backtrace handler code.
5136 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
5138 o Minor bugfixes (protocol, logging):
5139 - Downgrade a log statement about unexpected relay cells from "bug"
5140 to "protocol warning", because there is at least one use case
5141 where it can be triggered by a buggy tor implementation. Fixes bug
5142 21293; bugfix on 0.1.1.14-alpha.
5144 o Minor bugfixes (testing):
5145 - Use unbuffered I/O for utility functions around the
5146 process_handle_t type. This fixes unit test failures reported on
5147 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
5148 - Make display of captured unit test log messages consistent. Fixes
5149 bug 21510; bugfix on 0.2.9.3-alpha.
5150 - Make test-network.sh always call chutney's test-network.sh.
5151 Previously, this only worked on systems which had bash installed,
5152 due to some bash-specific code in the script. Fixes bug 19699;
5153 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
5155 o Minor bugfixes (voting consistency):
5156 - Reject version numbers with non-numeric prefixes (such as +, -, or
5157 whitespace). Disallowing whitespace prevents differential version
5158 parsing between POSIX-based and Windows platforms. Fixes bug 21507
5159 and part of 21508; bugfix on 0.0.8pre1.
5161 o Minor bugfixes (windows, relay):
5162 - Resolve "Failure from drain_fd: No error" warnings on Windows
5163 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
5165 o Code simplification and refactoring:
5166 - Break up the 630-line function connection_dir_client_reached_eof()
5167 into a dozen smaller functions. This change should help
5168 maintainability and readability of the client directory code.
5169 - Isolate our use of the openssl headers so that they are only
5170 included from our crypto wrapper modules, and from tests that
5171 examine those modules' internals. Closes ticket 21841.
5172 - Simplify our API to launch directory requests, making it more
5173 extensible and less error-prone. Now it's easier to add extra
5174 headers to directory requests. Closes ticket 21646.
5175 - Our base64 decoding functions no longer overestimate the output
5176 space that they need when parsing unpadded inputs. Closes
5178 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
5179 Resolves ticket 22213.
5180 - The logic that directory caches use to spool request to clients,
5181 serving them one part at a time so as not to allocate too much
5182 memory, has been refactored for consistency. Previously there was
5183 a separate spooling implementation per type of spoolable data. Now
5184 there is one common spooling implementation, with extensible data
5185 types. Closes ticket 21651.
5186 - Tor's compression module now supports multiple backends. Part of
5187 the implementation for proposal 278; closes ticket 21663.
5190 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
5191 Closes ticket 21873.
5192 - Correct documentation about the default DataDirectory value.
5193 Closes ticket 21151.
5194 - Document the default behavior of NumEntryGuards and
5195 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
5197 - Document key=value pluggable transport arguments for Bridge lines
5198 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
5199 - Note that bandwidth-limiting options don't affect TCP headers or
5200 DNS. Closes ticket 17170.
5202 o Removed features (configuration options, all in ticket 22060):
5203 - These configuration options are now marked Obsolete, and no longer
5204 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
5205 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
5206 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
5207 in 0.2.9.2-alpha and have now been removed. The previous default
5208 behavior is now always chosen; the previous (less secure) non-
5209 default behavior is now unavailable.
5210 - CloseHSClientCircuitsImmediatelyOnTimeout and
5211 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
5212 0.2.9.2-alpha and now have been removed. HS circuits never close
5213 on circuit build timeout; they have a longer timeout period.
5214 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
5215 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
5216 (and others) to configure listen-only and advertise-only addresses.
5218 o Removed features (tools):
5219 - We've removed the tor-checkkey tool from src/tools. Long ago, we
5220 used it to help people detect RSA keys that were generated by
5221 versions of Debian affected by CVE-2008-0166. But those keys have
5222 been out of circulation for ages, and this tool is no longer
5223 required. Closes ticket 21842.
5226 Changes in version 0.3.0.7 - 2017-05-15
5227 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
5228 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
5229 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
5230 clients are not affected.
5232 o Major bugfixes (hidden service directory, security):
5233 - Fix an assertion failure in the hidden service directory code, which
5234 could be used by an attacker to remotely cause a Tor relay process to
5235 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
5236 should upgrade. This security issue is tracked as TROVE-2017-002.
5237 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
5240 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
5243 o Minor features (future-proofing):
5244 - Tor no longer refuses to download microdescriptors or descriptors
5245 if they are listed as "published in the future". This change will
5246 eventually allow us to stop listing meaningful "published" dates
5247 in microdescriptor consensuses, and thereby allow us to reduce the
5248 resources required to download consensus diffs by over 50%.
5249 Implements part of ticket 21642; implements part of proposal 275.
5251 o Minor bugfixes (Linux seccomp2 sandbox):
5252 - The getpid() system call is now permitted under the Linux seccomp2
5253 sandbox, to avoid crashing with versions of OpenSSL (and other
5254 libraries) that attempt to learn the process's PID by using the
5255 syscall rather than the VDSO code. Fixes bug 21943; bugfix
5259 Changes in version 0.3.0.6 - 2017-04-26
5260 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
5262 With the 0.3.0 series, clients and relays now use Ed25519 keys to
5263 authenticate their link connections to relays, rather than the old
5264 RSA1024 keys that they used before. (Circuit crypto has been
5265 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
5266 the guard selection and replacement algorithm to behave more robustly
5267 in the presence of unreliable networks, and to resist guard-
5270 This series also includes numerous other small features and bugfixes,
5271 along with more groundwork for the upcoming hidden-services revamp.
5273 Per our stable release policy, we plan to support the Tor 0.3.0
5274 release series for at least the next nine months, or for three months
5275 after the first stable release of the 0.3.1 series: whichever is
5276 longer. If you need a release with long-term support, we recommend
5277 that you stay with the 0.2.9 series.
5279 Below are the changes since 0.3.0.5-rc. For a list of all changes
5280 since 0.2.9, see the ReleaseNotes file.
5282 o Minor features (geoip):
5283 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
5286 o Minor bugfixes (control port):
5287 - The GETINFO extra-info/digest/<digest> command was broken because
5288 of a wrong base16 decode return value check, introduced when
5289 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
5291 o Minor bugfixes (crash prevention):
5292 - Fix a (currently untriggerable, but potentially dangerous) crash
5293 bug when base32-encoding inputs whose sizes are not a multiple of
5294 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
5297 Changes in version 0.3.0.5-rc - 2017-04-05
5298 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
5299 0.3.0 release series.
5301 This is the second release candidate in the Tor 0.3.0 series, and has
5302 much fewer changes than the first. If we find no new bugs or
5303 regressions here, the first stable 0.3.0 release will be nearly
5306 o Major bugfixes (crash, directory connections):
5307 - Fix a rare crash when sending a begin cell on a circuit whose
5308 linked directory connection had already been closed. Fixes bug
5309 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
5311 o Major bugfixes (guard selection):
5312 - Fix a guard selection bug where Tor would refuse to bootstrap in
5313 some cases if the user swapped a bridge for another bridge in
5314 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
5315 Reported by "torvlnt33r".
5317 o Minor features (geoip):
5318 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
5321 o Minor bugfix (compilation):
5322 - Fix a warning when compiling hs_service.c. Previously, it had no
5323 exported symbols when compiled for libor.a, resulting in a
5324 compilation warning from clang. Fixes bug 21825; bugfix
5327 o Minor bugfixes (hidden services):
5328 - Make hidden services check for failed intro point connections,
5329 even when they have exceeded their intro point creation limit.
5330 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
5331 - Make hidden services with 8 to 10 introduction points check for
5332 failed circuits immediately after startup. Previously, they would
5333 wait for 5 minutes before performing their first checks. Fixes bug
5334 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
5336 o Minor bugfixes (memory leaks):
5337 - Fix a memory leak when using GETCONF on a port option. Fixes bug
5338 21682; bugfix on 0.3.0.3-alpha.
5340 o Minor bugfixes (relay):
5341 - Avoid a double-marked-circuit warning that could happen when we
5342 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
5345 o Minor bugfixes (tests):
5346 - Run the entry_guard_parse_from_state_full() test with the time set
5347 to a specific date. (The guard state that this test was parsing
5348 contained guards that had expired since the test was first
5349 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
5352 - Update the description of the directory server options in the
5353 manual page, to clarify that a relay no longer needs to set
5354 DirPort in order to be a directory cache. Closes ticket 21720.
5358 Changes in version 0.2.8.13 - 2017-03-03
5359 Tor 0.2.8.13 backports a security fix from later Tor
5360 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
5361 this release, if for some reason they cannot upgrade to a later
5362 release series, and if they build Tor with the --enable-expensive-hardening
5365 Note that support for Tor 0.2.8.x is ending next year: we will not issue
5366 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
5367 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5369 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5370 - Fix an integer underflow bug when comparing malformed Tor
5371 versions. This bug could crash Tor when built with
5372 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5373 0.2.9.8, which were built with -ftrapv by default. In other cases
5374 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5375 on 0.0.8pre1. Found by OSS-Fuzz.
5377 o Minor features (geoip):
5378 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5382 Changes in version 0.2.7.7 - 2017-03-03
5383 Tor 0.2.7.7 backports a number of security fixes from later Tor
5384 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
5385 this release, if for some reason they cannot upgrade to a later
5388 Note that support for Tor 0.2.7.x is ending this year: we will not issue
5389 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
5390 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5392 o Directory authority changes (backport from 0.2.8.5-rc):
5393 - Urras is no longer a directory authority. Closes ticket 19271.
5395 o Directory authority changes (backport from 0.2.9.2-alpha):
5396 - The "Tonga" bridge authority has been retired; the new bridge
5397 authority is "Bifroest". Closes tickets 19728 and 19690.
5399 o Directory authority key updates (backport from 0.2.8.1-alpha):
5400 - Update the V3 identity key for the dannenberg directory authority:
5401 it was changed on 18 November 2015. Closes task 17906. Patch
5404 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5405 - Fix a bug in parsing that could cause clients to read a single
5406 byte past the end of an allocated region. This bug could be used
5407 to cause hardened clients (built with --enable-expensive-hardening)
5408 to crash if they tried to visit a hostile hidden service. Non-
5409 hardened clients are only affected depending on the details of
5410 their platform's memory allocator. Fixes bug 21018; bugfix on
5411 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5412 2016-12-002 and as CVE-2016-1254.
5414 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5415 - Stop a crash that could occur when a client running with DNSPort
5416 received a query with multiple address types, and the first
5417 address type was not supported. Found and fixed by Scott Dial.
5418 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5419 - Prevent a class of security bugs caused by treating the contents
5420 of a buffer chunk as if they were a NUL-terminated string. At
5421 least one such bug seems to be present in all currently used
5422 versions of Tor, and would allow an attacker to remotely crash
5423 most Tor instances, especially those compiled with extra compiler
5424 hardening. With this defense in place, such bugs can't crash Tor,
5425 though we should still fix them as they occur. Closes ticket
5426 20384 (TROVE-2016-10-001).
5428 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5429 - Avoid a difficult-to-trigger heap corruption attack when extending
5430 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5431 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5432 Reported by Guido Vranken.
5434 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5435 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5436 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5438 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5439 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5440 pointer to the previous (uninitialized) key value. The impact here
5441 should be limited to a difficult-to-trigger crash, if OpenSSL is
5442 running an engine that makes key generation failures possible, or
5443 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5444 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5447 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5448 - Fix an integer underflow bug when comparing malformed Tor
5449 versions. This bug could crash Tor when built with
5450 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5451 0.2.9.8, which were built with -ftrapv by default. In other cases
5452 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5453 on 0.0.8pre1. Found by OSS-Fuzz.
5455 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5456 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5457 zero size. Check size argument to memwipe() for underflow. Fixes
5458 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5461 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5462 - Make Tor survive errors involving connections without a
5463 corresponding event object. Previously we'd fail with an
5464 assertion; now we produce a log message. Related to bug 16248.
5466 o Minor features (geoip):
5467 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5471 Changes in version 0.2.6.11 - 2017-03-03
5472 Tor 0.2.6.11 backports a number of security fixes from later Tor
5473 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
5474 this release, if for some reason they cannot upgrade to a later
5477 Note that support for Tor 0.2.6.x is ending this year: we will not issue
5478 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
5479 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5481 o Directory authority changes (backport from 0.2.8.5-rc):
5482 - Urras is no longer a directory authority. Closes ticket 19271.
5484 o Directory authority changes (backport from 0.2.9.2-alpha):
5485 - The "Tonga" bridge authority has been retired; the new bridge
5486 authority is "Bifroest". Closes tickets 19728 and 19690.
5488 o Directory authority key updates (backport from 0.2.8.1-alpha):
5489 - Update the V3 identity key for the dannenberg directory authority:
5490 it was changed on 18 November 2015. Closes task 17906. Patch
5493 o Major features (security fixes, backport from 0.2.9.4-alpha):
5494 - Prevent a class of security bugs caused by treating the contents
5495 of a buffer chunk as if they were a NUL-terminated string. At
5496 least one such bug seems to be present in all currently used
5497 versions of Tor, and would allow an attacker to remotely crash
5498 most Tor instances, especially those compiled with extra compiler
5499 hardening. With this defense in place, such bugs can't crash Tor,
5500 though we should still fix them as they occur. Closes ticket
5501 20384 (TROVE-2016-10-001).
5503 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5504 - Fix a bug in parsing that could cause clients to read a single
5505 byte past the end of an allocated region. This bug could be used
5506 to cause hardened clients (built with --enable-expensive-hardening)
5507 to crash if they tried to visit a hostile hidden service. Non-
5508 hardened clients are only affected depending on the details of
5509 their platform's memory allocator. Fixes bug 21018; bugfix on
5510 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5511 2016-12-002 and as CVE-2016-1254.
5513 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5514 - Stop a crash that could occur when a client running with DNSPort
5515 received a query with multiple address types, and the first
5516 address type was not supported. Found and fixed by Scott Dial.
5517 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5519 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5520 - Fix an error that could cause us to read 4 bytes before the
5521 beginning of an openssl string. This bug could be used to cause
5522 Tor to crash on systems with unusual malloc implementations, or
5523 systems with unusual hardening installed. Fixes bug 17404; bugfix
5526 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5527 - Avoid a difficult-to-trigger heap corruption attack when extending
5528 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5529 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5530 Reported by Guido Vranken.
5532 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5533 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5534 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5536 o Major bugfixes (guard selection, backport from 0.2.7.6):
5537 - Actually look at the Guard flag when selecting a new directory
5538 guard. When we implemented the directory guard design, we
5539 accidentally started treating all relays as if they have the Guard
5540 flag during guard selection, leading to weaker anonymity and worse
5541 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5544 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5545 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5546 pointer to the previous (uninitialized) key value. The impact here
5547 should be limited to a difficult-to-trigger crash, if OpenSSL is
5548 running an engine that makes key generation failures possible, or
5549 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5550 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5553 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5554 - Fix an integer underflow bug when comparing malformed Tor
5555 versions. This bug could crash Tor when built with
5556 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5557 0.2.9.8, which were built with -ftrapv by default. In other cases
5558 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5559 on 0.0.8pre1. Found by OSS-Fuzz.
5561 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5562 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5563 zero size. Check size argument to memwipe() for underflow. Fixes
5564 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5567 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5568 - Make Tor survive errors involving connections without a
5569 corresponding event object. Previously we'd fail with an
5570 assertion; now we produce a log message. Related to bug 16248.
5572 o Minor features (geoip):
5573 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5576 o Minor bugfixes (compilation, backport from 0.2.7.6):
5577 - Fix a compilation warning with Clang 3.6: Do not check the
5578 presence of an address which can never be NULL. Fixes bug 17781.
5581 Changes in version 0.2.5.13 - 2017-03-03
5582 Tor 0.2.5.13 backports a number of security fixes from later Tor
5583 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
5584 this release, if for some reason they cannot upgrade to a later
5587 Note that support for Tor 0.2.5.x is ending next year: we will not issue
5588 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
5589 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5591 o Directory authority changes (backport from 0.2.8.5-rc):
5592 - Urras is no longer a directory authority. Closes ticket 19271.
5594 o Directory authority changes (backport from 0.2.9.2-alpha):
5595 - The "Tonga" bridge authority has been retired; the new bridge
5596 authority is "Bifroest". Closes tickets 19728 and 19690.
5598 o Directory authority key updates (backport from 0.2.8.1-alpha):
5599 - Update the V3 identity key for the dannenberg directory authority:
5600 it was changed on 18 November 2015. Closes task 17906. Patch
5603 o Major features (security fixes, backport from 0.2.9.4-alpha):
5604 - Prevent a class of security bugs caused by treating the contents
5605 of a buffer chunk as if they were a NUL-terminated string. At
5606 least one such bug seems to be present in all currently used
5607 versions of Tor, and would allow an attacker to remotely crash
5608 most Tor instances, especially those compiled with extra compiler
5609 hardening. With this defense in place, such bugs can't crash Tor,
5610 though we should still fix them as they occur. Closes ticket
5611 20384 (TROVE-2016-10-001).
5613 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5614 - Fix a bug in parsing that could cause clients to read a single
5615 byte past the end of an allocated region. This bug could be used
5616 to cause hardened clients (built with --enable-expensive-hardening)
5617 to crash if they tried to visit a hostile hidden service. Non-
5618 hardened clients are only affected depending on the details of
5619 their platform's memory allocator. Fixes bug 21018; bugfix on
5620 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5621 2016-12-002 and as CVE-2016-1254.
5623 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5624 - Stop a crash that could occur when a client running with DNSPort
5625 received a query with multiple address types, and the first
5626 address type was not supported. Found and fixed by Scott Dial.
5627 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5629 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5630 - Fix an error that could cause us to read 4 bytes before the
5631 beginning of an openssl string. This bug could be used to cause
5632 Tor to crash on systems with unusual malloc implementations, or
5633 systems with unusual hardening installed. Fixes bug 17404; bugfix
5636 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5637 - Avoid a difficult-to-trigger heap corruption attack when extending
5638 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5639 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5640 Reported by Guido Vranken.
5642 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5643 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5644 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5646 o Major bugfixes (guard selection, backport from 0.2.7.6):
5647 - Actually look at the Guard flag when selecting a new directory
5648 guard. When we implemented the directory guard design, we
5649 accidentally started treating all relays as if they have the Guard
5650 flag during guard selection, leading to weaker anonymity and worse
5651 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5654 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5655 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5656 pointer to the previous (uninitialized) key value. The impact here
5657 should be limited to a difficult-to-trigger crash, if OpenSSL is
5658 running an engine that makes key generation failures possible, or
5659 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5660 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5663 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5664 - Fix an integer underflow bug when comparing malformed Tor
5665 versions. This bug could crash Tor when built with
5666 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5667 0.2.9.8, which were built with -ftrapv by default. In other cases
5668 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5669 on 0.0.8pre1. Found by OSS-Fuzz.
5671 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5672 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5673 zero size. Check size argument to memwipe() for underflow. Fixes
5674 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5677 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5678 - Make Tor survive errors involving connections without a
5679 corresponding event object. Previously we'd fail with an
5680 assertion; now we produce a log message. Related to bug 16248.
5682 o Minor features (geoip):
5683 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5686 o Minor bugfixes (compilation, backport from 0.2.7.6):
5687 - Fix a compilation warning with Clang 3.6: Do not check the
5688 presence of an address which can never be NULL. Fixes bug 17781.
5690 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
5691 - Check for failures from crypto_early_init, and refuse to continue.
5692 A previous typo meant that we could keep going with an
5693 uninitialized crypto library, and would have OpenSSL initialize
5694 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
5695 when implementing ticket 4900. Patch by "teor".
5697 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5698 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5699 a client authorized hidden service. Fixes bug 15823; bugfix
5703 Changes in version 0.2.4.28 - 2017-03-03
5704 Tor 0.2.4.28 backports a number of security fixes from later Tor
5705 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
5706 this release, if for some reason they cannot upgrade to a later
5709 Note that support for Tor 0.2.4.x is ending soon: we will not issue
5710 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
5711 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
5713 o Directory authority changes (backport from 0.2.8.5-rc):
5714 - Urras is no longer a directory authority. Closes ticket 19271.
5716 o Directory authority changes (backport from 0.2.9.2-alpha):
5717 - The "Tonga" bridge authority has been retired; the new bridge
5718 authority is "Bifroest". Closes tickets 19728 and 19690.
5720 o Directory authority key updates (backport from 0.2.8.1-alpha):
5721 - Update the V3 identity key for the dannenberg directory authority:
5722 it was changed on 18 November 2015. Closes task 17906. Patch
5725 o Major features (security fixes, backport from 0.2.9.4-alpha):
5726 - Prevent a class of security bugs caused by treating the contents
5727 of a buffer chunk as if they were a NUL-terminated string. At
5728 least one such bug seems to be present in all currently used
5729 versions of Tor, and would allow an attacker to remotely crash
5730 most Tor instances, especially those compiled with extra compiler
5731 hardening. With this defense in place, such bugs can't crash Tor,
5732 though we should still fix them as they occur. Closes ticket
5733 20384 (TROVE-2016-10-001).
5735 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5736 - Fix a bug in parsing that could cause clients to read a single
5737 byte past the end of an allocated region. This bug could be used
5738 to cause hardened clients (built with --enable-expensive-hardening)
5739 to crash if they tried to visit a hostile hidden service. Non-
5740 hardened clients are only affected depending on the details of
5741 their platform's memory allocator. Fixes bug 21018; bugfix on
5742 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5743 2016-12-002 and as CVE-2016-1254.
5745 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5746 - Fix an error that could cause us to read 4 bytes before the
5747 beginning of an openssl string. This bug could be used to cause
5748 Tor to crash on systems with unusual malloc implementations, or
5749 systems with unusual hardening installed. Fixes bug 17404; bugfix
5752 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5753 - Avoid a difficult-to-trigger heap corruption attack when extending
5754 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5755 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5756 Reported by Guido Vranken.
5758 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5759 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5760 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5762 o Major bugfixes (guard selection, backport from 0.2.7.6):
5763 - Actually look at the Guard flag when selecting a new directory
5764 guard. When we implemented the directory guard design, we
5765 accidentally started treating all relays as if they have the Guard
5766 flag during guard selection, leading to weaker anonymity and worse
5767 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5770 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5771 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5772 pointer to the previous (uninitialized) key value. The impact here
5773 should be limited to a difficult-to-trigger crash, if OpenSSL is
5774 running an engine that makes key generation failures possible, or
5775 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5776 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5779 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5780 - Fix an integer underflow bug when comparing malformed Tor
5781 versions. This bug could crash Tor when built with
5782 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5783 0.2.9.8, which were built with -ftrapv by default. In other cases
5784 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5785 on 0.0.8pre1. Found by OSS-Fuzz.
5787 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5788 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5789 zero size. Check size argument to memwipe() for underflow. Fixes
5790 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5793 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5794 - Make Tor survive errors involving connections without a
5795 corresponding event object. Previously we'd fail with an
5796 assertion; now we produce a log message. Related to bug 16248.
5798 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
5799 - Make it harder for attackers to overload hidden services with
5800 introductions, by blocking multiple introduction requests on the
5801 same circuit. Resolves ticket 15515.
5803 o Minor features (geoip):
5804 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5807 o Minor bugfixes (compilation, backport from 0.2.7.6):
5808 - Fix a compilation warning with Clang 3.6: Do not check the
5809 presence of an address which can never be NULL. Fixes bug 17781.
5811 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5812 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5813 a client authorized hidden service. Fixes bug 15823; bugfix
5817 Changes in version 0.3.0.4-rc - 2017-03-01
5818 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
5819 0.3.0 release series, and introduces a few reliability features to
5820 keep them from coming back.
5822 This is the first release candidate in the Tor 0.3.0 series. If we
5823 find no new bugs or regressions here, the first stable 0.3.0 release
5824 will be nearly identical to it.
5826 o Major bugfixes (bridges):
5827 - When the same bridge is configured multiple times with the same
5828 identity, but at different address:port combinations, treat those
5829 bridge instances as separate guards. This fix restores the ability
5830 of clients to configure the same bridge with multiple pluggable
5831 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
5833 o Major bugfixes (hidden service directory v3):
5834 - Stop crashing on a failed v3 hidden service descriptor lookup
5835 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
5837 o Major bugfixes (parsing):
5838 - When parsing a malformed content-length field from an HTTP
5839 message, do not read off the end of the buffer. This bug was a
5840 potential remote denial-of-service attack against Tor clients and
5841 relays. A workaround was released in October 2016, to prevent this
5842 bug from crashing Tor. This is a fix for the underlying issue,
5843 which should no longer matter (if you applied the earlier patch).
5844 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
5845 using AFL (http://lcamtuf.coredump.cx/afl/).
5846 - Fix an integer underflow bug when comparing malformed Tor
5847 versions. This bug could crash Tor when built with
5848 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5849 0.2.9.8, which were built with -ftrapv by default. In other cases
5850 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5851 on 0.0.8pre1. Found by OSS-Fuzz.
5853 o Minor feature (protocol versioning):
5854 - Add new protocol version for proposal 224. HSIntro now advertises
5855 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
5857 o Minor features (directory authorities):
5858 - Directory authorities now reject descriptors that claim to be
5859 malformed versions of Tor. Helps prevent exploitation of
5861 - Reject version numbers with components that exceed INT32_MAX.
5862 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
5863 Fixes bug 21450; bugfix on 0.0.8pre1.
5864 - Directory authorities now reject relays running versions
5865 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
5866 suffer from bug 20499 and don't keep their consensus cache
5867 up-to-date. Resolves ticket 20509.
5869 o Minor features (geoip):
5870 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5873 o Minor features (reliability, crash):
5874 - Try better to detect problems in buffers where they might grow (or
5875 think they have grown) over 2 GB in size. Diagnostic for
5878 o Minor features (testing):
5879 - During 'make test-network-all', if tor logs any warnings, ask
5880 chutney to output them. Requires a recent version of chutney with
5881 the 21572 patch. Implements 21570.
5883 o Minor bugfixes (certificate expiration time):
5884 - Avoid using link certificates that don't become valid till some
5885 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
5887 o Minor bugfixes (code correctness):
5888 - Repair a couple of (unreachable or harmless) cases of the risky
5889 comparison-by-subtraction pattern that caused bug 21278.
5890 - Remove a redundant check for the UseEntryGuards option from the
5891 options_transition_affects_guards() function. Fixes bug 21492;
5892 bugfix on 0.3.0.1-alpha.
5894 o Minor bugfixes (directory mirrors):
5895 - Allow relays to use directory mirrors without a DirPort: these
5896 relays need to be contacted over their ORPorts using a begindir
5897 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
5898 - Clarify the message logged when a remote relay is unexpectedly
5899 missing an ORPort or DirPort: users were confusing this with a
5900 local port. Fixes another case of bug 20711; bugfix
5903 o Minor bugfixes (guards):
5904 - Don't warn about a missing guard state on timeout-measurement
5905 circuits: they aren't supposed to be using guards. Fixes an
5906 instance of bug 21007; bugfix on 0.3.0.1-alpha.
5907 - Silence a BUG() warning when attempting to use a guard whose
5908 descriptor we don't know, and make this scenario less likely to
5909 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
5911 o Minor bugfixes (hidden service):
5912 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
5913 cells. Previously, we were using sizeof() on a pointer, instead of
5914 the real destination buffer. Fortunately, that value was only used
5915 to double-check that there was enough room--which was already
5916 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
5918 o Minor bugfixes (testing):
5919 - Fix Raspbian build issues related to missing socket errno in
5920 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
5922 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
5923 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
5924 - Use bash in src/test/test-network.sh. This ensures we reliably
5925 call chutney's newer tools/test-network.sh when available. Fixes
5926 bug 21562; bugfix on 0.2.9.1-alpha.
5929 - Small fixes to the fuzzing documentation. Closes ticket 21472.
5932 Changes in version 0.2.9.10 - 2017-03-01
5933 Tor 0.2.9.10 backports a security fix from later Tor release. It also
5934 includes fixes for some major issues affecting directory authorities,
5935 LibreSSL compatibility, and IPv6 correctness.
5937 The Tor 0.2.9.x release series is now marked as a long-term-support
5938 series. We intend to backport security fixes to 0.2.9.x until at
5939 least January of 2020.
5941 o Major bugfixes (directory authority, 0.3.0.3-alpha):
5942 - During voting, when marking a relay as a probable sybil, do not
5943 clear its BadExit flag: sybils can still be bad in other ways
5944 too. (We still clear the other flags.) Fixes bug 21108; bugfix
5947 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
5948 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
5949 any IPv6 addresses. Instead, only reject a port over IPv6 if the
5950 exit policy rejects that port on more than an IPv6 /16 of
5951 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
5952 which rejected a relay's own IPv6 address by default. Fixes bug
5953 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
5955 o Major bugfixes (parsing, also in 0.3.0.4-rc):
5956 - Fix an integer underflow bug when comparing malformed Tor
5957 versions. This bug could crash Tor when built with
5958 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5959 0.2.9.8, which were built with -ftrapv by default. In other cases
5960 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5961 on 0.0.8pre1. Found by OSS-Fuzz.
5963 o Minor features (directory authorities, also in 0.3.0.4-rc):
5964 - Directory authorities now reject descriptors that claim to be
5965 malformed versions of Tor. Helps prevent exploitation of
5967 - Reject version numbers with components that exceed INT32_MAX.
5968 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
5969 Fixes bug 21450; bugfix on 0.0.8pre1.
5971 o Minor features (geoip):
5972 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5975 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
5976 - Autoconf now checks to determine if OpenSSL structures are opaque,
5977 instead of explicitly checking for OpenSSL version numbers. Part
5979 - Support building with recent LibreSSL code that uses opaque
5980 structures. Closes ticket 21359.
5982 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
5983 - Repair a couple of (unreachable or harmless) cases of the risky
5984 comparison-by-subtraction pattern that caused bug 21278.
5986 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
5987 - The tor-resolve command line tool now rejects hostnames over 255
5988 characters in length. Previously, it would silently truncate them,
5989 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
5990 Patch by "junglefowl".
5993 Changes in version 0.3.0.3-alpha - 2017-02-03
5994 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
5995 0.3.0.x development series, including some that could cause
5996 authorities to behave badly. There is also a fix for a longstanding
5997 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
5998 includes some smaller features and bugfixes.
6000 The Tor 0.3.0.x release series is now in patch-freeze: no additional
6001 features will be considered for inclusion in 0.3.0.x. We suspect that
6002 some bugs will probably remain, however, and we encourage people to
6005 o Major bugfixes (directory authority):
6006 - During voting, when marking a relay as a probable sybil, do not
6007 clear its BadExit flag: sybils can still be bad in other ways
6008 too. (We still clear the other flags.) Fixes bug 21108; bugfix
6010 - When deciding whether we have just found a router to be reachable,
6011 do not penalize it for not having performed an Ed25519 link
6012 handshake if it does not claim to support an Ed25519 handshake.
6013 Previously, we would treat such relays as non-running. Fixes bug
6014 21107; bugfix on 0.3.0.1-alpha.
6016 o Major bugfixes (entry guards):
6017 - Stop trying to build circuits through entry guards for which we
6018 have no descriptor. Also, stop crashing in the case that we *do*
6019 accidentally try to build a circuit in such a state. Fixes bug
6020 21242; bugfix on 0.3.0.1-alpha.
6022 o Major bugfixes (IPv6 Exits):
6023 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
6024 any IPv6 addresses. Instead, only reject a port over IPv6 if the
6025 exit policy rejects that port on more than an IPv6 /16 of
6026 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
6027 which rejected a relay's own IPv6 address by default. Fixes bug
6028 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
6030 o Minor feature (client):
6031 - Enable IPv6 traffic on the SocksPort by default. To disable this,
6032 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
6034 o Minor feature (fallback scripts):
6035 - Add a check_existing mode to updateFallbackDirs.py, which checks
6036 if fallbacks in the hard-coded list are working. Closes ticket
6037 20174. Patch by haxxpop.
6039 o Minor features (ciphersuite selection):
6040 - Clients now advertise a list of ciphersuites closer to the ones
6041 preferred by Firefox. Closes part of ticket 15426.
6042 - Allow relays to accept a wider range of ciphersuites, including
6043 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
6045 o Minor features (controller, configuration):
6046 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
6047 and so on, now comes with a __*Port variant that will not be saved
6048 to the torrc file by the controller's SAVECONF command. This
6049 change allows TorBrowser to set up a single-use domain socket for
6050 each time it launches Tor. Closes ticket 20956.
6051 - The GETCONF command can now query options that may only be
6052 meaningful in context-sensitive lists. This allows the controller
6053 to query the mixed SocksPort/__SocksPort style options introduced
6054 in feature 20956. Implements ticket 21300.
6056 o Minor features (portability, compilation):
6057 - Autoconf now checks to determine if OpenSSL structures are opaque,
6058 instead of explicitly checking for OpenSSL version numbers. Part
6060 - Support building with recent LibreSSL code that uses opaque
6061 structures. Closes ticket 21359.
6063 o Minor features (relay):
6064 - We now allow separation of exit and relay traffic to different
6065 source IP addresses, using the OutboundBindAddressExit and
6066 OutboundBindAddressOR options respectively. Closes ticket 17975.
6067 Written by Michael Sonntag.
6069 o Minor bugfix (logging):
6070 - Don't recommend the use of Tor2web in non-anonymous mode.
6071 Recommending Tor2web is a bad idea because the client loses all
6072 anonymity. Tor2web should only be used in specific cases by users
6073 who *know* and understand the issues. Fixes bug 21294; bugfix
6076 o Minor bugfixes (client):
6077 - Always recover from failures in extend_info_from_node(), in an
6078 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
6079 bugfix on 0.2.3.1-alpha.
6081 o Minor bugfixes (client, entry guards):
6082 - Fix a bug warning (with backtrace) when we fail a channel that
6083 circuits to fallback directories on it. Fixes bug 21128; bugfix
6085 - Fix a spurious bug warning (with backtrace) when removing an
6086 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
6087 - Fix a bug of the new guard algorithm where tor could stall for up
6088 to 10 minutes before retrying a guard after a long period of no
6089 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
6090 - Do not try to build circuits until we have descriptors for our
6091 primary entry guards. Related to fix for bug 21242.
6093 o Minor bugfixes (configure, autoconf):
6094 - Rename the configure option --enable-expensive-hardening to
6095 --enable-fragile-hardening. Expensive hardening makes the tor
6096 daemon abort when some kinds of issues are detected. Thus, it
6097 makes tor more at risk of remote crashes but safer against RCE or
6098 heartbleed bug category. We now try to explain this issue in a
6099 message from the configure script. Fixes bug 21290; bugfix
6102 o Minor bugfixes (controller):
6103 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
6104 20824; bugfix on 0.3.0.1-alpha.
6106 o Minor bugfixes (hidden service):
6107 - Clean up the code for expiring intro points with no associated
6108 circuits. It was causing, rarely, a service with some expiring
6109 introduction points to not open enough additional introduction
6110 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
6111 - Stop setting the torrc option HiddenServiceStatistics to "0" just
6112 because we're not a bridge or relay. Instead, we preserve whatever
6113 value the user set (or didn't set). Fixes bug 21150; bugfix
6115 - Resolve two possible underflows which could lead to creating and
6116 closing a lot of introduction point circuits in a non-stop loop.
6117 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
6119 o Minor bugfixes (portability):
6120 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
6121 It is supported by OpenBSD itself, and also by most OpenBSD
6122 variants (such as Bitrig). Fixes bug 20980; bugfix
6124 - When mapping a file of length greater than SIZE_MAX, do not
6125 silently truncate its contents. This issue could occur on 32 bit
6126 systems with large file support and files which are larger than 4
6127 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
6129 o Minor bugfixes (tor-resolve):
6130 - The tor-resolve command line tool now rejects hostnames over 255
6131 characters in length. Previously, it would silently truncate them,
6132 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
6133 Patch by "junglefowl".
6135 o Minor bugfixes (Windows services):
6136 - Be sure to initialize the monotonic time subsystem before using
6137 it, even when running as an NT service. Fixes bug 21356; bugfix
6141 Changes in version 0.3.0.2-alpha - 2017-01-23
6142 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
6143 cause relays and clients to crash, even if they were not built with
6144 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
6145 versions, and also affects 0.3.0.1-alpha: all relays running an affected
6146 version should upgrade.
6148 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
6149 time-to-live values, makes directory authorities enforce the 1-to-1
6150 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
6151 client-side onion service reachability bug, does better at selecting
6152 the set of fallback directories, and more.
6154 o Major bugfixes (security, also in 0.2.9.9):
6155 - Downgrade the "-ftrapv" option from "always on" to "only on when
6156 --enable-expensive-hardening is provided." This hardening option, like
6157 others, can turn survivable bugs into crashes--and having it on by
6158 default made a (relatively harmless) integer overflow bug into a
6159 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
6162 o Major features (security):
6163 - Change the algorithm used to decide DNS TTLs on client and server
6164 side, to better resist DNS-based correlation attacks like the
6165 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
6166 Feamster. Now relays only return one of two possible DNS TTL
6167 values, and clients are willing to believe DNS TTL values up to 3
6168 hours long. Closes ticket 19769.
6170 o Major features (directory authority, security):
6171 - The default for AuthDirPinKeys is now 1: directory authorities
6172 will reject relays where the RSA identity key matches a previously
6173 seen value, but the Ed25519 key has changed. Closes ticket 18319.
6175 o Major bugfixes (client, guard, crash):
6176 - In circuit_get_global_origin_list(), return the actual list of
6177 origin circuits. The previous version of this code returned the
6178 list of all the circuits, and could have caused strange bugs,
6179 including possible crashes. Fixes bug 21118; bugfix
6182 o Major bugfixes (client, onion service, also in 0.2.9.9):
6183 - Fix a client-side onion service reachability bug, where multiple
6184 socks requests to an onion service (or a single slow request)
6185 could cause us to mistakenly mark some of the service's
6186 introduction points as failed, and we cache that failure so
6187 eventually we run out and can't reach the service. Also resolves a
6188 mysterious "Remote server sent bogus reason code 65021" log
6189 warning. The bug was introduced in ticket 17218, where we tried to
6190 remember the circuit end reason as a uint16_t, which mangled
6191 negative values. Partially fixes bug 21056 and fixes bug 20307;
6192 bugfix on 0.2.8.1-alpha.
6194 o Major bugfixes (DNS):
6195 - Fix a bug that prevented exit nodes from caching DNS records for
6196 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
6198 o Minor features (controller):
6199 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
6200 shared-random values to the controller. Closes ticket 19925.
6202 o Minor features (entry guards):
6203 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
6204 break regression tests.
6205 - Require UseEntryGuards when UseBridges is set, in order to make
6206 sure bridges aren't bypassed. Resolves ticket 20502.
6208 o Minor features (fallback directories):
6209 - Select 200 fallback directories for each release. Closes
6211 - Allow 3 fallback relays per operator, which is safe now that we
6212 are choosing 200 fallback relays. Closes ticket 20912.
6213 - Exclude relays affected by bug 20499 from the fallback list.
6214 Exclude relays from the fallback list if they are running versions
6215 known to be affected by bug 20499, or if in our tests they deliver
6216 a stale consensus (i.e. one that expired more than 24 hours ago).
6217 Closes ticket 20539.
6218 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
6220 - Require fallback directories to have the same address and port for
6221 7 days (now that we have enough relays with this stability).
6222 Relays whose OnionOO stability timer is reset on restart by bug
6223 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
6224 this issue. Closes ticket 20880; maintains short-term fix
6226 - Require fallbacks to have flags for 90% of the time (weighted
6227 decaying average), rather than 95%. This allows at least 73% of
6228 clients to bootstrap in the first 5 seconds without contacting an
6229 authority. Part of ticket 18828.
6230 - Annotate updateFallbackDirs.py with the bandwidth and consensus
6231 weight for each candidate fallback. Closes ticket 20878.
6232 - Make it easier to change the output sort order of fallbacks.
6233 Closes ticket 20822.
6234 - Display the relay fingerprint when downloading consensuses from
6235 fallbacks. Closes ticket 20908.
6237 o Minor features (geoip, also in 0.2.9.9):
6238 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
6241 o Minor features (next-gen onion service directories):
6242 - Remove the "EnableOnionServicesV3" consensus parameter that we
6243 introduced in 0.3.0.1-alpha: relays are now always willing to act
6244 as v3 onion service directories. Resolves ticket 19899.
6246 o Minor features (linting):
6247 - Enhance the changes file linter to warn on Tor versions that are
6248 prefixed with "tor-". Closes ticket 21096.
6250 o Minor features (logging):
6251 - In several places, describe unset ed25519 keys as "<unset>",
6252 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
6254 o Minor bugfix (control protocol):
6255 - The reply to a "GETINFO config/names" request via the control
6256 protocol now spells the type "Dependent" correctly. This is a
6257 breaking change in the control protocol. (The field seems to be
6258 ignored by the most common known controllers.) Fixes bug 18146;
6259 bugfix on 0.1.1.4-alpha.
6261 o Minor bugfixes (bug resilience):
6262 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
6263 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
6264 Hans Jerry Illikainen.
6266 o Minor bugfixes (build):
6267 - Replace obsolete Autoconf macros with their modern equivalent and
6268 prevent similar issues in the future. Fixes bug 20990; bugfix
6271 o Minor bugfixes (client, guards):
6272 - Fix bug where Tor would think that there are circuits waiting for
6273 better guards even though those circuits have been freed. Fixes
6274 bug 21142; bugfix on 0.3.0.1-alpha.
6276 o Minor bugfixes (config):
6277 - Don't assert on startup when trying to get the options list and
6278 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
6279 options so of course they aren't ready yet. Fixes bug 21062;
6280 bugfix on 0.2.9.3-alpha.
6282 o Minor bugfixes (controller):
6283 - Make the GETINFO interface for inquiring about entry guards
6284 support the new guards backend. Fixes bug 20823; bugfix
6287 o Minor bugfixes (dead code):
6288 - Remove a redundant check for PidFile changes at runtime in
6289 options_transition_allowed(): this check is already performed
6290 regardless of whether the sandbox is active. Fixes bug 21123;
6291 bugfix on 0.2.5.4-alpha.
6293 o Minor bugfixes (documentation):
6294 - Update the tor manual page to document every option that can not
6295 be changed while tor is running. Fixes bug 21122.
6297 o Minor bugfixes (fallback directories):
6298 - Stop failing when a relay has no uptime data in
6299 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
6300 - Avoid checking fallback candidates' DirPorts if they are down in
6301 OnionOO. When a relay operator has multiple relays, this
6302 prioritizes relays that are up over relays that are down. Fixes
6303 bug 20926; bugfix on 0.2.8.3-alpha.
6304 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
6305 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
6307 o Minor bugfixes (guards, bootstrapping):
6308 - When connecting to a directory guard during bootstrap, do not mark
6309 the guard as successful until we receive a good-looking directory
6310 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
6312 o Minor bugfixes (onion services):
6313 - Fix the config reload pruning of old vs new services so it
6314 actually works when both ephemeral and non-ephemeral services are
6315 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
6316 - Allow the number of introduction points to be as low as 0, rather
6317 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
6319 o Minor bugfixes (IPv6):
6320 - Make IPv6-using clients try harder to find an IPv6 directory
6321 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
6322 - When IPv6 addresses have not been downloaded yet (microdesc
6323 consensus documents don't list relay IPv6 addresses), use hard-
6324 coded addresses for authorities, fallbacks, and configured
6325 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
6326 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
6328 o Minor bugfixes (memory leaks):
6329 - Fix a memory leak when configuring hidden services. Fixes bug
6330 20987; bugfix on 0.3.0.1-alpha.
6332 o Minor bugfixes (portability, also in 0.2.9.9):
6333 - Avoid crashing when Tor is built using headers that contain
6334 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
6335 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
6337 - Fix Libevent detection on platforms without Libevent 1 headers
6338 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
6340 o Minor bugfixes (relay):
6341 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
6342 initializing the keys would reset the DataDirectory to 0700
6343 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
6344 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
6346 o Minor bugfixes (testing):
6347 - Remove undefined behavior from the backtrace generator by removing
6348 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
6350 o Minor bugfixes (unit tests):
6351 - Allow the unit tests to pass even when DNS lookups of bogus
6352 addresses do not fail as expected. Fixes bug 20862 and 20863;
6353 bugfix on unit tests introduced in 0.2.8.1-alpha
6354 through 0.2.9.4-alpha.
6356 o Code simplification and refactoring:
6357 - Refactor code to manipulate global_origin_circuit_list into
6358 separate functions. Closes ticket 20921.
6360 o Documentation (formatting):
6361 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
6362 blocks were incorrectly appearing. Closes ticket 20885.
6364 o Documentation (man page):
6365 - Clarify many options in tor.1 and add some min/max values for
6366 HiddenService options. Closes ticket 21058.
6369 Changes in version 0.2.9.9 - 2017-01-23
6370 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
6371 cause relays and clients to crash, even if they were not built with
6372 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
6373 versions, and also affects 0.3.0.1-alpha: all relays running an affected
6374 version should upgrade.
6376 This release also resolves a client-side onion service reachability
6377 bug, and resolves a pair of small portability issues.
6379 o Major bugfixes (security):
6380 - Downgrade the "-ftrapv" option from "always on" to "only on when
6381 --enable-expensive-hardening is provided." This hardening option,
6382 like others, can turn survivable bugs into crashes -- and having
6383 it on by default made a (relatively harmless) integer overflow bug
6384 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
6385 bugfix on 0.2.9.1-alpha.
6387 o Major bugfixes (client, onion service):
6388 - Fix a client-side onion service reachability bug, where multiple
6389 socks requests to an onion service (or a single slow request)
6390 could cause us to mistakenly mark some of the service's
6391 introduction points as failed, and we cache that failure so
6392 eventually we run out and can't reach the service. Also resolves a
6393 mysterious "Remote server sent bogus reason code 65021" log
6394 warning. The bug was introduced in ticket 17218, where we tried to
6395 remember the circuit end reason as a uint16_t, which mangled
6396 negative values. Partially fixes bug 21056 and fixes bug 20307;
6397 bugfix on 0.2.8.1-alpha.
6399 o Minor features (geoip):
6400 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
6403 o Minor bugfixes (portability):
6404 - Avoid crashing when Tor is built using headers that contain
6405 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
6406 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
6408 - Fix Libevent detection on platforms without Libevent 1 headers
6409 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
6412 Changes in version 0.3.0.1-alpha - 2016-12-19
6413 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
6414 series. It strengthens Tor's link and circuit handshakes by
6415 identifying relays by their Ed25519 keys, improves the algorithm that
6416 clients use to choose and maintain their list of guards, and includes
6417 additional backend support for the next-generation hidden service
6418 design. It also contains numerous other small features and
6419 improvements to security, correctness, and performance.
6421 Below are the changes since 0.2.9.8.
6423 o Major features (guard selection algorithm):
6424 - Tor's guard selection algorithm has been redesigned from the
6425 ground up, to better support unreliable networks and restrictive
6426 sets of entry nodes, and to better resist guard-capture attacks by
6427 hostile local networks. Implements proposal 271; closes
6430 o Major features (next-generation hidden services):
6431 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
6432 prop224 aka "Next Generation Hidden Services". Service and clients
6433 don't use this functionality yet. Closes ticket 19043. Based on
6434 initial code by Alec Heifetz.
6435 - Relays now support the HSDir version 3 protocol, so that they can
6436 can store and serve v3 descriptors. This is part of the next-
6437 generation onion service work detailed in proposal 224. Closes
6440 o Major features (protocol, ed25519 identity keys):
6441 - Relays now use Ed25519 to prove their Ed25519 identities and to
6442 one another, and to clients. This algorithm is faster and more
6443 secure than the RSA-based handshake we've been doing until now.
6444 Implements the second big part of proposal 220; Closes
6446 - Clients now support including Ed25519 identity keys in the EXTEND2
6447 cells they generate. By default, this is controlled by a consensus
6448 parameter, currently disabled. You can turn this feature on for
6449 testing by setting ExtendByEd25519ID in your configuration. This
6450 might make your traffic appear different than the traffic
6451 generated by other users, however. Implements part of ticket
6452 15056; part of proposal 220.
6453 - Relays now understand requests to extend to other relays by their
6454 Ed25519 identity keys. When an Ed25519 identity key is included in
6455 an EXTEND2 cell, the relay will only extend the circuit if the
6456 other relay can prove ownership of that identity. Implements part
6457 of ticket 15056; part of proposal 220.
6459 o Major bugfixes (scheduler):
6460 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
6461 caused the channel scheduler to behave more or less randomly,
6462 rather than preferring channels with higher-priority circuits.
6463 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
6465 o Minor features (controller):
6466 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
6467 rather than "unrecognized." Closes ticket 20389; patch from
6470 o Minor features (diagnostic, directory client):
6471 - Warn when we find an unexpected inconsistency in directory
6472 download status objects. Prevents some negative consequences of
6475 o Minor features (directory authority):
6476 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
6477 default) to control whether authorities should try to probe relays
6478 by their Ed25519 link keys. This option will go away in a few
6479 releases--unless we encounter major trouble in our ed25519 link
6480 protocol rollout, in which case it will serve as a safety option.
6482 o Minor features (directory cache):
6483 - Relays and bridges will now refuse to serve the consensus they
6484 have if they know it is too old for a client to use. Closes
6487 o Minor features (ed25519 link handshake):
6488 - Advertise support for the ed25519 link handshake using the
6489 subprotocol-versions mechanism, so that clients can tell which
6490 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
6492 o Minor features (fingerprinting resistance, authentication):
6493 - Extend the length of RSA keys used for TLS link authentication to
6494 2048 bits. (These weren't used for forward secrecy; for forward
6495 secrecy, we used P256.) Closes ticket 13752.
6497 o Minor features (infrastructure):
6498 - Implement smartlist_add_strdup() function. Replaces the use of
6499 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
6501 o Minor bugfixes (client):
6502 - When clients that use bridges start up with a cached consensus on
6503 disk, they were ignoring it and downloading a new one. Now they
6504 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
6506 o Minor bugfixes (configuration):
6507 - Accept non-space whitespace characters after the severity level in
6508 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
6509 - Support "TByte" and "TBytes" units in options given in bytes.
6510 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
6511 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
6513 o Minor bugfixes (consensus weight):
6514 - Add new consensus method that initializes bw weights to 1 instead
6515 of 0. This prevents a zero weight from making it all the way to
6516 the end (happens in small testing networks) and causing an error.
6517 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
6519 o Minor bugfixes (descriptors):
6520 - Correctly recognise downloaded full descriptors as valid, even
6521 when using microdescriptors as circuits. This affects clients with
6522 FetchUselessDescriptors set, and may affect directory authorities.
6523 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
6525 o Minor bugfixes (directory system):
6526 - Download all consensus flavors, descriptors, and authority
6527 certificates when FetchUselessDescriptors is set, regardless of
6528 whether tor is a directory cache or not. Fixes bug 20667; bugfix
6529 on all recent tor versions.
6530 - Bridges and relays now use microdescriptors (like clients do)
6531 rather than old-style router descriptors. Now bridges will blend
6532 in with clients in terms of the circuits they build. Fixes bug
6533 6769; bugfix on 0.2.3.2-alpha.
6535 o Minor bugfixes (ed25519 certificates):
6536 - Correctly interpret ed25519 certificates that would expire some
6537 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
6539 o Minor bugfixes (hidden services):
6540 - Stop ignoring misconfigured hidden services. Instead, refuse to
6541 start tor until the misconfigurations have been corrected. Fixes
6542 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
6545 o Minor bugfixes (memory leak at exit):
6546 - Fix a small harmless memory leak at exit of the previously unused
6547 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
6550 o Minor bugfixes (util):
6551 - When finishing writing a file to disk, if we were about to replace
6552 the file with the temporary file created before and we fail to
6553 replace it, remove the temporary file so it doesn't stay on disk.
6554 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
6556 o Minor bugfixes (Windows):
6557 - Check for getpagesize before using it to mmap files. This fixes
6558 compilation in some MinGW environments. Fixes bug 20530; bugfix on
6559 0.1.2.1-alpha. Reported by "ice".
6561 o Code simplification and refactoring:
6562 - Abolish all global guard context in entrynodes.c; replace with new
6563 guard_selection_t structure as preparation for proposal 271.
6564 Closes ticket 19858.
6565 - Introduce rend_service_is_ephemeral() that tells if given onion
6566 service is ephemeral. Replace unclear NULL-checkings for service
6567 directory with this function. Closes ticket 20526.
6568 - Extract magic numbers in circuituse.c into defined variables.
6569 - Refactor circuit_is_available_for_use to remove unnecessary check.
6570 - Refactor circuit_predict_and_launch_new for readability and
6571 testability. Closes ticket 18873.
6572 - Refactor large if statement in purpose_needs_anonymity to use
6573 switch statement instead. Closes part of ticket 20077.
6574 - Refactor the hashing API to return negative values for errors, as
6575 is done as throughout the codebase. Closes ticket 20717.
6576 - Remove data structures that were used to index or_connection
6577 objects by their RSA identity digests. These structures are fully
6578 redundant with the similar structures used in the
6579 channel abstraction.
6580 - Remove duplicate code in the channel_write_*cell() functions.
6581 Closes ticket 13827; patch from Pingl.
6582 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
6583 use only purpose_needs_anonymity. Closes part of ticket 20077.
6584 - The code to generate and parse EXTEND and EXTEND2 cells has been
6585 replaced with code automatically generated by the
6589 - Include the "TBits" unit in Tor's man page. Fixes part of bug
6590 20622; bugfix on 0.2.5.1-alpha.
6591 - Change '1' to 'weight_scale' in consensus bw weights calculation
6592 comments, as that is reality. Closes ticket 20273. Patch
6594 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
6595 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
6597 - Stop the man page from incorrectly stating that HiddenServiceDir
6598 must already exist. Fixes 20486.
6599 - Clarify that when ClientRejectInternalAddresses is enabled (which
6600 is the default), multicast DNS hostnames for machines on the local
6601 network (of the form *.local) are also rejected. Closes
6605 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
6606 limit for relays running on a single IP applies to authority IP
6607 addresses as well as to non-authority IP addresses. Closes
6609 - The UseDirectoryGuards torrc option no longer exists: all users
6610 that use entry guards will also use directory guards. Related to
6611 proposal 271; implements part of ticket 20831.
6614 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
6615 from "overcaffeinated".
6616 - Perform the coding style checks when running the tests and fail
6617 when coding style violations are found. Closes ticket 5500.
6618 - Add tests for networkstatus_compute_bw_weights_v10.
6619 - Add unit tests circuit_predict_and_launch_new.
6620 - Extract dummy_origin_circuit_new so it can be used by other
6624 Changes in version 0.2.8.12 - 2016-12-19
6625 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
6626 below) where Tor clients could crash when attempting to visit a
6627 hostile hidden service. Clients are recommended to upgrade as packages
6628 become available for their systems.
6630 It also includes an updated list of fallback directories, backported
6633 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
6634 backported to 0.2.8 in the future.
6636 o Major bugfixes (parsing, security, backported from 0.2.9.8):
6637 - Fix a bug in parsing that could cause clients to read a single
6638 byte past the end of an allocated region. This bug could be used
6639 to cause hardened clients (built with --enable-expensive-hardening)
6640 to crash if they tried to visit a hostile hidden service. Non-
6641 hardened clients are only affected depending on the details of
6642 their platform's memory allocator. Fixes bug 21018; bugfix on
6643 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
6644 2016-12-002 and as CVE-2016-1254.
6646 o Minor features (fallback directory list, backported from 0.2.9.8):
6647 - Replace the 81 remaining fallbacks of the 100 originally
6648 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
6649 fallbacks (123 new, 54 existing, 27 removed) generated in December
6650 2016. Resolves ticket 20170.
6652 o Minor features (geoip, backported from 0.2.9.7-rc):
6653 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
6657 Changes in version 0.2.9.8 - 2016-12-19
6658 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
6660 The Tor 0.2.9 series makes mandatory a number of security features
6661 that were formerly optional. It includes support for a new shared-
6662 randomness protocol that will form the basis for next generation
6663 hidden services, includes a single-hop hidden service mode for
6664 optimizing .onion services that don't actually want to be hidden,
6665 tries harder not to overload the directory authorities with excessive
6666 downloads, and supports a better protocol versioning scheme for
6667 improved compatibility with other implementations of the Tor protocol.
6669 And of course, there are numerous other bugfixes and improvements.
6671 This release also includes a fix for a medium-severity issue (bug
6672 21018 below) where Tor clients could crash when attempting to visit a
6673 hostile hidden service. Clients are recommended to upgrade as packages
6674 become available for their systems.
6676 Below are the changes since 0.2.9.7-rc. For a list of all changes
6677 since 0.2.8, see the ReleaseNotes file.
6679 o Major bugfixes (parsing, security):
6680 - Fix a bug in parsing that could cause clients to read a single
6681 byte past the end of an allocated region. This bug could be used
6682 to cause hardened clients (built with --enable-expensive-hardening)
6683 to crash if they tried to visit a hostile hidden service. Non-
6684 hardened clients are only affected depending on the details of
6685 their platform's memory allocator. Fixes bug 21018; bugfix on
6686 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
6687 2016-12-002 and as CVE-2016-1254.
6689 o Minor features (fallback directory list):
6690 - Replace the 81 remaining fallbacks of the 100 originally
6691 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
6692 fallbacks (123 new, 54 existing, 27 removed) generated in December
6693 2016. Resolves ticket 20170.
6696 Changes in version 0.2.9.7-rc - 2016-12-12
6697 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
6698 including a few that had prevented tests from passing on
6701 o Minor features (geoip):
6702 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
6705 o Minor bugfix (build):
6706 - The current Git revision when building from a local repository is
6707 now detected correctly when using git worktrees. Fixes bug 20492;
6708 bugfix on 0.2.3.9-alpha.
6710 o Minor bugfixes (directory authority):
6711 - When computing old Tor protocol line version in protover, we were
6712 looking at 0.2.7.5 twice instead of a specific case for
6713 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
6715 o Minor bugfixes (download scheduling):
6716 - Resolve a "bug" warning when considering a download schedule whose
6717 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
6719 o Minor bugfixes (logging):
6720 - Downgrade a harmless log message about the
6721 pending_entry_connections list from "warn" to "info". Mitigates
6724 o Minor bugfixes (memory leak):
6725 - Fix a small memory leak when receiving AF_UNIX connections on a
6726 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
6727 - When moving a signed descriptor object from a source to an
6728 existing destination, free the allocated memory inside that
6729 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
6731 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
6732 - Fix a memory leak and use-after-free error when removing entries
6733 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
6734 0.2.5.5-alpha. Patch from "cypherpunks".
6736 o Minor bugfixes (portability):
6737 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
6738 Fixes bug 20935; bugfix on 0.2.9.6-rc.
6740 o Minor bugfixes (unit tests):
6741 - Stop expecting NetBSD unit tests to report success for ipfw. Part
6742 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
6743 - Fix tolerances in unit tests for monotonic time comparisons
6744 between nanoseconds and microseconds. Previously, we accepted a 10
6745 us difference only, which is not realistic on every platform's
6746 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
6747 - Remove a double-free in the single onion service unit test. Stop
6748 ignoring a return value. Make future changes less error-prone.
6749 Fixes bug 20864; bugfix on 0.2.9.6-rc.
6752 Changes in version 0.2.8.11 - 2016-12-08
6753 Tor 0.2.8.11 backports fixes for additional portability issues that
6754 could prevent Tor from building correctly on OSX Sierra, or with
6755 OpenSSL 1.1. Affected users should upgrade; others can safely stay
6758 o Minor bugfixes (portability):
6759 - Avoid compilation errors when building on OSX Sierra. Sierra began
6760 to support the getentropy() and clock_gettime() APIs, but created
6761 a few problems in doing so. Tor 0.2.9 has a more thorough set of
6762 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
6763 monotonic time interfaces. Fixes bug 20865. Bugfix
6766 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
6767 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
6768 architectures. Closes ticket 20588.
6771 Changes in version 0.2.8.10 - 2016-12-02
6772 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
6773 unusable after they left standby mode. It also backports fixes for
6774 a few portability issues and a small but problematic memory leak.
6776 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
6777 - When Tor leaves standby because of a new application request, open
6778 circuits as needed to serve that request. Previously, we would
6779 potentially wait a very long time. Fixes part of bug 19969; bugfix
6782 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
6783 - Clients now respond to new application stream requests immediately
6784 when they arrive, rather than waiting up to one second before
6785 starting to handle them. Fixes part of bug 19969; bugfix
6788 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
6789 - Work around a bug in the OSX 10.12 SDK that would prevent us from
6790 successfully targeting earlier versions of OSX. Resolves
6793 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
6794 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
6795 20551; bugfix on 0.2.1.1-alpha.
6797 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
6798 - Work around a memory leak in OpenSSL 1.1 when encoding public
6799 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
6801 o Minor features (geoip):
6802 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
6805 Changes in version 0.2.9.6-rc - 2016-12-02
6806 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
6807 version. We hope that it will be ready to become stable soon, and we
6808 encourage everyone to test this release. If no showstopper bugs are
6809 found here, the next 0.2.9 release will be stable.
6811 o Major bugfixes (relay, resolver, logging):
6812 - For relays that don't know their own address, avoid attempting a
6813 local hostname resolve for each descriptor we download. This
6814 will cut down on the number of "Success: chose address 'x.x.x.x'"
6815 log lines, and also avoid confusing clock jumps if the resolver
6816 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
6818 o Minor bugfixes (client, fascistfirewall):
6819 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
6820 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
6822 o Minor bugfixes (hidden services):
6823 - Stop ignoring the anonymity status of saved keys for hidden
6824 services and single onion services when first starting tor.
6825 Instead, refuse to start tor if any hidden service key has been
6826 used in a different hidden service anonymity mode. Fixes bug
6827 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
6829 o Minor bugfixes (portability):
6830 - Work around a bug in the OSX 10.12 SDK that would prevent us from
6831 successfully targeting earlier versions of OSX. Resolves
6833 - Run correctly when built on Windows build environments that
6834 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
6836 o Minor bugfixes (single onion services, Tor2web):
6837 - Stop complaining about long-term one-hop circuits deliberately
6838 created by single onion services and Tor2web. These log messages
6839 are intended to diagnose issue 8387, which relates to circuits
6840 hanging around forever for no reason. Fixes bug 20613; bugfix on
6841 0.2.9.1-alpha. Reported by "pastly".
6843 o Minor bugfixes (unit tests):
6844 - Stop spurious failures in the local interface address discovery
6845 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
6849 - Correct the minimum bandwidth value in torrc.sample, and queue a
6850 corresponding change for torrc.minimal. Closes ticket 20085.
6853 Changes in version 0.2.9.5-alpha - 2016-11-08
6854 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
6855 version. We believe one or two probably remain, and we encourage
6856 everyone to test this release.
6858 o Major bugfixes (client performance):
6859 - Clients now respond to new application stream requests immediately
6860 when they arrive, rather than waiting up to one second before
6861 starting to handle them. Fixes part of bug 19969; bugfix
6864 o Major bugfixes (client reliability):
6865 - When Tor leaves standby because of a new application request, open
6866 circuits as needed to serve that request. Previously, we would
6867 potentially wait a very long time. Fixes part of bug 19969; bugfix
6870 o Major bugfixes (download scheduling):
6871 - When using an exponential backoff schedule, do not give up on
6872 downloading just because we have failed a bunch of times. Since
6873 each delay is longer than the last, retrying indefinitely won't
6874 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
6875 - If a consensus expires while we are waiting for certificates to
6876 download, stop waiting for certificates.
6877 - If we stop waiting for certificates less than a minute after we
6878 started downloading them, do not consider the certificate download
6879 failure a separate failure. Fixes bug 20533; bugfix
6881 - Remove the maximum delay on exponential-backoff scheduling. Since
6882 we now allow an infinite number of failures (see ticket 20536), we
6883 must now allow the time to grow longer on each failure. Fixes part
6884 of bug 20534; bugfix on 0.2.9.1-alpha.
6885 - Make our initial download delays closer to those from 0.2.8. Fixes
6886 another part of bug 20534; bugfix on 0.2.9.1-alpha.
6887 - When determining when to download a directory object, handle times
6888 after 2038 if the operating system supports them. (Someday this
6889 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
6890 - When using exponential backoff in test networks, use a lower
6891 exponent, so the delays do not vary as much. This helps test
6892 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
6894 o Minor features (geoip):
6895 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
6898 o Minor bugfixes (client directory scheduling):
6899 - Treat "relay too busy to answer request" as a failed request and a
6900 reason to back off on our retry frequency. This is safe now that
6901 exponential backoffs retry indefinitely, and avoids a bug where we
6902 would reset our download schedule erroneously. Fixes bug 20593;
6903 bugfix on 0.2.9.1-alpha.
6905 o Minor bugfixes (client, logging):
6906 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
6907 assume all nodes support EXTEND2. Use ntor whenever a key is
6908 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
6909 - On DNSPort, stop logging a BUG warning on a failed hostname
6910 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
6912 o Minor bugfixes (hidden services):
6913 - When configuring hidden services, check every hidden service
6914 directory's permissions. Previously, we only checked the last
6915 hidden service. Fixes bug 20529; bugfix the work to fix 13942
6918 o Minor bugfixes (portability):
6919 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
6920 architectures. Closes ticket 20588.
6921 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
6922 removed the ECDH ciphers which caused the tests to fail on
6923 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
6924 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
6925 20551; bugfix on 0.2.1.1-alpha.
6927 o Minor bugfixes (relay bootstrap):
6928 - Ensure relays don't make multiple connections during bootstrap.
6929 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
6931 o Minor bugfixes (relay):
6932 - Work around a memory leak in OpenSSL 1.1 when encoding public
6933 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
6934 - Avoid a small memory leak when informing worker threads about
6935 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
6936 - Do not try to parallelize workers more than 16x without the user
6937 explicitly configuring us to do so, even if we do detect more than
6938 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
6940 o Minor bugfixes (single onion services):
6941 - Start correctly when creating a single onion service in a
6942 directory that did not previously exist. Fixes bug 20484; bugfix
6945 o Minor bugfixes (testing):
6946 - Avoid a unit test failure on systems with over 16 detectable CPU
6947 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
6950 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
6951 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
6952 - Module-level documentation for several more modules. Closes
6953 tickets 19287 and 19290.
6956 Changes in version 0.2.8.9 - 2016-10-17
6957 Tor 0.2.8.9 backports a fix for a security hole in previous versions
6958 of Tor that would allow a remote attacker to crash a Tor client,
6959 hidden service, relay, or authority. All Tor users should upgrade to
6960 this version, or to 0.2.9.4-alpha. Patches will be released for older
6963 o Major features (security fixes, also in 0.2.9.4-alpha):
6964 - Prevent a class of security bugs caused by treating the contents
6965 of a buffer chunk as if they were a NUL-terminated string. At
6966 least one such bug seems to be present in all currently used
6967 versions of Tor, and would allow an attacker to remotely crash
6968 most Tor instances, especially those compiled with extra compiler
6969 hardening. With this defense in place, such bugs can't crash Tor,
6970 though we should still fix them as they occur. Closes ticket
6971 20384 (TROVE-2016-10-001).
6973 o Minor features (geoip):
6974 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
6978 Changes in version 0.2.9.4-alpha - 2016-10-17
6979 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
6980 that would allow a remote attacker to crash a Tor client, hidden
6981 service, relay, or authority. All Tor users should upgrade to this
6982 version, or to 0.2.8.9. Patches will be released for older versions
6985 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
6986 previous versions of Tor, including the implementation of a feature to
6987 future- proof the Tor ecosystem against protocol changes, some bug
6988 fixes necessary for Tor Browser to use unix domain sockets correctly,
6989 and several portability improvements. We anticipate that this will be
6990 the last alpha in the Tor 0.2.9 series, and that the next release will
6991 be a release candidate.
6993 o Major features (security fixes):
6994 - Prevent a class of security bugs caused by treating the contents
6995 of a buffer chunk as if they were a NUL-terminated string. At
6996 least one such bug seems to be present in all currently used
6997 versions of Tor, and would allow an attacker to remotely crash
6998 most Tor instances, especially those compiled with extra compiler
6999 hardening. With this defense in place, such bugs can't crash Tor,
7000 though we should still fix them as they occur. Closes ticket
7001 20384 (TROVE-2016-10-001).
7003 o Major features (subprotocol versions):
7004 - Tor directory authorities now vote on a set of recommended
7005 subprotocol versions, and on a set of required subprotocol
7006 versions. Clients and relays that lack support for a _required_
7007 subprotocol version will not start; those that lack support for a
7008 _recommended_ subprotocol version will warn the user to upgrade.
7009 Closes ticket 19958; implements part of proposal 264.
7010 - Tor now uses "subprotocol versions" to indicate compatibility.
7011 Previously, versions of Tor looked at the declared Tor version of
7012 a relay to tell whether they could use a given feature. Now, they
7013 should be able to rely on its declared subprotocol versions. This
7014 change allows compatible implementations of the Tor protocol(s) to
7015 exist without pretending to be 100% bug-compatible with particular
7016 releases of Tor itself. Closes ticket 19958; implements part of
7019 o Minor feature (fallback directories):
7020 - Remove broken fallbacks from the hard-coded fallback directory
7021 list. Closes ticket 20190; patch by teor.
7023 o Minor features (client, directory):
7024 - Since authorities now omit all routers that lack the Running and
7025 Valid flags, we assume that any relay listed in the consensus must
7026 have those flags. Closes ticket 20001; implements part of
7029 o Minor features (compilation, portability):
7030 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
7033 o Minor features (development tools, etags):
7034 - Teach the "make tags" Makefile target how to correctly find
7035 "MOCK_IMPL" function definitions. Patch from nherring; closes
7038 o Minor features (geoip):
7039 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
7042 o Minor features (unix domain sockets):
7043 - When configuring a unix domain socket for a SocksPort,
7044 ControlPort, or Hidden service, you can now wrap the address in
7045 quotes, using C-style escapes inside the quotes. This allows unix
7046 domain socket paths to contain spaces.
7048 o Minor features (virtual addresses):
7049 - Increase the maximum number of bits for the IPv6 virtual network
7050 prefix from 16 to 104. In this way, the condition for address
7051 allocation is less restrictive. Closes ticket 20151; feature
7054 o Minor bugfixes (address discovery):
7055 - Stop reordering IP addresses returned by the OS. This makes it
7056 more likely that Tor will guess the same relay IP address every
7057 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
7058 Reported by René Mayrhofer, patch by "cypherpunks".
7060 o Minor bugfixes (client, unix domain sockets):
7061 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
7062 the client address is meaningless. Fixes bug 20261; bugfix
7065 o Minor bugfixes (compilation, OpenBSD):
7066 - Detect Libevent2 functions correctly on systems that provide
7067 libevent2, but where libevent1 is linked with -levent. Fixes bug
7068 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
7070 o Minor bugfixes (configuration):
7071 - When parsing quoted configuration values from the torrc file,
7072 handle windows line endings correctly. Fixes bug 19167; bugfix on
7073 0.2.0.16-alpha. Patch from "Pingl".
7075 o Minor bugfixes (getpass):
7076 - Defensively fix a non-triggerable heap corruption at do_getpass()
7077 to protect ourselves from mistakes in the future. Fixes bug
7078 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
7081 o Minor bugfixes (hidden service):
7082 - Allow hidden services to run on IPv6 addresses even when the
7083 IPv6Exit option is not set. Fixes bug 18357; bugfix
7087 - Add module-level internal documentation for 36 C files that
7088 previously didn't have a high-level overview. Closes ticket #20385.
7090 o Required libraries:
7091 - When building with OpenSSL, Tor now requires version 1.0.1 or
7092 later. OpenSSL 1.0.0 and earlier are no longer supported by the
7093 OpenSSL team, and should not be used. Closes ticket 20303.
7096 Changes in version 0.2.9.3-alpha - 2016-09-23
7097 Tor 0.2.9.3-alpha adds improved support for entities that want to make
7098 high-performance services available through the Tor .onion mechanism
7099 without themselves receiving anonymity as they host those services. It
7100 also tries harder to ensure that all steps on a circuit are using the
7101 strongest crypto possible, strengthens some TLS properties, and
7102 resolves several bugs -- including a pair of crash bugs from the 0.2.8
7103 series. Anybody running an earlier version of 0.2.9.x should upgrade.
7105 o Major bugfixes (crash, also in 0.2.8.8):
7106 - Fix a complicated crash bug that could affect Tor clients
7107 configured to use bridges when replacing a networkstatus consensus
7108 in which one of their bridges was mentioned. OpenBSD users saw
7109 more crashes here, but all platforms were potentially affected.
7110 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
7112 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
7113 - Fix a timing-dependent assertion failure that could occur when we
7114 tried to flush from a circuit after having freed its cells because
7115 of an out-of-memory condition. Fixes bug 20203; bugfix on
7116 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
7119 o Major features (circuit building, security):
7120 - Authorities, relays and clients now require ntor keys in all
7121 descriptors, for all hops (except for rare hidden service protocol
7122 cases), for all circuits, and for all other roles. Part of
7124 - Tor authorities, relays, and clients only use ntor, except for
7125 rare cases in the hidden service protocol. Part of ticket 19163.
7127 o Major features (single-hop "hidden" services):
7128 - Add experimental HiddenServiceSingleHopMode and
7129 HiddenServiceNonAnonymousMode options. When both are set to 1,
7130 every hidden service on a Tor instance becomes a non-anonymous
7131 Single Onion Service. Single Onions make one-hop (direct)
7132 connections to their introduction and renzedvous points. One-hop
7133 circuits make Single Onion servers easily locatable, but clients
7134 remain location-anonymous. This is compatible with the existing
7135 hidden service implementation, and works on the current tor
7136 network without any changes to older relays or clients. Implements
7137 proposal 260, completes ticket 17178. Patch by teor and asn.
7139 o Major features (resource management):
7140 - Tor can now notice it is about to run out of sockets, and
7141 preemptively close connections of lower priority. (This feature is
7142 off by default for now, since the current prioritizing method is
7143 yet not mature enough. You can enable it by setting
7144 "DisableOOSCheck 0", but watch out: it might close some sockets
7145 you would rather have it keep.) Closes ticket 18640.
7147 o Major bugfixes (circuit building):
7148 - Hidden service client-to-intro-point and service-to-rendezvous-
7149 point circuits use the TAP key supplied by the protocol, to avoid
7150 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
7152 o Major bugfixes (compilation, OpenBSD):
7153 - Fix a Libevent-detection bug in our autoconf script that would
7154 prevent Tor from linking successfully on OpenBSD. Patch from
7155 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
7157 o Major bugfixes (hidden services):
7158 - Clients now require hidden services to include the TAP keys for
7159 their intro points in the hidden service descriptor. This prevents
7160 an inadvertent upgrade to ntor, which a malicious hidden service
7161 could use to distinguish clients by consensus version. Fixes bug
7162 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
7164 o Minor features (security, TLS):
7165 - Servers no longer support clients that without AES ciphersuites.
7166 (3DES is no longer considered an acceptable cipher.) We believe
7167 that no such Tor clients currently exist, since Tor has required
7168 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
7170 o Minor feature (fallback directories):
7171 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
7172 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
7173 2016. Closes ticket 20190; patch by teor.
7175 o Minor features (geoip, also in 0.2.8.8):
7176 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
7179 o Minor feature (port flags):
7180 - Add new flags to the *Port options to finer control over which
7181 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
7182 and the synthetic flag OnionTrafficOnly, which is equivalent to
7183 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
7184 18693; patch by "teor".
7186 o Minor features (directory authority):
7187 - After voting, if the authorities decide that a relay is not
7188 "Valid", they no longer include it in the consensus at all. Closes
7189 ticket 20002; implements part of proposal 272.
7191 o Minor features (testing):
7192 - Disable memory protections on OpenBSD when performing our unit
7193 tests for memwipe(). The test deliberately invokes undefined
7194 behavior, and the OpenBSD protections interfere with this. Patch
7195 from "rubiate". Closes ticket 20066.
7197 o Minor features (testing, ipv6):
7198 - Add the single-onion and single-onion-ipv6 chutney targets to
7199 "make test-network-all". This requires a recent chutney version
7200 with the single onion network flavours (git c72a652 or later).
7201 Closes ticket 20072; patch by teor.
7202 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
7203 tests. Remove bridges+hs, as it's somewhat redundant. This
7204 requires a recent chutney version that supports IPv6 clients,
7205 relays, and authorities. Closes ticket 20069; patch by teor.
7207 o Minor features (Tor2web):
7208 - Make Tor2web clients respect ReachableAddresses. This feature was
7209 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
7210 0.2.8.7. Implements feature 20034. Patch by teor.
7212 o Minor features (unit tests):
7213 - We've done significant work to make the unit tests run faster.
7214 - Our link-handshake unit tests now check that when invalid
7215 handshakes fail, they fail with the error messages we expected.
7216 - Our unit testing code that captures log messages no longer
7217 prevents them from being written out if the user asked for them
7218 (by passing --debug or --info or or --notice --warn to the "test"
7219 binary). This change prevents us from missing unexpected log
7220 messages simply because we were looking for others. Related to
7222 - The unit tests now log all warning messages with the "BUG" flag.
7223 Previously, they only logged errors by default. This change will
7224 help us make our testing code more correct, and make sure that we
7225 only hit this code when we mean to. In the meantime, however,
7226 there will be more warnings in the unit test logs than before.
7227 This is preparatory work for ticket 19999.
7228 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
7229 assertion as a test failure.
7231 o Minor bug fixes (circuits):
7232 - Use the CircuitBuildTimeout option whenever
7233 LearnCircuitBuildTimeout is disabled. Previously, we would respect
7234 the option when a user disabled it, but not when it was disabled
7235 because some other option was set. Fixes bug 20073; bugfix on
7236 0.2.4.12-alpha. Patch by teor.
7238 o Minor bugfixes (allocation):
7239 - Change how we allocate memory for large chunks on buffers, to
7240 avoid a (currently impossible) integer overflow, and to waste less
7241 space when allocating unusually large chunks. Fixes bug 20081;
7242 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
7243 - Always include orconfig.h before including any other C headers.
7244 Sometimes, it includes macros that affect the behavior of the
7245 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
7246 first version to use AC_USE_SYSTEM_EXTENSIONS).
7247 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
7248 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
7249 Patch from Gisle Vanem.
7250 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
7251 They apparently require a set of annotations that we aren't
7252 currently using, and they create false positives in our pthreads
7253 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
7255 o Minor bugfixes (directory authority):
7256 - Die with a more useful error when the operator forgets to place
7257 the authority_signing_key file into the keys directory. This
7258 avoids an uninformative assert & traceback about having an invalid
7259 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
7260 - When allowing private addresses, mark Exits that only exit to
7261 private locations as such. Fixes bug 20064; bugfix
7264 o Minor bugfixes (documentation):
7265 - Document the default PathsNeededToBuildCircuits value that's used
7266 by clients when the directory authorities don't set
7267 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
7268 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
7269 - Fix manual for the User option: it takes a username, not a UID.
7270 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
7273 o Minor bugfixes (hidden services):
7274 - Stop logging intro point details to the client log on certain
7275 error conditions. Fixed as part of bug 20012; bugfix on
7276 0.2.4.8-alpha. Patch by teor.
7278 o Minor bugfixes (IPv6, testing):
7279 - Check for IPv6 correctly on Linux when running test networks.
7280 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
7282 o Minor bugfixes (Linux seccomp2 sandbox):
7283 - Add permission to run the sched_yield() and sigaltstack() system
7284 calls, in order to support versions of Tor compiled with asan or
7285 ubsan code that use these calls. Now "sandbox 1" and
7286 "--enable-expensive-hardening" should be compatible on more
7287 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
7289 o Minor bugfixes (logging):
7290 - When logging a message from the BUG() macro, be explicit about
7291 what we were asserting. Previously we were confusing what we were
7292 asserting with what the bug was. Fixes bug 20093; bugfix
7294 - When we are unable to remove the bw_accounting file, do not warn
7295 if the reason we couldn't remove it was that it didn't exist.
7296 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
7298 o Minor bugfixes (option parsing):
7299 - Count unix sockets when counting client listeners (SOCKS, Trans,
7300 NATD, and DNS). This has no user-visible behaviour changes: these
7301 options are set once, and never read. Required for correct
7302 behaviour in ticket 17178. Fixes bug 19677; bugfix on
7303 0.2.6.3-alpha. Patch by teor.
7305 o Minor bugfixes (options):
7306 - Check the consistency of UseEntryGuards and EntryNodes more
7307 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
7309 - Stop changing the configured value of UseEntryGuards on
7310 authorities and Tor2web clients. Fixes bug 20074; bugfix on
7311 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
7314 o Minor bugfixes (Tor2web):
7315 - Prevent Tor2web clients running hidden services, these services
7316 are not anonymous due to the one-hop client paths. Fixes bug
7317 19678. Patch by teor.
7319 o Minor bugfixes (unit tests):
7320 - Fix a shared-random unit test that was failing on big endian
7321 architectures due to internal representation of a integer copied
7322 to a buffer. The test is changed to take a full 32 bytes of data
7323 and use the output of a python script that make the COMMIT and
7324 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
7326 - The tor_tls_server_info_callback unit test no longer crashes when
7327 debug-level logging is turned on. Fixes bug 20041; bugfix
7331 Changes in version 0.2.8.8 - 2016-09-23
7332 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
7333 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
7334 who select public relays as their bridges.
7336 o Major bugfixes (crash):
7337 - Fix a complicated crash bug that could affect Tor clients
7338 configured to use bridges when replacing a networkstatus consensus
7339 in which one of their bridges was mentioned. OpenBSD users saw
7340 more crashes here, but all platforms were potentially affected.
7341 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
7343 o Major bugfixes (relay, OOM handler):
7344 - Fix a timing-dependent assertion failure that could occur when we
7345 tried to flush from a circuit after having freed its cells because
7346 of an out-of-memory condition. Fixes bug 20203; bugfix on
7347 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
7350 o Minor feature (fallback directories):
7351 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
7352 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
7353 2016. Closes ticket 20190; patch by teor.
7355 o Minor features (geoip):
7356 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
7360 Changes in version 0.2.9.2-alpha - 2016-08-24
7361 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
7362 several new features and bugfixes. It also includes an important
7363 authority update and an important bugfix from 0.2.8.7. Everyone who
7364 sets the ReachableAddresses option, and all bridges, are strongly
7365 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
7367 o Directory authority changes (also in 0.2.8.7):
7368 - The "Tonga" bridge authority has been retired; the new bridge
7369 authority is "Bifroest". Closes tickets 19728 and 19690.
7371 o Major bugfixes (client, security, also in 0.2.8.7):
7372 - Only use the ReachableAddresses option to restrict the first hop
7373 in a path. In earlier versions of 0.2.8.x, it would apply to
7374 every hop in the path, with a possible degradation in anonymity
7375 for anyone using an uncommon ReachableAddress setting. Fixes bug
7376 19973; bugfix on 0.2.8.2-alpha.
7378 o Major features (user interface):
7379 - Tor now supports the ability to declare options deprecated, so
7380 that we can recommend that people stop using them. Previously,
7381 this was done in an ad-hoc way. Closes ticket 19820.
7383 o Major bugfixes (directory downloads):
7384 - Avoid resetting download status for consensuses hourly, since we
7385 already have another, smarter retry mechanism. Fixes bug 8625;
7386 bugfix on 0.2.0.9-alpha.
7388 o Minor features (config):
7389 - Warn users when descriptor and port addresses are inconsistent.
7390 Mitigates bug 13953; patch by teor.
7392 o Minor features (geoip):
7393 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
7396 o Minor features (user interface):
7397 - There is a new --list-deprecated-options command-line option to
7398 list all of the deprecated options. Implemented as part of
7401 o Minor bugfixes (code style):
7402 - Fix an integer signedness conversion issue in the case conversion
7403 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
7405 o Minor bugfixes (compilation):
7406 - Build correctly on versions of libevent2 without support for
7407 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
7409 - Fix a compilation warning on GCC versions before 4.6. Our
7410 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
7411 when it is also required as an argument to the compiler pragma.
7412 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
7414 o Minor bugfixes (compilation, also in 0.2.8.7):
7415 - Remove an inappropriate "inline" in tortls.c that was causing
7416 warnings on older versions of GCC. Fixes bug 19903; bugfix
7419 o Minor bugfixes (fallback directories, also in 0.2.8.7):
7420 - Avoid logging a NULL string pointer when loading fallback
7421 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
7422 and 0.2.8.1-alpha. Report and patch by "rubiate".
7424 o Minor bugfixes (logging):
7425 - Log a more accurate message when we fail to dump a microdescriptor.
7426 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
7428 o Minor bugfixes (memory leak):
7429 - Fix a series of slow memory leaks related to parsing torrc files
7430 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
7432 o Deprecated features:
7433 - A number of DNS-cache-related sub-options for client ports are now
7434 deprecated for security reasons, and may be removed in a future
7435 version of Tor. (We believe that client-side DNS caching is a bad
7436 idea for anonymity, and you should not turn it on.) The options
7437 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
7438 UseIPv4Cache, and UseIPv6Cache.
7439 - A number of options are deprecated for security reasons, and may
7440 be removed in a future version of Tor. The options are:
7441 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
7442 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
7443 CloseHSClientCircuitsImmediatelyOnTimeout,
7444 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
7445 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
7446 UseNTorHandshake, and WarnUnsafeSocks.
7447 - The *ListenAddress options are now deprecated as unnecessary: the
7448 corresponding *Port options should be used instead. These options
7449 may someday be removed. The affected options are:
7450 ControlListenAddress, DNSListenAddress, DirListenAddress,
7451 NATDListenAddress, ORListenAddress, SocksListenAddress,
7452 and TransListenAddress.
7455 - Correct the IPv6 syntax in our documentation for the
7456 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
7459 - We no longer include the (dead, deprecated) bufferevent code in
7460 Tor. Closes ticket 19450. Based on a patch from U+039b.
7463 Changes in version 0.2.8.7 - 2016-08-24
7464 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
7465 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
7466 who sets the ReachableAddresses option, and all bridges, are strongly
7467 encouraged to upgrade.
7469 o Directory authority changes:
7470 - The "Tonga" bridge authority has been retired; the new bridge
7471 authority is "Bifroest". Closes tickets 19728 and 19690.
7473 o Major bugfixes (client, security):
7474 - Only use the ReachableAddresses option to restrict the first hop
7475 in a path. In earlier versions of 0.2.8.x, it would apply to
7476 every hop in the path, with a possible degradation in anonymity
7477 for anyone using an uncommon ReachableAddress setting. Fixes bug
7478 19973; bugfix on 0.2.8.2-alpha.
7480 o Minor features (geoip):
7481 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
7484 o Minor bugfixes (compilation):
7485 - Remove an inappropriate "inline" in tortls.c that was causing
7486 warnings on older versions of GCC. Fixes bug 19903; bugfix
7489 o Minor bugfixes (fallback directories):
7490 - Avoid logging a NULL string pointer when loading fallback
7491 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
7492 and 0.2.8.1-alpha. Report and patch by "rubiate".
7495 Changes in version 0.2.9.1-alpha - 2016-08-08
7496 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
7497 series. It improves our support for hardened builds and compiler
7498 warnings, deploys some critical infrastructure for improvements to
7499 hidden services, includes a new timing backend that we hope to use for
7500 better support for traffic padding, makes it easier for programmers to
7501 log unexpected events, and contains other small improvements to
7502 security, correctness, and performance.
7504 Below are the changes since 0.2.8.6.
7506 o New system requirements:
7507 - Tor now requires Libevent version 2.0.10-stable or later. Older
7508 versions of Libevent have less efficient backends for several
7509 platforms, and lack the DNS code that we use for our server-side
7510 DNS support. This implements ticket 19554.
7511 - Tor now requires zlib version 1.2 or later, for security,
7512 efficiency, and (eventually) gzip support. (Back when we started,
7513 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
7514 released in 2003. We recommend the latest version.)
7516 o Major features (build, hardening):
7517 - Tor now builds with -ftrapv by default on compilers that support
7518 it. This option detects signed integer overflow (which C forbids),
7519 and turns it into a hard-failure. We do not apply this option to
7520 code that needs to run in constant time to avoid side-channels;
7521 instead, we use -fwrapv in that code. Closes ticket 17983.
7522 - When --enable-expensive-hardening is selected, stop applying the
7523 clang/gcc sanitizers to code that needs to run in constant time.
7524 Although we are aware of no introduced side-channels, we are not
7525 able to prove that there are none. Related to ticket 17983.
7527 o Major features (compilation):
7528 - Our big list of extra GCC warnings is now enabled by default when
7529 building with GCC (or with anything like Clang that claims to be
7530 GCC-compatible). To make all warnings into fatal compilation
7531 errors, pass --enable-fatal-warnings to configure. Closes
7533 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
7534 turn on C and POSIX extensions. (Previously, we attempted to do
7535 this on an ad hoc basis.) Closes ticket 19139.
7537 o Major features (directory authorities, hidden services):
7538 - Directory authorities can now perform the shared randomness
7539 protocol specified by proposal 250. Using this protocol, directory
7540 authorities generate a global fresh random value every day. In the
7541 future, this value will be used by hidden services to select
7542 HSDirs. This release implements the directory authority feature;
7543 the hidden service side will be implemented in the future as part
7544 of proposal 224. Resolves ticket 16943; implements proposal 250.
7546 o Major features (downloading, random exponential backoff):
7547 - When we fail to download an object from a directory service, wait
7548 for an (exponentially increasing) randomized amount of time before
7549 retrying, rather than a fixed interval as we did before. This
7550 prevents a group of Tor instances from becoming too synchronized,
7551 or a single Tor instance from becoming too predictable, in its
7552 download schedule. Closes ticket 15942.
7554 o Major bugfixes (exit policies):
7555 - Avoid disclosing exit outbound bind addresses, configured port
7556 bind addresses, and local interface addresses in relay descriptors
7557 by default under ExitPolicyRejectPrivate. Instead, only reject
7558 these (otherwise unlisted) addresses if
7559 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
7560 0.2.7.2-alpha. Patch by teor.
7562 o Major bugfixes (hidden service client):
7563 - Allow Tor clients with appropriate controllers to work with
7564 FetchHidServDescriptors set to 0. Previously, this option also
7565 disabled descriptor cache lookup, thus breaking hidden services
7566 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
7568 o Minor features (build, hardening):
7569 - Detect and work around a libclang_rt problem that would prevent
7570 clang from finding __mulodi4() on some 32-bit platforms, and thus
7571 keep -ftrapv from linking on those systems. Closes ticket 19079.
7572 - When building on a system without runtime support for the runtime
7573 hardening options, try to log a useful warning at configuration
7574 time, rather than an incomprehensible warning at link time. If
7575 expensive hardening was requested, this warning becomes an error.
7576 Closes ticket 18895.
7578 o Minor features (code safety):
7579 - In our integer-parsing functions, ensure that maxiumum value we
7580 give is no smaller than the minimum value. Closes ticket 19063;
7583 o Minor features (controller):
7584 - Implement new GETINFO queries for all downloads that use
7585 download_status_t to schedule retries. This allows controllers to
7586 examine the schedule for pending downloads. Closes ticket 19323.
7587 - Allow controllers to configure basic client authorization on
7588 hidden services when they create them with the ADD_ONION control
7589 command. Implements ticket 15588. Patch by "special".
7590 - Fire a STATUS_SERVER controller event whenever the hibernation
7591 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
7593 o Minor features (directory authority):
7594 - Directory authorities now only give the Guard flag to a relay if
7595 they are also giving it the Stable flag. This change allows us to
7596 simplify path selection for clients. It should have minimal effect
7597 in practice, since >99% of Guards already have the Stable flag.
7598 Implements ticket 18624.
7599 - Directory authorities now write their v3-status-votes file out to
7600 disk earlier in the consensus process, so we have a record of the
7601 votes even if we abort the consensus process. Resolves
7604 o Minor features (hidden service):
7605 - Stop being so strict about the payload length of "rendezvous1"
7606 cells. We used to be locked in to the "TAP" handshake length, and
7607 now we can handle better handshakes like "ntor". Resolves
7610 o Minor features (infrastructure, time):
7611 - Tor now uses the operating system's monotonic timers (where
7612 available) for internal fine-grained timing. Previously we would
7613 look at the system clock, and then attempt to compensate for the
7614 clock running backwards. Closes ticket 18908.
7615 - Tor now includes an improved timer backend, so that we can
7616 efficiently support tens or hundreds of thousands of concurrent
7617 timers, as will be needed for some of our planned anti-traffic-
7618 analysis work. This code is based on William Ahern's "timeout.c"
7619 project, which implements a "tickless hierarchical timing wheel".
7620 Closes ticket 18365.
7622 o Minor features (logging):
7623 - Provide a more useful warning message when configured with an
7624 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
7625 - When dumping unparseable router descriptors, optionally store them
7626 in separate files, named by digest, up to a configurable size
7627 limit. You can change the size limit by setting the
7628 MaxUnparseableDescSizeToLog option, and disable this feature by
7629 setting that option to 0. Closes ticket 18322.
7630 - Add a set of macros to check nonfatal assertions, for internal
7631 use. Migrating more of our checks to these should help us avoid
7632 needless crash bugs. Closes ticket 18613.
7634 o Minor features (performance):
7635 - Changer the "optimistic data" extension from "off by default" to
7636 "on by default". The default was ordinarily overridden by a
7637 consensus option, but when clients were bootstrapping for the
7638 first time, they would not have a consensus to get the option
7639 from. Changing this default When fetching a consensus for the
7640 first time, use optimistic data. This saves a round-trip during
7641 startup. Closes ticket 18815.
7643 o Minor features (relay, usability):
7644 - When the directory authorities refuse a bad relay's descriptor,
7645 encourage the relay operator to contact us. Many relay operators
7646 won't notice this line in their logs, but it's a win if even a few
7647 learn why we don't like what their relay was doing. Resolves
7650 o Minor features (testing):
7651 - Let backtrace tests work correctly under AddressSanitizer. Fixes
7652 part of bug 18934; bugfix on 0.2.5.2-alpha.
7653 - Move the test-network.sh script to chutney, and modify tor's test-
7654 network.sh to call the (newer) chutney version when available.
7655 Resolves ticket 19116. Patch by teor.
7656 - Use the lcov convention for marking lines as unreachable, so that
7657 we don't count them when we're generating test coverage data.
7658 Update our coverage tools to understand this convention. Closes
7661 o Minor bugfixes (bootstrap):
7662 - Remember the directory we fetched the consensus or previous
7663 certificates from, and use it to fetch future authority
7664 certificates. This change improves bootstrapping performance.
7665 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
7667 o Minor bugfixes (build):
7668 - The test-stem and test-network makefile targets now depend only on
7669 the tor binary that they are testing. Previously, they depended on
7670 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
7671 patch from "cypherpunks".
7673 o Minor bugfixes (circuits):
7674 - Make sure extend_info_from_router() is only called on servers.
7675 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
7677 o Minor bugfixes (compilation):
7678 - When building with Clang, use a full set of GCC warnings.
7679 (Previously, we included only a subset, because of the way we
7680 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
7682 o Minor bugfixes (directory authority):
7683 - Authorities now sort the "package" lines in their votes, for ease
7684 of debugging. (They are already sorted in consensus documents.)
7685 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
7686 - When parsing a detached signature, make sure we use the length of
7687 the digest algorithm instead of an hardcoded DIGEST256_LEN in
7688 order to avoid comparing bytes out-of-bounds with a smaller digest
7689 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
7691 o Minor bugfixes (documentation):
7692 - Document the --passphrase-fd option in the tor manpage. Fixes bug
7693 19504; bugfix on 0.2.7.3-rc.
7694 - Fix the description of the --passphrase-fd option in the
7695 tor-gencert manpage. The option is used to pass the number of a
7696 file descriptor to read the passphrase from, not to read the file
7697 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
7699 o Minor bugfixes (ephemeral hidden service):
7700 - When deleting an ephemeral hidden service, close its intro points
7701 even if they are not completely open. Fixes bug 18604; bugfix
7704 o Minor bugfixes (guard selection):
7705 - Use a single entry guard even if the NumEntryGuards consensus
7706 parameter is not provided. Fixes bug 17688; bugfix
7708 - Don't mark guards as unreachable if connection_connect() fails.
7709 That function fails for local reasons, so it shouldn't reveal
7710 anything about the status of the guard. Fixes bug 14334; bugfix
7713 o Minor bugfixes (hidden service client):
7714 - Increase the minimum number of internal circuits we preemptively
7715 build from 2 to 3, so a circuit is available when a client
7716 connects to another onion service. Fixes bug 13239; bugfix
7719 o Minor bugfixes (logging):
7720 - When logging a directory ownership mismatch, log the owning
7721 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
7723 o Minor bugfixes (memory leaks):
7724 - Fix a small, uncommon memory leak that could occur when reading a
7725 truncated ed25519 key file. Fixes bug 18956; bugfix
7728 o Minor bugfixes (testing):
7729 - Allow clients to retry HSDirs much faster in test networks. Fixes
7730 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
7731 - Disable ASAN's detection of segmentation faults while running
7732 test_bt.sh, so that we can make sure that our own backtrace
7733 generation code works. Fixes another aspect of bug 18934; bugfix
7734 on 0.2.5.2-alpha. Patch from "cypherpunks".
7735 - Fix the test-network-all target on out-of-tree builds by using the
7736 correct path to the test driver script. Fixes bug 19421; bugfix
7739 o Minor bugfixes (time):
7740 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
7741 bugfix on all released tor versions.
7742 - When computing the difference between two times in milliseconds,
7743 we now round to the nearest millisecond correctly. Previously, we
7744 could sometimes round in the wrong direction. Fixes bug 19428;
7745 bugfix on 0.2.2.2-alpha.
7747 o Minor bugfixes (user interface):
7748 - Display a more accurate number of suppressed messages in the log
7749 rate-limiter. Previously, there was a potential integer overflow
7750 in the counter. Now, if the number of messages hits a maximum, the
7751 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
7753 - Fix a typo in the passphrase prompt for the ed25519 identity key.
7754 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
7756 o Code simplification and refactoring:
7757 - Remove redundant declarations of the MIN macro. Closes
7759 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
7760 Closes ticket 18462; patch from "icanhasaccount".
7761 - Split the 600-line directory_handle_command_get function into
7762 separate functions for different URL types. Closes ticket 16698.
7765 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
7766 ticket 19153. Patch from "U+039b".
7769 - Remove support for "GET /tor/bytes.txt" DirPort request, and
7770 "GETINFO dir-usage" controller request, which were only available
7771 via a compile-time option in Tor anyway. Feature was added in
7772 0.2.2.1-alpha. Resolves ticket 19035.
7773 - There is no longer a compile-time option to disable support for
7774 TransPort. (If you don't want TransPort; just don't use it.) Patch
7775 from "U+039b". Closes ticket 19449.
7778 - Run more workqueue tests as part of "make check". These had
7779 previously been implemented, but you needed to know special
7780 command-line options to enable them.
7781 - We now have unit tests for our code to reject zlib "compression
7782 bombs". (Fortunately, the code works fine.)
7785 Changes in version 0.2.8.6 - 2016-08-02
7787 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
7789 The Tor 0.2.8 series improves client bootstrapping performance,
7790 completes the authority-side implementation of improved identity
7791 keys for relays, and includes numerous bugfixes and performance
7792 improvements throughout the program. This release continues to
7793 improve the coverage of Tor's test suite. For a full list of
7794 changes since Tor 0.2.7, see the ReleaseNotes file.
7796 Changes since 0.2.8.5-rc:
7798 o Minor features (geoip):
7799 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
7802 o Minor bugfixes (compilation):
7803 - Fix a compilation warning in the unit tests on systems where char
7804 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
7806 o Minor bugfixes (fallback directories):
7807 - Remove 1 fallback that was on the hardcoded list, then opted-out,
7808 leaving 89 of the 100 fallbacks originally introduced in Tor
7809 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
7811 o Minor bugfixes (Linux seccomp2 sandbox):
7812 - Allow more syscalls when running with "Sandbox 1" enabled:
7813 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
7814 some systems, these are required for Tor to start. Fixes bug
7815 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
7816 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
7817 so that get_interface_address6_via_udp_socket_hack() can work.
7818 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
7821 Changes in version 0.2.8.5-rc - 2016-07-07
7822 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
7823 series. If we find no new bugs or regressions here, the first stable
7824 0.2.8 release will be identical to it. It has a few small bugfixes
7825 against previous versions.
7827 o Directory authority changes:
7828 - Urras is no longer a directory authority. Closes ticket 19271.
7830 o Major bugfixes (heartbeat):
7831 - Fix a regression that would crash Tor when the periodic
7832 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
7833 0.2.8.1-alpha. Reported by "kubaku".
7835 o Minor features (build):
7836 - Tor now again builds with the recent OpenSSL 1.1 development
7837 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
7838 - When building manual pages, set the timezone to "UTC", so that the
7839 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
7840 Patch from intrigeri.
7842 o Minor bugfixes (fallback directory selection):
7843 - Avoid errors during fallback selection if there are no eligible
7844 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
7847 o Minor bugfixes (IPv6, microdescriptors):
7848 - Don't check node addresses when we only have a routerstatus. This
7849 allows IPv6-only clients to bootstrap by fetching microdescriptors
7850 from fallback directory mirrors. (The microdescriptor consensus
7851 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
7854 o Minor bugfixes (logging):
7855 - Reduce pointlessly verbose log messages when directory servers
7856 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
7857 0.2.8.1-alpha. Patch by teor.
7858 - When a fallback directory changes its fingerprint from the hard-
7859 coded fingerprint, log a less severe, more explanatory log
7860 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
7862 o Minor bugfixes (Linux seccomp2 sandboxing):
7863 - Allow statistics to be written to disk when "Sandbox 1" is
7864 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
7865 0.2.6.1-alpha respectively.
7867 o Minor bugfixes (user interface):
7868 - Remove a warning message "Service [scrubbed] not found after
7869 descriptor upload". This message appears when one uses HSPOST
7870 control command to upload a service descriptor. Since there is
7871 only a descriptor and no service, showing this message is
7872 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
7874 o Fallback directory list:
7875 - Add a comment to the generated fallback directory list that
7876 explains how to comment out unsuitable fallbacks in a way that's
7877 compatible with the stem fallback parser.
7878 - Update fallback whitelist and blacklist based on relay operator
7879 emails. Blacklist unsuitable (non-working, over-volatile)
7880 fallbacks. Resolves ticket 19071. Patch by teor.
7881 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
7882 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
7883 ticket 19071; patch by teor.
7886 Changes in version 0.2.8.4-rc - 2016-06-15
7887 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
7888 If we find no new bugs or regressions here, the first stable 0.2.8
7889 release will be identical to it. It has a few small bugfixes against
7892 o Major bugfixes (user interface):
7893 - Correctly give a warning in the cases where a relay is specified
7894 by nickname, and one such relay is found, but it is not officially
7895 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
7897 o Minor features (build):
7898 - Tor now builds once again with the recent OpenSSL 1.1 development
7899 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
7901 o Minor features (geoip):
7902 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
7905 o Minor bugfixes (compilation):
7906 - Cause the unit tests to compile correctly on mingw64 versions that
7907 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
7909 o Minor bugfixes (downloading):
7910 - Predict more correctly whether we'll be downloading over HTTP when
7911 we determine the maximum length of a URL. This should avoid a
7912 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
7916 Changes in version 0.2.8.3-alpha - 2016-05-26
7917 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
7918 the course of the 0.2.8 development cycle. It improves the behavior of
7919 directory clients, fixes several crash bugs, fixes a gap in compiler
7920 hardening, and allows the full integration test suite to run on
7923 o Major bugfixes (security, client, DNS proxy):
7924 - Stop a crash that could occur when a client running with DNSPort
7925 received a query with multiple address types, and the first
7926 address type was not supported. Found and fixed by Scott Dial.
7927 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7929 o Major bugfixes (security, compilation):
7930 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
7931 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
7932 cause a compiler warning, thereby making other checks fail, and
7933 needlessly disabling compiler-hardening support. Fixes one case of
7934 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
7936 o Major bugfixes (security, directory authorities):
7937 - Fix a crash and out-of-bounds write during authority voting, when
7938 the list of relays includes duplicate ed25519 identity keys. Fixes
7939 bug 19032; bugfix on 0.2.8.2-alpha.
7941 o Major bugfixes (client, bootstrapping):
7942 - Check if bootstrap consensus downloads are still needed when the
7943 linked connection attaches. This prevents tor making unnecessary
7944 begindir-style connections, which are the only directory
7945 connections tor clients make since the fix for 18483 was merged.
7946 - Fix some edge cases where consensus download connections may not
7947 have been closed, even though they were not needed. Related to fix
7949 - Make relays retry consensus downloads the correct number of times,
7950 rather than the more aggressive client retry count. Fixes part of
7952 - Stop downloading consensuses when we have a consensus, even if we
7953 don't have all the certificates for it yet. Fixes bug 18809;
7954 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
7956 o Major bugfixes (directory mirrors):
7957 - Decide whether to advertise begindir support in the the same way
7958 we decide whether to advertise our DirPort. Allowing these
7959 decisions to become out-of-sync led to surprising behavior like
7960 advertising begindir support when hibernation made us not
7961 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
7964 o Major bugfixes (IPv6 bridges, client):
7965 - Actually use IPv6 addresses when selecting directory addresses for
7966 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
7969 o Major bugfixes (key management):
7970 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7971 pointer to the previous (uninitialized) key value. The impact here
7972 should be limited to a difficult-to-trigger crash, if OpenSSL is
7973 running an engine that makes key generation failures possible, or
7974 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7975 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7978 o Major bugfixes (testing):
7979 - Fix a bug that would block 'make test-network-all' on systems where
7980 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
7981 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
7982 bugfix on 0.2.8.1-alpha.
7984 o Minor features (clients):
7985 - Make clients, onion services, and bridge relays always use an
7986 encrypted begindir connection for directory requests. Resolves
7987 ticket 18483. Patch by "teor".
7989 o Minor features (fallback directory mirrors):
7990 - Give each fallback the same weight for client selection; restrict
7991 fallbacks to one per operator; report fallback directory detail
7992 changes when rebuilding list; add new fallback directory mirrors
7993 to the whitelist; and many other minor simplifications and fixes.
7994 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
7995 0.2.8.1-alpha; patch by "teor".
7996 - Replace the 21 fallbacks generated in January 2016 and included in
7997 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
7998 2016. Closes task 17158; patch by "teor".
8000 o Minor features (geoip):
8001 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
8004 o Minor bugfixes (assert, portability):
8005 - Fix an assertion failure in memarea.c on systems where "long" is
8006 shorter than the size of a pointer. Fixes bug 18716; bugfix
8009 o Minor bugfixes (bootstrap):
8010 - Consistently use the consensus download schedule for authority
8011 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
8013 o Minor bugfixes (build):
8014 - Remove a pair of redundant AM_CONDITIONAL declarations from
8015 configure.ac. Fixes one final case of bug 17744; bugfix
8017 - Resolve warnings when building on systems that are concerned with
8018 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
8020 - When libscrypt.h is found, but no libscrypt library can be linked,
8021 treat libscrypt as absent. Fixes bug 19161; bugfix
8024 o Minor bugfixes (client):
8025 - Turn all TestingClientBootstrap* into non-testing torrc options.
8026 This changes simply renames them by removing "Testing" in front of
8027 them and they do not require TestingTorNetwork to be enabled
8028 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
8029 - Make directory node selection more reliable, mainly for IPv6-only
8030 clients and clients with few reachable addresses. Fixes bug 18929;
8031 bugfix on 0.2.8.1-alpha. Patch by "teor".
8033 o Minor bugfixes (controller, microdescriptors):
8034 - Make GETINFO dir/status-vote/current/consensus conform to the
8035 control specification by returning "551 Could not open cached
8036 consensus..." when not caching consensuses. Fixes bug 18920;
8037 bugfix on 0.2.2.6-alpha.
8039 o Minor bugfixes (crypto, portability):
8040 - The SHA3 and SHAKE routines now produce the correct output on Big
8041 Endian systems. No code calls either algorithm yet, so this is
8042 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
8043 - Tor now builds again with the recent OpenSSL 1.1 development
8044 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
8047 o Minor bugfixes (directories):
8048 - When fetching extrainfo documents, compare their SHA256 digests
8049 and Ed25519 signing key certificates with the routerinfo that led
8050 us to fetch them, rather than with the most recent routerinfo.
8051 Otherwise we generate many spurious warnings about mismatches.
8052 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
8054 o Minor bugfixes (logging):
8055 - When we can't generate a signing key because OfflineMasterKey is
8056 set, do not imply that we should have been able to load it. Fixes
8057 bug 18133; bugfix on 0.2.7.2-alpha.
8058 - Stop periodic_event_dispatch() from blasting twelve lines per
8059 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
8060 - When rejecting a misformed INTRODUCE2 cell, only log at
8061 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
8063 o Minor bugfixes (pluggable transports):
8064 - Avoid reporting a spurious error when we decide that we don't need
8065 to terminate a pluggable transport because it has already exited.
8066 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
8068 o Minor bugfixes (pointer arithmetic):
8069 - Fix a bug in memarea_alloc() that could have resulted in remote
8070 heap write access, if Tor had ever passed an unchecked size to
8071 memarea_alloc(). Fortunately, all the sizes we pass to
8072 memarea_alloc() are pre-checked to be less than 128 kilobytes.
8073 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
8076 o Minor bugfixes (relays):
8077 - Consider more config options when relays decide whether to
8078 regenerate their descriptor. Fixes more of bug 12538; bugfix
8080 - Resolve some edge cases where we might launch an ORPort
8081 reachability check even when DisableNetwork is set. Noticed while
8082 fixing bug 18616; bugfix on 0.2.3.9-alpha.
8084 o Minor bugfixes (statistics):
8085 - We now include consensus downloads via IPv6 in our directory-
8086 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
8088 o Minor bugfixes (testing):
8089 - Allow directories in small networks to bootstrap by skipping
8090 DirPort checks when the consensus has no exits. Fixes bug 19003;
8091 bugfix on 0.2.8.1-alpha. Patch by teor.
8092 - Fix a small memory leak that would occur when the
8093 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
8094 bugfix on 0.2.5.2-alpha.
8096 o Minor bugfixes (time handling):
8097 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
8098 field. Otherwise, our unit tests crash on Windows. Fixes bug
8099 18977; bugfix on 0.2.2.25-alpha.
8102 - Document the contents of the 'datadir/keys' subdirectory in the
8103 manual page. Closes ticket 17621.
8104 - Stop recommending use of nicknames to identify relays in our
8105 MapAddress documentation. Closes ticket 18312.
8108 Changes in version 0.2.8.2-alpha - 2016-03-28
8109 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
8110 bugs in earlier versions of Tor, including some that prevented
8111 authorities using Tor 0.2.7.x from running correctly. IPv6 and
8112 directory support should also be much improved.
8114 o New system requirements:
8115 - Tor no longer supports versions of OpenSSL with a broken
8116 implementation of counter mode. (This bug was present in OpenSSL
8117 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
8118 longer runs with, these versions.
8119 - Tor no longer attempts to support platforms where the "time_t"
8120 type is unsigned. (To the best of our knowledge, only OpenVMS does
8121 this, and Tor has never actually built on OpenVMS.) Closes
8123 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
8124 later (released in 2008 and 2009 respectively). If you are
8125 building Tor from the git repository instead of from the source
8126 distribution, and your tools are older than this, you will need to
8127 upgrade. Closes ticket 17732.
8129 o Major bugfixes (security, pointers):
8130 - Avoid a difficult-to-trigger heap corruption attack when extending
8131 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8132 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8133 Reported by Guido Vranken.
8135 o Major bugfixes (bridges, pluggable transports):
8136 - Modify the check for OR connections to private addresses. Allow
8137 bridges on private addresses, including pluggable transports that
8138 ignore the (potentially private) address in the bridge line. Fixes
8139 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
8141 o Major bugfixes (compilation):
8142 - Repair hardened builds under the clang compiler. Previously, our
8143 use of _FORTIFY_SOURCE would conflict with clang's address
8144 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
8146 o Major bugfixes (crash on shutdown):
8147 - Correctly handle detaching circuits from muxes when shutting down.
8148 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
8149 - Fix an assert-on-exit bug related to counting memory usage in
8150 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
8152 o Major bugfixes (crash on startup):
8153 - Fix a segfault during startup: If a Unix domain socket was
8154 configured as listener (such as a ControlSocket or a SocksPort
8155 "unix:" socket), and tor was started as root but not configured to
8156 switch to another user, tor would segfault while trying to string
8157 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
8160 o Major bugfixes (dns proxy mode, crash):
8161 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8162 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8164 o Major bugfixes (relays, bridge clients):
8165 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
8166 bridge clients use the address configured in the bridge line.
8167 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
8170 o Major bugfixes (voting):
8171 - Actually enable support for authorities to match routers by their
8172 Ed25519 identities. Previously, the code had been written, but
8173 some debugging code that had accidentally been left in the
8174 codebase made it stay turned off. Fixes bug 17702; bugfix
8176 - When collating votes by Ed25519 identities, authorities now
8177 include a "NoEdConsensus" flag if the ed25519 value (or lack
8178 thereof) for a server does not reflect the majority consensus.
8179 Related to bug 17668; bugfix on 0.2.7.2-alpha.
8180 - When generating a vote with keypinning disabled, never include two
8181 entries for the same ed25519 identity. This bug was causing
8182 authorities to generate votes that they could not parse when a
8183 router violated key pinning by changing its RSA identity but
8184 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
8185 18318. Bugfix on 0.2.7.2-alpha.
8187 o Minor features (security, win32):
8188 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
8189 attack. Fixes bug 18123; bugfix on all tor versions. Patch
8192 o Minor features (bug-resistance):
8193 - Make Tor survive errors involving connections without a
8194 corresponding event object. Previously we'd fail with an
8195 assertion; now we produce a log message. Related to bug 16248.
8197 o Minor features (build):
8198 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
8199 as having possible IPFW support. Closes ticket 18448. Patch from
8202 o Minor features (code hardening):
8203 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
8204 level code, to harden against accidental failures to NUL-
8205 terminate. Part of ticket 17852. Patch from jsturgix. Found
8208 o Minor features (crypto):
8209 - Validate the hard-coded Diffie-Hellman parameters and ensure that
8210 p is a safe prime, and g is a suitable generator. Closes
8213 o Minor features (geoip):
8214 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
8217 o Minor features (hidden service directory):
8218 - Streamline relay-side hsdir handling: when relays consider whether
8219 to accept an uploaded hidden service descriptor, they no longer
8220 check whether they are one of the relays in the network that is
8221 "supposed" to handle that descriptor. Implements ticket 18332.
8223 o Minor features (IPv6):
8224 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
8225 to 1, tor prefers IPv6 directory addresses.
8226 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
8227 avoids using IPv4 for client OR and directory connections.
8228 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
8229 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
8230 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
8232 o Minor features (linux seccomp2 sandbox):
8233 - Reject attempts to change our Address with "Sandbox 1" enabled.
8234 Changing Address with Sandbox turned on would never actually work,
8235 but previously it would fail in strange and confusing ways. Found
8238 o Minor features (robustness):
8239 - Exit immediately with an error message if the code attempts to use
8240 Libevent without having initialized it. This should resolve some
8241 frequently-made mistakes in our unit tests. Closes ticket 18241.
8243 o Minor features (unix domain sockets):
8244 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
8245 Unix domain sockets without checking the permissions on the parent
8246 directory. (Tor checks permissions by default because some
8247 operating systems only check permissions on the parent directory.
8248 However, some operating systems do look at permissions on the
8249 socket, and tor's default check is unneeded.) Closes ticket 18458.
8252 o Minor bugfixes (exit policies, security):
8253 - Refresh an exit relay's exit policy when interface addresses
8254 change. Previously, tor only refreshed the exit policy when the
8255 configured external address changed. Fixes bug 18208; bugfix on
8256 0.2.7.3-rc. Patch by teor.
8258 o Minor bugfixes (security, hidden services):
8259 - Prevent hidden services connecting to client-supplied rendezvous
8260 addresses that are reserved as internal or multicast. Fixes bug
8261 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
8263 o Minor bugfixes (build):
8264 - Do not link the unit tests against both the testing and non-
8265 testing versions of the static libraries. Fixes bug 18490; bugfix
8267 - Avoid spurious failures from configure files related to calling
8268 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
8269 0.2.0.1-alpha. Patch from "cypherpunks".
8270 - Silence spurious clang-scan warnings in the ed25519_donna code by
8271 explicitly initializing some objects. Fixes bug 18384; bugfix on
8272 0.2.7.2-alpha. Patch by teor.
8274 o Minor bugfixes (client, bootstrap):
8275 - Count receipt of new microdescriptors as progress towards
8276 bootstrapping. Previously, with EntryNodes set, Tor might not
8277 successfully repopulate the guard set on bootstrapping. Fixes bug
8278 16825; bugfix on 0.2.3.1-alpha.
8280 o Minor bugfixes (code correctness):
8281 - Update to the latest version of Trunnel, which tries harder to
8282 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
8283 by clang address sanitizer. Fixes bug 18373; bugfix
8286 o Minor bugfixes (configuration):
8287 - Fix a tiny memory leak when parsing a port configuration ending in
8288 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
8290 o Minor bugfixes (containers):
8291 - If we somehow attempt to construct a heap with more than
8292 1073741822 elements, avoid an integer overflow when maintaining
8293 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
8295 o Minor bugfixes (correctness):
8296 - Fix a bad memory handling bug that would occur if we had queued a
8297 cell on a channel's incoming queue. Fortunately, we can't actually
8298 queue a cell like that as our code is constructed today, but it's
8299 best to avoid this kind of error, even if there isn't any code
8300 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
8302 o Minor bugfixes (directory):
8303 - When generating a URL for a directory server on an IPv6 address,
8304 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
8305 on 0.2.3.9-alpha. Patch from Malek.
8307 o Minor bugfixes (fallback directory mirrors):
8308 - When requesting extrainfo descriptors from a trusted directory
8309 server, check whether it is an authority or a fallback directory
8310 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
8311 0.2.4.7-alpha. Reported by atagar, patch by teor.
8313 o Minor bugfixes (hidden service, client):
8314 - Handle the case where the user makes several fast consecutive
8315 requests to the same .onion address. Previously, the first six
8316 requests would each trigger a descriptor fetch, each picking a
8317 directory (there are 6 overall) and the seventh one would fail
8318 because no directories were left, thereby triggering a close on
8319 all current directory connections asking for the hidden service.
8320 The solution here is to not close the connections if we have
8321 pending directory fetches. Fixes bug 15937; bugfix
8324 o Minor bugfixes (hidden service, control port):
8325 - Add the onion address to the HS_DESC event for the UPLOADED action
8326 both on success or failure. It was previously hardcoded with
8327 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
8329 o Minor bugfixes (hidden service, directory):
8330 - Bridges now refuse "rendezvous2" (hidden service descriptor)
8331 publish attempts. Suggested by ticket 18332.
8333 o Minor bugfixes (linux seccomp2 sandbox):
8334 - Allow the setrlimit syscall, and the prlimit and prlimit64
8335 syscalls, which some libc implementations use under the hood.
8336 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
8337 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
8338 enabled and no DNS resolvers configured. This should help TAILS
8339 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
8340 - Fix the sandbox's interoperability with unix domain sockets under
8341 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
8343 o Minor bugfixes (logging):
8344 - When logging information about an unparsable networkstatus vote or
8345 consensus, do not say "vote" when we mean consensus. Fixes bug
8346 18368; bugfix on 0.2.0.8-alpha.
8347 - Scrub service name in "unrecognized service ID" log messages.
8348 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
8349 - Downgrade logs and backtraces about IP versions to info-level.
8350 Only log backtraces once each time tor runs. Assists in diagnosing
8351 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
8352 Christian, patch by teor.
8354 o Minor bugfixes (memory safety):
8355 - Avoid freeing an uninitialized pointer when opening a socket fails
8356 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
8357 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
8359 - Correctly duplicate addresses in get_interface_address6_list().
8360 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
8361 patch by "cypherpunks".
8362 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
8364 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
8365 18672; bugfix on 0.2.5.1-alpha.
8367 o Minor bugfixes (private directory):
8368 - Prevent a race condition when creating private directories. Fixes
8369 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
8370 Patch from jsturgix. Found with Flawfinder.
8372 o Minor bugfixes (test networks, IPv6):
8373 - Allow internal IPv6 addresses in descriptors in test networks.
8374 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
8377 o Minor bugfixes (testing):
8378 - We no longer disable assertions in the unit tests when coverage is
8379 enabled. Instead, we require you to say --disable-asserts-in-tests
8380 to the configure script if you need assertions disabled in the
8381 unit tests (for example, if you want to perform branch coverage).
8382 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
8384 o Minor bugfixes (time parsing):
8385 - Avoid overflow in tor_timegm when parsing dates in and after 2038
8386 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
8387 0.0.2pre14. Patch by teor.
8389 o Minor bugfixes (tor-gencert):
8390 - Correctly handle the case where an authority operator enters a
8391 passphrase but sends an EOF before sending a newline. Fixes bug
8392 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
8394 o Code simplification and refactoring:
8395 - Quote all the string interpolations in configure.ac -- even those
8396 which we are pretty sure can't contain spaces. Closes ticket
8397 17744. Patch from zerosion.
8398 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
8399 inplace, so there's no need to have a separate implementation for
8400 the non-inplace code. Closes ticket 18258. Patch from Malek.
8401 - Simplify return types for some crypto functions that can't
8402 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
8405 - Change build messages to refer to "Fedora" instead of "Fedora
8406 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
8407 Patches from "icanhasaccount" and "cypherpunks".
8410 - We no longer maintain an internal freelist in memarea.c.
8411 Allocators should be good enough to make this code unnecessary,
8412 and it's doubtful that it ever had any performance benefit.
8415 - Fix several warnings from clang's address sanitizer produced in
8417 - Treat backtrace test failures as expected on FreeBSD until we
8418 solve bug 17808. Closes ticket 18204.
8421 Changes in version 0.2.8.1-alpha - 2016-02-04
8422 Tor 0.2.8.1-alpha is the first alpha release in its series. It
8423 includes numerous small features and bugfixes against previous Tor
8424 versions, and numerous small infrastructure improvements. The most
8425 notable features are a set of improvements to the directory subsystem.
8427 o Major features (security, Linux):
8428 - When Tor starts as root on Linux and is told to switch user ID, it
8429 can now retain the capability to bind to low ports. By default,
8430 Tor will do this only when it's switching user ID and some low
8431 ports have been configured. You can change this behavior with the
8432 new option KeepBindCapabilities. Closes ticket 8195.
8434 o Major features (directory system):
8435 - When bootstrapping multiple consensus downloads at a time, use the
8436 first one that starts downloading, and close the rest. This
8437 reduces failures when authorities or fallback directories are slow
8438 or down. Together with the code for feature 15775, this feature
8439 should reduces failures due to fallback churn. Implements ticket
8440 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
8441 "mikeperry" and "teor".
8442 - Include a trial list of 21 default fallback directories, generated
8443 in January 2016, based on an opt-in survey of suitable relays.
8444 Doing this should make clients bootstrap more quickly and reliably,
8445 and reduce the load on the directory authorities. Closes ticket
8446 15775. Patch by "teor".
8447 Candidates identified using an OnionOO script by "weasel", "teor",
8448 "gsathya", and "karsten".
8449 - Previously only relays that explicitly opened a directory port
8450 (DirPort) accepted directory requests from clients. Now all
8451 relays, with and without a DirPort, accept and serve tunneled
8452 directory requests that they receive through their ORPort. You can
8453 disable this behavior using the new DirCache option. Closes
8456 o Major key updates:
8457 - Update the V3 identity key for the dannenberg directory authority:
8458 it was changed on 18 November 2015. Closes task 17906. Patch
8461 o Minor features (security, clock):
8462 - Warn when the system clock appears to move back in time (when the
8463 state file was last written in the future). Tor doesn't know that
8464 consensuses have expired if the clock is in the past. Patch by
8465 "teor". Implements ticket 17188.
8467 o Minor features (security, exit policies):
8468 - ExitPolicyRejectPrivate now rejects more private addresses by
8469 default. Specifically, it now rejects the relay's outbound bind
8470 addresses (if configured), and the relay's configured port
8471 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
8472 0.2.0.11-alpha. Patch by "teor".
8474 o Minor features (security, memory erasure):
8475 - Set the unused entries in a smartlist to NULL. This helped catch
8476 a (harmless) bug, and shouldn't affect performance too much.
8477 Implements ticket 17026.
8478 - Use SecureMemoryWipe() function to securely clean memory on
8479 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
8480 Implements feature 17986.
8481 - Use explicit_bzero or memset_s when present. Previously, we'd use
8482 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
8483 from <logan@hackers.mu> and <selven@hackers.mu>.
8484 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8485 zero size. Check size argument to memwipe() for underflow. Fixes
8486 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8489 o Minor features (security, RNG):
8490 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
8491 positively are not allowed to fail. Previously we depended on
8492 internal details of OpenSSL's behavior. Closes ticket 17686.
8493 - Never use the system entropy output directly for anything besides
8494 seeding the PRNG. When we want to generate important keys, instead
8495 of using system entropy directly, we now hash it with the PRNG
8496 stream. This may help resist certain attacks based on broken OS
8497 entropy implementations. Closes part of ticket 17694.
8498 - Use modern system calls (like getentropy() or getrandom()) to
8499 generate strong entropy on platforms that have them. Closes
8502 o Minor features (accounting):
8503 - Added two modes to the AccountingRule option: One for limiting
8504 only the number of bytes sent ("AccountingRule out"), and one for
8505 limiting only the number of bytes received ("AccountingRule in").
8506 Closes ticket 15989; patch from "unixninja92".
8508 o Minor features (build):
8509 - Since our build process now uses "make distcheck", we no longer
8510 force "make dist" to depend on "make check". Closes ticket 17893;
8511 patch from "cypherpunks."
8512 - Tor now builds successfully with the recent OpenSSL 1.1
8513 development branch, and with the latest LibreSSL. Closes tickets
8514 17549, 17921, and 17984.
8516 o Minor features (controller):
8517 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
8518 tickets 16774 and 17817. Patch by George Tankersley.
8519 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
8520 service descriptor from a service's local hidden service
8521 descriptor cache. Closes ticket 14846.
8522 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
8523 controllers can examine the the reject rules added by
8524 ExitPolicyRejectPrivate. This makes it easier for stem to display
8527 o Minor features (crypto):
8528 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
8530 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
8531 - When allocating a digest state object, allocate no more space than
8532 we actually need. Previously, we would allocate as much space as
8533 the state for the largest algorithm would need. This change saves
8534 up to 672 bytes per circuit. Closes ticket 17796.
8535 - Improve performance when hashing non-multiple of 8 sized buffers,
8536 based on Andrew Moon's public domain SipHash-2-4 implementation.
8537 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
8539 o Minor features (directory downloads):
8540 - Wait for busy authorities and fallback directories to become non-
8541 busy when bootstrapping. (A similar change was made in 6c443e987d
8542 for directory caches chosen from the consensus.) Closes ticket
8543 17864; patch by "teor".
8544 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
8545 directory mirrors. The default is 1; set it to 0 to disable
8546 fallbacks. Implements ticket 17576. Patch by "teor".
8548 o Minor features (geoip):
8549 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
8552 o Minor features (IPv6):
8553 - Add an argument 'ipv6=address:orport' to the DirAuthority and
8554 FallbackDir torrc options, to specify an IPv6 address for an
8555 authority or fallback directory. Add hard-coded ipv6 addresses for
8556 directory authorities that have them. Closes ticket 17327; patch
8557 from Nick Mathewson and "teor".
8558 - Add address policy assume_action support for IPv6 addresses.
8559 - Limit IPv6 mask bits to 128.
8560 - Warn when comparing against an AF_UNSPEC address in a policy, it's
8561 almost always a bug. Closes ticket 17863; patch by "teor".
8562 - Allow users to configure directory authorities and fallback
8563 directory servers with IPv6 addresses and ORPorts. Resolves
8565 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
8566 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
8567 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
8568 17638; bugfix on 0.0.2pre8. Patch by "teor".
8570 o Minor features (logging):
8571 - When logging to syslog, allow a tag to be added to the syslog
8572 identity (the string prepended to every log message). The tag can
8573 be configured with SyslogIdentityTag and defaults to none. Setting
8574 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
8577 o Minor features (portability):
8578 - Use timingsafe_memcmp() where available. Closes ticket 17944;
8579 patch from <logan@hackers.mu>.
8581 o Minor features (relay, address discovery):
8582 - Add a family argument to get_interface_addresses_raw() and
8583 subfunctions to make network interface address interogation more
8584 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
8585 types of interfaces from the operating system. Resolves
8587 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
8588 fails to enumerate interface addresses using the platform-specific
8589 API, have it rely on the UDP socket fallback technique to try and
8590 find out what IP addresses (both IPv4 and IPv6) our machine has.
8591 Resolves ticket 17951.
8593 o Minor features (replay cache):
8594 - The replay cache now uses SHA256 instead of SHA1. Implements
8595 feature 8961. Patch by "teor", issue reported by "rransom".
8597 o Minor features (unix file permissions):
8598 - Defer creation of Unix sockets until after setuid. This avoids
8599 needing CAP_CHOWN and CAP_FOWNER when using systemd's
8600 CapabilityBoundingSet, or chown and fowner when using SELinux.
8601 Implements part of ticket 17562. Patch from Jamie Nguyen.
8602 - If any directory created by Tor is marked as group readable, the
8603 filesystem group is allowed to be either the default GID or the
8604 root user. Allowing root to read the DataDirectory prevents the
8605 need for CAP_READ_SEARCH when using systemd's
8606 CapabilityBoundingSet, or dac_read_search when using SELinux.
8607 Implements part of ticket 17562. Patch from Jamie Nguyen.
8608 - Introduce a new DataDirectoryGroupReadable option. If it is set to
8609 1, the DataDirectory will be made readable by the default GID.
8610 Implements part of ticket 17562. Patch from Jamie Nguyen.
8612 o Minor bugfixes (accounting):
8613 - The max bandwidth when using 'AccountRule sum' is now correctly
8614 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
8617 o Minor bugfixes (code correctness):
8618 - When closing an entry connection, generate a warning if we should
8619 have sent an end cell for it but we haven't. Fixes bug 17876;
8620 bugfix on 0.2.3.2-alpha.
8621 - Assert that allocated memory held by the reputation code is freed
8622 according to its internal counters. Fixes bug 17753; bugfix
8624 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
8627 o Minor bugfixes (compilation):
8628 - Mark all object files that include micro-revision.i as depending
8629 on it, so as to make parallel builds more reliable. Fixes bug
8630 17826; bugfix on 0.2.5.1-alpha.
8631 - Don't try to use the pthread_condattr_setclock() function unless
8632 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
8633 17819; bugfix on 0.2.6.3-alpha.
8634 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
8636 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
8637 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
8638 - Fix search for libevent libraries on OpenBSD (and other systems
8639 that install libevent 1 and libevent 2 in parallel). Fixes bug
8640 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
8641 - Isolate environment variables meant for tests from the rest of the
8642 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
8643 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
8645 - Remove config.log only from make distclean, not from make clean.
8646 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
8648 o Minor bugfixes (crypto):
8649 - Check the return value of HMAC() and assert on failure. Fixes bug
8650 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
8652 o Minor bugfixes (fallback directories):
8653 - Mark fallbacks as "too busy" when they return a 503 response,
8654 rather than just marking authorities. Fixes bug 17572; bugfix on
8655 0.2.4.7-alpha. Patch by "teor".
8657 o Minor bugfixes (IPv6):
8658 - Update the limits in max_dl_per_request for IPv6 address length.
8659 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
8661 o Minor bugfixes (linux seccomp2 sandbox):
8662 - Fix a crash when using offline master ed25519 keys with the Linux
8663 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
8665 o Minor bugfixes (logging):
8666 - In log messages that include a function name, use __FUNCTION__
8667 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
8668 with clang __PRETTY_FUNCTION__ has extra information we don't
8669 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
8671 - Remove needless quotes from a log message about unparseable
8672 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
8674 o Minor bugfixes (portability):
8675 - Remove an #endif from configure.ac so that we correctly detect the
8676 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
8679 o Minor bugfixes (relays):
8680 - Check that both the ORPort and DirPort (if present) are reachable
8681 before publishing a relay descriptor. Otherwise, relays publish a
8682 descriptor with DirPort 0 when the DirPort reachability test takes
8683 longer than the ORPort reachability test. Fixes bug 18050; bugfix
8684 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
8686 o Minor bugfixes (relays, hidden services):
8687 - Refuse connection requests to private OR addresses unless
8688 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
8689 then refuse to send any cells to a private address. Fixes bugs
8690 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
8692 o Minor bugfixes (safe logging):
8693 - When logging a malformed hostname received through socks4, scrub
8694 it if SafeLogging says we should. Fixes bug 17419; bugfix
8697 o Minor bugfixes (statistics code):
8698 - Consistently check for overflow in round_*_to_next_multiple_of
8699 functions, and add unit tests with additional and maximal values.
8700 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
8701 - Handle edge cases in the laplace functions: avoid division by
8702 zero, avoid taking the log of zero, and silence clang type
8703 conversion warnings using round and trunc. Add unit tests for edge
8704 cases with maximal values. Fixes part of bug 13192; bugfix
8707 o Minor bugfixes (testing):
8708 - The test for log_heartbeat was incorrectly failing in timezones
8709 with non-integer offsets. Instead of comparing the end of the time
8710 string against a constant, compare it to the output of
8711 format_local_iso_time when given the correct input. Fixes bug
8712 18039; bugfix on 0.2.5.4-alpha.
8713 - Make unit tests pass on IPv6-only systems, and systems without
8714 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
8715 bugfix on 0.2.7.3-rc. Patch by "teor".
8716 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
8718 - Check the full results of SHA256 and SHA512 digests in the unit
8719 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
8721 o Code simplification and refactoring:
8722 - Move logging of redundant policy entries in
8723 policies_parse_exit_policy_internal into its own function. Closes
8724 ticket 17608; patch from "juce".
8725 - Extract the more complicated parts of circuit_mark_for_close()
8726 into a new function that we run periodically before circuits are
8727 freed. This change removes more than half of the functions
8728 currently in the "blob". Closes ticket 17218.
8729 - Clean up a little duplicated code in
8730 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
8732 - Decouple the list of streams waiting to be attached to circuits
8733 from the overall connection list. This change makes it possible to
8734 attach streams quickly while simplifying Tor's callgraph and
8735 avoiding O(N) scans of the entire connection list. Closes
8737 - When a direct directory request fails immediately on launch,
8738 instead of relaunching that request from inside the code that
8739 launches it, instead mark the connection for teardown. This change
8740 simplifies Tor's callback and prevents the directory-request
8741 launching code from invoking itself recursively. Closes
8743 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
8744 use them. Closes ticket 17926.
8747 - Add a description of the correct use of the '--keygen' command-
8748 line option. Closes ticket 17583; based on text by 's7r'.
8749 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
8750 - Explain actual minima for BandwidthRate. Closes ticket 16382.
8751 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
8752 - Mention torspec URL in the manpage and point the reader to it
8753 whenever we mention a document that belongs in torspce. Fixes
8757 - Remove client-side support for connecting to Tor relays running
8758 versions of Tor before 0.2.3.6-alpha. These relays didn't support
8759 the v3 TLS handshake protocol, and are no longer allowed on the
8760 Tor network. Implements the client side of ticket 11150. Based on
8761 patches by Tom van der Woerdt.
8764 - Add unit tests to check for common RNG failure modes, such as
8765 returning all zeroes, identical values, or incrementing values
8766 (OpenSSL's rand_predictable feature). Patch by "teor".
8767 - Log more information when the backtrace tests fail. Closes ticket
8768 17892. Patch from "cypherpunks."
8769 - Always test both ed25519 backends, so that we can be sure that our
8770 batch-open replacement code works. Part of ticket 16794.
8771 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
8772 portion of ticket 16831.
8773 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
8774 util_format.c, directory.c, and options_validate.c. Closes tickets
8775 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
8777 - Unit tests for directory_handle_command_get. Closes ticket 17004.
8778 Patch from Reinaldo de Souza Jr.
8781 Changes in version 0.2.7.6 - 2015-12-10
8782 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
8783 well as a minor bug in hidden service reliability.
8785 o Major bugfixes (guard selection):
8786 - Actually look at the Guard flag when selecting a new directory
8787 guard. When we implemented the directory guard design, we
8788 accidentally started treating all relays as if they have the Guard
8789 flag during guard selection, leading to weaker anonymity and worse
8790 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8793 o Minor features (geoip):
8794 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
8797 o Minor bugfixes (compilation):
8798 - When checking for net/pfvar.h, include netinet/in.h if possible.
8799 This fixes transparent proxy detection on OpenBSD. Fixes bug
8800 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
8801 - Fix a compilation warning with Clang 3.6: Do not check the
8802 presence of an address which can never be NULL. Fixes bug 17781.
8804 o Minor bugfixes (correctness):
8805 - When displaying an IPv6 exit policy, include the mask bits
8806 correctly even when the number is greater than 31. Fixes bug
8807 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
8808 - The wrong list was used when looking up expired intro points in a
8809 rend service object, causing what we think could be reachability
8810 issues for hidden services, and triggering a BUG log. Fixes bug
8811 16702; bugfix on 0.2.7.2-alpha.
8812 - Fix undefined behavior in the tor_cert_checksig function. Fixes
8813 bug 17722; bugfix on 0.2.7.2-alpha.
8816 Changes in version 0.2.7.5 - 2015-11-20
8817 The Tor 0.2.7 release series is dedicated to the memory of Tor user
8818 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
8819 tirelessly to advocate human rights regardless of national borders,
8820 and oppose the encroachments of mass surveillance. He opposed national
8821 exceptionalism, he brought clarity to legal and policy debates, he
8822 understood and predicted the impact of mass surveillance on the world,
8823 and he laid the groundwork for resisting it. While serving on the Tor
8824 Project's board of directors, he brought us his uncompromising focus
8825 on technical excellence in the service of humankind. Caspar was an
8826 inimitable force for good and a wonderful friend. He was kind,
8827 humorous, generous, gallant, and believed we should protect one
8828 another without exception. We honor him here for his ideals, his
8829 efforts, and his accomplishments. Please honor his memory with works
8830 that would make him proud.
8832 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
8834 The 0.2.7 series adds a more secure identity key type for relays,
8835 improves cryptography performance, resolves several longstanding
8836 hidden-service performance issues, improves controller support for
8837 hidden services, and includes small bugfixes and performance
8838 improvements throughout the program. This release series also includes
8839 more tests than before, and significant simplifications to which parts
8840 of Tor invoke which others.
8842 (This release contains no code changes since 0.2.7.4-rc.)
8845 Changes in version 0.2.7.4-rc - 2015-10-21
8846 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
8847 fixes some important memory leaks, and a scary-looking (but mostly
8848 harmless in practice) invalid-read bug. It also has a few small
8849 bugfixes, notably fixes for compilation and portability on different
8850 platforms. If no further significant bounds are found, the next
8851 release will the the official stable release.
8853 o Major bugfixes (security, correctness):
8854 - Fix an error that could cause us to read 4 bytes before the
8855 beginning of an openssl string. This bug could be used to cause
8856 Tor to crash on systems with unusual malloc implementations, or
8857 systems with unusual hardening installed. Fixes bug 17404; bugfix
8860 o Major bugfixes (correctness):
8861 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
8862 bug 17401; bugfix on 0.2.7.3-rc.
8864 o Major bugfixes (memory leaks):
8865 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
8866 17398; bugfix on 0.2.6.1-alpha.
8867 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
8868 17402; bugfix on 0.2.7.3-rc.
8869 - Fix a memory leak when reading an expired signing key from disk.
8870 Fixes bug 17403; bugfix on 0.2.7.2-rc.
8872 o Minor features (geoIP):
8873 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
8876 o Minor bugfixes (compilation):
8877 - Repair compilation with the most recent (unreleased, alpha)
8878 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
8879 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
8880 17251; bugfix on 0.2.7.2-alpha.
8881 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
8882 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
8884 o Minor bugfixes (portability):
8885 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
8886 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
8889 o Minor bugfixes (sandbox):
8890 - Add the "hidserv-stats" filename to our sandbox filter for the
8891 HiddenServiceStatistics option to work properly. Fixes bug 17354;
8892 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
8894 o Minor bugfixes (testing):
8895 - Add unit tests for get_interface_address* failure cases. Fixes bug
8896 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
8897 - Fix breakage when running 'make check' with BSD make. Fixes bug
8898 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
8899 - Make the get_ifaddrs_* unit tests more tolerant of different
8900 network configurations. (Don't assume every test box has an IPv4
8901 address, and don't assume every test box has a non-localhost
8902 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
8903 - Skip backtrace tests when backtrace support is not compiled in.
8904 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
8908 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
8909 - Note that HiddenServicePorts can take a unix domain socket. Closes
8913 Changes in version 0.2.7.3-rc - 2015-09-25
8914 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
8915 contains numerous usability fixes for Ed25519 keys, safeguards against
8916 several misconfiguration problems, significant simplifications to
8917 Tor's callgraph, and numerous bugfixes and small features.
8919 This is the most tested release of Tor to date. The unit tests cover
8920 39.40% of the code, and the integration tests (accessible with "make
8921 test-full-online", requiring stem and chutney and a network
8922 connection) raise the coverage to 64.49%.
8924 o Major features (security, hidden services):
8925 - Hidden services, if using the EntryNodes option, are required to
8926 use more than one EntryNode, in order to avoid a guard discovery
8927 attack. (This would only affect people who had configured hidden
8928 services and manually specified the EntryNodes option with a
8929 single entry-node. The impact was that it would be easy to
8930 remotely identify the guard node used by such a hidden service.
8931 See ticket for more information.) Fixes ticket 14917.
8933 o Major features (Ed25519 keys, keypinning):
8934 - The key-pinning option on directory authorities is now advisory-
8935 only by default. In a future version, or when the AuthDirPinKeys
8936 option is set, pins are enforced again. Disabling key-pinning
8937 seemed like a good idea so that we can survive the fallout of any
8938 usability problems associated with Ed25519 keys. Closes
8941 o Major features (Ed25519 performance):
8942 - Improve the speed of Ed25519 operations and Curve25519 keypair
8943 generation when built targeting 32 bit x86 platforms with SSE2
8944 available. Implements ticket 16535.
8945 - Improve the runtime speed of Ed25519 signature verification by
8946 using Ed25519-donna's batch verification support. Implements
8949 o Major features (performance testing):
8950 - The test-network.sh script now supports performance testing.
8951 Requires corresponding chutney performance testing changes. Patch
8952 by "teor". Closes ticket 14175.
8954 o Major features (relay, Ed25519):
8955 - Significant usability improvements for Ed25519 key management. Log
8956 messages are better, and the code can recover from far more
8957 failure conditions. Thanks to "s7r" for reporting and diagnosing
8959 - Add a new OfflineMasterKey option to tell Tor never to try loading
8960 or generating a secret Ed25519 identity key. You can use this in
8961 combination with tor --keygen to manage offline and/or encrypted
8962 Ed25519 keys. Implements ticket 16944.
8963 - Add a --newpass option to allow changing or removing the
8964 passphrase of an encrypted key with tor --keygen. Implements part
8966 - On receiving a HUP signal, check to see whether the Ed25519
8967 signing key has changed, and reload it if so. Closes ticket 16790.
8969 o Major bugfixes (relay, Ed25519):
8970 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
8971 0.2.7.2-alpha. Reported by "s7r".
8972 - Improve handling of expired signing keys with offline master keys.
8973 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
8975 o Minor features (client-side privacy):
8976 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
8977 lifespan when IsolateSOCKSAuth and streams with SOCKS
8978 authentication are attached to the circuit. This allows
8979 applications like TorBrowser to manage circuit lifetime on their
8980 own. Implements feature 15482.
8981 - When logging malformed hostnames from SOCKS5 requests, respect
8982 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
8984 o Minor features (compilation):
8985 - Give a warning as early as possible when trying to build with an
8986 unsupported OpenSSL version. Closes ticket 16901.
8987 - Fail during configure if we're trying to build against an OpenSSL
8988 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
8989 which started requiring ECC.
8991 o Minor features (geoip):
8992 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
8995 o Minor features (hidden services):
8996 - Relays need to have the Fast flag to get the HSDir flag. As this
8997 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
8998 drop. This change should make some attacks against the hidden
8999 service directory system harder. Fixes ticket 15963.
9000 - Turn on hidden service statistics collection by setting the torrc
9001 option HiddenServiceStatistics to "1" by default. (This keeps
9002 track only of the fraction of traffic used by hidden services, and
9003 the total number of hidden services in existence.) Closes
9005 - Client now uses an introduction point failure cache to know when
9006 to fetch or keep a descriptor in their cache. Previously, failures
9007 were recorded implicitly, but not explicitly remembered. Closes
9010 o Minor features (testing, authorities, documentation):
9011 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
9012 explicitly manage consensus flags in testing networks. Patch by
9013 "robgjansen", modified by "teor". Implements part of ticket 14882.
9015 o Minor bugfixes (security, exit policies):
9016 - ExitPolicyRejectPrivate now also rejects the relay's published
9017 IPv6 address (if any), and any publicly routable IPv4 or IPv6
9018 addresses on any local interfaces. ticket 17027. Patch by "teor".
9019 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
9021 o Minor bug fixes (torrc exit policies):
9022 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
9023 produce IPv6 wildcard addresses. Previously they would produce
9024 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
9025 of bug 16069; bugfix on 0.2.4.7-alpha.
9026 - When parsing torrc ExitPolicies, we now warn for a number of cases
9027 where the user's intent is likely to differ from Tor's actual
9028 behavior. These include: using an IPv4 address with an accept6 or
9029 reject6 line; using "private" on an accept6 or reject6 line; and
9030 including any ExitPolicy lines after accept *:* or reject *:*.
9031 Related to ticket 16069.
9032 - When parsing torrc ExitPolicies, we now issue an info-level
9033 message when expanding an "accept/reject *" line to include both
9034 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
9035 - In each instance above, usage advice is provided to avoid the
9036 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
9037 16069; bugfix on 0.2.4.7-alpha.
9039 o Minor bugfixes (authority):
9040 - Don't assign "HSDir" to a router if it isn't Valid and Running.
9041 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
9042 - Downgrade log messages about Ed25519 key issues if they are in old
9043 cached router descriptors. Fixes part of bug 16286; bugfix
9045 - When we find an Ed25519 key issue in a cached descriptor, stop
9046 saying the descriptor was just "uploaded". Fixes another part of
9047 bug 16286; bugfix on 0.2.7.2-alpha.
9049 o Minor bugfixes (control port):
9050 - Repair a warning and a spurious result when getting the maximum
9051 number of file descriptors from the controller. Fixes bug 16697;
9052 bugfix on 0.2.7.2-alpha.
9054 o Minor bugfixes (correctness):
9055 - When calling channel_free_list(), avoid calling smartlist_remove()
9056 while inside a FOREACH loop. This partially reverts commit
9057 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
9058 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
9060 o Minor bugfixes (documentation):
9061 - Advise users on how to configure separate IPv4 and IPv6 exit
9062 policies in the manpage and sample torrcs. Related to ticket 16069.
9063 - Fix the usage message of tor-resolve(1) so that it no longer lists
9064 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
9065 - Fix an error in the manual page and comments for
9066 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
9067 required "ORPort connectivity". While this is true, it is in no
9068 way unique to the HSDir flag. Of all the flags, only HSDirs need a
9069 DirPort configured in order for the authorities to assign that
9070 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
9073 o Minor bugfixes (Ed25519):
9074 - Fix a memory leak when reading router descriptors with expired
9075 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
9077 o Minor bugfixes (linux seccomp2 sandbox):
9078 - Allow bridge authorities to run correctly under the seccomp2
9079 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
9080 - Allow routers with ed25519 keys to run correctly under the
9081 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
9083 o Minor bugfixes (open file limit):
9084 - Fix set_max_file_descriptors() to set by default the max open file
9085 limit to the current limit when setrlimit() fails. Fixes bug
9086 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
9088 o Minor bugfixes (portability):
9089 - Try harder to normalize the exit status of the Tor process to the
9090 standard-provided range. Fixes bug 16975; bugfix on every version
9092 - Check correctly for Windows socket errors in the workqueue
9093 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
9094 - Fix the behavior of crypto_rand_time_range() when told to consider
9095 times before 1970. (These times were possible when running in a
9096 simulated network environment where time()'s output starts at
9097 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
9098 - Restore correct operation of TLS client-cipher detection on
9099 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
9101 o Minor bugfixes (relay):
9102 - Ensure that worker threads actually exit when a fatal error or
9103 shutdown is indicated. This fix doesn't currently affect the
9104 behavior of Tor, because Tor workers never indicates fatal error
9105 or shutdown except in the unit tests. Fixes bug 16868; bugfix
9107 - Unblock threads before releasing the work queue mutex to ensure
9108 predictable scheduling behavior. Fixes bug 16644; bugfix
9111 o Code simplification and refactoring:
9112 - Change the function that's called when we need to retry all
9113 downloads so that it only reschedules the downloads to happen
9114 immediately, rather than launching them all at once itself. This
9115 further simplifies Tor's callgraph.
9116 - Move some format-parsing functions out of crypto.c and
9117 crypto_curve25519.c into crypto_format.c and/or util_format.c.
9118 - Move the client-only parts of init_keys() into a separate
9119 function. Closes ticket 16763.
9120 - Simplify the microdesc_free() implementation so that it no longer
9121 appears (to code analysis tools) to potentially invoke a huge
9122 suite of other microdesc functions.
9123 - Simply the control graph further by deferring the inner body of
9124 directory_all_unreachable() into a callback. Closes ticket 16762.
9125 - Treat the loss of an owning controller as equivalent to a SIGTERM
9126 signal. This removes a tiny amount of duplicated code, and
9127 simplifies our callgraph. Closes ticket 16788.
9128 - When generating an event to send to the controller, we no longer
9129 put the event over the network immediately. Instead, we queue
9130 these events, and use a Libevent callback to deliver them. This
9131 change simplifies Tor's callgraph by reducing the number of
9132 functions from which all other Tor functions are reachable. Closes
9134 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
9135 that try to scan or compile every file on Unix won't decide that
9137 - Remove the unused "nulterminate" argument from buf_pullup().
9140 - Recommend a 40 GB example AccountingMax in torrc.sample rather
9141 than a 4 GB max. Closes ticket 16742.
9142 - Include the TUNING document in our source tarball. It is referred
9143 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
9147 - The internal pure-C tor-fw-helper tool is now removed from the Tor
9148 distribution, in favor of the pure-Go clone available from
9149 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
9150 used by the C tor-fw-helper are not, in our opinion, very
9151 confidence- inspiring in their secure-programming techniques.
9152 Closes ticket 13338.
9153 - Remove the code that would try to aggressively flush controller
9154 connections while writing to them. This code was introduced in
9155 0.1.2.7-alpha, in order to keep output buffers from exceeding
9156 their limits. But there is no longer a maximum output buffer size,
9157 and flushing data in this way caused some undesirable recursions
9158 in our call graph. Closes ticket 16480.
9161 - Make "bridges+hs" the default test network. This tests almost all
9162 tor functionality during make test-network, while allowing tests
9163 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
9164 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
9165 (chutney). Patches by "teor".
9166 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
9167 by-side in the same parent directory. Closes ticket 16903. Patch
9169 - Use environment variables rather than autoconf substitutions to
9170 send variables from the build system to the test scripts. This
9171 change should be easier to maintain, and cause 'make distcheck' to
9172 work better than before. Fixes bug 17148.
9173 - Add a new set of callgraph analysis scripts that use clang to
9174 produce a list of which Tor functions are reachable from which
9175 other Tor functions. We're planning to use these to help simplify
9176 our code structure by identifying illogical dependencies.
9177 - Add new 'test-full' and 'test-full-online' targets to run all
9178 tests, including integration tests with stem and chutney.
9179 - Make the test-workqueue test work on Windows by initializing the
9180 network before we begin.
9181 - New make target (make test-network-all) to run multiple applicable
9182 chutney test cases. Patch from Teor; closes 16953.
9183 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
9184 functions in dns.c. Implements a portion of ticket 16831.
9185 - When building Tor with testing coverage enabled, run Chutney tests
9186 (if any) using the 'tor-cov' coverage binary.
9187 - When running test-network or test-stem, check for the absence of
9188 stem/chutney before doing any build operations.
9191 Changes in version 0.2.7.2-alpha - 2015-07-27
9192 This, the second alpha in the Tor 0.2.7 series, has a number of new
9193 features, including a way to manually pick the number of introduction
9194 points for hidden services, and the much stronger Ed25519 signing key
9195 algorithm for regular Tor relays (including support for encrypted
9196 offline identity keys in the new algorithm).
9198 Support for Ed25519 on relays is currently limited to signing router
9199 descriptors; later alphas in this series will extend Ed25519 key
9200 support to more parts of the Tor protocol.
9202 o Major features (Ed25519 identity keys, Proposal 220):
9203 - All relays now maintain a stronger identity key, using the Ed25519
9204 elliptic curve signature format. This master key is designed so
9205 that it can be kept offline. Relays also generate an online
9206 signing key, and a set of other Ed25519 keys and certificates.
9207 These are all automatically regenerated and rotated as needed.
9208 Implements part of ticket 12498.
9209 - Directory authorities now vote on Ed25519 identity keys along with
9210 RSA1024 keys. Implements part of ticket 12498.
9211 - Directory authorities track which Ed25519 identity keys have been
9212 used with which RSA1024 identity keys, and do not allow them to
9213 vary freely. Implements part of ticket 12498.
9214 - Microdescriptors now include Ed25519 identity keys. Implements
9215 part of ticket 12498.
9216 - Add support for offline encrypted Ed25519 master keys. To use this
9217 feature on your tor relay, run "tor --keygen" to make a new master
9218 key (or to make a new signing key if you already have a master
9219 key). Closes ticket 13642.
9221 o Major features (Hidden services):
9222 - Add the torrc option HiddenServiceNumIntroductionPoints, to
9223 specify a fixed number of introduction points. Its maximum value
9224 is 10 and default is 3. Using this option can increase a hidden
9225 service's reliability under load, at the cost of making it more
9226 visible that the hidden service is facing extra load. Closes
9228 - Remove the adaptive algorithm for choosing the number of
9229 introduction points, which used to change the number of
9230 introduction points (poorly) depending on the number of
9231 connections the HS sees. Closes ticket 4862.
9233 o Major features (onion key cross-certification):
9234 - Relay descriptors now include signatures of their own identity
9235 keys, made using the TAP and ntor onion keys. These signatures
9236 allow relays to prove ownership of their own onion keys. Because
9237 of this change, microdescriptors will no longer need to include
9238 RSA identity keys. Implements proposal 228; closes ticket 12499.
9240 o Major features (performance):
9241 - Improve the runtime speed of Ed25519 operations by using the
9242 public-domain Ed25519-donna by Andrew M. ("floodyberry").
9243 Implements ticket 16467.
9244 - Improve the runtime speed of the ntor handshake by using an
9245 optimized curve25519 basepoint scalarmult implementation from the
9246 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
9247 ideas by Adam Langley. Implements ticket 9663.
9249 o Major bugfixes (client-side privacy, also in 0.2.6.9):
9250 - Properly separate out each SOCKSPort when applying stream
9251 isolation. The error occurred because each port's session group
9252 was being overwritten by a default value when the listener
9253 connection was initialized. Fixes bug 16247; bugfix on
9254 0.2.6.3-alpha. Patch by "jojelino".
9256 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
9257 - Stop refusing to store updated hidden service descriptors on a
9258 client. This reverts commit 9407040c59218 (which indeed fixed bug
9259 14219, but introduced a major hidden service reachability
9260 regression detailed in bug 16381). This is a temporary fix since
9261 we can live with the minor issue in bug 14219 (it just results in
9262 some load on the network) but the regression of 16381 is too much
9263 of a setback. First-round fix for bug 16381; bugfix
9266 o Major bugfixes (hidden services):
9267 - When cannibalizing a circuit for an introduction point, always
9268 extend to the chosen exit node (creating a 4 hop circuit).
9269 Previously Tor would use the current circuit exit node, which
9270 changed the original choice of introduction point, and could cause
9271 the hidden service to skip excluded introduction points or
9272 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
9275 o Major bugfixes (open file limit):
9276 - The open file limit wasn't checked before calling
9277 tor_accept_socket_nonblocking(), which would make Tor exceed the
9278 limit. Now, before opening a new socket, Tor validates the open
9279 file limit just before, and if the max has been reached, return an
9280 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
9282 o Major bugfixes (stability, also in 0.2.6.10):
9283 - Stop crashing with an assertion failure when parsing certain kinds
9284 of malformed or truncated microdescriptors. Fixes bug 16400;
9285 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
9286 by "cypherpunks_backup".
9287 - Stop random client-side assertion failures that could occur when
9288 connecting to a busy hidden service, or connecting to a hidden
9289 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
9292 o Minor features (directory authorities, security, also in 0.2.6.9):
9293 - The HSDir flag given by authorities now requires the Stable flag.
9294 For the current network, this results in going from 2887 to 2806
9295 HSDirs. Also, it makes it harder for an attacker to launch a sybil
9296 attack by raising the effort for a relay to become Stable to
9297 require at the very least 7 days, while maintaining the 96 hours
9298 uptime requirement for HSDir. Implements ticket 8243.
9300 o Minor features (client):
9301 - Relax the validation of hostnames in SOCKS5 requests, allowing the
9302 character '_' to appear, in order to cope with domains observed in
9303 the wild that are serving non-RFC compliant records. Resolves
9305 - Relax the validation done to hostnames in SOCKS5 requests, and
9306 allow a single trailing '.' to cope with clients that pass FQDNs
9307 using that syntax to explicitly indicate that the domain name is
9308 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
9309 - Add GroupWritable and WorldWritable options to unix-socket based
9310 SocksPort and ControlPort options. These options apply to a single
9311 socket, and override {Control,Socks}SocketsGroupWritable. Closes
9314 o Minor features (control protocol):
9315 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
9316 the control protocol. Resolves ticket 15358.
9318 o Minor features (directory authorities):
9319 - Directory authorities no longer vote against the "Fast", "Stable",
9320 and "HSDir" flags just because they were going to vote against
9321 "Running": if the consensus turns out to be that the router was
9322 running, then the authority's vote should count. Patch from Peter
9323 Retzlaff; closes issue 8712.
9325 o Minor features (geoip, also in 0.2.6.10):
9326 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
9327 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
9329 o Minor features (hidden services):
9330 - Add the new options "HiddenServiceMaxStreams" and
9331 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
9332 limit the maximum number of simultaneous streams per circuit, and
9333 optionally tear down the circuit when the limit is exceeded. Part
9336 o Minor features (portability):
9337 - Use C99 variadic macros when the compiler is not GCC. This avoids
9338 failing compilations on MSVC, and fixes a log-file-based race
9339 condition in our old workarounds. Original patch from Gisle Vanem.
9341 o Minor bugfixes (compilation, also in 0.2.6.9):
9342 - Build with --enable-systemd correctly when libsystemd is
9343 installed, but systemd is not. Fixes bug 16164; bugfix on
9344 0.2.6.3-alpha. Patch from Peter Palfrader.
9346 o Minor bugfixes (controller):
9347 - Add the descriptor ID in each HS_DESC control event. It was
9348 missing, but specified in control-spec.txt. Fixes bug 15881;
9349 bugfix on 0.2.5.2-alpha.
9351 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
9352 - Check for failures from crypto_early_init, and refuse to continue.
9353 A previous typo meant that we could keep going with an
9354 uninitialized crypto library, and would have OpenSSL initialize
9355 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9356 when implementing ticket 4900. Patch by "teor".
9358 o Minor bugfixes (hidden services):
9359 - Fix a crash when reloading configuration while at least one
9360 configured and one ephemeral hidden service exists. Fixes bug
9361 16060; bugfix on 0.2.7.1-alpha.
9362 - Avoid crashing with a double-free bug when we create an ephemeral
9363 hidden service but adding it fails for some reason. Fixes bug
9364 16228; bugfix on 0.2.7.1-alpha.
9366 o Minor bugfixes (Linux seccomp2 sandbox):
9367 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
9368 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
9370 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
9371 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
9372 these when eventfd2() support is missing. Fixes bug 16363; bugfix
9373 on 0.2.6.3-alpha. Patch from "teor".
9375 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
9376 - Fix sandboxing to work when running as a relay, by allowing the
9377 renaming of secret_id_key, and allowing the eventfd2 and futex
9378 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
9380 - Allow systemd connections to work with the Linux seccomp2 sandbox
9381 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
9384 o Minor bugfixes (relay):
9385 - Fix a rarely-encountered memory leak when failing to initialize
9386 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
9389 o Minor bugfixes (systemd):
9390 - Fix an accidental formatting error that broke the systemd
9391 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
9392 - Tor's systemd unit file no longer contains extraneous spaces.
9393 These spaces would sometimes confuse tools like deb-systemd-
9394 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
9396 o Minor bugfixes (tests):
9397 - Use the configured Python executable when running test-stem-full.
9398 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
9400 o Minor bugfixes (tests, also in 0.2.6.9):
9401 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
9402 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
9404 o Minor bugfixes (threads, comments):
9405 - Always initialize return value in compute_desc_id in rendcommon.c
9406 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
9407 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
9408 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
9409 - Remove undefined directive-in-macro in test_util_writepid clang
9410 3.7 complains that using a preprocessor directive inside a macro
9411 invocation in test_util_writepid in test_util.c is undefined.
9412 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
9414 o Code simplification and refactoring:
9415 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
9416 to ensure they remain consistent and visible everywhere.
9417 - Remove some vestigial workarounds for the MSVC6 compiler. We
9418 haven't supported that in ages.
9419 - The link authentication code has been refactored for better
9420 testability and reliability. It now uses code generated with the
9421 "trunnel" binary encoding generator, to reduce the risk of bugs
9422 due to programmer error. Done as part of ticket 12498.
9425 - Include a specific and (hopefully) accurate documentation of the
9426 torrc file's meta-format in doc/torrc_format.txt. This is mainly
9427 of interest to people writing programs to parse or generate torrc
9428 files. This document is not a commitment to long-term
9429 compatibility; some aspects of the current format are a bit
9430 ridiculous. Closes ticket 2325.
9433 - Tor no longer supports copies of OpenSSL that are missing support
9434 for Elliptic Curve Cryptography. (We began using ECC when
9435 available in 0.2.4.8-alpha, for more safe and efficient key
9436 negotiation.) In particular, support for at least one of P256 or
9437 P224 is now required, with manual configuration needed if only
9438 P224 is available. Resolves ticket 16140.
9439 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
9440 on an operating system that has not upgraded to OpenSSL 1.0 or
9441 later, and you compile Tor from source, you will need to install a
9442 more recent OpenSSL to link Tor against.) These versions of
9443 OpenSSL are still supported by the OpenSSL, but the numerous
9444 cryptographic improvements in later OpenSSL releases makes them a
9445 clear choice. Resolves ticket 16034.
9446 - Remove the HidServDirectoryV2 option. Now all relays offer to
9447 store hidden service descriptors. Related to 16543.
9448 - Remove the VoteOnHidServDirectoriesV2 option, since all
9449 authorities have long set it to 1. Closes ticket 16543.
9452 - Document use of coverity, clang static analyzer, and clang dynamic
9453 undefined behavior and address sanitizers in doc/HACKING. Include
9454 detailed usage instructions in the blacklist. Patch by "teor".
9455 Closes ticket 15817.
9456 - The link authentication protocol code now has extensive tests.
9457 - The relay descriptor signature testing code now has
9459 - The test_workqueue program now runs faster, and is enabled by
9460 default as a part of "make check".
9461 - Now that OpenSSL has its own scrypt implementation, add an unit
9462 test that checks for interoperability between libscrypt_scrypt()
9463 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
9464 and rely on EVP_PBE_scrypt() whenever possible. Resolves
9468 Changes in version 0.2.6.10 - 2015-07-12
9469 Tor version 0.2.6.10 fixes some significant stability and hidden
9470 service client bugs, bulletproofs the cryptography init process, and
9471 fixes a bug when using the sandbox code with some older versions of
9472 Linux. Everyone running an older version, especially an older version
9473 of 0.2.6, should upgrade.
9475 o Major bugfixes (hidden service clients, stability):
9476 - Stop refusing to store updated hidden service descriptors on a
9477 client. This reverts commit 9407040c59218 (which indeed fixed bug
9478 14219, but introduced a major hidden service reachability
9479 regression detailed in bug 16381). This is a temporary fix since
9480 we can live with the minor issue in bug 14219 (it just results in
9481 some load on the network) but the regression of 16381 is too much
9482 of a setback. First-round fix for bug 16381; bugfix
9485 o Major bugfixes (stability):
9486 - Stop crashing with an assertion failure when parsing certain kinds
9487 of malformed or truncated microdescriptors. Fixes bug 16400;
9488 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
9489 by "cypherpunks_backup".
9490 - Stop random client-side assertion failures that could occur when
9491 connecting to a busy hidden service, or connecting to a hidden
9492 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
9495 o Minor features (geoip):
9496 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
9497 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
9499 o Minor bugfixes (crypto error-handling):
9500 - Check for failures from crypto_early_init, and refuse to continue.
9501 A previous typo meant that we could keep going with an
9502 uninitialized crypto library, and would have OpenSSL initialize
9503 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9504 when implementing ticket 4900. Patch by "teor".
9506 o Minor bugfixes (Linux seccomp2 sandbox):
9507 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
9508 these when eventfd2() support is missing. Fixes bug 16363; bugfix
9509 on 0.2.6.3-alpha. Patch from "teor".
9512 Changes in version 0.2.6.9 - 2015-06-11
9513 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
9514 requirements for receiving an HSDir flag, and addresses some other small
9515 bugs in the systemd and sandbox code. Clients using circuit isolation
9516 should upgrade; all directory authorities should upgrade.
9518 o Major bugfixes (client-side privacy):
9519 - Properly separate out each SOCKSPort when applying stream
9520 isolation. The error occurred because each port's session group was
9521 being overwritten by a default value when the listener connection
9522 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
9525 o Minor feature (directory authorities, security):
9526 - The HSDir flag given by authorities now requires the Stable flag.
9527 For the current network, this results in going from 2887 to 2806
9528 HSDirs. Also, it makes it harder for an attacker to launch a sybil
9529 attack by raising the effort for a relay to become Stable which
9530 takes at the very least 7 days to do so and by keeping the 96
9531 hours uptime requirement for HSDir. Implements ticket 8243.
9533 o Minor bugfixes (compilation):
9534 - Build with --enable-systemd correctly when libsystemd is
9535 installed, but systemd is not. Fixes bug 16164; bugfix on
9536 0.2.6.3-alpha. Patch from Peter Palfrader.
9538 o Minor bugfixes (Linux seccomp2 sandbox):
9539 - Fix sandboxing to work when running as a relaymby renaming of
9540 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
9541 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
9542 - Allow systemd connections to work with the Linux seccomp2 sandbox
9543 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
9546 o Minor bugfixes (tests):
9547 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
9548 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
9551 Changes in version 0.2.6.8 - 2015-05-21
9552 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
9553 fixes an authority-side bug in assigning the HSDir flag. All directory
9554 authorities should upgrade.
9556 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
9557 - Revert commit that made directory authorities assign the HSDir
9558 flag to relays without a DirPort; this was bad because such relays
9559 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
9562 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9563 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9564 a client authorized hidden service. Fixes bug 15823; bugfix
9567 o Minor features (geoip):
9568 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
9569 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
9573 Changes in version 0.2.7.1-alpha - 2015-05-12
9574 Tor 0.2.7.1-alpha is the first alpha release in its series. It
9575 includes numerous small features and bugfixes against previous Tor
9576 versions, and numerous small infrastructure improvements. The most
9577 notable features are several new ways for controllers to interact with
9578 the hidden services subsystem.
9580 o New system requirements:
9581 - Tor no longer includes workarounds to support Libevent versions
9582 before 1.3e. Libevent 2.0 or later is recommended. Closes
9585 o Major features (controller):
9586 - Add the ADD_ONION and DEL_ONION commands that allow the creation
9587 and management of hidden services via the controller. Closes
9589 - New "GETINFO onions/current" and "GETINFO onions/detached"
9590 commands to get information about hidden services created via the
9591 controller. Part of ticket 6411.
9592 - New HSFETCH command to launch a request for a hidden service
9593 descriptor. Closes ticket 14847.
9594 - New HSPOST command to upload a hidden service descriptor. Closes
9595 ticket 3523. Patch by "DonnchaC".
9597 o Major bugfixes (hidden services):
9598 - Revert commit that made directory authorities assign the HSDir
9599 flag to relays without a DirPort; this was bad because such relays
9600 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
9603 o Minor features (clock-jump tolerance):
9604 - Recover better when our clock jumps back many hours, like might
9605 happen for Tails or Whonix users who start with a very wrong
9606 hardware clock, use Tor to discover a more accurate time, and then
9607 fix their clock. Resolves part of ticket 8766.
9609 o Minor features (command-line interface):
9610 - Make --hash-password imply --hush to prevent unnecessary noise.
9611 Closes ticket 15542. Patch from "cypherpunks".
9612 - Print a warning whenever we find a relative file path being used
9613 as torrc option. Resolves issue 14018.
9615 o Minor features (controller):
9616 - Add DirAuthority lines for default directory authorities to the
9617 output of the "GETINFO config/defaults" command if not already
9618 present. Implements ticket 14840.
9619 - Controllers can now use "GETINFO hs/client/desc/id/..." to
9620 retrieve items from the client's hidden service descriptor cache.
9621 Closes ticket 14845.
9622 - Implement a new controller command "GETINFO status/fresh-relay-
9623 descs" to fetch a descriptor/extrainfo pair that was generated on
9624 demand just for the controller's use. Implements ticket 14784.
9626 o Minor features (DoS-resistance):
9627 - Make it harder for attackers to overload hidden services with
9628 introductions, by blocking multiple introduction requests on the
9629 same circuit. Resolves ticket 15515.
9631 o Minor features (geoip):
9632 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
9633 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
9636 o Minor features (HS popularity countermeasure):
9637 - To avoid leaking HS popularity, don't cycle the introduction point
9638 when we've handled a fixed number of INTRODUCE2 cells but instead
9639 cycle it when a random number of introductions is reached, thus
9640 making it more difficult for an attacker to find out the amount of
9641 clients that have used the introduction point for a specific HS.
9642 Closes ticket 15745.
9644 o Minor features (logging):
9645 - Include the Tor version in all LD_BUG log messages, since people
9646 tend to cut and paste those into the bugtracker. Implements
9649 o Minor features (pluggable transports):
9650 - When launching managed pluggable transports on Linux systems,
9651 attempt to have the kernel deliver a SIGTERM on tor exit if the
9652 pluggable transport process is still running. Resolves
9654 - When launching managed pluggable transports, setup a valid open
9655 stdin in the child process that can be used to detect if tor has
9656 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
9657 can be used by implementations to detect this new behavior.
9658 Resolves ticket 15435.
9660 o Minor features (testing):
9661 - Add a test to verify that the compiler does not eliminate our
9662 memwipe() implementation. Closes ticket 15377.
9663 - Add make rule `check-changes` to verify the format of changes
9664 files. Closes ticket 15180.
9665 - Add unit tests for control_event_is_interesting(). Add a compile-
9666 time check that the number of events doesn't exceed the capacity
9667 of control_event_t.event_mask. Closes ticket 15431, checks for
9668 bugs similar to 13085. Patch by "teor".
9669 - Command-line argument tests moved to Stem. Resolves ticket 14806.
9670 - Integrate the ntor, backtrace, and zero-length keys tests into the
9671 automake test suite. Closes ticket 15344.
9672 - Remove assertions during builds to determine Tor's test coverage.
9673 We don't want to trigger these even in assertions, so including
9674 them artificially makes our branch coverage look worse than it is.
9675 This patch provides the new test-stem-full and coverage-html-full
9676 configure options. Implements ticket 15400.
9678 o Minor bugfixes (build):
9679 - Improve out-of-tree builds by making non-standard rules work and
9680 clean up additional files and directories. Fixes bug 15053; bugfix
9683 o Minor bugfixes (command-line interface):
9684 - When "--quiet" is provided along with "--validate-config", do not
9685 write anything to stdout on success. Fixes bug 14994; bugfix
9687 - When complaining about bad arguments to "--dump-config", use
9690 o Minor bugfixes (configuration, unit tests):
9691 - Only add the default fallback directories when the DirAuthorities,
9692 AlternateDirAuthority, and FallbackDir directory config options
9693 are set to their defaults. The default fallback directory list is
9694 currently empty, this fix will only change tor's behavior when it
9695 has default fallback directories. Includes unit tests for
9696 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
9697 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
9699 o Minor bugfixes (correctness):
9700 - For correctness, avoid modifying a constant string in
9701 handle_control_postdescriptor. Fixes bug 15546; bugfix
9703 - Remove side-effects from tor_assert() calls. This was harmless,
9704 because we never disable assertions, but it is bad style and
9705 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
9708 o Minor bugfixes (hidden service):
9709 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9710 a client authorized hidden service. Fixes bug 15823; bugfix
9712 - Remove an extraneous newline character from the end of hidden
9713 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
9715 o Minor bugfixes (interface):
9716 - Print usage information for --dump-config when it is used without
9717 an argument. Also, fix the error message to use different wording
9718 and add newline at the end. Fixes bug 15541; bugfix
9721 o Minor bugfixes (logs):
9722 - When building Tor under Clang, do not include an extra set of
9723 parentheses in log messages that include function names. Fixes bug
9724 15269; bugfix on every released version of Tor when compiled with
9725 recent enough Clang.
9727 o Minor bugfixes (network):
9728 - When attempting to use fallback technique for network interface
9729 lookup, disregard loopback and multicast addresses since they are
9730 unsuitable for public communications.
9732 o Minor bugfixes (statistics):
9733 - Disregard the ConnDirectionStatistics torrc options when Tor is
9734 not a relay since in that mode of operation no sensible data is
9735 being collected and because Tor might run into measurement hiccups
9736 when running as a client for some time, then becoming a relay.
9737 Fixes bug 15604; bugfix on 0.2.2.35.
9739 o Minor bugfixes (test networks):
9740 - When self-testing reachability, use ExtendAllowPrivateAddresses to
9741 determine if local/private addresses imply reachability. The
9742 previous fix used TestingTorNetwork, which implies
9743 ExtendAllowPrivateAddresses, but this excluded rare configurations
9744 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
9745 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
9746 issue discovered by CJ Ess.
9748 o Minor bugfixes (testing):
9749 - Check for matching value in server response in ntor_ref.py. Fixes
9750 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
9752 - Set the severity correctly when testing
9753 get_interface_addresses_ifaddrs() and
9754 get_interface_addresses_win32(), so that the tests fail gracefully
9755 instead of triggering an assertion. Fixes bug 15759; bugfix on
9756 0.2.6.3-alpha. Reported by Nicolas Derive.
9758 o Code simplification and refactoring:
9759 - Move the hacky fallback code out of get_interface_address6() into
9760 separate function and get it covered with unit-tests. Resolves
9762 - Refactor hidden service client-side cache lookup to intelligently
9763 report its various failure cases, and disentangle failure cases
9764 involving a lack of introduction points. Closes ticket 14391.
9765 - Use our own Base64 encoder instead of OpenSSL's, to allow more
9766 control over the output. Part of ticket 15652.
9769 - Improve the descriptions of statistics-related torrc options in
9770 the manpage to describe rationale and possible uses cases. Fixes
9772 - Improve the layout and formatting of ./configure --help messages.
9773 Closes ticket 15024. Patch from "cypherpunks".
9774 - Standardize on the term "server descriptor" in the manual page.
9775 Previously, we had used "router descriptor", "server descriptor",
9776 and "relay descriptor" interchangeably. Part of ticket 14987.
9779 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
9780 and always use the internal Base64 decoder. The internal decoder
9781 has been part of tor since 0.2.0.10-alpha, and no one should
9782 be using the OpenSSL one. Part of ticket 15652.
9783 - Remove the 'tor_strclear()' function; use memwipe() instead.
9784 Closes ticket 14922.
9787 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
9788 fingerprinting we now recommend pluggable transports; for forward-
9789 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
9790 - Remove the undocumented "--digests" command-line option. It
9791 complicated our build process, caused subtle build issues on
9792 multiple platforms, and is now redundant since we started
9793 including git version identifiers. Closes ticket 14742.
9794 - Tor no longer contains checks for ancient directory cache versions
9795 that didn't know about microdescriptors.
9796 - Tor no longer contains workarounds for stat files generated by
9797 super-old versions of Tor that didn't choose guards sensibly.
9800 Changes in version 0.2.4.27 - 2015-04-06
9801 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
9802 could be used by an attacker to crash hidden services, or crash clients
9803 visiting hidden services. Hidden services should upgrade as soon as
9804 possible; clients should upgrade whenever packages become available.
9806 This release also backports a simple improvement to make hidden
9807 services a bit less vulnerable to denial-of-service attacks.
9809 o Major bugfixes (security, hidden service):
9810 - Fix an issue that would allow a malicious client to trigger an
9811 assertion failure and halt a hidden service. Fixes bug 15600;
9812 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
9813 - Fix a bug that could cause a client to crash with an assertion
9814 failure when parsing a malformed hidden service descriptor. Fixes
9815 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
9817 o Minor features (DoS-resistance, hidden service):
9818 - Introduction points no longer allow multiple INTRODUCE1 cells to
9819 arrive on the same circuit. This should make it more expensive for
9820 attackers to overwhelm hidden services with introductions.
9821 Resolves ticket 15515.
9824 Changes in version 0.2.5.12 - 2015-04-06
9825 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
9826 could be used by an attacker to crash hidden services, or crash clients
9827 visiting hidden services. Hidden services should upgrade as soon as
9828 possible; clients should upgrade whenever packages become available.
9830 This release also backports a simple improvement to make hidden
9831 services a bit less vulnerable to denial-of-service attacks.
9833 o Major bugfixes (security, hidden service):
9834 - Fix an issue that would allow a malicious client to trigger an
9835 assertion failure and halt a hidden service. Fixes bug 15600;
9836 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
9837 - Fix a bug that could cause a client to crash with an assertion
9838 failure when parsing a malformed hidden service descriptor. Fixes
9839 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
9841 o Minor features (DoS-resistance, hidden service):
9842 - Introduction points no longer allow multiple INTRODUCE1 cells to
9843 arrive on the same circuit. This should make it more expensive for
9844 attackers to overwhelm hidden services with introductions.
9845 Resolves ticket 15515.
9848 Changes in version 0.2.6.7 - 2015-04-06
9849 Tor 0.2.6.7 fixes two security issues that could be used by an
9850 attacker to crash hidden services, or crash clients visiting hidden
9851 services. Hidden services should upgrade as soon as possible; clients
9852 should upgrade whenever packages become available.
9854 This release also contains two simple improvements to make hidden
9855 services a bit less vulnerable to denial-of-service attacks.
9857 o Major bugfixes (security, hidden service):
9858 - Fix an issue that would allow a malicious client to trigger an
9859 assertion failure and halt a hidden service. Fixes bug 15600;
9860 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
9861 - Fix a bug that could cause a client to crash with an assertion
9862 failure when parsing a malformed hidden service descriptor. Fixes
9863 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
9865 o Minor features (DoS-resistance, hidden service):
9866 - Introduction points no longer allow multiple INTRODUCE1 cells to
9867 arrive on the same circuit. This should make it more expensive for
9868 attackers to overwhelm hidden services with introductions.
9869 Resolves ticket 15515.
9870 - Decrease the amount of reattempts that a hidden service performs
9871 when its rendezvous circuits fail. This reduces the computational
9872 cost for running a hidden service under heavy load. Resolves
9876 Changes in version 0.2.6.6 - 2015-03-24
9877 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
9879 It adds numerous safety, security, correctness, and performance
9880 improvements. Client programs can be configured to use more kinds of
9881 sockets, AutomapHosts works better, the multithreading backend is
9882 improved, cell transmission is refactored, test coverage is much
9883 higher, more denial-of-service attacks are handled, guard selection is
9884 improved to handle long-term guards better, pluggable transports
9885 should work a bit better, and some annoying hidden service performance
9886 bugs should be addressed.
9888 o Minor bugfixes (portability):
9889 - Use the correct datatype in the SipHash-2-4 function to prevent
9890 compilers from assuming any sort of alignment. Fixes bug 15436;
9891 bugfix on 0.2.5.3-alpha.
9893 Changes in version 0.2.6.5-rc - 2015-03-18
9894 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
9895 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
9897 o Major bugfixes (client):
9898 - Avoid crashing when making certain configuration option changes on
9899 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
9902 o Major bugfixes (pluggable transports):
9903 - Initialize the extended OR Port authentication cookie before
9904 launching pluggable transports. This prevents a race condition
9905 that occurred when server-side pluggable transports would cache the
9906 authentication cookie before it has been (re)generated. Fixes bug
9907 15240; bugfix on 0.2.5.1-alpha.
9909 o Major bugfixes (portability):
9910 - Do not crash on startup when running on Solaris. Fixes a bug
9911 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
9914 o Minor features (heartbeat):
9915 - On relays, report how many connections we negotiated using each
9916 version of the Tor link protocols. This information will let us
9917 know if removing support for very old versions of the Tor
9918 protocols is harming the network. Closes ticket 15212.
9920 o Code simplification and refactoring:
9921 - Refactor main loop to extract the 'loop' part. This makes it
9922 easier to run Tor under Shadow. Closes ticket 15176.
9925 Changes in version 0.2.5.11 - 2015-03-17
9926 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
9928 It backports several bugfixes from the 0.2.6 branch, including a
9929 couple of medium-level security fixes for relays and exit nodes.
9930 It also updates the list of directory authorities.
9932 o Directory authority changes:
9933 - Remove turtles as a directory authority.
9934 - Add longclaw as a new (v3) directory authority. This implements
9935 ticket 13296. This keeps the directory authority count at 9.
9936 - The directory authority Faravahar has a new IP address. This
9937 closes ticket 14487.
9939 o Major bugfixes (crash, OSX, security):
9940 - Fix a remote denial-of-service opportunity caused by a bug in
9941 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
9944 o Major bugfixes (relay, stability, possible security):
9945 - Fix a bug that could lead to a relay crashing with an assertion
9946 failure if a buffer of exactly the wrong layout was passed to
9947 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
9948 0.2.0.10-alpha. Patch from 'cypherpunks'.
9949 - Do not assert if the 'data' pointer on a buffer is advanced to the
9950 very end of the buffer; log a BUG message instead. Only assert if
9951 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
9953 o Major bugfixes (exit node stability):
9954 - Fix an assertion failure that could occur under high DNS load.
9955 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
9956 diagnosed and fixed by "cypherpunks".
9958 o Major bugfixes (Linux seccomp2 sandbox):
9959 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
9960 crash during attempts to call wait4. Fixes bug 15088; bugfix on
9961 0.2.5.1-alpha. Patch from "sanic".
9963 o Minor features (controller):
9964 - New "GETINFO bw-event-cache" to get information about recent
9965 bandwidth events. Closes ticket 14128. Useful for controllers to
9966 get recent bandwidth history after the fix for ticket 13988.
9968 o Minor features (geoip):
9969 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
9970 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
9973 o Minor bugfixes (client, automapping):
9974 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
9975 no value follows the option. Fixes bug 14142; bugfix on
9976 0.2.4.7-alpha. Patch by "teor".
9977 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
9978 14195; bugfix on 0.1.0.1-rc.
9980 o Minor bugfixes (compilation):
9981 - Build without warnings with the stock OpenSSL srtp.h header, which
9982 has a duplicate declaration of SSL_get_selected_srtp_profile().
9983 Fixes bug 14220; this is OpenSSL's bug, not ours.
9985 o Minor bugfixes (directory authority):
9986 - Allow directory authorities to fetch more data from one another if
9987 they find themselves missing lots of votes. Previously, they had
9988 been bumping against the 10 MB queued data limit. Fixes bug 14261;
9989 bugfix on 0.1.2.5-alpha.
9990 - Enlarge the buffer to read bwauth generated files to avoid an
9991 issue when parsing the file in dirserv_read_measured_bandwidths().
9992 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
9994 o Minor bugfixes (statistics):
9995 - Increase period over which bandwidth observations are aggregated
9996 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
9998 o Minor bugfixes (preventative security, C safety):
9999 - When reading a hexadecimal, base-32, or base-64 encoded value from
10000 a string, always overwrite the whole output buffer. This prevents
10001 some bugs where we would look at (but fortunately, not reveal)
10002 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
10006 Changes in version 0.2.4.26 - 2015-03-17
10007 Tor 0.2.4.26 includes an updated list of directory authorities. It
10008 also backports a couple of stability and security bugfixes from 0.2.5
10011 o Directory authority changes:
10012 - Remove turtles as a directory authority.
10013 - Add longclaw as a new (v3) directory authority. This implements
10014 ticket 13296. This keeps the directory authority count at 9.
10015 - The directory authority Faravahar has a new IP address. This
10016 closes ticket 14487.
10018 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
10019 - Fix an assertion failure that could occur under high DNS load.
10020 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
10021 diagnosed and fixed by "cypherpunks".
10023 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
10024 - Fix a bug that could lead to a relay crashing with an assertion
10025 failure if a buffer of exactly the wrong layout was passed to
10026 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
10027 0.2.0.10-alpha. Patch from 'cypherpunks'.
10028 - Do not assert if the 'data' pointer on a buffer is advanced to the
10029 very end of the buffer; log a BUG message instead. Only assert if
10030 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
10032 o Minor features (geoip):
10033 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
10034 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
10037 Changes in version 0.2.6.4-rc - 2015-03-09
10038 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
10039 attacker might be able to use in order to crash certain Tor
10040 directories. It also resolves some minor issues left over from, or
10041 introduced in, Tor 0.2.6.3-alpha or earlier.
10043 o Major bugfixes (crash, OSX, security):
10044 - Fix a remote denial-of-service opportunity caused by a bug in
10045 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
10048 o Major bugfixes (relay, stability, possible security):
10049 - Fix a bug that could lead to a relay crashing with an assertion
10050 failure if a buffer of exactly the wrong layout is passed to
10051 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
10052 0.2.0.10-alpha. Patch from "cypherpunks".
10053 - Do not assert if the 'data' pointer on a buffer is advanced to the
10054 very end of the buffer; log a BUG message instead. Only assert if
10055 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
10057 o Major bugfixes (FreeBSD IPFW transparent proxy):
10058 - Fix address detection with FreeBSD transparent proxies, when
10059 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
10062 o Major bugfixes (Linux seccomp2 sandbox):
10063 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
10064 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
10066 - Allow AF_UNIX hidden services to be used with the seccomp2
10067 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
10068 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
10069 crash during attempts to call wait4. Fixes bug 15088; bugfix on
10070 0.2.5.1-alpha. Patch from "sanic".
10072 o Minor features (controller):
10073 - Messages about problems in the bootstrap process now include
10074 information about the server we were trying to connect to when we
10075 noticed the problem. Closes ticket 15006.
10077 o Minor features (geoip):
10078 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
10079 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
10082 o Minor features (logs):
10083 - Quiet some log messages in the heartbeat and at startup. Closes
10086 o Minor bugfixes (certificate handling):
10087 - If an authority operator accidentally makes a signing certificate
10088 with a future publication time, do not discard its real signing
10089 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
10090 - Remove any old authority certificates that have been superseded
10091 for at least two days. Previously, we would keep superseded
10092 certificates until they expired, if they were published close in
10093 time to the certificate that superseded them. Fixes bug 11454;
10094 bugfix on 0.2.1.8-alpha.
10096 o Minor bugfixes (compilation):
10097 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
10099 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
10102 o Minor bugfixes (testing):
10103 - Fix endianness issues in unit test for resolve_my_address() to
10104 have it pass on big endian systems. Fixes bug 14980; bugfix on
10106 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
10107 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
10108 - When running the new 'make test-stem' target, use the configured
10109 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
10110 from "cypherpunks".
10111 - When running the zero-length-keys tests, do not use the default
10112 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
10115 o Directory authority IP change:
10116 - The directory authority Faravahar has a new IP address. This
10117 closes ticket 14487.
10120 - Remove some lingering dead code that once supported mempools.
10121 Mempools were disabled by default in 0.2.5, and removed entirely
10122 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
10126 Changes in version 0.2.6.3-alpha - 2015-02-19
10127 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
10128 the 0.2.6.x series. It introduces support for more kinds of sockets,
10129 makes it harder to accidentally run an exit, improves our
10130 multithreading backend, incorporates several fixes for the
10131 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
10133 If no major regressions or security holes are found in this version,
10134 the next version will be a release candidate.
10136 o Deprecated versions:
10137 - Tor relays older than 0.2.4.18-rc are no longer allowed to
10138 advertise themselves on the network. Closes ticket 13555.
10140 o Major features (security, unix domain sockets):
10141 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
10142 applications can reach Tor without having to create AF_INET or
10143 AF_INET6 sockets, meaning they can completely disable their
10144 ability to make non-Tor network connections. To create a socket of
10145 this type, use "SocksPort unix:/path/to/socket". Implements
10147 - Support mapping hidden service virtual ports to AF_UNIX sockets.
10148 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
10149 Implements ticket 11485.
10151 o Major features (changed defaults):
10152 - Prevent relay operators from unintentionally running exits: When a
10153 relay is configured as an exit node, we now warn the user unless
10154 the "ExitRelay" option is set to 1. We warn even more loudly if
10155 the relay is configured with the default exit policy, since this
10156 can indicate accidental misconfiguration. Setting "ExitRelay 0"
10157 stops Tor from running as an exit relay. Closes ticket 10067.
10159 o Major features (directory system):
10160 - When downloading server- or microdescriptors from a directory
10161 server, we no longer launch multiple simultaneous requests to the
10162 same server. This reduces load on the directory servers,
10163 especially when directory guards are in use. Closes ticket 9969.
10164 - When downloading server- or microdescriptors over a tunneled
10165 connection, do not limit the length of our requests to what the
10166 Squid proxy is willing to handle. Part of ticket 9969.
10167 - Authorities can now vote on the correct digests and latest
10168 versions for different software packages. This allows packages
10169 that include Tor to use the Tor authority system as a way to get
10170 notified of updates and their correct digests. Implements proposal
10171 227. Closes ticket 10395.
10173 o Major features (guards):
10174 - Introduce the Guardfraction feature to improves load balancing on
10175 guard nodes. Specifically, it aims to reduce the traffic gap that
10176 guard nodes experience when they first get the Guard flag. This is
10177 a required step if we want to increase the guard lifetime to 9
10178 months or greater. Closes ticket 9321.
10180 o Major features (performance):
10181 - Make the CPU worker implementation more efficient by avoiding the
10182 kernel and lengthening pipelines. The original implementation used
10183 sockets to transfer data from the main thread to the workers, and
10184 didn't allow any thread to be assigned more than a single piece of
10185 work at once. The new implementation avoids communications
10186 overhead by making requests in shared memory, avoiding kernel IO
10187 where possible, and keeping more requests in flight at once.
10188 Implements ticket 9682.
10190 o Major features (relay):
10191 - Raise the minimum acceptable configured bandwidth rate for bridges
10192 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
10193 20 KiB/sec.) Closes ticket 13822.
10195 o Major bugfixes (exit node stability):
10196 - Fix an assertion failure that could occur under high DNS load.
10197 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
10198 diagnosed and fixed by "cypherpunks".
10200 o Major bugfixes (mixed relay-client operation):
10201 - When running as a relay and client at the same time (not
10202 recommended), if we decide not to use a new guard because we want
10203 to retry older guards, only close the locally-originating circuits
10204 passing through that guard. Previously we would close all the
10205 circuits through that guard. Fixes bug 9819; bugfix on
10206 0.2.1.1-alpha. Reported by "skruffy".
10208 o Minor features (build):
10209 - New --disable-system-torrc compile-time option to prevent Tor from
10210 looking for the system-wide torrc or torrc-defaults files.
10211 Resolves ticket 13037.
10213 o Minor features (controller):
10214 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
10215 events so controllers can observe circuit isolation inputs. Closes
10217 - ControlPort now supports the unix:/path/to/socket syntax as an
10218 alternative to the ControlSocket option, for consistency with
10219 SocksPort and HiddenServicePort. Closes ticket 14451.
10220 - New "GETINFO bw-event-cache" to get information about recent
10221 bandwidth events. Closes ticket 14128. Useful for controllers to
10222 get recent bandwidth history after the fix for ticket 13988.
10224 o Minor features (Denial of service resistance):
10225 - Count the total number of bytes used storing hidden service
10226 descriptors against the value of MaxMemInQueues. If we're low on
10227 memory, and more than 20% of our memory is used holding hidden
10228 service descriptors, free them until no more than 10% of our
10229 memory holds hidden service descriptors. Free the least recently
10230 fetched descriptors first. Resolves ticket 13806.
10231 - When we have recently been under memory pressure (over 3/4 of
10232 MaxMemInQueues is allocated), then allocate smaller zlib objects
10233 for small requests. Closes ticket 11791.
10235 o Minor features (geoip):
10236 - Update geoip and geoip6 files to the January 7 2015 Maxmind
10237 GeoLite2 Country database.
10239 o Minor features (guard nodes):
10240 - Reduce the time delay before saving guard status to disk from 10
10241 minutes to 30 seconds (or from one hour to 10 minutes if
10242 AvoidDiskWrites is set). Closes ticket 12485.
10244 o Minor features (hidden service):
10245 - Make Sybil attacks against hidden services harder by changing the
10246 minimum time required to get the HSDir flag from 25 hours up to 96
10247 hours. Addresses ticket 14149.
10248 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
10249 services to disable the anti-scanning feature introduced in
10250 0.2.6.2-alpha. With this option not set, a connection to an
10251 unlisted port closes the circuit. With this option set, only a
10252 RELAY_DONE cell is sent. Closes ticket 14084.
10254 o Minor features (interface):
10255 - Implement "-f -" command-line option to read torrc configuration
10256 from standard input, if you don't want to store the torrc file in
10257 the file system. Implements feature 13865.
10259 o Minor features (logging):
10260 - Add a count of unique clients to the bridge heartbeat message.
10261 Resolves ticket 6852.
10262 - Suppress "router info incompatible with extra info" message when
10263 reading extrainfo documents from cache. (This message got loud
10264 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
10266 - Elevate hidden service authorized-client message from DEBUG to
10267 INFO. Closes ticket 14015.
10269 o Minor features (stability):
10270 - Add assertions in our hash-table iteration code to check for
10271 corrupted values that could cause infinite loops. Closes
10274 o Minor features (systemd):
10275 - Various improvements and modernizations in systemd hardening
10276 support. Closes ticket 13805. Patch from Craig Andrews.
10278 o Minor features (testing networks):
10279 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
10280 and the default on a testing network to 2 minutes. Drop the
10281 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
10282 keep the default on a testing network at 30 seconds. This reduces
10283 HS bootstrap time to around 25 seconds. Also, change the default
10284 time in test-network.sh to match. Closes ticket 13401. Patch
10286 - Create TestingDirAuthVoteHSDir to correspond to
10287 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
10288 HSDir flag for the listed relays regardless of uptime or ORPort
10289 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
10290 Partial implementation for ticket 14067. Patch by "teor".
10292 o Minor features (tor2web mode):
10293 - Introduce the config option Tor2webRendezvousPoints, which allows
10294 clients in Tor2webMode to select a specific Rendezvous Point to be
10295 used in HS circuits. This might allow better performance for
10296 Tor2Web nodes. Implements ticket 12844.
10298 o Minor bugfixes (client DNS):
10299 - Report the correct cached DNS expiration times on SOCKS port or in
10300 DNS replies. Previously, we would report everything as "never
10301 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
10302 - Avoid a small memory leak when we find a cached answer for a
10303 reverse DNS lookup in a client-side DNS cache. (Remember, client-
10304 side DNS caching is off by default, and is not recommended.) Fixes
10305 bug 14259; bugfix on 0.2.0.1-alpha.
10307 o Minor bugfixes (client, automapping):
10308 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
10309 no value follows the option. Fixes bug 14142; bugfix on
10310 0.2.4.7-alpha. Patch by "teor".
10311 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
10312 14195; bugfix on 0.1.0.1-rc.
10313 - Prevent changes to other options from removing the wildcard value
10314 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
10316 - Allow MapAddress and AutomapHostsOnResolve to work together when
10317 an address is mapped into another address type (like .onion) that
10318 must be automapped at resolve time. Fixes bug 7555; bugfix
10321 o Minor bugfixes (client, bridges):
10322 - When we are using bridges and we had a network connectivity
10323 problem, only retry connecting to our currently configured
10324 bridges, not all bridges we know about and remember using. Fixes
10325 bug 14216; bugfix on 0.2.2.17-alpha.
10327 o Minor bugfixes (client, IPv6):
10328 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
10329 flag is not set; and not because the NoIPv4Traffic flag was set.
10330 Previously we'd looked at the NoIPv4Traffic flag for both types of
10331 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
10333 o Minor bugfixes (compilation):
10334 - The address of an array in the middle of a structure will always
10335 be non-NULL. clang recognises this and complains. Disable the
10336 tautologous and redundant check to silence this warning. Fixes bug
10337 14001; bugfix on 0.2.1.2-alpha.
10338 - Avoid warnings when building with systemd 209 or later. Fixes bug
10339 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
10340 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
10341 Addresses ticket 14188.
10342 - Build without warnings with the stock OpenSSL srtp.h header, which
10343 has a duplicate declaration of SSL_get_selected_srtp_profile().
10344 Fixes bug 14220; this is OpenSSL's bug, not ours.
10345 - Do not compile any code related to Tor2Web mode when Tor2Web mode
10346 is not enabled at compile time. Previously, this code was included
10347 in a disabled state. See discussion on ticket 12844.
10348 - Remove the --disable-threads configure option again. It was
10349 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
10350 14819; bugfix on 0.2.6.2-alpha.
10352 o Minor bugfixes (controller):
10353 - Report "down" in response to the "GETINFO entry-guards" command
10354 when relays are down with an unreachable_since value. Previously,
10355 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
10356 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
10357 14116; bugfix on 0.2.2.9-alpha.
10358 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
10359 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
10361 o Minor bugfixes (directory authority):
10362 - Allow directory authorities to fetch more data from one another if
10363 they find themselves missing lots of votes. Previously, they had
10364 been bumping against the 10 MB queued data limit. Fixes bug 14261;
10365 bugfix on 0.1.2.5-alpha.
10366 - Do not attempt to download extrainfo documents which we will be
10367 unable to validate with a matching server descriptor. Fixes bug
10368 13762; bugfix on 0.2.0.1-alpha.
10369 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
10370 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
10371 - Enlarge the buffer to read bwauth generated files to avoid an
10372 issue when parsing the file in dirserv_read_measured_bandwidths().
10373 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
10375 o Minor bugfixes (file handling):
10376 - Stop failing when key files are zero-length. Instead, generate new
10377 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
10378 on all versions of Tor. Patch by "teor".
10379 - Stop generating a fresh .old RSA onion key file when the .old file
10380 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
10381 - Avoid overwriting .old key files with empty key files.
10382 - Skip loading zero-length extrainfo store, router store, stats,
10383 state, and key files.
10384 - Avoid crashing when trying to reload a torrc specified as a
10385 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
10388 o Minor bugfixes (hidden services):
10389 - Close the introduction circuit when we have no more usable intro
10390 points, instead of waiting for it to time out. This also ensures
10391 that no follow-up HS descriptor fetch is triggered when the
10392 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
10393 - When fetching a hidden service descriptor for a down service that
10394 was recently up, do not keep refetching until we try the same
10395 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
10396 - Successfully launch Tor with a nonexistent hidden service
10397 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
10398 14106; bugfix on 0.2.6.2-alpha.
10400 o Minor bugfixes (logging):
10401 - Avoid crashing when there are more log domains than entries in
10402 domain_list. Bugfix on 0.2.3.1-alpha.
10403 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
10405 - Don't log messages to stdout twice when starting up. Fixes bug
10406 13993; bugfix on 0.2.6.1-alpha.
10408 o Minor bugfixes (parsing):
10409 - Stop accepting milliseconds (or other junk) at the end of
10410 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
10411 - Support two-number and three-number version numbers correctly, in
10412 case we change the Tor versioning system in the future. Fixes bug
10413 13661; bugfix on 0.0.8pre1.
10415 o Minor bugfixes (path counting):
10416 - When deciding whether the consensus lists any exit nodes, count
10417 the number listed in the consensus, not the number we have
10418 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
10419 - When deciding whether we have any exit nodes, only examine
10420 ExitNodes when the ExitNodes option is actually set. Fixes part of
10421 bug 14918; bugfix on 0.2.6.2-alpha.
10422 - Get rid of redundant and possibly scary warnings that we are
10423 missing directory information while we bootstrap. Fixes part of
10424 bug 14918; bugfix on 0.2.6.2-alpha.
10426 o Minor bugfixes (portability):
10427 - Fix the ioctl()-based network interface lookup code so that it
10428 will work on systems that have variable-length struct ifreq, for
10430 - Fix scheduler compilation on targets where char is unsigned. Fixes
10431 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
10433 o Minor bugfixes (sandbox):
10434 - Allow glibc fatal errors to be sent to stderr before Tor exits.
10435 Previously, glibc would try to write them to /dev/tty, and the
10436 sandbox would trap the call and make Tor exit prematurely. Fixes
10437 bug 14759; bugfix on 0.2.5.1-alpha.
10439 o Minor bugfixes (shutdown):
10440 - When shutting down, always call event_del() on lingering read or
10441 write events before freeing them. Otherwise, we risk double-frees
10442 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
10445 o Minor bugfixes (small memory leaks):
10446 - Avoid leaking memory when using IPv6 virtual address mappings.
10447 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
10450 o Minor bugfixes (statistics):
10451 - Increase period over which bandwidth observations are aggregated
10452 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
10454 o Minor bugfixes (systemd support):
10455 - Fix detection and operation of systemd watchdog. Fixes part of bug
10456 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
10457 - Run correctly under systemd with the RunAsDaemon option set. Fixes
10458 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
10459 - Inform the systemd supervisor about more changes in the Tor
10460 process status. Implements part of ticket 14141. Patch from
10462 - Cause the "--disable-systemd" option to actually disable systemd
10463 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
10466 o Minor bugfixes (TLS):
10467 - Check more thoroughly throughout the TLS code for possible
10468 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
10470 o Minor bugfixes (transparent proxy):
10471 - Use getsockname, not getsockopt, to retrieve the address for a
10472 TPROXY-redirected connection. Fixes bug 13796; bugfix
10475 o Code simplification and refactoring:
10476 - Move fields related to isolating and configuring client ports into
10477 a shared structure. Previously, they were duplicated across
10478 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
10479 to copy them correctly had been the cause of at least one bug in
10480 the past. Closes ticket 8546.
10481 - Refactor the get_interface_addresses_raw() doom-function into
10482 multiple smaller and simpler subfunctions. Cover the resulting
10483 subfunctions with unit-tests. Fixes a significant portion of
10485 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
10486 only for version <= 0.2.2.24 which is now deprecated. Closes
10488 - Remove a test for a long-defunct broken version-one
10492 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
10493 for writing the OpenBSD-specific tips. Resolves ticket 13702.
10494 - Make the tor-resolve documentation match its help string and its
10495 options. Resolves part of ticket 14325.
10496 - Log a more useful error message from tor-resolve when failing to
10497 look up a hidden service address. Resolves part of ticket 14325.
10499 o Downgraded warnings:
10500 - Don't warn when we've attempted to contact a relay using the wrong
10501 ntor onion key. Closes ticket 9635.
10503 o Removed features:
10504 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
10505 longer silently accepted as an alias for "ExitNodes".
10506 - The --enable-mempool and --enable-buf-freelists options, which
10507 were originally created to work around bad malloc implementations,
10508 no longer exist. They were off-by-default in 0.2.5. Closes
10512 - Make the checkdir/perms test complete successfully even if the
10513 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
10514 - Test that tor does not fail when key files are zero-length. Check
10515 that tor generates new keys, and overwrites the empty key files.
10516 - Test that tor generates new keys when keys are missing
10517 (existing behavior).
10518 - Test that tor does not overwrite key files that already contain
10519 data (existing behavior). Tests bug 13111. Patch by "teor".
10520 - New "make test-stem" target to run stem integration tests.
10521 Requires that the "STEM_SOURCE_DIR" environment variable be set.
10522 Closes ticket 14107.
10523 - Make the test_cmdline_args.py script work correctly on Windows.
10524 Patch from Gisle Vanem.
10525 - Move the slower unit tests into a new "./src/test/test-slow"
10526 binary that can be run independently of the other tests. Closes
10528 - Avoid undefined behavior when sampling huge values from the
10529 Laplace distribution. This made unittests fail on Raspberry Pi.
10530 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
10533 Changes in version 0.2.6.2-alpha - 2014-12-31
10534 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
10535 It introduces a major new backend for deciding when to send cells on
10536 channels, which should lead down the road to big performance
10537 increases. It contains security and statistics features for better
10538 work on hidden services, and numerous bugfixes.
10540 This release contains many new unit tests, along with major
10541 performance improvements for running testing networks using Chutney.
10542 Thanks to a series of patches contributed by "teor", testing networks
10543 should now bootstrap in seconds, rather than minutes.
10545 o Major features (relay, infrastructure):
10546 - Complete revision of the code that relays use to decide which cell
10547 to send next. Formerly, we selected the best circuit to write on
10548 each channel, but we didn't select among channels in any
10549 sophisticated way. Now, we choose the best circuits globally from
10550 among those whose channels are ready to deliver traffic.
10552 This patch implements a new inter-cmux comparison API, a global
10553 high/low watermark mechanism and a global scheduler loop for
10554 transmission prioritization across all channels as well as among
10555 circuits on one channel. This schedule is currently tuned to
10556 (tolerantly) avoid making changes in network performance, but it
10557 should form the basis for major circuit performance increases in
10558 the future. Code by Andrea; tuning by Rob Jansen; implements
10561 o Major features (hidden services):
10562 - Make HS port scanning more difficult by immediately closing the
10563 circuit when a user attempts to connect to a nonexistent port.
10564 Closes ticket 13667.
10565 - Add a HiddenServiceStatistics option that allows Tor relays to
10566 gather and publish statistics about the overall size and volume of
10567 hidden service usage. Specifically, when this option is turned on,
10568 an HSDir will publish an approximate number of hidden services
10569 that have published descriptors to it the past 24 hours. Also, if
10570 a relay has acted as a hidden service rendezvous point, it will
10571 publish the approximate amount of rendezvous cells it has relayed
10572 the past 24 hours. The statistics themselves are obfuscated so
10573 that the exact values cannot be derived. For more details see
10574 proposal 238, "Better hidden service stats from Tor relays". This
10575 feature is currently disabled by default. Implements feature 13192.
10577 o Major bugfixes (client, automap):
10578 - Repair automapping with IPv6 addresses. This automapping should
10579 have worked previously, but one piece of debugging code that we
10580 inserted to detect a regression actually caused the regression to
10581 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
10582 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
10585 o Major bugfixes (hidden services):
10586 - When closing an introduction circuit that was opened in parallel
10587 with others, don't mark the introduction point as unreachable.
10588 Previously, the first successful connection to an introduction
10589 point would make the other introduction points get marked as
10590 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
10592 o Directory authority changes:
10593 - Remove turtles as a directory authority.
10594 - Add longclaw as a new (v3) directory authority. This implements
10595 ticket 13296. This keeps the directory authority count at 9.
10597 o Major removed features:
10598 - Tor clients no longer support connecting to hidden services
10599 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
10600 option has been removed. (There shouldn't be any hidden services
10601 running these versions on the network.) Closes ticket 7803.
10603 o Minor features (client):
10604 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
10605 is enabled, reject requests with IP addresses as hostnames.
10606 Resolves ticket 13315.
10608 o Minor features (controller):
10609 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
10610 write an unscheduled heartbeat message to the log. Implements
10613 o Minor features (geoip):
10614 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
10617 o Minor features (hidden services):
10618 - When re-enabling the network, don't try to build introduction
10619 circuits until we have successfully built a circuit. This makes
10620 hidden services come up faster when the network is re-enabled.
10621 Patch from "akwizgran". Closes ticket 13447.
10622 - When we fail to retrieve a hidden service descriptor, send the
10623 controller an "HS_DESC FAILED" controller event. Implements
10625 - New HiddenServiceDirGroupReadable option to cause hidden service
10626 directories and hostname files to be created group-readable. Patch
10627 from "anon", David Stainton, and "meejah". Closes ticket 11291.
10629 o Minor features (systemd):
10630 - Where supported, when running with systemd, report successful
10631 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
10632 - When running with systemd, support systemd watchdog messages. Part
10633 of ticket 11016. Patch by Michael Scherer.
10635 o Minor features (transparent proxy):
10636 - Update the transparent proxy option checks to allow for both ipfw
10637 and pf on OS X. Closes ticket 14002.
10638 - Use the correct option when using IPv6 with transparent proxy
10639 support on Linux. Resolves 13808. Patch by Francisco Blas
10642 o Minor bugfixes (preventative security, C safety):
10643 - When reading a hexadecimal, base-32, or base-64 encoded value from
10644 a string, always overwrite the whole output buffer. This prevents
10645 some bugs where we would look at (but fortunately, not reveal)
10646 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
10648 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
10649 just the part that's used. This makes it harder for data leak bugs
10650 to occur in the event of other programming failures. Resolves
10653 o Minor bugfixes (client, microdescriptors):
10654 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
10655 computing which microdescriptors to download. This keeps us from
10656 erroneous download behavior if two microdescriptor digests ever
10657 have the same first 160 bits. Fixes part of bug 13399; bugfix
10659 - Reset a router's status if its microdescriptor digest changes,
10660 even if the first 160 bits remain the same. Fixes part of bug
10661 13399; bugfix on 0.2.3.1-alpha.
10663 o Minor bugfixes (compilation):
10664 - Silence clang warnings under --enable-expensive-hardening,
10665 including implicit truncation of 64 bit values to 32 bit, const
10666 char assignment to self, tautological compare, and additional
10667 parentheses around equality tests. Fixes bug 13577; bugfix
10669 - Fix a clang warning about checking whether an address in the
10670 middle of a structure is NULL. Fixes bug 14001; bugfix
10673 o Minor bugfixes (hidden services):
10674 - Correctly send a controller event when we find that a rendezvous
10675 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
10676 - Pre-check directory permissions for new hidden-services to avoid
10677 at least one case of "Bug: Acting on config options left us in a
10678 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
10679 - When adding a new hidden service (for example, via SETCONF), Tor
10680 no longer congratulates the user for running a relay. Fixes bug
10681 13941; bugfix on 0.2.6.1-alpha.
10682 - When fetching hidden service descriptors, we now check not only
10683 for whether we got the hidden service we had in mind, but also
10684 whether we got the particular descriptors we wanted. This prevents
10685 a class of inefficient but annoying DoS attacks by hidden service
10686 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
10689 o Minor bugfixes (Linux seccomp2 sandbox):
10690 - Make transparent proxy support work along with the seccomp2
10691 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
10692 by Francisco Blas Izquierdo Riera.
10693 - Fix a memory leak in tor-resolve when running with the sandbox
10694 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
10696 o Minor bugfixes (logging):
10697 - Downgrade warnings about RSA signature failures to info log level.
10698 Emit a warning when an extra info document is found incompatible
10699 with a corresponding router descriptor. Fixes bug 9812; bugfix
10701 - Make connection_ap_handshake_attach_circuit() log the circuit ID
10702 correctly. Fixes bug 13701; bugfix on 0.0.6.
10704 o Minor bugfixes (misc):
10705 - Stop allowing invalid address patterns like "*/24" that contain
10706 both a wildcard address and a bit prefix length. This affects all
10707 our address-range parsing code. Fixes bug 7484; bugfix
10710 o Minor bugfixes (testing networks, fast startup):
10711 - Allow Tor to build circuits using a consensus with no exits. If
10712 the consensus has no exits (typical of a bootstrapping test
10713 network), allow Tor to build circuits once enough descriptors have
10714 been downloaded. This assists in bootstrapping a testing Tor
10715 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
10717 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
10718 header to directory servers. This allows us to obtain consensuses
10719 promptly when the consensus interval is very short. This assists
10720 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
10721 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
10722 - Stop assuming that private addresses are local when checking
10723 reachability in a TestingTorNetwork. Instead, when testing, assume
10724 all OR connections are remote. (This is necessary due to many test
10725 scenarios running all relays on localhost.) This assists in
10726 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
10727 0.1.0.1-rc. Patch by "teor".
10728 - Avoid building exit circuits from a consensus with no exits. Now
10729 thanks to our fix for 13718, we accept a no-exit network as not
10730 wholly lost, but we need to remember not to try to build exit
10731 circuits on it. Closes ticket 13814; patch by "teor".
10732 - Stop requiring exits to have non-zero bandwithcapacity in a
10733 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
10734 ignore exit bandwidthcapacity. This assists in bootstrapping a
10735 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
10736 on 0.2.0.3-alpha. Patch by "teor".
10737 - Add "internal" to some bootstrap statuses when no exits are
10738 available. If the consensus does not contain Exits, Tor will only
10739 build internal circuits. In this case, relevant statuses will
10740 contain the word "internal" as indicated in the Tor control-
10741 spec.txt. When bootstrap completes, Tor will be ready to build
10742 internal circuits. If a future consensus contains Exits, exit
10743 circuits may become available. Fixes part of bug 13718; bugfix on
10744 0.2.4.10-alpha. Patch by "teor".
10745 - Decrease minimum consensus interval to 10 seconds when
10746 TestingTorNetwork is set, or 5 seconds for the first consensus.
10747 Fix assumptions throughout the code that assume larger intervals.
10748 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
10750 - Avoid excluding guards from path building in minimal test
10751 networks, when we're in a test network and excluding guards would
10752 exclude all relays. This typically occurs in incredibly small tor
10753 networks, and those using "TestingAuthVoteGuard *". Fixes part of
10754 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
10756 o Code simplification and refactoring:
10757 - Stop using can_complete_circuits as a global variable; access it
10758 with a function instead.
10759 - Avoid using operators directly as macro arguments: this lets us
10760 apply coccinelle transformations to our codebase more directly.
10761 Closes ticket 13172.
10762 - Combine the functions used to parse ClientTransportPlugin and
10763 ServerTransportPlugin into a single function. Closes ticket 6456.
10764 - Add inline functions and convenience macros for inspecting channel
10765 state. Refactor the code to use convenience macros instead of
10766 checking channel state directly. Fixes issue 7356.
10767 - Document all members of was_router_added_t and rename
10768 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
10769 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
10770 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
10771 constant instead of hardcoded value. Fixes issue 13840.
10772 - Refactor our generic strmap and digestmap types into a single
10773 implementation, so that we can add a new digest256map
10777 - Document the bridge-authority-only 'networkstatus-bridges' file.
10778 Closes ticket 13713; patch from "tom".
10779 - Fix typo in PredictedPortsRelevanceTime option description in
10780 manpage. Resolves issue 13707.
10781 - Stop suggesting that users specify relays by nickname: it isn't a
10782 good idea. Also, properly cross-reference how to specify relays in
10783 all parts of manual documenting options that take a list of
10784 relays. Closes ticket 13381.
10785 - Clarify the HiddenServiceDir option description in manpage to make
10786 it clear that relative paths are taken with respect to the current
10787 working directory. Also clarify that this behavior is not
10788 guaranteed to remain indefinitely. Fixes issue 13913.
10791 - New tests for many parts of channel, relay, and circuitmux
10792 functionality. Code by Andrea; part of 9262.
10793 - New tests for parse_transport_line(). Part of ticket 6456.
10794 - In the unit tests, use chgrp() to change the group of the unit
10795 test temporary directory to the current user, so that the sticky
10796 bit doesn't interfere with tests that check directory groups.
10798 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
10802 Changes in version 0.2.6.1-alpha - 2014-10-30
10803 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
10804 includes numerous code cleanups and new tests, and fixes a large
10805 number of annoying bugs. Out-of-memory conditions are handled better
10806 than in 0.2.5, pluggable transports have improved proxy support, and
10807 clients now use optimistic data for contacting hidden services. Also,
10808 we are now more robust to changes in what we consider a parseable
10809 directory object, so that tightening restrictions does not have a risk
10810 of introducing infinite download loops.
10812 This is the first alpha release in a new series, so expect there to be
10813 bugs. Users who would rather test out a more stable branch should stay
10814 with 0.2.5.x for now.
10816 o New compiler and system requirements:
10817 - Tor 0.2.6.x requires that your compiler support more of the C99
10818 language standard than before. The 'configure' script now detects
10819 whether your compiler supports C99 mid-block declarations and
10820 designated initializers. If it does not, Tor will not compile.
10822 We may revisit this requirement if it turns out that a significant
10823 number of people need to build Tor with compilers that don't
10824 bother implementing a 15-year-old standard. Closes ticket 13233.
10825 - Tor no longer supports systems without threading support. When we
10826 began working on Tor, there were several systems that didn't have
10827 threads, or where the thread support wasn't able to run the
10828 threads of a single process on multiple CPUs. That no longer
10829 holds: every system where Tor needs to run well now has threading
10830 support. Resolves ticket 12439.
10832 o Removed platform support:
10833 - We no longer include special code to build on Windows CE; as far
10834 as we know, nobody has used Tor on Windows CE in a very long time.
10835 Closes ticket 11446.
10837 o Major features (bridges):
10838 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
10839 transports if they are configured via the "TOR_PT_PROXY"
10840 environment variable. Implements proposal 232. Resolves
10843 o Major features (client performance, hidden services):
10844 - Allow clients to use optimistic data when connecting to a hidden
10845 service, which should remove a round-trip from hidden service
10846 initialization. See proposal 181 for details. Implements
10849 o Major features (directory system):
10850 - Upon receiving an unparseable directory object, if its digest
10851 matches what we expected, then don't try to download it again.
10852 Previously, when we got a descriptor we didn't like, we would keep
10853 trying to download it over and over. Closes ticket 11243.
10855 o Major features (sample torrc):
10856 - Add a new, infrequently-changed "torrc.minimal". This file is
10857 similar to torrc.sample, but it will change as infrequently as
10858 possible, for the benefit of users whose systems prompt them for
10859 intervention whenever a default configuration file is changed.
10860 Making this change allows us to update torrc.sample to be a more
10861 generally useful "sample torrc".
10863 o Major bugfixes (directory authorities):
10864 - Do not assign the HSDir flag to relays if they are not Valid, or
10865 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
10867 o Major bugfixes (directory bandwidth performance):
10868 - Don't flush the zlib buffer aggressively when compressing
10869 directory information for clients. This should save about 7% of
10870 the bandwidth currently used for compressed descriptors and
10871 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
10873 o Minor features (security, memory wiping):
10874 - Ensure we securely wipe keys from memory after
10875 crypto_digest_get_digest and init_curve25519_keypair_from_file
10876 have finished using them. Resolves ticket 13477.
10878 o Minor features (security, out-of-memory handling):
10879 - When handling an out-of-memory condition, allocate less memory for
10880 temporary data structures. Fixes issue 10115.
10881 - When handling an out-of-memory condition, consider more types of
10882 buffers, including those on directory connections, and zlib
10883 buffers. Resolves ticket 11792.
10886 - When identity keypair is generated for first time, log a
10887 congratulatory message that links to the new relay lifecycle
10888 document. Implements feature 10427.
10890 o Minor features (client):
10891 - Clients are now willing to send optimistic data (before they
10892 receive a 'connected' cell) to relays of any version. (Relays
10893 without support for optimistic data are no longer supported on the
10894 Tor network.) Resolves ticket 13153.
10896 o Minor features (directory authorities):
10897 - Don't list relays with a bandwidth estimate of 0 in the consensus.
10898 Implements a feature proposed during discussion of bug 13000.
10899 - In tor-gencert, report an error if the user provides the same
10900 argument more than once.
10901 - If a directory authority can't find a best consensus method in the
10902 votes that it holds, it now falls back to its favorite consensus
10903 method. Previously, it fell back to method 1. Neither of these is
10904 likely to get enough signatures, but "fall back to favorite"
10905 doesn't require us to maintain support an obsolete consensus
10906 method. Implements part of proposal 215.
10908 o Minor features (logging):
10909 - On Unix-like systems, you can now use named pipes as the target of
10910 the Log option, and other options that try to append to files.
10911 Closes ticket 12061. Patch from "carlo von lynX".
10912 - When opening a log file at startup, send it every log message that
10913 we generated between startup and opening it. Previously, log
10914 messages that were generated before opening the log file were only
10915 logged to stdout. Closes ticket 6938.
10916 - Add a TruncateLogFile option to overwrite logs instead of
10917 appending to them. Closes ticket 5583.
10919 o Minor features (portability, Solaris):
10920 - Threads are no longer disabled by default on Solaris; we believe
10921 that the versions of Solaris with broken threading support are all
10922 obsolete by now. Resolves ticket 9495.
10924 o Minor features (relay):
10925 - Re-check our address after we detect a changed IP address from
10926 getsockname(). This ensures that the controller command "GETINFO
10927 address" will report the correct value. Resolves ticket 11582.
10929 - A new AccountingRule option lets Relays set whether they'd like
10930 AccountingMax to be applied separately to inbound and outbound
10931 traffic, or applied to the sum of inbound and outbound traffic.
10932 Resolves ticket 961. Patch by "chobe".
10934 o Minor features (testing networks):
10935 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
10936 the "Exit" flag regardless of their uptime, bandwidth, or exit
10937 policy. TestingTorNetwork must be set for this option to have any
10938 effect. Previously, authorities would take up to 35 minutes to
10939 give nodes the Exit flag in a test network. Partially implements
10942 o Minor features (validation):
10943 - Check all date/time values passed to tor_timegm and
10944 parse_rfc1123_time for validity, taking leap years into account.
10945 Improves HTTP header validation. Implemented with bug 13476.
10946 - In correct_tm(), limit the range of values returned by system
10947 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
10948 This means we don't have to deal with negative or too large dates,
10949 even if a clock is wrong. Otherwise we might fail to read a file
10950 written by us which includes such a date. Fixes bug 13476.
10952 o Minor bugfixes (bridge clients):
10953 - When configured to use a bridge without an identity digest (not
10954 recommended), avoid launching an extra channel to it when
10955 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
10957 o Minor bugfixes (bridges):
10958 - When DisableNetwork is set, do not launch pluggable transport
10959 plugins, and if any are running, terminate them. Fixes bug 13213;
10960 bugfix on 0.2.3.6-alpha.
10962 o Minor bugfixes (C correctness):
10963 - Fix several instances of possible integer overflow/underflow/NaN.
10964 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
10966 - In circuit_build_times_calculate_timeout() in circuitstats.c,
10967 avoid dividing by zero in the pareto calculations. This traps
10968 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
10970 - Fix an integer overflow in format_time_interval(). Fixes bug
10971 13393; bugfix on 0.2.0.10-alpha.
10972 - Set the correct day of year value when the system's localtime(_r)
10973 or gmtime(_r) functions fail to set struct tm. Not externally
10974 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
10975 - Avoid unlikely signed integer overflow in tor_timegm on systems
10976 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
10978 o Minor bugfixes (client):
10979 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
10980 BadExit flag are not considered worthy candidates. Fixes bug
10981 13066; bugfix on 0.1.2.3-alpha.
10982 - Use the consensus schedule for downloading consensuses, and not
10983 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
10984 - Handle unsupported or malformed SOCKS5 requests properly by
10985 responding with the appropriate error message before closing the
10986 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
10988 o Minor bugfixes (client, torrc):
10989 - Stop modifying the value of our DirReqStatistics torrc option just
10990 because we're not a bridge or relay. This bug was causing Tor
10991 Browser users to write "DirReqStatistics 0" in their torrc files
10992 as if they had chosen to change the config. Fixes bug 4244; bugfix
10994 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
10995 that our options have changed every time we SIGHUP. Fixes bug
10996 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
10998 o Minor bugfixes (controller):
10999 - Return an error when the second or later arguments of the
11000 "setevents" controller command are invalid events. Previously we
11001 would return success while silently skipping invalid events. Fixes
11002 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
11004 o Minor bugfixes (directory system):
11005 - Always believe that v3 directory authorities serve extra-info
11006 documents, whether they advertise "caches-extra-info" or not.
11007 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
11008 - When running as a v3 directory authority, advertise that you serve
11009 extra-info documents so that clients who want them can find them
11010 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
11011 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
11012 Previously, directories offering BRIDGE_DIRINFO and some other
11013 flag (i.e. microdescriptors or extrainfo) would be ignored when
11014 looking for bridges. Partially fixes bug 13163; bugfix
11017 o Minor bugfixes (networking):
11018 - Check for orconns and use connection_or_close_for_error() rather
11019 than connection_mark_for_close() directly in the getsockopt()
11020 failure case of connection_handle_write_impl(). Fixes bug 11302;
11021 bugfix on 0.2.4.4-alpha.
11023 o Minor bugfixes (relay):
11024 - When generating our family list, remove spaces from around the
11025 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
11026 - If our previous bandwidth estimate was 0 bytes, allow publishing a
11027 new relay descriptor immediately. Fixes bug 13000; bugfix
11030 o Minor bugfixes (testing networks):
11031 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
11032 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
11033 - Stop using the default authorities in networks which provide both
11034 AlternateDirAuthority and AlternateBridgeAuthority. Partially
11035 fixes bug 13163; bugfix on 0.2.0.13-alpha.
11037 o Minor bugfixes (testing):
11038 - Stop spawn test failures due to a race condition between the
11039 SIGCHLD handler updating the process status, and the test reading
11040 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
11042 o Minor bugfixes (testing, Windows):
11043 - Avoid passing an extra backslash when creating a temporary
11044 directory for running the unit tests on Windows. Fixes bug 12392;
11045 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
11047 o Minor bugfixes (windows):
11048 - Remove code to special-case handling of NTE_BAD_KEYSET when
11049 acquiring windows CryptoAPI context. This error can't actually
11050 occur for the parameters we're providing. Fixes bug 10816; bugfix
11053 o Minor bugfixes (zlib):
11054 - Avoid truncating a zlib stream when trying to finalize it with an
11055 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
11058 - Allow our configure script to build correctly with autoconf 2.62
11059 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
11060 - Improve the error message from ./configure to make it clear that
11061 when asciidoc has not been found, the user will have to either add
11062 --disable-asciidoc argument or install asciidoc. Resolves
11065 o Code simplification and refactoring:
11066 - Change the entry_is_live() function to take named bitfield
11067 elements instead of an unnamed list of booleans. Closes
11069 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
11070 Resolves ticket 12205.
11071 - Use calloc and reallocarray functions instead of multiply-
11072 then-malloc. This makes it less likely for us to fall victim to an
11073 integer overflow attack when allocating. Resolves ticket 12855.
11074 - Use the standard macro name SIZE_MAX, instead of our
11076 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
11077 functions which take them as arguments. Replace 0 with NO_DIRINFO
11078 in a function call for clarity. Seeks to prevent future issues
11080 - Avoid 4 null pointer errors under clang static analysis by using
11081 tor_assert() to prove that the pointers aren't null. Fixes
11083 - Rework the API of policies_parse_exit_policy() to use a bitmask to
11084 represent parsing options, instead of a confusing mess of
11085 booleans. Resolves ticket 8197.
11086 - Introduce a helper function to parse ExitPolicy in
11087 or_options_t structure.
11090 - Add a doc/TUNING document with tips for handling large numbers of
11091 TCP connections when running busy Tor relay. Update the warning
11092 message to point to this file when running out of sockets
11093 operating system is allowing to use simultaneously. Resolves
11096 o Removed features:
11097 - We no longer remind the user about configuration options that have
11098 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
11099 - Remove our old, non-weighted bandwidth-based node selection code.
11100 Previously, we used it as a fallback when we couldn't perform
11101 weighted bandwidth-based node selection. But that would only
11102 happen in the cases where we had no consensus, or when we had a
11103 consensus generated by buggy or ancient directory authorities. In
11104 either case, it's better to use the more modern, better maintained
11105 algorithm, with reasonable defaults for the weights. Closes
11107 - Remove the --disable-curve25519 configure option. Relays and
11108 clients now are required to support curve25519 and the
11110 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
11111 used to be deprecated synonyms for "StrictNodes", are now marked
11112 obsolete. Resolves ticket 12226.
11113 - Clients don't understand the BadDirectory flag in the consensus
11114 anymore, and ignore it.
11117 - Refactor the function that chooses guard nodes so that it can more
11118 easily be tested; write some tests for it.
11119 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
11120 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
11121 - Create unit tests for format_time_interval(). With bug 13393.
11122 - Add unit tests for tor_timegm signed overflow, tor_timegm and
11123 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
11124 tests (visible) fixes in bug 13476.
11125 - Add a "coverage-html" make target to generate HTML-visualized
11126 coverage results when building with --enable-coverage. (Requires
11127 lcov.) Patch from Kevin Murray.
11128 - Enable the backtrace handler (where supported) when running the
11130 - Revise all unit tests that used the legacy test_* macros to
11131 instead use the recommended tt_* macros. This patch was generated
11132 with coccinelle, to avoid manual errors. Closes ticket 13119.
11134 o Distribution (systemd):
11135 - systemd unit file: only allow tor to write to /var/lib/tor and
11136 /var/log/tor. The rest of the filesystem is accessible for reading
11137 only. Patch by intrigeri; resolves ticket 12751.
11138 - systemd unit file: ensure that the process and all its children
11139 can never gain new privileges. Patch by intrigeri; resolves
11141 - systemd unit file: set up /var/run/tor as writable for the Tor
11142 service. Patch by intrigeri; resolves ticket 13196.
11144 o Removed features (directory authorities):
11145 - Remove code that prevented authorities from listing Tor relays
11146 affected by CVE-2011-2769 as guards. These relays are already
11147 rejected altogether due to the minimum version requirement of
11148 0.2.3.16-alpha. Closes ticket 13152.
11149 - The "AuthDirRejectUnlisted" option no longer has any effect, as
11150 the fingerprints file (approved-routers) has been deprecated.
11151 - Directory authorities do not support being Naming dirauths anymore.
11152 The "NamingAuthoritativeDir" config option is now obsolete.
11153 - Directory authorities do not support giving out the BadDirectory
11155 - Directory authorities no longer advertise or support consensus
11156 methods 1 through 12 inclusive. These consensus methods were
11157 obsolete and/or insecure: maintaining the ability to support them
11158 served no good purpose. Implements part of proposal 215; closes
11161 o Testing (test-network.sh):
11162 - Stop using "echo -n", as some shells' built-in echo doesn't
11163 support "-n". Instead, use "/bin/echo -n". Partially fixes
11165 - Stop an apparent test-network hang when used with make -j2. Fixes
11167 - Add a --delay option to test-network.sh, which configures the
11168 delay before the chutney network tests for data transmission.
11169 Partially implements ticket 13161.
11172 Changes in version 0.2.5.10 - 2014-10-24
11173 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
11175 It adds several new security features, including improved
11176 denial-of-service resistance for relays, new compiler hardening
11177 options, and a system-call sandbox for hardened installations on Linux
11178 (requires seccomp2). The controller protocol has several new features,
11179 resolving IPv6 addresses should work better than before, and relays
11180 should be a little more CPU-efficient. We've added support for more
11181 OpenBSD and FreeBSD transparent proxy types. We've improved the build
11182 system and testing infrastructure to allow unit testing of more parts
11183 of the Tor codebase. Finally, we've addressed several nagging pluggable
11184 transport usability issues, and included numerous other small bugfixes
11185 and features mentioned below.
11187 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
11188 have accumulated many known flaws; everyone should upgrade.
11190 o Deprecated versions:
11191 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
11192 attention for some while.
11195 Changes in version 0.2.5.9-rc - 2014-10-20
11196 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
11197 series. It disables SSL3 in response to the recent "POODLE" attack
11198 (even though POODLE does not affect Tor). It also works around a crash
11199 bug caused by some operating systems' response to the "POODLE" attack
11200 (which does affect Tor). It also contains a few miscellaneous fixes.
11202 o Major security fixes:
11203 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
11204 today support TLS 1.0 or later, so we can safely turn off support
11205 for this old (and insecure) protocol. Fixes bug 13426.
11207 o Major bugfixes (openssl bug workaround):
11208 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
11209 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
11210 13471. This is a workaround for an OpenSSL bug.
11213 - Disable the sandbox name resolver cache when running tor-resolve:
11214 tor-resolve doesn't use the sandbox code, and turning it on was
11215 breaking attempts to do tor-resolve on a non-default server on
11216 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
11218 o Compilation fixes:
11219 - Build and run correctly on systems like OpenBSD-current that have
11220 patched OpenSSL to remove get_cipher_by_char and/or its
11221 implementations. Fixes issue 13325.
11223 o Downgraded warnings:
11224 - Downgrade the severity of the 'unexpected sendme cell from client'
11225 from 'warn' to 'protocol warning'. Closes ticket 8093.
11228 Changes in version 0.2.4.25 - 2014-10-20
11229 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
11230 (even though POODLE does not affect Tor). It also works around a crash
11231 bug caused by some operating systems' response to the "POODLE" attack
11232 (which does affect Tor).
11234 o Major security fixes (also in 0.2.5.9-rc):
11235 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
11236 today support TLS 1.0 or later, so we can safely turn off support
11237 for this old (and insecure) protocol. Fixes bug 13426.
11239 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
11240 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
11241 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
11242 13471. This is a workaround for an OpenSSL bug.
11245 Changes in version 0.2.5.8-rc - 2014-09-22
11246 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
11247 series. It fixes a bug that affects consistency and speed when
11248 connecting to hidden services, and it updates the location of one of
11249 the directory authorities.
11252 - Clients now send the correct address for their chosen rendezvous
11253 point when trying to access a hidden service. They used to send
11254 the wrong address, which would still work some of the time because
11255 they also sent the identity digest of the rendezvous point, and if
11256 the hidden service happened to try connecting to the rendezvous
11257 point from a relay that already had a connection open to it,
11258 the relay would reuse that connection. Now connections to hidden
11259 services should be more robust and faster. Also, this bug meant
11260 that clients were leaking to the hidden service whether they were
11261 on a little-endian (common) or big-endian (rare) system, which for
11262 some users might have reduced their anonymity. Fixes bug 13151;
11263 bugfix on 0.2.1.5-alpha.
11265 o Directory authority changes:
11266 - Change IP address for gabelmoo (v3 directory authority).
11269 Changes in version 0.2.4.24 - 2014-09-22
11270 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
11271 connecting to hidden services, and it updates the location of one of
11272 the directory authorities.
11275 - Clients now send the correct address for their chosen rendezvous
11276 point when trying to access a hidden service. They used to send
11277 the wrong address, which would still work some of the time because
11278 they also sent the identity digest of the rendezvous point, and if
11279 the hidden service happened to try connecting to the rendezvous
11280 point from a relay that already had a connection open to it,
11281 the relay would reuse that connection. Now connections to hidden
11282 services should be more robust and faster. Also, this bug meant
11283 that clients were leaking to the hidden service whether they were
11284 on a little-endian (common) or big-endian (rare) system, which for
11285 some users might have reduced their anonymity. Fixes bug 13151;
11286 bugfix on 0.2.1.5-alpha.
11288 o Directory authority changes:
11289 - Change IP address for gabelmoo (v3 directory authority).
11291 o Minor features (geoip):
11292 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
11296 Changes in version 0.2.5.7-rc - 2014-09-11
11297 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
11298 release series, and some long-standing bugs related to ORPort reachability
11299 testing and failure to send CREATE cells. It is the first release
11300 candidate for the Tor 0.2.5.x series.
11302 o Major bugfixes (client, startup):
11303 - Start making circuits as soon as DisabledNetwork is turned off.
11304 When Tor started with DisabledNetwork set, it would correctly
11305 conclude that it shouldn't build circuits, but it would mistakenly
11306 cache this conclusion, and continue believing it even when
11307 DisableNetwork is set to 0. Fixes the bug introduced by the fix
11308 for bug 11200; bugfix on 0.2.5.4-alpha.
11309 - Resume expanding abbreviations for command-line options. The fix
11310 for bug 4647 accidentally removed our hack from bug 586 that
11311 rewrote HashedControlPassword to __HashedControlSessionPassword
11312 when it appears on the commandline (which allowed the user to set
11313 her own HashedControlPassword in the torrc file while the
11314 controller generates a fresh session password for each run). Fixes
11315 bug 12948; bugfix on 0.2.5.1-alpha.
11316 - Warn about attempts to run hidden services and relays in the same
11317 process: that's probably not a good idea. Closes ticket 12908.
11319 o Major bugfixes (relay):
11320 - Avoid queuing or sending destroy cells for circuit ID zero when we
11321 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
11322 Found and fixed by "cypherpunks".
11323 - Fix ORPort reachability detection on relays running behind a
11324 proxy, by correctly updating the "local" mark on the controlling
11325 channel when changing the address of an or_connection_t after the
11326 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
11328 o Minor features (bridge):
11329 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
11330 cookie file for the ExtORPort g+r by default.
11332 o Minor features (geoip):
11333 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
11336 o Minor bugfixes (logging):
11337 - Reduce the log severity of the "Pluggable transport proxy does not
11338 provide any needed transports and will not be launched." message,
11339 since Tor Browser includes several ClientTransportPlugin lines in
11340 its torrc-defaults file, leading every Tor Browser user who looks
11341 at her logs to see these notices and wonder if they're dangerous.
11342 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
11343 - Downgrade "Unexpected onionskin length after decryption" warning
11344 to a protocol-warn, since there's nothing relay operators can do
11345 about a client that sends them a malformed create cell. Resolves
11346 bug 12996; bugfix on 0.0.6rc1.
11347 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
11348 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
11349 - When logging information about an EXTEND2 or EXTENDED2 cell, log
11350 their names correctly. Fixes part of bug 12700; bugfix
11352 - When logging information about a relay cell whose command we don't
11353 recognize, log its command as an integer. Fixes part of bug 12700;
11354 bugfix on 0.2.1.10-alpha.
11355 - Escape all strings from the directory connection before logging
11356 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
11358 o Minor bugfixes (controller):
11359 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
11360 bug 12864; bugfix on 0.2.5.1-alpha.
11361 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
11362 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
11365 o Minor bugfixes (compilation):
11366 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
11367 bugfix on 0.2.5.5-alpha.
11368 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
11369 0.2.5.1-alpha. Patch from "NewEraCracker".
11370 - In routerlist_assert_ok(), don't take the address of a
11371 routerinfo's cache_info member unless that routerinfo is non-NULL.
11372 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
11373 - Fix a large number of false positive warnings from the clang
11374 analyzer static analysis tool. This should make real warnings
11375 easier for clang analyzer to find. Patch from "teor". Closes
11378 o Distribution (systemd):
11379 - Verify configuration file via ExecStartPre in the systemd unit
11380 file. Patch from intrigeri; resolves ticket 12730.
11381 - Explicitly disable RunAsDaemon in the systemd unit file. Our
11382 current systemd unit uses "Type = simple", so systemd does not
11383 expect tor to fork. If the user has "RunAsDaemon 1" in their
11384 torrc, then things won't work as expected. This is e.g. the case
11385 on Debian (and derivatives), since there we pass "--defaults-torrc
11386 /usr/share/tor/tor-service-defaults-torrc" (that contains
11387 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
11391 - Adjust the URLs in the README to refer to the new locations of
11392 several documents on the website. Fixes bug 12830. Patch from
11394 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
11398 Changes in version 0.2.5.6-alpha - 2014-07-28
11399 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
11400 risk from guard rotation, and fixes a variety of other issues to get
11401 us closer to a release candidate.
11403 o Major features (also in 0.2.4.23):
11404 - Make the number of entry guards configurable via a new
11405 NumEntryGuards consensus parameter, and the number of directory
11406 guards configurable via a new NumDirectoryGuards consensus
11407 parameter. Implements ticket 12688.
11409 o Major bugfixes (also in 0.2.4.23):
11410 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
11411 implementation that caused incorrect results on 32-bit
11412 implementations when certain malformed inputs were used along with
11413 a small class of private ntor keys. This bug does not currently
11414 appear to allow an attacker to learn private keys or impersonate a
11415 Tor server, but it could provide a means to distinguish 32-bit Tor
11416 implementations from 64-bit Tor implementations. Fixes bug 12694;
11417 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
11421 - Perform circuit cleanup operations even when circuit
11422 construction operations are disabled (because the network is
11423 disabled, or because there isn't enough directory information).
11424 Previously, when we were not building predictive circuits, we
11425 were not closing expired circuits either. Fixes bug 8387; bugfix on
11426 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
11427 became more strict about when we have "enough directory information
11428 to build circuits".
11431 - Authorities now assign the Guard flag to the fastest 25% of the
11432 network (it used to be the fastest 50%). Also raise the consensus
11433 weight that guarantees the Guard flag from 250 to 2000. For the
11434 current network, this results in about 1100 guards, down from 2500.
11435 This step paves the way for moving the number of entry guards
11436 down to 1 (proposal 236) while still providing reasonable expected
11437 performance for most users. Implements ticket 12690.
11438 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
11440 - Slightly enhance the diagnostic message for bug 12184.
11442 o Minor bugfixes (also in 0.2.4.23):
11443 - Warn and drop the circuit if we receive an inbound 'relay early'
11444 cell. Those used to be normal to receive on hidden service circuits
11445 due to bug 1038, but the buggy Tor versions are long gone from
11446 the network so we can afford to resume watching for them. Resolves
11447 the rest of bug 1038; bugfix on 0.2.1.19.
11448 - Correct a confusing error message when trying to extend a circuit
11449 via the control protocol but we don't know a descriptor or
11450 microdescriptor for one of the specified relays. Fixes bug 12718;
11451 bugfix on 0.2.3.1-alpha.
11454 - Fix compilation when building with bufferevents enabled. (This
11455 configuration is still not expected to work, however.)
11456 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
11457 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
11459 - Compile correctly with builds and forks of OpenSSL (such as
11460 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
11461 0.2.1.1-alpha. Patch from "dhill".
11464 Changes in version 0.2.4.23 - 2014-07-28
11465 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
11466 guard rotation, and also backports several important fixes from the
11467 Tor 0.2.5 alpha release series.
11470 - Clients now look at the "usecreatefast" consensus parameter to
11471 decide whether to use CREATE_FAST or CREATE cells for the first hop
11472 of their circuit. This approach can improve security on connections
11473 where Tor's circuit handshake is stronger than the available TLS
11474 connection security levels, but the tradeoff is more computational
11475 load on guard relays. Implements proposal 221. Resolves ticket 9386.
11476 - Make the number of entry guards configurable via a new
11477 NumEntryGuards consensus parameter, and the number of directory
11478 guards configurable via a new NumDirectoryGuards consensus
11479 parameter. Implements ticket 12688.
11482 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
11483 implementation that caused incorrect results on 32-bit
11484 implementations when certain malformed inputs were used along with
11485 a small class of private ntor keys. This bug does not currently
11486 appear to allow an attacker to learn private keys or impersonate a
11487 Tor server, but it could provide a means to distinguish 32-bit Tor
11488 implementations from 64-bit Tor implementations. Fixes bug 12694;
11489 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
11493 - Warn and drop the circuit if we receive an inbound 'relay early'
11494 cell. Those used to be normal to receive on hidden service circuits
11495 due to bug 1038, but the buggy Tor versions are long gone from
11496 the network so we can afford to resume watching for them. Resolves
11497 the rest of bug 1038; bugfix on 0.2.1.19.
11498 - Correct a confusing error message when trying to extend a circuit
11499 via the control protocol but we don't know a descriptor or
11500 microdescriptor for one of the specified relays. Fixes bug 12718;
11501 bugfix on 0.2.3.1-alpha.
11502 - Avoid an illegal read from stack when initializing the TLS
11503 module using a version of OpenSSL without all of the ciphers
11504 used by the v2 link handshake. Fixes bug 12227; bugfix on
11505 0.2.4.8-alpha. Found by "starlight".
11508 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
11512 Changes in version 0.2.5.5-alpha - 2014-06-18
11513 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
11514 0.2.5.x release series, including a couple of DoS issues, some
11515 performance regressions, a large number of bugs affecting the Linux
11516 seccomp2 sandbox code, and various other bugfixes. It also adds
11517 diagnostic bugfixes for a few tricky issues that we're trying to
11520 o Major features (security, traffic analysis resistance):
11521 - Several major improvements to the algorithm used to decide when to
11522 close TLS connections. Previous versions of Tor closed connections
11523 at a fixed interval after the last time a non-padding cell was
11524 sent over the connection, regardless of the target of the
11525 connection. Now, we randomize the intervals by adding up to 50% of
11526 their base value, we measure the length of time since connection
11527 last had at least one circuit, and we allow connections to known
11528 ORs to remain open a little longer (15 minutes instead of 3
11529 minutes minimum). These changes should improve Tor's resistance
11530 against some kinds of traffic analysis, and lower some overhead
11531 from needlessly closed connections. Fixes ticket 6799.
11532 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
11534 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
11535 - Fix a memory leak that could occur if a microdescriptor parse
11536 fails during the tokenizing step. This bug could enable a memory
11537 exhaustion attack by directory servers. Fixes bug 11649; bugfix
11540 o Major bugfixes (security, directory authorities):
11541 - Directory authorities now include a digest of each relay's
11542 identity key as a part of its microdescriptor.
11544 This is a workaround for bug 11743 (reported by "cypherpunks"),
11545 where Tor clients do not support receiving multiple
11546 microdescriptors with the same SHA256 digest in the same
11547 consensus. When clients receive a consensus like this, they only
11548 use one of the relays. Without this fix, a hostile relay could
11549 selectively disable some client use of target relays by
11550 constructing a router descriptor with a different identity and the
11551 same microdescriptor parameters and getting the authorities to
11552 list it in a microdescriptor consensus. This fix prevents an
11553 attacker from causing a microdescriptor collision, because the
11554 router's identity is not forgeable.
11556 o Major bugfixes (relay):
11557 - Use a direct dirport connection when uploading non-anonymous
11558 descriptors to the directory authorities. Previously, relays would
11559 incorrectly use tunnel connections under a fairly wide variety of
11560 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
11561 - When a circuit accidentally has the same circuit ID for its
11562 forward and reverse direction, correctly detect the direction of
11563 cells using that circuit. Previously, this bug made roughly one
11564 circuit in a million non-functional. Fixes bug 12195; this is a
11565 bugfix on every version of Tor.
11567 o Major bugfixes (client, pluggable transports):
11568 - When managing pluggable transports, use OS notification facilities
11569 to learn if they have crashed, and don't attempt to kill any
11570 process that has already exited. Fixes bug 8746; bugfix
11573 o Minor features (diagnostic):
11574 - When logging a warning because of bug 7164, additionally check the
11575 hash table for consistency (as proposed on ticket 11737). This may
11576 help diagnose bug 7164.
11577 - When we log a heartbeat, log how many one-hop circuits we have
11578 that are at least 30 minutes old, and log status information about
11579 a few of them. This is an attempt to track down bug 8387.
11580 - When encountering an unexpected CR while writing text to a file on
11581 Windows, log the name of the file. Should help diagnosing
11583 - Give more specific warnings when a client notices that an onion
11584 handshake has failed. Fixes ticket 9635.
11585 - Add significant new logging code to attempt to diagnose bug 12184,
11586 where relays seem to run out of available circuit IDs.
11587 - Improve the diagnostic log message for bug 8387 even further to
11588 try to improve our odds of figuring out why one-hop directory
11589 circuits sometimes do not get closed.
11591 o Minor features (security, memory management):
11592 - Memory allocation tricks (mempools and buffer freelists) are now
11593 disabled by default. You can turn them back on with
11594 --enable-mempools and --enable-buf-freelists respectively. We're
11595 disabling these features because malloc performance is good enough
11596 on most platforms, and a similar feature in OpenSSL exacerbated
11597 exploitation of the Heartbleed attack. Resolves ticket 11476.
11599 o Minor features (security):
11600 - Apply the secure SipHash-2-4 function to the hash table mapping
11601 circuit IDs and channels to circuits. We missed this one when we
11602 were converting all the other hash functions to use SipHash back
11603 in 0.2.5.3-alpha. Resolves ticket 11750.
11605 o Minor features (build):
11606 - The configure script has a --disable-seccomp option to turn off
11607 support for libseccomp on systems that have it, in case it (or
11608 Tor's use of it) is broken. Resolves ticket 11628.
11610 o Minor features (other):
11611 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
11614 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
11615 - When running a hidden service, do not allow TunneledDirConns 0;
11616 this will keep the hidden service from running, and also
11617 make it publish its descriptors directly over HTTP. Fixes bug 10849;
11618 bugfix on 0.2.1.1-alpha.
11620 o Minor bugfixes (performance):
11621 - Avoid a bug where every successful connection made us recompute
11622 the flag telling us whether we have sufficient information to
11623 build circuits. Previously, we would forget our cached value
11624 whenever we successfully opened a channel (or marked a router as
11625 running or not running for any other reason), regardless of
11626 whether we had previously believed the router to be running. This
11627 forced us to run an expensive update operation far too often.
11628 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
11629 - Avoid using tor_memeq() for checking relay cell integrity. This
11630 removes a possible performance bottleneck. Fixes part of bug
11631 12169; bugfix on 0.2.1.31.
11633 o Minor bugfixes (compilation):
11634 - Fix compilation of test_status.c when building with MVSC. Bugfix
11635 on 0.2.5.4-alpha. Patch from Gisle Vanem.
11636 - Resolve GCC complaints on OpenBSD about discarding constness in
11637 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
11638 on 0.1.1.23. Patch from Dana Koch.
11639 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
11640 treatment of long and time_t as comparable types. Fixes part of
11641 bug 11633. Patch from Dana Koch.
11642 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
11643 11623; bugfix on 0.2.5.3-alpha.
11644 - When deciding whether to build the 64-bit curve25519
11645 implementation, detect platforms where we can compile 128-bit
11646 arithmetic but cannot link it. Fixes bug 11729; bugfix on
11647 0.2.4.8-alpha. Patch from "conradev".
11648 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
11649 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
11650 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
11653 o Minor bugfixes (Directory server):
11654 - When sending a compressed set of descriptors or microdescriptors,
11655 make sure to finalize the zlib stream. Previously, we would write
11656 all the compressed data, but if the last descriptor we wanted to
11657 send was missing or too old, we would not mark the stream as
11658 finished. This caused problems for decompression tools. Fixes bug
11659 11648; bugfix on 0.1.1.23.
11661 o Minor bugfixes (Linux seccomp sandbox):
11662 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
11663 11622; bugfix on 0.2.5.1-alpha.
11664 - Avoid crashing when re-opening listener ports with the seccomp
11665 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
11666 - Avoid crashing with the seccomp sandbox enabled along with
11667 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
11668 - When we receive a SIGHUP with the sandbox enabled, correctly
11669 support rotating our log files. Fixes bug 12032; bugfix
11671 - Avoid crash when running with sandboxing enabled and
11672 DirReqStatistics not disabled. Fixes bug 12035; bugfix
11674 - Fix a "BUG" warning when trying to write bridge-stats files with
11675 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
11677 - Prevent the sandbox from crashing on startup when run with the
11678 --enable-expensive-hardening configuration option. Fixes bug
11679 11477; bugfix on 0.2.5.4-alpha.
11680 - When running with DirPortFrontPage and sandboxing both enabled,
11681 reload the DirPortFrontPage correctly when restarting. Fixes bug
11682 12028; bugfix on 0.2.5.1-alpha.
11683 - Don't try to enable the sandbox when using the Tor binary to check
11684 its configuration, hash a passphrase, or so on. Doing so was
11685 crashing on startup for some users. Fixes bug 11609; bugfix
11687 - Avoid warnings when running with sandboxing and node statistics
11688 enabled at the same time. Fixes part of 12064; bugfix on
11689 0.2.5.1-alpha. Patch from Michael Wolf.
11690 - Avoid warnings when running with sandboxing enabled at the same
11691 time as cookie authentication, hidden services, or directory
11692 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
11693 - Do not allow options that require calls to exec to be enabled
11694 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
11695 bug 12043; bugfix on 0.2.5.1-alpha.
11696 - Handle failures in getpwnam()/getpwuid() when running with the
11697 User option set and the Linux syscall sandbox enabled. Fixes bug
11698 11946; bugfix on 0.2.5.1-alpha.
11699 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
11700 to avoid calling getaddrinfo() after installing the sandbox
11701 filters. Previously, it preloaded a cache with the IPv4 address
11702 for our hostname, and nothing else. Now, it loads the cache with
11703 every address that it used to initialize the Tor process. Fixes
11704 bug 11970; bugfix on 0.2.5.1-alpha.
11706 o Minor bugfixes (pluggable transports):
11707 - Enable the ExtORPortCookieAuthFile option, to allow changing the
11708 default location of the authentication token for the extended OR
11709 Port as used by sever-side pluggable transports. We had
11710 implemented this option before, but the code to make it settable
11711 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
11712 - Avoid another 60-second delay when starting Tor in a pluggable-
11713 transport-using configuration when we already have cached
11714 descriptors for our bridges. Fixes bug 11965; bugfix
11717 o Minor bugfixes (client):
11718 - Avoid "Tried to open a socket with DisableNetwork set" warnings
11719 when starting a client with bridges configured and DisableNetwork
11720 set. (Tor launcher starts Tor with DisableNetwork set the first
11721 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
11723 o Minor bugfixes (testing):
11724 - The Python parts of the test scripts now work on Python 3 as well
11725 as Python 2, so systems where '/usr/bin/python' is Python 3 will
11726 no longer have the tests break. Fixes bug 11608; bugfix
11728 - When looking for versions of python that we could run the tests
11729 with, check for "python2.7" and "python3.3"; previously we were
11730 only looking for "python", "python2", and "python3". Patch from
11731 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
11732 - Fix all valgrind warnings produced by the unit tests. There were
11733 over a thousand memory leak warnings previously, mostly produced
11734 by forgetting to free things in the unit test code. Fixes bug
11735 11618, bugfixes on many versions of Tor.
11737 o Minor bugfixes (tor-fw-helper):
11738 - Give a correct log message when tor-fw-helper fails to launch.
11739 (Previously, we would say something like "tor-fw-helper sent us a
11740 string we could not parse".) Fixes bug 9781; bugfix
11743 o Minor bugfixes (relay, threading):
11744 - Check return code on spawn_func() in cpuworker code, so that we
11745 don't think we've spawned a nonworking cpuworker and write junk to
11746 it forever. Fix related to bug 4345; bugfix on all released Tor
11747 versions. Found by "skruffy".
11748 - Use a pthread_attr to make sure that spawn_func() cannot return an
11749 error while at the same time launching a thread. Fix related to
11750 bug 4345; bugfix on all released Tor versions. Reported
11753 o Minor bugfixes (relay, oom prevention):
11754 - Correctly detect the total available system memory. We tried to do
11755 this in 0.2.5.4-alpha, but the code was set up to always return an
11756 error value, even on success. Fixes bug 11805; bugfix
11759 o Minor bugfixes (relay, other):
11760 - We now drop CREATE cells for already-existent circuit IDs and for
11761 zero-valued circuit IDs, regardless of other factors that might
11762 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
11764 - Avoid an illegal read from stack when initializing the TLS module
11765 using a version of OpenSSL without all of the ciphers used by the
11766 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
11768 - When rejecting DATA cells for stream_id zero, still count them
11769 against the circuit's deliver window so that we don't fail to send
11770 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
11772 o Minor bugfixes (logging):
11773 - Fix a misformatted log message about delayed directory fetches.
11774 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
11775 - Squelch a spurious LD_BUG message "No origin circuit for
11776 successful SOCKS stream" in certain hidden service failure cases;
11780 - Include a tor.service file in contrib/dist for use with systemd.
11781 Some distributions will be able to use this file unmodified;
11782 others will need to tweak it, or write their own. Patch from Jamie
11783 Nguyen; resolves ticket 8368.
11786 - Clean up several option names in the manpage to match their real
11787 names, add the missing documentation for a couple of testing and
11788 directory authority options, remove the documentation for a
11789 V2-directory fetching option that no longer exists. Resolves
11791 - Correct the documentation so that it lists the correct directory
11792 for the stats files. (They are in a subdirectory called "stats",
11794 - In the manpage, move more authority-only options into the
11795 directory authority section so that operators of regular directory
11796 caches don't get confused.
11799 - The contrib directory has been sorted and tidied. Before, it was
11800 an unsorted dumping ground for useful and not-so-useful things.
11801 Now, it is divided based on functionality, and the items which
11802 seemed to be nonfunctional or useless have been removed. Resolves
11803 ticket 8966; based on patches from "rl1987".
11806 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
11807 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
11808 - The TunnelDirConns and PreferTunnelledDirConns options no longer
11809 exist; tunneled directory connections have been available since
11810 0.1.2.5-alpha, and turning them off is not a good idea. This is a
11811 brute-force fix for 10849, where "TunnelDirConns 0" would break
11815 Changes in version 0.2.4.22 - 2014-05-16
11816 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
11817 alpha release series. These include blocking all authority signing
11818 keys that may have been affected by the OpenSSL "heartbleed" bug,
11819 choosing a far more secure set of TLS ciphersuites by default, closing
11820 a couple of memory leaks that could be used to run a target relay out
11821 of RAM, and several others.
11823 o Major features (security, backport from 0.2.5.4-alpha):
11824 - Block authority signing keys that were used on authorities
11825 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
11826 don't have any evidence that these keys _were_ compromised; we're
11827 doing this to be prudent.) Resolves ticket 11464.
11829 o Major bugfixes (security, OOM):
11830 - Fix a memory leak that could occur if a microdescriptor parse
11831 fails during the tokenizing step. This bug could enable a memory
11832 exhaustion attack by directory servers. Fixes bug 11649; bugfix
11835 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
11836 - The relay ciphersuite list is now generated automatically based on
11837 uniform criteria, and includes all OpenSSL ciphersuites with
11838 acceptable strength and forward secrecy. Previously, we had left
11839 some perfectly fine ciphersuites unsupported due to omission or
11840 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
11841 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
11842 - Relays now trust themselves to have a better view than clients of
11843 which TLS ciphersuites are better than others. (Thanks to bug
11844 11513, the relay list is now well-considered, whereas the client
11845 list has been chosen mainly for anti-fingerprinting purposes.)
11846 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
11847 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
11848 AES128. Resolves ticket 11528.
11849 - Clients now try to advertise the same list of ciphersuites as
11850 Firefox 28. This change enables selection of (fast) GCM
11851 ciphersuites, disables some strange old ciphers, and stops
11852 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
11853 Resolves ticket 11438.
11855 o Minor bugfixes (configuration, security):
11856 - When running a hidden service, do not allow TunneledDirConns 0:
11857 trying to set that option together with a hidden service would
11858 otherwise prevent the hidden service from running, and also make
11859 it publish its descriptors directly over HTTP. Fixes bug 10849;
11860 bugfix on 0.2.1.1-alpha.
11862 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
11863 - Avoid sending a garbage value to the controller when a circuit is
11864 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
11866 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
11867 - Stop leaking memory when we successfully resolve a PTR record.
11868 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
11870 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
11871 - Avoid 60-second delays in the bootstrapping process when Tor is
11872 launching for a second time while using bridges. Fixes bug 9229;
11873 bugfix on 0.2.0.3-alpha.
11875 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
11876 - Give the correct URL in the warning message when trying to run a
11877 relay on an ancient version of Windows. Fixes bug 9393.
11879 o Minor bugfixes (compilation):
11880 - Fix a compilation error when compiling with --disable-curve25519.
11881 Fixes bug 9700; bugfix on 0.2.4.17-rc.
11884 - Downgrade the warning severity for the the "md was still
11885 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
11886 for trying to diagnose this bug, and the current warning in
11887 earlier versions of tor achieves nothing useful. Addresses warning
11890 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
11891 - When we run out of usable circuit IDs on a channel, log only one
11892 warning for the whole channel, and describe how many circuits
11893 there were on the channel. Fixes part of ticket 11553.
11895 o Minor features (security, backport from 0.2.5.4-alpha):
11896 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
11897 leave the default at 8GBytes), to better support Raspberry Pi
11898 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
11900 o Documentation (backport from 0.2.5.4-alpha):
11901 - Correctly document that we search for a system torrc file before
11902 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
11906 Changes in version 0.2.5.4-alpha - 2014-04-25
11907 Tor 0.2.5.4-alpha includes several security and performance
11908 improvements for clients and relays, including blacklisting authority
11909 signing keys that were used while susceptible to the OpenSSL
11910 "heartbleed" bug, fixing two expensive functions on busy relays,
11911 improved TLS ciphersuite preference lists, support for run-time
11912 hardening on compilers that support AddressSanitizer, and more work on
11913 the Linux sandbox code.
11915 There are also several usability fixes for clients (especially clients
11916 that use bridges), two new TransPort protocols supported (one on
11917 OpenBSD, one on FreeBSD), and various other bugfixes.
11919 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
11920 have accumulated many known flaws; everyone should upgrade.
11922 o Major features (security):
11923 - If you don't specify MaxMemInQueues yourself, Tor now tries to
11924 pick a good value based on your total system memory. Previously,
11925 the default was always 8 GB. You can still override the default by
11926 setting MaxMemInQueues yourself. Resolves ticket 11396.
11927 - Block authority signing keys that were used on authorities
11928 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
11929 don't have any evidence that these keys _were_ compromised; we're
11930 doing this to be prudent.) Resolves ticket 11464.
11932 o Major features (relay performance):
11933 - Speed up server-side lookups of rendezvous and introduction point
11934 circuits by using hashtables instead of linear searches. These
11935 functions previously accounted between 3 and 7% of CPU usage on
11936 some busy relays. Resolves ticket 9841.
11937 - Avoid wasting CPU when extending a circuit over a channel that is
11938 nearly out of circuit IDs. Previously, we would do a linear scan
11939 over possible circuit IDs before finding one or deciding that we
11940 had exhausted our possibilities. Now, we try at most 64 random
11941 circuit IDs before deciding that we probably won't succeed. Fixes
11942 a possible root cause of ticket 11553.
11944 o Major features (seccomp2 sandbox, Linux only):
11945 - The seccomp2 sandbox can now run a test network for multiple hours
11946 without crashing. The sandbox is still experimental, and more bugs
11947 will probably turn up. To try it, enable "Sandbox 1" on a Linux
11948 host. Resolves ticket 11351.
11949 - Strengthen sandbox code: the sandbox can now test the arguments
11950 for rename(), and blocks _sysctl() entirely. Resolves another part
11952 - When the sandbox blocks a system call, it now tries to log a stack
11953 trace before exiting. Resolves ticket 11465.
11955 o Major bugfixes (TLS cipher selection):
11956 - The relay ciphersuite list is now generated automatically based on
11957 uniform criteria, and includes all OpenSSL ciphersuites with
11958 acceptable strength and forward secrecy. Previously, we had left
11959 some perfectly fine ciphersuites unsupported due to omission or
11960 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
11961 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
11962 - Relays now trust themselves to have a better view than clients of
11963 which TLS ciphersuites are better than others. (Thanks to bug
11964 11513, the relay list is now well-considered, whereas the client
11965 list has been chosen mainly for anti-fingerprinting purposes.)
11966 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
11967 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
11968 AES128. Resolves ticket 11528.
11969 - Clients now try to advertise the same list of ciphersuites as
11970 Firefox 28. This change enables selection of (fast) GCM
11971 ciphersuites, disables some strange old ciphers, and stops
11972 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
11973 Resolves ticket 11438.
11975 o Major bugfixes (bridge client):
11976 - Avoid 60-second delays in the bootstrapping process when Tor is
11977 launching for a second time while using bridges. Fixes bug 9229;
11978 bugfix on 0.2.0.3-alpha.
11980 o Minor features (transparent proxy, *BSD):
11981 - Support FreeBSD's ipfw firewall interface for TransPort ports on
11982 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
11983 10267; patch from "yurivict".
11984 - Support OpenBSD's divert-to rules with the pf firewall for
11985 transparent proxy ports. To enable it, set "TransProxyType
11986 pf-divert". This allows Tor to run a TransPort transparent proxy
11987 port on OpenBSD 4.4 or later without root privileges. See the
11988 pf.conf(5) manual page for information on configuring pf to use
11989 divert-to rules. Closes ticket 10896; patch from Dana Koch.
11991 o Minor features (security):
11992 - New --enable-expensive-hardening option to enable security
11993 hardening options that consume nontrivial amounts of CPU and
11994 memory. Right now, this includes AddressSanitizer and UbSan, which
11995 are supported in newer versions of GCC and Clang. Closes ticket
11998 o Minor features (log verbosity):
11999 - Demote the message that we give when a flushing connection times
12000 out for too long from NOTICE to INFO. It was usually meaningless.
12001 Resolves ticket 5286.
12002 - Don't log so many notice-level bootstrapping messages at startup
12003 about downloading descriptors. Previously, we'd log a notice
12004 whenever we learned about more routers. Now, we only log a notice
12005 at every 5% of progress. Fixes bug 9963.
12006 - Warn less verbosely when receiving a malformed
12007 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
12008 - When we run out of usable circuit IDs on a channel, log only one
12009 warning for the whole channel, and describe how many circuits
12010 there were on the channel. Fixes part of ticket 11553.
12012 o Minor features (relay):
12013 - If a circuit timed out for at least 3 minutes, check if we have a
12014 new external IP address, and publish a new descriptor with the new
12015 IP address if it changed. Resolves ticket 2454.
12017 o Minor features (controller):
12018 - Make the entire exit policy available from the control port via
12019 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
12021 - Because of the fix for ticket 11396, the real limit for memory
12022 usage may no longer match the configured MaxMemInQueues value. The
12023 real limit is now exposed via GETINFO limits/max-mem-in-queues.
12025 o Minor features (bridge client):
12026 - Report a more useful failure message when we can't connect to a
12027 bridge because we don't have the right pluggable transport
12028 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
12030 o Minor features (diagnostic):
12031 - Add more log messages to diagnose bug 7164, which causes
12032 intermittent "microdesc_free() called but md was still referenced"
12033 warnings. We now include more information, to figure out why we
12034 might be cleaning a microdescriptor for being too old if it's
12035 still referenced by a live node_t object.
12037 o Minor bugfixes (client, DNSPort):
12038 - When using DNSPort, try to respond to AAAA requests with AAAA
12039 answers. Previously, we hadn't looked at the request type when
12040 deciding which answer type to prefer. Fixes bug 10468; bugfix on
12042 - When receiving a DNS query for an unsupported record type, reply
12043 with no answer rather than with a NOTIMPL error. This behavior
12044 isn't correct either, but it will break fewer client programs, we
12045 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
12048 o Minor bugfixes (exit relay):
12049 - Stop leaking memory when we successfully resolve a PTR record.
12050 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
12052 o Minor bugfixes (bridge client):
12053 - Stop accepting bridge lines containing hostnames. Doing so would
12054 cause clients to perform DNS requests on the hostnames, which was
12055 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
12056 - Avoid a 60-second delay in the bootstrapping process when a Tor
12057 client with pluggable transports re-reads its configuration at
12058 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
12060 o Minor bugfixes (client, logging during bootstrap):
12061 - Warn only once if we start logging in an unsafe way. Previously,
12062 we complain as many times as we had problems. Fixes bug 9870;
12063 bugfix on 0.2.5.1-alpha.
12064 - Only report the first fatal bootstrap error on a given OR
12065 connection. This stops us from telling the controller bogus error
12066 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
12067 - Be more helpful when trying to run sandboxed on Linux without
12068 libseccomp. Instead of saying "Sandbox is not implemented on this
12069 platform", we now explain that we need to be built with
12070 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
12071 - Avoid generating spurious warnings when starting with
12072 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
12075 o Minor bugfixes (closing OR connections):
12076 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
12077 check if it's an or_connection_t and correctly call
12078 connection_or_close_for_error() rather than
12079 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
12081 - When closing all connections on setting DisableNetwork to 1, use
12082 connection_or_close_normally() rather than closing OR connections
12083 out from under the channel layer. Fixes bug 11306; bugfix on
12086 o Minor bugfixes (controller):
12087 - Avoid sending a garbage value to the controller when a circuit is
12088 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
12090 o Minor bugfixes (tor-fw-helper):
12091 - Allow tor-fw-helper to build again by adding src/ext to its
12092 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
12094 o Minor bugfixes (bridges):
12095 - Avoid potential crashes or bad behavior when launching a
12096 server-side managed proxy with ORPort or ExtORPort temporarily
12097 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
12099 o Minor bugfixes (platform-specific):
12100 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
12101 bug 11426; bugfix on 0.2.5.3-alpha.
12102 - When dumping a malformed directory object to disk, save it in
12103 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
12105 - Don't report failures from make_socket_reuseable() on incoming
12106 sockets on OSX: this can happen when incoming connections close
12107 early. Fixes bug 10081.
12109 o Minor bugfixes (trivial memory leaks):
12110 - Fix a small memory leak when signing a directory object. Fixes bug
12111 11275; bugfix on 0.2.4.13-alpha.
12112 - Free placeholder entries in our circuit table at exit; fixes a
12113 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
12114 - Don't re-initialize a second set of OpenSSL mutexes when starting
12115 up. Previously, we'd make one set of mutexes, and then immediately
12116 replace them with another. Fixes bug 11726; bugfix on
12118 - Resolve some memory leaks found by coverity in the unit tests, on
12119 exit in tor-gencert, and on a failure to compute digests for our
12120 own keys when generating a v3 networkstatus vote. These leaks
12121 should never have affected anyone in practice.
12123 o Minor bugfixes (hidden service):
12124 - Only retry attempts to connect to a chosen rendezvous point 8
12125 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
12127 o Minor bugfixes (misc code correctness):
12128 - Fix various instances of undefined behavior in channeltls.c,
12129 tor_memmem(), and eventdns.c that would cause us to construct
12130 pointers to memory outside an allocated object. (These invalid
12131 pointers were not accessed, but C does not even allow them to
12132 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
12133 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
12134 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
12135 fix some miscellaneous errors in our tests and codebase. Fixes bug
12136 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
12137 - Always check return values for unlink, munmap, UnmapViewOfFile;
12138 check strftime return values more often. In some cases all we can
12139 do is report a warning, but this may help prevent deeper bugs from
12140 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
12142 - Fix numerous warnings from the clang "scan-build" static analyzer.
12143 Some of these are programming style issues; some of them are false
12144 positives that indicated awkward code; some are undefined behavior
12145 cases related to constructing (but not using) invalid pointers;
12146 some are assumptions about API behavior; some are (harmlessly)
12147 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
12148 correct; and one or two are genuine bugs that weren't reachable
12149 from the rest of the program. Fixes bug 8793; bugfixes on many,
12153 - Build the torify.1 manpage again. Previously, we were only trying
12154 to build it when also building tor-fw-helper. That's why we didn't
12155 notice that we'd broken the ability to build it. Fixes bug 11321;
12156 bugfix on 0.2.5.1-alpha.
12157 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
12158 11061; bugfix on 0.2.4.7-alpha.
12159 - Correctly document that we search for a system torrc file before
12160 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
12162 - Resolve warnings from Doxygen.
12164 o Code simplifications and refactoring:
12165 - Remove is_internal_IP() function. Resolves ticket 4645.
12166 - Remove unused function circuit_dump_by_chan from circuitlist.c.
12167 Closes issue 9107; patch from "marek".
12168 - Change our use of the ENUM_BF macro to avoid declarations that
12171 o Deprecated versions:
12172 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
12173 attention for some while. Directory authorities no longer accept
12174 descriptors from relays running any version of Tor prior to Tor
12175 0.2.3.16-alpha. Resolves ticket 11149.
12178 - New macros in test.h to simplify writing mock-functions for unit
12179 tests. Part of ticket 11507. Patch from Dana Koch.
12180 - Complete tests for the status.c module. Resolves ticket 11507.
12181 Patch from Dana Koch.
12184 - Remove all code for the long unused v1 directory protocol.
12185 Resolves ticket 11070.
12188 Changes in version 0.2.5.3-alpha - 2014-03-22
12189 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
12190 two new anti-DoS features for Tor relays, resolves a bug that kept
12191 SOCKS5 support for IPv6 from working, fixes several annoying usability
12192 issues for bridge users, and removes more old code for unused
12195 The Tor 0.2.5.x release series is now in patch-freeze: no feature
12196 patches not already written will be considered for inclusion in 0.2.5.x.
12198 o Major features (relay security, DoS-resistance):
12199 - When deciding whether we have run out of memory and we need to
12200 close circuits, also consider memory allocated in buffers for
12201 streams attached to each circuit.
12203 This change, which extends an anti-DoS feature introduced in
12204 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
12205 better resist more memory-based DoS attacks than before. Since the
12206 MaxMemInCellQueues option now applies to all queues, it is renamed
12207 to MaxMemInQueues. This feature fixes bug 10169.
12208 - Avoid hash-flooding denial-of-service attacks by using the secure
12209 SipHash-2-4 hash function for our hashtables. Without this
12210 feature, an attacker could degrade performance of a targeted
12211 client or server by flooding their data structures with a large
12212 number of entries to be stored at the same hash table position,
12213 thereby slowing down the Tor instance. With this feature, hash
12214 table positions are derived from a randomized cryptographic key,
12215 and an attacker cannot predict which entries will collide. Closes
12217 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
12218 the default at 8GBytes), to better support Raspberry Pi users. Fixes
12219 bug 9686; bugfix on 0.2.4.14-alpha.
12221 o Minor features (bridges, pluggable transports):
12222 - Bridges now write the SHA1 digest of their identity key
12223 fingerprint (that is, a hash of a hash of their public key) to
12224 notice-level logs, and to a new hashed-fingerprint file. This
12225 information will help bridge operators look up their bridge in
12226 Globe and similar tools. Resolves ticket 10884.
12227 - Improve the message that Tor displays when running as a bridge
12228 using pluggable transports without an Extended ORPort listener.
12229 Also, log the message in the log file too. Resolves ticket 11043.
12231 o Minor features (other):
12232 - Add a new option, PredictedPortsRelevanceTime, to control how long
12233 after having received a request to connect to a given port Tor
12234 will try to keep circuits ready in anticipation of future requests
12235 for that port. Patch from "unixninja92"; implements ticket 9176.
12236 - Generate a warning if any ports are listed in the SocksPolicy,
12237 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
12238 AuthDirBadExit options. (These options only support address
12239 ranges.) Fixes part of ticket 11108.
12240 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
12243 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
12244 - Build without warnings under clang 3.4. (We have some macros that
12245 define static functions only some of which will get used later in
12246 the module. Starting with clang 3.4, these give a warning unless the
12247 unused attribute is set on them.) Resolves ticket 10904.
12248 - Fix build warnings about missing "a2x" comment when building the
12249 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
12250 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
12252 o Minor bugfixes (client):
12253 - Improve the log message when we can't connect to a hidden service
12254 because all of the hidden service directory nodes hosting its
12255 descriptor are excluded. Improves on our fix for bug 10722, which
12256 was a bugfix on 0.2.0.10-alpha.
12257 - Raise a control port warning when we fail to connect to all of
12258 our bridges. Previously, we didn't inform the controller, and
12259 the bootstrap process would stall. Fixes bug 11069; bugfix on
12261 - Exit immediately when a process-owning controller exits.
12262 Previously, tor relays would wait for a little while after their
12263 controller exited, as if they had gotten an INT signal -- but this
12264 was problematic, since there was no feedback for the user. To do a
12265 clean shutdown, controllers should send an INT signal and give Tor
12266 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
12267 - Stop attempting to connect to bridges before our pluggable
12268 transports are configured (harmless but resulted in some erroneous
12269 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
12270 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
12271 generating incorrect SOCKS5 responses, and confusing client
12272 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
12274 o Minor bugfixes (relays and bridges):
12275 - Avoid crashing on a malformed resolv.conf file when running a
12276 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
12277 - Non-exit relays no longer launch mock DNS requests to check for
12278 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
12279 non-exit relays stopped servicing DNS requests. Fixes bug 965;
12280 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
12281 - Bridges now report complete directory request statistics. Related
12282 to bug 5824; bugfix on 0.2.2.1-alpha.
12283 - Bridges now never collect statistics that were designed for
12284 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
12285 - Stop giving annoying warning messages when we decide not to launch
12286 a pluggable transport proxy that we don't need (because there are
12287 no bridges configured to use it). Resolves ticket 5018; bugfix
12289 - Give the correct URL in the warning message when trying to run a
12290 relay on an ancient version of Windows. Fixes bug 9393.
12292 o Minor bugfixes (backtrace support):
12293 - Support automatic backtraces on more platforms by using the
12294 "-fasynchronous-unwind-tables" compiler option. This option is
12295 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
12296 is on by default and table generation is not. This doesn't yet
12297 add Windows support; only Linux, OSX, and some BSDs are affected.
12298 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
12299 - Avoid strange behavior if two threads hit failed assertions at the
12300 same time and both try to log backtraces at once. (Previously, if
12301 this had happened, both threads would have stored their intermediate
12302 results in the same buffer, and generated junk outputs.) Reported by
12303 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
12304 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
12305 0.2.5.2-alpha; patch from Nick Hopper.
12307 o Minor bugfixes (unit tests):
12308 - Fix a small bug in the unit tests that might have made the tests
12309 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
12310 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
12313 - Remove all remaining code related to version-0 hidden service
12314 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
12315 the rest of bug 10841.
12318 - Document in the manpage that "KBytes" may also be written as
12319 "kilobytes" or "KB", that "Kbits" may also be written as
12320 "kilobits", and so forth. Closes ticket 9222.
12321 - Document that the ClientOnly config option overrides ORPort.
12322 Our old explanation made ClientOnly sound as though it did
12323 nothing at all. Resolves bug 9059.
12324 - Explain that SocksPolicy, DirPolicy, and similar options don't
12325 take port arguments. Fixes the other part of ticket 11108.
12326 - Fix a comment about the rend_server_descriptor_t.protocols field
12327 to more accurately describe its range. Also, make that field
12328 unsigned, to more accurately reflect its usage. Fixes bug 9099;
12329 bugfix on 0.2.1.5-alpha.
12330 - Fix the manpage's description of HiddenServiceAuthorizeClient:
12331 the maximum client name length is 16, not 19. Fixes bug 11118;
12332 bugfix on 0.2.1.6-alpha.
12334 o Code simplifications and refactoring:
12335 - Get rid of router->address, since in all cases it was just the
12336 string representation of router->addr. Resolves ticket 5528.
12338 o Test infrastructure:
12339 - Update to the latest version of tinytest.
12340 - Improve the tinytest implementation of string operation tests so
12341 that comparisons with NULL strings no longer crash the tests; they
12342 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
12345 Changes in version 0.2.4.21 - 2014-02-28
12346 Tor 0.2.4.21 further improves security against potential adversaries who
12347 find breaking 1024-bit crypto doable, and backports several stability
12348 and robustness patches from the 0.2.5 branch.
12350 o Major features (client security):
12351 - When we choose a path for a 3-hop circuit, make sure it contains
12352 at least one relay that supports the NTor circuit extension
12353 handshake. Otherwise, there is a chance that we're building
12354 a circuit that's worth attacking by an adversary who finds
12355 breaking 1024-bit crypto doable, and that chance changes the game
12356 theory. Implements ticket 9777.
12359 - Do not treat streams that fail with reason
12360 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
12361 since it could also indicate an ENETUNREACH connection error. Fixes
12362 part of bug 10777; bugfix on 0.2.4.8-alpha.
12364 o Code simplification and refactoring:
12365 - Remove data structures which were introduced to implement the
12366 CellStatistics option: they are now redundant with the new timestamp
12367 field in the regular packed_cell_t data structure, which we did
12368 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
12371 - Always clear OpenSSL bignums before freeing them -- even bignums
12372 that don't contain secrets. Resolves ticket 10793. Patch by
12374 - Build without warnings under clang 3.4. (We have some macros that
12375 define static functions only some of which will get used later in
12376 the module. Starting with clang 3.4, these give a warning unless the
12377 unused attribute is set on them.) Resolves ticket 10904.
12378 - Update geoip and geoip6 files to the February 7 2014 Maxmind
12379 GeoLite2 Country database.
12382 - Set the listen() backlog limit to the largest actually supported
12383 on the system, not to the value in a header file. Fixes bug 9716;
12384 bugfix on every released Tor.
12385 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
12386 exit node as a NOROUTE error, not an INTERNAL error, since they
12387 can apparently happen when trying to connect to the wrong sort
12388 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
12389 - Fix build warnings about missing "a2x" comment when building the
12390 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
12391 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
12392 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
12393 not entirely remove it from the connection lists. Fixes bug 9602;
12394 bugfix on 0.2.4.4-alpha.
12395 - Fix a segmentation fault in our benchmark code when running with
12396 Fedora's OpenSSL package, or any other OpenSSL that provides
12397 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
12398 - Turn "circuit handshake stats since last time" log messages into a
12399 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
12401 o Documentation fixes:
12402 - Document that all but one DirPort entry must have the NoAdvertise
12403 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
12406 Changes in version 0.2.5.2-alpha - 2014-02-13
12407 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
12408 like the "poor random number generation" fix and the "building too many
12409 circuits" fix. It also further improves security against potential
12410 adversaries who find breaking 1024-bit crypto doable, and launches
12411 pluggable transports on demand (which gets us closer to integrating
12412 pluggable transport support by default -- not to be confused with Tor
12413 bundles enabling pluggable transports and bridges by default).
12415 o Major features (client security):
12416 - When we choose a path for a 3-hop circuit, make sure it contains
12417 at least one relay that supports the NTor circuit extension
12418 handshake. Otherwise, there is a chance that we're building
12419 a circuit that's worth attacking by an adversary who finds
12420 breaking 1024-bit crypto doable, and that chance changes the game
12421 theory. Implements ticket 9777.
12422 - Clients now look at the "usecreatefast" consensus parameter to
12423 decide whether to use CREATE_FAST or CREATE cells for the first hop
12424 of their circuit. This approach can improve security on connections
12425 where Tor's circuit handshake is stronger than the available TLS
12426 connection security levels, but the tradeoff is more computational
12427 load on guard relays. Implements proposal 221. Resolves ticket 9386.
12429 o Major features (bridges):
12430 - Don't launch pluggable transport proxies if we don't have any
12431 bridges configured that would use them. Now we can list many
12432 pluggable transports, and Tor will dynamically start one when it
12433 hears a bridge address that needs it. Resolves ticket 5018.
12434 - The bridge directory authority now assigns status flags (Stable,
12435 Guard, etc) to bridges based on thresholds calculated over all
12436 Running bridges. Now bridgedb can finally make use of its features
12437 to e.g. include at least one Stable bridge in its answers. Fixes
12440 o Major features (other):
12441 - Extend ORCONN controller event to include an "ID" parameter,
12442 and add four new controller event types CONN_BW, CIRC_BW,
12443 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
12444 The new events are emitted in private Tor networks only, with the
12445 goal of being able to better track performance and load during
12446 full-network simulations. Implements proposal 218 and ticket 7359.
12447 - On some platforms (currently: recent OSX versions, glibc-based
12448 platforms that support the ELF format, and a few other
12449 Unix-like operating systems), Tor can now dump stack traces
12450 when a crash occurs or an assertion fails. By default, traces
12451 are dumped to stderr (if possible) and to any logs that are
12452 reporting errors. Implements ticket 9299.
12455 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
12456 not entirely remove it from the connection lists. Fixes bug 9602;
12457 bugfix on 0.2.4.4-alpha.
12458 - Do not treat streams that fail with reason
12459 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
12460 since it could also indicate an ENETUNREACH connection error. Fixes
12461 part of bug 10777; bugfix on 0.2.4.8-alpha.
12463 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
12464 - Do not allow OpenSSL engines to replace the PRNG, even when
12465 HardwareAccel is set. The only default builtin PRNG engine uses
12466 the Intel RDRAND instruction to replace the entire PRNG, and
12467 ignores all attempts to seed it with more entropy. That's
12468 cryptographically stupid: the right response to a new alleged
12469 entropy source is never to discard all previously used entropy
12470 sources. Fixes bug 10402; works around behavior introduced in
12471 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
12473 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
12474 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
12475 - Avoid launching spurious extra circuits when a stream is pending.
12476 This fixes a bug where any circuit that _wasn't_ unusable for new
12477 streams would be treated as if it were, causing extra circuits to
12478 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
12480 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12481 - No longer stop reading or writing on cpuworker connections when
12482 our rate limiting buckets go empty. Now we should handle circuit
12483 handshake requests more promptly. Resolves bug 9731.
12484 - Stop trying to bootstrap all our directory information from
12485 only our first guard. Discovered while fixing bug 9946; bugfix
12488 o Minor features (bridges, pluggable transports):
12489 - Add threshold cutoffs to the networkstatus document created by
12490 the Bridge Authority. Fixes bug 1117.
12491 - On Windows, spawn background processes using the CREATE_NO_WINDOW
12492 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
12493 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
12494 Vidalia set this option for us.) Implements ticket 10297.
12496 o Minor features (security):
12497 - Always clear OpenSSL bignums before freeing them -- even bignums
12498 that don't contain secrets. Resolves ticket 10793. Patch by
12499 Florent Daignière.
12501 o Minor features (config options and command line):
12502 - Add an --allow-missing-torrc commandline option that tells Tor to
12503 run even if the configuration file specified by -f is not available.
12504 Implements ticket 10060.
12505 - Add support for the TPROXY transparent proxying facility on Linux.
12506 See documentation for the new TransProxyType option for more
12507 details. Implementation by "thomo". Closes ticket 10582.
12509 o Minor features (controller):
12510 - Add a new "HS_DESC" controller event that reports activities
12511 related to hidden service descriptors. Resolves ticket 8510.
12512 - New "DROPGUARDS" controller command to forget all current entry
12513 guards. Not recommended for ordinary use, since replacing guards
12514 too frequently makes several attacks easier. Resolves ticket 9934;
12517 o Minor features (build):
12518 - Assume that a user using ./configure --host wants to cross-compile,
12519 and give an error if we cannot find a properly named
12520 tool-chain. Add a --disable-tool-name-check option to proceed
12521 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
12522 - If we run ./configure and the compiler recognizes -fstack-protector
12523 but the linker rejects it, warn the user about a potentially missing
12524 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
12526 o Minor features (testing):
12527 - If Python is installed, "make check" now runs extra tests beyond
12528 the unit test scripts.
12529 - When bootstrapping a test network, sometimes very few relays get
12530 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
12531 specify a set of relays which should be voted Guard regardless of
12532 their uptime or bandwidth. Addresses ticket 9206.
12534 o Minor features (log messages):
12535 - When ServerTransportPlugin is set on a bridge, Tor can write more
12536 useful statistics about bridge use in its extrainfo descriptors,
12537 but only if the Extended ORPort ("ExtORPort") is set too. Add a
12538 log message to inform the user in this case. Resolves ticket 9651.
12539 - When receiving a new controller connection, log the origin address.
12540 Resolves ticket 9698; patch from "sigpipe".
12541 - When logging OpenSSL engine status at startup, log the status of
12542 more engines. Fixes ticket 10043; patch from Joshua Datko.
12543 - Turn "circuit handshake stats since last time" log messages into a
12544 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
12546 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12547 - Improve the circuit queue out-of-memory handler. Previously, when
12548 we ran low on memory, we'd close whichever circuits had the most
12549 queued cells. Now, we close those that have the *oldest* queued
12550 cells, on the theory that those are most responsible for us
12551 running low on memory. Based on analysis from a forthcoming paper
12552 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
12553 - Generate bootstrapping status update events correctly when fetching
12554 microdescriptors. Fixes bug 9927.
12555 - Update to the October 2 2013 Maxmind GeoLite Country database.
12557 o Minor bugfixes (clients):
12558 - When closing a channel that has already been open, do not close
12559 pending circuits that were waiting to connect to the same relay.
12560 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
12563 o Minor bugfixes (relays):
12564 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
12565 exit node as a NOROUTE error, not an INTERNAL error, since they
12566 can apparently happen when trying to connect to the wrong sort
12567 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
12569 o Minor bugfixes (bridges):
12570 - Fix a bug where the first connection works to a bridge that uses a
12571 pluggable transport with client-side parameters, but we don't send
12572 the client-side parameters on subsequent connections. (We don't
12573 use any pluggable transports with client-side parameters yet,
12574 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
12575 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
12577 o Minor bugfixes (node selection):
12578 - If ExcludeNodes is set, consider non-excluded hidden service
12579 directory servers before excluded ones. Do not consider excluded
12580 hidden service directory servers at all if StrictNodes is
12581 set. (Previously, we would sometimes decide to connect to those
12582 servers, and then realize before we initiated a connection that
12583 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
12584 Reported by "mr-4".
12585 - If we set the ExitNodes option but it doesn't include any nodes
12586 that have the Exit flag, we would choose not to bootstrap. Now we
12587 bootstrap so long as ExitNodes includes nodes which can exit to
12588 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
12590 o Minor bugfixes (controller and command-line):
12591 - If changing a config option via "setconf" fails in a recoverable
12592 way, we used to nonetheless write our new control ports to the
12593 file described by the "ControlPortWriteToFile" option. Now we only
12594 write out that file if we successfully switch to the new config
12595 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
12596 - When a command-line option such as --version or --help that
12597 ordinarily implies --hush appears on the command line along with
12598 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
12599 only if it appeared later on the command line. Fixes bug 9578;
12600 bugfix on 0.2.5.1-alpha.
12602 o Minor bugfixes (code correctness):
12603 - Previously we used two temporary files when writing descriptors to
12604 disk; now we only use one. Fixes bug 1376.
12605 - Remove an erroneous (but impossible and thus harmless) pointer
12606 comparison that would have allowed compilers to skip a bounds
12607 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
12608 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
12609 - Fix an always-true assertion in pluggable transports code so it
12610 actually checks what it was trying to check. Fixes bug 10046;
12611 bugfix on 0.2.3.9-alpha. Found by "dcb".
12613 o Minor bugfixes (protocol correctness):
12614 - When receiving a VERSIONS cell with an odd number of bytes, close
12615 the connection immediately since the cell is malformed. Fixes bug
12616 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
12619 o Minor bugfixes (build):
12620 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
12621 turned off (that is, without support for v2 link handshakes). Fixes
12622 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
12623 - Fix compilation warnings and startup issues when running with
12624 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
12626 - Fix compilation on Solaris 9, which didn't like us having an
12627 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
12629 o Minor bugfixes (testing):
12630 - Fix a segmentation fault in our benchmark code when running with
12631 Fedora's OpenSSL package, or any other OpenSSL that provides
12632 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
12634 o Minor bugfixes (log messages):
12635 - Fix a bug where clients using bridges would report themselves
12636 as 50% bootstrapped even without a live consensus document.
12637 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
12638 - Suppress a warning where, if there's only one directory authority
12639 in the network, we would complain that votes and signatures cannot
12640 be uploaded to other directory authorities. Fixes bug 10842;
12641 bugfix on 0.2.2.26-beta.
12642 - Report bootstrapping progress correctly when we're downloading
12643 microdescriptors. We had updated our "do we have enough microdescs
12644 to begin building circuits?" logic most recently in 0.2.4.10-alpha
12645 (see bug 5956), but we left the bootstrap status event logic at
12646 "how far through getting 1/4 of them are we?" Fixes bug 9958;
12647 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
12649 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
12650 - Avoid a crash bug when starting with a corrupted microdescriptor
12651 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
12652 - If we fail to dump a previously cached microdescriptor to disk, avoid
12653 freeing duplicate data later on. Fixes bug 10423; bugfix on
12654 0.2.4.13-alpha. Spotted by "bobnomnom".
12656 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12657 - Correctly log long IPv6 exit policies, instead of truncating them
12658 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
12659 - Our default TLS ecdhe groups were backwards: we meant to be using
12660 P224 for relays (for performance win) and P256 for bridges (since
12661 it is more common in the wild). Instead we had it backwards. After
12662 reconsideration, we decided that the default should be P256 on all
12663 hosts, since its security is probably better, and since P224 is
12664 reportedly used quite little in the wild. Found by "skruffy" on
12665 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
12666 - Free directory authority certificate download statuses on exit
12667 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
12669 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12670 - If the guard we choose first doesn't answer, we would try the
12671 second guard, but once we connected to the second guard we would
12672 abandon it and retry the first one, slowing down bootstrapping.
12673 The fix is to treat all our initially chosen guards as acceptable
12674 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
12675 - Fix an assertion failure that would occur when disabling the
12676 ORPort setting on a running Tor process while accounting was
12677 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
12678 - When examining the list of network interfaces to find our address,
12679 do not consider non-running or disabled network interfaces. Fixes
12680 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
12681 - Avoid an off-by-one error when checking buffer boundaries when
12682 formatting the exit status of a pluggable transport helper.
12683 This is probably not an exploitable bug, but better safe than
12684 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
12687 o Removed code and features:
12688 - Clients now reject any directory authority certificates lacking
12689 a dir-key-crosscert element. These have been included since
12690 0.2.1.9-alpha, so there's no real reason for them to be optional
12691 any longer. Completes proposal 157. Resolves ticket 10162.
12692 - Remove all code that existed to support the v2 directory system,
12693 since there are no longer any v2 directory authorities. Resolves
12695 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
12696 options, which were used for designating authorities as "Hidden
12697 service authorities". There has been no use of hidden service
12698 authorities since 0.2.2.1-alpha, when we stopped uploading or
12699 downloading v0 hidden service descriptors. Fixes bug 10881; also
12700 part of a fix for bug 10841.
12702 o Code simplification and refactoring:
12703 - Remove some old fallback code designed to keep Tor clients working
12704 in a network with only two working relays. Elsewhere in the code we
12705 have long since stopped supporting such networks, so there wasn't
12706 much point in keeping it around. Addresses ticket 9926.
12707 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
12708 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
12709 - Remove data structures which were introduced to implement the
12710 CellStatistics option: they are now redundant with the addition
12711 of a timestamp to the regular packed_cell_t data structure, which
12712 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
12715 o Documentation (man page) fixes:
12716 - Update manpage to describe some of the files you can expect to
12717 find in Tor's DataDirectory. Addresses ticket 9839.
12718 - Document that all but one DirPort entry must have the NoAdvertise
12719 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
12721 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12722 - Clarify the usage and risks of setting the ContactInfo torrc line
12723 for your relay or bridge. Resolves ticket 9854.
12724 - Add anchors to the manpage so we can link to the html version of
12725 the documentation for specific options. Resolves ticket 9866.
12726 - Replace remaining references to DirServer in man page and
12727 log entries. Resolves ticket 10124.
12730 - Make the "tor-gencert" tool used by directory authority operators
12731 create 2048-bit signing keys by default (rather than 1024-bit, since
12732 1024-bit is uncomfortably small these days). Addresses ticket 10324.
12735 Changes in version 0.2.4.20 - 2013-12-22
12736 Tor 0.2.4.20 fixes potentially poor random number generation for users
12737 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
12738 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
12739 and 4) have no state file in their DataDirectory (as would happen on
12740 first start). Users who generated relay or hidden service identity
12741 keys in such a situation should discard them and generate new ones.
12743 This release also fixes a logic error that caused Tor clients to build
12744 many more preemptive circuits than they actually need.
12747 - Do not allow OpenSSL engines to replace the PRNG, even when
12748 HardwareAccel is set. The only default builtin PRNG engine uses
12749 the Intel RDRAND instruction to replace the entire PRNG, and
12750 ignores all attempts to seed it with more entropy. That's
12751 cryptographically stupid: the right response to a new alleged
12752 entropy source is never to discard all previously used entropy
12753 sources. Fixes bug 10402; works around behavior introduced in
12754 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
12756 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
12757 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
12758 - Avoid launching spurious extra circuits when a stream is pending.
12759 This fixes a bug where any circuit that _wasn't_ unusable for new
12760 streams would be treated as if it were, causing extra circuits to
12761 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
12764 - Avoid a crash bug when starting with a corrupted microdescriptor
12765 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
12766 - If we fail to dump a previously cached microdescriptor to disk, avoid
12767 freeing duplicate data later on. Fixes bug 10423; bugfix on
12768 0.2.4.13-alpha. Spotted by "bobnomnom".
12771 Changes in version 0.2.4.19 - 2013-12-11
12772 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
12773 (1986-2013). Aaron worked on diverse projects including helping to guide
12774 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
12775 transparency to the U.S government's PACER documents, and contributing
12776 design and development for Tor and Tor2Web. Aaron was one of the latest
12777 martyrs in our collective fight for civil liberties and human rights,
12778 and his death is all the more painful because he was one of us.
12780 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
12781 a new circuit handshake and link encryption that use ECC to provide
12782 better security and efficiency; makes relays better manage circuit
12783 creation requests; uses "directory guards" to reduce client enumeration
12784 risks; makes bridges collect and report statistics about the pluggable
12785 transports they support; cleans up and improves our geoip database;
12786 gets much closer to IPv6 support for clients, bridges, and relays; makes
12787 directory authorities use measured bandwidths rather than advertised
12788 ones when computing flags and thresholds; disables client-side DNS
12789 caching to reduce tracking risks; and fixes a big bug in bridge
12790 reachability testing. This release introduces two new design
12791 abstractions in the code: a new "channel" abstraction between circuits
12792 and or_connections to allow for implementing alternate relay-to-relay
12793 transports, and a new "circuitmux" abstraction storing the queue of
12794 circuits for a channel. The release also includes many stability,
12795 security, and privacy fixes.
12798 Changes in version 0.2.4.18-rc - 2013-11-16
12799 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
12800 series. It takes a variety of fixes from the 0.2.5.x branch to improve
12801 stability, performance, and better handling of edge cases.
12804 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
12805 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
12806 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
12807 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
12808 them to solve bug 6033.)
12811 - No longer stop reading or writing on cpuworker connections when
12812 our rate limiting buckets go empty. Now we should handle circuit
12813 handshake requests more promptly. Resolves bug 9731.
12814 - If we are unable to save a microdescriptor to the journal, do not
12815 drop it from memory and then reattempt downloading it. Fixes bug
12816 9645; bugfix on 0.2.2.6-alpha.
12817 - Stop trying to bootstrap all our directory information from
12818 only our first guard. Discovered while fixing bug 9946; bugfix
12820 - The new channel code sometimes lost track of in-progress circuits,
12821 causing long-running clients to stop building new circuits. The
12822 fix is to always call circuit_n_chan_done(chan, 0) from
12823 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
12825 o Minor bugfixes (on 0.2.4.x):
12826 - Correctly log long IPv6 exit policies, instead of truncating them
12827 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
12828 - Our default TLS ecdhe groups were backwards: we meant to be using
12829 P224 for relays (for performance win) and P256 for bridges (since
12830 it is more common in the wild). Instead we had it backwards. After
12831 reconsideration, we decided that the default should be P256 on all
12832 hosts, since its security is probably better, and since P224 is
12833 reportedly used quite little in the wild. Found by "skruffy" on
12834 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
12835 - Free directory authority certificate download statuses on exit
12836 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
12838 o Minor bugfixes (on 0.2.3.x and earlier):
12839 - If the guard we choose first doesn't answer, we would try the
12840 second guard, but once we connected to the second guard we would
12841 abandon it and retry the first one, slowing down bootstrapping.
12842 The fix is to treat all our initially chosen guards as acceptable
12843 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
12844 - Fix an assertion failure that would occur when disabling the
12845 ORPort setting on a running Tor process while accounting was
12846 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
12847 - When examining the list of network interfaces to find our address,
12848 do not consider non-running or disabled network interfaces. Fixes
12849 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
12850 - Avoid an off-by-one error when checking buffer boundaries when
12851 formatting the exit status of a pluggable transport helper.
12852 This is probably not an exploitable bug, but better safe than
12853 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
12856 o Minor features (protecting client timestamps):
12857 - Clients no longer send timestamps in their NETINFO cells. These were
12858 not used for anything, and they provided one small way for clients
12859 to be distinguished from each other as they moved from network to
12860 network or behind NAT. Implements part of proposal 222.
12861 - Clients now round timestamps in INTRODUCE cells down to the nearest
12862 10 minutes. If a new Support022HiddenServices option is set to 0, or
12863 if it's set to "auto" and the feature is disabled in the consensus,
12864 the timestamp is sent as 0 instead. Implements part of proposal 222.
12865 - Stop sending timestamps in AUTHENTICATE cells. This is not such
12866 a big deal from a security point of view, but it achieves no actual
12867 good purpose, and isn't needed. Implements part of proposal 222.
12868 - Reduce down accuracy of timestamps in hidden service descriptors.
12869 Implements part of proposal 222.
12871 o Minor features (other):
12872 - Improve the circuit queue out-of-memory handler. Previously, when
12873 we ran low on memory, we'd close whichever circuits had the most
12874 queued cells. Now, we close those that have the *oldest* queued
12875 cells, on the theory that those are most responsible for us
12876 running low on memory. Based on analysis from a forthcoming paper
12877 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
12878 - Generate bootstrapping status update events correctly when fetching
12879 microdescriptors. Fixes bug 9927.
12880 - Update to the October 2 2013 Maxmind GeoLite Country database.
12882 o Documentation fixes:
12883 - Clarify the usage and risks of setting the ContactInfo torrc line
12884 for your relay or bridge. Resolves ticket 9854.
12885 - Add anchors to the manpage so we can link to the html version of
12886 the documentation for specific options. Resolves ticket 9866.
12887 - Replace remaining references to DirServer in man page and
12888 log entries. Resolves ticket 10124.
12891 Changes in version 0.2.5.1-alpha - 2013-10-02
12892 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
12893 on Linux, allows bridges that offer pluggable transports to report usage
12894 statistics, fixes many issues to make testing easier, and provides
12895 a pile of minor features and bugfixes that have been waiting for a
12896 release of the new branch.
12898 This is the first alpha release in a new series, so expect there to
12899 be bugs. Users who would rather test out a more stable branch should
12900 stay with 0.2.4.x for now.
12902 o Major features (security):
12903 - Use the seccomp2 syscall filtering facility on Linux to limit
12904 which system calls Tor can invoke. This is an experimental,
12905 Linux-only feature to provide defense-in-depth against unknown
12906 attacks. To try turning it on, set "Sandbox 1" in your torrc
12907 file. Please be ready to report bugs. We hope to add support
12908 for better sandboxing in the future, including more fine-grained
12909 filters, better division of responsibility, and support for more
12910 platforms. This work has been done by Cristian-Matei Toader for
12911 Google Summer of Code.
12912 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
12913 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
12914 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
12915 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
12916 them to solve bug 6033.)
12918 o Major features (other):
12919 - Add support for passing arguments to managed pluggable transport
12920 proxies. Implements ticket 3594.
12921 - Bridges now track GeoIP information and the number of their users
12922 even when pluggable transports are in use, and report usage
12923 statistics in their extra-info descriptors. Resolves tickets 4773
12925 - Make testing Tor networks bootstrap better: lower directory fetch
12926 retry schedules and maximum interval without directory requests,
12927 and raise maximum download tries. Implements ticket 6752.
12928 - Add make target 'test-network' to run tests on a Chutney network.
12929 Implements ticket 8530.
12930 - The ntor handshake is now on-by-default, no matter what the
12931 directory authorities recommend. Implements ticket 8561.
12934 - Instead of writing destroy cells directly to outgoing connection
12935 buffers, queue them and intersperse them with other outgoing cells.
12936 This can prevent a set of resource starvation conditions where too
12937 many pending destroy cells prevent data cells from actually getting
12938 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
12939 bugfix on 0.2.0.1-alpha.
12940 - If we are unable to save a microdescriptor to the journal, do not
12941 drop it from memory and then reattempt downloading it. Fixes bug
12942 9645; bugfix on 0.2.2.6-alpha.
12943 - The new channel code sometimes lost track of in-progress circuits,
12944 causing long-running clients to stop building new circuits. The
12945 fix is to always call circuit_n_chan_done(chan, 0) from
12946 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
12949 - Tor now builds each source file in two modes: a mode that avoids
12950 exposing identifiers needlessly, and another mode that exposes
12951 more identifiers for testing. This lets the compiler do better at
12952 optimizing the production code, while enabling us to take more
12953 radical measures to let the unit tests test things.
12954 - The production builds no longer include functions used only in
12955 the unit tests; all functions exposed from a module only for
12956 unit-testing are now static in production builds.
12957 - Add an --enable-coverage configuration option to make the unit
12958 tests (and a new src/or/tor-cov target) to build with gcov test
12962 - We now have rudimentary function mocking support that our unit
12963 tests can use to test functions in isolation. Function mocking
12964 lets the tests temporarily replace a function's dependencies with
12965 stub functions, so that the tests can check the function without
12966 invoking the other functions it calls.
12967 - Add more unit tests for the <circid,channel>->circuit map, and
12968 the destroy-cell-tracking code to fix bug 7912.
12969 - Unit tests for failing cases of the TAP onion handshake.
12970 - More unit tests for address-manipulation functions.
12972 o Minor features (protecting client timestamps):
12973 - Clients no longer send timestamps in their NETINFO cells. These were
12974 not used for anything, and they provided one small way for clients
12975 to be distinguished from each other as they moved from network to
12976 network or behind NAT. Implements part of proposal 222.
12977 - Clients now round timestamps in INTRODUCE cells down to the nearest
12978 10 minutes. If a new Support022HiddenServices option is set to 0, or
12979 if it's set to "auto" and the feature is disabled in the consensus,
12980 the timestamp is sent as 0 instead. Implements part of proposal 222.
12981 - Stop sending timestamps in AUTHENTICATE cells. This is not such
12982 a big deal from a security point of view, but it achieves no actual
12983 good purpose, and isn't needed. Implements part of proposal 222.
12984 - Reduce down accuracy of timestamps in hidden service descriptors.
12985 Implements part of proposal 222.
12987 o Minor features (config options):
12988 - Config (torrc) lines now handle fingerprints which are missing
12989 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
12990 - Support a --dump-config option to print some or all of the
12991 configured options. Mainly useful for debugging the command-line
12992 option parsing code. Helps resolve ticket 4647.
12993 - Raise awareness of safer logging: notify user of potentially
12994 unsafe config options, like logging more verbosely than severity
12995 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
12996 - Add a new configuration option TestingV3AuthVotingStartOffset
12997 that bootstraps a network faster by changing the timing for
12998 consensus votes. Addresses ticket 8532.
12999 - Add a new torrc option "ServerTransportOptions" that allows
13000 bridge operators to pass configuration parameters to their
13001 pluggable transports. Resolves ticket 8929.
13002 - The config (torrc) file now accepts bandwidth and space limits in
13003 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
13004 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
13007 o Minor features (build):
13008 - Add support for `--library-versions` flag. Implements ticket 6384.
13009 - Return the "unexpected sendme" warnings to a warn severity, but make
13010 them rate limited, to help diagnose ticket 8093.
13011 - Detect a missing asciidoc, and warn the user about it, during
13012 configure rather than at build time. Fixes issue 6506. Patch from
13015 o Minor features (other):
13016 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
13017 sockets in a single system call. Implements ticket 5129.
13018 - Log current accounting state (bytes sent and received + remaining
13019 time for the current accounting period) in the relay's heartbeat
13020 message. Implements ticket 5526; patch from Peter Retzlaff.
13021 - Implement the TRANSPORT_LAUNCHED control port event that
13022 notifies controllers about new launched pluggable
13023 transports. Resolves ticket 5609.
13024 - If we're using the pure-C 32-bit curve25519_donna implementation
13025 of curve25519, build it with the -fomit-frame-pointer option to
13026 make it go faster on register-starved hosts. This improves our
13027 handshake performance by about 6% on i386 hosts without nacl.
13028 Closes ticket 8109.
13029 - Update to the September 4 2013 Maxmind GeoLite Country database.
13032 - Set the listen() backlog limit to the largest actually supported
13033 on the system, not to the value in a header file. Fixes bug 9716;
13034 bugfix on every released Tor.
13035 - No longer accept malformed http headers when parsing urls from
13036 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
13037 bugfix on 0.0.6pre1.
13038 - In munge_extrainfo_into_routerinfo(), check the return value of
13039 memchr(). This would have been a serious issue if we ever passed
13040 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
13042 - On the chance that somebody manages to build Tor on a
13043 platform where time_t is unsigned, correct the way that
13044 microdesc_add_to_cache() handles negative time arguments.
13045 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
13046 - Reject relative control socket paths and emit a warning. Previously,
13047 single-component control socket paths would be rejected, but Tor
13048 would not log why it could not validate the config. Fixes bug 9258;
13049 bugfix on 0.2.3.16-alpha.
13051 o Minor bugfixes (command line):
13052 - Use a single command-line parser for parsing torrc options on the
13053 command line and for finding special command-line options to avoid
13054 inconsistent behavior for torrc option arguments that have the same
13055 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
13057 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
13058 9573; bugfix on 0.0.9pre5.
13060 o Minor fixes (build, auxiliary programs):
13061 - Stop preprocessing the "torify" script with autoconf, since
13062 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
13064 - The tor-fw-helper program now follows the standard convention and
13065 exits with status code "0" on success. Fixes bug 9030; bugfix on
13066 0.2.3.1-alpha. Patch by Arlo Breault.
13067 - Corrected ./configure advice for what openssl dev package you should
13068 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
13070 o Minor code improvements:
13071 - Remove constants and tests for PKCS1 padding; it's insecure and
13072 shouldn't be used for anything new. Fixes bug 8792; patch
13074 - Remove instances of strcpy() from the unit tests. They weren't
13075 hurting anything, since they were only in the unit tests, but it's
13076 embarrassing to have strcpy() in the code at all, and some analysis
13077 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
13078 0.2.3.8-alpha. Patch from Arlo Breault.
13080 o Removed features:
13081 - Remove migration code from when we renamed the "cached-routers"
13082 file to "cached-descriptors" back in 0.2.0.8-alpha. This
13083 incidentally resolves ticket 6502 by cleaning up the related code
13084 a bit. Patch from Akshay Hebbar.
13086 o Code simplification and refactoring:
13087 - Extract the common duplicated code for creating a subdirectory
13088 of the data directory and writing to a file in it. Fixes ticket
13089 4282; patch from Peter Retzlaff.
13090 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
13091 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
13092 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
13093 - Add a set of accessor functions for the circuit timeout data
13094 structure. Fixes ticket 6153; patch from "piet".
13095 - Clean up exit paths from connection_listener_new(). Closes ticket
13096 8789. Patch from Arlo Breault.
13097 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
13098 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
13099 - Use a doubly-linked list to implement the global circuit list.
13100 Resolves ticket 9108. Patch from Marek Majkowski.
13101 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
13104 Changes in version 0.2.4.17-rc - 2013-09-05
13105 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
13106 series. It adds an emergency step to help us tolerate the massive
13107 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
13108 circuit-level handshakes now effectively jump the queue compared to
13109 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
13110 big bug hindering bridge reachability tests.
13113 - Relays now process the new "NTor" circuit-level handshake requests
13114 with higher priority than the old "TAP" circuit-level handshake
13115 requests. We still process some TAP requests to not totally starve
13116 0.2.3 clients when NTor becomes popular. A new consensus parameter
13117 "NumNTorsPerTAP" lets us tune the balance later if we need to.
13118 Implements ticket 9574.
13121 - If the circuit build timeout logic is disabled (via the consensus,
13122 or because we are an authority), then don't build testing circuits.
13123 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
13124 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
13125 previously they did not, which prevented them from receiving
13126 successful connections from relays for self-test or bandwidth
13127 testing. Also, when a relay is extending a circuit to a bridge,
13128 it needs to send a NETINFO cell, even when the bridge hasn't sent
13129 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
13130 - If the time to download the next old-style networkstatus is in
13131 the future, do not decline to consider whether to download the
13132 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
13136 - Avoid double-closing the listener socket in our socketpair()
13137 replacement (used on Windows) in the case where the addresses on
13138 our opened sockets don't match what we expected. Fixes bug 9400;
13139 bugfix on 0.0.2pre7. Found by Coverity.
13141 o Minor fixes (config options):
13142 - Avoid overflows when the user sets MaxCircuitDirtiness to a
13143 ridiculously high value, by imposing a (ridiculously high) 30-day
13144 maximum on MaxCircuitDirtiness.
13145 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
13146 message is logged at notice, not at info.
13147 - Warn and fail if a server is configured not to advertise any
13148 ORPorts at all. (We need *something* to put in our descriptor,
13149 or we just won't work.)
13152 - Track how many "TAP" and "NTor" circuit handshake requests we get,
13153 and how many we complete, and log it every hour to help relay
13154 operators follow trends in network load. Addresses ticket 9658.
13155 - Update to the August 7 2013 Maxmind GeoLite Country database.
13158 Changes in version 0.2.4.16-rc - 2013-08-10
13159 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
13160 series. It fixes several crash bugs in the 0.2.4 branch.
13163 - Fix a bug in the voting algorithm that could yield incorrect results
13164 when a non-naming authority declared too many flags. Fixes bug 9200;
13165 bugfix on 0.2.0.3-alpha.
13166 - Fix an uninitialized read that could in some cases lead to a remote
13167 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
13168 Anybody running a hidden service on the experimental 0.2.4.x
13169 branch should upgrade. (This is, so far as we know, unrelated to
13171 - Avoid an assertion failure when processing DNS replies without the
13172 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
13173 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
13174 0.2.4.15-rc. Found by stem integration tests.
13177 - Fix an invalid memory read that occurred when a pluggable
13178 transport proxy failed its configuration protocol.
13179 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
13180 - When evaluating whether to use a connection that we haven't
13181 decided is canonical using a recent link protocol version,
13182 decide that it's canonical only if it used address _does_
13183 match the desired address. Fixes bug 9309; bugfix on
13184 0.2.4.4-alpha. Reported by skruffy.
13185 - Make the default behavior of NumDirectoryGuards be to track
13186 NumEntryGuards. Now a user who changes only NumEntryGuards will get
13187 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
13188 - Fix a spurious compilation warning with some older versions of
13189 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
13192 - Update to the July 3 2013 Maxmind GeoLite Country database.
13195 Changes in version 0.2.4.15-rc - 2013-07-01
13196 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
13197 series. It fixes a few smaller bugs, but generally appears stable.
13198 Please test it and let us know whether it is!
13201 - When receiving a new configuration file via the control port's
13202 LOADCONF command, do not treat the defaults file as absent.
13203 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
13206 - Issue a warning when running with the bufferevents backend enabled.
13207 It's still not stable, and people should know that they're likely
13208 to hit unexpected problems. Closes ticket 9147.
13211 Changes in version 0.2.4.14-alpha - 2013-06-18
13212 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
13213 present in 0.2.4.13-alpha.
13216 - When we have too much memory queued in circuits (according to a new
13217 MaxMemInCellQueues option), close the circuits consuming the most
13218 memory. This prevents us from running out of memory as a relay if
13219 circuits fill up faster than they can be drained. Fixes bug 9063;
13220 bugfix on the 54th commit of Tor. This bug is a further fix beyond
13221 bug 6252, whose fix was merged into 0.2.3.21-rc.
13223 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
13224 where we tried to solve this issue simply by imposing an upper limit
13225 on the number of queued cells for a single circuit. That approach
13226 proved to be problematic, since there are ways to provoke clients to
13227 send a number of cells in excess of any such reasonable limit. Fixes
13228 bug 9072; bugfix on 0.2.4.13-alpha.
13230 - Limit hidden service descriptors to at most ten introduction
13231 points, to slow one kind of guard enumeration. Fixes bug 9002;
13232 bugfix on 0.1.1.11-alpha.
13235 Changes in version 0.2.4.13-alpha - 2013-06-14
13236 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
13237 vulnerabilities, makes socks5 username/password circuit isolation
13238 actually actually work (this time for sure!), and cleans up a bunch
13239 of other issues in preparation for a release candidate.
13241 o Major bugfixes (robustness):
13242 - Close any circuit that has too many cells queued on it. Fixes
13243 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
13244 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
13245 - Prevent the get_freelists() function from running off the end of
13246 the list of freelists if it somehow gets an unrecognized
13247 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
13249 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
13250 when an exit connection with optimistic data succeeds immediately
13251 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
13253 - Fix a directory authority crash bug when building a consensus
13254 using an older consensus as its basis. Fixes bug 8833. Bugfix
13258 - Avoid a memory leak where we would leak a consensus body when we
13259 find that a consensus which we couldn't previously verify due to
13260 missing certificates is now verifiable. Fixes bug 8719; bugfix
13262 - We used to always request authority certificates by identity digest,
13263 meaning we'd get the newest one even when we wanted one with a
13264 different signing key. Then we would complain about being given
13265 a certificate we already had, and never get the one we really
13266 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
13267 resource to request the one we want. Fixes bug 5595; bugfix on
13269 - Follow the socks5 protocol when offering username/password
13270 authentication. The fix for bug 8117 exposed this bug, and it
13271 turns out real-world applications like Pidgin do care. Bugfix on
13272 0.2.3.2-alpha; fixes bug 8879.
13273 - Prevent failures on Windows Vista and later when rebuilding the
13274 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
13275 bugfix on 0.2.4.12-alpha.
13278 - Fix an impossible buffer overrun in the AES unit tests. Fixes
13279 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
13280 - If for some reason we fail to write a microdescriptor while
13281 rebuilding the cache, do not let the annotations from that
13282 microdescriptor linger in the cache file, and do not let the
13283 microdescriptor stay recorded as present in its old location.
13284 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
13285 - Fix a memory leak that would occur whenever a configuration
13286 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
13287 - Paste the description for PathBias parameters from the man
13288 page into or.h, so the code documents them too. Fixes bug 7982;
13289 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
13290 - Relays now treat a changed IPv6 ORPort as sufficient reason to
13291 publish an updated descriptor. Fixes bug 6026; bugfix on
13293 - When launching a resolve request on behalf of an AF_UNIX control
13294 socket, omit the address field of the new entry connection, used in
13295 subsequent controller events, rather than letting tor_dup_addr()
13296 set it to "<unknown address type>". Fixes bug 8639; bugfix on
13299 o Minor bugfixes (log messages):
13300 - Fix a scaling issue in the path bias accounting code that
13301 resulted in "Bug:" log messages from either
13302 pathbias_scale_close_rates() or pathbias_count_build_success().
13303 This represents a bugfix on a previous bugfix: the original fix
13304 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
13306 - Give a less useless error message when the user asks for an IPv4
13307 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
13311 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
13312 to tolerate bug 8093 for now.
13313 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
13314 in directory authority votes to describe whether they have enough
13315 measured bandwidths to ignore advertised (relay descriptor)
13316 bandwidth claims. Resolves ticket 8711.
13317 - Update to the June 5 2013 Maxmind GeoLite Country database.
13319 o Removed documentation:
13320 - Remove some of the older contents of doc/ as obsolete; move others
13321 to torspec.git. Fixes bug 8965.
13323 o Code simplification and refactoring:
13324 - Avoid using character buffers when constructing most directory
13325 objects: this approach was unwieldy and error-prone. Instead,
13326 build smartlists of strings, and concatenate them when done.
13329 Changes in version 0.2.4.12-alpha - 2013-04-18
13330 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
13331 process for lengthening the guard rotation period, makes directory
13332 authority opinions in the consensus a bit less gameable, makes socks5
13333 username/password circuit isolation actually work, and fixes a wide
13334 variety of other issues.
13337 - Raise the default time that a client keeps an entry guard from
13338 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
13339 2012 paper. (We would make it even longer, but we need better client
13340 load balancing first.) Also, make the guard lifetime controllable
13341 via a new GuardLifetime torrc option and a GuardLifetime consensus
13342 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
13343 - Directory authorities now prefer using measured bandwidths to
13344 advertised ones when computing flags and thresholds. Resolves
13346 - Directory authorities that have more than a threshold number
13347 of relays with measured bandwidths now treat relays with unmeasured
13348 bandwidths as having bandwidth 0. Resolves ticket 8435.
13350 o Major bugfixes (assert / resource use):
13351 - Avoid a bug where our response to TLS renegotiation under certain
13352 network conditions could lead to a busy-loop, with 100% CPU
13353 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
13354 - Avoid an assertion when we discover that we'd like to write a cell
13355 onto a closing connection: just discard the cell. Fixes another
13356 case of bug 7350; bugfix on 0.2.4.4-alpha.
13358 o Major bugfixes (client-side privacy):
13359 - When we mark a circuit as unusable for new circuits, have it
13360 continue to be unusable for new circuits even if MaxCircuitDirtiness
13361 is increased too much at the wrong time, or the system clock jumps
13362 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
13363 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
13364 which have resolved to internal addresses") is set, apply that
13365 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
13366 - When an exit relay rejects a stream with reason "exit policy", but
13367 we only know an exit policy summary (e.g. from the microdesc
13368 consensus) for it, do not mark the relay as useless for all exiting.
13369 Instead, mark just the circuit as unsuitable for that particular
13370 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
13371 - Allow applications to get proper stream isolation with
13372 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
13373 username/password authentication also offer "no authentication". Tor
13374 had previously preferred "no authentication", so the applications
13375 never actually sent Tor their auth details. Now Tor selects
13376 username/password authentication if it's offered. You can disable
13377 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
13378 bug 8117; bugfix on 0.2.3.3-alpha.
13380 o Major bugfixes (other):
13381 - When unable to find any working directory nodes to use as a
13382 directory guard, give up rather than adding the same non-working
13383 nodes to the directory guard list over and over. Fixes bug 8231;
13384 bugfix on 0.2.4.8-alpha.
13387 - Reject as invalid most directory objects containing a NUL.
13388 Belt-and-suspender fix for bug 8037.
13389 - In our testsuite, create temporary directories with a bit more
13390 entropy in their name to make name collisions less likely. Fixes
13392 - Add CACHED keyword to ADDRMAP events in the control protocol
13393 to indicate whether a DNS result will be cached or not. Resolves
13395 - Update to the April 3 2013 Maxmind GeoLite Country database.
13397 o Minor features (build):
13398 - Detect and reject attempts to build Tor with threading support
13399 when OpenSSL has been compiled without threading support.
13401 - Clarify that when autoconf is checking for nacl, it is checking
13402 specifically for nacl with a fast curve25519 implementation.
13404 - Warn if building on a platform with an unsigned time_t: there
13405 are too many places where Tor currently assumes that time_t can
13406 hold negative values. We'd like to fix them all, but probably
13409 o Minor bugfixes (build):
13410 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
13411 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
13412 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
13413 - Add the old src/or/micro-revision.i filename to CLEANFILES.
13414 On the off chance that somebody has one, it will go away as soon
13415 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
13416 - Build Tor correctly on 32-bit platforms where the compiler can build
13417 but not run code using the "uint128_t" construction. Fixes bug 8587;
13418 bugfix on 0.2.4.8-alpha.
13419 - Fix compilation warning with some versions of clang that would
13420 prefer the -Wswitch-enum compiler flag to warn about switch
13421 statements with missing enum values, even if those switch
13422 statements have a "default:" statement. Fixes bug 8598; bugfix
13425 o Minor bugfixes (protocol):
13426 - Fix the handling of a TRUNCATE cell when it arrives while the
13427 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
13428 - Fix a misframing issue when reading the version numbers in a
13429 VERSIONS cell. Previously we would recognize [00 01 00 02] as
13430 'version 1, version 2, and version 0x100', when it should have
13431 only included versions 1 and 2. Fixes bug 8059; bugfix on
13432 0.2.0.10-alpha. Reported pseudonymously.
13433 - Make the format and order of STREAM events for DNS lookups
13434 consistent among the various ways to launch DNS lookups. Fixes
13435 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
13436 - Correct our check for which versions of Tor support the EXTEND2
13437 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
13438 later, when support was really added in version 0.2.4.8-alpha.
13439 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
13441 o Minor bugfixes (other):
13442 - Correctly store microdescriptors and extrainfo descriptors with
13443 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
13444 Bug reported by "cypherpunks".
13445 - Increase the width of the field used to remember a connection's
13446 link protocol version to two bytes. Harmless for now, since the
13447 only currently recognized versions are one byte long. Reported
13448 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
13449 - If the state file's path bias counts are invalid (presumably from a
13450 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
13451 additional checks and log messages to the scaling of Path Bias
13452 counts, in case there still are remaining issues with scaling.
13453 Should help resolve bug 8235.
13454 - Eliminate several instances where we use "Nickname=ID" to refer to
13455 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
13456 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
13457 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
13459 o Minor bugfixes (syscalls):
13460 - Always check the return values of functions fcntl() and
13461 setsockopt(). We don't believe these are ever actually failing in
13462 practice, but better safe than sorry. Also, checking these return
13463 values should please analysis tools like Coverity. Patch from
13464 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
13465 - Use direct writes rather than stdio when building microdescriptor
13466 caches, in an attempt to mitigate bug 8031, or at least make it
13469 o Minor bugfixes (config):
13470 - When rejecting a configuration because we were unable to parse a
13471 quoted string, log an actual error message. Fixes bug 7950; bugfix
13473 - Behave correctly when the user disables LearnCircuitBuildTimeout
13474 but doesn't tell us what they would like the timeout to be. Fixes
13475 bug 6304; bugfix on 0.2.2.14-alpha.
13476 - When autodetecting the number of CPUs, use the number of available
13477 CPUs in preference to the number of configured CPUs. Inform the
13478 user if this reduces the number of available CPUs. Fixes bug 8002;
13479 bugfix on 0.2.3.1-alpha.
13480 - Make it an error when you set EntryNodes but disable UseGuardNodes,
13481 since it will (surprisingly to some users) ignore EntryNodes. Fixes
13482 bug 8180; bugfix on 0.2.3.11-alpha.
13483 - Allow TestingTorNetworks to override the 4096-byte minimum for
13484 the Fast threshold. Otherwise they can't bootstrap until they've
13485 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
13486 - Fix some logic errors when the user manually overrides the
13487 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
13490 o Minor bugfixes (log messages to help diagnose bugs):
13491 - If we fail to free a microdescriptor because of bug 7164, log
13492 the filename and line number from which we tried to free it.
13493 - Add another diagnostic to the heartbeat message: track and log
13494 overhead that TLS is adding to the data we write. If this is
13495 high, we are sending too little data to SSL_write at a time.
13496 Diagnostic for bug 7707.
13497 - Add more detail to a log message about relaxed timeouts, to help
13499 - Warn more aggressively when flushing microdescriptors to a
13500 microdescriptor cache fails, in an attempt to mitigate bug 8031,
13501 or at least make it more diagnosable.
13502 - Improve debugging output to help track down bug 8185 ("Bug:
13503 outgoing relay cell has n_chan==NULL. Dropping.")
13504 - Log the purpose of a path-bias testing circuit correctly.
13505 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
13507 o Minor bugfixes (0.2.4.x log messages that were too noisy):
13508 - Don't attempt to relax the timeout of already opened 1-hop circuits.
13509 They might never timeout. This should eliminate some/all cases of
13510 the relaxed timeout log message.
13511 - Use circuit creation time for network liveness evaluation. This
13512 should eliminate warning log messages about liveness caused
13513 by changes in timeout evaluation. Fixes bug 6572; bugfix on
13515 - Reduce a path bias length check from notice to info. The message
13516 is triggered when creating controller circuits. Fixes bug 8196;
13517 bugfix on 0.2.4.8-alpha.
13518 - Fix a path state issue that triggered a notice during relay startup.
13519 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
13520 - Reduce occurrences of warns about circuit purpose in
13521 connection_ap_expire_building(). Fixes bug 8477; bugfix on
13524 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
13525 - If we encounter a write failure on a SOCKS connection before we
13526 finish our SOCKS handshake, don't warn that we closed the
13527 connection before we could send a SOCKS reply. Fixes bug 8427;
13528 bugfix on 0.1.0.1-rc.
13529 - Correctly recognize that [::1] is a loopback address. Fixes
13530 bug 8377; bugfix on 0.2.1.3-alpha.
13531 - Fix a directory authority warn caused when we have a large amount
13532 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
13533 - Don't log inappropriate heartbeat messages when hibernating: a
13534 hibernating node is _expected_ to drop out of the consensus,
13535 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
13536 bugfix on 0.2.3.1-alpha.
13537 - Don't complain about bootstrapping problems while hibernating.
13538 These complaints reflect a general code problem, but not one
13539 with any problematic effects (no connections are actually
13540 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
13542 o Documentation fixes:
13543 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
13544 names match. Fixes bug 7768.
13545 - Make the torify manpage no longer refer to tsocks; torify hasn't
13546 supported tsocks since 0.2.3.14-alpha.
13547 - Make the tor manpage no longer reference tsocks.
13548 - Fix the GeoIPExcludeUnknown documentation to refer to
13549 ExcludeExitNodes rather than the currently nonexistent
13550 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
13553 - The tor-tsocks.conf is no longer distributed or installed. We
13554 recommend that tsocks users use torsocks instead. Resolves
13558 Changes in version 0.2.4.11-alpha - 2013-03-11
13559 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
13560 more robust, makes hidden service authentication work again, and
13561 resolves a DPI fingerprint for Tor's SSL transport.
13563 o Major features (directory authorities):
13564 - Directory authorities now support a new consensus method (17)
13565 where they cap the published bandwidth of servers for which
13566 insufficient bandwidth measurements exist. Fixes part of bug 2286.
13567 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
13568 serve any v2 directory information. Now we can test disabling the
13569 old deprecated v2 directory format, and see whether doing so has
13570 any effect on network load. Begins to fix bug 6783.
13571 - Directory authorities now include inside each vote a statement of
13572 the performance thresholds they used when assigning flags.
13573 Implements ticket 8151.
13575 o Major bugfixes (directory authorities):
13576 - Stop marking every relay as having been down for one hour every
13577 time we restart a directory authority. These artificial downtimes
13578 were messing with our Stable and Guard flag calculations. Fixes
13579 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
13581 o Major bugfixes (hidden services):
13582 - Allow hidden service authentication to succeed again. When we
13583 refactored the hidden service introduction code back
13584 in 0.2.4.1-alpha, we didn't update the code that checks
13585 whether authentication information is present, causing all
13586 authentication checks to return "false". Fix for bug 8207; bugfix
13587 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
13589 o Minor features (relays, bridges):
13590 - Make bridge relays check once a minute for whether their IP
13591 address has changed, rather than only every 15 minutes. Resolves
13592 bugs 1913 and 1992.
13593 - Refactor resolve_my_address() so it returns the method by which we
13594 decided our public IP address (explicitly configured, resolved from
13595 explicit hostname, guessed from interfaces, learned by gethostname).
13596 Now we can provide more helpful log messages when a relay guesses
13597 its IP address incorrectly (e.g. due to unexpected lines in
13598 /etc/hosts). Resolves ticket 2267.
13599 - Teach bridge-using clients to avoid 0.2.2 bridges when making
13600 microdescriptor-related dir requests, and only fall back to normal
13601 descriptors if none of their bridges can handle microdescriptors
13602 (as opposed to the fix in ticket 4013, which caused them to fall
13603 back to normal descriptors if *any* of their bridges preferred
13604 them). Resolves ticket 4994.
13605 - Randomize the lifetime of our SSL link certificate, so censors can't
13606 use the static value for filtering Tor flows. Resolves ticket 8443;
13607 related to ticket 4014 which was included in 0.2.2.33.
13608 - Support a new version of the link protocol that allows 4-byte circuit
13609 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
13610 a possible resource exhaustion issue. Closes ticket 7351; implements
13613 o Minor features (portability):
13614 - Tweak the curve25519-donna*.c implementations to tolerate systems
13615 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
13616 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
13617 the signs of types during autoconf. This is better than our old
13618 approach, which didn't work when cross-compiling.
13619 - Detect the sign of enum values, rather than assuming that MSC is the
13620 only compiler where enum types are all signed. Fixes bug 7727;
13621 bugfix on 0.2.4.10-alpha.
13623 o Minor features (other):
13624 - Say "KBytes" rather than "KB" in the man page (for various values
13625 of K), to further reduce confusion about whether Tor counts in
13626 units of memory or fractions of units of memory. Resolves ticket 7054.
13627 - Clear the high bit on curve25519 public keys before passing them to
13628 our backend, in case we ever wind up using a backend that doesn't do
13629 so itself. If we used such a backend, and *didn't* clear the high bit,
13630 we could wind up in a situation where users with such backends would
13631 be distinguishable from users without. Fixes bug 8121; bugfix on
13633 - Update to the March 6 2013 Maxmind GeoLite Country database.
13635 o Minor bugfixes (clients):
13636 - When we receive a RELAY_END cell with the reason DONE, or with no
13637 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
13638 status as "connection refused". Previously we reported these cases
13639 as success but then immediately closed the connection. Fixes bug
13640 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
13641 - Downgrade an assertion in connection_ap_expire_beginning to an
13642 LD_BUG message. The fix for bug 8024 should prevent this message
13643 from displaying, but just in case, a warn that we can diagnose
13644 is better than more assert crashes. Fixes bug 8065; bugfix on
13646 - Lower path use bias thresholds to .80 for notice and .60 for warn.
13647 Also make the rate limiting flags for the path use bias log messages
13648 independent from the original path bias flags. Fixes bug 8161;
13649 bugfix on 0.2.4.10-alpha.
13651 o Minor bugfixes (relays):
13652 - Stop trying to resolve our hostname so often (e.g. every time we
13653 think about doing a directory fetch). Now we reuse the cached
13654 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
13655 and 2410 (bugfix on 0.1.2.2-alpha).
13656 - Stop sending a stray "(null)" in some cases for the server status
13657 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
13659 - When choosing which stream on a formerly stalled circuit to wake
13660 first, make better use of the platform's weak RNG. Previously,
13661 we had been using the % ("modulo") operator to try to generate a
13662 1/N chance of picking each stream, but this behaves badly with
13663 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
13665 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
13666 Irix's random() only return 15 bits; Solaris's random() returns more
13667 bits but its RAND_MAX says it only returns 15, and so on. Motivated
13668 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
13670 o Minor bugfixes (directory authorities):
13671 - Directory authorities now use less space when formatting identical
13672 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
13675 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
13676 - Avoid leaking memory if we fail to compute a consensus signature
13677 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
13678 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
13680 - Fix a memory leak during safe-cookie controller authentication.
13681 Bugfix on 0.2.3.13-alpha.
13682 - Avoid memory leak of IPv6 policy content if we fail to format it into
13683 a router descriptor. Bugfix on 0.2.4.7-alpha.
13685 o Minor bugfixes (other code correctness issues):
13686 - Avoid a crash if we fail to generate an extrainfo descriptor.
13687 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
13688 this is CID 718634.
13689 - When detecting the largest possible file descriptor (in order to
13690 close all file descriptors when launching a new program), actually
13691 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
13692 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
13694 - Fix a copy-and-paste error when adding a missing A1 to a routerset
13695 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
13696 Bugfix on 0.2.4.10-alpha.
13697 - Fix an impossible-to-trigger integer overflow when estimating how
13698 long our onionskin queue would take. (This overflow would require us
13699 to accept 4 million onionskins before processing 100 of them.) Fixes
13700 bug 8210; bugfix on 0.2.4.10-alpha.
13702 o Code simplification and refactoring:
13703 - Add a wrapper function for the common "log a message with a
13707 Changes in version 0.2.4.10-alpha - 2013-02-04
13708 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
13709 certain attacks that flood the network with relays; changes the queue
13710 for circuit create requests from a sized-based limit to a time-based
13711 limit; resumes building with MSVC on Windows; and fixes a wide variety
13714 o Major bugfixes (directory authority):
13715 - When computing directory thresholds, ignore any rejected-as-sybil
13716 nodes during the computation so that they can't influence Fast,
13717 Guard, etc. (We should have done this for proposal 109.) Fixes
13719 - When marking a node as a likely sybil, reset its uptime metrics
13720 to zero, so that it cannot time towards getting marked as Guard,
13721 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
13725 - When a TLS write is partially successful but incomplete, remember
13726 that the flushed part has been flushed, and notice that bytes were
13727 actually written. Reported and fixed pseudonymously. Fixes bug
13728 7708; bugfix on Tor 0.1.0.5-rc.
13729 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
13730 ID: these could be used to create unexpected streams and circuits
13731 which would count as "present" to some parts of Tor but "absent"
13732 to others, leading to zombie circuits and streams or to a bandwidth
13733 denial-of-service. Fixes bug 7889; bugfix on every released version
13734 of Tor. Reported by "oftc_must_be_destroyed".
13735 - Rename all macros in our local copy of queue.h to begin with "TOR_".
13736 This change seems the only good way to permanently prevent conflicts
13737 with queue.h on various operating systems. Fixes bug 8107; bugfix
13740 o Major features (relay):
13741 - Instead of limiting the number of queued onionskins (aka circuit
13742 create requests) to a fixed, hard-to-configure number, we limit
13743 the size of the queue based on how many we expect to be able to
13744 process in a given amount of time. We estimate the time it will
13745 take to process an onionskin based on average processing time
13746 of previous onionskins. Closes ticket 7291. You'll never have to
13747 configure MaxOnionsPending again.
13749 o Major features (portability):
13750 - Resume building correctly with MSVC and Makefile.nmake. This patch
13751 resolves numerous bugs and fixes reported by ultramage, including
13752 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
13753 - Make the ntor and curve25519 code build correctly with MSVC.
13754 Fix on 0.2.4.8-alpha.
13757 - When directory authorities are computing thresholds for flags,
13758 never let the threshold for the Fast flag fall below 4096
13759 bytes. Also, do not consider nodes with extremely low bandwidths
13760 when deciding thresholds for various directory flags. This change
13761 should raise our threshold for Fast relays, possibly in turn
13762 improving overall network performance; see ticket 1854. Resolves
13764 - The Tor client now ignores sub-domain components of a .onion
13765 address. This change makes HTTP "virtual" hosting
13766 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
13767 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
13768 hosted on the same hidden service. Implements proposal 204.
13769 - We compute the overhead from passing onionskins back and forth to
13770 cpuworkers, and report it when dumping statistics in response to
13771 SIGUSR1. Supports ticket 7291.
13773 o Minor features (path selection):
13774 - When deciding whether we have enough descriptors to build circuits,
13775 instead of looking at raw relay counts, look at which fraction
13776 of (bandwidth-weighted) paths we're able to build. This approach
13777 keeps clients from building circuits if their paths are likely to
13778 stand out statistically. The default fraction of paths needed is
13779 taken from the consensus directory; you can override it with the
13780 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
13781 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
13782 and we have GeoIP information, also exclude all nodes with unknown
13783 countries "??" and "A1". This behavior is controlled by the
13784 new GeoIPExcludeUnknown option: you can make such nodes always
13785 excluded with "GeoIPExcludeUnknown 1", and disable the feature
13786 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
13787 gets you the default behavior. Implements feature 7706.
13788 - Path Use Bias: Perform separate accounting for successful circuit
13789 use. Keep separate statistics on stream attempt rates versus stream
13790 success rates for each guard. Provide configurable thresholds to
13791 determine when to emit log messages or disable use of guards that
13792 fail too many stream attempts. Resolves ticket 7802.
13794 o Minor features (log messages):
13795 - When learning a fingerprint for a bridge, log its corresponding
13796 transport type. Implements ticket 7896.
13797 - Improve the log message when "Bug/attack: unexpected sendme cell
13798 from client" occurs, to help us track bug 8093.
13801 - Remove a couple of extraneous semicolons that were upsetting the
13802 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
13803 bugfix on 0.2.2.1-alpha.
13804 - Remove a source of rounding error during path bias count scaling;
13805 don't count cannibalized circuits as used for path bias until we
13806 actually try to use them; and fix a circuit_package_relay_cell()
13807 warning message about n_chan==NULL. Fixes bug 7802.
13808 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
13809 actually link against nacl when we're configured to use it. Fixes
13810 bug 7972; bugfix on 0.2.4.8-alpha.
13811 - Compile correctly with the --disable-curve25519 option. Fixes
13812 bug 8153; bugfix on 0.2.4.8-alpha.
13814 o Build improvements:
13815 - Do not report status verbosely from autogen.sh unless the -v flag
13816 is specified. Fixes issue 4664. Patch from Onizuka.
13817 - Replace all calls to snprintf() outside of src/ext with
13818 tor_snprintf(). Also remove the #define to replace snprintf with
13819 _snprintf on Windows; they have different semantics, and all of
13820 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
13821 - Try to detect if we are ever building on a platform where
13822 memset(...,0,...) does not set the value of a double to 0.0. Such
13823 platforms are permitted by the C standard, though in practice
13824 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
13825 currently support them, but it's better to detect them and fail
13826 than to perform erroneously.
13828 o Removed features:
13829 - Stop exporting estimates of v2 and v3 directory traffic shares
13830 in extrainfo documents. They were unneeded and sometimes inaccurate.
13831 Also stop exporting any v2 directory request statistics. Resolves
13833 - Drop support for detecting and warning about versions of Libevent
13834 before 1.3e. Nothing reasonable ships with them any longer;
13835 warning the user about them shouldn't be needed. Resolves ticket
13838 o Code simplifications and refactoring:
13839 - Rename "isin" functions to "contains", for grammar. Resolves
13841 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
13842 with the natural logarithm function from the system libm. Resolves
13846 Changes in version 0.2.4.9-alpha - 2013-01-15
13847 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
13848 work more robustly.
13851 - Fix backward compatibility logic when receiving an embedded ntor
13852 handshake tunneled in a CREATE cell. This clears up the "Bug:
13853 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
13857 Changes in version 0.2.4.8-alpha - 2013-01-14
13858 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
13859 risks, adds a new stronger and faster circuit handshake, and offers
13860 stronger and faster link encryption when both sides support it.
13863 - Preliminary support for directory guards (proposal 207): when
13864 possible, clients now use their entry guards for non-anonymous
13865 directory requests. This can help prevent client enumeration. Note
13866 that this behavior only works when we have a usable consensus
13867 directory, and when options about what to download are more or less
13868 standard. In the future we should re-bootstrap from our guards,
13869 rather than re-bootstrapping from the preconfigured list of
13870 directory sources that ships with Tor. Resolves ticket 6526.
13871 - Tor relays and clients now support a better CREATE/EXTEND cell
13872 format, allowing the sender to specify multiple address, identity,
13873 and handshake types. Implements Robert Ransom's proposal 200;
13874 closes ticket 7199.
13876 o Major features (new circuit handshake):
13877 - Tor now supports a new circuit extension handshake designed by Ian
13878 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
13879 circuit extension handshake, later called "TAP", was a bit slow
13880 (especially on the relay side), had a fragile security proof, and
13881 used weaker keys than we'd now prefer. The new circuit handshake
13882 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
13883 function, making it significantly more secure than the older
13884 handshake, and significantly faster. Tor can use one of two built-in
13885 pure-C curve25519-donna implementations by Adam Langley, or it
13886 can link against the "nacl" library for a tuned version if present.
13888 The built-in version is very fast for 64-bit systems when building
13889 with GCC. The built-in 32-bit version is still faster than the
13890 old TAP protocol, but using libnacl is better on most such hosts.
13892 Clients don't currently use this protocol by default, since
13893 comparatively few clients support it so far. To try it, set
13894 UseNTorHandshake to 1.
13896 Implements proposal 216; closes ticket 7202.
13898 o Major features (better link encryption):
13899 - Relays can now enable the ECDHE TLS ciphersuites when available
13900 and appropriate. These ciphersuites let us negotiate forward-secure
13901 TLS secret keys more safely and more efficiently than with our
13902 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
13903 public relays prefer the (faster) P224 group, and bridges prefer
13904 the (more common) P256 group; you can override this with the
13907 Enabling these ciphers was a little tricky, since for a long time,
13908 clients had been claiming to support them without actually doing
13909 so, in order to foil fingerprinting. But with the client-side
13910 implementation of proposal 198 in 0.2.3.17-beta, clients can now
13911 match the ciphers from recent Firefox versions *and* list the
13912 ciphers they actually mean, so relays can believe such clients
13913 when they advertise ECDHE support in their TLS ClientHello messages.
13915 This feature requires clients running 0.2.3.17-beta or later,
13916 and requires both sides to be running OpenSSL 1.0.0 or later
13917 with ECC support. OpenSSL 1.0.1, with the compile-time option
13918 "enable-ec_nistp_64_gcc_128", is highly recommended.
13920 Implements the relay side of proposal 198; closes ticket 7200.
13923 - Avoid crashing when, as a relay without IPv6-exit support, a
13924 client insists on getting an IPv6 address or nothing. Fixes bug
13925 7814; bugfix on 0.2.4.7-alpha.
13928 - Improve circuit build timeout handling for hidden services.
13929 In particular: adjust build timeouts more accurately depending
13930 upon the number of hop-RTTs that a particular circuit type
13931 undergoes. Additionally, launch intro circuits in parallel
13932 if they timeout, and take the first one to reply as valid.
13933 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
13934 separate error codes; or at least, don't break for that reason.
13935 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
13936 - Update to the January 2 2013 Maxmind GeoLite Country database.
13938 o Minor features (testing):
13939 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
13940 (P-256) Diffie-Hellman handshakes to src/or/bench.
13941 - Add benchmark functions to test onion handshake performance.
13943 o Minor features (path bias detection):
13944 - Alter the Path Bias log messages to be more descriptive in terms
13945 of reporting timeouts and other statistics.
13946 - Create three levels of Path Bias log messages, as opposed to just
13947 two. These are configurable via consensus as well as via the torrc
13948 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
13949 The default values are 0.70, 0.50, and 0.30 respectively.
13950 - Separate the log message levels from the decision to drop guards,
13951 which also is available via torrc option PathBiasDropGuards.
13952 PathBiasDropGuards still defaults to 0 (off).
13953 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
13954 in combination with PathBiasExtremeRate.
13955 - Increase the default values for PathBiasScaleThreshold and
13956 PathBiasCircThreshold from (200, 20) to (300, 150).
13957 - Add in circuit usage accounting to path bias. If we try to use a
13958 built circuit but fail for any reason, it counts as path bias.
13959 Certain classes of circuits where the adversary gets to pick your
13960 destination node are exempt from this accounting. Usage accounting
13961 can be specifically disabled via consensus parameter or torrc.
13962 - Convert all internal path bias state to double-precision floating
13963 point, to avoid roundoff error and other issues.
13964 - Only record path bias information for circuits that have completed
13965 *two* hops. Assuming end-to-end tagging is the attack vector, this
13966 makes us more resilient to ambient circuit failure without any
13967 detection capability loss.
13969 o Minor bugfixes (log messages):
13970 - Rate-limit the "No circuits are opened. Relaxed timeout for a
13971 circuit with channel state open..." message to once per hour to
13972 keep it from filling the notice logs. Mitigates bug 7799 but does
13973 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
13974 - Avoid spurious warnings when configuring multiple client ports of
13975 which only some are nonlocal. Previously, we had claimed that some
13976 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
13979 o Code simplifications and refactoring:
13980 - Get rid of a couple of harmless clang warnings, where we compared
13981 enums to ints. These warnings are newly introduced in clang 3.2.
13982 - Split the onion.c file into separate modules for the onion queue
13983 and the different handshakes it supports.
13984 - Remove the marshalling/unmarshalling code for sending requests to
13985 cpuworkers over a socket, and instead just send structs. The
13986 recipient will always be the same Tor binary as the sender, so
13987 any encoding is overkill.
13990 Changes in version 0.2.4.7-alpha - 2012-12-24
13991 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
13992 directory mirrors for more robust bootstrapping; fixes more issues where
13993 clients with changing network conditions refuse to make any circuits;
13994 adds initial support for exiting to IPv6 addresses; resumes being able
13995 to update our GeoIP database, and includes the geoip6 file this time;
13996 turns off the client-side DNS cache by default due to privacy risks;
13997 and fixes a variety of other issues.
13999 o Major features (client resilience):
14000 - Add a new "FallbackDir" torrc option to use when we can't use
14001 a directory mirror from the consensus (either because we lack a
14002 consensus, or because they're all down). Currently, all authorities
14003 are fallbacks by default, and there are no other default fallbacks,
14004 but that will change. This option will allow us to give clients a
14005 longer list of servers to try to get a consensus from when first
14006 connecting to the Tor network, and thereby reduce load on the
14007 directory authorities. Implements proposal 206, "Preconfigured
14008 directory sources for bootstrapping". We also removed the old
14009 "FallbackNetworkstatus" option, since we never got it working well
14010 enough to use it. Closes bug 572.
14011 - If we have no circuits open, use a relaxed timeout (the
14012 95-percentile cutoff) until a circuit succeeds. This heuristic
14013 should allow Tor to succeed at building circuits even when the
14014 network connection drastically changes. Should help with bug 3443.
14016 o Major features (IPv6):
14017 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
14018 connectivity, then set the IPv6Exit flag to 1. Also make sure your
14019 exit policy reads as you would like: the address * applies to all
14020 address families, whereas *4 is IPv4 address only, and *6 is IPv6
14021 addresses only. On the client side, you'll need to wait until the
14022 authorities have upgraded, wait for enough exits to support IPv6,
14023 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
14024 ticket 5547, implements proposal 117 as revised in proposal 208.
14026 We DO NOT recommend that clients with actual anonymity needs start
14027 using IPv6 over Tor yet, since not enough exits support it yet.
14029 o Major features (geoip database):
14030 - Maxmind began labelling Tor relays as being in country "A1",
14031 which breaks by-country node selection inside Tor. Now we use a
14032 script to replace "A1" ("Anonymous Proxy") entries in our geoip
14033 file with real country codes. This script fixes about 90% of "A1"
14034 entries automatically and uses manual country code assignments to
14035 fix the remaining 10%. See src/config/README.geoip for details.
14036 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
14037 Country database, as modified above.
14039 o Major bugfixes (client-side DNS):
14040 - Turn off the client-side DNS cache by default. Updating and using
14041 the DNS cache is now configurable on a per-client-port
14042 level. SOCKSPort, DNSPort, etc lines may now contain
14043 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
14044 cache these types of DNS answers when we receive them from an
14045 exit node in response to an application request on this port, and
14046 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
14047 cached DNS answers of these types, we shouldn't use them. It's
14048 potentially risky to use cached DNS answers at the client, since
14049 doing so can indicate to one exit what answers we've gotten
14050 for DNS lookups in the past. With IPv6, this becomes especially
14051 problematic. Using cached DNS answers for requests on the same
14052 circuit would present less linkability risk, since all traffic
14053 on a circuit is already linkable, but it would also provide
14054 little performance benefit: the exit node caches DNS replies
14055 too. Implements a simplified version of Proposal 205. Implements
14058 o Major bugfixes (other):
14059 - Alter circuit build timeout measurement to start at the point
14060 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
14061 initialization). This should make our timeout measurements more
14062 uniform. Previously, we were sometimes including ORconn setup time
14063 in our circuit build time measurements. Should resolve bug 3443.
14064 - Fix an assertion that could trigger in hibernate_go_dormant() when
14065 closing an or_connection_t: call channel_mark_for_close() rather
14066 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
14068 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
14069 7655; bugfix on 0.2.4.6-alpha.
14072 - Add a new torrc option "ServerTransportListenAddr" to let bridge
14073 operators select the address where their pluggable transports will
14074 listen for connections. Resolves ticket 7013.
14075 - Allow an optional $ before the node identity digest in the
14076 controller command GETINFO ns/id/<identity>, for consistency with
14077 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
14078 - Log packaged cell fullness as part of the heartbeat message.
14079 Diagnosis to try to determine the extent of bug 7743.
14081 o Minor features (IPv6):
14082 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
14083 prefer to hand out virtual IPv6 addresses, since there are more of
14084 them and we can't run out. To override this behavior and make IPv4
14085 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
14086 or DNSPort you're using for resolving. Implements ticket 7571.
14087 - AutomapHostsOnResolve responses are now randomized, to avoid
14088 annoying situations where Tor is restarted and applications
14089 connect to the wrong addresses.
14090 - Never try more than 1000 times to pick a new virtual address when
14091 AutomapHostsOnResolve is set. That's good enough so long as we
14092 aren't close to handing out our entire virtual address space;
14093 if you're getting there, it's best to switch to IPv6 virtual
14097 - The ADDRMAP command can no longer generate an ill-formed error
14098 code on a failed MAPADDRESS. It now says "internal" rather than
14099 an English sentence fragment with spaces in the middle. Bugfix on
14100 Tor 0.2.0.19-alpha.
14101 - Fix log messages and comments to avoid saying "GMT" when we mean
14102 "UTC". Fixes bug 6113.
14103 - Compile on win64 using mingw64. Fixes bug 7260; patches from
14105 - Fix a crash when debugging unit tests on Windows: deallocate a
14106 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
14107 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
14110 - The DirServer option is now DirAuthority, for consistency with
14111 current naming patterns. You can still use the old DirServer form.
14113 o Code simplification and refactoring:
14114 - Move the client-side address-map/virtual-address/DNS-cache code
14115 out of connection_edge.c into a new addressmap.c module.
14116 - Remove unused code for parsing v1 directories and "running routers"
14117 documents. Fixes bug 6887.
14120 Changes in version 0.2.3.25 - 2012-11-19
14121 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
14122 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
14123 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
14124 programmer, and friend. Unstinting in his dedication to the cause of
14125 freedom, he inspired and helped many of us as we began our work on
14126 anonymity, and inspires us still. Please honor his memory by writing
14127 software to protect people's freedoms, and by helping others to do so.
14129 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
14130 significantly reduced directory overhead (via microdescriptors),
14131 enormous crypto performance improvements for fast relays on new
14132 enough hardware, a new v3 TLS handshake protocol that can better
14133 resist fingerprinting, support for protocol obfuscation plugins (aka
14134 pluggable transports), better scalability for hidden services, IPv6
14135 support for bridges, performance improvements like allowing clients
14136 to skip the first round-trip on the circuit ("optimistic data") and
14137 refilling token buckets more often, a new "stream isolation" design
14138 to isolate different applications on different circuits, and many
14139 stability, security, and privacy fixes.
14142 - Tor tries to wipe potentially sensitive data after using it, so
14143 that if some subsequent security failure exposes Tor's memory,
14144 the damage will be limited. But we had a bug where the compiler
14145 was eliminating these wipe operations when it decided that the
14146 memory was no longer visible to a (correctly running) program,
14147 hence defeating our attempt at defense in depth. We fix that
14148 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
14149 is unlikely to optimize away. Future versions of Tor may use
14150 a less ridiculously heavy approach for this. Fixes bug 7352.
14151 Reported in an article by Andrey Karpov.
14154 - Fix a harmless bug when opting against publishing a relay descriptor
14155 because DisableNetwork is set. Fixes bug 7464; bugfix on
14159 Changes in version 0.2.4.6-alpha - 2012-11-13
14160 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
14161 makes our defense-in-depth memory wiping more reliable, and begins to
14162 count IPv6 addresses in bridge statistics,
14165 - Fix an assertion failure that could occur when closing a connection
14166 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
14168 - Tor tries to wipe potentially sensitive data after using it, so
14169 that if some subsequent security failure exposes Tor's memory,
14170 the damage will be limited. But we had a bug where the compiler
14171 was eliminating these wipe operations when it decided that the
14172 memory was no longer visible to a (correctly running) program,
14173 hence defeating our attempt at defense in depth. We fix that
14174 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
14175 is unlikely to optimize away. Future versions of Tor may use
14176 a less ridiculously heavy approach for this. Fixes bug 7352.
14177 Reported in an article by Andrey Karpov.
14180 - Add GeoIP database for IPv6 addresses. The new config option
14182 - Bridge statistics now count bridge clients connecting over IPv6:
14183 bridge statistics files now list "bridge-ip-versions" and
14184 extra-info documents list "geoip6-db-digest". The control protocol
14185 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
14186 implementation by "shkoo", addressing ticket 5055.
14189 - Warn when we are binding low ports when hibernation is enabled;
14190 previously we had warned when we were _advertising_ low ports with
14191 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
14192 - Fix a harmless bug when opting against publishing a relay descriptor
14193 because DisableNetwork is set. Fixes bug 7464; bugfix on
14195 - Add warning message when a managed proxy dies during configuration.
14196 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
14197 - Fix a linking error when building tor-fw-helper without miniupnp.
14198 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
14199 - Check for closing an or_connection_t without going through correct
14200 channel functions; emit a warning and then call
14201 connection_or_close_for_error() so we don't assert as in bugs 7212
14203 - Compile correctly on compilers without C99 designated initializer
14204 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
14205 - Avoid a possible assert that can occur when channel_send_destroy() is
14206 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
14207 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
14208 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
14209 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
14210 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
14212 o Code simplification and refactoring:
14213 - Start using OpenBSD's implementation of queue.h, so that we don't
14214 need to hand-roll our own pointer and list structures whenever we
14215 need them. (We can't rely on a sys/queue.h, since some operating
14216 systems don't have them, and the ones that do have them don't all
14217 present the same extensions.)
14220 Changes in version 0.2.4.5-alpha - 2012-10-25
14221 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
14222 two important security vulnerabilities that could lead to remotely
14223 triggerable relay crashes, fix a major bug that was preventing clients
14224 from choosing suitable exit nodes, and refactor some of our code.
14226 o Major bugfixes (security, also in 0.2.3.24-rc):
14227 - Fix a group of remotely triggerable assertion failures related to
14228 incorrect link protocol negotiation. Found, diagnosed, and fixed
14229 by "some guy from France". Fix for CVE-2012-2250; bugfix on
14231 - Fix a denial of service attack by which any directory authority
14232 could crash all the others, or by which a single v2 directory
14233 authority could crash everybody downloading v2 directory
14234 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
14236 o Major bugfixes (also in 0.2.3.24-rc):
14237 - When parsing exit policy summaries from microdescriptors, we had
14238 previously been ignoring the last character in each one, so that
14239 "accept 80,443,8080" would be treated by clients as indicating
14240 a node that allows access to ports 80, 443, and 808. That would
14241 lead to clients attempting connections that could never work,
14242 and ignoring exit nodes that would support their connections. Now
14243 clients parse these exit policy summaries correctly. Fixes bug 7192;
14244 bugfix on 0.2.3.1-alpha.
14246 o Minor bugfixes (also in 0.2.3.24-rc):
14247 - Clients now consider the ClientRejectInternalAddresses config option
14248 when using a microdescriptor consensus stanza to decide whether
14249 an exit relay would allow exiting to an internal address. Fixes
14250 bug 7190; bugfix on 0.2.3.1-alpha.
14253 - Only disable TLS session ticket support when running as a TLS
14254 server. Now clients will blend better with regular Firefox
14255 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
14257 o Code simplification and refactoring:
14258 - Start using OpenBSD's implementation of queue.h (originally by
14260 - Move the entry node code from circuitbuild.c to its own file.
14261 - Move the circuit build timeout tracking code from circuitbuild.c
14265 Changes in version 0.2.3.24-rc - 2012-10-25
14266 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
14267 could lead to remotely triggerable relay crashes, and fixes
14268 a major bug that was preventing clients from choosing suitable exit
14271 o Major bugfixes (security):
14272 - Fix a group of remotely triggerable assertion failures related to
14273 incorrect link protocol negotiation. Found, diagnosed, and fixed
14274 by "some guy from France". Fix for CVE-2012-2250; bugfix on
14276 - Fix a denial of service attack by which any directory authority
14277 could crash all the others, or by which a single v2 directory
14278 authority could crash everybody downloading v2 directory
14279 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
14282 - When parsing exit policy summaries from microdescriptors, we had
14283 previously been ignoring the last character in each one, so that
14284 "accept 80,443,8080" would be treated by clients as indicating
14285 a node that allows access to ports 80, 443, and 808. That would
14286 lead to clients attempting connections that could never work,
14287 and ignoring exit nodes that would support their connections. Now
14288 clients parse these exit policy summaries correctly. Fixes bug 7192;
14289 bugfix on 0.2.3.1-alpha.
14292 - Clients now consider the ClientRejectInternalAddresses config option
14293 when using a microdescriptor consensus stanza to decide whether
14294 an exit relay would allow exiting to an internal address. Fixes
14295 bug 7190; bugfix on 0.2.3.1-alpha.
14298 Changes in version 0.2.4.4-alpha - 2012-10-20
14299 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
14300 vulnerability introduced by a change in OpenSSL, fixes a remotely
14301 triggerable assert, and adds new channel_t and circuitmux_t abstractions
14302 that will make it easier to test new connection transport and cell
14303 scheduling algorithms.
14305 o New directory authorities (also in 0.2.3.23-rc):
14306 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
14307 authority. Closes ticket 5749.
14309 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
14310 - Disable TLS session tickets. OpenSSL's implementation was giving
14311 our TLS session keys the lifetime of our TLS context objects, when
14312 perfect forward secrecy would want us to discard anything that
14313 could decrypt a link connection as soon as the link connection
14314 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
14315 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
14316 - Discard extraneous renegotiation attempts once the V3 link
14317 protocol has been initiated. Failure to do so left us open to
14318 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
14319 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
14321 o Internal abstraction features:
14322 - Introduce new channel_t abstraction between circuits and
14323 or_connection_t to allow for implementing alternate OR-to-OR
14324 transports. A channel_t is an abstract object which can either be a
14325 cell-bearing channel, which is responsible for authenticating and
14326 handshaking with the remote OR and transmitting cells to and from
14327 it, or a listening channel, which spawns new cell-bearing channels
14328 at the request of remote ORs. Implements part of ticket 6465.
14329 - Also new is the channel_tls_t subclass of channel_t, adapting it
14330 to the existing or_connection_t code. The V2/V3 protocol handshaking
14331 code which formerly resided in command.c has been moved below the
14332 channel_t abstraction layer and may be found in channeltls.c now.
14333 Implements the rest of ticket 6465.
14334 - Introduce new circuitmux_t storing the queue of circuits for
14335 a channel; this encapsulates and abstracts the queue logic and
14336 circuit selection policy, and allows the latter to be overridden
14337 easily by switching out a policy object. The existing EWMA behavior
14338 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
14340 o Required libraries:
14341 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
14342 strongly recommended.
14345 - Warn users who run hidden services on a Tor client with
14346 UseEntryGuards disabled that their hidden services will be
14347 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
14348 attack which motivated Tor to support entry guards in the first
14349 place). Resolves ticket 6889.
14350 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
14351 dhill. Resolves ticket 6982.
14352 - Option OutboundBindAddress can be specified multiple times and
14353 accepts IPv6 addresses. Resolves ticket 6876.
14355 o Minor bugfixes (also in 0.2.3.23-rc):
14356 - Don't serve or accept v2 hidden service descriptors over a
14357 relay's DirPort. It's never correct to do so, and disabling it
14358 might make it more annoying to exploit any bugs that turn up in the
14359 descriptor-parsing code. Fixes bug 7149.
14360 - Fix two cases in src/or/transports.c where we were calling
14361 fmt_addr() twice in a parameter list. Bug found by David
14362 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
14363 - Fix memory leaks whenever we logged any message about the "path
14364 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
14365 - When relays refuse a "create" cell because their queue of pending
14366 create cells is too big (typically because their cpu can't keep up
14367 with the arrival rate), send back reason "resource limit" rather
14368 than reason "internal", so network measurement scripts can get a
14369 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
14372 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
14373 - Free some more still-in-use memory at exit, to make hunting for
14374 memory leaks easier. Resolves bug 7029.
14375 - When a Tor client gets a "truncated" relay cell, the first byte of
14376 its payload specifies why the circuit was truncated. We were
14377 ignoring this 'reason' byte when tearing down the circuit, resulting
14378 in the controller not being told why the circuit closed. Now we
14379 pass the reason from the truncated cell to the controller. Bugfix
14380 on 0.1.2.3-alpha; fixes bug 7039.
14381 - Downgrade "Failed to hand off onionskin" messages to "debug"
14382 severity, since they're typically redundant with the "Your computer
14383 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
14384 - Make clients running with IPv6 bridges connect over IPv6 again,
14385 even without setting new config options ClientUseIPv6 and
14386 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
14387 - Use square brackets around IPv6 addresses in numerous places
14388 that needed them, including log messages, HTTPS CONNECT proxy
14389 requests, TransportProxy statefile entries, and pluggable transport
14390 extra-info lines. Fixes bug 7011; patch by David Fifield.
14392 o Code refactoring and cleanup:
14393 - Source files taken from other packages now reside in src/ext;
14394 previously they were scattered around the rest of Tor.
14395 - Avoid use of reserved identifiers in our C code. The C standard
14396 doesn't like us declaring anything that starts with an
14397 underscore, so let's knock it off before we get in trouble. Fix
14398 for bug 1031; bugfix on the first Tor commit.
14401 Changes in version 0.2.3.23-rc - 2012-10-20
14402 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
14403 vulnerability introduced by a change in OpenSSL, and fixes a variety
14404 of smaller bugs in preparation for the release.
14406 o New directory authorities:
14407 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
14408 authority. Closes ticket 5749.
14410 o Major bugfixes (security/privacy):
14411 - Disable TLS session tickets. OpenSSL's implementation was giving
14412 our TLS session keys the lifetime of our TLS context objects, when
14413 perfect forward secrecy would want us to discard anything that
14414 could decrypt a link connection as soon as the link connection
14415 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
14416 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
14417 - Discard extraneous renegotiation attempts once the V3 link
14418 protocol has been initiated. Failure to do so left us open to
14419 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
14420 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
14423 - Fix a possible crash bug when checking for deactivated circuits
14424 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
14425 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
14427 o Minor bugfixes (on 0.2.3.x):
14428 - Fix two cases in src/or/transports.c where we were calling
14429 fmt_addr() twice in a parameter list. Bug found by David
14430 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
14431 - Convert an assert in the pathbias code to a log message. The assert
14432 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
14433 bugfix on 0.2.3.17-beta.
14434 - Fix memory leaks whenever we logged any message about the "path
14435 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
14437 o Minor bugfixes (on 0.2.2.x and earlier):
14438 - Don't serve or accept v2 hidden service descriptors over a relay's
14439 DirPort. It's never correct to do so, and disabling it might
14440 make it more annoying to exploit any bugs that turn up in the
14441 descriptor-parsing code. Fixes bug 7149.
14442 - When relays refuse a "create" cell because their queue of pending
14443 create cells is too big (typically because their cpu can't keep up
14444 with the arrival rate), send back reason "resource limit" rather
14445 than reason "internal", so network measurement scripts can get a
14446 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
14447 - Correct file sizes when reading binary files on Cygwin, to avoid
14448 a bug where Tor would fail to read its state file. Fixes bug 6844;
14449 bugfix on 0.1.2.7-alpha.
14450 - Avoid undefined behavior when parsing the list of supported
14451 rendezvous/introduction protocols in a hidden service descriptor.
14452 Previously, Tor would have confused (as-yet-unused) protocol version
14453 numbers greater than 32 with lower ones on many platforms. Fixes
14454 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
14456 o Documentation fixes:
14457 - Clarify that hidden services are TCP only. Fixes bug 6024.
14460 Changes in version 0.2.4.3-alpha - 2012-09-22
14461 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
14462 assertion, resumes letting relays test reachability of their DirPort,
14463 and cleans up a bunch of smaller bugs.
14466 - Fix an assertion failure in tor_timegm() that could be triggered
14467 by a badly formatted directory object. Bug found by fuzzing with
14468 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
14471 - Fix a possible crash bug when checking for deactivated circuits
14472 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
14473 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
14474 - Allow routers to detect that their own DirPorts are running. When
14475 we removed support for versions_supports_begindir, we also
14476 accidentally removed the mechanism we used to self-test our
14477 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
14478 bugfix on 0.2.4.2-alpha.
14480 o Security features:
14481 - Switch to a completely time-invariant approach for picking nodes
14482 weighted by bandwidth. Our old approach would run through the
14483 part of the loop after it had made its choice slightly slower
14484 than it ran through the part of the loop before it had made its
14485 choice. Addresses ticket 6538.
14486 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
14487 by tor2web clients allows hidden services to identify tor2web
14488 clients through their repeated selection of the same rendezvous
14489 and introduction point circuit endpoints (their guards). Resolves
14493 - Enable Tor to read configuration, state, and key information from
14494 a FIFO. Previously Tor would only read from files with a positive
14495 stat.st_size. Code from meejah; fixes bug 6044.
14498 - Correct file sizes when reading binary files on Cygwin, to avoid
14499 a bug where Tor would fail to read its state file. Fixes bug 6844;
14500 bugfix on 0.1.2.7-alpha.
14501 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
14502 bugfix on 0.2.0.3-alpha.
14503 - When complaining about a client port on a public address, log
14504 which address we're complaining about. Fixes bug 4020; bugfix on
14505 0.2.3.3-alpha. Patch by Tom Fitzhenry.
14506 - Convert an assert in the pathbias code to a log message. The assert
14507 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
14508 bugfix on 0.2.3.17-beta.
14509 - Our new buildsystem was overzealous about rebuilding manpages: it
14510 would rebuild them all whenever any one of them changed. Now our
14511 dependency checking should be correct. Fixes bug 6843; bugfix on
14513 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
14514 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
14515 - Correct log printout about which address family is preferred
14516 when connecting to a bridge with both an IPv4 and IPv6 OR port.
14517 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
14519 o Minor bugfixes (code cleanliness):
14520 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
14521 with large values. This situation was untriggered, but nevertheless
14522 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
14523 - Reject consensus votes with more than 64 known-flags. We aren't even
14524 close to that limit yet, and our code doesn't handle it correctly.
14525 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
14526 - Avoid undefined behavior when parsing the list of supported
14527 rendezvous/introduction protocols in a hidden service descriptor.
14528 Previously, Tor would have confused (as-yet-unused) protocol version
14529 numbers greater than 32 with lower ones on many platforms. Fixes
14530 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
14531 - Fix handling of rendezvous client authorization types over 8.
14532 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
14533 - Fix building with older versions of GCC (2.95, for one) that don't
14534 like preprocessor directives inside macro arguments. Found by
14535 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
14536 - Switch weighted node selection rule from using a list of doubles
14537 to using a list of int64_t. This change should make the process
14538 slightly easier to debug and maintain. Needed to finish ticket 6538.
14540 o Code simplification and refactoring:
14541 - Move the generic "config" code into a new file, and have "config.c"
14542 hold only torrc- and state-related code. Resolves ticket 6823.
14543 - Move the core of our "choose a weighted element at random" logic
14544 into its own function, and give it unit tests. Now the logic is
14545 testable, and a little less fragile too.
14546 - Removed the testing_since field of node_t, which hasn't been used
14547 for anything since 0.2.0.9-alpha.
14549 o Documentation fixes:
14550 - Clarify that hidden services are TCP only. Fixes bug 6024.
14551 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
14555 Changes in version 0.2.3.22-rc - 2012-09-11
14556 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
14560 - Fix an assertion failure in tor_timegm() that could be triggered
14561 by a badly formatted directory object. Bug found by fuzzing with
14562 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
14565 - Avoid segfault when starting up having run with an extremely old
14566 version of Tor and parsing its state file. Fixes bug 6801; bugfix
14570 Changes in version 0.2.2.39 - 2012-09-11
14571 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
14575 - Fix an assertion failure in tor_timegm() that could be triggered
14576 by a badly formatted directory object. Bug found by fuzzing with
14577 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
14578 - Do not crash when comparing an address with port value 0 to an
14579 address policy. This bug could have been used to cause a remote
14580 assertion failure by or against directory authorities, or to
14581 allow some applications to crash clients. Fixes bug 6690; bugfix
14585 Changes in version 0.2.4.2-alpha - 2012-09-10
14586 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
14587 raises the default rate limiting even more, and makes the bootstrapping
14588 log messages less noisy.
14591 - Automatically forward the TCP ports of pluggable transport
14592 proxies using tor-fw-helper if PortForwarding is enabled. Implements
14596 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
14597 to 1GB/1GB. The previous defaults were intended to be "basically
14598 infinite", but it turns out they're now limiting our 100mbit+
14599 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
14600 last time we raised it).
14603 - Detect when we're running with a version of OpenSSL other than the
14604 one we compiled with. This has occasionally given people hard-to-
14606 - Log fewer lines at level "notice" about our OpenSSL and Libevent
14607 versions and capabilities when everything is going right. Resolves
14608 part of ticket 6736.
14609 - Directory authorities no long accept descriptors for any version of
14610 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
14611 These versions are insecure, unsupported, or both. Implements
14615 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
14616 to start with a triple-underscore so the controller won't touch it.
14617 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
14618 - Avoid segfault when starting up having run with an extremely old
14619 version of Tor and parsing its state file. Fixes bug 6801; bugfix
14621 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
14622 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
14623 - Don't follow the NULL pointer if microdescriptor generation fails.
14624 (This does not appear to be triggerable, but it's best to be safe.)
14625 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
14626 - Fix mis-declared dependencies on src/common/crypto.c and
14627 src/or/tor_main.c that could break out-of-tree builds under some
14628 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
14629 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
14630 6778; bugfix on 0.2.4.1-alpha.
14631 - Fix a harmless (in this case) build warning for implicitly
14632 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
14634 o Removed features:
14635 - Now that all versions before 0.2.2.x are disallowed, we no longer
14636 need to work around their missing features. Thus we can remove a
14637 bunch of compatibility code.
14639 o Code refactoring:
14640 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
14641 TCP ports to forward. In the past it only accepted two ports:
14642 the ORPort and the DirPort.
14645 Changes in version 0.2.4.1-alpha - 2012-09-05
14646 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
14647 bridgedb; lets relays use IPv6 addresses and directory authorities
14648 advertise them; and switches to a cleaner build interface.
14650 This is the first alpha release in a new series, so expect there to
14651 be bugs. Users who would rather test out a more stable branch should
14652 stay with 0.2.3.x for now.
14654 o Major features (bridges):
14655 - Bridges now report the pluggable transports they support to the
14656 bridge authority, so it can pass the supported transports on to
14657 bridgedb and/or eventually do reachability testing. Implements
14660 o Major features (IPv6):
14661 - Bridge authorities now accept IPv6 bridge addresses and include
14662 them in network status documents. Implements ticket 5534.
14663 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
14664 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
14665 to happen. Implements ticket 5535.
14666 - All kind of relays, not just bridges, can now advertise an IPv6
14667 OR port. Implements ticket 6362.
14668 - Directory authorities vote on IPv6 OR ports using the new consensus
14669 method 14. Implements ticket 6363.
14671 o Major features (build):
14672 - Switch to a nonrecursive Makefile structure. Now instead of each
14673 Makefile.am invoking other Makefile.am's, there is a master
14674 Makefile.am that includes the others. This change makes our build
14675 process slightly more maintainable, and improves parallelism for
14676 building with make -j. Original patch by Stewart Smith; various
14677 fixes by Jim Meyering.
14678 - Where available, we now use automake's "silent" make rules by
14679 default, so that warnings are easier to spot. You can get the old
14680 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
14682 o Minor features (code security and spec conformance):
14683 - Clear keys and key-derived material left on the stack in
14684 rendservice.c and rendclient.c. Check return value of
14685 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
14686 These fixes should make us more forward-secure against cold-boot
14687 attacks and the like. Fixes bug 2385.
14688 - Reject EXTEND cells sent to nonexistent streams. According to the
14689 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
14690 we were only checking for stream IDs that were currently in use.
14691 Found while hunting for more instances of bug 6271. Bugfix on
14692 0.0.2pre8, which introduced incremental circuit construction.
14694 o Minor features (streamlining);
14695 - No longer include the "opt" prefix when generating routerinfos
14696 or v2 directories: it has been needless since Tor 0.1.2. Closes
14698 - Remove some now-needless code that tried to aggressively flush
14699 OR connections as data was added to them. Since 0.2.0.1-alpha, our
14700 cell queue logic has saved us from the failure mode that this code
14701 was supposed to prevent. Removing this code will limit the number
14702 of baroque control flow paths through Tor's network logic. Reported
14703 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
14705 o Minor features (controller):
14706 - Add a "GETINFO signal/names" control port command. Implements
14708 - Provide default values for all options via "GETINFO config/defaults".
14709 Implements ticket 4971.
14711 o Minor features (IPv6):
14712 - New config option "AuthDirHasIPv6Connectivity 1" that directory
14713 authorities should set if they have IPv6 connectivity and want to
14714 do reachability tests for IPv6 relays. Implements feature 5974.
14715 - A relay with an IPv6 OR port now sends that address in NETINFO
14716 cells (in addition to its other address). Implements ticket 6364.
14718 o Minor features (log messages):
14719 - Omit the first heartbeat log message, because it never has anything
14720 useful to say, and it clutters up the bootstrapping messages.
14721 Resolves ticket 6758.
14722 - Don't log about reloading the microdescriptor cache at startup. Our
14723 bootstrap warnings are supposed to tell the user when there's a
14724 problem, and our bootstrap notices say when there isn't. Resolves
14725 ticket 6759; bugfix on 0.2.2.6-alpha.
14726 - Don't log "I learned some more directory information" when we're
14727 reading cached directory information. Reserve it for when new
14728 directory information arrives in response to a fetch. Resolves
14730 - Prevent rounding error in path bias counts when scaling
14731 them down, and use the correct scale factor default. Also demote
14732 some path bias related log messages down a level and make others
14733 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
14734 - We no longer warn so much when generating manpages from their
14737 o Code simplifications and refactoring:
14738 - Enhance our internal sscanf replacement so that we can eliminate
14739 the last remaining uses of the system sscanf. (Though those uses
14740 of sscanf were safe, sscanf itself is generally error prone, so
14741 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
14743 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
14744 - Move last_reachable and testing_since from routerinfo_t to node_t.
14745 Implements ticket 5529.
14746 - Add replaycache_t structure, functions and unit tests, then refactor
14747 rend_service_introduce() to be more clear to read, improve, debug,
14748 and test. Resolves bug 6177.
14749 - Finally remove support for malloc_good_size and malloc_usable_size.
14750 We had hoped that these functions would let us eke a little more
14751 memory out of our malloc implementation. Unfortunately, the only
14752 implementations that provided these functions are also ones that
14753 are already efficient about not overallocation: they never got us
14754 more than 7 or so bytes per allocation. Removing them saves us a
14755 little code complexity and a nontrivial amount of build complexity.
14757 o New requirements:
14758 - Tor maintainers now require Automake version 1.9 or later to build
14759 Tor from the Git repository. (Automake is not required when building
14760 from a source distribution.)
14763 Changes in version 0.2.3.21-rc - 2012-09-05
14764 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
14765 series. It fixes a trio of potential security bugs, fixes a bug where
14766 we were leaving some of the fast relays out of the microdescriptor
14767 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
14768 and cleans up other smaller issues.
14770 o Major bugfixes (security):
14771 - Tear down the circuit if we get an unexpected SENDME cell. Clients
14772 could use this trick to make their circuits receive cells faster
14773 than our flow control would have allowed, or to gum up the network,
14774 or possibly to do targeted memory denial-of-service attacks on
14775 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
14776 from July 2002, before the release of Tor 0.0.0. We had committed
14777 this patch previously, but we had to revert it because of bug 6271.
14778 Now that 6271 is fixed, this patch appears to work.
14779 - Reject any attempt to extend to an internal address. Without
14780 this fix, a router could be used to probe addresses on an internal
14781 network to see whether they were accepting connections. Fixes bug
14782 6710; bugfix on 0.0.8pre1.
14783 - Do not crash when comparing an address with port value 0 to an
14784 address policy. This bug could have been used to cause a remote
14785 assertion failure by or against directory authorities, or to
14786 allow some applications to crash clients. Fixes bug 6690; bugfix
14790 - Remove the upper bound on microdescriptor length. We were hitting
14791 the limit for routers with complex exit policies or family
14792 declarations, causing clients to not use them. Fixes the first
14793 piece of bug 6404; fix on 0.2.2.6-alpha.
14794 - Detect "ORPort 0" as meaning, uniformly, that we're not running
14795 as a relay. Previously, some of our code would treat the presence
14796 of any ORPort line as meaning that we should act like a relay,
14797 even though our new listener code would correctly not open any
14798 ORPorts for ORPort 0. Similar bugs in other Port options are also
14799 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
14802 - Avoid a pair of double-free and use-after-mark bugs that can
14803 occur with certain timings in canceled and re-received DNS
14804 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
14805 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
14806 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
14807 - Allow one-hop directory fetching circuits the full "circuit build
14808 timeout" period, rather than just half of it, before failing them
14809 and marking the relay down. This fix should help reduce cases where
14810 clients declare relays (or worse, bridges) unreachable because
14811 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
14812 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
14814 - Authorities no longer include any router in their microdescriptor
14815 consensuses for which they couldn't generate or agree on a
14816 microdescriptor. Fixes the second piece of bug 6404; fix on
14818 - Detect and reject attempts to specify both "FooPort" and
14819 "FooPort 0" in the same configuration domain. (It's still okay
14820 to have a FooPort in your configuration file, and use "FooPort 0"
14821 on the command line to disable it.) Fixes the second half of bug
14822 6507; bugfix on 0.2.3.3-alpha.
14823 - Make wildcarded addresses (that is, ones beginning with "*.") work
14824 when provided via the controller's MapAddress command. Previously,
14825 they were accepted, but we never actually noticed that they were
14826 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
14827 - Avoid crashing on a malformed state file where EntryGuardPathBias
14828 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
14829 - Add a (probably redundant) memory clear between iterations of
14830 the router status voting loop, to prevent future coding errors
14831 where data might leak between iterations of the loop. Resolves
14834 o Minor bugfixes (log messages):
14835 - Downgrade "set buildtimeout to low value" messages to "info"
14836 severity; they were never an actual problem, there was never
14837 anything reasonable to do about them, and they tended to spam logs
14838 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
14839 - Downgrade path-bias warning messages to "info". We'll try to get
14840 them working better in 0.2.4. Add internal circuit construction
14841 state to protect against the noisy warn message "Unexpectedly high
14842 circuit_successes". Also add some additional rate-limited notice
14843 messages to help determine the root cause of the warn. Fixes bug
14844 6475. Bugfix against 0.2.3.17-beta.
14845 - Move log message when unable to find a microdesc in a routerstatus
14846 entry to parse time. Previously we'd spam this warning every time
14847 we tried to figure out which microdescriptors to download. Fixes
14848 the third piece of bug 6404; fix on 0.2.3.18-rc.
14851 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
14852 change when the authority is deciding whether to accept a newly
14853 uploaded descriptor. Implements ticket 6423.
14854 - Add missing documentation for consensus and microdesc files.
14855 Resolves ticket 6732.
14858 Changes in version 0.2.2.38 - 2012-08-12
14859 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
14860 attack that could in theory leak path information.
14863 - Avoid an uninitialized memory read when reading a vote or consensus
14864 document that has an unrecognized flavor name. This read could
14865 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
14866 - Try to leak less information about what relays a client is
14867 choosing to a side-channel attacker. Previously, a Tor client would
14868 stop iterating through the list of available relays as soon as it
14869 had chosen one, thus finishing a little earlier when it picked
14870 a router earlier in the list. If an attacker can recover this
14871 timing information (nontrivial but not proven to be impossible),
14872 they could learn some coarse-grained information about which relays
14873 a client was picking (middle nodes in particular are likelier to
14874 be affected than exits). The timing attack might be mitigated by
14875 other factors (see bug 6537 for some discussion), but it's best
14876 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
14879 Changes in version 0.2.3.20-rc - 2012-08-05
14880 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
14881 series. It fixes a pair of code security bugs and a potential anonymity
14882 issue, updates our RPM spec files, and cleans up other smaller issues.
14885 - Avoid read-from-freed-memory and double-free bugs that could occur
14886 when a DNS request fails while launching it. Fixes bug 6480;
14887 bugfix on 0.2.0.1-alpha.
14888 - Avoid an uninitialized memory read when reading a vote or consensus
14889 document that has an unrecognized flavor name. This read could
14890 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
14891 - Try to leak less information about what relays a client is
14892 choosing to a side-channel attacker. Previously, a Tor client would
14893 stop iterating through the list of available relays as soon as it
14894 had chosen one, thus finishing a little earlier when it picked
14895 a router earlier in the list. If an attacker can recover this
14896 timing information (nontrivial but not proven to be impossible),
14897 they could learn some coarse-grained information about which relays
14898 a client was picking (middle nodes in particular are likelier to
14899 be affected than exits). The timing attack might be mitigated by
14900 other factors (see bug 6537 for some discussion), but it's best
14901 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
14904 - Try to make the warning when giving an obsolete SOCKSListenAddress
14905 a little more useful.
14906 - Terminate active server managed proxies if Tor stops being a
14907 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
14908 - Provide a better error message about possible OSX Asciidoc failure
14909 reasons. Fixes bug 6436.
14910 - Warn when Tor is configured to use accounting in a way that can
14911 link a hidden service to some other hidden service or public
14912 address. Resolves ticket 6490.
14915 - Check return value of fputs() when writing authority certificate
14916 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
14917 - Ignore ServerTransportPlugin lines when Tor is not configured as
14918 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
14919 - When disabling guards for having too high a proportion of failed
14920 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
14924 - Update our default RPM spec files to work with mock and rpmbuild
14925 on RHEL/Fedora. They have an updated set of dependencies and
14926 conflicts, a fix for an ancient typo when creating the "_tor"
14927 user, and better instructions. Thanks to Ondrej Mikle for the
14928 patch series. Fixes bug 6043.
14931 - Make it possible to set the TestingTorNetwork configuration
14932 option using AlternateDirAuthority and AlternateBridgeAuthority
14933 as an alternative to setting DirServer. Addresses ticket 6377.
14936 - Clarify the documentation for the Alternate*Authority options.
14938 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
14940 o Code simplification and refactoring:
14941 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
14942 10 lines. Also, don't nest them. Doing so in the past has
14943 led to hard-to-debug code. The new style is to use the
14944 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
14947 Changes in version 0.2.3.19-rc - 2012-07-06
14948 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
14949 series. It fixes the compile on Windows, reverts to a GeoIP database
14950 that isn't as broken, and fixes a flow control bug that has been around
14951 since the beginning of Tor.
14954 - Fix a bug handling SENDME cells on nonexistent streams that could
14955 result in bizarre window values. Report and patch contributed
14956 pseudonymously. Fixes part of bug 6271. This bug was introduced
14957 before the first Tor release, in svn commit r152.
14958 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
14959 June 2012 database, Maxmind marked many Tor relays as country "A1",
14960 which will cause risky behavior for clients that set EntryNodes
14961 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
14962 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
14963 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
14966 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
14967 bugfix on 0.2.1.10-alpha.
14970 Changes in version 0.2.3.18-rc - 2012-06-28
14971 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
14972 series. It fixes a few smaller bugs, but generally appears stable.
14973 Please test it and let us know whether it is!
14976 - Allow wildcarded mapaddress targets to be specified on the
14977 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
14978 - Make our linker option detection code more robust against linkers
14979 such as on FreeBSD 8, where a bad combination of options completes
14980 successfully but makes an unrunnable binary. Fixes bug 6173;
14981 bugfix on 0.2.3.17-beta.
14983 o Minor bugfixes (on 0.2.2.x and earlier):
14984 - Avoid a false positive in the util/threads unit test by increasing
14985 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
14986 - Replace "Sending publish request" log messages with "Launching
14987 upload", so that they no longer confusingly imply that we're
14988 sending something to a directory we might not even be connected
14989 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
14990 - Make sure to set *socket_error in all error cases in
14991 connection_connect(), so it can't produce a warning about
14992 errno being zero from errno_to_orconn_end_reason(). Bugfix on
14993 0.2.1.1-alpha; resolves ticket 6028.
14994 - Downgrade "Got a certificate, but we already have it" log messages
14995 from warning to info, except when we're a dirauth. Fixes bug 5238;
14996 bugfix on 0.2.1.7-alpha.
14997 - When checking for requested signatures on the latest consensus
14998 before serving it to a client, make sure to check the right
14999 consensus flavor. Bugfix on 0.2.2.6-alpha.
15000 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
15001 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
15003 o Minor bugfixes (on 0.2.3.x):
15004 - Make format_helper_exit_status() avoid unnecessary space padding
15005 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
15007 - Downgrade a message about cleaning the microdescriptor cache to
15008 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
15009 - Log a BUG message at severity INFO if we have a networkstatus with
15010 a missing entry for some microdescriptor. Continues on a patch
15012 - Improve the log message when a managed proxy fails to launch. Fixes
15013 bug 5099; bugfix on 0.2.3.6-alpha.
15014 - Don't do DNS lookups when parsing corrupted managed proxy protocol
15015 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
15016 - When formatting wildcarded address mappings for the controller,
15017 be sure to include "*." as appropriate. Partially fixes bug 6244;
15018 bugfix on 0.2.3.9-alpha.
15019 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
15020 Bugfix on 0.2.3.13-alpha.
15021 - Stop logging messages about running with circuit timeout learning
15022 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
15023 - Disable a spurious warning about reading on a marked and flushing
15024 connection. We shouldn't be doing that, but apparently we
15025 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
15026 - Fix a bug that stopped AllowDotExit from working on addresses
15027 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
15030 o Code simplification, refactoring, unit tests:
15031 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
15032 Libevent's notion of cached time when possible.
15033 - Remove duplicate code for invoking getrlimit() from control.c.
15034 - Add a unit test for the environment_variable_names_equal function.
15037 - Document the --defaults-torrc option, and the new (in 0.2.3)
15038 semantics for overriding, extending, and clearing lists of
15039 options. Closes bug 4748.
15042 Changes in version 0.2.3.17-beta - 2012-06-15
15043 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
15044 gets our TLS handshake back on track for being able to blend in with
15045 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
15046 with Vidalia, and otherwise continues to get us closer to a release
15050 - Enable gcc and ld hardening by default. Resolves ticket 5210.
15051 - Update TLS cipher list to match Firefox 8 and later. Resolves
15053 - Implement the client side of proposal 198: remove support for
15054 clients falsely claiming to support standard ciphersuites that
15055 they can actually provide. As of modern OpenSSL versions, it's not
15056 necessary to fake any standard ciphersuite, and doing so prevents
15057 us from using better ciphersuites in the future, since servers
15058 can't know whether an advertised ciphersuite is really supported or
15059 not. Some hosts -- notably, ones with very old versions of OpenSSL
15060 or where OpenSSL has been built with ECC disabled -- will stand
15061 out because of this change; TBB users should not be affected.
15064 - Change the default value for DynamicDHGroups (introduced in
15065 0.2.3.9-alpha) to 0. This feature can make Tor relays less
15066 identifiable by their use of the mod_ssl DH group, but at
15067 the cost of some usability (#4721) and bridge tracing (#6087)
15068 regressions. Resolves ticket 5598.
15069 - Send a CRLF at the end of each STATUS_* control protocol event. This
15070 bug tickled a bug in Vidalia which would make it freeze. Fixes
15071 bug 6094; bugfix on 0.2.3.16-alpha.
15074 - Disable writing on marked-for-close connections when they are
15075 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
15076 bug 5263; bugfix on 0.0.2pre13, where we first added a special
15077 case for flushing marked connections.
15078 - Detect SSL handshake even when the initial attempt to write the
15079 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
15080 - Change the AllowDotExit rules so they should actually work.
15081 We now enforce AllowDotExit only immediately after receiving an
15082 address via SOCKS or DNSPort: other sources are free to provide
15083 .exit addresses after the resolution occurs. Fixes bug 3940;
15084 bugfix on 0.2.2.1-alpha.
15085 - Fix a (harmless) integer overflow in cell statistics reported by
15086 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
15087 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
15088 right places and never depends on the consensus parameters or
15089 computes adaptive timeouts when it is disabled. Fixes bug 5049;
15090 bugfix on 0.2.2.14-alpha.
15091 - When building Tor on Windows with -DUNICODE (not default), ensure
15092 that error messages, filenames, and DNS server names are always
15093 NUL-terminated when we convert them to a single-byte encoding.
15094 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
15095 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
15096 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
15097 - Fix an edge case where TestingTorNetwork is set but the authorities
15098 and relays all have an uptime of zero, where the private Tor network
15099 could briefly lack support for hidden services. Fixes bug 3886;
15100 bugfix on 0.2.2.18-alpha.
15101 - Correct the manpage's descriptions for the default values of
15102 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
15104 - Fix the documentation for the --hush and --quiet command line
15105 options, which changed their behavior back in 0.2.3.3-alpha.
15106 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
15110 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
15111 more information to it, so that we can track it down in case it
15112 returns again. Mitigates bug 5235.
15113 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
15114 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
15115 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
15116 - Warn the user when HTTPProxy, but no other proxy type, is
15117 configured. This can cause surprising behavior: it doesn't send
15118 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
15119 directory traffic only. Resolves ticket 4663.
15120 - Issue a notice if a guard completes less than 40% of your circuits.
15121 Threshold is configurable by torrc option PathBiasNoticeRate and
15122 consensus parameter pb_noticepct. There is additional, off-by-
15123 default code to disable guards which fail too many circuits.
15124 Addresses ticket 5458.
15125 - Update to the June 6 2012 Maxmind GeoLite Country database.
15127 o Code simplifications and refactoring:
15128 - Remove validate_pluggable_transports_config(): its warning
15129 message is now handled by connection_or_connect().
15132 Changes in version 0.2.2.37 - 2012-06-06
15133 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
15134 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
15138 - Work around a bug in OpenSSL that broke renegotiation with TLS
15139 1.1 and TLS 1.2. Without this workaround, all attempts to speak
15140 the v2 Tor connection protocol when both sides were using OpenSSL
15141 1.0.1 would fail. Resolves ticket 6033.
15142 - When waiting for a client to renegotiate, don't allow it to add
15143 any bytes to the input buffer. This fixes a potential DoS issue.
15144 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
15145 - Fix an edge case where if we fetch or publish a hidden service
15146 descriptor, we might build a 4-hop circuit and then use that circuit
15147 for exiting afterwards -- even if the new last hop doesn't obey our
15148 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
15151 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
15152 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
15155 - Tell GCC and Clang to check for any errors in format strings passed
15156 to the tor_v*(print|scan)f functions.
15159 Changes in version 0.2.3.16-alpha - 2012-06-05
15160 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
15161 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
15162 currently). It also fixes a variety of smaller bugs and other cleanups
15163 that get us closer to a release candidate.
15165 o Major bugfixes (general):
15166 - Work around a bug in OpenSSL that broke renegotiation with TLS
15167 1.1 and TLS 1.2. Without this workaround, all attempts to speak
15168 the v2 Tor connection protocol when both sides were using OpenSSL
15169 1.0.1 would fail. Resolves ticket 6033.
15170 - When waiting for a client to renegotiate, don't allow it to add
15171 any bytes to the input buffer. This fixes a potential DoS issue.
15172 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
15173 - Pass correct OR address to managed proxies (like obfsproxy),
15174 even when ORListenAddress is used. Fixes bug 4865; bugfix on
15176 - The advertised platform of a router now includes only its operating
15177 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
15178 service pack level (for Windows) or its CPU architecture (for Unix).
15179 We also no longer include the "git-XYZ" tag in the version. Resolves
15182 o Major bugfixes (clients):
15183 - If we are unable to find any exit that supports our predicted ports,
15184 stop calling them predicted, so that we don't loop and build
15185 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
15186 which introduced predicted ports.
15187 - Fix an edge case where if we fetch or publish a hidden service
15188 descriptor, we might build a 4-hop circuit and then use that circuit
15189 for exiting afterwards -- even if the new last hop doesn't obey our
15190 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
15191 - Check at each new consensus whether our entry guards were picked
15192 long enough ago that we should rotate them. Previously, we only
15193 did this check at startup, which could lead to us holding a guard
15194 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
15195 - When fetching a bridge descriptor from a bridge authority,
15196 always do so anonymously, whether we have been able to open
15197 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
15198 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
15199 but we'll need to wait for bug 6010 before it's actually usable.
15201 o Major bugfixes (directory authorities):
15202 - When computing weight parameters, behave more robustly in the
15203 presence of a bad bwweightscale value. Previously, the authorities
15204 would crash if they agreed on a sufficiently broken weight_scale
15205 value: now, they use a reasonable default and carry on. Partial
15206 fix for 5786; bugfix on 0.2.2.17-alpha.
15207 - Check more thoroughly to prevent a rogue authority from
15208 double-voting on any consensus directory parameter. Previously,
15209 authorities would crash in this case if the total number of
15210 votes for any parameter exceeded the number of active voters,
15211 but would let it pass otherwise. Partial fix for bug 5786; bugfix
15215 - Rate-limit log messages when asked to connect anonymously to
15216 a private address. When these hit, they tended to hit fast and
15217 often. Also, don't bother trying to connect to addresses that we
15218 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
15219 reply makes us think we have been lied to, even when the address the
15220 client tried to connect to was "localhost." Resolves ticket 2822.
15221 - Allow packagers to insert an extra string in server descriptor
15222 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
15223 Resolves the rest of ticket 2988.
15224 - Raise the threshold of server descriptors needed (75%) and exit
15225 server descriptors needed (50%) before we will declare ourselves
15226 bootstrapped. This will make clients start building circuits a
15227 little later, but makes the initially constructed circuits less
15228 skewed and less in conflict with further directory fetches. Fixes
15230 - Close any connection that sends unrecognized junk before the
15231 handshake. Solves an issue noted in bug 4369.
15232 - Improve log messages about managed transports. Resolves ticket 5070.
15233 - Tag a bridge's descriptor as "never to be sent unencrypted".
15234 This shouldn't matter, since bridges don't open non-anonymous
15235 connections to the bridge authority and don't allow unencrypted
15236 directory connections from clients, but we might as well make
15237 sure. Closes bug 5139.
15238 - Expose our view of whether we have gone dormant to the controller,
15239 via a new "GETINFO dormant" value. Torbutton and other controllers
15240 can use this to avoid doing periodic requests through Tor while
15241 it's dormant (bug 4718). Fixes bug 5954.
15242 - Tell GCC and Clang to check for any errors in format strings passed
15243 to the tor_v*(print|scan)f functions.
15244 - Update to the May 1 2012 Maxmind GeoLite Country database.
15246 o Minor bugfixes (already included in 0.2.2.36):
15247 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
15248 Fixes bug 5346; bugfix on 0.0.8pre3.
15249 - Correct parsing of certain date types in parse_http_time().
15250 Without this patch, If-Modified-Since would behave
15251 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
15252 Esteban Manchado Velázques.
15253 - Make our number-parsing functions always treat too-large values
15254 as an error, even when those values exceed the width of the
15255 underlying type. Previously, if the caller provided these
15256 functions with minima or maxima set to the extreme values of the
15257 underlying integer type, these functions would return those
15258 values on overflow rather than treating overflow as an error.
15259 Fixes part of bug 5786; bugfix on 0.0.9.
15260 - If we hit the error case where routerlist_insert() replaces an
15261 existing (old) server descriptor, make sure to remove that
15262 server descriptor from the old_routers list. Fix related to bug
15263 1776. Bugfix on 0.2.2.18-alpha.
15264 - Clarify the behavior of MaxCircuitDirtiness with hidden service
15265 circuits. Fixes issue 5259.
15267 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
15268 - Prevent a null-pointer dereference when receiving a data cell
15269 for a nonexistent stream when the circuit in question has an
15270 empty deliver window. We don't believe this is triggerable,
15271 since we don't currently allow deliver windows to become empty,
15272 but the logic is tricky enough that it's better to make the code
15273 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
15274 - Fix a memory leak when trying to launch a DNS request when the
15275 network is disabled or the nameservers are unconfigurable. Fixes
15276 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
15277 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
15278 - Don't hold a Windows file handle open for every file mapping;
15279 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
15281 - Avoid O(n^2) performance characteristics when parsing a large
15282 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
15283 - Format more doubles with %f, not %lf. Patch from grarpamp to make
15284 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
15286 - Make our replacement implementation of strtok_r() compatible with
15287 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
15288 bugfix on 0.2.2.1-alpha.
15289 - Fix a NULL-pointer dereference on a badly formed
15290 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
15291 bugfix on 0.2.2.9-alpha.
15292 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
15293 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
15294 - Defensively refactor rend_mid_rendezvous() so that protocol
15295 violations and length checks happen in the beginning. Fixes
15297 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
15298 that IPv6 stuff will compile on MSVC, and compilation issues
15299 will be easier to track down. Fixes bug 5861.
15301 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
15302 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
15303 resource exhaustion, so that clients can adjust their load to
15304 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
15305 started using END_STREAM_REASON_RESOURCELIMIT.
15306 - Don't check for whether the address we're using for outbound
15307 connections has changed until after the outbound connection has
15308 completed. On Windows, getsockname() doesn't succeed until the
15309 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
15310 - If the configuration tries to set MyFamily on a bridge, refuse to
15311 do so, and warn about the security implications. Fixes bug 4657;
15312 bugfix on 0.2.0.3-alpha.
15313 - If the client fails to set a reasonable set of ciphersuites
15314 during its v2 handshake renegotiation, allow the renegotiation to
15315 continue nevertheless (i.e. send all the required certificates).
15316 Fixes bug 4591; bugfix on 0.2.0.20-rc.
15317 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
15318 option is set to 0 (which Vidalia version 0.2.16 now does when
15319 a SAVECONF attempt fails), perform other actions that SIGHUP
15320 usually causes (like reopening the logs). Fixes bug 5095; bugfix
15322 - If we fail to write a microdescriptor to the disk cache, do not
15323 continue replacing the old microdescriptor file. Fixes bug 2954;
15324 bugfix on 0.2.2.6-alpha.
15325 - Exit nodes don't need to fetch certificates for authorities that
15326 they don't recognize; only directory authorities, bridges,
15327 and caches need to do that. Fixes part of bug 2297; bugfix on
15329 - Correctly handle checking the permissions on the parent
15330 directory of a control socket in the root directory. Bug found
15331 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
15333 - When told to add a bridge with the same digest as a preexisting
15334 bridge but a different addr:port, change the addr:port as
15335 requested. Previously we would not notice the change. Fixes half
15336 of bug 5603; fix on 0.2.2.26-beta.
15337 - End AUTHCHALLENGE error messages (in the control protocol) with
15338 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
15340 o Minor bugfixes (on 0.2.3.x):
15341 - Turn an assertion (that the number of handshakes received as a
15342 server is not < 1) into a warning. Fixes bug 4873; bugfix on
15344 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
15345 we had reversed them when the answer was cached.) Fixes bug
15346 5723; bugfix on 0.2.3.1-alpha.
15347 - Work correctly on Linux systems with accept4 support advertised in
15348 their headers, but without accept4 support in the kernel. Fix
15349 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
15350 - When told to add a bridge with the same addr:port as a preexisting
15351 bridge but a different transport, change the transport as
15352 requested. Previously we would not notice the change. Fixes half
15353 of bug 5603; fix on 0.2.3.2-alpha.
15354 - Avoid a "double-reply" warning when replying to a SOCKS request
15355 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
15356 bugfix on 0.2.3.4-alpha.
15357 - Fix a bug where a bridge authority crashes if it has seen no
15358 directory requests when it's time to write statistics to disk.
15359 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
15361 - Don't try to open non-control listeners when DisableNetwork is set.
15362 Previously, we'd open all listeners, then immediately close them.
15363 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
15364 - Don't abort the managed proxy protocol if the managed proxy
15365 sends us an unrecognized line; ignore it instead. Fixes bug
15366 5910; bugfix on 0.2.3.9-alpha.
15367 - Fix a compile warning in crypto.c when compiling with clang 3.1.
15368 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
15369 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
15370 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
15371 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
15372 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
15373 - Resolve numerous small warnings and build issues with MSVC. Resolves
15376 o Documentation fixes:
15377 - Improve the manual's documentation for the NT Service command-line
15378 options. Addresses ticket 3964.
15379 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
15380 - Document the changes to the ORPort and DirPort options, and the
15381 fact that {OR/Dir}ListenAddress is now unnecessary (and
15382 therefore deprecated). Resolves ticket 5597.
15385 - Remove the torrc.bridge file: we don't use it for anything, and
15386 it had become badly desynchronized from torrc.sample. Resolves
15390 Changes in version 0.2.2.36 - 2012-05-24
15391 Tor 0.2.2.36 updates the addresses for two of the eight directory
15392 authorities, fixes some potential anonymity and security issues,
15393 and fixes several crash bugs.
15395 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
15396 known flaws, and nobody should be using them. You should upgrade. If
15397 you're using a Linux or BSD and its packages are obsolete, stop using
15398 those packages and upgrade anyway.
15400 o Directory authority changes:
15401 - Change IP address for maatuska (v3 directory authority).
15402 - Change IP address for ides (v3 directory authority), and rename
15406 - When building or running with any version of OpenSSL earlier
15407 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
15408 versions have a bug (CVE-2011-4576) in which their block cipher
15409 padding includes uninitialized data, potentially leaking sensitive
15410 information to any peer with whom they make a SSLv3 connection. Tor
15411 does not use SSL v3 by default, but a hostile client or server
15412 could force an SSLv3 connection in order to gain information that
15413 they shouldn't have been able to get. The best solution here is to
15414 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
15415 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
15416 to make sure that the bug can't happen.
15417 - Never use a bridge or a controller-supplied node as an exit, even
15418 if its exit policy allows it. Found by wanoskarnet. Fixes bug
15419 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
15420 and 0.2.0.3-alpha (for bridge-purpose descriptors).
15421 - Only build circuits if we have a sufficient threshold of the total
15422 descriptors that are marked in the consensus with the "Exit"
15423 flag. This mitigates an attack proposed by wanoskarnet, in which
15424 all of a client's bridges collude to restrict the exit nodes that
15425 the client knows about. Fixes bug 5343.
15426 - Provide controllers with a safer way to implement the cookie
15427 authentication mechanism. With the old method, if another locally
15428 running program could convince a controller that it was the Tor
15429 process, then that program could trick the controller into telling
15430 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
15431 authentication method uses a challenge-response approach to prevent
15432 this attack. Fixes bug 5185; implements proposal 193.
15435 - Avoid logging uninitialized data when unable to decode a hidden
15436 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
15437 - Avoid a client-side assertion failure when receiving an INTRODUCE2
15438 cell on a general purpose circuit. Fixes bug 5644; bugfix on
15440 - Fix builds when the path to sed, openssl, or sha1sum contains
15441 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
15443 - Correct our replacements for the timeradd() and timersub() functions
15444 on platforms that lack them (for example, Windows). The timersub()
15445 function is used when expiring circuits, while timeradd() is
15446 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
15447 bugfix on 0.2.2.24-alpha.
15448 - Fix the SOCKET_OK test that we use to tell when socket
15449 creation fails so that it works on Win64. Fixes part of bug 4533;
15450 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
15453 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
15454 Fixes bug 5346; bugfix on 0.0.8pre3.
15455 - Make our number-parsing functions always treat too-large values
15456 as an error, even when those values exceed the width of the
15457 underlying type. Previously, if the caller provided these
15458 functions with minima or maxima set to the extreme values of the
15459 underlying integer type, these functions would return those
15460 values on overflow rather than treating overflow as an error.
15461 Fixes part of bug 5786; bugfix on 0.0.9.
15462 - Older Linux kernels erroneously respond to strange nmap behavior
15463 by having accept() return successfully with a zero-length
15464 socket. When this happens, just close the connection. Previously,
15465 we would try harder to learn the remote address: but there was
15466 no such remote address to learn, and our method for trying to
15467 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
15468 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
15469 - Correct parsing of certain date types in parse_http_time().
15470 Without this patch, If-Modified-Since would behave
15471 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
15472 Esteban Manchado Velázques.
15473 - Change the BridgePassword feature (part of the "bridge community"
15474 design, which is not yet implemented) to use a time-independent
15475 comparison. The old behavior might have allowed an adversary
15476 to use timing to guess the BridgePassword value. Fixes bug 5543;
15477 bugfix on 0.2.0.14-alpha.
15478 - Detect and reject certain misformed escape sequences in
15479 configuration values. Previously, these values would cause us
15480 to crash if received in a torrc file or over an authenticated
15481 control port. Bug found by Esteban Manchado Velázquez, and
15482 independently by Robert Connolly from Matta Consulting who further
15483 noted that it allows a post-authentication heap overflow. Patch
15484 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
15485 bugfix on 0.2.0.16-alpha.
15486 - Fix a compile warning when using the --enable-openbsd-malloc
15487 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
15488 - During configure, detect when we're building with clang version
15489 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
15490 CFLAGS. clang doesn't support them yet.
15491 - When sending an HTTP/1.1 proxy request, include a Host header.
15492 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
15493 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
15494 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
15495 - If we hit the error case where routerlist_insert() replaces an
15496 existing (old) server descriptor, make sure to remove that
15497 server descriptor from the old_routers list. Fix related to bug
15498 1776. Bugfix on 0.2.2.18-alpha.
15500 o Minor bugfixes (documentation and log messages):
15501 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
15502 Fixes bug 4856; bugfix on Tor 0.0.6.
15503 - Update "ClientOnly" man page entry to explain that there isn't
15504 really any point to messing with it. Resolves ticket 5005.
15505 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
15506 directory authority option (introduced in Tor 0.2.2.34).
15507 - Downgrade the "We're missing a certificate" message from notice
15508 to info: people kept mistaking it for a real problem, whereas it
15509 is seldom the problem even when we are failing to bootstrap. Fixes
15510 bug 5067; bugfix on 0.2.0.10-alpha.
15511 - Correctly spell "connect" in a log message on failure to create a
15512 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
15513 - Clarify the behavior of MaxCircuitDirtiness with hidden service
15514 circuits. Fixes issue 5259.
15517 - Directory authorities now reject versions of Tor older than
15518 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
15519 inclusive. These versions accounted for only a small fraction of
15520 the Tor network, and have numerous known security issues. Resolves
15522 - Update to the May 1 2012 Maxmind GeoLite Country database.
15525 - When sending or relaying a RELAY_EARLY cell, we used to convert
15526 it to a RELAY cell if the connection was using the v1 link
15527 protocol. This was a workaround for older versions of Tor, which
15528 didn't handle RELAY_EARLY cells properly. Now that all supported
15529 versions can handle RELAY_EARLY cells, and now that we're enforcing
15530 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
15531 remove this workaround. Addresses bug 4786.
15534 Changes in version 0.2.3.15-alpha - 2012-04-30
15535 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
15536 the development branch build on Windows again.
15538 o Minor bugfixes (on 0.2.2.x and earlier):
15539 - Make sure that there are no unhandled pending TLS errors before
15540 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
15541 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
15542 Bugfix on 0.1.0.5-rc; fixes bug 4528.
15543 - Fix an assert that directory authorities could trigger on sighup
15544 during some configuration state transitions. We now don't treat
15545 it as a fatal error when the new descriptor we just generated in
15546 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
15547 - After we pick a directory mirror, we would refuse to use it if
15548 it's in our ExcludeExitNodes list, resulting in mysterious failures
15549 to bootstrap for people who just wanted to avoid exiting from
15550 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
15551 - When building with --enable-static-tor on OpenBSD, do not
15552 erroneously attempt to link -lrt. Fixes bug 5103.
15554 o Minor bugfixes (on 0.2.3.x):
15555 - When Tor is built with kernel headers from a recent (last few
15556 years) Linux kernel, do not fail to run on older (pre-2.6.28
15557 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
15558 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
15559 and 0.2.3.12-alpha.
15560 - Fix compilation with miniupnpc version 1.6; patch from
15561 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
15562 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
15563 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
15564 - Fix compilation on platforms without unistd.h, or where environ
15565 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
15568 - Directory authorities are now a little more lenient at accepting
15569 older router descriptors, or newer router descriptors that don't
15570 make big changes. This should help ameliorate past and future
15571 issues where routers think they have uploaded valid descriptors,
15572 but the authorities don't think so. Fix for ticket 2479.
15573 - Make the code that clients use to detect an address change be
15574 IPv6-aware, so that it won't fill clients' logs with error
15575 messages when trying to get the IPv4 address of an IPv6
15576 connection. Implements ticket 5537.
15578 o Removed features:
15579 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
15580 authorities needed to use it for a while to keep the network working
15581 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
15582 that was six months ago. As of now, it should no longer be needed
15586 Changes in version 0.2.3.14-alpha - 2012-04-23
15587 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
15588 candidate. It also dramatically speeds up AES: fast relays should
15589 consider switching to the newer OpenSSL library.
15591 o Directory authority changes:
15592 - Change IP address for ides (v3 directory authority), and rename
15596 - Avoid logging uninitialized data when unable to decode a hidden
15597 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
15598 - Avoid a client-side assertion failure when receiving an INTRODUCE2
15599 cell on a general purpose circuit. Fixes bug 5644; bugfix on
15601 - If authorities are unable to get a v2 consensus document from other
15602 directory authorities, they no longer fall back to fetching
15603 them from regular directory caches. Fixes bug 5635; bugfix on
15604 0.2.2.26-beta, where routers stopped downloading v2 consensus
15605 documents entirely.
15606 - When we start a Tor client with a normal consensus already cached,
15607 be willing to download a microdescriptor consensus. Fixes bug 4011;
15608 fix on 0.2.3.1-alpha.
15610 o Major features (performance):
15611 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
15612 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
15613 vectorized AES implementations as appropriate. These can be much,
15614 much faster than other AES implementations.
15616 o Minor bugfixes (0.2.2.x and earlier):
15617 - Don't launch more than 10 service-side introduction-point circuits
15618 for a hidden service in five minutes. Previously, we would consider
15619 launching more introduction-point circuits if at least one second
15620 had passed without any introduction-point circuits failing. Fixes
15621 bug 4607; bugfix on 0.0.7pre1.
15622 - Change the BridgePassword feature (part of the "bridge community"
15623 design, which is not yet implemented) to use a time-independent
15624 comparison. The old behavior might have allowed an adversary
15625 to use timing to guess the BridgePassword value. Fixes bug 5543;
15626 bugfix on 0.2.0.14-alpha.
15627 - Enforce correct return behavior of tor_vsscanf() when the '%%'
15628 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
15629 - When sending an HTTP/1.1 proxy request, include a Host header.
15630 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
15631 - Don't log that we have "decided to publish new relay descriptor"
15632 unless we are actually publishing a descriptor. Fixes bug 3942;
15633 bugfix on 0.2.2.28-beta.
15635 o Minor bugfixes (0.2.3.x):
15636 - Fix a bug where a bridge authority crashes (on a failed assert)
15637 if it has seen no directory requests when it's time to write
15638 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
15639 - Fix bug stomping on ORPort option NoListen and ignoring option
15640 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
15641 - In the testsuite, provide a large enough buffer in the tor_sscanf
15642 unit test. Otherwise we'd overrun that buffer and crash during
15643 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
15645 - Make sure we create the keys directory if it doesn't exist and we're
15646 about to store the dynamic Diffie-Hellman parameters. Fixes bug
15647 5572; bugfix on 0.2.3.13-alpha.
15648 - Fix a small memory leak when trying to decode incorrect base16
15649 authenticator during SAFECOOKIE authentication. Found by
15650 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
15653 - Add more information to a log statement that might help track down
15654 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
15655 non-IP address" messages (or any Bug messages, for that matter!),
15656 please let us know about it.
15657 - Relays now understand an IPv6 address when they get one from a
15658 directory server. Resolves ticket 4875.
15659 - Resolve IPv6 addresses in bridge and entry statistics to country
15660 code "??" which means we at least count them. Resolves ticket 5053;
15661 improves on 0.2.3.9-alpha.
15662 - Update to the April 3 2012 Maxmind GeoLite Country database.
15663 - Begin a doc/state-contents.txt file to explain the contents of
15664 the Tor state file. Fixes bug 2987.
15666 o Default torrc changes:
15667 - Stop listing "socksport 9050" in torrc.sample. We open a socks
15668 port on 9050 by default anyway, so this should not change anything
15670 - Stop mentioning the deprecated *ListenAddress options in
15671 torrc.sample. Fixes bug 5438.
15672 - Document unit of bandwidth related options in sample torrc.
15675 o Removed features:
15676 - The "torify" script no longer supports the "tsocks" socksifier
15677 tool, since tsocks doesn't support DNS and UDP right for Tor.
15678 Everyone should be using torsocks instead. Fixes bugs 3530 and
15679 5180. Based on a patch by "ugh".
15681 o Code refactoring:
15682 - Change the symmetric cipher interface so that creating and
15683 initializing a stream cipher are no longer separate functions.
15684 - Remove all internal support for unpadded RSA. We never used it, and
15685 it would be a bad idea to start.
15688 Changes in version 0.2.3.13-alpha - 2012-03-26
15689 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
15690 in managed pluggable transports, as well as providing other cleanups
15691 that get us closer to a release candidate.
15693 o Directory authority changes:
15694 - Change IP address for maatuska (v3 directory authority).
15697 - Provide controllers with a safer way to implement the cookie
15698 authentication mechanism. With the old method, if another locally
15699 running program could convince a controller that it was the Tor
15700 process, then that program could trick the controller into telling
15701 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
15702 authentication method uses a challenge-response approach to prevent
15703 this attack. Fixes bug 5185, implements proposal 193.
15704 - Never use a bridge or a controller-supplied node as an exit, even
15705 if its exit policy allows it. Found by wanoskarnet. Fixes bug
15706 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
15707 and 0.2.0.3-alpha (for bridge-purpose descriptors).
15708 - Only build circuits if we have a sufficient threshold of the total
15709 descriptors that are marked in the consensus with the "Exit"
15710 flag. This mitigates an attack proposed by wanoskarnet, in which
15711 all of a client's bridges collude to restrict the exit nodes that
15712 the client knows about. Fixes bug 5343.
15714 o Major bugfixes (on Tor 0.2.3.x):
15715 - Avoid an assert when managed proxies like obfsproxy are configured,
15716 and we receive HUP signals or setconf attempts too rapidly. This
15717 situation happens most commonly when Vidalia tries to attach to
15718 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
15719 bugfix on 0.2.3.6-alpha.
15720 - Fix a relay-side pluggable transports bug where managed proxies were
15721 unreachable from the Internet, because Tor asked them to bind on
15722 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
15723 - Stop discarding command-line arguments when TestingTorNetwork
15724 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
15725 0.2.3.9-alpha, where task 4552 added support for two layers of
15727 - Resume allowing the unit tests to run in gdb. This was accidentally
15728 made impossible when the DisableDebuggerAttachment option was
15729 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
15730 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
15731 0.2.3.11-alpha. Reported by Anthony G. Basile.
15733 o Minor bugfixes (on 0.2.2.x and earlier):
15734 - Ensure we don't cannibalize circuits that are longer than three hops
15735 already, so we don't end up making circuits with 5 or more
15736 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
15737 0.1.0.1-rc which introduced cannibalization.
15738 - Detect and reject certain misformed escape sequences in
15739 configuration values. Previously, these values would cause us
15740 to crash if received in a torrc file or over an authenticated
15741 control port. Bug found by Esteban Manchado Velázquez, and
15742 independently by Robert Connolly from Matta Consulting who further
15743 noted that it allows a post-authentication heap overflow. Patch
15744 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
15745 bugfix on 0.2.0.16-alpha.
15746 - Fix a compile warning when using the --enable-openbsd-malloc
15747 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
15748 - Directory caches no longer refuse to clean out descriptors because
15749 of missing v2 networkstatus documents, unless they're configured
15750 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
15751 0.2.2.26-beta. Patch by Daniel Bryg.
15752 - Update to the latest version of the tinytest unit testing framework.
15753 This includes a couple of bugfixes that can be relevant for
15754 running forked unit tests on Windows, and removes all reserved
15757 o Minor bugfixes (on 0.2.3.x):
15758 - On a failed pipe() call, don't leak file descriptors. Fixes bug
15759 4296; bugfix on 0.2.3.1-alpha.
15760 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
15761 until after we have received a CERTS cell. Fixes bug 4361; bugfix
15762 on 0.2.3.6-alpha. Patch by "frosty".
15763 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
15764 option, so that the IP stack doesn't decide to use it for IPv4
15765 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
15766 - Ensure that variables set in Tor's environment cannot override
15767 environment variables that Tor passes to a managed
15768 pluggable-transport proxy. Previously, Tor would pass every
15769 variable in its environment to managed proxies along with the new
15770 ones, in such a way that on many operating systems, the inherited
15771 environment variables would override those which Tor tried to
15772 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
15773 bugfix on 0.2.3.9-alpha for Windows.
15776 - A wide variety of new unit tests by Esteban Manchado Velázquez.
15777 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
15778 - Update to the March 6 2012 Maxmind GeoLite Country database.
15781 Changes in version 0.2.3.12-alpha - 2012-02-13
15782 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
15783 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
15784 when Tor is configured to use a pluggable transport like obfsproxy.
15787 - Fix builds when the path to sed, openssl, or sha1sum contains
15788 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
15790 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
15791 connections. This change should allow busy exit relays to stop
15792 running out of available sockets as quickly. Fixes bug 4950;
15793 bugfix on 0.2.2.26-beta.
15794 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
15795 would ask the bridge for microdescriptors, which are only supported
15796 in 0.2.3.x, and then fail to bootstrap when it didn't get the
15797 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
15798 - Properly set up obfsproxy's environment when in managed mode. The
15799 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
15800 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
15801 5076 and 5082; bugfix on 0.2.3.6-alpha.
15804 - Use the dead_strip option when building Tor on OS X. This reduces
15805 binary size by almost 19% when linking openssl and libevent
15806 statically, which we do for Tor Browser Bundle.
15807 - Fix broken URLs in the sample torrc file, and tell readers about
15808 the OutboundBindAddress, ExitPolicyRejectPrivate, and
15809 PublishServerDescriptor options. Addresses bug 4652.
15810 - Update to the February 7 2012 Maxmind GeoLite Country database.
15813 - Downgrade the "We're missing a certificate" message from notice
15814 to info: people kept mistaking it for a real problem, whereas it
15815 is seldom the problem even when we are failing to bootstrap. Fixes
15816 bug 5067; bugfix on 0.2.0.10-alpha.
15817 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
15818 managed pluggable transport server proxy's environment.
15819 Previously, we would put it there, even though Tor doesn't
15820 implement an 'extended server port' yet, and even though Tor
15821 almost certainly isn't listening at that address. For now, we set
15822 it to an empty string to avoid crashing older obfsproxies. Bugfix
15824 - Log the heartbeat message every HeartbeatPeriod seconds, not every
15825 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
15826 0.2.3.1-alpha. Bug reported by Scott Bennett.
15827 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
15828 bugfix on 0.2.3.11-alpha.
15829 - Update "ClientOnly" man page entry to explain that there isn't
15830 really any point to messing with it. Resolves ticket 5005.
15831 - Use the correct CVE number for CVE-2011-4576 in our comments and
15832 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
15835 o Code simplifications and refactoring:
15836 - Use the _WIN32 macro throughout our code to detect Windows.
15837 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
15841 Changes in version 0.2.3.11-alpha - 2012-01-22
15842 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
15843 the last step of the plan to limit maximum circuit length, includes
15844 a wide variety of hidden service performance and correctness fixes,
15845 works around an OpenSSL security flaw if your distro is too stubborn
15846 to upgrade, and fixes a bunch of smaller issues.
15849 - Now that Tor 0.2.0.x is completely deprecated, enable the final
15850 part of "Proposal 110: Avoiding infinite length circuits" by
15851 refusing all circuit-extend requests that do not use a relay_early
15852 cell. This change helps Tor resist a class of denial-of-service
15853 attacks by limiting the maximum circuit length.
15854 - Adjust the number of introduction points that a hidden service
15855 will try to maintain based on how long its introduction points
15856 remain in use and how many introductions they handle. Fixes
15858 - Try to use system facilities for enumerating local interface
15859 addresses, before falling back to our old approach (which was
15860 binding a UDP socket, and calling getsockname() on it). That
15861 approach was scaring OS X users whose draconian firewall
15862 software warned about binding to UDP sockets, regardless of
15863 whether packets were sent. Now we try to use getifaddrs(),
15864 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
15865 system supports. Resolves ticket 1827.
15867 o Major security workaround:
15868 - When building or running with any version of OpenSSL earlier
15869 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
15870 versions have a bug (CVE-2011-4576) in which their block cipher
15871 padding includes uninitialized data, potentially leaking sensitive
15872 information to any peer with whom they make a SSLv3 connection. Tor
15873 does not use SSL v3 by default, but a hostile client or server
15874 could force an SSLv3 connection in order to gain information that
15875 they shouldn't have been able to get. The best solution here is to
15876 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
15877 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
15878 to make sure that the bug can't happen.
15881 - Fix the SOCKET_OK test that we use to tell when socket
15882 creation fails so that it works on Win64. Fixes part of bug 4533;
15883 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
15884 - Correct our replacements for the timeradd() and timersub() functions
15885 on platforms that lack them (for example, Windows). The timersub()
15886 function is used when expiring circuits, while timeradd() is
15887 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
15888 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
15889 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
15890 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
15891 bug at runtime, not compile time, because some distributions hack
15892 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
15893 on 0.2.3.9-alpha. Found by Pascal.
15895 o Minor features (controller):
15896 - Use absolute path names when reporting the torrc filename in the
15897 control protocol, so a controller can more easily find the torrc
15898 file. Resolves bug 1101.
15899 - Extend the control protocol to report flags that control a circuit's
15900 path selection in CIRC events and in replies to 'GETINFO
15901 circuit-status'. Implements part of ticket 2411.
15902 - Extend the control protocol to report the hidden service address
15903 and current state of a hidden-service-related circuit in CIRC
15904 events and in replies to 'GETINFO circuit-status'. Implements part
15906 - When reporting the path to the cookie file to the controller,
15907 give an absolute path. Resolves ticket 4881.
15908 - Allow controllers to request an event notification whenever a
15909 circuit is cannibalized or its purpose is changed. Implements
15910 part of ticket 3457.
15911 - Include the creation time of a circuit in CIRC and CIRC2
15912 control-port events and the list produced by the 'GETINFO
15913 circuit-status' control-port command.
15915 o Minor features (directory authorities):
15916 - Directory authorities now reject versions of Tor older than
15917 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
15918 inclusive. These versions accounted for only a small fraction of
15919 the Tor network, and have numerous known security issues. Resolves
15921 - Authority operators can now vote for all relays in a given
15922 set of countries to be BadDir/BadExit/Invalid/Rejected.
15923 - Provide two consensus parameters (FastFlagMinThreshold and
15924 FastFlagMaxThreshold) to control the range of allowable bandwidths
15925 for the Fast directory flag. These allow authorities to run
15926 experiments on appropriate requirements for being a "Fast" node.
15927 The AuthDirFastGuarantee config value still applies. Implements
15929 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
15930 directory authority option (introduced in Tor 0.2.2.34).
15932 o Minor features (other):
15933 - Don't disable the DirPort when we cannot exceed our AccountingMax
15934 limit during this interval because the effective bandwidthrate is
15935 low enough. This is useful in a situation where AccountMax is only
15936 used as an additional safeguard or to provide statistics.
15937 - Prepend an informative header to generated dynamic_dh_params files.
15938 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
15939 EntryNodes will have no effect. Resolves issue 2571.
15940 - Log more useful messages when we fail to disable debugger
15942 - Log which authority we're missing votes from when we go to fetch
15943 them from the other auths.
15944 - Log (at debug level) whenever a circuit's purpose is changed.
15945 - Add missing documentation for the MaxClientCircuitsPending,
15946 UseMicrodescriptors, UserspaceIOCPBuffers, and
15947 _UseFilteringSSLBufferevents options, all introduced during
15948 the 0.2.3.x series.
15949 - Update to the January 3 2012 Maxmind GeoLite Country database.
15951 o Minor bugfixes (hidden services):
15952 - Don't close hidden service client circuits which have almost
15953 finished connecting to their destination when they reach
15954 the normal circuit-build timeout. Previously, we would close
15955 introduction circuits which are waiting for an acknowledgement
15956 from the introduction point, and rendezvous circuits which have
15957 been specified in an INTRODUCE1 cell sent to a hidden service,
15958 after the normal CBT. Now, we mark them as 'timed out', and launch
15959 another rendezvous attempt in parallel. This behavior change can
15960 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
15961 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
15962 - Don't close hidden-service-side rendezvous circuits when they
15963 reach the normal circuit-build timeout. This behavior change can
15964 be disabled using the new
15965 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
15966 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
15967 - Make sure we never mark the wrong rendezvous circuit as having
15968 had its introduction cell acknowledged by the introduction-point
15969 relay. Previously, when we received an INTRODUCE_ACK cell on a
15970 client-side hidden-service introduction circuit, we might have
15971 marked a rendezvous circuit other than the one we specified in
15972 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
15973 a warning message and interfered with the hidden service
15974 connection-establishment process. Fixes bug 4759; bugfix on
15975 0.2.3.3-alpha, when we added the stream-isolation feature which
15976 might cause Tor to open multiple rendezvous circuits for the same
15978 - Don't trigger an assertion failure when we mark a new client-side
15979 hidden-service introduction circuit for close during the process
15980 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
15983 o Minor bugfixes (log messages):
15984 - Correctly spell "connect" in a log message on failure to create a
15985 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
15987 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
15988 Fixes bug 4856; bugfix on Tor 0.0.6.
15989 - Fix the log message describing how we work around discovering
15990 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
15991 4837; bugfix on 0.2.2.9-alpha.
15992 - When logging about a disallowed .exit name, do not also call it
15993 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
15995 o Minor bugfixes (build fixes):
15996 - During configure, detect when we're building with clang version
15997 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
15998 CFLAGS. clang doesn't support them yet.
15999 - During configure, search for library containing cos function as
16000 libm lives in libcore on some platforms (BeOS/Haiku). Linking
16001 against libm was hard-coded before. Fixes the first part of bug
16002 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
16004 - Detect attempts to build Tor on (as yet hypothetical) versions
16005 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
16006 fix for bug 4533. Bugfix on 0.2.2.28-beta.
16007 - Preprocessor directives should not be put inside the arguments
16008 of a macro. This would break compilation with GCC releases prior
16009 to version 3.3. We would never recommend such an old GCC version,
16010 but it is apparently required for binary compatibility on some
16011 platforms (namely, certain builds of Haiku). Fixes the other part
16012 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
16015 o Minor bugfixes (other):
16016 - Older Linux kernels erroneously respond to strange nmap behavior
16017 by having accept() return successfully with a zero-length
16018 socket. When this happens, just close the connection. Previously,
16019 we would try harder to learn the remote address: but there was
16020 no such remote address to learn, and our method for trying to
16021 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
16022 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
16023 - Fix null-pointer access that could occur if TLS allocation failed.
16024 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
16025 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
16026 accidentally been reverted.
16027 - Fix our implementation of crypto_random_hostname() so it can't
16028 overflow on ridiculously large inputs. (No Tor version has ever
16029 provided this kind of bad inputs, but let's be correct in depth.)
16030 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
16031 - Find more places in the code that should have been testing for
16032 invalid sockets using the SOCKET_OK macro. Required for a fix
16033 for bug 4533. Bugfix on 0.2.2.28-beta.
16034 - Fix an assertion failure when, while running with bufferevents, a
16035 connection finishes connecting after it is marked for close, but
16036 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
16037 - test_util_spawn_background_ok() hardcoded the expected value
16038 for ENOENT to 2. This isn't portable as error numbers are
16039 platform specific, and particularly the hurd has ENOENT at
16040 0x40000002. Construct expected string at runtime, using the correct
16041 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
16042 - Reject attempts to disable DisableDebuggerAttachment while Tor is
16043 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
16044 - Use an appropriate-width type for sockets in tor-fw-helper on
16045 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
16048 - When sending or relaying a RELAY_EARLY cell, we used to convert
16049 it to a RELAY cell if the connection was using the v1 link
16050 protocol. This was a workaround for older versions of Tor, which
16051 didn't handle RELAY_EARLY cells properly. Now that all supported
16052 versions can handle RELAY_EARLY cells, and now that we're enforcing
16053 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
16054 remove this workaround. Addresses bug 4786.
16056 o Code simplifications and refactoring:
16057 - Use OpenSSL's built-in SSL_state_string_long() instead of our
16058 own homebrewed ssl_state_to_string() replacement. Patch from
16059 Emile Snyder. Fixes bug 4653.
16060 - Use macros to indicate OpenSSL versions, so we don't need to worry
16061 about accidental hexadecimal bit shifts.
16062 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
16064 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
16065 - Use the smartlist_add_asprintf() alias more consistently.
16066 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
16067 invalid value, rather than just -1.
16068 - Rename a handful of old identifiers, mostly related to crypto
16069 structures and crypto functions. By convention, our "create an
16070 object" functions are called "type_new()", our "free an object"
16071 functions are called "type_free()", and our types indicate that
16072 they are types only with a final "_t". But a handful of older
16073 types and functions broke these rules, with function names like
16074 "type_create" or "subsystem_op_type", or with type names like
16078 Changes in version 0.2.3.10-alpha - 2011-12-16
16079 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
16080 Tor's buffers code. Absolutely everybody should upgrade.
16082 The bug relied on an incorrect calculation when making data continuous
16083 in one of our IO buffers, if the first chunk of the buffer was
16084 misaligned by just the wrong amount. The miscalculation would allow an
16085 attacker to overflow a piece of heap-allocated memory. To mount this
16086 attack, the attacker would need to either open a SOCKS connection to
16087 Tor's SocksPort (usually restricted to localhost), or target a Tor
16088 instance configured to make its connections through a SOCKS proxy
16089 (which Tor does not do by default).
16091 Good security practice requires that all heap-overflow bugs should be
16092 presumed to be exploitable until proven otherwise, so we are treating
16093 this as a potential code execution attack. Please upgrade immediately!
16094 This bug does not affect bufferevents-based builds of Tor. Special
16095 thanks to "Vektor" for reporting this issue to us!
16097 This release also contains a few minor bugfixes for issues discovered
16101 - Fix a heap overflow bug that could occur when trying to pull
16102 data into the first chunk of a buffer, when that chunk had
16103 already had some data drained from it. Fixes CVE-2011-2778;
16104 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
16107 - If we can't attach streams to a rendezvous circuit when we
16108 finish connecting to a hidden service, clear the rendezvous
16109 circuit's stream-isolation state and try to attach streams
16110 again. Previously, we cleared rendezvous circuits' isolation
16111 state either too early (if they were freshly built) or not at all
16112 (if they had been built earlier and were cannibalized). Bugfix on
16113 0.2.3.3-alpha; fixes bug 4655.
16114 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
16115 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
16116 - Fix an assertion failure when a relay with accounting enabled
16117 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
16120 - Update to the December 6 2011 Maxmind GeoLite Country database.
16123 Changes in version 0.2.2.35 - 2011-12-16
16124 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
16125 buffers code. Absolutely everybody should upgrade.
16127 The bug relied on an incorrect calculation when making data continuous
16128 in one of our IO buffers, if the first chunk of the buffer was
16129 misaligned by just the wrong amount. The miscalculation would allow an
16130 attacker to overflow a piece of heap-allocated memory. To mount this
16131 attack, the attacker would need to either open a SOCKS connection to
16132 Tor's SocksPort (usually restricted to localhost), or target a Tor
16133 instance configured to make its connections through a SOCKS proxy
16134 (which Tor does not do by default).
16136 Good security practice requires that all heap-overflow bugs should be
16137 presumed to be exploitable until proven otherwise, so we are treating
16138 this as a potential code execution attack. Please upgrade immediately!
16139 This bug does not affect bufferevents-based builds of Tor. Special
16140 thanks to "Vektor" for reporting this issue to us!
16142 Tor 0.2.2.35 also fixes several bugs in previous versions, including
16143 crash bugs for unusual configurations, and a long-term bug that
16144 would prevent Tor from starting on Windows machines with draconian
16147 With this release, we remind everyone that 0.2.0.x has reached its
16148 formal end-of-life. Those Tor versions have many known flaws, and
16149 nobody should be using them. You should upgrade -- ideally to the
16150 0.2.2.x series. If you're using a Linux or BSD and its packages are
16151 obsolete, stop using those packages and upgrade anyway.
16153 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
16154 longer receive support after some time in early 2012.
16157 - Fix a heap overflow bug that could occur when trying to pull
16158 data into the first chunk of a buffer, when that chunk had
16159 already had some data drained from it. Fixes CVE-2011-2778;
16160 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
16161 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
16162 that it doesn't attempt to allocate a socketpair. This could cause
16163 some problems on Windows systems with overzealous firewalls. Fix for
16164 bug 4457; workaround for Libevent versions 2.0.1-alpha through
16166 - If we mark an OR connection for close based on a cell we process,
16167 don't process any further cells on it. We already avoid further
16168 reads on marked-for-close connections, but now we also discard the
16169 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
16170 which was the first version where we might mark a connection for
16171 close based on processing a cell on it.
16172 - Correctly sanity-check that we don't underflow on a memory
16173 allocation (and then assert) for hidden service introduction
16174 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
16175 bugfix on 0.2.1.5-alpha.
16176 - Fix a memory leak when we check whether a hidden service
16177 descriptor has any usable introduction points left. Fixes bug
16178 4424. Bugfix on 0.2.2.25-alpha.
16179 - Don't crash when we're running as a relay and don't have a GeoIP
16180 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
16181 we've had in the 0.2.3.x branch already.
16182 - When running as a client, do not print a misleading (and plain
16183 wrong) log message that we're collecting "directory request"
16184 statistics: clients don't collect statistics. Also don't create a
16185 useless (because empty) stats file in the stats/ directory. Fixes
16186 bug 4353; bugfix on 0.2.2.34.
16189 - Detect failure to initialize Libevent. This fix provides better
16190 detection for future instances of bug 4457.
16191 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
16192 function. This was eating up hideously large amounts of time on some
16193 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
16194 - Resolve an integer overflow bug in smartlist_ensure_capacity().
16195 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
16197 - Don't warn about unused log_mutex in log.c when building with
16198 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
16199 0.1.0.6-rc which introduced --disable-threads.
16200 - When configuring, starting, or stopping an NT service, stop
16201 immediately after the service configuration attempt has succeeded
16202 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
16203 - When sending a NETINFO cell, include the original address
16204 received for the other side, not its canonical address. Found
16205 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
16206 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
16207 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
16208 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
16209 occurred when a client tried to fetch a descriptor for a bridge
16210 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
16211 - Backport fixes for a pair of compilation warnings on Windows.
16212 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
16213 - If we had ever tried to call tor_addr_to_str on an address of
16214 unknown type, we would have done a strdup on an uninitialized
16215 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
16216 Reported by "troll_un".
16217 - Correctly detect and handle transient lookup failures from
16218 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
16219 Reported by "troll_un".
16220 - Fix null-pointer access that could occur if TLS allocation failed.
16221 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
16222 - Use tor_socket_t type for listener argument to accept(). Fixes bug
16223 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
16226 - Add two new config options for directory authorities:
16227 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
16228 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
16229 that is always sufficient to satisfy the bandwidth requirement for
16230 the Guard flag. Now it will be easier for researchers to simulate
16231 Tor networks with different values. Resolves ticket 4484.
16232 - When Tor ignores a hidden service specified in its configuration,
16233 include the hidden service's directory in the warning message.
16234 Previously, we would only tell the user that some hidden service
16235 was ignored. Bugfix on 0.0.6; fixes bug 4426.
16236 - Update to the December 6 2011 Maxmind GeoLite Country database.
16238 o Packaging changes:
16239 - Make it easier to automate expert package builds on Windows,
16240 by removing an absolute path from makensis.exe command.
16243 Changes in version 0.2.1.32 - 2011-12-16
16244 Tor 0.2.1.32 backports important security and privacy fixes for
16245 oldstable. This release is intended only for package maintainers and
16246 others who cannot use the 0.2.2 stable series. All others should be
16247 using Tor 0.2.2.x or newer.
16249 The Tor 0.2.1.x series will reach formal end-of-life some time in
16250 early 2012; we will stop releasing patches for it then.
16252 o Major bugfixes (also included in 0.2.2.x):
16253 - Correctly sanity-check that we don't underflow on a memory
16254 allocation (and then assert) for hidden service introduction
16255 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
16256 bugfix on 0.2.1.5-alpha.
16257 - Fix a heap overflow bug that could occur when trying to pull
16258 data into the first chunk of a buffer, when that chunk had
16259 already had some data drained from it. Fixes CVE-2011-2778;
16260 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
16263 - Update to the December 6 2011 Maxmind GeoLite Country database.
16266 Changes in version 0.2.3.9-alpha - 2011-12-08
16267 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
16268 a "DisableNetwork" security feature that bundles can use to avoid
16269 touching the network until bridges are configured, moves forward on
16270 the pluggable transport design, fixes a flaw in the hidden service
16271 design that unnecessarily prevented clients with wrong clocks from
16272 reaching hidden services, and fixes a wide variety of other issues.
16275 - Clients can now connect to private bridges over IPv6. Bridges
16276 still need at least one IPv4 address in order to connect to
16277 other relays. Note that we don't yet handle the case where the
16278 user has two bridge lines for the same bridge (one IPv4, one
16279 IPv6). Implements parts of proposal 186.
16280 - New "DisableNetwork" config option to prevent Tor from launching any
16281 connections or accepting any connections except on a control port.
16282 Bundles and controllers can set this option before letting Tor talk
16283 to the rest of the network, for example to prevent any connections
16284 to a non-bridge address. Packages like Orbot can also use this
16285 option to instruct Tor to save power when the network is off.
16286 - Clients and bridges can now be configured to use a separate
16287 "transport" proxy. This approach makes the censorship arms race
16288 easier by allowing bridges to use protocol obfuscation plugins. It
16289 implements the "managed proxy" part of proposal 180 (ticket 3472).
16290 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
16291 implementation. It makes AES_CTR about 7% faster than our old one
16292 (which was about 10% faster than the one OpenSSL used to provide).
16293 Resolves ticket 4526.
16294 - Add a "tor2web mode" for clients that want to connect to hidden
16295 services non-anonymously (and possibly more quickly). As a safety
16296 measure to try to keep users from turning this on without knowing
16297 what they are doing, tor2web mode must be explicitly enabled at
16298 compile time, and a copy of Tor compiled to run in tor2web mode
16299 cannot be used as a normal Tor client. Implements feature 2553.
16300 - Add experimental support for running on Windows with IOCP and no
16301 kernel-space socket buffers. This feature is controlled by a new
16302 "UserspaceIOCPBuffers" config option (off by default), which has
16303 no effect unless Tor has been built with support for bufferevents,
16304 is running on Windows, and has enabled IOCP. This may, in the long
16305 run, help solve or mitigate bug 98.
16306 - Use a more secure consensus parameter voting algorithm. Now at
16307 least three directory authorities or a majority of them must
16308 vote on a given parameter before it will be included in the
16309 consensus. Implements proposal 178.
16312 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
16313 They used to check that the timestamp was within 30 minutes
16314 of their system clock, so they could cap the size of their
16315 replay-detection cache, but that approach unnecessarily refused
16316 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
16317 the v3 intro-point protocol (the first one which sent a timestamp
16318 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
16319 - Only use the EVP interface when AES acceleration is enabled,
16320 to avoid a 5-7% performance regression. Resolves issue 4525;
16321 bugfix on 0.2.3.8-alpha.
16323 o Privacy/anonymity features (bridge detection):
16324 - Make bridge SSL certificates a bit more stealthy by using random
16325 serial numbers, in the same fashion as OpenSSL when generating
16326 self-signed certificates. Implements ticket 4584.
16327 - Introduce a new config option "DynamicDHGroups", enabled by
16328 default, which provides each bridge with a unique prime DH modulus
16329 to be used during SSL handshakes. This option attempts to help
16330 against censors who might use the Apache DH modulus as a static
16331 identifier for bridges. Addresses ticket 4548.
16333 o Minor features (new/different config options):
16334 - New configuration option "DisableDebuggerAttachment" (on by default)
16335 to prevent basic debugging attachment attempts by other processes.
16336 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
16337 - Allow MapAddress directives to specify matches against super-domains,
16338 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
16339 Implements issue 933.
16340 - Slightly change behavior of "list" options (that is, config
16341 options that can appear more than once) when they appear both in
16342 torrc and on the command line. Previously, the command-line options
16343 would be appended to the ones from torrc. Now, the command-line
16344 options override the torrc options entirely. This new behavior
16345 allows the user to override list options (like exit policies and
16346 ports to listen on) from the command line, rather than simply
16347 appending to the list.
16348 - You can get the old (appending) command-line behavior for "list"
16349 options by prefixing the option name with a "+".
16350 - You can remove all the values for a "list" option from the command
16351 line without adding any new ones by prefixing the option name
16353 - Add experimental support for a "defaults" torrc file to be parsed
16354 before the regular torrc. Torrc options override the defaults file's
16355 options in the same way that the command line overrides the torrc.
16356 The SAVECONF controller command saves only those options which
16357 differ between the current configuration and the defaults file. HUP
16358 reloads both files. (Note: This is an experimental feature; its
16359 behavior will probably be refined in future 0.2.3.x-alpha versions
16360 to better meet packagers' needs.) Implements task 4552.
16363 - Try to make the introductory warning message that Tor prints on
16364 startup more useful for actually finding help and information.
16365 Resolves ticket 2474.
16366 - Running "make version" now displays the version of Tor that
16367 we're about to build. Idea from katmagic; resolves issue 4400.
16368 - Expire old or over-used hidden service introduction points.
16369 Required by fix for bug 3460.
16370 - Move the replay-detection cache for the RSA-encrypted parts of
16371 INTRODUCE2 cells to the introduction point data structures.
16372 Previously, we would use one replay-detection cache per hidden
16373 service. Required by fix for bug 3460.
16374 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
16375 public key replay-detection cache from 60 minutes to 5 minutes. This
16376 replay-detection cache is now used only to detect multiple
16377 INTRODUCE2 cells specifying the same rendezvous point, so we can
16378 avoid launching multiple simultaneous attempts to connect to it.
16380 o Minor bugfixes (on Tor 0.2.2.x and earlier):
16381 - Resolve an integer overflow bug in smartlist_ensure_capacity().
16382 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
16384 - Fix a minor formatting issue in one of tor-gencert's error messages.
16386 - Prevent a false positive from the check-spaces script, by disabling
16387 the "whitespace between function name and (" check for functions
16389 - Fix a log message suggesting that people contact a non-existent
16390 email address. Fixes bug 3448.
16391 - Fix null-pointer access that could occur if TLS allocation failed.
16392 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
16393 - Report a real bootstrap problem to the controller on router
16394 identity mismatch. Previously we just said "foo", which probably
16395 made a lot of sense at the time. Fixes bug 4169; bugfix on
16397 - If we had ever tried to call tor_addr_to_str() on an address of
16398 unknown type, we would have done a strdup() on an uninitialized
16399 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
16400 Reported by "troll_un".
16401 - Correctly detect and handle transient lookup failures from
16402 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
16403 Reported by "troll_un".
16404 - Use tor_socket_t type for listener argument to accept(). Fixes bug
16405 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
16406 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
16407 bug 4532; found by "troll_un".
16409 o Minor bugfixes (on Tor 0.2.3.x):
16410 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
16412 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
16413 circuit for use as a hidden service client's rendezvous point.
16414 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
16415 with help from wanoskarnet.
16416 - Restore behavior of overriding SocksPort, ORPort, and similar
16417 options from the command line. Bugfix on 0.2.3.3-alpha.
16420 - Properly handle the case where the build-tree is not the same
16421 as the source tree when generating src/common/common_sha1.i,
16422 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
16423 bugfix on 0.2.0.1-alpha.
16425 o Code simplifications, cleanups, and refactorings:
16426 - Remove the pure attribute from all functions that used it
16427 previously. In many cases we assigned it incorrectly, because the
16428 functions might assert or call impure functions, and we don't have
16429 evidence that keeping the pure attribute is worthwhile. Implements
16430 changes suggested in ticket 4421.
16431 - Remove some dead code spotted by coverity. Fixes cid 432.
16432 Bugfix on 0.2.3.1-alpha, closes bug 4637.
16435 Changes in version 0.2.3.8-alpha - 2011-11-22
16436 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
16437 socketpair-related bug that has been bothering Windows users. It adds
16438 support to serve microdescriptors to controllers, so Vidalia's network
16439 map can resume listing relays (once Vidalia implements its side),
16440 and adds better support for hardware AES acceleration. Finally, it
16441 starts the process of adjusting the bandwidth cutoff for getting the
16442 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
16443 that tiny relays harm performance more than they help network capacity.
16446 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
16447 that it doesn't attempt to allocate a socketpair. This could cause
16448 some problems on Windows systems with overzealous firewalls. Fix for
16449 bug 4457; workaround for Libevent versions 2.0.1-alpha through
16451 - Correctly sanity-check that we don't underflow on a memory
16452 allocation (and then assert) for hidden service introduction
16453 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
16454 bugfix on 0.2.1.5-alpha.
16455 - Remove the artificially low cutoff of 20KB to guarantee the Fast
16456 flag. In the past few years the average relay speed has picked
16457 up, and while the "top 7/8 of the network get the Fast flag" and
16458 "all relays with 20KB or more of capacity get the Fast flag" rules
16459 used to have the same result, now the top 7/8 of the network has
16460 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
16461 - Fix a rare assertion failure when checking whether a v0 hidden
16462 service descriptor has any usable introduction points left, and
16463 we don't have enough information to build a circuit to the first
16464 intro point named in the descriptor. The HS client code in
16465 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
16466 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
16467 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
16468 - Make bridge authorities not crash when they are asked for their own
16469 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
16470 - When running as a client, do not print a misleading (and plain
16471 wrong) log message that we're collecting "directory request"
16472 statistics: clients don't collect statistics. Also don't create a
16473 useless (because empty) stats file in the stats/ directory. Fixes
16474 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
16477 - Allow Tor controllers like Vidalia to obtain the microdescriptor
16478 for a relay by identity digest or nickname. Previously,
16479 microdescriptors were only available by their own digests, so a
16480 controller would have to ask for and parse the whole microdescriptor
16481 consensus in order to look up a single relay's microdesc. Fixes
16482 bug 3832; bugfix on 0.2.3.1-alpha.
16483 - Use OpenSSL's EVP interface for AES encryption, so that all AES
16484 operations can use hardware acceleration (if present). Resolves
16487 o Minor bugfixes (on 0.2.2.x and earlier):
16488 - Detect failure to initialize Libevent. This fix provides better
16489 detection for future instances of bug 4457.
16490 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
16491 function. This was eating up hideously large amounts of time on some
16492 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
16493 - Don't warn about unused log_mutex in log.c when building with
16494 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
16495 0.1.0.6-rc which introduced --disable-threads.
16496 - Allow manual 'authenticate' commands to the controller interface
16497 from netcat (nc) as well as telnet. We were rejecting them because
16498 they didn't come with the expected whitespace at the end of the
16499 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
16500 - Fix some (not actually triggerable) buffer size checks in usage of
16501 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
16503 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
16504 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
16505 - When configuring, starting, or stopping an NT service, stop
16506 immediately after the service configuration attempt has succeeded
16507 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
16508 - When sending a NETINFO cell, include the original address
16509 received for the other side, not its canonical address. Found
16510 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
16511 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
16512 can pick them up when the tests aren't disabled. Bugfix on
16513 0.2.2.4-alpha which introduced tinytest.
16514 - Fix a memory leak when we check whether a hidden service
16515 descriptor has any usable introduction points left. Fixes bug
16516 4424. Bugfix on 0.2.2.25-alpha.
16517 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
16518 occurred when a client tried to fetch a descriptor for a bridge
16519 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
16521 o Minor bugfixes (on 0.2.3.x):
16522 - Make util unit tests build correctly with MSVC. Bugfix on
16523 0.2.3.3-alpha. Patch by Gisle Vanem.
16524 - Successfully detect AUTH_CHALLENGE cells with no recognized
16525 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
16526 Found by frosty_un.
16527 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
16528 it should still send a NETINFO cell to allow the connection to
16529 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
16531 - Log less loudly when we get an invalid authentication certificate
16532 from a source other than a directory authority: it's not unusual
16533 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
16535 - Tolerate servers with more clock skew in their authentication
16536 certificates than previously. Fixes bug 4371; bugfix on
16538 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
16539 on 0.2.3.4-alpha and 0.2.3.6-alpha.
16542 - Add two new config options for directory authorities:
16543 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
16544 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
16545 that is always sufficient to satisfy the bandwidth requirement for
16546 the Guard flag. Now it will be easier for researchers to simulate
16547 Tor networks with different values. Resolves ticket 4484.
16548 - When Tor ignores a hidden service specified in its configuration,
16549 include the hidden service's directory in the warning message.
16550 Previously, we would only tell the user that some hidden service
16551 was ignored. Bugfix on 0.0.6; fixes bug 4426.
16552 - When we fail to initialize Libevent, retry with IOCP disabled so we
16553 don't need to turn on multi-threading support in Libevent, which in
16554 turn requires a working socketpair(). This is a workaround for bug
16555 4457, which affects Libevent versions from 2.0.1-alpha through
16557 - Detect when we try to build on a platform that doesn't define
16558 AF_UNSPEC to 0. We don't work there, so refuse to compile.
16559 - Update to the November 1 2011 Maxmind GeoLite Country database.
16561 o Packaging changes:
16562 - Make it easier to automate expert package builds on Windows,
16563 by removing an absolute path from makensis.exe command.
16565 o Code simplifications and refactoring:
16566 - Remove some redundant #include directives throughout the code.
16567 Patch from Andrea Gelmini.
16568 - Unconditionally use OpenSSL's AES implementation instead of our
16569 old built-in one. OpenSSL's AES has been better for a while, and
16570 relatively few servers should still be on any version of OpenSSL
16571 that doesn't have good optimized assembly AES.
16572 - Use the name "CERTS" consistently to refer to the new cell type;
16573 we were calling it CERT in some places and CERTS in others.
16576 - Numerous new unit tests for functions in util.c and address.c by
16578 - The long-disabled benchmark tests are now split into their own
16579 ./src/test/bench binary.
16580 - The benchmark tests can now use more accurate timers than
16581 gettimeofday() when such timers are available.
16584 Changes in version 0.2.3.7-alpha - 2011-10-30
16585 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
16586 the new v3 handshake. It also resolves yet another bridge address
16590 - If we mark an OR connection for close based on a cell we process,
16591 don't process any further cells on it. We already avoid further
16592 reads on marked-for-close connections, but now we also discard the
16593 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
16594 which was the first version where we might mark a connection for
16595 close based on processing a cell on it.
16596 - Fix a double-free bug that would occur when we received an invalid
16597 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
16598 bugfix on 0.2.3.6-alpha.
16599 - Bridges no longer include their address in NETINFO cells on outgoing
16600 OR connections, to allow them to blend in better with clients.
16601 Removes another avenue for enumerating bridges. Reported by
16602 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
16603 cells were introduced.
16606 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
16607 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
16610 Changes in version 0.2.3.6-alpha - 2011-10-26
16611 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
16612 anonymity vulnerability where an attacker can deanonymize Tor
16613 users. Everybody should upgrade.
16615 This release also features support for a new v3 connection handshake
16616 protocol, and fixes to make hidden service connections more robust.
16619 - Implement a new handshake protocol (v3) for authenticating Tors to
16620 each other over TLS. It should be more resistant to fingerprinting
16621 than previous protocols, and should require less TLS hacking for
16622 future Tor implementations. Implements proposal 176.
16623 - Allow variable-length padding cells to disguise the length of
16624 Tor's TLS records. Implements part of proposal 184.
16626 o Privacy/anonymity fixes (clients):
16627 - Clients and bridges no longer send TLS certificate chains on
16628 outgoing OR connections. Previously, each client or bridge would
16629 use the same cert chain for all outgoing OR connections until
16630 its IP address changes, which allowed any relay that the client
16631 or bridge contacted to determine which entry guards it is using.
16632 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16633 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16634 no longer considers that connection as suitable for satisfying a
16635 circuit EXTEND request. Now relays can protect clients from the
16636 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16637 - Directory authorities no longer assign the Guard flag to relays
16638 that haven't upgraded to the above "refuse EXTEND requests
16639 to client connections" fix. Now directory authorities can
16640 protect clients from the CVE-2011-2768 issue even if neither
16641 the clients nor the relays have upgraded yet. There's a new
16642 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
16643 to let us transition smoothly, else tomorrow there would be no
16646 o Major bugfixes (hidden services):
16647 - Improve hidden service robustness: when an attempt to connect to
16648 a hidden service ends, be willing to refetch its hidden service
16649 descriptors from each of the HSDir relays responsible for them
16650 immediately. Previously, we would not consider refetching the
16651 service's descriptors from each HSDir for 15 minutes after the last
16652 fetch, which was inconvenient if the hidden service was not running
16653 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
16654 - When one of a hidden service's introduction points appears to be
16655 unreachable, stop trying it. Previously, we would keep trying
16656 to build circuits to the introduction point until we lost the
16657 descriptor, usually because the user gave up and restarted Tor.
16658 Partly fixes bug 3825.
16659 - Don't launch a useless circuit after failing to use one of a
16660 hidden service's introduction points. Previously, we would
16661 launch a new introduction circuit, but not set the hidden service
16662 which that circuit was intended to connect to, so it would never
16663 actually be used. A different piece of code would then create a
16664 new introduction circuit correctly. Bug reported by katmagic and
16665 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
16667 o Major bugfixes (other):
16668 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
16669 that they initiated. Relays could distinguish incoming bridge
16670 connections from client connections, creating another avenue for
16671 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
16672 Found by "frosty_un".
16673 - Don't update the AccountingSoftLimitHitAt state file entry whenever
16674 tor gets started. This prevents a wrong average bandwidth
16675 estimate, which would cause relays to always start a new accounting
16676 interval at the earliest possible moment. Fixes bug 2003; bugfix
16677 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
16678 immensely in tracking this bug down.
16679 - Fix a crash bug when changing node restrictions while a DNS lookup
16680 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
16683 o Minor bugfixes (on 0.2.2.x and earlier):
16684 - When a hidden service turns an extra service-side introduction
16685 circuit into a general-purpose circuit, free the rend_data and
16686 intro_key fields first, so we won't leak memory if the circuit
16687 is cannibalized for use as another service-side introduction
16688 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
16689 - Rephrase the log message emitted if the TestSocks check is
16690 successful. Patch from Fabian Keil; fixes bug 4094.
16691 - Bridges now skip DNS self-tests, to act a little more stealthily.
16692 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
16693 bridges. Patch by "warms0x".
16694 - Remove a confusing dollar sign from the example fingerprint in the
16695 man page, and also make the example fingerprint a valid one. Fixes
16696 bug 4309; bugfix on 0.2.1.3-alpha.
16697 - Fix internal bug-checking logic that was supposed to catch
16698 failures in digest generation so that it will fail more robustly
16699 if we ask for a nonexistent algorithm. Found by Coverity Scan.
16700 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
16701 - Report any failure in init_keys() calls launched because our
16702 IP address has changed. Spotted by Coverity Scan. Bugfix on
16703 0.1.1.4-alpha; fixes CID 484.
16705 o Minor bugfixes (on 0.2.3.x):
16706 - Fix a bug in configure.in that kept it from building a configure
16707 script with autoconf versions earlier than 2.61. Fixes bug 2430;
16708 bugfix on 0.2.3.1-alpha.
16709 - Don't warn users that they are exposing a client port to the
16710 Internet if they have specified an RFC1918 address. Previously,
16711 we would warn if the user had specified any non-loopback
16712 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
16713 - Fix memory leaks in the failing cases of the new SocksPort and
16714 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
16715 fixes coverity CIDs 485, 486, and 487.
16718 - When a hidden service's introduction point times out, consider
16719 trying it again during the next attempt to connect to the
16720 HS. Previously, we would not try it again unless a newly fetched
16721 descriptor contained it. Required by fixes for bugs 1297 and 3825.
16722 - The next version of Windows will be called Windows 8, and it has
16723 a major version of 6, minor version of 2. Correctly identify that
16724 version instead of calling it "Very recent version". Resolves
16725 ticket 4153; reported by funkstar.
16726 - The Bridge Authority now writes statistics on how many bridge
16727 descriptors it gave out in total, and how many unique descriptors
16728 it gave out. It also lists how often the most and least commonly
16729 fetched descriptors were given out, as well as the median and
16730 25th/75th percentile. Implements tickets 4200 and 4294.
16731 - Update to the October 4 2011 Maxmind GeoLite Country database.
16733 o Code simplifications and refactoring:
16734 - Remove some old code to remember statistics about which descriptors
16735 we've served as a directory mirror. The feature wasn't used and
16736 is outdated now that microdescriptors are around.
16737 - Rename Tor functions that turn strings into addresses, so that
16738 "parse" indicates that no hostname resolution occurs, and
16739 "lookup" indicates that hostname resolution may occur. This
16740 should help prevent mistakes in the future. Fixes bug 3512.
16743 Changes in version 0.2.2.34 - 2011-10-26
16744 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
16745 can deanonymize Tor users. Everybody should upgrade.
16747 The attack relies on four components: 1) Clients reuse their TLS cert
16748 when talking to different relays, so relays can recognize a user by
16749 the identity key in her cert. 2) An attacker who knows the client's
16750 identity key can probe each guard relay to see if that identity key
16751 is connected to that guard relay right now. 3) A variety of active
16752 attacks in the literature (starting from "Low-Cost Traffic Analysis
16753 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
16754 discover the guard relays that a Tor user visiting the website is using.
16755 4) Clients typically pick three guards at random, so the set of guards
16756 for a given user could well be a unique fingerprint for her. This
16757 release fixes components #1 and #2, which is enough to block the attack;
16758 the other two remain as open research problems. Special thanks to
16759 "frosty_un" for reporting the issue to us!
16761 Clients should upgrade so they are no longer recognizable by the TLS
16762 certs they present. Relays should upgrade so they no longer allow a
16763 remote attacker to probe them to test whether unpatched clients are
16764 currently connected to them.
16766 This release also fixes several vulnerabilities that allow an attacker
16767 to enumerate bridge relays. Some bridge enumeration attacks still
16768 remain; see for example proposal 188.
16770 o Privacy/anonymity fixes (clients):
16771 - Clients and bridges no longer send TLS certificate chains on
16772 outgoing OR connections. Previously, each client or bridge would
16773 use the same cert chain for all outgoing OR connections until
16774 its IP address changes, which allowed any relay that the client
16775 or bridge contacted to determine which entry guards it is using.
16776 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16777 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16778 no longer considers that connection as suitable for satisfying a
16779 circuit EXTEND request. Now relays can protect clients from the
16780 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16781 - Directory authorities no longer assign the Guard flag to relays
16782 that haven't upgraded to the above "refuse EXTEND requests
16783 to client connections" fix. Now directory authorities can
16784 protect clients from the CVE-2011-2768 issue even if neither
16785 the clients nor the relays have upgraded yet. There's a new
16786 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
16787 to let us transition smoothly, else tomorrow there would be no
16790 o Privacy/anonymity fixes (bridge enumeration):
16791 - Bridge relays now do their directory fetches inside Tor TLS
16792 connections, like all the other clients do, rather than connecting
16793 directly to the DirPort like public relays do. Removes another
16794 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
16795 - Bridges relays now build circuits for themselves in a more similar
16796 way to how clients build them. Removes another avenue for
16797 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
16798 when bridges were introduced.
16799 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
16800 that they initiated. Relays could distinguish incoming bridge
16801 connections from client connections, creating another avenue for
16802 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
16803 Found by "frosty_un".
16806 - Fix a crash bug when changing node restrictions while a DNS lookup
16807 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
16809 - Don't launch a useless circuit after failing to use one of a
16810 hidden service's introduction points. Previously, we would
16811 launch a new introduction circuit, but not set the hidden service
16812 which that circuit was intended to connect to, so it would never
16813 actually be used. A different piece of code would then create a
16814 new introduction circuit correctly. Bug reported by katmagic and
16815 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
16818 - Change an integer overflow check in the OpenBSD_Malloc code so
16819 that GCC is less likely to eliminate it as impossible. Patch
16820 from Mansour Moufid. Fixes bug 4059.
16821 - When a hidden service turns an extra service-side introduction
16822 circuit into a general-purpose circuit, free the rend_data and
16823 intro_key fields first, so we won't leak memory if the circuit
16824 is cannibalized for use as another service-side introduction
16825 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
16826 - Bridges now skip DNS self-tests, to act a little more stealthily.
16827 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
16828 bridges. Patch by "warms0x".
16829 - Fix internal bug-checking logic that was supposed to catch
16830 failures in digest generation so that it will fail more robustly
16831 if we ask for a nonexistent algorithm. Found by Coverity Scan.
16832 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
16833 - Report any failure in init_keys() calls launched because our
16834 IP address has changed. Spotted by Coverity Scan. Bugfix on
16835 0.1.1.4-alpha; fixes CID 484.
16837 o Minor bugfixes (log messages and documentation):
16838 - Remove a confusing dollar sign from the example fingerprint in the
16839 man page, and also make the example fingerprint a valid one. Fixes
16840 bug 4309; bugfix on 0.2.1.3-alpha.
16841 - The next version of Windows will be called Windows 8, and it has
16842 a major version of 6, minor version of 2. Correctly identify that
16843 version instead of calling it "Very recent version". Resolves
16844 ticket 4153; reported by funkstar.
16845 - Downgrade log messages about circuit timeout calibration from
16846 "notice" to "info": they don't require or suggest any human
16847 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
16848 bugfix on 0.2.2.14-alpha.
16851 - Turn on directory request statistics by default and include them in
16852 extra-info descriptors. Don't break if we have no GeoIP database.
16853 Backported from 0.2.3.1-alpha; implements ticket 3951.
16854 - Update to the October 4 2011 Maxmind GeoLite Country database.
16857 Changes in version 0.2.1.31 - 2011-10-26
16858 Tor 0.2.1.31 backports important security and privacy fixes for
16859 oldstable. This release is intended only for package maintainers and
16860 others who cannot use the 0.2.2 stable series. All others should be
16861 using Tor 0.2.2.x or newer.
16863 o Security fixes (also included in 0.2.2.x):
16864 - Replace all potentially sensitive memory comparison operations
16865 with versions whose runtime does not depend on the data being
16866 compared. This will help resist a class of attacks where an
16867 adversary can use variations in timing information to learn
16868 sensitive data. Fix for one case of bug 3122. (Safe memcmp
16869 implementation by Robert Ransom based partially on code by DJB.)
16870 - Fix an assert in parsing router descriptors containing IPv6
16871 addresses. This one took down the directory authorities when
16872 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
16874 o Privacy/anonymity fixes (also included in 0.2.2.x):
16875 - Clients and bridges no longer send TLS certificate chains on
16876 outgoing OR connections. Previously, each client or bridge would
16877 use the same cert chain for all outgoing OR connections until
16878 its IP address changes, which allowed any relay that the client
16879 or bridge contacted to determine which entry guards it is using.
16880 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16881 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16882 no longer considers that connection as suitable for satisfying a
16883 circuit EXTEND request. Now relays can protect clients from the
16884 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16885 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
16886 that they initiated. Relays could distinguish incoming bridge
16887 connections from client connections, creating another avenue for
16888 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
16889 Found by "frosty_un".
16890 - When receiving a hidden service descriptor, check that it is for
16891 the hidden service we wanted. Previously, Tor would store any
16892 hidden service descriptors that a directory gave it, whether it
16893 wanted them or not. This wouldn't have let an attacker impersonate
16894 a hidden service, but it did let directories pre-seed a client
16895 with descriptors that it didn't want. Bugfix on 0.0.6.
16896 - Avoid linkability based on cached hidden service descriptors: forget
16897 all hidden service descriptors cached as a client when processing a
16898 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
16899 - Make the bridge directory authority refuse to answer directory
16900 requests for "all" descriptors. It used to include bridge
16901 descriptors in its answer, which was a major information leak.
16902 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
16903 - Don't attach new streams to old rendezvous circuits after SIGNAL
16904 NEWNYM. Previously, we would keep using an existing rendezvous
16905 circuit if it remained open (i.e. if it were kept open by a
16906 long-lived stream, or if a new stream were attached to it before
16907 Tor could notice that it was old and no longer in use). Bugfix on
16908 0.1.1.15-rc; fixes bug 3375.
16910 o Minor bugfixes (also included in 0.2.2.x):
16911 - When we restart our relay, we might get a successful connection
16912 from the outside before we've started our reachability tests,
16913 triggering a warning: "ORPort found reachable, but I have no
16914 routerinfo yet. Failing to inform controller of success." This
16915 bug was harmless unless Tor is running under a controller
16916 like Vidalia, in which case the controller would never get a
16917 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
16919 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
16920 enabled. Fixes bug 1526.
16921 - Remove undocumented option "-F" from tor-resolve: it hasn't done
16922 anything since 0.2.1.16-rc.
16923 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
16924 None of the cases where we did this before were wrong, but by making
16925 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
16926 - Fix a rare crash bug that could occur when a client was configured
16927 with a large number of bridges. Fixes bug 2629; bugfix on
16928 0.2.1.2-alpha. Bugfix by trac user "shitlei".
16929 - Correct the warning displayed when a rendezvous descriptor exceeds
16930 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
16932 - Fix an uncommon assertion failure when running with DNSPort under
16933 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
16934 - When warning about missing zlib development packages during compile,
16935 give the correct package names. Bugfix on 0.2.0.1-alpha.
16936 - Require that introduction point keys and onion keys have public
16937 exponent 65537. Bugfix on 0.2.0.10-alpha.
16938 - Do not crash when our configuration file becomes unreadable, for
16939 example due to a permissions change, between when we start up
16940 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
16942 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
16944 - Always NUL-terminate the sun_path field of a sockaddr_un before
16945 passing it to the kernel. (Not a security issue: kernels are
16946 smart enough to reject bad sockaddr_uns.) Found by Coverity;
16947 CID #428. Bugfix on Tor 0.2.0.3-alpha.
16948 - Don't stack-allocate the list of supplementary GIDs when we're
16949 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
16950 could take up to 256K, which is way too much stack. Found by
16951 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
16953 o Minor bugfixes (only in 0.2.1.x):
16954 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
16955 rely on them. Bugfix on 0.2.1.30.
16956 - Use git revisions instead of svn revisions when generating our
16957 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
16959 o Minor features (also included in 0.2.2.x):
16960 - Adjust the expiration time on our SSL session certificates to
16961 better match SSL certs seen in the wild. Resolves ticket 4014.
16962 - Allow nameservers with IPv6 address. Resolves bug 2574.
16963 - Update to the October 4 2011 Maxmind GeoLite Country database.
16966 Changes in version 0.2.3.5-alpha - 2011-09-28
16967 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
16968 bridge relays; fixes an assertion error that many users started hitting
16969 today; and adds the ability to refill token buckets more often than
16970 once per second, allowing significant performance improvements.
16973 - Bridge relays now do their directory fetches inside Tor TLS
16974 connections, like all the other clients do, rather than connecting
16975 directly to the DirPort like public relays do. Removes another
16976 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
16977 - Bridges relays now build circuits for themselves in a more similar
16978 way to how clients build them. Removes another avenue for
16979 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
16980 when bridges were introduced.
16983 - Fix an "Assertion md->held_by_node == 1 failed" error that could
16984 occur when the same microdescriptor was referenced by two node_t
16985 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
16987 o Major features (networking):
16988 - Add a new TokenBucketRefillInterval option to refill token buckets
16989 more frequently than once per second. This should improve network
16990 performance, alleviate queueing problems, and make traffic less
16991 bursty. Implements proposal 183; closes ticket 3630. Design by
16992 Florian Tschorsch and Björn Scheuermann; implementation by
16996 - Change an integer overflow check in the OpenBSD_Malloc code so
16997 that GCC is less likely to eliminate it as impossible. Patch
16998 from Mansour Moufid. Fixes bug 4059.
17000 o Minor bugfixes (usability):
17001 - Downgrade log messages about circuit timeout calibration from
17002 "notice" to "info": they don't require or suggest any human
17003 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
17004 bugfix on 0.2.2.14-alpha.
17006 o Minor features (diagnostics):
17007 - When the system call to create a listener socket fails, log the
17008 error message explaining why. This may help diagnose bug 4027.
17011 Changes in version 0.2.3.4-alpha - 2011-09-13
17012 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
17013 tweak to Tor's TLS handshake that makes relays and bridges that run
17014 this new version reachable from Iran again. It also fixes a few new
17015 bugs in 0.2.3.x, and teaches relays to recognize when they're not
17016 listed in the network consensus and republish.
17018 o Major bugfixes (also part of 0.2.2.33):
17019 - Avoid an assertion failure when reloading a configuration with
17020 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
17021 3923; bugfix on 0.2.2.25-alpha.
17023 o Minor features (security, also part of 0.2.2.33):
17024 - Check for replays of the public-key encrypted portion of an
17025 INTRODUCE1 cell, in addition to the current check for replays of
17026 the g^x value. This prevents a possible class of active attacks
17027 by an attacker who controls both an introduction point and a
17028 rendezvous point, and who uses the malleability of AES-CTR to
17029 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
17030 that these attacks are infeasible (requiring the attacker to send
17031 on the order of zettabytes of altered cells in a short interval),
17032 but we'd rather block them off in case there are any classes of
17033 this attack that we missed. Reported by Willem Pinckaers.
17035 o Minor features (also part of 0.2.2.33):
17036 - Adjust the expiration time on our SSL session certificates to
17037 better match SSL certs seen in the wild. Resolves ticket 4014.
17038 - Change the default required uptime for a relay to be accepted as
17039 a HSDir (hidden service directory) from 24 hours to 25 hours.
17040 Improves on 0.2.0.10-alpha; resolves ticket 2649.
17041 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
17042 authorities to abstain from voting on assignment of the HSDir
17043 consensus flag. Related to bug 2649.
17044 - Update to the September 6 2011 Maxmind GeoLite Country database.
17046 o Minor bugfixes (also part of 0.2.2.33):
17047 - Demote the 'replay detected' log message emitted when a hidden
17048 service receives the same Diffie-Hellman public key in two different
17049 INTRODUCE2 cells to info level. A normal Tor client can cause that
17050 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
17051 fixes part of bug 2442.
17052 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
17053 level. There is nothing that a hidden service's operator can do
17054 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
17056 - Clarify a log message specifying the characters permitted in
17057 HiddenServiceAuthorizeClient client names. Previously, the log
17058 message said that "[A-Za-z0-9+-_]" were permitted; that could have
17059 given the impression that every ASCII character between "+" and "_"
17060 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
17062 o Build fixes (also part of 0.2.2.33):
17063 - Clean up some code issues that prevented Tor from building on older
17064 BSDs. Fixes bug 3894; reported by "grarpamp".
17065 - Search for a platform-specific version of "ar" when cross-compiling.
17066 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
17069 - Fix a bug where the SocksPort option (for example) would get
17070 ignored and replaced by the default if a SocksListenAddress
17071 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
17075 - Relays now try regenerating and uploading their descriptor more
17076 frequently if they are not listed in the consensus, or if the
17077 version of their descriptor listed in the consensus is too
17078 old. This fix should prevent situations where a server declines
17079 to re-publish itself because it has done so too recently, even
17080 though the authorities decided not to list its recent-enough
17081 descriptor. Fix for bug 3327.
17084 - Relays now include a reason for regenerating their descriptors
17085 in an HTTP header when uploading to the authorities. This will
17086 make it easier to debug descriptor-upload issues in the future.
17087 - When starting as root and then changing our UID via the User
17088 control option, and we have a ControlSocket configured, make sure
17089 that the ControlSocket is owned by the same account that Tor will
17090 run under. Implements ticket 3421; fix by Jérémy Bobbio.
17093 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
17094 utility function used in the control-port code). This shouldn't
17095 ever happen unless Tor is completely out of memory, but if it did
17096 happen and Tor somehow recovered from it, Tor could have sent a log
17097 message to a control port in the middle of a reply to a controller
17098 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
17099 - Make 'FetchUselessDescriptors' cause all descriptor types and
17100 all consensus types (including microdescriptors) to get fetched.
17101 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
17103 o Code refactoring:
17104 - Make a new "entry connection" struct as an internal subtype of "edge
17105 connection", to simplify the code and make exit connections smaller.
17108 Changes in version 0.2.2.33 - 2011-09-13
17109 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
17110 TLS handshake that makes relays and bridges that run this new version
17111 reachable from Iran again.
17114 - Avoid an assertion failure when reloading a configuration with
17115 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
17116 3923; bugfix on 0.2.2.25-alpha.
17118 o Minor features (security):
17119 - Check for replays of the public-key encrypted portion of an
17120 INTRODUCE1 cell, in addition to the current check for replays of
17121 the g^x value. This prevents a possible class of active attacks
17122 by an attacker who controls both an introduction point and a
17123 rendezvous point, and who uses the malleability of AES-CTR to
17124 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
17125 that these attacks are infeasible (requiring the attacker to send
17126 on the order of zettabytes of altered cells in a short interval),
17127 but we'd rather block them off in case there are any classes of
17128 this attack that we missed. Reported by Willem Pinckaers.
17131 - Adjust the expiration time on our SSL session certificates to
17132 better match SSL certs seen in the wild. Resolves ticket 4014.
17133 - Change the default required uptime for a relay to be accepted as
17134 a HSDir (hidden service directory) from 24 hours to 25 hours.
17135 Improves on 0.2.0.10-alpha; resolves ticket 2649.
17136 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
17137 authorities to abstain from voting on assignment of the HSDir
17138 consensus flag. Related to bug 2649.
17139 - Update to the September 6 2011 Maxmind GeoLite Country database.
17141 o Minor bugfixes (documentation and log messages):
17142 - Correct the man page to explain that HashedControlPassword and
17143 CookieAuthentication can both be set, in which case either method
17144 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
17145 when we decided to allow these config options to both be set. Issue
17146 raised by bug 3898.
17147 - Demote the 'replay detected' log message emitted when a hidden
17148 service receives the same Diffie-Hellman public key in two different
17149 INTRODUCE2 cells to info level. A normal Tor client can cause that
17150 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
17151 fixes part of bug 2442.
17152 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
17153 level. There is nothing that a hidden service's operator can do
17154 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
17156 - Clarify a log message specifying the characters permitted in
17157 HiddenServiceAuthorizeClient client names. Previously, the log
17158 message said that "[A-Za-z0-9+-_]" were permitted; that could have
17159 given the impression that every ASCII character between "+" and "_"
17160 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
17163 - Provide a substitute implementation of lround() for MSVC, which
17164 apparently lacks it. Patch from Gisle Vanem.
17165 - Clean up some code issues that prevented Tor from building on older
17166 BSDs. Fixes bug 3894; reported by "grarpamp".
17167 - Search for a platform-specific version of "ar" when cross-compiling.
17168 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
17171 Changes in version 0.2.3.3-alpha - 2011-09-01
17172 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
17173 security, and provides client-side support for the microdescriptor
17174 and optimistic data features introduced earlier in the 0.2.3.x
17175 series. It also includes numerous critical bugfixes in the (optional)
17176 bufferevent-based networking backend.
17178 o Major features (stream isolation):
17179 - You can now configure Tor so that streams from different
17180 applications are isolated on different circuits, to prevent an
17181 attacker who sees your streams as they leave an exit node from
17182 linking your sessions to one another. To do this, choose some way
17183 to distinguish the applications: have them connect to different
17184 SocksPorts, or have one of them use SOCKS4 while the other uses
17185 SOCKS5, or have them pass different authentication strings to the
17186 SOCKS proxy. Then, use the new SocksPort syntax to configure the
17187 degree of isolation you need. This implements Proposal 171.
17188 - There's a new syntax for specifying multiple client ports (such as
17189 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
17190 multiple *Port entries with full addr:port syntax on each.
17191 The old *ListenAddress format is still supported, but you can't
17192 mix it with the new *Port syntax.
17194 o Major features (other):
17195 - Enable microdescriptor fetching by default for clients. This allows
17196 clients to download a much smaller amount of directory information.
17197 To disable it (and go back to the old-style consensus and
17198 descriptors), set "UseMicrodescriptors 0" in your torrc file.
17199 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
17200 "PortForwarding" config option), now supports Windows.
17201 - When using an exit relay running 0.2.3.x, clients can now
17202 "optimistically" send data before the exit relay reports that
17203 the stream has opened. This saves a round trip when starting
17204 connections where the client speaks first (such as web browsing).
17205 This behavior is controlled by a consensus parameter (currently
17206 disabled). To turn it on or off manually, use the "OptimisticData"
17207 torrc option. Implements proposal 181; code by Ian Goldberg.
17209 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
17210 - When using IOCP on Windows, we need to enable Libevent windows
17212 - The IOCP backend now works even when the user has not specified
17213 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
17214 Fixes part of bug 3752.
17215 - Correctly record the bytes we've read and written when using
17216 bufferevents, so that we can include them in our bandwidth history
17217 and advertised bandwidth. Fixes bug 3803.
17218 - Apply rate-limiting only at the bottom of a chain of filtering
17219 bufferevents. This prevents us from filling up internal read
17220 buffers and violating rate-limits when filtering bufferevents
17221 are enabled. Fixes part of bug 3804.
17222 - Add high-watermarks to the output buffers for filtered
17223 bufferevents. This prevents us from filling up internal write
17224 buffers and wasting CPU cycles when filtering bufferevents are
17225 enabled. Fixes part of bug 3804.
17226 - Correctly notice when data has been written from a bufferevent
17227 without flushing it completely. Fixes bug 3805.
17228 - Fix a bug where server-side tunneled bufferevent-based directory
17229 streams would get closed prematurely. Fixes bug 3814.
17230 - Fix a use-after-free error with per-connection rate-limiting
17231 buckets. Fixes bug 3888.
17233 o Major bugfixes (also part of 0.2.2.31-rc):
17234 - If we're configured to write our ControlPorts to disk, only write
17235 them after switching UID and creating the data directory. This way,
17236 we don't fail when starting up with a nonexistent DataDirectory
17237 and a ControlPortWriteToFile setting based on that directory. Fixes
17238 bug 3747; bugfix on Tor 0.2.2.26-beta.
17241 - Added a new CONF_CHANGED event so that controllers can be notified
17242 of any configuration changes made by other controllers, or by the
17243 user. Implements ticket 1692.
17244 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
17245 leak when using bufferevents, and lets Libevent worry about how to
17246 best copy data out of a buffer.
17247 - Replace files in stats/ rather than appending to them. Now that we
17248 include statistics in extra-info descriptors, it makes no sense to
17249 keep old statistics forever. Implements ticket 2930.
17251 o Minor features (build compatibility):
17252 - Limited, experimental support for building with nmake and MSVC.
17253 - Provide a substitute implementation of lround() for MSVC, which
17254 apparently lacks it. Patch from Gisle Vanem.
17256 o Minor features (also part of 0.2.2.31-rc):
17257 - Update to the August 2 2011 Maxmind GeoLite Country database.
17259 o Minor bugfixes (on 0.2.3.x-alpha):
17260 - Fix a spurious warning when parsing SOCKS requests with
17261 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
17262 - Get rid of a harmless warning that could happen on relays running
17263 with bufferevents. The warning was caused by someone doing an http
17264 request to a relay's orport. Also don't warn for a few related
17265 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
17267 o Minor bugfixes (on 2.2.x and earlier):
17268 - Correct the man page to explain that HashedControlPassword and
17269 CookieAuthentication can both be set, in which case either method
17270 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
17271 when we decided to allow these config options to both be set. Issue
17272 raised by bug 3898.
17273 - The "--quiet" and "--hush" options now apply not only to Tor's
17274 behavior before logs are configured, but also to Tor's behavior in
17275 the absence of configured logs. Fixes bug 3550; bugfix on
17278 o Minor bugfixes (also part of 0.2.2.31-rc):
17279 - Write several files in text mode, on OSes that distinguish text
17280 mode from binary mode (namely, Windows). These files are:
17281 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
17282 that collect those statistics; 'client_keys' and 'hostname' for
17283 hidden services that use authentication; and (in the tor-gencert
17284 utility) newly generated identity and signing keys. Previously,
17285 we wouldn't specify text mode or binary mode, leading to an
17286 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
17287 the DirRecordUsageByCountry option which would have triggered
17288 the assertion failure was added), although this assertion failure
17289 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
17290 - Selectively disable deprecation warnings on OS X because Lion
17291 started deprecating the shipped copy of openssl. Fixes bug 3643.
17292 - Remove an extra pair of quotation marks around the error
17293 message in control-port STATUS_GENERAL BUG events. Bugfix on
17294 0.1.2.6-alpha; fixes bug 3732.
17295 - When unable to format an address as a string, report its value
17296 as "???" rather than reusing the last formatted address. Bugfix
17299 o Code simplifications and refactoring:
17300 - Rewrite the listener-selection logic so that parsing which ports
17301 we want to listen on is now separate from binding to the ports
17305 - Building Tor with bufferevent support now requires Libevent
17306 2.0.13-stable or later. Previous versions of Libevent had bugs in
17307 SSL-related bufferevents and related issues that would make Tor
17308 work badly with bufferevents. Requiring 2.0.13-stable also allows
17309 Tor with bufferevents to take advantage of Libevent APIs
17310 introduced after 2.0.8-rc.
17313 Changes in version 0.2.2.32 - 2011-08-27
17314 The Tor 0.2.2 release series is dedicated to the memory of Andreas
17315 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
17316 a founder of the PETS community, a leader in our field, a mentor,
17317 and a friend. He left us with these words: "I had the possibility
17318 to contribute to this world that is not as it should be. I hope I
17319 could help in some areas to make the world a better place, and that
17320 I could also encourage other people to be engaged in improving the
17321 world. Please, stay engaged. This world needs you, your love, your
17322 initiative -- now I cannot be part of that anymore."
17324 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
17325 ready. More than two years in the making, this release features improved
17326 client performance and hidden service reliability, better compatibility
17327 for Android, correct behavior for bridges that listen on more than
17328 one address, more extensible and flexible directory object handling,
17329 better reporting of network statistics, improved code security, and
17330 many many other features and bugfixes.
17333 Changes in version 0.2.2.31-rc - 2011-08-17
17334 Tor 0.2.2.31-rc is the second and hopefully final release candidate
17335 for the Tor 0.2.2.x series.
17338 - Remove an extra pair of quotation marks around the error
17339 message in control-port STATUS_GENERAL BUG events. Bugfix on
17340 0.1.2.6-alpha; fixes bug 3732.
17341 - If we're configured to write our ControlPorts to disk, only write
17342 them after switching UID and creating the data directory. This way,
17343 we don't fail when starting up with a nonexistent DataDirectory
17344 and a ControlPortWriteToFile setting based on that directory. Fixes
17345 bug 3747; bugfix on Tor 0.2.2.26-beta.
17348 - Update to the August 2 2011 Maxmind GeoLite Country database.
17351 - Allow GETINFO fingerprint to return a fingerprint even when
17352 we have not yet built a router descriptor. Fixes bug 3577;
17353 bugfix on 0.2.0.1-alpha.
17354 - Write several files in text mode, on OSes that distinguish text
17355 mode from binary mode (namely, Windows). These files are:
17356 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
17357 that collect those statistics; 'client_keys' and 'hostname' for
17358 hidden services that use authentication; and (in the tor-gencert
17359 utility) newly generated identity and signing keys. Previously,
17360 we wouldn't specify text mode or binary mode, leading to an
17361 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
17362 the DirRecordUsageByCountry option which would have triggered
17363 the assertion failure was added), although this assertion failure
17364 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
17365 - Selectively disable deprecation warnings on OS X because Lion
17366 started deprecating the shipped copy of openssl. Fixes bug 3643.
17367 - When unable to format an address as a string, report its value
17368 as "???" rather than reusing the last formatted address. Bugfix
17372 Changes in version 0.2.3.2-alpha - 2011-07-18
17373 Tor 0.2.3.2-alpha introduces two new experimental features:
17374 microdescriptors and pluggable transports. It also continues cleaning
17375 up a variety of recently introduced features.
17378 - Clients can now use microdescriptors instead of regular descriptors
17379 to build circuits. Microdescriptors are authority-generated
17380 summaries of regular descriptors' contents, designed to change
17381 very rarely (see proposal 158 for details). This feature is
17382 designed to save bandwidth, especially for clients on slow internet
17383 connections. It's off by default for now, since nearly no caches
17384 support it, but it will be on-by-default for clients in a future
17385 version. You can use the UseMicrodescriptors option to turn it on.
17386 - Tor clients using bridges can now be configured to use a separate
17387 'transport' proxy for each bridge. This approach helps to resist
17388 censorship by allowing bridges to use protocol obfuscation
17389 plugins. It implements part of proposal 180. Implements ticket 2841.
17390 - While we're trying to bootstrap, record how many TLS connections
17391 fail in each state, and report which states saw the most failures
17392 in response to any bootstrap failures. This feature may speed up
17393 diagnosis of censorship events. Implements ticket 3116.
17395 o Major bugfixes (on 0.2.3.1-alpha):
17396 - When configuring a large set of nodes in EntryNodes (as with
17397 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
17398 random subset to be guards, and choose them in random
17399 order. Fixes bug 2798.
17400 - Tor could crash when remembering a consensus in a non-used consensus
17401 flavor without having a current consensus set. Fixes bug 3361.
17402 - Comparing an unknown address to a microdescriptor's shortened exit
17403 policy would always give a "rejected" result. Fixes bug 3599.
17404 - Using microdescriptors as a client no longer prevents Tor from
17405 uploading and downloading hidden service descriptors. Fixes
17409 - Allow nameservers with IPv6 address. Resolves bug 2574.
17410 - Accept attempts to include a password authenticator in the
17411 handshake, as supported by SOCKS5. This handles SOCKS clients that
17412 don't know how to omit a password when authenticating. Resolves
17414 - When configuring a large set of nodes in EntryNodes, and there are
17415 enough of them listed as Guard so that we don't need to consider
17416 the non-guard entries, prefer the ones listed with the Guard flag.
17417 - Check for and recover from inconsistency in the microdescriptor
17418 cache. This will make it harder for us to accidentally free a
17419 microdescriptor without removing it from the appropriate data
17420 structures. Fixes issue 3135; issue noted by "wanoskarnet".
17421 - Log SSL state transitions at log level DEBUG, log domain
17422 HANDSHAKE. This can be useful for debugging censorship events.
17423 Implements ticket 3264.
17424 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
17425 implements ticket 3439.
17427 o Minor bugfixes (on 0.2.3.1-alpha):
17428 - Do not free all general-purpose regular descriptors just
17429 because microdescriptor use is enabled. Fixes bug 3113.
17430 - Correctly link libevent_openssl when --enable-static-libevent
17431 is passed to configure. Fixes bug 3118.
17432 - Bridges should not complain during their heartbeat log messages that
17433 they are unlisted in the consensus: that's more or less the point
17434 of being a bridge. Fixes bug 3183.
17435 - Report a SIGNAL event to controllers when acting on a delayed
17436 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
17437 event to the controller if we acted on a SIGNAL NEWNYM command
17438 immediately, and otherwise not report a SIGNAL event for the
17439 command at all. Fixes bug 3349.
17440 - Fix a crash when handling the SIGNAL controller command or
17441 reporting ERR-level status events with bufferevents enabled. Found
17442 by Robert Ransom. Fixes bug 3367.
17443 - Always ship the tor-fw-helper manpage in our release tarballs.
17444 Fixes bug 3389. Reported by Stephen Walker.
17445 - Fix a class of double-mark-for-close bugs when bufferevents
17446 are enabled. Fixes bug 3403.
17447 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
17448 - Add SIGNAL to the list returned by the 'GETINFO events/names'
17449 control-port command. Fixes part of bug 3465.
17450 - Prevent using negative indices during unit test runs when read_all()
17451 fails. Spotted by coverity.
17452 - Fix a rare memory leak when checking the nodelist without it being
17453 present. Found by coverity.
17454 - Only try to download a microdescriptor-flavored consensus from
17455 a directory cache that provides them.
17457 o Minor bugfixes (on 0.2.2.x and earlier):
17458 - Assert that hidden-service-related operations are not performed
17459 using single-hop circuits. Previously, Tor would assert that
17460 client-side streams are not attached to single-hop circuits,
17461 but not that other sensitive operations on the client and service
17462 side are not performed using single-hop circuits. Fixes bug 3332;
17464 - Don't publish a new relay descriptor when we reload our onion key,
17465 unless the onion key has actually changed. Fixes bug 3263 and
17466 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
17467 - Allow GETINFO fingerprint to return a fingerprint even when
17468 we have not yet built a router descriptor. Fixes bug 3577;
17469 bugfix on 0.2.0.1-alpha.
17470 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
17471 on 0.2.2.4-alpha; fixes bug 3427.
17473 o Code simplification and refactoring:
17474 - Use tor_sscanf() in place of scanf() in more places through the
17475 code. This makes us a little more locale-independent, and
17476 should help shut up code-analysis tools that can't tell
17477 a safe sscanf string from a dangerous one.
17478 - Use tt_assert(), not tor_assert(), for checking for test failures.
17479 This makes the unit tests more able to go on in the event that
17481 - Split connection_about_to_close() into separate functions for each
17485 - On Windows, we now define the _WIN32_WINNT macros only if they
17486 are not already defined. This lets the person building Tor decide,
17487 if they want, to require a later version of Windows.
17490 Changes in version 0.2.2.30-rc - 2011-07-07
17491 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
17492 series. It fixes a few smaller bugs, but generally appears stable.
17493 Please test it and let us know whether it is!
17496 - Send a SUCCEEDED stream event to the controller when a reverse
17497 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
17498 discovered by katmagic.
17499 - Always NUL-terminate the sun_path field of a sockaddr_un before
17500 passing it to the kernel. (Not a security issue: kernels are
17501 smart enough to reject bad sockaddr_uns.) Found by Coverity;
17502 CID #428. Bugfix on Tor 0.2.0.3-alpha.
17503 - Don't stack-allocate the list of supplementary GIDs when we're
17504 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
17505 could take up to 256K, which is way too much stack. Found by
17506 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
17507 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
17508 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
17509 fixes part of bug 3465.
17510 - Fix a memory leak when receiving a descriptor for a hidden
17511 service we didn't ask for. Found by Coverity; CID #30. Bugfix
17515 - Update to the July 1 2011 Maxmind GeoLite Country database.
17518 Changes in version 0.2.2.29-beta - 2011-06-20
17519 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
17520 have bridge lines in their torrc but don't want to use them; gets
17521 us closer to having the control socket feature working on Debian;
17522 and fixes a variety of smaller bugs.
17525 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
17526 When we changed the default behavior to "use bridges if any
17527 are listed in the torrc", we surprised users who had bridges
17528 in their torrc files but who didn't actually want to use them.
17529 Partial resolution for bug 3354.
17532 - Don't attach new streams to old rendezvous circuits after SIGNAL
17533 NEWNYM. Previously, we would keep using an existing rendezvous
17534 circuit if it remained open (i.e. if it were kept open by a
17535 long-lived stream, or if a new stream were attached to it before
17536 Tor could notice that it was old and no longer in use). Bugfix on
17537 0.1.1.15-rc; fixes bug 3375.
17540 - Fix a bug when using ControlSocketsGroupWritable with User. The
17541 directory's group would be checked against the current group, not
17542 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
17543 bugfix on 0.2.2.26-beta.
17544 - Make connection_printf_to_buf()'s behavior sane. Its callers
17545 expect it to emit a CRLF iff the format string ends with CRLF;
17546 it actually emitted a CRLF iff (a) the format string ended with
17547 CRLF or (b) the resulting string was over 1023 characters long or
17548 (c) the format string did not end with CRLF *and* the resulting
17549 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
17550 fixes part of bug 3407.
17551 - Make send_control_event_impl()'s behavior sane. Its callers
17552 expect it to always emit a CRLF at the end of the string; it
17553 might have emitted extra control characters as well. Bugfix on
17554 0.1.1.9-alpha; fixes another part of bug 3407.
17555 - Make crypto_rand_int() check the value of its input correctly.
17556 Previously, it accepted values up to UINT_MAX, but could return a
17557 negative number if given a value above INT_MAX+1. Found by George
17558 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
17559 - Avoid a segfault when reading a malformed circuit build state
17560 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
17562 - When asked about a DNS record type we don't support via a
17563 client DNSPort, reply with NOTIMPL rather than an empty
17564 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
17565 - Fix a rare memory leak during stats writing. Found by coverity.
17568 - Update to the June 1 2011 Maxmind GeoLite Country database.
17570 o Code simplifications and refactoring:
17571 - Remove some dead code as indicated by coverity.
17572 - Remove a few dead assignments during router parsing. Found by
17574 - Add some forgotten return value checks during unit tests. Found
17576 - Don't use 1-bit wide signed bit fields. Found by coverity.
17579 Changes in version 0.2.2.28-beta - 2011-06-04
17580 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
17581 fixed a big bug in whether relays stay in the consensus consistently,
17582 we moved closer to handling bridges and hidden services correctly,
17583 and we started the process of better handling the dreaded "my Vidalia
17584 died, and now my Tor demands a password when I try to reconnect to it"
17588 - Don't decide to make a new descriptor when receiving a HUP signal.
17589 This bug has caused a lot of 0.2.2.x relays to disappear from the
17590 consensus periodically. Fixes the most common case of triggering
17591 bug 1810; bugfix on 0.2.2.7-alpha.
17592 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
17593 - Don't try to build descriptors if "ORPort auto" is set and we
17594 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
17596 - Resolve a crash that occurred when setting BridgeRelay to 1 with
17597 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
17598 - Apply circuit timeouts to opened hidden-service-related circuits
17599 based on the correct start time. Previously, we would apply the
17600 circuit build timeout based on time since the circuit's creation;
17601 it was supposed to be applied based on time since the circuit
17602 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
17603 - Use the same circuit timeout for client-side introduction
17604 circuits as for other four-hop circuits, rather than the timeout
17605 for single-hop directory-fetch circuits; the shorter timeout may
17606 have been appropriate with the static circuit build timeout in
17607 0.2.1.x and earlier, but caused many hidden service access attempts
17608 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
17609 on 0.2.2.2-alpha; fixes another part of bug 1297.
17610 - In ticket 2511 we fixed a case where you could use an unconfigured
17611 bridge if you had configured it as a bridge the last time you ran
17612 Tor. Now fix another edge case: if you had configured it as a bridge
17613 but then switched to a different bridge via the controller, you
17614 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
17618 - Add an __OwningControllerProcess configuration option and a
17619 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
17620 that when it exits, Tor will shut down. Implements feature 3049.
17621 - If "UseBridges 1" is set and no bridges are configured, Tor will
17622 now refuse to build any circuits until some bridges are set.
17623 If "UseBridges auto" is set, Tor will use bridges if they are
17624 configured and we are not running as a server, but otherwise will
17625 make circuits as usual. The new default is "auto". Patch by anonym,
17626 so the Tails LiveCD can stop automatically revealing you as a Tor
17630 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
17631 - Remove a trailing asterisk from "exit-policy/default" in the
17632 output of the control port command "GETINFO info/names". Bugfix
17634 - Use a wide type to hold sockets when built for 64-bit Windows builds.
17636 - Warn when the user configures two HiddenServiceDir lines that point
17637 to the same directory. Bugfix on 0.0.6 (the version introducing
17638 HiddenServiceDir); fixes bug 3289.
17639 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
17640 part of bug 2748; bugfix on 0.2.0.10-alpha.
17641 - Log malformed requests for rendezvous descriptors as protocol
17642 warnings, not warnings. Also, use a more informative log message
17643 in case someone sees it at log level warning without prior
17644 info-level messages. Fixes the other part of bug 2748; bugfix
17646 - Clear the table recording the time of the last request for each
17647 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
17648 Previously, we would clear our HS descriptor cache on SIGNAL
17649 NEWNYM, but if we had previously retrieved a descriptor (or tried
17650 to) from every directory responsible for it, we would refuse to
17651 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
17653 - Fix a log message that said "bits" while displaying a value in
17654 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
17656 - When checking for 1024-bit keys, check for 1024 bits, not 128
17657 bytes. This allows Tor to correctly discard keys of length 1017
17658 through 1023. Bugfix on 0.0.9pre5.
17661 - Relays now log the reason for publishing a new relay descriptor,
17662 so we have a better chance of hunting down instances of bug 1810.
17663 Resolves ticket 3252.
17664 - Revise most log messages that refer to nodes by nickname to
17665 instead use the "$key=nickname at address" format. This should be
17666 more useful, especially since nicknames are less and less likely
17667 to be unique. Resolves ticket 3045.
17668 - Log (at info level) when purging pieces of hidden-service-client
17669 state because of SIGNAL NEWNYM.
17672 - Remove undocumented option "-F" from tor-resolve: it hasn't done
17673 anything since 0.2.1.16-rc.
17676 Changes in version 0.2.2.27-beta - 2011-05-18
17677 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
17678 release, and also adds a few more general bugfixes.
17681 - Fix a crash bug when changing bridges in a running Tor process.
17682 Fixes bug 3213; bugfix on 0.2.2.26-beta.
17683 - When the controller configures a new bridge, don't wait 10 to 60
17684 seconds before trying to fetch its descriptor. Bugfix on
17685 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
17688 - Require that onion keys have exponent 65537 in microdescriptors too.
17689 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
17690 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
17691 Changed the limit to 512 characters by removing base64 newlines.
17692 Fixes bug 2752. Fix by Michael Yakubovich.
17693 - When a client starts or stops using bridges, never use a circuit
17694 that was built before the configuration change. This behavior could
17695 put at risk a user who uses bridges to ensure that her traffic
17696 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
17700 Changes in version 0.2.2.26-beta - 2011-05-17
17701 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
17702 also introduces a new "socksport auto" approach that should make it
17703 easier to run multiple Tors on the same system, and does a lot of
17704 cleanup to get us closer to a release candidate.
17706 o Security/privacy fixes:
17707 - Replace all potentially sensitive memory comparison operations
17708 with versions whose runtime does not depend on the data being
17709 compared. This will help resist a class of attacks where an
17710 adversary can use variations in timing information to learn
17711 sensitive data. Fix for one case of bug 3122. (Safe memcmp
17712 implementation by Robert Ransom based partially on code by DJB.)
17713 - When receiving a hidden service descriptor, check that it is for
17714 the hidden service we wanted. Previously, Tor would store any
17715 hidden service descriptors that a directory gave it, whether it
17716 wanted them or not. This wouldn't have let an attacker impersonate
17717 a hidden service, but it did let directories pre-seed a client
17718 with descriptors that it didn't want. Bugfix on 0.0.6.
17719 - On SIGHUP, do not clear out all TrackHostExits mappings, client
17720 DNS cache entries, and virtual address mappings: that's what
17721 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
17724 - The options SocksPort, ControlPort, and so on now all accept a
17725 value "auto" that opens a socket on an OS-selected port. A
17726 new ControlPortWriteToFile option tells Tor to write its
17727 actual control port or ports to a chosen file. If the option
17728 ControlPortFileGroupReadable is set, the file is created as
17729 group-readable. Now users can run two Tor clients on the same
17730 system without needing to manually mess with parameters. Resolves
17731 part of ticket 3076.
17732 - Set SO_REUSEADDR on all sockets, not just listeners. This should
17733 help busy exit nodes avoid running out of useable ports just
17734 because all the ports have been used in the near past. Resolves
17738 - New "GETINFO net/listeners/(type)" controller command to return
17739 a list of addresses and ports that are bound for listeners for a
17740 given connection type. This is useful when the user has configured
17741 "SocksPort auto" and the controller needs to know which port got
17742 chosen. Resolves another part of ticket 3076.
17743 - Add a new ControlSocketsGroupWritable configuration option: when
17744 it is turned on, ControlSockets are group-writeable by the default
17745 group of the current user. Patch by Jérémy Bobbio; implements
17747 - Tor now refuses to create a ControlSocket in a directory that is
17748 world-readable (or group-readable if ControlSocketsGroupWritable
17749 is 0). This is necessary because some operating systems do not
17750 enforce permissions on an AF_UNIX sockets. Permissions on the
17751 directory holding the socket, however, seems to work everywhere.
17752 - Rate-limit a warning about failures to download v2 networkstatus
17753 documents. Resolves part of bug 1352.
17754 - Backport code from 0.2.3.x that allows directory authorities to
17755 clean their microdescriptor caches. Needed to resolve bug 2230.
17756 - When an HTTPS proxy reports "403 Forbidden", we now explain
17757 what it means rather than calling it an unexpected status code.
17758 Closes bug 2503. Patch from Michael Yakubovich.
17759 - Update to the May 1 2011 Maxmind GeoLite Country database.
17762 - Authorities now clean their microdesc cache periodically and when
17763 reading from disk initially, not only when adding new descriptors.
17764 This prevents a bug where we could lose microdescriptors. Bugfix
17765 on 0.2.2.6-alpha. Fixes bug 2230.
17766 - Do not crash when our configuration file becomes unreadable, for
17767 example due to a permissions change, between when we start up
17768 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
17770 - Avoid a bug that would keep us from replacing a microdescriptor
17771 cache on Windows. (We would try to replace the file while still
17772 holding it open. That's fine on Unix, but Windows doesn't let us
17773 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
17774 - Add missing explanations for the authority-related torrc options
17775 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
17776 man page. Resolves issue 2379.
17777 - As an authority, do not upload our own vote or signature set to
17778 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
17779 it would get flagged as a duplicate. Resolves bug 3026.
17780 - Accept hidden service descriptors if we think we might be a hidden
17781 service directory, regardless of what our consensus says. This
17782 helps robustness, since clients and hidden services can sometimes
17783 have a more up-to-date view of the network consensus than we do,
17784 and if they think that the directory authorities list us a HSDir,
17785 we might actually be one. Related to bug 2732; bugfix on
17787 - When a controller changes TrackHostExits, remove mappings for
17788 hosts that should no longer have their exits tracked. Bugfix on
17790 - When a controller changes VirtualAddrNetwork, remove any mappings
17791 for hosts that were automapped to the old network. Bugfix on
17793 - When a controller changes one of the AutomapHosts* options, remove
17794 any mappings for hosts that should no longer be automapped. Bugfix
17796 - Do not reset the bridge descriptor download status every time we
17797 re-parse our configuration or get a configuration change. Fixes
17798 bug 3019; bugfix on 0.2.0.3-alpha.
17800 o Minor bugfixes (code cleanup):
17801 - When loading the microdesc journal, remember its current size.
17802 In 0.2.2, this helps prevent the microdesc journal from growing
17803 without limit on authorities (who are the only ones to use it in
17804 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
17805 Fix posted by "cypherpunks."
17806 - The microdesc journal is supposed to get rebuilt only if it is
17807 at least _half_ the length of the store, not _twice_ the length
17808 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
17809 - Fix a potential null-pointer dereference while computing a
17810 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
17812 - Avoid a possible null-pointer dereference when rebuilding the mdesc
17813 cache without actually having any descriptors to cache. Bugfix on
17814 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
17815 - If we fail to compute the identity digest of a v3 legacy keypair,
17816 warn, and don't use a buffer-full of junk instead. Bugfix on
17817 0.2.1.1-alpha; fixes bug 3106.
17818 - Resolve an untriggerable issue in smartlist_string_num_isin(),
17819 where if the function had ever in the future been used to check
17820 for the presence of a too-large number, it would have given an
17821 incorrect result. (Fortunately, we only used it for 16-bit
17822 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
17823 - Require that introduction point keys and onion handshake keys
17824 have a public exponent of 65537. Starts to fix bug 3207; bugfix
17827 o Removed features:
17828 - Caches no longer download and serve v2 networkstatus documents
17829 unless FetchV2Networkstatus flag is set: these documents haven't
17830 haven't been used by clients or relays since 0.2.0.x. Resolves
17834 Changes in version 0.2.3.1-alpha - 2011-05-05
17835 Tor 0.2.3.1-alpha adds some new experimental features, including support
17836 for an improved network IO backend, IOCP networking on Windows,
17837 microdescriptor caching, "fast-start" support for streams, and automatic
17838 home router configuration. There are also numerous internal improvements
17839 to try to make the code easier for developers to work with.
17841 This is the first alpha release in a new series, so expect there to be
17842 bugs. Users who would rather test out a more stable branch should
17843 stay with 0.2.2.x for now.
17846 - Tor can now optionally build with the "bufferevents" buffered IO
17847 backend provided by Libevent 2. To use this feature, make sure you
17848 have the latest possible version of Libevent, and pass the
17849 --enable-bufferevents flag to configure when building Tor from
17850 source. This feature will make our networking code more flexible,
17851 let us stack layers on each other, and let us use more efficient
17852 zero-copy transports where available.
17853 - As an experimental feature, Tor can use IOCP for networking on Windows.
17854 Once this code is tuned and optimized, it promises much better
17855 performance than the select-based backend we've used in the past. To
17856 try this feature, you must build Tor with Libevent 2, configure Tor
17857 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
17858 your torrc. There are known bugs here: only try this if you can help
17859 debug it as it breaks.
17860 - The EntryNodes option can now include country codes like {de} or IP
17861 addresses or network masks. Previously we had disallowed these options
17862 because we didn't have an efficient way to keep the list up to
17863 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
17864 - Exit nodes now accept and queue data on not-yet-connected streams.
17865 Previously, the client wasn't allowed to send data until the stream was
17866 connected, which slowed down all connections. This change will enable
17867 clients to perform a "fast-start" on streams and send data without
17868 having to wait for a confirmation that the stream has opened. (Patch
17869 from Ian Goldberg; implements the server side of Proposal 174.)
17870 - Tor now has initial support for automatic port mapping on the many
17871 home routers that support NAT-PMP or UPnP. (Not yet supported on
17872 Windows). To build the support code, you'll need to have libnatpnp
17873 library and/or the libminiupnpc library, and you'll need to enable the
17874 feature specifically by passing "--enable-upnp" and/or
17875 "--enable-natpnp" to configure. To turn it on, use the new
17876 PortForwarding option.
17877 - Caches now download, cache, and serve multiple "flavors" of the
17878 consensus, including a flavor that describes microdescriptors.
17879 - Caches now download, cache, and serve microdescriptors -- small
17880 summaries of router descriptors that are authenticated by all of the
17881 directory authorities. Once enough caches are running this code,
17882 clients will be able to save significant amounts of directory bandwidth
17883 by downloading microdescriptors instead of router descriptors.
17886 - Make logging resolution configurable with a new LogTimeGranularity
17887 option, and change the default from 1 millisecond to 1 second.
17888 Implements enhancement 1668.
17889 - We log which torrc file we're using on startup. Implements ticket
17891 - Ordinarily, Tor does not count traffic from private addresses (like
17892 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
17893 There is now a new option, CountPrivateBandwidth, to disable this
17894 behavior. Patch from Daniel Cagara.
17895 - New --enable-static-tor configure option for building Tor as
17896 statically as possible. Idea, general hackery and thoughts from
17897 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
17899 - If you set the NumCPUs option to 0, Tor will now try to detect how
17900 many CPUs you have. This is the new default behavior.
17901 - Turn on directory request statistics by default and include them in
17902 extra-info descriptors. Don't break if we have no GeoIP database.
17903 - Relays that set "ConnDirectionStatistics 1" write statistics on the
17904 bidirectional use of connections to disk every 24 hours.
17905 - Add a GeoIP file digest to the extra-info descriptor. Implements
17907 - The NodeFamily option -- which let you declare that you want to
17908 consider nodes to be part of a family whether they list themselves
17909 that way or not -- now allows IP address ranges and country codes.
17910 - Add a new 'Heartbeat' log message type to periodically log a message
17911 describing Tor's status at level Notice. This feature is meant for
17912 operators who log at notice, and want to make sure that their Tor
17913 server is still working. Implementation by George Kadianakis.
17915 o Minor bugfixes (on 0.2.2.25-alpha):
17916 - When loading the microdesc journal, remember its current size.
17917 In 0.2.2, this helps prevent the microdesc journal from growing
17918 without limit on authorities (who are the only ones to use it in
17919 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
17920 Fix posted by "cypherpunks."
17921 - The microdesc journal is supposed to get rebuilt only if it is
17922 at least _half_ the length of the store, not _twice_ the length
17923 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
17924 - If as an authority we fail to compute the identity digest of a v3
17925 legacy keypair, warn, and don't use a buffer-full of junk instead.
17926 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
17927 - Authorities now clean their microdesc cache periodically and when
17928 reading from disk initially, not only when adding new descriptors.
17929 This prevents a bug where we could lose microdescriptors. Bugfix
17932 o Minor features (controller):
17933 - Add a new SIGNAL event to the controller interface so that
17934 controllers can be notified when Tor handles a signal. Resolves
17935 issue 1955. Patch by John Brooks.
17936 - Add a new GETINFO option to get total bytes read and written. Patch
17937 from pipe, revised by atagar. Resolves ticket 2345.
17938 - Implement some GETINFO controller fields to provide information about
17939 the Tor process's pid, euid, username, and resource limits.
17942 - Our build system requires automake 1.6 or later to create the
17943 Makefile.in files. Previously, you could have used 1.4.
17944 This only affects developers and people building Tor from git;
17945 people who build Tor from the source distribution without changing
17946 the Makefile.am files should be fine.
17947 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
17948 so on. This is more robust against some of the failure modes
17949 associated with running the autotools pieces on their own.
17951 o Minor packaging issues:
17952 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
17953 already created. Patch from Andreas Stieger. Fixes bug 2573.
17955 o Code simplifications and refactoring:
17956 - A major revision to our internal node-selecting and listing logic.
17957 Tor already had at least two major ways to look at the question of
17958 "which Tor servers do we know about": a list of router descriptors,
17959 and a list of entries in the current consensus. With
17960 microdescriptors, we're adding a third. Having so many systems
17961 without an abstraction layer over them was hurting the codebase.
17962 Now, we have a new "node_t" abstraction that presents a consistent
17963 interface to a client's view of a Tor node, and holds (nearly) all
17964 of the mutable state formerly in routerinfo_t and routerstatus_t.
17965 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
17966 no longer link against Libevent: they never used it, but
17967 our library structure used to force them to link it.
17969 o Removed features:
17970 - Remove some old code to work around even older versions of Tor that
17971 used forked processes to handle DNS requests. Such versions of Tor
17972 are no longer in use as servers.
17974 o Documentation fixes:
17975 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
17976 - Add missing documentation for the authority-related torrc options
17977 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
17981 Changes in version 0.2.2.25-alpha - 2011-04-29
17982 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
17983 robust, routers no longer overreport their bandwidth, Win7 should crash
17984 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
17985 now prevents hidden service-related activity from being linkable. It
17986 provides more information to Vidalia so you can see if your bridge is
17987 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
17988 StrictNodes configuration options to make them more reliable, more
17989 understandable, and more regularly applied. If you use those options,
17990 please see the revised documentation for them in the manual page.
17993 - Relays were publishing grossly inflated bandwidth values because
17994 they were writing their state files wrong--now they write the
17995 correct value. Also, resume reading bandwidth history from the
17996 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
17997 - Improve hidden service robustness: When we find that we have
17998 extended a hidden service's introduction circuit to a relay not
17999 listed as an introduction point in the HS descriptor we currently
18000 have, retry with an introduction point from the current
18001 descriptor. Previously we would just give up. Fixes bugs 1024 and
18002 1930; bugfix on 0.2.0.10-alpha.
18003 - Clients now stop trying to use an exit node associated with a given
18004 destination by TrackHostExits if they fail to reach that exit node.
18005 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
18006 - Fix crash bug on platforms where gmtime and localtime can return
18007 NULL. Windows 7 users were running into this one. Fixes part of bug
18008 2077. Bugfix on all versions of Tor. Found by boboper.
18010 o Security and stability fixes:
18011 - Don't double-free a parsable, but invalid, microdescriptor, even if
18012 it is followed in the blob we're parsing by an unparsable
18013 microdescriptor. Fixes an issue reported in a comment on bug 2954.
18014 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
18015 - If the Nickname configuration option isn't given, Tor would pick a
18016 nickname based on the local hostname as the nickname for a relay.
18017 Because nicknames are not very important in today's Tor and the
18018 "Unnamed" nickname has been implemented, this is now problematic
18019 behavior: It leaks information about the hostname without being
18020 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
18021 introduced the Unnamed nickname. Reported by tagnaq.
18022 - Fix an uncommon assertion failure when running with DNSPort under
18023 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
18024 - Avoid linkability based on cached hidden service descriptors: forget
18025 all hidden service descriptors cached as a client when processing a
18026 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
18029 - Export GeoIP information on bridge usage to controllers even if we
18030 have not yet been running for 24 hours. Now Vidalia bridge operators
18031 can get more accurate and immediate feedback about their
18032 contributions to the network.
18034 o Major features and bugfixes (node selection):
18035 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
18036 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
18037 options. Previously, we had been ambiguous in describing what
18038 counted as an "exit" node, and what operations exactly "StrictNodes
18039 0" would permit. This created confusion when people saw nodes built
18040 through unexpected circuits, and made it hard to tell real bugs from
18041 surprises. Now the intended behavior is:
18042 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
18043 a node that delivers user traffic outside the Tor network.
18044 . "Entry", in the context of EntryNodes, means a node used as the
18045 first hop of a multihop circuit. It doesn't include direct
18046 connections to directory servers.
18047 . "ExcludeNodes" applies to all nodes.
18048 . "StrictNodes" changes the behavior of ExcludeNodes only. When
18049 StrictNodes is set, Tor should avoid all nodes listed in
18050 ExcludeNodes, even when it will make user requests fail. When
18051 StrictNodes is *not* set, then Tor should follow ExcludeNodes
18052 whenever it can, except when it must use an excluded node to
18053 perform self-tests, connect to a hidden service, provide a
18054 hidden service, fulfill a .exit request, upload directory
18055 information, or fetch directory information.
18056 Collectively, the changes to implement the behavior fix bug 1090.
18057 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
18058 a node is listed in both, it's treated as excluded.
18059 - ExcludeNodes now applies to directory nodes -- as a preference if
18060 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
18061 Don't exclude all the directory authorities and set StrictNodes to 1
18062 unless you really want your Tor to break.
18063 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
18064 - ExcludeExitNodes now overrides .exit requests.
18065 - We don't use bridges listed in ExcludeNodes.
18066 - When StrictNodes is 1:
18067 . We now apply ExcludeNodes to hidden service introduction points
18068 and to rendezvous points selected by hidden service users. This
18069 can make your hidden service less reliable: use it with caution!
18070 . If we have used ExcludeNodes on ourself, do not try relay
18071 reachability self-tests.
18072 . If we have excluded all the directory authorities, we will not
18073 even try to upload our descriptor if we're a relay.
18074 . Do not honor .exit requests to an excluded node.
18075 - Remove a misfeature that caused us to ignore the Fast/Stable flags
18076 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
18077 - When the set of permitted nodes changes, we now remove any mappings
18078 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
18080 - We never cannibalize a circuit that had excluded nodes on it, even
18081 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
18082 - Revert a change where we would be laxer about attaching streams to
18083 circuits than when building the circuits. This was meant to prevent
18084 a set of bugs where streams were never attachable, but our improved
18085 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
18086 - Keep track of how many times we launch a new circuit to handle a
18087 given stream. Too many launches could indicate an inconsistency
18088 between our "launch a circuit to handle this stream" logic and our
18089 "attach this stream to one of the available circuits" logic.
18090 - Improve log messages related to excluded nodes.
18093 - Fix a spurious warning when moving from a short month to a long
18094 month on relays with month-based BandwidthAccounting. Bugfix on
18095 0.2.2.17-alpha; fixes bug 3020.
18096 - When a client finds that an origin circuit has run out of 16-bit
18097 stream IDs, we now mark it as unusable for new streams. Previously,
18098 we would try to close the entire circuit. Bugfix on 0.0.6.
18099 - Add a forgotten cast that caused a compile warning on OS X 10.6.
18100 Bugfix on 0.2.2.24-alpha.
18101 - Be more careful about reporting the correct error from a failed
18102 connect() system call. Under some circumstances, it was possible to
18103 look at an incorrect value for errno when sending the end reason.
18104 Bugfix on 0.1.0.1-rc.
18105 - Correctly handle an "impossible" overflow cases in connection byte
18106 counting, where we write or read more than 4GB on an edge connection
18107 in a single second. Bugfix on 0.1.2.8-beta.
18108 - Correct the warning displayed when a rendezvous descriptor exceeds
18109 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
18111 - Clients and hidden services now use HSDir-flagged relays for hidden
18112 service descriptor downloads and uploads even if the relays have no
18113 DirPort set and the client has disabled TunnelDirConns. This will
18114 eventually allow us to give the HSDir flag to relays with no
18115 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
18116 - Downgrade "no current certificates known for authority" message from
18117 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
18118 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
18119 2917. Bugfix on 0.1.1.1-alpha.
18120 - Only limit the lengths of single HS descriptors, even when multiple
18121 HS descriptors are published to an HSDir relay in a single POST
18122 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
18123 - Write the current time into the LastWritten line in our state file,
18124 rather than the time from the previous write attempt. Also, stop
18125 trying to use a time of -1 in our log statements. Fixes bug 3039;
18126 bugfix on 0.2.2.14-alpha.
18127 - Be more consistent in our treatment of file system paths. "~" should
18128 get expanded to the user's home directory in the Log config option.
18129 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
18130 feature for the -f and --DataDirectory options.
18133 - Make sure every relay writes a state file at least every 12 hours.
18134 Previously, a relay could go for weeks without writing its state
18135 file, and on a crash could lose its bandwidth history, capacity
18136 estimates, client country statistics, and so on. Addresses bug 3012.
18137 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
18138 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
18139 clients are already deprecated because of security bugs.
18140 - Don't allow v0 hidden service authorities to act as clients.
18141 Required by fix for bug 3000.
18142 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
18143 by fix for bug 3000.
18144 - Ensure that no empty [dirreq-](read|write)-history lines are added
18145 to an extrainfo document. Implements ticket 2497.
18147 o Code simplification and refactoring:
18148 - Remove workaround code to handle directory responses from servers
18149 that had bug 539 (they would send HTTP status 503 responses _and_
18150 send a body too). Since only server versions before
18151 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
18152 keep the workaround in place.
18153 - Remove the old 'fuzzy time' logic. It was supposed to be used for
18154 handling calculations where we have a known amount of clock skew and
18155 an allowed amount of unknown skew. But we only used it in three
18156 places, and we never adjusted the known/unknown skew values. This is
18157 still something we might want to do someday, but if we do, we'll
18158 want to do it differently.
18159 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
18160 None of the cases where we did this before were wrong, but by making
18161 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
18162 - Use GetTempDir to find the proper temporary directory location on
18163 Windows when generating temporary files for the unit tests. Patch by
18167 Changes in version 0.2.2.24-alpha - 2011-04-08
18168 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
18169 prevented Tor clients from effectively using "multihomed" bridges,
18170 that is, bridges that listen on multiple ports or IP addresses so users
18171 can continue to use some of their addresses even if others get blocked.
18174 - Fix a bug where bridge users who configure the non-canonical
18175 address of a bridge automatically switch to its canonical
18176 address. If a bridge listens at more than one address, it should be
18177 able to advertise those addresses independently and any non-blocked
18178 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
18180 - If you configured Tor to use bridge A, and then quit and
18181 configured Tor to use bridge B instead, it would happily continue
18182 to use bridge A if it's still reachable. While this behavior is
18183 a feature if your goal is connectivity, in some scenarios it's a
18184 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
18185 - Directory authorities now use data collected from their own
18186 uptime observations when choosing whether to assign the HSDir flag
18187 to relays, instead of trusting the uptime value the relay reports in
18188 its descriptor. This change helps prevent an attack where a small
18189 set of nodes with frequently-changing identity keys can blackhole
18190 a hidden service. (Only authorities need upgrade; others will be
18191 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
18194 - When we restart our relay, we might get a successful connection
18195 from the outside before we've started our reachability tests,
18196 triggering a warning: "ORPort found reachable, but I have no
18197 routerinfo yet. Failing to inform controller of success." This
18198 bug was harmless unless Tor is running under a controller
18199 like Vidalia, in which case the controller would never get a
18200 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
18202 - Make directory authorities more accurate at recording when
18203 relays that have failed several reachability tests became
18204 unreachable, so we can provide more accuracy at assigning Stable,
18205 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
18206 - Fix an issue that prevented static linking of libevent on
18207 some platforms (notably Linux). Fixes bug 2698; bugfix on
18208 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
18209 the --with-static-libevent configure option).
18210 - We now ask the other side of a stream (the client or the exit)
18211 for more data on that stream when the amount of queued data on
18212 that stream dips low enough. Previously, we wouldn't ask the
18213 other side for more data until either it sent us more data (which
18214 it wasn't supposed to do if it had exhausted its window!) or we
18215 had completely flushed all our queued data. This flow control fix
18216 should improve throughput. Fixes bug 2756; bugfix on the earliest
18217 released versions of Tor (svn commit r152).
18218 - Avoid a double-mark-for-free warning when failing to attach a
18219 transparent proxy connection. (We thought we had fixed this in
18220 0.2.2.23-alpha, but it turns out our fix was checking the wrong
18221 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
18222 bug) and 0.2.2.23-alpha (the incorrect fix).
18223 - When warning about missing zlib development packages during compile,
18224 give the correct package names. Bugfix on 0.2.0.1-alpha.
18227 - Directory authorities now log the source of a rejected POSTed v3
18228 networkstatus vote.
18229 - Make compilation with clang possible when using
18230 --enable-gcc-warnings by removing two warning options that clang
18231 hasn't implemented yet and by fixing a few warnings. Implements
18233 - When expiring circuits, use microsecond timers rather than
18234 one-second timers. This can avoid an unpleasant situation where a
18235 circuit is launched near the end of one second and expired right
18236 near the beginning of the next, and prevent fluctuations in circuit
18238 - Use computed circuit-build timeouts to decide when to launch
18239 parallel introduction circuits for hidden services. (Previously,
18240 we would retry after 15 seconds.)
18241 - Update to the April 1 2011 Maxmind GeoLite Country database.
18244 - Create the /var/run/tor directory on startup on OpenSUSE if it is
18245 not already created. Patch from Andreas Stieger. Fixes bug 2573.
18247 o Documentation changes:
18248 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
18249 - Resolve all doxygen warnings except those for missing documentation.
18251 - Add doxygen documentation for more functions, fields, and types.
18254 Changes in version 0.2.2.23-alpha - 2011-03-08
18255 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
18256 they restart they don't lose their bandwidth capacity estimate. This
18257 release also fixes a diverse set of user-facing bugs, ranging from
18258 relays overrunning their rate limiting to clients falsely warning about
18259 clock skew to bridge descriptor leaks by our bridge directory authority.
18262 - Stop sending a CLOCK_SKEW controller status event whenever
18263 we fetch directory information from a relay that has a wrong clock.
18264 Instead, only inform the controller when it's a trusted authority
18265 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
18266 the rest of bug 1074.
18267 - Fix an assert in parsing router descriptors containing IPv6
18268 addresses. This one took down the directory authorities when
18269 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
18270 - Make the bridge directory authority refuse to answer directory
18271 requests for "all" descriptors. It used to include bridge
18272 descriptors in its answer, which was a major information leak.
18273 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
18274 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
18275 Tor would ignore their RelayBandwidthBurst setting,
18276 potentially using more bandwidth than expected. Bugfix on
18277 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
18278 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
18279 hidserv" in her torrc. The 'hidserv' argument never controlled
18280 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
18283 - Relays now save observed peak bandwidth throughput rates to their
18284 state file (along with total usage, which was already saved)
18285 so that they can determine their correct estimated bandwidth on
18286 restart. Resolves bug 1863, where Tor relays would reset their
18287 estimated bandwidth to 0 after restarting.
18288 - Directory authorities now take changes in router IP address and
18289 ORPort into account when determining router stability. Previously,
18290 if a router changed its IP or ORPort, the authorities would not
18291 treat it as having any downtime for the purposes of stability
18292 calculation, whereas clients would experience downtime since the
18293 change could take a while to propagate to them. Resolves issue 1035.
18294 - Enable Address Space Layout Randomization (ASLR) and Data Execution
18295 Prevention (DEP) by default on Windows to make it harder for
18296 attackers to exploit vulnerabilities. Patch from John Brooks.
18298 o Minor bugfixes (on 0.2.1.x and earlier):
18299 - Fix a rare crash bug that could occur when a client was configured
18300 with a large number of bridges. Fixes bug 2629; bugfix on
18301 0.2.1.2-alpha. Bugfix by trac user "shitlei".
18302 - Avoid a double mark-for-free warning when failing to attach a
18303 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
18305 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
18306 found by "cypherpunks". This bug was introduced before the first
18307 Tor release, in svn commit r110.
18308 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
18309 don't mention them in the manpage. Fixes bug 2450; issue
18310 spotted by keb and G-Lo.
18311 - Fix a bug in bandwidth history state parsing that could have been
18312 triggered if a future version of Tor ever changed the timing
18313 granularity at which bandwidth history is measured. Bugfix on
18314 Tor 0.1.1.11-alpha.
18315 - When a relay decides that its DNS is too broken for it to serve
18316 as an exit server, it advertised itself as a non-exit, but
18317 continued to act as an exit. This could create accidental
18318 partitioning opportunities for users. Instead, if a relay is
18319 going to advertise reject *:* as its exit policy, it should
18320 really act with exit policy "reject *:*". Fixes bug 2366.
18321 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
18322 - In the special case where you configure a public exit relay as your
18323 bridge, Tor would be willing to use that exit relay as the last
18324 hop in your circuit as well. Now we fail that circuit instead.
18325 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
18326 - Fix a bug with our locking implementation on Windows that couldn't
18327 correctly detect when a file was already locked. Fixes bug 2504,
18328 bugfix on 0.2.1.6-alpha.
18329 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
18330 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
18332 - Set target port in get_interface_address6() correctly. Bugfix
18333 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
18334 - Directory authorities are now more robust to hops back in time
18335 when calculating router stability. Previously, if a run of uptime
18336 or downtime appeared to be negative, the calculation could give
18337 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
18339 - Fix an assert that got triggered when using the TestingTorNetwork
18340 configuration option and then issuing a GETINFO config-text control
18341 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
18343 o Minor bugfixes (on 0.2.2.x):
18344 - Clients should not weight BadExit nodes as Exits in their node
18345 selection. Similarly, directory authorities should not count BadExit
18346 bandwidth as Exit bandwidth when computing bandwidth-weights.
18347 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
18348 - Correctly clear our dir_read/dir_write history when there is an
18349 error parsing any bw history value from the state file. Bugfix on
18350 Tor 0.2.2.15-alpha.
18351 - Resolve a bug in verifying signatures of directory objects
18352 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
18353 Fixes bug 2409. Found by "piebeer".
18354 - Bridge authorities no longer crash on SIGHUP when they try to
18355 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
18359 - Log less aggressively about circuit timeout changes, and improve
18360 some other circuit timeout messages. Resolves bug 2004.
18361 - Log a little more clearly about the times at which we're no longer
18362 accepting new connections. Resolves bug 2181.
18363 - Reject attempts at the client side to open connections to private
18364 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
18365 a randomly chosen exit node. Attempts to do so are always
18366 ill-defined, generally prevented by exit policies, and usually
18367 in error. This will also help to detect loops in transparent
18368 proxy configurations. You can disable this feature by setting
18369 "ClientRejectInternalAddresses 0" in your torrc.
18370 - Always treat failure to allocate an RSA key as an unrecoverable
18372 - Update to the March 1 2011 Maxmind GeoLite Country database.
18374 o Minor features (log subsystem):
18375 - Add documentation for configuring logging at different severities in
18376 different log domains. We've had this feature since 0.2.1.1-alpha,
18377 but for some reason it never made it into the manpage. Fixes
18379 - Make it simpler to specify "All log domains except for A and B".
18380 Previously you needed to say "[*,~A,~B]". Now you can just say
18382 - Add a "LogMessageDomains 1" option to include the domains of log
18383 messages along with the messages. Without this, there's no way
18384 to use log domains without reading the source or doing a lot
18387 o Packaging changes:
18388 - Stop shipping the Tor specs files and development proposal documents
18389 in the tarball. They are now in a separate git repository at
18390 git://git.torproject.org/torspec.git
18393 Changes in version 0.2.1.30 - 2011-02-23
18394 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
18395 change is a slight tweak to Tor's TLS handshake that makes relays
18396 and bridges that run this new version reachable from Iran again.
18397 We don't expect this tweak will win the arms race long-term, but it
18398 buys us time until we roll out a better solution.
18401 - Stop sending a CLOCK_SKEW controller status event whenever
18402 we fetch directory information from a relay that has a wrong clock.
18403 Instead, only inform the controller when it's a trusted authority
18404 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
18405 the rest of bug 1074.
18406 - Fix a bounds-checking error that could allow an attacker to
18407 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
18408 Found by "piebeer".
18409 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
18410 Tor would ignore their RelayBandwidthBurst setting,
18411 potentially using more bandwidth than expected. Bugfix on
18412 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
18413 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
18414 hidserv" in her torrc. The 'hidserv' argument never controlled
18415 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
18418 - Adjust our TLS Diffie-Hellman parameters to match those used by
18420 - Update to the February 1 2011 Maxmind GeoLite Country database.
18423 - Check for and reject overly long directory certificates and
18424 directory tokens before they have a chance to hit any assertions.
18425 Bugfix on 0.2.1.28. Found by "doorss".
18426 - Bring the logic that gathers routerinfos and assesses the
18427 acceptability of circuits into line. This prevents a Tor OP from
18428 getting locked in a cycle of choosing its local OR as an exit for a
18429 path (due to a .exit request) and then rejecting the circuit because
18430 its OR is not listed yet. It also prevents Tor clients from using an
18431 OR running in the same instance as an exit (due to a .exit request)
18432 if the OR does not meet the same requirements expected of an OR
18433 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
18435 o Packaging changes:
18436 - Stop shipping the Tor specs files and development proposal documents
18437 in the tarball. They are now in a separate git repository at
18438 git://git.torproject.org/torspec.git
18439 - Do not include Git version tags as though they are SVN tags when
18440 generating a tarball from inside a repository that has switched
18441 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
18444 Changes in version 0.2.2.22-alpha - 2011-01-25
18445 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
18446 main other change is a slight tweak to Tor's TLS handshake that makes
18447 relays and bridges that run this new version reachable from Iran again.
18448 We don't expect this tweak will win the arms race long-term, but it
18449 will buy us a bit more time until we roll out a better solution.
18452 - Fix a bounds-checking error that could allow an attacker to
18453 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
18454 Found by "piebeer".
18455 - Don't assert when changing from bridge to relay or vice versa
18456 via the controller. The assert happened because we didn't properly
18457 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
18458 bug 2433. Reported by bastik.
18461 - Adjust our TLS Diffie-Hellman parameters to match those used by
18463 - Provide a log message stating which geoip file we're parsing
18464 instead of just stating that we're parsing the geoip file.
18465 Implements ticket 2432.
18468 - Check for and reject overly long directory certificates and
18469 directory tokens before they have a chance to hit any assertions.
18470 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
18473 Changes in version 0.2.2.21-alpha - 2011-01-15
18474 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
18475 continues our recent code security audit work. The main fix resolves
18476 a remote heap overflow vulnerability that can allow remote code
18477 execution (CVE-2011-0427). Other fixes address a variety of assert
18478 and crash bugs, most of which we think are hard to exploit remotely.
18480 o Major bugfixes (security), also included in 0.2.1.29:
18481 - Fix a heap overflow bug where an adversary could cause heap
18482 corruption. This bug probably allows remote code execution
18483 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
18485 - Prevent a denial-of-service attack by disallowing any
18486 zlib-compressed data whose compression factor is implausibly
18487 high. Fixes part of bug 2324; reported by "doorss".
18488 - Zero out a few more keys in memory before freeing them. Fixes
18489 bug 2384 and part of bug 2385. These key instances found by
18490 "cypherpunks", based on Andrew Case's report about being able
18491 to find sensitive data in Tor's memory space if you have enough
18492 permissions. Bugfix on 0.0.2pre9.
18494 o Major bugfixes (crashes), also included in 0.2.1.29:
18495 - Prevent calls to Libevent from inside Libevent log handlers.
18496 This had potential to cause a nasty set of crashes, especially
18497 if running Libevent with debug logging enabled, and running
18498 Tor with a controller watching for low-severity log messages.
18499 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
18500 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
18501 underflow errors there too. Fixes the other part of bug 2324.
18502 - Fix a bug where we would assert if we ever had a
18503 cached-descriptors.new file (or another file read directly into
18504 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
18505 on 0.2.1.25. Found by doorss.
18506 - Fix some potential asserts and parsing issues with grossly
18507 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
18510 o Minor bugfixes (other), also included in 0.2.1.29:
18511 - Fix a bug with handling misformed replies to reverse DNS lookup
18512 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
18513 bug reported by doorss.
18514 - Fix compilation on mingw when a pthreads compatibility library
18515 has been installed. (We don't want to use it, so we shouldn't
18516 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
18517 - Fix a bug where we would declare that we had run out of virtual
18518 addresses when the address space was only half-exhausted. Bugfix
18520 - Correctly handle the case where AutomapHostsOnResolve is set but
18521 no virtual addresses are available. Fixes bug 2328; bugfix on
18522 0.1.2.1-alpha. Bug found by doorss.
18523 - Correctly handle wrapping around when we run out of virtual
18524 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
18526 o Minor features, also included in 0.2.1.29:
18527 - Update to the January 1 2011 Maxmind GeoLite Country database.
18528 - Introduce output size checks on all of our decryption functions.
18530 o Build changes, also included in 0.2.1.29:
18531 - Tor does not build packages correctly with Automake 1.6 and earlier;
18532 added a check to Makefile.am to make sure that we're building with
18533 Automake 1.7 or later.
18534 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
18535 because we built it with a too-old version of automake. Thus that
18536 release broke ./configure --enable-openbsd-malloc, which is popular
18537 among really fast exit relays on Linux.
18539 o Major bugfixes, new in 0.2.2.21-alpha:
18540 - Prevent crash/heap corruption when the cbtnummodes consensus
18541 parameter is set to 0 or large values. Fixes bug 2317; bugfix
18544 o Major features, new in 0.2.2.21-alpha:
18545 - Introduce minimum/maximum values that clients will believe
18546 from the consensus. Now we'll have a better chance to avoid crashes
18547 or worse when a consensus param has a weird value.
18549 o Minor features, new in 0.2.2.21-alpha:
18550 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
18551 used on bridges, and it makes bridge scanning somewhat easier.
18552 - If writing the state file to disk fails, wait up to an hour before
18553 retrying again, rather than trying again each second. Fixes bug
18554 2346; bugfix on Tor 0.1.1.3-alpha.
18555 - Make Libevent log messages get delivered to controllers later,
18556 and not from inside the Libevent log handler. This prevents unsafe
18557 reentrant Libevent calls while still letting the log messages
18559 - Detect platforms that brokenly use a signed size_t, and refuse to
18560 build there. Found and analyzed by doorss and rransom.
18561 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
18564 o Minor bugfixes, new in 0.2.2.21-alpha:
18565 - Handle SOCKS messages longer than 128 bytes long correctly, rather
18566 than waiting forever for them to finish. Fixes bug 2330; bugfix
18567 on 0.2.0.16-alpha. Found by doorss.
18568 - Add assertions to check for overflow in arguments to
18569 base32_encode() and base32_decode(); fix a signed-unsigned
18570 comparison there too. These bugs are not actually reachable in Tor,
18571 but it's good to prevent future errors too. Found by doorss.
18572 - Correctly detect failures to create DNS requests when using Libevent
18573 versions before v2. (Before Libevent 2, we used our own evdns
18574 implementation. Its return values for Libevent's evdns_resolve_*()
18575 functions are not consistent with those from Libevent.) Fixes bug
18576 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
18578 o Documentation, new in 0.2.2.21-alpha:
18579 - Document the default socks host and port (127.0.0.1:9050) for
18583 Changes in version 0.2.1.29 - 2011-01-15
18584 Tor 0.2.1.29 continues our recent code security audit work. The main
18585 fix resolves a remote heap overflow vulnerability that can allow remote
18586 code execution. Other fixes address a variety of assert and crash bugs,
18587 most of which we think are hard to exploit remotely.
18589 o Major bugfixes (security):
18590 - Fix a heap overflow bug where an adversary could cause heap
18591 corruption. This bug probably allows remote code execution
18592 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
18594 - Prevent a denial-of-service attack by disallowing any
18595 zlib-compressed data whose compression factor is implausibly
18596 high. Fixes part of bug 2324; reported by "doorss".
18597 - Zero out a few more keys in memory before freeing them. Fixes
18598 bug 2384 and part of bug 2385. These key instances found by
18599 "cypherpunks", based on Andrew Case's report about being able
18600 to find sensitive data in Tor's memory space if you have enough
18601 permissions. Bugfix on 0.0.2pre9.
18603 o Major bugfixes (crashes):
18604 - Prevent calls to Libevent from inside Libevent log handlers.
18605 This had potential to cause a nasty set of crashes, especially
18606 if running Libevent with debug logging enabled, and running
18607 Tor with a controller watching for low-severity log messages.
18608 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
18609 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
18610 underflow errors there too. Fixes the other part of bug 2324.
18611 - Fix a bug where we would assert if we ever had a
18612 cached-descriptors.new file (or another file read directly into
18613 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
18614 on 0.2.1.25. Found by doorss.
18615 - Fix some potential asserts and parsing issues with grossly
18616 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
18619 o Minor bugfixes (other):
18620 - Fix a bug with handling misformed replies to reverse DNS lookup
18621 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
18622 bug reported by doorss.
18623 - Fix compilation on mingw when a pthreads compatibility library
18624 has been installed. (We don't want to use it, so we shouldn't
18625 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
18626 - Fix a bug where we would declare that we had run out of virtual
18627 addresses when the address space was only half-exhausted. Bugfix
18629 - Correctly handle the case where AutomapHostsOnResolve is set but
18630 no virtual addresses are available. Fixes bug 2328; bugfix on
18631 0.1.2.1-alpha. Bug found by doorss.
18632 - Correctly handle wrapping around to when we run out of virtual
18633 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
18634 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
18635 because we built it with a too-old version of automake. Thus that
18636 release broke ./configure --enable-openbsd-malloc, which is popular
18637 among really fast exit relays on Linux.
18640 - Update to the January 1 2011 Maxmind GeoLite Country database.
18641 - Introduce output size checks on all of our decryption functions.
18644 - Tor does not build packages correctly with Automake 1.6 and earlier;
18645 added a check to Makefile.am to make sure that we're building with
18646 Automake 1.7 or later.
18649 Changes in version 0.2.2.20-alpha - 2010-12-17
18650 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
18651 exploitable bugs. We also fix a variety of other significant bugs,
18652 change the IP address for one of our directory authorities, and update
18653 the minimum version that Tor relays must run to join the network.
18656 - Fix a remotely exploitable bug that could be used to crash instances
18657 of Tor remotely by overflowing on the heap. Remote-code execution
18658 hasn't been confirmed, but can't be ruled out. Everyone should
18659 upgrade. Bugfix on the 0.1.1 series and later.
18660 - Fix a bug that could break accounting on 64-bit systems with large
18661 time_t values, making them hibernate for impossibly long intervals.
18662 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
18663 - Fix a logic error in directory_fetches_from_authorities() that
18664 would cause all _non_-exits refusing single-hop-like circuits
18665 to fetch from authorities, when we wanted to have _exits_ fetch
18666 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
18668 - Fix a stream fairness bug that would cause newer streams on a given
18669 circuit to get preference when reading bytes from the origin or
18670 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
18671 introduced before the first Tor release, in svn revision r152.
18673 o Directory authority changes:
18674 - Change IP address and ports for gabelmoo (v3 directory authority).
18677 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
18678 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
18679 - Fix an off-by-one error in calculating some controller command
18680 argument lengths. Fortunately, this mistake is harmless since
18681 the controller code does redundant NUL termination too. Found by
18682 boboper. Bugfix on 0.1.1.1-alpha.
18683 - Do not dereference NULL if a bridge fails to build its
18684 extra-info descriptor. Found by an anonymous commenter on
18685 Trac. Bugfix on 0.2.2.19-alpha.
18688 - Update to the December 1 2010 Maxmind GeoLite Country database.
18689 - Directory authorities now reject relays running any versions of
18690 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
18691 known bugs that keep RELAY_EARLY cells from working on rendezvous
18692 circuits. Followup to fix for bug 2081.
18693 - Directory authorities now reject relays running any version of Tor
18694 older than 0.2.0.26-rc. That version is the earliest that fetches
18695 current directory information correctly. Fixes bug 2156.
18696 - Report only the top 10 ports in exit-port stats in order not to
18697 exceed the maximum extra-info descriptor length of 50 KB. Implements
18701 Changes in version 0.2.1.28 - 2010-12-17
18702 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
18703 exploitable bugs. We also took this opportunity to change the IP address
18704 for one of our directory authorities, and to update the geoip database
18708 - Fix a remotely exploitable bug that could be used to crash instances
18709 of Tor remotely by overflowing on the heap. Remote-code execution
18710 hasn't been confirmed, but can't be ruled out. Everyone should
18711 upgrade. Bugfix on the 0.1.1 series and later.
18713 o Directory authority changes:
18714 - Change IP address and ports for gabelmoo (v3 directory authority).
18717 - Update to the December 1 2010 Maxmind GeoLite Country database.
18720 Changes in version 0.2.1.27 - 2010-11-23
18721 Yet another OpenSSL security patch broke its compatibility with Tor:
18722 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
18723 also took this opportunity to fix several crash bugs, integrate a new
18724 directory authority, and update the bundled GeoIP database.
18727 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
18728 No longer set the tlsext_host_name extension on server SSL objects;
18729 but continue to set it on client SSL objects. Our goal in setting
18730 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
18731 bugfix on 0.2.1.1-alpha.
18732 - Do not log messages to the controller while shrinking buffer
18733 freelists. Doing so would sometimes make the controller connection
18734 try to allocate a buffer chunk, which would mess up the internals
18735 of the freelist and cause an assertion failure. Fixes bug 1125;
18736 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
18737 - Learn our external IP address when we're a relay or bridge, even if
18738 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
18739 where we introduced bridge relays that don't need to publish to
18740 be useful. Fixes bug 2050.
18741 - Do even more to reject (and not just ignore) annotations on
18742 router descriptors received anywhere but from the cache. Previously
18743 we would ignore such annotations at first, but cache them to disk
18744 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
18745 - When you're using bridges and your network goes away and your
18746 bridges get marked as down, recover when you attempt a new socks
18747 connection (if the network is back), rather than waiting up to an
18748 hour to try fetching new descriptors for your bridges. Bugfix on
18749 0.2.0.3-alpha; fixes bug 1981.
18752 - Move to the November 2010 Maxmind GeoLite country db (rather
18753 than the June 2009 ip-to-country GeoIP db) for our statistics that
18754 count how many users relays are seeing from each country. Now we'll
18755 have more accurate data, especially for many African countries.
18757 o New directory authorities:
18758 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
18762 - Fix an assertion failure that could occur in directory caches or
18763 bridge users when using a very short voting interval on a testing
18764 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
18766 - Enforce multiplicity rules when parsing annotations. Bugfix on
18767 0.2.0.8-alpha. Found by piebeer.
18768 - Allow handshaking OR connections to take a full KeepalivePeriod
18769 seconds to handshake. Previously, we would close them after
18770 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
18771 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
18773 - When building with --enable-gcc-warnings on OpenBSD, disable
18774 warnings in system headers. This makes --enable-gcc-warnings
18775 pass on OpenBSD 4.8.
18778 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
18779 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
18780 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
18781 Servers can start sending this code when enough clients recognize
18782 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
18783 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
18784 Patch from mingw-san.
18787 - Remove the old debian/ directory from the main Tor distribution.
18788 The official Tor-for-debian git repository lives at the URL
18789 https://git.torproject.org/debian/tor.git
18790 - Stop shipping the old doc/website/ directory in the tarball. We
18791 changed the website format in late 2010, and what we shipped in
18792 0.2.1.26 really wasn't that useful anyway.
18795 Changes in version 0.2.2.19-alpha - 2010-11-22
18796 Yet another OpenSSL security patch broke its compatibility with Tor:
18797 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
18800 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
18801 No longer set the tlsext_host_name extension on server SSL objects;
18802 but continue to set it on client SSL objects. Our goal in setting
18803 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
18804 bugfix on 0.2.1.1-alpha.
18807 - Try harder not to exceed the maximum length of 50 KB when writing
18808 statistics to extra-info descriptors. This bug was triggered by very
18809 fast relays reporting exit-port, entry, and dirreq statistics.
18810 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
18811 - Publish a router descriptor even if generating an extra-info
18812 descriptor fails. Previously we would not publish a router
18813 descriptor without an extra-info descriptor; this can cause fast
18814 exit relays collecting exit-port statistics to drop from the
18815 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
18818 Changes in version 0.2.2.18-alpha - 2010-11-16
18819 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
18820 us lately, makes unpublished bridge relays able to detect their IP
18821 address, and fixes a wide variety of other bugs to get us much closer
18822 to a stable release.
18825 - Do even more to reject (and not just ignore) annotations on
18826 router descriptors received anywhere but from the cache. Previously
18827 we would ignore such annotations at first, but cache them to disk
18828 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
18829 - Do not log messages to the controller while shrinking buffer
18830 freelists. Doing so would sometimes make the controller connection
18831 try to allocate a buffer chunk, which would mess up the internals
18832 of the freelist and cause an assertion failure. Fixes bug 1125;
18833 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
18834 - Learn our external IP address when we're a relay or bridge, even if
18835 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
18836 where we introduced bridge relays that don't need to publish to
18837 be useful. Fixes bug 2050.
18838 - Maintain separate TLS contexts and certificates for incoming and
18839 outgoing connections in bridge relays. Previously we would use the
18840 same TLS contexts and certs for incoming and outgoing connections.
18841 Bugfix on 0.2.0.3-alpha; addresses bug 988.
18842 - Maintain separate identity keys for incoming and outgoing TLS
18843 contexts in bridge relays. Previously we would use the same
18844 identity keys for incoming and outgoing TLS contexts. Bugfix on
18845 0.2.0.3-alpha; addresses the other half of bug 988.
18846 - Avoid an assertion failure when we as an authority receive a
18847 duplicate upload of a router descriptor that we already have,
18848 but which we previously considered an obsolete descriptor.
18849 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
18850 - Avoid a crash bug triggered by looking at a dangling pointer while
18851 setting the network status consensus. Found by Robert Ransom.
18852 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
18853 - Fix a logic error where servers that _didn't_ act as exits would
18854 try to keep their server lists more aggressively up to date than
18855 exits, when it was supposed to be the other way around. Bugfix
18858 o Minor bugfixes (on Tor 0.2.1.x and earlier):
18859 - When we're trying to guess whether we know our IP address as
18860 a relay, we would log various ways that we failed to guess
18861 our address, but never log that we ended up guessing it
18862 successfully. Now add a log line to help confused and anxious
18863 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
18864 - Bring the logic that gathers routerinfos and assesses the
18865 acceptability of circuits into line. This prevents a Tor OP from
18866 getting locked in a cycle of choosing its local OR as an exit for a
18867 path (due to a .exit request) and then rejecting the circuit because
18868 its OR is not listed yet. It also prevents Tor clients from using an
18869 OR running in the same instance as an exit (due to a .exit request)
18870 if the OR does not meet the same requirements expected of an OR
18871 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
18872 - Correctly describe errors that occur when generating a TLS object.
18873 Previously we would attribute them to a failure while generating a
18874 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
18876 - Enforce multiplicity rules when parsing annotations. Bugfix on
18877 0.2.0.8-alpha. Found by piebeer.
18878 - Fix warnings that newer versions of autoconf produced during
18879 ./autogen.sh. These warnings appear to be harmless in our case,
18880 but they were extremely verbose. Fixes bug 2020.
18882 o Minor bugfixes (on Tor 0.2.2.x):
18883 - Enable protection of small arrays whenever we build with gcc
18884 hardening features, not only when also building with warnings
18885 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
18888 - Make hidden services work better in private Tor networks by not
18889 requiring any uptime to join the hidden service descriptor
18890 DHT. Implements ticket 2088.
18891 - Rate-limit the "your application is giving Tor only an IP address"
18892 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
18893 - When AllowSingleHopExits is set, print a warning to explain to the
18894 relay operator why most clients are avoiding her relay.
18895 - Update to the November 1 2010 Maxmind GeoLite Country database.
18897 o Code simplifications and refactoring:
18898 - When we fixed bug 1038 we had to put in a restriction not to send
18899 RELAY_EARLY cells on rend circuits. This was necessary as long
18900 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
18901 active. Now remove this obsolete check. Resolves bug 2081.
18902 - Some options used different conventions for uppercasing of acronyms
18903 when comparing manpage and source. Fix those in favor of the
18904 manpage, as it makes sense to capitalize acronyms.
18905 - Remove the torrc.complete file. It hasn't been kept up to date
18906 and users will have better luck checking out the manpage.
18907 - Remove the obsolete "NoPublish" option; it has been flagged
18908 as obsolete and has produced a warning since 0.1.1.18-rc.
18909 - Remove everything related to building the expert bundle for OS X.
18910 It has confused many users, doesn't work right on OS X 10.6,
18911 and is hard to get rid of once installed. Resolves bug 1274.
18914 Changes in version 0.2.2.17-alpha - 2010-09-30
18915 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
18916 to use one-hop circuits (which can put the exit relays at higher risk,
18917 plus unbalance the network); fixes a big bug in bandwidth accounting
18918 for relays that want to limit their monthly bandwidth use; fixes a
18919 big pile of bugs in how clients tolerate temporary network failure;
18920 and makes our adaptive circuit build timeout feature (which improves
18921 client performance if your network is fast while not breaking things
18922 if your network is slow) better handle bad networks.
18925 - Exit relays now try harder to block exit attempts from unknown
18926 relays, to make it harder for people to use them as one-hop proxies
18927 a la tortunnel. Controlled by the refuseunknownexits consensus
18928 parameter (currently enabled), or you can override it on your
18929 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
18931 o Major bugfixes (0.2.1.x and earlier):
18932 - Fix a bug in bandwidth accounting that could make us use twice
18933 the intended bandwidth when our interval start changes due to
18934 daylight saving time. Now we tolerate skew in stored vs computed
18935 interval starts: if the start of the period changes by no more than
18936 50% of the period's duration, we remember bytes that we transferred
18937 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
18938 - Always search the Windows system directory for system DLLs, and
18939 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
18940 - When you're using bridges and your network goes away and your
18941 bridges get marked as down, recover when you attempt a new socks
18942 connection (if the network is back), rather than waiting up to an
18943 hour to try fetching new descriptors for your bridges. Bugfix on
18944 0.2.0.3-alpha; fixes bug 1981.
18946 o Major bugfixes (on 0.2.2.x):
18947 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
18949 - Fix a segfault that could happen when operating a bridge relay with
18950 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
18951 - The consensus bandwidth-weights (used by clients to choose fast
18952 relays) entered an unexpected edge case in September where
18953 Exits were much scarcer than Guards, resulting in bad weight
18954 recommendations. Now we compute them using new constraints that
18955 should succeed in all cases. Also alter directory authorities to
18956 not include the bandwidth-weights line if they fail to produce
18957 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
18958 - When weighting bridges during path selection, we used to trust
18959 the bandwidths they provided in their descriptor, only capping them
18960 at 10MB/s. This turned out to be problematic for two reasons:
18961 Bridges could claim to handle a lot more traffic then they
18962 actually would, thus making more clients pick them and have a
18963 pretty effective DoS attack. The other issue is that new bridges
18964 that might not have a good estimate for their bw capacity yet
18965 would not get used at all unless no other bridges are available
18966 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
18968 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
18969 - Ignore cannibalized circuits when recording circuit build times.
18970 This should provide for a minor performance improvement for hidden
18971 service users using 0.2.2.14-alpha, and should remove two spurious
18972 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
18973 - Simplify the logic that causes us to decide if the network is
18974 unavailable for purposes of recording circuit build times. If we
18975 receive no cells whatsoever for the entire duration of a circuit's
18976 full measured lifetime, the network is probably down. Also ignore
18977 one-hop directory fetching circuit timeouts when calculating our
18978 circuit build times. These changes should hopefully reduce the
18979 cases where we see ridiculous circuit build timeouts for people
18980 with spotty wireless connections. Fixes part of bug 1772; bugfix
18982 - Prevent the circuit build timeout from becoming larger than
18983 the maximum build time we have ever seen. Also, prevent the time
18984 period for measurement circuits from becoming larger than twice that
18985 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
18988 - When we run out of directory information such that we can't build
18989 circuits, but then get enough that we can build circuits, log when
18990 we actually construct a circuit, so the user has a better chance of
18991 knowing what's going on. Fixes bug 1362.
18992 - Be more generous with how much bandwidth we'd use up (with
18993 accounting enabled) before entering "soft hibernation". Previously,
18994 we'd refuse new connections and circuits once we'd used up 95% of
18995 our allotment. Now, we use up 95% of our allotment, AND make sure
18996 that we have no more than 500MB (or 3 hours of expected traffic,
18997 whichever is lower) remaining before we enter soft hibernation.
18998 - If we've configured EntryNodes and our network goes away and/or all
18999 our entrynodes get marked down, optimistically retry them all when
19000 a new socks application request appears. Fixes bug 1882.
19001 - Add some more defensive programming for architectures that can't
19002 handle unaligned integer accesses. We don't know of any actual bugs
19003 right now, but that's the best time to fix them. Fixes bug 1943.
19004 - Support line continuations in the torrc config file. If a line
19005 ends with a single backslash character, the newline is ignored, and
19006 the configuration value is treated as continuing on the next line.
19009 o Minor bugfixes (on 0.2.1.x and earlier):
19010 - For bandwidth accounting, calculate our expected bandwidth rate
19011 based on the time during which we were active and not in
19012 soft-hibernation during the last interval. Previously, we were
19013 also considering the time spent in soft-hibernation. If this
19014 was a long time, we would wind up underestimating our bandwidth
19015 by a lot, and skewing our wakeup time towards the start of the
19016 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
19018 o Minor bugfixes (on 0.2.2.x):
19019 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
19020 which were disabled by the circuit build timeout changes in
19021 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
19022 - Make sure we don't warn about missing bandwidth weights when
19023 choosing bridges or other relays not in the consensus. Bugfix on
19024 0.2.2.10-alpha; fixes bug 1805.
19025 - In our logs, do not double-report signatures from unrecognized
19026 authorities both as "from unknown authority" and "not
19027 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
19030 Changes in version 0.2.2.16-alpha - 2010-09-17
19031 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
19032 evident at exit relays), and also continues to resolve all the little
19033 bugs that have been filling up trac lately.
19035 o Major bugfixes (stream-level fairness):
19036 - When receiving a circuit-level SENDME for a blocked circuit, try
19037 to package cells fairly from all the streams that had previously
19038 been blocked on that circuit. Previously, we had started with the
19039 oldest stream, and allowed each stream to potentially exhaust
19040 the circuit's package window. This gave older streams on any
19041 given circuit priority over newer ones. Fixes bug 1937. Detected
19042 originally by Camilo Viecco. This bug was introduced before the
19043 first Tor release, in svn commit r152: it is the new winner of
19044 the longest-lived bug prize.
19045 - When the exit relay got a circuit-level sendme cell, it started
19046 reading on the exit streams, even if had 500 cells queued in the
19047 circuit queue already, so the circuit queue just grew and grew in
19048 some cases. We fix this by not re-enabling reading on receipt of a
19049 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
19050 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
19052 - Newly created streams were allowed to read cells onto circuits,
19053 even if the circuit's cell queue was blocked and waiting to drain.
19054 This created potential unfairness, as older streams would be
19055 blocked, but newer streams would gladly fill the queue completely.
19056 We add code to detect this situation and prevent any stream from
19057 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
19061 - Update to the September 1 2010 Maxmind GeoLite Country database.
19062 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
19063 not. This would lead to a cookie that is still not group readable.
19064 Closes bug 1843. Suggested by katmagic.
19065 - When logging a rate-limited warning, we now mention how many messages
19066 got suppressed since the last warning.
19067 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
19068 do individual connection-level rate limiting of clients. The torrc
19069 config options with the same names trump the consensus params, if
19070 both are present. Replaces the old "bwconnrate" and "bwconnburst"
19071 consensus params which were broken from 0.2.2.7-alpha through
19072 0.2.2.14-alpha. Closes bug 1947.
19073 - When a router changes IP address or port, authorities now launch
19074 a new reachability test for it. Implements ticket 1899.
19075 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
19076 2 no signature, 4 required" messages about consensus signatures
19077 easier to read, and make sure they get logged at the same severity
19078 as the messages explaining which keys are which. Fixes bug 1290.
19079 - Don't warn when we have a consensus that we can't verify because
19080 of missing certificates, unless those certificates are ones
19081 that we have been trying and failing to download. Fixes bug 1145.
19082 - If you configure your bridge with a known identity fingerprint,
19083 and the bridge authority is unreachable (as it is in at least
19084 one country now), fall back to directly requesting the descriptor
19085 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
19087 - When building with --enable-gcc-warnings on OpenBSD, disable
19088 warnings in system headers. This makes --enable-gcc-warnings
19089 pass on OpenBSD 4.8.
19091 o Minor bugfixes (on 0.2.1.x and earlier):
19092 - Authorities will now attempt to download consensuses if their
19093 own efforts to make a live consensus have failed. This change
19094 means authorities that restart will fetch a valid consensus, and
19095 it means authorities that didn't agree with the current consensus
19096 will still fetch and serve it if it has enough signatures. Bugfix
19097 on 0.2.0.9-alpha; fixes bug 1300.
19098 - Ensure DNS requests launched by "RESOLVE" commands from the
19099 controller respect the __LeaveStreamsUnattached setconf options. The
19100 same goes for requests launched via DNSPort or transparent
19101 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
19102 - Allow handshaking OR connections to take a full KeepalivePeriod
19103 seconds to handshake. Previously, we would close them after
19104 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
19105 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
19107 - Rate-limit "Failed to hand off onionskin" warnings.
19108 - Never relay a cell for a circuit we have already destroyed.
19109 Between marking a circuit as closeable and finally closing it,
19110 it may have been possible for a few queued cells to get relayed,
19111 even though they would have been immediately dropped by the next
19112 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
19113 - Never queue a cell for a circuit that's already been marked
19115 - Never vote for a server as "Running" if we have a descriptor for
19116 it claiming to be hibernating, and that descriptor was published
19117 more recently than our last contact with the server. Bugfix on
19118 0.2.0.3-alpha; fixes bug 911.
19119 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
19122 o Minor bugfixes (on 0.2.2.x):
19123 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
19124 down if a directory fetch fails and you've configured either
19125 bridges or EntryNodes. The intent was to mark the relay as down
19126 _unless_ you're using bridges or EntryNodes, since if you are
19127 then you could quickly run out of entry points.
19128 - Fix the Windows directory-listing code. A bug introduced in
19129 0.2.2.14-alpha could make Windows directory servers forget to load
19130 some of their cached v2 networkstatus files.
19131 - Really allow clients to use relays as bridges. Fixes bug 1776;
19132 bugfix on 0.2.2.15-alpha.
19133 - Demote a warn to info that happens when the CellStatistics option
19134 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
19135 Reported by Moritz Bartl.
19136 - On Windows, build correctly either with or without Unicode support.
19137 This is necessary so that Tor can support fringe platforms like
19138 Windows 98 (which has no Unicode), or Windows CE (which has no
19139 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
19142 - Add a unit test for cross-platform directory-listing code.
19145 Changes in version 0.2.2.15-alpha - 2010-08-18
19146 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
19147 fixes a variety of other bugs that were preventing performance
19148 experiments from moving forward, fixes several bothersome memory leaks,
19149 and generally closes a lot of smaller bugs that have been filling up
19153 - Stop assigning the HSDir flag to relays that disable their
19154 DirPort (and thus will refuse to answer directory requests). This
19155 fix should dramatically improve the reachability of hidden services:
19156 hidden services and hidden service clients pick six HSDir relays
19157 to store and retrieve the hidden service descriptor, and currently
19158 about half of the HSDir relays will refuse to work. Bugfix on
19159 0.2.0.10-alpha; fixes part of bug 1693.
19160 - The PerConnBWRate and Burst config options, along with the
19161 bwconnrate and bwconnburst consensus params, initialized each conn's
19162 token bucket values only when the connection is established. Now we
19163 update them if the config options change, and update them every time
19164 we get a new consensus. Otherwise we can encounter an ugly edge
19165 case where we initialize an OR conn to client-level bandwidth,
19166 but then later the relay joins the consensus and we leave it
19167 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
19168 - Fix a regression that caused Tor to rebind its ports if it receives
19169 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
19172 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
19173 should give us approximately 40-50% more Guard-flagged nodes,
19174 improving the anonymity the Tor network can provide and also
19175 decreasing the dropoff in throughput that relays experience when
19176 they first get the Guard flag.
19177 - Allow enabling or disabling the *Statistics config options while
19181 - Update to the August 1 2010 Maxmind GeoLite Country database.
19182 - Have the controller interface give a more useful message than
19183 "Internal Error" in response to failed GETINFO requests.
19184 - Warn when the same option is provided more than once in a torrc
19185 file, on the command line, or in a single SETCONF statement, and
19186 the option is one that only accepts a single line. Closes bug 1384.
19187 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
19188 Patch from mingw-san.
19189 - Add support for the country code "{??}" in torrc options like
19190 ExcludeNodes, to indicate all routers of unknown country. Closes
19192 - Relays report the number of bytes spent on answering directory
19193 requests in extra-info descriptors similar to {read,write}-history.
19194 Implements enhancement 1790.
19196 o Minor bugfixes (on 0.2.1.x and earlier):
19197 - Complain if PublishServerDescriptor is given multiple arguments that
19198 include 0 or 1. This configuration will be rejected in the future.
19199 Bugfix on 0.2.0.1-alpha; closes bug 1107.
19200 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
19201 Bugfix on 0.2.0.13-alpha; closes bug 928.
19202 - Change "Application request when we're believed to be offline."
19203 notice to "Application request when we haven't used client
19204 functionality lately.", to clarify that it's not an error. Bugfix
19205 on 0.0.9.3; fixes bug 1222.
19206 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
19207 would return "551 Internal error" rather than "552 Unrecognized key
19208 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
19209 - Users can't configure a regular relay to be their bridge. It didn't
19210 work because when Tor fetched the bridge descriptor, it found
19211 that it already had it, and didn't realize that the purpose of the
19212 descriptor had changed. Now we replace routers with a purpose other
19213 than bridge with bridge descriptors when fetching them. Bugfix on
19214 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
19215 refetch the descriptor with router purpose 'general', disabling
19217 - Fix a rare bug in rend_fn unit tests: we would fail a test when
19218 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
19219 on 0.2.0.10-alpha; fixes bug 1808.
19220 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
19221 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
19222 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
19223 Servers can start sending this code when enough clients recognize
19224 it. Also update the spec to reflect this new reason. Bugfix on
19225 0.1.0.1-rc; fixes part of bug 1793.
19226 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
19227 when we switch from being a public relay to a bridge. Otherwise
19228 there will still be clients that see the relay in their consensus,
19229 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
19231 - Instead of giving an assertion failure on an internal mismatch
19232 on estimated freelist size, just log a BUG warning and try later.
19233 Mitigates but does not fix bug 1125.
19234 - Fix an assertion failure that could occur in caches or bridge users
19235 when using a very short voting interval on a testing network.
19236 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
19238 o Minor bugfixes (on 0.2.2.x):
19239 - Alter directory authorities to always consider Exit-flagged nodes
19240 as potential Guard nodes in their votes. The actual decision to
19241 use Exits as Guards is done in the consensus bandwidth weights.
19242 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
19243 - When the controller is reporting the purpose of circuits that
19244 didn't finish building before the circuit build timeout, it was
19245 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
19246 - Our libevent version parsing code couldn't handle versions like
19247 1.4.14b-stable and incorrectly warned the user about using an
19248 old and broken version of libevent. Treat 1.4.14b-stable like
19249 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
19251 - Don't use substitution references like $(VAR:MOD) when
19252 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
19253 '$(:x)' to 'x' rather than the empty string. This bites us in
19254 doc/ when configured with --disable-asciidoc. Bugfix on
19255 0.2.2.9-alpha; fixes bug 1773.
19256 - Remove a spurious hidden service server-side log notice about
19257 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
19259 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
19261 - Correctly report written bytes on linked connections. Found while
19262 implementing 1790. Bugfix on 0.2.2.4-alpha.
19263 - Fix three memory leaks: one in circuit_build_times_parse_state(),
19264 one in dirvote_add_signatures_to_pending_consensus(), and one every
19265 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
19266 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
19268 o Code simplifications and refactoring:
19269 - Take a first step towards making or.h smaller by splitting out
19270 function definitions for all source files in src/or/. Leave
19271 structures and defines in or.h for now.
19272 - Remove a bunch of unused function declarations as well as a block of
19273 #if 0'd code from the unit tests. Closes bug 1824.
19274 - New unit tests for exit-port history statistics; refactored exit
19275 statistics code to be more easily tested.
19276 - Remove the old debian/ directory from the main Tor distribution.
19277 The official Tor-for-debian git repository lives at the URL
19278 https://git.torproject.org/debian/tor.git
19281 Changes in version 0.2.2.14-alpha - 2010-07-12
19282 Tor 0.2.2.14-alpha greatly improves client-side handling of
19283 circuit build timeouts, which are used to estimate speed and improve
19284 performance. We also move to a much better GeoIP database, port Tor to
19285 Windows CE, introduce new compile flags that improve code security,
19286 add an eighth v3 directory authority, and address a lot of more
19290 - Tor directory authorities no longer crash when started with a
19291 cached-microdesc-consensus file in their data directory. Bugfix
19292 on 0.2.2.6-alpha; fixes bug 1532.
19293 - Treat an unset $HOME like an empty $HOME rather than triggering an
19294 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
19295 - Ignore negative and large circuit build timeout values that can
19296 happen during a suspend or hibernate. These values caused various
19297 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
19298 - Alter calculation of Pareto distribution parameter 'Xm' for
19299 Circuit Build Timeout learning to use the weighted average of the
19300 top N=3 modes (because we have three entry guards). Considering
19301 multiple modes should improve the timeout calculation in some cases,
19302 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
19304 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
19305 right censored distribution model. This approach improves over the
19306 synthetic timeout generation approach that was producing insanely
19307 high timeout values. Now we calculate build timeouts using truncated
19308 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
19309 - Do not close circuits that are under construction when they reach
19310 the circuit build timeout. Instead, leave them building (but do not
19311 use them) for up until the time corresponding to the 95th percentile
19312 on the Pareto CDF or 60 seconds, whichever is greater. This is done
19313 to provide better data for the new Pareto model. This percentile
19314 can be controlled by the consensus.
19317 - Move to the June 2010 Maxmind GeoLite country db (rather than the
19318 June 2009 ip-to-country GeoIP db) for our statistics that count
19319 how many users relays are seeing from each country. Now we have
19320 more accurate data for many African countries.
19321 - Port Tor to build and run correctly on Windows CE systems, using
19322 the wcecompat library. Contributed by Valerio Lupi.
19323 - New "--enable-gcc-hardening" ./configure flag (off by default)
19324 to turn on gcc compile time hardening options. It ensures
19325 that signed ints have defined behavior (-fwrapv), enables
19326 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
19327 with canaries (-fstack-protector-all), turns on ASLR protection if
19328 supported by the kernel (-fPIE, -pie), and adds additional security
19329 related warnings. Verified to work on Mac OS X and Debian Lenny.
19330 - New "--enable-linker-hardening" ./configure flag (off by default)
19331 to turn on ELF specific hardening features (relro, now). This does
19332 not work with Mac OS X or any other non-ELF binary format.
19334 o New directory authorities:
19335 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
19339 - New config option "WarnUnsafeSocks 0" disables the warning that
19340 occurs whenever Tor receives a socks handshake using a version of
19341 the socks protocol that can only provide an IP address (rather
19342 than a hostname). Setups that do DNS locally over Tor are fine,
19343 and we shouldn't spam the logs in that case.
19344 - Convert the HACKING file to asciidoc, and add a few new sections
19345 to it, explaining how we use Git, how we make changelogs, and
19346 what should go in a patch.
19347 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
19348 event, to give information on the current rate of circuit timeouts
19349 over our stored history.
19350 - Add ability to disable circuit build time learning via consensus
19351 parameter and via a LearnCircuitBuildTimeout config option. Also
19352 automatically disable circuit build time calculation if we are
19353 either a AuthoritativeDirectory, or if we fail to write our state
19354 file. Fixes bug 1296.
19355 - More gracefully handle corrupt state files, removing asserts
19356 in favor of saving a backup and resetting state.
19357 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
19361 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
19363 - When a2x fails, mention that the user could disable manpages instead
19364 of trying to fix their asciidoc installation.
19365 - Where available, use Libevent 2.0's periodic timers so that our
19366 once-per-second cleanup code gets called even more closely to
19367 once per second than it would otherwise. Fixes bug 943.
19368 - If you run a bridge that listens on multiple IP addresses, and
19369 some user configures a bridge address that uses a different IP
19370 address than your bridge writes in its router descriptor, and the
19371 user doesn't specify an identity key, their Tor would discard the
19372 descriptor because "it isn't one of our configured bridges", and
19373 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
19374 Bugfix on 0.2.0.3-alpha.
19375 - If OpenSSL fails to make a duplicate of a private or public key, log
19376 an error message and try to exit cleanly. May help with debugging
19377 if bug 1209 ever remanifests.
19378 - Save a couple bytes in memory allocation every time we escape
19379 certain characters in a string. Patch from Florian Zumbiehl.
19380 - Make it explicit that we don't cannibalize one-hop circuits. This
19381 happens in the wild, but doesn't turn out to be a problem because
19382 we fortunately don't use those circuits. Many thanks to outofwords
19383 for the initial analysis and to swissknife who confirmed that
19384 two-hop circuits are actually created.
19385 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
19386 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
19387 - Eliminate a case where a circuit build time warning was displayed
19388 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
19391 Changes in version 0.2.1.26 - 2010-05-02
19392 Tor 0.2.1.26 addresses the recent connection and memory overload
19393 problems we've been seeing on relays, especially relays with their
19394 DirPort open. If your relay has been crashing, or you turned it off
19395 because it used too many resources, give this release a try.
19397 This release also fixes yet another instance of broken OpenSSL libraries
19398 that was causing some relays to drop out of the consensus.
19401 - Teach relays to defend themselves from connection overload. Relays
19402 now close idle circuits early if it looks like they were intended
19403 for directory fetches. Relays are also more aggressive about closing
19404 TLS connections that have no circuits on them. Such circuits are
19405 unlikely to be re-used, and tens of thousands of them were piling
19406 up at the fast relays, causing the relays to run out of sockets
19407 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
19408 their directory fetches over TLS).
19409 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
19410 that claim to be earlier than 0.9.8m, but which have in reality
19411 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
19412 behavior. Possible fix for some cases of bug 1346.
19413 - Directory mirrors were fetching relay descriptors only from v2
19414 directory authorities, rather than v3 authorities like they should.
19415 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
19416 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
19419 - Finally get rid of the deprecated and now harmful notion of "clique
19420 mode", where directory authorities maintain TLS connections to
19424 - In the util/threads test, no longer free the test_mutex before all
19425 worker threads have finished. Bugfix on 0.2.1.6-alpha.
19426 - The master thread could starve the worker threads quite badly on
19427 certain systems, causing them to run only partially in the allowed
19428 window. This resulted in test failures. Now the master thread sleeps
19429 occasionally for a few microseconds while the two worker-threads
19430 compete for the mutex. Bugfix on 0.2.0.1-alpha.
19433 Changes in version 0.2.2.13-alpha - 2010-04-24
19434 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
19435 problems we've been seeing on relays, especially relays with their
19436 DirPort open. If your relay has been crashing, or you turned it off
19437 because it used too many resources, give this release a try.
19440 - Teach relays to defend themselves from connection overload. Relays
19441 now close idle circuits early if it looks like they were intended
19442 for directory fetches. Relays are also more aggressive about closing
19443 TLS connections that have no circuits on them. Such circuits are
19444 unlikely to be re-used, and tens of thousands of them were piling
19445 up at the fast relays, causing the relays to run out of sockets
19446 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
19447 their directory fetches over TLS).
19450 - Finally get rid of the deprecated and now harmful notion of "clique
19451 mode", where directory authorities maintain TLS connections to
19453 - Directory authorities now do an immediate reachability check as soon
19454 as they hear about a new relay. This change should slightly reduce
19455 the time between setting up a relay and getting listed as running
19456 in the consensus. It should also improve the time between setting
19457 up a bridge and seeing use by bridge users.
19458 - Directory authorities no longer launch a TLS connection to every
19459 relay as they startup. Now that we have 2k+ descriptors cached,
19460 the resulting network hiccup is becoming a burden. Besides,
19461 authorities already avoid voting about Running for the first half
19462 hour of their uptime.
19465 Changes in version 0.2.2.12-alpha - 2010-04-20
19466 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
19467 handle and vote on descriptors. It was causing relays to drop out of
19471 - Many relays have been falling out of the consensus lately because
19472 not enough authorities know about their descriptor for them to get
19473 a majority of votes. When we deprecated the v2 directory protocol,
19474 we got rid of the only way that v3 authorities can hear from each
19475 other about other descriptors. Now authorities examine every v3
19476 vote for new descriptors, and fetch them from that authority. Bugfix
19478 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
19479 and a warning in or.h related to bandwidth_weight_rule_t that
19480 prevented clean compile on OS X. Fixes bug 1363; bugfix on
19482 - Fix a segfault on relays when DirReqStatistics is enabled
19483 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
19487 - Demote a confusing TLS warning that relay operators might get when
19488 someone tries to talk to their OrPort. It is neither the operator's
19489 fault nor can they do anything about it. Fixes bug 1364; bugfix
19493 Changes in version 0.2.2.11-alpha - 2010-04-15
19494 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
19495 libraries that was causing some relays to drop out of the consensus.
19498 - Directory mirrors were fetching relay descriptors only from v2
19499 directory authorities, rather than v3 authorities like they should.
19500 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
19501 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
19502 - Fix a parsing error that made every possible value of
19503 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
19504 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
19505 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
19506 about the option without breaking older ones.
19507 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
19508 that claim to be earlier than 0.9.8m, but which have in reality
19509 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
19510 behavior. Possible fix for some cases of bug 1346.
19513 - Experiment with a more aggressive approach to preventing clients
19514 from making one-hop exit streams. Exit relays who want to try it
19515 out can set "RefuseUnknownExits 1" in their torrc, and then look
19516 for "Attempt by %s to open a stream" log messages. Let us know
19518 - Add support for statically linking zlib by specifying
19519 --enable-static-zlib, to go with our support for statically linking
19520 openssl and libevent. Resolves bug 1358.
19523 - Fix a segfault that happens whenever a Tor client that is using
19524 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
19526 - When we cleaned up the contrib/tor-exit-notice.html file, we left
19527 out the first line. Fixes bug 1295.
19528 - When building the manpage from a tarball, we required asciidoc, but
19529 the asciidoc -> roff/html conversion was already done for the
19530 tarball. Make 'make' complain only when we need asciidoc (either
19531 because we're compiling directly from git, or because we altered
19532 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
19533 - When none of the directory authorities vote on any params, Tor
19534 segfaulted when trying to make the consensus from the votes. We
19535 didn't trigger the bug in practice, because authorities do include
19536 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
19539 - In the util/threads test, no longer free the test_mutex before all
19540 worker threads have finished. Bugfix on 0.2.1.6-alpha.
19541 - The master thread could starve the worker threads quite badly on
19542 certain systems, causing them to run only partially in the allowed
19543 window. This resulted in test failures. Now the master thread sleeps
19544 occasionally for a few microseconds while the two worker-threads
19545 compete for the mutex. Bugfix on 0.2.0.1-alpha.
19548 Changes in version 0.2.2.10-alpha - 2010-03-07
19549 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
19550 could prevent relays from guessing their IP address correctly. It also
19551 starts the groundwork for another client-side performance boost, since
19552 currently we're not making efficient use of relays that have both the
19553 Guard flag and the Exit flag.
19556 - Fix a regression from our patch for bug 1244 that caused relays
19557 to guess their IP address incorrectly if they didn't set Address
19558 in their torrc and/or their address fails to resolve. Bugfix on
19559 0.2.2.9-alpha; fixes bug 1269.
19561 o Major features (performance):
19562 - Directory authorities now compute consensus weightings that instruct
19563 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
19564 and no flag. Clients that use these weightings will distribute
19565 network load more evenly across these different relay types. The
19566 weightings are in the consensus so we can change them globally in
19567 the future. Extra thanks to "outofwords" for finding some nasty
19568 security bugs in the first implementation of this feature.
19570 o Minor features (performance):
19571 - Always perform router selections using weighted relay bandwidth,
19572 even if we don't need a high capacity circuit at the time. Non-fast
19573 circuits now only differ from fast ones in that they can use relays
19574 not marked with the Fast flag. This "feature" could turn out to
19575 be a horrible bug; we should investigate more before it goes into
19579 - Allow disabling building of the manpages. Skipping the manpage
19580 speeds up the build considerably.
19582 o Minor bugfixes (on 0.2.2.x):
19583 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
19584 Bugfix on 0.2.2.9-alpha.
19585 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
19586 config option. Bugfix on 0.2.2.7-alpha.
19587 - Ship the asciidoc-helper file in the tarball, so that people can
19588 build from source if they want to, and touching the .1.txt files
19589 doesn't break the build. Bugfix on 0.2.2.9-alpha.
19591 o Minor bugfixes (on 0.2.1.x or earlier):
19592 - Fix a dereference-then-NULL-check sequence when publishing
19593 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
19595 - Fix another dereference-then-NULL-check sequence. Bugfix on
19596 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
19597 - Make sure we treat potentially not NUL-terminated strings correctly.
19598 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
19600 o Code simplifications and refactoring:
19601 - Fix some urls in the exit notice file and make it XHTML1.1 strict
19602 compliant. Based on a patch from Christian Kujau.
19603 - Don't use sed in asciidoc-helper anymore.
19604 - Make the build process fail if asciidoc cannot be found and
19605 building with asciidoc isn't disabled.
19608 Changes in version 0.2.2.9-alpha - 2010-02-22
19609 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
19610 location of a directory authority, and cleans up a bunch of small bugs.
19612 o Directory authority changes:
19613 - Change IP address for dannenberg (v3 directory authority), and
19614 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
19615 service directory authority) from the list.
19618 - Make Tor work again on the latest OS X: when deciding whether to
19619 use strange flags to turn TLS renegotiation on, detect the OpenSSL
19620 version at run-time, not compile time. We need to do this because
19621 Apple doesn't update its dev-tools headers when it updates its
19622 libraries in a security patch.
19623 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
19624 that could happen on 32-bit platforms with 64-bit time_t. Also fix
19625 a memory leak when requesting a hidden service descriptor we've
19626 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
19628 - Authorities could be tricked into giving out the Exit flag to relays
19629 that didn't allow exiting to any ports. This bug could screw
19630 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
19631 1238. Bug discovered by Martin Kowalczyk.
19632 - When freeing a session key, zero it out completely. We only zeroed
19633 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
19634 patched by ekir. Fixes bug 1254.
19637 - Fix static compilation by listing the openssl libraries in the right
19638 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
19639 - Resume handling .exit hostnames in a special way: originally we
19640 stripped the .exit part and used the requested exit relay. In
19641 0.2.2.1-alpha we stopped treating them in any special way, meaning
19642 if you use a .exit address then Tor will pass it on to the exit
19643 relay. Now we reject the .exit stream outright, since that behavior
19644 might be more expected by the user. Found and diagnosed by Scott
19645 Bennett and Downie on or-talk.
19646 - Don't spam the controller with events when we have no file
19647 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
19648 for log messages was already solved from bug 748.)
19649 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
19651 - Make the DNSPort option work with libevent 2.x. Don't alter the
19652 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
19653 - Emit a GUARD DROPPED controller event for a case we missed.
19654 - Make more fields in the controller protocol case-insensitive, since
19655 control-spec.txt said they were.
19656 - Refactor resolve_my_address() to not use gethostbyname() anymore.
19657 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
19658 - Fix a spec conformance issue: the network-status-version token
19659 must be the first token in a v3 consensus or vote. Discovered by
19660 parakeep. Bugfix on 0.2.0.3-alpha.
19662 o Code simplifications and refactoring:
19663 - Generate our manpage and HTML documentation using Asciidoc. This
19664 change should make it easier to maintain the documentation, and
19665 produce nicer HTML.
19666 - Remove the --enable-iphone option. According to reports from Marco
19667 Bonetti, Tor builds fine without any special tweaking on recent
19668 iPhone SDK versions.
19669 - Removed some unnecessary files from the source distribution. The
19670 AUTHORS file has now been merged into the people page on the
19671 website. The roadmaps and design doc can now be found in the
19672 projects directory in svn.
19673 - Enabled various circuit build timeout constants to be controlled
19674 by consensus parameters. Also set better defaults for these
19675 parameters based on experimentation on broadband and simulated
19676 high latency links.
19679 - The 'EXTENDCIRCUIT' control port command can now be used with
19680 a circ id of 0 and no path. This feature will cause Tor to build
19681 a new 'fast' general purpose circuit using its own path selection
19683 - Added a BUILDTIMEOUT_SET controller event to describe changes
19684 to the circuit build timeout.
19685 - Future-proof the controller protocol a bit by ignoring keyword
19686 arguments we do not recognize.
19687 - Expand homedirs passed to tor-checkkey. This should silence a
19688 coverity complaint about passing a user-supplied string into
19689 open() without checking it.
19692 Changes in version 0.2.1.25 - 2010-03-16
19693 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
19694 prevent relays from guessing their IP address correctly. It also fixes
19695 several minor potential security bugs.
19698 - Fix a regression from our patch for bug 1244 that caused relays
19699 to guess their IP address incorrectly if they didn't set Address
19700 in their torrc and/or their address fails to resolve. Bugfix on
19701 0.2.1.23; fixes bug 1269.
19702 - When freeing a session key, zero it out completely. We only zeroed
19703 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
19704 patched by ekir. Fixes bug 1254.
19707 - Fix a dereference-then-NULL-check sequence when publishing
19708 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
19710 - Fix another dereference-then-NULL-check sequence. Bugfix on
19711 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
19712 - Make sure we treat potentially not NUL-terminated strings correctly.
19713 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
19717 Changes in version 0.2.1.24 - 2010-02-21
19718 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
19722 - Work correctly out-of-the-box with even more vendor-patched versions
19723 of OpenSSL. In particular, make it so Debian and OS X don't need
19724 customized patches to run/build.
19727 Changes in version 0.2.1.23 - 2010-02-13
19728 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
19729 again on the latest OS X, and updates the location of a directory
19732 o Major bugfixes (performance):
19733 - We were selecting our guards uniformly at random, and then weighting
19734 which of our guards we'd use uniformly at random. This imbalance
19735 meant that Tor clients were severely limited on throughput (and
19736 probably latency too) by the first hop in their circuit. Now we
19737 select guards weighted by currently advertised bandwidth. We also
19738 automatically discard guards picked using the old algorithm. Fixes
19739 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
19742 - Make Tor work again on the latest OS X: when deciding whether to
19743 use strange flags to turn TLS renegotiation on, detect the OpenSSL
19744 version at run-time, not compile time. We need to do this because
19745 Apple doesn't update its dev-tools headers when it updates its
19746 libraries in a security patch.
19747 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
19748 that could happen on 32-bit platforms with 64-bit time_t. Also fix
19749 a memory leak when requesting a hidden service descriptor we've
19750 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
19753 o Directory authority changes:
19754 - Change IP address for dannenberg (v3 directory authority), and
19755 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
19756 service directory authority) from the list.
19759 - Refactor resolve_my_address() to not use gethostbyname() anymore.
19760 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
19763 - Avoid a mad rush at the beginning of each month when each client
19764 rotates half of its guards. Instead we spread the rotation out
19765 throughout the month, but we still avoid leaving a precise timestamp
19766 in the state file about when we first picked the guard. Improves
19767 over the behavior introduced in 0.1.2.17.
19770 Changes in version 0.2.2.8-alpha - 2010-01-26
19771 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
19772 causing bridge relays to disappear. If you're running a bridge,
19776 - Fix a memory corruption bug on bridges that occurred during the
19777 inclusion of stats data in extra-info descriptors. Also fix the
19778 interface for geoip_get_bridge_stats* to prevent similar bugs in
19779 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
19780 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
19783 - Ignore OutboundBindAddress when connecting to localhost.
19784 Connections to localhost need to come _from_ localhost, or else
19785 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
19789 Changes in version 0.2.2.7-alpha - 2010-01-19
19790 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
19791 as laying the groundwork for further relay-side performance fixes. It
19792 also starts cleaning up client behavior with respect to the EntryNodes,
19793 ExitNodes, and StrictNodes config options.
19795 This release also rotates two directory authority keys, due to a
19796 security breach of some of the Torproject servers.
19798 o Directory authority changes:
19799 - Rotate keys (both v3 identity and relay identity) for moria1
19802 o Major features (performance):
19803 - We were selecting our guards uniformly at random, and then weighting
19804 which of our guards we'd use uniformly at random. This imbalance
19805 meant that Tor clients were severely limited on throughput (and
19806 probably latency too) by the first hop in their circuit. Now we
19807 select guards weighted by currently advertised bandwidth. We also
19808 automatically discard guards picked using the old algorithm. Fixes
19809 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
19810 - When choosing which cells to relay first, relays can now favor
19811 circuits that have been quiet recently, to provide lower latency
19812 for low-volume circuits. By default, relays enable or disable this
19813 feature based on a setting in the consensus. You can override
19814 this default by using the new "CircuitPriorityHalflife" config
19815 option. Design and code by Ian Goldberg, Can Tang, and Chris
19817 - Add separate per-conn write limiting to go with the per-conn read
19818 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
19819 but never per-conn write limits.
19820 - New consensus params "bwconnrate" and "bwconnburst" to let us
19821 rate-limit client connections as they enter the network. It's
19822 controlled in the consensus so we can turn it on and off for
19823 experiments. It's starting out off. Based on proposal 163.
19825 o Major features (relay selection options):
19826 - Switch to a StrictNodes config option, rather than the previous
19827 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
19828 "StrictExcludeNodes" option.
19829 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
19830 change during a config reload, mark and discard all our origin
19831 circuits. This fix should address edge cases where we change the
19832 config options and but then choose a circuit that we created before
19834 - If EntryNodes or ExitNodes are set, be more willing to use an
19835 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
19837 - Make EntryNodes config option much more aggressive even when
19838 StrictNodes is not set. Before it would prepend your requested
19839 entrynodes to your list of guard nodes, but feel free to use others
19840 after that. Now it chooses only from your EntryNodes if any of
19841 those are available, and only falls back to others if a) they're
19842 all down and b) StrictNodes is not set.
19843 - Now we refresh your entry guards from EntryNodes at each consensus
19844 fetch -- rather than just at startup and then they slowly rot as
19845 the network changes.
19848 - Stop bridge directory authorities from answering dbg-stability.txt
19849 directory queries, which would let people fetch a list of all
19850 bridge identities they track. Bugfix on 0.2.1.6-alpha.
19853 - Log a notice when we get a new control connection. Now it's easier
19854 for security-conscious users to recognize when a local application
19855 is knocking on their controller door. Suggested by bug 1196.
19856 - New config option "CircuitStreamTimeout" to override our internal
19857 timeout schedule for how many seconds until we detach a stream from
19858 a circuit and try a new circuit. If your network is particularly
19859 slow, you might want to set this to a number like 60.
19860 - New controller command "getinfo config-text". It returns the
19861 contents that Tor would write if you send it a SAVECONF command,
19862 so the controller can write the file to disk itself.
19863 - New options for SafeLogging to allow scrubbing only log messages
19864 generated while acting as a relay.
19865 - Ship the bridges spec file in the tarball too.
19866 - Avoid a mad rush at the beginning of each month when each client
19867 rotates half of its guards. Instead we spread the rotation out
19868 throughout the month, but we still avoid leaving a precise timestamp
19869 in the state file about when we first picked the guard. Improves
19870 over the behavior introduced in 0.1.2.17.
19872 o Minor bugfixes (compiling):
19873 - Fix compilation on OS X 10.3, which has a stub mlockall() but
19874 hides it. Bugfix on 0.2.2.6-alpha.
19875 - Fix compilation on Solaris by removing support for the
19876 DisableAllSwap config option. Solaris doesn't have an rlimit for
19877 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
19880 o Minor bugfixes (crashes):
19881 - Do not segfault when writing buffer stats when we haven't observed
19882 a single circuit to report about. Found by Fabian Lanze. Bugfix on
19884 - If we're in the pathological case where there's no exit bandwidth
19885 but there is non-exit bandwidth, or no guard bandwidth but there
19886 is non-guard bandwidth, don't crash during path selection. Bugfix
19888 - Fix an impossible-to-actually-trigger buffer overflow in relay
19889 descriptor generation. Bugfix on 0.1.0.15.
19891 o Minor bugfixes (privacy):
19892 - Fix an instance where a Tor directory mirror might accidentally
19893 log the IP address of a misbehaving Tor client. Bugfix on
19895 - Don't list Windows capabilities in relay descriptors. We never made
19896 use of them, and maybe it's a bad idea to publish them. Bugfix
19899 o Minor bugfixes (other):
19900 - Resolve an edge case in path weighting that could make us misweight
19901 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
19902 - Fix statistics on client numbers by country as seen by bridges that
19903 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
19904 intervals instead of variable 12-to-48-hour intervals.
19905 - After we free an internal connection structure, overwrite it
19906 with a different memory value than we use for overwriting a freed
19907 internal circuit structure. Should help with debugging. Suggested
19909 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
19912 o Removed features:
19913 - Remove the HSAuthorityRecordStats option that version 0 hidden
19914 service authorities could have used to track statistics of overall
19915 hidden service usage.
19918 Changes in version 0.2.1.22 - 2010-01-19
19919 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
19920 authorities -- it would tell you its whole history of bridge descriptors
19921 if you make the right directory request. This stable update also
19922 rotates two of the seven v3 directory authority keys and locations.
19924 o Directory authority changes:
19925 - Rotate keys (both v3 identity and relay identity) for moria1
19929 - Stop bridge directory authorities from answering dbg-stability.txt
19930 directory queries, which would let people fetch a list of all
19931 bridge identities they track. Bugfix on 0.2.1.6-alpha.
19934 Changes in version 0.2.1.21 - 2009-12-21
19935 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
19936 library. If you use Tor on Linux / Unix and you're getting SSL
19937 renegotiation errors, upgrading should help. We also recommend an
19938 upgrade if you're an exit relay.
19941 - Work around a security feature in OpenSSL 0.9.8l that prevents our
19942 handshake from working unless we explicitly tell OpenSSL that we
19943 are using SSL renegotiation safely. We are, of course, but OpenSSL
19944 0.9.8l won't work unless we say we are.
19945 - Avoid crashing if the client is trying to upload many bytes and the
19946 circuit gets torn down at the same time, or if the flip side
19947 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
19950 - Do not refuse to learn about authority certs and v2 networkstatus
19951 documents that are older than the latest consensus. This bug might
19952 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
19953 Spotted and fixed by xmux.
19954 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
19955 trigger platform-specific option misparsing case found by Coverity
19957 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
19958 trigger assert. Fixes bug 1173.
19961 Changes in version 0.2.2.6-alpha - 2009-11-19
19962 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
19963 support for the new lower-footprint "microdescriptor" directory design,
19964 future-proofing our consensus format against new hash functions or
19965 other changes, and an Android port. It also makes Tor compatible with
19966 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
19969 - Directory authorities can now create, vote on, and serve multiple
19970 parallel formats of directory data as part of their voting process.
19971 Partially implements Proposal 162: "Publish the consensus in
19973 - Directory authorities can now agree on and publish small summaries
19974 of router information that clients can use in place of regular
19975 server descriptors. This transition will eventually allow clients
19976 to use far less bandwidth for downloading information about the
19977 network. Begins the implementation of Proposal 158: "Clients
19978 download consensus + microdescriptors".
19979 - The directory voting system is now extensible to use multiple hash
19980 algorithms for signatures and resource selection. Newer formats
19981 are signed with SHA256, with a possibility for moving to a better
19982 hash algorithm in the future.
19983 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
19984 current and future memory pages via mlockall(). On supported
19985 platforms (modern Linux and probably BSD but not Windows or OS X),
19986 this should effectively disable any and all attempts to page out
19987 memory. This option requires that you start your Tor as root --
19988 if you use DisableAllSwap, please consider using the User option
19989 to properly reduce the privileges of your Tor.
19990 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
19991 to help Tor build correctly for Android phones.
19994 - Work around a security feature in OpenSSL 0.9.8l that prevents our
19995 handshake from working unless we explicitly tell OpenSSL that we
19996 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
19997 won't work unless we say we are.
20000 - Fix a crash bug when trying to initialize the evdns module in
20001 Libevent 2. Bugfix on 0.2.1.16-rc.
20002 - Stop logging at severity 'warn' when some other Tor client tries
20003 to establish a circuit with us using weak DH keys. It's a protocol
20004 violation, but that doesn't mean ordinary users need to hear about
20005 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
20006 - Do not refuse to learn about authority certs and v2 networkstatus
20007 documents that are older than the latest consensus. This bug might
20008 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
20009 Spotted and fixed by xmux.
20010 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
20011 - If all authorities restart at once right before a consensus vote,
20012 nobody will vote about "Running", and clients will get a consensus
20013 with no usable relays. Instead, authorities refuse to build a
20014 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
20015 - If your relay can't keep up with the number of incoming create
20016 cells, it would log one warning per failure into your logs. Limit
20017 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
20018 - Bridges now use "reject *:*" as their default exit policy. Bugfix
20019 on 0.2.0.3-alpha; fixes bug 1113.
20020 - Fix a memory leak on directory authorities during voting that was
20021 introduced in 0.2.2.1-alpha. Found via valgrind.
20024 Changes in version 0.2.1.20 - 2009-10-15
20025 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
20026 services at once, prepares for more performance improvements, and
20027 fixes a bunch of smaller bugs.
20029 The Windows and OS X bundles also include a more recent Vidalia,
20030 and switch from Privoxy to Polipo.
20032 The OS X installers are now drag and drop. It's best to un-install
20033 Tor/Vidalia and then install this new bundle, rather than upgrade. If
20034 you want to upgrade, you'll need to update the paths for Tor and Polipo
20035 in the Vidalia Settings window.
20038 - Send circuit or stream sendme cells when our window has decreased
20039 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
20040 by Karsten when testing the "reduce circuit window" performance
20041 patch. Bugfix on the 54th commit on Tor -- from July 2002,
20042 before the release of Tor 0.0.0. This is the new winner of the
20044 - Fix a remotely triggerable memory leak when a consensus document
20045 contains more than one signature from the same voter. Bugfix on
20047 - Avoid segfault in rare cases when finishing an introduction circuit
20048 as a client and finding out that we don't have an introduction key
20049 for it. Fixes bug 1073. Reported by Aaron Swartz.
20052 - Tor now reads the "circwindow" parameter out of the consensus,
20053 and uses that value for its circuit package window rather than the
20054 default of 1000 cells. Begins the implementation of proposal 168.
20056 o New directory authorities:
20057 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
20059 - Move moria1 and tonga to alternate IP addresses.
20062 - Fix a signed/unsigned compile warning in 0.2.1.19.
20063 - Fix possible segmentation fault on directory authorities. Bugfix on
20065 - Fix an extremely rare infinite recursion bug that could occur if
20066 we tried to log a message after shutting down the log subsystem.
20067 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
20068 - Fix an obscure bug where hidden services on 64-bit big-endian
20069 systems might mis-read the timestamp in v3 introduce cells, and
20070 refuse to connect back to the client. Discovered by "rotor".
20071 Bugfix on 0.2.1.6-alpha.
20072 - We were triggering a CLOCK_SKEW controller status event whenever
20073 we connect via the v2 connection protocol to any relay that has
20074 a wrong clock. Instead, we should only inform the controller when
20075 it's a trusted authority that claims our clock is wrong. Bugfix
20076 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
20077 - We were telling the controller about CHECKING_REACHABILITY and
20078 REACHABILITY_FAILED status events whenever we launch a testing
20079 circuit or notice that one has failed. Instead, only tell the
20080 controller when we want to inform the user of overall success or
20081 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
20083 - Don't warn when we're using a circuit that ends with a node
20084 excluded in ExcludeExitNodes, but the circuit is not used to access
20085 the outside world. This should help fix bug 1090. Bugfix on
20087 - Work around a small memory leak in some versions of OpenSSL that
20088 stopped the memory used by the hostname TLS extension from being
20092 - Add a "getinfo status/accepted-server-descriptor" controller
20093 command, which is the recommended way for controllers to learn
20094 whether our server descriptor has been successfully received by at
20095 least on directory authority. Un-recommend good-server-descriptor
20096 getinfo and status events until we have a better design for them.
20099 Changes in version 0.2.2.5-alpha - 2009-10-11
20100 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
20103 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
20105 o Directory authorities:
20106 - Temporarily (just for this release) move dizum to an alternate
20110 Changes in version 0.2.2.4-alpha - 2009-10-10
20111 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
20112 introduces a new unit test framework, shifts directry authority
20113 addresses around to reduce the impact from recent blocking events,
20114 and fixes a few smaller bugs.
20117 - Fix several more asserts in the circuit_build_times code, for
20118 example one that causes Tor to fail to start once we have
20119 accumulated 5000 build times in the state file. Bugfixes on
20120 0.2.2.2-alpha; fixes bug 1108.
20122 o New directory authorities:
20123 - Move moria1 and Tonga to alternate IP addresses.
20126 - Log SSL state transitions at debug level during handshake, and
20127 include SSL states in error messages. This may help debug future
20128 SSL handshake issues.
20129 - Add a new "Handshake" log domain for activities that happen
20130 during the TLS handshake.
20131 - Revert to the "June 3 2009" ip-to-country file. The September one
20132 seems to have removed most US IP addresses.
20133 - Directory authorities now reject Tor relays with versions less than
20134 0.1.2.14. This step cuts out four relays from the current network,
20135 none of which are very big.
20138 - Fix a couple of smaller issues with gathering statistics. Bugfixes
20140 - Fix two memory leaks in the error case of
20141 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
20142 - Don't count one-hop circuits when we're estimating how long it
20143 takes circuits to build on average. Otherwise we'll set our circuit
20144 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
20145 - Directory authorities no longer change their opinion of, or vote on,
20146 whether a router is Running, unless they have themselves been
20147 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
20150 o Code simplifications and refactoring:
20151 - Revise our unit tests to use the "tinytest" framework, so we
20152 can run tests in their own processes, have smarter setup/teardown
20153 code, and so on. The unit test code has moved to its own
20154 subdirectory, and has been split into multiple modules.
20157 Changes in version 0.2.2.3-alpha - 2009-09-23
20158 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
20161 - Fix an overzealous assert in our new circuit build timeout code.
20162 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
20165 - If the networkstatus consensus tells us that we should use a
20166 negative circuit package window, ignore it. Otherwise we'll
20167 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
20170 Changes in version 0.2.2.2-alpha - 2009-09-21
20171 Tor 0.2.2.2-alpha introduces our latest performance improvement for
20172 clients: Tor tracks the average time it takes to build a circuit, and
20173 avoids using circuits that take too long to build. For fast connections,
20174 this feature can cut your expected latency in half. For slow or flaky
20175 connections, it could ruin your Tor experience. Let us know if it does!
20178 - Tor now tracks how long it takes to build client-side circuits
20179 over time, and adapts its timeout to local network performance.
20180 Since a circuit that takes a long time to build will also provide
20181 bad performance, we get significant latency improvements by
20182 discarding the slowest 20% of circuits. Specifically, Tor creates
20183 circuits more aggressively than usual until it has enough data
20184 points for a good timeout estimate. Implements proposal 151.
20185 We are especially looking for reports (good and bad) from users with
20186 both EDGE and broadband connections that can move from broadband
20187 to EDGE and find out if the build-time data in the .tor/state gets
20188 reset without loss of Tor usability. You should also see a notice
20189 log message telling you that Tor has reset its timeout.
20190 - Directory authorities can now vote on arbitrary integer values as
20191 part of the consensus process. This is designed to help set
20192 network-wide parameters. Implements proposal 167.
20193 - Tor now reads the "circwindow" parameter out of the consensus,
20194 and uses that value for its circuit package window rather than the
20195 default of 1000 cells. Begins the implementation of proposal 168.
20198 - Fix a remotely triggerable memory leak when a consensus document
20199 contains more than one signature from the same voter. Bugfix on
20203 - Fix an extremely rare infinite recursion bug that could occur if
20204 we tried to log a message after shutting down the log subsystem.
20205 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
20206 - Fix parsing for memory or time units given without a space between
20207 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
20208 - A networkstatus vote must contain exactly one signature. Spec
20209 conformance issue. Bugfix on 0.2.0.3-alpha.
20210 - Fix an obscure bug where hidden services on 64-bit big-endian
20211 systems might mis-read the timestamp in v3 introduce cells, and
20212 refuse to connect back to the client. Discovered by "rotor".
20213 Bugfix on 0.2.1.6-alpha.
20214 - We were triggering a CLOCK_SKEW controller status event whenever
20215 we connect via the v2 connection protocol to any relay that has
20216 a wrong clock. Instead, we should only inform the controller when
20217 it's a trusted authority that claims our clock is wrong. Bugfix
20218 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
20219 - We were telling the controller about CHECKING_REACHABILITY and
20220 REACHABILITY_FAILED status events whenever we launch a testing
20221 circuit or notice that one has failed. Instead, only tell the
20222 controller when we want to inform the user of overall success or
20223 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
20225 - Don't warn when we're using a circuit that ends with a node
20226 excluded in ExcludeExitNodes, but the circuit is not used to access
20227 the outside world. This should help fix bug 1090, but more problems
20228 remain. Bugfix on 0.2.1.6-alpha.
20229 - Work around a small memory leak in some versions of OpenSSL that
20230 stopped the memory used by the hostname TLS extension from being
20232 - Make our 'torify' script more portable; if we have only one of
20233 'torsocks' or 'tsocks' installed, don't complain to the user;
20234 and explain our warning about tsocks better.
20237 - Add a "getinfo status/accepted-server-descriptor" controller
20238 command, which is the recommended way for controllers to learn
20239 whether our server descriptor has been successfully received by at
20240 least on directory authority. Un-recommend good-server-descriptor
20241 getinfo and status events until we have a better design for them.
20242 - Update to the "September 4 2009" ip-to-country file.
20245 Changes in version 0.2.2.1-alpha - 2009-08-26
20246 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
20247 Tor clients to bootstrap on networks where only port 80 is reachable,
20248 makes it more straightforward to support hardware crypto accelerators,
20249 and starts the groundwork for gathering stats safely at relays.
20252 - Start the process of disabling ".exit" address notation, since it
20253 can be used for a variety of esoteric application-level attacks
20254 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
20257 o New directory authorities:
20258 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
20262 - New AccelName and AccelDir options add support for dynamic OpenSSL
20263 hardware crypto acceleration engines.
20264 - Tor now supports tunneling all of its outgoing connections over
20265 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
20266 configuration options. Code by Christopher Davis.
20269 - Send circuit or stream sendme cells when our window has decreased
20270 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
20271 by Karsten when testing the "reduce circuit window" performance
20272 patch. Bugfix on the 54th commit on Tor -- from July 2002,
20273 before the release of Tor 0.0.0. This is the new winner of the
20276 o New options for gathering stats safely:
20277 - Directory mirrors that set "DirReqStatistics 1" write statistics
20278 about directory requests to disk every 24 hours. As compared to the
20279 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
20280 1) stats are written to disk exactly every 24 hours; 2) estimated
20281 shares of v2 and v3 requests are determined as mean values, not at
20282 the end of a measurement period; 3) unresolved requests are listed
20283 with country code '??'; 4) directories also measure download times.
20284 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
20285 number of exit streams and transferred bytes per port to disk every
20287 - Relays that set "CellStatistics 1" write statistics on how long
20288 cells spend in their circuit queues to disk every 24 hours.
20289 - Entry nodes that set "EntryStatistics 1" write statistics on the
20290 rough number and origins of connecting clients to disk every 24
20292 - Relays that write any of the above statistics to disk and set
20293 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
20294 their extra-info documents.
20297 - New --digests command-line switch to output the digests of the
20298 source files Tor was built with.
20299 - The "torify" script now uses torsocks where available.
20300 - The memarea code now uses a sentinel value at the end of each area
20301 to make sure nothing writes beyond the end of an area. This might
20302 help debug some conceivable causes of bug 930.
20303 - Time and memory units in the configuration file can now be set to
20304 fractional units. For example, "2.5 GB" is now a valid value for
20306 - Certain Tor clients (such as those behind check.torproject.org) may
20307 want to fetch the consensus in an extra early manner. To enable this
20308 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
20309 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
20310 as only certain clients who must have this information sooner should
20312 - Instead of adding the svn revision to the Tor version string, report
20313 the git commit (when we're building from a git checkout).
20316 - If any of the v3 certs we download are unparseable, we should
20317 actually notice the failure so we don't retry indefinitely. Bugfix
20318 on 0.2.0.x; reported by "rotator".
20319 - If the cached cert file is unparseable, warn but don't exit.
20320 - Fix possible segmentation fault on directory authorities. Bugfix on
20322 - When Tor fails to parse a descriptor of any kind, dump it to disk.
20323 Might help diagnosing bug 1051.
20325 o Deprecated and removed features:
20326 - The controller no longer accepts the old obsolete "addr-mappings/"
20327 or "unregistered-servers-" GETINFO values.
20328 - Hidden services no longer publish version 0 descriptors, and clients
20329 do not request or use version 0 descriptors. However, the old hidden
20330 service authorities still accept and serve version 0 descriptors
20331 when contacted by older hidden services/clients.
20332 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
20333 always on; using them is necessary for correct forward-compatible
20335 - Remove support for .noconnect style addresses. Nobody was using
20336 them, and they provided another avenue for detecting Tor users
20337 via application-level web tricks.
20339 o Packaging changes:
20340 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
20341 installer bundles. See
20342 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
20343 for details of what's new in Vidalia 0.2.3.
20344 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
20345 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
20346 configuration file, rather than the old Privoxy.
20347 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
20348 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
20349 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
20350 better compatibility with OS X 10.6, aka Snow Leopard.
20351 - OS X Vidalia Bundle: The multi-package installer is now replaced
20352 by a simple drag and drop to the /Applications folder. This change
20353 occurred with the upgrade to Vidalia 0.2.3.
20356 Changes in version 0.2.1.19 - 2009-07-28
20357 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
20358 services on Tor 0.2.1.3-alpha through 0.2.1.18.
20361 - Make accessing hidden services on 0.2.1.x work right again.
20362 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
20363 part of patch provided by "optimist".
20366 - When a relay/bridge is writing out its identity key fingerprint to
20367 the "fingerprint" file and to its logs, write it without spaces. Now
20368 it will look like the fingerprints in our bridges documentation,
20369 and confuse fewer users.
20372 - Relays no longer publish a new server descriptor if they change
20373 their MaxAdvertisedBandwidth config option but it doesn't end up
20374 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
20375 fixes bug 1026. Patch from Sebastian.
20376 - Avoid leaking memory every time we get a create cell but we have
20377 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
20378 fixes bug 1034. Reported by BarkerJr.
20381 Changes in version 0.2.1.18 - 2009-07-24
20382 Tor 0.2.1.18 lays the foundations for performance improvements,
20383 adds status events to help users diagnose bootstrap problems, adds
20384 optional authentication/authorization for hidden services, fixes a
20385 variety of potential anonymity problems, and includes a huge pile of
20386 other features and bug fixes.
20389 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
20392 Changes in version 0.2.1.17-rc - 2009-07-07
20393 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
20394 candidate for the 0.2.1.x series. It lays the groundwork for further
20395 client performance improvements, and also fixes a big bug with directory
20396 authorities that were causing them to assign Guard and Stable flags
20399 The Windows bundles also finally include the geoip database that we
20400 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
20401 should actually install Torbutton rather than giving you a cryptic
20402 failure message (oops).
20405 - Clients now use the bandwidth values in the consensus, rather than
20406 the bandwidth values in each relay descriptor. This approach opens
20407 the door to more accurate bandwidth estimates once the directory
20408 authorities start doing active measurements. Implements more of
20412 - When Tor clients restart after 1-5 days, they discard all their
20413 cached descriptors as too old, but they still use the cached
20414 consensus document. This approach is good for robustness, but
20415 bad for performance: since they don't know any bandwidths, they
20416 end up choosing at random rather than weighting their choice by
20417 speed. Fixed by the above feature of putting bandwidths in the
20418 consensus. Bugfix on 0.2.0.x.
20419 - Directory authorities were neglecting to mark relays down in their
20420 internal histories if the relays fall off the routerlist without
20421 ever being found unreachable. So there were relays in the histories
20422 that haven't been seen for eight months, and are listed as being
20423 up for eight months. This wreaked havoc on the "median wfu"
20424 and "median mtbf" calculations, in turn making Guard and Stable
20425 flags very wrong, hurting network performance. Fixes bugs 696 and
20426 969. Bugfix on 0.2.0.6-alpha.
20429 - Serve the DirPortFrontPage page even when we have been approaching
20430 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
20431 - The control port would close the connection before flushing long
20432 replies, such as the network consensus, if a QUIT command was issued
20433 before the reply had completed. Now, the control port flushes all
20434 pending replies before closing the connection. Also fixed a spurious
20435 warning when a QUIT command is issued after a malformed or rejected
20436 AUTHENTICATE command, but before the connection was closed. Patch
20437 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
20438 - When we can't find an intro key for a v2 hidden service descriptor,
20439 fall back to the v0 hidden service descriptor and log a bug message.
20440 Workaround for bug 1024.
20441 - Fix a log message that did not respect the SafeLogging option.
20445 - If we're a relay and we change our IP address, be more verbose
20446 about the reason that made us change. Should help track down
20447 further bugs for relays on dynamic IP addresses.
20450 Changes in version 0.2.0.35 - 2009-06-24
20452 - Avoid crashing in the presence of certain malformed descriptors.
20453 Found by lark, and by automated fuzzing.
20454 - Fix an edge case where a malicious exit relay could convince a
20455 controller that the client's DNS question resolves to an internal IP
20456 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
20459 - Finally fix the bug where dynamic-IP relays disappear when their
20460 IP address changes: directory mirrors were mistakenly telling
20461 them their old address if they asked via begin_dir, so they
20462 never got an accurate answer about their new address, so they
20463 just vanished after a day. For belt-and-suspenders, relays that
20464 don't set Address in their config now avoid using begin_dir for
20465 all direct connections. Should fix bugs 827, 883, and 900.
20466 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
20467 that would occur on some exit nodes when DNS failures and timeouts
20468 occurred in certain patterns. Fix for bug 957.
20471 - When starting with a cache over a few days old, do not leak
20472 memory for the obsolete router descriptors in it. Bugfix on
20473 0.2.0.33; fixes bug 672.
20474 - Hidden service clients didn't use a cached service descriptor that
20475 was older than 15 minutes, but wouldn't fetch a new one either,
20476 because there was already one in the cache. Now, fetch a v2
20477 descriptor unless the same descriptor was added to the cache within
20478 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
20481 Changes in version 0.2.1.16-rc - 2009-06-20
20482 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
20483 a bunch of minor bugs.
20486 - Fix an edge case where a malicious exit relay could convince a
20487 controller that the client's DNS question resolves to an internal IP
20488 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
20490 o Major performance improvements (on 0.2.0.x):
20491 - Disable and refactor some debugging checks that forced a linear scan
20492 over the whole server-side DNS cache. These accounted for over 50%
20493 of CPU time on a relatively busy exit node's gprof profile. Found
20495 - Disable some debugging checks that appeared in exit node profile
20499 - Update to the "June 3 2009" ip-to-country file.
20500 - Do not have tor-resolve automatically refuse all .onion addresses;
20501 if AutomapHostsOnResolve is set in your torrc, this will work fine.
20503 o Minor bugfixes (on 0.2.0.x):
20504 - Log correct error messages for DNS-related network errors on
20506 - Fix a race condition that could cause crashes or memory corruption
20507 when running as a server with a controller listening for log
20509 - Avoid crashing when we have a policy specified in a DirPolicy or
20510 SocksPolicy or ReachableAddresses option with ports set on it,
20511 and we re-load the policy. May fix bug 996.
20512 - Hidden service clients didn't use a cached service descriptor that
20513 was older than 15 minutes, but wouldn't fetch a new one either,
20514 because there was already one in the cache. Now, fetch a v2
20515 descriptor unless the same descriptor was added to the cache within
20516 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
20518 o Minor bugfixes (on 0.2.1.x):
20519 - Don't warn users about low port and hibernation mix when they
20520 provide a *ListenAddress directive to fix that. Bugfix on
20522 - When switching back and forth between bridge mode, do not start
20523 gathering GeoIP data until two hours have passed.
20524 - Do not complain that the user has requested an excluded node as
20525 an exit when the node is not really an exit. This could happen
20526 because the circuit was for testing, or an introduction point.
20530 Changes in version 0.2.1.15-rc - 2009-05-25
20531 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
20532 series. It fixes a major bug on fast exit relays, as well as a variety
20533 of more minor bugs.
20535 o Major bugfixes (on 0.2.0.x):
20536 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
20537 that would occur on some exit nodes when DNS failures and timeouts
20538 occurred in certain patterns. Fix for bug 957.
20540 o Minor bugfixes (on 0.2.0.x):
20541 - Actually return -1 in the error case for read_bandwidth_usage().
20542 Harmless bug, since we currently don't care about the return value
20543 anywhere. Bugfix on 0.2.0.9-alpha.
20544 - Provide a more useful log message if bug 977 (related to buffer
20545 freelists) ever reappears, and do not crash right away.
20546 - Fix an assertion failure on 64-bit platforms when we allocated
20547 memory right up to the end of a memarea, then realigned the memory
20548 one step beyond the end. Fixes a possible cause of bug 930.
20549 - Protect the count of open sockets with a mutex, so we can't
20550 corrupt it when two threads are closing or opening sockets at once.
20551 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
20552 - Don't allow a bridge to publish its router descriptor to a
20553 non-bridge directory authority. Fixes part of bug 932.
20554 - When we change to or from being a bridge, reset our counts of
20555 client usage by country. Fixes bug 932.
20556 - Fix a bug that made stream bandwidth get misreported to the
20558 - Stop using malloc_usable_size() to use more area than we had
20559 actually allocated: it was safe, but made valgrind really unhappy.
20560 - Fix a memory leak when v3 directory authorities load their keys
20561 and cert from disk. Bugfix on 0.2.0.1-alpha.
20563 o Minor bugfixes (on 0.2.1.x):
20564 - Fix use of freed memory when deciding to mark a non-addable
20565 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
20568 Changes in version 0.2.1.14-rc - 2009-04-12
20569 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
20570 series. It begins fixing some major performance problems, and also
20571 finally addresses the bug that was causing relays on dynamic IP
20572 addresses to fall out of the directory.
20575 - Clients replace entry guards that were chosen more than a few months
20576 ago. This change should significantly improve client performance,
20577 especially once more people upgrade, since relays that have been
20578 a guard for a long time are currently overloaded.
20580 o Major bugfixes (on 0.2.0):
20581 - Finally fix the bug where dynamic-IP relays disappear when their
20582 IP address changes: directory mirrors were mistakenly telling
20583 them their old address if they asked via begin_dir, so they
20584 never got an accurate answer about their new address, so they
20585 just vanished after a day. For belt-and-suspenders, relays that
20586 don't set Address in their config now avoid using begin_dir for
20587 all direct connections. Should fix bugs 827, 883, and 900.
20588 - Relays were falling out of the networkstatus consensus for
20589 part of a day if they changed their local config but the
20590 authorities discarded their new descriptor as "not sufficiently
20591 different". Now directory authorities accept a descriptor as changed
20592 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
20593 patch by Sebastian.
20594 - Avoid crashing in the presence of certain malformed descriptors.
20595 Found by lark, and by automated fuzzing.
20598 - When generating circuit events with verbose nicknames for
20599 controllers, try harder to look up nicknames for routers on a
20600 circuit. (Previously, we would look in the router descriptors we had
20601 for nicknames, but not in the consensus.) Partial fix for bug 941.
20602 - If the bridge config line doesn't specify a port, assume 443.
20603 This makes bridge lines a bit smaller and easier for users to
20605 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
20606 bytes (aka 20KB/s), to match our documentation. Also update
20607 directory authorities so they always assign the Fast flag to relays
20608 with 20KB/s of capacity. Now people running relays won't suddenly
20609 find themselves not seeing any use, if the network gets faster
20611 - Update to the "April 3 2009" ip-to-country file.
20614 - Avoid trying to print raw memory to the logs when we decide to
20615 give up on downloading a given relay descriptor. Bugfix on
20617 - In tor-resolve, when the Tor client to use is specified by
20618 <hostname>:<port>, actually use the specified port rather than
20619 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
20620 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
20621 - When starting with a cache over a few days old, do not leak
20622 memory for the obsolete router descriptors in it. Bugfix on
20624 - Avoid double-free on list of successfully uploaded hidden
20625 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
20626 - Change memarea_strndup() implementation to work even when
20627 duplicating a string at the end of a page. This bug was
20628 harmless for now, but could have meant crashes later. Fix by
20629 lark. Bugfix on 0.2.1.1-alpha.
20630 - Limit uploaded directory documents to be 16M rather than 500K.
20631 The directory authorities were refusing v3 consensus votes from
20632 other authorities, since the votes are now 504K. Fixes bug 959;
20633 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
20634 - Directory authorities should never send a 503 "busy" response to
20635 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
20639 Changes in version 0.2.1.13-alpha - 2009-03-09
20640 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
20641 cleanups. We're finally getting close to a release candidate.
20644 - Correctly update the list of which countries we exclude as
20645 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
20646 lark. Bugfix on 0.2.1.6-alpha.
20648 o Minor bugfixes (on 0.2.0.x and earlier):
20649 - Automatically detect MacOSX versions earlier than 10.4.0, and
20650 disable kqueue from inside Tor when running with these versions.
20651 We previously did this from the startup script, but that was no
20652 help to people who didn't use the startup script. Resolves bug 863.
20653 - When we had picked an exit node for a connection, but marked it as
20654 "optional", and it turned out we had no onion key for the exit,
20655 stop wanting that exit and try again. This situation may not
20656 be possible now, but will probably become feasible with proposal
20657 158. Spotted by rovv. Fixes another case of bug 752.
20658 - Clients no longer cache certificates for authorities they do not
20659 recognize. Bugfix on 0.2.0.9-alpha.
20660 - When we can't transmit a DNS request due to a network error, retry
20661 it after a while, and eventually transmit a failing response to
20662 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
20663 - If the controller claimed responsibility for a stream, but that
20664 stream never finished making its connection, it would live
20665 forever in circuit_wait state. Now we close it after SocksTimeout
20666 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
20667 - Drop begin cells to a hidden service if they come from the middle
20668 of a circuit. Patch from lark.
20669 - When we erroneously receive two EXTEND cells for the same circuit
20670 ID on the same connection, drop the second. Patch from lark.
20671 - Fix a crash that occurs on exit nodes when a nameserver request
20672 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
20673 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
20675 - Do not assume that a stack-allocated character array will be
20676 64-bit aligned on platforms that demand that uint64_t access is
20677 aligned. Possible fix for bug 604.
20678 - Parse dates and IPv4 addresses in a locale- and libc-independent
20679 manner, to avoid platform-dependent behavior on malformed input.
20680 - Build correctly when configured to build outside the main source
20681 path. Patch from Michael Gold.
20682 - We were already rejecting relay begin cells with destination port
20683 of 0. Now also reject extend cells with destination port or address
20684 of 0. Suggested by lark.
20686 o Minor bugfixes (on 0.2.1.x):
20687 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
20688 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
20689 - If we're an exit node, scrub the IP address to which we are exiting
20690 in the logs. Bugfix on 0.2.1.8-alpha.
20693 - On Linux, use the prctl call to re-enable core dumps when the user
20695 - New controller event NEWCONSENSUS that lists the networkstatus
20696 lines for every recommended relay. Now controllers like Torflow
20697 can keep up-to-date on which relays they should be using.
20698 - Update to the "February 26 2009" ip-to-country file.
20701 Changes in version 0.2.0.34 - 2009-02-08
20702 Tor 0.2.0.34 features several more security-related fixes. You should
20703 upgrade, especially if you run an exit relay (remote crash) or a
20704 directory authority (remote infinite loop), or you're on an older
20705 (pre-XP) or not-recently-patched Windows (remote exploit).
20707 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
20708 have many known flaws, and nobody should be using them. You should
20709 upgrade. If you're using a Linux or BSD and its packages are obsolete,
20710 stop using those packages and upgrade anyway.
20713 - Fix an infinite-loop bug on handling corrupt votes under certain
20714 circumstances. Bugfix on 0.2.0.8-alpha.
20715 - Fix a temporary DoS vulnerability that could be performed by
20716 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
20717 - Avoid a potential crash on exit nodes when processing malformed
20718 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
20719 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
20720 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
20723 - Fix compilation on systems where time_t is a 64-bit integer.
20724 Patch from Matthias Drochner.
20725 - Don't consider expiring already-closed client connections. Fixes
20726 bug 893. Bugfix on 0.0.2pre20.
20729 Changes in version 0.2.1.12-alpha - 2009-02-08
20730 Tor 0.2.1.12-alpha features several more security-related fixes. You
20731 should upgrade, especially if you run an exit relay (remote crash) or
20732 a directory authority (remote infinite loop), or you're on an older
20733 (pre-XP) or not-recently-patched Windows (remote exploit). It also
20734 includes a big pile of minor bugfixes and cleanups.
20737 - Fix an infinite-loop bug on handling corrupt votes under certain
20738 circumstances. Bugfix on 0.2.0.8-alpha.
20739 - Fix a temporary DoS vulnerability that could be performed by
20740 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
20741 - Avoid a potential crash on exit nodes when processing malformed
20742 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
20745 - Let controllers actually ask for the "clients_seen" event for
20746 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
20747 reported by Matt Edman.
20748 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
20750 - Fix a bug in address parsing that was preventing bridges or hidden
20751 service targets from being at IPv6 addresses.
20752 - Solve a bug that kept hardware crypto acceleration from getting
20753 enabled when accounting was turned on. Fixes bug 907. Bugfix on
20755 - Remove a bash-ism from configure.in to build properly on non-Linux
20756 platforms. Bugfix on 0.2.1.1-alpha.
20757 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
20758 headers. Bugfix on 0.2.0.10-alpha.
20759 - Don't consider expiring already-closed client connections. Fixes
20760 bug 893. Bugfix on 0.0.2pre20.
20761 - Fix another interesting corner-case of bug 891 spotted by rovv:
20762 Previously, if two hosts had different amounts of clock drift, and
20763 one of them created a new connection with just the wrong timing,
20764 the other might decide to deprecate the new connection erroneously.
20765 Bugfix on 0.1.1.13-alpha.
20766 - Resolve a very rare crash bug that could occur when the user forced
20767 a nameserver reconfiguration during the middle of a nameserver
20768 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
20769 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
20770 Bugfix on 0.2.1.7-alpha.
20771 - If we're using bridges and our network goes away, be more willing
20772 to forgive our bridges and try again when we get an application
20773 request. Bugfix on 0.2.0.x.
20776 - Support platforms where time_t is 64 bits long. (Congratulations,
20777 NetBSD!) Patch from Matthias Drochner.
20778 - Add a 'getinfo status/clients-seen' controller command, in case
20779 controllers want to hear clients_seen events but connect late.
20782 - Disable GCC's strict alias optimization by default, to avoid the
20783 likelihood of its introducing subtle bugs whenever our code violates
20784 the letter of C99's alias rules.
20787 Changes in version 0.2.0.33 - 2009-01-21
20788 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
20789 useful to users. It also finally fixes a bug where a relay or client
20790 that's been off for many days would take a long time to bootstrap.
20792 This update also fixes an important security-related bug reported by
20793 Ilja van Sprundel. You should upgrade. (We'll send out more details
20794 about the bug once people have had some time to upgrade.)
20797 - Fix a heap-corruption bug that may be remotely triggerable on
20798 some platforms. Reported by Ilja van Sprundel.
20801 - When a stream at an exit relay is in state "resolving" or
20802 "connecting" and it receives an "end" relay cell, the exit relay
20803 would silently ignore the end cell and not close the stream. If
20804 the client never closes the circuit, then the exit relay never
20805 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
20806 reported by "wood".
20807 - When sending CREATED cells back for a given circuit, use a 64-bit
20808 connection ID to find the right connection, rather than an addr:port
20809 combination. Now that we can have multiple OR connections between
20810 the same ORs, it is no longer possible to use addr:port to uniquely
20811 identify a connection.
20812 - Bridge relays that had DirPort set to 0 would stop fetching
20813 descriptors shortly after startup, and then briefly resume
20814 after a new bandwidth test and/or after publishing a new bridge
20815 descriptor. Bridge users that try to bootstrap from them would
20816 get a recent networkstatus but would get descriptors from up to
20817 18 hours earlier, meaning most of the descriptors were obsolete
20818 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
20819 - Prevent bridge relays from serving their 'extrainfo' document
20820 to anybody who asks, now that extrainfo docs include potentially
20821 sensitive aggregated client geoip summaries. Bugfix on
20823 - If the cached networkstatus consensus is more than five days old,
20824 discard it rather than trying to use it. In theory it could be
20825 useful because it lists alternate directory mirrors, but in practice
20826 it just means we spend many minutes trying directory mirrors that
20827 are long gone from the network. Also discard router descriptors as
20828 we load them if they are more than five days old, since the onion
20829 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
20832 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
20833 could make gcc generate non-functional binary search code. Bugfix
20835 - Build correctly on platforms without socklen_t.
20836 - Compile without warnings on solaris.
20837 - Avoid potential crash on internal error during signature collection.
20838 Fixes bug 864. Patch from rovv.
20839 - Correct handling of possible malformed authority signing key
20840 certificates with internal signature types. Fixes bug 880.
20841 Bugfix on 0.2.0.3-alpha.
20842 - Fix a hard-to-trigger resource leak when logging credential status.
20844 - When we can't initialize DNS because the network is down, do not
20845 automatically stop Tor from starting. Instead, we retry failed
20846 dns_init() every 10 minutes, and change the exit policy to reject
20847 *:* until one succeeds. Fixes bug 691.
20848 - Use 64 bits instead of 32 bits for connection identifiers used with
20849 the controller protocol, to greatly reduce risk of identifier reuse.
20850 - When we're choosing an exit node for a circuit, and we have
20851 no pending streams, choose a good general exit rather than one that
20852 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
20853 - Fix another case of assuming, when a specific exit is requested,
20854 that we know more than the user about what hosts it allows.
20855 Fixes one case of bug 752. Patch from rovv.
20856 - Clip the MaxCircuitDirtiness config option to a minimum of 10
20857 seconds. Warn the user if lower values are given in the
20858 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
20859 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
20860 user if lower values are given in the configuration. Bugfix on
20861 0.1.1.17-rc. Patch by Sebastian.
20862 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
20863 the cache because we already had a v0 descriptor with the same ID.
20864 Bugfix on 0.2.0.18-alpha.
20865 - Fix a race condition when freeing keys shared between main thread
20866 and CPU workers that could result in a memory leak. Bugfix on
20867 0.1.0.1-rc. Fixes bug 889.
20868 - Send a valid END cell back when a client tries to connect to a
20869 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
20870 840. Patch from rovv.
20871 - Check which hops rendezvous stream cells are associated with to
20872 prevent possible guess-the-streamid injection attacks from
20873 intermediate hops. Fixes another case of bug 446. Based on patch
20875 - If a broken client asks a non-exit router to connect somewhere,
20876 do not even do the DNS lookup before rejecting the connection.
20877 Fixes another case of bug 619. Patch from rovv.
20878 - When a relay gets a create cell it can't decrypt (e.g. because it's
20879 using the wrong onion key), we were dropping it and letting the
20880 client time out. Now actually answer with a destroy cell. Fixes
20881 bug 904. Bugfix on 0.0.2pre8.
20883 o Minor bugfixes (hidden services):
20884 - Do not throw away existing introduction points on SIGHUP. Bugfix on
20885 0.0.6pre1. Patch by Karsten. Fixes bug 874.
20888 - Report the case where all signatures in a detached set are rejected
20889 differently than the case where there is an error handling the
20891 - When we realize that another process has modified our cached
20892 descriptors, print out a more useful error message rather than
20893 triggering an assertion. Fixes bug 885. Patch from Karsten.
20894 - Implement the 0x20 hack to better resist DNS poisoning: set the
20895 case on outgoing DNS requests randomly, and reject responses that do
20896 not match the case correctly. This logic can be disabled with the
20897 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
20898 of servers that do not reliably preserve case in replies. See
20899 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
20901 - Check DNS replies for more matching fields to better resist DNS
20903 - Never use OpenSSL compression: it wastes RAM and CPU trying to
20904 compress cells, which are basically all encrypted, compressed, or
20908 Changes in version 0.2.1.11-alpha - 2009-01-20
20909 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
20910 week it will take a long time to bootstrap again" bug. It also fixes
20911 an important security-related bug reported by Ilja van Sprundel. You
20912 should upgrade. (We'll send out more details about the bug once people
20913 have had some time to upgrade.)
20916 - Fix a heap-corruption bug that may be remotely triggerable on
20917 some platforms. Reported by Ilja van Sprundel.
20920 - Discard router descriptors as we load them if they are more than
20921 five days old. Otherwise if Tor is off for a long time and then
20922 starts with cached descriptors, it will try to use the onion
20923 keys in those obsolete descriptors when building circuits. Bugfix
20924 on 0.2.0.x. Fixes bug 887.
20927 - Try to make sure that the version of Libevent we're running with
20928 is binary-compatible with the one we built with. May address bug
20930 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
20931 for bug 905. Bugfix on 0.2.1.7-alpha.
20932 - Add a new --enable-local-appdata configuration switch to change
20933 the default location of the datadir on win32 from APPDATA to
20934 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
20935 entirely. Patch from coderman.
20938 - Make outbound DNS packets respect the OutboundBindAddress setting.
20939 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
20940 - When our circuit fails at the first hop (e.g. we get a destroy
20941 cell back), avoid using that OR connection anymore, and also
20942 tell all the one-hop directory requests waiting for it that they
20943 should fail. Bugfix on 0.2.1.3-alpha.
20944 - In the torify(1) manpage, mention that tsocks will leak your
20948 Changes in version 0.2.1.10-alpha - 2009-01-06
20949 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
20950 would make the bridge relay not so useful if it had DirPort set to 0,
20951 and one that could let an attacker learn a little bit of information
20952 about the bridge's users), and a bug that would cause your Tor relay
20953 to ignore a circuit create request it can't decrypt (rather than reply
20954 with an error). It also fixes a wide variety of other bugs.
20957 - If the cached networkstatus consensus is more than five days old,
20958 discard it rather than trying to use it. In theory it could
20959 be useful because it lists alternate directory mirrors, but in
20960 practice it just means we spend many minutes trying directory
20961 mirrors that are long gone from the network. Helps bug 887 a bit;
20963 - Bridge relays that had DirPort set to 0 would stop fetching
20964 descriptors shortly after startup, and then briefly resume
20965 after a new bandwidth test and/or after publishing a new bridge
20966 descriptor. Bridge users that try to bootstrap from them would
20967 get a recent networkstatus but would get descriptors from up to
20968 18 hours earlier, meaning most of the descriptors were obsolete
20969 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
20970 - Prevent bridge relays from serving their 'extrainfo' document
20971 to anybody who asks, now that extrainfo docs include potentially
20972 sensitive aggregated client geoip summaries. Bugfix on
20976 - New controller event "clients_seen" to report a geoip-based summary
20977 of which countries we've seen clients from recently. Now controllers
20978 like Vidalia can show bridge operators that they're actually making
20980 - Build correctly against versions of OpenSSL 0.9.8 or later built
20981 without support for deprecated functions.
20982 - Update to the "December 19 2008" ip-to-country file.
20984 o Minor bugfixes (on 0.2.0.x):
20985 - Authorities now vote for the Stable flag for any router whose
20986 weighted MTBF is at least 5 days, regardless of the mean MTBF.
20987 - Do not remove routers as too old if we do not have any consensus
20988 document. Bugfix on 0.2.0.7-alpha.
20989 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
20990 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
20991 - When an exit relay resolves a stream address to a local IP address,
20992 do not just keep retrying that same exit relay over and
20993 over. Instead, just close the stream. Addresses bug 872. Bugfix
20994 on 0.2.0.32. Patch from rovv.
20995 - If a hidden service sends us an END cell, do not consider
20996 retrying the connection; just close it. Patch from rovv.
20997 - When we made bridge authorities stop serving bridge descriptors over
20998 unencrypted links, we also broke DirPort reachability testing for
20999 bridges. So bridges with a non-zero DirPort were printing spurious
21000 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
21001 - When a relay gets a create cell it can't decrypt (e.g. because it's
21002 using the wrong onion key), we were dropping it and letting the
21003 client time out. Now actually answer with a destroy cell. Fixes
21004 bug 904. Bugfix on 0.0.2pre8.
21005 - Squeeze 2-5% out of client performance (according to oprofile) by
21006 improving the implementation of some policy-manipulation functions.
21008 o Minor bugfixes (on 0.2.1.x):
21009 - Make get_interface_address() function work properly again; stop
21010 guessing the wrong parts of our address as our address.
21011 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
21012 send on that circuit. Otherwise we might violate the proposal-110
21013 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
21015 - When we're sending non-EXTEND cells to the first hop in a circuit,
21016 for example to use an encrypted directory connection, we don't need
21017 to use RELAY_EARLY cells: the first hop knows what kind of cell
21018 it is, and nobody else can even see the cell type. Conserving
21019 RELAY_EARLY cells makes it easier to cannibalize circuits like
21021 - Stop logging nameserver addresses in reverse order.
21022 - If we are retrying a directory download slowly over and over, do
21023 not automatically give up after the 254th failure. Bugfix on
21025 - Resume reporting accurate "stream end" reasons to the local control
21026 port. They were lost in the changes for Proposal 148. Bugfix on
21029 o Deprecated and removed features:
21030 - The old "tor --version --version" command, which would print out
21031 the subversion "Id" of most of the source files, is now removed. It
21032 turned out to be less useful than we'd expected, and harder to
21035 o Code simplifications and refactoring:
21036 - Change our header file guard macros to be less likely to conflict
21037 with system headers. Adam Langley noticed that we were conflicting
21038 with log.h on Android.
21039 - Tool-assisted documentation cleanup. Nearly every function or
21040 static variable in Tor should have its own documentation now.
21043 Changes in version 0.2.1.9-alpha - 2008-12-25
21044 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
21046 o New directory authorities:
21047 - gabelmoo (the authority run by Karsten Loesing) now has a new
21051 - Never use a connection with a mismatched address to extend a
21052 circuit, unless that connection is canonical. A canonical
21053 connection is one whose address is authenticated by the router's
21054 identity key, either in a NETINFO cell or in a router descriptor.
21055 - Avoid a possible memory corruption bug when receiving hidden service
21056 descriptors. Bugfix on 0.2.1.6-alpha.
21059 - Fix a logic error that would automatically reject all but the first
21060 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
21061 part of bug 813/868. Bug spotted by coderman.
21062 - When a stream at an exit relay is in state "resolving" or
21063 "connecting" and it receives an "end" relay cell, the exit relay
21064 would silently ignore the end cell and not close the stream. If
21065 the client never closes the circuit, then the exit relay never
21066 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
21067 reported by "wood".
21068 - When we can't initialize DNS because the network is down, do not
21069 automatically stop Tor from starting. Instead, retry failed
21070 dns_init() every 10 minutes, and change the exit policy to reject
21071 *:* until one succeeds. Fixes bug 691.
21074 - Give a better error message when an overzealous init script says
21075 "sudo -u username tor --user username". Makes Bug 882 easier for
21077 - When a directory authority gives us a new guess for our IP address,
21078 log which authority we used. Hopefully this will help us debug
21079 the recent complaints about bad IP address guesses.
21080 - Detect svn revision properly when we're using git-svn.
21081 - Try not to open more than one descriptor-downloading connection
21082 to an authority at once. This should reduce load on directory
21083 authorities. Fixes bug 366.
21084 - Add cross-certification to newly generated certificates, so that
21085 a signing key is enough information to look up a certificate.
21086 Partial implementation of proposal 157.
21087 - Start serving certificates by <identity digest, signing key digest>
21088 pairs. Partial implementation of proposal 157.
21089 - Clients now never report any stream end reason except 'MISC'.
21090 Implements proposal 148.
21091 - On platforms with a maximum syslog string length, truncate syslog
21092 messages to that length ourselves, rather than relying on the
21093 system to do it for us.
21094 - Optimize out calls to time(NULL) that occur for every IO operation,
21095 or for every cell. On systems where time() is a slow syscall,
21096 this fix will be slightly helpful.
21097 - Exit servers can now answer resolve requests for ip6.arpa addresses.
21098 - When we download a descriptor that we then immediately (as
21099 a directory authority) reject, do not retry downloading it right
21100 away. Should save some bandwidth on authorities. Fix for bug
21101 888. Patch by Sebastian Hahn.
21102 - When a download gets us zero good descriptors, do not notify
21103 Tor that new directory information has arrived.
21104 - Avoid some nasty corner cases in the logic for marking connections
21105 as too old or obsolete or noncanonical for circuits. Partial
21108 o Minor features (controller):
21109 - New CONSENSUS_ARRIVED event to note when a new consensus has
21110 been fetched and validated.
21111 - When we realize that another process has modified our cached
21112 descriptors file, print out a more useful error message rather
21113 than triggering an assertion. Fixes bug 885. Patch from Karsten.
21114 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
21115 controllers to prevent SIGHUP from reloading the
21116 configuration. Fixes bug 856.
21119 - Resume using the correct "REASON=" stream when telling the
21120 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
21121 - When a canonical connection appears later in our internal list
21122 than a noncanonical one for a given OR ID, always use the
21123 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
21125 - Clip the MaxCircuitDirtiness config option to a minimum of 10
21126 seconds. Warn the user if lower values are given in the
21127 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
21128 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
21129 user if lower values are given in the configuration. Bugfix on
21130 0.1.1.17-rc. Patch by Sebastian.
21131 - Fix a race condition when freeing keys shared between main thread
21132 and CPU workers that could result in a memory leak. Bugfix on
21133 0.1.0.1-rc. Fixes bug 889.
21135 o Minor bugfixes (hidden services):
21136 - Do not throw away existing introduction points on SIGHUP (bugfix on
21137 0.0.6pre1); also, do not stall hidden services because we're
21138 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
21139 by John Brooks. Patch by Karsten. Fixes bug 874.
21140 - Fix a memory leak when we decline to add a v2 rendezvous
21141 descriptor to the cache because we already had a v0 descriptor
21142 with the same ID. Bugfix on 0.2.0.18-alpha.
21144 o Deprecated and removed features:
21145 - RedirectExits has been removed. It was deprecated since
21147 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
21148 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
21149 - Cell pools are now always enabled; --disable-cell-pools is ignored.
21151 o Code simplifications and refactoring:
21152 - Rename the confusing or_is_obsolete field to the more appropriate
21153 is_bad_for_new_circs, and move it to or_connection_t where it
21155 - Move edge-only flags from connection_t to edge_connection_t: not
21156 only is this better coding, but on machines of plausible alignment,
21157 it should save 4-8 bytes per connection_t. "Every little bit helps."
21158 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
21159 for consistency; keep old option working for backward compatibility.
21160 - Simplify the code for finding connections to use for a circuit.
21163 Changes in version 0.2.1.8-alpha - 2008-12-08
21164 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
21165 builds better on unusual platforms like Solaris and old OS X, and
21166 fixes a variety of other issues.
21169 - New DirPortFrontPage option that takes an html file and publishes
21170 it as "/" on the DirPort. Now relay operators can provide a
21171 disclaimer without needing to set up a separate webserver. There's
21172 a sample disclaimer in contrib/tor-exit-notice.html.
21175 - When the client is choosing entry guards, now it selects at most
21176 one guard from a given relay family. Otherwise we could end up with
21177 all of our entry points into the network run by the same operator.
21178 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
21181 - Fix a DOS opportunity during the voting signature collection process
21182 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
21183 - Fix a possible segfault when establishing an exit connection. Bugfix
21187 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
21189 - Made Tor a little less aggressive about deleting expired
21190 certificates. Partial fix for bug 854.
21191 - Stop doing unaligned memory access that generated bus errors on
21192 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
21193 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
21194 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
21195 - Make USR2 log-level switch take effect immediately. Bugfix on
21197 - If one win32 nameserver fails to get added, continue adding the
21198 rest, and don't automatically fail.
21199 - Use fcntl() for locking when flock() is not available. Should fix
21200 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
21201 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
21202 could make gcc generate non-functional binary search code. Bugfix
21204 - Build correctly on platforms without socklen_t.
21205 - Avoid potential crash on internal error during signature collection.
21206 Fixes bug 864. Patch from rovv.
21207 - Do not use C's stdio library for writing to log files. This will
21208 improve logging performance by a minute amount, and will stop
21209 leaking fds when our disk is full. Fixes bug 861.
21210 - Stop erroneous use of O_APPEND in cases where we did not in fact
21211 want to re-seek to the end of a file before every last write().
21212 - Correct handling of possible malformed authority signing key
21213 certificates with internal signature types. Fixes bug 880. Bugfix
21215 - Fix a hard-to-trigger resource leak when logging credential status.
21219 - Directory mirrors no longer fetch the v1 directory or
21220 running-routers files. They are obsolete, and nobody asks for them
21221 anymore. This is the first step to making v1 authorities obsolete.
21223 o Minor features (controller):
21224 - Return circuit purposes in response to GETINFO circuit-status. Fixes
21228 Changes in version 0.2.0.32 - 2008-11-20
21229 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
21230 packages (and maybe other packages) noticed by Theo de Raadt, fixes
21231 a smaller security flaw that might allow an attacker to access local
21232 services, further improves hidden service performance, and fixes a
21233 variety of other issues.
21236 - The "User" and "Group" config options did not clear the
21237 supplementary group entries for the Tor process. The "User" option
21238 is now more robust, and we now set the groups to the specified
21239 user's primary group. The "Group" option is now ignored. For more
21240 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
21241 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
21242 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
21243 - The "ClientDNSRejectInternalAddresses" config option wasn't being
21244 consistently obeyed: if an exit relay refuses a stream because its
21245 exit policy doesn't allow it, we would remember what IP address
21246 the relay said the destination address resolves to, even if it's
21247 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
21250 - Fix a DOS opportunity during the voting signature collection process
21251 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
21253 o Major bugfixes (hidden services):
21254 - When fetching v0 and v2 rendezvous service descriptors in parallel,
21255 we were failing the whole hidden service request when the v0
21256 descriptor fetch fails, even if the v2 fetch is still pending and
21257 might succeed. Similarly, if the last v2 fetch fails, we were
21258 failing the whole hidden service request even if a v0 fetch is
21259 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
21260 - When extending a circuit to a hidden service directory to upload a
21261 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
21262 requests failed, because the router descriptor has not been
21263 downloaded yet. In these cases, do not attempt to upload the
21264 rendezvous descriptor, but wait until the router descriptor is
21265 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
21266 descriptor from a hidden service directory for which the router
21267 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
21271 - Fix several infrequent memory leaks spotted by Coverity.
21272 - When testing for libevent functions, set the LDFLAGS variable
21273 correctly. Found by Riastradh.
21274 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
21275 bootstrapping with tunneled directory connections. Bugfix on
21276 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
21277 - When asked to connect to A.B.exit:80, if we don't know the IP for A
21278 and we know that server B rejects most-but-not all connections to
21279 port 80, we would previously reject the connection. Now, we assume
21280 the user knows what they were asking for. Fixes bug 752. Bugfix
21281 on 0.0.9rc5. Diagnosed by BarkerJr.
21282 - If we overrun our per-second write limits a little, count this as
21283 having used up our write allocation for the second, and choke
21284 outgoing directory writes. Previously, we had only counted this when
21285 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
21286 Bugfix on 0.2.0.x (??).
21287 - Remove the old v2 directory authority 'lefkada' from the default
21288 list. It has been gone for many months.
21289 - Stop doing unaligned memory access that generated bus errors on
21290 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
21291 - Make USR2 log-level switch take effect immediately. Bugfix on
21294 o Minor bugfixes (controller):
21295 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
21296 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
21299 Changes in version 0.2.1.7-alpha - 2008-11-08
21300 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
21301 packages (and maybe other packages) noticed by Theo de Raadt, fixes
21302 a smaller security flaw that might allow an attacker to access local
21303 services, adds better defense against DNS poisoning attacks on exit
21304 relays, further improves hidden service performance, and fixes a
21305 variety of other issues.
21308 - The "ClientDNSRejectInternalAddresses" config option wasn't being
21309 consistently obeyed: if an exit relay refuses a stream because its
21310 exit policy doesn't allow it, we would remember what IP address
21311 the relay said the destination address resolves to, even if it's
21312 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
21313 - The "User" and "Group" config options did not clear the
21314 supplementary group entries for the Tor process. The "User" option
21315 is now more robust, and we now set the groups to the specified
21316 user's primary group. The "Group" option is now ignored. For more
21317 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
21318 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
21319 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
21320 - Do not use or believe expired v3 authority certificates. Patch
21321 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
21324 - Now NodeFamily and MyFamily config options allow spaces in
21325 identity fingerprints, so it's easier to paste them in.
21326 Suggested by Lucky Green.
21327 - Implement the 0x20 hack to better resist DNS poisoning: set the
21328 case on outgoing DNS requests randomly, and reject responses that do
21329 not match the case correctly. This logic can be disabled with the
21330 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
21331 of servers that do not reliably preserve case in replies. See
21332 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
21334 - Preserve case in replies to DNSPort requests in order to support
21335 the 0x20 hack for resisting DNS poisoning attacks.
21337 o Hidden service performance improvements:
21338 - When the client launches an introduction circuit, retry with a
21339 new circuit after 30 seconds rather than 60 seconds.
21340 - Launch a second client-side introduction circuit in parallel
21341 after a delay of 15 seconds (based on work by Christian Wilms).
21342 - Hidden services start out building five intro circuits rather
21343 than three, and when the first three finish they publish a service
21344 descriptor using those. Now we publish our service descriptor much
21345 faster after restart.
21348 - Minor fix in the warning messages when you're having problems
21349 bootstrapping; also, be more forgiving of bootstrap problems when
21350 we're still making incremental progress on a given bootstrap phase.
21351 - When we're choosing an exit node for a circuit, and we have
21352 no pending streams, choose a good general exit rather than one that
21353 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
21354 - Send a valid END cell back when a client tries to connect to a
21355 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
21356 840. Patch from rovv.
21357 - If a broken client asks a non-exit router to connect somewhere,
21358 do not even do the DNS lookup before rejecting the connection.
21359 Fixes another case of bug 619. Patch from rovv.
21360 - Fix another case of assuming, when a specific exit is requested,
21361 that we know more than the user about what hosts it allows.
21362 Fixes another case of bug 752. Patch from rovv.
21363 - Check which hops rendezvous stream cells are associated with to
21364 prevent possible guess-the-streamid injection attacks from
21365 intermediate hops. Fixes another case of bug 446. Based on patch
21367 - Avoid using a negative right-shift when comparing 32-bit
21368 addresses. Possible fix for bug 845 and bug 811.
21369 - Make the assert_circuit_ok() function work correctly on circuits that
21370 have already been marked for close.
21371 - Fix read-off-the-end-of-string error in unit tests when decoding
21372 introduction points.
21373 - Fix uninitialized size field for memory area allocation: may improve
21374 memory performance during directory parsing.
21375 - Treat duplicate certificate fetches as failures, so that we do
21376 not try to re-fetch an expired certificate over and over and over.
21377 - Do not say we're fetching a certificate when we'll in fact skip it
21378 because of a pending download.
21381 Changes in version 0.2.1.6-alpha - 2008-09-30
21382 Tor 0.2.1.6-alpha further improves performance and robustness of
21383 hidden services, starts work on supporting per-country relay selection,
21384 and fixes a variety of smaller issues.
21387 - Implement proposal 121: make it possible to build hidden services
21388 that only certain clients are allowed to connect to. This is
21389 enforced at several points, so that unauthorized clients are unable
21390 to send INTRODUCE cells to the service, or even (depending on the
21391 type of authentication) to learn introduction points. This feature
21392 raises the bar for certain kinds of active attacks against hidden
21393 services. Code by Karsten Loesing.
21394 - Relays now store and serve v2 hidden service descriptors by default,
21395 i.e., the new default value for HidServDirectoryV2 is 1. This is
21396 the last step in proposal 114, which aims to make hidden service
21397 lookups more reliable.
21398 - Start work to allow node restrictions to include country codes. The
21399 syntax to exclude nodes in a country with country code XX is
21400 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
21401 refinement to decide what config options should take priority if
21402 you ask to both use a particular node and exclude it.
21403 - Allow ExitNodes list to include IP ranges and country codes, just
21404 like the Exclude*Nodes lists. Patch from Robert Hogan.
21407 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
21408 Tor to fail to start if you had it configured to use a bridge
21409 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
21410 - When extending a circuit to a hidden service directory to upload a
21411 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
21412 requests failed, because the router descriptor had not been
21413 downloaded yet. In these cases, we now wait until the router
21414 descriptor is downloaded, and then retry. Likewise, clients
21415 now skip over a hidden service directory if they don't yet have
21416 its router descriptor, rather than futilely requesting it and
21417 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
21419 - When fetching v0 and v2 rendezvous service descriptors in parallel,
21420 we were failing the whole hidden service request when the v0
21421 descriptor fetch fails, even if the v2 fetch is still pending and
21422 might succeed. Similarly, if the last v2 fetch fails, we were
21423 failing the whole hidden service request even if a v0 fetch is
21424 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
21425 - DNS replies need to have names matching their requests, but
21426 these names should be in the questions section, not necessarily
21427 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
21430 - Update to the "September 1 2008" ip-to-country file.
21431 - Allow ports 465 and 587 in the default exit policy again. We had
21432 rejected them in 0.1.0.15, because back in 2005 they were commonly
21433 misconfigured and ended up as spam targets. We hear they are better
21434 locked down these days.
21435 - Use a lockfile to make sure that two Tor processes are not
21436 simultaneously running with the same datadir.
21437 - Serve the latest v3 networkstatus consensus via the control
21438 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
21439 - Better logging about stability/reliability calculations on directory
21441 - Drop the requirement to have an open dir port for storing and
21442 serving v2 hidden service descriptors.
21443 - Directory authorities now serve a /tor/dbg-stability.txt URL to
21444 help debug WFU and MTBF calculations.
21445 - Implement most of Proposal 152: allow specialized servers to permit
21446 single-hop circuits, and clients to use those servers to build
21447 single-hop circuits when using a specialized controller. Patch
21448 from Josh Albrecht. Resolves feature request 768.
21449 - Add a -p option to tor-resolve for specifying the SOCKS port: some
21450 people find host:port too confusing.
21451 - Make TrackHostExit mappings expire a while after their last use, not
21452 after their creation. Patch from Robert Hogan.
21453 - Provide circuit purposes along with circuit events to the controller.
21456 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
21458 - Fixed some memory leaks -- some quite frequent, some almost
21459 impossible to trigger -- based on results from Coverity.
21460 - When testing for libevent functions, set the LDFLAGS variable
21461 correctly. Found by Riastradh.
21462 - Fix an assertion bug in parsing policy-related options; possible fix
21464 - Catch and report a few more bootstrapping failure cases when Tor
21465 fails to establish a TCP connection. Cleanup on 0.2.1.x.
21466 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
21467 bootstrapping with tunneled directory connections. Bugfix on
21468 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
21469 - When asked to connect to A.B.exit:80, if we don't know the IP for A
21470 and we know that server B rejects most-but-not all connections to
21471 port 80, we would previously reject the connection. Now, we assume
21472 the user knows what they were asking for. Fixes bug 752. Bugfix
21473 on 0.0.9rc5. Diagnosed by BarkerJr.
21474 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
21475 service directories if they have no advertised dir port. Bugfix
21477 - If we overrun our per-second write limits a little, count this as
21478 having used up our write allocation for the second, and choke
21479 outgoing directory writes. Previously, we had only counted this when
21480 we had met our limits precisely. Fixes bug 824. Patch by rovv.
21481 Bugfix on 0.2.0.x (??).
21482 - Avoid a "0 divided by 0" calculation when calculating router uptime
21483 at directory authorities. Bugfix on 0.2.0.8-alpha.
21484 - Make DNS resolved controller events into "CLOSED", not
21485 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
21487 - Fix a bug where an unreachable relay would establish enough
21488 reachability testing circuits to do a bandwidth test -- if
21489 we already have a connection to the middle hop of the testing
21490 circuit, then it could establish the last hop by using the existing
21491 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
21492 circuits no longer use entry guards in 0.2.1.3-alpha.
21493 - If we have correct permissions on $datadir, we complain to stdout
21494 and fail to start. But dangerous permissions on
21495 $datadir/cached-status/ would cause us to open a log and complain
21496 there. Now complain to stdout and fail to start in both cases. Fixes
21497 bug 820, reported by seeess.
21498 - Remove the old v2 directory authority 'lefkada' from the default
21499 list. It has been gone for many months.
21501 o Code simplifications and refactoring:
21502 - Revise the connection_new functions so that a more typesafe variant
21503 exists. This will work better with Coverity, and let us find any
21504 actual mistakes we're making here.
21505 - Refactor unit testing logic so that dmalloc can be used sensibly
21506 with unit tests to check for memory leaks.
21507 - Move all hidden-service related fields from connection and circuit
21508 structure to substructures: this way they won't eat so much memory.
21511 Changes in version 0.2.0.31 - 2008-09-03
21512 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
21513 a big bug we're seeing where in rare cases traffic from one Tor stream
21514 gets mixed into another stream, and fixes a variety of smaller issues.
21517 - Make sure that two circuits can never exist on the same connection
21518 with the same circuit ID, even if one is marked for close. This
21519 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
21520 - Relays now reject risky extend cells: if the extend cell includes
21521 a digest of all zeroes, or asks to extend back to the relay that
21522 sent the extend cell, tear down the circuit. Ideas suggested
21524 - If not enough of our entry guards are available so we add a new
21525 one, we might use the new one even if it overlapped with the
21526 current circuit's exit relay (or its family). Anonymity bugfix
21527 pointed out by rovv.
21530 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
21531 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
21532 - Correctly detect the presence of the linux/netfilter_ipv4.h header
21533 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
21534 - Pick size of default geoip filename string correctly on windows.
21535 Fixes bug 806. Bugfix on 0.2.0.30.
21536 - Make the autoconf script accept the obsolete --with-ssl-dir
21537 option as an alias for the actually-working --with-openssl-dir
21538 option. Fix the help documentation to recommend --with-openssl-dir.
21539 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
21540 - When using the TransPort option on OpenBSD, and using the User
21541 option to change UID and drop privileges, make sure to open
21542 /dev/pf before dropping privileges. Fixes bug 782. Patch from
21543 Christopher Davis. Bugfix on 0.1.2.1-alpha.
21544 - Try to attach connections immediately upon receiving a RENDEZVOUS2
21545 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
21546 on the client side when connecting to a hidden service. Bugfix
21547 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
21548 - When closing an application-side connection because its circuit is
21549 getting torn down, generate the stream event correctly. Bugfix on
21550 0.1.2.x. Anonymous patch.
21553 Changes in version 0.2.1.5-alpha - 2008-08-31
21554 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
21555 in a lot of the infrastructure for adding authorization to hidden
21556 services, lays the groundwork for having clients read their load
21557 balancing information out of the networkstatus consensus rather than
21558 the individual router descriptors, addresses two potential anonymity
21559 issues, and fixes a variety of smaller issues.
21562 - Convert many internal address representations to optionally hold
21564 - Generate and accept IPv6 addresses in many protocol elements.
21565 - Make resolver code handle nameservers located at ipv6 addresses.
21566 - Begin implementation of proposal 121 ("Client authorization for
21567 hidden services"): configure hidden services with client
21568 authorization, publish descriptors for them, and configure
21569 authorization data for hidden services at clients. The next
21570 step is to actually access hidden services that perform client
21572 - More progress toward proposal 141: Network status consensus
21573 documents and votes now contain bandwidth information for each
21574 router and a summary of that router's exit policy. Eventually this
21575 will be used by clients so that they do not have to download every
21576 known descriptor before building circuits.
21578 o Major bugfixes (on 0.2.0.x and before):
21579 - When sending CREATED cells back for a given circuit, use a 64-bit
21580 connection ID to find the right connection, rather than an addr:port
21581 combination. Now that we can have multiple OR connections between
21582 the same ORs, it is no longer possible to use addr:port to uniquely
21583 identify a connection.
21584 - Relays now reject risky extend cells: if the extend cell includes
21585 a digest of all zeroes, or asks to extend back to the relay that
21586 sent the extend cell, tear down the circuit. Ideas suggested
21588 - If not enough of our entry guards are available so we add a new
21589 one, we might use the new one even if it overlapped with the
21590 current circuit's exit relay (or its family). Anonymity bugfix
21591 pointed out by rovv.
21594 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
21595 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
21596 - When using the TransPort option on OpenBSD, and using the User
21597 option to change UID and drop privileges, make sure to open /dev/pf
21598 before dropping privileges. Fixes bug 782. Patch from Christopher
21599 Davis. Bugfix on 0.1.2.1-alpha.
21600 - Correctly detect the presence of the linux/netfilter_ipv4.h header
21601 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
21602 - Add a missing safe_str() call for a debug log message.
21603 - Use 64 bits instead of 32 bits for connection identifiers used with
21604 the controller protocol, to greatly reduce risk of identifier reuse.
21605 - Make the autoconf script accept the obsolete --with-ssl-dir
21606 option as an alias for the actually-working --with-openssl-dir
21607 option. Fix the help documentation to recommend --with-openssl-dir.
21608 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
21611 - Rate-limit too-many-sockets messages: when they happen, they happen
21612 a lot. Resolves bug 748.
21613 - Resist DNS poisoning a little better by making sure that names in
21614 answer sections match.
21615 - Print the SOCKS5 error message string as well as the error code
21616 when a tor-resolve request fails. Patch from Jacob.
21619 Changes in version 0.2.1.4-alpha - 2008-08-04
21620 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
21623 - The address part of exit policies was not correctly written
21624 to router descriptors. This generated router descriptors that failed
21625 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
21627 - Tor triggered a false assert when extending a circuit to a relay
21628 but we already have a connection open to that relay. Noticed by
21629 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
21632 - Fix a hidden service logging bug: in some edge cases, the router
21633 descriptor of a previously picked introduction point becomes
21634 obsolete and we need to give up on it rather than continually
21635 complaining that it has become obsolete. Observed by xiando. Bugfix
21638 o Removed features:
21639 - Take out the TestVia config option, since it was a workaround for
21640 a bug that was fixed in Tor 0.1.1.21.
21643 Changes in version 0.2.1.3-alpha - 2008-08-03
21644 Tor 0.2.1.3-alpha implements most of the pieces to prevent
21645 infinite-length circuit attacks (see proposal 110); fixes a bug that
21646 might cause exit relays to corrupt streams they send back; allows
21647 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
21648 ExcludeExitNodes config options; and fixes a big pile of bugs.
21650 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
21651 - Send a bootstrap problem "warn" event on the first problem if the
21652 reason is NO_ROUTE (that is, our network is down).
21655 - Implement most of proposal 110: The first K cells to be sent
21656 along a circuit are marked as special "early" cells; only K "early"
21657 cells will be allowed. Once this code is universal, we can block
21658 certain kinds of DOS attack by requiring that EXTEND commands must
21659 be sent using an "early" cell.
21662 - Try to attach connections immediately upon receiving a RENDEZVOUS2
21663 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
21664 on the client side when connecting to a hidden service. Bugfix
21665 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
21666 - Ensure that two circuits can never exist on the same connection
21667 with the same circuit ID, even if one is marked for close. This
21668 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
21671 - When relays do their initial bandwidth measurement, don't limit
21672 to just our entry guards for the test circuits. Otherwise we tend
21673 to have multiple test circuits going through a single entry guard,
21674 which makes our bandwidth test less accurate. Fixes part of bug 654;
21675 patch contributed by Josh Albrecht.
21676 - Add an ExcludeExitNodes option so users can list a set of nodes
21677 that should be be excluded from the exit node position, but
21678 allowed elsewhere. Implements proposal 151.
21679 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
21680 ExcludeNodes and ExcludeExitNodes lists.
21681 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
21682 be more efficient. Formerly it was quadratic in the number of
21683 servers; now it should be linear. Fixes bug 509.
21684 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
21685 and n_conn_id_digest fields into a separate structure that's
21686 only needed when the circuit has not yet attached to an n_conn.
21689 - Change the contrib/tor.logrotate script so it makes the new
21690 logs as "_tor:_tor" rather than the default, which is generally
21691 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
21692 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
21693 warnings (occasionally), but it can also cause the compiler to
21694 eliminate error-checking code. Suggested by Peter Gutmann.
21695 - When a hidden service is giving up on an introduction point candidate
21696 that was not included in the last published rendezvous descriptor,
21697 don't reschedule publication of the next descriptor. Fixes bug 763.
21699 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
21700 HiddenServiceExcludeNodes as obsolete: they never worked properly,
21701 and nobody claims to be using them. Fixes bug 754. Bugfix on
21702 0.1.0.1-rc. Patch from Christian Wilms.
21703 - Fix a small alignment and memory-wasting bug on buffer chunks.
21706 o Minor bugfixes (controller):
21707 - When closing an application-side connection because its circuit
21708 is getting torn down, generate the stream event correctly.
21709 Bugfix on 0.1.2.x. Anonymous patch.
21711 o Removed features:
21712 - Remove all backward-compatibility code to support relays running
21713 versions of Tor so old that they no longer work at all on the
21717 Changes in version 0.2.0.30 - 2008-07-15
21719 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
21720 warnings (occasionally), but it can also cause the compiler to
21721 eliminate error-checking code. Suggested by Peter Gutmann.
21724 Changes in version 0.2.0.29-rc - 2008-07-08
21725 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
21726 hidden-service performance bugs, and fixes a bunch of smaller bugs.
21729 - If you have more than one bridge but don't know their keys,
21730 you would only launch a request for the descriptor of the first one
21731 on your list. (Tor considered launching requests for the others, but
21732 found that it already had a connection on the way for $0000...0000
21733 so it didn't open another.) Bugfix on 0.2.0.x.
21734 - If you have more than one bridge but don't know their keys, and the
21735 connection to one of the bridges failed, you would cancel all
21736 pending bridge connections. (After all, they all have the same
21737 digest.) Bugfix on 0.2.0.x.
21738 - When a hidden service was trying to establish an introduction point,
21739 and Tor had built circuits preemptively for such purposes, we
21740 were ignoring all the preemptive circuits and launching a new one
21741 instead. Bugfix on 0.2.0.14-alpha.
21742 - When a hidden service was trying to establish an introduction point,
21743 and Tor *did* manage to reuse one of the preemptively built
21744 circuits, it didn't correctly remember which one it used,
21745 so it asked for another one soon after, until there were no
21746 more preemptive circuits, at which point it launched one from
21747 scratch. Bugfix on 0.0.9.x.
21748 - Make directory servers include the X-Your-Address-Is: http header in
21749 their responses even for begin_dir conns. Now clients who only
21750 ever use begin_dir connections still have a way to learn their IP
21751 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
21754 - Fix a macro/CPP interaction that was confusing some compilers:
21755 some GCCs don't like #if/#endif pairs inside macro arguments.
21757 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
21758 Fixes bug 704; fix from Steven Murdoch.
21759 - When opening /dev/null in finish_daemonize(), do not pass the
21760 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
21761 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
21762 - Correctly detect transparent proxy support on Linux hosts that
21763 require in.h to be included before netfilter_ipv4.h. Patch
21765 - Disallow session resumption attempts during the renegotiation
21766 stage of the v2 handshake protocol. Clients should never be trying
21767 session resumption at this point, but apparently some did, in
21768 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
21769 found by Geoff Goodell.
21772 Changes in version 0.2.1.2-alpha - 2008-06-20
21773 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
21774 make it easier to set up your own private Tor network; fixes several
21775 big bugs with using more than one bridge relay; fixes a big bug with
21776 offering hidden services quickly after Tor starts; and uses a better
21777 API for reporting potential bootstrapping problems to the controller.
21780 - New TestingTorNetwork config option to allow adjustment of
21781 previously constant values that, while reasonable, could slow
21782 bootstrapping. Implements proposal 135. Patch from Karsten.
21785 - If you have more than one bridge but don't know their digests,
21786 you would only learn a request for the descriptor of the first one
21787 on your list. (Tor considered launching requests for the others, but
21788 found that it already had a connection on the way for $0000...0000
21789 so it didn't open another.) Bugfix on 0.2.0.x.
21790 - If you have more than one bridge but don't know their digests,
21791 and the connection to one of the bridges failed, you would cancel
21792 all pending bridge connections. (After all, they all have the
21793 same digest.) Bugfix on 0.2.0.x.
21794 - When establishing a hidden service, introduction points that
21795 originate from cannibalized circuits are completely ignored and not
21796 included in rendezvous service descriptors. This might be another
21797 reason for delay in making a hidden service available. Bugfix
21798 from long ago (0.0.9.x?)
21801 - Allow OpenSSL to use dynamic locks if it wants.
21802 - When building a consensus, do not include routers that are down.
21803 This will cut down 30% to 40% on consensus size. Implements
21805 - In directory authorities' approved-routers files, allow
21806 fingerprints with or without space.
21807 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
21808 controller can query our current bootstrap state in case it attaches
21809 partway through and wants to catch up.
21810 - Send an initial "Starting" bootstrap status event, so we have a
21811 state to start out in.
21814 - Asking for a conditional consensus at .../consensus/<fingerprints>
21815 would crash a dirserver if it did not already have a
21816 consensus. Bugfix on 0.2.1.1-alpha.
21817 - Clean up some macro/CPP interactions: some GCC versions don't like
21818 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
21821 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
21822 - Directory authorities shouldn't complain about bootstrapping
21823 problems just because they do a lot of reachability testing and
21824 some of the connection attempts fail.
21825 - Start sending "count" and "recommendation" key/value pairs in
21826 bootstrap problem status events, so the controller can hear about
21827 problems even before Tor decides they're worth reporting for sure.
21828 - If you're using bridges, generate "bootstrap problem" warnings
21829 as soon as you run out of working bridges, rather than waiting
21830 for ten failures -- which will never happen if you have less than
21832 - If we close our OR connection because there's been a circuit
21833 pending on it for too long, we were telling our bootstrap status
21834 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
21837 Changes in version 0.2.1.1-alpha - 2008-06-13
21838 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
21839 were making the Tor process bloat especially on Linux; makes our TLS
21840 handshake blend in better; sends "bootstrap phase" status events to
21841 the controller, so it can keep the user informed of progress (and
21842 problems) fetching directory information and establishing circuits;
21843 and adds a variety of smaller features.
21846 - More work on making our TLS handshake blend in: modify the list
21847 of ciphers advertised by OpenSSL in client mode to even more
21848 closely resemble a common web browser. We cheat a little so that
21849 we can advertise ciphers that the locally installed OpenSSL doesn't
21851 - Start sending "bootstrap phase" status events to the controller,
21852 so it can keep the user informed of progress fetching directory
21853 information and establishing circuits. Also inform the controller
21854 if we think we're stuck at a particular bootstrap phase. Implements
21856 - Resume using OpenSSL's RAND_poll() for better (and more portable)
21857 cross-platform entropy collection again. We used to use it, then
21858 stopped using it because of a bug that could crash systems that
21859 called RAND_poll when they had a lot of fds open. It looks like the
21860 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
21861 at startup, and to call RAND_poll() when we reseed later only if
21862 we have a non-buggy OpenSSL version.
21865 - When we choose to abandon a new entry guard because we think our
21866 older ones might be better, close any circuits pending on that
21867 new entry guard connection. This fix should make us recover much
21868 faster when our network is down and then comes back. Bugfix on
21869 0.1.2.8-beta; found by lodger.
21871 o Memory fixes and improvements:
21872 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
21873 to avoid unused RAM in buffer chunks and memory pools.
21874 - Speed up parsing and cut down on memory fragmentation by using
21875 stack-style allocations for parsing directory objects. Previously,
21876 this accounted for over 40% of allocations from within Tor's code
21877 on a typical directory cache.
21878 - Use a Bloom filter rather than a digest-based set to track which
21879 descriptors we need to keep around when we're cleaning out old
21880 router descriptors. This speeds up the computation significantly,
21881 and may reduce fragmentation.
21882 - Reduce the default smartlist size from 32 to 16; it turns out that
21883 most smartlists hold around 8-12 elements tops.
21884 - Make dumpstats() log the fullness and size of openssl-internal
21886 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
21887 patch to their OpenSSL, turn it on to save memory on servers. This
21888 patch will (with any luck) get included in a mainline distribution
21890 - Never use OpenSSL compression: it wastes RAM and CPU trying to
21891 compress cells, which are basically all encrypted, compressed,
21895 - Stop reloading the router list from disk for no reason when we
21896 run out of reachable directory mirrors. Once upon a time reloading
21897 it would set the 'is_running' flag back to 1 for them. It hasn't
21898 done that for a long time.
21899 - In very rare situations new hidden service descriptors were
21900 published earlier than 30 seconds after the last change to the
21901 service. (We currently think that a hidden service descriptor
21902 that's been stable for 30 seconds is worth publishing.)
21905 - Allow separate log levels to be configured for different logging
21906 domains. For example, this allows one to log all notices, warnings,
21907 or errors, plus all memory management messages of level debug or
21908 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
21909 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
21910 and stop using a warning that had become unfixably verbose under
21912 - New --hush command-line option similar to --quiet. While --quiet
21913 disables all logging to the console on startup, --hush limits the
21914 output to messages of warning and error severity.
21915 - Servers support a new URL scheme for consensus downloads that
21916 allows the client to specify which authorities are trusted.
21917 The server then only sends the consensus if the client will trust
21918 it. Otherwise a 404 error is sent back. Clients use this
21919 new scheme when the server supports it (meaning it's running
21920 0.2.1.1-alpha or later). Implements proposal 134.
21921 - New configure/torrc options (--enable-geoip-stats,
21922 DirRecordUsageByCountry) to record how many IPs we've served
21923 directory info to in each country code, how many status documents
21924 total we've sent to each country code, and what share of the total
21925 directory requests we should expect to see.
21926 - Use the TLS1 hostname extension to more closely resemble browser
21928 - Lots of new unit tests.
21929 - Add a macro to implement the common pattern of iterating through
21930 two parallel lists in lockstep.
21933 Changes in version 0.2.0.28-rc - 2008-06-13
21934 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
21935 performance bug, and fixes a bunch of smaller bugs.
21938 - Fix a bug where, when we were choosing the 'end stream reason' to
21939 put in our relay end cell that we send to the exit relay, Tor
21940 clients on Windows were sometimes sending the wrong 'reason'. The
21941 anonymity problem is that exit relays may be able to guess whether
21942 the client is running Windows, thus helping partition the anonymity
21943 set. Down the road we should stop sending reasons to exit relays,
21944 or otherwise prevent future versions of this bug.
21947 - While setting up a hidden service, some valid introduction circuits
21948 were overlooked and abandoned. This might be the reason for
21949 the long delay in making a hidden service available. Bugfix on
21953 - Update to the "June 9 2008" ip-to-country file.
21954 - Run 'make test' as part of 'make dist', so we stop releasing so
21955 many development snapshots that fail their unit tests.
21958 - When we're checking if we have enough dir info for each relay
21959 to begin establishing circuits, make sure that we actually have
21960 the descriptor listed in the consensus, not just any descriptor.
21962 - Bridge relays no longer print "xx=0" in their extrainfo document
21963 for every single country code in the geoip db. Bugfix on
21965 - Only warn when we fail to load the geoip file if we were planning to
21966 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
21967 - If we change our MaxAdvertisedBandwidth and then reload torrc,
21968 Tor won't realize it should publish a new relay descriptor. Fixes
21969 bug 688, reported by mfr. Bugfix on 0.1.2.x.
21970 - When we haven't had any application requests lately, don't bother
21971 logging that we have expired a bunch of descriptors. Bugfix
21973 - Make relay cells written on a connection count as non-padding when
21974 tracking how long a connection has been in use. Bugfix on
21975 0.2.0.1-alpha. Spotted by lodger.
21976 - Fix unit tests in 0.2.0.27-rc.
21977 - Fix compile on Windows.
21980 Changes in version 0.2.0.27-rc - 2008-06-03
21981 Tor 0.2.0.27-rc adds a few features we left out of the earlier
21982 release candidates. In particular, we now include an IP-to-country
21983 GeoIP database, so controllers can easily look up what country a
21984 given relay is in, and so bridge relays can give us some sanitized
21985 summaries about which countries are making use of bridges. (See proposal
21986 126-geoip-fetching.txt for details.)
21989 - Include an IP-to-country GeoIP file in the tarball, so bridge
21990 relays can report sanitized summaries of the usage they're seeing.
21993 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
21994 Robert Hogan. Fixes the first part of bug 681.
21995 - Make bridge authorities never serve extrainfo docs.
21996 - Add support to detect Libevent versions in the 1.4.x series
21998 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
21999 - Include a new contrib/tor-exit-notice.html file that exit relay
22000 operators can put on their website to help reduce abuse queries.
22003 - When tunneling an encrypted directory connection, and its first
22004 circuit fails, do not leave it unattached and ask the controller
22005 to deal. Fixes the second part of bug 681.
22006 - Make bridge authorities correctly expire old extrainfo documents
22010 Changes in version 0.2.0.26-rc - 2008-05-13
22011 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
22012 in Debian's OpenSSL packages. All users running any 0.2.0.x version
22013 should upgrade, whether they're running Debian or not.
22015 o Major security fixes:
22016 - Use new V3 directory authority keys on the tor26, gabelmoo, and
22017 moria1 V3 directory authorities. The old keys were generated with
22018 a vulnerable version of Debian's OpenSSL package, and must be
22019 considered compromised. Other authorities' keys were not generated
22020 with an affected version of OpenSSL.
22023 - List authority signatures as "unrecognized" based on DirServer
22024 lines, not on cert cache. Bugfix on 0.2.0.x.
22027 - Add a new V3AuthUseLegacyKey option to make it easier for
22028 authorities to change their identity keys if they have to.
22031 Changes in version 0.2.0.25-rc - 2008-04-23
22032 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
22035 - Remember to initialize threading before initializing logging.
22036 Otherwise, many BSD-family implementations will crash hard on
22037 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
22040 - Authorities correctly free policies on bad servers on
22041 exit. Fixes bug 672. Bugfix on 0.2.0.x.
22044 Changes in version 0.2.0.24-rc - 2008-04-22
22045 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
22046 v3 directory authority, makes relays with dynamic IP addresses and no
22047 DirPort notice more quickly when their IP address changes, fixes a few
22048 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
22050 o New directory authorities:
22051 - Take lefkada out of the list of v3 directory authorities, since
22052 it has been down for months.
22053 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
22057 - Detect address changes more quickly on non-directory mirror
22058 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
22060 o Minor features (security):
22061 - Reject requests for reverse-dns lookup of names that are in
22062 a private address space. Patch from lodger.
22063 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
22066 o Minor bugfixes (crashes):
22067 - Avoid a rare assert that can trigger when Tor doesn't have much
22068 directory information yet and it tries to fetch a v2 hidden
22069 service descriptor. Fixes bug 651, reported by nwf.
22070 - Initialize log mutex before initializing dmalloc. Otherwise,
22071 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
22072 - Use recursive pthread mutexes in order to avoid deadlock when
22073 logging debug-level messages to a controller. Bug spotted by nwf,
22074 bugfix on 0.2.0.16-alpha.
22076 o Minor bugfixes (resource management):
22077 - Keep address policies from leaking memory: start their refcount
22078 at 1, not 2. Bugfix on 0.2.0.16-alpha.
22079 - Free authority certificates on exit, so they don't look like memory
22080 leaks. Bugfix on 0.2.0.19-alpha.
22081 - Free static hashtables for policy maps and for TLS connections on
22082 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
22083 - Avoid allocating extra space when computing consensuses on 64-bit
22084 platforms. Bug spotted by aakova.
22086 o Minor bugfixes (misc):
22087 - Do not read the configuration file when we've only been told to
22088 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
22089 based on patch from Sebastian Hahn.
22090 - Exit relays that are used as a client can now reach themselves
22091 using the .exit notation, rather than just launching an infinite
22092 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
22093 - When attempting to open a logfile fails, tell us why.
22094 - Fix a dumb bug that was preventing us from knowing that we should
22095 preemptively build circuits to handle expected directory requests.
22096 Fixes bug 660. Bugfix on 0.1.2.x.
22097 - Warn less verbosely about clock skew from netinfo cells from
22098 untrusted sources. Fixes bug 663.
22099 - Make controller stream events for DNS requests more consistent,
22100 by adding "new stream" events for DNS requests, and removing
22101 spurious "stream closed" events" for cached reverse resolves.
22102 Patch from mwenge. Fixes bug 646.
22103 - Correctly notify one-hop connections when a circuit build has
22104 failed. Possible fix for bug 669. Found by lodger.
22107 Changes in version 0.2.0.23-rc - 2008-03-24
22108 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
22109 makes bootstrapping faster if the first directory mirror you contact
22110 is down. The bundles also include the new Vidalia 0.1.2 release.
22113 - When a tunneled directory request is made to a directory server
22114 that's down, notice after 30 seconds rather than 120 seconds. Also,
22115 fail any begindir streams that are pending on it, so they can
22116 retry elsewhere. This was causing multi-minute delays on bootstrap.
22119 Changes in version 0.2.0.22-rc - 2008-03-18
22120 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
22121 enables encrypted directory connections by default for non-relays, fixes
22122 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
22123 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
22126 - Enable encrypted directory connections by default for non-relays,
22127 so censor tools that block Tor directory connections based on their
22128 plaintext patterns will no longer work. This means Tor works in
22129 certain censored countries by default again.
22132 - Make sure servers always request certificates from clients during
22133 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
22134 - Do not enter a CPU-eating loop when a connection is closed in
22135 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
22136 diagnosed by lodger; bugfix on 0.2.0.20-rc.
22137 - Fix assertion failure that could occur when a blocked circuit
22138 became unblocked, and it had pending client DNS requests. Bugfix
22139 on 0.2.0.1-alpha. Fixes bug 632.
22141 o Minor bugfixes (on 0.1.2.x):
22142 - Generate "STATUS_SERVER" events rather than misspelled
22143 "STATUS_SEVER" events. Caught by mwenge.
22144 - When counting the number of bytes written on a TLS connection,
22145 look at the BIO actually used for writing to the network, not
22146 at the BIO used (sometimes) to buffer data for the network.
22147 Looking at different BIOs could result in write counts on the
22148 order of ULONG_MAX. Fixes bug 614.
22149 - On Windows, correctly detect errors when listing the contents of
22150 a directory. Fix from lodger.
22152 o Minor bugfixes (on 0.2.0.x):
22153 - Downgrade "sslv3 alert handshake failure" message to INFO.
22154 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
22155 left BandwidthRate and BandwidthBurst at the default, we would be
22156 silently limited by those defaults. Now raise them to match the
22157 RelayBandwidth* values.
22158 - Fix the SVK version detection logic to work correctly on a branch.
22159 - Make --enable-openbsd-malloc work correctly on Linux with alpha
22160 CPUs. Fixes bug 625.
22161 - Logging functions now check that the passed severity is sane.
22162 - Use proper log levels in the testsuite call of
22163 get_interface_address6().
22164 - When using a nonstandard malloc, do not use the platform values for
22165 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
22166 - Make the openbsd malloc code use 8k pages on alpha CPUs and
22168 - Detect mismatched page sizes when using --enable-openbsd-malloc.
22169 - Avoid double-marked-for-close warning when certain kinds of invalid
22170 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
22171 for bug 617. Bugfix on 0.2.0.1-alpha.
22172 - Make sure that the "NULL-means-reject *:*" convention is followed by
22173 all the policy manipulation functions, avoiding some possible crash
22174 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
22175 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
22176 actually works, and doesn't warn about every single reverse lookup.
22177 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
22180 - Only log guard node status when guard node status has changed.
22181 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
22182 make "INFO" 75% less verbose.
22185 Changes in version 0.2.0.21-rc - 2008-03-02
22186 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
22187 makes Tor work well with Vidalia again, fixes a rare assert bug,
22188 and fixes a pair of more minor bugs. The bundles also include Vidalia
22189 0.1.0 and Torbutton 1.1.16.
22192 - The control port should declare that it requires password auth
22193 when HashedControlSessionPassword is set too. Patch from Matt Edman;
22194 bugfix on 0.2.0.20-rc. Fixes bug 615.
22195 - Downgrade assert in connection_buckets_decrement() to a log message.
22196 This may help us solve bug 614, and in any case will make its
22197 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
22198 - We were sometimes miscounting the number of bytes read from the
22199 network, causing our rate limiting to not be followed exactly.
22200 Bugfix on 0.2.0.16-alpha. Reported by lodger.
22203 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
22204 OpenSSL versions should have been working fine. Diagnosis and patch
22205 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
22206 Bugfix on 0.2.0.20-rc.
22209 Changes in version 0.2.0.20-rc - 2008-02-24
22210 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
22211 makes more progress towards normalizing Tor's TLS handshake, makes
22212 hidden services work better again, helps relays bootstrap if they don't
22213 know their IP address, adds optional support for linking in openbsd's
22214 allocator or tcmalloc, allows really fast relays to scale past 15000
22215 sockets, and fixes a bunch of minor bugs reported by Veracode.
22218 - Enable the revised TLS handshake based on the one designed by
22219 Steven Murdoch in proposal 124, as revised in proposal 130. It
22220 includes version negotiation for OR connections as described in
22221 proposal 105. The new handshake is meant to be harder for censors
22222 to fingerprint, and it adds the ability to detect certain kinds of
22223 man-in-the-middle traffic analysis attacks. The version negotiation
22224 feature will allow us to improve Tor's link protocol more safely
22226 - Choose which bridge to use proportional to its advertised bandwidth,
22227 rather than uniformly at random. This should speed up Tor for
22228 bridge users. Also do this for people who set StrictEntryNodes.
22229 - When a TrackHostExits-chosen exit fails too many times in a row,
22230 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
22233 - Resolved problems with (re-)fetching hidden service descriptors.
22234 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
22235 and 0.2.0.19-alpha.
22236 - If we only ever used Tor for hidden service lookups or posts, we
22237 would stop building circuits and start refusing connections after
22238 24 hours, since we falsely believed that Tor was dormant. Reported
22239 by nwf; bugfix on 0.1.2.x.
22240 - Servers that don't know their own IP address should go to the
22241 authorities for their first directory fetch, even if their DirPort
22242 is off or if they don't know they're reachable yet. This will help
22243 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
22244 - When counting the number of open sockets, count not only the number
22245 of sockets we have received from the socket() call, but also
22246 the number we've gotten from accept() and socketpair(). This bug
22247 made us fail to count all sockets that we were using for incoming
22248 connections. Bugfix on 0.2.0.x.
22249 - Fix code used to find strings within buffers, when those strings
22250 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
22251 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
22252 - Add a new __HashedControlSessionPassword option for controllers
22253 to use for one-off session password hashes that shouldn't get
22254 saved to disk by SAVECONF --- Vidalia users were accumulating a
22255 pile of HashedControlPassword lines in their torrc files, one for
22256 each time they had restarted Tor and then clicked Save. Make Tor
22257 automatically convert "HashedControlPassword" to this new option but
22258 only when it's given on the command line. Partial fix for bug 586.
22260 o Minor features (performance):
22261 - Tune parameters for cell pool allocation to minimize amount of
22263 - Add OpenBSD malloc code from phk as an optional malloc
22264 replacement on Linux: some glibc libraries do very poorly
22265 with Tor's memory allocation patterns. Pass
22266 --enable-openbsd-malloc to get the replacement malloc code.
22267 - Add a --with-tcmalloc option to the configure script to link
22268 against tcmalloc (if present). Does not yet search for
22269 non-system include paths.
22270 - Stop imposing an arbitrary maximum on the number of file descriptors
22271 used for busy servers. Bug reported by Olaf Selke; patch from
22274 o Minor features (other):
22275 - When SafeLogging is disabled, log addresses along with all TLS
22277 - When building with --enable-gcc-warnings, check for whether Apple's
22278 warning "-Wshorten-64-to-32" is available.
22279 - Add a --passphrase-fd argument to the tor-gencert command for
22282 o Minor bugfixes (memory leaks and code problems):
22283 - We were leaking a file descriptor if Tor started with a zero-length
22284 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
22285 - Detect size overflow in zlib code. Reported by Justin Ferguson and
22287 - We were comparing the raw BridgePassword entry with a base64'ed
22288 version of it, when handling a "/tor/networkstatus-bridges"
22289 directory request. Now compare correctly. Noticed by Veracode.
22290 - Recover from bad tracked-since value in MTBF-history file.
22291 Should fix bug 537.
22292 - Alter the code that tries to recover from unhandled write
22293 errors, to not try to flush onto a socket that's given us
22294 unhandled errors. Bugfix on 0.1.2.x.
22295 - Make Unix controlsockets work correctly on OpenBSD. Patch from
22296 tup. Bugfix on 0.2.0.3-alpha.
22298 o Minor bugfixes (other):
22299 - If we have an extra-info document for our server, always make
22300 it available on the control port, even if we haven't gotten
22301 a copy of it from an authority yet. Patch from mwenge.
22302 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
22303 - Directory mirrors no longer include a guess at the client's IP
22304 address if the connection appears to be coming from the same /24
22305 network; it was producing too many wrong guesses.
22306 - Make the new hidden service code respect the SafeLogging setting.
22307 Bugfix on 0.2.0.x. Patch from Karsten.
22308 - When starting as an authority, do not overwrite all certificates
22309 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
22310 - If we're trying to flush the last bytes on a connection (for
22311 example, when answering a directory request), reset the
22312 time-to-give-up timeout every time we manage to write something
22313 on the socket. Bugfix on 0.1.2.x.
22314 - Change the behavior of "getinfo status/good-server-descriptor"
22315 so it doesn't return failure when any authority disappears.
22316 - Even though the man page said that "TrackHostExits ." should
22317 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
22318 - Report TLS "zero return" case as a "clean close" and "IO error"
22319 as a "close". Stop calling closes "unexpected closes": existing
22320 Tors don't use SSL_close(), so having a connection close without
22321 the TLS shutdown handshake is hardly unexpected.
22322 - Send NAMESERVER_STATUS messages for a single failed nameserver
22325 o Code simplifications and refactoring:
22326 - Remove the tor_strpartition function: its logic was confused,
22327 and it was only used for one thing that could be implemented far
22331 Changes in version 0.2.0.19-alpha - 2008-02-09
22332 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
22333 handshake, makes path selection for relays more secure and IP address
22334 guessing more robust, and generally fixes a lot of bugs in preparation
22335 for calling the 0.2.0 branch stable.
22338 - Do not include recognizeable strings in the commonname part of
22339 Tor's x509 certificates.
22342 - If we're a relay, avoid picking ourselves as an introduction point,
22343 a rendezvous point, or as the final hop for internal circuits. Bug
22344 reported by taranis and lodger. Bugfix on 0.1.2.x.
22345 - Patch from "Andrew S. Lists" to catch when we contact a directory
22346 mirror at IP address X and he says we look like we're coming from
22347 IP address X. Bugfix on 0.1.2.x.
22349 o Minor features (security):
22350 - Be more paranoid about overwriting sensitive memory on free(),
22351 as a defensive programming tactic to ensure forward secrecy.
22353 o Minor features (directory authority):
22354 - Actually validate the options passed to AuthDirReject,
22355 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
22356 - Reject router descriptors with out-of-range bandwidthcapacity or
22357 bandwidthburst values.
22359 o Minor features (controller):
22360 - Reject controller commands over 1MB in length. This keeps rogue
22361 processes from running us out of memory.
22363 o Minor features (misc):
22364 - Give more descriptive well-formedness errors for out-of-range
22365 hidden service descriptor/protocol versions.
22366 - Make memory debugging information describe more about history
22367 of cell allocation, so we can help reduce our memory use.
22369 o Deprecated features (controller):
22370 - The status/version/num-versioning and status/version/num-concurring
22371 GETINFO options are no longer useful in the v3 directory protocol:
22372 treat them as deprecated, and warn when they're used.
22375 - When our consensus networkstatus has been expired for a while, stop
22376 being willing to build circuits using it. Fixes bug 401. Bugfix
22378 - Directory caches now fetch certificates from all authorities
22379 listed in a networkstatus consensus, even when they do not
22380 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
22381 - When connecting to a bridge without specifying its key, insert
22382 the connection into the identity-to-connection map as soon as
22383 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
22384 - Detect versions of OS X where malloc_good_size() is present in the
22385 library but never actually declared. Resolves bug 587. Bugfix
22387 - Stop incorrectly truncating zlib responses to directory authority
22388 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
22389 - Stop recommending that every server operator send mail to tor-ops.
22390 Resolves bug 597. Bugfix on 0.1.2.x.
22391 - Don't trigger an assert if we start a directory authority with a
22392 private IP address (like 127.0.0.1).
22393 - Avoid possible failures when generating a directory with routers
22394 with over-long versions strings, or too many flags set. Bugfix
22396 - If an attempt to launch a DNS resolve request over the control
22397 port fails because we have overrun the limit on the number of
22398 connections, tell the controller that the request has failed.
22399 - Avoid using too little bandwidth when our clock skips a few
22400 seconds. Bugfix on 0.1.2.x.
22401 - Fix shell error when warning about missing packages in configure
22402 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
22403 - Do not become confused when receiving a spurious VERSIONS-like
22404 cell from a confused v1 client. Bugfix on 0.2.0.x.
22405 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
22406 introduction points for a hidden service have failed. Patch from
22407 Karsten Loesing. Bugfix on 0.2.0.x.
22409 o Code simplifications and refactoring:
22410 - Remove some needless generality from cpuworker code, for improved
22412 - Stop overloading the circuit_t.onionskin field for both "onionskin
22413 from a CREATE cell that we are waiting for a cpuworker to be
22414 assigned" and "onionskin from an EXTEND cell that we are going to
22415 send to an OR as soon as we are connected". Might help with bug 600.
22416 - Add an in-place version of aes_crypt() so that we can avoid doing a
22417 needless memcpy() call on each cell payload.
22420 Changes in version 0.2.0.18-alpha - 2008-01-25
22421 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
22422 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
22423 that can warn or reject connections to ports generally associated with
22424 vulnerable-plaintext protocols.
22426 o New directory authorities:
22427 - Set up dannenberg (run by CCC) as the sixth v3 directory
22431 - Fix a major memory leak when attempting to use the v2 TLS
22432 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
22433 - We accidentally enabled the under-development v2 TLS handshake
22434 code, which was causing log entries like "TLS error while
22435 renegotiating handshake". Disable it again. Resolves bug 590.
22436 - We were computing the wrong Content-Length: header for directory
22437 responses that need to be compressed on the fly, causing clients
22438 asking for those items to always fail. Bugfix on 0.2.0.x; partially
22442 - Avoid going directly to the directory authorities even if you're a
22443 relay, if you haven't found yourself reachable yet or if you've
22444 decided not to advertise your dirport yet. Addresses bug 556.
22445 - If we've gone 12 hours since our last bandwidth check, and we
22446 estimate we have less than 50KB bandwidth capacity but we could
22447 handle more, do another bandwidth test.
22448 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
22449 Tor can warn and/or refuse connections to ports commonly used with
22450 vulnerable-plaintext protocols. Currently we warn on ports 23,
22451 109, 110, and 143, but we don't reject any.
22454 - When we setconf ClientOnly to 1, close any current OR and Dir
22455 listeners. Reported by mwenge.
22456 - When we get a consensus that's been signed by more people than
22457 we expect, don't log about it; it's not a big deal. Reported
22461 - Don't answer "/tor/networkstatus-bridges" directory requests if
22462 the request isn't encrypted.
22463 - Make "ClientOnly 1" config option disable directory ports too.
22464 - Patches from Karsten Loesing to make v2 hidden services more
22465 robust: work even when there aren't enough HSDir relays available;
22466 retry when a v2 rend desc fetch fails; but don't retry if we
22467 already have a usable v0 rend desc.
22470 Changes in version 0.2.0.17-alpha - 2008-01-17
22471 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
22474 - Make the tor-gencert man page get included correctly in the tarball.
22477 Changes in version 0.2.0.16-alpha - 2008-01-17
22478 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
22479 Loesing, and generally cleans up a lot of features and minor bugs.
22481 o New directory authorities:
22482 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
22485 o Major performance improvements:
22486 - Switch our old ring buffer implementation for one more like that
22487 used by free Unix kernels. The wasted space in a buffer with 1mb
22488 of data will now be more like 8k than 1mb. The new implementation
22489 also avoids realloc();realloc(); patterns that can contribute to
22490 memory fragmentation.
22493 - Configuration files now accept C-style strings as values. This
22494 helps encode characters not allowed in the current configuration
22495 file format, such as newline or #. Addresses bug 557.
22496 - Although we fixed bug 539 (where servers would send HTTP status 503
22497 responses _and_ send a body too), there are still servers out
22498 there that haven't upgraded. Therefore, make clients parse such
22499 bodies when they receive them.
22500 - When we're not serving v2 directory information, there is no reason
22501 to actually keep any around. Remove the obsolete files and directory
22502 on startup if they are very old and we aren't going to serve them.
22504 o Minor performance improvements:
22505 - Reference-count and share copies of address policy entries; only 5%
22506 of them were actually distinct.
22507 - Never walk through the list of logs if we know that no log is
22508 interested in a given message.
22511 - When an authority has not signed a consensus, do not try to
22512 download a nonexistent "certificate with key 00000000". Bugfix
22513 on 0.2.0.x. Fixes bug 569.
22514 - Fix a rare assert error when we're closing one of our threads:
22515 use a mutex to protect the list of logs, so we never write to the
22516 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
22517 bug 575, which is kind of the revenge of bug 222.
22518 - Patch from Karsten Loesing to complain less at both the client
22519 and the relay when a relay used to have the HSDir flag but doesn't
22520 anymore, and we try to upload a hidden service descriptor.
22521 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
22523 - Do not try to download missing certificates until we have tried
22524 to check our fallback consensus. Fixes bug 583.
22525 - Make bridges round reported GeoIP stats info up to the nearest
22526 estimate, not down. Now we can distinguish between "0 people from
22527 this country" and "1 person from this country".
22528 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
22529 - Avoid possible segfault if key generation fails in
22530 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
22531 - Avoid segfault in the case where a badly behaved v2 versioning
22532 directory sends a signed networkstatus with missing client-versions.
22534 - Avoid segfaults on certain complex invocations of
22535 router_get_by_hexdigest(). Bugfix on 0.1.2.
22536 - Correct bad index on array access in parse_http_time(). Bugfix
22538 - Fix possible bug in vote generation when server versions are present
22539 but client versions are not.
22540 - Fix rare bug on REDIRECTSTREAM control command when called with no
22541 port set: it could erroneously report an error when none had
22543 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
22544 compressing large objects and find ourselves with more than 4k
22545 left over. Bugfix on 0.2.0.
22546 - Fix a small memory leak when setting up a hidden service.
22547 - Fix a few memory leaks that could in theory happen under bizarre
22549 - Fix an assert if we post a general-purpose descriptor via the
22550 control port but that descriptor isn't mentioned in our current
22551 network consensus. Bug reported by Jon McLachlan; bugfix on
22554 o Minor features (controller):
22555 - Get NS events working again. Patch from tup.
22556 - The GETCONF command now escapes and quotes configuration values
22557 that don't otherwise fit into the torrc file.
22558 - The SETCONF command now handles quoted values correctly.
22560 o Minor features (directory authorities):
22561 - New configuration options to override default maximum number of
22562 servers allowed on a single IP address. This is important for
22563 running a test network on a single host.
22564 - Actually implement the -s option to tor-gencert.
22565 - Add a manual page for tor-gencert.
22567 o Minor features (bridges):
22568 - Bridge authorities no longer serve bridge descriptors over
22569 unencrypted connections.
22571 o Minor features (other):
22572 - Add hidden services and DNSPorts to the list of things that make
22573 Tor accept that it has running ports. Change starting Tor with no
22574 ports from a fatal error to a warning; we might change it back if
22575 this turns out to confuse anybody. Fixes bug 579.
22578 Changes in version 0.1.2.19 - 2008-01-17
22579 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
22580 exit policy a little bit more conservative so it's safer to run an
22581 exit relay on a home system, and fixes a variety of smaller issues.
22584 - Exit policies now reject connections that are addressed to a
22585 relay's public (external) IP address too, unless
22586 ExitPolicyRejectPrivate is turned off. We do this because too
22587 many relays are running nearby to services that trust them based
22588 on network address.
22591 - When the clock jumps forward a lot, do not allow the bandwidth
22592 buckets to become negative. Fixes bug 544.
22593 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
22594 on every successful resolve. Reported by Mike Perry.
22595 - Purge old entries from the "rephist" database and the hidden
22596 service descriptor database even when DirPort is zero.
22597 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
22598 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
22599 crashing or mis-answering these requests.
22600 - When we decide to send a 503 response to a request for servers, do
22601 not then also send the server descriptors: this defeats the whole
22602 purpose. Fixes bug 539.
22605 - Changing the ExitPolicyRejectPrivate setting should cause us to
22606 rebuild our server descriptor.
22607 - Fix handling of hex nicknames when answering controller requests for
22608 networkstatus by name, or when deciding whether to warn about
22609 unknown routers in a config option. (Patch from mwenge.)
22610 - Fix a couple of hard-to-trigger autoconf problems that could result
22611 in really weird results on platforms whose sys/types.h files define
22612 nonstandard integer types.
22613 - Don't try to create the datadir when running --verify-config or
22614 --hash-password. Resolves bug 540.
22615 - If we were having problems getting a particular descriptor from the
22616 directory caches, and then we learned about a new descriptor for
22617 that router, we weren't resetting our failure count. Reported
22619 - Although we fixed bug 539 (where servers would send HTTP status 503
22620 responses _and_ send a body too), there are still servers out there
22621 that haven't upgraded. Therefore, make clients parse such bodies
22622 when they receive them.
22623 - Run correctly on systems where rlim_t is larger than unsigned long.
22624 This includes some 64-bit systems.
22625 - Run correctly on platforms (like some versions of OS X 10.5) where
22626 the real limit for number of open files is OPEN_FILES, not rlim_max
22627 from getrlimit(RLIMIT_NOFILES).
22628 - Avoid a spurious free on base64 failure.
22629 - Avoid segfaults on certain complex invocations of
22630 router_get_by_hexdigest().
22631 - Fix rare bug on REDIRECTSTREAM control command when called with no
22632 port set: it could erroneously report an error when none had
22636 Changes in version 0.2.0.15-alpha - 2007-12-25
22637 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
22638 features added in 0.2.0.13-alpha.
22641 - Fix several remotely triggerable asserts based on DirPort requests
22642 for a v2 or v3 networkstatus object before we were prepared. This
22643 was particularly bad for 0.2.0.13 and later bridge relays, who
22644 would never have a v2 networkstatus and would thus always crash
22645 when used. Bugfixes on 0.2.0.x.
22646 - Estimate the v3 networkstatus size more accurately, rather than
22647 estimating it at zero bytes and giving it artificially high priority
22648 compared to other directory requests. Bugfix on 0.2.0.x.
22651 - Fix configure.in logic for cross-compilation.
22652 - When we load a bridge descriptor from the cache, and it was
22653 previously unreachable, mark it as retriable so we won't just
22654 ignore it. Also, try fetching a new copy immediately. Bugfixes
22656 - The bridge GeoIP stats were counting other relays, for example
22657 self-reachability and authority-reachability tests.
22660 - Support compilation to target iPhone; patch from cjacker huang.
22661 To build for iPhone, pass the --enable-iphone option to configure.
22664 Changes in version 0.2.0.14-alpha - 2007-12-23
22666 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
22667 without a datadirectory from a previous Tor install. Reported
22669 - Fix a crash when we fetch a descriptor that turns out to be
22670 unexpected (it used to be in our networkstatus when we started
22671 fetching it, but it isn't in our current networkstatus), and we
22672 aren't using bridges. Bugfix on 0.2.0.x.
22673 - Fix a crash when accessing hidden services: it would work the first
22674 time you use a given introduction point for your service, but
22675 on subsequent requests we'd be using garbage memory. Fixed by
22676 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
22677 - Fix a crash when we load a bridge descriptor from disk but we don't
22678 currently have a Bridge line for it in our torrc. Bugfix on
22682 - If bridge authorities set BridgePassword, they will serve a
22683 snapshot of known bridge routerstatuses from their DirPort to
22684 anybody who knows that password. Unset by default.
22687 - Make the unit tests build again.
22688 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
22689 - Make PublishServerDescriptor default to 1, so the default doesn't
22690 have to change as we invent new directory protocol versions.
22691 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
22692 be included unless sys/time.h is already included. Fixes
22693 bug 553. Bugfix on 0.2.0.x.
22694 - If we receive a general-purpose descriptor and then receive an
22695 identical bridge-purpose descriptor soon after, don't discard
22696 the next one as a duplicate.
22699 - If BridgeRelay is set to 1, then the default for
22700 PublishServerDescriptor is now "bridge" rather than "v2,v3".
22701 - If the user sets RelayBandwidthRate but doesn't set
22702 RelayBandwidthBurst, then make them equal rather than erroring out.
22705 Changes in version 0.2.0.13-alpha - 2007-12-21
22706 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
22707 Goodell, fixes many more bugs, and adds a lot of infrastructure for
22710 o New directory authorities:
22711 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
22715 - Only update guard status (usable / not usable) once we have
22716 enough directory information. This was causing us to always pick
22717 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
22718 causing us to discard all our guards on startup if we hadn't been
22719 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
22720 - Purge old entries from the "rephist" database and the hidden
22721 service descriptor databases even when DirPort is zero. Bugfix
22723 - We were ignoring our RelayBandwidthRate for the first 30 seconds
22724 after opening a circuit -- even a relayed circuit. Bugfix on
22726 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
22727 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
22728 crashing or mis-answering these types of requests.
22729 - Relays were publishing their server descriptor to v1 and v2
22730 directory authorities, but they didn't try publishing to v3-only
22731 authorities. Fix this; and also stop publishing to v1 authorities.
22733 - When we were reading router descriptors from cache, we were ignoring
22734 the annotations -- so for example we were reading in bridge-purpose
22735 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
22736 - When we decided to send a 503 response to a request for servers, we
22737 were then also sending the server descriptors: this defeats the
22738 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
22741 - Bridge relays now behave like clients with respect to time
22742 intervals for downloading new consensus documents -- otherwise they
22743 stand out. Bridge users now wait until the end of the interval,
22744 so their bridge relay will be sure to have a new consensus document.
22745 - Three new config options (AlternateDirAuthority,
22746 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
22747 user selectively replace the default directory authorities by type,
22748 rather than the all-or-nothing replacement that DirServer offers.
22749 - Tor can now be configured to read a GeoIP file from disk in one
22750 of two formats. This can be used by controllers to map IP addresses
22751 to countries. Eventually, it may support exit-by-country.
22752 - When possible, bridge relays remember which countries users
22753 are coming from, and report aggregate information in their
22754 extra-info documents, so that the bridge authorities can learn
22755 where Tor is blocked.
22756 - Bridge directory authorities now do reachability testing on the
22757 bridges they know. They provide router status summaries to the
22758 controller via "getinfo ns/purpose/bridge", and also dump summaries
22759 to a file periodically.
22760 - Stop fetching directory info so aggressively if your DirPort is
22761 on but your ORPort is off; stop fetching v2 dir info entirely.
22762 You can override these choices with the new FetchDirInfoEarly
22766 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
22767 consensus documents when there are too many relays at a single
22768 IP address. Now clear it in v2 network status documents too, and
22769 also clear it in routerinfo_t when the relay is no longer listed
22770 in the relevant networkstatus document.
22771 - Don't crash if we get an unexpected value for the
22772 PublishServerDescriptor config option. Reported by Matt Edman;
22773 bugfix on 0.2.0.9-alpha.
22774 - Our new v2 hidden service descriptor format allows descriptors
22775 that have no introduction points. But Tor crashed when we tried
22776 to build a descriptor with no intro points (and it would have
22777 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
22778 by Karsten Loesing.
22779 - Fix building with dmalloc 5.5.2 with glibc.
22780 - Reject uploaded descriptors and extrainfo documents if they're
22781 huge. Otherwise we'll cache them all over the network and it'll
22782 clog everything up. Reported by Aljosha Judmayer.
22783 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
22784 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
22785 - When the DANGEROUS_VERSION controller status event told us we're
22786 running an obsolete version, it used the string "OLD" to describe
22787 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
22788 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
22789 - If we can't expand our list of entry guards (e.g. because we're
22790 using bridges or we have StrictEntryNodes set), don't mark relays
22791 down when they fail a directory request. Otherwise we're too quick
22792 to mark all our entry points down. Bugfix on 0.1.2.x.
22793 - Fix handling of hex nicknames when answering controller requests for
22794 networkstatus by name, or when deciding whether to warn about unknown
22795 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
22796 - Fix a couple of hard-to-trigger autoconf problems that could result
22797 in really weird results on platforms whose sys/types.h files define
22798 nonstandard integer types. Bugfix on 0.1.2.x.
22799 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
22800 - Don't crash on name lookup when we have no current consensus. Fixes
22801 bug 538; bugfix on 0.2.0.x.
22802 - Only Tors that want to mirror the v2 directory info should
22803 create the "cached-status" directory in their datadir. (All Tors
22804 used to create it.) Bugfix on 0.2.0.9-alpha.
22805 - Directory authorities should only automatically download Extra Info
22806 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
22809 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
22810 consumers. (We already do this on HUP.)
22811 - Authorities and caches fetch the v2 networkstatus documents
22812 less often, now that v3 is encouraged.
22813 - Add a new config option BridgeRelay that specifies you want to
22814 be a bridge relay. Right now the only difference is that it makes
22815 you answer begin_dir requests, and it makes you cache dir info,
22816 even if your DirPort isn't on.
22817 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
22818 ask about source, timestamp of arrival, purpose, etc. We need
22819 something like this to help Vidalia not do GeoIP lookups on bridge
22821 - Allow multiple HashedControlPassword config lines, to support
22822 multiple controller passwords.
22823 - Authorities now decide whether they're authoritative for a given
22824 router based on the router's purpose.
22825 - New config options AuthDirBadDir and AuthDirListBadDirs for
22826 authorities to mark certain relays as "bad directories" in the
22827 networkstatus documents. Also supports the "!baddir" directive in
22828 the approved-routers file.
22831 Changes in version 0.2.0.12-alpha - 2007-11-16
22832 This twelfth development snapshot fixes some more build problems as
22833 well as a few minor bugs.
22836 - Make it build on OpenBSD again. Patch from tup.
22837 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
22838 package-building for Red Hat, OS X, etc.
22840 o Minor bugfixes (on 0.1.2.x):
22841 - Changing the ExitPolicyRejectPrivate setting should cause us to
22842 rebuild our server descriptor.
22844 o Minor bugfixes (on 0.2.0.x):
22845 - When we're lacking a consensus, don't try to perform rendezvous
22846 operations. Reported by Karsten Loesing.
22847 - Fix a small memory leak whenever we decide against using a
22848 newly picked entry guard. Reported by Mike Perry.
22849 - When authorities detected more than two relays running on the same
22850 IP address, they were clearing all the status flags but forgetting
22851 to clear the "hsdir" flag. So clients were being told that a
22852 given relay was the right choice for a v2 hsdir lookup, yet they
22853 never had its descriptor because it was marked as 'not running'
22855 - If we're trying to fetch a bridge descriptor and there's no way
22856 the bridge authority could help us (for example, we don't know
22857 a digest, or there is no bridge authority), don't be so eager to
22858 fall back to asking the bridge authority.
22859 - If we're using bridges or have strictentrynodes set, and our
22860 chosen exit is in the same family as all our bridges/entry guards,
22861 then be flexible about families.
22864 - When we negotiate a v2 link-layer connection (not yet implemented),
22865 accept RELAY_EARLY cells and turn them into RELAY cells if we've
22866 negotiated a v1 connection for their next step. Initial code for
22870 Changes in version 0.2.0.11-alpha - 2007-11-12
22871 This eleventh development snapshot fixes some build problems with
22872 the previous snapshot. It also includes a more secure-by-default exit
22873 policy for relays, fixes an enormous memory leak for exit relays, and
22874 fixes another bug where servers were falling out of the directory list.
22877 - Exit policies now reject connections that are addressed to a
22878 relay's public (external) IP address too, unless
22879 ExitPolicyRejectPrivate is turned off. We do this because too
22880 many relays are running nearby to services that trust them based
22881 on network address. Bugfix on 0.1.2.x.
22884 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
22885 on every successful resolve. Reported by Mike Perry; bugfix
22887 - On authorities, never downgrade to old router descriptors simply
22888 because they're listed in the consensus. This created a catch-22
22889 where we wouldn't list a new descriptor because there was an
22890 old one in the consensus, and we couldn't get the new one in the
22891 consensus because we wouldn't list it. Possible fix for bug 548.
22892 Also, this might cause bug 543 to appear on authorities; if so,
22893 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
22895 o Packaging fixes on 0.2.0.10-alpha:
22896 - We were including instructions about what to do with the
22897 src/config/fallback-consensus file, but we weren't actually
22898 including it in the tarball. Disable all of that for now.
22901 - Allow people to say PreferTunnelledDirConns rather than
22902 PreferTunneledDirConns, for those alternate-spellers out there.
22905 - Don't reevaluate all the information from our consensus document
22906 just because we've downloaded a v2 networkstatus that we intend
22907 to cache. Fixes bug 545; bugfix on 0.2.0.x.
22910 Changes in version 0.2.0.10-alpha - 2007-11-10
22911 This tenth development snapshot adds a third v3 directory authority
22912 run by Mike Perry, adds most of Karsten Loesing's new hidden service
22913 descriptor format, fixes a bad crash bug and new bridge bugs introduced
22914 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
22915 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
22916 addresses many more minor issues.
22918 o New directory authorities:
22919 - Set up ides (run by Mike Perry) as the third v3 directory authority.
22922 - Allow tunnelled directory connections to ask for an encrypted
22923 "begin_dir" connection or an anonymized "uses a full Tor circuit"
22924 connection independently. Now we can make anonymized begin_dir
22925 connections for (e.g.) more secure hidden service posting and
22927 - More progress on proposal 114: code from Karsten Loesing to
22928 implement new hidden service descriptor format.
22929 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
22930 accommodate the growing number of servers that use the default
22931 and are reaching it.
22932 - Directory authorities use a new formula for selecting which nodes
22933 to advertise as Guards: they must be in the top 7/8 in terms of
22934 how long we have known about them, and above the median of those
22935 nodes in terms of weighted fractional uptime.
22936 - Make "not enough dir info yet" warnings describe *why* Tor feels
22937 it doesn't have enough directory info yet.
22940 - Stop servers from crashing if they set a Family option (or
22941 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
22943 - Make bridge users work again -- the move to v3 directories in
22944 0.2.0.9-alpha had introduced a number of bugs that made bridges
22945 no longer work for clients.
22946 - When the clock jumps forward a lot, do not allow the bandwidth
22947 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
22949 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
22950 - When the consensus lists a router descriptor that we previously were
22951 mirroring, but that we considered non-canonical, reload the
22952 descriptor as canonical. This fixes bug 543 where Tor servers
22953 would start complaining after a few days that they don't have
22954 enough directory information to build a circuit.
22955 - Consider replacing the current consensus when certificates arrive
22956 that make the pending consensus valid. Previously, we were only
22957 considering replacement when the new certs _didn't_ help.
22958 - Fix an assert error on startup if we didn't already have the
22959 consensus and certs cached in our datadirectory: we were caching
22960 the consensus in consensus_waiting_for_certs but then free'ing it
22962 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
22963 Request) if we need more v3 certs but we've already got pending
22964 requests for all of them.
22965 - Correctly back off from failing certificate downloads. Fixes
22967 - Authorities don't vote on the Running flag if they have been running
22968 for less than 30 minutes themselves. Fixes bug 547, where a newly
22969 started authority would vote that everyone was down.
22971 o New requirements:
22972 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
22973 it, it had no AES, and it hasn't seen any security patches since
22977 - Clients now hold circuitless TLS connections open for 1.5 times
22978 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
22979 rebuild a new circuit over them within that timeframe. Previously,
22980 they held them open only for KeepalivePeriod (5 minutes).
22981 - Use "If-Modified-Since" to avoid retrieving consensus
22982 networkstatuses that we already have.
22983 - When we have no consensus, check FallbackNetworkstatusFile (defaults
22984 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
22985 we start knowing some directory caches.
22986 - When we receive a consensus from the future, warn about skew.
22987 - Improve skew reporting: try to give the user a better log message
22988 about how skewed they are, and how much this matters.
22989 - When we have a certificate for an authority, believe that
22990 certificate's claims about the authority's IP address.
22991 - New --quiet command-line option to suppress the default console log.
22992 Good in combination with --hash-password.
22993 - Authorities send back an X-Descriptor-Not-New header in response to
22994 an accepted-but-discarded descriptor upload. Partially implements
22996 - Make the log message for "tls error. breaking." more useful.
22997 - Better log messages about certificate downloads, to attempt to
22998 track down the second incarnation of bug 546.
23000 o Minor features (bridges):
23001 - If bridge users set UpdateBridgesFromAuthority, but the digest
23002 they ask for is a 404 from the bridge authority, they now fall
23003 back to trying the bridge directly.
23004 - Bridges now use begin_dir to publish their server descriptor to
23005 the bridge authority, even when they haven't set TunnelDirConns.
23007 o Minor features (controller):
23008 - When reporting clock skew, and we know that the clock is _at least
23009 as skewed_ as some value, but we don't know the actual value,
23010 report the value as a "minimum skew."
23013 - Update linux-tor-prio.sh script to allow QoS based on the uid of
23014 the Tor process. Patch from Marco Bonetti with tweaks from Mike
23018 - Refuse to start if both ORPort and UseBridges are set. Bugfix
23019 on 0.2.0.x, suggested by Matt Edman.
23020 - Don't stop fetching descriptors when FetchUselessDescriptors is
23021 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
23022 reported by tup and ioerror.
23023 - Better log message on vote from unknown authority.
23024 - Don't log "Launching 0 request for 0 router" message.
23026 o Minor bugfixes (memory leaks):
23027 - Stop leaking memory every time we parse a v3 certificate. Bugfix
23029 - Stop leaking memory every time we load a v3 certificate. Bugfix
23030 on 0.2.0.1-alpha. Fixes bug 536.
23031 - Stop leaking a cached networkstatus on exit. Bugfix on
23033 - Stop leaking voter information every time we free a consensus.
23034 Bugfix on 0.2.0.3-alpha.
23035 - Stop leaking signed data every time we check a voter signature.
23036 Bugfix on 0.2.0.3-alpha.
23037 - Stop leaking a signature every time we fail to parse a consensus or
23038 a vote. Bugfix on 0.2.0.3-alpha.
23039 - Stop leaking v2_download_status_map on shutdown. Bugfix on
23041 - Stop leaking conn->nickname every time we make a connection to a
23042 Tor relay without knowing its expected identity digest (e.g. when
23043 using bridges). Bugfix on 0.2.0.3-alpha.
23045 - Minor bugfixes (portability):
23046 - Run correctly on platforms where rlim_t is larger than unsigned
23047 long, and/or where the real limit for number of open files is
23048 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
23049 particular, these may be needed for OS X 10.5.
23052 Changes in version 0.1.2.18 - 2007-10-28
23053 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
23054 hidden service introduction that were causing huge delays, and a big
23055 bug that was causing some servers to disappear from the network status
23056 lists for a few hours each day.
23058 o Major bugfixes (crashes):
23059 - If a connection is shut down abruptly because of something that
23060 happened inside connection_flushed_some(), do not call
23061 connection_finished_flushing(). Should fix bug 451:
23062 "connection_stop_writing: Assertion conn->write_event failed"
23063 Bugfix on 0.1.2.7-alpha.
23064 - Fix possible segfaults in functions called from
23065 rend_process_relay_cell().
23067 o Major bugfixes (hidden services):
23068 - Hidden services were choosing introduction points uniquely by
23069 hexdigest, but when constructing the hidden service descriptor
23070 they merely wrote the (potentially ambiguous) nickname.
23071 - Clients now use the v2 intro format for hidden service
23072 connections: they specify their chosen rendezvous point by identity
23073 digest rather than by (potentially ambiguous) nickname. These
23074 changes could speed up hidden service connections dramatically.
23076 o Major bugfixes (other):
23077 - Stop publishing a new server descriptor just because we get a
23078 HUP signal. This led (in a roundabout way) to some servers getting
23079 dropped from the networkstatus lists for a few hours each day.
23080 - When looking for a circuit to cannibalize, consider family as well
23081 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
23082 circuit cannibalization).
23083 - When a router wasn't listed in a new networkstatus, we were leaving
23084 the flags for that router alone -- meaning it remained Named,
23085 Running, etc -- even though absence from the networkstatus means
23086 that it shouldn't be considered to exist at all anymore. Now we
23087 clear all the flags for routers that fall out of the networkstatus
23088 consensus. Fixes bug 529.
23091 - Don't try to access (or alter) the state file when running
23092 --list-fingerprint or --verify-config or --hash-password. Resolves
23094 - When generating information telling us how to extend to a given
23095 router, do not try to include the nickname if it is
23096 absent. Resolves bug 467.
23097 - Fix a user-triggerable segfault in expand_filename(). (There isn't
23098 a way to trigger this remotely.)
23099 - When sending a status event to the controller telling it that an
23100 OR address is reachable, set the port correctly. (Previously we
23101 were reporting the dir port.)
23102 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
23103 command. Bugfix on 0.1.2.17.
23104 - When loading bandwidth history, do not believe any information in
23105 the future. Fixes bug 434.
23106 - When loading entry guard information, do not believe any information
23108 - When we have our clock set far in the future and generate an
23109 onion key, then re-set our clock to be correct, we should not stop
23110 the onion key from getting rotated.
23111 - On some platforms, accept() can return a broken address. Detect
23112 this more quietly, and deal accordingly. Fixes bug 483.
23113 - It's not actually an error to find a non-pending entry in the DNS
23114 cache when canceling a pending resolve. Don't log unless stuff
23115 is fishy. Resolves bug 463.
23116 - Don't reset trusted dir server list when we set a configuration
23117 option. Patch from Robert Hogan.
23118 - Don't try to create the datadir when running --verify-config or
23119 --hash-password. Resolves bug 540.
23122 Changes in version 0.2.0.9-alpha - 2007-10-24
23123 This ninth development snapshot switches clients to the new v3 directory
23124 system; allows servers to be listed in the network status even when they
23125 have the same nickname as a registered server; and fixes many other
23126 bugs including a big one that was causing some servers to disappear
23127 from the network status lists for a few hours each day.
23129 o Major features (directory system):
23130 - Clients now download v3 consensus networkstatus documents instead
23131 of v2 networkstatus documents. Clients and caches now base their
23132 opinions about routers on these consensus documents. Clients only
23133 download router descriptors listed in the consensus.
23134 - Authorities now list servers who have the same nickname as
23135 a different named server, but list them with a new flag,
23136 "Unnamed". Now we can list servers that happen to pick the same
23137 nickname as a server that registered two years ago and then
23138 disappeared. Partially implements proposal 122.
23139 - If the consensus lists a router as "Unnamed", the name is assigned
23140 to a different router: do not identify the router by that name.
23141 Partially implements proposal 122.
23142 - Authorities can now come to a consensus on which method to use to
23143 compute the consensus. This gives us forward compatibility.
23146 - Stop publishing a new server descriptor just because we HUP or
23147 when we find our DirPort to be reachable but won't actually publish
23148 it. New descriptors without any real changes are dropped by the
23149 authorities, and can screw up our "publish every 18 hours" schedule.
23151 - When a router wasn't listed in a new networkstatus, we were leaving
23152 the flags for that router alone -- meaning it remained Named,
23153 Running, etc -- even though absence from the networkstatus means
23154 that it shouldn't be considered to exist at all anymore. Now we
23155 clear all the flags for routers that fall out of the networkstatus
23156 consensus. Fixes bug 529; bugfix on 0.1.2.x.
23157 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
23158 extrainfo documents and then discard them immediately for not
23159 matching the latest router. Bugfix on 0.2.0.1-alpha.
23161 o Minor features (v3 directory protocol):
23162 - Allow tor-gencert to generate a new certificate without replacing
23164 - Allow certificates to include an address.
23165 - When we change our directory-cache settings, reschedule all voting
23166 and download operations.
23167 - Reattempt certificate downloads immediately on failure, as long as
23168 we haven't failed a threshold number of times yet.
23169 - Delay retrying consensus downloads while we're downloading
23170 certificates to verify the one we just got. Also, count getting a
23171 consensus that we already have (or one that isn't valid) as a failure,
23172 and count failing to get the certificates after 20 minutes as a
23174 - Build circuits and download descriptors even if our consensus is a
23175 little expired. (This feature will go away once authorities are
23178 o Minor features (router descriptor cache):
23179 - If we find a cached-routers file that's been sitting around for more
23180 than 28 days unmodified, then most likely it's a leftover from
23181 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
23183 - When we (as a cache) download a descriptor because it was listed
23184 in a consensus, remember when the consensus was supposed to expire,
23185 and don't expire the descriptor until then.
23187 o Minor features (performance):
23188 - Call routerlist_remove_old_routers() much less often. This should
23189 speed startup, especially on directory caches.
23190 - Don't try to launch new descriptor downloads quite so often when we
23191 already have enough directory information to build circuits.
23192 - Base64 decoding was actually showing up on our profile when parsing
23193 the initial descriptor file; switch to an in-process all-at-once
23194 implementation that's about 3.5x times faster than calling out to
23197 o Minor features (compilation):
23198 - Detect non-ASCII platforms (if any still exist) and refuse to
23199 build there: some of our code assumes that 'A' is 65 and so on.
23201 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
23202 - Make the "next period" votes into "current period" votes immediately
23203 after publishing the consensus; avoid a heisenbug that made them
23204 stick around indefinitely.
23205 - When we discard a vote as a duplicate, do not report this as
23207 - Treat missing v3 keys or certificates as an error when running as a
23208 v3 directory authority.
23209 - When we're configured to be a v3 authority, but we're only listed
23210 as a non-v3 authority in our DirServer line for ourself, correct
23212 - If an authority doesn't have a qualified hostname, just put
23213 its address in the vote. This fixes the problem where we referred to
23214 "moria on moria:9031."
23215 - Distinguish between detached signatures for the wrong period, and
23216 detached signatures for a divergent vote.
23217 - Fix a small memory leak when computing a consensus.
23218 - When there's no consensus, we were forming a vote every 30
23219 minutes, but writing the "valid-after" line in our vote based
23220 on our configured V3AuthVotingInterval: so unless the intervals
23221 matched up, we immediately rejected our own vote because it didn't
23222 start at the voting interval that caused us to construct a vote.
23224 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
23225 - Delete unverified-consensus when the real consensus is set.
23226 - Consider retrying a consensus networkstatus fetch immediately
23227 after one fails: don't wait 60 seconds to notice.
23228 - When fetching a consensus as a cache, wait until a newer consensus
23229 should exist before trying to replace the current one.
23230 - Use a more forgiving schedule for retrying failed consensus
23231 downloads than for other types.
23233 o Minor bugfixes (other directory issues):
23234 - Correct the implementation of "download votes by digest." Bugfix on
23236 - Authorities no longer send back "400 you're unreachable please fix
23237 it" errors to Tor servers that aren't online all the time. We're
23238 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
23240 o Minor bugfixes (controller):
23241 - Don't reset trusted dir server list when we set a configuration
23242 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
23243 - Respond to INT and TERM SIGNAL commands before we execute the
23244 signal, in case the signal shuts us down. We had a patch in
23245 0.1.2.1-alpha that tried to do this by queueing the response on
23246 the connection's buffer before shutting down, but that really
23247 isn't the same thing at all. Bug located by Matt Edman.
23249 o Minor bugfixes (misc):
23250 - Correctly check for bad options to the "PublishServerDescriptor"
23251 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
23252 - Stop leaking memory on failing case of base32_decode, and make
23253 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
23254 - Don't try to download extrainfo documents when we're trying to
23255 fetch enough directory info to build a circuit: having enough
23256 info should get priority. Bugfix on 0.2.0.x.
23257 - Don't complain that "your server has not managed to confirm that its
23258 ports are reachable" if we haven't been able to build any circuits
23259 yet. Bug found by spending four hours without a v3 consensus. Bugfix
23261 - Detect the reason for failing to mmap a descriptor file we just
23262 wrote, and give a more useful log message. Fixes bug 533. Bugfix
23265 o Code simplifications and refactoring:
23266 - Remove support for the old bw_accounting file: we've been storing
23267 bandwidth accounting information in the state file since
23268 0.1.2.5-alpha. This may result in bandwidth accounting errors
23269 if you try to upgrade from 0.1.1.x or earlier, or if you try to
23270 downgrade to 0.1.1.x or earlier.
23271 - New convenience code to locate a file within the DataDirectory.
23272 - Move non-authority functionality out of dirvote.c.
23273 - Refactor the arguments for router_pick_{directory_|trusteddir}server
23274 so that they all take the same named flags.
23277 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
23278 Unix users an easy way to script their Tor process (e.g. by
23279 adjusting bandwidth based on the time of the day).
23282 Changes in version 0.2.0.8-alpha - 2007-10-12
23283 This eighth development snapshot fixes a crash bug that's been bothering
23284 us since February 2007, lets bridge authorities store a list of bridge
23285 descriptors they've seen, gets v3 directory voting closer to working,
23286 starts caching v3 directory consensus documents on directory mirrors,
23287 and fixes a variety of smaller issues including some minor memory leaks.
23289 o Major features (router descriptor cache):
23290 - Store routers in a file called cached-descriptors instead of in
23291 cached-routers. Initialize cached-descriptors from cached-routers
23292 if the old format is around. The new format allows us to store
23293 annotations along with descriptors.
23294 - Use annotations to record the time we received each descriptor, its
23295 source, and its purpose.
23296 - Disable the SETROUTERPURPOSE controller command: it is now
23298 - Controllers should now specify cache=no or cache=yes when using
23299 the +POSTDESCRIPTOR command.
23300 - Bridge authorities now write bridge descriptors to disk, meaning
23301 we can export them to other programs and begin distributing them
23304 o Major features (directory authorities):
23305 - When a v3 authority is missing votes or signatures, it now tries
23307 - Directory authorities track weighted fractional uptime as well as
23308 weighted mean-time-between failures. WFU is suitable for deciding
23309 whether a node is "usually up", while MTBF is suitable for deciding
23310 whether a node is "likely to stay up." We need both, because
23311 "usually up" is a good requirement for guards, while "likely to
23312 stay up" is a good requirement for long-lived connections.
23314 o Major features (v3 directory system):
23315 - Caches now download v3 network status documents as needed,
23316 and download the descriptors listed in them.
23317 - All hosts now attempt to download and keep fresh v3 authority
23318 certificates, and re-attempt after failures.
23319 - More internal-consistency checks for vote parsing.
23321 o Major bugfixes (crashes):
23322 - If a connection is shut down abruptly because of something that
23323 happened inside connection_flushed_some(), do not call
23324 connection_finished_flushing(). Should fix bug 451. Bugfix on
23327 o Major bugfixes (performance):
23328 - Fix really bad O(n^2) performance when parsing a long list of
23329 routers: Instead of searching the entire list for an "extra-info "
23330 string which usually wasn't there, once for every routerinfo
23331 we read, just scan lines forward until we find one we like.
23333 - When we add data to a write buffer in response to the data on that
23334 write buffer getting low because of a flush, do not consider the
23335 newly added data as a candidate for immediate flushing, but rather
23336 make it wait until the next round of writing. Otherwise, we flush
23337 and refill recursively, and a single greedy TLS connection can
23338 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
23340 o Minor features (v3 authority system):
23341 - Add more ways for tools to download the votes that lead to the
23343 - Send a 503 when low on bandwidth and a vote, consensus, or
23344 certificate is requested.
23345 - If-modified-since is now implemented properly for all kinds of
23346 certificate requests.
23348 o Minor bugfixes (network statuses):
23349 - Tweak the implementation of proposal 109 slightly: allow at most
23350 two Tor servers on the same IP address, except if it's the location
23351 of a directory authority, in which case allow five. Bugfix on
23354 o Minor bugfixes (controller):
23355 - When sending a status event to the controller telling it that an
23356 OR address is reachable, set the port correctly. (Previously we
23357 were reporting the dir port.) Bugfix on 0.1.2.x.
23359 o Minor bugfixes (v3 directory system):
23360 - Fix logic to look up a cert by its signing key digest. Bugfix on
23362 - Only change the reply to a vote to "OK" if it's not already
23363 set. This gets rid of annoying "400 OK" log messages, which may
23364 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
23365 - When we get a valid consensus, recompute the voting schedule.
23366 - Base the valid-after time of a vote on the consensus voting
23367 schedule, not on our preferred schedule.
23368 - Make the return values and messages from signature uploads and
23369 downloads more sensible.
23370 - Fix a memory leak when serving votes and consensus documents, and
23371 another when serving certificates.
23373 o Minor bugfixes (performance):
23374 - Use a slightly simpler string hashing algorithm (copying Python's
23375 instead of Java's) and optimize our digest hashing algorithm to take
23376 advantage of 64-bit platforms and to remove some possibly-costly
23378 - Fix a minor memory leak whenever we parse guards from our state
23379 file. Bugfix on 0.2.0.7-alpha.
23380 - Fix a minor memory leak whenever we write out a file. Bugfix on
23382 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
23383 command. Bugfix on 0.2.0.5-alpha.
23385 o Minor bugfixes (portability):
23386 - On some platforms, accept() can return a broken address. Detect
23387 this more quietly, and deal accordingly. Fixes bug 483.
23388 - Stop calling tor_strlower() on uninitialized memory in some cases.
23389 Bugfix in 0.2.0.7-alpha.
23391 o Minor bugfixes (usability):
23392 - Treat some 403 responses from directory servers as INFO rather than
23393 WARN-severity events.
23394 - It's not actually an error to find a non-pending entry in the DNS
23395 cache when canceling a pending resolve. Don't log unless stuff is
23396 fishy. Resolves bug 463.
23398 o Minor bugfixes (anonymity):
23399 - Never report that we've used more bandwidth than we're willing to
23400 relay: it leaks how much non-relay traffic we're using. Resolves
23402 - When looking for a circuit to cannibalize, consider family as well
23403 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
23404 circuit cannibalization).
23406 o Code simplifications and refactoring:
23407 - Make a bunch of functions static. Remove some dead code.
23408 - Pull out about a third of the really big routerlist.c; put it in a
23409 new module, networkstatus.c.
23410 - Merge the extra fields in local_routerstatus_t back into
23411 routerstatus_t: we used to need one routerstatus_t for each
23412 authority's opinion, plus a local_routerstatus_t for the locally
23413 computed consensus opinion. To save space, we put the locally
23414 modified fields into local_routerstatus_t, and only the common
23415 stuff into routerstatus_t. But once v3 directories are in use,
23416 clients and caches will no longer need to hold authority opinions;
23417 thus, the rationale for keeping the types separate is now gone.
23418 - Make the code used to reschedule and reattempt downloads more
23420 - Turn all 'Are we a directory server/mirror?' logic into a call to
23422 - Remove the code to generate the oldest (v1) directory format.
23423 The code has been disabled since 0.2.0.5-alpha.
23426 Changes in version 0.2.0.7-alpha - 2007-09-21
23427 This seventh development snapshot makes bridges work again, makes bridge
23428 authorities work for the first time, fixes two huge performance flaws
23429 in hidden services, and fixes a variety of minor issues.
23431 o New directory authorities:
23432 - Set up moria1 and tor26 as the first v3 directory authorities. See
23433 doc/spec/dir-spec.txt for details on the new directory design.
23435 o Major bugfixes (crashes):
23436 - Fix possible segfaults in functions called from
23437 rend_process_relay_cell(). Bugfix on 0.1.2.x.
23439 o Major bugfixes (bridges):
23440 - Fix a bug that made servers send a "404 Not found" in response to
23441 attempts to fetch their server descriptor. This caused Tor servers
23442 to take many minutes to establish reachability for their DirPort,
23443 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
23444 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
23445 users configure that and specify a bridge with an identity
23446 fingerprint, now they will lookup the bridge descriptor at the
23447 default bridge authority via a one-hop tunnel, but once circuits
23448 are established they will switch to a three-hop tunnel for later
23449 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
23451 o Major bugfixes (hidden services):
23452 - Hidden services were choosing introduction points uniquely by
23453 hexdigest, but when constructing the hidden service descriptor
23454 they merely wrote the (potentially ambiguous) nickname.
23455 - Clients now use the v2 intro format for hidden service
23456 connections: they specify their chosen rendezvous point by identity
23457 digest rather than by (potentially ambiguous) nickname. Both
23458 are bugfixes on 0.1.2.x, and they could speed up hidden service
23459 connections dramatically. Thanks to Karsten Loesing.
23461 o Minor features (security):
23462 - As a client, do not believe any server that tells us that an
23463 address maps to an internal address space.
23464 - Make it possible to enable HashedControlPassword and
23465 CookieAuthentication at the same time.
23467 o Minor features (guard nodes):
23468 - Tag every guard node in our state file with the version that
23469 we believe added it, or with our own version if we add it. This way,
23470 if a user temporarily runs an old version of Tor and then switches
23471 back to a new one, she doesn't automatically lose her guards.
23473 o Minor features (speed):
23474 - When implementing AES counter mode, update only the portions of the
23475 counter buffer that need to change, and don't keep separate
23476 network-order and host-order counters when they are the same (i.e.,
23477 on big-endian hosts.)
23479 o Minor features (controller):
23480 - Accept LF instead of CRLF on controller, since some software has a
23481 hard time generating real Internet newlines.
23482 - Add GETINFO values for the server status events
23483 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
23486 o Removed features:
23487 - Routers no longer include bandwidth-history lines in their
23488 descriptors; this information is already available in extra-info
23489 documents, and including it in router descriptors took up 60%
23490 (!) of compressed router descriptor downloads. Completes
23491 implementation of proposal 104.
23492 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
23493 and TorControl.py, as they use the old v0 controller protocol,
23494 and are obsoleted by TorFlow anyway.
23495 - Drop support for v1 rendezvous descriptors, since we never used
23496 them anyway, and the code has probably rotted by now. Based on
23497 patch from Karsten Loesing.
23498 - On OSX, stop warning the user that kqueue support in libevent is
23499 "experimental", since it seems to have worked fine for ages.
23502 - When generating information telling us how to extend to a given
23503 router, do not try to include the nickname if it is absent. Fixes
23504 bug 467. Bugfix on 0.2.0.3-alpha.
23505 - Fix a user-triggerable (but not remotely-triggerable) segfault
23506 in expand_filename(). Bugfix on 0.1.2.x.
23507 - Fix a memory leak when freeing incomplete requests from DNSPort.
23508 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
23509 - Don't try to access (or alter) the state file when running
23510 --list-fingerprint or --verify-config or --hash-password. (Resolves
23511 bug 499.) Bugfix on 0.1.2.x.
23512 - Servers used to decline to publish their DirPort if their
23513 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
23514 were below a threshold. Now they only look at BandwidthRate and
23515 RelayBandwidthRate. Bugfix on 0.1.2.x.
23516 - Remove an optimization in the AES counter-mode code that assumed
23517 that the counter never exceeded 2^68. When the counter can be set
23518 arbitrarily as an IV (as it is by Karsten's new hidden services
23519 code), this assumption no longer holds. Bugfix on 0.1.2.x.
23520 - Resume listing "AUTHORITY" flag for authorities in network status.
23521 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
23523 o Code simplifications and refactoring:
23524 - Revamp file-writing logic so we don't need to have the entire
23525 contents of a file in memory at once before we write to disk. Tor,
23527 - Turn "descriptor store" into a full-fledged type.
23528 - Move all NT services code into a separate source file.
23529 - Unify all code that computes medians, percentile elements, etc.
23530 - Get rid of a needless malloc when parsing address policies.
23533 Changes in version 0.1.2.17 - 2007-08-30
23534 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
23535 X bundles. Vidalia 0.0.14 makes authentication required for the
23536 ControlPort in the default configuration, which addresses important
23537 security risks. Everybody who uses Vidalia (or another controller)
23540 In addition, this Tor update fixes major load balancing problems with
23541 path selection, which should speed things up a lot once many people
23544 o Major bugfixes (security):
23545 - We removed support for the old (v0) control protocol. It has been
23546 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
23547 become more of a headache than it's worth.
23549 o Major bugfixes (load balancing):
23550 - When choosing nodes for non-guard positions, weight guards
23551 proportionally less, since they already have enough load. Patch
23553 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
23554 will allow fast Tor servers to get more attention.
23555 - When we're upgrading from an old Tor version, forget our current
23556 guards and pick new ones according to the new weightings. These
23557 three load balancing patches could raise effective network capacity
23558 by a factor of four. Thanks to Mike Perry for measurements.
23560 o Major bugfixes (stream expiration):
23561 - Expire not-yet-successful application streams in all cases if
23562 they've been around longer than SocksTimeout. Right now there are
23563 some cases where the stream will live forever, demanding a new
23564 circuit every 15 seconds. Fixes bug 454; reported by lodger.
23566 o Minor features (controller):
23567 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
23568 is valid before any authentication has been received. It tells
23569 a controller what kind of authentication is expected, and what
23570 protocol is spoken. Implements proposal 119.
23572 o Minor bugfixes (performance):
23573 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
23574 greatly speeding up loading cached-routers from disk on startup.
23575 - Disable sentinel-based debugging for buffer code: we squashed all
23576 the bugs that this was supposed to detect a long time ago, and now
23577 its only effect is to change our buffer sizes from nice powers of
23578 two (which platform mallocs tend to like) to values slightly over
23579 powers of two (which make some platform mallocs sad).
23581 o Minor bugfixes (misc):
23582 - If exit bandwidth ever exceeds one third of total bandwidth, then
23583 use the correct formula to weight exit nodes when choosing paths.
23584 Based on patch from Mike Perry.
23585 - Choose perfectly fairly among routers when choosing by bandwidth and
23586 weighting by fraction of bandwidth provided by exits. Previously, we
23587 would choose with only approximate fairness, and correct ourselves
23588 if we ran off the end of the list.
23589 - If we require CookieAuthentication but we fail to write the
23590 cookie file, we would warn but not exit, and end up in a state
23591 where no controller could authenticate. Now we exit.
23592 - If we require CookieAuthentication, stop generating a new cookie
23593 every time we change any piece of our config.
23594 - Refuse to start with certain directory authority keys, and
23595 encourage people using them to stop.
23596 - Terminate multi-line control events properly. Original patch
23598 - Fix a minor memory leak when we fail to find enough suitable
23599 servers to choose a circuit.
23600 - Stop leaking part of the descriptor when we run into a particularly
23601 unparseable piece of it.
23604 Changes in version 0.2.0.6-alpha - 2007-08-26
23605 This sixth development snapshot features a new Vidalia version in the
23606 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
23607 the ControlPort in the default configuration, which addresses important
23610 In addition, this snapshot fixes major load balancing problems
23611 with path selection, which should speed things up a lot once many
23612 people have upgraded. The directory authorities also use a new
23613 mean-time-between-failure approach to tracking which servers are stable,
23614 rather than just looking at the most recent uptime.
23616 o New directory authorities:
23617 - Set up Tonga as the default bridge directory authority.
23620 - Directory authorities now track servers by weighted
23621 mean-times-between-failures. When we have 4 or more days of data,
23622 use measured MTBF rather than declared uptime to decide whether
23623 to call a router Stable. Implements proposal 108.
23625 o Major bugfixes (load balancing):
23626 - When choosing nodes for non-guard positions, weight guards
23627 proportionally less, since they already have enough load. Patch
23629 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
23630 will allow fast Tor servers to get more attention.
23631 - When we're upgrading from an old Tor version, forget our current
23632 guards and pick new ones according to the new weightings. These
23633 three load balancing patches could raise effective network capacity
23634 by a factor of four. Thanks to Mike Perry for measurements.
23636 o Major bugfixes (descriptor parsing):
23637 - Handle unexpected whitespace better in malformed descriptors. Bug
23638 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
23641 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
23642 GETINFO for Torstat to use until it can switch to using extrainfos.
23643 - Optionally (if built with -DEXPORTMALLINFO) export the output
23644 of mallinfo via http, as tor/mallinfo.txt. Only accessible
23648 - Do not intermix bridge routers with controller-added
23649 routers. (Bugfix on 0.2.0.x)
23650 - Do not fail with an assert when accept() returns an unexpected
23651 address family. Addresses but does not wholly fix bug 483. (Bugfix
23653 - Let directory authorities startup even when they can't generate
23654 a descriptor immediately, e.g. because they don't know their
23656 - Stop putting the authentication cookie in a file called "0"
23657 in your working directory if you don't specify anything for the
23658 new CookieAuthFile option. Reported by Matt Edman.
23659 - Make it possible to read the PROTOCOLINFO response in a way that
23660 conforms to our control-spec. Reported by Matt Edman.
23661 - Fix a minor memory leak when we fail to find enough suitable
23662 servers to choose a circuit. Bugfix on 0.1.2.x.
23663 - Stop leaking part of the descriptor when we run into a particularly
23664 unparseable piece of it. Bugfix on 0.1.2.x.
23665 - Unmap the extrainfo cache file on exit.
23668 Changes in version 0.2.0.5-alpha - 2007-08-19
23669 This fifth development snapshot fixes compilation on Windows again;
23670 fixes an obnoxious client-side bug that slowed things down and put
23671 extra load on the network; gets us closer to using the v3 directory
23672 voting scheme; makes it easier for Tor controllers to use cookie-based
23673 authentication; and fixes a variety of other bugs.
23675 o Removed features:
23676 - Version 1 directories are no longer generated in full. Instead,
23677 authorities generate and serve "stub" v1 directories that list
23678 no servers. This will stop Tor versions 0.1.0.x and earlier from
23679 working, but (for security reasons) nobody should be running those
23682 o Major bugfixes (compilation, 0.2.0.x):
23683 - Try to fix Win32 compilation again: improve checking for IPv6 types.
23684 - Try to fix MSVC compilation: build correctly on platforms that do
23685 not define s6_addr16 or s6_addr32.
23686 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
23689 o Major bugfixes (stream expiration):
23690 - Expire not-yet-successful application streams in all cases if
23691 they've been around longer than SocksTimeout. Right now there are
23692 some cases where the stream will live forever, demanding a new
23693 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
23694 reported by lodger.
23696 o Minor features (directory servers):
23697 - When somebody requests a list of statuses or servers, and we have
23698 none of those, return a 404 rather than an empty 200.
23700 o Minor features (directory voting):
23701 - Store v3 consensus status consensuses on disk, and reload them
23704 o Minor features (security):
23705 - Warn about unsafe ControlPort configurations.
23706 - Refuse to start with certain directory authority keys, and
23707 encourage people using them to stop.
23709 o Minor features (controller):
23710 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
23711 is valid before any authentication has been received. It tells
23712 a controller what kind of authentication is expected, and what
23713 protocol is spoken. Implements proposal 119.
23714 - New config option CookieAuthFile to choose a new location for the
23715 cookie authentication file, and config option
23716 CookieAuthFileGroupReadable to make it group-readable.
23718 o Minor features (unit testing):
23719 - Add command-line arguments to unit-test executable so that we can
23720 invoke any chosen test from the command line rather than having
23721 to run the whole test suite at once; and so that we can turn on
23722 logging for the unit tests.
23724 o Minor bugfixes (on 0.1.2.x):
23725 - If we require CookieAuthentication but we fail to write the
23726 cookie file, we would warn but not exit, and end up in a state
23727 where no controller could authenticate. Now we exit.
23728 - If we require CookieAuthentication, stop generating a new cookie
23729 every time we change any piece of our config.
23730 - When loading bandwidth history, do not believe any information in
23731 the future. Fixes bug 434.
23732 - When loading entry guard information, do not believe any information
23734 - When we have our clock set far in the future and generate an
23735 onion key, then re-set our clock to be correct, we should not stop
23736 the onion key from getting rotated.
23737 - Clean up torrc sample config file.
23738 - Do not automatically run configure from autogen.sh. This
23739 non-standard behavior tended to annoy people who have built other
23742 o Minor bugfixes (on 0.2.0.x):
23743 - Fix a bug with AutomapHostsOnResolve that would always cause
23744 the second request to fail. Bug reported by Kate. Bugfix on
23746 - Fix a bug in ADDRMAP controller replies that would sometimes
23747 try to print a NULL. Patch from tup.
23748 - Read v3 directory authority keys from the right location.
23749 - Numerous bugfixes to directory voting code.
23752 Changes in version 0.1.2.16 - 2007-08-01
23753 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
23754 remote attacker in certain situations to rewrite the user's torrc
23755 configuration file. This can completely compromise anonymity of users
23756 in most configurations, including those running the Vidalia bundles,
23757 TorK, etc. Or worse.
23759 o Major security fixes:
23760 - Close immediately after missing authentication on control port;
23761 do not allow multiple authentication attempts.
23764 Changes in version 0.2.0.4-alpha - 2007-08-01
23765 This fourth development snapshot fixes a critical security vulnerability
23766 for most users, specifically those running Vidalia, TorK, etc. Everybody
23767 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
23769 o Major security fixes:
23770 - Close immediately after missing authentication on control port;
23771 do not allow multiple authentication attempts.
23773 o Major bugfixes (compilation):
23774 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
23777 o Minor features (performance):
23778 - Be even more aggressive about releasing RAM from small
23779 empty buffers. Thanks to our free-list code, this shouldn't be too
23780 performance-intensive.
23781 - Disable sentinel-based debugging for buffer code: we squashed all
23782 the bugs that this was supposed to detect a long time ago, and
23783 now its only effect is to change our buffer sizes from nice
23784 powers of two (which platform mallocs tend to like) to values
23785 slightly over powers of two (which make some platform mallocs sad).
23786 - Log malloc statistics from mallinfo() on platforms where it
23790 Changes in version 0.2.0.3-alpha - 2007-07-29
23791 This third development snapshot introduces new experimental
23792 blocking-resistance features and a preliminary version of the v3
23793 directory voting design, and includes many other smaller features
23797 - The first pieces of our "bridge" design for blocking-resistance
23798 are implemented. People can run bridge directory authorities;
23799 people can run bridges; and people can configure their Tor clients
23800 with a set of bridges to use as the first hop into the Tor network.
23801 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
23803 - Create listener connections before we setuid to the configured
23804 User and Group. Now non-Windows users can choose port values
23805 under 1024, start Tor as root, and have Tor bind those ports
23806 before it changes to another UID. (Windows users could already
23808 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
23809 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
23810 on "vserver" accounts. (Patch from coderman.)
23811 - Be even more aggressive about separating local traffic from relayed
23812 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
23814 o Major features (experimental):
23815 - First cut of code for "v3 dir voting": directory authorities will
23816 vote on a common network status document rather than each publishing
23817 their own opinion. This code needs more testing and more corner-case
23818 handling before it's ready for use.
23821 - Directory authorities now call routers Fast if their bandwidth is
23822 at least 100KB/s, and consider their bandwidth adequate to be a
23823 Guard if it is at least 250KB/s, no matter the medians. This fix
23824 complements proposal 107. [Bugfix on 0.1.2.x]
23825 - Directory authorities now never mark more than 3 servers per IP as
23826 Valid and Running. (Implements proposal 109, by Kevin Bauer and
23828 - Minor change to organizationName and commonName generation
23829 procedures in TLS certificates during Tor handshakes, to invalidate
23830 some earlier censorware approaches. This is not a long-term
23831 solution, but applying it will give us a bit of time to look into
23832 the epidemiology of countermeasures as they spread.
23834 o Major bugfixes (directory):
23835 - Rewrite directory tokenization code to never run off the end of
23836 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
23838 o Minor features (controller):
23839 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
23840 match requests to applications. (Patch from Robert Hogan.)
23841 - Report address and port correctly on connections to DNSPort. (Patch
23842 from Robert Hogan.)
23843 - Add a RESOLVE command to launch hostname lookups. (Original patch
23844 from Robert Hogan.)
23845 - Add GETINFO status/enough-dir-info to let controllers tell whether
23846 Tor has downloaded sufficient directory information. (Patch
23848 - You can now use the ControlSocket option to tell Tor to listen for
23849 controller connections on Unix domain sockets on systems that
23850 support them. (Patch from Peter Palfrader.)
23851 - STREAM NEW events are generated for DNSPort requests and for
23852 tunneled directory connections. (Patch from Robert Hogan.)
23853 - New "GETINFO address-mappings/*" command to get address mappings
23854 with expiry information. "addr-mappings/*" is now deprecated.
23857 o Minor features (misc):
23858 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
23860 - The tor-gencert tool for v3 directory authorities now creates all
23861 files as readable to the file creator only, and write-protects
23862 the authority identity key.
23863 - When dumping memory usage, list bytes used in buffer memory
23865 - When running with dmalloc, dump more stats on hup and on exit.
23866 - Directory authorities now fail quickly and (relatively) harmlessly
23867 if they generate a network status document that is somehow
23870 o Traffic load balancing improvements:
23871 - If exit bandwidth ever exceeds one third of total bandwidth, then
23872 use the correct formula to weight exit nodes when choosing paths.
23873 (Based on patch from Mike Perry.)
23874 - Choose perfectly fairly among routers when choosing by bandwidth and
23875 weighting by fraction of bandwidth provided by exits. Previously, we
23876 would choose with only approximate fairness, and correct ourselves
23877 if we ran off the end of the list. [Bugfix on 0.1.2.x]
23879 o Performance improvements:
23880 - Be more aggressive with freeing buffer RAM or putting it on the
23882 - Use Critical Sections rather than Mutexes for synchronizing threads
23883 on win32; Mutexes are heavier-weight, and designed for synchronizing
23886 o Deprecated and removed features:
23887 - RedirectExits is now deprecated.
23888 - Stop allowing address masks that do not correspond to bit prefixes.
23889 We have warned about these for a really long time; now it's time
23890 to reject them. (Patch from croup.)
23892 o Minor bugfixes (directory):
23893 - Fix another crash bug related to extra-info caching. (Bug found by
23894 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
23895 - Directories no longer return a "304 not modified" when they don't
23896 have the networkstatus the client asked for. Also fix a memory
23897 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
23898 - We had accidentally labelled 0.1.2.x directory servers as not
23899 suitable for begin_dir requests, and had labelled no directory
23900 servers as suitable for uploading extra-info documents. [Bugfix
23903 o Minor bugfixes (dns):
23904 - Fix a crash when DNSPort is set more than once. (Patch from Robert
23905 Hogan.) [Bugfix on 0.2.0.2-alpha]
23906 - Add DNSPort connections to the global connection list, so that we
23907 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
23909 - Fix a dangling reference that could lead to a crash when DNSPort is
23910 changed or closed (Patch from Robert Hogan.) [Bugfix on
23913 o Minor bugfixes (controller):
23914 - Provide DNS expiry times in GMT, not in local time. For backward
23915 compatibility, ADDRMAP events only provide GMT expiry in an extended
23916 field. "GETINFO address-mappings" always does the right thing.
23917 - Use CRLF line endings properly in NS events.
23918 - Terminate multi-line control events properly. (Original patch
23919 from tup.) [Bugfix on 0.1.2.x-alpha]
23920 - Do not include spaces in SOURCE_ADDR fields in STREAM
23921 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
23924 Changes in version 0.1.2.15 - 2007-07-17
23925 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
23926 problems, fixes compilation on BSD, and fixes a variety of other
23927 bugs. Everybody should upgrade.
23929 o Major bugfixes (compilation):
23930 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
23932 o Major bugfixes (crashes):
23933 - Try even harder not to dereference the first character after
23934 an mmap(). Reported by lodger.
23935 - Fix a crash bug in directory authorities when we re-number the
23936 routerlist while inserting a new router.
23937 - When the cached-routers file is an even multiple of the page size,
23938 don't run off the end and crash. (Fixes bug 455; based on idea
23940 - Fix eventdns.c behavior on Solaris: It is critical to include
23941 orconfig.h _before_ sys/types.h, so that we can get the expected
23942 definition of _FILE_OFFSET_BITS.
23944 o Major bugfixes (security):
23945 - Fix a possible buffer overrun when using BSD natd support. Bug
23947 - When sending destroy cells from a circuit's origin, don't include
23948 the reason for tearing down the circuit. The spec says we didn't,
23949 and now we actually don't. Reported by lodger.
23950 - Keep streamids from different exits on a circuit separate. This
23951 bug may have allowed other routers on a given circuit to inject
23952 cells into streams. Reported by lodger; fixes bug 446.
23953 - If there's a never-before-connected-to guard node in our list,
23954 never choose any guards past it. This way we don't expand our
23955 guard list unless we need to.
23957 o Minor bugfixes (guard nodes):
23958 - Weight guard selection by bandwidth, so that low-bandwidth nodes
23959 don't get overused as guards.
23961 o Minor bugfixes (directory):
23962 - Correctly count the number of authorities that recommend each
23963 version. Previously, we were under-counting by 1.
23964 - Fix a potential crash bug when we load many server descriptors at
23965 once and some of them make others of them obsolete. Fixes bug 458.
23967 o Minor bugfixes (hidden services):
23968 - Stop tearing down the whole circuit when the user asks for a
23969 connection to a port that the hidden service didn't configure.
23972 o Minor bugfixes (misc):
23973 - On Windows, we were preventing other processes from reading
23974 cached-routers while Tor was running. Reported by janbar.
23975 - Fix a possible (but very unlikely) bug in picking routers by
23976 bandwidth. Add a log message to confirm that it is in fact
23977 unlikely. Patch from lodger.
23978 - Backport a couple of memory leak fixes.
23979 - Backport miscellaneous cosmetic bugfixes.
23982 Changes in version 0.2.0.2-alpha - 2007-06-02
23983 o Major bugfixes on 0.2.0.1-alpha:
23984 - Fix an assertion failure related to servers without extra-info digests.
23985 Resolves bugs 441 and 442.
23987 o Minor features (directory):
23988 - Support "If-Modified-Since" when answering HTTP requests for
23989 directories, running-routers documents, and network-status documents.
23990 (There's no need to support it for router descriptors, since those
23991 are downloaded by descriptor digest.)
23993 o Minor build issues:
23994 - Clear up some MIPSPro compiler warnings.
23995 - When building from a tarball on a machine that happens to have SVK
23996 installed, report the micro-revision as whatever version existed
23997 in the tarball, not as "x".
24000 Changes in version 0.2.0.1-alpha - 2007-06-01
24001 This early development snapshot provides new features for people running
24002 Tor as both a client and a server (check out the new RelayBandwidth
24003 config options); lets Tor run as a DNS proxy; and generally moves us
24004 forward on a lot of fronts.
24006 o Major features, server usability:
24007 - New config options RelayBandwidthRate and RelayBandwidthBurst:
24008 a separate set of token buckets for relayed traffic. Right now
24009 relayed traffic is defined as answers to directory requests, and
24010 OR connections that don't have any local circuits on them.
24012 o Major features, client usability:
24013 - A client-side DNS proxy feature to replace the need for
24014 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
24015 for DNS requests on port 9999, use the Tor network to resolve them
24016 anonymously, and send the reply back like a regular DNS server.
24017 The code still only implements a subset of DNS.
24018 - Make PreferTunneledDirConns and TunnelDirConns work even when
24019 we have no cached directory info. This means Tor clients can now
24020 do all of their connections protected by TLS.
24022 o Major features, performance and efficiency:
24023 - Directory authorities accept and serve "extra info" documents for
24024 routers. These documents contain fields from router descriptors
24025 that aren't usually needed, and that use a lot of excess
24026 bandwidth. Once these fields are removed from router descriptors,
24027 the bandwidth savings should be about 60%. [Partially implements
24029 - Servers upload extra-info documents to any authority that accepts
24030 them. Authorities (and caches that have been configured to download
24031 extra-info documents) download them as needed. [Partially implements
24033 - Change the way that Tor buffers data that it is waiting to write.
24034 Instead of queueing data cells in an enormous ring buffer for each
24035 client->OR or OR->OR connection, we now queue cells on a separate
24036 queue for each circuit. This lets us use less slack memory, and
24037 will eventually let us be smarter about prioritizing different kinds
24039 - Use memory pools to allocate cells with better speed and memory
24040 efficiency, especially on platforms where malloc() is inefficient.
24041 - Stop reading on edge connections when their corresponding circuit
24042 buffers are full; start again as the circuits empty out.
24044 o Major features, other:
24045 - Add an HSAuthorityRecordStats option that hidden service authorities
24046 can use to track statistics of overall hidden service usage without
24047 logging information that would be very useful to an attacker.
24048 - Start work implementing multi-level keys for directory authorities:
24049 Add a standalone tool to generate key certificates. (Proposal 103.)
24052 - Directory authorities now call routers Stable if they have an
24053 uptime of at least 30 days, even if that's not the median uptime
24054 in the network. Implements proposal 107, suggested by Kevin Bauer
24057 o Minor fixes (resource management):
24058 - Count the number of open sockets separately from the number
24059 of active connection_t objects. This will let us avoid underusing
24060 our allocated connection limit.
24061 - We no longer use socket pairs to link an edge connection to an
24062 anonymous directory connection or a DirPort test connection.
24063 Instead, we track the link internally and transfer the data
24064 in-process. This saves two sockets per "linked" connection (at the
24065 client and at the server), and avoids the nasty Windows socketpair()
24067 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
24068 for every single inactive connection_t. Free items from the
24069 4k/16k-buffer free lists when they haven't been used for a while.
24071 o Minor features (build):
24072 - Make autoconf search for libevent, openssl, and zlib consistently.
24073 - Update deprecated macros in configure.in.
24074 - When warning about missing headers, tell the user to let us
24075 know if the compile succeeds anyway, so we can downgrade the
24077 - Include the current subversion revision as part of the version
24078 string: either fetch it directly if we're in an SVN checkout, do
24079 some magic to guess it if we're in an SVK checkout, or use
24080 the last-detected version if we're building from a .tar.gz.
24081 Use this version consistently in log messages.
24083 o Minor features (logging):
24084 - Always prepend "Bug: " to any log message about a bug.
24085 - Put a platform string (e.g. "Linux i686") in the startup log
24086 message, so when people paste just their logs, we know if it's
24087 OpenBSD or Windows or what.
24088 - When logging memory usage, break down memory used in buffers by
24091 o Minor features (directory system):
24092 - New config option V2AuthoritativeDirectory that all directory
24093 authorities should set. This will let future authorities choose
24094 not to serve V2 directory information.
24095 - Directory authorities allow multiple router descriptors and/or extra
24096 info documents to be uploaded in a single go. This will make
24097 implementing proposal 104 simpler.
24099 o Minor features (controller):
24100 - Add a new config option __DisablePredictedCircuits designed for
24101 use by the controller, when we don't want Tor to build any circuits
24103 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
24104 so we can exit from the middle of the circuit.
24105 - Implement "getinfo status/circuit-established".
24106 - Implement "getinfo status/version/..." so a controller can tell
24107 whether the current version is recommended, and whether any versions
24108 are good, and how many authorities agree. (Patch from shibz.)
24110 o Minor features (hidden services):
24111 - Allow multiple HiddenServicePort directives with the same virtual
24112 port; when they occur, the user is sent round-robin to one
24113 of the target ports chosen at random. Partially fixes bug 393 by
24114 adding limited ad-hoc round-robining.
24116 o Minor features (other):
24118 - Add a new AutomapHostsOnResolve option: when it is enabled, any
24119 resolve request for hosts matching a given pattern causes Tor to
24120 generate an internal virtual address mapping for that host. This
24121 allows DNSPort to work sensibly with hidden service users. By
24122 default, .exit and .onion addresses are remapped; the list of
24123 patterns can be reconfigured with AutomapHostsSuffixes.
24124 - Add an "-F" option to tor-resolve to force a resolve for a .onion
24125 address. Thanks to the AutomapHostsOnResolve option, this is no
24126 longer a completely silly thing to do.
24127 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
24128 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
24129 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
24130 minus 1 byte: the actual maximum declared bandwidth.
24132 o Removed features:
24133 - Removed support for the old binary "version 0" controller protocol.
24134 This has been deprecated since 0.1.1, and warnings have been issued
24135 since 0.1.2. When we encounter a v0 control message, we now send
24136 back an error and close the connection.
24137 - Remove the old "dns worker" server DNS code: it hasn't been default
24138 since 0.1.2.2-alpha, and all the servers seem to be using the new
24141 o Minor bugfixes (portability):
24142 - Even though Windows is equally happy with / and \ as path separators,
24143 try to use \ consistently on Windows and / consistently on Unix: it
24144 makes the log messages nicer.
24145 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
24146 - Read resolv.conf files correctly on platforms where read() returns
24147 partial results on small file reads.
24149 o Minor bugfixes (directory):
24150 - Correctly enforce that elements of directory objects do not appear
24151 more often than they are allowed to appear.
24152 - When we are reporting the DirServer line we just parsed, we were
24153 logging the second stanza of the key fingerprint, not the first.
24155 o Minor bugfixes (logging):
24156 - When we hit an EOF on a log (probably because we're shutting down),
24157 don't try to remove the log from the list: just mark it as
24158 unusable. (Bulletproofs against bug 222.)
24160 o Minor bugfixes (other):
24161 - In the exitlist script, only consider the most recently published
24162 server descriptor for each server. Also, when the user requests
24163 a list of servers that _reject_ connections to a given address,
24164 explicitly exclude the IPs that also have servers that accept
24165 connections to that address. (Resolves bug 405.)
24166 - Stop allowing hibernating servers to be "stable" or "fast".
24167 - On Windows, we were preventing other processes from reading
24168 cached-routers while Tor was running. (Reported by janbar)
24169 - Make the NodeFamilies config option work. (Reported by
24170 lodger -- it has never actually worked, even though we added it
24172 - Check return values from pthread_mutex functions.
24173 - Don't save non-general-purpose router descriptors to the disk cache,
24174 because we have no way of remembering what their purpose was when
24176 - Add even more asserts to hunt down bug 417.
24177 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
24178 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
24179 Add a log message to confirm that it is in fact unlikely.
24181 o Minor bugfixes (controller):
24182 - Make 'getinfo fingerprint' return a 551 error if we're not a
24183 server, so we match what the control spec claims we do. Reported
24185 - Fix a typo in an error message when extendcircuit fails that
24186 caused us to not follow the \r\n-based delimiter protocol. Reported
24189 o Code simplifications and refactoring:
24190 - Stop passing around circuit_t and crypt_path_t pointers that are
24191 implicit in other procedure arguments.
24192 - Drop the old code to choke directory connections when the
24193 corresponding OR connections got full: thanks to the cell queue
24194 feature, OR conns don't get full any more.
24195 - Make dns_resolve() handle attaching connections to circuits
24196 properly, so the caller doesn't have to.
24197 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
24198 - Keep the connection array as a dynamic smartlist_t, rather than as
24199 a fixed-sized array. This is important, as the number of connections
24200 is becoming increasingly decoupled from the number of sockets.
24203 Changes in version 0.1.2.14 - 2007-05-25
24204 Tor 0.1.2.14 changes the addresses of two directory authorities (this
24205 change especially affects those who serve or use hidden services),
24206 and fixes several other crash- and security-related bugs.
24208 o Directory authority changes:
24209 - Two directory authorities (moria1 and moria2) just moved to new
24210 IP addresses. This change will particularly affect those who serve
24211 or use hidden services.
24213 o Major bugfixes (crashes):
24214 - If a directory server runs out of space in the connection table
24215 as it's processing a begin_dir request, it will free the exit stream
24216 but leave it attached to the circuit, leading to unpredictable
24217 behavior. (Reported by seeess, fixes bug 425.)
24218 - Fix a bug in dirserv_remove_invalid() that would cause authorities
24219 to corrupt memory under some really unlikely scenarios.
24220 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
24221 - Avoid segfaults when reading from mmaped descriptor file. (Reported
24224 o Major bugfixes (security):
24225 - When choosing an entry guard for a circuit, avoid using guards
24226 that are in the same family as the chosen exit -- not just guards
24227 that are exactly the chosen exit. (Reported by lodger.)
24229 o Major bugfixes (resource management):
24230 - If a directory authority is down, skip it when deciding where to get
24231 networkstatus objects or descriptors. Otherwise we keep asking
24232 every 10 seconds forever. Fixes bug 384.
24233 - Count it as a failure if we fetch a valid network-status but we
24234 don't want to keep it. Otherwise we'll keep fetching it and keep
24235 not wanting to keep it. Fixes part of bug 422.
24236 - If all of our dirservers have given us bad or no networkstatuses
24237 lately, then stop hammering them once per minute even when we
24238 think they're failed. Fixes another part of bug 422.
24241 - Actually set the purpose correctly for descriptors inserted with
24242 purpose=controller.
24243 - When we have k non-v2 authorities in our DirServer config,
24244 we ignored the last k authorities in the list when updating our
24246 - Correctly back-off from requesting router descriptors that we are
24247 having a hard time downloading.
24248 - Read resolv.conf files correctly on platforms where read() returns
24249 partial results on small file reads.
24250 - Don't rebuild the entire router store every time we get 32K of
24251 routers: rebuild it when the journal gets very large, or when
24252 the gaps in the store get very large.
24255 - When routers publish SVN revisions in their router descriptors,
24256 authorities now include those versions correctly in networkstatus
24258 - Warn when using a version of libevent before 1.3b to run a server on
24259 OSX or BSD: these versions interact badly with userspace threads.
24262 Changes in version 0.1.2.13 - 2007-04-24
24263 This release features some major anonymity fixes, such as safer path
24264 selection; better client performance; faster bootstrapping, better
24265 address detection, and better DNS support for servers; write limiting as
24266 well as read limiting to make servers easier to run; and a huge pile of
24267 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
24269 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
24270 of the Freenode IRC network, remembering his patience and vision for
24271 free speech on the Internet.
24274 - Fix a memory leak when we ask for "all" networkstatuses and we
24275 get one we don't recognize.
24276 - Add more asserts to hunt down bug 417.
24277 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
24280 Changes in version 0.1.2.12-rc - 2007-03-16
24282 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
24283 directory information requested inside Tor connections (i.e. via
24284 begin_dir cells). It only triggered when the same connection was
24285 serving other data at the same time. Reported by seeess.
24288 - When creating a circuit via the controller, send a 'launched'
24289 event when we're done, so we follow the spec better.
24292 Changes in version 0.1.2.11-rc - 2007-03-15
24293 o Minor bugfixes (controller), reported by daejees:
24294 - Correct the control spec to match how the code actually responds
24295 to 'getinfo addr-mappings/*'.
24296 - The control spec described a GUARDS event, but the code
24297 implemented a GUARD event. Standardize on GUARD, but let people
24298 ask for GUARDS too.
24301 Changes in version 0.1.2.10-rc - 2007-03-07
24302 o Major bugfixes (Windows):
24303 - Do not load the NT services library functions (which may not exist)
24304 just to detect if we're a service trying to shut down. Now we run
24305 on Win98 and friends again.
24307 o Minor bugfixes (other):
24308 - Clarify a couple of log messages.
24309 - Fix a misleading socks5 error number.
24312 Changes in version 0.1.2.9-rc - 2007-03-02
24313 o Major bugfixes (Windows):
24314 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
24315 of the usual GCC "%llu". This prevents a bug when saving 64-bit
24316 int configuration values: the high-order 32 bits would get
24317 truncated. In particular, we were being bitten by the default
24318 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
24319 and maybe also bug 397.)
24321 o Minor bugfixes (performance):
24322 - Use OpenSSL's AES implementation on platforms where it's faster.
24323 This could save us as much as 10% CPU usage.
24325 o Minor bugfixes (server):
24326 - Do not rotate onion key immediately after setting it for the first
24329 o Minor bugfixes (directory authorities):
24330 - Stop calling servers that have been hibernating for a long time
24331 "stable". Also, stop letting hibernating or obsolete servers affect
24332 uptime and bandwidth cutoffs.
24333 - Stop listing hibernating servers in the v1 directory.
24335 o Minor bugfixes (hidden services):
24336 - Upload hidden service descriptors slightly less often, to reduce
24337 load on authorities.
24339 o Minor bugfixes (other):
24340 - Fix an assert that could trigger if a controller quickly set then
24341 cleared EntryNodes. Bug found by Udo van den Heuvel.
24342 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
24344 - Fix a potential race condition in the rpm installer. Found by
24346 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
24347 of 2 as indicating that the server is completely bad; it sometimes
24348 means that the server is just bad for the request in question. (may fix
24349 the last of bug 326.)
24350 - Disable encrypted directory connections when we don't have a server
24351 descriptor for the destination. We'll get this working again in
24355 Changes in version 0.1.2.8-beta - 2007-02-26
24356 o Major bugfixes (crashes):
24357 - Stop crashing when the controller asks us to resetconf more than
24358 one config option at once. (Vidalia 0.0.11 does this.)
24359 - Fix a crash that happened on Win98 when we're given command-line
24360 arguments: don't try to load NT service functions from advapi32.dll
24361 except when we need them. (Bug introduced in 0.1.2.7-alpha;
24363 - Fix a longstanding obscure crash bug that could occur when
24364 we run out of DNS worker processes. (Resolves bug 390.)
24366 o Major bugfixes (hidden services):
24367 - Correctly detect whether hidden service descriptor downloads are
24368 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
24370 o Major bugfixes (accounting):
24371 - When we start during an accounting interval before it's time to wake
24372 up, remember to wake up at the correct time. (May fix bug 342.)
24374 o Minor bugfixes (controller):
24375 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
24376 clear the corresponding on_circuit variable, and remember later
24377 that we don't need to send a redundant CLOSED event. Resolves part
24379 - Report events where a resolve succeeded or where we got a socks
24380 protocol error correctly, rather than calling both of them
24382 - Change reported stream target addresses to IP consistently when
24383 we finally get the IP from an exit node.
24384 - Send log messages to the controller even if they happen to be very
24387 o Minor bugfixes (other):
24388 - Display correct results when reporting which versions are
24389 recommended, and how recommended they are. (Resolves bug 383.)
24390 - Improve our estimates for directory bandwidth to be less random:
24391 guess that an unrecognized directory will have the average bandwidth
24392 from all known directories, not that it will have the average
24393 bandwidth from those directories earlier than it on the list.
24394 - If we start a server with ClientOnly 1, then set ClientOnly to 0
24395 and hup, stop triggering an assert based on an empty onion_key.
24396 - On platforms with no working mmap() equivalent, don't warn the
24397 user when cached-routers doesn't exist.
24398 - Warn the user when mmap() [or its equivalent] fails for some reason
24399 other than file-not-found.
24400 - Don't warn the user when cached-routers.new doesn't exist: that's
24401 perfectly fine when starting up for the first time.
24402 - When EntryNodes are configured, rebuild the guard list to contain,
24403 in order: the EntryNodes that were guards before; the rest of the
24404 EntryNodes; the nodes that were guards before.
24405 - Mask out all signals in sub-threads; only the libevent signal
24406 handler should be processing them. This should prevent some crashes
24407 on some machines using pthreads. (Patch from coderman.)
24408 - Fix switched arguments on memset in the implementation of
24409 tor_munmap() for systems with no mmap() call.
24410 - When Tor receives a router descriptor that it asked for, but
24411 no longer wants (because it has received fresh networkstatuses
24412 in the meantime), do not warn the user. Cache the descriptor if
24413 we're a cache; drop it if we aren't.
24414 - Make earlier entry guards _really_ get retried when the network
24416 - On a malformed DNS reply, always give an error to the corresponding
24418 - Build with recent libevents on platforms that do not define the
24419 nonstandard types "u_int8_t" and friends.
24421 o Minor features (controller):
24422 - Warn the user when an application uses the obsolete binary v0
24423 control protocol. We're planning to remove support for it during
24424 the next development series, so it's good to give people some
24426 - Add STREAM_BW events to report per-entry-stream bandwidth
24427 use. (Patch from Robert Hogan.)
24428 - Rate-limit SIGNEWNYM signals in response to controllers that
24429 impolitely generate them for every single stream. (Patch from
24430 mwenge; closes bug 394.)
24431 - Make REMAP stream events have a SOURCE (cache or exit), and
24432 make them generated in every case where we get a successful
24433 connected or resolved cell.
24435 o Minor bugfixes (performance):
24436 - Call router_have_min_dir_info half as often. (This is showing up in
24437 some profiles, but not others.)
24438 - When using GCC, make log_debug never get called at all, and its
24439 arguments never get evaluated, when no debug logs are configured.
24440 (This is showing up in some profiles, but not others.)
24443 - Remove some never-implemented options. Mark PathlenCoinWeight as
24445 - Implement proposal 106: Stop requiring clients to have well-formed
24446 certificates; stop checking nicknames in certificates. (Clients
24447 have certificates so that they can look like Tor servers, but in
24448 the future we might want to allow them to look like regular TLS
24449 clients instead. Nicknames in certificates serve no purpose other
24450 than making our protocol easier to recognize on the wire.)
24451 - Revise messages on handshake failure again to be even more clear about
24452 which are incoming connections and which are outgoing.
24453 - Discard any v1 directory info that's over 1 month old (for
24454 directories) or over 1 week old (for running-routers lists).
24455 - Do not warn when individual nodes in the configuration's EntryNodes,
24456 ExitNodes, etc are down: warn only when all possible nodes
24457 are down. (Fixes bug 348.)
24458 - Always remove expired routers and networkstatus docs before checking
24459 whether we have enough information to build circuits. (Fixes
24461 - Put a lower-bound on MaxAdvertisedBandwidth.
24464 Changes in version 0.1.2.7-alpha - 2007-02-06
24465 o Major bugfixes (rate limiting):
24466 - Servers decline directory requests much more aggressively when
24467 they're low on bandwidth. Otherwise they end up queueing more and
24468 more directory responses, which can't be good for latency.
24469 - But never refuse directory requests from local addresses.
24470 - Fix a memory leak when sending a 503 response for a networkstatus
24472 - Be willing to read or write on local connections (e.g. controller
24473 connections) even when the global rate limiting buckets are empty.
24474 - If our system clock jumps back in time, don't publish a negative
24475 uptime in the descriptor. Also, don't let the global rate limiting
24476 buckets go absurdly negative.
24477 - Flush local controller connection buffers periodically as we're
24478 writing to them, so we avoid queueing 4+ megabytes of data before
24481 o Major bugfixes (NT services):
24482 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
24483 command-line flag so that admins can override the default by saying
24484 "tor --service install --user "SomeUser"". This will not affect
24485 existing installed services. Also, warn the user that the service
24486 will look for its configuration file in the service user's
24487 %appdata% directory. (We can't do the 'hardwire the user's appdata
24488 directory' trick any more, since we may not have read access to that
24491 o Major bugfixes (other):
24492 - Previously, we would cache up to 16 old networkstatus documents
24493 indefinitely, if they came from nontrusted authorities. Now we
24494 discard them if they are more than 10 days old.
24495 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
24497 - Detect and reject malformed DNS responses containing circular
24499 - If exits are rare enough that we're not marking exits as guards,
24500 ignore exit bandwidth when we're deciding the required bandwidth
24502 - When we're handling a directory connection tunneled over Tor,
24503 don't fill up internal memory buffers with all the data we want
24504 to tunnel; instead, only add it if the OR connection that will
24505 eventually receive it has some room for it. (This can lead to
24506 slowdowns in tunneled dir connections; a better solution will have
24507 to wait for 0.2.0.)
24509 o Minor bugfixes (dns):
24510 - Add some defensive programming to eventdns.c in an attempt to catch
24511 possible memory-stomping bugs.
24512 - Detect and reject DNS replies containing IPv4 or IPv6 records with
24513 an incorrect number of bytes. (Previously, we would ignore the
24515 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
24516 in the correct order, and doesn't crash.
24517 - Free memory held in recently-completed DNS lookup attempts on exit.
24518 This was not a memory leak, but may have been hiding memory leaks.
24519 - Handle TTL values correctly on reverse DNS lookups.
24520 - Treat failure to parse resolv.conf as an error.
24522 o Minor bugfixes (other):
24523 - Fix crash with "tor --list-fingerprint" (reported by seeess).
24524 - When computing clock skew from directory HTTP headers, consider what
24525 time it was when we finished asking for the directory, not what
24527 - Expire socks connections if they spend too long waiting for the
24528 handshake to finish. Previously we would let them sit around for
24529 days, if the connecting application didn't close them either.
24530 - And if the socks handshake hasn't started, don't send a
24531 "DNS resolve socks failed" handshake reply; just close it.
24532 - Stop using C functions that OpenBSD's linker doesn't like.
24533 - Don't launch requests for descriptors unless we have networkstatuses
24534 from at least half of the authorities. This delays the first
24535 download slightly under pathological circumstances, but can prevent
24536 us from downloading a bunch of descriptors we don't need.
24537 - Do not log IPs with TLS failures for incoming TLS
24538 connections. (Fixes bug 382.)
24539 - If the user asks to use invalid exit nodes, be willing to use
24541 - Stop using the reserved ac_cv namespace in our configure script.
24542 - Call stat() slightly less often; use fstat() when possible.
24543 - Refactor the way we handle pending circuits when an OR connection
24544 completes or fails, in an attempt to fix a rare crash bug.
24545 - Only rewrite a conn's address based on X-Forwarded-For: headers
24546 if it's a parseable public IP address; and stop adding extra quotes
24547 to the resulting address.
24550 - Weight directory requests by advertised bandwidth. Now we can
24551 let servers enable write limiting but still allow most clients to
24552 succeed at their directory requests. (We still ignore weights when
24553 choosing a directory authority; I hope this is a feature.)
24556 - Create a new file ReleaseNotes which was the old ChangeLog. The
24557 new ChangeLog file now includes the summaries for all development
24559 - Check for addresses with invalid characters at the exit as well
24560 as at the client, and warn less verbosely when they fail. You can
24561 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
24562 - Adapt a patch from goodell to let the contrib/exitlist script
24563 take arguments rather than require direct editing.
24564 - Inform the server operator when we decide not to advertise a
24565 DirPort due to AccountingMax enabled or a low BandwidthRate. It
24566 was confusing Zax, so now we're hopefully more helpful.
24567 - Bring us one step closer to being able to establish an encrypted
24568 directory tunnel without knowing a descriptor first. Still not
24569 ready yet. As part of the change, now assume we can use a
24570 create_fast cell if we don't know anything about a router.
24571 - Allow exit nodes to use nameservers running on ports other than 53.
24572 - Servers now cache reverse DNS replies.
24573 - Add an --ignore-missing-torrc command-line option so that we can
24574 get the "use sensible defaults if the configuration file doesn't
24575 exist" behavior even when specifying a torrc location on the command
24578 o Minor features (controller):
24579 - Track reasons for OR connection failure; make these reasons
24580 available via the controller interface. (Patch from Mike Perry.)
24581 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
24582 can learn when clients are sending malformed hostnames to Tor.
24583 - Clean up documentation for controller status events.
24584 - Add a REMAP status to stream events to note that a stream's
24585 address has changed because of a cached address or a MapAddress
24589 Changes in version 0.1.2.6-alpha - 2007-01-09
24591 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
24592 connection handles more than 4 gigs in either direction, we crash.
24593 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
24594 advertised exit node, somebody might try to exit from us when
24595 we're bootstrapping and before we've built our descriptor yet.
24596 Refuse the connection rather than crashing.
24599 - Warn if we (as a server) find that we've resolved an address that we
24600 weren't planning to resolve.
24601 - Warn that using select() on any libevent version before 1.1 will be
24602 unnecessarily slow (even for select()).
24603 - Flush ERR-level controller status events just like we currently
24604 flush ERR-level log events, so that a Tor shutdown doesn't prevent
24605 the controller from learning about current events.
24607 o Minor features (more controller status events):
24608 - Implement EXTERNAL_ADDRESS server status event so controllers can
24609 learn when our address changes.
24610 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
24611 can learn when directories reject our descriptor.
24612 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
24613 can learn when a client application is speaking a non-socks protocol
24615 - Implement DANGEROUS_SOCKS client status event so controllers
24616 can learn when a client application is leaking DNS addresses.
24617 - Implement BUG general status event so controllers can learn when
24618 Tor is unhappy about its internal invariants.
24619 - Implement CLOCK_SKEW general status event so controllers can learn
24620 when Tor thinks the system clock is set incorrectly.
24621 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
24622 server status events so controllers can learn when their descriptors
24623 are accepted by a directory.
24624 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
24625 server status events so controllers can learn about Tor's progress in
24626 deciding whether it's reachable from the outside.
24627 - Implement BAD_LIBEVENT general status event so controllers can learn
24628 when we have a version/method combination in libevent that needs to
24630 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
24631 and DNS_USELESS server status events so controllers can learn
24632 about changes to DNS server status.
24634 o Minor features (directory):
24635 - Authorities no longer recommend exits as guards if this would shift
24636 too much load to the exit nodes.
24639 Changes in version 0.1.2.5-alpha - 2007-01-06
24641 - Enable write limiting as well as read limiting. Now we sacrifice
24642 capacity if we're pushing out lots of directory traffic, rather
24643 than overrunning the user's intended bandwidth limits.
24644 - Include TLS overhead when counting bandwidth usage; previously, we
24645 would count only the bytes sent over TLS, but not the bytes used
24647 - Support running the Tor service with a torrc not in the same
24648 directory as tor.exe and default to using the torrc located in
24649 the %appdata%\Tor\ of the user who installed the service. Patch
24651 - Servers now check for the case when common DNS requests are going to
24652 wildcarded addresses (i.e. all getting the same answer), and change
24653 their exit policy to reject *:* if it's happening.
24654 - Implement BEGIN_DIR cells, so we can connect to the directory
24655 server via TLS to do encrypted directory requests rather than
24656 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
24657 config options if you like.
24659 o Minor features (config and docs):
24660 - Start using the state file to store bandwidth accounting data:
24661 the bw_accounting file is now obsolete. We'll keep generating it
24662 for a while for people who are still using 0.1.2.4-alpha.
24663 - Try to batch changes to the state file so that we do as few
24664 disk writes as possible while still storing important things in
24666 - The state file and the bw_accounting file get saved less often when
24667 the AvoidDiskWrites config option is set.
24668 - Make PIDFile work on Windows (untested).
24669 - Add internal descriptions for a bunch of configuration options:
24670 accessible via controller interface and in comments in saved
24672 - Reject *:563 (NNTPS) in the default exit policy. We already reject
24673 NNTP by default, so this seems like a sensible addition.
24674 - Clients now reject hostnames with invalid characters. This should
24675 avoid some inadvertent info leaks. Add an option
24676 AllowNonRFC953Hostnames to disable this behavior, in case somebody
24677 is running a private network with hosts called @, !, and #.
24678 - Add a maintainer script to tell us which options are missing
24679 documentation: "make check-docs".
24680 - Add a new address-spec.txt document to describe our special-case
24681 addresses: .exit, .onion, and .noconnnect.
24683 o Minor features (DNS):
24684 - Ongoing work on eventdns infrastructure: now it has dns server
24685 and ipv6 support. One day Tor will make use of it.
24686 - Add client-side caching for reverse DNS lookups.
24687 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
24688 - When we change nameservers or IP addresses, reset and re-launch
24689 our tests for DNS hijacking.
24691 o Minor features (directory):
24692 - Authorities now specify server versions in networkstatus. This adds
24693 about 2% to the size of compressed networkstatus docs, and allows
24694 clients to tell which servers support BEGIN_DIR and which don't.
24695 The implementation is forward-compatible with a proposed future
24696 protocol version scheme not tied to Tor versions.
24697 - DirServer configuration lines now have an orport= option so
24698 clients can open encrypted tunnels to the authorities without
24699 having downloaded their descriptors yet. Enabled for moria1,
24700 moria2, tor26, and lefkada now in the default configuration.
24701 - Directory servers are more willing to send a 503 "busy" if they
24702 are near their write limit, especially for v1 directory requests.
24703 Now they can use their limited bandwidth for actual Tor traffic.
24704 - Clients track responses with status 503 from dirservers. After a
24705 dirserver has given us a 503, we try not to use it until an hour has
24706 gone by, or until we have no dirservers that haven't given us a 503.
24707 - When we get a 503 from a directory, and we're not a server, we don't
24708 count the failure against the total number of failures allowed
24709 for the thing we're trying to download.
24710 - Report X-Your-Address-Is correctly from tunneled directory
24711 connections; don't report X-Your-Address-Is when it's an internal
24712 address; and never believe reported remote addresses when they're
24714 - Protect against an unlikely DoS attack on directory servers.
24715 - Add a BadDirectory flag to network status docs so that authorities
24716 can (eventually) tell clients about caches they believe to be
24719 o Minor features (controller):
24720 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
24721 - Reimplement GETINFO so that info/names stays in sync with the
24723 - Implement "GETINFO fingerprint".
24724 - Implement "SETEVENTS GUARD" so controllers can get updates on
24725 entry guard status as it changes.
24727 o Minor features (clean up obsolete pieces):
24728 - Remove some options that have been deprecated since at least
24729 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
24730 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
24731 to set log options.
24732 - We no longer look for identity and onion keys in "identity.key" and
24733 "onion.key" -- these were replaced by secret_id_key and
24734 secret_onion_key in 0.0.8pre1.
24735 - We no longer require unrecognized directory entries to be
24738 o Major bugfixes (security):
24739 - Stop sending the HttpProxyAuthenticator string to directory
24740 servers when directory connections are tunnelled through Tor.
24741 - Clients no longer store bandwidth history in the state file.
24742 - Do not log introduction points for hidden services if SafeLogging
24744 - When generating bandwidth history, round down to the nearest
24745 1k. When storing accounting data, round up to the nearest 1k.
24746 - When we're running as a server, remember when we last rotated onion
24747 keys, so that we will rotate keys once they're a week old even if
24748 we never stay up for a week ourselves.
24750 o Major bugfixes (other):
24751 - Fix a longstanding bug in eventdns that prevented the count of
24752 timed-out resolves from ever being reset. This bug caused us to
24753 give up on a nameserver the third time it timed out, and try it
24754 10 seconds later... and to give up on it every time it timed out
24756 - Take out the '5 second' timeout from the connection retry
24757 schedule. Now the first connect attempt will wait a full 10
24758 seconds before switching to a new circuit. Perhaps this will help
24759 a lot. Based on observations from Mike Perry.
24760 - Fix a bug on the Windows implementation of tor_mmap_file() that
24761 would prevent the cached-routers file from ever loading. Reported
24765 - Fix an assert failure when a directory authority sets
24766 AuthDirRejectUnlisted and then receives a descriptor from an
24767 unlisted router. Reported by seeess.
24768 - Avoid a double-free when parsing malformed DirServer lines.
24769 - Fix a bug when a BSD-style PF socket is first used. Patch from
24771 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
24772 to resolve an address at a given exit node even when they ask for
24774 - Servers no longer ever list themselves in their "family" line,
24775 even if configured to do so. This makes it easier to configure
24776 family lists conveniently.
24777 - When running as a server, don't fall back to 127.0.0.1 when no
24778 nameservers are configured in /etc/resolv.conf; instead, make the
24779 user fix resolv.conf or specify nameservers explicitly. (Resolves
24781 - Stop accepting certain malformed ports in configured exit policies.
24782 - Don't re-write the fingerprint file every restart, unless it has
24784 - Stop warning when a single nameserver fails: only warn when _all_ of
24785 our nameservers have failed. Also, when we only have one nameserver,
24786 raise the threshold for deciding that the nameserver is dead.
24787 - Directory authorities now only decide that routers are reachable
24788 if their identity keys are as expected.
24789 - When the user uses bad syntax in the Log config line, stop
24790 suggesting other bad syntax as a replacement.
24791 - Correctly detect ipv6 DNS capability on OpenBSD.
24793 o Minor bugfixes (controller):
24794 - Report the circuit number correctly in STREAM CLOSED events. Bug
24795 reported by Mike Perry.
24796 - Do not report bizarre values for results of accounting GETINFOs
24797 when the last second's write or read exceeds the allotted bandwidth.
24798 - Report "unrecognized key" rather than an empty string when the
24799 controller tries to fetch a networkstatus that doesn't exist.
24802 Changes in version 0.1.1.26 - 2006-12-14
24803 o Security bugfixes:
24804 - Stop sending the HttpProxyAuthenticator string to directory
24805 servers when directory connections are tunnelled through Tor.
24806 - Clients no longer store bandwidth history in the state file.
24807 - Do not log introduction points for hidden services if SafeLogging
24811 - Fix an assert failure when a directory authority sets
24812 AuthDirRejectUnlisted and then receives a descriptor from an
24813 unlisted router (reported by seeess).
24816 Changes in version 0.1.2.4-alpha - 2006-12-03
24818 - Add support for using natd; this allows FreeBSDs earlier than
24819 5.1.2 to have ipfw send connections through Tor without using
24820 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
24823 - Make all connections to addresses of the form ".noconnect"
24824 immediately get closed. This lets application/controller combos
24825 successfully test whether they're talking to the same Tor by
24826 watching for STREAM events.
24827 - Make cross.sh cross-compilation script work even when autogen.sh
24828 hasn't been run. (Patch from Michael Mohr.)
24829 - Statistics dumped by -USR2 now include a breakdown of public key
24830 operations, for profiling.
24833 - Fix a major leak when directory authorities parse their
24834 approved-routers list, a minor memory leak when we fail to pick
24835 an exit node, and a few rare leaks on errors.
24836 - Handle TransPort connections even when the server sends data before
24837 the client sends data. Previously, the connection would just hang
24838 until the client sent data. (Patch from tup based on patch from
24840 - Avoid assert failure when our cached-routers file is empty on
24844 - Don't log spurious warnings when we see a circuit close reason we
24845 don't recognize; it's probably just from a newer version of Tor.
24846 - Have directory authorities allow larger amounts of drift in uptime
24847 without replacing the server descriptor: previously, a server that
24848 restarted every 30 minutes could have 48 "interesting" descriptors
24850 - Start linking to the Tor specification and Tor reference manual
24851 correctly in the Windows installer.
24852 - Add Vidalia to the OS X uninstaller script, so when we uninstall
24853 Tor/Privoxy we also uninstall Vidalia.
24854 - Resume building on Irix64, and fix a lot of warnings from its
24855 MIPSpro C compiler.
24856 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
24857 when we're running as a client.
24860 Changes in version 0.1.1.25 - 2006-11-04
24862 - When a client asks us to resolve (rather than connect to)
24863 an address, and we have a cached answer, give them the cached
24864 answer. Previously, we would give them no answer at all.
24865 - We were building exactly the wrong circuits when we predict
24866 hidden service requirements, meaning Tor would have to build all
24867 its circuits on demand.
24868 - If none of our live entry guards have a high uptime, but we
24869 require a guard with a high uptime, try adding a new guard before
24870 we give up on the requirement. This patch should make long-lived
24871 connections more stable on average.
24872 - When testing reachability of our DirPort, don't launch new
24873 tests when there's already one in progress -- unreachable
24874 servers were stacking up dozens of testing streams.
24876 o Security bugfixes:
24877 - When the user sends a NEWNYM signal, clear the client-side DNS
24878 cache too. Otherwise we continue to act on previous information.
24881 - Avoid a memory corruption bug when creating a hash table for
24883 - Avoid possibility of controller-triggered crash when misusing
24884 certain commands from a v0 controller on platforms that do not
24885 handle printf("%s",NULL) gracefully.
24886 - Avoid infinite loop on unexpected controller input.
24887 - Don't log spurious warnings when we see a circuit close reason we
24888 don't recognize; it's probably just from a newer version of Tor.
24889 - Add Vidalia to the OS X uninstaller script, so when we uninstall
24890 Tor/Privoxy we also uninstall Vidalia.
24893 Changes in version 0.1.2.3-alpha - 2006-10-29
24895 - Prepare for servers to publish descriptors less often: never
24896 discard a descriptor simply for being too old until either it is
24897 recommended by no authorities, or until we get a better one for
24898 the same router. Make caches consider retaining old recommended
24899 routers for even longer.
24900 - If most authorities set a BadExit flag for a server, clients
24901 don't think of it as a general-purpose exit. Clients only consider
24902 authorities that advertise themselves as listing bad exits.
24903 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
24904 headers for content, so that we can work better in the presence of
24905 caching HTTP proxies.
24906 - Allow authorities to list nodes as bad exits by fingerprint or by
24909 o Minor features, controller:
24910 - Add a REASON field to CIRC events; for backward compatibility, this
24911 field is sent only to controllers that have enabled the extended
24912 event format. Also, add additional reason codes to explain why
24913 a given circuit has been destroyed or truncated. (Patches from
24915 - Add a REMOTE_REASON field to extended CIRC events to tell the
24916 controller about why a remote OR told us to close a circuit.
24917 - Stream events also now have REASON and REMOTE_REASON fields,
24918 working much like those for circuit events.
24919 - There's now a GETINFO ns/... field so that controllers can ask Tor
24920 about the current status of a router.
24921 - A new event type "NS" to inform a controller when our opinion of
24922 a router's status has changed.
24923 - Add a GETINFO events/names and GETINFO features/names so controllers
24924 can tell which events and features are supported.
24925 - A new CLEARDNSCACHE signal to allow controllers to clear the
24926 client-side DNS cache without expiring circuits.
24928 o Security bugfixes:
24929 - When the user sends a NEWNYM signal, clear the client-side DNS
24930 cache too. Otherwise we continue to act on previous information.
24933 - Avoid sending junk to controllers or segfaulting when a controller
24934 uses EVENT_NEW_DESC with verbose nicknames.
24935 - Stop triggering asserts if the controller tries to extend hidden
24936 service circuits (reported by mwenge).
24937 - Avoid infinite loop on unexpected controller input.
24938 - When the controller does a "GETINFO network-status", tell it
24939 about even those routers whose descriptors are very old, and use
24940 long nicknames where appropriate.
24941 - Change NT service functions to be loaded on demand. This lets us
24942 build with MinGW without breaking Tor for Windows 98 users.
24943 - Do DirPort reachability tests less often, since a single test
24944 chews through many circuits before giving up.
24945 - In the hidden service example in torrc.sample, stop recommending
24946 esoteric and discouraged hidden service options.
24947 - When stopping an NT service, wait up to 10 sec for it to actually
24948 stop. Patch from Matt Edman; resolves bug 295.
24949 - Fix handling of verbose nicknames with ORCONN controller events:
24950 make them show up exactly when requested, rather than exactly when
24952 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
24953 printing a duplicate "$" in the keys we send (reported by mwenge).
24954 - Correctly set maximum connection limit on Cygwin. (This time
24956 - Try to detect Windows correctly when cross-compiling.
24957 - Detect the size of the routers file correctly even if it is
24958 corrupted (on systems without mmap) or not page-aligned (on systems
24959 with mmap). This bug was harmless.
24960 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
24961 to open a stream fails; now we do in more cases. This should
24962 make clients able to find a good exit faster in some cases, since
24963 unhandleable requests will now get an error rather than timing out.
24964 - Resolve two memory leaks when rebuilding the on-disk router cache
24965 (reported by fookoowa).
24966 - Clean up minor code warnings suggested by the MIPSpro C compiler,
24967 and reported by some Centos users.
24968 - Controller signals now work on non-Unix platforms that don't define
24969 SIGUSR1 and SIGUSR2 the way we expect.
24970 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
24971 values before failing, and always enables eventdns.
24972 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
24973 Try to fix this in configure.in by checking for most functions
24974 before we check for libevent.
24977 Changes in version 0.1.2.2-alpha - 2006-10-07
24979 - Make our async eventdns library on-by-default for Tor servers,
24980 and plan to deprecate the separate dnsworker threads.
24981 - Add server-side support for "reverse" DNS lookups (using PTR
24982 records so clients can determine the canonical hostname for a given
24983 IPv4 address). Only supported by servers using eventdns; servers
24984 now announce in their descriptors whether they support eventdns.
24985 - Specify and implement client-side SOCKS5 interface for reverse DNS
24986 lookups (see doc/socks-extensions.txt).
24987 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
24988 connect to directory servers through Tor. Previously, clients needed
24989 to find Tor exits to make private connections to directory servers.
24990 - Avoid choosing Exit nodes for entry or middle hops when the
24991 total bandwidth available from non-Exit nodes is much higher than
24992 the total bandwidth available from Exit nodes.
24993 - Workaround for name servers (like Earthlink's) that hijack failing
24994 DNS requests and replace the no-such-server answer with a "helpful"
24995 redirect to an advertising-driven search portal. Also work around
24996 DNS hijackers who "helpfully" decline to hijack known-invalid
24997 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
24998 lets you turn it off.
24999 - Send out a burst of long-range padding cells once we've established
25000 that we're reachable. Spread them over 4 circuits, so hopefully
25001 a few will be fast. This exercises our bandwidth and bootstraps
25002 us into the directory more quickly.
25004 o New/improved config options:
25005 - Add new config option "ResolvConf" to let the server operator
25006 choose an alternate resolve.conf file when using eventdns.
25007 - Add an "EnforceDistinctSubnets" option to control our "exclude
25008 servers on the same /16" behavior. It's still on by default; this
25009 is mostly for people who want to operate private test networks with
25010 all the machines on the same subnet.
25011 - If one of our entry guards is on the ExcludeNodes list, or the
25012 directory authorities don't think it's a good guard, treat it as
25013 if it were unlisted: stop using it as a guard, and throw it off
25014 the guards list if it stays that way for a long time.
25015 - Allow directory authorities to be marked separately as authorities
25016 for the v1 directory protocol, the v2 directory protocol, and
25017 as hidden service directories, to make it easier to retire old
25018 authorities. V1 authorities should set "HSAuthoritativeDir 1"
25019 to continue being hidden service authorities too.
25020 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
25022 o Minor features, controller:
25023 - Fix CIRC controller events so that controllers can learn the
25024 identity digests of non-Named servers used in circuit paths.
25025 - Let controllers ask for more useful identifiers for servers. Instead
25026 of learning identity digests for un-Named servers and nicknames
25027 for Named servers, the new identifiers include digest, nickname,
25028 and indication of Named status. Off by default; see control-spec.txt
25029 for more information.
25030 - Add a "getinfo address" controller command so it can display Tor's
25031 best guess to the user.
25032 - New controller event to alert the controller when our server
25033 descriptor has changed.
25034 - Give more meaningful errors on controller authentication failure.
25036 o Minor features, other:
25037 - When asked to resolve a hostname, don't use non-exit servers unless
25038 requested to do so. This allows servers with broken DNS to be
25039 useful to the network.
25040 - Divide eventdns log messages into warn and info messages.
25041 - Reserve the nickname "Unnamed" for routers that can't pick
25042 a hostname: any router can call itself Unnamed; directory
25043 authorities will never allocate Unnamed to any particular router;
25044 clients won't believe that any router is the canonical Unnamed.
25045 - Only include function names in log messages for info/debug messages.
25046 For notice/warn/err, the content of the message should be clear on
25047 its own, and printing the function name only confuses users.
25048 - Avoid some false positives during reachability testing: don't try
25049 to test via a server that's on the same /24 as us.
25050 - If we fail to build a circuit to an intended enclave, and it's
25051 not mandatory that we use that enclave, stop wanting it.
25052 - When eventdns is enabled, allow multithreaded builds on NetBSD and
25053 OpenBSD. (We had previously disabled threads on these platforms
25054 because they didn't have working thread-safe resolver functions.)
25056 o Major bugfixes, anonymity/security:
25057 - If a client asked for a server by name, and there's a named server
25058 in our network-status but we don't have its descriptor yet, we
25059 could return an unnamed server instead.
25060 - Fix NetBSD bug that could allow someone to force uninitialized RAM
25061 to be sent to a server's DNS resolver. This only affects NetBSD
25062 and other platforms that do not bounds-check tolower().
25063 - Reject (most) attempts to use Tor circuits with length one. (If
25064 many people start using Tor as a one-hop proxy, exit nodes become
25065 a more attractive target for compromise.)
25066 - Just because your DirPort is open doesn't mean people should be
25067 able to remotely teach you about hidden service descriptors. Now
25068 only accept rendezvous posts if you've got HSAuthoritativeDir set.
25070 o Major bugfixes, other:
25071 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
25072 - When a client asks the server to resolve (not connect to)
25073 an address, and it has a cached answer, give them the cached answer.
25074 Previously, the server would give them no answer at all.
25075 - Allow really slow clients to not hang up five minutes into their
25076 directory downloads (suggested by Adam J. Richter).
25077 - We were building exactly the wrong circuits when we anticipated
25078 hidden service requirements, meaning Tor would have to build all
25079 its circuits on demand.
25080 - Avoid crashing when we mmap a router cache file of size 0.
25081 - When testing reachability of our DirPort, don't launch new
25082 tests when there's already one in progress -- unreachable
25083 servers were stacking up dozens of testing streams.
25085 o Minor bugfixes, correctness:
25086 - If we're a directory mirror and we ask for "all" network status
25087 documents, we would discard status documents from authorities
25088 we don't recognize.
25089 - Avoid a memory corruption bug when creating a hash table for
25091 - Avoid controller-triggered crash when misusing certain commands
25092 from a v0 controller on platforms that do not handle
25093 printf("%s",NULL) gracefully.
25094 - Don't crash when a controller sends a third argument to an
25095 "extendcircuit" request.
25096 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
25097 response; fix error code when "getinfo dir/status/" fails.
25098 - Avoid crash when telling controller stream-status and a stream
25100 - Patch from Adam Langley to fix assert() in eventdns.c.
25101 - Fix a debug log message in eventdns to say "X resolved to Y"
25102 instead of "X resolved to X".
25103 - Make eventdns give strings for DNS errors, not just error numbers.
25104 - Track unreachable entry guards correctly: don't conflate
25105 'unreachable by us right now' with 'listed as down by the directory
25106 authorities'. With the old code, if a guard was unreachable by
25107 us but listed as running, it would clog our guard list forever.
25108 - Behave correctly in case we ever have a network with more than
25109 2GB/s total advertised capacity.
25110 - Make TrackExitHosts case-insensitive, and fix the behavior of
25111 ".suffix" TrackExitHosts items to avoid matching in the middle of
25113 - Finally fix the openssl warnings from newer gccs that believe that
25114 ignoring a return value is okay, but casting a return value and
25115 then ignoring it is a sign of madness.
25116 - Prevent the contrib/exitlist script from printing the same
25117 result more than once.
25118 - Patch from Steve Hildrey: Generate network status correctly on
25119 non-versioning dirservers.
25120 - Don't listen to the X-Your-Address-Is hint if you did the lookup
25121 via Tor; otherwise you'll think you're the exit node's IP address.
25123 o Minor bugfixes, performance:
25124 - Two small performance improvements on parsing descriptors.
25125 - Major performance improvement on inserting descriptors: change
25126 algorithm from O(n^2) to O(n).
25127 - Make the common memory allocation path faster on machines where
25128 malloc(0) returns a pointer.
25129 - Start remembering X-Your-Address-Is directory hints even if you're
25130 a client, so you can become a server more smoothly.
25131 - Avoid duplicate entries on MyFamily line in server descriptor.
25133 o Packaging, features:
25134 - Remove architecture from OS X builds. The official builds are
25135 now universal binaries.
25136 - The Debian package now uses --verify-config when (re)starting,
25137 to distinguish configuration errors from other errors.
25138 - Update RPMs to require libevent 1.1b.
25140 o Packaging, bugfixes:
25141 - Patches so Tor builds with MinGW on Windows.
25142 - Patches so Tor might run on Cygwin again.
25143 - Resume building on non-gcc compilers and ancient gcc. Resume
25144 building with the -O0 compile flag. Resume building cleanly on
25146 - Run correctly on OS X platforms with case-sensitive filesystems.
25147 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
25148 - Add autoconf checks so Tor can build on Solaris x86 again.
25151 - Documented (and renamed) ServerDNSSearchDomains and
25152 ServerDNSResolvConfFile options.
25153 - Be clearer that the *ListenAddress directives can be repeated
25157 Changes in version 0.1.1.24 - 2006-09-29
25159 - Allow really slow clients to not hang up five minutes into their
25160 directory downloads (suggested by Adam J. Richter).
25161 - Fix major performance regression from 0.1.0.x: instead of checking
25162 whether we have enough directory information every time we want to
25163 do something, only check when the directory information has changed.
25164 This should improve client CPU usage by 25-50%.
25165 - Don't crash if, after a server has been running for a while,
25166 it can't resolve its hostname.
25169 - Allow Tor to start when RunAsDaemon is set but no logs are set.
25170 - Don't crash when the controller receives a third argument to an
25171 "extendcircuit" request.
25172 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
25173 response; fix error code when "getinfo dir/status/" fails.
25174 - Fix configure.in to not produce broken configure files with
25175 more recent versions of autoconf. Thanks to Clint for his auto*
25177 - Fix security bug on NetBSD that could allow someone to force
25178 uninitialized RAM to be sent to a server's DNS resolver. This
25179 only affects NetBSD and other platforms that do not bounds-check
25181 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
25182 methods: these are known to be buggy.
25183 - If we're a directory mirror and we ask for "all" network status
25184 documents, we would discard status documents from authorities
25185 we don't recognize.
25188 Changes in version 0.1.2.1-alpha - 2006-08-27
25190 - Add "eventdns" async dns library from Adam Langley, tweaked to
25191 build on OSX and Windows. Only enabled if you pass the
25192 --enable-eventdns argument to configure.
25193 - Allow servers with no hostname or IP address to learn their
25194 IP address by asking the directory authorities. This code only
25195 kicks in when you would normally have exited with a "no address"
25196 error. Nothing's authenticated, so use with care.
25197 - Rather than waiting a fixed amount of time between retrying
25198 application connections, we wait only 5 seconds for the first,
25199 10 seconds for the second, and 15 seconds for each retry after
25200 that. Hopefully this will improve the expected user experience.
25201 - Patch from Tup to add support for transparent AP connections:
25202 this basically bundles the functionality of trans-proxy-tor
25203 into the Tor mainline. Now hosts with compliant pf/netfilter
25204 implementations can redirect TCP connections straight to Tor
25205 without diverting through SOCKS. Needs docs.
25206 - Busy directory servers save lots of memory by spooling server
25207 descriptors, v1 directories, and v2 networkstatus docs to buffers
25208 as needed rather than en masse. Also mmap the cached-routers
25209 files, so we don't need to keep the whole thing in memory too.
25210 - Automatically avoid picking more than one node from the same
25211 /16 network when constructing a circuit.
25212 - Revise and clean up the torrc.sample that we ship with; add
25213 a section for BandwidthRate and BandwidthBurst.
25216 - Split circuit_t into origin_circuit_t and or_circuit_t, and
25217 split connection_t into edge, or, dir, control, and base structs.
25218 These will save quite a bit of memory on busy servers, and they'll
25219 also help us track down bugs in the code and bugs in the spec.
25220 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
25221 or later. Log when we are doing this, so we can diagnose it when
25222 it fails. (Also, recommend libevent 1.1b for kqueue and
25223 win32 methods; deprecate libevent 1.0b harder; make libevent
25224 recommendation system saner.)
25225 - Start being able to build universal binaries on OS X (thanks
25227 - Export the default exit policy via the control port, so controllers
25228 don't need to guess what it is / will be later.
25229 - Add a man page entry for ProtocolWarnings.
25230 - Add TestVia config option to the man page.
25231 - Remove even more protocol-related warnings from Tor server logs,
25232 such as bad TLS handshakes and malformed begin cells.
25233 - Stop fetching descriptors if you're not a dir mirror and you
25234 haven't tried to establish any circuits lately. [This currently
25235 causes some dangerous behavior, because when you start up again
25236 you'll use your ancient server descriptors.]
25237 - New DirPort behavior: if you have your dirport set, you download
25238 descriptors aggressively like a directory mirror, whether or not
25239 your ORPort is set.
25240 - Get rid of the router_retry_connections notion. Now routers
25241 no longer try to rebuild long-term connections to directory
25242 authorities, and directory authorities no longer try to rebuild
25243 long-term connections to all servers. We still don't hang up
25244 connections in these two cases though -- we need to look at it
25245 more carefully to avoid flapping, and we likely need to wait til
25246 0.1.1.x is obsolete.
25247 - Drop compatibility with obsolete Tors that permit create cells
25248 to have the wrong circ_id_type.
25249 - Re-enable per-connection rate limiting. Get rid of the "OP
25250 bandwidth" concept. Lay groundwork for "bandwidth classes" --
25251 separate global buckets that apply depending on what sort of conn
25253 - Start publishing one minute or so after we find our ORPort
25254 to be reachable. This will help reduce the number of descriptors
25255 we have for ourselves floating around, since it's quite likely
25256 other things (e.g. DirPort) will change during that minute too.
25257 - Fork the v1 directory protocol into its own spec document,
25258 and mark dir-spec.txt as the currently correct (v2) spec.
25261 - When we find our DirPort to be reachable, publish a new descriptor
25262 so we'll tell the world (reported by pnx).
25263 - Publish a new descriptor after we hup/reload. This is important
25264 if our config has changed such that we'll want to start advertising
25265 our DirPort now, etc.
25266 - Allow Tor to start when RunAsDaemon is set but no logs are set.
25267 - When we have a state file we cannot parse, tell the user and
25268 move it aside. Now we avoid situations where the user starts
25269 Tor in 1904, Tor writes a state file with that timestamp in it,
25270 the user fixes her clock, and Tor refuses to start.
25271 - Fix configure.in to not produce broken configure files with
25272 more recent versions of autoconf. Thanks to Clint for his auto*
25274 - "tor --verify-config" now exits with -1(255) or 0 depending on
25275 whether the config options are bad or good.
25276 - Resolve bug 321 when using dnsworkers: append a period to every
25277 address we resolve at the exit node, so that we do not accidentally
25278 pick up local addresses, and so that failing searches are retried
25279 in the resolver search domains. (This is already solved for
25280 eventdns.) (This breaks Blossom servers for now.)
25281 - If we are using an exit enclave and we can't connect, e.g. because
25282 its webserver is misconfigured to not listen on localhost, then
25283 back off and try connecting from somewhere else before we fail.
25286 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
25287 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
25288 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
25289 when the IP address is mapped through MapAddress to a hostname.
25290 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
25291 useless IPv6 DNS resolves.
25292 - Patch suggested by Karsten Loesing: respond to SIGNAL command
25293 before we execute the signal, in case the signal shuts us down.
25294 - Clean up AllowInvalidNodes man page entry.
25295 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
25296 - Add more asserts to track down an assert error on a windows Tor
25297 server with connection_add being called with socket == -1.
25298 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
25299 - Fix misleading log messages: an entry guard that is "unlisted",
25300 as well as not known to be "down" (because we've never heard
25301 of it), is not therefore "up".
25302 - Remove code to special-case "-cvs" ending, since it has not
25303 actually mattered since 0.0.9.
25304 - Make our socks5 handling more robust to broken socks clients:
25305 throw out everything waiting on the buffer in between socks
25306 handshake phases, since they can't possibly (so the theory
25307 goes) have predicted what we plan to respond to them.
25310 Changes in version 0.1.1.23 - 2006-07-30
25312 - Fast Tor servers, especially exit nodes, were triggering asserts
25313 due to a bug in handling the list of pending DNS resolves. Some
25314 bugs still remain here; we're hunting them.
25315 - Entry guards could crash clients by sending unexpected input.
25316 - More fixes on reachability testing: if you find yourself reachable,
25317 then don't ever make any client requests (so you stop predicting
25318 circuits), then hup or have your clock jump, then later your IP
25319 changes, you won't think circuits are working, so you won't try to
25320 test reachability, so you won't publish.
25323 - Avoid a crash if the controller does a resetconf firewallports
25324 and then a setconf fascistfirewall=1.
25325 - Avoid an integer underflow when the dir authority decides whether
25326 a router is stable: we might wrongly label it stable, and compute
25327 a slightly wrong median stability, when a descriptor is published
25329 - Fix a place where we might trigger an assert if we can't build our
25330 own server descriptor yet.
25333 Changes in version 0.1.1.22 - 2006-07-05
25335 - Fix a big bug that was causing servers to not find themselves
25336 reachable if they changed IP addresses. Since only 0.1.1.22+
25337 servers can do reachability testing correctly, now we automatically
25338 make sure to test via one of these.
25339 - Fix to allow clients and mirrors to learn directory info from
25340 descriptor downloads that get cut off partway through.
25341 - Directory authorities had a bug in deciding if a newly published
25342 descriptor was novel enough to make everybody want a copy -- a few
25343 servers seem to be publishing new descriptors many times a minute.
25345 - Fix a rare bug that was causing some servers to complain about
25346 "closing wedged cpuworkers" and skip some circuit create requests.
25347 - Make the Exit flag in directory status documents actually work.
25350 Changes in version 0.1.1.21 - 2006-06-10
25351 o Crash and assert fixes from 0.1.1.20:
25352 - Fix a rare crash on Tor servers that have enabled hibernation.
25353 - Fix a seg fault on startup for Tor networks that use only one
25354 directory authority.
25355 - Fix an assert from a race condition that occurs on Tor servers
25356 while exiting, where various threads are trying to log that they're
25357 exiting, and delete the logs, at the same time.
25358 - Make our unit tests pass again on certain obscure platforms.
25361 - Add support for building SUSE RPM packages.
25362 - Speed up initial bootstrapping for clients: if we are making our
25363 first ever connection to any entry guard, then don't mark it down
25365 - When only one Tor server in the network is labelled as a guard,
25366 and we've already picked him, we would cycle endlessly picking him
25367 again, being unhappy about it, etc. Now we specifically exclude
25368 current guards when picking a new guard.
25369 - Servers send create cells more reliably after the TLS connection
25370 is established: we were sometimes forgetting to send half of them
25371 when we had more than one pending.
25372 - If we get a create cell that asks us to extend somewhere, but the
25373 Tor server there doesn't match the expected digest, we now send
25374 a destroy cell back, rather than silently doing nothing.
25375 - Make options->RedirectExit work again.
25376 - Make cookie authentication for the controller work again.
25377 - Stop being picky about unusual characters in the arguments to
25378 mapaddress. It's none of our business.
25379 - Add a new config option "TestVia" that lets you specify preferred
25380 middle hops to use for test circuits. Perhaps this will let me
25381 debug the reachability problems better.
25383 o Log / documentation fixes:
25384 - If we're a server and some peer has a broken TLS certificate, don't
25385 log about it unless ProtocolWarnings is set, i.e., we want to hear
25386 about protocol violations by others.
25387 - Fix spelling of VirtualAddrNetwork in man page.
25388 - Add a better explanation at the top of the autogenerated torrc file
25389 about what happened to our old torrc.
25392 Changes in version 0.1.1.20 - 2006-05-23
25394 - Downgrade a log severity where servers complain that they're
25396 - Avoid a compile warning on FreeBSD.
25397 - Remove string size limit on NEWDESC messages; solve bug 291.
25398 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
25399 more thoroughly when we're running on windows.
25402 Changes in version 0.1.1.19-rc - 2006-05-03
25404 - Regenerate our local descriptor if it's dirty and we try to use
25405 it locally (e.g. if it changes during reachability detection).
25406 - If we setconf our ORPort to 0, we continued to listen on the
25407 old ORPort and receive connections.
25408 - Avoid a second warning about machine/limits.h on Debian
25410 - Be willing to add our own routerinfo into the routerlist.
25411 Now authorities will include themselves in their directories
25412 and network-statuses.
25413 - Stop trying to upload rendezvous descriptors to every
25414 directory authority: only try the v1 authorities.
25415 - Servers no longer complain when they think they're not
25416 registered with the directory authorities. There were too many
25418 - Backport dist-rpm changes so rpms can be built without errors.
25421 - Implement an option, VirtualAddrMask, to set which addresses
25422 get handed out in response to mapaddress requests. This works
25423 around a bug in tsocks where 127.0.0.0/8 is never socksified.
25426 Changes in version 0.1.1.18-rc - 2006-04-10
25428 - Work harder to download live network-statuses from all the
25429 directory authorities we know about. Improve the threshold
25430 decision logic so we're more robust to edge cases.
25431 - When fetching rendezvous descriptors, we were willing to ask
25432 v2 authorities too, which would always return 404.
25435 - Stop listing down or invalid nodes in the v1 directory. This will
25436 reduce its bulk by about 1/3, and reduce load on directory
25438 - When deciding whether a router is Fast or Guard-worthy, consider
25439 his advertised BandwidthRate and not just the BandwidthCapacity.
25440 - No longer ship INSTALL and README files -- they are useless now.
25441 - Force rpmbuild to behave and honor target_cpu.
25442 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
25443 - Start to include translated versions of the tor-doc-*.html
25444 files, along with the screenshots. Still needs more work.
25445 - Start sending back 512 and 451 errors if mapaddress fails,
25446 rather than not sending anything back at all.
25447 - When we fail to bind or listen on an incoming or outgoing
25448 socket, we should close it before failing. otherwise we just
25449 leak it. (thanks to weasel for finding.)
25450 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
25451 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
25452 - Make NoPublish (even though deprecated) work again.
25453 - Fix a minor security flaw where a versioning auth dirserver
25454 could list a recommended version many times in a row to make
25455 clients more convinced that it's recommended.
25456 - Fix crash bug if there are two unregistered servers running
25457 with the same nickname, one of them is down, and you ask for
25458 them by nickname in your EntryNodes or ExitNodes. Also, try
25459 to pick the one that's running rather than an arbitrary one.
25460 - Fix an infinite loop we could hit if we go offline for too long.
25461 - Complain when we hit WSAENOBUFS on recv() or write() too.
25462 Perhaps this will help us hunt the bug.
25463 - If you're not a versioning dirserver, don't put the string
25464 "client-versions \nserver-versions \n" in your network-status.
25465 - Lower the minimum required number of file descriptors to 1000,
25466 so we can have some overhead for Valgrind on Linux, where the
25467 default ulimit -n is 1024.
25470 - Add tor.dizum.com as the fifth authoritative directory server.
25471 - Add a new config option FetchUselessDescriptors, off by default,
25472 for when you plan to run "exitlist" on your client and you want
25473 to know about even the non-running descriptors.
25476 Changes in version 0.1.1.17-rc - 2006-03-28
25478 - Clients and servers since 0.1.1.10-alpha have been expiring
25479 connections whenever they are idle for 5 minutes and they *do*
25480 have circuits on them. Oops. With this new version, clients will
25481 discard their previous entry guard choices and avoid choosing
25482 entry guards running these flawed versions.
25483 - Fix memory leak when uncompressing concatenated zlib streams. This
25484 was causing substantial leaks over time on Tor servers.
25485 - The v1 directory was including servers as much as 48 hours old,
25486 because that's how the new routerlist->routers works. Now only
25487 include them if they're 20 hours old or less.
25490 - Resume building on irix64, netbsd 2.0, etc.
25491 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
25493 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
25494 and it is confusing some users.
25495 - Mirrors stop caching the v1 directory so often.
25496 - Make the max number of old descriptors that a cache will hold
25497 rise with the number of directory authorities, so we can scale.
25498 - Change our win32 uname() hack to be more forgiving about what
25499 win32 versions it thinks it's found.
25502 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
25504 - When the controller's *setconf commands fail, collect an error
25505 message in a string and hand it back to the controller.
25506 - Make the v2 dir's "Fast" flag based on relative capacity, just
25507 like "Stable" is based on median uptime. Name everything in the
25508 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
25509 - Log server fingerprint on startup, so new server operators don't
25510 have to go hunting around their filesystem for it.
25511 - Return a robots.txt on our dirport to discourage google indexing.
25512 - Let the controller ask for GETINFO dir/status/foo so it can ask
25513 directly rather than connecting to the dir port. Only works when
25514 dirport is set for now.
25516 o New config options rather than constants in the code:
25517 - SocksTimeout: How long do we let a socks connection wait
25518 unattached before we fail it?
25519 - CircuitBuildTimeout: Cull non-open circuits that were born
25520 at least this many seconds ago.
25521 - CircuitIdleTimeout: Cull open clean circuits that were born
25522 at least this many seconds ago.
25525 Changes in version 0.1.1.16-rc - 2006-03-18
25526 o Bugfixes on 0.1.1.15-rc:
25527 - Fix assert when the controller asks to attachstream a connect-wait
25528 or resolve-wait stream.
25529 - Now do address rewriting when the controller asks us to attach
25530 to a particular circuit too. This will let Blossom specify
25531 "moria2.exit" without having to learn what moria2's IP address is.
25532 - Make the "tor --verify-config" command-line work again, so people
25533 can automatically check if their torrc will parse.
25534 - Authoritative dirservers no longer require an open connection from
25535 a server to consider him "reachable". We need this change because
25536 when we add new auth dirservers, old servers won't know not to
25538 - Let Tor build on Sun CC again.
25539 - Fix an off-by-one buffer size in dirserv.c that magically never
25540 hit our three authorities but broke sjmurdoch's own tor network.
25541 - If we as a directory mirror don't know of any v1 directory
25542 authorities, then don't try to cache any v1 directories.
25543 - Stop warning about unknown servers in our family when they are
25544 given as hex digests.
25545 - Stop complaining as quickly to the server operator that he
25546 hasn't registered his nickname/key binding.
25547 - Various cleanups so we can add new V2 Auth Dirservers.
25548 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
25549 reflect the updated flags in our v2 dir protocol.
25550 - Resume allowing non-printable characters for exit streams (both
25551 for connecting and for resolving). Now we tolerate applications
25552 that don't follow the RFCs. But continue to block malformed names
25555 o Bugfixes on 0.1.0.x:
25556 - Fix assert bug in close_logs(): when we close and delete logs,
25557 remove them all from the global "logfiles" list.
25558 - Fix minor integer overflow in calculating when we expect to use up
25559 our bandwidth allocation before hibernating.
25560 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
25561 there are multiple SSLs installed with different versions.
25562 - When we try to be a server and Address is not explicitly set and
25563 our hostname resolves to a private IP address, try to use an
25564 interface address if it has a public address. Now Windows machines
25565 that think of themselves as localhost can work by default.
25568 - Let the controller ask for GETINFO dir/server/foo so it can ask
25569 directly rather than connecting to the dir port.
25570 - Let the controller tell us about certain router descriptors
25571 that it doesn't want Tor to use in circuits. Implement
25572 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
25573 - New config option SafeSocks to reject all application connections
25574 using unsafe socks protocols. Defaults to off.
25577 Changes in version 0.1.1.15-rc - 2006-03-11
25578 o Bugfixes and cleanups:
25579 - When we're printing strings from the network, don't try to print
25580 non-printable characters. This protects us against shell escape
25581 sequence exploits, and also against attacks to fool humans into
25582 misreading their logs.
25583 - Fix a bug where Tor would fail to establish any connections if you
25584 left it off for 24 hours and then started it: we were happy with
25585 the obsolete network statuses, but they all referred to router
25586 descriptors that were too old to fetch, so we ended up with no
25587 valid router descriptors.
25588 - Fix a seg fault in the controller's "getinfo orconn-status"
25589 command while listing status on incoming handshaking connections.
25590 Introduce a status name "NEW" for these connections.
25591 - If we get a linelist or linelist_s config option from the torrc
25592 (e.g. ExitPolicy) and it has no value, warn and skip rather than
25593 silently resetting it to its default.
25594 - Don't abandon entry guards until they've been down or gone for
25596 - Cleaner and quieter log messages.
25599 - New controller signal NEWNYM that makes new application requests
25600 use clean circuits.
25601 - Add a new circuit purpose 'controller' to let the controller ask
25602 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
25603 controller command to let you specify the purpose if you're
25604 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
25605 command to let you change a circuit's purpose after it's been
25607 - Accept "private:*" in routerdesc exit policies; not generated yet
25608 because older Tors do not understand it.
25609 - Add BSD-style contributed startup script "rc.subr" from Peter
25613 Changes in version 0.1.1.14-alpha - 2006-02-20
25614 o Bugfixes on 0.1.1.x:
25615 - Don't die if we ask for a stdout or stderr log (even implicitly)
25616 and we're set to RunAsDaemon -- just warn.
25617 - We still had a few bugs in the OR connection rotation code that
25618 caused directory servers to slowly aggregate connections to other
25619 fast Tor servers. This time for sure!
25620 - Make log entries on Win32 include the name of the function again.
25621 - We were treating a pair of exit policies if they were equal even
25622 if one said accept and the other said reject -- causing us to
25623 not always publish a new descriptor since we thought nothing
25625 - Retry pending server downloads as well as pending networkstatus
25626 downloads when we unexpectedly get a socks request.
25627 - We were ignoring the IS_FAST flag in the directory status,
25628 meaning we were willing to pick trivial-bandwidth nodes for "fast"
25630 - If the controller's SAVECONF command fails (e.g. due to file
25631 permissions), let the controller know that it failed.
25634 - If we're trying to be a Tor server and running Windows 95/98/ME
25635 as a server, explain that we'll likely crash.
25636 - When we're a server, a client asks for an old-style directory,
25637 and our write bucket is empty, don't give it to him. This way
25638 small servers can continue to serve the directory *sometimes*,
25639 without getting overloaded.
25640 - Compress exit policies even more -- look for duplicate lines
25642 - Clients now honor the "guard" flag in the router status when
25643 picking entry guards, rather than looking at is_fast or is_stable.
25644 - Retain unrecognized lines in $DATADIR/state file, so that we can
25645 be forward-compatible.
25646 - Generate 18.0.0.0/8 address policy format in descs when we can;
25647 warn when the mask is not reducible to a bit-prefix.
25648 - Let the user set ControlListenAddress in the torrc. This can be
25649 dangerous, but there are some cases (like a secured LAN) where it
25651 - Split ReachableAddresses into ReachableDirAddresses and
25652 ReachableORAddresses, so we can restrict Dir conns to port 80
25653 and OR conns to port 443.
25654 - Now we can target arch and OS in rpm builds (contributed by
25655 Phobos). Also make the resulting dist-rpm filename match the
25657 - New config options to help controllers: FetchServerDescriptors
25658 and FetchHidServDescriptors for whether to fetch server
25659 info and hidserv info or let the controller do it, and
25660 PublishServerDescriptor and PublishHidServDescriptors.
25661 - Also let the controller set the __AllDirActionsPrivate config
25662 option if you want all directory fetches/publishes to happen via
25663 Tor (it assumes your controller bootstraps your circuits).
25666 Changes in version 0.1.0.17 - 2006-02-17
25667 o Crash bugfixes on 0.1.0.x:
25668 - When servers with a non-zero DirPort came out of hibernation,
25669 sometimes they would trigger an assert.
25671 o Other important bugfixes:
25672 - On platforms that don't have getrlimit (like Windows), we were
25673 artificially constraining ourselves to a max of 1024
25674 connections. Now just assume that we can handle as many as 15000
25675 connections. Hopefully this won't cause other problems.
25677 o Backported features:
25678 - When we're a server, a client asks for an old-style directory,
25679 and our write bucket is empty, don't give it to him. This way
25680 small servers can continue to serve the directory *sometimes*,
25681 without getting overloaded.
25682 - Whenever you get a 503 in response to a directory fetch, try
25683 once more. This will become important once servers start sending
25684 503's whenever they feel busy.
25685 - Fetch a new directory every 120 minutes, not every 40 minutes.
25686 Now that we have hundreds of thousands of users running the old
25687 directory algorithm, it's starting to hurt a lot.
25688 - Bump up the period for forcing a hidden service descriptor upload
25689 from 20 minutes to 1 hour.
25692 Changes in version 0.1.1.13-alpha - 2006-02-09
25693 o Crashes in 0.1.1.x:
25694 - When you tried to setconf ORPort via the controller, Tor would
25695 crash. So people using TorCP to become a server were sad.
25696 - Solve (I hope) the stack-smashing bug that we were seeing on fast
25697 servers. The problem appears to be something do with OpenSSL's
25698 random number generation, or how we call it, or something. Let me
25699 know if the crashes continue.
25700 - Turn crypto hardware acceleration off by default, until we find
25701 somebody smart who can test it for us. (It appears to produce
25702 seg faults in at least some cases.)
25703 - Fix a rare assert error when we've tried all intro points for
25704 a hidden service and we try fetching the service descriptor again:
25705 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
25708 - Fix a major load balance bug: we were round-robining in 16 KB
25709 chunks, and servers with bandwidthrate of 20 KB, while downloading
25710 a 600 KB directory, would starve their other connections. Now we
25711 try to be a bit more fair.
25712 - Dir authorities and mirrors were never expiring the newest
25713 descriptor for each server, causing memory and directory bloat.
25714 - Fix memory-bloating and connection-bloating bug on servers: We
25715 were never closing any connection that had ever had a circuit on
25716 it, because we were checking conn->n_circuits == 0, yet we had a
25717 bug that let it go negative.
25718 - Make Tor work using squid as your http proxy again -- squid
25719 returns an error if you ask for a URL that's too long, and it uses
25720 a really generic error message. Plus, many people are behind a
25721 transparent squid so they don't even realize it.
25722 - On platforms that don't have getrlimit (like Windows), we were
25723 artificially constraining ourselves to a max of 1024
25724 connections. Now just assume that we can handle as many as 15000
25725 connections. Hopefully this won't cause other problems.
25726 - Add a new config option ExitPolicyRejectPrivate which defaults to
25727 1. This means all exit policies will begin with rejecting private
25728 addresses, unless the server operator explicitly turns it off.
25731 - Clients no longer download descriptors for non-running
25733 - Before we add new directory authorities, we should make it
25734 clear that only v1 authorities should receive/publish hidden
25735 service descriptors.
25738 - As soon as we've fetched some more directory info, immediately
25739 try to download more server descriptors. This way we don't have
25740 a 10 second pause during initial bootstrapping.
25741 - Remove even more loud log messages that the server operator can't
25743 - When we're running an obsolete or un-recommended version, make
25744 the log message more clear about what the problem is and what
25745 versions *are* still recommended.
25746 - Provide a more useful warn message when our onion queue gets full:
25747 the CPU is too slow or the exit policy is too liberal.
25748 - Don't warn when we receive a 503 from a dirserver/cache -- this
25749 will pave the way for them being able to refuse if they're busy.
25750 - When we fail to bind a listener, try to provide a more useful
25751 log message: e.g., "Is Tor already running?"
25752 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
25753 Goldberg can prove things about our handshake protocol more
25755 - MaxConn has been obsolete for a while now. Document the ConnLimit
25756 config option, which is a *minimum* number of file descriptors
25757 that must be available else Tor refuses to start.
25758 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
25759 if you log to syslog and want something other than LOG_DAEMON.
25760 - Make dirservers generate a separate "guard" flag to mean,
25761 "would make a good entry guard". Make clients parse it and vote
25762 on it. Not used by clients yet.
25763 - Implement --with-libevent-dir option to ./configure. Also, improve
25764 search techniques to find libevent, and use those for openssl too.
25765 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
25766 - Only start testing reachability once we've established a
25767 circuit. This will make startup on dirservers less noisy.
25768 - Don't try to upload hidden service descriptors until we have
25769 established a circuit.
25770 - Fix the controller's "attachstream 0" command to treat conn like
25771 it just connected, doing address remapping, handling .exit and
25772 .onion idioms, and so on. Now we're more uniform in making sure
25773 that the controller hears about new and closing connections.
25776 Changes in version 0.1.1.12-alpha - 2006-01-11
25777 o Bugfixes on 0.1.1.x:
25778 - The fix to close duplicate server connections was closing all
25779 Tor client connections if they didn't establish a circuit
25780 quickly enough. Oops.
25781 - Fix minor memory issue (double-free) that happened on exit.
25783 o Bugfixes on 0.1.0.x:
25784 - Tor didn't warn when it failed to open a log file.
25787 Changes in version 0.1.1.11-alpha - 2006-01-10
25788 o Crashes in 0.1.1.x:
25789 - Include all the assert/crash fixes from 0.1.0.16.
25790 - If you start Tor and then quit very quickly, there were some
25791 races that tried to free things that weren't allocated yet.
25792 - Fix a rare memory stomp if you're running hidden services.
25793 - Fix segfault when specifying DirServer in config without nickname.
25794 - Fix a seg fault when you finish connecting to a server but at
25795 that moment you dump his server descriptor.
25796 - Extendcircuit and Attachstream controller commands would
25797 assert/crash if you don't give them enough arguments.
25798 - Fix an assert error when we're out of space in the connection_list
25799 and we try to post a hidden service descriptor (reported by weasel).
25800 - If you specify a relative torrc path and you set RunAsDaemon in
25801 your torrc, then it chdir()'s to the new directory. If you HUP,
25802 it tries to load the new torrc location, fails, and exits.
25803 The fix: no longer allow a relative path to torrc using -f.
25806 - Implement "entry guards": automatically choose a handful of entry
25807 nodes and stick with them for all circuits. Only pick new guards
25808 when the ones you have are unsuitable, and if the old guards
25809 become suitable again, switch back. This will increase security
25810 dramatically against certain end-point attacks. The EntryNodes
25811 config option now provides some hints about which entry guards you
25812 want to use most; and StrictEntryNodes means to only use those.
25813 - New directory logic: download by descriptor digest, not by
25814 fingerprint. Caches try to download all listed digests from
25815 authorities; clients try to download "best" digests from caches.
25816 This avoids partitioning and isolating attacks better.
25817 - Make the "stable" router flag in network-status be the median of
25818 the uptimes of running valid servers, and make clients pay
25819 attention to the network-status flags. Thus the cutoff adapts
25820 to the stability of the network as a whole, making IRC, IM, etc
25821 connections more reliable.
25824 - Tor servers with dynamic IP addresses were needing to wait 18
25825 hours before they could start doing reachability testing using
25826 the new IP address and ports. This is because they were using
25827 the internal descriptor to learn what to test, yet they were only
25828 rebuilding the descriptor once they decided they were reachable.
25829 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
25830 to download certain server descriptors, throw them away, and then
25831 fetch them again after 30 minutes. Now mirrors throw away these
25832 server descriptors so clients can't get them.
25833 - We were leaving duplicate connections to other ORs open for a week,
25834 rather than closing them once we detect a duplicate. This only
25835 really affected authdirservers, but it affected them a lot.
25836 - Spread the authdirservers' reachability testing over the entire
25837 testing interval, so we don't try to do 500 TLS's at once every
25841 - If the network is down, and we try to connect to a conn because
25842 we have a circuit in mind, and we timeout (30 seconds) because the
25843 network never answers, we were expiring the circuit, but we weren't
25844 obsoleting the connection or telling the entry_guards functions.
25845 - Some Tor servers process billions of cells per day. These statistics
25846 need to be uint64_t's.
25847 - Check for integer overflows in more places, when adding elements
25848 to smartlists. This could possibly prevent a buffer overflow
25849 on malicious huge inputs. I don't see any, but I haven't looked
25851 - ReachableAddresses kept growing new "reject *:*" lines on every
25853 - When you "setconf log" via the controller, it should remove all
25854 logs. We were automatically adding back in a "log notice stdout".
25855 - Newly bootstrapped Tor networks couldn't establish hidden service
25856 circuits until they had nodes with high uptime. Be more tolerant.
25857 - We were marking servers down when they could not answer every piece
25858 of the directory request we sent them. This was far too harsh.
25859 - Fix the torify (tsocks) config file to not use Tor for localhost
25861 - Directory authorities now go to the proper authority when asking for
25862 a networkstatus, even when they want a compressed one.
25863 - Fix a harmless bug that was causing Tor servers to log
25864 "Got an end because of misc error, but we're not an AP. Closing."
25865 - Authorities were treating their own descriptor changes as cosmetic,
25866 meaning the descriptor available in the network-status and the
25867 descriptor that clients downloaded were different.
25868 - The OS X installer was adding a symlink for tor_resolve but
25869 the binary was called tor-resolve (reported by Thomas Hardly).
25870 - Workaround a problem with some http proxies where they refuse GET
25871 requests that specify "Content-Length: 0" (reported by Adrian).
25872 - Fix wrong log message when you add a "HiddenServiceNodes" config
25873 line without any HiddenServiceDir line (reported by Chris Thomas).
25876 - Write the TorVersion into the state file so we have a prayer of
25877 keeping forward and backward compatibility.
25878 - Revive the FascistFirewall config option rather than eliminating it:
25879 now it's a synonym for ReachableAddresses *:80,*:443.
25880 - Clients choose directory servers from the network status lists,
25881 not from their internal list of router descriptors. Now they can
25882 go to caches directly rather than needing to go to authorities
25884 - Directory authorities ignore router descriptors that have only
25885 cosmetic differences: do this for 0.1.0.x servers now too.
25886 - Add a new flag to network-status indicating whether the server
25887 can answer v2 directory requests too.
25888 - Authdirs now stop whining so loudly about bad descriptors that
25889 they fetch from other dirservers. So when there's a log complaint,
25890 it's for sure from a freshly uploaded descriptor.
25891 - Reduce memory requirements in our structs by changing the order
25893 - There used to be two ways to specify your listening ports in a
25894 server descriptor: on the "router" line and with a separate "ports"
25895 line. Remove support for the "ports" line.
25896 - New config option "AuthDirRejectUnlisted" for auth dirservers as
25897 a panic button: if we get flooded with unusable servers we can
25898 revert to only listing servers in the approved-routers file.
25899 - Auth dir servers can now mark a fingerprint as "!reject" or
25900 "!invalid" in the approved-routers file (as its nickname), to
25901 refuse descriptors outright or include them but marked as invalid.
25902 - Servers store bandwidth history across restarts/crashes.
25903 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
25904 get a better idea of why their circuits failed. Not used yet.
25905 - Directory mirrors now cache up to 16 unrecognized network-status
25906 docs. Now we can add new authdirservers and they'll be cached too.
25907 - When picking a random directory, prefer non-authorities if any
25909 - New controller option "getinfo desc/all-recent" to fetch the
25910 latest server descriptor for every router that Tor knows about.
25913 Changes in version 0.1.0.16 - 2006-01-02
25914 o Crash bugfixes on 0.1.0.x:
25915 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
25916 corrupting the heap, losing FDs, or crashing when we need to resize
25917 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
25918 - It turns out sparc64 platforms crash on unaligned memory access
25919 too -- so detect and avoid this.
25920 - Handle truncated compressed data correctly (by detecting it and
25922 - Fix possible-but-unlikely free(NULL) in control.c.
25923 - When we were closing connections, there was a rare case that
25924 stomped on memory, triggering seg faults and asserts.
25925 - Avoid potential infinite recursion when building a descriptor. (We
25926 don't know that it ever happened, but better to fix it anyway.)
25927 - We were neglecting to unlink marked circuits from soon-to-close OR
25928 connections, which caused some rare scribbling on freed memory.
25929 - Fix a memory stomping race bug when closing the joining point of two
25930 rendezvous circuits.
25931 - Fix an assert in time parsing found by Steven Murdoch.
25933 o Other bugfixes on 0.1.0.x:
25934 - When we're doing reachability testing, provide more useful log
25935 messages so the operator knows what to expect.
25936 - Do not check whether DirPort is reachable when we are suppressing
25937 advertising it because of hibernation.
25938 - When building with -static or on Solaris, we sometimes needed -ldl.
25939 - When we're deciding whether a stream has enough circuits around
25940 that can handle it, count the freshly dirty ones and not the ones
25941 that are so dirty they won't be able to handle it.
25942 - When we're expiring old circuits, we had a logic error that caused
25943 us to close new rendezvous circuits rather than old ones.
25944 - Give a more helpful log message when you try to change ORPort via
25945 the controller: you should upgrade Tor if you want that to work.
25946 - We were failing to parse Tor versions that start with "Tor ".
25947 - Tolerate faulty streams better: when a stream fails for reason
25948 exitpolicy, stop assuming that the router is lying about his exit
25949 policy. When a stream fails for reason misc, allow it to retry just
25950 as if it was resolvefailed. When a stream has failed three times,
25951 reset its failure count so we can try again and get all three tries.
25954 Changes in version 0.1.1.10-alpha - 2005-12-11
25955 o Correctness bugfixes on 0.1.0.x:
25956 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
25957 corrupting the heap, losing FDs, or crashing when we need to resize
25958 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
25959 - Stop doing the complex voodoo overkill checking for insecure
25960 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
25961 - When we were closing connections, there was a rare case that
25962 stomped on memory, triggering seg faults and asserts.
25963 - We were neglecting to unlink marked circuits from soon-to-close OR
25964 connections, which caused some rare scribbling on freed memory.
25965 - When we're deciding whether a stream has enough circuits around
25966 that can handle it, count the freshly dirty ones and not the ones
25967 that are so dirty they won't be able to handle it.
25968 - Recover better from TCP connections to Tor servers that are
25969 broken but don't tell you (it happens!); and rotate TLS
25970 connections once a week.
25971 - When we're expiring old circuits, we had a logic error that caused
25972 us to close new rendezvous circuits rather than old ones.
25973 - Fix a scary-looking but apparently harmless bug where circuits
25974 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
25975 servers, and never switch to state CIRCUIT_STATE_OPEN.
25976 - When building with -static or on Solaris, we sometimes needed to
25978 - Give a useful message when people run Tor as the wrong user,
25979 rather than telling them to start chowning random directories.
25980 - We were failing to inform the controller about new .onion streams.
25982 o Security bugfixes on 0.1.0.x:
25983 - Refuse server descriptors if the fingerprint line doesn't match
25984 the included identity key. Tor doesn't care, but other apps (and
25985 humans) might actually be trusting the fingerprint line.
25986 - We used to kill the circuit when we receive a relay command we
25987 don't recognize. Now we just drop it.
25988 - Start obeying our firewall options more rigorously:
25989 . If we can't get to a dirserver directly, try going via Tor.
25990 . Don't ever try to connect (as a client) to a place our
25991 firewall options forbid.
25992 . If we specify a proxy and also firewall options, obey the
25993 firewall options even when we're using the proxy: some proxies
25994 can only proxy to certain destinations.
25995 - Fix a bug found by Lasse Overlier: when we were making internal
25996 circuits (intended to be cannibalized later for rendezvous and
25997 introduction circuits), we were picking them so that they had
25998 useful exit nodes. There was no need for this, and it actually
25999 aids some statistical attacks.
26000 - Start treating internal circuits and exit circuits separately.
26001 It's important to keep them separate because internal circuits
26002 have their last hops picked like middle hops, rather than like
26003 exit hops. So exiting on them will break the user's expectations.
26005 o Bugfixes on 0.1.1.x:
26006 - Take out the mis-feature where we tried to detect IP address
26007 flapping for people with DynDNS, and chose not to upload a new
26008 server descriptor sometimes.
26009 - Try to be compatible with OpenSSL 0.9.6 again.
26010 - Log fix: when the controller is logging about .onion addresses,
26011 sometimes it didn't include the ".onion" part of the address.
26012 - Don't try to modify options->DirServers internally -- if the
26013 user didn't specify any, just add the default ones directly to
26014 the trusted dirserver list. This fixes a bug where people running
26015 controllers would use SETCONF on some totally unrelated config
26016 option, and Tor would start yelling at them about changing their
26018 - Let the controller's redirectstream command specify a port, in
26019 case the controller wants to change that too.
26020 - When we requested a pile of server descriptors, we sometimes
26021 accidentally launched a duplicate request for the first one.
26022 - Bugfix for trackhostexits: write down the fingerprint of the
26023 chosen exit, not its nickname, because the chosen exit might not
26025 - When parsing foo.exit, if foo is unknown, and we are leaving
26026 circuits unattached, set the chosen_exit field and leave the
26027 address empty. This matters because controllers got confused
26029 - Directory authorities no longer try to download server
26030 descriptors that they know they will reject.
26032 o Features and updates:
26033 - Replace balanced trees with hash tables: this should make stuff
26034 significantly faster.
26035 - Resume using the AES counter-mode implementation that we ship,
26036 rather than OpenSSL's. Ours is significantly faster.
26037 - Many other CPU and memory improvements.
26038 - Add a new config option FastFirstHopPK (on by default) so clients
26039 do a trivial crypto handshake for their first hop, since TLS has
26040 already taken care of confidentiality and authentication.
26041 - Add a new config option TestSocks so people can see if their
26042 applications are using socks4, socks4a, socks5-with-ip, or
26043 socks5-with-hostname. This way they don't have to keep mucking
26044 with tcpdump and wondering if something got cached somewhere.
26045 - Warn when listening on a public address for socks. I suspect a
26046 lot of people are setting themselves up as open socks proxies,
26047 and they have no idea that jerks on the Internet are using them,
26048 since they simply proxy the traffic into the Tor network.
26049 - Add "private:*" as an alias in configuration for policies. Now
26050 you can simplify your exit policy rather than needing to list
26051 every single internal or nonroutable network space.
26052 - Add a new controller event type that allows controllers to get
26053 all server descriptors that were uploaded to a router in its role
26054 as authoritative dirserver.
26055 - Start shipping socks-extensions.txt, tor-doc-unix.html,
26056 tor-doc-server.html, and stylesheet.css in the tarball.
26057 - Stop shipping tor-doc.html in the tarball.
26060 Changes in version 0.1.1.9-alpha - 2005-11-15
26061 o Usability improvements:
26062 - Start calling it FooListenAddress rather than FooBindAddress,
26063 since few of our users know what it means to bind an address
26065 - Reduce clutter in server logs. We're going to try to make
26066 them actually usable now. New config option ProtocolWarnings that
26067 lets you hear about how _other Tors_ are breaking the protocol. Off
26069 - Divide log messages into logging domains. Once we put some sort
26070 of interface on this, it will let people looking at more verbose
26071 log levels specify the topics they want to hear more about.
26072 - Make directory servers return better http 404 error messages
26073 instead of a generic "Servers unavailable".
26074 - Check for even more Windows version flags when writing the platform
26075 string in server descriptors, and note any we don't recognize.
26076 - Clean up more of the OpenSSL memory when exiting, so we can detect
26077 memory leaks better.
26078 - Make directory authorities be non-versioning, non-naming by
26079 default. Now we can add new directory servers without requiring
26080 their operators to pay close attention.
26081 - When logging via syslog, include the pid whenever we provide
26082 a log entry. Suggested by Todd Fries.
26084 o Performance improvements:
26085 - Directory servers now silently throw away new descriptors that
26086 haven't changed much if the timestamps are similar. We do this to
26087 tolerate older Tor servers that upload a new descriptor every 15
26088 minutes. (It seemed like a good idea at the time.)
26089 - Inline bottleneck smartlist functions; use fast versions by default.
26090 - Add a "Map from digest to void*" abstraction digestmap_t so we
26091 can do less hex encoding/decoding. Use it in router_get_by_digest()
26092 to resolve a performance bottleneck.
26093 - Allow tor_gzip_uncompress to extract as much as possible from
26094 truncated compressed data. Try to extract as many
26095 descriptors as possible from truncated http responses (when
26096 DIR_PURPOSE_FETCH_ROUTERDESC).
26097 - Make circ->onionskin a pointer, not a static array. moria2 was using
26098 125000 circuit_t's after it had been up for a few weeks, which
26099 translates to 20+ megs of wasted space.
26100 - The private half of our EDH handshake keys are now chosen out
26101 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
26103 o Security improvements:
26104 - Start making directory caches retain old routerinfos, so soon
26105 clients can start asking by digest of descriptor rather than by
26106 fingerprint of server.
26107 - Add half our entropy from RAND_poll in OpenSSL. This knows how
26108 to use egd (if present), openbsd weirdness (if present), vms/os2
26109 weirdness (if we ever port there), and more in the future.
26111 o Bugfixes on 0.1.0.x:
26112 - Do round-robin writes of at most 16 kB per write. This might be
26113 more fair on loaded Tor servers, and it might resolve our Windows
26114 crash bug. It might also slow things down.
26115 - Our TLS handshakes were generating a single public/private
26116 keypair for the TLS context, rather than making a new one for
26117 each new connections. Oops. (But we were still rotating them
26118 periodically, so it's not so bad.)
26119 - When we were cannibalizing a circuit with a particular exit
26120 node in mind, we weren't checking to see if that exit node was
26121 already present earlier in the circuit. Oops.
26122 - When a Tor server's IP changes (e.g. from a dyndns address),
26123 upload a new descriptor so clients will learn too.
26124 - Really busy servers were keeping enough circuits open on stable
26125 connections that they were wrapping around the circuit_id
26126 space. (It's only two bytes.) This exposed a bug where we would
26127 feel free to reuse a circuit_id even if it still exists but has
26128 been marked for close. Try to fix this bug. Some bug remains.
26129 - If we would close a stream early (e.g. it asks for a .exit that
26130 we know would refuse it) but the LeaveStreamsUnattached config
26131 option is set by the controller, then don't close it.
26133 o Bugfixes on 0.1.1.8-alpha:
26134 - Fix a big pile of memory leaks, some of them serious.
26135 - Do not try to download a routerdesc if we would immediately reject
26137 - Resume inserting a newline between all router descriptors when
26138 generating (old style) signed directories, since our spec says
26140 - When providing content-type application/octet-stream for
26141 server descriptors using .z, we were leaving out the
26142 content-encoding header. Oops. (Everything tolerated this just
26143 fine, but that doesn't mean we need to be part of the problem.)
26144 - Fix a potential seg fault in getconf and getinfo using version 1
26145 of the controller protocol.
26146 - Avoid crash: do not check whether DirPort is reachable when we
26147 are suppressing it because of hibernation.
26148 - Make --hash-password not crash on exit.
26151 Changes in version 0.1.1.8-alpha - 2005-10-07
26152 o New features (major):
26153 - Clients don't download or use the directory anymore. Now they
26154 download and use network-statuses from the trusted dirservers,
26155 and fetch individual server descriptors as needed from mirrors.
26156 See dir-spec.txt for all the gory details.
26157 - Be more conservative about whether to advertise our DirPort.
26158 The main change is to not advertise if we're running at capacity
26159 and either a) we could hibernate or b) our capacity is low and
26160 we're using a default DirPort.
26161 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
26163 o New features (minor):
26164 - Try to be smart about when to retry network-status and
26165 server-descriptor fetches. Still needs some tuning.
26166 - Stop parsing, storing, or using running-routers output (but
26167 mirrors still cache and serve it).
26168 - Consider a threshold of versioning dirservers (dirservers who have
26169 an opinion about which Tor versions are still recommended) before
26170 deciding whether to warn the user that he's obsolete.
26171 - Dirservers can now reject/invalidate by key and IP, with the
26172 config options "AuthDirInvalid" and "AuthDirReject". This is
26173 useful since currently we automatically list servers as running
26174 and usable even if we know they're jerks.
26175 - Provide dire warnings to any users who set DirServer; move it out
26176 of torrc.sample and into torrc.complete.
26177 - Add MyFamily to torrc.sample in the server section.
26178 - Add nicknames to the DirServer line, so we can refer to them
26179 without requiring all our users to memorize their IP addresses.
26180 - When we get an EOF or a timeout on a directory connection, note
26181 how many bytes of serverdesc we are dropping. This will help
26182 us determine whether it is smart to parse incomplete serverdesc
26184 - Add a new function to "change pseudonyms" -- that is, to stop
26185 using any currently-dirty circuits for new streams, so we don't
26186 link new actions to old actions. Currently it's only called on
26187 HUP (or SIGNAL RELOAD).
26188 - On sighup, if UseHelperNodes changed to 1, use new circuits.
26189 - Start using RAND_bytes rather than RAND_pseudo_bytes from
26190 OpenSSL. Also, reseed our entropy every hour, not just at
26191 startup. And entropy in 512-bit chunks, not 160-bit chunks.
26193 o Fixes on 0.1.1.7-alpha:
26194 - Nobody ever implemented EVENT_ADDRMAP for control protocol
26195 version 0, so don't let version 0 controllers ask for it.
26196 - If you requested something with too many newlines via the
26197 v1 controller protocol, you could crash tor.
26198 - Fix a number of memory leaks, including some pretty serious ones.
26199 - Re-enable DirPort testing again, so Tor servers will be willing
26200 to advertise their DirPort if it's reachable.
26201 - On TLS handshake, only check the other router's nickname against
26202 its expected nickname if is_named is set.
26204 o Fixes forward-ported from 0.1.0.15:
26205 - Don't crash when we don't have any spare file descriptors and we
26206 try to spawn a dns or cpu worker.
26207 - Make the numbers in read-history and write-history into uint64s,
26208 so they don't overflow and publish negatives in the descriptor.
26210 o Fixes on 0.1.0.x:
26211 - For the OS X package's modified privoxy config file, comment
26212 out the "logfile" line so we don't log everything passed
26214 - We were whining about using socks4 or socks5-with-local-lookup
26215 even when it's an IP in the "virtual" range we designed exactly
26217 - We were leaking some memory every time the client changes IPs.
26218 - Never call free() on tor_malloc()d memory. This will help us
26219 use dmalloc to detect memory leaks.
26220 - Check for named servers when looking them up by nickname;
26221 warn when we'recalling a non-named server by its nickname;
26222 don't warn twice about the same name.
26223 - Try to list MyFamily elements by key, not by nickname, and warn
26224 if we've not heard of the server.
26225 - Make windows platform detection (uname equivalent) smarter.
26226 - It turns out sparc64 doesn't like unaligned access either.
26229 Changes in version 0.1.0.15 - 2005-09-23
26230 o Bugfixes on 0.1.0.x:
26231 - Reject ports 465 and 587 (spam targets) in default exit policy.
26232 - Don't crash when we don't have any spare file descriptors and we
26233 try to spawn a dns or cpu worker.
26234 - Get rid of IgnoreVersion undocumented config option, and make us
26235 only warn, never exit, when we're running an obsolete version.
26236 - Don't try to print a null string when your server finds itself to
26237 be unreachable and the Address config option is empty.
26238 - Make the numbers in read-history and write-history into uint64s,
26239 so they don't overflow and publish negatives in the descriptor.
26240 - Fix a minor memory leak in smartlist_string_remove().
26241 - We were only allowing ourselves to upload a server descriptor at
26242 most every 20 minutes, even if it changed earlier than that.
26243 - Clean up log entries that pointed to old URLs.
26246 Changes in version 0.1.1.7-alpha - 2005-09-14
26247 o Fixes on 0.1.1.6-alpha:
26248 - Exit servers were crashing when people asked them to make a
26249 connection to an address not in their exit policy.
26250 - Looking up a non-existent stream for a v1 control connection would
26252 - Fix a seg fault if we ask a dirserver for a descriptor by
26253 fingerprint but he doesn't know about him.
26254 - SETCONF was appending items to linelists, not clearing them.
26255 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
26256 out and refuse the setconf if it would fail.
26257 - Downgrade the dirserver log messages when whining about
26261 - Add Peter Palfrader's check-tor script to tor/contrib/
26262 It lets you easily check whether a given server (referenced by
26263 nickname) is reachable by you.
26264 - Numerous changes to move towards client-side v2 directories. Not
26267 o Fixes on 0.1.0.x:
26268 - If the user gave tor an odd number of command-line arguments,
26269 we were silently ignoring the last one. Now we complain and fail.
26270 [This wins the oldest-bug prize -- this bug has been present since
26271 November 2002, as released in Tor 0.0.0.]
26272 - Do not use unaligned memory access on alpha, mips, or mipsel.
26273 It *works*, but is very slow, so we treat them as if it doesn't.
26274 - Retry directory requests if we fail to get an answer we like
26275 from a given dirserver (we were retrying before, but only if
26276 we fail to connect).
26277 - When writing the RecommendedVersions line, sort them first.
26278 - When the client asked for a rendezvous port that the hidden
26279 service didn't want to provide, we were sending an IP address
26280 back along with the end cell. Fortunately, it was zero. But stop
26282 - Correct "your server is reachable" log entries to indicate that
26283 it was self-testing that told us so.
26286 Changes in version 0.1.1.6-alpha - 2005-09-09
26287 o Fixes on 0.1.1.5-alpha:
26288 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
26289 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
26290 - Fix bug with tor_memmem finding a match at the end of the string.
26291 - Make unit tests run without segfaulting.
26292 - Resolve some solaris x86 compile warnings.
26293 - Handle duplicate lines in approved-routers files without warning.
26294 - Fix bug where as soon as a server refused any requests due to his
26295 exit policy (e.g. when we ask for localhost and he tells us that's
26296 127.0.0.1 and he won't do it), we decided he wasn't obeying his
26297 exit policy using him for any exits.
26298 - Only do openssl hardware accelerator stuff if openssl version is
26301 o New controller features/fixes:
26302 - Add a "RESETCONF" command so you can set config options like
26303 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
26304 a config option in the torrc with no value, then it clears it
26305 entirely (rather than setting it to its default).
26306 - Add a "GETINFO config-file" to tell us where torrc is.
26307 - Avoid sending blank lines when GETINFO replies should be empty.
26308 - Add a QUIT command for the controller (for using it manually).
26309 - Fix a bug in SAVECONF that was adding default dirservers and
26310 other redundant entries to the torrc file.
26312 o Start on the new directory design:
26313 - Generate, publish, cache, serve new network-status format.
26314 - Publish individual descriptors (by fingerprint, by "all", and by
26316 - Publish client and server recommended versions separately.
26317 - Allow tor_gzip_uncompress() to handle multiple concatenated
26318 compressed strings. Serve compressed groups of router
26319 descriptors. The compression logic here could be more
26321 - Distinguish v1 authorities (all currently trusted directories)
26322 from v2 authorities (all trusted directories).
26323 - Change DirServers config line to note which dirs are v1 authorities.
26324 - Add configuration option "V1AuthoritativeDirectory 1" which
26325 moria1, moria2, and tor26 should set.
26326 - Remove option when getting directory cache to see whether they
26327 support running-routers; they all do now. Replace it with one
26328 to see whether caches support v2 stuff.
26331 - Dirservers now do their own external reachability testing of each
26332 Tor server, and only list them as running if they've been found to
26333 be reachable. We also send back warnings to the server's logs if
26334 it uploads a descriptor that we already believe is unreachable.
26335 - Implement exit enclaves: if we know an IP address for the
26336 destination, and there's a running Tor server at that address
26337 which allows exit to the destination, then extend the circuit to
26338 that exit first. This provides end-to-end encryption and end-to-end
26339 authentication. Also, if the user wants a .exit address or enclave,
26340 use 4 hops rather than 3, and cannibalize a general circ for it
26342 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
26343 controller. Also, rotate dns and cpu workers if the controller
26344 changes options that will affect them; and initialize the dns
26345 worker cache tree whether or not we start out as a server.
26346 - Only upload a new server descriptor when options change, 18
26347 hours have passed, uptime is reset, or bandwidth changes a lot.
26348 - Check [X-]Forwarded-For headers in HTTP requests when generating
26349 log messages. This lets people run dirservers (and caches) behind
26350 Apache but still know which IP addresses are causing warnings.
26352 o Config option changes:
26353 - Replace (Fascist)Firewall* config options with a new
26354 ReachableAddresses option that understands address policies.
26355 For example, "ReachableAddresses *:80,*:443"
26356 - Get rid of IgnoreVersion undocumented config option, and make us
26357 only warn, never exit, when we're running an obsolete version.
26358 - Make MonthlyAccountingStart config option truly obsolete now.
26360 o Fixes on 0.1.0.x:
26361 - Reject ports 465 and 587 in the default exit policy, since
26362 people have started using them for spam too.
26363 - It turns out we couldn't bootstrap a network since we added
26364 reachability detection in 0.1.0.1-rc. Good thing the Tor network
26365 has never gone down. Add an AssumeReachable config option to let
26366 servers and dirservers bootstrap. When we're trying to build a
26367 high-uptime or high-bandwidth circuit but there aren't enough
26368 suitable servers, try being less picky rather than simply failing.
26369 - Our logic to decide if the OR we connected to was the right guy
26370 was brittle and maybe open to a mitm for unverified routers.
26371 - We weren't cannibalizing circuits correctly for
26372 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
26373 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
26374 build those from scratch. This should make hidden services faster.
26375 - Predict required circuits better, with an eye toward making hidden
26376 services faster on the service end.
26377 - Retry streams if the exit node sends back a 'misc' failure. This
26378 should result in fewer random failures. Also, after failing
26379 from resolve failed or misc, reset the num failures, so we give
26380 it a fair shake next time we try.
26381 - Clean up the rendezvous warn log msgs, and downgrade some to info.
26382 - Reduce severity on logs about dns worker spawning and culling.
26383 - When we're shutting down and we do something like try to post a
26384 server descriptor or rendezvous descriptor, don't complain that
26385 we seem to be unreachable. Of course we are, we're shutting down.
26386 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
26387 We don't use them yet, but maybe one day our DNS resolver will be
26388 able to discover them.
26389 - Make ContactInfo mandatory for authoritative directory servers.
26390 - Require server descriptors to list IPv4 addresses -- hostnames
26391 are no longer allowed. This also fixes some potential security
26392 problems with people providing hostnames as their address and then
26393 preferentially resolving them to partition users.
26394 - Change log line for unreachability to explicitly suggest /etc/hosts
26395 as the culprit. Also make it clearer what IP address and ports we're
26396 testing for reachability.
26397 - Put quotes around user-supplied strings when logging so users are
26398 more likely to realize if they add bad characters (like quotes)
26400 - Let auth dir servers start without specifying an Address config
26402 - Make unit tests (and other invocations that aren't the real Tor)
26403 run without launching listeners, creating subdirectories, and so on.
26406 Changes in version 0.1.1.5-alpha - 2005-08-08
26407 o Bugfixes included in 0.1.0.14.
26409 o Bugfixes on 0.1.0.x:
26410 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
26411 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
26412 it would silently using ignore the 6668.
26415 Changes in version 0.1.0.14 - 2005-08-08
26416 o Bugfixes on 0.1.0.x:
26417 - Fix the other half of the bug with crypto handshakes
26419 - Fix an assert trigger if you send a 'signal term' via the
26420 controller when it's listening for 'event info' messages.
26423 Changes in version 0.1.1.4-alpha - 2005-08-04
26424 o Bugfixes included in 0.1.0.13.
26427 - Improve tor_gettimeofday() granularity on windows.
26428 - Make clients regenerate their keys when their IP address changes.
26429 - Implement some more GETINFO goodness: expose helper nodes, config
26430 options, getinfo keys.
26433 Changes in version 0.1.0.13 - 2005-08-04
26434 o Bugfixes on 0.1.0.x:
26435 - Fix a critical bug in the security of our crypto handshakes.
26436 - Fix a size_t underflow in smartlist_join_strings2() that made
26437 it do bad things when you hand it an empty smartlist.
26438 - Fix Windows installer to ship Tor license (thanks to Aphex for
26439 pointing out this oversight) and put a link to the doc directory
26441 - Explicitly set no-unaligned-access for sparc: it turns out the
26442 new gcc's let you compile broken code, but that doesn't make it
26446 Changes in version 0.1.1.3-alpha - 2005-07-23
26447 o Bugfixes on 0.1.1.2-alpha:
26448 - Fix a bug in handling the controller's "post descriptor"
26450 - Fix several bugs in handling the controller's "extend circuit"
26452 - Fix a bug in handling the controller's "stream status" event.
26453 - Fix an assert failure if we have a controller listening for
26454 circuit events and we go offline.
26455 - Re-allow hidden service descriptors to publish 0 intro points.
26456 - Fix a crash when generating your hidden service descriptor if
26457 you don't have enough intro points already.
26459 o New features on 0.1.1.2-alpha:
26460 - New controller function "getinfo accounting", to ask how
26461 many bytes we've used in this time period.
26462 - Experimental support for helper nodes: a lot of the risk from
26463 a small static adversary comes because users pick new random
26464 nodes every time they rebuild a circuit. Now users will try to
26465 stick to the same small set of entry nodes if they can. Not
26466 enabled by default yet.
26468 o Bugfixes on 0.1.0.12:
26469 - If you're an auth dir server, always publish your dirport,
26470 even if you haven't yet found yourself to be reachable.
26471 - Fix a size_t underflow in smartlist_join_strings2() that made
26472 it do bad things when you hand it an empty smartlist.
26475 Changes in version 0.1.0.12 - 2005-07-18
26476 o New directory servers:
26477 - tor26 has changed IP address.
26479 o Bugfixes on 0.1.0.x:
26480 - Fix a possible double-free in tor_gzip_uncompress().
26481 - When --disable-threads is set, do not search for or link against
26482 pthreads libraries.
26483 - Don't trigger an assert if an authoritative directory server
26484 claims its dirport is 0.
26485 - Fix bug with removing Tor as an NT service: some people were
26486 getting "The service did not return an error." Thanks to Matt
26490 Changes in version 0.1.1.2-alpha - 2005-07-15
26491 o New directory servers:
26492 - tor26 has changed IP address.
26494 o Bugfixes on 0.1.0.x, crashes/leaks:
26495 - Port the servers-not-obeying-their-exit-policies fix from
26497 - Fix an fd leak in start_daemon().
26498 - On Windows, you can't always reopen a port right after you've
26499 closed it. So change retry_listeners() to only close and re-open
26500 ports that have changed.
26501 - Fix a possible double-free in tor_gzip_uncompress().
26503 o Bugfixes on 0.1.0.x, usability:
26504 - When tor_socketpair() fails in Windows, give a reasonable
26505 Windows-style errno back.
26506 - Let people type "tor --install" as well as "tor -install" when
26508 want to make it an NT service.
26509 - NT service patch from Matt Edman to improve error messages.
26510 - When the controller asks for a config option with an abbreviated
26511 name, give the full name in our response.
26512 - Correct the man page entry on TrackHostExitsExpire.
26513 - Looks like we were never delivering deflated (i.e. compressed)
26514 running-routers lists, even when asked. Oops.
26515 - When --disable-threads is set, do not search for or link against
26516 pthreads libraries.
26518 o Bugfixes on 0.1.1.x:
26519 - Fix a seg fault with autodetecting which controller version is
26523 - New hidden service descriptor format: put a version in it, and
26524 let people specify introduction/rendezvous points that aren't
26525 in "the directory" (which is subjective anyway).
26526 - Allow the DEBUG controller event to work again. Mark certain log
26527 entries as "don't tell this to controllers", so we avoid cycles.
26530 Changes in version 0.1.0.11 - 2005-06-30
26531 o Bugfixes on 0.1.0.x:
26532 - Fix major security bug: servers were disregarding their
26533 exit policies if clients behaved unexpectedly.
26534 - Make OS X init script check for missing argument, so we don't
26535 confuse users who invoke it incorrectly.
26536 - Fix a seg fault in "tor --hash-password foo".
26537 - The MAPADDRESS control command was broken.
26540 Changes in version 0.1.1.1-alpha - 2005-06-29
26542 - Make OS X init script check for missing argument, so we don't
26543 confuse users who invoke it incorrectly.
26544 - Fix a seg fault in "tor --hash-password foo".
26545 - Fix a possible way to DoS dirservers.
26546 - When we complain that your exit policy implicitly allows local or
26547 private address spaces, name them explicitly so operators can
26549 - Make the log message less scary when all the dirservers are
26550 temporarily unreachable.
26551 - We were printing the number of idle dns workers incorrectly when
26555 - Revised controller protocol (version 1) that uses ascii rather
26556 than binary. Add supporting libraries in python and java so you
26557 can use the controller from your applications without caring how
26558 our protocol works.
26559 - Spiffy new support for crypto hardware accelerators. Can somebody
26563 Changes in version 0.0.9.10 - 2005-06-16
26564 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
26565 - Refuse relay cells that claim to have a length larger than the
26566 maximum allowed. This prevents a potential attack that could read
26567 arbitrary memory (e.g. keys) from an exit server's process
26571 Changes in version 0.1.0.10 - 2005-06-14
26572 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
26573 libevent before 1.1a.
26576 Changes in version 0.1.0.9-rc - 2005-06-09
26578 - Reset buf->highwater every time buf_shrink() is called, not just on
26579 a successful shrink. This was causing significant memory bloat.
26580 - Fix buffer overflow when checking hashed passwords.
26581 - Security fix: if seeding the RNG on Win32 fails, quit.
26582 - Allow seeding the RNG on Win32 even when you're not running as
26584 - Disable threading on Solaris too. Something is wonky with it,
26585 cpuworkers, and reentrant libs.
26586 - Reenable the part of the code that tries to flush as soon as an
26587 OR outbuf has a full TLS record available. Perhaps this will make
26588 OR outbufs not grow as huge except in rare cases, thus saving lots
26589 of CPU time plus memory.
26590 - Reject malformed .onion addresses rather then passing them on as
26591 normal web requests.
26592 - Adapt patch from Adam Langley: fix possible memory leak in
26593 tor_lookup_hostname().
26594 - Initialize libevent later in the startup process, so the logs are
26595 already established by the time we start logging libevent warns.
26596 - Use correct errno on win32 if libevent fails.
26597 - Check and warn about known-bad/slow libevent versions.
26598 - Pay more attention to the ClientOnly config option.
26599 - Have torctl.in/tor.sh.in check for location of su binary (needed
26601 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
26602 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
26603 HttpProxyAuthenticator
26604 - Stop warning about sigpipes in the logs. We're going to
26605 pretend that getting these occasionally is normal and fine.
26606 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
26608 installer screens; and don't put stuff into StartupItems unless
26609 the user asks you to.
26610 - Require servers that use the default dirservers to have public IP
26611 addresses. We have too many servers that are configured with private
26612 IPs and their admins never notice the log entries complaining that
26613 their descriptors are being rejected.
26614 - Add OSX uninstall instructions. An actual uninstall script will
26618 Changes in version 0.1.0.8-rc - 2005-05-23
26620 - It turns out that kqueue on OS X 10.3.9 was causing kernel
26621 panics. Disable kqueue on all OS X Tors.
26622 - Fix RPM: remove duplicate line accidentally added to the rpm
26624 - Disable threads on openbsd too, since its gethostaddr is not
26626 - Tolerate libevent 0.8 since it still works, even though it's
26628 - Enable building on Red Hat 9.0 again.
26629 - Allow the middle hop of the testing circuit to be running any
26630 version, now that most of them have the bugfix to let them connect
26631 to unknown servers. This will allow reachability testing to work
26632 even when 0.0.9.7-0.0.9.9 become obsolete.
26633 - Handle relay cells with rh.length too large. This prevents
26634 a potential attack that could read arbitrary memory (maybe even
26635 keys) from the exit server's process.
26636 - We screwed up the dirport reachability testing when we don't yet
26637 have a cached version of the directory. Hopefully now fixed.
26638 - Clean up router_load_single_router() (used by the controller),
26639 so it doesn't seg fault on error.
26640 - Fix a minor memory leak when somebody establishes an introduction
26641 point at your Tor server.
26642 - If a socks connection ends because read fails, don't warn that
26643 you're not sending a socks reply back.
26646 - Add HttpProxyAuthenticator config option too, that works like
26647 the HttpsProxyAuthenticator config option.
26648 - Encode hashed controller passwords in hex instead of base64,
26649 to make it easier to write controllers.
26652 Changes in version 0.1.0.7-rc - 2005-05-17
26654 - Fix a bug in the OS X package installer that prevented it from
26655 installing on Tiger.
26656 - Fix a script bug in the OS X package installer that made it
26657 complain during installation.
26658 - Find libevent even if it's hiding in /usr/local/ and your
26659 CFLAGS and LDFLAGS don't tell you to look there.
26660 - Be able to link with libevent as a shared library (the default
26661 after 1.0d), even if it's hiding in /usr/local/lib and even
26662 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
26663 assuming you're running gcc. Otherwise fail and give a useful
26665 - Fix a bug in the RPM packager: set home directory for _tor to
26666 something more reasonable when first installing.
26667 - Free a minor amount of memory that is still reachable on exit.
26670 Changes in version 0.1.0.6-rc - 2005-05-14
26672 - Implement --disable-threads configure option. Disable threads on
26673 netbsd by default, because it appears to have no reentrant resolver
26675 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
26676 release (1.1) detects and disables kqueue if it's broken.
26677 - Append default exit policy before checking for implicit internal
26678 addresses. Now we don't log a bunch of complaints on startup
26679 when using the default exit policy.
26680 - Some people were putting "Address " in their torrc, and they had
26681 a buggy resolver that resolved " " to 0.0.0.0. Oops.
26682 - If DataDir is ~/.tor, and that expands to /.tor, then default to
26683 LOCALSTATEDIR/tor instead.
26684 - Fix fragmented-message bug in TorControl.py.
26685 - Resolve a minor bug which would prevent unreachable dirports
26686 from getting suppressed in the published descriptor.
26687 - When the controller gave us a new descriptor, we weren't resolving
26688 it immediately, so Tor would think its address was 0.0.0.0 until
26689 we fetched a new directory.
26690 - Fix an uppercase/lowercase case error in suppressing a bogus
26691 libevent warning on some Linuxes.
26694 - Begin scrubbing sensitive strings from logs by default. Turn off
26695 the config option SafeLogging if you need to do debugging.
26696 - Switch to a new buffer management algorithm, which tries to avoid
26697 reallocing and copying quite as much. In first tests it looks like
26698 it uses *more* memory on average, but less cpu.
26699 - First cut at support for "create-fast" cells. Clients can use
26700 these when extending to their first hop, since the TLS already
26701 provides forward secrecy and authentication. Not enabled on
26703 - When dirservers refuse a router descriptor, we now log its
26704 contactinfo, platform, and the poster's IP address.
26705 - Call tor_free_all instead of connections_free_all after forking, to
26706 save memory on systems that need to fork.
26707 - Whine at you if you're a server and you don't set your contactinfo.
26708 - Implement --verify-config command-line option to check if your torrc
26709 is valid without actually launching Tor.
26710 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
26711 rather than just rejecting it.
26714 Changes in version 0.1.0.5-rc - 2005-04-27
26716 - Stop trying to print a null pointer if an OR conn fails because
26717 we didn't like its cert.
26719 - Switch our internal buffers implementation to use a ring buffer,
26720 to hopefully improve performance for fast servers a lot.
26721 - Add HttpsProxyAuthenticator support (basic auth only), based
26722 on patch from Adam Langley.
26723 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
26724 the fast servers that have been joining lately.
26725 - Give hidden service accesses extra time on the first attempt,
26726 since 60 seconds is often only barely enough. This might improve
26728 - Improve performance for dirservers: stop re-parsing the whole
26729 directory every time you regenerate it.
26730 - Add more debugging info to help us find the weird dns freebsd
26731 pthreads bug; cleaner debug messages to help track future issues.
26734 Changes in version 0.0.9.9 - 2005-04-23
26735 o Bugfixes on 0.0.9.x:
26736 - If unofficial Tor clients connect and send weird TLS certs, our
26737 Tor server triggers an assert. This release contains a minimal
26738 backport from the broader fix that we put into 0.1.0.4-rc.
26741 Changes in version 0.1.0.4-rc - 2005-04-23
26743 - If unofficial Tor clients connect and send weird TLS certs, our
26744 Tor server triggers an assert. Stop asserting, and start handling
26745 TLS errors better in other situations too.
26746 - When the controller asks us to tell it about all the debug-level
26747 logs, it turns out we were generating debug-level logs while
26748 telling it about them, which turns into a bad loop. Now keep
26749 track of whether you're sending a debug log to the controller,
26750 and don't log when you are.
26751 - Fix the "postdescriptor" feature of the controller interface: on
26752 non-complete success, only say "done" once.
26754 - Clients are now willing to load balance over up to 2mB, not 1mB,
26755 of advertised bandwidth capacity.
26756 - Add a NoPublish config option, so you can be a server (e.g. for
26757 testing running Tor servers in other Tor networks) without
26758 publishing your descriptor to the primary dirservers.
26761 Changes in version 0.1.0.3-rc - 2005-04-08
26762 o Improvements on 0.1.0.2-rc:
26763 - Client now retries when streams end early for 'hibernating' or
26764 'resource limit' reasons, rather than failing them.
26765 - More automated handling for dirserver operators:
26766 - Automatically approve nodes running 0.1.0.2-rc or later,
26767 now that the the reachability detection stuff is working.
26768 - Now we allow two unverified servers with the same nickname
26769 but different keys. But if a nickname is verified, only that
26770 nickname+key are allowed.
26771 - If you're an authdirserver connecting to an address:port,
26772 and it's not the OR you were expecting, forget about that
26773 descriptor. If he *was* the one you were expecting, then forget
26774 about all other descriptors for that address:port.
26775 - Allow servers to publish descriptors from 12 hours in the future.
26776 Corollary: only whine about clock skew from the dirserver if
26777 he's a trusted dirserver (since now even verified servers could
26778 have quite wrong clocks).
26779 - Adjust maximum skew and age for rendezvous descriptors: let skew
26780 be 48 hours rather than 90 minutes.
26781 - Efficiency improvements:
26782 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
26783 it much faster to look up a circuit for each relay cell.
26784 - Remove most calls to assert_all_pending_dns_resolves_ok(),
26785 since they're eating our cpu on exit nodes.
26786 - Stop wasting time doing a case insensitive comparison for every
26787 dns name every time we do any lookup. Canonicalize the names to
26788 lowercase and be done with it.
26789 - Start sending 'truncated' cells back rather than destroy cells,
26790 if the circuit closes in front of you. This means we won't have
26791 to abandon partially built circuits.
26792 - Only warn once per nickname from add_nickname_list_to_smartlist
26793 per failure, so an entrynode or exitnode choice that's down won't
26795 - Put a note in the torrc about abuse potential with the default
26797 - Revise control spec and implementation to allow all log messages to
26798 be sent to controller with their severities intact (suggested by
26799 Matt Edman). Update TorControl to handle new log event types.
26800 - Provide better explanation messages when controller's POSTDESCRIPTOR
26802 - Stop putting nodename in the Platform string in server descriptors.
26803 It doesn't actually help, and it is confusing/upsetting some people.
26805 o Bugfixes on 0.1.0.2-rc:
26806 - We were printing the host mask wrong in exit policies in server
26807 descriptors. This isn't a critical bug though, since we were still
26808 obeying the exit policy internally.
26809 - Fix Tor when compiled with libevent but without pthreads: move
26810 connection_unregister() from _connection_free() to
26812 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
26813 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
26814 when we look through the connection array, we'll find any of the
26815 cpu/dnsworkers. This is no good.
26817 o Bugfixes on 0.0.9.8:
26818 - Fix possible bug on threading platforms (e.g. win32) which was
26819 leaking a file descriptor whenever a cpuworker or dnsworker died.
26820 - When using preferred entry or exit nodes, ignore whether the
26821 circuit wants uptime or capacity. They asked for the nodes, they
26823 - chdir() to your datadirectory at the *end* of the daemonize process,
26824 not the beginning. This was a problem because the first time you
26825 run tor, if your datadir isn't there, and you have runasdaemon set
26826 to 1, it will try to chdir to it before it tries to create it. Oops.
26827 - Handle changed router status correctly when dirserver reloads
26828 fingerprint file. We used to be dropping all unverified descriptors
26829 right then. The bug was hidden because we would immediately
26830 fetch a directory from another dirserver, which would include the
26831 descriptors we just dropped.
26832 - When we're connecting to an OR and he's got a different nickname/key
26833 than we were expecting, only complain loudly if we're an OP or a
26834 dirserver. Complaining loudly to the OR admins just confuses them.
26835 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
26836 artificially capped at 500kB.
26839 Changes in version 0.0.9.8 - 2005-04-07
26840 o Bugfixes on 0.0.9.x:
26841 - We have a bug that I haven't found yet. Sometimes, very rarely,
26842 cpuworkers get stuck in the 'busy' state, even though the cpuworker
26843 thinks of itself as idle. This meant that no new circuits ever got
26844 established. Here's a workaround to kill any cpuworker that's been
26845 busy for more than 100 seconds.
26848 Changes in version 0.1.0.2-rc - 2005-04-01
26849 o Bugfixes on 0.1.0.1-rc:
26850 - Fixes on reachability detection:
26851 - Don't check for reachability while hibernating.
26852 - If ORPort is reachable but DirPort isn't, still publish the
26853 descriptor, but zero out DirPort until it's found reachable.
26854 - When building testing circs for ORPort testing, use only
26855 high-bandwidth nodes, so fewer circuits fail.
26856 - Complain about unreachable ORPort separately from unreachable
26857 DirPort, so the user knows what's going on.
26858 - Make sure we only conclude ORPort reachability if we didn't
26859 initiate the conn. Otherwise we could falsely conclude that
26860 we're reachable just because we connected to the guy earlier
26861 and he used that same pipe to extend to us.
26862 - Authdirservers shouldn't do ORPort reachability detection,
26863 since they're in clique mode, so it will be rare to find a
26864 server not already connected to them.
26865 - When building testing circuits, always pick middle hops running
26866 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
26867 bug. (This is a kludge; it will go away when 0.0.9.x becomes
26869 - When we decide we're reachable, actually publish our descriptor
26871 - Fix bug in redirectstream in the controller.
26872 - Fix the state descriptor strings so logs don't claim edge streams
26873 are in a different state than they actually are.
26874 - Use recent libevent features when possible (this only really affects
26875 win32 and osx right now, because the new libevent with these
26876 features hasn't been released yet). Add code to suppress spurious
26878 - Prevent possible segfault in connection_close_unattached_ap().
26879 - Fix newlines on torrc in win32.
26880 - Improve error msgs when tor-resolve fails.
26882 o Improvements on 0.0.9.x:
26883 - New experimental script tor/contrib/ExerciseServer.py (needs more
26884 work) that uses the controller interface to build circuits and
26885 fetch pages over them. This will help us bootstrap servers that
26886 have lots of capacity but haven't noticed it yet.
26887 - New experimental script tor/contrib/PathDemo.py (needs more work)
26888 that uses the controller interface to let you choose whole paths
26890 "<hostname>.<path,separated by dots>.<length of path>.path"
26891 - When we've connected to an OR and handshaked but didn't like
26892 the result, we were closing the conn without sending destroy
26893 cells back for pending circuits. Now send those destroys.
26896 Changes in version 0.0.9.7 - 2005-04-01
26897 o Bugfixes on 0.0.9.x:
26898 - Fix another race crash bug (thanks to Glenn Fink for reporting).
26899 - Compare identity to identity, not to nickname, when extending to
26900 a router not already in the directory. This was preventing us from
26901 extending to unknown routers. Oops.
26902 - Make sure to create OS X Tor user in <500 range, so we aren't
26903 creating actual system users.
26904 - Note where connection-that-hasn't-sent-end was marked, and fix
26905 a few really loud instances of this harmless bug (it's fixed more
26909 Changes in version 0.1.0.1-rc - 2005-03-28
26911 - Add reachability testing. Your Tor server will automatically try
26912 to see if its ORPort and DirPort are reachable from the outside,
26913 and it won't upload its descriptor until it decides they are.
26914 - Handle unavailable hidden services better. Handle slow or busy
26915 hidden services better.
26916 - Add support for CONNECTing through https proxies, with "HttpsProxy"
26918 - New exit policy: accept most low-numbered ports, rather than
26919 rejecting most low-numbered ports.
26920 - More Tor controller support (still experimental). See
26921 http://tor.eff.org/doc/control-spec.txt for all the new features,
26922 including signals to emulate unix signals from any platform;
26923 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
26924 closestream; closecircuit; etc.
26925 - Make nt services work and start on startup on win32 (based on
26926 patch by Matt Edman).
26927 - Add a new AddressMap config directive to rewrite incoming socks
26928 addresses. This lets you, for example, declare an implicit
26929 required exit node for certain sites.
26930 - Add a new TrackHostExits config directive to trigger addressmaps
26931 for certain incoming socks addresses -- for sites that break when
26932 your exit keeps changing (based on patch by Mike Perry).
26933 - Redo the client-side dns cache so it's just an addressmap too.
26934 - Notice when our IP changes, and reset stats/uptime/reachability.
26935 - When an application is using socks5, give him the whole variety of
26936 potential socks5 responses (connect refused, host unreachable, etc),
26937 rather than just "success" or "failure".
26938 - A more sane version numbering system. See
26939 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
26940 - New contributed script "exitlist": a simple python script to
26941 parse directories and find Tor nodes that exit to listed
26943 - New contributed script "privoxy-tor-toggle" to toggle whether
26944 Privoxy uses Tor. Seems to be configured for Debian by default.
26945 - Report HTTP reasons to client when getting a response from directory
26946 servers -- so you can actually know what went wrong.
26947 - New config option MaxAdvertisedBandwidth which lets you advertise
26948 a low bandwidthrate (to not attract as many circuits) while still
26949 allowing a higher bandwidthrate in reality.
26951 o Robustness/stability fixes:
26952 - Make Tor use Niels Provos's libevent instead of its current
26953 poll-but-sometimes-select mess. This will let us use faster async
26954 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
26956 - pthread support now too. This was forced because when we forked,
26957 we ended up wasting a lot of duplicate ram over time. Also switch
26958 to foo_r versions of some library calls to allow reentry and
26960 - Better handling for heterogeneous / unreliable nodes:
26961 - Annotate circuits w/ whether they aim to contain high uptime nodes
26962 and/or high capacity nodes. When building circuits, choose
26964 - This means that every single node in an intro rend circuit,
26965 not just the last one, will have a minimum uptime.
26966 - New config option LongLivedPorts to indicate application streams
26967 that will want high uptime circuits.
26968 - Servers reset uptime when a dir fetch entirely fails. This
26969 hopefully reflects stability of the server's network connectivity.
26970 - If somebody starts his tor server in Jan 2004 and then fixes his
26971 clock, don't make his published uptime be a year.
26972 - Reset published uptime when you wake up from hibernation.
26973 - Introduce a notion of 'internal' circs, which are chosen without
26974 regard to the exit policy of the last hop. Intro and rendezvous
26975 circs must be internal circs, to avoid leaking information. Resolve
26976 and connect streams can use internal circs if they want.
26977 - New circuit pooling algorithm: make sure to have enough circs around
26978 to satisfy any predicted ports, and also make sure to have 2 internal
26979 circs around if we've required internal circs lately (and with high
26980 uptime if we've seen that lately too).
26981 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
26982 which describes how often we retry making new circuits if current
26983 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
26984 how long we're willing to make use of an already-dirty circuit.
26985 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
26986 circ as necessary, if there are any completed ones lying around
26987 when we try to launch one.
26988 - Make hidden services try to establish a rendezvous for 30 seconds,
26989 rather than for n (where n=3) attempts to build a circuit.
26990 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
26991 "ShutdownWaitLength".
26992 - Try to be more zealous about calling connection_edge_end when
26993 things go bad with edge conns in connection.c.
26994 - Revise tor-spec to add more/better stream end reasons.
26995 - Revise all calls to connection_edge_end to avoid sending "misc",
26996 and to take errno into account where possible.
26999 - Fix a race condition that can trigger an assert, when we have a
27000 pending create cell and an OR connection fails right then.
27001 - Fix several double-mark-for-close bugs, e.g. where we were finding
27002 a conn for a cell even if that conn is already marked for close.
27003 - Make sequence of log messages when starting on win32 with no config
27004 file more reasonable.
27005 - When choosing an exit node for a new non-internal circ, don't take
27006 into account whether it'll be useful for any pending x.onion
27007 addresses -- it won't.
27008 - Turn addr_policy_compare from a tristate to a quadstate; this should
27009 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
27010 for google.com" problem.
27011 - Make "platform" string in descriptor more accurate for Win32 servers,
27012 so it's not just "unknown platform".
27013 - Fix an edge case in parsing config options (thanks weasel).
27014 If they say "--" on the commandline, it's not an option.
27015 - Reject odd-looking addresses at the client (e.g. addresses that
27016 contain a colon), rather than having the server drop them because
27018 - tor-resolve requests were ignoring .exit if there was a working circuit
27019 they could use instead.
27020 - REUSEADDR on normal platforms means you can rebind to the port
27021 right after somebody else has let it go. But REUSEADDR on win32
27022 means to let you bind to the port _even when somebody else
27023 already has it bound_! So, don't do that on Win32.
27024 - Change version parsing logic: a version is "obsolete" if it is not
27025 recommended and (1) there is a newer recommended version in the
27026 same series, or (2) there are no recommended versions in the same
27027 series, but there are some recommended versions in a newer series.
27028 A version is "new" if it is newer than any recommended version in
27030 - Stop most cases of hanging up on a socks connection without sending
27034 - Require BandwidthRate to be at least 20kB/s for servers.
27035 - When a dirserver causes you to give a warn, mention which dirserver
27037 - New config option DirAllowPrivateAddresses for authdirservers.
27038 Now by default they refuse router descriptors that have non-IP or
27039 private-IP addresses.
27040 - Stop publishing socksport in the directory, since it's not
27041 actually meant to be public. For compatibility, publish a 0 there
27043 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
27044 smart" value, that is low for servers and high for clients.
27045 - If our clock jumps forward by 100 seconds or more, assume something
27046 has gone wrong with our network and abandon all not-yet-used circs.
27047 - Warn when exit policy implicitly allows local addresses.
27048 - If we get an incredibly skewed timestamp from a dirserver mirror
27049 that isn't a verified OR, don't warn -- it's probably him that's
27051 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
27052 cookies to disk and doesn't log each web request to disk. (Thanks
27053 to Brett Carrington for pointing this out.)
27054 - When a client asks us for a dir mirror and we don't have one,
27055 launch an attempt to get a fresh one.
27056 - If we're hibernating and we get a SIGINT, exit immediately.
27057 - Add --with-dmalloc ./configure option, to track memory leaks.
27058 - And try to free all memory on closing, so we can detect what
27060 - Cache local dns resolves correctly even when they're .exit
27062 - Give a better warning when some other server advertises an
27063 ORPort that is actually an apache running ssl.
27064 - Add "opt hibernating 1" to server descriptor to make it clearer
27065 whether the server is hibernating.
27068 Changes in version 0.0.9.6 - 2005-03-24
27069 o Bugfixes on 0.0.9.x (crashes and asserts):
27070 - Add new end stream reasons to maintenance branch. Fix bug where
27071 reason (8) could trigger an assert. Prevent bug from recurring.
27072 - Apparently win32 stat wants paths to not end with a slash.
27073 - Fix assert triggers in assert_cpath_layer_ok(), where we were
27074 blowing away the circuit that conn->cpath_layer points to, then
27075 checking to see if the circ is well-formed. Backport check to make
27076 sure we dont use the cpath on a closed connection.
27077 - Prevent circuit_resume_edge_reading_helper() from trying to package
27078 inbufs for marked-for-close streams.
27079 - Don't crash on hup if your options->address has become unresolvable.
27080 - Some systems (like OS X) sometimes accept() a connection and tell
27081 you the remote host is 0.0.0.0:0. If this happens, due to some
27082 other mis-features, we get confused; so refuse the conn for now.
27084 o Bugfixes on 0.0.9.x (other):
27085 - Fix harmless but scary "Unrecognized content encoding" warn message.
27086 - Add new stream error reason: TORPROTOCOL reason means "you are not
27087 speaking a version of Tor I understand; say bye-bye to your stream."
27088 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
27089 into the future, now that we are more tolerant of skew. This
27090 resolves a bug where a Tor server would refuse to cache a directory
27091 because all the directories it gets are too far in the future;
27092 yet the Tor server never logs any complaints about clock skew.
27093 - Mac packaging magic: make man pages useable, and do not overwrite
27094 existing torrc files.
27095 - Make OS X log happily to /var/log/tor/tor.log
27098 Changes in version 0.0.9.5 - 2005-02-22
27099 o Bugfixes on 0.0.9.x:
27100 - Fix an assert race at exit nodes when resolve requests fail.
27101 - Stop picking unverified dir mirrors--it only leads to misery.
27102 - Patch from Matt Edman to make NT services work better. Service
27103 support is still not compiled into the executable by default.
27104 - Patch from Dmitri Bely so the Tor service runs better under
27105 the win32 SYSTEM account.
27106 - Make tor-resolve actually work (?) on Win32.
27107 - Fix a sign bug when getrlimit claims to have 4+ billion
27108 file descriptors available.
27109 - Stop refusing to start when bandwidthburst == bandwidthrate.
27110 - When create cells have been on the onion queue more than five
27111 seconds, just send back a destroy and take them off the list.
27114 Changes in version 0.0.9.4 - 2005-02-03
27115 o Bugfixes on 0.0.9:
27116 - Fix an assert bug that took down most of our servers: when
27117 a server claims to have 1 GB of bandwidthburst, don't
27119 - Don't crash as badly if we have spawned the max allowed number
27120 of dnsworkers, or we're out of file descriptors.
27121 - Block more file-sharing ports in the default exit policy.
27122 - MaxConn is now automatically set to the hard limit of max
27123 file descriptors we're allowed (ulimit -n), minus a few for
27125 - Give a clearer message when servers need to raise their
27126 ulimit -n when they start running out of file descriptors.
27127 - SGI Compatibility patches from Jan Schaumann.
27128 - Tolerate a corrupt cached directory better.
27129 - When a dirserver hasn't approved your server, list which one.
27130 - Go into soft hibernation after 95% of the bandwidth is used,
27131 not 99%. This is especially important for daily hibernators who
27132 have a small accounting max. Hopefully it will result in fewer
27133 cut connections when the hard hibernation starts.
27134 - Load-balance better when using servers that claim more than
27135 800kB/s of capacity.
27136 - Make NT services work (experimental, only used if compiled in).
27139 Changes in version 0.0.9.3 - 2005-01-21
27140 o Bugfixes on 0.0.9:
27141 - Backport the cpu use fixes from main branch, so busy servers won't
27142 need as much processor time.
27143 - Work better when we go offline and then come back, or when we
27144 run Tor at boot before the network is up. We do this by
27145 optimistically trying to fetch a new directory whenever an
27146 application request comes in and we think we're offline -- the
27147 human is hopefully a good measure of when the network is back.
27148 - Backport some minimal hidserv bugfixes: keep rend circuits open as
27149 long as you keep using them; actually publish hidserv descriptors
27150 shortly after they change, rather than waiting 20-40 minutes.
27151 - Enable Mac startup script by default.
27152 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
27153 - When you update AllowUnverifiedNodes or FirewallPorts via the
27154 controller's setconf feature, we were always appending, never
27156 - When you update HiddenServiceDir via setconf, it was screwing up
27157 the order of reading the lines, making it fail.
27158 - Do not rewrite a cached directory back to the cache; otherwise we
27159 will think it is recent and not fetch a newer one on startup.
27160 - Workaround for webservers that lie about Content-Encoding: Tor
27161 now tries to autodetect compressed directories and compression
27162 itself. This lets us Proxypass dir fetches through apache.
27165 Changes in version 0.0.9.2 - 2005-01-04
27166 o Bugfixes on 0.0.9 (crashes and asserts):
27167 - Fix an assert on startup when the disk is full and you're logging
27169 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
27170 style address, then we'd crash.
27171 - Fix an assert trigger when the running-routers string we get from
27172 a dirserver is broken.
27173 - Make worker threads start and run on win32. Now win32 servers
27175 - Bandaid (not actually fix, but now it doesn't crash) an assert
27176 where the dns worker dies mysteriously and the main Tor process
27177 doesn't remember anything about the address it was resolving.
27179 o Bugfixes on 0.0.9 (Win32):
27180 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
27181 name out of the warning/assert messages.
27182 - Fix a superficial "unhandled error on read" bug on win32.
27183 - The win32 installer no longer requires a click-through for our
27184 license, since our Free Software license grants rights but does not
27186 - Win32: When connecting to a dirserver fails, try another one
27187 immediately. (This was already working for non-win32 Tors.)
27188 - Stop trying to parse $HOME on win32 when hunting for default
27190 - Make tor-resolve.c work on win32 by calling network_init().
27192 o Bugfixes on 0.0.9 (other):
27193 - Make 0.0.9.x build on Solaris again.
27194 - Due to a fencepost error, we were blowing away the \n when reporting
27195 confvalue items in the controller. So asking for multiple config
27196 values at once couldn't work.
27197 - When listing circuits that are pending on an opening OR connection,
27198 if we're an OR we were listing circuits that *end* at us as
27199 being pending on every listener, dns/cpu worker, etc. Stop that.
27200 - Dirservers were failing to create 'running-routers' or 'directory'
27201 strings if we had more than some threshold of routers. Fix them so
27202 they can handle any number of routers.
27203 - Fix a superficial "Duplicate mark for close" bug.
27204 - Stop checking for clock skew for OR connections, even for servers.
27205 - Fix a fencepost error that was chopping off the last letter of any
27206 nickname that is the maximum allowed nickname length.
27207 - Update URLs in log messages so they point to the new website.
27208 - Fix a potential problem in mangling server private keys while
27209 writing to disk (not triggered yet, as far as we know).
27210 - Include the licenses for other free software we include in Tor,
27211 now that we're shipping binary distributions more regularly.
27214 Changes in version 0.0.9.1 - 2004-12-15
27215 o Bugfixes on 0.0.9:
27216 - Make hibernation actually work.
27217 - Make HashedControlPassword config option work.
27218 - When we're reporting event circuit status to a controller,
27219 don't use the stream status code.
27222 Changes in version 0.0.9 - 2004-12-12
27224 - Clean up manpage and torrc.sample file.
27225 - Clean up severities and text of log warnings.
27227 - Make servers trigger an assert when they enter hibernation.
27230 Changes in version 0.0.9rc7 - 2004-12-08
27231 o Bugfixes on 0.0.9rc:
27232 - Fix a stack-trashing crash when an exit node begins hibernating.
27233 - Avoid looking at unallocated memory while considering which
27234 ports we need to build circuits to cover.
27235 - Stop a sigpipe: when an 'end' cell races with eof from the app,
27236 we shouldn't hold-open-until-flush if the eof arrived first.
27237 - Fix a bug with init_cookie_authentication() in the controller.
27238 - When recommending new-format log lines, if the upper bound is
27239 LOG_ERR, leave it implicit.
27241 o Bugfixes on 0.0.8.1:
27242 - Fix a whole slew of memory leaks.
27243 - Fix isspace() and friends so they still make Solaris happy
27244 but also so they don't trigger asserts on win32.
27245 - Fix parse_iso_time on platforms without strptime (eg win32).
27246 - win32: tolerate extra "readable" events better.
27247 - win32: when being multithreaded, leave parent fdarray open.
27248 - Make unit tests work on win32.
27251 Changes in version 0.0.9rc6 - 2004-12-06
27252 o Bugfixes on 0.0.9pre:
27253 - Clean up some more integer underflow opportunities (not exploitable
27255 - While hibernating, hup should not regrow our listeners.
27256 - Send an end to the streams we close when we hibernate, rather
27257 than just chopping them off.
27258 - React to eof immediately on non-open edge connections.
27260 o Bugfixes on 0.0.8.1:
27261 - Calculate timeout for waiting for a connected cell from the time
27262 we sent the begin cell, not from the time the stream started. If
27263 it took a long time to establish the circuit, we would time out
27264 right after sending the begin cell.
27265 - Fix router_compare_addr_to_addr_policy: it was not treating a port
27266 of * as always matching, so we were picking reject *:* nodes as
27267 exit nodes too. Oops.
27270 - New circuit building strategy: keep a list of ports that we've
27271 used in the past 6 hours, and always try to have 2 circuits open
27272 or on the way that will handle each such port. Seed us with port
27273 80 so web users won't complain that Tor is "slow to start up".
27274 - Make kill -USR1 dump more useful stats about circuits.
27275 - When warning about retrying or giving up, print the address, so
27276 the user knows which one it's talking about.
27277 - If you haven't used a clean circuit in an hour, throw it away,
27278 just to be on the safe side. (This means after 6 hours a totally
27279 unused Tor client will have no circuits open.)
27282 Changes in version 0.0.9rc5 - 2004-12-01
27283 o Bugfixes on 0.0.8.1:
27284 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
27285 - Let resolve conns retry/expire also, rather than sticking around
27287 - If we are using select, make sure we stay within FD_SETSIZE.
27289 o Bugfixes on 0.0.9pre:
27290 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
27291 but doesn't seem to be currently; thanks to Ilja van Sprundel for
27293 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
27294 instead. Impose minima and maxima for all *Period options; impose
27295 even tighter maxima for fetching if we are a caching dirserver.
27296 Clip rather than rejecting.
27297 - Fetch cached running-routers from servers that serve it (that is,
27298 authdirservers and servers running 0.0.9rc5-cvs or later.)
27301 - Accept *:706 (silc) in default exit policy.
27302 - Implement new versioning format for post 0.1.
27303 - Support "foo.nickname.exit" addresses, to let Alice request the
27304 address "foo" as viewed by exit node "nickname". Based on a patch
27306 - Make tor --version --version dump the cvs Id of every file.
27309 Changes in version 0.0.9rc4 - 2004-11-28
27310 o Bugfixes on 0.0.8.1:
27311 - Make windows sockets actually non-blocking (oops), and handle
27312 win32 socket errors better.
27314 o Bugfixes on 0.0.9rc1:
27315 - Actually catch the -USR2 signal.
27318 Changes in version 0.0.9rc3 - 2004-11-25
27319 o Bugfixes on 0.0.8.1:
27320 - Flush the log file descriptor after we print "Tor opening log file",
27321 so we don't see those messages days later.
27323 o Bugfixes on 0.0.9rc1:
27324 - Make tor-resolve work again.
27325 - Avoid infinite loop in tor-resolve if tor hangs up on it.
27326 - Fix an assert trigger for clients/servers handling resolves.
27329 Changes in version 0.0.9rc2 - 2004-11-24
27330 o Bugfixes on 0.0.9rc1:
27331 - I broke socks5 support while fixing the eof bug.
27332 - Allow unitless bandwidths and intervals; they default to bytes
27334 - New servers don't start out hibernating; they are active until
27335 they run out of bytes, so they have a better estimate of how
27336 long it takes, and so their operators can know they're working.
27339 Changes in version 0.0.9rc1 - 2004-11-23
27340 o Bugfixes on 0.0.8.1:
27341 - Finally fix a bug that's been plaguing us for a year:
27342 With high load, circuit package window was reaching 0. Whenever
27343 we got a circuit-level sendme, we were reading a lot on each
27344 socket, but only writing out a bit. So we would eventually reach
27345 eof. This would be noticed and acted on even when there were still
27346 bytes sitting in the inbuf.
27347 - When poll() is interrupted, we shouldn't believe the revents values.
27349 o Bugfixes on 0.0.9pre6:
27350 - Fix hibernate bug that caused pre6 to be broken.
27351 - Don't keep rephist info for routers that haven't had activity for
27352 24 hours. (This matters now that clients have keys, since we track
27354 - Never call close_temp_logs while validating log options.
27355 - Fix backslash-escaping on tor.sh.in and torctl.in.
27358 - Implement weekly/monthly/daily accounting: now you specify your
27359 hibernation properties by
27360 AccountingMax N bytes|KB|MB|GB|TB
27361 AccountingStart day|week|month [day] HH:MM
27362 Defaults to "month 1 0:00".
27363 - Let bandwidth and interval config options be specified as 5 bytes,
27364 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
27365 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
27366 get back to normal.)
27367 - If your requested entry or exit node has advertised bandwidth 0,
27369 - Be more greedy about filling up relay cells -- we try reading again
27370 once we've processed the stuff we read, in case enough has arrived
27371 to fill the last cell completely.
27372 - Apply NT service patch from Osamu Fujino. Still needs more work.
27375 Changes in version 0.0.9pre6 - 2004-11-15
27376 o Bugfixes on 0.0.8.1:
27377 - Fix assert failure on malformed socks4a requests.
27378 - Use identity comparison, not nickname comparison, to choose which
27379 half of circuit-ID-space each side gets to use. This is needed
27380 because sometimes we think of a router as a nickname, and sometimes
27381 as a hex ID, and we can't predict what the other side will do.
27382 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
27383 write() call will fail and we handle it there.
27384 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
27385 and smartlist_len, which are two major profiling offenders.
27387 o Bugfixes on 0.0.9pre5:
27388 - Fix a bug in read_all that was corrupting config files on windows.
27389 - When we're raising the max number of open file descriptors to
27390 'unlimited', don't log that we just raised it to '-1'.
27391 - Include event code with events, as required by control-spec.txt.
27392 - Don't give a fingerprint when clients do --list-fingerprint:
27393 it's misleading, because it will never be the same again.
27394 - Stop using strlcpy in tor_strndup, since it was slowing us
27396 - Remove warn on startup about missing cached-directory file.
27397 - Make kill -USR1 work again.
27398 - Hibernate if we start tor during the "wait for wakeup-time" phase
27399 of an accounting interval. Log our hibernation plans better.
27400 - Authoritative dirservers now also cache their directory, so they
27401 have it on start-up.
27404 - Fetch running-routers; cache running-routers; compress
27405 running-routers; serve compressed running-routers.z
27406 - Add NSI installer script contributed by J Doe.
27407 - Commit VC6 and VC7 workspace/project files.
27408 - Commit a tor.spec for making RPM files, with help from jbash.
27409 - Add contrib/torctl.in contributed by Glenn Fink.
27410 - Implement the control-spec's SAVECONF command, to write your
27411 configuration to torrc.
27412 - Get cookie authentication for the controller closer to working.
27413 - Include control-spec.txt in the tarball.
27414 - When set_conf changes our server descriptor, upload a new copy.
27415 But don't upload it too often if there are frequent changes.
27416 - Document authentication config in man page, and document signals
27418 - Clean up confusing parts of man page and torrc.sample.
27419 - Make expand_filename handle ~ and ~username.
27420 - Use autoconf to enable largefile support where necessary. Use
27421 ftello where available, since ftell can fail at 2GB.
27422 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
27423 log more informatively.
27424 - Give a slightly more useful output for "tor -h".
27425 - Refuse application socks connections to port 0.
27426 - Check clock skew for verified servers, but allow unverified
27427 servers and clients to have any clock skew.
27428 - Break DirFetchPostPeriod into:
27429 - DirFetchPeriod for fetching full directory,
27430 - StatusFetchPeriod for fetching running-routers,
27431 - DirPostPeriod for posting server descriptor,
27432 - RendPostPeriod for posting hidden service descriptors.
27433 - Make sure the hidden service descriptors are at a random offset
27434 from each other, to hinder linkability.
27437 Changes in version 0.0.9pre5 - 2004-11-09
27438 o Bugfixes on 0.0.9pre4:
27439 - Fix a seg fault in unit tests (doesn't affect main program).
27440 - Fix an assert bug where a hidden service provider would fail if
27441 the first hop of his rendezvous circuit was down.
27442 - Hidden service operators now correctly handle version 1 style
27443 INTRODUCE1 cells (nobody generates them still, so not a critical
27445 - If do_hup fails, actually notice.
27446 - Handle more errnos from accept() without closing the listener.
27447 Some OpenBSD machines were closing their listeners because
27448 they ran out of file descriptors.
27449 - Send resolve cells to exit routers that are running a new
27450 enough version of the resolve code to work right.
27451 - Better handling of winsock includes on non-MSV win32 compilers.
27452 - Some people had wrapped their tor client/server in a script
27453 that would restart it whenever it died. This did not play well
27454 with our "shut down if your version is obsolete" code. Now people
27455 don't fetch a new directory if their local cached version is
27457 - Make our autogen.sh work on ksh as well as bash.
27460 - Hibernation: New config option "AccountingMaxKB" lets you
27461 set how many KBytes per month you want to allow your server to
27462 consume. Rather than spreading those bytes out evenly over the
27463 month, we instead hibernate for some of the month and pop up
27464 at a deterministic time, work until the bytes are consumed, then
27465 hibernate again. Config option "MonthlyAccountingStart" lets you
27466 specify which day of the month your billing cycle starts on.
27467 - Control interface: a separate program can now talk to your
27468 client/server over a socket, and get/set config options, receive
27469 notifications of circuits and streams starting/finishing/dying,
27470 bandwidth used, etc. The next step is to get some GUIs working.
27471 Let us know if you want to help out. See doc/control-spec.txt .
27472 - Ship a contrib/tor-control.py as an example script to interact
27473 with the control port.
27474 - "tor --hash-password zzyxz" will output a salted password for
27475 use in authenticating to the control interface.
27476 - New log format in config:
27477 "Log minsev[-maxsev] stdout|stderr|syslog" or
27478 "Log minsev[-maxsev] file /var/foo"
27481 - DirPolicy config option, to let people reject incoming addresses
27482 from their dirserver.
27483 - "tor --list-fingerprint" will list your identity key fingerprint
27485 - Add "pass" target for RedirectExit, to make it easier to break
27486 out of a sequence of RedirectExit rules.
27487 - Clients now generate a TLS cert too, in preparation for having
27488 them act more like real nodes.
27489 - Ship src/win32/ in the tarball, so people can use it to build.
27490 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
27492 - New "router-status" line in directory, to better bind each verified
27493 nickname to its identity key.
27494 - Deprecate unofficial config option abbreviations, and abbreviations
27495 not on the command line.
27496 - Add a pure-C tor-resolve implementation.
27497 - Use getrlimit and friends to ensure we can reach MaxConn (currently
27498 1024) file descriptors.
27500 o Code security improvements, inspired by Ilja:
27501 - Replace sprintf with snprintf. (I think they were all safe, but
27503 - Replace strcpy/strncpy with strlcpy in more places.
27504 - Avoid strcat; use snprintf or strlcat instead.
27505 - snprintf wrapper with consistent (though not C99) overflow behavior.
27508 Changes in version 0.0.9pre4 - 2004-10-17
27509 o Bugfixes on 0.0.9pre3:
27510 - If the server doesn't specify an exit policy, use the real default
27511 exit policy, not reject *:*.
27512 - Ignore fascistfirewall when uploading/downloading hidden service
27513 descriptors, since we go through Tor for those; and when using
27514 an HttpProxy, since we assume it can reach them all.
27515 - When looking for an authoritative dirserver, use only the ones
27516 configured at boot. Don't bother looking in the directory.
27517 - The rest of the fix for get_default_conf_file() on older win32.
27518 - Make 'Routerfile' config option obsolete.
27521 - New 'MyFamily nick1,...' config option for a server to
27522 specify other servers that shouldn't be used in the same circuit
27523 with it. Only believed if nick1 also specifies us.
27524 - New 'NodeFamily nick1,nick2,...' config option for a client to
27525 specify nodes that it doesn't want to use in the same circuit.
27526 - New 'Redirectexit pattern address:port' config option for a
27527 server to redirect exit connections, e.g. to a local squid.
27530 Changes in version 0.0.9pre3 - 2004-10-13
27531 o Bugfixes on 0.0.8.1:
27532 - Better torrc example lines for dirbindaddress and orbindaddress.
27533 - Improved bounds checking on parsed ints (e.g. config options and
27534 the ones we find in directories.)
27535 - Better handling of size_t vs int, so we're more robust on 64
27537 - Fix the rest of the bug where a newly started OR would appear
27538 as unverified even after we've added his fingerprint and hupped
27540 - Fix a bug from 0.0.7: when read() failed on a stream, we would
27541 close it without sending back an end. So 'connection refused'
27542 would simply be ignored and the user would get no response.
27544 o Bugfixes on 0.0.9pre2:
27545 - Serving the cached-on-disk directory to people is bad. We now
27546 provide no directory until we've fetched a fresh one.
27547 - Workaround for bug on windows where cached-directories get crlf
27549 - Make get_default_conf_file() work on older windows too.
27550 - If we write a *:* exit policy line in the descriptor, don't write
27551 any more exit policy lines.
27554 - Use only 0.0.9pre1 and later servers for resolve cells.
27555 - Make the dirservers file obsolete.
27556 - Include a dir-signing-key token in directories to tell the
27557 parsing entity which key is being used to sign.
27558 - Remove the built-in bulky default dirservers string.
27559 - New config option "Dirserver %s:%d [fingerprint]", which can be
27560 repeated as many times as needed. If no dirservers specified,
27561 default to moria1,moria2,tor26.
27562 - Make moria2 advertise a dirport of 80, so people behind firewalls
27563 will be able to get a directory.
27564 - Http proxy support
27565 - Dirservers translate requests for http://%s:%d/x to /x
27566 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
27567 be routed through this host.
27568 - Clients ask for /tor/x rather than /x for new enough dirservers.
27569 This way we can one day coexist peacefully with apache.
27570 - Clients specify a "Host: %s%d" http header, to be compatible
27571 with more proxies, and so running squid on an exit node can work.
27574 Changes in version 0.0.8.1 - 2004-10-13
27576 - Fix a seg fault that can be triggered remotely for Tor
27577 clients/servers with an open dirport.
27578 - Fix a rare assert trigger, where routerinfos for entries in
27579 our cpath would expire while we're building the path.
27580 - Fix a bug in OutboundBindAddress so it (hopefully) works.
27581 - Fix a rare seg fault for people running hidden services on
27582 intermittent connections.
27583 - Fix a bug in parsing opt keywords with objects.
27584 - Fix a stale pointer assert bug when a stream detaches and
27586 - Fix a string format vulnerability (probably not exploitable)
27587 in reporting stats locally.
27588 - Fix an assert trigger: sometimes launching circuits can fail
27589 immediately, e.g. because too many circuits have failed recently.
27590 - Fix a compile warning on 64 bit platforms.
27593 Changes in version 0.0.9pre2 - 2004-10-03
27595 - Make fetching a cached directory work for 64-bit platforms too.
27596 - Make zlib.h a required header, not an optional header.
27599 Changes in version 0.0.9pre1 - 2004-10-01
27601 - Stop using separate defaults for no-config-file and
27602 empty-config-file. Now you have to explicitly turn off SocksPort,
27603 if you don't want it open.
27604 - Fix a bug in OutboundBindAddress so it (hopefully) works.
27605 - Improve man page to mention more of the 0.0.8 features.
27606 - Fix a rare seg fault for people running hidden services on
27607 intermittent connections.
27608 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
27610 - Fix more dns related bugs: send back resolve_failed and end cells
27611 more reliably when the resolve fails, rather than closing the
27612 circuit and then trying to send the cell. Also attach dummy resolve
27613 connections to a circuit *before* calling dns_resolve(), to fix
27614 a bug where cached answers would never be sent in RESOLVED cells.
27615 - When we run out of disk space, or other log writing error, don't
27616 crash. Just stop logging to that log and continue.
27617 - We were starting to daemonize before we opened our logs, so if
27618 there were any problems opening logs, we would complain to stderr,
27619 which wouldn't work, and then mysteriously exit.
27620 - Fix a rare bug where sometimes a verified OR would connect to us
27621 before he'd uploaded his descriptor, which would cause us to
27622 assign conn->nickname as though he's unverified. Now we look through
27623 the fingerprint list to see if he's there.
27624 - Fix a rare assert trigger, where routerinfos for entries in
27625 our cpath would expire while we're building the path.
27628 - Clients can ask dirservers for /dir.z to get a compressed version
27629 of the directory. Only works for servers running 0.0.9, of course.
27630 - Make clients cache directories and use them to seed their router
27631 lists at startup. This means clients have a datadir again.
27632 - Configuration infrastructure support for warning on obsolete
27634 - Respond to content-encoding headers by trying to uncompress as
27636 - Reply with a deflated directory when a client asks for "dir.z".
27637 We could use allow-encodings instead, but allow-encodings isn't
27638 specified in HTTP 1.0.
27639 - Raise the max dns workers from 50 to 100.
27640 - Discourage people from setting their dirfetchpostperiod more often
27641 than once per minute.
27642 - Protect dirservers from overzealous descriptor uploading -- wait
27643 10 seconds after directory gets dirty, before regenerating.
27646 Changes in version 0.0.8 - 2004-08-25
27647 o Port it to SunOS 5.9 / Athena
27650 Changes in version 0.0.8rc2 - 2004-08-20
27651 o Make it compile on cygwin again.
27652 o When picking unverified routers, skip those with low uptime and/or
27653 low bandwidth, depending on what properties you care about.
27656 Changes in version 0.0.8rc1 - 2004-08-18
27657 o Changes from 0.0.7.3:
27659 - Fix assert triggers: if the other side returns an address 0.0.0.0,
27660 don't put it into the client dns cache.
27661 - If a begin failed due to exit policy, but we believe the IP address
27662 should have been allowed, switch that router to exitpolicy reject *:*
27663 until we get our next directory.
27665 - Clients choose nodes proportional to advertised bandwidth.
27666 - Avoid using nodes with low uptime as introduction points.
27667 - Handle servers with dynamic IP addresses: don't replace
27668 options->Address with the resolved one at startup, and
27669 detect our address right before we make a routerinfo each time.
27670 - 'FascistFirewall' option to pick dirservers and ORs on specific
27671 ports; plus 'FirewallPorts' config option to tell FascistFirewall
27672 which ports are open. (Defaults to 80,443)
27673 - Be more aggressive about trying to make circuits when the network
27674 has changed (e.g. when you unsuspend your laptop).
27675 - Check for time skew on http headers; report date in response to
27677 - If the entrynode config line has only one node, don't pick it as
27679 - Add strict{entry|exit}nodes config options. If set to 1, then
27680 we refuse to build circuits that don't include the specified entry
27682 - OutboundBindAddress config option, to bind to a specific
27683 IP address for outgoing connect()s.
27684 - End truncated log entries (e.g. directories) with "[truncated]".
27686 o Patches to 0.0.8preX:
27688 - Patches to compile and run on win32 again (maybe)?
27689 - Fix crash when looking for ~/.torrc with no $HOME set.
27690 - Fix a race bug in the unit tests.
27691 - Handle verified/unverified name collisions better when new
27692 routerinfo's arrive in a directory.
27693 - Sometimes routers were getting entered into the stats before
27694 we'd assigned their identity_digest. Oops.
27695 - Only pick and establish intro points after we've gotten a
27698 - AllowUnverifiedNodes config option to let circuits choose no-name
27699 routers in entry,middle,exit,introduction,rendezvous positions.
27700 Allow middle and rendezvous positions by default.
27701 - Add a man page for tor-resolve.
27704 Changes in version 0.0.7.3 - 2004-08-12
27705 o Stop dnsworkers from triggering an assert failure when you
27706 ask them to resolve the host "".
27709 Changes in version 0.0.8pre3 - 2004-08-09
27710 o Changes from 0.0.7.2:
27711 - Allow multiple ORs with same nickname in routerlist -- now when
27712 people give us one identity key for a nickname, then later
27713 another, we don't constantly complain until the first expires.
27714 - Remember used bandwidth (both in and out), and publish 15-minute
27715 snapshots for the past day into our descriptor.
27716 - You can now fetch $DIRURL/running-routers to get just the
27717 running-routers line, not the whole descriptor list. (But
27718 clients don't use this yet.)
27719 - When people mistakenly use Tor as an http proxy, point them
27720 at the tor-doc.html rather than the INSTALL.
27721 - Remove our mostly unused -- and broken -- hex_encode()
27722 function. Use base16_encode() instead. (Thanks to Timo Lindfors
27723 for pointing out this bug.)
27724 - Rotate onion keys every 12 hours, not every 2 hours, so we have
27725 fewer problems with people using the wrong key.
27726 - Change the default exit policy to reject the default edonkey,
27727 kazaa, gnutella ports.
27728 - Add replace_file() to util.[ch] to handle win32's rename().
27730 o Changes from 0.0.8preX:
27731 - Fix two bugs in saving onion keys to disk when rotating, so
27732 hopefully we'll get fewer people using old onion keys.
27733 - Fix an assert error that was making SocksPolicy not work.
27734 - Be willing to expire routers that have an open dirport -- it's
27735 just the authoritative dirservers we want to not forget.
27736 - Reject tor-resolve requests for .onion addresses early, so we
27737 don't build a whole rendezvous circuit and then fail.
27738 - When you're warning a server that he's unverified, don't cry
27739 wolf unpredictably.
27740 - Fix a race condition: don't try to extend onto a connection
27741 that's still handshaking.
27742 - For servers in clique mode, require the conn to be open before
27743 you'll choose it for your path.
27744 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
27745 end relay cell, etc.
27746 - Measure bandwidth capacity over the last 24 hours, not just 12
27747 - Bugfix: authoritative dirservers were making and signing a new
27748 directory for each client, rather than reusing the cached one.
27751 Changes in version 0.0.8pre2 - 2004-08-04
27752 o Changes from 0.0.7.2:
27754 - Check directory signature _before_ you decide whether you're
27755 you're running an obsolete version and should exit.
27756 - Check directory signature _before_ you parse the running-routers
27757 list to decide who's running or verified.
27758 - Bugfixes and features:
27759 - Check return value of fclose while writing to disk, so we don't
27760 end up with broken files when servers run out of disk space.
27761 - Log a warning if the user uses an unsafe socks variant, so people
27762 are more likely to learn about privoxy or socat.
27763 - Dirservers now include RFC1123-style dates in the HTTP headers,
27764 which one day we will use to better detect clock skew.
27766 o Changes from 0.0.8pre1:
27767 - Make it compile without warnings again on win32.
27768 - Log a warning if you're running an unverified server, to let you
27769 know you might want to get it verified.
27770 - Only pick a default nickname if you plan to be a server.
27773 Changes in version 0.0.8pre1 - 2004-07-23
27775 - Made our unit tests compile again on OpenBSD 3.5, and tor
27776 itself compile again on OpenBSD on a sparc64.
27777 - We were neglecting milliseconds when logging on win32, so
27778 everything appeared to happen at the beginning of each second.
27780 o Protocol changes:
27781 - 'Extend' relay cell payloads now include the digest of the
27782 intended next hop's identity key. Now we can verify that we're
27783 extending to the right router, and also extend to routers we
27784 hadn't heard of before.
27787 - Tor nodes can now act as relays (with an advertised ORPort)
27788 without being manually verified by the dirserver operators.
27789 - Uploaded descriptors of unverified routers are now accepted
27790 by the dirservers, and included in the directory.
27791 - Verified routers are listed by nickname in the running-routers
27792 list; unverified routers are listed as "$<fingerprint>".
27793 - We now use hash-of-identity-key in most places rather than
27794 nickname or addr:port, for improved security/flexibility.
27795 - To avoid Sybil attacks, paths still use only verified servers.
27796 But now we have a chance to play around with hybrid approaches.
27797 - Nodes track bandwidth usage to estimate capacity (not used yet).
27798 - ClientOnly option for nodes that never want to become servers.
27799 - Directory caching.
27800 - "AuthoritativeDir 1" option for the official dirservers.
27801 - Now other nodes (clients and servers) will cache the latest
27802 directory they've pulled down.
27803 - They can enable their DirPort to serve it to others.
27804 - Clients will pull down a directory from any node with an open
27805 DirPort, and check the signature/timestamp correctly.
27806 - Authoritative dirservers now fetch directories from other
27807 authdirservers, to stay better synced.
27808 - Running-routers list tells who's down also, along with noting
27809 if they're verified (listed by nickname) or unverified (listed
27811 - Allow dirservers to serve running-router list separately.
27812 This isn't used yet.
27813 - ORs connect-on-demand to other ORs
27814 - If you get an extend cell to an OR you're not connected to,
27815 connect, handshake, and forward the create cell.
27816 - The authoritative dirservers stay connected to everybody,
27817 and everybody stays connected to 0.0.7 servers, but otherwise
27818 clients/servers expire unused connections after 5 minutes.
27819 - When servers get a sigint, they delay 30 seconds (refusing new
27820 connections) then exit. A second sigint causes immediate exit.
27821 - File and name management:
27822 - Look for .torrc if no CONFDIR "torrc" is found.
27823 - If no datadir is defined, then choose, make, and secure ~/.tor
27825 - If torrc not found, exitpolicy reject *:*.
27826 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
27827 - If no nickname is defined, derive default from hostname.
27828 - Rename secret key files, e.g. identity.key -> secret_id_key,
27829 to discourage people from mailing their identity key to tor-ops.
27830 - Refuse to build a circuit before the directory has arrived --
27831 it won't work anyway, since you won't know the right onion keys
27833 - Try other dirservers immediately if the one you try is down. This
27834 should tolerate down dirservers better now.
27835 - Parse tor version numbers so we can do an is-newer-than check
27836 rather than an is-in-the-list check.
27837 - New socks command 'resolve', to let us shim gethostbyname()
27839 - A 'tor_resolve' script to access the socks resolve functionality.
27840 - A new socks-extensions.txt doc file to describe our
27841 interpretation and extensions to the socks protocols.
27842 - Add a ContactInfo option, which gets published in descriptor.
27843 - Publish OR uptime in descriptor (and thus in directory) too.
27844 - Write tor version at the top of each log file
27845 - New docs in the tarball:
27847 - Document that you should proxy your SSL traffic too.
27850 Changes in version 0.0.7.2 - 2004-07-07
27851 o A better fix for the 0.0.0.0 problem, that will hopefully
27852 eliminate the remaining related assertion failures.
27855 Changes in version 0.0.7.1 - 2004-07-04
27856 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
27857 since internally we use 0.0.0.0 to signify "not yet resolved".
27860 Changes in version 0.0.7 - 2004-06-07
27861 o Updated the man page to reflect the new features.
27864 Changes in version 0.0.7rc2 - 2004-06-06
27865 o Changes from 0.0.7rc1:
27866 - Make it build on Win32 again.
27867 o Changes from 0.0.6.2:
27868 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
27872 Changes in version 0.0.7rc1 - 2004-06-02
27874 - On sighup, we were adding another log without removing the first
27875 one. So log messages would get duplicated n times for n sighups.
27876 - Several cases of using a connection after we'd freed it. The
27877 problem was that connections that are pending resolve are in both
27878 the pending_resolve tree, and also the circuit's resolving_streams
27879 list. When you want to remove one, you must remove it from both.
27880 - Fix a double-mark-for-close where an end cell arrived for a
27881 resolving stream, and then the resolve failed.
27882 - Check directory signatures based on name of signer, not on whom
27883 we got the directory from. This will let us cache directories more
27886 - Crank up some of our constants to handle more users.
27889 Changes in version 0.0.7pre1 - 2004-06-02
27890 o Fixes for crashes and other obnoxious bugs:
27891 - Fix an epipe bug: sometimes when directory connections failed
27892 to connect, we would give them a chance to flush before closing
27894 - When we detached from a circuit because of resolvefailed, we
27895 would immediately try the same circuit twice more, and then
27896 give up on the resolve thinking we'd tried three different
27898 - Limit the number of intro circuits we'll attempt to build for a
27899 hidden service per 15-minute period.
27900 - Check recommended-software string *early*, before actually parsing
27901 the directory. Thus we can detect an obsolete version and exit,
27902 even if the new directory format doesn't parse.
27903 o Fixes for security bugs:
27904 - Remember which nodes are dirservers when you startup, and if a
27905 random OR enables his dirport, don't automatically assume he's
27906 a trusted dirserver.
27908 - Directory connections were asking the wrong poll socket to
27909 start writing, and not asking themselves to start writing.
27910 - When we detached from a circuit because we sent a begin but
27911 didn't get a connected, we would use it again the first time;
27912 but after that we would correctly switch to a different one.
27913 - Stop warning when the first onion decrypt attempt fails; they
27914 will sometimes legitimately fail now that we rotate keys.
27915 - Override unaligned-access-ok check when $host_cpu is ia64 or
27916 arm. Apparently they allow it but the kernel whines.
27917 - Dirservers try to reconnect periodically too, in case connections
27919 - Fix some memory leaks in directory servers.
27920 - Allow backslash in Win32 filenames.
27921 - Made Tor build complain-free on FreeBSD, hopefully without
27922 breaking other BSD builds. We'll see.
27924 - Doxygen markup on all functions and global variables.
27925 - Make directory functions update routerlist, not replace it. So
27926 now directory disagreements are not so critical a problem.
27927 - Remove the upper limit on number of descriptors in a dirserver's
27928 directory (not that we were anywhere close).
27929 - Allow multiple logfiles at different severity ranges.
27930 - Allow *BindAddress to specify ":port" rather than setting *Port
27931 separately. Allow multiple instances of each BindAddress config
27932 option, so you can bind to multiple interfaces if you want.
27933 - Allow multiple exit policy lines, which are processed in order.
27934 Now we don't need that huge line with all the commas in it.
27935 - Enable accept/reject policies on SOCKS connections, so you can bind
27936 to 0.0.0.0 but still control who can use your OP.
27939 Changes in version 0.0.6.2 - 2004-05-16
27940 o Our integrity-checking digest was checking only the most recent cell,
27941 not the previous cells like we'd thought.
27942 Thanks to Stefan Mark for finding the flaw!
27945 Changes in version 0.0.6.1 - 2004-05-06
27946 o Fix two bugs in our AES counter-mode implementation (this affected
27947 onion-level stream encryption, but not TLS-level). It turns
27948 out we were doing something much more akin to a 16-character
27949 polyalphabetic cipher. Oops.
27950 Thanks to Stefan Mark for finding the flaw!
27951 o Retire moria3 as a directory server, and add tor26 as a directory
27955 Changes in version 0.0.6 - 2004-05-02
27956 [version bump only]
27959 Changes in version 0.0.6rc4 - 2004-05-01
27960 o Update the built-in dirservers list to use the new directory format
27961 o Fix a rare seg fault: if a node offering a hidden service attempts
27962 to build a circuit to Alice's rendezvous point and fails before it
27963 reaches the last hop, it retries with a different circuit, but
27965 o Handle windows socket errors correctly.
27968 Changes in version 0.0.6rc3 - 2004-04-28
27969 o Don't expire non-general excess circuits (if we had enough
27970 circuits open, we were expiring rendezvous circuits -- even
27971 when they had a stream attached. oops.)
27972 o Fetch randomness from /dev/urandom better (not via fopen/fread)
27973 o Better debugging for tls errors
27974 o Some versions of openssl have an SSL_pending function that erroneously
27975 returns bytes when there is a non-application record pending.
27976 o Set Content-Type on the directory and hidserv descriptor.
27977 o Remove IVs from cipher code, since AES-ctr has none.
27978 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
27979 o We were using an array of length zero in a few places.
27980 o win32's gethostbyname can't resolve an IP to an IP.
27981 o win32's close can't close a socket.
27984 Changes in version 0.0.6rc2 - 2004-04-26
27985 o Fix a bug where we were closing tls connections intermittently.
27986 It turns out openssl keeps its errors around -- so if an error
27987 happens, and you don't ask about it, and then another openssl
27988 operation happens and succeeds, and you ask if there was an error,
27989 it tells you about the first error. Fun fun.
27990 o Fix a bug that's been lurking since 27 may 03 (!)
27991 When passing back a destroy cell, we would use the wrong circ id.
27992 'Mostly harmless', but still worth fixing.
27993 o Since we don't support truncateds much, don't bother sending them;
27994 just close the circ.
27995 o check for <machine/limits.h> so we build on NetBSD again (I hope).
27996 o don't crash if a conn that sent a begin has suddenly lost its circuit
27997 (this was quite rare).
28000 Changes in version 0.0.6rc1 - 2004-04-25
28001 o We now rotate link (tls context) keys and onion keys.
28002 o CREATE cells now include oaep padding, so you can tell
28003 if you decrypted them correctly.
28004 o Add bandwidthburst to server descriptor.
28005 o Directories now say which dirserver signed them.
28006 o Use a tor_assert macro that logs failed assertions too.
28009 Changes in version 0.0.6pre5 - 2004-04-18
28010 o changes from 0.0.6pre4:
28011 - make tor build on broken freebsd 5.2 installs
28012 - fix a failed assert when you try an intro point, get a nack, and try
28013 a second one and it works.
28014 - when alice uses a port that the hidden service doesn't accept,
28015 it now sends back an end cell (denied by exit policy). otherwise
28016 alice would just have to wait to time out.
28017 - fix another rare bug: when we had tried all the intro
28018 points for a hidden service, we fetched the descriptor
28019 again, but we left our introcirc thinking it had already
28020 sent an intro, so it kept waiting for a response...
28021 - bugfix: when you sleep your hidden-service laptop, as soon
28022 as it wakes up it tries to upload a service descriptor, but
28023 socketpair fails for some reason (localhost not up yet?).
28024 now we simply give up on that upload, and we'll try again later.
28025 i'd still like to find the bug though.
28026 - if an intro circ waiting for an ack dies before getting one, then
28028 - we were reusing stale service descriptors and refetching usable
28032 Changes in version 0.0.6pre4 - 2004-04-14
28033 o changes from 0.0.6pre3:
28034 - when bob fails to connect to the rendezvous point, and his
28035 circ didn't fail because of the rendezvous point itself, then
28036 he retries a couple of times
28037 - we expire introduction and rendezvous circs more thoroughly
28038 (sometimes they were hanging around forever)
28039 - we expire unattached rendezvous streams that have been around
28040 too long (they were sticking around forever).
28041 - fix a measly fencepost error that was crashing everybody with
28045 Changes in version 0.0.6pre3 - 2004-04-14
28046 o changes from 0.0.6pre2:
28047 - make hup work again
28048 - fix some memory leaks for dirservers
28049 - allow more skew in rendezvous descriptor timestamps, to help
28050 handle people like blanu who don't know what time it is
28051 - normal circs are 3 hops, but some rend/intro circs are 4, if
28052 the initiator doesn't get to choose the last hop
28053 - send acks for introductions, so alice can know whether to try
28055 - bob publishes intro points more correctly
28056 o changes from 0.0.5:
28057 - fix an assert trigger that's been plaguing us since the days
28058 of 0.0.2prexx (thanks weasel!)
28059 - retry stream correctly when we fail to connect because of
28060 exit-policy-reject (should try another) or can't-resolve-address
28061 (also should try another, because dns on random internet servers
28063 - when we hup a dirserver and we've *removed* a server from the
28064 approved-routers list, now we remove that server from the
28065 in-memory directories too
28068 Changes in version 0.0.6pre2 - 2004-04-08
28069 o We fixed our base32 implementation. Now it works on all architectures.
28072 Changes in version 0.0.6pre1 - 2004-04-08
28074 - Hidden services and rendezvous points are implemented. Go to
28075 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
28076 hidden services. (This only works via a socks4a proxy such as
28077 Privoxy, and currently it's quite slow.)
28080 Changes in version 0.0.5 - 2004-03-30
28081 [version bump only]
28084 Changes in version 0.0.5rc3 - 2004-03-29
28085 o Install torrc as torrc.sample -- we no longer clobber your
28087 o Re-enable recommendedversion checking (we broke it in rc2, oops)
28088 o Add in a 'notice' log level for things the operator should hear
28089 but that aren't warnings
28092 Changes in version 0.0.5rc2 - 2004-03-29
28093 o Hold socks connection open until reply is flushed (if possible)
28094 o Make exit nodes resolve IPs to IPs immediately, rather than asking
28095 the dns farm to do it.
28096 o Fix c99 aliasing warnings in rephist.c
28097 o Don't include server descriptors that are older than 24 hours in the
28099 o Give socks 'reject' replies their whole 15s to attempt to flush,
28100 rather than seeing the 60s timeout and assuming the flush had failed.
28101 o Clean automake droppings from the cvs repository
28104 Changes in version 0.0.5rc1 - 2004-03-28
28105 o Fix mangled-state bug in directory fetching (was causing sigpipes).
28106 o Only build circuits after we've fetched the directory: clients were
28107 using only the directory servers before they'd fetched a directory.
28108 This also means longer startup time; so it goes.
28109 o Fix an assert trigger where an OP would fail to handshake, and we'd
28110 expect it to have a nickname.
28111 o Work around a tsocks bug: do a socks reject when AP connection dies
28112 early, else tsocks goes into an infinite loop.
28115 Changes in version 0.0.4 - 2004-03-26
28116 o When connecting to a dirserver or OR and the network is down,
28120 Changes in version 0.0.3 - 2004-03-26
28121 o Warn and fail if server chose a nickname with illegal characters
28122 o Port to Solaris and Sparc:
28123 - include missing header fcntl.h
28124 - have autoconf find -lsocket -lnsl automatically
28125 - deal with hardware word alignment
28126 - make uname() work (solaris has a different return convention)
28127 - switch from using signal() to sigaction()
28128 o Preliminary work on reputation system:
28129 - Keep statistics on success/fail of connect attempts; they're published
28130 by kill -USR1 currently.
28131 - Add a RunTesting option to try to learn link state by creating test
28132 circuits, even when SocksPort is off.
28133 - Remove unused open circuits when there are too many.
28136 Changes in version 0.0.2 - 2004-03-19
28137 - Include strlcpy and strlcat for safer string ops
28138 - define INADDR_NONE so we compile (but still not run) on solaris
28141 Changes in version 0.0.2pre27 - 2004-03-14
28143 - Allow internal tor networks (we were rejecting internal IPs,
28144 now we allow them if they're set explicitly).
28145 - And fix a few endian issues.
28148 Changes in version 0.0.2pre26 - 2004-03-14
28150 - If a stream times out after 15s without a connected cell, don't
28151 try that circuit again: try a new one.
28152 - Retry streams at most 4 times. Then give up.
28153 - When a dirserver gets a descriptor from an unknown router, it
28154 logs its fingerprint (so the dirserver operator can choose to
28155 accept it even without mail from the server operator).
28156 - Inform unapproved servers when we reject their descriptors.
28157 - Make tor build on Windows again. It works as a client, who knows
28159 - Clearer instructions in the torrc for how to set up a server.
28160 - Be more efficient about reading fd's when our global token bucket
28161 (used for rate limiting) becomes empty.
28163 - Stop asserting that computers always go forward in time. It's
28165 - When we sent a cell (e.g. destroy) and then marked an OR connection
28166 expired, we might close it before finishing a flush if the other
28167 side isn't reading right then.
28168 - Don't allow dirservers to start if they haven't defined
28169 RecommendedVersions
28170 - We were caching transient dns failures. Oops.
28171 - Prevent servers from publishing an internal IP as their address.
28172 - Address a strcat vulnerability in circuit.c
28175 Changes in version 0.0.2pre25 - 2004-03-04
28177 - Put the OR's IP in its router descriptor, not its fqdn. That way
28178 we'll stop being stalled by gethostbyname for nodes with flaky dns,
28181 - If the user typed in an address that didn't resolve, the server
28185 Changes in version 0.0.2pre24 - 2004-03-03
28187 - Fix an assertion failure in dns.c, where we were trying to dequeue
28188 a pending dns resolve even if it wasn't pending
28189 - Fix a spurious socks5 warning about still trying to write after the
28190 connection is finished.
28191 - Hold certain marked_for_close connections open until they're finished
28192 flushing, rather than losing bytes by closing them too early.
28193 - Correctly report the reason for ending a stream
28194 - Remove some duplicate calls to connection_mark_for_close
28195 - Put switch_id and start_daemon earlier in the boot sequence, so it
28196 will actually try to chdir() to options.DataDirectory
28197 - Make 'make test' exit(1) if a test fails; fix some unit tests
28198 - Make tor fail when you use a config option it doesn't know about,
28199 rather than warn and continue.
28200 - Make --version work
28201 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
28204 Changes in version 0.0.2pre23 - 2004-02-29
28206 - Print a statement when the first circ is finished, so the user
28207 knows it's working.
28208 - If a relay cell is unrecognized at the end of the circuit,
28209 send back a destroy. (So attacks to mutate cells are more
28211 - New config option 'excludenodes' to avoid certain nodes for circuits.
28212 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
28213 so you can collect coredumps there.
28215 - Fix a bug in tls flushing where sometimes data got wedged and
28216 didn't flush until more data got sent. Hopefully this bug was
28217 a big factor in the random delays we were seeing.
28218 - Make 'connected' cells include the resolved IP, so the client
28219 dns cache actually gets populated.
28220 - Disallow changing from ORPort=0 to ORPort>0 on hup.
28221 - When we time-out on a stream and detach from the circuit, send an
28222 end cell down it first.
28223 - Only warn about an unknown router (in exitnodes, entrynodes,
28224 excludenodes) after we've fetched a directory.
28227 Changes in version 0.0.2pre22 - 2004-02-26
28229 - Servers publish less revealing uname information in descriptors.
28230 - More memory tracking and assertions, to crash more usefully when
28232 - If the default torrc isn't there, just use some default defaults.
28233 Plus provide an internal dirservers file if they don't have one.
28234 - When the user tries to use Tor as an http proxy, give them an http
28235 501 failure explaining that we're a socks proxy.
28236 - Dump a new router.desc on hup, to help confused people who change
28237 their exit policies and then wonder why router.desc doesn't reflect
28239 - Clean up the generic tor.sh init script that we ship with.
28241 - If the exit stream is pending on the resolve, and a destroy arrives,
28242 then the stream wasn't getting removed from the pending list. I
28243 think this was the one causing recent server crashes.
28244 - Use a more robust poll on OSX 10.3, since their poll is flaky.
28245 - When it couldn't resolve any dirservers, it was useless from then on.
28246 Now it reloads the RouterFile (or default dirservers) if it has no
28248 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
28249 many users don't even *have* a /usr/local/sbin/.
28252 Changes in version 0.0.2pre21 - 2004-02-18
28254 - There's a ChangeLog file that actually reflects the changelog.
28255 - There's a 'torify' wrapper script, with an accompanying
28256 tor-tsocks.conf, that simplifies the process of using tsocks for
28257 tor. It even has a man page.
28258 - The tor binary gets installed to sbin rather than bin now.
28259 - Retry streams where the connected cell hasn't arrived in 15 seconds
28260 - Clean up exit policy handling -- get the default out of the torrc,
28261 so we can update it without forcing each server operator to fix
28263 - Allow imaps and pop3s in default exit policy
28265 - Prevent picking middleman nodes as the last node in the circuit
28268 Changes in version 0.0.2pre20 - 2004-01-30
28270 - We now have a deb package, and it's in debian unstable. Go to
28271 it, apt-getters. :)
28272 - I've split the TotalBandwidth option into BandwidthRate (how many
28273 bytes per second you want to allow, long-term) and
28274 BandwidthBurst (how many bytes you will allow at once before the cap
28275 kicks in). This better token bucket approach lets you, say, set
28276 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
28277 performance while not exceeding your monthly bandwidth quota.
28278 - Push out a tls record's worth of data once you've got it, rather
28279 than waiting until you've read everything waiting to be read. This
28280 may improve performance by pipelining better. We'll see.
28281 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
28282 from failed circuits (if they haven't been connected yet) and attach
28284 - Expire old streams that haven't managed to connect. Some day we'll
28285 have them reattach to new circuits instead.
28288 - Fix several memory leaks that were causing servers to become bloated
28290 - Fix a few very rare assert triggers. A few more remain.
28291 - Setuid to User _before_ complaining about running as root.
28294 Changes in version 0.0.2pre19 - 2004-01-07
28296 - Fix deadlock condition in dns farm. We were telling a child to die by
28297 closing the parent's file descriptor to him. But newer children were
28298 inheriting the open file descriptor from the parent, and since they
28299 weren't closing it, the socket never closed, so the child never read
28300 eof, so he never knew to exit. Similarly, dns workers were holding
28301 open other sockets, leading to all sorts of chaos.
28302 - New cleaner daemon() code for forking and backgrounding.
28303 - If you log to a file, it now prints an entry at the top of the
28304 logfile so you know it's working.
28305 - The onionskin challenge length was 30 bytes longer than necessary.
28306 - Started to patch up the spec so it's not quite so out of date.
28309 Changes in version 0.0.2pre18 - 2004-01-02
28311 - Fix endian issues with the 'integrity' field in the relay header.
28312 - Fix a potential bug where connections in state
28313 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
28316 Changes in version 0.0.2pre17 - 2003-12-30
28318 - Made --debuglogfile (or any second log file, actually) work.
28319 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
28320 adversary could force us into an infinite loop.
28323 - Each onionskin handshake now includes a hash of the computed key,
28324 to prove the server's identity and help perfect forward secrecy.
28325 - Changed cell size from 256 to 512 bytes (working toward compatibility
28327 - Changed cell length to 2 bytes, and moved it to the relay header.
28328 - Implemented end-to-end integrity checking for the payloads of
28330 - Separated streamid from 'recognized' (otherwise circuits will get
28331 messed up when we try to have streams exit from the middle). We
28332 use the integrity-checking to confirm that a cell is addressed to
28334 - Randomize the initial circid and streamid values, so an adversary who
28335 breaks into a node can't learn how many circuits or streams have
28339 Changes in version 0.0.2pre16 - 2003-12-14
28341 - Fixed a bug that made HUP trigger an assert
28342 - Fixed a bug where a circuit that immediately failed wasn't being
28343 counted as a failed circuit in counting retries.
28346 - Now we close the circuit when we get a truncated cell: otherwise we're
28347 open to an anonymity attack where a bad node in the path truncates
28348 the circuit and then we open streams at him.
28349 - Add port ranges to exit policies
28350 - Add a conservative default exit policy
28351 - Warn if you're running tor as root
28352 - on HUP, retry OR connections and close/rebind listeners
28353 - options.EntryNodes: try these nodes first when picking the first node
28354 - options.ExitNodes: if your best choices happen to include any of
28355 your preferred exit nodes, you choose among just those preferred
28357 - options.ExcludedNodes: nodes that are never picked in path building
28360 Changes in version 0.0.2pre15 - 2003-12-03
28361 o Robustness and bugfixes:
28362 - Sometimes clients would cache incorrect DNS resolves, which would
28363 really screw things up.
28364 - An OP that goes offline would slowly leak all its sockets and stop
28366 - A wide variety of bugfixes in exit node selection, exit policy
28367 handling, and processing pending streams when a new circuit is
28369 - Pick nodes for a path only from those the directory says are up
28370 - Choose randomly from all running dirservers, not always the first one
28371 - Increase allowed http header size for directory fetch.
28372 - Stop writing to stderr (if we're daemonized it will be closed).
28373 - Enable -g always, so cores will be more useful to me.
28374 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
28377 - Wrote a man page. It lists commonly used options.
28380 - Change default loglevel to warn.
28381 - Make PidFile default to null rather than littering in your CWD.
28382 - OnionRouter config option is now obsolete. Instead it just checks
28384 - Moved to a single unified torrc file for both clients and servers.
28387 Changes in version 0.0.2pre14 - 2003-11-29
28388 o Robustness and bugfixes:
28389 - Force the admin to make the DataDirectory himself
28390 - to get ownership/permissions right
28391 - so clients no longer make a DataDirectory and then never use it
28392 - fix bug where a client who was offline for 45 minutes would never
28393 pull down a directory again
28394 - fix (or at least hide really well) the dns assert bug that was
28395 causing server crashes
28396 - warnings and improved robustness wrt clockskew for certs
28397 - use the native daemon(3) to daemonize, when available
28398 - exit if bind() fails
28399 - exit if neither socksport nor orport is defined
28400 - include our own tor_timegm (Win32 doesn't have its own)
28401 - bugfix for win32 with lots of connections
28402 - fix minor bias in PRNG
28403 - make dirserver more robust to corrupt cached directory
28406 - Wrote the design document (woo)
28408 o Circuit building and exit policies:
28409 - Circuits no longer try to use nodes that the directory has told them
28411 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
28412 bitcounts (18.0.0.0/8).
28413 - Make AP connections standby for a circuit if no suitable circuit
28414 exists, rather than failing
28415 - Circuits choose exit node based on addr/port, exit policies, and
28416 which AP connections are standing by
28417 - Bump min pathlen from 2 to 3
28418 - Relay end cells have a payload to describe why the stream ended.
28419 - If the stream failed because of exit policy, try again with a new
28421 - Clients have a dns cache to remember resolved addresses.
28422 - Notice more quickly when we have no working circuits
28425 - APPort is now called SocksPort
28426 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
28428 - RecommendedVersions is now a config variable rather than
28429 hardcoded (for dirservers)
28430 - Reloads config on HUP
28431 - Usage info on -h or --help
28432 - If you set User and Group config vars, it'll setu/gid to them.
28435 Changes in version 0.0.2pre13 - 2003-10-19
28436 o General stability:
28437 - SSL_write no longer fails when it returns WANTWRITE and the number
28438 of bytes in the buf has changed by the next SSL_write call.
28439 - Fix segfault fetching directory when network is down
28440 - Fix a variety of minor memory leaks
28441 - Dirservers reload the fingerprints file on HUP, so I don't have
28442 to take down the network when I approve a new router
28443 - Default server config file has explicit Address line to specify fqdn
28446 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
28447 - Make listener connections not ever alloc bufs
28449 o Autoconf improvements:
28450 - don't clobber an external CFLAGS in ./configure
28451 - Make install now works
28452 - create var/lib/tor on make install
28453 - autocreate a tor.sh initscript to help distribs
28454 - autocreate the torrc and sample-server-torrc with correct paths
28456 o Log files and Daemonizing now work:
28457 - If --DebugLogFile is specified, log to it at -l debug
28458 - If --LogFile is specified, use it instead of commandline
28459 - If --RunAsDaemon is set, tor forks and backgrounds on startup