1 Changes in version 0.3.5.1-alpha-2018-09-??
2 BLURB HERE. NOTE ABOUT NSS.
4 o Major features (experimental, library support):
5 - Tor now has _partial_ support for using the NSS cryptography
6 library in place of OpenSSL. When Tor is configured with
7 --enable-nss, it will use NSS for several (but not yet all) of its
8 cryptography. (It still relies on OpenSSL for the rest.)
9 Eventually, if all goes as planned, "--enable-nss" will produce a
10 version of Tor that does not depend on OpenSSL. Implements ticket
11 26816. WARNING: This feature is experimental. Don't use it for
12 real security yet, until the code has had much more review, and
13 more bugs have been shaken out.
14 - When built with --enable-nss, Tor now uses the NSS library for
15 digests, AES, and pseudorandom numbers. Closes ticket 26815.
17 o Major features (hidden service v3):
18 - Implement client authorization at the descriptor level. A new
19 torrc option was added to control this client side:
20 ClientOnionAuthDir <path>. On the service side, if the
21 "authorized_clients/" directory exists in the onion service
22 directory path, client configuration are read from the files
23 within. See the manpage for more details. Closes ticket 27547.
24 Patch done by Suphanat Chunhapanya (haxxpop).
26 o Major features (hidden service):
27 - For a newly created hidden service, the default version is now 3.
28 Tor still supports version 2 service but the operator now needs to
29 specifically set "HiddenServiceVersion 2" in order to create a new
30 service. For existing services, tor now learns the version by
31 reading the key file so the HiddenServiceVersion is not mandatory
32 in that case. Closes ticket 27215.
34 o Major features (new code layout):
35 - Nearly all of Tor's source code has been moved around into more
36 logical places. The "common" directory is now divided into a set
37 of libraries in "lib", and files in the "or" directory have been
38 split into "core" (logic absolutely needed for onion routing),
39 "feature" (independent modules in Tor), and "app" (to configure
40 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
41 more information. Closes ticket 26481.
43 This refactoring is not complete: although the libraries have been
44 refactored to be acyclic, the main body of Tor is still too
45 interconnected. We will attempt to improve this in the future.
47 o Major features (onion services):
48 - Improve revision counter generation in next-gen onion services.
49 Onion services can now scale by hosting multiple instances on
50 different hosts without synchronization between them, which was
51 previously impossible because descriptors would get rejected by
52 HSDirs. Addresses ticket 25552.
54 o Major features (portability, cryptography, experimental, TLS):
55 - Tor now has the option to compile with the NSS library instead of
56 OpenSSL. This feature is experimental, and we expect that bugs may
57 remain. It is mainly intended for environments where Tor's
58 performance is not CPU-bound, and where NSS is already known to be
59 installed. To try it out, configure Tor with the --enable-nss
60 flag. Closes ticket 26631.
62 o Major features (relay):
63 - Relays no longer run as exits by default. If the "ExitRelay"
64 option is auto (or unset), and no exit policy is specified with
65 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
66 Previously in this case, we allowed exit traffic and logged a
67 warning message. Closes ticket 21530. Patch by Neel Chauhan.
69 o Major bugfixes (directory authority):
70 - Actually check that address we get from DirAuthority configuration
71 line is valid IPv4. Explicitly disallow DirAuthority adress to be
72 DNS hostname. Fixes bug 26488; bugfix on 0.1.2.10-rc.
74 o Major bugfixes (restart-in-process):
75 - Fix a use-after-free error that could be caused by passing Tor an
76 impossible set of options that would fail during options_act().
77 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
79 o Minor features (admin tools):
80 - Add new tool that prints expiration date of signing cert in
81 ed25519_signing_cert. Resolves issue 19506.
83 o Minor features (bootstrap):
84 - Improve user experience by deferring directory progress reporting
85 until after a connection to a relay or bridge has succeeded. This
86 avoids reporting 80% progress based on cached directory
87 information when we can't even connect to a bridge or relay.
90 o Minor features (build):
91 - If you pass the "--enable-pic" option to configure, Tor will try
92 to tell the compiler to build position-independent code suitable
93 to link into a library. (The default remains -fPIE, for code
94 suitable for a relocatable executable.) Closes ticket 23846.
96 o Minor features (code correctness, testing):
97 - Tor's build process now includes a "check-includes" make target to
98 verify that no module of Tor relies on any headers from a higher-
99 level module. We hope to use this feature over time to help
100 refactor our codebase. Closes ticket 26447.
102 o Minor features (code layout):
103 - Make a new lowest-level error-handling API for use by code invoked
104 from within the logging module. This interface it makes it so the
105 logging code is no longer at risk of calling into itself if a
106 failure occurs while trying to log something. Closes ticket 26427.
108 o Minor features (compilation):
109 - Tor's configure script now supports a --with-malloc= option to
110 select your malloc implementation. Supported options are
111 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
112 default). Addresses part of ticket 20424. Based on a patch from
115 o Minor features (continuous integration):
116 - Don't do a distcheck with --disable-module-dirauth in Travis.
117 Implements ticket 27252.
118 - Install libcap-dev and libseccomp2-dev so these optional
119 dependencies get tested on Travis CI. Closes ticket 26560.
120 - Only run one online rust build in Travis, to reduce network
121 errors. Skip offline rust builds on Travis for Linux gcc, because
122 they're redundant. Implements ticket 27252.
123 - Skip gcc on OSX in Travis CI, it's rarely used. Skip a duplicate
124 hardening-off build in Travis on Tor 0.2.9. Skip gcc on Linux with
125 default settings, because all the non-default builds use gcc on
126 Linux. Implements ticket 27252.
128 o Minor features (controller):
129 - Emit CIRC_BW events as soon as we detect that we processed an
130 invalid or otherwise dropped cell on a circuit. This allows
131 vanguards and other controllers to react more quickly to dropped
132 cells. Closes ticket 27678.
133 - For purposes of CIRC_BW-based dropped cell detection, track half-
134 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
135 bias check cells to arrive without counting it as dropped until
136 either the END arrvies, or the windows are empty. Closes
138 - Implement 'GETINFO md/all' controller command to enable getting
139 all known microdesriptors. Closes ticket 8323.
140 - The GETINFO command now support an "uptime" argument, to return
141 Tor's uptime in seconds. Closes ticket 25132.
143 o Minor features (denial-of-service avoidance):
144 - Make our OOM handler aware of the DNS cache so that it doesn't
145 fill up the memory. This check is important for our DoS mitigation
146 subsystem. Closes ticket 18642. Patch by Neel Chauhan
148 o Minor features (development):
149 - Copy paragraph and URL to Tor's code of conduct document from
150 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
151 - Tor's makefile now supports running the "clippy" Rust style tool
152 on our Rust code. Closes ticket 22156.
154 o Minor features (directory authority):
155 - There is no longer an artificial upper limit on the length of
156 bandwidth lines. Closes ticket 26223.
157 - When a bandwidth file is used to obtain the bandwidth measurements,
158 include this bandwidth file headers in the votes. Closes
161 o Minor features (directory):
162 - Improved support for networks with only a single authority or a
163 single fallback directory. Patch from Gabriel Somlo. Closes
166 o Minor features (embedding API):
167 - The Tor controller API now supports a function to launch Tor with
168 a preconstructed owning controller FD, so that embedding
169 applications don't need to manage controller ports and
170 authentication. Closes ticket 24204.
172 o Minor features (geoip):
173 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
174 Country database. Closes ticket 27631.
176 o Minor features (in-process API):
177 - The tor_api now has a function that returns the name and version
178 of the backend implementing the API. Closes ticket 26947.
180 o Minor features (memory management):
181 - Get libevent code to use the same memory allocator that Tor code
182 is using by calling event_set_mem_functions() during
183 initialization. Resolves ticket 8415.
185 o Minor features (memory usage):
186 - When not using them, store legacy TAP public onion keys in DER-
187 encoded format, rather than as expanded public keys. This should
188 save several megabytes on typical clients. Closes ticket 27246.
190 o Minor features (openssl):
191 - When possible, use RFC5869 HKDF implementation from OpenSSL.
192 Resolves ticket 19979.
194 o Minor features (rust, code quality):
195 - Improve rust code quality in the Rust protover implementation by
196 making it more idiomatic. Includes changing an internal API to
197 take &str instead of &String. Closes ticket 26492.
199 o Minor features (testing):
200 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
201 chutney. Implements ticket 27211.
203 o Minor features (tor-resolve):
204 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
205 Side-effect of the refactoring for ticket 26526.
207 o Minor features (UI):
208 - Log each included configuration file or directory as we read it,
209 to provide more visibility about where Tor is reading from. Patch
210 from Unto Sten; closes ticket 27186.
212 o Minor features(config):
213 - The "auto" keyword in torrc is now case insensitive. Closes
216 o Minor bugfixes (security):
217 - Refrain from potentially insecure usage of strncat() in
218 configure_backtrace_handler(). Use snprintf() instead. Fixes bug
219 26522; bugfix on a969ce464dc23db39725a891d60537f3d3e51b50 (not in
222 o Minor bugfixes (appveyor ci):
223 - Improve Appveyor CI IRC logging. Generate correct branches and
224 URLs for pull requests and tags. Use unambiguous short commits.
225 Fixes bug 26979; bugfix on master.
227 o Minor bugfixes (bootstrap):
228 - Try harder to get descriptors in non-exit test networks, by using
229 the mid weight for the third hop when there are no exits. Fixes
230 bug 27237; bugfix on 0.2.6.2-alpha.
232 o Minor bugfixes (C correctness):
233 - Avoid casting smartlist index to int implicitly, as it may trigger
234 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
235 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
236 - Use time_t for all values in
237 predicted_ports_prediction_time_remaining(). Rework the code that
238 computes difference between durations/timestamps. Fixes bug 27165;
239 bugfix on 0.3.1.1-alpha.
241 o Minor bugfixes (client, memory usage):
242 - When not running as a directory cache, there is no need to store
243 the text of the current consensus networkstatus in RAM.
244 Previously, however, clients would store this anyway, at a cost of
245 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
248 o Minor bugfixes (client, reachableaddresses):
249 - Instead of adding an "reject *:*" line to ReachableAddresses when
250 loading the configuration, add one to the policy after parsing it
251 in parse_reachable_addresses(). This prevents extra "reject *.*"
252 lines from accumulating on reloads. Fixes bug 20874; bugfix on
253 0.3.5.1-alpha. Patch by Neel Chauhan.
255 o Minor bugfixes (code quality):
256 - Rename sandbox_getaddrinfo() and other functions to no longer
257 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
258 bugfix on 0.2.7.1-alpha.
260 o Minor bugfixes (compilation):
261 - Use Windows-compatible format strings in tor-print-ed-signing-
262 cert.c. Fixes bug 26986; bugfix on master.
264 o Minor bugfixes (configuration, Onion Services):
265 - In rend_service_parse_port_config(), disallow any input to remain
266 after address-port pair was parsed. This will catch address and
267 port being whitespace-separated by mistake of the user. Fixes bug
268 27044; bugfix on 0.2.9.10.
270 o Minor bugfixes (continuous integration):
271 - Stop reinstalling identical packages in our Windows CI. Fixes bug
272 27464; bugfix on 0.3.4.1-alpha.
274 o Minor bugfixes (controller):
275 - Consider all routerinfo errors other than "not a server" to be
276 transient for the purpose of "GETINFO exit-policy/*" controller
277 request. Print stacktrace in the unlikely case of failing to
278 recompute routerinfo digest. Fixes bug 27034; bugfix
281 o Minor bugfixes (directory connection shutdown):
282 - Avoid a double-close when shutting down a stalled directory
283 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
285 o Minor bugfixes (hidden service v2):
286 - Demote a log warning to info in case we do not have a consensus
287 when a .onion request comes in. This can happen while bootstrapping
288 for instance. The request will follow through after so we really
289 don't need to warn the user loudly. Fixes bug 27040; bugfix
292 o Minor bugfixes (hidden service v3):
293 - In case the hidden service directory can't be created or has wrong
294 permissions, do not BUG() on it which lead to a non fatal
295 stacktrace. Fixes bug 27335; bugfix on 0.3.2.1.
297 o Minor bugfixes (HTTP tunnel):
298 - Fix a bug warning when closing an HTTP tunnel connection due to an
299 HTTP request we couldn't handle. Fixes bug 26470; bugfix
302 o Minor bugfixes (ipv6):
303 - In addrs_in_same_network_family(), we choose the subnet size based
304 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
305 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
306 15518; bugfix on 0.3.5.1-alpha. Patch by Neel Chauhan.
308 o Minor bugfixes (logging):
309 - As a precaution, do an early return from log_addr_has_changed() if
310 Tor is running as client. Also, log a stack trace for debugging as
311 this function should only be called when Tor runs as server. Fixes
312 bug 26892; bugfix on 0.1.1.9-alpha.
313 - Refrain from mentioning bug 21018, as it is already fixed. Fixes
314 bug 25477; bugfix on 0.2.9.8.
316 o Minor bugfixes (logging, documentation):
317 - When SafeLogging is enabled, scrub IP address in
318 channel_tls_process_netinfo_cell(). Also, add a note to manpage
319 that scrubbing is not guaranteed on loglevels below Notice. Fixes
320 bug 26882; bugfix on 0.2.4.10-alpha.
322 o Minor bugfixes (netflow padding):
323 - Ensure circuitmux queues are empty before scheduling or sending
324 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
326 o Minor bugfixes (OS compatibility):
327 - On Linux and Windows properly handle configuration change that
328 moves a listener to/from wildcard IP address. In case first
329 attempt to bind a socket fails, close the old listener and try
330 binding a socket again. Fixes bug 17873; bugfix on 0.0.8pre-1.
332 o Minor bugfixes (performance)::
333 - Rework node_is_a_configured_bridge() to no longer call
334 node_get_all_orports(), which was performing too many memory
335 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
337 o Minor bugfixes (relay statistics):
338 - Update relay descriptor on bandwidth changes only when the uptime
339 is smaller than 24h in order to reduce the efficiency of guard
340 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
342 o Minor bugfixes (relay):
343 - In frac_nodes_with_descriptors(), add for_direct_connect, and
344 replace node_has_any_descriptor() with
345 node_has_preferred_descriptor(). Also, if we are using bridges and
346 there is at least one bridge with a full descriptor, set f_guard
347 in compute_frac_paths_available() to 1.0. Fixes bug 25886; bugfix
348 on 0.3.5.1-alpha. Patch by Neel Chauhan.
350 o Minor bugfixes (relays):
351 - Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
352 Guard flag. Update the message logged on relays when DirCache is
353 disabled. Fixes bug 24312; bugfix on 0.3.3.5-rc.
355 o Minor bugfixes (rust):
356 - The protover rewrite in 24031 allowed repeated votes from the same
357 voter for the same protocol version to be counted multiple times
358 in protover_compute_vote(). Fixes bug 27649; bugfix on 0.3.3.5-rc.
359 - protover parsed and accepted unknown protocol names containing
360 invalid characters outside the range [A-Za-z0-9-]. Fixes bug
361 27687; bugfix on 0.3.3.1-alpha.
363 o Minor bugfixes (testing):
364 - Fix two unit tests to work when HOME environment variable is not
365 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
366 - If a unit test running in a subprocess exits abnormally or with a
367 nonzero status code, treat the test as having failed, even if the
368 test reported success. Without this fix, memory leaks don't cause
369 cause the tests to fail, even with LeakSanitizer. Fixes bug 27658;
370 bugfix on 0.2.2.4-alpha.
371 - When logging a version mismatch in our openssl_version tests,
372 report the actual offending version strings. Fixes bug 26152;
373 bugfix on 0.2.9.1-alpha.
375 o Minor bugfixes (torrc):
376 - Tor now validates that the ContactInfo config option is valid UTF-
377 8 when parsing torrc. Fixes bug 27428; bugfix on 0.0.8pre1.
379 o Code simplification and refactoring:
380 - 'updateFallbackDirs.py' now ignores the blacklist file as it's not
381 longer needed Closes ticket 26502.
382 - Include paths to header files within Tor are now qualified by
383 directory within the top-level src directory.
384 - Low log level of "Scheduler type KIST has been enabled" to INFO.
386 - Many structures have been removed from the centralized "or.h"
387 header, and moved into their own headers. This will allow us to
388 reduce the number of places in the code that rely on each
389 structure's contents and layout. Closes ticket 26383.
390 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
391 - Remove GetAdaptersAddresses_fn_t. The code that used it was
392 removed as part of the 26481 refactor. Closes ticket 27467.
393 - Rework Tor SOCKS server code to use Trunnel and benefit from
394 autogenerated functions for parsing and generating SOCKS wire
395 format. New implementation is cleaner, more maintainable and
396 should be less prone to heartbleed-style vulnerabilities.
397 Implements a significant fraction of ticket 3569.
398 - Split sampled_guards_update_from_consensus() and
399 select_entry_guard_for_circuit() into subfunctions. In
400 entry_guards_update_primary() unite three smartlist enumerations
401 into one and move smartlist comparison code out of the function.
403 - Tor now assumes that you have standards-conformant stdint.h and
404 inttypes.h headers when compiling. Closes ticket 26626.
405 - Unify our bloom filter logic. Previously we had two copies of this
406 code: one for routerlist filtering, and one for address set
407 calculations. Closes ticket 26510.
408 - Use the simpler strcmpstart() helper in
409 rend_parse_v2_service_descriptor instead of strncmp(). Closes
411 - Utility functions that can perform a DNS lookup are now wholly
412 separated from those that can't, in separate headers and C
413 modules. Closes ticket 26526.
416 - Remove old instructions from INSTALL document. Closes ticket 26588.
417 - Warn users that they should not include MyFamily line(s) in their
418 torrc when running Tor bridge. Closes ticket 26908.
421 - Tor no longer supports building with the dmalloc library. For
422 debugging memory issues, we suggest using gperftools or msan
423 instead. Closes ticket 26426.
424 - Tor no longer attempts to run on Windows environments without the
425 GetAdaptersAddresses() function. This function has existed since
426 Windows XP, which is itself already older than we support.
429 - Fix forking tests on Windows when there is a space somewhere in
430 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
432 o Removed features (hidden service, tor2web):
433 - Remove Tor2web functionalities. The Tor2webMode and
434 Tor2webRendezvousPoints options are now obsolete. Note that this
435 feature was never shipped in vanilla Tor and it was only possible
436 to use this feature by building the support at compile time.
440 Changes in version 0.2.9.17 - 2018-09-10
441 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
443 o Minor features (compatibility, backport from 0.3.4.8):
444 - Tell OpenSSL to maintain backward compatibility with previous
445 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
446 ciphers are disabled by default. Closes ticket 27344.
448 o Minor features (continuous integration, backport from 0.3.4.7-rc):
449 - Enable macOS builds in our Travis CI configuration. Closes
451 - Install libcap-dev and libseccomp2-dev so these optional
452 dependencies get tested on Travis CI. Closes ticket 26560.
453 - Run asciidoc during Travis CI. Implements ticket 27087.
454 - Use ccache in our Travis CI configuration. Closes ticket 26952.
456 o Minor features (geoip):
457 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
458 Country database. Closes ticket 27089.
460 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
461 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
462 tell the compiler not to include the system malloc implementation.
463 Fixes bug 20424; bugfix on 0.2.0.20-rc.
465 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
466 - Silence a spurious compiler warning on the GetAdaptersAddresses
467 function pointer cast. This issue is already fixed by 26481 in
468 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
469 bugfix on 0.2.3.11-alpha.
470 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
471 supported, and always fails. Some compilers warn about the
472 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
475 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
476 - Don't link or search for pthreads when building for Windows, even
477 if we are using build environment (like mingw) that provides a
478 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
480 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
481 - Skip a pair of unreliable key generation tests on Windows, until
482 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
483 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
485 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
486 - Pass the module flags to distcheck configure, and log the flags
487 before running configure. (Backported to 0.2.9 and later as a
488 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
490 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
491 - When a Travis build fails, and showing a log fails, keep trying to
492 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
493 - When we use echo in Travis, don't pass a --flag as the first
494 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
496 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
497 - When voting for recommended versions, make sure that all of the
498 versions are well-formed and parsable. Fixes bug 26485; bugfix
501 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
502 - Fix a bug in out sandboxing rules for the openat() syscall.
503 Previously, no openat() call would be permitted, which would break
504 filesystem operations on recent glibc versions. Fixes bug 25440;
505 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
507 o Minor bugfixes (onion services, backport from 0.3.4.8):
508 - Silence a spurious compiler warning in
509 rend_client_send_introduction(). Fixes bug 27463; bugfix
512 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
513 - Log a protocol warning when single onion services or Tor2web clients
514 fail to authenticate direct connections to relays.
515 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
517 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
518 - Disable core dumps in test_bt.sh, to avoid failures in "make
519 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
521 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
522 - Before running make test-network-all, delete old logs and test
523 result files, to avoid spurious failures. Fixes bug 27295; bugfix
526 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
527 - Our "tortls/cert_matches_key" unit test no longer relies on
528 OpenSSL internals. Previously, it relied on unsupported OpenSSL
529 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
530 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
532 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
533 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
534 27185; bugfix on 0.2.2.2-alpha.
537 Changes in version 0.3.2.12 - 2018-09-10
538 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
540 o Minor features (compatibility, backport from 0.3.4.8):
541 - Tell OpenSSL to maintain backward compatibility with previous
542 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
543 ciphers are disabled by default. Closes ticket 27344.
545 o Minor features (continuous integration, backport from 0.3.4.7-rc):
546 - Enable macOS builds in our Travis CI configuration. Closes
548 - Install libcap-dev and libseccomp2-dev so these optional
549 dependencies get tested on Travis CI. Closes ticket 26560.
550 - Run asciidoc during Travis CI. Implements ticket 27087.
551 - Use ccache in our Travis CI configuration. Closes ticket 26952.
553 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
554 - Use cargo cache in our Travis CI configuration. Closes
557 o Minor features (controller, backport from 0.3.4.6-rc):
558 - The control port now exposes the list of HTTPTunnelPorts and
559 ExtOrPorts via GETINFO net/listeners/httptunnel and
560 net/listeners/extor respectively. Closes ticket 26647.
562 o Minor features (directory authorities, backport from 0.3.4.7-rc):
563 - Authorities no longer vote to make the subprotocol version
564 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
565 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
567 o Minor features (geoip):
568 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
569 Country database. Closes ticket 27089.
571 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
572 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
573 tell the compiler not to include the system malloc implementation.
574 Fixes bug 20424; bugfix on 0.2.0.20-rc.
575 - Don't try to use a pragma to temporarily disable the
576 -Wunused-const-variable warning if the compiler doesn't support
577 it. Fixes bug 26785; bugfix on 0.3.2.11.
579 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
580 - Silence a spurious compiler warning on the GetAdaptersAddresses
581 function pointer cast. This issue is already fixed by 26481 in
582 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
583 bugfix on 0.2.3.11-alpha.
584 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
585 supported, and always fails. Some compilers warn about the
586 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
589 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
590 - Don't link or search for pthreads when building for Windows, even
591 if we are using build environment (like mingw) that provides a
592 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
594 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
595 - Skip a pair of unreliable key generation tests on Windows, until
596 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
597 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
599 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
600 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
601 - Pass the module flags to distcheck configure, and log the flags
602 before running configure. (Backported to 0.2.9 and later as a
603 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
605 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
606 - When a Travis build fails, and showing a log fails, keep trying to
607 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
608 - When we use echo in Travis, don't pass a --flag as the first
609 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
611 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
612 - When voting for recommended versions, make sure that all of the
613 versions are well-formed and parsable. Fixes bug 26485; bugfix
616 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
617 - Fix a bug in out sandboxing rules for the openat() syscall.
618 Previously, no openat() call would be permitted, which would break
619 filesystem operations on recent glibc versions. Fixes bug 25440;
620 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
622 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
623 - Improve the log message when connection initiators fail to
624 authenticate direct connections to relays. Fixes bug 26927; bugfix
627 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
628 - Fix bug that causes services to not ever rotate their descriptors
629 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
632 o Minor bugfixes (onion services, backport from 0.3.4.8):
633 - Silence a spurious compiler warning in
634 rend_client_send_introduction(). Fixes bug 27463; bugfix
637 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
638 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
640 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
641 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
642 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
643 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
645 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
646 - Log a protocol warning when single onion services or Tor2web clients
647 fail to authenticate direct connections to relays.
648 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
650 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
651 - Disable core dumps in test_bt.sh, to avoid failures in "make
652 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
654 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
655 - When running make test-network-all, use the mixed+hs-v2 network.
656 (A previous fix to chutney removed v3 onion services from the
657 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
658 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
659 - Before running make test-network-all, delete old logs and test
660 result files, to avoid spurious failures. Fixes bug 27295; bugfix
663 o Minor bugfixes (testing, openssl compatibility):
664 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
665 internals. Previously, it relied on unsupported OpenSSL behavior in
666 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
667 bugfix on 0.2.5.1-alpha.
669 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
670 - Our "tortls/cert_matches_key" unit test no longer relies on
671 OpenSSL internals. Previously, it relied on unsupported OpenSSL
672 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
673 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
675 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
676 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
677 27185; bugfix on 0.2.2.2-alpha.
680 Changes in version 0.3.3.10 - 2018-09-10
681 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
683 o Minor features (bug workaround, backport from 0.3.4.7-rc):
684 - Compile correctly on systems that provide the C11 stdatomic.h
685 header, but where C11 atomic functions don't actually compile.
686 Closes ticket 26779; workaround for Debian issue 903709.
688 o Minor features (compatibility, backport from 0.3.4.8):
689 - Tell OpenSSL to maintain backward compatibility with previous
690 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
691 ciphers are disabled by default. Closes ticket 27344.
693 o Minor features (continuous integration, backport from 0.3.4.7-rc):
694 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
695 - Enable macOS builds in our Travis CI configuration. Closes
697 - Install libcap-dev and libseccomp2-dev so these optional
698 dependencies get tested on Travis CI. Closes ticket 26560.
699 - Run asciidoc during Travis CI. Implements ticket 27087.
700 - Use ccache in our Travis CI configuration. Closes ticket 26952.
702 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
703 - Use cargo cache in our Travis CI configuration. Closes
706 o Minor features (controller, backport from 0.3.4.6-rc):
707 - The control port now exposes the list of HTTPTunnelPorts and
708 ExtOrPorts via GETINFO net/listeners/httptunnel and
709 net/listeners/extor respectively. Closes ticket 26647.
711 o Minor features (directory authorities, backport from 0.3.4.7-rc):
712 - Authorities no longer vote to make the subprotocol version
713 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
714 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
716 o Minor features (geoip):
717 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
718 Country database. Closes ticket 27089.
720 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
721 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
722 tell the compiler not to include the system malloc implementation.
723 Fixes bug 20424; bugfix on 0.2.0.20-rc.
724 - Don't try to use a pragma to temporarily disable the
725 -Wunused-const-variable warning if the compiler doesn't support
726 it. Fixes bug 26785; bugfix on 0.3.2.11.
728 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
729 - Silence a spurious compiler warning on the GetAdaptersAddresses
730 function pointer cast. This issue is already fixed by 26481 in
731 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
732 bugfix on 0.2.3.11-alpha.
733 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
734 supported, and always fails. Some compilers warn about the
735 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
738 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
739 - Don't link or search for pthreads when building for Windows, even
740 if we are using build environment (like mingw) that provides a
741 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
743 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
744 - Skip a pair of unreliable key generation tests on Windows, until
745 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
746 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
748 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
749 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
750 - Pass the module flags to distcheck configure, and log the flags
751 before running configure. (Backported to 0.2.9 and later as a
752 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
754 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
755 - When a Travis build fails, and showing a log fails, keep trying to
756 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
757 - When we use echo in Travis, don't pass a --flag as the first
758 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
760 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
761 - When voting for recommended versions, make sure that all of the
762 versions are well-formed and parsable. Fixes bug 26485; bugfix
765 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
766 - Always call tor_free_all() when leaving tor_run_main(). When we
767 did not, restarting tor in-process would cause an assertion
768 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
770 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
771 - Fix a bug in our sandboxing rules for the openat() syscall.
772 Previously, no openat() call would be permitted, which would break
773 filesystem operations on recent glibc versions. Fixes bug 25440;
774 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
776 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
777 - Improve the log message when connection initiators fail to
778 authenticate direct connections to relays. Fixes bug 26927; bugfix
781 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
782 - Fix bug that causes services to not ever rotate their descriptors
783 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
786 o Minor bugfixes (onion services, backport from 0.3.4.8):
787 - Silence a spurious compiler warning in
788 rend_client_send_introduction(). Fixes bug 27463; bugfix
791 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
792 - Work around two different bugs in the OS X 10.10 and later SDKs
793 that would prevent us from successfully targeting earlier versions
794 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
796 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
797 - Fix compilation of the unit tests on GNU/Hurd, which does not
798 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
801 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
802 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
804 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
805 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
806 - Protover parsing was accepting the presence of whitespace in
807 version strings, which the C implementation would choke on, e.g.
808 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
809 - Protover parsing was ignoring a 2nd hyphen and everything after
810 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
812 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
813 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
814 - cd to ${abs_top_builddir}/src/rust before running cargo in
815 src/test/test_rust.sh. This makes the working directory consistent
816 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
818 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
819 - Log a protocol warning when single onion services or Tor2web clients
820 fail to authenticate direct connections to relays.
821 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
823 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
824 - Disable core dumps in test_bt.sh, to avoid failures in "make
825 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
827 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
828 - When running make test-network-all, use the mixed+hs-v2 network.
829 (A previous fix to chutney removed v3 onion services from the
830 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
831 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
832 - Before running make test-network-all, delete old logs and test
833 result files, to avoid spurious failures. Fixes bug 27295; bugfix
836 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
837 - Our "tortls/cert_matches_key" unit test no longer relies on
838 OpenSSL internals. Previously, it relied on unsupported OpenSSL
839 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
840 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
842 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
843 - Stop sending ed25519 link specifiers in v3 onion service introduce
844 cells and descriptors, when the rendezvous or introduction point
845 doesn't support ed25519 link authentication. Fixes bug 26627;
846 bugfix on 0.3.2.4-alpha.
848 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
849 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
850 27185; bugfix on 0.2.2.2-alpha.
853 Changes in version 0.3.4.8 - 2018-09-10
854 Tor 0.3.4.8 is the first stable release in its series; it includes
855 compilation and portability fixes.
857 The Tor 0.3.4 series includes improvements for running Tor in
858 low-power and embedded environments, which should help performance in
859 general. We've begun work on better modularity, and included preliminary
860 changes on the directory authority side to accommodate a new bandwidth
861 measurement system. We've also integrated more continuous-integration
862 systems into our development process, and made corresponding changes to
863 Tor's testing infrastructure. Finally, we've continued to refine
864 our anti-denial-of-service code.
866 Below are the changes since 0.3.4.7-rc. For a complete list of changes
867 since 0.3.3.9, see the ReleaseNotes file.
869 o Minor features (compatibility):
870 - Tell OpenSSL to maintain backward compatibility with previous
871 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
872 ciphers are disabled by default. Closes ticket 27344.
874 o Minor features (continuous integration):
875 - Log the compiler path and version during Appveyor builds.
876 Implements ticket 27449.
877 - Show config.log and test-suite.log after failed Appveyor builds.
878 Also upload the zipped full logs as a build artifact. Implements
881 o Minor bugfixes (compilation):
882 - Silence a spurious compiler warning on the GetAdaptersAddresses
883 function pointer cast. This issue is already fixed by 26481 in
884 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
885 bugfix on 0.2.3.11-alpha.
886 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
887 supported, and always fails. Some compilers warn about the
888 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
891 o Minor bugfixes (continuous integration):
892 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
893 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
894 Executables compiled for 64-bit Windows with this version of gcc
895 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
896 27460; bugfix on 0.3.4.1-alpha.
897 - When a Travis build fails, and showing a log fails, keep trying to
898 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
899 - When we use echo in Travis, don't pass a --flag as the first
900 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
902 o Minor bugfixes (onion services):
903 - Silence a spurious compiler warning in
904 rend_client_send_introduction(). Fixes bug 27463; bugfix
907 o Minor bugfixes (testing, chutney):
908 - When running make test-network-all, use the mixed+hs-v2 network.
909 (A previous fix to chutney removed v3 onion services from the
910 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
911 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
912 - Before running make test-network-all, delete old logs and test
913 result files, to avoid spurious failures. Fixes bug 27295; bugfix
916 Changes in version 0.3.4.7-rc - 2018-08-24
917 Tor 0.3.4.7-rc fixes several small compilation, portability, and
918 correctness issues in previous versions of Tor. This version is a
919 release candidate: if no serious bugs are found, we expect that the
920 stable 0.3.4 release will be (almost) the same as this release.
922 o Minor features (bug workaround):
923 - Compile correctly on systems that provide the C11 stdatomic.h
924 header, but where C11 atomic functions don't actually compile.
925 Closes ticket 26779; workaround for Debian issue 903709.
927 o Minor features (continuous integration):
928 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
929 - Enable macOS builds in our Travis CI configuration. Closes
931 - Install libcap-dev and libseccomp2-dev so these optional
932 dependencies get tested on Travis CI. Closes ticket 26560.
933 - Only post Appveyor IRC notifications when the build fails.
934 Implements ticket 27275.
935 - Run asciidoc during Travis CI. Implements ticket 27087.
936 - Use ccache in our Travis CI configuration. Closes ticket 26952.
938 o Minor features (continuous integration, rust):
939 - Use cargo cache in our Travis CI configuration. Closes
942 o Minor features (directory authorities):
943 - Authorities no longer vote to make the subprotocol version
944 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
945 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
947 o Minor features (geoip):
948 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
949 Country database. Closes ticket 27089.
951 o Minor bugfixes (compilation, windows):
952 - Don't link or search for pthreads when building for Windows, even
953 if we are using build environment (like mingw) that provides a
954 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
956 o Minor bugfixes (continuous integration):
957 - Improve Appveyor CI IRC logging. Generate correct branches and
958 URLs for pull requests and tags. Use unambiguous short commits.
959 Fixes bug 26979; bugfix on master.
960 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
961 - Pass the module flags to distcheck configure, and log the flags
962 before running configure. (Backported to 0.2.9 and later as a
963 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
965 o Minor bugfixes (in-process restart):
966 - Always call tor_free_all() when leaving tor_run_main(). When we
967 did not, restarting tor in-process would cause an assertion
968 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
970 o Minor bugfixes (linux seccomp2 sandbox):
971 - Fix a bug in out sandboxing rules for the openat() syscall.
972 Previously, no openat() call would be permitted, which would break
973 filesystem operations on recent glibc versions. Fixes bug 25440;
974 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
976 o Minor bugfixes (onion services):
977 - Fix bug that causes services to not ever rotate their descriptors
978 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
981 o Minor bugfixes (portability):
982 - Fix compilation of the unit tests on GNU/Hurd, which does not
983 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
986 o Minor bugfixes (rust):
987 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
989 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
990 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
991 - Protover parsing was accepting the presence of whitespace in
992 version strings, which the C implementation would choke on, e.g.
993 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
994 - Protover parsing was ignoring a 2nd hyphen and everything after
995 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
997 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
998 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
999 - cd to ${abs_top_builddir}/src/rust before running cargo in
1000 src/test/test_rust.sh. This makes the working directory consistent
1001 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
1003 o Minor bugfixes (testing, bootstrap):
1004 - When calculating bootstrap progress, check exit policies and the
1005 exit flag. Previously, Tor would only check the exit flag, which
1006 caused race conditions in small and fast networks like chutney.
1007 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
1009 o Minor bugfixes (testing, openssl compatibility):
1010 - Our "tortls/cert_matches_key" unit test no longer relies on
1011 OpenSSL internals. Previously, it relied on unsupported OpenSSL
1012 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
1013 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
1015 o Minor bugfixes (Windows, compilation):
1016 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
1017 27185; bugfix on 0.2.2.2-alpha.
1020 Changes in version 0.3.4.6-rc - 2018-08-06
1021 Tor 0.3.4.6-rc fixes several small compilation, portability, and
1022 correctness issues in previous versions of Tor. This version is a
1023 release candidate: if no serious bugs are found, we expect that the
1024 stable 0.3.4 release will be (almost) the same as this release.
1026 o Major bugfixes (event scheduler):
1027 - When we enable a periodic event, schedule it in the event loop
1028 rather than running it immediately. Previously, we would re-run
1029 periodic events immediately in the middle of (for example)
1030 changing our options, with unpredictable effects. Fixes bug 27003;
1031 bugfix on 0.3.4.1-alpha.
1033 o Minor features (compilation):
1034 - When building Tor, prefer to use Python 3 over Python 2, and more
1035 recent (contemplated) versions over older ones. Closes
1037 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
1038 tell the compiler not to include the system malloc implementation.
1039 Fixes bug 20424; bugfix on 0.2.0.20-rc.
1040 - Don't try to use a pragma to temporarily disable the
1041 -Wunused-const-variable warning if the compiler doesn't support
1042 it. Fixes bug 26785; bugfix on 0.3.2.11.
1044 o Minor bugfixes (continuous integration):
1045 - Skip a pair of unreliable key generation tests on Windows, until
1046 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
1047 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
1049 o Minor features (controller):
1050 - The control port now exposes the list of HTTPTunnelPorts and
1051 ExtOrPorts via GETINFO net/listeners/httptunnel and
1052 net/listeners/extor respectively. Closes ticket 26647.
1054 o Minor bugfixes (directory authority):
1055 - When voting for recommended versions, make sure that all of the
1056 versions are well-formed and parsable. Fixes bug 26485; bugfix
1059 o Minor features (geoip):
1060 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1061 Country database. Closes ticket 26674.
1063 o Minor features (Rust, portability):
1064 - Rust cross-compilation is now supported. Closes ticket 25895.
1066 o Minor bugfixes (compilation):
1067 - Update build system so that tor builds again with --disable-unittests
1068 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
1069 - Fix a compilation warning on some versions of GCC when building
1070 code that calls routerinfo_get_my_routerinfo() twice, assuming
1071 that the second call will succeed if the first one did. Fixes bug
1072 26269; bugfix on 0.2.8.2-alpha.
1074 o Minor bugfixes (controller):
1075 - Report the port correctly when a port is configured to bind to
1076 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
1077 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
1078 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
1079 on 0.3.3.1-alpha. Patch by "akwizgran".
1081 o Minor bugfixes (correctness, flow control):
1082 - Upon receiving a stream-level SENDME cell, verify that our window
1083 has not grown too large. Fixes bug 26214; bugfix on svn
1086 o Minor bugfixes (memory, correctness):
1087 - Fix a number of small memory leaks identified by coverity. Fixes
1088 bug 26467; bugfix on numerous Tor versions.
1090 o Minor bugfixes (logging):
1091 - Improve the log message when connection initiators fail to
1092 authenticate direct connections to relays. Fixes bug 26927; bugfix
1095 o Minor bugfixes (portability):
1096 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
1097 26994; bugfix on 0.3.4.1-alpha.
1098 - Work around two different bugs in the OS X 10.10 and later SDKs
1099 that would prevent us from successfully targeting earlier versions
1100 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
1102 o Minor bugfixes (single onion services, Tor2web):
1103 - Log a protocol warning when single onion services or Tor2web
1104 clients fail to authenticate direct connections to relays. Fixes
1105 bug 26924; bugfix on 0.2.9.1-alpha.
1107 o Minor bugfixes (testing):
1108 - Disable core dumps in test_bt.sh, to avoid failures in "make
1109 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
1111 o Minor bugfixes (testing, compatibility):
1112 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
1113 only to pass strings (rather than "bytes" objects) to the Python
1114 subprocess module. Python 3 on Windows seems to require this.
1115 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
1116 0.3.1.1-alpha (for hs_ntor_ref.py).
1118 o Minor bugfixes (v3 onion services):
1119 - Stop sending ed25519 link specifiers in v3 onion service introduce
1120 cells and descriptors, when the rendezvous or introduction point
1121 doesn't support ed25519 link authentication. Fixes bug 26627;
1122 bugfix on 0.3.2.4-alpha.
1125 Changes in version 0.3.4.5-rc - 2018-07-13
1126 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
1127 bridge relays should upgrade.
1129 o Directory authority changes:
1130 - The "Bifroest" bridge authority has been retired; the new bridge
1131 authority is "Serge", and it is operated by George from the
1132 TorBSD project. Closes ticket 26771.
1135 Changes in version 0.3.3.9 - 2018-07-13
1136 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
1137 bridge relays should upgrade.
1139 o Directory authority changes:
1140 - The "Bifroest" bridge authority has been retired; the new bridge
1141 authority is "Serge", and it is operated by George from the
1142 TorBSD project. Closes ticket 26771.
1145 Changes in version 0.3.2.11 - 2018-07-13
1146 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
1147 bridge relays should upgrade. We also take this opportunity to backport
1150 o Directory authority changes:
1151 - The "Bifroest" bridge authority has been retired; the new bridge
1152 authority is "Serge", and it is operated by George from the
1153 TorBSD project. Closes ticket 26771.
1155 o Directory authority changes (backport from 0.3.3.7):
1156 - Add an IPv6 address for the "dannenberg" directory authority.
1157 Closes ticket 26343.
1159 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
1160 - When directory authorities read a zero-byte bandwidth file, they
1161 would previously log a warning with the contents of an
1162 uninitialised buffer. They now log a warning about the empty file
1163 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
1165 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
1166 - Correctly detect when onion services get disabled after HUP. Fixes
1167 bug 25761; bugfix on 0.3.2.1.
1169 o Minor features (sandbox, backport from 0.3.3.4-alpha):
1170 - Explicitly permit the poll() system call when the Linux
1171 seccomp2-based sandbox is enabled: apparently, some versions of
1172 libc use poll() when calling getpwnam(). Closes ticket 25313.
1174 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
1175 - Update the Travis CI configuration to use the stable Rust channel,
1176 now that we have decided to require that. Closes ticket 25714.
1178 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
1179 - Our .travis.yml configuration now includes support for testing the
1180 results of "make distcheck". (It's not uncommon for "make check"
1181 to pass but "make distcheck" to fail.) Closes ticket 25814.
1182 - Our Travis CI configuration now integrates with the Coveralls
1183 coverage analysis tool. Closes ticket 25818.
1185 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
1186 - Add several checks to detect whether Tor relays are uploading
1187 their descriptors without specifying why they regenerated them.
1188 Diagnostic for ticket 25686.
1190 o Minor features (compilation, backport from 0.3.4.4-rc):
1191 - When building Tor, prefer to use Python 3 over Python 2, and more
1192 recent (contemplated) versions over older ones. Closes
1195 o Minor features (geoip):
1196 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1197 Country database. Closes ticket 26674.
1199 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
1200 - Upon receiving a malformed connected cell, stop processing the
1201 cell immediately. Previously we would mark the connection for
1202 close, but continue processing the cell as if the connection were
1203 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
1205 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
1206 - Allow the nanosleep() system call, which glibc uses to implement
1207 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
1209 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
1210 - When running the hs_ntor_ref.py test, make sure only to pass
1211 strings (rather than "bytes" objects) to the Python subprocess
1212 module. Python 3 on Windows seems to require this. Fixes bug
1213 26535; bugfix on 0.3.1.1-alpha.
1214 - When running the ntor_ref.py test, make sure only to pass strings
1215 (rather than "bytes" objects) to the Python subprocess module.
1216 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
1219 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
1220 - Work around a change in OpenSSL 1.1.1 where return values that
1221 would previously indicate "no password" now indicate an empty
1222 password. Without this workaround, Tor instances running with
1223 OpenSSL 1.1.1 would accept descriptors that other Tor instances
1224 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
1226 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
1227 - Document that the PerConnBW{Rate,Burst} options will fall back to
1228 their corresponding consensus parameters only if those parameters
1229 are set. Previously we had claimed that these values would always
1230 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
1232 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
1233 - Fix a compilation warning on some versions of GCC when building
1234 code that calls routerinfo_get_my_routerinfo() twice, assuming
1235 that the second call will succeed if the first one did. Fixes bug
1236 26269; bugfix on 0.2.8.2-alpha.
1238 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
1239 - Don't consider Tor running as a client if the ControlPort is open,
1240 but no actual client ports are open. Fixes bug 26062; bugfix
1243 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
1244 - Prevent a possible out-of-bounds smartlist read in
1245 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
1247 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
1248 - Fix a very unlikely (impossible, we believe) null pointer
1249 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
1250 Coverity; this is CID 1430932.
1252 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
1253 - Fix a memory leak when a v3 onion service is configured and gets a
1254 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
1255 - When parsing the descriptor signature, look for the token plus an
1256 extra white-space at the end. This is more correct but also will
1257 allow us to support new fields that might start with "signature".
1258 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
1260 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
1261 - Relays now correctly block attempts to re-extend to the previous
1262 relay by Ed25519 identity. Previously they would warn in this
1263 case, but not actually reject the attempt. Fixes bug 26158; bugfix
1266 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
1267 - Avoid a crash when running with DirPort set but ORPort turned off.
1268 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
1270 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
1271 - Silence unused-const-variable warnings in zstd.h with some GCC
1272 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
1274 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
1275 - Avoid intermittent test failures due to a test that had relied on
1276 onion service introduction point creation finishing within 5
1277 seconds of real clock time. Fixes bug 25450; bugfix
1280 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
1281 - Fix a C99 compliance issue in our configuration script that caused
1282 compilation issues when compiling Tor with certain versions of
1283 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
1285 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
1286 - Fix a number of small memory leaks identified by coverity. Fixes
1287 bug 26467; bugfix on numerous Tor versions.
1289 o Code simplification and refactoring (backport from 0.3.3.5-rc):
1290 - Move the list of default directory authorities to its own file.
1291 Closes ticket 24854. Patch by "beastr0".
1294 Changes in version 0.2.9.16 - 2018-07-13
1295 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
1296 bridge relays should upgrade. We also take this opportunity to backport
1299 o Directory authority changes:
1300 - The "Bifroest" bridge authority has been retired; the new bridge
1301 authority is "Serge", and it is operated by George from the
1302 TorBSD project. Closes ticket 26771.
1304 o Directory authority changes (backport from 0.3.3.7):
1305 - Add an IPv6 address for the "dannenberg" directory authority.
1306 Closes ticket 26343.
1308 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
1309 - When directory authorities read a zero-byte bandwidth file, they
1310 would previously log a warning with the contents of an
1311 uninitialised buffer. They now log a warning about the empty file
1312 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
1314 o Minor features (sandbox, backport from 0.3.3.4-alpha):
1315 - Explicitly permit the poll() system call when the Linux
1316 seccomp2-based sandbox is enabled: apparently, some versions of
1317 libc use poll() when calling getpwnam(). Closes ticket 25313.
1319 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
1320 - Our .travis.yml configuration now includes support for testing the
1321 results of "make distcheck". (It's not uncommon for "make check"
1322 to pass but "make distcheck" to fail.) Closes ticket 25814.
1323 - Our Travis CI configuration now integrates with the Coveralls
1324 coverage analysis tool. Closes ticket 25818.
1326 o Minor features (compilation, backport from 0.3.4.4-rc):
1327 - When building Tor, prefer to use Python 3 over Python 2, and more
1328 recent (contemplated) versions over older ones. Closes
1331 o Minor features (geoip):
1332 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1333 Country database. Closes ticket 26674.
1335 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
1336 - Upon receiving a malformed connected cell, stop processing the
1337 cell immediately. Previously we would mark the connection for
1338 close, but continue processing the cell as if the connection were
1339 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
1341 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
1342 - Allow the nanosleep() system call, which glibc uses to implement
1343 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
1345 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
1346 - When running the ntor_ref.py test, make sure only to pass strings
1347 (rather than "bytes" objects) to the Python subprocess module.
1348 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
1351 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
1352 - Work around a change in OpenSSL 1.1.1 where return values that
1353 would previously indicate "no password" now indicate an empty
1354 password. Without this workaround, Tor instances running with
1355 OpenSSL 1.1.1 would accept descriptors that other Tor instances
1356 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
1358 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
1359 - Fix a compilation warning on some versions of GCC when building
1360 code that calls routerinfo_get_my_routerinfo() twice, assuming
1361 that the second call will succeed if the first one did. Fixes bug
1362 26269; bugfix on 0.2.8.2-alpha.
1364 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
1365 - Don't consider Tor running as a client if the ControlPort is open,
1366 but no actual client ports are open. Fixes bug 26062; bugfix
1369 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
1370 - Prevent a possible out-of-bounds smartlist read in
1371 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
1373 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
1374 - Fix a very unlikely (impossible, we believe) null pointer
1375 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
1376 Coverity; this is CID 1430932.
1378 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
1379 - Fix a number of small memory leaks identified by coverity. Fixes
1380 bug 26467; bugfix on numerous Tor versions.
1382 o Code simplification and refactoring (backport from 0.3.3.5-rc):
1383 - Move the list of default directory authorities to its own file.
1384 Closes ticket 24854. Patch by "beastr0".
1387 Changes in version 0.3.4.4-rc - 2018-07-09
1388 Tor 0.3.4.4-rc fixes several small compilation, portability, and
1389 correctness issues in previous versions of Tor. This version is a
1390 release candidate: if no serious bugs are found, we expect that the
1391 stable 0.3.4 release will be (almost) the same as this release.
1393 o Minor features (compilation):
1394 - When building Tor, prefer to use Python 3 over Python 2, and more
1395 recent (contemplated) versions over older ones. Closes
1398 o Minor features (geoip):
1399 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1400 Country database. Closes ticket 26674.
1402 o Minor features (Rust, portability):
1403 - Rust cross-compilation is now supported. Closes ticket 25895.
1405 o Minor bugfixes (compilation):
1406 - Fix a compilation warning on some versions of GCC when building
1407 code that calls routerinfo_get_my_routerinfo() twice, assuming
1408 that the second call will succeed if the first one did. Fixes bug
1409 26269; bugfix on 0.2.8.2-alpha.
1411 o Minor bugfixes (control port):
1412 - Report the port correctly when a port is configured to bind to
1413 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
1414 - Handle the HSADDRESS= argument to the HSPOST command properly.
1415 (Previously, this argument was misparsed and thus ignored.) Fixes
1416 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
1418 o Minor bugfixes (correctness, flow control):
1419 - Upon receiving a stream-level SENDME cell, verify that our window
1420 has not grown too large. Fixes bug 26214; bugfix on svn
1423 o Minor bugfixes (memory, correctness):
1424 - Fix a number of small memory leaks identified by coverity. Fixes
1425 bug 26467; bugfix on numerous Tor versions.
1427 o Minor bugfixes (testing, compatibility):
1428 - When running the hs_ntor_ref.py test, make sure only to pass
1429 strings (rather than "bytes" objects) to the Python subprocess
1430 module. Python 3 on Windows seems to require this. Fixes bug
1431 26535; bugfix on 0.3.1.1-alpha.
1432 - When running the ntor_ref.py test, make sure only to pass strings
1433 (rather than "bytes" objects) to the Python subprocess module.
1434 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
1438 Changes in version 0.3.3.8 - 2018-07-09
1439 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
1440 fixes for a memory leak affecting directory authorities.
1442 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
1443 - Stop leaking memory on directory authorities when planning to
1444 vote. This bug was crashing authorities by exhausting their
1445 memory. Fixes bug 26435; bugfix on 0.3.3.6.
1447 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
1448 - Make sure that failing tests in Rust will actually cause the build
1449 to fail: previously, they were ignored. Fixes bug 26258; bugfix
1452 o Minor features (compilation, backport from 0.3.4.4-rc):
1453 - When building Tor, prefer to use Python 3 over Python 2, and more
1454 recent (contemplated) versions over older ones. Closes
1457 o Minor features (geoip):
1458 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1459 Country database. Closes ticket 26674.
1461 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
1462 - Add several checks to detect whether Tor relays are uploading
1463 their descriptors without specifying why they regenerated them.
1464 Diagnostic for ticket 25686.
1466 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
1467 - Don't count path selection failures as circuit build failures.
1468 This change should eliminate cases where Tor blames its guard or
1469 the network for situations like insufficient microdescriptors
1470 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
1473 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
1474 - Fix a compilation warning on some versions of GCC when building
1475 code that calls routerinfo_get_my_routerinfo() twice, assuming
1476 that the second call will succeed if the first one did. Fixes bug
1477 26269; bugfix on 0.2.8.2-alpha.
1479 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
1480 - Handle the HSADDRESS= argument to the HSPOST command properly.
1481 (Previously, this argument was misparsed and thus ignored.) Fixes
1482 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
1484 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
1485 - Fix a number of small memory leaks identified by coverity. Fixes
1486 bug 26467; bugfix on numerous Tor versions.
1488 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
1489 - Relays now correctly block attempts to re-extend to the previous
1490 relay by Ed25519 identity. Previously they would warn in this
1491 case, but not actually reject the attempt. Fixes bug 26158; bugfix
1494 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
1495 - When shutting down, Tor now clears all the flags in the control.c
1496 module. This should prevent a bug where authentication cookies are
1497 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
1499 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
1500 - When running the hs_ntor_ref.py test, make sure only to pass
1501 strings (rather than "bytes" objects) to the Python subprocess
1502 module. Python 3 on Windows seems to require this. Fixes bug
1503 26535; bugfix on 0.3.1.1-alpha.
1504 - When running the ntor_ref.py test, make sure only to pass strings
1505 (rather than "bytes" objects) to the Python subprocess module.
1506 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
1510 Changes in version 0.3.4.3-alpha - 2018-06-26
1511 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
1512 one that was causing stability issues on directory authorities.
1514 o Major bugfixes (directory authority):
1515 - Stop leaking memory on directory authorities when planning to
1516 vote. This bug was crashing authorities by exhausting their
1517 memory. Fixes bug 26435; bugfix on 0.3.3.6.
1519 o Major bugfixes (rust, testing):
1520 - Make sure that failing tests in Rust will actually cause the build
1521 to fail: previously, they were ignored. Fixes bug 26258; bugfix
1524 o Minor feature (directory authorities):
1525 - Stop warning about incomplete bw lines before the first complete
1526 bw line has been found, so that additional header lines can be
1527 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
1529 o Minor features (relay, diagnostic):
1530 - Add several checks to detect whether Tor relays are uploading
1531 their descriptors without specifying why they regenerated them.
1532 Diagnostic for ticket 25686.
1534 o Minor features (unit tests):
1535 - Test complete bandwidth measurements files, and test that
1536 incomplete bandwidth lines only give warnings when the end of the
1537 header has not been detected. Fixes bug 25947; bugfix
1540 o Minor bugfixes (compilation):
1541 - Refrain from compiling unit testing related object files when
1542 --disable-unittests is set to configure script. Fixes bug 24891;
1543 bugfix on 0.2.5.1-alpha.
1544 - When linking the libtor_testing.a library, only include the
1545 dirauth object files once. Previously, they were getting added
1546 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
1547 - The --enable-fatal-warnings flag now affects Rust code as well.
1548 Closes ticket 26245.
1550 o Minor bugfixes (onion services):
1551 - Recompute some consensus information after detecting a clock jump,
1552 or after transitioning from a non-live consensus to a live
1553 consensus. We do this to avoid having an outdated state, and
1554 miscalculating the index for next-generation onion services. Fixes
1555 bug 24977; bugfix on 0.3.2.1-alpha.
1557 o Minor bugfixes (relay):
1558 - Relays now correctly block attempts to re-extend to the previous
1559 relay by Ed25519 identity. Previously they would warn in this
1560 case, but not actually reject the attempt. Fixes bug 26158; bugfix
1563 o Minor bugfixes (testing):
1564 - Fix compilation of the doctests in the Rust crypto crate. Fixes
1565 bug 26415; bugfix on 0.3.4.1-alpha.
1566 - Instead of trying to read the geoip configuration files from
1567 within the unit tests, instead create our own ersatz files with
1568 just enough geoip data in the format we expect. Trying to read
1569 from the source directory created problems on Windows with mingw,
1570 where the build system's paths are not the same as the platform's
1571 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
1572 - Refrain from trying to get an item from an empty smartlist in
1573 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
1574 to catch improper smartlist usage. Furthermore, enable
1575 DEBUG_SMARTLIST globally when build is configured with fragile
1576 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
1579 Changes in version 0.3.3.7 - 2018-06-12
1580 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
1581 fixes for bugs affecting compatibility and stability.
1583 o Directory authority changes:
1584 - Add an IPv6 address for the "dannenberg" directory authority.
1585 Closes ticket 26343.
1587 o Minor features (geoip):
1588 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
1589 Country database. Closes ticket 26351.
1591 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
1592 - Work around a change in OpenSSL 1.1.1 where return values that
1593 would previously indicate "no password" now indicate an empty
1594 password. Without this workaround, Tor instances running with
1595 OpenSSL 1.1.1 would accept descriptors that other Tor instances
1596 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
1598 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
1599 - Silence unused-const-variable warnings in zstd.h with some GCC
1600 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
1602 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
1603 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
1604 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
1605 miscounting the total number of circuits for these field values.)
1606 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
1608 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
1609 - Prevent a possible out-of-bounds smartlist read in
1610 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
1612 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
1613 - Only select relays when they have the descriptors we prefer to use
1614 for them. This change fixes a bug where we could select a relay
1615 because it had _some_ descriptor, but reject it later with a
1616 nonfatal assertion error because it didn't have the exact one we
1617 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
1620 Changes in version 0.3.4.2-alpha - 2018-06-12
1621 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
1622 release, and forward-ports an authority-only security fix from 0.3.3.6.
1624 o Directory authority changes:
1625 - Add an IPv6 address for the "dannenberg" directory authority.
1626 Closes ticket 26343.
1628 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
1629 - Fix a bug that could have allowed an attacker to force a directory
1630 authority to use up all its RAM by passing it a maliciously
1631 crafted protocol versions string. Fixes bug 25517; bugfix on
1632 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
1634 o Minor features (continuous integration):
1635 - Add the necessary configuration files for continuous integration
1636 testing on Windows, via the Appveyor platform. Closes ticket
1637 25549. Patches from Marcin Cieślak and Isis Lovecruft.
1639 o Minor features (geoip):
1640 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
1641 Country database. Closes ticket 26351.
1643 o Minor bugfixes (compatibility, openssl):
1644 - Work around a change in OpenSSL 1.1.1 where return values that
1645 would previously indicate "no password" now indicate an empty
1646 password. Without this workaround, Tor instances running with
1647 OpenSSL 1.1.1 would accept descriptors that other Tor instances
1648 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
1650 o Minor bugfixes (compilation):
1651 - Silence unused-const-variable warnings in zstd.h with some GCC
1652 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
1653 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
1654 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
1655 - Avoid a compiler warning when casting the return value of
1656 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
1657 26283; bugfix on 0.2.4.10-alpha.
1659 o Minor bugfixes (control port):
1660 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
1661 CIRC_BW events. Previously, such cells were counted entirely in
1662 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
1665 o Minor bugfixes (controller):
1666 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
1667 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
1668 miscounting the total number of circuits for these field values.)
1669 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
1671 o Minor bugfixes (hardening):
1672 - Prevent a possible out-of-bounds smartlist read in
1673 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
1675 o Minor bugfixes (onion services):
1676 - Fix a bug that blocked the creation of ephemeral v3 onion
1677 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
1679 o Minor bugfixes (test coverage tools):
1680 - Update our "cov-diff" script to handle output from the latest
1681 version of gcov, and to remove extraneous timestamp information
1682 from its output. Fixes bugs 26101 and 26102; bugfix
1686 Changes in version 0.3.3.6 - 2018-05-22
1687 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
1688 backports several important fixes from the 0.3.4.1-alpha.
1690 The Tor 0.3.3 series includes controller support and other
1691 improvements for v3 onion services, official support for embedding Tor
1692 within other applications, and our first non-trivial module written in
1693 the Rust programming language. (Rust is still not enabled by default
1694 when building Tor.) And as usual, there are numerous other smaller
1695 bugfixes, features, and improvements.
1697 Below are the changes since 0.3.3.5-rc. For a list of all changes
1698 since 0.3.2.10, see the ReleaseNotes file.
1700 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
1701 - When directory authorities read a zero-byte bandwidth file, they
1702 would previously log a warning with the contents of an
1703 uninitialised buffer. They now log a warning about the empty file
1704 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
1706 o Major bugfixes (security, directory authority, denial-of-service):
1707 - Fix a bug that could have allowed an attacker to force a directory
1708 authority to use up all its RAM by passing it a maliciously
1709 crafted protocol versions string. Fixes bug 25517; bugfix on
1710 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
1712 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
1713 - Avoid a rare assertion failure in the circuit build timeout code
1714 if we fail to allow any circuits to actually complete. Fixes bug
1715 25733; bugfix on 0.2.2.2-alpha.
1717 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
1718 - Avoid a crash when testing router reachability on a router that
1719 could have an ed25519 ID, but which does not. Fixes bug 25415;
1720 bugfix on 0.3.3.2-alpha.
1722 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
1723 - Correctly detect when onion services get disabled after HUP. Fixes
1724 bug 25761; bugfix on 0.3.2.1.
1726 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
1727 - Impose a limit on circuit cell queue size. The limit can be
1728 controlled by a consensus parameter. Fixes bug 25226; bugfix
1731 o Minor features (compatibility, backport from 0.3.4.1-alpha):
1732 - Avoid some compilation warnings with recent versions of LibreSSL.
1733 Closes ticket 26006.
1735 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
1736 - Our .travis.yml configuration now includes support for testing the
1737 results of "make distcheck". (It's not uncommon for "make check"
1738 to pass but "make distcheck" to fail.) Closes ticket 25814.
1739 - Our Travis CI configuration now integrates with the Coveralls
1740 coverage analysis tool. Closes ticket 25818.
1742 o Minor features (geoip):
1743 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
1744 database. Closes ticket 26104.
1746 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
1747 - Don't consider Tor running as a client if the ControlPort is open,
1748 but no actual client ports are open. Fixes bug 26062; bugfix
1751 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
1752 - Upon receiving a malformed connected cell, stop processing the
1753 cell immediately. Previously we would mark the connection for
1754 close, but continue processing the cell as if the connection were
1755 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
1757 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
1758 - Stop saying in the manual that clients cache ipv4 dns answers from
1759 exit relays. We haven't used them since 0.2.6.3-alpha, and in
1760 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
1761 we forgot to say so in the man page. Fixes bug 26052; bugfix
1764 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
1765 - Allow the nanosleep() system call, which glibc uses to implement
1766 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
1768 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
1769 - Fix a memory leak when a v3 onion service is configured and gets a
1770 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
1771 - When parsing the descriptor signature, look for the token plus an
1772 extra white-space at the end. This is more correct but also will
1773 allow us to support new fields that might start with "signature".
1774 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
1776 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
1777 - Avoid a crash when running with DirPort set but ORPort turned off.
1778 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
1780 o Documentation (backport from 0.3.4.1-alpha):
1781 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
1782 ticket 25857. Patch from "CTassisF".
1785 Changes in version 0.3.4.1-alpha - 2018-05-17
1786 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
1787 includes refactoring to begin reducing Tor's binary size and idle CPU
1788 usage on mobile, along with prep work for new bandwidth scanners,
1789 improvements to the experimental "vanguards" feature, and numerous
1790 other small features and bugfixes.
1792 o New system requirements:
1793 - Tor no longer tries to support old operating systems without
1794 mmap() or some local equivalent. Apparently, compilation on such
1795 systems has been broken for some time, without anybody noticing or
1796 complaining. Closes ticket 25398.
1798 o Major feature (directory authority, modularization):
1799 - The directory authority subsystem has been modularized. The code
1800 is now located in src/or/dirauth/, and is compiled in by default.
1801 To disable the module, the configure option
1802 --disable-module-dirauth has been added. This module may be
1803 disabled by default in some future release. Closes ticket 25610.
1805 o Major features (main loop, CPU usage):
1806 - When Tor is disabled (via DisableNetwork or via hibernation), it
1807 no longer needs to run any per-second events. This change should
1808 make it easier for mobile applications to disable Tor while the
1809 device is sleeping, or Tor is not running. Closes ticket 26063.
1810 - Tor no longer enables all of its periodic events by default.
1811 Previously, Tor would enable all possible main loop events,
1812 regardless of whether it needed them. Furthermore, many of these
1813 events are now disabled with Tor is hibernating or DisableNetwork
1814 is set. This is a big step towards reducing client CPU usage by
1815 reducing the amount of wake-ups the daemon does. Closes ticket
1817 - The bandwidth-limitation logic has been refactored so that
1818 bandwidth calculations are performed on-demand, rather than every
1819 TokenBucketRefillInterval milliseconds. This change should improve
1820 the granularity of our bandwidth calculations, and limit the
1821 number of times that the Tor process needs to wake up when it is
1822 idle. Closes ticket 25373.
1823 - Move responsibility for many operations from a once-per-second
1824 callback to a callback that is only scheduled as needed. Moving
1825 this functionality has allowed us to disable the callback when
1826 Tor's network is disabled. Once enough items are removed from our
1827 once-per-second callback, we can eliminate it entirely to conserve
1828 CPU when idle. The functionality removed includes: closing
1829 connections, circuits, and channels (ticket 25932); consensus
1830 voting (25937); flushing log callbacks (25951); honoring delayed
1831 SIGNEWNYM requests (25949); rescanning the consensus cache
1832 (25931); saving the state file to disk (25948); warning relay
1833 operators about unreachable ports (25952); and keeping track of
1834 Tor's uptime (26009).
1836 o Major bugfixes (directory authorities, security):
1837 - When directory authorities read a zero-byte bandwidth file, they
1838 would previously log a warning with the contents of an
1839 uninitialised buffer. They now log a warning about the empty file
1840 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
1842 o Major bugfixes (crash):
1843 - Avoid a rare assertion failure in the circuit build timeout code
1844 if we fail to allow any circuits to actually complete. Fixes bug
1845 25733; bugfix on 0.2.2.2-alpha.
1847 o Major bugfixes (directory authority):
1848 - Avoid a crash when testing router reachability on a router that
1849 could have an ed25519 ID, but which does not. Fixes bug 25415;
1850 bugfix on 0.3.3.2-alpha.
1852 o Major bugfixes (onion service):
1853 - Correctly detect when onion services get disabled after HUP. Fixes
1854 bug 25761; bugfix on 0.3.2.1.
1856 o Major bugfixes (protover, voting):
1857 - Revise Rust implementation of protover to use a more memory-
1858 efficient voting algorithm and corresponding data structures, thus
1859 avoiding a potential (but small impact) DoS attack where specially
1860 crafted protocol strings would expand to several potential
1861 megabytes in memory. In the process, several portions of code were
1862 revised to be methods on new, custom types, rather than functions
1863 taking interchangeable types, thus increasing type safety of the
1864 module. Custom error types and handling were added as well, in
1865 order to facilitate better error dismissal/handling in outside
1866 crates and avoid mistakenly passing an internal error string to C
1867 over the FFI boundary. Many tests were added, and some previous
1868 differences between the C and Rust implementations have been
1869 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
1871 o Major bugfixes (relay, denial of service):
1872 - Impose a limit on circuit cell queue size. The limit can be
1873 controlled by a consensus parameter. Fixes bug 25226; bugfix
1876 o Minor features (accounting):
1877 - When Tor becomes dormant, it now uses a scheduled event to wake up
1878 at the right time. Previously, we would use the per-second timer
1879 to check whether to wake up, but we no longer have any per-second
1880 timers enabled when the network is disabled. Closes ticket 26064.
1882 o Minor features (code quality):
1883 - Add optional spell-checking for the Tor codebase, using the
1884 "misspell" program. To use this feature, run "make check-typos".
1885 Closes ticket 25024.
1887 o Minor features (compatibility):
1888 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
1889 the no-deprecated option, and builds correctly with them. Closes
1890 tickets 19429, 19981, and 25353.
1891 - Avoid some compilation warnings with recent versions of LibreSSL.
1892 Closes ticket 26006.
1894 o Minor features (compression, zstd):
1895 - When running with zstd, Tor now considers using advanced functions
1896 that the zstd maintainers have labeled as potentially unstable. To
1897 prevent breakage, Tor will only use this functionality when the
1898 runtime version of the zstd library matches the version with which
1899 Tor was compiled. Closes ticket 25162.
1901 o Minor features (configuration):
1902 - The "DownloadSchedule" options have been renamed to end with
1903 "DownloadInitialDelay". The old names are still allowed, but will
1904 produce a warning. Comma-separated lists are still permitted for
1905 these options, but all values after the first are ignored (as they
1906 have been since 0.2.9). Closes ticket 23354.
1908 o Minor features (continuous integration):
1909 - Our .travis.yml configuration now includes support for testing the
1910 results of "make distcheck". (It's not uncommon for "make check"
1911 to pass but "make distcheck" to fail.) Closes ticket 25814.
1912 - Our Travis CI configuration now integrates with the Coveralls
1913 coverage analysis tool. Closes ticket 25818.
1915 o Minor features (control port):
1916 - Introduce GETINFO "current-time/{local,utc}" to return the local
1917 and UTC times respectively in ISO format. This helps a controller
1918 like Tor Browser detect a time-related error. Closes ticket 25511.
1919 Patch by Neel Chauhan.
1920 - Introduce new fields to the CIRC_BW event. There are two new
1921 fields in each of the read and written directions. The DELIVERED
1922 fields report the total valid data on the circuit, as measured by
1923 the payload sizes of verified and error-checked relay command
1924 cells. The OVERHEAD fields report the total unused bytes in each
1925 of these cells. Closes ticket 25903.
1927 o Minor features (directory authority):
1928 - Directory authorities now open their key-pinning files as O_SYNC,
1929 to limit their chances of accidentally writing partial lines.
1930 Closes ticket 23909.
1932 o Minor features (directory authority, forward compatibility):
1933 - Make the lines of the measured bandwidth file able to contain
1934 their entries in any order. Previously, the node_id entry needed
1935 to come first. Closes ticket 26004.
1937 o Minor features (entry guards):
1938 - Introduce a new torrc option NumPrimaryGuards for controlling the
1939 number of primary guards. Closes ticket 25843.
1941 o Minor features (geoip):
1942 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
1943 database. Closes ticket 26104.
1945 o Minor features (performance):
1946 - Avoid a needless call to malloc() when processing an incoming
1947 relay cell. Closes ticket 24914.
1948 - Make our timing-wheel code run a tiny bit faster on 32-bit
1949 platforms, by preferring 32-bit math to 64-bit. Closes
1951 - Avoid a needless malloc()/free() pair every time we handle an ntor
1952 handshake. Closes ticket 25150.
1954 o Minor features (testing):
1955 - Add a unit test for voting_schedule_get_start_of_next_interval().
1956 Closes ticket 26014, and helps make unit test coverage
1958 - A new unittests module specifically for testing the functions in
1959 the (new-ish) bridges.c module has been created with new
1960 unittests, raising the code coverage percentages. Closes 25425.
1961 - We now have improved testing for addressmap_get_virtual_address()
1962 function. This should improve our test coverage, and make our test
1963 coverage more deterministic. Closes ticket 25993.
1965 o Minor features (timekeeping, circuit scheduling):
1966 - When keeping track of how busy each circuit have been recently on
1967 a given connection, use coarse-grained monotonic timers rather
1968 than gettimeofday(). This change should marginally increase
1969 accuracy and performance. Implements part of ticket 25927.
1971 o Minor bugfixes (bandwidth management):
1972 - Consider ourselves "low on write bandwidth" if we have exhausted
1973 our write bandwidth some time in the last second. This was the
1974 documented behavior before, but the actual behavior was to change
1975 this value every TokenBucketRefillInterval. Fixes bug 25828;
1976 bugfix on 0.2.3.5-alpha.
1978 o Minor bugfixes (C correctness):
1979 - Add a missing lock acquisition in the shutdown code of the control
1980 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
1981 Coverity; this is CID 1433643.
1983 o Minor bugfixes (circuit path selection):
1984 - Don't count path selection failures as circuit build failures.
1985 This change should eliminate cases where Tor blames its guard or
1986 the network for situations like insufficient microdescriptors
1987 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
1990 o Minor bugfixes (client):
1991 - Don't consider Tor running as a client if the ControlPort is open,
1992 but no actual client ports are open. Fixes bug 26062; bugfix
1995 o Minor bugfixes (code style):
1996 - Fixed multiple includes of transports.h in src/or/connection.c
1997 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
1998 - Remove the unused variable n_possible from the function
1999 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
2001 o Minor bugfixes (control interface):
2002 - Respond with more human-readable error messages to GETINFO exit-
2003 policy/* requests. Also, let controller know if an error is
2004 transient (response code 551) or not (response code 552). Fixes
2005 bug 25852; bugfix on 0.2.8.1-alpha.
2007 o Minor bugfixes (controller):
2008 - Make CIRC_BW event reflect the total of all data sent on a
2009 circuit, including padding and dropped cells. Also fix a mis-
2010 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
2011 bugfix on 0.2.5.2-alpha.
2013 o Minor bugfixes (correctness, client):
2014 - Upon receiving a malformed connected cell, stop processing the cell
2015 immediately. Previously we would mark the connection for close, but
2016 continue processing the cell as if the connection were open. Fixes bug
2017 26072; bugfix on 0.2.4.7-alpha.
2019 o Minor bugfixes (directory client):
2020 - When unverified-consensus is verified, rename it to cached-
2021 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
2022 - Fixed launching a certificate fetch always during the scheduled
2023 periodic consensus fetch by fetching only in those cases when
2024 consensus are waiting for certs. Fixes bug 24740; bugfix
2027 o Minor bugfixes (documentation):
2028 - Stop saying in the manual that clients cache ipv4 dns answers from
2029 exit relays. We haven't used them since 0.2.6.3-alpha, and in
2030 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
2031 we forgot to say so in the man page. Fixes bug 26052; bugfix
2034 o Minor bugfixes (error reporting):
2035 - Improve tolerance for directory authorities with skewed clocks.
2036 Previously, an authority with a clock more than 60 seconds ahead
2037 could cause a client with a correct clock to warn that the
2038 client's clock was behind. Now the clocks of a majority of
2039 directory authorities have to be ahead of the client before this
2040 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
2042 o Minor bugfixes (Linux seccomp2 sandbox):
2043 - Allow the nanosleep() system call, which glibc uses to implement
2044 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
2046 o Minor bugfixes (onion service):
2047 - Fix a memory leak when a v3 onion service is configured and gets a
2048 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
2049 - When parsing the descriptor signature, look for the token plus an
2050 extra white-space at the end. This is more correct but also will
2051 allow us to support new fields that might start with "signature".
2052 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
2054 o Minor bugfixes (path selection):
2055 - Only select relays when they have the descriptors we prefer to use
2056 for them. This change fixes a bug where we could select a relay
2057 because it had _some_ descriptor, but reject it later with a
2058 nonfatal assertion error because it didn't have the exact one we
2059 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
2061 o Minor bugfixes (portability):
2062 - Do not align mmap length, as it is not required by POSIX, and the
2063 getpagesize function is deprecated. Fixes bug 25399; bugfix
2066 o Minor bugfixes (portability, FreeBSD):
2067 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
2068 does not stringify on FreeBSD, so we switch to tor_asprintf().
2069 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
2071 o Minor bugfixes (relay statistics):
2072 - When a relay is collecting internal statistics about how many
2073 create cell requests it has seen of each type, accurately count
2074 the requests from relays that temporarily fall out of the
2075 consensus. (To be extra conservative, we were already ignoring
2076 requests from clients in our counts, and we continue ignoring them
2077 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
2079 o Minor bugfixes (relay, crash):
2080 - Avoid a crash when running with DirPort set but ORPort turned off.
2081 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
2083 o Minor bugfixes (restart-in-process):
2084 - When shutting down, Tor now clears all the flags in the control.c
2085 module. This should prevent a bug where authentication cookies are
2086 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
2088 o Minor bugfixes (testing):
2089 - When testing workqueue event-cancellation, make sure that we
2090 actually cancel an event, and that cancel each event with equal
2091 probability. (It was previously possible, though extremely
2092 unlikely, for our event-canceling test not to cancel any events.)
2093 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
2094 - Repeat part of the test in test_client_pick_intro() a number of
2095 times, to give it consistent coverage. Fixes bug 25996; bugfix
2097 - Remove randomness from the hs_common/responsible_hsdirs test, so
2098 that it always takes the same path through the function it tests.
2099 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
2100 - Change the behavior of the "channel/outbound" test so that it
2101 never causes a 10-second rollover for the EWMA circuitmux code.
2102 Previously, this behavior would happen randomly, and result in
2103 fluctuating test coverage. Fixes bug 25994; bugfix
2105 - Use X509_new() to allocate certificates that will be freed later
2106 with X509_free(). Previously, some parts of the unit tests had
2107 used tor_malloc_zero(), which is incorrect, and which caused test
2108 failures on Windows when they were built with extra hardening.
2109 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
2111 - While running the circuit_timeout test, fix the PRNG to a
2112 deterministic AES stream, so that the test coverage from this test
2113 will itself be deterministic. Fixes bug 25995; bugfix
2116 o Minor bugfixes (vanguards):
2117 - Allow the last hop in a vanguard circuit to be the same as our
2118 first, to prevent the adversary from influencing guard node choice
2119 by choice of last hop. Also prevent the creation of A - B - A
2120 paths, or A - A paths, which are forbidden by relays. Fixes bug
2121 25870; bugfix on 0.3.3.1-alpha.
2123 o Code simplification and refactoring:
2124 - Remove duplicate code in parse_{c,s}method_line and bootstrap
2125 their functionalities into a single function. Fixes bug 6236;
2126 bugfix on 0.2.3.6-alpha.
2127 - We remove the PortForwsrding and PortForwardingHelper options,
2128 related functions, and the port_forwarding tests. These options
2129 were used by the now-deprecated Vidalia to help ordinary users
2130 become Tor relays or bridges. Closes ticket 25409. Patch by
2132 - In order to make the OR and dir checking function in router.c less
2133 confusing we renamed some functions and
2134 consider_testing_reachability() has been split into
2135 router_should_check_reachability() and
2136 router_do_reachability_checks(). Also we improved the documentation
2137 in some functions. Closes ticket 18918.
2138 - Initial work to isolate Libevent usage to a handful of modules in
2139 our codebase, to simplify our call structure, and so that we can
2140 more easily change event loops in the future if needed. Closes
2142 - Introduce a function to call getsockname() and return tor_addr_t,
2143 to save a little complexity throughout the codebase. Closes
2145 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
2146 as hsdir_index is always present. Also, we move hsdir_index_t into
2147 or.h. Closes ticket 23094. Patch by Neel Chauhan.
2148 - Merge functions used for describing nodes and suppress the
2149 functions that do not allocate memory for the output buffer
2150 string. NODE_DESC_BUF_LEN constant and format_node_description()
2151 function cannot be used externally from router.c module anymore.
2152 Closes ticket 25432. Patch by valentecaio.
2153 - Our main loop has been simplified so that all important operations
2154 happen inside events. Previously, some operations had to happen
2155 outside the event loop, to prevent infinite sequences of event
2156 activations. Closes ticket 25374.
2157 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
2158 it in register_intro_circ() and service_intro_point_new(). This
2159 prevents the digest from being re-calculated each time. Closes
2160 ticket 23107. Patch by Neel Chauhan.
2161 - Refactor token-bucket implementations to use a common backend.
2162 Closes ticket 25766.
2163 - Remove extern declaration of stats_n_seconds_working variable from
2164 main, protecting its accesses with get_uptime() and reset_uptime()
2165 functions. Closes ticket 25081, patch by “valentecaio”.
2166 - Remove our previous logic for "cached gettimeofday()" -- our
2167 coarse monotonic timers are fast enough for this purpose, and far
2168 less error-prone. Implements part of ticket 25927.
2169 - Remove the return value for fascist_firewall_choose_address_base(),
2170 and sister functions such as fascist_firewall_choose_address_node()
2171 and fascist_firewall_choose_address_rs(). Also, while we're here,
2172 initialize the ap argument as leaving it uninitialized can pose a
2173 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
2174 - Rename two fields of connection_t struct. timestamp_lastwritten is
2175 renamed to timestamp_last_write_allowed and timestamp_lastread is
2176 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
2178 - Since Tor requires C99, remove our old workaround code for libc
2179 implementations where free(NULL) doesn't work. Closes ticket 24484.
2180 - Use our standard rate-limiting code to deal with excessive
2181 libevent failures, rather than the hand-rolled logic we had
2182 before. Closes ticket 26016.
2183 - We remove the return value of node_get_prim_orport() and
2184 node_get_prim_dirport(), and introduce node_get_prim_orport() in
2185 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
2186 check for a null address. Closes ticket 23873. Patch by
2188 - We switch to should_record_bridge_info() in
2189 geoip_note_client_seen() and options_need_geoip_info() instead of
2190 accessing the configuration values directly. Fixes bug 25290;
2191 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
2193 o Deprecated features:
2194 - As we are not recommending 0.2.5 anymore, we require relays that
2195 once had an ed25519 key associated with their RSA key to always
2196 have that key, instead of allowing them to drop back to a version
2197 that didn't support ed25519. This means they need to use a new RSA
2198 key if the want to downgrade to an older version of tor without
2199 ed25519. Closes ticket 20522.
2202 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
2203 ticket 25857. Patch from "CTassisF".
2206 - Directory authorities will no longer support voting according to
2207 any consensus method before consensus method 25. This keeps
2208 authorities compatible with all authorities running 0.2.9.8 and
2209 later, and does not break any clients or relays. Implements ticket
2210 24378 and proposal 290.
2211 - The PortForwarding and PortForwardingHelper features have been
2212 removed. The reasoning is, given that implementations of NAT
2213 traversal protocols within common consumer grade routers are
2214 frequently buggy, and that the target audience for a NAT punching
2215 feature is a perhaps less-technically-inclined relay operator,
2216 when the helper fails to setup traversal the problems are usually
2217 deep, ugly, and very router specific, making them horrendously
2218 impossible for technical support to reliable assist with, and thus
2219 resulting in frustration all around. Unfortunately, relay
2220 operators who would like to run relays behind NATs will need to
2221 become more familiar with the port forwarding configurations on
2222 their local router. Closes 25409.
2223 - The TestingEnableTbEmptyEvent option has been removed. It was used
2224 in testing simulations to measure how often connection buckets
2225 were emptied, in order to improve our scheduling, but it has not
2226 been actively used in years. Closes ticket 25760.
2227 - The old "round-robin" circuit multiplexer (circuitmux)
2228 implementation has been removed, along with a fairly large set of
2229 code that existed to support it. It has not been the default
2230 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
2231 but it still required an unreasonable amount of memory and CPU.
2232 Closes ticket 25268.
2235 Changes in version 0.3.3.5-rc - 2018-04-15
2236 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
2237 including some that could affect reliability or correctness.
2239 This is the first release candidate in the 0.3.3 series. If we find no
2240 new bugs or regression here, then the first stable 0.3.3 release will
2241 be nearly identical to this one.
2243 o Major bugfixes (security, protover, voting):
2244 - Revise Rust implementation of protover to use a more memory-
2245 efficient voting algorithm and corresponding data structures, thus
2246 avoiding a potential memory-based DoS attack where specially
2247 crafted protocol strings would expand to fill available memory.
2248 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
2250 o Major bugfixes (performance, load balancing):
2251 - Directory authorities no longer vote in favor of the Guard flag
2252 for relays without directory support. Starting in Tor
2253 0.3.0.1-alpha, clients have been avoiding using such relays in the
2254 Guard position, leading to increasingly broken load balancing for
2255 the 5%-or-so of Guards that don't advertise directory support.
2256 Fixes bug 22310; bugfix on 0.3.0.6.
2258 o Minor feature (continuous integration):
2259 - Update the Travis CI configuration to use the stable Rust channel,
2260 now that we have decided to require that. Closes ticket 25714.
2262 o Minor features (config options):
2263 - Change the way the default value for MaxMemInQueues is calculated.
2264 We now use 40% of the hardware RAM if the system has 8 GB RAM or
2265 more. Otherwise we use the former value of 75%. Closes
2268 o Minor features (geoip):
2269 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
2270 Country database. Closes ticket 25718.
2272 o Minor bugfixes (client):
2273 - When using a listed relay as a bridge, and also using
2274 microdescriptors, and considering that relay as a non-bridge in a
2275 circuit, treat its microdescriptor as a valid source of
2276 information about that relay. This change should prevent a non-
2277 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
2279 o Minor bugfixes (controller):
2280 - Restore the correct operation of the RESOLVE command, which had
2281 been broken since we added the ability to enable/disable DNS on
2282 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
2284 o Minor bugfixes (distribution, compilation, rust):
2285 - Build correctly when the rust dependencies submodule is loaded,
2286 but the TOR_RUST_DEPENDENCIES environment variable is not set.
2287 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
2288 - Actually include all of our Rust source in our source
2289 distributions. (Previously, a few of the files were accidentally
2290 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
2292 o Minor bugfixes (documentation):
2293 - Document that the PerConnBW{Rate,Burst} options will fall back to
2294 their corresponding consensus parameters only if those parameters
2295 are set. Previously we had claimed that these values would always
2296 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
2297 - Revert a misformatting issue in the ExitPolicy documentation.
2298 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
2300 o Minor bugfixes (exit relay DNS retries):
2301 - Re-attempt timed-out DNS queries 3 times before failure, since our
2302 timeout is 5 seconds for them, but clients wait 10-15. Also allow
2303 slightly more timeouts per resolver when an exit has multiple
2304 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
2306 o Minor bugfixes (onion services):
2307 - Re-instate counting the client HSDir fetch circuits against the
2308 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
2310 - Remove underscores from the _HSLayer{2,3}Nodes options. This
2311 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
2312 Fixes bug 25581; bugfix on 0.3.3.1-alpha
2314 o Code simplification and refactoring:
2315 - Move the list of default directory authorities to its own file.
2316 Closes ticket 24854. Patch by "beastr0".
2318 o Documentation (manpage, denial of service):
2319 - Provide more detail about the denial-of-service options, by
2320 listing each mitigation and explaining how they relate. Closes
2324 Changes in version 0.3.3.4-alpha - 2018-03-29
2325 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
2326 the alpha testing of earlier releases in its series. We are
2327 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
2329 o New system requirements:
2330 - When built with Rust, Tor now depends on version 0.2.39 of the
2331 libc crate. Closes tickets 25310 and 25664.
2333 o Major bugfixes (relay, connection):
2334 - If we have failed to connect to a relay and received a connection
2335 refused, timeout, or similar error (at the TCP level), do not try
2336 that same address/port again for 60 seconds after the failure has
2337 occurred. Fixes bug 24767; bugfix on 0.0.6.
2339 o Minor features (geoip):
2340 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
2341 Country database. Closes ticket 25469.
2343 o Minor features (log messages):
2344 - Improve log message in the out-of-memory handler to include
2345 information about memory usage from the different compression
2346 backends. Closes ticket 25372.
2348 o Minor features (sandbox):
2349 - Explicitly permit the poll() system call when the Linux
2350 seccomp2-based sandbox is enabled: apparently, some versions of
2351 libc use poll() when calling getpwnam(). Closes ticket 25313.
2353 o Minor bugfixes (C correctness):
2354 - Fix a very unlikely (impossible, we believe) null pointer
2355 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
2356 Coverity; this is CID 1430932.
2358 o Minor bugfixes (channel, client):
2359 - Better identify client connection when reporting to the geoip
2360 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
2362 o Minor bugfixes (compilation):
2363 - Fix a C99 compliance issue in our configuration script that caused
2364 compilation issues when compiling Tor with certain versions of
2365 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
2367 o Minor bugfixes (controller, reliability):
2368 - Avoid a (nonfatal) assertion failure when extending a one-hop
2369 circuit from the controller to become a multihop circuit. Fixes
2370 bug 24903; bugfix on 0.2.5.2-alpha.
2372 o Major bugfixes (networking):
2373 - Tor will no longer reject IPv6 address strings from Tor Browser
2374 when they are passed as hostnames in SOCKS5 requests. Fixes bug
2375 25036, bugfix on Tor 0.3.1.2.
2377 o Minor bugfixes (networking):
2378 - string_is_valid_hostname() will not consider IP strings to be
2379 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
2381 o Minor bugfixes (onion service v3):
2382 - Avoid an assertion failure when the next onion service
2383 descriptor rotation type is out of sync with the consensus's
2384 valid-after time. Instead, log a warning message with extra
2385 information, so we can better hunt down the cause of this
2386 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
2388 o Minor bugfixes (testing):
2389 - Avoid intermittent test failures due to a test that had relied on
2390 onion service introduction point creation finishing within 5
2391 seconds of real clock time. Fixes bug 25450; bugfix
2393 - Rust crates are now automatically detected and tested. Previously,
2394 some crates were not tested by `make test-rust` due to a static
2395 string in the `src/test/test_rust.sh` script specifying which
2396 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
2398 o Minor bugfixes (testing, benchmarks):
2399 - Fix a crash when running benchmark tests on win32 systems. The
2400 crash was due to a mutex that wasn't initialized before logging
2401 and options were initialized. Fixes bug 25479; bugfix
2404 o Minor bugfixes (warnings, ipv6):
2405 - Avoid a bug warning that could occur when trying to connect to a
2406 relay over IPv6. This warning would occur on a Tor instance that
2407 downloads router descriptors, but prefers to use microdescriptors.
2408 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
2410 o Code simplification and refactoring:
2411 - Remove the old (deterministic) directory retry logic entirely:
2412 We've used exponential backoff exclusively for some time. Closes
2416 - Improved the documentation of AccountingStart parameter. Closes
2418 - Update the documentation for "Log" to include the current list of
2419 logging domains. Closes ticket 25378.
2422 Changes in version 0.3.1.10 - 2018-03-03
2423 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
2426 It includes an important security fix for a remote crash attack
2427 against directory authorities, tracked as TROVE-2018-001.
2429 This release also backports our new system for improved resistance to
2430 denial-of-service attacks against relays.
2432 This release also fixes several minor bugs and annoyances from
2435 All directory authorities should upgrade to one of the versions
2436 released today. Relays running 0.3.1.x may wish to update to one of
2437 the versions released today, for the DoS mitigations.
2439 Please note: according to our release calendar, Tor 0.3.1 will no
2440 longer be supported after 1 July 2018. If you will be running Tor
2441 after that date, you should make sure to plan to upgrade to the latest
2442 stable version, or downgrade to 0.2.9 (which will receive long-term
2445 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
2446 - Fix a protocol-list handling bug that could be used to remotely crash
2447 directory authorities with a null-pointer exception. Fixes bug 25074;
2448 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
2451 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
2452 - Give relays some defenses against the recent network overload. We
2453 start with three defenses (default parameters in parentheses).
2454 First: if a single client address makes too many concurrent
2455 connections (>100), hang up on further connections. Second: if a
2456 single client address makes circuits too quickly (more than 3 per
2457 second, with an allowed burst of 90) while also having too many
2458 connections open (3), refuse new create cells for the next while
2459 (1-2 hours). Third: if a client asks to establish a rendezvous
2460 point to you directly, ignore the request. These defenses can be
2461 manually controlled by new torrc options, but relays will also
2462 take guidance from consensus parameters, so there's no need to
2463 configure anything manually. Implements ticket 24902.
2465 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
2466 - Update the sandbox rules so that they should now work correctly
2467 with Glibc 2.26. Closes ticket 24315.
2469 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
2470 - Fix an "off by 2" error in counting rendezvous failures on the
2471 onion service side. While we thought we would stop the rendezvous
2472 attempt after one failed circuit, we were actually making three
2473 circuit attempts before giving up. Now switch to a default of 2,
2474 and allow the consensus parameter "hs_service_max_rdv_failures" to
2475 override. Fixes bug 24895; bugfix on 0.0.6.
2477 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
2478 - Add Link protocol version 5 to the supported protocols list. Fixes
2479 bug 25070; bugfix on 0.3.1.1-alpha.
2481 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
2482 - Fix a set of false positives where relays would consider
2483 connections to other relays as being client-only connections (and
2484 thus e.g. deserving different link padding schemes) if those
2485 relays fell out of the consensus briefly. Now we look only at the
2486 initial handshake and whether the connection authenticated as a
2487 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
2489 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
2490 - Make our OOM handler aware of the geoip client history cache so it
2491 doesn't fill up the memory. This check is important for IPv6 and
2492 our DoS mitigation subsystem. Closes ticket 25122.
2494 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
2495 - Change relay bandwidth reporting stats interval from 4 hours to 24
2496 hours in order to reduce the efficiency of guard discovery
2497 attacks. Fixes ticket 23856.
2499 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
2500 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
2501 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
2502 since they neither disabled TLS 1.3 nor enabled any of the
2503 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
2504 Closes ticket 24978.
2506 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
2507 - The fallback directory list has been re-generated based on the
2508 current status of the network. Tor uses fallback directories to
2509 bootstrap when it doesn't yet have up-to-date directory
2510 information. Closes ticket 24801.
2511 - Make the default DirAuthorityFallbackRate 0.1, so that clients
2512 prefer to bootstrap from fallback directory mirrors. This is a
2513 follow-up to 24679, which removed weights from the default
2514 fallbacks. Implements ticket 24681.
2516 o Minor features (geoip):
2517 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
2520 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
2521 - Use the actual observed address of an incoming relay connection,
2522 not the canonical address of the relay from its descriptor, when
2523 making decisions about how to handle the incoming connection.
2524 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
2526 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
2527 - Directory authorities, when refusing a descriptor from a rejected
2528 relay, now explicitly tell the relay (in its logs) to set a valid
2529 ContactInfo address and contact the bad-relays@ mailing list.
2530 Fixes bug 25170; bugfix on 0.2.9.1.
2532 o Minor bugfixes (address selection, backport from 0.3.2.9):
2533 - When the fascist_firewall_choose_address_ functions don't find a
2534 reachable address, set the returned address to the null address
2535 and port. This is a precautionary measure, because some callers do
2536 not check the return value. Fixes bug 24736; bugfix
2539 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
2540 - Fetch descriptors aggressively whenever we lack enough to build
2541 circuits, regardless of how many descriptors we are missing.
2542 Previously, we would delay launching the fetch when we had fewer
2543 than 15 missing descriptors, even if some of those descriptors
2544 were blocking circuits from building. Fixes bug 23985; bugfix on
2545 0.1.1.11-alpha. The effects of this bug became worse in
2546 0.3.0.3-alpha, when we began treating missing descriptors from our
2547 primary guards as a reason to delay circuits.
2548 - Don't try fetching microdescriptors from relays that have failed
2549 to deliver them in the past. Fixes bug 23817; bugfix
2552 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
2553 - Fix a signed/unsigned comparison warning introduced by our fix to
2554 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
2556 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
2557 - Avoid a crash when attempting to use the seccomp2 sandbox together
2558 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
2561 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
2562 - Fix a possible crash on malformed consensus. If a consensus had
2563 contained an unparseable protocol line, it could have made clients
2564 and relays crash with a null-pointer exception. To exploit this
2565 issue, however, an attacker would need to be able to subvert the
2566 directory authority system. Fixes bug 25251; bugfix on
2567 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
2569 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
2570 - Recover better from empty or corrupt files in the consensus cache
2571 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
2572 - When a consensus diff calculation is only partially successful,
2573 only record the successful parts as having succeeded. Partial
2574 success can happen if (for example) one compression method fails
2575 but the others succeed. Previously we misrecorded all the
2576 calculations as having succeeded, which would later cause a
2577 nonfatal assertion failure. Fixes bug 24086; bugfix
2580 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
2581 - Tor now updates its guard state when it reads a consensus
2582 regardless of whether it's missing descriptors. That makes tor use
2583 its primary guards to fetch descriptors in some edge cases where
2584 it would previously have used fallback directories. Fixes bug
2585 23862; bugfix on 0.3.0.1-alpha.
2587 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
2588 - Don't treat inability to store a cached consensus object as a bug:
2589 it can happen normally when we are out of disk space. Fixes bug
2590 24859; bugfix on 0.3.1.1-alpha.
2592 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
2593 - When queuing DESTROY cells on a channel, only queue the circuit-id
2594 and reason fields: not the entire 514-byte cell. This fix should
2595 help mitigate any bugs or attacks that fill up these queues, and
2596 free more RAM for other uses. Fixes bug 24666; bugfix
2599 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
2600 - When closing a connection via close_connection_immediately(), we
2601 mark it as "not blocked on bandwidth", to prevent later calls from
2602 trying to unblock it, and give it permission to read. This fixes a
2603 backtrace warning that can happen on relays under various
2604 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
2606 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
2607 - When selecting relays by bandwidth, avoid a rounding error that
2608 could sometimes cause load to be imbalanced incorrectly.
2609 Previously, we would always round upwards; now, we round towards
2610 the nearest integer. This had the biggest effect when a relay's
2611 weight adjustments should have given it weight 0, but it got
2612 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
2613 - When calculating the fraction of nodes that have descriptors, and
2614 all nodes in the network have zero bandwidths, count the number of
2615 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
2616 - Actually log the total bandwidth in compute_weighted_bandwidths().
2617 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
2619 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
2620 - Improve the performance of our consensus-diff application code
2621 when Tor is built with the --enable-fragile-hardening option set.
2622 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
2624 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
2625 - Don't exit the Tor process if setrlimit() fails to change the file
2626 limit (which can happen sometimes on some versions of OSX). Fixes
2627 bug 21074; bugfix on 0.0.9pre5.
2629 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
2630 - Fix a bug in the bit-counting parts of our timing-wheel code on
2631 MSVC. (Note that MSVC is still not a supported build platform, due
2632 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
2635 o Minor bugfixes (relay, partial backport):
2636 - Make the internal channel_is_client() function look at what sort
2637 of connection handshake the other side used, rather than whether
2638 the other side ever sent a create_fast cell to us. Backports part
2639 of the fixes from bugs 22805 and 24898.
2641 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
2642 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
2644 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
2645 bugfix on 0.2.9.4-alpha.
2647 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
2648 - Update the "rust dependencies" submodule to be a project-level
2649 repository, rather than a user repository. Closes ticket 25323.
2652 Changes in version 0.2.9.15 - 2018-03-03
2653 Tor 0.2.9.15 backports important security and stability bugfixes from
2656 It includes an important security fix for a remote crash attack
2657 against directory authorities, tracked as TROVE-2018-001.
2659 This release also backports our new system for improved resistance to
2660 denial-of-service attacks against relays.
2662 This release also fixes several minor bugs and annoyances from
2665 All directory authorities should upgrade to one of the versions
2666 released today. Relays running 0.2.9.x may wish to update to one of
2667 the versions released today, for the DoS mitigations.
2669 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
2670 - Fix a protocol-list handling bug that could be used to remotely crash
2671 directory authorities with a null-pointer exception. Fixes bug 25074;
2672 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
2675 o Major features (denial-of-service mitigation):
2676 - Give relays some defenses against the recent network overload. We
2677 start with three defenses (default parameters in parentheses).
2678 First: if a single client address makes too many concurrent
2679 connections (>100), hang up on further connections. Second: if a
2680 single client address makes circuits too quickly (more than 3 per
2681 second, with an allowed burst of 90) while also having too many
2682 connections open (3), refuse new create cells for the next while
2683 (1-2 hours). Third: if a client asks to establish a rendezvous
2684 point to you directly, ignore the request. These defenses can be
2685 manually controlled by new torrc options, but relays will also
2686 take guidance from consensus parameters, so there's no need to
2687 configure anything manually. Implements ticket 24902.
2689 o Major bugfixes (bootstrapping):
2690 - Fetch descriptors aggressively whenever we lack enough to build
2691 circuits, regardless of how many descriptors we are missing.
2692 Previously, we would delay launching the fetch when we had fewer
2693 than 15 missing descriptors, even if some of those descriptors
2694 were blocking circuits from building. Fixes bug 23985; bugfix on
2695 0.1.1.11-alpha. The effects of this bug became worse in
2696 0.3.0.3-alpha, when we began treating missing descriptors from our
2697 primary guards as a reason to delay circuits.
2699 o Major bugfixes (onion services, retry behavior):
2700 - Fix an "off by 2" error in counting rendezvous failures on the
2701 onion service side. While we thought we would stop the rendezvous
2702 attempt after one failed circuit, we were actually making three
2703 circuit attempts before giving up. Now switch to a default of 2,
2704 and allow the consensus parameter "hs_service_max_rdv_failures" to
2705 override. Fixes bug 24895; bugfix on 0.0.6.
2707 o Minor feature (relay statistics):
2708 - Change relay bandwidth reporting stats interval from 4 hours to 24
2709 hours in order to reduce the efficiency of guard discovery
2710 attacks. Fixes ticket 23856.
2712 o Minor features (compatibility, OpenSSL):
2713 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
2714 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
2715 since they neither disabled TLS 1.3 nor enabled any of the
2716 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
2717 Closes ticket 24978.
2719 o Minor features (denial-of-service avoidance):
2720 - Make our OOM handler aware of the geoip client history cache so it
2721 doesn't fill up the memory. This check is important for IPv6 and
2722 our DoS mitigation subsystem. Closes ticket 25122.
2724 o Minor features (fallback directory mirrors):
2725 - The fallback directory list has been re-generated based on the
2726 current status of the network. Tor uses fallback directories to
2727 bootstrap when it doesn't yet have up-to-date directory
2728 information. Closes ticket 24801.
2729 - Make the default DirAuthorityFallbackRate 0.1, so that clients
2730 prefer to bootstrap from fallback directory mirrors. This is a
2731 follow-up to 24679, which removed weights from the default
2732 fallbacks. Implements ticket 24681.
2734 o Minor features (geoip):
2735 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
2738 o Minor features (linux seccomp2 sandbox):
2739 - Update the sandbox rules so that they should now work correctly
2740 with Glibc 2.26. Closes ticket 24315.
2742 o Minor bugfix (channel connection):
2743 - Use the actual observed address of an incoming relay connection,
2744 not the canonical address of the relay from its descriptor, when
2745 making decisions about how to handle the incoming connection.
2746 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
2748 o Minor bugfix (directory authority):
2749 - Directory authorities, when refusing a descriptor from a rejected
2750 relay, now explicitly tell the relay (in its logs) to set a valid
2751 ContactInfo address and contact the bad-relays@ mailing list.
2752 Fixes bug 25170; bugfix on 0.2.9.1.
2754 o Minor bugfixes (address selection):
2755 - When the fascist_firewall_choose_address_ functions don't find a
2756 reachable address, set the returned address to the null address
2757 and port. This is a precautionary measure, because some callers do
2758 not check the return value. Fixes bug 24736; bugfix
2761 o Minor bugfixes (compilation):
2762 - Fix a signed/unsigned comparison warning introduced by our fix to
2763 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
2765 o Minor bugfixes (control port, linux seccomp2 sandbox):
2766 - Avoid a crash when attempting to use the seccomp2 sandbox together
2767 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
2770 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
2771 - Fix a possible crash on malformed consensus. If a consensus had
2772 contained an unparseable protocol line, it could have made clients
2773 and relays crash with a null-pointer exception. To exploit this
2774 issue, however, an attacker would need to be able to subvert the
2775 directory authority system. Fixes bug 25251; bugfix on
2776 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
2778 o Minor bugfixes (memory usage):
2779 - When queuing DESTROY cells on a channel, only queue the circuit-id
2780 and reason fields: not the entire 514-byte cell. This fix should
2781 help mitigate any bugs or attacks that fill up these queues, and
2782 free more RAM for other uses. Fixes bug 24666; bugfix
2785 o Minor bugfixes (network layer):
2786 - When closing a connection via close_connection_immediately(), we
2787 mark it as "not blocked on bandwidth", to prevent later calls from
2788 trying to unblock it, and give it permission to read. This fixes a
2789 backtrace warning that can happen on relays under various
2790 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
2792 o Minor bugfixes (OSX):
2793 - Don't exit the Tor process if setrlimit() fails to change the file
2794 limit (which can happen sometimes on some versions of OSX). Fixes
2795 bug 21074; bugfix on 0.0.9pre5.
2797 o Minor bugfixes (path selection):
2798 - When selecting relays by bandwidth, avoid a rounding error that
2799 could sometimes cause load to be imbalanced incorrectly.
2800 Previously, we would always round upwards; now, we round towards
2801 the nearest integer. This had the biggest effect when a relay's
2802 weight adjustments should have given it weight 0, but it got
2803 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
2804 - When calculating the fraction of nodes that have descriptors, and
2805 all nodes in the network have zero bandwidths, count the number of
2806 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
2807 - Actually log the total bandwidth in compute_weighted_bandwidths().
2808 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
2810 o Minor bugfixes (portability, msvc):
2811 - Fix a bug in the bit-counting parts of our timing-wheel code on
2812 MSVC. (Note that MSVC is still not a supported build platform, due
2813 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
2816 o Minor bugfixes (relay):
2817 - Make the internal channel_is_client() function look at what sort
2818 of connection handshake the other side used, rather than whether
2819 the other side ever sent a create_fast cell to us. Backports part
2820 of the fixes from bugs 22805 and 24898.
2822 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
2823 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
2825 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
2826 bugfix on 0.2.9.4-alpha.
2829 Changes in version 0.3.2.10 - 2018-03-03
2830 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
2831 backports a number of bugfixes, including important fixes for security
2834 It includes an important security fix for a remote crash attack
2835 against directory authorities, tracked as TROVE-2018-001.
2837 Additionally, it backports a fix for a bug whose severity we have
2838 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
2839 triggered in order to crash relays with a use-after-free pattern. As
2840 such, we are now tracking that bug as TROVE-2018-002 and
2841 CVE-2018-0491, and backporting it to earlier releases. This bug
2842 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
2845 This release also backports our new system for improved resistance to
2846 denial-of-service attacks against relays.
2848 This release also fixes several minor bugs and annoyances from
2851 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
2852 today, for the fix to TROVE-2018-002. Directory authorities should
2853 also upgrade. (Relays on earlier versions might want to update too for
2854 the DoS mitigations.)
2856 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
2857 - Fix a protocol-list handling bug that could be used to remotely crash
2858 directory authorities with a null-pointer exception. Fixes bug 25074;
2859 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
2862 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
2863 - Avoid adding the same channel twice in the KIST scheduler pending
2864 list, which could lead to remote denial-of-service use-after-free
2865 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
2867 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
2868 - Give relays some defenses against the recent network overload. We
2869 start with three defenses (default parameters in parentheses).
2870 First: if a single client address makes too many concurrent
2871 connections (>100), hang up on further connections. Second: if a
2872 single client address makes circuits too quickly (more than 3 per
2873 second, with an allowed burst of 90) while also having too many
2874 connections open (3), refuse new create cells for the next while
2875 (1-2 hours). Third: if a client asks to establish a rendezvous
2876 point to you directly, ignore the request. These defenses can be
2877 manually controlled by new torrc options, but relays will also
2878 take guidance from consensus parameters, so there's no need to
2879 configure anything manually. Implements ticket 24902.
2881 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
2882 - Fix an "off by 2" error in counting rendezvous failures on the
2883 onion service side. While we thought we would stop the rendezvous
2884 attempt after one failed circuit, we were actually making three
2885 circuit attempts before giving up. Now switch to a default of 2,
2886 and allow the consensus parameter "hs_service_max_rdv_failures" to
2887 override. Fixes bug 24895; bugfix on 0.0.6.
2888 - New-style (v3) onion services now obey the "max rendezvous circuit
2889 attempts" logic. Previously they would make as many rendezvous
2890 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
2891 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
2893 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
2894 - Add Link protocol version 5 to the supported protocols list. Fixes
2895 bug 25070; bugfix on 0.3.1.1-alpha.
2897 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
2898 - Fix a set of false positives where relays would consider
2899 connections to other relays as being client-only connections (and
2900 thus e.g. deserving different link padding schemes) if those
2901 relays fell out of the consensus briefly. Now we look only at the
2902 initial handshake and whether the connection authenticated as a
2903 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
2905 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
2906 - The scheduler subsystem was failing to promptly notice changes in
2907 consensus parameters, making it harder to switch schedulers
2908 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
2910 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
2911 - Make our OOM handler aware of the geoip client history cache so it
2912 doesn't fill up the memory. This check is important for IPv6 and
2913 our DoS mitigation subsystem. Closes ticket 25122.
2915 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
2916 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
2917 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
2918 since they neither disabled TLS 1.3 nor enabled any of the
2919 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
2920 Closes ticket 24978.
2922 o Minor features (geoip):
2923 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
2926 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
2927 - When logging a failure to create an onion service's descriptor,
2928 also log what the problem with the descriptor was. Diagnostic
2931 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
2932 - Use the actual observed address of an incoming relay connection,
2933 not the canonical address of the relay from its descriptor, when
2934 making decisions about how to handle the incoming connection.
2935 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
2937 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
2938 - Fix a possible crash on malformed consensus. If a consensus had
2939 contained an unparseable protocol line, it could have made clients
2940 and relays crash with a null-pointer exception. To exploit this
2941 issue, however, an attacker would need to be able to subvert the
2942 directory authority system. Fixes bug 25251; bugfix on
2943 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
2945 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
2946 - Directory authorities, when refusing a descriptor from a rejected
2947 relay, now explicitly tell the relay (in its logs) to set a valid
2948 ContactInfo address and contact the bad-relays@ mailing list.
2949 Fixes bug 25170; bugfix on 0.2.9.1.
2951 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
2952 - When building with Rust on OSX, link against libresolv, to work
2953 around the issue at https://github.com/rust-lang/rust/issues/46797.
2954 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
2956 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
2957 - Remove a BUG() statement when a client fetches an onion descriptor
2958 that has a lower revision counter than the one in its cache. This
2959 can happen in normal circumstances due to HSDir desync. Fixes bug
2960 24976; bugfix on 0.3.2.1-alpha.
2962 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
2963 - Don't treat inability to store a cached consensus object as a bug:
2964 it can happen normally when we are out of disk space. Fixes bug
2965 24859; bugfix on 0.3.1.1-alpha.
2967 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
2968 - Improve the performance of our consensus-diff application code
2969 when Tor is built with the --enable-fragile-hardening option set.
2970 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
2972 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
2973 - Don't exit the Tor process if setrlimit() fails to change the file
2974 limit (which can happen sometimes on some versions of OSX). Fixes
2975 bug 21074; bugfix on 0.0.9pre5.
2977 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
2978 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
2980 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
2981 bugfix on 0.2.9.4-alpha.
2983 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
2984 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
2985 25005; bugfix on 0.3.2.7-rc.
2987 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
2988 - Look at the "HSRend" protocol version, not the "HSDir" protocol
2989 version, when deciding whether a consensus entry can support the
2990 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
2991 bugfix on 0.3.2.1-alpha.
2993 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
2994 - Update the "rust dependencies" submodule to be a project-level
2995 repository, rather than a user repository. Closes ticket 25323.
2997 o Documentation (backport from 0.3.3.1-alpha)
2998 - Document that operators who run more than one relay or bridge are
2999 expected to set MyFamily and ContactInfo correctly. Closes
3003 Changes in version 0.3.3.3-alpha - 2018-03-03
3004 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
3005 It includes an important security fix for a remote crash attack
3006 against directory authorities tracked as TROVE-2018-001.
3008 Additionally, with this release, we are upgrading the severity of a
3009 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
3010 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
3011 a use-after-free pattern. As such, we are now tracking that bug as
3012 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
3013 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
3015 This release also fixes several minor bugs and annoyances from
3018 Relays running 0.3.2.x should upgrade to one of the versions released
3019 today, for the fix to TROVE-2018-002. Directory authorities should
3020 also upgrade. (Relays on earlier versions might want to update too for
3021 the DoS mitigations.)
3023 o Major bugfixes (denial-of-service, directory authority):
3024 - Fix a protocol-list handling bug that could be used to remotely crash
3025 directory authorities with a null-pointer exception. Fixes bug 25074;
3026 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
3029 o Minor features (compatibility, OpenSSL):
3030 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
3031 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
3032 since they neither disabled TLS 1.3 nor enabled any of the
3033 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
3034 Closes ticket 24978.
3036 o Minor features (logging):
3037 - Clarify the log messages produced when getrandom() or a related
3038 entropy-generation mechanism gives an error. Closes ticket 25120.
3040 o Minor features (testing):
3041 - Add a "make test-rust" target to run the rust tests only. Closes
3044 o Minor bugfixes (denial-of-service):
3045 - Fix a possible crash on malformed consensus. If a consensus had
3046 contained an unparseable protocol line, it could have made clients
3047 and relays crash with a null-pointer exception. To exploit this
3048 issue, however, an attacker would need to be able to subvert the
3049 directory authority system. Fixes bug 25251; bugfix on
3050 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
3052 o Minor bugfixes (DoS mitigation):
3053 - Add extra safety checks when refilling the circuit creation bucket
3054 to ensure we never set a value above the allowed maximum burst.
3055 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
3056 - When a new consensus arrives, don't update our DoS-mitigation
3057 parameters if we aren't a public relay. Fixes bug 25223; bugfix
3060 o Minor bugfixes (man page, SocksPort):
3061 - Remove dead code from the old "SocksSocket" option, and rename
3062 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
3063 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
3065 o Minor bugfixes (performance):
3066 - Reduce the number of circuits that will be opened at once during
3067 the circuit build timeout phase. This is done by increasing the
3068 idle timeout to 3 minutes, and lowering the maximum number of
3069 concurrent learning circuits to 10. Fixes bug 24769; bugfix
3072 o Minor bugfixes (spec conformance):
3073 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
3075 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
3076 bugfix on 0.2.9.4-alpha.
3078 o Minor bugfixes (spec conformance, rust):
3079 - Resolve a denial-of-service issue caused by an infinite loop in
3080 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
3081 Also tracked as TROVE-2018-003.
3083 o Code simplification and refactoring:
3084 - Update the "rust dependencies" submodule to be a project-level
3085 repository, rather than a user repository. Closes ticket 25323.
3088 Changes in version 0.3.3.2-alpha - 2018-02-10
3089 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
3090 introduces a mechanism to handle the high loads that many relay
3091 operators have been reporting recently. It also fixes several bugs in
3092 older releases. If this new code proves reliable, we plan to backport
3093 it to older supported release series.
3095 o Major features (denial-of-service mitigation):
3096 - Give relays some defenses against the recent network overload. We
3097 start with three defenses (default parameters in parentheses).
3098 First: if a single client address makes too many concurrent
3099 connections (>100), hang up on further connections. Second: if a
3100 single client address makes circuits too quickly (more than 3 per
3101 second, with an allowed burst of 90) while also having too many
3102 connections open (3), refuse new create cells for the next while
3103 (1-2 hours). Third: if a client asks to establish a rendezvous
3104 point to you directly, ignore the request. These defenses can be
3105 manually controlled by new torrc options, but relays will also
3106 take guidance from consensus parameters, so there's no need to
3107 configure anything manually. Implements ticket 24902.
3109 o Major bugfixes (netflow padding):
3110 - Stop adding unneeded channel padding right after we finish
3111 flushing to a connection that has been trying to flush for many
3112 seconds. Instead, treat all partial or complete flushes as
3113 activity on the channel, which will defer the time until we need
3114 to add padding. This fix should resolve confusing and scary log
3115 messages like "Channel padding timeout scheduled 221453ms in the
3116 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
3118 o Major bugfixes (protocol versions):
3119 - Add Link protocol version 5 to the supported protocols list. Fixes
3120 bug 25070; bugfix on 0.3.1.1-alpha.
3122 o Major bugfixes (scheduler, consensus):
3123 - The scheduler subsystem was failing to promptly notice changes in
3124 consensus parameters, making it harder to switch schedulers
3125 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
3127 o Minor features (denial-of-service avoidance):
3128 - Make our OOM handler aware of the geoip client history cache so it
3129 doesn't fill up the memory. This check is important for IPv6 and
3130 our DoS mitigation subsystem. Closes ticket 25122.
3132 o Minor features (directory authority):
3133 - When directory authorities are unable to add signatures to a
3134 pending consensus, log the reason why. Closes ticket 24849.
3136 o Minor features (geoip):
3137 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
3140 o Minor features (logging, diagnostic):
3141 - When logging a failure to create an onion service's descriptor,
3142 also log what the problem with the descriptor was. Diagnostic for
3145 o Minor bugfix (channel connection):
3146 - Use the actual observed address of an incoming relay connection,
3147 not the canonical address of the relay from its descriptor, when
3148 making decisions about how to handle the incoming connection.
3149 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
3151 o Minor bugfix (directory authority):
3152 - Directory authorities, when refusing a descriptor from a rejected
3153 relay, now explicitly tell the relay (in its logs) to set a valid
3154 ContactInfo address and contact the bad-relays@ mailing list.
3155 Fixes bug 25170; bugfix on 0.2.9.1.
3157 o Minor bugfixes (all versions of Tor):
3158 - Use the "misspell" tool to detect and fix typos throughout the
3159 source code. Fixes bug 23650; bugfix on various versions of Tor.
3160 Patch from Deepesh Pathak.
3162 o Minor bugfixes (circuit, cannibalization):
3163 - Don't cannibalize preemptively-built circuits if we no longer
3164 recognize their first hop. This situation can happen if our Guard
3165 relay went off the consensus after the circuit was created. Fixes
3166 bug 24469; bugfix on 0.0.6.
3168 o Minor bugfixes (correctness):
3169 - Remove a nonworking, unnecessary check to see whether a circuit
3170 hop's identity digest was set when the circuit failed. Fixes bug
3171 24927; bugfix on 0.2.4.4-alpha.
3173 o Minor bugfixes (logging):
3174 - Don't treat inability to store a cached consensus object as a bug:
3175 it can happen normally when we are out of disk space. Fixes bug
3176 24859; bugfix on 0.3.1.1-alpha.
3177 - Fix a (mostly harmless) race condition when invoking
3178 LOG_PROTOCOL_WARN message from a subthread while the torrc options
3179 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
3181 o Minor bugfixes (onion services):
3182 - Remove a BUG() statement when a client fetches an onion descriptor
3183 that has a lower revision counter than the one in its cache. This
3184 can happen in normal circumstances due to HSDir desync. Fixes bug
3185 24976; bugfix on 0.3.2.1-alpha.
3186 - If we are configured to offer a single onion service, don't log
3187 long-term established one hop rendezvous points in the heartbeat.
3188 Fixes bug 25116; bugfix on 0.2.9.6-rc.
3190 o Minor bugfixes (performance):
3191 - Avoid calling protocol_list_supports_protocol() from inside tight
3192 loops when running with cached routerinfo_t objects. Instead,
3193 summarize the relevant protocols as flags in the routerinfo_t, as
3194 we do for routerstatus_t objects. This change simplifies our code
3195 a little, and saves a large amount of short-term memory allocation
3196 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
3198 o Minor bugfixes (Rust FFI):
3199 - Fix a minor memory leak which would happen whenever the C code
3200 would call the Rust implementation of
3201 protover_get_supported_protocols(). This was due to the C version
3202 returning a static string, whereas the Rust version newly allocated
3203 a CString to pass across the FFI boundary. Consequently, the C
3204 code was not expecting to need to free() what it was given. Fixes
3205 bug 25127; bugfix on 0.3.2.1-alpha.
3207 o Minor bugfixes (scheduler, KIST):
3208 - Avoid adding the same channel twice in the KIST scheduler pending
3209 list, which would waste CPU cycles. Fixes bug 24700; bugfix
3212 o Minor bugfixes (unit test, monotonic time):
3213 - Increase a constant (1msec to 10msec) in the monotonic time test
3214 that makes sure the nsec/usec/msec times read are synchronized.
3215 This change was needed to accommodate slow systems like armel or
3216 when the clock_gettime() is not a VDSO on the running kernel.
3217 Fixes bug 25113; bugfix on 0.2.9.1.
3219 o Minor bugfixes (v3 onion services):
3220 - Look at the "HSRend" protocol version, not the "HSDir" protocol
3221 version, when deciding whether a consensus entry can support the
3222 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
3223 bugfix on 0.3.2.1-alpha.
3225 o Code simplification and refactoring:
3226 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
3228 - Remove a series of counters used to track circuit extend attempts
3229 and connection status but that in reality we aren't using for
3230 anything other than stats logged by a SIGUSR1 signal. Closes
3233 o Documentation (man page):
3234 - The HiddenServiceVersion torrc option accepts only one number:
3235 either version 2 or 3. Closes ticket 25026; bugfix
3239 Changes in version 0.3.3.1-alpha - 2018-01-25
3240 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
3241 several new features to Tor, including several improvements to
3242 bootstrapping, and support for an experimental "vanguards" feature to
3243 resist guard discovery attacks. This series also includes better
3244 support for applications that need to embed Tor or manage v3
3247 o Major features (embedding):
3248 - There is now a documented stable API for programs that need to
3249 embed Tor. See tor_api.h for full documentation and known bugs.
3250 Closes ticket 23684.
3251 - Tor now has support for restarting in the same process.
3252 Controllers that run Tor using the "tor_api.h" interface can now
3253 restart Tor after Tor has exited. This support is incomplete,
3254 however: we fixed crash bugs that prevented it from working at
3255 all, but many bugs probably remain, including a possibility of
3256 security issues. Implements ticket 24581.
3258 o Major features (IPv6, directory documents):
3259 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
3260 consensus. This information makes it easier for IPv6 clients to
3261 bootstrap and choose reachable entry guards. Implements ticket 23826.
3262 - Add consensus method 28, which removes IPv6 ORPorts from
3263 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
3264 are redundant in microdescs. This change will be used by Tor clients
3265 on 0.2.8.x and later. (That is to say, with all Tor clients that
3266 have IPv6 bootstrap and guard support.) Implements ticket 23828.
3267 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
3268 set by different numbers of authorities. Fixes 23870
3271 o Major features (onion service v3, control port):
3272 - The control port now supports commands and events for v3 onion
3273 services. It is now possible to create ephemeral v3 services using
3274 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
3275 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
3276 DEL_ONION) have been extended to support v3 onion services. Closes
3277 ticket 20699; implements proposal 284.
3279 o Major features (onion services):
3280 - Provide torrc options to pin the second and third hops of onion
3281 service circuits to a list of nodes. The option HSLayer2Guards
3282 pins the second hop, and the option HSLayer3Guards pins the third
3283 hop. These options are for use in conjunction with experiments
3284 with "vanguards" for preventing guard enumeration attacks. Closes
3287 o Major features (rust, portability, experimental):
3288 - Tor now ships with an optional implementation of one of its
3289 smaller modules (protover.c) in the Rust programming language. To
3290 try it out, install a Rust build environment, and configure Tor
3291 with "--enable-rust --enable-cargo-online-mode". This should not
3292 cause any user-visible changes, but should help us gain more
3293 experience with Rust, and plan future Rust integration work.
3294 Implementation by Chelsea Komlo. Closes ticket 22840.
3296 o Minor features (storage, configuration):
3297 - Users can store cached directory documents somewhere other than
3298 the DataDirectory by using the CacheDirectory option. Similarly,
3299 the storage location for relay's keys can be overridden with the
3300 KeyDirectory option. Closes ticket 22703.
3302 o Major features (v3 onion services, ipv6):
3303 - When v3 onion service clients send introduce cells, they now
3304 include the IPv6 address of the rendezvous point, if it has one.
3305 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
3306 in future Tor versions, IPv6-only v3 single onion services will be
3307 able to use IPv6 addresses to connect directly to the rendezvous
3308 point. Closes ticket 23577. Patch by Neel Chauhan.
3310 o Major bugfixes (onion services, retry behavior):
3311 - Fix an "off by 2" error in counting rendezvous failures on the
3312 onion service side. While we thought we would stop the rendezvous
3313 attempt after one failed circuit, we were actually making three
3314 circuit attempts before giving up. Now switch to a default of 2,
3315 and allow the consensus parameter "hs_service_max_rdv_failures" to
3316 override. Fixes bug 24895; bugfix on 0.0.6.
3317 - New-style (v3) onion services now obey the "max rendezvous circuit
3318 attempts" logic. Previously they would make as many rendezvous
3319 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
3320 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
3322 o Major bugfixes (relays):
3323 - Fix a set of false positives where relays would consider
3324 connections to other relays as being client-only connections (and
3325 thus e.g. deserving different link padding schemes) if those
3326 relays fell out of the consensus briefly. Now we look only at the
3327 initial handshake and whether the connection authenticated as a
3328 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
3330 o Minor feature (IPv6):
3331 - Make IPv6-only clients wait for microdescs for relays, even if we
3332 were previously using descriptors (or were using them as a bridge)
3333 and have a cached descriptor for them. Implements ticket 23827.
3334 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
3335 them, rather than waiting to download microdescriptors.
3336 Implements ticket 23827.
3338 o Minor features (cleanup):
3339 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
3340 when it stops. Closes ticket 23271.
3342 o Minor features (defensive programming):
3343 - Most of the functions in Tor that free objects have been replaced
3344 with macros that free the objects and set the corresponding
3345 pointers to NULL. This change should help prevent a large class of
3346 dangling pointer bugs. Closes ticket 24337.
3347 - Where possible, the tor_free() macro now only evaluates its input
3348 once. Part of ticket 24337.
3349 - Check that microdesc ed25519 ids are non-zero in
3350 node_get_ed25519_id() before returning them. Implements ticket
3351 24001, patch by "aruna1234".
3353 o Minor features (embedding):
3354 - Tor can now start with a preauthenticated control connection
3355 created by the process that launched it. This feature is meant for
3356 use by programs that want to launch and manage a Tor process
3357 without allowing other programs to manage it as well. For more
3358 information, see the __OwningControllerFD option documented in
3359 control-spec.txt. Closes ticket 23900.
3360 - On most errors that would cause Tor to exit, it now tries to
3361 return from the tor_main() function, rather than calling the
3362 system exit() function. Most users won't notice a difference here,
3363 but it should be significant for programs that run Tor inside
3364 a separate thread: they should now be able to survive Tor's exit
3365 conditions rather than having Tor shut down the entire process.
3366 Closes ticket 23848.
3367 - Applications that want to embed Tor can now tell Tor not to
3368 register any of its own POSIX signal handlers, using the
3369 __DisableSignalHandlers option. Closes ticket 24588.
3371 o Minor features (fallback directory list):
3372 - Avoid selecting fallbacks that change their IP addresses too
3373 often. Select more fallbacks by ignoring the Guard flag, and
3374 allowing lower cutoffs for the Running and V2Dir flags. Also allow
3375 a lower bandwidth, and a higher number of fallbacks per operator
3376 (5% of the list). Implements ticket 24785.
3377 - Update the fallback whitelist and blacklist based on opt-ins and
3378 relay changes. Closes tickets 22321, 24678, 22527, 24135,
3381 o Minor features (fallback directory mirror configuration):
3382 - Add a nickname to each fallback in a C comment. This makes it
3383 easier for operators to find their relays, and allows stem to use
3384 nicknames to identify fallbacks. Implements ticket 24600.
3385 - Add a type and version header to the fallback directory mirror
3386 file. Also add a delimiter to the end of each fallback entry. This
3387 helps external parsers like stem and Relay Search. Implements
3389 - Add an extrainfo cache flag for each fallback in a C comment. This
3390 allows stem to use fallbacks to fetch extra-info documents, rather
3391 than using authorities. Implements ticket 22759.
3392 - Add the generateFallbackDirLine.py script for automatically
3393 generating fallback directory mirror lines from relay fingerprints.
3394 No more typos! Add the lookupFallbackDirContact.py script for
3395 automatically looking up operator contact info from relay
3396 fingerprints. Implements ticket 24706, patch by teor and atagar.
3397 - Reject any fallback directory mirror that serves an expired
3398 consensus. Implements ticket 20942, patch by "minik".
3399 - Remove commas and equals signs from external string inputs to the
3400 fallback list. This avoids format confusion attacks. Implements
3402 - Remove the "weight=10" line from fallback directory mirror
3403 entries. Ticket 24681 will maintain the current fallback weights
3404 by changing Tor's default fallback weight to 10. Implements
3406 - Stop logging excessive information about fallback netblocks.
3407 Implements ticket 24791.
3409 o Minor features (forward-compatibility):
3410 - If a relay supports some link authentication protocol that we do
3411 not recognize, then include that relay's ed25519 key when telling
3412 other relays to extend to it. Previously, we treated future
3413 versions as if they were too old to support ed25519 link
3414 authentication. Closes ticket 20895.
3416 o Minor features (heartbeat):
3417 - Add onion service information to our heartbeat logs, displaying
3418 stats about the activity of configured onion services. Closes
3421 o Minor features (instrumentation, development):
3422 - Add the MainloopStats option to allow developers to get
3423 instrumentation information from the main event loop via the
3424 heartbeat messages. We hope to use this to improve Tor's behavior
3425 when it's trying to sleep. Closes ticket 24605.
3427 o Minor features (log messages):
3428 - Improve a warning message that happens when we fail to re-parse an
3429 old router because of an expired certificate. Closes ticket 20020.
3430 - Make the log more quantitative when we hit MaxMemInQueues
3431 threshold exposing some values. Closes ticket 24501.
3433 o Minor features (logging, android):
3434 - Added support for the Android logging subsystem. Closes
3437 o Minor features (performance):
3438 - Support predictive circuit building for onion service circuits
3439 with multiple layers of guards. Closes ticket 23101.
3440 - Use stdatomic.h where available, rather than mutexes, to implement
3441 atomic_counter_t. Closes ticket 23953.
3443 o Minor features (performance, 32-bit):
3444 - Improve performance on 32-bit systems by avoiding 64-bit division
3445 when calculating the timestamp in milliseconds for channel padding
3446 computations. Implements ticket 24613.
3447 - Improve performance on 32-bit systems by avoiding 64-bit division
3448 when timestamping cells and buffer chunks for OOM calculations.
3449 Implements ticket 24374.
3451 o Minor features (performance, OSX, iOS):
3452 - Use the mach_approximate_time() function (when available) to
3453 implement coarse monotonic time. Having a coarse time function
3454 should avoid a large number of system calls, and improve
3455 performance slightly, especially under load. Closes ticket 24427.
3457 o Minor features (performance, windows):
3458 - Improve performance on Windows Vista and Windows 7 by adjusting
3459 TCP send window size according to the recommendation from
3460 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
3463 o Major features (relay):
3464 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
3465 operator to use a more reasonable ("reduced") exit policy, rather
3466 than the default one. If you want to run an exit node without
3467 thinking too hard about which ports to allow, this one is for you.
3468 Closes ticket 13605. Patch from Neel Chauhan.
3470 o Minor features (testing, debugging, embedding):
3471 - For development purposes, Tor now has a mode in which it runs for
3472 a few seconds, then stops, and starts again without exiting the
3473 process. This mode is meant to help us debug various issues with
3474 ticket 23847. To use this feature, compile with
3475 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
3476 environment variable. This is expected to crash a lot, and is
3477 really meant for developers only. It will likely be removed in a
3478 future release. Implements ticket 24583.
3480 o Minor bugfix (network IPv6 test):
3481 - Tor's test scripts now check if "ping -6 ::1" works when the user
3482 runs "make test-network-all". Fixes bug 24677; bugfix on
3483 0.2.9.3-alpha. Patch by "ffmancera".
3485 o Minor bugfixes (build, rust):
3486 - Fix output of autoconf checks to display success messages for Rust
3487 dependencies and a suitable rustc compiler version. Fixes bug
3488 24612; bugfix on 0.3.1.3-alpha.
3489 - When building with Rust on OSX, link against libresolv, to work
3490 around the issue at https://github.com/rust-lang/rust/issues/46797.
3491 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
3492 - Don't pass the --quiet option to cargo: it seems to suppress some
3493 errors, which is not what we want to do when building. Fixes bug
3494 24518; bugfix on 0.3.1.7.
3495 - Build correctly when building from outside Tor's source tree with
3496 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
3499 o Minor bugfixes (directory authorities, IPv6):
3500 - When creating a routerstatus (vote) from a routerinfo (descriptor),
3501 set the IPv6 address to the unspecified IPv6 address, and
3502 explicitly initialize the port to zero. Fixes bug 24488; bugfix
3505 o Minor bugfixes (fallback directory mirrors):
3506 - Make updateFallbackDirs.py search harder for python. (Some OSs
3507 don't put it in /usr/bin.) Fixes bug 24708; bugfix
3510 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
3511 - When hibernating, close connections normally and allow them to
3512 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
3514 - Do not attempt to launch self-reachability tests when entering
3515 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
3516 - Resolve several bugs related to descriptor fetching on bridge
3517 clients with bandwidth accounting enabled. (This combination is
3518 not recommended!) Fixes a case of bug 12062; bugfix
3520 - When hibernating, do not attempt to launch DNS checks. Fixes a
3521 case of bug 12062; bugfix on 0.1.2.2-alpha.
3522 - When hibernating, do not try to upload or download descriptors.
3523 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
3525 o Minor bugfixes (IPv6, bridges):
3526 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
3527 bugfix on 0.2.8.2-alpha.
3528 - Tor now sets IPv6 address in the routerstatus as well as in the
3529 router descriptors when updating addresses for a bridge. Closes
3530 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
3532 o Minor bugfixes (linux seccomp2 sandbox):
3533 - When running with the sandbox enabled, reload configuration files
3534 correctly even when %include was used. Previously we would crash.
3535 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
3537 o Minor bugfixes (memory leaks):
3538 - Avoid possible at-exit memory leaks related to use of Libevent's
3539 event_base_once() function. (This function tends to leak memory if
3540 the event_base is closed before the event fires.) Fixes bug 24584;
3541 bugfix on 0.2.8.1-alpha.
3542 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
3545 o Minor bugfixes (OSX):
3546 - Don't exit the Tor process if setrlimit() fails to change the file
3547 limit (which can happen sometimes on some versions of OSX). Fixes
3548 bug 21074; bugfix on 0.0.9pre5.
3550 o Minor bugfixes (performance, fragile-hardening):
3551 - Improve the performance of our consensus-diff application code
3552 when Tor is built with the --enable-fragile-hardening option set.
3553 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
3555 o Minor bugfixes (performance, timeouts):
3556 - Consider circuits for timeout as soon as they complete a hop. This
3557 is more accurate than applying the timeout in
3558 circuit_expire_building() because that function is only called
3559 once per second, which is now too slow for typical timeouts on the
3560 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
3561 - Use onion service circuits (and other circuits longer than 3 hops)
3562 to calculate a circuit build timeout. Previously, Tor only
3563 calculated its build timeout based on circuits that planned to be
3564 exactly 3 hops long. With this change, we include measurements
3565 from all circuits at the point where they complete their third
3566 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
3568 o Minor bugfixes (testing):
3569 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
3570 bugfix on 0.2.3.1-alpha.
3571 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
3572 25005; bugfix on 0.3.2.7-rc.
3574 o Code simplification and refactoring:
3575 - Remove /usr/athena from search path in configure.ac. Closes
3577 - Remove duplicate code in node_has_curve25519_onion_key() and
3578 node_get_curve25519_onion_key(), and add a check for a zero
3579 microdesc curve25519 onion key. Closes ticket 23966, patch by
3580 "aruna1234" and teor.
3581 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
3582 memory allocations with large numbers of OR connections (e.g.
3583 relays). Closes ticket 24119.
3584 - Separate the function that deletes ephemeral files when Tor
3586 - Small changes to Tor's buf_t API to make it suitable for use as a
3587 general-purpose safe string constructor. Closes ticket 22342.
3588 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
3589 avoid source code identifier confusion. Closes ticket 24467.
3590 - The tor_git_revision[] constant no longer needs to be redeclared
3591 by everything that links against the rest of Tor. Done as part of
3592 ticket 23845, to simplify our external API.
3593 - We make extend_info_from_node() use node_get_curve25519_onion_key()
3594 introduced in ticket 23577 to access the curve25519 public keys
3595 rather than accessing it directly. Closes ticket 23760. Patch by
3597 - Add a function to log channels' scheduler state changes to aid
3598 debugging efforts. Closes ticket 24531.
3601 - Add documentation on how to build tor with Rust dependencies
3602 without having to be online. Closes ticket 22907; bugfix
3604 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
3605 traffic. Closes ticket 24318.
3606 - Document that OutboundBindAddress doesn't apply to DNS requests.
3607 Closes ticket 22145. Patch from Aruna Maurya.
3608 - Document that operators who run more than one relay or bridge are
3609 expected to set MyFamily and ContactInfo correctly. Closes
3612 o Code simplification and refactoring (channels):
3613 - Remove the incoming and outgoing channel queues. These were never
3614 used, but still took up a step in our fast path.
3615 - The majority of the channel unit tests have been rewritten and the
3616 code coverage has now been raised to 83.6% for channel.c. Closes
3618 - Remove other dead code from the channel subsystem: All together,
3619 this cleanup has removed more than 1500 lines of code overall and
3620 adding very little except for unit test.
3622 o Code simplification and refactoring (circuit rendezvous):
3623 - Split the client-side rendezvous circuit lookup into two
3624 functions: one that returns only established circuits and another
3625 that returns all kinds of circuits. Closes ticket 23459.
3627 o Code simplification and refactoring (controller):
3628 - Make most of the variables in networkstatus_getinfo_by_purpose()
3629 const. Implements ticket 24489.
3632 Changes in version 0.3.2.9 - 2018-01-09
3633 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
3635 The 0.3.2 series includes our long-anticipated new onion service
3636 design, with numerous security features. (For more information, see
3637 our blog post at https://blog.torproject.org/fall-harvest.) We also
3638 have a new circuit scheduler algorithm for improved performance on
3639 relays everywhere (see https://blog.torproject.org/kist-and-tell),
3640 along with many smaller features and bugfixes.
3642 Per our stable release policy, we plan to support each stable release
3643 series for at least the next nine months, or for three months after
3644 the first stable release of the next series: whichever is longer. If
3645 you need a release with long-term support, we recommend that you stay
3646 with the 0.2.9 series.
3648 Below is a list of the changes since 0.3.2.8-rc. For a list of all
3649 changes since 0.3.1, see the ReleaseNotes file.
3651 o Minor features (fallback directory mirrors):
3652 - The fallback directory list has been re-generated based on the
3653 current status of the network. Tor uses fallback directories to
3654 bootstrap when it doesn't yet have up-to-date directory
3655 information. Closes ticket 24801.
3656 - Make the default DirAuthorityFallbackRate 0.1, so that clients
3657 prefer to bootstrap from fallback directory mirrors. This is a
3658 follow-up to 24679, which removed weights from the default
3659 fallbacks. Implements ticket 24681.
3661 o Minor features (geoip):
3662 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
3665 o Minor bugfixes (address selection):
3666 - When the fascist_firewall_choose_address_ functions don't find a
3667 reachable address, set the returned address to the null address
3668 and port. This is a precautionary measure, because some callers do
3669 not check the return value. Fixes bug 24736; bugfix
3672 o Minor bugfixes (compilation):
3673 - Resolve a few shadowed-variable warnings in the onion service
3674 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
3676 o Minor bugfixes (portability, msvc):
3677 - Fix a bug in the bit-counting parts of our timing-wheel code on
3678 MSVC. (Note that MSVC is still not a supported build platform, due
3679 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
3683 Changes in version 0.3.2.8-rc - 2017-12-21
3684 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
3685 schedulers that had led servers under heavy load to overload their
3686 outgoing connections. All relay operators running earlier 0.3.2.x
3687 versions should upgrade. This version also includes a mitigation for
3688 over-full DESTROY queues leading to out-of-memory conditions: if it
3689 works, we will soon backport it to earlier release series.
3691 This is the second release candidate in the 0.3.2 series. If we find
3692 no new bugs or regression here, then the first stable 0.3.2 release
3693 will be nearly identical to this.
3695 o Major bugfixes (KIST, scheduler):
3696 - The KIST scheduler did not correctly account for data already
3697 enqueued in each connection's send socket buffer, particularly in
3698 cases when the TCP/IP congestion window was reduced between
3699 scheduler calls. This situation lead to excessive per-connection
3700 buffering in the kernel, and a potential memory DoS. Fixes bug
3701 24665; bugfix on 0.3.2.1-alpha.
3703 o Minor features (geoip):
3704 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
3707 o Minor bugfixes (hidden service v3):
3708 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
3709 the probability of reaching a service for a client missing
3710 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
3712 o Minor bugfixes (memory usage):
3713 - When queuing DESTROY cells on a channel, only queue the circuit-id
3714 and reason fields: not the entire 514-byte cell. This fix should
3715 help mitigate any bugs or attacks that fill up these queues, and
3716 free more RAM for other uses. Fixes bug 24666; bugfix
3719 o Minor bugfixes (scheduler, KIST):
3720 - Use a sane write limit for KISTLite when writing onto a connection
3721 buffer instead of using INT_MAX and shoving as much as it can.
3722 Because the OOM handler cleans up circuit queues, we are better
3723 off at keeping them in that queue instead of the connection's
3724 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
3727 Changes in version 0.3.2.7-rc - 2017-12-14
3728 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
3729 including some that could affect reliability or correctness.
3731 This is the first release candidate in the 0.3.2 series. If we find no
3732 new bugs or regression here, then the first stable 0.3.2. release will
3733 be nearly identical to this.
3735 o Major bugfixes (circuit prediction):
3736 - Fix circuit prediction logic so that a client doesn't treat a port
3737 as being "handled" by a circuit if that circuit already has
3738 isolation settings on it. This change should make Tor clients more
3739 responsive by improving their chances of having a pre-created
3740 circuit ready for use when a request arrives. Fixes bug 18859;
3741 bugfix on 0.2.3.3-alpha.
3743 o Minor features (logging):
3744 - Provide better warnings when the getrandom() syscall fails. Closes
3747 o Minor features (portability):
3748 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
3749 (It doesn't yet work with the sandbox enabled.) Closes
3752 o Minor bugfixes (bridge clients, bootstrap):
3753 - Retry directory downloads when we get our first bridge descriptor
3754 during bootstrap or while reconnecting to the network. Keep
3755 retrying every time we get a bridge descriptor, until we have a
3756 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
3757 - Stop delaying bridge descriptor fetches when we have cached bridge
3758 descriptors. Instead, only delay bridge descriptor fetches when we
3759 have at least one reachable bridge. Fixes part of bug 24367;
3760 bugfix on 0.2.0.3-alpha.
3761 - Stop delaying directory fetches when we have cached bridge
3762 descriptors. Instead, only delay bridge descriptor fetches when
3763 all our bridges are definitely unreachable. Fixes part of bug
3764 24367; bugfix on 0.2.0.3-alpha.
3766 o Minor bugfixes (compilation):
3767 - Fix a signed/unsigned comparison warning introduced by our fix to
3768 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
3770 o Minor bugfixes (correctness):
3771 - Fix several places in our codebase where a C compiler would be
3772 likely to eliminate a check, based on assuming that undefined
3773 behavior had not happened elsewhere in the code. These cases are
3774 usually a sign of redundant checking or dubious arithmetic. Found
3775 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
3776 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
3779 o Minor bugfixes (onion service v3):
3780 - Fix a race where an onion service would launch a new intro circuit
3781 after closing an old one, but fail to register it before freeing
3782 the previously closed circuit. This bug was making the service
3783 unable to find the established intro circuit and thus not upload
3784 its descriptor, thus making a service unavailable for up to 24
3785 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
3787 o Minor bugfixes (scheduler, KIST):
3788 - Properly set the scheduler state of an unopened channel in the
3789 KIST scheduler main loop. This prevents a harmless but annoying
3790 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
3791 - Avoid a possible integer overflow when computing the available
3792 space on the TCP buffer of a channel. This had no security
3793 implications; but could make KIST allow too many cells on a
3794 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
3795 - Downgrade to "info" a harmless warning about the monotonic time
3796 moving backwards: This can happen on platform not supporting
3797 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
3800 Changes in version 0.3.2.6-alpha - 2017-12-01
3801 This version of Tor is the latest in the 0.3.2 alpha series. It
3802 includes fixes for several important security issues. All Tor users
3803 should upgrade to this release, or to one of the other releases coming
3806 o Major bugfixes (security):
3807 - Fix a denial of service bug where an attacker could use a
3808 malformed directory object to cause a Tor instance to pause while
3809 OpenSSL would try to read a passphrase from the terminal. (Tor
3810 instances run without a terminal, which is the case for most Tor
3811 packages, are not impacted.) Fixes bug 24246; bugfix on every
3812 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
3813 Found by OSS-Fuzz as testcase 6360145429790720.
3814 - Fix a denial of service issue where an attacker could crash a
3815 directory authority using a malformed router descriptor. Fixes bug
3816 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
3818 - When checking for replays in the INTRODUCE1 cell data for a
3819 (legacy) onion service, correctly detect replays in the RSA-
3820 encrypted part of the cell. We were previously checking for
3821 replays on the entire cell, but those can be circumvented due to
3822 the malleability of Tor's legacy hybrid encryption. This fix helps
3823 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
3824 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
3827 o Major bugfixes (security, onion service v2):
3828 - Fix a use-after-free error that could crash v2 Tor onion services
3829 when they failed to open circuits while expiring introduction
3830 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
3831 also tracked as TROVE-2017-013 and CVE-2017-8823.
3833 o Major bugfixes (security, relay):
3834 - When running as a relay, make sure that we never build a path
3835 through ourselves, even in the case where we have somehow lost the
3836 version of our descriptor appearing in the consensus. Fixes part
3837 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
3838 as TROVE-2017-012 and CVE-2017-8822.
3839 - When running as a relay, make sure that we never choose ourselves
3840 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
3841 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
3843 o Minor feature (relay statistics):
3844 - Change relay bandwidth reporting stats interval from 4 hours to 24
3845 hours in order to reduce the efficiency of guard discovery
3846 attacks. Fixes ticket 23856.
3848 o Minor features (directory authority):
3849 - Add an IPv6 address for the "bastet" directory authority. Closes
3852 o Minor bugfixes (client):
3853 - By default, do not enable storage of client-side DNS values. These
3854 values were unused by default previously, but they should not have
3855 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
3858 Changes in version 0.3.1.9 - 2017-12-01:
3859 Tor 0.3.1.9 backports important security and stability fixes from the
3860 0.3.2 development series. All Tor users should upgrade to this
3861 release, or to another of the releases coming out today.
3863 o Major bugfixes (security, backport from 0.3.2.6-alpha):
3864 - Fix a denial of service bug where an attacker could use a
3865 malformed directory object to cause a Tor instance to pause while
3866 OpenSSL would try to read a passphrase from the terminal. (Tor
3867 instances run without a terminal, which is the case for most Tor
3868 packages, are not impacted.) Fixes bug 24246; bugfix on every
3869 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
3870 Found by OSS-Fuzz as testcase 6360145429790720.
3871 - Fix a denial of service issue where an attacker could crash a
3872 directory authority using a malformed router descriptor. Fixes bug
3873 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
3875 - When checking for replays in the INTRODUCE1 cell data for a
3876 (legacy) onion service, correctly detect replays in the RSA-
3877 encrypted part of the cell. We were previously checking for
3878 replays on the entire cell, but those can be circumvented due to
3879 the malleability of Tor's legacy hybrid encryption. This fix helps
3880 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
3881 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
3884 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
3885 - Fix a use-after-free error that could crash v2 Tor onion services
3886 when they failed to open circuits while expiring introduction
3887 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
3888 also tracked as TROVE-2017-013 and CVE-2017-8823.
3890 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
3891 - When running as a relay, make sure that we never build a path
3892 through ourselves, even in the case where we have somehow lost the
3893 version of our descriptor appearing in the consensus. Fixes part
3894 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
3895 as TROVE-2017-012 and CVE-2017-8822.
3896 - When running as a relay, make sure that we never choose ourselves
3897 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
3898 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
3900 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
3901 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
3902 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
3903 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
3904 identifying and finding a workaround to this bug and to Moritz,
3905 Arthur Edelstein, and Roger for helping to track it down and
3908 o Minor features (bridge):
3909 - Bridges now include notice in their descriptors that they are
3910 bridges, and notice of their distribution status, based on their
3911 publication settings. Implements ticket 18329. For more fine-
3912 grained control of how a bridge is distributed, upgrade to 0.3.2.x
3915 o Minor features (directory authority, backport from 0.3.2.6-alpha):
3916 - Add an IPv6 address for the "bastet" directory authority. Closes
3919 o Minor features (geoip):
3920 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
3923 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
3924 - Avoid unnecessary calls to directory_fetches_from_authorities() on
3925 relays, to prevent spurious address resolutions and descriptor
3926 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
3927 bugfix on in 0.2.8.1-alpha.
3929 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
3930 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
3931 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
3933 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
3934 - When a circuit is marked for close, do not attempt to package any
3935 cells for channels on that circuit. Previously, we would detect
3936 this condition lower in the call stack, when we noticed that the
3937 circuit had no attached channel, and log an annoying message.
3938 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
3940 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
3941 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
3942 so it matches dir-spec.txt. Fixes bug 24262; bugfix
3945 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
3946 - Avoid a crash when transitioning from client mode to bridge mode.
3947 Previously, we would launch the worker threads whenever our
3948 "public server" mode changed, but not when our "server" mode
3949 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
3952 Changes in version 0.3.0.13 - 2017-12-01
3953 Tor 0.3.0.13 backports important security and stability bugfixes from
3954 later Tor releases. All Tor users should upgrade to this release, or
3955 to another of the releases coming out today.
3957 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
3958 2018. If you need a release with long-term support, please stick with
3959 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3961 o Major bugfixes (security, backport from 0.3.2.6-alpha):
3962 - Fix a denial of service bug where an attacker could use a
3963 malformed directory object to cause a Tor instance to pause while
3964 OpenSSL would try to read a passphrase from the terminal. (Tor
3965 instances run without a terminal, which is the case for most Tor
3966 packages, are not impacted.) Fixes bug 24246; bugfix on every
3967 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
3968 Found by OSS-Fuzz as testcase 6360145429790720.
3969 - Fix a denial of service issue where an attacker could crash a
3970 directory authority using a malformed router descriptor. Fixes bug
3971 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
3973 - When checking for replays in the INTRODUCE1 cell data for a
3974 (legacy) onion service, correctly detect replays in the RSA-
3975 encrypted part of the cell. We were previously checking for
3976 replays on the entire cell, but those can be circumvented due to
3977 the malleability of Tor's legacy hybrid encryption. This fix helps
3978 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
3979 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
3982 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
3983 - Fix a use-after-free error that could crash v2 Tor onion services
3984 when they failed to open circuits while expiring introduction
3985 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
3986 also tracked as TROVE-2017-013 and CVE-2017-8823.
3988 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
3989 - When running as a relay, make sure that we never build a path
3990 through ourselves, even in the case where we have somehow lost the
3991 version of our descriptor appearing in the consensus. Fixes part
3992 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
3993 as TROVE-2017-012 and CVE-2017-8822.
3994 - When running as a relay, make sure that we never choose ourselves
3995 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
3996 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
3998 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
3999 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
4000 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
4001 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
4002 identifying and finding a workaround to this bug and to Moritz,
4003 Arthur Edelstein, and Roger for helping to track it down and
4006 o Minor features (security, windows, backport from 0.3.1.1-alpha):
4007 - Enable a couple of pieces of Windows hardening: one
4008 (HeapEnableTerminationOnCorruption) that has been on-by-default
4009 since Windows 8, and unavailable before Windows 7; and one
4010 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
4011 affect us, but shouldn't do any harm. Closes ticket 21953.
4013 o Minor features (bridge, backport from 0.3.1.9):
4014 - Bridges now include notice in their descriptors that they are
4015 bridges, and notice of their distribution status, based on their
4016 publication settings. Implements ticket 18329. For more fine-
4017 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4020 o Minor features (directory authority, backport from 0.3.2.6-alpha):
4021 - Add an IPv6 address for the "bastet" directory authority. Closes
4024 o Minor features (geoip):
4025 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4028 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
4029 - Avoid unnecessary calls to directory_fetches_from_authorities() on
4030 relays, to prevent spurious address resolutions and descriptor
4031 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
4032 bugfix on in 0.2.8.1-alpha.
4034 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
4035 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
4036 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
4038 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
4039 - When a circuit is marked for close, do not attempt to package any
4040 cells for channels on that circuit. Previously, we would detect
4041 this condition lower in the call stack, when we noticed that the
4042 circuit had no attached channel, and log an annoying message.
4043 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
4045 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
4046 - Avoid a crash when transitioning from client mode to bridge mode.
4047 Previously, we would launch the worker threads whenever our
4048 "public server" mode changed, but not when our "server" mode
4049 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
4051 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
4052 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4053 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4056 Changes in version 0.2.9.14 - 2017-12-01
4057 Tor 0.3.0.13 backports important security and stability bugfixes from
4058 later Tor releases. All Tor users should upgrade to this release, or
4059 to another of the releases coming out today.
4061 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
4062 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
4063 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
4064 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
4065 identifying and finding a workaround to this bug and to Moritz,
4066 Arthur Edelstein, and Roger for helping to track it down and
4069 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4070 - Fix a denial of service bug where an attacker could use a
4071 malformed directory object to cause a Tor instance to pause while
4072 OpenSSL would try to read a passphrase from the terminal. (Tor
4073 instances run without a terminal, which is the case for most Tor
4074 packages, are not impacted.) Fixes bug 24246; bugfix on every
4075 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4076 Found by OSS-Fuzz as testcase 6360145429790720.
4077 - Fix a denial of service issue where an attacker could crash a
4078 directory authority using a malformed router descriptor. Fixes bug
4079 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
4081 - When checking for replays in the INTRODUCE1 cell data for a
4082 (legacy) onion service, correctly detect replays in the RSA-
4083 encrypted part of the cell. We were previously checking for
4084 replays on the entire cell, but those can be circumvented due to
4085 the malleability of Tor's legacy hybrid encryption. This fix helps
4086 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4087 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4090 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
4091 - Fix a use-after-free error that could crash v2 Tor onion services
4092 when they failed to open circuits while expiring introduction
4093 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
4094 also tracked as TROVE-2017-013 and CVE-2017-8823.
4096 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4097 - When running as a relay, make sure that we never build a path
4098 through ourselves, even in the case where we have somehow lost the
4099 version of our descriptor appearing in the consensus. Fixes part
4100 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
4101 as TROVE-2017-012 and CVE-2017-8822.
4103 o Minor features (bridge, backport from 0.3.1.9):
4104 - Bridges now include notice in their descriptors that they are
4105 bridges, and notice of their distribution status, based on their
4106 publication settings. Implements ticket 18329. For more fine-
4107 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4110 o Minor features (directory authority, backport from 0.3.2.6-alpha):
4111 - Add an IPv6 address for the "bastet" directory authority. Closes
4114 o Minor features (geoip):
4115 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4118 o Minor features (security, windows, backport from 0.3.1.1-alpha):
4119 - Enable a couple of pieces of Windows hardening: one
4120 (HeapEnableTerminationOnCorruption) that has been on-by-default
4121 since Windows 8, and unavailable before Windows 7; and one
4122 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
4123 affect us, but shouldn't do any harm. Closes ticket 21953.
4125 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
4126 - Avoid unnecessary calls to directory_fetches_from_authorities() on
4127 relays, to prevent spurious address resolutions and descriptor
4128 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
4129 bugfix on in 0.2.8.1-alpha.
4131 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
4132 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
4133 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
4135 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
4136 - When a circuit is marked for close, do not attempt to package any
4137 cells for channels on that circuit. Previously, we would detect
4138 this condition lower in the call stack, when we noticed that the
4139 circuit had no attached channel, and log an annoying message.
4140 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
4142 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
4143 - Avoid a crash when transitioning from client mode to bridge mode.
4144 Previously, we would launch the worker threads whenever our
4145 "public server" mode changed, but not when our "server" mode
4146 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
4148 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
4149 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4150 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4153 Changes in version 0.2.8.17 - 2017-12-01
4154 Tor 0.2.8.17 backports important security and stability bugfixes from
4155 later Tor releases. All Tor users should upgrade to this release, or
4156 to another of the releases coming out today.
4158 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
4159 2018. If you need a release with long-term support, please upgrade with
4160 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4162 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4163 - Fix a denial of service bug where an attacker could use a
4164 malformed directory object to cause a Tor instance to pause while
4165 OpenSSL would try to read a passphrase from the terminal. (Tor
4166 instances run without a terminal, which is the case for most Tor
4167 packages, are not impacted.) Fixes bug 24246; bugfix on every
4168 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4169 Found by OSS-Fuzz as testcase 6360145429790720.
4170 - When checking for replays in the INTRODUCE1 cell data for a
4171 (legacy) onion service, correctly detect replays in the RSA-
4172 encrypted part of the cell. We were previously checking for
4173 replays on the entire cell, but those can be circumvented due to
4174 the malleability of Tor's legacy hybrid encryption. This fix helps
4175 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4176 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4179 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
4180 - Fix a use-after-free error that could crash v2 Tor onion services
4181 when they failed to open circuits while expiring introduction
4182 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
4183 also tracked as TROVE-2017-013 and CVE-2017-8823.
4185 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4186 - When running as a relay, make sure that we never build a path through
4187 ourselves, even in the case where we have somehow lost the version of
4188 our descriptor appearing in the consensus. Fixes part of bug 21534;
4189 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
4192 o Minor features (bridge, backport from 0.3.1.9):
4193 - Bridges now include notice in their descriptors that they are
4194 bridges, and notice of their distribution status, based on their
4195 publication settings. Implements ticket 18329. For more fine-
4196 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4199 o Minor features (directory authority, backport from 0.3.2.6-alpha):
4200 - Add an IPv6 address for the "bastet" directory authority. Closes
4203 o Minor features (geoip):
4204 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4207 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
4208 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4209 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4212 Changes in version 0.2.5.16 - 2017-12-01
4213 Tor 0.2.5.13 backports important security and stability bugfixes from
4214 later Tor releases. All Tor users should upgrade to this release, or
4215 to another of the releases coming out today.
4217 Note: the Tor 0.2.5 series will no longer be supported after 1 May
4218 2018. If you need a release with long-term support, please upgrade to
4219 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4221 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4222 - Fix a denial of service bug where an attacker could use a
4223 malformed directory object to cause a Tor instance to pause while
4224 OpenSSL would try to read a passphrase from the terminal. (Tor
4225 instances run without a terminal, which is the case for most Tor
4226 packages, are not impacted.) Fixes bug 24246; bugfix on every
4227 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4228 Found by OSS-Fuzz as testcase 6360145429790720.
4229 - When checking for replays in the INTRODUCE1 cell data for a
4230 (legacy) onion service, correctly detect replays in the RSA-
4231 encrypted part of the cell. We were previously checking for
4232 replays on the entire cell, but those can be circumvented due to
4233 the malleability of Tor's legacy hybrid encryption. This fix helps
4234 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4235 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4238 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4239 - When running as a relay, make sure that we never build a path
4240 through ourselves, even in the case where we have somehow lost the
4241 version of our descriptor appearing in the consensus. Fixes part
4242 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
4243 as TROVE-2017-012 and CVE-2017-8822.
4245 o Minor features (bridge, backport from 0.3.1.9):
4246 - Bridges now include notice in their descriptors that they are
4247 bridges, and notice of their distribution status, based on their
4248 publication settings. Implements ticket 18329. For more fine-
4249 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4252 o Minor features (geoip):
4253 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4257 Changes in version 0.3.2.5-alpha - 2017-11-22
4258 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
4259 fixes several stability and reliability bugs, including a fix for
4260 intermittent bootstrapping failures that some people have been seeing
4261 since the 0.3.0.x series.
4263 Please test this alpha out -- many of these fixes will soon be
4264 backported to stable Tor versions if no additional bugs are found
4267 o Major bugfixes (bootstrapping):
4268 - Fetch descriptors aggressively whenever we lack enough to build
4269 circuits, regardless of how many descriptors we are missing.
4270 Previously, we would delay launching the fetch when we had fewer
4271 than 15 missing descriptors, even if some of those descriptors
4272 were blocking circuits from building. Fixes bug 23985; bugfix on
4273 0.1.1.11-alpha. The effects of this bug became worse in
4274 0.3.0.3-alpha, when we began treating missing descriptors from our
4275 primary guards as a reason to delay circuits.
4276 - Don't try fetching microdescriptors from relays that have failed
4277 to deliver them in the past. Fixes bug 23817; bugfix
4280 o Minor features (directory authority):
4281 - Make the "Exit" flag assignment only depend on whether the exit
4282 policy allows connections to ports 80 and 443. Previously relays
4283 would get the Exit flag if they allowed connections to one of
4284 these ports and also port 6667. Resolves ticket 23637.
4286 o Minor features (geoip):
4287 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4290 o Minor features (linux seccomp2 sandbox):
4291 - Update the sandbox rules so that they should now work correctly
4292 with Glibc 2.26. Closes ticket 24315.
4294 o Minor features (logging):
4295 - Downgrade a pair of log messages that could occur when an exit's
4296 resolver gave us an unusual (but not forbidden) response. Closes
4298 - Improve the message we log when re-enabling circuit build timeouts
4299 after having received a consensus. Closes ticket 20963.
4301 o Minor bugfixes (compilation):
4302 - Fix a memory leak warning in one of the libevent-related
4303 configuration tests that could occur when manually specifying
4304 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
4305 Found and patched by Alex Xu.
4306 - When detecting OpenSSL on Windows from our configure script, make
4307 sure to try linking with the ws2_32 library. Fixes bug 23783;
4308 bugfix on 0.3.2.2-alpha.
4310 o Minor bugfixes (control port, linux seccomp2 sandbox):
4311 - Avoid a crash when attempting to use the seccomp2 sandbox together
4312 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4315 o Minor bugfixes (control port, onion services):
4316 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
4317 HS_DESC event when a service is not able to upload a descriptor.
4318 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
4320 o Minor bugfixes (directory cache):
4321 - Recover better from empty or corrupt files in the consensus cache
4322 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
4323 - When a consensus diff calculation is only partially successful,
4324 only record the successful parts as having succeeded. Partial
4325 success can happen if (for example) one compression method fails
4326 but the others succeed. Previously we misrecorded all the
4327 calculations as having succeeded, which would later cause a
4328 nonfatal assertion failure. Fixes bug 24086; bugfix
4331 o Minor bugfixes (logging):
4332 - Only log once if we notice that KIST support is gone. Fixes bug
4333 24158; bugfix on 0.3.2.1-alpha.
4334 - Suppress a log notice when relay descriptors arrive. We already
4335 have a bootstrap progress for this so no need to log notice
4336 everytime tor receives relay descriptors. Microdescriptors behave
4337 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
4339 o Minor bugfixes (network layer):
4340 - When closing a connection via close_connection_immediately(), we
4341 mark it as "not blocked on bandwidth", to prevent later calls from
4342 trying to unblock it, and give it permission to read. This fixes a
4343 backtrace warning that can happen on relays under various
4344 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4346 o Minor bugfixes (onion services):
4347 - The introduction circuit was being timed out too quickly while
4348 waiting for the rendezvous circuit to complete. Keep the intro
4349 circuit around longer instead of timing out and reopening new ones
4350 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
4351 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
4352 so it matches dir-spec.txt. Fixes bug 24262; bugfix
4354 - Silence a warning about failed v3 onion descriptor uploads that
4355 can happen naturally under certain edge cases. Fixes part of bug
4356 23662; bugfix on 0.3.2.1-alpha.
4358 o Minor bugfixes (tests):
4359 - Fix a memory leak in one of the bridge-distribution test cases.
4360 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
4361 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
4362 to correctly handle cases where a caller gives it an RSA key of
4363 under 160 bits. (This is not actually a bug in Tor itself, but
4364 rather in our fuzzing code.) Fixes bug 24247; bugfix on
4365 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
4368 - Add notes in man page regarding OS support for the various
4369 scheduler types. Attempt to use less jargon in the scheduler
4370 section. Closes ticket 24254.
4373 Changes in version 0.3.2.4-alpha - 2017-11-08
4374 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
4375 It fixes several stability and reliability bugs, especially including
4376 a major reliability issue that has been plaguing fast exit relays in
4379 o Major bugfixes (exit relays, DNS):
4380 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
4381 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
4382 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
4383 identifying and finding a workaround to this bug and to Moritz,
4384 Arthur Edelstein, and Roger for helping to track it down and
4387 o Major bugfixes (scheduler, channel):
4388 - Stop processing scheduled channels if they closed while flushing
4389 cells. This can happen if the write on the connection fails
4390 leading to the channel being closed while in the scheduler loop.
4391 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
4393 o Minor features (logging, scheduler):
4394 - Introduce a SCHED_BUG() function to log extra information about
4395 the scheduler state if we ever catch a bug in the scheduler.
4396 Closes ticket 23753.
4398 o Minor features (removed deprecations):
4399 - The ClientDNSRejectInternalAddresses flag can once again be set in
4400 non-testing Tor networks, so long as they do not use the default
4401 directory authorities. This change also removes the deprecation of
4402 this flag from 0.2.9.2-alpha. Closes ticket 21031.
4404 o Minor features (testing):
4405 - Our fuzzing tests now test the encrypted portions of v3 onion
4406 service descriptors. Implements more of 21509.
4408 o Minor bugfixes (directory client):
4409 - On failure to download directory information, delay retry attempts
4410 by a random amount based on the "decorrelated jitter" algorithm.
4411 Our previous delay algorithm tended to produce extra-long delays
4412 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
4414 o Minor bugfixes (IPv6, v3 single onion services):
4415 - Remove buggy code for IPv6-only v3 single onion services, and
4416 reject attempts to configure them. This release supports IPv4,
4417 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
4418 stack v3 single onion services. Fixes bug 23820; bugfix
4421 o Minor bugfixes (logging, relay):
4422 - Give only a protocol warning when the ed25519 key is not
4423 consistent between the descriptor and microdescriptor of a relay.
4424 This can happen, for instance, if the relay has been flagged
4425 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
4427 o Minor bugfixes (manpage, onion service):
4428 - Document that the HiddenServiceNumIntroductionPoints option is
4429 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
4430 bugfix on 0.3.2.1-alpha.
4432 o Minor bugfixes (memory leaks):
4433 - Fix a minor memory leak at exit in the KIST scheduler. This bug
4434 should have no user-visible impact. Fixes bug 23774; bugfix
4436 - Fix a memory leak when decrypting a badly formatted v3 onion
4437 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
4438 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
4440 o Minor bugfixes (onion services):
4441 - Cache some needed onion service client information instead of
4442 constantly computing it over and over again. Fixes bug 23623;
4443 bugfix on 0.3.2.1-alpha.
4444 - Properly retry HSv3 descriptor fetches when missing required
4445 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
4447 o Minor bugfixes (path selection):
4448 - When selecting relays by bandwidth, avoid a rounding error that
4449 could sometimes cause load to be imbalanced incorrectly.
4450 Previously, we would always round upwards; now, we round towards
4451 the nearest integer. This had the biggest effect when a relay's
4452 weight adjustments should have given it weight 0, but it got
4453 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4454 - When calculating the fraction of nodes that have descriptors, and
4455 all nodes in the network have zero bandwidths, count the number of
4456 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4457 - Actually log the total bandwidth in compute_weighted_bandwidths().
4458 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4460 o Minor bugfixes (relay, crash):
4461 - Avoid a crash when transitioning from client mode to bridge mode.
4462 Previously, we would launch the worker threads whenever our
4463 "public server" mode changed, but not when our "server" mode
4464 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
4466 o Minor bugfixes (testing):
4467 - Fix a spurious fuzzing-only use of an uninitialized value. Found
4468 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
4469 - Test that IPv6-only clients can use microdescriptors when running
4470 "make test-network-all". Requires chutney master 61c28b9 or later.
4471 Closes ticket 24109.
4474 Changes in version 0.3.2.3-alpha - 2017-10-27
4475 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
4476 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
4477 directory authority, Bastet.
4479 o Directory authority changes:
4480 - Add "Bastet" as a ninth directory authority to the default list.
4481 Closes ticket 23910.
4482 - The directory authority "Longclaw" has changed its IP address.
4483 Closes ticket 23592.
4485 o Minor features (bridge):
4486 - Bridge relays can now set the BridgeDistribution config option to
4487 add a "bridge-distribution-request" line to their bridge
4488 descriptor, which tells BridgeDB how they'd like their bridge
4489 address to be given out. (Note that as of Oct 2017, BridgeDB does
4490 not yet implement this feature.) As a side benefit, this feature
4491 provides a way to distinguish bridge descriptors from non-bridge
4492 descriptors. Implements tickets 18329.
4494 o Minor features (client, entry guards):
4495 - Improve log messages when missing descriptors for primary guards.
4496 Resolves ticket 23670.
4498 o Minor features (geoip):
4499 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4502 o Minor bugfixes (bridge):
4503 - Overwrite the bridge address earlier in the process of retrieving
4504 its descriptor, to make sure we reach it on the configured
4505 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
4507 o Minor bugfixes (documentation):
4508 - Document better how to read gcov, and what our gcov postprocessing
4509 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
4511 o Minor bugfixes (entry guards):
4512 - Tor now updates its guard state when it reads a consensus
4513 regardless of whether it's missing descriptors. That makes tor use
4514 its primary guards to fetch descriptors in some edge cases where
4515 it would previously have used fallback directories. Fixes bug
4516 23862; bugfix on 0.3.0.1-alpha.
4518 o Minor bugfixes (hidden service client):
4519 - When handling multiple SOCKS request for the same .onion address,
4520 only fetch the service descriptor once.
4521 - When a descriptor fetch fails with a non-recoverable error, close
4522 all pending SOCKS requests for that .onion. Fixes bug 23653;
4523 bugfix on 0.3.2.1-alpha.
4525 o Minor bugfixes (hidden service):
4526 - Always regenerate missing hidden service public key files. Prior
4527 to this, if the public key was deleted from disk, it wouldn't get
4528 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
4530 - Make sure that we have a usable ed25519 key when the intro point
4531 relay supports ed25519 link authentication. Fixes bug 24002;
4532 bugfix on 0.3.2.1-alpha.
4534 o Minor bugfixes (hidden service, v2):
4535 - When reloading configured hidden services, copy all information
4536 from the old service object. Previously, some data was omitted,
4537 causing delays in descriptor upload, and other bugs. Fixes bug
4538 23790; bugfix on 0.2.1.9-alpha.
4540 o Minor bugfixes (memory safety, defensive programming):
4541 - Clear the target address when node_get_prim_orport() returns
4542 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
4544 o Minor bugfixes (relay):
4545 - Avoid a BUG warning when receiving a dubious CREATE cell while an
4546 option transition is in progress. Fixes bug 23952; bugfix
4549 o Minor bugfixes (testing):
4550 - Adjust the GitLab CI configuration to more closely match that of
4551 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
4552 - Prevent scripts/test/coverage from attempting to move gcov output
4553 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
4554 - When running unit tests as root, skip a test that would fail
4555 because it expects a permissions error. This affects some
4556 continuous integration setups. Fixes bug 23758; bugfix
4558 - Stop unconditionally mirroring the tor repository in GitLab CI.
4559 This prevented developers from enabling GitLab CI on master. Fixes
4560 bug 23755; bugfix on 0.3.2.2-alpha.
4561 - Fix the hidden service v3 descriptor decoding fuzzing to use the
4562 latest decoding API correctly. Fixes bug 21509; bugfix
4565 o Minor bugfixes (warnings):
4566 - When we get an HTTP request on a SOCKS port, tell the user about
4567 the new HTTPTunnelPort option. Previously, we would give a "Tor is
4568 not an HTTP Proxy" message, which stopped being true when
4569 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
4573 Changes in version 0.2.5.15 - 2017-10-25
4574 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
4575 series. It also adds a new directory authority, Bastet.
4577 Note: the Tor 0.2.5 series will no longer be supported after 1 May
4578 2018. If you need a release with long-term support, please upgrade to
4579 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4581 o Directory authority changes:
4582 - Add "Bastet" as a ninth directory authority to the default list.
4583 Closes ticket 23910.
4584 - The directory authority "Longclaw" has changed its IP address.
4585 Closes ticket 23592.
4587 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
4588 - Avoid an assertion failure bug affecting our implementation of
4589 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
4590 handling of "0xx" differs from what we had expected. Fixes bug
4591 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
4593 o Minor features (geoip):
4594 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4597 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
4598 - Fix a memset() off the end of an array when packing cells. This
4599 bug should be harmless in practice, since the corrupted bytes are
4600 still in the same structure, and are always padding bytes,
4601 ignored, or immediately overwritten, depending on compiler
4602 behavior. Nevertheless, because the memset()'s purpose is to make
4603 sure that any other cell-handling bugs can't expose bytes to the
4604 network, we need to fix it. Fixes bug 22737; bugfix on
4605 0.2.4.11-alpha. Fixes CID 1401591.
4607 o Build features (backport from 0.3.1.5-alpha):
4608 - Tor's repository now includes a Travis Continuous Integration (CI)
4609 configuration file (.travis.yml). This is meant to help new
4610 developers and contributors who fork Tor to a Github repository be
4611 better able to test their changes, and understand what we expect
4612 to pass. To use this new build feature, you must fork Tor to your
4613 Github account, then go into the "Integrations" menu in the
4614 repository settings for your fork and enable Travis, then push
4615 your changes. Closes ticket 22636.
4618 Changes in version 0.2.8.16 - 2017-10-25
4619 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
4620 series, including a bugfix for a crash issue that had affected relays
4621 under memory pressure. It also adds a new directory authority, Bastet.
4623 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
4624 2018. If you need a release with long-term support, please stick with
4625 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4627 o Directory authority changes:
4628 - Add "Bastet" as a ninth directory authority to the default list.
4629 Closes ticket 23910.
4630 - The directory authority "Longclaw" has changed its IP address.
4631 Closes ticket 23592.
4633 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
4634 - Fix a timing-based assertion failure that could occur when the
4635 circuit out-of-memory handler freed a connection's output buffer.
4636 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
4638 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
4639 - Remove longclaw's IPv6 address, as it will soon change. Authority
4640 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
4641 3/8 directory authorities with IPv6 addresses, but there are also
4642 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
4644 o Minor features (geoip):
4645 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4649 Changes in version 0.2.9.13 - 2017-10-25
4650 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
4651 series, including a bugfix for a crash issue that had affected relays
4652 under memory pressure. It also adds a new directory authority, Bastet.
4654 o Directory authority changes:
4655 - Add "Bastet" as a ninth directory authority to the default list.
4656 Closes ticket 23910.
4657 - The directory authority "Longclaw" has changed its IP address.
4658 Closes ticket 23592.
4660 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
4661 - Fix a timing-based assertion failure that could occur when the
4662 circuit out-of-memory handler freed a connection's output buffer.
4663 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
4665 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
4666 - Remove longclaw's IPv6 address, as it will soon change. Authority
4667 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
4668 3/8 directory authorities with IPv6 addresses, but there are also
4669 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
4671 o Minor features (geoip):
4672 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4675 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
4676 - When a directory authority rejects a descriptor or extrainfo with
4677 a given digest, mark that digest as undownloadable, so that we do
4678 not attempt to download it again over and over. We previously
4679 tried to avoid downloading such descriptors by other means, but we
4680 didn't notice if we accidentally downloaded one anyway. This
4681 behavior became problematic in 0.2.7.2-alpha, when authorities
4682 began pinning Ed25519 keys. Fixes bug 22349; bugfix
4685 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
4686 - Clear the address when node_get_prim_orport() returns early.
4687 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
4689 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
4690 - When running as a Windows service, set the ID of the main thread
4691 correctly. Failure to do so made us fail to send log messages to
4692 the controller in 0.2.1.16-rc, slowed down controller event
4693 delivery in 0.2.7.3-rc and later, and crash with an assertion
4694 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
4695 Patch and diagnosis from "Vort".
4698 Changes in version 0.3.0.12 - 2017-10-25
4699 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
4700 series, including a bugfix for a crash issue that had affected relays
4701 under memory pressure. It also adds a new directory authority, Bastet.
4703 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
4704 2018. If you need a release with long-term support, please stick with
4705 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4707 o Directory authority changes:
4708 - Add "Bastet" as a ninth directory authority to the default list.
4709 Closes ticket 23910.
4710 - The directory authority "Longclaw" has changed its IP address.
4711 Closes ticket 23592.
4713 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
4714 - Fix a timing-based assertion failure that could occur when the
4715 circuit out-of-memory handler freed a connection's output buffer.
4716 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
4718 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
4719 - Remove longclaw's IPv6 address, as it will soon change. Authority
4720 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
4721 3/8 directory authorities with IPv6 addresses, but there are also
4722 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
4724 o Minor features (geoip):
4725 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4728 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
4729 - When a directory authority rejects a descriptor or extrainfo with
4730 a given digest, mark that digest as undownloadable, so that we do
4731 not attempt to download it again over and over. We previously
4732 tried to avoid downloading such descriptors by other means, but we
4733 didn't notice if we accidentally downloaded one anyway. This
4734 behavior became problematic in 0.2.7.2-alpha, when authorities
4735 began pinning Ed25519 keys. Fixes bug 22349; bugfix
4738 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
4739 - Avoid a possible double close of a circuit by the intro point on
4740 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
4741 bugfix on 0.3.0.1-alpha.
4743 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
4744 - Clear the address when node_get_prim_orport() returns early.
4745 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
4747 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
4748 - When running as a Windows service, set the ID of the main thread
4749 correctly. Failure to do so made us fail to send log messages to
4750 the controller in 0.2.1.16-rc, slowed down controller event
4751 delivery in 0.2.7.3-rc and later, and crash with an assertion
4752 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
4753 Patch and diagnosis from "Vort".
4756 Changes in version 0.3.1.8 - 2017-10-25
4757 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
4758 It includes several bugfixes, including a bugfix for a crash issue
4759 that had affected relays under memory pressure. It also adds
4760 a new directory authority, Bastet.
4762 o Directory authority changes:
4763 - Add "Bastet" as a ninth directory authority to the default list.
4764 Closes ticket 23910.
4765 - The directory authority "Longclaw" has changed its IP address.
4766 Closes ticket 23592.
4768 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
4769 - Fix a timing-based assertion failure that could occur when the
4770 circuit out-of-memory handler freed a connection's output buffer.
4771 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
4773 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
4774 - Remove longclaw's IPv6 address, as it will soon change. Authority
4775 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
4776 3/8 directory authorities with IPv6 addresses, but there are also
4777 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
4779 o Minor features (geoip):
4780 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4783 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
4784 - Fix a compilation warning when building with zstd support on
4785 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
4786 and fixed by Andreas Stieger.
4788 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
4789 - Handle a pathological case when decompressing Zstandard data when
4790 the output buffer size is zero. Fixes bug 23551; bugfix
4793 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
4794 - Remove the length limit on HTTP status lines that authorities can
4795 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
4797 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
4798 - Avoid a possible double close of a circuit by the intro point on
4799 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
4800 bugfix on 0.3.0.1-alpha.
4802 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
4803 - Clear the address when node_get_prim_orport() returns early.
4804 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
4806 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
4807 - Fix additional channelpadding unit test failures by using mocked
4808 time instead of actual time for all tests. Fixes bug 23608; bugfix
4812 Changes in version 0.3.2.2-alpha - 2017-09-29
4813 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
4814 release fixes several minor bugs in the new scheduler and next-
4815 generation onion services; both features were newly added in the 0.3.2
4816 series. Other fixes in this alpha include several fixes for non-fatal
4817 tracebacks which would appear in logs.
4819 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
4820 alpha does not contain any substantial new features. Minor features
4821 include better testing and logging.
4823 The following comprises the complete list of changes included
4826 o Major bugfixes (relay, crash, assertion failure):
4827 - Fix a timing-based assertion failure that could occur when the
4828 circuit out-of-memory handler freed a connection's output buffer.
4829 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
4831 o Major bugfixes (scheduler):
4832 - If a channel is put into the scheduler's pending list, then it
4833 starts closing, and then if the scheduler runs before it finishes
4834 closing, the scheduler will get stuck trying to flush its cells
4835 while the lower layers refuse to cooperate. Fix that race
4836 condition by giving the scheduler an escape method. Fixes bug
4837 23676; bugfix on 0.3.2.1-alpha.
4839 o Minor features (build, compilation):
4840 - The "check-changes" feature is now part of the "make check" tests;
4841 we'll use it to try to prevent misformed changes files from
4842 accumulating. Closes ticket 23564.
4843 - Tor builds should now fail if there are any mismatches between the
4844 C type representing a configuration variable and the C type the
4845 data-driven parser uses to store a value there. Previously, we
4846 needed to check these by hand, which sometimes led to mistakes.
4847 Closes ticket 23643.
4849 o Minor features (directory authorities):
4850 - Remove longclaw's IPv6 address, as it will soon change. Authority
4851 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
4852 3/8 directory authorities with IPv6 addresses, but there are also
4853 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
4855 o Minor features (hidden service, circuit, logging):
4856 - Improve logging of many callsite in the circuit subsystem to print
4857 the circuit identifier(s).
4858 - Log when we cleanup an intro point from a service so we know when
4859 and for what reason it happened. Closes ticket 23604.
4861 o Minor features (logging):
4862 - Log more circuit information whenever we are about to try to
4863 package a relay cell on a circuit with a nonexistent n_chan.
4864 Attempt to diagnose ticket 8185.
4865 - Improve info-level log identification of particular circuits, to
4866 help with debugging. Closes ticket 23645.
4868 o Minor features (relay):
4869 - When choosing which circuits can be expired as unused, consider
4870 circuits from clients even if those clients used regular CREATE
4871 cells to make them; and do not consider circuits from relays even
4872 if they were made with CREATE_FAST. Part of ticket 22805.
4874 o Minor features (robustness):
4875 - Change several fatal assertions when flushing buffers into non-
4876 fatal assertions, to prevent any recurrence of 23690.
4878 o Minor features (spec conformance, bridge, diagnostic):
4879 - When handling the USERADDR command on an ExtOrPort, warn when the
4880 transports provides a USERADDR with no port. In a future version,
4881 USERADDR commands of this format may be rejected. Detects problems
4882 related to ticket 23080.
4884 o Minor features (testing):
4885 - Add a unit test to make sure that our own generated platform
4886 string will be accepted by directory authorities. Closes
4889 o Minor bugfixes (bootstrapping):
4890 - When warning about state file clock skew, report the correct
4891 direction for the detected skew. Fixes bug 23606; bugfix
4893 - Avoid an assertion failure when logging a state file clock skew
4894 very early in bootstrapping. Fixes bug 23607; bugfix
4897 o Minor bugfixes (build, compilation):
4898 - Fix a compilation warning when building with zstd support on
4899 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
4900 and fixed by Andreas Stieger.
4901 - When searching for OpenSSL, don't accept any OpenSSL library that
4902 lacks TLSv1_1_method(): Tor doesn't build with those versions.
4903 Additionally, look in /usr/local/opt/openssl, if it's present.
4904 These changes together repair the default build on OSX systems
4905 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
4907 o Minor bugfixes (compression):
4908 - Handle a pathological case when decompressing Zstandard data when
4909 the output buffer size is zero. Fixes bug 23551; bugfix
4912 o Minor bugfixes (documentation):
4913 - Fix manpage to not refer to the obsolete (and misspelled)
4914 UseEntryGuardsAsDirectoryGuards parameter in the description of
4915 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
4917 o Minor bugfixes (hidden service v3):
4918 - Don't log an assertion failure when we can't find the right
4919 information to extend to an introduction point. In rare cases,
4920 this could happen, causing a warning, even though tor would
4921 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
4922 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
4923 much bigger so the rendezvous point can't distinguish which hidden
4924 service protocol is being used. Fixes bug 23420; bugfix
4927 o Minor bugfixes (hidden service, relay):
4928 - Avoid a possible double close of a circuit by the intro point on
4929 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
4930 bugfix on 0.3.0.1-alpha.
4932 o Minor bugfixes (logging, relay shutdown, annoyance):
4933 - When a circuit is marked for close, do not attempt to package any
4934 cells for channels on that circuit. Previously, we would detect
4935 this condition lower in the call stack, when we noticed that the
4936 circuit had no attached channel, and log an annoying message.
4937 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
4939 o Minor bugfixes (scheduler):
4940 - When switching schedulers due to a consensus change, we didn't
4941 give the new scheduler a chance to react to the consensus. Fix
4942 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
4943 - Make the KISTSchedRunInterval option a non negative value. With
4944 this, the way to disable KIST through the consensus is to set it
4945 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
4946 - Only notice log the selected scheduler when we switch scheduler
4947 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
4948 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
4949 by a different tv_usec data type. Fixes bug 23575; bugfix
4951 - Make a hard exit if tor is unable to pick a scheduler which can
4952 happen if the user specifies a scheduler type that is not
4953 supported and not other types in Schedulers. Fixes bug 23581;
4954 bugfix on 0.3.2.1-alpha.
4955 - Properly initialize the scheduler last run time counter so it is
4956 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
4958 o Minor bugfixes (testing):
4959 - Capture and detect several "Result does not fit" warnings in unit
4960 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
4962 - Fix additional channelpadding unit test failures by using mocked
4963 time instead of actual time for all tests. Fixes bug 23608; bugfix
4965 - The removal of some old scheduler options caused some tests to
4966 fail on BSD systems. Assume current behavior is correct and make
4967 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
4969 o Code simplification and refactoring:
4970 - Remove various ways of testing circuits and connections for
4971 "clientness"; instead, favor channel_is_client(). Part of
4974 o Deprecated features:
4975 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
4976 now deprecated; they do not apply to relays, and they have had no
4977 effect on clients since 0.2.8.x. Closes ticket 19704.
4980 - HiddenServiceVersion man page entry wasn't mentioning the now
4981 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
4982 - Clarify that the Address option is entirely about setting an
4983 advertised IPv4 address. Closes ticket 18891.
4984 - Clarify the manpage's use of the term "address" to clarify what
4985 kind of address is intended. Closes ticket 21405.
4986 - Document that onion service subdomains are allowed, and ignored.
4987 Closes ticket 18736.
4990 Changes in version 0.3.2.1-alpha - 2017-09-18
4991 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
4992 includes support for our next-generation ("v3") onion service
4993 protocol, and adds a new circuit scheduler for more responsive
4994 forwarding decisions from relays. There are also numerous other small
4995 features and bugfixes here.
4997 Below are the changes since Tor 0.3.1.7.
4999 o Major feature (scheduler, channel):
5000 - Tor now uses new schedulers to decide which circuits should
5001 deliver cells first, in order to improve congestion at relays. The
5002 first type is called "KIST" ("Kernel Informed Socket Transport"),
5003 and is only available on Linux-like systems: it uses feedback from
5004 the kernel to prevent the kernel's TCP buffers from growing too
5005 full. The second new scheduler type is called "KISTLite": it
5006 behaves the same as KIST, but runs on systems without kernel
5007 support for inspecting TCP implementation details. The old
5008 scheduler is still available, under the name "Vanilla". To change
5009 the default scheduler preference order, use the new "Schedulers"
5010 option. (The default preference order is "KIST,KISTLite,Vanilla".)
5012 Matt Traudt implemented KIST, based on research by Rob Jansen,
5013 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
5014 more information, see the design paper at
5015 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
5016 followup implementation paper at https://arxiv.org/abs/1709.01044.
5017 Closes ticket 12541.
5019 o Major features (next-generation onion services):
5020 - Tor now supports the next-generation onion services protocol for
5021 clients and services! As part of this release, the core of
5022 proposal 224 has been implemented and is available for
5023 experimentation and testing by our users. This newer version of
5024 onion services ("v3") features many improvements over the legacy
5027 a) Better crypto (replaced SHA1/DH/RSA1024
5028 with SHA3/ed25519/curve25519)
5030 b) Improved directory protocol, leaking much less information to
5033 c) Improved directory protocol, with smaller surface for
5036 d) Better onion address security against impersonation.
5038 e) More extensible introduction/rendezvous protocol.
5040 f) A cleaner and more modular codebase.
5042 You can identify a next-generation onion address by its length:
5043 they are 56 characters long, as in
5044 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
5046 In the future, we will release more options and features for v3
5047 onion services, but we first need a testing period, so that the
5048 current codebase matures and becomes more robust. Planned features
5049 include: offline keys, advanced client authorization, improved
5050 guard algorithms, and statistics. For full details, see
5053 Legacy ("v2") onion services will still work for the foreseeable
5054 future, and will remain the default until this new codebase gets
5055 tested and hardened. Service operators who want to experiment with
5056 the new system can use the 'HiddenServiceVersion 3' torrc
5057 directive along with the regular onion service configuration
5058 options. We will publish a blog post about this new feature
5061 o Major bugfixes (usability, control port):
5062 - Report trusted clock skew indications as bootstrap errors, so
5063 controllers can more easily alert users when their clocks are
5064 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
5066 o Minor features (bug detection):
5067 - Log a warning message with a stack trace for any attempt to call
5068 get_options() during option validation. This pattern has caused
5069 subtle bugs in the past. Closes ticket 22281.
5071 o Minor features (client):
5072 - You can now use Tor as a tunneled HTTP proxy: use the new
5073 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
5074 requests. Closes ticket 22407.
5075 - Add an extra check to make sure that we always use the newer guard
5076 selection code for picking our guards. Closes ticket 22779.
5077 - When downloading (micro)descriptors, don't split the list into
5078 multiple requests unless we want at least 32 descriptors.
5079 Previously, we split at 4, not 32, which led to significant
5080 overhead in HTTP request size and degradation in compression
5081 performance. Closes ticket 23220.
5083 o Minor features (command line):
5084 - Add a new commandline option, --key-expiration, which prints when
5085 the current signing key is going to expire. Implements ticket
5086 17639; patch by Isis Lovecruft.
5088 o Minor features (control port):
5089 - If an application tries to use the control port as an HTTP proxy,
5090 respond with a meaningful "This is the Tor control port" message,
5091 and log the event. Closes ticket 1667. Patch from Ravi
5093 - Provide better error message for GETINFO desc/(id|name) when not
5094 fetching router descriptors. Closes ticket 5847. Patch by
5096 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
5097 whether Tor will try to download router descriptors and
5098 microdescriptors respectively. Closes ticket 22684.
5099 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
5100 so controllers can tell whether the geoip databases are loaded.
5101 Closes ticket 23237.
5102 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
5103 events. Closes ticket 19254. Patch by "DonnchaC".
5105 o Minor features (development support):
5106 - Developers can now generate a call-graph for Tor using the
5107 "calltool" python program, which post-processes object dumps. It
5108 should work okay on many Linux and OSX platforms, and might work
5109 elsewhere too. To run it, install calltool from
5110 https://gitweb.torproject.org/user/nickm/calltool.git and run
5111 "make callgraph". Closes ticket 19307.
5113 o Minor features (ed25519):
5114 - Add validation function to checks for torsion components in
5115 ed25519 public keys, used by prop224 client-side code. Closes
5116 ticket 22006. Math help by Ian Goldberg.
5118 o Minor features (exit relay, DNS):
5119 - Improve the clarity and safety of the log message from evdns when
5120 receiving an apparently spoofed DNS reply. Closes ticket 3056.
5122 o Minor features (integration, hardening):
5123 - Add a new NoExec option to prevent Tor from running other
5124 programs. When this option is set to 1, Tor will never try to run
5125 another program, regardless of the settings of
5126 PortForwardingHelper, ClientTransportPlugin, or
5127 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
5128 without restarting Tor. Closes ticket 22976.
5130 o Minor features (logging):
5131 - Improve the warning message for specifying a relay by nickname.
5132 The previous message implied that nickname registration was still
5133 part of the Tor network design, which it isn't. Closes
5135 - If the sandbox filter fails to load, suggest to the user that
5136 their kernel might not support seccomp2. Closes ticket 23090.
5138 o Minor features (portability):
5139 - Check at configure time whether uint8_t is the same type as
5140 unsigned char. Lots of existing code already makes this
5141 assumption, and there could be strict aliasing issues if the
5142 assumption is violated. Closes ticket 22410.
5144 o Minor features (relay, configuration):
5145 - Reject attempts to use relative file paths when RunAsDaemon is
5146 set. Previously, Tor would accept these, but the directory-
5147 changing step of RunAsDaemon would give strange and/or confusing
5148 results. Closes ticket 22731.
5150 o Minor features (startup, safety):
5151 - When configured to write a PID file, Tor now exits if it is unable
5152 to do so. Previously, it would warn and continue. Closes
5155 o Minor features (static analysis):
5156 - The BUG() macro has been changed slightly so that Coverity no
5157 longer complains about dead code if the bug is impossible. Closes
5160 o Minor features (testing):
5161 - The default chutney network tests now include tests for the v3
5162 hidden service design. Make sure you have the latest version of
5163 chutney if you want to run these. Closes ticket 22437.
5164 - Add a unit test to verify that we can parse a hardcoded v2 hidden
5165 service descriptor. Closes ticket 15554.
5167 o Minor bugfixes (certificate handling):
5168 - Fix a time handling bug in Tor certificates set to expire after
5169 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
5170 Coverity as CID 1415728.
5172 o Minor bugfixes (client, usability):
5173 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
5174 SOCKS4a requests that contain IP address strings, even when
5175 SafeSocks in enabled, as this prevents user from connecting to
5176 known IP addresses without relying on DNS for resolving. SafeSocks
5177 still rejects SOCKS connections that connect to IP addresses when
5178 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
5179 bugfix on Tor 0.2.6.2-alpha.
5181 o Minor bugfixes (code correctness):
5182 - Call htons() in extend_cell_format() for encoding a 16-bit value.
5183 Previously we used ntohs(), which happens to behave the same on
5184 all the platforms we support, but which isn't really correct.
5185 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
5186 - For defense-in-depth, make the controller's write_escaped_data()
5187 function robust to extremely long inputs. Fixes bug 19281; bugfix
5188 on 0.1.1.1-alpha. Reported by Guido Vranken.
5190 o Minor bugfixes (compilation):
5191 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
5192 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5194 o Minor bugfixes (consensus expiry):
5195 - Check for adequate directory information correctly. Previously, Tor
5196 would reconsider whether it had sufficient directory information
5197 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
5199 o Minor bugfixes (directory protocol):
5200 - Directory servers now include a "Date:" http header for response
5201 codes other than 200. Clients starting with a skewed clock and a
5202 recent consensus were getting "304 Not modified" responses from
5203 directory authorities, so without the Date header, the client
5204 would never hear about a wrong clock. Fixes bug 23499; bugfix
5206 - Make clients wait for 6 seconds before trying to download a
5207 consensus from an authority. Fixes bug 17750; bugfix
5210 o Minor bugfixes (DoS-resistance):
5211 - If future code asks if there are any running bridges, without
5212 checking if bridges are enabled, log a BUG warning rather than
5213 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
5215 o Minor bugfixes (format strictness):
5216 - Restrict several data formats to decimal. Previously, the
5217 BuildTimeHistogram entries in the state file, the "bw=" entries in
5218 the bandwidth authority file, and the process IDs passed to the
5219 __OwningControllerProcess option could all be specified in hex or
5220 octal as well as in decimal. This was not an intentional feature.
5221 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
5224 o Minor bugfixes (heartbeat):
5225 - If we fail to write a heartbeat message, schedule a retry for the
5226 minimum heartbeat interval number of seconds in the future. Fixes
5227 bug 19476; bugfix on 0.2.3.1-alpha.
5229 o Minor bugfixes (linux seccomp2 sandbox, logging):
5230 - Fix some messages on unexpected errors from the seccomp2 library.
5231 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
5233 o Minor bugfixes (logging):
5234 - Remove duplicate log messages regarding opening non-local
5235 SocksPorts upon parsing config and opening listeners at startup.
5236 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
5237 - Use a more comprehensible log message when telling the user
5238 they've excluded every running exit node. Fixes bug 7890; bugfix
5240 - When logging the number of descriptors we intend to download per
5241 directory request, do not log a number higher than then the number
5242 of descriptors we're fetching in total. Fixes bug 19648; bugfix
5244 - When warning about a directory owned by the wrong user, log the
5245 actual name of the user owning the directory. Previously, we'd log
5246 the name of the process owner twice. Fixes bug 23487; bugfix
5248 - The tor specification says hop counts are 1-based, so fix two log
5249 messages that mistakenly logged 0-based hop counts. Fixes bug
5250 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
5251 Credit to Xiaofan Li for reporting this issue.
5253 o Minor bugfixes (portability):
5254 - Stop using the PATH_MAX variable, which is not defined on GNU
5255 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
5257 o Minor bugfixes (relay):
5258 - When uploading our descriptor for the first time after startup,
5259 report the reason for uploading as "Tor just started" rather than
5260 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
5261 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5262 relays, to prevent spurious address resolutions and descriptor
5263 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5264 bugfix on in 0.2.8.1-alpha.
5266 o Minor bugfixes (tests):
5267 - Fix a broken unit test for the OutboundAddress option: the parsing
5268 function was never returning an error on failure. Fixes bug 23366;
5269 bugfix on 0.3.0.3-alpha.
5270 - Fix a signed-integer overflow in the unit tests for
5271 dir/download_status_random_backoff, which was untriggered until we
5272 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
5274 o Minor bugfixes (usability, control port):
5275 - Stop making an unnecessary routerlist check in NETINFO clock skew
5276 detection; this was preventing clients from reporting NETINFO clock
5277 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
5279 o Code simplification and refactoring:
5280 - Extract the code for handling newly-open channels into a separate
5281 function from the general code to handle channel state
5282 transitions. This change simplifies our callgraph, reducing the
5283 size of the largest strongly connected component by roughly a
5284 factor of two. Closes ticket 22608.
5285 - Remove dead code for largely unused statistics on the number of
5286 times we've attempted various public key operations. Fixes bug
5287 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
5288 - Remove several now-obsolete functions for asking about old
5289 variants directory authority status. Closes ticket 22311; patch
5291 - Remove some of the code that once supported "Named" and "Unnamed"
5292 routers. Authorities no longer vote for these flags. Closes
5294 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
5295 and old hidden services, to indicate that they aren't suitable for
5296 new protocols or formats. Closes ticket 23026.
5297 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
5298 22521. Patch from Neel Chauhan.
5299 - Split the enormous circuit_send_next_onion_skin() function into
5300 multiple subfunctions. Closes ticket 22804.
5301 - Split the portions of the buffer.c module that handle particular
5302 protocols into separate modules. Part of ticket 23149.
5303 - Use our test macros more consistently, to produce more useful
5304 error messages when our unit tests fail. Add coccinelle patches to
5305 allow us to re-check for test macro uses. Closes ticket 22497.
5307 o Deprecated features:
5308 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
5309 only applies to direct unencrypted HTTP connections to your
5310 directory server, which your Tor probably isn't using. Closes
5314 - Clarify in the manual that "Sandbox 1" is only supported on Linux
5315 kernels. Closes ticket 22677.
5316 - Document all values of PublishServerDescriptor in the manpage.
5317 Closes ticket 15645.
5318 - Improve the documentation for the directory port part of the
5319 DirAuthority line. Closes ticket 20152.
5320 - Restore documentation for the authorities' "approved-routers"
5321 file. Closes ticket 21148.
5324 - The AllowDotExit option has been removed as unsafe. It has been
5325 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
5326 - The ClientDNSRejectInternalAddresses flag can no longer be set on
5327 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
5328 Closes ticket 21031.
5329 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
5330 nobody was using it any longer. Closes ticket 22377.
5333 Changes in version 0.2.8.15 - 2017-09-18
5334 Tor 0.2.8.15 backports a collection of bugfixes from later
5337 Most significantly, it includes a fix for TROVE-2017-008, a
5338 security bug that affects hidden services running with the
5339 SafeLogging option disabled. For more information, see
5340 https://trac.torproject.org/projects/tor/ticket/23490
5342 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
5343 2018. We suggest that you upgrade to the latest stable release if
5344 possible. If you can't, we recommend that you upgrade at least to
5345 0.2.9, which will be supported until 2020.
5347 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
5348 - Avoid an assertion failure bug affecting our implementation of
5349 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5350 handling of "0xx" differs from what we had expected. Fixes bug
5351 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5354 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5357 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
5358 - Backport a fix for an "unused variable" warning that appeared
5359 in some versions of mingw. Fixes bug 22838; bugfix on
5362 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
5363 - Fix a memset() off the end of an array when packing cells. This
5364 bug should be harmless in practice, since the corrupted bytes are
5365 still in the same structure, and are always padding bytes,
5366 ignored, or immediately overwritten, depending on compiler
5367 behavior. Nevertheless, because the memset()'s purpose is to make
5368 sure that any other cell-handling bugs can't expose bytes to the
5369 network, we need to fix it. Fixes bug 22737; bugfix on
5370 0.2.4.11-alpha. Fixes CID 1401591.
5372 o Build features (backport from 0.3.1.5-alpha):
5373 - Tor's repository now includes a Travis Continuous Integration (CI)
5374 configuration file (.travis.yml). This is meant to help new
5375 developers and contributors who fork Tor to a Github repository be
5376 better able to test their changes, and understand what we expect
5377 to pass. To use this new build feature, you must fork Tor to your
5378 Github account, then go into the "Integrations" menu in the
5379 repository settings for your fork and enable Travis, then push
5380 your changes. Closes ticket 22636.
5383 Changes in version 0.2.9.12 - 2017-09-18
5384 Tor 0.2.9.12 backports a collection of bugfixes from later
5387 Most significantly, it includes a fix for TROVE-2017-008, a
5388 security bug that affects hidden services running with the
5389 SafeLogging option disabled. For more information, see
5390 https://trac.torproject.org/projects/tor/ticket/23490
5392 o Major features (security, backport from 0.3.0.2-alpha):
5393 - Change the algorithm used to decide DNS TTLs on client and server
5394 side, to better resist DNS-based correlation attacks like the
5395 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
5396 Feamster. Now relays only return one of two possible DNS TTL
5397 values, and clients are willing to believe DNS TTL values up to 3
5398 hours long. Closes ticket 19769.
5400 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
5401 - Fix a rare crash when sending a begin cell on a circuit whose
5402 linked directory connection had already been closed. Fixes bug
5403 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
5405 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
5406 - Fix a bug that prevented exit nodes from caching DNS records for
5407 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
5409 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
5410 - Fix a typo that had prevented TPROXY-based transparent proxying
5411 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
5412 Patch from "d4fq0fQAgoJ".
5414 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
5415 - Avoid an assertion failure bug affecting our implementation of
5416 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5417 handling of "0xx" differs from what we had expected. Fixes bug
5418 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5420 o Minor features (code style, backport from 0.3.1.3-alpha):
5421 - Add "Falls through" comments to our codebase, in order to silence
5422 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
5423 Stieger. Closes ticket 22446.
5425 o Minor features (geoip):
5426 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5429 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
5430 - Roll over monthly accounting at the configured hour and minute,
5431 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
5432 Found by Andrey Karpov with PVS-Studio.
5434 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
5435 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
5436 bugfix on 0.2.8.1-alpha.
5437 - Fix warnings when building with libscrypt and openssl scrypt support
5438 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
5439 - When building with certain versions the mingw C header files, avoid
5440 float-conversion warnings when calling the C functions isfinite(),
5441 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
5443 o Minor bugfixes (compilation, backport from 0.3.1.7):
5444 - Avoid compiler warnings in the unit tests for running tor_sscanf()
5445 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
5447 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
5448 - Backport a fix for an "unused variable" warning that appeared
5449 in some versions of mingw. Fixes bug 22838; bugfix on
5452 o Minor bugfixes (controller, backport from 0.3.1.7):
5453 - Do not crash when receiving a HSPOST command with an empty body.
5454 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
5455 - Do not crash when receiving a POSTDESCRIPTOR command with an
5456 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
5458 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
5459 - Avoid Coverity build warnings related to our BUG() macro. By
5460 default, Coverity treats BUG() as the Linux kernel does: an
5461 instant abort(). We need to override that so our BUG() macro
5462 doesn't prevent Coverity from analyzing functions that use it.
5463 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
5465 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
5466 - Fix a memset() off the end of an array when packing cells. This
5467 bug should be harmless in practice, since the corrupted bytes are
5468 still in the same structure, and are always padding bytes,
5469 ignored, or immediately overwritten, depending on compiler
5470 behavior. Nevertheless, because the memset()'s purpose is to make
5471 sure that any other cell-handling bugs can't expose bytes to the
5472 network, we need to fix it. Fixes bug 22737; bugfix on
5473 0.2.4.11-alpha. Fixes CID 1401591.
5475 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
5476 - When setting the maximum number of connections allowed by the OS,
5477 always allow some extra file descriptors for other files. Fixes
5478 bug 22797; bugfix on 0.2.0.10-alpha.
5480 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
5481 - Avoid a sandbox failure when trying to re-bind to a socket and
5482 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
5484 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
5485 - Permit the fchmod system call, to avoid crashing on startup when
5486 starting with the seccomp2 sandbox and an unexpected set of
5487 permissions on the data directory or its contents. Fixes bug
5488 22516; bugfix on 0.2.5.4-alpha.
5490 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
5491 - Avoid a double-marked-circuit warning that could happen when we
5492 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
5495 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
5496 - Reject version numbers with non-numeric prefixes (such as +, -, or
5497 whitespace). Disallowing whitespace prevents differential version
5498 parsing between POSIX-based and Windows platforms. Fixes bug 21507
5499 and part of 21508; bugfix on 0.0.8pre1.
5501 o Build features (backport from 0.3.1.5-alpha):
5502 - Tor's repository now includes a Travis Continuous Integration (CI)
5503 configuration file (.travis.yml). This is meant to help new
5504 developers and contributors who fork Tor to a Github repository be
5505 better able to test their changes, and understand what we expect
5506 to pass. To use this new build feature, you must fork Tor to your
5507 Github account, then go into the "Integrations" menu in the
5508 repository settings for your fork and enable Travis, then push
5509 your changes. Closes ticket 22636.
5512 Changes in version 0.3.0.11 - 2017-09-18
5513 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
5516 Most significantly, it includes a fix for TROVE-2017-008, a
5517 security bug that affects hidden services running with the
5518 SafeLogging option disabled. For more information, see
5519 https://trac.torproject.org/projects/tor/ticket/23490
5521 o Minor features (code style, backport from 0.3.1.7):
5522 - Add "Falls through" comments to our codebase, in order to silence
5523 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
5524 Stieger. Closes ticket 22446.
5527 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5530 o Minor bugfixes (compilation, backport from 0.3.1.7):
5531 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
5532 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
5534 o Minor bugfixes (controller, backport from 0.3.1.7):
5535 - Do not crash when receiving a HSPOST command with an empty body.
5536 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
5537 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
5538 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
5540 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
5541 - When setting the maximum number of connections allowed by the OS,
5542 always allow some extra file descriptors for other files. Fixes
5543 bug 22797; bugfix on 0.2.0.10-alpha.
5545 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
5546 - Remove a forgotten debugging message when an introduction point
5547 successfully establishes a hidden service prop224 circuit with
5549 - Change three other log_warn() for an introduction point to
5550 protocol warnings, because they can be failure from the network
5551 and are not relevant to the operator. Fixes bug 23078; bugfix on
5552 0.3.0.1-alpha and 0.3.0.2-alpha.
5555 Changes in version 0.3.1.7 - 2017-09-18
5556 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
5558 With the 0.3.1 series, Tor now serves and downloads directory
5559 information in more compact formats, to save on bandwidth overhead. It
5560 also contains a new padding system to resist netflow-based traffic
5561 analysis, and experimental support for building parts of Tor in Rust
5562 (though no parts of Tor are in Rust yet). There are also numerous
5563 small features, bugfixes on earlier release series, and groundwork for
5564 the hidden services revamp of 0.3.2.
5566 This release also includes a fix for TROVE-2017-008, a security bug
5567 that affects hidden services running with the SafeLogging option
5568 disabled. For more information, see
5569 https://trac.torproject.org/projects/tor/ticket/23490
5571 Per our stable release policy, we plan to support each stable release
5572 series for at least the next nine months, or for three months after
5573 the first stable release of the next series: whichever is longer. If
5574 you need a release with long-term support, we recommend that you stay
5575 with the 0.2.9 series.
5577 Below is a list of the changes since 0.3.1.6-rc. For a list of all
5578 changes since 0.3.0, see the ReleaseNotes file.
5580 o Major bugfixes (security, hidden services, loggging):
5581 - Fix a bug where we could log uninitialized stack when a certain
5582 hidden service error occurred while SafeLogging was disabled.
5583 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
5584 TROVE-2017-008 and CVE-2017-0380.
5586 o Minor features (defensive programming):
5587 - Create a pair of consensus parameters, nf_pad_tor2web and
5588 nf_pad_single_onion, to disable netflow padding in the consensus
5589 for non-anonymous connections in case the overhead is high. Closes
5592 o Minor features (diagnostic):
5593 - Add a stack trace to the bug warnings that can be logged when
5594 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
5595 attempt for bug 23105.
5597 o Minor features (geoip):
5598 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5601 o Minor bugfixes (compilation):
5602 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
5603 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
5605 o Minor bugfixes (controller):
5606 - Do not crash when receiving a HSPOST command with an empty body.
5607 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
5608 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
5609 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
5611 o Minor bugfixes (relay):
5612 - Inform the geoip and rephist modules about all requests, even on
5613 relays that are only fetching microdescriptors. Fixes a bug
5614 related to 21585; bugfix on 0.3.0.1-alpha.
5616 o Minor bugfixes (unit tests):
5617 - Fix a channelpadding unit test failure on slow systems by using
5618 mocked time instead of actual time. Fixes bug 23077; bugfix
5622 Changes in version 0.3.1.6-rc - 2017-09-05
5623 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
5624 release series, including a bug that produced weird behavior on
5625 Windows directory caches.
5627 This is the first release candidate in the Tor 0.3.1 series. If we
5628 find no new bugs or regressions here, the first stable 0.3.1 release
5629 will be nearly identical to it.
5631 o Major bugfixes (windows, directory cache):
5632 - On Windows, do not try to delete cached consensus documents and
5633 diffs before they are unmapped from memory--Windows won't allow
5634 that. Instead, allow the consensus cache directory to grow larger,
5635 to hold files that might need to stay around longer. Fixes bug
5636 22752; bugfix on 0.3.1.1-alpha.
5638 o Minor features (directory authority):
5639 - Improve the message that authorities report to relays that present
5640 RSA/Ed25519 keypairs that conflict with previously pinned keys.
5641 Closes ticket 22348.
5643 o Minor features (geoip):
5644 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
5647 o Minor features (testing):
5648 - Add more tests for compression backend initialization. Closes
5651 o Minor bugfixes (directory cache):
5652 - Fix a memory leak when recovering space in the consensus cache.
5653 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
5655 o Minor bugfixes (hidden service):
5656 - Increase the number of circuits that a service is allowed to
5657 open over a specific period of time. The value was lower than it
5658 should be (8 vs 12) in the normal case of 3 introduction points.
5659 Fixes bug 22159; bugfix on 0.3.0.5-rc.
5660 - Fix a BUG warning during HSv3 descriptor decoding that could be
5661 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
5662 on 0.3.0.1-alpha. Bug found by "haxxpop".
5663 - Rate-limit the log messages if we exceed the maximum number of
5664 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
5666 o Minor bugfixes (logging, relay):
5667 - Remove a forgotten debugging message when an introduction point
5668 successfully establishes a hidden service prop224 circuit with
5670 - Change three other log_warn() for an introduction point to
5671 protocol warnings, because they can be failure from the network
5672 and are not relevant to the operator. Fixes bug 23078; bugfix on
5673 0.3.0.1-alpha and 0.3.0.2-alpha.
5675 o Minor bugfixes (relay):
5676 - When a relay is not running as a directory cache, it will no
5677 longer generate compressed consensuses and consensus diff
5678 information. Previously, this was a waste of disk and CPU. Fixes
5679 bug 23275; bugfix on 0.3.1.1-alpha.
5681 o Minor bugfixes (robustness, error handling):
5682 - Improve our handling of the cases where OpenSSL encounters a
5683 memory error while encoding keys and certificates. We haven't
5684 observed these errors in the wild, but if they do happen, we now
5685 detect and respond better. Fixes bug 19418; bugfix on all versions
5686 of Tor. Reported by Guido Vranken.
5688 o Minor bugfixes (stability):
5689 - Avoid crashing on a double-free when unable to load or process an
5690 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
5691 with the clang static analyzer.
5693 o Minor bugfixes (testing):
5694 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5695 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5696 - Port the hs_ntor handshake test to work correctly with recent
5697 versions of the pysha3 module. Fixes bug 23071; bugfix
5700 o Minor bugfixes (Windows service):
5701 - When running as a Windows service, set the ID of the main thread
5702 correctly. Failure to do so made us fail to send log messages to
5703 the controller in 0.2.1.16-rc, slowed down controller event
5704 delivery in 0.2.7.3-rc and later, and crash with an assertion
5705 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
5706 Patch and diagnosis from "Vort".
5709 Changes in version 0.3.0.10 - 2017-08-02
5710 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
5711 from the current Tor alpha series. OpenBSD users and TPROXY users
5712 should upgrade; others are probably okay sticking with 0.3.0.9.
5714 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
5715 - Tor's repository now includes a Travis Continuous Integration (CI)
5716 configuration file (.travis.yml). This is meant to help new
5717 developers and contributors who fork Tor to a Github repository be
5718 better able to test their changes, and understand what we expect
5719 to pass. To use this new build feature, you must fork Tor to your
5720 Github account, then go into the "Integrations" menu in the
5721 repository settings for your fork and enable Travis, then push
5722 your changes. Closes ticket 22636.
5724 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
5725 - Fix a typo that had prevented TPROXY-based transparent proxying
5726 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
5727 Patch from "d4fq0fQAgoJ".
5729 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
5730 - Avoid an assertion failure bug affecting our implementation of
5731 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5732 handling of "0xbar" differs from what we had expected. Fixes bug
5733 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5735 o Minor features (backport from 0.3.1.5-alpha):
5736 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
5739 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
5740 - Roll over monthly accounting at the configured hour and minute,
5741 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
5742 Found by Andrey Karpov with PVS-Studio.
5744 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
5745 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
5746 bugfix on 0.2.8.1-alpha.
5747 - Fix warnings when building with libscrypt and openssl scrypt
5748 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
5749 - When building with certain versions of the mingw C header files,
5750 avoid float-conversion warnings when calling the C functions
5751 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
5754 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
5755 - Backport a fix for an "unused variable" warning that appeared
5756 in some versions of mingw. Fixes bug 22838; bugfix on
5759 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
5760 - Avoid Coverity build warnings related to our BUG() macro. By
5761 default, Coverity treats BUG() as the Linux kernel does: an
5762 instant abort(). We need to override that so our BUG() macro
5763 doesn't prevent Coverity from analyzing functions that use it.
5764 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
5766 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
5767 - When rejecting a router descriptor for running an obsolete version
5768 of Tor without ntor support, warn about the obsolete tor version,
5769 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
5771 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
5772 - Avoid a sandbox failure when trying to re-bind to a socket and
5773 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
5775 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
5776 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
5777 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
5780 Changes in version 0.3.1.5-alpha - 2017-08-01
5781 Tor 0.3.1.5-alpha improves the performance of consensus diff
5782 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
5783 several other bugs. If no serious bugs are found in this version, the
5784 next version will be a release candidate.
5786 This release also marks the end of support for the Tor 0.2.4.x,
5787 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
5788 further bug or security fixes. Anyone still running or distributing
5789 one of those versions should upgrade.
5791 o Major features (build system, continuous integration):
5792 - Tor's repository now includes a Travis Continuous Integration (CI)
5793 configuration file (.travis.yml). This is meant to help new
5794 developers and contributors who fork Tor to a Github repository be
5795 better able to test their changes, and understand what we expect
5796 to pass. To use this new build feature, you must fork Tor to your
5797 Github account, then go into the "Integrations" menu in the
5798 repository settings for your fork and enable Travis, then push
5799 your changes. Closes ticket 22636.
5801 o Major bugfixes (openbsd, denial-of-service):
5802 - Avoid an assertion failure bug affecting our implementation of
5803 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5804 handling of "0xbar" differs from what we had expected. Fixes bug
5805 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5807 o Major bugfixes (relay, performance):
5808 - Perform circuit handshake operations at a higher priority than we
5809 use for consensus diff creation and compression. This should
5810 prevent circuits from starving when a relay or bridge receives a
5811 new consensus, especially on lower-powered machines. Fixes bug
5812 22883; bugfix on 0.3.1.1-alpha.
5814 o Minor features (bridge authority):
5815 - Add "fingerprint" lines to the networkstatus-bridges file produced
5816 by bridge authorities. Closes ticket 22207.
5818 o Minor features (directory cache, consensus diff):
5819 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
5820 operators with low-resource environments to adjust the number of
5821 consensuses they'll store and generate diffs from. Most cache
5822 operators should leave it unchanged. Helps to work around
5825 o Minor features (geoip):
5826 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
5829 o Minor features (relay, performance):
5830 - Always start relays with at least two worker threads, to prevent
5831 priority inversion on slow tasks. Part of the fix for bug 22883.
5832 - Allow background work to be queued with different priorities, so
5833 that a big pile of slow low-priority jobs will not starve out
5834 higher priority jobs. This lays the groundwork for a fix for
5837 o Minor bugfixes (build system, rust):
5838 - Fix a problem where Rust toolchains were not being found when
5839 building without --enable-cargo-online-mode, due to setting the
5840 $HOME environment variable instead of $CARGO_HOME. Fixes bug
5841 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
5843 o Minor bugfixes (compatibility, zstd):
5844 - Write zstd epilogues correctly when the epilogue requires
5845 reallocation of the output buffer, even with zstd 1.3.0.
5846 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
5847 22927; bugfix on 0.3.1.1-alpha.
5849 o Minor bugfixes (compilation warnings):
5850 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
5851 22915; bugfix on 0.2.8.1-alpha.
5852 - Fix warnings when building with libscrypt and openssl scrypt
5853 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
5854 - Compile correctly when both openssl 1.1.0 and libscrypt are
5855 detected. Previously this would cause an error. Fixes bug 22892;
5856 bugfix on 0.3.1.1-alpha.
5857 - When building with certain versions of the mingw C header files,
5858 avoid float-conversion warnings when calling the C functions
5859 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
5862 o Minor bugfixes (coverity build support):
5863 - Avoid Coverity build warnings related to our BUG() macro. By
5864 default, Coverity treats BUG() as the Linux kernel does: an
5865 instant abort(). We need to override that so our BUG() macro
5866 doesn't prevent Coverity from analyzing functions that use it.
5867 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
5869 o Minor bugfixes (directory authority):
5870 - When a directory authority rejects a descriptor or extrainfo with
5871 a given digest, mark that digest as undownloadable, so that we do
5872 not attempt to download it again over and over. We previously
5873 tried to avoid downloading such descriptors by other means, but we
5874 didn't notice if we accidentally downloaded one anyway. This
5875 behavior became problematic in 0.2.7.2-alpha, when authorities
5876 began pinning Ed25519 keys. Fixes bug 22349; bugfix
5879 o Minor bugfixes (error reporting, windows):
5880 - When formatting Windows error messages, use the English format to
5881 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
5884 o Minor bugfixes (file limits, osx):
5885 - When setting the maximum number of connections allowed by the OS,
5886 always allow some extra file descriptors for other files. Fixes
5887 bug 22797; bugfix on 0.2.0.10-alpha.
5889 o Minor bugfixes (linux seccomp2 sandbox):
5890 - Avoid a sandbox failure when trying to re-bind to a socket and
5891 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
5893 o Minor bugfixes (memory leaks):
5894 - Fix a small memory leak when validating a configuration that uses
5895 two or more AF_UNIX sockets for the same port type. Fixes bug
5896 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
5898 o Minor bugfixes (unit tests):
5899 - test_consdiff_base64cmp would fail on OS X because while OS X
5900 follows the standard of (less than zero/zero/greater than zero),
5901 it doesn't follow the convention of (-1/0/+1). Make the test
5902 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
5903 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
5904 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
5907 Changes in version 0.3.1.4-alpha - 2017-06-29
5908 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
5909 to use a guard that was in the same network family as a chosen exit
5910 relay. This is a security regression; all clients running earlier
5911 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
5914 This release also fixes several other bugs introduced in 0.3.0.x
5915 and 0.3.1.x, including others that can affect bandwidth usage
5919 - To build with zstd and lzma support, Tor now requires the
5920 pkg-config tool at build time. (This requirement was new in
5921 0.3.1.1-alpha, but was not noted at the time. Noting it here to
5922 close ticket 22623.)
5924 o Major bugfixes (path selection, security):
5925 - When choosing which guard to use for a circuit, avoid the exit's
5926 family along with the exit itself. Previously, the new guard
5927 selection logic avoided the exit, but did not consider its family.
5928 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
5929 006 and CVE-2017-0377.
5931 o Major bugfixes (compression, zstd):
5932 - Correctly detect a full buffer when decompressing a large zstd-
5933 compressed input. Previously, we would sometimes treat a full
5934 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
5936 o Major bugfixes (directory protocol):
5937 - Ensure that we send "304 Not modified" as HTTP status code when a
5938 client is attempting to fetch a consensus or consensus diff, and
5939 the best one we can send them is one they already have. Fixes bug
5940 22702; bugfix on 0.3.1.1-alpha.
5942 o Major bugfixes (entry guards):
5943 - When starting with an old consensus, do not add new entry guards
5944 unless the consensus is "reasonably live" (under 1 day old). Fixes
5945 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
5947 o Minor features (bug mitigation, diagnostics, logging):
5948 - Avoid an assertion failure, and log a better error message, when
5949 unable to remove a file from the consensus cache on Windows.
5950 Attempts to mitigate and diagnose bug 22752.
5952 o Minor features (geoip):
5953 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
5956 o Minor bugfixes (compression):
5957 - When compressing or decompressing a buffer, check for a failure to
5958 create a compression object. Fixes bug 22626; bugfix
5960 - When decompressing a buffer, check for extra data after the end of
5961 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
5962 - When decompressing an object received over an anonymous directory
5963 connection, if we have already decompressed it using an acceptable
5964 compression method, do not reject it for looking like an
5965 unacceptable compression method. Fixes part of bug 22670; bugfix
5967 - When serving directory votes compressed with zlib, do not claim to
5968 have compressed them with zstd. Fixes bug 22669; bugfix
5970 - When spooling compressed data to an output buffer, don't try to
5971 spool more data when there is no more data to spool and we are not
5972 trying to flush the input. Previously, we would sometimes launch
5973 compression requests with nothing to do, which interferes with our
5974 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
5976 o Minor bugfixes (defensive programming):
5977 - Detect and break out of infinite loops in our compression code. We
5978 don't think that any such loops exist now, but it's best to be
5979 safe. Closes ticket 22672.
5980 - Fix a memset() off the end of an array when packing cells. This
5981 bug should be harmless in practice, since the corrupted bytes are
5982 still in the same structure, and are always padding bytes,
5983 ignored, or immediately overwritten, depending on compiler
5984 behavior. Nevertheless, because the memset()'s purpose is to make
5985 sure that any other cell-handling bugs can't expose bytes to the
5986 network, we need to fix it. Fixes bug 22737; bugfix on
5987 0.2.4.11-alpha. Fixes CID 1401591.
5989 o Minor bugfixes (linux seccomp2 sandbox):
5990 - Permit the fchmod system call, to avoid crashing on startup when
5991 starting with the seccomp2 sandbox and an unexpected set of
5992 permissions on the data directory or its contents. Fixes bug
5993 22516; bugfix on 0.2.5.4-alpha.
5994 - Fix a crash in the LZMA module, when the sandbox was enabled, and
5995 liblzma would allocate more than 16 MB of memory. We solve this by
5996 bumping the mprotect() limit in the sandbox module from 16 MB to
5997 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
5999 o Minor bugfixes (logging):
6000 - When decompressing, do not warn if we fail to decompress using a
6001 compression method that we merely guessed. Fixes part of bug
6002 22670; bugfix on 0.1.1.14-alpha.
6003 - When decompressing, treat mismatch between content-encoding and
6004 actual compression type as a protocol warning. Fixes part of bug
6005 22670; bugfix on 0.1.1.9-alpha.
6006 - Downgrade "assigned_to_cpuworker failed" message to info-level
6007 severity. In every case that can reach it, either a better warning
6008 has already been logged, or no warning is warranted. Fixes bug
6009 22356; bugfix on 0.2.6.3-alpha.
6010 - Demote a warn that was caused by libevent delays to info if
6011 netflow padding is less than 4.5 seconds late, or to notice
6012 if it is more (4.5 seconds is the amount of time that a netflow
6013 record might be emitted after, if we chose the maximum timeout).
6014 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
6016 o Minor bugfixes (process behavior):
6017 - When exiting because of an error, always exit with a nonzero exit
6018 status. Previously, we would fail to report an error in our exit
6019 status in cases related to __OwningControllerProcess failure,
6020 lockfile contention, and Ed25519 key initialization. Fixes bug
6021 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
6022 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
6026 - Add a manpage description for the key-pinning-journal file. Closes
6028 - Correctly note that bandwidth accounting values are stored in the
6029 state file, and the bw_accounting file is now obsolete. Closes
6031 - Document more of the files in the Tor data directory, including
6032 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
6033 approved-routers, sr-random, and diff-cache. Found while fixing
6037 Changes in version 0.3.0.9 - 2017-06-29
6038 Tor 0.3.0.9 fixes a path selection bug that would allow a client
6039 to use a guard that was in the same network family as a chosen exit
6040 relay. This is a security regression; all clients running earlier
6041 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
6044 This release also backports several other bugfixes from the 0.3.1.x
6047 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
6048 - When choosing which guard to use for a circuit, avoid the exit's
6049 family along with the exit itself. Previously, the new guard
6050 selection logic avoided the exit, but did not consider its family.
6051 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
6052 006 and CVE-2017-0377.
6054 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
6055 - Don't block bootstrapping when a primary bridge is offline and we
6056 can't get its descriptor. Fixes bug 22325; fixes one case of bug
6057 21969; bugfix on 0.3.0.3-alpha.
6059 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
6060 - When starting with an old consensus, do not add new entry guards
6061 unless the consensus is "reasonably live" (under 1 day old). Fixes
6062 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
6064 o Minor features (geoip):
6065 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
6068 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
6069 - Reject version numbers with non-numeric prefixes (such as +, -, or
6070 whitespace). Disallowing whitespace prevents differential version
6071 parsing between POSIX-based and Windows platforms. Fixes bug 21507
6072 and part of 21508; bugfix on 0.0.8pre1.
6074 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
6075 - Permit the fchmod system call, to avoid crashing on startup when
6076 starting with the seccomp2 sandbox and an unexpected set of
6077 permissions on the data directory or its contents. Fixes bug
6078 22516; bugfix on 0.2.5.4-alpha.
6080 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
6081 - Fix a memset() off the end of an array when packing cells. This
6082 bug should be harmless in practice, since the corrupted bytes are
6083 still in the same structure, and are always padding bytes,
6084 ignored, or immediately overwritten, depending on compiler
6085 behavior. Nevertheless, because the memset()'s purpose is to make
6086 sure that any other cell-handling bugs can't expose bytes to the
6087 network, we need to fix it. Fixes bug 22737; bugfix on
6088 0.2.4.11-alpha. Fixes CID 1401591.
6091 Changes in version 0.3.1.3-alpha - 2017-06-08
6092 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
6093 remotely crash a hidden service with an assertion failure. Anyone
6094 running a hidden service should upgrade to this version, or to some
6095 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
6097 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
6098 that sometimes made relays unreliable, as well as several other
6099 bugfixes described below.
6101 o Major bugfixes (hidden service, relay, security):
6102 - Fix a remotely triggerable assertion failure when a hidden service
6103 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
6104 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
6105 - Fix a remotely triggerable assertion failure caused by receiving a
6106 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6107 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6110 o Major bugfixes (relay, link handshake):
6111 - When performing the v3 link handshake on a TLS connection, report
6112 that we have the x509 certificate that we actually used on that
6113 connection, even if we have changed certificates since that
6114 connection was first opened. Previously, we would claim to have
6115 used our most recent x509 link certificate, which would sometimes
6116 make the link handshake fail. Fixes one case of bug 22460; bugfix
6119 o Major bugfixes (relays, key management):
6120 - Regenerate link and authentication certificates whenever the key
6121 that signs them changes; also, regenerate link certificates
6122 whenever the signed key changes. Previously, these processes were
6123 only weakly coupled, and we relays could (for minutes to hours)
6124 wind up with an inconsistent set of keys and certificates, which
6125 other relays would not accept. Fixes two cases of bug 22460;
6126 bugfix on 0.3.0.1-alpha.
6127 - When sending an Ed25519 signing->link certificate in a CERTS cell,
6128 send the certificate that matches the x509 certificate that we
6129 used on the TLS connection. Previously, there was a race condition
6130 if the TLS context rotated after we began the TLS handshake but
6131 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
6134 o Major bugfixes (torrc, crash):
6135 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
6136 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
6138 o Minor features (code style):
6139 - Add "Falls through" comments to our codebase, in order to silence
6140 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6141 Stieger. Closes ticket 22446.
6143 o Minor features (diagnostic):
6144 - Add logging messages to try to diagnose a rare bug that seems to
6145 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
6146 think this is happening because of incorrect system clocks, but
6147 we'd like to know for certain. Diagnostic for bug 22466.
6149 o Minor bugfixes (correctness):
6150 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6151 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6153 o Minor bugfixes (directory protocol):
6154 - Check for libzstd >= 1.1, because older versions lack the
6155 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
6157 o Minor bugfixes (link handshake):
6158 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
6159 months, and regenerate it when it is within one month of expiring.
6160 Previously, we had generated this certificate at startup with a
6161 ten-year lifetime, but that could lead to weird behavior when Tor
6162 was started with a grossly inaccurate clock. Mitigates bug 22466;
6163 mitigation on 0.3.0.1-alpha.
6165 o Minor bugfixes (storage directories):
6166 - Always check for underflows in the cached storage directory usage.
6167 If the usage does underflow, re-calculate it. Also, avoid a
6168 separate underflow when the usage is not known. Fixes bug 22424;
6169 bugfix on 0.3.1.1-alpha.
6171 o Minor bugfixes (unit tests):
6172 - The unit tests now pass on systems where localhost is misconfigured
6173 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
6177 - Clarify the manpage for the (deprecated) torify script. Closes
6180 Changes in version 0.3.0.8 - 2017-06-08
6181 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
6182 remotely crash a hidden service with an assertion failure. Anyone
6183 running a hidden service should upgrade to this version, or to some
6184 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
6186 Tor 0.3.0.8 also includes fixes for several key management bugs
6187 that sometimes made relays unreliable, as well as several other
6188 bugfixes described below.
6190 o Major bugfixes (hidden service, relay, security, backport
6191 from 0.3.1.3-alpha):
6192 - Fix a remotely triggerable assertion failure when a hidden service
6193 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
6194 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
6195 - Fix a remotely triggerable assertion failure caused by receiving a
6196 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6197 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6200 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
6201 - When performing the v3 link handshake on a TLS connection, report
6202 that we have the x509 certificate that we actually used on that
6203 connection, even if we have changed certificates since that
6204 connection was first opened. Previously, we would claim to have
6205 used our most recent x509 link certificate, which would sometimes
6206 make the link handshake fail. Fixes one case of bug 22460; bugfix
6209 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
6210 - Regenerate link and authentication certificates whenever the key
6211 that signs them changes; also, regenerate link certificates
6212 whenever the signed key changes. Previously, these processes were
6213 only weakly coupled, and we relays could (for minutes to hours)
6214 wind up with an inconsistent set of keys and certificates, which
6215 other relays would not accept. Fixes two cases of bug 22460;
6216 bugfix on 0.3.0.1-alpha.
6217 - When sending an Ed25519 signing->link certificate in a CERTS cell,
6218 send the certificate that matches the x509 certificate that we
6219 used on the TLS connection. Previously, there was a race condition
6220 if the TLS context rotated after we began the TLS handshake but
6221 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
6224 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
6225 - Stop rejecting v3 hidden service descriptors because their size
6226 did not match an old padding rule. Fixes bug 22447; bugfix on
6229 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6230 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6231 December 2016 (of which ~126 were still functional) with a list of
6232 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6233 2017. Resolves ticket 21564.
6235 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
6236 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
6237 bug 22252; bugfix on 0.2.9.3-alpha.
6239 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
6240 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6241 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6243 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
6244 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
6245 months, and regenerate it when it is within one month of expiring.
6246 Previously, we had generated this certificate at startup with a
6247 ten-year lifetime, but that could lead to weird behavior when Tor
6248 was started with a grossly inaccurate clock. Mitigates bug 22466;
6249 mitigation on 0.3.0.1-alpha.
6251 o Minor bugfixes (memory leak, directory authority, backport from
6253 - When directory authorities reject a router descriptor due to
6254 keypinning, free the router descriptor rather than leaking the
6255 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
6258 Changes in version 0.2.9.11 - 2017-06-08
6259 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
6260 remotely crash a hidden service with an assertion failure. Anyone
6261 running a hidden service should upgrade to this version, or to some
6262 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6263 are not affected by TROVE-2017-004.)
6265 Tor 0.2.9.11 also backports fixes for several key management bugs
6266 that sometimes made relays unreliable, as well as several other
6267 bugfixes described below.
6269 o Major bugfixes (hidden service, relay, security, backport
6270 from 0.3.1.3-alpha):
6271 - Fix a remotely triggerable assertion failure caused by receiving a
6272 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6273 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6276 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
6277 - When performing the v3 link handshake on a TLS connection, report
6278 that we have the x509 certificate that we actually used on that
6279 connection, even if we have changed certificates since that
6280 connection was first opened. Previously, we would claim to have
6281 used our most recent x509 link certificate, which would sometimes
6282 make the link handshake fail. Fixes one case of bug 22460; bugfix
6285 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6286 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6287 December 2016 (of which ~126 were still functional) with a list of
6288 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6289 2017. Resolves ticket 21564.
6291 o Minor features (future-proofing, backport from 0.3.0.7):
6292 - Tor no longer refuses to download microdescriptors or descriptors if
6293 they are listed as "published in the future". This change will
6294 eventually allow us to stop listing meaningful "published" dates
6295 in microdescriptor consensuses, and thereby allow us to reduce the
6296 resources required to download consensus diffs by over 50%.
6297 Implements part of ticket 21642; implements part of proposal 275.
6299 o Minor features (directory authorities, backport from 0.3.0.4-rc)
6300 - Directory authorities now reject relays running versions
6301 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
6302 suffer from bug 20499 and don't keep their consensus cache
6303 up-to-date. Resolves ticket 20509.
6305 o Minor features (geoip):
6306 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6309 o Minor bugfixes (control port, backport from 0.3.0.6):
6310 - The GETINFO extra-info/digest/<digest> command was broken because
6311 of a wrong base16 decode return value check, introduced when
6312 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
6314 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
6315 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6316 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6318 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
6319 - The getpid() system call is now permitted under the Linux seccomp2
6320 sandbox, to avoid crashing with versions of OpenSSL (and other
6321 libraries) that attempt to learn the process's PID by using the
6322 syscall rather than the VDSO code. Fixes bug 21943; bugfix
6325 o Minor bugfixes (memory leak, directory authority, backport
6326 from 0.3.1.2-alpha):
6327 - When directory authorities reject a router descriptor due to
6328 keypinning, free the router descriptor rather than leaking the
6329 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
6331 Changes in version 0.2.8.14 - 2017-06-08
6332 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
6333 remotely crash a hidden service with an assertion failure. Anyone
6334 running a hidden service should upgrade to this version, or to some
6335 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6336 are not affected by TROVE-2017-004.)
6338 o Major bugfixes (hidden service, relay, security):
6339 - Fix a remotely triggerable assertion failure caused by receiving a
6340 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6341 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6344 o Minor features (geoip):
6345 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6348 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6349 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6350 December 2016 (of which ~126 were still functional) with a list of
6351 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6352 2017. Resolves ticket 21564.
6354 o Minor bugfixes (correctness):
6355 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6356 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6358 Changes in version 0.2.7.8 - 2017-06-08
6359 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
6360 remotely crash a hidden service with an assertion failure. Anyone
6361 running a hidden service should upgrade to this version, or to some
6362 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6363 are not affected by TROVE-2017-004.)
6365 o Major bugfixes (hidden service, relay, security):
6366 - Fix a remotely triggerable assertion failure caused by receiving a
6367 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6368 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6371 o Minor features (geoip):
6372 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6375 o Minor bugfixes (correctness):
6376 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6377 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6380 Changes in version 0.2.6.12 - 2017-06-08
6381 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
6382 remotely crash a hidden service with an assertion failure. Anyone
6383 running a hidden service should upgrade to this version, or to some
6384 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6385 are not affected by TROVE-2017-004.)
6387 o Major bugfixes (hidden service, relay, security):
6388 - Fix a remotely triggerable assertion failure caused by receiving a
6389 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6390 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6393 o Minor features (geoip):
6394 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6397 o Minor bugfixes (correctness):
6398 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6399 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6401 Changes in version 0.2.5.14 - 2017-06-08
6402 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
6403 remotely crash a hidden service with an assertion failure. Anyone
6404 running a hidden service should upgrade to this version, or to some
6405 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6406 are not affected by TROVE-2017-004.)
6408 o Major bugfixes (hidden service, relay, security):
6409 - Fix a remotely triggerable assertion failure caused by receiving a
6410 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6411 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6414 o Minor features (geoip):
6415 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6418 o Minor bugfixes (correctness):
6419 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6420 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6422 Changes in version 0.2.4.29 - 2017-06-08
6423 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
6424 remotely crash a hidden service with an assertion failure. Anyone
6425 running a hidden service should upgrade to this version, or to some
6426 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6427 are not affected by TROVE-2017-004.)
6429 o Major bugfixes (hidden service, relay, security):
6430 - Fix a remotely triggerable assertion failure caused by receiving a
6431 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6432 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6435 o Minor features (geoip):
6436 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6439 o Minor bugfixes (correctness):
6440 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6441 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6444 Changes in version 0.3.1.2-alpha - 2017-05-26
6445 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
6446 fixes a few bugs found while testing 0.3.1.1-alpha, including a
6447 memory corruption bug that affected relay stability.
6449 o Major bugfixes (crash, relay):
6450 - Fix a memory-corruption bug in relays that set MyFamily.
6451 Previously, they would double-free MyFamily elements when making
6452 the next descriptor or when changing their configuration. Fixes
6453 bug 22368; bugfix on 0.3.1.1-alpha.
6455 o Minor bugfixes (logging):
6456 - Log a better message when a directory authority replies to an
6457 upload with an unexpected status code. Fixes bug 11121; bugfix
6460 o Minor bugfixes (memory leak, directory authority):
6461 - When directory authorities reject a router descriptor due to
6462 keypinning, free the router descriptor rather than leaking the
6463 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
6466 Changes in version 0.3.1.1-alpha - 2017-05-22
6467 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
6468 reduces the bandwidth usage for Tor's directory protocol, adds some
6469 basic padding to resist netflow-based traffic analysis and to serve as
6470 the basis of other padding in the future, and adds rust support to the
6473 It also contains numerous other small features and improvements to
6474 security, correctness, and performance.
6476 Below are the changes since 0.3.0.7.
6478 o Major features (directory protocol):
6479 - Tor relays and authorities can now serve clients an abbreviated
6480 version of the consensus document, containing only the changes
6481 since an older consensus document that the client holds. Clients
6482 now request these documents when available. When both client and
6483 server use this new protocol, they will use far less bandwidth (up
6484 to 94% less) to keep the client's consensus up-to-date. Implements
6485 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
6486 - Tor can now compress directory traffic with lzma or with zstd
6487 compression algorithms, which can deliver better bandwidth
6488 performance. Because lzma is computationally expensive, it's only
6489 used for documents that can be compressed once and served many
6490 times. Support for these algorithms requires that tor is built
6491 with the libzstd and/or liblzma libraries available. Implements
6492 proposal 278; closes ticket 21662.
6493 - Relays now perform the more expensive compression operations, and
6494 consensus diff generation, in worker threads. This separation
6495 avoids delaying the main thread when a new consensus arrives.
6497 o Major features (experimental):
6498 - Tor can now build modules written in Rust. To turn this on, pass
6499 the "--enable-rust" flag to the configure script. It's not time to
6500 get excited yet: currently, there is no actual Rust functionality
6501 beyond some simple glue code, and a notice at startup to tell you
6502 that Rust is running. Still, we hope that programmers and
6503 packagers will try building Tor with Rust support, so that we can
6504 find issues and solve portability problems. Closes ticket 22106.
6506 o Major features (traffic analysis resistance):
6507 - Connections between clients and relays now send a padding cell in
6508 each direction every 1.5 to 9.5 seconds (tunable via consensus
6509 parameters). This padding will not resist specialized
6510 eavesdroppers, but it should be enough to make many ISPs' routine
6511 network flow logging less useful in traffic analysis against
6514 Padding is negotiated using Tor's link protocol, so both relays
6515 and clients must upgrade for this to take effect. Clients may
6516 still send padding despite the relay's version by setting
6517 ConnectionPadding 1 in torrc, and may disable padding by setting
6518 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
6519 users with the torrc option ReducedConnectionPadding. Implements
6520 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
6521 - Relays will publish 24 hour totals of padding and non-padding cell
6522 counts to their extra-info descriptors, unless PaddingStatistics 0
6523 is set in torrc. These 24 hour totals are also rounded to
6526 o Major bugfixes (connection usage):
6527 - We use NETINFO cells to try to determine if both relays involved
6528 in a connection will agree on the canonical status of that
6529 connection. We prefer the connections where this is the case for
6530 extend cells, and try to close connections where relays disagree
6531 on their canonical status early. Also, we now prefer the oldest
6532 valid connection for extend cells. These two changes should reduce
6533 the number of long-term connections that are kept open between
6534 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
6535 - Relays now log hourly statistics (look for
6536 "channel_check_for_duplicates" lines) on the total number of
6537 connections to other relays. If the number of connections per
6538 relay is unexpectedly large, this log message is at notice level.
6539 Otherwise it is at info.
6541 o Major bugfixes (entry guards):
6542 - Don't block bootstrapping when a primary bridge is offline and we
6543 can't get its descriptor. Fixes bug 22325; fixes one case of bug
6544 21969; bugfix on 0.3.0.3-alpha.
6546 o Major bugfixes (linux TPROXY support):
6547 - Fix a typo that had prevented TPROXY-based transparent proxying
6548 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
6549 Patch from "d4fq0fQAgoJ".
6551 o Minor features (security, windows):
6552 - Enable a couple of pieces of Windows hardening: one
6553 (HeapEnableTerminationOnCorruption) that has been on-by-default
6554 since Windows 8, and unavailable before Windows 7; and one
6555 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6556 affect us, but shouldn't do any harm. Closes ticket 21953.
6558 o Minor features (config options):
6559 - Allow "%include" directives in torrc configuration files. These
6560 directives import the settings from other files, or from all the
6561 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
6562 - Make SAVECONF return an error when overwriting a torrc that has
6563 includes. Using SAVECONF with the FORCE option will allow it to
6564 overwrite torrc even if includes are used. Related to ticket 1922.
6565 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
6566 will work without the FORCE option. Related to ticket 1922.
6568 o Minor features (controller):
6569 - Warn the first time that a controller requests data in the long-
6570 deprecated 'GETINFO network-status' format. Closes ticket 21703.
6572 o Minor features (defaults):
6573 - The default value for UseCreateFast is now 0: clients which
6574 haven't yet received a consensus document will now use a proper
6575 ntor handshake to talk to their directory servers whenever they
6576 can. Closes ticket 21407.
6577 - Onion key rotation and expiry intervals are now defined as a
6578 network consensus parameter, per proposal 274. The default
6579 lifetime of an onion key is increased from 7 to 28 days. Old onion
6580 keys will expire after 7 days by default. This change will make
6581 consensus diffs much smaller, and save significant bandwidth.
6582 Closes ticket 21641.
6584 o Minor features (fallback directory list):
6585 - Update the fallback directory mirror whitelist and blacklist based
6586 on operator emails. Closes task 21121.
6587 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6588 December 2016 (of which ~126 were still functional) with a list of
6589 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6590 2017. Resolves ticket 21564.
6592 o Minor features (hidden services, logging):
6593 - Log a message when a hidden service descriptor has fewer
6594 introduction points than specified in
6595 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
6596 - Log a message when a hidden service reaches its introduction point
6597 circuit limit, and when that limit is reset. Follow up to ticket
6598 21594; closes ticket 21622.
6599 - Warn user if multiple entries in EntryNodes and at least one
6600 HiddenService are used together. Pinning EntryNodes along with a
6601 hidden service can be possibly harmful; for instance see ticket
6602 14917 or 21155. Closes ticket 21155.
6604 o Minor features (linux seccomp2 sandbox):
6605 - We now have a document storage backend compatible with the Linux
6606 seccomp2 sandbox. This backend is used for consensus documents and
6607 diffs between them; in the long term, we'd like to use it for
6608 unparseable directory material too. Closes ticket 21645
6609 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
6610 from 1MB to 16MB. This was necessary with the glibc allocator in
6611 order to allow worker threads to allocate more memory -- which in
6612 turn is necessary because of our new use of worker threads for
6613 compression. Closes ticket 22096.
6615 o Minor features (logging):
6616 - Log files are no longer created world-readable by default.
6617 (Previously, most distributors would store the logs in a non-
6618 world-readable location to prevent inappropriate access. This
6619 change is an extra precaution.) Closes ticket 21729; patch
6622 o Minor features (performance):
6623 - Our Keccak (SHA-3) implementation now accesses memory more
6624 efficiently, especially on little-endian systems. Closes
6626 - Add an O(1) implementation of channel_find_by_global_id(), to
6627 speed some controller functions.
6629 o Minor features (relay, configuration):
6630 - The MyFamily option may now be repeated as many times as desired,
6631 for relays that want to configure large families. Closes ticket
6632 4998; patch by Daniel Pinto.
6634 o Minor features (safety):
6635 - Add an explicit check to extrainfo_parse_entry_from_string() for
6636 NULL inputs. We don't believe this can actually happen, but it may
6637 help silence a warning from the Clang analyzer. Closes
6640 o Minor features (testing):
6641 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
6642 When Tor is compiled with this option, we disable a number of
6643 redundant memory-safety failsafes that are intended to stop bugs
6644 from becoming security issues. This makes it easier to hunt for
6645 bugs that would be security issues without the failsafes turned
6646 on. Closes ticket 21439.
6647 - Add a general event-tracing instrumentation support to Tor. This
6648 subsystem will enable developers and researchers to add fine-
6649 grained instrumentation to their Tor instances, for use when
6650 examining Tor network performance issues. There are no trace
6651 events yet, and event-tracing is off by default unless enabled at
6652 compile time. Implements ticket 13802.
6653 - Improve our version parsing tests: add tests for typical version
6654 components, add tests for invalid versions, including numeric
6655 range and non-numeric prefixes. Unit tests 21278, 21450, and
6656 21507. Partially implements 21470.
6658 o Minor bugfixes (bandwidth accounting):
6659 - Roll over monthly accounting at the configured hour and minute,
6660 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
6661 Found by Andrey Karpov with PVS-Studio.
6663 o Minor bugfixes (code correctness):
6664 - Accurately identify client connections by their lack of peer
6665 authentication. This means that we bail out earlier if asked to
6666 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
6669 o Minor bugfixes (configuration):
6670 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
6671 bug 22252; bugfix on 0.2.9.3-alpha.
6673 o Minor bugfixes (connection lifespan):
6674 - Allow more control over how long TLS connections are kept open:
6675 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
6676 single option called CircuitsAvailableTimeout. Also, allow the
6677 consensus to control the default values for both this preference
6678 and the lifespan of relay-to-relay connections. Fixes bug 17592;
6679 bugfix on 0.2.5.5-alpha.
6680 - Increase the initial circuit build timeout testing frequency, to
6681 help ensure that ReducedConnectionPadding clients finish learning
6682 a timeout before their orconn would expire. The initial testing
6683 rate was set back in the days of TAP and before the Tor Browser
6684 updater, when we had to be much more careful about new clients
6685 making lots of circuits. With this change, a circuit build timeout
6686 is learned in about 15-20 minutes, instead of 100-120 minutes.
6688 o Minor bugfixes (controller):
6689 - GETINFO onions/current and onions/detached no longer respond with
6690 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
6691 - Trigger HS descriptor events on the control port when the client
6692 fails to pick a hidden service directory for a hidden service.
6693 This can happen if all the hidden service directories are in
6694 ExcludeNodes, or they have all been queried within the last 15
6695 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
6697 o Minor bugfixes (directory authority):
6698 - When rejecting a router descriptor for running an obsolete version
6699 of Tor without ntor support, warn about the obsolete tor version,
6700 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
6701 - Prevent the shared randomness subsystem from asserting when
6702 initialized by a bridge authority with an incomplete configuration
6703 file. Fixes bug 21586; bugfix on 0.2.9.8.
6705 o Minor bugfixes (exit-side DNS):
6706 - Fix an untriggerable assertion that checked the output of a
6707 libevent DNS error, so that the assertion actually behaves as
6708 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
6709 Karpov using PVS-Studio.
6711 o Minor bugfixes (fallback directories):
6712 - Make the usage example in updateFallbackDirs.py actually work, and
6713 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
6714 - Decrease the guard flag average required to be a fallback. This
6715 allows us to keep relays that have their guard flag removed when
6716 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
6717 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
6718 bugfix on 0.2.8.1-alpha.
6719 - Make sure fallback directory mirrors have the same address, port,
6720 and relay identity key for at least 30 days before they are
6721 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
6723 o Minor bugfixes (hidden services):
6724 - Stop printing a cryptic warning when a hidden service gets a
6725 request to connect to a virtual port that it hasn't configured.
6726 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
6727 - Simplify hidden service descriptor creation by using an existing
6728 flag to check if an introduction point is established. Fixes bug
6729 21599; bugfix on 0.2.7.2-alpha.
6731 o Minor bugfixes (memory leak):
6732 - Fix a small memory leak at exit from the backtrace handler code.
6733 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
6735 o Minor bugfixes (protocol, logging):
6736 - Downgrade a log statement about unexpected relay cells from "bug"
6737 to "protocol warning", because there is at least one use case
6738 where it can be triggered by a buggy tor implementation. Fixes bug
6739 21293; bugfix on 0.1.1.14-alpha.
6741 o Minor bugfixes (testing):
6742 - Use unbuffered I/O for utility functions around the
6743 process_handle_t type. This fixes unit test failures reported on
6744 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
6745 - Make display of captured unit test log messages consistent. Fixes
6746 bug 21510; bugfix on 0.2.9.3-alpha.
6747 - Make test-network.sh always call chutney's test-network.sh.
6748 Previously, this only worked on systems which had bash installed,
6749 due to some bash-specific code in the script. Fixes bug 19699;
6750 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
6752 o Minor bugfixes (voting consistency):
6753 - Reject version numbers with non-numeric prefixes (such as +, -, or
6754 whitespace). Disallowing whitespace prevents differential version
6755 parsing between POSIX-based and Windows platforms. Fixes bug 21507
6756 and part of 21508; bugfix on 0.0.8pre1.
6758 o Minor bugfixes (windows, relay):
6759 - Resolve "Failure from drain_fd: No error" warnings on Windows
6760 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
6762 o Code simplification and refactoring:
6763 - Break up the 630-line function connection_dir_client_reached_eof()
6764 into a dozen smaller functions. This change should help
6765 maintainability and readability of the client directory code.
6766 - Isolate our use of the openssl headers so that they are only
6767 included from our crypto wrapper modules, and from tests that
6768 examine those modules' internals. Closes ticket 21841.
6769 - Simplify our API to launch directory requests, making it more
6770 extensible and less error-prone. Now it's easier to add extra
6771 headers to directory requests. Closes ticket 21646.
6772 - Our base64 decoding functions no longer overestimate the output
6773 space that they need when parsing unpadded inputs. Closes
6775 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
6776 Resolves ticket 22213.
6777 - The logic that directory caches use to spool request to clients,
6778 serving them one part at a time so as not to allocate too much
6779 memory, has been refactored for consistency. Previously there was
6780 a separate spooling implementation per type of spoolable data. Now
6781 there is one common spooling implementation, with extensible data
6782 types. Closes ticket 21651.
6783 - Tor's compression module now supports multiple backends. Part of
6784 the implementation for proposal 278; closes ticket 21663.
6787 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
6788 Closes ticket 21873.
6789 - Correct documentation about the default DataDirectory value.
6790 Closes ticket 21151.
6791 - Document the default behavior of NumEntryGuards and
6792 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
6794 - Document key=value pluggable transport arguments for Bridge lines
6795 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
6796 - Note that bandwidth-limiting options don't affect TCP headers or
6797 DNS. Closes ticket 17170.
6799 o Removed features (configuration options, all in ticket 22060):
6800 - These configuration options are now marked Obsolete, and no longer
6801 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
6802 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
6803 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
6804 in 0.2.9.2-alpha and have now been removed. The previous default
6805 behavior is now always chosen; the previous (less secure) non-
6806 default behavior is now unavailable.
6807 - CloseHSClientCircuitsImmediatelyOnTimeout and
6808 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
6809 0.2.9.2-alpha and now have been removed. HS circuits never close
6810 on circuit build timeout; they have a longer timeout period.
6811 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
6812 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
6813 (and others) to configure listen-only and advertise-only addresses.
6815 o Removed features (tools):
6816 - We've removed the tor-checkkey tool from src/tools. Long ago, we
6817 used it to help people detect RSA keys that were generated by
6818 versions of Debian affected by CVE-2008-0166. But those keys have
6819 been out of circulation for ages, and this tool is no longer
6820 required. Closes ticket 21842.
6823 Changes in version 0.3.0.7 - 2017-05-15
6824 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
6825 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
6826 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
6827 clients are not affected.
6829 o Major bugfixes (hidden service directory, security):
6830 - Fix an assertion failure in the hidden service directory code, which
6831 could be used by an attacker to remotely cause a Tor relay process to
6832 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
6833 should upgrade. This security issue is tracked as TROVE-2017-002.
6834 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
6837 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6840 o Minor features (future-proofing):
6841 - Tor no longer refuses to download microdescriptors or descriptors
6842 if they are listed as "published in the future". This change will
6843 eventually allow us to stop listing meaningful "published" dates
6844 in microdescriptor consensuses, and thereby allow us to reduce the
6845 resources required to download consensus diffs by over 50%.
6846 Implements part of ticket 21642; implements part of proposal 275.
6848 o Minor bugfixes (Linux seccomp2 sandbox):
6849 - The getpid() system call is now permitted under the Linux seccomp2
6850 sandbox, to avoid crashing with versions of OpenSSL (and other
6851 libraries) that attempt to learn the process's PID by using the
6852 syscall rather than the VDSO code. Fixes bug 21943; bugfix
6856 Changes in version 0.3.0.6 - 2017-04-26
6857 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
6859 With the 0.3.0 series, clients and relays now use Ed25519 keys to
6860 authenticate their link connections to relays, rather than the old
6861 RSA1024 keys that they used before. (Circuit crypto has been
6862 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
6863 the guard selection and replacement algorithm to behave more robustly
6864 in the presence of unreliable networks, and to resist guard-
6867 This series also includes numerous other small features and bugfixes,
6868 along with more groundwork for the upcoming hidden-services revamp.
6870 Per our stable release policy, we plan to support the Tor 0.3.0
6871 release series for at least the next nine months, or for three months
6872 after the first stable release of the 0.3.1 series: whichever is
6873 longer. If you need a release with long-term support, we recommend
6874 that you stay with the 0.2.9 series.
6876 Below are the changes since 0.3.0.5-rc. For a list of all changes
6877 since 0.2.9, see the ReleaseNotes file.
6879 o Minor features (geoip):
6880 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
6883 o Minor bugfixes (control port):
6884 - The GETINFO extra-info/digest/<digest> command was broken because
6885 of a wrong base16 decode return value check, introduced when
6886 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
6888 o Minor bugfixes (crash prevention):
6889 - Fix a (currently untriggerable, but potentially dangerous) crash
6890 bug when base32-encoding inputs whose sizes are not a multiple of
6891 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
6894 Changes in version 0.3.0.5-rc - 2017-04-05
6895 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
6896 0.3.0 release series.
6898 This is the second release candidate in the Tor 0.3.0 series, and has
6899 much fewer changes than the first. If we find no new bugs or
6900 regressions here, the first stable 0.3.0 release will be nearly
6903 o Major bugfixes (crash, directory connections):
6904 - Fix a rare crash when sending a begin cell on a circuit whose
6905 linked directory connection had already been closed. Fixes bug
6906 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
6908 o Major bugfixes (guard selection):
6909 - Fix a guard selection bug where Tor would refuse to bootstrap in
6910 some cases if the user swapped a bridge for another bridge in
6911 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
6912 Reported by "torvlnt33r".
6914 o Minor features (geoip):
6915 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
6918 o Minor bugfix (compilation):
6919 - Fix a warning when compiling hs_service.c. Previously, it had no
6920 exported symbols when compiled for libor.a, resulting in a
6921 compilation warning from clang. Fixes bug 21825; bugfix
6924 o Minor bugfixes (hidden services):
6925 - Make hidden services check for failed intro point connections,
6926 even when they have exceeded their intro point creation limit.
6927 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
6928 - Make hidden services with 8 to 10 introduction points check for
6929 failed circuits immediately after startup. Previously, they would
6930 wait for 5 minutes before performing their first checks. Fixes bug
6931 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
6933 o Minor bugfixes (memory leaks):
6934 - Fix a memory leak when using GETCONF on a port option. Fixes bug
6935 21682; bugfix on 0.3.0.3-alpha.
6937 o Minor bugfixes (relay):
6938 - Avoid a double-marked-circuit warning that could happen when we
6939 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
6942 o Minor bugfixes (tests):
6943 - Run the entry_guard_parse_from_state_full() test with the time set
6944 to a specific date. (The guard state that this test was parsing
6945 contained guards that had expired since the test was first
6946 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
6949 - Update the description of the directory server options in the
6950 manual page, to clarify that a relay no longer needs to set
6951 DirPort in order to be a directory cache. Closes ticket 21720.
6955 Changes in version 0.2.8.13 - 2017-03-03
6956 Tor 0.2.8.13 backports a security fix from later Tor
6957 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
6958 this release, if for some reason they cannot upgrade to a later
6959 release series, and if they build Tor with the --enable-expensive-hardening
6962 Note that support for Tor 0.2.8.x is ending next year: we will not issue
6963 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
6964 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
6966 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
6967 - Fix an integer underflow bug when comparing malformed Tor
6968 versions. This bug could crash Tor when built with
6969 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
6970 0.2.9.8, which were built with -ftrapv by default. In other cases
6971 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
6972 on 0.0.8pre1. Found by OSS-Fuzz.
6974 o Minor features (geoip):
6975 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
6979 Changes in version 0.2.7.7 - 2017-03-03
6980 Tor 0.2.7.7 backports a number of security fixes from later Tor
6981 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
6982 this release, if for some reason they cannot upgrade to a later
6985 Note that support for Tor 0.2.7.x is ending this year: we will not issue
6986 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
6987 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
6989 o Directory authority changes (backport from 0.2.8.5-rc):
6990 - Urras is no longer a directory authority. Closes ticket 19271.
6992 o Directory authority changes (backport from 0.2.9.2-alpha):
6993 - The "Tonga" bridge authority has been retired; the new bridge
6994 authority is "Bifroest". Closes tickets 19728 and 19690.
6996 o Directory authority key updates (backport from 0.2.8.1-alpha):
6997 - Update the V3 identity key for the dannenberg directory authority:
6998 it was changed on 18 November 2015. Closes task 17906. Patch
7001 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7002 - Fix a bug in parsing that could cause clients to read a single
7003 byte past the end of an allocated region. This bug could be used
7004 to cause hardened clients (built with --enable-expensive-hardening)
7005 to crash if they tried to visit a hostile hidden service. Non-
7006 hardened clients are only affected depending on the details of
7007 their platform's memory allocator. Fixes bug 21018; bugfix on
7008 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7009 2016-12-002 and as CVE-2016-1254.
7011 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
7012 - Stop a crash that could occur when a client running with DNSPort
7013 received a query with multiple address types, and the first
7014 address type was not supported. Found and fixed by Scott Dial.
7015 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7016 - Prevent a class of security bugs caused by treating the contents
7017 of a buffer chunk as if they were a NUL-terminated string. At
7018 least one such bug seems to be present in all currently used
7019 versions of Tor, and would allow an attacker to remotely crash
7020 most Tor instances, especially those compiled with extra compiler
7021 hardening. With this defense in place, such bugs can't crash Tor,
7022 though we should still fix them as they occur. Closes ticket
7023 20384 (TROVE-2016-10-001).
7025 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7026 - Avoid a difficult-to-trigger heap corruption attack when extending
7027 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7028 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7029 Reported by Guido Vranken.
7031 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7032 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7033 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7035 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7036 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7037 pointer to the previous (uninitialized) key value. The impact here
7038 should be limited to a difficult-to-trigger crash, if OpenSSL is
7039 running an engine that makes key generation failures possible, or
7040 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7041 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7044 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7045 - Fix an integer underflow bug when comparing malformed Tor
7046 versions. This bug could crash Tor when built with
7047 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7048 0.2.9.8, which were built with -ftrapv by default. In other cases
7049 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7050 on 0.0.8pre1. Found by OSS-Fuzz.
7052 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7053 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7054 zero size. Check size argument to memwipe() for underflow. Fixes
7055 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7058 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7059 - Make Tor survive errors involving connections without a
7060 corresponding event object. Previously we'd fail with an
7061 assertion; now we produce a log message. Related to bug 16248.
7063 o Minor features (geoip):
7064 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7068 Changes in version 0.2.6.11 - 2017-03-03
7069 Tor 0.2.6.11 backports a number of security fixes from later Tor
7070 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
7071 this release, if for some reason they cannot upgrade to a later
7074 Note that support for Tor 0.2.6.x is ending this year: we will not issue
7075 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
7076 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7078 o Directory authority changes (backport from 0.2.8.5-rc):
7079 - Urras is no longer a directory authority. Closes ticket 19271.
7081 o Directory authority changes (backport from 0.2.9.2-alpha):
7082 - The "Tonga" bridge authority has been retired; the new bridge
7083 authority is "Bifroest". Closes tickets 19728 and 19690.
7085 o Directory authority key updates (backport from 0.2.8.1-alpha):
7086 - Update the V3 identity key for the dannenberg directory authority:
7087 it was changed on 18 November 2015. Closes task 17906. Patch
7090 o Major features (security fixes, backport from 0.2.9.4-alpha):
7091 - Prevent a class of security bugs caused by treating the contents
7092 of a buffer chunk as if they were a NUL-terminated string. At
7093 least one such bug seems to be present in all currently used
7094 versions of Tor, and would allow an attacker to remotely crash
7095 most Tor instances, especially those compiled with extra compiler
7096 hardening. With this defense in place, such bugs can't crash Tor,
7097 though we should still fix them as they occur. Closes ticket
7098 20384 (TROVE-2016-10-001).
7100 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7101 - Fix a bug in parsing that could cause clients to read a single
7102 byte past the end of an allocated region. This bug could be used
7103 to cause hardened clients (built with --enable-expensive-hardening)
7104 to crash if they tried to visit a hostile hidden service. Non-
7105 hardened clients are only affected depending on the details of
7106 their platform's memory allocator. Fixes bug 21018; bugfix on
7107 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7108 2016-12-002 and as CVE-2016-1254.
7110 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
7111 - Stop a crash that could occur when a client running with DNSPort
7112 received a query with multiple address types, and the first
7113 address type was not supported. Found and fixed by Scott Dial.
7114 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7116 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7117 - Fix an error that could cause us to read 4 bytes before the
7118 beginning of an openssl string. This bug could be used to cause
7119 Tor to crash on systems with unusual malloc implementations, or
7120 systems with unusual hardening installed. Fixes bug 17404; bugfix
7123 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7124 - Avoid a difficult-to-trigger heap corruption attack when extending
7125 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7126 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7127 Reported by Guido Vranken.
7129 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7130 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7131 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7133 o Major bugfixes (guard selection, backport from 0.2.7.6):
7134 - Actually look at the Guard flag when selecting a new directory
7135 guard. When we implemented the directory guard design, we
7136 accidentally started treating all relays as if they have the Guard
7137 flag during guard selection, leading to weaker anonymity and worse
7138 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7141 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7142 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7143 pointer to the previous (uninitialized) key value. The impact here
7144 should be limited to a difficult-to-trigger crash, if OpenSSL is
7145 running an engine that makes key generation failures possible, or
7146 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7147 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7150 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7151 - Fix an integer underflow bug when comparing malformed Tor
7152 versions. This bug could crash Tor when built with
7153 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7154 0.2.9.8, which were built with -ftrapv by default. In other cases
7155 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7156 on 0.0.8pre1. Found by OSS-Fuzz.
7158 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7159 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7160 zero size. Check size argument to memwipe() for underflow. Fixes
7161 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7164 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7165 - Make Tor survive errors involving connections without a
7166 corresponding event object. Previously we'd fail with an
7167 assertion; now we produce a log message. Related to bug 16248.
7169 o Minor features (geoip):
7170 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7173 o Minor bugfixes (compilation, backport from 0.2.7.6):
7174 - Fix a compilation warning with Clang 3.6: Do not check the
7175 presence of an address which can never be NULL. Fixes bug 17781.
7178 Changes in version 0.2.5.13 - 2017-03-03
7179 Tor 0.2.5.13 backports a number of security fixes from later Tor
7180 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
7181 this release, if for some reason they cannot upgrade to a later
7184 Note that support for Tor 0.2.5.x is ending next year: we will not issue
7185 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
7186 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7188 o Directory authority changes (backport from 0.2.8.5-rc):
7189 - Urras is no longer a directory authority. Closes ticket 19271.
7191 o Directory authority changes (backport from 0.2.9.2-alpha):
7192 - The "Tonga" bridge authority has been retired; the new bridge
7193 authority is "Bifroest". Closes tickets 19728 and 19690.
7195 o Directory authority key updates (backport from 0.2.8.1-alpha):
7196 - Update the V3 identity key for the dannenberg directory authority:
7197 it was changed on 18 November 2015. Closes task 17906. Patch
7200 o Major features (security fixes, backport from 0.2.9.4-alpha):
7201 - Prevent a class of security bugs caused by treating the contents
7202 of a buffer chunk as if they were a NUL-terminated string. At
7203 least one such bug seems to be present in all currently used
7204 versions of Tor, and would allow an attacker to remotely crash
7205 most Tor instances, especially those compiled with extra compiler
7206 hardening. With this defense in place, such bugs can't crash Tor,
7207 though we should still fix them as they occur. Closes ticket
7208 20384 (TROVE-2016-10-001).
7210 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7211 - Fix a bug in parsing that could cause clients to read a single
7212 byte past the end of an allocated region. This bug could be used
7213 to cause hardened clients (built with --enable-expensive-hardening)
7214 to crash if they tried to visit a hostile hidden service. Non-
7215 hardened clients are only affected depending on the details of
7216 their platform's memory allocator. Fixes bug 21018; bugfix on
7217 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7218 2016-12-002 and as CVE-2016-1254.
7220 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
7221 - Stop a crash that could occur when a client running with DNSPort
7222 received a query with multiple address types, and the first
7223 address type was not supported. Found and fixed by Scott Dial.
7224 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7226 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7227 - Fix an error that could cause us to read 4 bytes before the
7228 beginning of an openssl string. This bug could be used to cause
7229 Tor to crash on systems with unusual malloc implementations, or
7230 systems with unusual hardening installed. Fixes bug 17404; bugfix
7233 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7234 - Avoid a difficult-to-trigger heap corruption attack when extending
7235 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7236 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7237 Reported by Guido Vranken.
7239 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7240 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7241 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7243 o Major bugfixes (guard selection, backport from 0.2.7.6):
7244 - Actually look at the Guard flag when selecting a new directory
7245 guard. When we implemented the directory guard design, we
7246 accidentally started treating all relays as if they have the Guard
7247 flag during guard selection, leading to weaker anonymity and worse
7248 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7251 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7252 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7253 pointer to the previous (uninitialized) key value. The impact here
7254 should be limited to a difficult-to-trigger crash, if OpenSSL is
7255 running an engine that makes key generation failures possible, or
7256 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7257 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7260 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7261 - Fix an integer underflow bug when comparing malformed Tor
7262 versions. This bug could crash Tor when built with
7263 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7264 0.2.9.8, which were built with -ftrapv by default. In other cases
7265 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7266 on 0.0.8pre1. Found by OSS-Fuzz.
7268 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7269 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7270 zero size. Check size argument to memwipe() for underflow. Fixes
7271 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7274 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7275 - Make Tor survive errors involving connections without a
7276 corresponding event object. Previously we'd fail with an
7277 assertion; now we produce a log message. Related to bug 16248.
7279 o Minor features (geoip):
7280 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7283 o Minor bugfixes (compilation, backport from 0.2.7.6):
7284 - Fix a compilation warning with Clang 3.6: Do not check the
7285 presence of an address which can never be NULL. Fixes bug 17781.
7287 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
7288 - Check for failures from crypto_early_init, and refuse to continue.
7289 A previous typo meant that we could keep going with an
7290 uninitialized crypto library, and would have OpenSSL initialize
7291 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7292 when implementing ticket 4900. Patch by "teor".
7294 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7295 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7296 a client authorized hidden service. Fixes bug 15823; bugfix
7300 Changes in version 0.2.4.28 - 2017-03-03
7301 Tor 0.2.4.28 backports a number of security fixes from later Tor
7302 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
7303 this release, if for some reason they cannot upgrade to a later
7306 Note that support for Tor 0.2.4.x is ending soon: we will not issue
7307 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
7308 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
7310 o Directory authority changes (backport from 0.2.8.5-rc):
7311 - Urras is no longer a directory authority. Closes ticket 19271.
7313 o Directory authority changes (backport from 0.2.9.2-alpha):
7314 - The "Tonga" bridge authority has been retired; the new bridge
7315 authority is "Bifroest". Closes tickets 19728 and 19690.
7317 o Directory authority key updates (backport from 0.2.8.1-alpha):
7318 - Update the V3 identity key for the dannenberg directory authority:
7319 it was changed on 18 November 2015. Closes task 17906. Patch
7322 o Major features (security fixes, backport from 0.2.9.4-alpha):
7323 - Prevent a class of security bugs caused by treating the contents
7324 of a buffer chunk as if they were a NUL-terminated string. At
7325 least one such bug seems to be present in all currently used
7326 versions of Tor, and would allow an attacker to remotely crash
7327 most Tor instances, especially those compiled with extra compiler
7328 hardening. With this defense in place, such bugs can't crash Tor,
7329 though we should still fix them as they occur. Closes ticket
7330 20384 (TROVE-2016-10-001).
7332 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7333 - Fix a bug in parsing that could cause clients to read a single
7334 byte past the end of an allocated region. This bug could be used
7335 to cause hardened clients (built with --enable-expensive-hardening)
7336 to crash if they tried to visit a hostile hidden service. Non-
7337 hardened clients are only affected depending on the details of
7338 their platform's memory allocator. Fixes bug 21018; bugfix on
7339 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7340 2016-12-002 and as CVE-2016-1254.
7342 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7343 - Fix an error that could cause us to read 4 bytes before the
7344 beginning of an openssl string. This bug could be used to cause
7345 Tor to crash on systems with unusual malloc implementations, or
7346 systems with unusual hardening installed. Fixes bug 17404; bugfix
7349 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7350 - Avoid a difficult-to-trigger heap corruption attack when extending
7351 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7352 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7353 Reported by Guido Vranken.
7355 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7356 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7357 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7359 o Major bugfixes (guard selection, backport from 0.2.7.6):
7360 - Actually look at the Guard flag when selecting a new directory
7361 guard. When we implemented the directory guard design, we
7362 accidentally started treating all relays as if they have the Guard
7363 flag during guard selection, leading to weaker anonymity and worse
7364 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7367 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7368 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7369 pointer to the previous (uninitialized) key value. The impact here
7370 should be limited to a difficult-to-trigger crash, if OpenSSL is
7371 running an engine that makes key generation failures possible, or
7372 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7373 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7376 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7377 - Fix an integer underflow bug when comparing malformed Tor
7378 versions. This bug could crash Tor when built with
7379 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7380 0.2.9.8, which were built with -ftrapv by default. In other cases
7381 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7382 on 0.0.8pre1. Found by OSS-Fuzz.
7384 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7385 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7386 zero size. Check size argument to memwipe() for underflow. Fixes
7387 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7390 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7391 - Make Tor survive errors involving connections without a
7392 corresponding event object. Previously we'd fail with an
7393 assertion; now we produce a log message. Related to bug 16248.
7395 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
7396 - Make it harder for attackers to overload hidden services with
7397 introductions, by blocking multiple introduction requests on the
7398 same circuit. Resolves ticket 15515.
7400 o Minor features (geoip):
7401 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7404 o Minor bugfixes (compilation, backport from 0.2.7.6):
7405 - Fix a compilation warning with Clang 3.6: Do not check the
7406 presence of an address which can never be NULL. Fixes bug 17781.
7408 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7409 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7410 a client authorized hidden service. Fixes bug 15823; bugfix
7414 Changes in version 0.3.0.4-rc - 2017-03-01
7415 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
7416 0.3.0 release series, and introduces a few reliability features to
7417 keep them from coming back.
7419 This is the first release candidate in the Tor 0.3.0 series. If we
7420 find no new bugs or regressions here, the first stable 0.3.0 release
7421 will be nearly identical to it.
7423 o Major bugfixes (bridges):
7424 - When the same bridge is configured multiple times with the same
7425 identity, but at different address:port combinations, treat those
7426 bridge instances as separate guards. This fix restores the ability
7427 of clients to configure the same bridge with multiple pluggable
7428 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
7430 o Major bugfixes (hidden service directory v3):
7431 - Stop crashing on a failed v3 hidden service descriptor lookup
7432 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
7434 o Major bugfixes (parsing):
7435 - When parsing a malformed content-length field from an HTTP
7436 message, do not read off the end of the buffer. This bug was a
7437 potential remote denial-of-service attack against Tor clients and
7438 relays. A workaround was released in October 2016, to prevent this
7439 bug from crashing Tor. This is a fix for the underlying issue,
7440 which should no longer matter (if you applied the earlier patch).
7441 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
7442 using AFL (http://lcamtuf.coredump.cx/afl/).
7443 - Fix an integer underflow bug when comparing malformed Tor
7444 versions. This bug could crash Tor when built with
7445 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7446 0.2.9.8, which were built with -ftrapv by default. In other cases
7447 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7448 on 0.0.8pre1. Found by OSS-Fuzz.
7450 o Minor feature (protocol versioning):
7451 - Add new protocol version for proposal 224. HSIntro now advertises
7452 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
7454 o Minor features (directory authorities):
7455 - Directory authorities now reject descriptors that claim to be
7456 malformed versions of Tor. Helps prevent exploitation of
7458 - Reject version numbers with components that exceed INT32_MAX.
7459 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
7460 Fixes bug 21450; bugfix on 0.0.8pre1.
7461 - Directory authorities now reject relays running versions
7462 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
7463 suffer from bug 20499 and don't keep their consensus cache
7464 up-to-date. Resolves ticket 20509.
7466 o Minor features (geoip):
7467 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7470 o Minor features (reliability, crash):
7471 - Try better to detect problems in buffers where they might grow (or
7472 think they have grown) over 2 GB in size. Diagnostic for
7475 o Minor features (testing):
7476 - During 'make test-network-all', if tor logs any warnings, ask
7477 chutney to output them. Requires a recent version of chutney with
7478 the 21572 patch. Implements 21570.
7480 o Minor bugfixes (certificate expiration time):
7481 - Avoid using link certificates that don't become valid till some
7482 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
7484 o Minor bugfixes (code correctness):
7485 - Repair a couple of (unreachable or harmless) cases of the risky
7486 comparison-by-subtraction pattern that caused bug 21278.
7487 - Remove a redundant check for the UseEntryGuards option from the
7488 options_transition_affects_guards() function. Fixes bug 21492;
7489 bugfix on 0.3.0.1-alpha.
7491 o Minor bugfixes (directory mirrors):
7492 - Allow relays to use directory mirrors without a DirPort: these
7493 relays need to be contacted over their ORPorts using a begindir
7494 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
7495 - Clarify the message logged when a remote relay is unexpectedly
7496 missing an ORPort or DirPort: users were confusing this with a
7497 local port. Fixes another case of bug 20711; bugfix
7500 o Minor bugfixes (guards):
7501 - Don't warn about a missing guard state on timeout-measurement
7502 circuits: they aren't supposed to be using guards. Fixes an
7503 instance of bug 21007; bugfix on 0.3.0.1-alpha.
7504 - Silence a BUG() warning when attempting to use a guard whose
7505 descriptor we don't know, and make this scenario less likely to
7506 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
7508 o Minor bugfixes (hidden service):
7509 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
7510 cells. Previously, we were using sizeof() on a pointer, instead of
7511 the real destination buffer. Fortunately, that value was only used
7512 to double-check that there was enough room--which was already
7513 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
7515 o Minor bugfixes (testing):
7516 - Fix Raspbian build issues related to missing socket errno in
7517 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
7519 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
7520 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
7521 - Use bash in src/test/test-network.sh. This ensures we reliably
7522 call chutney's newer tools/test-network.sh when available. Fixes
7523 bug 21562; bugfix on 0.2.9.1-alpha.
7526 - Small fixes to the fuzzing documentation. Closes ticket 21472.
7529 Changes in version 0.2.9.10 - 2017-03-01
7530 Tor 0.2.9.10 backports a security fix from later Tor release. It also
7531 includes fixes for some major issues affecting directory authorities,
7532 LibreSSL compatibility, and IPv6 correctness.
7534 The Tor 0.2.9.x release series is now marked as a long-term-support
7535 series. We intend to backport security fixes to 0.2.9.x until at
7536 least January of 2020.
7538 o Major bugfixes (directory authority, 0.3.0.3-alpha):
7539 - During voting, when marking a relay as a probable sybil, do not
7540 clear its BadExit flag: sybils can still be bad in other ways
7541 too. (We still clear the other flags.) Fixes bug 21108; bugfix
7544 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
7545 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
7546 any IPv6 addresses. Instead, only reject a port over IPv6 if the
7547 exit policy rejects that port on more than an IPv6 /16 of
7548 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
7549 which rejected a relay's own IPv6 address by default. Fixes bug
7550 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
7552 o Major bugfixes (parsing, also in 0.3.0.4-rc):
7553 - Fix an integer underflow bug when comparing malformed Tor
7554 versions. This bug could crash Tor when built with
7555 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7556 0.2.9.8, which were built with -ftrapv by default. In other cases
7557 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7558 on 0.0.8pre1. Found by OSS-Fuzz.
7560 o Minor features (directory authorities, also in 0.3.0.4-rc):
7561 - Directory authorities now reject descriptors that claim to be
7562 malformed versions of Tor. Helps prevent exploitation of
7564 - Reject version numbers with components that exceed INT32_MAX.
7565 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
7566 Fixes bug 21450; bugfix on 0.0.8pre1.
7568 o Minor features (geoip):
7569 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7572 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
7573 - Autoconf now checks to determine if OpenSSL structures are opaque,
7574 instead of explicitly checking for OpenSSL version numbers. Part
7576 - Support building with recent LibreSSL code that uses opaque
7577 structures. Closes ticket 21359.
7579 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
7580 - Repair a couple of (unreachable or harmless) cases of the risky
7581 comparison-by-subtraction pattern that caused bug 21278.
7583 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
7584 - The tor-resolve command line tool now rejects hostnames over 255
7585 characters in length. Previously, it would silently truncate them,
7586 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
7587 Patch by "junglefowl".
7590 Changes in version 0.3.0.3-alpha - 2017-02-03
7591 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
7592 0.3.0.x development series, including some that could cause
7593 authorities to behave badly. There is also a fix for a longstanding
7594 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
7595 includes some smaller features and bugfixes.
7597 The Tor 0.3.0.x release series is now in patch-freeze: no additional
7598 features will be considered for inclusion in 0.3.0.x. We suspect that
7599 some bugs will probably remain, however, and we encourage people to
7602 o Major bugfixes (directory authority):
7603 - During voting, when marking a relay as a probable sybil, do not
7604 clear its BadExit flag: sybils can still be bad in other ways
7605 too. (We still clear the other flags.) Fixes bug 21108; bugfix
7607 - When deciding whether we have just found a router to be reachable,
7608 do not penalize it for not having performed an Ed25519 link
7609 handshake if it does not claim to support an Ed25519 handshake.
7610 Previously, we would treat such relays as non-running. Fixes bug
7611 21107; bugfix on 0.3.0.1-alpha.
7613 o Major bugfixes (entry guards):
7614 - Stop trying to build circuits through entry guards for which we
7615 have no descriptor. Also, stop crashing in the case that we *do*
7616 accidentally try to build a circuit in such a state. Fixes bug
7617 21242; bugfix on 0.3.0.1-alpha.
7619 o Major bugfixes (IPv6 Exits):
7620 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
7621 any IPv6 addresses. Instead, only reject a port over IPv6 if the
7622 exit policy rejects that port on more than an IPv6 /16 of
7623 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
7624 which rejected a relay's own IPv6 address by default. Fixes bug
7625 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
7627 o Minor feature (client):
7628 - Enable IPv6 traffic on the SocksPort by default. To disable this,
7629 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
7631 o Minor feature (fallback scripts):
7632 - Add a check_existing mode to updateFallbackDirs.py, which checks
7633 if fallbacks in the hard-coded list are working. Closes ticket
7634 20174. Patch by haxxpop.
7636 o Minor features (ciphersuite selection):
7637 - Clients now advertise a list of ciphersuites closer to the ones
7638 preferred by Firefox. Closes part of ticket 15426.
7639 - Allow relays to accept a wider range of ciphersuites, including
7640 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
7642 o Minor features (controller, configuration):
7643 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
7644 and so on, now comes with a __*Port variant that will not be saved
7645 to the torrc file by the controller's SAVECONF command. This
7646 change allows TorBrowser to set up a single-use domain socket for
7647 each time it launches Tor. Closes ticket 20956.
7648 - The GETCONF command can now query options that may only be
7649 meaningful in context-sensitive lists. This allows the controller
7650 to query the mixed SocksPort/__SocksPort style options introduced
7651 in feature 20956. Implements ticket 21300.
7653 o Minor features (portability, compilation):
7654 - Autoconf now checks to determine if OpenSSL structures are opaque,
7655 instead of explicitly checking for OpenSSL version numbers. Part
7657 - Support building with recent LibreSSL code that uses opaque
7658 structures. Closes ticket 21359.
7660 o Minor features (relay):
7661 - We now allow separation of exit and relay traffic to different
7662 source IP addresses, using the OutboundBindAddressExit and
7663 OutboundBindAddressOR options respectively. Closes ticket 17975.
7664 Written by Michael Sonntag.
7666 o Minor bugfix (logging):
7667 - Don't recommend the use of Tor2web in non-anonymous mode.
7668 Recommending Tor2web is a bad idea because the client loses all
7669 anonymity. Tor2web should only be used in specific cases by users
7670 who *know* and understand the issues. Fixes bug 21294; bugfix
7673 o Minor bugfixes (client):
7674 - Always recover from failures in extend_info_from_node(), in an
7675 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
7676 bugfix on 0.2.3.1-alpha.
7678 o Minor bugfixes (client, entry guards):
7679 - Fix a bug warning (with backtrace) when we fail a channel that
7680 circuits to fallback directories on it. Fixes bug 21128; bugfix
7682 - Fix a spurious bug warning (with backtrace) when removing an
7683 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
7684 - Fix a bug of the new guard algorithm where tor could stall for up
7685 to 10 minutes before retrying a guard after a long period of no
7686 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
7687 - Do not try to build circuits until we have descriptors for our
7688 primary entry guards. Related to fix for bug 21242.
7690 o Minor bugfixes (configure, autoconf):
7691 - Rename the configure option --enable-expensive-hardening to
7692 --enable-fragile-hardening. Expensive hardening makes the tor
7693 daemon abort when some kinds of issues are detected. Thus, it
7694 makes tor more at risk of remote crashes but safer against RCE or
7695 heartbleed bug category. We now try to explain this issue in a
7696 message from the configure script. Fixes bug 21290; bugfix
7699 o Minor bugfixes (controller):
7700 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
7701 20824; bugfix on 0.3.0.1-alpha.
7703 o Minor bugfixes (hidden service):
7704 - Clean up the code for expiring intro points with no associated
7705 circuits. It was causing, rarely, a service with some expiring
7706 introduction points to not open enough additional introduction
7707 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
7708 - Stop setting the torrc option HiddenServiceStatistics to "0" just
7709 because we're not a bridge or relay. Instead, we preserve whatever
7710 value the user set (or didn't set). Fixes bug 21150; bugfix
7712 - Resolve two possible underflows which could lead to creating and
7713 closing a lot of introduction point circuits in a non-stop loop.
7714 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
7716 o Minor bugfixes (portability):
7717 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
7718 It is supported by OpenBSD itself, and also by most OpenBSD
7719 variants (such as Bitrig). Fixes bug 20980; bugfix
7721 - When mapping a file of length greater than SIZE_MAX, do not
7722 silently truncate its contents. This issue could occur on 32 bit
7723 systems with large file support and files which are larger than 4
7724 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
7726 o Minor bugfixes (tor-resolve):
7727 - The tor-resolve command line tool now rejects hostnames over 255
7728 characters in length. Previously, it would silently truncate them,
7729 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
7730 Patch by "junglefowl".
7732 o Minor bugfixes (Windows services):
7733 - Be sure to initialize the monotonic time subsystem before using
7734 it, even when running as an NT service. Fixes bug 21356; bugfix
7738 Changes in version 0.3.0.2-alpha - 2017-01-23
7739 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
7740 cause relays and clients to crash, even if they were not built with
7741 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
7742 versions, and also affects 0.3.0.1-alpha: all relays running an affected
7743 version should upgrade.
7745 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
7746 time-to-live values, makes directory authorities enforce the 1-to-1
7747 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
7748 client-side onion service reachability bug, does better at selecting
7749 the set of fallback directories, and more.
7751 o Major bugfixes (security, also in 0.2.9.9):
7752 - Downgrade the "-ftrapv" option from "always on" to "only on when
7753 --enable-expensive-hardening is provided." This hardening option, like
7754 others, can turn survivable bugs into crashes--and having it on by
7755 default made a (relatively harmless) integer overflow bug into a
7756 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
7759 o Major features (security):
7760 - Change the algorithm used to decide DNS TTLs on client and server
7761 side, to better resist DNS-based correlation attacks like the
7762 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
7763 Feamster. Now relays only return one of two possible DNS TTL
7764 values, and clients are willing to believe DNS TTL values up to 3
7765 hours long. Closes ticket 19769.
7767 o Major features (directory authority, security):
7768 - The default for AuthDirPinKeys is now 1: directory authorities
7769 will reject relays where the RSA identity key matches a previously
7770 seen value, but the Ed25519 key has changed. Closes ticket 18319.
7772 o Major bugfixes (client, guard, crash):
7773 - In circuit_get_global_origin_list(), return the actual list of
7774 origin circuits. The previous version of this code returned the
7775 list of all the circuits, and could have caused strange bugs,
7776 including possible crashes. Fixes bug 21118; bugfix
7779 o Major bugfixes (client, onion service, also in 0.2.9.9):
7780 - Fix a client-side onion service reachability bug, where multiple
7781 socks requests to an onion service (or a single slow request)
7782 could cause us to mistakenly mark some of the service's
7783 introduction points as failed, and we cache that failure so
7784 eventually we run out and can't reach the service. Also resolves a
7785 mysterious "Remote server sent bogus reason code 65021" log
7786 warning. The bug was introduced in ticket 17218, where we tried to
7787 remember the circuit end reason as a uint16_t, which mangled
7788 negative values. Partially fixes bug 21056 and fixes bug 20307;
7789 bugfix on 0.2.8.1-alpha.
7791 o Major bugfixes (DNS):
7792 - Fix a bug that prevented exit nodes from caching DNS records for
7793 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
7795 o Minor features (controller):
7796 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
7797 shared-random values to the controller. Closes ticket 19925.
7799 o Minor features (entry guards):
7800 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
7801 break regression tests.
7802 - Require UseEntryGuards when UseBridges is set, in order to make
7803 sure bridges aren't bypassed. Resolves ticket 20502.
7805 o Minor features (fallback directories):
7806 - Select 200 fallback directories for each release. Closes
7808 - Allow 3 fallback relays per operator, which is safe now that we
7809 are choosing 200 fallback relays. Closes ticket 20912.
7810 - Exclude relays affected by bug 20499 from the fallback list.
7811 Exclude relays from the fallback list if they are running versions
7812 known to be affected by bug 20499, or if in our tests they deliver
7813 a stale consensus (i.e. one that expired more than 24 hours ago).
7814 Closes ticket 20539.
7815 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
7817 - Require fallback directories to have the same address and port for
7818 7 days (now that we have enough relays with this stability).
7819 Relays whose OnionOO stability timer is reset on restart by bug
7820 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
7821 this issue. Closes ticket 20880; maintains short-term fix
7823 - Require fallbacks to have flags for 90% of the time (weighted
7824 decaying average), rather than 95%. This allows at least 73% of
7825 clients to bootstrap in the first 5 seconds without contacting an
7826 authority. Part of ticket 18828.
7827 - Annotate updateFallbackDirs.py with the bandwidth and consensus
7828 weight for each candidate fallback. Closes ticket 20878.
7829 - Make it easier to change the output sort order of fallbacks.
7830 Closes ticket 20822.
7831 - Display the relay fingerprint when downloading consensuses from
7832 fallbacks. Closes ticket 20908.
7834 o Minor features (geoip, also in 0.2.9.9):
7835 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
7838 o Minor features (next-gen onion service directories):
7839 - Remove the "EnableOnionServicesV3" consensus parameter that we
7840 introduced in 0.3.0.1-alpha: relays are now always willing to act
7841 as v3 onion service directories. Resolves ticket 19899.
7843 o Minor features (linting):
7844 - Enhance the changes file linter to warn on Tor versions that are
7845 prefixed with "tor-". Closes ticket 21096.
7847 o Minor features (logging):
7848 - In several places, describe unset ed25519 keys as "<unset>",
7849 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
7851 o Minor bugfix (control protocol):
7852 - The reply to a "GETINFO config/names" request via the control
7853 protocol now spells the type "Dependent" correctly. This is a
7854 breaking change in the control protocol. (The field seems to be
7855 ignored by the most common known controllers.) Fixes bug 18146;
7856 bugfix on 0.1.1.4-alpha.
7858 o Minor bugfixes (bug resilience):
7859 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
7860 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
7861 Hans Jerry Illikainen.
7863 o Minor bugfixes (build):
7864 - Replace obsolete Autoconf macros with their modern equivalent and
7865 prevent similar issues in the future. Fixes bug 20990; bugfix
7868 o Minor bugfixes (client, guards):
7869 - Fix bug where Tor would think that there are circuits waiting for
7870 better guards even though those circuits have been freed. Fixes
7871 bug 21142; bugfix on 0.3.0.1-alpha.
7873 o Minor bugfixes (config):
7874 - Don't assert on startup when trying to get the options list and
7875 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
7876 options so of course they aren't ready yet. Fixes bug 21062;
7877 bugfix on 0.2.9.3-alpha.
7879 o Minor bugfixes (controller):
7880 - Make the GETINFO interface for inquiring about entry guards
7881 support the new guards backend. Fixes bug 20823; bugfix
7884 o Minor bugfixes (dead code):
7885 - Remove a redundant check for PidFile changes at runtime in
7886 options_transition_allowed(): this check is already performed
7887 regardless of whether the sandbox is active. Fixes bug 21123;
7888 bugfix on 0.2.5.4-alpha.
7890 o Minor bugfixes (documentation):
7891 - Update the tor manual page to document every option that can not
7892 be changed while tor is running. Fixes bug 21122.
7894 o Minor bugfixes (fallback directories):
7895 - Stop failing when a relay has no uptime data in
7896 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
7897 - Avoid checking fallback candidates' DirPorts if they are down in
7898 OnionOO. When a relay operator has multiple relays, this
7899 prioritizes relays that are up over relays that are down. Fixes
7900 bug 20926; bugfix on 0.2.8.3-alpha.
7901 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
7902 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
7904 o Minor bugfixes (guards, bootstrapping):
7905 - When connecting to a directory guard during bootstrap, do not mark
7906 the guard as successful until we receive a good-looking directory
7907 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
7909 o Minor bugfixes (onion services):
7910 - Fix the config reload pruning of old vs new services so it
7911 actually works when both ephemeral and non-ephemeral services are
7912 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
7913 - Allow the number of introduction points to be as low as 0, rather
7914 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
7916 o Minor bugfixes (IPv6):
7917 - Make IPv6-using clients try harder to find an IPv6 directory
7918 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
7919 - When IPv6 addresses have not been downloaded yet (microdesc
7920 consensus documents don't list relay IPv6 addresses), use hard-
7921 coded addresses for authorities, fallbacks, and configured
7922 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
7923 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
7925 o Minor bugfixes (memory leaks):
7926 - Fix a memory leak when configuring hidden services. Fixes bug
7927 20987; bugfix on 0.3.0.1-alpha.
7929 o Minor bugfixes (portability, also in 0.2.9.9):
7930 - Avoid crashing when Tor is built using headers that contain
7931 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
7932 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
7934 - Fix Libevent detection on platforms without Libevent 1 headers
7935 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
7937 o Minor bugfixes (relay):
7938 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
7939 initializing the keys would reset the DataDirectory to 0700
7940 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
7941 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
7943 o Minor bugfixes (testing):
7944 - Remove undefined behavior from the backtrace generator by removing
7945 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
7947 o Minor bugfixes (unit tests):
7948 - Allow the unit tests to pass even when DNS lookups of bogus
7949 addresses do not fail as expected. Fixes bug 20862 and 20863;
7950 bugfix on unit tests introduced in 0.2.8.1-alpha
7951 through 0.2.9.4-alpha.
7953 o Code simplification and refactoring:
7954 - Refactor code to manipulate global_origin_circuit_list into
7955 separate functions. Closes ticket 20921.
7957 o Documentation (formatting):
7958 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
7959 blocks were incorrectly appearing. Closes ticket 20885.
7961 o Documentation (man page):
7962 - Clarify many options in tor.1 and add some min/max values for
7963 HiddenService options. Closes ticket 21058.
7966 Changes in version 0.2.9.9 - 2017-01-23
7967 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
7968 cause relays and clients to crash, even if they were not built with
7969 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
7970 versions, and also affects 0.3.0.1-alpha: all relays running an affected
7971 version should upgrade.
7973 This release also resolves a client-side onion service reachability
7974 bug, and resolves a pair of small portability issues.
7976 o Major bugfixes (security):
7977 - Downgrade the "-ftrapv" option from "always on" to "only on when
7978 --enable-expensive-hardening is provided." This hardening option,
7979 like others, can turn survivable bugs into crashes -- and having
7980 it on by default made a (relatively harmless) integer overflow bug
7981 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
7982 bugfix on 0.2.9.1-alpha.
7984 o Major bugfixes (client, onion service):
7985 - Fix a client-side onion service reachability bug, where multiple
7986 socks requests to an onion service (or a single slow request)
7987 could cause us to mistakenly mark some of the service's
7988 introduction points as failed, and we cache that failure so
7989 eventually we run out and can't reach the service. Also resolves a
7990 mysterious "Remote server sent bogus reason code 65021" log
7991 warning. The bug was introduced in ticket 17218, where we tried to
7992 remember the circuit end reason as a uint16_t, which mangled
7993 negative values. Partially fixes bug 21056 and fixes bug 20307;
7994 bugfix on 0.2.8.1-alpha.
7996 o Minor features (geoip):
7997 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
8000 o Minor bugfixes (portability):
8001 - Avoid crashing when Tor is built using headers that contain
8002 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
8003 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
8005 - Fix Libevent detection on platforms without Libevent 1 headers
8006 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
8009 Changes in version 0.3.0.1-alpha - 2016-12-19
8010 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
8011 series. It strengthens Tor's link and circuit handshakes by
8012 identifying relays by their Ed25519 keys, improves the algorithm that
8013 clients use to choose and maintain their list of guards, and includes
8014 additional backend support for the next-generation hidden service
8015 design. It also contains numerous other small features and
8016 improvements to security, correctness, and performance.
8018 Below are the changes since 0.2.9.8.
8020 o Major features (guard selection algorithm):
8021 - Tor's guard selection algorithm has been redesigned from the
8022 ground up, to better support unreliable networks and restrictive
8023 sets of entry nodes, and to better resist guard-capture attacks by
8024 hostile local networks. Implements proposal 271; closes
8027 o Major features (next-generation hidden services):
8028 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
8029 prop224 aka "Next Generation Hidden Services". Service and clients
8030 don't use this functionality yet. Closes ticket 19043. Based on
8031 initial code by Alec Heifetz.
8032 - Relays now support the HSDir version 3 protocol, so that they can
8033 can store and serve v3 descriptors. This is part of the next-
8034 generation onion service work detailed in proposal 224. Closes
8037 o Major features (protocol, ed25519 identity keys):
8038 - Relays now use Ed25519 to prove their Ed25519 identities and to
8039 one another, and to clients. This algorithm is faster and more
8040 secure than the RSA-based handshake we've been doing until now.
8041 Implements the second big part of proposal 220; Closes
8043 - Clients now support including Ed25519 identity keys in the EXTEND2
8044 cells they generate. By default, this is controlled by a consensus
8045 parameter, currently disabled. You can turn this feature on for
8046 testing by setting ExtendByEd25519ID in your configuration. This
8047 might make your traffic appear different than the traffic
8048 generated by other users, however. Implements part of ticket
8049 15056; part of proposal 220.
8050 - Relays now understand requests to extend to other relays by their
8051 Ed25519 identity keys. When an Ed25519 identity key is included in
8052 an EXTEND2 cell, the relay will only extend the circuit if the
8053 other relay can prove ownership of that identity. Implements part
8054 of ticket 15056; part of proposal 220.
8056 o Major bugfixes (scheduler):
8057 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
8058 caused the channel scheduler to behave more or less randomly,
8059 rather than preferring channels with higher-priority circuits.
8060 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
8062 o Minor features (controller):
8063 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
8064 rather than "unrecognized." Closes ticket 20389; patch from
8067 o Minor features (diagnostic, directory client):
8068 - Warn when we find an unexpected inconsistency in directory
8069 download status objects. Prevents some negative consequences of
8072 o Minor features (directory authority):
8073 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
8074 default) to control whether authorities should try to probe relays
8075 by their Ed25519 link keys. This option will go away in a few
8076 releases--unless we encounter major trouble in our ed25519 link
8077 protocol rollout, in which case it will serve as a safety option.
8079 o Minor features (directory cache):
8080 - Relays and bridges will now refuse to serve the consensus they
8081 have if they know it is too old for a client to use. Closes
8084 o Minor features (ed25519 link handshake):
8085 - Advertise support for the ed25519 link handshake using the
8086 subprotocol-versions mechanism, so that clients can tell which
8087 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
8089 o Minor features (fingerprinting resistance, authentication):
8090 - Extend the length of RSA keys used for TLS link authentication to
8091 2048 bits. (These weren't used for forward secrecy; for forward
8092 secrecy, we used P256.) Closes ticket 13752.
8094 o Minor features (infrastructure):
8095 - Implement smartlist_add_strdup() function. Replaces the use of
8096 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
8098 o Minor bugfixes (client):
8099 - When clients that use bridges start up with a cached consensus on
8100 disk, they were ignoring it and downloading a new one. Now they
8101 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
8103 o Minor bugfixes (configuration):
8104 - Accept non-space whitespace characters after the severity level in
8105 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
8106 - Support "TByte" and "TBytes" units in options given in bytes.
8107 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
8108 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
8110 o Minor bugfixes (consensus weight):
8111 - Add new consensus method that initializes bw weights to 1 instead
8112 of 0. This prevents a zero weight from making it all the way to
8113 the end (happens in small testing networks) and causing an error.
8114 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
8116 o Minor bugfixes (descriptors):
8117 - Correctly recognise downloaded full descriptors as valid, even
8118 when using microdescriptors as circuits. This affects clients with
8119 FetchUselessDescriptors set, and may affect directory authorities.
8120 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
8122 o Minor bugfixes (directory system):
8123 - Download all consensus flavors, descriptors, and authority
8124 certificates when FetchUselessDescriptors is set, regardless of
8125 whether tor is a directory cache or not. Fixes bug 20667; bugfix
8126 on all recent tor versions.
8127 - Bridges and relays now use microdescriptors (like clients do)
8128 rather than old-style router descriptors. Now bridges will blend
8129 in with clients in terms of the circuits they build. Fixes bug
8130 6769; bugfix on 0.2.3.2-alpha.
8132 o Minor bugfixes (ed25519 certificates):
8133 - Correctly interpret ed25519 certificates that would expire some
8134 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
8136 o Minor bugfixes (hidden services):
8137 - Stop ignoring misconfigured hidden services. Instead, refuse to
8138 start tor until the misconfigurations have been corrected. Fixes
8139 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
8142 o Minor bugfixes (memory leak at exit):
8143 - Fix a small harmless memory leak at exit of the previously unused
8144 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
8147 o Minor bugfixes (util):
8148 - When finishing writing a file to disk, if we were about to replace
8149 the file with the temporary file created before and we fail to
8150 replace it, remove the temporary file so it doesn't stay on disk.
8151 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
8153 o Minor bugfixes (Windows):
8154 - Check for getpagesize before using it to mmap files. This fixes
8155 compilation in some MinGW environments. Fixes bug 20530; bugfix on
8156 0.1.2.1-alpha. Reported by "ice".
8158 o Code simplification and refactoring:
8159 - Abolish all global guard context in entrynodes.c; replace with new
8160 guard_selection_t structure as preparation for proposal 271.
8161 Closes ticket 19858.
8162 - Introduce rend_service_is_ephemeral() that tells if given onion
8163 service is ephemeral. Replace unclear NULL-checkings for service
8164 directory with this function. Closes ticket 20526.
8165 - Extract magic numbers in circuituse.c into defined variables.
8166 - Refactor circuit_is_available_for_use to remove unnecessary check.
8167 - Refactor circuit_predict_and_launch_new for readability and
8168 testability. Closes ticket 18873.
8169 - Refactor large if statement in purpose_needs_anonymity to use
8170 switch statement instead. Closes part of ticket 20077.
8171 - Refactor the hashing API to return negative values for errors, as
8172 is done as throughout the codebase. Closes ticket 20717.
8173 - Remove data structures that were used to index or_connection
8174 objects by their RSA identity digests. These structures are fully
8175 redundant with the similar structures used in the
8176 channel abstraction.
8177 - Remove duplicate code in the channel_write_*cell() functions.
8178 Closes ticket 13827; patch from Pingl.
8179 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
8180 use only purpose_needs_anonymity. Closes part of ticket 20077.
8181 - The code to generate and parse EXTEND and EXTEND2 cells has been
8182 replaced with code automatically generated by the
8186 - Include the "TBits" unit in Tor's man page. Fixes part of bug
8187 20622; bugfix on 0.2.5.1-alpha.
8188 - Change '1' to 'weight_scale' in consensus bw weights calculation
8189 comments, as that is reality. Closes ticket 20273. Patch
8191 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
8192 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
8194 - Stop the man page from incorrectly stating that HiddenServiceDir
8195 must already exist. Fixes 20486.
8196 - Clarify that when ClientRejectInternalAddresses is enabled (which
8197 is the default), multicast DNS hostnames for machines on the local
8198 network (of the form *.local) are also rejected. Closes
8202 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
8203 limit for relays running on a single IP applies to authority IP
8204 addresses as well as to non-authority IP addresses. Closes
8206 - The UseDirectoryGuards torrc option no longer exists: all users
8207 that use entry guards will also use directory guards. Related to
8208 proposal 271; implements part of ticket 20831.
8211 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
8212 from "overcaffeinated".
8213 - Perform the coding style checks when running the tests and fail
8214 when coding style violations are found. Closes ticket 5500.
8215 - Add tests for networkstatus_compute_bw_weights_v10.
8216 - Add unit tests circuit_predict_and_launch_new.
8217 - Extract dummy_origin_circuit_new so it can be used by other
8221 Changes in version 0.2.8.12 - 2016-12-19
8222 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
8223 below) where Tor clients could crash when attempting to visit a
8224 hostile hidden service. Clients are recommended to upgrade as packages
8225 become available for their systems.
8227 It also includes an updated list of fallback directories, backported
8230 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
8231 backported to 0.2.8 in the future.
8233 o Major bugfixes (parsing, security, backported from 0.2.9.8):
8234 - Fix a bug in parsing that could cause clients to read a single
8235 byte past the end of an allocated region. This bug could be used
8236 to cause hardened clients (built with --enable-expensive-hardening)
8237 to crash if they tried to visit a hostile hidden service. Non-
8238 hardened clients are only affected depending on the details of
8239 their platform's memory allocator. Fixes bug 21018; bugfix on
8240 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8241 2016-12-002 and as CVE-2016-1254.
8243 o Minor features (fallback directory list, backported from 0.2.9.8):
8244 - Replace the 81 remaining fallbacks of the 100 originally
8245 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
8246 fallbacks (123 new, 54 existing, 27 removed) generated in December
8247 2016. Resolves ticket 20170.
8249 o Minor features (geoip, backported from 0.2.9.7-rc):
8250 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
8254 Changes in version 0.2.9.8 - 2016-12-19
8255 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
8257 The Tor 0.2.9 series makes mandatory a number of security features
8258 that were formerly optional. It includes support for a new shared-
8259 randomness protocol that will form the basis for next generation
8260 hidden services, includes a single-hop hidden service mode for
8261 optimizing .onion services that don't actually want to be hidden,
8262 tries harder not to overload the directory authorities with excessive
8263 downloads, and supports a better protocol versioning scheme for
8264 improved compatibility with other implementations of the Tor protocol.
8266 And of course, there are numerous other bugfixes and improvements.
8268 This release also includes a fix for a medium-severity issue (bug
8269 21018 below) where Tor clients could crash when attempting to visit a
8270 hostile hidden service. Clients are recommended to upgrade as packages
8271 become available for their systems.
8273 Below are the changes since 0.2.9.7-rc. For a list of all changes
8274 since 0.2.8, see the ReleaseNotes file.
8276 o Major bugfixes (parsing, security):
8277 - Fix a bug in parsing that could cause clients to read a single
8278 byte past the end of an allocated region. This bug could be used
8279 to cause hardened clients (built with --enable-expensive-hardening)
8280 to crash if they tried to visit a hostile hidden service. Non-
8281 hardened clients are only affected depending on the details of
8282 their platform's memory allocator. Fixes bug 21018; bugfix on
8283 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8284 2016-12-002 and as CVE-2016-1254.
8286 o Minor features (fallback directory list):
8287 - Replace the 81 remaining fallbacks of the 100 originally
8288 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
8289 fallbacks (123 new, 54 existing, 27 removed) generated in December
8290 2016. Resolves ticket 20170.
8293 Changes in version 0.2.9.7-rc - 2016-12-12
8294 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
8295 including a few that had prevented tests from passing on
8298 o Minor features (geoip):
8299 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
8302 o Minor bugfix (build):
8303 - The current Git revision when building from a local repository is
8304 now detected correctly when using git worktrees. Fixes bug 20492;
8305 bugfix on 0.2.3.9-alpha.
8307 o Minor bugfixes (directory authority):
8308 - When computing old Tor protocol line version in protover, we were
8309 looking at 0.2.7.5 twice instead of a specific case for
8310 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
8312 o Minor bugfixes (download scheduling):
8313 - Resolve a "bug" warning when considering a download schedule whose
8314 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
8316 o Minor bugfixes (logging):
8317 - Downgrade a harmless log message about the
8318 pending_entry_connections list from "warn" to "info". Mitigates
8321 o Minor bugfixes (memory leak):
8322 - Fix a small memory leak when receiving AF_UNIX connections on a
8323 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
8324 - When moving a signed descriptor object from a source to an
8325 existing destination, free the allocated memory inside that
8326 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
8328 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
8329 - Fix a memory leak and use-after-free error when removing entries
8330 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
8331 0.2.5.5-alpha. Patch from "cypherpunks".
8333 o Minor bugfixes (portability):
8334 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
8335 Fixes bug 20935; bugfix on 0.2.9.6-rc.
8337 o Minor bugfixes (unit tests):
8338 - Stop expecting NetBSD unit tests to report success for ipfw. Part
8339 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
8340 - Fix tolerances in unit tests for monotonic time comparisons
8341 between nanoseconds and microseconds. Previously, we accepted a 10
8342 us difference only, which is not realistic on every platform's
8343 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
8344 - Remove a double-free in the single onion service unit test. Stop
8345 ignoring a return value. Make future changes less error-prone.
8346 Fixes bug 20864; bugfix on 0.2.9.6-rc.
8349 Changes in version 0.2.8.11 - 2016-12-08
8350 Tor 0.2.8.11 backports fixes for additional portability issues that
8351 could prevent Tor from building correctly on OSX Sierra, or with
8352 OpenSSL 1.1. Affected users should upgrade; others can safely stay
8355 o Minor bugfixes (portability):
8356 - Avoid compilation errors when building on OSX Sierra. Sierra began
8357 to support the getentropy() and clock_gettime() APIs, but created
8358 a few problems in doing so. Tor 0.2.9 has a more thorough set of
8359 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
8360 monotonic time interfaces. Fixes bug 20865. Bugfix
8363 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
8364 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
8365 architectures. Closes ticket 20588.
8368 Changes in version 0.2.8.10 - 2016-12-02
8369 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
8370 unusable after they left standby mode. It also backports fixes for
8371 a few portability issues and a small but problematic memory leak.
8373 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
8374 - When Tor leaves standby because of a new application request, open
8375 circuits as needed to serve that request. Previously, we would
8376 potentially wait a very long time. Fixes part of bug 19969; bugfix
8379 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
8380 - Clients now respond to new application stream requests immediately
8381 when they arrive, rather than waiting up to one second before
8382 starting to handle them. Fixes part of bug 19969; bugfix
8385 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
8386 - Work around a bug in the OSX 10.12 SDK that would prevent us from
8387 successfully targeting earlier versions of OSX. Resolves
8390 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
8391 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
8392 20551; bugfix on 0.2.1.1-alpha.
8394 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
8395 - Work around a memory leak in OpenSSL 1.1 when encoding public
8396 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
8398 o Minor features (geoip):
8399 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
8402 Changes in version 0.2.9.6-rc - 2016-12-02
8403 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
8404 version. We hope that it will be ready to become stable soon, and we
8405 encourage everyone to test this release. If no showstopper bugs are
8406 found here, the next 0.2.9 release will be stable.
8408 o Major bugfixes (relay, resolver, logging):
8409 - For relays that don't know their own address, avoid attempting a
8410 local hostname resolve for each descriptor we download. This
8411 will cut down on the number of "Success: chose address 'x.x.x.x'"
8412 log lines, and also avoid confusing clock jumps if the resolver
8413 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
8415 o Minor bugfixes (client, fascistfirewall):
8416 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
8417 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
8419 o Minor bugfixes (hidden services):
8420 - Stop ignoring the anonymity status of saved keys for hidden
8421 services and single onion services when first starting tor.
8422 Instead, refuse to start tor if any hidden service key has been
8423 used in a different hidden service anonymity mode. Fixes bug
8424 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
8426 o Minor bugfixes (portability):
8427 - Work around a bug in the OSX 10.12 SDK that would prevent us from
8428 successfully targeting earlier versions of OSX. Resolves
8430 - Run correctly when built on Windows build environments that
8431 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
8433 o Minor bugfixes (single onion services, Tor2web):
8434 - Stop complaining about long-term one-hop circuits deliberately
8435 created by single onion services and Tor2web. These log messages
8436 are intended to diagnose issue 8387, which relates to circuits
8437 hanging around forever for no reason. Fixes bug 20613; bugfix on
8438 0.2.9.1-alpha. Reported by "pastly".
8440 o Minor bugfixes (unit tests):
8441 - Stop spurious failures in the local interface address discovery
8442 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
8446 - Correct the minimum bandwidth value in torrc.sample, and queue a
8447 corresponding change for torrc.minimal. Closes ticket 20085.
8450 Changes in version 0.2.9.5-alpha - 2016-11-08
8451 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
8452 version. We believe one or two probably remain, and we encourage
8453 everyone to test this release.
8455 o Major bugfixes (client performance):
8456 - Clients now respond to new application stream requests immediately
8457 when they arrive, rather than waiting up to one second before
8458 starting to handle them. Fixes part of bug 19969; bugfix
8461 o Major bugfixes (client reliability):
8462 - When Tor leaves standby because of a new application request, open
8463 circuits as needed to serve that request. Previously, we would
8464 potentially wait a very long time. Fixes part of bug 19969; bugfix
8467 o Major bugfixes (download scheduling):
8468 - When using an exponential backoff schedule, do not give up on
8469 downloading just because we have failed a bunch of times. Since
8470 each delay is longer than the last, retrying indefinitely won't
8471 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
8472 - If a consensus expires while we are waiting for certificates to
8473 download, stop waiting for certificates.
8474 - If we stop waiting for certificates less than a minute after we
8475 started downloading them, do not consider the certificate download
8476 failure a separate failure. Fixes bug 20533; bugfix
8478 - Remove the maximum delay on exponential-backoff scheduling. Since
8479 we now allow an infinite number of failures (see ticket 20536), we
8480 must now allow the time to grow longer on each failure. Fixes part
8481 of bug 20534; bugfix on 0.2.9.1-alpha.
8482 - Make our initial download delays closer to those from 0.2.8. Fixes
8483 another part of bug 20534; bugfix on 0.2.9.1-alpha.
8484 - When determining when to download a directory object, handle times
8485 after 2038 if the operating system supports them. (Someday this
8486 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
8487 - When using exponential backoff in test networks, use a lower
8488 exponent, so the delays do not vary as much. This helps test
8489 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
8491 o Minor features (geoip):
8492 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
8495 o Minor bugfixes (client directory scheduling):
8496 - Treat "relay too busy to answer request" as a failed request and a
8497 reason to back off on our retry frequency. This is safe now that
8498 exponential backoffs retry indefinitely, and avoids a bug where we
8499 would reset our download schedule erroneously. Fixes bug 20593;
8500 bugfix on 0.2.9.1-alpha.
8502 o Minor bugfixes (client, logging):
8503 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
8504 assume all nodes support EXTEND2. Use ntor whenever a key is
8505 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
8506 - On DNSPort, stop logging a BUG warning on a failed hostname
8507 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
8509 o Minor bugfixes (hidden services):
8510 - When configuring hidden services, check every hidden service
8511 directory's permissions. Previously, we only checked the last
8512 hidden service. Fixes bug 20529; bugfix the work to fix 13942
8515 o Minor bugfixes (portability):
8516 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
8517 architectures. Closes ticket 20588.
8518 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
8519 removed the ECDH ciphers which caused the tests to fail on
8520 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
8521 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
8522 20551; bugfix on 0.2.1.1-alpha.
8524 o Minor bugfixes (relay bootstrap):
8525 - Ensure relays don't make multiple connections during bootstrap.
8526 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
8528 o Minor bugfixes (relay):
8529 - Work around a memory leak in OpenSSL 1.1 when encoding public
8530 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
8531 - Avoid a small memory leak when informing worker threads about
8532 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
8533 - Do not try to parallelize workers more than 16x without the user
8534 explicitly configuring us to do so, even if we do detect more than
8535 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
8537 o Minor bugfixes (single onion services):
8538 - Start correctly when creating a single onion service in a
8539 directory that did not previously exist. Fixes bug 20484; bugfix
8542 o Minor bugfixes (testing):
8543 - Avoid a unit test failure on systems with over 16 detectable CPU
8544 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
8547 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
8548 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
8549 - Module-level documentation for several more modules. Closes
8550 tickets 19287 and 19290.
8553 Changes in version 0.2.8.9 - 2016-10-17
8554 Tor 0.2.8.9 backports a fix for a security hole in previous versions
8555 of Tor that would allow a remote attacker to crash a Tor client,
8556 hidden service, relay, or authority. All Tor users should upgrade to
8557 this version, or to 0.2.9.4-alpha. Patches will be released for older
8560 o Major features (security fixes, also in 0.2.9.4-alpha):
8561 - Prevent a class of security bugs caused by treating the contents
8562 of a buffer chunk as if they were a NUL-terminated string. At
8563 least one such bug seems to be present in all currently used
8564 versions of Tor, and would allow an attacker to remotely crash
8565 most Tor instances, especially those compiled with extra compiler
8566 hardening. With this defense in place, such bugs can't crash Tor,
8567 though we should still fix them as they occur. Closes ticket
8568 20384 (TROVE-2016-10-001).
8570 o Minor features (geoip):
8571 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
8575 Changes in version 0.2.9.4-alpha - 2016-10-17
8576 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
8577 that would allow a remote attacker to crash a Tor client, hidden
8578 service, relay, or authority. All Tor users should upgrade to this
8579 version, or to 0.2.8.9. Patches will be released for older versions
8582 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
8583 previous versions of Tor, including the implementation of a feature to
8584 future- proof the Tor ecosystem against protocol changes, some bug
8585 fixes necessary for Tor Browser to use unix domain sockets correctly,
8586 and several portability improvements. We anticipate that this will be
8587 the last alpha in the Tor 0.2.9 series, and that the next release will
8588 be a release candidate.
8590 o Major features (security fixes):
8591 - Prevent a class of security bugs caused by treating the contents
8592 of a buffer chunk as if they were a NUL-terminated string. At
8593 least one such bug seems to be present in all currently used
8594 versions of Tor, and would allow an attacker to remotely crash
8595 most Tor instances, especially those compiled with extra compiler
8596 hardening. With this defense in place, such bugs can't crash Tor,
8597 though we should still fix them as they occur. Closes ticket
8598 20384 (TROVE-2016-10-001).
8600 o Major features (subprotocol versions):
8601 - Tor directory authorities now vote on a set of recommended
8602 subprotocol versions, and on a set of required subprotocol
8603 versions. Clients and relays that lack support for a _required_
8604 subprotocol version will not start; those that lack support for a
8605 _recommended_ subprotocol version will warn the user to upgrade.
8606 Closes ticket 19958; implements part of proposal 264.
8607 - Tor now uses "subprotocol versions" to indicate compatibility.
8608 Previously, versions of Tor looked at the declared Tor version of
8609 a relay to tell whether they could use a given feature. Now, they
8610 should be able to rely on its declared subprotocol versions. This
8611 change allows compatible implementations of the Tor protocol(s) to
8612 exist without pretending to be 100% bug-compatible with particular
8613 releases of Tor itself. Closes ticket 19958; implements part of
8616 o Minor feature (fallback directories):
8617 - Remove broken fallbacks from the hard-coded fallback directory
8618 list. Closes ticket 20190; patch by teor.
8620 o Minor features (client, directory):
8621 - Since authorities now omit all routers that lack the Running and
8622 Valid flags, we assume that any relay listed in the consensus must
8623 have those flags. Closes ticket 20001; implements part of
8626 o Minor features (compilation, portability):
8627 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
8630 o Minor features (development tools, etags):
8631 - Teach the "make tags" Makefile target how to correctly find
8632 "MOCK_IMPL" function definitions. Patch from nherring; closes
8635 o Minor features (geoip):
8636 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
8639 o Minor features (unix domain sockets):
8640 - When configuring a unix domain socket for a SocksPort,
8641 ControlPort, or Hidden service, you can now wrap the address in
8642 quotes, using C-style escapes inside the quotes. This allows unix
8643 domain socket paths to contain spaces.
8645 o Minor features (virtual addresses):
8646 - Increase the maximum number of bits for the IPv6 virtual network
8647 prefix from 16 to 104. In this way, the condition for address
8648 allocation is less restrictive. Closes ticket 20151; feature
8651 o Minor bugfixes (address discovery):
8652 - Stop reordering IP addresses returned by the OS. This makes it
8653 more likely that Tor will guess the same relay IP address every
8654 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
8655 Reported by René Mayrhofer, patch by "cypherpunks".
8657 o Minor bugfixes (client, unix domain sockets):
8658 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
8659 the client address is meaningless. Fixes bug 20261; bugfix
8662 o Minor bugfixes (compilation, OpenBSD):
8663 - Detect Libevent2 functions correctly on systems that provide
8664 libevent2, but where libevent1 is linked with -levent. Fixes bug
8665 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
8667 o Minor bugfixes (configuration):
8668 - When parsing quoted configuration values from the torrc file,
8669 handle windows line endings correctly. Fixes bug 19167; bugfix on
8670 0.2.0.16-alpha. Patch from "Pingl".
8672 o Minor bugfixes (getpass):
8673 - Defensively fix a non-triggerable heap corruption at do_getpass()
8674 to protect ourselves from mistakes in the future. Fixes bug
8675 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
8678 o Minor bugfixes (hidden service):
8679 - Allow hidden services to run on IPv6 addresses even when the
8680 IPv6Exit option is not set. Fixes bug 18357; bugfix
8684 - Add module-level internal documentation for 36 C files that
8685 previously didn't have a high-level overview. Closes ticket #20385.
8687 o Required libraries:
8688 - When building with OpenSSL, Tor now requires version 1.0.1 or
8689 later. OpenSSL 1.0.0 and earlier are no longer supported by the
8690 OpenSSL team, and should not be used. Closes ticket 20303.
8693 Changes in version 0.2.9.3-alpha - 2016-09-23
8694 Tor 0.2.9.3-alpha adds improved support for entities that want to make
8695 high-performance services available through the Tor .onion mechanism
8696 without themselves receiving anonymity as they host those services. It
8697 also tries harder to ensure that all steps on a circuit are using the
8698 strongest crypto possible, strengthens some TLS properties, and
8699 resolves several bugs -- including a pair of crash bugs from the 0.2.8
8700 series. Anybody running an earlier version of 0.2.9.x should upgrade.
8702 o Major bugfixes (crash, also in 0.2.8.8):
8703 - Fix a complicated crash bug that could affect Tor clients
8704 configured to use bridges when replacing a networkstatus consensus
8705 in which one of their bridges was mentioned. OpenBSD users saw
8706 more crashes here, but all platforms were potentially affected.
8707 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
8709 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
8710 - Fix a timing-dependent assertion failure that could occur when we
8711 tried to flush from a circuit after having freed its cells because
8712 of an out-of-memory condition. Fixes bug 20203; bugfix on
8713 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
8716 o Major features (circuit building, security):
8717 - Authorities, relays and clients now require ntor keys in all
8718 descriptors, for all hops (except for rare hidden service protocol
8719 cases), for all circuits, and for all other roles. Part of
8721 - Tor authorities, relays, and clients only use ntor, except for
8722 rare cases in the hidden service protocol. Part of ticket 19163.
8724 o Major features (single-hop "hidden" services):
8725 - Add experimental HiddenServiceSingleHopMode and
8726 HiddenServiceNonAnonymousMode options. When both are set to 1,
8727 every hidden service on a Tor instance becomes a non-anonymous
8728 Single Onion Service. Single Onions make one-hop (direct)
8729 connections to their introduction and renzedvous points. One-hop
8730 circuits make Single Onion servers easily locatable, but clients
8731 remain location-anonymous. This is compatible with the existing
8732 hidden service implementation, and works on the current tor
8733 network without any changes to older relays or clients. Implements
8734 proposal 260, completes ticket 17178. Patch by teor and asn.
8736 o Major features (resource management):
8737 - Tor can now notice it is about to run out of sockets, and
8738 preemptively close connections of lower priority. (This feature is
8739 off by default for now, since the current prioritizing method is
8740 yet not mature enough. You can enable it by setting
8741 "DisableOOSCheck 0", but watch out: it might close some sockets
8742 you would rather have it keep.) Closes ticket 18640.
8744 o Major bugfixes (circuit building):
8745 - Hidden service client-to-intro-point and service-to-rendezvous-
8746 point circuits use the TAP key supplied by the protocol, to avoid
8747 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
8749 o Major bugfixes (compilation, OpenBSD):
8750 - Fix a Libevent-detection bug in our autoconf script that would
8751 prevent Tor from linking successfully on OpenBSD. Patch from
8752 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
8754 o Major bugfixes (hidden services):
8755 - Clients now require hidden services to include the TAP keys for
8756 their intro points in the hidden service descriptor. This prevents
8757 an inadvertent upgrade to ntor, which a malicious hidden service
8758 could use to distinguish clients by consensus version. Fixes bug
8759 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
8761 o Minor features (security, TLS):
8762 - Servers no longer support clients that without AES ciphersuites.
8763 (3DES is no longer considered an acceptable cipher.) We believe
8764 that no such Tor clients currently exist, since Tor has required
8765 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
8767 o Minor feature (fallback directories):
8768 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
8769 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
8770 2016. Closes ticket 20190; patch by teor.
8772 o Minor features (geoip, also in 0.2.8.8):
8773 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
8776 o Minor feature (port flags):
8777 - Add new flags to the *Port options to finer control over which
8778 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
8779 and the synthetic flag OnionTrafficOnly, which is equivalent to
8780 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
8781 18693; patch by "teor".
8783 o Minor features (directory authority):
8784 - After voting, if the authorities decide that a relay is not
8785 "Valid", they no longer include it in the consensus at all. Closes
8786 ticket 20002; implements part of proposal 272.
8788 o Minor features (testing):
8789 - Disable memory protections on OpenBSD when performing our unit
8790 tests for memwipe(). The test deliberately invokes undefined
8791 behavior, and the OpenBSD protections interfere with this. Patch
8792 from "rubiate". Closes ticket 20066.
8794 o Minor features (testing, ipv6):
8795 - Add the single-onion and single-onion-ipv6 chutney targets to
8796 "make test-network-all". This requires a recent chutney version
8797 with the single onion network flavours (git c72a652 or later).
8798 Closes ticket 20072; patch by teor.
8799 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
8800 tests. Remove bridges+hs, as it's somewhat redundant. This
8801 requires a recent chutney version that supports IPv6 clients,
8802 relays, and authorities. Closes ticket 20069; patch by teor.
8804 o Minor features (Tor2web):
8805 - Make Tor2web clients respect ReachableAddresses. This feature was
8806 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
8807 0.2.8.7. Implements feature 20034. Patch by teor.
8809 o Minor features (unit tests):
8810 - We've done significant work to make the unit tests run faster.
8811 - Our link-handshake unit tests now check that when invalid
8812 handshakes fail, they fail with the error messages we expected.
8813 - Our unit testing code that captures log messages no longer
8814 prevents them from being written out if the user asked for them
8815 (by passing --debug or --info or or --notice --warn to the "test"
8816 binary). This change prevents us from missing unexpected log
8817 messages simply because we were looking for others. Related to
8819 - The unit tests now log all warning messages with the "BUG" flag.
8820 Previously, they only logged errors by default. This change will
8821 help us make our testing code more correct, and make sure that we
8822 only hit this code when we mean to. In the meantime, however,
8823 there will be more warnings in the unit test logs than before.
8824 This is preparatory work for ticket 19999.
8825 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
8826 assertion as a test failure.
8828 o Minor bug fixes (circuits):
8829 - Use the CircuitBuildTimeout option whenever
8830 LearnCircuitBuildTimeout is disabled. Previously, we would respect
8831 the option when a user disabled it, but not when it was disabled
8832 because some other option was set. Fixes bug 20073; bugfix on
8833 0.2.4.12-alpha. Patch by teor.
8835 o Minor bugfixes (allocation):
8836 - Change how we allocate memory for large chunks on buffers, to
8837 avoid a (currently impossible) integer overflow, and to waste less
8838 space when allocating unusually large chunks. Fixes bug 20081;
8839 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
8840 - Always include orconfig.h before including any other C headers.
8841 Sometimes, it includes macros that affect the behavior of the
8842 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
8843 first version to use AC_USE_SYSTEM_EXTENSIONS).
8844 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
8845 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
8846 Patch from Gisle Vanem.
8847 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
8848 They apparently require a set of annotations that we aren't
8849 currently using, and they create false positives in our pthreads
8850 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
8852 o Minor bugfixes (directory authority):
8853 - Die with a more useful error when the operator forgets to place
8854 the authority_signing_key file into the keys directory. This
8855 avoids an uninformative assert & traceback about having an invalid
8856 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
8857 - When allowing private addresses, mark Exits that only exit to
8858 private locations as such. Fixes bug 20064; bugfix
8861 o Minor bugfixes (documentation):
8862 - Document the default PathsNeededToBuildCircuits value that's used
8863 by clients when the directory authorities don't set
8864 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
8865 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
8866 - Fix manual for the User option: it takes a username, not a UID.
8867 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
8870 o Minor bugfixes (hidden services):
8871 - Stop logging intro point details to the client log on certain
8872 error conditions. Fixed as part of bug 20012; bugfix on
8873 0.2.4.8-alpha. Patch by teor.
8875 o Minor bugfixes (IPv6, testing):
8876 - Check for IPv6 correctly on Linux when running test networks.
8877 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
8879 o Minor bugfixes (Linux seccomp2 sandbox):
8880 - Add permission to run the sched_yield() and sigaltstack() system
8881 calls, in order to support versions of Tor compiled with asan or
8882 ubsan code that use these calls. Now "sandbox 1" and
8883 "--enable-expensive-hardening" should be compatible on more
8884 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
8886 o Minor bugfixes (logging):
8887 - When logging a message from the BUG() macro, be explicit about
8888 what we were asserting. Previously we were confusing what we were
8889 asserting with what the bug was. Fixes bug 20093; bugfix
8891 - When we are unable to remove the bw_accounting file, do not warn
8892 if the reason we couldn't remove it was that it didn't exist.
8893 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
8895 o Minor bugfixes (option parsing):
8896 - Count unix sockets when counting client listeners (SOCKS, Trans,
8897 NATD, and DNS). This has no user-visible behaviour changes: these
8898 options are set once, and never read. Required for correct
8899 behaviour in ticket 17178. Fixes bug 19677; bugfix on
8900 0.2.6.3-alpha. Patch by teor.
8902 o Minor bugfixes (options):
8903 - Check the consistency of UseEntryGuards and EntryNodes more
8904 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
8906 - Stop changing the configured value of UseEntryGuards on
8907 authorities and Tor2web clients. Fixes bug 20074; bugfix on
8908 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
8911 o Minor bugfixes (Tor2web):
8912 - Prevent Tor2web clients running hidden services, these services
8913 are not anonymous due to the one-hop client paths. Fixes bug
8914 19678. Patch by teor.
8916 o Minor bugfixes (unit tests):
8917 - Fix a shared-random unit test that was failing on big endian
8918 architectures due to internal representation of a integer copied
8919 to a buffer. The test is changed to take a full 32 bytes of data
8920 and use the output of a python script that make the COMMIT and
8921 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
8923 - The tor_tls_server_info_callback unit test no longer crashes when
8924 debug-level logging is turned on. Fixes bug 20041; bugfix
8928 Changes in version 0.2.8.8 - 2016-09-23
8929 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
8930 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
8931 who select public relays as their bridges.
8933 o Major bugfixes (crash):
8934 - Fix a complicated crash bug that could affect Tor clients
8935 configured to use bridges when replacing a networkstatus consensus
8936 in which one of their bridges was mentioned. OpenBSD users saw
8937 more crashes here, but all platforms were potentially affected.
8938 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
8940 o Major bugfixes (relay, OOM handler):
8941 - Fix a timing-dependent assertion failure that could occur when we
8942 tried to flush from a circuit after having freed its cells because
8943 of an out-of-memory condition. Fixes bug 20203; bugfix on
8944 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
8947 o Minor feature (fallback directories):
8948 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
8949 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
8950 2016. Closes ticket 20190; patch by teor.
8952 o Minor features (geoip):
8953 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
8957 Changes in version 0.2.9.2-alpha - 2016-08-24
8958 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
8959 several new features and bugfixes. It also includes an important
8960 authority update and an important bugfix from 0.2.8.7. Everyone who
8961 sets the ReachableAddresses option, and all bridges, are strongly
8962 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
8964 o Directory authority changes (also in 0.2.8.7):
8965 - The "Tonga" bridge authority has been retired; the new bridge
8966 authority is "Bifroest". Closes tickets 19728 and 19690.
8968 o Major bugfixes (client, security, also in 0.2.8.7):
8969 - Only use the ReachableAddresses option to restrict the first hop
8970 in a path. In earlier versions of 0.2.8.x, it would apply to
8971 every hop in the path, with a possible degradation in anonymity
8972 for anyone using an uncommon ReachableAddress setting. Fixes bug
8973 19973; bugfix on 0.2.8.2-alpha.
8975 o Major features (user interface):
8976 - Tor now supports the ability to declare options deprecated, so
8977 that we can recommend that people stop using them. Previously,
8978 this was done in an ad-hoc way. Closes ticket 19820.
8980 o Major bugfixes (directory downloads):
8981 - Avoid resetting download status for consensuses hourly, since we
8982 already have another, smarter retry mechanism. Fixes bug 8625;
8983 bugfix on 0.2.0.9-alpha.
8985 o Minor features (config):
8986 - Warn users when descriptor and port addresses are inconsistent.
8987 Mitigates bug 13953; patch by teor.
8989 o Minor features (geoip):
8990 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
8993 o Minor features (user interface):
8994 - There is a new --list-deprecated-options command-line option to
8995 list all of the deprecated options. Implemented as part of
8998 o Minor bugfixes (code style):
8999 - Fix an integer signedness conversion issue in the case conversion
9000 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
9002 o Minor bugfixes (compilation):
9003 - Build correctly on versions of libevent2 without support for
9004 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
9006 - Fix a compilation warning on GCC versions before 4.6. Our
9007 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
9008 when it is also required as an argument to the compiler pragma.
9009 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
9011 o Minor bugfixes (compilation, also in 0.2.8.7):
9012 - Remove an inappropriate "inline" in tortls.c that was causing
9013 warnings on older versions of GCC. Fixes bug 19903; bugfix
9016 o Minor bugfixes (fallback directories, also in 0.2.8.7):
9017 - Avoid logging a NULL string pointer when loading fallback
9018 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
9019 and 0.2.8.1-alpha. Report and patch by "rubiate".
9021 o Minor bugfixes (logging):
9022 - Log a more accurate message when we fail to dump a microdescriptor.
9023 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
9025 o Minor bugfixes (memory leak):
9026 - Fix a series of slow memory leaks related to parsing torrc files
9027 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
9029 o Deprecated features:
9030 - A number of DNS-cache-related sub-options for client ports are now
9031 deprecated for security reasons, and may be removed in a future
9032 version of Tor. (We believe that client-side DNS caching is a bad
9033 idea for anonymity, and you should not turn it on.) The options
9034 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
9035 UseIPv4Cache, and UseIPv6Cache.
9036 - A number of options are deprecated for security reasons, and may
9037 be removed in a future version of Tor. The options are:
9038 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
9039 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
9040 CloseHSClientCircuitsImmediatelyOnTimeout,
9041 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
9042 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
9043 UseNTorHandshake, and WarnUnsafeSocks.
9044 - The *ListenAddress options are now deprecated as unnecessary: the
9045 corresponding *Port options should be used instead. These options
9046 may someday be removed. The affected options are:
9047 ControlListenAddress, DNSListenAddress, DirListenAddress,
9048 NATDListenAddress, ORListenAddress, SocksListenAddress,
9049 and TransListenAddress.
9052 - Correct the IPv6 syntax in our documentation for the
9053 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
9056 - We no longer include the (dead, deprecated) bufferevent code in
9057 Tor. Closes ticket 19450. Based on a patch from U+039b.
9060 Changes in version 0.2.8.7 - 2016-08-24
9061 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
9062 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
9063 who sets the ReachableAddresses option, and all bridges, are strongly
9064 encouraged to upgrade.
9066 o Directory authority changes:
9067 - The "Tonga" bridge authority has been retired; the new bridge
9068 authority is "Bifroest". Closes tickets 19728 and 19690.
9070 o Major bugfixes (client, security):
9071 - Only use the ReachableAddresses option to restrict the first hop
9072 in a path. In earlier versions of 0.2.8.x, it would apply to
9073 every hop in the path, with a possible degradation in anonymity
9074 for anyone using an uncommon ReachableAddress setting. Fixes bug
9075 19973; bugfix on 0.2.8.2-alpha.
9077 o Minor features (geoip):
9078 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
9081 o Minor bugfixes (compilation):
9082 - Remove an inappropriate "inline" in tortls.c that was causing
9083 warnings on older versions of GCC. Fixes bug 19903; bugfix
9086 o Minor bugfixes (fallback directories):
9087 - Avoid logging a NULL string pointer when loading fallback
9088 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
9089 and 0.2.8.1-alpha. Report and patch by "rubiate".
9092 Changes in version 0.2.9.1-alpha - 2016-08-08
9093 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
9094 series. It improves our support for hardened builds and compiler
9095 warnings, deploys some critical infrastructure for improvements to
9096 hidden services, includes a new timing backend that we hope to use for
9097 better support for traffic padding, makes it easier for programmers to
9098 log unexpected events, and contains other small improvements to
9099 security, correctness, and performance.
9101 Below are the changes since 0.2.8.6.
9103 o New system requirements:
9104 - Tor now requires Libevent version 2.0.10-stable or later. Older
9105 versions of Libevent have less efficient backends for several
9106 platforms, and lack the DNS code that we use for our server-side
9107 DNS support. This implements ticket 19554.
9108 - Tor now requires zlib version 1.2 or later, for security,
9109 efficiency, and (eventually) gzip support. (Back when we started,
9110 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
9111 released in 2003. We recommend the latest version.)
9113 o Major features (build, hardening):
9114 - Tor now builds with -ftrapv by default on compilers that support
9115 it. This option detects signed integer overflow (which C forbids),
9116 and turns it into a hard-failure. We do not apply this option to
9117 code that needs to run in constant time to avoid side-channels;
9118 instead, we use -fwrapv in that code. Closes ticket 17983.
9119 - When --enable-expensive-hardening is selected, stop applying the
9120 clang/gcc sanitizers to code that needs to run in constant time.
9121 Although we are aware of no introduced side-channels, we are not
9122 able to prove that there are none. Related to ticket 17983.
9124 o Major features (compilation):
9125 - Our big list of extra GCC warnings is now enabled by default when
9126 building with GCC (or with anything like Clang that claims to be
9127 GCC-compatible). To make all warnings into fatal compilation
9128 errors, pass --enable-fatal-warnings to configure. Closes
9130 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
9131 turn on C and POSIX extensions. (Previously, we attempted to do
9132 this on an ad hoc basis.) Closes ticket 19139.
9134 o Major features (directory authorities, hidden services):
9135 - Directory authorities can now perform the shared randomness
9136 protocol specified by proposal 250. Using this protocol, directory
9137 authorities generate a global fresh random value every day. In the
9138 future, this value will be used by hidden services to select
9139 HSDirs. This release implements the directory authority feature;
9140 the hidden service side will be implemented in the future as part
9141 of proposal 224. Resolves ticket 16943; implements proposal 250.
9143 o Major features (downloading, random exponential backoff):
9144 - When we fail to download an object from a directory service, wait
9145 for an (exponentially increasing) randomized amount of time before
9146 retrying, rather than a fixed interval as we did before. This
9147 prevents a group of Tor instances from becoming too synchronized,
9148 or a single Tor instance from becoming too predictable, in its
9149 download schedule. Closes ticket 15942.
9151 o Major bugfixes (exit policies):
9152 - Avoid disclosing exit outbound bind addresses, configured port
9153 bind addresses, and local interface addresses in relay descriptors
9154 by default under ExitPolicyRejectPrivate. Instead, only reject
9155 these (otherwise unlisted) addresses if
9156 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
9157 0.2.7.2-alpha. Patch by teor.
9159 o Major bugfixes (hidden service client):
9160 - Allow Tor clients with appropriate controllers to work with
9161 FetchHidServDescriptors set to 0. Previously, this option also
9162 disabled descriptor cache lookup, thus breaking hidden services
9163 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
9165 o Minor features (build, hardening):
9166 - Detect and work around a libclang_rt problem that would prevent
9167 clang from finding __mulodi4() on some 32-bit platforms, and thus
9168 keep -ftrapv from linking on those systems. Closes ticket 19079.
9169 - When building on a system without runtime support for the runtime
9170 hardening options, try to log a useful warning at configuration
9171 time, rather than an incomprehensible warning at link time. If
9172 expensive hardening was requested, this warning becomes an error.
9173 Closes ticket 18895.
9175 o Minor features (code safety):
9176 - In our integer-parsing functions, ensure that maxiumum value we
9177 give is no smaller than the minimum value. Closes ticket 19063;
9180 o Minor features (controller):
9181 - Implement new GETINFO queries for all downloads that use
9182 download_status_t to schedule retries. This allows controllers to
9183 examine the schedule for pending downloads. Closes ticket 19323.
9184 - Allow controllers to configure basic client authorization on
9185 hidden services when they create them with the ADD_ONION control
9186 command. Implements ticket 15588. Patch by "special".
9187 - Fire a STATUS_SERVER controller event whenever the hibernation
9188 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
9190 o Minor features (directory authority):
9191 - Directory authorities now only give the Guard flag to a relay if
9192 they are also giving it the Stable flag. This change allows us to
9193 simplify path selection for clients. It should have minimal effect
9194 in practice, since >99% of Guards already have the Stable flag.
9195 Implements ticket 18624.
9196 - Directory authorities now write their v3-status-votes file out to
9197 disk earlier in the consensus process, so we have a record of the
9198 votes even if we abort the consensus process. Resolves
9201 o Minor features (hidden service):
9202 - Stop being so strict about the payload length of "rendezvous1"
9203 cells. We used to be locked in to the "TAP" handshake length, and
9204 now we can handle better handshakes like "ntor". Resolves
9207 o Minor features (infrastructure, time):
9208 - Tor now uses the operating system's monotonic timers (where
9209 available) for internal fine-grained timing. Previously we would
9210 look at the system clock, and then attempt to compensate for the
9211 clock running backwards. Closes ticket 18908.
9212 - Tor now includes an improved timer backend, so that we can
9213 efficiently support tens or hundreds of thousands of concurrent
9214 timers, as will be needed for some of our planned anti-traffic-
9215 analysis work. This code is based on William Ahern's "timeout.c"
9216 project, which implements a "tickless hierarchical timing wheel".
9217 Closes ticket 18365.
9219 o Minor features (logging):
9220 - Provide a more useful warning message when configured with an
9221 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
9222 - When dumping unparseable router descriptors, optionally store them
9223 in separate files, named by digest, up to a configurable size
9224 limit. You can change the size limit by setting the
9225 MaxUnparseableDescSizeToLog option, and disable this feature by
9226 setting that option to 0. Closes ticket 18322.
9227 - Add a set of macros to check nonfatal assertions, for internal
9228 use. Migrating more of our checks to these should help us avoid
9229 needless crash bugs. Closes ticket 18613.
9231 o Minor features (performance):
9232 - Changer the "optimistic data" extension from "off by default" to
9233 "on by default". The default was ordinarily overridden by a
9234 consensus option, but when clients were bootstrapping for the
9235 first time, they would not have a consensus to get the option
9236 from. Changing this default When fetching a consensus for the
9237 first time, use optimistic data. This saves a round-trip during
9238 startup. Closes ticket 18815.
9240 o Minor features (relay, usability):
9241 - When the directory authorities refuse a bad relay's descriptor,
9242 encourage the relay operator to contact us. Many relay operators
9243 won't notice this line in their logs, but it's a win if even a few
9244 learn why we don't like what their relay was doing. Resolves
9247 o Minor features (testing):
9248 - Let backtrace tests work correctly under AddressSanitizer. Fixes
9249 part of bug 18934; bugfix on 0.2.5.2-alpha.
9250 - Move the test-network.sh script to chutney, and modify tor's test-
9251 network.sh to call the (newer) chutney version when available.
9252 Resolves ticket 19116. Patch by teor.
9253 - Use the lcov convention for marking lines as unreachable, so that
9254 we don't count them when we're generating test coverage data.
9255 Update our coverage tools to understand this convention. Closes
9258 o Minor bugfixes (bootstrap):
9259 - Remember the directory we fetched the consensus or previous
9260 certificates from, and use it to fetch future authority
9261 certificates. This change improves bootstrapping performance.
9262 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
9264 o Minor bugfixes (build):
9265 - The test-stem and test-network makefile targets now depend only on
9266 the tor binary that they are testing. Previously, they depended on
9267 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
9268 patch from "cypherpunks".
9270 o Minor bugfixes (circuits):
9271 - Make sure extend_info_from_router() is only called on servers.
9272 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
9274 o Minor bugfixes (compilation):
9275 - When building with Clang, use a full set of GCC warnings.
9276 (Previously, we included only a subset, because of the way we
9277 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
9279 o Minor bugfixes (directory authority):
9280 - Authorities now sort the "package" lines in their votes, for ease
9281 of debugging. (They are already sorted in consensus documents.)
9282 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
9283 - When parsing a detached signature, make sure we use the length of
9284 the digest algorithm instead of an hardcoded DIGEST256_LEN in
9285 order to avoid comparing bytes out-of-bounds with a smaller digest
9286 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
9288 o Minor bugfixes (documentation):
9289 - Document the --passphrase-fd option in the tor manpage. Fixes bug
9290 19504; bugfix on 0.2.7.3-rc.
9291 - Fix the description of the --passphrase-fd option in the
9292 tor-gencert manpage. The option is used to pass the number of a
9293 file descriptor to read the passphrase from, not to read the file
9294 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
9296 o Minor bugfixes (ephemeral hidden service):
9297 - When deleting an ephemeral hidden service, close its intro points
9298 even if they are not completely open. Fixes bug 18604; bugfix
9301 o Minor bugfixes (guard selection):
9302 - Use a single entry guard even if the NumEntryGuards consensus
9303 parameter is not provided. Fixes bug 17688; bugfix
9305 - Don't mark guards as unreachable if connection_connect() fails.
9306 That function fails for local reasons, so it shouldn't reveal
9307 anything about the status of the guard. Fixes bug 14334; bugfix
9310 o Minor bugfixes (hidden service client):
9311 - Increase the minimum number of internal circuits we preemptively
9312 build from 2 to 3, so a circuit is available when a client
9313 connects to another onion service. Fixes bug 13239; bugfix
9316 o Minor bugfixes (logging):
9317 - When logging a directory ownership mismatch, log the owning
9318 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
9320 o Minor bugfixes (memory leaks):
9321 - Fix a small, uncommon memory leak that could occur when reading a
9322 truncated ed25519 key file. Fixes bug 18956; bugfix
9325 o Minor bugfixes (testing):
9326 - Allow clients to retry HSDirs much faster in test networks. Fixes
9327 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
9328 - Disable ASAN's detection of segmentation faults while running
9329 test_bt.sh, so that we can make sure that our own backtrace
9330 generation code works. Fixes another aspect of bug 18934; bugfix
9331 on 0.2.5.2-alpha. Patch from "cypherpunks".
9332 - Fix the test-network-all target on out-of-tree builds by using the
9333 correct path to the test driver script. Fixes bug 19421; bugfix
9336 o Minor bugfixes (time):
9337 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
9338 bugfix on all released tor versions.
9339 - When computing the difference between two times in milliseconds,
9340 we now round to the nearest millisecond correctly. Previously, we
9341 could sometimes round in the wrong direction. Fixes bug 19428;
9342 bugfix on 0.2.2.2-alpha.
9344 o Minor bugfixes (user interface):
9345 - Display a more accurate number of suppressed messages in the log
9346 rate-limiter. Previously, there was a potential integer overflow
9347 in the counter. Now, if the number of messages hits a maximum, the
9348 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
9350 - Fix a typo in the passphrase prompt for the ed25519 identity key.
9351 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
9353 o Code simplification and refactoring:
9354 - Remove redundant declarations of the MIN macro. Closes
9356 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
9357 Closes ticket 18462; patch from "icanhasaccount".
9358 - Split the 600-line directory_handle_command_get function into
9359 separate functions for different URL types. Closes ticket 16698.
9362 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
9363 ticket 19153. Patch from "U+039b".
9366 - Remove support for "GET /tor/bytes.txt" DirPort request, and
9367 "GETINFO dir-usage" controller request, which were only available
9368 via a compile-time option in Tor anyway. Feature was added in
9369 0.2.2.1-alpha. Resolves ticket 19035.
9370 - There is no longer a compile-time option to disable support for
9371 TransPort. (If you don't want TransPort; just don't use it.) Patch
9372 from "U+039b". Closes ticket 19449.
9375 - Run more workqueue tests as part of "make check". These had
9376 previously been implemented, but you needed to know special
9377 command-line options to enable them.
9378 - We now have unit tests for our code to reject zlib "compression
9379 bombs". (Fortunately, the code works fine.)
9382 Changes in version 0.2.8.6 - 2016-08-02
9384 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
9386 The Tor 0.2.8 series improves client bootstrapping performance,
9387 completes the authority-side implementation of improved identity
9388 keys for relays, and includes numerous bugfixes and performance
9389 improvements throughout the program. This release continues to
9390 improve the coverage of Tor's test suite. For a full list of
9391 changes since Tor 0.2.7, see the ReleaseNotes file.
9393 Changes since 0.2.8.5-rc:
9395 o Minor features (geoip):
9396 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
9399 o Minor bugfixes (compilation):
9400 - Fix a compilation warning in the unit tests on systems where char
9401 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
9403 o Minor bugfixes (fallback directories):
9404 - Remove 1 fallback that was on the hardcoded list, then opted-out,
9405 leaving 89 of the 100 fallbacks originally introduced in Tor
9406 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
9408 o Minor bugfixes (Linux seccomp2 sandbox):
9409 - Allow more syscalls when running with "Sandbox 1" enabled:
9410 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
9411 some systems, these are required for Tor to start. Fixes bug
9412 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
9413 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
9414 so that get_interface_address6_via_udp_socket_hack() can work.
9415 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
9418 Changes in version 0.2.8.5-rc - 2016-07-07
9419 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
9420 series. If we find no new bugs or regressions here, the first stable
9421 0.2.8 release will be identical to it. It has a few small bugfixes
9422 against previous versions.
9424 o Directory authority changes:
9425 - Urras is no longer a directory authority. Closes ticket 19271.
9427 o Major bugfixes (heartbeat):
9428 - Fix a regression that would crash Tor when the periodic
9429 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
9430 0.2.8.1-alpha. Reported by "kubaku".
9432 o Minor features (build):
9433 - Tor now again builds with the recent OpenSSL 1.1 development
9434 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
9435 - When building manual pages, set the timezone to "UTC", so that the
9436 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
9437 Patch from intrigeri.
9439 o Minor bugfixes (fallback directory selection):
9440 - Avoid errors during fallback selection if there are no eligible
9441 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
9444 o Minor bugfixes (IPv6, microdescriptors):
9445 - Don't check node addresses when we only have a routerstatus. This
9446 allows IPv6-only clients to bootstrap by fetching microdescriptors
9447 from fallback directory mirrors. (The microdescriptor consensus
9448 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
9451 o Minor bugfixes (logging):
9452 - Reduce pointlessly verbose log messages when directory servers
9453 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
9454 0.2.8.1-alpha. Patch by teor.
9455 - When a fallback directory changes its fingerprint from the hard-
9456 coded fingerprint, log a less severe, more explanatory log
9457 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
9459 o Minor bugfixes (Linux seccomp2 sandboxing):
9460 - Allow statistics to be written to disk when "Sandbox 1" is
9461 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
9462 0.2.6.1-alpha respectively.
9464 o Minor bugfixes (user interface):
9465 - Remove a warning message "Service [scrubbed] not found after
9466 descriptor upload". This message appears when one uses HSPOST
9467 control command to upload a service descriptor. Since there is
9468 only a descriptor and no service, showing this message is
9469 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
9471 o Fallback directory list:
9472 - Add a comment to the generated fallback directory list that
9473 explains how to comment out unsuitable fallbacks in a way that's
9474 compatible with the stem fallback parser.
9475 - Update fallback whitelist and blacklist based on relay operator
9476 emails. Blacklist unsuitable (non-working, over-volatile)
9477 fallbacks. Resolves ticket 19071. Patch by teor.
9478 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
9479 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
9480 ticket 19071; patch by teor.
9483 Changes in version 0.2.8.4-rc - 2016-06-15
9484 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
9485 If we find no new bugs or regressions here, the first stable 0.2.8
9486 release will be identical to it. It has a few small bugfixes against
9489 o Major bugfixes (user interface):
9490 - Correctly give a warning in the cases where a relay is specified
9491 by nickname, and one such relay is found, but it is not officially
9492 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
9494 o Minor features (build):
9495 - Tor now builds once again with the recent OpenSSL 1.1 development
9496 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
9498 o Minor features (geoip):
9499 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
9502 o Minor bugfixes (compilation):
9503 - Cause the unit tests to compile correctly on mingw64 versions that
9504 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
9506 o Minor bugfixes (downloading):
9507 - Predict more correctly whether we'll be downloading over HTTP when
9508 we determine the maximum length of a URL. This should avoid a
9509 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
9513 Changes in version 0.2.8.3-alpha - 2016-05-26
9514 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
9515 the course of the 0.2.8 development cycle. It improves the behavior of
9516 directory clients, fixes several crash bugs, fixes a gap in compiler
9517 hardening, and allows the full integration test suite to run on
9520 o Major bugfixes (security, client, DNS proxy):
9521 - Stop a crash that could occur when a client running with DNSPort
9522 received a query with multiple address types, and the first
9523 address type was not supported. Found and fixed by Scott Dial.
9524 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9526 o Major bugfixes (security, compilation):
9527 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
9528 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
9529 cause a compiler warning, thereby making other checks fail, and
9530 needlessly disabling compiler-hardening support. Fixes one case of
9531 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
9533 o Major bugfixes (security, directory authorities):
9534 - Fix a crash and out-of-bounds write during authority voting, when
9535 the list of relays includes duplicate ed25519 identity keys. Fixes
9536 bug 19032; bugfix on 0.2.8.2-alpha.
9538 o Major bugfixes (client, bootstrapping):
9539 - Check if bootstrap consensus downloads are still needed when the
9540 linked connection attaches. This prevents tor making unnecessary
9541 begindir-style connections, which are the only directory
9542 connections tor clients make since the fix for 18483 was merged.
9543 - Fix some edge cases where consensus download connections may not
9544 have been closed, even though they were not needed. Related to fix
9546 - Make relays retry consensus downloads the correct number of times,
9547 rather than the more aggressive client retry count. Fixes part of
9549 - Stop downloading consensuses when we have a consensus, even if we
9550 don't have all the certificates for it yet. Fixes bug 18809;
9551 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
9553 o Major bugfixes (directory mirrors):
9554 - Decide whether to advertise begindir support in the the same way
9555 we decide whether to advertise our DirPort. Allowing these
9556 decisions to become out-of-sync led to surprising behavior like
9557 advertising begindir support when hibernation made us not
9558 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
9561 o Major bugfixes (IPv6 bridges, client):
9562 - Actually use IPv6 addresses when selecting directory addresses for
9563 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
9566 o Major bugfixes (key management):
9567 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9568 pointer to the previous (uninitialized) key value. The impact here
9569 should be limited to a difficult-to-trigger crash, if OpenSSL is
9570 running an engine that makes key generation failures possible, or
9571 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9572 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9575 o Major bugfixes (testing):
9576 - Fix a bug that would block 'make test-network-all' on systems where
9577 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
9578 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
9579 bugfix on 0.2.8.1-alpha.
9581 o Minor features (clients):
9582 - Make clients, onion services, and bridge relays always use an
9583 encrypted begindir connection for directory requests. Resolves
9584 ticket 18483. Patch by "teor".
9586 o Minor features (fallback directory mirrors):
9587 - Give each fallback the same weight for client selection; restrict
9588 fallbacks to one per operator; report fallback directory detail
9589 changes when rebuilding list; add new fallback directory mirrors
9590 to the whitelist; and many other minor simplifications and fixes.
9591 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
9592 0.2.8.1-alpha; patch by "teor".
9593 - Replace the 21 fallbacks generated in January 2016 and included in
9594 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
9595 2016. Closes task 17158; patch by "teor".
9597 o Minor features (geoip):
9598 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
9601 o Minor bugfixes (assert, portability):
9602 - Fix an assertion failure in memarea.c on systems where "long" is
9603 shorter than the size of a pointer. Fixes bug 18716; bugfix
9606 o Minor bugfixes (bootstrap):
9607 - Consistently use the consensus download schedule for authority
9608 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
9610 o Minor bugfixes (build):
9611 - Remove a pair of redundant AM_CONDITIONAL declarations from
9612 configure.ac. Fixes one final case of bug 17744; bugfix
9614 - Resolve warnings when building on systems that are concerned with
9615 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
9617 - When libscrypt.h is found, but no libscrypt library can be linked,
9618 treat libscrypt as absent. Fixes bug 19161; bugfix
9621 o Minor bugfixes (client):
9622 - Turn all TestingClientBootstrap* into non-testing torrc options.
9623 This changes simply renames them by removing "Testing" in front of
9624 them and they do not require TestingTorNetwork to be enabled
9625 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
9626 - Make directory node selection more reliable, mainly for IPv6-only
9627 clients and clients with few reachable addresses. Fixes bug 18929;
9628 bugfix on 0.2.8.1-alpha. Patch by "teor".
9630 o Minor bugfixes (controller, microdescriptors):
9631 - Make GETINFO dir/status-vote/current/consensus conform to the
9632 control specification by returning "551 Could not open cached
9633 consensus..." when not caching consensuses. Fixes bug 18920;
9634 bugfix on 0.2.2.6-alpha.
9636 o Minor bugfixes (crypto, portability):
9637 - The SHA3 and SHAKE routines now produce the correct output on Big
9638 Endian systems. No code calls either algorithm yet, so this is
9639 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
9640 - Tor now builds again with the recent OpenSSL 1.1 development
9641 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
9644 o Minor bugfixes (directories):
9645 - When fetching extrainfo documents, compare their SHA256 digests
9646 and Ed25519 signing key certificates with the routerinfo that led
9647 us to fetch them, rather than with the most recent routerinfo.
9648 Otherwise we generate many spurious warnings about mismatches.
9649 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
9651 o Minor bugfixes (logging):
9652 - When we can't generate a signing key because OfflineMasterKey is
9653 set, do not imply that we should have been able to load it. Fixes
9654 bug 18133; bugfix on 0.2.7.2-alpha.
9655 - Stop periodic_event_dispatch() from blasting twelve lines per
9656 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
9657 - When rejecting a misformed INTRODUCE2 cell, only log at
9658 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
9660 o Minor bugfixes (pluggable transports):
9661 - Avoid reporting a spurious error when we decide that we don't need
9662 to terminate a pluggable transport because it has already exited.
9663 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
9665 o Minor bugfixes (pointer arithmetic):
9666 - Fix a bug in memarea_alloc() that could have resulted in remote
9667 heap write access, if Tor had ever passed an unchecked size to
9668 memarea_alloc(). Fortunately, all the sizes we pass to
9669 memarea_alloc() are pre-checked to be less than 128 kilobytes.
9670 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
9673 o Minor bugfixes (relays):
9674 - Consider more config options when relays decide whether to
9675 regenerate their descriptor. Fixes more of bug 12538; bugfix
9677 - Resolve some edge cases where we might launch an ORPort
9678 reachability check even when DisableNetwork is set. Noticed while
9679 fixing bug 18616; bugfix on 0.2.3.9-alpha.
9681 o Minor bugfixes (statistics):
9682 - We now include consensus downloads via IPv6 in our directory-
9683 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
9685 o Minor bugfixes (testing):
9686 - Allow directories in small networks to bootstrap by skipping
9687 DirPort checks when the consensus has no exits. Fixes bug 19003;
9688 bugfix on 0.2.8.1-alpha. Patch by teor.
9689 - Fix a small memory leak that would occur when the
9690 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
9691 bugfix on 0.2.5.2-alpha.
9693 o Minor bugfixes (time handling):
9694 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
9695 field. Otherwise, our unit tests crash on Windows. Fixes bug
9696 18977; bugfix on 0.2.2.25-alpha.
9699 - Document the contents of the 'datadir/keys' subdirectory in the
9700 manual page. Closes ticket 17621.
9701 - Stop recommending use of nicknames to identify relays in our
9702 MapAddress documentation. Closes ticket 18312.
9705 Changes in version 0.2.8.2-alpha - 2016-03-28
9706 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
9707 bugs in earlier versions of Tor, including some that prevented
9708 authorities using Tor 0.2.7.x from running correctly. IPv6 and
9709 directory support should also be much improved.
9711 o New system requirements:
9712 - Tor no longer supports versions of OpenSSL with a broken
9713 implementation of counter mode. (This bug was present in OpenSSL
9714 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
9715 longer runs with, these versions.
9716 - Tor no longer attempts to support platforms where the "time_t"
9717 type is unsigned. (To the best of our knowledge, only OpenVMS does
9718 this, and Tor has never actually built on OpenVMS.) Closes
9720 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
9721 later (released in 2008 and 2009 respectively). If you are
9722 building Tor from the git repository instead of from the source
9723 distribution, and your tools are older than this, you will need to
9724 upgrade. Closes ticket 17732.
9726 o Major bugfixes (security, pointers):
9727 - Avoid a difficult-to-trigger heap corruption attack when extending
9728 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9729 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9730 Reported by Guido Vranken.
9732 o Major bugfixes (bridges, pluggable transports):
9733 - Modify the check for OR connections to private addresses. Allow
9734 bridges on private addresses, including pluggable transports that
9735 ignore the (potentially private) address in the bridge line. Fixes
9736 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
9738 o Major bugfixes (compilation):
9739 - Repair hardened builds under the clang compiler. Previously, our
9740 use of _FORTIFY_SOURCE would conflict with clang's address
9741 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
9743 o Major bugfixes (crash on shutdown):
9744 - Correctly handle detaching circuits from muxes when shutting down.
9745 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
9746 - Fix an assert-on-exit bug related to counting memory usage in
9747 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
9749 o Major bugfixes (crash on startup):
9750 - Fix a segfault during startup: If a Unix domain socket was
9751 configured as listener (such as a ControlSocket or a SocksPort
9752 "unix:" socket), and tor was started as root but not configured to
9753 switch to another user, tor would segfault while trying to string
9754 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
9757 o Major bugfixes (dns proxy mode, crash):
9758 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9759 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9761 o Major bugfixes (relays, bridge clients):
9762 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
9763 bridge clients use the address configured in the bridge line.
9764 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
9767 o Major bugfixes (voting):
9768 - Actually enable support for authorities to match routers by their
9769 Ed25519 identities. Previously, the code had been written, but
9770 some debugging code that had accidentally been left in the
9771 codebase made it stay turned off. Fixes bug 17702; bugfix
9773 - When collating votes by Ed25519 identities, authorities now
9774 include a "NoEdConsensus" flag if the ed25519 value (or lack
9775 thereof) for a server does not reflect the majority consensus.
9776 Related to bug 17668; bugfix on 0.2.7.2-alpha.
9777 - When generating a vote with keypinning disabled, never include two
9778 entries for the same ed25519 identity. This bug was causing
9779 authorities to generate votes that they could not parse when a
9780 router violated key pinning by changing its RSA identity but
9781 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
9782 18318. Bugfix on 0.2.7.2-alpha.
9784 o Minor features (security, win32):
9785 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
9786 attack. Fixes bug 18123; bugfix on all tor versions. Patch
9789 o Minor features (bug-resistance):
9790 - Make Tor survive errors involving connections without a
9791 corresponding event object. Previously we'd fail with an
9792 assertion; now we produce a log message. Related to bug 16248.
9794 o Minor features (build):
9795 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
9796 as having possible IPFW support. Closes ticket 18448. Patch from
9799 o Minor features (code hardening):
9800 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
9801 level code, to harden against accidental failures to NUL-
9802 terminate. Part of ticket 17852. Patch from jsturgix. Found
9805 o Minor features (crypto):
9806 - Validate the hard-coded Diffie-Hellman parameters and ensure that
9807 p is a safe prime, and g is a suitable generator. Closes
9810 o Minor features (geoip):
9811 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
9814 o Minor features (hidden service directory):
9815 - Streamline relay-side hsdir handling: when relays consider whether
9816 to accept an uploaded hidden service descriptor, they no longer
9817 check whether they are one of the relays in the network that is
9818 "supposed" to handle that descriptor. Implements ticket 18332.
9820 o Minor features (IPv6):
9821 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
9822 to 1, tor prefers IPv6 directory addresses.
9823 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
9824 avoids using IPv4 for client OR and directory connections.
9825 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
9826 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
9827 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
9829 o Minor features (linux seccomp2 sandbox):
9830 - Reject attempts to change our Address with "Sandbox 1" enabled.
9831 Changing Address with Sandbox turned on would never actually work,
9832 but previously it would fail in strange and confusing ways. Found
9835 o Minor features (robustness):
9836 - Exit immediately with an error message if the code attempts to use
9837 Libevent without having initialized it. This should resolve some
9838 frequently-made mistakes in our unit tests. Closes ticket 18241.
9840 o Minor features (unix domain sockets):
9841 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
9842 Unix domain sockets without checking the permissions on the parent
9843 directory. (Tor checks permissions by default because some
9844 operating systems only check permissions on the parent directory.
9845 However, some operating systems do look at permissions on the
9846 socket, and tor's default check is unneeded.) Closes ticket 18458.
9849 o Minor bugfixes (exit policies, security):
9850 - Refresh an exit relay's exit policy when interface addresses
9851 change. Previously, tor only refreshed the exit policy when the
9852 configured external address changed. Fixes bug 18208; bugfix on
9853 0.2.7.3-rc. Patch by teor.
9855 o Minor bugfixes (security, hidden services):
9856 - Prevent hidden services connecting to client-supplied rendezvous
9857 addresses that are reserved as internal or multicast. Fixes bug
9858 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
9860 o Minor bugfixes (build):
9861 - Do not link the unit tests against both the testing and non-
9862 testing versions of the static libraries. Fixes bug 18490; bugfix
9864 - Avoid spurious failures from configure files related to calling
9865 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
9866 0.2.0.1-alpha. Patch from "cypherpunks".
9867 - Silence spurious clang-scan warnings in the ed25519_donna code by
9868 explicitly initializing some objects. Fixes bug 18384; bugfix on
9869 0.2.7.2-alpha. Patch by teor.
9871 o Minor bugfixes (client, bootstrap):
9872 - Count receipt of new microdescriptors as progress towards
9873 bootstrapping. Previously, with EntryNodes set, Tor might not
9874 successfully repopulate the guard set on bootstrapping. Fixes bug
9875 16825; bugfix on 0.2.3.1-alpha.
9877 o Minor bugfixes (code correctness):
9878 - Update to the latest version of Trunnel, which tries harder to
9879 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
9880 by clang address sanitizer. Fixes bug 18373; bugfix
9883 o Minor bugfixes (configuration):
9884 - Fix a tiny memory leak when parsing a port configuration ending in
9885 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
9887 o Minor bugfixes (containers):
9888 - If we somehow attempt to construct a heap with more than
9889 1073741822 elements, avoid an integer overflow when maintaining
9890 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
9892 o Minor bugfixes (correctness):
9893 - Fix a bad memory handling bug that would occur if we had queued a
9894 cell on a channel's incoming queue. Fortunately, we can't actually
9895 queue a cell like that as our code is constructed today, but it's
9896 best to avoid this kind of error, even if there isn't any code
9897 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
9899 o Minor bugfixes (directory):
9900 - When generating a URL for a directory server on an IPv6 address,
9901 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
9902 on 0.2.3.9-alpha. Patch from Malek.
9904 o Minor bugfixes (fallback directory mirrors):
9905 - When requesting extrainfo descriptors from a trusted directory
9906 server, check whether it is an authority or a fallback directory
9907 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
9908 0.2.4.7-alpha. Reported by atagar, patch by teor.
9910 o Minor bugfixes (hidden service, client):
9911 - Handle the case where the user makes several fast consecutive
9912 requests to the same .onion address. Previously, the first six
9913 requests would each trigger a descriptor fetch, each picking a
9914 directory (there are 6 overall) and the seventh one would fail
9915 because no directories were left, thereby triggering a close on
9916 all current directory connections asking for the hidden service.
9917 The solution here is to not close the connections if we have
9918 pending directory fetches. Fixes bug 15937; bugfix
9921 o Minor bugfixes (hidden service, control port):
9922 - Add the onion address to the HS_DESC event for the UPLOADED action
9923 both on success or failure. It was previously hardcoded with
9924 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
9926 o Minor bugfixes (hidden service, directory):
9927 - Bridges now refuse "rendezvous2" (hidden service descriptor)
9928 publish attempts. Suggested by ticket 18332.
9930 o Minor bugfixes (linux seccomp2 sandbox):
9931 - Allow the setrlimit syscall, and the prlimit and prlimit64
9932 syscalls, which some libc implementations use under the hood.
9933 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
9934 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
9935 enabled and no DNS resolvers configured. This should help TAILS
9936 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
9937 - Fix the sandbox's interoperability with unix domain sockets under
9938 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
9940 o Minor bugfixes (logging):
9941 - When logging information about an unparsable networkstatus vote or
9942 consensus, do not say "vote" when we mean consensus. Fixes bug
9943 18368; bugfix on 0.2.0.8-alpha.
9944 - Scrub service name in "unrecognized service ID" log messages.
9945 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
9946 - Downgrade logs and backtraces about IP versions to info-level.
9947 Only log backtraces once each time tor runs. Assists in diagnosing
9948 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
9949 Christian, patch by teor.
9951 o Minor bugfixes (memory safety):
9952 - Avoid freeing an uninitialized pointer when opening a socket fails
9953 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
9954 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
9956 - Correctly duplicate addresses in get_interface_address6_list().
9957 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
9958 patch by "cypherpunks".
9959 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
9961 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
9962 18672; bugfix on 0.2.5.1-alpha.
9964 o Minor bugfixes (private directory):
9965 - Prevent a race condition when creating private directories. Fixes
9966 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
9967 Patch from jsturgix. Found with Flawfinder.
9969 o Minor bugfixes (test networks, IPv6):
9970 - Allow internal IPv6 addresses in descriptors in test networks.
9971 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
9974 o Minor bugfixes (testing):
9975 - We no longer disable assertions in the unit tests when coverage is
9976 enabled. Instead, we require you to say --disable-asserts-in-tests
9977 to the configure script if you need assertions disabled in the
9978 unit tests (for example, if you want to perform branch coverage).
9979 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
9981 o Minor bugfixes (time parsing):
9982 - Avoid overflow in tor_timegm when parsing dates in and after 2038
9983 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
9984 0.0.2pre14. Patch by teor.
9986 o Minor bugfixes (tor-gencert):
9987 - Correctly handle the case where an authority operator enters a
9988 passphrase but sends an EOF before sending a newline. Fixes bug
9989 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
9991 o Code simplification and refactoring:
9992 - Quote all the string interpolations in configure.ac -- even those
9993 which we are pretty sure can't contain spaces. Closes ticket
9994 17744. Patch from zerosion.
9995 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
9996 inplace, so there's no need to have a separate implementation for
9997 the non-inplace code. Closes ticket 18258. Patch from Malek.
9998 - Simplify return types for some crypto functions that can't
9999 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
10002 - Change build messages to refer to "Fedora" instead of "Fedora
10003 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
10004 Patches from "icanhasaccount" and "cypherpunks".
10006 o Removed features:
10007 - We no longer maintain an internal freelist in memarea.c.
10008 Allocators should be good enough to make this code unnecessary,
10009 and it's doubtful that it ever had any performance benefit.
10012 - Fix several warnings from clang's address sanitizer produced in
10014 - Treat backtrace test failures as expected on FreeBSD until we
10015 solve bug 17808. Closes ticket 18204.
10018 Changes in version 0.2.8.1-alpha - 2016-02-04
10019 Tor 0.2.8.1-alpha is the first alpha release in its series. It
10020 includes numerous small features and bugfixes against previous Tor
10021 versions, and numerous small infrastructure improvements. The most
10022 notable features are a set of improvements to the directory subsystem.
10024 o Major features (security, Linux):
10025 - When Tor starts as root on Linux and is told to switch user ID, it
10026 can now retain the capability to bind to low ports. By default,
10027 Tor will do this only when it's switching user ID and some low
10028 ports have been configured. You can change this behavior with the
10029 new option KeepBindCapabilities. Closes ticket 8195.
10031 o Major features (directory system):
10032 - When bootstrapping multiple consensus downloads at a time, use the
10033 first one that starts downloading, and close the rest. This
10034 reduces failures when authorities or fallback directories are slow
10035 or down. Together with the code for feature 15775, this feature
10036 should reduces failures due to fallback churn. Implements ticket
10037 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
10038 "mikeperry" and "teor".
10039 - Include a trial list of 21 default fallback directories, generated
10040 in January 2016, based on an opt-in survey of suitable relays.
10041 Doing this should make clients bootstrap more quickly and reliably,
10042 and reduce the load on the directory authorities. Closes ticket
10043 15775. Patch by "teor".
10044 Candidates identified using an OnionOO script by "weasel", "teor",
10045 "gsathya", and "karsten".
10046 - Previously only relays that explicitly opened a directory port
10047 (DirPort) accepted directory requests from clients. Now all
10048 relays, with and without a DirPort, accept and serve tunneled
10049 directory requests that they receive through their ORPort. You can
10050 disable this behavior using the new DirCache option. Closes
10053 o Major key updates:
10054 - Update the V3 identity key for the dannenberg directory authority:
10055 it was changed on 18 November 2015. Closes task 17906. Patch
10058 o Minor features (security, clock):
10059 - Warn when the system clock appears to move back in time (when the
10060 state file was last written in the future). Tor doesn't know that
10061 consensuses have expired if the clock is in the past. Patch by
10062 "teor". Implements ticket 17188.
10064 o Minor features (security, exit policies):
10065 - ExitPolicyRejectPrivate now rejects more private addresses by
10066 default. Specifically, it now rejects the relay's outbound bind
10067 addresses (if configured), and the relay's configured port
10068 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
10069 0.2.0.11-alpha. Patch by "teor".
10071 o Minor features (security, memory erasure):
10072 - Set the unused entries in a smartlist to NULL. This helped catch
10073 a (harmless) bug, and shouldn't affect performance too much.
10074 Implements ticket 17026.
10075 - Use SecureMemoryWipe() function to securely clean memory on
10076 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
10077 Implements feature 17986.
10078 - Use explicit_bzero or memset_s when present. Previously, we'd use
10079 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
10080 from <logan@hackers.mu> and <selven@hackers.mu>.
10081 - Make memwipe() do nothing when passed a NULL pointer or buffer of
10082 zero size. Check size argument to memwipe() for underflow. Fixes
10083 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
10086 o Minor features (security, RNG):
10087 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
10088 positively are not allowed to fail. Previously we depended on
10089 internal details of OpenSSL's behavior. Closes ticket 17686.
10090 - Never use the system entropy output directly for anything besides
10091 seeding the PRNG. When we want to generate important keys, instead
10092 of using system entropy directly, we now hash it with the PRNG
10093 stream. This may help resist certain attacks based on broken OS
10094 entropy implementations. Closes part of ticket 17694.
10095 - Use modern system calls (like getentropy() or getrandom()) to
10096 generate strong entropy on platforms that have them. Closes
10099 o Minor features (accounting):
10100 - Added two modes to the AccountingRule option: One for limiting
10101 only the number of bytes sent ("AccountingRule out"), and one for
10102 limiting only the number of bytes received ("AccountingRule in").
10103 Closes ticket 15989; patch from "unixninja92".
10105 o Minor features (build):
10106 - Since our build process now uses "make distcheck", we no longer
10107 force "make dist" to depend on "make check". Closes ticket 17893;
10108 patch from "cypherpunks."
10109 - Tor now builds successfully with the recent OpenSSL 1.1
10110 development branch, and with the latest LibreSSL. Closes tickets
10111 17549, 17921, and 17984.
10113 o Minor features (controller):
10114 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
10115 tickets 16774 and 17817. Patch by George Tankersley.
10116 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
10117 service descriptor from a service's local hidden service
10118 descriptor cache. Closes ticket 14846.
10119 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
10120 controllers can examine the the reject rules added by
10121 ExitPolicyRejectPrivate. This makes it easier for stem to display
10124 o Minor features (crypto):
10125 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
10127 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
10128 - When allocating a digest state object, allocate no more space than
10129 we actually need. Previously, we would allocate as much space as
10130 the state for the largest algorithm would need. This change saves
10131 up to 672 bytes per circuit. Closes ticket 17796.
10132 - Improve performance when hashing non-multiple of 8 sized buffers,
10133 based on Andrew Moon's public domain SipHash-2-4 implementation.
10134 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
10136 o Minor features (directory downloads):
10137 - Wait for busy authorities and fallback directories to become non-
10138 busy when bootstrapping. (A similar change was made in 6c443e987d
10139 for directory caches chosen from the consensus.) Closes ticket
10140 17864; patch by "teor".
10141 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
10142 directory mirrors. The default is 1; set it to 0 to disable
10143 fallbacks. Implements ticket 17576. Patch by "teor".
10145 o Minor features (geoip):
10146 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
10149 o Minor features (IPv6):
10150 - Add an argument 'ipv6=address:orport' to the DirAuthority and
10151 FallbackDir torrc options, to specify an IPv6 address for an
10152 authority or fallback directory. Add hard-coded ipv6 addresses for
10153 directory authorities that have them. Closes ticket 17327; patch
10154 from Nick Mathewson and "teor".
10155 - Add address policy assume_action support for IPv6 addresses.
10156 - Limit IPv6 mask bits to 128.
10157 - Warn when comparing against an AF_UNSPEC address in a policy, it's
10158 almost always a bug. Closes ticket 17863; patch by "teor".
10159 - Allow users to configure directory authorities and fallback
10160 directory servers with IPv6 addresses and ORPorts. Resolves
10162 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
10163 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
10164 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
10165 17638; bugfix on 0.0.2pre8. Patch by "teor".
10167 o Minor features (logging):
10168 - When logging to syslog, allow a tag to be added to the syslog
10169 identity (the string prepended to every log message). The tag can
10170 be configured with SyslogIdentityTag and defaults to none. Setting
10171 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
10174 o Minor features (portability):
10175 - Use timingsafe_memcmp() where available. Closes ticket 17944;
10176 patch from <logan@hackers.mu>.
10178 o Minor features (relay, address discovery):
10179 - Add a family argument to get_interface_addresses_raw() and
10180 subfunctions to make network interface address interogation more
10181 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
10182 types of interfaces from the operating system. Resolves
10184 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
10185 fails to enumerate interface addresses using the platform-specific
10186 API, have it rely on the UDP socket fallback technique to try and
10187 find out what IP addresses (both IPv4 and IPv6) our machine has.
10188 Resolves ticket 17951.
10190 o Minor features (replay cache):
10191 - The replay cache now uses SHA256 instead of SHA1. Implements
10192 feature 8961. Patch by "teor", issue reported by "rransom".
10194 o Minor features (unix file permissions):
10195 - Defer creation of Unix sockets until after setuid. This avoids
10196 needing CAP_CHOWN and CAP_FOWNER when using systemd's
10197 CapabilityBoundingSet, or chown and fowner when using SELinux.
10198 Implements part of ticket 17562. Patch from Jamie Nguyen.
10199 - If any directory created by Tor is marked as group readable, the
10200 filesystem group is allowed to be either the default GID or the
10201 root user. Allowing root to read the DataDirectory prevents the
10202 need for CAP_READ_SEARCH when using systemd's
10203 CapabilityBoundingSet, or dac_read_search when using SELinux.
10204 Implements part of ticket 17562. Patch from Jamie Nguyen.
10205 - Introduce a new DataDirectoryGroupReadable option. If it is set to
10206 1, the DataDirectory will be made readable by the default GID.
10207 Implements part of ticket 17562. Patch from Jamie Nguyen.
10209 o Minor bugfixes (accounting):
10210 - The max bandwidth when using 'AccountRule sum' is now correctly
10211 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
10212 from "unixninja92".
10214 o Minor bugfixes (code correctness):
10215 - When closing an entry connection, generate a warning if we should
10216 have sent an end cell for it but we haven't. Fixes bug 17876;
10217 bugfix on 0.2.3.2-alpha.
10218 - Assert that allocated memory held by the reputation code is freed
10219 according to its internal counters. Fixes bug 17753; bugfix
10221 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
10224 o Minor bugfixes (compilation):
10225 - Mark all object files that include micro-revision.i as depending
10226 on it, so as to make parallel builds more reliable. Fixes bug
10227 17826; bugfix on 0.2.5.1-alpha.
10228 - Don't try to use the pthread_condattr_setclock() function unless
10229 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
10230 17819; bugfix on 0.2.6.3-alpha.
10231 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
10233 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
10234 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
10235 - Fix search for libevent libraries on OpenBSD (and other systems
10236 that install libevent 1 and libevent 2 in parallel). Fixes bug
10237 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
10238 - Isolate environment variables meant for tests from the rest of the
10239 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
10240 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
10242 - Remove config.log only from make distclean, not from make clean.
10243 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
10245 o Minor bugfixes (crypto):
10246 - Check the return value of HMAC() and assert on failure. Fixes bug
10247 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
10249 o Minor bugfixes (fallback directories):
10250 - Mark fallbacks as "too busy" when they return a 503 response,
10251 rather than just marking authorities. Fixes bug 17572; bugfix on
10252 0.2.4.7-alpha. Patch by "teor".
10254 o Minor bugfixes (IPv6):
10255 - Update the limits in max_dl_per_request for IPv6 address length.
10256 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
10258 o Minor bugfixes (linux seccomp2 sandbox):
10259 - Fix a crash when using offline master ed25519 keys with the Linux
10260 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
10262 o Minor bugfixes (logging):
10263 - In log messages that include a function name, use __FUNCTION__
10264 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
10265 with clang __PRETTY_FUNCTION__ has extra information we don't
10266 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
10268 - Remove needless quotes from a log message about unparseable
10269 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
10271 o Minor bugfixes (portability):
10272 - Remove an #endif from configure.ac so that we correctly detect the
10273 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
10276 o Minor bugfixes (relays):
10277 - Check that both the ORPort and DirPort (if present) are reachable
10278 before publishing a relay descriptor. Otherwise, relays publish a
10279 descriptor with DirPort 0 when the DirPort reachability test takes
10280 longer than the ORPort reachability test. Fixes bug 18050; bugfix
10281 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
10283 o Minor bugfixes (relays, hidden services):
10284 - Refuse connection requests to private OR addresses unless
10285 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
10286 then refuse to send any cells to a private address. Fixes bugs
10287 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
10289 o Minor bugfixes (safe logging):
10290 - When logging a malformed hostname received through socks4, scrub
10291 it if SafeLogging says we should. Fixes bug 17419; bugfix
10294 o Minor bugfixes (statistics code):
10295 - Consistently check for overflow in round_*_to_next_multiple_of
10296 functions, and add unit tests with additional and maximal values.
10297 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
10298 - Handle edge cases in the laplace functions: avoid division by
10299 zero, avoid taking the log of zero, and silence clang type
10300 conversion warnings using round and trunc. Add unit tests for edge
10301 cases with maximal values. Fixes part of bug 13192; bugfix
10304 o Minor bugfixes (testing):
10305 - The test for log_heartbeat was incorrectly failing in timezones
10306 with non-integer offsets. Instead of comparing the end of the time
10307 string against a constant, compare it to the output of
10308 format_local_iso_time when given the correct input. Fixes bug
10309 18039; bugfix on 0.2.5.4-alpha.
10310 - Make unit tests pass on IPv6-only systems, and systems without
10311 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
10312 bugfix on 0.2.7.3-rc. Patch by "teor".
10313 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
10315 - Check the full results of SHA256 and SHA512 digests in the unit
10316 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
10318 o Code simplification and refactoring:
10319 - Move logging of redundant policy entries in
10320 policies_parse_exit_policy_internal into its own function. Closes
10321 ticket 17608; patch from "juce".
10322 - Extract the more complicated parts of circuit_mark_for_close()
10323 into a new function that we run periodically before circuits are
10324 freed. This change removes more than half of the functions
10325 currently in the "blob". Closes ticket 17218.
10326 - Clean up a little duplicated code in
10327 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
10329 - Decouple the list of streams waiting to be attached to circuits
10330 from the overall connection list. This change makes it possible to
10331 attach streams quickly while simplifying Tor's callgraph and
10332 avoiding O(N) scans of the entire connection list. Closes
10334 - When a direct directory request fails immediately on launch,
10335 instead of relaunching that request from inside the code that
10336 launches it, instead mark the connection for teardown. This change
10337 simplifies Tor's callback and prevents the directory-request
10338 launching code from invoking itself recursively. Closes
10340 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
10341 use them. Closes ticket 17926.
10344 - Add a description of the correct use of the '--keygen' command-
10345 line option. Closes ticket 17583; based on text by 's7r'.
10346 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
10347 - Explain actual minima for BandwidthRate. Closes ticket 16382.
10348 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
10349 - Mention torspec URL in the manpage and point the reader to it
10350 whenever we mention a document that belongs in torspce. Fixes
10353 o Removed features:
10354 - Remove client-side support for connecting to Tor relays running
10355 versions of Tor before 0.2.3.6-alpha. These relays didn't support
10356 the v3 TLS handshake protocol, and are no longer allowed on the
10357 Tor network. Implements the client side of ticket 11150. Based on
10358 patches by Tom van der Woerdt.
10361 - Add unit tests to check for common RNG failure modes, such as
10362 returning all zeroes, identical values, or incrementing values
10363 (OpenSSL's rand_predictable feature). Patch by "teor".
10364 - Log more information when the backtrace tests fail. Closes ticket
10365 17892. Patch from "cypherpunks."
10366 - Always test both ed25519 backends, so that we can be sure that our
10367 batch-open replacement code works. Part of ticket 16794.
10368 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
10369 portion of ticket 16831.
10370 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
10371 util_format.c, directory.c, and options_validate.c. Closes tickets
10372 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
10374 - Unit tests for directory_handle_command_get. Closes ticket 17004.
10375 Patch from Reinaldo de Souza Jr.
10378 Changes in version 0.2.7.6 - 2015-12-10
10379 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
10380 well as a minor bug in hidden service reliability.
10382 o Major bugfixes (guard selection):
10383 - Actually look at the Guard flag when selecting a new directory
10384 guard. When we implemented the directory guard design, we
10385 accidentally started treating all relays as if they have the Guard
10386 flag during guard selection, leading to weaker anonymity and worse
10387 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
10390 o Minor features (geoip):
10391 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
10394 o Minor bugfixes (compilation):
10395 - When checking for net/pfvar.h, include netinet/in.h if possible.
10396 This fixes transparent proxy detection on OpenBSD. Fixes bug
10397 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
10398 - Fix a compilation warning with Clang 3.6: Do not check the
10399 presence of an address which can never be NULL. Fixes bug 17781.
10401 o Minor bugfixes (correctness):
10402 - When displaying an IPv6 exit policy, include the mask bits
10403 correctly even when the number is greater than 31. Fixes bug
10404 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
10405 - The wrong list was used when looking up expired intro points in a
10406 rend service object, causing what we think could be reachability
10407 issues for hidden services, and triggering a BUG log. Fixes bug
10408 16702; bugfix on 0.2.7.2-alpha.
10409 - Fix undefined behavior in the tor_cert_checksig function. Fixes
10410 bug 17722; bugfix on 0.2.7.2-alpha.
10413 Changes in version 0.2.7.5 - 2015-11-20
10414 The Tor 0.2.7 release series is dedicated to the memory of Tor user
10415 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
10416 tirelessly to advocate human rights regardless of national borders,
10417 and oppose the encroachments of mass surveillance. He opposed national
10418 exceptionalism, he brought clarity to legal and policy debates, he
10419 understood and predicted the impact of mass surveillance on the world,
10420 and he laid the groundwork for resisting it. While serving on the Tor
10421 Project's board of directors, he brought us his uncompromising focus
10422 on technical excellence in the service of humankind. Caspar was an
10423 inimitable force for good and a wonderful friend. He was kind,
10424 humorous, generous, gallant, and believed we should protect one
10425 another without exception. We honor him here for his ideals, his
10426 efforts, and his accomplishments. Please honor his memory with works
10427 that would make him proud.
10429 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
10431 The 0.2.7 series adds a more secure identity key type for relays,
10432 improves cryptography performance, resolves several longstanding
10433 hidden-service performance issues, improves controller support for
10434 hidden services, and includes small bugfixes and performance
10435 improvements throughout the program. This release series also includes
10436 more tests than before, and significant simplifications to which parts
10437 of Tor invoke which others.
10439 (This release contains no code changes since 0.2.7.4-rc.)
10442 Changes in version 0.2.7.4-rc - 2015-10-21
10443 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
10444 fixes some important memory leaks, and a scary-looking (but mostly
10445 harmless in practice) invalid-read bug. It also has a few small
10446 bugfixes, notably fixes for compilation and portability on different
10447 platforms. If no further significant bounds are found, the next
10448 release will the the official stable release.
10450 o Major bugfixes (security, correctness):
10451 - Fix an error that could cause us to read 4 bytes before the
10452 beginning of an openssl string. This bug could be used to cause
10453 Tor to crash on systems with unusual malloc implementations, or
10454 systems with unusual hardening installed. Fixes bug 17404; bugfix
10457 o Major bugfixes (correctness):
10458 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
10459 bug 17401; bugfix on 0.2.7.3-rc.
10461 o Major bugfixes (memory leaks):
10462 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
10463 17398; bugfix on 0.2.6.1-alpha.
10464 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
10465 17402; bugfix on 0.2.7.3-rc.
10466 - Fix a memory leak when reading an expired signing key from disk.
10467 Fixes bug 17403; bugfix on 0.2.7.2-rc.
10469 o Minor features (geoIP):
10470 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
10473 o Minor bugfixes (compilation):
10474 - Repair compilation with the most recent (unreleased, alpha)
10475 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
10476 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
10477 17251; bugfix on 0.2.7.2-alpha.
10478 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
10479 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
10481 o Minor bugfixes (portability):
10482 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
10483 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
10486 o Minor bugfixes (sandbox):
10487 - Add the "hidserv-stats" filename to our sandbox filter for the
10488 HiddenServiceStatistics option to work properly. Fixes bug 17354;
10489 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
10491 o Minor bugfixes (testing):
10492 - Add unit tests for get_interface_address* failure cases. Fixes bug
10493 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
10494 - Fix breakage when running 'make check' with BSD make. Fixes bug
10495 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
10496 - Make the get_ifaddrs_* unit tests more tolerant of different
10497 network configurations. (Don't assume every test box has an IPv4
10498 address, and don't assume every test box has a non-localhost
10499 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
10500 - Skip backtrace tests when backtrace support is not compiled in.
10501 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
10505 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
10506 - Note that HiddenServicePorts can take a unix domain socket. Closes
10510 Changes in version 0.2.7.3-rc - 2015-09-25
10511 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
10512 contains numerous usability fixes for Ed25519 keys, safeguards against
10513 several misconfiguration problems, significant simplifications to
10514 Tor's callgraph, and numerous bugfixes and small features.
10516 This is the most tested release of Tor to date. The unit tests cover
10517 39.40% of the code, and the integration tests (accessible with "make
10518 test-full-online", requiring stem and chutney and a network
10519 connection) raise the coverage to 64.49%.
10521 o Major features (security, hidden services):
10522 - Hidden services, if using the EntryNodes option, are required to
10523 use more than one EntryNode, in order to avoid a guard discovery
10524 attack. (This would only affect people who had configured hidden
10525 services and manually specified the EntryNodes option with a
10526 single entry-node. The impact was that it would be easy to
10527 remotely identify the guard node used by such a hidden service.
10528 See ticket for more information.) Fixes ticket 14917.
10530 o Major features (Ed25519 keys, keypinning):
10531 - The key-pinning option on directory authorities is now advisory-
10532 only by default. In a future version, or when the AuthDirPinKeys
10533 option is set, pins are enforced again. Disabling key-pinning
10534 seemed like a good idea so that we can survive the fallout of any
10535 usability problems associated with Ed25519 keys. Closes
10538 o Major features (Ed25519 performance):
10539 - Improve the speed of Ed25519 operations and Curve25519 keypair
10540 generation when built targeting 32 bit x86 platforms with SSE2
10541 available. Implements ticket 16535.
10542 - Improve the runtime speed of Ed25519 signature verification by
10543 using Ed25519-donna's batch verification support. Implements
10546 o Major features (performance testing):
10547 - The test-network.sh script now supports performance testing.
10548 Requires corresponding chutney performance testing changes. Patch
10549 by "teor". Closes ticket 14175.
10551 o Major features (relay, Ed25519):
10552 - Significant usability improvements for Ed25519 key management. Log
10553 messages are better, and the code can recover from far more
10554 failure conditions. Thanks to "s7r" for reporting and diagnosing
10556 - Add a new OfflineMasterKey option to tell Tor never to try loading
10557 or generating a secret Ed25519 identity key. You can use this in
10558 combination with tor --keygen to manage offline and/or encrypted
10559 Ed25519 keys. Implements ticket 16944.
10560 - Add a --newpass option to allow changing or removing the
10561 passphrase of an encrypted key with tor --keygen. Implements part
10563 - On receiving a HUP signal, check to see whether the Ed25519
10564 signing key has changed, and reload it if so. Closes ticket 16790.
10566 o Major bugfixes (relay, Ed25519):
10567 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
10568 0.2.7.2-alpha. Reported by "s7r".
10569 - Improve handling of expired signing keys with offline master keys.
10570 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
10572 o Minor features (client-side privacy):
10573 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
10574 lifespan when IsolateSOCKSAuth and streams with SOCKS
10575 authentication are attached to the circuit. This allows
10576 applications like TorBrowser to manage circuit lifetime on their
10577 own. Implements feature 15482.
10578 - When logging malformed hostnames from SOCKS5 requests, respect
10579 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
10581 o Minor features (compilation):
10582 - Give a warning as early as possible when trying to build with an
10583 unsupported OpenSSL version. Closes ticket 16901.
10584 - Fail during configure if we're trying to build against an OpenSSL
10585 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
10586 which started requiring ECC.
10588 o Minor features (geoip):
10589 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
10592 o Minor features (hidden services):
10593 - Relays need to have the Fast flag to get the HSDir flag. As this
10594 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
10595 drop. This change should make some attacks against the hidden
10596 service directory system harder. Fixes ticket 15963.
10597 - Turn on hidden service statistics collection by setting the torrc
10598 option HiddenServiceStatistics to "1" by default. (This keeps
10599 track only of the fraction of traffic used by hidden services, and
10600 the total number of hidden services in existence.) Closes
10602 - Client now uses an introduction point failure cache to know when
10603 to fetch or keep a descriptor in their cache. Previously, failures
10604 were recorded implicitly, but not explicitly remembered. Closes
10607 o Minor features (testing, authorities, documentation):
10608 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
10609 explicitly manage consensus flags in testing networks. Patch by
10610 "robgjansen", modified by "teor". Implements part of ticket 14882.
10612 o Minor bugfixes (security, exit policies):
10613 - ExitPolicyRejectPrivate now also rejects the relay's published
10614 IPv6 address (if any), and any publicly routable IPv4 or IPv6
10615 addresses on any local interfaces. ticket 17027. Patch by "teor".
10616 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
10618 o Minor bug fixes (torrc exit policies):
10619 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
10620 produce IPv6 wildcard addresses. Previously they would produce
10621 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
10622 of bug 16069; bugfix on 0.2.4.7-alpha.
10623 - When parsing torrc ExitPolicies, we now warn for a number of cases
10624 where the user's intent is likely to differ from Tor's actual
10625 behavior. These include: using an IPv4 address with an accept6 or
10626 reject6 line; using "private" on an accept6 or reject6 line; and
10627 including any ExitPolicy lines after accept *:* or reject *:*.
10628 Related to ticket 16069.
10629 - When parsing torrc ExitPolicies, we now issue an info-level
10630 message when expanding an "accept/reject *" line to include both
10631 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
10632 - In each instance above, usage advice is provided to avoid the
10633 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
10634 16069; bugfix on 0.2.4.7-alpha.
10636 o Minor bugfixes (authority):
10637 - Don't assign "HSDir" to a router if it isn't Valid and Running.
10638 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
10639 - Downgrade log messages about Ed25519 key issues if they are in old
10640 cached router descriptors. Fixes part of bug 16286; bugfix
10642 - When we find an Ed25519 key issue in a cached descriptor, stop
10643 saying the descriptor was just "uploaded". Fixes another part of
10644 bug 16286; bugfix on 0.2.7.2-alpha.
10646 o Minor bugfixes (control port):
10647 - Repair a warning and a spurious result when getting the maximum
10648 number of file descriptors from the controller. Fixes bug 16697;
10649 bugfix on 0.2.7.2-alpha.
10651 o Minor bugfixes (correctness):
10652 - When calling channel_free_list(), avoid calling smartlist_remove()
10653 while inside a FOREACH loop. This partially reverts commit
10654 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
10655 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
10657 o Minor bugfixes (documentation):
10658 - Advise users on how to configure separate IPv4 and IPv6 exit
10659 policies in the manpage and sample torrcs. Related to ticket 16069.
10660 - Fix the usage message of tor-resolve(1) so that it no longer lists
10661 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
10662 - Fix an error in the manual page and comments for
10663 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
10664 required "ORPort connectivity". While this is true, it is in no
10665 way unique to the HSDir flag. Of all the flags, only HSDirs need a
10666 DirPort configured in order for the authorities to assign that
10667 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
10670 o Minor bugfixes (Ed25519):
10671 - Fix a memory leak when reading router descriptors with expired
10672 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
10674 o Minor bugfixes (linux seccomp2 sandbox):
10675 - Allow bridge authorities to run correctly under the seccomp2
10676 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
10677 - Allow routers with ed25519 keys to run correctly under the
10678 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
10680 o Minor bugfixes (open file limit):
10681 - Fix set_max_file_descriptors() to set by default the max open file
10682 limit to the current limit when setrlimit() fails. Fixes bug
10683 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
10685 o Minor bugfixes (portability):
10686 - Try harder to normalize the exit status of the Tor process to the
10687 standard-provided range. Fixes bug 16975; bugfix on every version
10689 - Check correctly for Windows socket errors in the workqueue
10690 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
10691 - Fix the behavior of crypto_rand_time_range() when told to consider
10692 times before 1970. (These times were possible when running in a
10693 simulated network environment where time()'s output starts at
10694 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
10695 - Restore correct operation of TLS client-cipher detection on
10696 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
10698 o Minor bugfixes (relay):
10699 - Ensure that worker threads actually exit when a fatal error or
10700 shutdown is indicated. This fix doesn't currently affect the
10701 behavior of Tor, because Tor workers never indicates fatal error
10702 or shutdown except in the unit tests. Fixes bug 16868; bugfix
10704 - Unblock threads before releasing the work queue mutex to ensure
10705 predictable scheduling behavior. Fixes bug 16644; bugfix
10708 o Code simplification and refactoring:
10709 - Change the function that's called when we need to retry all
10710 downloads so that it only reschedules the downloads to happen
10711 immediately, rather than launching them all at once itself. This
10712 further simplifies Tor's callgraph.
10713 - Move some format-parsing functions out of crypto.c and
10714 crypto_curve25519.c into crypto_format.c and/or util_format.c.
10715 - Move the client-only parts of init_keys() into a separate
10716 function. Closes ticket 16763.
10717 - Simplify the microdesc_free() implementation so that it no longer
10718 appears (to code analysis tools) to potentially invoke a huge
10719 suite of other microdesc functions.
10720 - Simply the control graph further by deferring the inner body of
10721 directory_all_unreachable() into a callback. Closes ticket 16762.
10722 - Treat the loss of an owning controller as equivalent to a SIGTERM
10723 signal. This removes a tiny amount of duplicated code, and
10724 simplifies our callgraph. Closes ticket 16788.
10725 - When generating an event to send to the controller, we no longer
10726 put the event over the network immediately. Instead, we queue
10727 these events, and use a Libevent callback to deliver them. This
10728 change simplifies Tor's callgraph by reducing the number of
10729 functions from which all other Tor functions are reachable. Closes
10731 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
10732 that try to scan or compile every file on Unix won't decide that
10734 - Remove the unused "nulterminate" argument from buf_pullup().
10737 - Recommend a 40 GB example AccountingMax in torrc.sample rather
10738 than a 4 GB max. Closes ticket 16742.
10739 - Include the TUNING document in our source tarball. It is referred
10740 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
10744 - The internal pure-C tor-fw-helper tool is now removed from the Tor
10745 distribution, in favor of the pure-Go clone available from
10746 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
10747 used by the C tor-fw-helper are not, in our opinion, very
10748 confidence- inspiring in their secure-programming techniques.
10749 Closes ticket 13338.
10750 - Remove the code that would try to aggressively flush controller
10751 connections while writing to them. This code was introduced in
10752 0.1.2.7-alpha, in order to keep output buffers from exceeding
10753 their limits. But there is no longer a maximum output buffer size,
10754 and flushing data in this way caused some undesirable recursions
10755 in our call graph. Closes ticket 16480.
10758 - Make "bridges+hs" the default test network. This tests almost all
10759 tor functionality during make test-network, while allowing tests
10760 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
10761 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
10762 (chutney). Patches by "teor".
10763 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
10764 by-side in the same parent directory. Closes ticket 16903. Patch
10766 - Use environment variables rather than autoconf substitutions to
10767 send variables from the build system to the test scripts. This
10768 change should be easier to maintain, and cause 'make distcheck' to
10769 work better than before. Fixes bug 17148.
10770 - Add a new set of callgraph analysis scripts that use clang to
10771 produce a list of which Tor functions are reachable from which
10772 other Tor functions. We're planning to use these to help simplify
10773 our code structure by identifying illogical dependencies.
10774 - Add new 'test-full' and 'test-full-online' targets to run all
10775 tests, including integration tests with stem and chutney.
10776 - Make the test-workqueue test work on Windows by initializing the
10777 network before we begin.
10778 - New make target (make test-network-all) to run multiple applicable
10779 chutney test cases. Patch from Teor; closes 16953.
10780 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
10781 functions in dns.c. Implements a portion of ticket 16831.
10782 - When building Tor with testing coverage enabled, run Chutney tests
10783 (if any) using the 'tor-cov' coverage binary.
10784 - When running test-network or test-stem, check for the absence of
10785 stem/chutney before doing any build operations.
10788 Changes in version 0.2.7.2-alpha - 2015-07-27
10789 This, the second alpha in the Tor 0.2.7 series, has a number of new
10790 features, including a way to manually pick the number of introduction
10791 points for hidden services, and the much stronger Ed25519 signing key
10792 algorithm for regular Tor relays (including support for encrypted
10793 offline identity keys in the new algorithm).
10795 Support for Ed25519 on relays is currently limited to signing router
10796 descriptors; later alphas in this series will extend Ed25519 key
10797 support to more parts of the Tor protocol.
10799 o Major features (Ed25519 identity keys, Proposal 220):
10800 - All relays now maintain a stronger identity key, using the Ed25519
10801 elliptic curve signature format. This master key is designed so
10802 that it can be kept offline. Relays also generate an online
10803 signing key, and a set of other Ed25519 keys and certificates.
10804 These are all automatically regenerated and rotated as needed.
10805 Implements part of ticket 12498.
10806 - Directory authorities now vote on Ed25519 identity keys along with
10807 RSA1024 keys. Implements part of ticket 12498.
10808 - Directory authorities track which Ed25519 identity keys have been
10809 used with which RSA1024 identity keys, and do not allow them to
10810 vary freely. Implements part of ticket 12498.
10811 - Microdescriptors now include Ed25519 identity keys. Implements
10812 part of ticket 12498.
10813 - Add support for offline encrypted Ed25519 master keys. To use this
10814 feature on your tor relay, run "tor --keygen" to make a new master
10815 key (or to make a new signing key if you already have a master
10816 key). Closes ticket 13642.
10818 o Major features (Hidden services):
10819 - Add the torrc option HiddenServiceNumIntroductionPoints, to
10820 specify a fixed number of introduction points. Its maximum value
10821 is 10 and default is 3. Using this option can increase a hidden
10822 service's reliability under load, at the cost of making it more
10823 visible that the hidden service is facing extra load. Closes
10825 - Remove the adaptive algorithm for choosing the number of
10826 introduction points, which used to change the number of
10827 introduction points (poorly) depending on the number of
10828 connections the HS sees. Closes ticket 4862.
10830 o Major features (onion key cross-certification):
10831 - Relay descriptors now include signatures of their own identity
10832 keys, made using the TAP and ntor onion keys. These signatures
10833 allow relays to prove ownership of their own onion keys. Because
10834 of this change, microdescriptors will no longer need to include
10835 RSA identity keys. Implements proposal 228; closes ticket 12499.
10837 o Major features (performance):
10838 - Improve the runtime speed of Ed25519 operations by using the
10839 public-domain Ed25519-donna by Andrew M. ("floodyberry").
10840 Implements ticket 16467.
10841 - Improve the runtime speed of the ntor handshake by using an
10842 optimized curve25519 basepoint scalarmult implementation from the
10843 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
10844 ideas by Adam Langley. Implements ticket 9663.
10846 o Major bugfixes (client-side privacy, also in 0.2.6.9):
10847 - Properly separate out each SOCKSPort when applying stream
10848 isolation. The error occurred because each port's session group
10849 was being overwritten by a default value when the listener
10850 connection was initialized. Fixes bug 16247; bugfix on
10851 0.2.6.3-alpha. Patch by "jojelino".
10853 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
10854 - Stop refusing to store updated hidden service descriptors on a
10855 client. This reverts commit 9407040c59218 (which indeed fixed bug
10856 14219, but introduced a major hidden service reachability
10857 regression detailed in bug 16381). This is a temporary fix since
10858 we can live with the minor issue in bug 14219 (it just results in
10859 some load on the network) but the regression of 16381 is too much
10860 of a setback. First-round fix for bug 16381; bugfix
10863 o Major bugfixes (hidden services):
10864 - When cannibalizing a circuit for an introduction point, always
10865 extend to the chosen exit node (creating a 4 hop circuit).
10866 Previously Tor would use the current circuit exit node, which
10867 changed the original choice of introduction point, and could cause
10868 the hidden service to skip excluded introduction points or
10869 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
10872 o Major bugfixes (open file limit):
10873 - The open file limit wasn't checked before calling
10874 tor_accept_socket_nonblocking(), which would make Tor exceed the
10875 limit. Now, before opening a new socket, Tor validates the open
10876 file limit just before, and if the max has been reached, return an
10877 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
10879 o Major bugfixes (stability, also in 0.2.6.10):
10880 - Stop crashing with an assertion failure when parsing certain kinds
10881 of malformed or truncated microdescriptors. Fixes bug 16400;
10882 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
10883 by "cypherpunks_backup".
10884 - Stop random client-side assertion failures that could occur when
10885 connecting to a busy hidden service, or connecting to a hidden
10886 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
10889 o Minor features (directory authorities, security, also in 0.2.6.9):
10890 - The HSDir flag given by authorities now requires the Stable flag.
10891 For the current network, this results in going from 2887 to 2806
10892 HSDirs. Also, it makes it harder for an attacker to launch a sybil
10893 attack by raising the effort for a relay to become Stable to
10894 require at the very least 7 days, while maintaining the 96 hours
10895 uptime requirement for HSDir. Implements ticket 8243.
10897 o Minor features (client):
10898 - Relax the validation of hostnames in SOCKS5 requests, allowing the
10899 character '_' to appear, in order to cope with domains observed in
10900 the wild that are serving non-RFC compliant records. Resolves
10902 - Relax the validation done to hostnames in SOCKS5 requests, and
10903 allow a single trailing '.' to cope with clients that pass FQDNs
10904 using that syntax to explicitly indicate that the domain name is
10905 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
10906 - Add GroupWritable and WorldWritable options to unix-socket based
10907 SocksPort and ControlPort options. These options apply to a single
10908 socket, and override {Control,Socks}SocketsGroupWritable. Closes
10911 o Minor features (control protocol):
10912 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
10913 the control protocol. Resolves ticket 15358.
10915 o Minor features (directory authorities):
10916 - Directory authorities no longer vote against the "Fast", "Stable",
10917 and "HSDir" flags just because they were going to vote against
10918 "Running": if the consensus turns out to be that the router was
10919 running, then the authority's vote should count. Patch from Peter
10920 Retzlaff; closes issue 8712.
10922 o Minor features (geoip, also in 0.2.6.10):
10923 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
10924 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
10926 o Minor features (hidden services):
10927 - Add the new options "HiddenServiceMaxStreams" and
10928 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
10929 limit the maximum number of simultaneous streams per circuit, and
10930 optionally tear down the circuit when the limit is exceeded. Part
10933 o Minor features (portability):
10934 - Use C99 variadic macros when the compiler is not GCC. This avoids
10935 failing compilations on MSVC, and fixes a log-file-based race
10936 condition in our old workarounds. Original patch from Gisle Vanem.
10938 o Minor bugfixes (compilation, also in 0.2.6.9):
10939 - Build with --enable-systemd correctly when libsystemd is
10940 installed, but systemd is not. Fixes bug 16164; bugfix on
10941 0.2.6.3-alpha. Patch from Peter Palfrader.
10943 o Minor bugfixes (controller):
10944 - Add the descriptor ID in each HS_DESC control event. It was
10945 missing, but specified in control-spec.txt. Fixes bug 15881;
10946 bugfix on 0.2.5.2-alpha.
10948 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
10949 - Check for failures from crypto_early_init, and refuse to continue.
10950 A previous typo meant that we could keep going with an
10951 uninitialized crypto library, and would have OpenSSL initialize
10952 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
10953 when implementing ticket 4900. Patch by "teor".
10955 o Minor bugfixes (hidden services):
10956 - Fix a crash when reloading configuration while at least one
10957 configured and one ephemeral hidden service exists. Fixes bug
10958 16060; bugfix on 0.2.7.1-alpha.
10959 - Avoid crashing with a double-free bug when we create an ephemeral
10960 hidden service but adding it fails for some reason. Fixes bug
10961 16228; bugfix on 0.2.7.1-alpha.
10963 o Minor bugfixes (Linux seccomp2 sandbox):
10964 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
10965 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
10967 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
10968 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
10969 these when eventfd2() support is missing. Fixes bug 16363; bugfix
10970 on 0.2.6.3-alpha. Patch from "teor".
10972 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
10973 - Fix sandboxing to work when running as a relay, by allowing the
10974 renaming of secret_id_key, and allowing the eventfd2 and futex
10975 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
10977 - Allow systemd connections to work with the Linux seccomp2 sandbox
10978 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
10981 o Minor bugfixes (relay):
10982 - Fix a rarely-encountered memory leak when failing to initialize
10983 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
10984 from "cypherpunks".
10986 o Minor bugfixes (systemd):
10987 - Fix an accidental formatting error that broke the systemd
10988 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
10989 - Tor's systemd unit file no longer contains extraneous spaces.
10990 These spaces would sometimes confuse tools like deb-systemd-
10991 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
10993 o Minor bugfixes (tests):
10994 - Use the configured Python executable when running test-stem-full.
10995 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
10997 o Minor bugfixes (tests, also in 0.2.6.9):
10998 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
10999 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
11001 o Minor bugfixes (threads, comments):
11002 - Always initialize return value in compute_desc_id in rendcommon.c
11003 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
11004 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
11005 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
11006 - Remove undefined directive-in-macro in test_util_writepid clang
11007 3.7 complains that using a preprocessor directive inside a macro
11008 invocation in test_util_writepid in test_util.c is undefined.
11009 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
11011 o Code simplification and refactoring:
11012 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
11013 to ensure they remain consistent and visible everywhere.
11014 - Remove some vestigial workarounds for the MSVC6 compiler. We
11015 haven't supported that in ages.
11016 - The link authentication code has been refactored for better
11017 testability and reliability. It now uses code generated with the
11018 "trunnel" binary encoding generator, to reduce the risk of bugs
11019 due to programmer error. Done as part of ticket 12498.
11022 - Include a specific and (hopefully) accurate documentation of the
11023 torrc file's meta-format in doc/torrc_format.txt. This is mainly
11024 of interest to people writing programs to parse or generate torrc
11025 files. This document is not a commitment to long-term
11026 compatibility; some aspects of the current format are a bit
11027 ridiculous. Closes ticket 2325.
11029 o Removed features:
11030 - Tor no longer supports copies of OpenSSL that are missing support
11031 for Elliptic Curve Cryptography. (We began using ECC when
11032 available in 0.2.4.8-alpha, for more safe and efficient key
11033 negotiation.) In particular, support for at least one of P256 or
11034 P224 is now required, with manual configuration needed if only
11035 P224 is available. Resolves ticket 16140.
11036 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
11037 on an operating system that has not upgraded to OpenSSL 1.0 or
11038 later, and you compile Tor from source, you will need to install a
11039 more recent OpenSSL to link Tor against.) These versions of
11040 OpenSSL are still supported by the OpenSSL, but the numerous
11041 cryptographic improvements in later OpenSSL releases makes them a
11042 clear choice. Resolves ticket 16034.
11043 - Remove the HidServDirectoryV2 option. Now all relays offer to
11044 store hidden service descriptors. Related to 16543.
11045 - Remove the VoteOnHidServDirectoriesV2 option, since all
11046 authorities have long set it to 1. Closes ticket 16543.
11049 - Document use of coverity, clang static analyzer, and clang dynamic
11050 undefined behavior and address sanitizers in doc/HACKING. Include
11051 detailed usage instructions in the blacklist. Patch by "teor".
11052 Closes ticket 15817.
11053 - The link authentication protocol code now has extensive tests.
11054 - The relay descriptor signature testing code now has
11056 - The test_workqueue program now runs faster, and is enabled by
11057 default as a part of "make check".
11058 - Now that OpenSSL has its own scrypt implementation, add an unit
11059 test that checks for interoperability between libscrypt_scrypt()
11060 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
11061 and rely on EVP_PBE_scrypt() whenever possible. Resolves
11065 Changes in version 0.2.6.10 - 2015-07-12
11066 Tor version 0.2.6.10 fixes some significant stability and hidden
11067 service client bugs, bulletproofs the cryptography init process, and
11068 fixes a bug when using the sandbox code with some older versions of
11069 Linux. Everyone running an older version, especially an older version
11070 of 0.2.6, should upgrade.
11072 o Major bugfixes (hidden service clients, stability):
11073 - Stop refusing to store updated hidden service descriptors on a
11074 client. This reverts commit 9407040c59218 (which indeed fixed bug
11075 14219, but introduced a major hidden service reachability
11076 regression detailed in bug 16381). This is a temporary fix since
11077 we can live with the minor issue in bug 14219 (it just results in
11078 some load on the network) but the regression of 16381 is too much
11079 of a setback. First-round fix for bug 16381; bugfix
11082 o Major bugfixes (stability):
11083 - Stop crashing with an assertion failure when parsing certain kinds
11084 of malformed or truncated microdescriptors. Fixes bug 16400;
11085 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
11086 by "cypherpunks_backup".
11087 - Stop random client-side assertion failures that could occur when
11088 connecting to a busy hidden service, or connecting to a hidden
11089 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
11092 o Minor features (geoip):
11093 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
11094 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
11096 o Minor bugfixes (crypto error-handling):
11097 - Check for failures from crypto_early_init, and refuse to continue.
11098 A previous typo meant that we could keep going with an
11099 uninitialized crypto library, and would have OpenSSL initialize
11100 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
11101 when implementing ticket 4900. Patch by "teor".
11103 o Minor bugfixes (Linux seccomp2 sandbox):
11104 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
11105 these when eventfd2() support is missing. Fixes bug 16363; bugfix
11106 on 0.2.6.3-alpha. Patch from "teor".
11109 Changes in version 0.2.6.9 - 2015-06-11
11110 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
11111 requirements for receiving an HSDir flag, and addresses some other small
11112 bugs in the systemd and sandbox code. Clients using circuit isolation
11113 should upgrade; all directory authorities should upgrade.
11115 o Major bugfixes (client-side privacy):
11116 - Properly separate out each SOCKSPort when applying stream
11117 isolation. The error occurred because each port's session group was
11118 being overwritten by a default value when the listener connection
11119 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
11122 o Minor feature (directory authorities, security):
11123 - The HSDir flag given by authorities now requires the Stable flag.
11124 For the current network, this results in going from 2887 to 2806
11125 HSDirs. Also, it makes it harder for an attacker to launch a sybil
11126 attack by raising the effort for a relay to become Stable which
11127 takes at the very least 7 days to do so and by keeping the 96
11128 hours uptime requirement for HSDir. Implements ticket 8243.
11130 o Minor bugfixes (compilation):
11131 - Build with --enable-systemd correctly when libsystemd is
11132 installed, but systemd is not. Fixes bug 16164; bugfix on
11133 0.2.6.3-alpha. Patch from Peter Palfrader.
11135 o Minor bugfixes (Linux seccomp2 sandbox):
11136 - Fix sandboxing to work when running as a relaymby renaming of
11137 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
11138 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
11139 - Allow systemd connections to work with the Linux seccomp2 sandbox
11140 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
11143 o Minor bugfixes (tests):
11144 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
11145 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
11148 Changes in version 0.2.6.8 - 2015-05-21
11149 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
11150 fixes an authority-side bug in assigning the HSDir flag. All directory
11151 authorities should upgrade.
11153 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
11154 - Revert commit that made directory authorities assign the HSDir
11155 flag to relays without a DirPort; this was bad because such relays
11156 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
11159 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
11160 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
11161 a client authorized hidden service. Fixes bug 15823; bugfix
11164 o Minor features (geoip):
11165 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
11166 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
11170 Changes in version 0.2.7.1-alpha - 2015-05-12
11171 Tor 0.2.7.1-alpha is the first alpha release in its series. It
11172 includes numerous small features and bugfixes against previous Tor
11173 versions, and numerous small infrastructure improvements. The most
11174 notable features are several new ways for controllers to interact with
11175 the hidden services subsystem.
11177 o New system requirements:
11178 - Tor no longer includes workarounds to support Libevent versions
11179 before 1.3e. Libevent 2.0 or later is recommended. Closes
11182 o Major features (controller):
11183 - Add the ADD_ONION and DEL_ONION commands that allow the creation
11184 and management of hidden services via the controller. Closes
11186 - New "GETINFO onions/current" and "GETINFO onions/detached"
11187 commands to get information about hidden services created via the
11188 controller. Part of ticket 6411.
11189 - New HSFETCH command to launch a request for a hidden service
11190 descriptor. Closes ticket 14847.
11191 - New HSPOST command to upload a hidden service descriptor. Closes
11192 ticket 3523. Patch by "DonnchaC".
11194 o Major bugfixes (hidden services):
11195 - Revert commit that made directory authorities assign the HSDir
11196 flag to relays without a DirPort; this was bad because such relays
11197 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
11200 o Minor features (clock-jump tolerance):
11201 - Recover better when our clock jumps back many hours, like might
11202 happen for Tails or Whonix users who start with a very wrong
11203 hardware clock, use Tor to discover a more accurate time, and then
11204 fix their clock. Resolves part of ticket 8766.
11206 o Minor features (command-line interface):
11207 - Make --hash-password imply --hush to prevent unnecessary noise.
11208 Closes ticket 15542. Patch from "cypherpunks".
11209 - Print a warning whenever we find a relative file path being used
11210 as torrc option. Resolves issue 14018.
11212 o Minor features (controller):
11213 - Add DirAuthority lines for default directory authorities to the
11214 output of the "GETINFO config/defaults" command if not already
11215 present. Implements ticket 14840.
11216 - Controllers can now use "GETINFO hs/client/desc/id/..." to
11217 retrieve items from the client's hidden service descriptor cache.
11218 Closes ticket 14845.
11219 - Implement a new controller command "GETINFO status/fresh-relay-
11220 descs" to fetch a descriptor/extrainfo pair that was generated on
11221 demand just for the controller's use. Implements ticket 14784.
11223 o Minor features (DoS-resistance):
11224 - Make it harder for attackers to overload hidden services with
11225 introductions, by blocking multiple introduction requests on the
11226 same circuit. Resolves ticket 15515.
11228 o Minor features (geoip):
11229 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
11230 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
11233 o Minor features (HS popularity countermeasure):
11234 - To avoid leaking HS popularity, don't cycle the introduction point
11235 when we've handled a fixed number of INTRODUCE2 cells but instead
11236 cycle it when a random number of introductions is reached, thus
11237 making it more difficult for an attacker to find out the amount of
11238 clients that have used the introduction point for a specific HS.
11239 Closes ticket 15745.
11241 o Minor features (logging):
11242 - Include the Tor version in all LD_BUG log messages, since people
11243 tend to cut and paste those into the bugtracker. Implements
11246 o Minor features (pluggable transports):
11247 - When launching managed pluggable transports on Linux systems,
11248 attempt to have the kernel deliver a SIGTERM on tor exit if the
11249 pluggable transport process is still running. Resolves
11251 - When launching managed pluggable transports, setup a valid open
11252 stdin in the child process that can be used to detect if tor has
11253 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
11254 can be used by implementations to detect this new behavior.
11255 Resolves ticket 15435.
11257 o Minor features (testing):
11258 - Add a test to verify that the compiler does not eliminate our
11259 memwipe() implementation. Closes ticket 15377.
11260 - Add make rule `check-changes` to verify the format of changes
11261 files. Closes ticket 15180.
11262 - Add unit tests for control_event_is_interesting(). Add a compile-
11263 time check that the number of events doesn't exceed the capacity
11264 of control_event_t.event_mask. Closes ticket 15431, checks for
11265 bugs similar to 13085. Patch by "teor".
11266 - Command-line argument tests moved to Stem. Resolves ticket 14806.
11267 - Integrate the ntor, backtrace, and zero-length keys tests into the
11268 automake test suite. Closes ticket 15344.
11269 - Remove assertions during builds to determine Tor's test coverage.
11270 We don't want to trigger these even in assertions, so including
11271 them artificially makes our branch coverage look worse than it is.
11272 This patch provides the new test-stem-full and coverage-html-full
11273 configure options. Implements ticket 15400.
11275 o Minor bugfixes (build):
11276 - Improve out-of-tree builds by making non-standard rules work and
11277 clean up additional files and directories. Fixes bug 15053; bugfix
11280 o Minor bugfixes (command-line interface):
11281 - When "--quiet" is provided along with "--validate-config", do not
11282 write anything to stdout on success. Fixes bug 14994; bugfix
11284 - When complaining about bad arguments to "--dump-config", use
11285 stderr, not stdout.
11287 o Minor bugfixes (configuration, unit tests):
11288 - Only add the default fallback directories when the DirAuthorities,
11289 AlternateDirAuthority, and FallbackDir directory config options
11290 are set to their defaults. The default fallback directory list is
11291 currently empty, this fix will only change tor's behavior when it
11292 has default fallback directories. Includes unit tests for
11293 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
11294 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
11296 o Minor bugfixes (correctness):
11297 - For correctness, avoid modifying a constant string in
11298 handle_control_postdescriptor. Fixes bug 15546; bugfix
11300 - Remove side-effects from tor_assert() calls. This was harmless,
11301 because we never disable assertions, but it is bad style and
11302 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
11305 o Minor bugfixes (hidden service):
11306 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
11307 a client authorized hidden service. Fixes bug 15823; bugfix
11309 - Remove an extraneous newline character from the end of hidden
11310 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
11312 o Minor bugfixes (interface):
11313 - Print usage information for --dump-config when it is used without
11314 an argument. Also, fix the error message to use different wording
11315 and add newline at the end. Fixes bug 15541; bugfix
11318 o Minor bugfixes (logs):
11319 - When building Tor under Clang, do not include an extra set of
11320 parentheses in log messages that include function names. Fixes bug
11321 15269; bugfix on every released version of Tor when compiled with
11322 recent enough Clang.
11324 o Minor bugfixes (network):
11325 - When attempting to use fallback technique for network interface
11326 lookup, disregard loopback and multicast addresses since they are
11327 unsuitable for public communications.
11329 o Minor bugfixes (statistics):
11330 - Disregard the ConnDirectionStatistics torrc options when Tor is
11331 not a relay since in that mode of operation no sensible data is
11332 being collected and because Tor might run into measurement hiccups
11333 when running as a client for some time, then becoming a relay.
11334 Fixes bug 15604; bugfix on 0.2.2.35.
11336 o Minor bugfixes (test networks):
11337 - When self-testing reachability, use ExtendAllowPrivateAddresses to
11338 determine if local/private addresses imply reachability. The
11339 previous fix used TestingTorNetwork, which implies
11340 ExtendAllowPrivateAddresses, but this excluded rare configurations
11341 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
11342 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
11343 issue discovered by CJ Ess.
11345 o Minor bugfixes (testing):
11346 - Check for matching value in server response in ntor_ref.py. Fixes
11347 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
11349 - Set the severity correctly when testing
11350 get_interface_addresses_ifaddrs() and
11351 get_interface_addresses_win32(), so that the tests fail gracefully
11352 instead of triggering an assertion. Fixes bug 15759; bugfix on
11353 0.2.6.3-alpha. Reported by Nicolas Derive.
11355 o Code simplification and refactoring:
11356 - Move the hacky fallback code out of get_interface_address6() into
11357 separate function and get it covered with unit-tests. Resolves
11359 - Refactor hidden service client-side cache lookup to intelligently
11360 report its various failure cases, and disentangle failure cases
11361 involving a lack of introduction points. Closes ticket 14391.
11362 - Use our own Base64 encoder instead of OpenSSL's, to allow more
11363 control over the output. Part of ticket 15652.
11366 - Improve the descriptions of statistics-related torrc options in
11367 the manpage to describe rationale and possible uses cases. Fixes
11369 - Improve the layout and formatting of ./configure --help messages.
11370 Closes ticket 15024. Patch from "cypherpunks".
11371 - Standardize on the term "server descriptor" in the manual page.
11372 Previously, we had used "router descriptor", "server descriptor",
11373 and "relay descriptor" interchangeably. Part of ticket 14987.
11376 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
11377 and always use the internal Base64 decoder. The internal decoder
11378 has been part of tor since 0.2.0.10-alpha, and no one should
11379 be using the OpenSSL one. Part of ticket 15652.
11380 - Remove the 'tor_strclear()' function; use memwipe() instead.
11381 Closes ticket 14922.
11383 o Removed features:
11384 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
11385 fingerprinting we now recommend pluggable transports; for forward-
11386 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
11387 - Remove the undocumented "--digests" command-line option. It
11388 complicated our build process, caused subtle build issues on
11389 multiple platforms, and is now redundant since we started
11390 including git version identifiers. Closes ticket 14742.
11391 - Tor no longer contains checks for ancient directory cache versions
11392 that didn't know about microdescriptors.
11393 - Tor no longer contains workarounds for stat files generated by
11394 super-old versions of Tor that didn't choose guards sensibly.
11397 Changes in version 0.2.4.27 - 2015-04-06
11398 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
11399 could be used by an attacker to crash hidden services, or crash clients
11400 visiting hidden services. Hidden services should upgrade as soon as
11401 possible; clients should upgrade whenever packages become available.
11403 This release also backports a simple improvement to make hidden
11404 services a bit less vulnerable to denial-of-service attacks.
11406 o Major bugfixes (security, hidden service):
11407 - Fix an issue that would allow a malicious client to trigger an
11408 assertion failure and halt a hidden service. Fixes bug 15600;
11409 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
11410 - Fix a bug that could cause a client to crash with an assertion
11411 failure when parsing a malformed hidden service descriptor. Fixes
11412 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
11414 o Minor features (DoS-resistance, hidden service):
11415 - Introduction points no longer allow multiple INTRODUCE1 cells to
11416 arrive on the same circuit. This should make it more expensive for
11417 attackers to overwhelm hidden services with introductions.
11418 Resolves ticket 15515.
11421 Changes in version 0.2.5.12 - 2015-04-06
11422 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
11423 could be used by an attacker to crash hidden services, or crash clients
11424 visiting hidden services. Hidden services should upgrade as soon as
11425 possible; clients should upgrade whenever packages become available.
11427 This release also backports a simple improvement to make hidden
11428 services a bit less vulnerable to denial-of-service attacks.
11430 o Major bugfixes (security, hidden service):
11431 - Fix an issue that would allow a malicious client to trigger an
11432 assertion failure and halt a hidden service. Fixes bug 15600;
11433 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
11434 - Fix a bug that could cause a client to crash with an assertion
11435 failure when parsing a malformed hidden service descriptor. Fixes
11436 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
11438 o Minor features (DoS-resistance, hidden service):
11439 - Introduction points no longer allow multiple INTRODUCE1 cells to
11440 arrive on the same circuit. This should make it more expensive for
11441 attackers to overwhelm hidden services with introductions.
11442 Resolves ticket 15515.
11445 Changes in version 0.2.6.7 - 2015-04-06
11446 Tor 0.2.6.7 fixes two security issues that could be used by an
11447 attacker to crash hidden services, or crash clients visiting hidden
11448 services. Hidden services should upgrade as soon as possible; clients
11449 should upgrade whenever packages become available.
11451 This release also contains two simple improvements to make hidden
11452 services a bit less vulnerable to denial-of-service attacks.
11454 o Major bugfixes (security, hidden service):
11455 - Fix an issue that would allow a malicious client to trigger an
11456 assertion failure and halt a hidden service. Fixes bug 15600;
11457 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
11458 - Fix a bug that could cause a client to crash with an assertion
11459 failure when parsing a malformed hidden service descriptor. Fixes
11460 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
11462 o Minor features (DoS-resistance, hidden service):
11463 - Introduction points no longer allow multiple INTRODUCE1 cells to
11464 arrive on the same circuit. This should make it more expensive for
11465 attackers to overwhelm hidden services with introductions.
11466 Resolves ticket 15515.
11467 - Decrease the amount of reattempts that a hidden service performs
11468 when its rendezvous circuits fail. This reduces the computational
11469 cost for running a hidden service under heavy load. Resolves
11473 Changes in version 0.2.6.6 - 2015-03-24
11474 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
11476 It adds numerous safety, security, correctness, and performance
11477 improvements. Client programs can be configured to use more kinds of
11478 sockets, AutomapHosts works better, the multithreading backend is
11479 improved, cell transmission is refactored, test coverage is much
11480 higher, more denial-of-service attacks are handled, guard selection is
11481 improved to handle long-term guards better, pluggable transports
11482 should work a bit better, and some annoying hidden service performance
11483 bugs should be addressed.
11485 o Minor bugfixes (portability):
11486 - Use the correct datatype in the SipHash-2-4 function to prevent
11487 compilers from assuming any sort of alignment. Fixes bug 15436;
11488 bugfix on 0.2.5.3-alpha.
11490 Changes in version 0.2.6.5-rc - 2015-03-18
11491 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
11492 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
11494 o Major bugfixes (client):
11495 - Avoid crashing when making certain configuration option changes on
11496 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
11499 o Major bugfixes (pluggable transports):
11500 - Initialize the extended OR Port authentication cookie before
11501 launching pluggable transports. This prevents a race condition
11502 that occurred when server-side pluggable transports would cache the
11503 authentication cookie before it has been (re)generated. Fixes bug
11504 15240; bugfix on 0.2.5.1-alpha.
11506 o Major bugfixes (portability):
11507 - Do not crash on startup when running on Solaris. Fixes a bug
11508 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
11511 o Minor features (heartbeat):
11512 - On relays, report how many connections we negotiated using each
11513 version of the Tor link protocols. This information will let us
11514 know if removing support for very old versions of the Tor
11515 protocols is harming the network. Closes ticket 15212.
11517 o Code simplification and refactoring:
11518 - Refactor main loop to extract the 'loop' part. This makes it
11519 easier to run Tor under Shadow. Closes ticket 15176.
11522 Changes in version 0.2.5.11 - 2015-03-17
11523 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
11525 It backports several bugfixes from the 0.2.6 branch, including a
11526 couple of medium-level security fixes for relays and exit nodes.
11527 It also updates the list of directory authorities.
11529 o Directory authority changes:
11530 - Remove turtles as a directory authority.
11531 - Add longclaw as a new (v3) directory authority. This implements
11532 ticket 13296. This keeps the directory authority count at 9.
11533 - The directory authority Faravahar has a new IP address. This
11534 closes ticket 14487.
11536 o Major bugfixes (crash, OSX, security):
11537 - Fix a remote denial-of-service opportunity caused by a bug in
11538 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
11541 o Major bugfixes (relay, stability, possible security):
11542 - Fix a bug that could lead to a relay crashing with an assertion
11543 failure if a buffer of exactly the wrong layout was passed to
11544 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
11545 0.2.0.10-alpha. Patch from 'cypherpunks'.
11546 - Do not assert if the 'data' pointer on a buffer is advanced to the
11547 very end of the buffer; log a BUG message instead. Only assert if
11548 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
11550 o Major bugfixes (exit node stability):
11551 - Fix an assertion failure that could occur under high DNS load.
11552 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
11553 diagnosed and fixed by "cypherpunks".
11555 o Major bugfixes (Linux seccomp2 sandbox):
11556 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
11557 crash during attempts to call wait4. Fixes bug 15088; bugfix on
11558 0.2.5.1-alpha. Patch from "sanic".
11560 o Minor features (controller):
11561 - New "GETINFO bw-event-cache" to get information about recent
11562 bandwidth events. Closes ticket 14128. Useful for controllers to
11563 get recent bandwidth history after the fix for ticket 13988.
11565 o Minor features (geoip):
11566 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
11567 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
11570 o Minor bugfixes (client, automapping):
11571 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
11572 no value follows the option. Fixes bug 14142; bugfix on
11573 0.2.4.7-alpha. Patch by "teor".
11574 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
11575 14195; bugfix on 0.1.0.1-rc.
11577 o Minor bugfixes (compilation):
11578 - Build without warnings with the stock OpenSSL srtp.h header, which
11579 has a duplicate declaration of SSL_get_selected_srtp_profile().
11580 Fixes bug 14220; this is OpenSSL's bug, not ours.
11582 o Minor bugfixes (directory authority):
11583 - Allow directory authorities to fetch more data from one another if
11584 they find themselves missing lots of votes. Previously, they had
11585 been bumping against the 10 MB queued data limit. Fixes bug 14261;
11586 bugfix on 0.1.2.5-alpha.
11587 - Enlarge the buffer to read bwauth generated files to avoid an
11588 issue when parsing the file in dirserv_read_measured_bandwidths().
11589 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
11591 o Minor bugfixes (statistics):
11592 - Increase period over which bandwidth observations are aggregated
11593 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
11595 o Minor bugfixes (preventative security, C safety):
11596 - When reading a hexadecimal, base-32, or base-64 encoded value from
11597 a string, always overwrite the whole output buffer. This prevents
11598 some bugs where we would look at (but fortunately, not reveal)
11599 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
11603 Changes in version 0.2.4.26 - 2015-03-17
11604 Tor 0.2.4.26 includes an updated list of directory authorities. It
11605 also backports a couple of stability and security bugfixes from 0.2.5
11608 o Directory authority changes:
11609 - Remove turtles as a directory authority.
11610 - Add longclaw as a new (v3) directory authority. This implements
11611 ticket 13296. This keeps the directory authority count at 9.
11612 - The directory authority Faravahar has a new IP address. This
11613 closes ticket 14487.
11615 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
11616 - Fix an assertion failure that could occur under high DNS load.
11617 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
11618 diagnosed and fixed by "cypherpunks".
11620 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
11621 - Fix a bug that could lead to a relay crashing with an assertion
11622 failure if a buffer of exactly the wrong layout was passed to
11623 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
11624 0.2.0.10-alpha. Patch from 'cypherpunks'.
11625 - Do not assert if the 'data' pointer on a buffer is advanced to the
11626 very end of the buffer; log a BUG message instead. Only assert if
11627 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
11629 o Minor features (geoip):
11630 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
11631 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
11634 Changes in version 0.2.6.4-rc - 2015-03-09
11635 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
11636 attacker might be able to use in order to crash certain Tor
11637 directories. It also resolves some minor issues left over from, or
11638 introduced in, Tor 0.2.6.3-alpha or earlier.
11640 o Major bugfixes (crash, OSX, security):
11641 - Fix a remote denial-of-service opportunity caused by a bug in
11642 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
11645 o Major bugfixes (relay, stability, possible security):
11646 - Fix a bug that could lead to a relay crashing with an assertion
11647 failure if a buffer of exactly the wrong layout is passed to
11648 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
11649 0.2.0.10-alpha. Patch from "cypherpunks".
11650 - Do not assert if the 'data' pointer on a buffer is advanced to the
11651 very end of the buffer; log a BUG message instead. Only assert if
11652 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
11654 o Major bugfixes (FreeBSD IPFW transparent proxy):
11655 - Fix address detection with FreeBSD transparent proxies, when
11656 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
11659 o Major bugfixes (Linux seccomp2 sandbox):
11660 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
11661 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
11663 - Allow AF_UNIX hidden services to be used with the seccomp2
11664 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
11665 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
11666 crash during attempts to call wait4. Fixes bug 15088; bugfix on
11667 0.2.5.1-alpha. Patch from "sanic".
11669 o Minor features (controller):
11670 - Messages about problems in the bootstrap process now include
11671 information about the server we were trying to connect to when we
11672 noticed the problem. Closes ticket 15006.
11674 o Minor features (geoip):
11675 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
11676 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
11679 o Minor features (logs):
11680 - Quiet some log messages in the heartbeat and at startup. Closes
11683 o Minor bugfixes (certificate handling):
11684 - If an authority operator accidentally makes a signing certificate
11685 with a future publication time, do not discard its real signing
11686 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
11687 - Remove any old authority certificates that have been superseded
11688 for at least two days. Previously, we would keep superseded
11689 certificates until they expired, if they were published close in
11690 time to the certificate that superseded them. Fixes bug 11454;
11691 bugfix on 0.2.1.8-alpha.
11693 o Minor bugfixes (compilation):
11694 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
11696 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
11699 o Minor bugfixes (testing):
11700 - Fix endianness issues in unit test for resolve_my_address() to
11701 have it pass on big endian systems. Fixes bug 14980; bugfix on
11703 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
11704 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
11705 - When running the new 'make test-stem' target, use the configured
11706 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
11707 from "cypherpunks".
11708 - When running the zero-length-keys tests, do not use the default
11709 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
11712 o Directory authority IP change:
11713 - The directory authority Faravahar has a new IP address. This
11714 closes ticket 14487.
11717 - Remove some lingering dead code that once supported mempools.
11718 Mempools were disabled by default in 0.2.5, and removed entirely
11719 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
11723 Changes in version 0.2.6.3-alpha - 2015-02-19
11724 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
11725 the 0.2.6.x series. It introduces support for more kinds of sockets,
11726 makes it harder to accidentally run an exit, improves our
11727 multithreading backend, incorporates several fixes for the
11728 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
11730 If no major regressions or security holes are found in this version,
11731 the next version will be a release candidate.
11733 o Deprecated versions:
11734 - Tor relays older than 0.2.4.18-rc are no longer allowed to
11735 advertise themselves on the network. Closes ticket 13555.
11737 o Major features (security, unix domain sockets):
11738 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
11739 applications can reach Tor without having to create AF_INET or
11740 AF_INET6 sockets, meaning they can completely disable their
11741 ability to make non-Tor network connections. To create a socket of
11742 this type, use "SocksPort unix:/path/to/socket". Implements
11744 - Support mapping hidden service virtual ports to AF_UNIX sockets.
11745 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
11746 Implements ticket 11485.
11748 o Major features (changed defaults):
11749 - Prevent relay operators from unintentionally running exits: When a
11750 relay is configured as an exit node, we now warn the user unless
11751 the "ExitRelay" option is set to 1. We warn even more loudly if
11752 the relay is configured with the default exit policy, since this
11753 can indicate accidental misconfiguration. Setting "ExitRelay 0"
11754 stops Tor from running as an exit relay. Closes ticket 10067.
11756 o Major features (directory system):
11757 - When downloading server- or microdescriptors from a directory
11758 server, we no longer launch multiple simultaneous requests to the
11759 same server. This reduces load on the directory servers,
11760 especially when directory guards are in use. Closes ticket 9969.
11761 - When downloading server- or microdescriptors over a tunneled
11762 connection, do not limit the length of our requests to what the
11763 Squid proxy is willing to handle. Part of ticket 9969.
11764 - Authorities can now vote on the correct digests and latest
11765 versions for different software packages. This allows packages
11766 that include Tor to use the Tor authority system as a way to get
11767 notified of updates and their correct digests. Implements proposal
11768 227. Closes ticket 10395.
11770 o Major features (guards):
11771 - Introduce the Guardfraction feature to improves load balancing on
11772 guard nodes. Specifically, it aims to reduce the traffic gap that
11773 guard nodes experience when they first get the Guard flag. This is
11774 a required step if we want to increase the guard lifetime to 9
11775 months or greater. Closes ticket 9321.
11777 o Major features (performance):
11778 - Make the CPU worker implementation more efficient by avoiding the
11779 kernel and lengthening pipelines. The original implementation used
11780 sockets to transfer data from the main thread to the workers, and
11781 didn't allow any thread to be assigned more than a single piece of
11782 work at once. The new implementation avoids communications
11783 overhead by making requests in shared memory, avoiding kernel IO
11784 where possible, and keeping more requests in flight at once.
11785 Implements ticket 9682.
11787 o Major features (relay):
11788 - Raise the minimum acceptable configured bandwidth rate for bridges
11789 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
11790 20 KiB/sec.) Closes ticket 13822.
11792 o Major bugfixes (exit node stability):
11793 - Fix an assertion failure that could occur under high DNS load.
11794 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
11795 diagnosed and fixed by "cypherpunks".
11797 o Major bugfixes (mixed relay-client operation):
11798 - When running as a relay and client at the same time (not
11799 recommended), if we decide not to use a new guard because we want
11800 to retry older guards, only close the locally-originating circuits
11801 passing through that guard. Previously we would close all the
11802 circuits through that guard. Fixes bug 9819; bugfix on
11803 0.2.1.1-alpha. Reported by "skruffy".
11805 o Minor features (build):
11806 - New --disable-system-torrc compile-time option to prevent Tor from
11807 looking for the system-wide torrc or torrc-defaults files.
11808 Resolves ticket 13037.
11810 o Minor features (controller):
11811 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
11812 events so controllers can observe circuit isolation inputs. Closes
11814 - ControlPort now supports the unix:/path/to/socket syntax as an
11815 alternative to the ControlSocket option, for consistency with
11816 SocksPort and HiddenServicePort. Closes ticket 14451.
11817 - New "GETINFO bw-event-cache" to get information about recent
11818 bandwidth events. Closes ticket 14128. Useful for controllers to
11819 get recent bandwidth history after the fix for ticket 13988.
11821 o Minor features (Denial of service resistance):
11822 - Count the total number of bytes used storing hidden service
11823 descriptors against the value of MaxMemInQueues. If we're low on
11824 memory, and more than 20% of our memory is used holding hidden
11825 service descriptors, free them until no more than 10% of our
11826 memory holds hidden service descriptors. Free the least recently
11827 fetched descriptors first. Resolves ticket 13806.
11828 - When we have recently been under memory pressure (over 3/4 of
11829 MaxMemInQueues is allocated), then allocate smaller zlib objects
11830 for small requests. Closes ticket 11791.
11832 o Minor features (geoip):
11833 - Update geoip and geoip6 files to the January 7 2015 Maxmind
11834 GeoLite2 Country database.
11836 o Minor features (guard nodes):
11837 - Reduce the time delay before saving guard status to disk from 10
11838 minutes to 30 seconds (or from one hour to 10 minutes if
11839 AvoidDiskWrites is set). Closes ticket 12485.
11841 o Minor features (hidden service):
11842 - Make Sybil attacks against hidden services harder by changing the
11843 minimum time required to get the HSDir flag from 25 hours up to 96
11844 hours. Addresses ticket 14149.
11845 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
11846 services to disable the anti-scanning feature introduced in
11847 0.2.6.2-alpha. With this option not set, a connection to an
11848 unlisted port closes the circuit. With this option set, only a
11849 RELAY_DONE cell is sent. Closes ticket 14084.
11851 o Minor features (interface):
11852 - Implement "-f -" command-line option to read torrc configuration
11853 from standard input, if you don't want to store the torrc file in
11854 the file system. Implements feature 13865.
11856 o Minor features (logging):
11857 - Add a count of unique clients to the bridge heartbeat message.
11858 Resolves ticket 6852.
11859 - Suppress "router info incompatible with extra info" message when
11860 reading extrainfo documents from cache. (This message got loud
11861 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
11863 - Elevate hidden service authorized-client message from DEBUG to
11864 INFO. Closes ticket 14015.
11866 o Minor features (stability):
11867 - Add assertions in our hash-table iteration code to check for
11868 corrupted values that could cause infinite loops. Closes
11871 o Minor features (systemd):
11872 - Various improvements and modernizations in systemd hardening
11873 support. Closes ticket 13805. Patch from Craig Andrews.
11875 o Minor features (testing networks):
11876 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
11877 and the default on a testing network to 2 minutes. Drop the
11878 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
11879 keep the default on a testing network at 30 seconds. This reduces
11880 HS bootstrap time to around 25 seconds. Also, change the default
11881 time in test-network.sh to match. Closes ticket 13401. Patch
11883 - Create TestingDirAuthVoteHSDir to correspond to
11884 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
11885 HSDir flag for the listed relays regardless of uptime or ORPort
11886 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
11887 Partial implementation for ticket 14067. Patch by "teor".
11889 o Minor features (tor2web mode):
11890 - Introduce the config option Tor2webRendezvousPoints, which allows
11891 clients in Tor2webMode to select a specific Rendezvous Point to be
11892 used in HS circuits. This might allow better performance for
11893 Tor2Web nodes. Implements ticket 12844.
11895 o Minor bugfixes (client DNS):
11896 - Report the correct cached DNS expiration times on SOCKS port or in
11897 DNS replies. Previously, we would report everything as "never
11898 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
11899 - Avoid a small memory leak when we find a cached answer for a
11900 reverse DNS lookup in a client-side DNS cache. (Remember, client-
11901 side DNS caching is off by default, and is not recommended.) Fixes
11902 bug 14259; bugfix on 0.2.0.1-alpha.
11904 o Minor bugfixes (client, automapping):
11905 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
11906 no value follows the option. Fixes bug 14142; bugfix on
11907 0.2.4.7-alpha. Patch by "teor".
11908 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
11909 14195; bugfix on 0.1.0.1-rc.
11910 - Prevent changes to other options from removing the wildcard value
11911 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
11913 - Allow MapAddress and AutomapHostsOnResolve to work together when
11914 an address is mapped into another address type (like .onion) that
11915 must be automapped at resolve time. Fixes bug 7555; bugfix
11918 o Minor bugfixes (client, bridges):
11919 - When we are using bridges and we had a network connectivity
11920 problem, only retry connecting to our currently configured
11921 bridges, not all bridges we know about and remember using. Fixes
11922 bug 14216; bugfix on 0.2.2.17-alpha.
11924 o Minor bugfixes (client, IPv6):
11925 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
11926 flag is not set; and not because the NoIPv4Traffic flag was set.
11927 Previously we'd looked at the NoIPv4Traffic flag for both types of
11928 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
11930 o Minor bugfixes (compilation):
11931 - The address of an array in the middle of a structure will always
11932 be non-NULL. clang recognises this and complains. Disable the
11933 tautologous and redundant check to silence this warning. Fixes bug
11934 14001; bugfix on 0.2.1.2-alpha.
11935 - Avoid warnings when building with systemd 209 or later. Fixes bug
11936 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
11937 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
11938 Addresses ticket 14188.
11939 - Build without warnings with the stock OpenSSL srtp.h header, which
11940 has a duplicate declaration of SSL_get_selected_srtp_profile().
11941 Fixes bug 14220; this is OpenSSL's bug, not ours.
11942 - Do not compile any code related to Tor2Web mode when Tor2Web mode
11943 is not enabled at compile time. Previously, this code was included
11944 in a disabled state. See discussion on ticket 12844.
11945 - Remove the --disable-threads configure option again. It was
11946 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
11947 14819; bugfix on 0.2.6.2-alpha.
11949 o Minor bugfixes (controller):
11950 - Report "down" in response to the "GETINFO entry-guards" command
11951 when relays are down with an unreachable_since value. Previously,
11952 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
11953 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
11954 14116; bugfix on 0.2.2.9-alpha.
11955 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
11956 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
11958 o Minor bugfixes (directory authority):
11959 - Allow directory authorities to fetch more data from one another if
11960 they find themselves missing lots of votes. Previously, they had
11961 been bumping against the 10 MB queued data limit. Fixes bug 14261;
11962 bugfix on 0.1.2.5-alpha.
11963 - Do not attempt to download extrainfo documents which we will be
11964 unable to validate with a matching server descriptor. Fixes bug
11965 13762; bugfix on 0.2.0.1-alpha.
11966 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
11967 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
11968 - Enlarge the buffer to read bwauth generated files to avoid an
11969 issue when parsing the file in dirserv_read_measured_bandwidths().
11970 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
11972 o Minor bugfixes (file handling):
11973 - Stop failing when key files are zero-length. Instead, generate new
11974 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
11975 on all versions of Tor. Patch by "teor".
11976 - Stop generating a fresh .old RSA onion key file when the .old file
11977 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
11978 - Avoid overwriting .old key files with empty key files.
11979 - Skip loading zero-length extrainfo store, router store, stats,
11980 state, and key files.
11981 - Avoid crashing when trying to reload a torrc specified as a
11982 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
11985 o Minor bugfixes (hidden services):
11986 - Close the introduction circuit when we have no more usable intro
11987 points, instead of waiting for it to time out. This also ensures
11988 that no follow-up HS descriptor fetch is triggered when the
11989 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
11990 - When fetching a hidden service descriptor for a down service that
11991 was recently up, do not keep refetching until we try the same
11992 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
11993 - Successfully launch Tor with a nonexistent hidden service
11994 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
11995 14106; bugfix on 0.2.6.2-alpha.
11997 o Minor bugfixes (logging):
11998 - Avoid crashing when there are more log domains than entries in
11999 domain_list. Bugfix on 0.2.3.1-alpha.
12000 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
12002 - Don't log messages to stdout twice when starting up. Fixes bug
12003 13993; bugfix on 0.2.6.1-alpha.
12005 o Minor bugfixes (parsing):
12006 - Stop accepting milliseconds (or other junk) at the end of
12007 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
12008 - Support two-number and three-number version numbers correctly, in
12009 case we change the Tor versioning system in the future. Fixes bug
12010 13661; bugfix on 0.0.8pre1.
12012 o Minor bugfixes (path counting):
12013 - When deciding whether the consensus lists any exit nodes, count
12014 the number listed in the consensus, not the number we have
12015 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
12016 - When deciding whether we have any exit nodes, only examine
12017 ExitNodes when the ExitNodes option is actually set. Fixes part of
12018 bug 14918; bugfix on 0.2.6.2-alpha.
12019 - Get rid of redundant and possibly scary warnings that we are
12020 missing directory information while we bootstrap. Fixes part of
12021 bug 14918; bugfix on 0.2.6.2-alpha.
12023 o Minor bugfixes (portability):
12024 - Fix the ioctl()-based network interface lookup code so that it
12025 will work on systems that have variable-length struct ifreq, for
12027 - Fix scheduler compilation on targets where char is unsigned. Fixes
12028 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
12030 o Minor bugfixes (sandbox):
12031 - Allow glibc fatal errors to be sent to stderr before Tor exits.
12032 Previously, glibc would try to write them to /dev/tty, and the
12033 sandbox would trap the call and make Tor exit prematurely. Fixes
12034 bug 14759; bugfix on 0.2.5.1-alpha.
12036 o Minor bugfixes (shutdown):
12037 - When shutting down, always call event_del() on lingering read or
12038 write events before freeing them. Otherwise, we risk double-frees
12039 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
12042 o Minor bugfixes (small memory leaks):
12043 - Avoid leaking memory when using IPv6 virtual address mappings.
12044 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
12047 o Minor bugfixes (statistics):
12048 - Increase period over which bandwidth observations are aggregated
12049 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
12051 o Minor bugfixes (systemd support):
12052 - Fix detection and operation of systemd watchdog. Fixes part of bug
12053 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
12054 - Run correctly under systemd with the RunAsDaemon option set. Fixes
12055 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
12056 - Inform the systemd supervisor about more changes in the Tor
12057 process status. Implements part of ticket 14141. Patch from
12059 - Cause the "--disable-systemd" option to actually disable systemd
12060 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
12063 o Minor bugfixes (TLS):
12064 - Check more thoroughly throughout the TLS code for possible
12065 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
12067 o Minor bugfixes (transparent proxy):
12068 - Use getsockname, not getsockopt, to retrieve the address for a
12069 TPROXY-redirected connection. Fixes bug 13796; bugfix
12072 o Code simplification and refactoring:
12073 - Move fields related to isolating and configuring client ports into
12074 a shared structure. Previously, they were duplicated across
12075 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
12076 to copy them correctly had been the cause of at least one bug in
12077 the past. Closes ticket 8546.
12078 - Refactor the get_interface_addresses_raw() doom-function into
12079 multiple smaller and simpler subfunctions. Cover the resulting
12080 subfunctions with unit-tests. Fixes a significant portion of
12082 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
12083 only for version <= 0.2.2.24 which is now deprecated. Closes
12085 - Remove a test for a long-defunct broken version-one
12089 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
12090 for writing the OpenBSD-specific tips. Resolves ticket 13702.
12091 - Make the tor-resolve documentation match its help string and its
12092 options. Resolves part of ticket 14325.
12093 - Log a more useful error message from tor-resolve when failing to
12094 look up a hidden service address. Resolves part of ticket 14325.
12096 o Downgraded warnings:
12097 - Don't warn when we've attempted to contact a relay using the wrong
12098 ntor onion key. Closes ticket 9635.
12100 o Removed features:
12101 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
12102 longer silently accepted as an alias for "ExitNodes".
12103 - The --enable-mempool and --enable-buf-freelists options, which
12104 were originally created to work around bad malloc implementations,
12105 no longer exist. They were off-by-default in 0.2.5. Closes
12109 - Make the checkdir/perms test complete successfully even if the
12110 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
12111 - Test that tor does not fail when key files are zero-length. Check
12112 that tor generates new keys, and overwrites the empty key files.
12113 - Test that tor generates new keys when keys are missing
12114 (existing behavior).
12115 - Test that tor does not overwrite key files that already contain
12116 data (existing behavior). Tests bug 13111. Patch by "teor".
12117 - New "make test-stem" target to run stem integration tests.
12118 Requires that the "STEM_SOURCE_DIR" environment variable be set.
12119 Closes ticket 14107.
12120 - Make the test_cmdline_args.py script work correctly on Windows.
12121 Patch from Gisle Vanem.
12122 - Move the slower unit tests into a new "./src/test/test-slow"
12123 binary that can be run independently of the other tests. Closes
12125 - Avoid undefined behavior when sampling huge values from the
12126 Laplace distribution. This made unittests fail on Raspberry Pi.
12127 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
12130 Changes in version 0.2.6.2-alpha - 2014-12-31
12131 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
12132 It introduces a major new backend for deciding when to send cells on
12133 channels, which should lead down the road to big performance
12134 increases. It contains security and statistics features for better
12135 work on hidden services, and numerous bugfixes.
12137 This release contains many new unit tests, along with major
12138 performance improvements for running testing networks using Chutney.
12139 Thanks to a series of patches contributed by "teor", testing networks
12140 should now bootstrap in seconds, rather than minutes.
12142 o Major features (relay, infrastructure):
12143 - Complete revision of the code that relays use to decide which cell
12144 to send next. Formerly, we selected the best circuit to write on
12145 each channel, but we didn't select among channels in any
12146 sophisticated way. Now, we choose the best circuits globally from
12147 among those whose channels are ready to deliver traffic.
12149 This patch implements a new inter-cmux comparison API, a global
12150 high/low watermark mechanism and a global scheduler loop for
12151 transmission prioritization across all channels as well as among
12152 circuits on one channel. This schedule is currently tuned to
12153 (tolerantly) avoid making changes in network performance, but it
12154 should form the basis for major circuit performance increases in
12155 the future. Code by Andrea; tuning by Rob Jansen; implements
12158 o Major features (hidden services):
12159 - Make HS port scanning more difficult by immediately closing the
12160 circuit when a user attempts to connect to a nonexistent port.
12161 Closes ticket 13667.
12162 - Add a HiddenServiceStatistics option that allows Tor relays to
12163 gather and publish statistics about the overall size and volume of
12164 hidden service usage. Specifically, when this option is turned on,
12165 an HSDir will publish an approximate number of hidden services
12166 that have published descriptors to it the past 24 hours. Also, if
12167 a relay has acted as a hidden service rendezvous point, it will
12168 publish the approximate amount of rendezvous cells it has relayed
12169 the past 24 hours. The statistics themselves are obfuscated so
12170 that the exact values cannot be derived. For more details see
12171 proposal 238, "Better hidden service stats from Tor relays". This
12172 feature is currently disabled by default. Implements feature 13192.
12174 o Major bugfixes (client, automap):
12175 - Repair automapping with IPv6 addresses. This automapping should
12176 have worked previously, but one piece of debugging code that we
12177 inserted to detect a regression actually caused the regression to
12178 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
12179 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
12182 o Major bugfixes (hidden services):
12183 - When closing an introduction circuit that was opened in parallel
12184 with others, don't mark the introduction point as unreachable.
12185 Previously, the first successful connection to an introduction
12186 point would make the other introduction points get marked as
12187 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
12189 o Directory authority changes:
12190 - Remove turtles as a directory authority.
12191 - Add longclaw as a new (v3) directory authority. This implements
12192 ticket 13296. This keeps the directory authority count at 9.
12194 o Major removed features:
12195 - Tor clients no longer support connecting to hidden services
12196 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
12197 option has been removed. (There shouldn't be any hidden services
12198 running these versions on the network.) Closes ticket 7803.
12200 o Minor features (client):
12201 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
12202 is enabled, reject requests with IP addresses as hostnames.
12203 Resolves ticket 13315.
12205 o Minor features (controller):
12206 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
12207 write an unscheduled heartbeat message to the log. Implements
12210 o Minor features (geoip):
12211 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
12214 o Minor features (hidden services):
12215 - When re-enabling the network, don't try to build introduction
12216 circuits until we have successfully built a circuit. This makes
12217 hidden services come up faster when the network is re-enabled.
12218 Patch from "akwizgran". Closes ticket 13447.
12219 - When we fail to retrieve a hidden service descriptor, send the
12220 controller an "HS_DESC FAILED" controller event. Implements
12222 - New HiddenServiceDirGroupReadable option to cause hidden service
12223 directories and hostname files to be created group-readable. Patch
12224 from "anon", David Stainton, and "meejah". Closes ticket 11291.
12226 o Minor features (systemd):
12227 - Where supported, when running with systemd, report successful
12228 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
12229 - When running with systemd, support systemd watchdog messages. Part
12230 of ticket 11016. Patch by Michael Scherer.
12232 o Minor features (transparent proxy):
12233 - Update the transparent proxy option checks to allow for both ipfw
12234 and pf on OS X. Closes ticket 14002.
12235 - Use the correct option when using IPv6 with transparent proxy
12236 support on Linux. Resolves 13808. Patch by Francisco Blas
12239 o Minor bugfixes (preventative security, C safety):
12240 - When reading a hexadecimal, base-32, or base-64 encoded value from
12241 a string, always overwrite the whole output buffer. This prevents
12242 some bugs where we would look at (but fortunately, not reveal)
12243 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
12245 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
12246 just the part that's used. This makes it harder for data leak bugs
12247 to occur in the event of other programming failures. Resolves
12250 o Minor bugfixes (client, microdescriptors):
12251 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
12252 computing which microdescriptors to download. This keeps us from
12253 erroneous download behavior if two microdescriptor digests ever
12254 have the same first 160 bits. Fixes part of bug 13399; bugfix
12256 - Reset a router's status if its microdescriptor digest changes,
12257 even if the first 160 bits remain the same. Fixes part of bug
12258 13399; bugfix on 0.2.3.1-alpha.
12260 o Minor bugfixes (compilation):
12261 - Silence clang warnings under --enable-expensive-hardening,
12262 including implicit truncation of 64 bit values to 32 bit, const
12263 char assignment to self, tautological compare, and additional
12264 parentheses around equality tests. Fixes bug 13577; bugfix
12266 - Fix a clang warning about checking whether an address in the
12267 middle of a structure is NULL. Fixes bug 14001; bugfix
12270 o Minor bugfixes (hidden services):
12271 - Correctly send a controller event when we find that a rendezvous
12272 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
12273 - Pre-check directory permissions for new hidden-services to avoid
12274 at least one case of "Bug: Acting on config options left us in a
12275 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
12276 - When adding a new hidden service (for example, via SETCONF), Tor
12277 no longer congratulates the user for running a relay. Fixes bug
12278 13941; bugfix on 0.2.6.1-alpha.
12279 - When fetching hidden service descriptors, we now check not only
12280 for whether we got the hidden service we had in mind, but also
12281 whether we got the particular descriptors we wanted. This prevents
12282 a class of inefficient but annoying DoS attacks by hidden service
12283 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
12286 o Minor bugfixes (Linux seccomp2 sandbox):
12287 - Make transparent proxy support work along with the seccomp2
12288 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
12289 by Francisco Blas Izquierdo Riera.
12290 - Fix a memory leak in tor-resolve when running with the sandbox
12291 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
12293 o Minor bugfixes (logging):
12294 - Downgrade warnings about RSA signature failures to info log level.
12295 Emit a warning when an extra info document is found incompatible
12296 with a corresponding router descriptor. Fixes bug 9812; bugfix
12298 - Make connection_ap_handshake_attach_circuit() log the circuit ID
12299 correctly. Fixes bug 13701; bugfix on 0.0.6.
12301 o Minor bugfixes (misc):
12302 - Stop allowing invalid address patterns like "*/24" that contain
12303 both a wildcard address and a bit prefix length. This affects all
12304 our address-range parsing code. Fixes bug 7484; bugfix
12307 o Minor bugfixes (testing networks, fast startup):
12308 - Allow Tor to build circuits using a consensus with no exits. If
12309 the consensus has no exits (typical of a bootstrapping test
12310 network), allow Tor to build circuits once enough descriptors have
12311 been downloaded. This assists in bootstrapping a testing Tor
12312 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
12314 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
12315 header to directory servers. This allows us to obtain consensuses
12316 promptly when the consensus interval is very short. This assists
12317 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
12318 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
12319 - Stop assuming that private addresses are local when checking
12320 reachability in a TestingTorNetwork. Instead, when testing, assume
12321 all OR connections are remote. (This is necessary due to many test
12322 scenarios running all relays on localhost.) This assists in
12323 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
12324 0.1.0.1-rc. Patch by "teor".
12325 - Avoid building exit circuits from a consensus with no exits. Now
12326 thanks to our fix for 13718, we accept a no-exit network as not
12327 wholly lost, but we need to remember not to try to build exit
12328 circuits on it. Closes ticket 13814; patch by "teor".
12329 - Stop requiring exits to have non-zero bandwithcapacity in a
12330 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
12331 ignore exit bandwidthcapacity. This assists in bootstrapping a
12332 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
12333 on 0.2.0.3-alpha. Patch by "teor".
12334 - Add "internal" to some bootstrap statuses when no exits are
12335 available. If the consensus does not contain Exits, Tor will only
12336 build internal circuits. In this case, relevant statuses will
12337 contain the word "internal" as indicated in the Tor control-
12338 spec.txt. When bootstrap completes, Tor will be ready to build
12339 internal circuits. If a future consensus contains Exits, exit
12340 circuits may become available. Fixes part of bug 13718; bugfix on
12341 0.2.4.10-alpha. Patch by "teor".
12342 - Decrease minimum consensus interval to 10 seconds when
12343 TestingTorNetwork is set, or 5 seconds for the first consensus.
12344 Fix assumptions throughout the code that assume larger intervals.
12345 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
12347 - Avoid excluding guards from path building in minimal test
12348 networks, when we're in a test network and excluding guards would
12349 exclude all relays. This typically occurs in incredibly small tor
12350 networks, and those using "TestingAuthVoteGuard *". Fixes part of
12351 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
12353 o Code simplification and refactoring:
12354 - Stop using can_complete_circuits as a global variable; access it
12355 with a function instead.
12356 - Avoid using operators directly as macro arguments: this lets us
12357 apply coccinelle transformations to our codebase more directly.
12358 Closes ticket 13172.
12359 - Combine the functions used to parse ClientTransportPlugin and
12360 ServerTransportPlugin into a single function. Closes ticket 6456.
12361 - Add inline functions and convenience macros for inspecting channel
12362 state. Refactor the code to use convenience macros instead of
12363 checking channel state directly. Fixes issue 7356.
12364 - Document all members of was_router_added_t and rename
12365 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
12366 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
12367 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
12368 constant instead of hardcoded value. Fixes issue 13840.
12369 - Refactor our generic strmap and digestmap types into a single
12370 implementation, so that we can add a new digest256map
12374 - Document the bridge-authority-only 'networkstatus-bridges' file.
12375 Closes ticket 13713; patch from "tom".
12376 - Fix typo in PredictedPortsRelevanceTime option description in
12377 manpage. Resolves issue 13707.
12378 - Stop suggesting that users specify relays by nickname: it isn't a
12379 good idea. Also, properly cross-reference how to specify relays in
12380 all parts of manual documenting options that take a list of
12381 relays. Closes ticket 13381.
12382 - Clarify the HiddenServiceDir option description in manpage to make
12383 it clear that relative paths are taken with respect to the current
12384 working directory. Also clarify that this behavior is not
12385 guaranteed to remain indefinitely. Fixes issue 13913.
12388 - New tests for many parts of channel, relay, and circuitmux
12389 functionality. Code by Andrea; part of 9262.
12390 - New tests for parse_transport_line(). Part of ticket 6456.
12391 - In the unit tests, use chgrp() to change the group of the unit
12392 test temporary directory to the current user, so that the sticky
12393 bit doesn't interfere with tests that check directory groups.
12395 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
12399 Changes in version 0.2.6.1-alpha - 2014-10-30
12400 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
12401 includes numerous code cleanups and new tests, and fixes a large
12402 number of annoying bugs. Out-of-memory conditions are handled better
12403 than in 0.2.5, pluggable transports have improved proxy support, and
12404 clients now use optimistic data for contacting hidden services. Also,
12405 we are now more robust to changes in what we consider a parseable
12406 directory object, so that tightening restrictions does not have a risk
12407 of introducing infinite download loops.
12409 This is the first alpha release in a new series, so expect there to be
12410 bugs. Users who would rather test out a more stable branch should stay
12411 with 0.2.5.x for now.
12413 o New compiler and system requirements:
12414 - Tor 0.2.6.x requires that your compiler support more of the C99
12415 language standard than before. The 'configure' script now detects
12416 whether your compiler supports C99 mid-block declarations and
12417 designated initializers. If it does not, Tor will not compile.
12419 We may revisit this requirement if it turns out that a significant
12420 number of people need to build Tor with compilers that don't
12421 bother implementing a 15-year-old standard. Closes ticket 13233.
12422 - Tor no longer supports systems without threading support. When we
12423 began working on Tor, there were several systems that didn't have
12424 threads, or where the thread support wasn't able to run the
12425 threads of a single process on multiple CPUs. That no longer
12426 holds: every system where Tor needs to run well now has threading
12427 support. Resolves ticket 12439.
12429 o Removed platform support:
12430 - We no longer include special code to build on Windows CE; as far
12431 as we know, nobody has used Tor on Windows CE in a very long time.
12432 Closes ticket 11446.
12434 o Major features (bridges):
12435 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
12436 transports if they are configured via the "TOR_PT_PROXY"
12437 environment variable. Implements proposal 232. Resolves
12440 o Major features (client performance, hidden services):
12441 - Allow clients to use optimistic data when connecting to a hidden
12442 service, which should remove a round-trip from hidden service
12443 initialization. See proposal 181 for details. Implements
12446 o Major features (directory system):
12447 - Upon receiving an unparseable directory object, if its digest
12448 matches what we expected, then don't try to download it again.
12449 Previously, when we got a descriptor we didn't like, we would keep
12450 trying to download it over and over. Closes ticket 11243.
12452 o Major features (sample torrc):
12453 - Add a new, infrequently-changed "torrc.minimal". This file is
12454 similar to torrc.sample, but it will change as infrequently as
12455 possible, for the benefit of users whose systems prompt them for
12456 intervention whenever a default configuration file is changed.
12457 Making this change allows us to update torrc.sample to be a more
12458 generally useful "sample torrc".
12460 o Major bugfixes (directory authorities):
12461 - Do not assign the HSDir flag to relays if they are not Valid, or
12462 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
12464 o Major bugfixes (directory bandwidth performance):
12465 - Don't flush the zlib buffer aggressively when compressing
12466 directory information for clients. This should save about 7% of
12467 the bandwidth currently used for compressed descriptors and
12468 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
12470 o Minor features (security, memory wiping):
12471 - Ensure we securely wipe keys from memory after
12472 crypto_digest_get_digest and init_curve25519_keypair_from_file
12473 have finished using them. Resolves ticket 13477.
12475 o Minor features (security, out-of-memory handling):
12476 - When handling an out-of-memory condition, allocate less memory for
12477 temporary data structures. Fixes issue 10115.
12478 - When handling an out-of-memory condition, consider more types of
12479 buffers, including those on directory connections, and zlib
12480 buffers. Resolves ticket 11792.
12483 - When identity keypair is generated for first time, log a
12484 congratulatory message that links to the new relay lifecycle
12485 document. Implements feature 10427.
12487 o Minor features (client):
12488 - Clients are now willing to send optimistic data (before they
12489 receive a 'connected' cell) to relays of any version. (Relays
12490 without support for optimistic data are no longer supported on the
12491 Tor network.) Resolves ticket 13153.
12493 o Minor features (directory authorities):
12494 - Don't list relays with a bandwidth estimate of 0 in the consensus.
12495 Implements a feature proposed during discussion of bug 13000.
12496 - In tor-gencert, report an error if the user provides the same
12497 argument more than once.
12498 - If a directory authority can't find a best consensus method in the
12499 votes that it holds, it now falls back to its favorite consensus
12500 method. Previously, it fell back to method 1. Neither of these is
12501 likely to get enough signatures, but "fall back to favorite"
12502 doesn't require us to maintain support an obsolete consensus
12503 method. Implements part of proposal 215.
12505 o Minor features (logging):
12506 - On Unix-like systems, you can now use named pipes as the target of
12507 the Log option, and other options that try to append to files.
12508 Closes ticket 12061. Patch from "carlo von lynX".
12509 - When opening a log file at startup, send it every log message that
12510 we generated between startup and opening it. Previously, log
12511 messages that were generated before opening the log file were only
12512 logged to stdout. Closes ticket 6938.
12513 - Add a TruncateLogFile option to overwrite logs instead of
12514 appending to them. Closes ticket 5583.
12516 o Minor features (portability, Solaris):
12517 - Threads are no longer disabled by default on Solaris; we believe
12518 that the versions of Solaris with broken threading support are all
12519 obsolete by now. Resolves ticket 9495.
12521 o Minor features (relay):
12522 - Re-check our address after we detect a changed IP address from
12523 getsockname(). This ensures that the controller command "GETINFO
12524 address" will report the correct value. Resolves ticket 11582.
12526 - A new AccountingRule option lets Relays set whether they'd like
12527 AccountingMax to be applied separately to inbound and outbound
12528 traffic, or applied to the sum of inbound and outbound traffic.
12529 Resolves ticket 961. Patch by "chobe".
12531 o Minor features (testing networks):
12532 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
12533 the "Exit" flag regardless of their uptime, bandwidth, or exit
12534 policy. TestingTorNetwork must be set for this option to have any
12535 effect. Previously, authorities would take up to 35 minutes to
12536 give nodes the Exit flag in a test network. Partially implements
12539 o Minor features (validation):
12540 - Check all date/time values passed to tor_timegm and
12541 parse_rfc1123_time for validity, taking leap years into account.
12542 Improves HTTP header validation. Implemented with bug 13476.
12543 - In correct_tm(), limit the range of values returned by system
12544 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
12545 This means we don't have to deal with negative or too large dates,
12546 even if a clock is wrong. Otherwise we might fail to read a file
12547 written by us which includes such a date. Fixes bug 13476.
12549 o Minor bugfixes (bridge clients):
12550 - When configured to use a bridge without an identity digest (not
12551 recommended), avoid launching an extra channel to it when
12552 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
12554 o Minor bugfixes (bridges):
12555 - When DisableNetwork is set, do not launch pluggable transport
12556 plugins, and if any are running, terminate them. Fixes bug 13213;
12557 bugfix on 0.2.3.6-alpha.
12559 o Minor bugfixes (C correctness):
12560 - Fix several instances of possible integer overflow/underflow/NaN.
12561 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
12563 - In circuit_build_times_calculate_timeout() in circuitstats.c,
12564 avoid dividing by zero in the pareto calculations. This traps
12565 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
12567 - Fix an integer overflow in format_time_interval(). Fixes bug
12568 13393; bugfix on 0.2.0.10-alpha.
12569 - Set the correct day of year value when the system's localtime(_r)
12570 or gmtime(_r) functions fail to set struct tm. Not externally
12571 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
12572 - Avoid unlikely signed integer overflow in tor_timegm on systems
12573 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
12575 o Minor bugfixes (client):
12576 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
12577 BadExit flag are not considered worthy candidates. Fixes bug
12578 13066; bugfix on 0.1.2.3-alpha.
12579 - Use the consensus schedule for downloading consensuses, and not
12580 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
12581 - Handle unsupported or malformed SOCKS5 requests properly by
12582 responding with the appropriate error message before closing the
12583 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
12585 o Minor bugfixes (client, torrc):
12586 - Stop modifying the value of our DirReqStatistics torrc option just
12587 because we're not a bridge or relay. This bug was causing Tor
12588 Browser users to write "DirReqStatistics 0" in their torrc files
12589 as if they had chosen to change the config. Fixes bug 4244; bugfix
12591 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
12592 that our options have changed every time we SIGHUP. Fixes bug
12593 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
12595 o Minor bugfixes (controller):
12596 - Return an error when the second or later arguments of the
12597 "setevents" controller command are invalid events. Previously we
12598 would return success while silently skipping invalid events. Fixes
12599 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
12601 o Minor bugfixes (directory system):
12602 - Always believe that v3 directory authorities serve extra-info
12603 documents, whether they advertise "caches-extra-info" or not.
12604 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
12605 - When running as a v3 directory authority, advertise that you serve
12606 extra-info documents so that clients who want them can find them
12607 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
12608 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
12609 Previously, directories offering BRIDGE_DIRINFO and some other
12610 flag (i.e. microdescriptors or extrainfo) would be ignored when
12611 looking for bridges. Partially fixes bug 13163; bugfix
12614 o Minor bugfixes (networking):
12615 - Check for orconns and use connection_or_close_for_error() rather
12616 than connection_mark_for_close() directly in the getsockopt()
12617 failure case of connection_handle_write_impl(). Fixes bug 11302;
12618 bugfix on 0.2.4.4-alpha.
12620 o Minor bugfixes (relay):
12621 - When generating our family list, remove spaces from around the
12622 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
12623 - If our previous bandwidth estimate was 0 bytes, allow publishing a
12624 new relay descriptor immediately. Fixes bug 13000; bugfix
12627 o Minor bugfixes (testing networks):
12628 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
12629 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
12630 - Stop using the default authorities in networks which provide both
12631 AlternateDirAuthority and AlternateBridgeAuthority. Partially
12632 fixes bug 13163; bugfix on 0.2.0.13-alpha.
12634 o Minor bugfixes (testing):
12635 - Stop spawn test failures due to a race condition between the
12636 SIGCHLD handler updating the process status, and the test reading
12637 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
12639 o Minor bugfixes (testing, Windows):
12640 - Avoid passing an extra backslash when creating a temporary
12641 directory for running the unit tests on Windows. Fixes bug 12392;
12642 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
12644 o Minor bugfixes (windows):
12645 - Remove code to special-case handling of NTE_BAD_KEYSET when
12646 acquiring windows CryptoAPI context. This error can't actually
12647 occur for the parameters we're providing. Fixes bug 10816; bugfix
12650 o Minor bugfixes (zlib):
12651 - Avoid truncating a zlib stream when trying to finalize it with an
12652 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
12655 - Allow our configure script to build correctly with autoconf 2.62
12656 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
12657 - Improve the error message from ./configure to make it clear that
12658 when asciidoc has not been found, the user will have to either add
12659 --disable-asciidoc argument or install asciidoc. Resolves
12662 o Code simplification and refactoring:
12663 - Change the entry_is_live() function to take named bitfield
12664 elements instead of an unnamed list of booleans. Closes
12666 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
12667 Resolves ticket 12205.
12668 - Use calloc and reallocarray functions instead of multiply-
12669 then-malloc. This makes it less likely for us to fall victim to an
12670 integer overflow attack when allocating. Resolves ticket 12855.
12671 - Use the standard macro name SIZE_MAX, instead of our
12673 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
12674 functions which take them as arguments. Replace 0 with NO_DIRINFO
12675 in a function call for clarity. Seeks to prevent future issues
12677 - Avoid 4 null pointer errors under clang static analysis by using
12678 tor_assert() to prove that the pointers aren't null. Fixes
12680 - Rework the API of policies_parse_exit_policy() to use a bitmask to
12681 represent parsing options, instead of a confusing mess of
12682 booleans. Resolves ticket 8197.
12683 - Introduce a helper function to parse ExitPolicy in
12684 or_options_t structure.
12687 - Add a doc/TUNING document with tips for handling large numbers of
12688 TCP connections when running busy Tor relay. Update the warning
12689 message to point to this file when running out of sockets
12690 operating system is allowing to use simultaneously. Resolves
12693 o Removed features:
12694 - We no longer remind the user about configuration options that have
12695 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
12696 - Remove our old, non-weighted bandwidth-based node selection code.
12697 Previously, we used it as a fallback when we couldn't perform
12698 weighted bandwidth-based node selection. But that would only
12699 happen in the cases where we had no consensus, or when we had a
12700 consensus generated by buggy or ancient directory authorities. In
12701 either case, it's better to use the more modern, better maintained
12702 algorithm, with reasonable defaults for the weights. Closes
12704 - Remove the --disable-curve25519 configure option. Relays and
12705 clients now are required to support curve25519 and the
12707 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
12708 used to be deprecated synonyms for "StrictNodes", are now marked
12709 obsolete. Resolves ticket 12226.
12710 - Clients don't understand the BadDirectory flag in the consensus
12711 anymore, and ignore it.
12714 - Refactor the function that chooses guard nodes so that it can more
12715 easily be tested; write some tests for it.
12716 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
12717 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
12718 - Create unit tests for format_time_interval(). With bug 13393.
12719 - Add unit tests for tor_timegm signed overflow, tor_timegm and
12720 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
12721 tests (visible) fixes in bug 13476.
12722 - Add a "coverage-html" make target to generate HTML-visualized
12723 coverage results when building with --enable-coverage. (Requires
12724 lcov.) Patch from Kevin Murray.
12725 - Enable the backtrace handler (where supported) when running the
12727 - Revise all unit tests that used the legacy test_* macros to
12728 instead use the recommended tt_* macros. This patch was generated
12729 with coccinelle, to avoid manual errors. Closes ticket 13119.
12731 o Distribution (systemd):
12732 - systemd unit file: only allow tor to write to /var/lib/tor and
12733 /var/log/tor. The rest of the filesystem is accessible for reading
12734 only. Patch by intrigeri; resolves ticket 12751.
12735 - systemd unit file: ensure that the process and all its children
12736 can never gain new privileges. Patch by intrigeri; resolves
12738 - systemd unit file: set up /var/run/tor as writable for the Tor
12739 service. Patch by intrigeri; resolves ticket 13196.
12741 o Removed features (directory authorities):
12742 - Remove code that prevented authorities from listing Tor relays
12743 affected by CVE-2011-2769 as guards. These relays are already
12744 rejected altogether due to the minimum version requirement of
12745 0.2.3.16-alpha. Closes ticket 13152.
12746 - The "AuthDirRejectUnlisted" option no longer has any effect, as
12747 the fingerprints file (approved-routers) has been deprecated.
12748 - Directory authorities do not support being Naming dirauths anymore.
12749 The "NamingAuthoritativeDir" config option is now obsolete.
12750 - Directory authorities do not support giving out the BadDirectory
12752 - Directory authorities no longer advertise or support consensus
12753 methods 1 through 12 inclusive. These consensus methods were
12754 obsolete and/or insecure: maintaining the ability to support them
12755 served no good purpose. Implements part of proposal 215; closes
12758 o Testing (test-network.sh):
12759 - Stop using "echo -n", as some shells' built-in echo doesn't
12760 support "-n". Instead, use "/bin/echo -n". Partially fixes
12762 - Stop an apparent test-network hang when used with make -j2. Fixes
12764 - Add a --delay option to test-network.sh, which configures the
12765 delay before the chutney network tests for data transmission.
12766 Partially implements ticket 13161.
12769 Changes in version 0.2.5.10 - 2014-10-24
12770 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
12772 It adds several new security features, including improved
12773 denial-of-service resistance for relays, new compiler hardening
12774 options, and a system-call sandbox for hardened installations on Linux
12775 (requires seccomp2). The controller protocol has several new features,
12776 resolving IPv6 addresses should work better than before, and relays
12777 should be a little more CPU-efficient. We've added support for more
12778 OpenBSD and FreeBSD transparent proxy types. We've improved the build
12779 system and testing infrastructure to allow unit testing of more parts
12780 of the Tor codebase. Finally, we've addressed several nagging pluggable
12781 transport usability issues, and included numerous other small bugfixes
12782 and features mentioned below.
12784 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
12785 have accumulated many known flaws; everyone should upgrade.
12787 o Deprecated versions:
12788 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
12789 attention for some while.
12792 Changes in version 0.2.5.9-rc - 2014-10-20
12793 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
12794 series. It disables SSL3 in response to the recent "POODLE" attack
12795 (even though POODLE does not affect Tor). It also works around a crash
12796 bug caused by some operating systems' response to the "POODLE" attack
12797 (which does affect Tor). It also contains a few miscellaneous fixes.
12799 o Major security fixes:
12800 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
12801 today support TLS 1.0 or later, so we can safely turn off support
12802 for this old (and insecure) protocol. Fixes bug 13426.
12804 o Major bugfixes (openssl bug workaround):
12805 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
12806 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
12807 13471. This is a workaround for an OpenSSL bug.
12810 - Disable the sandbox name resolver cache when running tor-resolve:
12811 tor-resolve doesn't use the sandbox code, and turning it on was
12812 breaking attempts to do tor-resolve on a non-default server on
12813 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
12815 o Compilation fixes:
12816 - Build and run correctly on systems like OpenBSD-current that have
12817 patched OpenSSL to remove get_cipher_by_char and/or its
12818 implementations. Fixes issue 13325.
12820 o Downgraded warnings:
12821 - Downgrade the severity of the 'unexpected sendme cell from client'
12822 from 'warn' to 'protocol warning'. Closes ticket 8093.
12825 Changes in version 0.2.4.25 - 2014-10-20
12826 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
12827 (even though POODLE does not affect Tor). It also works around a crash
12828 bug caused by some operating systems' response to the "POODLE" attack
12829 (which does affect Tor).
12831 o Major security fixes (also in 0.2.5.9-rc):
12832 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
12833 today support TLS 1.0 or later, so we can safely turn off support
12834 for this old (and insecure) protocol. Fixes bug 13426.
12836 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
12837 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
12838 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
12839 13471. This is a workaround for an OpenSSL bug.
12842 Changes in version 0.2.5.8-rc - 2014-09-22
12843 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
12844 series. It fixes a bug that affects consistency and speed when
12845 connecting to hidden services, and it updates the location of one of
12846 the directory authorities.
12849 - Clients now send the correct address for their chosen rendezvous
12850 point when trying to access a hidden service. They used to send
12851 the wrong address, which would still work some of the time because
12852 they also sent the identity digest of the rendezvous point, and if
12853 the hidden service happened to try connecting to the rendezvous
12854 point from a relay that already had a connection open to it,
12855 the relay would reuse that connection. Now connections to hidden
12856 services should be more robust and faster. Also, this bug meant
12857 that clients were leaking to the hidden service whether they were
12858 on a little-endian (common) or big-endian (rare) system, which for
12859 some users might have reduced their anonymity. Fixes bug 13151;
12860 bugfix on 0.2.1.5-alpha.
12862 o Directory authority changes:
12863 - Change IP address for gabelmoo (v3 directory authority).
12866 Changes in version 0.2.4.24 - 2014-09-22
12867 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
12868 connecting to hidden services, and it updates the location of one of
12869 the directory authorities.
12872 - Clients now send the correct address for their chosen rendezvous
12873 point when trying to access a hidden service. They used to send
12874 the wrong address, which would still work some of the time because
12875 they also sent the identity digest of the rendezvous point, and if
12876 the hidden service happened to try connecting to the rendezvous
12877 point from a relay that already had a connection open to it,
12878 the relay would reuse that connection. Now connections to hidden
12879 services should be more robust and faster. Also, this bug meant
12880 that clients were leaking to the hidden service whether they were
12881 on a little-endian (common) or big-endian (rare) system, which for
12882 some users might have reduced their anonymity. Fixes bug 13151;
12883 bugfix on 0.2.1.5-alpha.
12885 o Directory authority changes:
12886 - Change IP address for gabelmoo (v3 directory authority).
12888 o Minor features (geoip):
12889 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
12893 Changes in version 0.2.5.7-rc - 2014-09-11
12894 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
12895 release series, and some long-standing bugs related to ORPort reachability
12896 testing and failure to send CREATE cells. It is the first release
12897 candidate for the Tor 0.2.5.x series.
12899 o Major bugfixes (client, startup):
12900 - Start making circuits as soon as DisabledNetwork is turned off.
12901 When Tor started with DisabledNetwork set, it would correctly
12902 conclude that it shouldn't build circuits, but it would mistakenly
12903 cache this conclusion, and continue believing it even when
12904 DisableNetwork is set to 0. Fixes the bug introduced by the fix
12905 for bug 11200; bugfix on 0.2.5.4-alpha.
12906 - Resume expanding abbreviations for command-line options. The fix
12907 for bug 4647 accidentally removed our hack from bug 586 that
12908 rewrote HashedControlPassword to __HashedControlSessionPassword
12909 when it appears on the commandline (which allowed the user to set
12910 her own HashedControlPassword in the torrc file while the
12911 controller generates a fresh session password for each run). Fixes
12912 bug 12948; bugfix on 0.2.5.1-alpha.
12913 - Warn about attempts to run hidden services and relays in the same
12914 process: that's probably not a good idea. Closes ticket 12908.
12916 o Major bugfixes (relay):
12917 - Avoid queuing or sending destroy cells for circuit ID zero when we
12918 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
12919 Found and fixed by "cypherpunks".
12920 - Fix ORPort reachability detection on relays running behind a
12921 proxy, by correctly updating the "local" mark on the controlling
12922 channel when changing the address of an or_connection_t after the
12923 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
12925 o Minor features (bridge):
12926 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
12927 cookie file for the ExtORPort g+r by default.
12929 o Minor features (geoip):
12930 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
12933 o Minor bugfixes (logging):
12934 - Reduce the log severity of the "Pluggable transport proxy does not
12935 provide any needed transports and will not be launched." message,
12936 since Tor Browser includes several ClientTransportPlugin lines in
12937 its torrc-defaults file, leading every Tor Browser user who looks
12938 at her logs to see these notices and wonder if they're dangerous.
12939 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
12940 - Downgrade "Unexpected onionskin length after decryption" warning
12941 to a protocol-warn, since there's nothing relay operators can do
12942 about a client that sends them a malformed create cell. Resolves
12943 bug 12996; bugfix on 0.0.6rc1.
12944 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
12945 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
12946 - When logging information about an EXTEND2 or EXTENDED2 cell, log
12947 their names correctly. Fixes part of bug 12700; bugfix
12949 - When logging information about a relay cell whose command we don't
12950 recognize, log its command as an integer. Fixes part of bug 12700;
12951 bugfix on 0.2.1.10-alpha.
12952 - Escape all strings from the directory connection before logging
12953 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
12955 o Minor bugfixes (controller):
12956 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
12957 bug 12864; bugfix on 0.2.5.1-alpha.
12958 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
12959 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
12962 o Minor bugfixes (compilation):
12963 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
12964 bugfix on 0.2.5.5-alpha.
12965 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
12966 0.2.5.1-alpha. Patch from "NewEraCracker".
12967 - In routerlist_assert_ok(), don't take the address of a
12968 routerinfo's cache_info member unless that routerinfo is non-NULL.
12969 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
12970 - Fix a large number of false positive warnings from the clang
12971 analyzer static analysis tool. This should make real warnings
12972 easier for clang analyzer to find. Patch from "teor". Closes
12975 o Distribution (systemd):
12976 - Verify configuration file via ExecStartPre in the systemd unit
12977 file. Patch from intrigeri; resolves ticket 12730.
12978 - Explicitly disable RunAsDaemon in the systemd unit file. Our
12979 current systemd unit uses "Type = simple", so systemd does not
12980 expect tor to fork. If the user has "RunAsDaemon 1" in their
12981 torrc, then things won't work as expected. This is e.g. the case
12982 on Debian (and derivatives), since there we pass "--defaults-torrc
12983 /usr/share/tor/tor-service-defaults-torrc" (that contains
12984 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
12988 - Adjust the URLs in the README to refer to the new locations of
12989 several documents on the website. Fixes bug 12830. Patch from
12991 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
12995 Changes in version 0.2.5.6-alpha - 2014-07-28
12996 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
12997 risk from guard rotation, and fixes a variety of other issues to get
12998 us closer to a release candidate.
13000 o Major features (also in 0.2.4.23):
13001 - Make the number of entry guards configurable via a new
13002 NumEntryGuards consensus parameter, and the number of directory
13003 guards configurable via a new NumDirectoryGuards consensus
13004 parameter. Implements ticket 12688.
13006 o Major bugfixes (also in 0.2.4.23):
13007 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
13008 implementation that caused incorrect results on 32-bit
13009 implementations when certain malformed inputs were used along with
13010 a small class of private ntor keys. This bug does not currently
13011 appear to allow an attacker to learn private keys or impersonate a
13012 Tor server, but it could provide a means to distinguish 32-bit Tor
13013 implementations from 64-bit Tor implementations. Fixes bug 12694;
13014 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
13018 - Perform circuit cleanup operations even when circuit
13019 construction operations are disabled (because the network is
13020 disabled, or because there isn't enough directory information).
13021 Previously, when we were not building predictive circuits, we
13022 were not closing expired circuits either. Fixes bug 8387; bugfix on
13023 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
13024 became more strict about when we have "enough directory information
13025 to build circuits".
13028 - Authorities now assign the Guard flag to the fastest 25% of the
13029 network (it used to be the fastest 50%). Also raise the consensus
13030 weight that guarantees the Guard flag from 250 to 2000. For the
13031 current network, this results in about 1100 guards, down from 2500.
13032 This step paves the way for moving the number of entry guards
13033 down to 1 (proposal 236) while still providing reasonable expected
13034 performance for most users. Implements ticket 12690.
13035 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
13037 - Slightly enhance the diagnostic message for bug 12184.
13039 o Minor bugfixes (also in 0.2.4.23):
13040 - Warn and drop the circuit if we receive an inbound 'relay early'
13041 cell. Those used to be normal to receive on hidden service circuits
13042 due to bug 1038, but the buggy Tor versions are long gone from
13043 the network so we can afford to resume watching for them. Resolves
13044 the rest of bug 1038; bugfix on 0.2.1.19.
13045 - Correct a confusing error message when trying to extend a circuit
13046 via the control protocol but we don't know a descriptor or
13047 microdescriptor for one of the specified relays. Fixes bug 12718;
13048 bugfix on 0.2.3.1-alpha.
13051 - Fix compilation when building with bufferevents enabled. (This
13052 configuration is still not expected to work, however.)
13053 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
13054 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
13056 - Compile correctly with builds and forks of OpenSSL (such as
13057 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
13058 0.2.1.1-alpha. Patch from "dhill".
13061 Changes in version 0.2.4.23 - 2014-07-28
13062 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
13063 guard rotation, and also backports several important fixes from the
13064 Tor 0.2.5 alpha release series.
13067 - Clients now look at the "usecreatefast" consensus parameter to
13068 decide whether to use CREATE_FAST or CREATE cells for the first hop
13069 of their circuit. This approach can improve security on connections
13070 where Tor's circuit handshake is stronger than the available TLS
13071 connection security levels, but the tradeoff is more computational
13072 load on guard relays. Implements proposal 221. Resolves ticket 9386.
13073 - Make the number of entry guards configurable via a new
13074 NumEntryGuards consensus parameter, and the number of directory
13075 guards configurable via a new NumDirectoryGuards consensus
13076 parameter. Implements ticket 12688.
13079 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
13080 implementation that caused incorrect results on 32-bit
13081 implementations when certain malformed inputs were used along with
13082 a small class of private ntor keys. This bug does not currently
13083 appear to allow an attacker to learn private keys or impersonate a
13084 Tor server, but it could provide a means to distinguish 32-bit Tor
13085 implementations from 64-bit Tor implementations. Fixes bug 12694;
13086 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
13090 - Warn and drop the circuit if we receive an inbound 'relay early'
13091 cell. Those used to be normal to receive on hidden service circuits
13092 due to bug 1038, but the buggy Tor versions are long gone from
13093 the network so we can afford to resume watching for them. Resolves
13094 the rest of bug 1038; bugfix on 0.2.1.19.
13095 - Correct a confusing error message when trying to extend a circuit
13096 via the control protocol but we don't know a descriptor or
13097 microdescriptor for one of the specified relays. Fixes bug 12718;
13098 bugfix on 0.2.3.1-alpha.
13099 - Avoid an illegal read from stack when initializing the TLS
13100 module using a version of OpenSSL without all of the ciphers
13101 used by the v2 link handshake. Fixes bug 12227; bugfix on
13102 0.2.4.8-alpha. Found by "starlight".
13105 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
13109 Changes in version 0.2.5.5-alpha - 2014-06-18
13110 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
13111 0.2.5.x release series, including a couple of DoS issues, some
13112 performance regressions, a large number of bugs affecting the Linux
13113 seccomp2 sandbox code, and various other bugfixes. It also adds
13114 diagnostic bugfixes for a few tricky issues that we're trying to
13117 o Major features (security, traffic analysis resistance):
13118 - Several major improvements to the algorithm used to decide when to
13119 close TLS connections. Previous versions of Tor closed connections
13120 at a fixed interval after the last time a non-padding cell was
13121 sent over the connection, regardless of the target of the
13122 connection. Now, we randomize the intervals by adding up to 50% of
13123 their base value, we measure the length of time since connection
13124 last had at least one circuit, and we allow connections to known
13125 ORs to remain open a little longer (15 minutes instead of 3
13126 minutes minimum). These changes should improve Tor's resistance
13127 against some kinds of traffic analysis, and lower some overhead
13128 from needlessly closed connections. Fixes ticket 6799.
13129 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
13131 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
13132 - Fix a memory leak that could occur if a microdescriptor parse
13133 fails during the tokenizing step. This bug could enable a memory
13134 exhaustion attack by directory servers. Fixes bug 11649; bugfix
13137 o Major bugfixes (security, directory authorities):
13138 - Directory authorities now include a digest of each relay's
13139 identity key as a part of its microdescriptor.
13141 This is a workaround for bug 11743 (reported by "cypherpunks"),
13142 where Tor clients do not support receiving multiple
13143 microdescriptors with the same SHA256 digest in the same
13144 consensus. When clients receive a consensus like this, they only
13145 use one of the relays. Without this fix, a hostile relay could
13146 selectively disable some client use of target relays by
13147 constructing a router descriptor with a different identity and the
13148 same microdescriptor parameters and getting the authorities to
13149 list it in a microdescriptor consensus. This fix prevents an
13150 attacker from causing a microdescriptor collision, because the
13151 router's identity is not forgeable.
13153 o Major bugfixes (relay):
13154 - Use a direct dirport connection when uploading non-anonymous
13155 descriptors to the directory authorities. Previously, relays would
13156 incorrectly use tunnel connections under a fairly wide variety of
13157 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
13158 - When a circuit accidentally has the same circuit ID for its
13159 forward and reverse direction, correctly detect the direction of
13160 cells using that circuit. Previously, this bug made roughly one
13161 circuit in a million non-functional. Fixes bug 12195; this is a
13162 bugfix on every version of Tor.
13164 o Major bugfixes (client, pluggable transports):
13165 - When managing pluggable transports, use OS notification facilities
13166 to learn if they have crashed, and don't attempt to kill any
13167 process that has already exited. Fixes bug 8746; bugfix
13170 o Minor features (diagnostic):
13171 - When logging a warning because of bug 7164, additionally check the
13172 hash table for consistency (as proposed on ticket 11737). This may
13173 help diagnose bug 7164.
13174 - When we log a heartbeat, log how many one-hop circuits we have
13175 that are at least 30 minutes old, and log status information about
13176 a few of them. This is an attempt to track down bug 8387.
13177 - When encountering an unexpected CR while writing text to a file on
13178 Windows, log the name of the file. Should help diagnosing
13180 - Give more specific warnings when a client notices that an onion
13181 handshake has failed. Fixes ticket 9635.
13182 - Add significant new logging code to attempt to diagnose bug 12184,
13183 where relays seem to run out of available circuit IDs.
13184 - Improve the diagnostic log message for bug 8387 even further to
13185 try to improve our odds of figuring out why one-hop directory
13186 circuits sometimes do not get closed.
13188 o Minor features (security, memory management):
13189 - Memory allocation tricks (mempools and buffer freelists) are now
13190 disabled by default. You can turn them back on with
13191 --enable-mempools and --enable-buf-freelists respectively. We're
13192 disabling these features because malloc performance is good enough
13193 on most platforms, and a similar feature in OpenSSL exacerbated
13194 exploitation of the Heartbleed attack. Resolves ticket 11476.
13196 o Minor features (security):
13197 - Apply the secure SipHash-2-4 function to the hash table mapping
13198 circuit IDs and channels to circuits. We missed this one when we
13199 were converting all the other hash functions to use SipHash back
13200 in 0.2.5.3-alpha. Resolves ticket 11750.
13202 o Minor features (build):
13203 - The configure script has a --disable-seccomp option to turn off
13204 support for libseccomp on systems that have it, in case it (or
13205 Tor's use of it) is broken. Resolves ticket 11628.
13207 o Minor features (other):
13208 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
13211 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
13212 - When running a hidden service, do not allow TunneledDirConns 0;
13213 this will keep the hidden service from running, and also
13214 make it publish its descriptors directly over HTTP. Fixes bug 10849;
13215 bugfix on 0.2.1.1-alpha.
13217 o Minor bugfixes (performance):
13218 - Avoid a bug where every successful connection made us recompute
13219 the flag telling us whether we have sufficient information to
13220 build circuits. Previously, we would forget our cached value
13221 whenever we successfully opened a channel (or marked a router as
13222 running or not running for any other reason), regardless of
13223 whether we had previously believed the router to be running. This
13224 forced us to run an expensive update operation far too often.
13225 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
13226 - Avoid using tor_memeq() for checking relay cell integrity. This
13227 removes a possible performance bottleneck. Fixes part of bug
13228 12169; bugfix on 0.2.1.31.
13230 o Minor bugfixes (compilation):
13231 - Fix compilation of test_status.c when building with MVSC. Bugfix
13232 on 0.2.5.4-alpha. Patch from Gisle Vanem.
13233 - Resolve GCC complaints on OpenBSD about discarding constness in
13234 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
13235 on 0.1.1.23. Patch from Dana Koch.
13236 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
13237 treatment of long and time_t as comparable types. Fixes part of
13238 bug 11633. Patch from Dana Koch.
13239 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
13240 11623; bugfix on 0.2.5.3-alpha.
13241 - When deciding whether to build the 64-bit curve25519
13242 implementation, detect platforms where we can compile 128-bit
13243 arithmetic but cannot link it. Fixes bug 11729; bugfix on
13244 0.2.4.8-alpha. Patch from "conradev".
13245 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
13246 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
13247 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
13250 o Minor bugfixes (Directory server):
13251 - When sending a compressed set of descriptors or microdescriptors,
13252 make sure to finalize the zlib stream. Previously, we would write
13253 all the compressed data, but if the last descriptor we wanted to
13254 send was missing or too old, we would not mark the stream as
13255 finished. This caused problems for decompression tools. Fixes bug
13256 11648; bugfix on 0.1.1.23.
13258 o Minor bugfixes (Linux seccomp sandbox):
13259 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
13260 11622; bugfix on 0.2.5.1-alpha.
13261 - Avoid crashing when re-opening listener ports with the seccomp
13262 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
13263 - Avoid crashing with the seccomp sandbox enabled along with
13264 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
13265 - When we receive a SIGHUP with the sandbox enabled, correctly
13266 support rotating our log files. Fixes bug 12032; bugfix
13268 - Avoid crash when running with sandboxing enabled and
13269 DirReqStatistics not disabled. Fixes bug 12035; bugfix
13271 - Fix a "BUG" warning when trying to write bridge-stats files with
13272 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
13274 - Prevent the sandbox from crashing on startup when run with the
13275 --enable-expensive-hardening configuration option. Fixes bug
13276 11477; bugfix on 0.2.5.4-alpha.
13277 - When running with DirPortFrontPage and sandboxing both enabled,
13278 reload the DirPortFrontPage correctly when restarting. Fixes bug
13279 12028; bugfix on 0.2.5.1-alpha.
13280 - Don't try to enable the sandbox when using the Tor binary to check
13281 its configuration, hash a passphrase, or so on. Doing so was
13282 crashing on startup for some users. Fixes bug 11609; bugfix
13284 - Avoid warnings when running with sandboxing and node statistics
13285 enabled at the same time. Fixes part of 12064; bugfix on
13286 0.2.5.1-alpha. Patch from Michael Wolf.
13287 - Avoid warnings when running with sandboxing enabled at the same
13288 time as cookie authentication, hidden services, or directory
13289 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
13290 - Do not allow options that require calls to exec to be enabled
13291 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
13292 bug 12043; bugfix on 0.2.5.1-alpha.
13293 - Handle failures in getpwnam()/getpwuid() when running with the
13294 User option set and the Linux syscall sandbox enabled. Fixes bug
13295 11946; bugfix on 0.2.5.1-alpha.
13296 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
13297 to avoid calling getaddrinfo() after installing the sandbox
13298 filters. Previously, it preloaded a cache with the IPv4 address
13299 for our hostname, and nothing else. Now, it loads the cache with
13300 every address that it used to initialize the Tor process. Fixes
13301 bug 11970; bugfix on 0.2.5.1-alpha.
13303 o Minor bugfixes (pluggable transports):
13304 - Enable the ExtORPortCookieAuthFile option, to allow changing the
13305 default location of the authentication token for the extended OR
13306 Port as used by sever-side pluggable transports. We had
13307 implemented this option before, but the code to make it settable
13308 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
13309 - Avoid another 60-second delay when starting Tor in a pluggable-
13310 transport-using configuration when we already have cached
13311 descriptors for our bridges. Fixes bug 11965; bugfix
13314 o Minor bugfixes (client):
13315 - Avoid "Tried to open a socket with DisableNetwork set" warnings
13316 when starting a client with bridges configured and DisableNetwork
13317 set. (Tor launcher starts Tor with DisableNetwork set the first
13318 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
13320 o Minor bugfixes (testing):
13321 - The Python parts of the test scripts now work on Python 3 as well
13322 as Python 2, so systems where '/usr/bin/python' is Python 3 will
13323 no longer have the tests break. Fixes bug 11608; bugfix
13325 - When looking for versions of python that we could run the tests
13326 with, check for "python2.7" and "python3.3"; previously we were
13327 only looking for "python", "python2", and "python3". Patch from
13328 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
13329 - Fix all valgrind warnings produced by the unit tests. There were
13330 over a thousand memory leak warnings previously, mostly produced
13331 by forgetting to free things in the unit test code. Fixes bug
13332 11618, bugfixes on many versions of Tor.
13334 o Minor bugfixes (tor-fw-helper):
13335 - Give a correct log message when tor-fw-helper fails to launch.
13336 (Previously, we would say something like "tor-fw-helper sent us a
13337 string we could not parse".) Fixes bug 9781; bugfix
13340 o Minor bugfixes (relay, threading):
13341 - Check return code on spawn_func() in cpuworker code, so that we
13342 don't think we've spawned a nonworking cpuworker and write junk to
13343 it forever. Fix related to bug 4345; bugfix on all released Tor
13344 versions. Found by "skruffy".
13345 - Use a pthread_attr to make sure that spawn_func() cannot return an
13346 error while at the same time launching a thread. Fix related to
13347 bug 4345; bugfix on all released Tor versions. Reported
13350 o Minor bugfixes (relay, oom prevention):
13351 - Correctly detect the total available system memory. We tried to do
13352 this in 0.2.5.4-alpha, but the code was set up to always return an
13353 error value, even on success. Fixes bug 11805; bugfix
13356 o Minor bugfixes (relay, other):
13357 - We now drop CREATE cells for already-existent circuit IDs and for
13358 zero-valued circuit IDs, regardless of other factors that might
13359 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
13361 - Avoid an illegal read from stack when initializing the TLS module
13362 using a version of OpenSSL without all of the ciphers used by the
13363 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
13365 - When rejecting DATA cells for stream_id zero, still count them
13366 against the circuit's deliver window so that we don't fail to send
13367 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
13369 o Minor bugfixes (logging):
13370 - Fix a misformatted log message about delayed directory fetches.
13371 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
13372 - Squelch a spurious LD_BUG message "No origin circuit for
13373 successful SOCKS stream" in certain hidden service failure cases;
13377 - Include a tor.service file in contrib/dist for use with systemd.
13378 Some distributions will be able to use this file unmodified;
13379 others will need to tweak it, or write their own. Patch from Jamie
13380 Nguyen; resolves ticket 8368.
13383 - Clean up several option names in the manpage to match their real
13384 names, add the missing documentation for a couple of testing and
13385 directory authority options, remove the documentation for a
13386 V2-directory fetching option that no longer exists. Resolves
13388 - Correct the documentation so that it lists the correct directory
13389 for the stats files. (They are in a subdirectory called "stats",
13391 - In the manpage, move more authority-only options into the
13392 directory authority section so that operators of regular directory
13393 caches don't get confused.
13396 - The contrib directory has been sorted and tidied. Before, it was
13397 an unsorted dumping ground for useful and not-so-useful things.
13398 Now, it is divided based on functionality, and the items which
13399 seemed to be nonfunctional or useless have been removed. Resolves
13400 ticket 8966; based on patches from "rl1987".
13403 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
13404 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
13405 - The TunnelDirConns and PreferTunnelledDirConns options no longer
13406 exist; tunneled directory connections have been available since
13407 0.1.2.5-alpha, and turning them off is not a good idea. This is a
13408 brute-force fix for 10849, where "TunnelDirConns 0" would break
13412 Changes in version 0.2.4.22 - 2014-05-16
13413 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
13414 alpha release series. These include blocking all authority signing
13415 keys that may have been affected by the OpenSSL "heartbleed" bug,
13416 choosing a far more secure set of TLS ciphersuites by default, closing
13417 a couple of memory leaks that could be used to run a target relay out
13418 of RAM, and several others.
13420 o Major features (security, backport from 0.2.5.4-alpha):
13421 - Block authority signing keys that were used on authorities
13422 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
13423 don't have any evidence that these keys _were_ compromised; we're
13424 doing this to be prudent.) Resolves ticket 11464.
13426 o Major bugfixes (security, OOM):
13427 - Fix a memory leak that could occur if a microdescriptor parse
13428 fails during the tokenizing step. This bug could enable a memory
13429 exhaustion attack by directory servers. Fixes bug 11649; bugfix
13432 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
13433 - The relay ciphersuite list is now generated automatically based on
13434 uniform criteria, and includes all OpenSSL ciphersuites with
13435 acceptable strength and forward secrecy. Previously, we had left
13436 some perfectly fine ciphersuites unsupported due to omission or
13437 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
13438 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
13439 - Relays now trust themselves to have a better view than clients of
13440 which TLS ciphersuites are better than others. (Thanks to bug
13441 11513, the relay list is now well-considered, whereas the client
13442 list has been chosen mainly for anti-fingerprinting purposes.)
13443 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
13444 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
13445 AES128. Resolves ticket 11528.
13446 - Clients now try to advertise the same list of ciphersuites as
13447 Firefox 28. This change enables selection of (fast) GCM
13448 ciphersuites, disables some strange old ciphers, and stops
13449 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
13450 Resolves ticket 11438.
13452 o Minor bugfixes (configuration, security):
13453 - When running a hidden service, do not allow TunneledDirConns 0:
13454 trying to set that option together with a hidden service would
13455 otherwise prevent the hidden service from running, and also make
13456 it publish its descriptors directly over HTTP. Fixes bug 10849;
13457 bugfix on 0.2.1.1-alpha.
13459 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
13460 - Avoid sending a garbage value to the controller when a circuit is
13461 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
13463 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
13464 - Stop leaking memory when we successfully resolve a PTR record.
13465 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
13467 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
13468 - Avoid 60-second delays in the bootstrapping process when Tor is
13469 launching for a second time while using bridges. Fixes bug 9229;
13470 bugfix on 0.2.0.3-alpha.
13472 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
13473 - Give the correct URL in the warning message when trying to run a
13474 relay on an ancient version of Windows. Fixes bug 9393.
13476 o Minor bugfixes (compilation):
13477 - Fix a compilation error when compiling with --disable-curve25519.
13478 Fixes bug 9700; bugfix on 0.2.4.17-rc.
13481 - Downgrade the warning severity for the the "md was still
13482 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
13483 for trying to diagnose this bug, and the current warning in
13484 earlier versions of tor achieves nothing useful. Addresses warning
13487 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
13488 - When we run out of usable circuit IDs on a channel, log only one
13489 warning for the whole channel, and describe how many circuits
13490 there were on the channel. Fixes part of ticket 11553.
13492 o Minor features (security, backport from 0.2.5.4-alpha):
13493 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
13494 leave the default at 8GBytes), to better support Raspberry Pi
13495 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
13497 o Documentation (backport from 0.2.5.4-alpha):
13498 - Correctly document that we search for a system torrc file before
13499 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
13503 Changes in version 0.2.5.4-alpha - 2014-04-25
13504 Tor 0.2.5.4-alpha includes several security and performance
13505 improvements for clients and relays, including blacklisting authority
13506 signing keys that were used while susceptible to the OpenSSL
13507 "heartbleed" bug, fixing two expensive functions on busy relays,
13508 improved TLS ciphersuite preference lists, support for run-time
13509 hardening on compilers that support AddressSanitizer, and more work on
13510 the Linux sandbox code.
13512 There are also several usability fixes for clients (especially clients
13513 that use bridges), two new TransPort protocols supported (one on
13514 OpenBSD, one on FreeBSD), and various other bugfixes.
13516 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
13517 have accumulated many known flaws; everyone should upgrade.
13519 o Major features (security):
13520 - If you don't specify MaxMemInQueues yourself, Tor now tries to
13521 pick a good value based on your total system memory. Previously,
13522 the default was always 8 GB. You can still override the default by
13523 setting MaxMemInQueues yourself. Resolves ticket 11396.
13524 - Block authority signing keys that were used on authorities
13525 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
13526 don't have any evidence that these keys _were_ compromised; we're
13527 doing this to be prudent.) Resolves ticket 11464.
13529 o Major features (relay performance):
13530 - Speed up server-side lookups of rendezvous and introduction point
13531 circuits by using hashtables instead of linear searches. These
13532 functions previously accounted between 3 and 7% of CPU usage on
13533 some busy relays. Resolves ticket 9841.
13534 - Avoid wasting CPU when extending a circuit over a channel that is
13535 nearly out of circuit IDs. Previously, we would do a linear scan
13536 over possible circuit IDs before finding one or deciding that we
13537 had exhausted our possibilities. Now, we try at most 64 random
13538 circuit IDs before deciding that we probably won't succeed. Fixes
13539 a possible root cause of ticket 11553.
13541 o Major features (seccomp2 sandbox, Linux only):
13542 - The seccomp2 sandbox can now run a test network for multiple hours
13543 without crashing. The sandbox is still experimental, and more bugs
13544 will probably turn up. To try it, enable "Sandbox 1" on a Linux
13545 host. Resolves ticket 11351.
13546 - Strengthen sandbox code: the sandbox can now test the arguments
13547 for rename(), and blocks _sysctl() entirely. Resolves another part
13549 - When the sandbox blocks a system call, it now tries to log a stack
13550 trace before exiting. Resolves ticket 11465.
13552 o Major bugfixes (TLS cipher selection):
13553 - The relay ciphersuite list is now generated automatically based on
13554 uniform criteria, and includes all OpenSSL ciphersuites with
13555 acceptable strength and forward secrecy. Previously, we had left
13556 some perfectly fine ciphersuites unsupported due to omission or
13557 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
13558 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
13559 - Relays now trust themselves to have a better view than clients of
13560 which TLS ciphersuites are better than others. (Thanks to bug
13561 11513, the relay list is now well-considered, whereas the client
13562 list has been chosen mainly for anti-fingerprinting purposes.)
13563 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
13564 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
13565 AES128. Resolves ticket 11528.
13566 - Clients now try to advertise the same list of ciphersuites as
13567 Firefox 28. This change enables selection of (fast) GCM
13568 ciphersuites, disables some strange old ciphers, and stops
13569 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
13570 Resolves ticket 11438.
13572 o Major bugfixes (bridge client):
13573 - Avoid 60-second delays in the bootstrapping process when Tor is
13574 launching for a second time while using bridges. Fixes bug 9229;
13575 bugfix on 0.2.0.3-alpha.
13577 o Minor features (transparent proxy, *BSD):
13578 - Support FreeBSD's ipfw firewall interface for TransPort ports on
13579 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
13580 10267; patch from "yurivict".
13581 - Support OpenBSD's divert-to rules with the pf firewall for
13582 transparent proxy ports. To enable it, set "TransProxyType
13583 pf-divert". This allows Tor to run a TransPort transparent proxy
13584 port on OpenBSD 4.4 or later without root privileges. See the
13585 pf.conf(5) manual page for information on configuring pf to use
13586 divert-to rules. Closes ticket 10896; patch from Dana Koch.
13588 o Minor features (security):
13589 - New --enable-expensive-hardening option to enable security
13590 hardening options that consume nontrivial amounts of CPU and
13591 memory. Right now, this includes AddressSanitizer and UbSan, which
13592 are supported in newer versions of GCC and Clang. Closes ticket
13595 o Minor features (log verbosity):
13596 - Demote the message that we give when a flushing connection times
13597 out for too long from NOTICE to INFO. It was usually meaningless.
13598 Resolves ticket 5286.
13599 - Don't log so many notice-level bootstrapping messages at startup
13600 about downloading descriptors. Previously, we'd log a notice
13601 whenever we learned about more routers. Now, we only log a notice
13602 at every 5% of progress. Fixes bug 9963.
13603 - Warn less verbosely when receiving a malformed
13604 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
13605 - When we run out of usable circuit IDs on a channel, log only one
13606 warning for the whole channel, and describe how many circuits
13607 there were on the channel. Fixes part of ticket 11553.
13609 o Minor features (relay):
13610 - If a circuit timed out for at least 3 minutes, check if we have a
13611 new external IP address, and publish a new descriptor with the new
13612 IP address if it changed. Resolves ticket 2454.
13614 o Minor features (controller):
13615 - Make the entire exit policy available from the control port via
13616 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
13618 - Because of the fix for ticket 11396, the real limit for memory
13619 usage may no longer match the configured MaxMemInQueues value. The
13620 real limit is now exposed via GETINFO limits/max-mem-in-queues.
13622 o Minor features (bridge client):
13623 - Report a more useful failure message when we can't connect to a
13624 bridge because we don't have the right pluggable transport
13625 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
13627 o Minor features (diagnostic):
13628 - Add more log messages to diagnose bug 7164, which causes
13629 intermittent "microdesc_free() called but md was still referenced"
13630 warnings. We now include more information, to figure out why we
13631 might be cleaning a microdescriptor for being too old if it's
13632 still referenced by a live node_t object.
13634 o Minor bugfixes (client, DNSPort):
13635 - When using DNSPort, try to respond to AAAA requests with AAAA
13636 answers. Previously, we hadn't looked at the request type when
13637 deciding which answer type to prefer. Fixes bug 10468; bugfix on
13639 - When receiving a DNS query for an unsupported record type, reply
13640 with no answer rather than with a NOTIMPL error. This behavior
13641 isn't correct either, but it will break fewer client programs, we
13642 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
13645 o Minor bugfixes (exit relay):
13646 - Stop leaking memory when we successfully resolve a PTR record.
13647 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
13649 o Minor bugfixes (bridge client):
13650 - Stop accepting bridge lines containing hostnames. Doing so would
13651 cause clients to perform DNS requests on the hostnames, which was
13652 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
13653 - Avoid a 60-second delay in the bootstrapping process when a Tor
13654 client with pluggable transports re-reads its configuration at
13655 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
13657 o Minor bugfixes (client, logging during bootstrap):
13658 - Warn only once if we start logging in an unsafe way. Previously,
13659 we complain as many times as we had problems. Fixes bug 9870;
13660 bugfix on 0.2.5.1-alpha.
13661 - Only report the first fatal bootstrap error on a given OR
13662 connection. This stops us from telling the controller bogus error
13663 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
13664 - Be more helpful when trying to run sandboxed on Linux without
13665 libseccomp. Instead of saying "Sandbox is not implemented on this
13666 platform", we now explain that we need to be built with
13667 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
13668 - Avoid generating spurious warnings when starting with
13669 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
13672 o Minor bugfixes (closing OR connections):
13673 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
13674 check if it's an or_connection_t and correctly call
13675 connection_or_close_for_error() rather than
13676 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
13678 - When closing all connections on setting DisableNetwork to 1, use
13679 connection_or_close_normally() rather than closing OR connections
13680 out from under the channel layer. Fixes bug 11306; bugfix on
13683 o Minor bugfixes (controller):
13684 - Avoid sending a garbage value to the controller when a circuit is
13685 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
13687 o Minor bugfixes (tor-fw-helper):
13688 - Allow tor-fw-helper to build again by adding src/ext to its
13689 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
13691 o Minor bugfixes (bridges):
13692 - Avoid potential crashes or bad behavior when launching a
13693 server-side managed proxy with ORPort or ExtORPort temporarily
13694 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
13696 o Minor bugfixes (platform-specific):
13697 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
13698 bug 11426; bugfix on 0.2.5.3-alpha.
13699 - When dumping a malformed directory object to disk, save it in
13700 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
13702 - Don't report failures from make_socket_reuseable() on incoming
13703 sockets on OSX: this can happen when incoming connections close
13704 early. Fixes bug 10081.
13706 o Minor bugfixes (trivial memory leaks):
13707 - Fix a small memory leak when signing a directory object. Fixes bug
13708 11275; bugfix on 0.2.4.13-alpha.
13709 - Free placeholder entries in our circuit table at exit; fixes a
13710 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
13711 - Don't re-initialize a second set of OpenSSL mutexes when starting
13712 up. Previously, we'd make one set of mutexes, and then immediately
13713 replace them with another. Fixes bug 11726; bugfix on
13715 - Resolve some memory leaks found by coverity in the unit tests, on
13716 exit in tor-gencert, and on a failure to compute digests for our
13717 own keys when generating a v3 networkstatus vote. These leaks
13718 should never have affected anyone in practice.
13720 o Minor bugfixes (hidden service):
13721 - Only retry attempts to connect to a chosen rendezvous point 8
13722 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
13724 o Minor bugfixes (misc code correctness):
13725 - Fix various instances of undefined behavior in channeltls.c,
13726 tor_memmem(), and eventdns.c that would cause us to construct
13727 pointers to memory outside an allocated object. (These invalid
13728 pointers were not accessed, but C does not even allow them to
13729 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
13730 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
13731 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
13732 fix some miscellaneous errors in our tests and codebase. Fixes bug
13733 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
13734 - Always check return values for unlink, munmap, UnmapViewOfFile;
13735 check strftime return values more often. In some cases all we can
13736 do is report a warning, but this may help prevent deeper bugs from
13737 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
13739 - Fix numerous warnings from the clang "scan-build" static analyzer.
13740 Some of these are programming style issues; some of them are false
13741 positives that indicated awkward code; some are undefined behavior
13742 cases related to constructing (but not using) invalid pointers;
13743 some are assumptions about API behavior; some are (harmlessly)
13744 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
13745 correct; and one or two are genuine bugs that weren't reachable
13746 from the rest of the program. Fixes bug 8793; bugfixes on many,
13750 - Build the torify.1 manpage again. Previously, we were only trying
13751 to build it when also building tor-fw-helper. That's why we didn't
13752 notice that we'd broken the ability to build it. Fixes bug 11321;
13753 bugfix on 0.2.5.1-alpha.
13754 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
13755 11061; bugfix on 0.2.4.7-alpha.
13756 - Correctly document that we search for a system torrc file before
13757 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
13759 - Resolve warnings from Doxygen.
13761 o Code simplifications and refactoring:
13762 - Remove is_internal_IP() function. Resolves ticket 4645.
13763 - Remove unused function circuit_dump_by_chan from circuitlist.c.
13764 Closes issue 9107; patch from "marek".
13765 - Change our use of the ENUM_BF macro to avoid declarations that
13768 o Deprecated versions:
13769 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
13770 attention for some while. Directory authorities no longer accept
13771 descriptors from relays running any version of Tor prior to Tor
13772 0.2.3.16-alpha. Resolves ticket 11149.
13775 - New macros in test.h to simplify writing mock-functions for unit
13776 tests. Part of ticket 11507. Patch from Dana Koch.
13777 - Complete tests for the status.c module. Resolves ticket 11507.
13778 Patch from Dana Koch.
13781 - Remove all code for the long unused v1 directory protocol.
13782 Resolves ticket 11070.
13785 Changes in version 0.2.5.3-alpha - 2014-03-22
13786 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
13787 two new anti-DoS features for Tor relays, resolves a bug that kept
13788 SOCKS5 support for IPv6 from working, fixes several annoying usability
13789 issues for bridge users, and removes more old code for unused
13792 The Tor 0.2.5.x release series is now in patch-freeze: no feature
13793 patches not already written will be considered for inclusion in 0.2.5.x.
13795 o Major features (relay security, DoS-resistance):
13796 - When deciding whether we have run out of memory and we need to
13797 close circuits, also consider memory allocated in buffers for
13798 streams attached to each circuit.
13800 This change, which extends an anti-DoS feature introduced in
13801 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
13802 better resist more memory-based DoS attacks than before. Since the
13803 MaxMemInCellQueues option now applies to all queues, it is renamed
13804 to MaxMemInQueues. This feature fixes bug 10169.
13805 - Avoid hash-flooding denial-of-service attacks by using the secure
13806 SipHash-2-4 hash function for our hashtables. Without this
13807 feature, an attacker could degrade performance of a targeted
13808 client or server by flooding their data structures with a large
13809 number of entries to be stored at the same hash table position,
13810 thereby slowing down the Tor instance. With this feature, hash
13811 table positions are derived from a randomized cryptographic key,
13812 and an attacker cannot predict which entries will collide. Closes
13814 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
13815 the default at 8GBytes), to better support Raspberry Pi users. Fixes
13816 bug 9686; bugfix on 0.2.4.14-alpha.
13818 o Minor features (bridges, pluggable transports):
13819 - Bridges now write the SHA1 digest of their identity key
13820 fingerprint (that is, a hash of a hash of their public key) to
13821 notice-level logs, and to a new hashed-fingerprint file. This
13822 information will help bridge operators look up their bridge in
13823 Globe and similar tools. Resolves ticket 10884.
13824 - Improve the message that Tor displays when running as a bridge
13825 using pluggable transports without an Extended ORPort listener.
13826 Also, log the message in the log file too. Resolves ticket 11043.
13828 o Minor features (other):
13829 - Add a new option, PredictedPortsRelevanceTime, to control how long
13830 after having received a request to connect to a given port Tor
13831 will try to keep circuits ready in anticipation of future requests
13832 for that port. Patch from "unixninja92"; implements ticket 9176.
13833 - Generate a warning if any ports are listed in the SocksPolicy,
13834 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
13835 AuthDirBadExit options. (These options only support address
13836 ranges.) Fixes part of ticket 11108.
13837 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
13840 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
13841 - Build without warnings under clang 3.4. (We have some macros that
13842 define static functions only some of which will get used later in
13843 the module. Starting with clang 3.4, these give a warning unless the
13844 unused attribute is set on them.) Resolves ticket 10904.
13845 - Fix build warnings about missing "a2x" comment when building the
13846 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
13847 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
13849 o Minor bugfixes (client):
13850 - Improve the log message when we can't connect to a hidden service
13851 because all of the hidden service directory nodes hosting its
13852 descriptor are excluded. Improves on our fix for bug 10722, which
13853 was a bugfix on 0.2.0.10-alpha.
13854 - Raise a control port warning when we fail to connect to all of
13855 our bridges. Previously, we didn't inform the controller, and
13856 the bootstrap process would stall. Fixes bug 11069; bugfix on
13858 - Exit immediately when a process-owning controller exits.
13859 Previously, tor relays would wait for a little while after their
13860 controller exited, as if they had gotten an INT signal -- but this
13861 was problematic, since there was no feedback for the user. To do a
13862 clean shutdown, controllers should send an INT signal and give Tor
13863 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
13864 - Stop attempting to connect to bridges before our pluggable
13865 transports are configured (harmless but resulted in some erroneous
13866 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
13867 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
13868 generating incorrect SOCKS5 responses, and confusing client
13869 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
13871 o Minor bugfixes (relays and bridges):
13872 - Avoid crashing on a malformed resolv.conf file when running a
13873 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
13874 - Non-exit relays no longer launch mock DNS requests to check for
13875 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
13876 non-exit relays stopped servicing DNS requests. Fixes bug 965;
13877 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
13878 - Bridges now report complete directory request statistics. Related
13879 to bug 5824; bugfix on 0.2.2.1-alpha.
13880 - Bridges now never collect statistics that were designed for
13881 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
13882 - Stop giving annoying warning messages when we decide not to launch
13883 a pluggable transport proxy that we don't need (because there are
13884 no bridges configured to use it). Resolves ticket 5018; bugfix
13886 - Give the correct URL in the warning message when trying to run a
13887 relay on an ancient version of Windows. Fixes bug 9393.
13889 o Minor bugfixes (backtrace support):
13890 - Support automatic backtraces on more platforms by using the
13891 "-fasynchronous-unwind-tables" compiler option. This option is
13892 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
13893 is on by default and table generation is not. This doesn't yet
13894 add Windows support; only Linux, OSX, and some BSDs are affected.
13895 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
13896 - Avoid strange behavior if two threads hit failed assertions at the
13897 same time and both try to log backtraces at once. (Previously, if
13898 this had happened, both threads would have stored their intermediate
13899 results in the same buffer, and generated junk outputs.) Reported by
13900 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
13901 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
13902 0.2.5.2-alpha; patch from Nick Hopper.
13904 o Minor bugfixes (unit tests):
13905 - Fix a small bug in the unit tests that might have made the tests
13906 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
13907 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
13910 - Remove all remaining code related to version-0 hidden service
13911 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
13912 the rest of bug 10841.
13915 - Document in the manpage that "KBytes" may also be written as
13916 "kilobytes" or "KB", that "Kbits" may also be written as
13917 "kilobits", and so forth. Closes ticket 9222.
13918 - Document that the ClientOnly config option overrides ORPort.
13919 Our old explanation made ClientOnly sound as though it did
13920 nothing at all. Resolves bug 9059.
13921 - Explain that SocksPolicy, DirPolicy, and similar options don't
13922 take port arguments. Fixes the other part of ticket 11108.
13923 - Fix a comment about the rend_server_descriptor_t.protocols field
13924 to more accurately describe its range. Also, make that field
13925 unsigned, to more accurately reflect its usage. Fixes bug 9099;
13926 bugfix on 0.2.1.5-alpha.
13927 - Fix the manpage's description of HiddenServiceAuthorizeClient:
13928 the maximum client name length is 16, not 19. Fixes bug 11118;
13929 bugfix on 0.2.1.6-alpha.
13931 o Code simplifications and refactoring:
13932 - Get rid of router->address, since in all cases it was just the
13933 string representation of router->addr. Resolves ticket 5528.
13935 o Test infrastructure:
13936 - Update to the latest version of tinytest.
13937 - Improve the tinytest implementation of string operation tests so
13938 that comparisons with NULL strings no longer crash the tests; they
13939 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
13942 Changes in version 0.2.4.21 - 2014-02-28
13943 Tor 0.2.4.21 further improves security against potential adversaries who
13944 find breaking 1024-bit crypto doable, and backports several stability
13945 and robustness patches from the 0.2.5 branch.
13947 o Major features (client security):
13948 - When we choose a path for a 3-hop circuit, make sure it contains
13949 at least one relay that supports the NTor circuit extension
13950 handshake. Otherwise, there is a chance that we're building
13951 a circuit that's worth attacking by an adversary who finds
13952 breaking 1024-bit crypto doable, and that chance changes the game
13953 theory. Implements ticket 9777.
13956 - Do not treat streams that fail with reason
13957 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
13958 since it could also indicate an ENETUNREACH connection error. Fixes
13959 part of bug 10777; bugfix on 0.2.4.8-alpha.
13961 o Code simplification and refactoring:
13962 - Remove data structures which were introduced to implement the
13963 CellStatistics option: they are now redundant with the new timestamp
13964 field in the regular packed_cell_t data structure, which we did
13965 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
13968 - Always clear OpenSSL bignums before freeing them -- even bignums
13969 that don't contain secrets. Resolves ticket 10793. Patch by
13971 - Build without warnings under clang 3.4. (We have some macros that
13972 define static functions only some of which will get used later in
13973 the module. Starting with clang 3.4, these give a warning unless the
13974 unused attribute is set on them.) Resolves ticket 10904.
13975 - Update geoip and geoip6 files to the February 7 2014 Maxmind
13976 GeoLite2 Country database.
13979 - Set the listen() backlog limit to the largest actually supported
13980 on the system, not to the value in a header file. Fixes bug 9716;
13981 bugfix on every released Tor.
13982 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
13983 exit node as a NOROUTE error, not an INTERNAL error, since they
13984 can apparently happen when trying to connect to the wrong sort
13985 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
13986 - Fix build warnings about missing "a2x" comment when building the
13987 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
13988 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
13989 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
13990 not entirely remove it from the connection lists. Fixes bug 9602;
13991 bugfix on 0.2.4.4-alpha.
13992 - Fix a segmentation fault in our benchmark code when running with
13993 Fedora's OpenSSL package, or any other OpenSSL that provides
13994 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
13995 - Turn "circuit handshake stats since last time" log messages into a
13996 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
13998 o Documentation fixes:
13999 - Document that all but one DirPort entry must have the NoAdvertise
14000 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
14003 Changes in version 0.2.5.2-alpha - 2014-02-13
14004 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
14005 like the "poor random number generation" fix and the "building too many
14006 circuits" fix. It also further improves security against potential
14007 adversaries who find breaking 1024-bit crypto doable, and launches
14008 pluggable transports on demand (which gets us closer to integrating
14009 pluggable transport support by default -- not to be confused with Tor
14010 bundles enabling pluggable transports and bridges by default).
14012 o Major features (client security):
14013 - When we choose a path for a 3-hop circuit, make sure it contains
14014 at least one relay that supports the NTor circuit extension
14015 handshake. Otherwise, there is a chance that we're building
14016 a circuit that's worth attacking by an adversary who finds
14017 breaking 1024-bit crypto doable, and that chance changes the game
14018 theory. Implements ticket 9777.
14019 - Clients now look at the "usecreatefast" consensus parameter to
14020 decide whether to use CREATE_FAST or CREATE cells for the first hop
14021 of their circuit. This approach can improve security on connections
14022 where Tor's circuit handshake is stronger than the available TLS
14023 connection security levels, but the tradeoff is more computational
14024 load on guard relays. Implements proposal 221. Resolves ticket 9386.
14026 o Major features (bridges):
14027 - Don't launch pluggable transport proxies if we don't have any
14028 bridges configured that would use them. Now we can list many
14029 pluggable transports, and Tor will dynamically start one when it
14030 hears a bridge address that needs it. Resolves ticket 5018.
14031 - The bridge directory authority now assigns status flags (Stable,
14032 Guard, etc) to bridges based on thresholds calculated over all
14033 Running bridges. Now bridgedb can finally make use of its features
14034 to e.g. include at least one Stable bridge in its answers. Fixes
14037 o Major features (other):
14038 - Extend ORCONN controller event to include an "ID" parameter,
14039 and add four new controller event types CONN_BW, CIRC_BW,
14040 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
14041 The new events are emitted in private Tor networks only, with the
14042 goal of being able to better track performance and load during
14043 full-network simulations. Implements proposal 218 and ticket 7359.
14044 - On some platforms (currently: recent OSX versions, glibc-based
14045 platforms that support the ELF format, and a few other
14046 Unix-like operating systems), Tor can now dump stack traces
14047 when a crash occurs or an assertion fails. By default, traces
14048 are dumped to stderr (if possible) and to any logs that are
14049 reporting errors. Implements ticket 9299.
14052 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
14053 not entirely remove it from the connection lists. Fixes bug 9602;
14054 bugfix on 0.2.4.4-alpha.
14055 - Do not treat streams that fail with reason
14056 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
14057 since it could also indicate an ENETUNREACH connection error. Fixes
14058 part of bug 10777; bugfix on 0.2.4.8-alpha.
14060 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
14061 - Do not allow OpenSSL engines to replace the PRNG, even when
14062 HardwareAccel is set. The only default builtin PRNG engine uses
14063 the Intel RDRAND instruction to replace the entire PRNG, and
14064 ignores all attempts to seed it with more entropy. That's
14065 cryptographically stupid: the right response to a new alleged
14066 entropy source is never to discard all previously used entropy
14067 sources. Fixes bug 10402; works around behavior introduced in
14068 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
14070 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
14071 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
14072 - Avoid launching spurious extra circuits when a stream is pending.
14073 This fixes a bug where any circuit that _wasn't_ unusable for new
14074 streams would be treated as if it were, causing extra circuits to
14075 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
14077 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14078 - No longer stop reading or writing on cpuworker connections when
14079 our rate limiting buckets go empty. Now we should handle circuit
14080 handshake requests more promptly. Resolves bug 9731.
14081 - Stop trying to bootstrap all our directory information from
14082 only our first guard. Discovered while fixing bug 9946; bugfix
14085 o Minor features (bridges, pluggable transports):
14086 - Add threshold cutoffs to the networkstatus document created by
14087 the Bridge Authority. Fixes bug 1117.
14088 - On Windows, spawn background processes using the CREATE_NO_WINDOW
14089 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
14090 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
14091 Vidalia set this option for us.) Implements ticket 10297.
14093 o Minor features (security):
14094 - Always clear OpenSSL bignums before freeing them -- even bignums
14095 that don't contain secrets. Resolves ticket 10793. Patch by
14098 o Minor features (config options and command line):
14099 - Add an --allow-missing-torrc commandline option that tells Tor to
14100 run even if the configuration file specified by -f is not available.
14101 Implements ticket 10060.
14102 - Add support for the TPROXY transparent proxying facility on Linux.
14103 See documentation for the new TransProxyType option for more
14104 details. Implementation by "thomo". Closes ticket 10582.
14106 o Minor features (controller):
14107 - Add a new "HS_DESC" controller event that reports activities
14108 related to hidden service descriptors. Resolves ticket 8510.
14109 - New "DROPGUARDS" controller command to forget all current entry
14110 guards. Not recommended for ordinary use, since replacing guards
14111 too frequently makes several attacks easier. Resolves ticket 9934;
14114 o Minor features (build):
14115 - Assume that a user using ./configure --host wants to cross-compile,
14116 and give an error if we cannot find a properly named
14117 tool-chain. Add a --disable-tool-name-check option to proceed
14118 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
14119 - If we run ./configure and the compiler recognizes -fstack-protector
14120 but the linker rejects it, warn the user about a potentially missing
14121 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
14123 o Minor features (testing):
14124 - If Python is installed, "make check" now runs extra tests beyond
14125 the unit test scripts.
14126 - When bootstrapping a test network, sometimes very few relays get
14127 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
14128 specify a set of relays which should be voted Guard regardless of
14129 their uptime or bandwidth. Addresses ticket 9206.
14131 o Minor features (log messages):
14132 - When ServerTransportPlugin is set on a bridge, Tor can write more
14133 useful statistics about bridge use in its extrainfo descriptors,
14134 but only if the Extended ORPort ("ExtORPort") is set too. Add a
14135 log message to inform the user in this case. Resolves ticket 9651.
14136 - When receiving a new controller connection, log the origin address.
14137 Resolves ticket 9698; patch from "sigpipe".
14138 - When logging OpenSSL engine status at startup, log the status of
14139 more engines. Fixes ticket 10043; patch from Joshua Datko.
14140 - Turn "circuit handshake stats since last time" log messages into a
14141 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
14143 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14144 - Improve the circuit queue out-of-memory handler. Previously, when
14145 we ran low on memory, we'd close whichever circuits had the most
14146 queued cells. Now, we close those that have the *oldest* queued
14147 cells, on the theory that those are most responsible for us
14148 running low on memory. Based on analysis from a forthcoming paper
14149 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
14150 - Generate bootstrapping status update events correctly when fetching
14151 microdescriptors. Fixes bug 9927.
14152 - Update to the October 2 2013 Maxmind GeoLite Country database.
14154 o Minor bugfixes (clients):
14155 - When closing a channel that has already been open, do not close
14156 pending circuits that were waiting to connect to the same relay.
14157 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
14160 o Minor bugfixes (relays):
14161 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
14162 exit node as a NOROUTE error, not an INTERNAL error, since they
14163 can apparently happen when trying to connect to the wrong sort
14164 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
14166 o Minor bugfixes (bridges):
14167 - Fix a bug where the first connection works to a bridge that uses a
14168 pluggable transport with client-side parameters, but we don't send
14169 the client-side parameters on subsequent connections. (We don't
14170 use any pluggable transports with client-side parameters yet,
14171 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
14172 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
14174 o Minor bugfixes (node selection):
14175 - If ExcludeNodes is set, consider non-excluded hidden service
14176 directory servers before excluded ones. Do not consider excluded
14177 hidden service directory servers at all if StrictNodes is
14178 set. (Previously, we would sometimes decide to connect to those
14179 servers, and then realize before we initiated a connection that
14180 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
14181 Reported by "mr-4".
14182 - If we set the ExitNodes option but it doesn't include any nodes
14183 that have the Exit flag, we would choose not to bootstrap. Now we
14184 bootstrap so long as ExitNodes includes nodes which can exit to
14185 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
14187 o Minor bugfixes (controller and command-line):
14188 - If changing a config option via "setconf" fails in a recoverable
14189 way, we used to nonetheless write our new control ports to the
14190 file described by the "ControlPortWriteToFile" option. Now we only
14191 write out that file if we successfully switch to the new config
14192 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
14193 - When a command-line option such as --version or --help that
14194 ordinarily implies --hush appears on the command line along with
14195 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
14196 only if it appeared later on the command line. Fixes bug 9578;
14197 bugfix on 0.2.5.1-alpha.
14199 o Minor bugfixes (code correctness):
14200 - Previously we used two temporary files when writing descriptors to
14201 disk; now we only use one. Fixes bug 1376.
14202 - Remove an erroneous (but impossible and thus harmless) pointer
14203 comparison that would have allowed compilers to skip a bounds
14204 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
14205 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
14206 - Fix an always-true assertion in pluggable transports code so it
14207 actually checks what it was trying to check. Fixes bug 10046;
14208 bugfix on 0.2.3.9-alpha. Found by "dcb".
14210 o Minor bugfixes (protocol correctness):
14211 - When receiving a VERSIONS cell with an odd number of bytes, close
14212 the connection immediately since the cell is malformed. Fixes bug
14213 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
14216 o Minor bugfixes (build):
14217 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
14218 turned off (that is, without support for v2 link handshakes). Fixes
14219 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
14220 - Fix compilation warnings and startup issues when running with
14221 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
14223 - Fix compilation on Solaris 9, which didn't like us having an
14224 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
14226 o Minor bugfixes (testing):
14227 - Fix a segmentation fault in our benchmark code when running with
14228 Fedora's OpenSSL package, or any other OpenSSL that provides
14229 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
14231 o Minor bugfixes (log messages):
14232 - Fix a bug where clients using bridges would report themselves
14233 as 50% bootstrapped even without a live consensus document.
14234 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
14235 - Suppress a warning where, if there's only one directory authority
14236 in the network, we would complain that votes and signatures cannot
14237 be uploaded to other directory authorities. Fixes bug 10842;
14238 bugfix on 0.2.2.26-beta.
14239 - Report bootstrapping progress correctly when we're downloading
14240 microdescriptors. We had updated our "do we have enough microdescs
14241 to begin building circuits?" logic most recently in 0.2.4.10-alpha
14242 (see bug 5956), but we left the bootstrap status event logic at
14243 "how far through getting 1/4 of them are we?" Fixes bug 9958;
14244 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
14246 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
14247 - Avoid a crash bug when starting with a corrupted microdescriptor
14248 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
14249 - If we fail to dump a previously cached microdescriptor to disk, avoid
14250 freeing duplicate data later on. Fixes bug 10423; bugfix on
14251 0.2.4.13-alpha. Spotted by "bobnomnom".
14253 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14254 - Correctly log long IPv6 exit policies, instead of truncating them
14255 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
14256 - Our default TLS ecdhe groups were backwards: we meant to be using
14257 P224 for relays (for performance win) and P256 for bridges (since
14258 it is more common in the wild). Instead we had it backwards. After
14259 reconsideration, we decided that the default should be P256 on all
14260 hosts, since its security is probably better, and since P224 is
14261 reportedly used quite little in the wild. Found by "skruffy" on
14262 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
14263 - Free directory authority certificate download statuses on exit
14264 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
14266 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14267 - If the guard we choose first doesn't answer, we would try the
14268 second guard, but once we connected to the second guard we would
14269 abandon it and retry the first one, slowing down bootstrapping.
14270 The fix is to treat all our initially chosen guards as acceptable
14271 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
14272 - Fix an assertion failure that would occur when disabling the
14273 ORPort setting on a running Tor process while accounting was
14274 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
14275 - When examining the list of network interfaces to find our address,
14276 do not consider non-running or disabled network interfaces. Fixes
14277 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
14278 - Avoid an off-by-one error when checking buffer boundaries when
14279 formatting the exit status of a pluggable transport helper.
14280 This is probably not an exploitable bug, but better safe than
14281 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
14284 o Removed code and features:
14285 - Clients now reject any directory authority certificates lacking
14286 a dir-key-crosscert element. These have been included since
14287 0.2.1.9-alpha, so there's no real reason for them to be optional
14288 any longer. Completes proposal 157. Resolves ticket 10162.
14289 - Remove all code that existed to support the v2 directory system,
14290 since there are no longer any v2 directory authorities. Resolves
14292 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
14293 options, which were used for designating authorities as "Hidden
14294 service authorities". There has been no use of hidden service
14295 authorities since 0.2.2.1-alpha, when we stopped uploading or
14296 downloading v0 hidden service descriptors. Fixes bug 10881; also
14297 part of a fix for bug 10841.
14299 o Code simplification and refactoring:
14300 - Remove some old fallback code designed to keep Tor clients working
14301 in a network with only two working relays. Elsewhere in the code we
14302 have long since stopped supporting such networks, so there wasn't
14303 much point in keeping it around. Addresses ticket 9926.
14304 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
14305 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
14306 - Remove data structures which were introduced to implement the
14307 CellStatistics option: they are now redundant with the addition
14308 of a timestamp to the regular packed_cell_t data structure, which
14309 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
14312 o Documentation (man page) fixes:
14313 - Update manpage to describe some of the files you can expect to
14314 find in Tor's DataDirectory. Addresses ticket 9839.
14315 - Document that all but one DirPort entry must have the NoAdvertise
14316 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
14318 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14319 - Clarify the usage and risks of setting the ContactInfo torrc line
14320 for your relay or bridge. Resolves ticket 9854.
14321 - Add anchors to the manpage so we can link to the html version of
14322 the documentation for specific options. Resolves ticket 9866.
14323 - Replace remaining references to DirServer in man page and
14324 log entries. Resolves ticket 10124.
14327 - Make the "tor-gencert" tool used by directory authority operators
14328 create 2048-bit signing keys by default (rather than 1024-bit, since
14329 1024-bit is uncomfortably small these days). Addresses ticket 10324.
14332 Changes in version 0.2.4.20 - 2013-12-22
14333 Tor 0.2.4.20 fixes potentially poor random number generation for users
14334 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
14335 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
14336 and 4) have no state file in their DataDirectory (as would happen on
14337 first start). Users who generated relay or hidden service identity
14338 keys in such a situation should discard them and generate new ones.
14340 This release also fixes a logic error that caused Tor clients to build
14341 many more preemptive circuits than they actually need.
14344 - Do not allow OpenSSL engines to replace the PRNG, even when
14345 HardwareAccel is set. The only default builtin PRNG engine uses
14346 the Intel RDRAND instruction to replace the entire PRNG, and
14347 ignores all attempts to seed it with more entropy. That's
14348 cryptographically stupid: the right response to a new alleged
14349 entropy source is never to discard all previously used entropy
14350 sources. Fixes bug 10402; works around behavior introduced in
14351 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
14353 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
14354 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
14355 - Avoid launching spurious extra circuits when a stream is pending.
14356 This fixes a bug where any circuit that _wasn't_ unusable for new
14357 streams would be treated as if it were, causing extra circuits to
14358 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
14361 - Avoid a crash bug when starting with a corrupted microdescriptor
14362 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
14363 - If we fail to dump a previously cached microdescriptor to disk, avoid
14364 freeing duplicate data later on. Fixes bug 10423; bugfix on
14365 0.2.4.13-alpha. Spotted by "bobnomnom".
14368 Changes in version 0.2.4.19 - 2013-12-11
14369 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
14370 (1986-2013). Aaron worked on diverse projects including helping to guide
14371 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
14372 transparency to the U.S government's PACER documents, and contributing
14373 design and development for Tor and Tor2Web. Aaron was one of the latest
14374 martyrs in our collective fight for civil liberties and human rights,
14375 and his death is all the more painful because he was one of us.
14377 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
14378 a new circuit handshake and link encryption that use ECC to provide
14379 better security and efficiency; makes relays better manage circuit
14380 creation requests; uses "directory guards" to reduce client enumeration
14381 risks; makes bridges collect and report statistics about the pluggable
14382 transports they support; cleans up and improves our geoip database;
14383 gets much closer to IPv6 support for clients, bridges, and relays; makes
14384 directory authorities use measured bandwidths rather than advertised
14385 ones when computing flags and thresholds; disables client-side DNS
14386 caching to reduce tracking risks; and fixes a big bug in bridge
14387 reachability testing. This release introduces two new design
14388 abstractions in the code: a new "channel" abstraction between circuits
14389 and or_connections to allow for implementing alternate relay-to-relay
14390 transports, and a new "circuitmux" abstraction storing the queue of
14391 circuits for a channel. The release also includes many stability,
14392 security, and privacy fixes.
14395 Changes in version 0.2.4.18-rc - 2013-11-16
14396 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
14397 series. It takes a variety of fixes from the 0.2.5.x branch to improve
14398 stability, performance, and better handling of edge cases.
14401 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
14402 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
14403 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
14404 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
14405 them to solve bug 6033.)
14408 - No longer stop reading or writing on cpuworker connections when
14409 our rate limiting buckets go empty. Now we should handle circuit
14410 handshake requests more promptly. Resolves bug 9731.
14411 - If we are unable to save a microdescriptor to the journal, do not
14412 drop it from memory and then reattempt downloading it. Fixes bug
14413 9645; bugfix on 0.2.2.6-alpha.
14414 - Stop trying to bootstrap all our directory information from
14415 only our first guard. Discovered while fixing bug 9946; bugfix
14417 - The new channel code sometimes lost track of in-progress circuits,
14418 causing long-running clients to stop building new circuits. The
14419 fix is to always call circuit_n_chan_done(chan, 0) from
14420 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
14422 o Minor bugfixes (on 0.2.4.x):
14423 - Correctly log long IPv6 exit policies, instead of truncating them
14424 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
14425 - Our default TLS ecdhe groups were backwards: we meant to be using
14426 P224 for relays (for performance win) and P256 for bridges (since
14427 it is more common in the wild). Instead we had it backwards. After
14428 reconsideration, we decided that the default should be P256 on all
14429 hosts, since its security is probably better, and since P224 is
14430 reportedly used quite little in the wild. Found by "skruffy" on
14431 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
14432 - Free directory authority certificate download statuses on exit
14433 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
14435 o Minor bugfixes (on 0.2.3.x and earlier):
14436 - If the guard we choose first doesn't answer, we would try the
14437 second guard, but once we connected to the second guard we would
14438 abandon it and retry the first one, slowing down bootstrapping.
14439 The fix is to treat all our initially chosen guards as acceptable
14440 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
14441 - Fix an assertion failure that would occur when disabling the
14442 ORPort setting on a running Tor process while accounting was
14443 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
14444 - When examining the list of network interfaces to find our address,
14445 do not consider non-running or disabled network interfaces. Fixes
14446 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
14447 - Avoid an off-by-one error when checking buffer boundaries when
14448 formatting the exit status of a pluggable transport helper.
14449 This is probably not an exploitable bug, but better safe than
14450 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
14453 o Minor features (protecting client timestamps):
14454 - Clients no longer send timestamps in their NETINFO cells. These were
14455 not used for anything, and they provided one small way for clients
14456 to be distinguished from each other as they moved from network to
14457 network or behind NAT. Implements part of proposal 222.
14458 - Clients now round timestamps in INTRODUCE cells down to the nearest
14459 10 minutes. If a new Support022HiddenServices option is set to 0, or
14460 if it's set to "auto" and the feature is disabled in the consensus,
14461 the timestamp is sent as 0 instead. Implements part of proposal 222.
14462 - Stop sending timestamps in AUTHENTICATE cells. This is not such
14463 a big deal from a security point of view, but it achieves no actual
14464 good purpose, and isn't needed. Implements part of proposal 222.
14465 - Reduce down accuracy of timestamps in hidden service descriptors.
14466 Implements part of proposal 222.
14468 o Minor features (other):
14469 - Improve the circuit queue out-of-memory handler. Previously, when
14470 we ran low on memory, we'd close whichever circuits had the most
14471 queued cells. Now, we close those that have the *oldest* queued
14472 cells, on the theory that those are most responsible for us
14473 running low on memory. Based on analysis from a forthcoming paper
14474 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
14475 - Generate bootstrapping status update events correctly when fetching
14476 microdescriptors. Fixes bug 9927.
14477 - Update to the October 2 2013 Maxmind GeoLite Country database.
14479 o Documentation fixes:
14480 - Clarify the usage and risks of setting the ContactInfo torrc line
14481 for your relay or bridge. Resolves ticket 9854.
14482 - Add anchors to the manpage so we can link to the html version of
14483 the documentation for specific options. Resolves ticket 9866.
14484 - Replace remaining references to DirServer in man page and
14485 log entries. Resolves ticket 10124.
14488 Changes in version 0.2.5.1-alpha - 2013-10-02
14489 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
14490 on Linux, allows bridges that offer pluggable transports to report usage
14491 statistics, fixes many issues to make testing easier, and provides
14492 a pile of minor features and bugfixes that have been waiting for a
14493 release of the new branch.
14495 This is the first alpha release in a new series, so expect there to
14496 be bugs. Users who would rather test out a more stable branch should
14497 stay with 0.2.4.x for now.
14499 o Major features (security):
14500 - Use the seccomp2 syscall filtering facility on Linux to limit
14501 which system calls Tor can invoke. This is an experimental,
14502 Linux-only feature to provide defense-in-depth against unknown
14503 attacks. To try turning it on, set "Sandbox 1" in your torrc
14504 file. Please be ready to report bugs. We hope to add support
14505 for better sandboxing in the future, including more fine-grained
14506 filters, better division of responsibility, and support for more
14507 platforms. This work has been done by Cristian-Matei Toader for
14508 Google Summer of Code.
14509 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
14510 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
14511 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
14512 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
14513 them to solve bug 6033.)
14515 o Major features (other):
14516 - Add support for passing arguments to managed pluggable transport
14517 proxies. Implements ticket 3594.
14518 - Bridges now track GeoIP information and the number of their users
14519 even when pluggable transports are in use, and report usage
14520 statistics in their extra-info descriptors. Resolves tickets 4773
14522 - Make testing Tor networks bootstrap better: lower directory fetch
14523 retry schedules and maximum interval without directory requests,
14524 and raise maximum download tries. Implements ticket 6752.
14525 - Add make target 'test-network' to run tests on a Chutney network.
14526 Implements ticket 8530.
14527 - The ntor handshake is now on-by-default, no matter what the
14528 directory authorities recommend. Implements ticket 8561.
14531 - Instead of writing destroy cells directly to outgoing connection
14532 buffers, queue them and intersperse them with other outgoing cells.
14533 This can prevent a set of resource starvation conditions where too
14534 many pending destroy cells prevent data cells from actually getting
14535 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
14536 bugfix on 0.2.0.1-alpha.
14537 - If we are unable to save a microdescriptor to the journal, do not
14538 drop it from memory and then reattempt downloading it. Fixes bug
14539 9645; bugfix on 0.2.2.6-alpha.
14540 - The new channel code sometimes lost track of in-progress circuits,
14541 causing long-running clients to stop building new circuits. The
14542 fix is to always call circuit_n_chan_done(chan, 0) from
14543 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
14546 - Tor now builds each source file in two modes: a mode that avoids
14547 exposing identifiers needlessly, and another mode that exposes
14548 more identifiers for testing. This lets the compiler do better at
14549 optimizing the production code, while enabling us to take more
14550 radical measures to let the unit tests test things.
14551 - The production builds no longer include functions used only in
14552 the unit tests; all functions exposed from a module only for
14553 unit-testing are now static in production builds.
14554 - Add an --enable-coverage configuration option to make the unit
14555 tests (and a new src/or/tor-cov target) to build with gcov test
14559 - We now have rudimentary function mocking support that our unit
14560 tests can use to test functions in isolation. Function mocking
14561 lets the tests temporarily replace a function's dependencies with
14562 stub functions, so that the tests can check the function without
14563 invoking the other functions it calls.
14564 - Add more unit tests for the <circid,channel>->circuit map, and
14565 the destroy-cell-tracking code to fix bug 7912.
14566 - Unit tests for failing cases of the TAP onion handshake.
14567 - More unit tests for address-manipulation functions.
14569 o Minor features (protecting client timestamps):
14570 - Clients no longer send timestamps in their NETINFO cells. These were
14571 not used for anything, and they provided one small way for clients
14572 to be distinguished from each other as they moved from network to
14573 network or behind NAT. Implements part of proposal 222.
14574 - Clients now round timestamps in INTRODUCE cells down to the nearest
14575 10 minutes. If a new Support022HiddenServices option is set to 0, or
14576 if it's set to "auto" and the feature is disabled in the consensus,
14577 the timestamp is sent as 0 instead. Implements part of proposal 222.
14578 - Stop sending timestamps in AUTHENTICATE cells. This is not such
14579 a big deal from a security point of view, but it achieves no actual
14580 good purpose, and isn't needed. Implements part of proposal 222.
14581 - Reduce down accuracy of timestamps in hidden service descriptors.
14582 Implements part of proposal 222.
14584 o Minor features (config options):
14585 - Config (torrc) lines now handle fingerprints which are missing
14586 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
14587 - Support a --dump-config option to print some or all of the
14588 configured options. Mainly useful for debugging the command-line
14589 option parsing code. Helps resolve ticket 4647.
14590 - Raise awareness of safer logging: notify user of potentially
14591 unsafe config options, like logging more verbosely than severity
14592 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
14593 - Add a new configuration option TestingV3AuthVotingStartOffset
14594 that bootstraps a network faster by changing the timing for
14595 consensus votes. Addresses ticket 8532.
14596 - Add a new torrc option "ServerTransportOptions" that allows
14597 bridge operators to pass configuration parameters to their
14598 pluggable transports. Resolves ticket 8929.
14599 - The config (torrc) file now accepts bandwidth and space limits in
14600 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
14601 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
14604 o Minor features (build):
14605 - Add support for `--library-versions` flag. Implements ticket 6384.
14606 - Return the "unexpected sendme" warnings to a warn severity, but make
14607 them rate limited, to help diagnose ticket 8093.
14608 - Detect a missing asciidoc, and warn the user about it, during
14609 configure rather than at build time. Fixes issue 6506. Patch from
14612 o Minor features (other):
14613 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
14614 sockets in a single system call. Implements ticket 5129.
14615 - Log current accounting state (bytes sent and received + remaining
14616 time for the current accounting period) in the relay's heartbeat
14617 message. Implements ticket 5526; patch from Peter Retzlaff.
14618 - Implement the TRANSPORT_LAUNCHED control port event that
14619 notifies controllers about new launched pluggable
14620 transports. Resolves ticket 5609.
14621 - If we're using the pure-C 32-bit curve25519_donna implementation
14622 of curve25519, build it with the -fomit-frame-pointer option to
14623 make it go faster on register-starved hosts. This improves our
14624 handshake performance by about 6% on i386 hosts without nacl.
14625 Closes ticket 8109.
14626 - Update to the September 4 2013 Maxmind GeoLite Country database.
14629 - Set the listen() backlog limit to the largest actually supported
14630 on the system, not to the value in a header file. Fixes bug 9716;
14631 bugfix on every released Tor.
14632 - No longer accept malformed http headers when parsing urls from
14633 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
14634 bugfix on 0.0.6pre1.
14635 - In munge_extrainfo_into_routerinfo(), check the return value of
14636 memchr(). This would have been a serious issue if we ever passed
14637 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
14639 - On the chance that somebody manages to build Tor on a
14640 platform where time_t is unsigned, correct the way that
14641 microdesc_add_to_cache() handles negative time arguments.
14642 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
14643 - Reject relative control socket paths and emit a warning. Previously,
14644 single-component control socket paths would be rejected, but Tor
14645 would not log why it could not validate the config. Fixes bug 9258;
14646 bugfix on 0.2.3.16-alpha.
14648 o Minor bugfixes (command line):
14649 - Use a single command-line parser for parsing torrc options on the
14650 command line and for finding special command-line options to avoid
14651 inconsistent behavior for torrc option arguments that have the same
14652 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
14654 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
14655 9573; bugfix on 0.0.9pre5.
14657 o Minor fixes (build, auxiliary programs):
14658 - Stop preprocessing the "torify" script with autoconf, since
14659 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
14661 - The tor-fw-helper program now follows the standard convention and
14662 exits with status code "0" on success. Fixes bug 9030; bugfix on
14663 0.2.3.1-alpha. Patch by Arlo Breault.
14664 - Corrected ./configure advice for what openssl dev package you should
14665 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
14667 o Minor code improvements:
14668 - Remove constants and tests for PKCS1 padding; it's insecure and
14669 shouldn't be used for anything new. Fixes bug 8792; patch
14671 - Remove instances of strcpy() from the unit tests. They weren't
14672 hurting anything, since they were only in the unit tests, but it's
14673 embarrassing to have strcpy() in the code at all, and some analysis
14674 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
14675 0.2.3.8-alpha. Patch from Arlo Breault.
14677 o Removed features:
14678 - Remove migration code from when we renamed the "cached-routers"
14679 file to "cached-descriptors" back in 0.2.0.8-alpha. This
14680 incidentally resolves ticket 6502 by cleaning up the related code
14681 a bit. Patch from Akshay Hebbar.
14683 o Code simplification and refactoring:
14684 - Extract the common duplicated code for creating a subdirectory
14685 of the data directory and writing to a file in it. Fixes ticket
14686 4282; patch from Peter Retzlaff.
14687 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
14688 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
14689 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
14690 - Add a set of accessor functions for the circuit timeout data
14691 structure. Fixes ticket 6153; patch from "piet".
14692 - Clean up exit paths from connection_listener_new(). Closes ticket
14693 8789. Patch from Arlo Breault.
14694 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
14695 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
14696 - Use a doubly-linked list to implement the global circuit list.
14697 Resolves ticket 9108. Patch from Marek Majkowski.
14698 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
14701 Changes in version 0.2.4.17-rc - 2013-09-05
14702 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
14703 series. It adds an emergency step to help us tolerate the massive
14704 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
14705 circuit-level handshakes now effectively jump the queue compared to
14706 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
14707 big bug hindering bridge reachability tests.
14710 - Relays now process the new "NTor" circuit-level handshake requests
14711 with higher priority than the old "TAP" circuit-level handshake
14712 requests. We still process some TAP requests to not totally starve
14713 0.2.3 clients when NTor becomes popular. A new consensus parameter
14714 "NumNTorsPerTAP" lets us tune the balance later if we need to.
14715 Implements ticket 9574.
14718 - If the circuit build timeout logic is disabled (via the consensus,
14719 or because we are an authority), then don't build testing circuits.
14720 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
14721 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
14722 previously they did not, which prevented them from receiving
14723 successful connections from relays for self-test or bandwidth
14724 testing. Also, when a relay is extending a circuit to a bridge,
14725 it needs to send a NETINFO cell, even when the bridge hasn't sent
14726 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
14727 - If the time to download the next old-style networkstatus is in
14728 the future, do not decline to consider whether to download the
14729 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
14733 - Avoid double-closing the listener socket in our socketpair()
14734 replacement (used on Windows) in the case where the addresses on
14735 our opened sockets don't match what we expected. Fixes bug 9400;
14736 bugfix on 0.0.2pre7. Found by Coverity.
14738 o Minor fixes (config options):
14739 - Avoid overflows when the user sets MaxCircuitDirtiness to a
14740 ridiculously high value, by imposing a (ridiculously high) 30-day
14741 maximum on MaxCircuitDirtiness.
14742 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
14743 message is logged at notice, not at info.
14744 - Warn and fail if a server is configured not to advertise any
14745 ORPorts at all. (We need *something* to put in our descriptor,
14746 or we just won't work.)
14749 - Track how many "TAP" and "NTor" circuit handshake requests we get,
14750 and how many we complete, and log it every hour to help relay
14751 operators follow trends in network load. Addresses ticket 9658.
14752 - Update to the August 7 2013 Maxmind GeoLite Country database.
14755 Changes in version 0.2.4.16-rc - 2013-08-10
14756 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
14757 series. It fixes several crash bugs in the 0.2.4 branch.
14760 - Fix a bug in the voting algorithm that could yield incorrect results
14761 when a non-naming authority declared too many flags. Fixes bug 9200;
14762 bugfix on 0.2.0.3-alpha.
14763 - Fix an uninitialized read that could in some cases lead to a remote
14764 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
14765 Anybody running a hidden service on the experimental 0.2.4.x
14766 branch should upgrade. (This is, so far as we know, unrelated to
14768 - Avoid an assertion failure when processing DNS replies without the
14769 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
14770 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
14771 0.2.4.15-rc. Found by stem integration tests.
14774 - Fix an invalid memory read that occurred when a pluggable
14775 transport proxy failed its configuration protocol.
14776 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
14777 - When evaluating whether to use a connection that we haven't
14778 decided is canonical using a recent link protocol version,
14779 decide that it's canonical only if it used address _does_
14780 match the desired address. Fixes bug 9309; bugfix on
14781 0.2.4.4-alpha. Reported by skruffy.
14782 - Make the default behavior of NumDirectoryGuards be to track
14783 NumEntryGuards. Now a user who changes only NumEntryGuards will get
14784 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
14785 - Fix a spurious compilation warning with some older versions of
14786 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
14789 - Update to the July 3 2013 Maxmind GeoLite Country database.
14792 Changes in version 0.2.4.15-rc - 2013-07-01
14793 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
14794 series. It fixes a few smaller bugs, but generally appears stable.
14795 Please test it and let us know whether it is!
14798 - When receiving a new configuration file via the control port's
14799 LOADCONF command, do not treat the defaults file as absent.
14800 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
14803 - Issue a warning when running with the bufferevents backend enabled.
14804 It's still not stable, and people should know that they're likely
14805 to hit unexpected problems. Closes ticket 9147.
14808 Changes in version 0.2.4.14-alpha - 2013-06-18
14809 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
14810 present in 0.2.4.13-alpha.
14813 - When we have too much memory queued in circuits (according to a new
14814 MaxMemInCellQueues option), close the circuits consuming the most
14815 memory. This prevents us from running out of memory as a relay if
14816 circuits fill up faster than they can be drained. Fixes bug 9063;
14817 bugfix on the 54th commit of Tor. This bug is a further fix beyond
14818 bug 6252, whose fix was merged into 0.2.3.21-rc.
14820 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
14821 where we tried to solve this issue simply by imposing an upper limit
14822 on the number of queued cells for a single circuit. That approach
14823 proved to be problematic, since there are ways to provoke clients to
14824 send a number of cells in excess of any such reasonable limit. Fixes
14825 bug 9072; bugfix on 0.2.4.13-alpha.
14827 - Limit hidden service descriptors to at most ten introduction
14828 points, to slow one kind of guard enumeration. Fixes bug 9002;
14829 bugfix on 0.1.1.11-alpha.
14832 Changes in version 0.2.4.13-alpha - 2013-06-14
14833 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
14834 vulnerabilities, makes socks5 username/password circuit isolation
14835 actually actually work (this time for sure!), and cleans up a bunch
14836 of other issues in preparation for a release candidate.
14838 o Major bugfixes (robustness):
14839 - Close any circuit that has too many cells queued on it. Fixes
14840 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
14841 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
14842 - Prevent the get_freelists() function from running off the end of
14843 the list of freelists if it somehow gets an unrecognized
14844 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
14846 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
14847 when an exit connection with optimistic data succeeds immediately
14848 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
14850 - Fix a directory authority crash bug when building a consensus
14851 using an older consensus as its basis. Fixes bug 8833. Bugfix
14855 - Avoid a memory leak where we would leak a consensus body when we
14856 find that a consensus which we couldn't previously verify due to
14857 missing certificates is now verifiable. Fixes bug 8719; bugfix
14859 - We used to always request authority certificates by identity digest,
14860 meaning we'd get the newest one even when we wanted one with a
14861 different signing key. Then we would complain about being given
14862 a certificate we already had, and never get the one we really
14863 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
14864 resource to request the one we want. Fixes bug 5595; bugfix on
14866 - Follow the socks5 protocol when offering username/password
14867 authentication. The fix for bug 8117 exposed this bug, and it
14868 turns out real-world applications like Pidgin do care. Bugfix on
14869 0.2.3.2-alpha; fixes bug 8879.
14870 - Prevent failures on Windows Vista and later when rebuilding the
14871 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
14872 bugfix on 0.2.4.12-alpha.
14875 - Fix an impossible buffer overrun in the AES unit tests. Fixes
14876 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
14877 - If for some reason we fail to write a microdescriptor while
14878 rebuilding the cache, do not let the annotations from that
14879 microdescriptor linger in the cache file, and do not let the
14880 microdescriptor stay recorded as present in its old location.
14881 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
14882 - Fix a memory leak that would occur whenever a configuration
14883 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
14884 - Paste the description for PathBias parameters from the man
14885 page into or.h, so the code documents them too. Fixes bug 7982;
14886 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
14887 - Relays now treat a changed IPv6 ORPort as sufficient reason to
14888 publish an updated descriptor. Fixes bug 6026; bugfix on
14890 - When launching a resolve request on behalf of an AF_UNIX control
14891 socket, omit the address field of the new entry connection, used in
14892 subsequent controller events, rather than letting tor_dup_addr()
14893 set it to "<unknown address type>". Fixes bug 8639; bugfix on
14896 o Minor bugfixes (log messages):
14897 - Fix a scaling issue in the path bias accounting code that
14898 resulted in "Bug:" log messages from either
14899 pathbias_scale_close_rates() or pathbias_count_build_success().
14900 This represents a bugfix on a previous bugfix: the original fix
14901 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
14903 - Give a less useless error message when the user asks for an IPv4
14904 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
14908 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
14909 to tolerate bug 8093 for now.
14910 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
14911 in directory authority votes to describe whether they have enough
14912 measured bandwidths to ignore advertised (relay descriptor)
14913 bandwidth claims. Resolves ticket 8711.
14914 - Update to the June 5 2013 Maxmind GeoLite Country database.
14916 o Removed documentation:
14917 - Remove some of the older contents of doc/ as obsolete; move others
14918 to torspec.git. Fixes bug 8965.
14920 o Code simplification and refactoring:
14921 - Avoid using character buffers when constructing most directory
14922 objects: this approach was unwieldy and error-prone. Instead,
14923 build smartlists of strings, and concatenate them when done.
14926 Changes in version 0.2.4.12-alpha - 2013-04-18
14927 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
14928 process for lengthening the guard rotation period, makes directory
14929 authority opinions in the consensus a bit less gameable, makes socks5
14930 username/password circuit isolation actually work, and fixes a wide
14931 variety of other issues.
14934 - Raise the default time that a client keeps an entry guard from
14935 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
14936 2012 paper. (We would make it even longer, but we need better client
14937 load balancing first.) Also, make the guard lifetime controllable
14938 via a new GuardLifetime torrc option and a GuardLifetime consensus
14939 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
14940 - Directory authorities now prefer using measured bandwidths to
14941 advertised ones when computing flags and thresholds. Resolves
14943 - Directory authorities that have more than a threshold number
14944 of relays with measured bandwidths now treat relays with unmeasured
14945 bandwidths as having bandwidth 0. Resolves ticket 8435.
14947 o Major bugfixes (assert / resource use):
14948 - Avoid a bug where our response to TLS renegotiation under certain
14949 network conditions could lead to a busy-loop, with 100% CPU
14950 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
14951 - Avoid an assertion when we discover that we'd like to write a cell
14952 onto a closing connection: just discard the cell. Fixes another
14953 case of bug 7350; bugfix on 0.2.4.4-alpha.
14955 o Major bugfixes (client-side privacy):
14956 - When we mark a circuit as unusable for new circuits, have it
14957 continue to be unusable for new circuits even if MaxCircuitDirtiness
14958 is increased too much at the wrong time, or the system clock jumps
14959 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
14960 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
14961 which have resolved to internal addresses") is set, apply that
14962 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
14963 - When an exit relay rejects a stream with reason "exit policy", but
14964 we only know an exit policy summary (e.g. from the microdesc
14965 consensus) for it, do not mark the relay as useless for all exiting.
14966 Instead, mark just the circuit as unsuitable for that particular
14967 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
14968 - Allow applications to get proper stream isolation with
14969 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
14970 username/password authentication also offer "no authentication". Tor
14971 had previously preferred "no authentication", so the applications
14972 never actually sent Tor their auth details. Now Tor selects
14973 username/password authentication if it's offered. You can disable
14974 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
14975 bug 8117; bugfix on 0.2.3.3-alpha.
14977 o Major bugfixes (other):
14978 - When unable to find any working directory nodes to use as a
14979 directory guard, give up rather than adding the same non-working
14980 nodes to the directory guard list over and over. Fixes bug 8231;
14981 bugfix on 0.2.4.8-alpha.
14984 - Reject as invalid most directory objects containing a NUL.
14985 Belt-and-suspender fix for bug 8037.
14986 - In our testsuite, create temporary directories with a bit more
14987 entropy in their name to make name collisions less likely. Fixes
14989 - Add CACHED keyword to ADDRMAP events in the control protocol
14990 to indicate whether a DNS result will be cached or not. Resolves
14992 - Update to the April 3 2013 Maxmind GeoLite Country database.
14994 o Minor features (build):
14995 - Detect and reject attempts to build Tor with threading support
14996 when OpenSSL has been compiled without threading support.
14998 - Clarify that when autoconf is checking for nacl, it is checking
14999 specifically for nacl with a fast curve25519 implementation.
15001 - Warn if building on a platform with an unsigned time_t: there
15002 are too many places where Tor currently assumes that time_t can
15003 hold negative values. We'd like to fix them all, but probably
15006 o Minor bugfixes (build):
15007 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
15008 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
15009 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
15010 - Add the old src/or/micro-revision.i filename to CLEANFILES.
15011 On the off chance that somebody has one, it will go away as soon
15012 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
15013 - Build Tor correctly on 32-bit platforms where the compiler can build
15014 but not run code using the "uint128_t" construction. Fixes bug 8587;
15015 bugfix on 0.2.4.8-alpha.
15016 - Fix compilation warning with some versions of clang that would
15017 prefer the -Wswitch-enum compiler flag to warn about switch
15018 statements with missing enum values, even if those switch
15019 statements have a "default:" statement. Fixes bug 8598; bugfix
15022 o Minor bugfixes (protocol):
15023 - Fix the handling of a TRUNCATE cell when it arrives while the
15024 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
15025 - Fix a misframing issue when reading the version numbers in a
15026 VERSIONS cell. Previously we would recognize [00 01 00 02] as
15027 'version 1, version 2, and version 0x100', when it should have
15028 only included versions 1 and 2. Fixes bug 8059; bugfix on
15029 0.2.0.10-alpha. Reported pseudonymously.
15030 - Make the format and order of STREAM events for DNS lookups
15031 consistent among the various ways to launch DNS lookups. Fixes
15032 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
15033 - Correct our check for which versions of Tor support the EXTEND2
15034 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
15035 later, when support was really added in version 0.2.4.8-alpha.
15036 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
15038 o Minor bugfixes (other):
15039 - Correctly store microdescriptors and extrainfo descriptors with
15040 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
15041 Bug reported by "cypherpunks".
15042 - Increase the width of the field used to remember a connection's
15043 link protocol version to two bytes. Harmless for now, since the
15044 only currently recognized versions are one byte long. Reported
15045 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
15046 - If the state file's path bias counts are invalid (presumably from a
15047 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
15048 additional checks and log messages to the scaling of Path Bias
15049 counts, in case there still are remaining issues with scaling.
15050 Should help resolve bug 8235.
15051 - Eliminate several instances where we use "Nickname=ID" to refer to
15052 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
15053 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
15054 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
15056 o Minor bugfixes (syscalls):
15057 - Always check the return values of functions fcntl() and
15058 setsockopt(). We don't believe these are ever actually failing in
15059 practice, but better safe than sorry. Also, checking these return
15060 values should please analysis tools like Coverity. Patch from
15061 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
15062 - Use direct writes rather than stdio when building microdescriptor
15063 caches, in an attempt to mitigate bug 8031, or at least make it
15066 o Minor bugfixes (config):
15067 - When rejecting a configuration because we were unable to parse a
15068 quoted string, log an actual error message. Fixes bug 7950; bugfix
15070 - Behave correctly when the user disables LearnCircuitBuildTimeout
15071 but doesn't tell us what they would like the timeout to be. Fixes
15072 bug 6304; bugfix on 0.2.2.14-alpha.
15073 - When autodetecting the number of CPUs, use the number of available
15074 CPUs in preference to the number of configured CPUs. Inform the
15075 user if this reduces the number of available CPUs. Fixes bug 8002;
15076 bugfix on 0.2.3.1-alpha.
15077 - Make it an error when you set EntryNodes but disable UseGuardNodes,
15078 since it will (surprisingly to some users) ignore EntryNodes. Fixes
15079 bug 8180; bugfix on 0.2.3.11-alpha.
15080 - Allow TestingTorNetworks to override the 4096-byte minimum for
15081 the Fast threshold. Otherwise they can't bootstrap until they've
15082 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
15083 - Fix some logic errors when the user manually overrides the
15084 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
15087 o Minor bugfixes (log messages to help diagnose bugs):
15088 - If we fail to free a microdescriptor because of bug 7164, log
15089 the filename and line number from which we tried to free it.
15090 - Add another diagnostic to the heartbeat message: track and log
15091 overhead that TLS is adding to the data we write. If this is
15092 high, we are sending too little data to SSL_write at a time.
15093 Diagnostic for bug 7707.
15094 - Add more detail to a log message about relaxed timeouts, to help
15096 - Warn more aggressively when flushing microdescriptors to a
15097 microdescriptor cache fails, in an attempt to mitigate bug 8031,
15098 or at least make it more diagnosable.
15099 - Improve debugging output to help track down bug 8185 ("Bug:
15100 outgoing relay cell has n_chan==NULL. Dropping.")
15101 - Log the purpose of a path-bias testing circuit correctly.
15102 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
15104 o Minor bugfixes (0.2.4.x log messages that were too noisy):
15105 - Don't attempt to relax the timeout of already opened 1-hop circuits.
15106 They might never timeout. This should eliminate some/all cases of
15107 the relaxed timeout log message.
15108 - Use circuit creation time for network liveness evaluation. This
15109 should eliminate warning log messages about liveness caused
15110 by changes in timeout evaluation. Fixes bug 6572; bugfix on
15112 - Reduce a path bias length check from notice to info. The message
15113 is triggered when creating controller circuits. Fixes bug 8196;
15114 bugfix on 0.2.4.8-alpha.
15115 - Fix a path state issue that triggered a notice during relay startup.
15116 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
15117 - Reduce occurrences of warns about circuit purpose in
15118 connection_ap_expire_building(). Fixes bug 8477; bugfix on
15121 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
15122 - If we encounter a write failure on a SOCKS connection before we
15123 finish our SOCKS handshake, don't warn that we closed the
15124 connection before we could send a SOCKS reply. Fixes bug 8427;
15125 bugfix on 0.1.0.1-rc.
15126 - Correctly recognize that [::1] is a loopback address. Fixes
15127 bug 8377; bugfix on 0.2.1.3-alpha.
15128 - Fix a directory authority warn caused when we have a large amount
15129 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
15130 - Don't log inappropriate heartbeat messages when hibernating: a
15131 hibernating node is _expected_ to drop out of the consensus,
15132 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
15133 bugfix on 0.2.3.1-alpha.
15134 - Don't complain about bootstrapping problems while hibernating.
15135 These complaints reflect a general code problem, but not one
15136 with any problematic effects (no connections are actually
15137 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
15139 o Documentation fixes:
15140 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
15141 names match. Fixes bug 7768.
15142 - Make the torify manpage no longer refer to tsocks; torify hasn't
15143 supported tsocks since 0.2.3.14-alpha.
15144 - Make the tor manpage no longer reference tsocks.
15145 - Fix the GeoIPExcludeUnknown documentation to refer to
15146 ExcludeExitNodes rather than the currently nonexistent
15147 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
15150 - The tor-tsocks.conf is no longer distributed or installed. We
15151 recommend that tsocks users use torsocks instead. Resolves
15155 Changes in version 0.2.4.11-alpha - 2013-03-11
15156 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
15157 more robust, makes hidden service authentication work again, and
15158 resolves a DPI fingerprint for Tor's SSL transport.
15160 o Major features (directory authorities):
15161 - Directory authorities now support a new consensus method (17)
15162 where they cap the published bandwidth of servers for which
15163 insufficient bandwidth measurements exist. Fixes part of bug 2286.
15164 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
15165 serve any v2 directory information. Now we can test disabling the
15166 old deprecated v2 directory format, and see whether doing so has
15167 any effect on network load. Begins to fix bug 6783.
15168 - Directory authorities now include inside each vote a statement of
15169 the performance thresholds they used when assigning flags.
15170 Implements ticket 8151.
15172 o Major bugfixes (directory authorities):
15173 - Stop marking every relay as having been down for one hour every
15174 time we restart a directory authority. These artificial downtimes
15175 were messing with our Stable and Guard flag calculations. Fixes
15176 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
15178 o Major bugfixes (hidden services):
15179 - Allow hidden service authentication to succeed again. When we
15180 refactored the hidden service introduction code back
15181 in 0.2.4.1-alpha, we didn't update the code that checks
15182 whether authentication information is present, causing all
15183 authentication checks to return "false". Fix for bug 8207; bugfix
15184 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
15186 o Minor features (relays, bridges):
15187 - Make bridge relays check once a minute for whether their IP
15188 address has changed, rather than only every 15 minutes. Resolves
15189 bugs 1913 and 1992.
15190 - Refactor resolve_my_address() so it returns the method by which we
15191 decided our public IP address (explicitly configured, resolved from
15192 explicit hostname, guessed from interfaces, learned by gethostname).
15193 Now we can provide more helpful log messages when a relay guesses
15194 its IP address incorrectly (e.g. due to unexpected lines in
15195 /etc/hosts). Resolves ticket 2267.
15196 - Teach bridge-using clients to avoid 0.2.2 bridges when making
15197 microdescriptor-related dir requests, and only fall back to normal
15198 descriptors if none of their bridges can handle microdescriptors
15199 (as opposed to the fix in ticket 4013, which caused them to fall
15200 back to normal descriptors if *any* of their bridges preferred
15201 them). Resolves ticket 4994.
15202 - Randomize the lifetime of our SSL link certificate, so censors can't
15203 use the static value for filtering Tor flows. Resolves ticket 8443;
15204 related to ticket 4014 which was included in 0.2.2.33.
15205 - Support a new version of the link protocol that allows 4-byte circuit
15206 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
15207 a possible resource exhaustion issue. Closes ticket 7351; implements
15210 o Minor features (portability):
15211 - Tweak the curve25519-donna*.c implementations to tolerate systems
15212 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
15213 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
15214 the signs of types during autoconf. This is better than our old
15215 approach, which didn't work when cross-compiling.
15216 - Detect the sign of enum values, rather than assuming that MSC is the
15217 only compiler where enum types are all signed. Fixes bug 7727;
15218 bugfix on 0.2.4.10-alpha.
15220 o Minor features (other):
15221 - Say "KBytes" rather than "KB" in the man page (for various values
15222 of K), to further reduce confusion about whether Tor counts in
15223 units of memory or fractions of units of memory. Resolves ticket 7054.
15224 - Clear the high bit on curve25519 public keys before passing them to
15225 our backend, in case we ever wind up using a backend that doesn't do
15226 so itself. If we used such a backend, and *didn't* clear the high bit,
15227 we could wind up in a situation where users with such backends would
15228 be distinguishable from users without. Fixes bug 8121; bugfix on
15230 - Update to the March 6 2013 Maxmind GeoLite Country database.
15232 o Minor bugfixes (clients):
15233 - When we receive a RELAY_END cell with the reason DONE, or with no
15234 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
15235 status as "connection refused". Previously we reported these cases
15236 as success but then immediately closed the connection. Fixes bug
15237 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
15238 - Downgrade an assertion in connection_ap_expire_beginning to an
15239 LD_BUG message. The fix for bug 8024 should prevent this message
15240 from displaying, but just in case, a warn that we can diagnose
15241 is better than more assert crashes. Fixes bug 8065; bugfix on
15243 - Lower path use bias thresholds to .80 for notice and .60 for warn.
15244 Also make the rate limiting flags for the path use bias log messages
15245 independent from the original path bias flags. Fixes bug 8161;
15246 bugfix on 0.2.4.10-alpha.
15248 o Minor bugfixes (relays):
15249 - Stop trying to resolve our hostname so often (e.g. every time we
15250 think about doing a directory fetch). Now we reuse the cached
15251 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
15252 and 2410 (bugfix on 0.1.2.2-alpha).
15253 - Stop sending a stray "(null)" in some cases for the server status
15254 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
15256 - When choosing which stream on a formerly stalled circuit to wake
15257 first, make better use of the platform's weak RNG. Previously,
15258 we had been using the % ("modulo") operator to try to generate a
15259 1/N chance of picking each stream, but this behaves badly with
15260 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
15262 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
15263 Irix's random() only return 15 bits; Solaris's random() returns more
15264 bits but its RAND_MAX says it only returns 15, and so on. Motivated
15265 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
15267 o Minor bugfixes (directory authorities):
15268 - Directory authorities now use less space when formatting identical
15269 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
15272 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
15273 - Avoid leaking memory if we fail to compute a consensus signature
15274 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
15275 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
15277 - Fix a memory leak during safe-cookie controller authentication.
15278 Bugfix on 0.2.3.13-alpha.
15279 - Avoid memory leak of IPv6 policy content if we fail to format it into
15280 a router descriptor. Bugfix on 0.2.4.7-alpha.
15282 o Minor bugfixes (other code correctness issues):
15283 - Avoid a crash if we fail to generate an extrainfo descriptor.
15284 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
15285 this is CID 718634.
15286 - When detecting the largest possible file descriptor (in order to
15287 close all file descriptors when launching a new program), actually
15288 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
15289 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
15291 - Fix a copy-and-paste error when adding a missing A1 to a routerset
15292 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
15293 Bugfix on 0.2.4.10-alpha.
15294 - Fix an impossible-to-trigger integer overflow when estimating how
15295 long our onionskin queue would take. (This overflow would require us
15296 to accept 4 million onionskins before processing 100 of them.) Fixes
15297 bug 8210; bugfix on 0.2.4.10-alpha.
15299 o Code simplification and refactoring:
15300 - Add a wrapper function for the common "log a message with a
15304 Changes in version 0.2.4.10-alpha - 2013-02-04
15305 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
15306 certain attacks that flood the network with relays; changes the queue
15307 for circuit create requests from a sized-based limit to a time-based
15308 limit; resumes building with MSVC on Windows; and fixes a wide variety
15311 o Major bugfixes (directory authority):
15312 - When computing directory thresholds, ignore any rejected-as-sybil
15313 nodes during the computation so that they can't influence Fast,
15314 Guard, etc. (We should have done this for proposal 109.) Fixes
15316 - When marking a node as a likely sybil, reset its uptime metrics
15317 to zero, so that it cannot time towards getting marked as Guard,
15318 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
15322 - When a TLS write is partially successful but incomplete, remember
15323 that the flushed part has been flushed, and notice that bytes were
15324 actually written. Reported and fixed pseudonymously. Fixes bug
15325 7708; bugfix on Tor 0.1.0.5-rc.
15326 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
15327 ID: these could be used to create unexpected streams and circuits
15328 which would count as "present" to some parts of Tor but "absent"
15329 to others, leading to zombie circuits and streams or to a bandwidth
15330 denial-of-service. Fixes bug 7889; bugfix on every released version
15331 of Tor. Reported by "oftc_must_be_destroyed".
15332 - Rename all macros in our local copy of queue.h to begin with "TOR_".
15333 This change seems the only good way to permanently prevent conflicts
15334 with queue.h on various operating systems. Fixes bug 8107; bugfix
15337 o Major features (relay):
15338 - Instead of limiting the number of queued onionskins (aka circuit
15339 create requests) to a fixed, hard-to-configure number, we limit
15340 the size of the queue based on how many we expect to be able to
15341 process in a given amount of time. We estimate the time it will
15342 take to process an onionskin based on average processing time
15343 of previous onionskins. Closes ticket 7291. You'll never have to
15344 configure MaxOnionsPending again.
15346 o Major features (portability):
15347 - Resume building correctly with MSVC and Makefile.nmake. This patch
15348 resolves numerous bugs and fixes reported by ultramage, including
15349 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
15350 - Make the ntor and curve25519 code build correctly with MSVC.
15351 Fix on 0.2.4.8-alpha.
15354 - When directory authorities are computing thresholds for flags,
15355 never let the threshold for the Fast flag fall below 4096
15356 bytes. Also, do not consider nodes with extremely low bandwidths
15357 when deciding thresholds for various directory flags. This change
15358 should raise our threshold for Fast relays, possibly in turn
15359 improving overall network performance; see ticket 1854. Resolves
15361 - The Tor client now ignores sub-domain components of a .onion
15362 address. This change makes HTTP "virtual" hosting
15363 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
15364 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
15365 hosted on the same hidden service. Implements proposal 204.
15366 - We compute the overhead from passing onionskins back and forth to
15367 cpuworkers, and report it when dumping statistics in response to
15368 SIGUSR1. Supports ticket 7291.
15370 o Minor features (path selection):
15371 - When deciding whether we have enough descriptors to build circuits,
15372 instead of looking at raw relay counts, look at which fraction
15373 of (bandwidth-weighted) paths we're able to build. This approach
15374 keeps clients from building circuits if their paths are likely to
15375 stand out statistically. The default fraction of paths needed is
15376 taken from the consensus directory; you can override it with the
15377 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
15378 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
15379 and we have GeoIP information, also exclude all nodes with unknown
15380 countries "??" and "A1". This behavior is controlled by the
15381 new GeoIPExcludeUnknown option: you can make such nodes always
15382 excluded with "GeoIPExcludeUnknown 1", and disable the feature
15383 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
15384 gets you the default behavior. Implements feature 7706.
15385 - Path Use Bias: Perform separate accounting for successful circuit
15386 use. Keep separate statistics on stream attempt rates versus stream
15387 success rates for each guard. Provide configurable thresholds to
15388 determine when to emit log messages or disable use of guards that
15389 fail too many stream attempts. Resolves ticket 7802.
15391 o Minor features (log messages):
15392 - When learning a fingerprint for a bridge, log its corresponding
15393 transport type. Implements ticket 7896.
15394 - Improve the log message when "Bug/attack: unexpected sendme cell
15395 from client" occurs, to help us track bug 8093.
15398 - Remove a couple of extraneous semicolons that were upsetting the
15399 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
15400 bugfix on 0.2.2.1-alpha.
15401 - Remove a source of rounding error during path bias count scaling;
15402 don't count cannibalized circuits as used for path bias until we
15403 actually try to use them; and fix a circuit_package_relay_cell()
15404 warning message about n_chan==NULL. Fixes bug 7802.
15405 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
15406 actually link against nacl when we're configured to use it. Fixes
15407 bug 7972; bugfix on 0.2.4.8-alpha.
15408 - Compile correctly with the --disable-curve25519 option. Fixes
15409 bug 8153; bugfix on 0.2.4.8-alpha.
15411 o Build improvements:
15412 - Do not report status verbosely from autogen.sh unless the -v flag
15413 is specified. Fixes issue 4664. Patch from Onizuka.
15414 - Replace all calls to snprintf() outside of src/ext with
15415 tor_snprintf(). Also remove the #define to replace snprintf with
15416 _snprintf on Windows; they have different semantics, and all of
15417 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
15418 - Try to detect if we are ever building on a platform where
15419 memset(...,0,...) does not set the value of a double to 0.0. Such
15420 platforms are permitted by the C standard, though in practice
15421 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
15422 currently support them, but it's better to detect them and fail
15423 than to perform erroneously.
15425 o Removed features:
15426 - Stop exporting estimates of v2 and v3 directory traffic shares
15427 in extrainfo documents. They were unneeded and sometimes inaccurate.
15428 Also stop exporting any v2 directory request statistics. Resolves
15430 - Drop support for detecting and warning about versions of Libevent
15431 before 1.3e. Nothing reasonable ships with them any longer;
15432 warning the user about them shouldn't be needed. Resolves ticket
15435 o Code simplifications and refactoring:
15436 - Rename "isin" functions to "contains", for grammar. Resolves
15438 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
15439 with the natural logarithm function from the system libm. Resolves
15443 Changes in version 0.2.4.9-alpha - 2013-01-15
15444 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
15445 work more robustly.
15448 - Fix backward compatibility logic when receiving an embedded ntor
15449 handshake tunneled in a CREATE cell. This clears up the "Bug:
15450 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
15454 Changes in version 0.2.4.8-alpha - 2013-01-14
15455 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
15456 risks, adds a new stronger and faster circuit handshake, and offers
15457 stronger and faster link encryption when both sides support it.
15460 - Preliminary support for directory guards (proposal 207): when
15461 possible, clients now use their entry guards for non-anonymous
15462 directory requests. This can help prevent client enumeration. Note
15463 that this behavior only works when we have a usable consensus
15464 directory, and when options about what to download are more or less
15465 standard. In the future we should re-bootstrap from our guards,
15466 rather than re-bootstrapping from the preconfigured list of
15467 directory sources that ships with Tor. Resolves ticket 6526.
15468 - Tor relays and clients now support a better CREATE/EXTEND cell
15469 format, allowing the sender to specify multiple address, identity,
15470 and handshake types. Implements Robert Ransom's proposal 200;
15471 closes ticket 7199.
15473 o Major features (new circuit handshake):
15474 - Tor now supports a new circuit extension handshake designed by Ian
15475 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
15476 circuit extension handshake, later called "TAP", was a bit slow
15477 (especially on the relay side), had a fragile security proof, and
15478 used weaker keys than we'd now prefer. The new circuit handshake
15479 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
15480 function, making it significantly more secure than the older
15481 handshake, and significantly faster. Tor can use one of two built-in
15482 pure-C curve25519-donna implementations by Adam Langley, or it
15483 can link against the "nacl" library for a tuned version if present.
15485 The built-in version is very fast for 64-bit systems when building
15486 with GCC. The built-in 32-bit version is still faster than the
15487 old TAP protocol, but using libnacl is better on most such hosts.
15489 Clients don't currently use this protocol by default, since
15490 comparatively few clients support it so far. To try it, set
15491 UseNTorHandshake to 1.
15493 Implements proposal 216; closes ticket 7202.
15495 o Major features (better link encryption):
15496 - Relays can now enable the ECDHE TLS ciphersuites when available
15497 and appropriate. These ciphersuites let us negotiate forward-secure
15498 TLS secret keys more safely and more efficiently than with our
15499 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
15500 public relays prefer the (faster) P224 group, and bridges prefer
15501 the (more common) P256 group; you can override this with the
15504 Enabling these ciphers was a little tricky, since for a long time,
15505 clients had been claiming to support them without actually doing
15506 so, in order to foil fingerprinting. But with the client-side
15507 implementation of proposal 198 in 0.2.3.17-beta, clients can now
15508 match the ciphers from recent Firefox versions *and* list the
15509 ciphers they actually mean, so relays can believe such clients
15510 when they advertise ECDHE support in their TLS ClientHello messages.
15512 This feature requires clients running 0.2.3.17-beta or later,
15513 and requires both sides to be running OpenSSL 1.0.0 or later
15514 with ECC support. OpenSSL 1.0.1, with the compile-time option
15515 "enable-ec_nistp_64_gcc_128", is highly recommended.
15517 Implements the relay side of proposal 198; closes ticket 7200.
15520 - Avoid crashing when, as a relay without IPv6-exit support, a
15521 client insists on getting an IPv6 address or nothing. Fixes bug
15522 7814; bugfix on 0.2.4.7-alpha.
15525 - Improve circuit build timeout handling for hidden services.
15526 In particular: adjust build timeouts more accurately depending
15527 upon the number of hop-RTTs that a particular circuit type
15528 undergoes. Additionally, launch intro circuits in parallel
15529 if they timeout, and take the first one to reply as valid.
15530 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
15531 separate error codes; or at least, don't break for that reason.
15532 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
15533 - Update to the January 2 2013 Maxmind GeoLite Country database.
15535 o Minor features (testing):
15536 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
15537 (P-256) Diffie-Hellman handshakes to src/or/bench.
15538 - Add benchmark functions to test onion handshake performance.
15540 o Minor features (path bias detection):
15541 - Alter the Path Bias log messages to be more descriptive in terms
15542 of reporting timeouts and other statistics.
15543 - Create three levels of Path Bias log messages, as opposed to just
15544 two. These are configurable via consensus as well as via the torrc
15545 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
15546 The default values are 0.70, 0.50, and 0.30 respectively.
15547 - Separate the log message levels from the decision to drop guards,
15548 which also is available via torrc option PathBiasDropGuards.
15549 PathBiasDropGuards still defaults to 0 (off).
15550 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
15551 in combination with PathBiasExtremeRate.
15552 - Increase the default values for PathBiasScaleThreshold and
15553 PathBiasCircThreshold from (200, 20) to (300, 150).
15554 - Add in circuit usage accounting to path bias. If we try to use a
15555 built circuit but fail for any reason, it counts as path bias.
15556 Certain classes of circuits where the adversary gets to pick your
15557 destination node are exempt from this accounting. Usage accounting
15558 can be specifically disabled via consensus parameter or torrc.
15559 - Convert all internal path bias state to double-precision floating
15560 point, to avoid roundoff error and other issues.
15561 - Only record path bias information for circuits that have completed
15562 *two* hops. Assuming end-to-end tagging is the attack vector, this
15563 makes us more resilient to ambient circuit failure without any
15564 detection capability loss.
15566 o Minor bugfixes (log messages):
15567 - Rate-limit the "No circuits are opened. Relaxed timeout for a
15568 circuit with channel state open..." message to once per hour to
15569 keep it from filling the notice logs. Mitigates bug 7799 but does
15570 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
15571 - Avoid spurious warnings when configuring multiple client ports of
15572 which only some are nonlocal. Previously, we had claimed that some
15573 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
15576 o Code simplifications and refactoring:
15577 - Get rid of a couple of harmless clang warnings, where we compared
15578 enums to ints. These warnings are newly introduced in clang 3.2.
15579 - Split the onion.c file into separate modules for the onion queue
15580 and the different handshakes it supports.
15581 - Remove the marshalling/unmarshalling code for sending requests to
15582 cpuworkers over a socket, and instead just send structs. The
15583 recipient will always be the same Tor binary as the sender, so
15584 any encoding is overkill.
15587 Changes in version 0.2.4.7-alpha - 2012-12-24
15588 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
15589 directory mirrors for more robust bootstrapping; fixes more issues where
15590 clients with changing network conditions refuse to make any circuits;
15591 adds initial support for exiting to IPv6 addresses; resumes being able
15592 to update our GeoIP database, and includes the geoip6 file this time;
15593 turns off the client-side DNS cache by default due to privacy risks;
15594 and fixes a variety of other issues.
15596 o Major features (client resilience):
15597 - Add a new "FallbackDir" torrc option to use when we can't use
15598 a directory mirror from the consensus (either because we lack a
15599 consensus, or because they're all down). Currently, all authorities
15600 are fallbacks by default, and there are no other default fallbacks,
15601 but that will change. This option will allow us to give clients a
15602 longer list of servers to try to get a consensus from when first
15603 connecting to the Tor network, and thereby reduce load on the
15604 directory authorities. Implements proposal 206, "Preconfigured
15605 directory sources for bootstrapping". We also removed the old
15606 "FallbackNetworkstatus" option, since we never got it working well
15607 enough to use it. Closes bug 572.
15608 - If we have no circuits open, use a relaxed timeout (the
15609 95-percentile cutoff) until a circuit succeeds. This heuristic
15610 should allow Tor to succeed at building circuits even when the
15611 network connection drastically changes. Should help with bug 3443.
15613 o Major features (IPv6):
15614 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
15615 connectivity, then set the IPv6Exit flag to 1. Also make sure your
15616 exit policy reads as you would like: the address * applies to all
15617 address families, whereas *4 is IPv4 address only, and *6 is IPv6
15618 addresses only. On the client side, you'll need to wait until the
15619 authorities have upgraded, wait for enough exits to support IPv6,
15620 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
15621 ticket 5547, implements proposal 117 as revised in proposal 208.
15623 We DO NOT recommend that clients with actual anonymity needs start
15624 using IPv6 over Tor yet, since not enough exits support it yet.
15626 o Major features (geoip database):
15627 - Maxmind began labelling Tor relays as being in country "A1",
15628 which breaks by-country node selection inside Tor. Now we use a
15629 script to replace "A1" ("Anonymous Proxy") entries in our geoip
15630 file with real country codes. This script fixes about 90% of "A1"
15631 entries automatically and uses manual country code assignments to
15632 fix the remaining 10%. See src/config/README.geoip for details.
15633 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
15634 Country database, as modified above.
15636 o Major bugfixes (client-side DNS):
15637 - Turn off the client-side DNS cache by default. Updating and using
15638 the DNS cache is now configurable on a per-client-port
15639 level. SOCKSPort, DNSPort, etc lines may now contain
15640 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
15641 cache these types of DNS answers when we receive them from an
15642 exit node in response to an application request on this port, and
15643 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
15644 cached DNS answers of these types, we shouldn't use them. It's
15645 potentially risky to use cached DNS answers at the client, since
15646 doing so can indicate to one exit what answers we've gotten
15647 for DNS lookups in the past. With IPv6, this becomes especially
15648 problematic. Using cached DNS answers for requests on the same
15649 circuit would present less linkability risk, since all traffic
15650 on a circuit is already linkable, but it would also provide
15651 little performance benefit: the exit node caches DNS replies
15652 too. Implements a simplified version of Proposal 205. Implements
15655 o Major bugfixes (other):
15656 - Alter circuit build timeout measurement to start at the point
15657 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
15658 initialization). This should make our timeout measurements more
15659 uniform. Previously, we were sometimes including ORconn setup time
15660 in our circuit build time measurements. Should resolve bug 3443.
15661 - Fix an assertion that could trigger in hibernate_go_dormant() when
15662 closing an or_connection_t: call channel_mark_for_close() rather
15663 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
15665 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
15666 7655; bugfix on 0.2.4.6-alpha.
15669 - Add a new torrc option "ServerTransportListenAddr" to let bridge
15670 operators select the address where their pluggable transports will
15671 listen for connections. Resolves ticket 7013.
15672 - Allow an optional $ before the node identity digest in the
15673 controller command GETINFO ns/id/<identity>, for consistency with
15674 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
15675 - Log packaged cell fullness as part of the heartbeat message.
15676 Diagnosis to try to determine the extent of bug 7743.
15678 o Minor features (IPv6):
15679 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
15680 prefer to hand out virtual IPv6 addresses, since there are more of
15681 them and we can't run out. To override this behavior and make IPv4
15682 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
15683 or DNSPort you're using for resolving. Implements ticket 7571.
15684 - AutomapHostsOnResolve responses are now randomized, to avoid
15685 annoying situations where Tor is restarted and applications
15686 connect to the wrong addresses.
15687 - Never try more than 1000 times to pick a new virtual address when
15688 AutomapHostsOnResolve is set. That's good enough so long as we
15689 aren't close to handing out our entire virtual address space;
15690 if you're getting there, it's best to switch to IPv6 virtual
15694 - The ADDRMAP command can no longer generate an ill-formed error
15695 code on a failed MAPADDRESS. It now says "internal" rather than
15696 an English sentence fragment with spaces in the middle. Bugfix on
15697 Tor 0.2.0.19-alpha.
15698 - Fix log messages and comments to avoid saying "GMT" when we mean
15699 "UTC". Fixes bug 6113.
15700 - Compile on win64 using mingw64. Fixes bug 7260; patches from
15702 - Fix a crash when debugging unit tests on Windows: deallocate a
15703 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
15704 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
15707 - The DirServer option is now DirAuthority, for consistency with
15708 current naming patterns. You can still use the old DirServer form.
15710 o Code simplification and refactoring:
15711 - Move the client-side address-map/virtual-address/DNS-cache code
15712 out of connection_edge.c into a new addressmap.c module.
15713 - Remove unused code for parsing v1 directories and "running routers"
15714 documents. Fixes bug 6887.
15717 Changes in version 0.2.3.25 - 2012-11-19
15718 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
15719 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
15720 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
15721 programmer, and friend. Unstinting in his dedication to the cause of
15722 freedom, he inspired and helped many of us as we began our work on
15723 anonymity, and inspires us still. Please honor his memory by writing
15724 software to protect people's freedoms, and by helping others to do so.
15726 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
15727 significantly reduced directory overhead (via microdescriptors),
15728 enormous crypto performance improvements for fast relays on new
15729 enough hardware, a new v3 TLS handshake protocol that can better
15730 resist fingerprinting, support for protocol obfuscation plugins (aka
15731 pluggable transports), better scalability for hidden services, IPv6
15732 support for bridges, performance improvements like allowing clients
15733 to skip the first round-trip on the circuit ("optimistic data") and
15734 refilling token buckets more often, a new "stream isolation" design
15735 to isolate different applications on different circuits, and many
15736 stability, security, and privacy fixes.
15739 - Tor tries to wipe potentially sensitive data after using it, so
15740 that if some subsequent security failure exposes Tor's memory,
15741 the damage will be limited. But we had a bug where the compiler
15742 was eliminating these wipe operations when it decided that the
15743 memory was no longer visible to a (correctly running) program,
15744 hence defeating our attempt at defense in depth. We fix that
15745 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
15746 is unlikely to optimize away. Future versions of Tor may use
15747 a less ridiculously heavy approach for this. Fixes bug 7352.
15748 Reported in an article by Andrey Karpov.
15751 - Fix a harmless bug when opting against publishing a relay descriptor
15752 because DisableNetwork is set. Fixes bug 7464; bugfix on
15756 Changes in version 0.2.4.6-alpha - 2012-11-13
15757 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
15758 makes our defense-in-depth memory wiping more reliable, and begins to
15759 count IPv6 addresses in bridge statistics,
15762 - Fix an assertion failure that could occur when closing a connection
15763 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
15765 - Tor tries to wipe potentially sensitive data after using it, so
15766 that if some subsequent security failure exposes Tor's memory,
15767 the damage will be limited. But we had a bug where the compiler
15768 was eliminating these wipe operations when it decided that the
15769 memory was no longer visible to a (correctly running) program,
15770 hence defeating our attempt at defense in depth. We fix that
15771 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
15772 is unlikely to optimize away. Future versions of Tor may use
15773 a less ridiculously heavy approach for this. Fixes bug 7352.
15774 Reported in an article by Andrey Karpov.
15777 - Add GeoIP database for IPv6 addresses. The new config option
15779 - Bridge statistics now count bridge clients connecting over IPv6:
15780 bridge statistics files now list "bridge-ip-versions" and
15781 extra-info documents list "geoip6-db-digest". The control protocol
15782 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
15783 implementation by "shkoo", addressing ticket 5055.
15786 - Warn when we are binding low ports when hibernation is enabled;
15787 previously we had warned when we were _advertising_ low ports with
15788 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
15789 - Fix a harmless bug when opting against publishing a relay descriptor
15790 because DisableNetwork is set. Fixes bug 7464; bugfix on
15792 - Add warning message when a managed proxy dies during configuration.
15793 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
15794 - Fix a linking error when building tor-fw-helper without miniupnp.
15795 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
15796 - Check for closing an or_connection_t without going through correct
15797 channel functions; emit a warning and then call
15798 connection_or_close_for_error() so we don't assert as in bugs 7212
15800 - Compile correctly on compilers without C99 designated initializer
15801 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
15802 - Avoid a possible assert that can occur when channel_send_destroy() is
15803 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
15804 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
15805 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
15806 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
15807 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
15809 o Code simplification and refactoring:
15810 - Start using OpenBSD's implementation of queue.h, so that we don't
15811 need to hand-roll our own pointer and list structures whenever we
15812 need them. (We can't rely on a sys/queue.h, since some operating
15813 systems don't have them, and the ones that do have them don't all
15814 present the same extensions.)
15817 Changes in version 0.2.4.5-alpha - 2012-10-25
15818 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
15819 two important security vulnerabilities that could lead to remotely
15820 triggerable relay crashes, fix a major bug that was preventing clients
15821 from choosing suitable exit nodes, and refactor some of our code.
15823 o Major bugfixes (security, also in 0.2.3.24-rc):
15824 - Fix a group of remotely triggerable assertion failures related to
15825 incorrect link protocol negotiation. Found, diagnosed, and fixed
15826 by "some guy from France". Fix for CVE-2012-2250; bugfix on
15828 - Fix a denial of service attack by which any directory authority
15829 could crash all the others, or by which a single v2 directory
15830 authority could crash everybody downloading v2 directory
15831 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
15833 o Major bugfixes (also in 0.2.3.24-rc):
15834 - When parsing exit policy summaries from microdescriptors, we had
15835 previously been ignoring the last character in each one, so that
15836 "accept 80,443,8080" would be treated by clients as indicating
15837 a node that allows access to ports 80, 443, and 808. That would
15838 lead to clients attempting connections that could never work,
15839 and ignoring exit nodes that would support their connections. Now
15840 clients parse these exit policy summaries correctly. Fixes bug 7192;
15841 bugfix on 0.2.3.1-alpha.
15843 o Minor bugfixes (also in 0.2.3.24-rc):
15844 - Clients now consider the ClientRejectInternalAddresses config option
15845 when using a microdescriptor consensus stanza to decide whether
15846 an exit relay would allow exiting to an internal address. Fixes
15847 bug 7190; bugfix on 0.2.3.1-alpha.
15850 - Only disable TLS session ticket support when running as a TLS
15851 server. Now clients will blend better with regular Firefox
15852 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
15854 o Code simplification and refactoring:
15855 - Start using OpenBSD's implementation of queue.h (originally by
15857 - Move the entry node code from circuitbuild.c to its own file.
15858 - Move the circuit build timeout tracking code from circuitbuild.c
15862 Changes in version 0.2.3.24-rc - 2012-10-25
15863 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
15864 could lead to remotely triggerable relay crashes, and fixes
15865 a major bug that was preventing clients from choosing suitable exit
15868 o Major bugfixes (security):
15869 - Fix a group of remotely triggerable assertion failures related to
15870 incorrect link protocol negotiation. Found, diagnosed, and fixed
15871 by "some guy from France". Fix for CVE-2012-2250; bugfix on
15873 - Fix a denial of service attack by which any directory authority
15874 could crash all the others, or by which a single v2 directory
15875 authority could crash everybody downloading v2 directory
15876 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
15879 - When parsing exit policy summaries from microdescriptors, we had
15880 previously been ignoring the last character in each one, so that
15881 "accept 80,443,8080" would be treated by clients as indicating
15882 a node that allows access to ports 80, 443, and 808. That would
15883 lead to clients attempting connections that could never work,
15884 and ignoring exit nodes that would support their connections. Now
15885 clients parse these exit policy summaries correctly. Fixes bug 7192;
15886 bugfix on 0.2.3.1-alpha.
15889 - Clients now consider the ClientRejectInternalAddresses config option
15890 when using a microdescriptor consensus stanza to decide whether
15891 an exit relay would allow exiting to an internal address. Fixes
15892 bug 7190; bugfix on 0.2.3.1-alpha.
15895 Changes in version 0.2.4.4-alpha - 2012-10-20
15896 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
15897 vulnerability introduced by a change in OpenSSL, fixes a remotely
15898 triggerable assert, and adds new channel_t and circuitmux_t abstractions
15899 that will make it easier to test new connection transport and cell
15900 scheduling algorithms.
15902 o New directory authorities (also in 0.2.3.23-rc):
15903 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
15904 authority. Closes ticket 5749.
15906 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
15907 - Disable TLS session tickets. OpenSSL's implementation was giving
15908 our TLS session keys the lifetime of our TLS context objects, when
15909 perfect forward secrecy would want us to discard anything that
15910 could decrypt a link connection as soon as the link connection
15911 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
15912 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
15913 - Discard extraneous renegotiation attempts once the V3 link
15914 protocol has been initiated. Failure to do so left us open to
15915 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
15916 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
15918 o Internal abstraction features:
15919 - Introduce new channel_t abstraction between circuits and
15920 or_connection_t to allow for implementing alternate OR-to-OR
15921 transports. A channel_t is an abstract object which can either be a
15922 cell-bearing channel, which is responsible for authenticating and
15923 handshaking with the remote OR and transmitting cells to and from
15924 it, or a listening channel, which spawns new cell-bearing channels
15925 at the request of remote ORs. Implements part of ticket 6465.
15926 - Also new is the channel_tls_t subclass of channel_t, adapting it
15927 to the existing or_connection_t code. The V2/V3 protocol handshaking
15928 code which formerly resided in command.c has been moved below the
15929 channel_t abstraction layer and may be found in channeltls.c now.
15930 Implements the rest of ticket 6465.
15931 - Introduce new circuitmux_t storing the queue of circuits for
15932 a channel; this encapsulates and abstracts the queue logic and
15933 circuit selection policy, and allows the latter to be overridden
15934 easily by switching out a policy object. The existing EWMA behavior
15935 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
15937 o Required libraries:
15938 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
15939 strongly recommended.
15942 - Warn users who run hidden services on a Tor client with
15943 UseEntryGuards disabled that their hidden services will be
15944 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
15945 attack which motivated Tor to support entry guards in the first
15946 place). Resolves ticket 6889.
15947 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
15948 dhill. Resolves ticket 6982.
15949 - Option OutboundBindAddress can be specified multiple times and
15950 accepts IPv6 addresses. Resolves ticket 6876.
15952 o Minor bugfixes (also in 0.2.3.23-rc):
15953 - Don't serve or accept v2 hidden service descriptors over a
15954 relay's DirPort. It's never correct to do so, and disabling it
15955 might make it more annoying to exploit any bugs that turn up in the
15956 descriptor-parsing code. Fixes bug 7149.
15957 - Fix two cases in src/or/transports.c where we were calling
15958 fmt_addr() twice in a parameter list. Bug found by David
15959 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
15960 - Fix memory leaks whenever we logged any message about the "path
15961 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
15962 - When relays refuse a "create" cell because their queue of pending
15963 create cells is too big (typically because their cpu can't keep up
15964 with the arrival rate), send back reason "resource limit" rather
15965 than reason "internal", so network measurement scripts can get a
15966 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
15969 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
15970 - Free some more still-in-use memory at exit, to make hunting for
15971 memory leaks easier. Resolves bug 7029.
15972 - When a Tor client gets a "truncated" relay cell, the first byte of
15973 its payload specifies why the circuit was truncated. We were
15974 ignoring this 'reason' byte when tearing down the circuit, resulting
15975 in the controller not being told why the circuit closed. Now we
15976 pass the reason from the truncated cell to the controller. Bugfix
15977 on 0.1.2.3-alpha; fixes bug 7039.
15978 - Downgrade "Failed to hand off onionskin" messages to "debug"
15979 severity, since they're typically redundant with the "Your computer
15980 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
15981 - Make clients running with IPv6 bridges connect over IPv6 again,
15982 even without setting new config options ClientUseIPv6 and
15983 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
15984 - Use square brackets around IPv6 addresses in numerous places
15985 that needed them, including log messages, HTTPS CONNECT proxy
15986 requests, TransportProxy statefile entries, and pluggable transport
15987 extra-info lines. Fixes bug 7011; patch by David Fifield.
15989 o Code refactoring and cleanup:
15990 - Source files taken from other packages now reside in src/ext;
15991 previously they were scattered around the rest of Tor.
15992 - Avoid use of reserved identifiers in our C code. The C standard
15993 doesn't like us declaring anything that starts with an
15994 underscore, so let's knock it off before we get in trouble. Fix
15995 for bug 1031; bugfix on the first Tor commit.
15998 Changes in version 0.2.3.23-rc - 2012-10-20
15999 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
16000 vulnerability introduced by a change in OpenSSL, and fixes a variety
16001 of smaller bugs in preparation for the release.
16003 o New directory authorities:
16004 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
16005 authority. Closes ticket 5749.
16007 o Major bugfixes (security/privacy):
16008 - Disable TLS session tickets. OpenSSL's implementation was giving
16009 our TLS session keys the lifetime of our TLS context objects, when
16010 perfect forward secrecy would want us to discard anything that
16011 could decrypt a link connection as soon as the link connection
16012 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
16013 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
16014 - Discard extraneous renegotiation attempts once the V3 link
16015 protocol has been initiated. Failure to do so left us open to
16016 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
16017 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
16020 - Fix a possible crash bug when checking for deactivated circuits
16021 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
16022 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
16024 o Minor bugfixes (on 0.2.3.x):
16025 - Fix two cases in src/or/transports.c where we were calling
16026 fmt_addr() twice in a parameter list. Bug found by David
16027 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
16028 - Convert an assert in the pathbias code to a log message. The assert
16029 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
16030 bugfix on 0.2.3.17-beta.
16031 - Fix memory leaks whenever we logged any message about the "path
16032 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
16034 o Minor bugfixes (on 0.2.2.x and earlier):
16035 - Don't serve or accept v2 hidden service descriptors over a relay's
16036 DirPort. It's never correct to do so, and disabling it might
16037 make it more annoying to exploit any bugs that turn up in the
16038 descriptor-parsing code. Fixes bug 7149.
16039 - When relays refuse a "create" cell because their queue of pending
16040 create cells is too big (typically because their cpu can't keep up
16041 with the arrival rate), send back reason "resource limit" rather
16042 than reason "internal", so network measurement scripts can get a
16043 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
16044 - Correct file sizes when reading binary files on Cygwin, to avoid
16045 a bug where Tor would fail to read its state file. Fixes bug 6844;
16046 bugfix on 0.1.2.7-alpha.
16047 - Avoid undefined behavior when parsing the list of supported
16048 rendezvous/introduction protocols in a hidden service descriptor.
16049 Previously, Tor would have confused (as-yet-unused) protocol version
16050 numbers greater than 32 with lower ones on many platforms. Fixes
16051 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
16053 o Documentation fixes:
16054 - Clarify that hidden services are TCP only. Fixes bug 6024.
16057 Changes in version 0.2.4.3-alpha - 2012-09-22
16058 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
16059 assertion, resumes letting relays test reachability of their DirPort,
16060 and cleans up a bunch of smaller bugs.
16063 - Fix an assertion failure in tor_timegm() that could be triggered
16064 by a badly formatted directory object. Bug found by fuzzing with
16065 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
16068 - Fix a possible crash bug when checking for deactivated circuits
16069 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
16070 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
16071 - Allow routers to detect that their own DirPorts are running. When
16072 we removed support for versions_supports_begindir, we also
16073 accidentally removed the mechanism we used to self-test our
16074 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
16075 bugfix on 0.2.4.2-alpha.
16077 o Security features:
16078 - Switch to a completely time-invariant approach for picking nodes
16079 weighted by bandwidth. Our old approach would run through the
16080 part of the loop after it had made its choice slightly slower
16081 than it ran through the part of the loop before it had made its
16082 choice. Addresses ticket 6538.
16083 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
16084 by tor2web clients allows hidden services to identify tor2web
16085 clients through their repeated selection of the same rendezvous
16086 and introduction point circuit endpoints (their guards). Resolves
16090 - Enable Tor to read configuration, state, and key information from
16091 a FIFO. Previously Tor would only read from files with a positive
16092 stat.st_size. Code from meejah; fixes bug 6044.
16095 - Correct file sizes when reading binary files on Cygwin, to avoid
16096 a bug where Tor would fail to read its state file. Fixes bug 6844;
16097 bugfix on 0.1.2.7-alpha.
16098 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
16099 bugfix on 0.2.0.3-alpha.
16100 - When complaining about a client port on a public address, log
16101 which address we're complaining about. Fixes bug 4020; bugfix on
16102 0.2.3.3-alpha. Patch by Tom Fitzhenry.
16103 - Convert an assert in the pathbias code to a log message. The assert
16104 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
16105 bugfix on 0.2.3.17-beta.
16106 - Our new buildsystem was overzealous about rebuilding manpages: it
16107 would rebuild them all whenever any one of them changed. Now our
16108 dependency checking should be correct. Fixes bug 6843; bugfix on
16110 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
16111 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
16112 - Correct log printout about which address family is preferred
16113 when connecting to a bridge with both an IPv4 and IPv6 OR port.
16114 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
16116 o Minor bugfixes (code cleanliness):
16117 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
16118 with large values. This situation was untriggered, but nevertheless
16119 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
16120 - Reject consensus votes with more than 64 known-flags. We aren't even
16121 close to that limit yet, and our code doesn't handle it correctly.
16122 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
16123 - Avoid undefined behavior when parsing the list of supported
16124 rendezvous/introduction protocols in a hidden service descriptor.
16125 Previously, Tor would have confused (as-yet-unused) protocol version
16126 numbers greater than 32 with lower ones on many platforms. Fixes
16127 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
16128 - Fix handling of rendezvous client authorization types over 8.
16129 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
16130 - Fix building with older versions of GCC (2.95, for one) that don't
16131 like preprocessor directives inside macro arguments. Found by
16132 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
16133 - Switch weighted node selection rule from using a list of doubles
16134 to using a list of int64_t. This change should make the process
16135 slightly easier to debug and maintain. Needed to finish ticket 6538.
16137 o Code simplification and refactoring:
16138 - Move the generic "config" code into a new file, and have "config.c"
16139 hold only torrc- and state-related code. Resolves ticket 6823.
16140 - Move the core of our "choose a weighted element at random" logic
16141 into its own function, and give it unit tests. Now the logic is
16142 testable, and a little less fragile too.
16143 - Removed the testing_since field of node_t, which hasn't been used
16144 for anything since 0.2.0.9-alpha.
16146 o Documentation fixes:
16147 - Clarify that hidden services are TCP only. Fixes bug 6024.
16148 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
16152 Changes in version 0.2.3.22-rc - 2012-09-11
16153 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
16157 - Fix an assertion failure in tor_timegm() that could be triggered
16158 by a badly formatted directory object. Bug found by fuzzing with
16159 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
16162 - Avoid segfault when starting up having run with an extremely old
16163 version of Tor and parsing its state file. Fixes bug 6801; bugfix
16167 Changes in version 0.2.2.39 - 2012-09-11
16168 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
16172 - Fix an assertion failure in tor_timegm() that could be triggered
16173 by a badly formatted directory object. Bug found by fuzzing with
16174 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
16175 - Do not crash when comparing an address with port value 0 to an
16176 address policy. This bug could have been used to cause a remote
16177 assertion failure by or against directory authorities, or to
16178 allow some applications to crash clients. Fixes bug 6690; bugfix
16182 Changes in version 0.2.4.2-alpha - 2012-09-10
16183 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
16184 raises the default rate limiting even more, and makes the bootstrapping
16185 log messages less noisy.
16188 - Automatically forward the TCP ports of pluggable transport
16189 proxies using tor-fw-helper if PortForwarding is enabled. Implements
16193 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
16194 to 1GB/1GB. The previous defaults were intended to be "basically
16195 infinite", but it turns out they're now limiting our 100mbit+
16196 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
16197 last time we raised it).
16200 - Detect when we're running with a version of OpenSSL other than the
16201 one we compiled with. This has occasionally given people hard-to-
16203 - Log fewer lines at level "notice" about our OpenSSL and Libevent
16204 versions and capabilities when everything is going right. Resolves
16205 part of ticket 6736.
16206 - Directory authorities no long accept descriptors for any version of
16207 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
16208 These versions are insecure, unsupported, or both. Implements
16212 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
16213 to start with a triple-underscore so the controller won't touch it.
16214 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
16215 - Avoid segfault when starting up having run with an extremely old
16216 version of Tor and parsing its state file. Fixes bug 6801; bugfix
16218 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
16219 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
16220 - Don't follow the NULL pointer if microdescriptor generation fails.
16221 (This does not appear to be triggerable, but it's best to be safe.)
16222 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
16223 - Fix mis-declared dependencies on src/common/crypto.c and
16224 src/or/tor_main.c that could break out-of-tree builds under some
16225 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
16226 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
16227 6778; bugfix on 0.2.4.1-alpha.
16228 - Fix a harmless (in this case) build warning for implicitly
16229 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
16231 o Removed features:
16232 - Now that all versions before 0.2.2.x are disallowed, we no longer
16233 need to work around their missing features. Thus we can remove a
16234 bunch of compatibility code.
16236 o Code refactoring:
16237 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
16238 TCP ports to forward. In the past it only accepted two ports:
16239 the ORPort and the DirPort.
16242 Changes in version 0.2.4.1-alpha - 2012-09-05
16243 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
16244 bridgedb; lets relays use IPv6 addresses and directory authorities
16245 advertise them; and switches to a cleaner build interface.
16247 This is the first alpha release in a new series, so expect there to
16248 be bugs. Users who would rather test out a more stable branch should
16249 stay with 0.2.3.x for now.
16251 o Major features (bridges):
16252 - Bridges now report the pluggable transports they support to the
16253 bridge authority, so it can pass the supported transports on to
16254 bridgedb and/or eventually do reachability testing. Implements
16257 o Major features (IPv6):
16258 - Bridge authorities now accept IPv6 bridge addresses and include
16259 them in network status documents. Implements ticket 5534.
16260 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
16261 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
16262 to happen. Implements ticket 5535.
16263 - All kind of relays, not just bridges, can now advertise an IPv6
16264 OR port. Implements ticket 6362.
16265 - Directory authorities vote on IPv6 OR ports using the new consensus
16266 method 14. Implements ticket 6363.
16268 o Major features (build):
16269 - Switch to a nonrecursive Makefile structure. Now instead of each
16270 Makefile.am invoking other Makefile.am's, there is a master
16271 Makefile.am that includes the others. This change makes our build
16272 process slightly more maintainable, and improves parallelism for
16273 building with make -j. Original patch by Stewart Smith; various
16274 fixes by Jim Meyering.
16275 - Where available, we now use automake's "silent" make rules by
16276 default, so that warnings are easier to spot. You can get the old
16277 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
16279 o Minor features (code security and spec conformance):
16280 - Clear keys and key-derived material left on the stack in
16281 rendservice.c and rendclient.c. Check return value of
16282 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
16283 These fixes should make us more forward-secure against cold-boot
16284 attacks and the like. Fixes bug 2385.
16285 - Reject EXTEND cells sent to nonexistent streams. According to the
16286 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
16287 we were only checking for stream IDs that were currently in use.
16288 Found while hunting for more instances of bug 6271. Bugfix on
16289 0.0.2pre8, which introduced incremental circuit construction.
16291 o Minor features (streamlining);
16292 - No longer include the "opt" prefix when generating routerinfos
16293 or v2 directories: it has been needless since Tor 0.1.2. Closes
16295 - Remove some now-needless code that tried to aggressively flush
16296 OR connections as data was added to them. Since 0.2.0.1-alpha, our
16297 cell queue logic has saved us from the failure mode that this code
16298 was supposed to prevent. Removing this code will limit the number
16299 of baroque control flow paths through Tor's network logic. Reported
16300 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
16302 o Minor features (controller):
16303 - Add a "GETINFO signal/names" control port command. Implements
16305 - Provide default values for all options via "GETINFO config/defaults".
16306 Implements ticket 4971.
16308 o Minor features (IPv6):
16309 - New config option "AuthDirHasIPv6Connectivity 1" that directory
16310 authorities should set if they have IPv6 connectivity and want to
16311 do reachability tests for IPv6 relays. Implements feature 5974.
16312 - A relay with an IPv6 OR port now sends that address in NETINFO
16313 cells (in addition to its other address). Implements ticket 6364.
16315 o Minor features (log messages):
16316 - Omit the first heartbeat log message, because it never has anything
16317 useful to say, and it clutters up the bootstrapping messages.
16318 Resolves ticket 6758.
16319 - Don't log about reloading the microdescriptor cache at startup. Our
16320 bootstrap warnings are supposed to tell the user when there's a
16321 problem, and our bootstrap notices say when there isn't. Resolves
16322 ticket 6759; bugfix on 0.2.2.6-alpha.
16323 - Don't log "I learned some more directory information" when we're
16324 reading cached directory information. Reserve it for when new
16325 directory information arrives in response to a fetch. Resolves
16327 - Prevent rounding error in path bias counts when scaling
16328 them down, and use the correct scale factor default. Also demote
16329 some path bias related log messages down a level and make others
16330 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
16331 - We no longer warn so much when generating manpages from their
16334 o Code simplifications and refactoring:
16335 - Enhance our internal sscanf replacement so that we can eliminate
16336 the last remaining uses of the system sscanf. (Though those uses
16337 of sscanf were safe, sscanf itself is generally error prone, so
16338 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
16340 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
16341 - Move last_reachable and testing_since from routerinfo_t to node_t.
16342 Implements ticket 5529.
16343 - Add replaycache_t structure, functions and unit tests, then refactor
16344 rend_service_introduce() to be more clear to read, improve, debug,
16345 and test. Resolves bug 6177.
16346 - Finally remove support for malloc_good_size and malloc_usable_size.
16347 We had hoped that these functions would let us eke a little more
16348 memory out of our malloc implementation. Unfortunately, the only
16349 implementations that provided these functions are also ones that
16350 are already efficient about not overallocation: they never got us
16351 more than 7 or so bytes per allocation. Removing them saves us a
16352 little code complexity and a nontrivial amount of build complexity.
16354 o New requirements:
16355 - Tor maintainers now require Automake version 1.9 or later to build
16356 Tor from the Git repository. (Automake is not required when building
16357 from a source distribution.)
16360 Changes in version 0.2.3.21-rc - 2012-09-05
16361 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
16362 series. It fixes a trio of potential security bugs, fixes a bug where
16363 we were leaving some of the fast relays out of the microdescriptor
16364 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
16365 and cleans up other smaller issues.
16367 o Major bugfixes (security):
16368 - Tear down the circuit if we get an unexpected SENDME cell. Clients
16369 could use this trick to make their circuits receive cells faster
16370 than our flow control would have allowed, or to gum up the network,
16371 or possibly to do targeted memory denial-of-service attacks on
16372 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
16373 from July 2002, before the release of Tor 0.0.0. We had committed
16374 this patch previously, but we had to revert it because of bug 6271.
16375 Now that 6271 is fixed, this patch appears to work.
16376 - Reject any attempt to extend to an internal address. Without
16377 this fix, a router could be used to probe addresses on an internal
16378 network to see whether they were accepting connections. Fixes bug
16379 6710; bugfix on 0.0.8pre1.
16380 - Do not crash when comparing an address with port value 0 to an
16381 address policy. This bug could have been used to cause a remote
16382 assertion failure by or against directory authorities, or to
16383 allow some applications to crash clients. Fixes bug 6690; bugfix
16387 - Remove the upper bound on microdescriptor length. We were hitting
16388 the limit for routers with complex exit policies or family
16389 declarations, causing clients to not use them. Fixes the first
16390 piece of bug 6404; fix on 0.2.2.6-alpha.
16391 - Detect "ORPort 0" as meaning, uniformly, that we're not running
16392 as a relay. Previously, some of our code would treat the presence
16393 of any ORPort line as meaning that we should act like a relay,
16394 even though our new listener code would correctly not open any
16395 ORPorts for ORPort 0. Similar bugs in other Port options are also
16396 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
16399 - Avoid a pair of double-free and use-after-mark bugs that can
16400 occur with certain timings in canceled and re-received DNS
16401 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
16402 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
16403 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
16404 - Allow one-hop directory fetching circuits the full "circuit build
16405 timeout" period, rather than just half of it, before failing them
16406 and marking the relay down. This fix should help reduce cases where
16407 clients declare relays (or worse, bridges) unreachable because
16408 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
16409 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
16411 - Authorities no longer include any router in their microdescriptor
16412 consensuses for which they couldn't generate or agree on a
16413 microdescriptor. Fixes the second piece of bug 6404; fix on
16415 - Detect and reject attempts to specify both "FooPort" and
16416 "FooPort 0" in the same configuration domain. (It's still okay
16417 to have a FooPort in your configuration file, and use "FooPort 0"
16418 on the command line to disable it.) Fixes the second half of bug
16419 6507; bugfix on 0.2.3.3-alpha.
16420 - Make wildcarded addresses (that is, ones beginning with "*.") work
16421 when provided via the controller's MapAddress command. Previously,
16422 they were accepted, but we never actually noticed that they were
16423 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
16424 - Avoid crashing on a malformed state file where EntryGuardPathBias
16425 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
16426 - Add a (probably redundant) memory clear between iterations of
16427 the router status voting loop, to prevent future coding errors
16428 where data might leak between iterations of the loop. Resolves
16431 o Minor bugfixes (log messages):
16432 - Downgrade "set buildtimeout to low value" messages to "info"
16433 severity; they were never an actual problem, there was never
16434 anything reasonable to do about them, and they tended to spam logs
16435 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
16436 - Downgrade path-bias warning messages to "info". We'll try to get
16437 them working better in 0.2.4. Add internal circuit construction
16438 state to protect against the noisy warn message "Unexpectedly high
16439 circuit_successes". Also add some additional rate-limited notice
16440 messages to help determine the root cause of the warn. Fixes bug
16441 6475. Bugfix against 0.2.3.17-beta.
16442 - Move log message when unable to find a microdesc in a routerstatus
16443 entry to parse time. Previously we'd spam this warning every time
16444 we tried to figure out which microdescriptors to download. Fixes
16445 the third piece of bug 6404; fix on 0.2.3.18-rc.
16448 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
16449 change when the authority is deciding whether to accept a newly
16450 uploaded descriptor. Implements ticket 6423.
16451 - Add missing documentation for consensus and microdesc files.
16452 Resolves ticket 6732.
16455 Changes in version 0.2.2.38 - 2012-08-12
16456 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
16457 attack that could in theory leak path information.
16460 - Avoid an uninitialized memory read when reading a vote or consensus
16461 document that has an unrecognized flavor name. This read could
16462 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
16463 - Try to leak less information about what relays a client is
16464 choosing to a side-channel attacker. Previously, a Tor client would
16465 stop iterating through the list of available relays as soon as it
16466 had chosen one, thus finishing a little earlier when it picked
16467 a router earlier in the list. If an attacker can recover this
16468 timing information (nontrivial but not proven to be impossible),
16469 they could learn some coarse-grained information about which relays
16470 a client was picking (middle nodes in particular are likelier to
16471 be affected than exits). The timing attack might be mitigated by
16472 other factors (see bug 6537 for some discussion), but it's best
16473 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
16476 Changes in version 0.2.3.20-rc - 2012-08-05
16477 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
16478 series. It fixes a pair of code security bugs and a potential anonymity
16479 issue, updates our RPM spec files, and cleans up other smaller issues.
16482 - Avoid read-from-freed-memory and double-free bugs that could occur
16483 when a DNS request fails while launching it. Fixes bug 6480;
16484 bugfix on 0.2.0.1-alpha.
16485 - Avoid an uninitialized memory read when reading a vote or consensus
16486 document that has an unrecognized flavor name. This read could
16487 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
16488 - Try to leak less information about what relays a client is
16489 choosing to a side-channel attacker. Previously, a Tor client would
16490 stop iterating through the list of available relays as soon as it
16491 had chosen one, thus finishing a little earlier when it picked
16492 a router earlier in the list. If an attacker can recover this
16493 timing information (nontrivial but not proven to be impossible),
16494 they could learn some coarse-grained information about which relays
16495 a client was picking (middle nodes in particular are likelier to
16496 be affected than exits). The timing attack might be mitigated by
16497 other factors (see bug 6537 for some discussion), but it's best
16498 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
16501 - Try to make the warning when giving an obsolete SOCKSListenAddress
16502 a little more useful.
16503 - Terminate active server managed proxies if Tor stops being a
16504 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
16505 - Provide a better error message about possible OSX Asciidoc failure
16506 reasons. Fixes bug 6436.
16507 - Warn when Tor is configured to use accounting in a way that can
16508 link a hidden service to some other hidden service or public
16509 address. Resolves ticket 6490.
16512 - Check return value of fputs() when writing authority certificate
16513 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
16514 - Ignore ServerTransportPlugin lines when Tor is not configured as
16515 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
16516 - When disabling guards for having too high a proportion of failed
16517 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
16521 - Update our default RPM spec files to work with mock and rpmbuild
16522 on RHEL/Fedora. They have an updated set of dependencies and
16523 conflicts, a fix for an ancient typo when creating the "_tor"
16524 user, and better instructions. Thanks to Ondrej Mikle for the
16525 patch series. Fixes bug 6043.
16528 - Make it possible to set the TestingTorNetwork configuration
16529 option using AlternateDirAuthority and AlternateBridgeAuthority
16530 as an alternative to setting DirServer. Addresses ticket 6377.
16533 - Clarify the documentation for the Alternate*Authority options.
16535 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
16537 o Code simplification and refactoring:
16538 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
16539 10 lines. Also, don't nest them. Doing so in the past has
16540 led to hard-to-debug code. The new style is to use the
16541 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
16544 Changes in version 0.2.3.19-rc - 2012-07-06
16545 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
16546 series. It fixes the compile on Windows, reverts to a GeoIP database
16547 that isn't as broken, and fixes a flow control bug that has been around
16548 since the beginning of Tor.
16551 - Fix a bug handling SENDME cells on nonexistent streams that could
16552 result in bizarre window values. Report and patch contributed
16553 pseudonymously. Fixes part of bug 6271. This bug was introduced
16554 before the first Tor release, in svn commit r152.
16555 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
16556 June 2012 database, Maxmind marked many Tor relays as country "A1",
16557 which will cause risky behavior for clients that set EntryNodes
16558 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
16559 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
16560 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
16563 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
16564 bugfix on 0.2.1.10-alpha.
16567 Changes in version 0.2.3.18-rc - 2012-06-28
16568 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
16569 series. It fixes a few smaller bugs, but generally appears stable.
16570 Please test it and let us know whether it is!
16573 - Allow wildcarded mapaddress targets to be specified on the
16574 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
16575 - Make our linker option detection code more robust against linkers
16576 such as on FreeBSD 8, where a bad combination of options completes
16577 successfully but makes an unrunnable binary. Fixes bug 6173;
16578 bugfix on 0.2.3.17-beta.
16580 o Minor bugfixes (on 0.2.2.x and earlier):
16581 - Avoid a false positive in the util/threads unit test by increasing
16582 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
16583 - Replace "Sending publish request" log messages with "Launching
16584 upload", so that they no longer confusingly imply that we're
16585 sending something to a directory we might not even be connected
16586 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
16587 - Make sure to set *socket_error in all error cases in
16588 connection_connect(), so it can't produce a warning about
16589 errno being zero from errno_to_orconn_end_reason(). Bugfix on
16590 0.2.1.1-alpha; resolves ticket 6028.
16591 - Downgrade "Got a certificate, but we already have it" log messages
16592 from warning to info, except when we're a dirauth. Fixes bug 5238;
16593 bugfix on 0.2.1.7-alpha.
16594 - When checking for requested signatures on the latest consensus
16595 before serving it to a client, make sure to check the right
16596 consensus flavor. Bugfix on 0.2.2.6-alpha.
16597 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
16598 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
16600 o Minor bugfixes (on 0.2.3.x):
16601 - Make format_helper_exit_status() avoid unnecessary space padding
16602 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
16604 - Downgrade a message about cleaning the microdescriptor cache to
16605 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
16606 - Log a BUG message at severity INFO if we have a networkstatus with
16607 a missing entry for some microdescriptor. Continues on a patch
16609 - Improve the log message when a managed proxy fails to launch. Fixes
16610 bug 5099; bugfix on 0.2.3.6-alpha.
16611 - Don't do DNS lookups when parsing corrupted managed proxy protocol
16612 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
16613 - When formatting wildcarded address mappings for the controller,
16614 be sure to include "*." as appropriate. Partially fixes bug 6244;
16615 bugfix on 0.2.3.9-alpha.
16616 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
16617 Bugfix on 0.2.3.13-alpha.
16618 - Stop logging messages about running with circuit timeout learning
16619 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
16620 - Disable a spurious warning about reading on a marked and flushing
16621 connection. We shouldn't be doing that, but apparently we
16622 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
16623 - Fix a bug that stopped AllowDotExit from working on addresses
16624 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
16627 o Code simplification, refactoring, unit tests:
16628 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
16629 Libevent's notion of cached time when possible.
16630 - Remove duplicate code for invoking getrlimit() from control.c.
16631 - Add a unit test for the environment_variable_names_equal function.
16634 - Document the --defaults-torrc option, and the new (in 0.2.3)
16635 semantics for overriding, extending, and clearing lists of
16636 options. Closes bug 4748.
16639 Changes in version 0.2.3.17-beta - 2012-06-15
16640 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
16641 gets our TLS handshake back on track for being able to blend in with
16642 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
16643 with Vidalia, and otherwise continues to get us closer to a release
16647 - Enable gcc and ld hardening by default. Resolves ticket 5210.
16648 - Update TLS cipher list to match Firefox 8 and later. Resolves
16650 - Implement the client side of proposal 198: remove support for
16651 clients falsely claiming to support standard ciphersuites that
16652 they can actually provide. As of modern OpenSSL versions, it's not
16653 necessary to fake any standard ciphersuite, and doing so prevents
16654 us from using better ciphersuites in the future, since servers
16655 can't know whether an advertised ciphersuite is really supported or
16656 not. Some hosts -- notably, ones with very old versions of OpenSSL
16657 or where OpenSSL has been built with ECC disabled -- will stand
16658 out because of this change; TBB users should not be affected.
16661 - Change the default value for DynamicDHGroups (introduced in
16662 0.2.3.9-alpha) to 0. This feature can make Tor relays less
16663 identifiable by their use of the mod_ssl DH group, but at
16664 the cost of some usability (#4721) and bridge tracing (#6087)
16665 regressions. Resolves ticket 5598.
16666 - Send a CRLF at the end of each STATUS_* control protocol event. This
16667 bug tickled a bug in Vidalia which would make it freeze. Fixes
16668 bug 6094; bugfix on 0.2.3.16-alpha.
16671 - Disable writing on marked-for-close connections when they are
16672 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
16673 bug 5263; bugfix on 0.0.2pre13, where we first added a special
16674 case for flushing marked connections.
16675 - Detect SSL handshake even when the initial attempt to write the
16676 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
16677 - Change the AllowDotExit rules so they should actually work.
16678 We now enforce AllowDotExit only immediately after receiving an
16679 address via SOCKS or DNSPort: other sources are free to provide
16680 .exit addresses after the resolution occurs. Fixes bug 3940;
16681 bugfix on 0.2.2.1-alpha.
16682 - Fix a (harmless) integer overflow in cell statistics reported by
16683 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
16684 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
16685 right places and never depends on the consensus parameters or
16686 computes adaptive timeouts when it is disabled. Fixes bug 5049;
16687 bugfix on 0.2.2.14-alpha.
16688 - When building Tor on Windows with -DUNICODE (not default), ensure
16689 that error messages, filenames, and DNS server names are always
16690 NUL-terminated when we convert them to a single-byte encoding.
16691 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
16692 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
16693 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
16694 - Fix an edge case where TestingTorNetwork is set but the authorities
16695 and relays all have an uptime of zero, where the private Tor network
16696 could briefly lack support for hidden services. Fixes bug 3886;
16697 bugfix on 0.2.2.18-alpha.
16698 - Correct the manpage's descriptions for the default values of
16699 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
16701 - Fix the documentation for the --hush and --quiet command line
16702 options, which changed their behavior back in 0.2.3.3-alpha.
16703 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
16707 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
16708 more information to it, so that we can track it down in case it
16709 returns again. Mitigates bug 5235.
16710 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
16711 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
16712 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
16713 - Warn the user when HTTPProxy, but no other proxy type, is
16714 configured. This can cause surprising behavior: it doesn't send
16715 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
16716 directory traffic only. Resolves ticket 4663.
16717 - Issue a notice if a guard completes less than 40% of your circuits.
16718 Threshold is configurable by torrc option PathBiasNoticeRate and
16719 consensus parameter pb_noticepct. There is additional, off-by-
16720 default code to disable guards which fail too many circuits.
16721 Addresses ticket 5458.
16722 - Update to the June 6 2012 Maxmind GeoLite Country database.
16724 o Code simplifications and refactoring:
16725 - Remove validate_pluggable_transports_config(): its warning
16726 message is now handled by connection_or_connect().
16729 Changes in version 0.2.2.37 - 2012-06-06
16730 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
16731 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
16735 - Work around a bug in OpenSSL that broke renegotiation with TLS
16736 1.1 and TLS 1.2. Without this workaround, all attempts to speak
16737 the v2 Tor connection protocol when both sides were using OpenSSL
16738 1.0.1 would fail. Resolves ticket 6033.
16739 - When waiting for a client to renegotiate, don't allow it to add
16740 any bytes to the input buffer. This fixes a potential DoS issue.
16741 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
16742 - Fix an edge case where if we fetch or publish a hidden service
16743 descriptor, we might build a 4-hop circuit and then use that circuit
16744 for exiting afterwards -- even if the new last hop doesn't obey our
16745 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
16748 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
16749 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
16752 - Tell GCC and Clang to check for any errors in format strings passed
16753 to the tor_v*(print|scan)f functions.
16756 Changes in version 0.2.3.16-alpha - 2012-06-05
16757 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
16758 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
16759 currently). It also fixes a variety of smaller bugs and other cleanups
16760 that get us closer to a release candidate.
16762 o Major bugfixes (general):
16763 - Work around a bug in OpenSSL that broke renegotiation with TLS
16764 1.1 and TLS 1.2. Without this workaround, all attempts to speak
16765 the v2 Tor connection protocol when both sides were using OpenSSL
16766 1.0.1 would fail. Resolves ticket 6033.
16767 - When waiting for a client to renegotiate, don't allow it to add
16768 any bytes to the input buffer. This fixes a potential DoS issue.
16769 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
16770 - Pass correct OR address to managed proxies (like obfsproxy),
16771 even when ORListenAddress is used. Fixes bug 4865; bugfix on
16773 - The advertised platform of a router now includes only its operating
16774 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
16775 service pack level (for Windows) or its CPU architecture (for Unix).
16776 We also no longer include the "git-XYZ" tag in the version. Resolves
16779 o Major bugfixes (clients):
16780 - If we are unable to find any exit that supports our predicted ports,
16781 stop calling them predicted, so that we don't loop and build
16782 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
16783 which introduced predicted ports.
16784 - Fix an edge case where if we fetch or publish a hidden service
16785 descriptor, we might build a 4-hop circuit and then use that circuit
16786 for exiting afterwards -- even if the new last hop doesn't obey our
16787 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
16788 - Check at each new consensus whether our entry guards were picked
16789 long enough ago that we should rotate them. Previously, we only
16790 did this check at startup, which could lead to us holding a guard
16791 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
16792 - When fetching a bridge descriptor from a bridge authority,
16793 always do so anonymously, whether we have been able to open
16794 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
16795 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
16796 but we'll need to wait for bug 6010 before it's actually usable.
16798 o Major bugfixes (directory authorities):
16799 - When computing weight parameters, behave more robustly in the
16800 presence of a bad bwweightscale value. Previously, the authorities
16801 would crash if they agreed on a sufficiently broken weight_scale
16802 value: now, they use a reasonable default and carry on. Partial
16803 fix for 5786; bugfix on 0.2.2.17-alpha.
16804 - Check more thoroughly to prevent a rogue authority from
16805 double-voting on any consensus directory parameter. Previously,
16806 authorities would crash in this case if the total number of
16807 votes for any parameter exceeded the number of active voters,
16808 but would let it pass otherwise. Partial fix for bug 5786; bugfix
16812 - Rate-limit log messages when asked to connect anonymously to
16813 a private address. When these hit, they tended to hit fast and
16814 often. Also, don't bother trying to connect to addresses that we
16815 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
16816 reply makes us think we have been lied to, even when the address the
16817 client tried to connect to was "localhost." Resolves ticket 2822.
16818 - Allow packagers to insert an extra string in server descriptor
16819 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
16820 Resolves the rest of ticket 2988.
16821 - Raise the threshold of server descriptors needed (75%) and exit
16822 server descriptors needed (50%) before we will declare ourselves
16823 bootstrapped. This will make clients start building circuits a
16824 little later, but makes the initially constructed circuits less
16825 skewed and less in conflict with further directory fetches. Fixes
16827 - Close any connection that sends unrecognized junk before the
16828 handshake. Solves an issue noted in bug 4369.
16829 - Improve log messages about managed transports. Resolves ticket 5070.
16830 - Tag a bridge's descriptor as "never to be sent unencrypted".
16831 This shouldn't matter, since bridges don't open non-anonymous
16832 connections to the bridge authority and don't allow unencrypted
16833 directory connections from clients, but we might as well make
16834 sure. Closes bug 5139.
16835 - Expose our view of whether we have gone dormant to the controller,
16836 via a new "GETINFO dormant" value. Torbutton and other controllers
16837 can use this to avoid doing periodic requests through Tor while
16838 it's dormant (bug 4718). Fixes bug 5954.
16839 - Tell GCC and Clang to check for any errors in format strings passed
16840 to the tor_v*(print|scan)f functions.
16841 - Update to the May 1 2012 Maxmind GeoLite Country database.
16843 o Minor bugfixes (already included in 0.2.2.36):
16844 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
16845 Fixes bug 5346; bugfix on 0.0.8pre3.
16846 - Correct parsing of certain date types in parse_http_time().
16847 Without this patch, If-Modified-Since would behave
16848 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
16849 Esteban Manchado Velázques.
16850 - Make our number-parsing functions always treat too-large values
16851 as an error, even when those values exceed the width of the
16852 underlying type. Previously, if the caller provided these
16853 functions with minima or maxima set to the extreme values of the
16854 underlying integer type, these functions would return those
16855 values on overflow rather than treating overflow as an error.
16856 Fixes part of bug 5786; bugfix on 0.0.9.
16857 - If we hit the error case where routerlist_insert() replaces an
16858 existing (old) server descriptor, make sure to remove that
16859 server descriptor from the old_routers list. Fix related to bug
16860 1776. Bugfix on 0.2.2.18-alpha.
16861 - Clarify the behavior of MaxCircuitDirtiness with hidden service
16862 circuits. Fixes issue 5259.
16864 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
16865 - Prevent a null-pointer dereference when receiving a data cell
16866 for a nonexistent stream when the circuit in question has an
16867 empty deliver window. We don't believe this is triggerable,
16868 since we don't currently allow deliver windows to become empty,
16869 but the logic is tricky enough that it's better to make the code
16870 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
16871 - Fix a memory leak when trying to launch a DNS request when the
16872 network is disabled or the nameservers are unconfigurable. Fixes
16873 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
16874 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
16875 - Don't hold a Windows file handle open for every file mapping;
16876 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
16878 - Avoid O(n^2) performance characteristics when parsing a large
16879 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
16880 - Format more doubles with %f, not %lf. Patch from grarpamp to make
16881 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
16883 - Make our replacement implementation of strtok_r() compatible with
16884 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
16885 bugfix on 0.2.2.1-alpha.
16886 - Fix a NULL-pointer dereference on a badly formed
16887 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
16888 bugfix on 0.2.2.9-alpha.
16889 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
16890 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
16891 - Defensively refactor rend_mid_rendezvous() so that protocol
16892 violations and length checks happen in the beginning. Fixes
16894 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
16895 that IPv6 stuff will compile on MSVC, and compilation issues
16896 will be easier to track down. Fixes bug 5861.
16898 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
16899 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
16900 resource exhaustion, so that clients can adjust their load to
16901 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
16902 started using END_STREAM_REASON_RESOURCELIMIT.
16903 - Don't check for whether the address we're using for outbound
16904 connections has changed until after the outbound connection has
16905 completed. On Windows, getsockname() doesn't succeed until the
16906 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
16907 - If the configuration tries to set MyFamily on a bridge, refuse to
16908 do so, and warn about the security implications. Fixes bug 4657;
16909 bugfix on 0.2.0.3-alpha.
16910 - If the client fails to set a reasonable set of ciphersuites
16911 during its v2 handshake renegotiation, allow the renegotiation to
16912 continue nevertheless (i.e. send all the required certificates).
16913 Fixes bug 4591; bugfix on 0.2.0.20-rc.
16914 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
16915 option is set to 0 (which Vidalia version 0.2.16 now does when
16916 a SAVECONF attempt fails), perform other actions that SIGHUP
16917 usually causes (like reopening the logs). Fixes bug 5095; bugfix
16919 - If we fail to write a microdescriptor to the disk cache, do not
16920 continue replacing the old microdescriptor file. Fixes bug 2954;
16921 bugfix on 0.2.2.6-alpha.
16922 - Exit nodes don't need to fetch certificates for authorities that
16923 they don't recognize; only directory authorities, bridges,
16924 and caches need to do that. Fixes part of bug 2297; bugfix on
16926 - Correctly handle checking the permissions on the parent
16927 directory of a control socket in the root directory. Bug found
16928 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
16930 - When told to add a bridge with the same digest as a preexisting
16931 bridge but a different addr:port, change the addr:port as
16932 requested. Previously we would not notice the change. Fixes half
16933 of bug 5603; fix on 0.2.2.26-beta.
16934 - End AUTHCHALLENGE error messages (in the control protocol) with
16935 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
16937 o Minor bugfixes (on 0.2.3.x):
16938 - Turn an assertion (that the number of handshakes received as a
16939 server is not < 1) into a warning. Fixes bug 4873; bugfix on
16941 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
16942 we had reversed them when the answer was cached.) Fixes bug
16943 5723; bugfix on 0.2.3.1-alpha.
16944 - Work correctly on Linux systems with accept4 support advertised in
16945 their headers, but without accept4 support in the kernel. Fix
16946 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
16947 - When told to add a bridge with the same addr:port as a preexisting
16948 bridge but a different transport, change the transport as
16949 requested. Previously we would not notice the change. Fixes half
16950 of bug 5603; fix on 0.2.3.2-alpha.
16951 - Avoid a "double-reply" warning when replying to a SOCKS request
16952 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
16953 bugfix on 0.2.3.4-alpha.
16954 - Fix a bug where a bridge authority crashes if it has seen no
16955 directory requests when it's time to write statistics to disk.
16956 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
16958 - Don't try to open non-control listeners when DisableNetwork is set.
16959 Previously, we'd open all listeners, then immediately close them.
16960 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
16961 - Don't abort the managed proxy protocol if the managed proxy
16962 sends us an unrecognized line; ignore it instead. Fixes bug
16963 5910; bugfix on 0.2.3.9-alpha.
16964 - Fix a compile warning in crypto.c when compiling with clang 3.1.
16965 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
16966 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
16967 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
16968 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
16969 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
16970 - Resolve numerous small warnings and build issues with MSVC. Resolves
16973 o Documentation fixes:
16974 - Improve the manual's documentation for the NT Service command-line
16975 options. Addresses ticket 3964.
16976 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
16977 - Document the changes to the ORPort and DirPort options, and the
16978 fact that {OR/Dir}ListenAddress is now unnecessary (and
16979 therefore deprecated). Resolves ticket 5597.
16982 - Remove the torrc.bridge file: we don't use it for anything, and
16983 it had become badly desynchronized from torrc.sample. Resolves
16987 Changes in version 0.2.2.36 - 2012-05-24
16988 Tor 0.2.2.36 updates the addresses for two of the eight directory
16989 authorities, fixes some potential anonymity and security issues,
16990 and fixes several crash bugs.
16992 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
16993 known flaws, and nobody should be using them. You should upgrade. If
16994 you're using a Linux or BSD and its packages are obsolete, stop using
16995 those packages and upgrade anyway.
16997 o Directory authority changes:
16998 - Change IP address for maatuska (v3 directory authority).
16999 - Change IP address for ides (v3 directory authority), and rename
17003 - When building or running with any version of OpenSSL earlier
17004 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
17005 versions have a bug (CVE-2011-4576) in which their block cipher
17006 padding includes uninitialized data, potentially leaking sensitive
17007 information to any peer with whom they make a SSLv3 connection. Tor
17008 does not use SSL v3 by default, but a hostile client or server
17009 could force an SSLv3 connection in order to gain information that
17010 they shouldn't have been able to get. The best solution here is to
17011 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
17012 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
17013 to make sure that the bug can't happen.
17014 - Never use a bridge or a controller-supplied node as an exit, even
17015 if its exit policy allows it. Found by wanoskarnet. Fixes bug
17016 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
17017 and 0.2.0.3-alpha (for bridge-purpose descriptors).
17018 - Only build circuits if we have a sufficient threshold of the total
17019 descriptors that are marked in the consensus with the "Exit"
17020 flag. This mitigates an attack proposed by wanoskarnet, in which
17021 all of a client's bridges collude to restrict the exit nodes that
17022 the client knows about. Fixes bug 5343.
17023 - Provide controllers with a safer way to implement the cookie
17024 authentication mechanism. With the old method, if another locally
17025 running program could convince a controller that it was the Tor
17026 process, then that program could trick the controller into telling
17027 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
17028 authentication method uses a challenge-response approach to prevent
17029 this attack. Fixes bug 5185; implements proposal 193.
17032 - Avoid logging uninitialized data when unable to decode a hidden
17033 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
17034 - Avoid a client-side assertion failure when receiving an INTRODUCE2
17035 cell on a general purpose circuit. Fixes bug 5644; bugfix on
17037 - Fix builds when the path to sed, openssl, or sha1sum contains
17038 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
17040 - Correct our replacements for the timeradd() and timersub() functions
17041 on platforms that lack them (for example, Windows). The timersub()
17042 function is used when expiring circuits, while timeradd() is
17043 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
17044 bugfix on 0.2.2.24-alpha.
17045 - Fix the SOCKET_OK test that we use to tell when socket
17046 creation fails so that it works on Win64. Fixes part of bug 4533;
17047 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
17050 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
17051 Fixes bug 5346; bugfix on 0.0.8pre3.
17052 - Make our number-parsing functions always treat too-large values
17053 as an error, even when those values exceed the width of the
17054 underlying type. Previously, if the caller provided these
17055 functions with minima or maxima set to the extreme values of the
17056 underlying integer type, these functions would return those
17057 values on overflow rather than treating overflow as an error.
17058 Fixes part of bug 5786; bugfix on 0.0.9.
17059 - Older Linux kernels erroneously respond to strange nmap behavior
17060 by having accept() return successfully with a zero-length
17061 socket. When this happens, just close the connection. Previously,
17062 we would try harder to learn the remote address: but there was
17063 no such remote address to learn, and our method for trying to
17064 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
17065 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
17066 - Correct parsing of certain date types in parse_http_time().
17067 Without this patch, If-Modified-Since would behave
17068 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
17069 Esteban Manchado Velázques.
17070 - Change the BridgePassword feature (part of the "bridge community"
17071 design, which is not yet implemented) to use a time-independent
17072 comparison. The old behavior might have allowed an adversary
17073 to use timing to guess the BridgePassword value. Fixes bug 5543;
17074 bugfix on 0.2.0.14-alpha.
17075 - Detect and reject certain misformed escape sequences in
17076 configuration values. Previously, these values would cause us
17077 to crash if received in a torrc file or over an authenticated
17078 control port. Bug found by Esteban Manchado Velázquez, and
17079 independently by Robert Connolly from Matta Consulting who further
17080 noted that it allows a post-authentication heap overflow. Patch
17081 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
17082 bugfix on 0.2.0.16-alpha.
17083 - Fix a compile warning when using the --enable-openbsd-malloc
17084 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
17085 - During configure, detect when we're building with clang version
17086 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
17087 CFLAGS. clang doesn't support them yet.
17088 - When sending an HTTP/1.1 proxy request, include a Host header.
17089 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
17090 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
17091 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
17092 - If we hit the error case where routerlist_insert() replaces an
17093 existing (old) server descriptor, make sure to remove that
17094 server descriptor from the old_routers list. Fix related to bug
17095 1776. Bugfix on 0.2.2.18-alpha.
17097 o Minor bugfixes (documentation and log messages):
17098 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
17099 Fixes bug 4856; bugfix on Tor 0.0.6.
17100 - Update "ClientOnly" man page entry to explain that there isn't
17101 really any point to messing with it. Resolves ticket 5005.
17102 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
17103 directory authority option (introduced in Tor 0.2.2.34).
17104 - Downgrade the "We're missing a certificate" message from notice
17105 to info: people kept mistaking it for a real problem, whereas it
17106 is seldom the problem even when we are failing to bootstrap. Fixes
17107 bug 5067; bugfix on 0.2.0.10-alpha.
17108 - Correctly spell "connect" in a log message on failure to create a
17109 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
17110 - Clarify the behavior of MaxCircuitDirtiness with hidden service
17111 circuits. Fixes issue 5259.
17114 - Directory authorities now reject versions of Tor older than
17115 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
17116 inclusive. These versions accounted for only a small fraction of
17117 the Tor network, and have numerous known security issues. Resolves
17119 - Update to the May 1 2012 Maxmind GeoLite Country database.
17122 - When sending or relaying a RELAY_EARLY cell, we used to convert
17123 it to a RELAY cell if the connection was using the v1 link
17124 protocol. This was a workaround for older versions of Tor, which
17125 didn't handle RELAY_EARLY cells properly. Now that all supported
17126 versions can handle RELAY_EARLY cells, and now that we're enforcing
17127 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
17128 remove this workaround. Addresses bug 4786.
17131 Changes in version 0.2.3.15-alpha - 2012-04-30
17132 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
17133 the development branch build on Windows again.
17135 o Minor bugfixes (on 0.2.2.x and earlier):
17136 - Make sure that there are no unhandled pending TLS errors before
17137 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
17138 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
17139 Bugfix on 0.1.0.5-rc; fixes bug 4528.
17140 - Fix an assert that directory authorities could trigger on sighup
17141 during some configuration state transitions. We now don't treat
17142 it as a fatal error when the new descriptor we just generated in
17143 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
17144 - After we pick a directory mirror, we would refuse to use it if
17145 it's in our ExcludeExitNodes list, resulting in mysterious failures
17146 to bootstrap for people who just wanted to avoid exiting from
17147 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
17148 - When building with --enable-static-tor on OpenBSD, do not
17149 erroneously attempt to link -lrt. Fixes bug 5103.
17151 o Minor bugfixes (on 0.2.3.x):
17152 - When Tor is built with kernel headers from a recent (last few
17153 years) Linux kernel, do not fail to run on older (pre-2.6.28
17154 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
17155 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
17156 and 0.2.3.12-alpha.
17157 - Fix compilation with miniupnpc version 1.6; patch from
17158 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
17159 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
17160 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
17161 - Fix compilation on platforms without unistd.h, or where environ
17162 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
17165 - Directory authorities are now a little more lenient at accepting
17166 older router descriptors, or newer router descriptors that don't
17167 make big changes. This should help ameliorate past and future
17168 issues where routers think they have uploaded valid descriptors,
17169 but the authorities don't think so. Fix for ticket 2479.
17170 - Make the code that clients use to detect an address change be
17171 IPv6-aware, so that it won't fill clients' logs with error
17172 messages when trying to get the IPv4 address of an IPv6
17173 connection. Implements ticket 5537.
17175 o Removed features:
17176 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
17177 authorities needed to use it for a while to keep the network working
17178 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
17179 that was six months ago. As of now, it should no longer be needed
17183 Changes in version 0.2.3.14-alpha - 2012-04-23
17184 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
17185 candidate. It also dramatically speeds up AES: fast relays should
17186 consider switching to the newer OpenSSL library.
17188 o Directory authority changes:
17189 - Change IP address for ides (v3 directory authority), and rename
17193 - Avoid logging uninitialized data when unable to decode a hidden
17194 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
17195 - Avoid a client-side assertion failure when receiving an INTRODUCE2
17196 cell on a general purpose circuit. Fixes bug 5644; bugfix on
17198 - If authorities are unable to get a v2 consensus document from other
17199 directory authorities, they no longer fall back to fetching
17200 them from regular directory caches. Fixes bug 5635; bugfix on
17201 0.2.2.26-beta, where routers stopped downloading v2 consensus
17202 documents entirely.
17203 - When we start a Tor client with a normal consensus already cached,
17204 be willing to download a microdescriptor consensus. Fixes bug 4011;
17205 fix on 0.2.3.1-alpha.
17207 o Major features (performance):
17208 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
17209 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
17210 vectorized AES implementations as appropriate. These can be much,
17211 much faster than other AES implementations.
17213 o Minor bugfixes (0.2.2.x and earlier):
17214 - Don't launch more than 10 service-side introduction-point circuits
17215 for a hidden service in five minutes. Previously, we would consider
17216 launching more introduction-point circuits if at least one second
17217 had passed without any introduction-point circuits failing. Fixes
17218 bug 4607; bugfix on 0.0.7pre1.
17219 - Change the BridgePassword feature (part of the "bridge community"
17220 design, which is not yet implemented) to use a time-independent
17221 comparison. The old behavior might have allowed an adversary
17222 to use timing to guess the BridgePassword value. Fixes bug 5543;
17223 bugfix on 0.2.0.14-alpha.
17224 - Enforce correct return behavior of tor_vsscanf() when the '%%'
17225 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
17226 - When sending an HTTP/1.1 proxy request, include a Host header.
17227 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
17228 - Don't log that we have "decided to publish new relay descriptor"
17229 unless we are actually publishing a descriptor. Fixes bug 3942;
17230 bugfix on 0.2.2.28-beta.
17232 o Minor bugfixes (0.2.3.x):
17233 - Fix a bug where a bridge authority crashes (on a failed assert)
17234 if it has seen no directory requests when it's time to write
17235 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
17236 - Fix bug stomping on ORPort option NoListen and ignoring option
17237 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
17238 - In the testsuite, provide a large enough buffer in the tor_sscanf
17239 unit test. Otherwise we'd overrun that buffer and crash during
17240 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
17242 - Make sure we create the keys directory if it doesn't exist and we're
17243 about to store the dynamic Diffie-Hellman parameters. Fixes bug
17244 5572; bugfix on 0.2.3.13-alpha.
17245 - Fix a small memory leak when trying to decode incorrect base16
17246 authenticator during SAFECOOKIE authentication. Found by
17247 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
17250 - Add more information to a log statement that might help track down
17251 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
17252 non-IP address" messages (or any Bug messages, for that matter!),
17253 please let us know about it.
17254 - Relays now understand an IPv6 address when they get one from a
17255 directory server. Resolves ticket 4875.
17256 - Resolve IPv6 addresses in bridge and entry statistics to country
17257 code "??" which means we at least count them. Resolves ticket 5053;
17258 improves on 0.2.3.9-alpha.
17259 - Update to the April 3 2012 Maxmind GeoLite Country database.
17260 - Begin a doc/state-contents.txt file to explain the contents of
17261 the Tor state file. Fixes bug 2987.
17263 o Default torrc changes:
17264 - Stop listing "socksport 9050" in torrc.sample. We open a socks
17265 port on 9050 by default anyway, so this should not change anything
17267 - Stop mentioning the deprecated *ListenAddress options in
17268 torrc.sample. Fixes bug 5438.
17269 - Document unit of bandwidth related options in sample torrc.
17272 o Removed features:
17273 - The "torify" script no longer supports the "tsocks" socksifier
17274 tool, since tsocks doesn't support DNS and UDP right for Tor.
17275 Everyone should be using torsocks instead. Fixes bugs 3530 and
17276 5180. Based on a patch by "ugh".
17278 o Code refactoring:
17279 - Change the symmetric cipher interface so that creating and
17280 initializing a stream cipher are no longer separate functions.
17281 - Remove all internal support for unpadded RSA. We never used it, and
17282 it would be a bad idea to start.
17285 Changes in version 0.2.3.13-alpha - 2012-03-26
17286 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
17287 in managed pluggable transports, as well as providing other cleanups
17288 that get us closer to a release candidate.
17290 o Directory authority changes:
17291 - Change IP address for maatuska (v3 directory authority).
17294 - Provide controllers with a safer way to implement the cookie
17295 authentication mechanism. With the old method, if another locally
17296 running program could convince a controller that it was the Tor
17297 process, then that program could trick the controller into telling
17298 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
17299 authentication method uses a challenge-response approach to prevent
17300 this attack. Fixes bug 5185, implements proposal 193.
17301 - Never use a bridge or a controller-supplied node as an exit, even
17302 if its exit policy allows it. Found by wanoskarnet. Fixes bug
17303 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
17304 and 0.2.0.3-alpha (for bridge-purpose descriptors).
17305 - Only build circuits if we have a sufficient threshold of the total
17306 descriptors that are marked in the consensus with the "Exit"
17307 flag. This mitigates an attack proposed by wanoskarnet, in which
17308 all of a client's bridges collude to restrict the exit nodes that
17309 the client knows about. Fixes bug 5343.
17311 o Major bugfixes (on Tor 0.2.3.x):
17312 - Avoid an assert when managed proxies like obfsproxy are configured,
17313 and we receive HUP signals or setconf attempts too rapidly. This
17314 situation happens most commonly when Vidalia tries to attach to
17315 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
17316 bugfix on 0.2.3.6-alpha.
17317 - Fix a relay-side pluggable transports bug where managed proxies were
17318 unreachable from the Internet, because Tor asked them to bind on
17319 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
17320 - Stop discarding command-line arguments when TestingTorNetwork
17321 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
17322 0.2.3.9-alpha, where task 4552 added support for two layers of
17324 - Resume allowing the unit tests to run in gdb. This was accidentally
17325 made impossible when the DisableDebuggerAttachment option was
17326 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
17327 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
17328 0.2.3.11-alpha. Reported by Anthony G. Basile.
17330 o Minor bugfixes (on 0.2.2.x and earlier):
17331 - Ensure we don't cannibalize circuits that are longer than three hops
17332 already, so we don't end up making circuits with 5 or more
17333 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
17334 0.1.0.1-rc which introduced cannibalization.
17335 - Detect and reject certain misformed escape sequences in
17336 configuration values. Previously, these values would cause us
17337 to crash if received in a torrc file or over an authenticated
17338 control port. Bug found by Esteban Manchado Velázquez, and
17339 independently by Robert Connolly from Matta Consulting who further
17340 noted that it allows a post-authentication heap overflow. Patch
17341 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
17342 bugfix on 0.2.0.16-alpha.
17343 - Fix a compile warning when using the --enable-openbsd-malloc
17344 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
17345 - Directory caches no longer refuse to clean out descriptors because
17346 of missing v2 networkstatus documents, unless they're configured
17347 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
17348 0.2.2.26-beta. Patch by Daniel Bryg.
17349 - Update to the latest version of the tinytest unit testing framework.
17350 This includes a couple of bugfixes that can be relevant for
17351 running forked unit tests on Windows, and removes all reserved
17354 o Minor bugfixes (on 0.2.3.x):
17355 - On a failed pipe() call, don't leak file descriptors. Fixes bug
17356 4296; bugfix on 0.2.3.1-alpha.
17357 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
17358 until after we have received a CERTS cell. Fixes bug 4361; bugfix
17359 on 0.2.3.6-alpha. Patch by "frosty".
17360 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
17361 option, so that the IP stack doesn't decide to use it for IPv4
17362 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
17363 - Ensure that variables set in Tor's environment cannot override
17364 environment variables that Tor passes to a managed
17365 pluggable-transport proxy. Previously, Tor would pass every
17366 variable in its environment to managed proxies along with the new
17367 ones, in such a way that on many operating systems, the inherited
17368 environment variables would override those which Tor tried to
17369 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
17370 bugfix on 0.2.3.9-alpha for Windows.
17373 - A wide variety of new unit tests by Esteban Manchado Velázquez.
17374 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
17375 - Update to the March 6 2012 Maxmind GeoLite Country database.
17378 Changes in version 0.2.3.12-alpha - 2012-02-13
17379 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
17380 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
17381 when Tor is configured to use a pluggable transport like obfsproxy.
17384 - Fix builds when the path to sed, openssl, or sha1sum contains
17385 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
17387 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
17388 connections. This change should allow busy exit relays to stop
17389 running out of available sockets as quickly. Fixes bug 4950;
17390 bugfix on 0.2.2.26-beta.
17391 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
17392 would ask the bridge for microdescriptors, which are only supported
17393 in 0.2.3.x, and then fail to bootstrap when it didn't get the
17394 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
17395 - Properly set up obfsproxy's environment when in managed mode. The
17396 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
17397 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
17398 5076 and 5082; bugfix on 0.2.3.6-alpha.
17401 - Use the dead_strip option when building Tor on OS X. This reduces
17402 binary size by almost 19% when linking openssl and libevent
17403 statically, which we do for Tor Browser Bundle.
17404 - Fix broken URLs in the sample torrc file, and tell readers about
17405 the OutboundBindAddress, ExitPolicyRejectPrivate, and
17406 PublishServerDescriptor options. Addresses bug 4652.
17407 - Update to the February 7 2012 Maxmind GeoLite Country database.
17410 - Downgrade the "We're missing a certificate" message from notice
17411 to info: people kept mistaking it for a real problem, whereas it
17412 is seldom the problem even when we are failing to bootstrap. Fixes
17413 bug 5067; bugfix on 0.2.0.10-alpha.
17414 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
17415 managed pluggable transport server proxy's environment.
17416 Previously, we would put it there, even though Tor doesn't
17417 implement an 'extended server port' yet, and even though Tor
17418 almost certainly isn't listening at that address. For now, we set
17419 it to an empty string to avoid crashing older obfsproxies. Bugfix
17421 - Log the heartbeat message every HeartbeatPeriod seconds, not every
17422 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
17423 0.2.3.1-alpha. Bug reported by Scott Bennett.
17424 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
17425 bugfix on 0.2.3.11-alpha.
17426 - Update "ClientOnly" man page entry to explain that there isn't
17427 really any point to messing with it. Resolves ticket 5005.
17428 - Use the correct CVE number for CVE-2011-4576 in our comments and
17429 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
17432 o Code simplifications and refactoring:
17433 - Use the _WIN32 macro throughout our code to detect Windows.
17434 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
17438 Changes in version 0.2.3.11-alpha - 2012-01-22
17439 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
17440 the last step of the plan to limit maximum circuit length, includes
17441 a wide variety of hidden service performance and correctness fixes,
17442 works around an OpenSSL security flaw if your distro is too stubborn
17443 to upgrade, and fixes a bunch of smaller issues.
17446 - Now that Tor 0.2.0.x is completely deprecated, enable the final
17447 part of "Proposal 110: Avoiding infinite length circuits" by
17448 refusing all circuit-extend requests that do not use a relay_early
17449 cell. This change helps Tor resist a class of denial-of-service
17450 attacks by limiting the maximum circuit length.
17451 - Adjust the number of introduction points that a hidden service
17452 will try to maintain based on how long its introduction points
17453 remain in use and how many introductions they handle. Fixes
17455 - Try to use system facilities for enumerating local interface
17456 addresses, before falling back to our old approach (which was
17457 binding a UDP socket, and calling getsockname() on it). That
17458 approach was scaring OS X users whose draconian firewall
17459 software warned about binding to UDP sockets, regardless of
17460 whether packets were sent. Now we try to use getifaddrs(),
17461 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
17462 system supports. Resolves ticket 1827.
17464 o Major security workaround:
17465 - When building or running with any version of OpenSSL earlier
17466 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
17467 versions have a bug (CVE-2011-4576) in which their block cipher
17468 padding includes uninitialized data, potentially leaking sensitive
17469 information to any peer with whom they make a SSLv3 connection. Tor
17470 does not use SSL v3 by default, but a hostile client or server
17471 could force an SSLv3 connection in order to gain information that
17472 they shouldn't have been able to get. The best solution here is to
17473 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
17474 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
17475 to make sure that the bug can't happen.
17478 - Fix the SOCKET_OK test that we use to tell when socket
17479 creation fails so that it works on Win64. Fixes part of bug 4533;
17480 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
17481 - Correct our replacements for the timeradd() and timersub() functions
17482 on platforms that lack them (for example, Windows). The timersub()
17483 function is used when expiring circuits, while timeradd() is
17484 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
17485 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
17486 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
17487 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
17488 bug at runtime, not compile time, because some distributions hack
17489 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
17490 on 0.2.3.9-alpha. Found by Pascal.
17492 o Minor features (controller):
17493 - Use absolute path names when reporting the torrc filename in the
17494 control protocol, so a controller can more easily find the torrc
17495 file. Resolves bug 1101.
17496 - Extend the control protocol to report flags that control a circuit's
17497 path selection in CIRC events and in replies to 'GETINFO
17498 circuit-status'. Implements part of ticket 2411.
17499 - Extend the control protocol to report the hidden service address
17500 and current state of a hidden-service-related circuit in CIRC
17501 events and in replies to 'GETINFO circuit-status'. Implements part
17503 - When reporting the path to the cookie file to the controller,
17504 give an absolute path. Resolves ticket 4881.
17505 - Allow controllers to request an event notification whenever a
17506 circuit is cannibalized or its purpose is changed. Implements
17507 part of ticket 3457.
17508 - Include the creation time of a circuit in CIRC and CIRC2
17509 control-port events and the list produced by the 'GETINFO
17510 circuit-status' control-port command.
17512 o Minor features (directory authorities):
17513 - Directory authorities now reject versions of Tor older than
17514 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
17515 inclusive. These versions accounted for only a small fraction of
17516 the Tor network, and have numerous known security issues. Resolves
17518 - Authority operators can now vote for all relays in a given
17519 set of countries to be BadDir/BadExit/Invalid/Rejected.
17520 - Provide two consensus parameters (FastFlagMinThreshold and
17521 FastFlagMaxThreshold) to control the range of allowable bandwidths
17522 for the Fast directory flag. These allow authorities to run
17523 experiments on appropriate requirements for being a "Fast" node.
17524 The AuthDirFastGuarantee config value still applies. Implements
17526 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
17527 directory authority option (introduced in Tor 0.2.2.34).
17529 o Minor features (other):
17530 - Don't disable the DirPort when we cannot exceed our AccountingMax
17531 limit during this interval because the effective bandwidthrate is
17532 low enough. This is useful in a situation where AccountMax is only
17533 used as an additional safeguard or to provide statistics.
17534 - Prepend an informative header to generated dynamic_dh_params files.
17535 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
17536 EntryNodes will have no effect. Resolves issue 2571.
17537 - Log more useful messages when we fail to disable debugger
17539 - Log which authority we're missing votes from when we go to fetch
17540 them from the other auths.
17541 - Log (at debug level) whenever a circuit's purpose is changed.
17542 - Add missing documentation for the MaxClientCircuitsPending,
17543 UseMicrodescriptors, UserspaceIOCPBuffers, and
17544 _UseFilteringSSLBufferevents options, all introduced during
17545 the 0.2.3.x series.
17546 - Update to the January 3 2012 Maxmind GeoLite Country database.
17548 o Minor bugfixes (hidden services):
17549 - Don't close hidden service client circuits which have almost
17550 finished connecting to their destination when they reach
17551 the normal circuit-build timeout. Previously, we would close
17552 introduction circuits which are waiting for an acknowledgement
17553 from the introduction point, and rendezvous circuits which have
17554 been specified in an INTRODUCE1 cell sent to a hidden service,
17555 after the normal CBT. Now, we mark them as 'timed out', and launch
17556 another rendezvous attempt in parallel. This behavior change can
17557 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
17558 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
17559 - Don't close hidden-service-side rendezvous circuits when they
17560 reach the normal circuit-build timeout. This behavior change can
17561 be disabled using the new
17562 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
17563 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
17564 - Make sure we never mark the wrong rendezvous circuit as having
17565 had its introduction cell acknowledged by the introduction-point
17566 relay. Previously, when we received an INTRODUCE_ACK cell on a
17567 client-side hidden-service introduction circuit, we might have
17568 marked a rendezvous circuit other than the one we specified in
17569 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
17570 a warning message and interfered with the hidden service
17571 connection-establishment process. Fixes bug 4759; bugfix on
17572 0.2.3.3-alpha, when we added the stream-isolation feature which
17573 might cause Tor to open multiple rendezvous circuits for the same
17575 - Don't trigger an assertion failure when we mark a new client-side
17576 hidden-service introduction circuit for close during the process
17577 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
17580 o Minor bugfixes (log messages):
17581 - Correctly spell "connect" in a log message on failure to create a
17582 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
17584 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
17585 Fixes bug 4856; bugfix on Tor 0.0.6.
17586 - Fix the log message describing how we work around discovering
17587 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
17588 4837; bugfix on 0.2.2.9-alpha.
17589 - When logging about a disallowed .exit name, do not also call it
17590 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
17592 o Minor bugfixes (build fixes):
17593 - During configure, detect when we're building with clang version
17594 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
17595 CFLAGS. clang doesn't support them yet.
17596 - During configure, search for library containing cos function as
17597 libm lives in libcore on some platforms (BeOS/Haiku). Linking
17598 against libm was hard-coded before. Fixes the first part of bug
17599 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
17601 - Detect attempts to build Tor on (as yet hypothetical) versions
17602 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
17603 fix for bug 4533. Bugfix on 0.2.2.28-beta.
17604 - Preprocessor directives should not be put inside the arguments
17605 of a macro. This would break compilation with GCC releases prior
17606 to version 3.3. We would never recommend such an old GCC version,
17607 but it is apparently required for binary compatibility on some
17608 platforms (namely, certain builds of Haiku). Fixes the other part
17609 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
17612 o Minor bugfixes (other):
17613 - Older Linux kernels erroneously respond to strange nmap behavior
17614 by having accept() return successfully with a zero-length
17615 socket. When this happens, just close the connection. Previously,
17616 we would try harder to learn the remote address: but there was
17617 no such remote address to learn, and our method for trying to
17618 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
17619 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
17620 - Fix null-pointer access that could occur if TLS allocation failed.
17621 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
17622 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
17623 accidentally been reverted.
17624 - Fix our implementation of crypto_random_hostname() so it can't
17625 overflow on ridiculously large inputs. (No Tor version has ever
17626 provided this kind of bad inputs, but let's be correct in depth.)
17627 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
17628 - Find more places in the code that should have been testing for
17629 invalid sockets using the SOCKET_OK macro. Required for a fix
17630 for bug 4533. Bugfix on 0.2.2.28-beta.
17631 - Fix an assertion failure when, while running with bufferevents, a
17632 connection finishes connecting after it is marked for close, but
17633 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
17634 - test_util_spawn_background_ok() hardcoded the expected value
17635 for ENOENT to 2. This isn't portable as error numbers are
17636 platform specific, and particularly the hurd has ENOENT at
17637 0x40000002. Construct expected string at runtime, using the correct
17638 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
17639 - Reject attempts to disable DisableDebuggerAttachment while Tor is
17640 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
17641 - Use an appropriate-width type for sockets in tor-fw-helper on
17642 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
17645 - When sending or relaying a RELAY_EARLY cell, we used to convert
17646 it to a RELAY cell if the connection was using the v1 link
17647 protocol. This was a workaround for older versions of Tor, which
17648 didn't handle RELAY_EARLY cells properly. Now that all supported
17649 versions can handle RELAY_EARLY cells, and now that we're enforcing
17650 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
17651 remove this workaround. Addresses bug 4786.
17653 o Code simplifications and refactoring:
17654 - Use OpenSSL's built-in SSL_state_string_long() instead of our
17655 own homebrewed ssl_state_to_string() replacement. Patch from
17656 Emile Snyder. Fixes bug 4653.
17657 - Use macros to indicate OpenSSL versions, so we don't need to worry
17658 about accidental hexadecimal bit shifts.
17659 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
17661 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
17662 - Use the smartlist_add_asprintf() alias more consistently.
17663 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
17664 invalid value, rather than just -1.
17665 - Rename a handful of old identifiers, mostly related to crypto
17666 structures and crypto functions. By convention, our "create an
17667 object" functions are called "type_new()", our "free an object"
17668 functions are called "type_free()", and our types indicate that
17669 they are types only with a final "_t". But a handful of older
17670 types and functions broke these rules, with function names like
17671 "type_create" or "subsystem_op_type", or with type names like
17675 Changes in version 0.2.3.10-alpha - 2011-12-16
17676 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
17677 Tor's buffers code. Absolutely everybody should upgrade.
17679 The bug relied on an incorrect calculation when making data continuous
17680 in one of our IO buffers, if the first chunk of the buffer was
17681 misaligned by just the wrong amount. The miscalculation would allow an
17682 attacker to overflow a piece of heap-allocated memory. To mount this
17683 attack, the attacker would need to either open a SOCKS connection to
17684 Tor's SocksPort (usually restricted to localhost), or target a Tor
17685 instance configured to make its connections through a SOCKS proxy
17686 (which Tor does not do by default).
17688 Good security practice requires that all heap-overflow bugs should be
17689 presumed to be exploitable until proven otherwise, so we are treating
17690 this as a potential code execution attack. Please upgrade immediately!
17691 This bug does not affect bufferevents-based builds of Tor. Special
17692 thanks to "Vektor" for reporting this issue to us!
17694 This release also contains a few minor bugfixes for issues discovered
17698 - Fix a heap overflow bug that could occur when trying to pull
17699 data into the first chunk of a buffer, when that chunk had
17700 already had some data drained from it. Fixes CVE-2011-2778;
17701 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
17704 - If we can't attach streams to a rendezvous circuit when we
17705 finish connecting to a hidden service, clear the rendezvous
17706 circuit's stream-isolation state and try to attach streams
17707 again. Previously, we cleared rendezvous circuits' isolation
17708 state either too early (if they were freshly built) or not at all
17709 (if they had been built earlier and were cannibalized). Bugfix on
17710 0.2.3.3-alpha; fixes bug 4655.
17711 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
17712 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
17713 - Fix an assertion failure when a relay with accounting enabled
17714 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
17717 - Update to the December 6 2011 Maxmind GeoLite Country database.
17720 Changes in version 0.2.2.35 - 2011-12-16
17721 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
17722 buffers code. Absolutely everybody should upgrade.
17724 The bug relied on an incorrect calculation when making data continuous
17725 in one of our IO buffers, if the first chunk of the buffer was
17726 misaligned by just the wrong amount. The miscalculation would allow an
17727 attacker to overflow a piece of heap-allocated memory. To mount this
17728 attack, the attacker would need to either open a SOCKS connection to
17729 Tor's SocksPort (usually restricted to localhost), or target a Tor
17730 instance configured to make its connections through a SOCKS proxy
17731 (which Tor does not do by default).
17733 Good security practice requires that all heap-overflow bugs should be
17734 presumed to be exploitable until proven otherwise, so we are treating
17735 this as a potential code execution attack. Please upgrade immediately!
17736 This bug does not affect bufferevents-based builds of Tor. Special
17737 thanks to "Vektor" for reporting this issue to us!
17739 Tor 0.2.2.35 also fixes several bugs in previous versions, including
17740 crash bugs for unusual configurations, and a long-term bug that
17741 would prevent Tor from starting on Windows machines with draconian
17744 With this release, we remind everyone that 0.2.0.x has reached its
17745 formal end-of-life. Those Tor versions have many known flaws, and
17746 nobody should be using them. You should upgrade -- ideally to the
17747 0.2.2.x series. If you're using a Linux or BSD and its packages are
17748 obsolete, stop using those packages and upgrade anyway.
17750 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
17751 longer receive support after some time in early 2012.
17754 - Fix a heap overflow bug that could occur when trying to pull
17755 data into the first chunk of a buffer, when that chunk had
17756 already had some data drained from it. Fixes CVE-2011-2778;
17757 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
17758 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
17759 that it doesn't attempt to allocate a socketpair. This could cause
17760 some problems on Windows systems with overzealous firewalls. Fix for
17761 bug 4457; workaround for Libevent versions 2.0.1-alpha through
17763 - If we mark an OR connection for close based on a cell we process,
17764 don't process any further cells on it. We already avoid further
17765 reads on marked-for-close connections, but now we also discard the
17766 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
17767 which was the first version where we might mark a connection for
17768 close based on processing a cell on it.
17769 - Correctly sanity-check that we don't underflow on a memory
17770 allocation (and then assert) for hidden service introduction
17771 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
17772 bugfix on 0.2.1.5-alpha.
17773 - Fix a memory leak when we check whether a hidden service
17774 descriptor has any usable introduction points left. Fixes bug
17775 4424. Bugfix on 0.2.2.25-alpha.
17776 - Don't crash when we're running as a relay and don't have a GeoIP
17777 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
17778 we've had in the 0.2.3.x branch already.
17779 - When running as a client, do not print a misleading (and plain
17780 wrong) log message that we're collecting "directory request"
17781 statistics: clients don't collect statistics. Also don't create a
17782 useless (because empty) stats file in the stats/ directory. Fixes
17783 bug 4353; bugfix on 0.2.2.34.
17786 - Detect failure to initialize Libevent. This fix provides better
17787 detection for future instances of bug 4457.
17788 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
17789 function. This was eating up hideously large amounts of time on some
17790 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
17791 - Resolve an integer overflow bug in smartlist_ensure_capacity().
17792 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
17794 - Don't warn about unused log_mutex in log.c when building with
17795 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
17796 0.1.0.6-rc which introduced --disable-threads.
17797 - When configuring, starting, or stopping an NT service, stop
17798 immediately after the service configuration attempt has succeeded
17799 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
17800 - When sending a NETINFO cell, include the original address
17801 received for the other side, not its canonical address. Found
17802 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
17803 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
17804 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
17805 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
17806 occurred when a client tried to fetch a descriptor for a bridge
17807 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
17808 - Backport fixes for a pair of compilation warnings on Windows.
17809 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
17810 - If we had ever tried to call tor_addr_to_str on an address of
17811 unknown type, we would have done a strdup on an uninitialized
17812 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
17813 Reported by "troll_un".
17814 - Correctly detect and handle transient lookup failures from
17815 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
17816 Reported by "troll_un".
17817 - Fix null-pointer access that could occur if TLS allocation failed.
17818 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
17819 - Use tor_socket_t type for listener argument to accept(). Fixes bug
17820 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
17823 - Add two new config options for directory authorities:
17824 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
17825 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
17826 that is always sufficient to satisfy the bandwidth requirement for
17827 the Guard flag. Now it will be easier for researchers to simulate
17828 Tor networks with different values. Resolves ticket 4484.
17829 - When Tor ignores a hidden service specified in its configuration,
17830 include the hidden service's directory in the warning message.
17831 Previously, we would only tell the user that some hidden service
17832 was ignored. Bugfix on 0.0.6; fixes bug 4426.
17833 - Update to the December 6 2011 Maxmind GeoLite Country database.
17835 o Packaging changes:
17836 - Make it easier to automate expert package builds on Windows,
17837 by removing an absolute path from makensis.exe command.
17840 Changes in version 0.2.1.32 - 2011-12-16
17841 Tor 0.2.1.32 backports important security and privacy fixes for
17842 oldstable. This release is intended only for package maintainers and
17843 others who cannot use the 0.2.2 stable series. All others should be
17844 using Tor 0.2.2.x or newer.
17846 The Tor 0.2.1.x series will reach formal end-of-life some time in
17847 early 2012; we will stop releasing patches for it then.
17849 o Major bugfixes (also included in 0.2.2.x):
17850 - Correctly sanity-check that we don't underflow on a memory
17851 allocation (and then assert) for hidden service introduction
17852 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
17853 bugfix on 0.2.1.5-alpha.
17854 - Fix a heap overflow bug that could occur when trying to pull
17855 data into the first chunk of a buffer, when that chunk had
17856 already had some data drained from it. Fixes CVE-2011-2778;
17857 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
17860 - Update to the December 6 2011 Maxmind GeoLite Country database.
17863 Changes in version 0.2.3.9-alpha - 2011-12-08
17864 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
17865 a "DisableNetwork" security feature that bundles can use to avoid
17866 touching the network until bridges are configured, moves forward on
17867 the pluggable transport design, fixes a flaw in the hidden service
17868 design that unnecessarily prevented clients with wrong clocks from
17869 reaching hidden services, and fixes a wide variety of other issues.
17872 - Clients can now connect to private bridges over IPv6. Bridges
17873 still need at least one IPv4 address in order to connect to
17874 other relays. Note that we don't yet handle the case where the
17875 user has two bridge lines for the same bridge (one IPv4, one
17876 IPv6). Implements parts of proposal 186.
17877 - New "DisableNetwork" config option to prevent Tor from launching any
17878 connections or accepting any connections except on a control port.
17879 Bundles and controllers can set this option before letting Tor talk
17880 to the rest of the network, for example to prevent any connections
17881 to a non-bridge address. Packages like Orbot can also use this
17882 option to instruct Tor to save power when the network is off.
17883 - Clients and bridges can now be configured to use a separate
17884 "transport" proxy. This approach makes the censorship arms race
17885 easier by allowing bridges to use protocol obfuscation plugins. It
17886 implements the "managed proxy" part of proposal 180 (ticket 3472).
17887 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
17888 implementation. It makes AES_CTR about 7% faster than our old one
17889 (which was about 10% faster than the one OpenSSL used to provide).
17890 Resolves ticket 4526.
17891 - Add a "tor2web mode" for clients that want to connect to hidden
17892 services non-anonymously (and possibly more quickly). As a safety
17893 measure to try to keep users from turning this on without knowing
17894 what they are doing, tor2web mode must be explicitly enabled at
17895 compile time, and a copy of Tor compiled to run in tor2web mode
17896 cannot be used as a normal Tor client. Implements feature 2553.
17897 - Add experimental support for running on Windows with IOCP and no
17898 kernel-space socket buffers. This feature is controlled by a new
17899 "UserspaceIOCPBuffers" config option (off by default), which has
17900 no effect unless Tor has been built with support for bufferevents,
17901 is running on Windows, and has enabled IOCP. This may, in the long
17902 run, help solve or mitigate bug 98.
17903 - Use a more secure consensus parameter voting algorithm. Now at
17904 least three directory authorities or a majority of them must
17905 vote on a given parameter before it will be included in the
17906 consensus. Implements proposal 178.
17909 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
17910 They used to check that the timestamp was within 30 minutes
17911 of their system clock, so they could cap the size of their
17912 replay-detection cache, but that approach unnecessarily refused
17913 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
17914 the v3 intro-point protocol (the first one which sent a timestamp
17915 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
17916 - Only use the EVP interface when AES acceleration is enabled,
17917 to avoid a 5-7% performance regression. Resolves issue 4525;
17918 bugfix on 0.2.3.8-alpha.
17920 o Privacy/anonymity features (bridge detection):
17921 - Make bridge SSL certificates a bit more stealthy by using random
17922 serial numbers, in the same fashion as OpenSSL when generating
17923 self-signed certificates. Implements ticket 4584.
17924 - Introduce a new config option "DynamicDHGroups", enabled by
17925 default, which provides each bridge with a unique prime DH modulus
17926 to be used during SSL handshakes. This option attempts to help
17927 against censors who might use the Apache DH modulus as a static
17928 identifier for bridges. Addresses ticket 4548.
17930 o Minor features (new/different config options):
17931 - New configuration option "DisableDebuggerAttachment" (on by default)
17932 to prevent basic debugging attachment attempts by other processes.
17933 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
17934 - Allow MapAddress directives to specify matches against super-domains,
17935 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
17936 Implements issue 933.
17937 - Slightly change behavior of "list" options (that is, config
17938 options that can appear more than once) when they appear both in
17939 torrc and on the command line. Previously, the command-line options
17940 would be appended to the ones from torrc. Now, the command-line
17941 options override the torrc options entirely. This new behavior
17942 allows the user to override list options (like exit policies and
17943 ports to listen on) from the command line, rather than simply
17944 appending to the list.
17945 - You can get the old (appending) command-line behavior for "list"
17946 options by prefixing the option name with a "+".
17947 - You can remove all the values for a "list" option from the command
17948 line without adding any new ones by prefixing the option name
17950 - Add experimental support for a "defaults" torrc file to be parsed
17951 before the regular torrc. Torrc options override the defaults file's
17952 options in the same way that the command line overrides the torrc.
17953 The SAVECONF controller command saves only those options which
17954 differ between the current configuration and the defaults file. HUP
17955 reloads both files. (Note: This is an experimental feature; its
17956 behavior will probably be refined in future 0.2.3.x-alpha versions
17957 to better meet packagers' needs.) Implements task 4552.
17960 - Try to make the introductory warning message that Tor prints on
17961 startup more useful for actually finding help and information.
17962 Resolves ticket 2474.
17963 - Running "make version" now displays the version of Tor that
17964 we're about to build. Idea from katmagic; resolves issue 4400.
17965 - Expire old or over-used hidden service introduction points.
17966 Required by fix for bug 3460.
17967 - Move the replay-detection cache for the RSA-encrypted parts of
17968 INTRODUCE2 cells to the introduction point data structures.
17969 Previously, we would use one replay-detection cache per hidden
17970 service. Required by fix for bug 3460.
17971 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
17972 public key replay-detection cache from 60 minutes to 5 minutes. This
17973 replay-detection cache is now used only to detect multiple
17974 INTRODUCE2 cells specifying the same rendezvous point, so we can
17975 avoid launching multiple simultaneous attempts to connect to it.
17977 o Minor bugfixes (on Tor 0.2.2.x and earlier):
17978 - Resolve an integer overflow bug in smartlist_ensure_capacity().
17979 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
17981 - Fix a minor formatting issue in one of tor-gencert's error messages.
17983 - Prevent a false positive from the check-spaces script, by disabling
17984 the "whitespace between function name and (" check for functions
17986 - Fix a log message suggesting that people contact a non-existent
17987 email address. Fixes bug 3448.
17988 - Fix null-pointer access that could occur if TLS allocation failed.
17989 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
17990 - Report a real bootstrap problem to the controller on router
17991 identity mismatch. Previously we just said "foo", which probably
17992 made a lot of sense at the time. Fixes bug 4169; bugfix on
17994 - If we had ever tried to call tor_addr_to_str() on an address of
17995 unknown type, we would have done a strdup() on an uninitialized
17996 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
17997 Reported by "troll_un".
17998 - Correctly detect and handle transient lookup failures from
17999 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
18000 Reported by "troll_un".
18001 - Use tor_socket_t type for listener argument to accept(). Fixes bug
18002 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
18003 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
18004 bug 4532; found by "troll_un".
18006 o Minor bugfixes (on Tor 0.2.3.x):
18007 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
18009 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
18010 circuit for use as a hidden service client's rendezvous point.
18011 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
18012 with help from wanoskarnet.
18013 - Restore behavior of overriding SocksPort, ORPort, and similar
18014 options from the command line. Bugfix on 0.2.3.3-alpha.
18017 - Properly handle the case where the build-tree is not the same
18018 as the source tree when generating src/common/common_sha1.i,
18019 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
18020 bugfix on 0.2.0.1-alpha.
18022 o Code simplifications, cleanups, and refactorings:
18023 - Remove the pure attribute from all functions that used it
18024 previously. In many cases we assigned it incorrectly, because the
18025 functions might assert or call impure functions, and we don't have
18026 evidence that keeping the pure attribute is worthwhile. Implements
18027 changes suggested in ticket 4421.
18028 - Remove some dead code spotted by coverity. Fixes cid 432.
18029 Bugfix on 0.2.3.1-alpha, closes bug 4637.
18032 Changes in version 0.2.3.8-alpha - 2011-11-22
18033 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
18034 socketpair-related bug that has been bothering Windows users. It adds
18035 support to serve microdescriptors to controllers, so Vidalia's network
18036 map can resume listing relays (once Vidalia implements its side),
18037 and adds better support for hardware AES acceleration. Finally, it
18038 starts the process of adjusting the bandwidth cutoff for getting the
18039 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
18040 that tiny relays harm performance more than they help network capacity.
18043 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
18044 that it doesn't attempt to allocate a socketpair. This could cause
18045 some problems on Windows systems with overzealous firewalls. Fix for
18046 bug 4457; workaround for Libevent versions 2.0.1-alpha through
18048 - Correctly sanity-check that we don't underflow on a memory
18049 allocation (and then assert) for hidden service introduction
18050 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
18051 bugfix on 0.2.1.5-alpha.
18052 - Remove the artificially low cutoff of 20KB to guarantee the Fast
18053 flag. In the past few years the average relay speed has picked
18054 up, and while the "top 7/8 of the network get the Fast flag" and
18055 "all relays with 20KB or more of capacity get the Fast flag" rules
18056 used to have the same result, now the top 7/8 of the network has
18057 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
18058 - Fix a rare assertion failure when checking whether a v0 hidden
18059 service descriptor has any usable introduction points left, and
18060 we don't have enough information to build a circuit to the first
18061 intro point named in the descriptor. The HS client code in
18062 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
18063 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
18064 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
18065 - Make bridge authorities not crash when they are asked for their own
18066 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
18067 - When running as a client, do not print a misleading (and plain
18068 wrong) log message that we're collecting "directory request"
18069 statistics: clients don't collect statistics. Also don't create a
18070 useless (because empty) stats file in the stats/ directory. Fixes
18071 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
18074 - Allow Tor controllers like Vidalia to obtain the microdescriptor
18075 for a relay by identity digest or nickname. Previously,
18076 microdescriptors were only available by their own digests, so a
18077 controller would have to ask for and parse the whole microdescriptor
18078 consensus in order to look up a single relay's microdesc. Fixes
18079 bug 3832; bugfix on 0.2.3.1-alpha.
18080 - Use OpenSSL's EVP interface for AES encryption, so that all AES
18081 operations can use hardware acceleration (if present). Resolves
18084 o Minor bugfixes (on 0.2.2.x and earlier):
18085 - Detect failure to initialize Libevent. This fix provides better
18086 detection for future instances of bug 4457.
18087 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
18088 function. This was eating up hideously large amounts of time on some
18089 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
18090 - Don't warn about unused log_mutex in log.c when building with
18091 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
18092 0.1.0.6-rc which introduced --disable-threads.
18093 - Allow manual 'authenticate' commands to the controller interface
18094 from netcat (nc) as well as telnet. We were rejecting them because
18095 they didn't come with the expected whitespace at the end of the
18096 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
18097 - Fix some (not actually triggerable) buffer size checks in usage of
18098 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
18100 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
18101 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
18102 - When configuring, starting, or stopping an NT service, stop
18103 immediately after the service configuration attempt has succeeded
18104 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
18105 - When sending a NETINFO cell, include the original address
18106 received for the other side, not its canonical address. Found
18107 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
18108 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
18109 can pick them up when the tests aren't disabled. Bugfix on
18110 0.2.2.4-alpha which introduced tinytest.
18111 - Fix a memory leak when we check whether a hidden service
18112 descriptor has any usable introduction points left. Fixes bug
18113 4424. Bugfix on 0.2.2.25-alpha.
18114 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
18115 occurred when a client tried to fetch a descriptor for a bridge
18116 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
18118 o Minor bugfixes (on 0.2.3.x):
18119 - Make util unit tests build correctly with MSVC. Bugfix on
18120 0.2.3.3-alpha. Patch by Gisle Vanem.
18121 - Successfully detect AUTH_CHALLENGE cells with no recognized
18122 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
18123 Found by frosty_un.
18124 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
18125 it should still send a NETINFO cell to allow the connection to
18126 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
18128 - Log less loudly when we get an invalid authentication certificate
18129 from a source other than a directory authority: it's not unusual
18130 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
18132 - Tolerate servers with more clock skew in their authentication
18133 certificates than previously. Fixes bug 4371; bugfix on
18135 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
18136 on 0.2.3.4-alpha and 0.2.3.6-alpha.
18139 - Add two new config options for directory authorities:
18140 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
18141 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
18142 that is always sufficient to satisfy the bandwidth requirement for
18143 the Guard flag. Now it will be easier for researchers to simulate
18144 Tor networks with different values. Resolves ticket 4484.
18145 - When Tor ignores a hidden service specified in its configuration,
18146 include the hidden service's directory in the warning message.
18147 Previously, we would only tell the user that some hidden service
18148 was ignored. Bugfix on 0.0.6; fixes bug 4426.
18149 - When we fail to initialize Libevent, retry with IOCP disabled so we
18150 don't need to turn on multi-threading support in Libevent, which in
18151 turn requires a working socketpair(). This is a workaround for bug
18152 4457, which affects Libevent versions from 2.0.1-alpha through
18154 - Detect when we try to build on a platform that doesn't define
18155 AF_UNSPEC to 0. We don't work there, so refuse to compile.
18156 - Update to the November 1 2011 Maxmind GeoLite Country database.
18158 o Packaging changes:
18159 - Make it easier to automate expert package builds on Windows,
18160 by removing an absolute path from makensis.exe command.
18162 o Code simplifications and refactoring:
18163 - Remove some redundant #include directives throughout the code.
18164 Patch from Andrea Gelmini.
18165 - Unconditionally use OpenSSL's AES implementation instead of our
18166 old built-in one. OpenSSL's AES has been better for a while, and
18167 relatively few servers should still be on any version of OpenSSL
18168 that doesn't have good optimized assembly AES.
18169 - Use the name "CERTS" consistently to refer to the new cell type;
18170 we were calling it CERT in some places and CERTS in others.
18173 - Numerous new unit tests for functions in util.c and address.c by
18175 - The long-disabled benchmark tests are now split into their own
18176 ./src/test/bench binary.
18177 - The benchmark tests can now use more accurate timers than
18178 gettimeofday() when such timers are available.
18181 Changes in version 0.2.3.7-alpha - 2011-10-30
18182 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
18183 the new v3 handshake. It also resolves yet another bridge address
18187 - If we mark an OR connection for close based on a cell we process,
18188 don't process any further cells on it. We already avoid further
18189 reads on marked-for-close connections, but now we also discard the
18190 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
18191 which was the first version where we might mark a connection for
18192 close based on processing a cell on it.
18193 - Fix a double-free bug that would occur when we received an invalid
18194 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
18195 bugfix on 0.2.3.6-alpha.
18196 - Bridges no longer include their address in NETINFO cells on outgoing
18197 OR connections, to allow them to blend in better with clients.
18198 Removes another avenue for enumerating bridges. Reported by
18199 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
18200 cells were introduced.
18203 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
18204 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
18207 Changes in version 0.2.3.6-alpha - 2011-10-26
18208 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
18209 anonymity vulnerability where an attacker can deanonymize Tor
18210 users. Everybody should upgrade.
18212 This release also features support for a new v3 connection handshake
18213 protocol, and fixes to make hidden service connections more robust.
18216 - Implement a new handshake protocol (v3) for authenticating Tors to
18217 each other over TLS. It should be more resistant to fingerprinting
18218 than previous protocols, and should require less TLS hacking for
18219 future Tor implementations. Implements proposal 176.
18220 - Allow variable-length padding cells to disguise the length of
18221 Tor's TLS records. Implements part of proposal 184.
18223 o Privacy/anonymity fixes (clients):
18224 - Clients and bridges no longer send TLS certificate chains on
18225 outgoing OR connections. Previously, each client or bridge would
18226 use the same cert chain for all outgoing OR connections until
18227 its IP address changes, which allowed any relay that the client
18228 or bridge contacted to determine which entry guards it is using.
18229 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
18230 - If a relay receives a CREATE_FAST cell on a TLS connection, it
18231 no longer considers that connection as suitable for satisfying a
18232 circuit EXTEND request. Now relays can protect clients from the
18233 CVE-2011-2768 issue even if the clients haven't upgraded yet.
18234 - Directory authorities no longer assign the Guard flag to relays
18235 that haven't upgraded to the above "refuse EXTEND requests
18236 to client connections" fix. Now directory authorities can
18237 protect clients from the CVE-2011-2768 issue even if neither
18238 the clients nor the relays have upgraded yet. There's a new
18239 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
18240 to let us transition smoothly, else tomorrow there would be no
18243 o Major bugfixes (hidden services):
18244 - Improve hidden service robustness: when an attempt to connect to
18245 a hidden service ends, be willing to refetch its hidden service
18246 descriptors from each of the HSDir relays responsible for them
18247 immediately. Previously, we would not consider refetching the
18248 service's descriptors from each HSDir for 15 minutes after the last
18249 fetch, which was inconvenient if the hidden service was not running
18250 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
18251 - When one of a hidden service's introduction points appears to be
18252 unreachable, stop trying it. Previously, we would keep trying
18253 to build circuits to the introduction point until we lost the
18254 descriptor, usually because the user gave up and restarted Tor.
18255 Partly fixes bug 3825.
18256 - Don't launch a useless circuit after failing to use one of a
18257 hidden service's introduction points. Previously, we would
18258 launch a new introduction circuit, but not set the hidden service
18259 which that circuit was intended to connect to, so it would never
18260 actually be used. A different piece of code would then create a
18261 new introduction circuit correctly. Bug reported by katmagic and
18262 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
18264 o Major bugfixes (other):
18265 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
18266 that they initiated. Relays could distinguish incoming bridge
18267 connections from client connections, creating another avenue for
18268 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
18269 Found by "frosty_un".
18270 - Don't update the AccountingSoftLimitHitAt state file entry whenever
18271 tor gets started. This prevents a wrong average bandwidth
18272 estimate, which would cause relays to always start a new accounting
18273 interval at the earliest possible moment. Fixes bug 2003; bugfix
18274 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
18275 immensely in tracking this bug down.
18276 - Fix a crash bug when changing node restrictions while a DNS lookup
18277 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
18280 o Minor bugfixes (on 0.2.2.x and earlier):
18281 - When a hidden service turns an extra service-side introduction
18282 circuit into a general-purpose circuit, free the rend_data and
18283 intro_key fields first, so we won't leak memory if the circuit
18284 is cannibalized for use as another service-side introduction
18285 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
18286 - Rephrase the log message emitted if the TestSocks check is
18287 successful. Patch from Fabian Keil; fixes bug 4094.
18288 - Bridges now skip DNS self-tests, to act a little more stealthily.
18289 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
18290 bridges. Patch by "warms0x".
18291 - Remove a confusing dollar sign from the example fingerprint in the
18292 man page, and also make the example fingerprint a valid one. Fixes
18293 bug 4309; bugfix on 0.2.1.3-alpha.
18294 - Fix internal bug-checking logic that was supposed to catch
18295 failures in digest generation so that it will fail more robustly
18296 if we ask for a nonexistent algorithm. Found by Coverity Scan.
18297 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
18298 - Report any failure in init_keys() calls launched because our
18299 IP address has changed. Spotted by Coverity Scan. Bugfix on
18300 0.1.1.4-alpha; fixes CID 484.
18302 o Minor bugfixes (on 0.2.3.x):
18303 - Fix a bug in configure.in that kept it from building a configure
18304 script with autoconf versions earlier than 2.61. Fixes bug 2430;
18305 bugfix on 0.2.3.1-alpha.
18306 - Don't warn users that they are exposing a client port to the
18307 Internet if they have specified an RFC1918 address. Previously,
18308 we would warn if the user had specified any non-loopback
18309 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
18310 - Fix memory leaks in the failing cases of the new SocksPort and
18311 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
18312 fixes coverity CIDs 485, 486, and 487.
18315 - When a hidden service's introduction point times out, consider
18316 trying it again during the next attempt to connect to the
18317 HS. Previously, we would not try it again unless a newly fetched
18318 descriptor contained it. Required by fixes for bugs 1297 and 3825.
18319 - The next version of Windows will be called Windows 8, and it has
18320 a major version of 6, minor version of 2. Correctly identify that
18321 version instead of calling it "Very recent version". Resolves
18322 ticket 4153; reported by funkstar.
18323 - The Bridge Authority now writes statistics on how many bridge
18324 descriptors it gave out in total, and how many unique descriptors
18325 it gave out. It also lists how often the most and least commonly
18326 fetched descriptors were given out, as well as the median and
18327 25th/75th percentile. Implements tickets 4200 and 4294.
18328 - Update to the October 4 2011 Maxmind GeoLite Country database.
18330 o Code simplifications and refactoring:
18331 - Remove some old code to remember statistics about which descriptors
18332 we've served as a directory mirror. The feature wasn't used and
18333 is outdated now that microdescriptors are around.
18334 - Rename Tor functions that turn strings into addresses, so that
18335 "parse" indicates that no hostname resolution occurs, and
18336 "lookup" indicates that hostname resolution may occur. This
18337 should help prevent mistakes in the future. Fixes bug 3512.
18340 Changes in version 0.2.2.34 - 2011-10-26
18341 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
18342 can deanonymize Tor users. Everybody should upgrade.
18344 The attack relies on four components: 1) Clients reuse their TLS cert
18345 when talking to different relays, so relays can recognize a user by
18346 the identity key in her cert. 2) An attacker who knows the client's
18347 identity key can probe each guard relay to see if that identity key
18348 is connected to that guard relay right now. 3) A variety of active
18349 attacks in the literature (starting from "Low-Cost Traffic Analysis
18350 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
18351 discover the guard relays that a Tor user visiting the website is using.
18352 4) Clients typically pick three guards at random, so the set of guards
18353 for a given user could well be a unique fingerprint for her. This
18354 release fixes components #1 and #2, which is enough to block the attack;
18355 the other two remain as open research problems. Special thanks to
18356 "frosty_un" for reporting the issue to us!
18358 Clients should upgrade so they are no longer recognizable by the TLS
18359 certs they present. Relays should upgrade so they no longer allow a
18360 remote attacker to probe them to test whether unpatched clients are
18361 currently connected to them.
18363 This release also fixes several vulnerabilities that allow an attacker
18364 to enumerate bridge relays. Some bridge enumeration attacks still
18365 remain; see for example proposal 188.
18367 o Privacy/anonymity fixes (clients):
18368 - Clients and bridges no longer send TLS certificate chains on
18369 outgoing OR connections. Previously, each client or bridge would
18370 use the same cert chain for all outgoing OR connections until
18371 its IP address changes, which allowed any relay that the client
18372 or bridge contacted to determine which entry guards it is using.
18373 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
18374 - If a relay receives a CREATE_FAST cell on a TLS connection, it
18375 no longer considers that connection as suitable for satisfying a
18376 circuit EXTEND request. Now relays can protect clients from the
18377 CVE-2011-2768 issue even if the clients haven't upgraded yet.
18378 - Directory authorities no longer assign the Guard flag to relays
18379 that haven't upgraded to the above "refuse EXTEND requests
18380 to client connections" fix. Now directory authorities can
18381 protect clients from the CVE-2011-2768 issue even if neither
18382 the clients nor the relays have upgraded yet. There's a new
18383 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
18384 to let us transition smoothly, else tomorrow there would be no
18387 o Privacy/anonymity fixes (bridge enumeration):
18388 - Bridge relays now do their directory fetches inside Tor TLS
18389 connections, like all the other clients do, rather than connecting
18390 directly to the DirPort like public relays do. Removes another
18391 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
18392 - Bridges relays now build circuits for themselves in a more similar
18393 way to how clients build them. Removes another avenue for
18394 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
18395 when bridges were introduced.
18396 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
18397 that they initiated. Relays could distinguish incoming bridge
18398 connections from client connections, creating another avenue for
18399 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
18400 Found by "frosty_un".
18403 - Fix a crash bug when changing node restrictions while a DNS lookup
18404 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
18406 - Don't launch a useless circuit after failing to use one of a
18407 hidden service's introduction points. Previously, we would
18408 launch a new introduction circuit, but not set the hidden service
18409 which that circuit was intended to connect to, so it would never
18410 actually be used. A different piece of code would then create a
18411 new introduction circuit correctly. Bug reported by katmagic and
18412 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
18415 - Change an integer overflow check in the OpenBSD_Malloc code so
18416 that GCC is less likely to eliminate it as impossible. Patch
18417 from Mansour Moufid. Fixes bug 4059.
18418 - When a hidden service turns an extra service-side introduction
18419 circuit into a general-purpose circuit, free the rend_data and
18420 intro_key fields first, so we won't leak memory if the circuit
18421 is cannibalized for use as another service-side introduction
18422 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
18423 - Bridges now skip DNS self-tests, to act a little more stealthily.
18424 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
18425 bridges. Patch by "warms0x".
18426 - Fix internal bug-checking logic that was supposed to catch
18427 failures in digest generation so that it will fail more robustly
18428 if we ask for a nonexistent algorithm. Found by Coverity Scan.
18429 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
18430 - Report any failure in init_keys() calls launched because our
18431 IP address has changed. Spotted by Coverity Scan. Bugfix on
18432 0.1.1.4-alpha; fixes CID 484.
18434 o Minor bugfixes (log messages and documentation):
18435 - Remove a confusing dollar sign from the example fingerprint in the
18436 man page, and also make the example fingerprint a valid one. Fixes
18437 bug 4309; bugfix on 0.2.1.3-alpha.
18438 - The next version of Windows will be called Windows 8, and it has
18439 a major version of 6, minor version of 2. Correctly identify that
18440 version instead of calling it "Very recent version". Resolves
18441 ticket 4153; reported by funkstar.
18442 - Downgrade log messages about circuit timeout calibration from
18443 "notice" to "info": they don't require or suggest any human
18444 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
18445 bugfix on 0.2.2.14-alpha.
18448 - Turn on directory request statistics by default and include them in
18449 extra-info descriptors. Don't break if we have no GeoIP database.
18450 Backported from 0.2.3.1-alpha; implements ticket 3951.
18451 - Update to the October 4 2011 Maxmind GeoLite Country database.
18454 Changes in version 0.2.1.31 - 2011-10-26
18455 Tor 0.2.1.31 backports important security and privacy fixes for
18456 oldstable. This release is intended only for package maintainers and
18457 others who cannot use the 0.2.2 stable series. All others should be
18458 using Tor 0.2.2.x or newer.
18460 o Security fixes (also included in 0.2.2.x):
18461 - Replace all potentially sensitive memory comparison operations
18462 with versions whose runtime does not depend on the data being
18463 compared. This will help resist a class of attacks where an
18464 adversary can use variations in timing information to learn
18465 sensitive data. Fix for one case of bug 3122. (Safe memcmp
18466 implementation by Robert Ransom based partially on code by DJB.)
18467 - Fix an assert in parsing router descriptors containing IPv6
18468 addresses. This one took down the directory authorities when
18469 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
18471 o Privacy/anonymity fixes (also included in 0.2.2.x):
18472 - Clients and bridges no longer send TLS certificate chains on
18473 outgoing OR connections. Previously, each client or bridge would
18474 use the same cert chain for all outgoing OR connections until
18475 its IP address changes, which allowed any relay that the client
18476 or bridge contacted to determine which entry guards it is using.
18477 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
18478 - If a relay receives a CREATE_FAST cell on a TLS connection, it
18479 no longer considers that connection as suitable for satisfying a
18480 circuit EXTEND request. Now relays can protect clients from the
18481 CVE-2011-2768 issue even if the clients haven't upgraded yet.
18482 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
18483 that they initiated. Relays could distinguish incoming bridge
18484 connections from client connections, creating another avenue for
18485 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
18486 Found by "frosty_un".
18487 - When receiving a hidden service descriptor, check that it is for
18488 the hidden service we wanted. Previously, Tor would store any
18489 hidden service descriptors that a directory gave it, whether it
18490 wanted them or not. This wouldn't have let an attacker impersonate
18491 a hidden service, but it did let directories pre-seed a client
18492 with descriptors that it didn't want. Bugfix on 0.0.6.
18493 - Avoid linkability based on cached hidden service descriptors: forget
18494 all hidden service descriptors cached as a client when processing a
18495 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
18496 - Make the bridge directory authority refuse to answer directory
18497 requests for "all" descriptors. It used to include bridge
18498 descriptors in its answer, which was a major information leak.
18499 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
18500 - Don't attach new streams to old rendezvous circuits after SIGNAL
18501 NEWNYM. Previously, we would keep using an existing rendezvous
18502 circuit if it remained open (i.e. if it were kept open by a
18503 long-lived stream, or if a new stream were attached to it before
18504 Tor could notice that it was old and no longer in use). Bugfix on
18505 0.1.1.15-rc; fixes bug 3375.
18507 o Minor bugfixes (also included in 0.2.2.x):
18508 - When we restart our relay, we might get a successful connection
18509 from the outside before we've started our reachability tests,
18510 triggering a warning: "ORPort found reachable, but I have no
18511 routerinfo yet. Failing to inform controller of success." This
18512 bug was harmless unless Tor is running under a controller
18513 like Vidalia, in which case the controller would never get a
18514 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
18516 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
18517 enabled. Fixes bug 1526.
18518 - Remove undocumented option "-F" from tor-resolve: it hasn't done
18519 anything since 0.2.1.16-rc.
18520 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
18521 None of the cases where we did this before were wrong, but by making
18522 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
18523 - Fix a rare crash bug that could occur when a client was configured
18524 with a large number of bridges. Fixes bug 2629; bugfix on
18525 0.2.1.2-alpha. Bugfix by trac user "shitlei".
18526 - Correct the warning displayed when a rendezvous descriptor exceeds
18527 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
18529 - Fix an uncommon assertion failure when running with DNSPort under
18530 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
18531 - When warning about missing zlib development packages during compile,
18532 give the correct package names. Bugfix on 0.2.0.1-alpha.
18533 - Require that introduction point keys and onion keys have public
18534 exponent 65537. Bugfix on 0.2.0.10-alpha.
18535 - Do not crash when our configuration file becomes unreadable, for
18536 example due to a permissions change, between when we start up
18537 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
18539 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
18541 - Always NUL-terminate the sun_path field of a sockaddr_un before
18542 passing it to the kernel. (Not a security issue: kernels are
18543 smart enough to reject bad sockaddr_uns.) Found by Coverity;
18544 CID #428. Bugfix on Tor 0.2.0.3-alpha.
18545 - Don't stack-allocate the list of supplementary GIDs when we're
18546 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
18547 could take up to 256K, which is way too much stack. Found by
18548 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
18550 o Minor bugfixes (only in 0.2.1.x):
18551 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
18552 rely on them. Bugfix on 0.2.1.30.
18553 - Use git revisions instead of svn revisions when generating our
18554 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
18556 o Minor features (also included in 0.2.2.x):
18557 - Adjust the expiration time on our SSL session certificates to
18558 better match SSL certs seen in the wild. Resolves ticket 4014.
18559 - Allow nameservers with IPv6 address. Resolves bug 2574.
18560 - Update to the October 4 2011 Maxmind GeoLite Country database.
18563 Changes in version 0.2.3.5-alpha - 2011-09-28
18564 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
18565 bridge relays; fixes an assertion error that many users started hitting
18566 today; and adds the ability to refill token buckets more often than
18567 once per second, allowing significant performance improvements.
18570 - Bridge relays now do their directory fetches inside Tor TLS
18571 connections, like all the other clients do, rather than connecting
18572 directly to the DirPort like public relays do. Removes another
18573 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
18574 - Bridges relays now build circuits for themselves in a more similar
18575 way to how clients build them. Removes another avenue for
18576 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
18577 when bridges were introduced.
18580 - Fix an "Assertion md->held_by_node == 1 failed" error that could
18581 occur when the same microdescriptor was referenced by two node_t
18582 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
18584 o Major features (networking):
18585 - Add a new TokenBucketRefillInterval option to refill token buckets
18586 more frequently than once per second. This should improve network
18587 performance, alleviate queueing problems, and make traffic less
18588 bursty. Implements proposal 183; closes ticket 3630. Design by
18589 Florian Tschorsch and Björn Scheuermann; implementation by
18593 - Change an integer overflow check in the OpenBSD_Malloc code so
18594 that GCC is less likely to eliminate it as impossible. Patch
18595 from Mansour Moufid. Fixes bug 4059.
18597 o Minor bugfixes (usability):
18598 - Downgrade log messages about circuit timeout calibration from
18599 "notice" to "info": they don't require or suggest any human
18600 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
18601 bugfix on 0.2.2.14-alpha.
18603 o Minor features (diagnostics):
18604 - When the system call to create a listener socket fails, log the
18605 error message explaining why. This may help diagnose bug 4027.
18608 Changes in version 0.2.3.4-alpha - 2011-09-13
18609 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
18610 tweak to Tor's TLS handshake that makes relays and bridges that run
18611 this new version reachable from Iran again. It also fixes a few new
18612 bugs in 0.2.3.x, and teaches relays to recognize when they're not
18613 listed in the network consensus and republish.
18615 o Major bugfixes (also part of 0.2.2.33):
18616 - Avoid an assertion failure when reloading a configuration with
18617 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
18618 3923; bugfix on 0.2.2.25-alpha.
18620 o Minor features (security, also part of 0.2.2.33):
18621 - Check for replays of the public-key encrypted portion of an
18622 INTRODUCE1 cell, in addition to the current check for replays of
18623 the g^x value. This prevents a possible class of active attacks
18624 by an attacker who controls both an introduction point and a
18625 rendezvous point, and who uses the malleability of AES-CTR to
18626 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
18627 that these attacks are infeasible (requiring the attacker to send
18628 on the order of zettabytes of altered cells in a short interval),
18629 but we'd rather block them off in case there are any classes of
18630 this attack that we missed. Reported by Willem Pinckaers.
18632 o Minor features (also part of 0.2.2.33):
18633 - Adjust the expiration time on our SSL session certificates to
18634 better match SSL certs seen in the wild. Resolves ticket 4014.
18635 - Change the default required uptime for a relay to be accepted as
18636 a HSDir (hidden service directory) from 24 hours to 25 hours.
18637 Improves on 0.2.0.10-alpha; resolves ticket 2649.
18638 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
18639 authorities to abstain from voting on assignment of the HSDir
18640 consensus flag. Related to bug 2649.
18641 - Update to the September 6 2011 Maxmind GeoLite Country database.
18643 o Minor bugfixes (also part of 0.2.2.33):
18644 - Demote the 'replay detected' log message emitted when a hidden
18645 service receives the same Diffie-Hellman public key in two different
18646 INTRODUCE2 cells to info level. A normal Tor client can cause that
18647 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
18648 fixes part of bug 2442.
18649 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
18650 level. There is nothing that a hidden service's operator can do
18651 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
18653 - Clarify a log message specifying the characters permitted in
18654 HiddenServiceAuthorizeClient client names. Previously, the log
18655 message said that "[A-Za-z0-9+-_]" were permitted; that could have
18656 given the impression that every ASCII character between "+" and "_"
18657 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
18659 o Build fixes (also part of 0.2.2.33):
18660 - Clean up some code issues that prevented Tor from building on older
18661 BSDs. Fixes bug 3894; reported by "grarpamp".
18662 - Search for a platform-specific version of "ar" when cross-compiling.
18663 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
18666 - Fix a bug where the SocksPort option (for example) would get
18667 ignored and replaced by the default if a SocksListenAddress
18668 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
18672 - Relays now try regenerating and uploading their descriptor more
18673 frequently if they are not listed in the consensus, or if the
18674 version of their descriptor listed in the consensus is too
18675 old. This fix should prevent situations where a server declines
18676 to re-publish itself because it has done so too recently, even
18677 though the authorities decided not to list its recent-enough
18678 descriptor. Fix for bug 3327.
18681 - Relays now include a reason for regenerating their descriptors
18682 in an HTTP header when uploading to the authorities. This will
18683 make it easier to debug descriptor-upload issues in the future.
18684 - When starting as root and then changing our UID via the User
18685 control option, and we have a ControlSocket configured, make sure
18686 that the ControlSocket is owned by the same account that Tor will
18687 run under. Implements ticket 3421; fix by Jérémy Bobbio.
18690 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
18691 utility function used in the control-port code). This shouldn't
18692 ever happen unless Tor is completely out of memory, but if it did
18693 happen and Tor somehow recovered from it, Tor could have sent a log
18694 message to a control port in the middle of a reply to a controller
18695 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
18696 - Make 'FetchUselessDescriptors' cause all descriptor types and
18697 all consensus types (including microdescriptors) to get fetched.
18698 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
18700 o Code refactoring:
18701 - Make a new "entry connection" struct as an internal subtype of "edge
18702 connection", to simplify the code and make exit connections smaller.
18705 Changes in version 0.2.2.33 - 2011-09-13
18706 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
18707 TLS handshake that makes relays and bridges that run this new version
18708 reachable from Iran again.
18711 - Avoid an assertion failure when reloading a configuration with
18712 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
18713 3923; bugfix on 0.2.2.25-alpha.
18715 o Minor features (security):
18716 - Check for replays of the public-key encrypted portion of an
18717 INTRODUCE1 cell, in addition to the current check for replays of
18718 the g^x value. This prevents a possible class of active attacks
18719 by an attacker who controls both an introduction point and a
18720 rendezvous point, and who uses the malleability of AES-CTR to
18721 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
18722 that these attacks are infeasible (requiring the attacker to send
18723 on the order of zettabytes of altered cells in a short interval),
18724 but we'd rather block them off in case there are any classes of
18725 this attack that we missed. Reported by Willem Pinckaers.
18728 - Adjust the expiration time on our SSL session certificates to
18729 better match SSL certs seen in the wild. Resolves ticket 4014.
18730 - Change the default required uptime for a relay to be accepted as
18731 a HSDir (hidden service directory) from 24 hours to 25 hours.
18732 Improves on 0.2.0.10-alpha; resolves ticket 2649.
18733 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
18734 authorities to abstain from voting on assignment of the HSDir
18735 consensus flag. Related to bug 2649.
18736 - Update to the September 6 2011 Maxmind GeoLite Country database.
18738 o Minor bugfixes (documentation and log messages):
18739 - Correct the man page to explain that HashedControlPassword and
18740 CookieAuthentication can both be set, in which case either method
18741 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
18742 when we decided to allow these config options to both be set. Issue
18743 raised by bug 3898.
18744 - Demote the 'replay detected' log message emitted when a hidden
18745 service receives the same Diffie-Hellman public key in two different
18746 INTRODUCE2 cells to info level. A normal Tor client can cause that
18747 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
18748 fixes part of bug 2442.
18749 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
18750 level. There is nothing that a hidden service's operator can do
18751 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
18753 - Clarify a log message specifying the characters permitted in
18754 HiddenServiceAuthorizeClient client names. Previously, the log
18755 message said that "[A-Za-z0-9+-_]" were permitted; that could have
18756 given the impression that every ASCII character between "+" and "_"
18757 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
18760 - Provide a substitute implementation of lround() for MSVC, which
18761 apparently lacks it. Patch from Gisle Vanem.
18762 - Clean up some code issues that prevented Tor from building on older
18763 BSDs. Fixes bug 3894; reported by "grarpamp".
18764 - Search for a platform-specific version of "ar" when cross-compiling.
18765 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
18768 Changes in version 0.2.3.3-alpha - 2011-09-01
18769 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
18770 security, and provides client-side support for the microdescriptor
18771 and optimistic data features introduced earlier in the 0.2.3.x
18772 series. It also includes numerous critical bugfixes in the (optional)
18773 bufferevent-based networking backend.
18775 o Major features (stream isolation):
18776 - You can now configure Tor so that streams from different
18777 applications are isolated on different circuits, to prevent an
18778 attacker who sees your streams as they leave an exit node from
18779 linking your sessions to one another. To do this, choose some way
18780 to distinguish the applications: have them connect to different
18781 SocksPorts, or have one of them use SOCKS4 while the other uses
18782 SOCKS5, or have them pass different authentication strings to the
18783 SOCKS proxy. Then, use the new SocksPort syntax to configure the
18784 degree of isolation you need. This implements Proposal 171.
18785 - There's a new syntax for specifying multiple client ports (such as
18786 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
18787 multiple *Port entries with full addr:port syntax on each.
18788 The old *ListenAddress format is still supported, but you can't
18789 mix it with the new *Port syntax.
18791 o Major features (other):
18792 - Enable microdescriptor fetching by default for clients. This allows
18793 clients to download a much smaller amount of directory information.
18794 To disable it (and go back to the old-style consensus and
18795 descriptors), set "UseMicrodescriptors 0" in your torrc file.
18796 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
18797 "PortForwarding" config option), now supports Windows.
18798 - When using an exit relay running 0.2.3.x, clients can now
18799 "optimistically" send data before the exit relay reports that
18800 the stream has opened. This saves a round trip when starting
18801 connections where the client speaks first (such as web browsing).
18802 This behavior is controlled by a consensus parameter (currently
18803 disabled). To turn it on or off manually, use the "OptimisticData"
18804 torrc option. Implements proposal 181; code by Ian Goldberg.
18806 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
18807 - When using IOCP on Windows, we need to enable Libevent windows
18809 - The IOCP backend now works even when the user has not specified
18810 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
18811 Fixes part of bug 3752.
18812 - Correctly record the bytes we've read and written when using
18813 bufferevents, so that we can include them in our bandwidth history
18814 and advertised bandwidth. Fixes bug 3803.
18815 - Apply rate-limiting only at the bottom of a chain of filtering
18816 bufferevents. This prevents us from filling up internal read
18817 buffers and violating rate-limits when filtering bufferevents
18818 are enabled. Fixes part of bug 3804.
18819 - Add high-watermarks to the output buffers for filtered
18820 bufferevents. This prevents us from filling up internal write
18821 buffers and wasting CPU cycles when filtering bufferevents are
18822 enabled. Fixes part of bug 3804.
18823 - Correctly notice when data has been written from a bufferevent
18824 without flushing it completely. Fixes bug 3805.
18825 - Fix a bug where server-side tunneled bufferevent-based directory
18826 streams would get closed prematurely. Fixes bug 3814.
18827 - Fix a use-after-free error with per-connection rate-limiting
18828 buckets. Fixes bug 3888.
18830 o Major bugfixes (also part of 0.2.2.31-rc):
18831 - If we're configured to write our ControlPorts to disk, only write
18832 them after switching UID and creating the data directory. This way,
18833 we don't fail when starting up with a nonexistent DataDirectory
18834 and a ControlPortWriteToFile setting based on that directory. Fixes
18835 bug 3747; bugfix on Tor 0.2.2.26-beta.
18838 - Added a new CONF_CHANGED event so that controllers can be notified
18839 of any configuration changes made by other controllers, or by the
18840 user. Implements ticket 1692.
18841 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
18842 leak when using bufferevents, and lets Libevent worry about how to
18843 best copy data out of a buffer.
18844 - Replace files in stats/ rather than appending to them. Now that we
18845 include statistics in extra-info descriptors, it makes no sense to
18846 keep old statistics forever. Implements ticket 2930.
18848 o Minor features (build compatibility):
18849 - Limited, experimental support for building with nmake and MSVC.
18850 - Provide a substitute implementation of lround() for MSVC, which
18851 apparently lacks it. Patch from Gisle Vanem.
18853 o Minor features (also part of 0.2.2.31-rc):
18854 - Update to the August 2 2011 Maxmind GeoLite Country database.
18856 o Minor bugfixes (on 0.2.3.x-alpha):
18857 - Fix a spurious warning when parsing SOCKS requests with
18858 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
18859 - Get rid of a harmless warning that could happen on relays running
18860 with bufferevents. The warning was caused by someone doing an http
18861 request to a relay's orport. Also don't warn for a few related
18862 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
18864 o Minor bugfixes (on 2.2.x and earlier):
18865 - Correct the man page to explain that HashedControlPassword and
18866 CookieAuthentication can both be set, in which case either method
18867 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
18868 when we decided to allow these config options to both be set. Issue
18869 raised by bug 3898.
18870 - The "--quiet" and "--hush" options now apply not only to Tor's
18871 behavior before logs are configured, but also to Tor's behavior in
18872 the absence of configured logs. Fixes bug 3550; bugfix on
18875 o Minor bugfixes (also part of 0.2.2.31-rc):
18876 - Write several files in text mode, on OSes that distinguish text
18877 mode from binary mode (namely, Windows). These files are:
18878 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
18879 that collect those statistics; 'client_keys' and 'hostname' for
18880 hidden services that use authentication; and (in the tor-gencert
18881 utility) newly generated identity and signing keys. Previously,
18882 we wouldn't specify text mode or binary mode, leading to an
18883 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
18884 the DirRecordUsageByCountry option which would have triggered
18885 the assertion failure was added), although this assertion failure
18886 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
18887 - Selectively disable deprecation warnings on OS X because Lion
18888 started deprecating the shipped copy of openssl. Fixes bug 3643.
18889 - Remove an extra pair of quotation marks around the error
18890 message in control-port STATUS_GENERAL BUG events. Bugfix on
18891 0.1.2.6-alpha; fixes bug 3732.
18892 - When unable to format an address as a string, report its value
18893 as "???" rather than reusing the last formatted address. Bugfix
18896 o Code simplifications and refactoring:
18897 - Rewrite the listener-selection logic so that parsing which ports
18898 we want to listen on is now separate from binding to the ports
18902 - Building Tor with bufferevent support now requires Libevent
18903 2.0.13-stable or later. Previous versions of Libevent had bugs in
18904 SSL-related bufferevents and related issues that would make Tor
18905 work badly with bufferevents. Requiring 2.0.13-stable also allows
18906 Tor with bufferevents to take advantage of Libevent APIs
18907 introduced after 2.0.8-rc.
18910 Changes in version 0.2.2.32 - 2011-08-27
18911 The Tor 0.2.2 release series is dedicated to the memory of Andreas
18912 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
18913 a founder of the PETS community, a leader in our field, a mentor,
18914 and a friend. He left us with these words: "I had the possibility
18915 to contribute to this world that is not as it should be. I hope I
18916 could help in some areas to make the world a better place, and that
18917 I could also encourage other people to be engaged in improving the
18918 world. Please, stay engaged. This world needs you, your love, your
18919 initiative -- now I cannot be part of that anymore."
18921 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
18922 ready. More than two years in the making, this release features improved
18923 client performance and hidden service reliability, better compatibility
18924 for Android, correct behavior for bridges that listen on more than
18925 one address, more extensible and flexible directory object handling,
18926 better reporting of network statistics, improved code security, and
18927 many many other features and bugfixes.
18930 Changes in version 0.2.2.31-rc - 2011-08-17
18931 Tor 0.2.2.31-rc is the second and hopefully final release candidate
18932 for the Tor 0.2.2.x series.
18935 - Remove an extra pair of quotation marks around the error
18936 message in control-port STATUS_GENERAL BUG events. Bugfix on
18937 0.1.2.6-alpha; fixes bug 3732.
18938 - If we're configured to write our ControlPorts to disk, only write
18939 them after switching UID and creating the data directory. This way,
18940 we don't fail when starting up with a nonexistent DataDirectory
18941 and a ControlPortWriteToFile setting based on that directory. Fixes
18942 bug 3747; bugfix on Tor 0.2.2.26-beta.
18945 - Update to the August 2 2011 Maxmind GeoLite Country database.
18948 - Allow GETINFO fingerprint to return a fingerprint even when
18949 we have not yet built a router descriptor. Fixes bug 3577;
18950 bugfix on 0.2.0.1-alpha.
18951 - Write several files in text mode, on OSes that distinguish text
18952 mode from binary mode (namely, Windows). These files are:
18953 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
18954 that collect those statistics; 'client_keys' and 'hostname' for
18955 hidden services that use authentication; and (in the tor-gencert
18956 utility) newly generated identity and signing keys. Previously,
18957 we wouldn't specify text mode or binary mode, leading to an
18958 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
18959 the DirRecordUsageByCountry option which would have triggered
18960 the assertion failure was added), although this assertion failure
18961 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
18962 - Selectively disable deprecation warnings on OS X because Lion
18963 started deprecating the shipped copy of openssl. Fixes bug 3643.
18964 - When unable to format an address as a string, report its value
18965 as "???" rather than reusing the last formatted address. Bugfix
18969 Changes in version 0.2.3.2-alpha - 2011-07-18
18970 Tor 0.2.3.2-alpha introduces two new experimental features:
18971 microdescriptors and pluggable transports. It also continues cleaning
18972 up a variety of recently introduced features.
18975 - Clients can now use microdescriptors instead of regular descriptors
18976 to build circuits. Microdescriptors are authority-generated
18977 summaries of regular descriptors' contents, designed to change
18978 very rarely (see proposal 158 for details). This feature is
18979 designed to save bandwidth, especially for clients on slow internet
18980 connections. It's off by default for now, since nearly no caches
18981 support it, but it will be on-by-default for clients in a future
18982 version. You can use the UseMicrodescriptors option to turn it on.
18983 - Tor clients using bridges can now be configured to use a separate
18984 'transport' proxy for each bridge. This approach helps to resist
18985 censorship by allowing bridges to use protocol obfuscation
18986 plugins. It implements part of proposal 180. Implements ticket 2841.
18987 - While we're trying to bootstrap, record how many TLS connections
18988 fail in each state, and report which states saw the most failures
18989 in response to any bootstrap failures. This feature may speed up
18990 diagnosis of censorship events. Implements ticket 3116.
18992 o Major bugfixes (on 0.2.3.1-alpha):
18993 - When configuring a large set of nodes in EntryNodes (as with
18994 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
18995 random subset to be guards, and choose them in random
18996 order. Fixes bug 2798.
18997 - Tor could crash when remembering a consensus in a non-used consensus
18998 flavor without having a current consensus set. Fixes bug 3361.
18999 - Comparing an unknown address to a microdescriptor's shortened exit
19000 policy would always give a "rejected" result. Fixes bug 3599.
19001 - Using microdescriptors as a client no longer prevents Tor from
19002 uploading and downloading hidden service descriptors. Fixes
19006 - Allow nameservers with IPv6 address. Resolves bug 2574.
19007 - Accept attempts to include a password authenticator in the
19008 handshake, as supported by SOCKS5. This handles SOCKS clients that
19009 don't know how to omit a password when authenticating. Resolves
19011 - When configuring a large set of nodes in EntryNodes, and there are
19012 enough of them listed as Guard so that we don't need to consider
19013 the non-guard entries, prefer the ones listed with the Guard flag.
19014 - Check for and recover from inconsistency in the microdescriptor
19015 cache. This will make it harder for us to accidentally free a
19016 microdescriptor without removing it from the appropriate data
19017 structures. Fixes issue 3135; issue noted by "wanoskarnet".
19018 - Log SSL state transitions at log level DEBUG, log domain
19019 HANDSHAKE. This can be useful for debugging censorship events.
19020 Implements ticket 3264.
19021 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
19022 implements ticket 3439.
19024 o Minor bugfixes (on 0.2.3.1-alpha):
19025 - Do not free all general-purpose regular descriptors just
19026 because microdescriptor use is enabled. Fixes bug 3113.
19027 - Correctly link libevent_openssl when --enable-static-libevent
19028 is passed to configure. Fixes bug 3118.
19029 - Bridges should not complain during their heartbeat log messages that
19030 they are unlisted in the consensus: that's more or less the point
19031 of being a bridge. Fixes bug 3183.
19032 - Report a SIGNAL event to controllers when acting on a delayed
19033 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
19034 event to the controller if we acted on a SIGNAL NEWNYM command
19035 immediately, and otherwise not report a SIGNAL event for the
19036 command at all. Fixes bug 3349.
19037 - Fix a crash when handling the SIGNAL controller command or
19038 reporting ERR-level status events with bufferevents enabled. Found
19039 by Robert Ransom. Fixes bug 3367.
19040 - Always ship the tor-fw-helper manpage in our release tarballs.
19041 Fixes bug 3389. Reported by Stephen Walker.
19042 - Fix a class of double-mark-for-close bugs when bufferevents
19043 are enabled. Fixes bug 3403.
19044 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
19045 - Add SIGNAL to the list returned by the 'GETINFO events/names'
19046 control-port command. Fixes part of bug 3465.
19047 - Prevent using negative indices during unit test runs when read_all()
19048 fails. Spotted by coverity.
19049 - Fix a rare memory leak when checking the nodelist without it being
19050 present. Found by coverity.
19051 - Only try to download a microdescriptor-flavored consensus from
19052 a directory cache that provides them.
19054 o Minor bugfixes (on 0.2.2.x and earlier):
19055 - Assert that hidden-service-related operations are not performed
19056 using single-hop circuits. Previously, Tor would assert that
19057 client-side streams are not attached to single-hop circuits,
19058 but not that other sensitive operations on the client and service
19059 side are not performed using single-hop circuits. Fixes bug 3332;
19061 - Don't publish a new relay descriptor when we reload our onion key,
19062 unless the onion key has actually changed. Fixes bug 3263 and
19063 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
19064 - Allow GETINFO fingerprint to return a fingerprint even when
19065 we have not yet built a router descriptor. Fixes bug 3577;
19066 bugfix on 0.2.0.1-alpha.
19067 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
19068 on 0.2.2.4-alpha; fixes bug 3427.
19070 o Code simplification and refactoring:
19071 - Use tor_sscanf() in place of scanf() in more places through the
19072 code. This makes us a little more locale-independent, and
19073 should help shut up code-analysis tools that can't tell
19074 a safe sscanf string from a dangerous one.
19075 - Use tt_assert(), not tor_assert(), for checking for test failures.
19076 This makes the unit tests more able to go on in the event that
19078 - Split connection_about_to_close() into separate functions for each
19082 - On Windows, we now define the _WIN32_WINNT macros only if they
19083 are not already defined. This lets the person building Tor decide,
19084 if they want, to require a later version of Windows.
19087 Changes in version 0.2.2.30-rc - 2011-07-07
19088 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
19089 series. It fixes a few smaller bugs, but generally appears stable.
19090 Please test it and let us know whether it is!
19093 - Send a SUCCEEDED stream event to the controller when a reverse
19094 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
19095 discovered by katmagic.
19096 - Always NUL-terminate the sun_path field of a sockaddr_un before
19097 passing it to the kernel. (Not a security issue: kernels are
19098 smart enough to reject bad sockaddr_uns.) Found by Coverity;
19099 CID #428. Bugfix on Tor 0.2.0.3-alpha.
19100 - Don't stack-allocate the list of supplementary GIDs when we're
19101 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
19102 could take up to 256K, which is way too much stack. Found by
19103 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
19104 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
19105 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
19106 fixes part of bug 3465.
19107 - Fix a memory leak when receiving a descriptor for a hidden
19108 service we didn't ask for. Found by Coverity; CID #30. Bugfix
19112 - Update to the July 1 2011 Maxmind GeoLite Country database.
19115 Changes in version 0.2.2.29-beta - 2011-06-20
19116 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
19117 have bridge lines in their torrc but don't want to use them; gets
19118 us closer to having the control socket feature working on Debian;
19119 and fixes a variety of smaller bugs.
19122 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
19123 When we changed the default behavior to "use bridges if any
19124 are listed in the torrc", we surprised users who had bridges
19125 in their torrc files but who didn't actually want to use them.
19126 Partial resolution for bug 3354.
19129 - Don't attach new streams to old rendezvous circuits after SIGNAL
19130 NEWNYM. Previously, we would keep using an existing rendezvous
19131 circuit if it remained open (i.e. if it were kept open by a
19132 long-lived stream, or if a new stream were attached to it before
19133 Tor could notice that it was old and no longer in use). Bugfix on
19134 0.1.1.15-rc; fixes bug 3375.
19137 - Fix a bug when using ControlSocketsGroupWritable with User. The
19138 directory's group would be checked against the current group, not
19139 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
19140 bugfix on 0.2.2.26-beta.
19141 - Make connection_printf_to_buf()'s behavior sane. Its callers
19142 expect it to emit a CRLF iff the format string ends with CRLF;
19143 it actually emitted a CRLF iff (a) the format string ended with
19144 CRLF or (b) the resulting string was over 1023 characters long or
19145 (c) the format string did not end with CRLF *and* the resulting
19146 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
19147 fixes part of bug 3407.
19148 - Make send_control_event_impl()'s behavior sane. Its callers
19149 expect it to always emit a CRLF at the end of the string; it
19150 might have emitted extra control characters as well. Bugfix on
19151 0.1.1.9-alpha; fixes another part of bug 3407.
19152 - Make crypto_rand_int() check the value of its input correctly.
19153 Previously, it accepted values up to UINT_MAX, but could return a
19154 negative number if given a value above INT_MAX+1. Found by George
19155 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
19156 - Avoid a segfault when reading a malformed circuit build state
19157 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
19159 - When asked about a DNS record type we don't support via a
19160 client DNSPort, reply with NOTIMPL rather than an empty
19161 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
19162 - Fix a rare memory leak during stats writing. Found by coverity.
19165 - Update to the June 1 2011 Maxmind GeoLite Country database.
19167 o Code simplifications and refactoring:
19168 - Remove some dead code as indicated by coverity.
19169 - Remove a few dead assignments during router parsing. Found by
19171 - Add some forgotten return value checks during unit tests. Found
19173 - Don't use 1-bit wide signed bit fields. Found by coverity.
19176 Changes in version 0.2.2.28-beta - 2011-06-04
19177 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
19178 fixed a big bug in whether relays stay in the consensus consistently,
19179 we moved closer to handling bridges and hidden services correctly,
19180 and we started the process of better handling the dreaded "my Vidalia
19181 died, and now my Tor demands a password when I try to reconnect to it"
19185 - Don't decide to make a new descriptor when receiving a HUP signal.
19186 This bug has caused a lot of 0.2.2.x relays to disappear from the
19187 consensus periodically. Fixes the most common case of triggering
19188 bug 1810; bugfix on 0.2.2.7-alpha.
19189 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
19190 - Don't try to build descriptors if "ORPort auto" is set and we
19191 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
19193 - Resolve a crash that occurred when setting BridgeRelay to 1 with
19194 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
19195 - Apply circuit timeouts to opened hidden-service-related circuits
19196 based on the correct start time. Previously, we would apply the
19197 circuit build timeout based on time since the circuit's creation;
19198 it was supposed to be applied based on time since the circuit
19199 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
19200 - Use the same circuit timeout for client-side introduction
19201 circuits as for other four-hop circuits, rather than the timeout
19202 for single-hop directory-fetch circuits; the shorter timeout may
19203 have been appropriate with the static circuit build timeout in
19204 0.2.1.x and earlier, but caused many hidden service access attempts
19205 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
19206 on 0.2.2.2-alpha; fixes another part of bug 1297.
19207 - In ticket 2511 we fixed a case where you could use an unconfigured
19208 bridge if you had configured it as a bridge the last time you ran
19209 Tor. Now fix another edge case: if you had configured it as a bridge
19210 but then switched to a different bridge via the controller, you
19211 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
19215 - Add an __OwningControllerProcess configuration option and a
19216 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
19217 that when it exits, Tor will shut down. Implements feature 3049.
19218 - If "UseBridges 1" is set and no bridges are configured, Tor will
19219 now refuse to build any circuits until some bridges are set.
19220 If "UseBridges auto" is set, Tor will use bridges if they are
19221 configured and we are not running as a server, but otherwise will
19222 make circuits as usual. The new default is "auto". Patch by anonym,
19223 so the Tails LiveCD can stop automatically revealing you as a Tor
19227 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
19228 - Remove a trailing asterisk from "exit-policy/default" in the
19229 output of the control port command "GETINFO info/names". Bugfix
19231 - Use a wide type to hold sockets when built for 64-bit Windows builds.
19233 - Warn when the user configures two HiddenServiceDir lines that point
19234 to the same directory. Bugfix on 0.0.6 (the version introducing
19235 HiddenServiceDir); fixes bug 3289.
19236 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
19237 part of bug 2748; bugfix on 0.2.0.10-alpha.
19238 - Log malformed requests for rendezvous descriptors as protocol
19239 warnings, not warnings. Also, use a more informative log message
19240 in case someone sees it at log level warning without prior
19241 info-level messages. Fixes the other part of bug 2748; bugfix
19243 - Clear the table recording the time of the last request for each
19244 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
19245 Previously, we would clear our HS descriptor cache on SIGNAL
19246 NEWNYM, but if we had previously retrieved a descriptor (or tried
19247 to) from every directory responsible for it, we would refuse to
19248 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
19250 - Fix a log message that said "bits" while displaying a value in
19251 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
19253 - When checking for 1024-bit keys, check for 1024 bits, not 128
19254 bytes. This allows Tor to correctly discard keys of length 1017
19255 through 1023. Bugfix on 0.0.9pre5.
19258 - Relays now log the reason for publishing a new relay descriptor,
19259 so we have a better chance of hunting down instances of bug 1810.
19260 Resolves ticket 3252.
19261 - Revise most log messages that refer to nodes by nickname to
19262 instead use the "$key=nickname at address" format. This should be
19263 more useful, especially since nicknames are less and less likely
19264 to be unique. Resolves ticket 3045.
19265 - Log (at info level) when purging pieces of hidden-service-client
19266 state because of SIGNAL NEWNYM.
19269 - Remove undocumented option "-F" from tor-resolve: it hasn't done
19270 anything since 0.2.1.16-rc.
19273 Changes in version 0.2.2.27-beta - 2011-05-18
19274 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
19275 release, and also adds a few more general bugfixes.
19278 - Fix a crash bug when changing bridges in a running Tor process.
19279 Fixes bug 3213; bugfix on 0.2.2.26-beta.
19280 - When the controller configures a new bridge, don't wait 10 to 60
19281 seconds before trying to fetch its descriptor. Bugfix on
19282 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
19285 - Require that onion keys have exponent 65537 in microdescriptors too.
19286 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
19287 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
19288 Changed the limit to 512 characters by removing base64 newlines.
19289 Fixes bug 2752. Fix by Michael Yakubovich.
19290 - When a client starts or stops using bridges, never use a circuit
19291 that was built before the configuration change. This behavior could
19292 put at risk a user who uses bridges to ensure that her traffic
19293 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
19297 Changes in version 0.2.2.26-beta - 2011-05-17
19298 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
19299 also introduces a new "socksport auto" approach that should make it
19300 easier to run multiple Tors on the same system, and does a lot of
19301 cleanup to get us closer to a release candidate.
19303 o Security/privacy fixes:
19304 - Replace all potentially sensitive memory comparison operations
19305 with versions whose runtime does not depend on the data being
19306 compared. This will help resist a class of attacks where an
19307 adversary can use variations in timing information to learn
19308 sensitive data. Fix for one case of bug 3122. (Safe memcmp
19309 implementation by Robert Ransom based partially on code by DJB.)
19310 - When receiving a hidden service descriptor, check that it is for
19311 the hidden service we wanted. Previously, Tor would store any
19312 hidden service descriptors that a directory gave it, whether it
19313 wanted them or not. This wouldn't have let an attacker impersonate
19314 a hidden service, but it did let directories pre-seed a client
19315 with descriptors that it didn't want. Bugfix on 0.0.6.
19316 - On SIGHUP, do not clear out all TrackHostExits mappings, client
19317 DNS cache entries, and virtual address mappings: that's what
19318 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
19321 - The options SocksPort, ControlPort, and so on now all accept a
19322 value "auto" that opens a socket on an OS-selected port. A
19323 new ControlPortWriteToFile option tells Tor to write its
19324 actual control port or ports to a chosen file. If the option
19325 ControlPortFileGroupReadable is set, the file is created as
19326 group-readable. Now users can run two Tor clients on the same
19327 system without needing to manually mess with parameters. Resolves
19328 part of ticket 3076.
19329 - Set SO_REUSEADDR on all sockets, not just listeners. This should
19330 help busy exit nodes avoid running out of useable ports just
19331 because all the ports have been used in the near past. Resolves
19335 - New "GETINFO net/listeners/(type)" controller command to return
19336 a list of addresses and ports that are bound for listeners for a
19337 given connection type. This is useful when the user has configured
19338 "SocksPort auto" and the controller needs to know which port got
19339 chosen. Resolves another part of ticket 3076.
19340 - Add a new ControlSocketsGroupWritable configuration option: when
19341 it is turned on, ControlSockets are group-writeable by the default
19342 group of the current user. Patch by Jérémy Bobbio; implements
19344 - Tor now refuses to create a ControlSocket in a directory that is
19345 world-readable (or group-readable if ControlSocketsGroupWritable
19346 is 0). This is necessary because some operating systems do not
19347 enforce permissions on an AF_UNIX sockets. Permissions on the
19348 directory holding the socket, however, seems to work everywhere.
19349 - Rate-limit a warning about failures to download v2 networkstatus
19350 documents. Resolves part of bug 1352.
19351 - Backport code from 0.2.3.x that allows directory authorities to
19352 clean their microdescriptor caches. Needed to resolve bug 2230.
19353 - When an HTTPS proxy reports "403 Forbidden", we now explain
19354 what it means rather than calling it an unexpected status code.
19355 Closes bug 2503. Patch from Michael Yakubovich.
19356 - Update to the May 1 2011 Maxmind GeoLite Country database.
19359 - Authorities now clean their microdesc cache periodically and when
19360 reading from disk initially, not only when adding new descriptors.
19361 This prevents a bug where we could lose microdescriptors. Bugfix
19362 on 0.2.2.6-alpha. Fixes bug 2230.
19363 - Do not crash when our configuration file becomes unreadable, for
19364 example due to a permissions change, between when we start up
19365 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
19367 - Avoid a bug that would keep us from replacing a microdescriptor
19368 cache on Windows. (We would try to replace the file while still
19369 holding it open. That's fine on Unix, but Windows doesn't let us
19370 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
19371 - Add missing explanations for the authority-related torrc options
19372 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
19373 man page. Resolves issue 2379.
19374 - As an authority, do not upload our own vote or signature set to
19375 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
19376 it would get flagged as a duplicate. Resolves bug 3026.
19377 - Accept hidden service descriptors if we think we might be a hidden
19378 service directory, regardless of what our consensus says. This
19379 helps robustness, since clients and hidden services can sometimes
19380 have a more up-to-date view of the network consensus than we do,
19381 and if they think that the directory authorities list us a HSDir,
19382 we might actually be one. Related to bug 2732; bugfix on
19384 - When a controller changes TrackHostExits, remove mappings for
19385 hosts that should no longer have their exits tracked. Bugfix on
19387 - When a controller changes VirtualAddrNetwork, remove any mappings
19388 for hosts that were automapped to the old network. Bugfix on
19390 - When a controller changes one of the AutomapHosts* options, remove
19391 any mappings for hosts that should no longer be automapped. Bugfix
19393 - Do not reset the bridge descriptor download status every time we
19394 re-parse our configuration or get a configuration change. Fixes
19395 bug 3019; bugfix on 0.2.0.3-alpha.
19397 o Minor bugfixes (code cleanup):
19398 - When loading the microdesc journal, remember its current size.
19399 In 0.2.2, this helps prevent the microdesc journal from growing
19400 without limit on authorities (who are the only ones to use it in
19401 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
19402 Fix posted by "cypherpunks."
19403 - The microdesc journal is supposed to get rebuilt only if it is
19404 at least _half_ the length of the store, not _twice_ the length
19405 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
19406 - Fix a potential null-pointer dereference while computing a
19407 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
19409 - Avoid a possible null-pointer dereference when rebuilding the mdesc
19410 cache without actually having any descriptors to cache. Bugfix on
19411 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
19412 - If we fail to compute the identity digest of a v3 legacy keypair,
19413 warn, and don't use a buffer-full of junk instead. Bugfix on
19414 0.2.1.1-alpha; fixes bug 3106.
19415 - Resolve an untriggerable issue in smartlist_string_num_isin(),
19416 where if the function had ever in the future been used to check
19417 for the presence of a too-large number, it would have given an
19418 incorrect result. (Fortunately, we only used it for 16-bit
19419 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
19420 - Require that introduction point keys and onion handshake keys
19421 have a public exponent of 65537. Starts to fix bug 3207; bugfix
19424 o Removed features:
19425 - Caches no longer download and serve v2 networkstatus documents
19426 unless FetchV2Networkstatus flag is set: these documents haven't
19427 haven't been used by clients or relays since 0.2.0.x. Resolves
19431 Changes in version 0.2.3.1-alpha - 2011-05-05
19432 Tor 0.2.3.1-alpha adds some new experimental features, including support
19433 for an improved network IO backend, IOCP networking on Windows,
19434 microdescriptor caching, "fast-start" support for streams, and automatic
19435 home router configuration. There are also numerous internal improvements
19436 to try to make the code easier for developers to work with.
19438 This is the first alpha release in a new series, so expect there to be
19439 bugs. Users who would rather test out a more stable branch should
19440 stay with 0.2.2.x for now.
19443 - Tor can now optionally build with the "bufferevents" buffered IO
19444 backend provided by Libevent 2. To use this feature, make sure you
19445 have the latest possible version of Libevent, and pass the
19446 --enable-bufferevents flag to configure when building Tor from
19447 source. This feature will make our networking code more flexible,
19448 let us stack layers on each other, and let us use more efficient
19449 zero-copy transports where available.
19450 - As an experimental feature, Tor can use IOCP for networking on Windows.
19451 Once this code is tuned and optimized, it promises much better
19452 performance than the select-based backend we've used in the past. To
19453 try this feature, you must build Tor with Libevent 2, configure Tor
19454 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
19455 your torrc. There are known bugs here: only try this if you can help
19456 debug it as it breaks.
19457 - The EntryNodes option can now include country codes like {de} or IP
19458 addresses or network masks. Previously we had disallowed these options
19459 because we didn't have an efficient way to keep the list up to
19460 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
19461 - Exit nodes now accept and queue data on not-yet-connected streams.
19462 Previously, the client wasn't allowed to send data until the stream was
19463 connected, which slowed down all connections. This change will enable
19464 clients to perform a "fast-start" on streams and send data without
19465 having to wait for a confirmation that the stream has opened. (Patch
19466 from Ian Goldberg; implements the server side of Proposal 174.)
19467 - Tor now has initial support for automatic port mapping on the many
19468 home routers that support NAT-PMP or UPnP. (Not yet supported on
19469 Windows). To build the support code, you'll need to have libnatpnp
19470 library and/or the libminiupnpc library, and you'll need to enable the
19471 feature specifically by passing "--enable-upnp" and/or
19472 "--enable-natpnp" to configure. To turn it on, use the new
19473 PortForwarding option.
19474 - Caches now download, cache, and serve multiple "flavors" of the
19475 consensus, including a flavor that describes microdescriptors.
19476 - Caches now download, cache, and serve microdescriptors -- small
19477 summaries of router descriptors that are authenticated by all of the
19478 directory authorities. Once enough caches are running this code,
19479 clients will be able to save significant amounts of directory bandwidth
19480 by downloading microdescriptors instead of router descriptors.
19483 - Make logging resolution configurable with a new LogTimeGranularity
19484 option, and change the default from 1 millisecond to 1 second.
19485 Implements enhancement 1668.
19486 - We log which torrc file we're using on startup. Implements ticket
19488 - Ordinarily, Tor does not count traffic from private addresses (like
19489 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
19490 There is now a new option, CountPrivateBandwidth, to disable this
19491 behavior. Patch from Daniel Cagara.
19492 - New --enable-static-tor configure option for building Tor as
19493 statically as possible. Idea, general hackery and thoughts from
19494 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
19496 - If you set the NumCPUs option to 0, Tor will now try to detect how
19497 many CPUs you have. This is the new default behavior.
19498 - Turn on directory request statistics by default and include them in
19499 extra-info descriptors. Don't break if we have no GeoIP database.
19500 - Relays that set "ConnDirectionStatistics 1" write statistics on the
19501 bidirectional use of connections to disk every 24 hours.
19502 - Add a GeoIP file digest to the extra-info descriptor. Implements
19504 - The NodeFamily option -- which let you declare that you want to
19505 consider nodes to be part of a family whether they list themselves
19506 that way or not -- now allows IP address ranges and country codes.
19507 - Add a new 'Heartbeat' log message type to periodically log a message
19508 describing Tor's status at level Notice. This feature is meant for
19509 operators who log at notice, and want to make sure that their Tor
19510 server is still working. Implementation by George Kadianakis.
19512 o Minor bugfixes (on 0.2.2.25-alpha):
19513 - When loading the microdesc journal, remember its current size.
19514 In 0.2.2, this helps prevent the microdesc journal from growing
19515 without limit on authorities (who are the only ones to use it in
19516 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
19517 Fix posted by "cypherpunks."
19518 - The microdesc journal is supposed to get rebuilt only if it is
19519 at least _half_ the length of the store, not _twice_ the length
19520 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
19521 - If as an authority we fail to compute the identity digest of a v3
19522 legacy keypair, warn, and don't use a buffer-full of junk instead.
19523 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
19524 - Authorities now clean their microdesc cache periodically and when
19525 reading from disk initially, not only when adding new descriptors.
19526 This prevents a bug where we could lose microdescriptors. Bugfix
19529 o Minor features (controller):
19530 - Add a new SIGNAL event to the controller interface so that
19531 controllers can be notified when Tor handles a signal. Resolves
19532 issue 1955. Patch by John Brooks.
19533 - Add a new GETINFO option to get total bytes read and written. Patch
19534 from pipe, revised by atagar. Resolves ticket 2345.
19535 - Implement some GETINFO controller fields to provide information about
19536 the Tor process's pid, euid, username, and resource limits.
19539 - Our build system requires automake 1.6 or later to create the
19540 Makefile.in files. Previously, you could have used 1.4.
19541 This only affects developers and people building Tor from git;
19542 people who build Tor from the source distribution without changing
19543 the Makefile.am files should be fine.
19544 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
19545 so on. This is more robust against some of the failure modes
19546 associated with running the autotools pieces on their own.
19548 o Minor packaging issues:
19549 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
19550 already created. Patch from Andreas Stieger. Fixes bug 2573.
19552 o Code simplifications and refactoring:
19553 - A major revision to our internal node-selecting and listing logic.
19554 Tor already had at least two major ways to look at the question of
19555 "which Tor servers do we know about": a list of router descriptors,
19556 and a list of entries in the current consensus. With
19557 microdescriptors, we're adding a third. Having so many systems
19558 without an abstraction layer over them was hurting the codebase.
19559 Now, we have a new "node_t" abstraction that presents a consistent
19560 interface to a client's view of a Tor node, and holds (nearly) all
19561 of the mutable state formerly in routerinfo_t and routerstatus_t.
19562 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
19563 no longer link against Libevent: they never used it, but
19564 our library structure used to force them to link it.
19566 o Removed features:
19567 - Remove some old code to work around even older versions of Tor that
19568 used forked processes to handle DNS requests. Such versions of Tor
19569 are no longer in use as servers.
19571 o Documentation fixes:
19572 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
19573 - Add missing documentation for the authority-related torrc options
19574 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
19578 Changes in version 0.2.2.25-alpha - 2011-04-29
19579 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
19580 robust, routers no longer overreport their bandwidth, Win7 should crash
19581 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
19582 now prevents hidden service-related activity from being linkable. It
19583 provides more information to Vidalia so you can see if your bridge is
19584 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
19585 StrictNodes configuration options to make them more reliable, more
19586 understandable, and more regularly applied. If you use those options,
19587 please see the revised documentation for them in the manual page.
19590 - Relays were publishing grossly inflated bandwidth values because
19591 they were writing their state files wrong--now they write the
19592 correct value. Also, resume reading bandwidth history from the
19593 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
19594 - Improve hidden service robustness: When we find that we have
19595 extended a hidden service's introduction circuit to a relay not
19596 listed as an introduction point in the HS descriptor we currently
19597 have, retry with an introduction point from the current
19598 descriptor. Previously we would just give up. Fixes bugs 1024 and
19599 1930; bugfix on 0.2.0.10-alpha.
19600 - Clients now stop trying to use an exit node associated with a given
19601 destination by TrackHostExits if they fail to reach that exit node.
19602 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
19603 - Fix crash bug on platforms where gmtime and localtime can return
19604 NULL. Windows 7 users were running into this one. Fixes part of bug
19605 2077. Bugfix on all versions of Tor. Found by boboper.
19607 o Security and stability fixes:
19608 - Don't double-free a parsable, but invalid, microdescriptor, even if
19609 it is followed in the blob we're parsing by an unparsable
19610 microdescriptor. Fixes an issue reported in a comment on bug 2954.
19611 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
19612 - If the Nickname configuration option isn't given, Tor would pick a
19613 nickname based on the local hostname as the nickname for a relay.
19614 Because nicknames are not very important in today's Tor and the
19615 "Unnamed" nickname has been implemented, this is now problematic
19616 behavior: It leaks information about the hostname without being
19617 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
19618 introduced the Unnamed nickname. Reported by tagnaq.
19619 - Fix an uncommon assertion failure when running with DNSPort under
19620 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
19621 - Avoid linkability based on cached hidden service descriptors: forget
19622 all hidden service descriptors cached as a client when processing a
19623 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
19626 - Export GeoIP information on bridge usage to controllers even if we
19627 have not yet been running for 24 hours. Now Vidalia bridge operators
19628 can get more accurate and immediate feedback about their
19629 contributions to the network.
19631 o Major features and bugfixes (node selection):
19632 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
19633 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
19634 options. Previously, we had been ambiguous in describing what
19635 counted as an "exit" node, and what operations exactly "StrictNodes
19636 0" would permit. This created confusion when people saw nodes built
19637 through unexpected circuits, and made it hard to tell real bugs from
19638 surprises. Now the intended behavior is:
19639 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
19640 a node that delivers user traffic outside the Tor network.
19641 . "Entry", in the context of EntryNodes, means a node used as the
19642 first hop of a multihop circuit. It doesn't include direct
19643 connections to directory servers.
19644 . "ExcludeNodes" applies to all nodes.
19645 . "StrictNodes" changes the behavior of ExcludeNodes only. When
19646 StrictNodes is set, Tor should avoid all nodes listed in
19647 ExcludeNodes, even when it will make user requests fail. When
19648 StrictNodes is *not* set, then Tor should follow ExcludeNodes
19649 whenever it can, except when it must use an excluded node to
19650 perform self-tests, connect to a hidden service, provide a
19651 hidden service, fulfill a .exit request, upload directory
19652 information, or fetch directory information.
19653 Collectively, the changes to implement the behavior fix bug 1090.
19654 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
19655 a node is listed in both, it's treated as excluded.
19656 - ExcludeNodes now applies to directory nodes -- as a preference if
19657 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
19658 Don't exclude all the directory authorities and set StrictNodes to 1
19659 unless you really want your Tor to break.
19660 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
19661 - ExcludeExitNodes now overrides .exit requests.
19662 - We don't use bridges listed in ExcludeNodes.
19663 - When StrictNodes is 1:
19664 . We now apply ExcludeNodes to hidden service introduction points
19665 and to rendezvous points selected by hidden service users. This
19666 can make your hidden service less reliable: use it with caution!
19667 . If we have used ExcludeNodes on ourself, do not try relay
19668 reachability self-tests.
19669 . If we have excluded all the directory authorities, we will not
19670 even try to upload our descriptor if we're a relay.
19671 . Do not honor .exit requests to an excluded node.
19672 - Remove a misfeature that caused us to ignore the Fast/Stable flags
19673 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
19674 - When the set of permitted nodes changes, we now remove any mappings
19675 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
19677 - We never cannibalize a circuit that had excluded nodes on it, even
19678 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
19679 - Revert a change where we would be laxer about attaching streams to
19680 circuits than when building the circuits. This was meant to prevent
19681 a set of bugs where streams were never attachable, but our improved
19682 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
19683 - Keep track of how many times we launch a new circuit to handle a
19684 given stream. Too many launches could indicate an inconsistency
19685 between our "launch a circuit to handle this stream" logic and our
19686 "attach this stream to one of the available circuits" logic.
19687 - Improve log messages related to excluded nodes.
19690 - Fix a spurious warning when moving from a short month to a long
19691 month on relays with month-based BandwidthAccounting. Bugfix on
19692 0.2.2.17-alpha; fixes bug 3020.
19693 - When a client finds that an origin circuit has run out of 16-bit
19694 stream IDs, we now mark it as unusable for new streams. Previously,
19695 we would try to close the entire circuit. Bugfix on 0.0.6.
19696 - Add a forgotten cast that caused a compile warning on OS X 10.6.
19697 Bugfix on 0.2.2.24-alpha.
19698 - Be more careful about reporting the correct error from a failed
19699 connect() system call. Under some circumstances, it was possible to
19700 look at an incorrect value for errno when sending the end reason.
19701 Bugfix on 0.1.0.1-rc.
19702 - Correctly handle an "impossible" overflow cases in connection byte
19703 counting, where we write or read more than 4GB on an edge connection
19704 in a single second. Bugfix on 0.1.2.8-beta.
19705 - Correct the warning displayed when a rendezvous descriptor exceeds
19706 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
19708 - Clients and hidden services now use HSDir-flagged relays for hidden
19709 service descriptor downloads and uploads even if the relays have no
19710 DirPort set and the client has disabled TunnelDirConns. This will
19711 eventually allow us to give the HSDir flag to relays with no
19712 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
19713 - Downgrade "no current certificates known for authority" message from
19714 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
19715 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
19716 2917. Bugfix on 0.1.1.1-alpha.
19717 - Only limit the lengths of single HS descriptors, even when multiple
19718 HS descriptors are published to an HSDir relay in a single POST
19719 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
19720 - Write the current time into the LastWritten line in our state file,
19721 rather than the time from the previous write attempt. Also, stop
19722 trying to use a time of -1 in our log statements. Fixes bug 3039;
19723 bugfix on 0.2.2.14-alpha.
19724 - Be more consistent in our treatment of file system paths. "~" should
19725 get expanded to the user's home directory in the Log config option.
19726 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
19727 feature for the -f and --DataDirectory options.
19730 - Make sure every relay writes a state file at least every 12 hours.
19731 Previously, a relay could go for weeks without writing its state
19732 file, and on a crash could lose its bandwidth history, capacity
19733 estimates, client country statistics, and so on. Addresses bug 3012.
19734 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
19735 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
19736 clients are already deprecated because of security bugs.
19737 - Don't allow v0 hidden service authorities to act as clients.
19738 Required by fix for bug 3000.
19739 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
19740 by fix for bug 3000.
19741 - Ensure that no empty [dirreq-](read|write)-history lines are added
19742 to an extrainfo document. Implements ticket 2497.
19744 o Code simplification and refactoring:
19745 - Remove workaround code to handle directory responses from servers
19746 that had bug 539 (they would send HTTP status 503 responses _and_
19747 send a body too). Since only server versions before
19748 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
19749 keep the workaround in place.
19750 - Remove the old 'fuzzy time' logic. It was supposed to be used for
19751 handling calculations where we have a known amount of clock skew and
19752 an allowed amount of unknown skew. But we only used it in three
19753 places, and we never adjusted the known/unknown skew values. This is
19754 still something we might want to do someday, but if we do, we'll
19755 want to do it differently.
19756 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
19757 None of the cases where we did this before were wrong, but by making
19758 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
19759 - Use GetTempDir to find the proper temporary directory location on
19760 Windows when generating temporary files for the unit tests. Patch by
19764 Changes in version 0.2.2.24-alpha - 2011-04-08
19765 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
19766 prevented Tor clients from effectively using "multihomed" bridges,
19767 that is, bridges that listen on multiple ports or IP addresses so users
19768 can continue to use some of their addresses even if others get blocked.
19771 - Fix a bug where bridge users who configure the non-canonical
19772 address of a bridge automatically switch to its canonical
19773 address. If a bridge listens at more than one address, it should be
19774 able to advertise those addresses independently and any non-blocked
19775 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
19777 - If you configured Tor to use bridge A, and then quit and
19778 configured Tor to use bridge B instead, it would happily continue
19779 to use bridge A if it's still reachable. While this behavior is
19780 a feature if your goal is connectivity, in some scenarios it's a
19781 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
19782 - Directory authorities now use data collected from their own
19783 uptime observations when choosing whether to assign the HSDir flag
19784 to relays, instead of trusting the uptime value the relay reports in
19785 its descriptor. This change helps prevent an attack where a small
19786 set of nodes with frequently-changing identity keys can blackhole
19787 a hidden service. (Only authorities need upgrade; others will be
19788 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
19791 - When we restart our relay, we might get a successful connection
19792 from the outside before we've started our reachability tests,
19793 triggering a warning: "ORPort found reachable, but I have no
19794 routerinfo yet. Failing to inform controller of success." This
19795 bug was harmless unless Tor is running under a controller
19796 like Vidalia, in which case the controller would never get a
19797 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
19799 - Make directory authorities more accurate at recording when
19800 relays that have failed several reachability tests became
19801 unreachable, so we can provide more accuracy at assigning Stable,
19802 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
19803 - Fix an issue that prevented static linking of libevent on
19804 some platforms (notably Linux). Fixes bug 2698; bugfix on
19805 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
19806 the --with-static-libevent configure option).
19807 - We now ask the other side of a stream (the client or the exit)
19808 for more data on that stream when the amount of queued data on
19809 that stream dips low enough. Previously, we wouldn't ask the
19810 other side for more data until either it sent us more data (which
19811 it wasn't supposed to do if it had exhausted its window!) or we
19812 had completely flushed all our queued data. This flow control fix
19813 should improve throughput. Fixes bug 2756; bugfix on the earliest
19814 released versions of Tor (svn commit r152).
19815 - Avoid a double-mark-for-free warning when failing to attach a
19816 transparent proxy connection. (We thought we had fixed this in
19817 0.2.2.23-alpha, but it turns out our fix was checking the wrong
19818 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
19819 bug) and 0.2.2.23-alpha (the incorrect fix).
19820 - When warning about missing zlib development packages during compile,
19821 give the correct package names. Bugfix on 0.2.0.1-alpha.
19824 - Directory authorities now log the source of a rejected POSTed v3
19825 networkstatus vote.
19826 - Make compilation with clang possible when using
19827 --enable-gcc-warnings by removing two warning options that clang
19828 hasn't implemented yet and by fixing a few warnings. Implements
19830 - When expiring circuits, use microsecond timers rather than
19831 one-second timers. This can avoid an unpleasant situation where a
19832 circuit is launched near the end of one second and expired right
19833 near the beginning of the next, and prevent fluctuations in circuit
19835 - Use computed circuit-build timeouts to decide when to launch
19836 parallel introduction circuits for hidden services. (Previously,
19837 we would retry after 15 seconds.)
19838 - Update to the April 1 2011 Maxmind GeoLite Country database.
19841 - Create the /var/run/tor directory on startup on OpenSUSE if it is
19842 not already created. Patch from Andreas Stieger. Fixes bug 2573.
19844 o Documentation changes:
19845 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
19846 - Resolve all doxygen warnings except those for missing documentation.
19848 - Add doxygen documentation for more functions, fields, and types.
19851 Changes in version 0.2.2.23-alpha - 2011-03-08
19852 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
19853 they restart they don't lose their bandwidth capacity estimate. This
19854 release also fixes a diverse set of user-facing bugs, ranging from
19855 relays overrunning their rate limiting to clients falsely warning about
19856 clock skew to bridge descriptor leaks by our bridge directory authority.
19859 - Stop sending a CLOCK_SKEW controller status event whenever
19860 we fetch directory information from a relay that has a wrong clock.
19861 Instead, only inform the controller when it's a trusted authority
19862 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
19863 the rest of bug 1074.
19864 - Fix an assert in parsing router descriptors containing IPv6
19865 addresses. This one took down the directory authorities when
19866 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
19867 - Make the bridge directory authority refuse to answer directory
19868 requests for "all" descriptors. It used to include bridge
19869 descriptors in its answer, which was a major information leak.
19870 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
19871 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
19872 Tor would ignore their RelayBandwidthBurst setting,
19873 potentially using more bandwidth than expected. Bugfix on
19874 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
19875 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
19876 hidserv" in her torrc. The 'hidserv' argument never controlled
19877 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
19880 - Relays now save observed peak bandwidth throughput rates to their
19881 state file (along with total usage, which was already saved)
19882 so that they can determine their correct estimated bandwidth on
19883 restart. Resolves bug 1863, where Tor relays would reset their
19884 estimated bandwidth to 0 after restarting.
19885 - Directory authorities now take changes in router IP address and
19886 ORPort into account when determining router stability. Previously,
19887 if a router changed its IP or ORPort, the authorities would not
19888 treat it as having any downtime for the purposes of stability
19889 calculation, whereas clients would experience downtime since the
19890 change could take a while to propagate to them. Resolves issue 1035.
19891 - Enable Address Space Layout Randomization (ASLR) and Data Execution
19892 Prevention (DEP) by default on Windows to make it harder for
19893 attackers to exploit vulnerabilities. Patch from John Brooks.
19895 o Minor bugfixes (on 0.2.1.x and earlier):
19896 - Fix a rare crash bug that could occur when a client was configured
19897 with a large number of bridges. Fixes bug 2629; bugfix on
19898 0.2.1.2-alpha. Bugfix by trac user "shitlei".
19899 - Avoid a double mark-for-free warning when failing to attach a
19900 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
19902 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
19903 found by "cypherpunks". This bug was introduced before the first
19904 Tor release, in svn commit r110.
19905 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
19906 don't mention them in the manpage. Fixes bug 2450; issue
19907 spotted by keb and G-Lo.
19908 - Fix a bug in bandwidth history state parsing that could have been
19909 triggered if a future version of Tor ever changed the timing
19910 granularity at which bandwidth history is measured. Bugfix on
19911 Tor 0.1.1.11-alpha.
19912 - When a relay decides that its DNS is too broken for it to serve
19913 as an exit server, it advertised itself as a non-exit, but
19914 continued to act as an exit. This could create accidental
19915 partitioning opportunities for users. Instead, if a relay is
19916 going to advertise reject *:* as its exit policy, it should
19917 really act with exit policy "reject *:*". Fixes bug 2366.
19918 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
19919 - In the special case where you configure a public exit relay as your
19920 bridge, Tor would be willing to use that exit relay as the last
19921 hop in your circuit as well. Now we fail that circuit instead.
19922 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
19923 - Fix a bug with our locking implementation on Windows that couldn't
19924 correctly detect when a file was already locked. Fixes bug 2504,
19925 bugfix on 0.2.1.6-alpha.
19926 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
19927 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
19929 - Set target port in get_interface_address6() correctly. Bugfix
19930 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
19931 - Directory authorities are now more robust to hops back in time
19932 when calculating router stability. Previously, if a run of uptime
19933 or downtime appeared to be negative, the calculation could give
19934 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
19936 - Fix an assert that got triggered when using the TestingTorNetwork
19937 configuration option and then issuing a GETINFO config-text control
19938 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
19940 o Minor bugfixes (on 0.2.2.x):
19941 - Clients should not weight BadExit nodes as Exits in their node
19942 selection. Similarly, directory authorities should not count BadExit
19943 bandwidth as Exit bandwidth when computing bandwidth-weights.
19944 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
19945 - Correctly clear our dir_read/dir_write history when there is an
19946 error parsing any bw history value from the state file. Bugfix on
19947 Tor 0.2.2.15-alpha.
19948 - Resolve a bug in verifying signatures of directory objects
19949 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
19950 Fixes bug 2409. Found by "piebeer".
19951 - Bridge authorities no longer crash on SIGHUP when they try to
19952 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
19956 - Log less aggressively about circuit timeout changes, and improve
19957 some other circuit timeout messages. Resolves bug 2004.
19958 - Log a little more clearly about the times at which we're no longer
19959 accepting new connections. Resolves bug 2181.
19960 - Reject attempts at the client side to open connections to private
19961 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
19962 a randomly chosen exit node. Attempts to do so are always
19963 ill-defined, generally prevented by exit policies, and usually
19964 in error. This will also help to detect loops in transparent
19965 proxy configurations. You can disable this feature by setting
19966 "ClientRejectInternalAddresses 0" in your torrc.
19967 - Always treat failure to allocate an RSA key as an unrecoverable
19969 - Update to the March 1 2011 Maxmind GeoLite Country database.
19971 o Minor features (log subsystem):
19972 - Add documentation for configuring logging at different severities in
19973 different log domains. We've had this feature since 0.2.1.1-alpha,
19974 but for some reason it never made it into the manpage. Fixes
19976 - Make it simpler to specify "All log domains except for A and B".
19977 Previously you needed to say "[*,~A,~B]". Now you can just say
19979 - Add a "LogMessageDomains 1" option to include the domains of log
19980 messages along with the messages. Without this, there's no way
19981 to use log domains without reading the source or doing a lot
19984 o Packaging changes:
19985 - Stop shipping the Tor specs files and development proposal documents
19986 in the tarball. They are now in a separate git repository at
19987 git://git.torproject.org/torspec.git
19990 Changes in version 0.2.1.30 - 2011-02-23
19991 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
19992 change is a slight tweak to Tor's TLS handshake that makes relays
19993 and bridges that run this new version reachable from Iran again.
19994 We don't expect this tweak will win the arms race long-term, but it
19995 buys us time until we roll out a better solution.
19998 - Stop sending a CLOCK_SKEW controller status event whenever
19999 we fetch directory information from a relay that has a wrong clock.
20000 Instead, only inform the controller when it's a trusted authority
20001 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
20002 the rest of bug 1074.
20003 - Fix a bounds-checking error that could allow an attacker to
20004 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
20005 Found by "piebeer".
20006 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
20007 Tor would ignore their RelayBandwidthBurst setting,
20008 potentially using more bandwidth than expected. Bugfix on
20009 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
20010 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
20011 hidserv" in her torrc. The 'hidserv' argument never controlled
20012 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
20015 - Adjust our TLS Diffie-Hellman parameters to match those used by
20017 - Update to the February 1 2011 Maxmind GeoLite Country database.
20020 - Check for and reject overly long directory certificates and
20021 directory tokens before they have a chance to hit any assertions.
20022 Bugfix on 0.2.1.28. Found by "doorss".
20023 - Bring the logic that gathers routerinfos and assesses the
20024 acceptability of circuits into line. This prevents a Tor OP from
20025 getting locked in a cycle of choosing its local OR as an exit for a
20026 path (due to a .exit request) and then rejecting the circuit because
20027 its OR is not listed yet. It also prevents Tor clients from using an
20028 OR running in the same instance as an exit (due to a .exit request)
20029 if the OR does not meet the same requirements expected of an OR
20030 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
20032 o Packaging changes:
20033 - Stop shipping the Tor specs files and development proposal documents
20034 in the tarball. They are now in a separate git repository at
20035 git://git.torproject.org/torspec.git
20036 - Do not include Git version tags as though they are SVN tags when
20037 generating a tarball from inside a repository that has switched
20038 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20041 Changes in version 0.2.2.22-alpha - 2011-01-25
20042 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
20043 main other change is a slight tweak to Tor's TLS handshake that makes
20044 relays and bridges that run this new version reachable from Iran again.
20045 We don't expect this tweak will win the arms race long-term, but it
20046 will buy us a bit more time until we roll out a better solution.
20049 - Fix a bounds-checking error that could allow an attacker to
20050 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
20051 Found by "piebeer".
20052 - Don't assert when changing from bridge to relay or vice versa
20053 via the controller. The assert happened because we didn't properly
20054 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
20055 bug 2433. Reported by bastik.
20058 - Adjust our TLS Diffie-Hellman parameters to match those used by
20060 - Provide a log message stating which geoip file we're parsing
20061 instead of just stating that we're parsing the geoip file.
20062 Implements ticket 2432.
20065 - Check for and reject overly long directory certificates and
20066 directory tokens before they have a chance to hit any assertions.
20067 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
20070 Changes in version 0.2.2.21-alpha - 2011-01-15
20071 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
20072 continues our recent code security audit work. The main fix resolves
20073 a remote heap overflow vulnerability that can allow remote code
20074 execution (CVE-2011-0427). Other fixes address a variety of assert
20075 and crash bugs, most of which we think are hard to exploit remotely.
20077 o Major bugfixes (security), also included in 0.2.1.29:
20078 - Fix a heap overflow bug where an adversary could cause heap
20079 corruption. This bug probably allows remote code execution
20080 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
20082 - Prevent a denial-of-service attack by disallowing any
20083 zlib-compressed data whose compression factor is implausibly
20084 high. Fixes part of bug 2324; reported by "doorss".
20085 - Zero out a few more keys in memory before freeing them. Fixes
20086 bug 2384 and part of bug 2385. These key instances found by
20087 "cypherpunks", based on Andrew Case's report about being able
20088 to find sensitive data in Tor's memory space if you have enough
20089 permissions. Bugfix on 0.0.2pre9.
20091 o Major bugfixes (crashes), also included in 0.2.1.29:
20092 - Prevent calls to Libevent from inside Libevent log handlers.
20093 This had potential to cause a nasty set of crashes, especially
20094 if running Libevent with debug logging enabled, and running
20095 Tor with a controller watching for low-severity log messages.
20096 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
20097 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
20098 underflow errors there too. Fixes the other part of bug 2324.
20099 - Fix a bug where we would assert if we ever had a
20100 cached-descriptors.new file (or another file read directly into
20101 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
20102 on 0.2.1.25. Found by doorss.
20103 - Fix some potential asserts and parsing issues with grossly
20104 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
20107 o Minor bugfixes (other), also included in 0.2.1.29:
20108 - Fix a bug with handling misformed replies to reverse DNS lookup
20109 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
20110 bug reported by doorss.
20111 - Fix compilation on mingw when a pthreads compatibility library
20112 has been installed. (We don't want to use it, so we shouldn't
20113 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
20114 - Fix a bug where we would declare that we had run out of virtual
20115 addresses when the address space was only half-exhausted. Bugfix
20117 - Correctly handle the case where AutomapHostsOnResolve is set but
20118 no virtual addresses are available. Fixes bug 2328; bugfix on
20119 0.1.2.1-alpha. Bug found by doorss.
20120 - Correctly handle wrapping around when we run out of virtual
20121 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
20123 o Minor features, also included in 0.2.1.29:
20124 - Update to the January 1 2011 Maxmind GeoLite Country database.
20125 - Introduce output size checks on all of our decryption functions.
20127 o Build changes, also included in 0.2.1.29:
20128 - Tor does not build packages correctly with Automake 1.6 and earlier;
20129 added a check to Makefile.am to make sure that we're building with
20130 Automake 1.7 or later.
20131 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
20132 because we built it with a too-old version of automake. Thus that
20133 release broke ./configure --enable-openbsd-malloc, which is popular
20134 among really fast exit relays on Linux.
20136 o Major bugfixes, new in 0.2.2.21-alpha:
20137 - Prevent crash/heap corruption when the cbtnummodes consensus
20138 parameter is set to 0 or large values. Fixes bug 2317; bugfix
20141 o Major features, new in 0.2.2.21-alpha:
20142 - Introduce minimum/maximum values that clients will believe
20143 from the consensus. Now we'll have a better chance to avoid crashes
20144 or worse when a consensus param has a weird value.
20146 o Minor features, new in 0.2.2.21-alpha:
20147 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
20148 used on bridges, and it makes bridge scanning somewhat easier.
20149 - If writing the state file to disk fails, wait up to an hour before
20150 retrying again, rather than trying again each second. Fixes bug
20151 2346; bugfix on Tor 0.1.1.3-alpha.
20152 - Make Libevent log messages get delivered to controllers later,
20153 and not from inside the Libevent log handler. This prevents unsafe
20154 reentrant Libevent calls while still letting the log messages
20156 - Detect platforms that brokenly use a signed size_t, and refuse to
20157 build there. Found and analyzed by doorss and rransom.
20158 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
20161 o Minor bugfixes, new in 0.2.2.21-alpha:
20162 - Handle SOCKS messages longer than 128 bytes long correctly, rather
20163 than waiting forever for them to finish. Fixes bug 2330; bugfix
20164 on 0.2.0.16-alpha. Found by doorss.
20165 - Add assertions to check for overflow in arguments to
20166 base32_encode() and base32_decode(); fix a signed-unsigned
20167 comparison there too. These bugs are not actually reachable in Tor,
20168 but it's good to prevent future errors too. Found by doorss.
20169 - Correctly detect failures to create DNS requests when using Libevent
20170 versions before v2. (Before Libevent 2, we used our own evdns
20171 implementation. Its return values for Libevent's evdns_resolve_*()
20172 functions are not consistent with those from Libevent.) Fixes bug
20173 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
20175 o Documentation, new in 0.2.2.21-alpha:
20176 - Document the default socks host and port (127.0.0.1:9050) for
20180 Changes in version 0.2.1.29 - 2011-01-15
20181 Tor 0.2.1.29 continues our recent code security audit work. The main
20182 fix resolves a remote heap overflow vulnerability that can allow remote
20183 code execution. Other fixes address a variety of assert and crash bugs,
20184 most of which we think are hard to exploit remotely.
20186 o Major bugfixes (security):
20187 - Fix a heap overflow bug where an adversary could cause heap
20188 corruption. This bug probably allows remote code execution
20189 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
20191 - Prevent a denial-of-service attack by disallowing any
20192 zlib-compressed data whose compression factor is implausibly
20193 high. Fixes part of bug 2324; reported by "doorss".
20194 - Zero out a few more keys in memory before freeing them. Fixes
20195 bug 2384 and part of bug 2385. These key instances found by
20196 "cypherpunks", based on Andrew Case's report about being able
20197 to find sensitive data in Tor's memory space if you have enough
20198 permissions. Bugfix on 0.0.2pre9.
20200 o Major bugfixes (crashes):
20201 - Prevent calls to Libevent from inside Libevent log handlers.
20202 This had potential to cause a nasty set of crashes, especially
20203 if running Libevent with debug logging enabled, and running
20204 Tor with a controller watching for low-severity log messages.
20205 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
20206 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
20207 underflow errors there too. Fixes the other part of bug 2324.
20208 - Fix a bug where we would assert if we ever had a
20209 cached-descriptors.new file (or another file read directly into
20210 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
20211 on 0.2.1.25. Found by doorss.
20212 - Fix some potential asserts and parsing issues with grossly
20213 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
20216 o Minor bugfixes (other):
20217 - Fix a bug with handling misformed replies to reverse DNS lookup
20218 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
20219 bug reported by doorss.
20220 - Fix compilation on mingw when a pthreads compatibility library
20221 has been installed. (We don't want to use it, so we shouldn't
20222 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
20223 - Fix a bug where we would declare that we had run out of virtual
20224 addresses when the address space was only half-exhausted. Bugfix
20226 - Correctly handle the case where AutomapHostsOnResolve is set but
20227 no virtual addresses are available. Fixes bug 2328; bugfix on
20228 0.1.2.1-alpha. Bug found by doorss.
20229 - Correctly handle wrapping around to when we run out of virtual
20230 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
20231 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
20232 because we built it with a too-old version of automake. Thus that
20233 release broke ./configure --enable-openbsd-malloc, which is popular
20234 among really fast exit relays on Linux.
20237 - Update to the January 1 2011 Maxmind GeoLite Country database.
20238 - Introduce output size checks on all of our decryption functions.
20241 - Tor does not build packages correctly with Automake 1.6 and earlier;
20242 added a check to Makefile.am to make sure that we're building with
20243 Automake 1.7 or later.
20246 Changes in version 0.2.2.20-alpha - 2010-12-17
20247 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
20248 exploitable bugs. We also fix a variety of other significant bugs,
20249 change the IP address for one of our directory authorities, and update
20250 the minimum version that Tor relays must run to join the network.
20253 - Fix a remotely exploitable bug that could be used to crash instances
20254 of Tor remotely by overflowing on the heap. Remote-code execution
20255 hasn't been confirmed, but can't be ruled out. Everyone should
20256 upgrade. Bugfix on the 0.1.1 series and later.
20257 - Fix a bug that could break accounting on 64-bit systems with large
20258 time_t values, making them hibernate for impossibly long intervals.
20259 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
20260 - Fix a logic error in directory_fetches_from_authorities() that
20261 would cause all _non_-exits refusing single-hop-like circuits
20262 to fetch from authorities, when we wanted to have _exits_ fetch
20263 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
20265 - Fix a stream fairness bug that would cause newer streams on a given
20266 circuit to get preference when reading bytes from the origin or
20267 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
20268 introduced before the first Tor release, in svn revision r152.
20270 o Directory authority changes:
20271 - Change IP address and ports for gabelmoo (v3 directory authority).
20274 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
20275 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
20276 - Fix an off-by-one error in calculating some controller command
20277 argument lengths. Fortunately, this mistake is harmless since
20278 the controller code does redundant NUL termination too. Found by
20279 boboper. Bugfix on 0.1.1.1-alpha.
20280 - Do not dereference NULL if a bridge fails to build its
20281 extra-info descriptor. Found by an anonymous commenter on
20282 Trac. Bugfix on 0.2.2.19-alpha.
20285 - Update to the December 1 2010 Maxmind GeoLite Country database.
20286 - Directory authorities now reject relays running any versions of
20287 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
20288 known bugs that keep RELAY_EARLY cells from working on rendezvous
20289 circuits. Followup to fix for bug 2081.
20290 - Directory authorities now reject relays running any version of Tor
20291 older than 0.2.0.26-rc. That version is the earliest that fetches
20292 current directory information correctly. Fixes bug 2156.
20293 - Report only the top 10 ports in exit-port stats in order not to
20294 exceed the maximum extra-info descriptor length of 50 KB. Implements
20298 Changes in version 0.2.1.28 - 2010-12-17
20299 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
20300 exploitable bugs. We also took this opportunity to change the IP address
20301 for one of our directory authorities, and to update the geoip database
20305 - Fix a remotely exploitable bug that could be used to crash instances
20306 of Tor remotely by overflowing on the heap. Remote-code execution
20307 hasn't been confirmed, but can't be ruled out. Everyone should
20308 upgrade. Bugfix on the 0.1.1 series and later.
20310 o Directory authority changes:
20311 - Change IP address and ports for gabelmoo (v3 directory authority).
20314 - Update to the December 1 2010 Maxmind GeoLite Country database.
20317 Changes in version 0.2.1.27 - 2010-11-23
20318 Yet another OpenSSL security patch broke its compatibility with Tor:
20319 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
20320 also took this opportunity to fix several crash bugs, integrate a new
20321 directory authority, and update the bundled GeoIP database.
20324 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
20325 No longer set the tlsext_host_name extension on server SSL objects;
20326 but continue to set it on client SSL objects. Our goal in setting
20327 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
20328 bugfix on 0.2.1.1-alpha.
20329 - Do not log messages to the controller while shrinking buffer
20330 freelists. Doing so would sometimes make the controller connection
20331 try to allocate a buffer chunk, which would mess up the internals
20332 of the freelist and cause an assertion failure. Fixes bug 1125;
20333 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
20334 - Learn our external IP address when we're a relay or bridge, even if
20335 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
20336 where we introduced bridge relays that don't need to publish to
20337 be useful. Fixes bug 2050.
20338 - Do even more to reject (and not just ignore) annotations on
20339 router descriptors received anywhere but from the cache. Previously
20340 we would ignore such annotations at first, but cache them to disk
20341 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
20342 - When you're using bridges and your network goes away and your
20343 bridges get marked as down, recover when you attempt a new socks
20344 connection (if the network is back), rather than waiting up to an
20345 hour to try fetching new descriptors for your bridges. Bugfix on
20346 0.2.0.3-alpha; fixes bug 1981.
20349 - Move to the November 2010 Maxmind GeoLite country db (rather
20350 than the June 2009 ip-to-country GeoIP db) for our statistics that
20351 count how many users relays are seeing from each country. Now we'll
20352 have more accurate data, especially for many African countries.
20354 o New directory authorities:
20355 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
20359 - Fix an assertion failure that could occur in directory caches or
20360 bridge users when using a very short voting interval on a testing
20361 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
20363 - Enforce multiplicity rules when parsing annotations. Bugfix on
20364 0.2.0.8-alpha. Found by piebeer.
20365 - Allow handshaking OR connections to take a full KeepalivePeriod
20366 seconds to handshake. Previously, we would close them after
20367 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
20368 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
20370 - When building with --enable-gcc-warnings on OpenBSD, disable
20371 warnings in system headers. This makes --enable-gcc-warnings
20372 pass on OpenBSD 4.8.
20375 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
20376 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
20377 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
20378 Servers can start sending this code when enough clients recognize
20379 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
20380 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
20381 Patch from mingw-san.
20384 - Remove the old debian/ directory from the main Tor distribution.
20385 The official Tor-for-debian git repository lives at the URL
20386 https://git.torproject.org/debian/tor.git
20387 - Stop shipping the old doc/website/ directory in the tarball. We
20388 changed the website format in late 2010, and what we shipped in
20389 0.2.1.26 really wasn't that useful anyway.
20392 Changes in version 0.2.2.19-alpha - 2010-11-22
20393 Yet another OpenSSL security patch broke its compatibility with Tor:
20394 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
20397 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
20398 No longer set the tlsext_host_name extension on server SSL objects;
20399 but continue to set it on client SSL objects. Our goal in setting
20400 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
20401 bugfix on 0.2.1.1-alpha.
20404 - Try harder not to exceed the maximum length of 50 KB when writing
20405 statistics to extra-info descriptors. This bug was triggered by very
20406 fast relays reporting exit-port, entry, and dirreq statistics.
20407 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
20408 - Publish a router descriptor even if generating an extra-info
20409 descriptor fails. Previously we would not publish a router
20410 descriptor without an extra-info descriptor; this can cause fast
20411 exit relays collecting exit-port statistics to drop from the
20412 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
20415 Changes in version 0.2.2.18-alpha - 2010-11-16
20416 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
20417 us lately, makes unpublished bridge relays able to detect their IP
20418 address, and fixes a wide variety of other bugs to get us much closer
20419 to a stable release.
20422 - Do even more to reject (and not just ignore) annotations on
20423 router descriptors received anywhere but from the cache. Previously
20424 we would ignore such annotations at first, but cache them to disk
20425 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
20426 - Do not log messages to the controller while shrinking buffer
20427 freelists. Doing so would sometimes make the controller connection
20428 try to allocate a buffer chunk, which would mess up the internals
20429 of the freelist and cause an assertion failure. Fixes bug 1125;
20430 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
20431 - Learn our external IP address when we're a relay or bridge, even if
20432 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
20433 where we introduced bridge relays that don't need to publish to
20434 be useful. Fixes bug 2050.
20435 - Maintain separate TLS contexts and certificates for incoming and
20436 outgoing connections in bridge relays. Previously we would use the
20437 same TLS contexts and certs for incoming and outgoing connections.
20438 Bugfix on 0.2.0.3-alpha; addresses bug 988.
20439 - Maintain separate identity keys for incoming and outgoing TLS
20440 contexts in bridge relays. Previously we would use the same
20441 identity keys for incoming and outgoing TLS contexts. Bugfix on
20442 0.2.0.3-alpha; addresses the other half of bug 988.
20443 - Avoid an assertion failure when we as an authority receive a
20444 duplicate upload of a router descriptor that we already have,
20445 but which we previously considered an obsolete descriptor.
20446 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
20447 - Avoid a crash bug triggered by looking at a dangling pointer while
20448 setting the network status consensus. Found by Robert Ransom.
20449 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
20450 - Fix a logic error where servers that _didn't_ act as exits would
20451 try to keep their server lists more aggressively up to date than
20452 exits, when it was supposed to be the other way around. Bugfix
20455 o Minor bugfixes (on Tor 0.2.1.x and earlier):
20456 - When we're trying to guess whether we know our IP address as
20457 a relay, we would log various ways that we failed to guess
20458 our address, but never log that we ended up guessing it
20459 successfully. Now add a log line to help confused and anxious
20460 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
20461 - Bring the logic that gathers routerinfos and assesses the
20462 acceptability of circuits into line. This prevents a Tor OP from
20463 getting locked in a cycle of choosing its local OR as an exit for a
20464 path (due to a .exit request) and then rejecting the circuit because
20465 its OR is not listed yet. It also prevents Tor clients from using an
20466 OR running in the same instance as an exit (due to a .exit request)
20467 if the OR does not meet the same requirements expected of an OR
20468 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
20469 - Correctly describe errors that occur when generating a TLS object.
20470 Previously we would attribute them to a failure while generating a
20471 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
20473 - Enforce multiplicity rules when parsing annotations. Bugfix on
20474 0.2.0.8-alpha. Found by piebeer.
20475 - Fix warnings that newer versions of autoconf produced during
20476 ./autogen.sh. These warnings appear to be harmless in our case,
20477 but they were extremely verbose. Fixes bug 2020.
20479 o Minor bugfixes (on Tor 0.2.2.x):
20480 - Enable protection of small arrays whenever we build with gcc
20481 hardening features, not only when also building with warnings
20482 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
20485 - Make hidden services work better in private Tor networks by not
20486 requiring any uptime to join the hidden service descriptor
20487 DHT. Implements ticket 2088.
20488 - Rate-limit the "your application is giving Tor only an IP address"
20489 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
20490 - When AllowSingleHopExits is set, print a warning to explain to the
20491 relay operator why most clients are avoiding her relay.
20492 - Update to the November 1 2010 Maxmind GeoLite Country database.
20494 o Code simplifications and refactoring:
20495 - When we fixed bug 1038 we had to put in a restriction not to send
20496 RELAY_EARLY cells on rend circuits. This was necessary as long
20497 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
20498 active. Now remove this obsolete check. Resolves bug 2081.
20499 - Some options used different conventions for uppercasing of acronyms
20500 when comparing manpage and source. Fix those in favor of the
20501 manpage, as it makes sense to capitalize acronyms.
20502 - Remove the torrc.complete file. It hasn't been kept up to date
20503 and users will have better luck checking out the manpage.
20504 - Remove the obsolete "NoPublish" option; it has been flagged
20505 as obsolete and has produced a warning since 0.1.1.18-rc.
20506 - Remove everything related to building the expert bundle for OS X.
20507 It has confused many users, doesn't work right on OS X 10.6,
20508 and is hard to get rid of once installed. Resolves bug 1274.
20511 Changes in version 0.2.2.17-alpha - 2010-09-30
20512 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
20513 to use one-hop circuits (which can put the exit relays at higher risk,
20514 plus unbalance the network); fixes a big bug in bandwidth accounting
20515 for relays that want to limit their monthly bandwidth use; fixes a
20516 big pile of bugs in how clients tolerate temporary network failure;
20517 and makes our adaptive circuit build timeout feature (which improves
20518 client performance if your network is fast while not breaking things
20519 if your network is slow) better handle bad networks.
20522 - Exit relays now try harder to block exit attempts from unknown
20523 relays, to make it harder for people to use them as one-hop proxies
20524 a la tortunnel. Controlled by the refuseunknownexits consensus
20525 parameter (currently enabled), or you can override it on your
20526 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
20528 o Major bugfixes (0.2.1.x and earlier):
20529 - Fix a bug in bandwidth accounting that could make us use twice
20530 the intended bandwidth when our interval start changes due to
20531 daylight saving time. Now we tolerate skew in stored vs computed
20532 interval starts: if the start of the period changes by no more than
20533 50% of the period's duration, we remember bytes that we transferred
20534 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
20535 - Always search the Windows system directory for system DLLs, and
20536 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
20537 - When you're using bridges and your network goes away and your
20538 bridges get marked as down, recover when you attempt a new socks
20539 connection (if the network is back), rather than waiting up to an
20540 hour to try fetching new descriptors for your bridges. Bugfix on
20541 0.2.0.3-alpha; fixes bug 1981.
20543 o Major bugfixes (on 0.2.2.x):
20544 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
20546 - Fix a segfault that could happen when operating a bridge relay with
20547 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
20548 - The consensus bandwidth-weights (used by clients to choose fast
20549 relays) entered an unexpected edge case in September where
20550 Exits were much scarcer than Guards, resulting in bad weight
20551 recommendations. Now we compute them using new constraints that
20552 should succeed in all cases. Also alter directory authorities to
20553 not include the bandwidth-weights line if they fail to produce
20554 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
20555 - When weighting bridges during path selection, we used to trust
20556 the bandwidths they provided in their descriptor, only capping them
20557 at 10MB/s. This turned out to be problematic for two reasons:
20558 Bridges could claim to handle a lot more traffic then they
20559 actually would, thus making more clients pick them and have a
20560 pretty effective DoS attack. The other issue is that new bridges
20561 that might not have a good estimate for their bw capacity yet
20562 would not get used at all unless no other bridges are available
20563 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
20565 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
20566 - Ignore cannibalized circuits when recording circuit build times.
20567 This should provide for a minor performance improvement for hidden
20568 service users using 0.2.2.14-alpha, and should remove two spurious
20569 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
20570 - Simplify the logic that causes us to decide if the network is
20571 unavailable for purposes of recording circuit build times. If we
20572 receive no cells whatsoever for the entire duration of a circuit's
20573 full measured lifetime, the network is probably down. Also ignore
20574 one-hop directory fetching circuit timeouts when calculating our
20575 circuit build times. These changes should hopefully reduce the
20576 cases where we see ridiculous circuit build timeouts for people
20577 with spotty wireless connections. Fixes part of bug 1772; bugfix
20579 - Prevent the circuit build timeout from becoming larger than
20580 the maximum build time we have ever seen. Also, prevent the time
20581 period for measurement circuits from becoming larger than twice that
20582 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
20585 - When we run out of directory information such that we can't build
20586 circuits, but then get enough that we can build circuits, log when
20587 we actually construct a circuit, so the user has a better chance of
20588 knowing what's going on. Fixes bug 1362.
20589 - Be more generous with how much bandwidth we'd use up (with
20590 accounting enabled) before entering "soft hibernation". Previously,
20591 we'd refuse new connections and circuits once we'd used up 95% of
20592 our allotment. Now, we use up 95% of our allotment, AND make sure
20593 that we have no more than 500MB (or 3 hours of expected traffic,
20594 whichever is lower) remaining before we enter soft hibernation.
20595 - If we've configured EntryNodes and our network goes away and/or all
20596 our entrynodes get marked down, optimistically retry them all when
20597 a new socks application request appears. Fixes bug 1882.
20598 - Add some more defensive programming for architectures that can't
20599 handle unaligned integer accesses. We don't know of any actual bugs
20600 right now, but that's the best time to fix them. Fixes bug 1943.
20601 - Support line continuations in the torrc config file. If a line
20602 ends with a single backslash character, the newline is ignored, and
20603 the configuration value is treated as continuing on the next line.
20606 o Minor bugfixes (on 0.2.1.x and earlier):
20607 - For bandwidth accounting, calculate our expected bandwidth rate
20608 based on the time during which we were active and not in
20609 soft-hibernation during the last interval. Previously, we were
20610 also considering the time spent in soft-hibernation. If this
20611 was a long time, we would wind up underestimating our bandwidth
20612 by a lot, and skewing our wakeup time towards the start of the
20613 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
20615 o Minor bugfixes (on 0.2.2.x):
20616 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
20617 which were disabled by the circuit build timeout changes in
20618 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
20619 - Make sure we don't warn about missing bandwidth weights when
20620 choosing bridges or other relays not in the consensus. Bugfix on
20621 0.2.2.10-alpha; fixes bug 1805.
20622 - In our logs, do not double-report signatures from unrecognized
20623 authorities both as "from unknown authority" and "not
20624 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
20627 Changes in version 0.2.2.16-alpha - 2010-09-17
20628 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
20629 evident at exit relays), and also continues to resolve all the little
20630 bugs that have been filling up trac lately.
20632 o Major bugfixes (stream-level fairness):
20633 - When receiving a circuit-level SENDME for a blocked circuit, try
20634 to package cells fairly from all the streams that had previously
20635 been blocked on that circuit. Previously, we had started with the
20636 oldest stream, and allowed each stream to potentially exhaust
20637 the circuit's package window. This gave older streams on any
20638 given circuit priority over newer ones. Fixes bug 1937. Detected
20639 originally by Camilo Viecco. This bug was introduced before the
20640 first Tor release, in svn commit r152: it is the new winner of
20641 the longest-lived bug prize.
20642 - When the exit relay got a circuit-level sendme cell, it started
20643 reading on the exit streams, even if had 500 cells queued in the
20644 circuit queue already, so the circuit queue just grew and grew in
20645 some cases. We fix this by not re-enabling reading on receipt of a
20646 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
20647 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
20649 - Newly created streams were allowed to read cells onto circuits,
20650 even if the circuit's cell queue was blocked and waiting to drain.
20651 This created potential unfairness, as older streams would be
20652 blocked, but newer streams would gladly fill the queue completely.
20653 We add code to detect this situation and prevent any stream from
20654 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
20658 - Update to the September 1 2010 Maxmind GeoLite Country database.
20659 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
20660 not. This would lead to a cookie that is still not group readable.
20661 Closes bug 1843. Suggested by katmagic.
20662 - When logging a rate-limited warning, we now mention how many messages
20663 got suppressed since the last warning.
20664 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
20665 do individual connection-level rate limiting of clients. The torrc
20666 config options with the same names trump the consensus params, if
20667 both are present. Replaces the old "bwconnrate" and "bwconnburst"
20668 consensus params which were broken from 0.2.2.7-alpha through
20669 0.2.2.14-alpha. Closes bug 1947.
20670 - When a router changes IP address or port, authorities now launch
20671 a new reachability test for it. Implements ticket 1899.
20672 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
20673 2 no signature, 4 required" messages about consensus signatures
20674 easier to read, and make sure they get logged at the same severity
20675 as the messages explaining which keys are which. Fixes bug 1290.
20676 - Don't warn when we have a consensus that we can't verify because
20677 of missing certificates, unless those certificates are ones
20678 that we have been trying and failing to download. Fixes bug 1145.
20679 - If you configure your bridge with a known identity fingerprint,
20680 and the bridge authority is unreachable (as it is in at least
20681 one country now), fall back to directly requesting the descriptor
20682 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
20684 - When building with --enable-gcc-warnings on OpenBSD, disable
20685 warnings in system headers. This makes --enable-gcc-warnings
20686 pass on OpenBSD 4.8.
20688 o Minor bugfixes (on 0.2.1.x and earlier):
20689 - Authorities will now attempt to download consensuses if their
20690 own efforts to make a live consensus have failed. This change
20691 means authorities that restart will fetch a valid consensus, and
20692 it means authorities that didn't agree with the current consensus
20693 will still fetch and serve it if it has enough signatures. Bugfix
20694 on 0.2.0.9-alpha; fixes bug 1300.
20695 - Ensure DNS requests launched by "RESOLVE" commands from the
20696 controller respect the __LeaveStreamsUnattached setconf options. The
20697 same goes for requests launched via DNSPort or transparent
20698 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
20699 - Allow handshaking OR connections to take a full KeepalivePeriod
20700 seconds to handshake. Previously, we would close them after
20701 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
20702 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
20704 - Rate-limit "Failed to hand off onionskin" warnings.
20705 - Never relay a cell for a circuit we have already destroyed.
20706 Between marking a circuit as closeable and finally closing it,
20707 it may have been possible for a few queued cells to get relayed,
20708 even though they would have been immediately dropped by the next
20709 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
20710 - Never queue a cell for a circuit that's already been marked
20712 - Never vote for a server as "Running" if we have a descriptor for
20713 it claiming to be hibernating, and that descriptor was published
20714 more recently than our last contact with the server. Bugfix on
20715 0.2.0.3-alpha; fixes bug 911.
20716 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
20719 o Minor bugfixes (on 0.2.2.x):
20720 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
20721 down if a directory fetch fails and you've configured either
20722 bridges or EntryNodes. The intent was to mark the relay as down
20723 _unless_ you're using bridges or EntryNodes, since if you are
20724 then you could quickly run out of entry points.
20725 - Fix the Windows directory-listing code. A bug introduced in
20726 0.2.2.14-alpha could make Windows directory servers forget to load
20727 some of their cached v2 networkstatus files.
20728 - Really allow clients to use relays as bridges. Fixes bug 1776;
20729 bugfix on 0.2.2.15-alpha.
20730 - Demote a warn to info that happens when the CellStatistics option
20731 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
20732 Reported by Moritz Bartl.
20733 - On Windows, build correctly either with or without Unicode support.
20734 This is necessary so that Tor can support fringe platforms like
20735 Windows 98 (which has no Unicode), or Windows CE (which has no
20736 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
20739 - Add a unit test for cross-platform directory-listing code.
20742 Changes in version 0.2.2.15-alpha - 2010-08-18
20743 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
20744 fixes a variety of other bugs that were preventing performance
20745 experiments from moving forward, fixes several bothersome memory leaks,
20746 and generally closes a lot of smaller bugs that have been filling up
20750 - Stop assigning the HSDir flag to relays that disable their
20751 DirPort (and thus will refuse to answer directory requests). This
20752 fix should dramatically improve the reachability of hidden services:
20753 hidden services and hidden service clients pick six HSDir relays
20754 to store and retrieve the hidden service descriptor, and currently
20755 about half of the HSDir relays will refuse to work. Bugfix on
20756 0.2.0.10-alpha; fixes part of bug 1693.
20757 - The PerConnBWRate and Burst config options, along with the
20758 bwconnrate and bwconnburst consensus params, initialized each conn's
20759 token bucket values only when the connection is established. Now we
20760 update them if the config options change, and update them every time
20761 we get a new consensus. Otherwise we can encounter an ugly edge
20762 case where we initialize an OR conn to client-level bandwidth,
20763 but then later the relay joins the consensus and we leave it
20764 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
20765 - Fix a regression that caused Tor to rebind its ports if it receives
20766 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
20769 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
20770 should give us approximately 40-50% more Guard-flagged nodes,
20771 improving the anonymity the Tor network can provide and also
20772 decreasing the dropoff in throughput that relays experience when
20773 they first get the Guard flag.
20774 - Allow enabling or disabling the *Statistics config options while
20778 - Update to the August 1 2010 Maxmind GeoLite Country database.
20779 - Have the controller interface give a more useful message than
20780 "Internal Error" in response to failed GETINFO requests.
20781 - Warn when the same option is provided more than once in a torrc
20782 file, on the command line, or in a single SETCONF statement, and
20783 the option is one that only accepts a single line. Closes bug 1384.
20784 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
20785 Patch from mingw-san.
20786 - Add support for the country code "{??}" in torrc options like
20787 ExcludeNodes, to indicate all routers of unknown country. Closes
20789 - Relays report the number of bytes spent on answering directory
20790 requests in extra-info descriptors similar to {read,write}-history.
20791 Implements enhancement 1790.
20793 o Minor bugfixes (on 0.2.1.x and earlier):
20794 - Complain if PublishServerDescriptor is given multiple arguments that
20795 include 0 or 1. This configuration will be rejected in the future.
20796 Bugfix on 0.2.0.1-alpha; closes bug 1107.
20797 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
20798 Bugfix on 0.2.0.13-alpha; closes bug 928.
20799 - Change "Application request when we're believed to be offline."
20800 notice to "Application request when we haven't used client
20801 functionality lately.", to clarify that it's not an error. Bugfix
20802 on 0.0.9.3; fixes bug 1222.
20803 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
20804 would return "551 Internal error" rather than "552 Unrecognized key
20805 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
20806 - Users can't configure a regular relay to be their bridge. It didn't
20807 work because when Tor fetched the bridge descriptor, it found
20808 that it already had it, and didn't realize that the purpose of the
20809 descriptor had changed. Now we replace routers with a purpose other
20810 than bridge with bridge descriptors when fetching them. Bugfix on
20811 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
20812 refetch the descriptor with router purpose 'general', disabling
20814 - Fix a rare bug in rend_fn unit tests: we would fail a test when
20815 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
20816 on 0.2.0.10-alpha; fixes bug 1808.
20817 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
20818 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
20819 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
20820 Servers can start sending this code when enough clients recognize
20821 it. Also update the spec to reflect this new reason. Bugfix on
20822 0.1.0.1-rc; fixes part of bug 1793.
20823 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
20824 when we switch from being a public relay to a bridge. Otherwise
20825 there will still be clients that see the relay in their consensus,
20826 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
20828 - Instead of giving an assertion failure on an internal mismatch
20829 on estimated freelist size, just log a BUG warning and try later.
20830 Mitigates but does not fix bug 1125.
20831 - Fix an assertion failure that could occur in caches or bridge users
20832 when using a very short voting interval on a testing network.
20833 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
20835 o Minor bugfixes (on 0.2.2.x):
20836 - Alter directory authorities to always consider Exit-flagged nodes
20837 as potential Guard nodes in their votes. The actual decision to
20838 use Exits as Guards is done in the consensus bandwidth weights.
20839 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
20840 - When the controller is reporting the purpose of circuits that
20841 didn't finish building before the circuit build timeout, it was
20842 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
20843 - Our libevent version parsing code couldn't handle versions like
20844 1.4.14b-stable and incorrectly warned the user about using an
20845 old and broken version of libevent. Treat 1.4.14b-stable like
20846 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
20848 - Don't use substitution references like $(VAR:MOD) when
20849 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
20850 '$(:x)' to 'x' rather than the empty string. This bites us in
20851 doc/ when configured with --disable-asciidoc. Bugfix on
20852 0.2.2.9-alpha; fixes bug 1773.
20853 - Remove a spurious hidden service server-side log notice about
20854 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
20856 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
20858 - Correctly report written bytes on linked connections. Found while
20859 implementing 1790. Bugfix on 0.2.2.4-alpha.
20860 - Fix three memory leaks: one in circuit_build_times_parse_state(),
20861 one in dirvote_add_signatures_to_pending_consensus(), and one every
20862 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
20863 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
20865 o Code simplifications and refactoring:
20866 - Take a first step towards making or.h smaller by splitting out
20867 function definitions for all source files in src/or/. Leave
20868 structures and defines in or.h for now.
20869 - Remove a bunch of unused function declarations as well as a block of
20870 #if 0'd code from the unit tests. Closes bug 1824.
20871 - New unit tests for exit-port history statistics; refactored exit
20872 statistics code to be more easily tested.
20873 - Remove the old debian/ directory from the main Tor distribution.
20874 The official Tor-for-debian git repository lives at the URL
20875 https://git.torproject.org/debian/tor.git
20878 Changes in version 0.2.2.14-alpha - 2010-07-12
20879 Tor 0.2.2.14-alpha greatly improves client-side handling of
20880 circuit build timeouts, which are used to estimate speed and improve
20881 performance. We also move to a much better GeoIP database, port Tor to
20882 Windows CE, introduce new compile flags that improve code security,
20883 add an eighth v3 directory authority, and address a lot of more
20887 - Tor directory authorities no longer crash when started with a
20888 cached-microdesc-consensus file in their data directory. Bugfix
20889 on 0.2.2.6-alpha; fixes bug 1532.
20890 - Treat an unset $HOME like an empty $HOME rather than triggering an
20891 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
20892 - Ignore negative and large circuit build timeout values that can
20893 happen during a suspend or hibernate. These values caused various
20894 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
20895 - Alter calculation of Pareto distribution parameter 'Xm' for
20896 Circuit Build Timeout learning to use the weighted average of the
20897 top N=3 modes (because we have three entry guards). Considering
20898 multiple modes should improve the timeout calculation in some cases,
20899 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
20901 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
20902 right censored distribution model. This approach improves over the
20903 synthetic timeout generation approach that was producing insanely
20904 high timeout values. Now we calculate build timeouts using truncated
20905 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
20906 - Do not close circuits that are under construction when they reach
20907 the circuit build timeout. Instead, leave them building (but do not
20908 use them) for up until the time corresponding to the 95th percentile
20909 on the Pareto CDF or 60 seconds, whichever is greater. This is done
20910 to provide better data for the new Pareto model. This percentile
20911 can be controlled by the consensus.
20914 - Move to the June 2010 Maxmind GeoLite country db (rather than the
20915 June 2009 ip-to-country GeoIP db) for our statistics that count
20916 how many users relays are seeing from each country. Now we have
20917 more accurate data for many African countries.
20918 - Port Tor to build and run correctly on Windows CE systems, using
20919 the wcecompat library. Contributed by Valerio Lupi.
20920 - New "--enable-gcc-hardening" ./configure flag (off by default)
20921 to turn on gcc compile time hardening options. It ensures
20922 that signed ints have defined behavior (-fwrapv), enables
20923 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
20924 with canaries (-fstack-protector-all), turns on ASLR protection if
20925 supported by the kernel (-fPIE, -pie), and adds additional security
20926 related warnings. Verified to work on Mac OS X and Debian Lenny.
20927 - New "--enable-linker-hardening" ./configure flag (off by default)
20928 to turn on ELF specific hardening features (relro, now). This does
20929 not work with Mac OS X or any other non-ELF binary format.
20931 o New directory authorities:
20932 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
20936 - New config option "WarnUnsafeSocks 0" disables the warning that
20937 occurs whenever Tor receives a socks handshake using a version of
20938 the socks protocol that can only provide an IP address (rather
20939 than a hostname). Setups that do DNS locally over Tor are fine,
20940 and we shouldn't spam the logs in that case.
20941 - Convert the HACKING file to asciidoc, and add a few new sections
20942 to it, explaining how we use Git, how we make changelogs, and
20943 what should go in a patch.
20944 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
20945 event, to give information on the current rate of circuit timeouts
20946 over our stored history.
20947 - Add ability to disable circuit build time learning via consensus
20948 parameter and via a LearnCircuitBuildTimeout config option. Also
20949 automatically disable circuit build time calculation if we are
20950 either a AuthoritativeDirectory, or if we fail to write our state
20951 file. Fixes bug 1296.
20952 - More gracefully handle corrupt state files, removing asserts
20953 in favor of saving a backup and resetting state.
20954 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
20958 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
20960 - When a2x fails, mention that the user could disable manpages instead
20961 of trying to fix their asciidoc installation.
20962 - Where available, use Libevent 2.0's periodic timers so that our
20963 once-per-second cleanup code gets called even more closely to
20964 once per second than it would otherwise. Fixes bug 943.
20965 - If you run a bridge that listens on multiple IP addresses, and
20966 some user configures a bridge address that uses a different IP
20967 address than your bridge writes in its router descriptor, and the
20968 user doesn't specify an identity key, their Tor would discard the
20969 descriptor because "it isn't one of our configured bridges", and
20970 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
20971 Bugfix on 0.2.0.3-alpha.
20972 - If OpenSSL fails to make a duplicate of a private or public key, log
20973 an error message and try to exit cleanly. May help with debugging
20974 if bug 1209 ever remanifests.
20975 - Save a couple bytes in memory allocation every time we escape
20976 certain characters in a string. Patch from Florian Zumbiehl.
20977 - Make it explicit that we don't cannibalize one-hop circuits. This
20978 happens in the wild, but doesn't turn out to be a problem because
20979 we fortunately don't use those circuits. Many thanks to outofwords
20980 for the initial analysis and to swissknife who confirmed that
20981 two-hop circuits are actually created.
20982 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
20983 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
20984 - Eliminate a case where a circuit build time warning was displayed
20985 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
20988 Changes in version 0.2.1.26 - 2010-05-02
20989 Tor 0.2.1.26 addresses the recent connection and memory overload
20990 problems we've been seeing on relays, especially relays with their
20991 DirPort open. If your relay has been crashing, or you turned it off
20992 because it used too many resources, give this release a try.
20994 This release also fixes yet another instance of broken OpenSSL libraries
20995 that was causing some relays to drop out of the consensus.
20998 - Teach relays to defend themselves from connection overload. Relays
20999 now close idle circuits early if it looks like they were intended
21000 for directory fetches. Relays are also more aggressive about closing
21001 TLS connections that have no circuits on them. Such circuits are
21002 unlikely to be re-used, and tens of thousands of them were piling
21003 up at the fast relays, causing the relays to run out of sockets
21004 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
21005 their directory fetches over TLS).
21006 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
21007 that claim to be earlier than 0.9.8m, but which have in reality
21008 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
21009 behavior. Possible fix for some cases of bug 1346.
21010 - Directory mirrors were fetching relay descriptors only from v2
21011 directory authorities, rather than v3 authorities like they should.
21012 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
21013 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
21016 - Finally get rid of the deprecated and now harmful notion of "clique
21017 mode", where directory authorities maintain TLS connections to
21021 - In the util/threads test, no longer free the test_mutex before all
21022 worker threads have finished. Bugfix on 0.2.1.6-alpha.
21023 - The master thread could starve the worker threads quite badly on
21024 certain systems, causing them to run only partially in the allowed
21025 window. This resulted in test failures. Now the master thread sleeps
21026 occasionally for a few microseconds while the two worker-threads
21027 compete for the mutex. Bugfix on 0.2.0.1-alpha.
21030 Changes in version 0.2.2.13-alpha - 2010-04-24
21031 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
21032 problems we've been seeing on relays, especially relays with their
21033 DirPort open. If your relay has been crashing, or you turned it off
21034 because it used too many resources, give this release a try.
21037 - Teach relays to defend themselves from connection overload. Relays
21038 now close idle circuits early if it looks like they were intended
21039 for directory fetches. Relays are also more aggressive about closing
21040 TLS connections that have no circuits on them. Such circuits are
21041 unlikely to be re-used, and tens of thousands of them were piling
21042 up at the fast relays, causing the relays to run out of sockets
21043 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
21044 their directory fetches over TLS).
21047 - Finally get rid of the deprecated and now harmful notion of "clique
21048 mode", where directory authorities maintain TLS connections to
21050 - Directory authorities now do an immediate reachability check as soon
21051 as they hear about a new relay. This change should slightly reduce
21052 the time between setting up a relay and getting listed as running
21053 in the consensus. It should also improve the time between setting
21054 up a bridge and seeing use by bridge users.
21055 - Directory authorities no longer launch a TLS connection to every
21056 relay as they startup. Now that we have 2k+ descriptors cached,
21057 the resulting network hiccup is becoming a burden. Besides,
21058 authorities already avoid voting about Running for the first half
21059 hour of their uptime.
21062 Changes in version 0.2.2.12-alpha - 2010-04-20
21063 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
21064 handle and vote on descriptors. It was causing relays to drop out of
21068 - Many relays have been falling out of the consensus lately because
21069 not enough authorities know about their descriptor for them to get
21070 a majority of votes. When we deprecated the v2 directory protocol,
21071 we got rid of the only way that v3 authorities can hear from each
21072 other about other descriptors. Now authorities examine every v3
21073 vote for new descriptors, and fetch them from that authority. Bugfix
21075 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
21076 and a warning in or.h related to bandwidth_weight_rule_t that
21077 prevented clean compile on OS X. Fixes bug 1363; bugfix on
21079 - Fix a segfault on relays when DirReqStatistics is enabled
21080 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
21084 - Demote a confusing TLS warning that relay operators might get when
21085 someone tries to talk to their OrPort. It is neither the operator's
21086 fault nor can they do anything about it. Fixes bug 1364; bugfix
21090 Changes in version 0.2.2.11-alpha - 2010-04-15
21091 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
21092 libraries that was causing some relays to drop out of the consensus.
21095 - Directory mirrors were fetching relay descriptors only from v2
21096 directory authorities, rather than v3 authorities like they should.
21097 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
21098 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
21099 - Fix a parsing error that made every possible value of
21100 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
21101 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
21102 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
21103 about the option without breaking older ones.
21104 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
21105 that claim to be earlier than 0.9.8m, but which have in reality
21106 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
21107 behavior. Possible fix for some cases of bug 1346.
21110 - Experiment with a more aggressive approach to preventing clients
21111 from making one-hop exit streams. Exit relays who want to try it
21112 out can set "RefuseUnknownExits 1" in their torrc, and then look
21113 for "Attempt by %s to open a stream" log messages. Let us know
21115 - Add support for statically linking zlib by specifying
21116 --enable-static-zlib, to go with our support for statically linking
21117 openssl and libevent. Resolves bug 1358.
21120 - Fix a segfault that happens whenever a Tor client that is using
21121 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
21123 - When we cleaned up the contrib/tor-exit-notice.html file, we left
21124 out the first line. Fixes bug 1295.
21125 - When building the manpage from a tarball, we required asciidoc, but
21126 the asciidoc -> roff/html conversion was already done for the
21127 tarball. Make 'make' complain only when we need asciidoc (either
21128 because we're compiling directly from git, or because we altered
21129 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
21130 - When none of the directory authorities vote on any params, Tor
21131 segfaulted when trying to make the consensus from the votes. We
21132 didn't trigger the bug in practice, because authorities do include
21133 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
21136 - In the util/threads test, no longer free the test_mutex before all
21137 worker threads have finished. Bugfix on 0.2.1.6-alpha.
21138 - The master thread could starve the worker threads quite badly on
21139 certain systems, causing them to run only partially in the allowed
21140 window. This resulted in test failures. Now the master thread sleeps
21141 occasionally for a few microseconds while the two worker-threads
21142 compete for the mutex. Bugfix on 0.2.0.1-alpha.
21145 Changes in version 0.2.2.10-alpha - 2010-03-07
21146 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
21147 could prevent relays from guessing their IP address correctly. It also
21148 starts the groundwork for another client-side performance boost, since
21149 currently we're not making efficient use of relays that have both the
21150 Guard flag and the Exit flag.
21153 - Fix a regression from our patch for bug 1244 that caused relays
21154 to guess their IP address incorrectly if they didn't set Address
21155 in their torrc and/or their address fails to resolve. Bugfix on
21156 0.2.2.9-alpha; fixes bug 1269.
21158 o Major features (performance):
21159 - Directory authorities now compute consensus weightings that instruct
21160 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
21161 and no flag. Clients that use these weightings will distribute
21162 network load more evenly across these different relay types. The
21163 weightings are in the consensus so we can change them globally in
21164 the future. Extra thanks to "outofwords" for finding some nasty
21165 security bugs in the first implementation of this feature.
21167 o Minor features (performance):
21168 - Always perform router selections using weighted relay bandwidth,
21169 even if we don't need a high capacity circuit at the time. Non-fast
21170 circuits now only differ from fast ones in that they can use relays
21171 not marked with the Fast flag. This "feature" could turn out to
21172 be a horrible bug; we should investigate more before it goes into
21176 - Allow disabling building of the manpages. Skipping the manpage
21177 speeds up the build considerably.
21179 o Minor bugfixes (on 0.2.2.x):
21180 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
21181 Bugfix on 0.2.2.9-alpha.
21182 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
21183 config option. Bugfix on 0.2.2.7-alpha.
21184 - Ship the asciidoc-helper file in the tarball, so that people can
21185 build from source if they want to, and touching the .1.txt files
21186 doesn't break the build. Bugfix on 0.2.2.9-alpha.
21188 o Minor bugfixes (on 0.2.1.x or earlier):
21189 - Fix a dereference-then-NULL-check sequence when publishing
21190 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
21192 - Fix another dereference-then-NULL-check sequence. Bugfix on
21193 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
21194 - Make sure we treat potentially not NUL-terminated strings correctly.
21195 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
21197 o Code simplifications and refactoring:
21198 - Fix some urls in the exit notice file and make it XHTML1.1 strict
21199 compliant. Based on a patch from Christian Kujau.
21200 - Don't use sed in asciidoc-helper anymore.
21201 - Make the build process fail if asciidoc cannot be found and
21202 building with asciidoc isn't disabled.
21205 Changes in version 0.2.2.9-alpha - 2010-02-22
21206 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
21207 location of a directory authority, and cleans up a bunch of small bugs.
21209 o Directory authority changes:
21210 - Change IP address for dannenberg (v3 directory authority), and
21211 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
21212 service directory authority) from the list.
21215 - Make Tor work again on the latest OS X: when deciding whether to
21216 use strange flags to turn TLS renegotiation on, detect the OpenSSL
21217 version at run-time, not compile time. We need to do this because
21218 Apple doesn't update its dev-tools headers when it updates its
21219 libraries in a security patch.
21220 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
21221 that could happen on 32-bit platforms with 64-bit time_t. Also fix
21222 a memory leak when requesting a hidden service descriptor we've
21223 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
21225 - Authorities could be tricked into giving out the Exit flag to relays
21226 that didn't allow exiting to any ports. This bug could screw
21227 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
21228 1238. Bug discovered by Martin Kowalczyk.
21229 - When freeing a session key, zero it out completely. We only zeroed
21230 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
21231 patched by ekir. Fixes bug 1254.
21234 - Fix static compilation by listing the openssl libraries in the right
21235 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
21236 - Resume handling .exit hostnames in a special way: originally we
21237 stripped the .exit part and used the requested exit relay. In
21238 0.2.2.1-alpha we stopped treating them in any special way, meaning
21239 if you use a .exit address then Tor will pass it on to the exit
21240 relay. Now we reject the .exit stream outright, since that behavior
21241 might be more expected by the user. Found and diagnosed by Scott
21242 Bennett and Downie on or-talk.
21243 - Don't spam the controller with events when we have no file
21244 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
21245 for log messages was already solved from bug 748.)
21246 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
21248 - Make the DNSPort option work with libevent 2.x. Don't alter the
21249 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
21250 - Emit a GUARD DROPPED controller event for a case we missed.
21251 - Make more fields in the controller protocol case-insensitive, since
21252 control-spec.txt said they were.
21253 - Refactor resolve_my_address() to not use gethostbyname() anymore.
21254 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
21255 - Fix a spec conformance issue: the network-status-version token
21256 must be the first token in a v3 consensus or vote. Discovered by
21257 parakeep. Bugfix on 0.2.0.3-alpha.
21259 o Code simplifications and refactoring:
21260 - Generate our manpage and HTML documentation using Asciidoc. This
21261 change should make it easier to maintain the documentation, and
21262 produce nicer HTML.
21263 - Remove the --enable-iphone option. According to reports from Marco
21264 Bonetti, Tor builds fine without any special tweaking on recent
21265 iPhone SDK versions.
21266 - Removed some unnecessary files from the source distribution. The
21267 AUTHORS file has now been merged into the people page on the
21268 website. The roadmaps and design doc can now be found in the
21269 projects directory in svn.
21270 - Enabled various circuit build timeout constants to be controlled
21271 by consensus parameters. Also set better defaults for these
21272 parameters based on experimentation on broadband and simulated
21273 high latency links.
21276 - The 'EXTENDCIRCUIT' control port command can now be used with
21277 a circ id of 0 and no path. This feature will cause Tor to build
21278 a new 'fast' general purpose circuit using its own path selection
21280 - Added a BUILDTIMEOUT_SET controller event to describe changes
21281 to the circuit build timeout.
21282 - Future-proof the controller protocol a bit by ignoring keyword
21283 arguments we do not recognize.
21284 - Expand homedirs passed to tor-checkkey. This should silence a
21285 coverity complaint about passing a user-supplied string into
21286 open() without checking it.
21289 Changes in version 0.2.1.25 - 2010-03-16
21290 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
21291 prevent relays from guessing their IP address correctly. It also fixes
21292 several minor potential security bugs.
21295 - Fix a regression from our patch for bug 1244 that caused relays
21296 to guess their IP address incorrectly if they didn't set Address
21297 in their torrc and/or their address fails to resolve. Bugfix on
21298 0.2.1.23; fixes bug 1269.
21299 - When freeing a session key, zero it out completely. We only zeroed
21300 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
21301 patched by ekir. Fixes bug 1254.
21304 - Fix a dereference-then-NULL-check sequence when publishing
21305 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
21307 - Fix another dereference-then-NULL-check sequence. Bugfix on
21308 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
21309 - Make sure we treat potentially not NUL-terminated strings correctly.
21310 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
21314 Changes in version 0.2.1.24 - 2010-02-21
21315 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
21319 - Work correctly out-of-the-box with even more vendor-patched versions
21320 of OpenSSL. In particular, make it so Debian and OS X don't need
21321 customized patches to run/build.
21324 Changes in version 0.2.1.23 - 2010-02-13
21325 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
21326 again on the latest OS X, and updates the location of a directory
21329 o Major bugfixes (performance):
21330 - We were selecting our guards uniformly at random, and then weighting
21331 which of our guards we'd use uniformly at random. This imbalance
21332 meant that Tor clients were severely limited on throughput (and
21333 probably latency too) by the first hop in their circuit. Now we
21334 select guards weighted by currently advertised bandwidth. We also
21335 automatically discard guards picked using the old algorithm. Fixes
21336 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
21339 - Make Tor work again on the latest OS X: when deciding whether to
21340 use strange flags to turn TLS renegotiation on, detect the OpenSSL
21341 version at run-time, not compile time. We need to do this because
21342 Apple doesn't update its dev-tools headers when it updates its
21343 libraries in a security patch.
21344 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
21345 that could happen on 32-bit platforms with 64-bit time_t. Also fix
21346 a memory leak when requesting a hidden service descriptor we've
21347 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
21350 o Directory authority changes:
21351 - Change IP address for dannenberg (v3 directory authority), and
21352 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
21353 service directory authority) from the list.
21356 - Refactor resolve_my_address() to not use gethostbyname() anymore.
21357 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
21360 - Avoid a mad rush at the beginning of each month when each client
21361 rotates half of its guards. Instead we spread the rotation out
21362 throughout the month, but we still avoid leaving a precise timestamp
21363 in the state file about when we first picked the guard. Improves
21364 over the behavior introduced in 0.1.2.17.
21367 Changes in version 0.2.2.8-alpha - 2010-01-26
21368 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
21369 causing bridge relays to disappear. If you're running a bridge,
21373 - Fix a memory corruption bug on bridges that occurred during the
21374 inclusion of stats data in extra-info descriptors. Also fix the
21375 interface for geoip_get_bridge_stats* to prevent similar bugs in
21376 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
21377 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
21380 - Ignore OutboundBindAddress when connecting to localhost.
21381 Connections to localhost need to come _from_ localhost, or else
21382 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
21386 Changes in version 0.2.2.7-alpha - 2010-01-19
21387 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
21388 as laying the groundwork for further relay-side performance fixes. It
21389 also starts cleaning up client behavior with respect to the EntryNodes,
21390 ExitNodes, and StrictNodes config options.
21392 This release also rotates two directory authority keys, due to a
21393 security breach of some of the Torproject servers.
21395 o Directory authority changes:
21396 - Rotate keys (both v3 identity and relay identity) for moria1
21399 o Major features (performance):
21400 - We were selecting our guards uniformly at random, and then weighting
21401 which of our guards we'd use uniformly at random. This imbalance
21402 meant that Tor clients were severely limited on throughput (and
21403 probably latency too) by the first hop in their circuit. Now we
21404 select guards weighted by currently advertised bandwidth. We also
21405 automatically discard guards picked using the old algorithm. Fixes
21406 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
21407 - When choosing which cells to relay first, relays can now favor
21408 circuits that have been quiet recently, to provide lower latency
21409 for low-volume circuits. By default, relays enable or disable this
21410 feature based on a setting in the consensus. You can override
21411 this default by using the new "CircuitPriorityHalflife" config
21412 option. Design and code by Ian Goldberg, Can Tang, and Chris
21414 - Add separate per-conn write limiting to go with the per-conn read
21415 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
21416 but never per-conn write limits.
21417 - New consensus params "bwconnrate" and "bwconnburst" to let us
21418 rate-limit client connections as they enter the network. It's
21419 controlled in the consensus so we can turn it on and off for
21420 experiments. It's starting out off. Based on proposal 163.
21422 o Major features (relay selection options):
21423 - Switch to a StrictNodes config option, rather than the previous
21424 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
21425 "StrictExcludeNodes" option.
21426 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
21427 change during a config reload, mark and discard all our origin
21428 circuits. This fix should address edge cases where we change the
21429 config options and but then choose a circuit that we created before
21431 - If EntryNodes or ExitNodes are set, be more willing to use an
21432 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
21434 - Make EntryNodes config option much more aggressive even when
21435 StrictNodes is not set. Before it would prepend your requested
21436 entrynodes to your list of guard nodes, but feel free to use others
21437 after that. Now it chooses only from your EntryNodes if any of
21438 those are available, and only falls back to others if a) they're
21439 all down and b) StrictNodes is not set.
21440 - Now we refresh your entry guards from EntryNodes at each consensus
21441 fetch -- rather than just at startup and then they slowly rot as
21442 the network changes.
21445 - Stop bridge directory authorities from answering dbg-stability.txt
21446 directory queries, which would let people fetch a list of all
21447 bridge identities they track. Bugfix on 0.2.1.6-alpha.
21450 - Log a notice when we get a new control connection. Now it's easier
21451 for security-conscious users to recognize when a local application
21452 is knocking on their controller door. Suggested by bug 1196.
21453 - New config option "CircuitStreamTimeout" to override our internal
21454 timeout schedule for how many seconds until we detach a stream from
21455 a circuit and try a new circuit. If your network is particularly
21456 slow, you might want to set this to a number like 60.
21457 - New controller command "getinfo config-text". It returns the
21458 contents that Tor would write if you send it a SAVECONF command,
21459 so the controller can write the file to disk itself.
21460 - New options for SafeLogging to allow scrubbing only log messages
21461 generated while acting as a relay.
21462 - Ship the bridges spec file in the tarball too.
21463 - Avoid a mad rush at the beginning of each month when each client
21464 rotates half of its guards. Instead we spread the rotation out
21465 throughout the month, but we still avoid leaving a precise timestamp
21466 in the state file about when we first picked the guard. Improves
21467 over the behavior introduced in 0.1.2.17.
21469 o Minor bugfixes (compiling):
21470 - Fix compilation on OS X 10.3, which has a stub mlockall() but
21471 hides it. Bugfix on 0.2.2.6-alpha.
21472 - Fix compilation on Solaris by removing support for the
21473 DisableAllSwap config option. Solaris doesn't have an rlimit for
21474 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
21477 o Minor bugfixes (crashes):
21478 - Do not segfault when writing buffer stats when we haven't observed
21479 a single circuit to report about. Found by Fabian Lanze. Bugfix on
21481 - If we're in the pathological case where there's no exit bandwidth
21482 but there is non-exit bandwidth, or no guard bandwidth but there
21483 is non-guard bandwidth, don't crash during path selection. Bugfix
21485 - Fix an impossible-to-actually-trigger buffer overflow in relay
21486 descriptor generation. Bugfix on 0.1.0.15.
21488 o Minor bugfixes (privacy):
21489 - Fix an instance where a Tor directory mirror might accidentally
21490 log the IP address of a misbehaving Tor client. Bugfix on
21492 - Don't list Windows capabilities in relay descriptors. We never made
21493 use of them, and maybe it's a bad idea to publish them. Bugfix
21496 o Minor bugfixes (other):
21497 - Resolve an edge case in path weighting that could make us misweight
21498 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
21499 - Fix statistics on client numbers by country as seen by bridges that
21500 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
21501 intervals instead of variable 12-to-48-hour intervals.
21502 - After we free an internal connection structure, overwrite it
21503 with a different memory value than we use for overwriting a freed
21504 internal circuit structure. Should help with debugging. Suggested
21506 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
21509 o Removed features:
21510 - Remove the HSAuthorityRecordStats option that version 0 hidden
21511 service authorities could have used to track statistics of overall
21512 hidden service usage.
21515 Changes in version 0.2.1.22 - 2010-01-19
21516 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
21517 authorities -- it would tell you its whole history of bridge descriptors
21518 if you make the right directory request. This stable update also
21519 rotates two of the seven v3 directory authority keys and locations.
21521 o Directory authority changes:
21522 - Rotate keys (both v3 identity and relay identity) for moria1
21526 - Stop bridge directory authorities from answering dbg-stability.txt
21527 directory queries, which would let people fetch a list of all
21528 bridge identities they track. Bugfix on 0.2.1.6-alpha.
21531 Changes in version 0.2.1.21 - 2009-12-21
21532 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
21533 library. If you use Tor on Linux / Unix and you're getting SSL
21534 renegotiation errors, upgrading should help. We also recommend an
21535 upgrade if you're an exit relay.
21538 - Work around a security feature in OpenSSL 0.9.8l that prevents our
21539 handshake from working unless we explicitly tell OpenSSL that we
21540 are using SSL renegotiation safely. We are, of course, but OpenSSL
21541 0.9.8l won't work unless we say we are.
21542 - Avoid crashing if the client is trying to upload many bytes and the
21543 circuit gets torn down at the same time, or if the flip side
21544 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
21547 - Do not refuse to learn about authority certs and v2 networkstatus
21548 documents that are older than the latest consensus. This bug might
21549 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
21550 Spotted and fixed by xmux.
21551 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
21552 trigger platform-specific option misparsing case found by Coverity
21554 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
21555 trigger assert. Fixes bug 1173.
21558 Changes in version 0.2.2.6-alpha - 2009-11-19
21559 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
21560 support for the new lower-footprint "microdescriptor" directory design,
21561 future-proofing our consensus format against new hash functions or
21562 other changes, and an Android port. It also makes Tor compatible with
21563 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
21566 - Directory authorities can now create, vote on, and serve multiple
21567 parallel formats of directory data as part of their voting process.
21568 Partially implements Proposal 162: "Publish the consensus in
21570 - Directory authorities can now agree on and publish small summaries
21571 of router information that clients can use in place of regular
21572 server descriptors. This transition will eventually allow clients
21573 to use far less bandwidth for downloading information about the
21574 network. Begins the implementation of Proposal 158: "Clients
21575 download consensus + microdescriptors".
21576 - The directory voting system is now extensible to use multiple hash
21577 algorithms for signatures and resource selection. Newer formats
21578 are signed with SHA256, with a possibility for moving to a better
21579 hash algorithm in the future.
21580 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
21581 current and future memory pages via mlockall(). On supported
21582 platforms (modern Linux and probably BSD but not Windows or OS X),
21583 this should effectively disable any and all attempts to page out
21584 memory. This option requires that you start your Tor as root --
21585 if you use DisableAllSwap, please consider using the User option
21586 to properly reduce the privileges of your Tor.
21587 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
21588 to help Tor build correctly for Android phones.
21591 - Work around a security feature in OpenSSL 0.9.8l that prevents our
21592 handshake from working unless we explicitly tell OpenSSL that we
21593 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
21594 won't work unless we say we are.
21597 - Fix a crash bug when trying to initialize the evdns module in
21598 Libevent 2. Bugfix on 0.2.1.16-rc.
21599 - Stop logging at severity 'warn' when some other Tor client tries
21600 to establish a circuit with us using weak DH keys. It's a protocol
21601 violation, but that doesn't mean ordinary users need to hear about
21602 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
21603 - Do not refuse to learn about authority certs and v2 networkstatus
21604 documents that are older than the latest consensus. This bug might
21605 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
21606 Spotted and fixed by xmux.
21607 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
21608 - If all authorities restart at once right before a consensus vote,
21609 nobody will vote about "Running", and clients will get a consensus
21610 with no usable relays. Instead, authorities refuse to build a
21611 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
21612 - If your relay can't keep up with the number of incoming create
21613 cells, it would log one warning per failure into your logs. Limit
21614 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
21615 - Bridges now use "reject *:*" as their default exit policy. Bugfix
21616 on 0.2.0.3-alpha; fixes bug 1113.
21617 - Fix a memory leak on directory authorities during voting that was
21618 introduced in 0.2.2.1-alpha. Found via valgrind.
21621 Changes in version 0.2.1.20 - 2009-10-15
21622 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
21623 services at once, prepares for more performance improvements, and
21624 fixes a bunch of smaller bugs.
21626 The Windows and OS X bundles also include a more recent Vidalia,
21627 and switch from Privoxy to Polipo.
21629 The OS X installers are now drag and drop. It's best to un-install
21630 Tor/Vidalia and then install this new bundle, rather than upgrade. If
21631 you want to upgrade, you'll need to update the paths for Tor and Polipo
21632 in the Vidalia Settings window.
21635 - Send circuit or stream sendme cells when our window has decreased
21636 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
21637 by Karsten when testing the "reduce circuit window" performance
21638 patch. Bugfix on the 54th commit on Tor -- from July 2002,
21639 before the release of Tor 0.0.0. This is the new winner of the
21641 - Fix a remotely triggerable memory leak when a consensus document
21642 contains more than one signature from the same voter. Bugfix on
21644 - Avoid segfault in rare cases when finishing an introduction circuit
21645 as a client and finding out that we don't have an introduction key
21646 for it. Fixes bug 1073. Reported by Aaron Swartz.
21649 - Tor now reads the "circwindow" parameter out of the consensus,
21650 and uses that value for its circuit package window rather than the
21651 default of 1000 cells. Begins the implementation of proposal 168.
21653 o New directory authorities:
21654 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
21656 - Move moria1 and tonga to alternate IP addresses.
21659 - Fix a signed/unsigned compile warning in 0.2.1.19.
21660 - Fix possible segmentation fault on directory authorities. Bugfix on
21662 - Fix an extremely rare infinite recursion bug that could occur if
21663 we tried to log a message after shutting down the log subsystem.
21664 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
21665 - Fix an obscure bug where hidden services on 64-bit big-endian
21666 systems might mis-read the timestamp in v3 introduce cells, and
21667 refuse to connect back to the client. Discovered by "rotor".
21668 Bugfix on 0.2.1.6-alpha.
21669 - We were triggering a CLOCK_SKEW controller status event whenever
21670 we connect via the v2 connection protocol to any relay that has
21671 a wrong clock. Instead, we should only inform the controller when
21672 it's a trusted authority that claims our clock is wrong. Bugfix
21673 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
21674 - We were telling the controller about CHECKING_REACHABILITY and
21675 REACHABILITY_FAILED status events whenever we launch a testing
21676 circuit or notice that one has failed. Instead, only tell the
21677 controller when we want to inform the user of overall success or
21678 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
21680 - Don't warn when we're using a circuit that ends with a node
21681 excluded in ExcludeExitNodes, but the circuit is not used to access
21682 the outside world. This should help fix bug 1090. Bugfix on
21684 - Work around a small memory leak in some versions of OpenSSL that
21685 stopped the memory used by the hostname TLS extension from being
21689 - Add a "getinfo status/accepted-server-descriptor" controller
21690 command, which is the recommended way for controllers to learn
21691 whether our server descriptor has been successfully received by at
21692 least on directory authority. Un-recommend good-server-descriptor
21693 getinfo and status events until we have a better design for them.
21696 Changes in version 0.2.2.5-alpha - 2009-10-11
21697 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
21700 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
21702 o Directory authorities:
21703 - Temporarily (just for this release) move dizum to an alternate
21707 Changes in version 0.2.2.4-alpha - 2009-10-10
21708 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
21709 introduces a new unit test framework, shifts directry authority
21710 addresses around to reduce the impact from recent blocking events,
21711 and fixes a few smaller bugs.
21714 - Fix several more asserts in the circuit_build_times code, for
21715 example one that causes Tor to fail to start once we have
21716 accumulated 5000 build times in the state file. Bugfixes on
21717 0.2.2.2-alpha; fixes bug 1108.
21719 o New directory authorities:
21720 - Move moria1 and Tonga to alternate IP addresses.
21723 - Log SSL state transitions at debug level during handshake, and
21724 include SSL states in error messages. This may help debug future
21725 SSL handshake issues.
21726 - Add a new "Handshake" log domain for activities that happen
21727 during the TLS handshake.
21728 - Revert to the "June 3 2009" ip-to-country file. The September one
21729 seems to have removed most US IP addresses.
21730 - Directory authorities now reject Tor relays with versions less than
21731 0.1.2.14. This step cuts out four relays from the current network,
21732 none of which are very big.
21735 - Fix a couple of smaller issues with gathering statistics. Bugfixes
21737 - Fix two memory leaks in the error case of
21738 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
21739 - Don't count one-hop circuits when we're estimating how long it
21740 takes circuits to build on average. Otherwise we'll set our circuit
21741 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
21742 - Directory authorities no longer change their opinion of, or vote on,
21743 whether a router is Running, unless they have themselves been
21744 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
21747 o Code simplifications and refactoring:
21748 - Revise our unit tests to use the "tinytest" framework, so we
21749 can run tests in their own processes, have smarter setup/teardown
21750 code, and so on. The unit test code has moved to its own
21751 subdirectory, and has been split into multiple modules.
21754 Changes in version 0.2.2.3-alpha - 2009-09-23
21755 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
21758 - Fix an overzealous assert in our new circuit build timeout code.
21759 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
21762 - If the networkstatus consensus tells us that we should use a
21763 negative circuit package window, ignore it. Otherwise we'll
21764 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
21767 Changes in version 0.2.2.2-alpha - 2009-09-21
21768 Tor 0.2.2.2-alpha introduces our latest performance improvement for
21769 clients: Tor tracks the average time it takes to build a circuit, and
21770 avoids using circuits that take too long to build. For fast connections,
21771 this feature can cut your expected latency in half. For slow or flaky
21772 connections, it could ruin your Tor experience. Let us know if it does!
21775 - Tor now tracks how long it takes to build client-side circuits
21776 over time, and adapts its timeout to local network performance.
21777 Since a circuit that takes a long time to build will also provide
21778 bad performance, we get significant latency improvements by
21779 discarding the slowest 20% of circuits. Specifically, Tor creates
21780 circuits more aggressively than usual until it has enough data
21781 points for a good timeout estimate. Implements proposal 151.
21782 We are especially looking for reports (good and bad) from users with
21783 both EDGE and broadband connections that can move from broadband
21784 to EDGE and find out if the build-time data in the .tor/state gets
21785 reset without loss of Tor usability. You should also see a notice
21786 log message telling you that Tor has reset its timeout.
21787 - Directory authorities can now vote on arbitrary integer values as
21788 part of the consensus process. This is designed to help set
21789 network-wide parameters. Implements proposal 167.
21790 - Tor now reads the "circwindow" parameter out of the consensus,
21791 and uses that value for its circuit package window rather than the
21792 default of 1000 cells. Begins the implementation of proposal 168.
21795 - Fix a remotely triggerable memory leak when a consensus document
21796 contains more than one signature from the same voter. Bugfix on
21800 - Fix an extremely rare infinite recursion bug that could occur if
21801 we tried to log a message after shutting down the log subsystem.
21802 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
21803 - Fix parsing for memory or time units given without a space between
21804 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
21805 - A networkstatus vote must contain exactly one signature. Spec
21806 conformance issue. Bugfix on 0.2.0.3-alpha.
21807 - Fix an obscure bug where hidden services on 64-bit big-endian
21808 systems might mis-read the timestamp in v3 introduce cells, and
21809 refuse to connect back to the client. Discovered by "rotor".
21810 Bugfix on 0.2.1.6-alpha.
21811 - We were triggering a CLOCK_SKEW controller status event whenever
21812 we connect via the v2 connection protocol to any relay that has
21813 a wrong clock. Instead, we should only inform the controller when
21814 it's a trusted authority that claims our clock is wrong. Bugfix
21815 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
21816 - We were telling the controller about CHECKING_REACHABILITY and
21817 REACHABILITY_FAILED status events whenever we launch a testing
21818 circuit or notice that one has failed. Instead, only tell the
21819 controller when we want to inform the user of overall success or
21820 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
21822 - Don't warn when we're using a circuit that ends with a node
21823 excluded in ExcludeExitNodes, but the circuit is not used to access
21824 the outside world. This should help fix bug 1090, but more problems
21825 remain. Bugfix on 0.2.1.6-alpha.
21826 - Work around a small memory leak in some versions of OpenSSL that
21827 stopped the memory used by the hostname TLS extension from being
21829 - Make our 'torify' script more portable; if we have only one of
21830 'torsocks' or 'tsocks' installed, don't complain to the user;
21831 and explain our warning about tsocks better.
21834 - Add a "getinfo status/accepted-server-descriptor" controller
21835 command, which is the recommended way for controllers to learn
21836 whether our server descriptor has been successfully received by at
21837 least on directory authority. Un-recommend good-server-descriptor
21838 getinfo and status events until we have a better design for them.
21839 - Update to the "September 4 2009" ip-to-country file.
21842 Changes in version 0.2.2.1-alpha - 2009-08-26
21843 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
21844 Tor clients to bootstrap on networks where only port 80 is reachable,
21845 makes it more straightforward to support hardware crypto accelerators,
21846 and starts the groundwork for gathering stats safely at relays.
21849 - Start the process of disabling ".exit" address notation, since it
21850 can be used for a variety of esoteric application-level attacks
21851 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
21854 o New directory authorities:
21855 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
21859 - New AccelName and AccelDir options add support for dynamic OpenSSL
21860 hardware crypto acceleration engines.
21861 - Tor now supports tunneling all of its outgoing connections over
21862 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
21863 configuration options. Code by Christopher Davis.
21866 - Send circuit or stream sendme cells when our window has decreased
21867 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
21868 by Karsten when testing the "reduce circuit window" performance
21869 patch. Bugfix on the 54th commit on Tor -- from July 2002,
21870 before the release of Tor 0.0.0. This is the new winner of the
21873 o New options for gathering stats safely:
21874 - Directory mirrors that set "DirReqStatistics 1" write statistics
21875 about directory requests to disk every 24 hours. As compared to the
21876 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
21877 1) stats are written to disk exactly every 24 hours; 2) estimated
21878 shares of v2 and v3 requests are determined as mean values, not at
21879 the end of a measurement period; 3) unresolved requests are listed
21880 with country code '??'; 4) directories also measure download times.
21881 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
21882 number of exit streams and transferred bytes per port to disk every
21884 - Relays that set "CellStatistics 1" write statistics on how long
21885 cells spend in their circuit queues to disk every 24 hours.
21886 - Entry nodes that set "EntryStatistics 1" write statistics on the
21887 rough number and origins of connecting clients to disk every 24
21889 - Relays that write any of the above statistics to disk and set
21890 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
21891 their extra-info documents.
21894 - New --digests command-line switch to output the digests of the
21895 source files Tor was built with.
21896 - The "torify" script now uses torsocks where available.
21897 - The memarea code now uses a sentinel value at the end of each area
21898 to make sure nothing writes beyond the end of an area. This might
21899 help debug some conceivable causes of bug 930.
21900 - Time and memory units in the configuration file can now be set to
21901 fractional units. For example, "2.5 GB" is now a valid value for
21903 - Certain Tor clients (such as those behind check.torproject.org) may
21904 want to fetch the consensus in an extra early manner. To enable this
21905 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
21906 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
21907 as only certain clients who must have this information sooner should
21909 - Instead of adding the svn revision to the Tor version string, report
21910 the git commit (when we're building from a git checkout).
21913 - If any of the v3 certs we download are unparseable, we should
21914 actually notice the failure so we don't retry indefinitely. Bugfix
21915 on 0.2.0.x; reported by "rotator".
21916 - If the cached cert file is unparseable, warn but don't exit.
21917 - Fix possible segmentation fault on directory authorities. Bugfix on
21919 - When Tor fails to parse a descriptor of any kind, dump it to disk.
21920 Might help diagnosing bug 1051.
21922 o Deprecated and removed features:
21923 - The controller no longer accepts the old obsolete "addr-mappings/"
21924 or "unregistered-servers-" GETINFO values.
21925 - Hidden services no longer publish version 0 descriptors, and clients
21926 do not request or use version 0 descriptors. However, the old hidden
21927 service authorities still accept and serve version 0 descriptors
21928 when contacted by older hidden services/clients.
21929 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
21930 always on; using them is necessary for correct forward-compatible
21932 - Remove support for .noconnect style addresses. Nobody was using
21933 them, and they provided another avenue for detecting Tor users
21934 via application-level web tricks.
21936 o Packaging changes:
21937 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
21938 installer bundles. See
21939 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
21940 for details of what's new in Vidalia 0.2.3.
21941 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
21942 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
21943 configuration file, rather than the old Privoxy.
21944 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
21945 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
21946 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
21947 better compatibility with OS X 10.6, aka Snow Leopard.
21948 - OS X Vidalia Bundle: The multi-package installer is now replaced
21949 by a simple drag and drop to the /Applications folder. This change
21950 occurred with the upgrade to Vidalia 0.2.3.
21953 Changes in version 0.2.1.19 - 2009-07-28
21954 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
21955 services on Tor 0.2.1.3-alpha through 0.2.1.18.
21958 - Make accessing hidden services on 0.2.1.x work right again.
21959 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
21960 part of patch provided by "optimist".
21963 - When a relay/bridge is writing out its identity key fingerprint to
21964 the "fingerprint" file and to its logs, write it without spaces. Now
21965 it will look like the fingerprints in our bridges documentation,
21966 and confuse fewer users.
21969 - Relays no longer publish a new server descriptor if they change
21970 their MaxAdvertisedBandwidth config option but it doesn't end up
21971 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
21972 fixes bug 1026. Patch from Sebastian.
21973 - Avoid leaking memory every time we get a create cell but we have
21974 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
21975 fixes bug 1034. Reported by BarkerJr.
21978 Changes in version 0.2.1.18 - 2009-07-24
21979 Tor 0.2.1.18 lays the foundations for performance improvements,
21980 adds status events to help users diagnose bootstrap problems, adds
21981 optional authentication/authorization for hidden services, fixes a
21982 variety of potential anonymity problems, and includes a huge pile of
21983 other features and bug fixes.
21986 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
21989 Changes in version 0.2.1.17-rc - 2009-07-07
21990 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
21991 candidate for the 0.2.1.x series. It lays the groundwork for further
21992 client performance improvements, and also fixes a big bug with directory
21993 authorities that were causing them to assign Guard and Stable flags
21996 The Windows bundles also finally include the geoip database that we
21997 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
21998 should actually install Torbutton rather than giving you a cryptic
21999 failure message (oops).
22002 - Clients now use the bandwidth values in the consensus, rather than
22003 the bandwidth values in each relay descriptor. This approach opens
22004 the door to more accurate bandwidth estimates once the directory
22005 authorities start doing active measurements. Implements more of
22009 - When Tor clients restart after 1-5 days, they discard all their
22010 cached descriptors as too old, but they still use the cached
22011 consensus document. This approach is good for robustness, but
22012 bad for performance: since they don't know any bandwidths, they
22013 end up choosing at random rather than weighting their choice by
22014 speed. Fixed by the above feature of putting bandwidths in the
22015 consensus. Bugfix on 0.2.0.x.
22016 - Directory authorities were neglecting to mark relays down in their
22017 internal histories if the relays fall off the routerlist without
22018 ever being found unreachable. So there were relays in the histories
22019 that haven't been seen for eight months, and are listed as being
22020 up for eight months. This wreaked havoc on the "median wfu"
22021 and "median mtbf" calculations, in turn making Guard and Stable
22022 flags very wrong, hurting network performance. Fixes bugs 696 and
22023 969. Bugfix on 0.2.0.6-alpha.
22026 - Serve the DirPortFrontPage page even when we have been approaching
22027 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
22028 - The control port would close the connection before flushing long
22029 replies, such as the network consensus, if a QUIT command was issued
22030 before the reply had completed. Now, the control port flushes all
22031 pending replies before closing the connection. Also fixed a spurious
22032 warning when a QUIT command is issued after a malformed or rejected
22033 AUTHENTICATE command, but before the connection was closed. Patch
22034 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
22035 - When we can't find an intro key for a v2 hidden service descriptor,
22036 fall back to the v0 hidden service descriptor and log a bug message.
22037 Workaround for bug 1024.
22038 - Fix a log message that did not respect the SafeLogging option.
22042 - If we're a relay and we change our IP address, be more verbose
22043 about the reason that made us change. Should help track down
22044 further bugs for relays on dynamic IP addresses.
22047 Changes in version 0.2.0.35 - 2009-06-24
22049 - Avoid crashing in the presence of certain malformed descriptors.
22050 Found by lark, and by automated fuzzing.
22051 - Fix an edge case where a malicious exit relay could convince a
22052 controller that the client's DNS question resolves to an internal IP
22053 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
22056 - Finally fix the bug where dynamic-IP relays disappear when their
22057 IP address changes: directory mirrors were mistakenly telling
22058 them their old address if they asked via begin_dir, so they
22059 never got an accurate answer about their new address, so they
22060 just vanished after a day. For belt-and-suspenders, relays that
22061 don't set Address in their config now avoid using begin_dir for
22062 all direct connections. Should fix bugs 827, 883, and 900.
22063 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
22064 that would occur on some exit nodes when DNS failures and timeouts
22065 occurred in certain patterns. Fix for bug 957.
22068 - When starting with a cache over a few days old, do not leak
22069 memory for the obsolete router descriptors in it. Bugfix on
22070 0.2.0.33; fixes bug 672.
22071 - Hidden service clients didn't use a cached service descriptor that
22072 was older than 15 minutes, but wouldn't fetch a new one either,
22073 because there was already one in the cache. Now, fetch a v2
22074 descriptor unless the same descriptor was added to the cache within
22075 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
22078 Changes in version 0.2.1.16-rc - 2009-06-20
22079 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
22080 a bunch of minor bugs.
22083 - Fix an edge case where a malicious exit relay could convince a
22084 controller that the client's DNS question resolves to an internal IP
22085 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
22087 o Major performance improvements (on 0.2.0.x):
22088 - Disable and refactor some debugging checks that forced a linear scan
22089 over the whole server-side DNS cache. These accounted for over 50%
22090 of CPU time on a relatively busy exit node's gprof profile. Found
22092 - Disable some debugging checks that appeared in exit node profile
22096 - Update to the "June 3 2009" ip-to-country file.
22097 - Do not have tor-resolve automatically refuse all .onion addresses;
22098 if AutomapHostsOnResolve is set in your torrc, this will work fine.
22100 o Minor bugfixes (on 0.2.0.x):
22101 - Log correct error messages for DNS-related network errors on
22103 - Fix a race condition that could cause crashes or memory corruption
22104 when running as a server with a controller listening for log
22106 - Avoid crashing when we have a policy specified in a DirPolicy or
22107 SocksPolicy or ReachableAddresses option with ports set on it,
22108 and we re-load the policy. May fix bug 996.
22109 - Hidden service clients didn't use a cached service descriptor that
22110 was older than 15 minutes, but wouldn't fetch a new one either,
22111 because there was already one in the cache. Now, fetch a v2
22112 descriptor unless the same descriptor was added to the cache within
22113 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
22115 o Minor bugfixes (on 0.2.1.x):
22116 - Don't warn users about low port and hibernation mix when they
22117 provide a *ListenAddress directive to fix that. Bugfix on
22119 - When switching back and forth between bridge mode, do not start
22120 gathering GeoIP data until two hours have passed.
22121 - Do not complain that the user has requested an excluded node as
22122 an exit when the node is not really an exit. This could happen
22123 because the circuit was for testing, or an introduction point.
22127 Changes in version 0.2.1.15-rc - 2009-05-25
22128 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
22129 series. It fixes a major bug on fast exit relays, as well as a variety
22130 of more minor bugs.
22132 o Major bugfixes (on 0.2.0.x):
22133 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
22134 that would occur on some exit nodes when DNS failures and timeouts
22135 occurred in certain patterns. Fix for bug 957.
22137 o Minor bugfixes (on 0.2.0.x):
22138 - Actually return -1 in the error case for read_bandwidth_usage().
22139 Harmless bug, since we currently don't care about the return value
22140 anywhere. Bugfix on 0.2.0.9-alpha.
22141 - Provide a more useful log message if bug 977 (related to buffer
22142 freelists) ever reappears, and do not crash right away.
22143 - Fix an assertion failure on 64-bit platforms when we allocated
22144 memory right up to the end of a memarea, then realigned the memory
22145 one step beyond the end. Fixes a possible cause of bug 930.
22146 - Protect the count of open sockets with a mutex, so we can't
22147 corrupt it when two threads are closing or opening sockets at once.
22148 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
22149 - Don't allow a bridge to publish its router descriptor to a
22150 non-bridge directory authority. Fixes part of bug 932.
22151 - When we change to or from being a bridge, reset our counts of
22152 client usage by country. Fixes bug 932.
22153 - Fix a bug that made stream bandwidth get misreported to the
22155 - Stop using malloc_usable_size() to use more area than we had
22156 actually allocated: it was safe, but made valgrind really unhappy.
22157 - Fix a memory leak when v3 directory authorities load their keys
22158 and cert from disk. Bugfix on 0.2.0.1-alpha.
22160 o Minor bugfixes (on 0.2.1.x):
22161 - Fix use of freed memory when deciding to mark a non-addable
22162 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
22165 Changes in version 0.2.1.14-rc - 2009-04-12
22166 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
22167 series. It begins fixing some major performance problems, and also
22168 finally addresses the bug that was causing relays on dynamic IP
22169 addresses to fall out of the directory.
22172 - Clients replace entry guards that were chosen more than a few months
22173 ago. This change should significantly improve client performance,
22174 especially once more people upgrade, since relays that have been
22175 a guard for a long time are currently overloaded.
22177 o Major bugfixes (on 0.2.0):
22178 - Finally fix the bug where dynamic-IP relays disappear when their
22179 IP address changes: directory mirrors were mistakenly telling
22180 them their old address if they asked via begin_dir, so they
22181 never got an accurate answer about their new address, so they
22182 just vanished after a day. For belt-and-suspenders, relays that
22183 don't set Address in their config now avoid using begin_dir for
22184 all direct connections. Should fix bugs 827, 883, and 900.
22185 - Relays were falling out of the networkstatus consensus for
22186 part of a day if they changed their local config but the
22187 authorities discarded their new descriptor as "not sufficiently
22188 different". Now directory authorities accept a descriptor as changed
22189 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
22190 patch by Sebastian.
22191 - Avoid crashing in the presence of certain malformed descriptors.
22192 Found by lark, and by automated fuzzing.
22195 - When generating circuit events with verbose nicknames for
22196 controllers, try harder to look up nicknames for routers on a
22197 circuit. (Previously, we would look in the router descriptors we had
22198 for nicknames, but not in the consensus.) Partial fix for bug 941.
22199 - If the bridge config line doesn't specify a port, assume 443.
22200 This makes bridge lines a bit smaller and easier for users to
22202 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
22203 bytes (aka 20KB/s), to match our documentation. Also update
22204 directory authorities so they always assign the Fast flag to relays
22205 with 20KB/s of capacity. Now people running relays won't suddenly
22206 find themselves not seeing any use, if the network gets faster
22208 - Update to the "April 3 2009" ip-to-country file.
22211 - Avoid trying to print raw memory to the logs when we decide to
22212 give up on downloading a given relay descriptor. Bugfix on
22214 - In tor-resolve, when the Tor client to use is specified by
22215 <hostname>:<port>, actually use the specified port rather than
22216 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
22217 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
22218 - When starting with a cache over a few days old, do not leak
22219 memory for the obsolete router descriptors in it. Bugfix on
22221 - Avoid double-free on list of successfully uploaded hidden
22222 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
22223 - Change memarea_strndup() implementation to work even when
22224 duplicating a string at the end of a page. This bug was
22225 harmless for now, but could have meant crashes later. Fix by
22226 lark. Bugfix on 0.2.1.1-alpha.
22227 - Limit uploaded directory documents to be 16M rather than 500K.
22228 The directory authorities were refusing v3 consensus votes from
22229 other authorities, since the votes are now 504K. Fixes bug 959;
22230 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
22231 - Directory authorities should never send a 503 "busy" response to
22232 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
22236 Changes in version 0.2.1.13-alpha - 2009-03-09
22237 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
22238 cleanups. We're finally getting close to a release candidate.
22241 - Correctly update the list of which countries we exclude as
22242 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
22243 lark. Bugfix on 0.2.1.6-alpha.
22245 o Minor bugfixes (on 0.2.0.x and earlier):
22246 - Automatically detect MacOSX versions earlier than 10.4.0, and
22247 disable kqueue from inside Tor when running with these versions.
22248 We previously did this from the startup script, but that was no
22249 help to people who didn't use the startup script. Resolves bug 863.
22250 - When we had picked an exit node for a connection, but marked it as
22251 "optional", and it turned out we had no onion key for the exit,
22252 stop wanting that exit and try again. This situation may not
22253 be possible now, but will probably become feasible with proposal
22254 158. Spotted by rovv. Fixes another case of bug 752.
22255 - Clients no longer cache certificates for authorities they do not
22256 recognize. Bugfix on 0.2.0.9-alpha.
22257 - When we can't transmit a DNS request due to a network error, retry
22258 it after a while, and eventually transmit a failing response to
22259 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
22260 - If the controller claimed responsibility for a stream, but that
22261 stream never finished making its connection, it would live
22262 forever in circuit_wait state. Now we close it after SocksTimeout
22263 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
22264 - Drop begin cells to a hidden service if they come from the middle
22265 of a circuit. Patch from lark.
22266 - When we erroneously receive two EXTEND cells for the same circuit
22267 ID on the same connection, drop the second. Patch from lark.
22268 - Fix a crash that occurs on exit nodes when a nameserver request
22269 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
22270 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
22272 - Do not assume that a stack-allocated character array will be
22273 64-bit aligned on platforms that demand that uint64_t access is
22274 aligned. Possible fix for bug 604.
22275 - Parse dates and IPv4 addresses in a locale- and libc-independent
22276 manner, to avoid platform-dependent behavior on malformed input.
22277 - Build correctly when configured to build outside the main source
22278 path. Patch from Michael Gold.
22279 - We were already rejecting relay begin cells with destination port
22280 of 0. Now also reject extend cells with destination port or address
22281 of 0. Suggested by lark.
22283 o Minor bugfixes (on 0.2.1.x):
22284 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
22285 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
22286 - If we're an exit node, scrub the IP address to which we are exiting
22287 in the logs. Bugfix on 0.2.1.8-alpha.
22290 - On Linux, use the prctl call to re-enable core dumps when the user
22292 - New controller event NEWCONSENSUS that lists the networkstatus
22293 lines for every recommended relay. Now controllers like Torflow
22294 can keep up-to-date on which relays they should be using.
22295 - Update to the "February 26 2009" ip-to-country file.
22298 Changes in version 0.2.0.34 - 2009-02-08
22299 Tor 0.2.0.34 features several more security-related fixes. You should
22300 upgrade, especially if you run an exit relay (remote crash) or a
22301 directory authority (remote infinite loop), or you're on an older
22302 (pre-XP) or not-recently-patched Windows (remote exploit).
22304 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
22305 have many known flaws, and nobody should be using them. You should
22306 upgrade. If you're using a Linux or BSD and its packages are obsolete,
22307 stop using those packages and upgrade anyway.
22310 - Fix an infinite-loop bug on handling corrupt votes under certain
22311 circumstances. Bugfix on 0.2.0.8-alpha.
22312 - Fix a temporary DoS vulnerability that could be performed by
22313 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
22314 - Avoid a potential crash on exit nodes when processing malformed
22315 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
22316 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
22317 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
22320 - Fix compilation on systems where time_t is a 64-bit integer.
22321 Patch from Matthias Drochner.
22322 - Don't consider expiring already-closed client connections. Fixes
22323 bug 893. Bugfix on 0.0.2pre20.
22326 Changes in version 0.2.1.12-alpha - 2009-02-08
22327 Tor 0.2.1.12-alpha features several more security-related fixes. You
22328 should upgrade, especially if you run an exit relay (remote crash) or
22329 a directory authority (remote infinite loop), or you're on an older
22330 (pre-XP) or not-recently-patched Windows (remote exploit). It also
22331 includes a big pile of minor bugfixes and cleanups.
22334 - Fix an infinite-loop bug on handling corrupt votes under certain
22335 circumstances. Bugfix on 0.2.0.8-alpha.
22336 - Fix a temporary DoS vulnerability that could be performed by
22337 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
22338 - Avoid a potential crash on exit nodes when processing malformed
22339 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
22342 - Let controllers actually ask for the "clients_seen" event for
22343 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
22344 reported by Matt Edman.
22345 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
22347 - Fix a bug in address parsing that was preventing bridges or hidden
22348 service targets from being at IPv6 addresses.
22349 - Solve a bug that kept hardware crypto acceleration from getting
22350 enabled when accounting was turned on. Fixes bug 907. Bugfix on
22352 - Remove a bash-ism from configure.in to build properly on non-Linux
22353 platforms. Bugfix on 0.2.1.1-alpha.
22354 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
22355 headers. Bugfix on 0.2.0.10-alpha.
22356 - Don't consider expiring already-closed client connections. Fixes
22357 bug 893. Bugfix on 0.0.2pre20.
22358 - Fix another interesting corner-case of bug 891 spotted by rovv:
22359 Previously, if two hosts had different amounts of clock drift, and
22360 one of them created a new connection with just the wrong timing,
22361 the other might decide to deprecate the new connection erroneously.
22362 Bugfix on 0.1.1.13-alpha.
22363 - Resolve a very rare crash bug that could occur when the user forced
22364 a nameserver reconfiguration during the middle of a nameserver
22365 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
22366 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
22367 Bugfix on 0.2.1.7-alpha.
22368 - If we're using bridges and our network goes away, be more willing
22369 to forgive our bridges and try again when we get an application
22370 request. Bugfix on 0.2.0.x.
22373 - Support platforms where time_t is 64 bits long. (Congratulations,
22374 NetBSD!) Patch from Matthias Drochner.
22375 - Add a 'getinfo status/clients-seen' controller command, in case
22376 controllers want to hear clients_seen events but connect late.
22379 - Disable GCC's strict alias optimization by default, to avoid the
22380 likelihood of its introducing subtle bugs whenever our code violates
22381 the letter of C99's alias rules.
22384 Changes in version 0.2.0.33 - 2009-01-21
22385 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
22386 useful to users. It also finally fixes a bug where a relay or client
22387 that's been off for many days would take a long time to bootstrap.
22389 This update also fixes an important security-related bug reported by
22390 Ilja van Sprundel. You should upgrade. (We'll send out more details
22391 about the bug once people have had some time to upgrade.)
22394 - Fix a heap-corruption bug that may be remotely triggerable on
22395 some platforms. Reported by Ilja van Sprundel.
22398 - When a stream at an exit relay is in state "resolving" or
22399 "connecting" and it receives an "end" relay cell, the exit relay
22400 would silently ignore the end cell and not close the stream. If
22401 the client never closes the circuit, then the exit relay never
22402 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
22403 reported by "wood".
22404 - When sending CREATED cells back for a given circuit, use a 64-bit
22405 connection ID to find the right connection, rather than an addr:port
22406 combination. Now that we can have multiple OR connections between
22407 the same ORs, it is no longer possible to use addr:port to uniquely
22408 identify a connection.
22409 - Bridge relays that had DirPort set to 0 would stop fetching
22410 descriptors shortly after startup, and then briefly resume
22411 after a new bandwidth test and/or after publishing a new bridge
22412 descriptor. Bridge users that try to bootstrap from them would
22413 get a recent networkstatus but would get descriptors from up to
22414 18 hours earlier, meaning most of the descriptors were obsolete
22415 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
22416 - Prevent bridge relays from serving their 'extrainfo' document
22417 to anybody who asks, now that extrainfo docs include potentially
22418 sensitive aggregated client geoip summaries. Bugfix on
22420 - If the cached networkstatus consensus is more than five days old,
22421 discard it rather than trying to use it. In theory it could be
22422 useful because it lists alternate directory mirrors, but in practice
22423 it just means we spend many minutes trying directory mirrors that
22424 are long gone from the network. Also discard router descriptors as
22425 we load them if they are more than five days old, since the onion
22426 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
22429 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
22430 could make gcc generate non-functional binary search code. Bugfix
22432 - Build correctly on platforms without socklen_t.
22433 - Compile without warnings on solaris.
22434 - Avoid potential crash on internal error during signature collection.
22435 Fixes bug 864. Patch from rovv.
22436 - Correct handling of possible malformed authority signing key
22437 certificates with internal signature types. Fixes bug 880.
22438 Bugfix on 0.2.0.3-alpha.
22439 - Fix a hard-to-trigger resource leak when logging credential status.
22441 - When we can't initialize DNS because the network is down, do not
22442 automatically stop Tor from starting. Instead, we retry failed
22443 dns_init() every 10 minutes, and change the exit policy to reject
22444 *:* until one succeeds. Fixes bug 691.
22445 - Use 64 bits instead of 32 bits for connection identifiers used with
22446 the controller protocol, to greatly reduce risk of identifier reuse.
22447 - When we're choosing an exit node for a circuit, and we have
22448 no pending streams, choose a good general exit rather than one that
22449 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
22450 - Fix another case of assuming, when a specific exit is requested,
22451 that we know more than the user about what hosts it allows.
22452 Fixes one case of bug 752. Patch from rovv.
22453 - Clip the MaxCircuitDirtiness config option to a minimum of 10
22454 seconds. Warn the user if lower values are given in the
22455 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
22456 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
22457 user if lower values are given in the configuration. Bugfix on
22458 0.1.1.17-rc. Patch by Sebastian.
22459 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
22460 the cache because we already had a v0 descriptor with the same ID.
22461 Bugfix on 0.2.0.18-alpha.
22462 - Fix a race condition when freeing keys shared between main thread
22463 and CPU workers that could result in a memory leak. Bugfix on
22464 0.1.0.1-rc. Fixes bug 889.
22465 - Send a valid END cell back when a client tries to connect to a
22466 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
22467 840. Patch from rovv.
22468 - Check which hops rendezvous stream cells are associated with to
22469 prevent possible guess-the-streamid injection attacks from
22470 intermediate hops. Fixes another case of bug 446. Based on patch
22472 - If a broken client asks a non-exit router to connect somewhere,
22473 do not even do the DNS lookup before rejecting the connection.
22474 Fixes another case of bug 619. Patch from rovv.
22475 - When a relay gets a create cell it can't decrypt (e.g. because it's
22476 using the wrong onion key), we were dropping it and letting the
22477 client time out. Now actually answer with a destroy cell. Fixes
22478 bug 904. Bugfix on 0.0.2pre8.
22480 o Minor bugfixes (hidden services):
22481 - Do not throw away existing introduction points on SIGHUP. Bugfix on
22482 0.0.6pre1. Patch by Karsten. Fixes bug 874.
22485 - Report the case where all signatures in a detached set are rejected
22486 differently than the case where there is an error handling the
22488 - When we realize that another process has modified our cached
22489 descriptors, print out a more useful error message rather than
22490 triggering an assertion. Fixes bug 885. Patch from Karsten.
22491 - Implement the 0x20 hack to better resist DNS poisoning: set the
22492 case on outgoing DNS requests randomly, and reject responses that do
22493 not match the case correctly. This logic can be disabled with the
22494 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
22495 of servers that do not reliably preserve case in replies. See
22496 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
22498 - Check DNS replies for more matching fields to better resist DNS
22500 - Never use OpenSSL compression: it wastes RAM and CPU trying to
22501 compress cells, which are basically all encrypted, compressed, or
22505 Changes in version 0.2.1.11-alpha - 2009-01-20
22506 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
22507 week it will take a long time to bootstrap again" bug. It also fixes
22508 an important security-related bug reported by Ilja van Sprundel. You
22509 should upgrade. (We'll send out more details about the bug once people
22510 have had some time to upgrade.)
22513 - Fix a heap-corruption bug that may be remotely triggerable on
22514 some platforms. Reported by Ilja van Sprundel.
22517 - Discard router descriptors as we load them if they are more than
22518 five days old. Otherwise if Tor is off for a long time and then
22519 starts with cached descriptors, it will try to use the onion
22520 keys in those obsolete descriptors when building circuits. Bugfix
22521 on 0.2.0.x. Fixes bug 887.
22524 - Try to make sure that the version of Libevent we're running with
22525 is binary-compatible with the one we built with. May address bug
22527 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
22528 for bug 905. Bugfix on 0.2.1.7-alpha.
22529 - Add a new --enable-local-appdata configuration switch to change
22530 the default location of the datadir on win32 from APPDATA to
22531 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
22532 entirely. Patch from coderman.
22535 - Make outbound DNS packets respect the OutboundBindAddress setting.
22536 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
22537 - When our circuit fails at the first hop (e.g. we get a destroy
22538 cell back), avoid using that OR connection anymore, and also
22539 tell all the one-hop directory requests waiting for it that they
22540 should fail. Bugfix on 0.2.1.3-alpha.
22541 - In the torify(1) manpage, mention that tsocks will leak your
22545 Changes in version 0.2.1.10-alpha - 2009-01-06
22546 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
22547 would make the bridge relay not so useful if it had DirPort set to 0,
22548 and one that could let an attacker learn a little bit of information
22549 about the bridge's users), and a bug that would cause your Tor relay
22550 to ignore a circuit create request it can't decrypt (rather than reply
22551 with an error). It also fixes a wide variety of other bugs.
22554 - If the cached networkstatus consensus is more than five days old,
22555 discard it rather than trying to use it. In theory it could
22556 be useful because it lists alternate directory mirrors, but in
22557 practice it just means we spend many minutes trying directory
22558 mirrors that are long gone from the network. Helps bug 887 a bit;
22560 - Bridge relays that had DirPort set to 0 would stop fetching
22561 descriptors shortly after startup, and then briefly resume
22562 after a new bandwidth test and/or after publishing a new bridge
22563 descriptor. Bridge users that try to bootstrap from them would
22564 get a recent networkstatus but would get descriptors from up to
22565 18 hours earlier, meaning most of the descriptors were obsolete
22566 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
22567 - Prevent bridge relays from serving their 'extrainfo' document
22568 to anybody who asks, now that extrainfo docs include potentially
22569 sensitive aggregated client geoip summaries. Bugfix on
22573 - New controller event "clients_seen" to report a geoip-based summary
22574 of which countries we've seen clients from recently. Now controllers
22575 like Vidalia can show bridge operators that they're actually making
22577 - Build correctly against versions of OpenSSL 0.9.8 or later built
22578 without support for deprecated functions.
22579 - Update to the "December 19 2008" ip-to-country file.
22581 o Minor bugfixes (on 0.2.0.x):
22582 - Authorities now vote for the Stable flag for any router whose
22583 weighted MTBF is at least 5 days, regardless of the mean MTBF.
22584 - Do not remove routers as too old if we do not have any consensus
22585 document. Bugfix on 0.2.0.7-alpha.
22586 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
22587 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
22588 - When an exit relay resolves a stream address to a local IP address,
22589 do not just keep retrying that same exit relay over and
22590 over. Instead, just close the stream. Addresses bug 872. Bugfix
22591 on 0.2.0.32. Patch from rovv.
22592 - If a hidden service sends us an END cell, do not consider
22593 retrying the connection; just close it. Patch from rovv.
22594 - When we made bridge authorities stop serving bridge descriptors over
22595 unencrypted links, we also broke DirPort reachability testing for
22596 bridges. So bridges with a non-zero DirPort were printing spurious
22597 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
22598 - When a relay gets a create cell it can't decrypt (e.g. because it's
22599 using the wrong onion key), we were dropping it and letting the
22600 client time out. Now actually answer with a destroy cell. Fixes
22601 bug 904. Bugfix on 0.0.2pre8.
22602 - Squeeze 2-5% out of client performance (according to oprofile) by
22603 improving the implementation of some policy-manipulation functions.
22605 o Minor bugfixes (on 0.2.1.x):
22606 - Make get_interface_address() function work properly again; stop
22607 guessing the wrong parts of our address as our address.
22608 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
22609 send on that circuit. Otherwise we might violate the proposal-110
22610 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
22612 - When we're sending non-EXTEND cells to the first hop in a circuit,
22613 for example to use an encrypted directory connection, we don't need
22614 to use RELAY_EARLY cells: the first hop knows what kind of cell
22615 it is, and nobody else can even see the cell type. Conserving
22616 RELAY_EARLY cells makes it easier to cannibalize circuits like
22618 - Stop logging nameserver addresses in reverse order.
22619 - If we are retrying a directory download slowly over and over, do
22620 not automatically give up after the 254th failure. Bugfix on
22622 - Resume reporting accurate "stream end" reasons to the local control
22623 port. They were lost in the changes for Proposal 148. Bugfix on
22626 o Deprecated and removed features:
22627 - The old "tor --version --version" command, which would print out
22628 the subversion "Id" of most of the source files, is now removed. It
22629 turned out to be less useful than we'd expected, and harder to
22632 o Code simplifications and refactoring:
22633 - Change our header file guard macros to be less likely to conflict
22634 with system headers. Adam Langley noticed that we were conflicting
22635 with log.h on Android.
22636 - Tool-assisted documentation cleanup. Nearly every function or
22637 static variable in Tor should have its own documentation now.
22640 Changes in version 0.2.1.9-alpha - 2008-12-25
22641 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
22643 o New directory authorities:
22644 - gabelmoo (the authority run by Karsten Loesing) now has a new
22648 - Never use a connection with a mismatched address to extend a
22649 circuit, unless that connection is canonical. A canonical
22650 connection is one whose address is authenticated by the router's
22651 identity key, either in a NETINFO cell or in a router descriptor.
22652 - Avoid a possible memory corruption bug when receiving hidden service
22653 descriptors. Bugfix on 0.2.1.6-alpha.
22656 - Fix a logic error that would automatically reject all but the first
22657 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
22658 part of bug 813/868. Bug spotted by coderman.
22659 - When a stream at an exit relay is in state "resolving" or
22660 "connecting" and it receives an "end" relay cell, the exit relay
22661 would silently ignore the end cell and not close the stream. If
22662 the client never closes the circuit, then the exit relay never
22663 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
22664 reported by "wood".
22665 - When we can't initialize DNS because the network is down, do not
22666 automatically stop Tor from starting. Instead, retry failed
22667 dns_init() every 10 minutes, and change the exit policy to reject
22668 *:* until one succeeds. Fixes bug 691.
22671 - Give a better error message when an overzealous init script says
22672 "sudo -u username tor --user username". Makes Bug 882 easier for
22674 - When a directory authority gives us a new guess for our IP address,
22675 log which authority we used. Hopefully this will help us debug
22676 the recent complaints about bad IP address guesses.
22677 - Detect svn revision properly when we're using git-svn.
22678 - Try not to open more than one descriptor-downloading connection
22679 to an authority at once. This should reduce load on directory
22680 authorities. Fixes bug 366.
22681 - Add cross-certification to newly generated certificates, so that
22682 a signing key is enough information to look up a certificate.
22683 Partial implementation of proposal 157.
22684 - Start serving certificates by <identity digest, signing key digest>
22685 pairs. Partial implementation of proposal 157.
22686 - Clients now never report any stream end reason except 'MISC'.
22687 Implements proposal 148.
22688 - On platforms with a maximum syslog string length, truncate syslog
22689 messages to that length ourselves, rather than relying on the
22690 system to do it for us.
22691 - Optimize out calls to time(NULL) that occur for every IO operation,
22692 or for every cell. On systems where time() is a slow syscall,
22693 this fix will be slightly helpful.
22694 - Exit servers can now answer resolve requests for ip6.arpa addresses.
22695 - When we download a descriptor that we then immediately (as
22696 a directory authority) reject, do not retry downloading it right
22697 away. Should save some bandwidth on authorities. Fix for bug
22698 888. Patch by Sebastian Hahn.
22699 - When a download gets us zero good descriptors, do not notify
22700 Tor that new directory information has arrived.
22701 - Avoid some nasty corner cases in the logic for marking connections
22702 as too old or obsolete or noncanonical for circuits. Partial
22705 o Minor features (controller):
22706 - New CONSENSUS_ARRIVED event to note when a new consensus has
22707 been fetched and validated.
22708 - When we realize that another process has modified our cached
22709 descriptors file, print out a more useful error message rather
22710 than triggering an assertion. Fixes bug 885. Patch from Karsten.
22711 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
22712 controllers to prevent SIGHUP from reloading the
22713 configuration. Fixes bug 856.
22716 - Resume using the correct "REASON=" stream when telling the
22717 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
22718 - When a canonical connection appears later in our internal list
22719 than a noncanonical one for a given OR ID, always use the
22720 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
22722 - Clip the MaxCircuitDirtiness config option to a minimum of 10
22723 seconds. Warn the user if lower values are given in the
22724 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
22725 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
22726 user if lower values are given in the configuration. Bugfix on
22727 0.1.1.17-rc. Patch by Sebastian.
22728 - Fix a race condition when freeing keys shared between main thread
22729 and CPU workers that could result in a memory leak. Bugfix on
22730 0.1.0.1-rc. Fixes bug 889.
22732 o Minor bugfixes (hidden services):
22733 - Do not throw away existing introduction points on SIGHUP (bugfix on
22734 0.0.6pre1); also, do not stall hidden services because we're
22735 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
22736 by John Brooks. Patch by Karsten. Fixes bug 874.
22737 - Fix a memory leak when we decline to add a v2 rendezvous
22738 descriptor to the cache because we already had a v0 descriptor
22739 with the same ID. Bugfix on 0.2.0.18-alpha.
22741 o Deprecated and removed features:
22742 - RedirectExits has been removed. It was deprecated since
22744 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
22745 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
22746 - Cell pools are now always enabled; --disable-cell-pools is ignored.
22748 o Code simplifications and refactoring:
22749 - Rename the confusing or_is_obsolete field to the more appropriate
22750 is_bad_for_new_circs, and move it to or_connection_t where it
22752 - Move edge-only flags from connection_t to edge_connection_t: not
22753 only is this better coding, but on machines of plausible alignment,
22754 it should save 4-8 bytes per connection_t. "Every little bit helps."
22755 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
22756 for consistency; keep old option working for backward compatibility.
22757 - Simplify the code for finding connections to use for a circuit.
22760 Changes in version 0.2.1.8-alpha - 2008-12-08
22761 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
22762 builds better on unusual platforms like Solaris and old OS X, and
22763 fixes a variety of other issues.
22766 - New DirPortFrontPage option that takes an html file and publishes
22767 it as "/" on the DirPort. Now relay operators can provide a
22768 disclaimer without needing to set up a separate webserver. There's
22769 a sample disclaimer in contrib/tor-exit-notice.html.
22772 - When the client is choosing entry guards, now it selects at most
22773 one guard from a given relay family. Otherwise we could end up with
22774 all of our entry points into the network run by the same operator.
22775 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
22778 - Fix a DOS opportunity during the voting signature collection process
22779 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
22780 - Fix a possible segfault when establishing an exit connection. Bugfix
22784 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
22786 - Made Tor a little less aggressive about deleting expired
22787 certificates. Partial fix for bug 854.
22788 - Stop doing unaligned memory access that generated bus errors on
22789 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
22790 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
22791 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
22792 - Make USR2 log-level switch take effect immediately. Bugfix on
22794 - If one win32 nameserver fails to get added, continue adding the
22795 rest, and don't automatically fail.
22796 - Use fcntl() for locking when flock() is not available. Should fix
22797 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
22798 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
22799 could make gcc generate non-functional binary search code. Bugfix
22801 - Build correctly on platforms without socklen_t.
22802 - Avoid potential crash on internal error during signature collection.
22803 Fixes bug 864. Patch from rovv.
22804 - Do not use C's stdio library for writing to log files. This will
22805 improve logging performance by a minute amount, and will stop
22806 leaking fds when our disk is full. Fixes bug 861.
22807 - Stop erroneous use of O_APPEND in cases where we did not in fact
22808 want to re-seek to the end of a file before every last write().
22809 - Correct handling of possible malformed authority signing key
22810 certificates with internal signature types. Fixes bug 880. Bugfix
22812 - Fix a hard-to-trigger resource leak when logging credential status.
22816 - Directory mirrors no longer fetch the v1 directory or
22817 running-routers files. They are obsolete, and nobody asks for them
22818 anymore. This is the first step to making v1 authorities obsolete.
22820 o Minor features (controller):
22821 - Return circuit purposes in response to GETINFO circuit-status. Fixes
22825 Changes in version 0.2.0.32 - 2008-11-20
22826 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
22827 packages (and maybe other packages) noticed by Theo de Raadt, fixes
22828 a smaller security flaw that might allow an attacker to access local
22829 services, further improves hidden service performance, and fixes a
22830 variety of other issues.
22833 - The "User" and "Group" config options did not clear the
22834 supplementary group entries for the Tor process. The "User" option
22835 is now more robust, and we now set the groups to the specified
22836 user's primary group. The "Group" option is now ignored. For more
22837 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
22838 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
22839 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
22840 - The "ClientDNSRejectInternalAddresses" config option wasn't being
22841 consistently obeyed: if an exit relay refuses a stream because its
22842 exit policy doesn't allow it, we would remember what IP address
22843 the relay said the destination address resolves to, even if it's
22844 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
22847 - Fix a DOS opportunity during the voting signature collection process
22848 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
22850 o Major bugfixes (hidden services):
22851 - When fetching v0 and v2 rendezvous service descriptors in parallel,
22852 we were failing the whole hidden service request when the v0
22853 descriptor fetch fails, even if the v2 fetch is still pending and
22854 might succeed. Similarly, if the last v2 fetch fails, we were
22855 failing the whole hidden service request even if a v0 fetch is
22856 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
22857 - When extending a circuit to a hidden service directory to upload a
22858 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
22859 requests failed, because the router descriptor has not been
22860 downloaded yet. In these cases, do not attempt to upload the
22861 rendezvous descriptor, but wait until the router descriptor is
22862 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
22863 descriptor from a hidden service directory for which the router
22864 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
22868 - Fix several infrequent memory leaks spotted by Coverity.
22869 - When testing for libevent functions, set the LDFLAGS variable
22870 correctly. Found by Riastradh.
22871 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
22872 bootstrapping with tunneled directory connections. Bugfix on
22873 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
22874 - When asked to connect to A.B.exit:80, if we don't know the IP for A
22875 and we know that server B rejects most-but-not all connections to
22876 port 80, we would previously reject the connection. Now, we assume
22877 the user knows what they were asking for. Fixes bug 752. Bugfix
22878 on 0.0.9rc5. Diagnosed by BarkerJr.
22879 - If we overrun our per-second write limits a little, count this as
22880 having used up our write allocation for the second, and choke
22881 outgoing directory writes. Previously, we had only counted this when
22882 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
22883 Bugfix on 0.2.0.x (??).
22884 - Remove the old v2 directory authority 'lefkada' from the default
22885 list. It has been gone for many months.
22886 - Stop doing unaligned memory access that generated bus errors on
22887 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
22888 - Make USR2 log-level switch take effect immediately. Bugfix on
22891 o Minor bugfixes (controller):
22892 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
22893 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
22896 Changes in version 0.2.1.7-alpha - 2008-11-08
22897 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
22898 packages (and maybe other packages) noticed by Theo de Raadt, fixes
22899 a smaller security flaw that might allow an attacker to access local
22900 services, adds better defense against DNS poisoning attacks on exit
22901 relays, further improves hidden service performance, and fixes a
22902 variety of other issues.
22905 - The "ClientDNSRejectInternalAddresses" config option wasn't being
22906 consistently obeyed: if an exit relay refuses a stream because its
22907 exit policy doesn't allow it, we would remember what IP address
22908 the relay said the destination address resolves to, even if it's
22909 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
22910 - The "User" and "Group" config options did not clear the
22911 supplementary group entries for the Tor process. The "User" option
22912 is now more robust, and we now set the groups to the specified
22913 user's primary group. The "Group" option is now ignored. For more
22914 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
22915 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
22916 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
22917 - Do not use or believe expired v3 authority certificates. Patch
22918 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
22921 - Now NodeFamily and MyFamily config options allow spaces in
22922 identity fingerprints, so it's easier to paste them in.
22923 Suggested by Lucky Green.
22924 - Implement the 0x20 hack to better resist DNS poisoning: set the
22925 case on outgoing DNS requests randomly, and reject responses that do
22926 not match the case correctly. This logic can be disabled with the
22927 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
22928 of servers that do not reliably preserve case in replies. See
22929 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
22931 - Preserve case in replies to DNSPort requests in order to support
22932 the 0x20 hack for resisting DNS poisoning attacks.
22934 o Hidden service performance improvements:
22935 - When the client launches an introduction circuit, retry with a
22936 new circuit after 30 seconds rather than 60 seconds.
22937 - Launch a second client-side introduction circuit in parallel
22938 after a delay of 15 seconds (based on work by Christian Wilms).
22939 - Hidden services start out building five intro circuits rather
22940 than three, and when the first three finish they publish a service
22941 descriptor using those. Now we publish our service descriptor much
22942 faster after restart.
22945 - Minor fix in the warning messages when you're having problems
22946 bootstrapping; also, be more forgiving of bootstrap problems when
22947 we're still making incremental progress on a given bootstrap phase.
22948 - When we're choosing an exit node for a circuit, and we have
22949 no pending streams, choose a good general exit rather than one that
22950 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
22951 - Send a valid END cell back when a client tries to connect to a
22952 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
22953 840. Patch from rovv.
22954 - If a broken client asks a non-exit router to connect somewhere,
22955 do not even do the DNS lookup before rejecting the connection.
22956 Fixes another case of bug 619. Patch from rovv.
22957 - Fix another case of assuming, when a specific exit is requested,
22958 that we know more than the user about what hosts it allows.
22959 Fixes another case of bug 752. Patch from rovv.
22960 - Check which hops rendezvous stream cells are associated with to
22961 prevent possible guess-the-streamid injection attacks from
22962 intermediate hops. Fixes another case of bug 446. Based on patch
22964 - Avoid using a negative right-shift when comparing 32-bit
22965 addresses. Possible fix for bug 845 and bug 811.
22966 - Make the assert_circuit_ok() function work correctly on circuits that
22967 have already been marked for close.
22968 - Fix read-off-the-end-of-string error in unit tests when decoding
22969 introduction points.
22970 - Fix uninitialized size field for memory area allocation: may improve
22971 memory performance during directory parsing.
22972 - Treat duplicate certificate fetches as failures, so that we do
22973 not try to re-fetch an expired certificate over and over and over.
22974 - Do not say we're fetching a certificate when we'll in fact skip it
22975 because of a pending download.
22978 Changes in version 0.2.1.6-alpha - 2008-09-30
22979 Tor 0.2.1.6-alpha further improves performance and robustness of
22980 hidden services, starts work on supporting per-country relay selection,
22981 and fixes a variety of smaller issues.
22984 - Implement proposal 121: make it possible to build hidden services
22985 that only certain clients are allowed to connect to. This is
22986 enforced at several points, so that unauthorized clients are unable
22987 to send INTRODUCE cells to the service, or even (depending on the
22988 type of authentication) to learn introduction points. This feature
22989 raises the bar for certain kinds of active attacks against hidden
22990 services. Code by Karsten Loesing.
22991 - Relays now store and serve v2 hidden service descriptors by default,
22992 i.e., the new default value for HidServDirectoryV2 is 1. This is
22993 the last step in proposal 114, which aims to make hidden service
22994 lookups more reliable.
22995 - Start work to allow node restrictions to include country codes. The
22996 syntax to exclude nodes in a country with country code XX is
22997 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
22998 refinement to decide what config options should take priority if
22999 you ask to both use a particular node and exclude it.
23000 - Allow ExitNodes list to include IP ranges and country codes, just
23001 like the Exclude*Nodes lists. Patch from Robert Hogan.
23004 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
23005 Tor to fail to start if you had it configured to use a bridge
23006 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
23007 - When extending a circuit to a hidden service directory to upload a
23008 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
23009 requests failed, because the router descriptor had not been
23010 downloaded yet. In these cases, we now wait until the router
23011 descriptor is downloaded, and then retry. Likewise, clients
23012 now skip over a hidden service directory if they don't yet have
23013 its router descriptor, rather than futilely requesting it and
23014 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
23016 - When fetching v0 and v2 rendezvous service descriptors in parallel,
23017 we were failing the whole hidden service request when the v0
23018 descriptor fetch fails, even if the v2 fetch is still pending and
23019 might succeed. Similarly, if the last v2 fetch fails, we were
23020 failing the whole hidden service request even if a v0 fetch is
23021 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
23022 - DNS replies need to have names matching their requests, but
23023 these names should be in the questions section, not necessarily
23024 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
23027 - Update to the "September 1 2008" ip-to-country file.
23028 - Allow ports 465 and 587 in the default exit policy again. We had
23029 rejected them in 0.1.0.15, because back in 2005 they were commonly
23030 misconfigured and ended up as spam targets. We hear they are better
23031 locked down these days.
23032 - Use a lockfile to make sure that two Tor processes are not
23033 simultaneously running with the same datadir.
23034 - Serve the latest v3 networkstatus consensus via the control
23035 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
23036 - Better logging about stability/reliability calculations on directory
23038 - Drop the requirement to have an open dir port for storing and
23039 serving v2 hidden service descriptors.
23040 - Directory authorities now serve a /tor/dbg-stability.txt URL to
23041 help debug WFU and MTBF calculations.
23042 - Implement most of Proposal 152: allow specialized servers to permit
23043 single-hop circuits, and clients to use those servers to build
23044 single-hop circuits when using a specialized controller. Patch
23045 from Josh Albrecht. Resolves feature request 768.
23046 - Add a -p option to tor-resolve for specifying the SOCKS port: some
23047 people find host:port too confusing.
23048 - Make TrackHostExit mappings expire a while after their last use, not
23049 after their creation. Patch from Robert Hogan.
23050 - Provide circuit purposes along with circuit events to the controller.
23053 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
23055 - Fixed some memory leaks -- some quite frequent, some almost
23056 impossible to trigger -- based on results from Coverity.
23057 - When testing for libevent functions, set the LDFLAGS variable
23058 correctly. Found by Riastradh.
23059 - Fix an assertion bug in parsing policy-related options; possible fix
23061 - Catch and report a few more bootstrapping failure cases when Tor
23062 fails to establish a TCP connection. Cleanup on 0.2.1.x.
23063 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
23064 bootstrapping with tunneled directory connections. Bugfix on
23065 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
23066 - When asked to connect to A.B.exit:80, if we don't know the IP for A
23067 and we know that server B rejects most-but-not all connections to
23068 port 80, we would previously reject the connection. Now, we assume
23069 the user knows what they were asking for. Fixes bug 752. Bugfix
23070 on 0.0.9rc5. Diagnosed by BarkerJr.
23071 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
23072 service directories if they have no advertised dir port. Bugfix
23074 - If we overrun our per-second write limits a little, count this as
23075 having used up our write allocation for the second, and choke
23076 outgoing directory writes. Previously, we had only counted this when
23077 we had met our limits precisely. Fixes bug 824. Patch by rovv.
23078 Bugfix on 0.2.0.x (??).
23079 - Avoid a "0 divided by 0" calculation when calculating router uptime
23080 at directory authorities. Bugfix on 0.2.0.8-alpha.
23081 - Make DNS resolved controller events into "CLOSED", not
23082 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
23084 - Fix a bug where an unreachable relay would establish enough
23085 reachability testing circuits to do a bandwidth test -- if
23086 we already have a connection to the middle hop of the testing
23087 circuit, then it could establish the last hop by using the existing
23088 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
23089 circuits no longer use entry guards in 0.2.1.3-alpha.
23090 - If we have correct permissions on $datadir, we complain to stdout
23091 and fail to start. But dangerous permissions on
23092 $datadir/cached-status/ would cause us to open a log and complain
23093 there. Now complain to stdout and fail to start in both cases. Fixes
23094 bug 820, reported by seeess.
23095 - Remove the old v2 directory authority 'lefkada' from the default
23096 list. It has been gone for many months.
23098 o Code simplifications and refactoring:
23099 - Revise the connection_new functions so that a more typesafe variant
23100 exists. This will work better with Coverity, and let us find any
23101 actual mistakes we're making here.
23102 - Refactor unit testing logic so that dmalloc can be used sensibly
23103 with unit tests to check for memory leaks.
23104 - Move all hidden-service related fields from connection and circuit
23105 structure to substructures: this way they won't eat so much memory.
23108 Changes in version 0.2.0.31 - 2008-09-03
23109 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
23110 a big bug we're seeing where in rare cases traffic from one Tor stream
23111 gets mixed into another stream, and fixes a variety of smaller issues.
23114 - Make sure that two circuits can never exist on the same connection
23115 with the same circuit ID, even if one is marked for close. This
23116 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
23117 - Relays now reject risky extend cells: if the extend cell includes
23118 a digest of all zeroes, or asks to extend back to the relay that
23119 sent the extend cell, tear down the circuit. Ideas suggested
23121 - If not enough of our entry guards are available so we add a new
23122 one, we might use the new one even if it overlapped with the
23123 current circuit's exit relay (or its family). Anonymity bugfix
23124 pointed out by rovv.
23127 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
23128 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
23129 - Correctly detect the presence of the linux/netfilter_ipv4.h header
23130 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
23131 - Pick size of default geoip filename string correctly on windows.
23132 Fixes bug 806. Bugfix on 0.2.0.30.
23133 - Make the autoconf script accept the obsolete --with-ssl-dir
23134 option as an alias for the actually-working --with-openssl-dir
23135 option. Fix the help documentation to recommend --with-openssl-dir.
23136 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
23137 - When using the TransPort option on OpenBSD, and using the User
23138 option to change UID and drop privileges, make sure to open
23139 /dev/pf before dropping privileges. Fixes bug 782. Patch from
23140 Christopher Davis. Bugfix on 0.1.2.1-alpha.
23141 - Try to attach connections immediately upon receiving a RENDEZVOUS2
23142 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
23143 on the client side when connecting to a hidden service. Bugfix
23144 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
23145 - When closing an application-side connection because its circuit is
23146 getting torn down, generate the stream event correctly. Bugfix on
23147 0.1.2.x. Anonymous patch.
23150 Changes in version 0.2.1.5-alpha - 2008-08-31
23151 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
23152 in a lot of the infrastructure for adding authorization to hidden
23153 services, lays the groundwork for having clients read their load
23154 balancing information out of the networkstatus consensus rather than
23155 the individual router descriptors, addresses two potential anonymity
23156 issues, and fixes a variety of smaller issues.
23159 - Convert many internal address representations to optionally hold
23161 - Generate and accept IPv6 addresses in many protocol elements.
23162 - Make resolver code handle nameservers located at ipv6 addresses.
23163 - Begin implementation of proposal 121 ("Client authorization for
23164 hidden services"): configure hidden services with client
23165 authorization, publish descriptors for them, and configure
23166 authorization data for hidden services at clients. The next
23167 step is to actually access hidden services that perform client
23169 - More progress toward proposal 141: Network status consensus
23170 documents and votes now contain bandwidth information for each
23171 router and a summary of that router's exit policy. Eventually this
23172 will be used by clients so that they do not have to download every
23173 known descriptor before building circuits.
23175 o Major bugfixes (on 0.2.0.x and before):
23176 - When sending CREATED cells back for a given circuit, use a 64-bit
23177 connection ID to find the right connection, rather than an addr:port
23178 combination. Now that we can have multiple OR connections between
23179 the same ORs, it is no longer possible to use addr:port to uniquely
23180 identify a connection.
23181 - Relays now reject risky extend cells: if the extend cell includes
23182 a digest of all zeroes, or asks to extend back to the relay that
23183 sent the extend cell, tear down the circuit. Ideas suggested
23185 - If not enough of our entry guards are available so we add a new
23186 one, we might use the new one even if it overlapped with the
23187 current circuit's exit relay (or its family). Anonymity bugfix
23188 pointed out by rovv.
23191 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
23192 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
23193 - When using the TransPort option on OpenBSD, and using the User
23194 option to change UID and drop privileges, make sure to open /dev/pf
23195 before dropping privileges. Fixes bug 782. Patch from Christopher
23196 Davis. Bugfix on 0.1.2.1-alpha.
23197 - Correctly detect the presence of the linux/netfilter_ipv4.h header
23198 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
23199 - Add a missing safe_str() call for a debug log message.
23200 - Use 64 bits instead of 32 bits for connection identifiers used with
23201 the controller protocol, to greatly reduce risk of identifier reuse.
23202 - Make the autoconf script accept the obsolete --with-ssl-dir
23203 option as an alias for the actually-working --with-openssl-dir
23204 option. Fix the help documentation to recommend --with-openssl-dir.
23205 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
23208 - Rate-limit too-many-sockets messages: when they happen, they happen
23209 a lot. Resolves bug 748.
23210 - Resist DNS poisoning a little better by making sure that names in
23211 answer sections match.
23212 - Print the SOCKS5 error message string as well as the error code
23213 when a tor-resolve request fails. Patch from Jacob.
23216 Changes in version 0.2.1.4-alpha - 2008-08-04
23217 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
23220 - The address part of exit policies was not correctly written
23221 to router descriptors. This generated router descriptors that failed
23222 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
23224 - Tor triggered a false assert when extending a circuit to a relay
23225 but we already have a connection open to that relay. Noticed by
23226 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
23229 - Fix a hidden service logging bug: in some edge cases, the router
23230 descriptor of a previously picked introduction point becomes
23231 obsolete and we need to give up on it rather than continually
23232 complaining that it has become obsolete. Observed by xiando. Bugfix
23235 o Removed features:
23236 - Take out the TestVia config option, since it was a workaround for
23237 a bug that was fixed in Tor 0.1.1.21.
23240 Changes in version 0.2.1.3-alpha - 2008-08-03
23241 Tor 0.2.1.3-alpha implements most of the pieces to prevent
23242 infinite-length circuit attacks (see proposal 110); fixes a bug that
23243 might cause exit relays to corrupt streams they send back; allows
23244 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
23245 ExcludeExitNodes config options; and fixes a big pile of bugs.
23247 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
23248 - Send a bootstrap problem "warn" event on the first problem if the
23249 reason is NO_ROUTE (that is, our network is down).
23252 - Implement most of proposal 110: The first K cells to be sent
23253 along a circuit are marked as special "early" cells; only K "early"
23254 cells will be allowed. Once this code is universal, we can block
23255 certain kinds of DOS attack by requiring that EXTEND commands must
23256 be sent using an "early" cell.
23259 - Try to attach connections immediately upon receiving a RENDEZVOUS2
23260 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
23261 on the client side when connecting to a hidden service. Bugfix
23262 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
23263 - Ensure that two circuits can never exist on the same connection
23264 with the same circuit ID, even if one is marked for close. This
23265 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
23268 - When relays do their initial bandwidth measurement, don't limit
23269 to just our entry guards for the test circuits. Otherwise we tend
23270 to have multiple test circuits going through a single entry guard,
23271 which makes our bandwidth test less accurate. Fixes part of bug 654;
23272 patch contributed by Josh Albrecht.
23273 - Add an ExcludeExitNodes option so users can list a set of nodes
23274 that should be be excluded from the exit node position, but
23275 allowed elsewhere. Implements proposal 151.
23276 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
23277 ExcludeNodes and ExcludeExitNodes lists.
23278 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
23279 be more efficient. Formerly it was quadratic in the number of
23280 servers; now it should be linear. Fixes bug 509.
23281 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
23282 and n_conn_id_digest fields into a separate structure that's
23283 only needed when the circuit has not yet attached to an n_conn.
23286 - Change the contrib/tor.logrotate script so it makes the new
23287 logs as "_tor:_tor" rather than the default, which is generally
23288 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
23289 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
23290 warnings (occasionally), but it can also cause the compiler to
23291 eliminate error-checking code. Suggested by Peter Gutmann.
23292 - When a hidden service is giving up on an introduction point candidate
23293 that was not included in the last published rendezvous descriptor,
23294 don't reschedule publication of the next descriptor. Fixes bug 763.
23296 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
23297 HiddenServiceExcludeNodes as obsolete: they never worked properly,
23298 and nobody claims to be using them. Fixes bug 754. Bugfix on
23299 0.1.0.1-rc. Patch from Christian Wilms.
23300 - Fix a small alignment and memory-wasting bug on buffer chunks.
23303 o Minor bugfixes (controller):
23304 - When closing an application-side connection because its circuit
23305 is getting torn down, generate the stream event correctly.
23306 Bugfix on 0.1.2.x. Anonymous patch.
23308 o Removed features:
23309 - Remove all backward-compatibility code to support relays running
23310 versions of Tor so old that they no longer work at all on the
23314 Changes in version 0.2.0.30 - 2008-07-15
23316 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
23317 warnings (occasionally), but it can also cause the compiler to
23318 eliminate error-checking code. Suggested by Peter Gutmann.
23321 Changes in version 0.2.0.29-rc - 2008-07-08
23322 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
23323 hidden-service performance bugs, and fixes a bunch of smaller bugs.
23326 - If you have more than one bridge but don't know their keys,
23327 you would only launch a request for the descriptor of the first one
23328 on your list. (Tor considered launching requests for the others, but
23329 found that it already had a connection on the way for $0000...0000
23330 so it didn't open another.) Bugfix on 0.2.0.x.
23331 - If you have more than one bridge but don't know their keys, and the
23332 connection to one of the bridges failed, you would cancel all
23333 pending bridge connections. (After all, they all have the same
23334 digest.) Bugfix on 0.2.0.x.
23335 - When a hidden service was trying to establish an introduction point,
23336 and Tor had built circuits preemptively for such purposes, we
23337 were ignoring all the preemptive circuits and launching a new one
23338 instead. Bugfix on 0.2.0.14-alpha.
23339 - When a hidden service was trying to establish an introduction point,
23340 and Tor *did* manage to reuse one of the preemptively built
23341 circuits, it didn't correctly remember which one it used,
23342 so it asked for another one soon after, until there were no
23343 more preemptive circuits, at which point it launched one from
23344 scratch. Bugfix on 0.0.9.x.
23345 - Make directory servers include the X-Your-Address-Is: http header in
23346 their responses even for begin_dir conns. Now clients who only
23347 ever use begin_dir connections still have a way to learn their IP
23348 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
23351 - Fix a macro/CPP interaction that was confusing some compilers:
23352 some GCCs don't like #if/#endif pairs inside macro arguments.
23354 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
23355 Fixes bug 704; fix from Steven Murdoch.
23356 - When opening /dev/null in finish_daemonize(), do not pass the
23357 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
23358 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
23359 - Correctly detect transparent proxy support on Linux hosts that
23360 require in.h to be included before netfilter_ipv4.h. Patch
23362 - Disallow session resumption attempts during the renegotiation
23363 stage of the v2 handshake protocol. Clients should never be trying
23364 session resumption at this point, but apparently some did, in
23365 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
23366 found by Geoff Goodell.
23369 Changes in version 0.2.1.2-alpha - 2008-06-20
23370 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
23371 make it easier to set up your own private Tor network; fixes several
23372 big bugs with using more than one bridge relay; fixes a big bug with
23373 offering hidden services quickly after Tor starts; and uses a better
23374 API for reporting potential bootstrapping problems to the controller.
23377 - New TestingTorNetwork config option to allow adjustment of
23378 previously constant values that, while reasonable, could slow
23379 bootstrapping. Implements proposal 135. Patch from Karsten.
23382 - If you have more than one bridge but don't know their digests,
23383 you would only learn a request for the descriptor of the first one
23384 on your list. (Tor considered launching requests for the others, but
23385 found that it already had a connection on the way for $0000...0000
23386 so it didn't open another.) Bugfix on 0.2.0.x.
23387 - If you have more than one bridge but don't know their digests,
23388 and the connection to one of the bridges failed, you would cancel
23389 all pending bridge connections. (After all, they all have the
23390 same digest.) Bugfix on 0.2.0.x.
23391 - When establishing a hidden service, introduction points that
23392 originate from cannibalized circuits are completely ignored and not
23393 included in rendezvous service descriptors. This might be another
23394 reason for delay in making a hidden service available. Bugfix
23395 from long ago (0.0.9.x?)
23398 - Allow OpenSSL to use dynamic locks if it wants.
23399 - When building a consensus, do not include routers that are down.
23400 This will cut down 30% to 40% on consensus size. Implements
23402 - In directory authorities' approved-routers files, allow
23403 fingerprints with or without space.
23404 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
23405 controller can query our current bootstrap state in case it attaches
23406 partway through and wants to catch up.
23407 - Send an initial "Starting" bootstrap status event, so we have a
23408 state to start out in.
23411 - Asking for a conditional consensus at .../consensus/<fingerprints>
23412 would crash a dirserver if it did not already have a
23413 consensus. Bugfix on 0.2.1.1-alpha.
23414 - Clean up some macro/CPP interactions: some GCC versions don't like
23415 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
23418 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
23419 - Directory authorities shouldn't complain about bootstrapping
23420 problems just because they do a lot of reachability testing and
23421 some of the connection attempts fail.
23422 - Start sending "count" and "recommendation" key/value pairs in
23423 bootstrap problem status events, so the controller can hear about
23424 problems even before Tor decides they're worth reporting for sure.
23425 - If you're using bridges, generate "bootstrap problem" warnings
23426 as soon as you run out of working bridges, rather than waiting
23427 for ten failures -- which will never happen if you have less than
23429 - If we close our OR connection because there's been a circuit
23430 pending on it for too long, we were telling our bootstrap status
23431 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
23434 Changes in version 0.2.1.1-alpha - 2008-06-13
23435 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
23436 were making the Tor process bloat especially on Linux; makes our TLS
23437 handshake blend in better; sends "bootstrap phase" status events to
23438 the controller, so it can keep the user informed of progress (and
23439 problems) fetching directory information and establishing circuits;
23440 and adds a variety of smaller features.
23443 - More work on making our TLS handshake blend in: modify the list
23444 of ciphers advertised by OpenSSL in client mode to even more
23445 closely resemble a common web browser. We cheat a little so that
23446 we can advertise ciphers that the locally installed OpenSSL doesn't
23448 - Start sending "bootstrap phase" status events to the controller,
23449 so it can keep the user informed of progress fetching directory
23450 information and establishing circuits. Also inform the controller
23451 if we think we're stuck at a particular bootstrap phase. Implements
23453 - Resume using OpenSSL's RAND_poll() for better (and more portable)
23454 cross-platform entropy collection again. We used to use it, then
23455 stopped using it because of a bug that could crash systems that
23456 called RAND_poll when they had a lot of fds open. It looks like the
23457 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
23458 at startup, and to call RAND_poll() when we reseed later only if
23459 we have a non-buggy OpenSSL version.
23462 - When we choose to abandon a new entry guard because we think our
23463 older ones might be better, close any circuits pending on that
23464 new entry guard connection. This fix should make us recover much
23465 faster when our network is down and then comes back. Bugfix on
23466 0.1.2.8-beta; found by lodger.
23468 o Memory fixes and improvements:
23469 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
23470 to avoid unused RAM in buffer chunks and memory pools.
23471 - Speed up parsing and cut down on memory fragmentation by using
23472 stack-style allocations for parsing directory objects. Previously,
23473 this accounted for over 40% of allocations from within Tor's code
23474 on a typical directory cache.
23475 - Use a Bloom filter rather than a digest-based set to track which
23476 descriptors we need to keep around when we're cleaning out old
23477 router descriptors. This speeds up the computation significantly,
23478 and may reduce fragmentation.
23479 - Reduce the default smartlist size from 32 to 16; it turns out that
23480 most smartlists hold around 8-12 elements tops.
23481 - Make dumpstats() log the fullness and size of openssl-internal
23483 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
23484 patch to their OpenSSL, turn it on to save memory on servers. This
23485 patch will (with any luck) get included in a mainline distribution
23487 - Never use OpenSSL compression: it wastes RAM and CPU trying to
23488 compress cells, which are basically all encrypted, compressed,
23492 - Stop reloading the router list from disk for no reason when we
23493 run out of reachable directory mirrors. Once upon a time reloading
23494 it would set the 'is_running' flag back to 1 for them. It hasn't
23495 done that for a long time.
23496 - In very rare situations new hidden service descriptors were
23497 published earlier than 30 seconds after the last change to the
23498 service. (We currently think that a hidden service descriptor
23499 that's been stable for 30 seconds is worth publishing.)
23502 - Allow separate log levels to be configured for different logging
23503 domains. For example, this allows one to log all notices, warnings,
23504 or errors, plus all memory management messages of level debug or
23505 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
23506 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
23507 and stop using a warning that had become unfixably verbose under
23509 - New --hush command-line option similar to --quiet. While --quiet
23510 disables all logging to the console on startup, --hush limits the
23511 output to messages of warning and error severity.
23512 - Servers support a new URL scheme for consensus downloads that
23513 allows the client to specify which authorities are trusted.
23514 The server then only sends the consensus if the client will trust
23515 it. Otherwise a 404 error is sent back. Clients use this
23516 new scheme when the server supports it (meaning it's running
23517 0.2.1.1-alpha or later). Implements proposal 134.
23518 - New configure/torrc options (--enable-geoip-stats,
23519 DirRecordUsageByCountry) to record how many IPs we've served
23520 directory info to in each country code, how many status documents
23521 total we've sent to each country code, and what share of the total
23522 directory requests we should expect to see.
23523 - Use the TLS1 hostname extension to more closely resemble browser
23525 - Lots of new unit tests.
23526 - Add a macro to implement the common pattern of iterating through
23527 two parallel lists in lockstep.
23530 Changes in version 0.2.0.28-rc - 2008-06-13
23531 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
23532 performance bug, and fixes a bunch of smaller bugs.
23535 - Fix a bug where, when we were choosing the 'end stream reason' to
23536 put in our relay end cell that we send to the exit relay, Tor
23537 clients on Windows were sometimes sending the wrong 'reason'. The
23538 anonymity problem is that exit relays may be able to guess whether
23539 the client is running Windows, thus helping partition the anonymity
23540 set. Down the road we should stop sending reasons to exit relays,
23541 or otherwise prevent future versions of this bug.
23544 - While setting up a hidden service, some valid introduction circuits
23545 were overlooked and abandoned. This might be the reason for
23546 the long delay in making a hidden service available. Bugfix on
23550 - Update to the "June 9 2008" ip-to-country file.
23551 - Run 'make test' as part of 'make dist', so we stop releasing so
23552 many development snapshots that fail their unit tests.
23555 - When we're checking if we have enough dir info for each relay
23556 to begin establishing circuits, make sure that we actually have
23557 the descriptor listed in the consensus, not just any descriptor.
23559 - Bridge relays no longer print "xx=0" in their extrainfo document
23560 for every single country code in the geoip db. Bugfix on
23562 - Only warn when we fail to load the geoip file if we were planning to
23563 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
23564 - If we change our MaxAdvertisedBandwidth and then reload torrc,
23565 Tor won't realize it should publish a new relay descriptor. Fixes
23566 bug 688, reported by mfr. Bugfix on 0.1.2.x.
23567 - When we haven't had any application requests lately, don't bother
23568 logging that we have expired a bunch of descriptors. Bugfix
23570 - Make relay cells written on a connection count as non-padding when
23571 tracking how long a connection has been in use. Bugfix on
23572 0.2.0.1-alpha. Spotted by lodger.
23573 - Fix unit tests in 0.2.0.27-rc.
23574 - Fix compile on Windows.
23577 Changes in version 0.2.0.27-rc - 2008-06-03
23578 Tor 0.2.0.27-rc adds a few features we left out of the earlier
23579 release candidates. In particular, we now include an IP-to-country
23580 GeoIP database, so controllers can easily look up what country a
23581 given relay is in, and so bridge relays can give us some sanitized
23582 summaries about which countries are making use of bridges. (See proposal
23583 126-geoip-fetching.txt for details.)
23586 - Include an IP-to-country GeoIP file in the tarball, so bridge
23587 relays can report sanitized summaries of the usage they're seeing.
23590 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
23591 Robert Hogan. Fixes the first part of bug 681.
23592 - Make bridge authorities never serve extrainfo docs.
23593 - Add support to detect Libevent versions in the 1.4.x series
23595 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
23596 - Include a new contrib/tor-exit-notice.html file that exit relay
23597 operators can put on their website to help reduce abuse queries.
23600 - When tunneling an encrypted directory connection, and its first
23601 circuit fails, do not leave it unattached and ask the controller
23602 to deal. Fixes the second part of bug 681.
23603 - Make bridge authorities correctly expire old extrainfo documents
23607 Changes in version 0.2.0.26-rc - 2008-05-13
23608 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
23609 in Debian's OpenSSL packages. All users running any 0.2.0.x version
23610 should upgrade, whether they're running Debian or not.
23612 o Major security fixes:
23613 - Use new V3 directory authority keys on the tor26, gabelmoo, and
23614 moria1 V3 directory authorities. The old keys were generated with
23615 a vulnerable version of Debian's OpenSSL package, and must be
23616 considered compromised. Other authorities' keys were not generated
23617 with an affected version of OpenSSL.
23620 - List authority signatures as "unrecognized" based on DirServer
23621 lines, not on cert cache. Bugfix on 0.2.0.x.
23624 - Add a new V3AuthUseLegacyKey option to make it easier for
23625 authorities to change their identity keys if they have to.
23628 Changes in version 0.2.0.25-rc - 2008-04-23
23629 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
23632 - Remember to initialize threading before initializing logging.
23633 Otherwise, many BSD-family implementations will crash hard on
23634 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
23637 - Authorities correctly free policies on bad servers on
23638 exit. Fixes bug 672. Bugfix on 0.2.0.x.
23641 Changes in version 0.2.0.24-rc - 2008-04-22
23642 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
23643 v3 directory authority, makes relays with dynamic IP addresses and no
23644 DirPort notice more quickly when their IP address changes, fixes a few
23645 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
23647 o New directory authorities:
23648 - Take lefkada out of the list of v3 directory authorities, since
23649 it has been down for months.
23650 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
23654 - Detect address changes more quickly on non-directory mirror
23655 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
23657 o Minor features (security):
23658 - Reject requests for reverse-dns lookup of names that are in
23659 a private address space. Patch from lodger.
23660 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
23663 o Minor bugfixes (crashes):
23664 - Avoid a rare assert that can trigger when Tor doesn't have much
23665 directory information yet and it tries to fetch a v2 hidden
23666 service descriptor. Fixes bug 651, reported by nwf.
23667 - Initialize log mutex before initializing dmalloc. Otherwise,
23668 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
23669 - Use recursive pthread mutexes in order to avoid deadlock when
23670 logging debug-level messages to a controller. Bug spotted by nwf,
23671 bugfix on 0.2.0.16-alpha.
23673 o Minor bugfixes (resource management):
23674 - Keep address policies from leaking memory: start their refcount
23675 at 1, not 2. Bugfix on 0.2.0.16-alpha.
23676 - Free authority certificates on exit, so they don't look like memory
23677 leaks. Bugfix on 0.2.0.19-alpha.
23678 - Free static hashtables for policy maps and for TLS connections on
23679 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
23680 - Avoid allocating extra space when computing consensuses on 64-bit
23681 platforms. Bug spotted by aakova.
23683 o Minor bugfixes (misc):
23684 - Do not read the configuration file when we've only been told to
23685 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
23686 based on patch from Sebastian Hahn.
23687 - Exit relays that are used as a client can now reach themselves
23688 using the .exit notation, rather than just launching an infinite
23689 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
23690 - When attempting to open a logfile fails, tell us why.
23691 - Fix a dumb bug that was preventing us from knowing that we should
23692 preemptively build circuits to handle expected directory requests.
23693 Fixes bug 660. Bugfix on 0.1.2.x.
23694 - Warn less verbosely about clock skew from netinfo cells from
23695 untrusted sources. Fixes bug 663.
23696 - Make controller stream events for DNS requests more consistent,
23697 by adding "new stream" events for DNS requests, and removing
23698 spurious "stream closed" events" for cached reverse resolves.
23699 Patch from mwenge. Fixes bug 646.
23700 - Correctly notify one-hop connections when a circuit build has
23701 failed. Possible fix for bug 669. Found by lodger.
23704 Changes in version 0.2.0.23-rc - 2008-03-24
23705 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
23706 makes bootstrapping faster if the first directory mirror you contact
23707 is down. The bundles also include the new Vidalia 0.1.2 release.
23710 - When a tunneled directory request is made to a directory server
23711 that's down, notice after 30 seconds rather than 120 seconds. Also,
23712 fail any begindir streams that are pending on it, so they can
23713 retry elsewhere. This was causing multi-minute delays on bootstrap.
23716 Changes in version 0.2.0.22-rc - 2008-03-18
23717 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
23718 enables encrypted directory connections by default for non-relays, fixes
23719 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
23720 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
23723 - Enable encrypted directory connections by default for non-relays,
23724 so censor tools that block Tor directory connections based on their
23725 plaintext patterns will no longer work. This means Tor works in
23726 certain censored countries by default again.
23729 - Make sure servers always request certificates from clients during
23730 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
23731 - Do not enter a CPU-eating loop when a connection is closed in
23732 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
23733 diagnosed by lodger; bugfix on 0.2.0.20-rc.
23734 - Fix assertion failure that could occur when a blocked circuit
23735 became unblocked, and it had pending client DNS requests. Bugfix
23736 on 0.2.0.1-alpha. Fixes bug 632.
23738 o Minor bugfixes (on 0.1.2.x):
23739 - Generate "STATUS_SERVER" events rather than misspelled
23740 "STATUS_SEVER" events. Caught by mwenge.
23741 - When counting the number of bytes written on a TLS connection,
23742 look at the BIO actually used for writing to the network, not
23743 at the BIO used (sometimes) to buffer data for the network.
23744 Looking at different BIOs could result in write counts on the
23745 order of ULONG_MAX. Fixes bug 614.
23746 - On Windows, correctly detect errors when listing the contents of
23747 a directory. Fix from lodger.
23749 o Minor bugfixes (on 0.2.0.x):
23750 - Downgrade "sslv3 alert handshake failure" message to INFO.
23751 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
23752 left BandwidthRate and BandwidthBurst at the default, we would be
23753 silently limited by those defaults. Now raise them to match the
23754 RelayBandwidth* values.
23755 - Fix the SVK version detection logic to work correctly on a branch.
23756 - Make --enable-openbsd-malloc work correctly on Linux with alpha
23757 CPUs. Fixes bug 625.
23758 - Logging functions now check that the passed severity is sane.
23759 - Use proper log levels in the testsuite call of
23760 get_interface_address6().
23761 - When using a nonstandard malloc, do not use the platform values for
23762 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
23763 - Make the openbsd malloc code use 8k pages on alpha CPUs and
23765 - Detect mismatched page sizes when using --enable-openbsd-malloc.
23766 - Avoid double-marked-for-close warning when certain kinds of invalid
23767 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
23768 for bug 617. Bugfix on 0.2.0.1-alpha.
23769 - Make sure that the "NULL-means-reject *:*" convention is followed by
23770 all the policy manipulation functions, avoiding some possible crash
23771 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
23772 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
23773 actually works, and doesn't warn about every single reverse lookup.
23774 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
23777 - Only log guard node status when guard node status has changed.
23778 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
23779 make "INFO" 75% less verbose.
23782 Changes in version 0.2.0.21-rc - 2008-03-02
23783 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
23784 makes Tor work well with Vidalia again, fixes a rare assert bug,
23785 and fixes a pair of more minor bugs. The bundles also include Vidalia
23786 0.1.0 and Torbutton 1.1.16.
23789 - The control port should declare that it requires password auth
23790 when HashedControlSessionPassword is set too. Patch from Matt Edman;
23791 bugfix on 0.2.0.20-rc. Fixes bug 615.
23792 - Downgrade assert in connection_buckets_decrement() to a log message.
23793 This may help us solve bug 614, and in any case will make its
23794 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
23795 - We were sometimes miscounting the number of bytes read from the
23796 network, causing our rate limiting to not be followed exactly.
23797 Bugfix on 0.2.0.16-alpha. Reported by lodger.
23800 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
23801 OpenSSL versions should have been working fine. Diagnosis and patch
23802 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
23803 Bugfix on 0.2.0.20-rc.
23806 Changes in version 0.2.0.20-rc - 2008-02-24
23807 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
23808 makes more progress towards normalizing Tor's TLS handshake, makes
23809 hidden services work better again, helps relays bootstrap if they don't
23810 know their IP address, adds optional support for linking in openbsd's
23811 allocator or tcmalloc, allows really fast relays to scale past 15000
23812 sockets, and fixes a bunch of minor bugs reported by Veracode.
23815 - Enable the revised TLS handshake based on the one designed by
23816 Steven Murdoch in proposal 124, as revised in proposal 130. It
23817 includes version negotiation for OR connections as described in
23818 proposal 105. The new handshake is meant to be harder for censors
23819 to fingerprint, and it adds the ability to detect certain kinds of
23820 man-in-the-middle traffic analysis attacks. The version negotiation
23821 feature will allow us to improve Tor's link protocol more safely
23823 - Choose which bridge to use proportional to its advertised bandwidth,
23824 rather than uniformly at random. This should speed up Tor for
23825 bridge users. Also do this for people who set StrictEntryNodes.
23826 - When a TrackHostExits-chosen exit fails too many times in a row,
23827 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
23830 - Resolved problems with (re-)fetching hidden service descriptors.
23831 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
23832 and 0.2.0.19-alpha.
23833 - If we only ever used Tor for hidden service lookups or posts, we
23834 would stop building circuits and start refusing connections after
23835 24 hours, since we falsely believed that Tor was dormant. Reported
23836 by nwf; bugfix on 0.1.2.x.
23837 - Servers that don't know their own IP address should go to the
23838 authorities for their first directory fetch, even if their DirPort
23839 is off or if they don't know they're reachable yet. This will help
23840 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
23841 - When counting the number of open sockets, count not only the number
23842 of sockets we have received from the socket() call, but also
23843 the number we've gotten from accept() and socketpair(). This bug
23844 made us fail to count all sockets that we were using for incoming
23845 connections. Bugfix on 0.2.0.x.
23846 - Fix code used to find strings within buffers, when those strings
23847 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
23848 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
23849 - Add a new __HashedControlSessionPassword option for controllers
23850 to use for one-off session password hashes that shouldn't get
23851 saved to disk by SAVECONF --- Vidalia users were accumulating a
23852 pile of HashedControlPassword lines in their torrc files, one for
23853 each time they had restarted Tor and then clicked Save. Make Tor
23854 automatically convert "HashedControlPassword" to this new option but
23855 only when it's given on the command line. Partial fix for bug 586.
23857 o Minor features (performance):
23858 - Tune parameters for cell pool allocation to minimize amount of
23860 - Add OpenBSD malloc code from phk as an optional malloc
23861 replacement on Linux: some glibc libraries do very poorly
23862 with Tor's memory allocation patterns. Pass
23863 --enable-openbsd-malloc to get the replacement malloc code.
23864 - Add a --with-tcmalloc option to the configure script to link
23865 against tcmalloc (if present). Does not yet search for
23866 non-system include paths.
23867 - Stop imposing an arbitrary maximum on the number of file descriptors
23868 used for busy servers. Bug reported by Olaf Selke; patch from
23871 o Minor features (other):
23872 - When SafeLogging is disabled, log addresses along with all TLS
23874 - When building with --enable-gcc-warnings, check for whether Apple's
23875 warning "-Wshorten-64-to-32" is available.
23876 - Add a --passphrase-fd argument to the tor-gencert command for
23879 o Minor bugfixes (memory leaks and code problems):
23880 - We were leaking a file descriptor if Tor started with a zero-length
23881 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
23882 - Detect size overflow in zlib code. Reported by Justin Ferguson and
23884 - We were comparing the raw BridgePassword entry with a base64'ed
23885 version of it, when handling a "/tor/networkstatus-bridges"
23886 directory request. Now compare correctly. Noticed by Veracode.
23887 - Recover from bad tracked-since value in MTBF-history file.
23888 Should fix bug 537.
23889 - Alter the code that tries to recover from unhandled write
23890 errors, to not try to flush onto a socket that's given us
23891 unhandled errors. Bugfix on 0.1.2.x.
23892 - Make Unix controlsockets work correctly on OpenBSD. Patch from
23893 tup. Bugfix on 0.2.0.3-alpha.
23895 o Minor bugfixes (other):
23896 - If we have an extra-info document for our server, always make
23897 it available on the control port, even if we haven't gotten
23898 a copy of it from an authority yet. Patch from mwenge.
23899 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
23900 - Directory mirrors no longer include a guess at the client's IP
23901 address if the connection appears to be coming from the same /24
23902 network; it was producing too many wrong guesses.
23903 - Make the new hidden service code respect the SafeLogging setting.
23904 Bugfix on 0.2.0.x. Patch from Karsten.
23905 - When starting as an authority, do not overwrite all certificates
23906 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
23907 - If we're trying to flush the last bytes on a connection (for
23908 example, when answering a directory request), reset the
23909 time-to-give-up timeout every time we manage to write something
23910 on the socket. Bugfix on 0.1.2.x.
23911 - Change the behavior of "getinfo status/good-server-descriptor"
23912 so it doesn't return failure when any authority disappears.
23913 - Even though the man page said that "TrackHostExits ." should
23914 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
23915 - Report TLS "zero return" case as a "clean close" and "IO error"
23916 as a "close". Stop calling closes "unexpected closes": existing
23917 Tors don't use SSL_close(), so having a connection close without
23918 the TLS shutdown handshake is hardly unexpected.
23919 - Send NAMESERVER_STATUS messages for a single failed nameserver
23922 o Code simplifications and refactoring:
23923 - Remove the tor_strpartition function: its logic was confused,
23924 and it was only used for one thing that could be implemented far
23928 Changes in version 0.2.0.19-alpha - 2008-02-09
23929 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
23930 handshake, makes path selection for relays more secure and IP address
23931 guessing more robust, and generally fixes a lot of bugs in preparation
23932 for calling the 0.2.0 branch stable.
23935 - Do not include recognizeable strings in the commonname part of
23936 Tor's x509 certificates.
23939 - If we're a relay, avoid picking ourselves as an introduction point,
23940 a rendezvous point, or as the final hop for internal circuits. Bug
23941 reported by taranis and lodger. Bugfix on 0.1.2.x.
23942 - Patch from "Andrew S. Lists" to catch when we contact a directory
23943 mirror at IP address X and he says we look like we're coming from
23944 IP address X. Bugfix on 0.1.2.x.
23946 o Minor features (security):
23947 - Be more paranoid about overwriting sensitive memory on free(),
23948 as a defensive programming tactic to ensure forward secrecy.
23950 o Minor features (directory authority):
23951 - Actually validate the options passed to AuthDirReject,
23952 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
23953 - Reject router descriptors with out-of-range bandwidthcapacity or
23954 bandwidthburst values.
23956 o Minor features (controller):
23957 - Reject controller commands over 1MB in length. This keeps rogue
23958 processes from running us out of memory.
23960 o Minor features (misc):
23961 - Give more descriptive well-formedness errors for out-of-range
23962 hidden service descriptor/protocol versions.
23963 - Make memory debugging information describe more about history
23964 of cell allocation, so we can help reduce our memory use.
23966 o Deprecated features (controller):
23967 - The status/version/num-versioning and status/version/num-concurring
23968 GETINFO options are no longer useful in the v3 directory protocol:
23969 treat them as deprecated, and warn when they're used.
23972 - When our consensus networkstatus has been expired for a while, stop
23973 being willing to build circuits using it. Fixes bug 401. Bugfix
23975 - Directory caches now fetch certificates from all authorities
23976 listed in a networkstatus consensus, even when they do not
23977 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
23978 - When connecting to a bridge without specifying its key, insert
23979 the connection into the identity-to-connection map as soon as
23980 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
23981 - Detect versions of OS X where malloc_good_size() is present in the
23982 library but never actually declared. Resolves bug 587. Bugfix
23984 - Stop incorrectly truncating zlib responses to directory authority
23985 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
23986 - Stop recommending that every server operator send mail to tor-ops.
23987 Resolves bug 597. Bugfix on 0.1.2.x.
23988 - Don't trigger an assert if we start a directory authority with a
23989 private IP address (like 127.0.0.1).
23990 - Avoid possible failures when generating a directory with routers
23991 with over-long versions strings, or too many flags set. Bugfix
23993 - If an attempt to launch a DNS resolve request over the control
23994 port fails because we have overrun the limit on the number of
23995 connections, tell the controller that the request has failed.
23996 - Avoid using too little bandwidth when our clock skips a few
23997 seconds. Bugfix on 0.1.2.x.
23998 - Fix shell error when warning about missing packages in configure
23999 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
24000 - Do not become confused when receiving a spurious VERSIONS-like
24001 cell from a confused v1 client. Bugfix on 0.2.0.x.
24002 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
24003 introduction points for a hidden service have failed. Patch from
24004 Karsten Loesing. Bugfix on 0.2.0.x.
24006 o Code simplifications and refactoring:
24007 - Remove some needless generality from cpuworker code, for improved
24009 - Stop overloading the circuit_t.onionskin field for both "onionskin
24010 from a CREATE cell that we are waiting for a cpuworker to be
24011 assigned" and "onionskin from an EXTEND cell that we are going to
24012 send to an OR as soon as we are connected". Might help with bug 600.
24013 - Add an in-place version of aes_crypt() so that we can avoid doing a
24014 needless memcpy() call on each cell payload.
24017 Changes in version 0.2.0.18-alpha - 2008-01-25
24018 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
24019 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
24020 that can warn or reject connections to ports generally associated with
24021 vulnerable-plaintext protocols.
24023 o New directory authorities:
24024 - Set up dannenberg (run by CCC) as the sixth v3 directory
24028 - Fix a major memory leak when attempting to use the v2 TLS
24029 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
24030 - We accidentally enabled the under-development v2 TLS handshake
24031 code, which was causing log entries like "TLS error while
24032 renegotiating handshake". Disable it again. Resolves bug 590.
24033 - We were computing the wrong Content-Length: header for directory
24034 responses that need to be compressed on the fly, causing clients
24035 asking for those items to always fail. Bugfix on 0.2.0.x; partially
24039 - Avoid going directly to the directory authorities even if you're a
24040 relay, if you haven't found yourself reachable yet or if you've
24041 decided not to advertise your dirport yet. Addresses bug 556.
24042 - If we've gone 12 hours since our last bandwidth check, and we
24043 estimate we have less than 50KB bandwidth capacity but we could
24044 handle more, do another bandwidth test.
24045 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
24046 Tor can warn and/or refuse connections to ports commonly used with
24047 vulnerable-plaintext protocols. Currently we warn on ports 23,
24048 109, 110, and 143, but we don't reject any.
24051 - When we setconf ClientOnly to 1, close any current OR and Dir
24052 listeners. Reported by mwenge.
24053 - When we get a consensus that's been signed by more people than
24054 we expect, don't log about it; it's not a big deal. Reported
24058 - Don't answer "/tor/networkstatus-bridges" directory requests if
24059 the request isn't encrypted.
24060 - Make "ClientOnly 1" config option disable directory ports too.
24061 - Patches from Karsten Loesing to make v2 hidden services more
24062 robust: work even when there aren't enough HSDir relays available;
24063 retry when a v2 rend desc fetch fails; but don't retry if we
24064 already have a usable v0 rend desc.
24067 Changes in version 0.2.0.17-alpha - 2008-01-17
24068 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
24071 - Make the tor-gencert man page get included correctly in the tarball.
24074 Changes in version 0.2.0.16-alpha - 2008-01-17
24075 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
24076 Loesing, and generally cleans up a lot of features and minor bugs.
24078 o New directory authorities:
24079 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
24082 o Major performance improvements:
24083 - Switch our old ring buffer implementation for one more like that
24084 used by free Unix kernels. The wasted space in a buffer with 1mb
24085 of data will now be more like 8k than 1mb. The new implementation
24086 also avoids realloc();realloc(); patterns that can contribute to
24087 memory fragmentation.
24090 - Configuration files now accept C-style strings as values. This
24091 helps encode characters not allowed in the current configuration
24092 file format, such as newline or #. Addresses bug 557.
24093 - Although we fixed bug 539 (where servers would send HTTP status 503
24094 responses _and_ send a body too), there are still servers out
24095 there that haven't upgraded. Therefore, make clients parse such
24096 bodies when they receive them.
24097 - When we're not serving v2 directory information, there is no reason
24098 to actually keep any around. Remove the obsolete files and directory
24099 on startup if they are very old and we aren't going to serve them.
24101 o Minor performance improvements:
24102 - Reference-count and share copies of address policy entries; only 5%
24103 of them were actually distinct.
24104 - Never walk through the list of logs if we know that no log is
24105 interested in a given message.
24108 - When an authority has not signed a consensus, do not try to
24109 download a nonexistent "certificate with key 00000000". Bugfix
24110 on 0.2.0.x. Fixes bug 569.
24111 - Fix a rare assert error when we're closing one of our threads:
24112 use a mutex to protect the list of logs, so we never write to the
24113 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
24114 bug 575, which is kind of the revenge of bug 222.
24115 - Patch from Karsten Loesing to complain less at both the client
24116 and the relay when a relay used to have the HSDir flag but doesn't
24117 anymore, and we try to upload a hidden service descriptor.
24118 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
24120 - Do not try to download missing certificates until we have tried
24121 to check our fallback consensus. Fixes bug 583.
24122 - Make bridges round reported GeoIP stats info up to the nearest
24123 estimate, not down. Now we can distinguish between "0 people from
24124 this country" and "1 person from this country".
24125 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
24126 - Avoid possible segfault if key generation fails in
24127 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
24128 - Avoid segfault in the case where a badly behaved v2 versioning
24129 directory sends a signed networkstatus with missing client-versions.
24131 - Avoid segfaults on certain complex invocations of
24132 router_get_by_hexdigest(). Bugfix on 0.1.2.
24133 - Correct bad index on array access in parse_http_time(). Bugfix
24135 - Fix possible bug in vote generation when server versions are present
24136 but client versions are not.
24137 - Fix rare bug on REDIRECTSTREAM control command when called with no
24138 port set: it could erroneously report an error when none had
24140 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
24141 compressing large objects and find ourselves with more than 4k
24142 left over. Bugfix on 0.2.0.
24143 - Fix a small memory leak when setting up a hidden service.
24144 - Fix a few memory leaks that could in theory happen under bizarre
24146 - Fix an assert if we post a general-purpose descriptor via the
24147 control port but that descriptor isn't mentioned in our current
24148 network consensus. Bug reported by Jon McLachlan; bugfix on
24151 o Minor features (controller):
24152 - Get NS events working again. Patch from tup.
24153 - The GETCONF command now escapes and quotes configuration values
24154 that don't otherwise fit into the torrc file.
24155 - The SETCONF command now handles quoted values correctly.
24157 o Minor features (directory authorities):
24158 - New configuration options to override default maximum number of
24159 servers allowed on a single IP address. This is important for
24160 running a test network on a single host.
24161 - Actually implement the -s option to tor-gencert.
24162 - Add a manual page for tor-gencert.
24164 o Minor features (bridges):
24165 - Bridge authorities no longer serve bridge descriptors over
24166 unencrypted connections.
24168 o Minor features (other):
24169 - Add hidden services and DNSPorts to the list of things that make
24170 Tor accept that it has running ports. Change starting Tor with no
24171 ports from a fatal error to a warning; we might change it back if
24172 this turns out to confuse anybody. Fixes bug 579.
24175 Changes in version 0.1.2.19 - 2008-01-17
24176 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
24177 exit policy a little bit more conservative so it's safer to run an
24178 exit relay on a home system, and fixes a variety of smaller issues.
24181 - Exit policies now reject connections that are addressed to a
24182 relay's public (external) IP address too, unless
24183 ExitPolicyRejectPrivate is turned off. We do this because too
24184 many relays are running nearby to services that trust them based
24185 on network address.
24188 - When the clock jumps forward a lot, do not allow the bandwidth
24189 buckets to become negative. Fixes bug 544.
24190 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
24191 on every successful resolve. Reported by Mike Perry.
24192 - Purge old entries from the "rephist" database and the hidden
24193 service descriptor database even when DirPort is zero.
24194 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
24195 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
24196 crashing or mis-answering these requests.
24197 - When we decide to send a 503 response to a request for servers, do
24198 not then also send the server descriptors: this defeats the whole
24199 purpose. Fixes bug 539.
24202 - Changing the ExitPolicyRejectPrivate setting should cause us to
24203 rebuild our server descriptor.
24204 - Fix handling of hex nicknames when answering controller requests for
24205 networkstatus by name, or when deciding whether to warn about
24206 unknown routers in a config option. (Patch from mwenge.)
24207 - Fix a couple of hard-to-trigger autoconf problems that could result
24208 in really weird results on platforms whose sys/types.h files define
24209 nonstandard integer types.
24210 - Don't try to create the datadir when running --verify-config or
24211 --hash-password. Resolves bug 540.
24212 - If we were having problems getting a particular descriptor from the
24213 directory caches, and then we learned about a new descriptor for
24214 that router, we weren't resetting our failure count. Reported
24216 - Although we fixed bug 539 (where servers would send HTTP status 503
24217 responses _and_ send a body too), there are still servers out there
24218 that haven't upgraded. Therefore, make clients parse such bodies
24219 when they receive them.
24220 - Run correctly on systems where rlim_t is larger than unsigned long.
24221 This includes some 64-bit systems.
24222 - Run correctly on platforms (like some versions of OS X 10.5) where
24223 the real limit for number of open files is OPEN_FILES, not rlim_max
24224 from getrlimit(RLIMIT_NOFILES).
24225 - Avoid a spurious free on base64 failure.
24226 - Avoid segfaults on certain complex invocations of
24227 router_get_by_hexdigest().
24228 - Fix rare bug on REDIRECTSTREAM control command when called with no
24229 port set: it could erroneously report an error when none had
24233 Changes in version 0.2.0.15-alpha - 2007-12-25
24234 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
24235 features added in 0.2.0.13-alpha.
24238 - Fix several remotely triggerable asserts based on DirPort requests
24239 for a v2 or v3 networkstatus object before we were prepared. This
24240 was particularly bad for 0.2.0.13 and later bridge relays, who
24241 would never have a v2 networkstatus and would thus always crash
24242 when used. Bugfixes on 0.2.0.x.
24243 - Estimate the v3 networkstatus size more accurately, rather than
24244 estimating it at zero bytes and giving it artificially high priority
24245 compared to other directory requests. Bugfix on 0.2.0.x.
24248 - Fix configure.in logic for cross-compilation.
24249 - When we load a bridge descriptor from the cache, and it was
24250 previously unreachable, mark it as retriable so we won't just
24251 ignore it. Also, try fetching a new copy immediately. Bugfixes
24253 - The bridge GeoIP stats were counting other relays, for example
24254 self-reachability and authority-reachability tests.
24257 - Support compilation to target iPhone; patch from cjacker huang.
24258 To build for iPhone, pass the --enable-iphone option to configure.
24261 Changes in version 0.2.0.14-alpha - 2007-12-23
24263 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
24264 without a datadirectory from a previous Tor install. Reported
24266 - Fix a crash when we fetch a descriptor that turns out to be
24267 unexpected (it used to be in our networkstatus when we started
24268 fetching it, but it isn't in our current networkstatus), and we
24269 aren't using bridges. Bugfix on 0.2.0.x.
24270 - Fix a crash when accessing hidden services: it would work the first
24271 time you use a given introduction point for your service, but
24272 on subsequent requests we'd be using garbage memory. Fixed by
24273 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
24274 - Fix a crash when we load a bridge descriptor from disk but we don't
24275 currently have a Bridge line for it in our torrc. Bugfix on
24279 - If bridge authorities set BridgePassword, they will serve a
24280 snapshot of known bridge routerstatuses from their DirPort to
24281 anybody who knows that password. Unset by default.
24284 - Make the unit tests build again.
24285 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
24286 - Make PublishServerDescriptor default to 1, so the default doesn't
24287 have to change as we invent new directory protocol versions.
24288 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
24289 be included unless sys/time.h is already included. Fixes
24290 bug 553. Bugfix on 0.2.0.x.
24291 - If we receive a general-purpose descriptor and then receive an
24292 identical bridge-purpose descriptor soon after, don't discard
24293 the next one as a duplicate.
24296 - If BridgeRelay is set to 1, then the default for
24297 PublishServerDescriptor is now "bridge" rather than "v2,v3".
24298 - If the user sets RelayBandwidthRate but doesn't set
24299 RelayBandwidthBurst, then make them equal rather than erroring out.
24302 Changes in version 0.2.0.13-alpha - 2007-12-21
24303 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
24304 Goodell, fixes many more bugs, and adds a lot of infrastructure for
24307 o New directory authorities:
24308 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
24312 - Only update guard status (usable / not usable) once we have
24313 enough directory information. This was causing us to always pick
24314 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
24315 causing us to discard all our guards on startup if we hadn't been
24316 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
24317 - Purge old entries from the "rephist" database and the hidden
24318 service descriptor databases even when DirPort is zero. Bugfix
24320 - We were ignoring our RelayBandwidthRate for the first 30 seconds
24321 after opening a circuit -- even a relayed circuit. Bugfix on
24323 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
24324 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
24325 crashing or mis-answering these types of requests.
24326 - Relays were publishing their server descriptor to v1 and v2
24327 directory authorities, but they didn't try publishing to v3-only
24328 authorities. Fix this; and also stop publishing to v1 authorities.
24330 - When we were reading router descriptors from cache, we were ignoring
24331 the annotations -- so for example we were reading in bridge-purpose
24332 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
24333 - When we decided to send a 503 response to a request for servers, we
24334 were then also sending the server descriptors: this defeats the
24335 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
24338 - Bridge relays now behave like clients with respect to time
24339 intervals for downloading new consensus documents -- otherwise they
24340 stand out. Bridge users now wait until the end of the interval,
24341 so their bridge relay will be sure to have a new consensus document.
24342 - Three new config options (AlternateDirAuthority,
24343 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
24344 user selectively replace the default directory authorities by type,
24345 rather than the all-or-nothing replacement that DirServer offers.
24346 - Tor can now be configured to read a GeoIP file from disk in one
24347 of two formats. This can be used by controllers to map IP addresses
24348 to countries. Eventually, it may support exit-by-country.
24349 - When possible, bridge relays remember which countries users
24350 are coming from, and report aggregate information in their
24351 extra-info documents, so that the bridge authorities can learn
24352 where Tor is blocked.
24353 - Bridge directory authorities now do reachability testing on the
24354 bridges they know. They provide router status summaries to the
24355 controller via "getinfo ns/purpose/bridge", and also dump summaries
24356 to a file periodically.
24357 - Stop fetching directory info so aggressively if your DirPort is
24358 on but your ORPort is off; stop fetching v2 dir info entirely.
24359 You can override these choices with the new FetchDirInfoEarly
24363 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
24364 consensus documents when there are too many relays at a single
24365 IP address. Now clear it in v2 network status documents too, and
24366 also clear it in routerinfo_t when the relay is no longer listed
24367 in the relevant networkstatus document.
24368 - Don't crash if we get an unexpected value for the
24369 PublishServerDescriptor config option. Reported by Matt Edman;
24370 bugfix on 0.2.0.9-alpha.
24371 - Our new v2 hidden service descriptor format allows descriptors
24372 that have no introduction points. But Tor crashed when we tried
24373 to build a descriptor with no intro points (and it would have
24374 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
24375 by Karsten Loesing.
24376 - Fix building with dmalloc 5.5.2 with glibc.
24377 - Reject uploaded descriptors and extrainfo documents if they're
24378 huge. Otherwise we'll cache them all over the network and it'll
24379 clog everything up. Reported by Aljosha Judmayer.
24380 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
24381 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
24382 - When the DANGEROUS_VERSION controller status event told us we're
24383 running an obsolete version, it used the string "OLD" to describe
24384 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
24385 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
24386 - If we can't expand our list of entry guards (e.g. because we're
24387 using bridges or we have StrictEntryNodes set), don't mark relays
24388 down when they fail a directory request. Otherwise we're too quick
24389 to mark all our entry points down. Bugfix on 0.1.2.x.
24390 - Fix handling of hex nicknames when answering controller requests for
24391 networkstatus by name, or when deciding whether to warn about unknown
24392 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
24393 - Fix a couple of hard-to-trigger autoconf problems that could result
24394 in really weird results on platforms whose sys/types.h files define
24395 nonstandard integer types. Bugfix on 0.1.2.x.
24396 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
24397 - Don't crash on name lookup when we have no current consensus. Fixes
24398 bug 538; bugfix on 0.2.0.x.
24399 - Only Tors that want to mirror the v2 directory info should
24400 create the "cached-status" directory in their datadir. (All Tors
24401 used to create it.) Bugfix on 0.2.0.9-alpha.
24402 - Directory authorities should only automatically download Extra Info
24403 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
24406 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
24407 consumers. (We already do this on HUP.)
24408 - Authorities and caches fetch the v2 networkstatus documents
24409 less often, now that v3 is encouraged.
24410 - Add a new config option BridgeRelay that specifies you want to
24411 be a bridge relay. Right now the only difference is that it makes
24412 you answer begin_dir requests, and it makes you cache dir info,
24413 even if your DirPort isn't on.
24414 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
24415 ask about source, timestamp of arrival, purpose, etc. We need
24416 something like this to help Vidalia not do GeoIP lookups on bridge
24418 - Allow multiple HashedControlPassword config lines, to support
24419 multiple controller passwords.
24420 - Authorities now decide whether they're authoritative for a given
24421 router based on the router's purpose.
24422 - New config options AuthDirBadDir and AuthDirListBadDirs for
24423 authorities to mark certain relays as "bad directories" in the
24424 networkstatus documents. Also supports the "!baddir" directive in
24425 the approved-routers file.
24428 Changes in version 0.2.0.12-alpha - 2007-11-16
24429 This twelfth development snapshot fixes some more build problems as
24430 well as a few minor bugs.
24433 - Make it build on OpenBSD again. Patch from tup.
24434 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
24435 package-building for Red Hat, OS X, etc.
24437 o Minor bugfixes (on 0.1.2.x):
24438 - Changing the ExitPolicyRejectPrivate setting should cause us to
24439 rebuild our server descriptor.
24441 o Minor bugfixes (on 0.2.0.x):
24442 - When we're lacking a consensus, don't try to perform rendezvous
24443 operations. Reported by Karsten Loesing.
24444 - Fix a small memory leak whenever we decide against using a
24445 newly picked entry guard. Reported by Mike Perry.
24446 - When authorities detected more than two relays running on the same
24447 IP address, they were clearing all the status flags but forgetting
24448 to clear the "hsdir" flag. So clients were being told that a
24449 given relay was the right choice for a v2 hsdir lookup, yet they
24450 never had its descriptor because it was marked as 'not running'
24452 - If we're trying to fetch a bridge descriptor and there's no way
24453 the bridge authority could help us (for example, we don't know
24454 a digest, or there is no bridge authority), don't be so eager to
24455 fall back to asking the bridge authority.
24456 - If we're using bridges or have strictentrynodes set, and our
24457 chosen exit is in the same family as all our bridges/entry guards,
24458 then be flexible about families.
24461 - When we negotiate a v2 link-layer connection (not yet implemented),
24462 accept RELAY_EARLY cells and turn them into RELAY cells if we've
24463 negotiated a v1 connection for their next step. Initial code for
24467 Changes in version 0.2.0.11-alpha - 2007-11-12
24468 This eleventh development snapshot fixes some build problems with
24469 the previous snapshot. It also includes a more secure-by-default exit
24470 policy for relays, fixes an enormous memory leak for exit relays, and
24471 fixes another bug where servers were falling out of the directory list.
24474 - Exit policies now reject connections that are addressed to a
24475 relay's public (external) IP address too, unless
24476 ExitPolicyRejectPrivate is turned off. We do this because too
24477 many relays are running nearby to services that trust them based
24478 on network address. Bugfix on 0.1.2.x.
24481 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
24482 on every successful resolve. Reported by Mike Perry; bugfix
24484 - On authorities, never downgrade to old router descriptors simply
24485 because they're listed in the consensus. This created a catch-22
24486 where we wouldn't list a new descriptor because there was an
24487 old one in the consensus, and we couldn't get the new one in the
24488 consensus because we wouldn't list it. Possible fix for bug 548.
24489 Also, this might cause bug 543 to appear on authorities; if so,
24490 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
24492 o Packaging fixes on 0.2.0.10-alpha:
24493 - We were including instructions about what to do with the
24494 src/config/fallback-consensus file, but we weren't actually
24495 including it in the tarball. Disable all of that for now.
24498 - Allow people to say PreferTunnelledDirConns rather than
24499 PreferTunneledDirConns, for those alternate-spellers out there.
24502 - Don't reevaluate all the information from our consensus document
24503 just because we've downloaded a v2 networkstatus that we intend
24504 to cache. Fixes bug 545; bugfix on 0.2.0.x.
24507 Changes in version 0.2.0.10-alpha - 2007-11-10
24508 This tenth development snapshot adds a third v3 directory authority
24509 run by Mike Perry, adds most of Karsten Loesing's new hidden service
24510 descriptor format, fixes a bad crash bug and new bridge bugs introduced
24511 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
24512 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
24513 addresses many more minor issues.
24515 o New directory authorities:
24516 - Set up ides (run by Mike Perry) as the third v3 directory authority.
24519 - Allow tunnelled directory connections to ask for an encrypted
24520 "begin_dir" connection or an anonymized "uses a full Tor circuit"
24521 connection independently. Now we can make anonymized begin_dir
24522 connections for (e.g.) more secure hidden service posting and
24524 - More progress on proposal 114: code from Karsten Loesing to
24525 implement new hidden service descriptor format.
24526 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
24527 accommodate the growing number of servers that use the default
24528 and are reaching it.
24529 - Directory authorities use a new formula for selecting which nodes
24530 to advertise as Guards: they must be in the top 7/8 in terms of
24531 how long we have known about them, and above the median of those
24532 nodes in terms of weighted fractional uptime.
24533 - Make "not enough dir info yet" warnings describe *why* Tor feels
24534 it doesn't have enough directory info yet.
24537 - Stop servers from crashing if they set a Family option (or
24538 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
24540 - Make bridge users work again -- the move to v3 directories in
24541 0.2.0.9-alpha had introduced a number of bugs that made bridges
24542 no longer work for clients.
24543 - When the clock jumps forward a lot, do not allow the bandwidth
24544 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
24546 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
24547 - When the consensus lists a router descriptor that we previously were
24548 mirroring, but that we considered non-canonical, reload the
24549 descriptor as canonical. This fixes bug 543 where Tor servers
24550 would start complaining after a few days that they don't have
24551 enough directory information to build a circuit.
24552 - Consider replacing the current consensus when certificates arrive
24553 that make the pending consensus valid. Previously, we were only
24554 considering replacement when the new certs _didn't_ help.
24555 - Fix an assert error on startup if we didn't already have the
24556 consensus and certs cached in our datadirectory: we were caching
24557 the consensus in consensus_waiting_for_certs but then free'ing it
24559 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
24560 Request) if we need more v3 certs but we've already got pending
24561 requests for all of them.
24562 - Correctly back off from failing certificate downloads. Fixes
24564 - Authorities don't vote on the Running flag if they have been running
24565 for less than 30 minutes themselves. Fixes bug 547, where a newly
24566 started authority would vote that everyone was down.
24568 o New requirements:
24569 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
24570 it, it had no AES, and it hasn't seen any security patches since
24574 - Clients now hold circuitless TLS connections open for 1.5 times
24575 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
24576 rebuild a new circuit over them within that timeframe. Previously,
24577 they held them open only for KeepalivePeriod (5 minutes).
24578 - Use "If-Modified-Since" to avoid retrieving consensus
24579 networkstatuses that we already have.
24580 - When we have no consensus, check FallbackNetworkstatusFile (defaults
24581 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
24582 we start knowing some directory caches.
24583 - When we receive a consensus from the future, warn about skew.
24584 - Improve skew reporting: try to give the user a better log message
24585 about how skewed they are, and how much this matters.
24586 - When we have a certificate for an authority, believe that
24587 certificate's claims about the authority's IP address.
24588 - New --quiet command-line option to suppress the default console log.
24589 Good in combination with --hash-password.
24590 - Authorities send back an X-Descriptor-Not-New header in response to
24591 an accepted-but-discarded descriptor upload. Partially implements
24593 - Make the log message for "tls error. breaking." more useful.
24594 - Better log messages about certificate downloads, to attempt to
24595 track down the second incarnation of bug 546.
24597 o Minor features (bridges):
24598 - If bridge users set UpdateBridgesFromAuthority, but the digest
24599 they ask for is a 404 from the bridge authority, they now fall
24600 back to trying the bridge directly.
24601 - Bridges now use begin_dir to publish their server descriptor to
24602 the bridge authority, even when they haven't set TunnelDirConns.
24604 o Minor features (controller):
24605 - When reporting clock skew, and we know that the clock is _at least
24606 as skewed_ as some value, but we don't know the actual value,
24607 report the value as a "minimum skew."
24610 - Update linux-tor-prio.sh script to allow QoS based on the uid of
24611 the Tor process. Patch from Marco Bonetti with tweaks from Mike
24615 - Refuse to start if both ORPort and UseBridges are set. Bugfix
24616 on 0.2.0.x, suggested by Matt Edman.
24617 - Don't stop fetching descriptors when FetchUselessDescriptors is
24618 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
24619 reported by tup and ioerror.
24620 - Better log message on vote from unknown authority.
24621 - Don't log "Launching 0 request for 0 router" message.
24623 o Minor bugfixes (memory leaks):
24624 - Stop leaking memory every time we parse a v3 certificate. Bugfix
24626 - Stop leaking memory every time we load a v3 certificate. Bugfix
24627 on 0.2.0.1-alpha. Fixes bug 536.
24628 - Stop leaking a cached networkstatus on exit. Bugfix on
24630 - Stop leaking voter information every time we free a consensus.
24631 Bugfix on 0.2.0.3-alpha.
24632 - Stop leaking signed data every time we check a voter signature.
24633 Bugfix on 0.2.0.3-alpha.
24634 - Stop leaking a signature every time we fail to parse a consensus or
24635 a vote. Bugfix on 0.2.0.3-alpha.
24636 - Stop leaking v2_download_status_map on shutdown. Bugfix on
24638 - Stop leaking conn->nickname every time we make a connection to a
24639 Tor relay without knowing its expected identity digest (e.g. when
24640 using bridges). Bugfix on 0.2.0.3-alpha.
24642 - Minor bugfixes (portability):
24643 - Run correctly on platforms where rlim_t is larger than unsigned
24644 long, and/or where the real limit for number of open files is
24645 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
24646 particular, these may be needed for OS X 10.5.
24649 Changes in version 0.1.2.18 - 2007-10-28
24650 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
24651 hidden service introduction that were causing huge delays, and a big
24652 bug that was causing some servers to disappear from the network status
24653 lists for a few hours each day.
24655 o Major bugfixes (crashes):
24656 - If a connection is shut down abruptly because of something that
24657 happened inside connection_flushed_some(), do not call
24658 connection_finished_flushing(). Should fix bug 451:
24659 "connection_stop_writing: Assertion conn->write_event failed"
24660 Bugfix on 0.1.2.7-alpha.
24661 - Fix possible segfaults in functions called from
24662 rend_process_relay_cell().
24664 o Major bugfixes (hidden services):
24665 - Hidden services were choosing introduction points uniquely by
24666 hexdigest, but when constructing the hidden service descriptor
24667 they merely wrote the (potentially ambiguous) nickname.
24668 - Clients now use the v2 intro format for hidden service
24669 connections: they specify their chosen rendezvous point by identity
24670 digest rather than by (potentially ambiguous) nickname. These
24671 changes could speed up hidden service connections dramatically.
24673 o Major bugfixes (other):
24674 - Stop publishing a new server descriptor just because we get a
24675 HUP signal. This led (in a roundabout way) to some servers getting
24676 dropped from the networkstatus lists for a few hours each day.
24677 - When looking for a circuit to cannibalize, consider family as well
24678 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
24679 circuit cannibalization).
24680 - When a router wasn't listed in a new networkstatus, we were leaving
24681 the flags for that router alone -- meaning it remained Named,
24682 Running, etc -- even though absence from the networkstatus means
24683 that it shouldn't be considered to exist at all anymore. Now we
24684 clear all the flags for routers that fall out of the networkstatus
24685 consensus. Fixes bug 529.
24688 - Don't try to access (or alter) the state file when running
24689 --list-fingerprint or --verify-config or --hash-password. Resolves
24691 - When generating information telling us how to extend to a given
24692 router, do not try to include the nickname if it is
24693 absent. Resolves bug 467.
24694 - Fix a user-triggerable segfault in expand_filename(). (There isn't
24695 a way to trigger this remotely.)
24696 - When sending a status event to the controller telling it that an
24697 OR address is reachable, set the port correctly. (Previously we
24698 were reporting the dir port.)
24699 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
24700 command. Bugfix on 0.1.2.17.
24701 - When loading bandwidth history, do not believe any information in
24702 the future. Fixes bug 434.
24703 - When loading entry guard information, do not believe any information
24705 - When we have our clock set far in the future and generate an
24706 onion key, then re-set our clock to be correct, we should not stop
24707 the onion key from getting rotated.
24708 - On some platforms, accept() can return a broken address. Detect
24709 this more quietly, and deal accordingly. Fixes bug 483.
24710 - It's not actually an error to find a non-pending entry in the DNS
24711 cache when canceling a pending resolve. Don't log unless stuff
24712 is fishy. Resolves bug 463.
24713 - Don't reset trusted dir server list when we set a configuration
24714 option. Patch from Robert Hogan.
24715 - Don't try to create the datadir when running --verify-config or
24716 --hash-password. Resolves bug 540.
24719 Changes in version 0.2.0.9-alpha - 2007-10-24
24720 This ninth development snapshot switches clients to the new v3 directory
24721 system; allows servers to be listed in the network status even when they
24722 have the same nickname as a registered server; and fixes many other
24723 bugs including a big one that was causing some servers to disappear
24724 from the network status lists for a few hours each day.
24726 o Major features (directory system):
24727 - Clients now download v3 consensus networkstatus documents instead
24728 of v2 networkstatus documents. Clients and caches now base their
24729 opinions about routers on these consensus documents. Clients only
24730 download router descriptors listed in the consensus.
24731 - Authorities now list servers who have the same nickname as
24732 a different named server, but list them with a new flag,
24733 "Unnamed". Now we can list servers that happen to pick the same
24734 nickname as a server that registered two years ago and then
24735 disappeared. Partially implements proposal 122.
24736 - If the consensus lists a router as "Unnamed", the name is assigned
24737 to a different router: do not identify the router by that name.
24738 Partially implements proposal 122.
24739 - Authorities can now come to a consensus on which method to use to
24740 compute the consensus. This gives us forward compatibility.
24743 - Stop publishing a new server descriptor just because we HUP or
24744 when we find our DirPort to be reachable but won't actually publish
24745 it. New descriptors without any real changes are dropped by the
24746 authorities, and can screw up our "publish every 18 hours" schedule.
24748 - When a router wasn't listed in a new networkstatus, we were leaving
24749 the flags for that router alone -- meaning it remained Named,
24750 Running, etc -- even though absence from the networkstatus means
24751 that it shouldn't be considered to exist at all anymore. Now we
24752 clear all the flags for routers that fall out of the networkstatus
24753 consensus. Fixes bug 529; bugfix on 0.1.2.x.
24754 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
24755 extrainfo documents and then discard them immediately for not
24756 matching the latest router. Bugfix on 0.2.0.1-alpha.
24758 o Minor features (v3 directory protocol):
24759 - Allow tor-gencert to generate a new certificate without replacing
24761 - Allow certificates to include an address.
24762 - When we change our directory-cache settings, reschedule all voting
24763 and download operations.
24764 - Reattempt certificate downloads immediately on failure, as long as
24765 we haven't failed a threshold number of times yet.
24766 - Delay retrying consensus downloads while we're downloading
24767 certificates to verify the one we just got. Also, count getting a
24768 consensus that we already have (or one that isn't valid) as a failure,
24769 and count failing to get the certificates after 20 minutes as a
24771 - Build circuits and download descriptors even if our consensus is a
24772 little expired. (This feature will go away once authorities are
24775 o Minor features (router descriptor cache):
24776 - If we find a cached-routers file that's been sitting around for more
24777 than 28 days unmodified, then most likely it's a leftover from
24778 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
24780 - When we (as a cache) download a descriptor because it was listed
24781 in a consensus, remember when the consensus was supposed to expire,
24782 and don't expire the descriptor until then.
24784 o Minor features (performance):
24785 - Call routerlist_remove_old_routers() much less often. This should
24786 speed startup, especially on directory caches.
24787 - Don't try to launch new descriptor downloads quite so often when we
24788 already have enough directory information to build circuits.
24789 - Base64 decoding was actually showing up on our profile when parsing
24790 the initial descriptor file; switch to an in-process all-at-once
24791 implementation that's about 3.5x times faster than calling out to
24794 o Minor features (compilation):
24795 - Detect non-ASCII platforms (if any still exist) and refuse to
24796 build there: some of our code assumes that 'A' is 65 and so on.
24798 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
24799 - Make the "next period" votes into "current period" votes immediately
24800 after publishing the consensus; avoid a heisenbug that made them
24801 stick around indefinitely.
24802 - When we discard a vote as a duplicate, do not report this as
24804 - Treat missing v3 keys or certificates as an error when running as a
24805 v3 directory authority.
24806 - When we're configured to be a v3 authority, but we're only listed
24807 as a non-v3 authority in our DirServer line for ourself, correct
24809 - If an authority doesn't have a qualified hostname, just put
24810 its address in the vote. This fixes the problem where we referred to
24811 "moria on moria:9031."
24812 - Distinguish between detached signatures for the wrong period, and
24813 detached signatures for a divergent vote.
24814 - Fix a small memory leak when computing a consensus.
24815 - When there's no consensus, we were forming a vote every 30
24816 minutes, but writing the "valid-after" line in our vote based
24817 on our configured V3AuthVotingInterval: so unless the intervals
24818 matched up, we immediately rejected our own vote because it didn't
24819 start at the voting interval that caused us to construct a vote.
24821 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
24822 - Delete unverified-consensus when the real consensus is set.
24823 - Consider retrying a consensus networkstatus fetch immediately
24824 after one fails: don't wait 60 seconds to notice.
24825 - When fetching a consensus as a cache, wait until a newer consensus
24826 should exist before trying to replace the current one.
24827 - Use a more forgiving schedule for retrying failed consensus
24828 downloads than for other types.
24830 o Minor bugfixes (other directory issues):
24831 - Correct the implementation of "download votes by digest." Bugfix on
24833 - Authorities no longer send back "400 you're unreachable please fix
24834 it" errors to Tor servers that aren't online all the time. We're
24835 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
24837 o Minor bugfixes (controller):
24838 - Don't reset trusted dir server list when we set a configuration
24839 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
24840 - Respond to INT and TERM SIGNAL commands before we execute the
24841 signal, in case the signal shuts us down. We had a patch in
24842 0.1.2.1-alpha that tried to do this by queueing the response on
24843 the connection's buffer before shutting down, but that really
24844 isn't the same thing at all. Bug located by Matt Edman.
24846 o Minor bugfixes (misc):
24847 - Correctly check for bad options to the "PublishServerDescriptor"
24848 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
24849 - Stop leaking memory on failing case of base32_decode, and make
24850 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
24851 - Don't try to download extrainfo documents when we're trying to
24852 fetch enough directory info to build a circuit: having enough
24853 info should get priority. Bugfix on 0.2.0.x.
24854 - Don't complain that "your server has not managed to confirm that its
24855 ports are reachable" if we haven't been able to build any circuits
24856 yet. Bug found by spending four hours without a v3 consensus. Bugfix
24858 - Detect the reason for failing to mmap a descriptor file we just
24859 wrote, and give a more useful log message. Fixes bug 533. Bugfix
24862 o Code simplifications and refactoring:
24863 - Remove support for the old bw_accounting file: we've been storing
24864 bandwidth accounting information in the state file since
24865 0.1.2.5-alpha. This may result in bandwidth accounting errors
24866 if you try to upgrade from 0.1.1.x or earlier, or if you try to
24867 downgrade to 0.1.1.x or earlier.
24868 - New convenience code to locate a file within the DataDirectory.
24869 - Move non-authority functionality out of dirvote.c.
24870 - Refactor the arguments for router_pick_{directory_|trusteddir}server
24871 so that they all take the same named flags.
24874 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
24875 Unix users an easy way to script their Tor process (e.g. by
24876 adjusting bandwidth based on the time of the day).
24879 Changes in version 0.2.0.8-alpha - 2007-10-12
24880 This eighth development snapshot fixes a crash bug that's been bothering
24881 us since February 2007, lets bridge authorities store a list of bridge
24882 descriptors they've seen, gets v3 directory voting closer to working,
24883 starts caching v3 directory consensus documents on directory mirrors,
24884 and fixes a variety of smaller issues including some minor memory leaks.
24886 o Major features (router descriptor cache):
24887 - Store routers in a file called cached-descriptors instead of in
24888 cached-routers. Initialize cached-descriptors from cached-routers
24889 if the old format is around. The new format allows us to store
24890 annotations along with descriptors.
24891 - Use annotations to record the time we received each descriptor, its
24892 source, and its purpose.
24893 - Disable the SETROUTERPURPOSE controller command: it is now
24895 - Controllers should now specify cache=no or cache=yes when using
24896 the +POSTDESCRIPTOR command.
24897 - Bridge authorities now write bridge descriptors to disk, meaning
24898 we can export them to other programs and begin distributing them
24901 o Major features (directory authorities):
24902 - When a v3 authority is missing votes or signatures, it now tries
24904 - Directory authorities track weighted fractional uptime as well as
24905 weighted mean-time-between failures. WFU is suitable for deciding
24906 whether a node is "usually up", while MTBF is suitable for deciding
24907 whether a node is "likely to stay up." We need both, because
24908 "usually up" is a good requirement for guards, while "likely to
24909 stay up" is a good requirement for long-lived connections.
24911 o Major features (v3 directory system):
24912 - Caches now download v3 network status documents as needed,
24913 and download the descriptors listed in them.
24914 - All hosts now attempt to download and keep fresh v3 authority
24915 certificates, and re-attempt after failures.
24916 - More internal-consistency checks for vote parsing.
24918 o Major bugfixes (crashes):
24919 - If a connection is shut down abruptly because of something that
24920 happened inside connection_flushed_some(), do not call
24921 connection_finished_flushing(). Should fix bug 451. Bugfix on
24924 o Major bugfixes (performance):
24925 - Fix really bad O(n^2) performance when parsing a long list of
24926 routers: Instead of searching the entire list for an "extra-info "
24927 string which usually wasn't there, once for every routerinfo
24928 we read, just scan lines forward until we find one we like.
24930 - When we add data to a write buffer in response to the data on that
24931 write buffer getting low because of a flush, do not consider the
24932 newly added data as a candidate for immediate flushing, but rather
24933 make it wait until the next round of writing. Otherwise, we flush
24934 and refill recursively, and a single greedy TLS connection can
24935 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
24937 o Minor features (v3 authority system):
24938 - Add more ways for tools to download the votes that lead to the
24940 - Send a 503 when low on bandwidth and a vote, consensus, or
24941 certificate is requested.
24942 - If-modified-since is now implemented properly for all kinds of
24943 certificate requests.
24945 o Minor bugfixes (network statuses):
24946 - Tweak the implementation of proposal 109 slightly: allow at most
24947 two Tor servers on the same IP address, except if it's the location
24948 of a directory authority, in which case allow five. Bugfix on
24951 o Minor bugfixes (controller):
24952 - When sending a status event to the controller telling it that an
24953 OR address is reachable, set the port correctly. (Previously we
24954 were reporting the dir port.) Bugfix on 0.1.2.x.
24956 o Minor bugfixes (v3 directory system):
24957 - Fix logic to look up a cert by its signing key digest. Bugfix on
24959 - Only change the reply to a vote to "OK" if it's not already
24960 set. This gets rid of annoying "400 OK" log messages, which may
24961 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
24962 - When we get a valid consensus, recompute the voting schedule.
24963 - Base the valid-after time of a vote on the consensus voting
24964 schedule, not on our preferred schedule.
24965 - Make the return values and messages from signature uploads and
24966 downloads more sensible.
24967 - Fix a memory leak when serving votes and consensus documents, and
24968 another when serving certificates.
24970 o Minor bugfixes (performance):
24971 - Use a slightly simpler string hashing algorithm (copying Python's
24972 instead of Java's) and optimize our digest hashing algorithm to take
24973 advantage of 64-bit platforms and to remove some possibly-costly
24975 - Fix a minor memory leak whenever we parse guards from our state
24976 file. Bugfix on 0.2.0.7-alpha.
24977 - Fix a minor memory leak whenever we write out a file. Bugfix on
24979 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
24980 command. Bugfix on 0.2.0.5-alpha.
24982 o Minor bugfixes (portability):
24983 - On some platforms, accept() can return a broken address. Detect
24984 this more quietly, and deal accordingly. Fixes bug 483.
24985 - Stop calling tor_strlower() on uninitialized memory in some cases.
24986 Bugfix in 0.2.0.7-alpha.
24988 o Minor bugfixes (usability):
24989 - Treat some 403 responses from directory servers as INFO rather than
24990 WARN-severity events.
24991 - It's not actually an error to find a non-pending entry in the DNS
24992 cache when canceling a pending resolve. Don't log unless stuff is
24993 fishy. Resolves bug 463.
24995 o Minor bugfixes (anonymity):
24996 - Never report that we've used more bandwidth than we're willing to
24997 relay: it leaks how much non-relay traffic we're using. Resolves
24999 - When looking for a circuit to cannibalize, consider family as well
25000 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
25001 circuit cannibalization).
25003 o Code simplifications and refactoring:
25004 - Make a bunch of functions static. Remove some dead code.
25005 - Pull out about a third of the really big routerlist.c; put it in a
25006 new module, networkstatus.c.
25007 - Merge the extra fields in local_routerstatus_t back into
25008 routerstatus_t: we used to need one routerstatus_t for each
25009 authority's opinion, plus a local_routerstatus_t for the locally
25010 computed consensus opinion. To save space, we put the locally
25011 modified fields into local_routerstatus_t, and only the common
25012 stuff into routerstatus_t. But once v3 directories are in use,
25013 clients and caches will no longer need to hold authority opinions;
25014 thus, the rationale for keeping the types separate is now gone.
25015 - Make the code used to reschedule and reattempt downloads more
25017 - Turn all 'Are we a directory server/mirror?' logic into a call to
25019 - Remove the code to generate the oldest (v1) directory format.
25020 The code has been disabled since 0.2.0.5-alpha.
25023 Changes in version 0.2.0.7-alpha - 2007-09-21
25024 This seventh development snapshot makes bridges work again, makes bridge
25025 authorities work for the first time, fixes two huge performance flaws
25026 in hidden services, and fixes a variety of minor issues.
25028 o New directory authorities:
25029 - Set up moria1 and tor26 as the first v3 directory authorities. See
25030 doc/spec/dir-spec.txt for details on the new directory design.
25032 o Major bugfixes (crashes):
25033 - Fix possible segfaults in functions called from
25034 rend_process_relay_cell(). Bugfix on 0.1.2.x.
25036 o Major bugfixes (bridges):
25037 - Fix a bug that made servers send a "404 Not found" in response to
25038 attempts to fetch their server descriptor. This caused Tor servers
25039 to take many minutes to establish reachability for their DirPort,
25040 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
25041 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
25042 users configure that and specify a bridge with an identity
25043 fingerprint, now they will lookup the bridge descriptor at the
25044 default bridge authority via a one-hop tunnel, but once circuits
25045 are established they will switch to a three-hop tunnel for later
25046 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
25048 o Major bugfixes (hidden services):
25049 - Hidden services were choosing introduction points uniquely by
25050 hexdigest, but when constructing the hidden service descriptor
25051 they merely wrote the (potentially ambiguous) nickname.
25052 - Clients now use the v2 intro format for hidden service
25053 connections: they specify their chosen rendezvous point by identity
25054 digest rather than by (potentially ambiguous) nickname. Both
25055 are bugfixes on 0.1.2.x, and they could speed up hidden service
25056 connections dramatically. Thanks to Karsten Loesing.
25058 o Minor features (security):
25059 - As a client, do not believe any server that tells us that an
25060 address maps to an internal address space.
25061 - Make it possible to enable HashedControlPassword and
25062 CookieAuthentication at the same time.
25064 o Minor features (guard nodes):
25065 - Tag every guard node in our state file with the version that
25066 we believe added it, or with our own version if we add it. This way,
25067 if a user temporarily runs an old version of Tor and then switches
25068 back to a new one, she doesn't automatically lose her guards.
25070 o Minor features (speed):
25071 - When implementing AES counter mode, update only the portions of the
25072 counter buffer that need to change, and don't keep separate
25073 network-order and host-order counters when they are the same (i.e.,
25074 on big-endian hosts.)
25076 o Minor features (controller):
25077 - Accept LF instead of CRLF on controller, since some software has a
25078 hard time generating real Internet newlines.
25079 - Add GETINFO values for the server status events
25080 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
25083 o Removed features:
25084 - Routers no longer include bandwidth-history lines in their
25085 descriptors; this information is already available in extra-info
25086 documents, and including it in router descriptors took up 60%
25087 (!) of compressed router descriptor downloads. Completes
25088 implementation of proposal 104.
25089 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
25090 and TorControl.py, as they use the old v0 controller protocol,
25091 and are obsoleted by TorFlow anyway.
25092 - Drop support for v1 rendezvous descriptors, since we never used
25093 them anyway, and the code has probably rotted by now. Based on
25094 patch from Karsten Loesing.
25095 - On OSX, stop warning the user that kqueue support in libevent is
25096 "experimental", since it seems to have worked fine for ages.
25099 - When generating information telling us how to extend to a given
25100 router, do not try to include the nickname if it is absent. Fixes
25101 bug 467. Bugfix on 0.2.0.3-alpha.
25102 - Fix a user-triggerable (but not remotely-triggerable) segfault
25103 in expand_filename(). Bugfix on 0.1.2.x.
25104 - Fix a memory leak when freeing incomplete requests from DNSPort.
25105 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
25106 - Don't try to access (or alter) the state file when running
25107 --list-fingerprint or --verify-config or --hash-password. (Resolves
25108 bug 499.) Bugfix on 0.1.2.x.
25109 - Servers used to decline to publish their DirPort if their
25110 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
25111 were below a threshold. Now they only look at BandwidthRate and
25112 RelayBandwidthRate. Bugfix on 0.1.2.x.
25113 - Remove an optimization in the AES counter-mode code that assumed
25114 that the counter never exceeded 2^68. When the counter can be set
25115 arbitrarily as an IV (as it is by Karsten's new hidden services
25116 code), this assumption no longer holds. Bugfix on 0.1.2.x.
25117 - Resume listing "AUTHORITY" flag for authorities in network status.
25118 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
25120 o Code simplifications and refactoring:
25121 - Revamp file-writing logic so we don't need to have the entire
25122 contents of a file in memory at once before we write to disk. Tor,
25124 - Turn "descriptor store" into a full-fledged type.
25125 - Move all NT services code into a separate source file.
25126 - Unify all code that computes medians, percentile elements, etc.
25127 - Get rid of a needless malloc when parsing address policies.
25130 Changes in version 0.1.2.17 - 2007-08-30
25131 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
25132 X bundles. Vidalia 0.0.14 makes authentication required for the
25133 ControlPort in the default configuration, which addresses important
25134 security risks. Everybody who uses Vidalia (or another controller)
25137 In addition, this Tor update fixes major load balancing problems with
25138 path selection, which should speed things up a lot once many people
25141 o Major bugfixes (security):
25142 - We removed support for the old (v0) control protocol. It has been
25143 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
25144 become more of a headache than it's worth.
25146 o Major bugfixes (load balancing):
25147 - When choosing nodes for non-guard positions, weight guards
25148 proportionally less, since they already have enough load. Patch
25150 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
25151 will allow fast Tor servers to get more attention.
25152 - When we're upgrading from an old Tor version, forget our current
25153 guards and pick new ones according to the new weightings. These
25154 three load balancing patches could raise effective network capacity
25155 by a factor of four. Thanks to Mike Perry for measurements.
25157 o Major bugfixes (stream expiration):
25158 - Expire not-yet-successful application streams in all cases if
25159 they've been around longer than SocksTimeout. Right now there are
25160 some cases where the stream will live forever, demanding a new
25161 circuit every 15 seconds. Fixes bug 454; reported by lodger.
25163 o Minor features (controller):
25164 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
25165 is valid before any authentication has been received. It tells
25166 a controller what kind of authentication is expected, and what
25167 protocol is spoken. Implements proposal 119.
25169 o Minor bugfixes (performance):
25170 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
25171 greatly speeding up loading cached-routers from disk on startup.
25172 - Disable sentinel-based debugging for buffer code: we squashed all
25173 the bugs that this was supposed to detect a long time ago, and now
25174 its only effect is to change our buffer sizes from nice powers of
25175 two (which platform mallocs tend to like) to values slightly over
25176 powers of two (which make some platform mallocs sad).
25178 o Minor bugfixes (misc):
25179 - If exit bandwidth ever exceeds one third of total bandwidth, then
25180 use the correct formula to weight exit nodes when choosing paths.
25181 Based on patch from Mike Perry.
25182 - Choose perfectly fairly among routers when choosing by bandwidth and
25183 weighting by fraction of bandwidth provided by exits. Previously, we
25184 would choose with only approximate fairness, and correct ourselves
25185 if we ran off the end of the list.
25186 - If we require CookieAuthentication but we fail to write the
25187 cookie file, we would warn but not exit, and end up in a state
25188 where no controller could authenticate. Now we exit.
25189 - If we require CookieAuthentication, stop generating a new cookie
25190 every time we change any piece of our config.
25191 - Refuse to start with certain directory authority keys, and
25192 encourage people using them to stop.
25193 - Terminate multi-line control events properly. Original patch
25195 - Fix a minor memory leak when we fail to find enough suitable
25196 servers to choose a circuit.
25197 - Stop leaking part of the descriptor when we run into a particularly
25198 unparseable piece of it.
25201 Changes in version 0.2.0.6-alpha - 2007-08-26
25202 This sixth development snapshot features a new Vidalia version in the
25203 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
25204 the ControlPort in the default configuration, which addresses important
25207 In addition, this snapshot fixes major load balancing problems
25208 with path selection, which should speed things up a lot once many
25209 people have upgraded. The directory authorities also use a new
25210 mean-time-between-failure approach to tracking which servers are stable,
25211 rather than just looking at the most recent uptime.
25213 o New directory authorities:
25214 - Set up Tonga as the default bridge directory authority.
25217 - Directory authorities now track servers by weighted
25218 mean-times-between-failures. When we have 4 or more days of data,
25219 use measured MTBF rather than declared uptime to decide whether
25220 to call a router Stable. Implements proposal 108.
25222 o Major bugfixes (load balancing):
25223 - When choosing nodes for non-guard positions, weight guards
25224 proportionally less, since they already have enough load. Patch
25226 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
25227 will allow fast Tor servers to get more attention.
25228 - When we're upgrading from an old Tor version, forget our current
25229 guards and pick new ones according to the new weightings. These
25230 three load balancing patches could raise effective network capacity
25231 by a factor of four. Thanks to Mike Perry for measurements.
25233 o Major bugfixes (descriptor parsing):
25234 - Handle unexpected whitespace better in malformed descriptors. Bug
25235 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
25238 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
25239 GETINFO for Torstat to use until it can switch to using extrainfos.
25240 - Optionally (if built with -DEXPORTMALLINFO) export the output
25241 of mallinfo via http, as tor/mallinfo.txt. Only accessible
25245 - Do not intermix bridge routers with controller-added
25246 routers. (Bugfix on 0.2.0.x)
25247 - Do not fail with an assert when accept() returns an unexpected
25248 address family. Addresses but does not wholly fix bug 483. (Bugfix
25250 - Let directory authorities startup even when they can't generate
25251 a descriptor immediately, e.g. because they don't know their
25253 - Stop putting the authentication cookie in a file called "0"
25254 in your working directory if you don't specify anything for the
25255 new CookieAuthFile option. Reported by Matt Edman.
25256 - Make it possible to read the PROTOCOLINFO response in a way that
25257 conforms to our control-spec. Reported by Matt Edman.
25258 - Fix a minor memory leak when we fail to find enough suitable
25259 servers to choose a circuit. Bugfix on 0.1.2.x.
25260 - Stop leaking part of the descriptor when we run into a particularly
25261 unparseable piece of it. Bugfix on 0.1.2.x.
25262 - Unmap the extrainfo cache file on exit.
25265 Changes in version 0.2.0.5-alpha - 2007-08-19
25266 This fifth development snapshot fixes compilation on Windows again;
25267 fixes an obnoxious client-side bug that slowed things down and put
25268 extra load on the network; gets us closer to using the v3 directory
25269 voting scheme; makes it easier for Tor controllers to use cookie-based
25270 authentication; and fixes a variety of other bugs.
25272 o Removed features:
25273 - Version 1 directories are no longer generated in full. Instead,
25274 authorities generate and serve "stub" v1 directories that list
25275 no servers. This will stop Tor versions 0.1.0.x and earlier from
25276 working, but (for security reasons) nobody should be running those
25279 o Major bugfixes (compilation, 0.2.0.x):
25280 - Try to fix Win32 compilation again: improve checking for IPv6 types.
25281 - Try to fix MSVC compilation: build correctly on platforms that do
25282 not define s6_addr16 or s6_addr32.
25283 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
25286 o Major bugfixes (stream expiration):
25287 - Expire not-yet-successful application streams in all cases if
25288 they've been around longer than SocksTimeout. Right now there are
25289 some cases where the stream will live forever, demanding a new
25290 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
25291 reported by lodger.
25293 o Minor features (directory servers):
25294 - When somebody requests a list of statuses or servers, and we have
25295 none of those, return a 404 rather than an empty 200.
25297 o Minor features (directory voting):
25298 - Store v3 consensus status consensuses on disk, and reload them
25301 o Minor features (security):
25302 - Warn about unsafe ControlPort configurations.
25303 - Refuse to start with certain directory authority keys, and
25304 encourage people using them to stop.
25306 o Minor features (controller):
25307 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
25308 is valid before any authentication has been received. It tells
25309 a controller what kind of authentication is expected, and what
25310 protocol is spoken. Implements proposal 119.
25311 - New config option CookieAuthFile to choose a new location for the
25312 cookie authentication file, and config option
25313 CookieAuthFileGroupReadable to make it group-readable.
25315 o Minor features (unit testing):
25316 - Add command-line arguments to unit-test executable so that we can
25317 invoke any chosen test from the command line rather than having
25318 to run the whole test suite at once; and so that we can turn on
25319 logging for the unit tests.
25321 o Minor bugfixes (on 0.1.2.x):
25322 - If we require CookieAuthentication but we fail to write the
25323 cookie file, we would warn but not exit, and end up in a state
25324 where no controller could authenticate. Now we exit.
25325 - If we require CookieAuthentication, stop generating a new cookie
25326 every time we change any piece of our config.
25327 - When loading bandwidth history, do not believe any information in
25328 the future. Fixes bug 434.
25329 - When loading entry guard information, do not believe any information
25331 - When we have our clock set far in the future and generate an
25332 onion key, then re-set our clock to be correct, we should not stop
25333 the onion key from getting rotated.
25334 - Clean up torrc sample config file.
25335 - Do not automatically run configure from autogen.sh. This
25336 non-standard behavior tended to annoy people who have built other
25339 o Minor bugfixes (on 0.2.0.x):
25340 - Fix a bug with AutomapHostsOnResolve that would always cause
25341 the second request to fail. Bug reported by Kate. Bugfix on
25343 - Fix a bug in ADDRMAP controller replies that would sometimes
25344 try to print a NULL. Patch from tup.
25345 - Read v3 directory authority keys from the right location.
25346 - Numerous bugfixes to directory voting code.
25349 Changes in version 0.1.2.16 - 2007-08-01
25350 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
25351 remote attacker in certain situations to rewrite the user's torrc
25352 configuration file. This can completely compromise anonymity of users
25353 in most configurations, including those running the Vidalia bundles,
25354 TorK, etc. Or worse.
25356 o Major security fixes:
25357 - Close immediately after missing authentication on control port;
25358 do not allow multiple authentication attempts.
25361 Changes in version 0.2.0.4-alpha - 2007-08-01
25362 This fourth development snapshot fixes a critical security vulnerability
25363 for most users, specifically those running Vidalia, TorK, etc. Everybody
25364 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
25366 o Major security fixes:
25367 - Close immediately after missing authentication on control port;
25368 do not allow multiple authentication attempts.
25370 o Major bugfixes (compilation):
25371 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
25374 o Minor features (performance):
25375 - Be even more aggressive about releasing RAM from small
25376 empty buffers. Thanks to our free-list code, this shouldn't be too
25377 performance-intensive.
25378 - Disable sentinel-based debugging for buffer code: we squashed all
25379 the bugs that this was supposed to detect a long time ago, and
25380 now its only effect is to change our buffer sizes from nice
25381 powers of two (which platform mallocs tend to like) to values
25382 slightly over powers of two (which make some platform mallocs sad).
25383 - Log malloc statistics from mallinfo() on platforms where it
25387 Changes in version 0.2.0.3-alpha - 2007-07-29
25388 This third development snapshot introduces new experimental
25389 blocking-resistance features and a preliminary version of the v3
25390 directory voting design, and includes many other smaller features
25394 - The first pieces of our "bridge" design for blocking-resistance
25395 are implemented. People can run bridge directory authorities;
25396 people can run bridges; and people can configure their Tor clients
25397 with a set of bridges to use as the first hop into the Tor network.
25398 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
25400 - Create listener connections before we setuid to the configured
25401 User and Group. Now non-Windows users can choose port values
25402 under 1024, start Tor as root, and have Tor bind those ports
25403 before it changes to another UID. (Windows users could already
25405 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
25406 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
25407 on "vserver" accounts. (Patch from coderman.)
25408 - Be even more aggressive about separating local traffic from relayed
25409 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
25411 o Major features (experimental):
25412 - First cut of code for "v3 dir voting": directory authorities will
25413 vote on a common network status document rather than each publishing
25414 their own opinion. This code needs more testing and more corner-case
25415 handling before it's ready for use.
25418 - Directory authorities now call routers Fast if their bandwidth is
25419 at least 100KB/s, and consider their bandwidth adequate to be a
25420 Guard if it is at least 250KB/s, no matter the medians. This fix
25421 complements proposal 107. [Bugfix on 0.1.2.x]
25422 - Directory authorities now never mark more than 3 servers per IP as
25423 Valid and Running. (Implements proposal 109, by Kevin Bauer and
25425 - Minor change to organizationName and commonName generation
25426 procedures in TLS certificates during Tor handshakes, to invalidate
25427 some earlier censorware approaches. This is not a long-term
25428 solution, but applying it will give us a bit of time to look into
25429 the epidemiology of countermeasures as they spread.
25431 o Major bugfixes (directory):
25432 - Rewrite directory tokenization code to never run off the end of
25433 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
25435 o Minor features (controller):
25436 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
25437 match requests to applications. (Patch from Robert Hogan.)
25438 - Report address and port correctly on connections to DNSPort. (Patch
25439 from Robert Hogan.)
25440 - Add a RESOLVE command to launch hostname lookups. (Original patch
25441 from Robert Hogan.)
25442 - Add GETINFO status/enough-dir-info to let controllers tell whether
25443 Tor has downloaded sufficient directory information. (Patch
25445 - You can now use the ControlSocket option to tell Tor to listen for
25446 controller connections on Unix domain sockets on systems that
25447 support them. (Patch from Peter Palfrader.)
25448 - STREAM NEW events are generated for DNSPort requests and for
25449 tunneled directory connections. (Patch from Robert Hogan.)
25450 - New "GETINFO address-mappings/*" command to get address mappings
25451 with expiry information. "addr-mappings/*" is now deprecated.
25454 o Minor features (misc):
25455 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
25457 - The tor-gencert tool for v3 directory authorities now creates all
25458 files as readable to the file creator only, and write-protects
25459 the authority identity key.
25460 - When dumping memory usage, list bytes used in buffer memory
25462 - When running with dmalloc, dump more stats on hup and on exit.
25463 - Directory authorities now fail quickly and (relatively) harmlessly
25464 if they generate a network status document that is somehow
25467 o Traffic load balancing improvements:
25468 - If exit bandwidth ever exceeds one third of total bandwidth, then
25469 use the correct formula to weight exit nodes when choosing paths.
25470 (Based on patch from Mike Perry.)
25471 - Choose perfectly fairly among routers when choosing by bandwidth and
25472 weighting by fraction of bandwidth provided by exits. Previously, we
25473 would choose with only approximate fairness, and correct ourselves
25474 if we ran off the end of the list. [Bugfix on 0.1.2.x]
25476 o Performance improvements:
25477 - Be more aggressive with freeing buffer RAM or putting it on the
25479 - Use Critical Sections rather than Mutexes for synchronizing threads
25480 on win32; Mutexes are heavier-weight, and designed for synchronizing
25483 o Deprecated and removed features:
25484 - RedirectExits is now deprecated.
25485 - Stop allowing address masks that do not correspond to bit prefixes.
25486 We have warned about these for a really long time; now it's time
25487 to reject them. (Patch from croup.)
25489 o Minor bugfixes (directory):
25490 - Fix another crash bug related to extra-info caching. (Bug found by
25491 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
25492 - Directories no longer return a "304 not modified" when they don't
25493 have the networkstatus the client asked for. Also fix a memory
25494 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
25495 - We had accidentally labelled 0.1.2.x directory servers as not
25496 suitable for begin_dir requests, and had labelled no directory
25497 servers as suitable for uploading extra-info documents. [Bugfix
25500 o Minor bugfixes (dns):
25501 - Fix a crash when DNSPort is set more than once. (Patch from Robert
25502 Hogan.) [Bugfix on 0.2.0.2-alpha]
25503 - Add DNSPort connections to the global connection list, so that we
25504 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
25506 - Fix a dangling reference that could lead to a crash when DNSPort is
25507 changed or closed (Patch from Robert Hogan.) [Bugfix on
25510 o Minor bugfixes (controller):
25511 - Provide DNS expiry times in GMT, not in local time. For backward
25512 compatibility, ADDRMAP events only provide GMT expiry in an extended
25513 field. "GETINFO address-mappings" always does the right thing.
25514 - Use CRLF line endings properly in NS events.
25515 - Terminate multi-line control events properly. (Original patch
25516 from tup.) [Bugfix on 0.1.2.x-alpha]
25517 - Do not include spaces in SOURCE_ADDR fields in STREAM
25518 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
25521 Changes in version 0.1.2.15 - 2007-07-17
25522 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
25523 problems, fixes compilation on BSD, and fixes a variety of other
25524 bugs. Everybody should upgrade.
25526 o Major bugfixes (compilation):
25527 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
25529 o Major bugfixes (crashes):
25530 - Try even harder not to dereference the first character after
25531 an mmap(). Reported by lodger.
25532 - Fix a crash bug in directory authorities when we re-number the
25533 routerlist while inserting a new router.
25534 - When the cached-routers file is an even multiple of the page size,
25535 don't run off the end and crash. (Fixes bug 455; based on idea
25537 - Fix eventdns.c behavior on Solaris: It is critical to include
25538 orconfig.h _before_ sys/types.h, so that we can get the expected
25539 definition of _FILE_OFFSET_BITS.
25541 o Major bugfixes (security):
25542 - Fix a possible buffer overrun when using BSD natd support. Bug
25544 - When sending destroy cells from a circuit's origin, don't include
25545 the reason for tearing down the circuit. The spec says we didn't,
25546 and now we actually don't. Reported by lodger.
25547 - Keep streamids from different exits on a circuit separate. This
25548 bug may have allowed other routers on a given circuit to inject
25549 cells into streams. Reported by lodger; fixes bug 446.
25550 - If there's a never-before-connected-to guard node in our list,
25551 never choose any guards past it. This way we don't expand our
25552 guard list unless we need to.
25554 o Minor bugfixes (guard nodes):
25555 - Weight guard selection by bandwidth, so that low-bandwidth nodes
25556 don't get overused as guards.
25558 o Minor bugfixes (directory):
25559 - Correctly count the number of authorities that recommend each
25560 version. Previously, we were under-counting by 1.
25561 - Fix a potential crash bug when we load many server descriptors at
25562 once and some of them make others of them obsolete. Fixes bug 458.
25564 o Minor bugfixes (hidden services):
25565 - Stop tearing down the whole circuit when the user asks for a
25566 connection to a port that the hidden service didn't configure.
25569 o Minor bugfixes (misc):
25570 - On Windows, we were preventing other processes from reading
25571 cached-routers while Tor was running. Reported by janbar.
25572 - Fix a possible (but very unlikely) bug in picking routers by
25573 bandwidth. Add a log message to confirm that it is in fact
25574 unlikely. Patch from lodger.
25575 - Backport a couple of memory leak fixes.
25576 - Backport miscellaneous cosmetic bugfixes.
25579 Changes in version 0.2.0.2-alpha - 2007-06-02
25580 o Major bugfixes on 0.2.0.1-alpha:
25581 - Fix an assertion failure related to servers without extra-info digests.
25582 Resolves bugs 441 and 442.
25584 o Minor features (directory):
25585 - Support "If-Modified-Since" when answering HTTP requests for
25586 directories, running-routers documents, and network-status documents.
25587 (There's no need to support it for router descriptors, since those
25588 are downloaded by descriptor digest.)
25590 o Minor build issues:
25591 - Clear up some MIPSPro compiler warnings.
25592 - When building from a tarball on a machine that happens to have SVK
25593 installed, report the micro-revision as whatever version existed
25594 in the tarball, not as "x".
25597 Changes in version 0.2.0.1-alpha - 2007-06-01
25598 This early development snapshot provides new features for people running
25599 Tor as both a client and a server (check out the new RelayBandwidth
25600 config options); lets Tor run as a DNS proxy; and generally moves us
25601 forward on a lot of fronts.
25603 o Major features, server usability:
25604 - New config options RelayBandwidthRate and RelayBandwidthBurst:
25605 a separate set of token buckets for relayed traffic. Right now
25606 relayed traffic is defined as answers to directory requests, and
25607 OR connections that don't have any local circuits on them.
25609 o Major features, client usability:
25610 - A client-side DNS proxy feature to replace the need for
25611 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
25612 for DNS requests on port 9999, use the Tor network to resolve them
25613 anonymously, and send the reply back like a regular DNS server.
25614 The code still only implements a subset of DNS.
25615 - Make PreferTunneledDirConns and TunnelDirConns work even when
25616 we have no cached directory info. This means Tor clients can now
25617 do all of their connections protected by TLS.
25619 o Major features, performance and efficiency:
25620 - Directory authorities accept and serve "extra info" documents for
25621 routers. These documents contain fields from router descriptors
25622 that aren't usually needed, and that use a lot of excess
25623 bandwidth. Once these fields are removed from router descriptors,
25624 the bandwidth savings should be about 60%. [Partially implements
25626 - Servers upload extra-info documents to any authority that accepts
25627 them. Authorities (and caches that have been configured to download
25628 extra-info documents) download them as needed. [Partially implements
25630 - Change the way that Tor buffers data that it is waiting to write.
25631 Instead of queueing data cells in an enormous ring buffer for each
25632 client->OR or OR->OR connection, we now queue cells on a separate
25633 queue for each circuit. This lets us use less slack memory, and
25634 will eventually let us be smarter about prioritizing different kinds
25636 - Use memory pools to allocate cells with better speed and memory
25637 efficiency, especially on platforms where malloc() is inefficient.
25638 - Stop reading on edge connections when their corresponding circuit
25639 buffers are full; start again as the circuits empty out.
25641 o Major features, other:
25642 - Add an HSAuthorityRecordStats option that hidden service authorities
25643 can use to track statistics of overall hidden service usage without
25644 logging information that would be very useful to an attacker.
25645 - Start work implementing multi-level keys for directory authorities:
25646 Add a standalone tool to generate key certificates. (Proposal 103.)
25649 - Directory authorities now call routers Stable if they have an
25650 uptime of at least 30 days, even if that's not the median uptime
25651 in the network. Implements proposal 107, suggested by Kevin Bauer
25654 o Minor fixes (resource management):
25655 - Count the number of open sockets separately from the number
25656 of active connection_t objects. This will let us avoid underusing
25657 our allocated connection limit.
25658 - We no longer use socket pairs to link an edge connection to an
25659 anonymous directory connection or a DirPort test connection.
25660 Instead, we track the link internally and transfer the data
25661 in-process. This saves two sockets per "linked" connection (at the
25662 client and at the server), and avoids the nasty Windows socketpair()
25664 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
25665 for every single inactive connection_t. Free items from the
25666 4k/16k-buffer free lists when they haven't been used for a while.
25668 o Minor features (build):
25669 - Make autoconf search for libevent, openssl, and zlib consistently.
25670 - Update deprecated macros in configure.in.
25671 - When warning about missing headers, tell the user to let us
25672 know if the compile succeeds anyway, so we can downgrade the
25674 - Include the current subversion revision as part of the version
25675 string: either fetch it directly if we're in an SVN checkout, do
25676 some magic to guess it if we're in an SVK checkout, or use
25677 the last-detected version if we're building from a .tar.gz.
25678 Use this version consistently in log messages.
25680 o Minor features (logging):
25681 - Always prepend "Bug: " to any log message about a bug.
25682 - Put a platform string (e.g. "Linux i686") in the startup log
25683 message, so when people paste just their logs, we know if it's
25684 OpenBSD or Windows or what.
25685 - When logging memory usage, break down memory used in buffers by
25688 o Minor features (directory system):
25689 - New config option V2AuthoritativeDirectory that all directory
25690 authorities should set. This will let future authorities choose
25691 not to serve V2 directory information.
25692 - Directory authorities allow multiple router descriptors and/or extra
25693 info documents to be uploaded in a single go. This will make
25694 implementing proposal 104 simpler.
25696 o Minor features (controller):
25697 - Add a new config option __DisablePredictedCircuits designed for
25698 use by the controller, when we don't want Tor to build any circuits
25700 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
25701 so we can exit from the middle of the circuit.
25702 - Implement "getinfo status/circuit-established".
25703 - Implement "getinfo status/version/..." so a controller can tell
25704 whether the current version is recommended, and whether any versions
25705 are good, and how many authorities agree. (Patch from shibz.)
25707 o Minor features (hidden services):
25708 - Allow multiple HiddenServicePort directives with the same virtual
25709 port; when they occur, the user is sent round-robin to one
25710 of the target ports chosen at random. Partially fixes bug 393 by
25711 adding limited ad-hoc round-robining.
25713 o Minor features (other):
25715 - Add a new AutomapHostsOnResolve option: when it is enabled, any
25716 resolve request for hosts matching a given pattern causes Tor to
25717 generate an internal virtual address mapping for that host. This
25718 allows DNSPort to work sensibly with hidden service users. By
25719 default, .exit and .onion addresses are remapped; the list of
25720 patterns can be reconfigured with AutomapHostsSuffixes.
25721 - Add an "-F" option to tor-resolve to force a resolve for a .onion
25722 address. Thanks to the AutomapHostsOnResolve option, this is no
25723 longer a completely silly thing to do.
25724 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
25725 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
25726 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
25727 minus 1 byte: the actual maximum declared bandwidth.
25729 o Removed features:
25730 - Removed support for the old binary "version 0" controller protocol.
25731 This has been deprecated since 0.1.1, and warnings have been issued
25732 since 0.1.2. When we encounter a v0 control message, we now send
25733 back an error and close the connection.
25734 - Remove the old "dns worker" server DNS code: it hasn't been default
25735 since 0.1.2.2-alpha, and all the servers seem to be using the new
25738 o Minor bugfixes (portability):
25739 - Even though Windows is equally happy with / and \ as path separators,
25740 try to use \ consistently on Windows and / consistently on Unix: it
25741 makes the log messages nicer.
25742 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
25743 - Read resolv.conf files correctly on platforms where read() returns
25744 partial results on small file reads.
25746 o Minor bugfixes (directory):
25747 - Correctly enforce that elements of directory objects do not appear
25748 more often than they are allowed to appear.
25749 - When we are reporting the DirServer line we just parsed, we were
25750 logging the second stanza of the key fingerprint, not the first.
25752 o Minor bugfixes (logging):
25753 - When we hit an EOF on a log (probably because we're shutting down),
25754 don't try to remove the log from the list: just mark it as
25755 unusable. (Bulletproofs against bug 222.)
25757 o Minor bugfixes (other):
25758 - In the exitlist script, only consider the most recently published
25759 server descriptor for each server. Also, when the user requests
25760 a list of servers that _reject_ connections to a given address,
25761 explicitly exclude the IPs that also have servers that accept
25762 connections to that address. (Resolves bug 405.)
25763 - Stop allowing hibernating servers to be "stable" or "fast".
25764 - On Windows, we were preventing other processes from reading
25765 cached-routers while Tor was running. (Reported by janbar)
25766 - Make the NodeFamilies config option work. (Reported by
25767 lodger -- it has never actually worked, even though we added it
25769 - Check return values from pthread_mutex functions.
25770 - Don't save non-general-purpose router descriptors to the disk cache,
25771 because we have no way of remembering what their purpose was when
25773 - Add even more asserts to hunt down bug 417.
25774 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
25775 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
25776 Add a log message to confirm that it is in fact unlikely.
25778 o Minor bugfixes (controller):
25779 - Make 'getinfo fingerprint' return a 551 error if we're not a
25780 server, so we match what the control spec claims we do. Reported
25782 - Fix a typo in an error message when extendcircuit fails that
25783 caused us to not follow the \r\n-based delimiter protocol. Reported
25786 o Code simplifications and refactoring:
25787 - Stop passing around circuit_t and crypt_path_t pointers that are
25788 implicit in other procedure arguments.
25789 - Drop the old code to choke directory connections when the
25790 corresponding OR connections got full: thanks to the cell queue
25791 feature, OR conns don't get full any more.
25792 - Make dns_resolve() handle attaching connections to circuits
25793 properly, so the caller doesn't have to.
25794 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
25795 - Keep the connection array as a dynamic smartlist_t, rather than as
25796 a fixed-sized array. This is important, as the number of connections
25797 is becoming increasingly decoupled from the number of sockets.
25800 Changes in version 0.1.2.14 - 2007-05-25
25801 Tor 0.1.2.14 changes the addresses of two directory authorities (this
25802 change especially affects those who serve or use hidden services),
25803 and fixes several other crash- and security-related bugs.
25805 o Directory authority changes:
25806 - Two directory authorities (moria1 and moria2) just moved to new
25807 IP addresses. This change will particularly affect those who serve
25808 or use hidden services.
25810 o Major bugfixes (crashes):
25811 - If a directory server runs out of space in the connection table
25812 as it's processing a begin_dir request, it will free the exit stream
25813 but leave it attached to the circuit, leading to unpredictable
25814 behavior. (Reported by seeess, fixes bug 425.)
25815 - Fix a bug in dirserv_remove_invalid() that would cause authorities
25816 to corrupt memory under some really unlikely scenarios.
25817 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
25818 - Avoid segfaults when reading from mmaped descriptor file. (Reported
25821 o Major bugfixes (security):
25822 - When choosing an entry guard for a circuit, avoid using guards
25823 that are in the same family as the chosen exit -- not just guards
25824 that are exactly the chosen exit. (Reported by lodger.)
25826 o Major bugfixes (resource management):
25827 - If a directory authority is down, skip it when deciding where to get
25828 networkstatus objects or descriptors. Otherwise we keep asking
25829 every 10 seconds forever. Fixes bug 384.
25830 - Count it as a failure if we fetch a valid network-status but we
25831 don't want to keep it. Otherwise we'll keep fetching it and keep
25832 not wanting to keep it. Fixes part of bug 422.
25833 - If all of our dirservers have given us bad or no networkstatuses
25834 lately, then stop hammering them once per minute even when we
25835 think they're failed. Fixes another part of bug 422.
25838 - Actually set the purpose correctly for descriptors inserted with
25839 purpose=controller.
25840 - When we have k non-v2 authorities in our DirServer config,
25841 we ignored the last k authorities in the list when updating our
25843 - Correctly back-off from requesting router descriptors that we are
25844 having a hard time downloading.
25845 - Read resolv.conf files correctly on platforms where read() returns
25846 partial results on small file reads.
25847 - Don't rebuild the entire router store every time we get 32K of
25848 routers: rebuild it when the journal gets very large, or when
25849 the gaps in the store get very large.
25852 - When routers publish SVN revisions in their router descriptors,
25853 authorities now include those versions correctly in networkstatus
25855 - Warn when using a version of libevent before 1.3b to run a server on
25856 OSX or BSD: these versions interact badly with userspace threads.
25859 Changes in version 0.1.2.13 - 2007-04-24
25860 This release features some major anonymity fixes, such as safer path
25861 selection; better client performance; faster bootstrapping, better
25862 address detection, and better DNS support for servers; write limiting as
25863 well as read limiting to make servers easier to run; and a huge pile of
25864 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
25866 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
25867 of the Freenode IRC network, remembering his patience and vision for
25868 free speech on the Internet.
25871 - Fix a memory leak when we ask for "all" networkstatuses and we
25872 get one we don't recognize.
25873 - Add more asserts to hunt down bug 417.
25874 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
25877 Changes in version 0.1.2.12-rc - 2007-03-16
25879 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
25880 directory information requested inside Tor connections (i.e. via
25881 begin_dir cells). It only triggered when the same connection was
25882 serving other data at the same time. Reported by seeess.
25885 - When creating a circuit via the controller, send a 'launched'
25886 event when we're done, so we follow the spec better.
25889 Changes in version 0.1.2.11-rc - 2007-03-15
25890 o Minor bugfixes (controller), reported by daejees:
25891 - Correct the control spec to match how the code actually responds
25892 to 'getinfo addr-mappings/*'.
25893 - The control spec described a GUARDS event, but the code
25894 implemented a GUARD event. Standardize on GUARD, but let people
25895 ask for GUARDS too.
25898 Changes in version 0.1.2.10-rc - 2007-03-07
25899 o Major bugfixes (Windows):
25900 - Do not load the NT services library functions (which may not exist)
25901 just to detect if we're a service trying to shut down. Now we run
25902 on Win98 and friends again.
25904 o Minor bugfixes (other):
25905 - Clarify a couple of log messages.
25906 - Fix a misleading socks5 error number.
25909 Changes in version 0.1.2.9-rc - 2007-03-02
25910 o Major bugfixes (Windows):
25911 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
25912 of the usual GCC "%llu". This prevents a bug when saving 64-bit
25913 int configuration values: the high-order 32 bits would get
25914 truncated. In particular, we were being bitten by the default
25915 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
25916 and maybe also bug 397.)
25918 o Minor bugfixes (performance):
25919 - Use OpenSSL's AES implementation on platforms where it's faster.
25920 This could save us as much as 10% CPU usage.
25922 o Minor bugfixes (server):
25923 - Do not rotate onion key immediately after setting it for the first
25926 o Minor bugfixes (directory authorities):
25927 - Stop calling servers that have been hibernating for a long time
25928 "stable". Also, stop letting hibernating or obsolete servers affect
25929 uptime and bandwidth cutoffs.
25930 - Stop listing hibernating servers in the v1 directory.
25932 o Minor bugfixes (hidden services):
25933 - Upload hidden service descriptors slightly less often, to reduce
25934 load on authorities.
25936 o Minor bugfixes (other):
25937 - Fix an assert that could trigger if a controller quickly set then
25938 cleared EntryNodes. Bug found by Udo van den Heuvel.
25939 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
25941 - Fix a potential race condition in the rpm installer. Found by
25943 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
25944 of 2 as indicating that the server is completely bad; it sometimes
25945 means that the server is just bad for the request in question. (may fix
25946 the last of bug 326.)
25947 - Disable encrypted directory connections when we don't have a server
25948 descriptor for the destination. We'll get this working again in
25952 Changes in version 0.1.2.8-beta - 2007-02-26
25953 o Major bugfixes (crashes):
25954 - Stop crashing when the controller asks us to resetconf more than
25955 one config option at once. (Vidalia 0.0.11 does this.)
25956 - Fix a crash that happened on Win98 when we're given command-line
25957 arguments: don't try to load NT service functions from advapi32.dll
25958 except when we need them. (Bug introduced in 0.1.2.7-alpha;
25960 - Fix a longstanding obscure crash bug that could occur when
25961 we run out of DNS worker processes. (Resolves bug 390.)
25963 o Major bugfixes (hidden services):
25964 - Correctly detect whether hidden service descriptor downloads are
25965 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
25967 o Major bugfixes (accounting):
25968 - When we start during an accounting interval before it's time to wake
25969 up, remember to wake up at the correct time. (May fix bug 342.)
25971 o Minor bugfixes (controller):
25972 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
25973 clear the corresponding on_circuit variable, and remember later
25974 that we don't need to send a redundant CLOSED event. Resolves part
25976 - Report events where a resolve succeeded or where we got a socks
25977 protocol error correctly, rather than calling both of them
25979 - Change reported stream target addresses to IP consistently when
25980 we finally get the IP from an exit node.
25981 - Send log messages to the controller even if they happen to be very
25984 o Minor bugfixes (other):
25985 - Display correct results when reporting which versions are
25986 recommended, and how recommended they are. (Resolves bug 383.)
25987 - Improve our estimates for directory bandwidth to be less random:
25988 guess that an unrecognized directory will have the average bandwidth
25989 from all known directories, not that it will have the average
25990 bandwidth from those directories earlier than it on the list.
25991 - If we start a server with ClientOnly 1, then set ClientOnly to 0
25992 and hup, stop triggering an assert based on an empty onion_key.
25993 - On platforms with no working mmap() equivalent, don't warn the
25994 user when cached-routers doesn't exist.
25995 - Warn the user when mmap() [or its equivalent] fails for some reason
25996 other than file-not-found.
25997 - Don't warn the user when cached-routers.new doesn't exist: that's
25998 perfectly fine when starting up for the first time.
25999 - When EntryNodes are configured, rebuild the guard list to contain,
26000 in order: the EntryNodes that were guards before; the rest of the
26001 EntryNodes; the nodes that were guards before.
26002 - Mask out all signals in sub-threads; only the libevent signal
26003 handler should be processing them. This should prevent some crashes
26004 on some machines using pthreads. (Patch from coderman.)
26005 - Fix switched arguments on memset in the implementation of
26006 tor_munmap() for systems with no mmap() call.
26007 - When Tor receives a router descriptor that it asked for, but
26008 no longer wants (because it has received fresh networkstatuses
26009 in the meantime), do not warn the user. Cache the descriptor if
26010 we're a cache; drop it if we aren't.
26011 - Make earlier entry guards _really_ get retried when the network
26013 - On a malformed DNS reply, always give an error to the corresponding
26015 - Build with recent libevents on platforms that do not define the
26016 nonstandard types "u_int8_t" and friends.
26018 o Minor features (controller):
26019 - Warn the user when an application uses the obsolete binary v0
26020 control protocol. We're planning to remove support for it during
26021 the next development series, so it's good to give people some
26023 - Add STREAM_BW events to report per-entry-stream bandwidth
26024 use. (Patch from Robert Hogan.)
26025 - Rate-limit SIGNEWNYM signals in response to controllers that
26026 impolitely generate them for every single stream. (Patch from
26027 mwenge; closes bug 394.)
26028 - Make REMAP stream events have a SOURCE (cache or exit), and
26029 make them generated in every case where we get a successful
26030 connected or resolved cell.
26032 o Minor bugfixes (performance):
26033 - Call router_have_min_dir_info half as often. (This is showing up in
26034 some profiles, but not others.)
26035 - When using GCC, make log_debug never get called at all, and its
26036 arguments never get evaluated, when no debug logs are configured.
26037 (This is showing up in some profiles, but not others.)
26040 - Remove some never-implemented options. Mark PathlenCoinWeight as
26042 - Implement proposal 106: Stop requiring clients to have well-formed
26043 certificates; stop checking nicknames in certificates. (Clients
26044 have certificates so that they can look like Tor servers, but in
26045 the future we might want to allow them to look like regular TLS
26046 clients instead. Nicknames in certificates serve no purpose other
26047 than making our protocol easier to recognize on the wire.)
26048 - Revise messages on handshake failure again to be even more clear about
26049 which are incoming connections and which are outgoing.
26050 - Discard any v1 directory info that's over 1 month old (for
26051 directories) or over 1 week old (for running-routers lists).
26052 - Do not warn when individual nodes in the configuration's EntryNodes,
26053 ExitNodes, etc are down: warn only when all possible nodes
26054 are down. (Fixes bug 348.)
26055 - Always remove expired routers and networkstatus docs before checking
26056 whether we have enough information to build circuits. (Fixes
26058 - Put a lower-bound on MaxAdvertisedBandwidth.
26061 Changes in version 0.1.2.7-alpha - 2007-02-06
26062 o Major bugfixes (rate limiting):
26063 - Servers decline directory requests much more aggressively when
26064 they're low on bandwidth. Otherwise they end up queueing more and
26065 more directory responses, which can't be good for latency.
26066 - But never refuse directory requests from local addresses.
26067 - Fix a memory leak when sending a 503 response for a networkstatus
26069 - Be willing to read or write on local connections (e.g. controller
26070 connections) even when the global rate limiting buckets are empty.
26071 - If our system clock jumps back in time, don't publish a negative
26072 uptime in the descriptor. Also, don't let the global rate limiting
26073 buckets go absurdly negative.
26074 - Flush local controller connection buffers periodically as we're
26075 writing to them, so we avoid queueing 4+ megabytes of data before
26078 o Major bugfixes (NT services):
26079 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
26080 command-line flag so that admins can override the default by saying
26081 "tor --service install --user "SomeUser"". This will not affect
26082 existing installed services. Also, warn the user that the service
26083 will look for its configuration file in the service user's
26084 %appdata% directory. (We can't do the 'hardwire the user's appdata
26085 directory' trick any more, since we may not have read access to that
26088 o Major bugfixes (other):
26089 - Previously, we would cache up to 16 old networkstatus documents
26090 indefinitely, if they came from nontrusted authorities. Now we
26091 discard them if they are more than 10 days old.
26092 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
26094 - Detect and reject malformed DNS responses containing circular
26096 - If exits are rare enough that we're not marking exits as guards,
26097 ignore exit bandwidth when we're deciding the required bandwidth
26099 - When we're handling a directory connection tunneled over Tor,
26100 don't fill up internal memory buffers with all the data we want
26101 to tunnel; instead, only add it if the OR connection that will
26102 eventually receive it has some room for it. (This can lead to
26103 slowdowns in tunneled dir connections; a better solution will have
26104 to wait for 0.2.0.)
26106 o Minor bugfixes (dns):
26107 - Add some defensive programming to eventdns.c in an attempt to catch
26108 possible memory-stomping bugs.
26109 - Detect and reject DNS replies containing IPv4 or IPv6 records with
26110 an incorrect number of bytes. (Previously, we would ignore the
26112 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
26113 in the correct order, and doesn't crash.
26114 - Free memory held in recently-completed DNS lookup attempts on exit.
26115 This was not a memory leak, but may have been hiding memory leaks.
26116 - Handle TTL values correctly on reverse DNS lookups.
26117 - Treat failure to parse resolv.conf as an error.
26119 o Minor bugfixes (other):
26120 - Fix crash with "tor --list-fingerprint" (reported by seeess).
26121 - When computing clock skew from directory HTTP headers, consider what
26122 time it was when we finished asking for the directory, not what
26124 - Expire socks connections if they spend too long waiting for the
26125 handshake to finish. Previously we would let them sit around for
26126 days, if the connecting application didn't close them either.
26127 - And if the socks handshake hasn't started, don't send a
26128 "DNS resolve socks failed" handshake reply; just close it.
26129 - Stop using C functions that OpenBSD's linker doesn't like.
26130 - Don't launch requests for descriptors unless we have networkstatuses
26131 from at least half of the authorities. This delays the first
26132 download slightly under pathological circumstances, but can prevent
26133 us from downloading a bunch of descriptors we don't need.
26134 - Do not log IPs with TLS failures for incoming TLS
26135 connections. (Fixes bug 382.)
26136 - If the user asks to use invalid exit nodes, be willing to use
26138 - Stop using the reserved ac_cv namespace in our configure script.
26139 - Call stat() slightly less often; use fstat() when possible.
26140 - Refactor the way we handle pending circuits when an OR connection
26141 completes or fails, in an attempt to fix a rare crash bug.
26142 - Only rewrite a conn's address based on X-Forwarded-For: headers
26143 if it's a parseable public IP address; and stop adding extra quotes
26144 to the resulting address.
26147 - Weight directory requests by advertised bandwidth. Now we can
26148 let servers enable write limiting but still allow most clients to
26149 succeed at their directory requests. (We still ignore weights when
26150 choosing a directory authority; I hope this is a feature.)
26153 - Create a new file ReleaseNotes which was the old ChangeLog. The
26154 new ChangeLog file now includes the summaries for all development
26156 - Check for addresses with invalid characters at the exit as well
26157 as at the client, and warn less verbosely when they fail. You can
26158 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
26159 - Adapt a patch from goodell to let the contrib/exitlist script
26160 take arguments rather than require direct editing.
26161 - Inform the server operator when we decide not to advertise a
26162 DirPort due to AccountingMax enabled or a low BandwidthRate. It
26163 was confusing Zax, so now we're hopefully more helpful.
26164 - Bring us one step closer to being able to establish an encrypted
26165 directory tunnel without knowing a descriptor first. Still not
26166 ready yet. As part of the change, now assume we can use a
26167 create_fast cell if we don't know anything about a router.
26168 - Allow exit nodes to use nameservers running on ports other than 53.
26169 - Servers now cache reverse DNS replies.
26170 - Add an --ignore-missing-torrc command-line option so that we can
26171 get the "use sensible defaults if the configuration file doesn't
26172 exist" behavior even when specifying a torrc location on the command
26175 o Minor features (controller):
26176 - Track reasons for OR connection failure; make these reasons
26177 available via the controller interface. (Patch from Mike Perry.)
26178 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
26179 can learn when clients are sending malformed hostnames to Tor.
26180 - Clean up documentation for controller status events.
26181 - Add a REMAP status to stream events to note that a stream's
26182 address has changed because of a cached address or a MapAddress
26186 Changes in version 0.1.2.6-alpha - 2007-01-09
26188 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
26189 connection handles more than 4 gigs in either direction, we crash.
26190 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
26191 advertised exit node, somebody might try to exit from us when
26192 we're bootstrapping and before we've built our descriptor yet.
26193 Refuse the connection rather than crashing.
26196 - Warn if we (as a server) find that we've resolved an address that we
26197 weren't planning to resolve.
26198 - Warn that using select() on any libevent version before 1.1 will be
26199 unnecessarily slow (even for select()).
26200 - Flush ERR-level controller status events just like we currently
26201 flush ERR-level log events, so that a Tor shutdown doesn't prevent
26202 the controller from learning about current events.
26204 o Minor features (more controller status events):
26205 - Implement EXTERNAL_ADDRESS server status event so controllers can
26206 learn when our address changes.
26207 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
26208 can learn when directories reject our descriptor.
26209 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
26210 can learn when a client application is speaking a non-socks protocol
26212 - Implement DANGEROUS_SOCKS client status event so controllers
26213 can learn when a client application is leaking DNS addresses.
26214 - Implement BUG general status event so controllers can learn when
26215 Tor is unhappy about its internal invariants.
26216 - Implement CLOCK_SKEW general status event so controllers can learn
26217 when Tor thinks the system clock is set incorrectly.
26218 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
26219 server status events so controllers can learn when their descriptors
26220 are accepted by a directory.
26221 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
26222 server status events so controllers can learn about Tor's progress in
26223 deciding whether it's reachable from the outside.
26224 - Implement BAD_LIBEVENT general status event so controllers can learn
26225 when we have a version/method combination in libevent that needs to
26227 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
26228 and DNS_USELESS server status events so controllers can learn
26229 about changes to DNS server status.
26231 o Minor features (directory):
26232 - Authorities no longer recommend exits as guards if this would shift
26233 too much load to the exit nodes.
26236 Changes in version 0.1.2.5-alpha - 2007-01-06
26238 - Enable write limiting as well as read limiting. Now we sacrifice
26239 capacity if we're pushing out lots of directory traffic, rather
26240 than overrunning the user's intended bandwidth limits.
26241 - Include TLS overhead when counting bandwidth usage; previously, we
26242 would count only the bytes sent over TLS, but not the bytes used
26244 - Support running the Tor service with a torrc not in the same
26245 directory as tor.exe and default to using the torrc located in
26246 the %appdata%\Tor\ of the user who installed the service. Patch
26248 - Servers now check for the case when common DNS requests are going to
26249 wildcarded addresses (i.e. all getting the same answer), and change
26250 their exit policy to reject *:* if it's happening.
26251 - Implement BEGIN_DIR cells, so we can connect to the directory
26252 server via TLS to do encrypted directory requests rather than
26253 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
26254 config options if you like.
26256 o Minor features (config and docs):
26257 - Start using the state file to store bandwidth accounting data:
26258 the bw_accounting file is now obsolete. We'll keep generating it
26259 for a while for people who are still using 0.1.2.4-alpha.
26260 - Try to batch changes to the state file so that we do as few
26261 disk writes as possible while still storing important things in
26263 - The state file and the bw_accounting file get saved less often when
26264 the AvoidDiskWrites config option is set.
26265 - Make PIDFile work on Windows (untested).
26266 - Add internal descriptions for a bunch of configuration options:
26267 accessible via controller interface and in comments in saved
26269 - Reject *:563 (NNTPS) in the default exit policy. We already reject
26270 NNTP by default, so this seems like a sensible addition.
26271 - Clients now reject hostnames with invalid characters. This should
26272 avoid some inadvertent info leaks. Add an option
26273 AllowNonRFC953Hostnames to disable this behavior, in case somebody
26274 is running a private network with hosts called @, !, and #.
26275 - Add a maintainer script to tell us which options are missing
26276 documentation: "make check-docs".
26277 - Add a new address-spec.txt document to describe our special-case
26278 addresses: .exit, .onion, and .noconnnect.
26280 o Minor features (DNS):
26281 - Ongoing work on eventdns infrastructure: now it has dns server
26282 and ipv6 support. One day Tor will make use of it.
26283 - Add client-side caching for reverse DNS lookups.
26284 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
26285 - When we change nameservers or IP addresses, reset and re-launch
26286 our tests for DNS hijacking.
26288 o Minor features (directory):
26289 - Authorities now specify server versions in networkstatus. This adds
26290 about 2% to the size of compressed networkstatus docs, and allows
26291 clients to tell which servers support BEGIN_DIR and which don't.
26292 The implementation is forward-compatible with a proposed future
26293 protocol version scheme not tied to Tor versions.
26294 - DirServer configuration lines now have an orport= option so
26295 clients can open encrypted tunnels to the authorities without
26296 having downloaded their descriptors yet. Enabled for moria1,
26297 moria2, tor26, and lefkada now in the default configuration.
26298 - Directory servers are more willing to send a 503 "busy" if they
26299 are near their write limit, especially for v1 directory requests.
26300 Now they can use their limited bandwidth for actual Tor traffic.
26301 - Clients track responses with status 503 from dirservers. After a
26302 dirserver has given us a 503, we try not to use it until an hour has
26303 gone by, or until we have no dirservers that haven't given us a 503.
26304 - When we get a 503 from a directory, and we're not a server, we don't
26305 count the failure against the total number of failures allowed
26306 for the thing we're trying to download.
26307 - Report X-Your-Address-Is correctly from tunneled directory
26308 connections; don't report X-Your-Address-Is when it's an internal
26309 address; and never believe reported remote addresses when they're
26311 - Protect against an unlikely DoS attack on directory servers.
26312 - Add a BadDirectory flag to network status docs so that authorities
26313 can (eventually) tell clients about caches they believe to be
26316 o Minor features (controller):
26317 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
26318 - Reimplement GETINFO so that info/names stays in sync with the
26320 - Implement "GETINFO fingerprint".
26321 - Implement "SETEVENTS GUARD" so controllers can get updates on
26322 entry guard status as it changes.
26324 o Minor features (clean up obsolete pieces):
26325 - Remove some options that have been deprecated since at least
26326 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
26327 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
26328 to set log options.
26329 - We no longer look for identity and onion keys in "identity.key" and
26330 "onion.key" -- these were replaced by secret_id_key and
26331 secret_onion_key in 0.0.8pre1.
26332 - We no longer require unrecognized directory entries to be
26335 o Major bugfixes (security):
26336 - Stop sending the HttpProxyAuthenticator string to directory
26337 servers when directory connections are tunnelled through Tor.
26338 - Clients no longer store bandwidth history in the state file.
26339 - Do not log introduction points for hidden services if SafeLogging
26341 - When generating bandwidth history, round down to the nearest
26342 1k. When storing accounting data, round up to the nearest 1k.
26343 - When we're running as a server, remember when we last rotated onion
26344 keys, so that we will rotate keys once they're a week old even if
26345 we never stay up for a week ourselves.
26347 o Major bugfixes (other):
26348 - Fix a longstanding bug in eventdns that prevented the count of
26349 timed-out resolves from ever being reset. This bug caused us to
26350 give up on a nameserver the third time it timed out, and try it
26351 10 seconds later... and to give up on it every time it timed out
26353 - Take out the '5 second' timeout from the connection retry
26354 schedule. Now the first connect attempt will wait a full 10
26355 seconds before switching to a new circuit. Perhaps this will help
26356 a lot. Based on observations from Mike Perry.
26357 - Fix a bug on the Windows implementation of tor_mmap_file() that
26358 would prevent the cached-routers file from ever loading. Reported
26362 - Fix an assert failure when a directory authority sets
26363 AuthDirRejectUnlisted and then receives a descriptor from an
26364 unlisted router. Reported by seeess.
26365 - Avoid a double-free when parsing malformed DirServer lines.
26366 - Fix a bug when a BSD-style PF socket is first used. Patch from
26368 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
26369 to resolve an address at a given exit node even when they ask for
26371 - Servers no longer ever list themselves in their "family" line,
26372 even if configured to do so. This makes it easier to configure
26373 family lists conveniently.
26374 - When running as a server, don't fall back to 127.0.0.1 when no
26375 nameservers are configured in /etc/resolv.conf; instead, make the
26376 user fix resolv.conf or specify nameservers explicitly. (Resolves
26378 - Stop accepting certain malformed ports in configured exit policies.
26379 - Don't re-write the fingerprint file every restart, unless it has
26381 - Stop warning when a single nameserver fails: only warn when _all_ of
26382 our nameservers have failed. Also, when we only have one nameserver,
26383 raise the threshold for deciding that the nameserver is dead.
26384 - Directory authorities now only decide that routers are reachable
26385 if their identity keys are as expected.
26386 - When the user uses bad syntax in the Log config line, stop
26387 suggesting other bad syntax as a replacement.
26388 - Correctly detect ipv6 DNS capability on OpenBSD.
26390 o Minor bugfixes (controller):
26391 - Report the circuit number correctly in STREAM CLOSED events. Bug
26392 reported by Mike Perry.
26393 - Do not report bizarre values for results of accounting GETINFOs
26394 when the last second's write or read exceeds the allotted bandwidth.
26395 - Report "unrecognized key" rather than an empty string when the
26396 controller tries to fetch a networkstatus that doesn't exist.
26399 Changes in version 0.1.1.26 - 2006-12-14
26400 o Security bugfixes:
26401 - Stop sending the HttpProxyAuthenticator string to directory
26402 servers when directory connections are tunnelled through Tor.
26403 - Clients no longer store bandwidth history in the state file.
26404 - Do not log introduction points for hidden services if SafeLogging
26408 - Fix an assert failure when a directory authority sets
26409 AuthDirRejectUnlisted and then receives a descriptor from an
26410 unlisted router (reported by seeess).
26413 Changes in version 0.1.2.4-alpha - 2006-12-03
26415 - Add support for using natd; this allows FreeBSDs earlier than
26416 5.1.2 to have ipfw send connections through Tor without using
26417 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
26420 - Make all connections to addresses of the form ".noconnect"
26421 immediately get closed. This lets application/controller combos
26422 successfully test whether they're talking to the same Tor by
26423 watching for STREAM events.
26424 - Make cross.sh cross-compilation script work even when autogen.sh
26425 hasn't been run. (Patch from Michael Mohr.)
26426 - Statistics dumped by -USR2 now include a breakdown of public key
26427 operations, for profiling.
26430 - Fix a major leak when directory authorities parse their
26431 approved-routers list, a minor memory leak when we fail to pick
26432 an exit node, and a few rare leaks on errors.
26433 - Handle TransPort connections even when the server sends data before
26434 the client sends data. Previously, the connection would just hang
26435 until the client sent data. (Patch from tup based on patch from
26437 - Avoid assert failure when our cached-routers file is empty on
26441 - Don't log spurious warnings when we see a circuit close reason we
26442 don't recognize; it's probably just from a newer version of Tor.
26443 - Have directory authorities allow larger amounts of drift in uptime
26444 without replacing the server descriptor: previously, a server that
26445 restarted every 30 minutes could have 48 "interesting" descriptors
26447 - Start linking to the Tor specification and Tor reference manual
26448 correctly in the Windows installer.
26449 - Add Vidalia to the OS X uninstaller script, so when we uninstall
26450 Tor/Privoxy we also uninstall Vidalia.
26451 - Resume building on Irix64, and fix a lot of warnings from its
26452 MIPSpro C compiler.
26453 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
26454 when we're running as a client.
26457 Changes in version 0.1.1.25 - 2006-11-04
26459 - When a client asks us to resolve (rather than connect to)
26460 an address, and we have a cached answer, give them the cached
26461 answer. Previously, we would give them no answer at all.
26462 - We were building exactly the wrong circuits when we predict
26463 hidden service requirements, meaning Tor would have to build all
26464 its circuits on demand.
26465 - If none of our live entry guards have a high uptime, but we
26466 require a guard with a high uptime, try adding a new guard before
26467 we give up on the requirement. This patch should make long-lived
26468 connections more stable on average.
26469 - When testing reachability of our DirPort, don't launch new
26470 tests when there's already one in progress -- unreachable
26471 servers were stacking up dozens of testing streams.
26473 o Security bugfixes:
26474 - When the user sends a NEWNYM signal, clear the client-side DNS
26475 cache too. Otherwise we continue to act on previous information.
26478 - Avoid a memory corruption bug when creating a hash table for
26480 - Avoid possibility of controller-triggered crash when misusing
26481 certain commands from a v0 controller on platforms that do not
26482 handle printf("%s",NULL) gracefully.
26483 - Avoid infinite loop on unexpected controller input.
26484 - Don't log spurious warnings when we see a circuit close reason we
26485 don't recognize; it's probably just from a newer version of Tor.
26486 - Add Vidalia to the OS X uninstaller script, so when we uninstall
26487 Tor/Privoxy we also uninstall Vidalia.
26490 Changes in version 0.1.2.3-alpha - 2006-10-29
26492 - Prepare for servers to publish descriptors less often: never
26493 discard a descriptor simply for being too old until either it is
26494 recommended by no authorities, or until we get a better one for
26495 the same router. Make caches consider retaining old recommended
26496 routers for even longer.
26497 - If most authorities set a BadExit flag for a server, clients
26498 don't think of it as a general-purpose exit. Clients only consider
26499 authorities that advertise themselves as listing bad exits.
26500 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
26501 headers for content, so that we can work better in the presence of
26502 caching HTTP proxies.
26503 - Allow authorities to list nodes as bad exits by fingerprint or by
26506 o Minor features, controller:
26507 - Add a REASON field to CIRC events; for backward compatibility, this
26508 field is sent only to controllers that have enabled the extended
26509 event format. Also, add additional reason codes to explain why
26510 a given circuit has been destroyed or truncated. (Patches from
26512 - Add a REMOTE_REASON field to extended CIRC events to tell the
26513 controller about why a remote OR told us to close a circuit.
26514 - Stream events also now have REASON and REMOTE_REASON fields,
26515 working much like those for circuit events.
26516 - There's now a GETINFO ns/... field so that controllers can ask Tor
26517 about the current status of a router.
26518 - A new event type "NS" to inform a controller when our opinion of
26519 a router's status has changed.
26520 - Add a GETINFO events/names and GETINFO features/names so controllers
26521 can tell which events and features are supported.
26522 - A new CLEARDNSCACHE signal to allow controllers to clear the
26523 client-side DNS cache without expiring circuits.
26525 o Security bugfixes:
26526 - When the user sends a NEWNYM signal, clear the client-side DNS
26527 cache too. Otherwise we continue to act on previous information.
26530 - Avoid sending junk to controllers or segfaulting when a controller
26531 uses EVENT_NEW_DESC with verbose nicknames.
26532 - Stop triggering asserts if the controller tries to extend hidden
26533 service circuits (reported by mwenge).
26534 - Avoid infinite loop on unexpected controller input.
26535 - When the controller does a "GETINFO network-status", tell it
26536 about even those routers whose descriptors are very old, and use
26537 long nicknames where appropriate.
26538 - Change NT service functions to be loaded on demand. This lets us
26539 build with MinGW without breaking Tor for Windows 98 users.
26540 - Do DirPort reachability tests less often, since a single test
26541 chews through many circuits before giving up.
26542 - In the hidden service example in torrc.sample, stop recommending
26543 esoteric and discouraged hidden service options.
26544 - When stopping an NT service, wait up to 10 sec for it to actually
26545 stop. Patch from Matt Edman; resolves bug 295.
26546 - Fix handling of verbose nicknames with ORCONN controller events:
26547 make them show up exactly when requested, rather than exactly when
26549 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
26550 printing a duplicate "$" in the keys we send (reported by mwenge).
26551 - Correctly set maximum connection limit on Cygwin. (This time
26553 - Try to detect Windows correctly when cross-compiling.
26554 - Detect the size of the routers file correctly even if it is
26555 corrupted (on systems without mmap) or not page-aligned (on systems
26556 with mmap). This bug was harmless.
26557 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
26558 to open a stream fails; now we do in more cases. This should
26559 make clients able to find a good exit faster in some cases, since
26560 unhandleable requests will now get an error rather than timing out.
26561 - Resolve two memory leaks when rebuilding the on-disk router cache
26562 (reported by fookoowa).
26563 - Clean up minor code warnings suggested by the MIPSpro C compiler,
26564 and reported by some Centos users.
26565 - Controller signals now work on non-Unix platforms that don't define
26566 SIGUSR1 and SIGUSR2 the way we expect.
26567 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
26568 values before failing, and always enables eventdns.
26569 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
26570 Try to fix this in configure.in by checking for most functions
26571 before we check for libevent.
26574 Changes in version 0.1.2.2-alpha - 2006-10-07
26576 - Make our async eventdns library on-by-default for Tor servers,
26577 and plan to deprecate the separate dnsworker threads.
26578 - Add server-side support for "reverse" DNS lookups (using PTR
26579 records so clients can determine the canonical hostname for a given
26580 IPv4 address). Only supported by servers using eventdns; servers
26581 now announce in their descriptors whether they support eventdns.
26582 - Specify and implement client-side SOCKS5 interface for reverse DNS
26583 lookups (see doc/socks-extensions.txt).
26584 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
26585 connect to directory servers through Tor. Previously, clients needed
26586 to find Tor exits to make private connections to directory servers.
26587 - Avoid choosing Exit nodes for entry or middle hops when the
26588 total bandwidth available from non-Exit nodes is much higher than
26589 the total bandwidth available from Exit nodes.
26590 - Workaround for name servers (like Earthlink's) that hijack failing
26591 DNS requests and replace the no-such-server answer with a "helpful"
26592 redirect to an advertising-driven search portal. Also work around
26593 DNS hijackers who "helpfully" decline to hijack known-invalid
26594 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
26595 lets you turn it off.
26596 - Send out a burst of long-range padding cells once we've established
26597 that we're reachable. Spread them over 4 circuits, so hopefully
26598 a few will be fast. This exercises our bandwidth and bootstraps
26599 us into the directory more quickly.
26601 o New/improved config options:
26602 - Add new config option "ResolvConf" to let the server operator
26603 choose an alternate resolve.conf file when using eventdns.
26604 - Add an "EnforceDistinctSubnets" option to control our "exclude
26605 servers on the same /16" behavior. It's still on by default; this
26606 is mostly for people who want to operate private test networks with
26607 all the machines on the same subnet.
26608 - If one of our entry guards is on the ExcludeNodes list, or the
26609 directory authorities don't think it's a good guard, treat it as
26610 if it were unlisted: stop using it as a guard, and throw it off
26611 the guards list if it stays that way for a long time.
26612 - Allow directory authorities to be marked separately as authorities
26613 for the v1 directory protocol, the v2 directory protocol, and
26614 as hidden service directories, to make it easier to retire old
26615 authorities. V1 authorities should set "HSAuthoritativeDir 1"
26616 to continue being hidden service authorities too.
26617 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
26619 o Minor features, controller:
26620 - Fix CIRC controller events so that controllers can learn the
26621 identity digests of non-Named servers used in circuit paths.
26622 - Let controllers ask for more useful identifiers for servers. Instead
26623 of learning identity digests for un-Named servers and nicknames
26624 for Named servers, the new identifiers include digest, nickname,
26625 and indication of Named status. Off by default; see control-spec.txt
26626 for more information.
26627 - Add a "getinfo address" controller command so it can display Tor's
26628 best guess to the user.
26629 - New controller event to alert the controller when our server
26630 descriptor has changed.
26631 - Give more meaningful errors on controller authentication failure.
26633 o Minor features, other:
26634 - When asked to resolve a hostname, don't use non-exit servers unless
26635 requested to do so. This allows servers with broken DNS to be
26636 useful to the network.
26637 - Divide eventdns log messages into warn and info messages.
26638 - Reserve the nickname "Unnamed" for routers that can't pick
26639 a hostname: any router can call itself Unnamed; directory
26640 authorities will never allocate Unnamed to any particular router;
26641 clients won't believe that any router is the canonical Unnamed.
26642 - Only include function names in log messages for info/debug messages.
26643 For notice/warn/err, the content of the message should be clear on
26644 its own, and printing the function name only confuses users.
26645 - Avoid some false positives during reachability testing: don't try
26646 to test via a server that's on the same /24 as us.
26647 - If we fail to build a circuit to an intended enclave, and it's
26648 not mandatory that we use that enclave, stop wanting it.
26649 - When eventdns is enabled, allow multithreaded builds on NetBSD and
26650 OpenBSD. (We had previously disabled threads on these platforms
26651 because they didn't have working thread-safe resolver functions.)
26653 o Major bugfixes, anonymity/security:
26654 - If a client asked for a server by name, and there's a named server
26655 in our network-status but we don't have its descriptor yet, we
26656 could return an unnamed server instead.
26657 - Fix NetBSD bug that could allow someone to force uninitialized RAM
26658 to be sent to a server's DNS resolver. This only affects NetBSD
26659 and other platforms that do not bounds-check tolower().
26660 - Reject (most) attempts to use Tor circuits with length one. (If
26661 many people start using Tor as a one-hop proxy, exit nodes become
26662 a more attractive target for compromise.)
26663 - Just because your DirPort is open doesn't mean people should be
26664 able to remotely teach you about hidden service descriptors. Now
26665 only accept rendezvous posts if you've got HSAuthoritativeDir set.
26667 o Major bugfixes, other:
26668 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
26669 - When a client asks the server to resolve (not connect to)
26670 an address, and it has a cached answer, give them the cached answer.
26671 Previously, the server would give them no answer at all.
26672 - Allow really slow clients to not hang up five minutes into their
26673 directory downloads (suggested by Adam J. Richter).
26674 - We were building exactly the wrong circuits when we anticipated
26675 hidden service requirements, meaning Tor would have to build all
26676 its circuits on demand.
26677 - Avoid crashing when we mmap a router cache file of size 0.
26678 - When testing reachability of our DirPort, don't launch new
26679 tests when there's already one in progress -- unreachable
26680 servers were stacking up dozens of testing streams.
26682 o Minor bugfixes, correctness:
26683 - If we're a directory mirror and we ask for "all" network status
26684 documents, we would discard status documents from authorities
26685 we don't recognize.
26686 - Avoid a memory corruption bug when creating a hash table for
26688 - Avoid controller-triggered crash when misusing certain commands
26689 from a v0 controller on platforms that do not handle
26690 printf("%s",NULL) gracefully.
26691 - Don't crash when a controller sends a third argument to an
26692 "extendcircuit" request.
26693 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
26694 response; fix error code when "getinfo dir/status/" fails.
26695 - Avoid crash when telling controller stream-status and a stream
26697 - Patch from Adam Langley to fix assert() in eventdns.c.
26698 - Fix a debug log message in eventdns to say "X resolved to Y"
26699 instead of "X resolved to X".
26700 - Make eventdns give strings for DNS errors, not just error numbers.
26701 - Track unreachable entry guards correctly: don't conflate
26702 'unreachable by us right now' with 'listed as down by the directory
26703 authorities'. With the old code, if a guard was unreachable by
26704 us but listed as running, it would clog our guard list forever.
26705 - Behave correctly in case we ever have a network with more than
26706 2GB/s total advertised capacity.
26707 - Make TrackExitHosts case-insensitive, and fix the behavior of
26708 ".suffix" TrackExitHosts items to avoid matching in the middle of
26710 - Finally fix the openssl warnings from newer gccs that believe that
26711 ignoring a return value is okay, but casting a return value and
26712 then ignoring it is a sign of madness.
26713 - Prevent the contrib/exitlist script from printing the same
26714 result more than once.
26715 - Patch from Steve Hildrey: Generate network status correctly on
26716 non-versioning dirservers.
26717 - Don't listen to the X-Your-Address-Is hint if you did the lookup
26718 via Tor; otherwise you'll think you're the exit node's IP address.
26720 o Minor bugfixes, performance:
26721 - Two small performance improvements on parsing descriptors.
26722 - Major performance improvement on inserting descriptors: change
26723 algorithm from O(n^2) to O(n).
26724 - Make the common memory allocation path faster on machines where
26725 malloc(0) returns a pointer.
26726 - Start remembering X-Your-Address-Is directory hints even if you're
26727 a client, so you can become a server more smoothly.
26728 - Avoid duplicate entries on MyFamily line in server descriptor.
26730 o Packaging, features:
26731 - Remove architecture from OS X builds. The official builds are
26732 now universal binaries.
26733 - The Debian package now uses --verify-config when (re)starting,
26734 to distinguish configuration errors from other errors.
26735 - Update RPMs to require libevent 1.1b.
26737 o Packaging, bugfixes:
26738 - Patches so Tor builds with MinGW on Windows.
26739 - Patches so Tor might run on Cygwin again.
26740 - Resume building on non-gcc compilers and ancient gcc. Resume
26741 building with the -O0 compile flag. Resume building cleanly on
26743 - Run correctly on OS X platforms with case-sensitive filesystems.
26744 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
26745 - Add autoconf checks so Tor can build on Solaris x86 again.
26748 - Documented (and renamed) ServerDNSSearchDomains and
26749 ServerDNSResolvConfFile options.
26750 - Be clearer that the *ListenAddress directives can be repeated
26754 Changes in version 0.1.1.24 - 2006-09-29
26756 - Allow really slow clients to not hang up five minutes into their
26757 directory downloads (suggested by Adam J. Richter).
26758 - Fix major performance regression from 0.1.0.x: instead of checking
26759 whether we have enough directory information every time we want to
26760 do something, only check when the directory information has changed.
26761 This should improve client CPU usage by 25-50%.
26762 - Don't crash if, after a server has been running for a while,
26763 it can't resolve its hostname.
26766 - Allow Tor to start when RunAsDaemon is set but no logs are set.
26767 - Don't crash when the controller receives a third argument to an
26768 "extendcircuit" request.
26769 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
26770 response; fix error code when "getinfo dir/status/" fails.
26771 - Fix configure.in to not produce broken configure files with
26772 more recent versions of autoconf. Thanks to Clint for his auto*
26774 - Fix security bug on NetBSD that could allow someone to force
26775 uninitialized RAM to be sent to a server's DNS resolver. This
26776 only affects NetBSD and other platforms that do not bounds-check
26778 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
26779 methods: these are known to be buggy.
26780 - If we're a directory mirror and we ask for "all" network status
26781 documents, we would discard status documents from authorities
26782 we don't recognize.
26785 Changes in version 0.1.2.1-alpha - 2006-08-27
26787 - Add "eventdns" async dns library from Adam Langley, tweaked to
26788 build on OSX and Windows. Only enabled if you pass the
26789 --enable-eventdns argument to configure.
26790 - Allow servers with no hostname or IP address to learn their
26791 IP address by asking the directory authorities. This code only
26792 kicks in when you would normally have exited with a "no address"
26793 error. Nothing's authenticated, so use with care.
26794 - Rather than waiting a fixed amount of time between retrying
26795 application connections, we wait only 5 seconds for the first,
26796 10 seconds for the second, and 15 seconds for each retry after
26797 that. Hopefully this will improve the expected user experience.
26798 - Patch from Tup to add support for transparent AP connections:
26799 this basically bundles the functionality of trans-proxy-tor
26800 into the Tor mainline. Now hosts with compliant pf/netfilter
26801 implementations can redirect TCP connections straight to Tor
26802 without diverting through SOCKS. Needs docs.
26803 - Busy directory servers save lots of memory by spooling server
26804 descriptors, v1 directories, and v2 networkstatus docs to buffers
26805 as needed rather than en masse. Also mmap the cached-routers
26806 files, so we don't need to keep the whole thing in memory too.
26807 - Automatically avoid picking more than one node from the same
26808 /16 network when constructing a circuit.
26809 - Revise and clean up the torrc.sample that we ship with; add
26810 a section for BandwidthRate and BandwidthBurst.
26813 - Split circuit_t into origin_circuit_t and or_circuit_t, and
26814 split connection_t into edge, or, dir, control, and base structs.
26815 These will save quite a bit of memory on busy servers, and they'll
26816 also help us track down bugs in the code and bugs in the spec.
26817 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
26818 or later. Log when we are doing this, so we can diagnose it when
26819 it fails. (Also, recommend libevent 1.1b for kqueue and
26820 win32 methods; deprecate libevent 1.0b harder; make libevent
26821 recommendation system saner.)
26822 - Start being able to build universal binaries on OS X (thanks
26824 - Export the default exit policy via the control port, so controllers
26825 don't need to guess what it is / will be later.
26826 - Add a man page entry for ProtocolWarnings.
26827 - Add TestVia config option to the man page.
26828 - Remove even more protocol-related warnings from Tor server logs,
26829 such as bad TLS handshakes and malformed begin cells.
26830 - Stop fetching descriptors if you're not a dir mirror and you
26831 haven't tried to establish any circuits lately. [This currently
26832 causes some dangerous behavior, because when you start up again
26833 you'll use your ancient server descriptors.]
26834 - New DirPort behavior: if you have your dirport set, you download
26835 descriptors aggressively like a directory mirror, whether or not
26836 your ORPort is set.
26837 - Get rid of the router_retry_connections notion. Now routers
26838 no longer try to rebuild long-term connections to directory
26839 authorities, and directory authorities no longer try to rebuild
26840 long-term connections to all servers. We still don't hang up
26841 connections in these two cases though -- we need to look at it
26842 more carefully to avoid flapping, and we likely need to wait til
26843 0.1.1.x is obsolete.
26844 - Drop compatibility with obsolete Tors that permit create cells
26845 to have the wrong circ_id_type.
26846 - Re-enable per-connection rate limiting. Get rid of the "OP
26847 bandwidth" concept. Lay groundwork for "bandwidth classes" --
26848 separate global buckets that apply depending on what sort of conn
26850 - Start publishing one minute or so after we find our ORPort
26851 to be reachable. This will help reduce the number of descriptors
26852 we have for ourselves floating around, since it's quite likely
26853 other things (e.g. DirPort) will change during that minute too.
26854 - Fork the v1 directory protocol into its own spec document,
26855 and mark dir-spec.txt as the currently correct (v2) spec.
26858 - When we find our DirPort to be reachable, publish a new descriptor
26859 so we'll tell the world (reported by pnx).
26860 - Publish a new descriptor after we hup/reload. This is important
26861 if our config has changed such that we'll want to start advertising
26862 our DirPort now, etc.
26863 - Allow Tor to start when RunAsDaemon is set but no logs are set.
26864 - When we have a state file we cannot parse, tell the user and
26865 move it aside. Now we avoid situations where the user starts
26866 Tor in 1904, Tor writes a state file with that timestamp in it,
26867 the user fixes her clock, and Tor refuses to start.
26868 - Fix configure.in to not produce broken configure files with
26869 more recent versions of autoconf. Thanks to Clint for his auto*
26871 - "tor --verify-config" now exits with -1(255) or 0 depending on
26872 whether the config options are bad or good.
26873 - Resolve bug 321 when using dnsworkers: append a period to every
26874 address we resolve at the exit node, so that we do not accidentally
26875 pick up local addresses, and so that failing searches are retried
26876 in the resolver search domains. (This is already solved for
26877 eventdns.) (This breaks Blossom servers for now.)
26878 - If we are using an exit enclave and we can't connect, e.g. because
26879 its webserver is misconfigured to not listen on localhost, then
26880 back off and try connecting from somewhere else before we fail.
26883 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
26884 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
26885 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
26886 when the IP address is mapped through MapAddress to a hostname.
26887 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
26888 useless IPv6 DNS resolves.
26889 - Patch suggested by Karsten Loesing: respond to SIGNAL command
26890 before we execute the signal, in case the signal shuts us down.
26891 - Clean up AllowInvalidNodes man page entry.
26892 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
26893 - Add more asserts to track down an assert error on a windows Tor
26894 server with connection_add being called with socket == -1.
26895 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
26896 - Fix misleading log messages: an entry guard that is "unlisted",
26897 as well as not known to be "down" (because we've never heard
26898 of it), is not therefore "up".
26899 - Remove code to special-case "-cvs" ending, since it has not
26900 actually mattered since 0.0.9.
26901 - Make our socks5 handling more robust to broken socks clients:
26902 throw out everything waiting on the buffer in between socks
26903 handshake phases, since they can't possibly (so the theory
26904 goes) have predicted what we plan to respond to them.
26907 Changes in version 0.1.1.23 - 2006-07-30
26909 - Fast Tor servers, especially exit nodes, were triggering asserts
26910 due to a bug in handling the list of pending DNS resolves. Some
26911 bugs still remain here; we're hunting them.
26912 - Entry guards could crash clients by sending unexpected input.
26913 - More fixes on reachability testing: if you find yourself reachable,
26914 then don't ever make any client requests (so you stop predicting
26915 circuits), then hup or have your clock jump, then later your IP
26916 changes, you won't think circuits are working, so you won't try to
26917 test reachability, so you won't publish.
26920 - Avoid a crash if the controller does a resetconf firewallports
26921 and then a setconf fascistfirewall=1.
26922 - Avoid an integer underflow when the dir authority decides whether
26923 a router is stable: we might wrongly label it stable, and compute
26924 a slightly wrong median stability, when a descriptor is published
26926 - Fix a place where we might trigger an assert if we can't build our
26927 own server descriptor yet.
26930 Changes in version 0.1.1.22 - 2006-07-05
26932 - Fix a big bug that was causing servers to not find themselves
26933 reachable if they changed IP addresses. Since only 0.1.1.22+
26934 servers can do reachability testing correctly, now we automatically
26935 make sure to test via one of these.
26936 - Fix to allow clients and mirrors to learn directory info from
26937 descriptor downloads that get cut off partway through.
26938 - Directory authorities had a bug in deciding if a newly published
26939 descriptor was novel enough to make everybody want a copy -- a few
26940 servers seem to be publishing new descriptors many times a minute.
26942 - Fix a rare bug that was causing some servers to complain about
26943 "closing wedged cpuworkers" and skip some circuit create requests.
26944 - Make the Exit flag in directory status documents actually work.
26947 Changes in version 0.1.1.21 - 2006-06-10
26948 o Crash and assert fixes from 0.1.1.20:
26949 - Fix a rare crash on Tor servers that have enabled hibernation.
26950 - Fix a seg fault on startup for Tor networks that use only one
26951 directory authority.
26952 - Fix an assert from a race condition that occurs on Tor servers
26953 while exiting, where various threads are trying to log that they're
26954 exiting, and delete the logs, at the same time.
26955 - Make our unit tests pass again on certain obscure platforms.
26958 - Add support for building SUSE RPM packages.
26959 - Speed up initial bootstrapping for clients: if we are making our
26960 first ever connection to any entry guard, then don't mark it down
26962 - When only one Tor server in the network is labelled as a guard,
26963 and we've already picked him, we would cycle endlessly picking him
26964 again, being unhappy about it, etc. Now we specifically exclude
26965 current guards when picking a new guard.
26966 - Servers send create cells more reliably after the TLS connection
26967 is established: we were sometimes forgetting to send half of them
26968 when we had more than one pending.
26969 - If we get a create cell that asks us to extend somewhere, but the
26970 Tor server there doesn't match the expected digest, we now send
26971 a destroy cell back, rather than silently doing nothing.
26972 - Make options->RedirectExit work again.
26973 - Make cookie authentication for the controller work again.
26974 - Stop being picky about unusual characters in the arguments to
26975 mapaddress. It's none of our business.
26976 - Add a new config option "TestVia" that lets you specify preferred
26977 middle hops to use for test circuits. Perhaps this will let me
26978 debug the reachability problems better.
26980 o Log / documentation fixes:
26981 - If we're a server and some peer has a broken TLS certificate, don't
26982 log about it unless ProtocolWarnings is set, i.e., we want to hear
26983 about protocol violations by others.
26984 - Fix spelling of VirtualAddrNetwork in man page.
26985 - Add a better explanation at the top of the autogenerated torrc file
26986 about what happened to our old torrc.
26989 Changes in version 0.1.1.20 - 2006-05-23
26991 - Downgrade a log severity where servers complain that they're
26993 - Avoid a compile warning on FreeBSD.
26994 - Remove string size limit on NEWDESC messages; solve bug 291.
26995 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
26996 more thoroughly when we're running on windows.
26999 Changes in version 0.1.1.19-rc - 2006-05-03
27001 - Regenerate our local descriptor if it's dirty and we try to use
27002 it locally (e.g. if it changes during reachability detection).
27003 - If we setconf our ORPort to 0, we continued to listen on the
27004 old ORPort and receive connections.
27005 - Avoid a second warning about machine/limits.h on Debian
27007 - Be willing to add our own routerinfo into the routerlist.
27008 Now authorities will include themselves in their directories
27009 and network-statuses.
27010 - Stop trying to upload rendezvous descriptors to every
27011 directory authority: only try the v1 authorities.
27012 - Servers no longer complain when they think they're not
27013 registered with the directory authorities. There were too many
27015 - Backport dist-rpm changes so rpms can be built without errors.
27018 - Implement an option, VirtualAddrMask, to set which addresses
27019 get handed out in response to mapaddress requests. This works
27020 around a bug in tsocks where 127.0.0.0/8 is never socksified.
27023 Changes in version 0.1.1.18-rc - 2006-04-10
27025 - Work harder to download live network-statuses from all the
27026 directory authorities we know about. Improve the threshold
27027 decision logic so we're more robust to edge cases.
27028 - When fetching rendezvous descriptors, we were willing to ask
27029 v2 authorities too, which would always return 404.
27032 - Stop listing down or invalid nodes in the v1 directory. This will
27033 reduce its bulk by about 1/3, and reduce load on directory
27035 - When deciding whether a router is Fast or Guard-worthy, consider
27036 his advertised BandwidthRate and not just the BandwidthCapacity.
27037 - No longer ship INSTALL and README files -- they are useless now.
27038 - Force rpmbuild to behave and honor target_cpu.
27039 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
27040 - Start to include translated versions of the tor-doc-*.html
27041 files, along with the screenshots. Still needs more work.
27042 - Start sending back 512 and 451 errors if mapaddress fails,
27043 rather than not sending anything back at all.
27044 - When we fail to bind or listen on an incoming or outgoing
27045 socket, we should close it before failing. otherwise we just
27046 leak it. (thanks to weasel for finding.)
27047 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
27048 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
27049 - Make NoPublish (even though deprecated) work again.
27050 - Fix a minor security flaw where a versioning auth dirserver
27051 could list a recommended version many times in a row to make
27052 clients more convinced that it's recommended.
27053 - Fix crash bug if there are two unregistered servers running
27054 with the same nickname, one of them is down, and you ask for
27055 them by nickname in your EntryNodes or ExitNodes. Also, try
27056 to pick the one that's running rather than an arbitrary one.
27057 - Fix an infinite loop we could hit if we go offline for too long.
27058 - Complain when we hit WSAENOBUFS on recv() or write() too.
27059 Perhaps this will help us hunt the bug.
27060 - If you're not a versioning dirserver, don't put the string
27061 "client-versions \nserver-versions \n" in your network-status.
27062 - Lower the minimum required number of file descriptors to 1000,
27063 so we can have some overhead for Valgrind on Linux, where the
27064 default ulimit -n is 1024.
27067 - Add tor.dizum.com as the fifth authoritative directory server.
27068 - Add a new config option FetchUselessDescriptors, off by default,
27069 for when you plan to run "exitlist" on your client and you want
27070 to know about even the non-running descriptors.
27073 Changes in version 0.1.1.17-rc - 2006-03-28
27075 - Clients and servers since 0.1.1.10-alpha have been expiring
27076 connections whenever they are idle for 5 minutes and they *do*
27077 have circuits on them. Oops. With this new version, clients will
27078 discard their previous entry guard choices and avoid choosing
27079 entry guards running these flawed versions.
27080 - Fix memory leak when uncompressing concatenated zlib streams. This
27081 was causing substantial leaks over time on Tor servers.
27082 - The v1 directory was including servers as much as 48 hours old,
27083 because that's how the new routerlist->routers works. Now only
27084 include them if they're 20 hours old or less.
27087 - Resume building on irix64, netbsd 2.0, etc.
27088 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
27090 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
27091 and it is confusing some users.
27092 - Mirrors stop caching the v1 directory so often.
27093 - Make the max number of old descriptors that a cache will hold
27094 rise with the number of directory authorities, so we can scale.
27095 - Change our win32 uname() hack to be more forgiving about what
27096 win32 versions it thinks it's found.
27099 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
27101 - When the controller's *setconf commands fail, collect an error
27102 message in a string and hand it back to the controller.
27103 - Make the v2 dir's "Fast" flag based on relative capacity, just
27104 like "Stable" is based on median uptime. Name everything in the
27105 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
27106 - Log server fingerprint on startup, so new server operators don't
27107 have to go hunting around their filesystem for it.
27108 - Return a robots.txt on our dirport to discourage google indexing.
27109 - Let the controller ask for GETINFO dir/status/foo so it can ask
27110 directly rather than connecting to the dir port. Only works when
27111 dirport is set for now.
27113 o New config options rather than constants in the code:
27114 - SocksTimeout: How long do we let a socks connection wait
27115 unattached before we fail it?
27116 - CircuitBuildTimeout: Cull non-open circuits that were born
27117 at least this many seconds ago.
27118 - CircuitIdleTimeout: Cull open clean circuits that were born
27119 at least this many seconds ago.
27122 Changes in version 0.1.1.16-rc - 2006-03-18
27123 o Bugfixes on 0.1.1.15-rc:
27124 - Fix assert when the controller asks to attachstream a connect-wait
27125 or resolve-wait stream.
27126 - Now do address rewriting when the controller asks us to attach
27127 to a particular circuit too. This will let Blossom specify
27128 "moria2.exit" without having to learn what moria2's IP address is.
27129 - Make the "tor --verify-config" command-line work again, so people
27130 can automatically check if their torrc will parse.
27131 - Authoritative dirservers no longer require an open connection from
27132 a server to consider him "reachable". We need this change because
27133 when we add new auth dirservers, old servers won't know not to
27135 - Let Tor build on Sun CC again.
27136 - Fix an off-by-one buffer size in dirserv.c that magically never
27137 hit our three authorities but broke sjmurdoch's own tor network.
27138 - If we as a directory mirror don't know of any v1 directory
27139 authorities, then don't try to cache any v1 directories.
27140 - Stop warning about unknown servers in our family when they are
27141 given as hex digests.
27142 - Stop complaining as quickly to the server operator that he
27143 hasn't registered his nickname/key binding.
27144 - Various cleanups so we can add new V2 Auth Dirservers.
27145 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
27146 reflect the updated flags in our v2 dir protocol.
27147 - Resume allowing non-printable characters for exit streams (both
27148 for connecting and for resolving). Now we tolerate applications
27149 that don't follow the RFCs. But continue to block malformed names
27152 o Bugfixes on 0.1.0.x:
27153 - Fix assert bug in close_logs(): when we close and delete logs,
27154 remove them all from the global "logfiles" list.
27155 - Fix minor integer overflow in calculating when we expect to use up
27156 our bandwidth allocation before hibernating.
27157 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
27158 there are multiple SSLs installed with different versions.
27159 - When we try to be a server and Address is not explicitly set and
27160 our hostname resolves to a private IP address, try to use an
27161 interface address if it has a public address. Now Windows machines
27162 that think of themselves as localhost can work by default.
27165 - Let the controller ask for GETINFO dir/server/foo so it can ask
27166 directly rather than connecting to the dir port.
27167 - Let the controller tell us about certain router descriptors
27168 that it doesn't want Tor to use in circuits. Implement
27169 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
27170 - New config option SafeSocks to reject all application connections
27171 using unsafe socks protocols. Defaults to off.
27174 Changes in version 0.1.1.15-rc - 2006-03-11
27175 o Bugfixes and cleanups:
27176 - When we're printing strings from the network, don't try to print
27177 non-printable characters. This protects us against shell escape
27178 sequence exploits, and also against attacks to fool humans into
27179 misreading their logs.
27180 - Fix a bug where Tor would fail to establish any connections if you
27181 left it off for 24 hours and then started it: we were happy with
27182 the obsolete network statuses, but they all referred to router
27183 descriptors that were too old to fetch, so we ended up with no
27184 valid router descriptors.
27185 - Fix a seg fault in the controller's "getinfo orconn-status"
27186 command while listing status on incoming handshaking connections.
27187 Introduce a status name "NEW" for these connections.
27188 - If we get a linelist or linelist_s config option from the torrc
27189 (e.g. ExitPolicy) and it has no value, warn and skip rather than
27190 silently resetting it to its default.
27191 - Don't abandon entry guards until they've been down or gone for
27193 - Cleaner and quieter log messages.
27196 - New controller signal NEWNYM that makes new application requests
27197 use clean circuits.
27198 - Add a new circuit purpose 'controller' to let the controller ask
27199 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
27200 controller command to let you specify the purpose if you're
27201 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
27202 command to let you change a circuit's purpose after it's been
27204 - Accept "private:*" in routerdesc exit policies; not generated yet
27205 because older Tors do not understand it.
27206 - Add BSD-style contributed startup script "rc.subr" from Peter
27210 Changes in version 0.1.1.14-alpha - 2006-02-20
27211 o Bugfixes on 0.1.1.x:
27212 - Don't die if we ask for a stdout or stderr log (even implicitly)
27213 and we're set to RunAsDaemon -- just warn.
27214 - We still had a few bugs in the OR connection rotation code that
27215 caused directory servers to slowly aggregate connections to other
27216 fast Tor servers. This time for sure!
27217 - Make log entries on Win32 include the name of the function again.
27218 - We were treating a pair of exit policies if they were equal even
27219 if one said accept and the other said reject -- causing us to
27220 not always publish a new descriptor since we thought nothing
27222 - Retry pending server downloads as well as pending networkstatus
27223 downloads when we unexpectedly get a socks request.
27224 - We were ignoring the IS_FAST flag in the directory status,
27225 meaning we were willing to pick trivial-bandwidth nodes for "fast"
27227 - If the controller's SAVECONF command fails (e.g. due to file
27228 permissions), let the controller know that it failed.
27231 - If we're trying to be a Tor server and running Windows 95/98/ME
27232 as a server, explain that we'll likely crash.
27233 - When we're a server, a client asks for an old-style directory,
27234 and our write bucket is empty, don't give it to him. This way
27235 small servers can continue to serve the directory *sometimes*,
27236 without getting overloaded.
27237 - Compress exit policies even more -- look for duplicate lines
27239 - Clients now honor the "guard" flag in the router status when
27240 picking entry guards, rather than looking at is_fast or is_stable.
27241 - Retain unrecognized lines in $DATADIR/state file, so that we can
27242 be forward-compatible.
27243 - Generate 18.0.0.0/8 address policy format in descs when we can;
27244 warn when the mask is not reducible to a bit-prefix.
27245 - Let the user set ControlListenAddress in the torrc. This can be
27246 dangerous, but there are some cases (like a secured LAN) where it
27248 - Split ReachableAddresses into ReachableDirAddresses and
27249 ReachableORAddresses, so we can restrict Dir conns to port 80
27250 and OR conns to port 443.
27251 - Now we can target arch and OS in rpm builds (contributed by
27252 Phobos). Also make the resulting dist-rpm filename match the
27254 - New config options to help controllers: FetchServerDescriptors
27255 and FetchHidServDescriptors for whether to fetch server
27256 info and hidserv info or let the controller do it, and
27257 PublishServerDescriptor and PublishHidServDescriptors.
27258 - Also let the controller set the __AllDirActionsPrivate config
27259 option if you want all directory fetches/publishes to happen via
27260 Tor (it assumes your controller bootstraps your circuits).
27263 Changes in version 0.1.0.17 - 2006-02-17
27264 o Crash bugfixes on 0.1.0.x:
27265 - When servers with a non-zero DirPort came out of hibernation,
27266 sometimes they would trigger an assert.
27268 o Other important bugfixes:
27269 - On platforms that don't have getrlimit (like Windows), we were
27270 artificially constraining ourselves to a max of 1024
27271 connections. Now just assume that we can handle as many as 15000
27272 connections. Hopefully this won't cause other problems.
27274 o Backported features:
27275 - When we're a server, a client asks for an old-style directory,
27276 and our write bucket is empty, don't give it to him. This way
27277 small servers can continue to serve the directory *sometimes*,
27278 without getting overloaded.
27279 - Whenever you get a 503 in response to a directory fetch, try
27280 once more. This will become important once servers start sending
27281 503's whenever they feel busy.
27282 - Fetch a new directory every 120 minutes, not every 40 minutes.
27283 Now that we have hundreds of thousands of users running the old
27284 directory algorithm, it's starting to hurt a lot.
27285 - Bump up the period for forcing a hidden service descriptor upload
27286 from 20 minutes to 1 hour.
27289 Changes in version 0.1.1.13-alpha - 2006-02-09
27290 o Crashes in 0.1.1.x:
27291 - When you tried to setconf ORPort via the controller, Tor would
27292 crash. So people using TorCP to become a server were sad.
27293 - Solve (I hope) the stack-smashing bug that we were seeing on fast
27294 servers. The problem appears to be something do with OpenSSL's
27295 random number generation, or how we call it, or something. Let me
27296 know if the crashes continue.
27297 - Turn crypto hardware acceleration off by default, until we find
27298 somebody smart who can test it for us. (It appears to produce
27299 seg faults in at least some cases.)
27300 - Fix a rare assert error when we've tried all intro points for
27301 a hidden service and we try fetching the service descriptor again:
27302 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
27305 - Fix a major load balance bug: we were round-robining in 16 KB
27306 chunks, and servers with bandwidthrate of 20 KB, while downloading
27307 a 600 KB directory, would starve their other connections. Now we
27308 try to be a bit more fair.
27309 - Dir authorities and mirrors were never expiring the newest
27310 descriptor for each server, causing memory and directory bloat.
27311 - Fix memory-bloating and connection-bloating bug on servers: We
27312 were never closing any connection that had ever had a circuit on
27313 it, because we were checking conn->n_circuits == 0, yet we had a
27314 bug that let it go negative.
27315 - Make Tor work using squid as your http proxy again -- squid
27316 returns an error if you ask for a URL that's too long, and it uses
27317 a really generic error message. Plus, many people are behind a
27318 transparent squid so they don't even realize it.
27319 - On platforms that don't have getrlimit (like Windows), we were
27320 artificially constraining ourselves to a max of 1024
27321 connections. Now just assume that we can handle as many as 15000
27322 connections. Hopefully this won't cause other problems.
27323 - Add a new config option ExitPolicyRejectPrivate which defaults to
27324 1. This means all exit policies will begin with rejecting private
27325 addresses, unless the server operator explicitly turns it off.
27328 - Clients no longer download descriptors for non-running
27330 - Before we add new directory authorities, we should make it
27331 clear that only v1 authorities should receive/publish hidden
27332 service descriptors.
27335 - As soon as we've fetched some more directory info, immediately
27336 try to download more server descriptors. This way we don't have
27337 a 10 second pause during initial bootstrapping.
27338 - Remove even more loud log messages that the server operator can't
27340 - When we're running an obsolete or un-recommended version, make
27341 the log message more clear about what the problem is and what
27342 versions *are* still recommended.
27343 - Provide a more useful warn message when our onion queue gets full:
27344 the CPU is too slow or the exit policy is too liberal.
27345 - Don't warn when we receive a 503 from a dirserver/cache -- this
27346 will pave the way for them being able to refuse if they're busy.
27347 - When we fail to bind a listener, try to provide a more useful
27348 log message: e.g., "Is Tor already running?"
27349 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
27350 Goldberg can prove things about our handshake protocol more
27352 - MaxConn has been obsolete for a while now. Document the ConnLimit
27353 config option, which is a *minimum* number of file descriptors
27354 that must be available else Tor refuses to start.
27355 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
27356 if you log to syslog and want something other than LOG_DAEMON.
27357 - Make dirservers generate a separate "guard" flag to mean,
27358 "would make a good entry guard". Make clients parse it and vote
27359 on it. Not used by clients yet.
27360 - Implement --with-libevent-dir option to ./configure. Also, improve
27361 search techniques to find libevent, and use those for openssl too.
27362 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
27363 - Only start testing reachability once we've established a
27364 circuit. This will make startup on dirservers less noisy.
27365 - Don't try to upload hidden service descriptors until we have
27366 established a circuit.
27367 - Fix the controller's "attachstream 0" command to treat conn like
27368 it just connected, doing address remapping, handling .exit and
27369 .onion idioms, and so on. Now we're more uniform in making sure
27370 that the controller hears about new and closing connections.
27373 Changes in version 0.1.1.12-alpha - 2006-01-11
27374 o Bugfixes on 0.1.1.x:
27375 - The fix to close duplicate server connections was closing all
27376 Tor client connections if they didn't establish a circuit
27377 quickly enough. Oops.
27378 - Fix minor memory issue (double-free) that happened on exit.
27380 o Bugfixes on 0.1.0.x:
27381 - Tor didn't warn when it failed to open a log file.
27384 Changes in version 0.1.1.11-alpha - 2006-01-10
27385 o Crashes in 0.1.1.x:
27386 - Include all the assert/crash fixes from 0.1.0.16.
27387 - If you start Tor and then quit very quickly, there were some
27388 races that tried to free things that weren't allocated yet.
27389 - Fix a rare memory stomp if you're running hidden services.
27390 - Fix segfault when specifying DirServer in config without nickname.
27391 - Fix a seg fault when you finish connecting to a server but at
27392 that moment you dump his server descriptor.
27393 - Extendcircuit and Attachstream controller commands would
27394 assert/crash if you don't give them enough arguments.
27395 - Fix an assert error when we're out of space in the connection_list
27396 and we try to post a hidden service descriptor (reported by weasel).
27397 - If you specify a relative torrc path and you set RunAsDaemon in
27398 your torrc, then it chdir()'s to the new directory. If you HUP,
27399 it tries to load the new torrc location, fails, and exits.
27400 The fix: no longer allow a relative path to torrc using -f.
27403 - Implement "entry guards": automatically choose a handful of entry
27404 nodes and stick with them for all circuits. Only pick new guards
27405 when the ones you have are unsuitable, and if the old guards
27406 become suitable again, switch back. This will increase security
27407 dramatically against certain end-point attacks. The EntryNodes
27408 config option now provides some hints about which entry guards you
27409 want to use most; and StrictEntryNodes means to only use those.
27410 - New directory logic: download by descriptor digest, not by
27411 fingerprint. Caches try to download all listed digests from
27412 authorities; clients try to download "best" digests from caches.
27413 This avoids partitioning and isolating attacks better.
27414 - Make the "stable" router flag in network-status be the median of
27415 the uptimes of running valid servers, and make clients pay
27416 attention to the network-status flags. Thus the cutoff adapts
27417 to the stability of the network as a whole, making IRC, IM, etc
27418 connections more reliable.
27421 - Tor servers with dynamic IP addresses were needing to wait 18
27422 hours before they could start doing reachability testing using
27423 the new IP address and ports. This is because they were using
27424 the internal descriptor to learn what to test, yet they were only
27425 rebuilding the descriptor once they decided they were reachable.
27426 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
27427 to download certain server descriptors, throw them away, and then
27428 fetch them again after 30 minutes. Now mirrors throw away these
27429 server descriptors so clients can't get them.
27430 - We were leaving duplicate connections to other ORs open for a week,
27431 rather than closing them once we detect a duplicate. This only
27432 really affected authdirservers, but it affected them a lot.
27433 - Spread the authdirservers' reachability testing over the entire
27434 testing interval, so we don't try to do 500 TLS's at once every
27438 - If the network is down, and we try to connect to a conn because
27439 we have a circuit in mind, and we timeout (30 seconds) because the
27440 network never answers, we were expiring the circuit, but we weren't
27441 obsoleting the connection or telling the entry_guards functions.
27442 - Some Tor servers process billions of cells per day. These statistics
27443 need to be uint64_t's.
27444 - Check for integer overflows in more places, when adding elements
27445 to smartlists. This could possibly prevent a buffer overflow
27446 on malicious huge inputs. I don't see any, but I haven't looked
27448 - ReachableAddresses kept growing new "reject *:*" lines on every
27450 - When you "setconf log" via the controller, it should remove all
27451 logs. We were automatically adding back in a "log notice stdout".
27452 - Newly bootstrapped Tor networks couldn't establish hidden service
27453 circuits until they had nodes with high uptime. Be more tolerant.
27454 - We were marking servers down when they could not answer every piece
27455 of the directory request we sent them. This was far too harsh.
27456 - Fix the torify (tsocks) config file to not use Tor for localhost
27458 - Directory authorities now go to the proper authority when asking for
27459 a networkstatus, even when they want a compressed one.
27460 - Fix a harmless bug that was causing Tor servers to log
27461 "Got an end because of misc error, but we're not an AP. Closing."
27462 - Authorities were treating their own descriptor changes as cosmetic,
27463 meaning the descriptor available in the network-status and the
27464 descriptor that clients downloaded were different.
27465 - The OS X installer was adding a symlink for tor_resolve but
27466 the binary was called tor-resolve (reported by Thomas Hardly).
27467 - Workaround a problem with some http proxies where they refuse GET
27468 requests that specify "Content-Length: 0" (reported by Adrian).
27469 - Fix wrong log message when you add a "HiddenServiceNodes" config
27470 line without any HiddenServiceDir line (reported by Chris Thomas).
27473 - Write the TorVersion into the state file so we have a prayer of
27474 keeping forward and backward compatibility.
27475 - Revive the FascistFirewall config option rather than eliminating it:
27476 now it's a synonym for ReachableAddresses *:80,*:443.
27477 - Clients choose directory servers from the network status lists,
27478 not from their internal list of router descriptors. Now they can
27479 go to caches directly rather than needing to go to authorities
27481 - Directory authorities ignore router descriptors that have only
27482 cosmetic differences: do this for 0.1.0.x servers now too.
27483 - Add a new flag to network-status indicating whether the server
27484 can answer v2 directory requests too.
27485 - Authdirs now stop whining so loudly about bad descriptors that
27486 they fetch from other dirservers. So when there's a log complaint,
27487 it's for sure from a freshly uploaded descriptor.
27488 - Reduce memory requirements in our structs by changing the order
27490 - There used to be two ways to specify your listening ports in a
27491 server descriptor: on the "router" line and with a separate "ports"
27492 line. Remove support for the "ports" line.
27493 - New config option "AuthDirRejectUnlisted" for auth dirservers as
27494 a panic button: if we get flooded with unusable servers we can
27495 revert to only listing servers in the approved-routers file.
27496 - Auth dir servers can now mark a fingerprint as "!reject" or
27497 "!invalid" in the approved-routers file (as its nickname), to
27498 refuse descriptors outright or include them but marked as invalid.
27499 - Servers store bandwidth history across restarts/crashes.
27500 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
27501 get a better idea of why their circuits failed. Not used yet.
27502 - Directory mirrors now cache up to 16 unrecognized network-status
27503 docs. Now we can add new authdirservers and they'll be cached too.
27504 - When picking a random directory, prefer non-authorities if any
27506 - New controller option "getinfo desc/all-recent" to fetch the
27507 latest server descriptor for every router that Tor knows about.
27510 Changes in version 0.1.0.16 - 2006-01-02
27511 o Crash bugfixes on 0.1.0.x:
27512 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
27513 corrupting the heap, losing FDs, or crashing when we need to resize
27514 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
27515 - It turns out sparc64 platforms crash on unaligned memory access
27516 too -- so detect and avoid this.
27517 - Handle truncated compressed data correctly (by detecting it and
27519 - Fix possible-but-unlikely free(NULL) in control.c.
27520 - When we were closing connections, there was a rare case that
27521 stomped on memory, triggering seg faults and asserts.
27522 - Avoid potential infinite recursion when building a descriptor. (We
27523 don't know that it ever happened, but better to fix it anyway.)
27524 - We were neglecting to unlink marked circuits from soon-to-close OR
27525 connections, which caused some rare scribbling on freed memory.
27526 - Fix a memory stomping race bug when closing the joining point of two
27527 rendezvous circuits.
27528 - Fix an assert in time parsing found by Steven Murdoch.
27530 o Other bugfixes on 0.1.0.x:
27531 - When we're doing reachability testing, provide more useful log
27532 messages so the operator knows what to expect.
27533 - Do not check whether DirPort is reachable when we are suppressing
27534 advertising it because of hibernation.
27535 - When building with -static or on Solaris, we sometimes needed -ldl.
27536 - When we're deciding whether a stream has enough circuits around
27537 that can handle it, count the freshly dirty ones and not the ones
27538 that are so dirty they won't be able to handle it.
27539 - When we're expiring old circuits, we had a logic error that caused
27540 us to close new rendezvous circuits rather than old ones.
27541 - Give a more helpful log message when you try to change ORPort via
27542 the controller: you should upgrade Tor if you want that to work.
27543 - We were failing to parse Tor versions that start with "Tor ".
27544 - Tolerate faulty streams better: when a stream fails for reason
27545 exitpolicy, stop assuming that the router is lying about his exit
27546 policy. When a stream fails for reason misc, allow it to retry just
27547 as if it was resolvefailed. When a stream has failed three times,
27548 reset its failure count so we can try again and get all three tries.
27551 Changes in version 0.1.1.10-alpha - 2005-12-11
27552 o Correctness bugfixes on 0.1.0.x:
27553 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
27554 corrupting the heap, losing FDs, or crashing when we need to resize
27555 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
27556 - Stop doing the complex voodoo overkill checking for insecure
27557 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
27558 - When we were closing connections, there was a rare case that
27559 stomped on memory, triggering seg faults and asserts.
27560 - We were neglecting to unlink marked circuits from soon-to-close OR
27561 connections, which caused some rare scribbling on freed memory.
27562 - When we're deciding whether a stream has enough circuits around
27563 that can handle it, count the freshly dirty ones and not the ones
27564 that are so dirty they won't be able to handle it.
27565 - Recover better from TCP connections to Tor servers that are
27566 broken but don't tell you (it happens!); and rotate TLS
27567 connections once a week.
27568 - When we're expiring old circuits, we had a logic error that caused
27569 us to close new rendezvous circuits rather than old ones.
27570 - Fix a scary-looking but apparently harmless bug where circuits
27571 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
27572 servers, and never switch to state CIRCUIT_STATE_OPEN.
27573 - When building with -static or on Solaris, we sometimes needed to
27575 - Give a useful message when people run Tor as the wrong user,
27576 rather than telling them to start chowning random directories.
27577 - We were failing to inform the controller about new .onion streams.
27579 o Security bugfixes on 0.1.0.x:
27580 - Refuse server descriptors if the fingerprint line doesn't match
27581 the included identity key. Tor doesn't care, but other apps (and
27582 humans) might actually be trusting the fingerprint line.
27583 - We used to kill the circuit when we receive a relay command we
27584 don't recognize. Now we just drop it.
27585 - Start obeying our firewall options more rigorously:
27586 . If we can't get to a dirserver directly, try going via Tor.
27587 . Don't ever try to connect (as a client) to a place our
27588 firewall options forbid.
27589 . If we specify a proxy and also firewall options, obey the
27590 firewall options even when we're using the proxy: some proxies
27591 can only proxy to certain destinations.
27592 - Fix a bug found by Lasse Overlier: when we were making internal
27593 circuits (intended to be cannibalized later for rendezvous and
27594 introduction circuits), we were picking them so that they had
27595 useful exit nodes. There was no need for this, and it actually
27596 aids some statistical attacks.
27597 - Start treating internal circuits and exit circuits separately.
27598 It's important to keep them separate because internal circuits
27599 have their last hops picked like middle hops, rather than like
27600 exit hops. So exiting on them will break the user's expectations.
27602 o Bugfixes on 0.1.1.x:
27603 - Take out the mis-feature where we tried to detect IP address
27604 flapping for people with DynDNS, and chose not to upload a new
27605 server descriptor sometimes.
27606 - Try to be compatible with OpenSSL 0.9.6 again.
27607 - Log fix: when the controller is logging about .onion addresses,
27608 sometimes it didn't include the ".onion" part of the address.
27609 - Don't try to modify options->DirServers internally -- if the
27610 user didn't specify any, just add the default ones directly to
27611 the trusted dirserver list. This fixes a bug where people running
27612 controllers would use SETCONF on some totally unrelated config
27613 option, and Tor would start yelling at them about changing their
27615 - Let the controller's redirectstream command specify a port, in
27616 case the controller wants to change that too.
27617 - When we requested a pile of server descriptors, we sometimes
27618 accidentally launched a duplicate request for the first one.
27619 - Bugfix for trackhostexits: write down the fingerprint of the
27620 chosen exit, not its nickname, because the chosen exit might not
27622 - When parsing foo.exit, if foo is unknown, and we are leaving
27623 circuits unattached, set the chosen_exit field and leave the
27624 address empty. This matters because controllers got confused
27626 - Directory authorities no longer try to download server
27627 descriptors that they know they will reject.
27629 o Features and updates:
27630 - Replace balanced trees with hash tables: this should make stuff
27631 significantly faster.
27632 - Resume using the AES counter-mode implementation that we ship,
27633 rather than OpenSSL's. Ours is significantly faster.
27634 - Many other CPU and memory improvements.
27635 - Add a new config option FastFirstHopPK (on by default) so clients
27636 do a trivial crypto handshake for their first hop, since TLS has
27637 already taken care of confidentiality and authentication.
27638 - Add a new config option TestSocks so people can see if their
27639 applications are using socks4, socks4a, socks5-with-ip, or
27640 socks5-with-hostname. This way they don't have to keep mucking
27641 with tcpdump and wondering if something got cached somewhere.
27642 - Warn when listening on a public address for socks. I suspect a
27643 lot of people are setting themselves up as open socks proxies,
27644 and they have no idea that jerks on the Internet are using them,
27645 since they simply proxy the traffic into the Tor network.
27646 - Add "private:*" as an alias in configuration for policies. Now
27647 you can simplify your exit policy rather than needing to list
27648 every single internal or nonroutable network space.
27649 - Add a new controller event type that allows controllers to get
27650 all server descriptors that were uploaded to a router in its role
27651 as authoritative dirserver.
27652 - Start shipping socks-extensions.txt, tor-doc-unix.html,
27653 tor-doc-server.html, and stylesheet.css in the tarball.
27654 - Stop shipping tor-doc.html in the tarball.
27657 Changes in version 0.1.1.9-alpha - 2005-11-15
27658 o Usability improvements:
27659 - Start calling it FooListenAddress rather than FooBindAddress,
27660 since few of our users know what it means to bind an address
27662 - Reduce clutter in server logs. We're going to try to make
27663 them actually usable now. New config option ProtocolWarnings that
27664 lets you hear about how _other Tors_ are breaking the protocol. Off
27666 - Divide log messages into logging domains. Once we put some sort
27667 of interface on this, it will let people looking at more verbose
27668 log levels specify the topics they want to hear more about.
27669 - Make directory servers return better http 404 error messages
27670 instead of a generic "Servers unavailable".
27671 - Check for even more Windows version flags when writing the platform
27672 string in server descriptors, and note any we don't recognize.
27673 - Clean up more of the OpenSSL memory when exiting, so we can detect
27674 memory leaks better.
27675 - Make directory authorities be non-versioning, non-naming by
27676 default. Now we can add new directory servers without requiring
27677 their operators to pay close attention.
27678 - When logging via syslog, include the pid whenever we provide
27679 a log entry. Suggested by Todd Fries.
27681 o Performance improvements:
27682 - Directory servers now silently throw away new descriptors that
27683 haven't changed much if the timestamps are similar. We do this to
27684 tolerate older Tor servers that upload a new descriptor every 15
27685 minutes. (It seemed like a good idea at the time.)
27686 - Inline bottleneck smartlist functions; use fast versions by default.
27687 - Add a "Map from digest to void*" abstraction digestmap_t so we
27688 can do less hex encoding/decoding. Use it in router_get_by_digest()
27689 to resolve a performance bottleneck.
27690 - Allow tor_gzip_uncompress to extract as much as possible from
27691 truncated compressed data. Try to extract as many
27692 descriptors as possible from truncated http responses (when
27693 DIR_PURPOSE_FETCH_ROUTERDESC).
27694 - Make circ->onionskin a pointer, not a static array. moria2 was using
27695 125000 circuit_t's after it had been up for a few weeks, which
27696 translates to 20+ megs of wasted space.
27697 - The private half of our EDH handshake keys are now chosen out
27698 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
27700 o Security improvements:
27701 - Start making directory caches retain old routerinfos, so soon
27702 clients can start asking by digest of descriptor rather than by
27703 fingerprint of server.
27704 - Add half our entropy from RAND_poll in OpenSSL. This knows how
27705 to use egd (if present), openbsd weirdness (if present), vms/os2
27706 weirdness (if we ever port there), and more in the future.
27708 o Bugfixes on 0.1.0.x:
27709 - Do round-robin writes of at most 16 kB per write. This might be
27710 more fair on loaded Tor servers, and it might resolve our Windows
27711 crash bug. It might also slow things down.
27712 - Our TLS handshakes were generating a single public/private
27713 keypair for the TLS context, rather than making a new one for
27714 each new connections. Oops. (But we were still rotating them
27715 periodically, so it's not so bad.)
27716 - When we were cannibalizing a circuit with a particular exit
27717 node in mind, we weren't checking to see if that exit node was
27718 already present earlier in the circuit. Oops.
27719 - When a Tor server's IP changes (e.g. from a dyndns address),
27720 upload a new descriptor so clients will learn too.
27721 - Really busy servers were keeping enough circuits open on stable
27722 connections that they were wrapping around the circuit_id
27723 space. (It's only two bytes.) This exposed a bug where we would
27724 feel free to reuse a circuit_id even if it still exists but has
27725 been marked for close. Try to fix this bug. Some bug remains.
27726 - If we would close a stream early (e.g. it asks for a .exit that
27727 we know would refuse it) but the LeaveStreamsUnattached config
27728 option is set by the controller, then don't close it.
27730 o Bugfixes on 0.1.1.8-alpha:
27731 - Fix a big pile of memory leaks, some of them serious.
27732 - Do not try to download a routerdesc if we would immediately reject
27734 - Resume inserting a newline between all router descriptors when
27735 generating (old style) signed directories, since our spec says
27737 - When providing content-type application/octet-stream for
27738 server descriptors using .z, we were leaving out the
27739 content-encoding header. Oops. (Everything tolerated this just
27740 fine, but that doesn't mean we need to be part of the problem.)
27741 - Fix a potential seg fault in getconf and getinfo using version 1
27742 of the controller protocol.
27743 - Avoid crash: do not check whether DirPort is reachable when we
27744 are suppressing it because of hibernation.
27745 - Make --hash-password not crash on exit.
27748 Changes in version 0.1.1.8-alpha - 2005-10-07
27749 o New features (major):
27750 - Clients don't download or use the directory anymore. Now they
27751 download and use network-statuses from the trusted dirservers,
27752 and fetch individual server descriptors as needed from mirrors.
27753 See dir-spec.txt for all the gory details.
27754 - Be more conservative about whether to advertise our DirPort.
27755 The main change is to not advertise if we're running at capacity
27756 and either a) we could hibernate or b) our capacity is low and
27757 we're using a default DirPort.
27758 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
27760 o New features (minor):
27761 - Try to be smart about when to retry network-status and
27762 server-descriptor fetches. Still needs some tuning.
27763 - Stop parsing, storing, or using running-routers output (but
27764 mirrors still cache and serve it).
27765 - Consider a threshold of versioning dirservers (dirservers who have
27766 an opinion about which Tor versions are still recommended) before
27767 deciding whether to warn the user that he's obsolete.
27768 - Dirservers can now reject/invalidate by key and IP, with the
27769 config options "AuthDirInvalid" and "AuthDirReject". This is
27770 useful since currently we automatically list servers as running
27771 and usable even if we know they're jerks.
27772 - Provide dire warnings to any users who set DirServer; move it out
27773 of torrc.sample and into torrc.complete.
27774 - Add MyFamily to torrc.sample in the server section.
27775 - Add nicknames to the DirServer line, so we can refer to them
27776 without requiring all our users to memorize their IP addresses.
27777 - When we get an EOF or a timeout on a directory connection, note
27778 how many bytes of serverdesc we are dropping. This will help
27779 us determine whether it is smart to parse incomplete serverdesc
27781 - Add a new function to "change pseudonyms" -- that is, to stop
27782 using any currently-dirty circuits for new streams, so we don't
27783 link new actions to old actions. Currently it's only called on
27784 HUP (or SIGNAL RELOAD).
27785 - On sighup, if UseHelperNodes changed to 1, use new circuits.
27786 - Start using RAND_bytes rather than RAND_pseudo_bytes from
27787 OpenSSL. Also, reseed our entropy every hour, not just at
27788 startup. And entropy in 512-bit chunks, not 160-bit chunks.
27790 o Fixes on 0.1.1.7-alpha:
27791 - Nobody ever implemented EVENT_ADDRMAP for control protocol
27792 version 0, so don't let version 0 controllers ask for it.
27793 - If you requested something with too many newlines via the
27794 v1 controller protocol, you could crash tor.
27795 - Fix a number of memory leaks, including some pretty serious ones.
27796 - Re-enable DirPort testing again, so Tor servers will be willing
27797 to advertise their DirPort if it's reachable.
27798 - On TLS handshake, only check the other router's nickname against
27799 its expected nickname if is_named is set.
27801 o Fixes forward-ported from 0.1.0.15:
27802 - Don't crash when we don't have any spare file descriptors and we
27803 try to spawn a dns or cpu worker.
27804 - Make the numbers in read-history and write-history into uint64s,
27805 so they don't overflow and publish negatives in the descriptor.
27807 o Fixes on 0.1.0.x:
27808 - For the OS X package's modified privoxy config file, comment
27809 out the "logfile" line so we don't log everything passed
27811 - We were whining about using socks4 or socks5-with-local-lookup
27812 even when it's an IP in the "virtual" range we designed exactly
27814 - We were leaking some memory every time the client changes IPs.
27815 - Never call free() on tor_malloc()d memory. This will help us
27816 use dmalloc to detect memory leaks.
27817 - Check for named servers when looking them up by nickname;
27818 warn when we'recalling a non-named server by its nickname;
27819 don't warn twice about the same name.
27820 - Try to list MyFamily elements by key, not by nickname, and warn
27821 if we've not heard of the server.
27822 - Make windows platform detection (uname equivalent) smarter.
27823 - It turns out sparc64 doesn't like unaligned access either.
27826 Changes in version 0.1.0.15 - 2005-09-23
27827 o Bugfixes on 0.1.0.x:
27828 - Reject ports 465 and 587 (spam targets) in default exit policy.
27829 - Don't crash when we don't have any spare file descriptors and we
27830 try to spawn a dns or cpu worker.
27831 - Get rid of IgnoreVersion undocumented config option, and make us
27832 only warn, never exit, when we're running an obsolete version.
27833 - Don't try to print a null string when your server finds itself to
27834 be unreachable and the Address config option is empty.
27835 - Make the numbers in read-history and write-history into uint64s,
27836 so they don't overflow and publish negatives in the descriptor.
27837 - Fix a minor memory leak in smartlist_string_remove().
27838 - We were only allowing ourselves to upload a server descriptor at
27839 most every 20 minutes, even if it changed earlier than that.
27840 - Clean up log entries that pointed to old URLs.
27843 Changes in version 0.1.1.7-alpha - 2005-09-14
27844 o Fixes on 0.1.1.6-alpha:
27845 - Exit servers were crashing when people asked them to make a
27846 connection to an address not in their exit policy.
27847 - Looking up a non-existent stream for a v1 control connection would
27849 - Fix a seg fault if we ask a dirserver for a descriptor by
27850 fingerprint but he doesn't know about him.
27851 - SETCONF was appending items to linelists, not clearing them.
27852 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
27853 out and refuse the setconf if it would fail.
27854 - Downgrade the dirserver log messages when whining about
27858 - Add Peter Palfrader's check-tor script to tor/contrib/
27859 It lets you easily check whether a given server (referenced by
27860 nickname) is reachable by you.
27861 - Numerous changes to move towards client-side v2 directories. Not
27864 o Fixes on 0.1.0.x:
27865 - If the user gave tor an odd number of command-line arguments,
27866 we were silently ignoring the last one. Now we complain and fail.
27867 [This wins the oldest-bug prize -- this bug has been present since
27868 November 2002, as released in Tor 0.0.0.]
27869 - Do not use unaligned memory access on alpha, mips, or mipsel.
27870 It *works*, but is very slow, so we treat them as if it doesn't.
27871 - Retry directory requests if we fail to get an answer we like
27872 from a given dirserver (we were retrying before, but only if
27873 we fail to connect).
27874 - When writing the RecommendedVersions line, sort them first.
27875 - When the client asked for a rendezvous port that the hidden
27876 service didn't want to provide, we were sending an IP address
27877 back along with the end cell. Fortunately, it was zero. But stop
27879 - Correct "your server is reachable" log entries to indicate that
27880 it was self-testing that told us so.
27883 Changes in version 0.1.1.6-alpha - 2005-09-09
27884 o Fixes on 0.1.1.5-alpha:
27885 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
27886 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
27887 - Fix bug with tor_memmem finding a match at the end of the string.
27888 - Make unit tests run without segfaulting.
27889 - Resolve some solaris x86 compile warnings.
27890 - Handle duplicate lines in approved-routers files without warning.
27891 - Fix bug where as soon as a server refused any requests due to his
27892 exit policy (e.g. when we ask for localhost and he tells us that's
27893 127.0.0.1 and he won't do it), we decided he wasn't obeying his
27894 exit policy using him for any exits.
27895 - Only do openssl hardware accelerator stuff if openssl version is
27898 o New controller features/fixes:
27899 - Add a "RESETCONF" command so you can set config options like
27900 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
27901 a config option in the torrc with no value, then it clears it
27902 entirely (rather than setting it to its default).
27903 - Add a "GETINFO config-file" to tell us where torrc is.
27904 - Avoid sending blank lines when GETINFO replies should be empty.
27905 - Add a QUIT command for the controller (for using it manually).
27906 - Fix a bug in SAVECONF that was adding default dirservers and
27907 other redundant entries to the torrc file.
27909 o Start on the new directory design:
27910 - Generate, publish, cache, serve new network-status format.
27911 - Publish individual descriptors (by fingerprint, by "all", and by
27913 - Publish client and server recommended versions separately.
27914 - Allow tor_gzip_uncompress() to handle multiple concatenated
27915 compressed strings. Serve compressed groups of router
27916 descriptors. The compression logic here could be more
27918 - Distinguish v1 authorities (all currently trusted directories)
27919 from v2 authorities (all trusted directories).
27920 - Change DirServers config line to note which dirs are v1 authorities.
27921 - Add configuration option "V1AuthoritativeDirectory 1" which
27922 moria1, moria2, and tor26 should set.
27923 - Remove option when getting directory cache to see whether they
27924 support running-routers; they all do now. Replace it with one
27925 to see whether caches support v2 stuff.
27928 - Dirservers now do their own external reachability testing of each
27929 Tor server, and only list them as running if they've been found to
27930 be reachable. We also send back warnings to the server's logs if
27931 it uploads a descriptor that we already believe is unreachable.
27932 - Implement exit enclaves: if we know an IP address for the
27933 destination, and there's a running Tor server at that address
27934 which allows exit to the destination, then extend the circuit to
27935 that exit first. This provides end-to-end encryption and end-to-end
27936 authentication. Also, if the user wants a .exit address or enclave,
27937 use 4 hops rather than 3, and cannibalize a general circ for it
27939 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
27940 controller. Also, rotate dns and cpu workers if the controller
27941 changes options that will affect them; and initialize the dns
27942 worker cache tree whether or not we start out as a server.
27943 - Only upload a new server descriptor when options change, 18
27944 hours have passed, uptime is reset, or bandwidth changes a lot.
27945 - Check [X-]Forwarded-For headers in HTTP requests when generating
27946 log messages. This lets people run dirservers (and caches) behind
27947 Apache but still know which IP addresses are causing warnings.
27949 o Config option changes:
27950 - Replace (Fascist)Firewall* config options with a new
27951 ReachableAddresses option that understands address policies.
27952 For example, "ReachableAddresses *:80,*:443"
27953 - Get rid of IgnoreVersion undocumented config option, and make us
27954 only warn, never exit, when we're running an obsolete version.
27955 - Make MonthlyAccountingStart config option truly obsolete now.
27957 o Fixes on 0.1.0.x:
27958 - Reject ports 465 and 587 in the default exit policy, since
27959 people have started using them for spam too.
27960 - It turns out we couldn't bootstrap a network since we added
27961 reachability detection in 0.1.0.1-rc. Good thing the Tor network
27962 has never gone down. Add an AssumeReachable config option to let
27963 servers and dirservers bootstrap. When we're trying to build a
27964 high-uptime or high-bandwidth circuit but there aren't enough
27965 suitable servers, try being less picky rather than simply failing.
27966 - Our logic to decide if the OR we connected to was the right guy
27967 was brittle and maybe open to a mitm for unverified routers.
27968 - We weren't cannibalizing circuits correctly for
27969 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
27970 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
27971 build those from scratch. This should make hidden services faster.
27972 - Predict required circuits better, with an eye toward making hidden
27973 services faster on the service end.
27974 - Retry streams if the exit node sends back a 'misc' failure. This
27975 should result in fewer random failures. Also, after failing
27976 from resolve failed or misc, reset the num failures, so we give
27977 it a fair shake next time we try.
27978 - Clean up the rendezvous warn log msgs, and downgrade some to info.
27979 - Reduce severity on logs about dns worker spawning and culling.
27980 - When we're shutting down and we do something like try to post a
27981 server descriptor or rendezvous descriptor, don't complain that
27982 we seem to be unreachable. Of course we are, we're shutting down.
27983 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
27984 We don't use them yet, but maybe one day our DNS resolver will be
27985 able to discover them.
27986 - Make ContactInfo mandatory for authoritative directory servers.
27987 - Require server descriptors to list IPv4 addresses -- hostnames
27988 are no longer allowed. This also fixes some potential security
27989 problems with people providing hostnames as their address and then
27990 preferentially resolving them to partition users.
27991 - Change log line for unreachability to explicitly suggest /etc/hosts
27992 as the culprit. Also make it clearer what IP address and ports we're
27993 testing for reachability.
27994 - Put quotes around user-supplied strings when logging so users are
27995 more likely to realize if they add bad characters (like quotes)
27997 - Let auth dir servers start without specifying an Address config
27999 - Make unit tests (and other invocations that aren't the real Tor)
28000 run without launching listeners, creating subdirectories, and so on.
28003 Changes in version 0.1.1.5-alpha - 2005-08-08
28004 o Bugfixes included in 0.1.0.14.
28006 o Bugfixes on 0.1.0.x:
28007 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
28008 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
28009 it would silently using ignore the 6668.
28012 Changes in version 0.1.0.14 - 2005-08-08
28013 o Bugfixes on 0.1.0.x:
28014 - Fix the other half of the bug with crypto handshakes
28016 - Fix an assert trigger if you send a 'signal term' via the
28017 controller when it's listening for 'event info' messages.
28020 Changes in version 0.1.1.4-alpha - 2005-08-04
28021 o Bugfixes included in 0.1.0.13.
28024 - Improve tor_gettimeofday() granularity on windows.
28025 - Make clients regenerate their keys when their IP address changes.
28026 - Implement some more GETINFO goodness: expose helper nodes, config
28027 options, getinfo keys.
28030 Changes in version 0.1.0.13 - 2005-08-04
28031 o Bugfixes on 0.1.0.x:
28032 - Fix a critical bug in the security of our crypto handshakes.
28033 - Fix a size_t underflow in smartlist_join_strings2() that made
28034 it do bad things when you hand it an empty smartlist.
28035 - Fix Windows installer to ship Tor license (thanks to Aphex for
28036 pointing out this oversight) and put a link to the doc directory
28038 - Explicitly set no-unaligned-access for sparc: it turns out the
28039 new gcc's let you compile broken code, but that doesn't make it
28043 Changes in version 0.1.1.3-alpha - 2005-07-23
28044 o Bugfixes on 0.1.1.2-alpha:
28045 - Fix a bug in handling the controller's "post descriptor"
28047 - Fix several bugs in handling the controller's "extend circuit"
28049 - Fix a bug in handling the controller's "stream status" event.
28050 - Fix an assert failure if we have a controller listening for
28051 circuit events and we go offline.
28052 - Re-allow hidden service descriptors to publish 0 intro points.
28053 - Fix a crash when generating your hidden service descriptor if
28054 you don't have enough intro points already.
28056 o New features on 0.1.1.2-alpha:
28057 - New controller function "getinfo accounting", to ask how
28058 many bytes we've used in this time period.
28059 - Experimental support for helper nodes: a lot of the risk from
28060 a small static adversary comes because users pick new random
28061 nodes every time they rebuild a circuit. Now users will try to
28062 stick to the same small set of entry nodes if they can. Not
28063 enabled by default yet.
28065 o Bugfixes on 0.1.0.12:
28066 - If you're an auth dir server, always publish your dirport,
28067 even if you haven't yet found yourself to be reachable.
28068 - Fix a size_t underflow in smartlist_join_strings2() that made
28069 it do bad things when you hand it an empty smartlist.
28072 Changes in version 0.1.0.12 - 2005-07-18
28073 o New directory servers:
28074 - tor26 has changed IP address.
28076 o Bugfixes on 0.1.0.x:
28077 - Fix a possible double-free in tor_gzip_uncompress().
28078 - When --disable-threads is set, do not search for or link against
28079 pthreads libraries.
28080 - Don't trigger an assert if an authoritative directory server
28081 claims its dirport is 0.
28082 - Fix bug with removing Tor as an NT service: some people were
28083 getting "The service did not return an error." Thanks to Matt
28087 Changes in version 0.1.1.2-alpha - 2005-07-15
28088 o New directory servers:
28089 - tor26 has changed IP address.
28091 o Bugfixes on 0.1.0.x, crashes/leaks:
28092 - Port the servers-not-obeying-their-exit-policies fix from
28094 - Fix an fd leak in start_daemon().
28095 - On Windows, you can't always reopen a port right after you've
28096 closed it. So change retry_listeners() to only close and re-open
28097 ports that have changed.
28098 - Fix a possible double-free in tor_gzip_uncompress().
28100 o Bugfixes on 0.1.0.x, usability:
28101 - When tor_socketpair() fails in Windows, give a reasonable
28102 Windows-style errno back.
28103 - Let people type "tor --install" as well as "tor -install" when
28105 want to make it an NT service.
28106 - NT service patch from Matt Edman to improve error messages.
28107 - When the controller asks for a config option with an abbreviated
28108 name, give the full name in our response.
28109 - Correct the man page entry on TrackHostExitsExpire.
28110 - Looks like we were never delivering deflated (i.e. compressed)
28111 running-routers lists, even when asked. Oops.
28112 - When --disable-threads is set, do not search for or link against
28113 pthreads libraries.
28115 o Bugfixes on 0.1.1.x:
28116 - Fix a seg fault with autodetecting which controller version is
28120 - New hidden service descriptor format: put a version in it, and
28121 let people specify introduction/rendezvous points that aren't
28122 in "the directory" (which is subjective anyway).
28123 - Allow the DEBUG controller event to work again. Mark certain log
28124 entries as "don't tell this to controllers", so we avoid cycles.
28127 Changes in version 0.1.0.11 - 2005-06-30
28128 o Bugfixes on 0.1.0.x:
28129 - Fix major security bug: servers were disregarding their
28130 exit policies if clients behaved unexpectedly.
28131 - Make OS X init script check for missing argument, so we don't
28132 confuse users who invoke it incorrectly.
28133 - Fix a seg fault in "tor --hash-password foo".
28134 - The MAPADDRESS control command was broken.
28137 Changes in version 0.1.1.1-alpha - 2005-06-29
28139 - Make OS X init script check for missing argument, so we don't
28140 confuse users who invoke it incorrectly.
28141 - Fix a seg fault in "tor --hash-password foo".
28142 - Fix a possible way to DoS dirservers.
28143 - When we complain that your exit policy implicitly allows local or
28144 private address spaces, name them explicitly so operators can
28146 - Make the log message less scary when all the dirservers are
28147 temporarily unreachable.
28148 - We were printing the number of idle dns workers incorrectly when
28152 - Revised controller protocol (version 1) that uses ascii rather
28153 than binary. Add supporting libraries in python and java so you
28154 can use the controller from your applications without caring how
28155 our protocol works.
28156 - Spiffy new support for crypto hardware accelerators. Can somebody
28160 Changes in version 0.0.9.10 - 2005-06-16
28161 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
28162 - Refuse relay cells that claim to have a length larger than the
28163 maximum allowed. This prevents a potential attack that could read
28164 arbitrary memory (e.g. keys) from an exit server's process
28168 Changes in version 0.1.0.10 - 2005-06-14
28169 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
28170 libevent before 1.1a.
28173 Changes in version 0.1.0.9-rc - 2005-06-09
28175 - Reset buf->highwater every time buf_shrink() is called, not just on
28176 a successful shrink. This was causing significant memory bloat.
28177 - Fix buffer overflow when checking hashed passwords.
28178 - Security fix: if seeding the RNG on Win32 fails, quit.
28179 - Allow seeding the RNG on Win32 even when you're not running as
28181 - Disable threading on Solaris too. Something is wonky with it,
28182 cpuworkers, and reentrant libs.
28183 - Reenable the part of the code that tries to flush as soon as an
28184 OR outbuf has a full TLS record available. Perhaps this will make
28185 OR outbufs not grow as huge except in rare cases, thus saving lots
28186 of CPU time plus memory.
28187 - Reject malformed .onion addresses rather then passing them on as
28188 normal web requests.
28189 - Adapt patch from Adam Langley: fix possible memory leak in
28190 tor_lookup_hostname().
28191 - Initialize libevent later in the startup process, so the logs are
28192 already established by the time we start logging libevent warns.
28193 - Use correct errno on win32 if libevent fails.
28194 - Check and warn about known-bad/slow libevent versions.
28195 - Pay more attention to the ClientOnly config option.
28196 - Have torctl.in/tor.sh.in check for location of su binary (needed
28198 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
28199 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
28200 HttpProxyAuthenticator
28201 - Stop warning about sigpipes in the logs. We're going to
28202 pretend that getting these occasionally is normal and fine.
28203 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
28205 installer screens; and don't put stuff into StartupItems unless
28206 the user asks you to.
28207 - Require servers that use the default dirservers to have public IP
28208 addresses. We have too many servers that are configured with private
28209 IPs and their admins never notice the log entries complaining that
28210 their descriptors are being rejected.
28211 - Add OSX uninstall instructions. An actual uninstall script will
28215 Changes in version 0.1.0.8-rc - 2005-05-23
28217 - It turns out that kqueue on OS X 10.3.9 was causing kernel
28218 panics. Disable kqueue on all OS X Tors.
28219 - Fix RPM: remove duplicate line accidentally added to the rpm
28221 - Disable threads on openbsd too, since its gethostaddr is not
28223 - Tolerate libevent 0.8 since it still works, even though it's
28225 - Enable building on Red Hat 9.0 again.
28226 - Allow the middle hop of the testing circuit to be running any
28227 version, now that most of them have the bugfix to let them connect
28228 to unknown servers. This will allow reachability testing to work
28229 even when 0.0.9.7-0.0.9.9 become obsolete.
28230 - Handle relay cells with rh.length too large. This prevents
28231 a potential attack that could read arbitrary memory (maybe even
28232 keys) from the exit server's process.
28233 - We screwed up the dirport reachability testing when we don't yet
28234 have a cached version of the directory. Hopefully now fixed.
28235 - Clean up router_load_single_router() (used by the controller),
28236 so it doesn't seg fault on error.
28237 - Fix a minor memory leak when somebody establishes an introduction
28238 point at your Tor server.
28239 - If a socks connection ends because read fails, don't warn that
28240 you're not sending a socks reply back.
28243 - Add HttpProxyAuthenticator config option too, that works like
28244 the HttpsProxyAuthenticator config option.
28245 - Encode hashed controller passwords in hex instead of base64,
28246 to make it easier to write controllers.
28249 Changes in version 0.1.0.7-rc - 2005-05-17
28251 - Fix a bug in the OS X package installer that prevented it from
28252 installing on Tiger.
28253 - Fix a script bug in the OS X package installer that made it
28254 complain during installation.
28255 - Find libevent even if it's hiding in /usr/local/ and your
28256 CFLAGS and LDFLAGS don't tell you to look there.
28257 - Be able to link with libevent as a shared library (the default
28258 after 1.0d), even if it's hiding in /usr/local/lib and even
28259 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
28260 assuming you're running gcc. Otherwise fail and give a useful
28262 - Fix a bug in the RPM packager: set home directory for _tor to
28263 something more reasonable when first installing.
28264 - Free a minor amount of memory that is still reachable on exit.
28267 Changes in version 0.1.0.6-rc - 2005-05-14
28269 - Implement --disable-threads configure option. Disable threads on
28270 netbsd by default, because it appears to have no reentrant resolver
28272 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
28273 release (1.1) detects and disables kqueue if it's broken.
28274 - Append default exit policy before checking for implicit internal
28275 addresses. Now we don't log a bunch of complaints on startup
28276 when using the default exit policy.
28277 - Some people were putting "Address " in their torrc, and they had
28278 a buggy resolver that resolved " " to 0.0.0.0. Oops.
28279 - If DataDir is ~/.tor, and that expands to /.tor, then default to
28280 LOCALSTATEDIR/tor instead.
28281 - Fix fragmented-message bug in TorControl.py.
28282 - Resolve a minor bug which would prevent unreachable dirports
28283 from getting suppressed in the published descriptor.
28284 - When the controller gave us a new descriptor, we weren't resolving
28285 it immediately, so Tor would think its address was 0.0.0.0 until
28286 we fetched a new directory.
28287 - Fix an uppercase/lowercase case error in suppressing a bogus
28288 libevent warning on some Linuxes.
28291 - Begin scrubbing sensitive strings from logs by default. Turn off
28292 the config option SafeLogging if you need to do debugging.
28293 - Switch to a new buffer management algorithm, which tries to avoid
28294 reallocing and copying quite as much. In first tests it looks like
28295 it uses *more* memory on average, but less cpu.
28296 - First cut at support for "create-fast" cells. Clients can use
28297 these when extending to their first hop, since the TLS already
28298 provides forward secrecy and authentication. Not enabled on
28300 - When dirservers refuse a router descriptor, we now log its
28301 contactinfo, platform, and the poster's IP address.
28302 - Call tor_free_all instead of connections_free_all after forking, to
28303 save memory on systems that need to fork.
28304 - Whine at you if you're a server and you don't set your contactinfo.
28305 - Implement --verify-config command-line option to check if your torrc
28306 is valid without actually launching Tor.
28307 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
28308 rather than just rejecting it.
28311 Changes in version 0.1.0.5-rc - 2005-04-27
28313 - Stop trying to print a null pointer if an OR conn fails because
28314 we didn't like its cert.
28316 - Switch our internal buffers implementation to use a ring buffer,
28317 to hopefully improve performance for fast servers a lot.
28318 - Add HttpsProxyAuthenticator support (basic auth only), based
28319 on patch from Adam Langley.
28320 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
28321 the fast servers that have been joining lately.
28322 - Give hidden service accesses extra time on the first attempt,
28323 since 60 seconds is often only barely enough. This might improve
28325 - Improve performance for dirservers: stop re-parsing the whole
28326 directory every time you regenerate it.
28327 - Add more debugging info to help us find the weird dns freebsd
28328 pthreads bug; cleaner debug messages to help track future issues.
28331 Changes in version 0.0.9.9 - 2005-04-23
28332 o Bugfixes on 0.0.9.x:
28333 - If unofficial Tor clients connect and send weird TLS certs, our
28334 Tor server triggers an assert. This release contains a minimal
28335 backport from the broader fix that we put into 0.1.0.4-rc.
28338 Changes in version 0.1.0.4-rc - 2005-04-23
28340 - If unofficial Tor clients connect and send weird TLS certs, our
28341 Tor server triggers an assert. Stop asserting, and start handling
28342 TLS errors better in other situations too.
28343 - When the controller asks us to tell it about all the debug-level
28344 logs, it turns out we were generating debug-level logs while
28345 telling it about them, which turns into a bad loop. Now keep
28346 track of whether you're sending a debug log to the controller,
28347 and don't log when you are.
28348 - Fix the "postdescriptor" feature of the controller interface: on
28349 non-complete success, only say "done" once.
28351 - Clients are now willing to load balance over up to 2mB, not 1mB,
28352 of advertised bandwidth capacity.
28353 - Add a NoPublish config option, so you can be a server (e.g. for
28354 testing running Tor servers in other Tor networks) without
28355 publishing your descriptor to the primary dirservers.
28358 Changes in version 0.1.0.3-rc - 2005-04-08
28359 o Improvements on 0.1.0.2-rc:
28360 - Client now retries when streams end early for 'hibernating' or
28361 'resource limit' reasons, rather than failing them.
28362 - More automated handling for dirserver operators:
28363 - Automatically approve nodes running 0.1.0.2-rc or later,
28364 now that the the reachability detection stuff is working.
28365 - Now we allow two unverified servers with the same nickname
28366 but different keys. But if a nickname is verified, only that
28367 nickname+key are allowed.
28368 - If you're an authdirserver connecting to an address:port,
28369 and it's not the OR you were expecting, forget about that
28370 descriptor. If he *was* the one you were expecting, then forget
28371 about all other descriptors for that address:port.
28372 - Allow servers to publish descriptors from 12 hours in the future.
28373 Corollary: only whine about clock skew from the dirserver if
28374 he's a trusted dirserver (since now even verified servers could
28375 have quite wrong clocks).
28376 - Adjust maximum skew and age for rendezvous descriptors: let skew
28377 be 48 hours rather than 90 minutes.
28378 - Efficiency improvements:
28379 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
28380 it much faster to look up a circuit for each relay cell.
28381 - Remove most calls to assert_all_pending_dns_resolves_ok(),
28382 since they're eating our cpu on exit nodes.
28383 - Stop wasting time doing a case insensitive comparison for every
28384 dns name every time we do any lookup. Canonicalize the names to
28385 lowercase and be done with it.
28386 - Start sending 'truncated' cells back rather than destroy cells,
28387 if the circuit closes in front of you. This means we won't have
28388 to abandon partially built circuits.
28389 - Only warn once per nickname from add_nickname_list_to_smartlist
28390 per failure, so an entrynode or exitnode choice that's down won't
28392 - Put a note in the torrc about abuse potential with the default
28394 - Revise control spec and implementation to allow all log messages to
28395 be sent to controller with their severities intact (suggested by
28396 Matt Edman). Update TorControl to handle new log event types.
28397 - Provide better explanation messages when controller's POSTDESCRIPTOR
28399 - Stop putting nodename in the Platform string in server descriptors.
28400 It doesn't actually help, and it is confusing/upsetting some people.
28402 o Bugfixes on 0.1.0.2-rc:
28403 - We were printing the host mask wrong in exit policies in server
28404 descriptors. This isn't a critical bug though, since we were still
28405 obeying the exit policy internally.
28406 - Fix Tor when compiled with libevent but without pthreads: move
28407 connection_unregister() from _connection_free() to
28409 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
28410 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
28411 when we look through the connection array, we'll find any of the
28412 cpu/dnsworkers. This is no good.
28414 o Bugfixes on 0.0.9.8:
28415 - Fix possible bug on threading platforms (e.g. win32) which was
28416 leaking a file descriptor whenever a cpuworker or dnsworker died.
28417 - When using preferred entry or exit nodes, ignore whether the
28418 circuit wants uptime or capacity. They asked for the nodes, they
28420 - chdir() to your datadirectory at the *end* of the daemonize process,
28421 not the beginning. This was a problem because the first time you
28422 run tor, if your datadir isn't there, and you have runasdaemon set
28423 to 1, it will try to chdir to it before it tries to create it. Oops.
28424 - Handle changed router status correctly when dirserver reloads
28425 fingerprint file. We used to be dropping all unverified descriptors
28426 right then. The bug was hidden because we would immediately
28427 fetch a directory from another dirserver, which would include the
28428 descriptors we just dropped.
28429 - When we're connecting to an OR and he's got a different nickname/key
28430 than we were expecting, only complain loudly if we're an OP or a
28431 dirserver. Complaining loudly to the OR admins just confuses them.
28432 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
28433 artificially capped at 500kB.
28436 Changes in version 0.0.9.8 - 2005-04-07
28437 o Bugfixes on 0.0.9.x:
28438 - We have a bug that I haven't found yet. Sometimes, very rarely,
28439 cpuworkers get stuck in the 'busy' state, even though the cpuworker
28440 thinks of itself as idle. This meant that no new circuits ever got
28441 established. Here's a workaround to kill any cpuworker that's been
28442 busy for more than 100 seconds.
28445 Changes in version 0.1.0.2-rc - 2005-04-01
28446 o Bugfixes on 0.1.0.1-rc:
28447 - Fixes on reachability detection:
28448 - Don't check for reachability while hibernating.
28449 - If ORPort is reachable but DirPort isn't, still publish the
28450 descriptor, but zero out DirPort until it's found reachable.
28451 - When building testing circs for ORPort testing, use only
28452 high-bandwidth nodes, so fewer circuits fail.
28453 - Complain about unreachable ORPort separately from unreachable
28454 DirPort, so the user knows what's going on.
28455 - Make sure we only conclude ORPort reachability if we didn't
28456 initiate the conn. Otherwise we could falsely conclude that
28457 we're reachable just because we connected to the guy earlier
28458 and he used that same pipe to extend to us.
28459 - Authdirservers shouldn't do ORPort reachability detection,
28460 since they're in clique mode, so it will be rare to find a
28461 server not already connected to them.
28462 - When building testing circuits, always pick middle hops running
28463 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
28464 bug. (This is a kludge; it will go away when 0.0.9.x becomes
28466 - When we decide we're reachable, actually publish our descriptor
28468 - Fix bug in redirectstream in the controller.
28469 - Fix the state descriptor strings so logs don't claim edge streams
28470 are in a different state than they actually are.
28471 - Use recent libevent features when possible (this only really affects
28472 win32 and osx right now, because the new libevent with these
28473 features hasn't been released yet). Add code to suppress spurious
28475 - Prevent possible segfault in connection_close_unattached_ap().
28476 - Fix newlines on torrc in win32.
28477 - Improve error msgs when tor-resolve fails.
28479 o Improvements on 0.0.9.x:
28480 - New experimental script tor/contrib/ExerciseServer.py (needs more
28481 work) that uses the controller interface to build circuits and
28482 fetch pages over them. This will help us bootstrap servers that
28483 have lots of capacity but haven't noticed it yet.
28484 - New experimental script tor/contrib/PathDemo.py (needs more work)
28485 that uses the controller interface to let you choose whole paths
28487 "<hostname>.<path,separated by dots>.<length of path>.path"
28488 - When we've connected to an OR and handshaked but didn't like
28489 the result, we were closing the conn without sending destroy
28490 cells back for pending circuits. Now send those destroys.
28493 Changes in version 0.0.9.7 - 2005-04-01
28494 o Bugfixes on 0.0.9.x:
28495 - Fix another race crash bug (thanks to Glenn Fink for reporting).
28496 - Compare identity to identity, not to nickname, when extending to
28497 a router not already in the directory. This was preventing us from
28498 extending to unknown routers. Oops.
28499 - Make sure to create OS X Tor user in <500 range, so we aren't
28500 creating actual system users.
28501 - Note where connection-that-hasn't-sent-end was marked, and fix
28502 a few really loud instances of this harmless bug (it's fixed more
28506 Changes in version 0.1.0.1-rc - 2005-03-28
28508 - Add reachability testing. Your Tor server will automatically try
28509 to see if its ORPort and DirPort are reachable from the outside,
28510 and it won't upload its descriptor until it decides they are.
28511 - Handle unavailable hidden services better. Handle slow or busy
28512 hidden services better.
28513 - Add support for CONNECTing through https proxies, with "HttpsProxy"
28515 - New exit policy: accept most low-numbered ports, rather than
28516 rejecting most low-numbered ports.
28517 - More Tor controller support (still experimental). See
28518 http://tor.eff.org/doc/control-spec.txt for all the new features,
28519 including signals to emulate unix signals from any platform;
28520 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
28521 closestream; closecircuit; etc.
28522 - Make nt services work and start on startup on win32 (based on
28523 patch by Matt Edman).
28524 - Add a new AddressMap config directive to rewrite incoming socks
28525 addresses. This lets you, for example, declare an implicit
28526 required exit node for certain sites.
28527 - Add a new TrackHostExits config directive to trigger addressmaps
28528 for certain incoming socks addresses -- for sites that break when
28529 your exit keeps changing (based on patch by Mike Perry).
28530 - Redo the client-side dns cache so it's just an addressmap too.
28531 - Notice when our IP changes, and reset stats/uptime/reachability.
28532 - When an application is using socks5, give him the whole variety of
28533 potential socks5 responses (connect refused, host unreachable, etc),
28534 rather than just "success" or "failure".
28535 - A more sane version numbering system. See
28536 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
28537 - New contributed script "exitlist": a simple python script to
28538 parse directories and find Tor nodes that exit to listed
28540 - New contributed script "privoxy-tor-toggle" to toggle whether
28541 Privoxy uses Tor. Seems to be configured for Debian by default.
28542 - Report HTTP reasons to client when getting a response from directory
28543 servers -- so you can actually know what went wrong.
28544 - New config option MaxAdvertisedBandwidth which lets you advertise
28545 a low bandwidthrate (to not attract as many circuits) while still
28546 allowing a higher bandwidthrate in reality.
28548 o Robustness/stability fixes:
28549 - Make Tor use Niels Provos's libevent instead of its current
28550 poll-but-sometimes-select mess. This will let us use faster async
28551 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
28553 - pthread support now too. This was forced because when we forked,
28554 we ended up wasting a lot of duplicate ram over time. Also switch
28555 to foo_r versions of some library calls to allow reentry and
28557 - Better handling for heterogeneous / unreliable nodes:
28558 - Annotate circuits w/ whether they aim to contain high uptime nodes
28559 and/or high capacity nodes. When building circuits, choose
28561 - This means that every single node in an intro rend circuit,
28562 not just the last one, will have a minimum uptime.
28563 - New config option LongLivedPorts to indicate application streams
28564 that will want high uptime circuits.
28565 - Servers reset uptime when a dir fetch entirely fails. This
28566 hopefully reflects stability of the server's network connectivity.
28567 - If somebody starts his tor server in Jan 2004 and then fixes his
28568 clock, don't make his published uptime be a year.
28569 - Reset published uptime when you wake up from hibernation.
28570 - Introduce a notion of 'internal' circs, which are chosen without
28571 regard to the exit policy of the last hop. Intro and rendezvous
28572 circs must be internal circs, to avoid leaking information. Resolve
28573 and connect streams can use internal circs if they want.
28574 - New circuit pooling algorithm: make sure to have enough circs around
28575 to satisfy any predicted ports, and also make sure to have 2 internal
28576 circs around if we've required internal circs lately (and with high
28577 uptime if we've seen that lately too).
28578 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
28579 which describes how often we retry making new circuits if current
28580 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
28581 how long we're willing to make use of an already-dirty circuit.
28582 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
28583 circ as necessary, if there are any completed ones lying around
28584 when we try to launch one.
28585 - Make hidden services try to establish a rendezvous for 30 seconds,
28586 rather than for n (where n=3) attempts to build a circuit.
28587 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
28588 "ShutdownWaitLength".
28589 - Try to be more zealous about calling connection_edge_end when
28590 things go bad with edge conns in connection.c.
28591 - Revise tor-spec to add more/better stream end reasons.
28592 - Revise all calls to connection_edge_end to avoid sending "misc",
28593 and to take errno into account where possible.
28596 - Fix a race condition that can trigger an assert, when we have a
28597 pending create cell and an OR connection fails right then.
28598 - Fix several double-mark-for-close bugs, e.g. where we were finding
28599 a conn for a cell even if that conn is already marked for close.
28600 - Make sequence of log messages when starting on win32 with no config
28601 file more reasonable.
28602 - When choosing an exit node for a new non-internal circ, don't take
28603 into account whether it'll be useful for any pending x.onion
28604 addresses -- it won't.
28605 - Turn addr_policy_compare from a tristate to a quadstate; this should
28606 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
28607 for google.com" problem.
28608 - Make "platform" string in descriptor more accurate for Win32 servers,
28609 so it's not just "unknown platform".
28610 - Fix an edge case in parsing config options (thanks weasel).
28611 If they say "--" on the commandline, it's not an option.
28612 - Reject odd-looking addresses at the client (e.g. addresses that
28613 contain a colon), rather than having the server drop them because
28615 - tor-resolve requests were ignoring .exit if there was a working circuit
28616 they could use instead.
28617 - REUSEADDR on normal platforms means you can rebind to the port
28618 right after somebody else has let it go. But REUSEADDR on win32
28619 means to let you bind to the port _even when somebody else
28620 already has it bound_! So, don't do that on Win32.
28621 - Change version parsing logic: a version is "obsolete" if it is not
28622 recommended and (1) there is a newer recommended version in the
28623 same series, or (2) there are no recommended versions in the same
28624 series, but there are some recommended versions in a newer series.
28625 A version is "new" if it is newer than any recommended version in
28627 - Stop most cases of hanging up on a socks connection without sending
28631 - Require BandwidthRate to be at least 20kB/s for servers.
28632 - When a dirserver causes you to give a warn, mention which dirserver
28634 - New config option DirAllowPrivateAddresses for authdirservers.
28635 Now by default they refuse router descriptors that have non-IP or
28636 private-IP addresses.
28637 - Stop publishing socksport in the directory, since it's not
28638 actually meant to be public. For compatibility, publish a 0 there
28640 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
28641 smart" value, that is low for servers and high for clients.
28642 - If our clock jumps forward by 100 seconds or more, assume something
28643 has gone wrong with our network and abandon all not-yet-used circs.
28644 - Warn when exit policy implicitly allows local addresses.
28645 - If we get an incredibly skewed timestamp from a dirserver mirror
28646 that isn't a verified OR, don't warn -- it's probably him that's
28648 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
28649 cookies to disk and doesn't log each web request to disk. (Thanks
28650 to Brett Carrington for pointing this out.)
28651 - When a client asks us for a dir mirror and we don't have one,
28652 launch an attempt to get a fresh one.
28653 - If we're hibernating and we get a SIGINT, exit immediately.
28654 - Add --with-dmalloc ./configure option, to track memory leaks.
28655 - And try to free all memory on closing, so we can detect what
28657 - Cache local dns resolves correctly even when they're .exit
28659 - Give a better warning when some other server advertises an
28660 ORPort that is actually an apache running ssl.
28661 - Add "opt hibernating 1" to server descriptor to make it clearer
28662 whether the server is hibernating.
28665 Changes in version 0.0.9.6 - 2005-03-24
28666 o Bugfixes on 0.0.9.x (crashes and asserts):
28667 - Add new end stream reasons to maintenance branch. Fix bug where
28668 reason (8) could trigger an assert. Prevent bug from recurring.
28669 - Apparently win32 stat wants paths to not end with a slash.
28670 - Fix assert triggers in assert_cpath_layer_ok(), where we were
28671 blowing away the circuit that conn->cpath_layer points to, then
28672 checking to see if the circ is well-formed. Backport check to make
28673 sure we dont use the cpath on a closed connection.
28674 - Prevent circuit_resume_edge_reading_helper() from trying to package
28675 inbufs for marked-for-close streams.
28676 - Don't crash on hup if your options->address has become unresolvable.
28677 - Some systems (like OS X) sometimes accept() a connection and tell
28678 you the remote host is 0.0.0.0:0. If this happens, due to some
28679 other mis-features, we get confused; so refuse the conn for now.
28681 o Bugfixes on 0.0.9.x (other):
28682 - Fix harmless but scary "Unrecognized content encoding" warn message.
28683 - Add new stream error reason: TORPROTOCOL reason means "you are not
28684 speaking a version of Tor I understand; say bye-bye to your stream."
28685 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
28686 into the future, now that we are more tolerant of skew. This
28687 resolves a bug where a Tor server would refuse to cache a directory
28688 because all the directories it gets are too far in the future;
28689 yet the Tor server never logs any complaints about clock skew.
28690 - Mac packaging magic: make man pages useable, and do not overwrite
28691 existing torrc files.
28692 - Make OS X log happily to /var/log/tor/tor.log
28695 Changes in version 0.0.9.5 - 2005-02-22
28696 o Bugfixes on 0.0.9.x:
28697 - Fix an assert race at exit nodes when resolve requests fail.
28698 - Stop picking unverified dir mirrors--it only leads to misery.
28699 - Patch from Matt Edman to make NT services work better. Service
28700 support is still not compiled into the executable by default.
28701 - Patch from Dmitri Bely so the Tor service runs better under
28702 the win32 SYSTEM account.
28703 - Make tor-resolve actually work (?) on Win32.
28704 - Fix a sign bug when getrlimit claims to have 4+ billion
28705 file descriptors available.
28706 - Stop refusing to start when bandwidthburst == bandwidthrate.
28707 - When create cells have been on the onion queue more than five
28708 seconds, just send back a destroy and take them off the list.
28711 Changes in version 0.0.9.4 - 2005-02-03
28712 o Bugfixes on 0.0.9:
28713 - Fix an assert bug that took down most of our servers: when
28714 a server claims to have 1 GB of bandwidthburst, don't
28716 - Don't crash as badly if we have spawned the max allowed number
28717 of dnsworkers, or we're out of file descriptors.
28718 - Block more file-sharing ports in the default exit policy.
28719 - MaxConn is now automatically set to the hard limit of max
28720 file descriptors we're allowed (ulimit -n), minus a few for
28722 - Give a clearer message when servers need to raise their
28723 ulimit -n when they start running out of file descriptors.
28724 - SGI Compatibility patches from Jan Schaumann.
28725 - Tolerate a corrupt cached directory better.
28726 - When a dirserver hasn't approved your server, list which one.
28727 - Go into soft hibernation after 95% of the bandwidth is used,
28728 not 99%. This is especially important for daily hibernators who
28729 have a small accounting max. Hopefully it will result in fewer
28730 cut connections when the hard hibernation starts.
28731 - Load-balance better when using servers that claim more than
28732 800kB/s of capacity.
28733 - Make NT services work (experimental, only used if compiled in).
28736 Changes in version 0.0.9.3 - 2005-01-21
28737 o Bugfixes on 0.0.9:
28738 - Backport the cpu use fixes from main branch, so busy servers won't
28739 need as much processor time.
28740 - Work better when we go offline and then come back, or when we
28741 run Tor at boot before the network is up. We do this by
28742 optimistically trying to fetch a new directory whenever an
28743 application request comes in and we think we're offline -- the
28744 human is hopefully a good measure of when the network is back.
28745 - Backport some minimal hidserv bugfixes: keep rend circuits open as
28746 long as you keep using them; actually publish hidserv descriptors
28747 shortly after they change, rather than waiting 20-40 minutes.
28748 - Enable Mac startup script by default.
28749 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
28750 - When you update AllowUnverifiedNodes or FirewallPorts via the
28751 controller's setconf feature, we were always appending, never
28753 - When you update HiddenServiceDir via setconf, it was screwing up
28754 the order of reading the lines, making it fail.
28755 - Do not rewrite a cached directory back to the cache; otherwise we
28756 will think it is recent and not fetch a newer one on startup.
28757 - Workaround for webservers that lie about Content-Encoding: Tor
28758 now tries to autodetect compressed directories and compression
28759 itself. This lets us Proxypass dir fetches through apache.
28762 Changes in version 0.0.9.2 - 2005-01-04
28763 o Bugfixes on 0.0.9 (crashes and asserts):
28764 - Fix an assert on startup when the disk is full and you're logging
28766 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
28767 style address, then we'd crash.
28768 - Fix an assert trigger when the running-routers string we get from
28769 a dirserver is broken.
28770 - Make worker threads start and run on win32. Now win32 servers
28772 - Bandaid (not actually fix, but now it doesn't crash) an assert
28773 where the dns worker dies mysteriously and the main Tor process
28774 doesn't remember anything about the address it was resolving.
28776 o Bugfixes on 0.0.9 (Win32):
28777 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
28778 name out of the warning/assert messages.
28779 - Fix a superficial "unhandled error on read" bug on win32.
28780 - The win32 installer no longer requires a click-through for our
28781 license, since our Free Software license grants rights but does not
28783 - Win32: When connecting to a dirserver fails, try another one
28784 immediately. (This was already working for non-win32 Tors.)
28785 - Stop trying to parse $HOME on win32 when hunting for default
28787 - Make tor-resolve.c work on win32 by calling network_init().
28789 o Bugfixes on 0.0.9 (other):
28790 - Make 0.0.9.x build on Solaris again.
28791 - Due to a fencepost error, we were blowing away the \n when reporting
28792 confvalue items in the controller. So asking for multiple config
28793 values at once couldn't work.
28794 - When listing circuits that are pending on an opening OR connection,
28795 if we're an OR we were listing circuits that *end* at us as
28796 being pending on every listener, dns/cpu worker, etc. Stop that.
28797 - Dirservers were failing to create 'running-routers' or 'directory'
28798 strings if we had more than some threshold of routers. Fix them so
28799 they can handle any number of routers.
28800 - Fix a superficial "Duplicate mark for close" bug.
28801 - Stop checking for clock skew for OR connections, even for servers.
28802 - Fix a fencepost error that was chopping off the last letter of any
28803 nickname that is the maximum allowed nickname length.
28804 - Update URLs in log messages so they point to the new website.
28805 - Fix a potential problem in mangling server private keys while
28806 writing to disk (not triggered yet, as far as we know).
28807 - Include the licenses for other free software we include in Tor,
28808 now that we're shipping binary distributions more regularly.
28811 Changes in version 0.0.9.1 - 2004-12-15
28812 o Bugfixes on 0.0.9:
28813 - Make hibernation actually work.
28814 - Make HashedControlPassword config option work.
28815 - When we're reporting event circuit status to a controller,
28816 don't use the stream status code.
28819 Changes in version 0.0.9 - 2004-12-12
28821 - Clean up manpage and torrc.sample file.
28822 - Clean up severities and text of log warnings.
28824 - Make servers trigger an assert when they enter hibernation.
28827 Changes in version 0.0.9rc7 - 2004-12-08
28828 o Bugfixes on 0.0.9rc:
28829 - Fix a stack-trashing crash when an exit node begins hibernating.
28830 - Avoid looking at unallocated memory while considering which
28831 ports we need to build circuits to cover.
28832 - Stop a sigpipe: when an 'end' cell races with eof from the app,
28833 we shouldn't hold-open-until-flush if the eof arrived first.
28834 - Fix a bug with init_cookie_authentication() in the controller.
28835 - When recommending new-format log lines, if the upper bound is
28836 LOG_ERR, leave it implicit.
28838 o Bugfixes on 0.0.8.1:
28839 - Fix a whole slew of memory leaks.
28840 - Fix isspace() and friends so they still make Solaris happy
28841 but also so they don't trigger asserts on win32.
28842 - Fix parse_iso_time on platforms without strptime (eg win32).
28843 - win32: tolerate extra "readable" events better.
28844 - win32: when being multithreaded, leave parent fdarray open.
28845 - Make unit tests work on win32.
28848 Changes in version 0.0.9rc6 - 2004-12-06
28849 o Bugfixes on 0.0.9pre:
28850 - Clean up some more integer underflow opportunities (not exploitable
28852 - While hibernating, hup should not regrow our listeners.
28853 - Send an end to the streams we close when we hibernate, rather
28854 than just chopping them off.
28855 - React to eof immediately on non-open edge connections.
28857 o Bugfixes on 0.0.8.1:
28858 - Calculate timeout for waiting for a connected cell from the time
28859 we sent the begin cell, not from the time the stream started. If
28860 it took a long time to establish the circuit, we would time out
28861 right after sending the begin cell.
28862 - Fix router_compare_addr_to_addr_policy: it was not treating a port
28863 of * as always matching, so we were picking reject *:* nodes as
28864 exit nodes too. Oops.
28867 - New circuit building strategy: keep a list of ports that we've
28868 used in the past 6 hours, and always try to have 2 circuits open
28869 or on the way that will handle each such port. Seed us with port
28870 80 so web users won't complain that Tor is "slow to start up".
28871 - Make kill -USR1 dump more useful stats about circuits.
28872 - When warning about retrying or giving up, print the address, so
28873 the user knows which one it's talking about.
28874 - If you haven't used a clean circuit in an hour, throw it away,
28875 just to be on the safe side. (This means after 6 hours a totally
28876 unused Tor client will have no circuits open.)
28879 Changes in version 0.0.9rc5 - 2004-12-01
28880 o Bugfixes on 0.0.8.1:
28881 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
28882 - Let resolve conns retry/expire also, rather than sticking around
28884 - If we are using select, make sure we stay within FD_SETSIZE.
28886 o Bugfixes on 0.0.9pre:
28887 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
28888 but doesn't seem to be currently; thanks to Ilja van Sprundel for
28890 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
28891 instead. Impose minima and maxima for all *Period options; impose
28892 even tighter maxima for fetching if we are a caching dirserver.
28893 Clip rather than rejecting.
28894 - Fetch cached running-routers from servers that serve it (that is,
28895 authdirservers and servers running 0.0.9rc5-cvs or later.)
28898 - Accept *:706 (silc) in default exit policy.
28899 - Implement new versioning format for post 0.1.
28900 - Support "foo.nickname.exit" addresses, to let Alice request the
28901 address "foo" as viewed by exit node "nickname". Based on a patch
28903 - Make tor --version --version dump the cvs Id of every file.
28906 Changes in version 0.0.9rc4 - 2004-11-28
28907 o Bugfixes on 0.0.8.1:
28908 - Make windows sockets actually non-blocking (oops), and handle
28909 win32 socket errors better.
28911 o Bugfixes on 0.0.9rc1:
28912 - Actually catch the -USR2 signal.
28915 Changes in version 0.0.9rc3 - 2004-11-25
28916 o Bugfixes on 0.0.8.1:
28917 - Flush the log file descriptor after we print "Tor opening log file",
28918 so we don't see those messages days later.
28920 o Bugfixes on 0.0.9rc1:
28921 - Make tor-resolve work again.
28922 - Avoid infinite loop in tor-resolve if tor hangs up on it.
28923 - Fix an assert trigger for clients/servers handling resolves.
28926 Changes in version 0.0.9rc2 - 2004-11-24
28927 o Bugfixes on 0.0.9rc1:
28928 - I broke socks5 support while fixing the eof bug.
28929 - Allow unitless bandwidths and intervals; they default to bytes
28931 - New servers don't start out hibernating; they are active until
28932 they run out of bytes, so they have a better estimate of how
28933 long it takes, and so their operators can know they're working.
28936 Changes in version 0.0.9rc1 - 2004-11-23
28937 o Bugfixes on 0.0.8.1:
28938 - Finally fix a bug that's been plaguing us for a year:
28939 With high load, circuit package window was reaching 0. Whenever
28940 we got a circuit-level sendme, we were reading a lot on each
28941 socket, but only writing out a bit. So we would eventually reach
28942 eof. This would be noticed and acted on even when there were still
28943 bytes sitting in the inbuf.
28944 - When poll() is interrupted, we shouldn't believe the revents values.
28946 o Bugfixes on 0.0.9pre6:
28947 - Fix hibernate bug that caused pre6 to be broken.
28948 - Don't keep rephist info for routers that haven't had activity for
28949 24 hours. (This matters now that clients have keys, since we track
28951 - Never call close_temp_logs while validating log options.
28952 - Fix backslash-escaping on tor.sh.in and torctl.in.
28955 - Implement weekly/monthly/daily accounting: now you specify your
28956 hibernation properties by
28957 AccountingMax N bytes|KB|MB|GB|TB
28958 AccountingStart day|week|month [day] HH:MM
28959 Defaults to "month 1 0:00".
28960 - Let bandwidth and interval config options be specified as 5 bytes,
28961 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
28962 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
28963 get back to normal.)
28964 - If your requested entry or exit node has advertised bandwidth 0,
28966 - Be more greedy about filling up relay cells -- we try reading again
28967 once we've processed the stuff we read, in case enough has arrived
28968 to fill the last cell completely.
28969 - Apply NT service patch from Osamu Fujino. Still needs more work.
28972 Changes in version 0.0.9pre6 - 2004-11-15
28973 o Bugfixes on 0.0.8.1:
28974 - Fix assert failure on malformed socks4a requests.
28975 - Use identity comparison, not nickname comparison, to choose which
28976 half of circuit-ID-space each side gets to use. This is needed
28977 because sometimes we think of a router as a nickname, and sometimes
28978 as a hex ID, and we can't predict what the other side will do.
28979 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
28980 write() call will fail and we handle it there.
28981 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
28982 and smartlist_len, which are two major profiling offenders.
28984 o Bugfixes on 0.0.9pre5:
28985 - Fix a bug in read_all that was corrupting config files on windows.
28986 - When we're raising the max number of open file descriptors to
28987 'unlimited', don't log that we just raised it to '-1'.
28988 - Include event code with events, as required by control-spec.txt.
28989 - Don't give a fingerprint when clients do --list-fingerprint:
28990 it's misleading, because it will never be the same again.
28991 - Stop using strlcpy in tor_strndup, since it was slowing us
28993 - Remove warn on startup about missing cached-directory file.
28994 - Make kill -USR1 work again.
28995 - Hibernate if we start tor during the "wait for wakeup-time" phase
28996 of an accounting interval. Log our hibernation plans better.
28997 - Authoritative dirservers now also cache their directory, so they
28998 have it on start-up.
29001 - Fetch running-routers; cache running-routers; compress
29002 running-routers; serve compressed running-routers.z
29003 - Add NSI installer script contributed by J Doe.
29004 - Commit VC6 and VC7 workspace/project files.
29005 - Commit a tor.spec for making RPM files, with help from jbash.
29006 - Add contrib/torctl.in contributed by Glenn Fink.
29007 - Implement the control-spec's SAVECONF command, to write your
29008 configuration to torrc.
29009 - Get cookie authentication for the controller closer to working.
29010 - Include control-spec.txt in the tarball.
29011 - When set_conf changes our server descriptor, upload a new copy.
29012 But don't upload it too often if there are frequent changes.
29013 - Document authentication config in man page, and document signals
29015 - Clean up confusing parts of man page and torrc.sample.
29016 - Make expand_filename handle ~ and ~username.
29017 - Use autoconf to enable largefile support where necessary. Use
29018 ftello where available, since ftell can fail at 2GB.
29019 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
29020 log more informatively.
29021 - Give a slightly more useful output for "tor -h".
29022 - Refuse application socks connections to port 0.
29023 - Check clock skew for verified servers, but allow unverified
29024 servers and clients to have any clock skew.
29025 - Break DirFetchPostPeriod into:
29026 - DirFetchPeriod for fetching full directory,
29027 - StatusFetchPeriod for fetching running-routers,
29028 - DirPostPeriod for posting server descriptor,
29029 - RendPostPeriod for posting hidden service descriptors.
29030 - Make sure the hidden service descriptors are at a random offset
29031 from each other, to hinder linkability.
29034 Changes in version 0.0.9pre5 - 2004-11-09
29035 o Bugfixes on 0.0.9pre4:
29036 - Fix a seg fault in unit tests (doesn't affect main program).
29037 - Fix an assert bug where a hidden service provider would fail if
29038 the first hop of his rendezvous circuit was down.
29039 - Hidden service operators now correctly handle version 1 style
29040 INTRODUCE1 cells (nobody generates them still, so not a critical
29042 - If do_hup fails, actually notice.
29043 - Handle more errnos from accept() without closing the listener.
29044 Some OpenBSD machines were closing their listeners because
29045 they ran out of file descriptors.
29046 - Send resolve cells to exit routers that are running a new
29047 enough version of the resolve code to work right.
29048 - Better handling of winsock includes on non-MSV win32 compilers.
29049 - Some people had wrapped their tor client/server in a script
29050 that would restart it whenever it died. This did not play well
29051 with our "shut down if your version is obsolete" code. Now people
29052 don't fetch a new directory if their local cached version is
29054 - Make our autogen.sh work on ksh as well as bash.
29057 - Hibernation: New config option "AccountingMaxKB" lets you
29058 set how many KBytes per month you want to allow your server to
29059 consume. Rather than spreading those bytes out evenly over the
29060 month, we instead hibernate for some of the month and pop up
29061 at a deterministic time, work until the bytes are consumed, then
29062 hibernate again. Config option "MonthlyAccountingStart" lets you
29063 specify which day of the month your billing cycle starts on.
29064 - Control interface: a separate program can now talk to your
29065 client/server over a socket, and get/set config options, receive
29066 notifications of circuits and streams starting/finishing/dying,
29067 bandwidth used, etc. The next step is to get some GUIs working.
29068 Let us know if you want to help out. See doc/control-spec.txt .
29069 - Ship a contrib/tor-control.py as an example script to interact
29070 with the control port.
29071 - "tor --hash-password zzyxz" will output a salted password for
29072 use in authenticating to the control interface.
29073 - New log format in config:
29074 "Log minsev[-maxsev] stdout|stderr|syslog" or
29075 "Log minsev[-maxsev] file /var/foo"
29078 - DirPolicy config option, to let people reject incoming addresses
29079 from their dirserver.
29080 - "tor --list-fingerprint" will list your identity key fingerprint
29082 - Add "pass" target for RedirectExit, to make it easier to break
29083 out of a sequence of RedirectExit rules.
29084 - Clients now generate a TLS cert too, in preparation for having
29085 them act more like real nodes.
29086 - Ship src/win32/ in the tarball, so people can use it to build.
29087 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
29089 - New "router-status" line in directory, to better bind each verified
29090 nickname to its identity key.
29091 - Deprecate unofficial config option abbreviations, and abbreviations
29092 not on the command line.
29093 - Add a pure-C tor-resolve implementation.
29094 - Use getrlimit and friends to ensure we can reach MaxConn (currently
29095 1024) file descriptors.
29097 o Code security improvements, inspired by Ilja:
29098 - Replace sprintf with snprintf. (I think they were all safe, but
29100 - Replace strcpy/strncpy with strlcpy in more places.
29101 - Avoid strcat; use snprintf or strlcat instead.
29102 - snprintf wrapper with consistent (though not C99) overflow behavior.
29105 Changes in version 0.0.9pre4 - 2004-10-17
29106 o Bugfixes on 0.0.9pre3:
29107 - If the server doesn't specify an exit policy, use the real default
29108 exit policy, not reject *:*.
29109 - Ignore fascistfirewall when uploading/downloading hidden service
29110 descriptors, since we go through Tor for those; and when using
29111 an HttpProxy, since we assume it can reach them all.
29112 - When looking for an authoritative dirserver, use only the ones
29113 configured at boot. Don't bother looking in the directory.
29114 - The rest of the fix for get_default_conf_file() on older win32.
29115 - Make 'Routerfile' config option obsolete.
29118 - New 'MyFamily nick1,...' config option for a server to
29119 specify other servers that shouldn't be used in the same circuit
29120 with it. Only believed if nick1 also specifies us.
29121 - New 'NodeFamily nick1,nick2,...' config option for a client to
29122 specify nodes that it doesn't want to use in the same circuit.
29123 - New 'Redirectexit pattern address:port' config option for a
29124 server to redirect exit connections, e.g. to a local squid.
29127 Changes in version 0.0.9pre3 - 2004-10-13
29128 o Bugfixes on 0.0.8.1:
29129 - Better torrc example lines for dirbindaddress and orbindaddress.
29130 - Improved bounds checking on parsed ints (e.g. config options and
29131 the ones we find in directories.)
29132 - Better handling of size_t vs int, so we're more robust on 64
29134 - Fix the rest of the bug where a newly started OR would appear
29135 as unverified even after we've added his fingerprint and hupped
29137 - Fix a bug from 0.0.7: when read() failed on a stream, we would
29138 close it without sending back an end. So 'connection refused'
29139 would simply be ignored and the user would get no response.
29141 o Bugfixes on 0.0.9pre2:
29142 - Serving the cached-on-disk directory to people is bad. We now
29143 provide no directory until we've fetched a fresh one.
29144 - Workaround for bug on windows where cached-directories get crlf
29146 - Make get_default_conf_file() work on older windows too.
29147 - If we write a *:* exit policy line in the descriptor, don't write
29148 any more exit policy lines.
29151 - Use only 0.0.9pre1 and later servers for resolve cells.
29152 - Make the dirservers file obsolete.
29153 - Include a dir-signing-key token in directories to tell the
29154 parsing entity which key is being used to sign.
29155 - Remove the built-in bulky default dirservers string.
29156 - New config option "Dirserver %s:%d [fingerprint]", which can be
29157 repeated as many times as needed. If no dirservers specified,
29158 default to moria1,moria2,tor26.
29159 - Make moria2 advertise a dirport of 80, so people behind firewalls
29160 will be able to get a directory.
29161 - Http proxy support
29162 - Dirservers translate requests for http://%s:%d/x to /x
29163 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
29164 be routed through this host.
29165 - Clients ask for /tor/x rather than /x for new enough dirservers.
29166 This way we can one day coexist peacefully with apache.
29167 - Clients specify a "Host: %s%d" http header, to be compatible
29168 with more proxies, and so running squid on an exit node can work.
29171 Changes in version 0.0.8.1 - 2004-10-13
29173 - Fix a seg fault that can be triggered remotely for Tor
29174 clients/servers with an open dirport.
29175 - Fix a rare assert trigger, where routerinfos for entries in
29176 our cpath would expire while we're building the path.
29177 - Fix a bug in OutboundBindAddress so it (hopefully) works.
29178 - Fix a rare seg fault for people running hidden services on
29179 intermittent connections.
29180 - Fix a bug in parsing opt keywords with objects.
29181 - Fix a stale pointer assert bug when a stream detaches and
29183 - Fix a string format vulnerability (probably not exploitable)
29184 in reporting stats locally.
29185 - Fix an assert trigger: sometimes launching circuits can fail
29186 immediately, e.g. because too many circuits have failed recently.
29187 - Fix a compile warning on 64 bit platforms.
29190 Changes in version 0.0.9pre2 - 2004-10-03
29192 - Make fetching a cached directory work for 64-bit platforms too.
29193 - Make zlib.h a required header, not an optional header.
29196 Changes in version 0.0.9pre1 - 2004-10-01
29198 - Stop using separate defaults for no-config-file and
29199 empty-config-file. Now you have to explicitly turn off SocksPort,
29200 if you don't want it open.
29201 - Fix a bug in OutboundBindAddress so it (hopefully) works.
29202 - Improve man page to mention more of the 0.0.8 features.
29203 - Fix a rare seg fault for people running hidden services on
29204 intermittent connections.
29205 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
29207 - Fix more dns related bugs: send back resolve_failed and end cells
29208 more reliably when the resolve fails, rather than closing the
29209 circuit and then trying to send the cell. Also attach dummy resolve
29210 connections to a circuit *before* calling dns_resolve(), to fix
29211 a bug where cached answers would never be sent in RESOLVED cells.
29212 - When we run out of disk space, or other log writing error, don't
29213 crash. Just stop logging to that log and continue.
29214 - We were starting to daemonize before we opened our logs, so if
29215 there were any problems opening logs, we would complain to stderr,
29216 which wouldn't work, and then mysteriously exit.
29217 - Fix a rare bug where sometimes a verified OR would connect to us
29218 before he'd uploaded his descriptor, which would cause us to
29219 assign conn->nickname as though he's unverified. Now we look through
29220 the fingerprint list to see if he's there.
29221 - Fix a rare assert trigger, where routerinfos for entries in
29222 our cpath would expire while we're building the path.
29225 - Clients can ask dirservers for /dir.z to get a compressed version
29226 of the directory. Only works for servers running 0.0.9, of course.
29227 - Make clients cache directories and use them to seed their router
29228 lists at startup. This means clients have a datadir again.
29229 - Configuration infrastructure support for warning on obsolete
29231 - Respond to content-encoding headers by trying to uncompress as
29233 - Reply with a deflated directory when a client asks for "dir.z".
29234 We could use allow-encodings instead, but allow-encodings isn't
29235 specified in HTTP 1.0.
29236 - Raise the max dns workers from 50 to 100.
29237 - Discourage people from setting their dirfetchpostperiod more often
29238 than once per minute.
29239 - Protect dirservers from overzealous descriptor uploading -- wait
29240 10 seconds after directory gets dirty, before regenerating.
29243 Changes in version 0.0.8 - 2004-08-25
29244 o Port it to SunOS 5.9 / Athena
29247 Changes in version 0.0.8rc2 - 2004-08-20
29248 o Make it compile on cygwin again.
29249 o When picking unverified routers, skip those with low uptime and/or
29250 low bandwidth, depending on what properties you care about.
29253 Changes in version 0.0.8rc1 - 2004-08-18
29254 o Changes from 0.0.7.3:
29256 - Fix assert triggers: if the other side returns an address 0.0.0.0,
29257 don't put it into the client dns cache.
29258 - If a begin failed due to exit policy, but we believe the IP address
29259 should have been allowed, switch that router to exitpolicy reject *:*
29260 until we get our next directory.
29262 - Clients choose nodes proportional to advertised bandwidth.
29263 - Avoid using nodes with low uptime as introduction points.
29264 - Handle servers with dynamic IP addresses: don't replace
29265 options->Address with the resolved one at startup, and
29266 detect our address right before we make a routerinfo each time.
29267 - 'FascistFirewall' option to pick dirservers and ORs on specific
29268 ports; plus 'FirewallPorts' config option to tell FascistFirewall
29269 which ports are open. (Defaults to 80,443)
29270 - Be more aggressive about trying to make circuits when the network
29271 has changed (e.g. when you unsuspend your laptop).
29272 - Check for time skew on http headers; report date in response to
29274 - If the entrynode config line has only one node, don't pick it as
29276 - Add strict{entry|exit}nodes config options. If set to 1, then
29277 we refuse to build circuits that don't include the specified entry
29279 - OutboundBindAddress config option, to bind to a specific
29280 IP address for outgoing connect()s.
29281 - End truncated log entries (e.g. directories) with "[truncated]".
29283 o Patches to 0.0.8preX:
29285 - Patches to compile and run on win32 again (maybe)?
29286 - Fix crash when looking for ~/.torrc with no $HOME set.
29287 - Fix a race bug in the unit tests.
29288 - Handle verified/unverified name collisions better when new
29289 routerinfo's arrive in a directory.
29290 - Sometimes routers were getting entered into the stats before
29291 we'd assigned their identity_digest. Oops.
29292 - Only pick and establish intro points after we've gotten a
29295 - AllowUnverifiedNodes config option to let circuits choose no-name
29296 routers in entry,middle,exit,introduction,rendezvous positions.
29297 Allow middle and rendezvous positions by default.
29298 - Add a man page for tor-resolve.
29301 Changes in version 0.0.7.3 - 2004-08-12
29302 o Stop dnsworkers from triggering an assert failure when you
29303 ask them to resolve the host "".
29306 Changes in version 0.0.8pre3 - 2004-08-09
29307 o Changes from 0.0.7.2:
29308 - Allow multiple ORs with same nickname in routerlist -- now when
29309 people give us one identity key for a nickname, then later
29310 another, we don't constantly complain until the first expires.
29311 - Remember used bandwidth (both in and out), and publish 15-minute
29312 snapshots for the past day into our descriptor.
29313 - You can now fetch $DIRURL/running-routers to get just the
29314 running-routers line, not the whole descriptor list. (But
29315 clients don't use this yet.)
29316 - When people mistakenly use Tor as an http proxy, point them
29317 at the tor-doc.html rather than the INSTALL.
29318 - Remove our mostly unused -- and broken -- hex_encode()
29319 function. Use base16_encode() instead. (Thanks to Timo Lindfors
29320 for pointing out this bug.)
29321 - Rotate onion keys every 12 hours, not every 2 hours, so we have
29322 fewer problems with people using the wrong key.
29323 - Change the default exit policy to reject the default edonkey,
29324 kazaa, gnutella ports.
29325 - Add replace_file() to util.[ch] to handle win32's rename().
29327 o Changes from 0.0.8preX:
29328 - Fix two bugs in saving onion keys to disk when rotating, so
29329 hopefully we'll get fewer people using old onion keys.
29330 - Fix an assert error that was making SocksPolicy not work.
29331 - Be willing to expire routers that have an open dirport -- it's
29332 just the authoritative dirservers we want to not forget.
29333 - Reject tor-resolve requests for .onion addresses early, so we
29334 don't build a whole rendezvous circuit and then fail.
29335 - When you're warning a server that he's unverified, don't cry
29336 wolf unpredictably.
29337 - Fix a race condition: don't try to extend onto a connection
29338 that's still handshaking.
29339 - For servers in clique mode, require the conn to be open before
29340 you'll choose it for your path.
29341 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
29342 end relay cell, etc.
29343 - Measure bandwidth capacity over the last 24 hours, not just 12
29344 - Bugfix: authoritative dirservers were making and signing a new
29345 directory for each client, rather than reusing the cached one.
29348 Changes in version 0.0.8pre2 - 2004-08-04
29349 o Changes from 0.0.7.2:
29351 - Check directory signature _before_ you decide whether you're
29352 you're running an obsolete version and should exit.
29353 - Check directory signature _before_ you parse the running-routers
29354 list to decide who's running or verified.
29355 - Bugfixes and features:
29356 - Check return value of fclose while writing to disk, so we don't
29357 end up with broken files when servers run out of disk space.
29358 - Log a warning if the user uses an unsafe socks variant, so people
29359 are more likely to learn about privoxy or socat.
29360 - Dirservers now include RFC1123-style dates in the HTTP headers,
29361 which one day we will use to better detect clock skew.
29363 o Changes from 0.0.8pre1:
29364 - Make it compile without warnings again on win32.
29365 - Log a warning if you're running an unverified server, to let you
29366 know you might want to get it verified.
29367 - Only pick a default nickname if you plan to be a server.
29370 Changes in version 0.0.8pre1 - 2004-07-23
29372 - Made our unit tests compile again on OpenBSD 3.5, and tor
29373 itself compile again on OpenBSD on a sparc64.
29374 - We were neglecting milliseconds when logging on win32, so
29375 everything appeared to happen at the beginning of each second.
29377 o Protocol changes:
29378 - 'Extend' relay cell payloads now include the digest of the
29379 intended next hop's identity key. Now we can verify that we're
29380 extending to the right router, and also extend to routers we
29381 hadn't heard of before.
29384 - Tor nodes can now act as relays (with an advertised ORPort)
29385 without being manually verified by the dirserver operators.
29386 - Uploaded descriptors of unverified routers are now accepted
29387 by the dirservers, and included in the directory.
29388 - Verified routers are listed by nickname in the running-routers
29389 list; unverified routers are listed as "$<fingerprint>".
29390 - We now use hash-of-identity-key in most places rather than
29391 nickname or addr:port, for improved security/flexibility.
29392 - To avoid Sybil attacks, paths still use only verified servers.
29393 But now we have a chance to play around with hybrid approaches.
29394 - Nodes track bandwidth usage to estimate capacity (not used yet).
29395 - ClientOnly option for nodes that never want to become servers.
29396 - Directory caching.
29397 - "AuthoritativeDir 1" option for the official dirservers.
29398 - Now other nodes (clients and servers) will cache the latest
29399 directory they've pulled down.
29400 - They can enable their DirPort to serve it to others.
29401 - Clients will pull down a directory from any node with an open
29402 DirPort, and check the signature/timestamp correctly.
29403 - Authoritative dirservers now fetch directories from other
29404 authdirservers, to stay better synced.
29405 - Running-routers list tells who's down also, along with noting
29406 if they're verified (listed by nickname) or unverified (listed
29408 - Allow dirservers to serve running-router list separately.
29409 This isn't used yet.
29410 - ORs connect-on-demand to other ORs
29411 - If you get an extend cell to an OR you're not connected to,
29412 connect, handshake, and forward the create cell.
29413 - The authoritative dirservers stay connected to everybody,
29414 and everybody stays connected to 0.0.7 servers, but otherwise
29415 clients/servers expire unused connections after 5 minutes.
29416 - When servers get a sigint, they delay 30 seconds (refusing new
29417 connections) then exit. A second sigint causes immediate exit.
29418 - File and name management:
29419 - Look for .torrc if no CONFDIR "torrc" is found.
29420 - If no datadir is defined, then choose, make, and secure ~/.tor
29422 - If torrc not found, exitpolicy reject *:*.
29423 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
29424 - If no nickname is defined, derive default from hostname.
29425 - Rename secret key files, e.g. identity.key -> secret_id_key,
29426 to discourage people from mailing their identity key to tor-ops.
29427 - Refuse to build a circuit before the directory has arrived --
29428 it won't work anyway, since you won't know the right onion keys
29430 - Try other dirservers immediately if the one you try is down. This
29431 should tolerate down dirservers better now.
29432 - Parse tor version numbers so we can do an is-newer-than check
29433 rather than an is-in-the-list check.
29434 - New socks command 'resolve', to let us shim gethostbyname()
29436 - A 'tor_resolve' script to access the socks resolve functionality.
29437 - A new socks-extensions.txt doc file to describe our
29438 interpretation and extensions to the socks protocols.
29439 - Add a ContactInfo option, which gets published in descriptor.
29440 - Publish OR uptime in descriptor (and thus in directory) too.
29441 - Write tor version at the top of each log file
29442 - New docs in the tarball:
29444 - Document that you should proxy your SSL traffic too.
29447 Changes in version 0.0.7.2 - 2004-07-07
29448 o A better fix for the 0.0.0.0 problem, that will hopefully
29449 eliminate the remaining related assertion failures.
29452 Changes in version 0.0.7.1 - 2004-07-04
29453 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
29454 since internally we use 0.0.0.0 to signify "not yet resolved".
29457 Changes in version 0.0.7 - 2004-06-07
29458 o Updated the man page to reflect the new features.
29461 Changes in version 0.0.7rc2 - 2004-06-06
29462 o Changes from 0.0.7rc1:
29463 - Make it build on Win32 again.
29464 o Changes from 0.0.6.2:
29465 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
29469 Changes in version 0.0.7rc1 - 2004-06-02
29471 - On sighup, we were adding another log without removing the first
29472 one. So log messages would get duplicated n times for n sighups.
29473 - Several cases of using a connection after we'd freed it. The
29474 problem was that connections that are pending resolve are in both
29475 the pending_resolve tree, and also the circuit's resolving_streams
29476 list. When you want to remove one, you must remove it from both.
29477 - Fix a double-mark-for-close where an end cell arrived for a
29478 resolving stream, and then the resolve failed.
29479 - Check directory signatures based on name of signer, not on whom
29480 we got the directory from. This will let us cache directories more
29483 - Crank up some of our constants to handle more users.
29486 Changes in version 0.0.7pre1 - 2004-06-02
29487 o Fixes for crashes and other obnoxious bugs:
29488 - Fix an epipe bug: sometimes when directory connections failed
29489 to connect, we would give them a chance to flush before closing
29491 - When we detached from a circuit because of resolvefailed, we
29492 would immediately try the same circuit twice more, and then
29493 give up on the resolve thinking we'd tried three different
29495 - Limit the number of intro circuits we'll attempt to build for a
29496 hidden service per 15-minute period.
29497 - Check recommended-software string *early*, before actually parsing
29498 the directory. Thus we can detect an obsolete version and exit,
29499 even if the new directory format doesn't parse.
29500 o Fixes for security bugs:
29501 - Remember which nodes are dirservers when you startup, and if a
29502 random OR enables his dirport, don't automatically assume he's
29503 a trusted dirserver.
29505 - Directory connections were asking the wrong poll socket to
29506 start writing, and not asking themselves to start writing.
29507 - When we detached from a circuit because we sent a begin but
29508 didn't get a connected, we would use it again the first time;
29509 but after that we would correctly switch to a different one.
29510 - Stop warning when the first onion decrypt attempt fails; they
29511 will sometimes legitimately fail now that we rotate keys.
29512 - Override unaligned-access-ok check when $host_cpu is ia64 or
29513 arm. Apparently they allow it but the kernel whines.
29514 - Dirservers try to reconnect periodically too, in case connections
29516 - Fix some memory leaks in directory servers.
29517 - Allow backslash in Win32 filenames.
29518 - Made Tor build complain-free on FreeBSD, hopefully without
29519 breaking other BSD builds. We'll see.
29521 - Doxygen markup on all functions and global variables.
29522 - Make directory functions update routerlist, not replace it. So
29523 now directory disagreements are not so critical a problem.
29524 - Remove the upper limit on number of descriptors in a dirserver's
29525 directory (not that we were anywhere close).
29526 - Allow multiple logfiles at different severity ranges.
29527 - Allow *BindAddress to specify ":port" rather than setting *Port
29528 separately. Allow multiple instances of each BindAddress config
29529 option, so you can bind to multiple interfaces if you want.
29530 - Allow multiple exit policy lines, which are processed in order.
29531 Now we don't need that huge line with all the commas in it.
29532 - Enable accept/reject policies on SOCKS connections, so you can bind
29533 to 0.0.0.0 but still control who can use your OP.
29536 Changes in version 0.0.6.2 - 2004-05-16
29537 o Our integrity-checking digest was checking only the most recent cell,
29538 not the previous cells like we'd thought.
29539 Thanks to Stefan Mark for finding the flaw!
29542 Changes in version 0.0.6.1 - 2004-05-06
29543 o Fix two bugs in our AES counter-mode implementation (this affected
29544 onion-level stream encryption, but not TLS-level). It turns
29545 out we were doing something much more akin to a 16-character
29546 polyalphabetic cipher. Oops.
29547 Thanks to Stefan Mark for finding the flaw!
29548 o Retire moria3 as a directory server, and add tor26 as a directory
29552 Changes in version 0.0.6 - 2004-05-02
29553 [version bump only]
29556 Changes in version 0.0.6rc4 - 2004-05-01
29557 o Update the built-in dirservers list to use the new directory format
29558 o Fix a rare seg fault: if a node offering a hidden service attempts
29559 to build a circuit to Alice's rendezvous point and fails before it
29560 reaches the last hop, it retries with a different circuit, but
29562 o Handle windows socket errors correctly.
29565 Changes in version 0.0.6rc3 - 2004-04-28
29566 o Don't expire non-general excess circuits (if we had enough
29567 circuits open, we were expiring rendezvous circuits -- even
29568 when they had a stream attached. oops.)
29569 o Fetch randomness from /dev/urandom better (not via fopen/fread)
29570 o Better debugging for tls errors
29571 o Some versions of openssl have an SSL_pending function that erroneously
29572 returns bytes when there is a non-application record pending.
29573 o Set Content-Type on the directory and hidserv descriptor.
29574 o Remove IVs from cipher code, since AES-ctr has none.
29575 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
29576 o We were using an array of length zero in a few places.
29577 o win32's gethostbyname can't resolve an IP to an IP.
29578 o win32's close can't close a socket.
29581 Changes in version 0.0.6rc2 - 2004-04-26
29582 o Fix a bug where we were closing tls connections intermittently.
29583 It turns out openssl keeps its errors around -- so if an error
29584 happens, and you don't ask about it, and then another openssl
29585 operation happens and succeeds, and you ask if there was an error,
29586 it tells you about the first error. Fun fun.
29587 o Fix a bug that's been lurking since 27 may 03 (!)
29588 When passing back a destroy cell, we would use the wrong circ id.
29589 'Mostly harmless', but still worth fixing.
29590 o Since we don't support truncateds much, don't bother sending them;
29591 just close the circ.
29592 o check for <machine/limits.h> so we build on NetBSD again (I hope).
29593 o don't crash if a conn that sent a begin has suddenly lost its circuit
29594 (this was quite rare).
29597 Changes in version 0.0.6rc1 - 2004-04-25
29598 o We now rotate link (tls context) keys and onion keys.
29599 o CREATE cells now include oaep padding, so you can tell
29600 if you decrypted them correctly.
29601 o Add bandwidthburst to server descriptor.
29602 o Directories now say which dirserver signed them.
29603 o Use a tor_assert macro that logs failed assertions too.
29606 Changes in version 0.0.6pre5 - 2004-04-18
29607 o changes from 0.0.6pre4:
29608 - make tor build on broken freebsd 5.2 installs
29609 - fix a failed assert when you try an intro point, get a nack, and try
29610 a second one and it works.
29611 - when alice uses a port that the hidden service doesn't accept,
29612 it now sends back an end cell (denied by exit policy). otherwise
29613 alice would just have to wait to time out.
29614 - fix another rare bug: when we had tried all the intro
29615 points for a hidden service, we fetched the descriptor
29616 again, but we left our introcirc thinking it had already
29617 sent an intro, so it kept waiting for a response...
29618 - bugfix: when you sleep your hidden-service laptop, as soon
29619 as it wakes up it tries to upload a service descriptor, but
29620 socketpair fails for some reason (localhost not up yet?).
29621 now we simply give up on that upload, and we'll try again later.
29622 i'd still like to find the bug though.
29623 - if an intro circ waiting for an ack dies before getting one, then
29625 - we were reusing stale service descriptors and refetching usable
29629 Changes in version 0.0.6pre4 - 2004-04-14
29630 o changes from 0.0.6pre3:
29631 - when bob fails to connect to the rendezvous point, and his
29632 circ didn't fail because of the rendezvous point itself, then
29633 he retries a couple of times
29634 - we expire introduction and rendezvous circs more thoroughly
29635 (sometimes they were hanging around forever)
29636 - we expire unattached rendezvous streams that have been around
29637 too long (they were sticking around forever).
29638 - fix a measly fencepost error that was crashing everybody with
29642 Changes in version 0.0.6pre3 - 2004-04-14
29643 o changes from 0.0.6pre2:
29644 - make hup work again
29645 - fix some memory leaks for dirservers
29646 - allow more skew in rendezvous descriptor timestamps, to help
29647 handle people like blanu who don't know what time it is
29648 - normal circs are 3 hops, but some rend/intro circs are 4, if
29649 the initiator doesn't get to choose the last hop
29650 - send acks for introductions, so alice can know whether to try
29652 - bob publishes intro points more correctly
29653 o changes from 0.0.5:
29654 - fix an assert trigger that's been plaguing us since the days
29655 of 0.0.2prexx (thanks weasel!)
29656 - retry stream correctly when we fail to connect because of
29657 exit-policy-reject (should try another) or can't-resolve-address
29658 (also should try another, because dns on random internet servers
29660 - when we hup a dirserver and we've *removed* a server from the
29661 approved-routers list, now we remove that server from the
29662 in-memory directories too
29665 Changes in version 0.0.6pre2 - 2004-04-08
29666 o We fixed our base32 implementation. Now it works on all architectures.
29669 Changes in version 0.0.6pre1 - 2004-04-08
29671 - Hidden services and rendezvous points are implemented. Go to
29672 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
29673 hidden services. (This only works via a socks4a proxy such as
29674 Privoxy, and currently it's quite slow.)
29677 Changes in version 0.0.5 - 2004-03-30
29678 [version bump only]
29681 Changes in version 0.0.5rc3 - 2004-03-29
29682 o Install torrc as torrc.sample -- we no longer clobber your
29684 o Re-enable recommendedversion checking (we broke it in rc2, oops)
29685 o Add in a 'notice' log level for things the operator should hear
29686 but that aren't warnings
29689 Changes in version 0.0.5rc2 - 2004-03-29
29690 o Hold socks connection open until reply is flushed (if possible)
29691 o Make exit nodes resolve IPs to IPs immediately, rather than asking
29692 the dns farm to do it.
29693 o Fix c99 aliasing warnings in rephist.c
29694 o Don't include server descriptors that are older than 24 hours in the
29696 o Give socks 'reject' replies their whole 15s to attempt to flush,
29697 rather than seeing the 60s timeout and assuming the flush had failed.
29698 o Clean automake droppings from the cvs repository
29701 Changes in version 0.0.5rc1 - 2004-03-28
29702 o Fix mangled-state bug in directory fetching (was causing sigpipes).
29703 o Only build circuits after we've fetched the directory: clients were
29704 using only the directory servers before they'd fetched a directory.
29705 This also means longer startup time; so it goes.
29706 o Fix an assert trigger where an OP would fail to handshake, and we'd
29707 expect it to have a nickname.
29708 o Work around a tsocks bug: do a socks reject when AP connection dies
29709 early, else tsocks goes into an infinite loop.
29712 Changes in version 0.0.4 - 2004-03-26
29713 o When connecting to a dirserver or OR and the network is down,
29717 Changes in version 0.0.3 - 2004-03-26
29718 o Warn and fail if server chose a nickname with illegal characters
29719 o Port to Solaris and Sparc:
29720 - include missing header fcntl.h
29721 - have autoconf find -lsocket -lnsl automatically
29722 - deal with hardware word alignment
29723 - make uname() work (solaris has a different return convention)
29724 - switch from using signal() to sigaction()
29725 o Preliminary work on reputation system:
29726 - Keep statistics on success/fail of connect attempts; they're published
29727 by kill -USR1 currently.
29728 - Add a RunTesting option to try to learn link state by creating test
29729 circuits, even when SocksPort is off.
29730 - Remove unused open circuits when there are too many.
29733 Changes in version 0.0.2 - 2004-03-19
29734 - Include strlcpy and strlcat for safer string ops
29735 - define INADDR_NONE so we compile (but still not run) on solaris
29738 Changes in version 0.0.2pre27 - 2004-03-14
29740 - Allow internal tor networks (we were rejecting internal IPs,
29741 now we allow them if they're set explicitly).
29742 - And fix a few endian issues.
29745 Changes in version 0.0.2pre26 - 2004-03-14
29747 - If a stream times out after 15s without a connected cell, don't
29748 try that circuit again: try a new one.
29749 - Retry streams at most 4 times. Then give up.
29750 - When a dirserver gets a descriptor from an unknown router, it
29751 logs its fingerprint (so the dirserver operator can choose to
29752 accept it even without mail from the server operator).
29753 - Inform unapproved servers when we reject their descriptors.
29754 - Make tor build on Windows again. It works as a client, who knows
29756 - Clearer instructions in the torrc for how to set up a server.
29757 - Be more efficient about reading fd's when our global token bucket
29758 (used for rate limiting) becomes empty.
29760 - Stop asserting that computers always go forward in time. It's
29762 - When we sent a cell (e.g. destroy) and then marked an OR connection
29763 expired, we might close it before finishing a flush if the other
29764 side isn't reading right then.
29765 - Don't allow dirservers to start if they haven't defined
29766 RecommendedVersions
29767 - We were caching transient dns failures. Oops.
29768 - Prevent servers from publishing an internal IP as their address.
29769 - Address a strcat vulnerability in circuit.c
29772 Changes in version 0.0.2pre25 - 2004-03-04
29774 - Put the OR's IP in its router descriptor, not its fqdn. That way
29775 we'll stop being stalled by gethostbyname for nodes with flaky dns,
29778 - If the user typed in an address that didn't resolve, the server
29782 Changes in version 0.0.2pre24 - 2004-03-03
29784 - Fix an assertion failure in dns.c, where we were trying to dequeue
29785 a pending dns resolve even if it wasn't pending
29786 - Fix a spurious socks5 warning about still trying to write after the
29787 connection is finished.
29788 - Hold certain marked_for_close connections open until they're finished
29789 flushing, rather than losing bytes by closing them too early.
29790 - Correctly report the reason for ending a stream
29791 - Remove some duplicate calls to connection_mark_for_close
29792 - Put switch_id and start_daemon earlier in the boot sequence, so it
29793 will actually try to chdir() to options.DataDirectory
29794 - Make 'make test' exit(1) if a test fails; fix some unit tests
29795 - Make tor fail when you use a config option it doesn't know about,
29796 rather than warn and continue.
29797 - Make --version work
29798 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
29801 Changes in version 0.0.2pre23 - 2004-02-29
29803 - Print a statement when the first circ is finished, so the user
29804 knows it's working.
29805 - If a relay cell is unrecognized at the end of the circuit,
29806 send back a destroy. (So attacks to mutate cells are more
29808 - New config option 'excludenodes' to avoid certain nodes for circuits.
29809 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
29810 so you can collect coredumps there.
29812 - Fix a bug in tls flushing where sometimes data got wedged and
29813 didn't flush until more data got sent. Hopefully this bug was
29814 a big factor in the random delays we were seeing.
29815 - Make 'connected' cells include the resolved IP, so the client
29816 dns cache actually gets populated.
29817 - Disallow changing from ORPort=0 to ORPort>0 on hup.
29818 - When we time-out on a stream and detach from the circuit, send an
29819 end cell down it first.
29820 - Only warn about an unknown router (in exitnodes, entrynodes,
29821 excludenodes) after we've fetched a directory.
29824 Changes in version 0.0.2pre22 - 2004-02-26
29826 - Servers publish less revealing uname information in descriptors.
29827 - More memory tracking and assertions, to crash more usefully when
29829 - If the default torrc isn't there, just use some default defaults.
29830 Plus provide an internal dirservers file if they don't have one.
29831 - When the user tries to use Tor as an http proxy, give them an http
29832 501 failure explaining that we're a socks proxy.
29833 - Dump a new router.desc on hup, to help confused people who change
29834 their exit policies and then wonder why router.desc doesn't reflect
29836 - Clean up the generic tor.sh init script that we ship with.
29838 - If the exit stream is pending on the resolve, and a destroy arrives,
29839 then the stream wasn't getting removed from the pending list. I
29840 think this was the one causing recent server crashes.
29841 - Use a more robust poll on OSX 10.3, since their poll is flaky.
29842 - When it couldn't resolve any dirservers, it was useless from then on.
29843 Now it reloads the RouterFile (or default dirservers) if it has no
29845 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
29846 many users don't even *have* a /usr/local/sbin/.
29849 Changes in version 0.0.2pre21 - 2004-02-18
29851 - There's a ChangeLog file that actually reflects the changelog.
29852 - There's a 'torify' wrapper script, with an accompanying
29853 tor-tsocks.conf, that simplifies the process of using tsocks for
29854 tor. It even has a man page.
29855 - The tor binary gets installed to sbin rather than bin now.
29856 - Retry streams where the connected cell hasn't arrived in 15 seconds
29857 - Clean up exit policy handling -- get the default out of the torrc,
29858 so we can update it without forcing each server operator to fix
29860 - Allow imaps and pop3s in default exit policy
29862 - Prevent picking middleman nodes as the last node in the circuit
29865 Changes in version 0.0.2pre20 - 2004-01-30
29867 - We now have a deb package, and it's in debian unstable. Go to
29868 it, apt-getters. :)
29869 - I've split the TotalBandwidth option into BandwidthRate (how many
29870 bytes per second you want to allow, long-term) and
29871 BandwidthBurst (how many bytes you will allow at once before the cap
29872 kicks in). This better token bucket approach lets you, say, set
29873 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
29874 performance while not exceeding your monthly bandwidth quota.
29875 - Push out a tls record's worth of data once you've got it, rather
29876 than waiting until you've read everything waiting to be read. This
29877 may improve performance by pipelining better. We'll see.
29878 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
29879 from failed circuits (if they haven't been connected yet) and attach
29881 - Expire old streams that haven't managed to connect. Some day we'll
29882 have them reattach to new circuits instead.
29885 - Fix several memory leaks that were causing servers to become bloated
29887 - Fix a few very rare assert triggers. A few more remain.
29888 - Setuid to User _before_ complaining about running as root.
29891 Changes in version 0.0.2pre19 - 2004-01-07
29893 - Fix deadlock condition in dns farm. We were telling a child to die by
29894 closing the parent's file descriptor to him. But newer children were
29895 inheriting the open file descriptor from the parent, and since they
29896 weren't closing it, the socket never closed, so the child never read
29897 eof, so he never knew to exit. Similarly, dns workers were holding
29898 open other sockets, leading to all sorts of chaos.
29899 - New cleaner daemon() code for forking and backgrounding.
29900 - If you log to a file, it now prints an entry at the top of the
29901 logfile so you know it's working.
29902 - The onionskin challenge length was 30 bytes longer than necessary.
29903 - Started to patch up the spec so it's not quite so out of date.
29906 Changes in version 0.0.2pre18 - 2004-01-02
29908 - Fix endian issues with the 'integrity' field in the relay header.
29909 - Fix a potential bug where connections in state
29910 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
29913 Changes in version 0.0.2pre17 - 2003-12-30
29915 - Made --debuglogfile (or any second log file, actually) work.
29916 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
29917 adversary could force us into an infinite loop.
29920 - Each onionskin handshake now includes a hash of the computed key,
29921 to prove the server's identity and help perfect forward secrecy.
29922 - Changed cell size from 256 to 512 bytes (working toward compatibility
29924 - Changed cell length to 2 bytes, and moved it to the relay header.
29925 - Implemented end-to-end integrity checking for the payloads of
29927 - Separated streamid from 'recognized' (otherwise circuits will get
29928 messed up when we try to have streams exit from the middle). We
29929 use the integrity-checking to confirm that a cell is addressed to
29931 - Randomize the initial circid and streamid values, so an adversary who
29932 breaks into a node can't learn how many circuits or streams have
29936 Changes in version 0.0.2pre16 - 2003-12-14
29938 - Fixed a bug that made HUP trigger an assert
29939 - Fixed a bug where a circuit that immediately failed wasn't being
29940 counted as a failed circuit in counting retries.
29943 - Now we close the circuit when we get a truncated cell: otherwise we're
29944 open to an anonymity attack where a bad node in the path truncates
29945 the circuit and then we open streams at him.
29946 - Add port ranges to exit policies
29947 - Add a conservative default exit policy
29948 - Warn if you're running tor as root
29949 - on HUP, retry OR connections and close/rebind listeners
29950 - options.EntryNodes: try these nodes first when picking the first node
29951 - options.ExitNodes: if your best choices happen to include any of
29952 your preferred exit nodes, you choose among just those preferred
29954 - options.ExcludedNodes: nodes that are never picked in path building
29957 Changes in version 0.0.2pre15 - 2003-12-03
29958 o Robustness and bugfixes:
29959 - Sometimes clients would cache incorrect DNS resolves, which would
29960 really screw things up.
29961 - An OP that goes offline would slowly leak all its sockets and stop
29963 - A wide variety of bugfixes in exit node selection, exit policy
29964 handling, and processing pending streams when a new circuit is
29966 - Pick nodes for a path only from those the directory says are up
29967 - Choose randomly from all running dirservers, not always the first one
29968 - Increase allowed http header size for directory fetch.
29969 - Stop writing to stderr (if we're daemonized it will be closed).
29970 - Enable -g always, so cores will be more useful to me.
29971 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
29974 - Wrote a man page. It lists commonly used options.
29977 - Change default loglevel to warn.
29978 - Make PidFile default to null rather than littering in your CWD.
29979 - OnionRouter config option is now obsolete. Instead it just checks
29981 - Moved to a single unified torrc file for both clients and servers.
29984 Changes in version 0.0.2pre14 - 2003-11-29
29985 o Robustness and bugfixes:
29986 - Force the admin to make the DataDirectory himself
29987 - to get ownership/permissions right
29988 - so clients no longer make a DataDirectory and then never use it
29989 - fix bug where a client who was offline for 45 minutes would never
29990 pull down a directory again
29991 - fix (or at least hide really well) the dns assert bug that was
29992 causing server crashes
29993 - warnings and improved robustness wrt clockskew for certs
29994 - use the native daemon(3) to daemonize, when available
29995 - exit if bind() fails
29996 - exit if neither socksport nor orport is defined
29997 - include our own tor_timegm (Win32 doesn't have its own)
29998 - bugfix for win32 with lots of connections
29999 - fix minor bias in PRNG
30000 - make dirserver more robust to corrupt cached directory
30003 - Wrote the design document (woo)
30005 o Circuit building and exit policies:
30006 - Circuits no longer try to use nodes that the directory has told them
30008 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
30009 bitcounts (18.0.0.0/8).
30010 - Make AP connections standby for a circuit if no suitable circuit
30011 exists, rather than failing
30012 - Circuits choose exit node based on addr/port, exit policies, and
30013 which AP connections are standing by
30014 - Bump min pathlen from 2 to 3
30015 - Relay end cells have a payload to describe why the stream ended.
30016 - If the stream failed because of exit policy, try again with a new
30018 - Clients have a dns cache to remember resolved addresses.
30019 - Notice more quickly when we have no working circuits
30022 - APPort is now called SocksPort
30023 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
30025 - RecommendedVersions is now a config variable rather than
30026 hardcoded (for dirservers)
30027 - Reloads config on HUP
30028 - Usage info on -h or --help
30029 - If you set User and Group config vars, it'll setu/gid to them.
30032 Changes in version 0.0.2pre13 - 2003-10-19
30033 o General stability:
30034 - SSL_write no longer fails when it returns WANTWRITE and the number
30035 of bytes in the buf has changed by the next SSL_write call.
30036 - Fix segfault fetching directory when network is down
30037 - Fix a variety of minor memory leaks
30038 - Dirservers reload the fingerprints file on HUP, so I don't have
30039 to take down the network when I approve a new router
30040 - Default server config file has explicit Address line to specify fqdn
30043 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
30044 - Make listener connections not ever alloc bufs
30046 o Autoconf improvements:
30047 - don't clobber an external CFLAGS in ./configure
30048 - Make install now works
30049 - create var/lib/tor on make install
30050 - autocreate a tor.sh initscript to help distribs
30051 - autocreate the torrc and sample-server-torrc with correct paths
30053 o Log files and Daemonizing now work:
30054 - If --DebugLogFile is specified, log to it at -l debug
30055 - If --LogFile is specified, use it instead of commandline
30056 - If --RunAsDaemon is set, tor forks and backgrounds on startup