1 Changes in version 0.3.3.8 - 2018-07-09
2 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
3 fixes for a memory leak affecting directory authorities.
5 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
6 - Stop leaking memory on directory authorities when planning to
7 vote. This bug was crashing authorities by exhausting their
8 memory. Fixes bug 26435; bugfix on 0.3.3.6.
10 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
11 - Make sure that failing tests in Rust will actually cause the build
12 to fail: previously, they were ignored. Fixes bug 26258; bugfix
15 o Minor features (compilation, backport from 0.3.4.4-rc):
16 - When building Tor, prefer to use Python 3 over Python 2, and more
17 recent (contemplated) versions over older ones. Closes
20 o Minor features (geoip):
21 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
22 Country database. Closes ticket 26674.
24 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
25 - Add several checks to detect whether Tor relays are uploading
26 their descriptors without specifying why they regenerated them.
27 Diagnostic for ticket 25686.
29 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
30 - Don't count path selection failures as circuit build failures.
31 This change should eliminate cases where Tor blames its guard or
32 the network for situations like insufficient microdescriptors
33 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
36 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
37 - Fix a compilation warning on some versions of GCC when building
38 code that calls routerinfo_get_my_routerinfo() twice, assuming
39 that the second call will succeed if the first one did. Fixes bug
40 26269; bugfix on 0.2.8.2-alpha.
42 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
43 - Handle the HSADDRESS= argument to the HSPOST command properly.
44 (Previously, this argument was misparsed and thus ignored.) Fixes
45 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
47 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
48 - Fix a number of small memory leaks identified by coverity. Fixes
49 bug 26467; bugfix on numerous Tor versions.
51 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
52 - Relays now correctly block attempts to re-extend to the previous
53 relay by Ed25519 identity. Previously they would warn in this
54 case, but not actually reject the attempt. Fixes bug 26158; bugfix
57 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
58 - When shutting down, Tor now clears all the flags in the control.c
59 module. This should prevent a bug where authentication cookies are
60 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
62 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
63 - When running the hs_ntor_ref.py test, make sure only to pass
64 strings (rather than "bytes" objects) to the Python subprocess
65 module. Python 3 on Windows seems to require this. Fixes bug
66 26535; bugfix on 0.3.1.1-alpha.
67 - When running the ntor_ref.py test, make sure only to pass strings
68 (rather than "bytes" objects) to the Python subprocess module.
69 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
73 Changes in version 0.3.4.4-rc - 2018-07-09
74 Tor 0.3.4.4-rc fixes several small compilation, portability, and
75 correctness issues in previous versions of Tor. This version is a
76 release candidate: if no serious bugs are found, we expect that the
77 stable 0.3.4 release will be (almost) the same as this release.
79 o Minor features (compilation):
80 - When building Tor, prefer to use Python 3 over Python 2, and more
81 recent (contemplated) versions over older ones. Closes
84 o Minor features (geoip):
85 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
86 Country database. Closes ticket 26674.
88 o Minor features (Rust, portability):
89 - Rust cross-compilation is now supported. Closes ticket 25895.
91 o Minor bugfixes (compilation):
92 - Fix a compilation warning on some versions of GCC when building
93 code that calls routerinfo_get_my_routerinfo() twice, assuming
94 that the second call will succeed if the first one did. Fixes bug
95 26269; bugfix on 0.2.8.2-alpha.
97 o Minor bugfixes (control port):
98 - Report the port correctly when a port is configured to bind to
99 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
100 - Handle the HSADDRESS= argument to the HSPOST command properly.
101 (Previously, this argument was misparsed and thus ignored.) Fixes
102 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
104 o Minor bugfixes (correctness, flow control):
105 - Upon receiving a stream-level SENDME cell, verify that our window
106 has not grown too large. Fixes bug 26214; bugfix on svn
109 o Minor bugfixes (memory, correctness):
110 - Fix a number of small memory leaks identified by coverity. Fixes
111 bug 26467; bugfix on numerous Tor versions.
113 o Minor bugfixes (testing, compatibility):
114 - When running the hs_ntor_ref.py test, make sure only to pass
115 strings (rather than "bytes" objects) to the Python subprocess
116 module. Python 3 on Windows seems to require this. Fixes bug
117 26535; bugfix on 0.3.1.1-alpha.
118 - When running the ntor_ref.py test, make sure only to pass strings
119 (rather than "bytes" objects) to the Python subprocess module.
120 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
124 Changes in version 0.3.4.3-alpha - 2018-06-26
125 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
126 one that was causing stability issues on directory authorities.
128 o Major bugfixes (directory authority):
129 - Stop leaking memory on directory authorities when planning to
130 vote. This bug was crashing authorities by exhausting their
131 memory. Fixes bug 26435; bugfix on 0.3.3.6.
133 o Major bugfixes (rust, testing):
134 - Make sure that failing tests in Rust will actually cause the build
135 to fail: previously, they were ignored. Fixes bug 26258; bugfix
138 o Minor feature (directory authorities):
139 - Stop warning about incomplete bw lines before the first complete
140 bw line has been found, so that additional header lines can be
141 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
143 o Minor features (relay, diagnostic):
144 - Add several checks to detect whether Tor relays are uploading
145 their descriptors without specifying why they regenerated them.
146 Diagnostic for ticket 25686.
148 o Minor features (unit tests):
149 - Test complete bandwidth measurements files, and test that
150 incomplete bandwidth lines only give warnings when the end of the
151 header has not been detected. Fixes bug 25947; bugfix
154 o Minor bugfixes (compilation):
155 - Refrain from compiling unit testing related object files when
156 --disable-unittests is set to configure script. Fixes bug 24891;
157 bugfix on 0.2.5.1-alpha.
158 - When linking the libtor_testing.a library, only include the
159 dirauth object files once. Previously, they were getting added
160 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
161 - The --enable-fatal-warnings flag now affects Rust code as well.
164 o Minor bugfixes (onion services):
165 - Recompute some consensus information after detecting a clock jump,
166 or after transitioning from a non-live consensus to a live
167 consensus. We do this to avoid having an outdated state, and
168 miscalculating the index for next-generation onion services. Fixes
169 bug 24977; bugfix on 0.3.2.1-alpha.
171 o Minor bugfixes (relay):
172 - Relays now correctly block attempts to re-extend to the previous
173 relay by Ed25519 identity. Previously they would warn in this
174 case, but not actually reject the attempt. Fixes bug 26158; bugfix
177 o Minor bugfixes (testing):
178 - Fix compilation of the doctests in the Rust crypto crate. Fixes
179 bug 26415; bugfix on 0.3.4.1-alpha.
180 - Instead of trying to read the geoip configuration files from
181 within the unit tests, instead create our own ersatz files with
182 just enough geoip data in the format we expect. Trying to read
183 from the source directory created problems on Windows with mingw,
184 where the build system's paths are not the same as the platform's
185 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
186 - Refrain from trying to get an item from an empty smartlist in
187 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
188 to catch improper smartlist usage. Furthermore, enable
189 DEBUG_SMARTLIST globally when build is configured with fragile
190 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
193 Changes in version 0.3.3.7 - 2018-06-12
194 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
195 fixes for bugs affecting compatibility and stability.
197 o Directory authority changes:
198 - Add an IPv6 address for the "dannenberg" directory authority.
201 o Minor features (geoip):
202 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
203 Country database. Closes ticket 26351.
205 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
206 - Work around a change in OpenSSL 1.1.1 where return values that
207 would previously indicate "no password" now indicate an empty
208 password. Without this workaround, Tor instances running with
209 OpenSSL 1.1.1 would accept descriptors that other Tor instances
210 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
212 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
213 - Silence unused-const-variable warnings in zstd.h with some GCC
214 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
216 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
217 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
218 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
219 miscounting the total number of circuits for these field values.)
220 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
222 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
223 - Prevent a possible out-of-bounds smartlist read in
224 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
226 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
227 - Only select relays when they have the descriptors we prefer to use
228 for them. This change fixes a bug where we could select a relay
229 because it had _some_ descriptor, but reject it later with a
230 nonfatal assertion error because it didn't have the exact one we
231 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
234 Changes in version 0.3.4.2-alpha - 2018-06-12
235 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
236 release, and forward-ports an authority-only security fix from 0.3.3.6.
238 o Directory authority changes:
239 - Add an IPv6 address for the "dannenberg" directory authority.
242 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
243 - Fix a bug that could have allowed an attacker to force a directory
244 authority to use up all its RAM by passing it a maliciously
245 crafted protocol versions string. Fixes bug 25517; bugfix on
246 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
248 o Minor features (continuous integration):
249 - Add the necessary configuration files for continuous integration
250 testing on Windows, via the Appveyor platform. Closes ticket
251 25549. Patches from Marcin Cieślak and Isis Lovecruft.
253 o Minor features (geoip):
254 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
255 Country database. Closes ticket 26351.
257 o Minor bugfixes (compatibility, openssl):
258 - Work around a change in OpenSSL 1.1.1 where return values that
259 would previously indicate "no password" now indicate an empty
260 password. Without this workaround, Tor instances running with
261 OpenSSL 1.1.1 would accept descriptors that other Tor instances
262 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
264 o Minor bugfixes (compilation):
265 - Silence unused-const-variable warnings in zstd.h with some GCC
266 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
267 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
268 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
269 - Avoid a compiler warning when casting the return value of
270 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
271 26283; bugfix on 0.2.4.10-alpha.
273 o Minor bugfixes (control port):
274 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
275 CIRC_BW events. Previously, such cells were counted entirely in
276 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
279 o Minor bugfixes (controller):
280 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
281 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
282 miscounting the total number of circuits for these field values.)
283 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
285 o Minor bugfixes (hardening):
286 - Prevent a possible out-of-bounds smartlist read in
287 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
289 o Minor bugfixes (onion services):
290 - Fix a bug that blocked the creation of ephemeral v3 onion
291 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
293 o Minor bugfixes (test coverage tools):
294 - Update our "cov-diff" script to handle output from the latest
295 version of gcov, and to remove extraneous timestamp information
296 from its output. Fixes bugs 26101 and 26102; bugfix
300 Changes in version 0.3.3.6 - 2018-05-22
301 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
302 backports several important fixes from the 0.3.4.1-alpha.
304 The Tor 0.3.3 series includes controller support and other
305 improvements for v3 onion services, official support for embedding Tor
306 within other applications, and our first non-trivial module written in
307 the Rust programming language. (Rust is still not enabled by default
308 when building Tor.) And as usual, there are numerous other smaller
309 bugfixes, features, and improvements.
311 Below are the changes since 0.3.3.5-rc. For a list of all changes
312 since 0.3.2.10, see the ReleaseNotes file.
314 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
315 - When directory authorities read a zero-byte bandwidth file, they
316 would previously log a warning with the contents of an
317 uninitialised buffer. They now log a warning about the empty file
318 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
320 o Major bugfixes (security, directory authority, denial-of-service):
321 - Fix a bug that could have allowed an attacker to force a directory
322 authority to use up all its RAM by passing it a maliciously
323 crafted protocol versions string. Fixes bug 25517; bugfix on
324 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
326 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
327 - Avoid a rare assertion failure in the circuit build timeout code
328 if we fail to allow any circuits to actually complete. Fixes bug
329 25733; bugfix on 0.2.2.2-alpha.
331 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
332 - Avoid a crash when testing router reachability on a router that
333 could have an ed25519 ID, but which does not. Fixes bug 25415;
334 bugfix on 0.3.3.2-alpha.
336 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
337 - Correctly detect when onion services get disabled after HUP. Fixes
338 bug 25761; bugfix on 0.3.2.1.
340 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
341 - Impose a limit on circuit cell queue size. The limit can be
342 controlled by a consensus parameter. Fixes bug 25226; bugfix
345 o Minor features (compatibility, backport from 0.3.4.1-alpha):
346 - Avoid some compilation warnings with recent versions of LibreSSL.
349 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
350 - Our .travis.yml configuration now includes support for testing the
351 results of "make distcheck". (It's not uncommon for "make check"
352 to pass but "make distcheck" to fail.) Closes ticket 25814.
353 - Our Travis CI configuration now integrates with the Coveralls
354 coverage analysis tool. Closes ticket 25818.
356 o Minor features (geoip):
357 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
358 database. Closes ticket 26104.
360 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
361 - Don't consider Tor running as a client if the ControlPort is open,
362 but no actual client ports are open. Fixes bug 26062; bugfix
365 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
366 - Upon receiving a malformed connected cell, stop processing the
367 cell immediately. Previously we would mark the connection for
368 close, but continue processing the cell as if the connection were
369 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
371 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
372 - Stop saying in the manual that clients cache ipv4 dns answers from
373 exit relays. We haven't used them since 0.2.6.3-alpha, and in
374 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
375 we forgot to say so in the man page. Fixes bug 26052; bugfix
378 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
379 - Allow the nanosleep() system call, which glibc uses to implement
380 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
382 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
383 - Fix a memory leak when a v3 onion service is configured and gets a
384 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
385 - When parsing the descriptor signature, look for the token plus an
386 extra white-space at the end. This is more correct but also will
387 allow us to support new fields that might start with "signature".
388 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
390 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
391 - Avoid a crash when running with DirPort set but ORPort tuned off.
392 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
394 o Documentation (backport from 0.3.4.1-alpha):
395 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
396 ticket 25857. Patch from "CTassisF".
399 Changes in version 0.3.4.1-alpha - 2018-05-17
400 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
401 includes refactoring to begin reducing Tor's binary size and idle CPU
402 usage on mobile, along with prep work for new bandwidth scanners,
403 improvements to the experimental "vanguards" feature, and numerous
404 other small features and bugfixes.
406 o New system requirements:
407 - Tor no longer tries to support old operating systems without
408 mmap() or some local equivalent. Apparently, compilation on such
409 systems has been broken for some time, without anybody noticing or
410 complaining. Closes ticket 25398.
412 o Major feature (directory authority, modularization):
413 - The directory authority subsystem has been modularized. The code
414 is now located in src/or/dirauth/, and is compiled in by default.
415 To disable the module, the configure option
416 --disable-module-dirauth has been added. This module may be
417 disabled by default in some future release. Closes ticket 25610.
419 o Major features (main loop, CPU usage):
420 - When Tor is disabled (via DisableNetwork or via hibernation), it
421 no longer needs to run any per-second events. This change should
422 make it easier for mobile applications to disable Tor while the
423 device is sleeping, or Tor is not running. Closes ticket 26063.
424 - Tor no longer enables all of its periodic events by default.
425 Previously, Tor would enable all possible main loop events,
426 regardless of whether it needed them. Furthermore, many of these
427 events are now disabled with Tor is hibernating or DisableNetwork
428 is set. This is a big step towards reducing client CPU usage by
429 reducing the amount of wake-ups the daemon does. Closes ticket
431 - The bandwidth-limitation logic has been refactored so that
432 bandwidth calculations are performed on-demand, rather than every
433 TokenBucketRefillInterval milliseconds. This change should improve
434 the granularity of our bandwidth calculations, and limit the
435 number of times that the Tor process needs to wake up when it is
436 idle. Closes ticket 25373.
437 - Move responsibility for many operations from a once-per-second
438 callback to a callback that is only scheduled as needed. Moving
439 this functionality has allowed us to disable the callback when
440 Tor's network is disabled. Once enough items are removed from our
441 once-per-second callback, we can eliminate it entirely to conserve
442 CPU when idle. The functionality removed includes: closing
443 connections, circuits, and channels (ticket 25932); consensus
444 voting (25937); flushing log callbacks (25951); honoring delayed
445 SIGNEWNYM requests (25949); rescanning the consensus cache
446 (25931); saving the state file to disk (25948); warning relay
447 operators about unreachable ports (25952); and keeping track of
448 Tor's uptime (26009).
450 o Major bugfixes (directory authorities, security):
451 - When directory authorities read a zero-byte bandwidth file, they
452 would previously log a warning with the contents of an
453 uninitialised buffer. They now log a warning about the empty file
454 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
456 o Major bugfixes (crash):
457 - Avoid a rare assertion failure in the circuit build timeout code
458 if we fail to allow any circuits to actually complete. Fixes bug
459 25733; bugfix on 0.2.2.2-alpha.
461 o Major bugfixes (directory authority):
462 - Avoid a crash when testing router reachability on a router that
463 could have an ed25519 ID, but which does not. Fixes bug 25415;
464 bugfix on 0.3.3.2-alpha.
466 o Major bugfixes (onion service):
467 - Correctly detect when onion services get disabled after HUP. Fixes
468 bug 25761; bugfix on 0.3.2.1.
470 o Major bugfixes (protover, voting):
471 - Revise Rust implementation of protover to use a more memory-
472 efficient voting algorithm and corresponding data structures, thus
473 avoiding a potential (but small impact) DoS attack where specially
474 crafted protocol strings would expand to several potential
475 megabytes in memory. In the process, several portions of code were
476 revised to be methods on new, custom types, rather than functions
477 taking interchangeable types, thus increasing type safety of the
478 module. Custom error types and handling were added as well, in
479 order to facilitate better error dismissal/handling in outside
480 crates and avoid mistakenly passing an internal error string to C
481 over the FFI boundary. Many tests were added, and some previous
482 differences between the C and Rust implementations have been
483 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
485 o Major bugfixes (relay, denial of service):
486 - Impose a limit on circuit cell queue size. The limit can be
487 controlled by a consensus parameter. Fixes bug 25226; bugfix
490 o Minor features (accounting):
491 - When Tor becomes dormant, it now uses a scheduled event to wake up
492 at the right time. Previously, we would use the per-second timer
493 to check whether to wake up, but we no longer have any per-second
494 timers enabled when the network is disabled. Closes ticket 26064.
496 o Minor features (code quality):
497 - Add optional spell-checking for the Tor codebase, using the
498 "misspell" program. To use this feature, run "make check-typos".
501 o Minor features (compatibility):
502 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
503 the no-deprecated option, and builds correctly with them. Closes
504 tickets 19429, 19981, and 25353.
505 - Avoid some compilation warnings with recent versions of LibreSSL.
508 o Minor features (compression, zstd):
509 - When running with zstd, Tor now considers using advanced functions
510 that the zstd maintainers have labeled as potentially unstable. To
511 prevent breakage, Tor will only use this functionality when the
512 runtime version of the zstd library matches the version with which
513 Tor was compiled. Closes ticket 25162.
515 o Minor features (configuration):
516 - The "DownloadSchedule" options have been renamed to end with
517 "DownloadInitialDelay". The old names are still allowed, but will
518 produce a warning. Comma-separated lists are still permitted for
519 these options, but all values after the first are ignored (as they
520 have been since 0.2.9). Closes ticket 23354.
522 o Minor features (continuous integration):
523 - Our .travis.yml configuration now includes support for testing the
524 results of "make distcheck". (It's not uncommon for "make check"
525 to pass but "make distcheck" to fail.) Closes ticket 25814.
526 - Our Travis CI configuration now integrates with the Coveralls
527 coverage analysis tool. Closes ticket 25818.
529 o Minor features (control port):
530 - Introduce GETINFO "current-time/{local,utc}" to return the local
531 and UTC times respectively in ISO format. This helps a controller
532 like Tor Browser detect a time-related error. Closes ticket 25511.
533 Patch by Neel Chauhan.
534 - Introduce new fields to the CIRC_BW event. There are two new
535 fields in each of the read and written directions. The DELIVERED
536 fields report the total valid data on the circuit, as measured by
537 the payload sizes of verified and error-checked relay command
538 cells. The OVERHEAD fields report the total unused bytes in each
539 of these cells. Closes ticket 25903.
541 o Minor features (directory authority):
542 - Directory authorities now open their key-pinning files as O_SYNC,
543 to limit their chances of accidentally writing partial lines.
546 o Minor features (directory authority, forward compatibility):
547 - Make the lines of the measured bandwidth file able to contain
548 their entries in any order. Previously, the node_id entry needed
549 to come first. Closes ticket 26004.
551 o Minor features (entry guards):
552 - Introduce a new torrc option NumPrimaryGuards for controlling the
553 number of primary guards. Closes ticket 25843.
555 o Minor features (geoip):
556 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
557 database. Closes ticket 26104.
559 o Minor features (performance):
560 - Avoid a needless call to malloc() when processing an incoming
561 relay cell. Closes ticket 24914.
562 - Make our timing-wheel code run a tiny bit faster on 32-bit
563 platforms, by preferring 32-bit math to 64-bit. Closes
565 - Avoid a needless malloc()/free() pair every time we handle an ntor
566 handshake. Closes ticket 25150.
568 o Minor features (testing):
569 - Add a unit test for voting_schedule_get_start_of_next_interval().
570 Closes ticket 26014, and helps make unit test coverage
572 - A new unittests module specifically for testing the functions in
573 the (new-ish) bridges.c module has been created with new
574 unittests, raising the code coverage percentages. Closes 25425.
575 - We now have improved testing for addressmap_get_virtual_address()
576 function. This should improve our test coverage, and make our test
577 coverage more deterministic. Closes ticket 25993.
579 o Minor features (timekeeping, circuit scheduling):
580 - When keeping track of how busy each circuit have been recently on
581 a given connection, use coarse-grained monotonic timers rather
582 than gettimeofday(). This change should marginally increase
583 accuracy and performance. Implements part of ticket 25927.
585 o Minor bugfixes (bandwidth management):
586 - Consider ourselves "low on write bandwidth" if we have exhausted
587 our write bandwidth some time in the last second. This was the
588 documented behavior before, but the actual behavior was to change
589 this value every TokenBucketRefillInterval. Fixes bug 25828;
590 bugfix on 0.2.3.5-alpha.
592 o Minor bugfixes (C correctness):
593 - Add a missing lock acquisition in the shutdown code of the control
594 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
595 Coverity; this is CID 1433643.
597 o Minor bugfixes (circuit path selection):
598 - Don't count path selection failures as circuit build failures.
599 This change should eliminate cases where Tor blames its guard or
600 the network for situations like insufficient microdescriptors
601 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
604 o Minor bugfixes (client):
605 - Don't consider Tor running as a client if the ControlPort is open,
606 but no actual client ports are open. Fixes bug 26062; bugfix
609 o Minor bugfixes (code style):
610 - Fixed multiple includes of transports.h in src/or/connection.c
611 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
612 - Remove the unused variable n_possible from the function
613 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
615 o Minor bugfixes (control interface):
616 - Respond with more human-readable error messages to GETINFO exit-
617 policy/* requests. Also, let controller know if an error is
618 transient (response code 551) or not (response code 552). Fixes
619 bug 25852; bugfix on 0.2.8.1-alpha.
621 o Minor bugfixes (controller):
622 - Make CIRC_BW event reflect the total of all data sent on a
623 circuit, including padding and dropped cells. Also fix a mis-
624 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
625 bugfix on 0.2.5.2-alpha.
627 o Minor bugfixes (correctness, client):
628 - Upon receiving a malformed connected cell, stop processing the cell
629 immediately. Previously we would mark the connection for close, but
630 continue processing the cell as if the connection were open. Fixes bug
631 26072; bugfix on 0.2.4.7-alpha.
633 o Minor bugfixes (directory client):
634 - When unverified-consensus is verified, rename it to cached-
635 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
636 - Fixed launching a certificate fetch always during the scheduled
637 periodic consensus fetch by fetching only in those cases when
638 consensus are waiting for certs. Fixes bug 24740; bugfix
641 o Minor bugfixes (documentation):
642 - Stop saying in the manual that clients cache ipv4 dns answers from
643 exit relays. We haven't used them since 0.2.6.3-alpha, and in
644 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
645 we forgot to say so in the man page. Fixes bug 26052; bugfix
648 o Minor bugfixes (error reporting):
649 - Improve tolerance for directory authorities with skewed clocks.
650 Previously, an authority with a clock more than 60 seconds ahead
651 could cause a client with a correct clock to warn that the
652 client's clock was behind. Now the clocks of a majority of
653 directory authorities have to be ahead of the client before this
654 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
656 o Minor bugfixes (Linux seccomp2 sandbox):
657 - Allow the nanosleep() system call, which glibc uses to implement
658 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
660 o Minor bugfixes (onion service):
661 - Fix a memory leak when a v3 onion service is configured and gets a
662 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
663 - When parsing the descriptor signature, look for the token plus an
664 extra white-space at the end. This is more correct but also will
665 allow us to support new fields that might start with "signature".
666 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
668 o Minor bugfixes (path selection):
669 - Only select relays when they have the descriptors we prefer to use
670 for them. This change fixes a bug where we could select a relay
671 because it had _some_ descriptor, but reject it later with a
672 nonfatal assertion error because it didn't have the exact one we
673 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
675 o Minor bugfixes (portability):
676 - Do not align mmap length, as it is not required by POSIX, and the
677 getpagesize function is deprecated. Fixes bug 25399; bugfix
680 o Minor bugfixes (portability, FreeBSD):
681 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
682 does not stringify on FreeBSD, so we switch to tor_asprintf().
683 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
685 o Minor bugfixes (relay statistics):
686 - When a relay is collecting internal statistics about how many
687 create cell requests it has seen of each type, accurately count
688 the requests from relays that temporarily fall out of the
689 consensus. (To be extra conservative, we were already ignoring
690 requests from clients in our counts, and we continue ignoring them
691 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
693 o Minor bugfixes (relay, crash):
694 - Avoid a crash when running with DirPort set but ORPort tuned off.
695 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
697 o Minor bugfixes (restart-in-process):
698 - When shutting down, Tor now clears all the flags in the control.c
699 module. This should prevent a bug where authentication cookies are
700 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
702 o Minor bugfixes (testing):
703 - When testing workqueue event-cancellation, make sure that we
704 actually cancel an event, and that cancel each event with equal
705 probability. (It was previously possible, though extremely
706 unlikely, for our event-canceling test not to cancel any events.)
707 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
708 - Repeat part of the test in test_client_pick_intro() a number of
709 times, to give it consistent coverage. Fixes bug 25996; bugfix
711 - Remove randomness from the hs_common/responsible_hsdirs test, so
712 that it always takes the same path through the function it tests.
713 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
714 - Change the behavior of the "channel/outbound" test so that it
715 never causes a 10-second rollover for the EWMA circuitmux code.
716 Previously, this behavior would happen randomly, and result in
717 fluctuating test coverage. Fixes bug 25994; bugfix
719 - Use X509_new() to allocate certificates that will be freed later
720 with X509_free(). Previously, some parts of the unit tests had
721 used tor_malloc_zero(), which is incorrect, and which caused test
722 failures on Windows when they were built with extra hardening.
723 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
725 - While running the circuit_timeout test, fix the PRNG to a
726 deterministic AES stream, so that the test coverage from this test
727 will itself be deterministic. Fixes bug 25995; bugfix
730 o Minor bugfixes (vanguards):
731 - Allow the last hop in a vanguard circuit to be the same as our
732 first, to prevent the adversary from influencing guard node choice
733 by choice of last hop. Also prevent the creation of A - B - A
734 paths, or A - A paths, which are forbidden by relays. Fixes bug
735 25870; bugfix on 0.3.3.1-alpha.
737 o Code simplification and refactoring:
738 - Remove duplicate code in parse_{c,s}method_line and bootstrap
739 their functionalities into a single function. Fixes bug 6236;
740 bugfix on 0.2.3.6-alpha.
741 - We remove the PortForwsrding and PortForwardingHelper options,
742 related functions, and the port_forwarding tests. These options
743 were used by the now-deprecated Vidalia to help ordinary users
744 become Tor relays or bridges. Closes ticket 25409. Patch by
746 - In order to make the OR and dir checking function in router.c less
747 confusing we renamed some functions and
748 consider_testing_reachability() has been split into
749 router_should_check_reachability() and
750 router_do_reachability_checks(). Also we improved the documentation
751 in some functions. Closes ticket 18918.
752 - Initial work to isolate Libevent usage to a handful of modules in
753 our codebase, to simplify our call structure, and so that we can
754 more easily change event loops in the future if needed. Closes
756 - Introduce a function to call getsockname() and return tor_addr_t,
757 to save a little complexity throughout the codebase. Closes
759 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
760 as hsdir_index is always present. Also, we move hsdir_index_t into
761 or.h. Closes ticket 23094. Patch by Neel Chauhan.
762 - Merge functions used for describing nodes and suppress the
763 functions that do not allocate memory for the output buffer
764 string. NODE_DESC_BUF_LEN constant and format_node_description()
765 function cannot be used externally from router.c module anymore.
766 Closes ticket 25432. Patch by valentecaio.
767 - Our main loop has been simplified so that all important operations
768 happen inside events. Previously, some operations had to happen
769 outside the event loop, to prevent infinite sequences of event
770 activations. Closes ticket 25374.
771 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
772 it in register_intro_circ() and service_intro_point_new(). This
773 prevents the digest from being re-calculated each time. Closes
774 ticket 23107. Patch by Neel Chauhan.
775 - Refactor token-bucket implementations to use a common backend.
777 - Remove extern declaration of stats_n_seconds_working variable from
778 main, protecting its accesses with get_uptime() and reset_uptime()
779 functions. Closes ticket 25081, patch by “valentecaio”.
780 - Remove our previous logic for "cached gettimeofday()" -- our
781 coarse monotonic timers are fast enough for this purpose, and far
782 less error-prone. Implements part of ticket 25927.
783 - Remove the return value for fascist_firewall_choose_address_base(),
784 and sister functions such as fascist_firewall_choose_address_node()
785 and fascist_firewall_choose_address_rs(). Also, while we're here,
786 initialize the ap argument as leaving it uninitialized can pose a
787 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
788 - Rename two fields of connection_t struct. timestamp_lastwritten is
789 renamed to timestamp_last_write_allowed and timestamp_lastread is
790 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
792 - Since Tor requires C99, remove our old workaround code for libc
793 implementations where free(NULL) doesn't work. Closes ticket 24484.
794 - Use our standard rate-limiting code to deal with excessive
795 libevent failures, rather than the hand-rolled logic we had
796 before. Closes ticket 26016.
797 - We remove the return value of node_get_prim_orport() and
798 node_get_prim_dirport(), and introduce node_get_prim_orport() in
799 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
800 check for a null address. Closes ticket 23873. Patch by
802 - We switch to should_record_bridge_info() in
803 geoip_note_client_seen() and options_need_geoip_info() instead of
804 accessing the configuration values directly. Fixes bug 25290;
805 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
807 o Deprecated features:
808 - As we are not recommending 0.2.5 anymore, we require relays that
809 once had an ed25519 key associated with their RSA key to always
810 have that key, instead of allowing them to drop back to a version
811 that didn't support ed25519. This means they need to use a new RSA
812 key if the want to downgrade to an older version of tor without
813 ed25519. Closes ticket 20522.
816 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
817 ticket 25857. Patch from "CTassisF".
820 - Directory authorities will no longer support voting according to
821 any consensus method before consensus method 25. This keeps
822 authorities compatible with all authorities running 0.2.9.8 and
823 later, and does not break any clients or relays. Implements ticket
824 24378 and proposal 290.
825 - The PortForwarding and PortForwardingHelper features have been
826 removed. The reasoning is, given that implementations of NAT
827 traversal protocols within common consumer grade routers are
828 frequently buggy, and that the target audience for a NAT punching
829 feature is a perhaps less-technically-inclined relay operator,
830 when the helper fails to setup traversal the problems are usually
831 deep, ugly, and very router specific, making them horrendously
832 impossible for technical support to reliable assist with, and thus
833 resulting in frustration all around. Unfortunately, relay
834 operators who would like to run relays behind NATs will need to
835 become more familiar with the port forwarding configurations on
836 their local router. Closes 25409.
837 - The TestingEnableTbEmptyEvent option has been removed. It was used
838 in testing simulations to measure how often connection buckets
839 were emptied, in order to improve our scheduling, but it has not
840 been actively used in years. Closes ticket 25760.
841 - The old "round-robin" circuit multiplexer (circuitmux)
842 implementation has been removed, along with a fairly large set of
843 code that existed to support it. It has not been the default
844 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
845 but it still required an unreasonable amount of memory and CPU.
849 Changes in version 0.3.3.5-rc - 2018-04-15
850 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
851 including some that could affect reliability or correctness.
853 This is the first release candidate in the 0.3.3 series. If we find no
854 new bugs or regression here, then the first stable 0.3.3 release will
855 be nearly identical to this one.
857 o Major bugfixes (security, protover, voting):
858 - Revise Rust implementation of protover to use a more memory-
859 efficient voting algorithm and corresponding data structures, thus
860 avoiding a potential memory-based DoS attack where specially
861 crafted protocol strings would expand to fill available memory.
862 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
864 o Major bugfixes (performance, load balancing):
865 - Directory authorities no longer vote in favor of the Guard flag
866 for relays without directory support. Starting in Tor
867 0.3.0.1-alpha, clients have been avoiding using such relays in the
868 Guard position, leading to increasingly broken load balancing for
869 the 5%-or-so of Guards that don't advertise directory support.
870 Fixes bug 22310; bugfix on 0.3.0.6.
872 o Minor feature (continuous integration):
873 - Update the Travis CI configuration to use the stable Rust channel,
874 now that we have decided to require that. Closes ticket 25714.
876 o Minor features (config options):
877 - Change the way the default value for MaxMemInQueues is calculated.
878 We now use 40% of the hardware RAM if the system has 8 GB RAM or
879 more. Otherwise we use the former value of 75%. Closes
882 o Minor features (geoip):
883 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
884 Country database. Closes ticket 25718.
886 o Minor bugfixes (client):
887 - When using a listed relay as a bridge, and also using
888 microdescriptors, and considering that relay as a non-bridge in a
889 circuit, treat its microdescriptor as a valid source of
890 information about that relay. This change should prevent a non-
891 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
893 o Minor bugfixes (controller):
894 - Restore the correct operation of the RESOLVE command, which had
895 been broken since we added the ability to enable/disable DNS on
896 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
898 o Minor bugfixes (distribution, compilation, rust):
899 - Build correctly when the rust dependencies submodule is loaded,
900 but the TOR_RUST_DEPENDENCIES environment variable is not set.
901 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
902 - Actually include all of our Rust source in our source
903 distributions. (Previously, a few of the files were accidentally
904 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
906 o Minor bugfixes (documentation):
907 - Document that the PerConnBW{Rate,Burst} options will fall back to
908 their corresponding consensus parameters only if those parameters
909 are set. Previously we had claimed that these values would always
910 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
911 - Revert a misformatting issue in the ExitPolicy documentation.
912 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
914 o Minor bugfixes (exit relay DNS retries):
915 - Re-attempt timed-out DNS queries 3 times before failure, since our
916 timeout is 5 seconds for them, but clients wait 10-15. Also allow
917 slightly more timeouts per resolver when an exit has multiple
918 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
920 o Minor bugfixes (onion services):
921 - Re-instate counting the client HSDir fetch circuits against the
922 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
924 - Remove underscores from the _HSLayer{2,3}Nodes options. This
925 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
926 Fixes bug 25581; bugfix on 0.3.3.1-alpha
928 o Code simplification and refactoring:
929 - Move the list of default directory authorities to its own file.
930 Closes ticket 24854. Patch by "beastr0".
932 o Documentation (manpage, denial of service):
933 - Provide more detail about the denial-of-service options, by
934 listing each mitigation and explaining how they relate. Closes
938 Changes in version 0.3.3.4-alpha - 2018-03-29
939 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
940 the alpha testing of earlier releases in its series. We are
941 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
943 o New system requirements:
944 - When built with Rust, Tor now depends on version 0.2.39 of the
945 libc crate. Closes tickets 25310 and 25664.
947 o Major bugfixes (relay, connection):
948 - If we have failed to connect to a relay and received a connection
949 refused, timeout, or similar error (at the TCP level), do not try
950 that same address/port again for 60 seconds after the failure has
951 occurred. Fixes bug 24767; bugfix on 0.0.6.
953 o Minor features (geoip):
954 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
955 Country database. Closes ticket 25469.
957 o Minor features (log messages):
958 - Improve log message in the out-of-memory handler to include
959 information about memory usage from the different compression
960 backends. Closes ticket 25372.
962 o Minor features (sandbox):
963 - Explicitly permit the poll() system call when the Linux
964 seccomp2-based sandbox is enabled: apparently, some versions of
965 libc use poll() when calling getpwnam(). Closes ticket 25313.
967 o Minor bugfixes (C correctness):
968 - Fix a very unlikely (impossible, we believe) null pointer
969 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
970 Coverity; this is CID 1430932.
972 o Minor bugfixes (channel, client):
973 - Better identify client connection when reporting to the geoip
974 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
976 o Minor bugfixes (compilation):
977 - Fix a C99 compliance issue in our configuration script that caused
978 compilation issues when compiling Tor with certain versions of
979 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
981 o Minor bugfixes (controller, reliability):
982 - Avoid a (nonfatal) assertion failure when extending a one-hop
983 circuit from the controller to become a multihop circuit. Fixes
984 bug 24903; bugfix on 0.2.5.2-alpha.
986 o Major bugfixes (networking):
987 - Tor will no longer reject IPv6 address strings from Tor Browser
988 when they are passed as hostnames in SOCKS5 requests. Fixes bug
989 25036, bugfix on Tor 0.3.1.2.
991 o Minor bugfixes (networking):
992 - string_is_valid_hostname() will not consider IP strings to be
993 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
995 o Minor bugfixes (onion service v3):
996 - Avoid an assertion failure when the next onion service
997 descriptor rotation type is out of sync with the consensus's
998 valid-after time. Instead, log a warning message with extra
999 information, so we can better hunt down the cause of this
1000 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
1002 o Minor bugfixes (testing):
1003 - Avoid intermittent test failures due to a test that had relied on
1004 onion service introduction point creation finishing within 5
1005 seconds of real clock time. Fixes bug 25450; bugfix
1007 - Rust crates are now automatically detected and tested. Previously,
1008 some crates were not tested by `make test-rust` due to a static
1009 string in the `src/test/test_rust.sh` script specifying which
1010 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
1012 o Minor bugfixes (testing, benchmarks):
1013 - Fix a crash when running benchmark tests on win32 systems. The
1014 crash was due to a mutex that wasn't initialized before logging
1015 and options were initialized. Fixes bug 25479; bugfix
1018 o Minor bugfixes (warnings, ipv6):
1019 - Avoid a bug warning that could occur when trying to connect to a
1020 relay over IPv6. This warning would occur on a Tor instance that
1021 downloads router descriptors, but prefers to use microdescriptors.
1022 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
1024 o Code simplification and refactoring:
1025 - Remove the old (deterministic) directory retry logic entirely:
1026 We've used exponential backoff exclusively for some time. Closes
1030 - Improved the documentation of AccountingStart parameter. Closes
1032 - Update the documentation for "Log" to include the current list of
1033 logging domains. Closes ticket 25378.
1036 Changes in version 0.3.1.10 - 2018-03-03
1037 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
1040 It includes an important security fix for a remote crash attack
1041 against directory authorities, tracked as TROVE-2018-001.
1043 This release also backports our new system for improved resistance to
1044 denial-of-service attacks against relays.
1046 This release also fixes several minor bugs and annoyances from
1049 All directory authorities should upgrade to one of the versions
1050 released today. Relays running 0.3.1.x may wish to update to one of
1051 the versions released today, for the DoS mitigations.
1053 Please note: according to our release calendar, Tor 0.3.1 will no
1054 longer be supported after 1 July 2018. If you will be running Tor
1055 after that date, you should make sure to plan to upgrade to the latest
1056 stable version, or downgrade to 0.2.9 (which will receive long-term
1059 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1060 - Fix a protocol-list handling bug that could be used to remotely crash
1061 directory authorities with a null-pointer exception. Fixes bug 25074;
1062 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1065 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
1066 - Give relays some defenses against the recent network overload. We
1067 start with three defenses (default parameters in parentheses).
1068 First: if a single client address makes too many concurrent
1069 connections (>100), hang up on further connections. Second: if a
1070 single client address makes circuits too quickly (more than 3 per
1071 second, with an allowed burst of 90) while also having too many
1072 connections open (3), refuse new create cells for the next while
1073 (1-2 hours). Third: if a client asks to establish a rendezvous
1074 point to you directly, ignore the request. These defenses can be
1075 manually controlled by new torrc options, but relays will also
1076 take guidance from consensus parameters, so there's no need to
1077 configure anything manually. Implements ticket 24902.
1079 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
1080 - Update the sandbox rules so that they should now work correctly
1081 with Glibc 2.26. Closes ticket 24315.
1083 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
1084 - Fix an "off by 2" error in counting rendezvous failures on the
1085 onion service side. While we thought we would stop the rendezvous
1086 attempt after one failed circuit, we were actually making three
1087 circuit attempts before giving up. Now switch to a default of 2,
1088 and allow the consensus parameter "hs_service_max_rdv_failures" to
1089 override. Fixes bug 24895; bugfix on 0.0.6.
1091 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
1092 - Add Link protocol version 5 to the supported protocols list. Fixes
1093 bug 25070; bugfix on 0.3.1.1-alpha.
1095 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
1096 - Fix a set of false positives where relays would consider
1097 connections to other relays as being client-only connections (and
1098 thus e.g. deserving different link padding schemes) if those
1099 relays fell out of the consensus briefly. Now we look only at the
1100 initial handshake and whether the connection authenticated as a
1101 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1103 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
1104 - Make our OOM handler aware of the geoip client history cache so it
1105 doesn't fill up the memory. This check is important for IPv6 and
1106 our DoS mitigation subsystem. Closes ticket 25122.
1108 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
1109 - Change relay bandwidth reporting stats interval from 4 hours to 24
1110 hours in order to reduce the efficiency of guard discovery
1111 attacks. Fixes ticket 23856.
1113 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
1114 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1115 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1116 since they neither disabled TLS 1.3 nor enabled any of the
1117 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1118 Closes ticket 24978.
1120 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
1121 - The fallback directory list has been re-generated based on the
1122 current status of the network. Tor uses fallback directories to
1123 bootstrap when it doesn't yet have up-to-date directory
1124 information. Closes ticket 24801.
1125 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1126 prefer to bootstrap from fallback directory mirrors. This is a
1127 follow-up to 24679, which removed weights from the default
1128 fallbacks. Implements ticket 24681.
1130 o Minor features (geoip):
1131 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1134 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
1135 - Use the actual observed address of an incoming relay connection,
1136 not the canonical address of the relay from its descriptor, when
1137 making decisions about how to handle the incoming connection.
1138 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1140 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
1141 - Directory authorities, when refusing a descriptor from a rejected
1142 relay, now explicitly tell the relay (in its logs) to set a valid
1143 ContactInfo address and contact the bad-relays@ mailing list.
1144 Fixes bug 25170; bugfix on 0.2.9.1.
1146 o Minor bugfixes (address selection, backport from 0.3.2.9):
1147 - When the fascist_firewall_choose_address_ functions don't find a
1148 reachable address, set the returned address to the null address
1149 and port. This is a precautionary measure, because some callers do
1150 not check the return value. Fixes bug 24736; bugfix
1153 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
1154 - Fetch descriptors aggressively whenever we lack enough to build
1155 circuits, regardless of how many descriptors we are missing.
1156 Previously, we would delay launching the fetch when we had fewer
1157 than 15 missing descriptors, even if some of those descriptors
1158 were blocking circuits from building. Fixes bug 23985; bugfix on
1159 0.1.1.11-alpha. The effects of this bug became worse in
1160 0.3.0.3-alpha, when we began treating missing descriptors from our
1161 primary guards as a reason to delay circuits.
1162 - Don't try fetching microdescriptors from relays that have failed
1163 to deliver them in the past. Fixes bug 23817; bugfix
1166 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
1167 - Fix a signed/unsigned comparison warning introduced by our fix to
1168 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1170 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
1171 - Avoid a crash when attempting to use the seccomp2 sandbox together
1172 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1175 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1176 - Fix a possible crash on malformed consensus. If a consensus had
1177 contained an unparseable protocol line, it could have made clients
1178 and relays crash with a null-pointer exception. To exploit this
1179 issue, however, an attacker would need to be able to subvert the
1180 directory authority system. Fixes bug 25251; bugfix on
1181 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1183 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
1184 - Recover better from empty or corrupt files in the consensus cache
1185 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
1186 - When a consensus diff calculation is only partially successful,
1187 only record the successful parts as having succeeded. Partial
1188 success can happen if (for example) one compression method fails
1189 but the others succeed. Previously we misrecorded all the
1190 calculations as having succeeded, which would later cause a
1191 nonfatal assertion failure. Fixes bug 24086; bugfix
1194 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
1195 - Tor now updates its guard state when it reads a consensus
1196 regardless of whether it's missing descriptors. That makes tor use
1197 its primary guards to fetch descriptors in some edge cases where
1198 it would previously have used fallback directories. Fixes bug
1199 23862; bugfix on 0.3.0.1-alpha.
1201 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
1202 - Don't treat inability to store a cached consensus object as a bug:
1203 it can happen normally when we are out of disk space. Fixes bug
1204 24859; bugfix on 0.3.1.1-alpha.
1206 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
1207 - When queuing DESTROY cells on a channel, only queue the circuit-id
1208 and reason fields: not the entire 514-byte cell. This fix should
1209 help mitigate any bugs or attacks that fill up these queues, and
1210 free more RAM for other uses. Fixes bug 24666; bugfix
1213 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
1214 - When closing a connection via close_connection_immediately(), we
1215 mark it as "not blocked on bandwidth", to prevent later calls from
1216 trying to unblock it, and give it permission to read. This fixes a
1217 backtrace warning that can happen on relays under various
1218 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1220 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
1221 - When selecting relays by bandwidth, avoid a rounding error that
1222 could sometimes cause load to be imbalanced incorrectly.
1223 Previously, we would always round upwards; now, we round towards
1224 the nearest integer. This had the biggest effect when a relay's
1225 weight adjustments should have given it weight 0, but it got
1226 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1227 - When calculating the fraction of nodes that have descriptors, and
1228 all nodes in the network have zero bandwidths, count the number of
1229 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1230 - Actually log the total bandwidth in compute_weighted_bandwidths().
1231 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1233 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
1234 - Improve the performance of our consensus-diff application code
1235 when Tor is built with the --enable-fragile-hardening option set.
1236 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1238 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
1239 - Don't exit the Tor process if setrlimit() fails to change the file
1240 limit (which can happen sometimes on some versions of OSX). Fixes
1241 bug 21074; bugfix on 0.0.9pre5.
1243 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
1244 - Fix a bug in the bit-counting parts of our timing-wheel code on
1245 MSVC. (Note that MSVC is still not a supported build platform, due
1246 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
1249 o Minor bugfixes (relay, partial backport):
1250 - Make the internal channel_is_client() function look at what sort
1251 of connection handshake the other side used, rather than whether
1252 the other side ever sent a create_fast cell to us. Backports part
1253 of the fixes from bugs 22805 and 24898.
1255 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1256 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1258 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1259 bugfix on 0.2.9.4-alpha.
1261 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
1262 - Update the "rust dependencies" submodule to be a project-level
1263 repository, rather than a user repository. Closes ticket 25323.
1266 Changes in version 0.2.9.15 - 2018-03-03
1267 Tor 0.2.9.15 backports important security and stability bugfixes from
1270 It includes an important security fix for a remote crash attack
1271 against directory authorities, tracked as TROVE-2018-001.
1273 This release also backports our new system for improved resistance to
1274 denial-of-service attacks against relays.
1276 This release also fixes several minor bugs and annoyances from
1279 All directory authorities should upgrade to one of the versions
1280 released today. Relays running 0.2.9.x may wish to update to one of
1281 the versions released today, for the DoS mitigations.
1283 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1284 - Fix a protocol-list handling bug that could be used to remotely crash
1285 directory authorities with a null-pointer exception. Fixes bug 25074;
1286 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1289 o Major features (denial-of-service mitigation):
1290 - Give relays some defenses against the recent network overload. We
1291 start with three defenses (default parameters in parentheses).
1292 First: if a single client address makes too many concurrent
1293 connections (>100), hang up on further connections. Second: if a
1294 single client address makes circuits too quickly (more than 3 per
1295 second, with an allowed burst of 90) while also having too many
1296 connections open (3), refuse new create cells for the next while
1297 (1-2 hours). Third: if a client asks to establish a rendezvous
1298 point to you directly, ignore the request. These defenses can be
1299 manually controlled by new torrc options, but relays will also
1300 take guidance from consensus parameters, so there's no need to
1301 configure anything manually. Implements ticket 24902.
1303 o Major bugfixes (bootstrapping):
1304 - Fetch descriptors aggressively whenever we lack enough to build
1305 circuits, regardless of how many descriptors we are missing.
1306 Previously, we would delay launching the fetch when we had fewer
1307 than 15 missing descriptors, even if some of those descriptors
1308 were blocking circuits from building. Fixes bug 23985; bugfix on
1309 0.1.1.11-alpha. The effects of this bug became worse in
1310 0.3.0.3-alpha, when we began treating missing descriptors from our
1311 primary guards as a reason to delay circuits.
1313 o Major bugfixes (onion services, retry behavior):
1314 - Fix an "off by 2" error in counting rendezvous failures on the
1315 onion service side. While we thought we would stop the rendezvous
1316 attempt after one failed circuit, we were actually making three
1317 circuit attempts before giving up. Now switch to a default of 2,
1318 and allow the consensus parameter "hs_service_max_rdv_failures" to
1319 override. Fixes bug 24895; bugfix on 0.0.6.
1321 o Minor feature (relay statistics):
1322 - Change relay bandwidth reporting stats interval from 4 hours to 24
1323 hours in order to reduce the efficiency of guard discovery
1324 attacks. Fixes ticket 23856.
1326 o Minor features (compatibility, OpenSSL):
1327 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1328 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1329 since they neither disabled TLS 1.3 nor enabled any of the
1330 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1331 Closes ticket 24978.
1333 o Minor features (denial-of-service avoidance):
1334 - Make our OOM handler aware of the geoip client history cache so it
1335 doesn't fill up the memory. This check is important for IPv6 and
1336 our DoS mitigation subsystem. Closes ticket 25122.
1338 o Minor features (fallback directory mirrors):
1339 - The fallback directory list has been re-generated based on the
1340 current status of the network. Tor uses fallback directories to
1341 bootstrap when it doesn't yet have up-to-date directory
1342 information. Closes ticket 24801.
1343 - Make the default DirAuthorityFallbackRate 0.1, so that clients
1344 prefer to bootstrap from fallback directory mirrors. This is a
1345 follow-up to 24679, which removed weights from the default
1346 fallbacks. Implements ticket 24681.
1348 o Minor features (geoip):
1349 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1352 o Minor features (linux seccomp2 sandbox):
1353 - Update the sandbox rules so that they should now work correctly
1354 with Glibc 2.26. Closes ticket 24315.
1356 o Minor bugfix (channel connection):
1357 - Use the actual observed address of an incoming relay connection,
1358 not the canonical address of the relay from its descriptor, when
1359 making decisions about how to handle the incoming connection.
1360 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1362 o Minor bugfix (directory authority):
1363 - Directory authorities, when refusing a descriptor from a rejected
1364 relay, now explicitly tell the relay (in its logs) to set a valid
1365 ContactInfo address and contact the bad-relays@ mailing list.
1366 Fixes bug 25170; bugfix on 0.2.9.1.
1368 o Minor bugfixes (address selection):
1369 - When the fascist_firewall_choose_address_ functions don't find a
1370 reachable address, set the returned address to the null address
1371 and port. This is a precautionary measure, because some callers do
1372 not check the return value. Fixes bug 24736; bugfix
1375 o Minor bugfixes (compilation):
1376 - Fix a signed/unsigned comparison warning introduced by our fix to
1377 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
1379 o Minor bugfixes (control port, linux seccomp2 sandbox):
1380 - Avoid a crash when attempting to use the seccomp2 sandbox together
1381 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
1384 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1385 - Fix a possible crash on malformed consensus. If a consensus had
1386 contained an unparseable protocol line, it could have made clients
1387 and relays crash with a null-pointer exception. To exploit this
1388 issue, however, an attacker would need to be able to subvert the
1389 directory authority system. Fixes bug 25251; bugfix on
1390 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1392 o Minor bugfixes (memory usage):
1393 - When queuing DESTROY cells on a channel, only queue the circuit-id
1394 and reason fields: not the entire 514-byte cell. This fix should
1395 help mitigate any bugs or attacks that fill up these queues, and
1396 free more RAM for other uses. Fixes bug 24666; bugfix
1399 o Minor bugfixes (network layer):
1400 - When closing a connection via close_connection_immediately(), we
1401 mark it as "not blocked on bandwidth", to prevent later calls from
1402 trying to unblock it, and give it permission to read. This fixes a
1403 backtrace warning that can happen on relays under various
1404 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
1406 o Minor bugfixes (OSX):
1407 - Don't exit the Tor process if setrlimit() fails to change the file
1408 limit (which can happen sometimes on some versions of OSX). Fixes
1409 bug 21074; bugfix on 0.0.9pre5.
1411 o Minor bugfixes (path selection):
1412 - When selecting relays by bandwidth, avoid a rounding error that
1413 could sometimes cause load to be imbalanced incorrectly.
1414 Previously, we would always round upwards; now, we round towards
1415 the nearest integer. This had the biggest effect when a relay's
1416 weight adjustments should have given it weight 0, but it got
1417 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
1418 - When calculating the fraction of nodes that have descriptors, and
1419 all nodes in the network have zero bandwidths, count the number of
1420 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
1421 - Actually log the total bandwidth in compute_weighted_bandwidths().
1422 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
1424 o Minor bugfixes (portability, msvc):
1425 - Fix a bug in the bit-counting parts of our timing-wheel code on
1426 MSVC. (Note that MSVC is still not a supported build platform, due
1427 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
1430 o Minor bugfixes (relay):
1431 - Make the internal channel_is_client() function look at what sort
1432 of connection handshake the other side used, rather than whether
1433 the other side ever sent a create_fast cell to us. Backports part
1434 of the fixes from bugs 22805 and 24898.
1436 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1437 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1439 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1440 bugfix on 0.2.9.4-alpha.
1443 Changes in version 0.3.2.10 - 2018-03-03
1444 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
1445 backports a number of bugfixes, including important fixes for security
1448 It includes an important security fix for a remote crash attack
1449 against directory authorities, tracked as TROVE-2018-001.
1451 Additionally, it backports a fix for a bug whose severity we have
1452 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
1453 triggered in order to crash relays with a use-after-free pattern. As
1454 such, we are now tracking that bug as TROVE-2018-002 and
1455 CVE-2018-0491, and backporting it to earlier releases. This bug
1456 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
1459 This release also backports our new system for improved resistance to
1460 denial-of-service attacks against relays.
1462 This release also fixes several minor bugs and annoyances from
1465 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
1466 today, for the fix to TROVE-2018-002. Directory authorities should
1467 also upgrade. (Relays on earlier versions might want to update too for
1468 the DoS mitigations.)
1470 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
1471 - Fix a protocol-list handling bug that could be used to remotely crash
1472 directory authorities with a null-pointer exception. Fixes bug 25074;
1473 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1476 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
1477 - Avoid adding the same channel twice in the KIST scheduler pending
1478 list, which could lead to remote denial-of-service use-after-free
1479 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
1481 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
1482 - Give relays some defenses against the recent network overload. We
1483 start with three defenses (default parameters in parentheses).
1484 First: if a single client address makes too many concurrent
1485 connections (>100), hang up on further connections. Second: if a
1486 single client address makes circuits too quickly (more than 3 per
1487 second, with an allowed burst of 90) while also having too many
1488 connections open (3), refuse new create cells for the next while
1489 (1-2 hours). Third: if a client asks to establish a rendezvous
1490 point to you directly, ignore the request. These defenses can be
1491 manually controlled by new torrc options, but relays will also
1492 take guidance from consensus parameters, so there's no need to
1493 configure anything manually. Implements ticket 24902.
1495 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
1496 - Fix an "off by 2" error in counting rendezvous failures on the
1497 onion service side. While we thought we would stop the rendezvous
1498 attempt after one failed circuit, we were actually making three
1499 circuit attempts before giving up. Now switch to a default of 2,
1500 and allow the consensus parameter "hs_service_max_rdv_failures" to
1501 override. Fixes bug 24895; bugfix on 0.0.6.
1502 - New-style (v3) onion services now obey the "max rendezvous circuit
1503 attempts" logic. Previously they would make as many rendezvous
1504 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
1505 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
1507 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
1508 - Add Link protocol version 5 to the supported protocols list. Fixes
1509 bug 25070; bugfix on 0.3.1.1-alpha.
1511 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
1512 - Fix a set of false positives where relays would consider
1513 connections to other relays as being client-only connections (and
1514 thus e.g. deserving different link padding schemes) if those
1515 relays fell out of the consensus briefly. Now we look only at the
1516 initial handshake and whether the connection authenticated as a
1517 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1519 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
1520 - The scheduler subsystem was failing to promptly notice changes in
1521 consensus parameters, making it harder to switch schedulers
1522 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
1524 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
1525 - Make our OOM handler aware of the geoip client history cache so it
1526 doesn't fill up the memory. This check is important for IPv6 and
1527 our DoS mitigation subsystem. Closes ticket 25122.
1529 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
1530 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1531 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1532 since they neither disabled TLS 1.3 nor enabled any of the
1533 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1534 Closes ticket 24978.
1536 o Minor features (geoip):
1537 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1540 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
1541 - When logging a failure to create an onion service's descriptor,
1542 also log what the problem with the descriptor was. Diagnostic
1545 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
1546 - Use the actual observed address of an incoming relay connection,
1547 not the canonical address of the relay from its descriptor, when
1548 making decisions about how to handle the incoming connection.
1549 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1551 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
1552 - Fix a possible crash on malformed consensus. If a consensus had
1553 contained an unparseable protocol line, it could have made clients
1554 and relays crash with a null-pointer exception. To exploit this
1555 issue, however, an attacker would need to be able to subvert the
1556 directory authority system. Fixes bug 25251; bugfix on
1557 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1559 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
1560 - Directory authorities, when refusing a descriptor from a rejected
1561 relay, now explicitly tell the relay (in its logs) to set a valid
1562 ContactInfo address and contact the bad-relays@ mailing list.
1563 Fixes bug 25170; bugfix on 0.2.9.1.
1565 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
1566 - When building with Rust on OSX, link against libresolv, to work
1567 around the issue at https://github.com/rust-lang/rust/issues/46797.
1568 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
1570 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
1571 - Remove a BUG() statement when a client fetches an onion descriptor
1572 that has a lower revision counter than the one in its cache. This
1573 can happen in normal circumstances due to HSDir desync. Fixes bug
1574 24976; bugfix on 0.3.2.1-alpha.
1576 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
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.
1581 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
1582 - Improve the performance of our consensus-diff application code
1583 when Tor is built with the --enable-fragile-hardening option set.
1584 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
1586 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
1587 - Don't exit the Tor process if setrlimit() fails to change the file
1588 limit (which can happen sometimes on some versions of OSX). Fixes
1589 bug 21074; bugfix on 0.0.9pre5.
1591 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
1592 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1594 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1595 bugfix on 0.2.9.4-alpha.
1597 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
1598 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
1599 25005; bugfix on 0.3.2.7-rc.
1601 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
1602 - Look at the "HSRend" protocol version, not the "HSDir" protocol
1603 version, when deciding whether a consensus entry can support the
1604 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
1605 bugfix on 0.3.2.1-alpha.
1607 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
1608 - Update the "rust dependencies" submodule to be a project-level
1609 repository, rather than a user repository. Closes ticket 25323.
1611 o Documentation (backport from 0.3.3.1-alpha)
1612 - Document that operators who run more than one relay or bridge are
1613 expected to set MyFamily and ContactInfo correctly. Closes
1617 Changes in version 0.3.3.3-alpha - 2018-03-03
1618 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
1619 It includes an important security fix for a remote crash attack
1620 against directory authorities tracked as TROVE-2018-001.
1622 Additionally, with this release, we are upgrading the severity of a
1623 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
1624 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
1625 a use-after-free pattern. As such, we are now tracking that bug as
1626 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
1627 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
1629 This release also fixes several minor bugs and annoyances from
1632 Relays running 0.3.2.x should upgrade to one of the versions released
1633 today, for the fix to TROVE-2018-002. Directory authorities should
1634 also upgrade. (Relays on earlier versions might want to update too for
1635 the DoS mitigations.)
1637 o Major bugfixes (denial-of-service, directory authority):
1638 - Fix a protocol-list handling bug that could be used to remotely crash
1639 directory authorities with a null-pointer exception. Fixes bug 25074;
1640 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
1643 o Minor features (compatibility, OpenSSL):
1644 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
1645 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
1646 since they neither disabled TLS 1.3 nor enabled any of the
1647 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
1648 Closes ticket 24978.
1650 o Minor features (logging):
1651 - Clarify the log messages produced when getrandom() or a related
1652 entropy-generation mechanism gives an error. Closes ticket 25120.
1654 o Minor features (testing):
1655 - Add a "make test-rust" target to run the rust tests only. Closes
1658 o Minor bugfixes (denial-of-service):
1659 - Fix a possible crash on malformed consensus. If a consensus had
1660 contained an unparseable protocol line, it could have made clients
1661 and relays crash with a null-pointer exception. To exploit this
1662 issue, however, an attacker would need to be able to subvert the
1663 directory authority system. Fixes bug 25251; bugfix on
1664 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
1666 o Minor bugfixes (DoS mitigation):
1667 - Add extra safety checks when refilling the circuit creation bucket
1668 to ensure we never set a value above the allowed maximum burst.
1669 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
1670 - When a new consensus arrives, don't update our DoS-mitigation
1671 parameters if we aren't a public relay. Fixes bug 25223; bugfix
1674 o Minor bugfixes (man page, SocksPort):
1675 - Remove dead code from the old "SocksSocket" option, and rename
1676 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
1677 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
1679 o Minor bugfixes (performance):
1680 - Reduce the number of circuits that will be opened at once during
1681 the circuit build timeout phase. This is done by increasing the
1682 idle timeout to 3 minutes, and lowering the maximum number of
1683 concurrent learning circuits to 10. Fixes bug 24769; bugfix
1686 o Minor bugfixes (spec conformance):
1687 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
1689 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
1690 bugfix on 0.2.9.4-alpha.
1692 o Minor bugfixes (spec conformance, rust):
1693 - Resolve a denial-of-service issue caused by an infinite loop in
1694 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
1695 Also tracked as TROVE-2018-003.
1697 o Code simplification and refactoring:
1698 - Update the "rust dependencies" submodule to be a project-level
1699 repository, rather than a user repository. Closes ticket 25323.
1702 Changes in version 0.3.3.2-alpha - 2018-02-10
1703 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
1704 introduces a mechanism to handle the high loads that many relay
1705 operators have been reporting recently. It also fixes several bugs in
1706 older releases. If this new code proves reliable, we plan to backport
1707 it to older supported release series.
1709 o Major features (denial-of-service mitigation):
1710 - Give relays some defenses against the recent network overload. We
1711 start with three defenses (default parameters in parentheses).
1712 First: if a single client address makes too many concurrent
1713 connections (>100), hang up on further connections. Second: if a
1714 single client address makes circuits too quickly (more than 3 per
1715 second, with an allowed burst of 90) while also having too many
1716 connections open (3), refuse new create cells for the next while
1717 (1-2 hours). Third: if a client asks to establish a rendezvous
1718 point to you directly, ignore the request. These defenses can be
1719 manually controlled by new torrc options, but relays will also
1720 take guidance from consensus parameters, so there's no need to
1721 configure anything manually. Implements ticket 24902.
1723 o Major bugfixes (netflow padding):
1724 - Stop adding unneeded channel padding right after we finish
1725 flushing to a connection that has been trying to flush for many
1726 seconds. Instead, treat all partial or complete flushes as
1727 activity on the channel, which will defer the time until we need
1728 to add padding. This fix should resolve confusing and scary log
1729 messages like "Channel padding timeout scheduled 221453ms in the
1730 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
1732 o Major bugfixes (protocol versions):
1733 - Add Link protocol version 5 to the supported protocols list. Fixes
1734 bug 25070; bugfix on 0.3.1.1-alpha.
1736 o Major bugfixes (scheduler, consensus):
1737 - The scheduler subsystem was failing to promptly notice changes in
1738 consensus parameters, making it harder to switch schedulers
1739 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
1741 o Minor features (denial-of-service avoidance):
1742 - Make our OOM handler aware of the geoip client history cache so it
1743 doesn't fill up the memory. This check is important for IPv6 and
1744 our DoS mitigation subsystem. Closes ticket 25122.
1746 o Minor features (directory authority):
1747 - When directory authorities are unable to add signatures to a
1748 pending consensus, log the reason why. Closes ticket 24849.
1750 o Minor features (geoip):
1751 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
1754 o Minor features (logging, diagnostic):
1755 - When logging a failure to create an onion service's descriptor,
1756 also log what the problem with the descriptor was. Diagnostic for
1759 o Minor bugfix (channel connection):
1760 - Use the actual observed address of an incoming relay connection,
1761 not the canonical address of the relay from its descriptor, when
1762 making decisions about how to handle the incoming connection.
1763 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
1765 o Minor bugfix (directory authority):
1766 - Directory authorities, when refusing a descriptor from a rejected
1767 relay, now explicitly tell the relay (in its logs) to set a valid
1768 ContactInfo address and contact the bad-relays@ mailing list.
1769 Fixes bug 25170; bugfix on 0.2.9.1.
1771 o Minor bugfixes (all versions of Tor):
1772 - Use the "misspell" tool to detect and fix typos throughout the
1773 source code. Fixes bug 23650; bugfix on various versions of Tor.
1774 Patch from Deepesh Pathak.
1776 o Minor bugfixes (circuit, cannibalization):
1777 - Don't cannibalize preemptively-built circuits if we no longer
1778 recognize their first hop. This situation can happen if our Guard
1779 relay went off the consensus after the circuit was created. Fixes
1780 bug 24469; bugfix on 0.0.6.
1782 o Minor bugfixes (correctness):
1783 - Remove a nonworking, unnecessary check to see whether a circuit
1784 hop's identity digest was set when the circuit failed. Fixes bug
1785 24927; bugfix on 0.2.4.4-alpha.
1787 o Minor bugfixes (logging):
1788 - Don't treat inability to store a cached consensus object as a bug:
1789 it can happen normally when we are out of disk space. Fixes bug
1790 24859; bugfix on 0.3.1.1-alpha.
1791 - Fix a (mostly harmless) race condition when invoking
1792 LOG_PROTOCOL_WARN message from a subthread while the torrc options
1793 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
1795 o Minor bugfixes (onion services):
1796 - Remove a BUG() statement when a client fetches an onion descriptor
1797 that has a lower revision counter than the one in its cache. This
1798 can happen in normal circumstances due to HSDir desync. Fixes bug
1799 24976; bugfix on 0.3.2.1-alpha.
1800 - If we are configured to offer a single onion service, don't log
1801 long-term established one hop rendezvous points in the heartbeat.
1802 Fixes bug 25116; bugfix on 0.2.9.6-rc.
1804 o Minor bugfixes (performance):
1805 - Avoid calling protocol_list_supports_protocol() from inside tight
1806 loops when running with cached routerinfo_t objects. Instead,
1807 summarize the relevant protocols as flags in the routerinfo_t, as
1808 we do for routerstatus_t objects. This change simplifies our code
1809 a little, and saves a large amount of short-term memory allocation
1810 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
1812 o Minor bugfixes (Rust FFI):
1813 - Fix a minor memory leak which would happen whenever the C code
1814 would call the Rust implementation of
1815 protover_get_supported_protocols(). This was due to the C version
1816 returning a static string, whereas the Rust version newly allocated
1817 a CString to pass across the FFI boundary. Consequently, the C
1818 code was not expecting to need to free() what it was given. Fixes
1819 bug 25127; bugfix on 0.3.2.1-alpha.
1821 o Minor bugfixes (scheduler, KIST):
1822 - Avoid adding the same channel twice in the KIST scheduler pending
1823 list, which would waste CPU cycles. Fixes bug 24700; bugfix
1826 o Minor bugfixes (unit test, monotonic time):
1827 - Increase a constant (1msec to 10msec) in the monotonic time test
1828 that makes sure the nsec/usec/msec times read are synchronized.
1829 This change was needed to accommodate slow systems like armel or
1830 when the clock_gettime() is not a VDSO on the running kernel.
1831 Fixes bug 25113; bugfix on 0.2.9.1.
1833 o Minor bugfixes (v3 onion services):
1834 - Look at the "HSRend" protocol version, not the "HSDir" protocol
1835 version, when deciding whether a consensus entry can support the
1836 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
1837 bugfix on 0.3.2.1-alpha.
1839 o Code simplification and refactoring:
1840 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
1842 - Remove a series of counters used to track circuit extend attempts
1843 and connection status but that in reality we aren't using for
1844 anything other than stats logged by a SIGUSR1 signal. Closes
1847 o Documentation (man page):
1848 - The HiddenServiceVersion torrc option accepts only one number:
1849 either version 2 or 3. Closes ticket 25026; bugfix
1853 Changes in version 0.3.3.1-alpha - 2018-01-25
1854 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
1855 several new features to Tor, including several improvements to
1856 bootstrapping, and support for an experimental "vanguards" feature to
1857 resist guard discovery attacks. This series also includes better
1858 support for applications that need to embed Tor or manage v3
1861 o Major features (embedding):
1862 - There is now a documented stable API for programs that need to
1863 embed Tor. See tor_api.h for full documentation and known bugs.
1864 Closes ticket 23684.
1865 - Tor now has support for restarting in the same process.
1866 Controllers that run Tor using the "tor_api.h" interface can now
1867 restart Tor after Tor has exited. This support is incomplete,
1868 however: we fixed crash bugs that prevented it from working at
1869 all, but many bugs probably remain, including a possibility of
1870 security issues. Implements ticket 24581.
1872 o Major features (IPv6, directory documents):
1873 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
1874 consensus. This information makes it easier for IPv6 clients to
1875 bootstrap and choose reachable entry guards. Implements ticket 23826.
1876 - Add consensus method 28, which removes IPv6 ORPorts from
1877 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
1878 are redundant in microdescs. This change will be used by Tor clients
1879 on 0.2.8.x and later. (That is to say, with all Tor clients that
1880 have IPv6 bootstrap and guard support.) Implements ticket 23828.
1881 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
1882 set by different numbers of authorities. Fixes 23870
1885 o Major features (onion service v3, control port):
1886 - The control port now supports commands and events for v3 onion
1887 services. It is now possible to create ephemeral v3 services using
1888 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
1889 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
1890 DEL_ONION) have been extended to support v3 onion services. Closes
1891 ticket 20699; implements proposal 284.
1893 o Major features (onion services):
1894 - Provide torrc options to pin the second and third hops of onion
1895 service circuits to a list of nodes. The option HSLayer2Guards
1896 pins the second hop, and the option HSLayer3Guards pins the third
1897 hop. These options are for use in conjunction with experiments
1898 with "vanguards" for preventing guard enumeration attacks. Closes
1901 o Major features (rust, portability, experimental):
1902 - Tor now ships with an optional implementation of one of its
1903 smaller modules (protover.c) in the Rust programming language. To
1904 try it out, install a Rust build environment, and configure Tor
1905 with "--enable-rust --enable-cargo-online-mode". This should not
1906 cause any user-visible changes, but should help us gain more
1907 experience with Rust, and plan future Rust integration work.
1908 Implementation by Chelsea Komlo. Closes ticket 22840.
1910 o Minor features (storage, configuration):
1911 - Users can store cached directory documents somewhere other than
1912 the DataDirectory by using the CacheDirectory option. Similarly,
1913 the storage location for relay's keys can be overridden with the
1914 KeyDirectory option. Closes ticket 22703.
1916 o Major features (v3 onion services, ipv6):
1917 - When v3 onion service clients send introduce cells, they now
1918 include the IPv6 address of the rendezvous point, if it has one.
1919 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
1920 in future Tor versions, IPv6-only v3 single onion services will be
1921 able to use IPv6 addresses to connect directly to the rendezvous
1922 point. Closes ticket 23577. Patch by Neel Chauhan.
1924 o Major bugfixes (onion services, retry behavior):
1925 - Fix an "off by 2" error in counting rendezvous failures on the
1926 onion service side. While we thought we would stop the rendezvous
1927 attempt after one failed circuit, we were actually making three
1928 circuit attempts before giving up. Now switch to a default of 2,
1929 and allow the consensus parameter "hs_service_max_rdv_failures" to
1930 override. Fixes bug 24895; bugfix on 0.0.6.
1931 - New-style (v3) onion services now obey the "max rendezvous circuit
1932 attempts" logic. Previously they would make as many rendezvous
1933 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
1934 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
1936 o Major bugfixes (relays):
1937 - Fix a set of false positives where relays would consider
1938 connections to other relays as being client-only connections (and
1939 thus e.g. deserving different link padding schemes) if those
1940 relays fell out of the consensus briefly. Now we look only at the
1941 initial handshake and whether the connection authenticated as a
1942 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
1944 o Minor feature (IPv6):
1945 - Make IPv6-only clients wait for microdescs for relays, even if we
1946 were previously using descriptors (or were using them as a bridge)
1947 and have a cached descriptor for them. Implements ticket 23827.
1948 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
1949 them, rather than waiting to download microdescriptors.
1950 Implements ticket 23827.
1952 o Minor features (cleanup):
1953 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
1954 when it stops. Closes ticket 23271.
1956 o Minor features (defensive programming):
1957 - Most of the functions in Tor that free objects have been replaced
1958 with macros that free the objects and set the corresponding
1959 pointers to NULL. This change should help prevent a large class of
1960 dangling pointer bugs. Closes ticket 24337.
1961 - Where possible, the tor_free() macro now only evaluates its input
1962 once. Part of ticket 24337.
1963 - Check that microdesc ed25519 ids are non-zero in
1964 node_get_ed25519_id() before returning them. Implements ticket
1965 24001, patch by "aruna1234".
1967 o Minor features (embedding):
1968 - Tor can now start with a preauthenticated control connection
1969 created by the process that launched it. This feature is meant for
1970 use by programs that want to launch and manage a Tor process
1971 without allowing other programs to manage it as well. For more
1972 information, see the __OwningControllerFD option documented in
1973 control-spec.txt. Closes ticket 23900.
1974 - On most errors that would cause Tor to exit, it now tries to
1975 return from the tor_main() function, rather than calling the
1976 system exit() function. Most users won't notice a difference here,
1977 but it should be significant for programs that run Tor inside
1978 a separate thread: they should now be able to survive Tor's exit
1979 conditions rather than having Tor shut down the entire process.
1980 Closes ticket 23848.
1981 - Applications that want to embed Tor can now tell Tor not to
1982 register any of its own POSIX signal handlers, using the
1983 __DisableSignalHandlers option. Closes ticket 24588.
1985 o Minor features (fallback directory list):
1986 - Avoid selecting fallbacks that change their IP addresses too
1987 often. Select more fallbacks by ignoring the Guard flag, and
1988 allowing lower cutoffs for the Running and V2Dir flags. Also allow
1989 a lower bandwidth, and a higher number of fallbacks per operator
1990 (5% of the list). Implements ticket 24785.
1991 - Update the fallback whitelist and blacklist based on opt-ins and
1992 relay changes. Closes tickets 22321, 24678, 22527, 24135,
1995 o Minor features (fallback directory mirror configuration):
1996 - Add a nickname to each fallback in a C comment. This makes it
1997 easier for operators to find their relays, and allows stem to use
1998 nicknames to identify fallbacks. Implements ticket 24600.
1999 - Add a type and version header to the fallback directory mirror
2000 file. Also add a delimiter to the end of each fallback entry. This
2001 helps external parsers like stem and Relay Search. Implements
2003 - Add an extrainfo cache flag for each fallback in a C comment. This
2004 allows stem to use fallbacks to fetch extra-info documents, rather
2005 than using authorities. Implements ticket 22759.
2006 - Add the generateFallbackDirLine.py script for automatically
2007 generating fallback directory mirror lines from relay fingerprints.
2008 No more typos! Add the lookupFallbackDirContact.py script for
2009 automatically looking up operator contact info from relay
2010 fingerprints. Implements ticket 24706, patch by teor and atagar.
2011 - Reject any fallback directory mirror that serves an expired
2012 consensus. Implements ticket 20942, patch by "minik".
2013 - Remove commas and equals signs from external string inputs to the
2014 fallback list. This avoids format confusion attacks. Implements
2016 - Remove the "weight=10" line from fallback directory mirror
2017 entries. Ticket 24681 will maintain the current fallback weights
2018 by changing Tor's default fallback weight to 10. Implements
2020 - Stop logging excessive information about fallback netblocks.
2021 Implements ticket 24791.
2023 o Minor features (forward-compatibility):
2024 - If a relay supports some link authentication protocol that we do
2025 not recognize, then include that relay's ed25519 key when telling
2026 other relays to extend to it. Previously, we treated future
2027 versions as if they were too old to support ed25519 link
2028 authentication. Closes ticket 20895.
2030 o Minor features (heartbeat):
2031 - Add onion service information to our heartbeat logs, displaying
2032 stats about the activity of configured onion services. Closes
2035 o Minor features (instrumentation, development):
2036 - Add the MainloopStats option to allow developers to get
2037 instrumentation information from the main event loop via the
2038 heartbeat messages. We hope to use this to improve Tor's behavior
2039 when it's trying to sleep. Closes ticket 24605.
2041 o Minor features (log messages):
2042 - Improve a warning message that happens when we fail to re-parse an
2043 old router because of an expired certificate. Closes ticket 20020.
2044 - Make the log more quantitative when we hit MaxMemInQueues
2045 threshold exposing some values. Closes ticket 24501.
2047 o Minor features (logging, android):
2048 - Added support for the Android logging subsystem. Closes
2051 o Minor features (performance):
2052 - Support predictive circuit building for onion service circuits
2053 with multiple layers of guards. Closes ticket 23101.
2054 - Use stdatomic.h where available, rather than mutexes, to implement
2055 atomic_counter_t. Closes ticket 23953.
2057 o Minor features (performance, 32-bit):
2058 - Improve performance on 32-bit systems by avoiding 64-bit division
2059 when calculating the timestamp in milliseconds for channel padding
2060 computations. Implements ticket 24613.
2061 - Improve performance on 32-bit systems by avoiding 64-bit division
2062 when timestamping cells and buffer chunks for OOM calculations.
2063 Implements ticket 24374.
2065 o Minor features (performance, OSX, iOS):
2066 - Use the mach_approximate_time() function (when available) to
2067 implement coarse monotonic time. Having a coarse time function
2068 should avoid a large number of system calls, and improve
2069 performance slightly, especially under load. Closes ticket 24427.
2071 o Minor features (performance, windows):
2072 - Improve performance on Windows Vista and Windows 7 by adjusting
2073 TCP send window size according to the recommendation from
2074 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
2077 o Major features (relay):
2078 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
2079 operator to use a more reasonable ("reduced") exit policy, rather
2080 than the default one. If you want to run an exit node without
2081 thinking too hard about which ports to allow, this one is for you.
2082 Closes ticket 13605. Patch from Neel Chauhan.
2084 o Minor features (testing, debugging, embedding):
2085 - For development purposes, Tor now has a mode in which it runs for
2086 a few seconds, then stops, and starts again without exiting the
2087 process. This mode is meant to help us debug various issues with
2088 ticket 23847. To use this feature, compile with
2089 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
2090 environment variable. This is expected to crash a lot, and is
2091 really meant for developers only. It will likely be removed in a
2092 future release. Implements ticket 24583.
2094 o Minor bugfix (network IPv6 test):
2095 - Tor's test scripts now check if "ping -6 ::1" works when the user
2096 runs "make test-network-all". Fixes bug 24677; bugfix on
2097 0.2.9.3-alpha. Patch by "ffmancera".
2099 o Minor bugfixes (build, rust):
2100 - Fix output of autoconf checks to display success messages for Rust
2101 dependencies and a suitable rustc compiler version. Fixes bug
2102 24612; bugfix on 0.3.1.3-alpha.
2103 - When building with Rust on OSX, link against libresolv, to work
2104 around the issue at https://github.com/rust-lang/rust/issues/46797.
2105 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
2106 - Don't pass the --quiet option to cargo: it seems to suppress some
2107 errors, which is not what we want to do when building. Fixes bug
2108 24518; bugfix on 0.3.1.7.
2109 - Build correctly when building from outside Tor's source tree with
2110 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
2113 o Minor bugfixes (directory authorities, IPv6):
2114 - When creating a routerstatus (vote) from a routerinfo (descriptor),
2115 set the IPv6 address to the unspecified IPv6 address, and
2116 explicitly initialize the port to zero. Fixes bug 24488; bugfix
2119 o Minor bugfixes (fallback directory mirrors):
2120 - Make updateFallbackDirs.py search harder for python. (Some OSs
2121 don't put it in /usr/bin.) Fixes bug 24708; bugfix
2124 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
2125 - When hibernating, close connections normally and allow them to
2126 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
2128 - Do not attempt to launch self-reachability tests when entering
2129 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
2130 - Resolve several bugs related to descriptor fetching on bridge
2131 clients with bandwidth accounting enabled. (This combination is
2132 not recommended!) Fixes a case of bug 12062; bugfix
2134 - When hibernating, do not attempt to launch DNS checks. Fixes a
2135 case of bug 12062; bugfix on 0.1.2.2-alpha.
2136 - When hibernating, do not try to upload or download descriptors.
2137 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
2139 o Minor bugfixes (IPv6, bridges):
2140 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
2141 bugfix on 0.2.8.2-alpha.
2142 - Tor now sets IPv6 address in the routerstatus as well as in the
2143 router descriptors when updating addresses for a bridge. Closes
2144 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
2146 o Minor bugfixes (linux seccomp2 sandbox):
2147 - When running with the sandbox enabled, reload configuration files
2148 correctly even when %include was used. Previously we would crash.
2149 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
2151 o Minor bugfixes (memory leaks):
2152 - Avoid possible at-exit memory leaks related to use of Libevent's
2153 event_base_once() function. (This function tends to leak memory if
2154 the event_base is closed before the event fires.) Fixes bug 24584;
2155 bugfix on 0.2.8.1-alpha.
2156 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
2159 o Minor bugfixes (OSX):
2160 - Don't exit the Tor process if setrlimit() fails to change the file
2161 limit (which can happen sometimes on some versions of OSX). Fixes
2162 bug 21074; bugfix on 0.0.9pre5.
2164 o Minor bugfixes (performance, fragile-hardening):
2165 - Improve the performance of our consensus-diff application code
2166 when Tor is built with the --enable-fragile-hardening option set.
2167 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
2169 o Minor bugfixes (performance, timeouts):
2170 - Consider circuits for timeout as soon as they complete a hop. This
2171 is more accurate than applying the timeout in
2172 circuit_expire_building() because that function is only called
2173 once per second, which is now too slow for typical timeouts on the
2174 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
2175 - Use onion service circuits (and other circuits longer than 3 hops)
2176 to calculate a circuit build timeout. Previously, Tor only
2177 calculated its build timeout based on circuits that planned to be
2178 exactly 3 hops long. With this change, we include measurements
2179 from all circuits at the point where they complete their third
2180 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
2182 o Minor bugfixes (testing):
2183 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
2184 bugfix on 0.2.3.1-alpha.
2185 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
2186 25005; bugfix on 0.3.2.7-rc.
2188 o Code simplification and refactoring:
2189 - Remove /usr/athena from search path in configure.ac. Closes
2191 - Remove duplicate code in node_has_curve25519_onion_key() and
2192 node_get_curve25519_onion_key(), and add a check for a zero
2193 microdesc curve25519 onion key. Closes ticket 23966, patch by
2194 "aruna1234" and teor.
2195 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
2196 memory allocations with large numbers of OR connections (e.g.
2197 relays). Closes ticket 24119.
2198 - Separate the function that deletes ephemeral files when Tor
2200 - Small changes to Tor's buf_t API to make it suitable for use as a
2201 general-purpose safe string constructor. Closes ticket 22342.
2202 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
2203 avoid source code identifier confusion. Closes ticket 24467.
2204 - The tor_git_revision[] constant no longer needs to be redeclared
2205 by everything that links against the rest of Tor. Done as part of
2206 ticket 23845, to simplify our external API.
2207 - We make extend_info_from_node() use node_get_curve25519_onion_key()
2208 introduced in ticket 23577 to access the curve25519 public keys
2209 rather than accessing it directly. Closes ticket 23760. Patch by
2211 - Add a function to log channels' scheduler state changes to aid
2212 debugging efforts. Closes ticket 24531.
2215 - Add documentation on how to build tor with Rust dependencies
2216 without having to be online. Closes ticket 22907; bugfix
2218 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
2219 traffic. Closes ticket 24318.
2220 - Document that OutboundBindAddress doesn't apply to DNS requests.
2221 Closes ticket 22145. Patch from Aruna Maurya.
2222 - Document that operators who run more than one relay or bridge are
2223 expected to set MyFamily and ContactInfo correctly. Closes
2226 o Code simplification and refactoring (channels):
2227 - Remove the incoming and outgoing channel queues. These were never
2228 used, but still took up a step in our fast path.
2229 - The majority of the channel unit tests have been rewritten and the
2230 code coverage has now been raised to 83.6% for channel.c. Closes
2232 - Remove other dead code from the channel subsystem: All together,
2233 this cleanup has removed more than 1500 lines of code overall and
2234 adding very little except for unit test.
2236 o Code simplification and refactoring (circuit rendezvous):
2237 - Split the client-side rendezvous circuit lookup into two
2238 functions: one that returns only established circuits and another
2239 that returns all kinds of circuits. Closes ticket 23459.
2241 o Code simplification and refactoring (controller):
2242 - Make most of the variables in networkstatus_getinfo_by_purpose()
2243 const. Implements ticket 24489.
2246 Changes in version 0.3.2.9 - 2018-01-09
2247 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
2249 The 0.3.2 series includes our long-anticipated new onion service
2250 design, with numerous security features. (For more information, see
2251 our blog post at https://blog.torproject.org/fall-harvest.) We also
2252 have a new circuit scheduler algorithm for improved performance on
2253 relays everywhere (see https://blog.torproject.org/kist-and-tell),
2254 along with many smaller features and bugfixes.
2256 Per our stable release policy, we plan to support each stable release
2257 series for at least the next nine months, or for three months after
2258 the first stable release of the next series: whichever is longer. If
2259 you need a release with long-term support, we recommend that you stay
2260 with the 0.2.9 series.
2262 Below is a list of the changes since 0.3.2.8-rc. For a list of all
2263 changes since 0.3.1, see the ReleaseNotes file.
2265 o Minor features (fallback directory mirrors):
2266 - The fallback directory list has been re-generated based on the
2267 current status of the network. Tor uses fallback directories to
2268 bootstrap when it doesn't yet have up-to-date directory
2269 information. Closes ticket 24801.
2270 - Make the default DirAuthorityFallbackRate 0.1, so that clients
2271 prefer to bootstrap from fallback directory mirrors. This is a
2272 follow-up to 24679, which removed weights from the default
2273 fallbacks. Implements ticket 24681.
2275 o Minor features (geoip):
2276 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
2279 o Minor bugfixes (address selection):
2280 - When the fascist_firewall_choose_address_ functions don't find a
2281 reachable address, set the returned address to the null address
2282 and port. This is a precautionary measure, because some callers do
2283 not check the return value. Fixes bug 24736; bugfix
2286 o Minor bugfixes (compilation):
2287 - Resolve a few shadowed-variable warnings in the onion service
2288 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
2290 o Minor bugfixes (portability, msvc):
2291 - Fix a bug in the bit-counting parts of our timing-wheel code on
2292 MSVC. (Note that MSVC is still not a supported build platform, due
2293 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
2297 Changes in version 0.3.2.8-rc - 2017-12-21
2298 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
2299 schedulers that had led servers under heavy load to overload their
2300 outgoing connections. All relay operators running earlier 0.3.2.x
2301 versions should upgrade. This version also includes a mitigation for
2302 over-full DESTROY queues leading to out-of-memory conditions: if it
2303 works, we will soon backport it to earlier release series.
2305 This is the second release candidate in the 0.3.2 series. If we find
2306 no new bugs or regression here, then the first stable 0.3.2 release
2307 will be nearly identical to this.
2309 o Major bugfixes (KIST, scheduler):
2310 - The KIST scheduler did not correctly account for data already
2311 enqueued in each connection's send socket buffer, particularly in
2312 cases when the TCP/IP congestion window was reduced between
2313 scheduler calls. This situation lead to excessive per-connection
2314 buffering in the kernel, and a potential memory DoS. Fixes bug
2315 24665; bugfix on 0.3.2.1-alpha.
2317 o Minor features (geoip):
2318 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
2321 o Minor bugfixes (hidden service v3):
2322 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
2323 the probability of reaching a service for a client missing
2324 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
2326 o Minor bugfixes (memory usage):
2327 - When queuing DESTROY cells on a channel, only queue the circuit-id
2328 and reason fields: not the entire 514-byte cell. This fix should
2329 help mitigate any bugs or attacks that fill up these queues, and
2330 free more RAM for other uses. Fixes bug 24666; bugfix
2333 o Minor bugfixes (scheduler, KIST):
2334 - Use a sane write limit for KISTLite when writing onto a connection
2335 buffer instead of using INT_MAX and shoving as much as it can.
2336 Because the OOM handler cleans up circuit queues, we are better
2337 off at keeping them in that queue instead of the connection's
2338 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
2341 Changes in version 0.3.2.7-rc - 2017-12-14
2342 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
2343 including some that could affect reliability or correctness.
2345 This is the first release candidate in the 0.3.2 series. If we find no
2346 new bugs or regression here, then the first stable 0.3.2. release will
2347 be nearly identical to this.
2349 o Major bugfixes (circuit prediction):
2350 - Fix circuit prediction logic so that a client doesn't treat a port
2351 as being "handled" by a circuit if that circuit already has
2352 isolation settings on it. This change should make Tor clients more
2353 responsive by improving their chances of having a pre-created
2354 circuit ready for use when a request arrives. Fixes bug 18859;
2355 bugfix on 0.2.3.3-alpha.
2357 o Minor features (logging):
2358 - Provide better warnings when the getrandom() syscall fails. Closes
2361 o Minor features (portability):
2362 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
2363 (It doesn't yet work with the sandbox enabled.) Closes
2366 o Minor bugfixes (bridge clients, bootstrap):
2367 - Retry directory downloads when we get our first bridge descriptor
2368 during bootstrap or while reconnecting to the network. Keep
2369 retrying every time we get a bridge descriptor, until we have a
2370 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
2371 - Stop delaying bridge descriptor fetches when we have cached bridge
2372 descriptors. Instead, only delay bridge descriptor fetches when we
2373 have at least one reachable bridge. Fixes part of bug 24367;
2374 bugfix on 0.2.0.3-alpha.
2375 - Stop delaying directory fetches when we have cached bridge
2376 descriptors. Instead, only delay bridge descriptor fetches when
2377 all our bridges are definitely unreachable. Fixes part of bug
2378 24367; bugfix on 0.2.0.3-alpha.
2380 o Minor bugfixes (compilation):
2381 - Fix a signed/unsigned comparison warning introduced by our fix to
2382 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
2384 o Minor bugfixes (correctness):
2385 - Fix several places in our codebase where a C compiler would be
2386 likely to eliminate a check, based on assuming that undefined
2387 behavior had not happened elsewhere in the code. These cases are
2388 usually a sign of redundant checking or dubious arithmetic. Found
2389 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
2390 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
2393 o Minor bugfixes (onion service v3):
2394 - Fix a race where an onion service would launch a new intro circuit
2395 after closing an old one, but fail to register it before freeing
2396 the previously closed circuit. This bug was making the service
2397 unable to find the established intro circuit and thus not upload
2398 its descriptor, thus making a service unavailable for up to 24
2399 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
2401 o Minor bugfixes (scheduler, KIST):
2402 - Properly set the scheduler state of an unopened channel in the
2403 KIST scheduler main loop. This prevents a harmless but annoying
2404 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
2405 - Avoid a possible integer overflow when computing the available
2406 space on the TCP buffer of a channel. This had no security
2407 implications; but could make KIST allow too many cells on a
2408 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
2409 - Downgrade to "info" a harmless warning about the monotonic time
2410 moving backwards: This can happen on platform not supporting
2411 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
2414 Changes in version 0.3.2.6-alpha - 2017-12-01
2415 This version of Tor is the latest in the 0.3.2 alpha series. It
2416 includes fixes for several important security issues. All Tor users
2417 should upgrade to this release, or to one of the other releases coming
2420 o Major bugfixes (security):
2421 - Fix a denial of service bug where an attacker could use a
2422 malformed directory object to cause a Tor instance to pause while
2423 OpenSSL would try to read a passphrase from the terminal. (Tor
2424 instances run without a terminal, which is the case for most Tor
2425 packages, are not impacted.) Fixes bug 24246; bugfix on every
2426 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2427 Found by OSS-Fuzz as testcase 6360145429790720.
2428 - Fix a denial of service issue where an attacker could crash a
2429 directory authority using a malformed router descriptor. Fixes bug
2430 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2432 - When checking for replays in the INTRODUCE1 cell data for a
2433 (legacy) onion service, correctly detect replays in the RSA-
2434 encrypted part of the cell. We were previously checking for
2435 replays on the entire cell, but those can be circumvented due to
2436 the malleability of Tor's legacy hybrid encryption. This fix helps
2437 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2438 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2441 o Major bugfixes (security, onion service v2):
2442 - Fix a use-after-free error that could crash v2 Tor onion services
2443 when they failed to open circuits while expiring introduction
2444 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2445 also tracked as TROVE-2017-013 and CVE-2017-8823.
2447 o Major bugfixes (security, relay):
2448 - When running as a relay, make sure that we never build a path
2449 through ourselves, even in the case where we have somehow lost the
2450 version of our descriptor appearing in the consensus. Fixes part
2451 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2452 as TROVE-2017-012 and CVE-2017-8822.
2453 - When running as a relay, make sure that we never choose ourselves
2454 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2455 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2457 o Minor feature (relay statistics):
2458 - Change relay bandwidth reporting stats interval from 4 hours to 24
2459 hours in order to reduce the efficiency of guard discovery
2460 attacks. Fixes ticket 23856.
2462 o Minor features (directory authority):
2463 - Add an IPv6 address for the "bastet" directory authority. Closes
2466 o Minor bugfixes (client):
2467 - By default, do not enable storage of client-side DNS values. These
2468 values were unused by default previously, but they should not have
2469 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
2472 Changes in version 0.3.1.9 - 2017-12-01:
2473 Tor 0.3.1.9 backports important security and stability fixes from the
2474 0.3.2 development series. All Tor users should upgrade to this
2475 release, or to another of the releases coming out today.
2477 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2478 - Fix a denial of service bug where an attacker could use a
2479 malformed directory object to cause a Tor instance to pause while
2480 OpenSSL would try to read a passphrase from the terminal. (Tor
2481 instances run without a terminal, which is the case for most Tor
2482 packages, are not impacted.) Fixes bug 24246; bugfix on every
2483 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2484 Found by OSS-Fuzz as testcase 6360145429790720.
2485 - Fix a denial of service issue where an attacker could crash a
2486 directory authority using a malformed router descriptor. Fixes bug
2487 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2489 - When checking for replays in the INTRODUCE1 cell data for a
2490 (legacy) onion service, correctly detect replays in the RSA-
2491 encrypted part of the cell. We were previously checking for
2492 replays on the entire cell, but those can be circumvented due to
2493 the malleability of Tor's legacy hybrid encryption. This fix helps
2494 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2495 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2498 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2499 - Fix a use-after-free error that could crash v2 Tor onion services
2500 when they failed to open circuits while expiring introduction
2501 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2502 also tracked as TROVE-2017-013 and CVE-2017-8823.
2504 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2505 - When running as a relay, make sure that we never build a path
2506 through ourselves, even in the case where we have somehow lost the
2507 version of our descriptor appearing in the consensus. Fixes part
2508 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2509 as TROVE-2017-012 and CVE-2017-8822.
2510 - When running as a relay, make sure that we never choose ourselves
2511 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2512 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2514 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2515 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2516 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2517 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2518 identifying and finding a workaround to this bug and to Moritz,
2519 Arthur Edelstein, and Roger for helping to track it down and
2522 o Minor features (bridge):
2523 - Bridges now include notice in their descriptors that they are
2524 bridges, and notice of their distribution status, based on their
2525 publication settings. Implements ticket 18329. For more fine-
2526 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2529 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2530 - Add an IPv6 address for the "bastet" directory authority. Closes
2533 o Minor features (geoip):
2534 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2537 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2538 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2539 relays, to prevent spurious address resolutions and descriptor
2540 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2541 bugfix on in 0.2.8.1-alpha.
2543 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2544 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2545 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2547 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2548 - When a circuit is marked for close, do not attempt to package any
2549 cells for channels on that circuit. Previously, we would detect
2550 this condition lower in the call stack, when we noticed that the
2551 circuit had no attached channel, and log an annoying message.
2552 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2554 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
2555 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2556 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2559 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2560 - Avoid a crash when transitioning from client mode to bridge mode.
2561 Previously, we would launch the worker threads whenever our
2562 "public server" mode changed, but not when our "server" mode
2563 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2566 Changes in version 0.3.0.13 - 2017-12-01
2567 Tor 0.3.0.13 backports important security and stability bugfixes from
2568 later Tor releases. All Tor users should upgrade to this release, or
2569 to another of the releases coming out today.
2571 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
2572 2018. If you need a release with long-term support, please stick with
2573 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2575 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2576 - Fix a denial of service bug where an attacker could use a
2577 malformed directory object to cause a Tor instance to pause while
2578 OpenSSL would try to read a passphrase from the terminal. (Tor
2579 instances run without a terminal, which is the case for most Tor
2580 packages, are not impacted.) Fixes bug 24246; bugfix on every
2581 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2582 Found by OSS-Fuzz as testcase 6360145429790720.
2583 - Fix a denial of service issue where an attacker could crash a
2584 directory authority using a malformed router descriptor. Fixes bug
2585 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2587 - When checking for replays in the INTRODUCE1 cell data for a
2588 (legacy) onion service, correctly detect replays in the RSA-
2589 encrypted part of the cell. We were previously checking for
2590 replays on the entire cell, but those can be circumvented due to
2591 the malleability of Tor's legacy hybrid encryption. This fix helps
2592 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2593 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2596 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2597 - Fix a use-after-free error that could crash v2 Tor onion services
2598 when they failed to open circuits while expiring introduction
2599 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2600 also tracked as TROVE-2017-013 and CVE-2017-8823.
2602 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2603 - When running as a relay, make sure that we never build a path
2604 through ourselves, even in the case where we have somehow lost the
2605 version of our descriptor appearing in the consensus. Fixes part
2606 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2607 as TROVE-2017-012 and CVE-2017-8822.
2608 - When running as a relay, make sure that we never choose ourselves
2609 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
2610 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
2612 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2613 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2614 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2615 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2616 identifying and finding a workaround to this bug and to Moritz,
2617 Arthur Edelstein, and Roger for helping to track it down and
2620 o Minor features (security, windows, backport from 0.3.1.1-alpha):
2621 - Enable a couple of pieces of Windows hardening: one
2622 (HeapEnableTerminationOnCorruption) that has been on-by-default
2623 since Windows 8, and unavailable before Windows 7; and one
2624 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2625 affect us, but shouldn't do any harm. Closes ticket 21953.
2627 o Minor features (bridge, backport from 0.3.1.9):
2628 - Bridges now include notice in their descriptors that they are
2629 bridges, and notice of their distribution status, based on their
2630 publication settings. Implements ticket 18329. For more fine-
2631 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2634 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2635 - Add an IPv6 address for the "bastet" directory authority. Closes
2638 o Minor features (geoip):
2639 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2642 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2643 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2644 relays, to prevent spurious address resolutions and descriptor
2645 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2646 bugfix on in 0.2.8.1-alpha.
2648 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2649 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2650 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2652 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2653 - When a circuit is marked for close, do not attempt to package any
2654 cells for channels on that circuit. Previously, we would detect
2655 this condition lower in the call stack, when we noticed that the
2656 circuit had no attached channel, and log an annoying message.
2657 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2659 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2660 - Avoid a crash when transitioning from client mode to bridge mode.
2661 Previously, we would launch the worker threads whenever our
2662 "public server" mode changed, but not when our "server" mode
2663 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2665 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2666 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2667 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2670 Changes in version 0.2.9.14 - 2017-12-01
2671 Tor 0.3.0.13 backports important security and stability bugfixes from
2672 later Tor releases. All Tor users should upgrade to this release, or
2673 to another of the releases coming out today.
2675 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
2676 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2677 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2678 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2679 identifying and finding a workaround to this bug and to Moritz,
2680 Arthur Edelstein, and Roger for helping to track it down and
2683 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2684 - Fix a denial of service bug where an attacker could use a
2685 malformed directory object to cause a Tor instance to pause while
2686 OpenSSL would try to read a passphrase from the terminal. (Tor
2687 instances run without a terminal, which is the case for most Tor
2688 packages, are not impacted.) Fixes bug 24246; bugfix on every
2689 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2690 Found by OSS-Fuzz as testcase 6360145429790720.
2691 - Fix a denial of service issue where an attacker could crash a
2692 directory authority using a malformed router descriptor. Fixes bug
2693 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
2695 - When checking for replays in the INTRODUCE1 cell data for a
2696 (legacy) onion service, correctly detect replays in the RSA-
2697 encrypted part of the cell. We were previously checking for
2698 replays on the entire cell, but those can be circumvented due to
2699 the malleability of Tor's legacy hybrid encryption. This fix helps
2700 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2701 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2704 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2705 - Fix a use-after-free error that could crash v2 Tor onion services
2706 when they failed to open circuits while expiring introduction
2707 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2708 also tracked as TROVE-2017-013 and CVE-2017-8823.
2710 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2711 - When running as a relay, make sure that we never build a path
2712 through ourselves, even in the case where we have somehow lost the
2713 version of our descriptor appearing in the consensus. Fixes part
2714 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2715 as TROVE-2017-012 and CVE-2017-8822.
2717 o Minor features (bridge, backport from 0.3.1.9):
2718 - Bridges now include notice in their descriptors that they are
2719 bridges, and notice of their distribution status, based on their
2720 publication settings. Implements ticket 18329. For more fine-
2721 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2724 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2725 - Add an IPv6 address for the "bastet" directory authority. Closes
2728 o Minor features (geoip):
2729 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2732 o Minor features (security, windows, backport from 0.3.1.1-alpha):
2733 - Enable a couple of pieces of Windows hardening: one
2734 (HeapEnableTerminationOnCorruption) that has been on-by-default
2735 since Windows 8, and unavailable before Windows 7; and one
2736 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
2737 affect us, but shouldn't do any harm. Closes ticket 21953.
2739 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
2740 - Avoid unnecessary calls to directory_fetches_from_authorities() on
2741 relays, to prevent spurious address resolutions and descriptor
2742 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
2743 bugfix on in 0.2.8.1-alpha.
2745 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
2746 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
2747 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
2749 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
2750 - When a circuit is marked for close, do not attempt to package any
2751 cells for channels on that circuit. Previously, we would detect
2752 this condition lower in the call stack, when we noticed that the
2753 circuit had no attached channel, and log an annoying message.
2754 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
2756 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
2757 - Avoid a crash when transitioning from client mode to bridge mode.
2758 Previously, we would launch the worker threads whenever our
2759 "public server" mode changed, but not when our "server" mode
2760 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
2762 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2763 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2764 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2767 Changes in version 0.2.8.17 - 2017-12-01
2768 Tor 0.2.8.17 backports important security and stability bugfixes from
2769 later Tor releases. All Tor users should upgrade to this release, or
2770 to another of the releases coming out today.
2772 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
2773 2018. If you need a release with long-term support, please upgrade with
2774 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2776 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2777 - Fix a denial of service bug where an attacker could use a
2778 malformed directory object to cause a Tor instance to pause while
2779 OpenSSL would try to read a passphrase from the terminal. (Tor
2780 instances run without a terminal, which is the case for most Tor
2781 packages, are not impacted.) Fixes bug 24246; bugfix on every
2782 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2783 Found by OSS-Fuzz as testcase 6360145429790720.
2784 - When checking for replays in the INTRODUCE1 cell data for a
2785 (legacy) onion service, correctly detect replays in the RSA-
2786 encrypted part of the cell. We were previously checking for
2787 replays on the entire cell, but those can be circumvented due to
2788 the malleability of Tor's legacy hybrid encryption. This fix helps
2789 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2790 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2793 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
2794 - Fix a use-after-free error that could crash v2 Tor onion services
2795 when they failed to open circuits while expiring introduction
2796 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
2797 also tracked as TROVE-2017-013 and CVE-2017-8823.
2799 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2800 - When running as a relay, make sure that we never build a path through
2801 ourselves, even in the case where we have somehow lost the version of
2802 our descriptor appearing in the consensus. Fixes part of bug 21534;
2803 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
2806 o Minor features (bridge, backport from 0.3.1.9):
2807 - Bridges now include notice in their descriptors that they are
2808 bridges, and notice of their distribution status, based on their
2809 publication settings. Implements ticket 18329. For more fine-
2810 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2813 o Minor features (directory authority, backport from 0.3.2.6-alpha):
2814 - Add an IPv6 address for the "bastet" directory authority. Closes
2817 o Minor features (geoip):
2818 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2821 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
2822 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2823 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2826 Changes in version 0.2.5.16 - 2017-12-01
2827 Tor 0.2.5.13 backports important security and stability bugfixes from
2828 later Tor releases. All Tor users should upgrade to this release, or
2829 to another of the releases coming out today.
2831 Note: the Tor 0.2.5 series will no longer be supported after 1 May
2832 2018. If you need a release with long-term support, please upgrade to
2833 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
2835 o Major bugfixes (security, backport from 0.3.2.6-alpha):
2836 - Fix a denial of service bug where an attacker could use a
2837 malformed directory object to cause a Tor instance to pause while
2838 OpenSSL would try to read a passphrase from the terminal. (Tor
2839 instances run without a terminal, which is the case for most Tor
2840 packages, are not impacted.) Fixes bug 24246; bugfix on every
2841 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
2842 Found by OSS-Fuzz as testcase 6360145429790720.
2843 - When checking for replays in the INTRODUCE1 cell data for a
2844 (legacy) onion service, correctly detect replays in the RSA-
2845 encrypted part of the cell. We were previously checking for
2846 replays on the entire cell, but those can be circumvented due to
2847 the malleability of Tor's legacy hybrid encryption. This fix helps
2848 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
2849 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
2852 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
2853 - When running as a relay, make sure that we never build a path
2854 through ourselves, even in the case where we have somehow lost the
2855 version of our descriptor appearing in the consensus. Fixes part
2856 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
2857 as TROVE-2017-012 and CVE-2017-8822.
2859 o Minor features (bridge, backport from 0.3.1.9):
2860 - Bridges now include notice in their descriptors that they are
2861 bridges, and notice of their distribution status, based on their
2862 publication settings. Implements ticket 18329. For more fine-
2863 grained control of how a bridge is distributed, upgrade to 0.3.2.x
2866 o Minor features (geoip):
2867 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2871 Changes in version 0.3.2.5-alpha - 2017-11-22
2872 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
2873 fixes several stability and reliability bugs, including a fix for
2874 intermittent bootstrapping failures that some people have been seeing
2875 since the 0.3.0.x series.
2877 Please test this alpha out -- many of these fixes will soon be
2878 backported to stable Tor versions if no additional bugs are found
2881 o Major bugfixes (bootstrapping):
2882 - Fetch descriptors aggressively whenever we lack enough to build
2883 circuits, regardless of how many descriptors we are missing.
2884 Previously, we would delay launching the fetch when we had fewer
2885 than 15 missing descriptors, even if some of those descriptors
2886 were blocking circuits from building. Fixes bug 23985; bugfix on
2887 0.1.1.11-alpha. The effects of this bug became worse in
2888 0.3.0.3-alpha, when we began treating missing descriptors from our
2889 primary guards as a reason to delay circuits.
2890 - Don't try fetching microdescriptors from relays that have failed
2891 to deliver them in the past. Fixes bug 23817; bugfix
2894 o Minor features (directory authority):
2895 - Make the "Exit" flag assignment only depend on whether the exit
2896 policy allows connections to ports 80 and 443. Previously relays
2897 would get the Exit flag if they allowed connections to one of
2898 these ports and also port 6667. Resolves ticket 23637.
2900 o Minor features (geoip):
2901 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
2904 o Minor features (linux seccomp2 sandbox):
2905 - Update the sandbox rules so that they should now work correctly
2906 with Glibc 2.26. Closes ticket 24315.
2908 o Minor features (logging):
2909 - Downgrade a pair of log messages that could occur when an exit's
2910 resolver gave us an unusual (but not forbidden) response. Closes
2912 - Improve the message we log when re-enabling circuit build timeouts
2913 after having received a consensus. Closes ticket 20963.
2915 o Minor bugfixes (compilation):
2916 - Fix a memory leak warning in one of the libevent-related
2917 configuration tests that could occur when manually specifying
2918 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
2919 Found and patched by Alex Xu.
2920 - When detecting OpenSSL on Windows from our configure script, make
2921 sure to try linking with the ws2_32 library. Fixes bug 23783;
2922 bugfix on 0.3.2.2-alpha.
2924 o Minor bugfixes (control port, linux seccomp2 sandbox):
2925 - Avoid a crash when attempting to use the seccomp2 sandbox together
2926 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
2929 o Minor bugfixes (control port, onion services):
2930 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
2931 HS_DESC event when a service is not able to upload a descriptor.
2932 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
2934 o Minor bugfixes (directory cache):
2935 - Recover better from empty or corrupt files in the consensus cache
2936 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
2937 - When a consensus diff calculation is only partially successful,
2938 only record the successful parts as having succeeded. Partial
2939 success can happen if (for example) one compression method fails
2940 but the others succeed. Previously we misrecorded all the
2941 calculations as having succeeded, which would later cause a
2942 nonfatal assertion failure. Fixes bug 24086; bugfix
2945 o Minor bugfixes (logging):
2946 - Only log once if we notice that KIST support is gone. Fixes bug
2947 24158; bugfix on 0.3.2.1-alpha.
2948 - Suppress a log notice when relay descriptors arrive. We already
2949 have a bootstrap progress for this so no need to log notice
2950 everytime tor receives relay descriptors. Microdescriptors behave
2951 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
2953 o Minor bugfixes (network layer):
2954 - When closing a connection via close_connection_immediately(), we
2955 mark it as "not blocked on bandwidth", to prevent later calls from
2956 trying to unblock it, and give it permission to read. This fixes a
2957 backtrace warning that can happen on relays under various
2958 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
2960 o Minor bugfixes (onion services):
2961 - The introduction circuit was being timed out too quickly while
2962 waiting for the rendezvous circuit to complete. Keep the intro
2963 circuit around longer instead of timing out and reopening new ones
2964 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
2965 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
2966 so it matches dir-spec.txt. Fixes bug 24262; bugfix
2968 - Silence a warning about failed v3 onion descriptor uploads that
2969 can happen naturally under certain edge cases. Fixes part of bug
2970 23662; bugfix on 0.3.2.1-alpha.
2972 o Minor bugfixes (tests):
2973 - Fix a memory leak in one of the bridge-distribution test cases.
2974 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
2975 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
2976 to correctly handle cases where a caller gives it an RSA key of
2977 under 160 bits. (This is not actually a bug in Tor itself, but
2978 rather in our fuzzing code.) Fixes bug 24247; bugfix on
2979 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
2982 - Add notes in man page regarding OS support for the various
2983 scheduler types. Attempt to use less jargon in the scheduler
2984 section. Closes ticket 24254.
2987 Changes in version 0.3.2.4-alpha - 2017-11-08
2988 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
2989 It fixes several stability and reliability bugs, especially including
2990 a major reliability issue that has been plaguing fast exit relays in
2993 o Major bugfixes (exit relays, DNS):
2994 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
2995 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
2996 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
2997 identifying and finding a workaround to this bug and to Moritz,
2998 Arthur Edelstein, and Roger for helping to track it down and
3001 o Major bugfixes (scheduler, channel):
3002 - Stop processing scheduled channels if they closed while flushing
3003 cells. This can happen if the write on the connection fails
3004 leading to the channel being closed while in the scheduler loop.
3005 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
3007 o Minor features (logging, scheduler):
3008 - Introduce a SCHED_BUG() function to log extra information about
3009 the scheduler state if we ever catch a bug in the scheduler.
3010 Closes ticket 23753.
3012 o Minor features (removed deprecations):
3013 - The ClientDNSRejectInternalAddresses flag can once again be set in
3014 non-testing Tor networks, so long as they do not use the default
3015 directory authorities. This change also removes the deprecation of
3016 this flag from 0.2.9.2-alpha. Closes ticket 21031.
3018 o Minor features (testing):
3019 - Our fuzzing tests now test the encrypted portions of v3 onion
3020 service descriptors. Implements more of 21509.
3022 o Minor bugfixes (directory client):
3023 - On failure to download directory information, delay retry attempts
3024 by a random amount based on the "decorrelated jitter" algorithm.
3025 Our previous delay algorithm tended to produce extra-long delays
3026 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
3028 o Minor bugfixes (IPv6, v3 single onion services):
3029 - Remove buggy code for IPv6-only v3 single onion services, and
3030 reject attempts to configure them. This release supports IPv4,
3031 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
3032 stack v3 single onion services. Fixes bug 23820; bugfix
3035 o Minor bugfixes (logging, relay):
3036 - Give only a protocol warning when the ed25519 key is not
3037 consistent between the descriptor and microdescriptor of a relay.
3038 This can happen, for instance, if the relay has been flagged
3039 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
3041 o Minor bugfixes (manpage, onion service):
3042 - Document that the HiddenServiceNumIntroductionPoints option is
3043 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
3044 bugfix on 0.3.2.1-alpha.
3046 o Minor bugfixes (memory leaks):
3047 - Fix a minor memory leak at exit in the KIST scheduler. This bug
3048 should have no user-visible impact. Fixes bug 23774; bugfix
3050 - Fix a memory leak when decrypting a badly formatted v3 onion
3051 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
3052 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
3054 o Minor bugfixes (onion services):
3055 - Cache some needed onion service client information instead of
3056 constantly computing it over and over again. Fixes bug 23623;
3057 bugfix on 0.3.2.1-alpha.
3058 - Properly retry HSv3 descriptor fetches when missing required
3059 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
3061 o Minor bugfixes (path selection):
3062 - When selecting relays by bandwidth, avoid a rounding error that
3063 could sometimes cause load to be imbalanced incorrectly.
3064 Previously, we would always round upwards; now, we round towards
3065 the nearest integer. This had the biggest effect when a relay's
3066 weight adjustments should have given it weight 0, but it got
3067 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
3068 - When calculating the fraction of nodes that have descriptors, and
3069 all nodes in the network have zero bandwidths, count the number of
3070 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
3071 - Actually log the total bandwidth in compute_weighted_bandwidths().
3072 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
3074 o Minor bugfixes (relay, crash):
3075 - Avoid a crash when transitioning from client mode to bridge mode.
3076 Previously, we would launch the worker threads whenever our
3077 "public server" mode changed, but not when our "server" mode
3078 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
3080 o Minor bugfixes (testing):
3081 - Fix a spurious fuzzing-only use of an uninitialized value. Found
3082 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
3083 - Test that IPv6-only clients can use microdescriptors when running
3084 "make test-network-all". Requires chutney master 61c28b9 or later.
3085 Closes ticket 24109.
3088 Changes in version 0.3.2.3-alpha - 2017-10-27
3089 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
3090 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
3091 directory authority, Bastet.
3093 o Directory authority changes:
3094 - Add "Bastet" as a ninth directory authority to the default list.
3095 Closes ticket 23910.
3096 - The directory authority "Longclaw" has changed its IP address.
3097 Closes ticket 23592.
3099 o Minor features (bridge):
3100 - Bridge relays can now set the BridgeDistribution config option to
3101 add a "bridge-distribution-request" line to their bridge
3102 descriptor, which tells BridgeDB how they'd like their bridge
3103 address to be given out. (Note that as of Oct 2017, BridgeDB does
3104 not yet implement this feature.) As a side benefit, this feature
3105 provides a way to distinguish bridge descriptors from non-bridge
3106 descriptors. Implements tickets 18329.
3108 o Minor features (client, entry guards):
3109 - Improve log messages when missing descriptors for primary guards.
3110 Resolves ticket 23670.
3112 o Minor features (geoip):
3113 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3116 o Minor bugfixes (bridge):
3117 - Overwrite the bridge address earlier in the process of retrieving
3118 its descriptor, to make sure we reach it on the configured
3119 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
3121 o Minor bugfixes (documentation):
3122 - Document better how to read gcov, and what our gcov postprocessing
3123 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
3125 o Minor bugfixes (entry guards):
3126 - Tor now updates its guard state when it reads a consensus
3127 regardless of whether it's missing descriptors. That makes tor use
3128 its primary guards to fetch descriptors in some edge cases where
3129 it would previously have used fallback directories. Fixes bug
3130 23862; bugfix on 0.3.0.1-alpha.
3132 o Minor bugfixes (hidden service client):
3133 - When handling multiple SOCKS request for the same .onion address,
3134 only fetch the service descriptor once.
3135 - When a descriptor fetch fails with a non-recoverable error, close
3136 all pending SOCKS requests for that .onion. Fixes bug 23653;
3137 bugfix on 0.3.2.1-alpha.
3139 o Minor bugfixes (hidden service):
3140 - Always regenerate missing hidden service public key files. Prior
3141 to this, if the public key was deleted from disk, it wouldn't get
3142 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
3144 - Make sure that we have a usable ed25519 key when the intro point
3145 relay supports ed25519 link authentication. Fixes bug 24002;
3146 bugfix on 0.3.2.1-alpha.
3148 o Minor bugfixes (hidden service, v2):
3149 - When reloading configured hidden services, copy all information
3150 from the old service object. Previously, some data was omitted,
3151 causing delays in descriptor upload, and other bugs. Fixes bug
3152 23790; bugfix on 0.2.1.9-alpha.
3154 o Minor bugfixes (memory safety, defensive programming):
3155 - Clear the target address when node_get_prim_orport() returns
3156 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
3158 o Minor bugfixes (relay):
3159 - Avoid a BUG warning when receiving a dubious CREATE cell while an
3160 option transition is in progress. Fixes bug 23952; bugfix
3163 o Minor bugfixes (testing):
3164 - Adjust the GitLab CI configuration to more closely match that of
3165 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
3166 - Prevent scripts/test/coverage from attempting to move gcov output
3167 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
3168 - When running unit tests as root, skip a test that would fail
3169 because it expects a permissions error. This affects some
3170 continuous integration setups. Fixes bug 23758; bugfix
3172 - Stop unconditionally mirroring the tor repository in GitLab CI.
3173 This prevented developers from enabling GitLab CI on master. Fixes
3174 bug 23755; bugfix on 0.3.2.2-alpha.
3175 - Fix the hidden service v3 descriptor decoding fuzzing to use the
3176 latest decoding API correctly. Fixes bug 21509; bugfix
3179 o Minor bugfixes (warnings):
3180 - When we get an HTTP request on a SOCKS port, tell the user about
3181 the new HTTPTunnelPort option. Previously, we would give a "Tor is
3182 not an HTTP Proxy" message, which stopped being true when
3183 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
3187 Changes in version 0.2.5.15 - 2017-10-25
3188 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
3189 series. It also adds a new directory authority, Bastet.
3191 Note: the Tor 0.2.5 series will no longer be supported after 1 May
3192 2018. If you need a release with long-term support, please upgrade to
3193 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3195 o Directory authority changes:
3196 - Add "Bastet" as a ninth directory authority to the default list.
3197 Closes ticket 23910.
3198 - The directory authority "Longclaw" has changed its IP address.
3199 Closes ticket 23592.
3201 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3202 - Avoid an assertion failure bug affecting our implementation of
3203 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3204 handling of "0xx" differs from what we had expected. Fixes bug
3205 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3207 o Minor features (geoip):
3208 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3211 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3212 - Fix a memset() off the end of an array when packing cells. This
3213 bug should be harmless in practice, since the corrupted bytes are
3214 still in the same structure, and are always padding bytes,
3215 ignored, or immediately overwritten, depending on compiler
3216 behavior. Nevertheless, because the memset()'s purpose is to make
3217 sure that any other cell-handling bugs can't expose bytes to the
3218 network, we need to fix it. Fixes bug 22737; bugfix on
3219 0.2.4.11-alpha. Fixes CID 1401591.
3221 o Build features (backport from 0.3.1.5-alpha):
3222 - Tor's repository now includes a Travis Continuous Integration (CI)
3223 configuration file (.travis.yml). This is meant to help new
3224 developers and contributors who fork Tor to a Github repository be
3225 better able to test their changes, and understand what we expect
3226 to pass. To use this new build feature, you must fork Tor to your
3227 Github account, then go into the "Integrations" menu in the
3228 repository settings for your fork and enable Travis, then push
3229 your changes. Closes ticket 22636.
3232 Changes in version 0.2.8.16 - 2017-10-25
3233 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
3234 series, including a bugfix for a crash issue that had affected relays
3235 under memory pressure. It also adds a new directory authority, Bastet.
3237 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
3238 2018. If you need a release with long-term support, please stick with
3239 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3241 o Directory authority changes:
3242 - Add "Bastet" as a ninth directory authority to the default list.
3243 Closes ticket 23910.
3244 - The directory authority "Longclaw" has changed its IP address.
3245 Closes ticket 23592.
3247 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3248 - Fix a timing-based assertion failure that could occur when the
3249 circuit out-of-memory handler freed a connection's output buffer.
3250 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3252 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
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 (geoip):
3259 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3263 Changes in version 0.2.9.13 - 2017-10-25
3264 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
3265 series, including a bugfix for a crash issue that had affected relays
3266 under memory pressure. It also adds a new directory authority, Bastet.
3268 o Directory authority changes:
3269 - Add "Bastet" as a ninth directory authority to the default list.
3270 Closes ticket 23910.
3271 - The directory authority "Longclaw" has changed its IP address.
3272 Closes ticket 23592.
3274 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3275 - Fix a timing-based assertion failure that could occur when the
3276 circuit out-of-memory handler freed a connection's output buffer.
3277 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3279 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3280 - Remove longclaw's IPv6 address, as it will soon change. Authority
3281 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3282 3/8 directory authorities with IPv6 addresses, but there are also
3283 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3285 o Minor features (geoip):
3286 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3289 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
3290 - When a directory authority rejects a descriptor or extrainfo with
3291 a given digest, mark that digest as undownloadable, so that we do
3292 not attempt to download it again over and over. We previously
3293 tried to avoid downloading such descriptors by other means, but we
3294 didn't notice if we accidentally downloaded one anyway. This
3295 behavior became problematic in 0.2.7.2-alpha, when authorities
3296 began pinning Ed25519 keys. Fixes bug 22349; bugfix
3299 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
3300 - Clear the address when node_get_prim_orport() returns early.
3301 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
3303 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
3304 - When running as a Windows service, set the ID of the main thread
3305 correctly. Failure to do so made us fail to send log messages to
3306 the controller in 0.2.1.16-rc, slowed down controller event
3307 delivery in 0.2.7.3-rc and later, and crash with an assertion
3308 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
3309 Patch and diagnosis from "Vort".
3312 Changes in version 0.3.0.12 - 2017-10-25
3313 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
3314 series, including a bugfix for a crash issue that had affected relays
3315 under memory pressure. It also adds a new directory authority, Bastet.
3317 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
3318 2018. If you need a release with long-term support, please stick with
3319 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3321 o Directory authority changes:
3322 - Add "Bastet" as a ninth directory authority to the default list.
3323 Closes ticket 23910.
3324 - The directory authority "Longclaw" has changed its IP address.
3325 Closes ticket 23592.
3327 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3328 - Fix a timing-based assertion failure that could occur when the
3329 circuit out-of-memory handler freed a connection's output buffer.
3330 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3332 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3333 - Remove longclaw's IPv6 address, as it will soon change. Authority
3334 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3335 3/8 directory authorities with IPv6 addresses, but there are also
3336 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3338 o Minor features (geoip):
3339 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3342 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
3343 - When a directory authority rejects a descriptor or extrainfo with
3344 a given digest, mark that digest as undownloadable, so that we do
3345 not attempt to download it again over and over. We previously
3346 tried to avoid downloading such descriptors by other means, but we
3347 didn't notice if we accidentally downloaded one anyway. This
3348 behavior became problematic in 0.2.7.2-alpha, when authorities
3349 began pinning Ed25519 keys. Fixes bug 22349; bugfix
3352 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
3353 - Avoid a possible double close of a circuit by the intro point on
3354 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
3355 bugfix on 0.3.0.1-alpha.
3357 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
3358 - Clear the address when node_get_prim_orport() returns early.
3359 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
3361 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
3362 - When running as a Windows service, set the ID of the main thread
3363 correctly. Failure to do so made us fail to send log messages to
3364 the controller in 0.2.1.16-rc, slowed down controller event
3365 delivery in 0.2.7.3-rc and later, and crash with an assertion
3366 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
3367 Patch and diagnosis from "Vort".
3370 Changes in version 0.3.1.8 - 2017-10-25
3371 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
3372 It includes several bugfixes, including a bugfix for a crash issue
3373 that had affected relays under memory pressure. It also adds
3374 a new directory authority, Bastet.
3376 o Directory authority changes:
3377 - Add "Bastet" as a ninth directory authority to the default list.
3378 Closes ticket 23910.
3379 - The directory authority "Longclaw" has changed its IP address.
3380 Closes ticket 23592.
3382 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
3383 - Fix a timing-based assertion failure that could occur when the
3384 circuit out-of-memory handler freed a connection's output buffer.
3385 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3387 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
3388 - Remove longclaw's IPv6 address, as it will soon change. Authority
3389 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3390 3/8 directory authorities with IPv6 addresses, but there are also
3391 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3393 o Minor features (geoip):
3394 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
3397 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
3398 - Fix a compilation warning when building with zstd support on
3399 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
3400 and fixed by Andreas Stieger.
3402 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
3403 - Handle a pathological case when decompressing Zstandard data when
3404 the output buffer size is zero. Fixes bug 23551; bugfix
3407 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
3408 - Remove the length limit on HTTP status lines that authorities can
3409 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
3411 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
3412 - Avoid a possible double close of a circuit by the intro point on
3413 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
3414 bugfix on 0.3.0.1-alpha.
3416 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
3417 - Clear the address when node_get_prim_orport() returns early.
3418 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
3420 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
3421 - Fix additional channelpadding unit test failures by using mocked
3422 time instead of actual time for all tests. Fixes bug 23608; bugfix
3426 Changes in version 0.3.2.2-alpha - 2017-09-29
3427 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
3428 release fixes several minor bugs in the new scheduler and next-
3429 generation onion services; both features were newly added in the 0.3.2
3430 series. Other fixes in this alpha include several fixes for non-fatal
3431 tracebacks which would appear in logs.
3433 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
3434 alpha does not contain any substantial new features. Minor features
3435 include better testing and logging.
3437 The following comprises the complete list of changes included
3440 o Major bugfixes (relay, crash, assertion failure):
3441 - Fix a timing-based assertion failure that could occur when the
3442 circuit out-of-memory handler freed a connection's output buffer.
3443 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
3445 o Major bugfixes (scheduler):
3446 - If a channel is put into the scheduler's pending list, then it
3447 starts closing, and then if the scheduler runs before it finishes
3448 closing, the scheduler will get stuck trying to flush its cells
3449 while the lower layers refuse to cooperate. Fix that race
3450 condition by giving the scheduler an escape method. Fixes bug
3451 23676; bugfix on 0.3.2.1-alpha.
3453 o Minor features (build, compilation):
3454 - The "check-changes" feature is now part of the "make check" tests;
3455 we'll use it to try to prevent misformed changes files from
3456 accumulating. Closes ticket 23564.
3457 - Tor builds should now fail if there are any mismatches between the
3458 C type representing a configuration variable and the C type the
3459 data-driven parser uses to store a value there. Previously, we
3460 needed to check these by hand, which sometimes led to mistakes.
3461 Closes ticket 23643.
3463 o Minor features (directory authorities):
3464 - Remove longclaw's IPv6 address, as it will soon change. Authority
3465 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
3466 3/8 directory authorities with IPv6 addresses, but there are also
3467 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
3469 o Minor features (hidden service, circuit, logging):
3470 - Improve logging of many callsite in the circuit subsystem to print
3471 the circuit identifier(s).
3472 - Log when we cleanup an intro point from a service so we know when
3473 and for what reason it happened. Closes ticket 23604.
3475 o Minor features (logging):
3476 - Log more circuit information whenever we are about to try to
3477 package a relay cell on a circuit with a nonexistent n_chan.
3478 Attempt to diagnose ticket 8185.
3479 - Improve info-level log identification of particular circuits, to
3480 help with debugging. Closes ticket 23645.
3482 o Minor features (relay):
3483 - When choosing which circuits can be expired as unused, consider
3484 circuits from clients even if those clients used regular CREATE
3485 cells to make them; and do not consider circuits from relays even
3486 if they were made with CREATE_FAST. Part of ticket 22805.
3488 o Minor features (robustness):
3489 - Change several fatal assertions when flushing buffers into non-
3490 fatal assertions, to prevent any recurrence of 23690.
3492 o Minor features (spec conformance, bridge, diagnostic):
3493 - When handling the USERADDR command on an ExtOrPort, warn when the
3494 transports provides a USERADDR with no port. In a future version,
3495 USERADDR commands of this format may be rejected. Detects problems
3496 related to ticket 23080.
3498 o Minor features (testing):
3499 - Add a unit test to make sure that our own generated platform
3500 string will be accepted by directory authorities. Closes
3503 o Minor bugfixes (bootstrapping):
3504 - When warning about state file clock skew, report the correct
3505 direction for the detected skew. Fixes bug 23606; bugfix
3507 - Avoid an assertion failure when logging a state file clock skew
3508 very early in bootstrapping. Fixes bug 23607; bugfix
3511 o Minor bugfixes (build, compilation):
3512 - Fix a compilation warning when building with zstd support on
3513 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
3514 and fixed by Andreas Stieger.
3515 - When searching for OpenSSL, don't accept any OpenSSL library that
3516 lacks TLSv1_1_method(): Tor doesn't build with those versions.
3517 Additionally, look in /usr/local/opt/openssl, if it's present.
3518 These changes together repair the default build on OSX systems
3519 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
3521 o Minor bugfixes (compression):
3522 - Handle a pathological case when decompressing Zstandard data when
3523 the output buffer size is zero. Fixes bug 23551; bugfix
3526 o Minor bugfixes (documentation):
3527 - Fix manpage to not refer to the obsolete (and misspelled)
3528 UseEntryGuardsAsDirectoryGuards parameter in the description of
3529 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
3531 o Minor bugfixes (hidden service v3):
3532 - Don't log an assertion failure when we can't find the right
3533 information to extend to an introduction point. In rare cases,
3534 this could happen, causing a warning, even though tor would
3535 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
3536 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
3537 much bigger so the rendezvous point can't distinguish which hidden
3538 service protocol is being used. Fixes bug 23420; bugfix
3541 o Minor bugfixes (hidden service, relay):
3542 - Avoid a possible double close of a circuit by the intro point on
3543 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
3544 bugfix on 0.3.0.1-alpha.
3546 o Minor bugfixes (logging, relay shutdown, annoyance):
3547 - When a circuit is marked for close, do not attempt to package any
3548 cells for channels on that circuit. Previously, we would detect
3549 this condition lower in the call stack, when we noticed that the
3550 circuit had no attached channel, and log an annoying message.
3551 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
3553 o Minor bugfixes (scheduler):
3554 - When switching schedulers due to a consensus change, we didn't
3555 give the new scheduler a chance to react to the consensus. Fix
3556 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
3557 - Make the KISTSchedRunInterval option a non negative value. With
3558 this, the way to disable KIST through the consensus is to set it
3559 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
3560 - Only notice log the selected scheduler when we switch scheduler
3561 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
3562 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
3563 by a different tv_usec data type. Fixes bug 23575; bugfix
3565 - Make a hard exit if tor is unable to pick a scheduler which can
3566 happen if the user specifies a scheduler type that is not
3567 supported and not other types in Schedulers. Fixes bug 23581;
3568 bugfix on 0.3.2.1-alpha.
3569 - Properly initialize the scheduler last run time counter so it is
3570 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
3572 o Minor bugfixes (testing):
3573 - Capture and detect several "Result does not fit" warnings in unit
3574 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
3576 - Fix additional channelpadding unit test failures by using mocked
3577 time instead of actual time for all tests. Fixes bug 23608; bugfix
3579 - The removal of some old scheduler options caused some tests to
3580 fail on BSD systems. Assume current behavior is correct and make
3581 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
3583 o Code simplification and refactoring:
3584 - Remove various ways of testing circuits and connections for
3585 "clientness"; instead, favor channel_is_client(). Part of
3588 o Deprecated features:
3589 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
3590 now deprecated; they do not apply to relays, and they have had no
3591 effect on clients since 0.2.8.x. Closes ticket 19704.
3594 - HiddenServiceVersion man page entry wasn't mentioning the now
3595 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
3596 - Clarify that the Address option is entirely about setting an
3597 advertised IPv4 address. Closes ticket 18891.
3598 - Clarify the manpage's use of the term "address" to clarify what
3599 kind of address is intended. Closes ticket 21405.
3600 - Document that onion service subdomains are allowed, and ignored.
3601 Closes ticket 18736.
3604 Changes in version 0.3.2.1-alpha - 2017-09-18
3605 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
3606 includes support for our next-generation ("v3") onion service
3607 protocol, and adds a new circuit scheduler for more responsive
3608 forwarding decisions from relays. There are also numerous other small
3609 features and bugfixes here.
3611 Below are the changes since Tor 0.3.1.7.
3613 o Major feature (scheduler, channel):
3614 - Tor now uses new schedulers to decide which circuits should
3615 deliver cells first, in order to improve congestion at relays. The
3616 first type is called "KIST" ("Kernel Informed Socket Transport"),
3617 and is only available on Linux-like systems: it uses feedback from
3618 the kernel to prevent the kernel's TCP buffers from growing too
3619 full. The second new scheduler type is called "KISTLite": it
3620 behaves the same as KIST, but runs on systems without kernel
3621 support for inspecting TCP implementation details. The old
3622 scheduler is still available, under the name "Vanilla". To change
3623 the default scheduler preference order, use the new "Schedulers"
3624 option. (The default preference order is "KIST,KISTLite,Vanilla".)
3626 Matt Traudt implemented KIST, based on research by Rob Jansen,
3627 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
3628 more information, see the design paper at
3629 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
3630 followup implementation paper at https://arxiv.org/abs/1709.01044.
3631 Closes ticket 12541.
3633 o Major features (next-generation onion services):
3634 - Tor now supports the next-generation onion services protocol for
3635 clients and services! As part of this release, the core of
3636 proposal 224 has been implemented and is available for
3637 experimentation and testing by our users. This newer version of
3638 onion services ("v3") features many improvements over the legacy
3641 a) Better crypto (replaced SHA1/DH/RSA1024
3642 with SHA3/ed25519/curve25519)
3644 b) Improved directory protocol, leaking much less information to
3647 c) Improved directory protocol, with smaller surface for
3650 d) Better onion address security against impersonation.
3652 e) More extensible introduction/rendezvous protocol.
3654 f) A cleaner and more modular codebase.
3656 You can identify a next-generation onion address by its length:
3657 they are 56 characters long, as in
3658 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
3660 In the future, we will release more options and features for v3
3661 onion services, but we first need a testing period, so that the
3662 current codebase matures and becomes more robust. Planned features
3663 include: offline keys, advanced client authorization, improved
3664 guard algorithms, and statistics. For full details, see
3667 Legacy ("v2") onion services will still work for the foreseeable
3668 future, and will remain the default until this new codebase gets
3669 tested and hardened. Service operators who want to experiment with
3670 the new system can use the 'HiddenServiceVersion 3' torrc
3671 directive along with the regular onion service configuration
3672 options. We will publish a blog post about this new feature
3675 o Major bugfixes (usability, control port):
3676 - Report trusted clock skew indications as bootstrap errors, so
3677 controllers can more easily alert users when their clocks are
3678 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
3680 o Minor features (bug detection):
3681 - Log a warning message with a stack trace for any attempt to call
3682 get_options() during option validation. This pattern has caused
3683 subtle bugs in the past. Closes ticket 22281.
3685 o Minor features (client):
3686 - You can now use Tor as a tunneled HTTP proxy: use the new
3687 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
3688 requests. Closes ticket 22407.
3689 - Add an extra check to make sure that we always use the newer guard
3690 selection code for picking our guards. Closes ticket 22779.
3691 - When downloading (micro)descriptors, don't split the list into
3692 multiple requests unless we want at least 32 descriptors.
3693 Previously, we split at 4, not 32, which led to significant
3694 overhead in HTTP request size and degradation in compression
3695 performance. Closes ticket 23220.
3697 o Minor features (command line):
3698 - Add a new commandline option, --key-expiration, which prints when
3699 the current signing key is going to expire. Implements ticket
3700 17639; patch by Isis Lovecruft.
3702 o Minor features (control port):
3703 - If an application tries to use the control port as an HTTP proxy,
3704 respond with a meaningful "This is the Tor control port" message,
3705 and log the event. Closes ticket 1667. Patch from Ravi
3707 - Provide better error message for GETINFO desc/(id|name) when not
3708 fetching router descriptors. Closes ticket 5847. Patch by
3710 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
3711 whether Tor will try to download router descriptors and
3712 microdescriptors respectively. Closes ticket 22684.
3713 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
3714 so controllers can tell whether the geoip databases are loaded.
3715 Closes ticket 23237.
3716 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
3717 events. Closes ticket 19254. Patch by "DonnchaC".
3719 o Minor features (development support):
3720 - Developers can now generate a call-graph for Tor using the
3721 "calltool" python program, which post-processes object dumps. It
3722 should work okay on many Linux and OSX platforms, and might work
3723 elsewhere too. To run it, install calltool from
3724 https://gitweb.torproject.org/user/nickm/calltool.git and run
3725 "make callgraph". Closes ticket 19307.
3727 o Minor features (ed25519):
3728 - Add validation function to checks for torsion components in
3729 ed25519 public keys, used by prop224 client-side code. Closes
3730 ticket 22006. Math help by Ian Goldberg.
3732 o Minor features (exit relay, DNS):
3733 - Improve the clarity and safety of the log message from evdns when
3734 receiving an apparently spoofed DNS reply. Closes ticket 3056.
3736 o Minor features (integration, hardening):
3737 - Add a new NoExec option to prevent Tor from running other
3738 programs. When this option is set to 1, Tor will never try to run
3739 another program, regardless of the settings of
3740 PortForwardingHelper, ClientTransportPlugin, or
3741 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
3742 without restarting Tor. Closes ticket 22976.
3744 o Minor features (logging):
3745 - Improve the warning message for specifying a relay by nickname.
3746 The previous message implied that nickname registration was still
3747 part of the Tor network design, which it isn't. Closes
3749 - If the sandbox filter fails to load, suggest to the user that
3750 their kernel might not support seccomp2. Closes ticket 23090.
3752 o Minor features (portability):
3753 - Check at configure time whether uint8_t is the same type as
3754 unsigned char. Lots of existing code already makes this
3755 assumption, and there could be strict aliasing issues if the
3756 assumption is violated. Closes ticket 22410.
3758 o Minor features (relay, configuration):
3759 - Reject attempts to use relative file paths when RunAsDaemon is
3760 set. Previously, Tor would accept these, but the directory-
3761 changing step of RunAsDaemon would give strange and/or confusing
3762 results. Closes ticket 22731.
3764 o Minor features (startup, safety):
3765 - When configured to write a PID file, Tor now exits if it is unable
3766 to do so. Previously, it would warn and continue. Closes
3769 o Minor features (static analysis):
3770 - The BUG() macro has been changed slightly so that Coverity no
3771 longer complains about dead code if the bug is impossible. Closes
3774 o Minor features (testing):
3775 - The default chutney network tests now include tests for the v3
3776 hidden service design. Make sure you have the latest version of
3777 chutney if you want to run these. Closes ticket 22437.
3778 - Add a unit test to verify that we can parse a hardcoded v2 hidden
3779 service descriptor. Closes ticket 15554.
3781 o Minor bugfixes (certificate handling):
3782 - Fix a time handling bug in Tor certificates set to expire after
3783 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
3784 Coverity as CID 1415728.
3786 o Minor bugfixes (client, usability):
3787 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
3788 SOCKS4a requests that contain IP address strings, even when
3789 SafeSocks in enabled, as this prevents user from connecting to
3790 known IP addresses without relying on DNS for resolving. SafeSocks
3791 still rejects SOCKS connections that connect to IP addresses when
3792 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
3793 bugfix on Tor 0.2.6.2-alpha.
3795 o Minor bugfixes (code correctness):
3796 - Call htons() in extend_cell_format() for encoding a 16-bit value.
3797 Previously we used ntohs(), which happens to behave the same on
3798 all the platforms we support, but which isn't really correct.
3799 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
3800 - For defense-in-depth, make the controller's write_escaped_data()
3801 function robust to extremely long inputs. Fixes bug 19281; bugfix
3802 on 0.1.1.1-alpha. Reported by Guido Vranken.
3804 o Minor bugfixes (compilation):
3805 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
3806 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
3808 o Minor bugfixes (consensus expiry):
3809 - Check for adequate directory information correctly. Previously, Tor
3810 would reconsider whether it had sufficient directory information
3811 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
3813 o Minor bugfixes (directory protocol):
3814 - Directory servers now include a "Date:" http header for response
3815 codes other than 200. Clients starting with a skewed clock and a
3816 recent consensus were getting "304 Not modified" responses from
3817 directory authorities, so without the Date header, the client
3818 would never hear about a wrong clock. Fixes bug 23499; bugfix
3820 - Make clients wait for 6 seconds before trying to download a
3821 consensus from an authority. Fixes bug 17750; bugfix
3824 o Minor bugfixes (DoS-resistance):
3825 - If future code asks if there are any running bridges, without
3826 checking if bridges are enabled, log a BUG warning rather than
3827 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
3829 o Minor bugfixes (format strictness):
3830 - Restrict several data formats to decimal. Previously, the
3831 BuildTimeHistogram entries in the state file, the "bw=" entries in
3832 the bandwidth authority file, and the process IDs passed to the
3833 __OwningControllerProcess option could all be specified in hex or
3834 octal as well as in decimal. This was not an intentional feature.
3835 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
3838 o Minor bugfixes (heartbeat):
3839 - If we fail to write a heartbeat message, schedule a retry for the
3840 minimum heartbeat interval number of seconds in the future. Fixes
3841 bug 19476; bugfix on 0.2.3.1-alpha.
3843 o Minor bugfixes (linux seccomp2 sandbox, logging):
3844 - Fix some messages on unexpected errors from the seccomp2 library.
3845 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
3847 o Minor bugfixes (logging):
3848 - Remove duplicate log messages regarding opening non-local
3849 SocksPorts upon parsing config and opening listeners at startup.
3850 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
3851 - Use a more comprehensible log message when telling the user
3852 they've excluded every running exit node. Fixes bug 7890; bugfix
3854 - When logging the number of descriptors we intend to download per
3855 directory request, do not log a number higher than then the number
3856 of descriptors we're fetching in total. Fixes bug 19648; bugfix
3858 - When warning about a directory owned by the wrong user, log the
3859 actual name of the user owning the directory. Previously, we'd log
3860 the name of the process owner twice. Fixes bug 23487; bugfix
3862 - The tor specification says hop counts are 1-based, so fix two log
3863 messages that mistakenly logged 0-based hop counts. Fixes bug
3864 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
3865 Credit to Xiaofan Li for reporting this issue.
3867 o Minor bugfixes (portability):
3868 - Stop using the PATH_MAX variable, which is not defined on GNU
3869 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
3871 o Minor bugfixes (relay):
3872 - When uploading our descriptor for the first time after startup,
3873 report the reason for uploading as "Tor just started" rather than
3874 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
3875 - Avoid unnecessary calls to directory_fetches_from_authorities() on
3876 relays, to prevent spurious address resolutions and descriptor
3877 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
3878 bugfix on in 0.2.8.1-alpha.
3880 o Minor bugfixes (tests):
3881 - Fix a broken unit test for the OutboundAddress option: the parsing
3882 function was never returning an error on failure. Fixes bug 23366;
3883 bugfix on 0.3.0.3-alpha.
3884 - Fix a signed-integer overflow in the unit tests for
3885 dir/download_status_random_backoff, which was untriggered until we
3886 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
3888 o Minor bugfixes (usability, control port):
3889 - Stop making an unnecessary routerlist check in NETINFO clock skew
3890 detection; this was preventing clients from reporting NETINFO clock
3891 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
3893 o Code simplification and refactoring:
3894 - Extract the code for handling newly-open channels into a separate
3895 function from the general code to handle channel state
3896 transitions. This change simplifies our callgraph, reducing the
3897 size of the largest strongly connected component by roughly a
3898 factor of two. Closes ticket 22608.
3899 - Remove dead code for largely unused statistics on the number of
3900 times we've attempted various public key operations. Fixes bug
3901 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
3902 - Remove several now-obsolete functions for asking about old
3903 variants directory authority status. Closes ticket 22311; patch
3905 - Remove some of the code that once supported "Named" and "Unnamed"
3906 routers. Authorities no longer vote for these flags. Closes
3908 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
3909 and old hidden services, to indicate that they aren't suitable for
3910 new protocols or formats. Closes ticket 23026.
3911 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
3912 22521. Patch from Neel Chauhan.
3913 - Split the enormous circuit_send_next_onion_skin() function into
3914 multiple subfunctions. Closes ticket 22804.
3915 - Split the portions of the buffer.c module that handle particular
3916 protocols into separate modules. Part of ticket 23149.
3917 - Use our test macros more consistently, to produce more useful
3918 error messages when our unit tests fail. Add coccinelle patches to
3919 allow us to re-check for test macro uses. Closes ticket 22497.
3921 o Deprecated features:
3922 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
3923 only applies to direct unencrypted HTTP connections to your
3924 directory server, which your Tor probably isn't using. Closes
3928 - Clarify in the manual that "Sandbox 1" is only supported on Linux
3929 kernels. Closes ticket 22677.
3930 - Document all values of PublishServerDescriptor in the manpage.
3931 Closes ticket 15645.
3932 - Improve the documentation for the directory port part of the
3933 DirAuthority line. Closes ticket 20152.
3934 - Restore documentation for the authorities' "approved-routers"
3935 file. Closes ticket 21148.
3938 - The AllowDotExit option has been removed as unsafe. It has been
3939 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
3940 - The ClientDNSRejectInternalAddresses flag can no longer be set on
3941 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
3942 Closes ticket 21031.
3943 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
3944 nobody was using it any longer. Closes ticket 22377.
3947 Changes in version 0.2.8.15 - 2017-09-18
3948 Tor 0.2.8.15 backports a collection of bugfixes from later
3951 Most significantly, it includes a fix for TROVE-2017-008, a
3952 security bug that affects hidden services running with the
3953 SafeLogging option disabled. For more information, see
3954 https://trac.torproject.org/projects/tor/ticket/23490
3956 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
3957 2018. We suggest that you upgrade to the latest stable release if
3958 possible. If you can't, we recommend that you upgrade at least to
3959 0.2.9, which will be supported until 2020.
3961 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
3962 - Avoid an assertion failure bug affecting our implementation of
3963 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
3964 handling of "0xx" differs from what we had expected. Fixes bug
3965 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
3968 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
3971 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
3972 - Backport a fix for an "unused variable" warning that appeared
3973 in some versions of mingw. Fixes bug 22838; bugfix on
3976 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
3977 - Fix a memset() off the end of an array when packing cells. This
3978 bug should be harmless in practice, since the corrupted bytes are
3979 still in the same structure, and are always padding bytes,
3980 ignored, or immediately overwritten, depending on compiler
3981 behavior. Nevertheless, because the memset()'s purpose is to make
3982 sure that any other cell-handling bugs can't expose bytes to the
3983 network, we need to fix it. Fixes bug 22737; bugfix on
3984 0.2.4.11-alpha. Fixes CID 1401591.
3986 o Build features (backport from 0.3.1.5-alpha):
3987 - Tor's repository now includes a Travis Continuous Integration (CI)
3988 configuration file (.travis.yml). This is meant to help new
3989 developers and contributors who fork Tor to a Github repository be
3990 better able to test their changes, and understand what we expect
3991 to pass. To use this new build feature, you must fork Tor to your
3992 Github account, then go into the "Integrations" menu in the
3993 repository settings for your fork and enable Travis, then push
3994 your changes. Closes ticket 22636.
3997 Changes in version 0.2.9.12 - 2017-09-18
3998 Tor 0.2.9.12 backports a collection of bugfixes from later
4001 Most significantly, it includes a fix for TROVE-2017-008, a
4002 security bug that affects hidden services running with the
4003 SafeLogging option disabled. For more information, see
4004 https://trac.torproject.org/projects/tor/ticket/23490
4006 o Major features (security, backport from 0.3.0.2-alpha):
4007 - Change the algorithm used to decide DNS TTLs on client and server
4008 side, to better resist DNS-based correlation attacks like the
4009 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
4010 Feamster. Now relays only return one of two possible DNS TTL
4011 values, and clients are willing to believe DNS TTL values up to 3
4012 hours long. Closes ticket 19769.
4014 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
4015 - Fix a rare crash when sending a begin cell on a circuit whose
4016 linked directory connection had already been closed. Fixes bug
4017 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
4019 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
4020 - Fix a bug that prevented exit nodes from caching DNS records for
4021 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
4023 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
4024 - Fix a typo that had prevented TPROXY-based transparent proxying
4025 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
4026 Patch from "d4fq0fQAgoJ".
4028 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
4029 - Avoid an assertion failure bug affecting our implementation of
4030 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
4031 handling of "0xx" differs from what we had expected. Fixes bug
4032 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
4034 o Minor features (code style, backport from 0.3.1.3-alpha):
4035 - Add "Falls through" comments to our codebase, in order to silence
4036 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
4037 Stieger. Closes ticket 22446.
4039 o Minor features (geoip):
4040 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
4043 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
4044 - Roll over monthly accounting at the configured hour and minute,
4045 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
4046 Found by Andrey Karpov with PVS-Studio.
4048 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
4049 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
4050 bugfix on 0.2.8.1-alpha.
4051 - Fix warnings when building with libscrypt and openssl scrypt support
4052 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
4053 - When building with certain versions the mingw C header files, avoid
4054 float-conversion warnings when calling the C functions isfinite(),
4055 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
4057 o Minor bugfixes (compilation, backport from 0.3.1.7):
4058 - Avoid compiler warnings in the unit tests for running tor_sscanf()
4059 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
4061 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
4062 - Backport a fix for an "unused variable" warning that appeared
4063 in some versions of mingw. Fixes bug 22838; bugfix on
4066 o Minor bugfixes (controller, backport from 0.3.1.7):
4067 - Do not crash when receiving a HSPOST command with an empty body.
4068 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
4069 - Do not crash when receiving a POSTDESCRIPTOR command with an
4070 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
4072 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
4073 - Avoid Coverity build warnings related to our BUG() macro. By
4074 default, Coverity treats BUG() as the Linux kernel does: an
4075 instant abort(). We need to override that so our BUG() macro
4076 doesn't prevent Coverity from analyzing functions that use it.
4077 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
4079 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
4080 - Fix a memset() off the end of an array when packing cells. This
4081 bug should be harmless in practice, since the corrupted bytes are
4082 still in the same structure, and are always padding bytes,
4083 ignored, or immediately overwritten, depending on compiler
4084 behavior. Nevertheless, because the memset()'s purpose is to make
4085 sure that any other cell-handling bugs can't expose bytes to the
4086 network, we need to fix it. Fixes bug 22737; bugfix on
4087 0.2.4.11-alpha. Fixes CID 1401591.
4089 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
4090 - When setting the maximum number of connections allowed by the OS,
4091 always allow some extra file descriptors for other files. Fixes
4092 bug 22797; bugfix on 0.2.0.10-alpha.
4094 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
4095 - Avoid a sandbox failure when trying to re-bind to a socket and
4096 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
4098 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
4099 - Permit the fchmod system call, to avoid crashing on startup when
4100 starting with the seccomp2 sandbox and an unexpected set of
4101 permissions on the data directory or its contents. Fixes bug
4102 22516; bugfix on 0.2.5.4-alpha.
4104 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
4105 - Avoid a double-marked-circuit warning that could happen when we
4106 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
4109 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
4110 - Reject version numbers with non-numeric prefixes (such as +, -, or
4111 whitespace). Disallowing whitespace prevents differential version
4112 parsing between POSIX-based and Windows platforms. Fixes bug 21507
4113 and part of 21508; bugfix on 0.0.8pre1.
4115 o Build features (backport from 0.3.1.5-alpha):
4116 - Tor's repository now includes a Travis Continuous Integration (CI)
4117 configuration file (.travis.yml). This is meant to help new
4118 developers and contributors who fork Tor to a Github repository be
4119 better able to test their changes, and understand what we expect
4120 to pass. To use this new build feature, you must fork Tor to your
4121 Github account, then go into the "Integrations" menu in the
4122 repository settings for your fork and enable Travis, then push
4123 your changes. Closes ticket 22636.
4126 Changes in version 0.3.0.11 - 2017-09-18
4127 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
4130 Most significantly, it includes a fix for TROVE-2017-008, a
4131 security bug that affects hidden services running with the
4132 SafeLogging option disabled. For more information, see
4133 https://trac.torproject.org/projects/tor/ticket/23490
4135 o Minor features (code style, backport from 0.3.1.7):
4136 - Add "Falls through" comments to our codebase, in order to silence
4137 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
4138 Stieger. Closes ticket 22446.
4141 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
4144 o Minor bugfixes (compilation, backport from 0.3.1.7):
4145 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
4146 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
4148 o Minor bugfixes (controller, backport from 0.3.1.7):
4149 - Do not crash when receiving a HSPOST command with an empty body.
4150 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
4151 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
4152 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
4154 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
4155 - When setting the maximum number of connections allowed by the OS,
4156 always allow some extra file descriptors for other files. Fixes
4157 bug 22797; bugfix on 0.2.0.10-alpha.
4159 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
4160 - Remove a forgotten debugging message when an introduction point
4161 successfully establishes a hidden service prop224 circuit with
4163 - Change three other log_warn() for an introduction point to
4164 protocol warnings, because they can be failure from the network
4165 and are not relevant to the operator. Fixes bug 23078; bugfix on
4166 0.3.0.1-alpha and 0.3.0.2-alpha.
4169 Changes in version 0.3.1.7 - 2017-09-18
4170 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
4172 With the 0.3.1 series, Tor now serves and downloads directory
4173 information in more compact formats, to save on bandwidth overhead. It
4174 also contains a new padding system to resist netflow-based traffic
4175 analysis, and experimental support for building parts of Tor in Rust
4176 (though no parts of Tor are in Rust yet). There are also numerous
4177 small features, bugfixes on earlier release series, and groundwork for
4178 the hidden services revamp of 0.3.2.
4180 This release also includes a fix for TROVE-2017-008, a security bug
4181 that affects hidden services running with the SafeLogging option
4182 disabled. For more information, see
4183 https://trac.torproject.org/projects/tor/ticket/23490
4185 Per our stable release policy, we plan to support each stable release
4186 series for at least the next nine months, or for three months after
4187 the first stable release of the next series: whichever is longer. If
4188 you need a release with long-term support, we recommend that you stay
4189 with the 0.2.9 series.
4191 Below is a list of the changes since 0.3.1.6-rc. For a list of all
4192 changes since 0.3.0, see the ReleaseNotes file.
4194 o Major bugfixes (security, hidden services, loggging):
4195 - Fix a bug where we could log uninitialized stack when a certain
4196 hidden service error occurred while SafeLogging was disabled.
4197 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
4198 TROVE-2017-008 and CVE-2017-0380.
4200 o Minor features (defensive programming):
4201 - Create a pair of consensus parameters, nf_pad_tor2web and
4202 nf_pad_single_onion, to disable netflow padding in the consensus
4203 for non-anonymous connections in case the overhead is high. Closes
4206 o Minor features (diagnostic):
4207 - Add a stack trace to the bug warnings that can be logged when
4208 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
4209 attempt for bug 23105.
4211 o Minor features (geoip):
4212 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
4215 o Minor bugfixes (compilation):
4216 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
4217 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
4219 o Minor bugfixes (controller):
4220 - Do not crash when receiving a HSPOST command with an empty body.
4221 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
4222 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
4223 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
4225 o Minor bugfixes (relay):
4226 - Inform the geoip and rephist modules about all requests, even on
4227 relays that are only fetching microdescriptors. Fixes a bug
4228 related to 21585; bugfix on 0.3.0.1-alpha.
4230 o Minor bugfixes (unit tests):
4231 - Fix a channelpadding unit test failure on slow systems by using
4232 mocked time instead of actual time. Fixes bug 23077; bugfix
4236 Changes in version 0.3.1.6-rc - 2017-09-05
4237 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
4238 release series, including a bug that produced weird behavior on
4239 Windows directory caches.
4241 This is the first release candidate in the Tor 0.3.1 series. If we
4242 find no new bugs or regressions here, the first stable 0.3.1 release
4243 will be nearly identical to it.
4245 o Major bugfixes (windows, directory cache):
4246 - On Windows, do not try to delete cached consensus documents and
4247 diffs before they are unmapped from memory--Windows won't allow
4248 that. Instead, allow the consensus cache directory to grow larger,
4249 to hold files that might need to stay around longer. Fixes bug
4250 22752; bugfix on 0.3.1.1-alpha.
4252 o Minor features (directory authority):
4253 - Improve the message that authorities report to relays that present
4254 RSA/Ed25519 keypairs that conflict with previously pinned keys.
4255 Closes ticket 22348.
4257 o Minor features (geoip):
4258 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
4261 o Minor features (testing):
4262 - Add more tests for compression backend initialization. Closes
4265 o Minor bugfixes (directory cache):
4266 - Fix a memory leak when recovering space in the consensus cache.
4267 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
4269 o Minor bugfixes (hidden service):
4270 - Increase the number of circuits that a service is allowed to
4271 open over a specific period of time. The value was lower than it
4272 should be (8 vs 12) in the normal case of 3 introduction points.
4273 Fixes bug 22159; bugfix on 0.3.0.5-rc.
4274 - Fix a BUG warning during HSv3 descriptor decoding that could be
4275 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
4276 on 0.3.0.1-alpha. Bug found by "haxxpop".
4277 - Rate-limit the log messages if we exceed the maximum number of
4278 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
4280 o Minor bugfixes (logging, relay):
4281 - Remove a forgotten debugging message when an introduction point
4282 successfully establishes a hidden service prop224 circuit with
4284 - Change three other log_warn() for an introduction point to
4285 protocol warnings, because they can be failure from the network
4286 and are not relevant to the operator. Fixes bug 23078; bugfix on
4287 0.3.0.1-alpha and 0.3.0.2-alpha.
4289 o Minor bugfixes (relay):
4290 - When a relay is not running as a directory cache, it will no
4291 longer generate compressed consensuses and consensus diff
4292 information. Previously, this was a waste of disk and CPU. Fixes
4293 bug 23275; bugfix on 0.3.1.1-alpha.
4295 o Minor bugfixes (robustness, error handling):
4296 - Improve our handling of the cases where OpenSSL encounters a
4297 memory error while encoding keys and certificates. We haven't
4298 observed these errors in the wild, but if they do happen, we now
4299 detect and respond better. Fixes bug 19418; bugfix on all versions
4300 of Tor. Reported by Guido Vranken.
4302 o Minor bugfixes (stability):
4303 - Avoid crashing on a double-free when unable to load or process an
4304 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
4305 with the clang static analyzer.
4307 o Minor bugfixes (testing):
4308 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4309 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4310 - Port the hs_ntor handshake test to work correctly with recent
4311 versions of the pysha3 module. Fixes bug 23071; bugfix
4314 o Minor bugfixes (Windows service):
4315 - When running as a Windows service, set the ID of the main thread
4316 correctly. Failure to do so made us fail to send log messages to
4317 the controller in 0.2.1.16-rc, slowed down controller event
4318 delivery in 0.2.7.3-rc and later, and crash with an assertion
4319 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
4320 Patch and diagnosis from "Vort".
4323 Changes in version 0.3.0.10 - 2017-08-02
4324 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
4325 from the current Tor alpha series. OpenBSD users and TPROXY users
4326 should upgrade; others are probably okay sticking with 0.3.0.9.
4328 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
4329 - Tor's repository now includes a Travis Continuous Integration (CI)
4330 configuration file (.travis.yml). This is meant to help new
4331 developers and contributors who fork Tor to a Github repository be
4332 better able to test their changes, and understand what we expect
4333 to pass. To use this new build feature, you must fork Tor to your
4334 Github account, then go into the "Integrations" menu in the
4335 repository settings for your fork and enable Travis, then push
4336 your changes. Closes ticket 22636.
4338 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
4339 - Fix a typo that had prevented TPROXY-based transparent proxying
4340 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
4341 Patch from "d4fq0fQAgoJ".
4343 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
4344 - Avoid an assertion failure bug affecting our implementation of
4345 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
4346 handling of "0xbar" differs from what we had expected. Fixes bug
4347 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
4349 o Minor features (backport from 0.3.1.5-alpha):
4350 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
4353 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
4354 - Roll over monthly accounting at the configured hour and minute,
4355 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
4356 Found by Andrey Karpov with PVS-Studio.
4358 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
4359 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
4360 bugfix on 0.2.8.1-alpha.
4361 - Fix warnings when building with libscrypt and openssl scrypt
4362 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
4363 - When building with certain versions of the mingw C header files,
4364 avoid float-conversion warnings when calling the C functions
4365 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
4368 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
4369 - Backport a fix for an "unused variable" warning that appeared
4370 in some versions of mingw. Fixes bug 22838; bugfix on
4373 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
4374 - Avoid Coverity build warnings related to our BUG() macro. By
4375 default, Coverity treats BUG() as the Linux kernel does: an
4376 instant abort(). We need to override that so our BUG() macro
4377 doesn't prevent Coverity from analyzing functions that use it.
4378 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
4380 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
4381 - When rejecting a router descriptor for running an obsolete version
4382 of Tor without ntor support, warn about the obsolete tor version,
4383 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
4385 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
4386 - Avoid a sandbox failure when trying to re-bind to a socket and
4387 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
4389 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
4390 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
4391 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
4394 Changes in version 0.3.1.5-alpha - 2017-08-01
4395 Tor 0.3.1.5-alpha improves the performance of consensus diff
4396 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
4397 several other bugs. If no serious bugs are found in this version, the
4398 next version will be a release candidate.
4400 This release also marks the end of support for the Tor 0.2.4.x,
4401 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
4402 further bug or security fixes. Anyone still running or distributing
4403 one of those versions should upgrade.
4405 o Major features (build system, continuous integration):
4406 - Tor's repository now includes a Travis Continuous Integration (CI)
4407 configuration file (.travis.yml). This is meant to help new
4408 developers and contributors who fork Tor to a Github repository be
4409 better able to test their changes, and understand what we expect
4410 to pass. To use this new build feature, you must fork Tor to your
4411 Github account, then go into the "Integrations" menu in the
4412 repository settings for your fork and enable Travis, then push
4413 your changes. Closes ticket 22636.
4415 o Major bugfixes (openbsd, denial-of-service):
4416 - Avoid an assertion failure bug affecting our implementation of
4417 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
4418 handling of "0xbar" differs from what we had expected. Fixes bug
4419 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
4421 o Major bugfixes (relay, performance):
4422 - Perform circuit handshake operations at a higher priority than we
4423 use for consensus diff creation and compression. This should
4424 prevent circuits from starving when a relay or bridge receives a
4425 new consensus, especially on lower-powered machines. Fixes bug
4426 22883; bugfix on 0.3.1.1-alpha.
4428 o Minor features (bridge authority):
4429 - Add "fingerprint" lines to the networkstatus-bridges file produced
4430 by bridge authorities. Closes ticket 22207.
4432 o Minor features (directory cache, consensus diff):
4433 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
4434 operators with low-resource environments to adjust the number of
4435 consensuses they'll store and generate diffs from. Most cache
4436 operators should leave it unchanged. Helps to work around
4439 o Minor features (geoip):
4440 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
4443 o Minor features (relay, performance):
4444 - Always start relays with at least two worker threads, to prevent
4445 priority inversion on slow tasks. Part of the fix for bug 22883.
4446 - Allow background work to be queued with different priorities, so
4447 that a big pile of slow low-priority jobs will not starve out
4448 higher priority jobs. This lays the groundwork for a fix for
4451 o Minor bugfixes (build system, rust):
4452 - Fix a problem where Rust toolchains were not being found when
4453 building without --enable-cargo-online-mode, due to setting the
4454 $HOME environment variable instead of $CARGO_HOME. Fixes bug
4455 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
4457 o Minor bugfixes (compatibility, zstd):
4458 - Write zstd epilogues correctly when the epilogue requires
4459 reallocation of the output buffer, even with zstd 1.3.0.
4460 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
4461 22927; bugfix on 0.3.1.1-alpha.
4463 o Minor bugfixes (compilation warnings):
4464 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
4465 22915; bugfix on 0.2.8.1-alpha.
4466 - Fix warnings when building with libscrypt and openssl scrypt
4467 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
4468 - Compile correctly when both openssl 1.1.0 and libscrypt are
4469 detected. Previously this would cause an error. Fixes bug 22892;
4470 bugfix on 0.3.1.1-alpha.
4471 - When building with certain versions of the mingw C header files,
4472 avoid float-conversion warnings when calling the C functions
4473 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
4476 o Minor bugfixes (coverity build support):
4477 - Avoid Coverity build warnings related to our BUG() macro. By
4478 default, Coverity treats BUG() as the Linux kernel does: an
4479 instant abort(). We need to override that so our BUG() macro
4480 doesn't prevent Coverity from analyzing functions that use it.
4481 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
4483 o Minor bugfixes (directory authority):
4484 - When a directory authority rejects a descriptor or extrainfo with
4485 a given digest, mark that digest as undownloadable, so that we do
4486 not attempt to download it again over and over. We previously
4487 tried to avoid downloading such descriptors by other means, but we
4488 didn't notice if we accidentally downloaded one anyway. This
4489 behavior became problematic in 0.2.7.2-alpha, when authorities
4490 began pinning Ed25519 keys. Fixes bug 22349; bugfix
4493 o Minor bugfixes (error reporting, windows):
4494 - When formatting Windows error messages, use the English format to
4495 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
4498 o Minor bugfixes (file limits, osx):
4499 - When setting the maximum number of connections allowed by the OS,
4500 always allow some extra file descriptors for other files. Fixes
4501 bug 22797; bugfix on 0.2.0.10-alpha.
4503 o Minor bugfixes (linux seccomp2 sandbox):
4504 - Avoid a sandbox failure when trying to re-bind to a socket and
4505 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
4507 o Minor bugfixes (memory leaks):
4508 - Fix a small memory leak when validating a configuration that uses
4509 two or more AF_UNIX sockets for the same port type. Fixes bug
4510 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
4512 o Minor bugfixes (unit tests):
4513 - test_consdiff_base64cmp would fail on OS X because while OS X
4514 follows the standard of (less than zero/zero/greater than zero),
4515 it doesn't follow the convention of (-1/0/+1). Make the test
4516 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
4517 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
4518 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
4521 Changes in version 0.3.1.4-alpha - 2017-06-29
4522 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
4523 to use a guard that was in the same network family as a chosen exit
4524 relay. This is a security regression; all clients running earlier
4525 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
4528 This release also fixes several other bugs introduced in 0.3.0.x
4529 and 0.3.1.x, including others that can affect bandwidth usage
4533 - To build with zstd and lzma support, Tor now requires the
4534 pkg-config tool at build time. (This requirement was new in
4535 0.3.1.1-alpha, but was not noted at the time. Noting it here to
4536 close ticket 22623.)
4538 o Major bugfixes (path selection, security):
4539 - When choosing which guard to use for a circuit, avoid the exit's
4540 family along with the exit itself. Previously, the new guard
4541 selection logic avoided the exit, but did not consider its family.
4542 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
4543 006 and CVE-2017-0377.
4545 o Major bugfixes (compression, zstd):
4546 - Correctly detect a full buffer when decompressing a large zstd-
4547 compressed input. Previously, we would sometimes treat a full
4548 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
4550 o Major bugfixes (directory protocol):
4551 - Ensure that we send "304 Not modified" as HTTP status code when a
4552 client is attempting to fetch a consensus or consensus diff, and
4553 the best one we can send them is one they already have. Fixes bug
4554 22702; bugfix on 0.3.1.1-alpha.
4556 o Major bugfixes (entry guards):
4557 - When starting with an old consensus, do not add new entry guards
4558 unless the consensus is "reasonably live" (under 1 day old). Fixes
4559 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
4561 o Minor features (bug mitigation, diagnostics, logging):
4562 - Avoid an assertion failure, and log a better error message, when
4563 unable to remove a file from the consensus cache on Windows.
4564 Attempts to mitigate and diagnose bug 22752.
4566 o Minor features (geoip):
4567 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
4570 o Minor bugfixes (compression):
4571 - When compressing or decompressing a buffer, check for a failure to
4572 create a compression object. Fixes bug 22626; bugfix
4574 - When decompressing a buffer, check for extra data after the end of
4575 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
4576 - When decompressing an object received over an anonymous directory
4577 connection, if we have already decompressed it using an acceptable
4578 compression method, do not reject it for looking like an
4579 unacceptable compression method. Fixes part of bug 22670; bugfix
4581 - When serving directory votes compressed with zlib, do not claim to
4582 have compressed them with zstd. Fixes bug 22669; bugfix
4584 - When spooling compressed data to an output buffer, don't try to
4585 spool more data when there is no more data to spool and we are not
4586 trying to flush the input. Previously, we would sometimes launch
4587 compression requests with nothing to do, which interferes with our
4588 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
4590 o Minor bugfixes (defensive programming):
4591 - Detect and break out of infinite loops in our compression code. We
4592 don't think that any such loops exist now, but it's best to be
4593 safe. Closes ticket 22672.
4594 - Fix a memset() off the end of an array when packing cells. This
4595 bug should be harmless in practice, since the corrupted bytes are
4596 still in the same structure, and are always padding bytes,
4597 ignored, or immediately overwritten, depending on compiler
4598 behavior. Nevertheless, because the memset()'s purpose is to make
4599 sure that any other cell-handling bugs can't expose bytes to the
4600 network, we need to fix it. Fixes bug 22737; bugfix on
4601 0.2.4.11-alpha. Fixes CID 1401591.
4603 o Minor bugfixes (linux seccomp2 sandbox):
4604 - Permit the fchmod system call, to avoid crashing on startup when
4605 starting with the seccomp2 sandbox and an unexpected set of
4606 permissions on the data directory or its contents. Fixes bug
4607 22516; bugfix on 0.2.5.4-alpha.
4608 - Fix a crash in the LZMA module, when the sandbox was enabled, and
4609 liblzma would allocate more than 16 MB of memory. We solve this by
4610 bumping the mprotect() limit in the sandbox module from 16 MB to
4611 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
4613 o Minor bugfixes (logging):
4614 - When decompressing, do not warn if we fail to decompress using a
4615 compression method that we merely guessed. Fixes part of bug
4616 22670; bugfix on 0.1.1.14-alpha.
4617 - When decompressing, treat mismatch between content-encoding and
4618 actual compression type as a protocol warning. Fixes part of bug
4619 22670; bugfix on 0.1.1.9-alpha.
4620 - Downgrade "assigned_to_cpuworker failed" message to info-level
4621 severity. In every case that can reach it, either a better warning
4622 has already been logged, or no warning is warranted. Fixes bug
4623 22356; bugfix on 0.2.6.3-alpha.
4624 - Demote a warn that was caused by libevent delays to info if
4625 netflow padding is less than 4.5 seconds late, or to notice
4626 if it is more (4.5 seconds is the amount of time that a netflow
4627 record might be emitted after, if we chose the maximum timeout).
4628 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
4630 o Minor bugfixes (process behavior):
4631 - When exiting because of an error, always exit with a nonzero exit
4632 status. Previously, we would fail to report an error in our exit
4633 status in cases related to __OwningControllerProcess failure,
4634 lockfile contention, and Ed25519 key initialization. Fixes bug
4635 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
4636 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
4640 - Add a manpage description for the key-pinning-journal file. Closes
4642 - Correctly note that bandwidth accounting values are stored in the
4643 state file, and the bw_accounting file is now obsolete. Closes
4645 - Document more of the files in the Tor data directory, including
4646 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
4647 approved-routers, sr-random, and diff-cache. Found while fixing
4651 Changes in version 0.3.0.9 - 2017-06-29
4652 Tor 0.3.0.9 fixes a path selection bug that would allow a client
4653 to use a guard that was in the same network family as a chosen exit
4654 relay. This is a security regression; all clients running earlier
4655 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
4658 This release also backports several other bugfixes from the 0.3.1.x
4661 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
4662 - When choosing which guard to use for a circuit, avoid the exit's
4663 family along with the exit itself. Previously, the new guard
4664 selection logic avoided the exit, but did not consider its family.
4665 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
4666 006 and CVE-2017-0377.
4668 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
4669 - Don't block bootstrapping when a primary bridge is offline and we
4670 can't get its descriptor. Fixes bug 22325; fixes one case of bug
4671 21969; bugfix on 0.3.0.3-alpha.
4673 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
4674 - When starting with an old consensus, do not add new entry guards
4675 unless the consensus is "reasonably live" (under 1 day old). Fixes
4676 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
4678 o Minor features (geoip):
4679 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
4682 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
4683 - Reject version numbers with non-numeric prefixes (such as +, -, or
4684 whitespace). Disallowing whitespace prevents differential version
4685 parsing between POSIX-based and Windows platforms. Fixes bug 21507
4686 and part of 21508; bugfix on 0.0.8pre1.
4688 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
4689 - Permit the fchmod system call, to avoid crashing on startup when
4690 starting with the seccomp2 sandbox and an unexpected set of
4691 permissions on the data directory or its contents. Fixes bug
4692 22516; bugfix on 0.2.5.4-alpha.
4694 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
4695 - Fix a memset() off the end of an array when packing cells. This
4696 bug should be harmless in practice, since the corrupted bytes are
4697 still in the same structure, and are always padding bytes,
4698 ignored, or immediately overwritten, depending on compiler
4699 behavior. Nevertheless, because the memset()'s purpose is to make
4700 sure that any other cell-handling bugs can't expose bytes to the
4701 network, we need to fix it. Fixes bug 22737; bugfix on
4702 0.2.4.11-alpha. Fixes CID 1401591.
4705 Changes in version 0.3.1.3-alpha - 2017-06-08
4706 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
4707 remotely crash a hidden service with an assertion failure. Anyone
4708 running a hidden service should upgrade to this version, or to some
4709 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
4711 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
4712 that sometimes made relays unreliable, as well as several other
4713 bugfixes described below.
4715 o Major bugfixes (hidden service, relay, security):
4716 - Fix a remotely triggerable assertion failure when a hidden service
4717 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
4718 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
4719 - Fix a remotely triggerable assertion failure caused by receiving a
4720 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4721 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4724 o Major bugfixes (relay, link handshake):
4725 - When performing the v3 link handshake on a TLS connection, report
4726 that we have the x509 certificate that we actually used on that
4727 connection, even if we have changed certificates since that
4728 connection was first opened. Previously, we would claim to have
4729 used our most recent x509 link certificate, which would sometimes
4730 make the link handshake fail. Fixes one case of bug 22460; bugfix
4733 o Major bugfixes (relays, key management):
4734 - Regenerate link and authentication certificates whenever the key
4735 that signs them changes; also, regenerate link certificates
4736 whenever the signed key changes. Previously, these processes were
4737 only weakly coupled, and we relays could (for minutes to hours)
4738 wind up with an inconsistent set of keys and certificates, which
4739 other relays would not accept. Fixes two cases of bug 22460;
4740 bugfix on 0.3.0.1-alpha.
4741 - When sending an Ed25519 signing->link certificate in a CERTS cell,
4742 send the certificate that matches the x509 certificate that we
4743 used on the TLS connection. Previously, there was a race condition
4744 if the TLS context rotated after we began the TLS handshake but
4745 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
4748 o Major bugfixes (torrc, crash):
4749 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
4750 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
4752 o Minor features (code style):
4753 - Add "Falls through" comments to our codebase, in order to silence
4754 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
4755 Stieger. Closes ticket 22446.
4757 o Minor features (diagnostic):
4758 - Add logging messages to try to diagnose a rare bug that seems to
4759 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
4760 think this is happening because of incorrect system clocks, but
4761 we'd like to know for certain. Diagnostic for bug 22466.
4763 o Minor bugfixes (correctness):
4764 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4765 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4767 o Minor bugfixes (directory protocol):
4768 - Check for libzstd >= 1.1, because older versions lack the
4769 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
4771 o Minor bugfixes (link handshake):
4772 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
4773 months, and regenerate it when it is within one month of expiring.
4774 Previously, we had generated this certificate at startup with a
4775 ten-year lifetime, but that could lead to weird behavior when Tor
4776 was started with a grossly inaccurate clock. Mitigates bug 22466;
4777 mitigation on 0.3.0.1-alpha.
4779 o Minor bugfixes (storage directories):
4780 - Always check for underflows in the cached storage directory usage.
4781 If the usage does underflow, re-calculate it. Also, avoid a
4782 separate underflow when the usage is not known. Fixes bug 22424;
4783 bugfix on 0.3.1.1-alpha.
4785 o Minor bugfixes (unit tests):
4786 - The unit tests now pass on systems where localhost is misconfigured
4787 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
4791 - Clarify the manpage for the (deprecated) torify script. Closes
4794 Changes in version 0.3.0.8 - 2017-06-08
4795 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
4796 remotely crash a hidden service with an assertion failure. Anyone
4797 running a hidden service should upgrade to this version, or to some
4798 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
4800 Tor 0.3.0.8 also includes fixes for several key management bugs
4801 that sometimes made relays unreliable, as well as several other
4802 bugfixes described below.
4804 o Major bugfixes (hidden service, relay, security, backport
4805 from 0.3.1.3-alpha):
4806 - Fix a remotely triggerable assertion failure when a hidden service
4807 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
4808 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
4809 - Fix a remotely triggerable assertion failure caused by receiving a
4810 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4811 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4814 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
4815 - When performing the v3 link handshake on a TLS connection, report
4816 that we have the x509 certificate that we actually used on that
4817 connection, even if we have changed certificates since that
4818 connection was first opened. Previously, we would claim to have
4819 used our most recent x509 link certificate, which would sometimes
4820 make the link handshake fail. Fixes one case of bug 22460; bugfix
4823 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
4824 - Regenerate link and authentication certificates whenever the key
4825 that signs them changes; also, regenerate link certificates
4826 whenever the signed key changes. Previously, these processes were
4827 only weakly coupled, and we relays could (for minutes to hours)
4828 wind up with an inconsistent set of keys and certificates, which
4829 other relays would not accept. Fixes two cases of bug 22460;
4830 bugfix on 0.3.0.1-alpha.
4831 - When sending an Ed25519 signing->link certificate in a CERTS cell,
4832 send the certificate that matches the x509 certificate that we
4833 used on the TLS connection. Previously, there was a race condition
4834 if the TLS context rotated after we began the TLS handshake but
4835 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
4838 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
4839 - Stop rejecting v3 hidden service descriptors because their size
4840 did not match an old padding rule. Fixes bug 22447; bugfix on
4843 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4844 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4845 December 2016 (of which ~126 were still functional) with a list of
4846 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4847 2017. Resolves ticket 21564.
4849 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
4850 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
4851 bug 22252; bugfix on 0.2.9.3-alpha.
4853 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
4854 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4855 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4857 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
4858 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
4859 months, and regenerate it when it is within one month of expiring.
4860 Previously, we had generated this certificate at startup with a
4861 ten-year lifetime, but that could lead to weird behavior when Tor
4862 was started with a grossly inaccurate clock. Mitigates bug 22466;
4863 mitigation on 0.3.0.1-alpha.
4865 o Minor bugfixes (memory leak, directory authority, backport from
4867 - When directory authorities reject a router descriptor due to
4868 keypinning, free the router descriptor rather than leaking the
4869 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4872 Changes in version 0.2.9.11 - 2017-06-08
4873 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
4874 remotely crash a hidden service with an assertion failure. Anyone
4875 running a hidden service should upgrade to this version, or to some
4876 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4877 are not affected by TROVE-2017-004.)
4879 Tor 0.2.9.11 also backports fixes for several key management bugs
4880 that sometimes made relays unreliable, as well as several other
4881 bugfixes described below.
4883 o Major bugfixes (hidden service, relay, security, backport
4884 from 0.3.1.3-alpha):
4885 - Fix a remotely triggerable assertion failure caused by receiving a
4886 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4887 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4890 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
4891 - When performing the v3 link handshake on a TLS connection, report
4892 that we have the x509 certificate that we actually used on that
4893 connection, even if we have changed certificates since that
4894 connection was first opened. Previously, we would claim to have
4895 used our most recent x509 link certificate, which would sometimes
4896 make the link handshake fail. Fixes one case of bug 22460; bugfix
4899 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4900 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4901 December 2016 (of which ~126 were still functional) with a list of
4902 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4903 2017. Resolves ticket 21564.
4905 o Minor features (future-proofing, backport from 0.3.0.7):
4906 - Tor no longer refuses to download microdescriptors or descriptors if
4907 they are listed as "published in the future". This change will
4908 eventually allow us to stop listing meaningful "published" dates
4909 in microdescriptor consensuses, and thereby allow us to reduce the
4910 resources required to download consensus diffs by over 50%.
4911 Implements part of ticket 21642; implements part of proposal 275.
4913 o Minor features (directory authorities, backport from 0.3.0.4-rc)
4914 - Directory authorities now reject relays running versions
4915 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
4916 suffer from bug 20499 and don't keep their consensus cache
4917 up-to-date. Resolves ticket 20509.
4919 o Minor features (geoip):
4920 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4923 o Minor bugfixes (control port, backport from 0.3.0.6):
4924 - The GETINFO extra-info/digest/<digest> command was broken because
4925 of a wrong base16 decode return value check, introduced when
4926 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
4928 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
4929 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4930 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4932 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
4933 - The getpid() system call is now permitted under the Linux seccomp2
4934 sandbox, to avoid crashing with versions of OpenSSL (and other
4935 libraries) that attempt to learn the process's PID by using the
4936 syscall rather than the VDSO code. Fixes bug 21943; bugfix
4939 o Minor bugfixes (memory leak, directory authority, backport
4940 from 0.3.1.2-alpha):
4941 - When directory authorities reject a router descriptor due to
4942 keypinning, free the router descriptor rather than leaking the
4943 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
4945 Changes in version 0.2.8.14 - 2017-06-08
4946 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4947 remotely crash a hidden service with an assertion failure. Anyone
4948 running a hidden service should upgrade to this version, or to some
4949 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4950 are not affected by TROVE-2017-004.)
4952 o Major bugfixes (hidden service, relay, security):
4953 - Fix a remotely triggerable assertion failure caused by receiving a
4954 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4955 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4958 o Minor features (geoip):
4959 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4962 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
4963 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
4964 December 2016 (of which ~126 were still functional) with a list of
4965 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
4966 2017. Resolves ticket 21564.
4968 o Minor bugfixes (correctness):
4969 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4970 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4972 Changes in version 0.2.7.8 - 2017-06-08
4973 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
4974 remotely crash a hidden service with an assertion failure. Anyone
4975 running a hidden service should upgrade to this version, or to some
4976 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4977 are not affected by TROVE-2017-004.)
4979 o Major bugfixes (hidden service, relay, security):
4980 - Fix a remotely triggerable assertion failure caused by receiving a
4981 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
4982 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
4985 o Minor features (geoip):
4986 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
4989 o Minor bugfixes (correctness):
4990 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
4991 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
4994 Changes in version 0.2.6.12 - 2017-06-08
4995 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
4996 remotely crash a hidden service with an assertion failure. Anyone
4997 running a hidden service should upgrade to this version, or to some
4998 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
4999 are not affected by TROVE-2017-004.)
5001 o Major bugfixes (hidden service, relay, security):
5002 - Fix a remotely triggerable assertion failure caused by receiving a
5003 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
5004 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
5007 o Minor features (geoip):
5008 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
5011 o Minor bugfixes (correctness):
5012 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
5013 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
5015 Changes in version 0.2.5.14 - 2017-06-08
5016 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
5017 remotely crash a hidden service with an assertion failure. Anyone
5018 running a hidden service should upgrade to this version, or to some
5019 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
5020 are not affected by TROVE-2017-004.)
5022 o Major bugfixes (hidden service, relay, security):
5023 - Fix a remotely triggerable assertion failure caused by receiving a
5024 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
5025 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
5028 o Minor features (geoip):
5029 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
5032 o Minor bugfixes (correctness):
5033 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
5034 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
5036 Changes in version 0.2.4.29 - 2017-06-08
5037 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
5038 remotely crash a hidden service with an assertion failure. Anyone
5039 running a hidden service should upgrade to this version, or to some
5040 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
5041 are not affected by TROVE-2017-004.)
5043 o Major bugfixes (hidden service, relay, security):
5044 - Fix a remotely triggerable assertion failure caused by receiving a
5045 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
5046 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
5049 o Minor features (geoip):
5050 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
5053 o Minor bugfixes (correctness):
5054 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
5055 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
5058 Changes in version 0.3.1.2-alpha - 2017-05-26
5059 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
5060 fixes a few bugs found while testing 0.3.1.1-alpha, including a
5061 memory corruption bug that affected relay stability.
5063 o Major bugfixes (crash, relay):
5064 - Fix a memory-corruption bug in relays that set MyFamily.
5065 Previously, they would double-free MyFamily elements when making
5066 the next descriptor or when changing their configuration. Fixes
5067 bug 22368; bugfix on 0.3.1.1-alpha.
5069 o Minor bugfixes (logging):
5070 - Log a better message when a directory authority replies to an
5071 upload with an unexpected status code. Fixes bug 11121; bugfix
5074 o Minor bugfixes (memory leak, directory authority):
5075 - When directory authorities reject a router descriptor due to
5076 keypinning, free the router descriptor rather than leaking the
5077 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
5080 Changes in version 0.3.1.1-alpha - 2017-05-22
5081 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
5082 reduces the bandwidth usage for Tor's directory protocol, adds some
5083 basic padding to resist netflow-based traffic analysis and to serve as
5084 the basis of other padding in the future, and adds rust support to the
5087 It also contains numerous other small features and improvements to
5088 security, correctness, and performance.
5090 Below are the changes since 0.3.0.7.
5092 o Major features (directory protocol):
5093 - Tor relays and authorities can now serve clients an abbreviated
5094 version of the consensus document, containing only the changes
5095 since an older consensus document that the client holds. Clients
5096 now request these documents when available. When both client and
5097 server use this new protocol, they will use far less bandwidth (up
5098 to 94% less) to keep the client's consensus up-to-date. Implements
5099 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
5100 - Tor can now compress directory traffic with lzma or with zstd
5101 compression algorithms, which can deliver better bandwidth
5102 performance. Because lzma is computationally expensive, it's only
5103 used for documents that can be compressed once and served many
5104 times. Support for these algorithms requires that tor is built
5105 with the libzstd and/or liblzma libraries available. Implements
5106 proposal 278; closes ticket 21662.
5107 - Relays now perform the more expensive compression operations, and
5108 consensus diff generation, in worker threads. This separation
5109 avoids delaying the main thread when a new consensus arrives.
5111 o Major features (experimental):
5112 - Tor can now build modules written in Rust. To turn this on, pass
5113 the "--enable-rust" flag to the configure script. It's not time to
5114 get excited yet: currently, there is no actual Rust functionality
5115 beyond some simple glue code, and a notice at startup to tell you
5116 that Rust is running. Still, we hope that programmers and
5117 packagers will try building Tor with Rust support, so that we can
5118 find issues and solve portability problems. Closes ticket 22106.
5120 o Major features (traffic analysis resistance):
5121 - Connections between clients and relays now send a padding cell in
5122 each direction every 1.5 to 9.5 seconds (tunable via consensus
5123 parameters). This padding will not resist specialized
5124 eavesdroppers, but it should be enough to make many ISPs' routine
5125 network flow logging less useful in traffic analysis against
5128 Padding is negotiated using Tor's link protocol, so both relays
5129 and clients must upgrade for this to take effect. Clients may
5130 still send padding despite the relay's version by setting
5131 ConnectionPadding 1 in torrc, and may disable padding by setting
5132 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
5133 users with the torrc option ReducedConnectionPadding. Implements
5134 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
5135 - Relays will publish 24 hour totals of padding and non-padding cell
5136 counts to their extra-info descriptors, unless PaddingStatistics 0
5137 is set in torrc. These 24 hour totals are also rounded to
5140 o Major bugfixes (connection usage):
5141 - We use NETINFO cells to try to determine if both relays involved
5142 in a connection will agree on the canonical status of that
5143 connection. We prefer the connections where this is the case for
5144 extend cells, and try to close connections where relays disagree
5145 on their canonical status early. Also, we now prefer the oldest
5146 valid connection for extend cells. These two changes should reduce
5147 the number of long-term connections that are kept open between
5148 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
5149 - Relays now log hourly statistics (look for
5150 "channel_check_for_duplicates" lines) on the total number of
5151 connections to other relays. If the number of connections per
5152 relay is unexpectedly large, this log message is at notice level.
5153 Otherwise it is at info.
5155 o Major bugfixes (entry guards):
5156 - Don't block bootstrapping when a primary bridge is offline and we
5157 can't get its descriptor. Fixes bug 22325; fixes one case of bug
5158 21969; bugfix on 0.3.0.3-alpha.
5160 o Major bugfixes (linux TPROXY support):
5161 - Fix a typo that had prevented TPROXY-based transparent proxying
5162 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
5163 Patch from "d4fq0fQAgoJ".
5165 o Minor features (security, windows):
5166 - Enable a couple of pieces of Windows hardening: one
5167 (HeapEnableTerminationOnCorruption) that has been on-by-default
5168 since Windows 8, and unavailable before Windows 7; and one
5169 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
5170 affect us, but shouldn't do any harm. Closes ticket 21953.
5172 o Minor features (config options):
5173 - Allow "%include" directives in torrc configuration files. These
5174 directives import the settings from other files, or from all the
5175 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
5176 - Make SAVECONF return an error when overwriting a torrc that has
5177 includes. Using SAVECONF with the FORCE option will allow it to
5178 overwrite torrc even if includes are used. Related to ticket 1922.
5179 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
5180 will work without the FORCE option. Related to ticket 1922.
5182 o Minor features (controller):
5183 - Warn the first time that a controller requests data in the long-
5184 deprecated 'GETINFO network-status' format. Closes ticket 21703.
5186 o Minor features (defaults):
5187 - The default value for UseCreateFast is now 0: clients which
5188 haven't yet received a consensus document will now use a proper
5189 ntor handshake to talk to their directory servers whenever they
5190 can. Closes ticket 21407.
5191 - Onion key rotation and expiry intervals are now defined as a
5192 network consensus parameter, per proposal 274. The default
5193 lifetime of an onion key is increased from 7 to 28 days. Old onion
5194 keys will expire after 7 days by default. This change will make
5195 consensus diffs much smaller, and save significant bandwidth.
5196 Closes ticket 21641.
5198 o Minor features (fallback directory list):
5199 - Update the fallback directory mirror whitelist and blacklist based
5200 on operator emails. Closes task 21121.
5201 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
5202 December 2016 (of which ~126 were still functional) with a list of
5203 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
5204 2017. Resolves ticket 21564.
5206 o Minor features (hidden services, logging):
5207 - Log a message when a hidden service descriptor has fewer
5208 introduction points than specified in
5209 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
5210 - Log a message when a hidden service reaches its introduction point
5211 circuit limit, and when that limit is reset. Follow up to ticket
5212 21594; closes ticket 21622.
5213 - Warn user if multiple entries in EntryNodes and at least one
5214 HiddenService are used together. Pinning EntryNodes along with a
5215 hidden service can be possibly harmful; for instance see ticket
5216 14917 or 21155. Closes ticket 21155.
5218 o Minor features (linux seccomp2 sandbox):
5219 - We now have a document storage backend compatible with the Linux
5220 seccomp2 sandbox. This backend is used for consensus documents and
5221 diffs between them; in the long term, we'd like to use it for
5222 unparseable directory material too. Closes ticket 21645
5223 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
5224 from 1MB to 16MB. This was necessary with the glibc allocator in
5225 order to allow worker threads to allocate more memory -- which in
5226 turn is necessary because of our new use of worker threads for
5227 compression. Closes ticket 22096.
5229 o Minor features (logging):
5230 - Log files are no longer created world-readable by default.
5231 (Previously, most distributors would store the logs in a non-
5232 world-readable location to prevent inappropriate access. This
5233 change is an extra precaution.) Closes ticket 21729; patch
5236 o Minor features (performance):
5237 - Our Keccak (SHA-3) implementation now accesses memory more
5238 efficiently, especially on little-endian systems. Closes
5240 - Add an O(1) implementation of channel_find_by_global_id(), to
5241 speed some controller functions.
5243 o Minor features (relay, configuration):
5244 - The MyFamily option may now be repeated as many times as desired,
5245 for relays that want to configure large families. Closes ticket
5246 4998; patch by Daniel Pinto.
5248 o Minor features (safety):
5249 - Add an explicit check to extrainfo_parse_entry_from_string() for
5250 NULL inputs. We don't believe this can actually happen, but it may
5251 help silence a warning from the Clang analyzer. Closes
5254 o Minor features (testing):
5255 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
5256 When Tor is compiled with this option, we disable a number of
5257 redundant memory-safety failsafes that are intended to stop bugs
5258 from becoming security issues. This makes it easier to hunt for
5259 bugs that would be security issues without the failsafes turned
5260 on. Closes ticket 21439.
5261 - Add a general event-tracing instrumentation support to Tor. This
5262 subsystem will enable developers and researchers to add fine-
5263 grained instrumentation to their Tor instances, for use when
5264 examining Tor network performance issues. There are no trace
5265 events yet, and event-tracing is off by default unless enabled at
5266 compile time. Implements ticket 13802.
5267 - Improve our version parsing tests: add tests for typical version
5268 components, add tests for invalid versions, including numeric
5269 range and non-numeric prefixes. Unit tests 21278, 21450, and
5270 21507. Partially implements 21470.
5272 o Minor bugfixes (bandwidth accounting):
5273 - Roll over monthly accounting at the configured hour and minute,
5274 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
5275 Found by Andrey Karpov with PVS-Studio.
5277 o Minor bugfixes (code correctness):
5278 - Accurately identify client connections by their lack of peer
5279 authentication. This means that we bail out earlier if asked to
5280 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
5283 o Minor bugfixes (configuration):
5284 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
5285 bug 22252; bugfix on 0.2.9.3-alpha.
5287 o Minor bugfixes (connection lifespan):
5288 - Allow more control over how long TLS connections are kept open:
5289 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
5290 single option called CircuitsAvailableTimeout. Also, allow the
5291 consensus to control the default values for both this preference
5292 and the lifespan of relay-to-relay connections. Fixes bug 17592;
5293 bugfix on 0.2.5.5-alpha.
5294 - Increase the initial circuit build timeout testing frequency, to
5295 help ensure that ReducedConnectionPadding clients finish learning
5296 a timeout before their orconn would expire. The initial testing
5297 rate was set back in the days of TAP and before the Tor Browser
5298 updater, when we had to be much more careful about new clients
5299 making lots of circuits. With this change, a circuit build timeout
5300 is learned in about 15-20 minutes, instead of 100-120 minutes.
5302 o Minor bugfixes (controller):
5303 - GETINFO onions/current and onions/detached no longer respond with
5304 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
5305 - Trigger HS descriptor events on the control port when the client
5306 fails to pick a hidden service directory for a hidden service.
5307 This can happen if all the hidden service directories are in
5308 ExcludeNodes, or they have all been queried within the last 15
5309 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
5311 o Minor bugfixes (directory authority):
5312 - When rejecting a router descriptor for running an obsolete version
5313 of Tor without ntor support, warn about the obsolete tor version,
5314 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
5315 - Prevent the shared randomness subsystem from asserting when
5316 initialized by a bridge authority with an incomplete configuration
5317 file. Fixes bug 21586; bugfix on 0.2.9.8.
5319 o Minor bugfixes (exit-side DNS):
5320 - Fix an untriggerable assertion that checked the output of a
5321 libevent DNS error, so that the assertion actually behaves as
5322 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
5323 Karpov using PVS-Studio.
5325 o Minor bugfixes (fallback directories):
5326 - Make the usage example in updateFallbackDirs.py actually work, and
5327 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
5328 - Decrease the guard flag average required to be a fallback. This
5329 allows us to keep relays that have their guard flag removed when
5330 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
5331 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
5332 bugfix on 0.2.8.1-alpha.
5333 - Make sure fallback directory mirrors have the same address, port,
5334 and relay identity key for at least 30 days before they are
5335 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
5337 o Minor bugfixes (hidden services):
5338 - Stop printing a cryptic warning when a hidden service gets a
5339 request to connect to a virtual port that it hasn't configured.
5340 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
5341 - Simplify hidden service descriptor creation by using an existing
5342 flag to check if an introduction point is established. Fixes bug
5343 21599; bugfix on 0.2.7.2-alpha.
5345 o Minor bugfixes (memory leak):
5346 - Fix a small memory leak at exit from the backtrace handler code.
5347 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
5349 o Minor bugfixes (protocol, logging):
5350 - Downgrade a log statement about unexpected relay cells from "bug"
5351 to "protocol warning", because there is at least one use case
5352 where it can be triggered by a buggy tor implementation. Fixes bug
5353 21293; bugfix on 0.1.1.14-alpha.
5355 o Minor bugfixes (testing):
5356 - Use unbuffered I/O for utility functions around the
5357 process_handle_t type. This fixes unit test failures reported on
5358 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
5359 - Make display of captured unit test log messages consistent. Fixes
5360 bug 21510; bugfix on 0.2.9.3-alpha.
5361 - Make test-network.sh always call chutney's test-network.sh.
5362 Previously, this only worked on systems which had bash installed,
5363 due to some bash-specific code in the script. Fixes bug 19699;
5364 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
5366 o Minor bugfixes (voting consistency):
5367 - Reject version numbers with non-numeric prefixes (such as +, -, or
5368 whitespace). Disallowing whitespace prevents differential version
5369 parsing between POSIX-based and Windows platforms. Fixes bug 21507
5370 and part of 21508; bugfix on 0.0.8pre1.
5372 o Minor bugfixes (windows, relay):
5373 - Resolve "Failure from drain_fd: No error" warnings on Windows
5374 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
5376 o Code simplification and refactoring:
5377 - Break up the 630-line function connection_dir_client_reached_eof()
5378 into a dozen smaller functions. This change should help
5379 maintainability and readability of the client directory code.
5380 - Isolate our use of the openssl headers so that they are only
5381 included from our crypto wrapper modules, and from tests that
5382 examine those modules' internals. Closes ticket 21841.
5383 - Simplify our API to launch directory requests, making it more
5384 extensible and less error-prone. Now it's easier to add extra
5385 headers to directory requests. Closes ticket 21646.
5386 - Our base64 decoding functions no longer overestimate the output
5387 space that they need when parsing unpadded inputs. Closes
5389 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
5390 Resolves ticket 22213.
5391 - The logic that directory caches use to spool request to clients,
5392 serving them one part at a time so as not to allocate too much
5393 memory, has been refactored for consistency. Previously there was
5394 a separate spooling implementation per type of spoolable data. Now
5395 there is one common spooling implementation, with extensible data
5396 types. Closes ticket 21651.
5397 - Tor's compression module now supports multiple backends. Part of
5398 the implementation for proposal 278; closes ticket 21663.
5401 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
5402 Closes ticket 21873.
5403 - Correct documentation about the default DataDirectory value.
5404 Closes ticket 21151.
5405 - Document the default behavior of NumEntryGuards and
5406 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
5408 - Document key=value pluggable transport arguments for Bridge lines
5409 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
5410 - Note that bandwidth-limiting options don't affect TCP headers or
5411 DNS. Closes ticket 17170.
5413 o Removed features (configuration options, all in ticket 22060):
5414 - These configuration options are now marked Obsolete, and no longer
5415 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
5416 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
5417 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
5418 in 0.2.9.2-alpha and have now been removed. The previous default
5419 behavior is now always chosen; the previous (less secure) non-
5420 default behavior is now unavailable.
5421 - CloseHSClientCircuitsImmediatelyOnTimeout and
5422 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
5423 0.2.9.2-alpha and now have been removed. HS circuits never close
5424 on circuit build timeout; they have a longer timeout period.
5425 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
5426 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
5427 (and others) to configure listen-only and advertise-only addresses.
5429 o Removed features (tools):
5430 - We've removed the tor-checkkey tool from src/tools. Long ago, we
5431 used it to help people detect RSA keys that were generated by
5432 versions of Debian affected by CVE-2008-0166. But those keys have
5433 been out of circulation for ages, and this tool is no longer
5434 required. Closes ticket 21842.
5437 Changes in version 0.3.0.7 - 2017-05-15
5438 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
5439 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
5440 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
5441 clients are not affected.
5443 o Major bugfixes (hidden service directory, security):
5444 - Fix an assertion failure in the hidden service directory code, which
5445 could be used by an attacker to remotely cause a Tor relay process to
5446 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
5447 should upgrade. This security issue is tracked as TROVE-2017-002.
5448 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
5451 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
5454 o Minor features (future-proofing):
5455 - Tor no longer refuses to download microdescriptors or descriptors
5456 if they are listed as "published in the future". This change will
5457 eventually allow us to stop listing meaningful "published" dates
5458 in microdescriptor consensuses, and thereby allow us to reduce the
5459 resources required to download consensus diffs by over 50%.
5460 Implements part of ticket 21642; implements part of proposal 275.
5462 o Minor bugfixes (Linux seccomp2 sandbox):
5463 - The getpid() system call is now permitted under the Linux seccomp2
5464 sandbox, to avoid crashing with versions of OpenSSL (and other
5465 libraries) that attempt to learn the process's PID by using the
5466 syscall rather than the VDSO code. Fixes bug 21943; bugfix
5470 Changes in version 0.3.0.6 - 2017-04-26
5471 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
5473 With the 0.3.0 series, clients and relays now use Ed25519 keys to
5474 authenticate their link connections to relays, rather than the old
5475 RSA1024 keys that they used before. (Circuit crypto has been
5476 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
5477 the guard selection and replacement algorithm to behave more robustly
5478 in the presence of unreliable networks, and to resist guard-
5481 This series also includes numerous other small features and bugfixes,
5482 along with more groundwork for the upcoming hidden-services revamp.
5484 Per our stable release policy, we plan to support the Tor 0.3.0
5485 release series for at least the next nine months, or for three months
5486 after the first stable release of the 0.3.1 series: whichever is
5487 longer. If you need a release with long-term support, we recommend
5488 that you stay with the 0.2.9 series.
5490 Below are the changes since 0.3.0.5-rc. For a list of all changes
5491 since 0.2.9, see the ReleaseNotes file.
5493 o Minor features (geoip):
5494 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
5497 o Minor bugfixes (control port):
5498 - The GETINFO extra-info/digest/<digest> command was broken because
5499 of a wrong base16 decode return value check, introduced when
5500 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
5502 o Minor bugfixes (crash prevention):
5503 - Fix a (currently untriggerable, but potentially dangerous) crash
5504 bug when base32-encoding inputs whose sizes are not a multiple of
5505 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
5508 Changes in version 0.3.0.5-rc - 2017-04-05
5509 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
5510 0.3.0 release series.
5512 This is the second release candidate in the Tor 0.3.0 series, and has
5513 much fewer changes than the first. If we find no new bugs or
5514 regressions here, the first stable 0.3.0 release will be nearly
5517 o Major bugfixes (crash, directory connections):
5518 - Fix a rare crash when sending a begin cell on a circuit whose
5519 linked directory connection had already been closed. Fixes bug
5520 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
5522 o Major bugfixes (guard selection):
5523 - Fix a guard selection bug where Tor would refuse to bootstrap in
5524 some cases if the user swapped a bridge for another bridge in
5525 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
5526 Reported by "torvlnt33r".
5528 o Minor features (geoip):
5529 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
5532 o Minor bugfix (compilation):
5533 - Fix a warning when compiling hs_service.c. Previously, it had no
5534 exported symbols when compiled for libor.a, resulting in a
5535 compilation warning from clang. Fixes bug 21825; bugfix
5538 o Minor bugfixes (hidden services):
5539 - Make hidden services check for failed intro point connections,
5540 even when they have exceeded their intro point creation limit.
5541 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
5542 - Make hidden services with 8 to 10 introduction points check for
5543 failed circuits immediately after startup. Previously, they would
5544 wait for 5 minutes before performing their first checks. Fixes bug
5545 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
5547 o Minor bugfixes (memory leaks):
5548 - Fix a memory leak when using GETCONF on a port option. Fixes bug
5549 21682; bugfix on 0.3.0.3-alpha.
5551 o Minor bugfixes (relay):
5552 - Avoid a double-marked-circuit warning that could happen when we
5553 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
5556 o Minor bugfixes (tests):
5557 - Run the entry_guard_parse_from_state_full() test with the time set
5558 to a specific date. (The guard state that this test was parsing
5559 contained guards that had expired since the test was first
5560 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
5563 - Update the description of the directory server options in the
5564 manual page, to clarify that a relay no longer needs to set
5565 DirPort in order to be a directory cache. Closes ticket 21720.
5569 Changes in version 0.2.8.13 - 2017-03-03
5570 Tor 0.2.8.13 backports a security fix from later Tor
5571 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
5572 this release, if for some reason they cannot upgrade to a later
5573 release series, and if they build Tor with the --enable-expensive-hardening
5576 Note that support for Tor 0.2.8.x is ending next year: we will not issue
5577 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
5578 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5580 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5581 - Fix an integer underflow bug when comparing malformed Tor
5582 versions. This bug could crash Tor when built with
5583 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5584 0.2.9.8, which were built with -ftrapv by default. In other cases
5585 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5586 on 0.0.8pre1. Found by OSS-Fuzz.
5588 o Minor features (geoip):
5589 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5593 Changes in version 0.2.7.7 - 2017-03-03
5594 Tor 0.2.7.7 backports a number of security fixes from later Tor
5595 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
5596 this release, if for some reason they cannot upgrade to a later
5599 Note that support for Tor 0.2.7.x is ending this year: we will not issue
5600 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
5601 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5603 o Directory authority changes (backport from 0.2.8.5-rc):
5604 - Urras is no longer a directory authority. Closes ticket 19271.
5606 o Directory authority changes (backport from 0.2.9.2-alpha):
5607 - The "Tonga" bridge authority has been retired; the new bridge
5608 authority is "Bifroest". Closes tickets 19728 and 19690.
5610 o Directory authority key updates (backport from 0.2.8.1-alpha):
5611 - Update the V3 identity key for the dannenberg directory authority:
5612 it was changed on 18 November 2015. Closes task 17906. Patch
5615 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5616 - Fix a bug in parsing that could cause clients to read a single
5617 byte past the end of an allocated region. This bug could be used
5618 to cause hardened clients (built with --enable-expensive-hardening)
5619 to crash if they tried to visit a hostile hidden service. Non-
5620 hardened clients are only affected depending on the details of
5621 their platform's memory allocator. Fixes bug 21018; bugfix on
5622 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5623 2016-12-002 and as CVE-2016-1254.
5625 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5626 - Stop a crash that could occur when a client running with DNSPort
5627 received a query with multiple address types, and the first
5628 address type was not supported. Found and fixed by Scott Dial.
5629 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5630 - Prevent a class of security bugs caused by treating the contents
5631 of a buffer chunk as if they were a NUL-terminated string. At
5632 least one such bug seems to be present in all currently used
5633 versions of Tor, and would allow an attacker to remotely crash
5634 most Tor instances, especially those compiled with extra compiler
5635 hardening. With this defense in place, such bugs can't crash Tor,
5636 though we should still fix them as they occur. Closes ticket
5637 20384 (TROVE-2016-10-001).
5639 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5640 - Avoid a difficult-to-trigger heap corruption attack when extending
5641 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5642 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5643 Reported by Guido Vranken.
5645 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5646 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5647 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5649 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5650 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5651 pointer to the previous (uninitialized) key value. The impact here
5652 should be limited to a difficult-to-trigger crash, if OpenSSL is
5653 running an engine that makes key generation failures possible, or
5654 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5655 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5658 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5659 - Fix an integer underflow bug when comparing malformed Tor
5660 versions. This bug could crash Tor when built with
5661 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5662 0.2.9.8, which were built with -ftrapv by default. In other cases
5663 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5664 on 0.0.8pre1. Found by OSS-Fuzz.
5666 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5667 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5668 zero size. Check size argument to memwipe() for underflow. Fixes
5669 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5672 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5673 - Make Tor survive errors involving connections without a
5674 corresponding event object. Previously we'd fail with an
5675 assertion; now we produce a log message. Related to bug 16248.
5677 o Minor features (geoip):
5678 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5682 Changes in version 0.2.6.11 - 2017-03-03
5683 Tor 0.2.6.11 backports a number of security fixes from later Tor
5684 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
5685 this release, if for some reason they cannot upgrade to a later
5688 Note that support for Tor 0.2.6.x is ending this year: we will not issue
5689 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
5690 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5692 o Directory authority changes (backport from 0.2.8.5-rc):
5693 - Urras is no longer a directory authority. Closes ticket 19271.
5695 o Directory authority changes (backport from 0.2.9.2-alpha):
5696 - The "Tonga" bridge authority has been retired; the new bridge
5697 authority is "Bifroest". Closes tickets 19728 and 19690.
5699 o Directory authority key updates (backport from 0.2.8.1-alpha):
5700 - Update the V3 identity key for the dannenberg directory authority:
5701 it was changed on 18 November 2015. Closes task 17906. Patch
5704 o Major features (security fixes, backport from 0.2.9.4-alpha):
5705 - Prevent a class of security bugs caused by treating the contents
5706 of a buffer chunk as if they were a NUL-terminated string. At
5707 least one such bug seems to be present in all currently used
5708 versions of Tor, and would allow an attacker to remotely crash
5709 most Tor instances, especially those compiled with extra compiler
5710 hardening. With this defense in place, such bugs can't crash Tor,
5711 though we should still fix them as they occur. Closes ticket
5712 20384 (TROVE-2016-10-001).
5714 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5715 - Fix a bug in parsing that could cause clients to read a single
5716 byte past the end of an allocated region. This bug could be used
5717 to cause hardened clients (built with --enable-expensive-hardening)
5718 to crash if they tried to visit a hostile hidden service. Non-
5719 hardened clients are only affected depending on the details of
5720 their platform's memory allocator. Fixes bug 21018; bugfix on
5721 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5722 2016-12-002 and as CVE-2016-1254.
5724 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5725 - Stop a crash that could occur when a client running with DNSPort
5726 received a query with multiple address types, and the first
5727 address type was not supported. Found and fixed by Scott Dial.
5728 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5730 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5731 - Fix an error that could cause us to read 4 bytes before the
5732 beginning of an openssl string. This bug could be used to cause
5733 Tor to crash on systems with unusual malloc implementations, or
5734 systems with unusual hardening installed. Fixes bug 17404; bugfix
5737 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5738 - Avoid a difficult-to-trigger heap corruption attack when extending
5739 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5740 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5741 Reported by Guido Vranken.
5743 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5744 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5745 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5747 o Major bugfixes (guard selection, backport from 0.2.7.6):
5748 - Actually look at the Guard flag when selecting a new directory
5749 guard. When we implemented the directory guard design, we
5750 accidentally started treating all relays as if they have the Guard
5751 flag during guard selection, leading to weaker anonymity and worse
5752 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5755 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5756 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5757 pointer to the previous (uninitialized) key value. The impact here
5758 should be limited to a difficult-to-trigger crash, if OpenSSL is
5759 running an engine that makes key generation failures possible, or
5760 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5761 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5764 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5765 - Fix an integer underflow bug when comparing malformed Tor
5766 versions. This bug could crash Tor when built with
5767 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5768 0.2.9.8, which were built with -ftrapv by default. In other cases
5769 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5770 on 0.0.8pre1. Found by OSS-Fuzz.
5772 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5773 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5774 zero size. Check size argument to memwipe() for underflow. Fixes
5775 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5778 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5779 - Make Tor survive errors involving connections without a
5780 corresponding event object. Previously we'd fail with an
5781 assertion; now we produce a log message. Related to bug 16248.
5783 o Minor features (geoip):
5784 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5787 o Minor bugfixes (compilation, backport from 0.2.7.6):
5788 - Fix a compilation warning with Clang 3.6: Do not check the
5789 presence of an address which can never be NULL. Fixes bug 17781.
5792 Changes in version 0.2.5.13 - 2017-03-03
5793 Tor 0.2.5.13 backports a number of security fixes from later Tor
5794 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
5795 this release, if for some reason they cannot upgrade to a later
5798 Note that support for Tor 0.2.5.x is ending next year: we will not issue
5799 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
5800 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
5802 o Directory authority changes (backport from 0.2.8.5-rc):
5803 - Urras is no longer a directory authority. Closes ticket 19271.
5805 o Directory authority changes (backport from 0.2.9.2-alpha):
5806 - The "Tonga" bridge authority has been retired; the new bridge
5807 authority is "Bifroest". Closes tickets 19728 and 19690.
5809 o Directory authority key updates (backport from 0.2.8.1-alpha):
5810 - Update the V3 identity key for the dannenberg directory authority:
5811 it was changed on 18 November 2015. Closes task 17906. Patch
5814 o Major features (security fixes, backport from 0.2.9.4-alpha):
5815 - Prevent a class of security bugs caused by treating the contents
5816 of a buffer chunk as if they were a NUL-terminated string. At
5817 least one such bug seems to be present in all currently used
5818 versions of Tor, and would allow an attacker to remotely crash
5819 most Tor instances, especially those compiled with extra compiler
5820 hardening. With this defense in place, such bugs can't crash Tor,
5821 though we should still fix them as they occur. Closes ticket
5822 20384 (TROVE-2016-10-001).
5824 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5825 - Fix a bug in parsing that could cause clients to read a single
5826 byte past the end of an allocated region. This bug could be used
5827 to cause hardened clients (built with --enable-expensive-hardening)
5828 to crash if they tried to visit a hostile hidden service. Non-
5829 hardened clients are only affected depending on the details of
5830 their platform's memory allocator. Fixes bug 21018; bugfix on
5831 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5832 2016-12-002 and as CVE-2016-1254.
5834 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
5835 - Stop a crash that could occur when a client running with DNSPort
5836 received a query with multiple address types, and the first
5837 address type was not supported. Found and fixed by Scott Dial.
5838 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
5840 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5841 - Fix an error that could cause us to read 4 bytes before the
5842 beginning of an openssl string. This bug could be used to cause
5843 Tor to crash on systems with unusual malloc implementations, or
5844 systems with unusual hardening installed. Fixes bug 17404; bugfix
5847 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5848 - Avoid a difficult-to-trigger heap corruption attack when extending
5849 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5850 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5851 Reported by Guido Vranken.
5853 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5854 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5855 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5857 o Major bugfixes (guard selection, backport from 0.2.7.6):
5858 - Actually look at the Guard flag when selecting a new directory
5859 guard. When we implemented the directory guard design, we
5860 accidentally started treating all relays as if they have the Guard
5861 flag during guard selection, leading to weaker anonymity and worse
5862 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5865 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5866 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5867 pointer to the previous (uninitialized) key value. The impact here
5868 should be limited to a difficult-to-trigger crash, if OpenSSL is
5869 running an engine that makes key generation failures possible, or
5870 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5871 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5874 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5875 - Fix an integer underflow bug when comparing malformed Tor
5876 versions. This bug could crash Tor when built with
5877 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5878 0.2.9.8, which were built with -ftrapv by default. In other cases
5879 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5880 on 0.0.8pre1. Found by OSS-Fuzz.
5882 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5883 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5884 zero size. Check size argument to memwipe() for underflow. Fixes
5885 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5888 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
5889 - Make Tor survive errors involving connections without a
5890 corresponding event object. Previously we'd fail with an
5891 assertion; now we produce a log message. Related to bug 16248.
5893 o Minor features (geoip):
5894 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
5897 o Minor bugfixes (compilation, backport from 0.2.7.6):
5898 - Fix a compilation warning with Clang 3.6: Do not check the
5899 presence of an address which can never be NULL. Fixes bug 17781.
5901 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
5902 - Check for failures from crypto_early_init, and refuse to continue.
5903 A previous typo meant that we could keep going with an
5904 uninitialized crypto library, and would have OpenSSL initialize
5905 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
5906 when implementing ticket 4900. Patch by "teor".
5908 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5909 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5910 a client authorized hidden service. Fixes bug 15823; bugfix
5914 Changes in version 0.2.4.28 - 2017-03-03
5915 Tor 0.2.4.28 backports a number of security fixes from later Tor
5916 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
5917 this release, if for some reason they cannot upgrade to a later
5920 Note that support for Tor 0.2.4.x is ending soon: we will not issue
5921 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
5922 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
5924 o Directory authority changes (backport from 0.2.8.5-rc):
5925 - Urras is no longer a directory authority. Closes ticket 19271.
5927 o Directory authority changes (backport from 0.2.9.2-alpha):
5928 - The "Tonga" bridge authority has been retired; the new bridge
5929 authority is "Bifroest". Closes tickets 19728 and 19690.
5931 o Directory authority key updates (backport from 0.2.8.1-alpha):
5932 - Update the V3 identity key for the dannenberg directory authority:
5933 it was changed on 18 November 2015. Closes task 17906. Patch
5936 o Major features (security fixes, backport from 0.2.9.4-alpha):
5937 - Prevent a class of security bugs caused by treating the contents
5938 of a buffer chunk as if they were a NUL-terminated string. At
5939 least one such bug seems to be present in all currently used
5940 versions of Tor, and would allow an attacker to remotely crash
5941 most Tor instances, especially those compiled with extra compiler
5942 hardening. With this defense in place, such bugs can't crash Tor,
5943 though we should still fix them as they occur. Closes ticket
5944 20384 (TROVE-2016-10-001).
5946 o Major bugfixes (parsing, security, backport from 0.2.9.8):
5947 - Fix a bug in parsing that could cause clients to read a single
5948 byte past the end of an allocated region. This bug could be used
5949 to cause hardened clients (built with --enable-expensive-hardening)
5950 to crash if they tried to visit a hostile hidden service. Non-
5951 hardened clients are only affected depending on the details of
5952 their platform's memory allocator. Fixes bug 21018; bugfix on
5953 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
5954 2016-12-002 and as CVE-2016-1254.
5956 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
5957 - Fix an error that could cause us to read 4 bytes before the
5958 beginning of an openssl string. This bug could be used to cause
5959 Tor to crash on systems with unusual malloc implementations, or
5960 systems with unusual hardening installed. Fixes bug 17404; bugfix
5963 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
5964 - Avoid a difficult-to-trigger heap corruption attack when extending
5965 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
5966 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
5967 Reported by Guido Vranken.
5969 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
5970 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
5971 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
5973 o Major bugfixes (guard selection, backport from 0.2.7.6):
5974 - Actually look at the Guard flag when selecting a new directory
5975 guard. When we implemented the directory guard design, we
5976 accidentally started treating all relays as if they have the Guard
5977 flag during guard selection, leading to weaker anonymity and worse
5978 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5981 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
5982 - If OpenSSL fails to generate an RSA key, do not retain a dangling
5983 pointer to the previous (uninitialized) key value. The impact here
5984 should be limited to a difficult-to-trigger crash, if OpenSSL is
5985 running an engine that makes key generation failures possible, or
5986 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
5987 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
5990 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
5991 - Fix an integer underflow bug when comparing malformed Tor
5992 versions. This bug could crash Tor when built with
5993 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
5994 0.2.9.8, which were built with -ftrapv by default. In other cases
5995 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
5996 on 0.0.8pre1. Found by OSS-Fuzz.
5998 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
5999 - Make memwipe() do nothing when passed a NULL pointer or buffer of
6000 zero size. Check size argument to memwipe() for underflow. Fixes
6001 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
6004 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
6005 - Make Tor survive errors involving connections without a
6006 corresponding event object. Previously we'd fail with an
6007 assertion; now we produce a log message. Related to bug 16248.
6009 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
6010 - Make it harder for attackers to overload hidden services with
6011 introductions, by blocking multiple introduction requests on the
6012 same circuit. Resolves ticket 15515.
6014 o Minor features (geoip):
6015 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
6018 o Minor bugfixes (compilation, backport from 0.2.7.6):
6019 - Fix a compilation warning with Clang 3.6: Do not check the
6020 presence of an address which can never be NULL. Fixes bug 17781.
6022 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
6023 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
6024 a client authorized hidden service. Fixes bug 15823; bugfix
6028 Changes in version 0.3.0.4-rc - 2017-03-01
6029 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
6030 0.3.0 release series, and introduces a few reliability features to
6031 keep them from coming back.
6033 This is the first release candidate in the Tor 0.3.0 series. If we
6034 find no new bugs or regressions here, the first stable 0.3.0 release
6035 will be nearly identical to it.
6037 o Major bugfixes (bridges):
6038 - When the same bridge is configured multiple times with the same
6039 identity, but at different address:port combinations, treat those
6040 bridge instances as separate guards. This fix restores the ability
6041 of clients to configure the same bridge with multiple pluggable
6042 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
6044 o Major bugfixes (hidden service directory v3):
6045 - Stop crashing on a failed v3 hidden service descriptor lookup
6046 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
6048 o Major bugfixes (parsing):
6049 - When parsing a malformed content-length field from an HTTP
6050 message, do not read off the end of the buffer. This bug was a
6051 potential remote denial-of-service attack against Tor clients and
6052 relays. A workaround was released in October 2016, to prevent this
6053 bug from crashing Tor. This is a fix for the underlying issue,
6054 which should no longer matter (if you applied the earlier patch).
6055 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
6056 using AFL (http://lcamtuf.coredump.cx/afl/).
6057 - Fix an integer underflow bug when comparing malformed Tor
6058 versions. This bug could crash Tor when built with
6059 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
6060 0.2.9.8, which were built with -ftrapv by default. In other cases
6061 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
6062 on 0.0.8pre1. Found by OSS-Fuzz.
6064 o Minor feature (protocol versioning):
6065 - Add new protocol version for proposal 224. HSIntro now advertises
6066 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
6068 o Minor features (directory authorities):
6069 - Directory authorities now reject descriptors that claim to be
6070 malformed versions of Tor. Helps prevent exploitation of
6072 - Reject version numbers with components that exceed INT32_MAX.
6073 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
6074 Fixes bug 21450; bugfix on 0.0.8pre1.
6075 - Directory authorities now reject relays running versions
6076 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
6077 suffer from bug 20499 and don't keep their consensus cache
6078 up-to-date. Resolves ticket 20509.
6080 o Minor features (geoip):
6081 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
6084 o Minor features (reliability, crash):
6085 - Try better to detect problems in buffers where they might grow (or
6086 think they have grown) over 2 GB in size. Diagnostic for
6089 o Minor features (testing):
6090 - During 'make test-network-all', if tor logs any warnings, ask
6091 chutney to output them. Requires a recent version of chutney with
6092 the 21572 patch. Implements 21570.
6094 o Minor bugfixes (certificate expiration time):
6095 - Avoid using link certificates that don't become valid till some
6096 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
6098 o Minor bugfixes (code correctness):
6099 - Repair a couple of (unreachable or harmless) cases of the risky
6100 comparison-by-subtraction pattern that caused bug 21278.
6101 - Remove a redundant check for the UseEntryGuards option from the
6102 options_transition_affects_guards() function. Fixes bug 21492;
6103 bugfix on 0.3.0.1-alpha.
6105 o Minor bugfixes (directory mirrors):
6106 - Allow relays to use directory mirrors without a DirPort: these
6107 relays need to be contacted over their ORPorts using a begindir
6108 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
6109 - Clarify the message logged when a remote relay is unexpectedly
6110 missing an ORPort or DirPort: users were confusing this with a
6111 local port. Fixes another case of bug 20711; bugfix
6114 o Minor bugfixes (guards):
6115 - Don't warn about a missing guard state on timeout-measurement
6116 circuits: they aren't supposed to be using guards. Fixes an
6117 instance of bug 21007; bugfix on 0.3.0.1-alpha.
6118 - Silence a BUG() warning when attempting to use a guard whose
6119 descriptor we don't know, and make this scenario less likely to
6120 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
6122 o Minor bugfixes (hidden service):
6123 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
6124 cells. Previously, we were using sizeof() on a pointer, instead of
6125 the real destination buffer. Fortunately, that value was only used
6126 to double-check that there was enough room--which was already
6127 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
6129 o Minor bugfixes (testing):
6130 - Fix Raspbian build issues related to missing socket errno in
6131 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
6133 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
6134 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
6135 - Use bash in src/test/test-network.sh. This ensures we reliably
6136 call chutney's newer tools/test-network.sh when available. Fixes
6137 bug 21562; bugfix on 0.2.9.1-alpha.
6140 - Small fixes to the fuzzing documentation. Closes ticket 21472.
6143 Changes in version 0.2.9.10 - 2017-03-01
6144 Tor 0.2.9.10 backports a security fix from later Tor release. It also
6145 includes fixes for some major issues affecting directory authorities,
6146 LibreSSL compatibility, and IPv6 correctness.
6148 The Tor 0.2.9.x release series is now marked as a long-term-support
6149 series. We intend to backport security fixes to 0.2.9.x until at
6150 least January of 2020.
6152 o Major bugfixes (directory authority, 0.3.0.3-alpha):
6153 - During voting, when marking a relay as a probable sybil, do not
6154 clear its BadExit flag: sybils can still be bad in other ways
6155 too. (We still clear the other flags.) Fixes bug 21108; bugfix
6158 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
6159 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
6160 any IPv6 addresses. Instead, only reject a port over IPv6 if the
6161 exit policy rejects that port on more than an IPv6 /16 of
6162 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
6163 which rejected a relay's own IPv6 address by default. Fixes bug
6164 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
6166 o Major bugfixes (parsing, also in 0.3.0.4-rc):
6167 - Fix an integer underflow bug when comparing malformed Tor
6168 versions. This bug could crash Tor when built with
6169 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
6170 0.2.9.8, which were built with -ftrapv by default. In other cases
6171 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
6172 on 0.0.8pre1. Found by OSS-Fuzz.
6174 o Minor features (directory authorities, also in 0.3.0.4-rc):
6175 - Directory authorities now reject descriptors that claim to be
6176 malformed versions of Tor. Helps prevent exploitation of
6178 - Reject version numbers with components that exceed INT32_MAX.
6179 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
6180 Fixes bug 21450; bugfix on 0.0.8pre1.
6182 o Minor features (geoip):
6183 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
6186 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
6187 - Autoconf now checks to determine if OpenSSL structures are opaque,
6188 instead of explicitly checking for OpenSSL version numbers. Part
6190 - Support building with recent LibreSSL code that uses opaque
6191 structures. Closes ticket 21359.
6193 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
6194 - Repair a couple of (unreachable or harmless) cases of the risky
6195 comparison-by-subtraction pattern that caused bug 21278.
6197 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
6198 - The tor-resolve command line tool now rejects hostnames over 255
6199 characters in length. Previously, it would silently truncate them,
6200 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
6201 Patch by "junglefowl".
6204 Changes in version 0.3.0.3-alpha - 2017-02-03
6205 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
6206 0.3.0.x development series, including some that could cause
6207 authorities to behave badly. There is also a fix for a longstanding
6208 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
6209 includes some smaller features and bugfixes.
6211 The Tor 0.3.0.x release series is now in patch-freeze: no additional
6212 features will be considered for inclusion in 0.3.0.x. We suspect that
6213 some bugs will probably remain, however, and we encourage people to
6216 o Major bugfixes (directory authority):
6217 - During voting, when marking a relay as a probable sybil, do not
6218 clear its BadExit flag: sybils can still be bad in other ways
6219 too. (We still clear the other flags.) Fixes bug 21108; bugfix
6221 - When deciding whether we have just found a router to be reachable,
6222 do not penalize it for not having performed an Ed25519 link
6223 handshake if it does not claim to support an Ed25519 handshake.
6224 Previously, we would treat such relays as non-running. Fixes bug
6225 21107; bugfix on 0.3.0.1-alpha.
6227 o Major bugfixes (entry guards):
6228 - Stop trying to build circuits through entry guards for which we
6229 have no descriptor. Also, stop crashing in the case that we *do*
6230 accidentally try to build a circuit in such a state. Fixes bug
6231 21242; bugfix on 0.3.0.1-alpha.
6233 o Major bugfixes (IPv6 Exits):
6234 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
6235 any IPv6 addresses. Instead, only reject a port over IPv6 if the
6236 exit policy rejects that port on more than an IPv6 /16 of
6237 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
6238 which rejected a relay's own IPv6 address by default. Fixes bug
6239 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
6241 o Minor feature (client):
6242 - Enable IPv6 traffic on the SocksPort by default. To disable this,
6243 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
6245 o Minor feature (fallback scripts):
6246 - Add a check_existing mode to updateFallbackDirs.py, which checks
6247 if fallbacks in the hard-coded list are working. Closes ticket
6248 20174. Patch by haxxpop.
6250 o Minor features (ciphersuite selection):
6251 - Clients now advertise a list of ciphersuites closer to the ones
6252 preferred by Firefox. Closes part of ticket 15426.
6253 - Allow relays to accept a wider range of ciphersuites, including
6254 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
6256 o Minor features (controller, configuration):
6257 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
6258 and so on, now comes with a __*Port variant that will not be saved
6259 to the torrc file by the controller's SAVECONF command. This
6260 change allows TorBrowser to set up a single-use domain socket for
6261 each time it launches Tor. Closes ticket 20956.
6262 - The GETCONF command can now query options that may only be
6263 meaningful in context-sensitive lists. This allows the controller
6264 to query the mixed SocksPort/__SocksPort style options introduced
6265 in feature 20956. Implements ticket 21300.
6267 o Minor features (portability, compilation):
6268 - Autoconf now checks to determine if OpenSSL structures are opaque,
6269 instead of explicitly checking for OpenSSL version numbers. Part
6271 - Support building with recent LibreSSL code that uses opaque
6272 structures. Closes ticket 21359.
6274 o Minor features (relay):
6275 - We now allow separation of exit and relay traffic to different
6276 source IP addresses, using the OutboundBindAddressExit and
6277 OutboundBindAddressOR options respectively. Closes ticket 17975.
6278 Written by Michael Sonntag.
6280 o Minor bugfix (logging):
6281 - Don't recommend the use of Tor2web in non-anonymous mode.
6282 Recommending Tor2web is a bad idea because the client loses all
6283 anonymity. Tor2web should only be used in specific cases by users
6284 who *know* and understand the issues. Fixes bug 21294; bugfix
6287 o Minor bugfixes (client):
6288 - Always recover from failures in extend_info_from_node(), in an
6289 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
6290 bugfix on 0.2.3.1-alpha.
6292 o Minor bugfixes (client, entry guards):
6293 - Fix a bug warning (with backtrace) when we fail a channel that
6294 circuits to fallback directories on it. Fixes bug 21128; bugfix
6296 - Fix a spurious bug warning (with backtrace) when removing an
6297 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
6298 - Fix a bug of the new guard algorithm where tor could stall for up
6299 to 10 minutes before retrying a guard after a long period of no
6300 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
6301 - Do not try to build circuits until we have descriptors for our
6302 primary entry guards. Related to fix for bug 21242.
6304 o Minor bugfixes (configure, autoconf):
6305 - Rename the configure option --enable-expensive-hardening to
6306 --enable-fragile-hardening. Expensive hardening makes the tor
6307 daemon abort when some kinds of issues are detected. Thus, it
6308 makes tor more at risk of remote crashes but safer against RCE or
6309 heartbleed bug category. We now try to explain this issue in a
6310 message from the configure script. Fixes bug 21290; bugfix
6313 o Minor bugfixes (controller):
6314 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
6315 20824; bugfix on 0.3.0.1-alpha.
6317 o Minor bugfixes (hidden service):
6318 - Clean up the code for expiring intro points with no associated
6319 circuits. It was causing, rarely, a service with some expiring
6320 introduction points to not open enough additional introduction
6321 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
6322 - Stop setting the torrc option HiddenServiceStatistics to "0" just
6323 because we're not a bridge or relay. Instead, we preserve whatever
6324 value the user set (or didn't set). Fixes bug 21150; bugfix
6326 - Resolve two possible underflows which could lead to creating and
6327 closing a lot of introduction point circuits in a non-stop loop.
6328 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
6330 o Minor bugfixes (portability):
6331 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
6332 It is supported by OpenBSD itself, and also by most OpenBSD
6333 variants (such as Bitrig). Fixes bug 20980; bugfix
6335 - When mapping a file of length greater than SIZE_MAX, do not
6336 silently truncate its contents. This issue could occur on 32 bit
6337 systems with large file support and files which are larger than 4
6338 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
6340 o Minor bugfixes (tor-resolve):
6341 - The tor-resolve command line tool now rejects hostnames over 255
6342 characters in length. Previously, it would silently truncate them,
6343 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
6344 Patch by "junglefowl".
6346 o Minor bugfixes (Windows services):
6347 - Be sure to initialize the monotonic time subsystem before using
6348 it, even when running as an NT service. Fixes bug 21356; bugfix
6352 Changes in version 0.3.0.2-alpha - 2017-01-23
6353 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
6354 cause relays and clients to crash, even if they were not built with
6355 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
6356 versions, and also affects 0.3.0.1-alpha: all relays running an affected
6357 version should upgrade.
6359 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
6360 time-to-live values, makes directory authorities enforce the 1-to-1
6361 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
6362 client-side onion service reachability bug, does better at selecting
6363 the set of fallback directories, and more.
6365 o Major bugfixes (security, also in 0.2.9.9):
6366 - Downgrade the "-ftrapv" option from "always on" to "only on when
6367 --enable-expensive-hardening is provided." This hardening option, like
6368 others, can turn survivable bugs into crashes--and having it on by
6369 default made a (relatively harmless) integer overflow bug into a
6370 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
6373 o Major features (security):
6374 - Change the algorithm used to decide DNS TTLs on client and server
6375 side, to better resist DNS-based correlation attacks like the
6376 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
6377 Feamster. Now relays only return one of two possible DNS TTL
6378 values, and clients are willing to believe DNS TTL values up to 3
6379 hours long. Closes ticket 19769.
6381 o Major features (directory authority, security):
6382 - The default for AuthDirPinKeys is now 1: directory authorities
6383 will reject relays where the RSA identity key matches a previously
6384 seen value, but the Ed25519 key has changed. Closes ticket 18319.
6386 o Major bugfixes (client, guard, crash):
6387 - In circuit_get_global_origin_list(), return the actual list of
6388 origin circuits. The previous version of this code returned the
6389 list of all the circuits, and could have caused strange bugs,
6390 including possible crashes. Fixes bug 21118; bugfix
6393 o Major bugfixes (client, onion service, also in 0.2.9.9):
6394 - Fix a client-side onion service reachability bug, where multiple
6395 socks requests to an onion service (or a single slow request)
6396 could cause us to mistakenly mark some of the service's
6397 introduction points as failed, and we cache that failure so
6398 eventually we run out and can't reach the service. Also resolves a
6399 mysterious "Remote server sent bogus reason code 65021" log
6400 warning. The bug was introduced in ticket 17218, where we tried to
6401 remember the circuit end reason as a uint16_t, which mangled
6402 negative values. Partially fixes bug 21056 and fixes bug 20307;
6403 bugfix on 0.2.8.1-alpha.
6405 o Major bugfixes (DNS):
6406 - Fix a bug that prevented exit nodes from caching DNS records for
6407 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
6409 o Minor features (controller):
6410 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
6411 shared-random values to the controller. Closes ticket 19925.
6413 o Minor features (entry guards):
6414 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
6415 break regression tests.
6416 - Require UseEntryGuards when UseBridges is set, in order to make
6417 sure bridges aren't bypassed. Resolves ticket 20502.
6419 o Minor features (fallback directories):
6420 - Select 200 fallback directories for each release. Closes
6422 - Allow 3 fallback relays per operator, which is safe now that we
6423 are choosing 200 fallback relays. Closes ticket 20912.
6424 - Exclude relays affected by bug 20499 from the fallback list.
6425 Exclude relays from the fallback list if they are running versions
6426 known to be affected by bug 20499, or if in our tests they deliver
6427 a stale consensus (i.e. one that expired more than 24 hours ago).
6428 Closes ticket 20539.
6429 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
6431 - Require fallback directories to have the same address and port for
6432 7 days (now that we have enough relays with this stability).
6433 Relays whose OnionOO stability timer is reset on restart by bug
6434 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
6435 this issue. Closes ticket 20880; maintains short-term fix
6437 - Require fallbacks to have flags for 90% of the time (weighted
6438 decaying average), rather than 95%. This allows at least 73% of
6439 clients to bootstrap in the first 5 seconds without contacting an
6440 authority. Part of ticket 18828.
6441 - Annotate updateFallbackDirs.py with the bandwidth and consensus
6442 weight for each candidate fallback. Closes ticket 20878.
6443 - Make it easier to change the output sort order of fallbacks.
6444 Closes ticket 20822.
6445 - Display the relay fingerprint when downloading consensuses from
6446 fallbacks. Closes ticket 20908.
6448 o Minor features (geoip, also in 0.2.9.9):
6449 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
6452 o Minor features (next-gen onion service directories):
6453 - Remove the "EnableOnionServicesV3" consensus parameter that we
6454 introduced in 0.3.0.1-alpha: relays are now always willing to act
6455 as v3 onion service directories. Resolves ticket 19899.
6457 o Minor features (linting):
6458 - Enhance the changes file linter to warn on Tor versions that are
6459 prefixed with "tor-". Closes ticket 21096.
6461 o Minor features (logging):
6462 - In several places, describe unset ed25519 keys as "<unset>",
6463 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
6465 o Minor bugfix (control protocol):
6466 - The reply to a "GETINFO config/names" request via the control
6467 protocol now spells the type "Dependent" correctly. This is a
6468 breaking change in the control protocol. (The field seems to be
6469 ignored by the most common known controllers.) Fixes bug 18146;
6470 bugfix on 0.1.1.4-alpha.
6472 o Minor bugfixes (bug resilience):
6473 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
6474 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
6475 Hans Jerry Illikainen.
6477 o Minor bugfixes (build):
6478 - Replace obsolete Autoconf macros with their modern equivalent and
6479 prevent similar issues in the future. Fixes bug 20990; bugfix
6482 o Minor bugfixes (client, guards):
6483 - Fix bug where Tor would think that there are circuits waiting for
6484 better guards even though those circuits have been freed. Fixes
6485 bug 21142; bugfix on 0.3.0.1-alpha.
6487 o Minor bugfixes (config):
6488 - Don't assert on startup when trying to get the options list and
6489 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
6490 options so of course they aren't ready yet. Fixes bug 21062;
6491 bugfix on 0.2.9.3-alpha.
6493 o Minor bugfixes (controller):
6494 - Make the GETINFO interface for inquiring about entry guards
6495 support the new guards backend. Fixes bug 20823; bugfix
6498 o Minor bugfixes (dead code):
6499 - Remove a redundant check for PidFile changes at runtime in
6500 options_transition_allowed(): this check is already performed
6501 regardless of whether the sandbox is active. Fixes bug 21123;
6502 bugfix on 0.2.5.4-alpha.
6504 o Minor bugfixes (documentation):
6505 - Update the tor manual page to document every option that can not
6506 be changed while tor is running. Fixes bug 21122.
6508 o Minor bugfixes (fallback directories):
6509 - Stop failing when a relay has no uptime data in
6510 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
6511 - Avoid checking fallback candidates' DirPorts if they are down in
6512 OnionOO. When a relay operator has multiple relays, this
6513 prioritizes relays that are up over relays that are down. Fixes
6514 bug 20926; bugfix on 0.2.8.3-alpha.
6515 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
6516 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
6518 o Minor bugfixes (guards, bootstrapping):
6519 - When connecting to a directory guard during bootstrap, do not mark
6520 the guard as successful until we receive a good-looking directory
6521 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
6523 o Minor bugfixes (onion services):
6524 - Fix the config reload pruning of old vs new services so it
6525 actually works when both ephemeral and non-ephemeral services are
6526 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
6527 - Allow the number of introduction points to be as low as 0, rather
6528 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
6530 o Minor bugfixes (IPv6):
6531 - Make IPv6-using clients try harder to find an IPv6 directory
6532 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
6533 - When IPv6 addresses have not been downloaded yet (microdesc
6534 consensus documents don't list relay IPv6 addresses), use hard-
6535 coded addresses for authorities, fallbacks, and configured
6536 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
6537 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
6539 o Minor bugfixes (memory leaks):
6540 - Fix a memory leak when configuring hidden services. Fixes bug
6541 20987; bugfix on 0.3.0.1-alpha.
6543 o Minor bugfixes (portability, also in 0.2.9.9):
6544 - Avoid crashing when Tor is built using headers that contain
6545 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
6546 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
6548 - Fix Libevent detection on platforms without Libevent 1 headers
6549 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
6551 o Minor bugfixes (relay):
6552 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
6553 initializing the keys would reset the DataDirectory to 0700
6554 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
6555 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
6557 o Minor bugfixes (testing):
6558 - Remove undefined behavior from the backtrace generator by removing
6559 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
6561 o Minor bugfixes (unit tests):
6562 - Allow the unit tests to pass even when DNS lookups of bogus
6563 addresses do not fail as expected. Fixes bug 20862 and 20863;
6564 bugfix on unit tests introduced in 0.2.8.1-alpha
6565 through 0.2.9.4-alpha.
6567 o Code simplification and refactoring:
6568 - Refactor code to manipulate global_origin_circuit_list into
6569 separate functions. Closes ticket 20921.
6571 o Documentation (formatting):
6572 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
6573 blocks were incorrectly appearing. Closes ticket 20885.
6575 o Documentation (man page):
6576 - Clarify many options in tor.1 and add some min/max values for
6577 HiddenService options. Closes ticket 21058.
6580 Changes in version 0.2.9.9 - 2017-01-23
6581 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
6582 cause relays and clients to crash, even if they were not built with
6583 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
6584 versions, and also affects 0.3.0.1-alpha: all relays running an affected
6585 version should upgrade.
6587 This release also resolves a client-side onion service reachability
6588 bug, and resolves a pair of small portability issues.
6590 o Major bugfixes (security):
6591 - Downgrade the "-ftrapv" option from "always on" to "only on when
6592 --enable-expensive-hardening is provided." This hardening option,
6593 like others, can turn survivable bugs into crashes -- and having
6594 it on by default made a (relatively harmless) integer overflow bug
6595 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
6596 bugfix on 0.2.9.1-alpha.
6598 o Major bugfixes (client, onion service):
6599 - Fix a client-side onion service reachability bug, where multiple
6600 socks requests to an onion service (or a single slow request)
6601 could cause us to mistakenly mark some of the service's
6602 introduction points as failed, and we cache that failure so
6603 eventually we run out and can't reach the service. Also resolves a
6604 mysterious "Remote server sent bogus reason code 65021" log
6605 warning. The bug was introduced in ticket 17218, where we tried to
6606 remember the circuit end reason as a uint16_t, which mangled
6607 negative values. Partially fixes bug 21056 and fixes bug 20307;
6608 bugfix on 0.2.8.1-alpha.
6610 o Minor features (geoip):
6611 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
6614 o Minor bugfixes (portability):
6615 - Avoid crashing when Tor is built using headers that contain
6616 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
6617 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
6619 - Fix Libevent detection on platforms without Libevent 1 headers
6620 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
6623 Changes in version 0.3.0.1-alpha - 2016-12-19
6624 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
6625 series. It strengthens Tor's link and circuit handshakes by
6626 identifying relays by their Ed25519 keys, improves the algorithm that
6627 clients use to choose and maintain their list of guards, and includes
6628 additional backend support for the next-generation hidden service
6629 design. It also contains numerous other small features and
6630 improvements to security, correctness, and performance.
6632 Below are the changes since 0.2.9.8.
6634 o Major features (guard selection algorithm):
6635 - Tor's guard selection algorithm has been redesigned from the
6636 ground up, to better support unreliable networks and restrictive
6637 sets of entry nodes, and to better resist guard-capture attacks by
6638 hostile local networks. Implements proposal 271; closes
6641 o Major features (next-generation hidden services):
6642 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
6643 prop224 aka "Next Generation Hidden Services". Service and clients
6644 don't use this functionality yet. Closes ticket 19043. Based on
6645 initial code by Alec Heifetz.
6646 - Relays now support the HSDir version 3 protocol, so that they can
6647 can store and serve v3 descriptors. This is part of the next-
6648 generation onion service work detailed in proposal 224. Closes
6651 o Major features (protocol, ed25519 identity keys):
6652 - Relays now use Ed25519 to prove their Ed25519 identities and to
6653 one another, and to clients. This algorithm is faster and more
6654 secure than the RSA-based handshake we've been doing until now.
6655 Implements the second big part of proposal 220; Closes
6657 - Clients now support including Ed25519 identity keys in the EXTEND2
6658 cells they generate. By default, this is controlled by a consensus
6659 parameter, currently disabled. You can turn this feature on for
6660 testing by setting ExtendByEd25519ID in your configuration. This
6661 might make your traffic appear different than the traffic
6662 generated by other users, however. Implements part of ticket
6663 15056; part of proposal 220.
6664 - Relays now understand requests to extend to other relays by their
6665 Ed25519 identity keys. When an Ed25519 identity key is included in
6666 an EXTEND2 cell, the relay will only extend the circuit if the
6667 other relay can prove ownership of that identity. Implements part
6668 of ticket 15056; part of proposal 220.
6670 o Major bugfixes (scheduler):
6671 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
6672 caused the channel scheduler to behave more or less randomly,
6673 rather than preferring channels with higher-priority circuits.
6674 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
6676 o Minor features (controller):
6677 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
6678 rather than "unrecognized." Closes ticket 20389; patch from
6681 o Minor features (diagnostic, directory client):
6682 - Warn when we find an unexpected inconsistency in directory
6683 download status objects. Prevents some negative consequences of
6686 o Minor features (directory authority):
6687 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
6688 default) to control whether authorities should try to probe relays
6689 by their Ed25519 link keys. This option will go away in a few
6690 releases--unless we encounter major trouble in our ed25519 link
6691 protocol rollout, in which case it will serve as a safety option.
6693 o Minor features (directory cache):
6694 - Relays and bridges will now refuse to serve the consensus they
6695 have if they know it is too old for a client to use. Closes
6698 o Minor features (ed25519 link handshake):
6699 - Advertise support for the ed25519 link handshake using the
6700 subprotocol-versions mechanism, so that clients can tell which
6701 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
6703 o Minor features (fingerprinting resistance, authentication):
6704 - Extend the length of RSA keys used for TLS link authentication to
6705 2048 bits. (These weren't used for forward secrecy; for forward
6706 secrecy, we used P256.) Closes ticket 13752.
6708 o Minor features (infrastructure):
6709 - Implement smartlist_add_strdup() function. Replaces the use of
6710 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
6712 o Minor bugfixes (client):
6713 - When clients that use bridges start up with a cached consensus on
6714 disk, they were ignoring it and downloading a new one. Now they
6715 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
6717 o Minor bugfixes (configuration):
6718 - Accept non-space whitespace characters after the severity level in
6719 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
6720 - Support "TByte" and "TBytes" units in options given in bytes.
6721 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
6722 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
6724 o Minor bugfixes (consensus weight):
6725 - Add new consensus method that initializes bw weights to 1 instead
6726 of 0. This prevents a zero weight from making it all the way to
6727 the end (happens in small testing networks) and causing an error.
6728 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
6730 o Minor bugfixes (descriptors):
6731 - Correctly recognise downloaded full descriptors as valid, even
6732 when using microdescriptors as circuits. This affects clients with
6733 FetchUselessDescriptors set, and may affect directory authorities.
6734 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
6736 o Minor bugfixes (directory system):
6737 - Download all consensus flavors, descriptors, and authority
6738 certificates when FetchUselessDescriptors is set, regardless of
6739 whether tor is a directory cache or not. Fixes bug 20667; bugfix
6740 on all recent tor versions.
6741 - Bridges and relays now use microdescriptors (like clients do)
6742 rather than old-style router descriptors. Now bridges will blend
6743 in with clients in terms of the circuits they build. Fixes bug
6744 6769; bugfix on 0.2.3.2-alpha.
6746 o Minor bugfixes (ed25519 certificates):
6747 - Correctly interpret ed25519 certificates that would expire some
6748 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
6750 o Minor bugfixes (hidden services):
6751 - Stop ignoring misconfigured hidden services. Instead, refuse to
6752 start tor until the misconfigurations have been corrected. Fixes
6753 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
6756 o Minor bugfixes (memory leak at exit):
6757 - Fix a small harmless memory leak at exit of the previously unused
6758 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
6761 o Minor bugfixes (util):
6762 - When finishing writing a file to disk, if we were about to replace
6763 the file with the temporary file created before and we fail to
6764 replace it, remove the temporary file so it doesn't stay on disk.
6765 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
6767 o Minor bugfixes (Windows):
6768 - Check for getpagesize before using it to mmap files. This fixes
6769 compilation in some MinGW environments. Fixes bug 20530; bugfix on
6770 0.1.2.1-alpha. Reported by "ice".
6772 o Code simplification and refactoring:
6773 - Abolish all global guard context in entrynodes.c; replace with new
6774 guard_selection_t structure as preparation for proposal 271.
6775 Closes ticket 19858.
6776 - Introduce rend_service_is_ephemeral() that tells if given onion
6777 service is ephemeral. Replace unclear NULL-checkings for service
6778 directory with this function. Closes ticket 20526.
6779 - Extract magic numbers in circuituse.c into defined variables.
6780 - Refactor circuit_is_available_for_use to remove unnecessary check.
6781 - Refactor circuit_predict_and_launch_new for readability and
6782 testability. Closes ticket 18873.
6783 - Refactor large if statement in purpose_needs_anonymity to use
6784 switch statement instead. Closes part of ticket 20077.
6785 - Refactor the hashing API to return negative values for errors, as
6786 is done as throughout the codebase. Closes ticket 20717.
6787 - Remove data structures that were used to index or_connection
6788 objects by their RSA identity digests. These structures are fully
6789 redundant with the similar structures used in the
6790 channel abstraction.
6791 - Remove duplicate code in the channel_write_*cell() functions.
6792 Closes ticket 13827; patch from Pingl.
6793 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
6794 use only purpose_needs_anonymity. Closes part of ticket 20077.
6795 - The code to generate and parse EXTEND and EXTEND2 cells has been
6796 replaced with code automatically generated by the
6800 - Include the "TBits" unit in Tor's man page. Fixes part of bug
6801 20622; bugfix on 0.2.5.1-alpha.
6802 - Change '1' to 'weight_scale' in consensus bw weights calculation
6803 comments, as that is reality. Closes ticket 20273. Patch
6805 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
6806 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
6808 - Stop the man page from incorrectly stating that HiddenServiceDir
6809 must already exist. Fixes 20486.
6810 - Clarify that when ClientRejectInternalAddresses is enabled (which
6811 is the default), multicast DNS hostnames for machines on the local
6812 network (of the form *.local) are also rejected. Closes
6816 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
6817 limit for relays running on a single IP applies to authority IP
6818 addresses as well as to non-authority IP addresses. Closes
6820 - The UseDirectoryGuards torrc option no longer exists: all users
6821 that use entry guards will also use directory guards. Related to
6822 proposal 271; implements part of ticket 20831.
6825 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
6826 from "overcaffeinated".
6827 - Perform the coding style checks when running the tests and fail
6828 when coding style violations are found. Closes ticket 5500.
6829 - Add tests for networkstatus_compute_bw_weights_v10.
6830 - Add unit tests circuit_predict_and_launch_new.
6831 - Extract dummy_origin_circuit_new so it can be used by other
6835 Changes in version 0.2.8.12 - 2016-12-19
6836 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
6837 below) where Tor clients could crash when attempting to visit a
6838 hostile hidden service. Clients are recommended to upgrade as packages
6839 become available for their systems.
6841 It also includes an updated list of fallback directories, backported
6844 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
6845 backported to 0.2.8 in the future.
6847 o Major bugfixes (parsing, security, backported from 0.2.9.8):
6848 - Fix a bug in parsing that could cause clients to read a single
6849 byte past the end of an allocated region. This bug could be used
6850 to cause hardened clients (built with --enable-expensive-hardening)
6851 to crash if they tried to visit a hostile hidden service. Non-
6852 hardened clients are only affected depending on the details of
6853 their platform's memory allocator. Fixes bug 21018; bugfix on
6854 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
6855 2016-12-002 and as CVE-2016-1254.
6857 o Minor features (fallback directory list, backported from 0.2.9.8):
6858 - Replace the 81 remaining fallbacks of the 100 originally
6859 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
6860 fallbacks (123 new, 54 existing, 27 removed) generated in December
6861 2016. Resolves ticket 20170.
6863 o Minor features (geoip, backported from 0.2.9.7-rc):
6864 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
6868 Changes in version 0.2.9.8 - 2016-12-19
6869 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
6871 The Tor 0.2.9 series makes mandatory a number of security features
6872 that were formerly optional. It includes support for a new shared-
6873 randomness protocol that will form the basis for next generation
6874 hidden services, includes a single-hop hidden service mode for
6875 optimizing .onion services that don't actually want to be hidden,
6876 tries harder not to overload the directory authorities with excessive
6877 downloads, and supports a better protocol versioning scheme for
6878 improved compatibility with other implementations of the Tor protocol.
6880 And of course, there are numerous other bugfixes and improvements.
6882 This release also includes a fix for a medium-severity issue (bug
6883 21018 below) where Tor clients could crash when attempting to visit a
6884 hostile hidden service. Clients are recommended to upgrade as packages
6885 become available for their systems.
6887 Below are the changes since 0.2.9.7-rc. For a list of all changes
6888 since 0.2.8, see the ReleaseNotes file.
6890 o Major bugfixes (parsing, security):
6891 - Fix a bug in parsing that could cause clients to read a single
6892 byte past the end of an allocated region. This bug could be used
6893 to cause hardened clients (built with --enable-expensive-hardening)
6894 to crash if they tried to visit a hostile hidden service. Non-
6895 hardened clients are only affected depending on the details of
6896 their platform's memory allocator. Fixes bug 21018; bugfix on
6897 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
6898 2016-12-002 and as CVE-2016-1254.
6900 o Minor features (fallback directory list):
6901 - Replace the 81 remaining fallbacks of the 100 originally
6902 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
6903 fallbacks (123 new, 54 existing, 27 removed) generated in December
6904 2016. Resolves ticket 20170.
6907 Changes in version 0.2.9.7-rc - 2016-12-12
6908 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
6909 including a few that had prevented tests from passing on
6912 o Minor features (geoip):
6913 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
6916 o Minor bugfix (build):
6917 - The current Git revision when building from a local repository is
6918 now detected correctly when using git worktrees. Fixes bug 20492;
6919 bugfix on 0.2.3.9-alpha.
6921 o Minor bugfixes (directory authority):
6922 - When computing old Tor protocol line version in protover, we were
6923 looking at 0.2.7.5 twice instead of a specific case for
6924 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
6926 o Minor bugfixes (download scheduling):
6927 - Resolve a "bug" warning when considering a download schedule whose
6928 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
6930 o Minor bugfixes (logging):
6931 - Downgrade a harmless log message about the
6932 pending_entry_connections list from "warn" to "info". Mitigates
6935 o Minor bugfixes (memory leak):
6936 - Fix a small memory leak when receiving AF_UNIX connections on a
6937 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
6938 - When moving a signed descriptor object from a source to an
6939 existing destination, free the allocated memory inside that
6940 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
6942 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
6943 - Fix a memory leak and use-after-free error when removing entries
6944 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
6945 0.2.5.5-alpha. Patch from "cypherpunks".
6947 o Minor bugfixes (portability):
6948 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
6949 Fixes bug 20935; bugfix on 0.2.9.6-rc.
6951 o Minor bugfixes (unit tests):
6952 - Stop expecting NetBSD unit tests to report success for ipfw. Part
6953 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
6954 - Fix tolerances in unit tests for monotonic time comparisons
6955 between nanoseconds and microseconds. Previously, we accepted a 10
6956 us difference only, which is not realistic on every platform's
6957 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
6958 - Remove a double-free in the single onion service unit test. Stop
6959 ignoring a return value. Make future changes less error-prone.
6960 Fixes bug 20864; bugfix on 0.2.9.6-rc.
6963 Changes in version 0.2.8.11 - 2016-12-08
6964 Tor 0.2.8.11 backports fixes for additional portability issues that
6965 could prevent Tor from building correctly on OSX Sierra, or with
6966 OpenSSL 1.1. Affected users should upgrade; others can safely stay
6969 o Minor bugfixes (portability):
6970 - Avoid compilation errors when building on OSX Sierra. Sierra began
6971 to support the getentropy() and clock_gettime() APIs, but created
6972 a few problems in doing so. Tor 0.2.9 has a more thorough set of
6973 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
6974 monotonic time interfaces. Fixes bug 20865. Bugfix
6977 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
6978 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
6979 architectures. Closes ticket 20588.
6982 Changes in version 0.2.8.10 - 2016-12-02
6983 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
6984 unusable after they left standby mode. It also backports fixes for
6985 a few portability issues and a small but problematic memory leak.
6987 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
6988 - When Tor leaves standby because of a new application request, open
6989 circuits as needed to serve that request. Previously, we would
6990 potentially wait a very long time. Fixes part of bug 19969; bugfix
6993 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
6994 - Clients now respond to new application stream requests immediately
6995 when they arrive, rather than waiting up to one second before
6996 starting to handle them. Fixes part of bug 19969; bugfix
6999 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
7000 - Work around a bug in the OSX 10.12 SDK that would prevent us from
7001 successfully targeting earlier versions of OSX. Resolves
7004 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
7005 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
7006 20551; bugfix on 0.2.1.1-alpha.
7008 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
7009 - Work around a memory leak in OpenSSL 1.1 when encoding public
7010 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
7012 o Minor features (geoip):
7013 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
7016 Changes in version 0.2.9.6-rc - 2016-12-02
7017 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
7018 version. We hope that it will be ready to become stable soon, and we
7019 encourage everyone to test this release. If no showstopper bugs are
7020 found here, the next 0.2.9 release will be stable.
7022 o Major bugfixes (relay, resolver, logging):
7023 - For relays that don't know their own address, avoid attempting a
7024 local hostname resolve for each descriptor we download. This
7025 will cut down on the number of "Success: chose address 'x.x.x.x'"
7026 log lines, and also avoid confusing clock jumps if the resolver
7027 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
7029 o Minor bugfixes (client, fascistfirewall):
7030 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
7031 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
7033 o Minor bugfixes (hidden services):
7034 - Stop ignoring the anonymity status of saved keys for hidden
7035 services and single onion services when first starting tor.
7036 Instead, refuse to start tor if any hidden service key has been
7037 used in a different hidden service anonymity mode. Fixes bug
7038 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
7040 o Minor bugfixes (portability):
7041 - Work around a bug in the OSX 10.12 SDK that would prevent us from
7042 successfully targeting earlier versions of OSX. Resolves
7044 - Run correctly when built on Windows build environments that
7045 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
7047 o Minor bugfixes (single onion services, Tor2web):
7048 - Stop complaining about long-term one-hop circuits deliberately
7049 created by single onion services and Tor2web. These log messages
7050 are intended to diagnose issue 8387, which relates to circuits
7051 hanging around forever for no reason. Fixes bug 20613; bugfix on
7052 0.2.9.1-alpha. Reported by "pastly".
7054 o Minor bugfixes (unit tests):
7055 - Stop spurious failures in the local interface address discovery
7056 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
7060 - Correct the minimum bandwidth value in torrc.sample, and queue a
7061 corresponding change for torrc.minimal. Closes ticket 20085.
7064 Changes in version 0.2.9.5-alpha - 2016-11-08
7065 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
7066 version. We believe one or two probably remain, and we encourage
7067 everyone to test this release.
7069 o Major bugfixes (client performance):
7070 - Clients now respond to new application stream requests immediately
7071 when they arrive, rather than waiting up to one second before
7072 starting to handle them. Fixes part of bug 19969; bugfix
7075 o Major bugfixes (client reliability):
7076 - When Tor leaves standby because of a new application request, open
7077 circuits as needed to serve that request. Previously, we would
7078 potentially wait a very long time. Fixes part of bug 19969; bugfix
7081 o Major bugfixes (download scheduling):
7082 - When using an exponential backoff schedule, do not give up on
7083 downloading just because we have failed a bunch of times. Since
7084 each delay is longer than the last, retrying indefinitely won't
7085 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
7086 - If a consensus expires while we are waiting for certificates to
7087 download, stop waiting for certificates.
7088 - If we stop waiting for certificates less than a minute after we
7089 started downloading them, do not consider the certificate download
7090 failure a separate failure. Fixes bug 20533; bugfix
7092 - Remove the maximum delay on exponential-backoff scheduling. Since
7093 we now allow an infinite number of failures (see ticket 20536), we
7094 must now allow the time to grow longer on each failure. Fixes part
7095 of bug 20534; bugfix on 0.2.9.1-alpha.
7096 - Make our initial download delays closer to those from 0.2.8. Fixes
7097 another part of bug 20534; bugfix on 0.2.9.1-alpha.
7098 - When determining when to download a directory object, handle times
7099 after 2038 if the operating system supports them. (Someday this
7100 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
7101 - When using exponential backoff in test networks, use a lower
7102 exponent, so the delays do not vary as much. This helps test
7103 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
7105 o Minor features (geoip):
7106 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
7109 o Minor bugfixes (client directory scheduling):
7110 - Treat "relay too busy to answer request" as a failed request and a
7111 reason to back off on our retry frequency. This is safe now that
7112 exponential backoffs retry indefinitely, and avoids a bug where we
7113 would reset our download schedule erroneously. Fixes bug 20593;
7114 bugfix on 0.2.9.1-alpha.
7116 o Minor bugfixes (client, logging):
7117 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
7118 assume all nodes support EXTEND2. Use ntor whenever a key is
7119 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
7120 - On DNSPort, stop logging a BUG warning on a failed hostname
7121 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
7123 o Minor bugfixes (hidden services):
7124 - When configuring hidden services, check every hidden service
7125 directory's permissions. Previously, we only checked the last
7126 hidden service. Fixes bug 20529; bugfix the work to fix 13942
7129 o Minor bugfixes (portability):
7130 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
7131 architectures. Closes ticket 20588.
7132 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
7133 removed the ECDH ciphers which caused the tests to fail on
7134 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
7135 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
7136 20551; bugfix on 0.2.1.1-alpha.
7138 o Minor bugfixes (relay bootstrap):
7139 - Ensure relays don't make multiple connections during bootstrap.
7140 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
7142 o Minor bugfixes (relay):
7143 - Work around a memory leak in OpenSSL 1.1 when encoding public
7144 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
7145 - Avoid a small memory leak when informing worker threads about
7146 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
7147 - Do not try to parallelize workers more than 16x without the user
7148 explicitly configuring us to do so, even if we do detect more than
7149 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
7151 o Minor bugfixes (single onion services):
7152 - Start correctly when creating a single onion service in a
7153 directory that did not previously exist. Fixes bug 20484; bugfix
7156 o Minor bugfixes (testing):
7157 - Avoid a unit test failure on systems with over 16 detectable CPU
7158 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
7161 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
7162 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
7163 - Module-level documentation for several more modules. Closes
7164 tickets 19287 and 19290.
7167 Changes in version 0.2.8.9 - 2016-10-17
7168 Tor 0.2.8.9 backports a fix for a security hole in previous versions
7169 of Tor that would allow a remote attacker to crash a Tor client,
7170 hidden service, relay, or authority. All Tor users should upgrade to
7171 this version, or to 0.2.9.4-alpha. Patches will be released for older
7174 o Major features (security fixes, also in 0.2.9.4-alpha):
7175 - Prevent a class of security bugs caused by treating the contents
7176 of a buffer chunk as if they were a NUL-terminated string. At
7177 least one such bug seems to be present in all currently used
7178 versions of Tor, and would allow an attacker to remotely crash
7179 most Tor instances, especially those compiled with extra compiler
7180 hardening. With this defense in place, such bugs can't crash Tor,
7181 though we should still fix them as they occur. Closes ticket
7182 20384 (TROVE-2016-10-001).
7184 o Minor features (geoip):
7185 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
7189 Changes in version 0.2.9.4-alpha - 2016-10-17
7190 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
7191 that would allow a remote attacker to crash a Tor client, hidden
7192 service, relay, or authority. All Tor users should upgrade to this
7193 version, or to 0.2.8.9. Patches will be released for older versions
7196 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
7197 previous versions of Tor, including the implementation of a feature to
7198 future- proof the Tor ecosystem against protocol changes, some bug
7199 fixes necessary for Tor Browser to use unix domain sockets correctly,
7200 and several portability improvements. We anticipate that this will be
7201 the last alpha in the Tor 0.2.9 series, and that the next release will
7202 be a release candidate.
7204 o Major features (security fixes):
7205 - Prevent a class of security bugs caused by treating the contents
7206 of a buffer chunk as if they were a NUL-terminated string. At
7207 least one such bug seems to be present in all currently used
7208 versions of Tor, and would allow an attacker to remotely crash
7209 most Tor instances, especially those compiled with extra compiler
7210 hardening. With this defense in place, such bugs can't crash Tor,
7211 though we should still fix them as they occur. Closes ticket
7212 20384 (TROVE-2016-10-001).
7214 o Major features (subprotocol versions):
7215 - Tor directory authorities now vote on a set of recommended
7216 subprotocol versions, and on a set of required subprotocol
7217 versions. Clients and relays that lack support for a _required_
7218 subprotocol version will not start; those that lack support for a
7219 _recommended_ subprotocol version will warn the user to upgrade.
7220 Closes ticket 19958; implements part of proposal 264.
7221 - Tor now uses "subprotocol versions" to indicate compatibility.
7222 Previously, versions of Tor looked at the declared Tor version of
7223 a relay to tell whether they could use a given feature. Now, they
7224 should be able to rely on its declared subprotocol versions. This
7225 change allows compatible implementations of the Tor protocol(s) to
7226 exist without pretending to be 100% bug-compatible with particular
7227 releases of Tor itself. Closes ticket 19958; implements part of
7230 o Minor feature (fallback directories):
7231 - Remove broken fallbacks from the hard-coded fallback directory
7232 list. Closes ticket 20190; patch by teor.
7234 o Minor features (client, directory):
7235 - Since authorities now omit all routers that lack the Running and
7236 Valid flags, we assume that any relay listed in the consensus must
7237 have those flags. Closes ticket 20001; implements part of
7240 o Minor features (compilation, portability):
7241 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
7244 o Minor features (development tools, etags):
7245 - Teach the "make tags" Makefile target how to correctly find
7246 "MOCK_IMPL" function definitions. Patch from nherring; closes
7249 o Minor features (geoip):
7250 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
7253 o Minor features (unix domain sockets):
7254 - When configuring a unix domain socket for a SocksPort,
7255 ControlPort, or Hidden service, you can now wrap the address in
7256 quotes, using C-style escapes inside the quotes. This allows unix
7257 domain socket paths to contain spaces.
7259 o Minor features (virtual addresses):
7260 - Increase the maximum number of bits for the IPv6 virtual network
7261 prefix from 16 to 104. In this way, the condition for address
7262 allocation is less restrictive. Closes ticket 20151; feature
7265 o Minor bugfixes (address discovery):
7266 - Stop reordering IP addresses returned by the OS. This makes it
7267 more likely that Tor will guess the same relay IP address every
7268 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
7269 Reported by René Mayrhofer, patch by "cypherpunks".
7271 o Minor bugfixes (client, unix domain sockets):
7272 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
7273 the client address is meaningless. Fixes bug 20261; bugfix
7276 o Minor bugfixes (compilation, OpenBSD):
7277 - Detect Libevent2 functions correctly on systems that provide
7278 libevent2, but where libevent1 is linked with -levent. Fixes bug
7279 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
7281 o Minor bugfixes (configuration):
7282 - When parsing quoted configuration values from the torrc file,
7283 handle windows line endings correctly. Fixes bug 19167; bugfix on
7284 0.2.0.16-alpha. Patch from "Pingl".
7286 o Minor bugfixes (getpass):
7287 - Defensively fix a non-triggerable heap corruption at do_getpass()
7288 to protect ourselves from mistakes in the future. Fixes bug
7289 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
7292 o Minor bugfixes (hidden service):
7293 - Allow hidden services to run on IPv6 addresses even when the
7294 IPv6Exit option is not set. Fixes bug 18357; bugfix
7298 - Add module-level internal documentation for 36 C files that
7299 previously didn't have a high-level overview. Closes ticket #20385.
7301 o Required libraries:
7302 - When building with OpenSSL, Tor now requires version 1.0.1 or
7303 later. OpenSSL 1.0.0 and earlier are no longer supported by the
7304 OpenSSL team, and should not be used. Closes ticket 20303.
7307 Changes in version 0.2.9.3-alpha - 2016-09-23
7308 Tor 0.2.9.3-alpha adds improved support for entities that want to make
7309 high-performance services available through the Tor .onion mechanism
7310 without themselves receiving anonymity as they host those services. It
7311 also tries harder to ensure that all steps on a circuit are using the
7312 strongest crypto possible, strengthens some TLS properties, and
7313 resolves several bugs -- including a pair of crash bugs from the 0.2.8
7314 series. Anybody running an earlier version of 0.2.9.x should upgrade.
7316 o Major bugfixes (crash, also in 0.2.8.8):
7317 - Fix a complicated crash bug that could affect Tor clients
7318 configured to use bridges when replacing a networkstatus consensus
7319 in which one of their bridges was mentioned. OpenBSD users saw
7320 more crashes here, but all platforms were potentially affected.
7321 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
7323 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
7324 - Fix a timing-dependent assertion failure that could occur when we
7325 tried to flush from a circuit after having freed its cells because
7326 of an out-of-memory condition. Fixes bug 20203; bugfix on
7327 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
7330 o Major features (circuit building, security):
7331 - Authorities, relays and clients now require ntor keys in all
7332 descriptors, for all hops (except for rare hidden service protocol
7333 cases), for all circuits, and for all other roles. Part of
7335 - Tor authorities, relays, and clients only use ntor, except for
7336 rare cases in the hidden service protocol. Part of ticket 19163.
7338 o Major features (single-hop "hidden" services):
7339 - Add experimental HiddenServiceSingleHopMode and
7340 HiddenServiceNonAnonymousMode options. When both are set to 1,
7341 every hidden service on a Tor instance becomes a non-anonymous
7342 Single Onion Service. Single Onions make one-hop (direct)
7343 connections to their introduction and renzedvous points. One-hop
7344 circuits make Single Onion servers easily locatable, but clients
7345 remain location-anonymous. This is compatible with the existing
7346 hidden service implementation, and works on the current tor
7347 network without any changes to older relays or clients. Implements
7348 proposal 260, completes ticket 17178. Patch by teor and asn.
7350 o Major features (resource management):
7351 - Tor can now notice it is about to run out of sockets, and
7352 preemptively close connections of lower priority. (This feature is
7353 off by default for now, since the current prioritizing method is
7354 yet not mature enough. You can enable it by setting
7355 "DisableOOSCheck 0", but watch out: it might close some sockets
7356 you would rather have it keep.) Closes ticket 18640.
7358 o Major bugfixes (circuit building):
7359 - Hidden service client-to-intro-point and service-to-rendezvous-
7360 point circuits use the TAP key supplied by the protocol, to avoid
7361 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
7363 o Major bugfixes (compilation, OpenBSD):
7364 - Fix a Libevent-detection bug in our autoconf script that would
7365 prevent Tor from linking successfully on OpenBSD. Patch from
7366 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
7368 o Major bugfixes (hidden services):
7369 - Clients now require hidden services to include the TAP keys for
7370 their intro points in the hidden service descriptor. This prevents
7371 an inadvertent upgrade to ntor, which a malicious hidden service
7372 could use to distinguish clients by consensus version. Fixes bug
7373 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
7375 o Minor features (security, TLS):
7376 - Servers no longer support clients that without AES ciphersuites.
7377 (3DES is no longer considered an acceptable cipher.) We believe
7378 that no such Tor clients currently exist, since Tor has required
7379 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
7381 o Minor feature (fallback directories):
7382 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
7383 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
7384 2016. Closes ticket 20190; patch by teor.
7386 o Minor features (geoip, also in 0.2.8.8):
7387 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
7390 o Minor feature (port flags):
7391 - Add new flags to the *Port options to finer control over which
7392 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
7393 and the synthetic flag OnionTrafficOnly, which is equivalent to
7394 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
7395 18693; patch by "teor".
7397 o Minor features (directory authority):
7398 - After voting, if the authorities decide that a relay is not
7399 "Valid", they no longer include it in the consensus at all. Closes
7400 ticket 20002; implements part of proposal 272.
7402 o Minor features (testing):
7403 - Disable memory protections on OpenBSD when performing our unit
7404 tests for memwipe(). The test deliberately invokes undefined
7405 behavior, and the OpenBSD protections interfere with this. Patch
7406 from "rubiate". Closes ticket 20066.
7408 o Minor features (testing, ipv6):
7409 - Add the single-onion and single-onion-ipv6 chutney targets to
7410 "make test-network-all". This requires a recent chutney version
7411 with the single onion network flavours (git c72a652 or later).
7412 Closes ticket 20072; patch by teor.
7413 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
7414 tests. Remove bridges+hs, as it's somewhat redundant. This
7415 requires a recent chutney version that supports IPv6 clients,
7416 relays, and authorities. Closes ticket 20069; patch by teor.
7418 o Minor features (Tor2web):
7419 - Make Tor2web clients respect ReachableAddresses. This feature was
7420 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
7421 0.2.8.7. Implements feature 20034. Patch by teor.
7423 o Minor features (unit tests):
7424 - We've done significant work to make the unit tests run faster.
7425 - Our link-handshake unit tests now check that when invalid
7426 handshakes fail, they fail with the error messages we expected.
7427 - Our unit testing code that captures log messages no longer
7428 prevents them from being written out if the user asked for them
7429 (by passing --debug or --info or or --notice --warn to the "test"
7430 binary). This change prevents us from missing unexpected log
7431 messages simply because we were looking for others. Related to
7433 - The unit tests now log all warning messages with the "BUG" flag.
7434 Previously, they only logged errors by default. This change will
7435 help us make our testing code more correct, and make sure that we
7436 only hit this code when we mean to. In the meantime, however,
7437 there will be more warnings in the unit test logs than before.
7438 This is preparatory work for ticket 19999.
7439 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
7440 assertion as a test failure.
7442 o Minor bug fixes (circuits):
7443 - Use the CircuitBuildTimeout option whenever
7444 LearnCircuitBuildTimeout is disabled. Previously, we would respect
7445 the option when a user disabled it, but not when it was disabled
7446 because some other option was set. Fixes bug 20073; bugfix on
7447 0.2.4.12-alpha. Patch by teor.
7449 o Minor bugfixes (allocation):
7450 - Change how we allocate memory for large chunks on buffers, to
7451 avoid a (currently impossible) integer overflow, and to waste less
7452 space when allocating unusually large chunks. Fixes bug 20081;
7453 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
7454 - Always include orconfig.h before including any other C headers.
7455 Sometimes, it includes macros that affect the behavior of the
7456 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
7457 first version to use AC_USE_SYSTEM_EXTENSIONS).
7458 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
7459 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
7460 Patch from Gisle Vanem.
7461 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
7462 They apparently require a set of annotations that we aren't
7463 currently using, and they create false positives in our pthreads
7464 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
7466 o Minor bugfixes (directory authority):
7467 - Die with a more useful error when the operator forgets to place
7468 the authority_signing_key file into the keys directory. This
7469 avoids an uninformative assert & traceback about having an invalid
7470 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
7471 - When allowing private addresses, mark Exits that only exit to
7472 private locations as such. Fixes bug 20064; bugfix
7475 o Minor bugfixes (documentation):
7476 - Document the default PathsNeededToBuildCircuits value that's used
7477 by clients when the directory authorities don't set
7478 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
7479 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
7480 - Fix manual for the User option: it takes a username, not a UID.
7481 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
7484 o Minor bugfixes (hidden services):
7485 - Stop logging intro point details to the client log on certain
7486 error conditions. Fixed as part of bug 20012; bugfix on
7487 0.2.4.8-alpha. Patch by teor.
7489 o Minor bugfixes (IPv6, testing):
7490 - Check for IPv6 correctly on Linux when running test networks.
7491 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
7493 o Minor bugfixes (Linux seccomp2 sandbox):
7494 - Add permission to run the sched_yield() and sigaltstack() system
7495 calls, in order to support versions of Tor compiled with asan or
7496 ubsan code that use these calls. Now "sandbox 1" and
7497 "--enable-expensive-hardening" should be compatible on more
7498 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
7500 o Minor bugfixes (logging):
7501 - When logging a message from the BUG() macro, be explicit about
7502 what we were asserting. Previously we were confusing what we were
7503 asserting with what the bug was. Fixes bug 20093; bugfix
7505 - When we are unable to remove the bw_accounting file, do not warn
7506 if the reason we couldn't remove it was that it didn't exist.
7507 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
7509 o Minor bugfixes (option parsing):
7510 - Count unix sockets when counting client listeners (SOCKS, Trans,
7511 NATD, and DNS). This has no user-visible behaviour changes: these
7512 options are set once, and never read. Required for correct
7513 behaviour in ticket 17178. Fixes bug 19677; bugfix on
7514 0.2.6.3-alpha. Patch by teor.
7516 o Minor bugfixes (options):
7517 - Check the consistency of UseEntryGuards and EntryNodes more
7518 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
7520 - Stop changing the configured value of UseEntryGuards on
7521 authorities and Tor2web clients. Fixes bug 20074; bugfix on
7522 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
7525 o Minor bugfixes (Tor2web):
7526 - Prevent Tor2web clients running hidden services, these services
7527 are not anonymous due to the one-hop client paths. Fixes bug
7528 19678. Patch by teor.
7530 o Minor bugfixes (unit tests):
7531 - Fix a shared-random unit test that was failing on big endian
7532 architectures due to internal representation of a integer copied
7533 to a buffer. The test is changed to take a full 32 bytes of data
7534 and use the output of a python script that make the COMMIT and
7535 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
7537 - The tor_tls_server_info_callback unit test no longer crashes when
7538 debug-level logging is turned on. Fixes bug 20041; bugfix
7542 Changes in version 0.2.8.8 - 2016-09-23
7543 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
7544 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
7545 who select public relays as their bridges.
7547 o Major bugfixes (crash):
7548 - Fix a complicated crash bug that could affect Tor clients
7549 configured to use bridges when replacing a networkstatus consensus
7550 in which one of their bridges was mentioned. OpenBSD users saw
7551 more crashes here, but all platforms were potentially affected.
7552 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
7554 o Major bugfixes (relay, OOM handler):
7555 - Fix a timing-dependent assertion failure that could occur when we
7556 tried to flush from a circuit after having freed its cells because
7557 of an out-of-memory condition. Fixes bug 20203; bugfix on
7558 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
7561 o Minor feature (fallback directories):
7562 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
7563 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
7564 2016. Closes ticket 20190; patch by teor.
7566 o Minor features (geoip):
7567 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
7571 Changes in version 0.2.9.2-alpha - 2016-08-24
7572 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
7573 several new features and bugfixes. It also includes an important
7574 authority update and an important bugfix from 0.2.8.7. Everyone who
7575 sets the ReachableAddresses option, and all bridges, are strongly
7576 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
7578 o Directory authority changes (also in 0.2.8.7):
7579 - The "Tonga" bridge authority has been retired; the new bridge
7580 authority is "Bifroest". Closes tickets 19728 and 19690.
7582 o Major bugfixes (client, security, also in 0.2.8.7):
7583 - Only use the ReachableAddresses option to restrict the first hop
7584 in a path. In earlier versions of 0.2.8.x, it would apply to
7585 every hop in the path, with a possible degradation in anonymity
7586 for anyone using an uncommon ReachableAddress setting. Fixes bug
7587 19973; bugfix on 0.2.8.2-alpha.
7589 o Major features (user interface):
7590 - Tor now supports the ability to declare options deprecated, so
7591 that we can recommend that people stop using them. Previously,
7592 this was done in an ad-hoc way. Closes ticket 19820.
7594 o Major bugfixes (directory downloads):
7595 - Avoid resetting download status for consensuses hourly, since we
7596 already have another, smarter retry mechanism. Fixes bug 8625;
7597 bugfix on 0.2.0.9-alpha.
7599 o Minor features (config):
7600 - Warn users when descriptor and port addresses are inconsistent.
7601 Mitigates bug 13953; patch by teor.
7603 o Minor features (geoip):
7604 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
7607 o Minor features (user interface):
7608 - There is a new --list-deprecated-options command-line option to
7609 list all of the deprecated options. Implemented as part of
7612 o Minor bugfixes (code style):
7613 - Fix an integer signedness conversion issue in the case conversion
7614 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
7616 o Minor bugfixes (compilation):
7617 - Build correctly on versions of libevent2 without support for
7618 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
7620 - Fix a compilation warning on GCC versions before 4.6. Our
7621 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
7622 when it is also required as an argument to the compiler pragma.
7623 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
7625 o Minor bugfixes (compilation, also in 0.2.8.7):
7626 - Remove an inappropriate "inline" in tortls.c that was causing
7627 warnings on older versions of GCC. Fixes bug 19903; bugfix
7630 o Minor bugfixes (fallback directories, also in 0.2.8.7):
7631 - Avoid logging a NULL string pointer when loading fallback
7632 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
7633 and 0.2.8.1-alpha. Report and patch by "rubiate".
7635 o Minor bugfixes (logging):
7636 - Log a more accurate message when we fail to dump a microdescriptor.
7637 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
7639 o Minor bugfixes (memory leak):
7640 - Fix a series of slow memory leaks related to parsing torrc files
7641 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
7643 o Deprecated features:
7644 - A number of DNS-cache-related sub-options for client ports are now
7645 deprecated for security reasons, and may be removed in a future
7646 version of Tor. (We believe that client-side DNS caching is a bad
7647 idea for anonymity, and you should not turn it on.) The options
7648 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
7649 UseIPv4Cache, and UseIPv6Cache.
7650 - A number of options are deprecated for security reasons, and may
7651 be removed in a future version of Tor. The options are:
7652 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
7653 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
7654 CloseHSClientCircuitsImmediatelyOnTimeout,
7655 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
7656 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
7657 UseNTorHandshake, and WarnUnsafeSocks.
7658 - The *ListenAddress options are now deprecated as unnecessary: the
7659 corresponding *Port options should be used instead. These options
7660 may someday be removed. The affected options are:
7661 ControlListenAddress, DNSListenAddress, DirListenAddress,
7662 NATDListenAddress, ORListenAddress, SocksListenAddress,
7663 and TransListenAddress.
7666 - Correct the IPv6 syntax in our documentation for the
7667 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
7670 - We no longer include the (dead, deprecated) bufferevent code in
7671 Tor. Closes ticket 19450. Based on a patch from U+039b.
7674 Changes in version 0.2.8.7 - 2016-08-24
7675 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
7676 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
7677 who sets the ReachableAddresses option, and all bridges, are strongly
7678 encouraged to upgrade.
7680 o Directory authority changes:
7681 - The "Tonga" bridge authority has been retired; the new bridge
7682 authority is "Bifroest". Closes tickets 19728 and 19690.
7684 o Major bugfixes (client, security):
7685 - Only use the ReachableAddresses option to restrict the first hop
7686 in a path. In earlier versions of 0.2.8.x, it would apply to
7687 every hop in the path, with a possible degradation in anonymity
7688 for anyone using an uncommon ReachableAddress setting. Fixes bug
7689 19973; bugfix on 0.2.8.2-alpha.
7691 o Minor features (geoip):
7692 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
7695 o Minor bugfixes (compilation):
7696 - Remove an inappropriate "inline" in tortls.c that was causing
7697 warnings on older versions of GCC. Fixes bug 19903; bugfix
7700 o Minor bugfixes (fallback directories):
7701 - Avoid logging a NULL string pointer when loading fallback
7702 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
7703 and 0.2.8.1-alpha. Report and patch by "rubiate".
7706 Changes in version 0.2.9.1-alpha - 2016-08-08
7707 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
7708 series. It improves our support for hardened builds and compiler
7709 warnings, deploys some critical infrastructure for improvements to
7710 hidden services, includes a new timing backend that we hope to use for
7711 better support for traffic padding, makes it easier for programmers to
7712 log unexpected events, and contains other small improvements to
7713 security, correctness, and performance.
7715 Below are the changes since 0.2.8.6.
7717 o New system requirements:
7718 - Tor now requires Libevent version 2.0.10-stable or later. Older
7719 versions of Libevent have less efficient backends for several
7720 platforms, and lack the DNS code that we use for our server-side
7721 DNS support. This implements ticket 19554.
7722 - Tor now requires zlib version 1.2 or later, for security,
7723 efficiency, and (eventually) gzip support. (Back when we started,
7724 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
7725 released in 2003. We recommend the latest version.)
7727 o Major features (build, hardening):
7728 - Tor now builds with -ftrapv by default on compilers that support
7729 it. This option detects signed integer overflow (which C forbids),
7730 and turns it into a hard-failure. We do not apply this option to
7731 code that needs to run in constant time to avoid side-channels;
7732 instead, we use -fwrapv in that code. Closes ticket 17983.
7733 - When --enable-expensive-hardening is selected, stop applying the
7734 clang/gcc sanitizers to code that needs to run in constant time.
7735 Although we are aware of no introduced side-channels, we are not
7736 able to prove that there are none. Related to ticket 17983.
7738 o Major features (compilation):
7739 - Our big list of extra GCC warnings is now enabled by default when
7740 building with GCC (or with anything like Clang that claims to be
7741 GCC-compatible). To make all warnings into fatal compilation
7742 errors, pass --enable-fatal-warnings to configure. Closes
7744 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
7745 turn on C and POSIX extensions. (Previously, we attempted to do
7746 this on an ad hoc basis.) Closes ticket 19139.
7748 o Major features (directory authorities, hidden services):
7749 - Directory authorities can now perform the shared randomness
7750 protocol specified by proposal 250. Using this protocol, directory
7751 authorities generate a global fresh random value every day. In the
7752 future, this value will be used by hidden services to select
7753 HSDirs. This release implements the directory authority feature;
7754 the hidden service side will be implemented in the future as part
7755 of proposal 224. Resolves ticket 16943; implements proposal 250.
7757 o Major features (downloading, random exponential backoff):
7758 - When we fail to download an object from a directory service, wait
7759 for an (exponentially increasing) randomized amount of time before
7760 retrying, rather than a fixed interval as we did before. This
7761 prevents a group of Tor instances from becoming too synchronized,
7762 or a single Tor instance from becoming too predictable, in its
7763 download schedule. Closes ticket 15942.
7765 o Major bugfixes (exit policies):
7766 - Avoid disclosing exit outbound bind addresses, configured port
7767 bind addresses, and local interface addresses in relay descriptors
7768 by default under ExitPolicyRejectPrivate. Instead, only reject
7769 these (otherwise unlisted) addresses if
7770 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
7771 0.2.7.2-alpha. Patch by teor.
7773 o Major bugfixes (hidden service client):
7774 - Allow Tor clients with appropriate controllers to work with
7775 FetchHidServDescriptors set to 0. Previously, this option also
7776 disabled descriptor cache lookup, thus breaking hidden services
7777 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
7779 o Minor features (build, hardening):
7780 - Detect and work around a libclang_rt problem that would prevent
7781 clang from finding __mulodi4() on some 32-bit platforms, and thus
7782 keep -ftrapv from linking on those systems. Closes ticket 19079.
7783 - When building on a system without runtime support for the runtime
7784 hardening options, try to log a useful warning at configuration
7785 time, rather than an incomprehensible warning at link time. If
7786 expensive hardening was requested, this warning becomes an error.
7787 Closes ticket 18895.
7789 o Minor features (code safety):
7790 - In our integer-parsing functions, ensure that maxiumum value we
7791 give is no smaller than the minimum value. Closes ticket 19063;
7794 o Minor features (controller):
7795 - Implement new GETINFO queries for all downloads that use
7796 download_status_t to schedule retries. This allows controllers to
7797 examine the schedule for pending downloads. Closes ticket 19323.
7798 - Allow controllers to configure basic client authorization on
7799 hidden services when they create them with the ADD_ONION control
7800 command. Implements ticket 15588. Patch by "special".
7801 - Fire a STATUS_SERVER controller event whenever the hibernation
7802 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
7804 o Minor features (directory authority):
7805 - Directory authorities now only give the Guard flag to a relay if
7806 they are also giving it the Stable flag. This change allows us to
7807 simplify path selection for clients. It should have minimal effect
7808 in practice, since >99% of Guards already have the Stable flag.
7809 Implements ticket 18624.
7810 - Directory authorities now write their v3-status-votes file out to
7811 disk earlier in the consensus process, so we have a record of the
7812 votes even if we abort the consensus process. Resolves
7815 o Minor features (hidden service):
7816 - Stop being so strict about the payload length of "rendezvous1"
7817 cells. We used to be locked in to the "TAP" handshake length, and
7818 now we can handle better handshakes like "ntor". Resolves
7821 o Minor features (infrastructure, time):
7822 - Tor now uses the operating system's monotonic timers (where
7823 available) for internal fine-grained timing. Previously we would
7824 look at the system clock, and then attempt to compensate for the
7825 clock running backwards. Closes ticket 18908.
7826 - Tor now includes an improved timer backend, so that we can
7827 efficiently support tens or hundreds of thousands of concurrent
7828 timers, as will be needed for some of our planned anti-traffic-
7829 analysis work. This code is based on William Ahern's "timeout.c"
7830 project, which implements a "tickless hierarchical timing wheel".
7831 Closes ticket 18365.
7833 o Minor features (logging):
7834 - Provide a more useful warning message when configured with an
7835 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
7836 - When dumping unparseable router descriptors, optionally store them
7837 in separate files, named by digest, up to a configurable size
7838 limit. You can change the size limit by setting the
7839 MaxUnparseableDescSizeToLog option, and disable this feature by
7840 setting that option to 0. Closes ticket 18322.
7841 - Add a set of macros to check nonfatal assertions, for internal
7842 use. Migrating more of our checks to these should help us avoid
7843 needless crash bugs. Closes ticket 18613.
7845 o Minor features (performance):
7846 - Changer the "optimistic data" extension from "off by default" to
7847 "on by default". The default was ordinarily overridden by a
7848 consensus option, but when clients were bootstrapping for the
7849 first time, they would not have a consensus to get the option
7850 from. Changing this default When fetching a consensus for the
7851 first time, use optimistic data. This saves a round-trip during
7852 startup. Closes ticket 18815.
7854 o Minor features (relay, usability):
7855 - When the directory authorities refuse a bad relay's descriptor,
7856 encourage the relay operator to contact us. Many relay operators
7857 won't notice this line in their logs, but it's a win if even a few
7858 learn why we don't like what their relay was doing. Resolves
7861 o Minor features (testing):
7862 - Let backtrace tests work correctly under AddressSanitizer. Fixes
7863 part of bug 18934; bugfix on 0.2.5.2-alpha.
7864 - Move the test-network.sh script to chutney, and modify tor's test-
7865 network.sh to call the (newer) chutney version when available.
7866 Resolves ticket 19116. Patch by teor.
7867 - Use the lcov convention for marking lines as unreachable, so that
7868 we don't count them when we're generating test coverage data.
7869 Update our coverage tools to understand this convention. Closes
7872 o Minor bugfixes (bootstrap):
7873 - Remember the directory we fetched the consensus or previous
7874 certificates from, and use it to fetch future authority
7875 certificates. This change improves bootstrapping performance.
7876 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
7878 o Minor bugfixes (build):
7879 - The test-stem and test-network makefile targets now depend only on
7880 the tor binary that they are testing. Previously, they depended on
7881 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
7882 patch from "cypherpunks".
7884 o Minor bugfixes (circuits):
7885 - Make sure extend_info_from_router() is only called on servers.
7886 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
7888 o Minor bugfixes (compilation):
7889 - When building with Clang, use a full set of GCC warnings.
7890 (Previously, we included only a subset, because of the way we
7891 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
7893 o Minor bugfixes (directory authority):
7894 - Authorities now sort the "package" lines in their votes, for ease
7895 of debugging. (They are already sorted in consensus documents.)
7896 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
7897 - When parsing a detached signature, make sure we use the length of
7898 the digest algorithm instead of an hardcoded DIGEST256_LEN in
7899 order to avoid comparing bytes out-of-bounds with a smaller digest
7900 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
7902 o Minor bugfixes (documentation):
7903 - Document the --passphrase-fd option in the tor manpage. Fixes bug
7904 19504; bugfix on 0.2.7.3-rc.
7905 - Fix the description of the --passphrase-fd option in the
7906 tor-gencert manpage. The option is used to pass the number of a
7907 file descriptor to read the passphrase from, not to read the file
7908 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
7910 o Minor bugfixes (ephemeral hidden service):
7911 - When deleting an ephemeral hidden service, close its intro points
7912 even if they are not completely open. Fixes bug 18604; bugfix
7915 o Minor bugfixes (guard selection):
7916 - Use a single entry guard even if the NumEntryGuards consensus
7917 parameter is not provided. Fixes bug 17688; bugfix
7919 - Don't mark guards as unreachable if connection_connect() fails.
7920 That function fails for local reasons, so it shouldn't reveal
7921 anything about the status of the guard. Fixes bug 14334; bugfix
7924 o Minor bugfixes (hidden service client):
7925 - Increase the minimum number of internal circuits we preemptively
7926 build from 2 to 3, so a circuit is available when a client
7927 connects to another onion service. Fixes bug 13239; bugfix
7930 o Minor bugfixes (logging):
7931 - When logging a directory ownership mismatch, log the owning
7932 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
7934 o Minor bugfixes (memory leaks):
7935 - Fix a small, uncommon memory leak that could occur when reading a
7936 truncated ed25519 key file. Fixes bug 18956; bugfix
7939 o Minor bugfixes (testing):
7940 - Allow clients to retry HSDirs much faster in test networks. Fixes
7941 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
7942 - Disable ASAN's detection of segmentation faults while running
7943 test_bt.sh, so that we can make sure that our own backtrace
7944 generation code works. Fixes another aspect of bug 18934; bugfix
7945 on 0.2.5.2-alpha. Patch from "cypherpunks".
7946 - Fix the test-network-all target on out-of-tree builds by using the
7947 correct path to the test driver script. Fixes bug 19421; bugfix
7950 o Minor bugfixes (time):
7951 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
7952 bugfix on all released tor versions.
7953 - When computing the difference between two times in milliseconds,
7954 we now round to the nearest millisecond correctly. Previously, we
7955 could sometimes round in the wrong direction. Fixes bug 19428;
7956 bugfix on 0.2.2.2-alpha.
7958 o Minor bugfixes (user interface):
7959 - Display a more accurate number of suppressed messages in the log
7960 rate-limiter. Previously, there was a potential integer overflow
7961 in the counter. Now, if the number of messages hits a maximum, the
7962 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
7964 - Fix a typo in the passphrase prompt for the ed25519 identity key.
7965 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
7967 o Code simplification and refactoring:
7968 - Remove redundant declarations of the MIN macro. Closes
7970 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
7971 Closes ticket 18462; patch from "icanhasaccount".
7972 - Split the 600-line directory_handle_command_get function into
7973 separate functions for different URL types. Closes ticket 16698.
7976 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
7977 ticket 19153. Patch from "U+039b".
7980 - Remove support for "GET /tor/bytes.txt" DirPort request, and
7981 "GETINFO dir-usage" controller request, which were only available
7982 via a compile-time option in Tor anyway. Feature was added in
7983 0.2.2.1-alpha. Resolves ticket 19035.
7984 - There is no longer a compile-time option to disable support for
7985 TransPort. (If you don't want TransPort; just don't use it.) Patch
7986 from "U+039b". Closes ticket 19449.
7989 - Run more workqueue tests as part of "make check". These had
7990 previously been implemented, but you needed to know special
7991 command-line options to enable them.
7992 - We now have unit tests for our code to reject zlib "compression
7993 bombs". (Fortunately, the code works fine.)
7996 Changes in version 0.2.8.6 - 2016-08-02
7998 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
8000 The Tor 0.2.8 series improves client bootstrapping performance,
8001 completes the authority-side implementation of improved identity
8002 keys for relays, and includes numerous bugfixes and performance
8003 improvements throughout the program. This release continues to
8004 improve the coverage of Tor's test suite. For a full list of
8005 changes since Tor 0.2.7, see the ReleaseNotes file.
8007 Changes since 0.2.8.5-rc:
8009 o Minor features (geoip):
8010 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
8013 o Minor bugfixes (compilation):
8014 - Fix a compilation warning in the unit tests on systems where char
8015 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
8017 o Minor bugfixes (fallback directories):
8018 - Remove 1 fallback that was on the hardcoded list, then opted-out,
8019 leaving 89 of the 100 fallbacks originally introduced in Tor
8020 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
8022 o Minor bugfixes (Linux seccomp2 sandbox):
8023 - Allow more syscalls when running with "Sandbox 1" enabled:
8024 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
8025 some systems, these are required for Tor to start. Fixes bug
8026 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
8027 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
8028 so that get_interface_address6_via_udp_socket_hack() can work.
8029 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
8032 Changes in version 0.2.8.5-rc - 2016-07-07
8033 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
8034 series. If we find no new bugs or regressions here, the first stable
8035 0.2.8 release will be identical to it. It has a few small bugfixes
8036 against previous versions.
8038 o Directory authority changes:
8039 - Urras is no longer a directory authority. Closes ticket 19271.
8041 o Major bugfixes (heartbeat):
8042 - Fix a regression that would crash Tor when the periodic
8043 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
8044 0.2.8.1-alpha. Reported by "kubaku".
8046 o Minor features (build):
8047 - Tor now again builds with the recent OpenSSL 1.1 development
8048 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
8049 - When building manual pages, set the timezone to "UTC", so that the
8050 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
8051 Patch from intrigeri.
8053 o Minor bugfixes (fallback directory selection):
8054 - Avoid errors during fallback selection if there are no eligible
8055 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
8058 o Minor bugfixes (IPv6, microdescriptors):
8059 - Don't check node addresses when we only have a routerstatus. This
8060 allows IPv6-only clients to bootstrap by fetching microdescriptors
8061 from fallback directory mirrors. (The microdescriptor consensus
8062 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
8065 o Minor bugfixes (logging):
8066 - Reduce pointlessly verbose log messages when directory servers
8067 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
8068 0.2.8.1-alpha. Patch by teor.
8069 - When a fallback directory changes its fingerprint from the hard-
8070 coded fingerprint, log a less severe, more explanatory log
8071 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
8073 o Minor bugfixes (Linux seccomp2 sandboxing):
8074 - Allow statistics to be written to disk when "Sandbox 1" is
8075 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
8076 0.2.6.1-alpha respectively.
8078 o Minor bugfixes (user interface):
8079 - Remove a warning message "Service [scrubbed] not found after
8080 descriptor upload". This message appears when one uses HSPOST
8081 control command to upload a service descriptor. Since there is
8082 only a descriptor and no service, showing this message is
8083 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
8085 o Fallback directory list:
8086 - Add a comment to the generated fallback directory list that
8087 explains how to comment out unsuitable fallbacks in a way that's
8088 compatible with the stem fallback parser.
8089 - Update fallback whitelist and blacklist based on relay operator
8090 emails. Blacklist unsuitable (non-working, over-volatile)
8091 fallbacks. Resolves ticket 19071. Patch by teor.
8092 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
8093 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
8094 ticket 19071; patch by teor.
8097 Changes in version 0.2.8.4-rc - 2016-06-15
8098 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
8099 If we find no new bugs or regressions here, the first stable 0.2.8
8100 release will be identical to it. It has a few small bugfixes against
8103 o Major bugfixes (user interface):
8104 - Correctly give a warning in the cases where a relay is specified
8105 by nickname, and one such relay is found, but it is not officially
8106 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
8108 o Minor features (build):
8109 - Tor now builds once again with the recent OpenSSL 1.1 development
8110 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
8112 o Minor features (geoip):
8113 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
8116 o Minor bugfixes (compilation):
8117 - Cause the unit tests to compile correctly on mingw64 versions that
8118 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
8120 o Minor bugfixes (downloading):
8121 - Predict more correctly whether we'll be downloading over HTTP when
8122 we determine the maximum length of a URL. This should avoid a
8123 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
8127 Changes in version 0.2.8.3-alpha - 2016-05-26
8128 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
8129 the course of the 0.2.8 development cycle. It improves the behavior of
8130 directory clients, fixes several crash bugs, fixes a gap in compiler
8131 hardening, and allows the full integration test suite to run on
8134 o Major bugfixes (security, client, DNS proxy):
8135 - Stop a crash that could occur when a client running with DNSPort
8136 received a query with multiple address types, and the first
8137 address type was not supported. Found and fixed by Scott Dial.
8138 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8140 o Major bugfixes (security, compilation):
8141 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
8142 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
8143 cause a compiler warning, thereby making other checks fail, and
8144 needlessly disabling compiler-hardening support. Fixes one case of
8145 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
8147 o Major bugfixes (security, directory authorities):
8148 - Fix a crash and out-of-bounds write during authority voting, when
8149 the list of relays includes duplicate ed25519 identity keys. Fixes
8150 bug 19032; bugfix on 0.2.8.2-alpha.
8152 o Major bugfixes (client, bootstrapping):
8153 - Check if bootstrap consensus downloads are still needed when the
8154 linked connection attaches. This prevents tor making unnecessary
8155 begindir-style connections, which are the only directory
8156 connections tor clients make since the fix for 18483 was merged.
8157 - Fix some edge cases where consensus download connections may not
8158 have been closed, even though they were not needed. Related to fix
8160 - Make relays retry consensus downloads the correct number of times,
8161 rather than the more aggressive client retry count. Fixes part of
8163 - Stop downloading consensuses when we have a consensus, even if we
8164 don't have all the certificates for it yet. Fixes bug 18809;
8165 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
8167 o Major bugfixes (directory mirrors):
8168 - Decide whether to advertise begindir support in the the same way
8169 we decide whether to advertise our DirPort. Allowing these
8170 decisions to become out-of-sync led to surprising behavior like
8171 advertising begindir support when hibernation made us not
8172 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
8175 o Major bugfixes (IPv6 bridges, client):
8176 - Actually use IPv6 addresses when selecting directory addresses for
8177 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
8180 o Major bugfixes (key management):
8181 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8182 pointer to the previous (uninitialized) key value. The impact here
8183 should be limited to a difficult-to-trigger crash, if OpenSSL is
8184 running an engine that makes key generation failures possible, or
8185 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8186 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8189 o Major bugfixes (testing):
8190 - Fix a bug that would block 'make test-network-all' on systems where
8191 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
8192 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
8193 bugfix on 0.2.8.1-alpha.
8195 o Minor features (clients):
8196 - Make clients, onion services, and bridge relays always use an
8197 encrypted begindir connection for directory requests. Resolves
8198 ticket 18483. Patch by "teor".
8200 o Minor features (fallback directory mirrors):
8201 - Give each fallback the same weight for client selection; restrict
8202 fallbacks to one per operator; report fallback directory detail
8203 changes when rebuilding list; add new fallback directory mirrors
8204 to the whitelist; and many other minor simplifications and fixes.
8205 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
8206 0.2.8.1-alpha; patch by "teor".
8207 - Replace the 21 fallbacks generated in January 2016 and included in
8208 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
8209 2016. Closes task 17158; patch by "teor".
8211 o Minor features (geoip):
8212 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
8215 o Minor bugfixes (assert, portability):
8216 - Fix an assertion failure in memarea.c on systems where "long" is
8217 shorter than the size of a pointer. Fixes bug 18716; bugfix
8220 o Minor bugfixes (bootstrap):
8221 - Consistently use the consensus download schedule for authority
8222 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
8224 o Minor bugfixes (build):
8225 - Remove a pair of redundant AM_CONDITIONAL declarations from
8226 configure.ac. Fixes one final case of bug 17744; bugfix
8228 - Resolve warnings when building on systems that are concerned with
8229 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
8231 - When libscrypt.h is found, but no libscrypt library can be linked,
8232 treat libscrypt as absent. Fixes bug 19161; bugfix
8235 o Minor bugfixes (client):
8236 - Turn all TestingClientBootstrap* into non-testing torrc options.
8237 This changes simply renames them by removing "Testing" in front of
8238 them and they do not require TestingTorNetwork to be enabled
8239 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
8240 - Make directory node selection more reliable, mainly for IPv6-only
8241 clients and clients with few reachable addresses. Fixes bug 18929;
8242 bugfix on 0.2.8.1-alpha. Patch by "teor".
8244 o Minor bugfixes (controller, microdescriptors):
8245 - Make GETINFO dir/status-vote/current/consensus conform to the
8246 control specification by returning "551 Could not open cached
8247 consensus..." when not caching consensuses. Fixes bug 18920;
8248 bugfix on 0.2.2.6-alpha.
8250 o Minor bugfixes (crypto, portability):
8251 - The SHA3 and SHAKE routines now produce the correct output on Big
8252 Endian systems. No code calls either algorithm yet, so this is
8253 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
8254 - Tor now builds again with the recent OpenSSL 1.1 development
8255 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
8258 o Minor bugfixes (directories):
8259 - When fetching extrainfo documents, compare their SHA256 digests
8260 and Ed25519 signing key certificates with the routerinfo that led
8261 us to fetch them, rather than with the most recent routerinfo.
8262 Otherwise we generate many spurious warnings about mismatches.
8263 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
8265 o Minor bugfixes (logging):
8266 - When we can't generate a signing key because OfflineMasterKey is
8267 set, do not imply that we should have been able to load it. Fixes
8268 bug 18133; bugfix on 0.2.7.2-alpha.
8269 - Stop periodic_event_dispatch() from blasting twelve lines per
8270 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
8271 - When rejecting a misformed INTRODUCE2 cell, only log at
8272 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
8274 o Minor bugfixes (pluggable transports):
8275 - Avoid reporting a spurious error when we decide that we don't need
8276 to terminate a pluggable transport because it has already exited.
8277 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
8279 o Minor bugfixes (pointer arithmetic):
8280 - Fix a bug in memarea_alloc() that could have resulted in remote
8281 heap write access, if Tor had ever passed an unchecked size to
8282 memarea_alloc(). Fortunately, all the sizes we pass to
8283 memarea_alloc() are pre-checked to be less than 128 kilobytes.
8284 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
8287 o Minor bugfixes (relays):
8288 - Consider more config options when relays decide whether to
8289 regenerate their descriptor. Fixes more of bug 12538; bugfix
8291 - Resolve some edge cases where we might launch an ORPort
8292 reachability check even when DisableNetwork is set. Noticed while
8293 fixing bug 18616; bugfix on 0.2.3.9-alpha.
8295 o Minor bugfixes (statistics):
8296 - We now include consensus downloads via IPv6 in our directory-
8297 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
8299 o Minor bugfixes (testing):
8300 - Allow directories in small networks to bootstrap by skipping
8301 DirPort checks when the consensus has no exits. Fixes bug 19003;
8302 bugfix on 0.2.8.1-alpha. Patch by teor.
8303 - Fix a small memory leak that would occur when the
8304 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
8305 bugfix on 0.2.5.2-alpha.
8307 o Minor bugfixes (time handling):
8308 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
8309 field. Otherwise, our unit tests crash on Windows. Fixes bug
8310 18977; bugfix on 0.2.2.25-alpha.
8313 - Document the contents of the 'datadir/keys' subdirectory in the
8314 manual page. Closes ticket 17621.
8315 - Stop recommending use of nicknames to identify relays in our
8316 MapAddress documentation. Closes ticket 18312.
8319 Changes in version 0.2.8.2-alpha - 2016-03-28
8320 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
8321 bugs in earlier versions of Tor, including some that prevented
8322 authorities using Tor 0.2.7.x from running correctly. IPv6 and
8323 directory support should also be much improved.
8325 o New system requirements:
8326 - Tor no longer supports versions of OpenSSL with a broken
8327 implementation of counter mode. (This bug was present in OpenSSL
8328 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
8329 longer runs with, these versions.
8330 - Tor no longer attempts to support platforms where the "time_t"
8331 type is unsigned. (To the best of our knowledge, only OpenVMS does
8332 this, and Tor has never actually built on OpenVMS.) Closes
8334 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
8335 later (released in 2008 and 2009 respectively). If you are
8336 building Tor from the git repository instead of from the source
8337 distribution, and your tools are older than this, you will need to
8338 upgrade. Closes ticket 17732.
8340 o Major bugfixes (security, pointers):
8341 - Avoid a difficult-to-trigger heap corruption attack when extending
8342 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8343 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8344 Reported by Guido Vranken.
8346 o Major bugfixes (bridges, pluggable transports):
8347 - Modify the check for OR connections to private addresses. Allow
8348 bridges on private addresses, including pluggable transports that
8349 ignore the (potentially private) address in the bridge line. Fixes
8350 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
8352 o Major bugfixes (compilation):
8353 - Repair hardened builds under the clang compiler. Previously, our
8354 use of _FORTIFY_SOURCE would conflict with clang's address
8355 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
8357 o Major bugfixes (crash on shutdown):
8358 - Correctly handle detaching circuits from muxes when shutting down.
8359 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
8360 - Fix an assert-on-exit bug related to counting memory usage in
8361 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
8363 o Major bugfixes (crash on startup):
8364 - Fix a segfault during startup: If a Unix domain socket was
8365 configured as listener (such as a ControlSocket or a SocksPort
8366 "unix:" socket), and tor was started as root but not configured to
8367 switch to another user, tor would segfault while trying to string
8368 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
8371 o Major bugfixes (dns proxy mode, crash):
8372 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8373 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8375 o Major bugfixes (relays, bridge clients):
8376 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
8377 bridge clients use the address configured in the bridge line.
8378 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
8381 o Major bugfixes (voting):
8382 - Actually enable support for authorities to match routers by their
8383 Ed25519 identities. Previously, the code had been written, but
8384 some debugging code that had accidentally been left in the
8385 codebase made it stay turned off. Fixes bug 17702; bugfix
8387 - When collating votes by Ed25519 identities, authorities now
8388 include a "NoEdConsensus" flag if the ed25519 value (or lack
8389 thereof) for a server does not reflect the majority consensus.
8390 Related to bug 17668; bugfix on 0.2.7.2-alpha.
8391 - When generating a vote with keypinning disabled, never include two
8392 entries for the same ed25519 identity. This bug was causing
8393 authorities to generate votes that they could not parse when a
8394 router violated key pinning by changing its RSA identity but
8395 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
8396 18318. Bugfix on 0.2.7.2-alpha.
8398 o Minor features (security, win32):
8399 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
8400 attack. Fixes bug 18123; bugfix on all tor versions. Patch
8403 o Minor features (bug-resistance):
8404 - Make Tor survive errors involving connections without a
8405 corresponding event object. Previously we'd fail with an
8406 assertion; now we produce a log message. Related to bug 16248.
8408 o Minor features (build):
8409 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
8410 as having possible IPFW support. Closes ticket 18448. Patch from
8413 o Minor features (code hardening):
8414 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
8415 level code, to harden against accidental failures to NUL-
8416 terminate. Part of ticket 17852. Patch from jsturgix. Found
8419 o Minor features (crypto):
8420 - Validate the hard-coded Diffie-Hellman parameters and ensure that
8421 p is a safe prime, and g is a suitable generator. Closes
8424 o Minor features (geoip):
8425 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
8428 o Minor features (hidden service directory):
8429 - Streamline relay-side hsdir handling: when relays consider whether
8430 to accept an uploaded hidden service descriptor, they no longer
8431 check whether they are one of the relays in the network that is
8432 "supposed" to handle that descriptor. Implements ticket 18332.
8434 o Minor features (IPv6):
8435 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
8436 to 1, tor prefers IPv6 directory addresses.
8437 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
8438 avoids using IPv4 for client OR and directory connections.
8439 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
8440 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
8441 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
8443 o Minor features (linux seccomp2 sandbox):
8444 - Reject attempts to change our Address with "Sandbox 1" enabled.
8445 Changing Address with Sandbox turned on would never actually work,
8446 but previously it would fail in strange and confusing ways. Found
8449 o Minor features (robustness):
8450 - Exit immediately with an error message if the code attempts to use
8451 Libevent without having initialized it. This should resolve some
8452 frequently-made mistakes in our unit tests. Closes ticket 18241.
8454 o Minor features (unix domain sockets):
8455 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
8456 Unix domain sockets without checking the permissions on the parent
8457 directory. (Tor checks permissions by default because some
8458 operating systems only check permissions on the parent directory.
8459 However, some operating systems do look at permissions on the
8460 socket, and tor's default check is unneeded.) Closes ticket 18458.
8463 o Minor bugfixes (exit policies, security):
8464 - Refresh an exit relay's exit policy when interface addresses
8465 change. Previously, tor only refreshed the exit policy when the
8466 configured external address changed. Fixes bug 18208; bugfix on
8467 0.2.7.3-rc. Patch by teor.
8469 o Minor bugfixes (security, hidden services):
8470 - Prevent hidden services connecting to client-supplied rendezvous
8471 addresses that are reserved as internal or multicast. Fixes bug
8472 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
8474 o Minor bugfixes (build):
8475 - Do not link the unit tests against both the testing and non-
8476 testing versions of the static libraries. Fixes bug 18490; bugfix
8478 - Avoid spurious failures from configure files related to calling
8479 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
8480 0.2.0.1-alpha. Patch from "cypherpunks".
8481 - Silence spurious clang-scan warnings in the ed25519_donna code by
8482 explicitly initializing some objects. Fixes bug 18384; bugfix on
8483 0.2.7.2-alpha. Patch by teor.
8485 o Minor bugfixes (client, bootstrap):
8486 - Count receipt of new microdescriptors as progress towards
8487 bootstrapping. Previously, with EntryNodes set, Tor might not
8488 successfully repopulate the guard set on bootstrapping. Fixes bug
8489 16825; bugfix on 0.2.3.1-alpha.
8491 o Minor bugfixes (code correctness):
8492 - Update to the latest version of Trunnel, which tries harder to
8493 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
8494 by clang address sanitizer. Fixes bug 18373; bugfix
8497 o Minor bugfixes (configuration):
8498 - Fix a tiny memory leak when parsing a port configuration ending in
8499 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
8501 o Minor bugfixes (containers):
8502 - If we somehow attempt to construct a heap with more than
8503 1073741822 elements, avoid an integer overflow when maintaining
8504 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
8506 o Minor bugfixes (correctness):
8507 - Fix a bad memory handling bug that would occur if we had queued a
8508 cell on a channel's incoming queue. Fortunately, we can't actually
8509 queue a cell like that as our code is constructed today, but it's
8510 best to avoid this kind of error, even if there isn't any code
8511 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
8513 o Minor bugfixes (directory):
8514 - When generating a URL for a directory server on an IPv6 address,
8515 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
8516 on 0.2.3.9-alpha. Patch from Malek.
8518 o Minor bugfixes (fallback directory mirrors):
8519 - When requesting extrainfo descriptors from a trusted directory
8520 server, check whether it is an authority or a fallback directory
8521 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
8522 0.2.4.7-alpha. Reported by atagar, patch by teor.
8524 o Minor bugfixes (hidden service, client):
8525 - Handle the case where the user makes several fast consecutive
8526 requests to the same .onion address. Previously, the first six
8527 requests would each trigger a descriptor fetch, each picking a
8528 directory (there are 6 overall) and the seventh one would fail
8529 because no directories were left, thereby triggering a close on
8530 all current directory connections asking for the hidden service.
8531 The solution here is to not close the connections if we have
8532 pending directory fetches. Fixes bug 15937; bugfix
8535 o Minor bugfixes (hidden service, control port):
8536 - Add the onion address to the HS_DESC event for the UPLOADED action
8537 both on success or failure. It was previously hardcoded with
8538 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
8540 o Minor bugfixes (hidden service, directory):
8541 - Bridges now refuse "rendezvous2" (hidden service descriptor)
8542 publish attempts. Suggested by ticket 18332.
8544 o Minor bugfixes (linux seccomp2 sandbox):
8545 - Allow the setrlimit syscall, and the prlimit and prlimit64
8546 syscalls, which some libc implementations use under the hood.
8547 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
8548 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
8549 enabled and no DNS resolvers configured. This should help TAILS
8550 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
8551 - Fix the sandbox's interoperability with unix domain sockets under
8552 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
8554 o Minor bugfixes (logging):
8555 - When logging information about an unparsable networkstatus vote or
8556 consensus, do not say "vote" when we mean consensus. Fixes bug
8557 18368; bugfix on 0.2.0.8-alpha.
8558 - Scrub service name in "unrecognized service ID" log messages.
8559 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
8560 - Downgrade logs and backtraces about IP versions to info-level.
8561 Only log backtraces once each time tor runs. Assists in diagnosing
8562 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
8563 Christian, patch by teor.
8565 o Minor bugfixes (memory safety):
8566 - Avoid freeing an uninitialized pointer when opening a socket fails
8567 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
8568 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
8570 - Correctly duplicate addresses in get_interface_address6_list().
8571 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
8572 patch by "cypherpunks".
8573 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
8575 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
8576 18672; bugfix on 0.2.5.1-alpha.
8578 o Minor bugfixes (private directory):
8579 - Prevent a race condition when creating private directories. Fixes
8580 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
8581 Patch from jsturgix. Found with Flawfinder.
8583 o Minor bugfixes (test networks, IPv6):
8584 - Allow internal IPv6 addresses in descriptors in test networks.
8585 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
8588 o Minor bugfixes (testing):
8589 - We no longer disable assertions in the unit tests when coverage is
8590 enabled. Instead, we require you to say --disable-asserts-in-tests
8591 to the configure script if you need assertions disabled in the
8592 unit tests (for example, if you want to perform branch coverage).
8593 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
8595 o Minor bugfixes (time parsing):
8596 - Avoid overflow in tor_timegm when parsing dates in and after 2038
8597 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
8598 0.0.2pre14. Patch by teor.
8600 o Minor bugfixes (tor-gencert):
8601 - Correctly handle the case where an authority operator enters a
8602 passphrase but sends an EOF before sending a newline. Fixes bug
8603 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
8605 o Code simplification and refactoring:
8606 - Quote all the string interpolations in configure.ac -- even those
8607 which we are pretty sure can't contain spaces. Closes ticket
8608 17744. Patch from zerosion.
8609 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
8610 inplace, so there's no need to have a separate implementation for
8611 the non-inplace code. Closes ticket 18258. Patch from Malek.
8612 - Simplify return types for some crypto functions that can't
8613 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
8616 - Change build messages to refer to "Fedora" instead of "Fedora
8617 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
8618 Patches from "icanhasaccount" and "cypherpunks".
8621 - We no longer maintain an internal freelist in memarea.c.
8622 Allocators should be good enough to make this code unnecessary,
8623 and it's doubtful that it ever had any performance benefit.
8626 - Fix several warnings from clang's address sanitizer produced in
8628 - Treat backtrace test failures as expected on FreeBSD until we
8629 solve bug 17808. Closes ticket 18204.
8632 Changes in version 0.2.8.1-alpha - 2016-02-04
8633 Tor 0.2.8.1-alpha is the first alpha release in its series. It
8634 includes numerous small features and bugfixes against previous Tor
8635 versions, and numerous small infrastructure improvements. The most
8636 notable features are a set of improvements to the directory subsystem.
8638 o Major features (security, Linux):
8639 - When Tor starts as root on Linux and is told to switch user ID, it
8640 can now retain the capability to bind to low ports. By default,
8641 Tor will do this only when it's switching user ID and some low
8642 ports have been configured. You can change this behavior with the
8643 new option KeepBindCapabilities. Closes ticket 8195.
8645 o Major features (directory system):
8646 - When bootstrapping multiple consensus downloads at a time, use the
8647 first one that starts downloading, and close the rest. This
8648 reduces failures when authorities or fallback directories are slow
8649 or down. Together with the code for feature 15775, this feature
8650 should reduces failures due to fallback churn. Implements ticket
8651 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
8652 "mikeperry" and "teor".
8653 - Include a trial list of 21 default fallback directories, generated
8654 in January 2016, based on an opt-in survey of suitable relays.
8655 Doing this should make clients bootstrap more quickly and reliably,
8656 and reduce the load on the directory authorities. Closes ticket
8657 15775. Patch by "teor".
8658 Candidates identified using an OnionOO script by "weasel", "teor",
8659 "gsathya", and "karsten".
8660 - Previously only relays that explicitly opened a directory port
8661 (DirPort) accepted directory requests from clients. Now all
8662 relays, with and without a DirPort, accept and serve tunneled
8663 directory requests that they receive through their ORPort. You can
8664 disable this behavior using the new DirCache option. Closes
8667 o Major key updates:
8668 - Update the V3 identity key for the dannenberg directory authority:
8669 it was changed on 18 November 2015. Closes task 17906. Patch
8672 o Minor features (security, clock):
8673 - Warn when the system clock appears to move back in time (when the
8674 state file was last written in the future). Tor doesn't know that
8675 consensuses have expired if the clock is in the past. Patch by
8676 "teor". Implements ticket 17188.
8678 o Minor features (security, exit policies):
8679 - ExitPolicyRejectPrivate now rejects more private addresses by
8680 default. Specifically, it now rejects the relay's outbound bind
8681 addresses (if configured), and the relay's configured port
8682 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
8683 0.2.0.11-alpha. Patch by "teor".
8685 o Minor features (security, memory erasure):
8686 - Set the unused entries in a smartlist to NULL. This helped catch
8687 a (harmless) bug, and shouldn't affect performance too much.
8688 Implements ticket 17026.
8689 - Use SecureMemoryWipe() function to securely clean memory on
8690 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
8691 Implements feature 17986.
8692 - Use explicit_bzero or memset_s when present. Previously, we'd use
8693 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
8694 from <logan@hackers.mu> and <selven@hackers.mu>.
8695 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8696 zero size. Check size argument to memwipe() for underflow. Fixes
8697 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8700 o Minor features (security, RNG):
8701 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
8702 positively are not allowed to fail. Previously we depended on
8703 internal details of OpenSSL's behavior. Closes ticket 17686.
8704 - Never use the system entropy output directly for anything besides
8705 seeding the PRNG. When we want to generate important keys, instead
8706 of using system entropy directly, we now hash it with the PRNG
8707 stream. This may help resist certain attacks based on broken OS
8708 entropy implementations. Closes part of ticket 17694.
8709 - Use modern system calls (like getentropy() or getrandom()) to
8710 generate strong entropy on platforms that have them. Closes
8713 o Minor features (accounting):
8714 - Added two modes to the AccountingRule option: One for limiting
8715 only the number of bytes sent ("AccountingRule out"), and one for
8716 limiting only the number of bytes received ("AccountingRule in").
8717 Closes ticket 15989; patch from "unixninja92".
8719 o Minor features (build):
8720 - Since our build process now uses "make distcheck", we no longer
8721 force "make dist" to depend on "make check". Closes ticket 17893;
8722 patch from "cypherpunks."
8723 - Tor now builds successfully with the recent OpenSSL 1.1
8724 development branch, and with the latest LibreSSL. Closes tickets
8725 17549, 17921, and 17984.
8727 o Minor features (controller):
8728 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
8729 tickets 16774 and 17817. Patch by George Tankersley.
8730 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
8731 service descriptor from a service's local hidden service
8732 descriptor cache. Closes ticket 14846.
8733 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
8734 controllers can examine the the reject rules added by
8735 ExitPolicyRejectPrivate. This makes it easier for stem to display
8738 o Minor features (crypto):
8739 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
8741 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
8742 - When allocating a digest state object, allocate no more space than
8743 we actually need. Previously, we would allocate as much space as
8744 the state for the largest algorithm would need. This change saves
8745 up to 672 bytes per circuit. Closes ticket 17796.
8746 - Improve performance when hashing non-multiple of 8 sized buffers,
8747 based on Andrew Moon's public domain SipHash-2-4 implementation.
8748 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
8750 o Minor features (directory downloads):
8751 - Wait for busy authorities and fallback directories to become non-
8752 busy when bootstrapping. (A similar change was made in 6c443e987d
8753 for directory caches chosen from the consensus.) Closes ticket
8754 17864; patch by "teor".
8755 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
8756 directory mirrors. The default is 1; set it to 0 to disable
8757 fallbacks. Implements ticket 17576. Patch by "teor".
8759 o Minor features (geoip):
8760 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
8763 o Minor features (IPv6):
8764 - Add an argument 'ipv6=address:orport' to the DirAuthority and
8765 FallbackDir torrc options, to specify an IPv6 address for an
8766 authority or fallback directory. Add hard-coded ipv6 addresses for
8767 directory authorities that have them. Closes ticket 17327; patch
8768 from Nick Mathewson and "teor".
8769 - Add address policy assume_action support for IPv6 addresses.
8770 - Limit IPv6 mask bits to 128.
8771 - Warn when comparing against an AF_UNSPEC address in a policy, it's
8772 almost always a bug. Closes ticket 17863; patch by "teor".
8773 - Allow users to configure directory authorities and fallback
8774 directory servers with IPv6 addresses and ORPorts. Resolves
8776 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
8777 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
8778 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
8779 17638; bugfix on 0.0.2pre8. Patch by "teor".
8781 o Minor features (logging):
8782 - When logging to syslog, allow a tag to be added to the syslog
8783 identity (the string prepended to every log message). The tag can
8784 be configured with SyslogIdentityTag and defaults to none. Setting
8785 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
8788 o Minor features (portability):
8789 - Use timingsafe_memcmp() where available. Closes ticket 17944;
8790 patch from <logan@hackers.mu>.
8792 o Minor features (relay, address discovery):
8793 - Add a family argument to get_interface_addresses_raw() and
8794 subfunctions to make network interface address interogation more
8795 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
8796 types of interfaces from the operating system. Resolves
8798 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
8799 fails to enumerate interface addresses using the platform-specific
8800 API, have it rely on the UDP socket fallback technique to try and
8801 find out what IP addresses (both IPv4 and IPv6) our machine has.
8802 Resolves ticket 17951.
8804 o Minor features (replay cache):
8805 - The replay cache now uses SHA256 instead of SHA1. Implements
8806 feature 8961. Patch by "teor", issue reported by "rransom".
8808 o Minor features (unix file permissions):
8809 - Defer creation of Unix sockets until after setuid. This avoids
8810 needing CAP_CHOWN and CAP_FOWNER when using systemd's
8811 CapabilityBoundingSet, or chown and fowner when using SELinux.
8812 Implements part of ticket 17562. Patch from Jamie Nguyen.
8813 - If any directory created by Tor is marked as group readable, the
8814 filesystem group is allowed to be either the default GID or the
8815 root user. Allowing root to read the DataDirectory prevents the
8816 need for CAP_READ_SEARCH when using systemd's
8817 CapabilityBoundingSet, or dac_read_search when using SELinux.
8818 Implements part of ticket 17562. Patch from Jamie Nguyen.
8819 - Introduce a new DataDirectoryGroupReadable option. If it is set to
8820 1, the DataDirectory will be made readable by the default GID.
8821 Implements part of ticket 17562. Patch from Jamie Nguyen.
8823 o Minor bugfixes (accounting):
8824 - The max bandwidth when using 'AccountRule sum' is now correctly
8825 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
8828 o Minor bugfixes (code correctness):
8829 - When closing an entry connection, generate a warning if we should
8830 have sent an end cell for it but we haven't. Fixes bug 17876;
8831 bugfix on 0.2.3.2-alpha.
8832 - Assert that allocated memory held by the reputation code is freed
8833 according to its internal counters. Fixes bug 17753; bugfix
8835 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
8838 o Minor bugfixes (compilation):
8839 - Mark all object files that include micro-revision.i as depending
8840 on it, so as to make parallel builds more reliable. Fixes bug
8841 17826; bugfix on 0.2.5.1-alpha.
8842 - Don't try to use the pthread_condattr_setclock() function unless
8843 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
8844 17819; bugfix on 0.2.6.3-alpha.
8845 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
8847 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
8848 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
8849 - Fix search for libevent libraries on OpenBSD (and other systems
8850 that install libevent 1 and libevent 2 in parallel). Fixes bug
8851 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
8852 - Isolate environment variables meant for tests from the rest of the
8853 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
8854 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
8856 - Remove config.log only from make distclean, not from make clean.
8857 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
8859 o Minor bugfixes (crypto):
8860 - Check the return value of HMAC() and assert on failure. Fixes bug
8861 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
8863 o Minor bugfixes (fallback directories):
8864 - Mark fallbacks as "too busy" when they return a 503 response,
8865 rather than just marking authorities. Fixes bug 17572; bugfix on
8866 0.2.4.7-alpha. Patch by "teor".
8868 o Minor bugfixes (IPv6):
8869 - Update the limits in max_dl_per_request for IPv6 address length.
8870 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
8872 o Minor bugfixes (linux seccomp2 sandbox):
8873 - Fix a crash when using offline master ed25519 keys with the Linux
8874 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
8876 o Minor bugfixes (logging):
8877 - In log messages that include a function name, use __FUNCTION__
8878 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
8879 with clang __PRETTY_FUNCTION__ has extra information we don't
8880 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
8882 - Remove needless quotes from a log message about unparseable
8883 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
8885 o Minor bugfixes (portability):
8886 - Remove an #endif from configure.ac so that we correctly detect the
8887 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
8890 o Minor bugfixes (relays):
8891 - Check that both the ORPort and DirPort (if present) are reachable
8892 before publishing a relay descriptor. Otherwise, relays publish a
8893 descriptor with DirPort 0 when the DirPort reachability test takes
8894 longer than the ORPort reachability test. Fixes bug 18050; bugfix
8895 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
8897 o Minor bugfixes (relays, hidden services):
8898 - Refuse connection requests to private OR addresses unless
8899 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
8900 then refuse to send any cells to a private address. Fixes bugs
8901 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
8903 o Minor bugfixes (safe logging):
8904 - When logging a malformed hostname received through socks4, scrub
8905 it if SafeLogging says we should. Fixes bug 17419; bugfix
8908 o Minor bugfixes (statistics code):
8909 - Consistently check for overflow in round_*_to_next_multiple_of
8910 functions, and add unit tests with additional and maximal values.
8911 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
8912 - Handle edge cases in the laplace functions: avoid division by
8913 zero, avoid taking the log of zero, and silence clang type
8914 conversion warnings using round and trunc. Add unit tests for edge
8915 cases with maximal values. Fixes part of bug 13192; bugfix
8918 o Minor bugfixes (testing):
8919 - The test for log_heartbeat was incorrectly failing in timezones
8920 with non-integer offsets. Instead of comparing the end of the time
8921 string against a constant, compare it to the output of
8922 format_local_iso_time when given the correct input. Fixes bug
8923 18039; bugfix on 0.2.5.4-alpha.
8924 - Make unit tests pass on IPv6-only systems, and systems without
8925 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
8926 bugfix on 0.2.7.3-rc. Patch by "teor".
8927 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
8929 - Check the full results of SHA256 and SHA512 digests in the unit
8930 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
8932 o Code simplification and refactoring:
8933 - Move logging of redundant policy entries in
8934 policies_parse_exit_policy_internal into its own function. Closes
8935 ticket 17608; patch from "juce".
8936 - Extract the more complicated parts of circuit_mark_for_close()
8937 into a new function that we run periodically before circuits are
8938 freed. This change removes more than half of the functions
8939 currently in the "blob". Closes ticket 17218.
8940 - Clean up a little duplicated code in
8941 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
8943 - Decouple the list of streams waiting to be attached to circuits
8944 from the overall connection list. This change makes it possible to
8945 attach streams quickly while simplifying Tor's callgraph and
8946 avoiding O(N) scans of the entire connection list. Closes
8948 - When a direct directory request fails immediately on launch,
8949 instead of relaunching that request from inside the code that
8950 launches it, instead mark the connection for teardown. This change
8951 simplifies Tor's callback and prevents the directory-request
8952 launching code from invoking itself recursively. Closes
8954 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
8955 use them. Closes ticket 17926.
8958 - Add a description of the correct use of the '--keygen' command-
8959 line option. Closes ticket 17583; based on text by 's7r'.
8960 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
8961 - Explain actual minima for BandwidthRate. Closes ticket 16382.
8962 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
8963 - Mention torspec URL in the manpage and point the reader to it
8964 whenever we mention a document that belongs in torspce. Fixes
8968 - Remove client-side support for connecting to Tor relays running
8969 versions of Tor before 0.2.3.6-alpha. These relays didn't support
8970 the v3 TLS handshake protocol, and are no longer allowed on the
8971 Tor network. Implements the client side of ticket 11150. Based on
8972 patches by Tom van der Woerdt.
8975 - Add unit tests to check for common RNG failure modes, such as
8976 returning all zeroes, identical values, or incrementing values
8977 (OpenSSL's rand_predictable feature). Patch by "teor".
8978 - Log more information when the backtrace tests fail. Closes ticket
8979 17892. Patch from "cypherpunks."
8980 - Always test both ed25519 backends, so that we can be sure that our
8981 batch-open replacement code works. Part of ticket 16794.
8982 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
8983 portion of ticket 16831.
8984 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
8985 util_format.c, directory.c, and options_validate.c. Closes tickets
8986 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
8988 - Unit tests for directory_handle_command_get. Closes ticket 17004.
8989 Patch from Reinaldo de Souza Jr.
8992 Changes in version 0.2.7.6 - 2015-12-10
8993 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
8994 well as a minor bug in hidden service reliability.
8996 o Major bugfixes (guard selection):
8997 - Actually look at the Guard flag when selecting a new directory
8998 guard. When we implemented the directory guard design, we
8999 accidentally started treating all relays as if they have the Guard
9000 flag during guard selection, leading to weaker anonymity and worse
9001 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9004 o Minor features (geoip):
9005 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
9008 o Minor bugfixes (compilation):
9009 - When checking for net/pfvar.h, include netinet/in.h if possible.
9010 This fixes transparent proxy detection on OpenBSD. Fixes bug
9011 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
9012 - Fix a compilation warning with Clang 3.6: Do not check the
9013 presence of an address which can never be NULL. Fixes bug 17781.
9015 o Minor bugfixes (correctness):
9016 - When displaying an IPv6 exit policy, include the mask bits
9017 correctly even when the number is greater than 31. Fixes bug
9018 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
9019 - The wrong list was used when looking up expired intro points in a
9020 rend service object, causing what we think could be reachability
9021 issues for hidden services, and triggering a BUG log. Fixes bug
9022 16702; bugfix on 0.2.7.2-alpha.
9023 - Fix undefined behavior in the tor_cert_checksig function. Fixes
9024 bug 17722; bugfix on 0.2.7.2-alpha.
9027 Changes in version 0.2.7.5 - 2015-11-20
9028 The Tor 0.2.7 release series is dedicated to the memory of Tor user
9029 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
9030 tirelessly to advocate human rights regardless of national borders,
9031 and oppose the encroachments of mass surveillance. He opposed national
9032 exceptionalism, he brought clarity to legal and policy debates, he
9033 understood and predicted the impact of mass surveillance on the world,
9034 and he laid the groundwork for resisting it. While serving on the Tor
9035 Project's board of directors, he brought us his uncompromising focus
9036 on technical excellence in the service of humankind. Caspar was an
9037 inimitable force for good and a wonderful friend. He was kind,
9038 humorous, generous, gallant, and believed we should protect one
9039 another without exception. We honor him here for his ideals, his
9040 efforts, and his accomplishments. Please honor his memory with works
9041 that would make him proud.
9043 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
9045 The 0.2.7 series adds a more secure identity key type for relays,
9046 improves cryptography performance, resolves several longstanding
9047 hidden-service performance issues, improves controller support for
9048 hidden services, and includes small bugfixes and performance
9049 improvements throughout the program. This release series also includes
9050 more tests than before, and significant simplifications to which parts
9051 of Tor invoke which others.
9053 (This release contains no code changes since 0.2.7.4-rc.)
9056 Changes in version 0.2.7.4-rc - 2015-10-21
9057 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
9058 fixes some important memory leaks, and a scary-looking (but mostly
9059 harmless in practice) invalid-read bug. It also has a few small
9060 bugfixes, notably fixes for compilation and portability on different
9061 platforms. If no further significant bounds are found, the next
9062 release will the the official stable release.
9064 o Major bugfixes (security, correctness):
9065 - Fix an error that could cause us to read 4 bytes before the
9066 beginning of an openssl string. This bug could be used to cause
9067 Tor to crash on systems with unusual malloc implementations, or
9068 systems with unusual hardening installed. Fixes bug 17404; bugfix
9071 o Major bugfixes (correctness):
9072 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
9073 bug 17401; bugfix on 0.2.7.3-rc.
9075 o Major bugfixes (memory leaks):
9076 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
9077 17398; bugfix on 0.2.6.1-alpha.
9078 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
9079 17402; bugfix on 0.2.7.3-rc.
9080 - Fix a memory leak when reading an expired signing key from disk.
9081 Fixes bug 17403; bugfix on 0.2.7.2-rc.
9083 o Minor features (geoIP):
9084 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
9087 o Minor bugfixes (compilation):
9088 - Repair compilation with the most recent (unreleased, alpha)
9089 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
9090 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
9091 17251; bugfix on 0.2.7.2-alpha.
9092 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
9093 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
9095 o Minor bugfixes (portability):
9096 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
9097 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
9100 o Minor bugfixes (sandbox):
9101 - Add the "hidserv-stats" filename to our sandbox filter for the
9102 HiddenServiceStatistics option to work properly. Fixes bug 17354;
9103 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
9105 o Minor bugfixes (testing):
9106 - Add unit tests for get_interface_address* failure cases. Fixes bug
9107 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
9108 - Fix breakage when running 'make check' with BSD make. Fixes bug
9109 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
9110 - Make the get_ifaddrs_* unit tests more tolerant of different
9111 network configurations. (Don't assume every test box has an IPv4
9112 address, and don't assume every test box has a non-localhost
9113 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
9114 - Skip backtrace tests when backtrace support is not compiled in.
9115 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
9119 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
9120 - Note that HiddenServicePorts can take a unix domain socket. Closes
9124 Changes in version 0.2.7.3-rc - 2015-09-25
9125 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
9126 contains numerous usability fixes for Ed25519 keys, safeguards against
9127 several misconfiguration problems, significant simplifications to
9128 Tor's callgraph, and numerous bugfixes and small features.
9130 This is the most tested release of Tor to date. The unit tests cover
9131 39.40% of the code, and the integration tests (accessible with "make
9132 test-full-online", requiring stem and chutney and a network
9133 connection) raise the coverage to 64.49%.
9135 o Major features (security, hidden services):
9136 - Hidden services, if using the EntryNodes option, are required to
9137 use more than one EntryNode, in order to avoid a guard discovery
9138 attack. (This would only affect people who had configured hidden
9139 services and manually specified the EntryNodes option with a
9140 single entry-node. The impact was that it would be easy to
9141 remotely identify the guard node used by such a hidden service.
9142 See ticket for more information.) Fixes ticket 14917.
9144 o Major features (Ed25519 keys, keypinning):
9145 - The key-pinning option on directory authorities is now advisory-
9146 only by default. In a future version, or when the AuthDirPinKeys
9147 option is set, pins are enforced again. Disabling key-pinning
9148 seemed like a good idea so that we can survive the fallout of any
9149 usability problems associated with Ed25519 keys. Closes
9152 o Major features (Ed25519 performance):
9153 - Improve the speed of Ed25519 operations and Curve25519 keypair
9154 generation when built targeting 32 bit x86 platforms with SSE2
9155 available. Implements ticket 16535.
9156 - Improve the runtime speed of Ed25519 signature verification by
9157 using Ed25519-donna's batch verification support. Implements
9160 o Major features (performance testing):
9161 - The test-network.sh script now supports performance testing.
9162 Requires corresponding chutney performance testing changes. Patch
9163 by "teor". Closes ticket 14175.
9165 o Major features (relay, Ed25519):
9166 - Significant usability improvements for Ed25519 key management. Log
9167 messages are better, and the code can recover from far more
9168 failure conditions. Thanks to "s7r" for reporting and diagnosing
9170 - Add a new OfflineMasterKey option to tell Tor never to try loading
9171 or generating a secret Ed25519 identity key. You can use this in
9172 combination with tor --keygen to manage offline and/or encrypted
9173 Ed25519 keys. Implements ticket 16944.
9174 - Add a --newpass option to allow changing or removing the
9175 passphrase of an encrypted key with tor --keygen. Implements part
9177 - On receiving a HUP signal, check to see whether the Ed25519
9178 signing key has changed, and reload it if so. Closes ticket 16790.
9180 o Major bugfixes (relay, Ed25519):
9181 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
9182 0.2.7.2-alpha. Reported by "s7r".
9183 - Improve handling of expired signing keys with offline master keys.
9184 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
9186 o Minor features (client-side privacy):
9187 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
9188 lifespan when IsolateSOCKSAuth and streams with SOCKS
9189 authentication are attached to the circuit. This allows
9190 applications like TorBrowser to manage circuit lifetime on their
9191 own. Implements feature 15482.
9192 - When logging malformed hostnames from SOCKS5 requests, respect
9193 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
9195 o Minor features (compilation):
9196 - Give a warning as early as possible when trying to build with an
9197 unsupported OpenSSL version. Closes ticket 16901.
9198 - Fail during configure if we're trying to build against an OpenSSL
9199 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
9200 which started requiring ECC.
9202 o Minor features (geoip):
9203 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
9206 o Minor features (hidden services):
9207 - Relays need to have the Fast flag to get the HSDir flag. As this
9208 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
9209 drop. This change should make some attacks against the hidden
9210 service directory system harder. Fixes ticket 15963.
9211 - Turn on hidden service statistics collection by setting the torrc
9212 option HiddenServiceStatistics to "1" by default. (This keeps
9213 track only of the fraction of traffic used by hidden services, and
9214 the total number of hidden services in existence.) Closes
9216 - Client now uses an introduction point failure cache to know when
9217 to fetch or keep a descriptor in their cache. Previously, failures
9218 were recorded implicitly, but not explicitly remembered. Closes
9221 o Minor features (testing, authorities, documentation):
9222 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
9223 explicitly manage consensus flags in testing networks. Patch by
9224 "robgjansen", modified by "teor". Implements part of ticket 14882.
9226 o Minor bugfixes (security, exit policies):
9227 - ExitPolicyRejectPrivate now also rejects the relay's published
9228 IPv6 address (if any), and any publicly routable IPv4 or IPv6
9229 addresses on any local interfaces. ticket 17027. Patch by "teor".
9230 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
9232 o Minor bug fixes (torrc exit policies):
9233 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
9234 produce IPv6 wildcard addresses. Previously they would produce
9235 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
9236 of bug 16069; bugfix on 0.2.4.7-alpha.
9237 - When parsing torrc ExitPolicies, we now warn for a number of cases
9238 where the user's intent is likely to differ from Tor's actual
9239 behavior. These include: using an IPv4 address with an accept6 or
9240 reject6 line; using "private" on an accept6 or reject6 line; and
9241 including any ExitPolicy lines after accept *:* or reject *:*.
9242 Related to ticket 16069.
9243 - When parsing torrc ExitPolicies, we now issue an info-level
9244 message when expanding an "accept/reject *" line to include both
9245 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
9246 - In each instance above, usage advice is provided to avoid the
9247 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
9248 16069; bugfix on 0.2.4.7-alpha.
9250 o Minor bugfixes (authority):
9251 - Don't assign "HSDir" to a router if it isn't Valid and Running.
9252 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
9253 - Downgrade log messages about Ed25519 key issues if they are in old
9254 cached router descriptors. Fixes part of bug 16286; bugfix
9256 - When we find an Ed25519 key issue in a cached descriptor, stop
9257 saying the descriptor was just "uploaded". Fixes another part of
9258 bug 16286; bugfix on 0.2.7.2-alpha.
9260 o Minor bugfixes (control port):
9261 - Repair a warning and a spurious result when getting the maximum
9262 number of file descriptors from the controller. Fixes bug 16697;
9263 bugfix on 0.2.7.2-alpha.
9265 o Minor bugfixes (correctness):
9266 - When calling channel_free_list(), avoid calling smartlist_remove()
9267 while inside a FOREACH loop. This partially reverts commit
9268 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
9269 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
9271 o Minor bugfixes (documentation):
9272 - Advise users on how to configure separate IPv4 and IPv6 exit
9273 policies in the manpage and sample torrcs. Related to ticket 16069.
9274 - Fix the usage message of tor-resolve(1) so that it no longer lists
9275 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
9276 - Fix an error in the manual page and comments for
9277 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
9278 required "ORPort connectivity". While this is true, it is in no
9279 way unique to the HSDir flag. Of all the flags, only HSDirs need a
9280 DirPort configured in order for the authorities to assign that
9281 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
9284 o Minor bugfixes (Ed25519):
9285 - Fix a memory leak when reading router descriptors with expired
9286 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
9288 o Minor bugfixes (linux seccomp2 sandbox):
9289 - Allow bridge authorities to run correctly under the seccomp2
9290 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
9291 - Allow routers with ed25519 keys to run correctly under the
9292 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
9294 o Minor bugfixes (open file limit):
9295 - Fix set_max_file_descriptors() to set by default the max open file
9296 limit to the current limit when setrlimit() fails. Fixes bug
9297 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
9299 o Minor bugfixes (portability):
9300 - Try harder to normalize the exit status of the Tor process to the
9301 standard-provided range. Fixes bug 16975; bugfix on every version
9303 - Check correctly for Windows socket errors in the workqueue
9304 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
9305 - Fix the behavior of crypto_rand_time_range() when told to consider
9306 times before 1970. (These times were possible when running in a
9307 simulated network environment where time()'s output starts at
9308 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
9309 - Restore correct operation of TLS client-cipher detection on
9310 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
9312 o Minor bugfixes (relay):
9313 - Ensure that worker threads actually exit when a fatal error or
9314 shutdown is indicated. This fix doesn't currently affect the
9315 behavior of Tor, because Tor workers never indicates fatal error
9316 or shutdown except in the unit tests. Fixes bug 16868; bugfix
9318 - Unblock threads before releasing the work queue mutex to ensure
9319 predictable scheduling behavior. Fixes bug 16644; bugfix
9322 o Code simplification and refactoring:
9323 - Change the function that's called when we need to retry all
9324 downloads so that it only reschedules the downloads to happen
9325 immediately, rather than launching them all at once itself. This
9326 further simplifies Tor's callgraph.
9327 - Move some format-parsing functions out of crypto.c and
9328 crypto_curve25519.c into crypto_format.c and/or util_format.c.
9329 - Move the client-only parts of init_keys() into a separate
9330 function. Closes ticket 16763.
9331 - Simplify the microdesc_free() implementation so that it no longer
9332 appears (to code analysis tools) to potentially invoke a huge
9333 suite of other microdesc functions.
9334 - Simply the control graph further by deferring the inner body of
9335 directory_all_unreachable() into a callback. Closes ticket 16762.
9336 - Treat the loss of an owning controller as equivalent to a SIGTERM
9337 signal. This removes a tiny amount of duplicated code, and
9338 simplifies our callgraph. Closes ticket 16788.
9339 - When generating an event to send to the controller, we no longer
9340 put the event over the network immediately. Instead, we queue
9341 these events, and use a Libevent callback to deliver them. This
9342 change simplifies Tor's callgraph by reducing the number of
9343 functions from which all other Tor functions are reachable. Closes
9345 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
9346 that try to scan or compile every file on Unix won't decide that
9348 - Remove the unused "nulterminate" argument from buf_pullup().
9351 - Recommend a 40 GB example AccountingMax in torrc.sample rather
9352 than a 4 GB max. Closes ticket 16742.
9353 - Include the TUNING document in our source tarball. It is referred
9354 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
9358 - The internal pure-C tor-fw-helper tool is now removed from the Tor
9359 distribution, in favor of the pure-Go clone available from
9360 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
9361 used by the C tor-fw-helper are not, in our opinion, very
9362 confidence- inspiring in their secure-programming techniques.
9363 Closes ticket 13338.
9364 - Remove the code that would try to aggressively flush controller
9365 connections while writing to them. This code was introduced in
9366 0.1.2.7-alpha, in order to keep output buffers from exceeding
9367 their limits. But there is no longer a maximum output buffer size,
9368 and flushing data in this way caused some undesirable recursions
9369 in our call graph. Closes ticket 16480.
9372 - Make "bridges+hs" the default test network. This tests almost all
9373 tor functionality during make test-network, while allowing tests
9374 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
9375 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
9376 (chutney). Patches by "teor".
9377 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
9378 by-side in the same parent directory. Closes ticket 16903. Patch
9380 - Use environment variables rather than autoconf substitutions to
9381 send variables from the build system to the test scripts. This
9382 change should be easier to maintain, and cause 'make distcheck' to
9383 work better than before. Fixes bug 17148.
9384 - Add a new set of callgraph analysis scripts that use clang to
9385 produce a list of which Tor functions are reachable from which
9386 other Tor functions. We're planning to use these to help simplify
9387 our code structure by identifying illogical dependencies.
9388 - Add new 'test-full' and 'test-full-online' targets to run all
9389 tests, including integration tests with stem and chutney.
9390 - Make the test-workqueue test work on Windows by initializing the
9391 network before we begin.
9392 - New make target (make test-network-all) to run multiple applicable
9393 chutney test cases. Patch from Teor; closes 16953.
9394 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
9395 functions in dns.c. Implements a portion of ticket 16831.
9396 - When building Tor with testing coverage enabled, run Chutney tests
9397 (if any) using the 'tor-cov' coverage binary.
9398 - When running test-network or test-stem, check for the absence of
9399 stem/chutney before doing any build operations.
9402 Changes in version 0.2.7.2-alpha - 2015-07-27
9403 This, the second alpha in the Tor 0.2.7 series, has a number of new
9404 features, including a way to manually pick the number of introduction
9405 points for hidden services, and the much stronger Ed25519 signing key
9406 algorithm for regular Tor relays (including support for encrypted
9407 offline identity keys in the new algorithm).
9409 Support for Ed25519 on relays is currently limited to signing router
9410 descriptors; later alphas in this series will extend Ed25519 key
9411 support to more parts of the Tor protocol.
9413 o Major features (Ed25519 identity keys, Proposal 220):
9414 - All relays now maintain a stronger identity key, using the Ed25519
9415 elliptic curve signature format. This master key is designed so
9416 that it can be kept offline. Relays also generate an online
9417 signing key, and a set of other Ed25519 keys and certificates.
9418 These are all automatically regenerated and rotated as needed.
9419 Implements part of ticket 12498.
9420 - Directory authorities now vote on Ed25519 identity keys along with
9421 RSA1024 keys. Implements part of ticket 12498.
9422 - Directory authorities track which Ed25519 identity keys have been
9423 used with which RSA1024 identity keys, and do not allow them to
9424 vary freely. Implements part of ticket 12498.
9425 - Microdescriptors now include Ed25519 identity keys. Implements
9426 part of ticket 12498.
9427 - Add support for offline encrypted Ed25519 master keys. To use this
9428 feature on your tor relay, run "tor --keygen" to make a new master
9429 key (or to make a new signing key if you already have a master
9430 key). Closes ticket 13642.
9432 o Major features (Hidden services):
9433 - Add the torrc option HiddenServiceNumIntroductionPoints, to
9434 specify a fixed number of introduction points. Its maximum value
9435 is 10 and default is 3. Using this option can increase a hidden
9436 service's reliability under load, at the cost of making it more
9437 visible that the hidden service is facing extra load. Closes
9439 - Remove the adaptive algorithm for choosing the number of
9440 introduction points, which used to change the number of
9441 introduction points (poorly) depending on the number of
9442 connections the HS sees. Closes ticket 4862.
9444 o Major features (onion key cross-certification):
9445 - Relay descriptors now include signatures of their own identity
9446 keys, made using the TAP and ntor onion keys. These signatures
9447 allow relays to prove ownership of their own onion keys. Because
9448 of this change, microdescriptors will no longer need to include
9449 RSA identity keys. Implements proposal 228; closes ticket 12499.
9451 o Major features (performance):
9452 - Improve the runtime speed of Ed25519 operations by using the
9453 public-domain Ed25519-donna by Andrew M. ("floodyberry").
9454 Implements ticket 16467.
9455 - Improve the runtime speed of the ntor handshake by using an
9456 optimized curve25519 basepoint scalarmult implementation from the
9457 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
9458 ideas by Adam Langley. Implements ticket 9663.
9460 o Major bugfixes (client-side privacy, also in 0.2.6.9):
9461 - Properly separate out each SOCKSPort when applying stream
9462 isolation. The error occurred because each port's session group
9463 was being overwritten by a default value when the listener
9464 connection was initialized. Fixes bug 16247; bugfix on
9465 0.2.6.3-alpha. Patch by "jojelino".
9467 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
9468 - Stop refusing to store updated hidden service descriptors on a
9469 client. This reverts commit 9407040c59218 (which indeed fixed bug
9470 14219, but introduced a major hidden service reachability
9471 regression detailed in bug 16381). This is a temporary fix since
9472 we can live with the minor issue in bug 14219 (it just results in
9473 some load on the network) but the regression of 16381 is too much
9474 of a setback. First-round fix for bug 16381; bugfix
9477 o Major bugfixes (hidden services):
9478 - When cannibalizing a circuit for an introduction point, always
9479 extend to the chosen exit node (creating a 4 hop circuit).
9480 Previously Tor would use the current circuit exit node, which
9481 changed the original choice of introduction point, and could cause
9482 the hidden service to skip excluded introduction points or
9483 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
9486 o Major bugfixes (open file limit):
9487 - The open file limit wasn't checked before calling
9488 tor_accept_socket_nonblocking(), which would make Tor exceed the
9489 limit. Now, before opening a new socket, Tor validates the open
9490 file limit just before, and if the max has been reached, return an
9491 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
9493 o Major bugfixes (stability, also in 0.2.6.10):
9494 - Stop crashing with an assertion failure when parsing certain kinds
9495 of malformed or truncated microdescriptors. Fixes bug 16400;
9496 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
9497 by "cypherpunks_backup".
9498 - Stop random client-side assertion failures that could occur when
9499 connecting to a busy hidden service, or connecting to a hidden
9500 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
9503 o Minor features (directory authorities, security, also in 0.2.6.9):
9504 - The HSDir flag given by authorities now requires the Stable flag.
9505 For the current network, this results in going from 2887 to 2806
9506 HSDirs. Also, it makes it harder for an attacker to launch a sybil
9507 attack by raising the effort for a relay to become Stable to
9508 require at the very least 7 days, while maintaining the 96 hours
9509 uptime requirement for HSDir. Implements ticket 8243.
9511 o Minor features (client):
9512 - Relax the validation of hostnames in SOCKS5 requests, allowing the
9513 character '_' to appear, in order to cope with domains observed in
9514 the wild that are serving non-RFC compliant records. Resolves
9516 - Relax the validation done to hostnames in SOCKS5 requests, and
9517 allow a single trailing '.' to cope with clients that pass FQDNs
9518 using that syntax to explicitly indicate that the domain name is
9519 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
9520 - Add GroupWritable and WorldWritable options to unix-socket based
9521 SocksPort and ControlPort options. These options apply to a single
9522 socket, and override {Control,Socks}SocketsGroupWritable. Closes
9525 o Minor features (control protocol):
9526 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
9527 the control protocol. Resolves ticket 15358.
9529 o Minor features (directory authorities):
9530 - Directory authorities no longer vote against the "Fast", "Stable",
9531 and "HSDir" flags just because they were going to vote against
9532 "Running": if the consensus turns out to be that the router was
9533 running, then the authority's vote should count. Patch from Peter
9534 Retzlaff; closes issue 8712.
9536 o Minor features (geoip, also in 0.2.6.10):
9537 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
9538 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
9540 o Minor features (hidden services):
9541 - Add the new options "HiddenServiceMaxStreams" and
9542 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
9543 limit the maximum number of simultaneous streams per circuit, and
9544 optionally tear down the circuit when the limit is exceeded. Part
9547 o Minor features (portability):
9548 - Use C99 variadic macros when the compiler is not GCC. This avoids
9549 failing compilations on MSVC, and fixes a log-file-based race
9550 condition in our old workarounds. Original patch from Gisle Vanem.
9552 o Minor bugfixes (compilation, also in 0.2.6.9):
9553 - Build with --enable-systemd correctly when libsystemd is
9554 installed, but systemd is not. Fixes bug 16164; bugfix on
9555 0.2.6.3-alpha. Patch from Peter Palfrader.
9557 o Minor bugfixes (controller):
9558 - Add the descriptor ID in each HS_DESC control event. It was
9559 missing, but specified in control-spec.txt. Fixes bug 15881;
9560 bugfix on 0.2.5.2-alpha.
9562 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
9563 - Check for failures from crypto_early_init, and refuse to continue.
9564 A previous typo meant that we could keep going with an
9565 uninitialized crypto library, and would have OpenSSL initialize
9566 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9567 when implementing ticket 4900. Patch by "teor".
9569 o Minor bugfixes (hidden services):
9570 - Fix a crash when reloading configuration while at least one
9571 configured and one ephemeral hidden service exists. Fixes bug
9572 16060; bugfix on 0.2.7.1-alpha.
9573 - Avoid crashing with a double-free bug when we create an ephemeral
9574 hidden service but adding it fails for some reason. Fixes bug
9575 16228; bugfix on 0.2.7.1-alpha.
9577 o Minor bugfixes (Linux seccomp2 sandbox):
9578 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
9579 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
9581 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
9582 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
9583 these when eventfd2() support is missing. Fixes bug 16363; bugfix
9584 on 0.2.6.3-alpha. Patch from "teor".
9586 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
9587 - Fix sandboxing to work when running as a relay, by allowing the
9588 renaming of secret_id_key, and allowing the eventfd2 and futex
9589 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
9591 - Allow systemd connections to work with the Linux seccomp2 sandbox
9592 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
9595 o Minor bugfixes (relay):
9596 - Fix a rarely-encountered memory leak when failing to initialize
9597 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
9600 o Minor bugfixes (systemd):
9601 - Fix an accidental formatting error that broke the systemd
9602 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
9603 - Tor's systemd unit file no longer contains extraneous spaces.
9604 These spaces would sometimes confuse tools like deb-systemd-
9605 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
9607 o Minor bugfixes (tests):
9608 - Use the configured Python executable when running test-stem-full.
9609 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
9611 o Minor bugfixes (tests, also in 0.2.6.9):
9612 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
9613 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
9615 o Minor bugfixes (threads, comments):
9616 - Always initialize return value in compute_desc_id in rendcommon.c
9617 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
9618 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
9619 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
9620 - Remove undefined directive-in-macro in test_util_writepid clang
9621 3.7 complains that using a preprocessor directive inside a macro
9622 invocation in test_util_writepid in test_util.c is undefined.
9623 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
9625 o Code simplification and refactoring:
9626 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
9627 to ensure they remain consistent and visible everywhere.
9628 - Remove some vestigial workarounds for the MSVC6 compiler. We
9629 haven't supported that in ages.
9630 - The link authentication code has been refactored for better
9631 testability and reliability. It now uses code generated with the
9632 "trunnel" binary encoding generator, to reduce the risk of bugs
9633 due to programmer error. Done as part of ticket 12498.
9636 - Include a specific and (hopefully) accurate documentation of the
9637 torrc file's meta-format in doc/torrc_format.txt. This is mainly
9638 of interest to people writing programs to parse or generate torrc
9639 files. This document is not a commitment to long-term
9640 compatibility; some aspects of the current format are a bit
9641 ridiculous. Closes ticket 2325.
9644 - Tor no longer supports copies of OpenSSL that are missing support
9645 for Elliptic Curve Cryptography. (We began using ECC when
9646 available in 0.2.4.8-alpha, for more safe and efficient key
9647 negotiation.) In particular, support for at least one of P256 or
9648 P224 is now required, with manual configuration needed if only
9649 P224 is available. Resolves ticket 16140.
9650 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
9651 on an operating system that has not upgraded to OpenSSL 1.0 or
9652 later, and you compile Tor from source, you will need to install a
9653 more recent OpenSSL to link Tor against.) These versions of
9654 OpenSSL are still supported by the OpenSSL, but the numerous
9655 cryptographic improvements in later OpenSSL releases makes them a
9656 clear choice. Resolves ticket 16034.
9657 - Remove the HidServDirectoryV2 option. Now all relays offer to
9658 store hidden service descriptors. Related to 16543.
9659 - Remove the VoteOnHidServDirectoriesV2 option, since all
9660 authorities have long set it to 1. Closes ticket 16543.
9663 - Document use of coverity, clang static analyzer, and clang dynamic
9664 undefined behavior and address sanitizers in doc/HACKING. Include
9665 detailed usage instructions in the blacklist. Patch by "teor".
9666 Closes ticket 15817.
9667 - The link authentication protocol code now has extensive tests.
9668 - The relay descriptor signature testing code now has
9670 - The test_workqueue program now runs faster, and is enabled by
9671 default as a part of "make check".
9672 - Now that OpenSSL has its own scrypt implementation, add an unit
9673 test that checks for interoperability between libscrypt_scrypt()
9674 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
9675 and rely on EVP_PBE_scrypt() whenever possible. Resolves
9679 Changes in version 0.2.6.10 - 2015-07-12
9680 Tor version 0.2.6.10 fixes some significant stability and hidden
9681 service client bugs, bulletproofs the cryptography init process, and
9682 fixes a bug when using the sandbox code with some older versions of
9683 Linux. Everyone running an older version, especially an older version
9684 of 0.2.6, should upgrade.
9686 o Major bugfixes (hidden service clients, stability):
9687 - Stop refusing to store updated hidden service descriptors on a
9688 client. This reverts commit 9407040c59218 (which indeed fixed bug
9689 14219, but introduced a major hidden service reachability
9690 regression detailed in bug 16381). This is a temporary fix since
9691 we can live with the minor issue in bug 14219 (it just results in
9692 some load on the network) but the regression of 16381 is too much
9693 of a setback. First-round fix for bug 16381; bugfix
9696 o Major bugfixes (stability):
9697 - Stop crashing with an assertion failure when parsing certain kinds
9698 of malformed or truncated microdescriptors. Fixes bug 16400;
9699 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
9700 by "cypherpunks_backup".
9701 - Stop random client-side assertion failures that could occur when
9702 connecting to a busy hidden service, or connecting to a hidden
9703 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
9706 o Minor features (geoip):
9707 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
9708 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
9710 o Minor bugfixes (crypto error-handling):
9711 - Check for failures from crypto_early_init, and refuse to continue.
9712 A previous typo meant that we could keep going with an
9713 uninitialized crypto library, and would have OpenSSL initialize
9714 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9715 when implementing ticket 4900. Patch by "teor".
9717 o Minor bugfixes (Linux seccomp2 sandbox):
9718 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
9719 these when eventfd2() support is missing. Fixes bug 16363; bugfix
9720 on 0.2.6.3-alpha. Patch from "teor".
9723 Changes in version 0.2.6.9 - 2015-06-11
9724 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
9725 requirements for receiving an HSDir flag, and addresses some other small
9726 bugs in the systemd and sandbox code. Clients using circuit isolation
9727 should upgrade; all directory authorities should upgrade.
9729 o Major bugfixes (client-side privacy):
9730 - Properly separate out each SOCKSPort when applying stream
9731 isolation. The error occurred because each port's session group was
9732 being overwritten by a default value when the listener connection
9733 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
9736 o Minor feature (directory authorities, security):
9737 - The HSDir flag given by authorities now requires the Stable flag.
9738 For the current network, this results in going from 2887 to 2806
9739 HSDirs. Also, it makes it harder for an attacker to launch a sybil
9740 attack by raising the effort for a relay to become Stable which
9741 takes at the very least 7 days to do so and by keeping the 96
9742 hours uptime requirement for HSDir. Implements ticket 8243.
9744 o Minor bugfixes (compilation):
9745 - Build with --enable-systemd correctly when libsystemd is
9746 installed, but systemd is not. Fixes bug 16164; bugfix on
9747 0.2.6.3-alpha. Patch from Peter Palfrader.
9749 o Minor bugfixes (Linux seccomp2 sandbox):
9750 - Fix sandboxing to work when running as a relaymby renaming of
9751 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
9752 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
9753 - Allow systemd connections to work with the Linux seccomp2 sandbox
9754 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
9757 o Minor bugfixes (tests):
9758 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
9759 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
9762 Changes in version 0.2.6.8 - 2015-05-21
9763 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
9764 fixes an authority-side bug in assigning the HSDir flag. All directory
9765 authorities should upgrade.
9767 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
9768 - Revert commit that made directory authorities assign the HSDir
9769 flag to relays without a DirPort; this was bad because such relays
9770 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
9773 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9774 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9775 a client authorized hidden service. Fixes bug 15823; bugfix
9778 o Minor features (geoip):
9779 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
9780 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
9784 Changes in version 0.2.7.1-alpha - 2015-05-12
9785 Tor 0.2.7.1-alpha is the first alpha release in its series. It
9786 includes numerous small features and bugfixes against previous Tor
9787 versions, and numerous small infrastructure improvements. The most
9788 notable features are several new ways for controllers to interact with
9789 the hidden services subsystem.
9791 o New system requirements:
9792 - Tor no longer includes workarounds to support Libevent versions
9793 before 1.3e. Libevent 2.0 or later is recommended. Closes
9796 o Major features (controller):
9797 - Add the ADD_ONION and DEL_ONION commands that allow the creation
9798 and management of hidden services via the controller. Closes
9800 - New "GETINFO onions/current" and "GETINFO onions/detached"
9801 commands to get information about hidden services created via the
9802 controller. Part of ticket 6411.
9803 - New HSFETCH command to launch a request for a hidden service
9804 descriptor. Closes ticket 14847.
9805 - New HSPOST command to upload a hidden service descriptor. Closes
9806 ticket 3523. Patch by "DonnchaC".
9808 o Major bugfixes (hidden services):
9809 - Revert commit that made directory authorities assign the HSDir
9810 flag to relays without a DirPort; this was bad because such relays
9811 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
9814 o Minor features (clock-jump tolerance):
9815 - Recover better when our clock jumps back many hours, like might
9816 happen for Tails or Whonix users who start with a very wrong
9817 hardware clock, use Tor to discover a more accurate time, and then
9818 fix their clock. Resolves part of ticket 8766.
9820 o Minor features (command-line interface):
9821 - Make --hash-password imply --hush to prevent unnecessary noise.
9822 Closes ticket 15542. Patch from "cypherpunks".
9823 - Print a warning whenever we find a relative file path being used
9824 as torrc option. Resolves issue 14018.
9826 o Minor features (controller):
9827 - Add DirAuthority lines for default directory authorities to the
9828 output of the "GETINFO config/defaults" command if not already
9829 present. Implements ticket 14840.
9830 - Controllers can now use "GETINFO hs/client/desc/id/..." to
9831 retrieve items from the client's hidden service descriptor cache.
9832 Closes ticket 14845.
9833 - Implement a new controller command "GETINFO status/fresh-relay-
9834 descs" to fetch a descriptor/extrainfo pair that was generated on
9835 demand just for the controller's use. Implements ticket 14784.
9837 o Minor features (DoS-resistance):
9838 - Make it harder for attackers to overload hidden services with
9839 introductions, by blocking multiple introduction requests on the
9840 same circuit. Resolves ticket 15515.
9842 o Minor features (geoip):
9843 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
9844 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
9847 o Minor features (HS popularity countermeasure):
9848 - To avoid leaking HS popularity, don't cycle the introduction point
9849 when we've handled a fixed number of INTRODUCE2 cells but instead
9850 cycle it when a random number of introductions is reached, thus
9851 making it more difficult for an attacker to find out the amount of
9852 clients that have used the introduction point for a specific HS.
9853 Closes ticket 15745.
9855 o Minor features (logging):
9856 - Include the Tor version in all LD_BUG log messages, since people
9857 tend to cut and paste those into the bugtracker. Implements
9860 o Minor features (pluggable transports):
9861 - When launching managed pluggable transports on Linux systems,
9862 attempt to have the kernel deliver a SIGTERM on tor exit if the
9863 pluggable transport process is still running. Resolves
9865 - When launching managed pluggable transports, setup a valid open
9866 stdin in the child process that can be used to detect if tor has
9867 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
9868 can be used by implementations to detect this new behavior.
9869 Resolves ticket 15435.
9871 o Minor features (testing):
9872 - Add a test to verify that the compiler does not eliminate our
9873 memwipe() implementation. Closes ticket 15377.
9874 - Add make rule `check-changes` to verify the format of changes
9875 files. Closes ticket 15180.
9876 - Add unit tests for control_event_is_interesting(). Add a compile-
9877 time check that the number of events doesn't exceed the capacity
9878 of control_event_t.event_mask. Closes ticket 15431, checks for
9879 bugs similar to 13085. Patch by "teor".
9880 - Command-line argument tests moved to Stem. Resolves ticket 14806.
9881 - Integrate the ntor, backtrace, and zero-length keys tests into the
9882 automake test suite. Closes ticket 15344.
9883 - Remove assertions during builds to determine Tor's test coverage.
9884 We don't want to trigger these even in assertions, so including
9885 them artificially makes our branch coverage look worse than it is.
9886 This patch provides the new test-stem-full and coverage-html-full
9887 configure options. Implements ticket 15400.
9889 o Minor bugfixes (build):
9890 - Improve out-of-tree builds by making non-standard rules work and
9891 clean up additional files and directories. Fixes bug 15053; bugfix
9894 o Minor bugfixes (command-line interface):
9895 - When "--quiet" is provided along with "--validate-config", do not
9896 write anything to stdout on success. Fixes bug 14994; bugfix
9898 - When complaining about bad arguments to "--dump-config", use
9901 o Minor bugfixes (configuration, unit tests):
9902 - Only add the default fallback directories when the DirAuthorities,
9903 AlternateDirAuthority, and FallbackDir directory config options
9904 are set to their defaults. The default fallback directory list is
9905 currently empty, this fix will only change tor's behavior when it
9906 has default fallback directories. Includes unit tests for
9907 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
9908 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
9910 o Minor bugfixes (correctness):
9911 - For correctness, avoid modifying a constant string in
9912 handle_control_postdescriptor. Fixes bug 15546; bugfix
9914 - Remove side-effects from tor_assert() calls. This was harmless,
9915 because we never disable assertions, but it is bad style and
9916 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
9919 o Minor bugfixes (hidden service):
9920 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9921 a client authorized hidden service. Fixes bug 15823; bugfix
9923 - Remove an extraneous newline character from the end of hidden
9924 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
9926 o Minor bugfixes (interface):
9927 - Print usage information for --dump-config when it is used without
9928 an argument. Also, fix the error message to use different wording
9929 and add newline at the end. Fixes bug 15541; bugfix
9932 o Minor bugfixes (logs):
9933 - When building Tor under Clang, do not include an extra set of
9934 parentheses in log messages that include function names. Fixes bug
9935 15269; bugfix on every released version of Tor when compiled with
9936 recent enough Clang.
9938 o Minor bugfixes (network):
9939 - When attempting to use fallback technique for network interface
9940 lookup, disregard loopback and multicast addresses since they are
9941 unsuitable for public communications.
9943 o Minor bugfixes (statistics):
9944 - Disregard the ConnDirectionStatistics torrc options when Tor is
9945 not a relay since in that mode of operation no sensible data is
9946 being collected and because Tor might run into measurement hiccups
9947 when running as a client for some time, then becoming a relay.
9948 Fixes bug 15604; bugfix on 0.2.2.35.
9950 o Minor bugfixes (test networks):
9951 - When self-testing reachability, use ExtendAllowPrivateAddresses to
9952 determine if local/private addresses imply reachability. The
9953 previous fix used TestingTorNetwork, which implies
9954 ExtendAllowPrivateAddresses, but this excluded rare configurations
9955 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
9956 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
9957 issue discovered by CJ Ess.
9959 o Minor bugfixes (testing):
9960 - Check for matching value in server response in ntor_ref.py. Fixes
9961 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
9963 - Set the severity correctly when testing
9964 get_interface_addresses_ifaddrs() and
9965 get_interface_addresses_win32(), so that the tests fail gracefully
9966 instead of triggering an assertion. Fixes bug 15759; bugfix on
9967 0.2.6.3-alpha. Reported by Nicolas Derive.
9969 o Code simplification and refactoring:
9970 - Move the hacky fallback code out of get_interface_address6() into
9971 separate function and get it covered with unit-tests. Resolves
9973 - Refactor hidden service client-side cache lookup to intelligently
9974 report its various failure cases, and disentangle failure cases
9975 involving a lack of introduction points. Closes ticket 14391.
9976 - Use our own Base64 encoder instead of OpenSSL's, to allow more
9977 control over the output. Part of ticket 15652.
9980 - Improve the descriptions of statistics-related torrc options in
9981 the manpage to describe rationale and possible uses cases. Fixes
9983 - Improve the layout and formatting of ./configure --help messages.
9984 Closes ticket 15024. Patch from "cypherpunks".
9985 - Standardize on the term "server descriptor" in the manual page.
9986 Previously, we had used "router descriptor", "server descriptor",
9987 and "relay descriptor" interchangeably. Part of ticket 14987.
9990 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
9991 and always use the internal Base64 decoder. The internal decoder
9992 has been part of tor since 0.2.0.10-alpha, and no one should
9993 be using the OpenSSL one. Part of ticket 15652.
9994 - Remove the 'tor_strclear()' function; use memwipe() instead.
9995 Closes ticket 14922.
9998 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
9999 fingerprinting we now recommend pluggable transports; for forward-
10000 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
10001 - Remove the undocumented "--digests" command-line option. It
10002 complicated our build process, caused subtle build issues on
10003 multiple platforms, and is now redundant since we started
10004 including git version identifiers. Closes ticket 14742.
10005 - Tor no longer contains checks for ancient directory cache versions
10006 that didn't know about microdescriptors.
10007 - Tor no longer contains workarounds for stat files generated by
10008 super-old versions of Tor that didn't choose guards sensibly.
10011 Changes in version 0.2.4.27 - 2015-04-06
10012 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
10013 could be used by an attacker to crash hidden services, or crash clients
10014 visiting hidden services. Hidden services should upgrade as soon as
10015 possible; clients should upgrade whenever packages become available.
10017 This release also backports a simple improvement to make hidden
10018 services a bit less vulnerable to denial-of-service attacks.
10020 o Major bugfixes (security, hidden service):
10021 - Fix an issue that would allow a malicious client to trigger an
10022 assertion failure and halt a hidden service. Fixes bug 15600;
10023 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
10024 - Fix a bug that could cause a client to crash with an assertion
10025 failure when parsing a malformed hidden service descriptor. Fixes
10026 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
10028 o Minor features (DoS-resistance, hidden service):
10029 - Introduction points no longer allow multiple INTRODUCE1 cells to
10030 arrive on the same circuit. This should make it more expensive for
10031 attackers to overwhelm hidden services with introductions.
10032 Resolves ticket 15515.
10035 Changes in version 0.2.5.12 - 2015-04-06
10036 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
10037 could be used by an attacker to crash hidden services, or crash clients
10038 visiting hidden services. Hidden services should upgrade as soon as
10039 possible; clients should upgrade whenever packages become available.
10041 This release also backports a simple improvement to make hidden
10042 services a bit less vulnerable to denial-of-service attacks.
10044 o Major bugfixes (security, hidden service):
10045 - Fix an issue that would allow a malicious client to trigger an
10046 assertion failure and halt a hidden service. Fixes bug 15600;
10047 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
10048 - Fix a bug that could cause a client to crash with an assertion
10049 failure when parsing a malformed hidden service descriptor. Fixes
10050 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
10052 o Minor features (DoS-resistance, hidden service):
10053 - Introduction points no longer allow multiple INTRODUCE1 cells to
10054 arrive on the same circuit. This should make it more expensive for
10055 attackers to overwhelm hidden services with introductions.
10056 Resolves ticket 15515.
10059 Changes in version 0.2.6.7 - 2015-04-06
10060 Tor 0.2.6.7 fixes two security issues that could be used by an
10061 attacker to crash hidden services, or crash clients visiting hidden
10062 services. Hidden services should upgrade as soon as possible; clients
10063 should upgrade whenever packages become available.
10065 This release also contains two simple improvements to make hidden
10066 services a bit less vulnerable to denial-of-service attacks.
10068 o Major bugfixes (security, hidden service):
10069 - Fix an issue that would allow a malicious client to trigger an
10070 assertion failure and halt a hidden service. Fixes bug 15600;
10071 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
10072 - Fix a bug that could cause a client to crash with an assertion
10073 failure when parsing a malformed hidden service descriptor. Fixes
10074 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
10076 o Minor features (DoS-resistance, hidden service):
10077 - Introduction points no longer allow multiple INTRODUCE1 cells to
10078 arrive on the same circuit. This should make it more expensive for
10079 attackers to overwhelm hidden services with introductions.
10080 Resolves ticket 15515.
10081 - Decrease the amount of reattempts that a hidden service performs
10082 when its rendezvous circuits fail. This reduces the computational
10083 cost for running a hidden service under heavy load. Resolves
10087 Changes in version 0.2.6.6 - 2015-03-24
10088 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
10090 It adds numerous safety, security, correctness, and performance
10091 improvements. Client programs can be configured to use more kinds of
10092 sockets, AutomapHosts works better, the multithreading backend is
10093 improved, cell transmission is refactored, test coverage is much
10094 higher, more denial-of-service attacks are handled, guard selection is
10095 improved to handle long-term guards better, pluggable transports
10096 should work a bit better, and some annoying hidden service performance
10097 bugs should be addressed.
10099 o Minor bugfixes (portability):
10100 - Use the correct datatype in the SipHash-2-4 function to prevent
10101 compilers from assuming any sort of alignment. Fixes bug 15436;
10102 bugfix on 0.2.5.3-alpha.
10104 Changes in version 0.2.6.5-rc - 2015-03-18
10105 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
10106 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
10108 o Major bugfixes (client):
10109 - Avoid crashing when making certain configuration option changes on
10110 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
10113 o Major bugfixes (pluggable transports):
10114 - Initialize the extended OR Port authentication cookie before
10115 launching pluggable transports. This prevents a race condition
10116 that occurred when server-side pluggable transports would cache the
10117 authentication cookie before it has been (re)generated. Fixes bug
10118 15240; bugfix on 0.2.5.1-alpha.
10120 o Major bugfixes (portability):
10121 - Do not crash on startup when running on Solaris. Fixes a bug
10122 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
10125 o Minor features (heartbeat):
10126 - On relays, report how many connections we negotiated using each
10127 version of the Tor link protocols. This information will let us
10128 know if removing support for very old versions of the Tor
10129 protocols is harming the network. Closes ticket 15212.
10131 o Code simplification and refactoring:
10132 - Refactor main loop to extract the 'loop' part. This makes it
10133 easier to run Tor under Shadow. Closes ticket 15176.
10136 Changes in version 0.2.5.11 - 2015-03-17
10137 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
10139 It backports several bugfixes from the 0.2.6 branch, including a
10140 couple of medium-level security fixes for relays and exit nodes.
10141 It also updates the list of directory authorities.
10143 o Directory authority changes:
10144 - Remove turtles as a directory authority.
10145 - Add longclaw as a new (v3) directory authority. This implements
10146 ticket 13296. This keeps the directory authority count at 9.
10147 - The directory authority Faravahar has a new IP address. This
10148 closes ticket 14487.
10150 o Major bugfixes (crash, OSX, security):
10151 - Fix a remote denial-of-service opportunity caused by a bug in
10152 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
10155 o Major bugfixes (relay, stability, possible security):
10156 - Fix a bug that could lead to a relay crashing with an assertion
10157 failure if a buffer of exactly the wrong layout was passed to
10158 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
10159 0.2.0.10-alpha. Patch from 'cypherpunks'.
10160 - Do not assert if the 'data' pointer on a buffer is advanced to the
10161 very end of the buffer; log a BUG message instead. Only assert if
10162 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
10164 o Major bugfixes (exit node stability):
10165 - Fix an assertion failure that could occur under high DNS load.
10166 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
10167 diagnosed and fixed by "cypherpunks".
10169 o Major bugfixes (Linux seccomp2 sandbox):
10170 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
10171 crash during attempts to call wait4. Fixes bug 15088; bugfix on
10172 0.2.5.1-alpha. Patch from "sanic".
10174 o Minor features (controller):
10175 - New "GETINFO bw-event-cache" to get information about recent
10176 bandwidth events. Closes ticket 14128. Useful for controllers to
10177 get recent bandwidth history after the fix for ticket 13988.
10179 o Minor features (geoip):
10180 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
10181 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
10184 o Minor bugfixes (client, automapping):
10185 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
10186 no value follows the option. Fixes bug 14142; bugfix on
10187 0.2.4.7-alpha. Patch by "teor".
10188 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
10189 14195; bugfix on 0.1.0.1-rc.
10191 o Minor bugfixes (compilation):
10192 - Build without warnings with the stock OpenSSL srtp.h header, which
10193 has a duplicate declaration of SSL_get_selected_srtp_profile().
10194 Fixes bug 14220; this is OpenSSL's bug, not ours.
10196 o Minor bugfixes (directory authority):
10197 - Allow directory authorities to fetch more data from one another if
10198 they find themselves missing lots of votes. Previously, they had
10199 been bumping against the 10 MB queued data limit. Fixes bug 14261;
10200 bugfix on 0.1.2.5-alpha.
10201 - Enlarge the buffer to read bwauth generated files to avoid an
10202 issue when parsing the file in dirserv_read_measured_bandwidths().
10203 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
10205 o Minor bugfixes (statistics):
10206 - Increase period over which bandwidth observations are aggregated
10207 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
10209 o Minor bugfixes (preventative security, C safety):
10210 - When reading a hexadecimal, base-32, or base-64 encoded value from
10211 a string, always overwrite the whole output buffer. This prevents
10212 some bugs where we would look at (but fortunately, not reveal)
10213 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
10217 Changes in version 0.2.4.26 - 2015-03-17
10218 Tor 0.2.4.26 includes an updated list of directory authorities. It
10219 also backports a couple of stability and security bugfixes from 0.2.5
10222 o Directory authority changes:
10223 - Remove turtles as a directory authority.
10224 - Add longclaw as a new (v3) directory authority. This implements
10225 ticket 13296. This keeps the directory authority count at 9.
10226 - The directory authority Faravahar has a new IP address. This
10227 closes ticket 14487.
10229 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
10230 - Fix an assertion failure that could occur under high DNS load.
10231 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
10232 diagnosed and fixed by "cypherpunks".
10234 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
10235 - Fix a bug that could lead to a relay crashing with an assertion
10236 failure if a buffer of exactly the wrong layout was passed to
10237 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
10238 0.2.0.10-alpha. Patch from 'cypherpunks'.
10239 - Do not assert if the 'data' pointer on a buffer is advanced to the
10240 very end of the buffer; log a BUG message instead. Only assert if
10241 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
10243 o Minor features (geoip):
10244 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
10245 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
10248 Changes in version 0.2.6.4-rc - 2015-03-09
10249 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
10250 attacker might be able to use in order to crash certain Tor
10251 directories. It also resolves some minor issues left over from, or
10252 introduced in, Tor 0.2.6.3-alpha or earlier.
10254 o Major bugfixes (crash, OSX, security):
10255 - Fix a remote denial-of-service opportunity caused by a bug in
10256 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
10259 o Major bugfixes (relay, stability, possible security):
10260 - Fix a bug that could lead to a relay crashing with an assertion
10261 failure if a buffer of exactly the wrong layout is passed to
10262 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
10263 0.2.0.10-alpha. Patch from "cypherpunks".
10264 - Do not assert if the 'data' pointer on a buffer is advanced to the
10265 very end of the buffer; log a BUG message instead. Only assert if
10266 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
10268 o Major bugfixes (FreeBSD IPFW transparent proxy):
10269 - Fix address detection with FreeBSD transparent proxies, when
10270 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
10273 o Major bugfixes (Linux seccomp2 sandbox):
10274 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
10275 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
10277 - Allow AF_UNIX hidden services to be used with the seccomp2
10278 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
10279 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
10280 crash during attempts to call wait4. Fixes bug 15088; bugfix on
10281 0.2.5.1-alpha. Patch from "sanic".
10283 o Minor features (controller):
10284 - Messages about problems in the bootstrap process now include
10285 information about the server we were trying to connect to when we
10286 noticed the problem. Closes ticket 15006.
10288 o Minor features (geoip):
10289 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
10290 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
10293 o Minor features (logs):
10294 - Quiet some log messages in the heartbeat and at startup. Closes
10297 o Minor bugfixes (certificate handling):
10298 - If an authority operator accidentally makes a signing certificate
10299 with a future publication time, do not discard its real signing
10300 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
10301 - Remove any old authority certificates that have been superseded
10302 for at least two days. Previously, we would keep superseded
10303 certificates until they expired, if they were published close in
10304 time to the certificate that superseded them. Fixes bug 11454;
10305 bugfix on 0.2.1.8-alpha.
10307 o Minor bugfixes (compilation):
10308 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
10310 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
10313 o Minor bugfixes (testing):
10314 - Fix endianness issues in unit test for resolve_my_address() to
10315 have it pass on big endian systems. Fixes bug 14980; bugfix on
10317 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
10318 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
10319 - When running the new 'make test-stem' target, use the configured
10320 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
10321 from "cypherpunks".
10322 - When running the zero-length-keys tests, do not use the default
10323 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
10326 o Directory authority IP change:
10327 - The directory authority Faravahar has a new IP address. This
10328 closes ticket 14487.
10331 - Remove some lingering dead code that once supported mempools.
10332 Mempools were disabled by default in 0.2.5, and removed entirely
10333 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
10337 Changes in version 0.2.6.3-alpha - 2015-02-19
10338 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
10339 the 0.2.6.x series. It introduces support for more kinds of sockets,
10340 makes it harder to accidentally run an exit, improves our
10341 multithreading backend, incorporates several fixes for the
10342 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
10344 If no major regressions or security holes are found in this version,
10345 the next version will be a release candidate.
10347 o Deprecated versions:
10348 - Tor relays older than 0.2.4.18-rc are no longer allowed to
10349 advertise themselves on the network. Closes ticket 13555.
10351 o Major features (security, unix domain sockets):
10352 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
10353 applications can reach Tor without having to create AF_INET or
10354 AF_INET6 sockets, meaning they can completely disable their
10355 ability to make non-Tor network connections. To create a socket of
10356 this type, use "SocksPort unix:/path/to/socket". Implements
10358 - Support mapping hidden service virtual ports to AF_UNIX sockets.
10359 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
10360 Implements ticket 11485.
10362 o Major features (changed defaults):
10363 - Prevent relay operators from unintentionally running exits: When a
10364 relay is configured as an exit node, we now warn the user unless
10365 the "ExitRelay" option is set to 1. We warn even more loudly if
10366 the relay is configured with the default exit policy, since this
10367 can indicate accidental misconfiguration. Setting "ExitRelay 0"
10368 stops Tor from running as an exit relay. Closes ticket 10067.
10370 o Major features (directory system):
10371 - When downloading server- or microdescriptors from a directory
10372 server, we no longer launch multiple simultaneous requests to the
10373 same server. This reduces load on the directory servers,
10374 especially when directory guards are in use. Closes ticket 9969.
10375 - When downloading server- or microdescriptors over a tunneled
10376 connection, do not limit the length of our requests to what the
10377 Squid proxy is willing to handle. Part of ticket 9969.
10378 - Authorities can now vote on the correct digests and latest
10379 versions for different software packages. This allows packages
10380 that include Tor to use the Tor authority system as a way to get
10381 notified of updates and their correct digests. Implements proposal
10382 227. Closes ticket 10395.
10384 o Major features (guards):
10385 - Introduce the Guardfraction feature to improves load balancing on
10386 guard nodes. Specifically, it aims to reduce the traffic gap that
10387 guard nodes experience when they first get the Guard flag. This is
10388 a required step if we want to increase the guard lifetime to 9
10389 months or greater. Closes ticket 9321.
10391 o Major features (performance):
10392 - Make the CPU worker implementation more efficient by avoiding the
10393 kernel and lengthening pipelines. The original implementation used
10394 sockets to transfer data from the main thread to the workers, and
10395 didn't allow any thread to be assigned more than a single piece of
10396 work at once. The new implementation avoids communications
10397 overhead by making requests in shared memory, avoiding kernel IO
10398 where possible, and keeping more requests in flight at once.
10399 Implements ticket 9682.
10401 o Major features (relay):
10402 - Raise the minimum acceptable configured bandwidth rate for bridges
10403 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
10404 20 KiB/sec.) Closes ticket 13822.
10406 o Major bugfixes (exit node stability):
10407 - Fix an assertion failure that could occur under high DNS load.
10408 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
10409 diagnosed and fixed by "cypherpunks".
10411 o Major bugfixes (mixed relay-client operation):
10412 - When running as a relay and client at the same time (not
10413 recommended), if we decide not to use a new guard because we want
10414 to retry older guards, only close the locally-originating circuits
10415 passing through that guard. Previously we would close all the
10416 circuits through that guard. Fixes bug 9819; bugfix on
10417 0.2.1.1-alpha. Reported by "skruffy".
10419 o Minor features (build):
10420 - New --disable-system-torrc compile-time option to prevent Tor from
10421 looking for the system-wide torrc or torrc-defaults files.
10422 Resolves ticket 13037.
10424 o Minor features (controller):
10425 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
10426 events so controllers can observe circuit isolation inputs. Closes
10428 - ControlPort now supports the unix:/path/to/socket syntax as an
10429 alternative to the ControlSocket option, for consistency with
10430 SocksPort and HiddenServicePort. Closes ticket 14451.
10431 - New "GETINFO bw-event-cache" to get information about recent
10432 bandwidth events. Closes ticket 14128. Useful for controllers to
10433 get recent bandwidth history after the fix for ticket 13988.
10435 o Minor features (Denial of service resistance):
10436 - Count the total number of bytes used storing hidden service
10437 descriptors against the value of MaxMemInQueues. If we're low on
10438 memory, and more than 20% of our memory is used holding hidden
10439 service descriptors, free them until no more than 10% of our
10440 memory holds hidden service descriptors. Free the least recently
10441 fetched descriptors first. Resolves ticket 13806.
10442 - When we have recently been under memory pressure (over 3/4 of
10443 MaxMemInQueues is allocated), then allocate smaller zlib objects
10444 for small requests. Closes ticket 11791.
10446 o Minor features (geoip):
10447 - Update geoip and geoip6 files to the January 7 2015 Maxmind
10448 GeoLite2 Country database.
10450 o Minor features (guard nodes):
10451 - Reduce the time delay before saving guard status to disk from 10
10452 minutes to 30 seconds (or from one hour to 10 minutes if
10453 AvoidDiskWrites is set). Closes ticket 12485.
10455 o Minor features (hidden service):
10456 - Make Sybil attacks against hidden services harder by changing the
10457 minimum time required to get the HSDir flag from 25 hours up to 96
10458 hours. Addresses ticket 14149.
10459 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
10460 services to disable the anti-scanning feature introduced in
10461 0.2.6.2-alpha. With this option not set, a connection to an
10462 unlisted port closes the circuit. With this option set, only a
10463 RELAY_DONE cell is sent. Closes ticket 14084.
10465 o Minor features (interface):
10466 - Implement "-f -" command-line option to read torrc configuration
10467 from standard input, if you don't want to store the torrc file in
10468 the file system. Implements feature 13865.
10470 o Minor features (logging):
10471 - Add a count of unique clients to the bridge heartbeat message.
10472 Resolves ticket 6852.
10473 - Suppress "router info incompatible with extra info" message when
10474 reading extrainfo documents from cache. (This message got loud
10475 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
10477 - Elevate hidden service authorized-client message from DEBUG to
10478 INFO. Closes ticket 14015.
10480 o Minor features (stability):
10481 - Add assertions in our hash-table iteration code to check for
10482 corrupted values that could cause infinite loops. Closes
10485 o Minor features (systemd):
10486 - Various improvements and modernizations in systemd hardening
10487 support. Closes ticket 13805. Patch from Craig Andrews.
10489 o Minor features (testing networks):
10490 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
10491 and the default on a testing network to 2 minutes. Drop the
10492 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
10493 keep the default on a testing network at 30 seconds. This reduces
10494 HS bootstrap time to around 25 seconds. Also, change the default
10495 time in test-network.sh to match. Closes ticket 13401. Patch
10497 - Create TestingDirAuthVoteHSDir to correspond to
10498 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
10499 HSDir flag for the listed relays regardless of uptime or ORPort
10500 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
10501 Partial implementation for ticket 14067. Patch by "teor".
10503 o Minor features (tor2web mode):
10504 - Introduce the config option Tor2webRendezvousPoints, which allows
10505 clients in Tor2webMode to select a specific Rendezvous Point to be
10506 used in HS circuits. This might allow better performance for
10507 Tor2Web nodes. Implements ticket 12844.
10509 o Minor bugfixes (client DNS):
10510 - Report the correct cached DNS expiration times on SOCKS port or in
10511 DNS replies. Previously, we would report everything as "never
10512 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
10513 - Avoid a small memory leak when we find a cached answer for a
10514 reverse DNS lookup in a client-side DNS cache. (Remember, client-
10515 side DNS caching is off by default, and is not recommended.) Fixes
10516 bug 14259; bugfix on 0.2.0.1-alpha.
10518 o Minor bugfixes (client, automapping):
10519 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
10520 no value follows the option. Fixes bug 14142; bugfix on
10521 0.2.4.7-alpha. Patch by "teor".
10522 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
10523 14195; bugfix on 0.1.0.1-rc.
10524 - Prevent changes to other options from removing the wildcard value
10525 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
10527 - Allow MapAddress and AutomapHostsOnResolve to work together when
10528 an address is mapped into another address type (like .onion) that
10529 must be automapped at resolve time. Fixes bug 7555; bugfix
10532 o Minor bugfixes (client, bridges):
10533 - When we are using bridges and we had a network connectivity
10534 problem, only retry connecting to our currently configured
10535 bridges, not all bridges we know about and remember using. Fixes
10536 bug 14216; bugfix on 0.2.2.17-alpha.
10538 o Minor bugfixes (client, IPv6):
10539 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
10540 flag is not set; and not because the NoIPv4Traffic flag was set.
10541 Previously we'd looked at the NoIPv4Traffic flag for both types of
10542 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
10544 o Minor bugfixes (compilation):
10545 - The address of an array in the middle of a structure will always
10546 be non-NULL. clang recognises this and complains. Disable the
10547 tautologous and redundant check to silence this warning. Fixes bug
10548 14001; bugfix on 0.2.1.2-alpha.
10549 - Avoid warnings when building with systemd 209 or later. Fixes bug
10550 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
10551 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
10552 Addresses ticket 14188.
10553 - Build without warnings with the stock OpenSSL srtp.h header, which
10554 has a duplicate declaration of SSL_get_selected_srtp_profile().
10555 Fixes bug 14220; this is OpenSSL's bug, not ours.
10556 - Do not compile any code related to Tor2Web mode when Tor2Web mode
10557 is not enabled at compile time. Previously, this code was included
10558 in a disabled state. See discussion on ticket 12844.
10559 - Remove the --disable-threads configure option again. It was
10560 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
10561 14819; bugfix on 0.2.6.2-alpha.
10563 o Minor bugfixes (controller):
10564 - Report "down" in response to the "GETINFO entry-guards" command
10565 when relays are down with an unreachable_since value. Previously,
10566 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
10567 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
10568 14116; bugfix on 0.2.2.9-alpha.
10569 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
10570 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
10572 o Minor bugfixes (directory authority):
10573 - Allow directory authorities to fetch more data from one another if
10574 they find themselves missing lots of votes. Previously, they had
10575 been bumping against the 10 MB queued data limit. Fixes bug 14261;
10576 bugfix on 0.1.2.5-alpha.
10577 - Do not attempt to download extrainfo documents which we will be
10578 unable to validate with a matching server descriptor. Fixes bug
10579 13762; bugfix on 0.2.0.1-alpha.
10580 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
10581 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
10582 - Enlarge the buffer to read bwauth generated files to avoid an
10583 issue when parsing the file in dirserv_read_measured_bandwidths().
10584 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
10586 o Minor bugfixes (file handling):
10587 - Stop failing when key files are zero-length. Instead, generate new
10588 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
10589 on all versions of Tor. Patch by "teor".
10590 - Stop generating a fresh .old RSA onion key file when the .old file
10591 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
10592 - Avoid overwriting .old key files with empty key files.
10593 - Skip loading zero-length extrainfo store, router store, stats,
10594 state, and key files.
10595 - Avoid crashing when trying to reload a torrc specified as a
10596 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
10599 o Minor bugfixes (hidden services):
10600 - Close the introduction circuit when we have no more usable intro
10601 points, instead of waiting for it to time out. This also ensures
10602 that no follow-up HS descriptor fetch is triggered when the
10603 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
10604 - When fetching a hidden service descriptor for a down service that
10605 was recently up, do not keep refetching until we try the same
10606 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
10607 - Successfully launch Tor with a nonexistent hidden service
10608 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
10609 14106; bugfix on 0.2.6.2-alpha.
10611 o Minor bugfixes (logging):
10612 - Avoid crashing when there are more log domains than entries in
10613 domain_list. Bugfix on 0.2.3.1-alpha.
10614 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
10616 - Don't log messages to stdout twice when starting up. Fixes bug
10617 13993; bugfix on 0.2.6.1-alpha.
10619 o Minor bugfixes (parsing):
10620 - Stop accepting milliseconds (or other junk) at the end of
10621 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
10622 - Support two-number and three-number version numbers correctly, in
10623 case we change the Tor versioning system in the future. Fixes bug
10624 13661; bugfix on 0.0.8pre1.
10626 o Minor bugfixes (path counting):
10627 - When deciding whether the consensus lists any exit nodes, count
10628 the number listed in the consensus, not the number we have
10629 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
10630 - When deciding whether we have any exit nodes, only examine
10631 ExitNodes when the ExitNodes option is actually set. Fixes part of
10632 bug 14918; bugfix on 0.2.6.2-alpha.
10633 - Get rid of redundant and possibly scary warnings that we are
10634 missing directory information while we bootstrap. Fixes part of
10635 bug 14918; bugfix on 0.2.6.2-alpha.
10637 o Minor bugfixes (portability):
10638 - Fix the ioctl()-based network interface lookup code so that it
10639 will work on systems that have variable-length struct ifreq, for
10641 - Fix scheduler compilation on targets where char is unsigned. Fixes
10642 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
10644 o Minor bugfixes (sandbox):
10645 - Allow glibc fatal errors to be sent to stderr before Tor exits.
10646 Previously, glibc would try to write them to /dev/tty, and the
10647 sandbox would trap the call and make Tor exit prematurely. Fixes
10648 bug 14759; bugfix on 0.2.5.1-alpha.
10650 o Minor bugfixes (shutdown):
10651 - When shutting down, always call event_del() on lingering read or
10652 write events before freeing them. Otherwise, we risk double-frees
10653 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
10656 o Minor bugfixes (small memory leaks):
10657 - Avoid leaking memory when using IPv6 virtual address mappings.
10658 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
10661 o Minor bugfixes (statistics):
10662 - Increase period over which bandwidth observations are aggregated
10663 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
10665 o Minor bugfixes (systemd support):
10666 - Fix detection and operation of systemd watchdog. Fixes part of bug
10667 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
10668 - Run correctly under systemd with the RunAsDaemon option set. Fixes
10669 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
10670 - Inform the systemd supervisor about more changes in the Tor
10671 process status. Implements part of ticket 14141. Patch from
10673 - Cause the "--disable-systemd" option to actually disable systemd
10674 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
10677 o Minor bugfixes (TLS):
10678 - Check more thoroughly throughout the TLS code for possible
10679 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
10681 o Minor bugfixes (transparent proxy):
10682 - Use getsockname, not getsockopt, to retrieve the address for a
10683 TPROXY-redirected connection. Fixes bug 13796; bugfix
10686 o Code simplification and refactoring:
10687 - Move fields related to isolating and configuring client ports into
10688 a shared structure. Previously, they were duplicated across
10689 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
10690 to copy them correctly had been the cause of at least one bug in
10691 the past. Closes ticket 8546.
10692 - Refactor the get_interface_addresses_raw() doom-function into
10693 multiple smaller and simpler subfunctions. Cover the resulting
10694 subfunctions with unit-tests. Fixes a significant portion of
10696 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
10697 only for version <= 0.2.2.24 which is now deprecated. Closes
10699 - Remove a test for a long-defunct broken version-one
10703 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
10704 for writing the OpenBSD-specific tips. Resolves ticket 13702.
10705 - Make the tor-resolve documentation match its help string and its
10706 options. Resolves part of ticket 14325.
10707 - Log a more useful error message from tor-resolve when failing to
10708 look up a hidden service address. Resolves part of ticket 14325.
10710 o Downgraded warnings:
10711 - Don't warn when we've attempted to contact a relay using the wrong
10712 ntor onion key. Closes ticket 9635.
10714 o Removed features:
10715 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
10716 longer silently accepted as an alias for "ExitNodes".
10717 - The --enable-mempool and --enable-buf-freelists options, which
10718 were originally created to work around bad malloc implementations,
10719 no longer exist. They were off-by-default in 0.2.5. Closes
10723 - Make the checkdir/perms test complete successfully even if the
10724 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
10725 - Test that tor does not fail when key files are zero-length. Check
10726 that tor generates new keys, and overwrites the empty key files.
10727 - Test that tor generates new keys when keys are missing
10728 (existing behavior).
10729 - Test that tor does not overwrite key files that already contain
10730 data (existing behavior). Tests bug 13111. Patch by "teor".
10731 - New "make test-stem" target to run stem integration tests.
10732 Requires that the "STEM_SOURCE_DIR" environment variable be set.
10733 Closes ticket 14107.
10734 - Make the test_cmdline_args.py script work correctly on Windows.
10735 Patch from Gisle Vanem.
10736 - Move the slower unit tests into a new "./src/test/test-slow"
10737 binary that can be run independently of the other tests. Closes
10739 - Avoid undefined behavior when sampling huge values from the
10740 Laplace distribution. This made unittests fail on Raspberry Pi.
10741 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
10744 Changes in version 0.2.6.2-alpha - 2014-12-31
10745 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
10746 It introduces a major new backend for deciding when to send cells on
10747 channels, which should lead down the road to big performance
10748 increases. It contains security and statistics features for better
10749 work on hidden services, and numerous bugfixes.
10751 This release contains many new unit tests, along with major
10752 performance improvements for running testing networks using Chutney.
10753 Thanks to a series of patches contributed by "teor", testing networks
10754 should now bootstrap in seconds, rather than minutes.
10756 o Major features (relay, infrastructure):
10757 - Complete revision of the code that relays use to decide which cell
10758 to send next. Formerly, we selected the best circuit to write on
10759 each channel, but we didn't select among channels in any
10760 sophisticated way. Now, we choose the best circuits globally from
10761 among those whose channels are ready to deliver traffic.
10763 This patch implements a new inter-cmux comparison API, a global
10764 high/low watermark mechanism and a global scheduler loop for
10765 transmission prioritization across all channels as well as among
10766 circuits on one channel. This schedule is currently tuned to
10767 (tolerantly) avoid making changes in network performance, but it
10768 should form the basis for major circuit performance increases in
10769 the future. Code by Andrea; tuning by Rob Jansen; implements
10772 o Major features (hidden services):
10773 - Make HS port scanning more difficult by immediately closing the
10774 circuit when a user attempts to connect to a nonexistent port.
10775 Closes ticket 13667.
10776 - Add a HiddenServiceStatistics option that allows Tor relays to
10777 gather and publish statistics about the overall size and volume of
10778 hidden service usage. Specifically, when this option is turned on,
10779 an HSDir will publish an approximate number of hidden services
10780 that have published descriptors to it the past 24 hours. Also, if
10781 a relay has acted as a hidden service rendezvous point, it will
10782 publish the approximate amount of rendezvous cells it has relayed
10783 the past 24 hours. The statistics themselves are obfuscated so
10784 that the exact values cannot be derived. For more details see
10785 proposal 238, "Better hidden service stats from Tor relays". This
10786 feature is currently disabled by default. Implements feature 13192.
10788 o Major bugfixes (client, automap):
10789 - Repair automapping with IPv6 addresses. This automapping should
10790 have worked previously, but one piece of debugging code that we
10791 inserted to detect a regression actually caused the regression to
10792 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
10793 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
10796 o Major bugfixes (hidden services):
10797 - When closing an introduction circuit that was opened in parallel
10798 with others, don't mark the introduction point as unreachable.
10799 Previously, the first successful connection to an introduction
10800 point would make the other introduction points get marked as
10801 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
10803 o Directory authority changes:
10804 - Remove turtles as a directory authority.
10805 - Add longclaw as a new (v3) directory authority. This implements
10806 ticket 13296. This keeps the directory authority count at 9.
10808 o Major removed features:
10809 - Tor clients no longer support connecting to hidden services
10810 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
10811 option has been removed. (There shouldn't be any hidden services
10812 running these versions on the network.) Closes ticket 7803.
10814 o Minor features (client):
10815 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
10816 is enabled, reject requests with IP addresses as hostnames.
10817 Resolves ticket 13315.
10819 o Minor features (controller):
10820 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
10821 write an unscheduled heartbeat message to the log. Implements
10824 o Minor features (geoip):
10825 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
10828 o Minor features (hidden services):
10829 - When re-enabling the network, don't try to build introduction
10830 circuits until we have successfully built a circuit. This makes
10831 hidden services come up faster when the network is re-enabled.
10832 Patch from "akwizgran". Closes ticket 13447.
10833 - When we fail to retrieve a hidden service descriptor, send the
10834 controller an "HS_DESC FAILED" controller event. Implements
10836 - New HiddenServiceDirGroupReadable option to cause hidden service
10837 directories and hostname files to be created group-readable. Patch
10838 from "anon", David Stainton, and "meejah". Closes ticket 11291.
10840 o Minor features (systemd):
10841 - Where supported, when running with systemd, report successful
10842 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
10843 - When running with systemd, support systemd watchdog messages. Part
10844 of ticket 11016. Patch by Michael Scherer.
10846 o Minor features (transparent proxy):
10847 - Update the transparent proxy option checks to allow for both ipfw
10848 and pf on OS X. Closes ticket 14002.
10849 - Use the correct option when using IPv6 with transparent proxy
10850 support on Linux. Resolves 13808. Patch by Francisco Blas
10853 o Minor bugfixes (preventative security, C safety):
10854 - When reading a hexadecimal, base-32, or base-64 encoded value from
10855 a string, always overwrite the whole output buffer. This prevents
10856 some bugs where we would look at (but fortunately, not reveal)
10857 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
10859 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
10860 just the part that's used. This makes it harder for data leak bugs
10861 to occur in the event of other programming failures. Resolves
10864 o Minor bugfixes (client, microdescriptors):
10865 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
10866 computing which microdescriptors to download. This keeps us from
10867 erroneous download behavior if two microdescriptor digests ever
10868 have the same first 160 bits. Fixes part of bug 13399; bugfix
10870 - Reset a router's status if its microdescriptor digest changes,
10871 even if the first 160 bits remain the same. Fixes part of bug
10872 13399; bugfix on 0.2.3.1-alpha.
10874 o Minor bugfixes (compilation):
10875 - Silence clang warnings under --enable-expensive-hardening,
10876 including implicit truncation of 64 bit values to 32 bit, const
10877 char assignment to self, tautological compare, and additional
10878 parentheses around equality tests. Fixes bug 13577; bugfix
10880 - Fix a clang warning about checking whether an address in the
10881 middle of a structure is NULL. Fixes bug 14001; bugfix
10884 o Minor bugfixes (hidden services):
10885 - Correctly send a controller event when we find that a rendezvous
10886 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
10887 - Pre-check directory permissions for new hidden-services to avoid
10888 at least one case of "Bug: Acting on config options left us in a
10889 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
10890 - When adding a new hidden service (for example, via SETCONF), Tor
10891 no longer congratulates the user for running a relay. Fixes bug
10892 13941; bugfix on 0.2.6.1-alpha.
10893 - When fetching hidden service descriptors, we now check not only
10894 for whether we got the hidden service we had in mind, but also
10895 whether we got the particular descriptors we wanted. This prevents
10896 a class of inefficient but annoying DoS attacks by hidden service
10897 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
10900 o Minor bugfixes (Linux seccomp2 sandbox):
10901 - Make transparent proxy support work along with the seccomp2
10902 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
10903 by Francisco Blas Izquierdo Riera.
10904 - Fix a memory leak in tor-resolve when running with the sandbox
10905 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
10907 o Minor bugfixes (logging):
10908 - Downgrade warnings about RSA signature failures to info log level.
10909 Emit a warning when an extra info document is found incompatible
10910 with a corresponding router descriptor. Fixes bug 9812; bugfix
10912 - Make connection_ap_handshake_attach_circuit() log the circuit ID
10913 correctly. Fixes bug 13701; bugfix on 0.0.6.
10915 o Minor bugfixes (misc):
10916 - Stop allowing invalid address patterns like "*/24" that contain
10917 both a wildcard address and a bit prefix length. This affects all
10918 our address-range parsing code. Fixes bug 7484; bugfix
10921 o Minor bugfixes (testing networks, fast startup):
10922 - Allow Tor to build circuits using a consensus with no exits. If
10923 the consensus has no exits (typical of a bootstrapping test
10924 network), allow Tor to build circuits once enough descriptors have
10925 been downloaded. This assists in bootstrapping a testing Tor
10926 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
10928 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
10929 header to directory servers. This allows us to obtain consensuses
10930 promptly when the consensus interval is very short. This assists
10931 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
10932 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
10933 - Stop assuming that private addresses are local when checking
10934 reachability in a TestingTorNetwork. Instead, when testing, assume
10935 all OR connections are remote. (This is necessary due to many test
10936 scenarios running all relays on localhost.) This assists in
10937 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
10938 0.1.0.1-rc. Patch by "teor".
10939 - Avoid building exit circuits from a consensus with no exits. Now
10940 thanks to our fix for 13718, we accept a no-exit network as not
10941 wholly lost, but we need to remember not to try to build exit
10942 circuits on it. Closes ticket 13814; patch by "teor".
10943 - Stop requiring exits to have non-zero bandwithcapacity in a
10944 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
10945 ignore exit bandwidthcapacity. This assists in bootstrapping a
10946 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
10947 on 0.2.0.3-alpha. Patch by "teor".
10948 - Add "internal" to some bootstrap statuses when no exits are
10949 available. If the consensus does not contain Exits, Tor will only
10950 build internal circuits. In this case, relevant statuses will
10951 contain the word "internal" as indicated in the Tor control-
10952 spec.txt. When bootstrap completes, Tor will be ready to build
10953 internal circuits. If a future consensus contains Exits, exit
10954 circuits may become available. Fixes part of bug 13718; bugfix on
10955 0.2.4.10-alpha. Patch by "teor".
10956 - Decrease minimum consensus interval to 10 seconds when
10957 TestingTorNetwork is set, or 5 seconds for the first consensus.
10958 Fix assumptions throughout the code that assume larger intervals.
10959 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
10961 - Avoid excluding guards from path building in minimal test
10962 networks, when we're in a test network and excluding guards would
10963 exclude all relays. This typically occurs in incredibly small tor
10964 networks, and those using "TestingAuthVoteGuard *". Fixes part of
10965 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
10967 o Code simplification and refactoring:
10968 - Stop using can_complete_circuits as a global variable; access it
10969 with a function instead.
10970 - Avoid using operators directly as macro arguments: this lets us
10971 apply coccinelle transformations to our codebase more directly.
10972 Closes ticket 13172.
10973 - Combine the functions used to parse ClientTransportPlugin and
10974 ServerTransportPlugin into a single function. Closes ticket 6456.
10975 - Add inline functions and convenience macros for inspecting channel
10976 state. Refactor the code to use convenience macros instead of
10977 checking channel state directly. Fixes issue 7356.
10978 - Document all members of was_router_added_t and rename
10979 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
10980 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
10981 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
10982 constant instead of hardcoded value. Fixes issue 13840.
10983 - Refactor our generic strmap and digestmap types into a single
10984 implementation, so that we can add a new digest256map
10988 - Document the bridge-authority-only 'networkstatus-bridges' file.
10989 Closes ticket 13713; patch from "tom".
10990 - Fix typo in PredictedPortsRelevanceTime option description in
10991 manpage. Resolves issue 13707.
10992 - Stop suggesting that users specify relays by nickname: it isn't a
10993 good idea. Also, properly cross-reference how to specify relays in
10994 all parts of manual documenting options that take a list of
10995 relays. Closes ticket 13381.
10996 - Clarify the HiddenServiceDir option description in manpage to make
10997 it clear that relative paths are taken with respect to the current
10998 working directory. Also clarify that this behavior is not
10999 guaranteed to remain indefinitely. Fixes issue 13913.
11002 - New tests for many parts of channel, relay, and circuitmux
11003 functionality. Code by Andrea; part of 9262.
11004 - New tests for parse_transport_line(). Part of ticket 6456.
11005 - In the unit tests, use chgrp() to change the group of the unit
11006 test temporary directory to the current user, so that the sticky
11007 bit doesn't interfere with tests that check directory groups.
11009 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
11013 Changes in version 0.2.6.1-alpha - 2014-10-30
11014 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
11015 includes numerous code cleanups and new tests, and fixes a large
11016 number of annoying bugs. Out-of-memory conditions are handled better
11017 than in 0.2.5, pluggable transports have improved proxy support, and
11018 clients now use optimistic data for contacting hidden services. Also,
11019 we are now more robust to changes in what we consider a parseable
11020 directory object, so that tightening restrictions does not have a risk
11021 of introducing infinite download loops.
11023 This is the first alpha release in a new series, so expect there to be
11024 bugs. Users who would rather test out a more stable branch should stay
11025 with 0.2.5.x for now.
11027 o New compiler and system requirements:
11028 - Tor 0.2.6.x requires that your compiler support more of the C99
11029 language standard than before. The 'configure' script now detects
11030 whether your compiler supports C99 mid-block declarations and
11031 designated initializers. If it does not, Tor will not compile.
11033 We may revisit this requirement if it turns out that a significant
11034 number of people need to build Tor with compilers that don't
11035 bother implementing a 15-year-old standard. Closes ticket 13233.
11036 - Tor no longer supports systems without threading support. When we
11037 began working on Tor, there were several systems that didn't have
11038 threads, or where the thread support wasn't able to run the
11039 threads of a single process on multiple CPUs. That no longer
11040 holds: every system where Tor needs to run well now has threading
11041 support. Resolves ticket 12439.
11043 o Removed platform support:
11044 - We no longer include special code to build on Windows CE; as far
11045 as we know, nobody has used Tor on Windows CE in a very long time.
11046 Closes ticket 11446.
11048 o Major features (bridges):
11049 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
11050 transports if they are configured via the "TOR_PT_PROXY"
11051 environment variable. Implements proposal 232. Resolves
11054 o Major features (client performance, hidden services):
11055 - Allow clients to use optimistic data when connecting to a hidden
11056 service, which should remove a round-trip from hidden service
11057 initialization. See proposal 181 for details. Implements
11060 o Major features (directory system):
11061 - Upon receiving an unparseable directory object, if its digest
11062 matches what we expected, then don't try to download it again.
11063 Previously, when we got a descriptor we didn't like, we would keep
11064 trying to download it over and over. Closes ticket 11243.
11066 o Major features (sample torrc):
11067 - Add a new, infrequently-changed "torrc.minimal". This file is
11068 similar to torrc.sample, but it will change as infrequently as
11069 possible, for the benefit of users whose systems prompt them for
11070 intervention whenever a default configuration file is changed.
11071 Making this change allows us to update torrc.sample to be a more
11072 generally useful "sample torrc".
11074 o Major bugfixes (directory authorities):
11075 - Do not assign the HSDir flag to relays if they are not Valid, or
11076 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
11078 o Major bugfixes (directory bandwidth performance):
11079 - Don't flush the zlib buffer aggressively when compressing
11080 directory information for clients. This should save about 7% of
11081 the bandwidth currently used for compressed descriptors and
11082 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
11084 o Minor features (security, memory wiping):
11085 - Ensure we securely wipe keys from memory after
11086 crypto_digest_get_digest and init_curve25519_keypair_from_file
11087 have finished using them. Resolves ticket 13477.
11089 o Minor features (security, out-of-memory handling):
11090 - When handling an out-of-memory condition, allocate less memory for
11091 temporary data structures. Fixes issue 10115.
11092 - When handling an out-of-memory condition, consider more types of
11093 buffers, including those on directory connections, and zlib
11094 buffers. Resolves ticket 11792.
11097 - When identity keypair is generated for first time, log a
11098 congratulatory message that links to the new relay lifecycle
11099 document. Implements feature 10427.
11101 o Minor features (client):
11102 - Clients are now willing to send optimistic data (before they
11103 receive a 'connected' cell) to relays of any version. (Relays
11104 without support for optimistic data are no longer supported on the
11105 Tor network.) Resolves ticket 13153.
11107 o Minor features (directory authorities):
11108 - Don't list relays with a bandwidth estimate of 0 in the consensus.
11109 Implements a feature proposed during discussion of bug 13000.
11110 - In tor-gencert, report an error if the user provides the same
11111 argument more than once.
11112 - If a directory authority can't find a best consensus method in the
11113 votes that it holds, it now falls back to its favorite consensus
11114 method. Previously, it fell back to method 1. Neither of these is
11115 likely to get enough signatures, but "fall back to favorite"
11116 doesn't require us to maintain support an obsolete consensus
11117 method. Implements part of proposal 215.
11119 o Minor features (logging):
11120 - On Unix-like systems, you can now use named pipes as the target of
11121 the Log option, and other options that try to append to files.
11122 Closes ticket 12061. Patch from "carlo von lynX".
11123 - When opening a log file at startup, send it every log message that
11124 we generated between startup and opening it. Previously, log
11125 messages that were generated before opening the log file were only
11126 logged to stdout. Closes ticket 6938.
11127 - Add a TruncateLogFile option to overwrite logs instead of
11128 appending to them. Closes ticket 5583.
11130 o Minor features (portability, Solaris):
11131 - Threads are no longer disabled by default on Solaris; we believe
11132 that the versions of Solaris with broken threading support are all
11133 obsolete by now. Resolves ticket 9495.
11135 o Minor features (relay):
11136 - Re-check our address after we detect a changed IP address from
11137 getsockname(). This ensures that the controller command "GETINFO
11138 address" will report the correct value. Resolves ticket 11582.
11140 - A new AccountingRule option lets Relays set whether they'd like
11141 AccountingMax to be applied separately to inbound and outbound
11142 traffic, or applied to the sum of inbound and outbound traffic.
11143 Resolves ticket 961. Patch by "chobe".
11145 o Minor features (testing networks):
11146 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
11147 the "Exit" flag regardless of their uptime, bandwidth, or exit
11148 policy. TestingTorNetwork must be set for this option to have any
11149 effect. Previously, authorities would take up to 35 minutes to
11150 give nodes the Exit flag in a test network. Partially implements
11153 o Minor features (validation):
11154 - Check all date/time values passed to tor_timegm and
11155 parse_rfc1123_time for validity, taking leap years into account.
11156 Improves HTTP header validation. Implemented with bug 13476.
11157 - In correct_tm(), limit the range of values returned by system
11158 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
11159 This means we don't have to deal with negative or too large dates,
11160 even if a clock is wrong. Otherwise we might fail to read a file
11161 written by us which includes such a date. Fixes bug 13476.
11163 o Minor bugfixes (bridge clients):
11164 - When configured to use a bridge without an identity digest (not
11165 recommended), avoid launching an extra channel to it when
11166 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
11168 o Minor bugfixes (bridges):
11169 - When DisableNetwork is set, do not launch pluggable transport
11170 plugins, and if any are running, terminate them. Fixes bug 13213;
11171 bugfix on 0.2.3.6-alpha.
11173 o Minor bugfixes (C correctness):
11174 - Fix several instances of possible integer overflow/underflow/NaN.
11175 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
11177 - In circuit_build_times_calculate_timeout() in circuitstats.c,
11178 avoid dividing by zero in the pareto calculations. This traps
11179 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
11181 - Fix an integer overflow in format_time_interval(). Fixes bug
11182 13393; bugfix on 0.2.0.10-alpha.
11183 - Set the correct day of year value when the system's localtime(_r)
11184 or gmtime(_r) functions fail to set struct tm. Not externally
11185 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
11186 - Avoid unlikely signed integer overflow in tor_timegm on systems
11187 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
11189 o Minor bugfixes (client):
11190 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
11191 BadExit flag are not considered worthy candidates. Fixes bug
11192 13066; bugfix on 0.1.2.3-alpha.
11193 - Use the consensus schedule for downloading consensuses, and not
11194 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
11195 - Handle unsupported or malformed SOCKS5 requests properly by
11196 responding with the appropriate error message before closing the
11197 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
11199 o Minor bugfixes (client, torrc):
11200 - Stop modifying the value of our DirReqStatistics torrc option just
11201 because we're not a bridge or relay. This bug was causing Tor
11202 Browser users to write "DirReqStatistics 0" in their torrc files
11203 as if they had chosen to change the config. Fixes bug 4244; bugfix
11205 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
11206 that our options have changed every time we SIGHUP. Fixes bug
11207 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
11209 o Minor bugfixes (controller):
11210 - Return an error when the second or later arguments of the
11211 "setevents" controller command are invalid events. Previously we
11212 would return success while silently skipping invalid events. Fixes
11213 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
11215 o Minor bugfixes (directory system):
11216 - Always believe that v3 directory authorities serve extra-info
11217 documents, whether they advertise "caches-extra-info" or not.
11218 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
11219 - When running as a v3 directory authority, advertise that you serve
11220 extra-info documents so that clients who want them can find them
11221 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
11222 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
11223 Previously, directories offering BRIDGE_DIRINFO and some other
11224 flag (i.e. microdescriptors or extrainfo) would be ignored when
11225 looking for bridges. Partially fixes bug 13163; bugfix
11228 o Minor bugfixes (networking):
11229 - Check for orconns and use connection_or_close_for_error() rather
11230 than connection_mark_for_close() directly in the getsockopt()
11231 failure case of connection_handle_write_impl(). Fixes bug 11302;
11232 bugfix on 0.2.4.4-alpha.
11234 o Minor bugfixes (relay):
11235 - When generating our family list, remove spaces from around the
11236 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
11237 - If our previous bandwidth estimate was 0 bytes, allow publishing a
11238 new relay descriptor immediately. Fixes bug 13000; bugfix
11241 o Minor bugfixes (testing networks):
11242 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
11243 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
11244 - Stop using the default authorities in networks which provide both
11245 AlternateDirAuthority and AlternateBridgeAuthority. Partially
11246 fixes bug 13163; bugfix on 0.2.0.13-alpha.
11248 o Minor bugfixes (testing):
11249 - Stop spawn test failures due to a race condition between the
11250 SIGCHLD handler updating the process status, and the test reading
11251 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
11253 o Minor bugfixes (testing, Windows):
11254 - Avoid passing an extra backslash when creating a temporary
11255 directory for running the unit tests on Windows. Fixes bug 12392;
11256 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
11258 o Minor bugfixes (windows):
11259 - Remove code to special-case handling of NTE_BAD_KEYSET when
11260 acquiring windows CryptoAPI context. This error can't actually
11261 occur for the parameters we're providing. Fixes bug 10816; bugfix
11264 o Minor bugfixes (zlib):
11265 - Avoid truncating a zlib stream when trying to finalize it with an
11266 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
11269 - Allow our configure script to build correctly with autoconf 2.62
11270 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
11271 - Improve the error message from ./configure to make it clear that
11272 when asciidoc has not been found, the user will have to either add
11273 --disable-asciidoc argument or install asciidoc. Resolves
11276 o Code simplification and refactoring:
11277 - Change the entry_is_live() function to take named bitfield
11278 elements instead of an unnamed list of booleans. Closes
11280 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
11281 Resolves ticket 12205.
11282 - Use calloc and reallocarray functions instead of multiply-
11283 then-malloc. This makes it less likely for us to fall victim to an
11284 integer overflow attack when allocating. Resolves ticket 12855.
11285 - Use the standard macro name SIZE_MAX, instead of our
11287 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
11288 functions which take them as arguments. Replace 0 with NO_DIRINFO
11289 in a function call for clarity. Seeks to prevent future issues
11291 - Avoid 4 null pointer errors under clang static analysis by using
11292 tor_assert() to prove that the pointers aren't null. Fixes
11294 - Rework the API of policies_parse_exit_policy() to use a bitmask to
11295 represent parsing options, instead of a confusing mess of
11296 booleans. Resolves ticket 8197.
11297 - Introduce a helper function to parse ExitPolicy in
11298 or_options_t structure.
11301 - Add a doc/TUNING document with tips for handling large numbers of
11302 TCP connections when running busy Tor relay. Update the warning
11303 message to point to this file when running out of sockets
11304 operating system is allowing to use simultaneously. Resolves
11307 o Removed features:
11308 - We no longer remind the user about configuration options that have
11309 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
11310 - Remove our old, non-weighted bandwidth-based node selection code.
11311 Previously, we used it as a fallback when we couldn't perform
11312 weighted bandwidth-based node selection. But that would only
11313 happen in the cases where we had no consensus, or when we had a
11314 consensus generated by buggy or ancient directory authorities. In
11315 either case, it's better to use the more modern, better maintained
11316 algorithm, with reasonable defaults for the weights. Closes
11318 - Remove the --disable-curve25519 configure option. Relays and
11319 clients now are required to support curve25519 and the
11321 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
11322 used to be deprecated synonyms for "StrictNodes", are now marked
11323 obsolete. Resolves ticket 12226.
11324 - Clients don't understand the BadDirectory flag in the consensus
11325 anymore, and ignore it.
11328 - Refactor the function that chooses guard nodes so that it can more
11329 easily be tested; write some tests for it.
11330 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
11331 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
11332 - Create unit tests for format_time_interval(). With bug 13393.
11333 - Add unit tests for tor_timegm signed overflow, tor_timegm and
11334 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
11335 tests (visible) fixes in bug 13476.
11336 - Add a "coverage-html" make target to generate HTML-visualized
11337 coverage results when building with --enable-coverage. (Requires
11338 lcov.) Patch from Kevin Murray.
11339 - Enable the backtrace handler (where supported) when running the
11341 - Revise all unit tests that used the legacy test_* macros to
11342 instead use the recommended tt_* macros. This patch was generated
11343 with coccinelle, to avoid manual errors. Closes ticket 13119.
11345 o Distribution (systemd):
11346 - systemd unit file: only allow tor to write to /var/lib/tor and
11347 /var/log/tor. The rest of the filesystem is accessible for reading
11348 only. Patch by intrigeri; resolves ticket 12751.
11349 - systemd unit file: ensure that the process and all its children
11350 can never gain new privileges. Patch by intrigeri; resolves
11352 - systemd unit file: set up /var/run/tor as writable for the Tor
11353 service. Patch by intrigeri; resolves ticket 13196.
11355 o Removed features (directory authorities):
11356 - Remove code that prevented authorities from listing Tor relays
11357 affected by CVE-2011-2769 as guards. These relays are already
11358 rejected altogether due to the minimum version requirement of
11359 0.2.3.16-alpha. Closes ticket 13152.
11360 - The "AuthDirRejectUnlisted" option no longer has any effect, as
11361 the fingerprints file (approved-routers) has been deprecated.
11362 - Directory authorities do not support being Naming dirauths anymore.
11363 The "NamingAuthoritativeDir" config option is now obsolete.
11364 - Directory authorities do not support giving out the BadDirectory
11366 - Directory authorities no longer advertise or support consensus
11367 methods 1 through 12 inclusive. These consensus methods were
11368 obsolete and/or insecure: maintaining the ability to support them
11369 served no good purpose. Implements part of proposal 215; closes
11372 o Testing (test-network.sh):
11373 - Stop using "echo -n", as some shells' built-in echo doesn't
11374 support "-n". Instead, use "/bin/echo -n". Partially fixes
11376 - Stop an apparent test-network hang when used with make -j2. Fixes
11378 - Add a --delay option to test-network.sh, which configures the
11379 delay before the chutney network tests for data transmission.
11380 Partially implements ticket 13161.
11383 Changes in version 0.2.5.10 - 2014-10-24
11384 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
11386 It adds several new security features, including improved
11387 denial-of-service resistance for relays, new compiler hardening
11388 options, and a system-call sandbox for hardened installations on Linux
11389 (requires seccomp2). The controller protocol has several new features,
11390 resolving IPv6 addresses should work better than before, and relays
11391 should be a little more CPU-efficient. We've added support for more
11392 OpenBSD and FreeBSD transparent proxy types. We've improved the build
11393 system and testing infrastructure to allow unit testing of more parts
11394 of the Tor codebase. Finally, we've addressed several nagging pluggable
11395 transport usability issues, and included numerous other small bugfixes
11396 and features mentioned below.
11398 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
11399 have accumulated many known flaws; everyone should upgrade.
11401 o Deprecated versions:
11402 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
11403 attention for some while.
11406 Changes in version 0.2.5.9-rc - 2014-10-20
11407 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
11408 series. It disables SSL3 in response to the recent "POODLE" attack
11409 (even though POODLE does not affect Tor). It also works around a crash
11410 bug caused by some operating systems' response to the "POODLE" attack
11411 (which does affect Tor). It also contains a few miscellaneous fixes.
11413 o Major security fixes:
11414 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
11415 today support TLS 1.0 or later, so we can safely turn off support
11416 for this old (and insecure) protocol. Fixes bug 13426.
11418 o Major bugfixes (openssl bug workaround):
11419 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
11420 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
11421 13471. This is a workaround for an OpenSSL bug.
11424 - Disable the sandbox name resolver cache when running tor-resolve:
11425 tor-resolve doesn't use the sandbox code, and turning it on was
11426 breaking attempts to do tor-resolve on a non-default server on
11427 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
11429 o Compilation fixes:
11430 - Build and run correctly on systems like OpenBSD-current that have
11431 patched OpenSSL to remove get_cipher_by_char and/or its
11432 implementations. Fixes issue 13325.
11434 o Downgraded warnings:
11435 - Downgrade the severity of the 'unexpected sendme cell from client'
11436 from 'warn' to 'protocol warning'. Closes ticket 8093.
11439 Changes in version 0.2.4.25 - 2014-10-20
11440 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
11441 (even though POODLE does not affect Tor). It also works around a crash
11442 bug caused by some operating systems' response to the "POODLE" attack
11443 (which does affect Tor).
11445 o Major security fixes (also in 0.2.5.9-rc):
11446 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
11447 today support TLS 1.0 or later, so we can safely turn off support
11448 for this old (and insecure) protocol. Fixes bug 13426.
11450 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
11451 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
11452 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
11453 13471. This is a workaround for an OpenSSL bug.
11456 Changes in version 0.2.5.8-rc - 2014-09-22
11457 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
11458 series. It fixes a bug that affects consistency and speed when
11459 connecting to hidden services, and it updates the location of one of
11460 the directory authorities.
11463 - Clients now send the correct address for their chosen rendezvous
11464 point when trying to access a hidden service. They used to send
11465 the wrong address, which would still work some of the time because
11466 they also sent the identity digest of the rendezvous point, and if
11467 the hidden service happened to try connecting to the rendezvous
11468 point from a relay that already had a connection open to it,
11469 the relay would reuse that connection. Now connections to hidden
11470 services should be more robust and faster. Also, this bug meant
11471 that clients were leaking to the hidden service whether they were
11472 on a little-endian (common) or big-endian (rare) system, which for
11473 some users might have reduced their anonymity. Fixes bug 13151;
11474 bugfix on 0.2.1.5-alpha.
11476 o Directory authority changes:
11477 - Change IP address for gabelmoo (v3 directory authority).
11480 Changes in version 0.2.4.24 - 2014-09-22
11481 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
11482 connecting to hidden services, and it updates the location of one of
11483 the directory authorities.
11486 - Clients now send the correct address for their chosen rendezvous
11487 point when trying to access a hidden service. They used to send
11488 the wrong address, which would still work some of the time because
11489 they also sent the identity digest of the rendezvous point, and if
11490 the hidden service happened to try connecting to the rendezvous
11491 point from a relay that already had a connection open to it,
11492 the relay would reuse that connection. Now connections to hidden
11493 services should be more robust and faster. Also, this bug meant
11494 that clients were leaking to the hidden service whether they were
11495 on a little-endian (common) or big-endian (rare) system, which for
11496 some users might have reduced their anonymity. Fixes bug 13151;
11497 bugfix on 0.2.1.5-alpha.
11499 o Directory authority changes:
11500 - Change IP address for gabelmoo (v3 directory authority).
11502 o Minor features (geoip):
11503 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
11507 Changes in version 0.2.5.7-rc - 2014-09-11
11508 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
11509 release series, and some long-standing bugs related to ORPort reachability
11510 testing and failure to send CREATE cells. It is the first release
11511 candidate for the Tor 0.2.5.x series.
11513 o Major bugfixes (client, startup):
11514 - Start making circuits as soon as DisabledNetwork is turned off.
11515 When Tor started with DisabledNetwork set, it would correctly
11516 conclude that it shouldn't build circuits, but it would mistakenly
11517 cache this conclusion, and continue believing it even when
11518 DisableNetwork is set to 0. Fixes the bug introduced by the fix
11519 for bug 11200; bugfix on 0.2.5.4-alpha.
11520 - Resume expanding abbreviations for command-line options. The fix
11521 for bug 4647 accidentally removed our hack from bug 586 that
11522 rewrote HashedControlPassword to __HashedControlSessionPassword
11523 when it appears on the commandline (which allowed the user to set
11524 her own HashedControlPassword in the torrc file while the
11525 controller generates a fresh session password for each run). Fixes
11526 bug 12948; bugfix on 0.2.5.1-alpha.
11527 - Warn about attempts to run hidden services and relays in the same
11528 process: that's probably not a good idea. Closes ticket 12908.
11530 o Major bugfixes (relay):
11531 - Avoid queuing or sending destroy cells for circuit ID zero when we
11532 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
11533 Found and fixed by "cypherpunks".
11534 - Fix ORPort reachability detection on relays running behind a
11535 proxy, by correctly updating the "local" mark on the controlling
11536 channel when changing the address of an or_connection_t after the
11537 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
11539 o Minor features (bridge):
11540 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
11541 cookie file for the ExtORPort g+r by default.
11543 o Minor features (geoip):
11544 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
11547 o Minor bugfixes (logging):
11548 - Reduce the log severity of the "Pluggable transport proxy does not
11549 provide any needed transports and will not be launched." message,
11550 since Tor Browser includes several ClientTransportPlugin lines in
11551 its torrc-defaults file, leading every Tor Browser user who looks
11552 at her logs to see these notices and wonder if they're dangerous.
11553 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
11554 - Downgrade "Unexpected onionskin length after decryption" warning
11555 to a protocol-warn, since there's nothing relay operators can do
11556 about a client that sends them a malformed create cell. Resolves
11557 bug 12996; bugfix on 0.0.6rc1.
11558 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
11559 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
11560 - When logging information about an EXTEND2 or EXTENDED2 cell, log
11561 their names correctly. Fixes part of bug 12700; bugfix
11563 - When logging information about a relay cell whose command we don't
11564 recognize, log its command as an integer. Fixes part of bug 12700;
11565 bugfix on 0.2.1.10-alpha.
11566 - Escape all strings from the directory connection before logging
11567 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
11569 o Minor bugfixes (controller):
11570 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
11571 bug 12864; bugfix on 0.2.5.1-alpha.
11572 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
11573 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
11576 o Minor bugfixes (compilation):
11577 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
11578 bugfix on 0.2.5.5-alpha.
11579 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
11580 0.2.5.1-alpha. Patch from "NewEraCracker".
11581 - In routerlist_assert_ok(), don't take the address of a
11582 routerinfo's cache_info member unless that routerinfo is non-NULL.
11583 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
11584 - Fix a large number of false positive warnings from the clang
11585 analyzer static analysis tool. This should make real warnings
11586 easier for clang analyzer to find. Patch from "teor". Closes
11589 o Distribution (systemd):
11590 - Verify configuration file via ExecStartPre in the systemd unit
11591 file. Patch from intrigeri; resolves ticket 12730.
11592 - Explicitly disable RunAsDaemon in the systemd unit file. Our
11593 current systemd unit uses "Type = simple", so systemd does not
11594 expect tor to fork. If the user has "RunAsDaemon 1" in their
11595 torrc, then things won't work as expected. This is e.g. the case
11596 on Debian (and derivatives), since there we pass "--defaults-torrc
11597 /usr/share/tor/tor-service-defaults-torrc" (that contains
11598 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
11602 - Adjust the URLs in the README to refer to the new locations of
11603 several documents on the website. Fixes bug 12830. Patch from
11605 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
11609 Changes in version 0.2.5.6-alpha - 2014-07-28
11610 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
11611 risk from guard rotation, and fixes a variety of other issues to get
11612 us closer to a release candidate.
11614 o Major features (also in 0.2.4.23):
11615 - Make the number of entry guards configurable via a new
11616 NumEntryGuards consensus parameter, and the number of directory
11617 guards configurable via a new NumDirectoryGuards consensus
11618 parameter. Implements ticket 12688.
11620 o Major bugfixes (also in 0.2.4.23):
11621 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
11622 implementation that caused incorrect results on 32-bit
11623 implementations when certain malformed inputs were used along with
11624 a small class of private ntor keys. This bug does not currently
11625 appear to allow an attacker to learn private keys or impersonate a
11626 Tor server, but it could provide a means to distinguish 32-bit Tor
11627 implementations from 64-bit Tor implementations. Fixes bug 12694;
11628 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
11632 - Perform circuit cleanup operations even when circuit
11633 construction operations are disabled (because the network is
11634 disabled, or because there isn't enough directory information).
11635 Previously, when we were not building predictive circuits, we
11636 were not closing expired circuits either. Fixes bug 8387; bugfix on
11637 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
11638 became more strict about when we have "enough directory information
11639 to build circuits".
11642 - Authorities now assign the Guard flag to the fastest 25% of the
11643 network (it used to be the fastest 50%). Also raise the consensus
11644 weight that guarantees the Guard flag from 250 to 2000. For the
11645 current network, this results in about 1100 guards, down from 2500.
11646 This step paves the way for moving the number of entry guards
11647 down to 1 (proposal 236) while still providing reasonable expected
11648 performance for most users. Implements ticket 12690.
11649 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
11651 - Slightly enhance the diagnostic message for bug 12184.
11653 o Minor bugfixes (also in 0.2.4.23):
11654 - Warn and drop the circuit if we receive an inbound 'relay early'
11655 cell. Those used to be normal to receive on hidden service circuits
11656 due to bug 1038, but the buggy Tor versions are long gone from
11657 the network so we can afford to resume watching for them. Resolves
11658 the rest of bug 1038; bugfix on 0.2.1.19.
11659 - Correct a confusing error message when trying to extend a circuit
11660 via the control protocol but we don't know a descriptor or
11661 microdescriptor for one of the specified relays. Fixes bug 12718;
11662 bugfix on 0.2.3.1-alpha.
11665 - Fix compilation when building with bufferevents enabled. (This
11666 configuration is still not expected to work, however.)
11667 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
11668 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
11670 - Compile correctly with builds and forks of OpenSSL (such as
11671 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
11672 0.2.1.1-alpha. Patch from "dhill".
11675 Changes in version 0.2.4.23 - 2014-07-28
11676 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
11677 guard rotation, and also backports several important fixes from the
11678 Tor 0.2.5 alpha release series.
11681 - Clients now look at the "usecreatefast" consensus parameter to
11682 decide whether to use CREATE_FAST or CREATE cells for the first hop
11683 of their circuit. This approach can improve security on connections
11684 where Tor's circuit handshake is stronger than the available TLS
11685 connection security levels, but the tradeoff is more computational
11686 load on guard relays. Implements proposal 221. Resolves ticket 9386.
11687 - Make the number of entry guards configurable via a new
11688 NumEntryGuards consensus parameter, and the number of directory
11689 guards configurable via a new NumDirectoryGuards consensus
11690 parameter. Implements ticket 12688.
11693 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
11694 implementation that caused incorrect results on 32-bit
11695 implementations when certain malformed inputs were used along with
11696 a small class of private ntor keys. This bug does not currently
11697 appear to allow an attacker to learn private keys or impersonate a
11698 Tor server, but it could provide a means to distinguish 32-bit Tor
11699 implementations from 64-bit Tor implementations. Fixes bug 12694;
11700 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
11704 - Warn and drop the circuit if we receive an inbound 'relay early'
11705 cell. Those used to be normal to receive on hidden service circuits
11706 due to bug 1038, but the buggy Tor versions are long gone from
11707 the network so we can afford to resume watching for them. Resolves
11708 the rest of bug 1038; bugfix on 0.2.1.19.
11709 - Correct a confusing error message when trying to extend a circuit
11710 via the control protocol but we don't know a descriptor or
11711 microdescriptor for one of the specified relays. Fixes bug 12718;
11712 bugfix on 0.2.3.1-alpha.
11713 - Avoid an illegal read from stack when initializing the TLS
11714 module using a version of OpenSSL without all of the ciphers
11715 used by the v2 link handshake. Fixes bug 12227; bugfix on
11716 0.2.4.8-alpha. Found by "starlight".
11719 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
11723 Changes in version 0.2.5.5-alpha - 2014-06-18
11724 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
11725 0.2.5.x release series, including a couple of DoS issues, some
11726 performance regressions, a large number of bugs affecting the Linux
11727 seccomp2 sandbox code, and various other bugfixes. It also adds
11728 diagnostic bugfixes for a few tricky issues that we're trying to
11731 o Major features (security, traffic analysis resistance):
11732 - Several major improvements to the algorithm used to decide when to
11733 close TLS connections. Previous versions of Tor closed connections
11734 at a fixed interval after the last time a non-padding cell was
11735 sent over the connection, regardless of the target of the
11736 connection. Now, we randomize the intervals by adding up to 50% of
11737 their base value, we measure the length of time since connection
11738 last had at least one circuit, and we allow connections to known
11739 ORs to remain open a little longer (15 minutes instead of 3
11740 minutes minimum). These changes should improve Tor's resistance
11741 against some kinds of traffic analysis, and lower some overhead
11742 from needlessly closed connections. Fixes ticket 6799.
11743 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
11745 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
11746 - Fix a memory leak that could occur if a microdescriptor parse
11747 fails during the tokenizing step. This bug could enable a memory
11748 exhaustion attack by directory servers. Fixes bug 11649; bugfix
11751 o Major bugfixes (security, directory authorities):
11752 - Directory authorities now include a digest of each relay's
11753 identity key as a part of its microdescriptor.
11755 This is a workaround for bug 11743 (reported by "cypherpunks"),
11756 where Tor clients do not support receiving multiple
11757 microdescriptors with the same SHA256 digest in the same
11758 consensus. When clients receive a consensus like this, they only
11759 use one of the relays. Without this fix, a hostile relay could
11760 selectively disable some client use of target relays by
11761 constructing a router descriptor with a different identity and the
11762 same microdescriptor parameters and getting the authorities to
11763 list it in a microdescriptor consensus. This fix prevents an
11764 attacker from causing a microdescriptor collision, because the
11765 router's identity is not forgeable.
11767 o Major bugfixes (relay):
11768 - Use a direct dirport connection when uploading non-anonymous
11769 descriptors to the directory authorities. Previously, relays would
11770 incorrectly use tunnel connections under a fairly wide variety of
11771 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
11772 - When a circuit accidentally has the same circuit ID for its
11773 forward and reverse direction, correctly detect the direction of
11774 cells using that circuit. Previously, this bug made roughly one
11775 circuit in a million non-functional. Fixes bug 12195; this is a
11776 bugfix on every version of Tor.
11778 o Major bugfixes (client, pluggable transports):
11779 - When managing pluggable transports, use OS notification facilities
11780 to learn if they have crashed, and don't attempt to kill any
11781 process that has already exited. Fixes bug 8746; bugfix
11784 o Minor features (diagnostic):
11785 - When logging a warning because of bug 7164, additionally check the
11786 hash table for consistency (as proposed on ticket 11737). This may
11787 help diagnose bug 7164.
11788 - When we log a heartbeat, log how many one-hop circuits we have
11789 that are at least 30 minutes old, and log status information about
11790 a few of them. This is an attempt to track down bug 8387.
11791 - When encountering an unexpected CR while writing text to a file on
11792 Windows, log the name of the file. Should help diagnosing
11794 - Give more specific warnings when a client notices that an onion
11795 handshake has failed. Fixes ticket 9635.
11796 - Add significant new logging code to attempt to diagnose bug 12184,
11797 where relays seem to run out of available circuit IDs.
11798 - Improve the diagnostic log message for bug 8387 even further to
11799 try to improve our odds of figuring out why one-hop directory
11800 circuits sometimes do not get closed.
11802 o Minor features (security, memory management):
11803 - Memory allocation tricks (mempools and buffer freelists) are now
11804 disabled by default. You can turn them back on with
11805 --enable-mempools and --enable-buf-freelists respectively. We're
11806 disabling these features because malloc performance is good enough
11807 on most platforms, and a similar feature in OpenSSL exacerbated
11808 exploitation of the Heartbleed attack. Resolves ticket 11476.
11810 o Minor features (security):
11811 - Apply the secure SipHash-2-4 function to the hash table mapping
11812 circuit IDs and channels to circuits. We missed this one when we
11813 were converting all the other hash functions to use SipHash back
11814 in 0.2.5.3-alpha. Resolves ticket 11750.
11816 o Minor features (build):
11817 - The configure script has a --disable-seccomp option to turn off
11818 support for libseccomp on systems that have it, in case it (or
11819 Tor's use of it) is broken. Resolves ticket 11628.
11821 o Minor features (other):
11822 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
11825 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
11826 - When running a hidden service, do not allow TunneledDirConns 0;
11827 this will keep the hidden service from running, and also
11828 make it publish its descriptors directly over HTTP. Fixes bug 10849;
11829 bugfix on 0.2.1.1-alpha.
11831 o Minor bugfixes (performance):
11832 - Avoid a bug where every successful connection made us recompute
11833 the flag telling us whether we have sufficient information to
11834 build circuits. Previously, we would forget our cached value
11835 whenever we successfully opened a channel (or marked a router as
11836 running or not running for any other reason), regardless of
11837 whether we had previously believed the router to be running. This
11838 forced us to run an expensive update operation far too often.
11839 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
11840 - Avoid using tor_memeq() for checking relay cell integrity. This
11841 removes a possible performance bottleneck. Fixes part of bug
11842 12169; bugfix on 0.2.1.31.
11844 o Minor bugfixes (compilation):
11845 - Fix compilation of test_status.c when building with MVSC. Bugfix
11846 on 0.2.5.4-alpha. Patch from Gisle Vanem.
11847 - Resolve GCC complaints on OpenBSD about discarding constness in
11848 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
11849 on 0.1.1.23. Patch from Dana Koch.
11850 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
11851 treatment of long and time_t as comparable types. Fixes part of
11852 bug 11633. Patch from Dana Koch.
11853 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
11854 11623; bugfix on 0.2.5.3-alpha.
11855 - When deciding whether to build the 64-bit curve25519
11856 implementation, detect platforms where we can compile 128-bit
11857 arithmetic but cannot link it. Fixes bug 11729; bugfix on
11858 0.2.4.8-alpha. Patch from "conradev".
11859 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
11860 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
11861 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
11864 o Minor bugfixes (Directory server):
11865 - When sending a compressed set of descriptors or microdescriptors,
11866 make sure to finalize the zlib stream. Previously, we would write
11867 all the compressed data, but if the last descriptor we wanted to
11868 send was missing or too old, we would not mark the stream as
11869 finished. This caused problems for decompression tools. Fixes bug
11870 11648; bugfix on 0.1.1.23.
11872 o Minor bugfixes (Linux seccomp sandbox):
11873 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
11874 11622; bugfix on 0.2.5.1-alpha.
11875 - Avoid crashing when re-opening listener ports with the seccomp
11876 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
11877 - Avoid crashing with the seccomp sandbox enabled along with
11878 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
11879 - When we receive a SIGHUP with the sandbox enabled, correctly
11880 support rotating our log files. Fixes bug 12032; bugfix
11882 - Avoid crash when running with sandboxing enabled and
11883 DirReqStatistics not disabled. Fixes bug 12035; bugfix
11885 - Fix a "BUG" warning when trying to write bridge-stats files with
11886 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
11888 - Prevent the sandbox from crashing on startup when run with the
11889 --enable-expensive-hardening configuration option. Fixes bug
11890 11477; bugfix on 0.2.5.4-alpha.
11891 - When running with DirPortFrontPage and sandboxing both enabled,
11892 reload the DirPortFrontPage correctly when restarting. Fixes bug
11893 12028; bugfix on 0.2.5.1-alpha.
11894 - Don't try to enable the sandbox when using the Tor binary to check
11895 its configuration, hash a passphrase, or so on. Doing so was
11896 crashing on startup for some users. Fixes bug 11609; bugfix
11898 - Avoid warnings when running with sandboxing and node statistics
11899 enabled at the same time. Fixes part of 12064; bugfix on
11900 0.2.5.1-alpha. Patch from Michael Wolf.
11901 - Avoid warnings when running with sandboxing enabled at the same
11902 time as cookie authentication, hidden services, or directory
11903 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
11904 - Do not allow options that require calls to exec to be enabled
11905 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
11906 bug 12043; bugfix on 0.2.5.1-alpha.
11907 - Handle failures in getpwnam()/getpwuid() when running with the
11908 User option set and the Linux syscall sandbox enabled. Fixes bug
11909 11946; bugfix on 0.2.5.1-alpha.
11910 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
11911 to avoid calling getaddrinfo() after installing the sandbox
11912 filters. Previously, it preloaded a cache with the IPv4 address
11913 for our hostname, and nothing else. Now, it loads the cache with
11914 every address that it used to initialize the Tor process. Fixes
11915 bug 11970; bugfix on 0.2.5.1-alpha.
11917 o Minor bugfixes (pluggable transports):
11918 - Enable the ExtORPortCookieAuthFile option, to allow changing the
11919 default location of the authentication token for the extended OR
11920 Port as used by sever-side pluggable transports. We had
11921 implemented this option before, but the code to make it settable
11922 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
11923 - Avoid another 60-second delay when starting Tor in a pluggable-
11924 transport-using configuration when we already have cached
11925 descriptors for our bridges. Fixes bug 11965; bugfix
11928 o Minor bugfixes (client):
11929 - Avoid "Tried to open a socket with DisableNetwork set" warnings
11930 when starting a client with bridges configured and DisableNetwork
11931 set. (Tor launcher starts Tor with DisableNetwork set the first
11932 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
11934 o Minor bugfixes (testing):
11935 - The Python parts of the test scripts now work on Python 3 as well
11936 as Python 2, so systems where '/usr/bin/python' is Python 3 will
11937 no longer have the tests break. Fixes bug 11608; bugfix
11939 - When looking for versions of python that we could run the tests
11940 with, check for "python2.7" and "python3.3"; previously we were
11941 only looking for "python", "python2", and "python3". Patch from
11942 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
11943 - Fix all valgrind warnings produced by the unit tests. There were
11944 over a thousand memory leak warnings previously, mostly produced
11945 by forgetting to free things in the unit test code. Fixes bug
11946 11618, bugfixes on many versions of Tor.
11948 o Minor bugfixes (tor-fw-helper):
11949 - Give a correct log message when tor-fw-helper fails to launch.
11950 (Previously, we would say something like "tor-fw-helper sent us a
11951 string we could not parse".) Fixes bug 9781; bugfix
11954 o Minor bugfixes (relay, threading):
11955 - Check return code on spawn_func() in cpuworker code, so that we
11956 don't think we've spawned a nonworking cpuworker and write junk to
11957 it forever. Fix related to bug 4345; bugfix on all released Tor
11958 versions. Found by "skruffy".
11959 - Use a pthread_attr to make sure that spawn_func() cannot return an
11960 error while at the same time launching a thread. Fix related to
11961 bug 4345; bugfix on all released Tor versions. Reported
11964 o Minor bugfixes (relay, oom prevention):
11965 - Correctly detect the total available system memory. We tried to do
11966 this in 0.2.5.4-alpha, but the code was set up to always return an
11967 error value, even on success. Fixes bug 11805; bugfix
11970 o Minor bugfixes (relay, other):
11971 - We now drop CREATE cells for already-existent circuit IDs and for
11972 zero-valued circuit IDs, regardless of other factors that might
11973 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
11975 - Avoid an illegal read from stack when initializing the TLS module
11976 using a version of OpenSSL without all of the ciphers used by the
11977 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
11979 - When rejecting DATA cells for stream_id zero, still count them
11980 against the circuit's deliver window so that we don't fail to send
11981 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
11983 o Minor bugfixes (logging):
11984 - Fix a misformatted log message about delayed directory fetches.
11985 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
11986 - Squelch a spurious LD_BUG message "No origin circuit for
11987 successful SOCKS stream" in certain hidden service failure cases;
11991 - Include a tor.service file in contrib/dist for use with systemd.
11992 Some distributions will be able to use this file unmodified;
11993 others will need to tweak it, or write their own. Patch from Jamie
11994 Nguyen; resolves ticket 8368.
11997 - Clean up several option names in the manpage to match their real
11998 names, add the missing documentation for a couple of testing and
11999 directory authority options, remove the documentation for a
12000 V2-directory fetching option that no longer exists. Resolves
12002 - Correct the documentation so that it lists the correct directory
12003 for the stats files. (They are in a subdirectory called "stats",
12005 - In the manpage, move more authority-only options into the
12006 directory authority section so that operators of regular directory
12007 caches don't get confused.
12010 - The contrib directory has been sorted and tidied. Before, it was
12011 an unsorted dumping ground for useful and not-so-useful things.
12012 Now, it is divided based on functionality, and the items which
12013 seemed to be nonfunctional or useless have been removed. Resolves
12014 ticket 8966; based on patches from "rl1987".
12017 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
12018 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
12019 - The TunnelDirConns and PreferTunnelledDirConns options no longer
12020 exist; tunneled directory connections have been available since
12021 0.1.2.5-alpha, and turning them off is not a good idea. This is a
12022 brute-force fix for 10849, where "TunnelDirConns 0" would break
12026 Changes in version 0.2.4.22 - 2014-05-16
12027 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
12028 alpha release series. These include blocking all authority signing
12029 keys that may have been affected by the OpenSSL "heartbleed" bug,
12030 choosing a far more secure set of TLS ciphersuites by default, closing
12031 a couple of memory leaks that could be used to run a target relay out
12032 of RAM, and several others.
12034 o Major features (security, backport from 0.2.5.4-alpha):
12035 - Block authority signing keys that were used on authorities
12036 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
12037 don't have any evidence that these keys _were_ compromised; we're
12038 doing this to be prudent.) Resolves ticket 11464.
12040 o Major bugfixes (security, OOM):
12041 - Fix a memory leak that could occur if a microdescriptor parse
12042 fails during the tokenizing step. This bug could enable a memory
12043 exhaustion attack by directory servers. Fixes bug 11649; bugfix
12046 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
12047 - The relay ciphersuite list is now generated automatically based on
12048 uniform criteria, and includes all OpenSSL ciphersuites with
12049 acceptable strength and forward secrecy. Previously, we had left
12050 some perfectly fine ciphersuites unsupported due to omission or
12051 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
12052 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
12053 - Relays now trust themselves to have a better view than clients of
12054 which TLS ciphersuites are better than others. (Thanks to bug
12055 11513, the relay list is now well-considered, whereas the client
12056 list has been chosen mainly for anti-fingerprinting purposes.)
12057 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
12058 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
12059 AES128. Resolves ticket 11528.
12060 - Clients now try to advertise the same list of ciphersuites as
12061 Firefox 28. This change enables selection of (fast) GCM
12062 ciphersuites, disables some strange old ciphers, and stops
12063 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
12064 Resolves ticket 11438.
12066 o Minor bugfixes (configuration, security):
12067 - When running a hidden service, do not allow TunneledDirConns 0:
12068 trying to set that option together with a hidden service would
12069 otherwise prevent the hidden service from running, and also make
12070 it publish its descriptors directly over HTTP. Fixes bug 10849;
12071 bugfix on 0.2.1.1-alpha.
12073 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
12074 - Avoid sending a garbage value to the controller when a circuit is
12075 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
12077 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
12078 - Stop leaking memory when we successfully resolve a PTR record.
12079 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
12081 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
12082 - Avoid 60-second delays in the bootstrapping process when Tor is
12083 launching for a second time while using bridges. Fixes bug 9229;
12084 bugfix on 0.2.0.3-alpha.
12086 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
12087 - Give the correct URL in the warning message when trying to run a
12088 relay on an ancient version of Windows. Fixes bug 9393.
12090 o Minor bugfixes (compilation):
12091 - Fix a compilation error when compiling with --disable-curve25519.
12092 Fixes bug 9700; bugfix on 0.2.4.17-rc.
12095 - Downgrade the warning severity for the the "md was still
12096 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
12097 for trying to diagnose this bug, and the current warning in
12098 earlier versions of tor achieves nothing useful. Addresses warning
12101 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
12102 - When we run out of usable circuit IDs on a channel, log only one
12103 warning for the whole channel, and describe how many circuits
12104 there were on the channel. Fixes part of ticket 11553.
12106 o Minor features (security, backport from 0.2.5.4-alpha):
12107 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
12108 leave the default at 8GBytes), to better support Raspberry Pi
12109 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
12111 o Documentation (backport from 0.2.5.4-alpha):
12112 - Correctly document that we search for a system torrc file before
12113 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
12117 Changes in version 0.2.5.4-alpha - 2014-04-25
12118 Tor 0.2.5.4-alpha includes several security and performance
12119 improvements for clients and relays, including blacklisting authority
12120 signing keys that were used while susceptible to the OpenSSL
12121 "heartbleed" bug, fixing two expensive functions on busy relays,
12122 improved TLS ciphersuite preference lists, support for run-time
12123 hardening on compilers that support AddressSanitizer, and more work on
12124 the Linux sandbox code.
12126 There are also several usability fixes for clients (especially clients
12127 that use bridges), two new TransPort protocols supported (one on
12128 OpenBSD, one on FreeBSD), and various other bugfixes.
12130 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
12131 have accumulated many known flaws; everyone should upgrade.
12133 o Major features (security):
12134 - If you don't specify MaxMemInQueues yourself, Tor now tries to
12135 pick a good value based on your total system memory. Previously,
12136 the default was always 8 GB. You can still override the default by
12137 setting MaxMemInQueues yourself. Resolves ticket 11396.
12138 - Block authority signing keys that were used on authorities
12139 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
12140 don't have any evidence that these keys _were_ compromised; we're
12141 doing this to be prudent.) Resolves ticket 11464.
12143 o Major features (relay performance):
12144 - Speed up server-side lookups of rendezvous and introduction point
12145 circuits by using hashtables instead of linear searches. These
12146 functions previously accounted between 3 and 7% of CPU usage on
12147 some busy relays. Resolves ticket 9841.
12148 - Avoid wasting CPU when extending a circuit over a channel that is
12149 nearly out of circuit IDs. Previously, we would do a linear scan
12150 over possible circuit IDs before finding one or deciding that we
12151 had exhausted our possibilities. Now, we try at most 64 random
12152 circuit IDs before deciding that we probably won't succeed. Fixes
12153 a possible root cause of ticket 11553.
12155 o Major features (seccomp2 sandbox, Linux only):
12156 - The seccomp2 sandbox can now run a test network for multiple hours
12157 without crashing. The sandbox is still experimental, and more bugs
12158 will probably turn up. To try it, enable "Sandbox 1" on a Linux
12159 host. Resolves ticket 11351.
12160 - Strengthen sandbox code: the sandbox can now test the arguments
12161 for rename(), and blocks _sysctl() entirely. Resolves another part
12163 - When the sandbox blocks a system call, it now tries to log a stack
12164 trace before exiting. Resolves ticket 11465.
12166 o Major bugfixes (TLS cipher selection):
12167 - The relay ciphersuite list is now generated automatically based on
12168 uniform criteria, and includes all OpenSSL ciphersuites with
12169 acceptable strength and forward secrecy. Previously, we had left
12170 some perfectly fine ciphersuites unsupported due to omission or
12171 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
12172 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
12173 - Relays now trust themselves to have a better view than clients of
12174 which TLS ciphersuites are better than others. (Thanks to bug
12175 11513, the relay list is now well-considered, whereas the client
12176 list has been chosen mainly for anti-fingerprinting purposes.)
12177 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
12178 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
12179 AES128. Resolves ticket 11528.
12180 - Clients now try to advertise the same list of ciphersuites as
12181 Firefox 28. This change enables selection of (fast) GCM
12182 ciphersuites, disables some strange old ciphers, and stops
12183 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
12184 Resolves ticket 11438.
12186 o Major bugfixes (bridge client):
12187 - Avoid 60-second delays in the bootstrapping process when Tor is
12188 launching for a second time while using bridges. Fixes bug 9229;
12189 bugfix on 0.2.0.3-alpha.
12191 o Minor features (transparent proxy, *BSD):
12192 - Support FreeBSD's ipfw firewall interface for TransPort ports on
12193 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
12194 10267; patch from "yurivict".
12195 - Support OpenBSD's divert-to rules with the pf firewall for
12196 transparent proxy ports. To enable it, set "TransProxyType
12197 pf-divert". This allows Tor to run a TransPort transparent proxy
12198 port on OpenBSD 4.4 or later without root privileges. See the
12199 pf.conf(5) manual page for information on configuring pf to use
12200 divert-to rules. Closes ticket 10896; patch from Dana Koch.
12202 o Minor features (security):
12203 - New --enable-expensive-hardening option to enable security
12204 hardening options that consume nontrivial amounts of CPU and
12205 memory. Right now, this includes AddressSanitizer and UbSan, which
12206 are supported in newer versions of GCC and Clang. Closes ticket
12209 o Minor features (log verbosity):
12210 - Demote the message that we give when a flushing connection times
12211 out for too long from NOTICE to INFO. It was usually meaningless.
12212 Resolves ticket 5286.
12213 - Don't log so many notice-level bootstrapping messages at startup
12214 about downloading descriptors. Previously, we'd log a notice
12215 whenever we learned about more routers. Now, we only log a notice
12216 at every 5% of progress. Fixes bug 9963.
12217 - Warn less verbosely when receiving a malformed
12218 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
12219 - When we run out of usable circuit IDs on a channel, log only one
12220 warning for the whole channel, and describe how many circuits
12221 there were on the channel. Fixes part of ticket 11553.
12223 o Minor features (relay):
12224 - If a circuit timed out for at least 3 minutes, check if we have a
12225 new external IP address, and publish a new descriptor with the new
12226 IP address if it changed. Resolves ticket 2454.
12228 o Minor features (controller):
12229 - Make the entire exit policy available from the control port via
12230 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
12232 - Because of the fix for ticket 11396, the real limit for memory
12233 usage may no longer match the configured MaxMemInQueues value. The
12234 real limit is now exposed via GETINFO limits/max-mem-in-queues.
12236 o Minor features (bridge client):
12237 - Report a more useful failure message when we can't connect to a
12238 bridge because we don't have the right pluggable transport
12239 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
12241 o Minor features (diagnostic):
12242 - Add more log messages to diagnose bug 7164, which causes
12243 intermittent "microdesc_free() called but md was still referenced"
12244 warnings. We now include more information, to figure out why we
12245 might be cleaning a microdescriptor for being too old if it's
12246 still referenced by a live node_t object.
12248 o Minor bugfixes (client, DNSPort):
12249 - When using DNSPort, try to respond to AAAA requests with AAAA
12250 answers. Previously, we hadn't looked at the request type when
12251 deciding which answer type to prefer. Fixes bug 10468; bugfix on
12253 - When receiving a DNS query for an unsupported record type, reply
12254 with no answer rather than with a NOTIMPL error. This behavior
12255 isn't correct either, but it will break fewer client programs, we
12256 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
12259 o Minor bugfixes (exit relay):
12260 - Stop leaking memory when we successfully resolve a PTR record.
12261 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
12263 o Minor bugfixes (bridge client):
12264 - Stop accepting bridge lines containing hostnames. Doing so would
12265 cause clients to perform DNS requests on the hostnames, which was
12266 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
12267 - Avoid a 60-second delay in the bootstrapping process when a Tor
12268 client with pluggable transports re-reads its configuration at
12269 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
12271 o Minor bugfixes (client, logging during bootstrap):
12272 - Warn only once if we start logging in an unsafe way. Previously,
12273 we complain as many times as we had problems. Fixes bug 9870;
12274 bugfix on 0.2.5.1-alpha.
12275 - Only report the first fatal bootstrap error on a given OR
12276 connection. This stops us from telling the controller bogus error
12277 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
12278 - Be more helpful when trying to run sandboxed on Linux without
12279 libseccomp. Instead of saying "Sandbox is not implemented on this
12280 platform", we now explain that we need to be built with
12281 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
12282 - Avoid generating spurious warnings when starting with
12283 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
12286 o Minor bugfixes (closing OR connections):
12287 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
12288 check if it's an or_connection_t and correctly call
12289 connection_or_close_for_error() rather than
12290 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
12292 - When closing all connections on setting DisableNetwork to 1, use
12293 connection_or_close_normally() rather than closing OR connections
12294 out from under the channel layer. Fixes bug 11306; bugfix on
12297 o Minor bugfixes (controller):
12298 - Avoid sending a garbage value to the controller when a circuit is
12299 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
12301 o Minor bugfixes (tor-fw-helper):
12302 - Allow tor-fw-helper to build again by adding src/ext to its
12303 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
12305 o Minor bugfixes (bridges):
12306 - Avoid potential crashes or bad behavior when launching a
12307 server-side managed proxy with ORPort or ExtORPort temporarily
12308 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
12310 o Minor bugfixes (platform-specific):
12311 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
12312 bug 11426; bugfix on 0.2.5.3-alpha.
12313 - When dumping a malformed directory object to disk, save it in
12314 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
12316 - Don't report failures from make_socket_reuseable() on incoming
12317 sockets on OSX: this can happen when incoming connections close
12318 early. Fixes bug 10081.
12320 o Minor bugfixes (trivial memory leaks):
12321 - Fix a small memory leak when signing a directory object. Fixes bug
12322 11275; bugfix on 0.2.4.13-alpha.
12323 - Free placeholder entries in our circuit table at exit; fixes a
12324 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
12325 - Don't re-initialize a second set of OpenSSL mutexes when starting
12326 up. Previously, we'd make one set of mutexes, and then immediately
12327 replace them with another. Fixes bug 11726; bugfix on
12329 - Resolve some memory leaks found by coverity in the unit tests, on
12330 exit in tor-gencert, and on a failure to compute digests for our
12331 own keys when generating a v3 networkstatus vote. These leaks
12332 should never have affected anyone in practice.
12334 o Minor bugfixes (hidden service):
12335 - Only retry attempts to connect to a chosen rendezvous point 8
12336 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
12338 o Minor bugfixes (misc code correctness):
12339 - Fix various instances of undefined behavior in channeltls.c,
12340 tor_memmem(), and eventdns.c that would cause us to construct
12341 pointers to memory outside an allocated object. (These invalid
12342 pointers were not accessed, but C does not even allow them to
12343 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
12344 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
12345 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
12346 fix some miscellaneous errors in our tests and codebase. Fixes bug
12347 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
12348 - Always check return values for unlink, munmap, UnmapViewOfFile;
12349 check strftime return values more often. In some cases all we can
12350 do is report a warning, but this may help prevent deeper bugs from
12351 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
12353 - Fix numerous warnings from the clang "scan-build" static analyzer.
12354 Some of these are programming style issues; some of them are false
12355 positives that indicated awkward code; some are undefined behavior
12356 cases related to constructing (but not using) invalid pointers;
12357 some are assumptions about API behavior; some are (harmlessly)
12358 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
12359 correct; and one or two are genuine bugs that weren't reachable
12360 from the rest of the program. Fixes bug 8793; bugfixes on many,
12364 - Build the torify.1 manpage again. Previously, we were only trying
12365 to build it when also building tor-fw-helper. That's why we didn't
12366 notice that we'd broken the ability to build it. Fixes bug 11321;
12367 bugfix on 0.2.5.1-alpha.
12368 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
12369 11061; bugfix on 0.2.4.7-alpha.
12370 - Correctly document that we search for a system torrc file before
12371 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
12373 - Resolve warnings from Doxygen.
12375 o Code simplifications and refactoring:
12376 - Remove is_internal_IP() function. Resolves ticket 4645.
12377 - Remove unused function circuit_dump_by_chan from circuitlist.c.
12378 Closes issue 9107; patch from "marek".
12379 - Change our use of the ENUM_BF macro to avoid declarations that
12382 o Deprecated versions:
12383 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
12384 attention for some while. Directory authorities no longer accept
12385 descriptors from relays running any version of Tor prior to Tor
12386 0.2.3.16-alpha. Resolves ticket 11149.
12389 - New macros in test.h to simplify writing mock-functions for unit
12390 tests. Part of ticket 11507. Patch from Dana Koch.
12391 - Complete tests for the status.c module. Resolves ticket 11507.
12392 Patch from Dana Koch.
12395 - Remove all code for the long unused v1 directory protocol.
12396 Resolves ticket 11070.
12399 Changes in version 0.2.5.3-alpha - 2014-03-22
12400 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
12401 two new anti-DoS features for Tor relays, resolves a bug that kept
12402 SOCKS5 support for IPv6 from working, fixes several annoying usability
12403 issues for bridge users, and removes more old code for unused
12406 The Tor 0.2.5.x release series is now in patch-freeze: no feature
12407 patches not already written will be considered for inclusion in 0.2.5.x.
12409 o Major features (relay security, DoS-resistance):
12410 - When deciding whether we have run out of memory and we need to
12411 close circuits, also consider memory allocated in buffers for
12412 streams attached to each circuit.
12414 This change, which extends an anti-DoS feature introduced in
12415 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
12416 better resist more memory-based DoS attacks than before. Since the
12417 MaxMemInCellQueues option now applies to all queues, it is renamed
12418 to MaxMemInQueues. This feature fixes bug 10169.
12419 - Avoid hash-flooding denial-of-service attacks by using the secure
12420 SipHash-2-4 hash function for our hashtables. Without this
12421 feature, an attacker could degrade performance of a targeted
12422 client or server by flooding their data structures with a large
12423 number of entries to be stored at the same hash table position,
12424 thereby slowing down the Tor instance. With this feature, hash
12425 table positions are derived from a randomized cryptographic key,
12426 and an attacker cannot predict which entries will collide. Closes
12428 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
12429 the default at 8GBytes), to better support Raspberry Pi users. Fixes
12430 bug 9686; bugfix on 0.2.4.14-alpha.
12432 o Minor features (bridges, pluggable transports):
12433 - Bridges now write the SHA1 digest of their identity key
12434 fingerprint (that is, a hash of a hash of their public key) to
12435 notice-level logs, and to a new hashed-fingerprint file. This
12436 information will help bridge operators look up their bridge in
12437 Globe and similar tools. Resolves ticket 10884.
12438 - Improve the message that Tor displays when running as a bridge
12439 using pluggable transports without an Extended ORPort listener.
12440 Also, log the message in the log file too. Resolves ticket 11043.
12442 o Minor features (other):
12443 - Add a new option, PredictedPortsRelevanceTime, to control how long
12444 after having received a request to connect to a given port Tor
12445 will try to keep circuits ready in anticipation of future requests
12446 for that port. Patch from "unixninja92"; implements ticket 9176.
12447 - Generate a warning if any ports are listed in the SocksPolicy,
12448 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
12449 AuthDirBadExit options. (These options only support address
12450 ranges.) Fixes part of ticket 11108.
12451 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
12454 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
12455 - Build without warnings under clang 3.4. (We have some macros that
12456 define static functions only some of which will get used later in
12457 the module. Starting with clang 3.4, these give a warning unless the
12458 unused attribute is set on them.) Resolves ticket 10904.
12459 - Fix build warnings about missing "a2x" comment when building the
12460 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
12461 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
12463 o Minor bugfixes (client):
12464 - Improve the log message when we can't connect to a hidden service
12465 because all of the hidden service directory nodes hosting its
12466 descriptor are excluded. Improves on our fix for bug 10722, which
12467 was a bugfix on 0.2.0.10-alpha.
12468 - Raise a control port warning when we fail to connect to all of
12469 our bridges. Previously, we didn't inform the controller, and
12470 the bootstrap process would stall. Fixes bug 11069; bugfix on
12472 - Exit immediately when a process-owning controller exits.
12473 Previously, tor relays would wait for a little while after their
12474 controller exited, as if they had gotten an INT signal -- but this
12475 was problematic, since there was no feedback for the user. To do a
12476 clean shutdown, controllers should send an INT signal and give Tor
12477 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
12478 - Stop attempting to connect to bridges before our pluggable
12479 transports are configured (harmless but resulted in some erroneous
12480 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
12481 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
12482 generating incorrect SOCKS5 responses, and confusing client
12483 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
12485 o Minor bugfixes (relays and bridges):
12486 - Avoid crashing on a malformed resolv.conf file when running a
12487 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
12488 - Non-exit relays no longer launch mock DNS requests to check for
12489 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
12490 non-exit relays stopped servicing DNS requests. Fixes bug 965;
12491 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
12492 - Bridges now report complete directory request statistics. Related
12493 to bug 5824; bugfix on 0.2.2.1-alpha.
12494 - Bridges now never collect statistics that were designed for
12495 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
12496 - Stop giving annoying warning messages when we decide not to launch
12497 a pluggable transport proxy that we don't need (because there are
12498 no bridges configured to use it). Resolves ticket 5018; bugfix
12500 - Give the correct URL in the warning message when trying to run a
12501 relay on an ancient version of Windows. Fixes bug 9393.
12503 o Minor bugfixes (backtrace support):
12504 - Support automatic backtraces on more platforms by using the
12505 "-fasynchronous-unwind-tables" compiler option. This option is
12506 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
12507 is on by default and table generation is not. This doesn't yet
12508 add Windows support; only Linux, OSX, and some BSDs are affected.
12509 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
12510 - Avoid strange behavior if two threads hit failed assertions at the
12511 same time and both try to log backtraces at once. (Previously, if
12512 this had happened, both threads would have stored their intermediate
12513 results in the same buffer, and generated junk outputs.) Reported by
12514 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
12515 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
12516 0.2.5.2-alpha; patch from Nick Hopper.
12518 o Minor bugfixes (unit tests):
12519 - Fix a small bug in the unit tests that might have made the tests
12520 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
12521 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
12524 - Remove all remaining code related to version-0 hidden service
12525 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
12526 the rest of bug 10841.
12529 - Document in the manpage that "KBytes" may also be written as
12530 "kilobytes" or "KB", that "Kbits" may also be written as
12531 "kilobits", and so forth. Closes ticket 9222.
12532 - Document that the ClientOnly config option overrides ORPort.
12533 Our old explanation made ClientOnly sound as though it did
12534 nothing at all. Resolves bug 9059.
12535 - Explain that SocksPolicy, DirPolicy, and similar options don't
12536 take port arguments. Fixes the other part of ticket 11108.
12537 - Fix a comment about the rend_server_descriptor_t.protocols field
12538 to more accurately describe its range. Also, make that field
12539 unsigned, to more accurately reflect its usage. Fixes bug 9099;
12540 bugfix on 0.2.1.5-alpha.
12541 - Fix the manpage's description of HiddenServiceAuthorizeClient:
12542 the maximum client name length is 16, not 19. Fixes bug 11118;
12543 bugfix on 0.2.1.6-alpha.
12545 o Code simplifications and refactoring:
12546 - Get rid of router->address, since in all cases it was just the
12547 string representation of router->addr. Resolves ticket 5528.
12549 o Test infrastructure:
12550 - Update to the latest version of tinytest.
12551 - Improve the tinytest implementation of string operation tests so
12552 that comparisons with NULL strings no longer crash the tests; they
12553 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
12556 Changes in version 0.2.4.21 - 2014-02-28
12557 Tor 0.2.4.21 further improves security against potential adversaries who
12558 find breaking 1024-bit crypto doable, and backports several stability
12559 and robustness patches from the 0.2.5 branch.
12561 o Major features (client security):
12562 - When we choose a path for a 3-hop circuit, make sure it contains
12563 at least one relay that supports the NTor circuit extension
12564 handshake. Otherwise, there is a chance that we're building
12565 a circuit that's worth attacking by an adversary who finds
12566 breaking 1024-bit crypto doable, and that chance changes the game
12567 theory. Implements ticket 9777.
12570 - Do not treat streams that fail with reason
12571 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
12572 since it could also indicate an ENETUNREACH connection error. Fixes
12573 part of bug 10777; bugfix on 0.2.4.8-alpha.
12575 o Code simplification and refactoring:
12576 - Remove data structures which were introduced to implement the
12577 CellStatistics option: they are now redundant with the new timestamp
12578 field in the regular packed_cell_t data structure, which we did
12579 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
12582 - Always clear OpenSSL bignums before freeing them -- even bignums
12583 that don't contain secrets. Resolves ticket 10793. Patch by
12585 - Build without warnings under clang 3.4. (We have some macros that
12586 define static functions only some of which will get used later in
12587 the module. Starting with clang 3.4, these give a warning unless the
12588 unused attribute is set on them.) Resolves ticket 10904.
12589 - Update geoip and geoip6 files to the February 7 2014 Maxmind
12590 GeoLite2 Country database.
12593 - Set the listen() backlog limit to the largest actually supported
12594 on the system, not to the value in a header file. Fixes bug 9716;
12595 bugfix on every released Tor.
12596 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
12597 exit node as a NOROUTE error, not an INTERNAL error, since they
12598 can apparently happen when trying to connect to the wrong sort
12599 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
12600 - Fix build warnings about missing "a2x" comment when building the
12601 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
12602 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
12603 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
12604 not entirely remove it from the connection lists. Fixes bug 9602;
12605 bugfix on 0.2.4.4-alpha.
12606 - Fix a segmentation fault in our benchmark code when running with
12607 Fedora's OpenSSL package, or any other OpenSSL that provides
12608 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
12609 - Turn "circuit handshake stats since last time" log messages into a
12610 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
12612 o Documentation fixes:
12613 - Document that all but one DirPort entry must have the NoAdvertise
12614 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
12617 Changes in version 0.2.5.2-alpha - 2014-02-13
12618 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
12619 like the "poor random number generation" fix and the "building too many
12620 circuits" fix. It also further improves security against potential
12621 adversaries who find breaking 1024-bit crypto doable, and launches
12622 pluggable transports on demand (which gets us closer to integrating
12623 pluggable transport support by default -- not to be confused with Tor
12624 bundles enabling pluggable transports and bridges by default).
12626 o Major features (client security):
12627 - When we choose a path for a 3-hop circuit, make sure it contains
12628 at least one relay that supports the NTor circuit extension
12629 handshake. Otherwise, there is a chance that we're building
12630 a circuit that's worth attacking by an adversary who finds
12631 breaking 1024-bit crypto doable, and that chance changes the game
12632 theory. Implements ticket 9777.
12633 - Clients now look at the "usecreatefast" consensus parameter to
12634 decide whether to use CREATE_FAST or CREATE cells for the first hop
12635 of their circuit. This approach can improve security on connections
12636 where Tor's circuit handshake is stronger than the available TLS
12637 connection security levels, but the tradeoff is more computational
12638 load on guard relays. Implements proposal 221. Resolves ticket 9386.
12640 o Major features (bridges):
12641 - Don't launch pluggable transport proxies if we don't have any
12642 bridges configured that would use them. Now we can list many
12643 pluggable transports, and Tor will dynamically start one when it
12644 hears a bridge address that needs it. Resolves ticket 5018.
12645 - The bridge directory authority now assigns status flags (Stable,
12646 Guard, etc) to bridges based on thresholds calculated over all
12647 Running bridges. Now bridgedb can finally make use of its features
12648 to e.g. include at least one Stable bridge in its answers. Fixes
12651 o Major features (other):
12652 - Extend ORCONN controller event to include an "ID" parameter,
12653 and add four new controller event types CONN_BW, CIRC_BW,
12654 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
12655 The new events are emitted in private Tor networks only, with the
12656 goal of being able to better track performance and load during
12657 full-network simulations. Implements proposal 218 and ticket 7359.
12658 - On some platforms (currently: recent OSX versions, glibc-based
12659 platforms that support the ELF format, and a few other
12660 Unix-like operating systems), Tor can now dump stack traces
12661 when a crash occurs or an assertion fails. By default, traces
12662 are dumped to stderr (if possible) and to any logs that are
12663 reporting errors. Implements ticket 9299.
12666 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
12667 not entirely remove it from the connection lists. Fixes bug 9602;
12668 bugfix on 0.2.4.4-alpha.
12669 - Do not treat streams that fail with reason
12670 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
12671 since it could also indicate an ENETUNREACH connection error. Fixes
12672 part of bug 10777; bugfix on 0.2.4.8-alpha.
12674 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
12675 - Do not allow OpenSSL engines to replace the PRNG, even when
12676 HardwareAccel is set. The only default builtin PRNG engine uses
12677 the Intel RDRAND instruction to replace the entire PRNG, and
12678 ignores all attempts to seed it with more entropy. That's
12679 cryptographically stupid: the right response to a new alleged
12680 entropy source is never to discard all previously used entropy
12681 sources. Fixes bug 10402; works around behavior introduced in
12682 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
12684 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
12685 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
12686 - Avoid launching spurious extra circuits when a stream is pending.
12687 This fixes a bug where any circuit that _wasn't_ unusable for new
12688 streams would be treated as if it were, causing extra circuits to
12689 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
12691 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12692 - No longer stop reading or writing on cpuworker connections when
12693 our rate limiting buckets go empty. Now we should handle circuit
12694 handshake requests more promptly. Resolves bug 9731.
12695 - Stop trying to bootstrap all our directory information from
12696 only our first guard. Discovered while fixing bug 9946; bugfix
12699 o Minor features (bridges, pluggable transports):
12700 - Add threshold cutoffs to the networkstatus document created by
12701 the Bridge Authority. Fixes bug 1117.
12702 - On Windows, spawn background processes using the CREATE_NO_WINDOW
12703 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
12704 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
12705 Vidalia set this option for us.) Implements ticket 10297.
12707 o Minor features (security):
12708 - Always clear OpenSSL bignums before freeing them -- even bignums
12709 that don't contain secrets. Resolves ticket 10793. Patch by
12712 o Minor features (config options and command line):
12713 - Add an --allow-missing-torrc commandline option that tells Tor to
12714 run even if the configuration file specified by -f is not available.
12715 Implements ticket 10060.
12716 - Add support for the TPROXY transparent proxying facility on Linux.
12717 See documentation for the new TransProxyType option for more
12718 details. Implementation by "thomo". Closes ticket 10582.
12720 o Minor features (controller):
12721 - Add a new "HS_DESC" controller event that reports activities
12722 related to hidden service descriptors. Resolves ticket 8510.
12723 - New "DROPGUARDS" controller command to forget all current entry
12724 guards. Not recommended for ordinary use, since replacing guards
12725 too frequently makes several attacks easier. Resolves ticket 9934;
12728 o Minor features (build):
12729 - Assume that a user using ./configure --host wants to cross-compile,
12730 and give an error if we cannot find a properly named
12731 tool-chain. Add a --disable-tool-name-check option to proceed
12732 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
12733 - If we run ./configure and the compiler recognizes -fstack-protector
12734 but the linker rejects it, warn the user about a potentially missing
12735 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
12737 o Minor features (testing):
12738 - If Python is installed, "make check" now runs extra tests beyond
12739 the unit test scripts.
12740 - When bootstrapping a test network, sometimes very few relays get
12741 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
12742 specify a set of relays which should be voted Guard regardless of
12743 their uptime or bandwidth. Addresses ticket 9206.
12745 o Minor features (log messages):
12746 - When ServerTransportPlugin is set on a bridge, Tor can write more
12747 useful statistics about bridge use in its extrainfo descriptors,
12748 but only if the Extended ORPort ("ExtORPort") is set too. Add a
12749 log message to inform the user in this case. Resolves ticket 9651.
12750 - When receiving a new controller connection, log the origin address.
12751 Resolves ticket 9698; patch from "sigpipe".
12752 - When logging OpenSSL engine status at startup, log the status of
12753 more engines. Fixes ticket 10043; patch from Joshua Datko.
12754 - Turn "circuit handshake stats since last time" log messages into a
12755 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
12757 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12758 - Improve the circuit queue out-of-memory handler. Previously, when
12759 we ran low on memory, we'd close whichever circuits had the most
12760 queued cells. Now, we close those that have the *oldest* queued
12761 cells, on the theory that those are most responsible for us
12762 running low on memory. Based on analysis from a forthcoming paper
12763 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
12764 - Generate bootstrapping status update events correctly when fetching
12765 microdescriptors. Fixes bug 9927.
12766 - Update to the October 2 2013 Maxmind GeoLite Country database.
12768 o Minor bugfixes (clients):
12769 - When closing a channel that has already been open, do not close
12770 pending circuits that were waiting to connect to the same relay.
12771 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
12774 o Minor bugfixes (relays):
12775 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
12776 exit node as a NOROUTE error, not an INTERNAL error, since they
12777 can apparently happen when trying to connect to the wrong sort
12778 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
12780 o Minor bugfixes (bridges):
12781 - Fix a bug where the first connection works to a bridge that uses a
12782 pluggable transport with client-side parameters, but we don't send
12783 the client-side parameters on subsequent connections. (We don't
12784 use any pluggable transports with client-side parameters yet,
12785 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
12786 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
12788 o Minor bugfixes (node selection):
12789 - If ExcludeNodes is set, consider non-excluded hidden service
12790 directory servers before excluded ones. Do not consider excluded
12791 hidden service directory servers at all if StrictNodes is
12792 set. (Previously, we would sometimes decide to connect to those
12793 servers, and then realize before we initiated a connection that
12794 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
12795 Reported by "mr-4".
12796 - If we set the ExitNodes option but it doesn't include any nodes
12797 that have the Exit flag, we would choose not to bootstrap. Now we
12798 bootstrap so long as ExitNodes includes nodes which can exit to
12799 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
12801 o Minor bugfixes (controller and command-line):
12802 - If changing a config option via "setconf" fails in a recoverable
12803 way, we used to nonetheless write our new control ports to the
12804 file described by the "ControlPortWriteToFile" option. Now we only
12805 write out that file if we successfully switch to the new config
12806 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
12807 - When a command-line option such as --version or --help that
12808 ordinarily implies --hush appears on the command line along with
12809 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
12810 only if it appeared later on the command line. Fixes bug 9578;
12811 bugfix on 0.2.5.1-alpha.
12813 o Minor bugfixes (code correctness):
12814 - Previously we used two temporary files when writing descriptors to
12815 disk; now we only use one. Fixes bug 1376.
12816 - Remove an erroneous (but impossible and thus harmless) pointer
12817 comparison that would have allowed compilers to skip a bounds
12818 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
12819 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
12820 - Fix an always-true assertion in pluggable transports code so it
12821 actually checks what it was trying to check. Fixes bug 10046;
12822 bugfix on 0.2.3.9-alpha. Found by "dcb".
12824 o Minor bugfixes (protocol correctness):
12825 - When receiving a VERSIONS cell with an odd number of bytes, close
12826 the connection immediately since the cell is malformed. Fixes bug
12827 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
12830 o Minor bugfixes (build):
12831 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
12832 turned off (that is, without support for v2 link handshakes). Fixes
12833 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
12834 - Fix compilation warnings and startup issues when running with
12835 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
12837 - Fix compilation on Solaris 9, which didn't like us having an
12838 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
12840 o Minor bugfixes (testing):
12841 - Fix a segmentation fault in our benchmark code when running with
12842 Fedora's OpenSSL package, or any other OpenSSL that provides
12843 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
12845 o Minor bugfixes (log messages):
12846 - Fix a bug where clients using bridges would report themselves
12847 as 50% bootstrapped even without a live consensus document.
12848 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
12849 - Suppress a warning where, if there's only one directory authority
12850 in the network, we would complain that votes and signatures cannot
12851 be uploaded to other directory authorities. Fixes bug 10842;
12852 bugfix on 0.2.2.26-beta.
12853 - Report bootstrapping progress correctly when we're downloading
12854 microdescriptors. We had updated our "do we have enough microdescs
12855 to begin building circuits?" logic most recently in 0.2.4.10-alpha
12856 (see bug 5956), but we left the bootstrap status event logic at
12857 "how far through getting 1/4 of them are we?" Fixes bug 9958;
12858 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
12860 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
12861 - Avoid a crash bug when starting with a corrupted microdescriptor
12862 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
12863 - If we fail to dump a previously cached microdescriptor to disk, avoid
12864 freeing duplicate data later on. Fixes bug 10423; bugfix on
12865 0.2.4.13-alpha. Spotted by "bobnomnom".
12867 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12868 - Correctly log long IPv6 exit policies, instead of truncating them
12869 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
12870 - Our default TLS ecdhe groups were backwards: we meant to be using
12871 P224 for relays (for performance win) and P256 for bridges (since
12872 it is more common in the wild). Instead we had it backwards. After
12873 reconsideration, we decided that the default should be P256 on all
12874 hosts, since its security is probably better, and since P224 is
12875 reportedly used quite little in the wild. Found by "skruffy" on
12876 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
12877 - Free directory authority certificate download statuses on exit
12878 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
12880 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12881 - If the guard we choose first doesn't answer, we would try the
12882 second guard, but once we connected to the second guard we would
12883 abandon it and retry the first one, slowing down bootstrapping.
12884 The fix is to treat all our initially chosen guards as acceptable
12885 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
12886 - Fix an assertion failure that would occur when disabling the
12887 ORPort setting on a running Tor process while accounting was
12888 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
12889 - When examining the list of network interfaces to find our address,
12890 do not consider non-running or disabled network interfaces. Fixes
12891 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
12892 - Avoid an off-by-one error when checking buffer boundaries when
12893 formatting the exit status of a pluggable transport helper.
12894 This is probably not an exploitable bug, but better safe than
12895 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
12898 o Removed code and features:
12899 - Clients now reject any directory authority certificates lacking
12900 a dir-key-crosscert element. These have been included since
12901 0.2.1.9-alpha, so there's no real reason for them to be optional
12902 any longer. Completes proposal 157. Resolves ticket 10162.
12903 - Remove all code that existed to support the v2 directory system,
12904 since there are no longer any v2 directory authorities. Resolves
12906 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
12907 options, which were used for designating authorities as "Hidden
12908 service authorities". There has been no use of hidden service
12909 authorities since 0.2.2.1-alpha, when we stopped uploading or
12910 downloading v0 hidden service descriptors. Fixes bug 10881; also
12911 part of a fix for bug 10841.
12913 o Code simplification and refactoring:
12914 - Remove some old fallback code designed to keep Tor clients working
12915 in a network with only two working relays. Elsewhere in the code we
12916 have long since stopped supporting such networks, so there wasn't
12917 much point in keeping it around. Addresses ticket 9926.
12918 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
12919 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
12920 - Remove data structures which were introduced to implement the
12921 CellStatistics option: they are now redundant with the addition
12922 of a timestamp to the regular packed_cell_t data structure, which
12923 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
12926 o Documentation (man page) fixes:
12927 - Update manpage to describe some of the files you can expect to
12928 find in Tor's DataDirectory. Addresses ticket 9839.
12929 - Document that all but one DirPort entry must have the NoAdvertise
12930 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
12932 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
12933 - Clarify the usage and risks of setting the ContactInfo torrc line
12934 for your relay or bridge. Resolves ticket 9854.
12935 - Add anchors to the manpage so we can link to the html version of
12936 the documentation for specific options. Resolves ticket 9866.
12937 - Replace remaining references to DirServer in man page and
12938 log entries. Resolves ticket 10124.
12941 - Make the "tor-gencert" tool used by directory authority operators
12942 create 2048-bit signing keys by default (rather than 1024-bit, since
12943 1024-bit is uncomfortably small these days). Addresses ticket 10324.
12946 Changes in version 0.2.4.20 - 2013-12-22
12947 Tor 0.2.4.20 fixes potentially poor random number generation for users
12948 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
12949 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
12950 and 4) have no state file in their DataDirectory (as would happen on
12951 first start). Users who generated relay or hidden service identity
12952 keys in such a situation should discard them and generate new ones.
12954 This release also fixes a logic error that caused Tor clients to build
12955 many more preemptive circuits than they actually need.
12958 - Do not allow OpenSSL engines to replace the PRNG, even when
12959 HardwareAccel is set. The only default builtin PRNG engine uses
12960 the Intel RDRAND instruction to replace the entire PRNG, and
12961 ignores all attempts to seed it with more entropy. That's
12962 cryptographically stupid: the right response to a new alleged
12963 entropy source is never to discard all previously used entropy
12964 sources. Fixes bug 10402; works around behavior introduced in
12965 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
12967 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
12968 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
12969 - Avoid launching spurious extra circuits when a stream is pending.
12970 This fixes a bug where any circuit that _wasn't_ unusable for new
12971 streams would be treated as if it were, causing extra circuits to
12972 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
12975 - Avoid a crash bug when starting with a corrupted microdescriptor
12976 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
12977 - If we fail to dump a previously cached microdescriptor to disk, avoid
12978 freeing duplicate data later on. Fixes bug 10423; bugfix on
12979 0.2.4.13-alpha. Spotted by "bobnomnom".
12982 Changes in version 0.2.4.19 - 2013-12-11
12983 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
12984 (1986-2013). Aaron worked on diverse projects including helping to guide
12985 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
12986 transparency to the U.S government's PACER documents, and contributing
12987 design and development for Tor and Tor2Web. Aaron was one of the latest
12988 martyrs in our collective fight for civil liberties and human rights,
12989 and his death is all the more painful because he was one of us.
12991 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
12992 a new circuit handshake and link encryption that use ECC to provide
12993 better security and efficiency; makes relays better manage circuit
12994 creation requests; uses "directory guards" to reduce client enumeration
12995 risks; makes bridges collect and report statistics about the pluggable
12996 transports they support; cleans up and improves our geoip database;
12997 gets much closer to IPv6 support for clients, bridges, and relays; makes
12998 directory authorities use measured bandwidths rather than advertised
12999 ones when computing flags and thresholds; disables client-side DNS
13000 caching to reduce tracking risks; and fixes a big bug in bridge
13001 reachability testing. This release introduces two new design
13002 abstractions in the code: a new "channel" abstraction between circuits
13003 and or_connections to allow for implementing alternate relay-to-relay
13004 transports, and a new "circuitmux" abstraction storing the queue of
13005 circuits for a channel. The release also includes many stability,
13006 security, and privacy fixes.
13009 Changes in version 0.2.4.18-rc - 2013-11-16
13010 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
13011 series. It takes a variety of fixes from the 0.2.5.x branch to improve
13012 stability, performance, and better handling of edge cases.
13015 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
13016 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
13017 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
13018 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
13019 them to solve bug 6033.)
13022 - No longer stop reading or writing on cpuworker connections when
13023 our rate limiting buckets go empty. Now we should handle circuit
13024 handshake requests more promptly. Resolves bug 9731.
13025 - If we are unable to save a microdescriptor to the journal, do not
13026 drop it from memory and then reattempt downloading it. Fixes bug
13027 9645; bugfix on 0.2.2.6-alpha.
13028 - Stop trying to bootstrap all our directory information from
13029 only our first guard. Discovered while fixing bug 9946; bugfix
13031 - The new channel code sometimes lost track of in-progress circuits,
13032 causing long-running clients to stop building new circuits. The
13033 fix is to always call circuit_n_chan_done(chan, 0) from
13034 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
13036 o Minor bugfixes (on 0.2.4.x):
13037 - Correctly log long IPv6 exit policies, instead of truncating them
13038 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
13039 - Our default TLS ecdhe groups were backwards: we meant to be using
13040 P224 for relays (for performance win) and P256 for bridges (since
13041 it is more common in the wild). Instead we had it backwards. After
13042 reconsideration, we decided that the default should be P256 on all
13043 hosts, since its security is probably better, and since P224 is
13044 reportedly used quite little in the wild. Found by "skruffy" on
13045 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
13046 - Free directory authority certificate download statuses on exit
13047 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
13049 o Minor bugfixes (on 0.2.3.x and earlier):
13050 - If the guard we choose first doesn't answer, we would try the
13051 second guard, but once we connected to the second guard we would
13052 abandon it and retry the first one, slowing down bootstrapping.
13053 The fix is to treat all our initially chosen guards as acceptable
13054 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
13055 - Fix an assertion failure that would occur when disabling the
13056 ORPort setting on a running Tor process while accounting was
13057 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
13058 - When examining the list of network interfaces to find our address,
13059 do not consider non-running or disabled network interfaces. Fixes
13060 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
13061 - Avoid an off-by-one error when checking buffer boundaries when
13062 formatting the exit status of a pluggable transport helper.
13063 This is probably not an exploitable bug, but better safe than
13064 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
13067 o Minor features (protecting client timestamps):
13068 - Clients no longer send timestamps in their NETINFO cells. These were
13069 not used for anything, and they provided one small way for clients
13070 to be distinguished from each other as they moved from network to
13071 network or behind NAT. Implements part of proposal 222.
13072 - Clients now round timestamps in INTRODUCE cells down to the nearest
13073 10 minutes. If a new Support022HiddenServices option is set to 0, or
13074 if it's set to "auto" and the feature is disabled in the consensus,
13075 the timestamp is sent as 0 instead. Implements part of proposal 222.
13076 - Stop sending timestamps in AUTHENTICATE cells. This is not such
13077 a big deal from a security point of view, but it achieves no actual
13078 good purpose, and isn't needed. Implements part of proposal 222.
13079 - Reduce down accuracy of timestamps in hidden service descriptors.
13080 Implements part of proposal 222.
13082 o Minor features (other):
13083 - Improve the circuit queue out-of-memory handler. Previously, when
13084 we ran low on memory, we'd close whichever circuits had the most
13085 queued cells. Now, we close those that have the *oldest* queued
13086 cells, on the theory that those are most responsible for us
13087 running low on memory. Based on analysis from a forthcoming paper
13088 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
13089 - Generate bootstrapping status update events correctly when fetching
13090 microdescriptors. Fixes bug 9927.
13091 - Update to the October 2 2013 Maxmind GeoLite Country database.
13093 o Documentation fixes:
13094 - Clarify the usage and risks of setting the ContactInfo torrc line
13095 for your relay or bridge. Resolves ticket 9854.
13096 - Add anchors to the manpage so we can link to the html version of
13097 the documentation for specific options. Resolves ticket 9866.
13098 - Replace remaining references to DirServer in man page and
13099 log entries. Resolves ticket 10124.
13102 Changes in version 0.2.5.1-alpha - 2013-10-02
13103 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
13104 on Linux, allows bridges that offer pluggable transports to report usage
13105 statistics, fixes many issues to make testing easier, and provides
13106 a pile of minor features and bugfixes that have been waiting for a
13107 release of the new branch.
13109 This is the first alpha release in a new series, so expect there to
13110 be bugs. Users who would rather test out a more stable branch should
13111 stay with 0.2.4.x for now.
13113 o Major features (security):
13114 - Use the seccomp2 syscall filtering facility on Linux to limit
13115 which system calls Tor can invoke. This is an experimental,
13116 Linux-only feature to provide defense-in-depth against unknown
13117 attacks. To try turning it on, set "Sandbox 1" in your torrc
13118 file. Please be ready to report bugs. We hope to add support
13119 for better sandboxing in the future, including more fine-grained
13120 filters, better division of responsibility, and support for more
13121 platforms. This work has been done by Cristian-Matei Toader for
13122 Google Summer of Code.
13123 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
13124 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
13125 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
13126 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
13127 them to solve bug 6033.)
13129 o Major features (other):
13130 - Add support for passing arguments to managed pluggable transport
13131 proxies. Implements ticket 3594.
13132 - Bridges now track GeoIP information and the number of their users
13133 even when pluggable transports are in use, and report usage
13134 statistics in their extra-info descriptors. Resolves tickets 4773
13136 - Make testing Tor networks bootstrap better: lower directory fetch
13137 retry schedules and maximum interval without directory requests,
13138 and raise maximum download tries. Implements ticket 6752.
13139 - Add make target 'test-network' to run tests on a Chutney network.
13140 Implements ticket 8530.
13141 - The ntor handshake is now on-by-default, no matter what the
13142 directory authorities recommend. Implements ticket 8561.
13145 - Instead of writing destroy cells directly to outgoing connection
13146 buffers, queue them and intersperse them with other outgoing cells.
13147 This can prevent a set of resource starvation conditions where too
13148 many pending destroy cells prevent data cells from actually getting
13149 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
13150 bugfix on 0.2.0.1-alpha.
13151 - If we are unable to save a microdescriptor to the journal, do not
13152 drop it from memory and then reattempt downloading it. Fixes bug
13153 9645; bugfix on 0.2.2.6-alpha.
13154 - The new channel code sometimes lost track of in-progress circuits,
13155 causing long-running clients to stop building new circuits. The
13156 fix is to always call circuit_n_chan_done(chan, 0) from
13157 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
13160 - Tor now builds each source file in two modes: a mode that avoids
13161 exposing identifiers needlessly, and another mode that exposes
13162 more identifiers for testing. This lets the compiler do better at
13163 optimizing the production code, while enabling us to take more
13164 radical measures to let the unit tests test things.
13165 - The production builds no longer include functions used only in
13166 the unit tests; all functions exposed from a module only for
13167 unit-testing are now static in production builds.
13168 - Add an --enable-coverage configuration option to make the unit
13169 tests (and a new src/or/tor-cov target) to build with gcov test
13173 - We now have rudimentary function mocking support that our unit
13174 tests can use to test functions in isolation. Function mocking
13175 lets the tests temporarily replace a function's dependencies with
13176 stub functions, so that the tests can check the function without
13177 invoking the other functions it calls.
13178 - Add more unit tests for the <circid,channel>->circuit map, and
13179 the destroy-cell-tracking code to fix bug 7912.
13180 - Unit tests for failing cases of the TAP onion handshake.
13181 - More unit tests for address-manipulation functions.
13183 o Minor features (protecting client timestamps):
13184 - Clients no longer send timestamps in their NETINFO cells. These were
13185 not used for anything, and they provided one small way for clients
13186 to be distinguished from each other as they moved from network to
13187 network or behind NAT. Implements part of proposal 222.
13188 - Clients now round timestamps in INTRODUCE cells down to the nearest
13189 10 minutes. If a new Support022HiddenServices option is set to 0, or
13190 if it's set to "auto" and the feature is disabled in the consensus,
13191 the timestamp is sent as 0 instead. Implements part of proposal 222.
13192 - Stop sending timestamps in AUTHENTICATE cells. This is not such
13193 a big deal from a security point of view, but it achieves no actual
13194 good purpose, and isn't needed. Implements part of proposal 222.
13195 - Reduce down accuracy of timestamps in hidden service descriptors.
13196 Implements part of proposal 222.
13198 o Minor features (config options):
13199 - Config (torrc) lines now handle fingerprints which are missing
13200 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
13201 - Support a --dump-config option to print some or all of the
13202 configured options. Mainly useful for debugging the command-line
13203 option parsing code. Helps resolve ticket 4647.
13204 - Raise awareness of safer logging: notify user of potentially
13205 unsafe config options, like logging more verbosely than severity
13206 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
13207 - Add a new configuration option TestingV3AuthVotingStartOffset
13208 that bootstraps a network faster by changing the timing for
13209 consensus votes. Addresses ticket 8532.
13210 - Add a new torrc option "ServerTransportOptions" that allows
13211 bridge operators to pass configuration parameters to their
13212 pluggable transports. Resolves ticket 8929.
13213 - The config (torrc) file now accepts bandwidth and space limits in
13214 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
13215 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
13218 o Minor features (build):
13219 - Add support for `--library-versions` flag. Implements ticket 6384.
13220 - Return the "unexpected sendme" warnings to a warn severity, but make
13221 them rate limited, to help diagnose ticket 8093.
13222 - Detect a missing asciidoc, and warn the user about it, during
13223 configure rather than at build time. Fixes issue 6506. Patch from
13226 o Minor features (other):
13227 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
13228 sockets in a single system call. Implements ticket 5129.
13229 - Log current accounting state (bytes sent and received + remaining
13230 time for the current accounting period) in the relay's heartbeat
13231 message. Implements ticket 5526; patch from Peter Retzlaff.
13232 - Implement the TRANSPORT_LAUNCHED control port event that
13233 notifies controllers about new launched pluggable
13234 transports. Resolves ticket 5609.
13235 - If we're using the pure-C 32-bit curve25519_donna implementation
13236 of curve25519, build it with the -fomit-frame-pointer option to
13237 make it go faster on register-starved hosts. This improves our
13238 handshake performance by about 6% on i386 hosts without nacl.
13239 Closes ticket 8109.
13240 - Update to the September 4 2013 Maxmind GeoLite Country database.
13243 - Set the listen() backlog limit to the largest actually supported
13244 on the system, not to the value in a header file. Fixes bug 9716;
13245 bugfix on every released Tor.
13246 - No longer accept malformed http headers when parsing urls from
13247 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
13248 bugfix on 0.0.6pre1.
13249 - In munge_extrainfo_into_routerinfo(), check the return value of
13250 memchr(). This would have been a serious issue if we ever passed
13251 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
13253 - On the chance that somebody manages to build Tor on a
13254 platform where time_t is unsigned, correct the way that
13255 microdesc_add_to_cache() handles negative time arguments.
13256 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
13257 - Reject relative control socket paths and emit a warning. Previously,
13258 single-component control socket paths would be rejected, but Tor
13259 would not log why it could not validate the config. Fixes bug 9258;
13260 bugfix on 0.2.3.16-alpha.
13262 o Minor bugfixes (command line):
13263 - Use a single command-line parser for parsing torrc options on the
13264 command line and for finding special command-line options to avoid
13265 inconsistent behavior for torrc option arguments that have the same
13266 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
13268 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
13269 9573; bugfix on 0.0.9pre5.
13271 o Minor fixes (build, auxiliary programs):
13272 - Stop preprocessing the "torify" script with autoconf, since
13273 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
13275 - The tor-fw-helper program now follows the standard convention and
13276 exits with status code "0" on success. Fixes bug 9030; bugfix on
13277 0.2.3.1-alpha. Patch by Arlo Breault.
13278 - Corrected ./configure advice for what openssl dev package you should
13279 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
13281 o Minor code improvements:
13282 - Remove constants and tests for PKCS1 padding; it's insecure and
13283 shouldn't be used for anything new. Fixes bug 8792; patch
13285 - Remove instances of strcpy() from the unit tests. They weren't
13286 hurting anything, since they were only in the unit tests, but it's
13287 embarrassing to have strcpy() in the code at all, and some analysis
13288 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
13289 0.2.3.8-alpha. Patch from Arlo Breault.
13291 o Removed features:
13292 - Remove migration code from when we renamed the "cached-routers"
13293 file to "cached-descriptors" back in 0.2.0.8-alpha. This
13294 incidentally resolves ticket 6502 by cleaning up the related code
13295 a bit. Patch from Akshay Hebbar.
13297 o Code simplification and refactoring:
13298 - Extract the common duplicated code for creating a subdirectory
13299 of the data directory and writing to a file in it. Fixes ticket
13300 4282; patch from Peter Retzlaff.
13301 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
13302 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
13303 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
13304 - Add a set of accessor functions for the circuit timeout data
13305 structure. Fixes ticket 6153; patch from "piet".
13306 - Clean up exit paths from connection_listener_new(). Closes ticket
13307 8789. Patch from Arlo Breault.
13308 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
13309 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
13310 - Use a doubly-linked list to implement the global circuit list.
13311 Resolves ticket 9108. Patch from Marek Majkowski.
13312 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
13315 Changes in version 0.2.4.17-rc - 2013-09-05
13316 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
13317 series. It adds an emergency step to help us tolerate the massive
13318 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
13319 circuit-level handshakes now effectively jump the queue compared to
13320 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
13321 big bug hindering bridge reachability tests.
13324 - Relays now process the new "NTor" circuit-level handshake requests
13325 with higher priority than the old "TAP" circuit-level handshake
13326 requests. We still process some TAP requests to not totally starve
13327 0.2.3 clients when NTor becomes popular. A new consensus parameter
13328 "NumNTorsPerTAP" lets us tune the balance later if we need to.
13329 Implements ticket 9574.
13332 - If the circuit build timeout logic is disabled (via the consensus,
13333 or because we are an authority), then don't build testing circuits.
13334 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
13335 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
13336 previously they did not, which prevented them from receiving
13337 successful connections from relays for self-test or bandwidth
13338 testing. Also, when a relay is extending a circuit to a bridge,
13339 it needs to send a NETINFO cell, even when the bridge hasn't sent
13340 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
13341 - If the time to download the next old-style networkstatus is in
13342 the future, do not decline to consider whether to download the
13343 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
13347 - Avoid double-closing the listener socket in our socketpair()
13348 replacement (used on Windows) in the case where the addresses on
13349 our opened sockets don't match what we expected. Fixes bug 9400;
13350 bugfix on 0.0.2pre7. Found by Coverity.
13352 o Minor fixes (config options):
13353 - Avoid overflows when the user sets MaxCircuitDirtiness to a
13354 ridiculously high value, by imposing a (ridiculously high) 30-day
13355 maximum on MaxCircuitDirtiness.
13356 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
13357 message is logged at notice, not at info.
13358 - Warn and fail if a server is configured not to advertise any
13359 ORPorts at all. (We need *something* to put in our descriptor,
13360 or we just won't work.)
13363 - Track how many "TAP" and "NTor" circuit handshake requests we get,
13364 and how many we complete, and log it every hour to help relay
13365 operators follow trends in network load. Addresses ticket 9658.
13366 - Update to the August 7 2013 Maxmind GeoLite Country database.
13369 Changes in version 0.2.4.16-rc - 2013-08-10
13370 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
13371 series. It fixes several crash bugs in the 0.2.4 branch.
13374 - Fix a bug in the voting algorithm that could yield incorrect results
13375 when a non-naming authority declared too many flags. Fixes bug 9200;
13376 bugfix on 0.2.0.3-alpha.
13377 - Fix an uninitialized read that could in some cases lead to a remote
13378 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
13379 Anybody running a hidden service on the experimental 0.2.4.x
13380 branch should upgrade. (This is, so far as we know, unrelated to
13382 - Avoid an assertion failure when processing DNS replies without the
13383 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
13384 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
13385 0.2.4.15-rc. Found by stem integration tests.
13388 - Fix an invalid memory read that occurred when a pluggable
13389 transport proxy failed its configuration protocol.
13390 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
13391 - When evaluating whether to use a connection that we haven't
13392 decided is canonical using a recent link protocol version,
13393 decide that it's canonical only if it used address _does_
13394 match the desired address. Fixes bug 9309; bugfix on
13395 0.2.4.4-alpha. Reported by skruffy.
13396 - Make the default behavior of NumDirectoryGuards be to track
13397 NumEntryGuards. Now a user who changes only NumEntryGuards will get
13398 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
13399 - Fix a spurious compilation warning with some older versions of
13400 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
13403 - Update to the July 3 2013 Maxmind GeoLite Country database.
13406 Changes in version 0.2.4.15-rc - 2013-07-01
13407 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
13408 series. It fixes a few smaller bugs, but generally appears stable.
13409 Please test it and let us know whether it is!
13412 - When receiving a new configuration file via the control port's
13413 LOADCONF command, do not treat the defaults file as absent.
13414 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
13417 - Issue a warning when running with the bufferevents backend enabled.
13418 It's still not stable, and people should know that they're likely
13419 to hit unexpected problems. Closes ticket 9147.
13422 Changes in version 0.2.4.14-alpha - 2013-06-18
13423 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
13424 present in 0.2.4.13-alpha.
13427 - When we have too much memory queued in circuits (according to a new
13428 MaxMemInCellQueues option), close the circuits consuming the most
13429 memory. This prevents us from running out of memory as a relay if
13430 circuits fill up faster than they can be drained. Fixes bug 9063;
13431 bugfix on the 54th commit of Tor. This bug is a further fix beyond
13432 bug 6252, whose fix was merged into 0.2.3.21-rc.
13434 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
13435 where we tried to solve this issue simply by imposing an upper limit
13436 on the number of queued cells for a single circuit. That approach
13437 proved to be problematic, since there are ways to provoke clients to
13438 send a number of cells in excess of any such reasonable limit. Fixes
13439 bug 9072; bugfix on 0.2.4.13-alpha.
13441 - Limit hidden service descriptors to at most ten introduction
13442 points, to slow one kind of guard enumeration. Fixes bug 9002;
13443 bugfix on 0.1.1.11-alpha.
13446 Changes in version 0.2.4.13-alpha - 2013-06-14
13447 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
13448 vulnerabilities, makes socks5 username/password circuit isolation
13449 actually actually work (this time for sure!), and cleans up a bunch
13450 of other issues in preparation for a release candidate.
13452 o Major bugfixes (robustness):
13453 - Close any circuit that has too many cells queued on it. Fixes
13454 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
13455 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
13456 - Prevent the get_freelists() function from running off the end of
13457 the list of freelists if it somehow gets an unrecognized
13458 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
13460 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
13461 when an exit connection with optimistic data succeeds immediately
13462 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
13464 - Fix a directory authority crash bug when building a consensus
13465 using an older consensus as its basis. Fixes bug 8833. Bugfix
13469 - Avoid a memory leak where we would leak a consensus body when we
13470 find that a consensus which we couldn't previously verify due to
13471 missing certificates is now verifiable. Fixes bug 8719; bugfix
13473 - We used to always request authority certificates by identity digest,
13474 meaning we'd get the newest one even when we wanted one with a
13475 different signing key. Then we would complain about being given
13476 a certificate we already had, and never get the one we really
13477 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
13478 resource to request the one we want. Fixes bug 5595; bugfix on
13480 - Follow the socks5 protocol when offering username/password
13481 authentication. The fix for bug 8117 exposed this bug, and it
13482 turns out real-world applications like Pidgin do care. Bugfix on
13483 0.2.3.2-alpha; fixes bug 8879.
13484 - Prevent failures on Windows Vista and later when rebuilding the
13485 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
13486 bugfix on 0.2.4.12-alpha.
13489 - Fix an impossible buffer overrun in the AES unit tests. Fixes
13490 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
13491 - If for some reason we fail to write a microdescriptor while
13492 rebuilding the cache, do not let the annotations from that
13493 microdescriptor linger in the cache file, and do not let the
13494 microdescriptor stay recorded as present in its old location.
13495 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
13496 - Fix a memory leak that would occur whenever a configuration
13497 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
13498 - Paste the description for PathBias parameters from the man
13499 page into or.h, so the code documents them too. Fixes bug 7982;
13500 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
13501 - Relays now treat a changed IPv6 ORPort as sufficient reason to
13502 publish an updated descriptor. Fixes bug 6026; bugfix on
13504 - When launching a resolve request on behalf of an AF_UNIX control
13505 socket, omit the address field of the new entry connection, used in
13506 subsequent controller events, rather than letting tor_dup_addr()
13507 set it to "<unknown address type>". Fixes bug 8639; bugfix on
13510 o Minor bugfixes (log messages):
13511 - Fix a scaling issue in the path bias accounting code that
13512 resulted in "Bug:" log messages from either
13513 pathbias_scale_close_rates() or pathbias_count_build_success().
13514 This represents a bugfix on a previous bugfix: the original fix
13515 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
13517 - Give a less useless error message when the user asks for an IPv4
13518 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
13522 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
13523 to tolerate bug 8093 for now.
13524 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
13525 in directory authority votes to describe whether they have enough
13526 measured bandwidths to ignore advertised (relay descriptor)
13527 bandwidth claims. Resolves ticket 8711.
13528 - Update to the June 5 2013 Maxmind GeoLite Country database.
13530 o Removed documentation:
13531 - Remove some of the older contents of doc/ as obsolete; move others
13532 to torspec.git. Fixes bug 8965.
13534 o Code simplification and refactoring:
13535 - Avoid using character buffers when constructing most directory
13536 objects: this approach was unwieldy and error-prone. Instead,
13537 build smartlists of strings, and concatenate them when done.
13540 Changes in version 0.2.4.12-alpha - 2013-04-18
13541 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
13542 process for lengthening the guard rotation period, makes directory
13543 authority opinions in the consensus a bit less gameable, makes socks5
13544 username/password circuit isolation actually work, and fixes a wide
13545 variety of other issues.
13548 - Raise the default time that a client keeps an entry guard from
13549 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
13550 2012 paper. (We would make it even longer, but we need better client
13551 load balancing first.) Also, make the guard lifetime controllable
13552 via a new GuardLifetime torrc option and a GuardLifetime consensus
13553 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
13554 - Directory authorities now prefer using measured bandwidths to
13555 advertised ones when computing flags and thresholds. Resolves
13557 - Directory authorities that have more than a threshold number
13558 of relays with measured bandwidths now treat relays with unmeasured
13559 bandwidths as having bandwidth 0. Resolves ticket 8435.
13561 o Major bugfixes (assert / resource use):
13562 - Avoid a bug where our response to TLS renegotiation under certain
13563 network conditions could lead to a busy-loop, with 100% CPU
13564 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
13565 - Avoid an assertion when we discover that we'd like to write a cell
13566 onto a closing connection: just discard the cell. Fixes another
13567 case of bug 7350; bugfix on 0.2.4.4-alpha.
13569 o Major bugfixes (client-side privacy):
13570 - When we mark a circuit as unusable for new circuits, have it
13571 continue to be unusable for new circuits even if MaxCircuitDirtiness
13572 is increased too much at the wrong time, or the system clock jumps
13573 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
13574 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
13575 which have resolved to internal addresses") is set, apply that
13576 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
13577 - When an exit relay rejects a stream with reason "exit policy", but
13578 we only know an exit policy summary (e.g. from the microdesc
13579 consensus) for it, do not mark the relay as useless for all exiting.
13580 Instead, mark just the circuit as unsuitable for that particular
13581 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
13582 - Allow applications to get proper stream isolation with
13583 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
13584 username/password authentication also offer "no authentication". Tor
13585 had previously preferred "no authentication", so the applications
13586 never actually sent Tor their auth details. Now Tor selects
13587 username/password authentication if it's offered. You can disable
13588 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
13589 bug 8117; bugfix on 0.2.3.3-alpha.
13591 o Major bugfixes (other):
13592 - When unable to find any working directory nodes to use as a
13593 directory guard, give up rather than adding the same non-working
13594 nodes to the directory guard list over and over. Fixes bug 8231;
13595 bugfix on 0.2.4.8-alpha.
13598 - Reject as invalid most directory objects containing a NUL.
13599 Belt-and-suspender fix for bug 8037.
13600 - In our testsuite, create temporary directories with a bit more
13601 entropy in their name to make name collisions less likely. Fixes
13603 - Add CACHED keyword to ADDRMAP events in the control protocol
13604 to indicate whether a DNS result will be cached or not. Resolves
13606 - Update to the April 3 2013 Maxmind GeoLite Country database.
13608 o Minor features (build):
13609 - Detect and reject attempts to build Tor with threading support
13610 when OpenSSL has been compiled without threading support.
13612 - Clarify that when autoconf is checking for nacl, it is checking
13613 specifically for nacl with a fast curve25519 implementation.
13615 - Warn if building on a platform with an unsigned time_t: there
13616 are too many places where Tor currently assumes that time_t can
13617 hold negative values. We'd like to fix them all, but probably
13620 o Minor bugfixes (build):
13621 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
13622 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
13623 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
13624 - Add the old src/or/micro-revision.i filename to CLEANFILES.
13625 On the off chance that somebody has one, it will go away as soon
13626 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
13627 - Build Tor correctly on 32-bit platforms where the compiler can build
13628 but not run code using the "uint128_t" construction. Fixes bug 8587;
13629 bugfix on 0.2.4.8-alpha.
13630 - Fix compilation warning with some versions of clang that would
13631 prefer the -Wswitch-enum compiler flag to warn about switch
13632 statements with missing enum values, even if those switch
13633 statements have a "default:" statement. Fixes bug 8598; bugfix
13636 o Minor bugfixes (protocol):
13637 - Fix the handling of a TRUNCATE cell when it arrives while the
13638 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
13639 - Fix a misframing issue when reading the version numbers in a
13640 VERSIONS cell. Previously we would recognize [00 01 00 02] as
13641 'version 1, version 2, and version 0x100', when it should have
13642 only included versions 1 and 2. Fixes bug 8059; bugfix on
13643 0.2.0.10-alpha. Reported pseudonymously.
13644 - Make the format and order of STREAM events for DNS lookups
13645 consistent among the various ways to launch DNS lookups. Fixes
13646 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
13647 - Correct our check for which versions of Tor support the EXTEND2
13648 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
13649 later, when support was really added in version 0.2.4.8-alpha.
13650 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
13652 o Minor bugfixes (other):
13653 - Correctly store microdescriptors and extrainfo descriptors with
13654 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
13655 Bug reported by "cypherpunks".
13656 - Increase the width of the field used to remember a connection's
13657 link protocol version to two bytes. Harmless for now, since the
13658 only currently recognized versions are one byte long. Reported
13659 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
13660 - If the state file's path bias counts are invalid (presumably from a
13661 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
13662 additional checks and log messages to the scaling of Path Bias
13663 counts, in case there still are remaining issues with scaling.
13664 Should help resolve bug 8235.
13665 - Eliminate several instances where we use "Nickname=ID" to refer to
13666 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
13667 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
13668 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
13670 o Minor bugfixes (syscalls):
13671 - Always check the return values of functions fcntl() and
13672 setsockopt(). We don't believe these are ever actually failing in
13673 practice, but better safe than sorry. Also, checking these return
13674 values should please analysis tools like Coverity. Patch from
13675 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
13676 - Use direct writes rather than stdio when building microdescriptor
13677 caches, in an attempt to mitigate bug 8031, or at least make it
13680 o Minor bugfixes (config):
13681 - When rejecting a configuration because we were unable to parse a
13682 quoted string, log an actual error message. Fixes bug 7950; bugfix
13684 - Behave correctly when the user disables LearnCircuitBuildTimeout
13685 but doesn't tell us what they would like the timeout to be. Fixes
13686 bug 6304; bugfix on 0.2.2.14-alpha.
13687 - When autodetecting the number of CPUs, use the number of available
13688 CPUs in preference to the number of configured CPUs. Inform the
13689 user if this reduces the number of available CPUs. Fixes bug 8002;
13690 bugfix on 0.2.3.1-alpha.
13691 - Make it an error when you set EntryNodes but disable UseGuardNodes,
13692 since it will (surprisingly to some users) ignore EntryNodes. Fixes
13693 bug 8180; bugfix on 0.2.3.11-alpha.
13694 - Allow TestingTorNetworks to override the 4096-byte minimum for
13695 the Fast threshold. Otherwise they can't bootstrap until they've
13696 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
13697 - Fix some logic errors when the user manually overrides the
13698 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
13701 o Minor bugfixes (log messages to help diagnose bugs):
13702 - If we fail to free a microdescriptor because of bug 7164, log
13703 the filename and line number from which we tried to free it.
13704 - Add another diagnostic to the heartbeat message: track and log
13705 overhead that TLS is adding to the data we write. If this is
13706 high, we are sending too little data to SSL_write at a time.
13707 Diagnostic for bug 7707.
13708 - Add more detail to a log message about relaxed timeouts, to help
13710 - Warn more aggressively when flushing microdescriptors to a
13711 microdescriptor cache fails, in an attempt to mitigate bug 8031,
13712 or at least make it more diagnosable.
13713 - Improve debugging output to help track down bug 8185 ("Bug:
13714 outgoing relay cell has n_chan==NULL. Dropping.")
13715 - Log the purpose of a path-bias testing circuit correctly.
13716 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
13718 o Minor bugfixes (0.2.4.x log messages that were too noisy):
13719 - Don't attempt to relax the timeout of already opened 1-hop circuits.
13720 They might never timeout. This should eliminate some/all cases of
13721 the relaxed timeout log message.
13722 - Use circuit creation time for network liveness evaluation. This
13723 should eliminate warning log messages about liveness caused
13724 by changes in timeout evaluation. Fixes bug 6572; bugfix on
13726 - Reduce a path bias length check from notice to info. The message
13727 is triggered when creating controller circuits. Fixes bug 8196;
13728 bugfix on 0.2.4.8-alpha.
13729 - Fix a path state issue that triggered a notice during relay startup.
13730 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
13731 - Reduce occurrences of warns about circuit purpose in
13732 connection_ap_expire_building(). Fixes bug 8477; bugfix on
13735 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
13736 - If we encounter a write failure on a SOCKS connection before we
13737 finish our SOCKS handshake, don't warn that we closed the
13738 connection before we could send a SOCKS reply. Fixes bug 8427;
13739 bugfix on 0.1.0.1-rc.
13740 - Correctly recognize that [::1] is a loopback address. Fixes
13741 bug 8377; bugfix on 0.2.1.3-alpha.
13742 - Fix a directory authority warn caused when we have a large amount
13743 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
13744 - Don't log inappropriate heartbeat messages when hibernating: a
13745 hibernating node is _expected_ to drop out of the consensus,
13746 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
13747 bugfix on 0.2.3.1-alpha.
13748 - Don't complain about bootstrapping problems while hibernating.
13749 These complaints reflect a general code problem, but not one
13750 with any problematic effects (no connections are actually
13751 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
13753 o Documentation fixes:
13754 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
13755 names match. Fixes bug 7768.
13756 - Make the torify manpage no longer refer to tsocks; torify hasn't
13757 supported tsocks since 0.2.3.14-alpha.
13758 - Make the tor manpage no longer reference tsocks.
13759 - Fix the GeoIPExcludeUnknown documentation to refer to
13760 ExcludeExitNodes rather than the currently nonexistent
13761 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
13764 - The tor-tsocks.conf is no longer distributed or installed. We
13765 recommend that tsocks users use torsocks instead. Resolves
13769 Changes in version 0.2.4.11-alpha - 2013-03-11
13770 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
13771 more robust, makes hidden service authentication work again, and
13772 resolves a DPI fingerprint for Tor's SSL transport.
13774 o Major features (directory authorities):
13775 - Directory authorities now support a new consensus method (17)
13776 where they cap the published bandwidth of servers for which
13777 insufficient bandwidth measurements exist. Fixes part of bug 2286.
13778 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
13779 serve any v2 directory information. Now we can test disabling the
13780 old deprecated v2 directory format, and see whether doing so has
13781 any effect on network load. Begins to fix bug 6783.
13782 - Directory authorities now include inside each vote a statement of
13783 the performance thresholds they used when assigning flags.
13784 Implements ticket 8151.
13786 o Major bugfixes (directory authorities):
13787 - Stop marking every relay as having been down for one hour every
13788 time we restart a directory authority. These artificial downtimes
13789 were messing with our Stable and Guard flag calculations. Fixes
13790 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
13792 o Major bugfixes (hidden services):
13793 - Allow hidden service authentication to succeed again. When we
13794 refactored the hidden service introduction code back
13795 in 0.2.4.1-alpha, we didn't update the code that checks
13796 whether authentication information is present, causing all
13797 authentication checks to return "false". Fix for bug 8207; bugfix
13798 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
13800 o Minor features (relays, bridges):
13801 - Make bridge relays check once a minute for whether their IP
13802 address has changed, rather than only every 15 minutes. Resolves
13803 bugs 1913 and 1992.
13804 - Refactor resolve_my_address() so it returns the method by which we
13805 decided our public IP address (explicitly configured, resolved from
13806 explicit hostname, guessed from interfaces, learned by gethostname).
13807 Now we can provide more helpful log messages when a relay guesses
13808 its IP address incorrectly (e.g. due to unexpected lines in
13809 /etc/hosts). Resolves ticket 2267.
13810 - Teach bridge-using clients to avoid 0.2.2 bridges when making
13811 microdescriptor-related dir requests, and only fall back to normal
13812 descriptors if none of their bridges can handle microdescriptors
13813 (as opposed to the fix in ticket 4013, which caused them to fall
13814 back to normal descriptors if *any* of their bridges preferred
13815 them). Resolves ticket 4994.
13816 - Randomize the lifetime of our SSL link certificate, so censors can't
13817 use the static value for filtering Tor flows. Resolves ticket 8443;
13818 related to ticket 4014 which was included in 0.2.2.33.
13819 - Support a new version of the link protocol that allows 4-byte circuit
13820 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
13821 a possible resource exhaustion issue. Closes ticket 7351; implements
13824 o Minor features (portability):
13825 - Tweak the curve25519-donna*.c implementations to tolerate systems
13826 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
13827 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
13828 the signs of types during autoconf. This is better than our old
13829 approach, which didn't work when cross-compiling.
13830 - Detect the sign of enum values, rather than assuming that MSC is the
13831 only compiler where enum types are all signed. Fixes bug 7727;
13832 bugfix on 0.2.4.10-alpha.
13834 o Minor features (other):
13835 - Say "KBytes" rather than "KB" in the man page (for various values
13836 of K), to further reduce confusion about whether Tor counts in
13837 units of memory or fractions of units of memory. Resolves ticket 7054.
13838 - Clear the high bit on curve25519 public keys before passing them to
13839 our backend, in case we ever wind up using a backend that doesn't do
13840 so itself. If we used such a backend, and *didn't* clear the high bit,
13841 we could wind up in a situation where users with such backends would
13842 be distinguishable from users without. Fixes bug 8121; bugfix on
13844 - Update to the March 6 2013 Maxmind GeoLite Country database.
13846 o Minor bugfixes (clients):
13847 - When we receive a RELAY_END cell with the reason DONE, or with no
13848 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
13849 status as "connection refused". Previously we reported these cases
13850 as success but then immediately closed the connection. Fixes bug
13851 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
13852 - Downgrade an assertion in connection_ap_expire_beginning to an
13853 LD_BUG message. The fix for bug 8024 should prevent this message
13854 from displaying, but just in case, a warn that we can diagnose
13855 is better than more assert crashes. Fixes bug 8065; bugfix on
13857 - Lower path use bias thresholds to .80 for notice and .60 for warn.
13858 Also make the rate limiting flags for the path use bias log messages
13859 independent from the original path bias flags. Fixes bug 8161;
13860 bugfix on 0.2.4.10-alpha.
13862 o Minor bugfixes (relays):
13863 - Stop trying to resolve our hostname so often (e.g. every time we
13864 think about doing a directory fetch). Now we reuse the cached
13865 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
13866 and 2410 (bugfix on 0.1.2.2-alpha).
13867 - Stop sending a stray "(null)" in some cases for the server status
13868 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
13870 - When choosing which stream on a formerly stalled circuit to wake
13871 first, make better use of the platform's weak RNG. Previously,
13872 we had been using the % ("modulo") operator to try to generate a
13873 1/N chance of picking each stream, but this behaves badly with
13874 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
13876 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
13877 Irix's random() only return 15 bits; Solaris's random() returns more
13878 bits but its RAND_MAX says it only returns 15, and so on. Motivated
13879 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
13881 o Minor bugfixes (directory authorities):
13882 - Directory authorities now use less space when formatting identical
13883 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
13886 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
13887 - Avoid leaking memory if we fail to compute a consensus signature
13888 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
13889 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
13891 - Fix a memory leak during safe-cookie controller authentication.
13892 Bugfix on 0.2.3.13-alpha.
13893 - Avoid memory leak of IPv6 policy content if we fail to format it into
13894 a router descriptor. Bugfix on 0.2.4.7-alpha.
13896 o Minor bugfixes (other code correctness issues):
13897 - Avoid a crash if we fail to generate an extrainfo descriptor.
13898 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
13899 this is CID 718634.
13900 - When detecting the largest possible file descriptor (in order to
13901 close all file descriptors when launching a new program), actually
13902 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
13903 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
13905 - Fix a copy-and-paste error when adding a missing A1 to a routerset
13906 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
13907 Bugfix on 0.2.4.10-alpha.
13908 - Fix an impossible-to-trigger integer overflow when estimating how
13909 long our onionskin queue would take. (This overflow would require us
13910 to accept 4 million onionskins before processing 100 of them.) Fixes
13911 bug 8210; bugfix on 0.2.4.10-alpha.
13913 o Code simplification and refactoring:
13914 - Add a wrapper function for the common "log a message with a
13918 Changes in version 0.2.4.10-alpha - 2013-02-04
13919 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
13920 certain attacks that flood the network with relays; changes the queue
13921 for circuit create requests from a sized-based limit to a time-based
13922 limit; resumes building with MSVC on Windows; and fixes a wide variety
13925 o Major bugfixes (directory authority):
13926 - When computing directory thresholds, ignore any rejected-as-sybil
13927 nodes during the computation so that they can't influence Fast,
13928 Guard, etc. (We should have done this for proposal 109.) Fixes
13930 - When marking a node as a likely sybil, reset its uptime metrics
13931 to zero, so that it cannot time towards getting marked as Guard,
13932 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
13936 - When a TLS write is partially successful but incomplete, remember
13937 that the flushed part has been flushed, and notice that bytes were
13938 actually written. Reported and fixed pseudonymously. Fixes bug
13939 7708; bugfix on Tor 0.1.0.5-rc.
13940 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
13941 ID: these could be used to create unexpected streams and circuits
13942 which would count as "present" to some parts of Tor but "absent"
13943 to others, leading to zombie circuits and streams or to a bandwidth
13944 denial-of-service. Fixes bug 7889; bugfix on every released version
13945 of Tor. Reported by "oftc_must_be_destroyed".
13946 - Rename all macros in our local copy of queue.h to begin with "TOR_".
13947 This change seems the only good way to permanently prevent conflicts
13948 with queue.h on various operating systems. Fixes bug 8107; bugfix
13951 o Major features (relay):
13952 - Instead of limiting the number of queued onionskins (aka circuit
13953 create requests) to a fixed, hard-to-configure number, we limit
13954 the size of the queue based on how many we expect to be able to
13955 process in a given amount of time. We estimate the time it will
13956 take to process an onionskin based on average processing time
13957 of previous onionskins. Closes ticket 7291. You'll never have to
13958 configure MaxOnionsPending again.
13960 o Major features (portability):
13961 - Resume building correctly with MSVC and Makefile.nmake. This patch
13962 resolves numerous bugs and fixes reported by ultramage, including
13963 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
13964 - Make the ntor and curve25519 code build correctly with MSVC.
13965 Fix on 0.2.4.8-alpha.
13968 - When directory authorities are computing thresholds for flags,
13969 never let the threshold for the Fast flag fall below 4096
13970 bytes. Also, do not consider nodes with extremely low bandwidths
13971 when deciding thresholds for various directory flags. This change
13972 should raise our threshold for Fast relays, possibly in turn
13973 improving overall network performance; see ticket 1854. Resolves
13975 - The Tor client now ignores sub-domain components of a .onion
13976 address. This change makes HTTP "virtual" hosting
13977 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
13978 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
13979 hosted on the same hidden service. Implements proposal 204.
13980 - We compute the overhead from passing onionskins back and forth to
13981 cpuworkers, and report it when dumping statistics in response to
13982 SIGUSR1. Supports ticket 7291.
13984 o Minor features (path selection):
13985 - When deciding whether we have enough descriptors to build circuits,
13986 instead of looking at raw relay counts, look at which fraction
13987 of (bandwidth-weighted) paths we're able to build. This approach
13988 keeps clients from building circuits if their paths are likely to
13989 stand out statistically. The default fraction of paths needed is
13990 taken from the consensus directory; you can override it with the
13991 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
13992 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
13993 and we have GeoIP information, also exclude all nodes with unknown
13994 countries "??" and "A1". This behavior is controlled by the
13995 new GeoIPExcludeUnknown option: you can make such nodes always
13996 excluded with "GeoIPExcludeUnknown 1", and disable the feature
13997 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
13998 gets you the default behavior. Implements feature 7706.
13999 - Path Use Bias: Perform separate accounting for successful circuit
14000 use. Keep separate statistics on stream attempt rates versus stream
14001 success rates for each guard. Provide configurable thresholds to
14002 determine when to emit log messages or disable use of guards that
14003 fail too many stream attempts. Resolves ticket 7802.
14005 o Minor features (log messages):
14006 - When learning a fingerprint for a bridge, log its corresponding
14007 transport type. Implements ticket 7896.
14008 - Improve the log message when "Bug/attack: unexpected sendme cell
14009 from client" occurs, to help us track bug 8093.
14012 - Remove a couple of extraneous semicolons that were upsetting the
14013 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
14014 bugfix on 0.2.2.1-alpha.
14015 - Remove a source of rounding error during path bias count scaling;
14016 don't count cannibalized circuits as used for path bias until we
14017 actually try to use them; and fix a circuit_package_relay_cell()
14018 warning message about n_chan==NULL. Fixes bug 7802.
14019 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
14020 actually link against nacl when we're configured to use it. Fixes
14021 bug 7972; bugfix on 0.2.4.8-alpha.
14022 - Compile correctly with the --disable-curve25519 option. Fixes
14023 bug 8153; bugfix on 0.2.4.8-alpha.
14025 o Build improvements:
14026 - Do not report status verbosely from autogen.sh unless the -v flag
14027 is specified. Fixes issue 4664. Patch from Onizuka.
14028 - Replace all calls to snprintf() outside of src/ext with
14029 tor_snprintf(). Also remove the #define to replace snprintf with
14030 _snprintf on Windows; they have different semantics, and all of
14031 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
14032 - Try to detect if we are ever building on a platform where
14033 memset(...,0,...) does not set the value of a double to 0.0. Such
14034 platforms are permitted by the C standard, though in practice
14035 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
14036 currently support them, but it's better to detect them and fail
14037 than to perform erroneously.
14039 o Removed features:
14040 - Stop exporting estimates of v2 and v3 directory traffic shares
14041 in extrainfo documents. They were unneeded and sometimes inaccurate.
14042 Also stop exporting any v2 directory request statistics. Resolves
14044 - Drop support for detecting and warning about versions of Libevent
14045 before 1.3e. Nothing reasonable ships with them any longer;
14046 warning the user about them shouldn't be needed. Resolves ticket
14049 o Code simplifications and refactoring:
14050 - Rename "isin" functions to "contains", for grammar. Resolves
14052 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
14053 with the natural logarithm function from the system libm. Resolves
14057 Changes in version 0.2.4.9-alpha - 2013-01-15
14058 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
14059 work more robustly.
14062 - Fix backward compatibility logic when receiving an embedded ntor
14063 handshake tunneled in a CREATE cell. This clears up the "Bug:
14064 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
14068 Changes in version 0.2.4.8-alpha - 2013-01-14
14069 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
14070 risks, adds a new stronger and faster circuit handshake, and offers
14071 stronger and faster link encryption when both sides support it.
14074 - Preliminary support for directory guards (proposal 207): when
14075 possible, clients now use their entry guards for non-anonymous
14076 directory requests. This can help prevent client enumeration. Note
14077 that this behavior only works when we have a usable consensus
14078 directory, and when options about what to download are more or less
14079 standard. In the future we should re-bootstrap from our guards,
14080 rather than re-bootstrapping from the preconfigured list of
14081 directory sources that ships with Tor. Resolves ticket 6526.
14082 - Tor relays and clients now support a better CREATE/EXTEND cell
14083 format, allowing the sender to specify multiple address, identity,
14084 and handshake types. Implements Robert Ransom's proposal 200;
14085 closes ticket 7199.
14087 o Major features (new circuit handshake):
14088 - Tor now supports a new circuit extension handshake designed by Ian
14089 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
14090 circuit extension handshake, later called "TAP", was a bit slow
14091 (especially on the relay side), had a fragile security proof, and
14092 used weaker keys than we'd now prefer. The new circuit handshake
14093 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
14094 function, making it significantly more secure than the older
14095 handshake, and significantly faster. Tor can use one of two built-in
14096 pure-C curve25519-donna implementations by Adam Langley, or it
14097 can link against the "nacl" library for a tuned version if present.
14099 The built-in version is very fast for 64-bit systems when building
14100 with GCC. The built-in 32-bit version is still faster than the
14101 old TAP protocol, but using libnacl is better on most such hosts.
14103 Clients don't currently use this protocol by default, since
14104 comparatively few clients support it so far. To try it, set
14105 UseNTorHandshake to 1.
14107 Implements proposal 216; closes ticket 7202.
14109 o Major features (better link encryption):
14110 - Relays can now enable the ECDHE TLS ciphersuites when available
14111 and appropriate. These ciphersuites let us negotiate forward-secure
14112 TLS secret keys more safely and more efficiently than with our
14113 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
14114 public relays prefer the (faster) P224 group, and bridges prefer
14115 the (more common) P256 group; you can override this with the
14118 Enabling these ciphers was a little tricky, since for a long time,
14119 clients had been claiming to support them without actually doing
14120 so, in order to foil fingerprinting. But with the client-side
14121 implementation of proposal 198 in 0.2.3.17-beta, clients can now
14122 match the ciphers from recent Firefox versions *and* list the
14123 ciphers they actually mean, so relays can believe such clients
14124 when they advertise ECDHE support in their TLS ClientHello messages.
14126 This feature requires clients running 0.2.3.17-beta or later,
14127 and requires both sides to be running OpenSSL 1.0.0 or later
14128 with ECC support. OpenSSL 1.0.1, with the compile-time option
14129 "enable-ec_nistp_64_gcc_128", is highly recommended.
14131 Implements the relay side of proposal 198; closes ticket 7200.
14134 - Avoid crashing when, as a relay without IPv6-exit support, a
14135 client insists on getting an IPv6 address or nothing. Fixes bug
14136 7814; bugfix on 0.2.4.7-alpha.
14139 - Improve circuit build timeout handling for hidden services.
14140 In particular: adjust build timeouts more accurately depending
14141 upon the number of hop-RTTs that a particular circuit type
14142 undergoes. Additionally, launch intro circuits in parallel
14143 if they timeout, and take the first one to reply as valid.
14144 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
14145 separate error codes; or at least, don't break for that reason.
14146 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
14147 - Update to the January 2 2013 Maxmind GeoLite Country database.
14149 o Minor features (testing):
14150 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
14151 (P-256) Diffie-Hellman handshakes to src/or/bench.
14152 - Add benchmark functions to test onion handshake performance.
14154 o Minor features (path bias detection):
14155 - Alter the Path Bias log messages to be more descriptive in terms
14156 of reporting timeouts and other statistics.
14157 - Create three levels of Path Bias log messages, as opposed to just
14158 two. These are configurable via consensus as well as via the torrc
14159 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
14160 The default values are 0.70, 0.50, and 0.30 respectively.
14161 - Separate the log message levels from the decision to drop guards,
14162 which also is available via torrc option PathBiasDropGuards.
14163 PathBiasDropGuards still defaults to 0 (off).
14164 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
14165 in combination with PathBiasExtremeRate.
14166 - Increase the default values for PathBiasScaleThreshold and
14167 PathBiasCircThreshold from (200, 20) to (300, 150).
14168 - Add in circuit usage accounting to path bias. If we try to use a
14169 built circuit but fail for any reason, it counts as path bias.
14170 Certain classes of circuits where the adversary gets to pick your
14171 destination node are exempt from this accounting. Usage accounting
14172 can be specifically disabled via consensus parameter or torrc.
14173 - Convert all internal path bias state to double-precision floating
14174 point, to avoid roundoff error and other issues.
14175 - Only record path bias information for circuits that have completed
14176 *two* hops. Assuming end-to-end tagging is the attack vector, this
14177 makes us more resilient to ambient circuit failure without any
14178 detection capability loss.
14180 o Minor bugfixes (log messages):
14181 - Rate-limit the "No circuits are opened. Relaxed timeout for a
14182 circuit with channel state open..." message to once per hour to
14183 keep it from filling the notice logs. Mitigates bug 7799 but does
14184 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
14185 - Avoid spurious warnings when configuring multiple client ports of
14186 which only some are nonlocal. Previously, we had claimed that some
14187 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
14190 o Code simplifications and refactoring:
14191 - Get rid of a couple of harmless clang warnings, where we compared
14192 enums to ints. These warnings are newly introduced in clang 3.2.
14193 - Split the onion.c file into separate modules for the onion queue
14194 and the different handshakes it supports.
14195 - Remove the marshalling/unmarshalling code for sending requests to
14196 cpuworkers over a socket, and instead just send structs. The
14197 recipient will always be the same Tor binary as the sender, so
14198 any encoding is overkill.
14201 Changes in version 0.2.4.7-alpha - 2012-12-24
14202 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
14203 directory mirrors for more robust bootstrapping; fixes more issues where
14204 clients with changing network conditions refuse to make any circuits;
14205 adds initial support for exiting to IPv6 addresses; resumes being able
14206 to update our GeoIP database, and includes the geoip6 file this time;
14207 turns off the client-side DNS cache by default due to privacy risks;
14208 and fixes a variety of other issues.
14210 o Major features (client resilience):
14211 - Add a new "FallbackDir" torrc option to use when we can't use
14212 a directory mirror from the consensus (either because we lack a
14213 consensus, or because they're all down). Currently, all authorities
14214 are fallbacks by default, and there are no other default fallbacks,
14215 but that will change. This option will allow us to give clients a
14216 longer list of servers to try to get a consensus from when first
14217 connecting to the Tor network, and thereby reduce load on the
14218 directory authorities. Implements proposal 206, "Preconfigured
14219 directory sources for bootstrapping". We also removed the old
14220 "FallbackNetworkstatus" option, since we never got it working well
14221 enough to use it. Closes bug 572.
14222 - If we have no circuits open, use a relaxed timeout (the
14223 95-percentile cutoff) until a circuit succeeds. This heuristic
14224 should allow Tor to succeed at building circuits even when the
14225 network connection drastically changes. Should help with bug 3443.
14227 o Major features (IPv6):
14228 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
14229 connectivity, then set the IPv6Exit flag to 1. Also make sure your
14230 exit policy reads as you would like: the address * applies to all
14231 address families, whereas *4 is IPv4 address only, and *6 is IPv6
14232 addresses only. On the client side, you'll need to wait until the
14233 authorities have upgraded, wait for enough exits to support IPv6,
14234 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
14235 ticket 5547, implements proposal 117 as revised in proposal 208.
14237 We DO NOT recommend that clients with actual anonymity needs start
14238 using IPv6 over Tor yet, since not enough exits support it yet.
14240 o Major features (geoip database):
14241 - Maxmind began labelling Tor relays as being in country "A1",
14242 which breaks by-country node selection inside Tor. Now we use a
14243 script to replace "A1" ("Anonymous Proxy") entries in our geoip
14244 file with real country codes. This script fixes about 90% of "A1"
14245 entries automatically and uses manual country code assignments to
14246 fix the remaining 10%. See src/config/README.geoip for details.
14247 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
14248 Country database, as modified above.
14250 o Major bugfixes (client-side DNS):
14251 - Turn off the client-side DNS cache by default. Updating and using
14252 the DNS cache is now configurable on a per-client-port
14253 level. SOCKSPort, DNSPort, etc lines may now contain
14254 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
14255 cache these types of DNS answers when we receive them from an
14256 exit node in response to an application request on this port, and
14257 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
14258 cached DNS answers of these types, we shouldn't use them. It's
14259 potentially risky to use cached DNS answers at the client, since
14260 doing so can indicate to one exit what answers we've gotten
14261 for DNS lookups in the past. With IPv6, this becomes especially
14262 problematic. Using cached DNS answers for requests on the same
14263 circuit would present less linkability risk, since all traffic
14264 on a circuit is already linkable, but it would also provide
14265 little performance benefit: the exit node caches DNS replies
14266 too. Implements a simplified version of Proposal 205. Implements
14269 o Major bugfixes (other):
14270 - Alter circuit build timeout measurement to start at the point
14271 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
14272 initialization). This should make our timeout measurements more
14273 uniform. Previously, we were sometimes including ORconn setup time
14274 in our circuit build time measurements. Should resolve bug 3443.
14275 - Fix an assertion that could trigger in hibernate_go_dormant() when
14276 closing an or_connection_t: call channel_mark_for_close() rather
14277 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
14279 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
14280 7655; bugfix on 0.2.4.6-alpha.
14283 - Add a new torrc option "ServerTransportListenAddr" to let bridge
14284 operators select the address where their pluggable transports will
14285 listen for connections. Resolves ticket 7013.
14286 - Allow an optional $ before the node identity digest in the
14287 controller command GETINFO ns/id/<identity>, for consistency with
14288 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
14289 - Log packaged cell fullness as part of the heartbeat message.
14290 Diagnosis to try to determine the extent of bug 7743.
14292 o Minor features (IPv6):
14293 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
14294 prefer to hand out virtual IPv6 addresses, since there are more of
14295 them and we can't run out. To override this behavior and make IPv4
14296 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
14297 or DNSPort you're using for resolving. Implements ticket 7571.
14298 - AutomapHostsOnResolve responses are now randomized, to avoid
14299 annoying situations where Tor is restarted and applications
14300 connect to the wrong addresses.
14301 - Never try more than 1000 times to pick a new virtual address when
14302 AutomapHostsOnResolve is set. That's good enough so long as we
14303 aren't close to handing out our entire virtual address space;
14304 if you're getting there, it's best to switch to IPv6 virtual
14308 - The ADDRMAP command can no longer generate an ill-formed error
14309 code on a failed MAPADDRESS. It now says "internal" rather than
14310 an English sentence fragment with spaces in the middle. Bugfix on
14311 Tor 0.2.0.19-alpha.
14312 - Fix log messages and comments to avoid saying "GMT" when we mean
14313 "UTC". Fixes bug 6113.
14314 - Compile on win64 using mingw64. Fixes bug 7260; patches from
14316 - Fix a crash when debugging unit tests on Windows: deallocate a
14317 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
14318 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
14321 - The DirServer option is now DirAuthority, for consistency with
14322 current naming patterns. You can still use the old DirServer form.
14324 o Code simplification and refactoring:
14325 - Move the client-side address-map/virtual-address/DNS-cache code
14326 out of connection_edge.c into a new addressmap.c module.
14327 - Remove unused code for parsing v1 directories and "running routers"
14328 documents. Fixes bug 6887.
14331 Changes in version 0.2.3.25 - 2012-11-19
14332 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
14333 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
14334 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
14335 programmer, and friend. Unstinting in his dedication to the cause of
14336 freedom, he inspired and helped many of us as we began our work on
14337 anonymity, and inspires us still. Please honor his memory by writing
14338 software to protect people's freedoms, and by helping others to do so.
14340 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
14341 significantly reduced directory overhead (via microdescriptors),
14342 enormous crypto performance improvements for fast relays on new
14343 enough hardware, a new v3 TLS handshake protocol that can better
14344 resist fingerprinting, support for protocol obfuscation plugins (aka
14345 pluggable transports), better scalability for hidden services, IPv6
14346 support for bridges, performance improvements like allowing clients
14347 to skip the first round-trip on the circuit ("optimistic data") and
14348 refilling token buckets more often, a new "stream isolation" design
14349 to isolate different applications on different circuits, and many
14350 stability, security, and privacy fixes.
14353 - Tor tries to wipe potentially sensitive data after using it, so
14354 that if some subsequent security failure exposes Tor's memory,
14355 the damage will be limited. But we had a bug where the compiler
14356 was eliminating these wipe operations when it decided that the
14357 memory was no longer visible to a (correctly running) program,
14358 hence defeating our attempt at defense in depth. We fix that
14359 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
14360 is unlikely to optimize away. Future versions of Tor may use
14361 a less ridiculously heavy approach for this. Fixes bug 7352.
14362 Reported in an article by Andrey Karpov.
14365 - Fix a harmless bug when opting against publishing a relay descriptor
14366 because DisableNetwork is set. Fixes bug 7464; bugfix on
14370 Changes in version 0.2.4.6-alpha - 2012-11-13
14371 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
14372 makes our defense-in-depth memory wiping more reliable, and begins to
14373 count IPv6 addresses in bridge statistics,
14376 - Fix an assertion failure that could occur when closing a connection
14377 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
14379 - Tor tries to wipe potentially sensitive data after using it, so
14380 that if some subsequent security failure exposes Tor's memory,
14381 the damage will be limited. But we had a bug where the compiler
14382 was eliminating these wipe operations when it decided that the
14383 memory was no longer visible to a (correctly running) program,
14384 hence defeating our attempt at defense in depth. We fix that
14385 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
14386 is unlikely to optimize away. Future versions of Tor may use
14387 a less ridiculously heavy approach for this. Fixes bug 7352.
14388 Reported in an article by Andrey Karpov.
14391 - Add GeoIP database for IPv6 addresses. The new config option
14393 - Bridge statistics now count bridge clients connecting over IPv6:
14394 bridge statistics files now list "bridge-ip-versions" and
14395 extra-info documents list "geoip6-db-digest". The control protocol
14396 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
14397 implementation by "shkoo", addressing ticket 5055.
14400 - Warn when we are binding low ports when hibernation is enabled;
14401 previously we had warned when we were _advertising_ low ports with
14402 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
14403 - Fix a harmless bug when opting against publishing a relay descriptor
14404 because DisableNetwork is set. Fixes bug 7464; bugfix on
14406 - Add warning message when a managed proxy dies during configuration.
14407 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
14408 - Fix a linking error when building tor-fw-helper without miniupnp.
14409 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
14410 - Check for closing an or_connection_t without going through correct
14411 channel functions; emit a warning and then call
14412 connection_or_close_for_error() so we don't assert as in bugs 7212
14414 - Compile correctly on compilers without C99 designated initializer
14415 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
14416 - Avoid a possible assert that can occur when channel_send_destroy() is
14417 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
14418 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
14419 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
14420 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
14421 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
14423 o Code simplification and refactoring:
14424 - Start using OpenBSD's implementation of queue.h, so that we don't
14425 need to hand-roll our own pointer and list structures whenever we
14426 need them. (We can't rely on a sys/queue.h, since some operating
14427 systems don't have them, and the ones that do have them don't all
14428 present the same extensions.)
14431 Changes in version 0.2.4.5-alpha - 2012-10-25
14432 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
14433 two important security vulnerabilities that could lead to remotely
14434 triggerable relay crashes, fix a major bug that was preventing clients
14435 from choosing suitable exit nodes, and refactor some of our code.
14437 o Major bugfixes (security, also in 0.2.3.24-rc):
14438 - Fix a group of remotely triggerable assertion failures related to
14439 incorrect link protocol negotiation. Found, diagnosed, and fixed
14440 by "some guy from France". Fix for CVE-2012-2250; bugfix on
14442 - Fix a denial of service attack by which any directory authority
14443 could crash all the others, or by which a single v2 directory
14444 authority could crash everybody downloading v2 directory
14445 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
14447 o Major bugfixes (also in 0.2.3.24-rc):
14448 - When parsing exit policy summaries from microdescriptors, we had
14449 previously been ignoring the last character in each one, so that
14450 "accept 80,443,8080" would be treated by clients as indicating
14451 a node that allows access to ports 80, 443, and 808. That would
14452 lead to clients attempting connections that could never work,
14453 and ignoring exit nodes that would support their connections. Now
14454 clients parse these exit policy summaries correctly. Fixes bug 7192;
14455 bugfix on 0.2.3.1-alpha.
14457 o Minor bugfixes (also in 0.2.3.24-rc):
14458 - Clients now consider the ClientRejectInternalAddresses config option
14459 when using a microdescriptor consensus stanza to decide whether
14460 an exit relay would allow exiting to an internal address. Fixes
14461 bug 7190; bugfix on 0.2.3.1-alpha.
14464 - Only disable TLS session ticket support when running as a TLS
14465 server. Now clients will blend better with regular Firefox
14466 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
14468 o Code simplification and refactoring:
14469 - Start using OpenBSD's implementation of queue.h (originally by
14471 - Move the entry node code from circuitbuild.c to its own file.
14472 - Move the circuit build timeout tracking code from circuitbuild.c
14476 Changes in version 0.2.3.24-rc - 2012-10-25
14477 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
14478 could lead to remotely triggerable relay crashes, and fixes
14479 a major bug that was preventing clients from choosing suitable exit
14482 o Major bugfixes (security):
14483 - Fix a group of remotely triggerable assertion failures related to
14484 incorrect link protocol negotiation. Found, diagnosed, and fixed
14485 by "some guy from France". Fix for CVE-2012-2250; bugfix on
14487 - Fix a denial of service attack by which any directory authority
14488 could crash all the others, or by which a single v2 directory
14489 authority could crash everybody downloading v2 directory
14490 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
14493 - When parsing exit policy summaries from microdescriptors, we had
14494 previously been ignoring the last character in each one, so that
14495 "accept 80,443,8080" would be treated by clients as indicating
14496 a node that allows access to ports 80, 443, and 808. That would
14497 lead to clients attempting connections that could never work,
14498 and ignoring exit nodes that would support their connections. Now
14499 clients parse these exit policy summaries correctly. Fixes bug 7192;
14500 bugfix on 0.2.3.1-alpha.
14503 - Clients now consider the ClientRejectInternalAddresses config option
14504 when using a microdescriptor consensus stanza to decide whether
14505 an exit relay would allow exiting to an internal address. Fixes
14506 bug 7190; bugfix on 0.2.3.1-alpha.
14509 Changes in version 0.2.4.4-alpha - 2012-10-20
14510 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
14511 vulnerability introduced by a change in OpenSSL, fixes a remotely
14512 triggerable assert, and adds new channel_t and circuitmux_t abstractions
14513 that will make it easier to test new connection transport and cell
14514 scheduling algorithms.
14516 o New directory authorities (also in 0.2.3.23-rc):
14517 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
14518 authority. Closes ticket 5749.
14520 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
14521 - Disable TLS session tickets. OpenSSL's implementation was giving
14522 our TLS session keys the lifetime of our TLS context objects, when
14523 perfect forward secrecy would want us to discard anything that
14524 could decrypt a link connection as soon as the link connection
14525 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
14526 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
14527 - Discard extraneous renegotiation attempts once the V3 link
14528 protocol has been initiated. Failure to do so left us open to
14529 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
14530 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
14532 o Internal abstraction features:
14533 - Introduce new channel_t abstraction between circuits and
14534 or_connection_t to allow for implementing alternate OR-to-OR
14535 transports. A channel_t is an abstract object which can either be a
14536 cell-bearing channel, which is responsible for authenticating and
14537 handshaking with the remote OR and transmitting cells to and from
14538 it, or a listening channel, which spawns new cell-bearing channels
14539 at the request of remote ORs. Implements part of ticket 6465.
14540 - Also new is the channel_tls_t subclass of channel_t, adapting it
14541 to the existing or_connection_t code. The V2/V3 protocol handshaking
14542 code which formerly resided in command.c has been moved below the
14543 channel_t abstraction layer and may be found in channeltls.c now.
14544 Implements the rest of ticket 6465.
14545 - Introduce new circuitmux_t storing the queue of circuits for
14546 a channel; this encapsulates and abstracts the queue logic and
14547 circuit selection policy, and allows the latter to be overridden
14548 easily by switching out a policy object. The existing EWMA behavior
14549 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
14551 o Required libraries:
14552 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
14553 strongly recommended.
14556 - Warn users who run hidden services on a Tor client with
14557 UseEntryGuards disabled that their hidden services will be
14558 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
14559 attack which motivated Tor to support entry guards in the first
14560 place). Resolves ticket 6889.
14561 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
14562 dhill. Resolves ticket 6982.
14563 - Option OutboundBindAddress can be specified multiple times and
14564 accepts IPv6 addresses. Resolves ticket 6876.
14566 o Minor bugfixes (also in 0.2.3.23-rc):
14567 - Don't serve or accept v2 hidden service descriptors over a
14568 relay's DirPort. It's never correct to do so, and disabling it
14569 might make it more annoying to exploit any bugs that turn up in the
14570 descriptor-parsing code. Fixes bug 7149.
14571 - Fix two cases in src/or/transports.c where we were calling
14572 fmt_addr() twice in a parameter list. Bug found by David
14573 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
14574 - Fix memory leaks whenever we logged any message about the "path
14575 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
14576 - When relays refuse a "create" cell because their queue of pending
14577 create cells is too big (typically because their cpu can't keep up
14578 with the arrival rate), send back reason "resource limit" rather
14579 than reason "internal", so network measurement scripts can get a
14580 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
14583 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
14584 - Free some more still-in-use memory at exit, to make hunting for
14585 memory leaks easier. Resolves bug 7029.
14586 - When a Tor client gets a "truncated" relay cell, the first byte of
14587 its payload specifies why the circuit was truncated. We were
14588 ignoring this 'reason' byte when tearing down the circuit, resulting
14589 in the controller not being told why the circuit closed. Now we
14590 pass the reason from the truncated cell to the controller. Bugfix
14591 on 0.1.2.3-alpha; fixes bug 7039.
14592 - Downgrade "Failed to hand off onionskin" messages to "debug"
14593 severity, since they're typically redundant with the "Your computer
14594 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
14595 - Make clients running with IPv6 bridges connect over IPv6 again,
14596 even without setting new config options ClientUseIPv6 and
14597 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
14598 - Use square brackets around IPv6 addresses in numerous places
14599 that needed them, including log messages, HTTPS CONNECT proxy
14600 requests, TransportProxy statefile entries, and pluggable transport
14601 extra-info lines. Fixes bug 7011; patch by David Fifield.
14603 o Code refactoring and cleanup:
14604 - Source files taken from other packages now reside in src/ext;
14605 previously they were scattered around the rest of Tor.
14606 - Avoid use of reserved identifiers in our C code. The C standard
14607 doesn't like us declaring anything that starts with an
14608 underscore, so let's knock it off before we get in trouble. Fix
14609 for bug 1031; bugfix on the first Tor commit.
14612 Changes in version 0.2.3.23-rc - 2012-10-20
14613 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
14614 vulnerability introduced by a change in OpenSSL, and fixes a variety
14615 of smaller bugs in preparation for the release.
14617 o New directory authorities:
14618 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
14619 authority. Closes ticket 5749.
14621 o Major bugfixes (security/privacy):
14622 - Disable TLS session tickets. OpenSSL's implementation was giving
14623 our TLS session keys the lifetime of our TLS context objects, when
14624 perfect forward secrecy would want us to discard anything that
14625 could decrypt a link connection as soon as the link connection
14626 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
14627 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
14628 - Discard extraneous renegotiation attempts once the V3 link
14629 protocol has been initiated. Failure to do so left us open to
14630 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
14631 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
14634 - Fix a possible crash bug when checking for deactivated circuits
14635 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
14636 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
14638 o Minor bugfixes (on 0.2.3.x):
14639 - Fix two cases in src/or/transports.c where we were calling
14640 fmt_addr() twice in a parameter list. Bug found by David
14641 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
14642 - Convert an assert in the pathbias code to a log message. The assert
14643 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
14644 bugfix on 0.2.3.17-beta.
14645 - Fix memory leaks whenever we logged any message about the "path
14646 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
14648 o Minor bugfixes (on 0.2.2.x and earlier):
14649 - Don't serve or accept v2 hidden service descriptors over a relay's
14650 DirPort. It's never correct to do so, and disabling it might
14651 make it more annoying to exploit any bugs that turn up in the
14652 descriptor-parsing code. Fixes bug 7149.
14653 - When relays refuse a "create" cell because their queue of pending
14654 create cells is too big (typically because their cpu can't keep up
14655 with the arrival rate), send back reason "resource limit" rather
14656 than reason "internal", so network measurement scripts can get a
14657 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
14658 - Correct file sizes when reading binary files on Cygwin, to avoid
14659 a bug where Tor would fail to read its state file. Fixes bug 6844;
14660 bugfix on 0.1.2.7-alpha.
14661 - Avoid undefined behavior when parsing the list of supported
14662 rendezvous/introduction protocols in a hidden service descriptor.
14663 Previously, Tor would have confused (as-yet-unused) protocol version
14664 numbers greater than 32 with lower ones on many platforms. Fixes
14665 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
14667 o Documentation fixes:
14668 - Clarify that hidden services are TCP only. Fixes bug 6024.
14671 Changes in version 0.2.4.3-alpha - 2012-09-22
14672 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
14673 assertion, resumes letting relays test reachability of their DirPort,
14674 and cleans up a bunch of smaller bugs.
14677 - Fix an assertion failure in tor_timegm() that could be triggered
14678 by a badly formatted directory object. Bug found by fuzzing with
14679 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
14682 - Fix a possible crash bug when checking for deactivated circuits
14683 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
14684 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
14685 - Allow routers to detect that their own DirPorts are running. When
14686 we removed support for versions_supports_begindir, we also
14687 accidentally removed the mechanism we used to self-test our
14688 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
14689 bugfix on 0.2.4.2-alpha.
14691 o Security features:
14692 - Switch to a completely time-invariant approach for picking nodes
14693 weighted by bandwidth. Our old approach would run through the
14694 part of the loop after it had made its choice slightly slower
14695 than it ran through the part of the loop before it had made its
14696 choice. Addresses ticket 6538.
14697 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
14698 by tor2web clients allows hidden services to identify tor2web
14699 clients through their repeated selection of the same rendezvous
14700 and introduction point circuit endpoints (their guards). Resolves
14704 - Enable Tor to read configuration, state, and key information from
14705 a FIFO. Previously Tor would only read from files with a positive
14706 stat.st_size. Code from meejah; fixes bug 6044.
14709 - Correct file sizes when reading binary files on Cygwin, to avoid
14710 a bug where Tor would fail to read its state file. Fixes bug 6844;
14711 bugfix on 0.1.2.7-alpha.
14712 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
14713 bugfix on 0.2.0.3-alpha.
14714 - When complaining about a client port on a public address, log
14715 which address we're complaining about. Fixes bug 4020; bugfix on
14716 0.2.3.3-alpha. Patch by Tom Fitzhenry.
14717 - Convert an assert in the pathbias code to a log message. The assert
14718 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
14719 bugfix on 0.2.3.17-beta.
14720 - Our new buildsystem was overzealous about rebuilding manpages: it
14721 would rebuild them all whenever any one of them changed. Now our
14722 dependency checking should be correct. Fixes bug 6843; bugfix on
14724 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
14725 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
14726 - Correct log printout about which address family is preferred
14727 when connecting to a bridge with both an IPv4 and IPv6 OR port.
14728 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
14730 o Minor bugfixes (code cleanliness):
14731 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
14732 with large values. This situation was untriggered, but nevertheless
14733 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
14734 - Reject consensus votes with more than 64 known-flags. We aren't even
14735 close to that limit yet, and our code doesn't handle it correctly.
14736 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
14737 - Avoid undefined behavior when parsing the list of supported
14738 rendezvous/introduction protocols in a hidden service descriptor.
14739 Previously, Tor would have confused (as-yet-unused) protocol version
14740 numbers greater than 32 with lower ones on many platforms. Fixes
14741 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
14742 - Fix handling of rendezvous client authorization types over 8.
14743 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
14744 - Fix building with older versions of GCC (2.95, for one) that don't
14745 like preprocessor directives inside macro arguments. Found by
14746 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
14747 - Switch weighted node selection rule from using a list of doubles
14748 to using a list of int64_t. This change should make the process
14749 slightly easier to debug and maintain. Needed to finish ticket 6538.
14751 o Code simplification and refactoring:
14752 - Move the generic "config" code into a new file, and have "config.c"
14753 hold only torrc- and state-related code. Resolves ticket 6823.
14754 - Move the core of our "choose a weighted element at random" logic
14755 into its own function, and give it unit tests. Now the logic is
14756 testable, and a little less fragile too.
14757 - Removed the testing_since field of node_t, which hasn't been used
14758 for anything since 0.2.0.9-alpha.
14760 o Documentation fixes:
14761 - Clarify that hidden services are TCP only. Fixes bug 6024.
14762 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
14766 Changes in version 0.2.3.22-rc - 2012-09-11
14767 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
14771 - Fix an assertion failure in tor_timegm() that could be triggered
14772 by a badly formatted directory object. Bug found by fuzzing with
14773 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
14776 - Avoid segfault when starting up having run with an extremely old
14777 version of Tor and parsing its state file. Fixes bug 6801; bugfix
14781 Changes in version 0.2.2.39 - 2012-09-11
14782 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
14786 - Fix an assertion failure in tor_timegm() that could be triggered
14787 by a badly formatted directory object. Bug found by fuzzing with
14788 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
14789 - Do not crash when comparing an address with port value 0 to an
14790 address policy. This bug could have been used to cause a remote
14791 assertion failure by or against directory authorities, or to
14792 allow some applications to crash clients. Fixes bug 6690; bugfix
14796 Changes in version 0.2.4.2-alpha - 2012-09-10
14797 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
14798 raises the default rate limiting even more, and makes the bootstrapping
14799 log messages less noisy.
14802 - Automatically forward the TCP ports of pluggable transport
14803 proxies using tor-fw-helper if PortForwarding is enabled. Implements
14807 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
14808 to 1GB/1GB. The previous defaults were intended to be "basically
14809 infinite", but it turns out they're now limiting our 100mbit+
14810 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
14811 last time we raised it).
14814 - Detect when we're running with a version of OpenSSL other than the
14815 one we compiled with. This has occasionally given people hard-to-
14817 - Log fewer lines at level "notice" about our OpenSSL and Libevent
14818 versions and capabilities when everything is going right. Resolves
14819 part of ticket 6736.
14820 - Directory authorities no long accept descriptors for any version of
14821 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
14822 These versions are insecure, unsupported, or both. Implements
14826 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
14827 to start with a triple-underscore so the controller won't touch it.
14828 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
14829 - Avoid segfault when starting up having run with an extremely old
14830 version of Tor and parsing its state file. Fixes bug 6801; bugfix
14832 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
14833 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
14834 - Don't follow the NULL pointer if microdescriptor generation fails.
14835 (This does not appear to be triggerable, but it's best to be safe.)
14836 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
14837 - Fix mis-declared dependencies on src/common/crypto.c and
14838 src/or/tor_main.c that could break out-of-tree builds under some
14839 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
14840 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
14841 6778; bugfix on 0.2.4.1-alpha.
14842 - Fix a harmless (in this case) build warning for implicitly
14843 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
14845 o Removed features:
14846 - Now that all versions before 0.2.2.x are disallowed, we no longer
14847 need to work around their missing features. Thus we can remove a
14848 bunch of compatibility code.
14850 o Code refactoring:
14851 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
14852 TCP ports to forward. In the past it only accepted two ports:
14853 the ORPort and the DirPort.
14856 Changes in version 0.2.4.1-alpha - 2012-09-05
14857 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
14858 bridgedb; lets relays use IPv6 addresses and directory authorities
14859 advertise them; and switches to a cleaner build interface.
14861 This is the first alpha release in a new series, so expect there to
14862 be bugs. Users who would rather test out a more stable branch should
14863 stay with 0.2.3.x for now.
14865 o Major features (bridges):
14866 - Bridges now report the pluggable transports they support to the
14867 bridge authority, so it can pass the supported transports on to
14868 bridgedb and/or eventually do reachability testing. Implements
14871 o Major features (IPv6):
14872 - Bridge authorities now accept IPv6 bridge addresses and include
14873 them in network status documents. Implements ticket 5534.
14874 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
14875 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
14876 to happen. Implements ticket 5535.
14877 - All kind of relays, not just bridges, can now advertise an IPv6
14878 OR port. Implements ticket 6362.
14879 - Directory authorities vote on IPv6 OR ports using the new consensus
14880 method 14. Implements ticket 6363.
14882 o Major features (build):
14883 - Switch to a nonrecursive Makefile structure. Now instead of each
14884 Makefile.am invoking other Makefile.am's, there is a master
14885 Makefile.am that includes the others. This change makes our build
14886 process slightly more maintainable, and improves parallelism for
14887 building with make -j. Original patch by Stewart Smith; various
14888 fixes by Jim Meyering.
14889 - Where available, we now use automake's "silent" make rules by
14890 default, so that warnings are easier to spot. You can get the old
14891 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
14893 o Minor features (code security and spec conformance):
14894 - Clear keys and key-derived material left on the stack in
14895 rendservice.c and rendclient.c. Check return value of
14896 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
14897 These fixes should make us more forward-secure against cold-boot
14898 attacks and the like. Fixes bug 2385.
14899 - Reject EXTEND cells sent to nonexistent streams. According to the
14900 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
14901 we were only checking for stream IDs that were currently in use.
14902 Found while hunting for more instances of bug 6271. Bugfix on
14903 0.0.2pre8, which introduced incremental circuit construction.
14905 o Minor features (streamlining);
14906 - No longer include the "opt" prefix when generating routerinfos
14907 or v2 directories: it has been needless since Tor 0.1.2. Closes
14909 - Remove some now-needless code that tried to aggressively flush
14910 OR connections as data was added to them. Since 0.2.0.1-alpha, our
14911 cell queue logic has saved us from the failure mode that this code
14912 was supposed to prevent. Removing this code will limit the number
14913 of baroque control flow paths through Tor's network logic. Reported
14914 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
14916 o Minor features (controller):
14917 - Add a "GETINFO signal/names" control port command. Implements
14919 - Provide default values for all options via "GETINFO config/defaults".
14920 Implements ticket 4971.
14922 o Minor features (IPv6):
14923 - New config option "AuthDirHasIPv6Connectivity 1" that directory
14924 authorities should set if they have IPv6 connectivity and want to
14925 do reachability tests for IPv6 relays. Implements feature 5974.
14926 - A relay with an IPv6 OR port now sends that address in NETINFO
14927 cells (in addition to its other address). Implements ticket 6364.
14929 o Minor features (log messages):
14930 - Omit the first heartbeat log message, because it never has anything
14931 useful to say, and it clutters up the bootstrapping messages.
14932 Resolves ticket 6758.
14933 - Don't log about reloading the microdescriptor cache at startup. Our
14934 bootstrap warnings are supposed to tell the user when there's a
14935 problem, and our bootstrap notices say when there isn't. Resolves
14936 ticket 6759; bugfix on 0.2.2.6-alpha.
14937 - Don't log "I learned some more directory information" when we're
14938 reading cached directory information. Reserve it for when new
14939 directory information arrives in response to a fetch. Resolves
14941 - Prevent rounding error in path bias counts when scaling
14942 them down, and use the correct scale factor default. Also demote
14943 some path bias related log messages down a level and make others
14944 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
14945 - We no longer warn so much when generating manpages from their
14948 o Code simplifications and refactoring:
14949 - Enhance our internal sscanf replacement so that we can eliminate
14950 the last remaining uses of the system sscanf. (Though those uses
14951 of sscanf were safe, sscanf itself is generally error prone, so
14952 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
14954 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
14955 - Move last_reachable and testing_since from routerinfo_t to node_t.
14956 Implements ticket 5529.
14957 - Add replaycache_t structure, functions and unit tests, then refactor
14958 rend_service_introduce() to be more clear to read, improve, debug,
14959 and test. Resolves bug 6177.
14960 - Finally remove support for malloc_good_size and malloc_usable_size.
14961 We had hoped that these functions would let us eke a little more
14962 memory out of our malloc implementation. Unfortunately, the only
14963 implementations that provided these functions are also ones that
14964 are already efficient about not overallocation: they never got us
14965 more than 7 or so bytes per allocation. Removing them saves us a
14966 little code complexity and a nontrivial amount of build complexity.
14968 o New requirements:
14969 - Tor maintainers now require Automake version 1.9 or later to build
14970 Tor from the Git repository. (Automake is not required when building
14971 from a source distribution.)
14974 Changes in version 0.2.3.21-rc - 2012-09-05
14975 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
14976 series. It fixes a trio of potential security bugs, fixes a bug where
14977 we were leaving some of the fast relays out of the microdescriptor
14978 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
14979 and cleans up other smaller issues.
14981 o Major bugfixes (security):
14982 - Tear down the circuit if we get an unexpected SENDME cell. Clients
14983 could use this trick to make their circuits receive cells faster
14984 than our flow control would have allowed, or to gum up the network,
14985 or possibly to do targeted memory denial-of-service attacks on
14986 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
14987 from July 2002, before the release of Tor 0.0.0. We had committed
14988 this patch previously, but we had to revert it because of bug 6271.
14989 Now that 6271 is fixed, this patch appears to work.
14990 - Reject any attempt to extend to an internal address. Without
14991 this fix, a router could be used to probe addresses on an internal
14992 network to see whether they were accepting connections. Fixes bug
14993 6710; bugfix on 0.0.8pre1.
14994 - Do not crash when comparing an address with port value 0 to an
14995 address policy. This bug could have been used to cause a remote
14996 assertion failure by or against directory authorities, or to
14997 allow some applications to crash clients. Fixes bug 6690; bugfix
15001 - Remove the upper bound on microdescriptor length. We were hitting
15002 the limit for routers with complex exit policies or family
15003 declarations, causing clients to not use them. Fixes the first
15004 piece of bug 6404; fix on 0.2.2.6-alpha.
15005 - Detect "ORPort 0" as meaning, uniformly, that we're not running
15006 as a relay. Previously, some of our code would treat the presence
15007 of any ORPort line as meaning that we should act like a relay,
15008 even though our new listener code would correctly not open any
15009 ORPorts for ORPort 0. Similar bugs in other Port options are also
15010 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
15013 - Avoid a pair of double-free and use-after-mark bugs that can
15014 occur with certain timings in canceled and re-received DNS
15015 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
15016 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
15017 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
15018 - Allow one-hop directory fetching circuits the full "circuit build
15019 timeout" period, rather than just half of it, before failing them
15020 and marking the relay down. This fix should help reduce cases where
15021 clients declare relays (or worse, bridges) unreachable because
15022 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
15023 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
15025 - Authorities no longer include any router in their microdescriptor
15026 consensuses for which they couldn't generate or agree on a
15027 microdescriptor. Fixes the second piece of bug 6404; fix on
15029 - Detect and reject attempts to specify both "FooPort" and
15030 "FooPort 0" in the same configuration domain. (It's still okay
15031 to have a FooPort in your configuration file, and use "FooPort 0"
15032 on the command line to disable it.) Fixes the second half of bug
15033 6507; bugfix on 0.2.3.3-alpha.
15034 - Make wildcarded addresses (that is, ones beginning with "*.") work
15035 when provided via the controller's MapAddress command. Previously,
15036 they were accepted, but we never actually noticed that they were
15037 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
15038 - Avoid crashing on a malformed state file where EntryGuardPathBias
15039 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
15040 - Add a (probably redundant) memory clear between iterations of
15041 the router status voting loop, to prevent future coding errors
15042 where data might leak between iterations of the loop. Resolves
15045 o Minor bugfixes (log messages):
15046 - Downgrade "set buildtimeout to low value" messages to "info"
15047 severity; they were never an actual problem, there was never
15048 anything reasonable to do about them, and they tended to spam logs
15049 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
15050 - Downgrade path-bias warning messages to "info". We'll try to get
15051 them working better in 0.2.4. Add internal circuit construction
15052 state to protect against the noisy warn message "Unexpectedly high
15053 circuit_successes". Also add some additional rate-limited notice
15054 messages to help determine the root cause of the warn. Fixes bug
15055 6475. Bugfix against 0.2.3.17-beta.
15056 - Move log message when unable to find a microdesc in a routerstatus
15057 entry to parse time. Previously we'd spam this warning every time
15058 we tried to figure out which microdescriptors to download. Fixes
15059 the third piece of bug 6404; fix on 0.2.3.18-rc.
15062 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
15063 change when the authority is deciding whether to accept a newly
15064 uploaded descriptor. Implements ticket 6423.
15065 - Add missing documentation for consensus and microdesc files.
15066 Resolves ticket 6732.
15069 Changes in version 0.2.2.38 - 2012-08-12
15070 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
15071 attack that could in theory leak path information.
15074 - Avoid an uninitialized memory read when reading a vote or consensus
15075 document that has an unrecognized flavor name. This read could
15076 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
15077 - Try to leak less information about what relays a client is
15078 choosing to a side-channel attacker. Previously, a Tor client would
15079 stop iterating through the list of available relays as soon as it
15080 had chosen one, thus finishing a little earlier when it picked
15081 a router earlier in the list. If an attacker can recover this
15082 timing information (nontrivial but not proven to be impossible),
15083 they could learn some coarse-grained information about which relays
15084 a client was picking (middle nodes in particular are likelier to
15085 be affected than exits). The timing attack might be mitigated by
15086 other factors (see bug 6537 for some discussion), but it's best
15087 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
15090 Changes in version 0.2.3.20-rc - 2012-08-05
15091 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
15092 series. It fixes a pair of code security bugs and a potential anonymity
15093 issue, updates our RPM spec files, and cleans up other smaller issues.
15096 - Avoid read-from-freed-memory and double-free bugs that could occur
15097 when a DNS request fails while launching it. Fixes bug 6480;
15098 bugfix on 0.2.0.1-alpha.
15099 - Avoid an uninitialized memory read when reading a vote or consensus
15100 document that has an unrecognized flavor name. This read could
15101 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
15102 - Try to leak less information about what relays a client is
15103 choosing to a side-channel attacker. Previously, a Tor client would
15104 stop iterating through the list of available relays as soon as it
15105 had chosen one, thus finishing a little earlier when it picked
15106 a router earlier in the list. If an attacker can recover this
15107 timing information (nontrivial but not proven to be impossible),
15108 they could learn some coarse-grained information about which relays
15109 a client was picking (middle nodes in particular are likelier to
15110 be affected than exits). The timing attack might be mitigated by
15111 other factors (see bug 6537 for some discussion), but it's best
15112 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
15115 - Try to make the warning when giving an obsolete SOCKSListenAddress
15116 a little more useful.
15117 - Terminate active server managed proxies if Tor stops being a
15118 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
15119 - Provide a better error message about possible OSX Asciidoc failure
15120 reasons. Fixes bug 6436.
15121 - Warn when Tor is configured to use accounting in a way that can
15122 link a hidden service to some other hidden service or public
15123 address. Resolves ticket 6490.
15126 - Check return value of fputs() when writing authority certificate
15127 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
15128 - Ignore ServerTransportPlugin lines when Tor is not configured as
15129 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
15130 - When disabling guards for having too high a proportion of failed
15131 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
15135 - Update our default RPM spec files to work with mock and rpmbuild
15136 on RHEL/Fedora. They have an updated set of dependencies and
15137 conflicts, a fix for an ancient typo when creating the "_tor"
15138 user, and better instructions. Thanks to Ondrej Mikle for the
15139 patch series. Fixes bug 6043.
15142 - Make it possible to set the TestingTorNetwork configuration
15143 option using AlternateDirAuthority and AlternateBridgeAuthority
15144 as an alternative to setting DirServer. Addresses ticket 6377.
15147 - Clarify the documentation for the Alternate*Authority options.
15149 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
15151 o Code simplification and refactoring:
15152 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
15153 10 lines. Also, don't nest them. Doing so in the past has
15154 led to hard-to-debug code. The new style is to use the
15155 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
15158 Changes in version 0.2.3.19-rc - 2012-07-06
15159 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
15160 series. It fixes the compile on Windows, reverts to a GeoIP database
15161 that isn't as broken, and fixes a flow control bug that has been around
15162 since the beginning of Tor.
15165 - Fix a bug handling SENDME cells on nonexistent streams that could
15166 result in bizarre window values. Report and patch contributed
15167 pseudonymously. Fixes part of bug 6271. This bug was introduced
15168 before the first Tor release, in svn commit r152.
15169 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
15170 June 2012 database, Maxmind marked many Tor relays as country "A1",
15171 which will cause risky behavior for clients that set EntryNodes
15172 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
15173 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
15174 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
15177 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
15178 bugfix on 0.2.1.10-alpha.
15181 Changes in version 0.2.3.18-rc - 2012-06-28
15182 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
15183 series. It fixes a few smaller bugs, but generally appears stable.
15184 Please test it and let us know whether it is!
15187 - Allow wildcarded mapaddress targets to be specified on the
15188 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
15189 - Make our linker option detection code more robust against linkers
15190 such as on FreeBSD 8, where a bad combination of options completes
15191 successfully but makes an unrunnable binary. Fixes bug 6173;
15192 bugfix on 0.2.3.17-beta.
15194 o Minor bugfixes (on 0.2.2.x and earlier):
15195 - Avoid a false positive in the util/threads unit test by increasing
15196 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
15197 - Replace "Sending publish request" log messages with "Launching
15198 upload", so that they no longer confusingly imply that we're
15199 sending something to a directory we might not even be connected
15200 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
15201 - Make sure to set *socket_error in all error cases in
15202 connection_connect(), so it can't produce a warning about
15203 errno being zero from errno_to_orconn_end_reason(). Bugfix on
15204 0.2.1.1-alpha; resolves ticket 6028.
15205 - Downgrade "Got a certificate, but we already have it" log messages
15206 from warning to info, except when we're a dirauth. Fixes bug 5238;
15207 bugfix on 0.2.1.7-alpha.
15208 - When checking for requested signatures on the latest consensus
15209 before serving it to a client, make sure to check the right
15210 consensus flavor. Bugfix on 0.2.2.6-alpha.
15211 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
15212 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
15214 o Minor bugfixes (on 0.2.3.x):
15215 - Make format_helper_exit_status() avoid unnecessary space padding
15216 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
15218 - Downgrade a message about cleaning the microdescriptor cache to
15219 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
15220 - Log a BUG message at severity INFO if we have a networkstatus with
15221 a missing entry for some microdescriptor. Continues on a patch
15223 - Improve the log message when a managed proxy fails to launch. Fixes
15224 bug 5099; bugfix on 0.2.3.6-alpha.
15225 - Don't do DNS lookups when parsing corrupted managed proxy protocol
15226 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
15227 - When formatting wildcarded address mappings for the controller,
15228 be sure to include "*." as appropriate. Partially fixes bug 6244;
15229 bugfix on 0.2.3.9-alpha.
15230 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
15231 Bugfix on 0.2.3.13-alpha.
15232 - Stop logging messages about running with circuit timeout learning
15233 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
15234 - Disable a spurious warning about reading on a marked and flushing
15235 connection. We shouldn't be doing that, but apparently we
15236 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
15237 - Fix a bug that stopped AllowDotExit from working on addresses
15238 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
15241 o Code simplification, refactoring, unit tests:
15242 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
15243 Libevent's notion of cached time when possible.
15244 - Remove duplicate code for invoking getrlimit() from control.c.
15245 - Add a unit test for the environment_variable_names_equal function.
15248 - Document the --defaults-torrc option, and the new (in 0.2.3)
15249 semantics for overriding, extending, and clearing lists of
15250 options. Closes bug 4748.
15253 Changes in version 0.2.3.17-beta - 2012-06-15
15254 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
15255 gets our TLS handshake back on track for being able to blend in with
15256 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
15257 with Vidalia, and otherwise continues to get us closer to a release
15261 - Enable gcc and ld hardening by default. Resolves ticket 5210.
15262 - Update TLS cipher list to match Firefox 8 and later. Resolves
15264 - Implement the client side of proposal 198: remove support for
15265 clients falsely claiming to support standard ciphersuites that
15266 they can actually provide. As of modern OpenSSL versions, it's not
15267 necessary to fake any standard ciphersuite, and doing so prevents
15268 us from using better ciphersuites in the future, since servers
15269 can't know whether an advertised ciphersuite is really supported or
15270 not. Some hosts -- notably, ones with very old versions of OpenSSL
15271 or where OpenSSL has been built with ECC disabled -- will stand
15272 out because of this change; TBB users should not be affected.
15275 - Change the default value for DynamicDHGroups (introduced in
15276 0.2.3.9-alpha) to 0. This feature can make Tor relays less
15277 identifiable by their use of the mod_ssl DH group, but at
15278 the cost of some usability (#4721) and bridge tracing (#6087)
15279 regressions. Resolves ticket 5598.
15280 - Send a CRLF at the end of each STATUS_* control protocol event. This
15281 bug tickled a bug in Vidalia which would make it freeze. Fixes
15282 bug 6094; bugfix on 0.2.3.16-alpha.
15285 - Disable writing on marked-for-close connections when they are
15286 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
15287 bug 5263; bugfix on 0.0.2pre13, where we first added a special
15288 case for flushing marked connections.
15289 - Detect SSL handshake even when the initial attempt to write the
15290 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
15291 - Change the AllowDotExit rules so they should actually work.
15292 We now enforce AllowDotExit only immediately after receiving an
15293 address via SOCKS or DNSPort: other sources are free to provide
15294 .exit addresses after the resolution occurs. Fixes bug 3940;
15295 bugfix on 0.2.2.1-alpha.
15296 - Fix a (harmless) integer overflow in cell statistics reported by
15297 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
15298 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
15299 right places and never depends on the consensus parameters or
15300 computes adaptive timeouts when it is disabled. Fixes bug 5049;
15301 bugfix on 0.2.2.14-alpha.
15302 - When building Tor on Windows with -DUNICODE (not default), ensure
15303 that error messages, filenames, and DNS server names are always
15304 NUL-terminated when we convert them to a single-byte encoding.
15305 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
15306 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
15307 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
15308 - Fix an edge case where TestingTorNetwork is set but the authorities
15309 and relays all have an uptime of zero, where the private Tor network
15310 could briefly lack support for hidden services. Fixes bug 3886;
15311 bugfix on 0.2.2.18-alpha.
15312 - Correct the manpage's descriptions for the default values of
15313 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
15315 - Fix the documentation for the --hush and --quiet command line
15316 options, which changed their behavior back in 0.2.3.3-alpha.
15317 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
15321 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
15322 more information to it, so that we can track it down in case it
15323 returns again. Mitigates bug 5235.
15324 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
15325 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
15326 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
15327 - Warn the user when HTTPProxy, but no other proxy type, is
15328 configured. This can cause surprising behavior: it doesn't send
15329 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
15330 directory traffic only. Resolves ticket 4663.
15331 - Issue a notice if a guard completes less than 40% of your circuits.
15332 Threshold is configurable by torrc option PathBiasNoticeRate and
15333 consensus parameter pb_noticepct. There is additional, off-by-
15334 default code to disable guards which fail too many circuits.
15335 Addresses ticket 5458.
15336 - Update to the June 6 2012 Maxmind GeoLite Country database.
15338 o Code simplifications and refactoring:
15339 - Remove validate_pluggable_transports_config(): its warning
15340 message is now handled by connection_or_connect().
15343 Changes in version 0.2.2.37 - 2012-06-06
15344 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
15345 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
15349 - Work around a bug in OpenSSL that broke renegotiation with TLS
15350 1.1 and TLS 1.2. Without this workaround, all attempts to speak
15351 the v2 Tor connection protocol when both sides were using OpenSSL
15352 1.0.1 would fail. Resolves ticket 6033.
15353 - When waiting for a client to renegotiate, don't allow it to add
15354 any bytes to the input buffer. This fixes a potential DoS issue.
15355 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
15356 - Fix an edge case where if we fetch or publish a hidden service
15357 descriptor, we might build a 4-hop circuit and then use that circuit
15358 for exiting afterwards -- even if the new last hop doesn't obey our
15359 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
15362 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
15363 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
15366 - Tell GCC and Clang to check for any errors in format strings passed
15367 to the tor_v*(print|scan)f functions.
15370 Changes in version 0.2.3.16-alpha - 2012-06-05
15371 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
15372 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
15373 currently). It also fixes a variety of smaller bugs and other cleanups
15374 that get us closer to a release candidate.
15376 o Major bugfixes (general):
15377 - Work around a bug in OpenSSL that broke renegotiation with TLS
15378 1.1 and TLS 1.2. Without this workaround, all attempts to speak
15379 the v2 Tor connection protocol when both sides were using OpenSSL
15380 1.0.1 would fail. Resolves ticket 6033.
15381 - When waiting for a client to renegotiate, don't allow it to add
15382 any bytes to the input buffer. This fixes a potential DoS issue.
15383 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
15384 - Pass correct OR address to managed proxies (like obfsproxy),
15385 even when ORListenAddress is used. Fixes bug 4865; bugfix on
15387 - The advertised platform of a router now includes only its operating
15388 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
15389 service pack level (for Windows) or its CPU architecture (for Unix).
15390 We also no longer include the "git-XYZ" tag in the version. Resolves
15393 o Major bugfixes (clients):
15394 - If we are unable to find any exit that supports our predicted ports,
15395 stop calling them predicted, so that we don't loop and build
15396 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
15397 which introduced predicted ports.
15398 - Fix an edge case where if we fetch or publish a hidden service
15399 descriptor, we might build a 4-hop circuit and then use that circuit
15400 for exiting afterwards -- even if the new last hop doesn't obey our
15401 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
15402 - Check at each new consensus whether our entry guards were picked
15403 long enough ago that we should rotate them. Previously, we only
15404 did this check at startup, which could lead to us holding a guard
15405 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
15406 - When fetching a bridge descriptor from a bridge authority,
15407 always do so anonymously, whether we have been able to open
15408 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
15409 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
15410 but we'll need to wait for bug 6010 before it's actually usable.
15412 o Major bugfixes (directory authorities):
15413 - When computing weight parameters, behave more robustly in the
15414 presence of a bad bwweightscale value. Previously, the authorities
15415 would crash if they agreed on a sufficiently broken weight_scale
15416 value: now, they use a reasonable default and carry on. Partial
15417 fix for 5786; bugfix on 0.2.2.17-alpha.
15418 - Check more thoroughly to prevent a rogue authority from
15419 double-voting on any consensus directory parameter. Previously,
15420 authorities would crash in this case if the total number of
15421 votes for any parameter exceeded the number of active voters,
15422 but would let it pass otherwise. Partial fix for bug 5786; bugfix
15426 - Rate-limit log messages when asked to connect anonymously to
15427 a private address. When these hit, they tended to hit fast and
15428 often. Also, don't bother trying to connect to addresses that we
15429 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
15430 reply makes us think we have been lied to, even when the address the
15431 client tried to connect to was "localhost." Resolves ticket 2822.
15432 - Allow packagers to insert an extra string in server descriptor
15433 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
15434 Resolves the rest of ticket 2988.
15435 - Raise the threshold of server descriptors needed (75%) and exit
15436 server descriptors needed (50%) before we will declare ourselves
15437 bootstrapped. This will make clients start building circuits a
15438 little later, but makes the initially constructed circuits less
15439 skewed and less in conflict with further directory fetches. Fixes
15441 - Close any connection that sends unrecognized junk before the
15442 handshake. Solves an issue noted in bug 4369.
15443 - Improve log messages about managed transports. Resolves ticket 5070.
15444 - Tag a bridge's descriptor as "never to be sent unencrypted".
15445 This shouldn't matter, since bridges don't open non-anonymous
15446 connections to the bridge authority and don't allow unencrypted
15447 directory connections from clients, but we might as well make
15448 sure. Closes bug 5139.
15449 - Expose our view of whether we have gone dormant to the controller,
15450 via a new "GETINFO dormant" value. Torbutton and other controllers
15451 can use this to avoid doing periodic requests through Tor while
15452 it's dormant (bug 4718). Fixes bug 5954.
15453 - Tell GCC and Clang to check for any errors in format strings passed
15454 to the tor_v*(print|scan)f functions.
15455 - Update to the May 1 2012 Maxmind GeoLite Country database.
15457 o Minor bugfixes (already included in 0.2.2.36):
15458 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
15459 Fixes bug 5346; bugfix on 0.0.8pre3.
15460 - Correct parsing of certain date types in parse_http_time().
15461 Without this patch, If-Modified-Since would behave
15462 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
15463 Esteban Manchado Velázques.
15464 - Make our number-parsing functions always treat too-large values
15465 as an error, even when those values exceed the width of the
15466 underlying type. Previously, if the caller provided these
15467 functions with minima or maxima set to the extreme values of the
15468 underlying integer type, these functions would return those
15469 values on overflow rather than treating overflow as an error.
15470 Fixes part of bug 5786; bugfix on 0.0.9.
15471 - If we hit the error case where routerlist_insert() replaces an
15472 existing (old) server descriptor, make sure to remove that
15473 server descriptor from the old_routers list. Fix related to bug
15474 1776. Bugfix on 0.2.2.18-alpha.
15475 - Clarify the behavior of MaxCircuitDirtiness with hidden service
15476 circuits. Fixes issue 5259.
15478 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
15479 - Prevent a null-pointer dereference when receiving a data cell
15480 for a nonexistent stream when the circuit in question has an
15481 empty deliver window. We don't believe this is triggerable,
15482 since we don't currently allow deliver windows to become empty,
15483 but the logic is tricky enough that it's better to make the code
15484 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
15485 - Fix a memory leak when trying to launch a DNS request when the
15486 network is disabled or the nameservers are unconfigurable. Fixes
15487 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
15488 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
15489 - Don't hold a Windows file handle open for every file mapping;
15490 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
15492 - Avoid O(n^2) performance characteristics when parsing a large
15493 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
15494 - Format more doubles with %f, not %lf. Patch from grarpamp to make
15495 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
15497 - Make our replacement implementation of strtok_r() compatible with
15498 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
15499 bugfix on 0.2.2.1-alpha.
15500 - Fix a NULL-pointer dereference on a badly formed
15501 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
15502 bugfix on 0.2.2.9-alpha.
15503 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
15504 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
15505 - Defensively refactor rend_mid_rendezvous() so that protocol
15506 violations and length checks happen in the beginning. Fixes
15508 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
15509 that IPv6 stuff will compile on MSVC, and compilation issues
15510 will be easier to track down. Fixes bug 5861.
15512 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
15513 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
15514 resource exhaustion, so that clients can adjust their load to
15515 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
15516 started using END_STREAM_REASON_RESOURCELIMIT.
15517 - Don't check for whether the address we're using for outbound
15518 connections has changed until after the outbound connection has
15519 completed. On Windows, getsockname() doesn't succeed until the
15520 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
15521 - If the configuration tries to set MyFamily on a bridge, refuse to
15522 do so, and warn about the security implications. Fixes bug 4657;
15523 bugfix on 0.2.0.3-alpha.
15524 - If the client fails to set a reasonable set of ciphersuites
15525 during its v2 handshake renegotiation, allow the renegotiation to
15526 continue nevertheless (i.e. send all the required certificates).
15527 Fixes bug 4591; bugfix on 0.2.0.20-rc.
15528 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
15529 option is set to 0 (which Vidalia version 0.2.16 now does when
15530 a SAVECONF attempt fails), perform other actions that SIGHUP
15531 usually causes (like reopening the logs). Fixes bug 5095; bugfix
15533 - If we fail to write a microdescriptor to the disk cache, do not
15534 continue replacing the old microdescriptor file. Fixes bug 2954;
15535 bugfix on 0.2.2.6-alpha.
15536 - Exit nodes don't need to fetch certificates for authorities that
15537 they don't recognize; only directory authorities, bridges,
15538 and caches need to do that. Fixes part of bug 2297; bugfix on
15540 - Correctly handle checking the permissions on the parent
15541 directory of a control socket in the root directory. Bug found
15542 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
15544 - When told to add a bridge with the same digest as a preexisting
15545 bridge but a different addr:port, change the addr:port as
15546 requested. Previously we would not notice the change. Fixes half
15547 of bug 5603; fix on 0.2.2.26-beta.
15548 - End AUTHCHALLENGE error messages (in the control protocol) with
15549 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
15551 o Minor bugfixes (on 0.2.3.x):
15552 - Turn an assertion (that the number of handshakes received as a
15553 server is not < 1) into a warning. Fixes bug 4873; bugfix on
15555 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
15556 we had reversed them when the answer was cached.) Fixes bug
15557 5723; bugfix on 0.2.3.1-alpha.
15558 - Work correctly on Linux systems with accept4 support advertised in
15559 their headers, but without accept4 support in the kernel. Fix
15560 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
15561 - When told to add a bridge with the same addr:port as a preexisting
15562 bridge but a different transport, change the transport as
15563 requested. Previously we would not notice the change. Fixes half
15564 of bug 5603; fix on 0.2.3.2-alpha.
15565 - Avoid a "double-reply" warning when replying to a SOCKS request
15566 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
15567 bugfix on 0.2.3.4-alpha.
15568 - Fix a bug where a bridge authority crashes if it has seen no
15569 directory requests when it's time to write statistics to disk.
15570 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
15572 - Don't try to open non-control listeners when DisableNetwork is set.
15573 Previously, we'd open all listeners, then immediately close them.
15574 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
15575 - Don't abort the managed proxy protocol if the managed proxy
15576 sends us an unrecognized line; ignore it instead. Fixes bug
15577 5910; bugfix on 0.2.3.9-alpha.
15578 - Fix a compile warning in crypto.c when compiling with clang 3.1.
15579 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
15580 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
15581 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
15582 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
15583 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
15584 - Resolve numerous small warnings and build issues with MSVC. Resolves
15587 o Documentation fixes:
15588 - Improve the manual's documentation for the NT Service command-line
15589 options. Addresses ticket 3964.
15590 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
15591 - Document the changes to the ORPort and DirPort options, and the
15592 fact that {OR/Dir}ListenAddress is now unnecessary (and
15593 therefore deprecated). Resolves ticket 5597.
15596 - Remove the torrc.bridge file: we don't use it for anything, and
15597 it had become badly desynchronized from torrc.sample. Resolves
15601 Changes in version 0.2.2.36 - 2012-05-24
15602 Tor 0.2.2.36 updates the addresses for two of the eight directory
15603 authorities, fixes some potential anonymity and security issues,
15604 and fixes several crash bugs.
15606 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
15607 known flaws, and nobody should be using them. You should upgrade. If
15608 you're using a Linux or BSD and its packages are obsolete, stop using
15609 those packages and upgrade anyway.
15611 o Directory authority changes:
15612 - Change IP address for maatuska (v3 directory authority).
15613 - Change IP address for ides (v3 directory authority), and rename
15617 - When building or running with any version of OpenSSL earlier
15618 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
15619 versions have a bug (CVE-2011-4576) in which their block cipher
15620 padding includes uninitialized data, potentially leaking sensitive
15621 information to any peer with whom they make a SSLv3 connection. Tor
15622 does not use SSL v3 by default, but a hostile client or server
15623 could force an SSLv3 connection in order to gain information that
15624 they shouldn't have been able to get. The best solution here is to
15625 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
15626 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
15627 to make sure that the bug can't happen.
15628 - Never use a bridge or a controller-supplied node as an exit, even
15629 if its exit policy allows it. Found by wanoskarnet. Fixes bug
15630 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
15631 and 0.2.0.3-alpha (for bridge-purpose descriptors).
15632 - Only build circuits if we have a sufficient threshold of the total
15633 descriptors that are marked in the consensus with the "Exit"
15634 flag. This mitigates an attack proposed by wanoskarnet, in which
15635 all of a client's bridges collude to restrict the exit nodes that
15636 the client knows about. Fixes bug 5343.
15637 - Provide controllers with a safer way to implement the cookie
15638 authentication mechanism. With the old method, if another locally
15639 running program could convince a controller that it was the Tor
15640 process, then that program could trick the controller into telling
15641 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
15642 authentication method uses a challenge-response approach to prevent
15643 this attack. Fixes bug 5185; implements proposal 193.
15646 - Avoid logging uninitialized data when unable to decode a hidden
15647 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
15648 - Avoid a client-side assertion failure when receiving an INTRODUCE2
15649 cell on a general purpose circuit. Fixes bug 5644; bugfix on
15651 - Fix builds when the path to sed, openssl, or sha1sum contains
15652 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
15654 - Correct our replacements for the timeradd() and timersub() functions
15655 on platforms that lack them (for example, Windows). The timersub()
15656 function is used when expiring circuits, while timeradd() is
15657 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
15658 bugfix on 0.2.2.24-alpha.
15659 - Fix the SOCKET_OK test that we use to tell when socket
15660 creation fails so that it works on Win64. Fixes part of bug 4533;
15661 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
15664 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
15665 Fixes bug 5346; bugfix on 0.0.8pre3.
15666 - Make our number-parsing functions always treat too-large values
15667 as an error, even when those values exceed the width of the
15668 underlying type. Previously, if the caller provided these
15669 functions with minima or maxima set to the extreme values of the
15670 underlying integer type, these functions would return those
15671 values on overflow rather than treating overflow as an error.
15672 Fixes part of bug 5786; bugfix on 0.0.9.
15673 - Older Linux kernels erroneously respond to strange nmap behavior
15674 by having accept() return successfully with a zero-length
15675 socket. When this happens, just close the connection. Previously,
15676 we would try harder to learn the remote address: but there was
15677 no such remote address to learn, and our method for trying to
15678 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
15679 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
15680 - Correct parsing of certain date types in parse_http_time().
15681 Without this patch, If-Modified-Since would behave
15682 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
15683 Esteban Manchado Velázques.
15684 - Change the BridgePassword feature (part of the "bridge community"
15685 design, which is not yet implemented) to use a time-independent
15686 comparison. The old behavior might have allowed an adversary
15687 to use timing to guess the BridgePassword value. Fixes bug 5543;
15688 bugfix on 0.2.0.14-alpha.
15689 - Detect and reject certain misformed escape sequences in
15690 configuration values. Previously, these values would cause us
15691 to crash if received in a torrc file or over an authenticated
15692 control port. Bug found by Esteban Manchado Velázquez, and
15693 independently by Robert Connolly from Matta Consulting who further
15694 noted that it allows a post-authentication heap overflow. Patch
15695 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
15696 bugfix on 0.2.0.16-alpha.
15697 - Fix a compile warning when using the --enable-openbsd-malloc
15698 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
15699 - During configure, detect when we're building with clang version
15700 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
15701 CFLAGS. clang doesn't support them yet.
15702 - When sending an HTTP/1.1 proxy request, include a Host header.
15703 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
15704 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
15705 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
15706 - If we hit the error case where routerlist_insert() replaces an
15707 existing (old) server descriptor, make sure to remove that
15708 server descriptor from the old_routers list. Fix related to bug
15709 1776. Bugfix on 0.2.2.18-alpha.
15711 o Minor bugfixes (documentation and log messages):
15712 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
15713 Fixes bug 4856; bugfix on Tor 0.0.6.
15714 - Update "ClientOnly" man page entry to explain that there isn't
15715 really any point to messing with it. Resolves ticket 5005.
15716 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
15717 directory authority option (introduced in Tor 0.2.2.34).
15718 - Downgrade the "We're missing a certificate" message from notice
15719 to info: people kept mistaking it for a real problem, whereas it
15720 is seldom the problem even when we are failing to bootstrap. Fixes
15721 bug 5067; bugfix on 0.2.0.10-alpha.
15722 - Correctly spell "connect" in a log message on failure to create a
15723 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
15724 - Clarify the behavior of MaxCircuitDirtiness with hidden service
15725 circuits. Fixes issue 5259.
15728 - Directory authorities now reject versions of Tor older than
15729 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
15730 inclusive. These versions accounted for only a small fraction of
15731 the Tor network, and have numerous known security issues. Resolves
15733 - Update to the May 1 2012 Maxmind GeoLite Country database.
15736 - When sending or relaying a RELAY_EARLY cell, we used to convert
15737 it to a RELAY cell if the connection was using the v1 link
15738 protocol. This was a workaround for older versions of Tor, which
15739 didn't handle RELAY_EARLY cells properly. Now that all supported
15740 versions can handle RELAY_EARLY cells, and now that we're enforcing
15741 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
15742 remove this workaround. Addresses bug 4786.
15745 Changes in version 0.2.3.15-alpha - 2012-04-30
15746 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
15747 the development branch build on Windows again.
15749 o Minor bugfixes (on 0.2.2.x and earlier):
15750 - Make sure that there are no unhandled pending TLS errors before
15751 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
15752 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
15753 Bugfix on 0.1.0.5-rc; fixes bug 4528.
15754 - Fix an assert that directory authorities could trigger on sighup
15755 during some configuration state transitions. We now don't treat
15756 it as a fatal error when the new descriptor we just generated in
15757 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
15758 - After we pick a directory mirror, we would refuse to use it if
15759 it's in our ExcludeExitNodes list, resulting in mysterious failures
15760 to bootstrap for people who just wanted to avoid exiting from
15761 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
15762 - When building with --enable-static-tor on OpenBSD, do not
15763 erroneously attempt to link -lrt. Fixes bug 5103.
15765 o Minor bugfixes (on 0.2.3.x):
15766 - When Tor is built with kernel headers from a recent (last few
15767 years) Linux kernel, do not fail to run on older (pre-2.6.28
15768 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
15769 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
15770 and 0.2.3.12-alpha.
15771 - Fix compilation with miniupnpc version 1.6; patch from
15772 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
15773 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
15774 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
15775 - Fix compilation on platforms without unistd.h, or where environ
15776 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
15779 - Directory authorities are now a little more lenient at accepting
15780 older router descriptors, or newer router descriptors that don't
15781 make big changes. This should help ameliorate past and future
15782 issues where routers think they have uploaded valid descriptors,
15783 but the authorities don't think so. Fix for ticket 2479.
15784 - Make the code that clients use to detect an address change be
15785 IPv6-aware, so that it won't fill clients' logs with error
15786 messages when trying to get the IPv4 address of an IPv6
15787 connection. Implements ticket 5537.
15789 o Removed features:
15790 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
15791 authorities needed to use it for a while to keep the network working
15792 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
15793 that was six months ago. As of now, it should no longer be needed
15797 Changes in version 0.2.3.14-alpha - 2012-04-23
15798 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
15799 candidate. It also dramatically speeds up AES: fast relays should
15800 consider switching to the newer OpenSSL library.
15802 o Directory authority changes:
15803 - Change IP address for ides (v3 directory authority), and rename
15807 - Avoid logging uninitialized data when unable to decode a hidden
15808 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
15809 - Avoid a client-side assertion failure when receiving an INTRODUCE2
15810 cell on a general purpose circuit. Fixes bug 5644; bugfix on
15812 - If authorities are unable to get a v2 consensus document from other
15813 directory authorities, they no longer fall back to fetching
15814 them from regular directory caches. Fixes bug 5635; bugfix on
15815 0.2.2.26-beta, where routers stopped downloading v2 consensus
15816 documents entirely.
15817 - When we start a Tor client with a normal consensus already cached,
15818 be willing to download a microdescriptor consensus. Fixes bug 4011;
15819 fix on 0.2.3.1-alpha.
15821 o Major features (performance):
15822 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
15823 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
15824 vectorized AES implementations as appropriate. These can be much,
15825 much faster than other AES implementations.
15827 o Minor bugfixes (0.2.2.x and earlier):
15828 - Don't launch more than 10 service-side introduction-point circuits
15829 for a hidden service in five minutes. Previously, we would consider
15830 launching more introduction-point circuits if at least one second
15831 had passed without any introduction-point circuits failing. Fixes
15832 bug 4607; bugfix on 0.0.7pre1.
15833 - Change the BridgePassword feature (part of the "bridge community"
15834 design, which is not yet implemented) to use a time-independent
15835 comparison. The old behavior might have allowed an adversary
15836 to use timing to guess the BridgePassword value. Fixes bug 5543;
15837 bugfix on 0.2.0.14-alpha.
15838 - Enforce correct return behavior of tor_vsscanf() when the '%%'
15839 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
15840 - When sending an HTTP/1.1 proxy request, include a Host header.
15841 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
15842 - Don't log that we have "decided to publish new relay descriptor"
15843 unless we are actually publishing a descriptor. Fixes bug 3942;
15844 bugfix on 0.2.2.28-beta.
15846 o Minor bugfixes (0.2.3.x):
15847 - Fix a bug where a bridge authority crashes (on a failed assert)
15848 if it has seen no directory requests when it's time to write
15849 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
15850 - Fix bug stomping on ORPort option NoListen and ignoring option
15851 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
15852 - In the testsuite, provide a large enough buffer in the tor_sscanf
15853 unit test. Otherwise we'd overrun that buffer and crash during
15854 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
15856 - Make sure we create the keys directory if it doesn't exist and we're
15857 about to store the dynamic Diffie-Hellman parameters. Fixes bug
15858 5572; bugfix on 0.2.3.13-alpha.
15859 - Fix a small memory leak when trying to decode incorrect base16
15860 authenticator during SAFECOOKIE authentication. Found by
15861 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
15864 - Add more information to a log statement that might help track down
15865 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
15866 non-IP address" messages (or any Bug messages, for that matter!),
15867 please let us know about it.
15868 - Relays now understand an IPv6 address when they get one from a
15869 directory server. Resolves ticket 4875.
15870 - Resolve IPv6 addresses in bridge and entry statistics to country
15871 code "??" which means we at least count them. Resolves ticket 5053;
15872 improves on 0.2.3.9-alpha.
15873 - Update to the April 3 2012 Maxmind GeoLite Country database.
15874 - Begin a doc/state-contents.txt file to explain the contents of
15875 the Tor state file. Fixes bug 2987.
15877 o Default torrc changes:
15878 - Stop listing "socksport 9050" in torrc.sample. We open a socks
15879 port on 9050 by default anyway, so this should not change anything
15881 - Stop mentioning the deprecated *ListenAddress options in
15882 torrc.sample. Fixes bug 5438.
15883 - Document unit of bandwidth related options in sample torrc.
15886 o Removed features:
15887 - The "torify" script no longer supports the "tsocks" socksifier
15888 tool, since tsocks doesn't support DNS and UDP right for Tor.
15889 Everyone should be using torsocks instead. Fixes bugs 3530 and
15890 5180. Based on a patch by "ugh".
15892 o Code refactoring:
15893 - Change the symmetric cipher interface so that creating and
15894 initializing a stream cipher are no longer separate functions.
15895 - Remove all internal support for unpadded RSA. We never used it, and
15896 it would be a bad idea to start.
15899 Changes in version 0.2.3.13-alpha - 2012-03-26
15900 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
15901 in managed pluggable transports, as well as providing other cleanups
15902 that get us closer to a release candidate.
15904 o Directory authority changes:
15905 - Change IP address for maatuska (v3 directory authority).
15908 - Provide controllers with a safer way to implement the cookie
15909 authentication mechanism. With the old method, if another locally
15910 running program could convince a controller that it was the Tor
15911 process, then that program could trick the controller into telling
15912 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
15913 authentication method uses a challenge-response approach to prevent
15914 this attack. Fixes bug 5185, implements proposal 193.
15915 - Never use a bridge or a controller-supplied node as an exit, even
15916 if its exit policy allows it. Found by wanoskarnet. Fixes bug
15917 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
15918 and 0.2.0.3-alpha (for bridge-purpose descriptors).
15919 - Only build circuits if we have a sufficient threshold of the total
15920 descriptors that are marked in the consensus with the "Exit"
15921 flag. This mitigates an attack proposed by wanoskarnet, in which
15922 all of a client's bridges collude to restrict the exit nodes that
15923 the client knows about. Fixes bug 5343.
15925 o Major bugfixes (on Tor 0.2.3.x):
15926 - Avoid an assert when managed proxies like obfsproxy are configured,
15927 and we receive HUP signals or setconf attempts too rapidly. This
15928 situation happens most commonly when Vidalia tries to attach to
15929 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
15930 bugfix on 0.2.3.6-alpha.
15931 - Fix a relay-side pluggable transports bug where managed proxies were
15932 unreachable from the Internet, because Tor asked them to bind on
15933 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
15934 - Stop discarding command-line arguments when TestingTorNetwork
15935 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
15936 0.2.3.9-alpha, where task 4552 added support for two layers of
15938 - Resume allowing the unit tests to run in gdb. This was accidentally
15939 made impossible when the DisableDebuggerAttachment option was
15940 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
15941 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
15942 0.2.3.11-alpha. Reported by Anthony G. Basile.
15944 o Minor bugfixes (on 0.2.2.x and earlier):
15945 - Ensure we don't cannibalize circuits that are longer than three hops
15946 already, so we don't end up making circuits with 5 or more
15947 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
15948 0.1.0.1-rc which introduced cannibalization.
15949 - Detect and reject certain misformed escape sequences in
15950 configuration values. Previously, these values would cause us
15951 to crash if received in a torrc file or over an authenticated
15952 control port. Bug found by Esteban Manchado Velázquez, and
15953 independently by Robert Connolly from Matta Consulting who further
15954 noted that it allows a post-authentication heap overflow. Patch
15955 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
15956 bugfix on 0.2.0.16-alpha.
15957 - Fix a compile warning when using the --enable-openbsd-malloc
15958 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
15959 - Directory caches no longer refuse to clean out descriptors because
15960 of missing v2 networkstatus documents, unless they're configured
15961 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
15962 0.2.2.26-beta. Patch by Daniel Bryg.
15963 - Update to the latest version of the tinytest unit testing framework.
15964 This includes a couple of bugfixes that can be relevant for
15965 running forked unit tests on Windows, and removes all reserved
15968 o Minor bugfixes (on 0.2.3.x):
15969 - On a failed pipe() call, don't leak file descriptors. Fixes bug
15970 4296; bugfix on 0.2.3.1-alpha.
15971 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
15972 until after we have received a CERTS cell. Fixes bug 4361; bugfix
15973 on 0.2.3.6-alpha. Patch by "frosty".
15974 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
15975 option, so that the IP stack doesn't decide to use it for IPv4
15976 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
15977 - Ensure that variables set in Tor's environment cannot override
15978 environment variables that Tor passes to a managed
15979 pluggable-transport proxy. Previously, Tor would pass every
15980 variable in its environment to managed proxies along with the new
15981 ones, in such a way that on many operating systems, the inherited
15982 environment variables would override those which Tor tried to
15983 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
15984 bugfix on 0.2.3.9-alpha for Windows.
15987 - A wide variety of new unit tests by Esteban Manchado Velázquez.
15988 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
15989 - Update to the March 6 2012 Maxmind GeoLite Country database.
15992 Changes in version 0.2.3.12-alpha - 2012-02-13
15993 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
15994 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
15995 when Tor is configured to use a pluggable transport like obfsproxy.
15998 - Fix builds when the path to sed, openssl, or sha1sum contains
15999 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
16001 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
16002 connections. This change should allow busy exit relays to stop
16003 running out of available sockets as quickly. Fixes bug 4950;
16004 bugfix on 0.2.2.26-beta.
16005 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
16006 would ask the bridge for microdescriptors, which are only supported
16007 in 0.2.3.x, and then fail to bootstrap when it didn't get the
16008 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
16009 - Properly set up obfsproxy's environment when in managed mode. The
16010 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
16011 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
16012 5076 and 5082; bugfix on 0.2.3.6-alpha.
16015 - Use the dead_strip option when building Tor on OS X. This reduces
16016 binary size by almost 19% when linking openssl and libevent
16017 statically, which we do for Tor Browser Bundle.
16018 - Fix broken URLs in the sample torrc file, and tell readers about
16019 the OutboundBindAddress, ExitPolicyRejectPrivate, and
16020 PublishServerDescriptor options. Addresses bug 4652.
16021 - Update to the February 7 2012 Maxmind GeoLite Country database.
16024 - Downgrade the "We're missing a certificate" message from notice
16025 to info: people kept mistaking it for a real problem, whereas it
16026 is seldom the problem even when we are failing to bootstrap. Fixes
16027 bug 5067; bugfix on 0.2.0.10-alpha.
16028 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
16029 managed pluggable transport server proxy's environment.
16030 Previously, we would put it there, even though Tor doesn't
16031 implement an 'extended server port' yet, and even though Tor
16032 almost certainly isn't listening at that address. For now, we set
16033 it to an empty string to avoid crashing older obfsproxies. Bugfix
16035 - Log the heartbeat message every HeartbeatPeriod seconds, not every
16036 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
16037 0.2.3.1-alpha. Bug reported by Scott Bennett.
16038 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
16039 bugfix on 0.2.3.11-alpha.
16040 - Update "ClientOnly" man page entry to explain that there isn't
16041 really any point to messing with it. Resolves ticket 5005.
16042 - Use the correct CVE number for CVE-2011-4576 in our comments and
16043 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
16046 o Code simplifications and refactoring:
16047 - Use the _WIN32 macro throughout our code to detect Windows.
16048 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
16052 Changes in version 0.2.3.11-alpha - 2012-01-22
16053 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
16054 the last step of the plan to limit maximum circuit length, includes
16055 a wide variety of hidden service performance and correctness fixes,
16056 works around an OpenSSL security flaw if your distro is too stubborn
16057 to upgrade, and fixes a bunch of smaller issues.
16060 - Now that Tor 0.2.0.x is completely deprecated, enable the final
16061 part of "Proposal 110: Avoiding infinite length circuits" by
16062 refusing all circuit-extend requests that do not use a relay_early
16063 cell. This change helps Tor resist a class of denial-of-service
16064 attacks by limiting the maximum circuit length.
16065 - Adjust the number of introduction points that a hidden service
16066 will try to maintain based on how long its introduction points
16067 remain in use and how many introductions they handle. Fixes
16069 - Try to use system facilities for enumerating local interface
16070 addresses, before falling back to our old approach (which was
16071 binding a UDP socket, and calling getsockname() on it). That
16072 approach was scaring OS X users whose draconian firewall
16073 software warned about binding to UDP sockets, regardless of
16074 whether packets were sent. Now we try to use getifaddrs(),
16075 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
16076 system supports. Resolves ticket 1827.
16078 o Major security workaround:
16079 - When building or running with any version of OpenSSL earlier
16080 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
16081 versions have a bug (CVE-2011-4576) in which their block cipher
16082 padding includes uninitialized data, potentially leaking sensitive
16083 information to any peer with whom they make a SSLv3 connection. Tor
16084 does not use SSL v3 by default, but a hostile client or server
16085 could force an SSLv3 connection in order to gain information that
16086 they shouldn't have been able to get. The best solution here is to
16087 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
16088 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
16089 to make sure that the bug can't happen.
16092 - Fix the SOCKET_OK test that we use to tell when socket
16093 creation fails so that it works on Win64. Fixes part of bug 4533;
16094 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
16095 - Correct our replacements for the timeradd() and timersub() functions
16096 on platforms that lack them (for example, Windows). The timersub()
16097 function is used when expiring circuits, while timeradd() is
16098 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
16099 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
16100 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
16101 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
16102 bug at runtime, not compile time, because some distributions hack
16103 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
16104 on 0.2.3.9-alpha. Found by Pascal.
16106 o Minor features (controller):
16107 - Use absolute path names when reporting the torrc filename in the
16108 control protocol, so a controller can more easily find the torrc
16109 file. Resolves bug 1101.
16110 - Extend the control protocol to report flags that control a circuit's
16111 path selection in CIRC events and in replies to 'GETINFO
16112 circuit-status'. Implements part of ticket 2411.
16113 - Extend the control protocol to report the hidden service address
16114 and current state of a hidden-service-related circuit in CIRC
16115 events and in replies to 'GETINFO circuit-status'. Implements part
16117 - When reporting the path to the cookie file to the controller,
16118 give an absolute path. Resolves ticket 4881.
16119 - Allow controllers to request an event notification whenever a
16120 circuit is cannibalized or its purpose is changed. Implements
16121 part of ticket 3457.
16122 - Include the creation time of a circuit in CIRC and CIRC2
16123 control-port events and the list produced by the 'GETINFO
16124 circuit-status' control-port command.
16126 o Minor features (directory authorities):
16127 - Directory authorities now reject versions of Tor older than
16128 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
16129 inclusive. These versions accounted for only a small fraction of
16130 the Tor network, and have numerous known security issues. Resolves
16132 - Authority operators can now vote for all relays in a given
16133 set of countries to be BadDir/BadExit/Invalid/Rejected.
16134 - Provide two consensus parameters (FastFlagMinThreshold and
16135 FastFlagMaxThreshold) to control the range of allowable bandwidths
16136 for the Fast directory flag. These allow authorities to run
16137 experiments on appropriate requirements for being a "Fast" node.
16138 The AuthDirFastGuarantee config value still applies. Implements
16140 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
16141 directory authority option (introduced in Tor 0.2.2.34).
16143 o Minor features (other):
16144 - Don't disable the DirPort when we cannot exceed our AccountingMax
16145 limit during this interval because the effective bandwidthrate is
16146 low enough. This is useful in a situation where AccountMax is only
16147 used as an additional safeguard or to provide statistics.
16148 - Prepend an informative header to generated dynamic_dh_params files.
16149 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
16150 EntryNodes will have no effect. Resolves issue 2571.
16151 - Log more useful messages when we fail to disable debugger
16153 - Log which authority we're missing votes from when we go to fetch
16154 them from the other auths.
16155 - Log (at debug level) whenever a circuit's purpose is changed.
16156 - Add missing documentation for the MaxClientCircuitsPending,
16157 UseMicrodescriptors, UserspaceIOCPBuffers, and
16158 _UseFilteringSSLBufferevents options, all introduced during
16159 the 0.2.3.x series.
16160 - Update to the January 3 2012 Maxmind GeoLite Country database.
16162 o Minor bugfixes (hidden services):
16163 - Don't close hidden service client circuits which have almost
16164 finished connecting to their destination when they reach
16165 the normal circuit-build timeout. Previously, we would close
16166 introduction circuits which are waiting for an acknowledgement
16167 from the introduction point, and rendezvous circuits which have
16168 been specified in an INTRODUCE1 cell sent to a hidden service,
16169 after the normal CBT. Now, we mark them as 'timed out', and launch
16170 another rendezvous attempt in parallel. This behavior change can
16171 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
16172 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
16173 - Don't close hidden-service-side rendezvous circuits when they
16174 reach the normal circuit-build timeout. This behavior change can
16175 be disabled using the new
16176 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
16177 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
16178 - Make sure we never mark the wrong rendezvous circuit as having
16179 had its introduction cell acknowledged by the introduction-point
16180 relay. Previously, when we received an INTRODUCE_ACK cell on a
16181 client-side hidden-service introduction circuit, we might have
16182 marked a rendezvous circuit other than the one we specified in
16183 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
16184 a warning message and interfered with the hidden service
16185 connection-establishment process. Fixes bug 4759; bugfix on
16186 0.2.3.3-alpha, when we added the stream-isolation feature which
16187 might cause Tor to open multiple rendezvous circuits for the same
16189 - Don't trigger an assertion failure when we mark a new client-side
16190 hidden-service introduction circuit for close during the process
16191 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
16194 o Minor bugfixes (log messages):
16195 - Correctly spell "connect" in a log message on failure to create a
16196 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
16198 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
16199 Fixes bug 4856; bugfix on Tor 0.0.6.
16200 - Fix the log message describing how we work around discovering
16201 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
16202 4837; bugfix on 0.2.2.9-alpha.
16203 - When logging about a disallowed .exit name, do not also call it
16204 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
16206 o Minor bugfixes (build fixes):
16207 - During configure, detect when we're building with clang version
16208 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
16209 CFLAGS. clang doesn't support them yet.
16210 - During configure, search for library containing cos function as
16211 libm lives in libcore on some platforms (BeOS/Haiku). Linking
16212 against libm was hard-coded before. Fixes the first part of bug
16213 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
16215 - Detect attempts to build Tor on (as yet hypothetical) versions
16216 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
16217 fix for bug 4533. Bugfix on 0.2.2.28-beta.
16218 - Preprocessor directives should not be put inside the arguments
16219 of a macro. This would break compilation with GCC releases prior
16220 to version 3.3. We would never recommend such an old GCC version,
16221 but it is apparently required for binary compatibility on some
16222 platforms (namely, certain builds of Haiku). Fixes the other part
16223 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
16226 o Minor bugfixes (other):
16227 - Older Linux kernels erroneously respond to strange nmap behavior
16228 by having accept() return successfully with a zero-length
16229 socket. When this happens, just close the connection. Previously,
16230 we would try harder to learn the remote address: but there was
16231 no such remote address to learn, and our method for trying to
16232 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
16233 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
16234 - Fix null-pointer access that could occur if TLS allocation failed.
16235 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
16236 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
16237 accidentally been reverted.
16238 - Fix our implementation of crypto_random_hostname() so it can't
16239 overflow on ridiculously large inputs. (No Tor version has ever
16240 provided this kind of bad inputs, but let's be correct in depth.)
16241 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
16242 - Find more places in the code that should have been testing for
16243 invalid sockets using the SOCKET_OK macro. Required for a fix
16244 for bug 4533. Bugfix on 0.2.2.28-beta.
16245 - Fix an assertion failure when, while running with bufferevents, a
16246 connection finishes connecting after it is marked for close, but
16247 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
16248 - test_util_spawn_background_ok() hardcoded the expected value
16249 for ENOENT to 2. This isn't portable as error numbers are
16250 platform specific, and particularly the hurd has ENOENT at
16251 0x40000002. Construct expected string at runtime, using the correct
16252 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
16253 - Reject attempts to disable DisableDebuggerAttachment while Tor is
16254 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
16255 - Use an appropriate-width type for sockets in tor-fw-helper on
16256 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
16259 - When sending or relaying a RELAY_EARLY cell, we used to convert
16260 it to a RELAY cell if the connection was using the v1 link
16261 protocol. This was a workaround for older versions of Tor, which
16262 didn't handle RELAY_EARLY cells properly. Now that all supported
16263 versions can handle RELAY_EARLY cells, and now that we're enforcing
16264 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
16265 remove this workaround. Addresses bug 4786.
16267 o Code simplifications and refactoring:
16268 - Use OpenSSL's built-in SSL_state_string_long() instead of our
16269 own homebrewed ssl_state_to_string() replacement. Patch from
16270 Emile Snyder. Fixes bug 4653.
16271 - Use macros to indicate OpenSSL versions, so we don't need to worry
16272 about accidental hexadecimal bit shifts.
16273 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
16275 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
16276 - Use the smartlist_add_asprintf() alias more consistently.
16277 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
16278 invalid value, rather than just -1.
16279 - Rename a handful of old identifiers, mostly related to crypto
16280 structures and crypto functions. By convention, our "create an
16281 object" functions are called "type_new()", our "free an object"
16282 functions are called "type_free()", and our types indicate that
16283 they are types only with a final "_t". But a handful of older
16284 types and functions broke these rules, with function names like
16285 "type_create" or "subsystem_op_type", or with type names like
16289 Changes in version 0.2.3.10-alpha - 2011-12-16
16290 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
16291 Tor's buffers code. Absolutely everybody should upgrade.
16293 The bug relied on an incorrect calculation when making data continuous
16294 in one of our IO buffers, if the first chunk of the buffer was
16295 misaligned by just the wrong amount. The miscalculation would allow an
16296 attacker to overflow a piece of heap-allocated memory. To mount this
16297 attack, the attacker would need to either open a SOCKS connection to
16298 Tor's SocksPort (usually restricted to localhost), or target a Tor
16299 instance configured to make its connections through a SOCKS proxy
16300 (which Tor does not do by default).
16302 Good security practice requires that all heap-overflow bugs should be
16303 presumed to be exploitable until proven otherwise, so we are treating
16304 this as a potential code execution attack. Please upgrade immediately!
16305 This bug does not affect bufferevents-based builds of Tor. Special
16306 thanks to "Vektor" for reporting this issue to us!
16308 This release also contains a few minor bugfixes for issues discovered
16312 - Fix a heap overflow bug that could occur when trying to pull
16313 data into the first chunk of a buffer, when that chunk had
16314 already had some data drained from it. Fixes CVE-2011-2778;
16315 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
16318 - If we can't attach streams to a rendezvous circuit when we
16319 finish connecting to a hidden service, clear the rendezvous
16320 circuit's stream-isolation state and try to attach streams
16321 again. Previously, we cleared rendezvous circuits' isolation
16322 state either too early (if they were freshly built) or not at all
16323 (if they had been built earlier and were cannibalized). Bugfix on
16324 0.2.3.3-alpha; fixes bug 4655.
16325 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
16326 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
16327 - Fix an assertion failure when a relay with accounting enabled
16328 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
16331 - Update to the December 6 2011 Maxmind GeoLite Country database.
16334 Changes in version 0.2.2.35 - 2011-12-16
16335 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
16336 buffers code. Absolutely everybody should upgrade.
16338 The bug relied on an incorrect calculation when making data continuous
16339 in one of our IO buffers, if the first chunk of the buffer was
16340 misaligned by just the wrong amount. The miscalculation would allow an
16341 attacker to overflow a piece of heap-allocated memory. To mount this
16342 attack, the attacker would need to either open a SOCKS connection to
16343 Tor's SocksPort (usually restricted to localhost), or target a Tor
16344 instance configured to make its connections through a SOCKS proxy
16345 (which Tor does not do by default).
16347 Good security practice requires that all heap-overflow bugs should be
16348 presumed to be exploitable until proven otherwise, so we are treating
16349 this as a potential code execution attack. Please upgrade immediately!
16350 This bug does not affect bufferevents-based builds of Tor. Special
16351 thanks to "Vektor" for reporting this issue to us!
16353 Tor 0.2.2.35 also fixes several bugs in previous versions, including
16354 crash bugs for unusual configurations, and a long-term bug that
16355 would prevent Tor from starting on Windows machines with draconian
16358 With this release, we remind everyone that 0.2.0.x has reached its
16359 formal end-of-life. Those Tor versions have many known flaws, and
16360 nobody should be using them. You should upgrade -- ideally to the
16361 0.2.2.x series. If you're using a Linux or BSD and its packages are
16362 obsolete, stop using those packages and upgrade anyway.
16364 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
16365 longer receive support after some time in early 2012.
16368 - Fix a heap overflow bug that could occur when trying to pull
16369 data into the first chunk of a buffer, when that chunk had
16370 already had some data drained from it. Fixes CVE-2011-2778;
16371 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
16372 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
16373 that it doesn't attempt to allocate a socketpair. This could cause
16374 some problems on Windows systems with overzealous firewalls. Fix for
16375 bug 4457; workaround for Libevent versions 2.0.1-alpha through
16377 - If we mark an OR connection for close based on a cell we process,
16378 don't process any further cells on it. We already avoid further
16379 reads on marked-for-close connections, but now we also discard the
16380 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
16381 which was the first version where we might mark a connection for
16382 close based on processing a cell on it.
16383 - Correctly sanity-check that we don't underflow on a memory
16384 allocation (and then assert) for hidden service introduction
16385 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
16386 bugfix on 0.2.1.5-alpha.
16387 - Fix a memory leak when we check whether a hidden service
16388 descriptor has any usable introduction points left. Fixes bug
16389 4424. Bugfix on 0.2.2.25-alpha.
16390 - Don't crash when we're running as a relay and don't have a GeoIP
16391 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
16392 we've had in the 0.2.3.x branch already.
16393 - When running as a client, do not print a misleading (and plain
16394 wrong) log message that we're collecting "directory request"
16395 statistics: clients don't collect statistics. Also don't create a
16396 useless (because empty) stats file in the stats/ directory. Fixes
16397 bug 4353; bugfix on 0.2.2.34.
16400 - Detect failure to initialize Libevent. This fix provides better
16401 detection for future instances of bug 4457.
16402 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
16403 function. This was eating up hideously large amounts of time on some
16404 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
16405 - Resolve an integer overflow bug in smartlist_ensure_capacity().
16406 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
16408 - Don't warn about unused log_mutex in log.c when building with
16409 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
16410 0.1.0.6-rc which introduced --disable-threads.
16411 - When configuring, starting, or stopping an NT service, stop
16412 immediately after the service configuration attempt has succeeded
16413 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
16414 - When sending a NETINFO cell, include the original address
16415 received for the other side, not its canonical address. Found
16416 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
16417 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
16418 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
16419 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
16420 occurred when a client tried to fetch a descriptor for a bridge
16421 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
16422 - Backport fixes for a pair of compilation warnings on Windows.
16423 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
16424 - If we had ever tried to call tor_addr_to_str on an address of
16425 unknown type, we would have done a strdup on an uninitialized
16426 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
16427 Reported by "troll_un".
16428 - Correctly detect and handle transient lookup failures from
16429 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
16430 Reported by "troll_un".
16431 - Fix null-pointer access that could occur if TLS allocation failed.
16432 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
16433 - Use tor_socket_t type for listener argument to accept(). Fixes bug
16434 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
16437 - Add two new config options for directory authorities:
16438 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
16439 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
16440 that is always sufficient to satisfy the bandwidth requirement for
16441 the Guard flag. Now it will be easier for researchers to simulate
16442 Tor networks with different values. Resolves ticket 4484.
16443 - When Tor ignores a hidden service specified in its configuration,
16444 include the hidden service's directory in the warning message.
16445 Previously, we would only tell the user that some hidden service
16446 was ignored. Bugfix on 0.0.6; fixes bug 4426.
16447 - Update to the December 6 2011 Maxmind GeoLite Country database.
16449 o Packaging changes:
16450 - Make it easier to automate expert package builds on Windows,
16451 by removing an absolute path from makensis.exe command.
16454 Changes in version 0.2.1.32 - 2011-12-16
16455 Tor 0.2.1.32 backports important security and privacy fixes for
16456 oldstable. This release is intended only for package maintainers and
16457 others who cannot use the 0.2.2 stable series. All others should be
16458 using Tor 0.2.2.x or newer.
16460 The Tor 0.2.1.x series will reach formal end-of-life some time in
16461 early 2012; we will stop releasing patches for it then.
16463 o Major bugfixes (also included in 0.2.2.x):
16464 - Correctly sanity-check that we don't underflow on a memory
16465 allocation (and then assert) for hidden service introduction
16466 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
16467 bugfix on 0.2.1.5-alpha.
16468 - Fix a heap overflow bug that could occur when trying to pull
16469 data into the first chunk of a buffer, when that chunk had
16470 already had some data drained from it. Fixes CVE-2011-2778;
16471 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
16474 - Update to the December 6 2011 Maxmind GeoLite Country database.
16477 Changes in version 0.2.3.9-alpha - 2011-12-08
16478 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
16479 a "DisableNetwork" security feature that bundles can use to avoid
16480 touching the network until bridges are configured, moves forward on
16481 the pluggable transport design, fixes a flaw in the hidden service
16482 design that unnecessarily prevented clients with wrong clocks from
16483 reaching hidden services, and fixes a wide variety of other issues.
16486 - Clients can now connect to private bridges over IPv6. Bridges
16487 still need at least one IPv4 address in order to connect to
16488 other relays. Note that we don't yet handle the case where the
16489 user has two bridge lines for the same bridge (one IPv4, one
16490 IPv6). Implements parts of proposal 186.
16491 - New "DisableNetwork" config option to prevent Tor from launching any
16492 connections or accepting any connections except on a control port.
16493 Bundles and controllers can set this option before letting Tor talk
16494 to the rest of the network, for example to prevent any connections
16495 to a non-bridge address. Packages like Orbot can also use this
16496 option to instruct Tor to save power when the network is off.
16497 - Clients and bridges can now be configured to use a separate
16498 "transport" proxy. This approach makes the censorship arms race
16499 easier by allowing bridges to use protocol obfuscation plugins. It
16500 implements the "managed proxy" part of proposal 180 (ticket 3472).
16501 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
16502 implementation. It makes AES_CTR about 7% faster than our old one
16503 (which was about 10% faster than the one OpenSSL used to provide).
16504 Resolves ticket 4526.
16505 - Add a "tor2web mode" for clients that want to connect to hidden
16506 services non-anonymously (and possibly more quickly). As a safety
16507 measure to try to keep users from turning this on without knowing
16508 what they are doing, tor2web mode must be explicitly enabled at
16509 compile time, and a copy of Tor compiled to run in tor2web mode
16510 cannot be used as a normal Tor client. Implements feature 2553.
16511 - Add experimental support for running on Windows with IOCP and no
16512 kernel-space socket buffers. This feature is controlled by a new
16513 "UserspaceIOCPBuffers" config option (off by default), which has
16514 no effect unless Tor has been built with support for bufferevents,
16515 is running on Windows, and has enabled IOCP. This may, in the long
16516 run, help solve or mitigate bug 98.
16517 - Use a more secure consensus parameter voting algorithm. Now at
16518 least three directory authorities or a majority of them must
16519 vote on a given parameter before it will be included in the
16520 consensus. Implements proposal 178.
16523 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
16524 They used to check that the timestamp was within 30 minutes
16525 of their system clock, so they could cap the size of their
16526 replay-detection cache, but that approach unnecessarily refused
16527 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
16528 the v3 intro-point protocol (the first one which sent a timestamp
16529 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
16530 - Only use the EVP interface when AES acceleration is enabled,
16531 to avoid a 5-7% performance regression. Resolves issue 4525;
16532 bugfix on 0.2.3.8-alpha.
16534 o Privacy/anonymity features (bridge detection):
16535 - Make bridge SSL certificates a bit more stealthy by using random
16536 serial numbers, in the same fashion as OpenSSL when generating
16537 self-signed certificates. Implements ticket 4584.
16538 - Introduce a new config option "DynamicDHGroups", enabled by
16539 default, which provides each bridge with a unique prime DH modulus
16540 to be used during SSL handshakes. This option attempts to help
16541 against censors who might use the Apache DH modulus as a static
16542 identifier for bridges. Addresses ticket 4548.
16544 o Minor features (new/different config options):
16545 - New configuration option "DisableDebuggerAttachment" (on by default)
16546 to prevent basic debugging attachment attempts by other processes.
16547 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
16548 - Allow MapAddress directives to specify matches against super-domains,
16549 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
16550 Implements issue 933.
16551 - Slightly change behavior of "list" options (that is, config
16552 options that can appear more than once) when they appear both in
16553 torrc and on the command line. Previously, the command-line options
16554 would be appended to the ones from torrc. Now, the command-line
16555 options override the torrc options entirely. This new behavior
16556 allows the user to override list options (like exit policies and
16557 ports to listen on) from the command line, rather than simply
16558 appending to the list.
16559 - You can get the old (appending) command-line behavior for "list"
16560 options by prefixing the option name with a "+".
16561 - You can remove all the values for a "list" option from the command
16562 line without adding any new ones by prefixing the option name
16564 - Add experimental support for a "defaults" torrc file to be parsed
16565 before the regular torrc. Torrc options override the defaults file's
16566 options in the same way that the command line overrides the torrc.
16567 The SAVECONF controller command saves only those options which
16568 differ between the current configuration and the defaults file. HUP
16569 reloads both files. (Note: This is an experimental feature; its
16570 behavior will probably be refined in future 0.2.3.x-alpha versions
16571 to better meet packagers' needs.) Implements task 4552.
16574 - Try to make the introductory warning message that Tor prints on
16575 startup more useful for actually finding help and information.
16576 Resolves ticket 2474.
16577 - Running "make version" now displays the version of Tor that
16578 we're about to build. Idea from katmagic; resolves issue 4400.
16579 - Expire old or over-used hidden service introduction points.
16580 Required by fix for bug 3460.
16581 - Move the replay-detection cache for the RSA-encrypted parts of
16582 INTRODUCE2 cells to the introduction point data structures.
16583 Previously, we would use one replay-detection cache per hidden
16584 service. Required by fix for bug 3460.
16585 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
16586 public key replay-detection cache from 60 minutes to 5 minutes. This
16587 replay-detection cache is now used only to detect multiple
16588 INTRODUCE2 cells specifying the same rendezvous point, so we can
16589 avoid launching multiple simultaneous attempts to connect to it.
16591 o Minor bugfixes (on Tor 0.2.2.x and earlier):
16592 - Resolve an integer overflow bug in smartlist_ensure_capacity().
16593 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
16595 - Fix a minor formatting issue in one of tor-gencert's error messages.
16597 - Prevent a false positive from the check-spaces script, by disabling
16598 the "whitespace between function name and (" check for functions
16600 - Fix a log message suggesting that people contact a non-existent
16601 email address. Fixes bug 3448.
16602 - Fix null-pointer access that could occur if TLS allocation failed.
16603 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
16604 - Report a real bootstrap problem to the controller on router
16605 identity mismatch. Previously we just said "foo", which probably
16606 made a lot of sense at the time. Fixes bug 4169; bugfix on
16608 - If we had ever tried to call tor_addr_to_str() on an address of
16609 unknown type, we would have done a strdup() on an uninitialized
16610 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
16611 Reported by "troll_un".
16612 - Correctly detect and handle transient lookup failures from
16613 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
16614 Reported by "troll_un".
16615 - Use tor_socket_t type for listener argument to accept(). Fixes bug
16616 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
16617 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
16618 bug 4532; found by "troll_un".
16620 o Minor bugfixes (on Tor 0.2.3.x):
16621 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
16623 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
16624 circuit for use as a hidden service client's rendezvous point.
16625 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
16626 with help from wanoskarnet.
16627 - Restore behavior of overriding SocksPort, ORPort, and similar
16628 options from the command line. Bugfix on 0.2.3.3-alpha.
16631 - Properly handle the case where the build-tree is not the same
16632 as the source tree when generating src/common/common_sha1.i,
16633 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
16634 bugfix on 0.2.0.1-alpha.
16636 o Code simplifications, cleanups, and refactorings:
16637 - Remove the pure attribute from all functions that used it
16638 previously. In many cases we assigned it incorrectly, because the
16639 functions might assert or call impure functions, and we don't have
16640 evidence that keeping the pure attribute is worthwhile. Implements
16641 changes suggested in ticket 4421.
16642 - Remove some dead code spotted by coverity. Fixes cid 432.
16643 Bugfix on 0.2.3.1-alpha, closes bug 4637.
16646 Changes in version 0.2.3.8-alpha - 2011-11-22
16647 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
16648 socketpair-related bug that has been bothering Windows users. It adds
16649 support to serve microdescriptors to controllers, so Vidalia's network
16650 map can resume listing relays (once Vidalia implements its side),
16651 and adds better support for hardware AES acceleration. Finally, it
16652 starts the process of adjusting the bandwidth cutoff for getting the
16653 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
16654 that tiny relays harm performance more than they help network capacity.
16657 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
16658 that it doesn't attempt to allocate a socketpair. This could cause
16659 some problems on Windows systems with overzealous firewalls. Fix for
16660 bug 4457; workaround for Libevent versions 2.0.1-alpha through
16662 - Correctly sanity-check that we don't underflow on a memory
16663 allocation (and then assert) for hidden service introduction
16664 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
16665 bugfix on 0.2.1.5-alpha.
16666 - Remove the artificially low cutoff of 20KB to guarantee the Fast
16667 flag. In the past few years the average relay speed has picked
16668 up, and while the "top 7/8 of the network get the Fast flag" and
16669 "all relays with 20KB or more of capacity get the Fast flag" rules
16670 used to have the same result, now the top 7/8 of the network has
16671 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
16672 - Fix a rare assertion failure when checking whether a v0 hidden
16673 service descriptor has any usable introduction points left, and
16674 we don't have enough information to build a circuit to the first
16675 intro point named in the descriptor. The HS client code in
16676 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
16677 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
16678 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
16679 - Make bridge authorities not crash when they are asked for their own
16680 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
16681 - When running as a client, do not print a misleading (and plain
16682 wrong) log message that we're collecting "directory request"
16683 statistics: clients don't collect statistics. Also don't create a
16684 useless (because empty) stats file in the stats/ directory. Fixes
16685 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
16688 - Allow Tor controllers like Vidalia to obtain the microdescriptor
16689 for a relay by identity digest or nickname. Previously,
16690 microdescriptors were only available by their own digests, so a
16691 controller would have to ask for and parse the whole microdescriptor
16692 consensus in order to look up a single relay's microdesc. Fixes
16693 bug 3832; bugfix on 0.2.3.1-alpha.
16694 - Use OpenSSL's EVP interface for AES encryption, so that all AES
16695 operations can use hardware acceleration (if present). Resolves
16698 o Minor bugfixes (on 0.2.2.x and earlier):
16699 - Detect failure to initialize Libevent. This fix provides better
16700 detection for future instances of bug 4457.
16701 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
16702 function. This was eating up hideously large amounts of time on some
16703 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
16704 - Don't warn about unused log_mutex in log.c when building with
16705 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
16706 0.1.0.6-rc which introduced --disable-threads.
16707 - Allow manual 'authenticate' commands to the controller interface
16708 from netcat (nc) as well as telnet. We were rejecting them because
16709 they didn't come with the expected whitespace at the end of the
16710 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
16711 - Fix some (not actually triggerable) buffer size checks in usage of
16712 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
16714 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
16715 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
16716 - When configuring, starting, or stopping an NT service, stop
16717 immediately after the service configuration attempt has succeeded
16718 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
16719 - When sending a NETINFO cell, include the original address
16720 received for the other side, not its canonical address. Found
16721 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
16722 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
16723 can pick them up when the tests aren't disabled. Bugfix on
16724 0.2.2.4-alpha which introduced tinytest.
16725 - Fix a memory leak when we check whether a hidden service
16726 descriptor has any usable introduction points left. Fixes bug
16727 4424. Bugfix on 0.2.2.25-alpha.
16728 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
16729 occurred when a client tried to fetch a descriptor for a bridge
16730 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
16732 o Minor bugfixes (on 0.2.3.x):
16733 - Make util unit tests build correctly with MSVC. Bugfix on
16734 0.2.3.3-alpha. Patch by Gisle Vanem.
16735 - Successfully detect AUTH_CHALLENGE cells with no recognized
16736 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
16737 Found by frosty_un.
16738 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
16739 it should still send a NETINFO cell to allow the connection to
16740 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
16742 - Log less loudly when we get an invalid authentication certificate
16743 from a source other than a directory authority: it's not unusual
16744 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
16746 - Tolerate servers with more clock skew in their authentication
16747 certificates than previously. Fixes bug 4371; bugfix on
16749 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
16750 on 0.2.3.4-alpha and 0.2.3.6-alpha.
16753 - Add two new config options for directory authorities:
16754 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
16755 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
16756 that is always sufficient to satisfy the bandwidth requirement for
16757 the Guard flag. Now it will be easier for researchers to simulate
16758 Tor networks with different values. Resolves ticket 4484.
16759 - When Tor ignores a hidden service specified in its configuration,
16760 include the hidden service's directory in the warning message.
16761 Previously, we would only tell the user that some hidden service
16762 was ignored. Bugfix on 0.0.6; fixes bug 4426.
16763 - When we fail to initialize Libevent, retry with IOCP disabled so we
16764 don't need to turn on multi-threading support in Libevent, which in
16765 turn requires a working socketpair(). This is a workaround for bug
16766 4457, which affects Libevent versions from 2.0.1-alpha through
16768 - Detect when we try to build on a platform that doesn't define
16769 AF_UNSPEC to 0. We don't work there, so refuse to compile.
16770 - Update to the November 1 2011 Maxmind GeoLite Country database.
16772 o Packaging changes:
16773 - Make it easier to automate expert package builds on Windows,
16774 by removing an absolute path from makensis.exe command.
16776 o Code simplifications and refactoring:
16777 - Remove some redundant #include directives throughout the code.
16778 Patch from Andrea Gelmini.
16779 - Unconditionally use OpenSSL's AES implementation instead of our
16780 old built-in one. OpenSSL's AES has been better for a while, and
16781 relatively few servers should still be on any version of OpenSSL
16782 that doesn't have good optimized assembly AES.
16783 - Use the name "CERTS" consistently to refer to the new cell type;
16784 we were calling it CERT in some places and CERTS in others.
16787 - Numerous new unit tests for functions in util.c and address.c by
16789 - The long-disabled benchmark tests are now split into their own
16790 ./src/test/bench binary.
16791 - The benchmark tests can now use more accurate timers than
16792 gettimeofday() when such timers are available.
16795 Changes in version 0.2.3.7-alpha - 2011-10-30
16796 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
16797 the new v3 handshake. It also resolves yet another bridge address
16801 - If we mark an OR connection for close based on a cell we process,
16802 don't process any further cells on it. We already avoid further
16803 reads on marked-for-close connections, but now we also discard the
16804 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
16805 which was the first version where we might mark a connection for
16806 close based on processing a cell on it.
16807 - Fix a double-free bug that would occur when we received an invalid
16808 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
16809 bugfix on 0.2.3.6-alpha.
16810 - Bridges no longer include their address in NETINFO cells on outgoing
16811 OR connections, to allow them to blend in better with clients.
16812 Removes another avenue for enumerating bridges. Reported by
16813 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
16814 cells were introduced.
16817 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
16818 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
16821 Changes in version 0.2.3.6-alpha - 2011-10-26
16822 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
16823 anonymity vulnerability where an attacker can deanonymize Tor
16824 users. Everybody should upgrade.
16826 This release also features support for a new v3 connection handshake
16827 protocol, and fixes to make hidden service connections more robust.
16830 - Implement a new handshake protocol (v3) for authenticating Tors to
16831 each other over TLS. It should be more resistant to fingerprinting
16832 than previous protocols, and should require less TLS hacking for
16833 future Tor implementations. Implements proposal 176.
16834 - Allow variable-length padding cells to disguise the length of
16835 Tor's TLS records. Implements part of proposal 184.
16837 o Privacy/anonymity fixes (clients):
16838 - Clients and bridges no longer send TLS certificate chains on
16839 outgoing OR connections. Previously, each client or bridge would
16840 use the same cert chain for all outgoing OR connections until
16841 its IP address changes, which allowed any relay that the client
16842 or bridge contacted to determine which entry guards it is using.
16843 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16844 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16845 no longer considers that connection as suitable for satisfying a
16846 circuit EXTEND request. Now relays can protect clients from the
16847 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16848 - Directory authorities no longer assign the Guard flag to relays
16849 that haven't upgraded to the above "refuse EXTEND requests
16850 to client connections" fix. Now directory authorities can
16851 protect clients from the CVE-2011-2768 issue even if neither
16852 the clients nor the relays have upgraded yet. There's a new
16853 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
16854 to let us transition smoothly, else tomorrow there would be no
16857 o Major bugfixes (hidden services):
16858 - Improve hidden service robustness: when an attempt to connect to
16859 a hidden service ends, be willing to refetch its hidden service
16860 descriptors from each of the HSDir relays responsible for them
16861 immediately. Previously, we would not consider refetching the
16862 service's descriptors from each HSDir for 15 minutes after the last
16863 fetch, which was inconvenient if the hidden service was not running
16864 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
16865 - When one of a hidden service's introduction points appears to be
16866 unreachable, stop trying it. Previously, we would keep trying
16867 to build circuits to the introduction point until we lost the
16868 descriptor, usually because the user gave up and restarted Tor.
16869 Partly fixes bug 3825.
16870 - Don't launch a useless circuit after failing to use one of a
16871 hidden service's introduction points. Previously, we would
16872 launch a new introduction circuit, but not set the hidden service
16873 which that circuit was intended to connect to, so it would never
16874 actually be used. A different piece of code would then create a
16875 new introduction circuit correctly. Bug reported by katmagic and
16876 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
16878 o Major bugfixes (other):
16879 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
16880 that they initiated. Relays could distinguish incoming bridge
16881 connections from client connections, creating another avenue for
16882 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
16883 Found by "frosty_un".
16884 - Don't update the AccountingSoftLimitHitAt state file entry whenever
16885 tor gets started. This prevents a wrong average bandwidth
16886 estimate, which would cause relays to always start a new accounting
16887 interval at the earliest possible moment. Fixes bug 2003; bugfix
16888 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
16889 immensely in tracking this bug down.
16890 - Fix a crash bug when changing node restrictions while a DNS lookup
16891 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
16894 o Minor bugfixes (on 0.2.2.x and earlier):
16895 - When a hidden service turns an extra service-side introduction
16896 circuit into a general-purpose circuit, free the rend_data and
16897 intro_key fields first, so we won't leak memory if the circuit
16898 is cannibalized for use as another service-side introduction
16899 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
16900 - Rephrase the log message emitted if the TestSocks check is
16901 successful. Patch from Fabian Keil; fixes bug 4094.
16902 - Bridges now skip DNS self-tests, to act a little more stealthily.
16903 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
16904 bridges. Patch by "warms0x".
16905 - Remove a confusing dollar sign from the example fingerprint in the
16906 man page, and also make the example fingerprint a valid one. Fixes
16907 bug 4309; bugfix on 0.2.1.3-alpha.
16908 - Fix internal bug-checking logic that was supposed to catch
16909 failures in digest generation so that it will fail more robustly
16910 if we ask for a nonexistent algorithm. Found by Coverity Scan.
16911 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
16912 - Report any failure in init_keys() calls launched because our
16913 IP address has changed. Spotted by Coverity Scan. Bugfix on
16914 0.1.1.4-alpha; fixes CID 484.
16916 o Minor bugfixes (on 0.2.3.x):
16917 - Fix a bug in configure.in that kept it from building a configure
16918 script with autoconf versions earlier than 2.61. Fixes bug 2430;
16919 bugfix on 0.2.3.1-alpha.
16920 - Don't warn users that they are exposing a client port to the
16921 Internet if they have specified an RFC1918 address. Previously,
16922 we would warn if the user had specified any non-loopback
16923 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
16924 - Fix memory leaks in the failing cases of the new SocksPort and
16925 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
16926 fixes coverity CIDs 485, 486, and 487.
16929 - When a hidden service's introduction point times out, consider
16930 trying it again during the next attempt to connect to the
16931 HS. Previously, we would not try it again unless a newly fetched
16932 descriptor contained it. Required by fixes for bugs 1297 and 3825.
16933 - The next version of Windows will be called Windows 8, and it has
16934 a major version of 6, minor version of 2. Correctly identify that
16935 version instead of calling it "Very recent version". Resolves
16936 ticket 4153; reported by funkstar.
16937 - The Bridge Authority now writes statistics on how many bridge
16938 descriptors it gave out in total, and how many unique descriptors
16939 it gave out. It also lists how often the most and least commonly
16940 fetched descriptors were given out, as well as the median and
16941 25th/75th percentile. Implements tickets 4200 and 4294.
16942 - Update to the October 4 2011 Maxmind GeoLite Country database.
16944 o Code simplifications and refactoring:
16945 - Remove some old code to remember statistics about which descriptors
16946 we've served as a directory mirror. The feature wasn't used and
16947 is outdated now that microdescriptors are around.
16948 - Rename Tor functions that turn strings into addresses, so that
16949 "parse" indicates that no hostname resolution occurs, and
16950 "lookup" indicates that hostname resolution may occur. This
16951 should help prevent mistakes in the future. Fixes bug 3512.
16954 Changes in version 0.2.2.34 - 2011-10-26
16955 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
16956 can deanonymize Tor users. Everybody should upgrade.
16958 The attack relies on four components: 1) Clients reuse their TLS cert
16959 when talking to different relays, so relays can recognize a user by
16960 the identity key in her cert. 2) An attacker who knows the client's
16961 identity key can probe each guard relay to see if that identity key
16962 is connected to that guard relay right now. 3) A variety of active
16963 attacks in the literature (starting from "Low-Cost Traffic Analysis
16964 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
16965 discover the guard relays that a Tor user visiting the website is using.
16966 4) Clients typically pick three guards at random, so the set of guards
16967 for a given user could well be a unique fingerprint for her. This
16968 release fixes components #1 and #2, which is enough to block the attack;
16969 the other two remain as open research problems. Special thanks to
16970 "frosty_un" for reporting the issue to us!
16972 Clients should upgrade so they are no longer recognizable by the TLS
16973 certs they present. Relays should upgrade so they no longer allow a
16974 remote attacker to probe them to test whether unpatched clients are
16975 currently connected to them.
16977 This release also fixes several vulnerabilities that allow an attacker
16978 to enumerate bridge relays. Some bridge enumeration attacks still
16979 remain; see for example proposal 188.
16981 o Privacy/anonymity fixes (clients):
16982 - Clients and bridges no longer send TLS certificate chains on
16983 outgoing OR connections. Previously, each client or bridge would
16984 use the same cert chain for all outgoing OR connections until
16985 its IP address changes, which allowed any relay that the client
16986 or bridge contacted to determine which entry guards it is using.
16987 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16988 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16989 no longer considers that connection as suitable for satisfying a
16990 circuit EXTEND request. Now relays can protect clients from the
16991 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16992 - Directory authorities no longer assign the Guard flag to relays
16993 that haven't upgraded to the above "refuse EXTEND requests
16994 to client connections" fix. Now directory authorities can
16995 protect clients from the CVE-2011-2768 issue even if neither
16996 the clients nor the relays have upgraded yet. There's a new
16997 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
16998 to let us transition smoothly, else tomorrow there would be no
17001 o Privacy/anonymity fixes (bridge enumeration):
17002 - Bridge relays now do their directory fetches inside Tor TLS
17003 connections, like all the other clients do, rather than connecting
17004 directly to the DirPort like public relays do. Removes another
17005 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
17006 - Bridges relays now build circuits for themselves in a more similar
17007 way to how clients build them. Removes another avenue for
17008 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
17009 when bridges were introduced.
17010 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
17011 that they initiated. Relays could distinguish incoming bridge
17012 connections from client connections, creating another avenue for
17013 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
17014 Found by "frosty_un".
17017 - Fix a crash bug when changing node restrictions while a DNS lookup
17018 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
17020 - Don't launch a useless circuit after failing to use one of a
17021 hidden service's introduction points. Previously, we would
17022 launch a new introduction circuit, but not set the hidden service
17023 which that circuit was intended to connect to, so it would never
17024 actually be used. A different piece of code would then create a
17025 new introduction circuit correctly. Bug reported by katmagic and
17026 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
17029 - Change an integer overflow check in the OpenBSD_Malloc code so
17030 that GCC is less likely to eliminate it as impossible. Patch
17031 from Mansour Moufid. Fixes bug 4059.
17032 - When a hidden service turns an extra service-side introduction
17033 circuit into a general-purpose circuit, free the rend_data and
17034 intro_key fields first, so we won't leak memory if the circuit
17035 is cannibalized for use as another service-side introduction
17036 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
17037 - Bridges now skip DNS self-tests, to act a little more stealthily.
17038 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
17039 bridges. Patch by "warms0x".
17040 - Fix internal bug-checking logic that was supposed to catch
17041 failures in digest generation so that it will fail more robustly
17042 if we ask for a nonexistent algorithm. Found by Coverity Scan.
17043 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
17044 - Report any failure in init_keys() calls launched because our
17045 IP address has changed. Spotted by Coverity Scan. Bugfix on
17046 0.1.1.4-alpha; fixes CID 484.
17048 o Minor bugfixes (log messages and documentation):
17049 - Remove a confusing dollar sign from the example fingerprint in the
17050 man page, and also make the example fingerprint a valid one. Fixes
17051 bug 4309; bugfix on 0.2.1.3-alpha.
17052 - The next version of Windows will be called Windows 8, and it has
17053 a major version of 6, minor version of 2. Correctly identify that
17054 version instead of calling it "Very recent version". Resolves
17055 ticket 4153; reported by funkstar.
17056 - Downgrade log messages about circuit timeout calibration from
17057 "notice" to "info": they don't require or suggest any human
17058 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
17059 bugfix on 0.2.2.14-alpha.
17062 - Turn on directory request statistics by default and include them in
17063 extra-info descriptors. Don't break if we have no GeoIP database.
17064 Backported from 0.2.3.1-alpha; implements ticket 3951.
17065 - Update to the October 4 2011 Maxmind GeoLite Country database.
17068 Changes in version 0.2.1.31 - 2011-10-26
17069 Tor 0.2.1.31 backports important security and privacy fixes for
17070 oldstable. This release is intended only for package maintainers and
17071 others who cannot use the 0.2.2 stable series. All others should be
17072 using Tor 0.2.2.x or newer.
17074 o Security fixes (also included in 0.2.2.x):
17075 - Replace all potentially sensitive memory comparison operations
17076 with versions whose runtime does not depend on the data being
17077 compared. This will help resist a class of attacks where an
17078 adversary can use variations in timing information to learn
17079 sensitive data. Fix for one case of bug 3122. (Safe memcmp
17080 implementation by Robert Ransom based partially on code by DJB.)
17081 - Fix an assert in parsing router descriptors containing IPv6
17082 addresses. This one took down the directory authorities when
17083 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
17085 o Privacy/anonymity fixes (also included in 0.2.2.x):
17086 - Clients and bridges no longer send TLS certificate chains on
17087 outgoing OR connections. Previously, each client or bridge would
17088 use the same cert chain for all outgoing OR connections until
17089 its IP address changes, which allowed any relay that the client
17090 or bridge contacted to determine which entry guards it is using.
17091 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
17092 - If a relay receives a CREATE_FAST cell on a TLS connection, it
17093 no longer considers that connection as suitable for satisfying a
17094 circuit EXTEND request. Now relays can protect clients from the
17095 CVE-2011-2768 issue even if the clients haven't upgraded yet.
17096 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
17097 that they initiated. Relays could distinguish incoming bridge
17098 connections from client connections, creating another avenue for
17099 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
17100 Found by "frosty_un".
17101 - When receiving a hidden service descriptor, check that it is for
17102 the hidden service we wanted. Previously, Tor would store any
17103 hidden service descriptors that a directory gave it, whether it
17104 wanted them or not. This wouldn't have let an attacker impersonate
17105 a hidden service, but it did let directories pre-seed a client
17106 with descriptors that it didn't want. Bugfix on 0.0.6.
17107 - Avoid linkability based on cached hidden service descriptors: forget
17108 all hidden service descriptors cached as a client when processing a
17109 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
17110 - Make the bridge directory authority refuse to answer directory
17111 requests for "all" descriptors. It used to include bridge
17112 descriptors in its answer, which was a major information leak.
17113 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
17114 - Don't attach new streams to old rendezvous circuits after SIGNAL
17115 NEWNYM. Previously, we would keep using an existing rendezvous
17116 circuit if it remained open (i.e. if it were kept open by a
17117 long-lived stream, or if a new stream were attached to it before
17118 Tor could notice that it was old and no longer in use). Bugfix on
17119 0.1.1.15-rc; fixes bug 3375.
17121 o Minor bugfixes (also included in 0.2.2.x):
17122 - When we restart our relay, we might get a successful connection
17123 from the outside before we've started our reachability tests,
17124 triggering a warning: "ORPort found reachable, but I have no
17125 routerinfo yet. Failing to inform controller of success." This
17126 bug was harmless unless Tor is running under a controller
17127 like Vidalia, in which case the controller would never get a
17128 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
17130 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
17131 enabled. Fixes bug 1526.
17132 - Remove undocumented option "-F" from tor-resolve: it hasn't done
17133 anything since 0.2.1.16-rc.
17134 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
17135 None of the cases where we did this before were wrong, but by making
17136 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
17137 - Fix a rare crash bug that could occur when a client was configured
17138 with a large number of bridges. Fixes bug 2629; bugfix on
17139 0.2.1.2-alpha. Bugfix by trac user "shitlei".
17140 - Correct the warning displayed when a rendezvous descriptor exceeds
17141 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
17143 - Fix an uncommon assertion failure when running with DNSPort under
17144 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
17145 - When warning about missing zlib development packages during compile,
17146 give the correct package names. Bugfix on 0.2.0.1-alpha.
17147 - Require that introduction point keys and onion keys have public
17148 exponent 65537. Bugfix on 0.2.0.10-alpha.
17149 - Do not crash when our configuration file becomes unreadable, for
17150 example due to a permissions change, between when we start up
17151 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
17153 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
17155 - Always NUL-terminate the sun_path field of a sockaddr_un before
17156 passing it to the kernel. (Not a security issue: kernels are
17157 smart enough to reject bad sockaddr_uns.) Found by Coverity;
17158 CID #428. Bugfix on Tor 0.2.0.3-alpha.
17159 - Don't stack-allocate the list of supplementary GIDs when we're
17160 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
17161 could take up to 256K, which is way too much stack. Found by
17162 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
17164 o Minor bugfixes (only in 0.2.1.x):
17165 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
17166 rely on them. Bugfix on 0.2.1.30.
17167 - Use git revisions instead of svn revisions when generating our
17168 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
17170 o Minor features (also included in 0.2.2.x):
17171 - Adjust the expiration time on our SSL session certificates to
17172 better match SSL certs seen in the wild. Resolves ticket 4014.
17173 - Allow nameservers with IPv6 address. Resolves bug 2574.
17174 - Update to the October 4 2011 Maxmind GeoLite Country database.
17177 Changes in version 0.2.3.5-alpha - 2011-09-28
17178 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
17179 bridge relays; fixes an assertion error that many users started hitting
17180 today; and adds the ability to refill token buckets more often than
17181 once per second, allowing significant performance improvements.
17184 - Bridge relays now do their directory fetches inside Tor TLS
17185 connections, like all the other clients do, rather than connecting
17186 directly to the DirPort like public relays do. Removes another
17187 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
17188 - Bridges relays now build circuits for themselves in a more similar
17189 way to how clients build them. Removes another avenue for
17190 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
17191 when bridges were introduced.
17194 - Fix an "Assertion md->held_by_node == 1 failed" error that could
17195 occur when the same microdescriptor was referenced by two node_t
17196 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
17198 o Major features (networking):
17199 - Add a new TokenBucketRefillInterval option to refill token buckets
17200 more frequently than once per second. This should improve network
17201 performance, alleviate queueing problems, and make traffic less
17202 bursty. Implements proposal 183; closes ticket 3630. Design by
17203 Florian Tschorsch and Björn Scheuermann; implementation by
17207 - Change an integer overflow check in the OpenBSD_Malloc code so
17208 that GCC is less likely to eliminate it as impossible. Patch
17209 from Mansour Moufid. Fixes bug 4059.
17211 o Minor bugfixes (usability):
17212 - Downgrade log messages about circuit timeout calibration from
17213 "notice" to "info": they don't require or suggest any human
17214 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
17215 bugfix on 0.2.2.14-alpha.
17217 o Minor features (diagnostics):
17218 - When the system call to create a listener socket fails, log the
17219 error message explaining why. This may help diagnose bug 4027.
17222 Changes in version 0.2.3.4-alpha - 2011-09-13
17223 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
17224 tweak to Tor's TLS handshake that makes relays and bridges that run
17225 this new version reachable from Iran again. It also fixes a few new
17226 bugs in 0.2.3.x, and teaches relays to recognize when they're not
17227 listed in the network consensus and republish.
17229 o Major bugfixes (also part of 0.2.2.33):
17230 - Avoid an assertion failure when reloading a configuration with
17231 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
17232 3923; bugfix on 0.2.2.25-alpha.
17234 o Minor features (security, also part of 0.2.2.33):
17235 - Check for replays of the public-key encrypted portion of an
17236 INTRODUCE1 cell, in addition to the current check for replays of
17237 the g^x value. This prevents a possible class of active attacks
17238 by an attacker who controls both an introduction point and a
17239 rendezvous point, and who uses the malleability of AES-CTR to
17240 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
17241 that these attacks are infeasible (requiring the attacker to send
17242 on the order of zettabytes of altered cells in a short interval),
17243 but we'd rather block them off in case there are any classes of
17244 this attack that we missed. Reported by Willem Pinckaers.
17246 o Minor features (also part of 0.2.2.33):
17247 - Adjust the expiration time on our SSL session certificates to
17248 better match SSL certs seen in the wild. Resolves ticket 4014.
17249 - Change the default required uptime for a relay to be accepted as
17250 a HSDir (hidden service directory) from 24 hours to 25 hours.
17251 Improves on 0.2.0.10-alpha; resolves ticket 2649.
17252 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
17253 authorities to abstain from voting on assignment of the HSDir
17254 consensus flag. Related to bug 2649.
17255 - Update to the September 6 2011 Maxmind GeoLite Country database.
17257 o Minor bugfixes (also part of 0.2.2.33):
17258 - Demote the 'replay detected' log message emitted when a hidden
17259 service receives the same Diffie-Hellman public key in two different
17260 INTRODUCE2 cells to info level. A normal Tor client can cause that
17261 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
17262 fixes part of bug 2442.
17263 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
17264 level. There is nothing that a hidden service's operator can do
17265 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
17267 - Clarify a log message specifying the characters permitted in
17268 HiddenServiceAuthorizeClient client names. Previously, the log
17269 message said that "[A-Za-z0-9+-_]" were permitted; that could have
17270 given the impression that every ASCII character between "+" and "_"
17271 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
17273 o Build fixes (also part of 0.2.2.33):
17274 - Clean up some code issues that prevented Tor from building on older
17275 BSDs. Fixes bug 3894; reported by "grarpamp".
17276 - Search for a platform-specific version of "ar" when cross-compiling.
17277 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
17280 - Fix a bug where the SocksPort option (for example) would get
17281 ignored and replaced by the default if a SocksListenAddress
17282 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
17286 - Relays now try regenerating and uploading their descriptor more
17287 frequently if they are not listed in the consensus, or if the
17288 version of their descriptor listed in the consensus is too
17289 old. This fix should prevent situations where a server declines
17290 to re-publish itself because it has done so too recently, even
17291 though the authorities decided not to list its recent-enough
17292 descriptor. Fix for bug 3327.
17295 - Relays now include a reason for regenerating their descriptors
17296 in an HTTP header when uploading to the authorities. This will
17297 make it easier to debug descriptor-upload issues in the future.
17298 - When starting as root and then changing our UID via the User
17299 control option, and we have a ControlSocket configured, make sure
17300 that the ControlSocket is owned by the same account that Tor will
17301 run under. Implements ticket 3421; fix by Jérémy Bobbio.
17304 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
17305 utility function used in the control-port code). This shouldn't
17306 ever happen unless Tor is completely out of memory, but if it did
17307 happen and Tor somehow recovered from it, Tor could have sent a log
17308 message to a control port in the middle of a reply to a controller
17309 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
17310 - Make 'FetchUselessDescriptors' cause all descriptor types and
17311 all consensus types (including microdescriptors) to get fetched.
17312 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
17314 o Code refactoring:
17315 - Make a new "entry connection" struct as an internal subtype of "edge
17316 connection", to simplify the code and make exit connections smaller.
17319 Changes in version 0.2.2.33 - 2011-09-13
17320 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
17321 TLS handshake that makes relays and bridges that run this new version
17322 reachable from Iran again.
17325 - Avoid an assertion failure when reloading a configuration with
17326 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
17327 3923; bugfix on 0.2.2.25-alpha.
17329 o Minor features (security):
17330 - Check for replays of the public-key encrypted portion of an
17331 INTRODUCE1 cell, in addition to the current check for replays of
17332 the g^x value. This prevents a possible class of active attacks
17333 by an attacker who controls both an introduction point and a
17334 rendezvous point, and who uses the malleability of AES-CTR to
17335 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
17336 that these attacks are infeasible (requiring the attacker to send
17337 on the order of zettabytes of altered cells in a short interval),
17338 but we'd rather block them off in case there are any classes of
17339 this attack that we missed. Reported by Willem Pinckaers.
17342 - Adjust the expiration time on our SSL session certificates to
17343 better match SSL certs seen in the wild. Resolves ticket 4014.
17344 - Change the default required uptime for a relay to be accepted as
17345 a HSDir (hidden service directory) from 24 hours to 25 hours.
17346 Improves on 0.2.0.10-alpha; resolves ticket 2649.
17347 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
17348 authorities to abstain from voting on assignment of the HSDir
17349 consensus flag. Related to bug 2649.
17350 - Update to the September 6 2011 Maxmind GeoLite Country database.
17352 o Minor bugfixes (documentation and log messages):
17353 - Correct the man page to explain that HashedControlPassword and
17354 CookieAuthentication can both be set, in which case either method
17355 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
17356 when we decided to allow these config options to both be set. Issue
17357 raised by bug 3898.
17358 - Demote the 'replay detected' log message emitted when a hidden
17359 service receives the same Diffie-Hellman public key in two different
17360 INTRODUCE2 cells to info level. A normal Tor client can cause that
17361 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
17362 fixes part of bug 2442.
17363 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
17364 level. There is nothing that a hidden service's operator can do
17365 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
17367 - Clarify a log message specifying the characters permitted in
17368 HiddenServiceAuthorizeClient client names. Previously, the log
17369 message said that "[A-Za-z0-9+-_]" were permitted; that could have
17370 given the impression that every ASCII character between "+" and "_"
17371 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
17374 - Provide a substitute implementation of lround() for MSVC, which
17375 apparently lacks it. Patch from Gisle Vanem.
17376 - Clean up some code issues that prevented Tor from building on older
17377 BSDs. Fixes bug 3894; reported by "grarpamp".
17378 - Search for a platform-specific version of "ar" when cross-compiling.
17379 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
17382 Changes in version 0.2.3.3-alpha - 2011-09-01
17383 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
17384 security, and provides client-side support for the microdescriptor
17385 and optimistic data features introduced earlier in the 0.2.3.x
17386 series. It also includes numerous critical bugfixes in the (optional)
17387 bufferevent-based networking backend.
17389 o Major features (stream isolation):
17390 - You can now configure Tor so that streams from different
17391 applications are isolated on different circuits, to prevent an
17392 attacker who sees your streams as they leave an exit node from
17393 linking your sessions to one another. To do this, choose some way
17394 to distinguish the applications: have them connect to different
17395 SocksPorts, or have one of them use SOCKS4 while the other uses
17396 SOCKS5, or have them pass different authentication strings to the
17397 SOCKS proxy. Then, use the new SocksPort syntax to configure the
17398 degree of isolation you need. This implements Proposal 171.
17399 - There's a new syntax for specifying multiple client ports (such as
17400 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
17401 multiple *Port entries with full addr:port syntax on each.
17402 The old *ListenAddress format is still supported, but you can't
17403 mix it with the new *Port syntax.
17405 o Major features (other):
17406 - Enable microdescriptor fetching by default for clients. This allows
17407 clients to download a much smaller amount of directory information.
17408 To disable it (and go back to the old-style consensus and
17409 descriptors), set "UseMicrodescriptors 0" in your torrc file.
17410 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
17411 "PortForwarding" config option), now supports Windows.
17412 - When using an exit relay running 0.2.3.x, clients can now
17413 "optimistically" send data before the exit relay reports that
17414 the stream has opened. This saves a round trip when starting
17415 connections where the client speaks first (such as web browsing).
17416 This behavior is controlled by a consensus parameter (currently
17417 disabled). To turn it on or off manually, use the "OptimisticData"
17418 torrc option. Implements proposal 181; code by Ian Goldberg.
17420 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
17421 - When using IOCP on Windows, we need to enable Libevent windows
17423 - The IOCP backend now works even when the user has not specified
17424 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
17425 Fixes part of bug 3752.
17426 - Correctly record the bytes we've read and written when using
17427 bufferevents, so that we can include them in our bandwidth history
17428 and advertised bandwidth. Fixes bug 3803.
17429 - Apply rate-limiting only at the bottom of a chain of filtering
17430 bufferevents. This prevents us from filling up internal read
17431 buffers and violating rate-limits when filtering bufferevents
17432 are enabled. Fixes part of bug 3804.
17433 - Add high-watermarks to the output buffers for filtered
17434 bufferevents. This prevents us from filling up internal write
17435 buffers and wasting CPU cycles when filtering bufferevents are
17436 enabled. Fixes part of bug 3804.
17437 - Correctly notice when data has been written from a bufferevent
17438 without flushing it completely. Fixes bug 3805.
17439 - Fix a bug where server-side tunneled bufferevent-based directory
17440 streams would get closed prematurely. Fixes bug 3814.
17441 - Fix a use-after-free error with per-connection rate-limiting
17442 buckets. Fixes bug 3888.
17444 o Major bugfixes (also part of 0.2.2.31-rc):
17445 - If we're configured to write our ControlPorts to disk, only write
17446 them after switching UID and creating the data directory. This way,
17447 we don't fail when starting up with a nonexistent DataDirectory
17448 and a ControlPortWriteToFile setting based on that directory. Fixes
17449 bug 3747; bugfix on Tor 0.2.2.26-beta.
17452 - Added a new CONF_CHANGED event so that controllers can be notified
17453 of any configuration changes made by other controllers, or by the
17454 user. Implements ticket 1692.
17455 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
17456 leak when using bufferevents, and lets Libevent worry about how to
17457 best copy data out of a buffer.
17458 - Replace files in stats/ rather than appending to them. Now that we
17459 include statistics in extra-info descriptors, it makes no sense to
17460 keep old statistics forever. Implements ticket 2930.
17462 o Minor features (build compatibility):
17463 - Limited, experimental support for building with nmake and MSVC.
17464 - Provide a substitute implementation of lround() for MSVC, which
17465 apparently lacks it. Patch from Gisle Vanem.
17467 o Minor features (also part of 0.2.2.31-rc):
17468 - Update to the August 2 2011 Maxmind GeoLite Country database.
17470 o Minor bugfixes (on 0.2.3.x-alpha):
17471 - Fix a spurious warning when parsing SOCKS requests with
17472 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
17473 - Get rid of a harmless warning that could happen on relays running
17474 with bufferevents. The warning was caused by someone doing an http
17475 request to a relay's orport. Also don't warn for a few related
17476 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
17478 o Minor bugfixes (on 2.2.x and earlier):
17479 - Correct the man page to explain that HashedControlPassword and
17480 CookieAuthentication can both be set, in which case either method
17481 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
17482 when we decided to allow these config options to both be set. Issue
17483 raised by bug 3898.
17484 - The "--quiet" and "--hush" options now apply not only to Tor's
17485 behavior before logs are configured, but also to Tor's behavior in
17486 the absence of configured logs. Fixes bug 3550; bugfix on
17489 o Minor bugfixes (also part of 0.2.2.31-rc):
17490 - Write several files in text mode, on OSes that distinguish text
17491 mode from binary mode (namely, Windows). These files are:
17492 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
17493 that collect those statistics; 'client_keys' and 'hostname' for
17494 hidden services that use authentication; and (in the tor-gencert
17495 utility) newly generated identity and signing keys. Previously,
17496 we wouldn't specify text mode or binary mode, leading to an
17497 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
17498 the DirRecordUsageByCountry option which would have triggered
17499 the assertion failure was added), although this assertion failure
17500 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
17501 - Selectively disable deprecation warnings on OS X because Lion
17502 started deprecating the shipped copy of openssl. Fixes bug 3643.
17503 - Remove an extra pair of quotation marks around the error
17504 message in control-port STATUS_GENERAL BUG events. Bugfix on
17505 0.1.2.6-alpha; fixes bug 3732.
17506 - When unable to format an address as a string, report its value
17507 as "???" rather than reusing the last formatted address. Bugfix
17510 o Code simplifications and refactoring:
17511 - Rewrite the listener-selection logic so that parsing which ports
17512 we want to listen on is now separate from binding to the ports
17516 - Building Tor with bufferevent support now requires Libevent
17517 2.0.13-stable or later. Previous versions of Libevent had bugs in
17518 SSL-related bufferevents and related issues that would make Tor
17519 work badly with bufferevents. Requiring 2.0.13-stable also allows
17520 Tor with bufferevents to take advantage of Libevent APIs
17521 introduced after 2.0.8-rc.
17524 Changes in version 0.2.2.32 - 2011-08-27
17525 The Tor 0.2.2 release series is dedicated to the memory of Andreas
17526 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
17527 a founder of the PETS community, a leader in our field, a mentor,
17528 and a friend. He left us with these words: "I had the possibility
17529 to contribute to this world that is not as it should be. I hope I
17530 could help in some areas to make the world a better place, and that
17531 I could also encourage other people to be engaged in improving the
17532 world. Please, stay engaged. This world needs you, your love, your
17533 initiative -- now I cannot be part of that anymore."
17535 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
17536 ready. More than two years in the making, this release features improved
17537 client performance and hidden service reliability, better compatibility
17538 for Android, correct behavior for bridges that listen on more than
17539 one address, more extensible and flexible directory object handling,
17540 better reporting of network statistics, improved code security, and
17541 many many other features and bugfixes.
17544 Changes in version 0.2.2.31-rc - 2011-08-17
17545 Tor 0.2.2.31-rc is the second and hopefully final release candidate
17546 for the Tor 0.2.2.x series.
17549 - Remove an extra pair of quotation marks around the error
17550 message in control-port STATUS_GENERAL BUG events. Bugfix on
17551 0.1.2.6-alpha; fixes bug 3732.
17552 - If we're configured to write our ControlPorts to disk, only write
17553 them after switching UID and creating the data directory. This way,
17554 we don't fail when starting up with a nonexistent DataDirectory
17555 and a ControlPortWriteToFile setting based on that directory. Fixes
17556 bug 3747; bugfix on Tor 0.2.2.26-beta.
17559 - Update to the August 2 2011 Maxmind GeoLite Country database.
17562 - Allow GETINFO fingerprint to return a fingerprint even when
17563 we have not yet built a router descriptor. Fixes bug 3577;
17564 bugfix on 0.2.0.1-alpha.
17565 - Write several files in text mode, on OSes that distinguish text
17566 mode from binary mode (namely, Windows). These files are:
17567 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
17568 that collect those statistics; 'client_keys' and 'hostname' for
17569 hidden services that use authentication; and (in the tor-gencert
17570 utility) newly generated identity and signing keys. Previously,
17571 we wouldn't specify text mode or binary mode, leading to an
17572 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
17573 the DirRecordUsageByCountry option which would have triggered
17574 the assertion failure was added), although this assertion failure
17575 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
17576 - Selectively disable deprecation warnings on OS X because Lion
17577 started deprecating the shipped copy of openssl. Fixes bug 3643.
17578 - When unable to format an address as a string, report its value
17579 as "???" rather than reusing the last formatted address. Bugfix
17583 Changes in version 0.2.3.2-alpha - 2011-07-18
17584 Tor 0.2.3.2-alpha introduces two new experimental features:
17585 microdescriptors and pluggable transports. It also continues cleaning
17586 up a variety of recently introduced features.
17589 - Clients can now use microdescriptors instead of regular descriptors
17590 to build circuits. Microdescriptors are authority-generated
17591 summaries of regular descriptors' contents, designed to change
17592 very rarely (see proposal 158 for details). This feature is
17593 designed to save bandwidth, especially for clients on slow internet
17594 connections. It's off by default for now, since nearly no caches
17595 support it, but it will be on-by-default for clients in a future
17596 version. You can use the UseMicrodescriptors option to turn it on.
17597 - Tor clients using bridges can now be configured to use a separate
17598 'transport' proxy for each bridge. This approach helps to resist
17599 censorship by allowing bridges to use protocol obfuscation
17600 plugins. It implements part of proposal 180. Implements ticket 2841.
17601 - While we're trying to bootstrap, record how many TLS connections
17602 fail in each state, and report which states saw the most failures
17603 in response to any bootstrap failures. This feature may speed up
17604 diagnosis of censorship events. Implements ticket 3116.
17606 o Major bugfixes (on 0.2.3.1-alpha):
17607 - When configuring a large set of nodes in EntryNodes (as with
17608 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
17609 random subset to be guards, and choose them in random
17610 order. Fixes bug 2798.
17611 - Tor could crash when remembering a consensus in a non-used consensus
17612 flavor without having a current consensus set. Fixes bug 3361.
17613 - Comparing an unknown address to a microdescriptor's shortened exit
17614 policy would always give a "rejected" result. Fixes bug 3599.
17615 - Using microdescriptors as a client no longer prevents Tor from
17616 uploading and downloading hidden service descriptors. Fixes
17620 - Allow nameservers with IPv6 address. Resolves bug 2574.
17621 - Accept attempts to include a password authenticator in the
17622 handshake, as supported by SOCKS5. This handles SOCKS clients that
17623 don't know how to omit a password when authenticating. Resolves
17625 - When configuring a large set of nodes in EntryNodes, and there are
17626 enough of them listed as Guard so that we don't need to consider
17627 the non-guard entries, prefer the ones listed with the Guard flag.
17628 - Check for and recover from inconsistency in the microdescriptor
17629 cache. This will make it harder for us to accidentally free a
17630 microdescriptor without removing it from the appropriate data
17631 structures. Fixes issue 3135; issue noted by "wanoskarnet".
17632 - Log SSL state transitions at log level DEBUG, log domain
17633 HANDSHAKE. This can be useful for debugging censorship events.
17634 Implements ticket 3264.
17635 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
17636 implements ticket 3439.
17638 o Minor bugfixes (on 0.2.3.1-alpha):
17639 - Do not free all general-purpose regular descriptors just
17640 because microdescriptor use is enabled. Fixes bug 3113.
17641 - Correctly link libevent_openssl when --enable-static-libevent
17642 is passed to configure. Fixes bug 3118.
17643 - Bridges should not complain during their heartbeat log messages that
17644 they are unlisted in the consensus: that's more or less the point
17645 of being a bridge. Fixes bug 3183.
17646 - Report a SIGNAL event to controllers when acting on a delayed
17647 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
17648 event to the controller if we acted on a SIGNAL NEWNYM command
17649 immediately, and otherwise not report a SIGNAL event for the
17650 command at all. Fixes bug 3349.
17651 - Fix a crash when handling the SIGNAL controller command or
17652 reporting ERR-level status events with bufferevents enabled. Found
17653 by Robert Ransom. Fixes bug 3367.
17654 - Always ship the tor-fw-helper manpage in our release tarballs.
17655 Fixes bug 3389. Reported by Stephen Walker.
17656 - Fix a class of double-mark-for-close bugs when bufferevents
17657 are enabled. Fixes bug 3403.
17658 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
17659 - Add SIGNAL to the list returned by the 'GETINFO events/names'
17660 control-port command. Fixes part of bug 3465.
17661 - Prevent using negative indices during unit test runs when read_all()
17662 fails. Spotted by coverity.
17663 - Fix a rare memory leak when checking the nodelist without it being
17664 present. Found by coverity.
17665 - Only try to download a microdescriptor-flavored consensus from
17666 a directory cache that provides them.
17668 o Minor bugfixes (on 0.2.2.x and earlier):
17669 - Assert that hidden-service-related operations are not performed
17670 using single-hop circuits. Previously, Tor would assert that
17671 client-side streams are not attached to single-hop circuits,
17672 but not that other sensitive operations on the client and service
17673 side are not performed using single-hop circuits. Fixes bug 3332;
17675 - Don't publish a new relay descriptor when we reload our onion key,
17676 unless the onion key has actually changed. Fixes bug 3263 and
17677 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
17678 - Allow GETINFO fingerprint to return a fingerprint even when
17679 we have not yet built a router descriptor. Fixes bug 3577;
17680 bugfix on 0.2.0.1-alpha.
17681 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
17682 on 0.2.2.4-alpha; fixes bug 3427.
17684 o Code simplification and refactoring:
17685 - Use tor_sscanf() in place of scanf() in more places through the
17686 code. This makes us a little more locale-independent, and
17687 should help shut up code-analysis tools that can't tell
17688 a safe sscanf string from a dangerous one.
17689 - Use tt_assert(), not tor_assert(), for checking for test failures.
17690 This makes the unit tests more able to go on in the event that
17692 - Split connection_about_to_close() into separate functions for each
17696 - On Windows, we now define the _WIN32_WINNT macros only if they
17697 are not already defined. This lets the person building Tor decide,
17698 if they want, to require a later version of Windows.
17701 Changes in version 0.2.2.30-rc - 2011-07-07
17702 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
17703 series. It fixes a few smaller bugs, but generally appears stable.
17704 Please test it and let us know whether it is!
17707 - Send a SUCCEEDED stream event to the controller when a reverse
17708 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
17709 discovered by katmagic.
17710 - Always NUL-terminate the sun_path field of a sockaddr_un before
17711 passing it to the kernel. (Not a security issue: kernels are
17712 smart enough to reject bad sockaddr_uns.) Found by Coverity;
17713 CID #428. Bugfix on Tor 0.2.0.3-alpha.
17714 - Don't stack-allocate the list of supplementary GIDs when we're
17715 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
17716 could take up to 256K, which is way too much stack. Found by
17717 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
17718 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
17719 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
17720 fixes part of bug 3465.
17721 - Fix a memory leak when receiving a descriptor for a hidden
17722 service we didn't ask for. Found by Coverity; CID #30. Bugfix
17726 - Update to the July 1 2011 Maxmind GeoLite Country database.
17729 Changes in version 0.2.2.29-beta - 2011-06-20
17730 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
17731 have bridge lines in their torrc but don't want to use them; gets
17732 us closer to having the control socket feature working on Debian;
17733 and fixes a variety of smaller bugs.
17736 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
17737 When we changed the default behavior to "use bridges if any
17738 are listed in the torrc", we surprised users who had bridges
17739 in their torrc files but who didn't actually want to use them.
17740 Partial resolution for bug 3354.
17743 - Don't attach new streams to old rendezvous circuits after SIGNAL
17744 NEWNYM. Previously, we would keep using an existing rendezvous
17745 circuit if it remained open (i.e. if it were kept open by a
17746 long-lived stream, or if a new stream were attached to it before
17747 Tor could notice that it was old and no longer in use). Bugfix on
17748 0.1.1.15-rc; fixes bug 3375.
17751 - Fix a bug when using ControlSocketsGroupWritable with User. The
17752 directory's group would be checked against the current group, not
17753 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
17754 bugfix on 0.2.2.26-beta.
17755 - Make connection_printf_to_buf()'s behavior sane. Its callers
17756 expect it to emit a CRLF iff the format string ends with CRLF;
17757 it actually emitted a CRLF iff (a) the format string ended with
17758 CRLF or (b) the resulting string was over 1023 characters long or
17759 (c) the format string did not end with CRLF *and* the resulting
17760 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
17761 fixes part of bug 3407.
17762 - Make send_control_event_impl()'s behavior sane. Its callers
17763 expect it to always emit a CRLF at the end of the string; it
17764 might have emitted extra control characters as well. Bugfix on
17765 0.1.1.9-alpha; fixes another part of bug 3407.
17766 - Make crypto_rand_int() check the value of its input correctly.
17767 Previously, it accepted values up to UINT_MAX, but could return a
17768 negative number if given a value above INT_MAX+1. Found by George
17769 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
17770 - Avoid a segfault when reading a malformed circuit build state
17771 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
17773 - When asked about a DNS record type we don't support via a
17774 client DNSPort, reply with NOTIMPL rather than an empty
17775 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
17776 - Fix a rare memory leak during stats writing. Found by coverity.
17779 - Update to the June 1 2011 Maxmind GeoLite Country database.
17781 o Code simplifications and refactoring:
17782 - Remove some dead code as indicated by coverity.
17783 - Remove a few dead assignments during router parsing. Found by
17785 - Add some forgotten return value checks during unit tests. Found
17787 - Don't use 1-bit wide signed bit fields. Found by coverity.
17790 Changes in version 0.2.2.28-beta - 2011-06-04
17791 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
17792 fixed a big bug in whether relays stay in the consensus consistently,
17793 we moved closer to handling bridges and hidden services correctly,
17794 and we started the process of better handling the dreaded "my Vidalia
17795 died, and now my Tor demands a password when I try to reconnect to it"
17799 - Don't decide to make a new descriptor when receiving a HUP signal.
17800 This bug has caused a lot of 0.2.2.x relays to disappear from the
17801 consensus periodically. Fixes the most common case of triggering
17802 bug 1810; bugfix on 0.2.2.7-alpha.
17803 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
17804 - Don't try to build descriptors if "ORPort auto" is set and we
17805 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
17807 - Resolve a crash that occurred when setting BridgeRelay to 1 with
17808 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
17809 - Apply circuit timeouts to opened hidden-service-related circuits
17810 based on the correct start time. Previously, we would apply the
17811 circuit build timeout based on time since the circuit's creation;
17812 it was supposed to be applied based on time since the circuit
17813 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
17814 - Use the same circuit timeout for client-side introduction
17815 circuits as for other four-hop circuits, rather than the timeout
17816 for single-hop directory-fetch circuits; the shorter timeout may
17817 have been appropriate with the static circuit build timeout in
17818 0.2.1.x and earlier, but caused many hidden service access attempts
17819 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
17820 on 0.2.2.2-alpha; fixes another part of bug 1297.
17821 - In ticket 2511 we fixed a case where you could use an unconfigured
17822 bridge if you had configured it as a bridge the last time you ran
17823 Tor. Now fix another edge case: if you had configured it as a bridge
17824 but then switched to a different bridge via the controller, you
17825 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
17829 - Add an __OwningControllerProcess configuration option and a
17830 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
17831 that when it exits, Tor will shut down. Implements feature 3049.
17832 - If "UseBridges 1" is set and no bridges are configured, Tor will
17833 now refuse to build any circuits until some bridges are set.
17834 If "UseBridges auto" is set, Tor will use bridges if they are
17835 configured and we are not running as a server, but otherwise will
17836 make circuits as usual. The new default is "auto". Patch by anonym,
17837 so the Tails LiveCD can stop automatically revealing you as a Tor
17841 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
17842 - Remove a trailing asterisk from "exit-policy/default" in the
17843 output of the control port command "GETINFO info/names". Bugfix
17845 - Use a wide type to hold sockets when built for 64-bit Windows builds.
17847 - Warn when the user configures two HiddenServiceDir lines that point
17848 to the same directory. Bugfix on 0.0.6 (the version introducing
17849 HiddenServiceDir); fixes bug 3289.
17850 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
17851 part of bug 2748; bugfix on 0.2.0.10-alpha.
17852 - Log malformed requests for rendezvous descriptors as protocol
17853 warnings, not warnings. Also, use a more informative log message
17854 in case someone sees it at log level warning without prior
17855 info-level messages. Fixes the other part of bug 2748; bugfix
17857 - Clear the table recording the time of the last request for each
17858 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
17859 Previously, we would clear our HS descriptor cache on SIGNAL
17860 NEWNYM, but if we had previously retrieved a descriptor (or tried
17861 to) from every directory responsible for it, we would refuse to
17862 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
17864 - Fix a log message that said "bits" while displaying a value in
17865 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
17867 - When checking for 1024-bit keys, check for 1024 bits, not 128
17868 bytes. This allows Tor to correctly discard keys of length 1017
17869 through 1023. Bugfix on 0.0.9pre5.
17872 - Relays now log the reason for publishing a new relay descriptor,
17873 so we have a better chance of hunting down instances of bug 1810.
17874 Resolves ticket 3252.
17875 - Revise most log messages that refer to nodes by nickname to
17876 instead use the "$key=nickname at address" format. This should be
17877 more useful, especially since nicknames are less and less likely
17878 to be unique. Resolves ticket 3045.
17879 - Log (at info level) when purging pieces of hidden-service-client
17880 state because of SIGNAL NEWNYM.
17883 - Remove undocumented option "-F" from tor-resolve: it hasn't done
17884 anything since 0.2.1.16-rc.
17887 Changes in version 0.2.2.27-beta - 2011-05-18
17888 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
17889 release, and also adds a few more general bugfixes.
17892 - Fix a crash bug when changing bridges in a running Tor process.
17893 Fixes bug 3213; bugfix on 0.2.2.26-beta.
17894 - When the controller configures a new bridge, don't wait 10 to 60
17895 seconds before trying to fetch its descriptor. Bugfix on
17896 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
17899 - Require that onion keys have exponent 65537 in microdescriptors too.
17900 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
17901 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
17902 Changed the limit to 512 characters by removing base64 newlines.
17903 Fixes bug 2752. Fix by Michael Yakubovich.
17904 - When a client starts or stops using bridges, never use a circuit
17905 that was built before the configuration change. This behavior could
17906 put at risk a user who uses bridges to ensure that her traffic
17907 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
17911 Changes in version 0.2.2.26-beta - 2011-05-17
17912 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
17913 also introduces a new "socksport auto" approach that should make it
17914 easier to run multiple Tors on the same system, and does a lot of
17915 cleanup to get us closer to a release candidate.
17917 o Security/privacy fixes:
17918 - Replace all potentially sensitive memory comparison operations
17919 with versions whose runtime does not depend on the data being
17920 compared. This will help resist a class of attacks where an
17921 adversary can use variations in timing information to learn
17922 sensitive data. Fix for one case of bug 3122. (Safe memcmp
17923 implementation by Robert Ransom based partially on code by DJB.)
17924 - When receiving a hidden service descriptor, check that it is for
17925 the hidden service we wanted. Previously, Tor would store any
17926 hidden service descriptors that a directory gave it, whether it
17927 wanted them or not. This wouldn't have let an attacker impersonate
17928 a hidden service, but it did let directories pre-seed a client
17929 with descriptors that it didn't want. Bugfix on 0.0.6.
17930 - On SIGHUP, do not clear out all TrackHostExits mappings, client
17931 DNS cache entries, and virtual address mappings: that's what
17932 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
17935 - The options SocksPort, ControlPort, and so on now all accept a
17936 value "auto" that opens a socket on an OS-selected port. A
17937 new ControlPortWriteToFile option tells Tor to write its
17938 actual control port or ports to a chosen file. If the option
17939 ControlPortFileGroupReadable is set, the file is created as
17940 group-readable. Now users can run two Tor clients on the same
17941 system without needing to manually mess with parameters. Resolves
17942 part of ticket 3076.
17943 - Set SO_REUSEADDR on all sockets, not just listeners. This should
17944 help busy exit nodes avoid running out of useable ports just
17945 because all the ports have been used in the near past. Resolves
17949 - New "GETINFO net/listeners/(type)" controller command to return
17950 a list of addresses and ports that are bound for listeners for a
17951 given connection type. This is useful when the user has configured
17952 "SocksPort auto" and the controller needs to know which port got
17953 chosen. Resolves another part of ticket 3076.
17954 - Add a new ControlSocketsGroupWritable configuration option: when
17955 it is turned on, ControlSockets are group-writeable by the default
17956 group of the current user. Patch by Jérémy Bobbio; implements
17958 - Tor now refuses to create a ControlSocket in a directory that is
17959 world-readable (or group-readable if ControlSocketsGroupWritable
17960 is 0). This is necessary because some operating systems do not
17961 enforce permissions on an AF_UNIX sockets. Permissions on the
17962 directory holding the socket, however, seems to work everywhere.
17963 - Rate-limit a warning about failures to download v2 networkstatus
17964 documents. Resolves part of bug 1352.
17965 - Backport code from 0.2.3.x that allows directory authorities to
17966 clean their microdescriptor caches. Needed to resolve bug 2230.
17967 - When an HTTPS proxy reports "403 Forbidden", we now explain
17968 what it means rather than calling it an unexpected status code.
17969 Closes bug 2503. Patch from Michael Yakubovich.
17970 - Update to the May 1 2011 Maxmind GeoLite Country database.
17973 - Authorities now clean their microdesc cache periodically and when
17974 reading from disk initially, not only when adding new descriptors.
17975 This prevents a bug where we could lose microdescriptors. Bugfix
17976 on 0.2.2.6-alpha. Fixes bug 2230.
17977 - Do not crash when our configuration file becomes unreadable, for
17978 example due to a permissions change, between when we start up
17979 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
17981 - Avoid a bug that would keep us from replacing a microdescriptor
17982 cache on Windows. (We would try to replace the file while still
17983 holding it open. That's fine on Unix, but Windows doesn't let us
17984 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
17985 - Add missing explanations for the authority-related torrc options
17986 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
17987 man page. Resolves issue 2379.
17988 - As an authority, do not upload our own vote or signature set to
17989 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
17990 it would get flagged as a duplicate. Resolves bug 3026.
17991 - Accept hidden service descriptors if we think we might be a hidden
17992 service directory, regardless of what our consensus says. This
17993 helps robustness, since clients and hidden services can sometimes
17994 have a more up-to-date view of the network consensus than we do,
17995 and if they think that the directory authorities list us a HSDir,
17996 we might actually be one. Related to bug 2732; bugfix on
17998 - When a controller changes TrackHostExits, remove mappings for
17999 hosts that should no longer have their exits tracked. Bugfix on
18001 - When a controller changes VirtualAddrNetwork, remove any mappings
18002 for hosts that were automapped to the old network. Bugfix on
18004 - When a controller changes one of the AutomapHosts* options, remove
18005 any mappings for hosts that should no longer be automapped. Bugfix
18007 - Do not reset the bridge descriptor download status every time we
18008 re-parse our configuration or get a configuration change. Fixes
18009 bug 3019; bugfix on 0.2.0.3-alpha.
18011 o Minor bugfixes (code cleanup):
18012 - When loading the microdesc journal, remember its current size.
18013 In 0.2.2, this helps prevent the microdesc journal from growing
18014 without limit on authorities (who are the only ones to use it in
18015 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
18016 Fix posted by "cypherpunks."
18017 - The microdesc journal is supposed to get rebuilt only if it is
18018 at least _half_ the length of the store, not _twice_ the length
18019 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
18020 - Fix a potential null-pointer dereference while computing a
18021 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
18023 - Avoid a possible null-pointer dereference when rebuilding the mdesc
18024 cache without actually having any descriptors to cache. Bugfix on
18025 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
18026 - If we fail to compute the identity digest of a v3 legacy keypair,
18027 warn, and don't use a buffer-full of junk instead. Bugfix on
18028 0.2.1.1-alpha; fixes bug 3106.
18029 - Resolve an untriggerable issue in smartlist_string_num_isin(),
18030 where if the function had ever in the future been used to check
18031 for the presence of a too-large number, it would have given an
18032 incorrect result. (Fortunately, we only used it for 16-bit
18033 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
18034 - Require that introduction point keys and onion handshake keys
18035 have a public exponent of 65537. Starts to fix bug 3207; bugfix
18038 o Removed features:
18039 - Caches no longer download and serve v2 networkstatus documents
18040 unless FetchV2Networkstatus flag is set: these documents haven't
18041 haven't been used by clients or relays since 0.2.0.x. Resolves
18045 Changes in version 0.2.3.1-alpha - 2011-05-05
18046 Tor 0.2.3.1-alpha adds some new experimental features, including support
18047 for an improved network IO backend, IOCP networking on Windows,
18048 microdescriptor caching, "fast-start" support for streams, and automatic
18049 home router configuration. There are also numerous internal improvements
18050 to try to make the code easier for developers to work with.
18052 This is the first alpha release in a new series, so expect there to be
18053 bugs. Users who would rather test out a more stable branch should
18054 stay with 0.2.2.x for now.
18057 - Tor can now optionally build with the "bufferevents" buffered IO
18058 backend provided by Libevent 2. To use this feature, make sure you
18059 have the latest possible version of Libevent, and pass the
18060 --enable-bufferevents flag to configure when building Tor from
18061 source. This feature will make our networking code more flexible,
18062 let us stack layers on each other, and let us use more efficient
18063 zero-copy transports where available.
18064 - As an experimental feature, Tor can use IOCP for networking on Windows.
18065 Once this code is tuned and optimized, it promises much better
18066 performance than the select-based backend we've used in the past. To
18067 try this feature, you must build Tor with Libevent 2, configure Tor
18068 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
18069 your torrc. There are known bugs here: only try this if you can help
18070 debug it as it breaks.
18071 - The EntryNodes option can now include country codes like {de} or IP
18072 addresses or network masks. Previously we had disallowed these options
18073 because we didn't have an efficient way to keep the list up to
18074 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
18075 - Exit nodes now accept and queue data on not-yet-connected streams.
18076 Previously, the client wasn't allowed to send data until the stream was
18077 connected, which slowed down all connections. This change will enable
18078 clients to perform a "fast-start" on streams and send data without
18079 having to wait for a confirmation that the stream has opened. (Patch
18080 from Ian Goldberg; implements the server side of Proposal 174.)
18081 - Tor now has initial support for automatic port mapping on the many
18082 home routers that support NAT-PMP or UPnP. (Not yet supported on
18083 Windows). To build the support code, you'll need to have libnatpnp
18084 library and/or the libminiupnpc library, and you'll need to enable the
18085 feature specifically by passing "--enable-upnp" and/or
18086 "--enable-natpnp" to configure. To turn it on, use the new
18087 PortForwarding option.
18088 - Caches now download, cache, and serve multiple "flavors" of the
18089 consensus, including a flavor that describes microdescriptors.
18090 - Caches now download, cache, and serve microdescriptors -- small
18091 summaries of router descriptors that are authenticated by all of the
18092 directory authorities. Once enough caches are running this code,
18093 clients will be able to save significant amounts of directory bandwidth
18094 by downloading microdescriptors instead of router descriptors.
18097 - Make logging resolution configurable with a new LogTimeGranularity
18098 option, and change the default from 1 millisecond to 1 second.
18099 Implements enhancement 1668.
18100 - We log which torrc file we're using on startup. Implements ticket
18102 - Ordinarily, Tor does not count traffic from private addresses (like
18103 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
18104 There is now a new option, CountPrivateBandwidth, to disable this
18105 behavior. Patch from Daniel Cagara.
18106 - New --enable-static-tor configure option for building Tor as
18107 statically as possible. Idea, general hackery and thoughts from
18108 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
18110 - If you set the NumCPUs option to 0, Tor will now try to detect how
18111 many CPUs you have. This is the new default behavior.
18112 - Turn on directory request statistics by default and include them in
18113 extra-info descriptors. Don't break if we have no GeoIP database.
18114 - Relays that set "ConnDirectionStatistics 1" write statistics on the
18115 bidirectional use of connections to disk every 24 hours.
18116 - Add a GeoIP file digest to the extra-info descriptor. Implements
18118 - The NodeFamily option -- which let you declare that you want to
18119 consider nodes to be part of a family whether they list themselves
18120 that way or not -- now allows IP address ranges and country codes.
18121 - Add a new 'Heartbeat' log message type to periodically log a message
18122 describing Tor's status at level Notice. This feature is meant for
18123 operators who log at notice, and want to make sure that their Tor
18124 server is still working. Implementation by George Kadianakis.
18126 o Minor bugfixes (on 0.2.2.25-alpha):
18127 - When loading the microdesc journal, remember its current size.
18128 In 0.2.2, this helps prevent the microdesc journal from growing
18129 without limit on authorities (who are the only ones to use it in
18130 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
18131 Fix posted by "cypherpunks."
18132 - The microdesc journal is supposed to get rebuilt only if it is
18133 at least _half_ the length of the store, not _twice_ the length
18134 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
18135 - If as an authority we fail to compute the identity digest of a v3
18136 legacy keypair, warn, and don't use a buffer-full of junk instead.
18137 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
18138 - Authorities now clean their microdesc cache periodically and when
18139 reading from disk initially, not only when adding new descriptors.
18140 This prevents a bug where we could lose microdescriptors. Bugfix
18143 o Minor features (controller):
18144 - Add a new SIGNAL event to the controller interface so that
18145 controllers can be notified when Tor handles a signal. Resolves
18146 issue 1955. Patch by John Brooks.
18147 - Add a new GETINFO option to get total bytes read and written. Patch
18148 from pipe, revised by atagar. Resolves ticket 2345.
18149 - Implement some GETINFO controller fields to provide information about
18150 the Tor process's pid, euid, username, and resource limits.
18153 - Our build system requires automake 1.6 or later to create the
18154 Makefile.in files. Previously, you could have used 1.4.
18155 This only affects developers and people building Tor from git;
18156 people who build Tor from the source distribution without changing
18157 the Makefile.am files should be fine.
18158 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
18159 so on. This is more robust against some of the failure modes
18160 associated with running the autotools pieces on their own.
18162 o Minor packaging issues:
18163 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
18164 already created. Patch from Andreas Stieger. Fixes bug 2573.
18166 o Code simplifications and refactoring:
18167 - A major revision to our internal node-selecting and listing logic.
18168 Tor already had at least two major ways to look at the question of
18169 "which Tor servers do we know about": a list of router descriptors,
18170 and a list of entries in the current consensus. With
18171 microdescriptors, we're adding a third. Having so many systems
18172 without an abstraction layer over them was hurting the codebase.
18173 Now, we have a new "node_t" abstraction that presents a consistent
18174 interface to a client's view of a Tor node, and holds (nearly) all
18175 of the mutable state formerly in routerinfo_t and routerstatus_t.
18176 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
18177 no longer link against Libevent: they never used it, but
18178 our library structure used to force them to link it.
18180 o Removed features:
18181 - Remove some old code to work around even older versions of Tor that
18182 used forked processes to handle DNS requests. Such versions of Tor
18183 are no longer in use as servers.
18185 o Documentation fixes:
18186 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
18187 - Add missing documentation for the authority-related torrc options
18188 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
18192 Changes in version 0.2.2.25-alpha - 2011-04-29
18193 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
18194 robust, routers no longer overreport their bandwidth, Win7 should crash
18195 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
18196 now prevents hidden service-related activity from being linkable. It
18197 provides more information to Vidalia so you can see if your bridge is
18198 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
18199 StrictNodes configuration options to make them more reliable, more
18200 understandable, and more regularly applied. If you use those options,
18201 please see the revised documentation for them in the manual page.
18204 - Relays were publishing grossly inflated bandwidth values because
18205 they were writing their state files wrong--now they write the
18206 correct value. Also, resume reading bandwidth history from the
18207 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
18208 - Improve hidden service robustness: When we find that we have
18209 extended a hidden service's introduction circuit to a relay not
18210 listed as an introduction point in the HS descriptor we currently
18211 have, retry with an introduction point from the current
18212 descriptor. Previously we would just give up. Fixes bugs 1024 and
18213 1930; bugfix on 0.2.0.10-alpha.
18214 - Clients now stop trying to use an exit node associated with a given
18215 destination by TrackHostExits if they fail to reach that exit node.
18216 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
18217 - Fix crash bug on platforms where gmtime and localtime can return
18218 NULL. Windows 7 users were running into this one. Fixes part of bug
18219 2077. Bugfix on all versions of Tor. Found by boboper.
18221 o Security and stability fixes:
18222 - Don't double-free a parsable, but invalid, microdescriptor, even if
18223 it is followed in the blob we're parsing by an unparsable
18224 microdescriptor. Fixes an issue reported in a comment on bug 2954.
18225 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
18226 - If the Nickname configuration option isn't given, Tor would pick a
18227 nickname based on the local hostname as the nickname for a relay.
18228 Because nicknames are not very important in today's Tor and the
18229 "Unnamed" nickname has been implemented, this is now problematic
18230 behavior: It leaks information about the hostname without being
18231 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
18232 introduced the Unnamed nickname. Reported by tagnaq.
18233 - Fix an uncommon assertion failure when running with DNSPort under
18234 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
18235 - Avoid linkability based on cached hidden service descriptors: forget
18236 all hidden service descriptors cached as a client when processing a
18237 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
18240 - Export GeoIP information on bridge usage to controllers even if we
18241 have not yet been running for 24 hours. Now Vidalia bridge operators
18242 can get more accurate and immediate feedback about their
18243 contributions to the network.
18245 o Major features and bugfixes (node selection):
18246 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
18247 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
18248 options. Previously, we had been ambiguous in describing what
18249 counted as an "exit" node, and what operations exactly "StrictNodes
18250 0" would permit. This created confusion when people saw nodes built
18251 through unexpected circuits, and made it hard to tell real bugs from
18252 surprises. Now the intended behavior is:
18253 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
18254 a node that delivers user traffic outside the Tor network.
18255 . "Entry", in the context of EntryNodes, means a node used as the
18256 first hop of a multihop circuit. It doesn't include direct
18257 connections to directory servers.
18258 . "ExcludeNodes" applies to all nodes.
18259 . "StrictNodes" changes the behavior of ExcludeNodes only. When
18260 StrictNodes is set, Tor should avoid all nodes listed in
18261 ExcludeNodes, even when it will make user requests fail. When
18262 StrictNodes is *not* set, then Tor should follow ExcludeNodes
18263 whenever it can, except when it must use an excluded node to
18264 perform self-tests, connect to a hidden service, provide a
18265 hidden service, fulfill a .exit request, upload directory
18266 information, or fetch directory information.
18267 Collectively, the changes to implement the behavior fix bug 1090.
18268 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
18269 a node is listed in both, it's treated as excluded.
18270 - ExcludeNodes now applies to directory nodes -- as a preference if
18271 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
18272 Don't exclude all the directory authorities and set StrictNodes to 1
18273 unless you really want your Tor to break.
18274 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
18275 - ExcludeExitNodes now overrides .exit requests.
18276 - We don't use bridges listed in ExcludeNodes.
18277 - When StrictNodes is 1:
18278 . We now apply ExcludeNodes to hidden service introduction points
18279 and to rendezvous points selected by hidden service users. This
18280 can make your hidden service less reliable: use it with caution!
18281 . If we have used ExcludeNodes on ourself, do not try relay
18282 reachability self-tests.
18283 . If we have excluded all the directory authorities, we will not
18284 even try to upload our descriptor if we're a relay.
18285 . Do not honor .exit requests to an excluded node.
18286 - Remove a misfeature that caused us to ignore the Fast/Stable flags
18287 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
18288 - When the set of permitted nodes changes, we now remove any mappings
18289 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
18291 - We never cannibalize a circuit that had excluded nodes on it, even
18292 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
18293 - Revert a change where we would be laxer about attaching streams to
18294 circuits than when building the circuits. This was meant to prevent
18295 a set of bugs where streams were never attachable, but our improved
18296 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
18297 - Keep track of how many times we launch a new circuit to handle a
18298 given stream. Too many launches could indicate an inconsistency
18299 between our "launch a circuit to handle this stream" logic and our
18300 "attach this stream to one of the available circuits" logic.
18301 - Improve log messages related to excluded nodes.
18304 - Fix a spurious warning when moving from a short month to a long
18305 month on relays with month-based BandwidthAccounting. Bugfix on
18306 0.2.2.17-alpha; fixes bug 3020.
18307 - When a client finds that an origin circuit has run out of 16-bit
18308 stream IDs, we now mark it as unusable for new streams. Previously,
18309 we would try to close the entire circuit. Bugfix on 0.0.6.
18310 - Add a forgotten cast that caused a compile warning on OS X 10.6.
18311 Bugfix on 0.2.2.24-alpha.
18312 - Be more careful about reporting the correct error from a failed
18313 connect() system call. Under some circumstances, it was possible to
18314 look at an incorrect value for errno when sending the end reason.
18315 Bugfix on 0.1.0.1-rc.
18316 - Correctly handle an "impossible" overflow cases in connection byte
18317 counting, where we write or read more than 4GB on an edge connection
18318 in a single second. Bugfix on 0.1.2.8-beta.
18319 - Correct the warning displayed when a rendezvous descriptor exceeds
18320 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
18322 - Clients and hidden services now use HSDir-flagged relays for hidden
18323 service descriptor downloads and uploads even if the relays have no
18324 DirPort set and the client has disabled TunnelDirConns. This will
18325 eventually allow us to give the HSDir flag to relays with no
18326 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
18327 - Downgrade "no current certificates known for authority" message from
18328 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
18329 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
18330 2917. Bugfix on 0.1.1.1-alpha.
18331 - Only limit the lengths of single HS descriptors, even when multiple
18332 HS descriptors are published to an HSDir relay in a single POST
18333 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
18334 - Write the current time into the LastWritten line in our state file,
18335 rather than the time from the previous write attempt. Also, stop
18336 trying to use a time of -1 in our log statements. Fixes bug 3039;
18337 bugfix on 0.2.2.14-alpha.
18338 - Be more consistent in our treatment of file system paths. "~" should
18339 get expanded to the user's home directory in the Log config option.
18340 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
18341 feature for the -f and --DataDirectory options.
18344 - Make sure every relay writes a state file at least every 12 hours.
18345 Previously, a relay could go for weeks without writing its state
18346 file, and on a crash could lose its bandwidth history, capacity
18347 estimates, client country statistics, and so on. Addresses bug 3012.
18348 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
18349 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
18350 clients are already deprecated because of security bugs.
18351 - Don't allow v0 hidden service authorities to act as clients.
18352 Required by fix for bug 3000.
18353 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
18354 by fix for bug 3000.
18355 - Ensure that no empty [dirreq-](read|write)-history lines are added
18356 to an extrainfo document. Implements ticket 2497.
18358 o Code simplification and refactoring:
18359 - Remove workaround code to handle directory responses from servers
18360 that had bug 539 (they would send HTTP status 503 responses _and_
18361 send a body too). Since only server versions before
18362 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
18363 keep the workaround in place.
18364 - Remove the old 'fuzzy time' logic. It was supposed to be used for
18365 handling calculations where we have a known amount of clock skew and
18366 an allowed amount of unknown skew. But we only used it in three
18367 places, and we never adjusted the known/unknown skew values. This is
18368 still something we might want to do someday, but if we do, we'll
18369 want to do it differently.
18370 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
18371 None of the cases where we did this before were wrong, but by making
18372 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
18373 - Use GetTempDir to find the proper temporary directory location on
18374 Windows when generating temporary files for the unit tests. Patch by
18378 Changes in version 0.2.2.24-alpha - 2011-04-08
18379 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
18380 prevented Tor clients from effectively using "multihomed" bridges,
18381 that is, bridges that listen on multiple ports or IP addresses so users
18382 can continue to use some of their addresses even if others get blocked.
18385 - Fix a bug where bridge users who configure the non-canonical
18386 address of a bridge automatically switch to its canonical
18387 address. If a bridge listens at more than one address, it should be
18388 able to advertise those addresses independently and any non-blocked
18389 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
18391 - If you configured Tor to use bridge A, and then quit and
18392 configured Tor to use bridge B instead, it would happily continue
18393 to use bridge A if it's still reachable. While this behavior is
18394 a feature if your goal is connectivity, in some scenarios it's a
18395 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
18396 - Directory authorities now use data collected from their own
18397 uptime observations when choosing whether to assign the HSDir flag
18398 to relays, instead of trusting the uptime value the relay reports in
18399 its descriptor. This change helps prevent an attack where a small
18400 set of nodes with frequently-changing identity keys can blackhole
18401 a hidden service. (Only authorities need upgrade; others will be
18402 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
18405 - When we restart our relay, we might get a successful connection
18406 from the outside before we've started our reachability tests,
18407 triggering a warning: "ORPort found reachable, but I have no
18408 routerinfo yet. Failing to inform controller of success." This
18409 bug was harmless unless Tor is running under a controller
18410 like Vidalia, in which case the controller would never get a
18411 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
18413 - Make directory authorities more accurate at recording when
18414 relays that have failed several reachability tests became
18415 unreachable, so we can provide more accuracy at assigning Stable,
18416 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
18417 - Fix an issue that prevented static linking of libevent on
18418 some platforms (notably Linux). Fixes bug 2698; bugfix on
18419 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
18420 the --with-static-libevent configure option).
18421 - We now ask the other side of a stream (the client or the exit)
18422 for more data on that stream when the amount of queued data on
18423 that stream dips low enough. Previously, we wouldn't ask the
18424 other side for more data until either it sent us more data (which
18425 it wasn't supposed to do if it had exhausted its window!) or we
18426 had completely flushed all our queued data. This flow control fix
18427 should improve throughput. Fixes bug 2756; bugfix on the earliest
18428 released versions of Tor (svn commit r152).
18429 - Avoid a double-mark-for-free warning when failing to attach a
18430 transparent proxy connection. (We thought we had fixed this in
18431 0.2.2.23-alpha, but it turns out our fix was checking the wrong
18432 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
18433 bug) and 0.2.2.23-alpha (the incorrect fix).
18434 - When warning about missing zlib development packages during compile,
18435 give the correct package names. Bugfix on 0.2.0.1-alpha.
18438 - Directory authorities now log the source of a rejected POSTed v3
18439 networkstatus vote.
18440 - Make compilation with clang possible when using
18441 --enable-gcc-warnings by removing two warning options that clang
18442 hasn't implemented yet and by fixing a few warnings. Implements
18444 - When expiring circuits, use microsecond timers rather than
18445 one-second timers. This can avoid an unpleasant situation where a
18446 circuit is launched near the end of one second and expired right
18447 near the beginning of the next, and prevent fluctuations in circuit
18449 - Use computed circuit-build timeouts to decide when to launch
18450 parallel introduction circuits for hidden services. (Previously,
18451 we would retry after 15 seconds.)
18452 - Update to the April 1 2011 Maxmind GeoLite Country database.
18455 - Create the /var/run/tor directory on startup on OpenSUSE if it is
18456 not already created. Patch from Andreas Stieger. Fixes bug 2573.
18458 o Documentation changes:
18459 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
18460 - Resolve all doxygen warnings except those for missing documentation.
18462 - Add doxygen documentation for more functions, fields, and types.
18465 Changes in version 0.2.2.23-alpha - 2011-03-08
18466 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
18467 they restart they don't lose their bandwidth capacity estimate. This
18468 release also fixes a diverse set of user-facing bugs, ranging from
18469 relays overrunning their rate limiting to clients falsely warning about
18470 clock skew to bridge descriptor leaks by our bridge directory authority.
18473 - Stop sending a CLOCK_SKEW controller status event whenever
18474 we fetch directory information from a relay that has a wrong clock.
18475 Instead, only inform the controller when it's a trusted authority
18476 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
18477 the rest of bug 1074.
18478 - Fix an assert in parsing router descriptors containing IPv6
18479 addresses. This one took down the directory authorities when
18480 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
18481 - Make the bridge directory authority refuse to answer directory
18482 requests for "all" descriptors. It used to include bridge
18483 descriptors in its answer, which was a major information leak.
18484 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
18485 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
18486 Tor would ignore their RelayBandwidthBurst setting,
18487 potentially using more bandwidth than expected. Bugfix on
18488 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
18489 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
18490 hidserv" in her torrc. The 'hidserv' argument never controlled
18491 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
18494 - Relays now save observed peak bandwidth throughput rates to their
18495 state file (along with total usage, which was already saved)
18496 so that they can determine their correct estimated bandwidth on
18497 restart. Resolves bug 1863, where Tor relays would reset their
18498 estimated bandwidth to 0 after restarting.
18499 - Directory authorities now take changes in router IP address and
18500 ORPort into account when determining router stability. Previously,
18501 if a router changed its IP or ORPort, the authorities would not
18502 treat it as having any downtime for the purposes of stability
18503 calculation, whereas clients would experience downtime since the
18504 change could take a while to propagate to them. Resolves issue 1035.
18505 - Enable Address Space Layout Randomization (ASLR) and Data Execution
18506 Prevention (DEP) by default on Windows to make it harder for
18507 attackers to exploit vulnerabilities. Patch from John Brooks.
18509 o Minor bugfixes (on 0.2.1.x and earlier):
18510 - Fix a rare crash bug that could occur when a client was configured
18511 with a large number of bridges. Fixes bug 2629; bugfix on
18512 0.2.1.2-alpha. Bugfix by trac user "shitlei".
18513 - Avoid a double mark-for-free warning when failing to attach a
18514 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
18516 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
18517 found by "cypherpunks". This bug was introduced before the first
18518 Tor release, in svn commit r110.
18519 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
18520 don't mention them in the manpage. Fixes bug 2450; issue
18521 spotted by keb and G-Lo.
18522 - Fix a bug in bandwidth history state parsing that could have been
18523 triggered if a future version of Tor ever changed the timing
18524 granularity at which bandwidth history is measured. Bugfix on
18525 Tor 0.1.1.11-alpha.
18526 - When a relay decides that its DNS is too broken for it to serve
18527 as an exit server, it advertised itself as a non-exit, but
18528 continued to act as an exit. This could create accidental
18529 partitioning opportunities for users. Instead, if a relay is
18530 going to advertise reject *:* as its exit policy, it should
18531 really act with exit policy "reject *:*". Fixes bug 2366.
18532 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
18533 - In the special case where you configure a public exit relay as your
18534 bridge, Tor would be willing to use that exit relay as the last
18535 hop in your circuit as well. Now we fail that circuit instead.
18536 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
18537 - Fix a bug with our locking implementation on Windows that couldn't
18538 correctly detect when a file was already locked. Fixes bug 2504,
18539 bugfix on 0.2.1.6-alpha.
18540 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
18541 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
18543 - Set target port in get_interface_address6() correctly. Bugfix
18544 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
18545 - Directory authorities are now more robust to hops back in time
18546 when calculating router stability. Previously, if a run of uptime
18547 or downtime appeared to be negative, the calculation could give
18548 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
18550 - Fix an assert that got triggered when using the TestingTorNetwork
18551 configuration option and then issuing a GETINFO config-text control
18552 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
18554 o Minor bugfixes (on 0.2.2.x):
18555 - Clients should not weight BadExit nodes as Exits in their node
18556 selection. Similarly, directory authorities should not count BadExit
18557 bandwidth as Exit bandwidth when computing bandwidth-weights.
18558 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
18559 - Correctly clear our dir_read/dir_write history when there is an
18560 error parsing any bw history value from the state file. Bugfix on
18561 Tor 0.2.2.15-alpha.
18562 - Resolve a bug in verifying signatures of directory objects
18563 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
18564 Fixes bug 2409. Found by "piebeer".
18565 - Bridge authorities no longer crash on SIGHUP when they try to
18566 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
18570 - Log less aggressively about circuit timeout changes, and improve
18571 some other circuit timeout messages. Resolves bug 2004.
18572 - Log a little more clearly about the times at which we're no longer
18573 accepting new connections. Resolves bug 2181.
18574 - Reject attempts at the client side to open connections to private
18575 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
18576 a randomly chosen exit node. Attempts to do so are always
18577 ill-defined, generally prevented by exit policies, and usually
18578 in error. This will also help to detect loops in transparent
18579 proxy configurations. You can disable this feature by setting
18580 "ClientRejectInternalAddresses 0" in your torrc.
18581 - Always treat failure to allocate an RSA key as an unrecoverable
18583 - Update to the March 1 2011 Maxmind GeoLite Country database.
18585 o Minor features (log subsystem):
18586 - Add documentation for configuring logging at different severities in
18587 different log domains. We've had this feature since 0.2.1.1-alpha,
18588 but for some reason it never made it into the manpage. Fixes
18590 - Make it simpler to specify "All log domains except for A and B".
18591 Previously you needed to say "[*,~A,~B]". Now you can just say
18593 - Add a "LogMessageDomains 1" option to include the domains of log
18594 messages along with the messages. Without this, there's no way
18595 to use log domains without reading the source or doing a lot
18598 o Packaging changes:
18599 - Stop shipping the Tor specs files and development proposal documents
18600 in the tarball. They are now in a separate git repository at
18601 git://git.torproject.org/torspec.git
18604 Changes in version 0.2.1.30 - 2011-02-23
18605 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
18606 change is a slight tweak to Tor's TLS handshake that makes relays
18607 and bridges that run this new version reachable from Iran again.
18608 We don't expect this tweak will win the arms race long-term, but it
18609 buys us time until we roll out a better solution.
18612 - Stop sending a CLOCK_SKEW controller status event whenever
18613 we fetch directory information from a relay that has a wrong clock.
18614 Instead, only inform the controller when it's a trusted authority
18615 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
18616 the rest of bug 1074.
18617 - Fix a bounds-checking error that could allow an attacker to
18618 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
18619 Found by "piebeer".
18620 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
18621 Tor would ignore their RelayBandwidthBurst setting,
18622 potentially using more bandwidth than expected. Bugfix on
18623 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
18624 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
18625 hidserv" in her torrc. The 'hidserv' argument never controlled
18626 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
18629 - Adjust our TLS Diffie-Hellman parameters to match those used by
18631 - Update to the February 1 2011 Maxmind GeoLite Country database.
18634 - Check for and reject overly long directory certificates and
18635 directory tokens before they have a chance to hit any assertions.
18636 Bugfix on 0.2.1.28. Found by "doorss".
18637 - Bring the logic that gathers routerinfos and assesses the
18638 acceptability of circuits into line. This prevents a Tor OP from
18639 getting locked in a cycle of choosing its local OR as an exit for a
18640 path (due to a .exit request) and then rejecting the circuit because
18641 its OR is not listed yet. It also prevents Tor clients from using an
18642 OR running in the same instance as an exit (due to a .exit request)
18643 if the OR does not meet the same requirements expected of an OR
18644 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
18646 o Packaging changes:
18647 - Stop shipping the Tor specs files and development proposal documents
18648 in the tarball. They are now in a separate git repository at
18649 git://git.torproject.org/torspec.git
18650 - Do not include Git version tags as though they are SVN tags when
18651 generating a tarball from inside a repository that has switched
18652 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
18655 Changes in version 0.2.2.22-alpha - 2011-01-25
18656 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
18657 main other change is a slight tweak to Tor's TLS handshake that makes
18658 relays and bridges that run this new version reachable from Iran again.
18659 We don't expect this tweak will win the arms race long-term, but it
18660 will buy us a bit more time until we roll out a better solution.
18663 - Fix a bounds-checking error that could allow an attacker to
18664 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
18665 Found by "piebeer".
18666 - Don't assert when changing from bridge to relay or vice versa
18667 via the controller. The assert happened because we didn't properly
18668 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
18669 bug 2433. Reported by bastik.
18672 - Adjust our TLS Diffie-Hellman parameters to match those used by
18674 - Provide a log message stating which geoip file we're parsing
18675 instead of just stating that we're parsing the geoip file.
18676 Implements ticket 2432.
18679 - Check for and reject overly long directory certificates and
18680 directory tokens before they have a chance to hit any assertions.
18681 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
18684 Changes in version 0.2.2.21-alpha - 2011-01-15
18685 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
18686 continues our recent code security audit work. The main fix resolves
18687 a remote heap overflow vulnerability that can allow remote code
18688 execution (CVE-2011-0427). Other fixes address a variety of assert
18689 and crash bugs, most of which we think are hard to exploit remotely.
18691 o Major bugfixes (security), also included in 0.2.1.29:
18692 - Fix a heap overflow bug where an adversary could cause heap
18693 corruption. This bug probably allows remote code execution
18694 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
18696 - Prevent a denial-of-service attack by disallowing any
18697 zlib-compressed data whose compression factor is implausibly
18698 high. Fixes part of bug 2324; reported by "doorss".
18699 - Zero out a few more keys in memory before freeing them. Fixes
18700 bug 2384 and part of bug 2385. These key instances found by
18701 "cypherpunks", based on Andrew Case's report about being able
18702 to find sensitive data in Tor's memory space if you have enough
18703 permissions. Bugfix on 0.0.2pre9.
18705 o Major bugfixes (crashes), also included in 0.2.1.29:
18706 - Prevent calls to Libevent from inside Libevent log handlers.
18707 This had potential to cause a nasty set of crashes, especially
18708 if running Libevent with debug logging enabled, and running
18709 Tor with a controller watching for low-severity log messages.
18710 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
18711 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
18712 underflow errors there too. Fixes the other part of bug 2324.
18713 - Fix a bug where we would assert if we ever had a
18714 cached-descriptors.new file (or another file read directly into
18715 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
18716 on 0.2.1.25. Found by doorss.
18717 - Fix some potential asserts and parsing issues with grossly
18718 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
18721 o Minor bugfixes (other), also included in 0.2.1.29:
18722 - Fix a bug with handling misformed replies to reverse DNS lookup
18723 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
18724 bug reported by doorss.
18725 - Fix compilation on mingw when a pthreads compatibility library
18726 has been installed. (We don't want to use it, so we shouldn't
18727 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
18728 - Fix a bug where we would declare that we had run out of virtual
18729 addresses when the address space was only half-exhausted. Bugfix
18731 - Correctly handle the case where AutomapHostsOnResolve is set but
18732 no virtual addresses are available. Fixes bug 2328; bugfix on
18733 0.1.2.1-alpha. Bug found by doorss.
18734 - Correctly handle wrapping around when we run out of virtual
18735 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
18737 o Minor features, also included in 0.2.1.29:
18738 - Update to the January 1 2011 Maxmind GeoLite Country database.
18739 - Introduce output size checks on all of our decryption functions.
18741 o Build changes, also included in 0.2.1.29:
18742 - Tor does not build packages correctly with Automake 1.6 and earlier;
18743 added a check to Makefile.am to make sure that we're building with
18744 Automake 1.7 or later.
18745 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
18746 because we built it with a too-old version of automake. Thus that
18747 release broke ./configure --enable-openbsd-malloc, which is popular
18748 among really fast exit relays on Linux.
18750 o Major bugfixes, new in 0.2.2.21-alpha:
18751 - Prevent crash/heap corruption when the cbtnummodes consensus
18752 parameter is set to 0 or large values. Fixes bug 2317; bugfix
18755 o Major features, new in 0.2.2.21-alpha:
18756 - Introduce minimum/maximum values that clients will believe
18757 from the consensus. Now we'll have a better chance to avoid crashes
18758 or worse when a consensus param has a weird value.
18760 o Minor features, new in 0.2.2.21-alpha:
18761 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
18762 used on bridges, and it makes bridge scanning somewhat easier.
18763 - If writing the state file to disk fails, wait up to an hour before
18764 retrying again, rather than trying again each second. Fixes bug
18765 2346; bugfix on Tor 0.1.1.3-alpha.
18766 - Make Libevent log messages get delivered to controllers later,
18767 and not from inside the Libevent log handler. This prevents unsafe
18768 reentrant Libevent calls while still letting the log messages
18770 - Detect platforms that brokenly use a signed size_t, and refuse to
18771 build there. Found and analyzed by doorss and rransom.
18772 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
18775 o Minor bugfixes, new in 0.2.2.21-alpha:
18776 - Handle SOCKS messages longer than 128 bytes long correctly, rather
18777 than waiting forever for them to finish. Fixes bug 2330; bugfix
18778 on 0.2.0.16-alpha. Found by doorss.
18779 - Add assertions to check for overflow in arguments to
18780 base32_encode() and base32_decode(); fix a signed-unsigned
18781 comparison there too. These bugs are not actually reachable in Tor,
18782 but it's good to prevent future errors too. Found by doorss.
18783 - Correctly detect failures to create DNS requests when using Libevent
18784 versions before v2. (Before Libevent 2, we used our own evdns
18785 implementation. Its return values for Libevent's evdns_resolve_*()
18786 functions are not consistent with those from Libevent.) Fixes bug
18787 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
18789 o Documentation, new in 0.2.2.21-alpha:
18790 - Document the default socks host and port (127.0.0.1:9050) for
18794 Changes in version 0.2.1.29 - 2011-01-15
18795 Tor 0.2.1.29 continues our recent code security audit work. The main
18796 fix resolves a remote heap overflow vulnerability that can allow remote
18797 code execution. Other fixes address a variety of assert and crash bugs,
18798 most of which we think are hard to exploit remotely.
18800 o Major bugfixes (security):
18801 - Fix a heap overflow bug where an adversary could cause heap
18802 corruption. This bug probably allows remote code execution
18803 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
18805 - Prevent a denial-of-service attack by disallowing any
18806 zlib-compressed data whose compression factor is implausibly
18807 high. Fixes part of bug 2324; reported by "doorss".
18808 - Zero out a few more keys in memory before freeing them. Fixes
18809 bug 2384 and part of bug 2385. These key instances found by
18810 "cypherpunks", based on Andrew Case's report about being able
18811 to find sensitive data in Tor's memory space if you have enough
18812 permissions. Bugfix on 0.0.2pre9.
18814 o Major bugfixes (crashes):
18815 - Prevent calls to Libevent from inside Libevent log handlers.
18816 This had potential to cause a nasty set of crashes, especially
18817 if running Libevent with debug logging enabled, and running
18818 Tor with a controller watching for low-severity log messages.
18819 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
18820 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
18821 underflow errors there too. Fixes the other part of bug 2324.
18822 - Fix a bug where we would assert if we ever had a
18823 cached-descriptors.new file (or another file read directly into
18824 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
18825 on 0.2.1.25. Found by doorss.
18826 - Fix some potential asserts and parsing issues with grossly
18827 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
18830 o Minor bugfixes (other):
18831 - Fix a bug with handling misformed replies to reverse DNS lookup
18832 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
18833 bug reported by doorss.
18834 - Fix compilation on mingw when a pthreads compatibility library
18835 has been installed. (We don't want to use it, so we shouldn't
18836 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
18837 - Fix a bug where we would declare that we had run out of virtual
18838 addresses when the address space was only half-exhausted. Bugfix
18840 - Correctly handle the case where AutomapHostsOnResolve is set but
18841 no virtual addresses are available. Fixes bug 2328; bugfix on
18842 0.1.2.1-alpha. Bug found by doorss.
18843 - Correctly handle wrapping around to when we run out of virtual
18844 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
18845 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
18846 because we built it with a too-old version of automake. Thus that
18847 release broke ./configure --enable-openbsd-malloc, which is popular
18848 among really fast exit relays on Linux.
18851 - Update to the January 1 2011 Maxmind GeoLite Country database.
18852 - Introduce output size checks on all of our decryption functions.
18855 - Tor does not build packages correctly with Automake 1.6 and earlier;
18856 added a check to Makefile.am to make sure that we're building with
18857 Automake 1.7 or later.
18860 Changes in version 0.2.2.20-alpha - 2010-12-17
18861 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
18862 exploitable bugs. We also fix a variety of other significant bugs,
18863 change the IP address for one of our directory authorities, and update
18864 the minimum version that Tor relays must run to join the network.
18867 - Fix a remotely exploitable bug that could be used to crash instances
18868 of Tor remotely by overflowing on the heap. Remote-code execution
18869 hasn't been confirmed, but can't be ruled out. Everyone should
18870 upgrade. Bugfix on the 0.1.1 series and later.
18871 - Fix a bug that could break accounting on 64-bit systems with large
18872 time_t values, making them hibernate for impossibly long intervals.
18873 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
18874 - Fix a logic error in directory_fetches_from_authorities() that
18875 would cause all _non_-exits refusing single-hop-like circuits
18876 to fetch from authorities, when we wanted to have _exits_ fetch
18877 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
18879 - Fix a stream fairness bug that would cause newer streams on a given
18880 circuit to get preference when reading bytes from the origin or
18881 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
18882 introduced before the first Tor release, in svn revision r152.
18884 o Directory authority changes:
18885 - Change IP address and ports for gabelmoo (v3 directory authority).
18888 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
18889 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
18890 - Fix an off-by-one error in calculating some controller command
18891 argument lengths. Fortunately, this mistake is harmless since
18892 the controller code does redundant NUL termination too. Found by
18893 boboper. Bugfix on 0.1.1.1-alpha.
18894 - Do not dereference NULL if a bridge fails to build its
18895 extra-info descriptor. Found by an anonymous commenter on
18896 Trac. Bugfix on 0.2.2.19-alpha.
18899 - Update to the December 1 2010 Maxmind GeoLite Country database.
18900 - Directory authorities now reject relays running any versions of
18901 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
18902 known bugs that keep RELAY_EARLY cells from working on rendezvous
18903 circuits. Followup to fix for bug 2081.
18904 - Directory authorities now reject relays running any version of Tor
18905 older than 0.2.0.26-rc. That version is the earliest that fetches
18906 current directory information correctly. Fixes bug 2156.
18907 - Report only the top 10 ports in exit-port stats in order not to
18908 exceed the maximum extra-info descriptor length of 50 KB. Implements
18912 Changes in version 0.2.1.28 - 2010-12-17
18913 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
18914 exploitable bugs. We also took this opportunity to change the IP address
18915 for one of our directory authorities, and to update the geoip database
18919 - Fix a remotely exploitable bug that could be used to crash instances
18920 of Tor remotely by overflowing on the heap. Remote-code execution
18921 hasn't been confirmed, but can't be ruled out. Everyone should
18922 upgrade. Bugfix on the 0.1.1 series and later.
18924 o Directory authority changes:
18925 - Change IP address and ports for gabelmoo (v3 directory authority).
18928 - Update to the December 1 2010 Maxmind GeoLite Country database.
18931 Changes in version 0.2.1.27 - 2010-11-23
18932 Yet another OpenSSL security patch broke its compatibility with Tor:
18933 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
18934 also took this opportunity to fix several crash bugs, integrate a new
18935 directory authority, and update the bundled GeoIP database.
18938 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
18939 No longer set the tlsext_host_name extension on server SSL objects;
18940 but continue to set it on client SSL objects. Our goal in setting
18941 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
18942 bugfix on 0.2.1.1-alpha.
18943 - Do not log messages to the controller while shrinking buffer
18944 freelists. Doing so would sometimes make the controller connection
18945 try to allocate a buffer chunk, which would mess up the internals
18946 of the freelist and cause an assertion failure. Fixes bug 1125;
18947 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
18948 - Learn our external IP address when we're a relay or bridge, even if
18949 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
18950 where we introduced bridge relays that don't need to publish to
18951 be useful. Fixes bug 2050.
18952 - Do even more to reject (and not just ignore) annotations on
18953 router descriptors received anywhere but from the cache. Previously
18954 we would ignore such annotations at first, but cache them to disk
18955 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
18956 - When you're using bridges and your network goes away and your
18957 bridges get marked as down, recover when you attempt a new socks
18958 connection (if the network is back), rather than waiting up to an
18959 hour to try fetching new descriptors for your bridges. Bugfix on
18960 0.2.0.3-alpha; fixes bug 1981.
18963 - Move to the November 2010 Maxmind GeoLite country db (rather
18964 than the June 2009 ip-to-country GeoIP db) for our statistics that
18965 count how many users relays are seeing from each country. Now we'll
18966 have more accurate data, especially for many African countries.
18968 o New directory authorities:
18969 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
18973 - Fix an assertion failure that could occur in directory caches or
18974 bridge users when using a very short voting interval on a testing
18975 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
18977 - Enforce multiplicity rules when parsing annotations. Bugfix on
18978 0.2.0.8-alpha. Found by piebeer.
18979 - Allow handshaking OR connections to take a full KeepalivePeriod
18980 seconds to handshake. Previously, we would close them after
18981 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
18982 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
18984 - When building with --enable-gcc-warnings on OpenBSD, disable
18985 warnings in system headers. This makes --enable-gcc-warnings
18986 pass on OpenBSD 4.8.
18989 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
18990 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
18991 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
18992 Servers can start sending this code when enough clients recognize
18993 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
18994 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
18995 Patch from mingw-san.
18998 - Remove the old debian/ directory from the main Tor distribution.
18999 The official Tor-for-debian git repository lives at the URL
19000 https://git.torproject.org/debian/tor.git
19001 - Stop shipping the old doc/website/ directory in the tarball. We
19002 changed the website format in late 2010, and what we shipped in
19003 0.2.1.26 really wasn't that useful anyway.
19006 Changes in version 0.2.2.19-alpha - 2010-11-22
19007 Yet another OpenSSL security patch broke its compatibility with Tor:
19008 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
19011 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
19012 No longer set the tlsext_host_name extension on server SSL objects;
19013 but continue to set it on client SSL objects. Our goal in setting
19014 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
19015 bugfix on 0.2.1.1-alpha.
19018 - Try harder not to exceed the maximum length of 50 KB when writing
19019 statistics to extra-info descriptors. This bug was triggered by very
19020 fast relays reporting exit-port, entry, and dirreq statistics.
19021 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
19022 - Publish a router descriptor even if generating an extra-info
19023 descriptor fails. Previously we would not publish a router
19024 descriptor without an extra-info descriptor; this can cause fast
19025 exit relays collecting exit-port statistics to drop from the
19026 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
19029 Changes in version 0.2.2.18-alpha - 2010-11-16
19030 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
19031 us lately, makes unpublished bridge relays able to detect their IP
19032 address, and fixes a wide variety of other bugs to get us much closer
19033 to a stable release.
19036 - Do even more to reject (and not just ignore) annotations on
19037 router descriptors received anywhere but from the cache. Previously
19038 we would ignore such annotations at first, but cache them to disk
19039 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
19040 - Do not log messages to the controller while shrinking buffer
19041 freelists. Doing so would sometimes make the controller connection
19042 try to allocate a buffer chunk, which would mess up the internals
19043 of the freelist and cause an assertion failure. Fixes bug 1125;
19044 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
19045 - Learn our external IP address when we're a relay or bridge, even if
19046 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
19047 where we introduced bridge relays that don't need to publish to
19048 be useful. Fixes bug 2050.
19049 - Maintain separate TLS contexts and certificates for incoming and
19050 outgoing connections in bridge relays. Previously we would use the
19051 same TLS contexts and certs for incoming and outgoing connections.
19052 Bugfix on 0.2.0.3-alpha; addresses bug 988.
19053 - Maintain separate identity keys for incoming and outgoing TLS
19054 contexts in bridge relays. Previously we would use the same
19055 identity keys for incoming and outgoing TLS contexts. Bugfix on
19056 0.2.0.3-alpha; addresses the other half of bug 988.
19057 - Avoid an assertion failure when we as an authority receive a
19058 duplicate upload of a router descriptor that we already have,
19059 but which we previously considered an obsolete descriptor.
19060 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
19061 - Avoid a crash bug triggered by looking at a dangling pointer while
19062 setting the network status consensus. Found by Robert Ransom.
19063 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
19064 - Fix a logic error where servers that _didn't_ act as exits would
19065 try to keep their server lists more aggressively up to date than
19066 exits, when it was supposed to be the other way around. Bugfix
19069 o Minor bugfixes (on Tor 0.2.1.x and earlier):
19070 - When we're trying to guess whether we know our IP address as
19071 a relay, we would log various ways that we failed to guess
19072 our address, but never log that we ended up guessing it
19073 successfully. Now add a log line to help confused and anxious
19074 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
19075 - Bring the logic that gathers routerinfos and assesses the
19076 acceptability of circuits into line. This prevents a Tor OP from
19077 getting locked in a cycle of choosing its local OR as an exit for a
19078 path (due to a .exit request) and then rejecting the circuit because
19079 its OR is not listed yet. It also prevents Tor clients from using an
19080 OR running in the same instance as an exit (due to a .exit request)
19081 if the OR does not meet the same requirements expected of an OR
19082 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
19083 - Correctly describe errors that occur when generating a TLS object.
19084 Previously we would attribute them to a failure while generating a
19085 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
19087 - Enforce multiplicity rules when parsing annotations. Bugfix on
19088 0.2.0.8-alpha. Found by piebeer.
19089 - Fix warnings that newer versions of autoconf produced during
19090 ./autogen.sh. These warnings appear to be harmless in our case,
19091 but they were extremely verbose. Fixes bug 2020.
19093 o Minor bugfixes (on Tor 0.2.2.x):
19094 - Enable protection of small arrays whenever we build with gcc
19095 hardening features, not only when also building with warnings
19096 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
19099 - Make hidden services work better in private Tor networks by not
19100 requiring any uptime to join the hidden service descriptor
19101 DHT. Implements ticket 2088.
19102 - Rate-limit the "your application is giving Tor only an IP address"
19103 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
19104 - When AllowSingleHopExits is set, print a warning to explain to the
19105 relay operator why most clients are avoiding her relay.
19106 - Update to the November 1 2010 Maxmind GeoLite Country database.
19108 o Code simplifications and refactoring:
19109 - When we fixed bug 1038 we had to put in a restriction not to send
19110 RELAY_EARLY cells on rend circuits. This was necessary as long
19111 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
19112 active. Now remove this obsolete check. Resolves bug 2081.
19113 - Some options used different conventions for uppercasing of acronyms
19114 when comparing manpage and source. Fix those in favor of the
19115 manpage, as it makes sense to capitalize acronyms.
19116 - Remove the torrc.complete file. It hasn't been kept up to date
19117 and users will have better luck checking out the manpage.
19118 - Remove the obsolete "NoPublish" option; it has been flagged
19119 as obsolete and has produced a warning since 0.1.1.18-rc.
19120 - Remove everything related to building the expert bundle for OS X.
19121 It has confused many users, doesn't work right on OS X 10.6,
19122 and is hard to get rid of once installed. Resolves bug 1274.
19125 Changes in version 0.2.2.17-alpha - 2010-09-30
19126 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
19127 to use one-hop circuits (which can put the exit relays at higher risk,
19128 plus unbalance the network); fixes a big bug in bandwidth accounting
19129 for relays that want to limit their monthly bandwidth use; fixes a
19130 big pile of bugs in how clients tolerate temporary network failure;
19131 and makes our adaptive circuit build timeout feature (which improves
19132 client performance if your network is fast while not breaking things
19133 if your network is slow) better handle bad networks.
19136 - Exit relays now try harder to block exit attempts from unknown
19137 relays, to make it harder for people to use them as one-hop proxies
19138 a la tortunnel. Controlled by the refuseunknownexits consensus
19139 parameter (currently enabled), or you can override it on your
19140 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
19142 o Major bugfixes (0.2.1.x and earlier):
19143 - Fix a bug in bandwidth accounting that could make us use twice
19144 the intended bandwidth when our interval start changes due to
19145 daylight saving time. Now we tolerate skew in stored vs computed
19146 interval starts: if the start of the period changes by no more than
19147 50% of the period's duration, we remember bytes that we transferred
19148 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
19149 - Always search the Windows system directory for system DLLs, and
19150 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
19151 - When you're using bridges and your network goes away and your
19152 bridges get marked as down, recover when you attempt a new socks
19153 connection (if the network is back), rather than waiting up to an
19154 hour to try fetching new descriptors for your bridges. Bugfix on
19155 0.2.0.3-alpha; fixes bug 1981.
19157 o Major bugfixes (on 0.2.2.x):
19158 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
19160 - Fix a segfault that could happen when operating a bridge relay with
19161 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
19162 - The consensus bandwidth-weights (used by clients to choose fast
19163 relays) entered an unexpected edge case in September where
19164 Exits were much scarcer than Guards, resulting in bad weight
19165 recommendations. Now we compute them using new constraints that
19166 should succeed in all cases. Also alter directory authorities to
19167 not include the bandwidth-weights line if they fail to produce
19168 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
19169 - When weighting bridges during path selection, we used to trust
19170 the bandwidths they provided in their descriptor, only capping them
19171 at 10MB/s. This turned out to be problematic for two reasons:
19172 Bridges could claim to handle a lot more traffic then they
19173 actually would, thus making more clients pick them and have a
19174 pretty effective DoS attack. The other issue is that new bridges
19175 that might not have a good estimate for their bw capacity yet
19176 would not get used at all unless no other bridges are available
19177 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
19179 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
19180 - Ignore cannibalized circuits when recording circuit build times.
19181 This should provide for a minor performance improvement for hidden
19182 service users using 0.2.2.14-alpha, and should remove two spurious
19183 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
19184 - Simplify the logic that causes us to decide if the network is
19185 unavailable for purposes of recording circuit build times. If we
19186 receive no cells whatsoever for the entire duration of a circuit's
19187 full measured lifetime, the network is probably down. Also ignore
19188 one-hop directory fetching circuit timeouts when calculating our
19189 circuit build times. These changes should hopefully reduce the
19190 cases where we see ridiculous circuit build timeouts for people
19191 with spotty wireless connections. Fixes part of bug 1772; bugfix
19193 - Prevent the circuit build timeout from becoming larger than
19194 the maximum build time we have ever seen. Also, prevent the time
19195 period for measurement circuits from becoming larger than twice that
19196 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
19199 - When we run out of directory information such that we can't build
19200 circuits, but then get enough that we can build circuits, log when
19201 we actually construct a circuit, so the user has a better chance of
19202 knowing what's going on. Fixes bug 1362.
19203 - Be more generous with how much bandwidth we'd use up (with
19204 accounting enabled) before entering "soft hibernation". Previously,
19205 we'd refuse new connections and circuits once we'd used up 95% of
19206 our allotment. Now, we use up 95% of our allotment, AND make sure
19207 that we have no more than 500MB (or 3 hours of expected traffic,
19208 whichever is lower) remaining before we enter soft hibernation.
19209 - If we've configured EntryNodes and our network goes away and/or all
19210 our entrynodes get marked down, optimistically retry them all when
19211 a new socks application request appears. Fixes bug 1882.
19212 - Add some more defensive programming for architectures that can't
19213 handle unaligned integer accesses. We don't know of any actual bugs
19214 right now, but that's the best time to fix them. Fixes bug 1943.
19215 - Support line continuations in the torrc config file. If a line
19216 ends with a single backslash character, the newline is ignored, and
19217 the configuration value is treated as continuing on the next line.
19220 o Minor bugfixes (on 0.2.1.x and earlier):
19221 - For bandwidth accounting, calculate our expected bandwidth rate
19222 based on the time during which we were active and not in
19223 soft-hibernation during the last interval. Previously, we were
19224 also considering the time spent in soft-hibernation. If this
19225 was a long time, we would wind up underestimating our bandwidth
19226 by a lot, and skewing our wakeup time towards the start of the
19227 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
19229 o Minor bugfixes (on 0.2.2.x):
19230 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
19231 which were disabled by the circuit build timeout changes in
19232 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
19233 - Make sure we don't warn about missing bandwidth weights when
19234 choosing bridges or other relays not in the consensus. Bugfix on
19235 0.2.2.10-alpha; fixes bug 1805.
19236 - In our logs, do not double-report signatures from unrecognized
19237 authorities both as "from unknown authority" and "not
19238 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
19241 Changes in version 0.2.2.16-alpha - 2010-09-17
19242 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
19243 evident at exit relays), and also continues to resolve all the little
19244 bugs that have been filling up trac lately.
19246 o Major bugfixes (stream-level fairness):
19247 - When receiving a circuit-level SENDME for a blocked circuit, try
19248 to package cells fairly from all the streams that had previously
19249 been blocked on that circuit. Previously, we had started with the
19250 oldest stream, and allowed each stream to potentially exhaust
19251 the circuit's package window. This gave older streams on any
19252 given circuit priority over newer ones. Fixes bug 1937. Detected
19253 originally by Camilo Viecco. This bug was introduced before the
19254 first Tor release, in svn commit r152: it is the new winner of
19255 the longest-lived bug prize.
19256 - When the exit relay got a circuit-level sendme cell, it started
19257 reading on the exit streams, even if had 500 cells queued in the
19258 circuit queue already, so the circuit queue just grew and grew in
19259 some cases. We fix this by not re-enabling reading on receipt of a
19260 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
19261 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
19263 - Newly created streams were allowed to read cells onto circuits,
19264 even if the circuit's cell queue was blocked and waiting to drain.
19265 This created potential unfairness, as older streams would be
19266 blocked, but newer streams would gladly fill the queue completely.
19267 We add code to detect this situation and prevent any stream from
19268 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
19272 - Update to the September 1 2010 Maxmind GeoLite Country database.
19273 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
19274 not. This would lead to a cookie that is still not group readable.
19275 Closes bug 1843. Suggested by katmagic.
19276 - When logging a rate-limited warning, we now mention how many messages
19277 got suppressed since the last warning.
19278 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
19279 do individual connection-level rate limiting of clients. The torrc
19280 config options with the same names trump the consensus params, if
19281 both are present. Replaces the old "bwconnrate" and "bwconnburst"
19282 consensus params which were broken from 0.2.2.7-alpha through
19283 0.2.2.14-alpha. Closes bug 1947.
19284 - When a router changes IP address or port, authorities now launch
19285 a new reachability test for it. Implements ticket 1899.
19286 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
19287 2 no signature, 4 required" messages about consensus signatures
19288 easier to read, and make sure they get logged at the same severity
19289 as the messages explaining which keys are which. Fixes bug 1290.
19290 - Don't warn when we have a consensus that we can't verify because
19291 of missing certificates, unless those certificates are ones
19292 that we have been trying and failing to download. Fixes bug 1145.
19293 - If you configure your bridge with a known identity fingerprint,
19294 and the bridge authority is unreachable (as it is in at least
19295 one country now), fall back to directly requesting the descriptor
19296 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
19298 - When building with --enable-gcc-warnings on OpenBSD, disable
19299 warnings in system headers. This makes --enable-gcc-warnings
19300 pass on OpenBSD 4.8.
19302 o Minor bugfixes (on 0.2.1.x and earlier):
19303 - Authorities will now attempt to download consensuses if their
19304 own efforts to make a live consensus have failed. This change
19305 means authorities that restart will fetch a valid consensus, and
19306 it means authorities that didn't agree with the current consensus
19307 will still fetch and serve it if it has enough signatures. Bugfix
19308 on 0.2.0.9-alpha; fixes bug 1300.
19309 - Ensure DNS requests launched by "RESOLVE" commands from the
19310 controller respect the __LeaveStreamsUnattached setconf options. The
19311 same goes for requests launched via DNSPort or transparent
19312 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
19313 - Allow handshaking OR connections to take a full KeepalivePeriod
19314 seconds to handshake. Previously, we would close them after
19315 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
19316 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
19318 - Rate-limit "Failed to hand off onionskin" warnings.
19319 - Never relay a cell for a circuit we have already destroyed.
19320 Between marking a circuit as closeable and finally closing it,
19321 it may have been possible for a few queued cells to get relayed,
19322 even though they would have been immediately dropped by the next
19323 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
19324 - Never queue a cell for a circuit that's already been marked
19326 - Never vote for a server as "Running" if we have a descriptor for
19327 it claiming to be hibernating, and that descriptor was published
19328 more recently than our last contact with the server. Bugfix on
19329 0.2.0.3-alpha; fixes bug 911.
19330 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
19333 o Minor bugfixes (on 0.2.2.x):
19334 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
19335 down if a directory fetch fails and you've configured either
19336 bridges or EntryNodes. The intent was to mark the relay as down
19337 _unless_ you're using bridges or EntryNodes, since if you are
19338 then you could quickly run out of entry points.
19339 - Fix the Windows directory-listing code. A bug introduced in
19340 0.2.2.14-alpha could make Windows directory servers forget to load
19341 some of their cached v2 networkstatus files.
19342 - Really allow clients to use relays as bridges. Fixes bug 1776;
19343 bugfix on 0.2.2.15-alpha.
19344 - Demote a warn to info that happens when the CellStatistics option
19345 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
19346 Reported by Moritz Bartl.
19347 - On Windows, build correctly either with or without Unicode support.
19348 This is necessary so that Tor can support fringe platforms like
19349 Windows 98 (which has no Unicode), or Windows CE (which has no
19350 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
19353 - Add a unit test for cross-platform directory-listing code.
19356 Changes in version 0.2.2.15-alpha - 2010-08-18
19357 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
19358 fixes a variety of other bugs that were preventing performance
19359 experiments from moving forward, fixes several bothersome memory leaks,
19360 and generally closes a lot of smaller bugs that have been filling up
19364 - Stop assigning the HSDir flag to relays that disable their
19365 DirPort (and thus will refuse to answer directory requests). This
19366 fix should dramatically improve the reachability of hidden services:
19367 hidden services and hidden service clients pick six HSDir relays
19368 to store and retrieve the hidden service descriptor, and currently
19369 about half of the HSDir relays will refuse to work. Bugfix on
19370 0.2.0.10-alpha; fixes part of bug 1693.
19371 - The PerConnBWRate and Burst config options, along with the
19372 bwconnrate and bwconnburst consensus params, initialized each conn's
19373 token bucket values only when the connection is established. Now we
19374 update them if the config options change, and update them every time
19375 we get a new consensus. Otherwise we can encounter an ugly edge
19376 case where we initialize an OR conn to client-level bandwidth,
19377 but then later the relay joins the consensus and we leave it
19378 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
19379 - Fix a regression that caused Tor to rebind its ports if it receives
19380 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
19383 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
19384 should give us approximately 40-50% more Guard-flagged nodes,
19385 improving the anonymity the Tor network can provide and also
19386 decreasing the dropoff in throughput that relays experience when
19387 they first get the Guard flag.
19388 - Allow enabling or disabling the *Statistics config options while
19392 - Update to the August 1 2010 Maxmind GeoLite Country database.
19393 - Have the controller interface give a more useful message than
19394 "Internal Error" in response to failed GETINFO requests.
19395 - Warn when the same option is provided more than once in a torrc
19396 file, on the command line, or in a single SETCONF statement, and
19397 the option is one that only accepts a single line. Closes bug 1384.
19398 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
19399 Patch from mingw-san.
19400 - Add support for the country code "{??}" in torrc options like
19401 ExcludeNodes, to indicate all routers of unknown country. Closes
19403 - Relays report the number of bytes spent on answering directory
19404 requests in extra-info descriptors similar to {read,write}-history.
19405 Implements enhancement 1790.
19407 o Minor bugfixes (on 0.2.1.x and earlier):
19408 - Complain if PublishServerDescriptor is given multiple arguments that
19409 include 0 or 1. This configuration will be rejected in the future.
19410 Bugfix on 0.2.0.1-alpha; closes bug 1107.
19411 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
19412 Bugfix on 0.2.0.13-alpha; closes bug 928.
19413 - Change "Application request when we're believed to be offline."
19414 notice to "Application request when we haven't used client
19415 functionality lately.", to clarify that it's not an error. Bugfix
19416 on 0.0.9.3; fixes bug 1222.
19417 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
19418 would return "551 Internal error" rather than "552 Unrecognized key
19419 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
19420 - Users can't configure a regular relay to be their bridge. It didn't
19421 work because when Tor fetched the bridge descriptor, it found
19422 that it already had it, and didn't realize that the purpose of the
19423 descriptor had changed. Now we replace routers with a purpose other
19424 than bridge with bridge descriptors when fetching them. Bugfix on
19425 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
19426 refetch the descriptor with router purpose 'general', disabling
19428 - Fix a rare bug in rend_fn unit tests: we would fail a test when
19429 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
19430 on 0.2.0.10-alpha; fixes bug 1808.
19431 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
19432 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
19433 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
19434 Servers can start sending this code when enough clients recognize
19435 it. Also update the spec to reflect this new reason. Bugfix on
19436 0.1.0.1-rc; fixes part of bug 1793.
19437 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
19438 when we switch from being a public relay to a bridge. Otherwise
19439 there will still be clients that see the relay in their consensus,
19440 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
19442 - Instead of giving an assertion failure on an internal mismatch
19443 on estimated freelist size, just log a BUG warning and try later.
19444 Mitigates but does not fix bug 1125.
19445 - Fix an assertion failure that could occur in caches or bridge users
19446 when using a very short voting interval on a testing network.
19447 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
19449 o Minor bugfixes (on 0.2.2.x):
19450 - Alter directory authorities to always consider Exit-flagged nodes
19451 as potential Guard nodes in their votes. The actual decision to
19452 use Exits as Guards is done in the consensus bandwidth weights.
19453 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
19454 - When the controller is reporting the purpose of circuits that
19455 didn't finish building before the circuit build timeout, it was
19456 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
19457 - Our libevent version parsing code couldn't handle versions like
19458 1.4.14b-stable and incorrectly warned the user about using an
19459 old and broken version of libevent. Treat 1.4.14b-stable like
19460 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
19462 - Don't use substitution references like $(VAR:MOD) when
19463 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
19464 '$(:x)' to 'x' rather than the empty string. This bites us in
19465 doc/ when configured with --disable-asciidoc. Bugfix on
19466 0.2.2.9-alpha; fixes bug 1773.
19467 - Remove a spurious hidden service server-side log notice about
19468 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
19470 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
19472 - Correctly report written bytes on linked connections. Found while
19473 implementing 1790. Bugfix on 0.2.2.4-alpha.
19474 - Fix three memory leaks: one in circuit_build_times_parse_state(),
19475 one in dirvote_add_signatures_to_pending_consensus(), and one every
19476 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
19477 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
19479 o Code simplifications and refactoring:
19480 - Take a first step towards making or.h smaller by splitting out
19481 function definitions for all source files in src/or/. Leave
19482 structures and defines in or.h for now.
19483 - Remove a bunch of unused function declarations as well as a block of
19484 #if 0'd code from the unit tests. Closes bug 1824.
19485 - New unit tests for exit-port history statistics; refactored exit
19486 statistics code to be more easily tested.
19487 - Remove the old debian/ directory from the main Tor distribution.
19488 The official Tor-for-debian git repository lives at the URL
19489 https://git.torproject.org/debian/tor.git
19492 Changes in version 0.2.2.14-alpha - 2010-07-12
19493 Tor 0.2.2.14-alpha greatly improves client-side handling of
19494 circuit build timeouts, which are used to estimate speed and improve
19495 performance. We also move to a much better GeoIP database, port Tor to
19496 Windows CE, introduce new compile flags that improve code security,
19497 add an eighth v3 directory authority, and address a lot of more
19501 - Tor directory authorities no longer crash when started with a
19502 cached-microdesc-consensus file in their data directory. Bugfix
19503 on 0.2.2.6-alpha; fixes bug 1532.
19504 - Treat an unset $HOME like an empty $HOME rather than triggering an
19505 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
19506 - Ignore negative and large circuit build timeout values that can
19507 happen during a suspend or hibernate. These values caused various
19508 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
19509 - Alter calculation of Pareto distribution parameter 'Xm' for
19510 Circuit Build Timeout learning to use the weighted average of the
19511 top N=3 modes (because we have three entry guards). Considering
19512 multiple modes should improve the timeout calculation in some cases,
19513 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
19515 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
19516 right censored distribution model. This approach improves over the
19517 synthetic timeout generation approach that was producing insanely
19518 high timeout values. Now we calculate build timeouts using truncated
19519 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
19520 - Do not close circuits that are under construction when they reach
19521 the circuit build timeout. Instead, leave them building (but do not
19522 use them) for up until the time corresponding to the 95th percentile
19523 on the Pareto CDF or 60 seconds, whichever is greater. This is done
19524 to provide better data for the new Pareto model. This percentile
19525 can be controlled by the consensus.
19528 - Move to the June 2010 Maxmind GeoLite country db (rather than the
19529 June 2009 ip-to-country GeoIP db) for our statistics that count
19530 how many users relays are seeing from each country. Now we have
19531 more accurate data for many African countries.
19532 - Port Tor to build and run correctly on Windows CE systems, using
19533 the wcecompat library. Contributed by Valerio Lupi.
19534 - New "--enable-gcc-hardening" ./configure flag (off by default)
19535 to turn on gcc compile time hardening options. It ensures
19536 that signed ints have defined behavior (-fwrapv), enables
19537 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
19538 with canaries (-fstack-protector-all), turns on ASLR protection if
19539 supported by the kernel (-fPIE, -pie), and adds additional security
19540 related warnings. Verified to work on Mac OS X and Debian Lenny.
19541 - New "--enable-linker-hardening" ./configure flag (off by default)
19542 to turn on ELF specific hardening features (relro, now). This does
19543 not work with Mac OS X or any other non-ELF binary format.
19545 o New directory authorities:
19546 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
19550 - New config option "WarnUnsafeSocks 0" disables the warning that
19551 occurs whenever Tor receives a socks handshake using a version of
19552 the socks protocol that can only provide an IP address (rather
19553 than a hostname). Setups that do DNS locally over Tor are fine,
19554 and we shouldn't spam the logs in that case.
19555 - Convert the HACKING file to asciidoc, and add a few new sections
19556 to it, explaining how we use Git, how we make changelogs, and
19557 what should go in a patch.
19558 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
19559 event, to give information on the current rate of circuit timeouts
19560 over our stored history.
19561 - Add ability to disable circuit build time learning via consensus
19562 parameter and via a LearnCircuitBuildTimeout config option. Also
19563 automatically disable circuit build time calculation if we are
19564 either a AuthoritativeDirectory, or if we fail to write our state
19565 file. Fixes bug 1296.
19566 - More gracefully handle corrupt state files, removing asserts
19567 in favor of saving a backup and resetting state.
19568 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
19572 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
19574 - When a2x fails, mention that the user could disable manpages instead
19575 of trying to fix their asciidoc installation.
19576 - Where available, use Libevent 2.0's periodic timers so that our
19577 once-per-second cleanup code gets called even more closely to
19578 once per second than it would otherwise. Fixes bug 943.
19579 - If you run a bridge that listens on multiple IP addresses, and
19580 some user configures a bridge address that uses a different IP
19581 address than your bridge writes in its router descriptor, and the
19582 user doesn't specify an identity key, their Tor would discard the
19583 descriptor because "it isn't one of our configured bridges", and
19584 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
19585 Bugfix on 0.2.0.3-alpha.
19586 - If OpenSSL fails to make a duplicate of a private or public key, log
19587 an error message and try to exit cleanly. May help with debugging
19588 if bug 1209 ever remanifests.
19589 - Save a couple bytes in memory allocation every time we escape
19590 certain characters in a string. Patch from Florian Zumbiehl.
19591 - Make it explicit that we don't cannibalize one-hop circuits. This
19592 happens in the wild, but doesn't turn out to be a problem because
19593 we fortunately don't use those circuits. Many thanks to outofwords
19594 for the initial analysis and to swissknife who confirmed that
19595 two-hop circuits are actually created.
19596 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
19597 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
19598 - Eliminate a case where a circuit build time warning was displayed
19599 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
19602 Changes in version 0.2.1.26 - 2010-05-02
19603 Tor 0.2.1.26 addresses the recent connection and memory overload
19604 problems we've been seeing on relays, especially relays with their
19605 DirPort open. If your relay has been crashing, or you turned it off
19606 because it used too many resources, give this release a try.
19608 This release also fixes yet another instance of broken OpenSSL libraries
19609 that was causing some relays to drop out of the consensus.
19612 - Teach relays to defend themselves from connection overload. Relays
19613 now close idle circuits early if it looks like they were intended
19614 for directory fetches. Relays are also more aggressive about closing
19615 TLS connections that have no circuits on them. Such circuits are
19616 unlikely to be re-used, and tens of thousands of them were piling
19617 up at the fast relays, causing the relays to run out of sockets
19618 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
19619 their directory fetches over TLS).
19620 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
19621 that claim to be earlier than 0.9.8m, but which have in reality
19622 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
19623 behavior. Possible fix for some cases of bug 1346.
19624 - Directory mirrors were fetching relay descriptors only from v2
19625 directory authorities, rather than v3 authorities like they should.
19626 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
19627 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
19630 - Finally get rid of the deprecated and now harmful notion of "clique
19631 mode", where directory authorities maintain TLS connections to
19635 - In the util/threads test, no longer free the test_mutex before all
19636 worker threads have finished. Bugfix on 0.2.1.6-alpha.
19637 - The master thread could starve the worker threads quite badly on
19638 certain systems, causing them to run only partially in the allowed
19639 window. This resulted in test failures. Now the master thread sleeps
19640 occasionally for a few microseconds while the two worker-threads
19641 compete for the mutex. Bugfix on 0.2.0.1-alpha.
19644 Changes in version 0.2.2.13-alpha - 2010-04-24
19645 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
19646 problems we've been seeing on relays, especially relays with their
19647 DirPort open. If your relay has been crashing, or you turned it off
19648 because it used too many resources, give this release a try.
19651 - Teach relays to defend themselves from connection overload. Relays
19652 now close idle circuits early if it looks like they were intended
19653 for directory fetches. Relays are also more aggressive about closing
19654 TLS connections that have no circuits on them. Such circuits are
19655 unlikely to be re-used, and tens of thousands of them were piling
19656 up at the fast relays, causing the relays to run out of sockets
19657 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
19658 their directory fetches over TLS).
19661 - Finally get rid of the deprecated and now harmful notion of "clique
19662 mode", where directory authorities maintain TLS connections to
19664 - Directory authorities now do an immediate reachability check as soon
19665 as they hear about a new relay. This change should slightly reduce
19666 the time between setting up a relay and getting listed as running
19667 in the consensus. It should also improve the time between setting
19668 up a bridge and seeing use by bridge users.
19669 - Directory authorities no longer launch a TLS connection to every
19670 relay as they startup. Now that we have 2k+ descriptors cached,
19671 the resulting network hiccup is becoming a burden. Besides,
19672 authorities already avoid voting about Running for the first half
19673 hour of their uptime.
19676 Changes in version 0.2.2.12-alpha - 2010-04-20
19677 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
19678 handle and vote on descriptors. It was causing relays to drop out of
19682 - Many relays have been falling out of the consensus lately because
19683 not enough authorities know about their descriptor for them to get
19684 a majority of votes. When we deprecated the v2 directory protocol,
19685 we got rid of the only way that v3 authorities can hear from each
19686 other about other descriptors. Now authorities examine every v3
19687 vote for new descriptors, and fetch them from that authority. Bugfix
19689 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
19690 and a warning in or.h related to bandwidth_weight_rule_t that
19691 prevented clean compile on OS X. Fixes bug 1363; bugfix on
19693 - Fix a segfault on relays when DirReqStatistics is enabled
19694 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
19698 - Demote a confusing TLS warning that relay operators might get when
19699 someone tries to talk to their OrPort. It is neither the operator's
19700 fault nor can they do anything about it. Fixes bug 1364; bugfix
19704 Changes in version 0.2.2.11-alpha - 2010-04-15
19705 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
19706 libraries that was causing some relays to drop out of the consensus.
19709 - Directory mirrors were fetching relay descriptors only from v2
19710 directory authorities, rather than v3 authorities like they should.
19711 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
19712 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
19713 - Fix a parsing error that made every possible value of
19714 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
19715 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
19716 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
19717 about the option without breaking older ones.
19718 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
19719 that claim to be earlier than 0.9.8m, but which have in reality
19720 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
19721 behavior. Possible fix for some cases of bug 1346.
19724 - Experiment with a more aggressive approach to preventing clients
19725 from making one-hop exit streams. Exit relays who want to try it
19726 out can set "RefuseUnknownExits 1" in their torrc, and then look
19727 for "Attempt by %s to open a stream" log messages. Let us know
19729 - Add support for statically linking zlib by specifying
19730 --enable-static-zlib, to go with our support for statically linking
19731 openssl and libevent. Resolves bug 1358.
19734 - Fix a segfault that happens whenever a Tor client that is using
19735 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
19737 - When we cleaned up the contrib/tor-exit-notice.html file, we left
19738 out the first line. Fixes bug 1295.
19739 - When building the manpage from a tarball, we required asciidoc, but
19740 the asciidoc -> roff/html conversion was already done for the
19741 tarball. Make 'make' complain only when we need asciidoc (either
19742 because we're compiling directly from git, or because we altered
19743 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
19744 - When none of the directory authorities vote on any params, Tor
19745 segfaulted when trying to make the consensus from the votes. We
19746 didn't trigger the bug in practice, because authorities do include
19747 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
19750 - In the util/threads test, no longer free the test_mutex before all
19751 worker threads have finished. Bugfix on 0.2.1.6-alpha.
19752 - The master thread could starve the worker threads quite badly on
19753 certain systems, causing them to run only partially in the allowed
19754 window. This resulted in test failures. Now the master thread sleeps
19755 occasionally for a few microseconds while the two worker-threads
19756 compete for the mutex. Bugfix on 0.2.0.1-alpha.
19759 Changes in version 0.2.2.10-alpha - 2010-03-07
19760 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
19761 could prevent relays from guessing their IP address correctly. It also
19762 starts the groundwork for another client-side performance boost, since
19763 currently we're not making efficient use of relays that have both the
19764 Guard flag and the Exit flag.
19767 - Fix a regression from our patch for bug 1244 that caused relays
19768 to guess their IP address incorrectly if they didn't set Address
19769 in their torrc and/or their address fails to resolve. Bugfix on
19770 0.2.2.9-alpha; fixes bug 1269.
19772 o Major features (performance):
19773 - Directory authorities now compute consensus weightings that instruct
19774 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
19775 and no flag. Clients that use these weightings will distribute
19776 network load more evenly across these different relay types. The
19777 weightings are in the consensus so we can change them globally in
19778 the future. Extra thanks to "outofwords" for finding some nasty
19779 security bugs in the first implementation of this feature.
19781 o Minor features (performance):
19782 - Always perform router selections using weighted relay bandwidth,
19783 even if we don't need a high capacity circuit at the time. Non-fast
19784 circuits now only differ from fast ones in that they can use relays
19785 not marked with the Fast flag. This "feature" could turn out to
19786 be a horrible bug; we should investigate more before it goes into
19790 - Allow disabling building of the manpages. Skipping the manpage
19791 speeds up the build considerably.
19793 o Minor bugfixes (on 0.2.2.x):
19794 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
19795 Bugfix on 0.2.2.9-alpha.
19796 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
19797 config option. Bugfix on 0.2.2.7-alpha.
19798 - Ship the asciidoc-helper file in the tarball, so that people can
19799 build from source if they want to, and touching the .1.txt files
19800 doesn't break the build. Bugfix on 0.2.2.9-alpha.
19802 o Minor bugfixes (on 0.2.1.x or earlier):
19803 - Fix a dereference-then-NULL-check sequence when publishing
19804 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
19806 - Fix another dereference-then-NULL-check sequence. Bugfix on
19807 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
19808 - Make sure we treat potentially not NUL-terminated strings correctly.
19809 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
19811 o Code simplifications and refactoring:
19812 - Fix some urls in the exit notice file and make it XHTML1.1 strict
19813 compliant. Based on a patch from Christian Kujau.
19814 - Don't use sed in asciidoc-helper anymore.
19815 - Make the build process fail if asciidoc cannot be found and
19816 building with asciidoc isn't disabled.
19819 Changes in version 0.2.2.9-alpha - 2010-02-22
19820 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
19821 location of a directory authority, and cleans up a bunch of small bugs.
19823 o Directory authority changes:
19824 - Change IP address for dannenberg (v3 directory authority), and
19825 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
19826 service directory authority) from the list.
19829 - Make Tor work again on the latest OS X: when deciding whether to
19830 use strange flags to turn TLS renegotiation on, detect the OpenSSL
19831 version at run-time, not compile time. We need to do this because
19832 Apple doesn't update its dev-tools headers when it updates its
19833 libraries in a security patch.
19834 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
19835 that could happen on 32-bit platforms with 64-bit time_t. Also fix
19836 a memory leak when requesting a hidden service descriptor we've
19837 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
19839 - Authorities could be tricked into giving out the Exit flag to relays
19840 that didn't allow exiting to any ports. This bug could screw
19841 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
19842 1238. Bug discovered by Martin Kowalczyk.
19843 - When freeing a session key, zero it out completely. We only zeroed
19844 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
19845 patched by ekir. Fixes bug 1254.
19848 - Fix static compilation by listing the openssl libraries in the right
19849 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
19850 - Resume handling .exit hostnames in a special way: originally we
19851 stripped the .exit part and used the requested exit relay. In
19852 0.2.2.1-alpha we stopped treating them in any special way, meaning
19853 if you use a .exit address then Tor will pass it on to the exit
19854 relay. Now we reject the .exit stream outright, since that behavior
19855 might be more expected by the user. Found and diagnosed by Scott
19856 Bennett and Downie on or-talk.
19857 - Don't spam the controller with events when we have no file
19858 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
19859 for log messages was already solved from bug 748.)
19860 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
19862 - Make the DNSPort option work with libevent 2.x. Don't alter the
19863 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
19864 - Emit a GUARD DROPPED controller event for a case we missed.
19865 - Make more fields in the controller protocol case-insensitive, since
19866 control-spec.txt said they were.
19867 - Refactor resolve_my_address() to not use gethostbyname() anymore.
19868 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
19869 - Fix a spec conformance issue: the network-status-version token
19870 must be the first token in a v3 consensus or vote. Discovered by
19871 parakeep. Bugfix on 0.2.0.3-alpha.
19873 o Code simplifications and refactoring:
19874 - Generate our manpage and HTML documentation using Asciidoc. This
19875 change should make it easier to maintain the documentation, and
19876 produce nicer HTML.
19877 - Remove the --enable-iphone option. According to reports from Marco
19878 Bonetti, Tor builds fine without any special tweaking on recent
19879 iPhone SDK versions.
19880 - Removed some unnecessary files from the source distribution. The
19881 AUTHORS file has now been merged into the people page on the
19882 website. The roadmaps and design doc can now be found in the
19883 projects directory in svn.
19884 - Enabled various circuit build timeout constants to be controlled
19885 by consensus parameters. Also set better defaults for these
19886 parameters based on experimentation on broadband and simulated
19887 high latency links.
19890 - The 'EXTENDCIRCUIT' control port command can now be used with
19891 a circ id of 0 and no path. This feature will cause Tor to build
19892 a new 'fast' general purpose circuit using its own path selection
19894 - Added a BUILDTIMEOUT_SET controller event to describe changes
19895 to the circuit build timeout.
19896 - Future-proof the controller protocol a bit by ignoring keyword
19897 arguments we do not recognize.
19898 - Expand homedirs passed to tor-checkkey. This should silence a
19899 coverity complaint about passing a user-supplied string into
19900 open() without checking it.
19903 Changes in version 0.2.1.25 - 2010-03-16
19904 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
19905 prevent relays from guessing their IP address correctly. It also fixes
19906 several minor potential security bugs.
19909 - Fix a regression from our patch for bug 1244 that caused relays
19910 to guess their IP address incorrectly if they didn't set Address
19911 in their torrc and/or their address fails to resolve. Bugfix on
19912 0.2.1.23; fixes bug 1269.
19913 - When freeing a session key, zero it out completely. We only zeroed
19914 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
19915 patched by ekir. Fixes bug 1254.
19918 - Fix a dereference-then-NULL-check sequence when publishing
19919 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
19921 - Fix another dereference-then-NULL-check sequence. Bugfix on
19922 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
19923 - Make sure we treat potentially not NUL-terminated strings correctly.
19924 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
19928 Changes in version 0.2.1.24 - 2010-02-21
19929 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
19933 - Work correctly out-of-the-box with even more vendor-patched versions
19934 of OpenSSL. In particular, make it so Debian and OS X don't need
19935 customized patches to run/build.
19938 Changes in version 0.2.1.23 - 2010-02-13
19939 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
19940 again on the latest OS X, and updates the location of a directory
19943 o Major bugfixes (performance):
19944 - We were selecting our guards uniformly at random, and then weighting
19945 which of our guards we'd use uniformly at random. This imbalance
19946 meant that Tor clients were severely limited on throughput (and
19947 probably latency too) by the first hop in their circuit. Now we
19948 select guards weighted by currently advertised bandwidth. We also
19949 automatically discard guards picked using the old algorithm. Fixes
19950 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
19953 - Make Tor work again on the latest OS X: when deciding whether to
19954 use strange flags to turn TLS renegotiation on, detect the OpenSSL
19955 version at run-time, not compile time. We need to do this because
19956 Apple doesn't update its dev-tools headers when it updates its
19957 libraries in a security patch.
19958 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
19959 that could happen on 32-bit platforms with 64-bit time_t. Also fix
19960 a memory leak when requesting a hidden service descriptor we've
19961 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
19964 o Directory authority changes:
19965 - Change IP address for dannenberg (v3 directory authority), and
19966 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
19967 service directory authority) from the list.
19970 - Refactor resolve_my_address() to not use gethostbyname() anymore.
19971 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
19974 - Avoid a mad rush at the beginning of each month when each client
19975 rotates half of its guards. Instead we spread the rotation out
19976 throughout the month, but we still avoid leaving a precise timestamp
19977 in the state file about when we first picked the guard. Improves
19978 over the behavior introduced in 0.1.2.17.
19981 Changes in version 0.2.2.8-alpha - 2010-01-26
19982 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
19983 causing bridge relays to disappear. If you're running a bridge,
19987 - Fix a memory corruption bug on bridges that occurred during the
19988 inclusion of stats data in extra-info descriptors. Also fix the
19989 interface for geoip_get_bridge_stats* to prevent similar bugs in
19990 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
19991 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
19994 - Ignore OutboundBindAddress when connecting to localhost.
19995 Connections to localhost need to come _from_ localhost, or else
19996 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
20000 Changes in version 0.2.2.7-alpha - 2010-01-19
20001 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
20002 as laying the groundwork for further relay-side performance fixes. It
20003 also starts cleaning up client behavior with respect to the EntryNodes,
20004 ExitNodes, and StrictNodes config options.
20006 This release also rotates two directory authority keys, due to a
20007 security breach of some of the Torproject servers.
20009 o Directory authority changes:
20010 - Rotate keys (both v3 identity and relay identity) for moria1
20013 o Major features (performance):
20014 - We were selecting our guards uniformly at random, and then weighting
20015 which of our guards we'd use uniformly at random. This imbalance
20016 meant that Tor clients were severely limited on throughput (and
20017 probably latency too) by the first hop in their circuit. Now we
20018 select guards weighted by currently advertised bandwidth. We also
20019 automatically discard guards picked using the old algorithm. Fixes
20020 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
20021 - When choosing which cells to relay first, relays can now favor
20022 circuits that have been quiet recently, to provide lower latency
20023 for low-volume circuits. By default, relays enable or disable this
20024 feature based on a setting in the consensus. You can override
20025 this default by using the new "CircuitPriorityHalflife" config
20026 option. Design and code by Ian Goldberg, Can Tang, and Chris
20028 - Add separate per-conn write limiting to go with the per-conn read
20029 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
20030 but never per-conn write limits.
20031 - New consensus params "bwconnrate" and "bwconnburst" to let us
20032 rate-limit client connections as they enter the network. It's
20033 controlled in the consensus so we can turn it on and off for
20034 experiments. It's starting out off. Based on proposal 163.
20036 o Major features (relay selection options):
20037 - Switch to a StrictNodes config option, rather than the previous
20038 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
20039 "StrictExcludeNodes" option.
20040 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
20041 change during a config reload, mark and discard all our origin
20042 circuits. This fix should address edge cases where we change the
20043 config options and but then choose a circuit that we created before
20045 - If EntryNodes or ExitNodes are set, be more willing to use an
20046 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
20048 - Make EntryNodes config option much more aggressive even when
20049 StrictNodes is not set. Before it would prepend your requested
20050 entrynodes to your list of guard nodes, but feel free to use others
20051 after that. Now it chooses only from your EntryNodes if any of
20052 those are available, and only falls back to others if a) they're
20053 all down and b) StrictNodes is not set.
20054 - Now we refresh your entry guards from EntryNodes at each consensus
20055 fetch -- rather than just at startup and then they slowly rot as
20056 the network changes.
20059 - Stop bridge directory authorities from answering dbg-stability.txt
20060 directory queries, which would let people fetch a list of all
20061 bridge identities they track. Bugfix on 0.2.1.6-alpha.
20064 - Log a notice when we get a new control connection. Now it's easier
20065 for security-conscious users to recognize when a local application
20066 is knocking on their controller door. Suggested by bug 1196.
20067 - New config option "CircuitStreamTimeout" to override our internal
20068 timeout schedule for how many seconds until we detach a stream from
20069 a circuit and try a new circuit. If your network is particularly
20070 slow, you might want to set this to a number like 60.
20071 - New controller command "getinfo config-text". It returns the
20072 contents that Tor would write if you send it a SAVECONF command,
20073 so the controller can write the file to disk itself.
20074 - New options for SafeLogging to allow scrubbing only log messages
20075 generated while acting as a relay.
20076 - Ship the bridges spec file in the tarball too.
20077 - Avoid a mad rush at the beginning of each month when each client
20078 rotates half of its guards. Instead we spread the rotation out
20079 throughout the month, but we still avoid leaving a precise timestamp
20080 in the state file about when we first picked the guard. Improves
20081 over the behavior introduced in 0.1.2.17.
20083 o Minor bugfixes (compiling):
20084 - Fix compilation on OS X 10.3, which has a stub mlockall() but
20085 hides it. Bugfix on 0.2.2.6-alpha.
20086 - Fix compilation on Solaris by removing support for the
20087 DisableAllSwap config option. Solaris doesn't have an rlimit for
20088 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
20091 o Minor bugfixes (crashes):
20092 - Do not segfault when writing buffer stats when we haven't observed
20093 a single circuit to report about. Found by Fabian Lanze. Bugfix on
20095 - If we're in the pathological case where there's no exit bandwidth
20096 but there is non-exit bandwidth, or no guard bandwidth but there
20097 is non-guard bandwidth, don't crash during path selection. Bugfix
20099 - Fix an impossible-to-actually-trigger buffer overflow in relay
20100 descriptor generation. Bugfix on 0.1.0.15.
20102 o Minor bugfixes (privacy):
20103 - Fix an instance where a Tor directory mirror might accidentally
20104 log the IP address of a misbehaving Tor client. Bugfix on
20106 - Don't list Windows capabilities in relay descriptors. We never made
20107 use of them, and maybe it's a bad idea to publish them. Bugfix
20110 o Minor bugfixes (other):
20111 - Resolve an edge case in path weighting that could make us misweight
20112 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
20113 - Fix statistics on client numbers by country as seen by bridges that
20114 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
20115 intervals instead of variable 12-to-48-hour intervals.
20116 - After we free an internal connection structure, overwrite it
20117 with a different memory value than we use for overwriting a freed
20118 internal circuit structure. Should help with debugging. Suggested
20120 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
20123 o Removed features:
20124 - Remove the HSAuthorityRecordStats option that version 0 hidden
20125 service authorities could have used to track statistics of overall
20126 hidden service usage.
20129 Changes in version 0.2.1.22 - 2010-01-19
20130 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
20131 authorities -- it would tell you its whole history of bridge descriptors
20132 if you make the right directory request. This stable update also
20133 rotates two of the seven v3 directory authority keys and locations.
20135 o Directory authority changes:
20136 - Rotate keys (both v3 identity and relay identity) for moria1
20140 - Stop bridge directory authorities from answering dbg-stability.txt
20141 directory queries, which would let people fetch a list of all
20142 bridge identities they track. Bugfix on 0.2.1.6-alpha.
20145 Changes in version 0.2.1.21 - 2009-12-21
20146 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
20147 library. If you use Tor on Linux / Unix and you're getting SSL
20148 renegotiation errors, upgrading should help. We also recommend an
20149 upgrade if you're an exit relay.
20152 - Work around a security feature in OpenSSL 0.9.8l that prevents our
20153 handshake from working unless we explicitly tell OpenSSL that we
20154 are using SSL renegotiation safely. We are, of course, but OpenSSL
20155 0.9.8l won't work unless we say we are.
20156 - Avoid crashing if the client is trying to upload many bytes and the
20157 circuit gets torn down at the same time, or if the flip side
20158 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
20161 - Do not refuse to learn about authority certs and v2 networkstatus
20162 documents that are older than the latest consensus. This bug might
20163 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
20164 Spotted and fixed by xmux.
20165 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
20166 trigger platform-specific option misparsing case found by Coverity
20168 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
20169 trigger assert. Fixes bug 1173.
20172 Changes in version 0.2.2.6-alpha - 2009-11-19
20173 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
20174 support for the new lower-footprint "microdescriptor" directory design,
20175 future-proofing our consensus format against new hash functions or
20176 other changes, and an Android port. It also makes Tor compatible with
20177 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
20180 - Directory authorities can now create, vote on, and serve multiple
20181 parallel formats of directory data as part of their voting process.
20182 Partially implements Proposal 162: "Publish the consensus in
20184 - Directory authorities can now agree on and publish small summaries
20185 of router information that clients can use in place of regular
20186 server descriptors. This transition will eventually allow clients
20187 to use far less bandwidth for downloading information about the
20188 network. Begins the implementation of Proposal 158: "Clients
20189 download consensus + microdescriptors".
20190 - The directory voting system is now extensible to use multiple hash
20191 algorithms for signatures and resource selection. Newer formats
20192 are signed with SHA256, with a possibility for moving to a better
20193 hash algorithm in the future.
20194 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
20195 current and future memory pages via mlockall(). On supported
20196 platforms (modern Linux and probably BSD but not Windows or OS X),
20197 this should effectively disable any and all attempts to page out
20198 memory. This option requires that you start your Tor as root --
20199 if you use DisableAllSwap, please consider using the User option
20200 to properly reduce the privileges of your Tor.
20201 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
20202 to help Tor build correctly for Android phones.
20205 - Work around a security feature in OpenSSL 0.9.8l that prevents our
20206 handshake from working unless we explicitly tell OpenSSL that we
20207 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
20208 won't work unless we say we are.
20211 - Fix a crash bug when trying to initialize the evdns module in
20212 Libevent 2. Bugfix on 0.2.1.16-rc.
20213 - Stop logging at severity 'warn' when some other Tor client tries
20214 to establish a circuit with us using weak DH keys. It's a protocol
20215 violation, but that doesn't mean ordinary users need to hear about
20216 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
20217 - Do not refuse to learn about authority certs and v2 networkstatus
20218 documents that are older than the latest consensus. This bug might
20219 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
20220 Spotted and fixed by xmux.
20221 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
20222 - If all authorities restart at once right before a consensus vote,
20223 nobody will vote about "Running", and clients will get a consensus
20224 with no usable relays. Instead, authorities refuse to build a
20225 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
20226 - If your relay can't keep up with the number of incoming create
20227 cells, it would log one warning per failure into your logs. Limit
20228 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
20229 - Bridges now use "reject *:*" as their default exit policy. Bugfix
20230 on 0.2.0.3-alpha; fixes bug 1113.
20231 - Fix a memory leak on directory authorities during voting that was
20232 introduced in 0.2.2.1-alpha. Found via valgrind.
20235 Changes in version 0.2.1.20 - 2009-10-15
20236 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
20237 services at once, prepares for more performance improvements, and
20238 fixes a bunch of smaller bugs.
20240 The Windows and OS X bundles also include a more recent Vidalia,
20241 and switch from Privoxy to Polipo.
20243 The OS X installers are now drag and drop. It's best to un-install
20244 Tor/Vidalia and then install this new bundle, rather than upgrade. If
20245 you want to upgrade, you'll need to update the paths for Tor and Polipo
20246 in the Vidalia Settings window.
20249 - Send circuit or stream sendme cells when our window has decreased
20250 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
20251 by Karsten when testing the "reduce circuit window" performance
20252 patch. Bugfix on the 54th commit on Tor -- from July 2002,
20253 before the release of Tor 0.0.0. This is the new winner of the
20255 - Fix a remotely triggerable memory leak when a consensus document
20256 contains more than one signature from the same voter. Bugfix on
20258 - Avoid segfault in rare cases when finishing an introduction circuit
20259 as a client and finding out that we don't have an introduction key
20260 for it. Fixes bug 1073. Reported by Aaron Swartz.
20263 - Tor now reads the "circwindow" parameter out of the consensus,
20264 and uses that value for its circuit package window rather than the
20265 default of 1000 cells. Begins the implementation of proposal 168.
20267 o New directory authorities:
20268 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
20270 - Move moria1 and tonga to alternate IP addresses.
20273 - Fix a signed/unsigned compile warning in 0.2.1.19.
20274 - Fix possible segmentation fault on directory authorities. Bugfix on
20276 - Fix an extremely rare infinite recursion bug that could occur if
20277 we tried to log a message after shutting down the log subsystem.
20278 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
20279 - Fix an obscure bug where hidden services on 64-bit big-endian
20280 systems might mis-read the timestamp in v3 introduce cells, and
20281 refuse to connect back to the client. Discovered by "rotor".
20282 Bugfix on 0.2.1.6-alpha.
20283 - We were triggering a CLOCK_SKEW controller status event whenever
20284 we connect via the v2 connection protocol to any relay that has
20285 a wrong clock. Instead, we should only inform the controller when
20286 it's a trusted authority that claims our clock is wrong. Bugfix
20287 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
20288 - We were telling the controller about CHECKING_REACHABILITY and
20289 REACHABILITY_FAILED status events whenever we launch a testing
20290 circuit or notice that one has failed. Instead, only tell the
20291 controller when we want to inform the user of overall success or
20292 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
20294 - Don't warn when we're using a circuit that ends with a node
20295 excluded in ExcludeExitNodes, but the circuit is not used to access
20296 the outside world. This should help fix bug 1090. Bugfix on
20298 - Work around a small memory leak in some versions of OpenSSL that
20299 stopped the memory used by the hostname TLS extension from being
20303 - Add a "getinfo status/accepted-server-descriptor" controller
20304 command, which is the recommended way for controllers to learn
20305 whether our server descriptor has been successfully received by at
20306 least on directory authority. Un-recommend good-server-descriptor
20307 getinfo and status events until we have a better design for them.
20310 Changes in version 0.2.2.5-alpha - 2009-10-11
20311 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
20314 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
20316 o Directory authorities:
20317 - Temporarily (just for this release) move dizum to an alternate
20321 Changes in version 0.2.2.4-alpha - 2009-10-10
20322 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
20323 introduces a new unit test framework, shifts directry authority
20324 addresses around to reduce the impact from recent blocking events,
20325 and fixes a few smaller bugs.
20328 - Fix several more asserts in the circuit_build_times code, for
20329 example one that causes Tor to fail to start once we have
20330 accumulated 5000 build times in the state file. Bugfixes on
20331 0.2.2.2-alpha; fixes bug 1108.
20333 o New directory authorities:
20334 - Move moria1 and Tonga to alternate IP addresses.
20337 - Log SSL state transitions at debug level during handshake, and
20338 include SSL states in error messages. This may help debug future
20339 SSL handshake issues.
20340 - Add a new "Handshake" log domain for activities that happen
20341 during the TLS handshake.
20342 - Revert to the "June 3 2009" ip-to-country file. The September one
20343 seems to have removed most US IP addresses.
20344 - Directory authorities now reject Tor relays with versions less than
20345 0.1.2.14. This step cuts out four relays from the current network,
20346 none of which are very big.
20349 - Fix a couple of smaller issues with gathering statistics. Bugfixes
20351 - Fix two memory leaks in the error case of
20352 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
20353 - Don't count one-hop circuits when we're estimating how long it
20354 takes circuits to build on average. Otherwise we'll set our circuit
20355 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
20356 - Directory authorities no longer change their opinion of, or vote on,
20357 whether a router is Running, unless they have themselves been
20358 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
20361 o Code simplifications and refactoring:
20362 - Revise our unit tests to use the "tinytest" framework, so we
20363 can run tests in their own processes, have smarter setup/teardown
20364 code, and so on. The unit test code has moved to its own
20365 subdirectory, and has been split into multiple modules.
20368 Changes in version 0.2.2.3-alpha - 2009-09-23
20369 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
20372 - Fix an overzealous assert in our new circuit build timeout code.
20373 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
20376 - If the networkstatus consensus tells us that we should use a
20377 negative circuit package window, ignore it. Otherwise we'll
20378 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
20381 Changes in version 0.2.2.2-alpha - 2009-09-21
20382 Tor 0.2.2.2-alpha introduces our latest performance improvement for
20383 clients: Tor tracks the average time it takes to build a circuit, and
20384 avoids using circuits that take too long to build. For fast connections,
20385 this feature can cut your expected latency in half. For slow or flaky
20386 connections, it could ruin your Tor experience. Let us know if it does!
20389 - Tor now tracks how long it takes to build client-side circuits
20390 over time, and adapts its timeout to local network performance.
20391 Since a circuit that takes a long time to build will also provide
20392 bad performance, we get significant latency improvements by
20393 discarding the slowest 20% of circuits. Specifically, Tor creates
20394 circuits more aggressively than usual until it has enough data
20395 points for a good timeout estimate. Implements proposal 151.
20396 We are especially looking for reports (good and bad) from users with
20397 both EDGE and broadband connections that can move from broadband
20398 to EDGE and find out if the build-time data in the .tor/state gets
20399 reset without loss of Tor usability. You should also see a notice
20400 log message telling you that Tor has reset its timeout.
20401 - Directory authorities can now vote on arbitrary integer values as
20402 part of the consensus process. This is designed to help set
20403 network-wide parameters. Implements proposal 167.
20404 - Tor now reads the "circwindow" parameter out of the consensus,
20405 and uses that value for its circuit package window rather than the
20406 default of 1000 cells. Begins the implementation of proposal 168.
20409 - Fix a remotely triggerable memory leak when a consensus document
20410 contains more than one signature from the same voter. Bugfix on
20414 - Fix an extremely rare infinite recursion bug that could occur if
20415 we tried to log a message after shutting down the log subsystem.
20416 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
20417 - Fix parsing for memory or time units given without a space between
20418 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
20419 - A networkstatus vote must contain exactly one signature. Spec
20420 conformance issue. Bugfix on 0.2.0.3-alpha.
20421 - Fix an obscure bug where hidden services on 64-bit big-endian
20422 systems might mis-read the timestamp in v3 introduce cells, and
20423 refuse to connect back to the client. Discovered by "rotor".
20424 Bugfix on 0.2.1.6-alpha.
20425 - We were triggering a CLOCK_SKEW controller status event whenever
20426 we connect via the v2 connection protocol to any relay that has
20427 a wrong clock. Instead, we should only inform the controller when
20428 it's a trusted authority that claims our clock is wrong. Bugfix
20429 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
20430 - We were telling the controller about CHECKING_REACHABILITY and
20431 REACHABILITY_FAILED status events whenever we launch a testing
20432 circuit or notice that one has failed. Instead, only tell the
20433 controller when we want to inform the user of overall success or
20434 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
20436 - Don't warn when we're using a circuit that ends with a node
20437 excluded in ExcludeExitNodes, but the circuit is not used to access
20438 the outside world. This should help fix bug 1090, but more problems
20439 remain. Bugfix on 0.2.1.6-alpha.
20440 - Work around a small memory leak in some versions of OpenSSL that
20441 stopped the memory used by the hostname TLS extension from being
20443 - Make our 'torify' script more portable; if we have only one of
20444 'torsocks' or 'tsocks' installed, don't complain to the user;
20445 and explain our warning about tsocks better.
20448 - Add a "getinfo status/accepted-server-descriptor" controller
20449 command, which is the recommended way for controllers to learn
20450 whether our server descriptor has been successfully received by at
20451 least on directory authority. Un-recommend good-server-descriptor
20452 getinfo and status events until we have a better design for them.
20453 - Update to the "September 4 2009" ip-to-country file.
20456 Changes in version 0.2.2.1-alpha - 2009-08-26
20457 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
20458 Tor clients to bootstrap on networks where only port 80 is reachable,
20459 makes it more straightforward to support hardware crypto accelerators,
20460 and starts the groundwork for gathering stats safely at relays.
20463 - Start the process of disabling ".exit" address notation, since it
20464 can be used for a variety of esoteric application-level attacks
20465 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
20468 o New directory authorities:
20469 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
20473 - New AccelName and AccelDir options add support for dynamic OpenSSL
20474 hardware crypto acceleration engines.
20475 - Tor now supports tunneling all of its outgoing connections over
20476 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
20477 configuration options. Code by Christopher Davis.
20480 - Send circuit or stream sendme cells when our window has decreased
20481 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
20482 by Karsten when testing the "reduce circuit window" performance
20483 patch. Bugfix on the 54th commit on Tor -- from July 2002,
20484 before the release of Tor 0.0.0. This is the new winner of the
20487 o New options for gathering stats safely:
20488 - Directory mirrors that set "DirReqStatistics 1" write statistics
20489 about directory requests to disk every 24 hours. As compared to the
20490 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
20491 1) stats are written to disk exactly every 24 hours; 2) estimated
20492 shares of v2 and v3 requests are determined as mean values, not at
20493 the end of a measurement period; 3) unresolved requests are listed
20494 with country code '??'; 4) directories also measure download times.
20495 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
20496 number of exit streams and transferred bytes per port to disk every
20498 - Relays that set "CellStatistics 1" write statistics on how long
20499 cells spend in their circuit queues to disk every 24 hours.
20500 - Entry nodes that set "EntryStatistics 1" write statistics on the
20501 rough number and origins of connecting clients to disk every 24
20503 - Relays that write any of the above statistics to disk and set
20504 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
20505 their extra-info documents.
20508 - New --digests command-line switch to output the digests of the
20509 source files Tor was built with.
20510 - The "torify" script now uses torsocks where available.
20511 - The memarea code now uses a sentinel value at the end of each area
20512 to make sure nothing writes beyond the end of an area. This might
20513 help debug some conceivable causes of bug 930.
20514 - Time and memory units in the configuration file can now be set to
20515 fractional units. For example, "2.5 GB" is now a valid value for
20517 - Certain Tor clients (such as those behind check.torproject.org) may
20518 want to fetch the consensus in an extra early manner. To enable this
20519 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
20520 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
20521 as only certain clients who must have this information sooner should
20523 - Instead of adding the svn revision to the Tor version string, report
20524 the git commit (when we're building from a git checkout).
20527 - If any of the v3 certs we download are unparseable, we should
20528 actually notice the failure so we don't retry indefinitely. Bugfix
20529 on 0.2.0.x; reported by "rotator".
20530 - If the cached cert file is unparseable, warn but don't exit.
20531 - Fix possible segmentation fault on directory authorities. Bugfix on
20533 - When Tor fails to parse a descriptor of any kind, dump it to disk.
20534 Might help diagnosing bug 1051.
20536 o Deprecated and removed features:
20537 - The controller no longer accepts the old obsolete "addr-mappings/"
20538 or "unregistered-servers-" GETINFO values.
20539 - Hidden services no longer publish version 0 descriptors, and clients
20540 do not request or use version 0 descriptors. However, the old hidden
20541 service authorities still accept and serve version 0 descriptors
20542 when contacted by older hidden services/clients.
20543 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
20544 always on; using them is necessary for correct forward-compatible
20546 - Remove support for .noconnect style addresses. Nobody was using
20547 them, and they provided another avenue for detecting Tor users
20548 via application-level web tricks.
20550 o Packaging changes:
20551 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
20552 installer bundles. See
20553 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
20554 for details of what's new in Vidalia 0.2.3.
20555 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
20556 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
20557 configuration file, rather than the old Privoxy.
20558 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
20559 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
20560 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
20561 better compatibility with OS X 10.6, aka Snow Leopard.
20562 - OS X Vidalia Bundle: The multi-package installer is now replaced
20563 by a simple drag and drop to the /Applications folder. This change
20564 occurred with the upgrade to Vidalia 0.2.3.
20567 Changes in version 0.2.1.19 - 2009-07-28
20568 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
20569 services on Tor 0.2.1.3-alpha through 0.2.1.18.
20572 - Make accessing hidden services on 0.2.1.x work right again.
20573 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
20574 part of patch provided by "optimist".
20577 - When a relay/bridge is writing out its identity key fingerprint to
20578 the "fingerprint" file and to its logs, write it without spaces. Now
20579 it will look like the fingerprints in our bridges documentation,
20580 and confuse fewer users.
20583 - Relays no longer publish a new server descriptor if they change
20584 their MaxAdvertisedBandwidth config option but it doesn't end up
20585 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
20586 fixes bug 1026. Patch from Sebastian.
20587 - Avoid leaking memory every time we get a create cell but we have
20588 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
20589 fixes bug 1034. Reported by BarkerJr.
20592 Changes in version 0.2.1.18 - 2009-07-24
20593 Tor 0.2.1.18 lays the foundations for performance improvements,
20594 adds status events to help users diagnose bootstrap problems, adds
20595 optional authentication/authorization for hidden services, fixes a
20596 variety of potential anonymity problems, and includes a huge pile of
20597 other features and bug fixes.
20600 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
20603 Changes in version 0.2.1.17-rc - 2009-07-07
20604 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
20605 candidate for the 0.2.1.x series. It lays the groundwork for further
20606 client performance improvements, and also fixes a big bug with directory
20607 authorities that were causing them to assign Guard and Stable flags
20610 The Windows bundles also finally include the geoip database that we
20611 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
20612 should actually install Torbutton rather than giving you a cryptic
20613 failure message (oops).
20616 - Clients now use the bandwidth values in the consensus, rather than
20617 the bandwidth values in each relay descriptor. This approach opens
20618 the door to more accurate bandwidth estimates once the directory
20619 authorities start doing active measurements. Implements more of
20623 - When Tor clients restart after 1-5 days, they discard all their
20624 cached descriptors as too old, but they still use the cached
20625 consensus document. This approach is good for robustness, but
20626 bad for performance: since they don't know any bandwidths, they
20627 end up choosing at random rather than weighting their choice by
20628 speed. Fixed by the above feature of putting bandwidths in the
20629 consensus. Bugfix on 0.2.0.x.
20630 - Directory authorities were neglecting to mark relays down in their
20631 internal histories if the relays fall off the routerlist without
20632 ever being found unreachable. So there were relays in the histories
20633 that haven't been seen for eight months, and are listed as being
20634 up for eight months. This wreaked havoc on the "median wfu"
20635 and "median mtbf" calculations, in turn making Guard and Stable
20636 flags very wrong, hurting network performance. Fixes bugs 696 and
20637 969. Bugfix on 0.2.0.6-alpha.
20640 - Serve the DirPortFrontPage page even when we have been approaching
20641 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
20642 - The control port would close the connection before flushing long
20643 replies, such as the network consensus, if a QUIT command was issued
20644 before the reply had completed. Now, the control port flushes all
20645 pending replies before closing the connection. Also fixed a spurious
20646 warning when a QUIT command is issued after a malformed or rejected
20647 AUTHENTICATE command, but before the connection was closed. Patch
20648 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
20649 - When we can't find an intro key for a v2 hidden service descriptor,
20650 fall back to the v0 hidden service descriptor and log a bug message.
20651 Workaround for bug 1024.
20652 - Fix a log message that did not respect the SafeLogging option.
20656 - If we're a relay and we change our IP address, be more verbose
20657 about the reason that made us change. Should help track down
20658 further bugs for relays on dynamic IP addresses.
20661 Changes in version 0.2.0.35 - 2009-06-24
20663 - Avoid crashing in the presence of certain malformed descriptors.
20664 Found by lark, and by automated fuzzing.
20665 - Fix an edge case where a malicious exit relay could convince a
20666 controller that the client's DNS question resolves to an internal IP
20667 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
20670 - Finally fix the bug where dynamic-IP relays disappear when their
20671 IP address changes: directory mirrors were mistakenly telling
20672 them their old address if they asked via begin_dir, so they
20673 never got an accurate answer about their new address, so they
20674 just vanished after a day. For belt-and-suspenders, relays that
20675 don't set Address in their config now avoid using begin_dir for
20676 all direct connections. Should fix bugs 827, 883, and 900.
20677 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
20678 that would occur on some exit nodes when DNS failures and timeouts
20679 occurred in certain patterns. Fix for bug 957.
20682 - When starting with a cache over a few days old, do not leak
20683 memory for the obsolete router descriptors in it. Bugfix on
20684 0.2.0.33; fixes bug 672.
20685 - Hidden service clients didn't use a cached service descriptor that
20686 was older than 15 minutes, but wouldn't fetch a new one either,
20687 because there was already one in the cache. Now, fetch a v2
20688 descriptor unless the same descriptor was added to the cache within
20689 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
20692 Changes in version 0.2.1.16-rc - 2009-06-20
20693 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
20694 a bunch of minor bugs.
20697 - Fix an edge case where a malicious exit relay could convince a
20698 controller that the client's DNS question resolves to an internal IP
20699 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
20701 o Major performance improvements (on 0.2.0.x):
20702 - Disable and refactor some debugging checks that forced a linear scan
20703 over the whole server-side DNS cache. These accounted for over 50%
20704 of CPU time on a relatively busy exit node's gprof profile. Found
20706 - Disable some debugging checks that appeared in exit node profile
20710 - Update to the "June 3 2009" ip-to-country file.
20711 - Do not have tor-resolve automatically refuse all .onion addresses;
20712 if AutomapHostsOnResolve is set in your torrc, this will work fine.
20714 o Minor bugfixes (on 0.2.0.x):
20715 - Log correct error messages for DNS-related network errors on
20717 - Fix a race condition that could cause crashes or memory corruption
20718 when running as a server with a controller listening for log
20720 - Avoid crashing when we have a policy specified in a DirPolicy or
20721 SocksPolicy or ReachableAddresses option with ports set on it,
20722 and we re-load the policy. May fix bug 996.
20723 - Hidden service clients didn't use a cached service descriptor that
20724 was older than 15 minutes, but wouldn't fetch a new one either,
20725 because there was already one in the cache. Now, fetch a v2
20726 descriptor unless the same descriptor was added to the cache within
20727 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
20729 o Minor bugfixes (on 0.2.1.x):
20730 - Don't warn users about low port and hibernation mix when they
20731 provide a *ListenAddress directive to fix that. Bugfix on
20733 - When switching back and forth between bridge mode, do not start
20734 gathering GeoIP data until two hours have passed.
20735 - Do not complain that the user has requested an excluded node as
20736 an exit when the node is not really an exit. This could happen
20737 because the circuit was for testing, or an introduction point.
20741 Changes in version 0.2.1.15-rc - 2009-05-25
20742 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
20743 series. It fixes a major bug on fast exit relays, as well as a variety
20744 of more minor bugs.
20746 o Major bugfixes (on 0.2.0.x):
20747 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
20748 that would occur on some exit nodes when DNS failures and timeouts
20749 occurred in certain patterns. Fix for bug 957.
20751 o Minor bugfixes (on 0.2.0.x):
20752 - Actually return -1 in the error case for read_bandwidth_usage().
20753 Harmless bug, since we currently don't care about the return value
20754 anywhere. Bugfix on 0.2.0.9-alpha.
20755 - Provide a more useful log message if bug 977 (related to buffer
20756 freelists) ever reappears, and do not crash right away.
20757 - Fix an assertion failure on 64-bit platforms when we allocated
20758 memory right up to the end of a memarea, then realigned the memory
20759 one step beyond the end. Fixes a possible cause of bug 930.
20760 - Protect the count of open sockets with a mutex, so we can't
20761 corrupt it when two threads are closing or opening sockets at once.
20762 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
20763 - Don't allow a bridge to publish its router descriptor to a
20764 non-bridge directory authority. Fixes part of bug 932.
20765 - When we change to or from being a bridge, reset our counts of
20766 client usage by country. Fixes bug 932.
20767 - Fix a bug that made stream bandwidth get misreported to the
20769 - Stop using malloc_usable_size() to use more area than we had
20770 actually allocated: it was safe, but made valgrind really unhappy.
20771 - Fix a memory leak when v3 directory authorities load their keys
20772 and cert from disk. Bugfix on 0.2.0.1-alpha.
20774 o Minor bugfixes (on 0.2.1.x):
20775 - Fix use of freed memory when deciding to mark a non-addable
20776 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
20779 Changes in version 0.2.1.14-rc - 2009-04-12
20780 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
20781 series. It begins fixing some major performance problems, and also
20782 finally addresses the bug that was causing relays on dynamic IP
20783 addresses to fall out of the directory.
20786 - Clients replace entry guards that were chosen more than a few months
20787 ago. This change should significantly improve client performance,
20788 especially once more people upgrade, since relays that have been
20789 a guard for a long time are currently overloaded.
20791 o Major bugfixes (on 0.2.0):
20792 - Finally fix the bug where dynamic-IP relays disappear when their
20793 IP address changes: directory mirrors were mistakenly telling
20794 them their old address if they asked via begin_dir, so they
20795 never got an accurate answer about their new address, so they
20796 just vanished after a day. For belt-and-suspenders, relays that
20797 don't set Address in their config now avoid using begin_dir for
20798 all direct connections. Should fix bugs 827, 883, and 900.
20799 - Relays were falling out of the networkstatus consensus for
20800 part of a day if they changed their local config but the
20801 authorities discarded their new descriptor as "not sufficiently
20802 different". Now directory authorities accept a descriptor as changed
20803 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
20804 patch by Sebastian.
20805 - Avoid crashing in the presence of certain malformed descriptors.
20806 Found by lark, and by automated fuzzing.
20809 - When generating circuit events with verbose nicknames for
20810 controllers, try harder to look up nicknames for routers on a
20811 circuit. (Previously, we would look in the router descriptors we had
20812 for nicknames, but not in the consensus.) Partial fix for bug 941.
20813 - If the bridge config line doesn't specify a port, assume 443.
20814 This makes bridge lines a bit smaller and easier for users to
20816 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
20817 bytes (aka 20KB/s), to match our documentation. Also update
20818 directory authorities so they always assign the Fast flag to relays
20819 with 20KB/s of capacity. Now people running relays won't suddenly
20820 find themselves not seeing any use, if the network gets faster
20822 - Update to the "April 3 2009" ip-to-country file.
20825 - Avoid trying to print raw memory to the logs when we decide to
20826 give up on downloading a given relay descriptor. Bugfix on
20828 - In tor-resolve, when the Tor client to use is specified by
20829 <hostname>:<port>, actually use the specified port rather than
20830 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
20831 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
20832 - When starting with a cache over a few days old, do not leak
20833 memory for the obsolete router descriptors in it. Bugfix on
20835 - Avoid double-free on list of successfully uploaded hidden
20836 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
20837 - Change memarea_strndup() implementation to work even when
20838 duplicating a string at the end of a page. This bug was
20839 harmless for now, but could have meant crashes later. Fix by
20840 lark. Bugfix on 0.2.1.1-alpha.
20841 - Limit uploaded directory documents to be 16M rather than 500K.
20842 The directory authorities were refusing v3 consensus votes from
20843 other authorities, since the votes are now 504K. Fixes bug 959;
20844 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
20845 - Directory authorities should never send a 503 "busy" response to
20846 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
20850 Changes in version 0.2.1.13-alpha - 2009-03-09
20851 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
20852 cleanups. We're finally getting close to a release candidate.
20855 - Correctly update the list of which countries we exclude as
20856 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
20857 lark. Bugfix on 0.2.1.6-alpha.
20859 o Minor bugfixes (on 0.2.0.x and earlier):
20860 - Automatically detect MacOSX versions earlier than 10.4.0, and
20861 disable kqueue from inside Tor when running with these versions.
20862 We previously did this from the startup script, but that was no
20863 help to people who didn't use the startup script. Resolves bug 863.
20864 - When we had picked an exit node for a connection, but marked it as
20865 "optional", and it turned out we had no onion key for the exit,
20866 stop wanting that exit and try again. This situation may not
20867 be possible now, but will probably become feasible with proposal
20868 158. Spotted by rovv. Fixes another case of bug 752.
20869 - Clients no longer cache certificates for authorities they do not
20870 recognize. Bugfix on 0.2.0.9-alpha.
20871 - When we can't transmit a DNS request due to a network error, retry
20872 it after a while, and eventually transmit a failing response to
20873 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
20874 - If the controller claimed responsibility for a stream, but that
20875 stream never finished making its connection, it would live
20876 forever in circuit_wait state. Now we close it after SocksTimeout
20877 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
20878 - Drop begin cells to a hidden service if they come from the middle
20879 of a circuit. Patch from lark.
20880 - When we erroneously receive two EXTEND cells for the same circuit
20881 ID on the same connection, drop the second. Patch from lark.
20882 - Fix a crash that occurs on exit nodes when a nameserver request
20883 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
20884 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
20886 - Do not assume that a stack-allocated character array will be
20887 64-bit aligned on platforms that demand that uint64_t access is
20888 aligned. Possible fix for bug 604.
20889 - Parse dates and IPv4 addresses in a locale- and libc-independent
20890 manner, to avoid platform-dependent behavior on malformed input.
20891 - Build correctly when configured to build outside the main source
20892 path. Patch from Michael Gold.
20893 - We were already rejecting relay begin cells with destination port
20894 of 0. Now also reject extend cells with destination port or address
20895 of 0. Suggested by lark.
20897 o Minor bugfixes (on 0.2.1.x):
20898 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
20899 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
20900 - If we're an exit node, scrub the IP address to which we are exiting
20901 in the logs. Bugfix on 0.2.1.8-alpha.
20904 - On Linux, use the prctl call to re-enable core dumps when the user
20906 - New controller event NEWCONSENSUS that lists the networkstatus
20907 lines for every recommended relay. Now controllers like Torflow
20908 can keep up-to-date on which relays they should be using.
20909 - Update to the "February 26 2009" ip-to-country file.
20912 Changes in version 0.2.0.34 - 2009-02-08
20913 Tor 0.2.0.34 features several more security-related fixes. You should
20914 upgrade, especially if you run an exit relay (remote crash) or a
20915 directory authority (remote infinite loop), or you're on an older
20916 (pre-XP) or not-recently-patched Windows (remote exploit).
20918 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
20919 have many known flaws, and nobody should be using them. You should
20920 upgrade. If you're using a Linux or BSD and its packages are obsolete,
20921 stop using those packages and upgrade anyway.
20924 - Fix an infinite-loop bug on handling corrupt votes under certain
20925 circumstances. Bugfix on 0.2.0.8-alpha.
20926 - Fix a temporary DoS vulnerability that could be performed by
20927 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
20928 - Avoid a potential crash on exit nodes when processing malformed
20929 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
20930 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
20931 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
20934 - Fix compilation on systems where time_t is a 64-bit integer.
20935 Patch from Matthias Drochner.
20936 - Don't consider expiring already-closed client connections. Fixes
20937 bug 893. Bugfix on 0.0.2pre20.
20940 Changes in version 0.2.1.12-alpha - 2009-02-08
20941 Tor 0.2.1.12-alpha features several more security-related fixes. You
20942 should upgrade, especially if you run an exit relay (remote crash) or
20943 a directory authority (remote infinite loop), or you're on an older
20944 (pre-XP) or not-recently-patched Windows (remote exploit). It also
20945 includes a big pile of minor bugfixes and cleanups.
20948 - Fix an infinite-loop bug on handling corrupt votes under certain
20949 circumstances. Bugfix on 0.2.0.8-alpha.
20950 - Fix a temporary DoS vulnerability that could be performed by
20951 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
20952 - Avoid a potential crash on exit nodes when processing malformed
20953 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
20956 - Let controllers actually ask for the "clients_seen" event for
20957 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
20958 reported by Matt Edman.
20959 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
20961 - Fix a bug in address parsing that was preventing bridges or hidden
20962 service targets from being at IPv6 addresses.
20963 - Solve a bug that kept hardware crypto acceleration from getting
20964 enabled when accounting was turned on. Fixes bug 907. Bugfix on
20966 - Remove a bash-ism from configure.in to build properly on non-Linux
20967 platforms. Bugfix on 0.2.1.1-alpha.
20968 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
20969 headers. Bugfix on 0.2.0.10-alpha.
20970 - Don't consider expiring already-closed client connections. Fixes
20971 bug 893. Bugfix on 0.0.2pre20.
20972 - Fix another interesting corner-case of bug 891 spotted by rovv:
20973 Previously, if two hosts had different amounts of clock drift, and
20974 one of them created a new connection with just the wrong timing,
20975 the other might decide to deprecate the new connection erroneously.
20976 Bugfix on 0.1.1.13-alpha.
20977 - Resolve a very rare crash bug that could occur when the user forced
20978 a nameserver reconfiguration during the middle of a nameserver
20979 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
20980 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
20981 Bugfix on 0.2.1.7-alpha.
20982 - If we're using bridges and our network goes away, be more willing
20983 to forgive our bridges and try again when we get an application
20984 request. Bugfix on 0.2.0.x.
20987 - Support platforms where time_t is 64 bits long. (Congratulations,
20988 NetBSD!) Patch from Matthias Drochner.
20989 - Add a 'getinfo status/clients-seen' controller command, in case
20990 controllers want to hear clients_seen events but connect late.
20993 - Disable GCC's strict alias optimization by default, to avoid the
20994 likelihood of its introducing subtle bugs whenever our code violates
20995 the letter of C99's alias rules.
20998 Changes in version 0.2.0.33 - 2009-01-21
20999 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
21000 useful to users. It also finally fixes a bug where a relay or client
21001 that's been off for many days would take a long time to bootstrap.
21003 This update also fixes an important security-related bug reported by
21004 Ilja van Sprundel. You should upgrade. (We'll send out more details
21005 about the bug once people have had some time to upgrade.)
21008 - Fix a heap-corruption bug that may be remotely triggerable on
21009 some platforms. Reported by Ilja van Sprundel.
21012 - When a stream at an exit relay is in state "resolving" or
21013 "connecting" and it receives an "end" relay cell, the exit relay
21014 would silently ignore the end cell and not close the stream. If
21015 the client never closes the circuit, then the exit relay never
21016 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
21017 reported by "wood".
21018 - When sending CREATED cells back for a given circuit, use a 64-bit
21019 connection ID to find the right connection, rather than an addr:port
21020 combination. Now that we can have multiple OR connections between
21021 the same ORs, it is no longer possible to use addr:port to uniquely
21022 identify a connection.
21023 - Bridge relays that had DirPort set to 0 would stop fetching
21024 descriptors shortly after startup, and then briefly resume
21025 after a new bandwidth test and/or after publishing a new bridge
21026 descriptor. Bridge users that try to bootstrap from them would
21027 get a recent networkstatus but would get descriptors from up to
21028 18 hours earlier, meaning most of the descriptors were obsolete
21029 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
21030 - Prevent bridge relays from serving their 'extrainfo' document
21031 to anybody who asks, now that extrainfo docs include potentially
21032 sensitive aggregated client geoip summaries. Bugfix on
21034 - If the cached networkstatus consensus is more than five days old,
21035 discard it rather than trying to use it. In theory it could be
21036 useful because it lists alternate directory mirrors, but in practice
21037 it just means we spend many minutes trying directory mirrors that
21038 are long gone from the network. Also discard router descriptors as
21039 we load them if they are more than five days old, since the onion
21040 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
21043 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
21044 could make gcc generate non-functional binary search code. Bugfix
21046 - Build correctly on platforms without socklen_t.
21047 - Compile without warnings on solaris.
21048 - Avoid potential crash on internal error during signature collection.
21049 Fixes bug 864. Patch from rovv.
21050 - Correct handling of possible malformed authority signing key
21051 certificates with internal signature types. Fixes bug 880.
21052 Bugfix on 0.2.0.3-alpha.
21053 - Fix a hard-to-trigger resource leak when logging credential status.
21055 - When we can't initialize DNS because the network is down, do not
21056 automatically stop Tor from starting. Instead, we retry failed
21057 dns_init() every 10 minutes, and change the exit policy to reject
21058 *:* until one succeeds. Fixes bug 691.
21059 - Use 64 bits instead of 32 bits for connection identifiers used with
21060 the controller protocol, to greatly reduce risk of identifier reuse.
21061 - When we're choosing an exit node for a circuit, and we have
21062 no pending streams, choose a good general exit rather than one that
21063 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
21064 - Fix another case of assuming, when a specific exit is requested,
21065 that we know more than the user about what hosts it allows.
21066 Fixes one case of bug 752. Patch from rovv.
21067 - Clip the MaxCircuitDirtiness config option to a minimum of 10
21068 seconds. Warn the user if lower values are given in the
21069 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
21070 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
21071 user if lower values are given in the configuration. Bugfix on
21072 0.1.1.17-rc. Patch by Sebastian.
21073 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
21074 the cache because we already had a v0 descriptor with the same ID.
21075 Bugfix on 0.2.0.18-alpha.
21076 - Fix a race condition when freeing keys shared between main thread
21077 and CPU workers that could result in a memory leak. Bugfix on
21078 0.1.0.1-rc. Fixes bug 889.
21079 - Send a valid END cell back when a client tries to connect to a
21080 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
21081 840. Patch from rovv.
21082 - Check which hops rendezvous stream cells are associated with to
21083 prevent possible guess-the-streamid injection attacks from
21084 intermediate hops. Fixes another case of bug 446. Based on patch
21086 - If a broken client asks a non-exit router to connect somewhere,
21087 do not even do the DNS lookup before rejecting the connection.
21088 Fixes another case of bug 619. Patch from rovv.
21089 - When a relay gets a create cell it can't decrypt (e.g. because it's
21090 using the wrong onion key), we were dropping it and letting the
21091 client time out. Now actually answer with a destroy cell. Fixes
21092 bug 904. Bugfix on 0.0.2pre8.
21094 o Minor bugfixes (hidden services):
21095 - Do not throw away existing introduction points on SIGHUP. Bugfix on
21096 0.0.6pre1. Patch by Karsten. Fixes bug 874.
21099 - Report the case where all signatures in a detached set are rejected
21100 differently than the case where there is an error handling the
21102 - When we realize that another process has modified our cached
21103 descriptors, print out a more useful error message rather than
21104 triggering an assertion. Fixes bug 885. Patch from Karsten.
21105 - Implement the 0x20 hack to better resist DNS poisoning: set the
21106 case on outgoing DNS requests randomly, and reject responses that do
21107 not match the case correctly. This logic can be disabled with the
21108 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
21109 of servers that do not reliably preserve case in replies. See
21110 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
21112 - Check DNS replies for more matching fields to better resist DNS
21114 - Never use OpenSSL compression: it wastes RAM and CPU trying to
21115 compress cells, which are basically all encrypted, compressed, or
21119 Changes in version 0.2.1.11-alpha - 2009-01-20
21120 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
21121 week it will take a long time to bootstrap again" bug. It also fixes
21122 an important security-related bug reported by Ilja van Sprundel. You
21123 should upgrade. (We'll send out more details about the bug once people
21124 have had some time to upgrade.)
21127 - Fix a heap-corruption bug that may be remotely triggerable on
21128 some platforms. Reported by Ilja van Sprundel.
21131 - Discard router descriptors as we load them if they are more than
21132 five days old. Otherwise if Tor is off for a long time and then
21133 starts with cached descriptors, it will try to use the onion
21134 keys in those obsolete descriptors when building circuits. Bugfix
21135 on 0.2.0.x. Fixes bug 887.
21138 - Try to make sure that the version of Libevent we're running with
21139 is binary-compatible with the one we built with. May address bug
21141 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
21142 for bug 905. Bugfix on 0.2.1.7-alpha.
21143 - Add a new --enable-local-appdata configuration switch to change
21144 the default location of the datadir on win32 from APPDATA to
21145 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
21146 entirely. Patch from coderman.
21149 - Make outbound DNS packets respect the OutboundBindAddress setting.
21150 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
21151 - When our circuit fails at the first hop (e.g. we get a destroy
21152 cell back), avoid using that OR connection anymore, and also
21153 tell all the one-hop directory requests waiting for it that they
21154 should fail. Bugfix on 0.2.1.3-alpha.
21155 - In the torify(1) manpage, mention that tsocks will leak your
21159 Changes in version 0.2.1.10-alpha - 2009-01-06
21160 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
21161 would make the bridge relay not so useful if it had DirPort set to 0,
21162 and one that could let an attacker learn a little bit of information
21163 about the bridge's users), and a bug that would cause your Tor relay
21164 to ignore a circuit create request it can't decrypt (rather than reply
21165 with an error). It also fixes a wide variety of other bugs.
21168 - If the cached networkstatus consensus is more than five days old,
21169 discard it rather than trying to use it. In theory it could
21170 be useful because it lists alternate directory mirrors, but in
21171 practice it just means we spend many minutes trying directory
21172 mirrors that are long gone from the network. Helps bug 887 a bit;
21174 - Bridge relays that had DirPort set to 0 would stop fetching
21175 descriptors shortly after startup, and then briefly resume
21176 after a new bandwidth test and/or after publishing a new bridge
21177 descriptor. Bridge users that try to bootstrap from them would
21178 get a recent networkstatus but would get descriptors from up to
21179 18 hours earlier, meaning most of the descriptors were obsolete
21180 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
21181 - Prevent bridge relays from serving their 'extrainfo' document
21182 to anybody who asks, now that extrainfo docs include potentially
21183 sensitive aggregated client geoip summaries. Bugfix on
21187 - New controller event "clients_seen" to report a geoip-based summary
21188 of which countries we've seen clients from recently. Now controllers
21189 like Vidalia can show bridge operators that they're actually making
21191 - Build correctly against versions of OpenSSL 0.9.8 or later built
21192 without support for deprecated functions.
21193 - Update to the "December 19 2008" ip-to-country file.
21195 o Minor bugfixes (on 0.2.0.x):
21196 - Authorities now vote for the Stable flag for any router whose
21197 weighted MTBF is at least 5 days, regardless of the mean MTBF.
21198 - Do not remove routers as too old if we do not have any consensus
21199 document. Bugfix on 0.2.0.7-alpha.
21200 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
21201 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
21202 - When an exit relay resolves a stream address to a local IP address,
21203 do not just keep retrying that same exit relay over and
21204 over. Instead, just close the stream. Addresses bug 872. Bugfix
21205 on 0.2.0.32. Patch from rovv.
21206 - If a hidden service sends us an END cell, do not consider
21207 retrying the connection; just close it. Patch from rovv.
21208 - When we made bridge authorities stop serving bridge descriptors over
21209 unencrypted links, we also broke DirPort reachability testing for
21210 bridges. So bridges with a non-zero DirPort were printing spurious
21211 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
21212 - When a relay gets a create cell it can't decrypt (e.g. because it's
21213 using the wrong onion key), we were dropping it and letting the
21214 client time out. Now actually answer with a destroy cell. Fixes
21215 bug 904. Bugfix on 0.0.2pre8.
21216 - Squeeze 2-5% out of client performance (according to oprofile) by
21217 improving the implementation of some policy-manipulation functions.
21219 o Minor bugfixes (on 0.2.1.x):
21220 - Make get_interface_address() function work properly again; stop
21221 guessing the wrong parts of our address as our address.
21222 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
21223 send on that circuit. Otherwise we might violate the proposal-110
21224 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
21226 - When we're sending non-EXTEND cells to the first hop in a circuit,
21227 for example to use an encrypted directory connection, we don't need
21228 to use RELAY_EARLY cells: the first hop knows what kind of cell
21229 it is, and nobody else can even see the cell type. Conserving
21230 RELAY_EARLY cells makes it easier to cannibalize circuits like
21232 - Stop logging nameserver addresses in reverse order.
21233 - If we are retrying a directory download slowly over and over, do
21234 not automatically give up after the 254th failure. Bugfix on
21236 - Resume reporting accurate "stream end" reasons to the local control
21237 port. They were lost in the changes for Proposal 148. Bugfix on
21240 o Deprecated and removed features:
21241 - The old "tor --version --version" command, which would print out
21242 the subversion "Id" of most of the source files, is now removed. It
21243 turned out to be less useful than we'd expected, and harder to
21246 o Code simplifications and refactoring:
21247 - Change our header file guard macros to be less likely to conflict
21248 with system headers. Adam Langley noticed that we were conflicting
21249 with log.h on Android.
21250 - Tool-assisted documentation cleanup. Nearly every function or
21251 static variable in Tor should have its own documentation now.
21254 Changes in version 0.2.1.9-alpha - 2008-12-25
21255 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
21257 o New directory authorities:
21258 - gabelmoo (the authority run by Karsten Loesing) now has a new
21262 - Never use a connection with a mismatched address to extend a
21263 circuit, unless that connection is canonical. A canonical
21264 connection is one whose address is authenticated by the router's
21265 identity key, either in a NETINFO cell or in a router descriptor.
21266 - Avoid a possible memory corruption bug when receiving hidden service
21267 descriptors. Bugfix on 0.2.1.6-alpha.
21270 - Fix a logic error that would automatically reject all but the first
21271 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
21272 part of bug 813/868. Bug spotted by coderman.
21273 - When a stream at an exit relay is in state "resolving" or
21274 "connecting" and it receives an "end" relay cell, the exit relay
21275 would silently ignore the end cell and not close the stream. If
21276 the client never closes the circuit, then the exit relay never
21277 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
21278 reported by "wood".
21279 - When we can't initialize DNS because the network is down, do not
21280 automatically stop Tor from starting. Instead, retry failed
21281 dns_init() every 10 minutes, and change the exit policy to reject
21282 *:* until one succeeds. Fixes bug 691.
21285 - Give a better error message when an overzealous init script says
21286 "sudo -u username tor --user username". Makes Bug 882 easier for
21288 - When a directory authority gives us a new guess for our IP address,
21289 log which authority we used. Hopefully this will help us debug
21290 the recent complaints about bad IP address guesses.
21291 - Detect svn revision properly when we're using git-svn.
21292 - Try not to open more than one descriptor-downloading connection
21293 to an authority at once. This should reduce load on directory
21294 authorities. Fixes bug 366.
21295 - Add cross-certification to newly generated certificates, so that
21296 a signing key is enough information to look up a certificate.
21297 Partial implementation of proposal 157.
21298 - Start serving certificates by <identity digest, signing key digest>
21299 pairs. Partial implementation of proposal 157.
21300 - Clients now never report any stream end reason except 'MISC'.
21301 Implements proposal 148.
21302 - On platforms with a maximum syslog string length, truncate syslog
21303 messages to that length ourselves, rather than relying on the
21304 system to do it for us.
21305 - Optimize out calls to time(NULL) that occur for every IO operation,
21306 or for every cell. On systems where time() is a slow syscall,
21307 this fix will be slightly helpful.
21308 - Exit servers can now answer resolve requests for ip6.arpa addresses.
21309 - When we download a descriptor that we then immediately (as
21310 a directory authority) reject, do not retry downloading it right
21311 away. Should save some bandwidth on authorities. Fix for bug
21312 888. Patch by Sebastian Hahn.
21313 - When a download gets us zero good descriptors, do not notify
21314 Tor that new directory information has arrived.
21315 - Avoid some nasty corner cases in the logic for marking connections
21316 as too old or obsolete or noncanonical for circuits. Partial
21319 o Minor features (controller):
21320 - New CONSENSUS_ARRIVED event to note when a new consensus has
21321 been fetched and validated.
21322 - When we realize that another process has modified our cached
21323 descriptors file, print out a more useful error message rather
21324 than triggering an assertion. Fixes bug 885. Patch from Karsten.
21325 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
21326 controllers to prevent SIGHUP from reloading the
21327 configuration. Fixes bug 856.
21330 - Resume using the correct "REASON=" stream when telling the
21331 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
21332 - When a canonical connection appears later in our internal list
21333 than a noncanonical one for a given OR ID, always use the
21334 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
21336 - Clip the MaxCircuitDirtiness config option to a minimum of 10
21337 seconds. Warn the user if lower values are given in the
21338 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
21339 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
21340 user if lower values are given in the configuration. Bugfix on
21341 0.1.1.17-rc. Patch by Sebastian.
21342 - Fix a race condition when freeing keys shared between main thread
21343 and CPU workers that could result in a memory leak. Bugfix on
21344 0.1.0.1-rc. Fixes bug 889.
21346 o Minor bugfixes (hidden services):
21347 - Do not throw away existing introduction points on SIGHUP (bugfix on
21348 0.0.6pre1); also, do not stall hidden services because we're
21349 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
21350 by John Brooks. Patch by Karsten. Fixes bug 874.
21351 - Fix a memory leak when we decline to add a v2 rendezvous
21352 descriptor to the cache because we already had a v0 descriptor
21353 with the same ID. Bugfix on 0.2.0.18-alpha.
21355 o Deprecated and removed features:
21356 - RedirectExits has been removed. It was deprecated since
21358 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
21359 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
21360 - Cell pools are now always enabled; --disable-cell-pools is ignored.
21362 o Code simplifications and refactoring:
21363 - Rename the confusing or_is_obsolete field to the more appropriate
21364 is_bad_for_new_circs, and move it to or_connection_t where it
21366 - Move edge-only flags from connection_t to edge_connection_t: not
21367 only is this better coding, but on machines of plausible alignment,
21368 it should save 4-8 bytes per connection_t. "Every little bit helps."
21369 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
21370 for consistency; keep old option working for backward compatibility.
21371 - Simplify the code for finding connections to use for a circuit.
21374 Changes in version 0.2.1.8-alpha - 2008-12-08
21375 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
21376 builds better on unusual platforms like Solaris and old OS X, and
21377 fixes a variety of other issues.
21380 - New DirPortFrontPage option that takes an html file and publishes
21381 it as "/" on the DirPort. Now relay operators can provide a
21382 disclaimer without needing to set up a separate webserver. There's
21383 a sample disclaimer in contrib/tor-exit-notice.html.
21386 - When the client is choosing entry guards, now it selects at most
21387 one guard from a given relay family. Otherwise we could end up with
21388 all of our entry points into the network run by the same operator.
21389 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
21392 - Fix a DOS opportunity during the voting signature collection process
21393 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
21394 - Fix a possible segfault when establishing an exit connection. Bugfix
21398 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
21400 - Made Tor a little less aggressive about deleting expired
21401 certificates. Partial fix for bug 854.
21402 - Stop doing unaligned memory access that generated bus errors on
21403 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
21404 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
21405 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
21406 - Make USR2 log-level switch take effect immediately. Bugfix on
21408 - If one win32 nameserver fails to get added, continue adding the
21409 rest, and don't automatically fail.
21410 - Use fcntl() for locking when flock() is not available. Should fix
21411 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
21412 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
21413 could make gcc generate non-functional binary search code. Bugfix
21415 - Build correctly on platforms without socklen_t.
21416 - Avoid potential crash on internal error during signature collection.
21417 Fixes bug 864. Patch from rovv.
21418 - Do not use C's stdio library for writing to log files. This will
21419 improve logging performance by a minute amount, and will stop
21420 leaking fds when our disk is full. Fixes bug 861.
21421 - Stop erroneous use of O_APPEND in cases where we did not in fact
21422 want to re-seek to the end of a file before every last write().
21423 - Correct handling of possible malformed authority signing key
21424 certificates with internal signature types. Fixes bug 880. Bugfix
21426 - Fix a hard-to-trigger resource leak when logging credential status.
21430 - Directory mirrors no longer fetch the v1 directory or
21431 running-routers files. They are obsolete, and nobody asks for them
21432 anymore. This is the first step to making v1 authorities obsolete.
21434 o Minor features (controller):
21435 - Return circuit purposes in response to GETINFO circuit-status. Fixes
21439 Changes in version 0.2.0.32 - 2008-11-20
21440 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
21441 packages (and maybe other packages) noticed by Theo de Raadt, fixes
21442 a smaller security flaw that might allow an attacker to access local
21443 services, further improves hidden service performance, and fixes a
21444 variety of other issues.
21447 - The "User" and "Group" config options did not clear the
21448 supplementary group entries for the Tor process. The "User" option
21449 is now more robust, and we now set the groups to the specified
21450 user's primary group. The "Group" option is now ignored. For more
21451 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
21452 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
21453 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
21454 - The "ClientDNSRejectInternalAddresses" config option wasn't being
21455 consistently obeyed: if an exit relay refuses a stream because its
21456 exit policy doesn't allow it, we would remember what IP address
21457 the relay said the destination address resolves to, even if it's
21458 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
21461 - Fix a DOS opportunity during the voting signature collection process
21462 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
21464 o Major bugfixes (hidden services):
21465 - When fetching v0 and v2 rendezvous service descriptors in parallel,
21466 we were failing the whole hidden service request when the v0
21467 descriptor fetch fails, even if the v2 fetch is still pending and
21468 might succeed. Similarly, if the last v2 fetch fails, we were
21469 failing the whole hidden service request even if a v0 fetch is
21470 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
21471 - When extending a circuit to a hidden service directory to upload a
21472 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
21473 requests failed, because the router descriptor has not been
21474 downloaded yet. In these cases, do not attempt to upload the
21475 rendezvous descriptor, but wait until the router descriptor is
21476 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
21477 descriptor from a hidden service directory for which the router
21478 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
21482 - Fix several infrequent memory leaks spotted by Coverity.
21483 - When testing for libevent functions, set the LDFLAGS variable
21484 correctly. Found by Riastradh.
21485 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
21486 bootstrapping with tunneled directory connections. Bugfix on
21487 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
21488 - When asked to connect to A.B.exit:80, if we don't know the IP for A
21489 and we know that server B rejects most-but-not all connections to
21490 port 80, we would previously reject the connection. Now, we assume
21491 the user knows what they were asking for. Fixes bug 752. Bugfix
21492 on 0.0.9rc5. Diagnosed by BarkerJr.
21493 - If we overrun our per-second write limits a little, count this as
21494 having used up our write allocation for the second, and choke
21495 outgoing directory writes. Previously, we had only counted this when
21496 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
21497 Bugfix on 0.2.0.x (??).
21498 - Remove the old v2 directory authority 'lefkada' from the default
21499 list. It has been gone for many months.
21500 - Stop doing unaligned memory access that generated bus errors on
21501 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
21502 - Make USR2 log-level switch take effect immediately. Bugfix on
21505 o Minor bugfixes (controller):
21506 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
21507 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
21510 Changes in version 0.2.1.7-alpha - 2008-11-08
21511 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
21512 packages (and maybe other packages) noticed by Theo de Raadt, fixes
21513 a smaller security flaw that might allow an attacker to access local
21514 services, adds better defense against DNS poisoning attacks on exit
21515 relays, further improves hidden service performance, and fixes a
21516 variety of other issues.
21519 - The "ClientDNSRejectInternalAddresses" config option wasn't being
21520 consistently obeyed: if an exit relay refuses a stream because its
21521 exit policy doesn't allow it, we would remember what IP address
21522 the relay said the destination address resolves to, even if it's
21523 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
21524 - The "User" and "Group" config options did not clear the
21525 supplementary group entries for the Tor process. The "User" option
21526 is now more robust, and we now set the groups to the specified
21527 user's primary group. The "Group" option is now ignored. For more
21528 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
21529 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
21530 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
21531 - Do not use or believe expired v3 authority certificates. Patch
21532 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
21535 - Now NodeFamily and MyFamily config options allow spaces in
21536 identity fingerprints, so it's easier to paste them in.
21537 Suggested by Lucky Green.
21538 - Implement the 0x20 hack to better resist DNS poisoning: set the
21539 case on outgoing DNS requests randomly, and reject responses that do
21540 not match the case correctly. This logic can be disabled with the
21541 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
21542 of servers that do not reliably preserve case in replies. See
21543 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
21545 - Preserve case in replies to DNSPort requests in order to support
21546 the 0x20 hack for resisting DNS poisoning attacks.
21548 o Hidden service performance improvements:
21549 - When the client launches an introduction circuit, retry with a
21550 new circuit after 30 seconds rather than 60 seconds.
21551 - Launch a second client-side introduction circuit in parallel
21552 after a delay of 15 seconds (based on work by Christian Wilms).
21553 - Hidden services start out building five intro circuits rather
21554 than three, and when the first three finish they publish a service
21555 descriptor using those. Now we publish our service descriptor much
21556 faster after restart.
21559 - Minor fix in the warning messages when you're having problems
21560 bootstrapping; also, be more forgiving of bootstrap problems when
21561 we're still making incremental progress on a given bootstrap phase.
21562 - When we're choosing an exit node for a circuit, and we have
21563 no pending streams, choose a good general exit rather than one that
21564 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
21565 - Send a valid END cell back when a client tries to connect to a
21566 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
21567 840. Patch from rovv.
21568 - If a broken client asks a non-exit router to connect somewhere,
21569 do not even do the DNS lookup before rejecting the connection.
21570 Fixes another case of bug 619. Patch from rovv.
21571 - Fix another case of assuming, when a specific exit is requested,
21572 that we know more than the user about what hosts it allows.
21573 Fixes another case of bug 752. Patch from rovv.
21574 - Check which hops rendezvous stream cells are associated with to
21575 prevent possible guess-the-streamid injection attacks from
21576 intermediate hops. Fixes another case of bug 446. Based on patch
21578 - Avoid using a negative right-shift when comparing 32-bit
21579 addresses. Possible fix for bug 845 and bug 811.
21580 - Make the assert_circuit_ok() function work correctly on circuits that
21581 have already been marked for close.
21582 - Fix read-off-the-end-of-string error in unit tests when decoding
21583 introduction points.
21584 - Fix uninitialized size field for memory area allocation: may improve
21585 memory performance during directory parsing.
21586 - Treat duplicate certificate fetches as failures, so that we do
21587 not try to re-fetch an expired certificate over and over and over.
21588 - Do not say we're fetching a certificate when we'll in fact skip it
21589 because of a pending download.
21592 Changes in version 0.2.1.6-alpha - 2008-09-30
21593 Tor 0.2.1.6-alpha further improves performance and robustness of
21594 hidden services, starts work on supporting per-country relay selection,
21595 and fixes a variety of smaller issues.
21598 - Implement proposal 121: make it possible to build hidden services
21599 that only certain clients are allowed to connect to. This is
21600 enforced at several points, so that unauthorized clients are unable
21601 to send INTRODUCE cells to the service, or even (depending on the
21602 type of authentication) to learn introduction points. This feature
21603 raises the bar for certain kinds of active attacks against hidden
21604 services. Code by Karsten Loesing.
21605 - Relays now store and serve v2 hidden service descriptors by default,
21606 i.e., the new default value for HidServDirectoryV2 is 1. This is
21607 the last step in proposal 114, which aims to make hidden service
21608 lookups more reliable.
21609 - Start work to allow node restrictions to include country codes. The
21610 syntax to exclude nodes in a country with country code XX is
21611 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
21612 refinement to decide what config options should take priority if
21613 you ask to both use a particular node and exclude it.
21614 - Allow ExitNodes list to include IP ranges and country codes, just
21615 like the Exclude*Nodes lists. Patch from Robert Hogan.
21618 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
21619 Tor to fail to start if you had it configured to use a bridge
21620 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
21621 - When extending a circuit to a hidden service directory to upload a
21622 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
21623 requests failed, because the router descriptor had not been
21624 downloaded yet. In these cases, we now wait until the router
21625 descriptor is downloaded, and then retry. Likewise, clients
21626 now skip over a hidden service directory if they don't yet have
21627 its router descriptor, rather than futilely requesting it and
21628 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
21630 - When fetching v0 and v2 rendezvous service descriptors in parallel,
21631 we were failing the whole hidden service request when the v0
21632 descriptor fetch fails, even if the v2 fetch is still pending and
21633 might succeed. Similarly, if the last v2 fetch fails, we were
21634 failing the whole hidden service request even if a v0 fetch is
21635 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
21636 - DNS replies need to have names matching their requests, but
21637 these names should be in the questions section, not necessarily
21638 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
21641 - Update to the "September 1 2008" ip-to-country file.
21642 - Allow ports 465 and 587 in the default exit policy again. We had
21643 rejected them in 0.1.0.15, because back in 2005 they were commonly
21644 misconfigured and ended up as spam targets. We hear they are better
21645 locked down these days.
21646 - Use a lockfile to make sure that two Tor processes are not
21647 simultaneously running with the same datadir.
21648 - Serve the latest v3 networkstatus consensus via the control
21649 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
21650 - Better logging about stability/reliability calculations on directory
21652 - Drop the requirement to have an open dir port for storing and
21653 serving v2 hidden service descriptors.
21654 - Directory authorities now serve a /tor/dbg-stability.txt URL to
21655 help debug WFU and MTBF calculations.
21656 - Implement most of Proposal 152: allow specialized servers to permit
21657 single-hop circuits, and clients to use those servers to build
21658 single-hop circuits when using a specialized controller. Patch
21659 from Josh Albrecht. Resolves feature request 768.
21660 - Add a -p option to tor-resolve for specifying the SOCKS port: some
21661 people find host:port too confusing.
21662 - Make TrackHostExit mappings expire a while after their last use, not
21663 after their creation. Patch from Robert Hogan.
21664 - Provide circuit purposes along with circuit events to the controller.
21667 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
21669 - Fixed some memory leaks -- some quite frequent, some almost
21670 impossible to trigger -- based on results from Coverity.
21671 - When testing for libevent functions, set the LDFLAGS variable
21672 correctly. Found by Riastradh.
21673 - Fix an assertion bug in parsing policy-related options; possible fix
21675 - Catch and report a few more bootstrapping failure cases when Tor
21676 fails to establish a TCP connection. Cleanup on 0.2.1.x.
21677 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
21678 bootstrapping with tunneled directory connections. Bugfix on
21679 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
21680 - When asked to connect to A.B.exit:80, if we don't know the IP for A
21681 and we know that server B rejects most-but-not all connections to
21682 port 80, we would previously reject the connection. Now, we assume
21683 the user knows what they were asking for. Fixes bug 752. Bugfix
21684 on 0.0.9rc5. Diagnosed by BarkerJr.
21685 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
21686 service directories if they have no advertised dir port. Bugfix
21688 - If we overrun our per-second write limits a little, count this as
21689 having used up our write allocation for the second, and choke
21690 outgoing directory writes. Previously, we had only counted this when
21691 we had met our limits precisely. Fixes bug 824. Patch by rovv.
21692 Bugfix on 0.2.0.x (??).
21693 - Avoid a "0 divided by 0" calculation when calculating router uptime
21694 at directory authorities. Bugfix on 0.2.0.8-alpha.
21695 - Make DNS resolved controller events into "CLOSED", not
21696 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
21698 - Fix a bug where an unreachable relay would establish enough
21699 reachability testing circuits to do a bandwidth test -- if
21700 we already have a connection to the middle hop of the testing
21701 circuit, then it could establish the last hop by using the existing
21702 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
21703 circuits no longer use entry guards in 0.2.1.3-alpha.
21704 - If we have correct permissions on $datadir, we complain to stdout
21705 and fail to start. But dangerous permissions on
21706 $datadir/cached-status/ would cause us to open a log and complain
21707 there. Now complain to stdout and fail to start in both cases. Fixes
21708 bug 820, reported by seeess.
21709 - Remove the old v2 directory authority 'lefkada' from the default
21710 list. It has been gone for many months.
21712 o Code simplifications and refactoring:
21713 - Revise the connection_new functions so that a more typesafe variant
21714 exists. This will work better with Coverity, and let us find any
21715 actual mistakes we're making here.
21716 - Refactor unit testing logic so that dmalloc can be used sensibly
21717 with unit tests to check for memory leaks.
21718 - Move all hidden-service related fields from connection and circuit
21719 structure to substructures: this way they won't eat so much memory.
21722 Changes in version 0.2.0.31 - 2008-09-03
21723 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
21724 a big bug we're seeing where in rare cases traffic from one Tor stream
21725 gets mixed into another stream, and fixes a variety of smaller issues.
21728 - Make sure that two circuits can never exist on the same connection
21729 with the same circuit ID, even if one is marked for close. This
21730 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
21731 - Relays now reject risky extend cells: if the extend cell includes
21732 a digest of all zeroes, or asks to extend back to the relay that
21733 sent the extend cell, tear down the circuit. Ideas suggested
21735 - If not enough of our entry guards are available so we add a new
21736 one, we might use the new one even if it overlapped with the
21737 current circuit's exit relay (or its family). Anonymity bugfix
21738 pointed out by rovv.
21741 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
21742 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
21743 - Correctly detect the presence of the linux/netfilter_ipv4.h header
21744 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
21745 - Pick size of default geoip filename string correctly on windows.
21746 Fixes bug 806. Bugfix on 0.2.0.30.
21747 - Make the autoconf script accept the obsolete --with-ssl-dir
21748 option as an alias for the actually-working --with-openssl-dir
21749 option. Fix the help documentation to recommend --with-openssl-dir.
21750 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
21751 - When using the TransPort option on OpenBSD, and using the User
21752 option to change UID and drop privileges, make sure to open
21753 /dev/pf before dropping privileges. Fixes bug 782. Patch from
21754 Christopher Davis. Bugfix on 0.1.2.1-alpha.
21755 - Try to attach connections immediately upon receiving a RENDEZVOUS2
21756 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
21757 on the client side when connecting to a hidden service. Bugfix
21758 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
21759 - When closing an application-side connection because its circuit is
21760 getting torn down, generate the stream event correctly. Bugfix on
21761 0.1.2.x. Anonymous patch.
21764 Changes in version 0.2.1.5-alpha - 2008-08-31
21765 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
21766 in a lot of the infrastructure for adding authorization to hidden
21767 services, lays the groundwork for having clients read their load
21768 balancing information out of the networkstatus consensus rather than
21769 the individual router descriptors, addresses two potential anonymity
21770 issues, and fixes a variety of smaller issues.
21773 - Convert many internal address representations to optionally hold
21775 - Generate and accept IPv6 addresses in many protocol elements.
21776 - Make resolver code handle nameservers located at ipv6 addresses.
21777 - Begin implementation of proposal 121 ("Client authorization for
21778 hidden services"): configure hidden services with client
21779 authorization, publish descriptors for them, and configure
21780 authorization data for hidden services at clients. The next
21781 step is to actually access hidden services that perform client
21783 - More progress toward proposal 141: Network status consensus
21784 documents and votes now contain bandwidth information for each
21785 router and a summary of that router's exit policy. Eventually this
21786 will be used by clients so that they do not have to download every
21787 known descriptor before building circuits.
21789 o Major bugfixes (on 0.2.0.x and before):
21790 - When sending CREATED cells back for a given circuit, use a 64-bit
21791 connection ID to find the right connection, rather than an addr:port
21792 combination. Now that we can have multiple OR connections between
21793 the same ORs, it is no longer possible to use addr:port to uniquely
21794 identify a connection.
21795 - Relays now reject risky extend cells: if the extend cell includes
21796 a digest of all zeroes, or asks to extend back to the relay that
21797 sent the extend cell, tear down the circuit. Ideas suggested
21799 - If not enough of our entry guards are available so we add a new
21800 one, we might use the new one even if it overlapped with the
21801 current circuit's exit relay (or its family). Anonymity bugfix
21802 pointed out by rovv.
21805 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
21806 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
21807 - When using the TransPort option on OpenBSD, and using the User
21808 option to change UID and drop privileges, make sure to open /dev/pf
21809 before dropping privileges. Fixes bug 782. Patch from Christopher
21810 Davis. Bugfix on 0.1.2.1-alpha.
21811 - Correctly detect the presence of the linux/netfilter_ipv4.h header
21812 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
21813 - Add a missing safe_str() call for a debug log message.
21814 - Use 64 bits instead of 32 bits for connection identifiers used with
21815 the controller protocol, to greatly reduce risk of identifier reuse.
21816 - Make the autoconf script accept the obsolete --with-ssl-dir
21817 option as an alias for the actually-working --with-openssl-dir
21818 option. Fix the help documentation to recommend --with-openssl-dir.
21819 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
21822 - Rate-limit too-many-sockets messages: when they happen, they happen
21823 a lot. Resolves bug 748.
21824 - Resist DNS poisoning a little better by making sure that names in
21825 answer sections match.
21826 - Print the SOCKS5 error message string as well as the error code
21827 when a tor-resolve request fails. Patch from Jacob.
21830 Changes in version 0.2.1.4-alpha - 2008-08-04
21831 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
21834 - The address part of exit policies was not correctly written
21835 to router descriptors. This generated router descriptors that failed
21836 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
21838 - Tor triggered a false assert when extending a circuit to a relay
21839 but we already have a connection open to that relay. Noticed by
21840 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
21843 - Fix a hidden service logging bug: in some edge cases, the router
21844 descriptor of a previously picked introduction point becomes
21845 obsolete and we need to give up on it rather than continually
21846 complaining that it has become obsolete. Observed by xiando. Bugfix
21849 o Removed features:
21850 - Take out the TestVia config option, since it was a workaround for
21851 a bug that was fixed in Tor 0.1.1.21.
21854 Changes in version 0.2.1.3-alpha - 2008-08-03
21855 Tor 0.2.1.3-alpha implements most of the pieces to prevent
21856 infinite-length circuit attacks (see proposal 110); fixes a bug that
21857 might cause exit relays to corrupt streams they send back; allows
21858 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
21859 ExcludeExitNodes config options; and fixes a big pile of bugs.
21861 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
21862 - Send a bootstrap problem "warn" event on the first problem if the
21863 reason is NO_ROUTE (that is, our network is down).
21866 - Implement most of proposal 110: The first K cells to be sent
21867 along a circuit are marked as special "early" cells; only K "early"
21868 cells will be allowed. Once this code is universal, we can block
21869 certain kinds of DOS attack by requiring that EXTEND commands must
21870 be sent using an "early" cell.
21873 - Try to attach connections immediately upon receiving a RENDEZVOUS2
21874 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
21875 on the client side when connecting to a hidden service. Bugfix
21876 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
21877 - Ensure that two circuits can never exist on the same connection
21878 with the same circuit ID, even if one is marked for close. This
21879 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
21882 - When relays do their initial bandwidth measurement, don't limit
21883 to just our entry guards for the test circuits. Otherwise we tend
21884 to have multiple test circuits going through a single entry guard,
21885 which makes our bandwidth test less accurate. Fixes part of bug 654;
21886 patch contributed by Josh Albrecht.
21887 - Add an ExcludeExitNodes option so users can list a set of nodes
21888 that should be be excluded from the exit node position, but
21889 allowed elsewhere. Implements proposal 151.
21890 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
21891 ExcludeNodes and ExcludeExitNodes lists.
21892 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
21893 be more efficient. Formerly it was quadratic in the number of
21894 servers; now it should be linear. Fixes bug 509.
21895 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
21896 and n_conn_id_digest fields into a separate structure that's
21897 only needed when the circuit has not yet attached to an n_conn.
21900 - Change the contrib/tor.logrotate script so it makes the new
21901 logs as "_tor:_tor" rather than the default, which is generally
21902 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
21903 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
21904 warnings (occasionally), but it can also cause the compiler to
21905 eliminate error-checking code. Suggested by Peter Gutmann.
21906 - When a hidden service is giving up on an introduction point candidate
21907 that was not included in the last published rendezvous descriptor,
21908 don't reschedule publication of the next descriptor. Fixes bug 763.
21910 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
21911 HiddenServiceExcludeNodes as obsolete: they never worked properly,
21912 and nobody claims to be using them. Fixes bug 754. Bugfix on
21913 0.1.0.1-rc. Patch from Christian Wilms.
21914 - Fix a small alignment and memory-wasting bug on buffer chunks.
21917 o Minor bugfixes (controller):
21918 - When closing an application-side connection because its circuit
21919 is getting torn down, generate the stream event correctly.
21920 Bugfix on 0.1.2.x. Anonymous patch.
21922 o Removed features:
21923 - Remove all backward-compatibility code to support relays running
21924 versions of Tor so old that they no longer work at all on the
21928 Changes in version 0.2.0.30 - 2008-07-15
21930 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
21931 warnings (occasionally), but it can also cause the compiler to
21932 eliminate error-checking code. Suggested by Peter Gutmann.
21935 Changes in version 0.2.0.29-rc - 2008-07-08
21936 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
21937 hidden-service performance bugs, and fixes a bunch of smaller bugs.
21940 - If you have more than one bridge but don't know their keys,
21941 you would only launch a request for the descriptor of the first one
21942 on your list. (Tor considered launching requests for the others, but
21943 found that it already had a connection on the way for $0000...0000
21944 so it didn't open another.) Bugfix on 0.2.0.x.
21945 - If you have more than one bridge but don't know their keys, and the
21946 connection to one of the bridges failed, you would cancel all
21947 pending bridge connections. (After all, they all have the same
21948 digest.) Bugfix on 0.2.0.x.
21949 - When a hidden service was trying to establish an introduction point,
21950 and Tor had built circuits preemptively for such purposes, we
21951 were ignoring all the preemptive circuits and launching a new one
21952 instead. Bugfix on 0.2.0.14-alpha.
21953 - When a hidden service was trying to establish an introduction point,
21954 and Tor *did* manage to reuse one of the preemptively built
21955 circuits, it didn't correctly remember which one it used,
21956 so it asked for another one soon after, until there were no
21957 more preemptive circuits, at which point it launched one from
21958 scratch. Bugfix on 0.0.9.x.
21959 - Make directory servers include the X-Your-Address-Is: http header in
21960 their responses even for begin_dir conns. Now clients who only
21961 ever use begin_dir connections still have a way to learn their IP
21962 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
21965 - Fix a macro/CPP interaction that was confusing some compilers:
21966 some GCCs don't like #if/#endif pairs inside macro arguments.
21968 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
21969 Fixes bug 704; fix from Steven Murdoch.
21970 - When opening /dev/null in finish_daemonize(), do not pass the
21971 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
21972 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
21973 - Correctly detect transparent proxy support on Linux hosts that
21974 require in.h to be included before netfilter_ipv4.h. Patch
21976 - Disallow session resumption attempts during the renegotiation
21977 stage of the v2 handshake protocol. Clients should never be trying
21978 session resumption at this point, but apparently some did, in
21979 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
21980 found by Geoff Goodell.
21983 Changes in version 0.2.1.2-alpha - 2008-06-20
21984 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
21985 make it easier to set up your own private Tor network; fixes several
21986 big bugs with using more than one bridge relay; fixes a big bug with
21987 offering hidden services quickly after Tor starts; and uses a better
21988 API for reporting potential bootstrapping problems to the controller.
21991 - New TestingTorNetwork config option to allow adjustment of
21992 previously constant values that, while reasonable, could slow
21993 bootstrapping. Implements proposal 135. Patch from Karsten.
21996 - If you have more than one bridge but don't know their digests,
21997 you would only learn a request for the descriptor of the first one
21998 on your list. (Tor considered launching requests for the others, but
21999 found that it already had a connection on the way for $0000...0000
22000 so it didn't open another.) Bugfix on 0.2.0.x.
22001 - If you have more than one bridge but don't know their digests,
22002 and the connection to one of the bridges failed, you would cancel
22003 all pending bridge connections. (After all, they all have the
22004 same digest.) Bugfix on 0.2.0.x.
22005 - When establishing a hidden service, introduction points that
22006 originate from cannibalized circuits are completely ignored and not
22007 included in rendezvous service descriptors. This might be another
22008 reason for delay in making a hidden service available. Bugfix
22009 from long ago (0.0.9.x?)
22012 - Allow OpenSSL to use dynamic locks if it wants.
22013 - When building a consensus, do not include routers that are down.
22014 This will cut down 30% to 40% on consensus size. Implements
22016 - In directory authorities' approved-routers files, allow
22017 fingerprints with or without space.
22018 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
22019 controller can query our current bootstrap state in case it attaches
22020 partway through and wants to catch up.
22021 - Send an initial "Starting" bootstrap status event, so we have a
22022 state to start out in.
22025 - Asking for a conditional consensus at .../consensus/<fingerprints>
22026 would crash a dirserver if it did not already have a
22027 consensus. Bugfix on 0.2.1.1-alpha.
22028 - Clean up some macro/CPP interactions: some GCC versions don't like
22029 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
22032 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
22033 - Directory authorities shouldn't complain about bootstrapping
22034 problems just because they do a lot of reachability testing and
22035 some of the connection attempts fail.
22036 - Start sending "count" and "recommendation" key/value pairs in
22037 bootstrap problem status events, so the controller can hear about
22038 problems even before Tor decides they're worth reporting for sure.
22039 - If you're using bridges, generate "bootstrap problem" warnings
22040 as soon as you run out of working bridges, rather than waiting
22041 for ten failures -- which will never happen if you have less than
22043 - If we close our OR connection because there's been a circuit
22044 pending on it for too long, we were telling our bootstrap status
22045 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
22048 Changes in version 0.2.1.1-alpha - 2008-06-13
22049 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
22050 were making the Tor process bloat especially on Linux; makes our TLS
22051 handshake blend in better; sends "bootstrap phase" status events to
22052 the controller, so it can keep the user informed of progress (and
22053 problems) fetching directory information and establishing circuits;
22054 and adds a variety of smaller features.
22057 - More work on making our TLS handshake blend in: modify the list
22058 of ciphers advertised by OpenSSL in client mode to even more
22059 closely resemble a common web browser. We cheat a little so that
22060 we can advertise ciphers that the locally installed OpenSSL doesn't
22062 - Start sending "bootstrap phase" status events to the controller,
22063 so it can keep the user informed of progress fetching directory
22064 information and establishing circuits. Also inform the controller
22065 if we think we're stuck at a particular bootstrap phase. Implements
22067 - Resume using OpenSSL's RAND_poll() for better (and more portable)
22068 cross-platform entropy collection again. We used to use it, then
22069 stopped using it because of a bug that could crash systems that
22070 called RAND_poll when they had a lot of fds open. It looks like the
22071 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
22072 at startup, and to call RAND_poll() when we reseed later only if
22073 we have a non-buggy OpenSSL version.
22076 - When we choose to abandon a new entry guard because we think our
22077 older ones might be better, close any circuits pending on that
22078 new entry guard connection. This fix should make us recover much
22079 faster when our network is down and then comes back. Bugfix on
22080 0.1.2.8-beta; found by lodger.
22082 o Memory fixes and improvements:
22083 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
22084 to avoid unused RAM in buffer chunks and memory pools.
22085 - Speed up parsing and cut down on memory fragmentation by using
22086 stack-style allocations for parsing directory objects. Previously,
22087 this accounted for over 40% of allocations from within Tor's code
22088 on a typical directory cache.
22089 - Use a Bloom filter rather than a digest-based set to track which
22090 descriptors we need to keep around when we're cleaning out old
22091 router descriptors. This speeds up the computation significantly,
22092 and may reduce fragmentation.
22093 - Reduce the default smartlist size from 32 to 16; it turns out that
22094 most smartlists hold around 8-12 elements tops.
22095 - Make dumpstats() log the fullness and size of openssl-internal
22097 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
22098 patch to their OpenSSL, turn it on to save memory on servers. This
22099 patch will (with any luck) get included in a mainline distribution
22101 - Never use OpenSSL compression: it wastes RAM and CPU trying to
22102 compress cells, which are basically all encrypted, compressed,
22106 - Stop reloading the router list from disk for no reason when we
22107 run out of reachable directory mirrors. Once upon a time reloading
22108 it would set the 'is_running' flag back to 1 for them. It hasn't
22109 done that for a long time.
22110 - In very rare situations new hidden service descriptors were
22111 published earlier than 30 seconds after the last change to the
22112 service. (We currently think that a hidden service descriptor
22113 that's been stable for 30 seconds is worth publishing.)
22116 - Allow separate log levels to be configured for different logging
22117 domains. For example, this allows one to log all notices, warnings,
22118 or errors, plus all memory management messages of level debug or
22119 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
22120 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
22121 and stop using a warning that had become unfixably verbose under
22123 - New --hush command-line option similar to --quiet. While --quiet
22124 disables all logging to the console on startup, --hush limits the
22125 output to messages of warning and error severity.
22126 - Servers support a new URL scheme for consensus downloads that
22127 allows the client to specify which authorities are trusted.
22128 The server then only sends the consensus if the client will trust
22129 it. Otherwise a 404 error is sent back. Clients use this
22130 new scheme when the server supports it (meaning it's running
22131 0.2.1.1-alpha or later). Implements proposal 134.
22132 - New configure/torrc options (--enable-geoip-stats,
22133 DirRecordUsageByCountry) to record how many IPs we've served
22134 directory info to in each country code, how many status documents
22135 total we've sent to each country code, and what share of the total
22136 directory requests we should expect to see.
22137 - Use the TLS1 hostname extension to more closely resemble browser
22139 - Lots of new unit tests.
22140 - Add a macro to implement the common pattern of iterating through
22141 two parallel lists in lockstep.
22144 Changes in version 0.2.0.28-rc - 2008-06-13
22145 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
22146 performance bug, and fixes a bunch of smaller bugs.
22149 - Fix a bug where, when we were choosing the 'end stream reason' to
22150 put in our relay end cell that we send to the exit relay, Tor
22151 clients on Windows were sometimes sending the wrong 'reason'. The
22152 anonymity problem is that exit relays may be able to guess whether
22153 the client is running Windows, thus helping partition the anonymity
22154 set. Down the road we should stop sending reasons to exit relays,
22155 or otherwise prevent future versions of this bug.
22158 - While setting up a hidden service, some valid introduction circuits
22159 were overlooked and abandoned. This might be the reason for
22160 the long delay in making a hidden service available. Bugfix on
22164 - Update to the "June 9 2008" ip-to-country file.
22165 - Run 'make test' as part of 'make dist', so we stop releasing so
22166 many development snapshots that fail their unit tests.
22169 - When we're checking if we have enough dir info for each relay
22170 to begin establishing circuits, make sure that we actually have
22171 the descriptor listed in the consensus, not just any descriptor.
22173 - Bridge relays no longer print "xx=0" in their extrainfo document
22174 for every single country code in the geoip db. Bugfix on
22176 - Only warn when we fail to load the geoip file if we were planning to
22177 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
22178 - If we change our MaxAdvertisedBandwidth and then reload torrc,
22179 Tor won't realize it should publish a new relay descriptor. Fixes
22180 bug 688, reported by mfr. Bugfix on 0.1.2.x.
22181 - When we haven't had any application requests lately, don't bother
22182 logging that we have expired a bunch of descriptors. Bugfix
22184 - Make relay cells written on a connection count as non-padding when
22185 tracking how long a connection has been in use. Bugfix on
22186 0.2.0.1-alpha. Spotted by lodger.
22187 - Fix unit tests in 0.2.0.27-rc.
22188 - Fix compile on Windows.
22191 Changes in version 0.2.0.27-rc - 2008-06-03
22192 Tor 0.2.0.27-rc adds a few features we left out of the earlier
22193 release candidates. In particular, we now include an IP-to-country
22194 GeoIP database, so controllers can easily look up what country a
22195 given relay is in, and so bridge relays can give us some sanitized
22196 summaries about which countries are making use of bridges. (See proposal
22197 126-geoip-fetching.txt for details.)
22200 - Include an IP-to-country GeoIP file in the tarball, so bridge
22201 relays can report sanitized summaries of the usage they're seeing.
22204 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
22205 Robert Hogan. Fixes the first part of bug 681.
22206 - Make bridge authorities never serve extrainfo docs.
22207 - Add support to detect Libevent versions in the 1.4.x series
22209 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
22210 - Include a new contrib/tor-exit-notice.html file that exit relay
22211 operators can put on their website to help reduce abuse queries.
22214 - When tunneling an encrypted directory connection, and its first
22215 circuit fails, do not leave it unattached and ask the controller
22216 to deal. Fixes the second part of bug 681.
22217 - Make bridge authorities correctly expire old extrainfo documents
22221 Changes in version 0.2.0.26-rc - 2008-05-13
22222 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
22223 in Debian's OpenSSL packages. All users running any 0.2.0.x version
22224 should upgrade, whether they're running Debian or not.
22226 o Major security fixes:
22227 - Use new V3 directory authority keys on the tor26, gabelmoo, and
22228 moria1 V3 directory authorities. The old keys were generated with
22229 a vulnerable version of Debian's OpenSSL package, and must be
22230 considered compromised. Other authorities' keys were not generated
22231 with an affected version of OpenSSL.
22234 - List authority signatures as "unrecognized" based on DirServer
22235 lines, not on cert cache. Bugfix on 0.2.0.x.
22238 - Add a new V3AuthUseLegacyKey option to make it easier for
22239 authorities to change their identity keys if they have to.
22242 Changes in version 0.2.0.25-rc - 2008-04-23
22243 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
22246 - Remember to initialize threading before initializing logging.
22247 Otherwise, many BSD-family implementations will crash hard on
22248 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
22251 - Authorities correctly free policies on bad servers on
22252 exit. Fixes bug 672. Bugfix on 0.2.0.x.
22255 Changes in version 0.2.0.24-rc - 2008-04-22
22256 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
22257 v3 directory authority, makes relays with dynamic IP addresses and no
22258 DirPort notice more quickly when their IP address changes, fixes a few
22259 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
22261 o New directory authorities:
22262 - Take lefkada out of the list of v3 directory authorities, since
22263 it has been down for months.
22264 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
22268 - Detect address changes more quickly on non-directory mirror
22269 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
22271 o Minor features (security):
22272 - Reject requests for reverse-dns lookup of names that are in
22273 a private address space. Patch from lodger.
22274 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
22277 o Minor bugfixes (crashes):
22278 - Avoid a rare assert that can trigger when Tor doesn't have much
22279 directory information yet and it tries to fetch a v2 hidden
22280 service descriptor. Fixes bug 651, reported by nwf.
22281 - Initialize log mutex before initializing dmalloc. Otherwise,
22282 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
22283 - Use recursive pthread mutexes in order to avoid deadlock when
22284 logging debug-level messages to a controller. Bug spotted by nwf,
22285 bugfix on 0.2.0.16-alpha.
22287 o Minor bugfixes (resource management):
22288 - Keep address policies from leaking memory: start their refcount
22289 at 1, not 2. Bugfix on 0.2.0.16-alpha.
22290 - Free authority certificates on exit, so they don't look like memory
22291 leaks. Bugfix on 0.2.0.19-alpha.
22292 - Free static hashtables for policy maps and for TLS connections on
22293 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
22294 - Avoid allocating extra space when computing consensuses on 64-bit
22295 platforms. Bug spotted by aakova.
22297 o Minor bugfixes (misc):
22298 - Do not read the configuration file when we've only been told to
22299 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
22300 based on patch from Sebastian Hahn.
22301 - Exit relays that are used as a client can now reach themselves
22302 using the .exit notation, rather than just launching an infinite
22303 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
22304 - When attempting to open a logfile fails, tell us why.
22305 - Fix a dumb bug that was preventing us from knowing that we should
22306 preemptively build circuits to handle expected directory requests.
22307 Fixes bug 660. Bugfix on 0.1.2.x.
22308 - Warn less verbosely about clock skew from netinfo cells from
22309 untrusted sources. Fixes bug 663.
22310 - Make controller stream events for DNS requests more consistent,
22311 by adding "new stream" events for DNS requests, and removing
22312 spurious "stream closed" events" for cached reverse resolves.
22313 Patch from mwenge. Fixes bug 646.
22314 - Correctly notify one-hop connections when a circuit build has
22315 failed. Possible fix for bug 669. Found by lodger.
22318 Changes in version 0.2.0.23-rc - 2008-03-24
22319 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
22320 makes bootstrapping faster if the first directory mirror you contact
22321 is down. The bundles also include the new Vidalia 0.1.2 release.
22324 - When a tunneled directory request is made to a directory server
22325 that's down, notice after 30 seconds rather than 120 seconds. Also,
22326 fail any begindir streams that are pending on it, so they can
22327 retry elsewhere. This was causing multi-minute delays on bootstrap.
22330 Changes in version 0.2.0.22-rc - 2008-03-18
22331 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
22332 enables encrypted directory connections by default for non-relays, fixes
22333 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
22334 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
22337 - Enable encrypted directory connections by default for non-relays,
22338 so censor tools that block Tor directory connections based on their
22339 plaintext patterns will no longer work. This means Tor works in
22340 certain censored countries by default again.
22343 - Make sure servers always request certificates from clients during
22344 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
22345 - Do not enter a CPU-eating loop when a connection is closed in
22346 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
22347 diagnosed by lodger; bugfix on 0.2.0.20-rc.
22348 - Fix assertion failure that could occur when a blocked circuit
22349 became unblocked, and it had pending client DNS requests. Bugfix
22350 on 0.2.0.1-alpha. Fixes bug 632.
22352 o Minor bugfixes (on 0.1.2.x):
22353 - Generate "STATUS_SERVER" events rather than misspelled
22354 "STATUS_SEVER" events. Caught by mwenge.
22355 - When counting the number of bytes written on a TLS connection,
22356 look at the BIO actually used for writing to the network, not
22357 at the BIO used (sometimes) to buffer data for the network.
22358 Looking at different BIOs could result in write counts on the
22359 order of ULONG_MAX. Fixes bug 614.
22360 - On Windows, correctly detect errors when listing the contents of
22361 a directory. Fix from lodger.
22363 o Minor bugfixes (on 0.2.0.x):
22364 - Downgrade "sslv3 alert handshake failure" message to INFO.
22365 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
22366 left BandwidthRate and BandwidthBurst at the default, we would be
22367 silently limited by those defaults. Now raise them to match the
22368 RelayBandwidth* values.
22369 - Fix the SVK version detection logic to work correctly on a branch.
22370 - Make --enable-openbsd-malloc work correctly on Linux with alpha
22371 CPUs. Fixes bug 625.
22372 - Logging functions now check that the passed severity is sane.
22373 - Use proper log levels in the testsuite call of
22374 get_interface_address6().
22375 - When using a nonstandard malloc, do not use the platform values for
22376 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
22377 - Make the openbsd malloc code use 8k pages on alpha CPUs and
22379 - Detect mismatched page sizes when using --enable-openbsd-malloc.
22380 - Avoid double-marked-for-close warning when certain kinds of invalid
22381 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
22382 for bug 617. Bugfix on 0.2.0.1-alpha.
22383 - Make sure that the "NULL-means-reject *:*" convention is followed by
22384 all the policy manipulation functions, avoiding some possible crash
22385 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
22386 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
22387 actually works, and doesn't warn about every single reverse lookup.
22388 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
22391 - Only log guard node status when guard node status has changed.
22392 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
22393 make "INFO" 75% less verbose.
22396 Changes in version 0.2.0.21-rc - 2008-03-02
22397 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
22398 makes Tor work well with Vidalia again, fixes a rare assert bug,
22399 and fixes a pair of more minor bugs. The bundles also include Vidalia
22400 0.1.0 and Torbutton 1.1.16.
22403 - The control port should declare that it requires password auth
22404 when HashedControlSessionPassword is set too. Patch from Matt Edman;
22405 bugfix on 0.2.0.20-rc. Fixes bug 615.
22406 - Downgrade assert in connection_buckets_decrement() to a log message.
22407 This may help us solve bug 614, and in any case will make its
22408 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
22409 - We were sometimes miscounting the number of bytes read from the
22410 network, causing our rate limiting to not be followed exactly.
22411 Bugfix on 0.2.0.16-alpha. Reported by lodger.
22414 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
22415 OpenSSL versions should have been working fine. Diagnosis and patch
22416 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
22417 Bugfix on 0.2.0.20-rc.
22420 Changes in version 0.2.0.20-rc - 2008-02-24
22421 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
22422 makes more progress towards normalizing Tor's TLS handshake, makes
22423 hidden services work better again, helps relays bootstrap if they don't
22424 know their IP address, adds optional support for linking in openbsd's
22425 allocator or tcmalloc, allows really fast relays to scale past 15000
22426 sockets, and fixes a bunch of minor bugs reported by Veracode.
22429 - Enable the revised TLS handshake based on the one designed by
22430 Steven Murdoch in proposal 124, as revised in proposal 130. It
22431 includes version negotiation for OR connections as described in
22432 proposal 105. The new handshake is meant to be harder for censors
22433 to fingerprint, and it adds the ability to detect certain kinds of
22434 man-in-the-middle traffic analysis attacks. The version negotiation
22435 feature will allow us to improve Tor's link protocol more safely
22437 - Choose which bridge to use proportional to its advertised bandwidth,
22438 rather than uniformly at random. This should speed up Tor for
22439 bridge users. Also do this for people who set StrictEntryNodes.
22440 - When a TrackHostExits-chosen exit fails too many times in a row,
22441 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
22444 - Resolved problems with (re-)fetching hidden service descriptors.
22445 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
22446 and 0.2.0.19-alpha.
22447 - If we only ever used Tor for hidden service lookups or posts, we
22448 would stop building circuits and start refusing connections after
22449 24 hours, since we falsely believed that Tor was dormant. Reported
22450 by nwf; bugfix on 0.1.2.x.
22451 - Servers that don't know their own IP address should go to the
22452 authorities for their first directory fetch, even if their DirPort
22453 is off or if they don't know they're reachable yet. This will help
22454 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
22455 - When counting the number of open sockets, count not only the number
22456 of sockets we have received from the socket() call, but also
22457 the number we've gotten from accept() and socketpair(). This bug
22458 made us fail to count all sockets that we were using for incoming
22459 connections. Bugfix on 0.2.0.x.
22460 - Fix code used to find strings within buffers, when those strings
22461 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
22462 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
22463 - Add a new __HashedControlSessionPassword option for controllers
22464 to use for one-off session password hashes that shouldn't get
22465 saved to disk by SAVECONF --- Vidalia users were accumulating a
22466 pile of HashedControlPassword lines in their torrc files, one for
22467 each time they had restarted Tor and then clicked Save. Make Tor
22468 automatically convert "HashedControlPassword" to this new option but
22469 only when it's given on the command line. Partial fix for bug 586.
22471 o Minor features (performance):
22472 - Tune parameters for cell pool allocation to minimize amount of
22474 - Add OpenBSD malloc code from phk as an optional malloc
22475 replacement on Linux: some glibc libraries do very poorly
22476 with Tor's memory allocation patterns. Pass
22477 --enable-openbsd-malloc to get the replacement malloc code.
22478 - Add a --with-tcmalloc option to the configure script to link
22479 against tcmalloc (if present). Does not yet search for
22480 non-system include paths.
22481 - Stop imposing an arbitrary maximum on the number of file descriptors
22482 used for busy servers. Bug reported by Olaf Selke; patch from
22485 o Minor features (other):
22486 - When SafeLogging is disabled, log addresses along with all TLS
22488 - When building with --enable-gcc-warnings, check for whether Apple's
22489 warning "-Wshorten-64-to-32" is available.
22490 - Add a --passphrase-fd argument to the tor-gencert command for
22493 o Minor bugfixes (memory leaks and code problems):
22494 - We were leaking a file descriptor if Tor started with a zero-length
22495 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
22496 - Detect size overflow in zlib code. Reported by Justin Ferguson and
22498 - We were comparing the raw BridgePassword entry with a base64'ed
22499 version of it, when handling a "/tor/networkstatus-bridges"
22500 directory request. Now compare correctly. Noticed by Veracode.
22501 - Recover from bad tracked-since value in MTBF-history file.
22502 Should fix bug 537.
22503 - Alter the code that tries to recover from unhandled write
22504 errors, to not try to flush onto a socket that's given us
22505 unhandled errors. Bugfix on 0.1.2.x.
22506 - Make Unix controlsockets work correctly on OpenBSD. Patch from
22507 tup. Bugfix on 0.2.0.3-alpha.
22509 o Minor bugfixes (other):
22510 - If we have an extra-info document for our server, always make
22511 it available on the control port, even if we haven't gotten
22512 a copy of it from an authority yet. Patch from mwenge.
22513 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
22514 - Directory mirrors no longer include a guess at the client's IP
22515 address if the connection appears to be coming from the same /24
22516 network; it was producing too many wrong guesses.
22517 - Make the new hidden service code respect the SafeLogging setting.
22518 Bugfix on 0.2.0.x. Patch from Karsten.
22519 - When starting as an authority, do not overwrite all certificates
22520 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
22521 - If we're trying to flush the last bytes on a connection (for
22522 example, when answering a directory request), reset the
22523 time-to-give-up timeout every time we manage to write something
22524 on the socket. Bugfix on 0.1.2.x.
22525 - Change the behavior of "getinfo status/good-server-descriptor"
22526 so it doesn't return failure when any authority disappears.
22527 - Even though the man page said that "TrackHostExits ." should
22528 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
22529 - Report TLS "zero return" case as a "clean close" and "IO error"
22530 as a "close". Stop calling closes "unexpected closes": existing
22531 Tors don't use SSL_close(), so having a connection close without
22532 the TLS shutdown handshake is hardly unexpected.
22533 - Send NAMESERVER_STATUS messages for a single failed nameserver
22536 o Code simplifications and refactoring:
22537 - Remove the tor_strpartition function: its logic was confused,
22538 and it was only used for one thing that could be implemented far
22542 Changes in version 0.2.0.19-alpha - 2008-02-09
22543 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
22544 handshake, makes path selection for relays more secure and IP address
22545 guessing more robust, and generally fixes a lot of bugs in preparation
22546 for calling the 0.2.0 branch stable.
22549 - Do not include recognizeable strings in the commonname part of
22550 Tor's x509 certificates.
22553 - If we're a relay, avoid picking ourselves as an introduction point,
22554 a rendezvous point, or as the final hop for internal circuits. Bug
22555 reported by taranis and lodger. Bugfix on 0.1.2.x.
22556 - Patch from "Andrew S. Lists" to catch when we contact a directory
22557 mirror at IP address X and he says we look like we're coming from
22558 IP address X. Bugfix on 0.1.2.x.
22560 o Minor features (security):
22561 - Be more paranoid about overwriting sensitive memory on free(),
22562 as a defensive programming tactic to ensure forward secrecy.
22564 o Minor features (directory authority):
22565 - Actually validate the options passed to AuthDirReject,
22566 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
22567 - Reject router descriptors with out-of-range bandwidthcapacity or
22568 bandwidthburst values.
22570 o Minor features (controller):
22571 - Reject controller commands over 1MB in length. This keeps rogue
22572 processes from running us out of memory.
22574 o Minor features (misc):
22575 - Give more descriptive well-formedness errors for out-of-range
22576 hidden service descriptor/protocol versions.
22577 - Make memory debugging information describe more about history
22578 of cell allocation, so we can help reduce our memory use.
22580 o Deprecated features (controller):
22581 - The status/version/num-versioning and status/version/num-concurring
22582 GETINFO options are no longer useful in the v3 directory protocol:
22583 treat them as deprecated, and warn when they're used.
22586 - When our consensus networkstatus has been expired for a while, stop
22587 being willing to build circuits using it. Fixes bug 401. Bugfix
22589 - Directory caches now fetch certificates from all authorities
22590 listed in a networkstatus consensus, even when they do not
22591 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
22592 - When connecting to a bridge without specifying its key, insert
22593 the connection into the identity-to-connection map as soon as
22594 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
22595 - Detect versions of OS X where malloc_good_size() is present in the
22596 library but never actually declared. Resolves bug 587. Bugfix
22598 - Stop incorrectly truncating zlib responses to directory authority
22599 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
22600 - Stop recommending that every server operator send mail to tor-ops.
22601 Resolves bug 597. Bugfix on 0.1.2.x.
22602 - Don't trigger an assert if we start a directory authority with a
22603 private IP address (like 127.0.0.1).
22604 - Avoid possible failures when generating a directory with routers
22605 with over-long versions strings, or too many flags set. Bugfix
22607 - If an attempt to launch a DNS resolve request over the control
22608 port fails because we have overrun the limit on the number of
22609 connections, tell the controller that the request has failed.
22610 - Avoid using too little bandwidth when our clock skips a few
22611 seconds. Bugfix on 0.1.2.x.
22612 - Fix shell error when warning about missing packages in configure
22613 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
22614 - Do not become confused when receiving a spurious VERSIONS-like
22615 cell from a confused v1 client. Bugfix on 0.2.0.x.
22616 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
22617 introduction points for a hidden service have failed. Patch from
22618 Karsten Loesing. Bugfix on 0.2.0.x.
22620 o Code simplifications and refactoring:
22621 - Remove some needless generality from cpuworker code, for improved
22623 - Stop overloading the circuit_t.onionskin field for both "onionskin
22624 from a CREATE cell that we are waiting for a cpuworker to be
22625 assigned" and "onionskin from an EXTEND cell that we are going to
22626 send to an OR as soon as we are connected". Might help with bug 600.
22627 - Add an in-place version of aes_crypt() so that we can avoid doing a
22628 needless memcpy() call on each cell payload.
22631 Changes in version 0.2.0.18-alpha - 2008-01-25
22632 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
22633 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
22634 that can warn or reject connections to ports generally associated with
22635 vulnerable-plaintext protocols.
22637 o New directory authorities:
22638 - Set up dannenberg (run by CCC) as the sixth v3 directory
22642 - Fix a major memory leak when attempting to use the v2 TLS
22643 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
22644 - We accidentally enabled the under-development v2 TLS handshake
22645 code, which was causing log entries like "TLS error while
22646 renegotiating handshake". Disable it again. Resolves bug 590.
22647 - We were computing the wrong Content-Length: header for directory
22648 responses that need to be compressed on the fly, causing clients
22649 asking for those items to always fail. Bugfix on 0.2.0.x; partially
22653 - Avoid going directly to the directory authorities even if you're a
22654 relay, if you haven't found yourself reachable yet or if you've
22655 decided not to advertise your dirport yet. Addresses bug 556.
22656 - If we've gone 12 hours since our last bandwidth check, and we
22657 estimate we have less than 50KB bandwidth capacity but we could
22658 handle more, do another bandwidth test.
22659 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
22660 Tor can warn and/or refuse connections to ports commonly used with
22661 vulnerable-plaintext protocols. Currently we warn on ports 23,
22662 109, 110, and 143, but we don't reject any.
22665 - When we setconf ClientOnly to 1, close any current OR and Dir
22666 listeners. Reported by mwenge.
22667 - When we get a consensus that's been signed by more people than
22668 we expect, don't log about it; it's not a big deal. Reported
22672 - Don't answer "/tor/networkstatus-bridges" directory requests if
22673 the request isn't encrypted.
22674 - Make "ClientOnly 1" config option disable directory ports too.
22675 - Patches from Karsten Loesing to make v2 hidden services more
22676 robust: work even when there aren't enough HSDir relays available;
22677 retry when a v2 rend desc fetch fails; but don't retry if we
22678 already have a usable v0 rend desc.
22681 Changes in version 0.2.0.17-alpha - 2008-01-17
22682 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
22685 - Make the tor-gencert man page get included correctly in the tarball.
22688 Changes in version 0.2.0.16-alpha - 2008-01-17
22689 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
22690 Loesing, and generally cleans up a lot of features and minor bugs.
22692 o New directory authorities:
22693 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
22696 o Major performance improvements:
22697 - Switch our old ring buffer implementation for one more like that
22698 used by free Unix kernels. The wasted space in a buffer with 1mb
22699 of data will now be more like 8k than 1mb. The new implementation
22700 also avoids realloc();realloc(); patterns that can contribute to
22701 memory fragmentation.
22704 - Configuration files now accept C-style strings as values. This
22705 helps encode characters not allowed in the current configuration
22706 file format, such as newline or #. Addresses bug 557.
22707 - Although we fixed bug 539 (where servers would send HTTP status 503
22708 responses _and_ send a body too), there are still servers out
22709 there that haven't upgraded. Therefore, make clients parse such
22710 bodies when they receive them.
22711 - When we're not serving v2 directory information, there is no reason
22712 to actually keep any around. Remove the obsolete files and directory
22713 on startup if they are very old and we aren't going to serve them.
22715 o Minor performance improvements:
22716 - Reference-count and share copies of address policy entries; only 5%
22717 of them were actually distinct.
22718 - Never walk through the list of logs if we know that no log is
22719 interested in a given message.
22722 - When an authority has not signed a consensus, do not try to
22723 download a nonexistent "certificate with key 00000000". Bugfix
22724 on 0.2.0.x. Fixes bug 569.
22725 - Fix a rare assert error when we're closing one of our threads:
22726 use a mutex to protect the list of logs, so we never write to the
22727 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
22728 bug 575, which is kind of the revenge of bug 222.
22729 - Patch from Karsten Loesing to complain less at both the client
22730 and the relay when a relay used to have the HSDir flag but doesn't
22731 anymore, and we try to upload a hidden service descriptor.
22732 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
22734 - Do not try to download missing certificates until we have tried
22735 to check our fallback consensus. Fixes bug 583.
22736 - Make bridges round reported GeoIP stats info up to the nearest
22737 estimate, not down. Now we can distinguish between "0 people from
22738 this country" and "1 person from this country".
22739 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
22740 - Avoid possible segfault if key generation fails in
22741 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
22742 - Avoid segfault in the case where a badly behaved v2 versioning
22743 directory sends a signed networkstatus with missing client-versions.
22745 - Avoid segfaults on certain complex invocations of
22746 router_get_by_hexdigest(). Bugfix on 0.1.2.
22747 - Correct bad index on array access in parse_http_time(). Bugfix
22749 - Fix possible bug in vote generation when server versions are present
22750 but client versions are not.
22751 - Fix rare bug on REDIRECTSTREAM control command when called with no
22752 port set: it could erroneously report an error when none had
22754 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
22755 compressing large objects and find ourselves with more than 4k
22756 left over. Bugfix on 0.2.0.
22757 - Fix a small memory leak when setting up a hidden service.
22758 - Fix a few memory leaks that could in theory happen under bizarre
22760 - Fix an assert if we post a general-purpose descriptor via the
22761 control port but that descriptor isn't mentioned in our current
22762 network consensus. Bug reported by Jon McLachlan; bugfix on
22765 o Minor features (controller):
22766 - Get NS events working again. Patch from tup.
22767 - The GETCONF command now escapes and quotes configuration values
22768 that don't otherwise fit into the torrc file.
22769 - The SETCONF command now handles quoted values correctly.
22771 o Minor features (directory authorities):
22772 - New configuration options to override default maximum number of
22773 servers allowed on a single IP address. This is important for
22774 running a test network on a single host.
22775 - Actually implement the -s option to tor-gencert.
22776 - Add a manual page for tor-gencert.
22778 o Minor features (bridges):
22779 - Bridge authorities no longer serve bridge descriptors over
22780 unencrypted connections.
22782 o Minor features (other):
22783 - Add hidden services and DNSPorts to the list of things that make
22784 Tor accept that it has running ports. Change starting Tor with no
22785 ports from a fatal error to a warning; we might change it back if
22786 this turns out to confuse anybody. Fixes bug 579.
22789 Changes in version 0.1.2.19 - 2008-01-17
22790 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
22791 exit policy a little bit more conservative so it's safer to run an
22792 exit relay on a home system, and fixes a variety of smaller issues.
22795 - Exit policies now reject connections that are addressed to a
22796 relay's public (external) IP address too, unless
22797 ExitPolicyRejectPrivate is turned off. We do this because too
22798 many relays are running nearby to services that trust them based
22799 on network address.
22802 - When the clock jumps forward a lot, do not allow the bandwidth
22803 buckets to become negative. Fixes bug 544.
22804 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
22805 on every successful resolve. Reported by Mike Perry.
22806 - Purge old entries from the "rephist" database and the hidden
22807 service descriptor database even when DirPort is zero.
22808 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
22809 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
22810 crashing or mis-answering these requests.
22811 - When we decide to send a 503 response to a request for servers, do
22812 not then also send the server descriptors: this defeats the whole
22813 purpose. Fixes bug 539.
22816 - Changing the ExitPolicyRejectPrivate setting should cause us to
22817 rebuild our server descriptor.
22818 - Fix handling of hex nicknames when answering controller requests for
22819 networkstatus by name, or when deciding whether to warn about
22820 unknown routers in a config option. (Patch from mwenge.)
22821 - Fix a couple of hard-to-trigger autoconf problems that could result
22822 in really weird results on platforms whose sys/types.h files define
22823 nonstandard integer types.
22824 - Don't try to create the datadir when running --verify-config or
22825 --hash-password. Resolves bug 540.
22826 - If we were having problems getting a particular descriptor from the
22827 directory caches, and then we learned about a new descriptor for
22828 that router, we weren't resetting our failure count. Reported
22830 - Although we fixed bug 539 (where servers would send HTTP status 503
22831 responses _and_ send a body too), there are still servers out there
22832 that haven't upgraded. Therefore, make clients parse such bodies
22833 when they receive them.
22834 - Run correctly on systems where rlim_t is larger than unsigned long.
22835 This includes some 64-bit systems.
22836 - Run correctly on platforms (like some versions of OS X 10.5) where
22837 the real limit for number of open files is OPEN_FILES, not rlim_max
22838 from getrlimit(RLIMIT_NOFILES).
22839 - Avoid a spurious free on base64 failure.
22840 - Avoid segfaults on certain complex invocations of
22841 router_get_by_hexdigest().
22842 - Fix rare bug on REDIRECTSTREAM control command when called with no
22843 port set: it could erroneously report an error when none had
22847 Changes in version 0.2.0.15-alpha - 2007-12-25
22848 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
22849 features added in 0.2.0.13-alpha.
22852 - Fix several remotely triggerable asserts based on DirPort requests
22853 for a v2 or v3 networkstatus object before we were prepared. This
22854 was particularly bad for 0.2.0.13 and later bridge relays, who
22855 would never have a v2 networkstatus and would thus always crash
22856 when used. Bugfixes on 0.2.0.x.
22857 - Estimate the v3 networkstatus size more accurately, rather than
22858 estimating it at zero bytes and giving it artificially high priority
22859 compared to other directory requests. Bugfix on 0.2.0.x.
22862 - Fix configure.in logic for cross-compilation.
22863 - When we load a bridge descriptor from the cache, and it was
22864 previously unreachable, mark it as retriable so we won't just
22865 ignore it. Also, try fetching a new copy immediately. Bugfixes
22867 - The bridge GeoIP stats were counting other relays, for example
22868 self-reachability and authority-reachability tests.
22871 - Support compilation to target iPhone; patch from cjacker huang.
22872 To build for iPhone, pass the --enable-iphone option to configure.
22875 Changes in version 0.2.0.14-alpha - 2007-12-23
22877 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
22878 without a datadirectory from a previous Tor install. Reported
22880 - Fix a crash when we fetch a descriptor that turns out to be
22881 unexpected (it used to be in our networkstatus when we started
22882 fetching it, but it isn't in our current networkstatus), and we
22883 aren't using bridges. Bugfix on 0.2.0.x.
22884 - Fix a crash when accessing hidden services: it would work the first
22885 time you use a given introduction point for your service, but
22886 on subsequent requests we'd be using garbage memory. Fixed by
22887 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
22888 - Fix a crash when we load a bridge descriptor from disk but we don't
22889 currently have a Bridge line for it in our torrc. Bugfix on
22893 - If bridge authorities set BridgePassword, they will serve a
22894 snapshot of known bridge routerstatuses from their DirPort to
22895 anybody who knows that password. Unset by default.
22898 - Make the unit tests build again.
22899 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
22900 - Make PublishServerDescriptor default to 1, so the default doesn't
22901 have to change as we invent new directory protocol versions.
22902 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
22903 be included unless sys/time.h is already included. Fixes
22904 bug 553. Bugfix on 0.2.0.x.
22905 - If we receive a general-purpose descriptor and then receive an
22906 identical bridge-purpose descriptor soon after, don't discard
22907 the next one as a duplicate.
22910 - If BridgeRelay is set to 1, then the default for
22911 PublishServerDescriptor is now "bridge" rather than "v2,v3".
22912 - If the user sets RelayBandwidthRate but doesn't set
22913 RelayBandwidthBurst, then make them equal rather than erroring out.
22916 Changes in version 0.2.0.13-alpha - 2007-12-21
22917 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
22918 Goodell, fixes many more bugs, and adds a lot of infrastructure for
22921 o New directory authorities:
22922 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
22926 - Only update guard status (usable / not usable) once we have
22927 enough directory information. This was causing us to always pick
22928 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
22929 causing us to discard all our guards on startup if we hadn't been
22930 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
22931 - Purge old entries from the "rephist" database and the hidden
22932 service descriptor databases even when DirPort is zero. Bugfix
22934 - We were ignoring our RelayBandwidthRate for the first 30 seconds
22935 after opening a circuit -- even a relayed circuit. Bugfix on
22937 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
22938 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
22939 crashing or mis-answering these types of requests.
22940 - Relays were publishing their server descriptor to v1 and v2
22941 directory authorities, but they didn't try publishing to v3-only
22942 authorities. Fix this; and also stop publishing to v1 authorities.
22944 - When we were reading router descriptors from cache, we were ignoring
22945 the annotations -- so for example we were reading in bridge-purpose
22946 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
22947 - When we decided to send a 503 response to a request for servers, we
22948 were then also sending the server descriptors: this defeats the
22949 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
22952 - Bridge relays now behave like clients with respect to time
22953 intervals for downloading new consensus documents -- otherwise they
22954 stand out. Bridge users now wait until the end of the interval,
22955 so their bridge relay will be sure to have a new consensus document.
22956 - Three new config options (AlternateDirAuthority,
22957 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
22958 user selectively replace the default directory authorities by type,
22959 rather than the all-or-nothing replacement that DirServer offers.
22960 - Tor can now be configured to read a GeoIP file from disk in one
22961 of two formats. This can be used by controllers to map IP addresses
22962 to countries. Eventually, it may support exit-by-country.
22963 - When possible, bridge relays remember which countries users
22964 are coming from, and report aggregate information in their
22965 extra-info documents, so that the bridge authorities can learn
22966 where Tor is blocked.
22967 - Bridge directory authorities now do reachability testing on the
22968 bridges they know. They provide router status summaries to the
22969 controller via "getinfo ns/purpose/bridge", and also dump summaries
22970 to a file periodically.
22971 - Stop fetching directory info so aggressively if your DirPort is
22972 on but your ORPort is off; stop fetching v2 dir info entirely.
22973 You can override these choices with the new FetchDirInfoEarly
22977 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
22978 consensus documents when there are too many relays at a single
22979 IP address. Now clear it in v2 network status documents too, and
22980 also clear it in routerinfo_t when the relay is no longer listed
22981 in the relevant networkstatus document.
22982 - Don't crash if we get an unexpected value for the
22983 PublishServerDescriptor config option. Reported by Matt Edman;
22984 bugfix on 0.2.0.9-alpha.
22985 - Our new v2 hidden service descriptor format allows descriptors
22986 that have no introduction points. But Tor crashed when we tried
22987 to build a descriptor with no intro points (and it would have
22988 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
22989 by Karsten Loesing.
22990 - Fix building with dmalloc 5.5.2 with glibc.
22991 - Reject uploaded descriptors and extrainfo documents if they're
22992 huge. Otherwise we'll cache them all over the network and it'll
22993 clog everything up. Reported by Aljosha Judmayer.
22994 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
22995 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
22996 - When the DANGEROUS_VERSION controller status event told us we're
22997 running an obsolete version, it used the string "OLD" to describe
22998 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
22999 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
23000 - If we can't expand our list of entry guards (e.g. because we're
23001 using bridges or we have StrictEntryNodes set), don't mark relays
23002 down when they fail a directory request. Otherwise we're too quick
23003 to mark all our entry points down. Bugfix on 0.1.2.x.
23004 - Fix handling of hex nicknames when answering controller requests for
23005 networkstatus by name, or when deciding whether to warn about unknown
23006 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
23007 - Fix a couple of hard-to-trigger autoconf problems that could result
23008 in really weird results on platforms whose sys/types.h files define
23009 nonstandard integer types. Bugfix on 0.1.2.x.
23010 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
23011 - Don't crash on name lookup when we have no current consensus. Fixes
23012 bug 538; bugfix on 0.2.0.x.
23013 - Only Tors that want to mirror the v2 directory info should
23014 create the "cached-status" directory in their datadir. (All Tors
23015 used to create it.) Bugfix on 0.2.0.9-alpha.
23016 - Directory authorities should only automatically download Extra Info
23017 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
23020 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
23021 consumers. (We already do this on HUP.)
23022 - Authorities and caches fetch the v2 networkstatus documents
23023 less often, now that v3 is encouraged.
23024 - Add a new config option BridgeRelay that specifies you want to
23025 be a bridge relay. Right now the only difference is that it makes
23026 you answer begin_dir requests, and it makes you cache dir info,
23027 even if your DirPort isn't on.
23028 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
23029 ask about source, timestamp of arrival, purpose, etc. We need
23030 something like this to help Vidalia not do GeoIP lookups on bridge
23032 - Allow multiple HashedControlPassword config lines, to support
23033 multiple controller passwords.
23034 - Authorities now decide whether they're authoritative for a given
23035 router based on the router's purpose.
23036 - New config options AuthDirBadDir and AuthDirListBadDirs for
23037 authorities to mark certain relays as "bad directories" in the
23038 networkstatus documents. Also supports the "!baddir" directive in
23039 the approved-routers file.
23042 Changes in version 0.2.0.12-alpha - 2007-11-16
23043 This twelfth development snapshot fixes some more build problems as
23044 well as a few minor bugs.
23047 - Make it build on OpenBSD again. Patch from tup.
23048 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
23049 package-building for Red Hat, OS X, etc.
23051 o Minor bugfixes (on 0.1.2.x):
23052 - Changing the ExitPolicyRejectPrivate setting should cause us to
23053 rebuild our server descriptor.
23055 o Minor bugfixes (on 0.2.0.x):
23056 - When we're lacking a consensus, don't try to perform rendezvous
23057 operations. Reported by Karsten Loesing.
23058 - Fix a small memory leak whenever we decide against using a
23059 newly picked entry guard. Reported by Mike Perry.
23060 - When authorities detected more than two relays running on the same
23061 IP address, they were clearing all the status flags but forgetting
23062 to clear the "hsdir" flag. So clients were being told that a
23063 given relay was the right choice for a v2 hsdir lookup, yet they
23064 never had its descriptor because it was marked as 'not running'
23066 - If we're trying to fetch a bridge descriptor and there's no way
23067 the bridge authority could help us (for example, we don't know
23068 a digest, or there is no bridge authority), don't be so eager to
23069 fall back to asking the bridge authority.
23070 - If we're using bridges or have strictentrynodes set, and our
23071 chosen exit is in the same family as all our bridges/entry guards,
23072 then be flexible about families.
23075 - When we negotiate a v2 link-layer connection (not yet implemented),
23076 accept RELAY_EARLY cells and turn them into RELAY cells if we've
23077 negotiated a v1 connection for their next step. Initial code for
23081 Changes in version 0.2.0.11-alpha - 2007-11-12
23082 This eleventh development snapshot fixes some build problems with
23083 the previous snapshot. It also includes a more secure-by-default exit
23084 policy for relays, fixes an enormous memory leak for exit relays, and
23085 fixes another bug where servers were falling out of the directory list.
23088 - Exit policies now reject connections that are addressed to a
23089 relay's public (external) IP address too, unless
23090 ExitPolicyRejectPrivate is turned off. We do this because too
23091 many relays are running nearby to services that trust them based
23092 on network address. Bugfix on 0.1.2.x.
23095 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
23096 on every successful resolve. Reported by Mike Perry; bugfix
23098 - On authorities, never downgrade to old router descriptors simply
23099 because they're listed in the consensus. This created a catch-22
23100 where we wouldn't list a new descriptor because there was an
23101 old one in the consensus, and we couldn't get the new one in the
23102 consensus because we wouldn't list it. Possible fix for bug 548.
23103 Also, this might cause bug 543 to appear on authorities; if so,
23104 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
23106 o Packaging fixes on 0.2.0.10-alpha:
23107 - We were including instructions about what to do with the
23108 src/config/fallback-consensus file, but we weren't actually
23109 including it in the tarball. Disable all of that for now.
23112 - Allow people to say PreferTunnelledDirConns rather than
23113 PreferTunneledDirConns, for those alternate-spellers out there.
23116 - Don't reevaluate all the information from our consensus document
23117 just because we've downloaded a v2 networkstatus that we intend
23118 to cache. Fixes bug 545; bugfix on 0.2.0.x.
23121 Changes in version 0.2.0.10-alpha - 2007-11-10
23122 This tenth development snapshot adds a third v3 directory authority
23123 run by Mike Perry, adds most of Karsten Loesing's new hidden service
23124 descriptor format, fixes a bad crash bug and new bridge bugs introduced
23125 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
23126 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
23127 addresses many more minor issues.
23129 o New directory authorities:
23130 - Set up ides (run by Mike Perry) as the third v3 directory authority.
23133 - Allow tunnelled directory connections to ask for an encrypted
23134 "begin_dir" connection or an anonymized "uses a full Tor circuit"
23135 connection independently. Now we can make anonymized begin_dir
23136 connections for (e.g.) more secure hidden service posting and
23138 - More progress on proposal 114: code from Karsten Loesing to
23139 implement new hidden service descriptor format.
23140 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
23141 accommodate the growing number of servers that use the default
23142 and are reaching it.
23143 - Directory authorities use a new formula for selecting which nodes
23144 to advertise as Guards: they must be in the top 7/8 in terms of
23145 how long we have known about them, and above the median of those
23146 nodes in terms of weighted fractional uptime.
23147 - Make "not enough dir info yet" warnings describe *why* Tor feels
23148 it doesn't have enough directory info yet.
23151 - Stop servers from crashing if they set a Family option (or
23152 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
23154 - Make bridge users work again -- the move to v3 directories in
23155 0.2.0.9-alpha had introduced a number of bugs that made bridges
23156 no longer work for clients.
23157 - When the clock jumps forward a lot, do not allow the bandwidth
23158 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
23160 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
23161 - When the consensus lists a router descriptor that we previously were
23162 mirroring, but that we considered non-canonical, reload the
23163 descriptor as canonical. This fixes bug 543 where Tor servers
23164 would start complaining after a few days that they don't have
23165 enough directory information to build a circuit.
23166 - Consider replacing the current consensus when certificates arrive
23167 that make the pending consensus valid. Previously, we were only
23168 considering replacement when the new certs _didn't_ help.
23169 - Fix an assert error on startup if we didn't already have the
23170 consensus and certs cached in our datadirectory: we were caching
23171 the consensus in consensus_waiting_for_certs but then free'ing it
23173 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
23174 Request) if we need more v3 certs but we've already got pending
23175 requests for all of them.
23176 - Correctly back off from failing certificate downloads. Fixes
23178 - Authorities don't vote on the Running flag if they have been running
23179 for less than 30 minutes themselves. Fixes bug 547, where a newly
23180 started authority would vote that everyone was down.
23182 o New requirements:
23183 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
23184 it, it had no AES, and it hasn't seen any security patches since
23188 - Clients now hold circuitless TLS connections open for 1.5 times
23189 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
23190 rebuild a new circuit over them within that timeframe. Previously,
23191 they held them open only for KeepalivePeriod (5 minutes).
23192 - Use "If-Modified-Since" to avoid retrieving consensus
23193 networkstatuses that we already have.
23194 - When we have no consensus, check FallbackNetworkstatusFile (defaults
23195 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
23196 we start knowing some directory caches.
23197 - When we receive a consensus from the future, warn about skew.
23198 - Improve skew reporting: try to give the user a better log message
23199 about how skewed they are, and how much this matters.
23200 - When we have a certificate for an authority, believe that
23201 certificate's claims about the authority's IP address.
23202 - New --quiet command-line option to suppress the default console log.
23203 Good in combination with --hash-password.
23204 - Authorities send back an X-Descriptor-Not-New header in response to
23205 an accepted-but-discarded descriptor upload. Partially implements
23207 - Make the log message for "tls error. breaking." more useful.
23208 - Better log messages about certificate downloads, to attempt to
23209 track down the second incarnation of bug 546.
23211 o Minor features (bridges):
23212 - If bridge users set UpdateBridgesFromAuthority, but the digest
23213 they ask for is a 404 from the bridge authority, they now fall
23214 back to trying the bridge directly.
23215 - Bridges now use begin_dir to publish their server descriptor to
23216 the bridge authority, even when they haven't set TunnelDirConns.
23218 o Minor features (controller):
23219 - When reporting clock skew, and we know that the clock is _at least
23220 as skewed_ as some value, but we don't know the actual value,
23221 report the value as a "minimum skew."
23224 - Update linux-tor-prio.sh script to allow QoS based on the uid of
23225 the Tor process. Patch from Marco Bonetti with tweaks from Mike
23229 - Refuse to start if both ORPort and UseBridges are set. Bugfix
23230 on 0.2.0.x, suggested by Matt Edman.
23231 - Don't stop fetching descriptors when FetchUselessDescriptors is
23232 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
23233 reported by tup and ioerror.
23234 - Better log message on vote from unknown authority.
23235 - Don't log "Launching 0 request for 0 router" message.
23237 o Minor bugfixes (memory leaks):
23238 - Stop leaking memory every time we parse a v3 certificate. Bugfix
23240 - Stop leaking memory every time we load a v3 certificate. Bugfix
23241 on 0.2.0.1-alpha. Fixes bug 536.
23242 - Stop leaking a cached networkstatus on exit. Bugfix on
23244 - Stop leaking voter information every time we free a consensus.
23245 Bugfix on 0.2.0.3-alpha.
23246 - Stop leaking signed data every time we check a voter signature.
23247 Bugfix on 0.2.0.3-alpha.
23248 - Stop leaking a signature every time we fail to parse a consensus or
23249 a vote. Bugfix on 0.2.0.3-alpha.
23250 - Stop leaking v2_download_status_map on shutdown. Bugfix on
23252 - Stop leaking conn->nickname every time we make a connection to a
23253 Tor relay without knowing its expected identity digest (e.g. when
23254 using bridges). Bugfix on 0.2.0.3-alpha.
23256 - Minor bugfixes (portability):
23257 - Run correctly on platforms where rlim_t is larger than unsigned
23258 long, and/or where the real limit for number of open files is
23259 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
23260 particular, these may be needed for OS X 10.5.
23263 Changes in version 0.1.2.18 - 2007-10-28
23264 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
23265 hidden service introduction that were causing huge delays, and a big
23266 bug that was causing some servers to disappear from the network status
23267 lists for a few hours each day.
23269 o Major bugfixes (crashes):
23270 - If a connection is shut down abruptly because of something that
23271 happened inside connection_flushed_some(), do not call
23272 connection_finished_flushing(). Should fix bug 451:
23273 "connection_stop_writing: Assertion conn->write_event failed"
23274 Bugfix on 0.1.2.7-alpha.
23275 - Fix possible segfaults in functions called from
23276 rend_process_relay_cell().
23278 o Major bugfixes (hidden services):
23279 - Hidden services were choosing introduction points uniquely by
23280 hexdigest, but when constructing the hidden service descriptor
23281 they merely wrote the (potentially ambiguous) nickname.
23282 - Clients now use the v2 intro format for hidden service
23283 connections: they specify their chosen rendezvous point by identity
23284 digest rather than by (potentially ambiguous) nickname. These
23285 changes could speed up hidden service connections dramatically.
23287 o Major bugfixes (other):
23288 - Stop publishing a new server descriptor just because we get a
23289 HUP signal. This led (in a roundabout way) to some servers getting
23290 dropped from the networkstatus lists for a few hours each day.
23291 - When looking for a circuit to cannibalize, consider family as well
23292 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
23293 circuit cannibalization).
23294 - When a router wasn't listed in a new networkstatus, we were leaving
23295 the flags for that router alone -- meaning it remained Named,
23296 Running, etc -- even though absence from the networkstatus means
23297 that it shouldn't be considered to exist at all anymore. Now we
23298 clear all the flags for routers that fall out of the networkstatus
23299 consensus. Fixes bug 529.
23302 - Don't try to access (or alter) the state file when running
23303 --list-fingerprint or --verify-config or --hash-password. Resolves
23305 - When generating information telling us how to extend to a given
23306 router, do not try to include the nickname if it is
23307 absent. Resolves bug 467.
23308 - Fix a user-triggerable segfault in expand_filename(). (There isn't
23309 a way to trigger this remotely.)
23310 - When sending a status event to the controller telling it that an
23311 OR address is reachable, set the port correctly. (Previously we
23312 were reporting the dir port.)
23313 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
23314 command. Bugfix on 0.1.2.17.
23315 - When loading bandwidth history, do not believe any information in
23316 the future. Fixes bug 434.
23317 - When loading entry guard information, do not believe any information
23319 - When we have our clock set far in the future and generate an
23320 onion key, then re-set our clock to be correct, we should not stop
23321 the onion key from getting rotated.
23322 - On some platforms, accept() can return a broken address. Detect
23323 this more quietly, and deal accordingly. Fixes bug 483.
23324 - It's not actually an error to find a non-pending entry in the DNS
23325 cache when canceling a pending resolve. Don't log unless stuff
23326 is fishy. Resolves bug 463.
23327 - Don't reset trusted dir server list when we set a configuration
23328 option. Patch from Robert Hogan.
23329 - Don't try to create the datadir when running --verify-config or
23330 --hash-password. Resolves bug 540.
23333 Changes in version 0.2.0.9-alpha - 2007-10-24
23334 This ninth development snapshot switches clients to the new v3 directory
23335 system; allows servers to be listed in the network status even when they
23336 have the same nickname as a registered server; and fixes many other
23337 bugs including a big one that was causing some servers to disappear
23338 from the network status lists for a few hours each day.
23340 o Major features (directory system):
23341 - Clients now download v3 consensus networkstatus documents instead
23342 of v2 networkstatus documents. Clients and caches now base their
23343 opinions about routers on these consensus documents. Clients only
23344 download router descriptors listed in the consensus.
23345 - Authorities now list servers who have the same nickname as
23346 a different named server, but list them with a new flag,
23347 "Unnamed". Now we can list servers that happen to pick the same
23348 nickname as a server that registered two years ago and then
23349 disappeared. Partially implements proposal 122.
23350 - If the consensus lists a router as "Unnamed", the name is assigned
23351 to a different router: do not identify the router by that name.
23352 Partially implements proposal 122.
23353 - Authorities can now come to a consensus on which method to use to
23354 compute the consensus. This gives us forward compatibility.
23357 - Stop publishing a new server descriptor just because we HUP or
23358 when we find our DirPort to be reachable but won't actually publish
23359 it. New descriptors without any real changes are dropped by the
23360 authorities, and can screw up our "publish every 18 hours" schedule.
23362 - When a router wasn't listed in a new networkstatus, we were leaving
23363 the flags for that router alone -- meaning it remained Named,
23364 Running, etc -- even though absence from the networkstatus means
23365 that it shouldn't be considered to exist at all anymore. Now we
23366 clear all the flags for routers that fall out of the networkstatus
23367 consensus. Fixes bug 529; bugfix on 0.1.2.x.
23368 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
23369 extrainfo documents and then discard them immediately for not
23370 matching the latest router. Bugfix on 0.2.0.1-alpha.
23372 o Minor features (v3 directory protocol):
23373 - Allow tor-gencert to generate a new certificate without replacing
23375 - Allow certificates to include an address.
23376 - When we change our directory-cache settings, reschedule all voting
23377 and download operations.
23378 - Reattempt certificate downloads immediately on failure, as long as
23379 we haven't failed a threshold number of times yet.
23380 - Delay retrying consensus downloads while we're downloading
23381 certificates to verify the one we just got. Also, count getting a
23382 consensus that we already have (or one that isn't valid) as a failure,
23383 and count failing to get the certificates after 20 minutes as a
23385 - Build circuits and download descriptors even if our consensus is a
23386 little expired. (This feature will go away once authorities are
23389 o Minor features (router descriptor cache):
23390 - If we find a cached-routers file that's been sitting around for more
23391 than 28 days unmodified, then most likely it's a leftover from
23392 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
23394 - When we (as a cache) download a descriptor because it was listed
23395 in a consensus, remember when the consensus was supposed to expire,
23396 and don't expire the descriptor until then.
23398 o Minor features (performance):
23399 - Call routerlist_remove_old_routers() much less often. This should
23400 speed startup, especially on directory caches.
23401 - Don't try to launch new descriptor downloads quite so often when we
23402 already have enough directory information to build circuits.
23403 - Base64 decoding was actually showing up on our profile when parsing
23404 the initial descriptor file; switch to an in-process all-at-once
23405 implementation that's about 3.5x times faster than calling out to
23408 o Minor features (compilation):
23409 - Detect non-ASCII platforms (if any still exist) and refuse to
23410 build there: some of our code assumes that 'A' is 65 and so on.
23412 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
23413 - Make the "next period" votes into "current period" votes immediately
23414 after publishing the consensus; avoid a heisenbug that made them
23415 stick around indefinitely.
23416 - When we discard a vote as a duplicate, do not report this as
23418 - Treat missing v3 keys or certificates as an error when running as a
23419 v3 directory authority.
23420 - When we're configured to be a v3 authority, but we're only listed
23421 as a non-v3 authority in our DirServer line for ourself, correct
23423 - If an authority doesn't have a qualified hostname, just put
23424 its address in the vote. This fixes the problem where we referred to
23425 "moria on moria:9031."
23426 - Distinguish between detached signatures for the wrong period, and
23427 detached signatures for a divergent vote.
23428 - Fix a small memory leak when computing a consensus.
23429 - When there's no consensus, we were forming a vote every 30
23430 minutes, but writing the "valid-after" line in our vote based
23431 on our configured V3AuthVotingInterval: so unless the intervals
23432 matched up, we immediately rejected our own vote because it didn't
23433 start at the voting interval that caused us to construct a vote.
23435 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
23436 - Delete unverified-consensus when the real consensus is set.
23437 - Consider retrying a consensus networkstatus fetch immediately
23438 after one fails: don't wait 60 seconds to notice.
23439 - When fetching a consensus as a cache, wait until a newer consensus
23440 should exist before trying to replace the current one.
23441 - Use a more forgiving schedule for retrying failed consensus
23442 downloads than for other types.
23444 o Minor bugfixes (other directory issues):
23445 - Correct the implementation of "download votes by digest." Bugfix on
23447 - Authorities no longer send back "400 you're unreachable please fix
23448 it" errors to Tor servers that aren't online all the time. We're
23449 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
23451 o Minor bugfixes (controller):
23452 - Don't reset trusted dir server list when we set a configuration
23453 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
23454 - Respond to INT and TERM SIGNAL commands before we execute the
23455 signal, in case the signal shuts us down. We had a patch in
23456 0.1.2.1-alpha that tried to do this by queueing the response on
23457 the connection's buffer before shutting down, but that really
23458 isn't the same thing at all. Bug located by Matt Edman.
23460 o Minor bugfixes (misc):
23461 - Correctly check for bad options to the "PublishServerDescriptor"
23462 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
23463 - Stop leaking memory on failing case of base32_decode, and make
23464 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
23465 - Don't try to download extrainfo documents when we're trying to
23466 fetch enough directory info to build a circuit: having enough
23467 info should get priority. Bugfix on 0.2.0.x.
23468 - Don't complain that "your server has not managed to confirm that its
23469 ports are reachable" if we haven't been able to build any circuits
23470 yet. Bug found by spending four hours without a v3 consensus. Bugfix
23472 - Detect the reason for failing to mmap a descriptor file we just
23473 wrote, and give a more useful log message. Fixes bug 533. Bugfix
23476 o Code simplifications and refactoring:
23477 - Remove support for the old bw_accounting file: we've been storing
23478 bandwidth accounting information in the state file since
23479 0.1.2.5-alpha. This may result in bandwidth accounting errors
23480 if you try to upgrade from 0.1.1.x or earlier, or if you try to
23481 downgrade to 0.1.1.x or earlier.
23482 - New convenience code to locate a file within the DataDirectory.
23483 - Move non-authority functionality out of dirvote.c.
23484 - Refactor the arguments for router_pick_{directory_|trusteddir}server
23485 so that they all take the same named flags.
23488 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
23489 Unix users an easy way to script their Tor process (e.g. by
23490 adjusting bandwidth based on the time of the day).
23493 Changes in version 0.2.0.8-alpha - 2007-10-12
23494 This eighth development snapshot fixes a crash bug that's been bothering
23495 us since February 2007, lets bridge authorities store a list of bridge
23496 descriptors they've seen, gets v3 directory voting closer to working,
23497 starts caching v3 directory consensus documents on directory mirrors,
23498 and fixes a variety of smaller issues including some minor memory leaks.
23500 o Major features (router descriptor cache):
23501 - Store routers in a file called cached-descriptors instead of in
23502 cached-routers. Initialize cached-descriptors from cached-routers
23503 if the old format is around. The new format allows us to store
23504 annotations along with descriptors.
23505 - Use annotations to record the time we received each descriptor, its
23506 source, and its purpose.
23507 - Disable the SETROUTERPURPOSE controller command: it is now
23509 - Controllers should now specify cache=no or cache=yes when using
23510 the +POSTDESCRIPTOR command.
23511 - Bridge authorities now write bridge descriptors to disk, meaning
23512 we can export them to other programs and begin distributing them
23515 o Major features (directory authorities):
23516 - When a v3 authority is missing votes or signatures, it now tries
23518 - Directory authorities track weighted fractional uptime as well as
23519 weighted mean-time-between failures. WFU is suitable for deciding
23520 whether a node is "usually up", while MTBF is suitable for deciding
23521 whether a node is "likely to stay up." We need both, because
23522 "usually up" is a good requirement for guards, while "likely to
23523 stay up" is a good requirement for long-lived connections.
23525 o Major features (v3 directory system):
23526 - Caches now download v3 network status documents as needed,
23527 and download the descriptors listed in them.
23528 - All hosts now attempt to download and keep fresh v3 authority
23529 certificates, and re-attempt after failures.
23530 - More internal-consistency checks for vote parsing.
23532 o Major bugfixes (crashes):
23533 - If a connection is shut down abruptly because of something that
23534 happened inside connection_flushed_some(), do not call
23535 connection_finished_flushing(). Should fix bug 451. Bugfix on
23538 o Major bugfixes (performance):
23539 - Fix really bad O(n^2) performance when parsing a long list of
23540 routers: Instead of searching the entire list for an "extra-info "
23541 string which usually wasn't there, once for every routerinfo
23542 we read, just scan lines forward until we find one we like.
23544 - When we add data to a write buffer in response to the data on that
23545 write buffer getting low because of a flush, do not consider the
23546 newly added data as a candidate for immediate flushing, but rather
23547 make it wait until the next round of writing. Otherwise, we flush
23548 and refill recursively, and a single greedy TLS connection can
23549 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
23551 o Minor features (v3 authority system):
23552 - Add more ways for tools to download the votes that lead to the
23554 - Send a 503 when low on bandwidth and a vote, consensus, or
23555 certificate is requested.
23556 - If-modified-since is now implemented properly for all kinds of
23557 certificate requests.
23559 o Minor bugfixes (network statuses):
23560 - Tweak the implementation of proposal 109 slightly: allow at most
23561 two Tor servers on the same IP address, except if it's the location
23562 of a directory authority, in which case allow five. Bugfix on
23565 o Minor bugfixes (controller):
23566 - When sending a status event to the controller telling it that an
23567 OR address is reachable, set the port correctly. (Previously we
23568 were reporting the dir port.) Bugfix on 0.1.2.x.
23570 o Minor bugfixes (v3 directory system):
23571 - Fix logic to look up a cert by its signing key digest. Bugfix on
23573 - Only change the reply to a vote to "OK" if it's not already
23574 set. This gets rid of annoying "400 OK" log messages, which may
23575 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
23576 - When we get a valid consensus, recompute the voting schedule.
23577 - Base the valid-after time of a vote on the consensus voting
23578 schedule, not on our preferred schedule.
23579 - Make the return values and messages from signature uploads and
23580 downloads more sensible.
23581 - Fix a memory leak when serving votes and consensus documents, and
23582 another when serving certificates.
23584 o Minor bugfixes (performance):
23585 - Use a slightly simpler string hashing algorithm (copying Python's
23586 instead of Java's) and optimize our digest hashing algorithm to take
23587 advantage of 64-bit platforms and to remove some possibly-costly
23589 - Fix a minor memory leak whenever we parse guards from our state
23590 file. Bugfix on 0.2.0.7-alpha.
23591 - Fix a minor memory leak whenever we write out a file. Bugfix on
23593 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
23594 command. Bugfix on 0.2.0.5-alpha.
23596 o Minor bugfixes (portability):
23597 - On some platforms, accept() can return a broken address. Detect
23598 this more quietly, and deal accordingly. Fixes bug 483.
23599 - Stop calling tor_strlower() on uninitialized memory in some cases.
23600 Bugfix in 0.2.0.7-alpha.
23602 o Minor bugfixes (usability):
23603 - Treat some 403 responses from directory servers as INFO rather than
23604 WARN-severity events.
23605 - It's not actually an error to find a non-pending entry in the DNS
23606 cache when canceling a pending resolve. Don't log unless stuff is
23607 fishy. Resolves bug 463.
23609 o Minor bugfixes (anonymity):
23610 - Never report that we've used more bandwidth than we're willing to
23611 relay: it leaks how much non-relay traffic we're using. Resolves
23613 - When looking for a circuit to cannibalize, consider family as well
23614 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
23615 circuit cannibalization).
23617 o Code simplifications and refactoring:
23618 - Make a bunch of functions static. Remove some dead code.
23619 - Pull out about a third of the really big routerlist.c; put it in a
23620 new module, networkstatus.c.
23621 - Merge the extra fields in local_routerstatus_t back into
23622 routerstatus_t: we used to need one routerstatus_t for each
23623 authority's opinion, plus a local_routerstatus_t for the locally
23624 computed consensus opinion. To save space, we put the locally
23625 modified fields into local_routerstatus_t, and only the common
23626 stuff into routerstatus_t. But once v3 directories are in use,
23627 clients and caches will no longer need to hold authority opinions;
23628 thus, the rationale for keeping the types separate is now gone.
23629 - Make the code used to reschedule and reattempt downloads more
23631 - Turn all 'Are we a directory server/mirror?' logic into a call to
23633 - Remove the code to generate the oldest (v1) directory format.
23634 The code has been disabled since 0.2.0.5-alpha.
23637 Changes in version 0.2.0.7-alpha - 2007-09-21
23638 This seventh development snapshot makes bridges work again, makes bridge
23639 authorities work for the first time, fixes two huge performance flaws
23640 in hidden services, and fixes a variety of minor issues.
23642 o New directory authorities:
23643 - Set up moria1 and tor26 as the first v3 directory authorities. See
23644 doc/spec/dir-spec.txt for details on the new directory design.
23646 o Major bugfixes (crashes):
23647 - Fix possible segfaults in functions called from
23648 rend_process_relay_cell(). Bugfix on 0.1.2.x.
23650 o Major bugfixes (bridges):
23651 - Fix a bug that made servers send a "404 Not found" in response to
23652 attempts to fetch their server descriptor. This caused Tor servers
23653 to take many minutes to establish reachability for their DirPort,
23654 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
23655 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
23656 users configure that and specify a bridge with an identity
23657 fingerprint, now they will lookup the bridge descriptor at the
23658 default bridge authority via a one-hop tunnel, but once circuits
23659 are established they will switch to a three-hop tunnel for later
23660 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
23662 o Major bugfixes (hidden services):
23663 - Hidden services were choosing introduction points uniquely by
23664 hexdigest, but when constructing the hidden service descriptor
23665 they merely wrote the (potentially ambiguous) nickname.
23666 - Clients now use the v2 intro format for hidden service
23667 connections: they specify their chosen rendezvous point by identity
23668 digest rather than by (potentially ambiguous) nickname. Both
23669 are bugfixes on 0.1.2.x, and they could speed up hidden service
23670 connections dramatically. Thanks to Karsten Loesing.
23672 o Minor features (security):
23673 - As a client, do not believe any server that tells us that an
23674 address maps to an internal address space.
23675 - Make it possible to enable HashedControlPassword and
23676 CookieAuthentication at the same time.
23678 o Minor features (guard nodes):
23679 - Tag every guard node in our state file with the version that
23680 we believe added it, or with our own version if we add it. This way,
23681 if a user temporarily runs an old version of Tor and then switches
23682 back to a new one, she doesn't automatically lose her guards.
23684 o Minor features (speed):
23685 - When implementing AES counter mode, update only the portions of the
23686 counter buffer that need to change, and don't keep separate
23687 network-order and host-order counters when they are the same (i.e.,
23688 on big-endian hosts.)
23690 o Minor features (controller):
23691 - Accept LF instead of CRLF on controller, since some software has a
23692 hard time generating real Internet newlines.
23693 - Add GETINFO values for the server status events
23694 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
23697 o Removed features:
23698 - Routers no longer include bandwidth-history lines in their
23699 descriptors; this information is already available in extra-info
23700 documents, and including it in router descriptors took up 60%
23701 (!) of compressed router descriptor downloads. Completes
23702 implementation of proposal 104.
23703 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
23704 and TorControl.py, as they use the old v0 controller protocol,
23705 and are obsoleted by TorFlow anyway.
23706 - Drop support for v1 rendezvous descriptors, since we never used
23707 them anyway, and the code has probably rotted by now. Based on
23708 patch from Karsten Loesing.
23709 - On OSX, stop warning the user that kqueue support in libevent is
23710 "experimental", since it seems to have worked fine for ages.
23713 - When generating information telling us how to extend to a given
23714 router, do not try to include the nickname if it is absent. Fixes
23715 bug 467. Bugfix on 0.2.0.3-alpha.
23716 - Fix a user-triggerable (but not remotely-triggerable) segfault
23717 in expand_filename(). Bugfix on 0.1.2.x.
23718 - Fix a memory leak when freeing incomplete requests from DNSPort.
23719 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
23720 - Don't try to access (or alter) the state file when running
23721 --list-fingerprint or --verify-config or --hash-password. (Resolves
23722 bug 499.) Bugfix on 0.1.2.x.
23723 - Servers used to decline to publish their DirPort if their
23724 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
23725 were below a threshold. Now they only look at BandwidthRate and
23726 RelayBandwidthRate. Bugfix on 0.1.2.x.
23727 - Remove an optimization in the AES counter-mode code that assumed
23728 that the counter never exceeded 2^68. When the counter can be set
23729 arbitrarily as an IV (as it is by Karsten's new hidden services
23730 code), this assumption no longer holds. Bugfix on 0.1.2.x.
23731 - Resume listing "AUTHORITY" flag for authorities in network status.
23732 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
23734 o Code simplifications and refactoring:
23735 - Revamp file-writing logic so we don't need to have the entire
23736 contents of a file in memory at once before we write to disk. Tor,
23738 - Turn "descriptor store" into a full-fledged type.
23739 - Move all NT services code into a separate source file.
23740 - Unify all code that computes medians, percentile elements, etc.
23741 - Get rid of a needless malloc when parsing address policies.
23744 Changes in version 0.1.2.17 - 2007-08-30
23745 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
23746 X bundles. Vidalia 0.0.14 makes authentication required for the
23747 ControlPort in the default configuration, which addresses important
23748 security risks. Everybody who uses Vidalia (or another controller)
23751 In addition, this Tor update fixes major load balancing problems with
23752 path selection, which should speed things up a lot once many people
23755 o Major bugfixes (security):
23756 - We removed support for the old (v0) control protocol. It has been
23757 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
23758 become more of a headache than it's worth.
23760 o Major bugfixes (load balancing):
23761 - When choosing nodes for non-guard positions, weight guards
23762 proportionally less, since they already have enough load. Patch
23764 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
23765 will allow fast Tor servers to get more attention.
23766 - When we're upgrading from an old Tor version, forget our current
23767 guards and pick new ones according to the new weightings. These
23768 three load balancing patches could raise effective network capacity
23769 by a factor of four. Thanks to Mike Perry for measurements.
23771 o Major bugfixes (stream expiration):
23772 - Expire not-yet-successful application streams in all cases if
23773 they've been around longer than SocksTimeout. Right now there are
23774 some cases where the stream will live forever, demanding a new
23775 circuit every 15 seconds. Fixes bug 454; reported by lodger.
23777 o Minor features (controller):
23778 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
23779 is valid before any authentication has been received. It tells
23780 a controller what kind of authentication is expected, and what
23781 protocol is spoken. Implements proposal 119.
23783 o Minor bugfixes (performance):
23784 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
23785 greatly speeding up loading cached-routers from disk on startup.
23786 - Disable sentinel-based debugging for buffer code: we squashed all
23787 the bugs that this was supposed to detect a long time ago, and now
23788 its only effect is to change our buffer sizes from nice powers of
23789 two (which platform mallocs tend to like) to values slightly over
23790 powers of two (which make some platform mallocs sad).
23792 o Minor bugfixes (misc):
23793 - If exit bandwidth ever exceeds one third of total bandwidth, then
23794 use the correct formula to weight exit nodes when choosing paths.
23795 Based on patch from Mike Perry.
23796 - Choose perfectly fairly among routers when choosing by bandwidth and
23797 weighting by fraction of bandwidth provided by exits. Previously, we
23798 would choose with only approximate fairness, and correct ourselves
23799 if we ran off the end of the list.
23800 - If we require CookieAuthentication but we fail to write the
23801 cookie file, we would warn but not exit, and end up in a state
23802 where no controller could authenticate. Now we exit.
23803 - If we require CookieAuthentication, stop generating a new cookie
23804 every time we change any piece of our config.
23805 - Refuse to start with certain directory authority keys, and
23806 encourage people using them to stop.
23807 - Terminate multi-line control events properly. Original patch
23809 - Fix a minor memory leak when we fail to find enough suitable
23810 servers to choose a circuit.
23811 - Stop leaking part of the descriptor when we run into a particularly
23812 unparseable piece of it.
23815 Changes in version 0.2.0.6-alpha - 2007-08-26
23816 This sixth development snapshot features a new Vidalia version in the
23817 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
23818 the ControlPort in the default configuration, which addresses important
23821 In addition, this snapshot fixes major load balancing problems
23822 with path selection, which should speed things up a lot once many
23823 people have upgraded. The directory authorities also use a new
23824 mean-time-between-failure approach to tracking which servers are stable,
23825 rather than just looking at the most recent uptime.
23827 o New directory authorities:
23828 - Set up Tonga as the default bridge directory authority.
23831 - Directory authorities now track servers by weighted
23832 mean-times-between-failures. When we have 4 or more days of data,
23833 use measured MTBF rather than declared uptime to decide whether
23834 to call a router Stable. Implements proposal 108.
23836 o Major bugfixes (load balancing):
23837 - When choosing nodes for non-guard positions, weight guards
23838 proportionally less, since they already have enough load. Patch
23840 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
23841 will allow fast Tor servers to get more attention.
23842 - When we're upgrading from an old Tor version, forget our current
23843 guards and pick new ones according to the new weightings. These
23844 three load balancing patches could raise effective network capacity
23845 by a factor of four. Thanks to Mike Perry for measurements.
23847 o Major bugfixes (descriptor parsing):
23848 - Handle unexpected whitespace better in malformed descriptors. Bug
23849 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
23852 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
23853 GETINFO for Torstat to use until it can switch to using extrainfos.
23854 - Optionally (if built with -DEXPORTMALLINFO) export the output
23855 of mallinfo via http, as tor/mallinfo.txt. Only accessible
23859 - Do not intermix bridge routers with controller-added
23860 routers. (Bugfix on 0.2.0.x)
23861 - Do not fail with an assert when accept() returns an unexpected
23862 address family. Addresses but does not wholly fix bug 483. (Bugfix
23864 - Let directory authorities startup even when they can't generate
23865 a descriptor immediately, e.g. because they don't know their
23867 - Stop putting the authentication cookie in a file called "0"
23868 in your working directory if you don't specify anything for the
23869 new CookieAuthFile option. Reported by Matt Edman.
23870 - Make it possible to read the PROTOCOLINFO response in a way that
23871 conforms to our control-spec. Reported by Matt Edman.
23872 - Fix a minor memory leak when we fail to find enough suitable
23873 servers to choose a circuit. Bugfix on 0.1.2.x.
23874 - Stop leaking part of the descriptor when we run into a particularly
23875 unparseable piece of it. Bugfix on 0.1.2.x.
23876 - Unmap the extrainfo cache file on exit.
23879 Changes in version 0.2.0.5-alpha - 2007-08-19
23880 This fifth development snapshot fixes compilation on Windows again;
23881 fixes an obnoxious client-side bug that slowed things down and put
23882 extra load on the network; gets us closer to using the v3 directory
23883 voting scheme; makes it easier for Tor controllers to use cookie-based
23884 authentication; and fixes a variety of other bugs.
23886 o Removed features:
23887 - Version 1 directories are no longer generated in full. Instead,
23888 authorities generate and serve "stub" v1 directories that list
23889 no servers. This will stop Tor versions 0.1.0.x and earlier from
23890 working, but (for security reasons) nobody should be running those
23893 o Major bugfixes (compilation, 0.2.0.x):
23894 - Try to fix Win32 compilation again: improve checking for IPv6 types.
23895 - Try to fix MSVC compilation: build correctly on platforms that do
23896 not define s6_addr16 or s6_addr32.
23897 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
23900 o Major bugfixes (stream expiration):
23901 - Expire not-yet-successful application streams in all cases if
23902 they've been around longer than SocksTimeout. Right now there are
23903 some cases where the stream will live forever, demanding a new
23904 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
23905 reported by lodger.
23907 o Minor features (directory servers):
23908 - When somebody requests a list of statuses or servers, and we have
23909 none of those, return a 404 rather than an empty 200.
23911 o Minor features (directory voting):
23912 - Store v3 consensus status consensuses on disk, and reload them
23915 o Minor features (security):
23916 - Warn about unsafe ControlPort configurations.
23917 - Refuse to start with certain directory authority keys, and
23918 encourage people using them to stop.
23920 o Minor features (controller):
23921 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
23922 is valid before any authentication has been received. It tells
23923 a controller what kind of authentication is expected, and what
23924 protocol is spoken. Implements proposal 119.
23925 - New config option CookieAuthFile to choose a new location for the
23926 cookie authentication file, and config option
23927 CookieAuthFileGroupReadable to make it group-readable.
23929 o Minor features (unit testing):
23930 - Add command-line arguments to unit-test executable so that we can
23931 invoke any chosen test from the command line rather than having
23932 to run the whole test suite at once; and so that we can turn on
23933 logging for the unit tests.
23935 o Minor bugfixes (on 0.1.2.x):
23936 - If we require CookieAuthentication but we fail to write the
23937 cookie file, we would warn but not exit, and end up in a state
23938 where no controller could authenticate. Now we exit.
23939 - If we require CookieAuthentication, stop generating a new cookie
23940 every time we change any piece of our config.
23941 - When loading bandwidth history, do not believe any information in
23942 the future. Fixes bug 434.
23943 - When loading entry guard information, do not believe any information
23945 - When we have our clock set far in the future and generate an
23946 onion key, then re-set our clock to be correct, we should not stop
23947 the onion key from getting rotated.
23948 - Clean up torrc sample config file.
23949 - Do not automatically run configure from autogen.sh. This
23950 non-standard behavior tended to annoy people who have built other
23953 o Minor bugfixes (on 0.2.0.x):
23954 - Fix a bug with AutomapHostsOnResolve that would always cause
23955 the second request to fail. Bug reported by Kate. Bugfix on
23957 - Fix a bug in ADDRMAP controller replies that would sometimes
23958 try to print a NULL. Patch from tup.
23959 - Read v3 directory authority keys from the right location.
23960 - Numerous bugfixes to directory voting code.
23963 Changes in version 0.1.2.16 - 2007-08-01
23964 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
23965 remote attacker in certain situations to rewrite the user's torrc
23966 configuration file. This can completely compromise anonymity of users
23967 in most configurations, including those running the Vidalia bundles,
23968 TorK, etc. Or worse.
23970 o Major security fixes:
23971 - Close immediately after missing authentication on control port;
23972 do not allow multiple authentication attempts.
23975 Changes in version 0.2.0.4-alpha - 2007-08-01
23976 This fourth development snapshot fixes a critical security vulnerability
23977 for most users, specifically those running Vidalia, TorK, etc. Everybody
23978 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
23980 o Major security fixes:
23981 - Close immediately after missing authentication on control port;
23982 do not allow multiple authentication attempts.
23984 o Major bugfixes (compilation):
23985 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
23988 o Minor features (performance):
23989 - Be even more aggressive about releasing RAM from small
23990 empty buffers. Thanks to our free-list code, this shouldn't be too
23991 performance-intensive.
23992 - Disable sentinel-based debugging for buffer code: we squashed all
23993 the bugs that this was supposed to detect a long time ago, and
23994 now its only effect is to change our buffer sizes from nice
23995 powers of two (which platform mallocs tend to like) to values
23996 slightly over powers of two (which make some platform mallocs sad).
23997 - Log malloc statistics from mallinfo() on platforms where it
24001 Changes in version 0.2.0.3-alpha - 2007-07-29
24002 This third development snapshot introduces new experimental
24003 blocking-resistance features and a preliminary version of the v3
24004 directory voting design, and includes many other smaller features
24008 - The first pieces of our "bridge" design for blocking-resistance
24009 are implemented. People can run bridge directory authorities;
24010 people can run bridges; and people can configure their Tor clients
24011 with a set of bridges to use as the first hop into the Tor network.
24012 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
24014 - Create listener connections before we setuid to the configured
24015 User and Group. Now non-Windows users can choose port values
24016 under 1024, start Tor as root, and have Tor bind those ports
24017 before it changes to another UID. (Windows users could already
24019 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
24020 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
24021 on "vserver" accounts. (Patch from coderman.)
24022 - Be even more aggressive about separating local traffic from relayed
24023 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
24025 o Major features (experimental):
24026 - First cut of code for "v3 dir voting": directory authorities will
24027 vote on a common network status document rather than each publishing
24028 their own opinion. This code needs more testing and more corner-case
24029 handling before it's ready for use.
24032 - Directory authorities now call routers Fast if their bandwidth is
24033 at least 100KB/s, and consider their bandwidth adequate to be a
24034 Guard if it is at least 250KB/s, no matter the medians. This fix
24035 complements proposal 107. [Bugfix on 0.1.2.x]
24036 - Directory authorities now never mark more than 3 servers per IP as
24037 Valid and Running. (Implements proposal 109, by Kevin Bauer and
24039 - Minor change to organizationName and commonName generation
24040 procedures in TLS certificates during Tor handshakes, to invalidate
24041 some earlier censorware approaches. This is not a long-term
24042 solution, but applying it will give us a bit of time to look into
24043 the epidemiology of countermeasures as they spread.
24045 o Major bugfixes (directory):
24046 - Rewrite directory tokenization code to never run off the end of
24047 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
24049 o Minor features (controller):
24050 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
24051 match requests to applications. (Patch from Robert Hogan.)
24052 - Report address and port correctly on connections to DNSPort. (Patch
24053 from Robert Hogan.)
24054 - Add a RESOLVE command to launch hostname lookups. (Original patch
24055 from Robert Hogan.)
24056 - Add GETINFO status/enough-dir-info to let controllers tell whether
24057 Tor has downloaded sufficient directory information. (Patch
24059 - You can now use the ControlSocket option to tell Tor to listen for
24060 controller connections on Unix domain sockets on systems that
24061 support them. (Patch from Peter Palfrader.)
24062 - STREAM NEW events are generated for DNSPort requests and for
24063 tunneled directory connections. (Patch from Robert Hogan.)
24064 - New "GETINFO address-mappings/*" command to get address mappings
24065 with expiry information. "addr-mappings/*" is now deprecated.
24068 o Minor features (misc):
24069 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
24071 - The tor-gencert tool for v3 directory authorities now creates all
24072 files as readable to the file creator only, and write-protects
24073 the authority identity key.
24074 - When dumping memory usage, list bytes used in buffer memory
24076 - When running with dmalloc, dump more stats on hup and on exit.
24077 - Directory authorities now fail quickly and (relatively) harmlessly
24078 if they generate a network status document that is somehow
24081 o Traffic load balancing improvements:
24082 - If exit bandwidth ever exceeds one third of total bandwidth, then
24083 use the correct formula to weight exit nodes when choosing paths.
24084 (Based on patch from Mike Perry.)
24085 - Choose perfectly fairly among routers when choosing by bandwidth and
24086 weighting by fraction of bandwidth provided by exits. Previously, we
24087 would choose with only approximate fairness, and correct ourselves
24088 if we ran off the end of the list. [Bugfix on 0.1.2.x]
24090 o Performance improvements:
24091 - Be more aggressive with freeing buffer RAM or putting it on the
24093 - Use Critical Sections rather than Mutexes for synchronizing threads
24094 on win32; Mutexes are heavier-weight, and designed for synchronizing
24097 o Deprecated and removed features:
24098 - RedirectExits is now deprecated.
24099 - Stop allowing address masks that do not correspond to bit prefixes.
24100 We have warned about these for a really long time; now it's time
24101 to reject them. (Patch from croup.)
24103 o Minor bugfixes (directory):
24104 - Fix another crash bug related to extra-info caching. (Bug found by
24105 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
24106 - Directories no longer return a "304 not modified" when they don't
24107 have the networkstatus the client asked for. Also fix a memory
24108 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
24109 - We had accidentally labelled 0.1.2.x directory servers as not
24110 suitable for begin_dir requests, and had labelled no directory
24111 servers as suitable for uploading extra-info documents. [Bugfix
24114 o Minor bugfixes (dns):
24115 - Fix a crash when DNSPort is set more than once. (Patch from Robert
24116 Hogan.) [Bugfix on 0.2.0.2-alpha]
24117 - Add DNSPort connections to the global connection list, so that we
24118 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
24120 - Fix a dangling reference that could lead to a crash when DNSPort is
24121 changed or closed (Patch from Robert Hogan.) [Bugfix on
24124 o Minor bugfixes (controller):
24125 - Provide DNS expiry times in GMT, not in local time. For backward
24126 compatibility, ADDRMAP events only provide GMT expiry in an extended
24127 field. "GETINFO address-mappings" always does the right thing.
24128 - Use CRLF line endings properly in NS events.
24129 - Terminate multi-line control events properly. (Original patch
24130 from tup.) [Bugfix on 0.1.2.x-alpha]
24131 - Do not include spaces in SOURCE_ADDR fields in STREAM
24132 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
24135 Changes in version 0.1.2.15 - 2007-07-17
24136 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
24137 problems, fixes compilation on BSD, and fixes a variety of other
24138 bugs. Everybody should upgrade.
24140 o Major bugfixes (compilation):
24141 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
24143 o Major bugfixes (crashes):
24144 - Try even harder not to dereference the first character after
24145 an mmap(). Reported by lodger.
24146 - Fix a crash bug in directory authorities when we re-number the
24147 routerlist while inserting a new router.
24148 - When the cached-routers file is an even multiple of the page size,
24149 don't run off the end and crash. (Fixes bug 455; based on idea
24151 - Fix eventdns.c behavior on Solaris: It is critical to include
24152 orconfig.h _before_ sys/types.h, so that we can get the expected
24153 definition of _FILE_OFFSET_BITS.
24155 o Major bugfixes (security):
24156 - Fix a possible buffer overrun when using BSD natd support. Bug
24158 - When sending destroy cells from a circuit's origin, don't include
24159 the reason for tearing down the circuit. The spec says we didn't,
24160 and now we actually don't. Reported by lodger.
24161 - Keep streamids from different exits on a circuit separate. This
24162 bug may have allowed other routers on a given circuit to inject
24163 cells into streams. Reported by lodger; fixes bug 446.
24164 - If there's a never-before-connected-to guard node in our list,
24165 never choose any guards past it. This way we don't expand our
24166 guard list unless we need to.
24168 o Minor bugfixes (guard nodes):
24169 - Weight guard selection by bandwidth, so that low-bandwidth nodes
24170 don't get overused as guards.
24172 o Minor bugfixes (directory):
24173 - Correctly count the number of authorities that recommend each
24174 version. Previously, we were under-counting by 1.
24175 - Fix a potential crash bug when we load many server descriptors at
24176 once and some of them make others of them obsolete. Fixes bug 458.
24178 o Minor bugfixes (hidden services):
24179 - Stop tearing down the whole circuit when the user asks for a
24180 connection to a port that the hidden service didn't configure.
24183 o Minor bugfixes (misc):
24184 - On Windows, we were preventing other processes from reading
24185 cached-routers while Tor was running. Reported by janbar.
24186 - Fix a possible (but very unlikely) bug in picking routers by
24187 bandwidth. Add a log message to confirm that it is in fact
24188 unlikely. Patch from lodger.
24189 - Backport a couple of memory leak fixes.
24190 - Backport miscellaneous cosmetic bugfixes.
24193 Changes in version 0.2.0.2-alpha - 2007-06-02
24194 o Major bugfixes on 0.2.0.1-alpha:
24195 - Fix an assertion failure related to servers without extra-info digests.
24196 Resolves bugs 441 and 442.
24198 o Minor features (directory):
24199 - Support "If-Modified-Since" when answering HTTP requests for
24200 directories, running-routers documents, and network-status documents.
24201 (There's no need to support it for router descriptors, since those
24202 are downloaded by descriptor digest.)
24204 o Minor build issues:
24205 - Clear up some MIPSPro compiler warnings.
24206 - When building from a tarball on a machine that happens to have SVK
24207 installed, report the micro-revision as whatever version existed
24208 in the tarball, not as "x".
24211 Changes in version 0.2.0.1-alpha - 2007-06-01
24212 This early development snapshot provides new features for people running
24213 Tor as both a client and a server (check out the new RelayBandwidth
24214 config options); lets Tor run as a DNS proxy; and generally moves us
24215 forward on a lot of fronts.
24217 o Major features, server usability:
24218 - New config options RelayBandwidthRate and RelayBandwidthBurst:
24219 a separate set of token buckets for relayed traffic. Right now
24220 relayed traffic is defined as answers to directory requests, and
24221 OR connections that don't have any local circuits on them.
24223 o Major features, client usability:
24224 - A client-side DNS proxy feature to replace the need for
24225 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
24226 for DNS requests on port 9999, use the Tor network to resolve them
24227 anonymously, and send the reply back like a regular DNS server.
24228 The code still only implements a subset of DNS.
24229 - Make PreferTunneledDirConns and TunnelDirConns work even when
24230 we have no cached directory info. This means Tor clients can now
24231 do all of their connections protected by TLS.
24233 o Major features, performance and efficiency:
24234 - Directory authorities accept and serve "extra info" documents for
24235 routers. These documents contain fields from router descriptors
24236 that aren't usually needed, and that use a lot of excess
24237 bandwidth. Once these fields are removed from router descriptors,
24238 the bandwidth savings should be about 60%. [Partially implements
24240 - Servers upload extra-info documents to any authority that accepts
24241 them. Authorities (and caches that have been configured to download
24242 extra-info documents) download them as needed. [Partially implements
24244 - Change the way that Tor buffers data that it is waiting to write.
24245 Instead of queueing data cells in an enormous ring buffer for each
24246 client->OR or OR->OR connection, we now queue cells on a separate
24247 queue for each circuit. This lets us use less slack memory, and
24248 will eventually let us be smarter about prioritizing different kinds
24250 - Use memory pools to allocate cells with better speed and memory
24251 efficiency, especially on platforms where malloc() is inefficient.
24252 - Stop reading on edge connections when their corresponding circuit
24253 buffers are full; start again as the circuits empty out.
24255 o Major features, other:
24256 - Add an HSAuthorityRecordStats option that hidden service authorities
24257 can use to track statistics of overall hidden service usage without
24258 logging information that would be very useful to an attacker.
24259 - Start work implementing multi-level keys for directory authorities:
24260 Add a standalone tool to generate key certificates. (Proposal 103.)
24263 - Directory authorities now call routers Stable if they have an
24264 uptime of at least 30 days, even if that's not the median uptime
24265 in the network. Implements proposal 107, suggested by Kevin Bauer
24268 o Minor fixes (resource management):
24269 - Count the number of open sockets separately from the number
24270 of active connection_t objects. This will let us avoid underusing
24271 our allocated connection limit.
24272 - We no longer use socket pairs to link an edge connection to an
24273 anonymous directory connection or a DirPort test connection.
24274 Instead, we track the link internally and transfer the data
24275 in-process. This saves two sockets per "linked" connection (at the
24276 client and at the server), and avoids the nasty Windows socketpair()
24278 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
24279 for every single inactive connection_t. Free items from the
24280 4k/16k-buffer free lists when they haven't been used for a while.
24282 o Minor features (build):
24283 - Make autoconf search for libevent, openssl, and zlib consistently.
24284 - Update deprecated macros in configure.in.
24285 - When warning about missing headers, tell the user to let us
24286 know if the compile succeeds anyway, so we can downgrade the
24288 - Include the current subversion revision as part of the version
24289 string: either fetch it directly if we're in an SVN checkout, do
24290 some magic to guess it if we're in an SVK checkout, or use
24291 the last-detected version if we're building from a .tar.gz.
24292 Use this version consistently in log messages.
24294 o Minor features (logging):
24295 - Always prepend "Bug: " to any log message about a bug.
24296 - Put a platform string (e.g. "Linux i686") in the startup log
24297 message, so when people paste just their logs, we know if it's
24298 OpenBSD or Windows or what.
24299 - When logging memory usage, break down memory used in buffers by
24302 o Minor features (directory system):
24303 - New config option V2AuthoritativeDirectory that all directory
24304 authorities should set. This will let future authorities choose
24305 not to serve V2 directory information.
24306 - Directory authorities allow multiple router descriptors and/or extra
24307 info documents to be uploaded in a single go. This will make
24308 implementing proposal 104 simpler.
24310 o Minor features (controller):
24311 - Add a new config option __DisablePredictedCircuits designed for
24312 use by the controller, when we don't want Tor to build any circuits
24314 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
24315 so we can exit from the middle of the circuit.
24316 - Implement "getinfo status/circuit-established".
24317 - Implement "getinfo status/version/..." so a controller can tell
24318 whether the current version is recommended, and whether any versions
24319 are good, and how many authorities agree. (Patch from shibz.)
24321 o Minor features (hidden services):
24322 - Allow multiple HiddenServicePort directives with the same virtual
24323 port; when they occur, the user is sent round-robin to one
24324 of the target ports chosen at random. Partially fixes bug 393 by
24325 adding limited ad-hoc round-robining.
24327 o Minor features (other):
24329 - Add a new AutomapHostsOnResolve option: when it is enabled, any
24330 resolve request for hosts matching a given pattern causes Tor to
24331 generate an internal virtual address mapping for that host. This
24332 allows DNSPort to work sensibly with hidden service users. By
24333 default, .exit and .onion addresses are remapped; the list of
24334 patterns can be reconfigured with AutomapHostsSuffixes.
24335 - Add an "-F" option to tor-resolve to force a resolve for a .onion
24336 address. Thanks to the AutomapHostsOnResolve option, this is no
24337 longer a completely silly thing to do.
24338 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
24339 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
24340 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
24341 minus 1 byte: the actual maximum declared bandwidth.
24343 o Removed features:
24344 - Removed support for the old binary "version 0" controller protocol.
24345 This has been deprecated since 0.1.1, and warnings have been issued
24346 since 0.1.2. When we encounter a v0 control message, we now send
24347 back an error and close the connection.
24348 - Remove the old "dns worker" server DNS code: it hasn't been default
24349 since 0.1.2.2-alpha, and all the servers seem to be using the new
24352 o Minor bugfixes (portability):
24353 - Even though Windows is equally happy with / and \ as path separators,
24354 try to use \ consistently on Windows and / consistently on Unix: it
24355 makes the log messages nicer.
24356 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
24357 - Read resolv.conf files correctly on platforms where read() returns
24358 partial results on small file reads.
24360 o Minor bugfixes (directory):
24361 - Correctly enforce that elements of directory objects do not appear
24362 more often than they are allowed to appear.
24363 - When we are reporting the DirServer line we just parsed, we were
24364 logging the second stanza of the key fingerprint, not the first.
24366 o Minor bugfixes (logging):
24367 - When we hit an EOF on a log (probably because we're shutting down),
24368 don't try to remove the log from the list: just mark it as
24369 unusable. (Bulletproofs against bug 222.)
24371 o Minor bugfixes (other):
24372 - In the exitlist script, only consider the most recently published
24373 server descriptor for each server. Also, when the user requests
24374 a list of servers that _reject_ connections to a given address,
24375 explicitly exclude the IPs that also have servers that accept
24376 connections to that address. (Resolves bug 405.)
24377 - Stop allowing hibernating servers to be "stable" or "fast".
24378 - On Windows, we were preventing other processes from reading
24379 cached-routers while Tor was running. (Reported by janbar)
24380 - Make the NodeFamilies config option work. (Reported by
24381 lodger -- it has never actually worked, even though we added it
24383 - Check return values from pthread_mutex functions.
24384 - Don't save non-general-purpose router descriptors to the disk cache,
24385 because we have no way of remembering what their purpose was when
24387 - Add even more asserts to hunt down bug 417.
24388 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
24389 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
24390 Add a log message to confirm that it is in fact unlikely.
24392 o Minor bugfixes (controller):
24393 - Make 'getinfo fingerprint' return a 551 error if we're not a
24394 server, so we match what the control spec claims we do. Reported
24396 - Fix a typo in an error message when extendcircuit fails that
24397 caused us to not follow the \r\n-based delimiter protocol. Reported
24400 o Code simplifications and refactoring:
24401 - Stop passing around circuit_t and crypt_path_t pointers that are
24402 implicit in other procedure arguments.
24403 - Drop the old code to choke directory connections when the
24404 corresponding OR connections got full: thanks to the cell queue
24405 feature, OR conns don't get full any more.
24406 - Make dns_resolve() handle attaching connections to circuits
24407 properly, so the caller doesn't have to.
24408 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
24409 - Keep the connection array as a dynamic smartlist_t, rather than as
24410 a fixed-sized array. This is important, as the number of connections
24411 is becoming increasingly decoupled from the number of sockets.
24414 Changes in version 0.1.2.14 - 2007-05-25
24415 Tor 0.1.2.14 changes the addresses of two directory authorities (this
24416 change especially affects those who serve or use hidden services),
24417 and fixes several other crash- and security-related bugs.
24419 o Directory authority changes:
24420 - Two directory authorities (moria1 and moria2) just moved to new
24421 IP addresses. This change will particularly affect those who serve
24422 or use hidden services.
24424 o Major bugfixes (crashes):
24425 - If a directory server runs out of space in the connection table
24426 as it's processing a begin_dir request, it will free the exit stream
24427 but leave it attached to the circuit, leading to unpredictable
24428 behavior. (Reported by seeess, fixes bug 425.)
24429 - Fix a bug in dirserv_remove_invalid() that would cause authorities
24430 to corrupt memory under some really unlikely scenarios.
24431 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
24432 - Avoid segfaults when reading from mmaped descriptor file. (Reported
24435 o Major bugfixes (security):
24436 - When choosing an entry guard for a circuit, avoid using guards
24437 that are in the same family as the chosen exit -- not just guards
24438 that are exactly the chosen exit. (Reported by lodger.)
24440 o Major bugfixes (resource management):
24441 - If a directory authority is down, skip it when deciding where to get
24442 networkstatus objects or descriptors. Otherwise we keep asking
24443 every 10 seconds forever. Fixes bug 384.
24444 - Count it as a failure if we fetch a valid network-status but we
24445 don't want to keep it. Otherwise we'll keep fetching it and keep
24446 not wanting to keep it. Fixes part of bug 422.
24447 - If all of our dirservers have given us bad or no networkstatuses
24448 lately, then stop hammering them once per minute even when we
24449 think they're failed. Fixes another part of bug 422.
24452 - Actually set the purpose correctly for descriptors inserted with
24453 purpose=controller.
24454 - When we have k non-v2 authorities in our DirServer config,
24455 we ignored the last k authorities in the list when updating our
24457 - Correctly back-off from requesting router descriptors that we are
24458 having a hard time downloading.
24459 - Read resolv.conf files correctly on platforms where read() returns
24460 partial results on small file reads.
24461 - Don't rebuild the entire router store every time we get 32K of
24462 routers: rebuild it when the journal gets very large, or when
24463 the gaps in the store get very large.
24466 - When routers publish SVN revisions in their router descriptors,
24467 authorities now include those versions correctly in networkstatus
24469 - Warn when using a version of libevent before 1.3b to run a server on
24470 OSX or BSD: these versions interact badly with userspace threads.
24473 Changes in version 0.1.2.13 - 2007-04-24
24474 This release features some major anonymity fixes, such as safer path
24475 selection; better client performance; faster bootstrapping, better
24476 address detection, and better DNS support for servers; write limiting as
24477 well as read limiting to make servers easier to run; and a huge pile of
24478 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
24480 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
24481 of the Freenode IRC network, remembering his patience and vision for
24482 free speech on the Internet.
24485 - Fix a memory leak when we ask for "all" networkstatuses and we
24486 get one we don't recognize.
24487 - Add more asserts to hunt down bug 417.
24488 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
24491 Changes in version 0.1.2.12-rc - 2007-03-16
24493 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
24494 directory information requested inside Tor connections (i.e. via
24495 begin_dir cells). It only triggered when the same connection was
24496 serving other data at the same time. Reported by seeess.
24499 - When creating a circuit via the controller, send a 'launched'
24500 event when we're done, so we follow the spec better.
24503 Changes in version 0.1.2.11-rc - 2007-03-15
24504 o Minor bugfixes (controller), reported by daejees:
24505 - Correct the control spec to match how the code actually responds
24506 to 'getinfo addr-mappings/*'.
24507 - The control spec described a GUARDS event, but the code
24508 implemented a GUARD event. Standardize on GUARD, but let people
24509 ask for GUARDS too.
24512 Changes in version 0.1.2.10-rc - 2007-03-07
24513 o Major bugfixes (Windows):
24514 - Do not load the NT services library functions (which may not exist)
24515 just to detect if we're a service trying to shut down. Now we run
24516 on Win98 and friends again.
24518 o Minor bugfixes (other):
24519 - Clarify a couple of log messages.
24520 - Fix a misleading socks5 error number.
24523 Changes in version 0.1.2.9-rc - 2007-03-02
24524 o Major bugfixes (Windows):
24525 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
24526 of the usual GCC "%llu". This prevents a bug when saving 64-bit
24527 int configuration values: the high-order 32 bits would get
24528 truncated. In particular, we were being bitten by the default
24529 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
24530 and maybe also bug 397.)
24532 o Minor bugfixes (performance):
24533 - Use OpenSSL's AES implementation on platforms where it's faster.
24534 This could save us as much as 10% CPU usage.
24536 o Minor bugfixes (server):
24537 - Do not rotate onion key immediately after setting it for the first
24540 o Minor bugfixes (directory authorities):
24541 - Stop calling servers that have been hibernating for a long time
24542 "stable". Also, stop letting hibernating or obsolete servers affect
24543 uptime and bandwidth cutoffs.
24544 - Stop listing hibernating servers in the v1 directory.
24546 o Minor bugfixes (hidden services):
24547 - Upload hidden service descriptors slightly less often, to reduce
24548 load on authorities.
24550 o Minor bugfixes (other):
24551 - Fix an assert that could trigger if a controller quickly set then
24552 cleared EntryNodes. Bug found by Udo van den Heuvel.
24553 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
24555 - Fix a potential race condition in the rpm installer. Found by
24557 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
24558 of 2 as indicating that the server is completely bad; it sometimes
24559 means that the server is just bad for the request in question. (may fix
24560 the last of bug 326.)
24561 - Disable encrypted directory connections when we don't have a server
24562 descriptor for the destination. We'll get this working again in
24566 Changes in version 0.1.2.8-beta - 2007-02-26
24567 o Major bugfixes (crashes):
24568 - Stop crashing when the controller asks us to resetconf more than
24569 one config option at once. (Vidalia 0.0.11 does this.)
24570 - Fix a crash that happened on Win98 when we're given command-line
24571 arguments: don't try to load NT service functions from advapi32.dll
24572 except when we need them. (Bug introduced in 0.1.2.7-alpha;
24574 - Fix a longstanding obscure crash bug that could occur when
24575 we run out of DNS worker processes. (Resolves bug 390.)
24577 o Major bugfixes (hidden services):
24578 - Correctly detect whether hidden service descriptor downloads are
24579 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
24581 o Major bugfixes (accounting):
24582 - When we start during an accounting interval before it's time to wake
24583 up, remember to wake up at the correct time. (May fix bug 342.)
24585 o Minor bugfixes (controller):
24586 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
24587 clear the corresponding on_circuit variable, and remember later
24588 that we don't need to send a redundant CLOSED event. Resolves part
24590 - Report events where a resolve succeeded or where we got a socks
24591 protocol error correctly, rather than calling both of them
24593 - Change reported stream target addresses to IP consistently when
24594 we finally get the IP from an exit node.
24595 - Send log messages to the controller even if they happen to be very
24598 o Minor bugfixes (other):
24599 - Display correct results when reporting which versions are
24600 recommended, and how recommended they are. (Resolves bug 383.)
24601 - Improve our estimates for directory bandwidth to be less random:
24602 guess that an unrecognized directory will have the average bandwidth
24603 from all known directories, not that it will have the average
24604 bandwidth from those directories earlier than it on the list.
24605 - If we start a server with ClientOnly 1, then set ClientOnly to 0
24606 and hup, stop triggering an assert based on an empty onion_key.
24607 - On platforms with no working mmap() equivalent, don't warn the
24608 user when cached-routers doesn't exist.
24609 - Warn the user when mmap() [or its equivalent] fails for some reason
24610 other than file-not-found.
24611 - Don't warn the user when cached-routers.new doesn't exist: that's
24612 perfectly fine when starting up for the first time.
24613 - When EntryNodes are configured, rebuild the guard list to contain,
24614 in order: the EntryNodes that were guards before; the rest of the
24615 EntryNodes; the nodes that were guards before.
24616 - Mask out all signals in sub-threads; only the libevent signal
24617 handler should be processing them. This should prevent some crashes
24618 on some machines using pthreads. (Patch from coderman.)
24619 - Fix switched arguments on memset in the implementation of
24620 tor_munmap() for systems with no mmap() call.
24621 - When Tor receives a router descriptor that it asked for, but
24622 no longer wants (because it has received fresh networkstatuses
24623 in the meantime), do not warn the user. Cache the descriptor if
24624 we're a cache; drop it if we aren't.
24625 - Make earlier entry guards _really_ get retried when the network
24627 - On a malformed DNS reply, always give an error to the corresponding
24629 - Build with recent libevents on platforms that do not define the
24630 nonstandard types "u_int8_t" and friends.
24632 o Minor features (controller):
24633 - Warn the user when an application uses the obsolete binary v0
24634 control protocol. We're planning to remove support for it during
24635 the next development series, so it's good to give people some
24637 - Add STREAM_BW events to report per-entry-stream bandwidth
24638 use. (Patch from Robert Hogan.)
24639 - Rate-limit SIGNEWNYM signals in response to controllers that
24640 impolitely generate them for every single stream. (Patch from
24641 mwenge; closes bug 394.)
24642 - Make REMAP stream events have a SOURCE (cache or exit), and
24643 make them generated in every case where we get a successful
24644 connected or resolved cell.
24646 o Minor bugfixes (performance):
24647 - Call router_have_min_dir_info half as often. (This is showing up in
24648 some profiles, but not others.)
24649 - When using GCC, make log_debug never get called at all, and its
24650 arguments never get evaluated, when no debug logs are configured.
24651 (This is showing up in some profiles, but not others.)
24654 - Remove some never-implemented options. Mark PathlenCoinWeight as
24656 - Implement proposal 106: Stop requiring clients to have well-formed
24657 certificates; stop checking nicknames in certificates. (Clients
24658 have certificates so that they can look like Tor servers, but in
24659 the future we might want to allow them to look like regular TLS
24660 clients instead. Nicknames in certificates serve no purpose other
24661 than making our protocol easier to recognize on the wire.)
24662 - Revise messages on handshake failure again to be even more clear about
24663 which are incoming connections and which are outgoing.
24664 - Discard any v1 directory info that's over 1 month old (for
24665 directories) or over 1 week old (for running-routers lists).
24666 - Do not warn when individual nodes in the configuration's EntryNodes,
24667 ExitNodes, etc are down: warn only when all possible nodes
24668 are down. (Fixes bug 348.)
24669 - Always remove expired routers and networkstatus docs before checking
24670 whether we have enough information to build circuits. (Fixes
24672 - Put a lower-bound on MaxAdvertisedBandwidth.
24675 Changes in version 0.1.2.7-alpha - 2007-02-06
24676 o Major bugfixes (rate limiting):
24677 - Servers decline directory requests much more aggressively when
24678 they're low on bandwidth. Otherwise they end up queueing more and
24679 more directory responses, which can't be good for latency.
24680 - But never refuse directory requests from local addresses.
24681 - Fix a memory leak when sending a 503 response for a networkstatus
24683 - Be willing to read or write on local connections (e.g. controller
24684 connections) even when the global rate limiting buckets are empty.
24685 - If our system clock jumps back in time, don't publish a negative
24686 uptime in the descriptor. Also, don't let the global rate limiting
24687 buckets go absurdly negative.
24688 - Flush local controller connection buffers periodically as we're
24689 writing to them, so we avoid queueing 4+ megabytes of data before
24692 o Major bugfixes (NT services):
24693 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
24694 command-line flag so that admins can override the default by saying
24695 "tor --service install --user "SomeUser"". This will not affect
24696 existing installed services. Also, warn the user that the service
24697 will look for its configuration file in the service user's
24698 %appdata% directory. (We can't do the 'hardwire the user's appdata
24699 directory' trick any more, since we may not have read access to that
24702 o Major bugfixes (other):
24703 - Previously, we would cache up to 16 old networkstatus documents
24704 indefinitely, if they came from nontrusted authorities. Now we
24705 discard them if they are more than 10 days old.
24706 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
24708 - Detect and reject malformed DNS responses containing circular
24710 - If exits are rare enough that we're not marking exits as guards,
24711 ignore exit bandwidth when we're deciding the required bandwidth
24713 - When we're handling a directory connection tunneled over Tor,
24714 don't fill up internal memory buffers with all the data we want
24715 to tunnel; instead, only add it if the OR connection that will
24716 eventually receive it has some room for it. (This can lead to
24717 slowdowns in tunneled dir connections; a better solution will have
24718 to wait for 0.2.0.)
24720 o Minor bugfixes (dns):
24721 - Add some defensive programming to eventdns.c in an attempt to catch
24722 possible memory-stomping bugs.
24723 - Detect and reject DNS replies containing IPv4 or IPv6 records with
24724 an incorrect number of bytes. (Previously, we would ignore the
24726 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
24727 in the correct order, and doesn't crash.
24728 - Free memory held in recently-completed DNS lookup attempts on exit.
24729 This was not a memory leak, but may have been hiding memory leaks.
24730 - Handle TTL values correctly on reverse DNS lookups.
24731 - Treat failure to parse resolv.conf as an error.
24733 o Minor bugfixes (other):
24734 - Fix crash with "tor --list-fingerprint" (reported by seeess).
24735 - When computing clock skew from directory HTTP headers, consider what
24736 time it was when we finished asking for the directory, not what
24738 - Expire socks connections if they spend too long waiting for the
24739 handshake to finish. Previously we would let them sit around for
24740 days, if the connecting application didn't close them either.
24741 - And if the socks handshake hasn't started, don't send a
24742 "DNS resolve socks failed" handshake reply; just close it.
24743 - Stop using C functions that OpenBSD's linker doesn't like.
24744 - Don't launch requests for descriptors unless we have networkstatuses
24745 from at least half of the authorities. This delays the first
24746 download slightly under pathological circumstances, but can prevent
24747 us from downloading a bunch of descriptors we don't need.
24748 - Do not log IPs with TLS failures for incoming TLS
24749 connections. (Fixes bug 382.)
24750 - If the user asks to use invalid exit nodes, be willing to use
24752 - Stop using the reserved ac_cv namespace in our configure script.
24753 - Call stat() slightly less often; use fstat() when possible.
24754 - Refactor the way we handle pending circuits when an OR connection
24755 completes or fails, in an attempt to fix a rare crash bug.
24756 - Only rewrite a conn's address based on X-Forwarded-For: headers
24757 if it's a parseable public IP address; and stop adding extra quotes
24758 to the resulting address.
24761 - Weight directory requests by advertised bandwidth. Now we can
24762 let servers enable write limiting but still allow most clients to
24763 succeed at their directory requests. (We still ignore weights when
24764 choosing a directory authority; I hope this is a feature.)
24767 - Create a new file ReleaseNotes which was the old ChangeLog. The
24768 new ChangeLog file now includes the summaries for all development
24770 - Check for addresses with invalid characters at the exit as well
24771 as at the client, and warn less verbosely when they fail. You can
24772 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
24773 - Adapt a patch from goodell to let the contrib/exitlist script
24774 take arguments rather than require direct editing.
24775 - Inform the server operator when we decide not to advertise a
24776 DirPort due to AccountingMax enabled or a low BandwidthRate. It
24777 was confusing Zax, so now we're hopefully more helpful.
24778 - Bring us one step closer to being able to establish an encrypted
24779 directory tunnel without knowing a descriptor first. Still not
24780 ready yet. As part of the change, now assume we can use a
24781 create_fast cell if we don't know anything about a router.
24782 - Allow exit nodes to use nameservers running on ports other than 53.
24783 - Servers now cache reverse DNS replies.
24784 - Add an --ignore-missing-torrc command-line option so that we can
24785 get the "use sensible defaults if the configuration file doesn't
24786 exist" behavior even when specifying a torrc location on the command
24789 o Minor features (controller):
24790 - Track reasons for OR connection failure; make these reasons
24791 available via the controller interface. (Patch from Mike Perry.)
24792 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
24793 can learn when clients are sending malformed hostnames to Tor.
24794 - Clean up documentation for controller status events.
24795 - Add a REMAP status to stream events to note that a stream's
24796 address has changed because of a cached address or a MapAddress
24800 Changes in version 0.1.2.6-alpha - 2007-01-09
24802 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
24803 connection handles more than 4 gigs in either direction, we crash.
24804 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
24805 advertised exit node, somebody might try to exit from us when
24806 we're bootstrapping and before we've built our descriptor yet.
24807 Refuse the connection rather than crashing.
24810 - Warn if we (as a server) find that we've resolved an address that we
24811 weren't planning to resolve.
24812 - Warn that using select() on any libevent version before 1.1 will be
24813 unnecessarily slow (even for select()).
24814 - Flush ERR-level controller status events just like we currently
24815 flush ERR-level log events, so that a Tor shutdown doesn't prevent
24816 the controller from learning about current events.
24818 o Minor features (more controller status events):
24819 - Implement EXTERNAL_ADDRESS server status event so controllers can
24820 learn when our address changes.
24821 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
24822 can learn when directories reject our descriptor.
24823 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
24824 can learn when a client application is speaking a non-socks protocol
24826 - Implement DANGEROUS_SOCKS client status event so controllers
24827 can learn when a client application is leaking DNS addresses.
24828 - Implement BUG general status event so controllers can learn when
24829 Tor is unhappy about its internal invariants.
24830 - Implement CLOCK_SKEW general status event so controllers can learn
24831 when Tor thinks the system clock is set incorrectly.
24832 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
24833 server status events so controllers can learn when their descriptors
24834 are accepted by a directory.
24835 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
24836 server status events so controllers can learn about Tor's progress in
24837 deciding whether it's reachable from the outside.
24838 - Implement BAD_LIBEVENT general status event so controllers can learn
24839 when we have a version/method combination in libevent that needs to
24841 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
24842 and DNS_USELESS server status events so controllers can learn
24843 about changes to DNS server status.
24845 o Minor features (directory):
24846 - Authorities no longer recommend exits as guards if this would shift
24847 too much load to the exit nodes.
24850 Changes in version 0.1.2.5-alpha - 2007-01-06
24852 - Enable write limiting as well as read limiting. Now we sacrifice
24853 capacity if we're pushing out lots of directory traffic, rather
24854 than overrunning the user's intended bandwidth limits.
24855 - Include TLS overhead when counting bandwidth usage; previously, we
24856 would count only the bytes sent over TLS, but not the bytes used
24858 - Support running the Tor service with a torrc not in the same
24859 directory as tor.exe and default to using the torrc located in
24860 the %appdata%\Tor\ of the user who installed the service. Patch
24862 - Servers now check for the case when common DNS requests are going to
24863 wildcarded addresses (i.e. all getting the same answer), and change
24864 their exit policy to reject *:* if it's happening.
24865 - Implement BEGIN_DIR cells, so we can connect to the directory
24866 server via TLS to do encrypted directory requests rather than
24867 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
24868 config options if you like.
24870 o Minor features (config and docs):
24871 - Start using the state file to store bandwidth accounting data:
24872 the bw_accounting file is now obsolete. We'll keep generating it
24873 for a while for people who are still using 0.1.2.4-alpha.
24874 - Try to batch changes to the state file so that we do as few
24875 disk writes as possible while still storing important things in
24877 - The state file and the bw_accounting file get saved less often when
24878 the AvoidDiskWrites config option is set.
24879 - Make PIDFile work on Windows (untested).
24880 - Add internal descriptions for a bunch of configuration options:
24881 accessible via controller interface and in comments in saved
24883 - Reject *:563 (NNTPS) in the default exit policy. We already reject
24884 NNTP by default, so this seems like a sensible addition.
24885 - Clients now reject hostnames with invalid characters. This should
24886 avoid some inadvertent info leaks. Add an option
24887 AllowNonRFC953Hostnames to disable this behavior, in case somebody
24888 is running a private network with hosts called @, !, and #.
24889 - Add a maintainer script to tell us which options are missing
24890 documentation: "make check-docs".
24891 - Add a new address-spec.txt document to describe our special-case
24892 addresses: .exit, .onion, and .noconnnect.
24894 o Minor features (DNS):
24895 - Ongoing work on eventdns infrastructure: now it has dns server
24896 and ipv6 support. One day Tor will make use of it.
24897 - Add client-side caching for reverse DNS lookups.
24898 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
24899 - When we change nameservers or IP addresses, reset and re-launch
24900 our tests for DNS hijacking.
24902 o Minor features (directory):
24903 - Authorities now specify server versions in networkstatus. This adds
24904 about 2% to the size of compressed networkstatus docs, and allows
24905 clients to tell which servers support BEGIN_DIR and which don't.
24906 The implementation is forward-compatible with a proposed future
24907 protocol version scheme not tied to Tor versions.
24908 - DirServer configuration lines now have an orport= option so
24909 clients can open encrypted tunnels to the authorities without
24910 having downloaded their descriptors yet. Enabled for moria1,
24911 moria2, tor26, and lefkada now in the default configuration.
24912 - Directory servers are more willing to send a 503 "busy" if they
24913 are near their write limit, especially for v1 directory requests.
24914 Now they can use their limited bandwidth for actual Tor traffic.
24915 - Clients track responses with status 503 from dirservers. After a
24916 dirserver has given us a 503, we try not to use it until an hour has
24917 gone by, or until we have no dirservers that haven't given us a 503.
24918 - When we get a 503 from a directory, and we're not a server, we don't
24919 count the failure against the total number of failures allowed
24920 for the thing we're trying to download.
24921 - Report X-Your-Address-Is correctly from tunneled directory
24922 connections; don't report X-Your-Address-Is when it's an internal
24923 address; and never believe reported remote addresses when they're
24925 - Protect against an unlikely DoS attack on directory servers.
24926 - Add a BadDirectory flag to network status docs so that authorities
24927 can (eventually) tell clients about caches they believe to be
24930 o Minor features (controller):
24931 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
24932 - Reimplement GETINFO so that info/names stays in sync with the
24934 - Implement "GETINFO fingerprint".
24935 - Implement "SETEVENTS GUARD" so controllers can get updates on
24936 entry guard status as it changes.
24938 o Minor features (clean up obsolete pieces):
24939 - Remove some options that have been deprecated since at least
24940 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
24941 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
24942 to set log options.
24943 - We no longer look for identity and onion keys in "identity.key" and
24944 "onion.key" -- these were replaced by secret_id_key and
24945 secret_onion_key in 0.0.8pre1.
24946 - We no longer require unrecognized directory entries to be
24949 o Major bugfixes (security):
24950 - Stop sending the HttpProxyAuthenticator string to directory
24951 servers when directory connections are tunnelled through Tor.
24952 - Clients no longer store bandwidth history in the state file.
24953 - Do not log introduction points for hidden services if SafeLogging
24955 - When generating bandwidth history, round down to the nearest
24956 1k. When storing accounting data, round up to the nearest 1k.
24957 - When we're running as a server, remember when we last rotated onion
24958 keys, so that we will rotate keys once they're a week old even if
24959 we never stay up for a week ourselves.
24961 o Major bugfixes (other):
24962 - Fix a longstanding bug in eventdns that prevented the count of
24963 timed-out resolves from ever being reset. This bug caused us to
24964 give up on a nameserver the third time it timed out, and try it
24965 10 seconds later... and to give up on it every time it timed out
24967 - Take out the '5 second' timeout from the connection retry
24968 schedule. Now the first connect attempt will wait a full 10
24969 seconds before switching to a new circuit. Perhaps this will help
24970 a lot. Based on observations from Mike Perry.
24971 - Fix a bug on the Windows implementation of tor_mmap_file() that
24972 would prevent the cached-routers file from ever loading. Reported
24976 - Fix an assert failure when a directory authority sets
24977 AuthDirRejectUnlisted and then receives a descriptor from an
24978 unlisted router. Reported by seeess.
24979 - Avoid a double-free when parsing malformed DirServer lines.
24980 - Fix a bug when a BSD-style PF socket is first used. Patch from
24982 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
24983 to resolve an address at a given exit node even when they ask for
24985 - Servers no longer ever list themselves in their "family" line,
24986 even if configured to do so. This makes it easier to configure
24987 family lists conveniently.
24988 - When running as a server, don't fall back to 127.0.0.1 when no
24989 nameservers are configured in /etc/resolv.conf; instead, make the
24990 user fix resolv.conf or specify nameservers explicitly. (Resolves
24992 - Stop accepting certain malformed ports in configured exit policies.
24993 - Don't re-write the fingerprint file every restart, unless it has
24995 - Stop warning when a single nameserver fails: only warn when _all_ of
24996 our nameservers have failed. Also, when we only have one nameserver,
24997 raise the threshold for deciding that the nameserver is dead.
24998 - Directory authorities now only decide that routers are reachable
24999 if their identity keys are as expected.
25000 - When the user uses bad syntax in the Log config line, stop
25001 suggesting other bad syntax as a replacement.
25002 - Correctly detect ipv6 DNS capability on OpenBSD.
25004 o Minor bugfixes (controller):
25005 - Report the circuit number correctly in STREAM CLOSED events. Bug
25006 reported by Mike Perry.
25007 - Do not report bizarre values for results of accounting GETINFOs
25008 when the last second's write or read exceeds the allotted bandwidth.
25009 - Report "unrecognized key" rather than an empty string when the
25010 controller tries to fetch a networkstatus that doesn't exist.
25013 Changes in version 0.1.1.26 - 2006-12-14
25014 o Security bugfixes:
25015 - Stop sending the HttpProxyAuthenticator string to directory
25016 servers when directory connections are tunnelled through Tor.
25017 - Clients no longer store bandwidth history in the state file.
25018 - Do not log introduction points for hidden services if SafeLogging
25022 - Fix an assert failure when a directory authority sets
25023 AuthDirRejectUnlisted and then receives a descriptor from an
25024 unlisted router (reported by seeess).
25027 Changes in version 0.1.2.4-alpha - 2006-12-03
25029 - Add support for using natd; this allows FreeBSDs earlier than
25030 5.1.2 to have ipfw send connections through Tor without using
25031 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
25034 - Make all connections to addresses of the form ".noconnect"
25035 immediately get closed. This lets application/controller combos
25036 successfully test whether they're talking to the same Tor by
25037 watching for STREAM events.
25038 - Make cross.sh cross-compilation script work even when autogen.sh
25039 hasn't been run. (Patch from Michael Mohr.)
25040 - Statistics dumped by -USR2 now include a breakdown of public key
25041 operations, for profiling.
25044 - Fix a major leak when directory authorities parse their
25045 approved-routers list, a minor memory leak when we fail to pick
25046 an exit node, and a few rare leaks on errors.
25047 - Handle TransPort connections even when the server sends data before
25048 the client sends data. Previously, the connection would just hang
25049 until the client sent data. (Patch from tup based on patch from
25051 - Avoid assert failure when our cached-routers file is empty on
25055 - Don't log spurious warnings when we see a circuit close reason we
25056 don't recognize; it's probably just from a newer version of Tor.
25057 - Have directory authorities allow larger amounts of drift in uptime
25058 without replacing the server descriptor: previously, a server that
25059 restarted every 30 minutes could have 48 "interesting" descriptors
25061 - Start linking to the Tor specification and Tor reference manual
25062 correctly in the Windows installer.
25063 - Add Vidalia to the OS X uninstaller script, so when we uninstall
25064 Tor/Privoxy we also uninstall Vidalia.
25065 - Resume building on Irix64, and fix a lot of warnings from its
25066 MIPSpro C compiler.
25067 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
25068 when we're running as a client.
25071 Changes in version 0.1.1.25 - 2006-11-04
25073 - When a client asks us to resolve (rather than connect to)
25074 an address, and we have a cached answer, give them the cached
25075 answer. Previously, we would give them no answer at all.
25076 - We were building exactly the wrong circuits when we predict
25077 hidden service requirements, meaning Tor would have to build all
25078 its circuits on demand.
25079 - If none of our live entry guards have a high uptime, but we
25080 require a guard with a high uptime, try adding a new guard before
25081 we give up on the requirement. This patch should make long-lived
25082 connections more stable on average.
25083 - When testing reachability of our DirPort, don't launch new
25084 tests when there's already one in progress -- unreachable
25085 servers were stacking up dozens of testing streams.
25087 o Security bugfixes:
25088 - When the user sends a NEWNYM signal, clear the client-side DNS
25089 cache too. Otherwise we continue to act on previous information.
25092 - Avoid a memory corruption bug when creating a hash table for
25094 - Avoid possibility of controller-triggered crash when misusing
25095 certain commands from a v0 controller on platforms that do not
25096 handle printf("%s",NULL) gracefully.
25097 - Avoid infinite loop on unexpected controller input.
25098 - Don't log spurious warnings when we see a circuit close reason we
25099 don't recognize; it's probably just from a newer version of Tor.
25100 - Add Vidalia to the OS X uninstaller script, so when we uninstall
25101 Tor/Privoxy we also uninstall Vidalia.
25104 Changes in version 0.1.2.3-alpha - 2006-10-29
25106 - Prepare for servers to publish descriptors less often: never
25107 discard a descriptor simply for being too old until either it is
25108 recommended by no authorities, or until we get a better one for
25109 the same router. Make caches consider retaining old recommended
25110 routers for even longer.
25111 - If most authorities set a BadExit flag for a server, clients
25112 don't think of it as a general-purpose exit. Clients only consider
25113 authorities that advertise themselves as listing bad exits.
25114 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
25115 headers for content, so that we can work better in the presence of
25116 caching HTTP proxies.
25117 - Allow authorities to list nodes as bad exits by fingerprint or by
25120 o Minor features, controller:
25121 - Add a REASON field to CIRC events; for backward compatibility, this
25122 field is sent only to controllers that have enabled the extended
25123 event format. Also, add additional reason codes to explain why
25124 a given circuit has been destroyed or truncated. (Patches from
25126 - Add a REMOTE_REASON field to extended CIRC events to tell the
25127 controller about why a remote OR told us to close a circuit.
25128 - Stream events also now have REASON and REMOTE_REASON fields,
25129 working much like those for circuit events.
25130 - There's now a GETINFO ns/... field so that controllers can ask Tor
25131 about the current status of a router.
25132 - A new event type "NS" to inform a controller when our opinion of
25133 a router's status has changed.
25134 - Add a GETINFO events/names and GETINFO features/names so controllers
25135 can tell which events and features are supported.
25136 - A new CLEARDNSCACHE signal to allow controllers to clear the
25137 client-side DNS cache without expiring circuits.
25139 o Security bugfixes:
25140 - When the user sends a NEWNYM signal, clear the client-side DNS
25141 cache too. Otherwise we continue to act on previous information.
25144 - Avoid sending junk to controllers or segfaulting when a controller
25145 uses EVENT_NEW_DESC with verbose nicknames.
25146 - Stop triggering asserts if the controller tries to extend hidden
25147 service circuits (reported by mwenge).
25148 - Avoid infinite loop on unexpected controller input.
25149 - When the controller does a "GETINFO network-status", tell it
25150 about even those routers whose descriptors are very old, and use
25151 long nicknames where appropriate.
25152 - Change NT service functions to be loaded on demand. This lets us
25153 build with MinGW without breaking Tor for Windows 98 users.
25154 - Do DirPort reachability tests less often, since a single test
25155 chews through many circuits before giving up.
25156 - In the hidden service example in torrc.sample, stop recommending
25157 esoteric and discouraged hidden service options.
25158 - When stopping an NT service, wait up to 10 sec for it to actually
25159 stop. Patch from Matt Edman; resolves bug 295.
25160 - Fix handling of verbose nicknames with ORCONN controller events:
25161 make them show up exactly when requested, rather than exactly when
25163 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
25164 printing a duplicate "$" in the keys we send (reported by mwenge).
25165 - Correctly set maximum connection limit on Cygwin. (This time
25167 - Try to detect Windows correctly when cross-compiling.
25168 - Detect the size of the routers file correctly even if it is
25169 corrupted (on systems without mmap) or not page-aligned (on systems
25170 with mmap). This bug was harmless.
25171 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
25172 to open a stream fails; now we do in more cases. This should
25173 make clients able to find a good exit faster in some cases, since
25174 unhandleable requests will now get an error rather than timing out.
25175 - Resolve two memory leaks when rebuilding the on-disk router cache
25176 (reported by fookoowa).
25177 - Clean up minor code warnings suggested by the MIPSpro C compiler,
25178 and reported by some Centos users.
25179 - Controller signals now work on non-Unix platforms that don't define
25180 SIGUSR1 and SIGUSR2 the way we expect.
25181 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
25182 values before failing, and always enables eventdns.
25183 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
25184 Try to fix this in configure.in by checking for most functions
25185 before we check for libevent.
25188 Changes in version 0.1.2.2-alpha - 2006-10-07
25190 - Make our async eventdns library on-by-default for Tor servers,
25191 and plan to deprecate the separate dnsworker threads.
25192 - Add server-side support for "reverse" DNS lookups (using PTR
25193 records so clients can determine the canonical hostname for a given
25194 IPv4 address). Only supported by servers using eventdns; servers
25195 now announce in their descriptors whether they support eventdns.
25196 - Specify and implement client-side SOCKS5 interface for reverse DNS
25197 lookups (see doc/socks-extensions.txt).
25198 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
25199 connect to directory servers through Tor. Previously, clients needed
25200 to find Tor exits to make private connections to directory servers.
25201 - Avoid choosing Exit nodes for entry or middle hops when the
25202 total bandwidth available from non-Exit nodes is much higher than
25203 the total bandwidth available from Exit nodes.
25204 - Workaround for name servers (like Earthlink's) that hijack failing
25205 DNS requests and replace the no-such-server answer with a "helpful"
25206 redirect to an advertising-driven search portal. Also work around
25207 DNS hijackers who "helpfully" decline to hijack known-invalid
25208 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
25209 lets you turn it off.
25210 - Send out a burst of long-range padding cells once we've established
25211 that we're reachable. Spread them over 4 circuits, so hopefully
25212 a few will be fast. This exercises our bandwidth and bootstraps
25213 us into the directory more quickly.
25215 o New/improved config options:
25216 - Add new config option "ResolvConf" to let the server operator
25217 choose an alternate resolve.conf file when using eventdns.
25218 - Add an "EnforceDistinctSubnets" option to control our "exclude
25219 servers on the same /16" behavior. It's still on by default; this
25220 is mostly for people who want to operate private test networks with
25221 all the machines on the same subnet.
25222 - If one of our entry guards is on the ExcludeNodes list, or the
25223 directory authorities don't think it's a good guard, treat it as
25224 if it were unlisted: stop using it as a guard, and throw it off
25225 the guards list if it stays that way for a long time.
25226 - Allow directory authorities to be marked separately as authorities
25227 for the v1 directory protocol, the v2 directory protocol, and
25228 as hidden service directories, to make it easier to retire old
25229 authorities. V1 authorities should set "HSAuthoritativeDir 1"
25230 to continue being hidden service authorities too.
25231 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
25233 o Minor features, controller:
25234 - Fix CIRC controller events so that controllers can learn the
25235 identity digests of non-Named servers used in circuit paths.
25236 - Let controllers ask for more useful identifiers for servers. Instead
25237 of learning identity digests for un-Named servers and nicknames
25238 for Named servers, the new identifiers include digest, nickname,
25239 and indication of Named status. Off by default; see control-spec.txt
25240 for more information.
25241 - Add a "getinfo address" controller command so it can display Tor's
25242 best guess to the user.
25243 - New controller event to alert the controller when our server
25244 descriptor has changed.
25245 - Give more meaningful errors on controller authentication failure.
25247 o Minor features, other:
25248 - When asked to resolve a hostname, don't use non-exit servers unless
25249 requested to do so. This allows servers with broken DNS to be
25250 useful to the network.
25251 - Divide eventdns log messages into warn and info messages.
25252 - Reserve the nickname "Unnamed" for routers that can't pick
25253 a hostname: any router can call itself Unnamed; directory
25254 authorities will never allocate Unnamed to any particular router;
25255 clients won't believe that any router is the canonical Unnamed.
25256 - Only include function names in log messages for info/debug messages.
25257 For notice/warn/err, the content of the message should be clear on
25258 its own, and printing the function name only confuses users.
25259 - Avoid some false positives during reachability testing: don't try
25260 to test via a server that's on the same /24 as us.
25261 - If we fail to build a circuit to an intended enclave, and it's
25262 not mandatory that we use that enclave, stop wanting it.
25263 - When eventdns is enabled, allow multithreaded builds on NetBSD and
25264 OpenBSD. (We had previously disabled threads on these platforms
25265 because they didn't have working thread-safe resolver functions.)
25267 o Major bugfixes, anonymity/security:
25268 - If a client asked for a server by name, and there's a named server
25269 in our network-status but we don't have its descriptor yet, we
25270 could return an unnamed server instead.
25271 - Fix NetBSD bug that could allow someone to force uninitialized RAM
25272 to be sent to a server's DNS resolver. This only affects NetBSD
25273 and other platforms that do not bounds-check tolower().
25274 - Reject (most) attempts to use Tor circuits with length one. (If
25275 many people start using Tor as a one-hop proxy, exit nodes become
25276 a more attractive target for compromise.)
25277 - Just because your DirPort is open doesn't mean people should be
25278 able to remotely teach you about hidden service descriptors. Now
25279 only accept rendezvous posts if you've got HSAuthoritativeDir set.
25281 o Major bugfixes, other:
25282 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
25283 - When a client asks the server to resolve (not connect to)
25284 an address, and it has a cached answer, give them the cached answer.
25285 Previously, the server would give them no answer at all.
25286 - Allow really slow clients to not hang up five minutes into their
25287 directory downloads (suggested by Adam J. Richter).
25288 - We were building exactly the wrong circuits when we anticipated
25289 hidden service requirements, meaning Tor would have to build all
25290 its circuits on demand.
25291 - Avoid crashing when we mmap a router cache file of size 0.
25292 - When testing reachability of our DirPort, don't launch new
25293 tests when there's already one in progress -- unreachable
25294 servers were stacking up dozens of testing streams.
25296 o Minor bugfixes, correctness:
25297 - If we're a directory mirror and we ask for "all" network status
25298 documents, we would discard status documents from authorities
25299 we don't recognize.
25300 - Avoid a memory corruption bug when creating a hash table for
25302 - Avoid controller-triggered crash when misusing certain commands
25303 from a v0 controller on platforms that do not handle
25304 printf("%s",NULL) gracefully.
25305 - Don't crash when a controller sends a third argument to an
25306 "extendcircuit" request.
25307 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
25308 response; fix error code when "getinfo dir/status/" fails.
25309 - Avoid crash when telling controller stream-status and a stream
25311 - Patch from Adam Langley to fix assert() in eventdns.c.
25312 - Fix a debug log message in eventdns to say "X resolved to Y"
25313 instead of "X resolved to X".
25314 - Make eventdns give strings for DNS errors, not just error numbers.
25315 - Track unreachable entry guards correctly: don't conflate
25316 'unreachable by us right now' with 'listed as down by the directory
25317 authorities'. With the old code, if a guard was unreachable by
25318 us but listed as running, it would clog our guard list forever.
25319 - Behave correctly in case we ever have a network with more than
25320 2GB/s total advertised capacity.
25321 - Make TrackExitHosts case-insensitive, and fix the behavior of
25322 ".suffix" TrackExitHosts items to avoid matching in the middle of
25324 - Finally fix the openssl warnings from newer gccs that believe that
25325 ignoring a return value is okay, but casting a return value and
25326 then ignoring it is a sign of madness.
25327 - Prevent the contrib/exitlist script from printing the same
25328 result more than once.
25329 - Patch from Steve Hildrey: Generate network status correctly on
25330 non-versioning dirservers.
25331 - Don't listen to the X-Your-Address-Is hint if you did the lookup
25332 via Tor; otherwise you'll think you're the exit node's IP address.
25334 o Minor bugfixes, performance:
25335 - Two small performance improvements on parsing descriptors.
25336 - Major performance improvement on inserting descriptors: change
25337 algorithm from O(n^2) to O(n).
25338 - Make the common memory allocation path faster on machines where
25339 malloc(0) returns a pointer.
25340 - Start remembering X-Your-Address-Is directory hints even if you're
25341 a client, so you can become a server more smoothly.
25342 - Avoid duplicate entries on MyFamily line in server descriptor.
25344 o Packaging, features:
25345 - Remove architecture from OS X builds. The official builds are
25346 now universal binaries.
25347 - The Debian package now uses --verify-config when (re)starting,
25348 to distinguish configuration errors from other errors.
25349 - Update RPMs to require libevent 1.1b.
25351 o Packaging, bugfixes:
25352 - Patches so Tor builds with MinGW on Windows.
25353 - Patches so Tor might run on Cygwin again.
25354 - Resume building on non-gcc compilers and ancient gcc. Resume
25355 building with the -O0 compile flag. Resume building cleanly on
25357 - Run correctly on OS X platforms with case-sensitive filesystems.
25358 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
25359 - Add autoconf checks so Tor can build on Solaris x86 again.
25362 - Documented (and renamed) ServerDNSSearchDomains and
25363 ServerDNSResolvConfFile options.
25364 - Be clearer that the *ListenAddress directives can be repeated
25368 Changes in version 0.1.1.24 - 2006-09-29
25370 - Allow really slow clients to not hang up five minutes into their
25371 directory downloads (suggested by Adam J. Richter).
25372 - Fix major performance regression from 0.1.0.x: instead of checking
25373 whether we have enough directory information every time we want to
25374 do something, only check when the directory information has changed.
25375 This should improve client CPU usage by 25-50%.
25376 - Don't crash if, after a server has been running for a while,
25377 it can't resolve its hostname.
25380 - Allow Tor to start when RunAsDaemon is set but no logs are set.
25381 - Don't crash when the controller receives a third argument to an
25382 "extendcircuit" request.
25383 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
25384 response; fix error code when "getinfo dir/status/" fails.
25385 - Fix configure.in to not produce broken configure files with
25386 more recent versions of autoconf. Thanks to Clint for his auto*
25388 - Fix security bug on NetBSD that could allow someone to force
25389 uninitialized RAM to be sent to a server's DNS resolver. This
25390 only affects NetBSD and other platforms that do not bounds-check
25392 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
25393 methods: these are known to be buggy.
25394 - If we're a directory mirror and we ask for "all" network status
25395 documents, we would discard status documents from authorities
25396 we don't recognize.
25399 Changes in version 0.1.2.1-alpha - 2006-08-27
25401 - Add "eventdns" async dns library from Adam Langley, tweaked to
25402 build on OSX and Windows. Only enabled if you pass the
25403 --enable-eventdns argument to configure.
25404 - Allow servers with no hostname or IP address to learn their
25405 IP address by asking the directory authorities. This code only
25406 kicks in when you would normally have exited with a "no address"
25407 error. Nothing's authenticated, so use with care.
25408 - Rather than waiting a fixed amount of time between retrying
25409 application connections, we wait only 5 seconds for the first,
25410 10 seconds for the second, and 15 seconds for each retry after
25411 that. Hopefully this will improve the expected user experience.
25412 - Patch from Tup to add support for transparent AP connections:
25413 this basically bundles the functionality of trans-proxy-tor
25414 into the Tor mainline. Now hosts with compliant pf/netfilter
25415 implementations can redirect TCP connections straight to Tor
25416 without diverting through SOCKS. Needs docs.
25417 - Busy directory servers save lots of memory by spooling server
25418 descriptors, v1 directories, and v2 networkstatus docs to buffers
25419 as needed rather than en masse. Also mmap the cached-routers
25420 files, so we don't need to keep the whole thing in memory too.
25421 - Automatically avoid picking more than one node from the same
25422 /16 network when constructing a circuit.
25423 - Revise and clean up the torrc.sample that we ship with; add
25424 a section for BandwidthRate and BandwidthBurst.
25427 - Split circuit_t into origin_circuit_t and or_circuit_t, and
25428 split connection_t into edge, or, dir, control, and base structs.
25429 These will save quite a bit of memory on busy servers, and they'll
25430 also help us track down bugs in the code and bugs in the spec.
25431 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
25432 or later. Log when we are doing this, so we can diagnose it when
25433 it fails. (Also, recommend libevent 1.1b for kqueue and
25434 win32 methods; deprecate libevent 1.0b harder; make libevent
25435 recommendation system saner.)
25436 - Start being able to build universal binaries on OS X (thanks
25438 - Export the default exit policy via the control port, so controllers
25439 don't need to guess what it is / will be later.
25440 - Add a man page entry for ProtocolWarnings.
25441 - Add TestVia config option to the man page.
25442 - Remove even more protocol-related warnings from Tor server logs,
25443 such as bad TLS handshakes and malformed begin cells.
25444 - Stop fetching descriptors if you're not a dir mirror and you
25445 haven't tried to establish any circuits lately. [This currently
25446 causes some dangerous behavior, because when you start up again
25447 you'll use your ancient server descriptors.]
25448 - New DirPort behavior: if you have your dirport set, you download
25449 descriptors aggressively like a directory mirror, whether or not
25450 your ORPort is set.
25451 - Get rid of the router_retry_connections notion. Now routers
25452 no longer try to rebuild long-term connections to directory
25453 authorities, and directory authorities no longer try to rebuild
25454 long-term connections to all servers. We still don't hang up
25455 connections in these two cases though -- we need to look at it
25456 more carefully to avoid flapping, and we likely need to wait til
25457 0.1.1.x is obsolete.
25458 - Drop compatibility with obsolete Tors that permit create cells
25459 to have the wrong circ_id_type.
25460 - Re-enable per-connection rate limiting. Get rid of the "OP
25461 bandwidth" concept. Lay groundwork for "bandwidth classes" --
25462 separate global buckets that apply depending on what sort of conn
25464 - Start publishing one minute or so after we find our ORPort
25465 to be reachable. This will help reduce the number of descriptors
25466 we have for ourselves floating around, since it's quite likely
25467 other things (e.g. DirPort) will change during that minute too.
25468 - Fork the v1 directory protocol into its own spec document,
25469 and mark dir-spec.txt as the currently correct (v2) spec.
25472 - When we find our DirPort to be reachable, publish a new descriptor
25473 so we'll tell the world (reported by pnx).
25474 - Publish a new descriptor after we hup/reload. This is important
25475 if our config has changed such that we'll want to start advertising
25476 our DirPort now, etc.
25477 - Allow Tor to start when RunAsDaemon is set but no logs are set.
25478 - When we have a state file we cannot parse, tell the user and
25479 move it aside. Now we avoid situations where the user starts
25480 Tor in 1904, Tor writes a state file with that timestamp in it,
25481 the user fixes her clock, and Tor refuses to start.
25482 - Fix configure.in to not produce broken configure files with
25483 more recent versions of autoconf. Thanks to Clint for his auto*
25485 - "tor --verify-config" now exits with -1(255) or 0 depending on
25486 whether the config options are bad or good.
25487 - Resolve bug 321 when using dnsworkers: append a period to every
25488 address we resolve at the exit node, so that we do not accidentally
25489 pick up local addresses, and so that failing searches are retried
25490 in the resolver search domains. (This is already solved for
25491 eventdns.) (This breaks Blossom servers for now.)
25492 - If we are using an exit enclave and we can't connect, e.g. because
25493 its webserver is misconfigured to not listen on localhost, then
25494 back off and try connecting from somewhere else before we fail.
25497 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
25498 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
25499 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
25500 when the IP address is mapped through MapAddress to a hostname.
25501 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
25502 useless IPv6 DNS resolves.
25503 - Patch suggested by Karsten Loesing: respond to SIGNAL command
25504 before we execute the signal, in case the signal shuts us down.
25505 - Clean up AllowInvalidNodes man page entry.
25506 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
25507 - Add more asserts to track down an assert error on a windows Tor
25508 server with connection_add being called with socket == -1.
25509 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
25510 - Fix misleading log messages: an entry guard that is "unlisted",
25511 as well as not known to be "down" (because we've never heard
25512 of it), is not therefore "up".
25513 - Remove code to special-case "-cvs" ending, since it has not
25514 actually mattered since 0.0.9.
25515 - Make our socks5 handling more robust to broken socks clients:
25516 throw out everything waiting on the buffer in between socks
25517 handshake phases, since they can't possibly (so the theory
25518 goes) have predicted what we plan to respond to them.
25521 Changes in version 0.1.1.23 - 2006-07-30
25523 - Fast Tor servers, especially exit nodes, were triggering asserts
25524 due to a bug in handling the list of pending DNS resolves. Some
25525 bugs still remain here; we're hunting them.
25526 - Entry guards could crash clients by sending unexpected input.
25527 - More fixes on reachability testing: if you find yourself reachable,
25528 then don't ever make any client requests (so you stop predicting
25529 circuits), then hup or have your clock jump, then later your IP
25530 changes, you won't think circuits are working, so you won't try to
25531 test reachability, so you won't publish.
25534 - Avoid a crash if the controller does a resetconf firewallports
25535 and then a setconf fascistfirewall=1.
25536 - Avoid an integer underflow when the dir authority decides whether
25537 a router is stable: we might wrongly label it stable, and compute
25538 a slightly wrong median stability, when a descriptor is published
25540 - Fix a place where we might trigger an assert if we can't build our
25541 own server descriptor yet.
25544 Changes in version 0.1.1.22 - 2006-07-05
25546 - Fix a big bug that was causing servers to not find themselves
25547 reachable if they changed IP addresses. Since only 0.1.1.22+
25548 servers can do reachability testing correctly, now we automatically
25549 make sure to test via one of these.
25550 - Fix to allow clients and mirrors to learn directory info from
25551 descriptor downloads that get cut off partway through.
25552 - Directory authorities had a bug in deciding if a newly published
25553 descriptor was novel enough to make everybody want a copy -- a few
25554 servers seem to be publishing new descriptors many times a minute.
25556 - Fix a rare bug that was causing some servers to complain about
25557 "closing wedged cpuworkers" and skip some circuit create requests.
25558 - Make the Exit flag in directory status documents actually work.
25561 Changes in version 0.1.1.21 - 2006-06-10
25562 o Crash and assert fixes from 0.1.1.20:
25563 - Fix a rare crash on Tor servers that have enabled hibernation.
25564 - Fix a seg fault on startup for Tor networks that use only one
25565 directory authority.
25566 - Fix an assert from a race condition that occurs on Tor servers
25567 while exiting, where various threads are trying to log that they're
25568 exiting, and delete the logs, at the same time.
25569 - Make our unit tests pass again on certain obscure platforms.
25572 - Add support for building SUSE RPM packages.
25573 - Speed up initial bootstrapping for clients: if we are making our
25574 first ever connection to any entry guard, then don't mark it down
25576 - When only one Tor server in the network is labelled as a guard,
25577 and we've already picked him, we would cycle endlessly picking him
25578 again, being unhappy about it, etc. Now we specifically exclude
25579 current guards when picking a new guard.
25580 - Servers send create cells more reliably after the TLS connection
25581 is established: we were sometimes forgetting to send half of them
25582 when we had more than one pending.
25583 - If we get a create cell that asks us to extend somewhere, but the
25584 Tor server there doesn't match the expected digest, we now send
25585 a destroy cell back, rather than silently doing nothing.
25586 - Make options->RedirectExit work again.
25587 - Make cookie authentication for the controller work again.
25588 - Stop being picky about unusual characters in the arguments to
25589 mapaddress. It's none of our business.
25590 - Add a new config option "TestVia" that lets you specify preferred
25591 middle hops to use for test circuits. Perhaps this will let me
25592 debug the reachability problems better.
25594 o Log / documentation fixes:
25595 - If we're a server and some peer has a broken TLS certificate, don't
25596 log about it unless ProtocolWarnings is set, i.e., we want to hear
25597 about protocol violations by others.
25598 - Fix spelling of VirtualAddrNetwork in man page.
25599 - Add a better explanation at the top of the autogenerated torrc file
25600 about what happened to our old torrc.
25603 Changes in version 0.1.1.20 - 2006-05-23
25605 - Downgrade a log severity where servers complain that they're
25607 - Avoid a compile warning on FreeBSD.
25608 - Remove string size limit on NEWDESC messages; solve bug 291.
25609 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
25610 more thoroughly when we're running on windows.
25613 Changes in version 0.1.1.19-rc - 2006-05-03
25615 - Regenerate our local descriptor if it's dirty and we try to use
25616 it locally (e.g. if it changes during reachability detection).
25617 - If we setconf our ORPort to 0, we continued to listen on the
25618 old ORPort and receive connections.
25619 - Avoid a second warning about machine/limits.h on Debian
25621 - Be willing to add our own routerinfo into the routerlist.
25622 Now authorities will include themselves in their directories
25623 and network-statuses.
25624 - Stop trying to upload rendezvous descriptors to every
25625 directory authority: only try the v1 authorities.
25626 - Servers no longer complain when they think they're not
25627 registered with the directory authorities. There were too many
25629 - Backport dist-rpm changes so rpms can be built without errors.
25632 - Implement an option, VirtualAddrMask, to set which addresses
25633 get handed out in response to mapaddress requests. This works
25634 around a bug in tsocks where 127.0.0.0/8 is never socksified.
25637 Changes in version 0.1.1.18-rc - 2006-04-10
25639 - Work harder to download live network-statuses from all the
25640 directory authorities we know about. Improve the threshold
25641 decision logic so we're more robust to edge cases.
25642 - When fetching rendezvous descriptors, we were willing to ask
25643 v2 authorities too, which would always return 404.
25646 - Stop listing down or invalid nodes in the v1 directory. This will
25647 reduce its bulk by about 1/3, and reduce load on directory
25649 - When deciding whether a router is Fast or Guard-worthy, consider
25650 his advertised BandwidthRate and not just the BandwidthCapacity.
25651 - No longer ship INSTALL and README files -- they are useless now.
25652 - Force rpmbuild to behave and honor target_cpu.
25653 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
25654 - Start to include translated versions of the tor-doc-*.html
25655 files, along with the screenshots. Still needs more work.
25656 - Start sending back 512 and 451 errors if mapaddress fails,
25657 rather than not sending anything back at all.
25658 - When we fail to bind or listen on an incoming or outgoing
25659 socket, we should close it before failing. otherwise we just
25660 leak it. (thanks to weasel for finding.)
25661 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
25662 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
25663 - Make NoPublish (even though deprecated) work again.
25664 - Fix a minor security flaw where a versioning auth dirserver
25665 could list a recommended version many times in a row to make
25666 clients more convinced that it's recommended.
25667 - Fix crash bug if there are two unregistered servers running
25668 with the same nickname, one of them is down, and you ask for
25669 them by nickname in your EntryNodes or ExitNodes. Also, try
25670 to pick the one that's running rather than an arbitrary one.
25671 - Fix an infinite loop we could hit if we go offline for too long.
25672 - Complain when we hit WSAENOBUFS on recv() or write() too.
25673 Perhaps this will help us hunt the bug.
25674 - If you're not a versioning dirserver, don't put the string
25675 "client-versions \nserver-versions \n" in your network-status.
25676 - Lower the minimum required number of file descriptors to 1000,
25677 so we can have some overhead for Valgrind on Linux, where the
25678 default ulimit -n is 1024.
25681 - Add tor.dizum.com as the fifth authoritative directory server.
25682 - Add a new config option FetchUselessDescriptors, off by default,
25683 for when you plan to run "exitlist" on your client and you want
25684 to know about even the non-running descriptors.
25687 Changes in version 0.1.1.17-rc - 2006-03-28
25689 - Clients and servers since 0.1.1.10-alpha have been expiring
25690 connections whenever they are idle for 5 minutes and they *do*
25691 have circuits on them. Oops. With this new version, clients will
25692 discard their previous entry guard choices and avoid choosing
25693 entry guards running these flawed versions.
25694 - Fix memory leak when uncompressing concatenated zlib streams. This
25695 was causing substantial leaks over time on Tor servers.
25696 - The v1 directory was including servers as much as 48 hours old,
25697 because that's how the new routerlist->routers works. Now only
25698 include them if they're 20 hours old or less.
25701 - Resume building on irix64, netbsd 2.0, etc.
25702 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
25704 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
25705 and it is confusing some users.
25706 - Mirrors stop caching the v1 directory so often.
25707 - Make the max number of old descriptors that a cache will hold
25708 rise with the number of directory authorities, so we can scale.
25709 - Change our win32 uname() hack to be more forgiving about what
25710 win32 versions it thinks it's found.
25713 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
25715 - When the controller's *setconf commands fail, collect an error
25716 message in a string and hand it back to the controller.
25717 - Make the v2 dir's "Fast" flag based on relative capacity, just
25718 like "Stable" is based on median uptime. Name everything in the
25719 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
25720 - Log server fingerprint on startup, so new server operators don't
25721 have to go hunting around their filesystem for it.
25722 - Return a robots.txt on our dirport to discourage google indexing.
25723 - Let the controller ask for GETINFO dir/status/foo so it can ask
25724 directly rather than connecting to the dir port. Only works when
25725 dirport is set for now.
25727 o New config options rather than constants in the code:
25728 - SocksTimeout: How long do we let a socks connection wait
25729 unattached before we fail it?
25730 - CircuitBuildTimeout: Cull non-open circuits that were born
25731 at least this many seconds ago.
25732 - CircuitIdleTimeout: Cull open clean circuits that were born
25733 at least this many seconds ago.
25736 Changes in version 0.1.1.16-rc - 2006-03-18
25737 o Bugfixes on 0.1.1.15-rc:
25738 - Fix assert when the controller asks to attachstream a connect-wait
25739 or resolve-wait stream.
25740 - Now do address rewriting when the controller asks us to attach
25741 to a particular circuit too. This will let Blossom specify
25742 "moria2.exit" without having to learn what moria2's IP address is.
25743 - Make the "tor --verify-config" command-line work again, so people
25744 can automatically check if their torrc will parse.
25745 - Authoritative dirservers no longer require an open connection from
25746 a server to consider him "reachable". We need this change because
25747 when we add new auth dirservers, old servers won't know not to
25749 - Let Tor build on Sun CC again.
25750 - Fix an off-by-one buffer size in dirserv.c that magically never
25751 hit our three authorities but broke sjmurdoch's own tor network.
25752 - If we as a directory mirror don't know of any v1 directory
25753 authorities, then don't try to cache any v1 directories.
25754 - Stop warning about unknown servers in our family when they are
25755 given as hex digests.
25756 - Stop complaining as quickly to the server operator that he
25757 hasn't registered his nickname/key binding.
25758 - Various cleanups so we can add new V2 Auth Dirservers.
25759 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
25760 reflect the updated flags in our v2 dir protocol.
25761 - Resume allowing non-printable characters for exit streams (both
25762 for connecting and for resolving). Now we tolerate applications
25763 that don't follow the RFCs. But continue to block malformed names
25766 o Bugfixes on 0.1.0.x:
25767 - Fix assert bug in close_logs(): when we close and delete logs,
25768 remove them all from the global "logfiles" list.
25769 - Fix minor integer overflow in calculating when we expect to use up
25770 our bandwidth allocation before hibernating.
25771 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
25772 there are multiple SSLs installed with different versions.
25773 - When we try to be a server and Address is not explicitly set and
25774 our hostname resolves to a private IP address, try to use an
25775 interface address if it has a public address. Now Windows machines
25776 that think of themselves as localhost can work by default.
25779 - Let the controller ask for GETINFO dir/server/foo so it can ask
25780 directly rather than connecting to the dir port.
25781 - Let the controller tell us about certain router descriptors
25782 that it doesn't want Tor to use in circuits. Implement
25783 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
25784 - New config option SafeSocks to reject all application connections
25785 using unsafe socks protocols. Defaults to off.
25788 Changes in version 0.1.1.15-rc - 2006-03-11
25789 o Bugfixes and cleanups:
25790 - When we're printing strings from the network, don't try to print
25791 non-printable characters. This protects us against shell escape
25792 sequence exploits, and also against attacks to fool humans into
25793 misreading their logs.
25794 - Fix a bug where Tor would fail to establish any connections if you
25795 left it off for 24 hours and then started it: we were happy with
25796 the obsolete network statuses, but they all referred to router
25797 descriptors that were too old to fetch, so we ended up with no
25798 valid router descriptors.
25799 - Fix a seg fault in the controller's "getinfo orconn-status"
25800 command while listing status on incoming handshaking connections.
25801 Introduce a status name "NEW" for these connections.
25802 - If we get a linelist or linelist_s config option from the torrc
25803 (e.g. ExitPolicy) and it has no value, warn and skip rather than
25804 silently resetting it to its default.
25805 - Don't abandon entry guards until they've been down or gone for
25807 - Cleaner and quieter log messages.
25810 - New controller signal NEWNYM that makes new application requests
25811 use clean circuits.
25812 - Add a new circuit purpose 'controller' to let the controller ask
25813 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
25814 controller command to let you specify the purpose if you're
25815 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
25816 command to let you change a circuit's purpose after it's been
25818 - Accept "private:*" in routerdesc exit policies; not generated yet
25819 because older Tors do not understand it.
25820 - Add BSD-style contributed startup script "rc.subr" from Peter
25824 Changes in version 0.1.1.14-alpha - 2006-02-20
25825 o Bugfixes on 0.1.1.x:
25826 - Don't die if we ask for a stdout or stderr log (even implicitly)
25827 and we're set to RunAsDaemon -- just warn.
25828 - We still had a few bugs in the OR connection rotation code that
25829 caused directory servers to slowly aggregate connections to other
25830 fast Tor servers. This time for sure!
25831 - Make log entries on Win32 include the name of the function again.
25832 - We were treating a pair of exit policies if they were equal even
25833 if one said accept and the other said reject -- causing us to
25834 not always publish a new descriptor since we thought nothing
25836 - Retry pending server downloads as well as pending networkstatus
25837 downloads when we unexpectedly get a socks request.
25838 - We were ignoring the IS_FAST flag in the directory status,
25839 meaning we were willing to pick trivial-bandwidth nodes for "fast"
25841 - If the controller's SAVECONF command fails (e.g. due to file
25842 permissions), let the controller know that it failed.
25845 - If we're trying to be a Tor server and running Windows 95/98/ME
25846 as a server, explain that we'll likely crash.
25847 - When we're a server, a client asks for an old-style directory,
25848 and our write bucket is empty, don't give it to him. This way
25849 small servers can continue to serve the directory *sometimes*,
25850 without getting overloaded.
25851 - Compress exit policies even more -- look for duplicate lines
25853 - Clients now honor the "guard" flag in the router status when
25854 picking entry guards, rather than looking at is_fast or is_stable.
25855 - Retain unrecognized lines in $DATADIR/state file, so that we can
25856 be forward-compatible.
25857 - Generate 18.0.0.0/8 address policy format in descs when we can;
25858 warn when the mask is not reducible to a bit-prefix.
25859 - Let the user set ControlListenAddress in the torrc. This can be
25860 dangerous, but there are some cases (like a secured LAN) where it
25862 - Split ReachableAddresses into ReachableDirAddresses and
25863 ReachableORAddresses, so we can restrict Dir conns to port 80
25864 and OR conns to port 443.
25865 - Now we can target arch and OS in rpm builds (contributed by
25866 Phobos). Also make the resulting dist-rpm filename match the
25868 - New config options to help controllers: FetchServerDescriptors
25869 and FetchHidServDescriptors for whether to fetch server
25870 info and hidserv info or let the controller do it, and
25871 PublishServerDescriptor and PublishHidServDescriptors.
25872 - Also let the controller set the __AllDirActionsPrivate config
25873 option if you want all directory fetches/publishes to happen via
25874 Tor (it assumes your controller bootstraps your circuits).
25877 Changes in version 0.1.0.17 - 2006-02-17
25878 o Crash bugfixes on 0.1.0.x:
25879 - When servers with a non-zero DirPort came out of hibernation,
25880 sometimes they would trigger an assert.
25882 o Other important bugfixes:
25883 - On platforms that don't have getrlimit (like Windows), we were
25884 artificially constraining ourselves to a max of 1024
25885 connections. Now just assume that we can handle as many as 15000
25886 connections. Hopefully this won't cause other problems.
25888 o Backported features:
25889 - When we're a server, a client asks for an old-style directory,
25890 and our write bucket is empty, don't give it to him. This way
25891 small servers can continue to serve the directory *sometimes*,
25892 without getting overloaded.
25893 - Whenever you get a 503 in response to a directory fetch, try
25894 once more. This will become important once servers start sending
25895 503's whenever they feel busy.
25896 - Fetch a new directory every 120 minutes, not every 40 minutes.
25897 Now that we have hundreds of thousands of users running the old
25898 directory algorithm, it's starting to hurt a lot.
25899 - Bump up the period for forcing a hidden service descriptor upload
25900 from 20 minutes to 1 hour.
25903 Changes in version 0.1.1.13-alpha - 2006-02-09
25904 o Crashes in 0.1.1.x:
25905 - When you tried to setconf ORPort via the controller, Tor would
25906 crash. So people using TorCP to become a server were sad.
25907 - Solve (I hope) the stack-smashing bug that we were seeing on fast
25908 servers. The problem appears to be something do with OpenSSL's
25909 random number generation, or how we call it, or something. Let me
25910 know if the crashes continue.
25911 - Turn crypto hardware acceleration off by default, until we find
25912 somebody smart who can test it for us. (It appears to produce
25913 seg faults in at least some cases.)
25914 - Fix a rare assert error when we've tried all intro points for
25915 a hidden service and we try fetching the service descriptor again:
25916 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
25919 - Fix a major load balance bug: we were round-robining in 16 KB
25920 chunks, and servers with bandwidthrate of 20 KB, while downloading
25921 a 600 KB directory, would starve their other connections. Now we
25922 try to be a bit more fair.
25923 - Dir authorities and mirrors were never expiring the newest
25924 descriptor for each server, causing memory and directory bloat.
25925 - Fix memory-bloating and connection-bloating bug on servers: We
25926 were never closing any connection that had ever had a circuit on
25927 it, because we were checking conn->n_circuits == 0, yet we had a
25928 bug that let it go negative.
25929 - Make Tor work using squid as your http proxy again -- squid
25930 returns an error if you ask for a URL that's too long, and it uses
25931 a really generic error message. Plus, many people are behind a
25932 transparent squid so they don't even realize it.
25933 - On platforms that don't have getrlimit (like Windows), we were
25934 artificially constraining ourselves to a max of 1024
25935 connections. Now just assume that we can handle as many as 15000
25936 connections. Hopefully this won't cause other problems.
25937 - Add a new config option ExitPolicyRejectPrivate which defaults to
25938 1. This means all exit policies will begin with rejecting private
25939 addresses, unless the server operator explicitly turns it off.
25942 - Clients no longer download descriptors for non-running
25944 - Before we add new directory authorities, we should make it
25945 clear that only v1 authorities should receive/publish hidden
25946 service descriptors.
25949 - As soon as we've fetched some more directory info, immediately
25950 try to download more server descriptors. This way we don't have
25951 a 10 second pause during initial bootstrapping.
25952 - Remove even more loud log messages that the server operator can't
25954 - When we're running an obsolete or un-recommended version, make
25955 the log message more clear about what the problem is and what
25956 versions *are* still recommended.
25957 - Provide a more useful warn message when our onion queue gets full:
25958 the CPU is too slow or the exit policy is too liberal.
25959 - Don't warn when we receive a 503 from a dirserver/cache -- this
25960 will pave the way for them being able to refuse if they're busy.
25961 - When we fail to bind a listener, try to provide a more useful
25962 log message: e.g., "Is Tor already running?"
25963 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
25964 Goldberg can prove things about our handshake protocol more
25966 - MaxConn has been obsolete for a while now. Document the ConnLimit
25967 config option, which is a *minimum* number of file descriptors
25968 that must be available else Tor refuses to start.
25969 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
25970 if you log to syslog and want something other than LOG_DAEMON.
25971 - Make dirservers generate a separate "guard" flag to mean,
25972 "would make a good entry guard". Make clients parse it and vote
25973 on it. Not used by clients yet.
25974 - Implement --with-libevent-dir option to ./configure. Also, improve
25975 search techniques to find libevent, and use those for openssl too.
25976 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
25977 - Only start testing reachability once we've established a
25978 circuit. This will make startup on dirservers less noisy.
25979 - Don't try to upload hidden service descriptors until we have
25980 established a circuit.
25981 - Fix the controller's "attachstream 0" command to treat conn like
25982 it just connected, doing address remapping, handling .exit and
25983 .onion idioms, and so on. Now we're more uniform in making sure
25984 that the controller hears about new and closing connections.
25987 Changes in version 0.1.1.12-alpha - 2006-01-11
25988 o Bugfixes on 0.1.1.x:
25989 - The fix to close duplicate server connections was closing all
25990 Tor client connections if they didn't establish a circuit
25991 quickly enough. Oops.
25992 - Fix minor memory issue (double-free) that happened on exit.
25994 o Bugfixes on 0.1.0.x:
25995 - Tor didn't warn when it failed to open a log file.
25998 Changes in version 0.1.1.11-alpha - 2006-01-10
25999 o Crashes in 0.1.1.x:
26000 - Include all the assert/crash fixes from 0.1.0.16.
26001 - If you start Tor and then quit very quickly, there were some
26002 races that tried to free things that weren't allocated yet.
26003 - Fix a rare memory stomp if you're running hidden services.
26004 - Fix segfault when specifying DirServer in config without nickname.
26005 - Fix a seg fault when you finish connecting to a server but at
26006 that moment you dump his server descriptor.
26007 - Extendcircuit and Attachstream controller commands would
26008 assert/crash if you don't give them enough arguments.
26009 - Fix an assert error when we're out of space in the connection_list
26010 and we try to post a hidden service descriptor (reported by weasel).
26011 - If you specify a relative torrc path and you set RunAsDaemon in
26012 your torrc, then it chdir()'s to the new directory. If you HUP,
26013 it tries to load the new torrc location, fails, and exits.
26014 The fix: no longer allow a relative path to torrc using -f.
26017 - Implement "entry guards": automatically choose a handful of entry
26018 nodes and stick with them for all circuits. Only pick new guards
26019 when the ones you have are unsuitable, and if the old guards
26020 become suitable again, switch back. This will increase security
26021 dramatically against certain end-point attacks. The EntryNodes
26022 config option now provides some hints about which entry guards you
26023 want to use most; and StrictEntryNodes means to only use those.
26024 - New directory logic: download by descriptor digest, not by
26025 fingerprint. Caches try to download all listed digests from
26026 authorities; clients try to download "best" digests from caches.
26027 This avoids partitioning and isolating attacks better.
26028 - Make the "stable" router flag in network-status be the median of
26029 the uptimes of running valid servers, and make clients pay
26030 attention to the network-status flags. Thus the cutoff adapts
26031 to the stability of the network as a whole, making IRC, IM, etc
26032 connections more reliable.
26035 - Tor servers with dynamic IP addresses were needing to wait 18
26036 hours before they could start doing reachability testing using
26037 the new IP address and ports. This is because they were using
26038 the internal descriptor to learn what to test, yet they were only
26039 rebuilding the descriptor once they decided they were reachable.
26040 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
26041 to download certain server descriptors, throw them away, and then
26042 fetch them again after 30 minutes. Now mirrors throw away these
26043 server descriptors so clients can't get them.
26044 - We were leaving duplicate connections to other ORs open for a week,
26045 rather than closing them once we detect a duplicate. This only
26046 really affected authdirservers, but it affected them a lot.
26047 - Spread the authdirservers' reachability testing over the entire
26048 testing interval, so we don't try to do 500 TLS's at once every
26052 - If the network is down, and we try to connect to a conn because
26053 we have a circuit in mind, and we timeout (30 seconds) because the
26054 network never answers, we were expiring the circuit, but we weren't
26055 obsoleting the connection or telling the entry_guards functions.
26056 - Some Tor servers process billions of cells per day. These statistics
26057 need to be uint64_t's.
26058 - Check for integer overflows in more places, when adding elements
26059 to smartlists. This could possibly prevent a buffer overflow
26060 on malicious huge inputs. I don't see any, but I haven't looked
26062 - ReachableAddresses kept growing new "reject *:*" lines on every
26064 - When you "setconf log" via the controller, it should remove all
26065 logs. We were automatically adding back in a "log notice stdout".
26066 - Newly bootstrapped Tor networks couldn't establish hidden service
26067 circuits until they had nodes with high uptime. Be more tolerant.
26068 - We were marking servers down when they could not answer every piece
26069 of the directory request we sent them. This was far too harsh.
26070 - Fix the torify (tsocks) config file to not use Tor for localhost
26072 - Directory authorities now go to the proper authority when asking for
26073 a networkstatus, even when they want a compressed one.
26074 - Fix a harmless bug that was causing Tor servers to log
26075 "Got an end because of misc error, but we're not an AP. Closing."
26076 - Authorities were treating their own descriptor changes as cosmetic,
26077 meaning the descriptor available in the network-status and the
26078 descriptor that clients downloaded were different.
26079 - The OS X installer was adding a symlink for tor_resolve but
26080 the binary was called tor-resolve (reported by Thomas Hardly).
26081 - Workaround a problem with some http proxies where they refuse GET
26082 requests that specify "Content-Length: 0" (reported by Adrian).
26083 - Fix wrong log message when you add a "HiddenServiceNodes" config
26084 line without any HiddenServiceDir line (reported by Chris Thomas).
26087 - Write the TorVersion into the state file so we have a prayer of
26088 keeping forward and backward compatibility.
26089 - Revive the FascistFirewall config option rather than eliminating it:
26090 now it's a synonym for ReachableAddresses *:80,*:443.
26091 - Clients choose directory servers from the network status lists,
26092 not from their internal list of router descriptors. Now they can
26093 go to caches directly rather than needing to go to authorities
26095 - Directory authorities ignore router descriptors that have only
26096 cosmetic differences: do this for 0.1.0.x servers now too.
26097 - Add a new flag to network-status indicating whether the server
26098 can answer v2 directory requests too.
26099 - Authdirs now stop whining so loudly about bad descriptors that
26100 they fetch from other dirservers. So when there's a log complaint,
26101 it's for sure from a freshly uploaded descriptor.
26102 - Reduce memory requirements in our structs by changing the order
26104 - There used to be two ways to specify your listening ports in a
26105 server descriptor: on the "router" line and with a separate "ports"
26106 line. Remove support for the "ports" line.
26107 - New config option "AuthDirRejectUnlisted" for auth dirservers as
26108 a panic button: if we get flooded with unusable servers we can
26109 revert to only listing servers in the approved-routers file.
26110 - Auth dir servers can now mark a fingerprint as "!reject" or
26111 "!invalid" in the approved-routers file (as its nickname), to
26112 refuse descriptors outright or include them but marked as invalid.
26113 - Servers store bandwidth history across restarts/crashes.
26114 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
26115 get a better idea of why their circuits failed. Not used yet.
26116 - Directory mirrors now cache up to 16 unrecognized network-status
26117 docs. Now we can add new authdirservers and they'll be cached too.
26118 - When picking a random directory, prefer non-authorities if any
26120 - New controller option "getinfo desc/all-recent" to fetch the
26121 latest server descriptor for every router that Tor knows about.
26124 Changes in version 0.1.0.16 - 2006-01-02
26125 o Crash bugfixes on 0.1.0.x:
26126 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
26127 corrupting the heap, losing FDs, or crashing when we need to resize
26128 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
26129 - It turns out sparc64 platforms crash on unaligned memory access
26130 too -- so detect and avoid this.
26131 - Handle truncated compressed data correctly (by detecting it and
26133 - Fix possible-but-unlikely free(NULL) in control.c.
26134 - When we were closing connections, there was a rare case that
26135 stomped on memory, triggering seg faults and asserts.
26136 - Avoid potential infinite recursion when building a descriptor. (We
26137 don't know that it ever happened, but better to fix it anyway.)
26138 - We were neglecting to unlink marked circuits from soon-to-close OR
26139 connections, which caused some rare scribbling on freed memory.
26140 - Fix a memory stomping race bug when closing the joining point of two
26141 rendezvous circuits.
26142 - Fix an assert in time parsing found by Steven Murdoch.
26144 o Other bugfixes on 0.1.0.x:
26145 - When we're doing reachability testing, provide more useful log
26146 messages so the operator knows what to expect.
26147 - Do not check whether DirPort is reachable when we are suppressing
26148 advertising it because of hibernation.
26149 - When building with -static or on Solaris, we sometimes needed -ldl.
26150 - When we're deciding whether a stream has enough circuits around
26151 that can handle it, count the freshly dirty ones and not the ones
26152 that are so dirty they won't be able to handle it.
26153 - When we're expiring old circuits, we had a logic error that caused
26154 us to close new rendezvous circuits rather than old ones.
26155 - Give a more helpful log message when you try to change ORPort via
26156 the controller: you should upgrade Tor if you want that to work.
26157 - We were failing to parse Tor versions that start with "Tor ".
26158 - Tolerate faulty streams better: when a stream fails for reason
26159 exitpolicy, stop assuming that the router is lying about his exit
26160 policy. When a stream fails for reason misc, allow it to retry just
26161 as if it was resolvefailed. When a stream has failed three times,
26162 reset its failure count so we can try again and get all three tries.
26165 Changes in version 0.1.1.10-alpha - 2005-12-11
26166 o Correctness bugfixes on 0.1.0.x:
26167 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
26168 corrupting the heap, losing FDs, or crashing when we need to resize
26169 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
26170 - Stop doing the complex voodoo overkill checking for insecure
26171 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
26172 - When we were closing connections, there was a rare case that
26173 stomped on memory, triggering seg faults and asserts.
26174 - We were neglecting to unlink marked circuits from soon-to-close OR
26175 connections, which caused some rare scribbling on freed memory.
26176 - When we're deciding whether a stream has enough circuits around
26177 that can handle it, count the freshly dirty ones and not the ones
26178 that are so dirty they won't be able to handle it.
26179 - Recover better from TCP connections to Tor servers that are
26180 broken but don't tell you (it happens!); and rotate TLS
26181 connections once a week.
26182 - When we're expiring old circuits, we had a logic error that caused
26183 us to close new rendezvous circuits rather than old ones.
26184 - Fix a scary-looking but apparently harmless bug where circuits
26185 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
26186 servers, and never switch to state CIRCUIT_STATE_OPEN.
26187 - When building with -static or on Solaris, we sometimes needed to
26189 - Give a useful message when people run Tor as the wrong user,
26190 rather than telling them to start chowning random directories.
26191 - We were failing to inform the controller about new .onion streams.
26193 o Security bugfixes on 0.1.0.x:
26194 - Refuse server descriptors if the fingerprint line doesn't match
26195 the included identity key. Tor doesn't care, but other apps (and
26196 humans) might actually be trusting the fingerprint line.
26197 - We used to kill the circuit when we receive a relay command we
26198 don't recognize. Now we just drop it.
26199 - Start obeying our firewall options more rigorously:
26200 . If we can't get to a dirserver directly, try going via Tor.
26201 . Don't ever try to connect (as a client) to a place our
26202 firewall options forbid.
26203 . If we specify a proxy and also firewall options, obey the
26204 firewall options even when we're using the proxy: some proxies
26205 can only proxy to certain destinations.
26206 - Fix a bug found by Lasse Overlier: when we were making internal
26207 circuits (intended to be cannibalized later for rendezvous and
26208 introduction circuits), we were picking them so that they had
26209 useful exit nodes. There was no need for this, and it actually
26210 aids some statistical attacks.
26211 - Start treating internal circuits and exit circuits separately.
26212 It's important to keep them separate because internal circuits
26213 have their last hops picked like middle hops, rather than like
26214 exit hops. So exiting on them will break the user's expectations.
26216 o Bugfixes on 0.1.1.x:
26217 - Take out the mis-feature where we tried to detect IP address
26218 flapping for people with DynDNS, and chose not to upload a new
26219 server descriptor sometimes.
26220 - Try to be compatible with OpenSSL 0.9.6 again.
26221 - Log fix: when the controller is logging about .onion addresses,
26222 sometimes it didn't include the ".onion" part of the address.
26223 - Don't try to modify options->DirServers internally -- if the
26224 user didn't specify any, just add the default ones directly to
26225 the trusted dirserver list. This fixes a bug where people running
26226 controllers would use SETCONF on some totally unrelated config
26227 option, and Tor would start yelling at them about changing their
26229 - Let the controller's redirectstream command specify a port, in
26230 case the controller wants to change that too.
26231 - When we requested a pile of server descriptors, we sometimes
26232 accidentally launched a duplicate request for the first one.
26233 - Bugfix for trackhostexits: write down the fingerprint of the
26234 chosen exit, not its nickname, because the chosen exit might not
26236 - When parsing foo.exit, if foo is unknown, and we are leaving
26237 circuits unattached, set the chosen_exit field and leave the
26238 address empty. This matters because controllers got confused
26240 - Directory authorities no longer try to download server
26241 descriptors that they know they will reject.
26243 o Features and updates:
26244 - Replace balanced trees with hash tables: this should make stuff
26245 significantly faster.
26246 - Resume using the AES counter-mode implementation that we ship,
26247 rather than OpenSSL's. Ours is significantly faster.
26248 - Many other CPU and memory improvements.
26249 - Add a new config option FastFirstHopPK (on by default) so clients
26250 do a trivial crypto handshake for their first hop, since TLS has
26251 already taken care of confidentiality and authentication.
26252 - Add a new config option TestSocks so people can see if their
26253 applications are using socks4, socks4a, socks5-with-ip, or
26254 socks5-with-hostname. This way they don't have to keep mucking
26255 with tcpdump and wondering if something got cached somewhere.
26256 - Warn when listening on a public address for socks. I suspect a
26257 lot of people are setting themselves up as open socks proxies,
26258 and they have no idea that jerks on the Internet are using them,
26259 since they simply proxy the traffic into the Tor network.
26260 - Add "private:*" as an alias in configuration for policies. Now
26261 you can simplify your exit policy rather than needing to list
26262 every single internal or nonroutable network space.
26263 - Add a new controller event type that allows controllers to get
26264 all server descriptors that were uploaded to a router in its role
26265 as authoritative dirserver.
26266 - Start shipping socks-extensions.txt, tor-doc-unix.html,
26267 tor-doc-server.html, and stylesheet.css in the tarball.
26268 - Stop shipping tor-doc.html in the tarball.
26271 Changes in version 0.1.1.9-alpha - 2005-11-15
26272 o Usability improvements:
26273 - Start calling it FooListenAddress rather than FooBindAddress,
26274 since few of our users know what it means to bind an address
26276 - Reduce clutter in server logs. We're going to try to make
26277 them actually usable now. New config option ProtocolWarnings that
26278 lets you hear about how _other Tors_ are breaking the protocol. Off
26280 - Divide log messages into logging domains. Once we put some sort
26281 of interface on this, it will let people looking at more verbose
26282 log levels specify the topics they want to hear more about.
26283 - Make directory servers return better http 404 error messages
26284 instead of a generic "Servers unavailable".
26285 - Check for even more Windows version flags when writing the platform
26286 string in server descriptors, and note any we don't recognize.
26287 - Clean up more of the OpenSSL memory when exiting, so we can detect
26288 memory leaks better.
26289 - Make directory authorities be non-versioning, non-naming by
26290 default. Now we can add new directory servers without requiring
26291 their operators to pay close attention.
26292 - When logging via syslog, include the pid whenever we provide
26293 a log entry. Suggested by Todd Fries.
26295 o Performance improvements:
26296 - Directory servers now silently throw away new descriptors that
26297 haven't changed much if the timestamps are similar. We do this to
26298 tolerate older Tor servers that upload a new descriptor every 15
26299 minutes. (It seemed like a good idea at the time.)
26300 - Inline bottleneck smartlist functions; use fast versions by default.
26301 - Add a "Map from digest to void*" abstraction digestmap_t so we
26302 can do less hex encoding/decoding. Use it in router_get_by_digest()
26303 to resolve a performance bottleneck.
26304 - Allow tor_gzip_uncompress to extract as much as possible from
26305 truncated compressed data. Try to extract as many
26306 descriptors as possible from truncated http responses (when
26307 DIR_PURPOSE_FETCH_ROUTERDESC).
26308 - Make circ->onionskin a pointer, not a static array. moria2 was using
26309 125000 circuit_t's after it had been up for a few weeks, which
26310 translates to 20+ megs of wasted space.
26311 - The private half of our EDH handshake keys are now chosen out
26312 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
26314 o Security improvements:
26315 - Start making directory caches retain old routerinfos, so soon
26316 clients can start asking by digest of descriptor rather than by
26317 fingerprint of server.
26318 - Add half our entropy from RAND_poll in OpenSSL. This knows how
26319 to use egd (if present), openbsd weirdness (if present), vms/os2
26320 weirdness (if we ever port there), and more in the future.
26322 o Bugfixes on 0.1.0.x:
26323 - Do round-robin writes of at most 16 kB per write. This might be
26324 more fair on loaded Tor servers, and it might resolve our Windows
26325 crash bug. It might also slow things down.
26326 - Our TLS handshakes were generating a single public/private
26327 keypair for the TLS context, rather than making a new one for
26328 each new connections. Oops. (But we were still rotating them
26329 periodically, so it's not so bad.)
26330 - When we were cannibalizing a circuit with a particular exit
26331 node in mind, we weren't checking to see if that exit node was
26332 already present earlier in the circuit. Oops.
26333 - When a Tor server's IP changes (e.g. from a dyndns address),
26334 upload a new descriptor so clients will learn too.
26335 - Really busy servers were keeping enough circuits open on stable
26336 connections that they were wrapping around the circuit_id
26337 space. (It's only two bytes.) This exposed a bug where we would
26338 feel free to reuse a circuit_id even if it still exists but has
26339 been marked for close. Try to fix this bug. Some bug remains.
26340 - If we would close a stream early (e.g. it asks for a .exit that
26341 we know would refuse it) but the LeaveStreamsUnattached config
26342 option is set by the controller, then don't close it.
26344 o Bugfixes on 0.1.1.8-alpha:
26345 - Fix a big pile of memory leaks, some of them serious.
26346 - Do not try to download a routerdesc if we would immediately reject
26348 - Resume inserting a newline between all router descriptors when
26349 generating (old style) signed directories, since our spec says
26351 - When providing content-type application/octet-stream for
26352 server descriptors using .z, we were leaving out the
26353 content-encoding header. Oops. (Everything tolerated this just
26354 fine, but that doesn't mean we need to be part of the problem.)
26355 - Fix a potential seg fault in getconf and getinfo using version 1
26356 of the controller protocol.
26357 - Avoid crash: do not check whether DirPort is reachable when we
26358 are suppressing it because of hibernation.
26359 - Make --hash-password not crash on exit.
26362 Changes in version 0.1.1.8-alpha - 2005-10-07
26363 o New features (major):
26364 - Clients don't download or use the directory anymore. Now they
26365 download and use network-statuses from the trusted dirservers,
26366 and fetch individual server descriptors as needed from mirrors.
26367 See dir-spec.txt for all the gory details.
26368 - Be more conservative about whether to advertise our DirPort.
26369 The main change is to not advertise if we're running at capacity
26370 and either a) we could hibernate or b) our capacity is low and
26371 we're using a default DirPort.
26372 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
26374 o New features (minor):
26375 - Try to be smart about when to retry network-status and
26376 server-descriptor fetches. Still needs some tuning.
26377 - Stop parsing, storing, or using running-routers output (but
26378 mirrors still cache and serve it).
26379 - Consider a threshold of versioning dirservers (dirservers who have
26380 an opinion about which Tor versions are still recommended) before
26381 deciding whether to warn the user that he's obsolete.
26382 - Dirservers can now reject/invalidate by key and IP, with the
26383 config options "AuthDirInvalid" and "AuthDirReject". This is
26384 useful since currently we automatically list servers as running
26385 and usable even if we know they're jerks.
26386 - Provide dire warnings to any users who set DirServer; move it out
26387 of torrc.sample and into torrc.complete.
26388 - Add MyFamily to torrc.sample in the server section.
26389 - Add nicknames to the DirServer line, so we can refer to them
26390 without requiring all our users to memorize their IP addresses.
26391 - When we get an EOF or a timeout on a directory connection, note
26392 how many bytes of serverdesc we are dropping. This will help
26393 us determine whether it is smart to parse incomplete serverdesc
26395 - Add a new function to "change pseudonyms" -- that is, to stop
26396 using any currently-dirty circuits for new streams, so we don't
26397 link new actions to old actions. Currently it's only called on
26398 HUP (or SIGNAL RELOAD).
26399 - On sighup, if UseHelperNodes changed to 1, use new circuits.
26400 - Start using RAND_bytes rather than RAND_pseudo_bytes from
26401 OpenSSL. Also, reseed our entropy every hour, not just at
26402 startup. And entropy in 512-bit chunks, not 160-bit chunks.
26404 o Fixes on 0.1.1.7-alpha:
26405 - Nobody ever implemented EVENT_ADDRMAP for control protocol
26406 version 0, so don't let version 0 controllers ask for it.
26407 - If you requested something with too many newlines via the
26408 v1 controller protocol, you could crash tor.
26409 - Fix a number of memory leaks, including some pretty serious ones.
26410 - Re-enable DirPort testing again, so Tor servers will be willing
26411 to advertise their DirPort if it's reachable.
26412 - On TLS handshake, only check the other router's nickname against
26413 its expected nickname if is_named is set.
26415 o Fixes forward-ported from 0.1.0.15:
26416 - Don't crash when we don't have any spare file descriptors and we
26417 try to spawn a dns or cpu worker.
26418 - Make the numbers in read-history and write-history into uint64s,
26419 so they don't overflow and publish negatives in the descriptor.
26421 o Fixes on 0.1.0.x:
26422 - For the OS X package's modified privoxy config file, comment
26423 out the "logfile" line so we don't log everything passed
26425 - We were whining about using socks4 or socks5-with-local-lookup
26426 even when it's an IP in the "virtual" range we designed exactly
26428 - We were leaking some memory every time the client changes IPs.
26429 - Never call free() on tor_malloc()d memory. This will help us
26430 use dmalloc to detect memory leaks.
26431 - Check for named servers when looking them up by nickname;
26432 warn when we'recalling a non-named server by its nickname;
26433 don't warn twice about the same name.
26434 - Try to list MyFamily elements by key, not by nickname, and warn
26435 if we've not heard of the server.
26436 - Make windows platform detection (uname equivalent) smarter.
26437 - It turns out sparc64 doesn't like unaligned access either.
26440 Changes in version 0.1.0.15 - 2005-09-23
26441 o Bugfixes on 0.1.0.x:
26442 - Reject ports 465 and 587 (spam targets) in default exit policy.
26443 - Don't crash when we don't have any spare file descriptors and we
26444 try to spawn a dns or cpu worker.
26445 - Get rid of IgnoreVersion undocumented config option, and make us
26446 only warn, never exit, when we're running an obsolete version.
26447 - Don't try to print a null string when your server finds itself to
26448 be unreachable and the Address config option is empty.
26449 - Make the numbers in read-history and write-history into uint64s,
26450 so they don't overflow and publish negatives in the descriptor.
26451 - Fix a minor memory leak in smartlist_string_remove().
26452 - We were only allowing ourselves to upload a server descriptor at
26453 most every 20 minutes, even if it changed earlier than that.
26454 - Clean up log entries that pointed to old URLs.
26457 Changes in version 0.1.1.7-alpha - 2005-09-14
26458 o Fixes on 0.1.1.6-alpha:
26459 - Exit servers were crashing when people asked them to make a
26460 connection to an address not in their exit policy.
26461 - Looking up a non-existent stream for a v1 control connection would
26463 - Fix a seg fault if we ask a dirserver for a descriptor by
26464 fingerprint but he doesn't know about him.
26465 - SETCONF was appending items to linelists, not clearing them.
26466 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
26467 out and refuse the setconf if it would fail.
26468 - Downgrade the dirserver log messages when whining about
26472 - Add Peter Palfrader's check-tor script to tor/contrib/
26473 It lets you easily check whether a given server (referenced by
26474 nickname) is reachable by you.
26475 - Numerous changes to move towards client-side v2 directories. Not
26478 o Fixes on 0.1.0.x:
26479 - If the user gave tor an odd number of command-line arguments,
26480 we were silently ignoring the last one. Now we complain and fail.
26481 [This wins the oldest-bug prize -- this bug has been present since
26482 November 2002, as released in Tor 0.0.0.]
26483 - Do not use unaligned memory access on alpha, mips, or mipsel.
26484 It *works*, but is very slow, so we treat them as if it doesn't.
26485 - Retry directory requests if we fail to get an answer we like
26486 from a given dirserver (we were retrying before, but only if
26487 we fail to connect).
26488 - When writing the RecommendedVersions line, sort them first.
26489 - When the client asked for a rendezvous port that the hidden
26490 service didn't want to provide, we were sending an IP address
26491 back along with the end cell. Fortunately, it was zero. But stop
26493 - Correct "your server is reachable" log entries to indicate that
26494 it was self-testing that told us so.
26497 Changes in version 0.1.1.6-alpha - 2005-09-09
26498 o Fixes on 0.1.1.5-alpha:
26499 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
26500 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
26501 - Fix bug with tor_memmem finding a match at the end of the string.
26502 - Make unit tests run without segfaulting.
26503 - Resolve some solaris x86 compile warnings.
26504 - Handle duplicate lines in approved-routers files without warning.
26505 - Fix bug where as soon as a server refused any requests due to his
26506 exit policy (e.g. when we ask for localhost and he tells us that's
26507 127.0.0.1 and he won't do it), we decided he wasn't obeying his
26508 exit policy using him for any exits.
26509 - Only do openssl hardware accelerator stuff if openssl version is
26512 o New controller features/fixes:
26513 - Add a "RESETCONF" command so you can set config options like
26514 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
26515 a config option in the torrc with no value, then it clears it
26516 entirely (rather than setting it to its default).
26517 - Add a "GETINFO config-file" to tell us where torrc is.
26518 - Avoid sending blank lines when GETINFO replies should be empty.
26519 - Add a QUIT command for the controller (for using it manually).
26520 - Fix a bug in SAVECONF that was adding default dirservers and
26521 other redundant entries to the torrc file.
26523 o Start on the new directory design:
26524 - Generate, publish, cache, serve new network-status format.
26525 - Publish individual descriptors (by fingerprint, by "all", and by
26527 - Publish client and server recommended versions separately.
26528 - Allow tor_gzip_uncompress() to handle multiple concatenated
26529 compressed strings. Serve compressed groups of router
26530 descriptors. The compression logic here could be more
26532 - Distinguish v1 authorities (all currently trusted directories)
26533 from v2 authorities (all trusted directories).
26534 - Change DirServers config line to note which dirs are v1 authorities.
26535 - Add configuration option "V1AuthoritativeDirectory 1" which
26536 moria1, moria2, and tor26 should set.
26537 - Remove option when getting directory cache to see whether they
26538 support running-routers; they all do now. Replace it with one
26539 to see whether caches support v2 stuff.
26542 - Dirservers now do their own external reachability testing of each
26543 Tor server, and only list them as running if they've been found to
26544 be reachable. We also send back warnings to the server's logs if
26545 it uploads a descriptor that we already believe is unreachable.
26546 - Implement exit enclaves: if we know an IP address for the
26547 destination, and there's a running Tor server at that address
26548 which allows exit to the destination, then extend the circuit to
26549 that exit first. This provides end-to-end encryption and end-to-end
26550 authentication. Also, if the user wants a .exit address or enclave,
26551 use 4 hops rather than 3, and cannibalize a general circ for it
26553 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
26554 controller. Also, rotate dns and cpu workers if the controller
26555 changes options that will affect them; and initialize the dns
26556 worker cache tree whether or not we start out as a server.
26557 - Only upload a new server descriptor when options change, 18
26558 hours have passed, uptime is reset, or bandwidth changes a lot.
26559 - Check [X-]Forwarded-For headers in HTTP requests when generating
26560 log messages. This lets people run dirservers (and caches) behind
26561 Apache but still know which IP addresses are causing warnings.
26563 o Config option changes:
26564 - Replace (Fascist)Firewall* config options with a new
26565 ReachableAddresses option that understands address policies.
26566 For example, "ReachableAddresses *:80,*:443"
26567 - Get rid of IgnoreVersion undocumented config option, and make us
26568 only warn, never exit, when we're running an obsolete version.
26569 - Make MonthlyAccountingStart config option truly obsolete now.
26571 o Fixes on 0.1.0.x:
26572 - Reject ports 465 and 587 in the default exit policy, since
26573 people have started using them for spam too.
26574 - It turns out we couldn't bootstrap a network since we added
26575 reachability detection in 0.1.0.1-rc. Good thing the Tor network
26576 has never gone down. Add an AssumeReachable config option to let
26577 servers and dirservers bootstrap. When we're trying to build a
26578 high-uptime or high-bandwidth circuit but there aren't enough
26579 suitable servers, try being less picky rather than simply failing.
26580 - Our logic to decide if the OR we connected to was the right guy
26581 was brittle and maybe open to a mitm for unverified routers.
26582 - We weren't cannibalizing circuits correctly for
26583 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
26584 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
26585 build those from scratch. This should make hidden services faster.
26586 - Predict required circuits better, with an eye toward making hidden
26587 services faster on the service end.
26588 - Retry streams if the exit node sends back a 'misc' failure. This
26589 should result in fewer random failures. Also, after failing
26590 from resolve failed or misc, reset the num failures, so we give
26591 it a fair shake next time we try.
26592 - Clean up the rendezvous warn log msgs, and downgrade some to info.
26593 - Reduce severity on logs about dns worker spawning and culling.
26594 - When we're shutting down and we do something like try to post a
26595 server descriptor or rendezvous descriptor, don't complain that
26596 we seem to be unreachable. Of course we are, we're shutting down.
26597 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
26598 We don't use them yet, but maybe one day our DNS resolver will be
26599 able to discover them.
26600 - Make ContactInfo mandatory for authoritative directory servers.
26601 - Require server descriptors to list IPv4 addresses -- hostnames
26602 are no longer allowed. This also fixes some potential security
26603 problems with people providing hostnames as their address and then
26604 preferentially resolving them to partition users.
26605 - Change log line for unreachability to explicitly suggest /etc/hosts
26606 as the culprit. Also make it clearer what IP address and ports we're
26607 testing for reachability.
26608 - Put quotes around user-supplied strings when logging so users are
26609 more likely to realize if they add bad characters (like quotes)
26611 - Let auth dir servers start without specifying an Address config
26613 - Make unit tests (and other invocations that aren't the real Tor)
26614 run without launching listeners, creating subdirectories, and so on.
26617 Changes in version 0.1.1.5-alpha - 2005-08-08
26618 o Bugfixes included in 0.1.0.14.
26620 o Bugfixes on 0.1.0.x:
26621 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
26622 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
26623 it would silently using ignore the 6668.
26626 Changes in version 0.1.0.14 - 2005-08-08
26627 o Bugfixes on 0.1.0.x:
26628 - Fix the other half of the bug with crypto handshakes
26630 - Fix an assert trigger if you send a 'signal term' via the
26631 controller when it's listening for 'event info' messages.
26634 Changes in version 0.1.1.4-alpha - 2005-08-04
26635 o Bugfixes included in 0.1.0.13.
26638 - Improve tor_gettimeofday() granularity on windows.
26639 - Make clients regenerate their keys when their IP address changes.
26640 - Implement some more GETINFO goodness: expose helper nodes, config
26641 options, getinfo keys.
26644 Changes in version 0.1.0.13 - 2005-08-04
26645 o Bugfixes on 0.1.0.x:
26646 - Fix a critical bug in the security of our crypto handshakes.
26647 - Fix a size_t underflow in smartlist_join_strings2() that made
26648 it do bad things when you hand it an empty smartlist.
26649 - Fix Windows installer to ship Tor license (thanks to Aphex for
26650 pointing out this oversight) and put a link to the doc directory
26652 - Explicitly set no-unaligned-access for sparc: it turns out the
26653 new gcc's let you compile broken code, but that doesn't make it
26657 Changes in version 0.1.1.3-alpha - 2005-07-23
26658 o Bugfixes on 0.1.1.2-alpha:
26659 - Fix a bug in handling the controller's "post descriptor"
26661 - Fix several bugs in handling the controller's "extend circuit"
26663 - Fix a bug in handling the controller's "stream status" event.
26664 - Fix an assert failure if we have a controller listening for
26665 circuit events and we go offline.
26666 - Re-allow hidden service descriptors to publish 0 intro points.
26667 - Fix a crash when generating your hidden service descriptor if
26668 you don't have enough intro points already.
26670 o New features on 0.1.1.2-alpha:
26671 - New controller function "getinfo accounting", to ask how
26672 many bytes we've used in this time period.
26673 - Experimental support for helper nodes: a lot of the risk from
26674 a small static adversary comes because users pick new random
26675 nodes every time they rebuild a circuit. Now users will try to
26676 stick to the same small set of entry nodes if they can. Not
26677 enabled by default yet.
26679 o Bugfixes on 0.1.0.12:
26680 - If you're an auth dir server, always publish your dirport,
26681 even if you haven't yet found yourself to be reachable.
26682 - Fix a size_t underflow in smartlist_join_strings2() that made
26683 it do bad things when you hand it an empty smartlist.
26686 Changes in version 0.1.0.12 - 2005-07-18
26687 o New directory servers:
26688 - tor26 has changed IP address.
26690 o Bugfixes on 0.1.0.x:
26691 - Fix a possible double-free in tor_gzip_uncompress().
26692 - When --disable-threads is set, do not search for or link against
26693 pthreads libraries.
26694 - Don't trigger an assert if an authoritative directory server
26695 claims its dirport is 0.
26696 - Fix bug with removing Tor as an NT service: some people were
26697 getting "The service did not return an error." Thanks to Matt
26701 Changes in version 0.1.1.2-alpha - 2005-07-15
26702 o New directory servers:
26703 - tor26 has changed IP address.
26705 o Bugfixes on 0.1.0.x, crashes/leaks:
26706 - Port the servers-not-obeying-their-exit-policies fix from
26708 - Fix an fd leak in start_daemon().
26709 - On Windows, you can't always reopen a port right after you've
26710 closed it. So change retry_listeners() to only close and re-open
26711 ports that have changed.
26712 - Fix a possible double-free in tor_gzip_uncompress().
26714 o Bugfixes on 0.1.0.x, usability:
26715 - When tor_socketpair() fails in Windows, give a reasonable
26716 Windows-style errno back.
26717 - Let people type "tor --install" as well as "tor -install" when
26719 want to make it an NT service.
26720 - NT service patch from Matt Edman to improve error messages.
26721 - When the controller asks for a config option with an abbreviated
26722 name, give the full name in our response.
26723 - Correct the man page entry on TrackHostExitsExpire.
26724 - Looks like we were never delivering deflated (i.e. compressed)
26725 running-routers lists, even when asked. Oops.
26726 - When --disable-threads is set, do not search for or link against
26727 pthreads libraries.
26729 o Bugfixes on 0.1.1.x:
26730 - Fix a seg fault with autodetecting which controller version is
26734 - New hidden service descriptor format: put a version in it, and
26735 let people specify introduction/rendezvous points that aren't
26736 in "the directory" (which is subjective anyway).
26737 - Allow the DEBUG controller event to work again. Mark certain log
26738 entries as "don't tell this to controllers", so we avoid cycles.
26741 Changes in version 0.1.0.11 - 2005-06-30
26742 o Bugfixes on 0.1.0.x:
26743 - Fix major security bug: servers were disregarding their
26744 exit policies if clients behaved unexpectedly.
26745 - Make OS X init script check for missing argument, so we don't
26746 confuse users who invoke it incorrectly.
26747 - Fix a seg fault in "tor --hash-password foo".
26748 - The MAPADDRESS control command was broken.
26751 Changes in version 0.1.1.1-alpha - 2005-06-29
26753 - Make OS X init script check for missing argument, so we don't
26754 confuse users who invoke it incorrectly.
26755 - Fix a seg fault in "tor --hash-password foo".
26756 - Fix a possible way to DoS dirservers.
26757 - When we complain that your exit policy implicitly allows local or
26758 private address spaces, name them explicitly so operators can
26760 - Make the log message less scary when all the dirservers are
26761 temporarily unreachable.
26762 - We were printing the number of idle dns workers incorrectly when
26766 - Revised controller protocol (version 1) that uses ascii rather
26767 than binary. Add supporting libraries in python and java so you
26768 can use the controller from your applications without caring how
26769 our protocol works.
26770 - Spiffy new support for crypto hardware accelerators. Can somebody
26774 Changes in version 0.0.9.10 - 2005-06-16
26775 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
26776 - Refuse relay cells that claim to have a length larger than the
26777 maximum allowed. This prevents a potential attack that could read
26778 arbitrary memory (e.g. keys) from an exit server's process
26782 Changes in version 0.1.0.10 - 2005-06-14
26783 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
26784 libevent before 1.1a.
26787 Changes in version 0.1.0.9-rc - 2005-06-09
26789 - Reset buf->highwater every time buf_shrink() is called, not just on
26790 a successful shrink. This was causing significant memory bloat.
26791 - Fix buffer overflow when checking hashed passwords.
26792 - Security fix: if seeding the RNG on Win32 fails, quit.
26793 - Allow seeding the RNG on Win32 even when you're not running as
26795 - Disable threading on Solaris too. Something is wonky with it,
26796 cpuworkers, and reentrant libs.
26797 - Reenable the part of the code that tries to flush as soon as an
26798 OR outbuf has a full TLS record available. Perhaps this will make
26799 OR outbufs not grow as huge except in rare cases, thus saving lots
26800 of CPU time plus memory.
26801 - Reject malformed .onion addresses rather then passing them on as
26802 normal web requests.
26803 - Adapt patch from Adam Langley: fix possible memory leak in
26804 tor_lookup_hostname().
26805 - Initialize libevent later in the startup process, so the logs are
26806 already established by the time we start logging libevent warns.
26807 - Use correct errno on win32 if libevent fails.
26808 - Check and warn about known-bad/slow libevent versions.
26809 - Pay more attention to the ClientOnly config option.
26810 - Have torctl.in/tor.sh.in check for location of su binary (needed
26812 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
26813 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
26814 HttpProxyAuthenticator
26815 - Stop warning about sigpipes in the logs. We're going to
26816 pretend that getting these occasionally is normal and fine.
26817 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
26819 installer screens; and don't put stuff into StartupItems unless
26820 the user asks you to.
26821 - Require servers that use the default dirservers to have public IP
26822 addresses. We have too many servers that are configured with private
26823 IPs and their admins never notice the log entries complaining that
26824 their descriptors are being rejected.
26825 - Add OSX uninstall instructions. An actual uninstall script will
26829 Changes in version 0.1.0.8-rc - 2005-05-23
26831 - It turns out that kqueue on OS X 10.3.9 was causing kernel
26832 panics. Disable kqueue on all OS X Tors.
26833 - Fix RPM: remove duplicate line accidentally added to the rpm
26835 - Disable threads on openbsd too, since its gethostaddr is not
26837 - Tolerate libevent 0.8 since it still works, even though it's
26839 - Enable building on Red Hat 9.0 again.
26840 - Allow the middle hop of the testing circuit to be running any
26841 version, now that most of them have the bugfix to let them connect
26842 to unknown servers. This will allow reachability testing to work
26843 even when 0.0.9.7-0.0.9.9 become obsolete.
26844 - Handle relay cells with rh.length too large. This prevents
26845 a potential attack that could read arbitrary memory (maybe even
26846 keys) from the exit server's process.
26847 - We screwed up the dirport reachability testing when we don't yet
26848 have a cached version of the directory. Hopefully now fixed.
26849 - Clean up router_load_single_router() (used by the controller),
26850 so it doesn't seg fault on error.
26851 - Fix a minor memory leak when somebody establishes an introduction
26852 point at your Tor server.
26853 - If a socks connection ends because read fails, don't warn that
26854 you're not sending a socks reply back.
26857 - Add HttpProxyAuthenticator config option too, that works like
26858 the HttpsProxyAuthenticator config option.
26859 - Encode hashed controller passwords in hex instead of base64,
26860 to make it easier to write controllers.
26863 Changes in version 0.1.0.7-rc - 2005-05-17
26865 - Fix a bug in the OS X package installer that prevented it from
26866 installing on Tiger.
26867 - Fix a script bug in the OS X package installer that made it
26868 complain during installation.
26869 - Find libevent even if it's hiding in /usr/local/ and your
26870 CFLAGS and LDFLAGS don't tell you to look there.
26871 - Be able to link with libevent as a shared library (the default
26872 after 1.0d), even if it's hiding in /usr/local/lib and even
26873 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
26874 assuming you're running gcc. Otherwise fail and give a useful
26876 - Fix a bug in the RPM packager: set home directory for _tor to
26877 something more reasonable when first installing.
26878 - Free a minor amount of memory that is still reachable on exit.
26881 Changes in version 0.1.0.6-rc - 2005-05-14
26883 - Implement --disable-threads configure option. Disable threads on
26884 netbsd by default, because it appears to have no reentrant resolver
26886 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
26887 release (1.1) detects and disables kqueue if it's broken.
26888 - Append default exit policy before checking for implicit internal
26889 addresses. Now we don't log a bunch of complaints on startup
26890 when using the default exit policy.
26891 - Some people were putting "Address " in their torrc, and they had
26892 a buggy resolver that resolved " " to 0.0.0.0. Oops.
26893 - If DataDir is ~/.tor, and that expands to /.tor, then default to
26894 LOCALSTATEDIR/tor instead.
26895 - Fix fragmented-message bug in TorControl.py.
26896 - Resolve a minor bug which would prevent unreachable dirports
26897 from getting suppressed in the published descriptor.
26898 - When the controller gave us a new descriptor, we weren't resolving
26899 it immediately, so Tor would think its address was 0.0.0.0 until
26900 we fetched a new directory.
26901 - Fix an uppercase/lowercase case error in suppressing a bogus
26902 libevent warning on some Linuxes.
26905 - Begin scrubbing sensitive strings from logs by default. Turn off
26906 the config option SafeLogging if you need to do debugging.
26907 - Switch to a new buffer management algorithm, which tries to avoid
26908 reallocing and copying quite as much. In first tests it looks like
26909 it uses *more* memory on average, but less cpu.
26910 - First cut at support for "create-fast" cells. Clients can use
26911 these when extending to their first hop, since the TLS already
26912 provides forward secrecy and authentication. Not enabled on
26914 - When dirservers refuse a router descriptor, we now log its
26915 contactinfo, platform, and the poster's IP address.
26916 - Call tor_free_all instead of connections_free_all after forking, to
26917 save memory on systems that need to fork.
26918 - Whine at you if you're a server and you don't set your contactinfo.
26919 - Implement --verify-config command-line option to check if your torrc
26920 is valid without actually launching Tor.
26921 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
26922 rather than just rejecting it.
26925 Changes in version 0.1.0.5-rc - 2005-04-27
26927 - Stop trying to print a null pointer if an OR conn fails because
26928 we didn't like its cert.
26930 - Switch our internal buffers implementation to use a ring buffer,
26931 to hopefully improve performance for fast servers a lot.
26932 - Add HttpsProxyAuthenticator support (basic auth only), based
26933 on patch from Adam Langley.
26934 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
26935 the fast servers that have been joining lately.
26936 - Give hidden service accesses extra time on the first attempt,
26937 since 60 seconds is often only barely enough. This might improve
26939 - Improve performance for dirservers: stop re-parsing the whole
26940 directory every time you regenerate it.
26941 - Add more debugging info to help us find the weird dns freebsd
26942 pthreads bug; cleaner debug messages to help track future issues.
26945 Changes in version 0.0.9.9 - 2005-04-23
26946 o Bugfixes on 0.0.9.x:
26947 - If unofficial Tor clients connect and send weird TLS certs, our
26948 Tor server triggers an assert. This release contains a minimal
26949 backport from the broader fix that we put into 0.1.0.4-rc.
26952 Changes in version 0.1.0.4-rc - 2005-04-23
26954 - If unofficial Tor clients connect and send weird TLS certs, our
26955 Tor server triggers an assert. Stop asserting, and start handling
26956 TLS errors better in other situations too.
26957 - When the controller asks us to tell it about all the debug-level
26958 logs, it turns out we were generating debug-level logs while
26959 telling it about them, which turns into a bad loop. Now keep
26960 track of whether you're sending a debug log to the controller,
26961 and don't log when you are.
26962 - Fix the "postdescriptor" feature of the controller interface: on
26963 non-complete success, only say "done" once.
26965 - Clients are now willing to load balance over up to 2mB, not 1mB,
26966 of advertised bandwidth capacity.
26967 - Add a NoPublish config option, so you can be a server (e.g. for
26968 testing running Tor servers in other Tor networks) without
26969 publishing your descriptor to the primary dirservers.
26972 Changes in version 0.1.0.3-rc - 2005-04-08
26973 o Improvements on 0.1.0.2-rc:
26974 - Client now retries when streams end early for 'hibernating' or
26975 'resource limit' reasons, rather than failing them.
26976 - More automated handling for dirserver operators:
26977 - Automatically approve nodes running 0.1.0.2-rc or later,
26978 now that the the reachability detection stuff is working.
26979 - Now we allow two unverified servers with the same nickname
26980 but different keys. But if a nickname is verified, only that
26981 nickname+key are allowed.
26982 - If you're an authdirserver connecting to an address:port,
26983 and it's not the OR you were expecting, forget about that
26984 descriptor. If he *was* the one you were expecting, then forget
26985 about all other descriptors for that address:port.
26986 - Allow servers to publish descriptors from 12 hours in the future.
26987 Corollary: only whine about clock skew from the dirserver if
26988 he's a trusted dirserver (since now even verified servers could
26989 have quite wrong clocks).
26990 - Adjust maximum skew and age for rendezvous descriptors: let skew
26991 be 48 hours rather than 90 minutes.
26992 - Efficiency improvements:
26993 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
26994 it much faster to look up a circuit for each relay cell.
26995 - Remove most calls to assert_all_pending_dns_resolves_ok(),
26996 since they're eating our cpu on exit nodes.
26997 - Stop wasting time doing a case insensitive comparison for every
26998 dns name every time we do any lookup. Canonicalize the names to
26999 lowercase and be done with it.
27000 - Start sending 'truncated' cells back rather than destroy cells,
27001 if the circuit closes in front of you. This means we won't have
27002 to abandon partially built circuits.
27003 - Only warn once per nickname from add_nickname_list_to_smartlist
27004 per failure, so an entrynode or exitnode choice that's down won't
27006 - Put a note in the torrc about abuse potential with the default
27008 - Revise control spec and implementation to allow all log messages to
27009 be sent to controller with their severities intact (suggested by
27010 Matt Edman). Update TorControl to handle new log event types.
27011 - Provide better explanation messages when controller's POSTDESCRIPTOR
27013 - Stop putting nodename in the Platform string in server descriptors.
27014 It doesn't actually help, and it is confusing/upsetting some people.
27016 o Bugfixes on 0.1.0.2-rc:
27017 - We were printing the host mask wrong in exit policies in server
27018 descriptors. This isn't a critical bug though, since we were still
27019 obeying the exit policy internally.
27020 - Fix Tor when compiled with libevent but without pthreads: move
27021 connection_unregister() from _connection_free() to
27023 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
27024 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
27025 when we look through the connection array, we'll find any of the
27026 cpu/dnsworkers. This is no good.
27028 o Bugfixes on 0.0.9.8:
27029 - Fix possible bug on threading platforms (e.g. win32) which was
27030 leaking a file descriptor whenever a cpuworker or dnsworker died.
27031 - When using preferred entry or exit nodes, ignore whether the
27032 circuit wants uptime or capacity. They asked for the nodes, they
27034 - chdir() to your datadirectory at the *end* of the daemonize process,
27035 not the beginning. This was a problem because the first time you
27036 run tor, if your datadir isn't there, and you have runasdaemon set
27037 to 1, it will try to chdir to it before it tries to create it. Oops.
27038 - Handle changed router status correctly when dirserver reloads
27039 fingerprint file. We used to be dropping all unverified descriptors
27040 right then. The bug was hidden because we would immediately
27041 fetch a directory from another dirserver, which would include the
27042 descriptors we just dropped.
27043 - When we're connecting to an OR and he's got a different nickname/key
27044 than we were expecting, only complain loudly if we're an OP or a
27045 dirserver. Complaining loudly to the OR admins just confuses them.
27046 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
27047 artificially capped at 500kB.
27050 Changes in version 0.0.9.8 - 2005-04-07
27051 o Bugfixes on 0.0.9.x:
27052 - We have a bug that I haven't found yet. Sometimes, very rarely,
27053 cpuworkers get stuck in the 'busy' state, even though the cpuworker
27054 thinks of itself as idle. This meant that no new circuits ever got
27055 established. Here's a workaround to kill any cpuworker that's been
27056 busy for more than 100 seconds.
27059 Changes in version 0.1.0.2-rc - 2005-04-01
27060 o Bugfixes on 0.1.0.1-rc:
27061 - Fixes on reachability detection:
27062 - Don't check for reachability while hibernating.
27063 - If ORPort is reachable but DirPort isn't, still publish the
27064 descriptor, but zero out DirPort until it's found reachable.
27065 - When building testing circs for ORPort testing, use only
27066 high-bandwidth nodes, so fewer circuits fail.
27067 - Complain about unreachable ORPort separately from unreachable
27068 DirPort, so the user knows what's going on.
27069 - Make sure we only conclude ORPort reachability if we didn't
27070 initiate the conn. Otherwise we could falsely conclude that
27071 we're reachable just because we connected to the guy earlier
27072 and he used that same pipe to extend to us.
27073 - Authdirservers shouldn't do ORPort reachability detection,
27074 since they're in clique mode, so it will be rare to find a
27075 server not already connected to them.
27076 - When building testing circuits, always pick middle hops running
27077 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
27078 bug. (This is a kludge; it will go away when 0.0.9.x becomes
27080 - When we decide we're reachable, actually publish our descriptor
27082 - Fix bug in redirectstream in the controller.
27083 - Fix the state descriptor strings so logs don't claim edge streams
27084 are in a different state than they actually are.
27085 - Use recent libevent features when possible (this only really affects
27086 win32 and osx right now, because the new libevent with these
27087 features hasn't been released yet). Add code to suppress spurious
27089 - Prevent possible segfault in connection_close_unattached_ap().
27090 - Fix newlines on torrc in win32.
27091 - Improve error msgs when tor-resolve fails.
27093 o Improvements on 0.0.9.x:
27094 - New experimental script tor/contrib/ExerciseServer.py (needs more
27095 work) that uses the controller interface to build circuits and
27096 fetch pages over them. This will help us bootstrap servers that
27097 have lots of capacity but haven't noticed it yet.
27098 - New experimental script tor/contrib/PathDemo.py (needs more work)
27099 that uses the controller interface to let you choose whole paths
27101 "<hostname>.<path,separated by dots>.<length of path>.path"
27102 - When we've connected to an OR and handshaked but didn't like
27103 the result, we were closing the conn without sending destroy
27104 cells back for pending circuits. Now send those destroys.
27107 Changes in version 0.0.9.7 - 2005-04-01
27108 o Bugfixes on 0.0.9.x:
27109 - Fix another race crash bug (thanks to Glenn Fink for reporting).
27110 - Compare identity to identity, not to nickname, when extending to
27111 a router not already in the directory. This was preventing us from
27112 extending to unknown routers. Oops.
27113 - Make sure to create OS X Tor user in <500 range, so we aren't
27114 creating actual system users.
27115 - Note where connection-that-hasn't-sent-end was marked, and fix
27116 a few really loud instances of this harmless bug (it's fixed more
27120 Changes in version 0.1.0.1-rc - 2005-03-28
27122 - Add reachability testing. Your Tor server will automatically try
27123 to see if its ORPort and DirPort are reachable from the outside,
27124 and it won't upload its descriptor until it decides they are.
27125 - Handle unavailable hidden services better. Handle slow or busy
27126 hidden services better.
27127 - Add support for CONNECTing through https proxies, with "HttpsProxy"
27129 - New exit policy: accept most low-numbered ports, rather than
27130 rejecting most low-numbered ports.
27131 - More Tor controller support (still experimental). See
27132 http://tor.eff.org/doc/control-spec.txt for all the new features,
27133 including signals to emulate unix signals from any platform;
27134 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
27135 closestream; closecircuit; etc.
27136 - Make nt services work and start on startup on win32 (based on
27137 patch by Matt Edman).
27138 - Add a new AddressMap config directive to rewrite incoming socks
27139 addresses. This lets you, for example, declare an implicit
27140 required exit node for certain sites.
27141 - Add a new TrackHostExits config directive to trigger addressmaps
27142 for certain incoming socks addresses -- for sites that break when
27143 your exit keeps changing (based on patch by Mike Perry).
27144 - Redo the client-side dns cache so it's just an addressmap too.
27145 - Notice when our IP changes, and reset stats/uptime/reachability.
27146 - When an application is using socks5, give him the whole variety of
27147 potential socks5 responses (connect refused, host unreachable, etc),
27148 rather than just "success" or "failure".
27149 - A more sane version numbering system. See
27150 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
27151 - New contributed script "exitlist": a simple python script to
27152 parse directories and find Tor nodes that exit to listed
27154 - New contributed script "privoxy-tor-toggle" to toggle whether
27155 Privoxy uses Tor. Seems to be configured for Debian by default.
27156 - Report HTTP reasons to client when getting a response from directory
27157 servers -- so you can actually know what went wrong.
27158 - New config option MaxAdvertisedBandwidth which lets you advertise
27159 a low bandwidthrate (to not attract as many circuits) while still
27160 allowing a higher bandwidthrate in reality.
27162 o Robustness/stability fixes:
27163 - Make Tor use Niels Provos's libevent instead of its current
27164 poll-but-sometimes-select mess. This will let us use faster async
27165 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
27167 - pthread support now too. This was forced because when we forked,
27168 we ended up wasting a lot of duplicate ram over time. Also switch
27169 to foo_r versions of some library calls to allow reentry and
27171 - Better handling for heterogeneous / unreliable nodes:
27172 - Annotate circuits w/ whether they aim to contain high uptime nodes
27173 and/or high capacity nodes. When building circuits, choose
27175 - This means that every single node in an intro rend circuit,
27176 not just the last one, will have a minimum uptime.
27177 - New config option LongLivedPorts to indicate application streams
27178 that will want high uptime circuits.
27179 - Servers reset uptime when a dir fetch entirely fails. This
27180 hopefully reflects stability of the server's network connectivity.
27181 - If somebody starts his tor server in Jan 2004 and then fixes his
27182 clock, don't make his published uptime be a year.
27183 - Reset published uptime when you wake up from hibernation.
27184 - Introduce a notion of 'internal' circs, which are chosen without
27185 regard to the exit policy of the last hop. Intro and rendezvous
27186 circs must be internal circs, to avoid leaking information. Resolve
27187 and connect streams can use internal circs if they want.
27188 - New circuit pooling algorithm: make sure to have enough circs around
27189 to satisfy any predicted ports, and also make sure to have 2 internal
27190 circs around if we've required internal circs lately (and with high
27191 uptime if we've seen that lately too).
27192 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
27193 which describes how often we retry making new circuits if current
27194 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
27195 how long we're willing to make use of an already-dirty circuit.
27196 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
27197 circ as necessary, if there are any completed ones lying around
27198 when we try to launch one.
27199 - Make hidden services try to establish a rendezvous for 30 seconds,
27200 rather than for n (where n=3) attempts to build a circuit.
27201 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
27202 "ShutdownWaitLength".
27203 - Try to be more zealous about calling connection_edge_end when
27204 things go bad with edge conns in connection.c.
27205 - Revise tor-spec to add more/better stream end reasons.
27206 - Revise all calls to connection_edge_end to avoid sending "misc",
27207 and to take errno into account where possible.
27210 - Fix a race condition that can trigger an assert, when we have a
27211 pending create cell and an OR connection fails right then.
27212 - Fix several double-mark-for-close bugs, e.g. where we were finding
27213 a conn for a cell even if that conn is already marked for close.
27214 - Make sequence of log messages when starting on win32 with no config
27215 file more reasonable.
27216 - When choosing an exit node for a new non-internal circ, don't take
27217 into account whether it'll be useful for any pending x.onion
27218 addresses -- it won't.
27219 - Turn addr_policy_compare from a tristate to a quadstate; this should
27220 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
27221 for google.com" problem.
27222 - Make "platform" string in descriptor more accurate for Win32 servers,
27223 so it's not just "unknown platform".
27224 - Fix an edge case in parsing config options (thanks weasel).
27225 If they say "--" on the commandline, it's not an option.
27226 - Reject odd-looking addresses at the client (e.g. addresses that
27227 contain a colon), rather than having the server drop them because
27229 - tor-resolve requests were ignoring .exit if there was a working circuit
27230 they could use instead.
27231 - REUSEADDR on normal platforms means you can rebind to the port
27232 right after somebody else has let it go. But REUSEADDR on win32
27233 means to let you bind to the port _even when somebody else
27234 already has it bound_! So, don't do that on Win32.
27235 - Change version parsing logic: a version is "obsolete" if it is not
27236 recommended and (1) there is a newer recommended version in the
27237 same series, or (2) there are no recommended versions in the same
27238 series, but there are some recommended versions in a newer series.
27239 A version is "new" if it is newer than any recommended version in
27241 - Stop most cases of hanging up on a socks connection without sending
27245 - Require BandwidthRate to be at least 20kB/s for servers.
27246 - When a dirserver causes you to give a warn, mention which dirserver
27248 - New config option DirAllowPrivateAddresses for authdirservers.
27249 Now by default they refuse router descriptors that have non-IP or
27250 private-IP addresses.
27251 - Stop publishing socksport in the directory, since it's not
27252 actually meant to be public. For compatibility, publish a 0 there
27254 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
27255 smart" value, that is low for servers and high for clients.
27256 - If our clock jumps forward by 100 seconds or more, assume something
27257 has gone wrong with our network and abandon all not-yet-used circs.
27258 - Warn when exit policy implicitly allows local addresses.
27259 - If we get an incredibly skewed timestamp from a dirserver mirror
27260 that isn't a verified OR, don't warn -- it's probably him that's
27262 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
27263 cookies to disk and doesn't log each web request to disk. (Thanks
27264 to Brett Carrington for pointing this out.)
27265 - When a client asks us for a dir mirror and we don't have one,
27266 launch an attempt to get a fresh one.
27267 - If we're hibernating and we get a SIGINT, exit immediately.
27268 - Add --with-dmalloc ./configure option, to track memory leaks.
27269 - And try to free all memory on closing, so we can detect what
27271 - Cache local dns resolves correctly even when they're .exit
27273 - Give a better warning when some other server advertises an
27274 ORPort that is actually an apache running ssl.
27275 - Add "opt hibernating 1" to server descriptor to make it clearer
27276 whether the server is hibernating.
27279 Changes in version 0.0.9.6 - 2005-03-24
27280 o Bugfixes on 0.0.9.x (crashes and asserts):
27281 - Add new end stream reasons to maintenance branch. Fix bug where
27282 reason (8) could trigger an assert. Prevent bug from recurring.
27283 - Apparently win32 stat wants paths to not end with a slash.
27284 - Fix assert triggers in assert_cpath_layer_ok(), where we were
27285 blowing away the circuit that conn->cpath_layer points to, then
27286 checking to see if the circ is well-formed. Backport check to make
27287 sure we dont use the cpath on a closed connection.
27288 - Prevent circuit_resume_edge_reading_helper() from trying to package
27289 inbufs for marked-for-close streams.
27290 - Don't crash on hup if your options->address has become unresolvable.
27291 - Some systems (like OS X) sometimes accept() a connection and tell
27292 you the remote host is 0.0.0.0:0. If this happens, due to some
27293 other mis-features, we get confused; so refuse the conn for now.
27295 o Bugfixes on 0.0.9.x (other):
27296 - Fix harmless but scary "Unrecognized content encoding" warn message.
27297 - Add new stream error reason: TORPROTOCOL reason means "you are not
27298 speaking a version of Tor I understand; say bye-bye to your stream."
27299 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
27300 into the future, now that we are more tolerant of skew. This
27301 resolves a bug where a Tor server would refuse to cache a directory
27302 because all the directories it gets are too far in the future;
27303 yet the Tor server never logs any complaints about clock skew.
27304 - Mac packaging magic: make man pages useable, and do not overwrite
27305 existing torrc files.
27306 - Make OS X log happily to /var/log/tor/tor.log
27309 Changes in version 0.0.9.5 - 2005-02-22
27310 o Bugfixes on 0.0.9.x:
27311 - Fix an assert race at exit nodes when resolve requests fail.
27312 - Stop picking unverified dir mirrors--it only leads to misery.
27313 - Patch from Matt Edman to make NT services work better. Service
27314 support is still not compiled into the executable by default.
27315 - Patch from Dmitri Bely so the Tor service runs better under
27316 the win32 SYSTEM account.
27317 - Make tor-resolve actually work (?) on Win32.
27318 - Fix a sign bug when getrlimit claims to have 4+ billion
27319 file descriptors available.
27320 - Stop refusing to start when bandwidthburst == bandwidthrate.
27321 - When create cells have been on the onion queue more than five
27322 seconds, just send back a destroy and take them off the list.
27325 Changes in version 0.0.9.4 - 2005-02-03
27326 o Bugfixes on 0.0.9:
27327 - Fix an assert bug that took down most of our servers: when
27328 a server claims to have 1 GB of bandwidthburst, don't
27330 - Don't crash as badly if we have spawned the max allowed number
27331 of dnsworkers, or we're out of file descriptors.
27332 - Block more file-sharing ports in the default exit policy.
27333 - MaxConn is now automatically set to the hard limit of max
27334 file descriptors we're allowed (ulimit -n), minus a few for
27336 - Give a clearer message when servers need to raise their
27337 ulimit -n when they start running out of file descriptors.
27338 - SGI Compatibility patches from Jan Schaumann.
27339 - Tolerate a corrupt cached directory better.
27340 - When a dirserver hasn't approved your server, list which one.
27341 - Go into soft hibernation after 95% of the bandwidth is used,
27342 not 99%. This is especially important for daily hibernators who
27343 have a small accounting max. Hopefully it will result in fewer
27344 cut connections when the hard hibernation starts.
27345 - Load-balance better when using servers that claim more than
27346 800kB/s of capacity.
27347 - Make NT services work (experimental, only used if compiled in).
27350 Changes in version 0.0.9.3 - 2005-01-21
27351 o Bugfixes on 0.0.9:
27352 - Backport the cpu use fixes from main branch, so busy servers won't
27353 need as much processor time.
27354 - Work better when we go offline and then come back, or when we
27355 run Tor at boot before the network is up. We do this by
27356 optimistically trying to fetch a new directory whenever an
27357 application request comes in and we think we're offline -- the
27358 human is hopefully a good measure of when the network is back.
27359 - Backport some minimal hidserv bugfixes: keep rend circuits open as
27360 long as you keep using them; actually publish hidserv descriptors
27361 shortly after they change, rather than waiting 20-40 minutes.
27362 - Enable Mac startup script by default.
27363 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
27364 - When you update AllowUnverifiedNodes or FirewallPorts via the
27365 controller's setconf feature, we were always appending, never
27367 - When you update HiddenServiceDir via setconf, it was screwing up
27368 the order of reading the lines, making it fail.
27369 - Do not rewrite a cached directory back to the cache; otherwise we
27370 will think it is recent and not fetch a newer one on startup.
27371 - Workaround for webservers that lie about Content-Encoding: Tor
27372 now tries to autodetect compressed directories and compression
27373 itself. This lets us Proxypass dir fetches through apache.
27376 Changes in version 0.0.9.2 - 2005-01-04
27377 o Bugfixes on 0.0.9 (crashes and asserts):
27378 - Fix an assert on startup when the disk is full and you're logging
27380 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
27381 style address, then we'd crash.
27382 - Fix an assert trigger when the running-routers string we get from
27383 a dirserver is broken.
27384 - Make worker threads start and run on win32. Now win32 servers
27386 - Bandaid (not actually fix, but now it doesn't crash) an assert
27387 where the dns worker dies mysteriously and the main Tor process
27388 doesn't remember anything about the address it was resolving.
27390 o Bugfixes on 0.0.9 (Win32):
27391 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
27392 name out of the warning/assert messages.
27393 - Fix a superficial "unhandled error on read" bug on win32.
27394 - The win32 installer no longer requires a click-through for our
27395 license, since our Free Software license grants rights but does not
27397 - Win32: When connecting to a dirserver fails, try another one
27398 immediately. (This was already working for non-win32 Tors.)
27399 - Stop trying to parse $HOME on win32 when hunting for default
27401 - Make tor-resolve.c work on win32 by calling network_init().
27403 o Bugfixes on 0.0.9 (other):
27404 - Make 0.0.9.x build on Solaris again.
27405 - Due to a fencepost error, we were blowing away the \n when reporting
27406 confvalue items in the controller. So asking for multiple config
27407 values at once couldn't work.
27408 - When listing circuits that are pending on an opening OR connection,
27409 if we're an OR we were listing circuits that *end* at us as
27410 being pending on every listener, dns/cpu worker, etc. Stop that.
27411 - Dirservers were failing to create 'running-routers' or 'directory'
27412 strings if we had more than some threshold of routers. Fix them so
27413 they can handle any number of routers.
27414 - Fix a superficial "Duplicate mark for close" bug.
27415 - Stop checking for clock skew for OR connections, even for servers.
27416 - Fix a fencepost error that was chopping off the last letter of any
27417 nickname that is the maximum allowed nickname length.
27418 - Update URLs in log messages so they point to the new website.
27419 - Fix a potential problem in mangling server private keys while
27420 writing to disk (not triggered yet, as far as we know).
27421 - Include the licenses for other free software we include in Tor,
27422 now that we're shipping binary distributions more regularly.
27425 Changes in version 0.0.9.1 - 2004-12-15
27426 o Bugfixes on 0.0.9:
27427 - Make hibernation actually work.
27428 - Make HashedControlPassword config option work.
27429 - When we're reporting event circuit status to a controller,
27430 don't use the stream status code.
27433 Changes in version 0.0.9 - 2004-12-12
27435 - Clean up manpage and torrc.sample file.
27436 - Clean up severities and text of log warnings.
27438 - Make servers trigger an assert when they enter hibernation.
27441 Changes in version 0.0.9rc7 - 2004-12-08
27442 o Bugfixes on 0.0.9rc:
27443 - Fix a stack-trashing crash when an exit node begins hibernating.
27444 - Avoid looking at unallocated memory while considering which
27445 ports we need to build circuits to cover.
27446 - Stop a sigpipe: when an 'end' cell races with eof from the app,
27447 we shouldn't hold-open-until-flush if the eof arrived first.
27448 - Fix a bug with init_cookie_authentication() in the controller.
27449 - When recommending new-format log lines, if the upper bound is
27450 LOG_ERR, leave it implicit.
27452 o Bugfixes on 0.0.8.1:
27453 - Fix a whole slew of memory leaks.
27454 - Fix isspace() and friends so they still make Solaris happy
27455 but also so they don't trigger asserts on win32.
27456 - Fix parse_iso_time on platforms without strptime (eg win32).
27457 - win32: tolerate extra "readable" events better.
27458 - win32: when being multithreaded, leave parent fdarray open.
27459 - Make unit tests work on win32.
27462 Changes in version 0.0.9rc6 - 2004-12-06
27463 o Bugfixes on 0.0.9pre:
27464 - Clean up some more integer underflow opportunities (not exploitable
27466 - While hibernating, hup should not regrow our listeners.
27467 - Send an end to the streams we close when we hibernate, rather
27468 than just chopping them off.
27469 - React to eof immediately on non-open edge connections.
27471 o Bugfixes on 0.0.8.1:
27472 - Calculate timeout for waiting for a connected cell from the time
27473 we sent the begin cell, not from the time the stream started. If
27474 it took a long time to establish the circuit, we would time out
27475 right after sending the begin cell.
27476 - Fix router_compare_addr_to_addr_policy: it was not treating a port
27477 of * as always matching, so we were picking reject *:* nodes as
27478 exit nodes too. Oops.
27481 - New circuit building strategy: keep a list of ports that we've
27482 used in the past 6 hours, and always try to have 2 circuits open
27483 or on the way that will handle each such port. Seed us with port
27484 80 so web users won't complain that Tor is "slow to start up".
27485 - Make kill -USR1 dump more useful stats about circuits.
27486 - When warning about retrying or giving up, print the address, so
27487 the user knows which one it's talking about.
27488 - If you haven't used a clean circuit in an hour, throw it away,
27489 just to be on the safe side. (This means after 6 hours a totally
27490 unused Tor client will have no circuits open.)
27493 Changes in version 0.0.9rc5 - 2004-12-01
27494 o Bugfixes on 0.0.8.1:
27495 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
27496 - Let resolve conns retry/expire also, rather than sticking around
27498 - If we are using select, make sure we stay within FD_SETSIZE.
27500 o Bugfixes on 0.0.9pre:
27501 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
27502 but doesn't seem to be currently; thanks to Ilja van Sprundel for
27504 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
27505 instead. Impose minima and maxima for all *Period options; impose
27506 even tighter maxima for fetching if we are a caching dirserver.
27507 Clip rather than rejecting.
27508 - Fetch cached running-routers from servers that serve it (that is,
27509 authdirservers and servers running 0.0.9rc5-cvs or later.)
27512 - Accept *:706 (silc) in default exit policy.
27513 - Implement new versioning format for post 0.1.
27514 - Support "foo.nickname.exit" addresses, to let Alice request the
27515 address "foo" as viewed by exit node "nickname". Based on a patch
27517 - Make tor --version --version dump the cvs Id of every file.
27520 Changes in version 0.0.9rc4 - 2004-11-28
27521 o Bugfixes on 0.0.8.1:
27522 - Make windows sockets actually non-blocking (oops), and handle
27523 win32 socket errors better.
27525 o Bugfixes on 0.0.9rc1:
27526 - Actually catch the -USR2 signal.
27529 Changes in version 0.0.9rc3 - 2004-11-25
27530 o Bugfixes on 0.0.8.1:
27531 - Flush the log file descriptor after we print "Tor opening log file",
27532 so we don't see those messages days later.
27534 o Bugfixes on 0.0.9rc1:
27535 - Make tor-resolve work again.
27536 - Avoid infinite loop in tor-resolve if tor hangs up on it.
27537 - Fix an assert trigger for clients/servers handling resolves.
27540 Changes in version 0.0.9rc2 - 2004-11-24
27541 o Bugfixes on 0.0.9rc1:
27542 - I broke socks5 support while fixing the eof bug.
27543 - Allow unitless bandwidths and intervals; they default to bytes
27545 - New servers don't start out hibernating; they are active until
27546 they run out of bytes, so they have a better estimate of how
27547 long it takes, and so their operators can know they're working.
27550 Changes in version 0.0.9rc1 - 2004-11-23
27551 o Bugfixes on 0.0.8.1:
27552 - Finally fix a bug that's been plaguing us for a year:
27553 With high load, circuit package window was reaching 0. Whenever
27554 we got a circuit-level sendme, we were reading a lot on each
27555 socket, but only writing out a bit. So we would eventually reach
27556 eof. This would be noticed and acted on even when there were still
27557 bytes sitting in the inbuf.
27558 - When poll() is interrupted, we shouldn't believe the revents values.
27560 o Bugfixes on 0.0.9pre6:
27561 - Fix hibernate bug that caused pre6 to be broken.
27562 - Don't keep rephist info for routers that haven't had activity for
27563 24 hours. (This matters now that clients have keys, since we track
27565 - Never call close_temp_logs while validating log options.
27566 - Fix backslash-escaping on tor.sh.in and torctl.in.
27569 - Implement weekly/monthly/daily accounting: now you specify your
27570 hibernation properties by
27571 AccountingMax N bytes|KB|MB|GB|TB
27572 AccountingStart day|week|month [day] HH:MM
27573 Defaults to "month 1 0:00".
27574 - Let bandwidth and interval config options be specified as 5 bytes,
27575 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
27576 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
27577 get back to normal.)
27578 - If your requested entry or exit node has advertised bandwidth 0,
27580 - Be more greedy about filling up relay cells -- we try reading again
27581 once we've processed the stuff we read, in case enough has arrived
27582 to fill the last cell completely.
27583 - Apply NT service patch from Osamu Fujino. Still needs more work.
27586 Changes in version 0.0.9pre6 - 2004-11-15
27587 o Bugfixes on 0.0.8.1:
27588 - Fix assert failure on malformed socks4a requests.
27589 - Use identity comparison, not nickname comparison, to choose which
27590 half of circuit-ID-space each side gets to use. This is needed
27591 because sometimes we think of a router as a nickname, and sometimes
27592 as a hex ID, and we can't predict what the other side will do.
27593 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
27594 write() call will fail and we handle it there.
27595 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
27596 and smartlist_len, which are two major profiling offenders.
27598 o Bugfixes on 0.0.9pre5:
27599 - Fix a bug in read_all that was corrupting config files on windows.
27600 - When we're raising the max number of open file descriptors to
27601 'unlimited', don't log that we just raised it to '-1'.
27602 - Include event code with events, as required by control-spec.txt.
27603 - Don't give a fingerprint when clients do --list-fingerprint:
27604 it's misleading, because it will never be the same again.
27605 - Stop using strlcpy in tor_strndup, since it was slowing us
27607 - Remove warn on startup about missing cached-directory file.
27608 - Make kill -USR1 work again.
27609 - Hibernate if we start tor during the "wait for wakeup-time" phase
27610 of an accounting interval. Log our hibernation plans better.
27611 - Authoritative dirservers now also cache their directory, so they
27612 have it on start-up.
27615 - Fetch running-routers; cache running-routers; compress
27616 running-routers; serve compressed running-routers.z
27617 - Add NSI installer script contributed by J Doe.
27618 - Commit VC6 and VC7 workspace/project files.
27619 - Commit a tor.spec for making RPM files, with help from jbash.
27620 - Add contrib/torctl.in contributed by Glenn Fink.
27621 - Implement the control-spec's SAVECONF command, to write your
27622 configuration to torrc.
27623 - Get cookie authentication for the controller closer to working.
27624 - Include control-spec.txt in the tarball.
27625 - When set_conf changes our server descriptor, upload a new copy.
27626 But don't upload it too often if there are frequent changes.
27627 - Document authentication config in man page, and document signals
27629 - Clean up confusing parts of man page and torrc.sample.
27630 - Make expand_filename handle ~ and ~username.
27631 - Use autoconf to enable largefile support where necessary. Use
27632 ftello where available, since ftell can fail at 2GB.
27633 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
27634 log more informatively.
27635 - Give a slightly more useful output for "tor -h".
27636 - Refuse application socks connections to port 0.
27637 - Check clock skew for verified servers, but allow unverified
27638 servers and clients to have any clock skew.
27639 - Break DirFetchPostPeriod into:
27640 - DirFetchPeriod for fetching full directory,
27641 - StatusFetchPeriod for fetching running-routers,
27642 - DirPostPeriod for posting server descriptor,
27643 - RendPostPeriod for posting hidden service descriptors.
27644 - Make sure the hidden service descriptors are at a random offset
27645 from each other, to hinder linkability.
27648 Changes in version 0.0.9pre5 - 2004-11-09
27649 o Bugfixes on 0.0.9pre4:
27650 - Fix a seg fault in unit tests (doesn't affect main program).
27651 - Fix an assert bug where a hidden service provider would fail if
27652 the first hop of his rendezvous circuit was down.
27653 - Hidden service operators now correctly handle version 1 style
27654 INTRODUCE1 cells (nobody generates them still, so not a critical
27656 - If do_hup fails, actually notice.
27657 - Handle more errnos from accept() without closing the listener.
27658 Some OpenBSD machines were closing their listeners because
27659 they ran out of file descriptors.
27660 - Send resolve cells to exit routers that are running a new
27661 enough version of the resolve code to work right.
27662 - Better handling of winsock includes on non-MSV win32 compilers.
27663 - Some people had wrapped their tor client/server in a script
27664 that would restart it whenever it died. This did not play well
27665 with our "shut down if your version is obsolete" code. Now people
27666 don't fetch a new directory if their local cached version is
27668 - Make our autogen.sh work on ksh as well as bash.
27671 - Hibernation: New config option "AccountingMaxKB" lets you
27672 set how many KBytes per month you want to allow your server to
27673 consume. Rather than spreading those bytes out evenly over the
27674 month, we instead hibernate for some of the month and pop up
27675 at a deterministic time, work until the bytes are consumed, then
27676 hibernate again. Config option "MonthlyAccountingStart" lets you
27677 specify which day of the month your billing cycle starts on.
27678 - Control interface: a separate program can now talk to your
27679 client/server over a socket, and get/set config options, receive
27680 notifications of circuits and streams starting/finishing/dying,
27681 bandwidth used, etc. The next step is to get some GUIs working.
27682 Let us know if you want to help out. See doc/control-spec.txt .
27683 - Ship a contrib/tor-control.py as an example script to interact
27684 with the control port.
27685 - "tor --hash-password zzyxz" will output a salted password for
27686 use in authenticating to the control interface.
27687 - New log format in config:
27688 "Log minsev[-maxsev] stdout|stderr|syslog" or
27689 "Log minsev[-maxsev] file /var/foo"
27692 - DirPolicy config option, to let people reject incoming addresses
27693 from their dirserver.
27694 - "tor --list-fingerprint" will list your identity key fingerprint
27696 - Add "pass" target for RedirectExit, to make it easier to break
27697 out of a sequence of RedirectExit rules.
27698 - Clients now generate a TLS cert too, in preparation for having
27699 them act more like real nodes.
27700 - Ship src/win32/ in the tarball, so people can use it to build.
27701 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
27703 - New "router-status" line in directory, to better bind each verified
27704 nickname to its identity key.
27705 - Deprecate unofficial config option abbreviations, and abbreviations
27706 not on the command line.
27707 - Add a pure-C tor-resolve implementation.
27708 - Use getrlimit and friends to ensure we can reach MaxConn (currently
27709 1024) file descriptors.
27711 o Code security improvements, inspired by Ilja:
27712 - Replace sprintf with snprintf. (I think they were all safe, but
27714 - Replace strcpy/strncpy with strlcpy in more places.
27715 - Avoid strcat; use snprintf or strlcat instead.
27716 - snprintf wrapper with consistent (though not C99) overflow behavior.
27719 Changes in version 0.0.9pre4 - 2004-10-17
27720 o Bugfixes on 0.0.9pre3:
27721 - If the server doesn't specify an exit policy, use the real default
27722 exit policy, not reject *:*.
27723 - Ignore fascistfirewall when uploading/downloading hidden service
27724 descriptors, since we go through Tor for those; and when using
27725 an HttpProxy, since we assume it can reach them all.
27726 - When looking for an authoritative dirserver, use only the ones
27727 configured at boot. Don't bother looking in the directory.
27728 - The rest of the fix for get_default_conf_file() on older win32.
27729 - Make 'Routerfile' config option obsolete.
27732 - New 'MyFamily nick1,...' config option for a server to
27733 specify other servers that shouldn't be used in the same circuit
27734 with it. Only believed if nick1 also specifies us.
27735 - New 'NodeFamily nick1,nick2,...' config option for a client to
27736 specify nodes that it doesn't want to use in the same circuit.
27737 - New 'Redirectexit pattern address:port' config option for a
27738 server to redirect exit connections, e.g. to a local squid.
27741 Changes in version 0.0.9pre3 - 2004-10-13
27742 o Bugfixes on 0.0.8.1:
27743 - Better torrc example lines for dirbindaddress and orbindaddress.
27744 - Improved bounds checking on parsed ints (e.g. config options and
27745 the ones we find in directories.)
27746 - Better handling of size_t vs int, so we're more robust on 64
27748 - Fix the rest of the bug where a newly started OR would appear
27749 as unverified even after we've added his fingerprint and hupped
27751 - Fix a bug from 0.0.7: when read() failed on a stream, we would
27752 close it without sending back an end. So 'connection refused'
27753 would simply be ignored and the user would get no response.
27755 o Bugfixes on 0.0.9pre2:
27756 - Serving the cached-on-disk directory to people is bad. We now
27757 provide no directory until we've fetched a fresh one.
27758 - Workaround for bug on windows where cached-directories get crlf
27760 - Make get_default_conf_file() work on older windows too.
27761 - If we write a *:* exit policy line in the descriptor, don't write
27762 any more exit policy lines.
27765 - Use only 0.0.9pre1 and later servers for resolve cells.
27766 - Make the dirservers file obsolete.
27767 - Include a dir-signing-key token in directories to tell the
27768 parsing entity which key is being used to sign.
27769 - Remove the built-in bulky default dirservers string.
27770 - New config option "Dirserver %s:%d [fingerprint]", which can be
27771 repeated as many times as needed. If no dirservers specified,
27772 default to moria1,moria2,tor26.
27773 - Make moria2 advertise a dirport of 80, so people behind firewalls
27774 will be able to get a directory.
27775 - Http proxy support
27776 - Dirservers translate requests for http://%s:%d/x to /x
27777 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
27778 be routed through this host.
27779 - Clients ask for /tor/x rather than /x for new enough dirservers.
27780 This way we can one day coexist peacefully with apache.
27781 - Clients specify a "Host: %s%d" http header, to be compatible
27782 with more proxies, and so running squid on an exit node can work.
27785 Changes in version 0.0.8.1 - 2004-10-13
27787 - Fix a seg fault that can be triggered remotely for Tor
27788 clients/servers with an open dirport.
27789 - Fix a rare assert trigger, where routerinfos for entries in
27790 our cpath would expire while we're building the path.
27791 - Fix a bug in OutboundBindAddress so it (hopefully) works.
27792 - Fix a rare seg fault for people running hidden services on
27793 intermittent connections.
27794 - Fix a bug in parsing opt keywords with objects.
27795 - Fix a stale pointer assert bug when a stream detaches and
27797 - Fix a string format vulnerability (probably not exploitable)
27798 in reporting stats locally.
27799 - Fix an assert trigger: sometimes launching circuits can fail
27800 immediately, e.g. because too many circuits have failed recently.
27801 - Fix a compile warning on 64 bit platforms.
27804 Changes in version 0.0.9pre2 - 2004-10-03
27806 - Make fetching a cached directory work for 64-bit platforms too.
27807 - Make zlib.h a required header, not an optional header.
27810 Changes in version 0.0.9pre1 - 2004-10-01
27812 - Stop using separate defaults for no-config-file and
27813 empty-config-file. Now you have to explicitly turn off SocksPort,
27814 if you don't want it open.
27815 - Fix a bug in OutboundBindAddress so it (hopefully) works.
27816 - Improve man page to mention more of the 0.0.8 features.
27817 - Fix a rare seg fault for people running hidden services on
27818 intermittent connections.
27819 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
27821 - Fix more dns related bugs: send back resolve_failed and end cells
27822 more reliably when the resolve fails, rather than closing the
27823 circuit and then trying to send the cell. Also attach dummy resolve
27824 connections to a circuit *before* calling dns_resolve(), to fix
27825 a bug where cached answers would never be sent in RESOLVED cells.
27826 - When we run out of disk space, or other log writing error, don't
27827 crash. Just stop logging to that log and continue.
27828 - We were starting to daemonize before we opened our logs, so if
27829 there were any problems opening logs, we would complain to stderr,
27830 which wouldn't work, and then mysteriously exit.
27831 - Fix a rare bug where sometimes a verified OR would connect to us
27832 before he'd uploaded his descriptor, which would cause us to
27833 assign conn->nickname as though he's unverified. Now we look through
27834 the fingerprint list to see if he's there.
27835 - Fix a rare assert trigger, where routerinfos for entries in
27836 our cpath would expire while we're building the path.
27839 - Clients can ask dirservers for /dir.z to get a compressed version
27840 of the directory. Only works for servers running 0.0.9, of course.
27841 - Make clients cache directories and use them to seed their router
27842 lists at startup. This means clients have a datadir again.
27843 - Configuration infrastructure support for warning on obsolete
27845 - Respond to content-encoding headers by trying to uncompress as
27847 - Reply with a deflated directory when a client asks for "dir.z".
27848 We could use allow-encodings instead, but allow-encodings isn't
27849 specified in HTTP 1.0.
27850 - Raise the max dns workers from 50 to 100.
27851 - Discourage people from setting their dirfetchpostperiod more often
27852 than once per minute.
27853 - Protect dirservers from overzealous descriptor uploading -- wait
27854 10 seconds after directory gets dirty, before regenerating.
27857 Changes in version 0.0.8 - 2004-08-25
27858 o Port it to SunOS 5.9 / Athena
27861 Changes in version 0.0.8rc2 - 2004-08-20
27862 o Make it compile on cygwin again.
27863 o When picking unverified routers, skip those with low uptime and/or
27864 low bandwidth, depending on what properties you care about.
27867 Changes in version 0.0.8rc1 - 2004-08-18
27868 o Changes from 0.0.7.3:
27870 - Fix assert triggers: if the other side returns an address 0.0.0.0,
27871 don't put it into the client dns cache.
27872 - If a begin failed due to exit policy, but we believe the IP address
27873 should have been allowed, switch that router to exitpolicy reject *:*
27874 until we get our next directory.
27876 - Clients choose nodes proportional to advertised bandwidth.
27877 - Avoid using nodes with low uptime as introduction points.
27878 - Handle servers with dynamic IP addresses: don't replace
27879 options->Address with the resolved one at startup, and
27880 detect our address right before we make a routerinfo each time.
27881 - 'FascistFirewall' option to pick dirservers and ORs on specific
27882 ports; plus 'FirewallPorts' config option to tell FascistFirewall
27883 which ports are open. (Defaults to 80,443)
27884 - Be more aggressive about trying to make circuits when the network
27885 has changed (e.g. when you unsuspend your laptop).
27886 - Check for time skew on http headers; report date in response to
27888 - If the entrynode config line has only one node, don't pick it as
27890 - Add strict{entry|exit}nodes config options. If set to 1, then
27891 we refuse to build circuits that don't include the specified entry
27893 - OutboundBindAddress config option, to bind to a specific
27894 IP address for outgoing connect()s.
27895 - End truncated log entries (e.g. directories) with "[truncated]".
27897 o Patches to 0.0.8preX:
27899 - Patches to compile and run on win32 again (maybe)?
27900 - Fix crash when looking for ~/.torrc with no $HOME set.
27901 - Fix a race bug in the unit tests.
27902 - Handle verified/unverified name collisions better when new
27903 routerinfo's arrive in a directory.
27904 - Sometimes routers were getting entered into the stats before
27905 we'd assigned their identity_digest. Oops.
27906 - Only pick and establish intro points after we've gotten a
27909 - AllowUnverifiedNodes config option to let circuits choose no-name
27910 routers in entry,middle,exit,introduction,rendezvous positions.
27911 Allow middle and rendezvous positions by default.
27912 - Add a man page for tor-resolve.
27915 Changes in version 0.0.7.3 - 2004-08-12
27916 o Stop dnsworkers from triggering an assert failure when you
27917 ask them to resolve the host "".
27920 Changes in version 0.0.8pre3 - 2004-08-09
27921 o Changes from 0.0.7.2:
27922 - Allow multiple ORs with same nickname in routerlist -- now when
27923 people give us one identity key for a nickname, then later
27924 another, we don't constantly complain until the first expires.
27925 - Remember used bandwidth (both in and out), and publish 15-minute
27926 snapshots for the past day into our descriptor.
27927 - You can now fetch $DIRURL/running-routers to get just the
27928 running-routers line, not the whole descriptor list. (But
27929 clients don't use this yet.)
27930 - When people mistakenly use Tor as an http proxy, point them
27931 at the tor-doc.html rather than the INSTALL.
27932 - Remove our mostly unused -- and broken -- hex_encode()
27933 function. Use base16_encode() instead. (Thanks to Timo Lindfors
27934 for pointing out this bug.)
27935 - Rotate onion keys every 12 hours, not every 2 hours, so we have
27936 fewer problems with people using the wrong key.
27937 - Change the default exit policy to reject the default edonkey,
27938 kazaa, gnutella ports.
27939 - Add replace_file() to util.[ch] to handle win32's rename().
27941 o Changes from 0.0.8preX:
27942 - Fix two bugs in saving onion keys to disk when rotating, so
27943 hopefully we'll get fewer people using old onion keys.
27944 - Fix an assert error that was making SocksPolicy not work.
27945 - Be willing to expire routers that have an open dirport -- it's
27946 just the authoritative dirservers we want to not forget.
27947 - Reject tor-resolve requests for .onion addresses early, so we
27948 don't build a whole rendezvous circuit and then fail.
27949 - When you're warning a server that he's unverified, don't cry
27950 wolf unpredictably.
27951 - Fix a race condition: don't try to extend onto a connection
27952 that's still handshaking.
27953 - For servers in clique mode, require the conn to be open before
27954 you'll choose it for your path.
27955 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
27956 end relay cell, etc.
27957 - Measure bandwidth capacity over the last 24 hours, not just 12
27958 - Bugfix: authoritative dirservers were making and signing a new
27959 directory for each client, rather than reusing the cached one.
27962 Changes in version 0.0.8pre2 - 2004-08-04
27963 o Changes from 0.0.7.2:
27965 - Check directory signature _before_ you decide whether you're
27966 you're running an obsolete version and should exit.
27967 - Check directory signature _before_ you parse the running-routers
27968 list to decide who's running or verified.
27969 - Bugfixes and features:
27970 - Check return value of fclose while writing to disk, so we don't
27971 end up with broken files when servers run out of disk space.
27972 - Log a warning if the user uses an unsafe socks variant, so people
27973 are more likely to learn about privoxy or socat.
27974 - Dirservers now include RFC1123-style dates in the HTTP headers,
27975 which one day we will use to better detect clock skew.
27977 o Changes from 0.0.8pre1:
27978 - Make it compile without warnings again on win32.
27979 - Log a warning if you're running an unverified server, to let you
27980 know you might want to get it verified.
27981 - Only pick a default nickname if you plan to be a server.
27984 Changes in version 0.0.8pre1 - 2004-07-23
27986 - Made our unit tests compile again on OpenBSD 3.5, and tor
27987 itself compile again on OpenBSD on a sparc64.
27988 - We were neglecting milliseconds when logging on win32, so
27989 everything appeared to happen at the beginning of each second.
27991 o Protocol changes:
27992 - 'Extend' relay cell payloads now include the digest of the
27993 intended next hop's identity key. Now we can verify that we're
27994 extending to the right router, and also extend to routers we
27995 hadn't heard of before.
27998 - Tor nodes can now act as relays (with an advertised ORPort)
27999 without being manually verified by the dirserver operators.
28000 - Uploaded descriptors of unverified routers are now accepted
28001 by the dirservers, and included in the directory.
28002 - Verified routers are listed by nickname in the running-routers
28003 list; unverified routers are listed as "$<fingerprint>".
28004 - We now use hash-of-identity-key in most places rather than
28005 nickname or addr:port, for improved security/flexibility.
28006 - To avoid Sybil attacks, paths still use only verified servers.
28007 But now we have a chance to play around with hybrid approaches.
28008 - Nodes track bandwidth usage to estimate capacity (not used yet).
28009 - ClientOnly option for nodes that never want to become servers.
28010 - Directory caching.
28011 - "AuthoritativeDir 1" option for the official dirservers.
28012 - Now other nodes (clients and servers) will cache the latest
28013 directory they've pulled down.
28014 - They can enable their DirPort to serve it to others.
28015 - Clients will pull down a directory from any node with an open
28016 DirPort, and check the signature/timestamp correctly.
28017 - Authoritative dirservers now fetch directories from other
28018 authdirservers, to stay better synced.
28019 - Running-routers list tells who's down also, along with noting
28020 if they're verified (listed by nickname) or unverified (listed
28022 - Allow dirservers to serve running-router list separately.
28023 This isn't used yet.
28024 - ORs connect-on-demand to other ORs
28025 - If you get an extend cell to an OR you're not connected to,
28026 connect, handshake, and forward the create cell.
28027 - The authoritative dirservers stay connected to everybody,
28028 and everybody stays connected to 0.0.7 servers, but otherwise
28029 clients/servers expire unused connections after 5 minutes.
28030 - When servers get a sigint, they delay 30 seconds (refusing new
28031 connections) then exit. A second sigint causes immediate exit.
28032 - File and name management:
28033 - Look for .torrc if no CONFDIR "torrc" is found.
28034 - If no datadir is defined, then choose, make, and secure ~/.tor
28036 - If torrc not found, exitpolicy reject *:*.
28037 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
28038 - If no nickname is defined, derive default from hostname.
28039 - Rename secret key files, e.g. identity.key -> secret_id_key,
28040 to discourage people from mailing their identity key to tor-ops.
28041 - Refuse to build a circuit before the directory has arrived --
28042 it won't work anyway, since you won't know the right onion keys
28044 - Try other dirservers immediately if the one you try is down. This
28045 should tolerate down dirservers better now.
28046 - Parse tor version numbers so we can do an is-newer-than check
28047 rather than an is-in-the-list check.
28048 - New socks command 'resolve', to let us shim gethostbyname()
28050 - A 'tor_resolve' script to access the socks resolve functionality.
28051 - A new socks-extensions.txt doc file to describe our
28052 interpretation and extensions to the socks protocols.
28053 - Add a ContactInfo option, which gets published in descriptor.
28054 - Publish OR uptime in descriptor (and thus in directory) too.
28055 - Write tor version at the top of each log file
28056 - New docs in the tarball:
28058 - Document that you should proxy your SSL traffic too.
28061 Changes in version 0.0.7.2 - 2004-07-07
28062 o A better fix for the 0.0.0.0 problem, that will hopefully
28063 eliminate the remaining related assertion failures.
28066 Changes in version 0.0.7.1 - 2004-07-04
28067 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
28068 since internally we use 0.0.0.0 to signify "not yet resolved".
28071 Changes in version 0.0.7 - 2004-06-07
28072 o Updated the man page to reflect the new features.
28075 Changes in version 0.0.7rc2 - 2004-06-06
28076 o Changes from 0.0.7rc1:
28077 - Make it build on Win32 again.
28078 o Changes from 0.0.6.2:
28079 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
28083 Changes in version 0.0.7rc1 - 2004-06-02
28085 - On sighup, we were adding another log without removing the first
28086 one. So log messages would get duplicated n times for n sighups.
28087 - Several cases of using a connection after we'd freed it. The
28088 problem was that connections that are pending resolve are in both
28089 the pending_resolve tree, and also the circuit's resolving_streams
28090 list. When you want to remove one, you must remove it from both.
28091 - Fix a double-mark-for-close where an end cell arrived for a
28092 resolving stream, and then the resolve failed.
28093 - Check directory signatures based on name of signer, not on whom
28094 we got the directory from. This will let us cache directories more
28097 - Crank up some of our constants to handle more users.
28100 Changes in version 0.0.7pre1 - 2004-06-02
28101 o Fixes for crashes and other obnoxious bugs:
28102 - Fix an epipe bug: sometimes when directory connections failed
28103 to connect, we would give them a chance to flush before closing
28105 - When we detached from a circuit because of resolvefailed, we
28106 would immediately try the same circuit twice more, and then
28107 give up on the resolve thinking we'd tried three different
28109 - Limit the number of intro circuits we'll attempt to build for a
28110 hidden service per 15-minute period.
28111 - Check recommended-software string *early*, before actually parsing
28112 the directory. Thus we can detect an obsolete version and exit,
28113 even if the new directory format doesn't parse.
28114 o Fixes for security bugs:
28115 - Remember which nodes are dirservers when you startup, and if a
28116 random OR enables his dirport, don't automatically assume he's
28117 a trusted dirserver.
28119 - Directory connections were asking the wrong poll socket to
28120 start writing, and not asking themselves to start writing.
28121 - When we detached from a circuit because we sent a begin but
28122 didn't get a connected, we would use it again the first time;
28123 but after that we would correctly switch to a different one.
28124 - Stop warning when the first onion decrypt attempt fails; they
28125 will sometimes legitimately fail now that we rotate keys.
28126 - Override unaligned-access-ok check when $host_cpu is ia64 or
28127 arm. Apparently they allow it but the kernel whines.
28128 - Dirservers try to reconnect periodically too, in case connections
28130 - Fix some memory leaks in directory servers.
28131 - Allow backslash in Win32 filenames.
28132 - Made Tor build complain-free on FreeBSD, hopefully without
28133 breaking other BSD builds. We'll see.
28135 - Doxygen markup on all functions and global variables.
28136 - Make directory functions update routerlist, not replace it. So
28137 now directory disagreements are not so critical a problem.
28138 - Remove the upper limit on number of descriptors in a dirserver's
28139 directory (not that we were anywhere close).
28140 - Allow multiple logfiles at different severity ranges.
28141 - Allow *BindAddress to specify ":port" rather than setting *Port
28142 separately. Allow multiple instances of each BindAddress config
28143 option, so you can bind to multiple interfaces if you want.
28144 - Allow multiple exit policy lines, which are processed in order.
28145 Now we don't need that huge line with all the commas in it.
28146 - Enable accept/reject policies on SOCKS connections, so you can bind
28147 to 0.0.0.0 but still control who can use your OP.
28150 Changes in version 0.0.6.2 - 2004-05-16
28151 o Our integrity-checking digest was checking only the most recent cell,
28152 not the previous cells like we'd thought.
28153 Thanks to Stefan Mark for finding the flaw!
28156 Changes in version 0.0.6.1 - 2004-05-06
28157 o Fix two bugs in our AES counter-mode implementation (this affected
28158 onion-level stream encryption, but not TLS-level). It turns
28159 out we were doing something much more akin to a 16-character
28160 polyalphabetic cipher. Oops.
28161 Thanks to Stefan Mark for finding the flaw!
28162 o Retire moria3 as a directory server, and add tor26 as a directory
28166 Changes in version 0.0.6 - 2004-05-02
28167 [version bump only]
28170 Changes in version 0.0.6rc4 - 2004-05-01
28171 o Update the built-in dirservers list to use the new directory format
28172 o Fix a rare seg fault: if a node offering a hidden service attempts
28173 to build a circuit to Alice's rendezvous point and fails before it
28174 reaches the last hop, it retries with a different circuit, but
28176 o Handle windows socket errors correctly.
28179 Changes in version 0.0.6rc3 - 2004-04-28
28180 o Don't expire non-general excess circuits (if we had enough
28181 circuits open, we were expiring rendezvous circuits -- even
28182 when they had a stream attached. oops.)
28183 o Fetch randomness from /dev/urandom better (not via fopen/fread)
28184 o Better debugging for tls errors
28185 o Some versions of openssl have an SSL_pending function that erroneously
28186 returns bytes when there is a non-application record pending.
28187 o Set Content-Type on the directory and hidserv descriptor.
28188 o Remove IVs from cipher code, since AES-ctr has none.
28189 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
28190 o We were using an array of length zero in a few places.
28191 o win32's gethostbyname can't resolve an IP to an IP.
28192 o win32's close can't close a socket.
28195 Changes in version 0.0.6rc2 - 2004-04-26
28196 o Fix a bug where we were closing tls connections intermittently.
28197 It turns out openssl keeps its errors around -- so if an error
28198 happens, and you don't ask about it, and then another openssl
28199 operation happens and succeeds, and you ask if there was an error,
28200 it tells you about the first error. Fun fun.
28201 o Fix a bug that's been lurking since 27 may 03 (!)
28202 When passing back a destroy cell, we would use the wrong circ id.
28203 'Mostly harmless', but still worth fixing.
28204 o Since we don't support truncateds much, don't bother sending them;
28205 just close the circ.
28206 o check for <machine/limits.h> so we build on NetBSD again (I hope).
28207 o don't crash if a conn that sent a begin has suddenly lost its circuit
28208 (this was quite rare).
28211 Changes in version 0.0.6rc1 - 2004-04-25
28212 o We now rotate link (tls context) keys and onion keys.
28213 o CREATE cells now include oaep padding, so you can tell
28214 if you decrypted them correctly.
28215 o Add bandwidthburst to server descriptor.
28216 o Directories now say which dirserver signed them.
28217 o Use a tor_assert macro that logs failed assertions too.
28220 Changes in version 0.0.6pre5 - 2004-04-18
28221 o changes from 0.0.6pre4:
28222 - make tor build on broken freebsd 5.2 installs
28223 - fix a failed assert when you try an intro point, get a nack, and try
28224 a second one and it works.
28225 - when alice uses a port that the hidden service doesn't accept,
28226 it now sends back an end cell (denied by exit policy). otherwise
28227 alice would just have to wait to time out.
28228 - fix another rare bug: when we had tried all the intro
28229 points for a hidden service, we fetched the descriptor
28230 again, but we left our introcirc thinking it had already
28231 sent an intro, so it kept waiting for a response...
28232 - bugfix: when you sleep your hidden-service laptop, as soon
28233 as it wakes up it tries to upload a service descriptor, but
28234 socketpair fails for some reason (localhost not up yet?).
28235 now we simply give up on that upload, and we'll try again later.
28236 i'd still like to find the bug though.
28237 - if an intro circ waiting for an ack dies before getting one, then
28239 - we were reusing stale service descriptors and refetching usable
28243 Changes in version 0.0.6pre4 - 2004-04-14
28244 o changes from 0.0.6pre3:
28245 - when bob fails to connect to the rendezvous point, and his
28246 circ didn't fail because of the rendezvous point itself, then
28247 he retries a couple of times
28248 - we expire introduction and rendezvous circs more thoroughly
28249 (sometimes they were hanging around forever)
28250 - we expire unattached rendezvous streams that have been around
28251 too long (they were sticking around forever).
28252 - fix a measly fencepost error that was crashing everybody with
28256 Changes in version 0.0.6pre3 - 2004-04-14
28257 o changes from 0.0.6pre2:
28258 - make hup work again
28259 - fix some memory leaks for dirservers
28260 - allow more skew in rendezvous descriptor timestamps, to help
28261 handle people like blanu who don't know what time it is
28262 - normal circs are 3 hops, but some rend/intro circs are 4, if
28263 the initiator doesn't get to choose the last hop
28264 - send acks for introductions, so alice can know whether to try
28266 - bob publishes intro points more correctly
28267 o changes from 0.0.5:
28268 - fix an assert trigger that's been plaguing us since the days
28269 of 0.0.2prexx (thanks weasel!)
28270 - retry stream correctly when we fail to connect because of
28271 exit-policy-reject (should try another) or can't-resolve-address
28272 (also should try another, because dns on random internet servers
28274 - when we hup a dirserver and we've *removed* a server from the
28275 approved-routers list, now we remove that server from the
28276 in-memory directories too
28279 Changes in version 0.0.6pre2 - 2004-04-08
28280 o We fixed our base32 implementation. Now it works on all architectures.
28283 Changes in version 0.0.6pre1 - 2004-04-08
28285 - Hidden services and rendezvous points are implemented. Go to
28286 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
28287 hidden services. (This only works via a socks4a proxy such as
28288 Privoxy, and currently it's quite slow.)
28291 Changes in version 0.0.5 - 2004-03-30
28292 [version bump only]
28295 Changes in version 0.0.5rc3 - 2004-03-29
28296 o Install torrc as torrc.sample -- we no longer clobber your
28298 o Re-enable recommendedversion checking (we broke it in rc2, oops)
28299 o Add in a 'notice' log level for things the operator should hear
28300 but that aren't warnings
28303 Changes in version 0.0.5rc2 - 2004-03-29
28304 o Hold socks connection open until reply is flushed (if possible)
28305 o Make exit nodes resolve IPs to IPs immediately, rather than asking
28306 the dns farm to do it.
28307 o Fix c99 aliasing warnings in rephist.c
28308 o Don't include server descriptors that are older than 24 hours in the
28310 o Give socks 'reject' replies their whole 15s to attempt to flush,
28311 rather than seeing the 60s timeout and assuming the flush had failed.
28312 o Clean automake droppings from the cvs repository
28315 Changes in version 0.0.5rc1 - 2004-03-28
28316 o Fix mangled-state bug in directory fetching (was causing sigpipes).
28317 o Only build circuits after we've fetched the directory: clients were
28318 using only the directory servers before they'd fetched a directory.
28319 This also means longer startup time; so it goes.
28320 o Fix an assert trigger where an OP would fail to handshake, and we'd
28321 expect it to have a nickname.
28322 o Work around a tsocks bug: do a socks reject when AP connection dies
28323 early, else tsocks goes into an infinite loop.
28326 Changes in version 0.0.4 - 2004-03-26
28327 o When connecting to a dirserver or OR and the network is down,
28331 Changes in version 0.0.3 - 2004-03-26
28332 o Warn and fail if server chose a nickname with illegal characters
28333 o Port to Solaris and Sparc:
28334 - include missing header fcntl.h
28335 - have autoconf find -lsocket -lnsl automatically
28336 - deal with hardware word alignment
28337 - make uname() work (solaris has a different return convention)
28338 - switch from using signal() to sigaction()
28339 o Preliminary work on reputation system:
28340 - Keep statistics on success/fail of connect attempts; they're published
28341 by kill -USR1 currently.
28342 - Add a RunTesting option to try to learn link state by creating test
28343 circuits, even when SocksPort is off.
28344 - Remove unused open circuits when there are too many.
28347 Changes in version 0.0.2 - 2004-03-19
28348 - Include strlcpy and strlcat for safer string ops
28349 - define INADDR_NONE so we compile (but still not run) on solaris
28352 Changes in version 0.0.2pre27 - 2004-03-14
28354 - Allow internal tor networks (we were rejecting internal IPs,
28355 now we allow them if they're set explicitly).
28356 - And fix a few endian issues.
28359 Changes in version 0.0.2pre26 - 2004-03-14
28361 - If a stream times out after 15s without a connected cell, don't
28362 try that circuit again: try a new one.
28363 - Retry streams at most 4 times. Then give up.
28364 - When a dirserver gets a descriptor from an unknown router, it
28365 logs its fingerprint (so the dirserver operator can choose to
28366 accept it even without mail from the server operator).
28367 - Inform unapproved servers when we reject their descriptors.
28368 - Make tor build on Windows again. It works as a client, who knows
28370 - Clearer instructions in the torrc for how to set up a server.
28371 - Be more efficient about reading fd's when our global token bucket
28372 (used for rate limiting) becomes empty.
28374 - Stop asserting that computers always go forward in time. It's
28376 - When we sent a cell (e.g. destroy) and then marked an OR connection
28377 expired, we might close it before finishing a flush if the other
28378 side isn't reading right then.
28379 - Don't allow dirservers to start if they haven't defined
28380 RecommendedVersions
28381 - We were caching transient dns failures. Oops.
28382 - Prevent servers from publishing an internal IP as their address.
28383 - Address a strcat vulnerability in circuit.c
28386 Changes in version 0.0.2pre25 - 2004-03-04
28388 - Put the OR's IP in its router descriptor, not its fqdn. That way
28389 we'll stop being stalled by gethostbyname for nodes with flaky dns,
28392 - If the user typed in an address that didn't resolve, the server
28396 Changes in version 0.0.2pre24 - 2004-03-03
28398 - Fix an assertion failure in dns.c, where we were trying to dequeue
28399 a pending dns resolve even if it wasn't pending
28400 - Fix a spurious socks5 warning about still trying to write after the
28401 connection is finished.
28402 - Hold certain marked_for_close connections open until they're finished
28403 flushing, rather than losing bytes by closing them too early.
28404 - Correctly report the reason for ending a stream
28405 - Remove some duplicate calls to connection_mark_for_close
28406 - Put switch_id and start_daemon earlier in the boot sequence, so it
28407 will actually try to chdir() to options.DataDirectory
28408 - Make 'make test' exit(1) if a test fails; fix some unit tests
28409 - Make tor fail when you use a config option it doesn't know about,
28410 rather than warn and continue.
28411 - Make --version work
28412 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
28415 Changes in version 0.0.2pre23 - 2004-02-29
28417 - Print a statement when the first circ is finished, so the user
28418 knows it's working.
28419 - If a relay cell is unrecognized at the end of the circuit,
28420 send back a destroy. (So attacks to mutate cells are more
28422 - New config option 'excludenodes' to avoid certain nodes for circuits.
28423 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
28424 so you can collect coredumps there.
28426 - Fix a bug in tls flushing where sometimes data got wedged and
28427 didn't flush until more data got sent. Hopefully this bug was
28428 a big factor in the random delays we were seeing.
28429 - Make 'connected' cells include the resolved IP, so the client
28430 dns cache actually gets populated.
28431 - Disallow changing from ORPort=0 to ORPort>0 on hup.
28432 - When we time-out on a stream and detach from the circuit, send an
28433 end cell down it first.
28434 - Only warn about an unknown router (in exitnodes, entrynodes,
28435 excludenodes) after we've fetched a directory.
28438 Changes in version 0.0.2pre22 - 2004-02-26
28440 - Servers publish less revealing uname information in descriptors.
28441 - More memory tracking and assertions, to crash more usefully when
28443 - If the default torrc isn't there, just use some default defaults.
28444 Plus provide an internal dirservers file if they don't have one.
28445 - When the user tries to use Tor as an http proxy, give them an http
28446 501 failure explaining that we're a socks proxy.
28447 - Dump a new router.desc on hup, to help confused people who change
28448 their exit policies and then wonder why router.desc doesn't reflect
28450 - Clean up the generic tor.sh init script that we ship with.
28452 - If the exit stream is pending on the resolve, and a destroy arrives,
28453 then the stream wasn't getting removed from the pending list. I
28454 think this was the one causing recent server crashes.
28455 - Use a more robust poll on OSX 10.3, since their poll is flaky.
28456 - When it couldn't resolve any dirservers, it was useless from then on.
28457 Now it reloads the RouterFile (or default dirservers) if it has no
28459 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
28460 many users don't even *have* a /usr/local/sbin/.
28463 Changes in version 0.0.2pre21 - 2004-02-18
28465 - There's a ChangeLog file that actually reflects the changelog.
28466 - There's a 'torify' wrapper script, with an accompanying
28467 tor-tsocks.conf, that simplifies the process of using tsocks for
28468 tor. It even has a man page.
28469 - The tor binary gets installed to sbin rather than bin now.
28470 - Retry streams where the connected cell hasn't arrived in 15 seconds
28471 - Clean up exit policy handling -- get the default out of the torrc,
28472 so we can update it without forcing each server operator to fix
28474 - Allow imaps and pop3s in default exit policy
28476 - Prevent picking middleman nodes as the last node in the circuit
28479 Changes in version 0.0.2pre20 - 2004-01-30
28481 - We now have a deb package, and it's in debian unstable. Go to
28482 it, apt-getters. :)
28483 - I've split the TotalBandwidth option into BandwidthRate (how many
28484 bytes per second you want to allow, long-term) and
28485 BandwidthBurst (how many bytes you will allow at once before the cap
28486 kicks in). This better token bucket approach lets you, say, set
28487 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
28488 performance while not exceeding your monthly bandwidth quota.
28489 - Push out a tls record's worth of data once you've got it, rather
28490 than waiting until you've read everything waiting to be read. This
28491 may improve performance by pipelining better. We'll see.
28492 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
28493 from failed circuits (if they haven't been connected yet) and attach
28495 - Expire old streams that haven't managed to connect. Some day we'll
28496 have them reattach to new circuits instead.
28499 - Fix several memory leaks that were causing servers to become bloated
28501 - Fix a few very rare assert triggers. A few more remain.
28502 - Setuid to User _before_ complaining about running as root.
28505 Changes in version 0.0.2pre19 - 2004-01-07
28507 - Fix deadlock condition in dns farm. We were telling a child to die by
28508 closing the parent's file descriptor to him. But newer children were
28509 inheriting the open file descriptor from the parent, and since they
28510 weren't closing it, the socket never closed, so the child never read
28511 eof, so he never knew to exit. Similarly, dns workers were holding
28512 open other sockets, leading to all sorts of chaos.
28513 - New cleaner daemon() code for forking and backgrounding.
28514 - If you log to a file, it now prints an entry at the top of the
28515 logfile so you know it's working.
28516 - The onionskin challenge length was 30 bytes longer than necessary.
28517 - Started to patch up the spec so it's not quite so out of date.
28520 Changes in version 0.0.2pre18 - 2004-01-02
28522 - Fix endian issues with the 'integrity' field in the relay header.
28523 - Fix a potential bug where connections in state
28524 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
28527 Changes in version 0.0.2pre17 - 2003-12-30
28529 - Made --debuglogfile (or any second log file, actually) work.
28530 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
28531 adversary could force us into an infinite loop.
28534 - Each onionskin handshake now includes a hash of the computed key,
28535 to prove the server's identity and help perfect forward secrecy.
28536 - Changed cell size from 256 to 512 bytes (working toward compatibility
28538 - Changed cell length to 2 bytes, and moved it to the relay header.
28539 - Implemented end-to-end integrity checking for the payloads of
28541 - Separated streamid from 'recognized' (otherwise circuits will get
28542 messed up when we try to have streams exit from the middle). We
28543 use the integrity-checking to confirm that a cell is addressed to
28545 - Randomize the initial circid and streamid values, so an adversary who
28546 breaks into a node can't learn how many circuits or streams have
28550 Changes in version 0.0.2pre16 - 2003-12-14
28552 - Fixed a bug that made HUP trigger an assert
28553 - Fixed a bug where a circuit that immediately failed wasn't being
28554 counted as a failed circuit in counting retries.
28557 - Now we close the circuit when we get a truncated cell: otherwise we're
28558 open to an anonymity attack where a bad node in the path truncates
28559 the circuit and then we open streams at him.
28560 - Add port ranges to exit policies
28561 - Add a conservative default exit policy
28562 - Warn if you're running tor as root
28563 - on HUP, retry OR connections and close/rebind listeners
28564 - options.EntryNodes: try these nodes first when picking the first node
28565 - options.ExitNodes: if your best choices happen to include any of
28566 your preferred exit nodes, you choose among just those preferred
28568 - options.ExcludedNodes: nodes that are never picked in path building
28571 Changes in version 0.0.2pre15 - 2003-12-03
28572 o Robustness and bugfixes:
28573 - Sometimes clients would cache incorrect DNS resolves, which would
28574 really screw things up.
28575 - An OP that goes offline would slowly leak all its sockets and stop
28577 - A wide variety of bugfixes in exit node selection, exit policy
28578 handling, and processing pending streams when a new circuit is
28580 - Pick nodes for a path only from those the directory says are up
28581 - Choose randomly from all running dirservers, not always the first one
28582 - Increase allowed http header size for directory fetch.
28583 - Stop writing to stderr (if we're daemonized it will be closed).
28584 - Enable -g always, so cores will be more useful to me.
28585 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
28588 - Wrote a man page. It lists commonly used options.
28591 - Change default loglevel to warn.
28592 - Make PidFile default to null rather than littering in your CWD.
28593 - OnionRouter config option is now obsolete. Instead it just checks
28595 - Moved to a single unified torrc file for both clients and servers.
28598 Changes in version 0.0.2pre14 - 2003-11-29
28599 o Robustness and bugfixes:
28600 - Force the admin to make the DataDirectory himself
28601 - to get ownership/permissions right
28602 - so clients no longer make a DataDirectory and then never use it
28603 - fix bug where a client who was offline for 45 minutes would never
28604 pull down a directory again
28605 - fix (or at least hide really well) the dns assert bug that was
28606 causing server crashes
28607 - warnings and improved robustness wrt clockskew for certs
28608 - use the native daemon(3) to daemonize, when available
28609 - exit if bind() fails
28610 - exit if neither socksport nor orport is defined
28611 - include our own tor_timegm (Win32 doesn't have its own)
28612 - bugfix for win32 with lots of connections
28613 - fix minor bias in PRNG
28614 - make dirserver more robust to corrupt cached directory
28617 - Wrote the design document (woo)
28619 o Circuit building and exit policies:
28620 - Circuits no longer try to use nodes that the directory has told them
28622 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
28623 bitcounts (18.0.0.0/8).
28624 - Make AP connections standby for a circuit if no suitable circuit
28625 exists, rather than failing
28626 - Circuits choose exit node based on addr/port, exit policies, and
28627 which AP connections are standing by
28628 - Bump min pathlen from 2 to 3
28629 - Relay end cells have a payload to describe why the stream ended.
28630 - If the stream failed because of exit policy, try again with a new
28632 - Clients have a dns cache to remember resolved addresses.
28633 - Notice more quickly when we have no working circuits
28636 - APPort is now called SocksPort
28637 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
28639 - RecommendedVersions is now a config variable rather than
28640 hardcoded (for dirservers)
28641 - Reloads config on HUP
28642 - Usage info on -h or --help
28643 - If you set User and Group config vars, it'll setu/gid to them.
28646 Changes in version 0.0.2pre13 - 2003-10-19
28647 o General stability:
28648 - SSL_write no longer fails when it returns WANTWRITE and the number
28649 of bytes in the buf has changed by the next SSL_write call.
28650 - Fix segfault fetching directory when network is down
28651 - Fix a variety of minor memory leaks
28652 - Dirservers reload the fingerprints file on HUP, so I don't have
28653 to take down the network when I approve a new router
28654 - Default server config file has explicit Address line to specify fqdn
28657 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
28658 - Make listener connections not ever alloc bufs
28660 o Autoconf improvements:
28661 - don't clobber an external CFLAGS in ./configure
28662 - Make install now works
28663 - create var/lib/tor on make install
28664 - autocreate a tor.sh initscript to help distribs
28665 - autocreate the torrc and sample-server-torrc with correct paths
28667 o Log files and Daemonizing now work:
28668 - If --DebugLogFile is specified, log to it at -l debug
28669 - If --LogFile is specified, use it instead of commandline
28670 - If --RunAsDaemon is set, tor forks and backgrounds on startup