1 Changes in version 0.3.5.1-alpha-2018-09-18
2 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
3 client authorization for modern (v3) onion services, improves
4 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
5 support for NSS in place of OpenSSL, and much more.
7 o Major features (onion services, UI change):
8 - For a newly created onion service, the default version is now 3.
9 Tor still supports existing version 2 services, but the operator
10 now needs to set "HiddenServiceVersion 2" in order to create a new
11 version 2 service. For existing services, Tor now learns the
12 version by reading the key file. Closes ticket 27215.
14 o Major features (relay, UI change):
15 - Relays no longer run as exits by default. If the "ExitRelay"
16 option is auto (or unset), and no exit policy is specified with
17 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
18 Previously in this case, we allowed exit traffic and logged a
19 warning message. Closes ticket 21530. Patch by Neel Chauhan.
21 o Major features (bootstrap):
22 - Don't report directory progress until after a connection to a
23 relay or bridge has succeeded. Previously, we'd report 80%
24 progress based on cached directory information when we couldn't
25 even connect to the network. Closes ticket 27169.
27 o Major features (new code layout):
28 - Nearly all of Tor's source code has been moved around into more
29 logical places. The "common" directory is now divided into a set
30 of libraries in "lib", and files in the "or" directory have been
31 split into "core" (logic absolutely needed for onion routing),
32 "feature" (independent modules in Tor), and "app" (to configure
33 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
34 more information. Closes ticket 26481.
36 This refactoring is not complete: although the libraries have been
37 refactored to be acyclic, the main body of Tor is still too
38 interconnected. We will attempt to improve this in the future.
40 o Major features (onion services v3):
41 - Implement onion service client authorization at the descriptor
42 level: only authorized clients can decrypt a service's descriptor
43 to find out how to contact it. A new torrc option was added to
44 control this client side: ClientOnionAuthDir <path>. On the
45 service side, if the "authorized_clients/" directory exists in the
46 onion service directory path, client configuration are read from
47 the files within. See the manpage for more details. Closes ticket
48 27547. Patch done by Suphanat Chunhapanya (haxxpop).
49 - Improve revision counter generation in next-gen onion services.
50 Onion services can now scale by hosting multiple instances on
51 different hosts without synchronization between them, which was
52 previously impossible because descriptors would get rejected by
53 HSDirs. Addresses ticket 25552.
55 o Major features (portability, cryptography, experimental, TLS):
56 - Tor now has the option to compile with the NSS library instead of
57 OpenSSL. This feature is experimental, and we expect that bugs may
58 remain. It is mainly intended for environments where Tor's
59 performance is not CPU-bound, and where NSS is already known to be
60 installed. To try it out, configure Tor with the --enable-nss
61 flag. Closes tickets 26631, 26815, and 26816.
63 If you are experimenting with this option and using an old cached
64 consensus, Tor may fail to start. To solve this, delete your
65 "cached-microdesc-consensus" file, and restart Tor.
67 o Major bugfixes (directory authority):
68 - Actually check that the address we get from DirAuthority
69 configuration line is valid IPv4. Explicitly disallow DirAuthority
70 adress to be a DNS hostname. Fixes bug 26488; bugfix
73 o Major bugfixes (restart-in-process):
74 - Fix a use-after-free error that could be caused by passing Tor an
75 impossible set of options that would fail during options_act().
76 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
78 o Minor features (admin tools):
79 - Add a new --key-expiration option to print the expiration date of
80 the signing cert in an ed25519_signing_cert file. Resolves
83 o Minor features (build):
84 - If you pass the "--enable-pic" option to configure, Tor will try
85 to tell the compiler to build position-independent code suitable
86 to link into a dynamic library. (The default remains -fPIE, for
87 code suitable for a relocatable executable.) Closes ticket 23846.
89 o Minor features (code correctness, testing):
90 - Tor's build process now includes a "check-includes" make target to
91 verify that no module of Tor relies on any headers from a higher-
92 level module. We hope to use this feature over time to help
93 refactor our codebase. Closes ticket 26447.
95 o Minor features (code layout):
96 - We have a new "lowest-level" error-handling API for use by code
97 invoked from within the logging module. With this interface, the
98 logging code is no longer at risk of calling into itself if a
99 failure occurs while it is trying to log something. Closes
102 o Minor features (compilation):
103 - Tor's configure script now supports a --with-malloc= option to
104 select your malloc implementation. Supported options are
105 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
106 default). Addresses part of ticket 20424. Based on a patch from
109 o Minor features (config):
110 - The "auto" keyword in torrc is now case-insensitive. Closes
113 o Minor features (continuous integration):
114 - Don't do a distcheck with --disable-module-dirauth in Travis.
115 Implements ticket 27252.
116 - Install libcap-dev and libseccomp2-dev so these optional
117 dependencies get tested on Travis CI. Closes ticket 26560.
118 - Only run one online rust build in Travis, to reduce network
119 errors. Skip offline rust builds on Travis for Linux gcc, because
120 they're redundant. Implements ticket 27252.
121 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
122 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
123 Linux with default settings, because all the non-default builds
124 use gcc on Linux. Implements ticket 27252.
126 o Minor features (controller):
127 - Emit CIRC_BW events as soon as we detect that we processed an
128 invalid or otherwise dropped cell on a circuit. This allows
129 vanguards and other controllers to react more quickly to dropped
130 cells. Closes ticket 27678.
131 - For purposes of CIRC_BW-based dropped cell detection, track half-
132 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
133 bias check cells to arrive without counting it as dropped until
134 either the END arrvies, or the windows are empty. Closes
136 - Implement a 'GETINFO md/all' controller command to enable getting
137 all known microdesriptors. Closes ticket 8323.
138 - The GETINFO command now support an "uptime" argument, to return
139 Tor's uptime in seconds. Closes ticket 25132.
141 o Minor features (denial-of-service avoidance):
142 - Make our OOM handler aware of the DNS cache so that it doesn't
143 fill up the memory. This check is important for our DoS mitigation
144 subsystem. Closes ticket 18642. Patch by Neel Chauhan
146 o Minor features (development):
147 - Tor's makefile now supports running the "clippy" Rust style tool
148 on our Rust code. Closes ticket 22156.
150 o Minor features (directory authority):
151 - There is no longer an artificial upper limit on the length of
152 bandwidth lines. Closes ticket 26223.
153 - When a bandwidth file is used to obtain the bandwidth measurements,
154 include this bandwidth file headers in the votes. Closes
156 - Improved support for networks with only a single authority or a
157 single fallback directory. Patch from Gabriel Somlo. Closes
160 o Minor features (embedding API):
161 - The Tor controller API now supports a function to launch Tor with
162 a preconstructed owning controller FD, so that embedding
163 applications don't need to manage controller ports and
164 authentication. Closes ticket 24204.
165 - The Tor controller API now has a function that returns the name
166 and version of the backend implementing the API. Closes
169 o Minor features (geoip):
170 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
171 Country database. Closes ticket 27631.
173 o Minor features (memory management):
174 - Get Libevent to use the same memory allocator as Tor, by calling
175 event_set_mem_functions() during initialization. Resolves
178 o Minor features (memory usage):
179 - When not using them, store legacy TAP public onion keys in DER-
180 encoded format, rather than as expanded public keys. This should
181 save several megabytes on typical clients. Closes ticket 27246.
183 o Minor features (OpenSSL):
184 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
185 than own own. Resolves ticket 19979.
187 o Minor features (Rust, code quality):
188 - Improve rust code quality in the rust protover implementation by
189 making it more idiomatic. Includes changing an internal API to
190 take &str instead of &String. Closes ticket 26492.
192 o Minor features (testing):
193 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
194 chutney. Implements ticket 27211.
196 o Minor features (tor-resolve):
197 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
198 Side-effect of the refactoring for ticket 26526.
200 o Minor features (UI):
201 - Log each included configuration file or directory as we read it,
202 to provide more visibility about where Tor is reading from. Patch
203 from Unto Sten; closes ticket 27186.
204 - Low log level of "Scheduler type KIST has been enabled" to INFO.
207 o Minor bugfixes (bootstrap):
208 - Try harder to get descriptors in non-exit test networks, by using
209 the mid weight for the third hop when there are no exits. Fixes
210 bug 27237; bugfix on 0.2.6.2-alpha.
212 o Minor bugfixes (C correctness):
213 - Avoid casting smartlist index to int implicitly, as it may trigger
214 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
215 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
216 - Use time_t for all values in
217 predicted_ports_prediction_time_remaining(). Rework the code that
218 computes difference between durations/timestamps. Fixes bug 27165;
219 bugfix on 0.3.1.1-alpha.
221 o Minor bugfixes (client, memory usage):
222 - When not running as a directory cache, there is no need to store
223 the text of the current consensus networkstatus in RAM.
224 Previously, however, clients would store it anyway, at a cost of
225 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
228 o Minor bugfixes (client, reachableaddresses):
229 - Instead of adding an "reject *:*" line to ReachableAddresses when
230 loading the configuration, add one to the policy after parsing it
231 in parse_reachable_addresses(). This prevents extra "reject *.*"
232 lines from accumulating on reloads. Fixes bug 20874; bugfix on
233 0.3.5.1-alpha. Patch by Neel Chauhan.
235 o Minor bugfixes (code quality):
236 - Rename sandbox_getaddrinfo() and other functions to no longer
237 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
238 bugfix on 0.2.7.1-alpha.
240 o Minor bugfixes (configuration, Onion Services):
241 - In rend_service_parse_port_config(), disallow any input to remain
242 after address-port pair was parsed. This will catch address and
243 port being whitespace-separated by mistake of the user. Fixes bug
244 27044; bugfix on 0.2.9.10.
246 o Minor bugfixes (continuous integration):
247 - Stop reinstalling identical packages in our Windows CI. Fixes bug
248 27464; bugfix on 0.3.4.1-alpha.
250 o Minor bugfixes (controller):
251 - Consider all routerinfo errors other than "not a server" to be
252 transient for the purpose of "GETINFO exit-policy/*" controller
253 request. Print stacktrace in the unlikely case of failing to
254 recompute routerinfo digest. Fixes bug 27034; bugfix
257 o Minor bugfixes (directory connection shutdown):
258 - Avoid a double-close when shutting down a stalled directory
259 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
261 o Minor bugfixes (HTTP tunnel):
262 - Fix a bug warning when closing an HTTP tunnel connection due to an
263 HTTP request we couldn't handle. Fixes bug 26470; bugfix
266 o Minor bugfixes (ipv6):
267 - In addrs_in_same_network_family(), we choose the subnet size based
268 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
269 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
270 15518; bugfix on 0.3.5.1-alpha. Patch by Neel Chauhan.
272 o Minor bugfixes (logging):
273 - As a precaution, do an early return from log_addr_has_changed() if
274 Tor is running as client. Also, log a stack trace for debugging as
275 this function should only be called when Tor runs as server. Fixes
276 bug 26892; bugfix on 0.1.1.9-alpha.
277 - Refrain from mentioning bug 21018 in the logs, as it is already
278 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
280 o Minor bugfixes (logging, documentation):
281 - When SafeLogging is enabled, scrub IP address in
282 channel_tls_process_netinfo_cell(). Also, add a note to manpage
283 that scrubbing is not guaranteed on loglevels below Notice. Fixes
284 bug 26882; bugfix on 0.2.4.10-alpha.
286 o Minor bugfixes (netflow padding):
287 - Ensure circuitmux queues are empty before scheduling or sending
288 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
290 o Minor bugfixes (onion service v2):
291 - Log at level "info", not "warning", in the case that we do not
292 have a consensus when a .onion request comes in. This can happen
293 normally while bootstrapping. Fixes bug 27040; bugfix
296 o Minor bugfixes (onion service v3):
297 - When the onion service directory can't be created or has the wrong
298 permissions, do not log a stack trace. Fixes bug 27335; bugfix
301 o Minor bugfixes (OS compatibility):
302 - Properly handle configuration changes that move a listener to/from
303 wildcard IP address. If the first attempt to bind a socket fails,
304 close the old listener and try binding the socket again. Fixes bug
305 17873; bugfix on 0.0.8pre-1.
307 o Minor bugfixes (performance)::
308 - Rework node_is_a_configured_bridge() to no longer call
309 node_get_all_orports(), which was performing too many memory
310 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
312 o Minor bugfixes (relay statistics):
313 - Update relay descriptor on bandwidth changes only when the uptime
314 is smaller than 24h, in order to reduce the efficiency of guard
315 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
317 o Minor bugfixes (relays):
318 - Consider the fact that we'll be making direct connections to our
319 entry and guard nodes when computing the fraction of nodes that
320 have their descriptors. Also, if we are using bridges and there is
321 at least one bridge with a full descriptor, treat the fraction of
322 guards available as 100%. Fixes bug 25886; bugfix on 0.3.5.1-alpha.
323 Patch by Neel Chauhan.
324 - Update the message logged on relays when DirCache is disabled.
325 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
326 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
328 o Minor bugfixes (rust, protover):
329 - Compute protover votes correctly in the rust version of the
330 protover code. Previously, the protover rewrite in 24031 allowed
331 repeated votes from the same voter for the same protocol version
332 to be counted multiple times in protover_compute_vote(). Fixes bug
333 27649; bugfix on 0.3.3.5-rc.
334 - Reject protover names that contain invalid characters. Fixes bug
335 27687; bugfix on 0.3.3.1-alpha.
337 o Minor bugfixes (testing):
338 - Fix two unit tests to work when HOME environment variable is not
339 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
340 - If a unit test running in a subprocess exits abnormally or with a
341 nonzero status code, treat the test as having failed, even if the
342 test reported success. Without this fix, memory leaks don't cause
343 cause the tests to fail, even with LeakSanitizer. Fixes bug 27658;
344 bugfix on 0.2.2.4-alpha.
345 - When logging a version mismatch in our openssl_version tests,
346 report the actual offending version strings. Fixes bug 26152;
347 bugfix on 0.2.9.1-alpha.
348 - Fix forking tests on Windows when there is a space somewhere in
349 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
351 o Minor bugfixes (torrc):
352 - Tor now validates that the ContactInfo config option is valid UTF-
353 8 when parsing torrc. Fixes bug 27428; bugfix on 0.0.8pre1.
355 o Code simplification and refactoring:
356 - 'updateFallbackDirs.py' now ignores the blacklist file as it's not
357 longer needed Closes ticket 26502.
358 - Include paths to header files within Tor are now qualified by
359 directory within the top-level src directory.
360 - Many structures have been removed from the centralized "or.h"
361 header, and moved into their own headers. This will allow us to
362 reduce the number of places in the code that rely on each
363 structure's contents and layout. Closes ticket 26383.
364 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
365 - Remove GetAdaptersAddresses_fn_t. The code that used it was
366 removed as part of the 26481 refactor. Closes ticket 27467.
367 - Rework Tor SOCKS server code to use Trunnel and benefit from
368 autogenerated functions for parsing and generating SOCKS wire
369 format. New implementation is cleaner, more maintainable and
370 should be less prone to heartbleed-style vulnerabilities.
371 Implements a significant fraction of ticket 3569.
372 - Split sampled_guards_update_from_consensus() and
373 select_entry_guard_for_circuit() into subfunctions. In
374 entry_guards_update_primary() unite three smartlist enumerations
375 into one and move smartlist comparison code out of the function.
377 - Tor now assumes that you have standards-conformant stdint.h and
378 inttypes.h headers when compiling. Closes ticket 26626.
379 - Unify our bloom filter logic. Previously we had two copies of this
380 code: one for routerlist filtering, and one for address set
381 calculations. Closes ticket 26510.
382 - Use the simpler strcmpstart() helper in
383 rend_parse_v2_service_descriptor instead of strncmp(). Closes
385 - Utility functions that can perform a DNS lookup are now wholly
386 separated from those that can't, in separate headers and C
387 modules. Closes ticket 26526.
390 - Copy paragraph and URL to Tor's code of conduct document from
391 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
392 - Remove old instructions from INSTALL document. Closes ticket 26588.
393 - Warn users that they should not include MyFamily line(s) in their
394 torrc when running Tor bridge. Closes ticket 26908.
397 - Tor no longer supports building with the dmalloc library. For
398 debugging memory issues, we suggest using gperftools or msan
399 instead. Closes ticket 26426.
400 - Tor no longer attempts to run on Windows environments without the
401 GetAdaptersAddresses() function. This function has existed since
402 Windows XP, which is itself already older than we support.
403 - Remove Tor2web functionality. The Tor2webMode and
404 Tor2webRendezvousPoints options are now obsolete. (This feature
405 was never shipped in vanilla Tor and it was only possible to use
406 this feature by building the support at compile time.) Closes
410 Changes in version 0.2.9.17 - 2018-09-10
411 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
413 o Minor features (compatibility, backport from 0.3.4.8):
414 - Tell OpenSSL to maintain backward compatibility with previous
415 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
416 ciphers are disabled by default. Closes ticket 27344.
418 o Minor features (continuous integration, backport from 0.3.4.7-rc):
419 - Enable macOS builds in our Travis CI configuration. Closes
421 - Install libcap-dev and libseccomp2-dev so these optional
422 dependencies get tested on Travis CI. Closes ticket 26560.
423 - Run asciidoc during Travis CI. Implements ticket 27087.
424 - Use ccache in our Travis CI configuration. Closes ticket 26952.
426 o Minor features (geoip):
427 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
428 Country database. Closes ticket 27089.
430 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
431 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
432 tell the compiler not to include the system malloc implementation.
433 Fixes bug 20424; bugfix on 0.2.0.20-rc.
435 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
436 - Silence a spurious compiler warning on the GetAdaptersAddresses
437 function pointer cast. This issue is already fixed by 26481 in
438 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
439 bugfix on 0.2.3.11-alpha.
440 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
441 supported, and always fails. Some compilers warn about the
442 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
445 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
446 - Don't link or search for pthreads when building for Windows, even
447 if we are using build environment (like mingw) that provides a
448 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
450 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
451 - Skip a pair of unreliable key generation tests on Windows, until
452 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
453 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
455 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
456 - Pass the module flags to distcheck configure, and log the flags
457 before running configure. (Backported to 0.2.9 and later as a
458 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
460 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
461 - When a Travis build fails, and showing a log fails, keep trying to
462 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
463 - When we use echo in Travis, don't pass a --flag as the first
464 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
466 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
467 - When voting for recommended versions, make sure that all of the
468 versions are well-formed and parsable. Fixes bug 26485; bugfix
471 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
472 - Fix a bug in out sandboxing rules for the openat() syscall.
473 Previously, no openat() call would be permitted, which would break
474 filesystem operations on recent glibc versions. Fixes bug 25440;
475 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
477 o Minor bugfixes (onion services, backport from 0.3.4.8):
478 - Silence a spurious compiler warning in
479 rend_client_send_introduction(). Fixes bug 27463; bugfix
482 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
483 - Log a protocol warning when single onion services or Tor2web clients
484 fail to authenticate direct connections to relays.
485 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
487 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
488 - Disable core dumps in test_bt.sh, to avoid failures in "make
489 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
491 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
492 - Before running make test-network-all, delete old logs and test
493 result files, to avoid spurious failures. Fixes bug 27295; bugfix
496 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
497 - Our "tortls/cert_matches_key" unit test no longer relies on
498 OpenSSL internals. Previously, it relied on unsupported OpenSSL
499 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
500 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
502 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
503 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
504 27185; bugfix on 0.2.2.2-alpha.
507 Changes in version 0.3.2.12 - 2018-09-10
508 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
510 o Minor features (compatibility, backport from 0.3.4.8):
511 - Tell OpenSSL to maintain backward compatibility with previous
512 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
513 ciphers are disabled by default. Closes ticket 27344.
515 o Minor features (continuous integration, backport from 0.3.4.7-rc):
516 - Enable macOS builds in our Travis CI configuration. Closes
518 - Install libcap-dev and libseccomp2-dev so these optional
519 dependencies get tested on Travis CI. Closes ticket 26560.
520 - Run asciidoc during Travis CI. Implements ticket 27087.
521 - Use ccache in our Travis CI configuration. Closes ticket 26952.
523 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
524 - Use cargo cache in our Travis CI configuration. Closes
527 o Minor features (controller, backport from 0.3.4.6-rc):
528 - The control port now exposes the list of HTTPTunnelPorts and
529 ExtOrPorts via GETINFO net/listeners/httptunnel and
530 net/listeners/extor respectively. Closes ticket 26647.
532 o Minor features (directory authorities, backport from 0.3.4.7-rc):
533 - Authorities no longer vote to make the subprotocol version
534 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
535 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
537 o Minor features (geoip):
538 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
539 Country database. Closes ticket 27089.
541 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
542 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
543 tell the compiler not to include the system malloc implementation.
544 Fixes bug 20424; bugfix on 0.2.0.20-rc.
545 - Don't try to use a pragma to temporarily disable the
546 -Wunused-const-variable warning if the compiler doesn't support
547 it. Fixes bug 26785; bugfix on 0.3.2.11.
549 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
550 - Silence a spurious compiler warning on the GetAdaptersAddresses
551 function pointer cast. This issue is already fixed by 26481 in
552 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
553 bugfix on 0.2.3.11-alpha.
554 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
555 supported, and always fails. Some compilers warn about the
556 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
559 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
560 - Don't link or search for pthreads when building for Windows, even
561 if we are using build environment (like mingw) that provides a
562 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
564 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
565 - Skip a pair of unreliable key generation tests on Windows, until
566 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
567 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
569 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
570 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
571 - Pass the module flags to distcheck configure, and log the flags
572 before running configure. (Backported to 0.2.9 and later as a
573 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
575 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
576 - When a Travis build fails, and showing a log fails, keep trying to
577 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
578 - When we use echo in Travis, don't pass a --flag as the first
579 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
581 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
582 - When voting for recommended versions, make sure that all of the
583 versions are well-formed and parsable. Fixes bug 26485; bugfix
586 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
587 - Fix a bug in out sandboxing rules for the openat() syscall.
588 Previously, no openat() call would be permitted, which would break
589 filesystem operations on recent glibc versions. Fixes bug 25440;
590 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
592 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
593 - Improve the log message when connection initiators fail to
594 authenticate direct connections to relays. Fixes bug 26927; bugfix
597 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
598 - Fix bug that causes services to not ever rotate their descriptors
599 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
602 o Minor bugfixes (onion services, backport from 0.3.4.8):
603 - Silence a spurious compiler warning in
604 rend_client_send_introduction(). Fixes bug 27463; bugfix
607 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
608 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
610 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
611 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
612 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
613 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
615 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
616 - Log a protocol warning when single onion services or Tor2web clients
617 fail to authenticate direct connections to relays.
618 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
620 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
621 - Disable core dumps in test_bt.sh, to avoid failures in "make
622 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
624 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
625 - When running make test-network-all, use the mixed+hs-v2 network.
626 (A previous fix to chutney removed v3 onion services from the
627 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
628 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
629 - Before running make test-network-all, delete old logs and test
630 result files, to avoid spurious failures. Fixes bug 27295; bugfix
633 o Minor bugfixes (testing, openssl compatibility):
634 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
635 internals. Previously, it relied on unsupported OpenSSL behavior in
636 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
637 bugfix on 0.2.5.1-alpha.
639 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
640 - Our "tortls/cert_matches_key" unit test no longer relies on
641 OpenSSL internals. Previously, it relied on unsupported OpenSSL
642 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
643 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
645 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
646 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
647 27185; bugfix on 0.2.2.2-alpha.
650 Changes in version 0.3.3.10 - 2018-09-10
651 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
653 o Minor features (bug workaround, backport from 0.3.4.7-rc):
654 - Compile correctly on systems that provide the C11 stdatomic.h
655 header, but where C11 atomic functions don't actually compile.
656 Closes ticket 26779; workaround for Debian issue 903709.
658 o Minor features (compatibility, backport from 0.3.4.8):
659 - Tell OpenSSL to maintain backward compatibility with previous
660 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
661 ciphers are disabled by default. Closes ticket 27344.
663 o Minor features (continuous integration, backport from 0.3.4.7-rc):
664 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
665 - Enable macOS builds in our Travis CI configuration. Closes
667 - Install libcap-dev and libseccomp2-dev so these optional
668 dependencies get tested on Travis CI. Closes ticket 26560.
669 - Run asciidoc during Travis CI. Implements ticket 27087.
670 - Use ccache in our Travis CI configuration. Closes ticket 26952.
672 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
673 - Use cargo cache in our Travis CI configuration. Closes
676 o Minor features (controller, backport from 0.3.4.6-rc):
677 - The control port now exposes the list of HTTPTunnelPorts and
678 ExtOrPorts via GETINFO net/listeners/httptunnel and
679 net/listeners/extor respectively. Closes ticket 26647.
681 o Minor features (directory authorities, backport from 0.3.4.7-rc):
682 - Authorities no longer vote to make the subprotocol version
683 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
684 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
686 o Minor features (geoip):
687 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
688 Country database. Closes ticket 27089.
690 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
691 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
692 tell the compiler not to include the system malloc implementation.
693 Fixes bug 20424; bugfix on 0.2.0.20-rc.
694 - Don't try to use a pragma to temporarily disable the
695 -Wunused-const-variable warning if the compiler doesn't support
696 it. Fixes bug 26785; bugfix on 0.3.2.11.
698 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
699 - Silence a spurious compiler warning on the GetAdaptersAddresses
700 function pointer cast. This issue is already fixed by 26481 in
701 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
702 bugfix on 0.2.3.11-alpha.
703 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
704 supported, and always fails. Some compilers warn about the
705 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
708 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
709 - Don't link or search for pthreads when building for Windows, even
710 if we are using build environment (like mingw) that provides a
711 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
713 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
714 - Skip a pair of unreliable key generation tests on Windows, until
715 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
716 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
718 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
719 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
720 - Pass the module flags to distcheck configure, and log the flags
721 before running configure. (Backported to 0.2.9 and later as a
722 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
724 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
725 - When a Travis build fails, and showing a log fails, keep trying to
726 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
727 - When we use echo in Travis, don't pass a --flag as the first
728 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
730 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
731 - When voting for recommended versions, make sure that all of the
732 versions are well-formed and parsable. Fixes bug 26485; bugfix
735 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
736 - Always call tor_free_all() when leaving tor_run_main(). When we
737 did not, restarting tor in-process would cause an assertion
738 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
740 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
741 - Fix a bug in our sandboxing rules for the openat() syscall.
742 Previously, no openat() call would be permitted, which would break
743 filesystem operations on recent glibc versions. Fixes bug 25440;
744 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
746 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
747 - Improve the log message when connection initiators fail to
748 authenticate direct connections to relays. Fixes bug 26927; bugfix
751 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
752 - Fix bug that causes services to not ever rotate their descriptors
753 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
756 o Minor bugfixes (onion services, backport from 0.3.4.8):
757 - Silence a spurious compiler warning in
758 rend_client_send_introduction(). Fixes bug 27463; bugfix
761 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
762 - Work around two different bugs in the OS X 10.10 and later SDKs
763 that would prevent us from successfully targeting earlier versions
764 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
766 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
767 - Fix compilation of the unit tests on GNU/Hurd, which does not
768 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
771 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
772 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
774 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
775 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
776 - Protover parsing was accepting the presence of whitespace in
777 version strings, which the C implementation would choke on, e.g.
778 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
779 - Protover parsing was ignoring a 2nd hyphen and everything after
780 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
782 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
783 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
784 - cd to ${abs_top_builddir}/src/rust before running cargo in
785 src/test/test_rust.sh. This makes the working directory consistent
786 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
788 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
789 - Log a protocol warning when single onion services or Tor2web clients
790 fail to authenticate direct connections to relays.
791 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
793 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
794 - Disable core dumps in test_bt.sh, to avoid failures in "make
795 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
797 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
798 - When running make test-network-all, use the mixed+hs-v2 network.
799 (A previous fix to chutney removed v3 onion services from the
800 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
801 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
802 - Before running make test-network-all, delete old logs and test
803 result files, to avoid spurious failures. Fixes bug 27295; bugfix
806 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
807 - Our "tortls/cert_matches_key" unit test no longer relies on
808 OpenSSL internals. Previously, it relied on unsupported OpenSSL
809 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
810 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
812 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
813 - Stop sending ed25519 link specifiers in v3 onion service introduce
814 cells and descriptors, when the rendezvous or introduction point
815 doesn't support ed25519 link authentication. Fixes bug 26627;
816 bugfix on 0.3.2.4-alpha.
818 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
819 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
820 27185; bugfix on 0.2.2.2-alpha.
823 Changes in version 0.3.4.8 - 2018-09-10
824 Tor 0.3.4.8 is the first stable release in its series; it includes
825 compilation and portability fixes.
827 The Tor 0.3.4 series includes improvements for running Tor in
828 low-power and embedded environments, which should help performance in
829 general. We've begun work on better modularity, and included preliminary
830 changes on the directory authority side to accommodate a new bandwidth
831 measurement system. We've also integrated more continuous-integration
832 systems into our development process, and made corresponding changes to
833 Tor's testing infrastructure. Finally, we've continued to refine
834 our anti-denial-of-service code.
836 Below are the changes since 0.3.4.7-rc. For a complete list of changes
837 since 0.3.3.9, see the ReleaseNotes file.
839 o Minor features (compatibility):
840 - Tell OpenSSL to maintain backward compatibility with previous
841 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
842 ciphers are disabled by default. Closes ticket 27344.
844 o Minor features (continuous integration):
845 - Log the compiler path and version during Appveyor builds.
846 Implements ticket 27449.
847 - Show config.log and test-suite.log after failed Appveyor builds.
848 Also upload the zipped full logs as a build artifact. Implements
851 o Minor bugfixes (compilation):
852 - Silence a spurious compiler warning on the GetAdaptersAddresses
853 function pointer cast. This issue is already fixed by 26481 in
854 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
855 bugfix on 0.2.3.11-alpha.
856 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
857 supported, and always fails. Some compilers warn about the
858 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
861 o Minor bugfixes (continuous integration):
862 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
863 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
864 Executables compiled for 64-bit Windows with this version of gcc
865 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
866 27460; bugfix on 0.3.4.1-alpha.
867 - When a Travis build fails, and showing a log fails, keep trying to
868 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
869 - When we use echo in Travis, don't pass a --flag as the first
870 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
872 o Minor bugfixes (onion services):
873 - Silence a spurious compiler warning in
874 rend_client_send_introduction(). Fixes bug 27463; bugfix
877 o Minor bugfixes (testing, chutney):
878 - When running make test-network-all, use the mixed+hs-v2 network.
879 (A previous fix to chutney removed v3 onion services from the
880 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
881 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
882 - Before running make test-network-all, delete old logs and test
883 result files, to avoid spurious failures. Fixes bug 27295; bugfix
886 Changes in version 0.3.4.7-rc - 2018-08-24
887 Tor 0.3.4.7-rc fixes several small compilation, portability, and
888 correctness issues in previous versions of Tor. This version is a
889 release candidate: if no serious bugs are found, we expect that the
890 stable 0.3.4 release will be (almost) the same as this release.
892 o Minor features (bug workaround):
893 - Compile correctly on systems that provide the C11 stdatomic.h
894 header, but where C11 atomic functions don't actually compile.
895 Closes ticket 26779; workaround for Debian issue 903709.
897 o Minor features (continuous integration):
898 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
899 - Enable macOS builds in our Travis CI configuration. Closes
901 - Install libcap-dev and libseccomp2-dev so these optional
902 dependencies get tested on Travis CI. Closes ticket 26560.
903 - Only post Appveyor IRC notifications when the build fails.
904 Implements ticket 27275.
905 - Run asciidoc during Travis CI. Implements ticket 27087.
906 - Use ccache in our Travis CI configuration. Closes ticket 26952.
908 o Minor features (continuous integration, rust):
909 - Use cargo cache in our Travis CI configuration. Closes
912 o Minor features (directory authorities):
913 - Authorities no longer vote to make the subprotocol version
914 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
915 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
917 o Minor features (geoip):
918 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
919 Country database. Closes ticket 27089.
921 o Minor bugfixes (compilation, windows):
922 - Don't link or search for pthreads when building for Windows, even
923 if we are using build environment (like mingw) that provides a
924 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
926 o Minor bugfixes (continuous integration):
927 - Improve Appveyor CI IRC logging. Generate correct branches and
928 URLs for pull requests and tags. Use unambiguous short commits.
929 Fixes bug 26979; bugfix on master.
930 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
931 - Pass the module flags to distcheck configure, and log the flags
932 before running configure. (Backported to 0.2.9 and later as a
933 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
935 o Minor bugfixes (in-process restart):
936 - Always call tor_free_all() when leaving tor_run_main(). When we
937 did not, restarting tor in-process would cause an assertion
938 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
940 o Minor bugfixes (linux seccomp2 sandbox):
941 - Fix a bug in out sandboxing rules for the openat() syscall.
942 Previously, no openat() call would be permitted, which would break
943 filesystem operations on recent glibc versions. Fixes bug 25440;
944 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
946 o Minor bugfixes (onion services):
947 - Fix bug that causes services to not ever rotate their descriptors
948 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
951 o Minor bugfixes (portability):
952 - Fix compilation of the unit tests on GNU/Hurd, which does not
953 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
956 o Minor bugfixes (rust):
957 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
959 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
960 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
961 - Protover parsing was accepting the presence of whitespace in
962 version strings, which the C implementation would choke on, e.g.
963 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
964 - Protover parsing was ignoring a 2nd hyphen and everything after
965 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
967 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
968 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
969 - cd to ${abs_top_builddir}/src/rust before running cargo in
970 src/test/test_rust.sh. This makes the working directory consistent
971 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
973 o Minor bugfixes (testing, bootstrap):
974 - When calculating bootstrap progress, check exit policies and the
975 exit flag. Previously, Tor would only check the exit flag, which
976 caused race conditions in small and fast networks like chutney.
977 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
979 o Minor bugfixes (testing, openssl compatibility):
980 - Our "tortls/cert_matches_key" unit test no longer relies on
981 OpenSSL internals. Previously, it relied on unsupported OpenSSL
982 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
983 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
985 o Minor bugfixes (Windows, compilation):
986 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
987 27185; bugfix on 0.2.2.2-alpha.
990 Changes in version 0.3.4.6-rc - 2018-08-06
991 Tor 0.3.4.6-rc fixes several small compilation, portability, and
992 correctness issues in previous versions of Tor. This version is a
993 release candidate: if no serious bugs are found, we expect that the
994 stable 0.3.4 release will be (almost) the same as this release.
996 o Major bugfixes (event scheduler):
997 - When we enable a periodic event, schedule it in the event loop
998 rather than running it immediately. Previously, we would re-run
999 periodic events immediately in the middle of (for example)
1000 changing our options, with unpredictable effects. Fixes bug 27003;
1001 bugfix on 0.3.4.1-alpha.
1003 o Minor features (compilation):
1004 - When building Tor, prefer to use Python 3 over Python 2, and more
1005 recent (contemplated) versions over older ones. Closes
1007 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
1008 tell the compiler not to include the system malloc implementation.
1009 Fixes bug 20424; bugfix on 0.2.0.20-rc.
1010 - Don't try to use a pragma to temporarily disable the
1011 -Wunused-const-variable warning if the compiler doesn't support
1012 it. Fixes bug 26785; bugfix on 0.3.2.11.
1014 o Minor bugfixes (continuous integration):
1015 - Skip a pair of unreliable key generation tests on Windows, until
1016 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
1017 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
1019 o Minor features (controller):
1020 - The control port now exposes the list of HTTPTunnelPorts and
1021 ExtOrPorts via GETINFO net/listeners/httptunnel and
1022 net/listeners/extor respectively. Closes ticket 26647.
1024 o Minor bugfixes (directory authority):
1025 - When voting for recommended versions, make sure that all of the
1026 versions are well-formed and parsable. Fixes bug 26485; bugfix
1029 o Minor features (geoip):
1030 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1031 Country database. Closes ticket 26674.
1033 o Minor features (Rust, portability):
1034 - Rust cross-compilation is now supported. Closes ticket 25895.
1036 o Minor bugfixes (compilation):
1037 - Update build system so that tor builds again with --disable-unittests
1038 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
1039 - Fix a compilation warning on some versions of GCC when building
1040 code that calls routerinfo_get_my_routerinfo() twice, assuming
1041 that the second call will succeed if the first one did. Fixes bug
1042 26269; bugfix on 0.2.8.2-alpha.
1044 o Minor bugfixes (controller):
1045 - Report the port correctly when a port is configured to bind to
1046 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
1047 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
1048 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
1049 on 0.3.3.1-alpha. Patch by "akwizgran".
1051 o Minor bugfixes (correctness, flow control):
1052 - Upon receiving a stream-level SENDME cell, verify that our window
1053 has not grown too large. Fixes bug 26214; bugfix on svn
1056 o Minor bugfixes (memory, correctness):
1057 - Fix a number of small memory leaks identified by coverity. Fixes
1058 bug 26467; bugfix on numerous Tor versions.
1060 o Minor bugfixes (logging):
1061 - Improve the log message when connection initiators fail to
1062 authenticate direct connections to relays. Fixes bug 26927; bugfix
1065 o Minor bugfixes (portability):
1066 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
1067 26994; bugfix on 0.3.4.1-alpha.
1068 - Work around two different bugs in the OS X 10.10 and later SDKs
1069 that would prevent us from successfully targeting earlier versions
1070 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
1072 o Minor bugfixes (single onion services, Tor2web):
1073 - Log a protocol warning when single onion services or Tor2web
1074 clients fail to authenticate direct connections to relays. Fixes
1075 bug 26924; bugfix on 0.2.9.1-alpha.
1077 o Minor bugfixes (testing):
1078 - Disable core dumps in test_bt.sh, to avoid failures in "make
1079 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
1081 o Minor bugfixes (testing, compatibility):
1082 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
1083 only to pass strings (rather than "bytes" objects) to the Python
1084 subprocess module. Python 3 on Windows seems to require this.
1085 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
1086 0.3.1.1-alpha (for hs_ntor_ref.py).
1088 o Minor bugfixes (v3 onion services):
1089 - Stop sending ed25519 link specifiers in v3 onion service introduce
1090 cells and descriptors, when the rendezvous or introduction point
1091 doesn't support ed25519 link authentication. Fixes bug 26627;
1092 bugfix on 0.3.2.4-alpha.
1095 Changes in version 0.3.4.5-rc - 2018-07-13
1096 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
1097 bridge relays should upgrade.
1099 o Directory authority changes:
1100 - The "Bifroest" bridge authority has been retired; the new bridge
1101 authority is "Serge", and it is operated by George from the
1102 TorBSD project. Closes ticket 26771.
1105 Changes in version 0.3.3.9 - 2018-07-13
1106 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
1107 bridge relays should upgrade.
1109 o Directory authority changes:
1110 - The "Bifroest" bridge authority has been retired; the new bridge
1111 authority is "Serge", and it is operated by George from the
1112 TorBSD project. Closes ticket 26771.
1115 Changes in version 0.3.2.11 - 2018-07-13
1116 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
1117 bridge relays should upgrade. We also take this opportunity to backport
1120 o Directory authority changes:
1121 - The "Bifroest" bridge authority has been retired; the new bridge
1122 authority is "Serge", and it is operated by George from the
1123 TorBSD project. Closes ticket 26771.
1125 o Directory authority changes (backport from 0.3.3.7):
1126 - Add an IPv6 address for the "dannenberg" directory authority.
1127 Closes ticket 26343.
1129 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
1130 - When directory authorities read a zero-byte bandwidth file, they
1131 would previously log a warning with the contents of an
1132 uninitialised buffer. They now log a warning about the empty file
1133 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
1135 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
1136 - Correctly detect when onion services get disabled after HUP. Fixes
1137 bug 25761; bugfix on 0.3.2.1.
1139 o Minor features (sandbox, backport from 0.3.3.4-alpha):
1140 - Explicitly permit the poll() system call when the Linux
1141 seccomp2-based sandbox is enabled: apparently, some versions of
1142 libc use poll() when calling getpwnam(). Closes ticket 25313.
1144 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
1145 - Update the Travis CI configuration to use the stable Rust channel,
1146 now that we have decided to require that. Closes ticket 25714.
1148 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
1149 - Our .travis.yml configuration now includes support for testing the
1150 results of "make distcheck". (It's not uncommon for "make check"
1151 to pass but "make distcheck" to fail.) Closes ticket 25814.
1152 - Our Travis CI configuration now integrates with the Coveralls
1153 coverage analysis tool. Closes ticket 25818.
1155 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
1156 - Add several checks to detect whether Tor relays are uploading
1157 their descriptors without specifying why they regenerated them.
1158 Diagnostic for ticket 25686.
1160 o Minor features (compilation, backport from 0.3.4.4-rc):
1161 - When building Tor, prefer to use Python 3 over Python 2, and more
1162 recent (contemplated) versions over older ones. Closes
1165 o Minor features (geoip):
1166 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1167 Country database. Closes ticket 26674.
1169 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
1170 - Upon receiving a malformed connected cell, stop processing the
1171 cell immediately. Previously we would mark the connection for
1172 close, but continue processing the cell as if the connection were
1173 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
1175 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
1176 - Allow the nanosleep() system call, which glibc uses to implement
1177 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
1179 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
1180 - When running the hs_ntor_ref.py test, make sure only to pass
1181 strings (rather than "bytes" objects) to the Python subprocess
1182 module. Python 3 on Windows seems to require this. Fixes bug
1183 26535; bugfix on 0.3.1.1-alpha.
1184 - When running the ntor_ref.py test, make sure only to pass strings
1185 (rather than "bytes" objects) to the Python subprocess module.
1186 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
1189 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
1190 - Work around a change in OpenSSL 1.1.1 where return values that
1191 would previously indicate "no password" now indicate an empty
1192 password. Without this workaround, Tor instances running with
1193 OpenSSL 1.1.1 would accept descriptors that other Tor instances
1194 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
1196 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
1197 - Document that the PerConnBW{Rate,Burst} options will fall back to
1198 their corresponding consensus parameters only if those parameters
1199 are set. Previously we had claimed that these values would always
1200 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
1202 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
1203 - Fix a compilation warning on some versions of GCC when building
1204 code that calls routerinfo_get_my_routerinfo() twice, assuming
1205 that the second call will succeed if the first one did. Fixes bug
1206 26269; bugfix on 0.2.8.2-alpha.
1208 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
1209 - Don't consider Tor running as a client if the ControlPort is open,
1210 but no actual client ports are open. Fixes bug 26062; bugfix
1213 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
1214 - Prevent a possible out-of-bounds smartlist read in
1215 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
1217 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
1218 - Fix a very unlikely (impossible, we believe) null pointer
1219 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
1220 Coverity; this is CID 1430932.
1222 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
1223 - Fix a memory leak when a v3 onion service is configured and gets a
1224 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
1225 - When parsing the descriptor signature, look for the token plus an
1226 extra white-space at the end. This is more correct but also will
1227 allow us to support new fields that might start with "signature".
1228 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
1230 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
1231 - Relays now correctly block attempts to re-extend to the previous
1232 relay by Ed25519 identity. Previously they would warn in this
1233 case, but not actually reject the attempt. Fixes bug 26158; bugfix
1236 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
1237 - Avoid a crash when running with DirPort set but ORPort turned off.
1238 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
1240 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
1241 - Silence unused-const-variable warnings in zstd.h with some GCC
1242 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
1244 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
1245 - Avoid intermittent test failures due to a test that had relied on
1246 onion service introduction point creation finishing within 5
1247 seconds of real clock time. Fixes bug 25450; bugfix
1250 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
1251 - Fix a C99 compliance issue in our configuration script that caused
1252 compilation issues when compiling Tor with certain versions of
1253 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
1255 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
1256 - Fix a number of small memory leaks identified by coverity. Fixes
1257 bug 26467; bugfix on numerous Tor versions.
1259 o Code simplification and refactoring (backport from 0.3.3.5-rc):
1260 - Move the list of default directory authorities to its own file.
1261 Closes ticket 24854. Patch by "beastr0".
1264 Changes in version 0.2.9.16 - 2018-07-13
1265 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
1266 bridge relays should upgrade. We also take this opportunity to backport
1269 o Directory authority changes:
1270 - The "Bifroest" bridge authority has been retired; the new bridge
1271 authority is "Serge", and it is operated by George from the
1272 TorBSD project. Closes ticket 26771.
1274 o Directory authority changes (backport from 0.3.3.7):
1275 - Add an IPv6 address for the "dannenberg" directory authority.
1276 Closes ticket 26343.
1278 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
1279 - When directory authorities read a zero-byte bandwidth file, they
1280 would previously log a warning with the contents of an
1281 uninitialised buffer. They now log a warning about the empty file
1282 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
1284 o Minor features (sandbox, backport from 0.3.3.4-alpha):
1285 - Explicitly permit the poll() system call when the Linux
1286 seccomp2-based sandbox is enabled: apparently, some versions of
1287 libc use poll() when calling getpwnam(). Closes ticket 25313.
1289 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
1290 - Our .travis.yml configuration now includes support for testing the
1291 results of "make distcheck". (It's not uncommon for "make check"
1292 to pass but "make distcheck" to fail.) Closes ticket 25814.
1293 - Our Travis CI configuration now integrates with the Coveralls
1294 coverage analysis tool. Closes ticket 25818.
1296 o Minor features (compilation, backport from 0.3.4.4-rc):
1297 - When building Tor, prefer to use Python 3 over Python 2, and more
1298 recent (contemplated) versions over older ones. Closes
1301 o Minor features (geoip):
1302 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1303 Country database. Closes ticket 26674.
1305 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
1306 - Upon receiving a malformed connected cell, stop processing the
1307 cell immediately. Previously we would mark the connection for
1308 close, but continue processing the cell as if the connection were
1309 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
1311 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
1312 - Allow the nanosleep() system call, which glibc uses to implement
1313 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
1315 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
1316 - When running the ntor_ref.py test, make sure only to pass strings
1317 (rather than "bytes" objects) to the Python subprocess module.
1318 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
1321 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
1322 - Work around a change in OpenSSL 1.1.1 where return values that
1323 would previously indicate "no password" now indicate an empty
1324 password. Without this workaround, Tor instances running with
1325 OpenSSL 1.1.1 would accept descriptors that other Tor instances
1326 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
1328 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
1329 - Fix a compilation warning on some versions of GCC when building
1330 code that calls routerinfo_get_my_routerinfo() twice, assuming
1331 that the second call will succeed if the first one did. Fixes bug
1332 26269; bugfix on 0.2.8.2-alpha.
1334 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
1335 - Don't consider Tor running as a client if the ControlPort is open,
1336 but no actual client ports are open. Fixes bug 26062; bugfix
1339 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
1340 - Prevent a possible out-of-bounds smartlist read in
1341 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
1343 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
1344 - Fix a very unlikely (impossible, we believe) null pointer
1345 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
1346 Coverity; this is CID 1430932.
1348 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
1349 - Fix a number of small memory leaks identified by coverity. Fixes
1350 bug 26467; bugfix on numerous Tor versions.
1352 o Code simplification and refactoring (backport from 0.3.3.5-rc):
1353 - Move the list of default directory authorities to its own file.
1354 Closes ticket 24854. Patch by "beastr0".
1357 Changes in version 0.3.4.4-rc - 2018-07-09
1358 Tor 0.3.4.4-rc fixes several small compilation, portability, and
1359 correctness issues in previous versions of Tor. This version is a
1360 release candidate: if no serious bugs are found, we expect that the
1361 stable 0.3.4 release will be (almost) the same as this release.
1363 o Minor features (compilation):
1364 - When building Tor, prefer to use Python 3 over Python 2, and more
1365 recent (contemplated) versions over older ones. Closes
1368 o Minor features (geoip):
1369 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1370 Country database. Closes ticket 26674.
1372 o Minor features (Rust, portability):
1373 - Rust cross-compilation is now supported. Closes ticket 25895.
1375 o Minor bugfixes (compilation):
1376 - Fix a compilation warning on some versions of GCC when building
1377 code that calls routerinfo_get_my_routerinfo() twice, assuming
1378 that the second call will succeed if the first one did. Fixes bug
1379 26269; bugfix on 0.2.8.2-alpha.
1381 o Minor bugfixes (control port):
1382 - Report the port correctly when a port is configured to bind to
1383 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
1384 - Handle the HSADDRESS= argument to the HSPOST command properly.
1385 (Previously, this argument was misparsed and thus ignored.) Fixes
1386 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
1388 o Minor bugfixes (correctness, flow control):
1389 - Upon receiving a stream-level SENDME cell, verify that our window
1390 has not grown too large. Fixes bug 26214; bugfix on svn
1393 o Minor bugfixes (memory, correctness):
1394 - Fix a number of small memory leaks identified by coverity. Fixes
1395 bug 26467; bugfix on numerous Tor versions.
1397 o Minor bugfixes (testing, compatibility):
1398 - When running the hs_ntor_ref.py test, make sure only to pass
1399 strings (rather than "bytes" objects) to the Python subprocess
1400 module. Python 3 on Windows seems to require this. Fixes bug
1401 26535; bugfix on 0.3.1.1-alpha.
1402 - When running the ntor_ref.py test, make sure only to pass strings
1403 (rather than "bytes" objects) to the Python subprocess module.
1404 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
1408 Changes in version 0.3.3.8 - 2018-07-09
1409 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
1410 fixes for a memory leak affecting directory authorities.
1412 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
1413 - Stop leaking memory on directory authorities when planning to
1414 vote. This bug was crashing authorities by exhausting their
1415 memory. Fixes bug 26435; bugfix on 0.3.3.6.
1417 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
1418 - Make sure that failing tests in Rust will actually cause the build
1419 to fail: previously, they were ignored. Fixes bug 26258; bugfix
1422 o Minor features (compilation, backport from 0.3.4.4-rc):
1423 - When building Tor, prefer to use Python 3 over Python 2, and more
1424 recent (contemplated) versions over older ones. Closes
1427 o Minor features (geoip):
1428 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
1429 Country database. Closes ticket 26674.
1431 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
1432 - Add several checks to detect whether Tor relays are uploading
1433 their descriptors without specifying why they regenerated them.
1434 Diagnostic for ticket 25686.
1436 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
1437 - Don't count path selection failures as circuit build failures.
1438 This change should eliminate cases where Tor blames its guard or
1439 the network for situations like insufficient microdescriptors
1440 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
1443 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
1444 - Fix a compilation warning on some versions of GCC when building
1445 code that calls routerinfo_get_my_routerinfo() twice, assuming
1446 that the second call will succeed if the first one did. Fixes bug
1447 26269; bugfix on 0.2.8.2-alpha.
1449 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
1450 - Handle the HSADDRESS= argument to the HSPOST command properly.
1451 (Previously, this argument was misparsed and thus ignored.) Fixes
1452 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
1454 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
1455 - Fix a number of small memory leaks identified by coverity. Fixes
1456 bug 26467; bugfix on numerous Tor versions.
1458 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
1459 - Relays now correctly block attempts to re-extend to the previous
1460 relay by Ed25519 identity. Previously they would warn in this
1461 case, but not actually reject the attempt. Fixes bug 26158; bugfix
1464 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
1465 - When shutting down, Tor now clears all the flags in the control.c
1466 module. This should prevent a bug where authentication cookies are
1467 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
1469 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
1470 - When running the hs_ntor_ref.py test, make sure only to pass
1471 strings (rather than "bytes" objects) to the Python subprocess
1472 module. Python 3 on Windows seems to require this. Fixes bug
1473 26535; bugfix on 0.3.1.1-alpha.
1474 - When running the ntor_ref.py test, make sure only to pass strings
1475 (rather than "bytes" objects) to the Python subprocess module.
1476 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
1480 Changes in version 0.3.4.3-alpha - 2018-06-26
1481 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
1482 one that was causing stability issues on directory authorities.
1484 o Major bugfixes (directory authority):
1485 - Stop leaking memory on directory authorities when planning to
1486 vote. This bug was crashing authorities by exhausting their
1487 memory. Fixes bug 26435; bugfix on 0.3.3.6.
1489 o Major bugfixes (rust, testing):
1490 - Make sure that failing tests in Rust will actually cause the build
1491 to fail: previously, they were ignored. Fixes bug 26258; bugfix
1494 o Minor feature (directory authorities):
1495 - Stop warning about incomplete bw lines before the first complete
1496 bw line has been found, so that additional header lines can be
1497 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
1499 o Minor features (relay, diagnostic):
1500 - Add several checks to detect whether Tor relays are uploading
1501 their descriptors without specifying why they regenerated them.
1502 Diagnostic for ticket 25686.
1504 o Minor features (unit tests):
1505 - Test complete bandwidth measurements files, and test that
1506 incomplete bandwidth lines only give warnings when the end of the
1507 header has not been detected. Fixes bug 25947; bugfix
1510 o Minor bugfixes (compilation):
1511 - Refrain from compiling unit testing related object files when
1512 --disable-unittests is set to configure script. Fixes bug 24891;
1513 bugfix on 0.2.5.1-alpha.
1514 - When linking the libtor_testing.a library, only include the
1515 dirauth object files once. Previously, they were getting added
1516 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
1517 - The --enable-fatal-warnings flag now affects Rust code as well.
1518 Closes ticket 26245.
1520 o Minor bugfixes (onion services):
1521 - Recompute some consensus information after detecting a clock jump,
1522 or after transitioning from a non-live consensus to a live
1523 consensus. We do this to avoid having an outdated state, and
1524 miscalculating the index for next-generation onion services. Fixes
1525 bug 24977; bugfix on 0.3.2.1-alpha.
1527 o Minor bugfixes (relay):
1528 - Relays now correctly block attempts to re-extend to the previous
1529 relay by Ed25519 identity. Previously they would warn in this
1530 case, but not actually reject the attempt. Fixes bug 26158; bugfix
1533 o Minor bugfixes (testing):
1534 - Fix compilation of the doctests in the Rust crypto crate. Fixes
1535 bug 26415; bugfix on 0.3.4.1-alpha.
1536 - Instead of trying to read the geoip configuration files from
1537 within the unit tests, instead create our own ersatz files with
1538 just enough geoip data in the format we expect. Trying to read
1539 from the source directory created problems on Windows with mingw,
1540 where the build system's paths are not the same as the platform's
1541 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
1542 - Refrain from trying to get an item from an empty smartlist in
1543 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
1544 to catch improper smartlist usage. Furthermore, enable
1545 DEBUG_SMARTLIST globally when build is configured with fragile
1546 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
1549 Changes in version 0.3.3.7 - 2018-06-12
1550 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
1551 fixes for bugs affecting compatibility and stability.
1553 o Directory authority changes:
1554 - Add an IPv6 address for the "dannenberg" directory authority.
1555 Closes ticket 26343.
1557 o Minor features (geoip):
1558 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
1559 Country database. Closes ticket 26351.
1561 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
1562 - Work around a change in OpenSSL 1.1.1 where return values that
1563 would previously indicate "no password" now indicate an empty
1564 password. Without this workaround, Tor instances running with
1565 OpenSSL 1.1.1 would accept descriptors that other Tor instances
1566 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
1568 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
1569 - Silence unused-const-variable warnings in zstd.h with some GCC
1570 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
1572 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
1573 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
1574 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
1575 miscounting the total number of circuits for these field values.)
1576 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
1578 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
1579 - Prevent a possible out-of-bounds smartlist read in
1580 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
1582 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
1583 - Only select relays when they have the descriptors we prefer to use
1584 for them. This change fixes a bug where we could select a relay
1585 because it had _some_ descriptor, but reject it later with a
1586 nonfatal assertion error because it didn't have the exact one we
1587 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
1590 Changes in version 0.3.4.2-alpha - 2018-06-12
1591 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
1592 release, and forward-ports an authority-only security fix from 0.3.3.6.
1594 o Directory authority changes:
1595 - Add an IPv6 address for the "dannenberg" directory authority.
1596 Closes ticket 26343.
1598 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
1599 - Fix a bug that could have allowed an attacker to force a directory
1600 authority to use up all its RAM by passing it a maliciously
1601 crafted protocol versions string. Fixes bug 25517; bugfix on
1602 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
1604 o Minor features (continuous integration):
1605 - Add the necessary configuration files for continuous integration
1606 testing on Windows, via the Appveyor platform. Closes ticket
1607 25549. Patches from Marcin Cieślak and Isis Lovecruft.
1609 o Minor features (geoip):
1610 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
1611 Country database. Closes ticket 26351.
1613 o Minor bugfixes (compatibility, openssl):
1614 - Work around a change in OpenSSL 1.1.1 where return values that
1615 would previously indicate "no password" now indicate an empty
1616 password. Without this workaround, Tor instances running with
1617 OpenSSL 1.1.1 would accept descriptors that other Tor instances
1618 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
1620 o Minor bugfixes (compilation):
1621 - Silence unused-const-variable warnings in zstd.h with some GCC
1622 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
1623 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
1624 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
1625 - Avoid a compiler warning when casting the return value of
1626 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
1627 26283; bugfix on 0.2.4.10-alpha.
1629 o Minor bugfixes (control port):
1630 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
1631 CIRC_BW events. Previously, such cells were counted entirely in
1632 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
1635 o Minor bugfixes (controller):
1636 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
1637 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
1638 miscounting the total number of circuits for these field values.)
1639 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
1641 o Minor bugfixes (hardening):
1642 - Prevent a possible out-of-bounds smartlist read in
1643 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
1645 o Minor bugfixes (onion services):
1646 - Fix a bug that blocked the creation of ephemeral v3 onion
1647 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
1649 o Minor bugfixes (test coverage tools):
1650 - Update our "cov-diff" script to handle output from the latest
1651 version of gcov, and to remove extraneous timestamp information
1652 from its output. Fixes bugs 26101 and 26102; bugfix
1656 Changes in version 0.3.3.6 - 2018-05-22
1657 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
1658 backports several important fixes from the 0.3.4.1-alpha.
1660 The Tor 0.3.3 series includes controller support and other
1661 improvements for v3 onion services, official support for embedding Tor
1662 within other applications, and our first non-trivial module written in
1663 the Rust programming language. (Rust is still not enabled by default
1664 when building Tor.) And as usual, there are numerous other smaller
1665 bugfixes, features, and improvements.
1667 Below are the changes since 0.3.3.5-rc. For a list of all changes
1668 since 0.3.2.10, see the ReleaseNotes file.
1670 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
1671 - When directory authorities read a zero-byte bandwidth file, they
1672 would previously log a warning with the contents of an
1673 uninitialised buffer. They now log a warning about the empty file
1674 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
1676 o Major bugfixes (security, directory authority, denial-of-service):
1677 - Fix a bug that could have allowed an attacker to force a directory
1678 authority to use up all its RAM by passing it a maliciously
1679 crafted protocol versions string. Fixes bug 25517; bugfix on
1680 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
1682 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
1683 - Avoid a rare assertion failure in the circuit build timeout code
1684 if we fail to allow any circuits to actually complete. Fixes bug
1685 25733; bugfix on 0.2.2.2-alpha.
1687 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
1688 - Avoid a crash when testing router reachability on a router that
1689 could have an ed25519 ID, but which does not. Fixes bug 25415;
1690 bugfix on 0.3.3.2-alpha.
1692 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
1693 - Correctly detect when onion services get disabled after HUP. Fixes
1694 bug 25761; bugfix on 0.3.2.1.
1696 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
1697 - Impose a limit on circuit cell queue size. The limit can be
1698 controlled by a consensus parameter. Fixes bug 25226; bugfix
1701 o Minor features (compatibility, backport from 0.3.4.1-alpha):
1702 - Avoid some compilation warnings with recent versions of LibreSSL.
1703 Closes ticket 26006.
1705 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
1706 - Our .travis.yml configuration now includes support for testing the
1707 results of "make distcheck". (It's not uncommon for "make check"
1708 to pass but "make distcheck" to fail.) Closes ticket 25814.
1709 - Our Travis CI configuration now integrates with the Coveralls
1710 coverage analysis tool. Closes ticket 25818.
1712 o Minor features (geoip):
1713 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
1714 database. Closes ticket 26104.
1716 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
1717 - Don't consider Tor running as a client if the ControlPort is open,
1718 but no actual client ports are open. Fixes bug 26062; bugfix
1721 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
1722 - Upon receiving a malformed connected cell, stop processing the
1723 cell immediately. Previously we would mark the connection for
1724 close, but continue processing the cell as if the connection were
1725 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
1727 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
1728 - Stop saying in the manual that clients cache ipv4 dns answers from
1729 exit relays. We haven't used them since 0.2.6.3-alpha, and in
1730 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
1731 we forgot to say so in the man page. Fixes bug 26052; bugfix
1734 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
1735 - Allow the nanosleep() system call, which glibc uses to implement
1736 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
1738 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
1739 - Fix a memory leak when a v3 onion service is configured and gets a
1740 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
1741 - When parsing the descriptor signature, look for the token plus an
1742 extra white-space at the end. This is more correct but also will
1743 allow us to support new fields that might start with "signature".
1744 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
1746 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
1747 - Avoid a crash when running with DirPort set but ORPort turned off.
1748 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
1750 o Documentation (backport from 0.3.4.1-alpha):
1751 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
1752 ticket 25857. Patch from "CTassisF".
1755 Changes in version 0.3.4.1-alpha - 2018-05-17
1756 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
1757 includes refactoring to begin reducing Tor's binary size and idle CPU
1758 usage on mobile, along with prep work for new bandwidth scanners,
1759 improvements to the experimental "vanguards" feature, and numerous
1760 other small features and bugfixes.
1762 o New system requirements:
1763 - Tor no longer tries to support old operating systems without
1764 mmap() or some local equivalent. Apparently, compilation on such
1765 systems has been broken for some time, without anybody noticing or
1766 complaining. Closes ticket 25398.
1768 o Major feature (directory authority, modularization):
1769 - The directory authority subsystem has been modularized. The code
1770 is now located in src/or/dirauth/, and is compiled in by default.
1771 To disable the module, the configure option
1772 --disable-module-dirauth has been added. This module may be
1773 disabled by default in some future release. Closes ticket 25610.
1775 o Major features (main loop, CPU usage):
1776 - When Tor is disabled (via DisableNetwork or via hibernation), it
1777 no longer needs to run any per-second events. This change should
1778 make it easier for mobile applications to disable Tor while the
1779 device is sleeping, or Tor is not running. Closes ticket 26063.
1780 - Tor no longer enables all of its periodic events by default.
1781 Previously, Tor would enable all possible main loop events,
1782 regardless of whether it needed them. Furthermore, many of these
1783 events are now disabled with Tor is hibernating or DisableNetwork
1784 is set. This is a big step towards reducing client CPU usage by
1785 reducing the amount of wake-ups the daemon does. Closes ticket
1787 - The bandwidth-limitation logic has been refactored so that
1788 bandwidth calculations are performed on-demand, rather than every
1789 TokenBucketRefillInterval milliseconds. This change should improve
1790 the granularity of our bandwidth calculations, and limit the
1791 number of times that the Tor process needs to wake up when it is
1792 idle. Closes ticket 25373.
1793 - Move responsibility for many operations from a once-per-second
1794 callback to a callback that is only scheduled as needed. Moving
1795 this functionality has allowed us to disable the callback when
1796 Tor's network is disabled. Once enough items are removed from our
1797 once-per-second callback, we can eliminate it entirely to conserve
1798 CPU when idle. The functionality removed includes: closing
1799 connections, circuits, and channels (ticket 25932); consensus
1800 voting (25937); flushing log callbacks (25951); honoring delayed
1801 SIGNEWNYM requests (25949); rescanning the consensus cache
1802 (25931); saving the state file to disk (25948); warning relay
1803 operators about unreachable ports (25952); and keeping track of
1804 Tor's uptime (26009).
1806 o Major bugfixes (directory authorities, security):
1807 - When directory authorities read a zero-byte bandwidth file, they
1808 would previously log a warning with the contents of an
1809 uninitialised buffer. They now log a warning about the empty file
1810 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
1812 o Major bugfixes (crash):
1813 - Avoid a rare assertion failure in the circuit build timeout code
1814 if we fail to allow any circuits to actually complete. Fixes bug
1815 25733; bugfix on 0.2.2.2-alpha.
1817 o Major bugfixes (directory authority):
1818 - Avoid a crash when testing router reachability on a router that
1819 could have an ed25519 ID, but which does not. Fixes bug 25415;
1820 bugfix on 0.3.3.2-alpha.
1822 o Major bugfixes (onion service):
1823 - Correctly detect when onion services get disabled after HUP. Fixes
1824 bug 25761; bugfix on 0.3.2.1.
1826 o Major bugfixes (protover, voting):
1827 - Revise Rust implementation of protover to use a more memory-
1828 efficient voting algorithm and corresponding data structures, thus
1829 avoiding a potential (but small impact) DoS attack where specially
1830 crafted protocol strings would expand to several potential
1831 megabytes in memory. In the process, several portions of code were
1832 revised to be methods on new, custom types, rather than functions
1833 taking interchangeable types, thus increasing type safety of the
1834 module. Custom error types and handling were added as well, in
1835 order to facilitate better error dismissal/handling in outside
1836 crates and avoid mistakenly passing an internal error string to C
1837 over the FFI boundary. Many tests were added, and some previous
1838 differences between the C and Rust implementations have been
1839 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
1841 o Major bugfixes (relay, denial of service):
1842 - Impose a limit on circuit cell queue size. The limit can be
1843 controlled by a consensus parameter. Fixes bug 25226; bugfix
1846 o Minor features (accounting):
1847 - When Tor becomes dormant, it now uses a scheduled event to wake up
1848 at the right time. Previously, we would use the per-second timer
1849 to check whether to wake up, but we no longer have any per-second
1850 timers enabled when the network is disabled. Closes ticket 26064.
1852 o Minor features (code quality):
1853 - Add optional spell-checking for the Tor codebase, using the
1854 "misspell" program. To use this feature, run "make check-typos".
1855 Closes ticket 25024.
1857 o Minor features (compatibility):
1858 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
1859 the no-deprecated option, and builds correctly with them. Closes
1860 tickets 19429, 19981, and 25353.
1861 - Avoid some compilation warnings with recent versions of LibreSSL.
1862 Closes ticket 26006.
1864 o Minor features (compression, zstd):
1865 - When running with zstd, Tor now considers using advanced functions
1866 that the zstd maintainers have labeled as potentially unstable. To
1867 prevent breakage, Tor will only use this functionality when the
1868 runtime version of the zstd library matches the version with which
1869 Tor was compiled. Closes ticket 25162.
1871 o Minor features (configuration):
1872 - The "DownloadSchedule" options have been renamed to end with
1873 "DownloadInitialDelay". The old names are still allowed, but will
1874 produce a warning. Comma-separated lists are still permitted for
1875 these options, but all values after the first are ignored (as they
1876 have been since 0.2.9). Closes ticket 23354.
1878 o Minor features (continuous integration):
1879 - Our .travis.yml configuration now includes support for testing the
1880 results of "make distcheck". (It's not uncommon for "make check"
1881 to pass but "make distcheck" to fail.) Closes ticket 25814.
1882 - Our Travis CI configuration now integrates with the Coveralls
1883 coverage analysis tool. Closes ticket 25818.
1885 o Minor features (control port):
1886 - Introduce GETINFO "current-time/{local,utc}" to return the local
1887 and UTC times respectively in ISO format. This helps a controller
1888 like Tor Browser detect a time-related error. Closes ticket 25511.
1889 Patch by Neel Chauhan.
1890 - Introduce new fields to the CIRC_BW event. There are two new
1891 fields in each of the read and written directions. The DELIVERED
1892 fields report the total valid data on the circuit, as measured by
1893 the payload sizes of verified and error-checked relay command
1894 cells. The OVERHEAD fields report the total unused bytes in each
1895 of these cells. Closes ticket 25903.
1897 o Minor features (directory authority):
1898 - Directory authorities now open their key-pinning files as O_SYNC,
1899 to limit their chances of accidentally writing partial lines.
1900 Closes ticket 23909.
1902 o Minor features (directory authority, forward compatibility):
1903 - Make the lines of the measured bandwidth file able to contain
1904 their entries in any order. Previously, the node_id entry needed
1905 to come first. Closes ticket 26004.
1907 o Minor features (entry guards):
1908 - Introduce a new torrc option NumPrimaryGuards for controlling the
1909 number of primary guards. Closes ticket 25843.
1911 o Minor features (geoip):
1912 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
1913 database. Closes ticket 26104.
1915 o Minor features (performance):
1916 - Avoid a needless call to malloc() when processing an incoming
1917 relay cell. Closes ticket 24914.
1918 - Make our timing-wheel code run a tiny bit faster on 32-bit
1919 platforms, by preferring 32-bit math to 64-bit. Closes
1921 - Avoid a needless malloc()/free() pair every time we handle an ntor
1922 handshake. Closes ticket 25150.
1924 o Minor features (testing):
1925 - Add a unit test for voting_schedule_get_start_of_next_interval().
1926 Closes ticket 26014, and helps make unit test coverage
1928 - A new unittests module specifically for testing the functions in
1929 the (new-ish) bridges.c module has been created with new
1930 unittests, raising the code coverage percentages. Closes 25425.
1931 - We now have improved testing for addressmap_get_virtual_address()
1932 function. This should improve our test coverage, and make our test
1933 coverage more deterministic. Closes ticket 25993.
1935 o Minor features (timekeeping, circuit scheduling):
1936 - When keeping track of how busy each circuit have been recently on
1937 a given connection, use coarse-grained monotonic timers rather
1938 than gettimeofday(). This change should marginally increase
1939 accuracy and performance. Implements part of ticket 25927.
1941 o Minor bugfixes (bandwidth management):
1942 - Consider ourselves "low on write bandwidth" if we have exhausted
1943 our write bandwidth some time in the last second. This was the
1944 documented behavior before, but the actual behavior was to change
1945 this value every TokenBucketRefillInterval. Fixes bug 25828;
1946 bugfix on 0.2.3.5-alpha.
1948 o Minor bugfixes (C correctness):
1949 - Add a missing lock acquisition in the shutdown code of the control
1950 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
1951 Coverity; this is CID 1433643.
1953 o Minor bugfixes (circuit path selection):
1954 - Don't count path selection failures as circuit build failures.
1955 This change should eliminate cases where Tor blames its guard or
1956 the network for situations like insufficient microdescriptors
1957 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
1960 o Minor bugfixes (client):
1961 - Don't consider Tor running as a client if the ControlPort is open,
1962 but no actual client ports are open. Fixes bug 26062; bugfix
1965 o Minor bugfixes (code style):
1966 - Fixed multiple includes of transports.h in src/or/connection.c
1967 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
1968 - Remove the unused variable n_possible from the function
1969 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
1971 o Minor bugfixes (control interface):
1972 - Respond with more human-readable error messages to GETINFO exit-
1973 policy/* requests. Also, let controller know if an error is
1974 transient (response code 551) or not (response code 552). Fixes
1975 bug 25852; bugfix on 0.2.8.1-alpha.
1977 o Minor bugfixes (controller):
1978 - Make CIRC_BW event reflect the total of all data sent on a
1979 circuit, including padding and dropped cells. Also fix a mis-
1980 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
1981 bugfix on 0.2.5.2-alpha.
1983 o Minor bugfixes (correctness, client):
1984 - Upon receiving a malformed connected cell, stop processing the cell
1985 immediately. Previously we would mark the connection for close, but
1986 continue processing the cell as if the connection were open. Fixes bug
1987 26072; bugfix on 0.2.4.7-alpha.
1989 o Minor bugfixes (directory client):
1990 - When unverified-consensus is verified, rename it to cached-
1991 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
1992 - Fixed launching a certificate fetch always during the scheduled
1993 periodic consensus fetch by fetching only in those cases when
1994 consensus are waiting for certs. Fixes bug 24740; bugfix
1997 o Minor bugfixes (documentation):
1998 - Stop saying in the manual that clients cache ipv4 dns answers from
1999 exit relays. We haven't used them since 0.2.6.3-alpha, and in
2000 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
2001 we forgot to say so in the man page. Fixes bug 26052; bugfix
2004 o Minor bugfixes (error reporting):
2005 - Improve tolerance for directory authorities with skewed clocks.
2006 Previously, an authority with a clock more than 60 seconds ahead
2007 could cause a client with a correct clock to warn that the
2008 client's clock was behind. Now the clocks of a majority of
2009 directory authorities have to be ahead of the client before this
2010 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
2012 o Minor bugfixes (Linux seccomp2 sandbox):
2013 - Allow the nanosleep() system call, which glibc uses to implement
2014 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
2016 o Minor bugfixes (onion service):
2017 - Fix a memory leak when a v3 onion service is configured and gets a
2018 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
2019 - When parsing the descriptor signature, look for the token plus an
2020 extra white-space at the end. This is more correct but also will
2021 allow us to support new fields that might start with "signature".
2022 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
2024 o Minor bugfixes (path selection):
2025 - Only select relays when they have the descriptors we prefer to use
2026 for them. This change fixes a bug where we could select a relay
2027 because it had _some_ descriptor, but reject it later with a
2028 nonfatal assertion error because it didn't have the exact one we
2029 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
2031 o Minor bugfixes (portability):
2032 - Do not align mmap length, as it is not required by POSIX, and the
2033 getpagesize function is deprecated. Fixes bug 25399; bugfix
2036 o Minor bugfixes (portability, FreeBSD):
2037 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
2038 does not stringify on FreeBSD, so we switch to tor_asprintf().
2039 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
2041 o Minor bugfixes (relay statistics):
2042 - When a relay is collecting internal statistics about how many
2043 create cell requests it has seen of each type, accurately count
2044 the requests from relays that temporarily fall out of the
2045 consensus. (To be extra conservative, we were already ignoring
2046 requests from clients in our counts, and we continue ignoring them
2047 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
2049 o Minor bugfixes (relay, crash):
2050 - Avoid a crash when running with DirPort set but ORPort turned off.
2051 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
2053 o Minor bugfixes (restart-in-process):
2054 - When shutting down, Tor now clears all the flags in the control.c
2055 module. This should prevent a bug where authentication cookies are
2056 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
2058 o Minor bugfixes (testing):
2059 - When testing workqueue event-cancellation, make sure that we
2060 actually cancel an event, and that cancel each event with equal
2061 probability. (It was previously possible, though extremely
2062 unlikely, for our event-canceling test not to cancel any events.)
2063 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
2064 - Repeat part of the test in test_client_pick_intro() a number of
2065 times, to give it consistent coverage. Fixes bug 25996; bugfix
2067 - Remove randomness from the hs_common/responsible_hsdirs test, so
2068 that it always takes the same path through the function it tests.
2069 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
2070 - Change the behavior of the "channel/outbound" test so that it
2071 never causes a 10-second rollover for the EWMA circuitmux code.
2072 Previously, this behavior would happen randomly, and result in
2073 fluctuating test coverage. Fixes bug 25994; bugfix
2075 - Use X509_new() to allocate certificates that will be freed later
2076 with X509_free(). Previously, some parts of the unit tests had
2077 used tor_malloc_zero(), which is incorrect, and which caused test
2078 failures on Windows when they were built with extra hardening.
2079 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
2081 - While running the circuit_timeout test, fix the PRNG to a
2082 deterministic AES stream, so that the test coverage from this test
2083 will itself be deterministic. Fixes bug 25995; bugfix
2086 o Minor bugfixes (vanguards):
2087 - Allow the last hop in a vanguard circuit to be the same as our
2088 first, to prevent the adversary from influencing guard node choice
2089 by choice of last hop. Also prevent the creation of A - B - A
2090 paths, or A - A paths, which are forbidden by relays. Fixes bug
2091 25870; bugfix on 0.3.3.1-alpha.
2093 o Code simplification and refactoring:
2094 - Remove duplicate code in parse_{c,s}method_line and bootstrap
2095 their functionalities into a single function. Fixes bug 6236;
2096 bugfix on 0.2.3.6-alpha.
2097 - We remove the PortForwsrding and PortForwardingHelper options,
2098 related functions, and the port_forwarding tests. These options
2099 were used by the now-deprecated Vidalia to help ordinary users
2100 become Tor relays or bridges. Closes ticket 25409. Patch by
2102 - In order to make the OR and dir checking function in router.c less
2103 confusing we renamed some functions and
2104 consider_testing_reachability() has been split into
2105 router_should_check_reachability() and
2106 router_do_reachability_checks(). Also we improved the documentation
2107 in some functions. Closes ticket 18918.
2108 - Initial work to isolate Libevent usage to a handful of modules in
2109 our codebase, to simplify our call structure, and so that we can
2110 more easily change event loops in the future if needed. Closes
2112 - Introduce a function to call getsockname() and return tor_addr_t,
2113 to save a little complexity throughout the codebase. Closes
2115 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
2116 as hsdir_index is always present. Also, we move hsdir_index_t into
2117 or.h. Closes ticket 23094. Patch by Neel Chauhan.
2118 - Merge functions used for describing nodes and suppress the
2119 functions that do not allocate memory for the output buffer
2120 string. NODE_DESC_BUF_LEN constant and format_node_description()
2121 function cannot be used externally from router.c module anymore.
2122 Closes ticket 25432. Patch by valentecaio.
2123 - Our main loop has been simplified so that all important operations
2124 happen inside events. Previously, some operations had to happen
2125 outside the event loop, to prevent infinite sequences of event
2126 activations. Closes ticket 25374.
2127 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
2128 it in register_intro_circ() and service_intro_point_new(). This
2129 prevents the digest from being re-calculated each time. Closes
2130 ticket 23107. Patch by Neel Chauhan.
2131 - Refactor token-bucket implementations to use a common backend.
2132 Closes ticket 25766.
2133 - Remove extern declaration of stats_n_seconds_working variable from
2134 main, protecting its accesses with get_uptime() and reset_uptime()
2135 functions. Closes ticket 25081, patch by “valentecaio”.
2136 - Remove our previous logic for "cached gettimeofday()" -- our
2137 coarse monotonic timers are fast enough for this purpose, and far
2138 less error-prone. Implements part of ticket 25927.
2139 - Remove the return value for fascist_firewall_choose_address_base(),
2140 and sister functions such as fascist_firewall_choose_address_node()
2141 and fascist_firewall_choose_address_rs(). Also, while we're here,
2142 initialize the ap argument as leaving it uninitialized can pose a
2143 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
2144 - Rename two fields of connection_t struct. timestamp_lastwritten is
2145 renamed to timestamp_last_write_allowed and timestamp_lastread is
2146 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
2148 - Since Tor requires C99, remove our old workaround code for libc
2149 implementations where free(NULL) doesn't work. Closes ticket 24484.
2150 - Use our standard rate-limiting code to deal with excessive
2151 libevent failures, rather than the hand-rolled logic we had
2152 before. Closes ticket 26016.
2153 - We remove the return value of node_get_prim_orport() and
2154 node_get_prim_dirport(), and introduce node_get_prim_orport() in
2155 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
2156 check for a null address. Closes ticket 23873. Patch by
2158 - We switch to should_record_bridge_info() in
2159 geoip_note_client_seen() and options_need_geoip_info() instead of
2160 accessing the configuration values directly. Fixes bug 25290;
2161 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
2163 o Deprecated features:
2164 - As we are not recommending 0.2.5 anymore, we require relays that
2165 once had an ed25519 key associated with their RSA key to always
2166 have that key, instead of allowing them to drop back to a version
2167 that didn't support ed25519. This means they need to use a new RSA
2168 key if the want to downgrade to an older version of tor without
2169 ed25519. Closes ticket 20522.
2172 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
2173 ticket 25857. Patch from "CTassisF".
2176 - Directory authorities will no longer support voting according to
2177 any consensus method before consensus method 25. This keeps
2178 authorities compatible with all authorities running 0.2.9.8 and
2179 later, and does not break any clients or relays. Implements ticket
2180 24378 and proposal 290.
2181 - The PortForwarding and PortForwardingHelper features have been
2182 removed. The reasoning is, given that implementations of NAT
2183 traversal protocols within common consumer grade routers are
2184 frequently buggy, and that the target audience for a NAT punching
2185 feature is a perhaps less-technically-inclined relay operator,
2186 when the helper fails to setup traversal the problems are usually
2187 deep, ugly, and very router specific, making them horrendously
2188 impossible for technical support to reliable assist with, and thus
2189 resulting in frustration all around. Unfortunately, relay
2190 operators who would like to run relays behind NATs will need to
2191 become more familiar with the port forwarding configurations on
2192 their local router. Closes 25409.
2193 - The TestingEnableTbEmptyEvent option has been removed. It was used
2194 in testing simulations to measure how often connection buckets
2195 were emptied, in order to improve our scheduling, but it has not
2196 been actively used in years. Closes ticket 25760.
2197 - The old "round-robin" circuit multiplexer (circuitmux)
2198 implementation has been removed, along with a fairly large set of
2199 code that existed to support it. It has not been the default
2200 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
2201 but it still required an unreasonable amount of memory and CPU.
2202 Closes ticket 25268.
2205 Changes in version 0.3.3.5-rc - 2018-04-15
2206 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
2207 including some that could affect reliability or correctness.
2209 This is the first release candidate in the 0.3.3 series. If we find no
2210 new bugs or regression here, then the first stable 0.3.3 release will
2211 be nearly identical to this one.
2213 o Major bugfixes (security, protover, voting):
2214 - Revise Rust implementation of protover to use a more memory-
2215 efficient voting algorithm and corresponding data structures, thus
2216 avoiding a potential memory-based DoS attack where specially
2217 crafted protocol strings would expand to fill available memory.
2218 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
2220 o Major bugfixes (performance, load balancing):
2221 - Directory authorities no longer vote in favor of the Guard flag
2222 for relays without directory support. Starting in Tor
2223 0.3.0.1-alpha, clients have been avoiding using such relays in the
2224 Guard position, leading to increasingly broken load balancing for
2225 the 5%-or-so of Guards that don't advertise directory support.
2226 Fixes bug 22310; bugfix on 0.3.0.6.
2228 o Minor feature (continuous integration):
2229 - Update the Travis CI configuration to use the stable Rust channel,
2230 now that we have decided to require that. Closes ticket 25714.
2232 o Minor features (config options):
2233 - Change the way the default value for MaxMemInQueues is calculated.
2234 We now use 40% of the hardware RAM if the system has 8 GB RAM or
2235 more. Otherwise we use the former value of 75%. Closes
2238 o Minor features (geoip):
2239 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
2240 Country database. Closes ticket 25718.
2242 o Minor bugfixes (client):
2243 - When using a listed relay as a bridge, and also using
2244 microdescriptors, and considering that relay as a non-bridge in a
2245 circuit, treat its microdescriptor as a valid source of
2246 information about that relay. This change should prevent a non-
2247 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
2249 o Minor bugfixes (controller):
2250 - Restore the correct operation of the RESOLVE command, which had
2251 been broken since we added the ability to enable/disable DNS on
2252 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
2254 o Minor bugfixes (distribution, compilation, rust):
2255 - Build correctly when the rust dependencies submodule is loaded,
2256 but the TOR_RUST_DEPENDENCIES environment variable is not set.
2257 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
2258 - Actually include all of our Rust source in our source
2259 distributions. (Previously, a few of the files were accidentally
2260 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
2262 o Minor bugfixes (documentation):
2263 - Document that the PerConnBW{Rate,Burst} options will fall back to
2264 their corresponding consensus parameters only if those parameters
2265 are set. Previously we had claimed that these values would always
2266 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
2267 - Revert a misformatting issue in the ExitPolicy documentation.
2268 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
2270 o Minor bugfixes (exit relay DNS retries):
2271 - Re-attempt timed-out DNS queries 3 times before failure, since our
2272 timeout is 5 seconds for them, but clients wait 10-15. Also allow
2273 slightly more timeouts per resolver when an exit has multiple
2274 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
2276 o Minor bugfixes (onion services):
2277 - Re-instate counting the client HSDir fetch circuits against the
2278 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
2280 - Remove underscores from the _HSLayer{2,3}Nodes options. This
2281 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
2282 Fixes bug 25581; bugfix on 0.3.3.1-alpha
2284 o Code simplification and refactoring:
2285 - Move the list of default directory authorities to its own file.
2286 Closes ticket 24854. Patch by "beastr0".
2288 o Documentation (manpage, denial of service):
2289 - Provide more detail about the denial-of-service options, by
2290 listing each mitigation and explaining how they relate. Closes
2294 Changes in version 0.3.3.4-alpha - 2018-03-29
2295 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
2296 the alpha testing of earlier releases in its series. We are
2297 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
2299 o New system requirements:
2300 - When built with Rust, Tor now depends on version 0.2.39 of the
2301 libc crate. Closes tickets 25310 and 25664.
2303 o Major bugfixes (relay, connection):
2304 - If we have failed to connect to a relay and received a connection
2305 refused, timeout, or similar error (at the TCP level), do not try
2306 that same address/port again for 60 seconds after the failure has
2307 occurred. Fixes bug 24767; bugfix on 0.0.6.
2309 o Minor features (geoip):
2310 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
2311 Country database. Closes ticket 25469.
2313 o Minor features (log messages):
2314 - Improve log message in the out-of-memory handler to include
2315 information about memory usage from the different compression
2316 backends. Closes ticket 25372.
2318 o Minor features (sandbox):
2319 - Explicitly permit the poll() system call when the Linux
2320 seccomp2-based sandbox is enabled: apparently, some versions of
2321 libc use poll() when calling getpwnam(). Closes ticket 25313.
2323 o Minor bugfixes (C correctness):
2324 - Fix a very unlikely (impossible, we believe) null pointer
2325 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
2326 Coverity; this is CID 1430932.
2328 o Minor bugfixes (channel, client):
2329 - Better identify client connection when reporting to the geoip
2330 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
2332 o Minor bugfixes (compilation):
2333 - Fix a C99 compliance issue in our configuration script that caused
2334 compilation issues when compiling Tor with certain versions of
2335 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
2337 o Minor bugfixes (controller, reliability):
2338 - Avoid a (nonfatal) assertion failure when extending a one-hop
2339 circuit from the controller to become a multihop circuit. Fixes
2340 bug 24903; bugfix on 0.2.5.2-alpha.
2342 o Major bugfixes (networking):
2343 - Tor will no longer reject IPv6 address strings from Tor Browser
2344 when they are passed as hostnames in SOCKS5 requests. Fixes bug
2345 25036, bugfix on Tor 0.3.1.2.
2347 o Minor bugfixes (networking):
2348 - string_is_valid_hostname() will not consider IP strings to be
2349 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
2351 o Minor bugfixes (onion service v3):
2352 - Avoid an assertion failure when the next onion service
2353 descriptor rotation type is out of sync with the consensus's
2354 valid-after time. Instead, log a warning message with extra
2355 information, so we can better hunt down the cause of this
2356 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
2358 o Minor bugfixes (testing):
2359 - Avoid intermittent test failures due to a test that had relied on
2360 onion service introduction point creation finishing within 5
2361 seconds of real clock time. Fixes bug 25450; bugfix
2363 - Rust crates are now automatically detected and tested. Previously,
2364 some crates were not tested by `make test-rust` due to a static
2365 string in the `src/test/test_rust.sh` script specifying which
2366 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
2368 o Minor bugfixes (testing, benchmarks):
2369 - Fix a crash when running benchmark tests on win32 systems. The
2370 crash was due to a mutex that wasn't initialized before logging
2371 and options were initialized. Fixes bug 25479; bugfix
2374 o Minor bugfixes (warnings, ipv6):
2375 - Avoid a bug warning that could occur when trying to connect to a
2376 relay over IPv6. This warning would occur on a Tor instance that
2377 downloads router descriptors, but prefers to use microdescriptors.
2378 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
2380 o Code simplification and refactoring:
2381 - Remove the old (deterministic) directory retry logic entirely:
2382 We've used exponential backoff exclusively for some time. Closes
2386 - Improved the documentation of AccountingStart parameter. Closes
2388 - Update the documentation for "Log" to include the current list of
2389 logging domains. Closes ticket 25378.
2392 Changes in version 0.3.1.10 - 2018-03-03
2393 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
2396 It includes an important security fix for a remote crash attack
2397 against directory authorities, tracked as TROVE-2018-001.
2399 This release also backports our new system for improved resistance to
2400 denial-of-service attacks against relays.
2402 This release also fixes several minor bugs and annoyances from
2405 All directory authorities should upgrade to one of the versions
2406 released today. Relays running 0.3.1.x may wish to update to one of
2407 the versions released today, for the DoS mitigations.
2409 Please note: according to our release calendar, Tor 0.3.1 will no
2410 longer be supported after 1 July 2018. If you will be running Tor
2411 after that date, you should make sure to plan to upgrade to the latest
2412 stable version, or downgrade to 0.2.9 (which will receive long-term
2415 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
2416 - Fix a protocol-list handling bug that could be used to remotely crash
2417 directory authorities with a null-pointer exception. Fixes bug 25074;
2418 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
2421 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
2422 - Give relays some defenses against the recent network overload. We
2423 start with three defenses (default parameters in parentheses).
2424 First: if a single client address makes too many concurrent
2425 connections (>100), hang up on further connections. Second: if a
2426 single client address makes circuits too quickly (more than 3 per
2427 second, with an allowed burst of 90) while also having too many
2428 connections open (3), refuse new create cells for the next while
2429 (1-2 hours). Third: if a client asks to establish a rendezvous
2430 point to you directly, ignore the request. These defenses can be
2431 manually controlled by new torrc options, but relays will also
2432 take guidance from consensus parameters, so there's no need to
2433 configure anything manually. Implements ticket 24902.
2435 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
2436 - Update the sandbox rules so that they should now work correctly
2437 with Glibc 2.26. Closes ticket 24315.
2439 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
2440 - Fix an "off by 2" error in counting rendezvous failures on the
2441 onion service side. While we thought we would stop the rendezvous
2442 attempt after one failed circuit, we were actually making three
2443 circuit attempts before giving up. Now switch to a default of 2,
2444 and allow the consensus parameter "hs_service_max_rdv_failures" to
2445 override. Fixes bug 24895; bugfix on 0.0.6.
2447 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
2448 - Add Link protocol version 5 to the supported protocols list. Fixes
2449 bug 25070; bugfix on 0.3.1.1-alpha.
2451 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
2452 - Fix a set of false positives where relays would consider
2453 connections to other relays as being client-only connections (and
2454 thus e.g. deserving different link padding schemes) if those
2455 relays fell out of the consensus briefly. Now we look only at the
2456 initial handshake and whether the connection authenticated as a
2457 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
2459 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
2460 - Make our OOM handler aware of the geoip client history cache so it
2461 doesn't fill up the memory. This check is important for IPv6 and
2462 our DoS mitigation subsystem. Closes ticket 25122.
2464 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
2465 - Change relay bandwidth reporting stats interval from 4 hours to 24
2466 hours in order to reduce the efficiency of guard discovery
2467 attacks. Fixes ticket 23856.
2469 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
2470 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
2471 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
2472 since they neither disabled TLS 1.3 nor enabled any of the
2473 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
2474 Closes ticket 24978.
2476 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
2477 - The fallback directory list has been re-generated based on the
2478 current status of the network. Tor uses fallback directories to
2479 bootstrap when it doesn't yet have up-to-date directory
2480 information. Closes ticket 24801.
2481 - Make the default DirAuthorityFallbackRate 0.1, so that clients
2482 prefer to bootstrap from fallback directory mirrors. This is a
2483 follow-up to 24679, which removed weights from the default
2484 fallbacks. Implements ticket 24681.
2486 o Minor features (geoip):
2487 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
2490 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
2491 - Use the actual observed address of an incoming relay connection,
2492 not the canonical address of the relay from its descriptor, when
2493 making decisions about how to handle the incoming connection.
2494 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
2496 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
2497 - Directory authorities, when refusing a descriptor from a rejected
2498 relay, now explicitly tell the relay (in its logs) to set a valid
2499 ContactInfo address and contact the bad-relays@ mailing list.
2500 Fixes bug 25170; bugfix on 0.2.9.1.
2502 o Minor bugfixes (address selection, backport from 0.3.2.9):
2503 - When the fascist_firewall_choose_address_ functions don't find a
2504 reachable address, set the returned address to the null address
2505 and port. This is a precautionary measure, because some callers do
2506 not check the return value. Fixes bug 24736; bugfix
2509 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
2510 - Fetch descriptors aggressively whenever we lack enough to build
2511 circuits, regardless of how many descriptors we are missing.
2512 Previously, we would delay launching the fetch when we had fewer
2513 than 15 missing descriptors, even if some of those descriptors
2514 were blocking circuits from building. Fixes bug 23985; bugfix on
2515 0.1.1.11-alpha. The effects of this bug became worse in
2516 0.3.0.3-alpha, when we began treating missing descriptors from our
2517 primary guards as a reason to delay circuits.
2518 - Don't try fetching microdescriptors from relays that have failed
2519 to deliver them in the past. Fixes bug 23817; bugfix
2522 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
2523 - Fix a signed/unsigned comparison warning introduced by our fix to
2524 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
2526 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
2527 - Avoid a crash when attempting to use the seccomp2 sandbox together
2528 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
2531 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
2532 - Fix a possible crash on malformed consensus. If a consensus had
2533 contained an unparseable protocol line, it could have made clients
2534 and relays crash with a null-pointer exception. To exploit this
2535 issue, however, an attacker would need to be able to subvert the
2536 directory authority system. Fixes bug 25251; bugfix on
2537 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
2539 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
2540 - Recover better from empty or corrupt files in the consensus cache
2541 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
2542 - When a consensus diff calculation is only partially successful,
2543 only record the successful parts as having succeeded. Partial
2544 success can happen if (for example) one compression method fails
2545 but the others succeed. Previously we misrecorded all the
2546 calculations as having succeeded, which would later cause a
2547 nonfatal assertion failure. Fixes bug 24086; bugfix
2550 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
2551 - Tor now updates its guard state when it reads a consensus
2552 regardless of whether it's missing descriptors. That makes tor use
2553 its primary guards to fetch descriptors in some edge cases where
2554 it would previously have used fallback directories. Fixes bug
2555 23862; bugfix on 0.3.0.1-alpha.
2557 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
2558 - Don't treat inability to store a cached consensus object as a bug:
2559 it can happen normally when we are out of disk space. Fixes bug
2560 24859; bugfix on 0.3.1.1-alpha.
2562 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
2563 - When queuing DESTROY cells on a channel, only queue the circuit-id
2564 and reason fields: not the entire 514-byte cell. This fix should
2565 help mitigate any bugs or attacks that fill up these queues, and
2566 free more RAM for other uses. Fixes bug 24666; bugfix
2569 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
2570 - When closing a connection via close_connection_immediately(), we
2571 mark it as "not blocked on bandwidth", to prevent later calls from
2572 trying to unblock it, and give it permission to read. This fixes a
2573 backtrace warning that can happen on relays under various
2574 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
2576 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
2577 - When selecting relays by bandwidth, avoid a rounding error that
2578 could sometimes cause load to be imbalanced incorrectly.
2579 Previously, we would always round upwards; now, we round towards
2580 the nearest integer. This had the biggest effect when a relay's
2581 weight adjustments should have given it weight 0, but it got
2582 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
2583 - When calculating the fraction of nodes that have descriptors, and
2584 all nodes in the network have zero bandwidths, count the number of
2585 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
2586 - Actually log the total bandwidth in compute_weighted_bandwidths().
2587 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
2589 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
2590 - Improve the performance of our consensus-diff application code
2591 when Tor is built with the --enable-fragile-hardening option set.
2592 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
2594 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
2595 - Don't exit the Tor process if setrlimit() fails to change the file
2596 limit (which can happen sometimes on some versions of OSX). Fixes
2597 bug 21074; bugfix on 0.0.9pre5.
2599 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
2600 - Fix a bug in the bit-counting parts of our timing-wheel code on
2601 MSVC. (Note that MSVC is still not a supported build platform, due
2602 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
2605 o Minor bugfixes (relay, partial backport):
2606 - Make the internal channel_is_client() function look at what sort
2607 of connection handshake the other side used, rather than whether
2608 the other side ever sent a create_fast cell to us. Backports part
2609 of the fixes from bugs 22805 and 24898.
2611 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
2612 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
2614 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
2615 bugfix on 0.2.9.4-alpha.
2617 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
2618 - Update the "rust dependencies" submodule to be a project-level
2619 repository, rather than a user repository. Closes ticket 25323.
2622 Changes in version 0.2.9.15 - 2018-03-03
2623 Tor 0.2.9.15 backports important security and stability bugfixes from
2626 It includes an important security fix for a remote crash attack
2627 against directory authorities, tracked as TROVE-2018-001.
2629 This release also backports our new system for improved resistance to
2630 denial-of-service attacks against relays.
2632 This release also fixes several minor bugs and annoyances from
2635 All directory authorities should upgrade to one of the versions
2636 released today. Relays running 0.2.9.x may wish to update to one of
2637 the versions released today, for the DoS mitigations.
2639 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
2640 - Fix a protocol-list handling bug that could be used to remotely crash
2641 directory authorities with a null-pointer exception. Fixes bug 25074;
2642 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
2645 o Major features (denial-of-service mitigation):
2646 - Give relays some defenses against the recent network overload. We
2647 start with three defenses (default parameters in parentheses).
2648 First: if a single client address makes too many concurrent
2649 connections (>100), hang up on further connections. Second: if a
2650 single client address makes circuits too quickly (more than 3 per
2651 second, with an allowed burst of 90) while also having too many
2652 connections open (3), refuse new create cells for the next while
2653 (1-2 hours). Third: if a client asks to establish a rendezvous
2654 point to you directly, ignore the request. These defenses can be
2655 manually controlled by new torrc options, but relays will also
2656 take guidance from consensus parameters, so there's no need to
2657 configure anything manually. Implements ticket 24902.
2659 o Major bugfixes (bootstrapping):
2660 - Fetch descriptors aggressively whenever we lack enough to build
2661 circuits, regardless of how many descriptors we are missing.
2662 Previously, we would delay launching the fetch when we had fewer
2663 than 15 missing descriptors, even if some of those descriptors
2664 were blocking circuits from building. Fixes bug 23985; bugfix on
2665 0.1.1.11-alpha. The effects of this bug became worse in
2666 0.3.0.3-alpha, when we began treating missing descriptors from our
2667 primary guards as a reason to delay circuits.
2669 o Major bugfixes (onion services, retry behavior):
2670 - Fix an "off by 2" error in counting rendezvous failures on the
2671 onion service side. While we thought we would stop the rendezvous
2672 attempt after one failed circuit, we were actually making three
2673 circuit attempts before giving up. Now switch to a default of 2,
2674 and allow the consensus parameter "hs_service_max_rdv_failures" to
2675 override. Fixes bug 24895; bugfix on 0.0.6.
2677 o Minor feature (relay statistics):
2678 - Change relay bandwidth reporting stats interval from 4 hours to 24
2679 hours in order to reduce the efficiency of guard discovery
2680 attacks. Fixes ticket 23856.
2682 o Minor features (compatibility, OpenSSL):
2683 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
2684 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
2685 since they neither disabled TLS 1.3 nor enabled any of the
2686 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
2687 Closes ticket 24978.
2689 o Minor features (denial-of-service avoidance):
2690 - Make our OOM handler aware of the geoip client history cache so it
2691 doesn't fill up the memory. This check is important for IPv6 and
2692 our DoS mitigation subsystem. Closes ticket 25122.
2694 o Minor features (fallback directory mirrors):
2695 - The fallback directory list has been re-generated based on the
2696 current status of the network. Tor uses fallback directories to
2697 bootstrap when it doesn't yet have up-to-date directory
2698 information. Closes ticket 24801.
2699 - Make the default DirAuthorityFallbackRate 0.1, so that clients
2700 prefer to bootstrap from fallback directory mirrors. This is a
2701 follow-up to 24679, which removed weights from the default
2702 fallbacks. Implements ticket 24681.
2704 o Minor features (geoip):
2705 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
2708 o Minor features (linux seccomp2 sandbox):
2709 - Update the sandbox rules so that they should now work correctly
2710 with Glibc 2.26. Closes ticket 24315.
2712 o Minor bugfix (channel connection):
2713 - Use the actual observed address of an incoming relay connection,
2714 not the canonical address of the relay from its descriptor, when
2715 making decisions about how to handle the incoming connection.
2716 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
2718 o Minor bugfix (directory authority):
2719 - Directory authorities, when refusing a descriptor from a rejected
2720 relay, now explicitly tell the relay (in its logs) to set a valid
2721 ContactInfo address and contact the bad-relays@ mailing list.
2722 Fixes bug 25170; bugfix on 0.2.9.1.
2724 o Minor bugfixes (address selection):
2725 - When the fascist_firewall_choose_address_ functions don't find a
2726 reachable address, set the returned address to the null address
2727 and port. This is a precautionary measure, because some callers do
2728 not check the return value. Fixes bug 24736; bugfix
2731 o Minor bugfixes (compilation):
2732 - Fix a signed/unsigned comparison warning introduced by our fix to
2733 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
2735 o Minor bugfixes (control port, linux seccomp2 sandbox):
2736 - Avoid a crash when attempting to use the seccomp2 sandbox together
2737 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
2740 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
2741 - Fix a possible crash on malformed consensus. If a consensus had
2742 contained an unparseable protocol line, it could have made clients
2743 and relays crash with a null-pointer exception. To exploit this
2744 issue, however, an attacker would need to be able to subvert the
2745 directory authority system. Fixes bug 25251; bugfix on
2746 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
2748 o Minor bugfixes (memory usage):
2749 - When queuing DESTROY cells on a channel, only queue the circuit-id
2750 and reason fields: not the entire 514-byte cell. This fix should
2751 help mitigate any bugs or attacks that fill up these queues, and
2752 free more RAM for other uses. Fixes bug 24666; bugfix
2755 o Minor bugfixes (network layer):
2756 - When closing a connection via close_connection_immediately(), we
2757 mark it as "not blocked on bandwidth", to prevent later calls from
2758 trying to unblock it, and give it permission to read. This fixes a
2759 backtrace warning that can happen on relays under various
2760 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
2762 o Minor bugfixes (OSX):
2763 - Don't exit the Tor process if setrlimit() fails to change the file
2764 limit (which can happen sometimes on some versions of OSX). Fixes
2765 bug 21074; bugfix on 0.0.9pre5.
2767 o Minor bugfixes (path selection):
2768 - When selecting relays by bandwidth, avoid a rounding error that
2769 could sometimes cause load to be imbalanced incorrectly.
2770 Previously, we would always round upwards; now, we round towards
2771 the nearest integer. This had the biggest effect when a relay's
2772 weight adjustments should have given it weight 0, but it got
2773 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
2774 - When calculating the fraction of nodes that have descriptors, and
2775 all nodes in the network have zero bandwidths, count the number of
2776 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
2777 - Actually log the total bandwidth in compute_weighted_bandwidths().
2778 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
2780 o Minor bugfixes (portability, msvc):
2781 - Fix a bug in the bit-counting parts of our timing-wheel code on
2782 MSVC. (Note that MSVC is still not a supported build platform, due
2783 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
2786 o Minor bugfixes (relay):
2787 - Make the internal channel_is_client() function look at what sort
2788 of connection handshake the other side used, rather than whether
2789 the other side ever sent a create_fast cell to us. Backports part
2790 of the fixes from bugs 22805 and 24898.
2792 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
2793 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
2795 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
2796 bugfix on 0.2.9.4-alpha.
2799 Changes in version 0.3.2.10 - 2018-03-03
2800 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
2801 backports a number of bugfixes, including important fixes for security
2804 It includes an important security fix for a remote crash attack
2805 against directory authorities, tracked as TROVE-2018-001.
2807 Additionally, it backports a fix for a bug whose severity we have
2808 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
2809 triggered in order to crash relays with a use-after-free pattern. As
2810 such, we are now tracking that bug as TROVE-2018-002 and
2811 CVE-2018-0491, and backporting it to earlier releases. This bug
2812 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
2815 This release also backports our new system for improved resistance to
2816 denial-of-service attacks against relays.
2818 This release also fixes several minor bugs and annoyances from
2821 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
2822 today, for the fix to TROVE-2018-002. Directory authorities should
2823 also upgrade. (Relays on earlier versions might want to update too for
2824 the DoS mitigations.)
2826 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
2827 - Fix a protocol-list handling bug that could be used to remotely crash
2828 directory authorities with a null-pointer exception. Fixes bug 25074;
2829 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
2832 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
2833 - Avoid adding the same channel twice in the KIST scheduler pending
2834 list, which could lead to remote denial-of-service use-after-free
2835 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
2837 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
2838 - Give relays some defenses against the recent network overload. We
2839 start with three defenses (default parameters in parentheses).
2840 First: if a single client address makes too many concurrent
2841 connections (>100), hang up on further connections. Second: if a
2842 single client address makes circuits too quickly (more than 3 per
2843 second, with an allowed burst of 90) while also having too many
2844 connections open (3), refuse new create cells for the next while
2845 (1-2 hours). Third: if a client asks to establish a rendezvous
2846 point to you directly, ignore the request. These defenses can be
2847 manually controlled by new torrc options, but relays will also
2848 take guidance from consensus parameters, so there's no need to
2849 configure anything manually. Implements ticket 24902.
2851 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
2852 - Fix an "off by 2" error in counting rendezvous failures on the
2853 onion service side. While we thought we would stop the rendezvous
2854 attempt after one failed circuit, we were actually making three
2855 circuit attempts before giving up. Now switch to a default of 2,
2856 and allow the consensus parameter "hs_service_max_rdv_failures" to
2857 override. Fixes bug 24895; bugfix on 0.0.6.
2858 - New-style (v3) onion services now obey the "max rendezvous circuit
2859 attempts" logic. Previously they would make as many rendezvous
2860 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
2861 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
2863 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
2864 - Add Link protocol version 5 to the supported protocols list. Fixes
2865 bug 25070; bugfix on 0.3.1.1-alpha.
2867 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
2868 - Fix a set of false positives where relays would consider
2869 connections to other relays as being client-only connections (and
2870 thus e.g. deserving different link padding schemes) if those
2871 relays fell out of the consensus briefly. Now we look only at the
2872 initial handshake and whether the connection authenticated as a
2873 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
2875 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
2876 - The scheduler subsystem was failing to promptly notice changes in
2877 consensus parameters, making it harder to switch schedulers
2878 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
2880 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
2881 - Make our OOM handler aware of the geoip client history cache so it
2882 doesn't fill up the memory. This check is important for IPv6 and
2883 our DoS mitigation subsystem. Closes ticket 25122.
2885 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
2886 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
2887 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
2888 since they neither disabled TLS 1.3 nor enabled any of the
2889 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
2890 Closes ticket 24978.
2892 o Minor features (geoip):
2893 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
2896 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
2897 - When logging a failure to create an onion service's descriptor,
2898 also log what the problem with the descriptor was. Diagnostic
2901 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
2902 - Use the actual observed address of an incoming relay connection,
2903 not the canonical address of the relay from its descriptor, when
2904 making decisions about how to handle the incoming connection.
2905 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
2907 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
2908 - Fix a possible crash on malformed consensus. If a consensus had
2909 contained an unparseable protocol line, it could have made clients
2910 and relays crash with a null-pointer exception. To exploit this
2911 issue, however, an attacker would need to be able to subvert the
2912 directory authority system. Fixes bug 25251; bugfix on
2913 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
2915 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
2916 - Directory authorities, when refusing a descriptor from a rejected
2917 relay, now explicitly tell the relay (in its logs) to set a valid
2918 ContactInfo address and contact the bad-relays@ mailing list.
2919 Fixes bug 25170; bugfix on 0.2.9.1.
2921 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
2922 - When building with Rust on OSX, link against libresolv, to work
2923 around the issue at https://github.com/rust-lang/rust/issues/46797.
2924 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
2926 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
2927 - Remove a BUG() statement when a client fetches an onion descriptor
2928 that has a lower revision counter than the one in its cache. This
2929 can happen in normal circumstances due to HSDir desync. Fixes bug
2930 24976; bugfix on 0.3.2.1-alpha.
2932 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
2933 - Don't treat inability to store a cached consensus object as a bug:
2934 it can happen normally when we are out of disk space. Fixes bug
2935 24859; bugfix on 0.3.1.1-alpha.
2937 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
2938 - Improve the performance of our consensus-diff application code
2939 when Tor is built with the --enable-fragile-hardening option set.
2940 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
2942 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
2943 - Don't exit the Tor process if setrlimit() fails to change the file
2944 limit (which can happen sometimes on some versions of OSX). Fixes
2945 bug 21074; bugfix on 0.0.9pre5.
2947 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
2948 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
2950 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
2951 bugfix on 0.2.9.4-alpha.
2953 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
2954 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
2955 25005; bugfix on 0.3.2.7-rc.
2957 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
2958 - Look at the "HSRend" protocol version, not the "HSDir" protocol
2959 version, when deciding whether a consensus entry can support the
2960 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
2961 bugfix on 0.3.2.1-alpha.
2963 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
2964 - Update the "rust dependencies" submodule to be a project-level
2965 repository, rather than a user repository. Closes ticket 25323.
2967 o Documentation (backport from 0.3.3.1-alpha)
2968 - Document that operators who run more than one relay or bridge are
2969 expected to set MyFamily and ContactInfo correctly. Closes
2973 Changes in version 0.3.3.3-alpha - 2018-03-03
2974 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
2975 It includes an important security fix for a remote crash attack
2976 against directory authorities tracked as TROVE-2018-001.
2978 Additionally, with this release, we are upgrading the severity of a
2979 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
2980 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
2981 a use-after-free pattern. As such, we are now tracking that bug as
2982 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
2983 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
2985 This release also fixes several minor bugs and annoyances from
2988 Relays running 0.3.2.x should upgrade to one of the versions released
2989 today, for the fix to TROVE-2018-002. Directory authorities should
2990 also upgrade. (Relays on earlier versions might want to update too for
2991 the DoS mitigations.)
2993 o Major bugfixes (denial-of-service, directory authority):
2994 - Fix a protocol-list handling bug that could be used to remotely crash
2995 directory authorities with a null-pointer exception. Fixes bug 25074;
2996 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
2999 o Minor features (compatibility, OpenSSL):
3000 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
3001 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
3002 since they neither disabled TLS 1.3 nor enabled any of the
3003 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
3004 Closes ticket 24978.
3006 o Minor features (logging):
3007 - Clarify the log messages produced when getrandom() or a related
3008 entropy-generation mechanism gives an error. Closes ticket 25120.
3010 o Minor features (testing):
3011 - Add a "make test-rust" target to run the rust tests only. Closes
3014 o Minor bugfixes (denial-of-service):
3015 - Fix a possible crash on malformed consensus. If a consensus had
3016 contained an unparseable protocol line, it could have made clients
3017 and relays crash with a null-pointer exception. To exploit this
3018 issue, however, an attacker would need to be able to subvert the
3019 directory authority system. Fixes bug 25251; bugfix on
3020 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
3022 o Minor bugfixes (DoS mitigation):
3023 - Add extra safety checks when refilling the circuit creation bucket
3024 to ensure we never set a value above the allowed maximum burst.
3025 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
3026 - When a new consensus arrives, don't update our DoS-mitigation
3027 parameters if we aren't a public relay. Fixes bug 25223; bugfix
3030 o Minor bugfixes (man page, SocksPort):
3031 - Remove dead code from the old "SocksSocket" option, and rename
3032 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
3033 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
3035 o Minor bugfixes (performance):
3036 - Reduce the number of circuits that will be opened at once during
3037 the circuit build timeout phase. This is done by increasing the
3038 idle timeout to 3 minutes, and lowering the maximum number of
3039 concurrent learning circuits to 10. Fixes bug 24769; bugfix
3042 o Minor bugfixes (spec conformance):
3043 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
3045 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
3046 bugfix on 0.2.9.4-alpha.
3048 o Minor bugfixes (spec conformance, rust):
3049 - Resolve a denial-of-service issue caused by an infinite loop in
3050 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
3051 Also tracked as TROVE-2018-003.
3053 o Code simplification and refactoring:
3054 - Update the "rust dependencies" submodule to be a project-level
3055 repository, rather than a user repository. Closes ticket 25323.
3058 Changes in version 0.3.3.2-alpha - 2018-02-10
3059 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
3060 introduces a mechanism to handle the high loads that many relay
3061 operators have been reporting recently. It also fixes several bugs in
3062 older releases. If this new code proves reliable, we plan to backport
3063 it to older supported release series.
3065 o Major features (denial-of-service mitigation):
3066 - Give relays some defenses against the recent network overload. We
3067 start with three defenses (default parameters in parentheses).
3068 First: if a single client address makes too many concurrent
3069 connections (>100), hang up on further connections. Second: if a
3070 single client address makes circuits too quickly (more than 3 per
3071 second, with an allowed burst of 90) while also having too many
3072 connections open (3), refuse new create cells for the next while
3073 (1-2 hours). Third: if a client asks to establish a rendezvous
3074 point to you directly, ignore the request. These defenses can be
3075 manually controlled by new torrc options, but relays will also
3076 take guidance from consensus parameters, so there's no need to
3077 configure anything manually. Implements ticket 24902.
3079 o Major bugfixes (netflow padding):
3080 - Stop adding unneeded channel padding right after we finish
3081 flushing to a connection that has been trying to flush for many
3082 seconds. Instead, treat all partial or complete flushes as
3083 activity on the channel, which will defer the time until we need
3084 to add padding. This fix should resolve confusing and scary log
3085 messages like "Channel padding timeout scheduled 221453ms in the
3086 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
3088 o Major bugfixes (protocol versions):
3089 - Add Link protocol version 5 to the supported protocols list. Fixes
3090 bug 25070; bugfix on 0.3.1.1-alpha.
3092 o Major bugfixes (scheduler, consensus):
3093 - The scheduler subsystem was failing to promptly notice changes in
3094 consensus parameters, making it harder to switch schedulers
3095 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
3097 o Minor features (denial-of-service avoidance):
3098 - Make our OOM handler aware of the geoip client history cache so it
3099 doesn't fill up the memory. This check is important for IPv6 and
3100 our DoS mitigation subsystem. Closes ticket 25122.
3102 o Minor features (directory authority):
3103 - When directory authorities are unable to add signatures to a
3104 pending consensus, log the reason why. Closes ticket 24849.
3106 o Minor features (geoip):
3107 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
3110 o Minor features (logging, diagnostic):
3111 - When logging a failure to create an onion service's descriptor,
3112 also log what the problem with the descriptor was. Diagnostic for
3115 o Minor bugfix (channel connection):
3116 - Use the actual observed address of an incoming relay connection,
3117 not the canonical address of the relay from its descriptor, when
3118 making decisions about how to handle the incoming connection.
3119 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
3121 o Minor bugfix (directory authority):
3122 - Directory authorities, when refusing a descriptor from a rejected
3123 relay, now explicitly tell the relay (in its logs) to set a valid
3124 ContactInfo address and contact the bad-relays@ mailing list.
3125 Fixes bug 25170; bugfix on 0.2.9.1.
3127 o Minor bugfixes (all versions of Tor):
3128 - Use the "misspell" tool to detect and fix typos throughout the
3129 source code. Fixes bug 23650; bugfix on various versions of Tor.
3130 Patch from Deepesh Pathak.
3132 o Minor bugfixes (circuit, cannibalization):
3133 - Don't cannibalize preemptively-built circuits if we no longer
3134 recognize their first hop. This situation can happen if our Guard
3135 relay went off the consensus after the circuit was created. Fixes
3136 bug 24469; bugfix on 0.0.6.
3138 o Minor bugfixes (correctness):
3139 - Remove a nonworking, unnecessary check to see whether a circuit
3140 hop's identity digest was set when the circuit failed. Fixes bug
3141 24927; bugfix on 0.2.4.4-alpha.
3143 o Minor bugfixes (logging):
3144 - Don't treat inability to store a cached consensus object as a bug:
3145 it can happen normally when we are out of disk space. Fixes bug
3146 24859; bugfix on 0.3.1.1-alpha.
3147 - Fix a (mostly harmless) race condition when invoking
3148 LOG_PROTOCOL_WARN message from a subthread while the torrc options
3149 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
3151 o Minor bugfixes (onion services):
3152 - Remove a BUG() statement when a client fetches an onion descriptor
3153 that has a lower revision counter than the one in its cache. This
3154 can happen in normal circumstances due to HSDir desync. Fixes bug
3155 24976; bugfix on 0.3.2.1-alpha.
3156 - If we are configured to offer a single onion service, don't log
3157 long-term established one hop rendezvous points in the heartbeat.
3158 Fixes bug 25116; bugfix on 0.2.9.6-rc.
3160 o Minor bugfixes (performance):
3161 - Avoid calling protocol_list_supports_protocol() from inside tight
3162 loops when running with cached routerinfo_t objects. Instead,
3163 summarize the relevant protocols as flags in the routerinfo_t, as
3164 we do for routerstatus_t objects. This change simplifies our code
3165 a little, and saves a large amount of short-term memory allocation
3166 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
3168 o Minor bugfixes (Rust FFI):
3169 - Fix a minor memory leak which would happen whenever the C code
3170 would call the Rust implementation of
3171 protover_get_supported_protocols(). This was due to the C version
3172 returning a static string, whereas the Rust version newly allocated
3173 a CString to pass across the FFI boundary. Consequently, the C
3174 code was not expecting to need to free() what it was given. Fixes
3175 bug 25127; bugfix on 0.3.2.1-alpha.
3177 o Minor bugfixes (scheduler, KIST):
3178 - Avoid adding the same channel twice in the KIST scheduler pending
3179 list, which would waste CPU cycles. Fixes bug 24700; bugfix
3182 o Minor bugfixes (unit test, monotonic time):
3183 - Increase a constant (1msec to 10msec) in the monotonic time test
3184 that makes sure the nsec/usec/msec times read are synchronized.
3185 This change was needed to accommodate slow systems like armel or
3186 when the clock_gettime() is not a VDSO on the running kernel.
3187 Fixes bug 25113; bugfix on 0.2.9.1.
3189 o Minor bugfixes (v3 onion services):
3190 - Look at the "HSRend" protocol version, not the "HSDir" protocol
3191 version, when deciding whether a consensus entry can support the
3192 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
3193 bugfix on 0.3.2.1-alpha.
3195 o Code simplification and refactoring:
3196 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
3198 - Remove a series of counters used to track circuit extend attempts
3199 and connection status but that in reality we aren't using for
3200 anything other than stats logged by a SIGUSR1 signal. Closes
3203 o Documentation (man page):
3204 - The HiddenServiceVersion torrc option accepts only one number:
3205 either version 2 or 3. Closes ticket 25026; bugfix
3209 Changes in version 0.3.3.1-alpha - 2018-01-25
3210 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
3211 several new features to Tor, including several improvements to
3212 bootstrapping, and support for an experimental "vanguards" feature to
3213 resist guard discovery attacks. This series also includes better
3214 support for applications that need to embed Tor or manage v3
3217 o Major features (embedding):
3218 - There is now a documented stable API for programs that need to
3219 embed Tor. See tor_api.h for full documentation and known bugs.
3220 Closes ticket 23684.
3221 - Tor now has support for restarting in the same process.
3222 Controllers that run Tor using the "tor_api.h" interface can now
3223 restart Tor after Tor has exited. This support is incomplete,
3224 however: we fixed crash bugs that prevented it from working at
3225 all, but many bugs probably remain, including a possibility of
3226 security issues. Implements ticket 24581.
3228 o Major features (IPv6, directory documents):
3229 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
3230 consensus. This information makes it easier for IPv6 clients to
3231 bootstrap and choose reachable entry guards. Implements ticket 23826.
3232 - Add consensus method 28, which removes IPv6 ORPorts from
3233 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
3234 are redundant in microdescs. This change will be used by Tor clients
3235 on 0.2.8.x and later. (That is to say, with all Tor clients that
3236 have IPv6 bootstrap and guard support.) Implements ticket 23828.
3237 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
3238 set by different numbers of authorities. Fixes 23870
3241 o Major features (onion service v3, control port):
3242 - The control port now supports commands and events for v3 onion
3243 services. It is now possible to create ephemeral v3 services using
3244 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
3245 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
3246 DEL_ONION) have been extended to support v3 onion services. Closes
3247 ticket 20699; implements proposal 284.
3249 o Major features (onion services):
3250 - Provide torrc options to pin the second and third hops of onion
3251 service circuits to a list of nodes. The option HSLayer2Guards
3252 pins the second hop, and the option HSLayer3Guards pins the third
3253 hop. These options are for use in conjunction with experiments
3254 with "vanguards" for preventing guard enumeration attacks. Closes
3257 o Major features (rust, portability, experimental):
3258 - Tor now ships with an optional implementation of one of its
3259 smaller modules (protover.c) in the Rust programming language. To
3260 try it out, install a Rust build environment, and configure Tor
3261 with "--enable-rust --enable-cargo-online-mode". This should not
3262 cause any user-visible changes, but should help us gain more
3263 experience with Rust, and plan future Rust integration work.
3264 Implementation by Chelsea Komlo. Closes ticket 22840.
3266 o Minor features (storage, configuration):
3267 - Users can store cached directory documents somewhere other than
3268 the DataDirectory by using the CacheDirectory option. Similarly,
3269 the storage location for relay's keys can be overridden with the
3270 KeyDirectory option. Closes ticket 22703.
3272 o Major features (v3 onion services, ipv6):
3273 - When v3 onion service clients send introduce cells, they now
3274 include the IPv6 address of the rendezvous point, if it has one.
3275 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
3276 in future Tor versions, IPv6-only v3 single onion services will be
3277 able to use IPv6 addresses to connect directly to the rendezvous
3278 point. Closes ticket 23577. Patch by Neel Chauhan.
3280 o Major bugfixes (onion services, retry behavior):
3281 - Fix an "off by 2" error in counting rendezvous failures on the
3282 onion service side. While we thought we would stop the rendezvous
3283 attempt after one failed circuit, we were actually making three
3284 circuit attempts before giving up. Now switch to a default of 2,
3285 and allow the consensus parameter "hs_service_max_rdv_failures" to
3286 override. Fixes bug 24895; bugfix on 0.0.6.
3287 - New-style (v3) onion services now obey the "max rendezvous circuit
3288 attempts" logic. Previously they would make as many rendezvous
3289 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
3290 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
3292 o Major bugfixes (relays):
3293 - Fix a set of false positives where relays would consider
3294 connections to other relays as being client-only connections (and
3295 thus e.g. deserving different link padding schemes) if those
3296 relays fell out of the consensus briefly. Now we look only at the
3297 initial handshake and whether the connection authenticated as a
3298 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
3300 o Minor feature (IPv6):
3301 - Make IPv6-only clients wait for microdescs for relays, even if we
3302 were previously using descriptors (or were using them as a bridge)
3303 and have a cached descriptor for them. Implements ticket 23827.
3304 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
3305 them, rather than waiting to download microdescriptors.
3306 Implements ticket 23827.
3308 o Minor features (cleanup):
3309 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
3310 when it stops. Closes ticket 23271.
3312 o Minor features (defensive programming):
3313 - Most of the functions in Tor that free objects have been replaced
3314 with macros that free the objects and set the corresponding
3315 pointers to NULL. This change should help prevent a large class of
3316 dangling pointer bugs. Closes ticket 24337.
3317 - Where possible, the tor_free() macro now only evaluates its input
3318 once. Part of ticket 24337.
3319 - Check that microdesc ed25519 ids are non-zero in
3320 node_get_ed25519_id() before returning them. Implements ticket
3321 24001, patch by "aruna1234".
3323 o Minor features (embedding):
3324 - Tor can now start with a preauthenticated control connection
3325 created by the process that launched it. This feature is meant for
3326 use by programs that want to launch and manage a Tor process
3327 without allowing other programs to manage it as well. For more
3328 information, see the __OwningControllerFD option documented in
3329 control-spec.txt. Closes ticket 23900.
3330 - On most errors that would cause Tor to exit, it now tries to
3331 return from the tor_main() function, rather than calling the
3332 system exit() function. Most users won't notice a difference here,
3333 but it should be significant for programs that run Tor inside
3334 a separate thread: they should now be able to survive Tor's exit
3335 conditions rather than having Tor shut down the entire process.
3336 Closes ticket 23848.
3337 - Applications that want to embed Tor can now tell Tor not to
3338 register any of its own POSIX signal handlers, using the
3339 __DisableSignalHandlers option. Closes ticket 24588.
3341 o Minor features (fallback directory list):
3342 - Avoid selecting fallbacks that change their IP addresses too
3343 often. Select more fallbacks by ignoring the Guard flag, and
3344 allowing lower cutoffs for the Running and V2Dir flags. Also allow
3345 a lower bandwidth, and a higher number of fallbacks per operator
3346 (5% of the list). Implements ticket 24785.
3347 - Update the fallback whitelist and blacklist based on opt-ins and
3348 relay changes. Closes tickets 22321, 24678, 22527, 24135,
3351 o Minor features (fallback directory mirror configuration):
3352 - Add a nickname to each fallback in a C comment. This makes it
3353 easier for operators to find their relays, and allows stem to use
3354 nicknames to identify fallbacks. Implements ticket 24600.
3355 - Add a type and version header to the fallback directory mirror
3356 file. Also add a delimiter to the end of each fallback entry. This
3357 helps external parsers like stem and Relay Search. Implements
3359 - Add an extrainfo cache flag for each fallback in a C comment. This
3360 allows stem to use fallbacks to fetch extra-info documents, rather
3361 than using authorities. Implements ticket 22759.
3362 - Add the generateFallbackDirLine.py script for automatically
3363 generating fallback directory mirror lines from relay fingerprints.
3364 No more typos! Add the lookupFallbackDirContact.py script for
3365 automatically looking up operator contact info from relay
3366 fingerprints. Implements ticket 24706, patch by teor and atagar.
3367 - Reject any fallback directory mirror that serves an expired
3368 consensus. Implements ticket 20942, patch by "minik".
3369 - Remove commas and equals signs from external string inputs to the
3370 fallback list. This avoids format confusion attacks. Implements
3372 - Remove the "weight=10" line from fallback directory mirror
3373 entries. Ticket 24681 will maintain the current fallback weights
3374 by changing Tor's default fallback weight to 10. Implements
3376 - Stop logging excessive information about fallback netblocks.
3377 Implements ticket 24791.
3379 o Minor features (forward-compatibility):
3380 - If a relay supports some link authentication protocol that we do
3381 not recognize, then include that relay's ed25519 key when telling
3382 other relays to extend to it. Previously, we treated future
3383 versions as if they were too old to support ed25519 link
3384 authentication. Closes ticket 20895.
3386 o Minor features (heartbeat):
3387 - Add onion service information to our heartbeat logs, displaying
3388 stats about the activity of configured onion services. Closes
3391 o Minor features (instrumentation, development):
3392 - Add the MainloopStats option to allow developers to get
3393 instrumentation information from the main event loop via the
3394 heartbeat messages. We hope to use this to improve Tor's behavior
3395 when it's trying to sleep. Closes ticket 24605.
3397 o Minor features (log messages):
3398 - Improve a warning message that happens when we fail to re-parse an
3399 old router because of an expired certificate. Closes ticket 20020.
3400 - Make the log more quantitative when we hit MaxMemInQueues
3401 threshold exposing some values. Closes ticket 24501.
3403 o Minor features (logging, android):
3404 - Added support for the Android logging subsystem. Closes
3407 o Minor features (performance):
3408 - Support predictive circuit building for onion service circuits
3409 with multiple layers of guards. Closes ticket 23101.
3410 - Use stdatomic.h where available, rather than mutexes, to implement
3411 atomic_counter_t. Closes ticket 23953.
3413 o Minor features (performance, 32-bit):
3414 - Improve performance on 32-bit systems by avoiding 64-bit division
3415 when calculating the timestamp in milliseconds for channel padding
3416 computations. Implements ticket 24613.
3417 - Improve performance on 32-bit systems by avoiding 64-bit division
3418 when timestamping cells and buffer chunks for OOM calculations.
3419 Implements ticket 24374.
3421 o Minor features (performance, OSX, iOS):
3422 - Use the mach_approximate_time() function (when available) to
3423 implement coarse monotonic time. Having a coarse time function
3424 should avoid a large number of system calls, and improve
3425 performance slightly, especially under load. Closes ticket 24427.
3427 o Minor features (performance, windows):
3428 - Improve performance on Windows Vista and Windows 7 by adjusting
3429 TCP send window size according to the recommendation from
3430 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
3433 o Major features (relay):
3434 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
3435 operator to use a more reasonable ("reduced") exit policy, rather
3436 than the default one. If you want to run an exit node without
3437 thinking too hard about which ports to allow, this one is for you.
3438 Closes ticket 13605. Patch from Neel Chauhan.
3440 o Minor features (testing, debugging, embedding):
3441 - For development purposes, Tor now has a mode in which it runs for
3442 a few seconds, then stops, and starts again without exiting the
3443 process. This mode is meant to help us debug various issues with
3444 ticket 23847. To use this feature, compile with
3445 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
3446 environment variable. This is expected to crash a lot, and is
3447 really meant for developers only. It will likely be removed in a
3448 future release. Implements ticket 24583.
3450 o Minor bugfix (network IPv6 test):
3451 - Tor's test scripts now check if "ping -6 ::1" works when the user
3452 runs "make test-network-all". Fixes bug 24677; bugfix on
3453 0.2.9.3-alpha. Patch by "ffmancera".
3455 o Minor bugfixes (build, rust):
3456 - Fix output of autoconf checks to display success messages for Rust
3457 dependencies and a suitable rustc compiler version. Fixes bug
3458 24612; bugfix on 0.3.1.3-alpha.
3459 - When building with Rust on OSX, link against libresolv, to work
3460 around the issue at https://github.com/rust-lang/rust/issues/46797.
3461 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
3462 - Don't pass the --quiet option to cargo: it seems to suppress some
3463 errors, which is not what we want to do when building. Fixes bug
3464 24518; bugfix on 0.3.1.7.
3465 - Build correctly when building from outside Tor's source tree with
3466 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
3469 o Minor bugfixes (directory authorities, IPv6):
3470 - When creating a routerstatus (vote) from a routerinfo (descriptor),
3471 set the IPv6 address to the unspecified IPv6 address, and
3472 explicitly initialize the port to zero. Fixes bug 24488; bugfix
3475 o Minor bugfixes (fallback directory mirrors):
3476 - Make updateFallbackDirs.py search harder for python. (Some OSs
3477 don't put it in /usr/bin.) Fixes bug 24708; bugfix
3480 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
3481 - When hibernating, close connections normally and allow them to
3482 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
3484 - Do not attempt to launch self-reachability tests when entering
3485 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
3486 - Resolve several bugs related to descriptor fetching on bridge
3487 clients with bandwidth accounting enabled. (This combination is
3488 not recommended!) Fixes a case of bug 12062; bugfix
3490 - When hibernating, do not attempt to launch DNS checks. Fixes a
3491 case of bug 12062; bugfix on 0.1.2.2-alpha.
3492 - When hibernating, do not try to upload or download descriptors.
3493 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
3495 o Minor bugfixes (IPv6, bridges):
3496 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
3497 bugfix on 0.2.8.2-alpha.
3498 - Tor now sets IPv6 address in the routerstatus as well as in the
3499 router descriptors when updating addresses for a bridge. Closes
3500 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
3502 o Minor bugfixes (linux seccomp2 sandbox):
3503 - When running with the sandbox enabled, reload configuration files
3504 correctly even when %include was used. Previously we would crash.
3505 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
3507 o Minor bugfixes (memory leaks):
3508 - Avoid possible at-exit memory leaks related to use of Libevent's
3509 event_base_once() function. (This function tends to leak memory if
3510 the event_base is closed before the event fires.) Fixes bug 24584;
3511 bugfix on 0.2.8.1-alpha.
3512 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
3515 o Minor bugfixes (OSX):
3516 - Don't exit the Tor process if setrlimit() fails to change the file
3517 limit (which can happen sometimes on some versions of OSX). Fixes
3518 bug 21074; bugfix on 0.0.9pre5.
3520 o Minor bugfixes (performance, fragile-hardening):
3521 - Improve the performance of our consensus-diff application code
3522 when Tor is built with the --enable-fragile-hardening option set.
3523 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
3525 o Minor bugfixes (performance, timeouts):
3526 - Consider circuits for timeout as soon as they complete a hop. This
3527 is more accurate than applying the timeout in
3528 circuit_expire_building() because that function is only called
3529 once per second, which is now too slow for typical timeouts on the
3530 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
3531 - Use onion service circuits (and other circuits longer than 3 hops)
3532 to calculate a circuit build timeout. Previously, Tor only
3533 calculated its build timeout based on circuits that planned to be
3534 exactly 3 hops long. With this change, we include measurements
3535 from all circuits at the point where they complete their third
3536 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
3538 o Minor bugfixes (testing):
3539 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
3540 bugfix on 0.2.3.1-alpha.
3541 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
3542 25005; bugfix on 0.3.2.7-rc.
3544 o Code simplification and refactoring:
3545 - Remove /usr/athena from search path in configure.ac. Closes
3547 - Remove duplicate code in node_has_curve25519_onion_key() and
3548 node_get_curve25519_onion_key(), and add a check for a zero
3549 microdesc curve25519 onion key. Closes ticket 23966, patch by
3550 "aruna1234" and teor.
3551 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
3552 memory allocations with large numbers of OR connections (e.g.
3553 relays). Closes ticket 24119.
3554 - Separate the function that deletes ephemeral files when Tor
3556 - Small changes to Tor's buf_t API to make it suitable for use as a
3557 general-purpose safe string constructor. Closes ticket 22342.
3558 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
3559 avoid source code identifier confusion. Closes ticket 24467.
3560 - The tor_git_revision[] constant no longer needs to be redeclared
3561 by everything that links against the rest of Tor. Done as part of
3562 ticket 23845, to simplify our external API.
3563 - We make extend_info_from_node() use node_get_curve25519_onion_key()
3564 introduced in ticket 23577 to access the curve25519 public keys
3565 rather than accessing it directly. Closes ticket 23760. Patch by
3567 - Add a function to log channels' scheduler state changes to aid
3568 debugging efforts. Closes ticket 24531.
3571 - Add documentation on how to build tor with Rust dependencies
3572 without having to be online. Closes ticket 22907; bugfix
3574 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
3575 traffic. Closes ticket 24318.
3576 - Document that OutboundBindAddress doesn't apply to DNS requests.
3577 Closes ticket 22145. Patch from Aruna Maurya.
3578 - Document that operators who run more than one relay or bridge are
3579 expected to set MyFamily and ContactInfo correctly. Closes
3582 o Code simplification and refactoring (channels):
3583 - Remove the incoming and outgoing channel queues. These were never
3584 used, but still took up a step in our fast path.
3585 - The majority of the channel unit tests have been rewritten and the
3586 code coverage has now been raised to 83.6% for channel.c. Closes
3588 - Remove other dead code from the channel subsystem: All together,
3589 this cleanup has removed more than 1500 lines of code overall and
3590 adding very little except for unit test.
3592 o Code simplification and refactoring (circuit rendezvous):
3593 - Split the client-side rendezvous circuit lookup into two
3594 functions: one that returns only established circuits and another
3595 that returns all kinds of circuits. Closes ticket 23459.
3597 o Code simplification and refactoring (controller):
3598 - Make most of the variables in networkstatus_getinfo_by_purpose()
3599 const. Implements ticket 24489.
3602 Changes in version 0.3.2.9 - 2018-01-09
3603 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
3605 The 0.3.2 series includes our long-anticipated new onion service
3606 design, with numerous security features. (For more information, see
3607 our blog post at https://blog.torproject.org/fall-harvest.) We also
3608 have a new circuit scheduler algorithm for improved performance on
3609 relays everywhere (see https://blog.torproject.org/kist-and-tell),
3610 along with many smaller features and bugfixes.
3612 Per our stable release policy, we plan to support each stable release
3613 series for at least the next nine months, or for three months after
3614 the first stable release of the next series: whichever is longer. If
3615 you need a release with long-term support, we recommend that you stay
3616 with the 0.2.9 series.
3618 Below is a list of the changes since 0.3.2.8-rc. For a list of all
3619 changes since 0.3.1, see the ReleaseNotes file.
3621 o Minor features (fallback directory mirrors):
3622 - The fallback directory list has been re-generated based on the
3623 current status of the network. Tor uses fallback directories to
3624 bootstrap when it doesn't yet have up-to-date directory
3625 information. Closes ticket 24801.
3626 - Make the default DirAuthorityFallbackRate 0.1, so that clients
3627 prefer to bootstrap from fallback directory mirrors. This is a
3628 follow-up to 24679, which removed weights from the default
3629 fallbacks. Implements ticket 24681.
3631 o Minor features (geoip):
3632 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
3635 o Minor bugfixes (address selection):
3636 - When the fascist_firewall_choose_address_ functions don't find a
3637 reachable address, set the returned address to the null address
3638 and port. This is a precautionary measure, because some callers do
3639 not check the return value. Fixes bug 24736; bugfix
3642 o Minor bugfixes (compilation):
3643 - Resolve a few shadowed-variable warnings in the onion service
3644 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
3646 o Minor bugfixes (portability, msvc):
3647 - Fix a bug in the bit-counting parts of our timing-wheel code on
3648 MSVC. (Note that MSVC is still not a supported build platform, due
3649 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
3653 Changes in version 0.3.2.8-rc - 2017-12-21
3654 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
3655 schedulers that had led servers under heavy load to overload their
3656 outgoing connections. All relay operators running earlier 0.3.2.x
3657 versions should upgrade. This version also includes a mitigation for
3658 over-full DESTROY queues leading to out-of-memory conditions: if it
3659 works, we will soon backport it to earlier release series.
3661 This is the second release candidate in the 0.3.2 series. If we find
3662 no new bugs or regression here, then the first stable 0.3.2 release
3663 will be nearly identical to this.
3665 o Major bugfixes (KIST, scheduler):
3666 - The KIST scheduler did not correctly account for data already
3667 enqueued in each connection's send socket buffer, particularly in
3668 cases when the TCP/IP congestion window was reduced between
3669 scheduler calls. This situation lead to excessive per-connection
3670 buffering in the kernel, and a potential memory DoS. Fixes bug
3671 24665; bugfix on 0.3.2.1-alpha.
3673 o Minor features (geoip):
3674 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
3677 o Minor bugfixes (hidden service v3):
3678 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
3679 the probability of reaching a service for a client missing
3680 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
3682 o Minor bugfixes (memory usage):
3683 - When queuing DESTROY cells on a channel, only queue the circuit-id
3684 and reason fields: not the entire 514-byte cell. This fix should
3685 help mitigate any bugs or attacks that fill up these queues, and
3686 free more RAM for other uses. Fixes bug 24666; bugfix
3689 o Minor bugfixes (scheduler, KIST):
3690 - Use a sane write limit for KISTLite when writing onto a connection
3691 buffer instead of using INT_MAX and shoving as much as it can.
3692 Because the OOM handler cleans up circuit queues, we are better
3693 off at keeping them in that queue instead of the connection's
3694 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
3697 Changes in version 0.3.2.7-rc - 2017-12-14
3698 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
3699 including some that could affect reliability or correctness.
3701 This is the first release candidate in the 0.3.2 series. If we find no
3702 new bugs or regression here, then the first stable 0.3.2. release will
3703 be nearly identical to this.
3705 o Major bugfixes (circuit prediction):
3706 - Fix circuit prediction logic so that a client doesn't treat a port
3707 as being "handled" by a circuit if that circuit already has
3708 isolation settings on it. This change should make Tor clients more
3709 responsive by improving their chances of having a pre-created
3710 circuit ready for use when a request arrives. Fixes bug 18859;
3711 bugfix on 0.2.3.3-alpha.
3713 o Minor features (logging):
3714 - Provide better warnings when the getrandom() syscall fails. Closes
3717 o Minor features (portability):
3718 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
3719 (It doesn't yet work with the sandbox enabled.) Closes
3722 o Minor bugfixes (bridge clients, bootstrap):
3723 - Retry directory downloads when we get our first bridge descriptor
3724 during bootstrap or while reconnecting to the network. Keep
3725 retrying every time we get a bridge descriptor, until we have a
3726 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
3727 - Stop delaying bridge descriptor fetches when we have cached bridge
3728 descriptors. Instead, only delay bridge descriptor fetches when we
3729 have at least one reachable bridge. Fixes part of bug 24367;
3730 bugfix on 0.2.0.3-alpha.
3731 - Stop delaying directory fetches when we have cached bridge
3732 descriptors. Instead, only delay bridge descriptor fetches when
3733 all our bridges are definitely unreachable. Fixes part of bug
3734 24367; bugfix on 0.2.0.3-alpha.
3736 o Minor bugfixes (compilation):
3737 - Fix a signed/unsigned comparison warning introduced by our fix to
3738 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
3740 o Minor bugfixes (correctness):
3741 - Fix several places in our codebase where a C compiler would be
3742 likely to eliminate a check, based on assuming that undefined
3743 behavior had not happened elsewhere in the code. These cases are
3744 usually a sign of redundant checking or dubious arithmetic. Found
3745 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
3746 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
3749 o Minor bugfixes (onion service v3):
3750 - Fix a race where an onion service would launch a new intro circuit
3751 after closing an old one, but fail to register it before freeing
3752 the previously closed circuit. This bug was making the service
3753 unable to find the established intro circuit and thus not upload
3754 its descriptor, thus making a service unavailable for up to 24
3755 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
3757 o Minor bugfixes (scheduler, KIST):
3758 - Properly set the scheduler state of an unopened channel in the
3759 KIST scheduler main loop. This prevents a harmless but annoying
3760 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
3761 - Avoid a possible integer overflow when computing the available
3762 space on the TCP buffer of a channel. This had no security
3763 implications; but could make KIST allow too many cells on a
3764 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
3765 - Downgrade to "info" a harmless warning about the monotonic time
3766 moving backwards: This can happen on platform not supporting
3767 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
3770 Changes in version 0.3.2.6-alpha - 2017-12-01
3771 This version of Tor is the latest in the 0.3.2 alpha series. It
3772 includes fixes for several important security issues. All Tor users
3773 should upgrade to this release, or to one of the other releases coming
3776 o Major bugfixes (security):
3777 - Fix a denial of service bug where an attacker could use a
3778 malformed directory object to cause a Tor instance to pause while
3779 OpenSSL would try to read a passphrase from the terminal. (Tor
3780 instances run without a terminal, which is the case for most Tor
3781 packages, are not impacted.) Fixes bug 24246; bugfix on every
3782 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
3783 Found by OSS-Fuzz as testcase 6360145429790720.
3784 - Fix a denial of service issue where an attacker could crash a
3785 directory authority using a malformed router descriptor. Fixes bug
3786 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
3788 - When checking for replays in the INTRODUCE1 cell data for a
3789 (legacy) onion service, correctly detect replays in the RSA-
3790 encrypted part of the cell. We were previously checking for
3791 replays on the entire cell, but those can be circumvented due to
3792 the malleability of Tor's legacy hybrid encryption. This fix helps
3793 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
3794 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
3797 o Major bugfixes (security, onion service v2):
3798 - Fix a use-after-free error that could crash v2 Tor onion services
3799 when they failed to open circuits while expiring introduction
3800 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
3801 also tracked as TROVE-2017-013 and CVE-2017-8823.
3803 o Major bugfixes (security, relay):
3804 - When running as a relay, make sure that we never build a path
3805 through ourselves, even in the case where we have somehow lost the
3806 version of our descriptor appearing in the consensus. Fixes part
3807 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
3808 as TROVE-2017-012 and CVE-2017-8822.
3809 - When running as a relay, make sure that we never choose ourselves
3810 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
3811 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
3813 o Minor feature (relay statistics):
3814 - Change relay bandwidth reporting stats interval from 4 hours to 24
3815 hours in order to reduce the efficiency of guard discovery
3816 attacks. Fixes ticket 23856.
3818 o Minor features (directory authority):
3819 - Add an IPv6 address for the "bastet" directory authority. Closes
3822 o Minor bugfixes (client):
3823 - By default, do not enable storage of client-side DNS values. These
3824 values were unused by default previously, but they should not have
3825 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
3828 Changes in version 0.3.1.9 - 2017-12-01:
3829 Tor 0.3.1.9 backports important security and stability fixes from the
3830 0.3.2 development series. All Tor users should upgrade to this
3831 release, or to another of the releases coming out today.
3833 o Major bugfixes (security, backport from 0.3.2.6-alpha):
3834 - Fix a denial of service bug where an attacker could use a
3835 malformed directory object to cause a Tor instance to pause while
3836 OpenSSL would try to read a passphrase from the terminal. (Tor
3837 instances run without a terminal, which is the case for most Tor
3838 packages, are not impacted.) Fixes bug 24246; bugfix on every
3839 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
3840 Found by OSS-Fuzz as testcase 6360145429790720.
3841 - Fix a denial of service issue where an attacker could crash a
3842 directory authority using a malformed router descriptor. Fixes bug
3843 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
3845 - When checking for replays in the INTRODUCE1 cell data for a
3846 (legacy) onion service, correctly detect replays in the RSA-
3847 encrypted part of the cell. We were previously checking for
3848 replays on the entire cell, but those can be circumvented due to
3849 the malleability of Tor's legacy hybrid encryption. This fix helps
3850 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
3851 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
3854 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
3855 - Fix a use-after-free error that could crash v2 Tor onion services
3856 when they failed to open circuits while expiring introduction
3857 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
3858 also tracked as TROVE-2017-013 and CVE-2017-8823.
3860 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
3861 - When running as a relay, make sure that we never build a path
3862 through ourselves, even in the case where we have somehow lost the
3863 version of our descriptor appearing in the consensus. Fixes part
3864 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
3865 as TROVE-2017-012 and CVE-2017-8822.
3866 - When running as a relay, make sure that we never choose ourselves
3867 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
3868 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
3870 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
3871 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
3872 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
3873 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
3874 identifying and finding a workaround to this bug and to Moritz,
3875 Arthur Edelstein, and Roger for helping to track it down and
3878 o Minor features (bridge):
3879 - Bridges now include notice in their descriptors that they are
3880 bridges, and notice of their distribution status, based on their
3881 publication settings. Implements ticket 18329. For more fine-
3882 grained control of how a bridge is distributed, upgrade to 0.3.2.x
3885 o Minor features (directory authority, backport from 0.3.2.6-alpha):
3886 - Add an IPv6 address for the "bastet" directory authority. Closes
3889 o Minor features (geoip):
3890 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
3893 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
3894 - Avoid unnecessary calls to directory_fetches_from_authorities() on
3895 relays, to prevent spurious address resolutions and descriptor
3896 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
3897 bugfix on in 0.2.8.1-alpha.
3899 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
3900 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
3901 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
3903 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
3904 - When a circuit is marked for close, do not attempt to package any
3905 cells for channels on that circuit. Previously, we would detect
3906 this condition lower in the call stack, when we noticed that the
3907 circuit had no attached channel, and log an annoying message.
3908 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
3910 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
3911 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
3912 so it matches dir-spec.txt. Fixes bug 24262; bugfix
3915 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
3916 - Avoid a crash when transitioning from client mode to bridge mode.
3917 Previously, we would launch the worker threads whenever our
3918 "public server" mode changed, but not when our "server" mode
3919 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
3922 Changes in version 0.3.0.13 - 2017-12-01
3923 Tor 0.3.0.13 backports important security and stability bugfixes from
3924 later Tor releases. All Tor users should upgrade to this release, or
3925 to another of the releases coming out today.
3927 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
3928 2018. If you need a release with long-term support, please stick with
3929 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
3931 o Major bugfixes (security, backport from 0.3.2.6-alpha):
3932 - Fix a denial of service bug where an attacker could use a
3933 malformed directory object to cause a Tor instance to pause while
3934 OpenSSL would try to read a passphrase from the terminal. (Tor
3935 instances run without a terminal, which is the case for most Tor
3936 packages, are not impacted.) Fixes bug 24246; bugfix on every
3937 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
3938 Found by OSS-Fuzz as testcase 6360145429790720.
3939 - Fix a denial of service issue where an attacker could crash a
3940 directory authority using a malformed router descriptor. Fixes bug
3941 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
3943 - When checking for replays in the INTRODUCE1 cell data for a
3944 (legacy) onion service, correctly detect replays in the RSA-
3945 encrypted part of the cell. We were previously checking for
3946 replays on the entire cell, but those can be circumvented due to
3947 the malleability of Tor's legacy hybrid encryption. This fix helps
3948 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
3949 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
3952 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
3953 - Fix a use-after-free error that could crash v2 Tor onion services
3954 when they failed to open circuits while expiring introduction
3955 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
3956 also tracked as TROVE-2017-013 and CVE-2017-8823.
3958 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
3959 - When running as a relay, make sure that we never build a path
3960 through ourselves, even in the case where we have somehow lost the
3961 version of our descriptor appearing in the consensus. Fixes part
3962 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
3963 as TROVE-2017-012 and CVE-2017-8822.
3964 - When running as a relay, make sure that we never choose ourselves
3965 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
3966 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
3968 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
3969 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
3970 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
3971 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
3972 identifying and finding a workaround to this bug and to Moritz,
3973 Arthur Edelstein, and Roger for helping to track it down and
3976 o Minor features (security, windows, backport from 0.3.1.1-alpha):
3977 - Enable a couple of pieces of Windows hardening: one
3978 (HeapEnableTerminationOnCorruption) that has been on-by-default
3979 since Windows 8, and unavailable before Windows 7; and one
3980 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
3981 affect us, but shouldn't do any harm. Closes ticket 21953.
3983 o Minor features (bridge, backport from 0.3.1.9):
3984 - Bridges now include notice in their descriptors that they are
3985 bridges, and notice of their distribution status, based on their
3986 publication settings. Implements ticket 18329. For more fine-
3987 grained control of how a bridge is distributed, upgrade to 0.3.2.x
3990 o Minor features (directory authority, backport from 0.3.2.6-alpha):
3991 - Add an IPv6 address for the "bastet" directory authority. Closes
3994 o Minor features (geoip):
3995 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
3998 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
3999 - Avoid unnecessary calls to directory_fetches_from_authorities() on
4000 relays, to prevent spurious address resolutions and descriptor
4001 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
4002 bugfix on in 0.2.8.1-alpha.
4004 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
4005 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
4006 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
4008 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
4009 - When a circuit is marked for close, do not attempt to package any
4010 cells for channels on that circuit. Previously, we would detect
4011 this condition lower in the call stack, when we noticed that the
4012 circuit had no attached channel, and log an annoying message.
4013 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
4015 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
4016 - Avoid a crash when transitioning from client mode to bridge mode.
4017 Previously, we would launch the worker threads whenever our
4018 "public server" mode changed, but not when our "server" mode
4019 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
4021 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
4022 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4023 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4026 Changes in version 0.2.9.14 - 2017-12-01
4027 Tor 0.3.0.13 backports important security and stability bugfixes from
4028 later Tor releases. All Tor users should upgrade to this release, or
4029 to another of the releases coming out today.
4031 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
4032 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
4033 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
4034 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
4035 identifying and finding a workaround to this bug and to Moritz,
4036 Arthur Edelstein, and Roger for helping to track it down and
4039 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4040 - Fix a denial of service bug where an attacker could use a
4041 malformed directory object to cause a Tor instance to pause while
4042 OpenSSL would try to read a passphrase from the terminal. (Tor
4043 instances run without a terminal, which is the case for most Tor
4044 packages, are not impacted.) Fixes bug 24246; bugfix on every
4045 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4046 Found by OSS-Fuzz as testcase 6360145429790720.
4047 - Fix a denial of service issue where an attacker could crash a
4048 directory authority using a malformed router descriptor. Fixes bug
4049 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
4051 - When checking for replays in the INTRODUCE1 cell data for a
4052 (legacy) onion service, correctly detect replays in the RSA-
4053 encrypted part of the cell. We were previously checking for
4054 replays on the entire cell, but those can be circumvented due to
4055 the malleability of Tor's legacy hybrid encryption. This fix helps
4056 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4057 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4060 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
4061 - Fix a use-after-free error that could crash v2 Tor onion services
4062 when they failed to open circuits while expiring introduction
4063 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
4064 also tracked as TROVE-2017-013 and CVE-2017-8823.
4066 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4067 - When running as a relay, make sure that we never build a path
4068 through ourselves, even in the case where we have somehow lost the
4069 version of our descriptor appearing in the consensus. Fixes part
4070 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
4071 as TROVE-2017-012 and CVE-2017-8822.
4073 o Minor features (bridge, backport from 0.3.1.9):
4074 - Bridges now include notice in their descriptors that they are
4075 bridges, and notice of their distribution status, based on their
4076 publication settings. Implements ticket 18329. For more fine-
4077 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4080 o Minor features (directory authority, backport from 0.3.2.6-alpha):
4081 - Add an IPv6 address for the "bastet" directory authority. Closes
4084 o Minor features (geoip):
4085 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4088 o Minor features (security, windows, backport from 0.3.1.1-alpha):
4089 - Enable a couple of pieces of Windows hardening: one
4090 (HeapEnableTerminationOnCorruption) that has been on-by-default
4091 since Windows 8, and unavailable before Windows 7; and one
4092 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
4093 affect us, but shouldn't do any harm. Closes ticket 21953.
4095 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
4096 - Avoid unnecessary calls to directory_fetches_from_authorities() on
4097 relays, to prevent spurious address resolutions and descriptor
4098 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
4099 bugfix on in 0.2.8.1-alpha.
4101 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
4102 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
4103 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
4105 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
4106 - When a circuit is marked for close, do not attempt to package any
4107 cells for channels on that circuit. Previously, we would detect
4108 this condition lower in the call stack, when we noticed that the
4109 circuit had no attached channel, and log an annoying message.
4110 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
4112 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
4113 - Avoid a crash when transitioning from client mode to bridge mode.
4114 Previously, we would launch the worker threads whenever our
4115 "public server" mode changed, but not when our "server" mode
4116 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
4118 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
4119 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4120 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4123 Changes in version 0.2.8.17 - 2017-12-01
4124 Tor 0.2.8.17 backports important security and stability bugfixes from
4125 later Tor releases. All Tor users should upgrade to this release, or
4126 to another of the releases coming out today.
4128 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
4129 2018. If you need a release with long-term support, please upgrade with
4130 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4132 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4133 - Fix a denial of service bug where an attacker could use a
4134 malformed directory object to cause a Tor instance to pause while
4135 OpenSSL would try to read a passphrase from the terminal. (Tor
4136 instances run without a terminal, which is the case for most Tor
4137 packages, are not impacted.) Fixes bug 24246; bugfix on every
4138 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4139 Found by OSS-Fuzz as testcase 6360145429790720.
4140 - When checking for replays in the INTRODUCE1 cell data for a
4141 (legacy) onion service, correctly detect replays in the RSA-
4142 encrypted part of the cell. We were previously checking for
4143 replays on the entire cell, but those can be circumvented due to
4144 the malleability of Tor's legacy hybrid encryption. This fix helps
4145 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4146 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4149 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
4150 - Fix a use-after-free error that could crash v2 Tor onion services
4151 when they failed to open circuits while expiring introduction
4152 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
4153 also tracked as TROVE-2017-013 and CVE-2017-8823.
4155 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4156 - When running as a relay, make sure that we never build a path through
4157 ourselves, even in the case where we have somehow lost the version of
4158 our descriptor appearing in the consensus. Fixes part of bug 21534;
4159 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
4162 o Minor features (bridge, backport from 0.3.1.9):
4163 - Bridges now include notice in their descriptors that they are
4164 bridges, and notice of their distribution status, based on their
4165 publication settings. Implements ticket 18329. For more fine-
4166 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4169 o Minor features (directory authority, backport from 0.3.2.6-alpha):
4170 - Add an IPv6 address for the "bastet" directory authority. Closes
4173 o Minor features (geoip):
4174 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4177 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
4178 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
4179 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
4182 Changes in version 0.2.5.16 - 2017-12-01
4183 Tor 0.2.5.13 backports important security and stability bugfixes from
4184 later Tor releases. All Tor users should upgrade to this release, or
4185 to another of the releases coming out today.
4187 Note: the Tor 0.2.5 series will no longer be supported after 1 May
4188 2018. If you need a release with long-term support, please upgrade to
4189 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4191 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4192 - Fix a denial of service bug where an attacker could use a
4193 malformed directory object to cause a Tor instance to pause while
4194 OpenSSL would try to read a passphrase from the terminal. (Tor
4195 instances run without a terminal, which is the case for most Tor
4196 packages, are not impacted.) Fixes bug 24246; bugfix on every
4197 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4198 Found by OSS-Fuzz as testcase 6360145429790720.
4199 - When checking for replays in the INTRODUCE1 cell data for a
4200 (legacy) onion service, correctly detect replays in the RSA-
4201 encrypted part of the cell. We were previously checking for
4202 replays on the entire cell, but those can be circumvented due to
4203 the malleability of Tor's legacy hybrid encryption. This fix helps
4204 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4205 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4208 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4209 - When running as a relay, make sure that we never build a path
4210 through ourselves, even in the case where we have somehow lost the
4211 version of our descriptor appearing in the consensus. Fixes part
4212 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
4213 as TROVE-2017-012 and CVE-2017-8822.
4215 o Minor features (bridge, backport from 0.3.1.9):
4216 - Bridges now include notice in their descriptors that they are
4217 bridges, and notice of their distribution status, based on their
4218 publication settings. Implements ticket 18329. For more fine-
4219 grained control of how a bridge is distributed, upgrade to 0.3.2.x
4222 o Minor features (geoip):
4223 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4227 Changes in version 0.3.2.5-alpha - 2017-11-22
4228 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
4229 fixes several stability and reliability bugs, including a fix for
4230 intermittent bootstrapping failures that some people have been seeing
4231 since the 0.3.0.x series.
4233 Please test this alpha out -- many of these fixes will soon be
4234 backported to stable Tor versions if no additional bugs are found
4237 o Major bugfixes (bootstrapping):
4238 - Fetch descriptors aggressively whenever we lack enough to build
4239 circuits, regardless of how many descriptors we are missing.
4240 Previously, we would delay launching the fetch when we had fewer
4241 than 15 missing descriptors, even if some of those descriptors
4242 were blocking circuits from building. Fixes bug 23985; bugfix on
4243 0.1.1.11-alpha. The effects of this bug became worse in
4244 0.3.0.3-alpha, when we began treating missing descriptors from our
4245 primary guards as a reason to delay circuits.
4246 - Don't try fetching microdescriptors from relays that have failed
4247 to deliver them in the past. Fixes bug 23817; bugfix
4250 o Minor features (directory authority):
4251 - Make the "Exit" flag assignment only depend on whether the exit
4252 policy allows connections to ports 80 and 443. Previously relays
4253 would get the Exit flag if they allowed connections to one of
4254 these ports and also port 6667. Resolves ticket 23637.
4256 o Minor features (geoip):
4257 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
4260 o Minor features (linux seccomp2 sandbox):
4261 - Update the sandbox rules so that they should now work correctly
4262 with Glibc 2.26. Closes ticket 24315.
4264 o Minor features (logging):
4265 - Downgrade a pair of log messages that could occur when an exit's
4266 resolver gave us an unusual (but not forbidden) response. Closes
4268 - Improve the message we log when re-enabling circuit build timeouts
4269 after having received a consensus. Closes ticket 20963.
4271 o Minor bugfixes (compilation):
4272 - Fix a memory leak warning in one of the libevent-related
4273 configuration tests that could occur when manually specifying
4274 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
4275 Found and patched by Alex Xu.
4276 - When detecting OpenSSL on Windows from our configure script, make
4277 sure to try linking with the ws2_32 library. Fixes bug 23783;
4278 bugfix on 0.3.2.2-alpha.
4280 o Minor bugfixes (control port, linux seccomp2 sandbox):
4281 - Avoid a crash when attempting to use the seccomp2 sandbox together
4282 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4285 o Minor bugfixes (control port, onion services):
4286 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
4287 HS_DESC event when a service is not able to upload a descriptor.
4288 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
4290 o Minor bugfixes (directory cache):
4291 - Recover better from empty or corrupt files in the consensus cache
4292 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
4293 - When a consensus diff calculation is only partially successful,
4294 only record the successful parts as having succeeded. Partial
4295 success can happen if (for example) one compression method fails
4296 but the others succeed. Previously we misrecorded all the
4297 calculations as having succeeded, which would later cause a
4298 nonfatal assertion failure. Fixes bug 24086; bugfix
4301 o Minor bugfixes (logging):
4302 - Only log once if we notice that KIST support is gone. Fixes bug
4303 24158; bugfix on 0.3.2.1-alpha.
4304 - Suppress a log notice when relay descriptors arrive. We already
4305 have a bootstrap progress for this so no need to log notice
4306 everytime tor receives relay descriptors. Microdescriptors behave
4307 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
4309 o Minor bugfixes (network layer):
4310 - When closing a connection via close_connection_immediately(), we
4311 mark it as "not blocked on bandwidth", to prevent later calls from
4312 trying to unblock it, and give it permission to read. This fixes a
4313 backtrace warning that can happen on relays under various
4314 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4316 o Minor bugfixes (onion services):
4317 - The introduction circuit was being timed out too quickly while
4318 waiting for the rendezvous circuit to complete. Keep the intro
4319 circuit around longer instead of timing out and reopening new ones
4320 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
4321 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
4322 so it matches dir-spec.txt. Fixes bug 24262; bugfix
4324 - Silence a warning about failed v3 onion descriptor uploads that
4325 can happen naturally under certain edge cases. Fixes part of bug
4326 23662; bugfix on 0.3.2.1-alpha.
4328 o Minor bugfixes (tests):
4329 - Fix a memory leak in one of the bridge-distribution test cases.
4330 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
4331 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
4332 to correctly handle cases where a caller gives it an RSA key of
4333 under 160 bits. (This is not actually a bug in Tor itself, but
4334 rather in our fuzzing code.) Fixes bug 24247; bugfix on
4335 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
4338 - Add notes in man page regarding OS support for the various
4339 scheduler types. Attempt to use less jargon in the scheduler
4340 section. Closes ticket 24254.
4343 Changes in version 0.3.2.4-alpha - 2017-11-08
4344 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
4345 It fixes several stability and reliability bugs, especially including
4346 a major reliability issue that has been plaguing fast exit relays in
4349 o Major bugfixes (exit relays, DNS):
4350 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
4351 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
4352 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
4353 identifying and finding a workaround to this bug and to Moritz,
4354 Arthur Edelstein, and Roger for helping to track it down and
4357 o Major bugfixes (scheduler, channel):
4358 - Stop processing scheduled channels if they closed while flushing
4359 cells. This can happen if the write on the connection fails
4360 leading to the channel being closed while in the scheduler loop.
4361 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
4363 o Minor features (logging, scheduler):
4364 - Introduce a SCHED_BUG() function to log extra information about
4365 the scheduler state if we ever catch a bug in the scheduler.
4366 Closes ticket 23753.
4368 o Minor features (removed deprecations):
4369 - The ClientDNSRejectInternalAddresses flag can once again be set in
4370 non-testing Tor networks, so long as they do not use the default
4371 directory authorities. This change also removes the deprecation of
4372 this flag from 0.2.9.2-alpha. Closes ticket 21031.
4374 o Minor features (testing):
4375 - Our fuzzing tests now test the encrypted portions of v3 onion
4376 service descriptors. Implements more of 21509.
4378 o Minor bugfixes (directory client):
4379 - On failure to download directory information, delay retry attempts
4380 by a random amount based on the "decorrelated jitter" algorithm.
4381 Our previous delay algorithm tended to produce extra-long delays
4382 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
4384 o Minor bugfixes (IPv6, v3 single onion services):
4385 - Remove buggy code for IPv6-only v3 single onion services, and
4386 reject attempts to configure them. This release supports IPv4,
4387 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
4388 stack v3 single onion services. Fixes bug 23820; bugfix
4391 o Minor bugfixes (logging, relay):
4392 - Give only a protocol warning when the ed25519 key is not
4393 consistent between the descriptor and microdescriptor of a relay.
4394 This can happen, for instance, if the relay has been flagged
4395 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
4397 o Minor bugfixes (manpage, onion service):
4398 - Document that the HiddenServiceNumIntroductionPoints option is
4399 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
4400 bugfix on 0.3.2.1-alpha.
4402 o Minor bugfixes (memory leaks):
4403 - Fix a minor memory leak at exit in the KIST scheduler. This bug
4404 should have no user-visible impact. Fixes bug 23774; bugfix
4406 - Fix a memory leak when decrypting a badly formatted v3 onion
4407 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
4408 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
4410 o Minor bugfixes (onion services):
4411 - Cache some needed onion service client information instead of
4412 constantly computing it over and over again. Fixes bug 23623;
4413 bugfix on 0.3.2.1-alpha.
4414 - Properly retry HSv3 descriptor fetches when missing required
4415 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
4417 o Minor bugfixes (path selection):
4418 - When selecting relays by bandwidth, avoid a rounding error that
4419 could sometimes cause load to be imbalanced incorrectly.
4420 Previously, we would always round upwards; now, we round towards
4421 the nearest integer. This had the biggest effect when a relay's
4422 weight adjustments should have given it weight 0, but it got
4423 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4424 - When calculating the fraction of nodes that have descriptors, and
4425 all nodes in the network have zero bandwidths, count the number of
4426 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4427 - Actually log the total bandwidth in compute_weighted_bandwidths().
4428 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4430 o Minor bugfixes (relay, crash):
4431 - Avoid a crash when transitioning from client mode to bridge mode.
4432 Previously, we would launch the worker threads whenever our
4433 "public server" mode changed, but not when our "server" mode
4434 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
4436 o Minor bugfixes (testing):
4437 - Fix a spurious fuzzing-only use of an uninitialized value. Found
4438 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
4439 - Test that IPv6-only clients can use microdescriptors when running
4440 "make test-network-all". Requires chutney master 61c28b9 or later.
4441 Closes ticket 24109.
4444 Changes in version 0.3.2.3-alpha - 2017-10-27
4445 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
4446 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
4447 directory authority, Bastet.
4449 o Directory authority changes:
4450 - Add "Bastet" as a ninth directory authority to the default list.
4451 Closes ticket 23910.
4452 - The directory authority "Longclaw" has changed its IP address.
4453 Closes ticket 23592.
4455 o Minor features (bridge):
4456 - Bridge relays can now set the BridgeDistribution config option to
4457 add a "bridge-distribution-request" line to their bridge
4458 descriptor, which tells BridgeDB how they'd like their bridge
4459 address to be given out. (Note that as of Oct 2017, BridgeDB does
4460 not yet implement this feature.) As a side benefit, this feature
4461 provides a way to distinguish bridge descriptors from non-bridge
4462 descriptors. Implements tickets 18329.
4464 o Minor features (client, entry guards):
4465 - Improve log messages when missing descriptors for primary guards.
4466 Resolves ticket 23670.
4468 o Minor features (geoip):
4469 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4472 o Minor bugfixes (bridge):
4473 - Overwrite the bridge address earlier in the process of retrieving
4474 its descriptor, to make sure we reach it on the configured
4475 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
4477 o Minor bugfixes (documentation):
4478 - Document better how to read gcov, and what our gcov postprocessing
4479 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
4481 o Minor bugfixes (entry guards):
4482 - Tor now updates its guard state when it reads a consensus
4483 regardless of whether it's missing descriptors. That makes tor use
4484 its primary guards to fetch descriptors in some edge cases where
4485 it would previously have used fallback directories. Fixes bug
4486 23862; bugfix on 0.3.0.1-alpha.
4488 o Minor bugfixes (hidden service client):
4489 - When handling multiple SOCKS request for the same .onion address,
4490 only fetch the service descriptor once.
4491 - When a descriptor fetch fails with a non-recoverable error, close
4492 all pending SOCKS requests for that .onion. Fixes bug 23653;
4493 bugfix on 0.3.2.1-alpha.
4495 o Minor bugfixes (hidden service):
4496 - Always regenerate missing hidden service public key files. Prior
4497 to this, if the public key was deleted from disk, it wouldn't get
4498 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
4500 - Make sure that we have a usable ed25519 key when the intro point
4501 relay supports ed25519 link authentication. Fixes bug 24002;
4502 bugfix on 0.3.2.1-alpha.
4504 o Minor bugfixes (hidden service, v2):
4505 - When reloading configured hidden services, copy all information
4506 from the old service object. Previously, some data was omitted,
4507 causing delays in descriptor upload, and other bugs. Fixes bug
4508 23790; bugfix on 0.2.1.9-alpha.
4510 o Minor bugfixes (memory safety, defensive programming):
4511 - Clear the target address when node_get_prim_orport() returns
4512 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
4514 o Minor bugfixes (relay):
4515 - Avoid a BUG warning when receiving a dubious CREATE cell while an
4516 option transition is in progress. Fixes bug 23952; bugfix
4519 o Minor bugfixes (testing):
4520 - Adjust the GitLab CI configuration to more closely match that of
4521 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
4522 - Prevent scripts/test/coverage from attempting to move gcov output
4523 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
4524 - When running unit tests as root, skip a test that would fail
4525 because it expects a permissions error. This affects some
4526 continuous integration setups. Fixes bug 23758; bugfix
4528 - Stop unconditionally mirroring the tor repository in GitLab CI.
4529 This prevented developers from enabling GitLab CI on master. Fixes
4530 bug 23755; bugfix on 0.3.2.2-alpha.
4531 - Fix the hidden service v3 descriptor decoding fuzzing to use the
4532 latest decoding API correctly. Fixes bug 21509; bugfix
4535 o Minor bugfixes (warnings):
4536 - When we get an HTTP request on a SOCKS port, tell the user about
4537 the new HTTPTunnelPort option. Previously, we would give a "Tor is
4538 not an HTTP Proxy" message, which stopped being true when
4539 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
4543 Changes in version 0.2.5.15 - 2017-10-25
4544 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
4545 series. It also adds a new directory authority, Bastet.
4547 Note: the Tor 0.2.5 series will no longer be supported after 1 May
4548 2018. If you need a release with long-term support, please upgrade to
4549 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4551 o Directory authority changes:
4552 - Add "Bastet" as a ninth directory authority to the default list.
4553 Closes ticket 23910.
4554 - The directory authority "Longclaw" has changed its IP address.
4555 Closes ticket 23592.
4557 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
4558 - Avoid an assertion failure bug affecting our implementation of
4559 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
4560 handling of "0xx" differs from what we had expected. Fixes bug
4561 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
4563 o Minor features (geoip):
4564 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4567 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
4568 - Fix a memset() off the end of an array when packing cells. This
4569 bug should be harmless in practice, since the corrupted bytes are
4570 still in the same structure, and are always padding bytes,
4571 ignored, or immediately overwritten, depending on compiler
4572 behavior. Nevertheless, because the memset()'s purpose is to make
4573 sure that any other cell-handling bugs can't expose bytes to the
4574 network, we need to fix it. Fixes bug 22737; bugfix on
4575 0.2.4.11-alpha. Fixes CID 1401591.
4577 o Build features (backport from 0.3.1.5-alpha):
4578 - Tor's repository now includes a Travis Continuous Integration (CI)
4579 configuration file (.travis.yml). This is meant to help new
4580 developers and contributors who fork Tor to a Github repository be
4581 better able to test their changes, and understand what we expect
4582 to pass. To use this new build feature, you must fork Tor to your
4583 Github account, then go into the "Integrations" menu in the
4584 repository settings for your fork and enable Travis, then push
4585 your changes. Closes ticket 22636.
4588 Changes in version 0.2.8.16 - 2017-10-25
4589 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
4590 series, including a bugfix for a crash issue that had affected relays
4591 under memory pressure. It also adds a new directory authority, Bastet.
4593 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
4594 2018. If you need a release with long-term support, please stick with
4595 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4597 o Directory authority changes:
4598 - Add "Bastet" as a ninth directory authority to the default list.
4599 Closes ticket 23910.
4600 - The directory authority "Longclaw" has changed its IP address.
4601 Closes ticket 23592.
4603 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
4604 - Fix a timing-based assertion failure that could occur when the
4605 circuit out-of-memory handler freed a connection's output buffer.
4606 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
4608 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
4609 - Remove longclaw's IPv6 address, as it will soon change. Authority
4610 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
4611 3/8 directory authorities with IPv6 addresses, but there are also
4612 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
4614 o Minor features (geoip):
4615 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4619 Changes in version 0.2.9.13 - 2017-10-25
4620 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
4621 series, including a bugfix for a crash issue that had affected relays
4622 under memory pressure. It also adds a new directory authority, Bastet.
4624 o Directory authority changes:
4625 - Add "Bastet" as a ninth directory authority to the default list.
4626 Closes ticket 23910.
4627 - The directory authority "Longclaw" has changed its IP address.
4628 Closes ticket 23592.
4630 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
4631 - Fix a timing-based assertion failure that could occur when the
4632 circuit out-of-memory handler freed a connection's output buffer.
4633 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
4635 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
4636 - Remove longclaw's IPv6 address, as it will soon change. Authority
4637 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
4638 3/8 directory authorities with IPv6 addresses, but there are also
4639 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
4641 o Minor features (geoip):
4642 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4645 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
4646 - When a directory authority rejects a descriptor or extrainfo with
4647 a given digest, mark that digest as undownloadable, so that we do
4648 not attempt to download it again over and over. We previously
4649 tried to avoid downloading such descriptors by other means, but we
4650 didn't notice if we accidentally downloaded one anyway. This
4651 behavior became problematic in 0.2.7.2-alpha, when authorities
4652 began pinning Ed25519 keys. Fixes bug 22349; bugfix
4655 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
4656 - Clear the address when node_get_prim_orport() returns early.
4657 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
4659 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
4660 - When running as a Windows service, set the ID of the main thread
4661 correctly. Failure to do so made us fail to send log messages to
4662 the controller in 0.2.1.16-rc, slowed down controller event
4663 delivery in 0.2.7.3-rc and later, and crash with an assertion
4664 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
4665 Patch and diagnosis from "Vort".
4668 Changes in version 0.3.0.12 - 2017-10-25
4669 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
4670 series, including a bugfix for a crash issue that had affected relays
4671 under memory pressure. It also adds a new directory authority, Bastet.
4673 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
4674 2018. If you need a release with long-term support, please stick with
4675 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
4677 o Directory authority changes:
4678 - Add "Bastet" as a ninth directory authority to the default list.
4679 Closes ticket 23910.
4680 - The directory authority "Longclaw" has changed its IP address.
4681 Closes ticket 23592.
4683 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
4684 - Fix a timing-based assertion failure that could occur when the
4685 circuit out-of-memory handler freed a connection's output buffer.
4686 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
4688 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
4689 - Remove longclaw's IPv6 address, as it will soon change. Authority
4690 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
4691 3/8 directory authorities with IPv6 addresses, but there are also
4692 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
4694 o Minor features (geoip):
4695 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4698 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
4699 - When a directory authority rejects a descriptor or extrainfo with
4700 a given digest, mark that digest as undownloadable, so that we do
4701 not attempt to download it again over and over. We previously
4702 tried to avoid downloading such descriptors by other means, but we
4703 didn't notice if we accidentally downloaded one anyway. This
4704 behavior became problematic in 0.2.7.2-alpha, when authorities
4705 began pinning Ed25519 keys. Fixes bug 22349; bugfix
4708 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
4709 - Avoid a possible double close of a circuit by the intro point on
4710 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
4711 bugfix on 0.3.0.1-alpha.
4713 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
4714 - Clear the address when node_get_prim_orport() returns early.
4715 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
4717 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
4718 - When running as a Windows service, set the ID of the main thread
4719 correctly. Failure to do so made us fail to send log messages to
4720 the controller in 0.2.1.16-rc, slowed down controller event
4721 delivery in 0.2.7.3-rc and later, and crash with an assertion
4722 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
4723 Patch and diagnosis from "Vort".
4726 Changes in version 0.3.1.8 - 2017-10-25
4727 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
4728 It includes several bugfixes, including a bugfix for a crash issue
4729 that had affected relays under memory pressure. It also adds
4730 a new directory authority, Bastet.
4732 o Directory authority changes:
4733 - Add "Bastet" as a ninth directory authority to the default list.
4734 Closes ticket 23910.
4735 - The directory authority "Longclaw" has changed its IP address.
4736 Closes ticket 23592.
4738 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
4739 - Fix a timing-based assertion failure that could occur when the
4740 circuit out-of-memory handler freed a connection's output buffer.
4741 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
4743 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
4744 - Remove longclaw's IPv6 address, as it will soon change. Authority
4745 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
4746 3/8 directory authorities with IPv6 addresses, but there are also
4747 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
4749 o Minor features (geoip):
4750 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
4753 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
4754 - Fix a compilation warning when building with zstd support on
4755 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
4756 and fixed by Andreas Stieger.
4758 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
4759 - Handle a pathological case when decompressing Zstandard data when
4760 the output buffer size is zero. Fixes bug 23551; bugfix
4763 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
4764 - Remove the length limit on HTTP status lines that authorities can
4765 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
4767 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
4768 - Avoid a possible double close of a circuit by the intro point on
4769 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
4770 bugfix on 0.3.0.1-alpha.
4772 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
4773 - Clear the address when node_get_prim_orport() returns early.
4774 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
4776 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
4777 - Fix additional channelpadding unit test failures by using mocked
4778 time instead of actual time for all tests. Fixes bug 23608; bugfix
4782 Changes in version 0.3.2.2-alpha - 2017-09-29
4783 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
4784 release fixes several minor bugs in the new scheduler and next-
4785 generation onion services; both features were newly added in the 0.3.2
4786 series. Other fixes in this alpha include several fixes for non-fatal
4787 tracebacks which would appear in logs.
4789 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
4790 alpha does not contain any substantial new features. Minor features
4791 include better testing and logging.
4793 The following comprises the complete list of changes included
4796 o Major bugfixes (relay, crash, assertion failure):
4797 - Fix a timing-based assertion failure that could occur when the
4798 circuit out-of-memory handler freed a connection's output buffer.
4799 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
4801 o Major bugfixes (scheduler):
4802 - If a channel is put into the scheduler's pending list, then it
4803 starts closing, and then if the scheduler runs before it finishes
4804 closing, the scheduler will get stuck trying to flush its cells
4805 while the lower layers refuse to cooperate. Fix that race
4806 condition by giving the scheduler an escape method. Fixes bug
4807 23676; bugfix on 0.3.2.1-alpha.
4809 o Minor features (build, compilation):
4810 - The "check-changes" feature is now part of the "make check" tests;
4811 we'll use it to try to prevent misformed changes files from
4812 accumulating. Closes ticket 23564.
4813 - Tor builds should now fail if there are any mismatches between the
4814 C type representing a configuration variable and the C type the
4815 data-driven parser uses to store a value there. Previously, we
4816 needed to check these by hand, which sometimes led to mistakes.
4817 Closes ticket 23643.
4819 o Minor features (directory authorities):
4820 - Remove longclaw's IPv6 address, as it will soon change. Authority
4821 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
4822 3/8 directory authorities with IPv6 addresses, but there are also
4823 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
4825 o Minor features (hidden service, circuit, logging):
4826 - Improve logging of many callsite in the circuit subsystem to print
4827 the circuit identifier(s).
4828 - Log when we cleanup an intro point from a service so we know when
4829 and for what reason it happened. Closes ticket 23604.
4831 o Minor features (logging):
4832 - Log more circuit information whenever we are about to try to
4833 package a relay cell on a circuit with a nonexistent n_chan.
4834 Attempt to diagnose ticket 8185.
4835 - Improve info-level log identification of particular circuits, to
4836 help with debugging. Closes ticket 23645.
4838 o Minor features (relay):
4839 - When choosing which circuits can be expired as unused, consider
4840 circuits from clients even if those clients used regular CREATE
4841 cells to make them; and do not consider circuits from relays even
4842 if they were made with CREATE_FAST. Part of ticket 22805.
4844 o Minor features (robustness):
4845 - Change several fatal assertions when flushing buffers into non-
4846 fatal assertions, to prevent any recurrence of 23690.
4848 o Minor features (spec conformance, bridge, diagnostic):
4849 - When handling the USERADDR command on an ExtOrPort, warn when the
4850 transports provides a USERADDR with no port. In a future version,
4851 USERADDR commands of this format may be rejected. Detects problems
4852 related to ticket 23080.
4854 o Minor features (testing):
4855 - Add a unit test to make sure that our own generated platform
4856 string will be accepted by directory authorities. Closes
4859 o Minor bugfixes (bootstrapping):
4860 - When warning about state file clock skew, report the correct
4861 direction for the detected skew. Fixes bug 23606; bugfix
4863 - Avoid an assertion failure when logging a state file clock skew
4864 very early in bootstrapping. Fixes bug 23607; bugfix
4867 o Minor bugfixes (build, compilation):
4868 - Fix a compilation warning when building with zstd support on
4869 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
4870 and fixed by Andreas Stieger.
4871 - When searching for OpenSSL, don't accept any OpenSSL library that
4872 lacks TLSv1_1_method(): Tor doesn't build with those versions.
4873 Additionally, look in /usr/local/opt/openssl, if it's present.
4874 These changes together repair the default build on OSX systems
4875 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
4877 o Minor bugfixes (compression):
4878 - Handle a pathological case when decompressing Zstandard data when
4879 the output buffer size is zero. Fixes bug 23551; bugfix
4882 o Minor bugfixes (documentation):
4883 - Fix manpage to not refer to the obsolete (and misspelled)
4884 UseEntryGuardsAsDirectoryGuards parameter in the description of
4885 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
4887 o Minor bugfixes (hidden service v3):
4888 - Don't log an assertion failure when we can't find the right
4889 information to extend to an introduction point. In rare cases,
4890 this could happen, causing a warning, even though tor would
4891 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
4892 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
4893 much bigger so the rendezvous point can't distinguish which hidden
4894 service protocol is being used. Fixes bug 23420; bugfix
4897 o Minor bugfixes (hidden service, relay):
4898 - Avoid a possible double close of a circuit by the intro point on
4899 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
4900 bugfix on 0.3.0.1-alpha.
4902 o Minor bugfixes (logging, relay shutdown, annoyance):
4903 - When a circuit is marked for close, do not attempt to package any
4904 cells for channels on that circuit. Previously, we would detect
4905 this condition lower in the call stack, when we noticed that the
4906 circuit had no attached channel, and log an annoying message.
4907 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
4909 o Minor bugfixes (scheduler):
4910 - When switching schedulers due to a consensus change, we didn't
4911 give the new scheduler a chance to react to the consensus. Fix
4912 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
4913 - Make the KISTSchedRunInterval option a non negative value. With
4914 this, the way to disable KIST through the consensus is to set it
4915 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
4916 - Only notice log the selected scheduler when we switch scheduler
4917 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
4918 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
4919 by a different tv_usec data type. Fixes bug 23575; bugfix
4921 - Make a hard exit if tor is unable to pick a scheduler which can
4922 happen if the user specifies a scheduler type that is not
4923 supported and not other types in Schedulers. Fixes bug 23581;
4924 bugfix on 0.3.2.1-alpha.
4925 - Properly initialize the scheduler last run time counter so it is
4926 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
4928 o Minor bugfixes (testing):
4929 - Capture and detect several "Result does not fit" warnings in unit
4930 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
4932 - Fix additional channelpadding unit test failures by using mocked
4933 time instead of actual time for all tests. Fixes bug 23608; bugfix
4935 - The removal of some old scheduler options caused some tests to
4936 fail on BSD systems. Assume current behavior is correct and make
4937 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
4939 o Code simplification and refactoring:
4940 - Remove various ways of testing circuits and connections for
4941 "clientness"; instead, favor channel_is_client(). Part of
4944 o Deprecated features:
4945 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
4946 now deprecated; they do not apply to relays, and they have had no
4947 effect on clients since 0.2.8.x. Closes ticket 19704.
4950 - HiddenServiceVersion man page entry wasn't mentioning the now
4951 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
4952 - Clarify that the Address option is entirely about setting an
4953 advertised IPv4 address. Closes ticket 18891.
4954 - Clarify the manpage's use of the term "address" to clarify what
4955 kind of address is intended. Closes ticket 21405.
4956 - Document that onion service subdomains are allowed, and ignored.
4957 Closes ticket 18736.
4960 Changes in version 0.3.2.1-alpha - 2017-09-18
4961 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
4962 includes support for our next-generation ("v3") onion service
4963 protocol, and adds a new circuit scheduler for more responsive
4964 forwarding decisions from relays. There are also numerous other small
4965 features and bugfixes here.
4967 Below are the changes since Tor 0.3.1.7.
4969 o Major feature (scheduler, channel):
4970 - Tor now uses new schedulers to decide which circuits should
4971 deliver cells first, in order to improve congestion at relays. The
4972 first type is called "KIST" ("Kernel Informed Socket Transport"),
4973 and is only available on Linux-like systems: it uses feedback from
4974 the kernel to prevent the kernel's TCP buffers from growing too
4975 full. The second new scheduler type is called "KISTLite": it
4976 behaves the same as KIST, but runs on systems without kernel
4977 support for inspecting TCP implementation details. The old
4978 scheduler is still available, under the name "Vanilla". To change
4979 the default scheduler preference order, use the new "Schedulers"
4980 option. (The default preference order is "KIST,KISTLite,Vanilla".)
4982 Matt Traudt implemented KIST, based on research by Rob Jansen,
4983 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
4984 more information, see the design paper at
4985 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
4986 followup implementation paper at https://arxiv.org/abs/1709.01044.
4987 Closes ticket 12541.
4989 o Major features (next-generation onion services):
4990 - Tor now supports the next-generation onion services protocol for
4991 clients and services! As part of this release, the core of
4992 proposal 224 has been implemented and is available for
4993 experimentation and testing by our users. This newer version of
4994 onion services ("v3") features many improvements over the legacy
4997 a) Better crypto (replaced SHA1/DH/RSA1024
4998 with SHA3/ed25519/curve25519)
5000 b) Improved directory protocol, leaking much less information to
5003 c) Improved directory protocol, with smaller surface for
5006 d) Better onion address security against impersonation.
5008 e) More extensible introduction/rendezvous protocol.
5010 f) A cleaner and more modular codebase.
5012 You can identify a next-generation onion address by its length:
5013 they are 56 characters long, as in
5014 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
5016 In the future, we will release more options and features for v3
5017 onion services, but we first need a testing period, so that the
5018 current codebase matures and becomes more robust. Planned features
5019 include: offline keys, advanced client authorization, improved
5020 guard algorithms, and statistics. For full details, see
5023 Legacy ("v2") onion services will still work for the foreseeable
5024 future, and will remain the default until this new codebase gets
5025 tested and hardened. Service operators who want to experiment with
5026 the new system can use the 'HiddenServiceVersion 3' torrc
5027 directive along with the regular onion service configuration
5028 options. We will publish a blog post about this new feature
5031 o Major bugfixes (usability, control port):
5032 - Report trusted clock skew indications as bootstrap errors, so
5033 controllers can more easily alert users when their clocks are
5034 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
5036 o Minor features (bug detection):
5037 - Log a warning message with a stack trace for any attempt to call
5038 get_options() during option validation. This pattern has caused
5039 subtle bugs in the past. Closes ticket 22281.
5041 o Minor features (client):
5042 - You can now use Tor as a tunneled HTTP proxy: use the new
5043 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
5044 requests. Closes ticket 22407.
5045 - Add an extra check to make sure that we always use the newer guard
5046 selection code for picking our guards. Closes ticket 22779.
5047 - When downloading (micro)descriptors, don't split the list into
5048 multiple requests unless we want at least 32 descriptors.
5049 Previously, we split at 4, not 32, which led to significant
5050 overhead in HTTP request size and degradation in compression
5051 performance. Closes ticket 23220.
5053 o Minor features (command line):
5054 - Add a new commandline option, --key-expiration, which prints when
5055 the current signing key is going to expire. Implements ticket
5056 17639; patch by Isis Lovecruft.
5058 o Minor features (control port):
5059 - If an application tries to use the control port as an HTTP proxy,
5060 respond with a meaningful "This is the Tor control port" message,
5061 and log the event. Closes ticket 1667. Patch from Ravi
5063 - Provide better error message for GETINFO desc/(id|name) when not
5064 fetching router descriptors. Closes ticket 5847. Patch by
5066 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
5067 whether Tor will try to download router descriptors and
5068 microdescriptors respectively. Closes ticket 22684.
5069 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
5070 so controllers can tell whether the geoip databases are loaded.
5071 Closes ticket 23237.
5072 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
5073 events. Closes ticket 19254. Patch by "DonnchaC".
5075 o Minor features (development support):
5076 - Developers can now generate a call-graph for Tor using the
5077 "calltool" python program, which post-processes object dumps. It
5078 should work okay on many Linux and OSX platforms, and might work
5079 elsewhere too. To run it, install calltool from
5080 https://gitweb.torproject.org/user/nickm/calltool.git and run
5081 "make callgraph". Closes ticket 19307.
5083 o Minor features (ed25519):
5084 - Add validation function to checks for torsion components in
5085 ed25519 public keys, used by prop224 client-side code. Closes
5086 ticket 22006. Math help by Ian Goldberg.
5088 o Minor features (exit relay, DNS):
5089 - Improve the clarity and safety of the log message from evdns when
5090 receiving an apparently spoofed DNS reply. Closes ticket 3056.
5092 o Minor features (integration, hardening):
5093 - Add a new NoExec option to prevent Tor from running other
5094 programs. When this option is set to 1, Tor will never try to run
5095 another program, regardless of the settings of
5096 PortForwardingHelper, ClientTransportPlugin, or
5097 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
5098 without restarting Tor. Closes ticket 22976.
5100 o Minor features (logging):
5101 - Improve the warning message for specifying a relay by nickname.
5102 The previous message implied that nickname registration was still
5103 part of the Tor network design, which it isn't. Closes
5105 - If the sandbox filter fails to load, suggest to the user that
5106 their kernel might not support seccomp2. Closes ticket 23090.
5108 o Minor features (portability):
5109 - Check at configure time whether uint8_t is the same type as
5110 unsigned char. Lots of existing code already makes this
5111 assumption, and there could be strict aliasing issues if the
5112 assumption is violated. Closes ticket 22410.
5114 o Minor features (relay, configuration):
5115 - Reject attempts to use relative file paths when RunAsDaemon is
5116 set. Previously, Tor would accept these, but the directory-
5117 changing step of RunAsDaemon would give strange and/or confusing
5118 results. Closes ticket 22731.
5120 o Minor features (startup, safety):
5121 - When configured to write a PID file, Tor now exits if it is unable
5122 to do so. Previously, it would warn and continue. Closes
5125 o Minor features (static analysis):
5126 - The BUG() macro has been changed slightly so that Coverity no
5127 longer complains about dead code if the bug is impossible. Closes
5130 o Minor features (testing):
5131 - The default chutney network tests now include tests for the v3
5132 hidden service design. Make sure you have the latest version of
5133 chutney if you want to run these. Closes ticket 22437.
5134 - Add a unit test to verify that we can parse a hardcoded v2 hidden
5135 service descriptor. Closes ticket 15554.
5137 o Minor bugfixes (certificate handling):
5138 - Fix a time handling bug in Tor certificates set to expire after
5139 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
5140 Coverity as CID 1415728.
5142 o Minor bugfixes (client, usability):
5143 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
5144 SOCKS4a requests that contain IP address strings, even when
5145 SafeSocks in enabled, as this prevents user from connecting to
5146 known IP addresses without relying on DNS for resolving. SafeSocks
5147 still rejects SOCKS connections that connect to IP addresses when
5148 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
5149 bugfix on Tor 0.2.6.2-alpha.
5151 o Minor bugfixes (code correctness):
5152 - Call htons() in extend_cell_format() for encoding a 16-bit value.
5153 Previously we used ntohs(), which happens to behave the same on
5154 all the platforms we support, but which isn't really correct.
5155 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
5156 - For defense-in-depth, make the controller's write_escaped_data()
5157 function robust to extremely long inputs. Fixes bug 19281; bugfix
5158 on 0.1.1.1-alpha. Reported by Guido Vranken.
5160 o Minor bugfixes (compilation):
5161 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
5162 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5164 o Minor bugfixes (consensus expiry):
5165 - Check for adequate directory information correctly. Previously, Tor
5166 would reconsider whether it had sufficient directory information
5167 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
5169 o Minor bugfixes (directory protocol):
5170 - Directory servers now include a "Date:" http header for response
5171 codes other than 200. Clients starting with a skewed clock and a
5172 recent consensus were getting "304 Not modified" responses from
5173 directory authorities, so without the Date header, the client
5174 would never hear about a wrong clock. Fixes bug 23499; bugfix
5176 - Make clients wait for 6 seconds before trying to download a
5177 consensus from an authority. Fixes bug 17750; bugfix
5180 o Minor bugfixes (DoS-resistance):
5181 - If future code asks if there are any running bridges, without
5182 checking if bridges are enabled, log a BUG warning rather than
5183 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
5185 o Minor bugfixes (format strictness):
5186 - Restrict several data formats to decimal. Previously, the
5187 BuildTimeHistogram entries in the state file, the "bw=" entries in
5188 the bandwidth authority file, and the process IDs passed to the
5189 __OwningControllerProcess option could all be specified in hex or
5190 octal as well as in decimal. This was not an intentional feature.
5191 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
5194 o Minor bugfixes (heartbeat):
5195 - If we fail to write a heartbeat message, schedule a retry for the
5196 minimum heartbeat interval number of seconds in the future. Fixes
5197 bug 19476; bugfix on 0.2.3.1-alpha.
5199 o Minor bugfixes (linux seccomp2 sandbox, logging):
5200 - Fix some messages on unexpected errors from the seccomp2 library.
5201 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
5203 o Minor bugfixes (logging):
5204 - Remove duplicate log messages regarding opening non-local
5205 SocksPorts upon parsing config and opening listeners at startup.
5206 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
5207 - Use a more comprehensible log message when telling the user
5208 they've excluded every running exit node. Fixes bug 7890; bugfix
5210 - When logging the number of descriptors we intend to download per
5211 directory request, do not log a number higher than then the number
5212 of descriptors we're fetching in total. Fixes bug 19648; bugfix
5214 - When warning about a directory owned by the wrong user, log the
5215 actual name of the user owning the directory. Previously, we'd log
5216 the name of the process owner twice. Fixes bug 23487; bugfix
5218 - The tor specification says hop counts are 1-based, so fix two log
5219 messages that mistakenly logged 0-based hop counts. Fixes bug
5220 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
5221 Credit to Xiaofan Li for reporting this issue.
5223 o Minor bugfixes (portability):
5224 - Stop using the PATH_MAX variable, which is not defined on GNU
5225 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
5227 o Minor bugfixes (relay):
5228 - When uploading our descriptor for the first time after startup,
5229 report the reason for uploading as "Tor just started" rather than
5230 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
5231 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5232 relays, to prevent spurious address resolutions and descriptor
5233 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5234 bugfix on in 0.2.8.1-alpha.
5236 o Minor bugfixes (tests):
5237 - Fix a broken unit test for the OutboundAddress option: the parsing
5238 function was never returning an error on failure. Fixes bug 23366;
5239 bugfix on 0.3.0.3-alpha.
5240 - Fix a signed-integer overflow in the unit tests for
5241 dir/download_status_random_backoff, which was untriggered until we
5242 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
5244 o Minor bugfixes (usability, control port):
5245 - Stop making an unnecessary routerlist check in NETINFO clock skew
5246 detection; this was preventing clients from reporting NETINFO clock
5247 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
5249 o Code simplification and refactoring:
5250 - Extract the code for handling newly-open channels into a separate
5251 function from the general code to handle channel state
5252 transitions. This change simplifies our callgraph, reducing the
5253 size of the largest strongly connected component by roughly a
5254 factor of two. Closes ticket 22608.
5255 - Remove dead code for largely unused statistics on the number of
5256 times we've attempted various public key operations. Fixes bug
5257 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
5258 - Remove several now-obsolete functions for asking about old
5259 variants directory authority status. Closes ticket 22311; patch
5261 - Remove some of the code that once supported "Named" and "Unnamed"
5262 routers. Authorities no longer vote for these flags. Closes
5264 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
5265 and old hidden services, to indicate that they aren't suitable for
5266 new protocols or formats. Closes ticket 23026.
5267 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
5268 22521. Patch from Neel Chauhan.
5269 - Split the enormous circuit_send_next_onion_skin() function into
5270 multiple subfunctions. Closes ticket 22804.
5271 - Split the portions of the buffer.c module that handle particular
5272 protocols into separate modules. Part of ticket 23149.
5273 - Use our test macros more consistently, to produce more useful
5274 error messages when our unit tests fail. Add coccinelle patches to
5275 allow us to re-check for test macro uses. Closes ticket 22497.
5277 o Deprecated features:
5278 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
5279 only applies to direct unencrypted HTTP connections to your
5280 directory server, which your Tor probably isn't using. Closes
5284 - Clarify in the manual that "Sandbox 1" is only supported on Linux
5285 kernels. Closes ticket 22677.
5286 - Document all values of PublishServerDescriptor in the manpage.
5287 Closes ticket 15645.
5288 - Improve the documentation for the directory port part of the
5289 DirAuthority line. Closes ticket 20152.
5290 - Restore documentation for the authorities' "approved-routers"
5291 file. Closes ticket 21148.
5294 - The AllowDotExit option has been removed as unsafe. It has been
5295 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
5296 - The ClientDNSRejectInternalAddresses flag can no longer be set on
5297 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
5298 Closes ticket 21031.
5299 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
5300 nobody was using it any longer. Closes ticket 22377.
5303 Changes in version 0.2.8.15 - 2017-09-18
5304 Tor 0.2.8.15 backports a collection of bugfixes from later
5307 Most significantly, it includes a fix for TROVE-2017-008, a
5308 security bug that affects hidden services running with the
5309 SafeLogging option disabled. For more information, see
5310 https://trac.torproject.org/projects/tor/ticket/23490
5312 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
5313 2018. We suggest that you upgrade to the latest stable release if
5314 possible. If you can't, we recommend that you upgrade at least to
5315 0.2.9, which will be supported until 2020.
5317 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
5318 - Avoid an assertion failure bug affecting our implementation of
5319 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5320 handling of "0xx" differs from what we had expected. Fixes bug
5321 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5324 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5327 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
5328 - Backport a fix for an "unused variable" warning that appeared
5329 in some versions of mingw. Fixes bug 22838; bugfix on
5332 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
5333 - Fix a memset() off the end of an array when packing cells. This
5334 bug should be harmless in practice, since the corrupted bytes are
5335 still in the same structure, and are always padding bytes,
5336 ignored, or immediately overwritten, depending on compiler
5337 behavior. Nevertheless, because the memset()'s purpose is to make
5338 sure that any other cell-handling bugs can't expose bytes to the
5339 network, we need to fix it. Fixes bug 22737; bugfix on
5340 0.2.4.11-alpha. Fixes CID 1401591.
5342 o Build features (backport from 0.3.1.5-alpha):
5343 - Tor's repository now includes a Travis Continuous Integration (CI)
5344 configuration file (.travis.yml). This is meant to help new
5345 developers and contributors who fork Tor to a Github repository be
5346 better able to test their changes, and understand what we expect
5347 to pass. To use this new build feature, you must fork Tor to your
5348 Github account, then go into the "Integrations" menu in the
5349 repository settings for your fork and enable Travis, then push
5350 your changes. Closes ticket 22636.
5353 Changes in version 0.2.9.12 - 2017-09-18
5354 Tor 0.2.9.12 backports a collection of bugfixes from later
5357 Most significantly, it includes a fix for TROVE-2017-008, a
5358 security bug that affects hidden services running with the
5359 SafeLogging option disabled. For more information, see
5360 https://trac.torproject.org/projects/tor/ticket/23490
5362 o Major features (security, backport from 0.3.0.2-alpha):
5363 - Change the algorithm used to decide DNS TTLs on client and server
5364 side, to better resist DNS-based correlation attacks like the
5365 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
5366 Feamster. Now relays only return one of two possible DNS TTL
5367 values, and clients are willing to believe DNS TTL values up to 3
5368 hours long. Closes ticket 19769.
5370 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
5371 - Fix a rare crash when sending a begin cell on a circuit whose
5372 linked directory connection had already been closed. Fixes bug
5373 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
5375 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
5376 - Fix a bug that prevented exit nodes from caching DNS records for
5377 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
5379 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
5380 - Fix a typo that had prevented TPROXY-based transparent proxying
5381 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
5382 Patch from "d4fq0fQAgoJ".
5384 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
5385 - Avoid an assertion failure bug affecting our implementation of
5386 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5387 handling of "0xx" differs from what we had expected. Fixes bug
5388 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5390 o Minor features (code style, backport from 0.3.1.3-alpha):
5391 - Add "Falls through" comments to our codebase, in order to silence
5392 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
5393 Stieger. Closes ticket 22446.
5395 o Minor features (geoip):
5396 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5399 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
5400 - Roll over monthly accounting at the configured hour and minute,
5401 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
5402 Found by Andrey Karpov with PVS-Studio.
5404 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
5405 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
5406 bugfix on 0.2.8.1-alpha.
5407 - Fix warnings when building with libscrypt and openssl scrypt support
5408 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
5409 - When building with certain versions the mingw C header files, avoid
5410 float-conversion warnings when calling the C functions isfinite(),
5411 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
5413 o Minor bugfixes (compilation, backport from 0.3.1.7):
5414 - Avoid compiler warnings in the unit tests for running tor_sscanf()
5415 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
5417 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
5418 - Backport a fix for an "unused variable" warning that appeared
5419 in some versions of mingw. Fixes bug 22838; bugfix on
5422 o Minor bugfixes (controller, backport from 0.3.1.7):
5423 - Do not crash when receiving a HSPOST command with an empty body.
5424 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
5425 - Do not crash when receiving a POSTDESCRIPTOR command with an
5426 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
5428 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
5429 - Avoid Coverity build warnings related to our BUG() macro. By
5430 default, Coverity treats BUG() as the Linux kernel does: an
5431 instant abort(). We need to override that so our BUG() macro
5432 doesn't prevent Coverity from analyzing functions that use it.
5433 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
5435 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
5436 - Fix a memset() off the end of an array when packing cells. This
5437 bug should be harmless in practice, since the corrupted bytes are
5438 still in the same structure, and are always padding bytes,
5439 ignored, or immediately overwritten, depending on compiler
5440 behavior. Nevertheless, because the memset()'s purpose is to make
5441 sure that any other cell-handling bugs can't expose bytes to the
5442 network, we need to fix it. Fixes bug 22737; bugfix on
5443 0.2.4.11-alpha. Fixes CID 1401591.
5445 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
5446 - When setting the maximum number of connections allowed by the OS,
5447 always allow some extra file descriptors for other files. Fixes
5448 bug 22797; bugfix on 0.2.0.10-alpha.
5450 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
5451 - Avoid a sandbox failure when trying to re-bind to a socket and
5452 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
5454 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
5455 - Permit the fchmod system call, to avoid crashing on startup when
5456 starting with the seccomp2 sandbox and an unexpected set of
5457 permissions on the data directory or its contents. Fixes bug
5458 22516; bugfix on 0.2.5.4-alpha.
5460 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
5461 - Avoid a double-marked-circuit warning that could happen when we
5462 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
5465 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
5466 - Reject version numbers with non-numeric prefixes (such as +, -, or
5467 whitespace). Disallowing whitespace prevents differential version
5468 parsing between POSIX-based and Windows platforms. Fixes bug 21507
5469 and part of 21508; bugfix on 0.0.8pre1.
5471 o Build features (backport from 0.3.1.5-alpha):
5472 - Tor's repository now includes a Travis Continuous Integration (CI)
5473 configuration file (.travis.yml). This is meant to help new
5474 developers and contributors who fork Tor to a Github repository be
5475 better able to test their changes, and understand what we expect
5476 to pass. To use this new build feature, you must fork Tor to your
5477 Github account, then go into the "Integrations" menu in the
5478 repository settings for your fork and enable Travis, then push
5479 your changes. Closes ticket 22636.
5482 Changes in version 0.3.0.11 - 2017-09-18
5483 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
5486 Most significantly, it includes a fix for TROVE-2017-008, a
5487 security bug that affects hidden services running with the
5488 SafeLogging option disabled. For more information, see
5489 https://trac.torproject.org/projects/tor/ticket/23490
5491 o Minor features (code style, backport from 0.3.1.7):
5492 - Add "Falls through" comments to our codebase, in order to silence
5493 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
5494 Stieger. Closes ticket 22446.
5497 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5500 o Minor bugfixes (compilation, backport from 0.3.1.7):
5501 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
5502 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
5504 o Minor bugfixes (controller, backport from 0.3.1.7):
5505 - Do not crash when receiving a HSPOST command with an empty body.
5506 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
5507 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
5508 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
5510 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
5511 - When setting the maximum number of connections allowed by the OS,
5512 always allow some extra file descriptors for other files. Fixes
5513 bug 22797; bugfix on 0.2.0.10-alpha.
5515 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
5516 - Remove a forgotten debugging message when an introduction point
5517 successfully establishes a hidden service prop224 circuit with
5519 - Change three other log_warn() for an introduction point to
5520 protocol warnings, because they can be failure from the network
5521 and are not relevant to the operator. Fixes bug 23078; bugfix on
5522 0.3.0.1-alpha and 0.3.0.2-alpha.
5525 Changes in version 0.3.1.7 - 2017-09-18
5526 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
5528 With the 0.3.1 series, Tor now serves and downloads directory
5529 information in more compact formats, to save on bandwidth overhead. It
5530 also contains a new padding system to resist netflow-based traffic
5531 analysis, and experimental support for building parts of Tor in Rust
5532 (though no parts of Tor are in Rust yet). There are also numerous
5533 small features, bugfixes on earlier release series, and groundwork for
5534 the hidden services revamp of 0.3.2.
5536 This release also includes a fix for TROVE-2017-008, a security bug
5537 that affects hidden services running with the SafeLogging option
5538 disabled. For more information, see
5539 https://trac.torproject.org/projects/tor/ticket/23490
5541 Per our stable release policy, we plan to support each stable release
5542 series for at least the next nine months, or for three months after
5543 the first stable release of the next series: whichever is longer. If
5544 you need a release with long-term support, we recommend that you stay
5545 with the 0.2.9 series.
5547 Below is a list of the changes since 0.3.1.6-rc. For a list of all
5548 changes since 0.3.0, see the ReleaseNotes file.
5550 o Major bugfixes (security, hidden services, loggging):
5551 - Fix a bug where we could log uninitialized stack when a certain
5552 hidden service error occurred while SafeLogging was disabled.
5553 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
5554 TROVE-2017-008 and CVE-2017-0380.
5556 o Minor features (defensive programming):
5557 - Create a pair of consensus parameters, nf_pad_tor2web and
5558 nf_pad_single_onion, to disable netflow padding in the consensus
5559 for non-anonymous connections in case the overhead is high. Closes
5562 o Minor features (diagnostic):
5563 - Add a stack trace to the bug warnings that can be logged when
5564 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
5565 attempt for bug 23105.
5567 o Minor features (geoip):
5568 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5571 o Minor bugfixes (compilation):
5572 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
5573 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
5575 o Minor bugfixes (controller):
5576 - Do not crash when receiving a HSPOST command with an empty body.
5577 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
5578 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
5579 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
5581 o Minor bugfixes (relay):
5582 - Inform the geoip and rephist modules about all requests, even on
5583 relays that are only fetching microdescriptors. Fixes a bug
5584 related to 21585; bugfix on 0.3.0.1-alpha.
5586 o Minor bugfixes (unit tests):
5587 - Fix a channelpadding unit test failure on slow systems by using
5588 mocked time instead of actual time. Fixes bug 23077; bugfix
5592 Changes in version 0.3.1.6-rc - 2017-09-05
5593 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
5594 release series, including a bug that produced weird behavior on
5595 Windows directory caches.
5597 This is the first release candidate in the Tor 0.3.1 series. If we
5598 find no new bugs or regressions here, the first stable 0.3.1 release
5599 will be nearly identical to it.
5601 o Major bugfixes (windows, directory cache):
5602 - On Windows, do not try to delete cached consensus documents and
5603 diffs before they are unmapped from memory--Windows won't allow
5604 that. Instead, allow the consensus cache directory to grow larger,
5605 to hold files that might need to stay around longer. Fixes bug
5606 22752; bugfix on 0.3.1.1-alpha.
5608 o Minor features (directory authority):
5609 - Improve the message that authorities report to relays that present
5610 RSA/Ed25519 keypairs that conflict with previously pinned keys.
5611 Closes ticket 22348.
5613 o Minor features (geoip):
5614 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
5617 o Minor features (testing):
5618 - Add more tests for compression backend initialization. Closes
5621 o Minor bugfixes (directory cache):
5622 - Fix a memory leak when recovering space in the consensus cache.
5623 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
5625 o Minor bugfixes (hidden service):
5626 - Increase the number of circuits that a service is allowed to
5627 open over a specific period of time. The value was lower than it
5628 should be (8 vs 12) in the normal case of 3 introduction points.
5629 Fixes bug 22159; bugfix on 0.3.0.5-rc.
5630 - Fix a BUG warning during HSv3 descriptor decoding that could be
5631 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
5632 on 0.3.0.1-alpha. Bug found by "haxxpop".
5633 - Rate-limit the log messages if we exceed the maximum number of
5634 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
5636 o Minor bugfixes (logging, relay):
5637 - Remove a forgotten debugging message when an introduction point
5638 successfully establishes a hidden service prop224 circuit with
5640 - Change three other log_warn() for an introduction point to
5641 protocol warnings, because they can be failure from the network
5642 and are not relevant to the operator. Fixes bug 23078; bugfix on
5643 0.3.0.1-alpha and 0.3.0.2-alpha.
5645 o Minor bugfixes (relay):
5646 - When a relay is not running as a directory cache, it will no
5647 longer generate compressed consensuses and consensus diff
5648 information. Previously, this was a waste of disk and CPU. Fixes
5649 bug 23275; bugfix on 0.3.1.1-alpha.
5651 o Minor bugfixes (robustness, error handling):
5652 - Improve our handling of the cases where OpenSSL encounters a
5653 memory error while encoding keys and certificates. We haven't
5654 observed these errors in the wild, but if they do happen, we now
5655 detect and respond better. Fixes bug 19418; bugfix on all versions
5656 of Tor. Reported by Guido Vranken.
5658 o Minor bugfixes (stability):
5659 - Avoid crashing on a double-free when unable to load or process an
5660 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
5661 with the clang static analyzer.
5663 o Minor bugfixes (testing):
5664 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5665 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5666 - Port the hs_ntor handshake test to work correctly with recent
5667 versions of the pysha3 module. Fixes bug 23071; bugfix
5670 o Minor bugfixes (Windows service):
5671 - When running as a Windows service, set the ID of the main thread
5672 correctly. Failure to do so made us fail to send log messages to
5673 the controller in 0.2.1.16-rc, slowed down controller event
5674 delivery in 0.2.7.3-rc and later, and crash with an assertion
5675 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
5676 Patch and diagnosis from "Vort".
5679 Changes in version 0.3.0.10 - 2017-08-02
5680 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
5681 from the current Tor alpha series. OpenBSD users and TPROXY users
5682 should upgrade; others are probably okay sticking with 0.3.0.9.
5684 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
5685 - Tor's repository now includes a Travis Continuous Integration (CI)
5686 configuration file (.travis.yml). This is meant to help new
5687 developers and contributors who fork Tor to a Github repository be
5688 better able to test their changes, and understand what we expect
5689 to pass. To use this new build feature, you must fork Tor to your
5690 Github account, then go into the "Integrations" menu in the
5691 repository settings for your fork and enable Travis, then push
5692 your changes. Closes ticket 22636.
5694 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
5695 - Fix a typo that had prevented TPROXY-based transparent proxying
5696 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
5697 Patch from "d4fq0fQAgoJ".
5699 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
5700 - Avoid an assertion failure bug affecting our implementation of
5701 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5702 handling of "0xbar" differs from what we had expected. Fixes bug
5703 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5705 o Minor features (backport from 0.3.1.5-alpha):
5706 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
5709 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
5710 - Roll over monthly accounting at the configured hour and minute,
5711 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
5712 Found by Andrey Karpov with PVS-Studio.
5714 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
5715 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
5716 bugfix on 0.2.8.1-alpha.
5717 - Fix warnings when building with libscrypt and openssl scrypt
5718 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
5719 - When building with certain versions of the mingw C header files,
5720 avoid float-conversion warnings when calling the C functions
5721 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
5724 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
5725 - Backport a fix for an "unused variable" warning that appeared
5726 in some versions of mingw. Fixes bug 22838; bugfix on
5729 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
5730 - Avoid Coverity build warnings related to our BUG() macro. By
5731 default, Coverity treats BUG() as the Linux kernel does: an
5732 instant abort(). We need to override that so our BUG() macro
5733 doesn't prevent Coverity from analyzing functions that use it.
5734 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
5736 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
5737 - When rejecting a router descriptor for running an obsolete version
5738 of Tor without ntor support, warn about the obsolete tor version,
5739 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
5741 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
5742 - Avoid a sandbox failure when trying to re-bind to a socket and
5743 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
5745 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
5746 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
5747 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
5750 Changes in version 0.3.1.5-alpha - 2017-08-01
5751 Tor 0.3.1.5-alpha improves the performance of consensus diff
5752 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
5753 several other bugs. If no serious bugs are found in this version, the
5754 next version will be a release candidate.
5756 This release also marks the end of support for the Tor 0.2.4.x,
5757 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
5758 further bug or security fixes. Anyone still running or distributing
5759 one of those versions should upgrade.
5761 o Major features (build system, continuous integration):
5762 - Tor's repository now includes a Travis Continuous Integration (CI)
5763 configuration file (.travis.yml). This is meant to help new
5764 developers and contributors who fork Tor to a Github repository be
5765 better able to test their changes, and understand what we expect
5766 to pass. To use this new build feature, you must fork Tor to your
5767 Github account, then go into the "Integrations" menu in the
5768 repository settings for your fork and enable Travis, then push
5769 your changes. Closes ticket 22636.
5771 o Major bugfixes (openbsd, denial-of-service):
5772 - Avoid an assertion failure bug affecting our implementation of
5773 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5774 handling of "0xbar" differs from what we had expected. Fixes bug
5775 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5777 o Major bugfixes (relay, performance):
5778 - Perform circuit handshake operations at a higher priority than we
5779 use for consensus diff creation and compression. This should
5780 prevent circuits from starving when a relay or bridge receives a
5781 new consensus, especially on lower-powered machines. Fixes bug
5782 22883; bugfix on 0.3.1.1-alpha.
5784 o Minor features (bridge authority):
5785 - Add "fingerprint" lines to the networkstatus-bridges file produced
5786 by bridge authorities. Closes ticket 22207.
5788 o Minor features (directory cache, consensus diff):
5789 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
5790 operators with low-resource environments to adjust the number of
5791 consensuses they'll store and generate diffs from. Most cache
5792 operators should leave it unchanged. Helps to work around
5795 o Minor features (geoip):
5796 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
5799 o Minor features (relay, performance):
5800 - Always start relays with at least two worker threads, to prevent
5801 priority inversion on slow tasks. Part of the fix for bug 22883.
5802 - Allow background work to be queued with different priorities, so
5803 that a big pile of slow low-priority jobs will not starve out
5804 higher priority jobs. This lays the groundwork for a fix for
5807 o Minor bugfixes (build system, rust):
5808 - Fix a problem where Rust toolchains were not being found when
5809 building without --enable-cargo-online-mode, due to setting the
5810 $HOME environment variable instead of $CARGO_HOME. Fixes bug
5811 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
5813 o Minor bugfixes (compatibility, zstd):
5814 - Write zstd epilogues correctly when the epilogue requires
5815 reallocation of the output buffer, even with zstd 1.3.0.
5816 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
5817 22927; bugfix on 0.3.1.1-alpha.
5819 o Minor bugfixes (compilation warnings):
5820 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
5821 22915; bugfix on 0.2.8.1-alpha.
5822 - Fix warnings when building with libscrypt and openssl scrypt
5823 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
5824 - Compile correctly when both openssl 1.1.0 and libscrypt are
5825 detected. Previously this would cause an error. Fixes bug 22892;
5826 bugfix on 0.3.1.1-alpha.
5827 - When building with certain versions of the mingw C header files,
5828 avoid float-conversion warnings when calling the C functions
5829 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
5832 o Minor bugfixes (coverity build support):
5833 - Avoid Coverity build warnings related to our BUG() macro. By
5834 default, Coverity treats BUG() as the Linux kernel does: an
5835 instant abort(). We need to override that so our BUG() macro
5836 doesn't prevent Coverity from analyzing functions that use it.
5837 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
5839 o Minor bugfixes (directory authority):
5840 - When a directory authority rejects a descriptor or extrainfo with
5841 a given digest, mark that digest as undownloadable, so that we do
5842 not attempt to download it again over and over. We previously
5843 tried to avoid downloading such descriptors by other means, but we
5844 didn't notice if we accidentally downloaded one anyway. This
5845 behavior became problematic in 0.2.7.2-alpha, when authorities
5846 began pinning Ed25519 keys. Fixes bug 22349; bugfix
5849 o Minor bugfixes (error reporting, windows):
5850 - When formatting Windows error messages, use the English format to
5851 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
5854 o Minor bugfixes (file limits, osx):
5855 - When setting the maximum number of connections allowed by the OS,
5856 always allow some extra file descriptors for other files. Fixes
5857 bug 22797; bugfix on 0.2.0.10-alpha.
5859 o Minor bugfixes (linux seccomp2 sandbox):
5860 - Avoid a sandbox failure when trying to re-bind to a socket and
5861 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
5863 o Minor bugfixes (memory leaks):
5864 - Fix a small memory leak when validating a configuration that uses
5865 two or more AF_UNIX sockets for the same port type. Fixes bug
5866 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
5868 o Minor bugfixes (unit tests):
5869 - test_consdiff_base64cmp would fail on OS X because while OS X
5870 follows the standard of (less than zero/zero/greater than zero),
5871 it doesn't follow the convention of (-1/0/+1). Make the test
5872 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
5873 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
5874 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
5877 Changes in version 0.3.1.4-alpha - 2017-06-29
5878 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
5879 to use a guard that was in the same network family as a chosen exit
5880 relay. This is a security regression; all clients running earlier
5881 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
5884 This release also fixes several other bugs introduced in 0.3.0.x
5885 and 0.3.1.x, including others that can affect bandwidth usage
5889 - To build with zstd and lzma support, Tor now requires the
5890 pkg-config tool at build time. (This requirement was new in
5891 0.3.1.1-alpha, but was not noted at the time. Noting it here to
5892 close ticket 22623.)
5894 o Major bugfixes (path selection, security):
5895 - When choosing which guard to use for a circuit, avoid the exit's
5896 family along with the exit itself. Previously, the new guard
5897 selection logic avoided the exit, but did not consider its family.
5898 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
5899 006 and CVE-2017-0377.
5901 o Major bugfixes (compression, zstd):
5902 - Correctly detect a full buffer when decompressing a large zstd-
5903 compressed input. Previously, we would sometimes treat a full
5904 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
5906 o Major bugfixes (directory protocol):
5907 - Ensure that we send "304 Not modified" as HTTP status code when a
5908 client is attempting to fetch a consensus or consensus diff, and
5909 the best one we can send them is one they already have. Fixes bug
5910 22702; bugfix on 0.3.1.1-alpha.
5912 o Major bugfixes (entry guards):
5913 - When starting with an old consensus, do not add new entry guards
5914 unless the consensus is "reasonably live" (under 1 day old). Fixes
5915 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
5917 o Minor features (bug mitigation, diagnostics, logging):
5918 - Avoid an assertion failure, and log a better error message, when
5919 unable to remove a file from the consensus cache on Windows.
5920 Attempts to mitigate and diagnose bug 22752.
5922 o Minor features (geoip):
5923 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
5926 o Minor bugfixes (compression):
5927 - When compressing or decompressing a buffer, check for a failure to
5928 create a compression object. Fixes bug 22626; bugfix
5930 - When decompressing a buffer, check for extra data after the end of
5931 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
5932 - When decompressing an object received over an anonymous directory
5933 connection, if we have already decompressed it using an acceptable
5934 compression method, do not reject it for looking like an
5935 unacceptable compression method. Fixes part of bug 22670; bugfix
5937 - When serving directory votes compressed with zlib, do not claim to
5938 have compressed them with zstd. Fixes bug 22669; bugfix
5940 - When spooling compressed data to an output buffer, don't try to
5941 spool more data when there is no more data to spool and we are not
5942 trying to flush the input. Previously, we would sometimes launch
5943 compression requests with nothing to do, which interferes with our
5944 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
5946 o Minor bugfixes (defensive programming):
5947 - Detect and break out of infinite loops in our compression code. We
5948 don't think that any such loops exist now, but it's best to be
5949 safe. Closes ticket 22672.
5950 - Fix a memset() off the end of an array when packing cells. This
5951 bug should be harmless in practice, since the corrupted bytes are
5952 still in the same structure, and are always padding bytes,
5953 ignored, or immediately overwritten, depending on compiler
5954 behavior. Nevertheless, because the memset()'s purpose is to make
5955 sure that any other cell-handling bugs can't expose bytes to the
5956 network, we need to fix it. Fixes bug 22737; bugfix on
5957 0.2.4.11-alpha. Fixes CID 1401591.
5959 o Minor bugfixes (linux seccomp2 sandbox):
5960 - Permit the fchmod system call, to avoid crashing on startup when
5961 starting with the seccomp2 sandbox and an unexpected set of
5962 permissions on the data directory or its contents. Fixes bug
5963 22516; bugfix on 0.2.5.4-alpha.
5964 - Fix a crash in the LZMA module, when the sandbox was enabled, and
5965 liblzma would allocate more than 16 MB of memory. We solve this by
5966 bumping the mprotect() limit in the sandbox module from 16 MB to
5967 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
5969 o Minor bugfixes (logging):
5970 - When decompressing, do not warn if we fail to decompress using a
5971 compression method that we merely guessed. Fixes part of bug
5972 22670; bugfix on 0.1.1.14-alpha.
5973 - When decompressing, treat mismatch between content-encoding and
5974 actual compression type as a protocol warning. Fixes part of bug
5975 22670; bugfix on 0.1.1.9-alpha.
5976 - Downgrade "assigned_to_cpuworker failed" message to info-level
5977 severity. In every case that can reach it, either a better warning
5978 has already been logged, or no warning is warranted. Fixes bug
5979 22356; bugfix on 0.2.6.3-alpha.
5980 - Demote a warn that was caused by libevent delays to info if
5981 netflow padding is less than 4.5 seconds late, or to notice
5982 if it is more (4.5 seconds is the amount of time that a netflow
5983 record might be emitted after, if we chose the maximum timeout).
5984 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
5986 o Minor bugfixes (process behavior):
5987 - When exiting because of an error, always exit with a nonzero exit
5988 status. Previously, we would fail to report an error in our exit
5989 status in cases related to __OwningControllerProcess failure,
5990 lockfile contention, and Ed25519 key initialization. Fixes bug
5991 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
5992 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
5996 - Add a manpage description for the key-pinning-journal file. Closes
5998 - Correctly note that bandwidth accounting values are stored in the
5999 state file, and the bw_accounting file is now obsolete. Closes
6001 - Document more of the files in the Tor data directory, including
6002 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
6003 approved-routers, sr-random, and diff-cache. Found while fixing
6007 Changes in version 0.3.0.9 - 2017-06-29
6008 Tor 0.3.0.9 fixes a path selection bug that would allow a client
6009 to use a guard that was in the same network family as a chosen exit
6010 relay. This is a security regression; all clients running earlier
6011 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
6014 This release also backports several other bugfixes from the 0.3.1.x
6017 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
6018 - When choosing which guard to use for a circuit, avoid the exit's
6019 family along with the exit itself. Previously, the new guard
6020 selection logic avoided the exit, but did not consider its family.
6021 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
6022 006 and CVE-2017-0377.
6024 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
6025 - Don't block bootstrapping when a primary bridge is offline and we
6026 can't get its descriptor. Fixes bug 22325; fixes one case of bug
6027 21969; bugfix on 0.3.0.3-alpha.
6029 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
6030 - When starting with an old consensus, do not add new entry guards
6031 unless the consensus is "reasonably live" (under 1 day old). Fixes
6032 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
6034 o Minor features (geoip):
6035 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
6038 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
6039 - Reject version numbers with non-numeric prefixes (such as +, -, or
6040 whitespace). Disallowing whitespace prevents differential version
6041 parsing between POSIX-based and Windows platforms. Fixes bug 21507
6042 and part of 21508; bugfix on 0.0.8pre1.
6044 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
6045 - Permit the fchmod system call, to avoid crashing on startup when
6046 starting with the seccomp2 sandbox and an unexpected set of
6047 permissions on the data directory or its contents. Fixes bug
6048 22516; bugfix on 0.2.5.4-alpha.
6050 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
6051 - Fix a memset() off the end of an array when packing cells. This
6052 bug should be harmless in practice, since the corrupted bytes are
6053 still in the same structure, and are always padding bytes,
6054 ignored, or immediately overwritten, depending on compiler
6055 behavior. Nevertheless, because the memset()'s purpose is to make
6056 sure that any other cell-handling bugs can't expose bytes to the
6057 network, we need to fix it. Fixes bug 22737; bugfix on
6058 0.2.4.11-alpha. Fixes CID 1401591.
6061 Changes in version 0.3.1.3-alpha - 2017-06-08
6062 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
6063 remotely crash a hidden service with an assertion failure. Anyone
6064 running a hidden service should upgrade to this version, or to some
6065 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
6067 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
6068 that sometimes made relays unreliable, as well as several other
6069 bugfixes described below.
6071 o Major bugfixes (hidden service, relay, security):
6072 - Fix a remotely triggerable assertion failure when a hidden service
6073 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
6074 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
6075 - Fix a remotely triggerable assertion failure caused by receiving a
6076 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6077 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6080 o Major bugfixes (relay, link handshake):
6081 - When performing the v3 link handshake on a TLS connection, report
6082 that we have the x509 certificate that we actually used on that
6083 connection, even if we have changed certificates since that
6084 connection was first opened. Previously, we would claim to have
6085 used our most recent x509 link certificate, which would sometimes
6086 make the link handshake fail. Fixes one case of bug 22460; bugfix
6089 o Major bugfixes (relays, key management):
6090 - Regenerate link and authentication certificates whenever the key
6091 that signs them changes; also, regenerate link certificates
6092 whenever the signed key changes. Previously, these processes were
6093 only weakly coupled, and we relays could (for minutes to hours)
6094 wind up with an inconsistent set of keys and certificates, which
6095 other relays would not accept. Fixes two cases of bug 22460;
6096 bugfix on 0.3.0.1-alpha.
6097 - When sending an Ed25519 signing->link certificate in a CERTS cell,
6098 send the certificate that matches the x509 certificate that we
6099 used on the TLS connection. Previously, there was a race condition
6100 if the TLS context rotated after we began the TLS handshake but
6101 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
6104 o Major bugfixes (torrc, crash):
6105 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
6106 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
6108 o Minor features (code style):
6109 - Add "Falls through" comments to our codebase, in order to silence
6110 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6111 Stieger. Closes ticket 22446.
6113 o Minor features (diagnostic):
6114 - Add logging messages to try to diagnose a rare bug that seems to
6115 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
6116 think this is happening because of incorrect system clocks, but
6117 we'd like to know for certain. Diagnostic for bug 22466.
6119 o Minor bugfixes (correctness):
6120 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6121 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6123 o Minor bugfixes (directory protocol):
6124 - Check for libzstd >= 1.1, because older versions lack the
6125 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
6127 o Minor bugfixes (link handshake):
6128 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
6129 months, and regenerate it when it is within one month of expiring.
6130 Previously, we had generated this certificate at startup with a
6131 ten-year lifetime, but that could lead to weird behavior when Tor
6132 was started with a grossly inaccurate clock. Mitigates bug 22466;
6133 mitigation on 0.3.0.1-alpha.
6135 o Minor bugfixes (storage directories):
6136 - Always check for underflows in the cached storage directory usage.
6137 If the usage does underflow, re-calculate it. Also, avoid a
6138 separate underflow when the usage is not known. Fixes bug 22424;
6139 bugfix on 0.3.1.1-alpha.
6141 o Minor bugfixes (unit tests):
6142 - The unit tests now pass on systems where localhost is misconfigured
6143 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
6147 - Clarify the manpage for the (deprecated) torify script. Closes
6150 Changes in version 0.3.0.8 - 2017-06-08
6151 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
6152 remotely crash a hidden service with an assertion failure. Anyone
6153 running a hidden service should upgrade to this version, or to some
6154 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
6156 Tor 0.3.0.8 also includes fixes for several key management bugs
6157 that sometimes made relays unreliable, as well as several other
6158 bugfixes described below.
6160 o Major bugfixes (hidden service, relay, security, backport
6161 from 0.3.1.3-alpha):
6162 - Fix a remotely triggerable assertion failure when a hidden service
6163 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
6164 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
6165 - Fix a remotely triggerable assertion failure caused by receiving a
6166 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6167 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6170 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
6171 - When performing the v3 link handshake on a TLS connection, report
6172 that we have the x509 certificate that we actually used on that
6173 connection, even if we have changed certificates since that
6174 connection was first opened. Previously, we would claim to have
6175 used our most recent x509 link certificate, which would sometimes
6176 make the link handshake fail. Fixes one case of bug 22460; bugfix
6179 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
6180 - Regenerate link and authentication certificates whenever the key
6181 that signs them changes; also, regenerate link certificates
6182 whenever the signed key changes. Previously, these processes were
6183 only weakly coupled, and we relays could (for minutes to hours)
6184 wind up with an inconsistent set of keys and certificates, which
6185 other relays would not accept. Fixes two cases of bug 22460;
6186 bugfix on 0.3.0.1-alpha.
6187 - When sending an Ed25519 signing->link certificate in a CERTS cell,
6188 send the certificate that matches the x509 certificate that we
6189 used on the TLS connection. Previously, there was a race condition
6190 if the TLS context rotated after we began the TLS handshake but
6191 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
6194 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
6195 - Stop rejecting v3 hidden service descriptors because their size
6196 did not match an old padding rule. Fixes bug 22447; bugfix on
6199 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6200 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6201 December 2016 (of which ~126 were still functional) with a list of
6202 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6203 2017. Resolves ticket 21564.
6205 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
6206 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
6207 bug 22252; bugfix on 0.2.9.3-alpha.
6209 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
6210 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6211 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6213 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
6214 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
6215 months, and regenerate it when it is within one month of expiring.
6216 Previously, we had generated this certificate at startup with a
6217 ten-year lifetime, but that could lead to weird behavior when Tor
6218 was started with a grossly inaccurate clock. Mitigates bug 22466;
6219 mitigation on 0.3.0.1-alpha.
6221 o Minor bugfixes (memory leak, directory authority, backport from
6223 - When directory authorities reject a router descriptor due to
6224 keypinning, free the router descriptor rather than leaking the
6225 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
6228 Changes in version 0.2.9.11 - 2017-06-08
6229 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
6230 remotely crash a hidden service with an assertion failure. Anyone
6231 running a hidden service should upgrade to this version, or to some
6232 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6233 are not affected by TROVE-2017-004.)
6235 Tor 0.2.9.11 also backports fixes for several key management bugs
6236 that sometimes made relays unreliable, as well as several other
6237 bugfixes described below.
6239 o Major bugfixes (hidden service, relay, security, backport
6240 from 0.3.1.3-alpha):
6241 - Fix a remotely triggerable assertion failure caused by receiving a
6242 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6243 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6246 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
6247 - When performing the v3 link handshake on a TLS connection, report
6248 that we have the x509 certificate that we actually used on that
6249 connection, even if we have changed certificates since that
6250 connection was first opened. Previously, we would claim to have
6251 used our most recent x509 link certificate, which would sometimes
6252 make the link handshake fail. Fixes one case of bug 22460; bugfix
6255 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6256 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6257 December 2016 (of which ~126 were still functional) with a list of
6258 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6259 2017. Resolves ticket 21564.
6261 o Minor features (future-proofing, backport from 0.3.0.7):
6262 - Tor no longer refuses to download microdescriptors or descriptors if
6263 they are listed as "published in the future". This change will
6264 eventually allow us to stop listing meaningful "published" dates
6265 in microdescriptor consensuses, and thereby allow us to reduce the
6266 resources required to download consensus diffs by over 50%.
6267 Implements part of ticket 21642; implements part of proposal 275.
6269 o Minor features (directory authorities, backport from 0.3.0.4-rc)
6270 - Directory authorities now reject relays running versions
6271 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
6272 suffer from bug 20499 and don't keep their consensus cache
6273 up-to-date. Resolves ticket 20509.
6275 o Minor features (geoip):
6276 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6279 o Minor bugfixes (control port, backport from 0.3.0.6):
6280 - The GETINFO extra-info/digest/<digest> command was broken because
6281 of a wrong base16 decode return value check, introduced when
6282 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
6284 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
6285 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6286 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6288 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
6289 - The getpid() system call is now permitted under the Linux seccomp2
6290 sandbox, to avoid crashing with versions of OpenSSL (and other
6291 libraries) that attempt to learn the process's PID by using the
6292 syscall rather than the VDSO code. Fixes bug 21943; bugfix
6295 o Minor bugfixes (memory leak, directory authority, backport
6296 from 0.3.1.2-alpha):
6297 - When directory authorities reject a router descriptor due to
6298 keypinning, free the router descriptor rather than leaking the
6299 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
6301 Changes in version 0.2.8.14 - 2017-06-08
6302 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
6303 remotely crash a hidden service with an assertion failure. Anyone
6304 running a hidden service should upgrade to this version, or to some
6305 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6306 are not affected by TROVE-2017-004.)
6308 o Major bugfixes (hidden service, relay, security):
6309 - Fix a remotely triggerable assertion failure caused by receiving a
6310 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6311 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6314 o Minor features (geoip):
6315 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6318 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6319 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6320 December 2016 (of which ~126 were still functional) with a list of
6321 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6322 2017. Resolves ticket 21564.
6324 o Minor bugfixes (correctness):
6325 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6326 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6328 Changes in version 0.2.7.8 - 2017-06-08
6329 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
6330 remotely crash a hidden service with an assertion failure. Anyone
6331 running a hidden service should upgrade to this version, or to some
6332 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6333 are not affected by TROVE-2017-004.)
6335 o Major bugfixes (hidden service, relay, security):
6336 - Fix a remotely triggerable assertion failure caused by receiving a
6337 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6338 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6341 o Minor features (geoip):
6342 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6345 o Minor bugfixes (correctness):
6346 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6347 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6350 Changes in version 0.2.6.12 - 2017-06-08
6351 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
6352 remotely crash a hidden service with an assertion failure. Anyone
6353 running a hidden service should upgrade to this version, or to some
6354 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6355 are not affected by TROVE-2017-004.)
6357 o Major bugfixes (hidden service, relay, security):
6358 - Fix a remotely triggerable assertion failure caused by receiving a
6359 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6360 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6363 o Minor features (geoip):
6364 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6367 o Minor bugfixes (correctness):
6368 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6369 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6371 Changes in version 0.2.5.14 - 2017-06-08
6372 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
6373 remotely crash a hidden service with an assertion failure. Anyone
6374 running a hidden service should upgrade to this version, or to some
6375 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6376 are not affected by TROVE-2017-004.)
6378 o Major bugfixes (hidden service, relay, security):
6379 - Fix a remotely triggerable assertion failure caused by receiving a
6380 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6381 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6384 o Minor features (geoip):
6385 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6388 o Minor bugfixes (correctness):
6389 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6390 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6392 Changes in version 0.2.4.29 - 2017-06-08
6393 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
6394 remotely crash a hidden service with an assertion failure. Anyone
6395 running a hidden service should upgrade to this version, or to some
6396 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6397 are not affected by TROVE-2017-004.)
6399 o Major bugfixes (hidden service, relay, security):
6400 - Fix a remotely triggerable assertion failure caused by receiving a
6401 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6402 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6405 o Minor features (geoip):
6406 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6409 o Minor bugfixes (correctness):
6410 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6411 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6414 Changes in version 0.3.1.2-alpha - 2017-05-26
6415 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
6416 fixes a few bugs found while testing 0.3.1.1-alpha, including a
6417 memory corruption bug that affected relay stability.
6419 o Major bugfixes (crash, relay):
6420 - Fix a memory-corruption bug in relays that set MyFamily.
6421 Previously, they would double-free MyFamily elements when making
6422 the next descriptor or when changing their configuration. Fixes
6423 bug 22368; bugfix on 0.3.1.1-alpha.
6425 o Minor bugfixes (logging):
6426 - Log a better message when a directory authority replies to an
6427 upload with an unexpected status code. Fixes bug 11121; bugfix
6430 o Minor bugfixes (memory leak, directory authority):
6431 - When directory authorities reject a router descriptor due to
6432 keypinning, free the router descriptor rather than leaking the
6433 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
6436 Changes in version 0.3.1.1-alpha - 2017-05-22
6437 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
6438 reduces the bandwidth usage for Tor's directory protocol, adds some
6439 basic padding to resist netflow-based traffic analysis and to serve as
6440 the basis of other padding in the future, and adds rust support to the
6443 It also contains numerous other small features and improvements to
6444 security, correctness, and performance.
6446 Below are the changes since 0.3.0.7.
6448 o Major features (directory protocol):
6449 - Tor relays and authorities can now serve clients an abbreviated
6450 version of the consensus document, containing only the changes
6451 since an older consensus document that the client holds. Clients
6452 now request these documents when available. When both client and
6453 server use this new protocol, they will use far less bandwidth (up
6454 to 94% less) to keep the client's consensus up-to-date. Implements
6455 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
6456 - Tor can now compress directory traffic with lzma or with zstd
6457 compression algorithms, which can deliver better bandwidth
6458 performance. Because lzma is computationally expensive, it's only
6459 used for documents that can be compressed once and served many
6460 times. Support for these algorithms requires that tor is built
6461 with the libzstd and/or liblzma libraries available. Implements
6462 proposal 278; closes ticket 21662.
6463 - Relays now perform the more expensive compression operations, and
6464 consensus diff generation, in worker threads. This separation
6465 avoids delaying the main thread when a new consensus arrives.
6467 o Major features (experimental):
6468 - Tor can now build modules written in Rust. To turn this on, pass
6469 the "--enable-rust" flag to the configure script. It's not time to
6470 get excited yet: currently, there is no actual Rust functionality
6471 beyond some simple glue code, and a notice at startup to tell you
6472 that Rust is running. Still, we hope that programmers and
6473 packagers will try building Tor with Rust support, so that we can
6474 find issues and solve portability problems. Closes ticket 22106.
6476 o Major features (traffic analysis resistance):
6477 - Connections between clients and relays now send a padding cell in
6478 each direction every 1.5 to 9.5 seconds (tunable via consensus
6479 parameters). This padding will not resist specialized
6480 eavesdroppers, but it should be enough to make many ISPs' routine
6481 network flow logging less useful in traffic analysis against
6484 Padding is negotiated using Tor's link protocol, so both relays
6485 and clients must upgrade for this to take effect. Clients may
6486 still send padding despite the relay's version by setting
6487 ConnectionPadding 1 in torrc, and may disable padding by setting
6488 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
6489 users with the torrc option ReducedConnectionPadding. Implements
6490 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
6491 - Relays will publish 24 hour totals of padding and non-padding cell
6492 counts to their extra-info descriptors, unless PaddingStatistics 0
6493 is set in torrc. These 24 hour totals are also rounded to
6496 o Major bugfixes (connection usage):
6497 - We use NETINFO cells to try to determine if both relays involved
6498 in a connection will agree on the canonical status of that
6499 connection. We prefer the connections where this is the case for
6500 extend cells, and try to close connections where relays disagree
6501 on their canonical status early. Also, we now prefer the oldest
6502 valid connection for extend cells. These two changes should reduce
6503 the number of long-term connections that are kept open between
6504 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
6505 - Relays now log hourly statistics (look for
6506 "channel_check_for_duplicates" lines) on the total number of
6507 connections to other relays. If the number of connections per
6508 relay is unexpectedly large, this log message is at notice level.
6509 Otherwise it is at info.
6511 o Major bugfixes (entry guards):
6512 - Don't block bootstrapping when a primary bridge is offline and we
6513 can't get its descriptor. Fixes bug 22325; fixes one case of bug
6514 21969; bugfix on 0.3.0.3-alpha.
6516 o Major bugfixes (linux TPROXY support):
6517 - Fix a typo that had prevented TPROXY-based transparent proxying
6518 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
6519 Patch from "d4fq0fQAgoJ".
6521 o Minor features (security, windows):
6522 - Enable a couple of pieces of Windows hardening: one
6523 (HeapEnableTerminationOnCorruption) that has been on-by-default
6524 since Windows 8, and unavailable before Windows 7; and one
6525 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6526 affect us, but shouldn't do any harm. Closes ticket 21953.
6528 o Minor features (config options):
6529 - Allow "%include" directives in torrc configuration files. These
6530 directives import the settings from other files, or from all the
6531 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
6532 - Make SAVECONF return an error when overwriting a torrc that has
6533 includes. Using SAVECONF with the FORCE option will allow it to
6534 overwrite torrc even if includes are used. Related to ticket 1922.
6535 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
6536 will work without the FORCE option. Related to ticket 1922.
6538 o Minor features (controller):
6539 - Warn the first time that a controller requests data in the long-
6540 deprecated 'GETINFO network-status' format. Closes ticket 21703.
6542 o Minor features (defaults):
6543 - The default value for UseCreateFast is now 0: clients which
6544 haven't yet received a consensus document will now use a proper
6545 ntor handshake to talk to their directory servers whenever they
6546 can. Closes ticket 21407.
6547 - Onion key rotation and expiry intervals are now defined as a
6548 network consensus parameter, per proposal 274. The default
6549 lifetime of an onion key is increased from 7 to 28 days. Old onion
6550 keys will expire after 7 days by default. This change will make
6551 consensus diffs much smaller, and save significant bandwidth.
6552 Closes ticket 21641.
6554 o Minor features (fallback directory list):
6555 - Update the fallback directory mirror whitelist and blacklist based
6556 on operator emails. Closes task 21121.
6557 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6558 December 2016 (of which ~126 were still functional) with a list of
6559 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6560 2017. Resolves ticket 21564.
6562 o Minor features (hidden services, logging):
6563 - Log a message when a hidden service descriptor has fewer
6564 introduction points than specified in
6565 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
6566 - Log a message when a hidden service reaches its introduction point
6567 circuit limit, and when that limit is reset. Follow up to ticket
6568 21594; closes ticket 21622.
6569 - Warn user if multiple entries in EntryNodes and at least one
6570 HiddenService are used together. Pinning EntryNodes along with a
6571 hidden service can be possibly harmful; for instance see ticket
6572 14917 or 21155. Closes ticket 21155.
6574 o Minor features (linux seccomp2 sandbox):
6575 - We now have a document storage backend compatible with the Linux
6576 seccomp2 sandbox. This backend is used for consensus documents and
6577 diffs between them; in the long term, we'd like to use it for
6578 unparseable directory material too. Closes ticket 21645
6579 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
6580 from 1MB to 16MB. This was necessary with the glibc allocator in
6581 order to allow worker threads to allocate more memory -- which in
6582 turn is necessary because of our new use of worker threads for
6583 compression. Closes ticket 22096.
6585 o Minor features (logging):
6586 - Log files are no longer created world-readable by default.
6587 (Previously, most distributors would store the logs in a non-
6588 world-readable location to prevent inappropriate access. This
6589 change is an extra precaution.) Closes ticket 21729; patch
6592 o Minor features (performance):
6593 - Our Keccak (SHA-3) implementation now accesses memory more
6594 efficiently, especially on little-endian systems. Closes
6596 - Add an O(1) implementation of channel_find_by_global_id(), to
6597 speed some controller functions.
6599 o Minor features (relay, configuration):
6600 - The MyFamily option may now be repeated as many times as desired,
6601 for relays that want to configure large families. Closes ticket
6602 4998; patch by Daniel Pinto.
6604 o Minor features (safety):
6605 - Add an explicit check to extrainfo_parse_entry_from_string() for
6606 NULL inputs. We don't believe this can actually happen, but it may
6607 help silence a warning from the Clang analyzer. Closes
6610 o Minor features (testing):
6611 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
6612 When Tor is compiled with this option, we disable a number of
6613 redundant memory-safety failsafes that are intended to stop bugs
6614 from becoming security issues. This makes it easier to hunt for
6615 bugs that would be security issues without the failsafes turned
6616 on. Closes ticket 21439.
6617 - Add a general event-tracing instrumentation support to Tor. This
6618 subsystem will enable developers and researchers to add fine-
6619 grained instrumentation to their Tor instances, for use when
6620 examining Tor network performance issues. There are no trace
6621 events yet, and event-tracing is off by default unless enabled at
6622 compile time. Implements ticket 13802.
6623 - Improve our version parsing tests: add tests for typical version
6624 components, add tests for invalid versions, including numeric
6625 range and non-numeric prefixes. Unit tests 21278, 21450, and
6626 21507. Partially implements 21470.
6628 o Minor bugfixes (bandwidth accounting):
6629 - Roll over monthly accounting at the configured hour and minute,
6630 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
6631 Found by Andrey Karpov with PVS-Studio.
6633 o Minor bugfixes (code correctness):
6634 - Accurately identify client connections by their lack of peer
6635 authentication. This means that we bail out earlier if asked to
6636 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
6639 o Minor bugfixes (configuration):
6640 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
6641 bug 22252; bugfix on 0.2.9.3-alpha.
6643 o Minor bugfixes (connection lifespan):
6644 - Allow more control over how long TLS connections are kept open:
6645 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
6646 single option called CircuitsAvailableTimeout. Also, allow the
6647 consensus to control the default values for both this preference
6648 and the lifespan of relay-to-relay connections. Fixes bug 17592;
6649 bugfix on 0.2.5.5-alpha.
6650 - Increase the initial circuit build timeout testing frequency, to
6651 help ensure that ReducedConnectionPadding clients finish learning
6652 a timeout before their orconn would expire. The initial testing
6653 rate was set back in the days of TAP and before the Tor Browser
6654 updater, when we had to be much more careful about new clients
6655 making lots of circuits. With this change, a circuit build timeout
6656 is learned in about 15-20 minutes, instead of 100-120 minutes.
6658 o Minor bugfixes (controller):
6659 - GETINFO onions/current and onions/detached no longer respond with
6660 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
6661 - Trigger HS descriptor events on the control port when the client
6662 fails to pick a hidden service directory for a hidden service.
6663 This can happen if all the hidden service directories are in
6664 ExcludeNodes, or they have all been queried within the last 15
6665 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
6667 o Minor bugfixes (directory authority):
6668 - When rejecting a router descriptor for running an obsolete version
6669 of Tor without ntor support, warn about the obsolete tor version,
6670 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
6671 - Prevent the shared randomness subsystem from asserting when
6672 initialized by a bridge authority with an incomplete configuration
6673 file. Fixes bug 21586; bugfix on 0.2.9.8.
6675 o Minor bugfixes (exit-side DNS):
6676 - Fix an untriggerable assertion that checked the output of a
6677 libevent DNS error, so that the assertion actually behaves as
6678 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
6679 Karpov using PVS-Studio.
6681 o Minor bugfixes (fallback directories):
6682 - Make the usage example in updateFallbackDirs.py actually work, and
6683 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
6684 - Decrease the guard flag average required to be a fallback. This
6685 allows us to keep relays that have their guard flag removed when
6686 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
6687 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
6688 bugfix on 0.2.8.1-alpha.
6689 - Make sure fallback directory mirrors have the same address, port,
6690 and relay identity key for at least 30 days before they are
6691 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
6693 o Minor bugfixes (hidden services):
6694 - Stop printing a cryptic warning when a hidden service gets a
6695 request to connect to a virtual port that it hasn't configured.
6696 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
6697 - Simplify hidden service descriptor creation by using an existing
6698 flag to check if an introduction point is established. Fixes bug
6699 21599; bugfix on 0.2.7.2-alpha.
6701 o Minor bugfixes (memory leak):
6702 - Fix a small memory leak at exit from the backtrace handler code.
6703 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
6705 o Minor bugfixes (protocol, logging):
6706 - Downgrade a log statement about unexpected relay cells from "bug"
6707 to "protocol warning", because there is at least one use case
6708 where it can be triggered by a buggy tor implementation. Fixes bug
6709 21293; bugfix on 0.1.1.14-alpha.
6711 o Minor bugfixes (testing):
6712 - Use unbuffered I/O for utility functions around the
6713 process_handle_t type. This fixes unit test failures reported on
6714 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
6715 - Make display of captured unit test log messages consistent. Fixes
6716 bug 21510; bugfix on 0.2.9.3-alpha.
6717 - Make test-network.sh always call chutney's test-network.sh.
6718 Previously, this only worked on systems which had bash installed,
6719 due to some bash-specific code in the script. Fixes bug 19699;
6720 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
6722 o Minor bugfixes (voting consistency):
6723 - Reject version numbers with non-numeric prefixes (such as +, -, or
6724 whitespace). Disallowing whitespace prevents differential version
6725 parsing between POSIX-based and Windows platforms. Fixes bug 21507
6726 and part of 21508; bugfix on 0.0.8pre1.
6728 o Minor bugfixes (windows, relay):
6729 - Resolve "Failure from drain_fd: No error" warnings on Windows
6730 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
6732 o Code simplification and refactoring:
6733 - Break up the 630-line function connection_dir_client_reached_eof()
6734 into a dozen smaller functions. This change should help
6735 maintainability and readability of the client directory code.
6736 - Isolate our use of the openssl headers so that they are only
6737 included from our crypto wrapper modules, and from tests that
6738 examine those modules' internals. Closes ticket 21841.
6739 - Simplify our API to launch directory requests, making it more
6740 extensible and less error-prone. Now it's easier to add extra
6741 headers to directory requests. Closes ticket 21646.
6742 - Our base64 decoding functions no longer overestimate the output
6743 space that they need when parsing unpadded inputs. Closes
6745 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
6746 Resolves ticket 22213.
6747 - The logic that directory caches use to spool request to clients,
6748 serving them one part at a time so as not to allocate too much
6749 memory, has been refactored for consistency. Previously there was
6750 a separate spooling implementation per type of spoolable data. Now
6751 there is one common spooling implementation, with extensible data
6752 types. Closes ticket 21651.
6753 - Tor's compression module now supports multiple backends. Part of
6754 the implementation for proposal 278; closes ticket 21663.
6757 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
6758 Closes ticket 21873.
6759 - Correct documentation about the default DataDirectory value.
6760 Closes ticket 21151.
6761 - Document the default behavior of NumEntryGuards and
6762 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
6764 - Document key=value pluggable transport arguments for Bridge lines
6765 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
6766 - Note that bandwidth-limiting options don't affect TCP headers or
6767 DNS. Closes ticket 17170.
6769 o Removed features (configuration options, all in ticket 22060):
6770 - These configuration options are now marked Obsolete, and no longer
6771 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
6772 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
6773 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
6774 in 0.2.9.2-alpha and have now been removed. The previous default
6775 behavior is now always chosen; the previous (less secure) non-
6776 default behavior is now unavailable.
6777 - CloseHSClientCircuitsImmediatelyOnTimeout and
6778 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
6779 0.2.9.2-alpha and now have been removed. HS circuits never close
6780 on circuit build timeout; they have a longer timeout period.
6781 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
6782 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
6783 (and others) to configure listen-only and advertise-only addresses.
6785 o Removed features (tools):
6786 - We've removed the tor-checkkey tool from src/tools. Long ago, we
6787 used it to help people detect RSA keys that were generated by
6788 versions of Debian affected by CVE-2008-0166. But those keys have
6789 been out of circulation for ages, and this tool is no longer
6790 required. Closes ticket 21842.
6793 Changes in version 0.3.0.7 - 2017-05-15
6794 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
6795 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
6796 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
6797 clients are not affected.
6799 o Major bugfixes (hidden service directory, security):
6800 - Fix an assertion failure in the hidden service directory code, which
6801 could be used by an attacker to remotely cause a Tor relay process to
6802 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
6803 should upgrade. This security issue is tracked as TROVE-2017-002.
6804 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
6807 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6810 o Minor features (future-proofing):
6811 - Tor no longer refuses to download microdescriptors or descriptors
6812 if they are listed as "published in the future". This change will
6813 eventually allow us to stop listing meaningful "published" dates
6814 in microdescriptor consensuses, and thereby allow us to reduce the
6815 resources required to download consensus diffs by over 50%.
6816 Implements part of ticket 21642; implements part of proposal 275.
6818 o Minor bugfixes (Linux seccomp2 sandbox):
6819 - The getpid() system call is now permitted under the Linux seccomp2
6820 sandbox, to avoid crashing with versions of OpenSSL (and other
6821 libraries) that attempt to learn the process's PID by using the
6822 syscall rather than the VDSO code. Fixes bug 21943; bugfix
6826 Changes in version 0.3.0.6 - 2017-04-26
6827 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
6829 With the 0.3.0 series, clients and relays now use Ed25519 keys to
6830 authenticate their link connections to relays, rather than the old
6831 RSA1024 keys that they used before. (Circuit crypto has been
6832 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
6833 the guard selection and replacement algorithm to behave more robustly
6834 in the presence of unreliable networks, and to resist guard-
6837 This series also includes numerous other small features and bugfixes,
6838 along with more groundwork for the upcoming hidden-services revamp.
6840 Per our stable release policy, we plan to support the Tor 0.3.0
6841 release series for at least the next nine months, or for three months
6842 after the first stable release of the 0.3.1 series: whichever is
6843 longer. If you need a release with long-term support, we recommend
6844 that you stay with the 0.2.9 series.
6846 Below are the changes since 0.3.0.5-rc. For a list of all changes
6847 since 0.2.9, see the ReleaseNotes file.
6849 o Minor features (geoip):
6850 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
6853 o Minor bugfixes (control port):
6854 - The GETINFO extra-info/digest/<digest> command was broken because
6855 of a wrong base16 decode return value check, introduced when
6856 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
6858 o Minor bugfixes (crash prevention):
6859 - Fix a (currently untriggerable, but potentially dangerous) crash
6860 bug when base32-encoding inputs whose sizes are not a multiple of
6861 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
6864 Changes in version 0.3.0.5-rc - 2017-04-05
6865 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
6866 0.3.0 release series.
6868 This is the second release candidate in the Tor 0.3.0 series, and has
6869 much fewer changes than the first. If we find no new bugs or
6870 regressions here, the first stable 0.3.0 release will be nearly
6873 o Major bugfixes (crash, directory connections):
6874 - Fix a rare crash when sending a begin cell on a circuit whose
6875 linked directory connection had already been closed. Fixes bug
6876 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
6878 o Major bugfixes (guard selection):
6879 - Fix a guard selection bug where Tor would refuse to bootstrap in
6880 some cases if the user swapped a bridge for another bridge in
6881 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
6882 Reported by "torvlnt33r".
6884 o Minor features (geoip):
6885 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
6888 o Minor bugfix (compilation):
6889 - Fix a warning when compiling hs_service.c. Previously, it had no
6890 exported symbols when compiled for libor.a, resulting in a
6891 compilation warning from clang. Fixes bug 21825; bugfix
6894 o Minor bugfixes (hidden services):
6895 - Make hidden services check for failed intro point connections,
6896 even when they have exceeded their intro point creation limit.
6897 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
6898 - Make hidden services with 8 to 10 introduction points check for
6899 failed circuits immediately after startup. Previously, they would
6900 wait for 5 minutes before performing their first checks. Fixes bug
6901 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
6903 o Minor bugfixes (memory leaks):
6904 - Fix a memory leak when using GETCONF on a port option. Fixes bug
6905 21682; bugfix on 0.3.0.3-alpha.
6907 o Minor bugfixes (relay):
6908 - Avoid a double-marked-circuit warning that could happen when we
6909 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
6912 o Minor bugfixes (tests):
6913 - Run the entry_guard_parse_from_state_full() test with the time set
6914 to a specific date. (The guard state that this test was parsing
6915 contained guards that had expired since the test was first
6916 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
6919 - Update the description of the directory server options in the
6920 manual page, to clarify that a relay no longer needs to set
6921 DirPort in order to be a directory cache. Closes ticket 21720.
6925 Changes in version 0.2.8.13 - 2017-03-03
6926 Tor 0.2.8.13 backports a security fix from later Tor
6927 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
6928 this release, if for some reason they cannot upgrade to a later
6929 release series, and if they build Tor with the --enable-expensive-hardening
6932 Note that support for Tor 0.2.8.x is ending next year: we will not issue
6933 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
6934 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
6936 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
6937 - Fix an integer underflow bug when comparing malformed Tor
6938 versions. This bug could crash Tor when built with
6939 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
6940 0.2.9.8, which were built with -ftrapv by default. In other cases
6941 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
6942 on 0.0.8pre1. Found by OSS-Fuzz.
6944 o Minor features (geoip):
6945 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
6949 Changes in version 0.2.7.7 - 2017-03-03
6950 Tor 0.2.7.7 backports a number of security fixes from later Tor
6951 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
6952 this release, if for some reason they cannot upgrade to a later
6955 Note that support for Tor 0.2.7.x is ending this year: we will not issue
6956 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
6957 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
6959 o Directory authority changes (backport from 0.2.8.5-rc):
6960 - Urras is no longer a directory authority. Closes ticket 19271.
6962 o Directory authority changes (backport from 0.2.9.2-alpha):
6963 - The "Tonga" bridge authority has been retired; the new bridge
6964 authority is "Bifroest". Closes tickets 19728 and 19690.
6966 o Directory authority key updates (backport from 0.2.8.1-alpha):
6967 - Update the V3 identity key for the dannenberg directory authority:
6968 it was changed on 18 November 2015. Closes task 17906. Patch
6971 o Major bugfixes (parsing, security, backport from 0.2.9.8):
6972 - Fix a bug in parsing that could cause clients to read a single
6973 byte past the end of an allocated region. This bug could be used
6974 to cause hardened clients (built with --enable-expensive-hardening)
6975 to crash if they tried to visit a hostile hidden service. Non-
6976 hardened clients are only affected depending on the details of
6977 their platform's memory allocator. Fixes bug 21018; bugfix on
6978 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
6979 2016-12-002 and as CVE-2016-1254.
6981 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
6982 - Stop a crash that could occur when a client running with DNSPort
6983 received a query with multiple address types, and the first
6984 address type was not supported. Found and fixed by Scott Dial.
6985 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
6986 - Prevent a class of security bugs caused by treating the contents
6987 of a buffer chunk as if they were a NUL-terminated string. At
6988 least one such bug seems to be present in all currently used
6989 versions of Tor, and would allow an attacker to remotely crash
6990 most Tor instances, especially those compiled with extra compiler
6991 hardening. With this defense in place, such bugs can't crash Tor,
6992 though we should still fix them as they occur. Closes ticket
6993 20384 (TROVE-2016-10-001).
6995 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
6996 - Avoid a difficult-to-trigger heap corruption attack when extending
6997 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
6998 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
6999 Reported by Guido Vranken.
7001 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7002 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7003 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7005 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7006 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7007 pointer to the previous (uninitialized) key value. The impact here
7008 should be limited to a difficult-to-trigger crash, if OpenSSL is
7009 running an engine that makes key generation failures possible, or
7010 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7011 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7014 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7015 - Fix an integer underflow bug when comparing malformed Tor
7016 versions. This bug could crash Tor when built with
7017 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7018 0.2.9.8, which were built with -ftrapv by default. In other cases
7019 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7020 on 0.0.8pre1. Found by OSS-Fuzz.
7022 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7023 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7024 zero size. Check size argument to memwipe() for underflow. Fixes
7025 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7028 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7029 - Make Tor survive errors involving connections without a
7030 corresponding event object. Previously we'd fail with an
7031 assertion; now we produce a log message. Related to bug 16248.
7033 o Minor features (geoip):
7034 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7038 Changes in version 0.2.6.11 - 2017-03-03
7039 Tor 0.2.6.11 backports a number of security fixes from later Tor
7040 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
7041 this release, if for some reason they cannot upgrade to a later
7044 Note that support for Tor 0.2.6.x is ending this year: we will not issue
7045 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
7046 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7048 o Directory authority changes (backport from 0.2.8.5-rc):
7049 - Urras is no longer a directory authority. Closes ticket 19271.
7051 o Directory authority changes (backport from 0.2.9.2-alpha):
7052 - The "Tonga" bridge authority has been retired; the new bridge
7053 authority is "Bifroest". Closes tickets 19728 and 19690.
7055 o Directory authority key updates (backport from 0.2.8.1-alpha):
7056 - Update the V3 identity key for the dannenberg directory authority:
7057 it was changed on 18 November 2015. Closes task 17906. Patch
7060 o Major features (security fixes, backport from 0.2.9.4-alpha):
7061 - Prevent a class of security bugs caused by treating the contents
7062 of a buffer chunk as if they were a NUL-terminated string. At
7063 least one such bug seems to be present in all currently used
7064 versions of Tor, and would allow an attacker to remotely crash
7065 most Tor instances, especially those compiled with extra compiler
7066 hardening. With this defense in place, such bugs can't crash Tor,
7067 though we should still fix them as they occur. Closes ticket
7068 20384 (TROVE-2016-10-001).
7070 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7071 - Fix a bug in parsing that could cause clients to read a single
7072 byte past the end of an allocated region. This bug could be used
7073 to cause hardened clients (built with --enable-expensive-hardening)
7074 to crash if they tried to visit a hostile hidden service. Non-
7075 hardened clients are only affected depending on the details of
7076 their platform's memory allocator. Fixes bug 21018; bugfix on
7077 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7078 2016-12-002 and as CVE-2016-1254.
7080 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
7081 - Stop a crash that could occur when a client running with DNSPort
7082 received a query with multiple address types, and the first
7083 address type was not supported. Found and fixed by Scott Dial.
7084 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7086 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7087 - Fix an error that could cause us to read 4 bytes before the
7088 beginning of an openssl string. This bug could be used to cause
7089 Tor to crash on systems with unusual malloc implementations, or
7090 systems with unusual hardening installed. Fixes bug 17404; bugfix
7093 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7094 - Avoid a difficult-to-trigger heap corruption attack when extending
7095 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7096 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7097 Reported by Guido Vranken.
7099 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7100 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7101 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7103 o Major bugfixes (guard selection, backport from 0.2.7.6):
7104 - Actually look at the Guard flag when selecting a new directory
7105 guard. When we implemented the directory guard design, we
7106 accidentally started treating all relays as if they have the Guard
7107 flag during guard selection, leading to weaker anonymity and worse
7108 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7111 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7112 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7113 pointer to the previous (uninitialized) key value. The impact here
7114 should be limited to a difficult-to-trigger crash, if OpenSSL is
7115 running an engine that makes key generation failures possible, or
7116 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7117 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7120 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7121 - Fix an integer underflow bug when comparing malformed Tor
7122 versions. This bug could crash Tor when built with
7123 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7124 0.2.9.8, which were built with -ftrapv by default. In other cases
7125 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7126 on 0.0.8pre1. Found by OSS-Fuzz.
7128 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7129 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7130 zero size. Check size argument to memwipe() for underflow. Fixes
7131 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7134 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7135 - Make Tor survive errors involving connections without a
7136 corresponding event object. Previously we'd fail with an
7137 assertion; now we produce a log message. Related to bug 16248.
7139 o Minor features (geoip):
7140 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7143 o Minor bugfixes (compilation, backport from 0.2.7.6):
7144 - Fix a compilation warning with Clang 3.6: Do not check the
7145 presence of an address which can never be NULL. Fixes bug 17781.
7148 Changes in version 0.2.5.13 - 2017-03-03
7149 Tor 0.2.5.13 backports a number of security fixes from later Tor
7150 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
7151 this release, if for some reason they cannot upgrade to a later
7154 Note that support for Tor 0.2.5.x is ending next year: we will not issue
7155 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
7156 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7158 o Directory authority changes (backport from 0.2.8.5-rc):
7159 - Urras is no longer a directory authority. Closes ticket 19271.
7161 o Directory authority changes (backport from 0.2.9.2-alpha):
7162 - The "Tonga" bridge authority has been retired; the new bridge
7163 authority is "Bifroest". Closes tickets 19728 and 19690.
7165 o Directory authority key updates (backport from 0.2.8.1-alpha):
7166 - Update the V3 identity key for the dannenberg directory authority:
7167 it was changed on 18 November 2015. Closes task 17906. Patch
7170 o Major features (security fixes, backport from 0.2.9.4-alpha):
7171 - Prevent a class of security bugs caused by treating the contents
7172 of a buffer chunk as if they were a NUL-terminated string. At
7173 least one such bug seems to be present in all currently used
7174 versions of Tor, and would allow an attacker to remotely crash
7175 most Tor instances, especially those compiled with extra compiler
7176 hardening. With this defense in place, such bugs can't crash Tor,
7177 though we should still fix them as they occur. Closes ticket
7178 20384 (TROVE-2016-10-001).
7180 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7181 - Fix a bug in parsing that could cause clients to read a single
7182 byte past the end of an allocated region. This bug could be used
7183 to cause hardened clients (built with --enable-expensive-hardening)
7184 to crash if they tried to visit a hostile hidden service. Non-
7185 hardened clients are only affected depending on the details of
7186 their platform's memory allocator. Fixes bug 21018; bugfix on
7187 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7188 2016-12-002 and as CVE-2016-1254.
7190 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
7191 - Stop a crash that could occur when a client running with DNSPort
7192 received a query with multiple address types, and the first
7193 address type was not supported. Found and fixed by Scott Dial.
7194 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7196 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7197 - Fix an error that could cause us to read 4 bytes before the
7198 beginning of an openssl string. This bug could be used to cause
7199 Tor to crash on systems with unusual malloc implementations, or
7200 systems with unusual hardening installed. Fixes bug 17404; bugfix
7203 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7204 - Avoid a difficult-to-trigger heap corruption attack when extending
7205 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7206 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7207 Reported by Guido Vranken.
7209 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7210 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7211 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7213 o Major bugfixes (guard selection, backport from 0.2.7.6):
7214 - Actually look at the Guard flag when selecting a new directory
7215 guard. When we implemented the directory guard design, we
7216 accidentally started treating all relays as if they have the Guard
7217 flag during guard selection, leading to weaker anonymity and worse
7218 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7221 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7222 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7223 pointer to the previous (uninitialized) key value. The impact here
7224 should be limited to a difficult-to-trigger crash, if OpenSSL is
7225 running an engine that makes key generation failures possible, or
7226 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7227 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7230 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7231 - Fix an integer underflow bug when comparing malformed Tor
7232 versions. This bug could crash Tor when built with
7233 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7234 0.2.9.8, which were built with -ftrapv by default. In other cases
7235 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7236 on 0.0.8pre1. Found by OSS-Fuzz.
7238 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7239 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7240 zero size. Check size argument to memwipe() for underflow. Fixes
7241 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7244 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7245 - Make Tor survive errors involving connections without a
7246 corresponding event object. Previously we'd fail with an
7247 assertion; now we produce a log message. Related to bug 16248.
7249 o Minor features (geoip):
7250 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7253 o Minor bugfixes (compilation, backport from 0.2.7.6):
7254 - Fix a compilation warning with Clang 3.6: Do not check the
7255 presence of an address which can never be NULL. Fixes bug 17781.
7257 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
7258 - Check for failures from crypto_early_init, and refuse to continue.
7259 A previous typo meant that we could keep going with an
7260 uninitialized crypto library, and would have OpenSSL initialize
7261 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7262 when implementing ticket 4900. Patch by "teor".
7264 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7265 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7266 a client authorized hidden service. Fixes bug 15823; bugfix
7270 Changes in version 0.2.4.28 - 2017-03-03
7271 Tor 0.2.4.28 backports a number of security fixes from later Tor
7272 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
7273 this release, if for some reason they cannot upgrade to a later
7276 Note that support for Tor 0.2.4.x is ending soon: we will not issue
7277 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
7278 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
7280 o Directory authority changes (backport from 0.2.8.5-rc):
7281 - Urras is no longer a directory authority. Closes ticket 19271.
7283 o Directory authority changes (backport from 0.2.9.2-alpha):
7284 - The "Tonga" bridge authority has been retired; the new bridge
7285 authority is "Bifroest". Closes tickets 19728 and 19690.
7287 o Directory authority key updates (backport from 0.2.8.1-alpha):
7288 - Update the V3 identity key for the dannenberg directory authority:
7289 it was changed on 18 November 2015. Closes task 17906. Patch
7292 o Major features (security fixes, backport from 0.2.9.4-alpha):
7293 - Prevent a class of security bugs caused by treating the contents
7294 of a buffer chunk as if they were a NUL-terminated string. At
7295 least one such bug seems to be present in all currently used
7296 versions of Tor, and would allow an attacker to remotely crash
7297 most Tor instances, especially those compiled with extra compiler
7298 hardening. With this defense in place, such bugs can't crash Tor,
7299 though we should still fix them as they occur. Closes ticket
7300 20384 (TROVE-2016-10-001).
7302 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7303 - Fix a bug in parsing that could cause clients to read a single
7304 byte past the end of an allocated region. This bug could be used
7305 to cause hardened clients (built with --enable-expensive-hardening)
7306 to crash if they tried to visit a hostile hidden service. Non-
7307 hardened clients are only affected depending on the details of
7308 their platform's memory allocator. Fixes bug 21018; bugfix on
7309 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7310 2016-12-002 and as CVE-2016-1254.
7312 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7313 - Fix an error that could cause us to read 4 bytes before the
7314 beginning of an openssl string. This bug could be used to cause
7315 Tor to crash on systems with unusual malloc implementations, or
7316 systems with unusual hardening installed. Fixes bug 17404; bugfix
7319 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7320 - Avoid a difficult-to-trigger heap corruption attack when extending
7321 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7322 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7323 Reported by Guido Vranken.
7325 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7326 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7327 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7329 o Major bugfixes (guard selection, backport from 0.2.7.6):
7330 - Actually look at the Guard flag when selecting a new directory
7331 guard. When we implemented the directory guard design, we
7332 accidentally started treating all relays as if they have the Guard
7333 flag during guard selection, leading to weaker anonymity and worse
7334 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7337 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7338 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7339 pointer to the previous (uninitialized) key value. The impact here
7340 should be limited to a difficult-to-trigger crash, if OpenSSL is
7341 running an engine that makes key generation failures possible, or
7342 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7343 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7346 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7347 - Fix an integer underflow bug when comparing malformed Tor
7348 versions. This bug could crash Tor when built with
7349 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7350 0.2.9.8, which were built with -ftrapv by default. In other cases
7351 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7352 on 0.0.8pre1. Found by OSS-Fuzz.
7354 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7355 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7356 zero size. Check size argument to memwipe() for underflow. Fixes
7357 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7360 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7361 - Make Tor survive errors involving connections without a
7362 corresponding event object. Previously we'd fail with an
7363 assertion; now we produce a log message. Related to bug 16248.
7365 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
7366 - Make it harder for attackers to overload hidden services with
7367 introductions, by blocking multiple introduction requests on the
7368 same circuit. Resolves ticket 15515.
7370 o Minor features (geoip):
7371 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7374 o Minor bugfixes (compilation, backport from 0.2.7.6):
7375 - Fix a compilation warning with Clang 3.6: Do not check the
7376 presence of an address which can never be NULL. Fixes bug 17781.
7378 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7379 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7380 a client authorized hidden service. Fixes bug 15823; bugfix
7384 Changes in version 0.3.0.4-rc - 2017-03-01
7385 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
7386 0.3.0 release series, and introduces a few reliability features to
7387 keep them from coming back.
7389 This is the first release candidate in the Tor 0.3.0 series. If we
7390 find no new bugs or regressions here, the first stable 0.3.0 release
7391 will be nearly identical to it.
7393 o Major bugfixes (bridges):
7394 - When the same bridge is configured multiple times with the same
7395 identity, but at different address:port combinations, treat those
7396 bridge instances as separate guards. This fix restores the ability
7397 of clients to configure the same bridge with multiple pluggable
7398 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
7400 o Major bugfixes (hidden service directory v3):
7401 - Stop crashing on a failed v3 hidden service descriptor lookup
7402 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
7404 o Major bugfixes (parsing):
7405 - When parsing a malformed content-length field from an HTTP
7406 message, do not read off the end of the buffer. This bug was a
7407 potential remote denial-of-service attack against Tor clients and
7408 relays. A workaround was released in October 2016, to prevent this
7409 bug from crashing Tor. This is a fix for the underlying issue,
7410 which should no longer matter (if you applied the earlier patch).
7411 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
7412 using AFL (http://lcamtuf.coredump.cx/afl/).
7413 - Fix an integer underflow bug when comparing malformed Tor
7414 versions. This bug could crash Tor when built with
7415 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7416 0.2.9.8, which were built with -ftrapv by default. In other cases
7417 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7418 on 0.0.8pre1. Found by OSS-Fuzz.
7420 o Minor feature (protocol versioning):
7421 - Add new protocol version for proposal 224. HSIntro now advertises
7422 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
7424 o Minor features (directory authorities):
7425 - Directory authorities now reject descriptors that claim to be
7426 malformed versions of Tor. Helps prevent exploitation of
7428 - Reject version numbers with components that exceed INT32_MAX.
7429 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
7430 Fixes bug 21450; bugfix on 0.0.8pre1.
7431 - Directory authorities now reject relays running versions
7432 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
7433 suffer from bug 20499 and don't keep their consensus cache
7434 up-to-date. Resolves ticket 20509.
7436 o Minor features (geoip):
7437 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7440 o Minor features (reliability, crash):
7441 - Try better to detect problems in buffers where they might grow (or
7442 think they have grown) over 2 GB in size. Diagnostic for
7445 o Minor features (testing):
7446 - During 'make test-network-all', if tor logs any warnings, ask
7447 chutney to output them. Requires a recent version of chutney with
7448 the 21572 patch. Implements 21570.
7450 o Minor bugfixes (certificate expiration time):
7451 - Avoid using link certificates that don't become valid till some
7452 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
7454 o Minor bugfixes (code correctness):
7455 - Repair a couple of (unreachable or harmless) cases of the risky
7456 comparison-by-subtraction pattern that caused bug 21278.
7457 - Remove a redundant check for the UseEntryGuards option from the
7458 options_transition_affects_guards() function. Fixes bug 21492;
7459 bugfix on 0.3.0.1-alpha.
7461 o Minor bugfixes (directory mirrors):
7462 - Allow relays to use directory mirrors without a DirPort: these
7463 relays need to be contacted over their ORPorts using a begindir
7464 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
7465 - Clarify the message logged when a remote relay is unexpectedly
7466 missing an ORPort or DirPort: users were confusing this with a
7467 local port. Fixes another case of bug 20711; bugfix
7470 o Minor bugfixes (guards):
7471 - Don't warn about a missing guard state on timeout-measurement
7472 circuits: they aren't supposed to be using guards. Fixes an
7473 instance of bug 21007; bugfix on 0.3.0.1-alpha.
7474 - Silence a BUG() warning when attempting to use a guard whose
7475 descriptor we don't know, and make this scenario less likely to
7476 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
7478 o Minor bugfixes (hidden service):
7479 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
7480 cells. Previously, we were using sizeof() on a pointer, instead of
7481 the real destination buffer. Fortunately, that value was only used
7482 to double-check that there was enough room--which was already
7483 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
7485 o Minor bugfixes (testing):
7486 - Fix Raspbian build issues related to missing socket errno in
7487 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
7489 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
7490 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
7491 - Use bash in src/test/test-network.sh. This ensures we reliably
7492 call chutney's newer tools/test-network.sh when available. Fixes
7493 bug 21562; bugfix on 0.2.9.1-alpha.
7496 - Small fixes to the fuzzing documentation. Closes ticket 21472.
7499 Changes in version 0.2.9.10 - 2017-03-01
7500 Tor 0.2.9.10 backports a security fix from later Tor release. It also
7501 includes fixes for some major issues affecting directory authorities,
7502 LibreSSL compatibility, and IPv6 correctness.
7504 The Tor 0.2.9.x release series is now marked as a long-term-support
7505 series. We intend to backport security fixes to 0.2.9.x until at
7506 least January of 2020.
7508 o Major bugfixes (directory authority, 0.3.0.3-alpha):
7509 - During voting, when marking a relay as a probable sybil, do not
7510 clear its BadExit flag: sybils can still be bad in other ways
7511 too. (We still clear the other flags.) Fixes bug 21108; bugfix
7514 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
7515 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
7516 any IPv6 addresses. Instead, only reject a port over IPv6 if the
7517 exit policy rejects that port on more than an IPv6 /16 of
7518 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
7519 which rejected a relay's own IPv6 address by default. Fixes bug
7520 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
7522 o Major bugfixes (parsing, also in 0.3.0.4-rc):
7523 - Fix an integer underflow bug when comparing malformed Tor
7524 versions. This bug could crash Tor when built with
7525 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7526 0.2.9.8, which were built with -ftrapv by default. In other cases
7527 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7528 on 0.0.8pre1. Found by OSS-Fuzz.
7530 o Minor features (directory authorities, also in 0.3.0.4-rc):
7531 - Directory authorities now reject descriptors that claim to be
7532 malformed versions of Tor. Helps prevent exploitation of
7534 - Reject version numbers with components that exceed INT32_MAX.
7535 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
7536 Fixes bug 21450; bugfix on 0.0.8pre1.
7538 o Minor features (geoip):
7539 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7542 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
7543 - Autoconf now checks to determine if OpenSSL structures are opaque,
7544 instead of explicitly checking for OpenSSL version numbers. Part
7546 - Support building with recent LibreSSL code that uses opaque
7547 structures. Closes ticket 21359.
7549 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
7550 - Repair a couple of (unreachable or harmless) cases of the risky
7551 comparison-by-subtraction pattern that caused bug 21278.
7553 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
7554 - The tor-resolve command line tool now rejects hostnames over 255
7555 characters in length. Previously, it would silently truncate them,
7556 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
7557 Patch by "junglefowl".
7560 Changes in version 0.3.0.3-alpha - 2017-02-03
7561 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
7562 0.3.0.x development series, including some that could cause
7563 authorities to behave badly. There is also a fix for a longstanding
7564 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
7565 includes some smaller features and bugfixes.
7567 The Tor 0.3.0.x release series is now in patch-freeze: no additional
7568 features will be considered for inclusion in 0.3.0.x. We suspect that
7569 some bugs will probably remain, however, and we encourage people to
7572 o Major bugfixes (directory authority):
7573 - During voting, when marking a relay as a probable sybil, do not
7574 clear its BadExit flag: sybils can still be bad in other ways
7575 too. (We still clear the other flags.) Fixes bug 21108; bugfix
7577 - When deciding whether we have just found a router to be reachable,
7578 do not penalize it for not having performed an Ed25519 link
7579 handshake if it does not claim to support an Ed25519 handshake.
7580 Previously, we would treat such relays as non-running. Fixes bug
7581 21107; bugfix on 0.3.0.1-alpha.
7583 o Major bugfixes (entry guards):
7584 - Stop trying to build circuits through entry guards for which we
7585 have no descriptor. Also, stop crashing in the case that we *do*
7586 accidentally try to build a circuit in such a state. Fixes bug
7587 21242; bugfix on 0.3.0.1-alpha.
7589 o Major bugfixes (IPv6 Exits):
7590 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
7591 any IPv6 addresses. Instead, only reject a port over IPv6 if the
7592 exit policy rejects that port on more than an IPv6 /16 of
7593 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
7594 which rejected a relay's own IPv6 address by default. Fixes bug
7595 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
7597 o Minor feature (client):
7598 - Enable IPv6 traffic on the SocksPort by default. To disable this,
7599 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
7601 o Minor feature (fallback scripts):
7602 - Add a check_existing mode to updateFallbackDirs.py, which checks
7603 if fallbacks in the hard-coded list are working. Closes ticket
7604 20174. Patch by haxxpop.
7606 o Minor features (ciphersuite selection):
7607 - Clients now advertise a list of ciphersuites closer to the ones
7608 preferred by Firefox. Closes part of ticket 15426.
7609 - Allow relays to accept a wider range of ciphersuites, including
7610 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
7612 o Minor features (controller, configuration):
7613 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
7614 and so on, now comes with a __*Port variant that will not be saved
7615 to the torrc file by the controller's SAVECONF command. This
7616 change allows TorBrowser to set up a single-use domain socket for
7617 each time it launches Tor. Closes ticket 20956.
7618 - The GETCONF command can now query options that may only be
7619 meaningful in context-sensitive lists. This allows the controller
7620 to query the mixed SocksPort/__SocksPort style options introduced
7621 in feature 20956. Implements ticket 21300.
7623 o Minor features (portability, compilation):
7624 - Autoconf now checks to determine if OpenSSL structures are opaque,
7625 instead of explicitly checking for OpenSSL version numbers. Part
7627 - Support building with recent LibreSSL code that uses opaque
7628 structures. Closes ticket 21359.
7630 o Minor features (relay):
7631 - We now allow separation of exit and relay traffic to different
7632 source IP addresses, using the OutboundBindAddressExit and
7633 OutboundBindAddressOR options respectively. Closes ticket 17975.
7634 Written by Michael Sonntag.
7636 o Minor bugfix (logging):
7637 - Don't recommend the use of Tor2web in non-anonymous mode.
7638 Recommending Tor2web is a bad idea because the client loses all
7639 anonymity. Tor2web should only be used in specific cases by users
7640 who *know* and understand the issues. Fixes bug 21294; bugfix
7643 o Minor bugfixes (client):
7644 - Always recover from failures in extend_info_from_node(), in an
7645 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
7646 bugfix on 0.2.3.1-alpha.
7648 o Minor bugfixes (client, entry guards):
7649 - Fix a bug warning (with backtrace) when we fail a channel that
7650 circuits to fallback directories on it. Fixes bug 21128; bugfix
7652 - Fix a spurious bug warning (with backtrace) when removing an
7653 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
7654 - Fix a bug of the new guard algorithm where tor could stall for up
7655 to 10 minutes before retrying a guard after a long period of no
7656 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
7657 - Do not try to build circuits until we have descriptors for our
7658 primary entry guards. Related to fix for bug 21242.
7660 o Minor bugfixes (configure, autoconf):
7661 - Rename the configure option --enable-expensive-hardening to
7662 --enable-fragile-hardening. Expensive hardening makes the tor
7663 daemon abort when some kinds of issues are detected. Thus, it
7664 makes tor more at risk of remote crashes but safer against RCE or
7665 heartbleed bug category. We now try to explain this issue in a
7666 message from the configure script. Fixes bug 21290; bugfix
7669 o Minor bugfixes (controller):
7670 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
7671 20824; bugfix on 0.3.0.1-alpha.
7673 o Minor bugfixes (hidden service):
7674 - Clean up the code for expiring intro points with no associated
7675 circuits. It was causing, rarely, a service with some expiring
7676 introduction points to not open enough additional introduction
7677 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
7678 - Stop setting the torrc option HiddenServiceStatistics to "0" just
7679 because we're not a bridge or relay. Instead, we preserve whatever
7680 value the user set (or didn't set). Fixes bug 21150; bugfix
7682 - Resolve two possible underflows which could lead to creating and
7683 closing a lot of introduction point circuits in a non-stop loop.
7684 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
7686 o Minor bugfixes (portability):
7687 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
7688 It is supported by OpenBSD itself, and also by most OpenBSD
7689 variants (such as Bitrig). Fixes bug 20980; bugfix
7691 - When mapping a file of length greater than SIZE_MAX, do not
7692 silently truncate its contents. This issue could occur on 32 bit
7693 systems with large file support and files which are larger than 4
7694 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
7696 o Minor bugfixes (tor-resolve):
7697 - The tor-resolve command line tool now rejects hostnames over 255
7698 characters in length. Previously, it would silently truncate them,
7699 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
7700 Patch by "junglefowl".
7702 o Minor bugfixes (Windows services):
7703 - Be sure to initialize the monotonic time subsystem before using
7704 it, even when running as an NT service. Fixes bug 21356; bugfix
7708 Changes in version 0.3.0.2-alpha - 2017-01-23
7709 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
7710 cause relays and clients to crash, even if they were not built with
7711 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
7712 versions, and also affects 0.3.0.1-alpha: all relays running an affected
7713 version should upgrade.
7715 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
7716 time-to-live values, makes directory authorities enforce the 1-to-1
7717 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
7718 client-side onion service reachability bug, does better at selecting
7719 the set of fallback directories, and more.
7721 o Major bugfixes (security, also in 0.2.9.9):
7722 - Downgrade the "-ftrapv" option from "always on" to "only on when
7723 --enable-expensive-hardening is provided." This hardening option, like
7724 others, can turn survivable bugs into crashes--and having it on by
7725 default made a (relatively harmless) integer overflow bug into a
7726 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
7729 o Major features (security):
7730 - Change the algorithm used to decide DNS TTLs on client and server
7731 side, to better resist DNS-based correlation attacks like the
7732 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
7733 Feamster. Now relays only return one of two possible DNS TTL
7734 values, and clients are willing to believe DNS TTL values up to 3
7735 hours long. Closes ticket 19769.
7737 o Major features (directory authority, security):
7738 - The default for AuthDirPinKeys is now 1: directory authorities
7739 will reject relays where the RSA identity key matches a previously
7740 seen value, but the Ed25519 key has changed. Closes ticket 18319.
7742 o Major bugfixes (client, guard, crash):
7743 - In circuit_get_global_origin_list(), return the actual list of
7744 origin circuits. The previous version of this code returned the
7745 list of all the circuits, and could have caused strange bugs,
7746 including possible crashes. Fixes bug 21118; bugfix
7749 o Major bugfixes (client, onion service, also in 0.2.9.9):
7750 - Fix a client-side onion service reachability bug, where multiple
7751 socks requests to an onion service (or a single slow request)
7752 could cause us to mistakenly mark some of the service's
7753 introduction points as failed, and we cache that failure so
7754 eventually we run out and can't reach the service. Also resolves a
7755 mysterious "Remote server sent bogus reason code 65021" log
7756 warning. The bug was introduced in ticket 17218, where we tried to
7757 remember the circuit end reason as a uint16_t, which mangled
7758 negative values. Partially fixes bug 21056 and fixes bug 20307;
7759 bugfix on 0.2.8.1-alpha.
7761 o Major bugfixes (DNS):
7762 - Fix a bug that prevented exit nodes from caching DNS records for
7763 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
7765 o Minor features (controller):
7766 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
7767 shared-random values to the controller. Closes ticket 19925.
7769 o Minor features (entry guards):
7770 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
7771 break regression tests.
7772 - Require UseEntryGuards when UseBridges is set, in order to make
7773 sure bridges aren't bypassed. Resolves ticket 20502.
7775 o Minor features (fallback directories):
7776 - Select 200 fallback directories for each release. Closes
7778 - Allow 3 fallback relays per operator, which is safe now that we
7779 are choosing 200 fallback relays. Closes ticket 20912.
7780 - Exclude relays affected by bug 20499 from the fallback list.
7781 Exclude relays from the fallback list if they are running versions
7782 known to be affected by bug 20499, or if in our tests they deliver
7783 a stale consensus (i.e. one that expired more than 24 hours ago).
7784 Closes ticket 20539.
7785 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
7787 - Require fallback directories to have the same address and port for
7788 7 days (now that we have enough relays with this stability).
7789 Relays whose OnionOO stability timer is reset on restart by bug
7790 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
7791 this issue. Closes ticket 20880; maintains short-term fix
7793 - Require fallbacks to have flags for 90% of the time (weighted
7794 decaying average), rather than 95%. This allows at least 73% of
7795 clients to bootstrap in the first 5 seconds without contacting an
7796 authority. Part of ticket 18828.
7797 - Annotate updateFallbackDirs.py with the bandwidth and consensus
7798 weight for each candidate fallback. Closes ticket 20878.
7799 - Make it easier to change the output sort order of fallbacks.
7800 Closes ticket 20822.
7801 - Display the relay fingerprint when downloading consensuses from
7802 fallbacks. Closes ticket 20908.
7804 o Minor features (geoip, also in 0.2.9.9):
7805 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
7808 o Minor features (next-gen onion service directories):
7809 - Remove the "EnableOnionServicesV3" consensus parameter that we
7810 introduced in 0.3.0.1-alpha: relays are now always willing to act
7811 as v3 onion service directories. Resolves ticket 19899.
7813 o Minor features (linting):
7814 - Enhance the changes file linter to warn on Tor versions that are
7815 prefixed with "tor-". Closes ticket 21096.
7817 o Minor features (logging):
7818 - In several places, describe unset ed25519 keys as "<unset>",
7819 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
7821 o Minor bugfix (control protocol):
7822 - The reply to a "GETINFO config/names" request via the control
7823 protocol now spells the type "Dependent" correctly. This is a
7824 breaking change in the control protocol. (The field seems to be
7825 ignored by the most common known controllers.) Fixes bug 18146;
7826 bugfix on 0.1.1.4-alpha.
7828 o Minor bugfixes (bug resilience):
7829 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
7830 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
7831 Hans Jerry Illikainen.
7833 o Minor bugfixes (build):
7834 - Replace obsolete Autoconf macros with their modern equivalent and
7835 prevent similar issues in the future. Fixes bug 20990; bugfix
7838 o Minor bugfixes (client, guards):
7839 - Fix bug where Tor would think that there are circuits waiting for
7840 better guards even though those circuits have been freed. Fixes
7841 bug 21142; bugfix on 0.3.0.1-alpha.
7843 o Minor bugfixes (config):
7844 - Don't assert on startup when trying to get the options list and
7845 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
7846 options so of course they aren't ready yet. Fixes bug 21062;
7847 bugfix on 0.2.9.3-alpha.
7849 o Minor bugfixes (controller):
7850 - Make the GETINFO interface for inquiring about entry guards
7851 support the new guards backend. Fixes bug 20823; bugfix
7854 o Minor bugfixes (dead code):
7855 - Remove a redundant check for PidFile changes at runtime in
7856 options_transition_allowed(): this check is already performed
7857 regardless of whether the sandbox is active. Fixes bug 21123;
7858 bugfix on 0.2.5.4-alpha.
7860 o Minor bugfixes (documentation):
7861 - Update the tor manual page to document every option that can not
7862 be changed while tor is running. Fixes bug 21122.
7864 o Minor bugfixes (fallback directories):
7865 - Stop failing when a relay has no uptime data in
7866 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
7867 - Avoid checking fallback candidates' DirPorts if they are down in
7868 OnionOO. When a relay operator has multiple relays, this
7869 prioritizes relays that are up over relays that are down. Fixes
7870 bug 20926; bugfix on 0.2.8.3-alpha.
7871 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
7872 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
7874 o Minor bugfixes (guards, bootstrapping):
7875 - When connecting to a directory guard during bootstrap, do not mark
7876 the guard as successful until we receive a good-looking directory
7877 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
7879 o Minor bugfixes (onion services):
7880 - Fix the config reload pruning of old vs new services so it
7881 actually works when both ephemeral and non-ephemeral services are
7882 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
7883 - Allow the number of introduction points to be as low as 0, rather
7884 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
7886 o Minor bugfixes (IPv6):
7887 - Make IPv6-using clients try harder to find an IPv6 directory
7888 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
7889 - When IPv6 addresses have not been downloaded yet (microdesc
7890 consensus documents don't list relay IPv6 addresses), use hard-
7891 coded addresses for authorities, fallbacks, and configured
7892 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
7893 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
7895 o Minor bugfixes (memory leaks):
7896 - Fix a memory leak when configuring hidden services. Fixes bug
7897 20987; bugfix on 0.3.0.1-alpha.
7899 o Minor bugfixes (portability, also in 0.2.9.9):
7900 - Avoid crashing when Tor is built using headers that contain
7901 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
7902 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
7904 - Fix Libevent detection on platforms without Libevent 1 headers
7905 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
7907 o Minor bugfixes (relay):
7908 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
7909 initializing the keys would reset the DataDirectory to 0700
7910 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
7911 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
7913 o Minor bugfixes (testing):
7914 - Remove undefined behavior from the backtrace generator by removing
7915 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
7917 o Minor bugfixes (unit tests):
7918 - Allow the unit tests to pass even when DNS lookups of bogus
7919 addresses do not fail as expected. Fixes bug 20862 and 20863;
7920 bugfix on unit tests introduced in 0.2.8.1-alpha
7921 through 0.2.9.4-alpha.
7923 o Code simplification and refactoring:
7924 - Refactor code to manipulate global_origin_circuit_list into
7925 separate functions. Closes ticket 20921.
7927 o Documentation (formatting):
7928 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
7929 blocks were incorrectly appearing. Closes ticket 20885.
7931 o Documentation (man page):
7932 - Clarify many options in tor.1 and add some min/max values for
7933 HiddenService options. Closes ticket 21058.
7936 Changes in version 0.2.9.9 - 2017-01-23
7937 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
7938 cause relays and clients to crash, even if they were not built with
7939 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
7940 versions, and also affects 0.3.0.1-alpha: all relays running an affected
7941 version should upgrade.
7943 This release also resolves a client-side onion service reachability
7944 bug, and resolves a pair of small portability issues.
7946 o Major bugfixes (security):
7947 - Downgrade the "-ftrapv" option from "always on" to "only on when
7948 --enable-expensive-hardening is provided." This hardening option,
7949 like others, can turn survivable bugs into crashes -- and having
7950 it on by default made a (relatively harmless) integer overflow bug
7951 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
7952 bugfix on 0.2.9.1-alpha.
7954 o Major bugfixes (client, onion service):
7955 - Fix a client-side onion service reachability bug, where multiple
7956 socks requests to an onion service (or a single slow request)
7957 could cause us to mistakenly mark some of the service's
7958 introduction points as failed, and we cache that failure so
7959 eventually we run out and can't reach the service. Also resolves a
7960 mysterious "Remote server sent bogus reason code 65021" log
7961 warning. The bug was introduced in ticket 17218, where we tried to
7962 remember the circuit end reason as a uint16_t, which mangled
7963 negative values. Partially fixes bug 21056 and fixes bug 20307;
7964 bugfix on 0.2.8.1-alpha.
7966 o Minor features (geoip):
7967 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
7970 o Minor bugfixes (portability):
7971 - Avoid crashing when Tor is built using headers that contain
7972 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
7973 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
7975 - Fix Libevent detection on platforms without Libevent 1 headers
7976 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
7979 Changes in version 0.3.0.1-alpha - 2016-12-19
7980 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
7981 series. It strengthens Tor's link and circuit handshakes by
7982 identifying relays by their Ed25519 keys, improves the algorithm that
7983 clients use to choose and maintain their list of guards, and includes
7984 additional backend support for the next-generation hidden service
7985 design. It also contains numerous other small features and
7986 improvements to security, correctness, and performance.
7988 Below are the changes since 0.2.9.8.
7990 o Major features (guard selection algorithm):
7991 - Tor's guard selection algorithm has been redesigned from the
7992 ground up, to better support unreliable networks and restrictive
7993 sets of entry nodes, and to better resist guard-capture attacks by
7994 hostile local networks. Implements proposal 271; closes
7997 o Major features (next-generation hidden services):
7998 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
7999 prop224 aka "Next Generation Hidden Services". Service and clients
8000 don't use this functionality yet. Closes ticket 19043. Based on
8001 initial code by Alec Heifetz.
8002 - Relays now support the HSDir version 3 protocol, so that they can
8003 can store and serve v3 descriptors. This is part of the next-
8004 generation onion service work detailed in proposal 224. Closes
8007 o Major features (protocol, ed25519 identity keys):
8008 - Relays now use Ed25519 to prove their Ed25519 identities and to
8009 one another, and to clients. This algorithm is faster and more
8010 secure than the RSA-based handshake we've been doing until now.
8011 Implements the second big part of proposal 220; Closes
8013 - Clients now support including Ed25519 identity keys in the EXTEND2
8014 cells they generate. By default, this is controlled by a consensus
8015 parameter, currently disabled. You can turn this feature on for
8016 testing by setting ExtendByEd25519ID in your configuration. This
8017 might make your traffic appear different than the traffic
8018 generated by other users, however. Implements part of ticket
8019 15056; part of proposal 220.
8020 - Relays now understand requests to extend to other relays by their
8021 Ed25519 identity keys. When an Ed25519 identity key is included in
8022 an EXTEND2 cell, the relay will only extend the circuit if the
8023 other relay can prove ownership of that identity. Implements part
8024 of ticket 15056; part of proposal 220.
8026 o Major bugfixes (scheduler):
8027 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
8028 caused the channel scheduler to behave more or less randomly,
8029 rather than preferring channels with higher-priority circuits.
8030 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
8032 o Minor features (controller):
8033 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
8034 rather than "unrecognized." Closes ticket 20389; patch from
8037 o Minor features (diagnostic, directory client):
8038 - Warn when we find an unexpected inconsistency in directory
8039 download status objects. Prevents some negative consequences of
8042 o Minor features (directory authority):
8043 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
8044 default) to control whether authorities should try to probe relays
8045 by their Ed25519 link keys. This option will go away in a few
8046 releases--unless we encounter major trouble in our ed25519 link
8047 protocol rollout, in which case it will serve as a safety option.
8049 o Minor features (directory cache):
8050 - Relays and bridges will now refuse to serve the consensus they
8051 have if they know it is too old for a client to use. Closes
8054 o Minor features (ed25519 link handshake):
8055 - Advertise support for the ed25519 link handshake using the
8056 subprotocol-versions mechanism, so that clients can tell which
8057 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
8059 o Minor features (fingerprinting resistance, authentication):
8060 - Extend the length of RSA keys used for TLS link authentication to
8061 2048 bits. (These weren't used for forward secrecy; for forward
8062 secrecy, we used P256.) Closes ticket 13752.
8064 o Minor features (infrastructure):
8065 - Implement smartlist_add_strdup() function. Replaces the use of
8066 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
8068 o Minor bugfixes (client):
8069 - When clients that use bridges start up with a cached consensus on
8070 disk, they were ignoring it and downloading a new one. Now they
8071 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
8073 o Minor bugfixes (configuration):
8074 - Accept non-space whitespace characters after the severity level in
8075 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
8076 - Support "TByte" and "TBytes" units in options given in bytes.
8077 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
8078 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
8080 o Minor bugfixes (consensus weight):
8081 - Add new consensus method that initializes bw weights to 1 instead
8082 of 0. This prevents a zero weight from making it all the way to
8083 the end (happens in small testing networks) and causing an error.
8084 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
8086 o Minor bugfixes (descriptors):
8087 - Correctly recognise downloaded full descriptors as valid, even
8088 when using microdescriptors as circuits. This affects clients with
8089 FetchUselessDescriptors set, and may affect directory authorities.
8090 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
8092 o Minor bugfixes (directory system):
8093 - Download all consensus flavors, descriptors, and authority
8094 certificates when FetchUselessDescriptors is set, regardless of
8095 whether tor is a directory cache or not. Fixes bug 20667; bugfix
8096 on all recent tor versions.
8097 - Bridges and relays now use microdescriptors (like clients do)
8098 rather than old-style router descriptors. Now bridges will blend
8099 in with clients in terms of the circuits they build. Fixes bug
8100 6769; bugfix on 0.2.3.2-alpha.
8102 o Minor bugfixes (ed25519 certificates):
8103 - Correctly interpret ed25519 certificates that would expire some
8104 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
8106 o Minor bugfixes (hidden services):
8107 - Stop ignoring misconfigured hidden services. Instead, refuse to
8108 start tor until the misconfigurations have been corrected. Fixes
8109 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
8112 o Minor bugfixes (memory leak at exit):
8113 - Fix a small harmless memory leak at exit of the previously unused
8114 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
8117 o Minor bugfixes (util):
8118 - When finishing writing a file to disk, if we were about to replace
8119 the file with the temporary file created before and we fail to
8120 replace it, remove the temporary file so it doesn't stay on disk.
8121 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
8123 o Minor bugfixes (Windows):
8124 - Check for getpagesize before using it to mmap files. This fixes
8125 compilation in some MinGW environments. Fixes bug 20530; bugfix on
8126 0.1.2.1-alpha. Reported by "ice".
8128 o Code simplification and refactoring:
8129 - Abolish all global guard context in entrynodes.c; replace with new
8130 guard_selection_t structure as preparation for proposal 271.
8131 Closes ticket 19858.
8132 - Introduce rend_service_is_ephemeral() that tells if given onion
8133 service is ephemeral. Replace unclear NULL-checkings for service
8134 directory with this function. Closes ticket 20526.
8135 - Extract magic numbers in circuituse.c into defined variables.
8136 - Refactor circuit_is_available_for_use to remove unnecessary check.
8137 - Refactor circuit_predict_and_launch_new for readability and
8138 testability. Closes ticket 18873.
8139 - Refactor large if statement in purpose_needs_anonymity to use
8140 switch statement instead. Closes part of ticket 20077.
8141 - Refactor the hashing API to return negative values for errors, as
8142 is done as throughout the codebase. Closes ticket 20717.
8143 - Remove data structures that were used to index or_connection
8144 objects by their RSA identity digests. These structures are fully
8145 redundant with the similar structures used in the
8146 channel abstraction.
8147 - Remove duplicate code in the channel_write_*cell() functions.
8148 Closes ticket 13827; patch from Pingl.
8149 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
8150 use only purpose_needs_anonymity. Closes part of ticket 20077.
8151 - The code to generate and parse EXTEND and EXTEND2 cells has been
8152 replaced with code automatically generated by the
8156 - Include the "TBits" unit in Tor's man page. Fixes part of bug
8157 20622; bugfix on 0.2.5.1-alpha.
8158 - Change '1' to 'weight_scale' in consensus bw weights calculation
8159 comments, as that is reality. Closes ticket 20273. Patch
8161 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
8162 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
8164 - Stop the man page from incorrectly stating that HiddenServiceDir
8165 must already exist. Fixes 20486.
8166 - Clarify that when ClientRejectInternalAddresses is enabled (which
8167 is the default), multicast DNS hostnames for machines on the local
8168 network (of the form *.local) are also rejected. Closes
8172 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
8173 limit for relays running on a single IP applies to authority IP
8174 addresses as well as to non-authority IP addresses. Closes
8176 - The UseDirectoryGuards torrc option no longer exists: all users
8177 that use entry guards will also use directory guards. Related to
8178 proposal 271; implements part of ticket 20831.
8181 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
8182 from "overcaffeinated".
8183 - Perform the coding style checks when running the tests and fail
8184 when coding style violations are found. Closes ticket 5500.
8185 - Add tests for networkstatus_compute_bw_weights_v10.
8186 - Add unit tests circuit_predict_and_launch_new.
8187 - Extract dummy_origin_circuit_new so it can be used by other
8191 Changes in version 0.2.8.12 - 2016-12-19
8192 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
8193 below) where Tor clients could crash when attempting to visit a
8194 hostile hidden service. Clients are recommended to upgrade as packages
8195 become available for their systems.
8197 It also includes an updated list of fallback directories, backported
8200 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
8201 backported to 0.2.8 in the future.
8203 o Major bugfixes (parsing, security, backported from 0.2.9.8):
8204 - Fix a bug in parsing that could cause clients to read a single
8205 byte past the end of an allocated region. This bug could be used
8206 to cause hardened clients (built with --enable-expensive-hardening)
8207 to crash if they tried to visit a hostile hidden service. Non-
8208 hardened clients are only affected depending on the details of
8209 their platform's memory allocator. Fixes bug 21018; bugfix on
8210 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8211 2016-12-002 and as CVE-2016-1254.
8213 o Minor features (fallback directory list, backported from 0.2.9.8):
8214 - Replace the 81 remaining fallbacks of the 100 originally
8215 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
8216 fallbacks (123 new, 54 existing, 27 removed) generated in December
8217 2016. Resolves ticket 20170.
8219 o Minor features (geoip, backported from 0.2.9.7-rc):
8220 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
8224 Changes in version 0.2.9.8 - 2016-12-19
8225 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
8227 The Tor 0.2.9 series makes mandatory a number of security features
8228 that were formerly optional. It includes support for a new shared-
8229 randomness protocol that will form the basis for next generation
8230 hidden services, includes a single-hop hidden service mode for
8231 optimizing .onion services that don't actually want to be hidden,
8232 tries harder not to overload the directory authorities with excessive
8233 downloads, and supports a better protocol versioning scheme for
8234 improved compatibility with other implementations of the Tor protocol.
8236 And of course, there are numerous other bugfixes and improvements.
8238 This release also includes a fix for a medium-severity issue (bug
8239 21018 below) where Tor clients could crash when attempting to visit a
8240 hostile hidden service. Clients are recommended to upgrade as packages
8241 become available for their systems.
8243 Below are the changes since 0.2.9.7-rc. For a list of all changes
8244 since 0.2.8, see the ReleaseNotes file.
8246 o Major bugfixes (parsing, security):
8247 - Fix a bug in parsing that could cause clients to read a single
8248 byte past the end of an allocated region. This bug could be used
8249 to cause hardened clients (built with --enable-expensive-hardening)
8250 to crash if they tried to visit a hostile hidden service. Non-
8251 hardened clients are only affected depending on the details of
8252 their platform's memory allocator. Fixes bug 21018; bugfix on
8253 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8254 2016-12-002 and as CVE-2016-1254.
8256 o Minor features (fallback directory list):
8257 - Replace the 81 remaining fallbacks of the 100 originally
8258 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
8259 fallbacks (123 new, 54 existing, 27 removed) generated in December
8260 2016. Resolves ticket 20170.
8263 Changes in version 0.2.9.7-rc - 2016-12-12
8264 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
8265 including a few that had prevented tests from passing on
8268 o Minor features (geoip):
8269 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
8272 o Minor bugfix (build):
8273 - The current Git revision when building from a local repository is
8274 now detected correctly when using git worktrees. Fixes bug 20492;
8275 bugfix on 0.2.3.9-alpha.
8277 o Minor bugfixes (directory authority):
8278 - When computing old Tor protocol line version in protover, we were
8279 looking at 0.2.7.5 twice instead of a specific case for
8280 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
8282 o Minor bugfixes (download scheduling):
8283 - Resolve a "bug" warning when considering a download schedule whose
8284 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
8286 o Minor bugfixes (logging):
8287 - Downgrade a harmless log message about the
8288 pending_entry_connections list from "warn" to "info". Mitigates
8291 o Minor bugfixes (memory leak):
8292 - Fix a small memory leak when receiving AF_UNIX connections on a
8293 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
8294 - When moving a signed descriptor object from a source to an
8295 existing destination, free the allocated memory inside that
8296 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
8298 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
8299 - Fix a memory leak and use-after-free error when removing entries
8300 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
8301 0.2.5.5-alpha. Patch from "cypherpunks".
8303 o Minor bugfixes (portability):
8304 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
8305 Fixes bug 20935; bugfix on 0.2.9.6-rc.
8307 o Minor bugfixes (unit tests):
8308 - Stop expecting NetBSD unit tests to report success for ipfw. Part
8309 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
8310 - Fix tolerances in unit tests for monotonic time comparisons
8311 between nanoseconds and microseconds. Previously, we accepted a 10
8312 us difference only, which is not realistic on every platform's
8313 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
8314 - Remove a double-free in the single onion service unit test. Stop
8315 ignoring a return value. Make future changes less error-prone.
8316 Fixes bug 20864; bugfix on 0.2.9.6-rc.
8319 Changes in version 0.2.8.11 - 2016-12-08
8320 Tor 0.2.8.11 backports fixes for additional portability issues that
8321 could prevent Tor from building correctly on OSX Sierra, or with
8322 OpenSSL 1.1. Affected users should upgrade; others can safely stay
8325 o Minor bugfixes (portability):
8326 - Avoid compilation errors when building on OSX Sierra. Sierra began
8327 to support the getentropy() and clock_gettime() APIs, but created
8328 a few problems in doing so. Tor 0.2.9 has a more thorough set of
8329 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
8330 monotonic time interfaces. Fixes bug 20865. Bugfix
8333 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
8334 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
8335 architectures. Closes ticket 20588.
8338 Changes in version 0.2.8.10 - 2016-12-02
8339 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
8340 unusable after they left standby mode. It also backports fixes for
8341 a few portability issues and a small but problematic memory leak.
8343 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
8344 - When Tor leaves standby because of a new application request, open
8345 circuits as needed to serve that request. Previously, we would
8346 potentially wait a very long time. Fixes part of bug 19969; bugfix
8349 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
8350 - Clients now respond to new application stream requests immediately
8351 when they arrive, rather than waiting up to one second before
8352 starting to handle them. Fixes part of bug 19969; bugfix
8355 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
8356 - Work around a bug in the OSX 10.12 SDK that would prevent us from
8357 successfully targeting earlier versions of OSX. Resolves
8360 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
8361 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
8362 20551; bugfix on 0.2.1.1-alpha.
8364 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
8365 - Work around a memory leak in OpenSSL 1.1 when encoding public
8366 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
8368 o Minor features (geoip):
8369 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
8372 Changes in version 0.2.9.6-rc - 2016-12-02
8373 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
8374 version. We hope that it will be ready to become stable soon, and we
8375 encourage everyone to test this release. If no showstopper bugs are
8376 found here, the next 0.2.9 release will be stable.
8378 o Major bugfixes (relay, resolver, logging):
8379 - For relays that don't know their own address, avoid attempting a
8380 local hostname resolve for each descriptor we download. This
8381 will cut down on the number of "Success: chose address 'x.x.x.x'"
8382 log lines, and also avoid confusing clock jumps if the resolver
8383 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
8385 o Minor bugfixes (client, fascistfirewall):
8386 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
8387 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
8389 o Minor bugfixes (hidden services):
8390 - Stop ignoring the anonymity status of saved keys for hidden
8391 services and single onion services when first starting tor.
8392 Instead, refuse to start tor if any hidden service key has been
8393 used in a different hidden service anonymity mode. Fixes bug
8394 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
8396 o Minor bugfixes (portability):
8397 - Work around a bug in the OSX 10.12 SDK that would prevent us from
8398 successfully targeting earlier versions of OSX. Resolves
8400 - Run correctly when built on Windows build environments that
8401 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
8403 o Minor bugfixes (single onion services, Tor2web):
8404 - Stop complaining about long-term one-hop circuits deliberately
8405 created by single onion services and Tor2web. These log messages
8406 are intended to diagnose issue 8387, which relates to circuits
8407 hanging around forever for no reason. Fixes bug 20613; bugfix on
8408 0.2.9.1-alpha. Reported by "pastly".
8410 o Minor bugfixes (unit tests):
8411 - Stop spurious failures in the local interface address discovery
8412 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
8416 - Correct the minimum bandwidth value in torrc.sample, and queue a
8417 corresponding change for torrc.minimal. Closes ticket 20085.
8420 Changes in version 0.2.9.5-alpha - 2016-11-08
8421 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
8422 version. We believe one or two probably remain, and we encourage
8423 everyone to test this release.
8425 o Major bugfixes (client performance):
8426 - Clients now respond to new application stream requests immediately
8427 when they arrive, rather than waiting up to one second before
8428 starting to handle them. Fixes part of bug 19969; bugfix
8431 o Major bugfixes (client reliability):
8432 - When Tor leaves standby because of a new application request, open
8433 circuits as needed to serve that request. Previously, we would
8434 potentially wait a very long time. Fixes part of bug 19969; bugfix
8437 o Major bugfixes (download scheduling):
8438 - When using an exponential backoff schedule, do not give up on
8439 downloading just because we have failed a bunch of times. Since
8440 each delay is longer than the last, retrying indefinitely won't
8441 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
8442 - If a consensus expires while we are waiting for certificates to
8443 download, stop waiting for certificates.
8444 - If we stop waiting for certificates less than a minute after we
8445 started downloading them, do not consider the certificate download
8446 failure a separate failure. Fixes bug 20533; bugfix
8448 - Remove the maximum delay on exponential-backoff scheduling. Since
8449 we now allow an infinite number of failures (see ticket 20536), we
8450 must now allow the time to grow longer on each failure. Fixes part
8451 of bug 20534; bugfix on 0.2.9.1-alpha.
8452 - Make our initial download delays closer to those from 0.2.8. Fixes
8453 another part of bug 20534; bugfix on 0.2.9.1-alpha.
8454 - When determining when to download a directory object, handle times
8455 after 2038 if the operating system supports them. (Someday this
8456 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
8457 - When using exponential backoff in test networks, use a lower
8458 exponent, so the delays do not vary as much. This helps test
8459 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
8461 o Minor features (geoip):
8462 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
8465 o Minor bugfixes (client directory scheduling):
8466 - Treat "relay too busy to answer request" as a failed request and a
8467 reason to back off on our retry frequency. This is safe now that
8468 exponential backoffs retry indefinitely, and avoids a bug where we
8469 would reset our download schedule erroneously. Fixes bug 20593;
8470 bugfix on 0.2.9.1-alpha.
8472 o Minor bugfixes (client, logging):
8473 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
8474 assume all nodes support EXTEND2. Use ntor whenever a key is
8475 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
8476 - On DNSPort, stop logging a BUG warning on a failed hostname
8477 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
8479 o Minor bugfixes (hidden services):
8480 - When configuring hidden services, check every hidden service
8481 directory's permissions. Previously, we only checked the last
8482 hidden service. Fixes bug 20529; bugfix the work to fix 13942
8485 o Minor bugfixes (portability):
8486 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
8487 architectures. Closes ticket 20588.
8488 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
8489 removed the ECDH ciphers which caused the tests to fail on
8490 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
8491 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
8492 20551; bugfix on 0.2.1.1-alpha.
8494 o Minor bugfixes (relay bootstrap):
8495 - Ensure relays don't make multiple connections during bootstrap.
8496 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
8498 o Minor bugfixes (relay):
8499 - Work around a memory leak in OpenSSL 1.1 when encoding public
8500 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
8501 - Avoid a small memory leak when informing worker threads about
8502 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
8503 - Do not try to parallelize workers more than 16x without the user
8504 explicitly configuring us to do so, even if we do detect more than
8505 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
8507 o Minor bugfixes (single onion services):
8508 - Start correctly when creating a single onion service in a
8509 directory that did not previously exist. Fixes bug 20484; bugfix
8512 o Minor bugfixes (testing):
8513 - Avoid a unit test failure on systems with over 16 detectable CPU
8514 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
8517 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
8518 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
8519 - Module-level documentation for several more modules. Closes
8520 tickets 19287 and 19290.
8523 Changes in version 0.2.8.9 - 2016-10-17
8524 Tor 0.2.8.9 backports a fix for a security hole in previous versions
8525 of Tor that would allow a remote attacker to crash a Tor client,
8526 hidden service, relay, or authority. All Tor users should upgrade to
8527 this version, or to 0.2.9.4-alpha. Patches will be released for older
8530 o Major features (security fixes, also in 0.2.9.4-alpha):
8531 - Prevent a class of security bugs caused by treating the contents
8532 of a buffer chunk as if they were a NUL-terminated string. At
8533 least one such bug seems to be present in all currently used
8534 versions of Tor, and would allow an attacker to remotely crash
8535 most Tor instances, especially those compiled with extra compiler
8536 hardening. With this defense in place, such bugs can't crash Tor,
8537 though we should still fix them as they occur. Closes ticket
8538 20384 (TROVE-2016-10-001).
8540 o Minor features (geoip):
8541 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
8545 Changes in version 0.2.9.4-alpha - 2016-10-17
8546 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
8547 that would allow a remote attacker to crash a Tor client, hidden
8548 service, relay, or authority. All Tor users should upgrade to this
8549 version, or to 0.2.8.9. Patches will be released for older versions
8552 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
8553 previous versions of Tor, including the implementation of a feature to
8554 future- proof the Tor ecosystem against protocol changes, some bug
8555 fixes necessary for Tor Browser to use unix domain sockets correctly,
8556 and several portability improvements. We anticipate that this will be
8557 the last alpha in the Tor 0.2.9 series, and that the next release will
8558 be a release candidate.
8560 o Major features (security fixes):
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 Major features (subprotocol versions):
8571 - Tor directory authorities now vote on a set of recommended
8572 subprotocol versions, and on a set of required subprotocol
8573 versions. Clients and relays that lack support for a _required_
8574 subprotocol version will not start; those that lack support for a
8575 _recommended_ subprotocol version will warn the user to upgrade.
8576 Closes ticket 19958; implements part of proposal 264.
8577 - Tor now uses "subprotocol versions" to indicate compatibility.
8578 Previously, versions of Tor looked at the declared Tor version of
8579 a relay to tell whether they could use a given feature. Now, they
8580 should be able to rely on its declared subprotocol versions. This
8581 change allows compatible implementations of the Tor protocol(s) to
8582 exist without pretending to be 100% bug-compatible with particular
8583 releases of Tor itself. Closes ticket 19958; implements part of
8586 o Minor feature (fallback directories):
8587 - Remove broken fallbacks from the hard-coded fallback directory
8588 list. Closes ticket 20190; patch by teor.
8590 o Minor features (client, directory):
8591 - Since authorities now omit all routers that lack the Running and
8592 Valid flags, we assume that any relay listed in the consensus must
8593 have those flags. Closes ticket 20001; implements part of
8596 o Minor features (compilation, portability):
8597 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
8600 o Minor features (development tools, etags):
8601 - Teach the "make tags" Makefile target how to correctly find
8602 "MOCK_IMPL" function definitions. Patch from nherring; closes
8605 o Minor features (geoip):
8606 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
8609 o Minor features (unix domain sockets):
8610 - When configuring a unix domain socket for a SocksPort,
8611 ControlPort, or Hidden service, you can now wrap the address in
8612 quotes, using C-style escapes inside the quotes. This allows unix
8613 domain socket paths to contain spaces.
8615 o Minor features (virtual addresses):
8616 - Increase the maximum number of bits for the IPv6 virtual network
8617 prefix from 16 to 104. In this way, the condition for address
8618 allocation is less restrictive. Closes ticket 20151; feature
8621 o Minor bugfixes (address discovery):
8622 - Stop reordering IP addresses returned by the OS. This makes it
8623 more likely that Tor will guess the same relay IP address every
8624 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
8625 Reported by René Mayrhofer, patch by "cypherpunks".
8627 o Minor bugfixes (client, unix domain sockets):
8628 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
8629 the client address is meaningless. Fixes bug 20261; bugfix
8632 o Minor bugfixes (compilation, OpenBSD):
8633 - Detect Libevent2 functions correctly on systems that provide
8634 libevent2, but where libevent1 is linked with -levent. Fixes bug
8635 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
8637 o Minor bugfixes (configuration):
8638 - When parsing quoted configuration values from the torrc file,
8639 handle windows line endings correctly. Fixes bug 19167; bugfix on
8640 0.2.0.16-alpha. Patch from "Pingl".
8642 o Minor bugfixes (getpass):
8643 - Defensively fix a non-triggerable heap corruption at do_getpass()
8644 to protect ourselves from mistakes in the future. Fixes bug
8645 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
8648 o Minor bugfixes (hidden service):
8649 - Allow hidden services to run on IPv6 addresses even when the
8650 IPv6Exit option is not set. Fixes bug 18357; bugfix
8654 - Add module-level internal documentation for 36 C files that
8655 previously didn't have a high-level overview. Closes ticket #20385.
8657 o Required libraries:
8658 - When building with OpenSSL, Tor now requires version 1.0.1 or
8659 later. OpenSSL 1.0.0 and earlier are no longer supported by the
8660 OpenSSL team, and should not be used. Closes ticket 20303.
8663 Changes in version 0.2.9.3-alpha - 2016-09-23
8664 Tor 0.2.9.3-alpha adds improved support for entities that want to make
8665 high-performance services available through the Tor .onion mechanism
8666 without themselves receiving anonymity as they host those services. It
8667 also tries harder to ensure that all steps on a circuit are using the
8668 strongest crypto possible, strengthens some TLS properties, and
8669 resolves several bugs -- including a pair of crash bugs from the 0.2.8
8670 series. Anybody running an earlier version of 0.2.9.x should upgrade.
8672 o Major bugfixes (crash, also in 0.2.8.8):
8673 - Fix a complicated crash bug that could affect Tor clients
8674 configured to use bridges when replacing a networkstatus consensus
8675 in which one of their bridges was mentioned. OpenBSD users saw
8676 more crashes here, but all platforms were potentially affected.
8677 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
8679 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
8680 - Fix a timing-dependent assertion failure that could occur when we
8681 tried to flush from a circuit after having freed its cells because
8682 of an out-of-memory condition. Fixes bug 20203; bugfix on
8683 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
8686 o Major features (circuit building, security):
8687 - Authorities, relays and clients now require ntor keys in all
8688 descriptors, for all hops (except for rare hidden service protocol
8689 cases), for all circuits, and for all other roles. Part of
8691 - Tor authorities, relays, and clients only use ntor, except for
8692 rare cases in the hidden service protocol. Part of ticket 19163.
8694 o Major features (single-hop "hidden" services):
8695 - Add experimental HiddenServiceSingleHopMode and
8696 HiddenServiceNonAnonymousMode options. When both are set to 1,
8697 every hidden service on a Tor instance becomes a non-anonymous
8698 Single Onion Service. Single Onions make one-hop (direct)
8699 connections to their introduction and renzedvous points. One-hop
8700 circuits make Single Onion servers easily locatable, but clients
8701 remain location-anonymous. This is compatible with the existing
8702 hidden service implementation, and works on the current tor
8703 network without any changes to older relays or clients. Implements
8704 proposal 260, completes ticket 17178. Patch by teor and asn.
8706 o Major features (resource management):
8707 - Tor can now notice it is about to run out of sockets, and
8708 preemptively close connections of lower priority. (This feature is
8709 off by default for now, since the current prioritizing method is
8710 yet not mature enough. You can enable it by setting
8711 "DisableOOSCheck 0", but watch out: it might close some sockets
8712 you would rather have it keep.) Closes ticket 18640.
8714 o Major bugfixes (circuit building):
8715 - Hidden service client-to-intro-point and service-to-rendezvous-
8716 point circuits use the TAP key supplied by the protocol, to avoid
8717 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
8719 o Major bugfixes (compilation, OpenBSD):
8720 - Fix a Libevent-detection bug in our autoconf script that would
8721 prevent Tor from linking successfully on OpenBSD. Patch from
8722 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
8724 o Major bugfixes (hidden services):
8725 - Clients now require hidden services to include the TAP keys for
8726 their intro points in the hidden service descriptor. This prevents
8727 an inadvertent upgrade to ntor, which a malicious hidden service
8728 could use to distinguish clients by consensus version. Fixes bug
8729 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
8731 o Minor features (security, TLS):
8732 - Servers no longer support clients that without AES ciphersuites.
8733 (3DES is no longer considered an acceptable cipher.) We believe
8734 that no such Tor clients currently exist, since Tor has required
8735 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
8737 o Minor feature (fallback directories):
8738 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
8739 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
8740 2016. Closes ticket 20190; patch by teor.
8742 o Minor features (geoip, also in 0.2.8.8):
8743 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
8746 o Minor feature (port flags):
8747 - Add new flags to the *Port options to finer control over which
8748 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
8749 and the synthetic flag OnionTrafficOnly, which is equivalent to
8750 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
8751 18693; patch by "teor".
8753 o Minor features (directory authority):
8754 - After voting, if the authorities decide that a relay is not
8755 "Valid", they no longer include it in the consensus at all. Closes
8756 ticket 20002; implements part of proposal 272.
8758 o Minor features (testing):
8759 - Disable memory protections on OpenBSD when performing our unit
8760 tests for memwipe(). The test deliberately invokes undefined
8761 behavior, and the OpenBSD protections interfere with this. Patch
8762 from "rubiate". Closes ticket 20066.
8764 o Minor features (testing, ipv6):
8765 - Add the single-onion and single-onion-ipv6 chutney targets to
8766 "make test-network-all". This requires a recent chutney version
8767 with the single onion network flavours (git c72a652 or later).
8768 Closes ticket 20072; patch by teor.
8769 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
8770 tests. Remove bridges+hs, as it's somewhat redundant. This
8771 requires a recent chutney version that supports IPv6 clients,
8772 relays, and authorities. Closes ticket 20069; patch by teor.
8774 o Minor features (Tor2web):
8775 - Make Tor2web clients respect ReachableAddresses. This feature was
8776 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
8777 0.2.8.7. Implements feature 20034. Patch by teor.
8779 o Minor features (unit tests):
8780 - We've done significant work to make the unit tests run faster.
8781 - Our link-handshake unit tests now check that when invalid
8782 handshakes fail, they fail with the error messages we expected.
8783 - Our unit testing code that captures log messages no longer
8784 prevents them from being written out if the user asked for them
8785 (by passing --debug or --info or or --notice --warn to the "test"
8786 binary). This change prevents us from missing unexpected log
8787 messages simply because we were looking for others. Related to
8789 - The unit tests now log all warning messages with the "BUG" flag.
8790 Previously, they only logged errors by default. This change will
8791 help us make our testing code more correct, and make sure that we
8792 only hit this code when we mean to. In the meantime, however,
8793 there will be more warnings in the unit test logs than before.
8794 This is preparatory work for ticket 19999.
8795 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
8796 assertion as a test failure.
8798 o Minor bug fixes (circuits):
8799 - Use the CircuitBuildTimeout option whenever
8800 LearnCircuitBuildTimeout is disabled. Previously, we would respect
8801 the option when a user disabled it, but not when it was disabled
8802 because some other option was set. Fixes bug 20073; bugfix on
8803 0.2.4.12-alpha. Patch by teor.
8805 o Minor bugfixes (allocation):
8806 - Change how we allocate memory for large chunks on buffers, to
8807 avoid a (currently impossible) integer overflow, and to waste less
8808 space when allocating unusually large chunks. Fixes bug 20081;
8809 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
8810 - Always include orconfig.h before including any other C headers.
8811 Sometimes, it includes macros that affect the behavior of the
8812 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
8813 first version to use AC_USE_SYSTEM_EXTENSIONS).
8814 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
8815 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
8816 Patch from Gisle Vanem.
8817 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
8818 They apparently require a set of annotations that we aren't
8819 currently using, and they create false positives in our pthreads
8820 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
8822 o Minor bugfixes (directory authority):
8823 - Die with a more useful error when the operator forgets to place
8824 the authority_signing_key file into the keys directory. This
8825 avoids an uninformative assert & traceback about having an invalid
8826 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
8827 - When allowing private addresses, mark Exits that only exit to
8828 private locations as such. Fixes bug 20064; bugfix
8831 o Minor bugfixes (documentation):
8832 - Document the default PathsNeededToBuildCircuits value that's used
8833 by clients when the directory authorities don't set
8834 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
8835 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
8836 - Fix manual for the User option: it takes a username, not a UID.
8837 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
8840 o Minor bugfixes (hidden services):
8841 - Stop logging intro point details to the client log on certain
8842 error conditions. Fixed as part of bug 20012; bugfix on
8843 0.2.4.8-alpha. Patch by teor.
8845 o Minor bugfixes (IPv6, testing):
8846 - Check for IPv6 correctly on Linux when running test networks.
8847 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
8849 o Minor bugfixes (Linux seccomp2 sandbox):
8850 - Add permission to run the sched_yield() and sigaltstack() system
8851 calls, in order to support versions of Tor compiled with asan or
8852 ubsan code that use these calls. Now "sandbox 1" and
8853 "--enable-expensive-hardening" should be compatible on more
8854 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
8856 o Minor bugfixes (logging):
8857 - When logging a message from the BUG() macro, be explicit about
8858 what we were asserting. Previously we were confusing what we were
8859 asserting with what the bug was. Fixes bug 20093; bugfix
8861 - When we are unable to remove the bw_accounting file, do not warn
8862 if the reason we couldn't remove it was that it didn't exist.
8863 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
8865 o Minor bugfixes (option parsing):
8866 - Count unix sockets when counting client listeners (SOCKS, Trans,
8867 NATD, and DNS). This has no user-visible behaviour changes: these
8868 options are set once, and never read. Required for correct
8869 behaviour in ticket 17178. Fixes bug 19677; bugfix on
8870 0.2.6.3-alpha. Patch by teor.
8872 o Minor bugfixes (options):
8873 - Check the consistency of UseEntryGuards and EntryNodes more
8874 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
8876 - Stop changing the configured value of UseEntryGuards on
8877 authorities and Tor2web clients. Fixes bug 20074; bugfix on
8878 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
8881 o Minor bugfixes (Tor2web):
8882 - Prevent Tor2web clients running hidden services, these services
8883 are not anonymous due to the one-hop client paths. Fixes bug
8884 19678. Patch by teor.
8886 o Minor bugfixes (unit tests):
8887 - Fix a shared-random unit test that was failing on big endian
8888 architectures due to internal representation of a integer copied
8889 to a buffer. The test is changed to take a full 32 bytes of data
8890 and use the output of a python script that make the COMMIT and
8891 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
8893 - The tor_tls_server_info_callback unit test no longer crashes when
8894 debug-level logging is turned on. Fixes bug 20041; bugfix
8898 Changes in version 0.2.8.8 - 2016-09-23
8899 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
8900 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
8901 who select public relays as their bridges.
8903 o Major bugfixes (crash):
8904 - Fix a complicated crash bug that could affect Tor clients
8905 configured to use bridges when replacing a networkstatus consensus
8906 in which one of their bridges was mentioned. OpenBSD users saw
8907 more crashes here, but all platforms were potentially affected.
8908 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
8910 o Major bugfixes (relay, OOM handler):
8911 - Fix a timing-dependent assertion failure that could occur when we
8912 tried to flush from a circuit after having freed its cells because
8913 of an out-of-memory condition. Fixes bug 20203; bugfix on
8914 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
8917 o Minor feature (fallback directories):
8918 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
8919 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
8920 2016. Closes ticket 20190; patch by teor.
8922 o Minor features (geoip):
8923 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
8927 Changes in version 0.2.9.2-alpha - 2016-08-24
8928 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
8929 several new features and bugfixes. It also includes an important
8930 authority update and an important bugfix from 0.2.8.7. Everyone who
8931 sets the ReachableAddresses option, and all bridges, are strongly
8932 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
8934 o Directory authority changes (also in 0.2.8.7):
8935 - The "Tonga" bridge authority has been retired; the new bridge
8936 authority is "Bifroest". Closes tickets 19728 and 19690.
8938 o Major bugfixes (client, security, also in 0.2.8.7):
8939 - Only use the ReachableAddresses option to restrict the first hop
8940 in a path. In earlier versions of 0.2.8.x, it would apply to
8941 every hop in the path, with a possible degradation in anonymity
8942 for anyone using an uncommon ReachableAddress setting. Fixes bug
8943 19973; bugfix on 0.2.8.2-alpha.
8945 o Major features (user interface):
8946 - Tor now supports the ability to declare options deprecated, so
8947 that we can recommend that people stop using them. Previously,
8948 this was done in an ad-hoc way. Closes ticket 19820.
8950 o Major bugfixes (directory downloads):
8951 - Avoid resetting download status for consensuses hourly, since we
8952 already have another, smarter retry mechanism. Fixes bug 8625;
8953 bugfix on 0.2.0.9-alpha.
8955 o Minor features (config):
8956 - Warn users when descriptor and port addresses are inconsistent.
8957 Mitigates bug 13953; patch by teor.
8959 o Minor features (geoip):
8960 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
8963 o Minor features (user interface):
8964 - There is a new --list-deprecated-options command-line option to
8965 list all of the deprecated options. Implemented as part of
8968 o Minor bugfixes (code style):
8969 - Fix an integer signedness conversion issue in the case conversion
8970 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
8972 o Minor bugfixes (compilation):
8973 - Build correctly on versions of libevent2 without support for
8974 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
8976 - Fix a compilation warning on GCC versions before 4.6. Our
8977 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
8978 when it is also required as an argument to the compiler pragma.
8979 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
8981 o Minor bugfixes (compilation, also in 0.2.8.7):
8982 - Remove an inappropriate "inline" in tortls.c that was causing
8983 warnings on older versions of GCC. Fixes bug 19903; bugfix
8986 o Minor bugfixes (fallback directories, also in 0.2.8.7):
8987 - Avoid logging a NULL string pointer when loading fallback
8988 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
8989 and 0.2.8.1-alpha. Report and patch by "rubiate".
8991 o Minor bugfixes (logging):
8992 - Log a more accurate message when we fail to dump a microdescriptor.
8993 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
8995 o Minor bugfixes (memory leak):
8996 - Fix a series of slow memory leaks related to parsing torrc files
8997 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
8999 o Deprecated features:
9000 - A number of DNS-cache-related sub-options for client ports are now
9001 deprecated for security reasons, and may be removed in a future
9002 version of Tor. (We believe that client-side DNS caching is a bad
9003 idea for anonymity, and you should not turn it on.) The options
9004 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
9005 UseIPv4Cache, and UseIPv6Cache.
9006 - A number of options are deprecated for security reasons, and may
9007 be removed in a future version of Tor. The options are:
9008 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
9009 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
9010 CloseHSClientCircuitsImmediatelyOnTimeout,
9011 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
9012 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
9013 UseNTorHandshake, and WarnUnsafeSocks.
9014 - The *ListenAddress options are now deprecated as unnecessary: the
9015 corresponding *Port options should be used instead. These options
9016 may someday be removed. The affected options are:
9017 ControlListenAddress, DNSListenAddress, DirListenAddress,
9018 NATDListenAddress, ORListenAddress, SocksListenAddress,
9019 and TransListenAddress.
9022 - Correct the IPv6 syntax in our documentation for the
9023 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
9026 - We no longer include the (dead, deprecated) bufferevent code in
9027 Tor. Closes ticket 19450. Based on a patch from U+039b.
9030 Changes in version 0.2.8.7 - 2016-08-24
9031 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
9032 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
9033 who sets the ReachableAddresses option, and all bridges, are strongly
9034 encouraged to upgrade.
9036 o Directory authority changes:
9037 - The "Tonga" bridge authority has been retired; the new bridge
9038 authority is "Bifroest". Closes tickets 19728 and 19690.
9040 o Major bugfixes (client, security):
9041 - Only use the ReachableAddresses option to restrict the first hop
9042 in a path. In earlier versions of 0.2.8.x, it would apply to
9043 every hop in the path, with a possible degradation in anonymity
9044 for anyone using an uncommon ReachableAddress setting. Fixes bug
9045 19973; bugfix on 0.2.8.2-alpha.
9047 o Minor features (geoip):
9048 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
9051 o Minor bugfixes (compilation):
9052 - Remove an inappropriate "inline" in tortls.c that was causing
9053 warnings on older versions of GCC. Fixes bug 19903; bugfix
9056 o Minor bugfixes (fallback directories):
9057 - Avoid logging a NULL string pointer when loading fallback
9058 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
9059 and 0.2.8.1-alpha. Report and patch by "rubiate".
9062 Changes in version 0.2.9.1-alpha - 2016-08-08
9063 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
9064 series. It improves our support for hardened builds and compiler
9065 warnings, deploys some critical infrastructure for improvements to
9066 hidden services, includes a new timing backend that we hope to use for
9067 better support for traffic padding, makes it easier for programmers to
9068 log unexpected events, and contains other small improvements to
9069 security, correctness, and performance.
9071 Below are the changes since 0.2.8.6.
9073 o New system requirements:
9074 - Tor now requires Libevent version 2.0.10-stable or later. Older
9075 versions of Libevent have less efficient backends for several
9076 platforms, and lack the DNS code that we use for our server-side
9077 DNS support. This implements ticket 19554.
9078 - Tor now requires zlib version 1.2 or later, for security,
9079 efficiency, and (eventually) gzip support. (Back when we started,
9080 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
9081 released in 2003. We recommend the latest version.)
9083 o Major features (build, hardening):
9084 - Tor now builds with -ftrapv by default on compilers that support
9085 it. This option detects signed integer overflow (which C forbids),
9086 and turns it into a hard-failure. We do not apply this option to
9087 code that needs to run in constant time to avoid side-channels;
9088 instead, we use -fwrapv in that code. Closes ticket 17983.
9089 - When --enable-expensive-hardening is selected, stop applying the
9090 clang/gcc sanitizers to code that needs to run in constant time.
9091 Although we are aware of no introduced side-channels, we are not
9092 able to prove that there are none. Related to ticket 17983.
9094 o Major features (compilation):
9095 - Our big list of extra GCC warnings is now enabled by default when
9096 building with GCC (or with anything like Clang that claims to be
9097 GCC-compatible). To make all warnings into fatal compilation
9098 errors, pass --enable-fatal-warnings to configure. Closes
9100 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
9101 turn on C and POSIX extensions. (Previously, we attempted to do
9102 this on an ad hoc basis.) Closes ticket 19139.
9104 o Major features (directory authorities, hidden services):
9105 - Directory authorities can now perform the shared randomness
9106 protocol specified by proposal 250. Using this protocol, directory
9107 authorities generate a global fresh random value every day. In the
9108 future, this value will be used by hidden services to select
9109 HSDirs. This release implements the directory authority feature;
9110 the hidden service side will be implemented in the future as part
9111 of proposal 224. Resolves ticket 16943; implements proposal 250.
9113 o Major features (downloading, random exponential backoff):
9114 - When we fail to download an object from a directory service, wait
9115 for an (exponentially increasing) randomized amount of time before
9116 retrying, rather than a fixed interval as we did before. This
9117 prevents a group of Tor instances from becoming too synchronized,
9118 or a single Tor instance from becoming too predictable, in its
9119 download schedule. Closes ticket 15942.
9121 o Major bugfixes (exit policies):
9122 - Avoid disclosing exit outbound bind addresses, configured port
9123 bind addresses, and local interface addresses in relay descriptors
9124 by default under ExitPolicyRejectPrivate. Instead, only reject
9125 these (otherwise unlisted) addresses if
9126 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
9127 0.2.7.2-alpha. Patch by teor.
9129 o Major bugfixes (hidden service client):
9130 - Allow Tor clients with appropriate controllers to work with
9131 FetchHidServDescriptors set to 0. Previously, this option also
9132 disabled descriptor cache lookup, thus breaking hidden services
9133 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
9135 o Minor features (build, hardening):
9136 - Detect and work around a libclang_rt problem that would prevent
9137 clang from finding __mulodi4() on some 32-bit platforms, and thus
9138 keep -ftrapv from linking on those systems. Closes ticket 19079.
9139 - When building on a system without runtime support for the runtime
9140 hardening options, try to log a useful warning at configuration
9141 time, rather than an incomprehensible warning at link time. If
9142 expensive hardening was requested, this warning becomes an error.
9143 Closes ticket 18895.
9145 o Minor features (code safety):
9146 - In our integer-parsing functions, ensure that maxiumum value we
9147 give is no smaller than the minimum value. Closes ticket 19063;
9150 o Minor features (controller):
9151 - Implement new GETINFO queries for all downloads that use
9152 download_status_t to schedule retries. This allows controllers to
9153 examine the schedule for pending downloads. Closes ticket 19323.
9154 - Allow controllers to configure basic client authorization on
9155 hidden services when they create them with the ADD_ONION control
9156 command. Implements ticket 15588. Patch by "special".
9157 - Fire a STATUS_SERVER controller event whenever the hibernation
9158 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
9160 o Minor features (directory authority):
9161 - Directory authorities now only give the Guard flag to a relay if
9162 they are also giving it the Stable flag. This change allows us to
9163 simplify path selection for clients. It should have minimal effect
9164 in practice, since >99% of Guards already have the Stable flag.
9165 Implements ticket 18624.
9166 - Directory authorities now write their v3-status-votes file out to
9167 disk earlier in the consensus process, so we have a record of the
9168 votes even if we abort the consensus process. Resolves
9171 o Minor features (hidden service):
9172 - Stop being so strict about the payload length of "rendezvous1"
9173 cells. We used to be locked in to the "TAP" handshake length, and
9174 now we can handle better handshakes like "ntor". Resolves
9177 o Minor features (infrastructure, time):
9178 - Tor now uses the operating system's monotonic timers (where
9179 available) for internal fine-grained timing. Previously we would
9180 look at the system clock, and then attempt to compensate for the
9181 clock running backwards. Closes ticket 18908.
9182 - Tor now includes an improved timer backend, so that we can
9183 efficiently support tens or hundreds of thousands of concurrent
9184 timers, as will be needed for some of our planned anti-traffic-
9185 analysis work. This code is based on William Ahern's "timeout.c"
9186 project, which implements a "tickless hierarchical timing wheel".
9187 Closes ticket 18365.
9189 o Minor features (logging):
9190 - Provide a more useful warning message when configured with an
9191 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
9192 - When dumping unparseable router descriptors, optionally store them
9193 in separate files, named by digest, up to a configurable size
9194 limit. You can change the size limit by setting the
9195 MaxUnparseableDescSizeToLog option, and disable this feature by
9196 setting that option to 0. Closes ticket 18322.
9197 - Add a set of macros to check nonfatal assertions, for internal
9198 use. Migrating more of our checks to these should help us avoid
9199 needless crash bugs. Closes ticket 18613.
9201 o Minor features (performance):
9202 - Changer the "optimistic data" extension from "off by default" to
9203 "on by default". The default was ordinarily overridden by a
9204 consensus option, but when clients were bootstrapping for the
9205 first time, they would not have a consensus to get the option
9206 from. Changing this default When fetching a consensus for the
9207 first time, use optimistic data. This saves a round-trip during
9208 startup. Closes ticket 18815.
9210 o Minor features (relay, usability):
9211 - When the directory authorities refuse a bad relay's descriptor,
9212 encourage the relay operator to contact us. Many relay operators
9213 won't notice this line in their logs, but it's a win if even a few
9214 learn why we don't like what their relay was doing. Resolves
9217 o Minor features (testing):
9218 - Let backtrace tests work correctly under AddressSanitizer. Fixes
9219 part of bug 18934; bugfix on 0.2.5.2-alpha.
9220 - Move the test-network.sh script to chutney, and modify tor's test-
9221 network.sh to call the (newer) chutney version when available.
9222 Resolves ticket 19116. Patch by teor.
9223 - Use the lcov convention for marking lines as unreachable, so that
9224 we don't count them when we're generating test coverage data.
9225 Update our coverage tools to understand this convention. Closes
9228 o Minor bugfixes (bootstrap):
9229 - Remember the directory we fetched the consensus or previous
9230 certificates from, and use it to fetch future authority
9231 certificates. This change improves bootstrapping performance.
9232 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
9234 o Minor bugfixes (build):
9235 - The test-stem and test-network makefile targets now depend only on
9236 the tor binary that they are testing. Previously, they depended on
9237 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
9238 patch from "cypherpunks".
9240 o Minor bugfixes (circuits):
9241 - Make sure extend_info_from_router() is only called on servers.
9242 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
9244 o Minor bugfixes (compilation):
9245 - When building with Clang, use a full set of GCC warnings.
9246 (Previously, we included only a subset, because of the way we
9247 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
9249 o Minor bugfixes (directory authority):
9250 - Authorities now sort the "package" lines in their votes, for ease
9251 of debugging. (They are already sorted in consensus documents.)
9252 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
9253 - When parsing a detached signature, make sure we use the length of
9254 the digest algorithm instead of an hardcoded DIGEST256_LEN in
9255 order to avoid comparing bytes out-of-bounds with a smaller digest
9256 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
9258 o Minor bugfixes (documentation):
9259 - Document the --passphrase-fd option in the tor manpage. Fixes bug
9260 19504; bugfix on 0.2.7.3-rc.
9261 - Fix the description of the --passphrase-fd option in the
9262 tor-gencert manpage. The option is used to pass the number of a
9263 file descriptor to read the passphrase from, not to read the file
9264 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
9266 o Minor bugfixes (ephemeral hidden service):
9267 - When deleting an ephemeral hidden service, close its intro points
9268 even if they are not completely open. Fixes bug 18604; bugfix
9271 o Minor bugfixes (guard selection):
9272 - Use a single entry guard even if the NumEntryGuards consensus
9273 parameter is not provided. Fixes bug 17688; bugfix
9275 - Don't mark guards as unreachable if connection_connect() fails.
9276 That function fails for local reasons, so it shouldn't reveal
9277 anything about the status of the guard. Fixes bug 14334; bugfix
9280 o Minor bugfixes (hidden service client):
9281 - Increase the minimum number of internal circuits we preemptively
9282 build from 2 to 3, so a circuit is available when a client
9283 connects to another onion service. Fixes bug 13239; bugfix
9286 o Minor bugfixes (logging):
9287 - When logging a directory ownership mismatch, log the owning
9288 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
9290 o Minor bugfixes (memory leaks):
9291 - Fix a small, uncommon memory leak that could occur when reading a
9292 truncated ed25519 key file. Fixes bug 18956; bugfix
9295 o Minor bugfixes (testing):
9296 - Allow clients to retry HSDirs much faster in test networks. Fixes
9297 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
9298 - Disable ASAN's detection of segmentation faults while running
9299 test_bt.sh, so that we can make sure that our own backtrace
9300 generation code works. Fixes another aspect of bug 18934; bugfix
9301 on 0.2.5.2-alpha. Patch from "cypherpunks".
9302 - Fix the test-network-all target on out-of-tree builds by using the
9303 correct path to the test driver script. Fixes bug 19421; bugfix
9306 o Minor bugfixes (time):
9307 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
9308 bugfix on all released tor versions.
9309 - When computing the difference between two times in milliseconds,
9310 we now round to the nearest millisecond correctly. Previously, we
9311 could sometimes round in the wrong direction. Fixes bug 19428;
9312 bugfix on 0.2.2.2-alpha.
9314 o Minor bugfixes (user interface):
9315 - Display a more accurate number of suppressed messages in the log
9316 rate-limiter. Previously, there was a potential integer overflow
9317 in the counter. Now, if the number of messages hits a maximum, the
9318 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
9320 - Fix a typo in the passphrase prompt for the ed25519 identity key.
9321 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
9323 o Code simplification and refactoring:
9324 - Remove redundant declarations of the MIN macro. Closes
9326 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
9327 Closes ticket 18462; patch from "icanhasaccount".
9328 - Split the 600-line directory_handle_command_get function into
9329 separate functions for different URL types. Closes ticket 16698.
9332 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
9333 ticket 19153. Patch from "U+039b".
9336 - Remove support for "GET /tor/bytes.txt" DirPort request, and
9337 "GETINFO dir-usage" controller request, which were only available
9338 via a compile-time option in Tor anyway. Feature was added in
9339 0.2.2.1-alpha. Resolves ticket 19035.
9340 - There is no longer a compile-time option to disable support for
9341 TransPort. (If you don't want TransPort; just don't use it.) Patch
9342 from "U+039b". Closes ticket 19449.
9345 - Run more workqueue tests as part of "make check". These had
9346 previously been implemented, but you needed to know special
9347 command-line options to enable them.
9348 - We now have unit tests for our code to reject zlib "compression
9349 bombs". (Fortunately, the code works fine.)
9352 Changes in version 0.2.8.6 - 2016-08-02
9354 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
9356 The Tor 0.2.8 series improves client bootstrapping performance,
9357 completes the authority-side implementation of improved identity
9358 keys for relays, and includes numerous bugfixes and performance
9359 improvements throughout the program. This release continues to
9360 improve the coverage of Tor's test suite. For a full list of
9361 changes since Tor 0.2.7, see the ReleaseNotes file.
9363 Changes since 0.2.8.5-rc:
9365 o Minor features (geoip):
9366 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
9369 o Minor bugfixes (compilation):
9370 - Fix a compilation warning in the unit tests on systems where char
9371 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
9373 o Minor bugfixes (fallback directories):
9374 - Remove 1 fallback that was on the hardcoded list, then opted-out,
9375 leaving 89 of the 100 fallbacks originally introduced in Tor
9376 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
9378 o Minor bugfixes (Linux seccomp2 sandbox):
9379 - Allow more syscalls when running with "Sandbox 1" enabled:
9380 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
9381 some systems, these are required for Tor to start. Fixes bug
9382 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
9383 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
9384 so that get_interface_address6_via_udp_socket_hack() can work.
9385 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
9388 Changes in version 0.2.8.5-rc - 2016-07-07
9389 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
9390 series. If we find no new bugs or regressions here, the first stable
9391 0.2.8 release will be identical to it. It has a few small bugfixes
9392 against previous versions.
9394 o Directory authority changes:
9395 - Urras is no longer a directory authority. Closes ticket 19271.
9397 o Major bugfixes (heartbeat):
9398 - Fix a regression that would crash Tor when the periodic
9399 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
9400 0.2.8.1-alpha. Reported by "kubaku".
9402 o Minor features (build):
9403 - Tor now again builds with the recent OpenSSL 1.1 development
9404 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
9405 - When building manual pages, set the timezone to "UTC", so that the
9406 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
9407 Patch from intrigeri.
9409 o Minor bugfixes (fallback directory selection):
9410 - Avoid errors during fallback selection if there are no eligible
9411 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
9414 o Minor bugfixes (IPv6, microdescriptors):
9415 - Don't check node addresses when we only have a routerstatus. This
9416 allows IPv6-only clients to bootstrap by fetching microdescriptors
9417 from fallback directory mirrors. (The microdescriptor consensus
9418 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
9421 o Minor bugfixes (logging):
9422 - Reduce pointlessly verbose log messages when directory servers
9423 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
9424 0.2.8.1-alpha. Patch by teor.
9425 - When a fallback directory changes its fingerprint from the hard-
9426 coded fingerprint, log a less severe, more explanatory log
9427 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
9429 o Minor bugfixes (Linux seccomp2 sandboxing):
9430 - Allow statistics to be written to disk when "Sandbox 1" is
9431 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
9432 0.2.6.1-alpha respectively.
9434 o Minor bugfixes (user interface):
9435 - Remove a warning message "Service [scrubbed] not found after
9436 descriptor upload". This message appears when one uses HSPOST
9437 control command to upload a service descriptor. Since there is
9438 only a descriptor and no service, showing this message is
9439 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
9441 o Fallback directory list:
9442 - Add a comment to the generated fallback directory list that
9443 explains how to comment out unsuitable fallbacks in a way that's
9444 compatible with the stem fallback parser.
9445 - Update fallback whitelist and blacklist based on relay operator
9446 emails. Blacklist unsuitable (non-working, over-volatile)
9447 fallbacks. Resolves ticket 19071. Patch by teor.
9448 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
9449 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
9450 ticket 19071; patch by teor.
9453 Changes in version 0.2.8.4-rc - 2016-06-15
9454 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
9455 If we find no new bugs or regressions here, the first stable 0.2.8
9456 release will be identical to it. It has a few small bugfixes against
9459 o Major bugfixes (user interface):
9460 - Correctly give a warning in the cases where a relay is specified
9461 by nickname, and one such relay is found, but it is not officially
9462 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
9464 o Minor features (build):
9465 - Tor now builds once again with the recent OpenSSL 1.1 development
9466 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
9468 o Minor features (geoip):
9469 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
9472 o Minor bugfixes (compilation):
9473 - Cause the unit tests to compile correctly on mingw64 versions that
9474 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
9476 o Minor bugfixes (downloading):
9477 - Predict more correctly whether we'll be downloading over HTTP when
9478 we determine the maximum length of a URL. This should avoid a
9479 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
9483 Changes in version 0.2.8.3-alpha - 2016-05-26
9484 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
9485 the course of the 0.2.8 development cycle. It improves the behavior of
9486 directory clients, fixes several crash bugs, fixes a gap in compiler
9487 hardening, and allows the full integration test suite to run on
9490 o Major bugfixes (security, client, DNS proxy):
9491 - Stop a crash that could occur when a client running with DNSPort
9492 received a query with multiple address types, and the first
9493 address type was not supported. Found and fixed by Scott Dial.
9494 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9496 o Major bugfixes (security, compilation):
9497 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
9498 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
9499 cause a compiler warning, thereby making other checks fail, and
9500 needlessly disabling compiler-hardening support. Fixes one case of
9501 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
9503 o Major bugfixes (security, directory authorities):
9504 - Fix a crash and out-of-bounds write during authority voting, when
9505 the list of relays includes duplicate ed25519 identity keys. Fixes
9506 bug 19032; bugfix on 0.2.8.2-alpha.
9508 o Major bugfixes (client, bootstrapping):
9509 - Check if bootstrap consensus downloads are still needed when the
9510 linked connection attaches. This prevents tor making unnecessary
9511 begindir-style connections, which are the only directory
9512 connections tor clients make since the fix for 18483 was merged.
9513 - Fix some edge cases where consensus download connections may not
9514 have been closed, even though they were not needed. Related to fix
9516 - Make relays retry consensus downloads the correct number of times,
9517 rather than the more aggressive client retry count. Fixes part of
9519 - Stop downloading consensuses when we have a consensus, even if we
9520 don't have all the certificates for it yet. Fixes bug 18809;
9521 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
9523 o Major bugfixes (directory mirrors):
9524 - Decide whether to advertise begindir support in the the same way
9525 we decide whether to advertise our DirPort. Allowing these
9526 decisions to become out-of-sync led to surprising behavior like
9527 advertising begindir support when hibernation made us not
9528 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
9531 o Major bugfixes (IPv6 bridges, client):
9532 - Actually use IPv6 addresses when selecting directory addresses for
9533 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
9536 o Major bugfixes (key management):
9537 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9538 pointer to the previous (uninitialized) key value. The impact here
9539 should be limited to a difficult-to-trigger crash, if OpenSSL is
9540 running an engine that makes key generation failures possible, or
9541 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9542 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9545 o Major bugfixes (testing):
9546 - Fix a bug that would block 'make test-network-all' on systems where
9547 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
9548 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
9549 bugfix on 0.2.8.1-alpha.
9551 o Minor features (clients):
9552 - Make clients, onion services, and bridge relays always use an
9553 encrypted begindir connection for directory requests. Resolves
9554 ticket 18483. Patch by "teor".
9556 o Minor features (fallback directory mirrors):
9557 - Give each fallback the same weight for client selection; restrict
9558 fallbacks to one per operator; report fallback directory detail
9559 changes when rebuilding list; add new fallback directory mirrors
9560 to the whitelist; and many other minor simplifications and fixes.
9561 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
9562 0.2.8.1-alpha; patch by "teor".
9563 - Replace the 21 fallbacks generated in January 2016 and included in
9564 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
9565 2016. Closes task 17158; patch by "teor".
9567 o Minor features (geoip):
9568 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
9571 o Minor bugfixes (assert, portability):
9572 - Fix an assertion failure in memarea.c on systems where "long" is
9573 shorter than the size of a pointer. Fixes bug 18716; bugfix
9576 o Minor bugfixes (bootstrap):
9577 - Consistently use the consensus download schedule for authority
9578 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
9580 o Minor bugfixes (build):
9581 - Remove a pair of redundant AM_CONDITIONAL declarations from
9582 configure.ac. Fixes one final case of bug 17744; bugfix
9584 - Resolve warnings when building on systems that are concerned with
9585 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
9587 - When libscrypt.h is found, but no libscrypt library can be linked,
9588 treat libscrypt as absent. Fixes bug 19161; bugfix
9591 o Minor bugfixes (client):
9592 - Turn all TestingClientBootstrap* into non-testing torrc options.
9593 This changes simply renames them by removing "Testing" in front of
9594 them and they do not require TestingTorNetwork to be enabled
9595 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
9596 - Make directory node selection more reliable, mainly for IPv6-only
9597 clients and clients with few reachable addresses. Fixes bug 18929;
9598 bugfix on 0.2.8.1-alpha. Patch by "teor".
9600 o Minor bugfixes (controller, microdescriptors):
9601 - Make GETINFO dir/status-vote/current/consensus conform to the
9602 control specification by returning "551 Could not open cached
9603 consensus..." when not caching consensuses. Fixes bug 18920;
9604 bugfix on 0.2.2.6-alpha.
9606 o Minor bugfixes (crypto, portability):
9607 - The SHA3 and SHAKE routines now produce the correct output on Big
9608 Endian systems. No code calls either algorithm yet, so this is
9609 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
9610 - Tor now builds again with the recent OpenSSL 1.1 development
9611 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
9614 o Minor bugfixes (directories):
9615 - When fetching extrainfo documents, compare their SHA256 digests
9616 and Ed25519 signing key certificates with the routerinfo that led
9617 us to fetch them, rather than with the most recent routerinfo.
9618 Otherwise we generate many spurious warnings about mismatches.
9619 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
9621 o Minor bugfixes (logging):
9622 - When we can't generate a signing key because OfflineMasterKey is
9623 set, do not imply that we should have been able to load it. Fixes
9624 bug 18133; bugfix on 0.2.7.2-alpha.
9625 - Stop periodic_event_dispatch() from blasting twelve lines per
9626 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
9627 - When rejecting a misformed INTRODUCE2 cell, only log at
9628 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
9630 o Minor bugfixes (pluggable transports):
9631 - Avoid reporting a spurious error when we decide that we don't need
9632 to terminate a pluggable transport because it has already exited.
9633 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
9635 o Minor bugfixes (pointer arithmetic):
9636 - Fix a bug in memarea_alloc() that could have resulted in remote
9637 heap write access, if Tor had ever passed an unchecked size to
9638 memarea_alloc(). Fortunately, all the sizes we pass to
9639 memarea_alloc() are pre-checked to be less than 128 kilobytes.
9640 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
9643 o Minor bugfixes (relays):
9644 - Consider more config options when relays decide whether to
9645 regenerate their descriptor. Fixes more of bug 12538; bugfix
9647 - Resolve some edge cases where we might launch an ORPort
9648 reachability check even when DisableNetwork is set. Noticed while
9649 fixing bug 18616; bugfix on 0.2.3.9-alpha.
9651 o Minor bugfixes (statistics):
9652 - We now include consensus downloads via IPv6 in our directory-
9653 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
9655 o Minor bugfixes (testing):
9656 - Allow directories in small networks to bootstrap by skipping
9657 DirPort checks when the consensus has no exits. Fixes bug 19003;
9658 bugfix on 0.2.8.1-alpha. Patch by teor.
9659 - Fix a small memory leak that would occur when the
9660 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
9661 bugfix on 0.2.5.2-alpha.
9663 o Minor bugfixes (time handling):
9664 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
9665 field. Otherwise, our unit tests crash on Windows. Fixes bug
9666 18977; bugfix on 0.2.2.25-alpha.
9669 - Document the contents of the 'datadir/keys' subdirectory in the
9670 manual page. Closes ticket 17621.
9671 - Stop recommending use of nicknames to identify relays in our
9672 MapAddress documentation. Closes ticket 18312.
9675 Changes in version 0.2.8.2-alpha - 2016-03-28
9676 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
9677 bugs in earlier versions of Tor, including some that prevented
9678 authorities using Tor 0.2.7.x from running correctly. IPv6 and
9679 directory support should also be much improved.
9681 o New system requirements:
9682 - Tor no longer supports versions of OpenSSL with a broken
9683 implementation of counter mode. (This bug was present in OpenSSL
9684 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
9685 longer runs with, these versions.
9686 - Tor no longer attempts to support platforms where the "time_t"
9687 type is unsigned. (To the best of our knowledge, only OpenVMS does
9688 this, and Tor has never actually built on OpenVMS.) Closes
9690 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
9691 later (released in 2008 and 2009 respectively). If you are
9692 building Tor from the git repository instead of from the source
9693 distribution, and your tools are older than this, you will need to
9694 upgrade. Closes ticket 17732.
9696 o Major bugfixes (security, pointers):
9697 - Avoid a difficult-to-trigger heap corruption attack when extending
9698 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9699 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9700 Reported by Guido Vranken.
9702 o Major bugfixes (bridges, pluggable transports):
9703 - Modify the check for OR connections to private addresses. Allow
9704 bridges on private addresses, including pluggable transports that
9705 ignore the (potentially private) address in the bridge line. Fixes
9706 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
9708 o Major bugfixes (compilation):
9709 - Repair hardened builds under the clang compiler. Previously, our
9710 use of _FORTIFY_SOURCE would conflict with clang's address
9711 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
9713 o Major bugfixes (crash on shutdown):
9714 - Correctly handle detaching circuits from muxes when shutting down.
9715 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
9716 - Fix an assert-on-exit bug related to counting memory usage in
9717 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
9719 o Major bugfixes (crash on startup):
9720 - Fix a segfault during startup: If a Unix domain socket was
9721 configured as listener (such as a ControlSocket or a SocksPort
9722 "unix:" socket), and tor was started as root but not configured to
9723 switch to another user, tor would segfault while trying to string
9724 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
9727 o Major bugfixes (dns proxy mode, crash):
9728 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9729 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9731 o Major bugfixes (relays, bridge clients):
9732 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
9733 bridge clients use the address configured in the bridge line.
9734 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
9737 o Major bugfixes (voting):
9738 - Actually enable support for authorities to match routers by their
9739 Ed25519 identities. Previously, the code had been written, but
9740 some debugging code that had accidentally been left in the
9741 codebase made it stay turned off. Fixes bug 17702; bugfix
9743 - When collating votes by Ed25519 identities, authorities now
9744 include a "NoEdConsensus" flag if the ed25519 value (or lack
9745 thereof) for a server does not reflect the majority consensus.
9746 Related to bug 17668; bugfix on 0.2.7.2-alpha.
9747 - When generating a vote with keypinning disabled, never include two
9748 entries for the same ed25519 identity. This bug was causing
9749 authorities to generate votes that they could not parse when a
9750 router violated key pinning by changing its RSA identity but
9751 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
9752 18318. Bugfix on 0.2.7.2-alpha.
9754 o Minor features (security, win32):
9755 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
9756 attack. Fixes bug 18123; bugfix on all tor versions. Patch
9759 o Minor features (bug-resistance):
9760 - Make Tor survive errors involving connections without a
9761 corresponding event object. Previously we'd fail with an
9762 assertion; now we produce a log message. Related to bug 16248.
9764 o Minor features (build):
9765 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
9766 as having possible IPFW support. Closes ticket 18448. Patch from
9769 o Minor features (code hardening):
9770 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
9771 level code, to harden against accidental failures to NUL-
9772 terminate. Part of ticket 17852. Patch from jsturgix. Found
9775 o Minor features (crypto):
9776 - Validate the hard-coded Diffie-Hellman parameters and ensure that
9777 p is a safe prime, and g is a suitable generator. Closes
9780 o Minor features (geoip):
9781 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
9784 o Minor features (hidden service directory):
9785 - Streamline relay-side hsdir handling: when relays consider whether
9786 to accept an uploaded hidden service descriptor, they no longer
9787 check whether they are one of the relays in the network that is
9788 "supposed" to handle that descriptor. Implements ticket 18332.
9790 o Minor features (IPv6):
9791 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
9792 to 1, tor prefers IPv6 directory addresses.
9793 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
9794 avoids using IPv4 for client OR and directory connections.
9795 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
9796 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
9797 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
9799 o Minor features (linux seccomp2 sandbox):
9800 - Reject attempts to change our Address with "Sandbox 1" enabled.
9801 Changing Address with Sandbox turned on would never actually work,
9802 but previously it would fail in strange and confusing ways. Found
9805 o Minor features (robustness):
9806 - Exit immediately with an error message if the code attempts to use
9807 Libevent without having initialized it. This should resolve some
9808 frequently-made mistakes in our unit tests. Closes ticket 18241.
9810 o Minor features (unix domain sockets):
9811 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
9812 Unix domain sockets without checking the permissions on the parent
9813 directory. (Tor checks permissions by default because some
9814 operating systems only check permissions on the parent directory.
9815 However, some operating systems do look at permissions on the
9816 socket, and tor's default check is unneeded.) Closes ticket 18458.
9819 o Minor bugfixes (exit policies, security):
9820 - Refresh an exit relay's exit policy when interface addresses
9821 change. Previously, tor only refreshed the exit policy when the
9822 configured external address changed. Fixes bug 18208; bugfix on
9823 0.2.7.3-rc. Patch by teor.
9825 o Minor bugfixes (security, hidden services):
9826 - Prevent hidden services connecting to client-supplied rendezvous
9827 addresses that are reserved as internal or multicast. Fixes bug
9828 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
9830 o Minor bugfixes (build):
9831 - Do not link the unit tests against both the testing and non-
9832 testing versions of the static libraries. Fixes bug 18490; bugfix
9834 - Avoid spurious failures from configure files related to calling
9835 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
9836 0.2.0.1-alpha. Patch from "cypherpunks".
9837 - Silence spurious clang-scan warnings in the ed25519_donna code by
9838 explicitly initializing some objects. Fixes bug 18384; bugfix on
9839 0.2.7.2-alpha. Patch by teor.
9841 o Minor bugfixes (client, bootstrap):
9842 - Count receipt of new microdescriptors as progress towards
9843 bootstrapping. Previously, with EntryNodes set, Tor might not
9844 successfully repopulate the guard set on bootstrapping. Fixes bug
9845 16825; bugfix on 0.2.3.1-alpha.
9847 o Minor bugfixes (code correctness):
9848 - Update to the latest version of Trunnel, which tries harder to
9849 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
9850 by clang address sanitizer. Fixes bug 18373; bugfix
9853 o Minor bugfixes (configuration):
9854 - Fix a tiny memory leak when parsing a port configuration ending in
9855 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
9857 o Minor bugfixes (containers):
9858 - If we somehow attempt to construct a heap with more than
9859 1073741822 elements, avoid an integer overflow when maintaining
9860 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
9862 o Minor bugfixes (correctness):
9863 - Fix a bad memory handling bug that would occur if we had queued a
9864 cell on a channel's incoming queue. Fortunately, we can't actually
9865 queue a cell like that as our code is constructed today, but it's
9866 best to avoid this kind of error, even if there isn't any code
9867 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
9869 o Minor bugfixes (directory):
9870 - When generating a URL for a directory server on an IPv6 address,
9871 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
9872 on 0.2.3.9-alpha. Patch from Malek.
9874 o Minor bugfixes (fallback directory mirrors):
9875 - When requesting extrainfo descriptors from a trusted directory
9876 server, check whether it is an authority or a fallback directory
9877 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
9878 0.2.4.7-alpha. Reported by atagar, patch by teor.
9880 o Minor bugfixes (hidden service, client):
9881 - Handle the case where the user makes several fast consecutive
9882 requests to the same .onion address. Previously, the first six
9883 requests would each trigger a descriptor fetch, each picking a
9884 directory (there are 6 overall) and the seventh one would fail
9885 because no directories were left, thereby triggering a close on
9886 all current directory connections asking for the hidden service.
9887 The solution here is to not close the connections if we have
9888 pending directory fetches. Fixes bug 15937; bugfix
9891 o Minor bugfixes (hidden service, control port):
9892 - Add the onion address to the HS_DESC event for the UPLOADED action
9893 both on success or failure. It was previously hardcoded with
9894 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
9896 o Minor bugfixes (hidden service, directory):
9897 - Bridges now refuse "rendezvous2" (hidden service descriptor)
9898 publish attempts. Suggested by ticket 18332.
9900 o Minor bugfixes (linux seccomp2 sandbox):
9901 - Allow the setrlimit syscall, and the prlimit and prlimit64
9902 syscalls, which some libc implementations use under the hood.
9903 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
9904 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
9905 enabled and no DNS resolvers configured. This should help TAILS
9906 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
9907 - Fix the sandbox's interoperability with unix domain sockets under
9908 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
9910 o Minor bugfixes (logging):
9911 - When logging information about an unparsable networkstatus vote or
9912 consensus, do not say "vote" when we mean consensus. Fixes bug
9913 18368; bugfix on 0.2.0.8-alpha.
9914 - Scrub service name in "unrecognized service ID" log messages.
9915 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
9916 - Downgrade logs and backtraces about IP versions to info-level.
9917 Only log backtraces once each time tor runs. Assists in diagnosing
9918 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
9919 Christian, patch by teor.
9921 o Minor bugfixes (memory safety):
9922 - Avoid freeing an uninitialized pointer when opening a socket fails
9923 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
9924 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
9926 - Correctly duplicate addresses in get_interface_address6_list().
9927 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
9928 patch by "cypherpunks".
9929 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
9931 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
9932 18672; bugfix on 0.2.5.1-alpha.
9934 o Minor bugfixes (private directory):
9935 - Prevent a race condition when creating private directories. Fixes
9936 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
9937 Patch from jsturgix. Found with Flawfinder.
9939 o Minor bugfixes (test networks, IPv6):
9940 - Allow internal IPv6 addresses in descriptors in test networks.
9941 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
9944 o Minor bugfixes (testing):
9945 - We no longer disable assertions in the unit tests when coverage is
9946 enabled. Instead, we require you to say --disable-asserts-in-tests
9947 to the configure script if you need assertions disabled in the
9948 unit tests (for example, if you want to perform branch coverage).
9949 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
9951 o Minor bugfixes (time parsing):
9952 - Avoid overflow in tor_timegm when parsing dates in and after 2038
9953 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
9954 0.0.2pre14. Patch by teor.
9956 o Minor bugfixes (tor-gencert):
9957 - Correctly handle the case where an authority operator enters a
9958 passphrase but sends an EOF before sending a newline. Fixes bug
9959 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
9961 o Code simplification and refactoring:
9962 - Quote all the string interpolations in configure.ac -- even those
9963 which we are pretty sure can't contain spaces. Closes ticket
9964 17744. Patch from zerosion.
9965 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
9966 inplace, so there's no need to have a separate implementation for
9967 the non-inplace code. Closes ticket 18258. Patch from Malek.
9968 - Simplify return types for some crypto functions that can't
9969 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
9972 - Change build messages to refer to "Fedora" instead of "Fedora
9973 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
9974 Patches from "icanhasaccount" and "cypherpunks".
9977 - We no longer maintain an internal freelist in memarea.c.
9978 Allocators should be good enough to make this code unnecessary,
9979 and it's doubtful that it ever had any performance benefit.
9982 - Fix several warnings from clang's address sanitizer produced in
9984 - Treat backtrace test failures as expected on FreeBSD until we
9985 solve bug 17808. Closes ticket 18204.
9988 Changes in version 0.2.8.1-alpha - 2016-02-04
9989 Tor 0.2.8.1-alpha is the first alpha release in its series. It
9990 includes numerous small features and bugfixes against previous Tor
9991 versions, and numerous small infrastructure improvements. The most
9992 notable features are a set of improvements to the directory subsystem.
9994 o Major features (security, Linux):
9995 - When Tor starts as root on Linux and is told to switch user ID, it
9996 can now retain the capability to bind to low ports. By default,
9997 Tor will do this only when it's switching user ID and some low
9998 ports have been configured. You can change this behavior with the
9999 new option KeepBindCapabilities. Closes ticket 8195.
10001 o Major features (directory system):
10002 - When bootstrapping multiple consensus downloads at a time, use the
10003 first one that starts downloading, and close the rest. This
10004 reduces failures when authorities or fallback directories are slow
10005 or down. Together with the code for feature 15775, this feature
10006 should reduces failures due to fallback churn. Implements ticket
10007 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
10008 "mikeperry" and "teor".
10009 - Include a trial list of 21 default fallback directories, generated
10010 in January 2016, based on an opt-in survey of suitable relays.
10011 Doing this should make clients bootstrap more quickly and reliably,
10012 and reduce the load on the directory authorities. Closes ticket
10013 15775. Patch by "teor".
10014 Candidates identified using an OnionOO script by "weasel", "teor",
10015 "gsathya", and "karsten".
10016 - Previously only relays that explicitly opened a directory port
10017 (DirPort) accepted directory requests from clients. Now all
10018 relays, with and without a DirPort, accept and serve tunneled
10019 directory requests that they receive through their ORPort. You can
10020 disable this behavior using the new DirCache option. Closes
10023 o Major key updates:
10024 - Update the V3 identity key for the dannenberg directory authority:
10025 it was changed on 18 November 2015. Closes task 17906. Patch
10028 o Minor features (security, clock):
10029 - Warn when the system clock appears to move back in time (when the
10030 state file was last written in the future). Tor doesn't know that
10031 consensuses have expired if the clock is in the past. Patch by
10032 "teor". Implements ticket 17188.
10034 o Minor features (security, exit policies):
10035 - ExitPolicyRejectPrivate now rejects more private addresses by
10036 default. Specifically, it now rejects the relay's outbound bind
10037 addresses (if configured), and the relay's configured port
10038 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
10039 0.2.0.11-alpha. Patch by "teor".
10041 o Minor features (security, memory erasure):
10042 - Set the unused entries in a smartlist to NULL. This helped catch
10043 a (harmless) bug, and shouldn't affect performance too much.
10044 Implements ticket 17026.
10045 - Use SecureMemoryWipe() function to securely clean memory on
10046 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
10047 Implements feature 17986.
10048 - Use explicit_bzero or memset_s when present. Previously, we'd use
10049 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
10050 from <logan@hackers.mu> and <selven@hackers.mu>.
10051 - Make memwipe() do nothing when passed a NULL pointer or buffer of
10052 zero size. Check size argument to memwipe() for underflow. Fixes
10053 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
10056 o Minor features (security, RNG):
10057 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
10058 positively are not allowed to fail. Previously we depended on
10059 internal details of OpenSSL's behavior. Closes ticket 17686.
10060 - Never use the system entropy output directly for anything besides
10061 seeding the PRNG. When we want to generate important keys, instead
10062 of using system entropy directly, we now hash it with the PRNG
10063 stream. This may help resist certain attacks based on broken OS
10064 entropy implementations. Closes part of ticket 17694.
10065 - Use modern system calls (like getentropy() or getrandom()) to
10066 generate strong entropy on platforms that have them. Closes
10069 o Minor features (accounting):
10070 - Added two modes to the AccountingRule option: One for limiting
10071 only the number of bytes sent ("AccountingRule out"), and one for
10072 limiting only the number of bytes received ("AccountingRule in").
10073 Closes ticket 15989; patch from "unixninja92".
10075 o Minor features (build):
10076 - Since our build process now uses "make distcheck", we no longer
10077 force "make dist" to depend on "make check". Closes ticket 17893;
10078 patch from "cypherpunks."
10079 - Tor now builds successfully with the recent OpenSSL 1.1
10080 development branch, and with the latest LibreSSL. Closes tickets
10081 17549, 17921, and 17984.
10083 o Minor features (controller):
10084 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
10085 tickets 16774 and 17817. Patch by George Tankersley.
10086 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
10087 service descriptor from a service's local hidden service
10088 descriptor cache. Closes ticket 14846.
10089 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
10090 controllers can examine the the reject rules added by
10091 ExitPolicyRejectPrivate. This makes it easier for stem to display
10094 o Minor features (crypto):
10095 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
10097 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
10098 - When allocating a digest state object, allocate no more space than
10099 we actually need. Previously, we would allocate as much space as
10100 the state for the largest algorithm would need. This change saves
10101 up to 672 bytes per circuit. Closes ticket 17796.
10102 - Improve performance when hashing non-multiple of 8 sized buffers,
10103 based on Andrew Moon's public domain SipHash-2-4 implementation.
10104 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
10106 o Minor features (directory downloads):
10107 - Wait for busy authorities and fallback directories to become non-
10108 busy when bootstrapping. (A similar change was made in 6c443e987d
10109 for directory caches chosen from the consensus.) Closes ticket
10110 17864; patch by "teor".
10111 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
10112 directory mirrors. The default is 1; set it to 0 to disable
10113 fallbacks. Implements ticket 17576. Patch by "teor".
10115 o Minor features (geoip):
10116 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
10119 o Minor features (IPv6):
10120 - Add an argument 'ipv6=address:orport' to the DirAuthority and
10121 FallbackDir torrc options, to specify an IPv6 address for an
10122 authority or fallback directory. Add hard-coded ipv6 addresses for
10123 directory authorities that have them. Closes ticket 17327; patch
10124 from Nick Mathewson and "teor".
10125 - Add address policy assume_action support for IPv6 addresses.
10126 - Limit IPv6 mask bits to 128.
10127 - Warn when comparing against an AF_UNSPEC address in a policy, it's
10128 almost always a bug. Closes ticket 17863; patch by "teor".
10129 - Allow users to configure directory authorities and fallback
10130 directory servers with IPv6 addresses and ORPorts. Resolves
10132 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
10133 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
10134 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
10135 17638; bugfix on 0.0.2pre8. Patch by "teor".
10137 o Minor features (logging):
10138 - When logging to syslog, allow a tag to be added to the syslog
10139 identity (the string prepended to every log message). The tag can
10140 be configured with SyslogIdentityTag and defaults to none. Setting
10141 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
10144 o Minor features (portability):
10145 - Use timingsafe_memcmp() where available. Closes ticket 17944;
10146 patch from <logan@hackers.mu>.
10148 o Minor features (relay, address discovery):
10149 - Add a family argument to get_interface_addresses_raw() and
10150 subfunctions to make network interface address interogation more
10151 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
10152 types of interfaces from the operating system. Resolves
10154 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
10155 fails to enumerate interface addresses using the platform-specific
10156 API, have it rely on the UDP socket fallback technique to try and
10157 find out what IP addresses (both IPv4 and IPv6) our machine has.
10158 Resolves ticket 17951.
10160 o Minor features (replay cache):
10161 - The replay cache now uses SHA256 instead of SHA1. Implements
10162 feature 8961. Patch by "teor", issue reported by "rransom".
10164 o Minor features (unix file permissions):
10165 - Defer creation of Unix sockets until after setuid. This avoids
10166 needing CAP_CHOWN and CAP_FOWNER when using systemd's
10167 CapabilityBoundingSet, or chown and fowner when using SELinux.
10168 Implements part of ticket 17562. Patch from Jamie Nguyen.
10169 - If any directory created by Tor is marked as group readable, the
10170 filesystem group is allowed to be either the default GID or the
10171 root user. Allowing root to read the DataDirectory prevents the
10172 need for CAP_READ_SEARCH when using systemd's
10173 CapabilityBoundingSet, or dac_read_search when using SELinux.
10174 Implements part of ticket 17562. Patch from Jamie Nguyen.
10175 - Introduce a new DataDirectoryGroupReadable option. If it is set to
10176 1, the DataDirectory will be made readable by the default GID.
10177 Implements part of ticket 17562. Patch from Jamie Nguyen.
10179 o Minor bugfixes (accounting):
10180 - The max bandwidth when using 'AccountRule sum' is now correctly
10181 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
10182 from "unixninja92".
10184 o Minor bugfixes (code correctness):
10185 - When closing an entry connection, generate a warning if we should
10186 have sent an end cell for it but we haven't. Fixes bug 17876;
10187 bugfix on 0.2.3.2-alpha.
10188 - Assert that allocated memory held by the reputation code is freed
10189 according to its internal counters. Fixes bug 17753; bugfix
10191 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
10194 o Minor bugfixes (compilation):
10195 - Mark all object files that include micro-revision.i as depending
10196 on it, so as to make parallel builds more reliable. Fixes bug
10197 17826; bugfix on 0.2.5.1-alpha.
10198 - Don't try to use the pthread_condattr_setclock() function unless
10199 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
10200 17819; bugfix on 0.2.6.3-alpha.
10201 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
10203 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
10204 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
10205 - Fix search for libevent libraries on OpenBSD (and other systems
10206 that install libevent 1 and libevent 2 in parallel). Fixes bug
10207 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
10208 - Isolate environment variables meant for tests from the rest of the
10209 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
10210 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
10212 - Remove config.log only from make distclean, not from make clean.
10213 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
10215 o Minor bugfixes (crypto):
10216 - Check the return value of HMAC() and assert on failure. Fixes bug
10217 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
10219 o Minor bugfixes (fallback directories):
10220 - Mark fallbacks as "too busy" when they return a 503 response,
10221 rather than just marking authorities. Fixes bug 17572; bugfix on
10222 0.2.4.7-alpha. Patch by "teor".
10224 o Minor bugfixes (IPv6):
10225 - Update the limits in max_dl_per_request for IPv6 address length.
10226 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
10228 o Minor bugfixes (linux seccomp2 sandbox):
10229 - Fix a crash when using offline master ed25519 keys with the Linux
10230 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
10232 o Minor bugfixes (logging):
10233 - In log messages that include a function name, use __FUNCTION__
10234 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
10235 with clang __PRETTY_FUNCTION__ has extra information we don't
10236 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
10238 - Remove needless quotes from a log message about unparseable
10239 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
10241 o Minor bugfixes (portability):
10242 - Remove an #endif from configure.ac so that we correctly detect the
10243 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
10246 o Minor bugfixes (relays):
10247 - Check that both the ORPort and DirPort (if present) are reachable
10248 before publishing a relay descriptor. Otherwise, relays publish a
10249 descriptor with DirPort 0 when the DirPort reachability test takes
10250 longer than the ORPort reachability test. Fixes bug 18050; bugfix
10251 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
10253 o Minor bugfixes (relays, hidden services):
10254 - Refuse connection requests to private OR addresses unless
10255 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
10256 then refuse to send any cells to a private address. Fixes bugs
10257 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
10259 o Minor bugfixes (safe logging):
10260 - When logging a malformed hostname received through socks4, scrub
10261 it if SafeLogging says we should. Fixes bug 17419; bugfix
10264 o Minor bugfixes (statistics code):
10265 - Consistently check for overflow in round_*_to_next_multiple_of
10266 functions, and add unit tests with additional and maximal values.
10267 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
10268 - Handle edge cases in the laplace functions: avoid division by
10269 zero, avoid taking the log of zero, and silence clang type
10270 conversion warnings using round and trunc. Add unit tests for edge
10271 cases with maximal values. Fixes part of bug 13192; bugfix
10274 o Minor bugfixes (testing):
10275 - The test for log_heartbeat was incorrectly failing in timezones
10276 with non-integer offsets. Instead of comparing the end of the time
10277 string against a constant, compare it to the output of
10278 format_local_iso_time when given the correct input. Fixes bug
10279 18039; bugfix on 0.2.5.4-alpha.
10280 - Make unit tests pass on IPv6-only systems, and systems without
10281 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
10282 bugfix on 0.2.7.3-rc. Patch by "teor".
10283 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
10285 - Check the full results of SHA256 and SHA512 digests in the unit
10286 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
10288 o Code simplification and refactoring:
10289 - Move logging of redundant policy entries in
10290 policies_parse_exit_policy_internal into its own function. Closes
10291 ticket 17608; patch from "juce".
10292 - Extract the more complicated parts of circuit_mark_for_close()
10293 into a new function that we run periodically before circuits are
10294 freed. This change removes more than half of the functions
10295 currently in the "blob". Closes ticket 17218.
10296 - Clean up a little duplicated code in
10297 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
10299 - Decouple the list of streams waiting to be attached to circuits
10300 from the overall connection list. This change makes it possible to
10301 attach streams quickly while simplifying Tor's callgraph and
10302 avoiding O(N) scans of the entire connection list. Closes
10304 - When a direct directory request fails immediately on launch,
10305 instead of relaunching that request from inside the code that
10306 launches it, instead mark the connection for teardown. This change
10307 simplifies Tor's callback and prevents the directory-request
10308 launching code from invoking itself recursively. Closes
10310 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
10311 use them. Closes ticket 17926.
10314 - Add a description of the correct use of the '--keygen' command-
10315 line option. Closes ticket 17583; based on text by 's7r'.
10316 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
10317 - Explain actual minima for BandwidthRate. Closes ticket 16382.
10318 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
10319 - Mention torspec URL in the manpage and point the reader to it
10320 whenever we mention a document that belongs in torspce. Fixes
10323 o Removed features:
10324 - Remove client-side support for connecting to Tor relays running
10325 versions of Tor before 0.2.3.6-alpha. These relays didn't support
10326 the v3 TLS handshake protocol, and are no longer allowed on the
10327 Tor network. Implements the client side of ticket 11150. Based on
10328 patches by Tom van der Woerdt.
10331 - Add unit tests to check for common RNG failure modes, such as
10332 returning all zeroes, identical values, or incrementing values
10333 (OpenSSL's rand_predictable feature). Patch by "teor".
10334 - Log more information when the backtrace tests fail. Closes ticket
10335 17892. Patch from "cypherpunks."
10336 - Always test both ed25519 backends, so that we can be sure that our
10337 batch-open replacement code works. Part of ticket 16794.
10338 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
10339 portion of ticket 16831.
10340 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
10341 util_format.c, directory.c, and options_validate.c. Closes tickets
10342 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
10344 - Unit tests for directory_handle_command_get. Closes ticket 17004.
10345 Patch from Reinaldo de Souza Jr.
10348 Changes in version 0.2.7.6 - 2015-12-10
10349 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
10350 well as a minor bug in hidden service reliability.
10352 o Major bugfixes (guard selection):
10353 - Actually look at the Guard flag when selecting a new directory
10354 guard. When we implemented the directory guard design, we
10355 accidentally started treating all relays as if they have the Guard
10356 flag during guard selection, leading to weaker anonymity and worse
10357 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
10360 o Minor features (geoip):
10361 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
10364 o Minor bugfixes (compilation):
10365 - When checking for net/pfvar.h, include netinet/in.h if possible.
10366 This fixes transparent proxy detection on OpenBSD. Fixes bug
10367 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
10368 - Fix a compilation warning with Clang 3.6: Do not check the
10369 presence of an address which can never be NULL. Fixes bug 17781.
10371 o Minor bugfixes (correctness):
10372 - When displaying an IPv6 exit policy, include the mask bits
10373 correctly even when the number is greater than 31. Fixes bug
10374 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
10375 - The wrong list was used when looking up expired intro points in a
10376 rend service object, causing what we think could be reachability
10377 issues for hidden services, and triggering a BUG log. Fixes bug
10378 16702; bugfix on 0.2.7.2-alpha.
10379 - Fix undefined behavior in the tor_cert_checksig function. Fixes
10380 bug 17722; bugfix on 0.2.7.2-alpha.
10383 Changes in version 0.2.7.5 - 2015-11-20
10384 The Tor 0.2.7 release series is dedicated to the memory of Tor user
10385 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
10386 tirelessly to advocate human rights regardless of national borders,
10387 and oppose the encroachments of mass surveillance. He opposed national
10388 exceptionalism, he brought clarity to legal and policy debates, he
10389 understood and predicted the impact of mass surveillance on the world,
10390 and he laid the groundwork for resisting it. While serving on the Tor
10391 Project's board of directors, he brought us his uncompromising focus
10392 on technical excellence in the service of humankind. Caspar was an
10393 inimitable force for good and a wonderful friend. He was kind,
10394 humorous, generous, gallant, and believed we should protect one
10395 another without exception. We honor him here for his ideals, his
10396 efforts, and his accomplishments. Please honor his memory with works
10397 that would make him proud.
10399 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
10401 The 0.2.7 series adds a more secure identity key type for relays,
10402 improves cryptography performance, resolves several longstanding
10403 hidden-service performance issues, improves controller support for
10404 hidden services, and includes small bugfixes and performance
10405 improvements throughout the program. This release series also includes
10406 more tests than before, and significant simplifications to which parts
10407 of Tor invoke which others.
10409 (This release contains no code changes since 0.2.7.4-rc.)
10412 Changes in version 0.2.7.4-rc - 2015-10-21
10413 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
10414 fixes some important memory leaks, and a scary-looking (but mostly
10415 harmless in practice) invalid-read bug. It also has a few small
10416 bugfixes, notably fixes for compilation and portability on different
10417 platforms. If no further significant bounds are found, the next
10418 release will the the official stable release.
10420 o Major bugfixes (security, correctness):
10421 - Fix an error that could cause us to read 4 bytes before the
10422 beginning of an openssl string. This bug could be used to cause
10423 Tor to crash on systems with unusual malloc implementations, or
10424 systems with unusual hardening installed. Fixes bug 17404; bugfix
10427 o Major bugfixes (correctness):
10428 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
10429 bug 17401; bugfix on 0.2.7.3-rc.
10431 o Major bugfixes (memory leaks):
10432 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
10433 17398; bugfix on 0.2.6.1-alpha.
10434 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
10435 17402; bugfix on 0.2.7.3-rc.
10436 - Fix a memory leak when reading an expired signing key from disk.
10437 Fixes bug 17403; bugfix on 0.2.7.2-rc.
10439 o Minor features (geoIP):
10440 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
10443 o Minor bugfixes (compilation):
10444 - Repair compilation with the most recent (unreleased, alpha)
10445 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
10446 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
10447 17251; bugfix on 0.2.7.2-alpha.
10448 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
10449 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
10451 o Minor bugfixes (portability):
10452 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
10453 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
10456 o Minor bugfixes (sandbox):
10457 - Add the "hidserv-stats" filename to our sandbox filter for the
10458 HiddenServiceStatistics option to work properly. Fixes bug 17354;
10459 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
10461 o Minor bugfixes (testing):
10462 - Add unit tests for get_interface_address* failure cases. Fixes bug
10463 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
10464 - Fix breakage when running 'make check' with BSD make. Fixes bug
10465 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
10466 - Make the get_ifaddrs_* unit tests more tolerant of different
10467 network configurations. (Don't assume every test box has an IPv4
10468 address, and don't assume every test box has a non-localhost
10469 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
10470 - Skip backtrace tests when backtrace support is not compiled in.
10471 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
10475 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
10476 - Note that HiddenServicePorts can take a unix domain socket. Closes
10480 Changes in version 0.2.7.3-rc - 2015-09-25
10481 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
10482 contains numerous usability fixes for Ed25519 keys, safeguards against
10483 several misconfiguration problems, significant simplifications to
10484 Tor's callgraph, and numerous bugfixes and small features.
10486 This is the most tested release of Tor to date. The unit tests cover
10487 39.40% of the code, and the integration tests (accessible with "make
10488 test-full-online", requiring stem and chutney and a network
10489 connection) raise the coverage to 64.49%.
10491 o Major features (security, hidden services):
10492 - Hidden services, if using the EntryNodes option, are required to
10493 use more than one EntryNode, in order to avoid a guard discovery
10494 attack. (This would only affect people who had configured hidden
10495 services and manually specified the EntryNodes option with a
10496 single entry-node. The impact was that it would be easy to
10497 remotely identify the guard node used by such a hidden service.
10498 See ticket for more information.) Fixes ticket 14917.
10500 o Major features (Ed25519 keys, keypinning):
10501 - The key-pinning option on directory authorities is now advisory-
10502 only by default. In a future version, or when the AuthDirPinKeys
10503 option is set, pins are enforced again. Disabling key-pinning
10504 seemed like a good idea so that we can survive the fallout of any
10505 usability problems associated with Ed25519 keys. Closes
10508 o Major features (Ed25519 performance):
10509 - Improve the speed of Ed25519 operations and Curve25519 keypair
10510 generation when built targeting 32 bit x86 platforms with SSE2
10511 available. Implements ticket 16535.
10512 - Improve the runtime speed of Ed25519 signature verification by
10513 using Ed25519-donna's batch verification support. Implements
10516 o Major features (performance testing):
10517 - The test-network.sh script now supports performance testing.
10518 Requires corresponding chutney performance testing changes. Patch
10519 by "teor". Closes ticket 14175.
10521 o Major features (relay, Ed25519):
10522 - Significant usability improvements for Ed25519 key management. Log
10523 messages are better, and the code can recover from far more
10524 failure conditions. Thanks to "s7r" for reporting and diagnosing
10526 - Add a new OfflineMasterKey option to tell Tor never to try loading
10527 or generating a secret Ed25519 identity key. You can use this in
10528 combination with tor --keygen to manage offline and/or encrypted
10529 Ed25519 keys. Implements ticket 16944.
10530 - Add a --newpass option to allow changing or removing the
10531 passphrase of an encrypted key with tor --keygen. Implements part
10533 - On receiving a HUP signal, check to see whether the Ed25519
10534 signing key has changed, and reload it if so. Closes ticket 16790.
10536 o Major bugfixes (relay, Ed25519):
10537 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
10538 0.2.7.2-alpha. Reported by "s7r".
10539 - Improve handling of expired signing keys with offline master keys.
10540 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
10542 o Minor features (client-side privacy):
10543 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
10544 lifespan when IsolateSOCKSAuth and streams with SOCKS
10545 authentication are attached to the circuit. This allows
10546 applications like TorBrowser to manage circuit lifetime on their
10547 own. Implements feature 15482.
10548 - When logging malformed hostnames from SOCKS5 requests, respect
10549 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
10551 o Minor features (compilation):
10552 - Give a warning as early as possible when trying to build with an
10553 unsupported OpenSSL version. Closes ticket 16901.
10554 - Fail during configure if we're trying to build against an OpenSSL
10555 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
10556 which started requiring ECC.
10558 o Minor features (geoip):
10559 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
10562 o Minor features (hidden services):
10563 - Relays need to have the Fast flag to get the HSDir flag. As this
10564 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
10565 drop. This change should make some attacks against the hidden
10566 service directory system harder. Fixes ticket 15963.
10567 - Turn on hidden service statistics collection by setting the torrc
10568 option HiddenServiceStatistics to "1" by default. (This keeps
10569 track only of the fraction of traffic used by hidden services, and
10570 the total number of hidden services in existence.) Closes
10572 - Client now uses an introduction point failure cache to know when
10573 to fetch or keep a descriptor in their cache. Previously, failures
10574 were recorded implicitly, but not explicitly remembered. Closes
10577 o Minor features (testing, authorities, documentation):
10578 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
10579 explicitly manage consensus flags in testing networks. Patch by
10580 "robgjansen", modified by "teor". Implements part of ticket 14882.
10582 o Minor bugfixes (security, exit policies):
10583 - ExitPolicyRejectPrivate now also rejects the relay's published
10584 IPv6 address (if any), and any publicly routable IPv4 or IPv6
10585 addresses on any local interfaces. ticket 17027. Patch by "teor".
10586 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
10588 o Minor bug fixes (torrc exit policies):
10589 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
10590 produce IPv6 wildcard addresses. Previously they would produce
10591 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
10592 of bug 16069; bugfix on 0.2.4.7-alpha.
10593 - When parsing torrc ExitPolicies, we now warn for a number of cases
10594 where the user's intent is likely to differ from Tor's actual
10595 behavior. These include: using an IPv4 address with an accept6 or
10596 reject6 line; using "private" on an accept6 or reject6 line; and
10597 including any ExitPolicy lines after accept *:* or reject *:*.
10598 Related to ticket 16069.
10599 - When parsing torrc ExitPolicies, we now issue an info-level
10600 message when expanding an "accept/reject *" line to include both
10601 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
10602 - In each instance above, usage advice is provided to avoid the
10603 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
10604 16069; bugfix on 0.2.4.7-alpha.
10606 o Minor bugfixes (authority):
10607 - Don't assign "HSDir" to a router if it isn't Valid and Running.
10608 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
10609 - Downgrade log messages about Ed25519 key issues if they are in old
10610 cached router descriptors. Fixes part of bug 16286; bugfix
10612 - When we find an Ed25519 key issue in a cached descriptor, stop
10613 saying the descriptor was just "uploaded". Fixes another part of
10614 bug 16286; bugfix on 0.2.7.2-alpha.
10616 o Minor bugfixes (control port):
10617 - Repair a warning and a spurious result when getting the maximum
10618 number of file descriptors from the controller. Fixes bug 16697;
10619 bugfix on 0.2.7.2-alpha.
10621 o Minor bugfixes (correctness):
10622 - When calling channel_free_list(), avoid calling smartlist_remove()
10623 while inside a FOREACH loop. This partially reverts commit
10624 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
10625 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
10627 o Minor bugfixes (documentation):
10628 - Advise users on how to configure separate IPv4 and IPv6 exit
10629 policies in the manpage and sample torrcs. Related to ticket 16069.
10630 - Fix the usage message of tor-resolve(1) so that it no longer lists
10631 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
10632 - Fix an error in the manual page and comments for
10633 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
10634 required "ORPort connectivity". While this is true, it is in no
10635 way unique to the HSDir flag. Of all the flags, only HSDirs need a
10636 DirPort configured in order for the authorities to assign that
10637 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
10640 o Minor bugfixes (Ed25519):
10641 - Fix a memory leak when reading router descriptors with expired
10642 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
10644 o Minor bugfixes (linux seccomp2 sandbox):
10645 - Allow bridge authorities to run correctly under the seccomp2
10646 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
10647 - Allow routers with ed25519 keys to run correctly under the
10648 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
10650 o Minor bugfixes (open file limit):
10651 - Fix set_max_file_descriptors() to set by default the max open file
10652 limit to the current limit when setrlimit() fails. Fixes bug
10653 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
10655 o Minor bugfixes (portability):
10656 - Try harder to normalize the exit status of the Tor process to the
10657 standard-provided range. Fixes bug 16975; bugfix on every version
10659 - Check correctly for Windows socket errors in the workqueue
10660 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
10661 - Fix the behavior of crypto_rand_time_range() when told to consider
10662 times before 1970. (These times were possible when running in a
10663 simulated network environment where time()'s output starts at
10664 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
10665 - Restore correct operation of TLS client-cipher detection on
10666 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
10668 o Minor bugfixes (relay):
10669 - Ensure that worker threads actually exit when a fatal error or
10670 shutdown is indicated. This fix doesn't currently affect the
10671 behavior of Tor, because Tor workers never indicates fatal error
10672 or shutdown except in the unit tests. Fixes bug 16868; bugfix
10674 - Unblock threads before releasing the work queue mutex to ensure
10675 predictable scheduling behavior. Fixes bug 16644; bugfix
10678 o Code simplification and refactoring:
10679 - Change the function that's called when we need to retry all
10680 downloads so that it only reschedules the downloads to happen
10681 immediately, rather than launching them all at once itself. This
10682 further simplifies Tor's callgraph.
10683 - Move some format-parsing functions out of crypto.c and
10684 crypto_curve25519.c into crypto_format.c and/or util_format.c.
10685 - Move the client-only parts of init_keys() into a separate
10686 function. Closes ticket 16763.
10687 - Simplify the microdesc_free() implementation so that it no longer
10688 appears (to code analysis tools) to potentially invoke a huge
10689 suite of other microdesc functions.
10690 - Simply the control graph further by deferring the inner body of
10691 directory_all_unreachable() into a callback. Closes ticket 16762.
10692 - Treat the loss of an owning controller as equivalent to a SIGTERM
10693 signal. This removes a tiny amount of duplicated code, and
10694 simplifies our callgraph. Closes ticket 16788.
10695 - When generating an event to send to the controller, we no longer
10696 put the event over the network immediately. Instead, we queue
10697 these events, and use a Libevent callback to deliver them. This
10698 change simplifies Tor's callgraph by reducing the number of
10699 functions from which all other Tor functions are reachable. Closes
10701 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
10702 that try to scan or compile every file on Unix won't decide that
10704 - Remove the unused "nulterminate" argument from buf_pullup().
10707 - Recommend a 40 GB example AccountingMax in torrc.sample rather
10708 than a 4 GB max. Closes ticket 16742.
10709 - Include the TUNING document in our source tarball. It is referred
10710 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
10714 - The internal pure-C tor-fw-helper tool is now removed from the Tor
10715 distribution, in favor of the pure-Go clone available from
10716 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
10717 used by the C tor-fw-helper are not, in our opinion, very
10718 confidence- inspiring in their secure-programming techniques.
10719 Closes ticket 13338.
10720 - Remove the code that would try to aggressively flush controller
10721 connections while writing to them. This code was introduced in
10722 0.1.2.7-alpha, in order to keep output buffers from exceeding
10723 their limits. But there is no longer a maximum output buffer size,
10724 and flushing data in this way caused some undesirable recursions
10725 in our call graph. Closes ticket 16480.
10728 - Make "bridges+hs" the default test network. This tests almost all
10729 tor functionality during make test-network, while allowing tests
10730 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
10731 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
10732 (chutney). Patches by "teor".
10733 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
10734 by-side in the same parent directory. Closes ticket 16903. Patch
10736 - Use environment variables rather than autoconf substitutions to
10737 send variables from the build system to the test scripts. This
10738 change should be easier to maintain, and cause 'make distcheck' to
10739 work better than before. Fixes bug 17148.
10740 - Add a new set of callgraph analysis scripts that use clang to
10741 produce a list of which Tor functions are reachable from which
10742 other Tor functions. We're planning to use these to help simplify
10743 our code structure by identifying illogical dependencies.
10744 - Add new 'test-full' and 'test-full-online' targets to run all
10745 tests, including integration tests with stem and chutney.
10746 - Make the test-workqueue test work on Windows by initializing the
10747 network before we begin.
10748 - New make target (make test-network-all) to run multiple applicable
10749 chutney test cases. Patch from Teor; closes 16953.
10750 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
10751 functions in dns.c. Implements a portion of ticket 16831.
10752 - When building Tor with testing coverage enabled, run Chutney tests
10753 (if any) using the 'tor-cov' coverage binary.
10754 - When running test-network or test-stem, check for the absence of
10755 stem/chutney before doing any build operations.
10758 Changes in version 0.2.7.2-alpha - 2015-07-27
10759 This, the second alpha in the Tor 0.2.7 series, has a number of new
10760 features, including a way to manually pick the number of introduction
10761 points for hidden services, and the much stronger Ed25519 signing key
10762 algorithm for regular Tor relays (including support for encrypted
10763 offline identity keys in the new algorithm).
10765 Support for Ed25519 on relays is currently limited to signing router
10766 descriptors; later alphas in this series will extend Ed25519 key
10767 support to more parts of the Tor protocol.
10769 o Major features (Ed25519 identity keys, Proposal 220):
10770 - All relays now maintain a stronger identity key, using the Ed25519
10771 elliptic curve signature format. This master key is designed so
10772 that it can be kept offline. Relays also generate an online
10773 signing key, and a set of other Ed25519 keys and certificates.
10774 These are all automatically regenerated and rotated as needed.
10775 Implements part of ticket 12498.
10776 - Directory authorities now vote on Ed25519 identity keys along with
10777 RSA1024 keys. Implements part of ticket 12498.
10778 - Directory authorities track which Ed25519 identity keys have been
10779 used with which RSA1024 identity keys, and do not allow them to
10780 vary freely. Implements part of ticket 12498.
10781 - Microdescriptors now include Ed25519 identity keys. Implements
10782 part of ticket 12498.
10783 - Add support for offline encrypted Ed25519 master keys. To use this
10784 feature on your tor relay, run "tor --keygen" to make a new master
10785 key (or to make a new signing key if you already have a master
10786 key). Closes ticket 13642.
10788 o Major features (Hidden services):
10789 - Add the torrc option HiddenServiceNumIntroductionPoints, to
10790 specify a fixed number of introduction points. Its maximum value
10791 is 10 and default is 3. Using this option can increase a hidden
10792 service's reliability under load, at the cost of making it more
10793 visible that the hidden service is facing extra load. Closes
10795 - Remove the adaptive algorithm for choosing the number of
10796 introduction points, which used to change the number of
10797 introduction points (poorly) depending on the number of
10798 connections the HS sees. Closes ticket 4862.
10800 o Major features (onion key cross-certification):
10801 - Relay descriptors now include signatures of their own identity
10802 keys, made using the TAP and ntor onion keys. These signatures
10803 allow relays to prove ownership of their own onion keys. Because
10804 of this change, microdescriptors will no longer need to include
10805 RSA identity keys. Implements proposal 228; closes ticket 12499.
10807 o Major features (performance):
10808 - Improve the runtime speed of Ed25519 operations by using the
10809 public-domain Ed25519-donna by Andrew M. ("floodyberry").
10810 Implements ticket 16467.
10811 - Improve the runtime speed of the ntor handshake by using an
10812 optimized curve25519 basepoint scalarmult implementation from the
10813 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
10814 ideas by Adam Langley. Implements ticket 9663.
10816 o Major bugfixes (client-side privacy, also in 0.2.6.9):
10817 - Properly separate out each SOCKSPort when applying stream
10818 isolation. The error occurred because each port's session group
10819 was being overwritten by a default value when the listener
10820 connection was initialized. Fixes bug 16247; bugfix on
10821 0.2.6.3-alpha. Patch by "jojelino".
10823 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
10824 - Stop refusing to store updated hidden service descriptors on a
10825 client. This reverts commit 9407040c59218 (which indeed fixed bug
10826 14219, but introduced a major hidden service reachability
10827 regression detailed in bug 16381). This is a temporary fix since
10828 we can live with the minor issue in bug 14219 (it just results in
10829 some load on the network) but the regression of 16381 is too much
10830 of a setback. First-round fix for bug 16381; bugfix
10833 o Major bugfixes (hidden services):
10834 - When cannibalizing a circuit for an introduction point, always
10835 extend to the chosen exit node (creating a 4 hop circuit).
10836 Previously Tor would use the current circuit exit node, which
10837 changed the original choice of introduction point, and could cause
10838 the hidden service to skip excluded introduction points or
10839 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
10842 o Major bugfixes (open file limit):
10843 - The open file limit wasn't checked before calling
10844 tor_accept_socket_nonblocking(), which would make Tor exceed the
10845 limit. Now, before opening a new socket, Tor validates the open
10846 file limit just before, and if the max has been reached, return an
10847 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
10849 o Major bugfixes (stability, also in 0.2.6.10):
10850 - Stop crashing with an assertion failure when parsing certain kinds
10851 of malformed or truncated microdescriptors. Fixes bug 16400;
10852 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
10853 by "cypherpunks_backup".
10854 - Stop random client-side assertion failures that could occur when
10855 connecting to a busy hidden service, or connecting to a hidden
10856 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
10859 o Minor features (directory authorities, security, also in 0.2.6.9):
10860 - The HSDir flag given by authorities now requires the Stable flag.
10861 For the current network, this results in going from 2887 to 2806
10862 HSDirs. Also, it makes it harder for an attacker to launch a sybil
10863 attack by raising the effort for a relay to become Stable to
10864 require at the very least 7 days, while maintaining the 96 hours
10865 uptime requirement for HSDir. Implements ticket 8243.
10867 o Minor features (client):
10868 - Relax the validation of hostnames in SOCKS5 requests, allowing the
10869 character '_' to appear, in order to cope with domains observed in
10870 the wild that are serving non-RFC compliant records. Resolves
10872 - Relax the validation done to hostnames in SOCKS5 requests, and
10873 allow a single trailing '.' to cope with clients that pass FQDNs
10874 using that syntax to explicitly indicate that the domain name is
10875 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
10876 - Add GroupWritable and WorldWritable options to unix-socket based
10877 SocksPort and ControlPort options. These options apply to a single
10878 socket, and override {Control,Socks}SocketsGroupWritable. Closes
10881 o Minor features (control protocol):
10882 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
10883 the control protocol. Resolves ticket 15358.
10885 o Minor features (directory authorities):
10886 - Directory authorities no longer vote against the "Fast", "Stable",
10887 and "HSDir" flags just because they were going to vote against
10888 "Running": if the consensus turns out to be that the router was
10889 running, then the authority's vote should count. Patch from Peter
10890 Retzlaff; closes issue 8712.
10892 o Minor features (geoip, also in 0.2.6.10):
10893 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
10894 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
10896 o Minor features (hidden services):
10897 - Add the new options "HiddenServiceMaxStreams" and
10898 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
10899 limit the maximum number of simultaneous streams per circuit, and
10900 optionally tear down the circuit when the limit is exceeded. Part
10903 o Minor features (portability):
10904 - Use C99 variadic macros when the compiler is not GCC. This avoids
10905 failing compilations on MSVC, and fixes a log-file-based race
10906 condition in our old workarounds. Original patch from Gisle Vanem.
10908 o Minor bugfixes (compilation, also in 0.2.6.9):
10909 - Build with --enable-systemd correctly when libsystemd is
10910 installed, but systemd is not. Fixes bug 16164; bugfix on
10911 0.2.6.3-alpha. Patch from Peter Palfrader.
10913 o Minor bugfixes (controller):
10914 - Add the descriptor ID in each HS_DESC control event. It was
10915 missing, but specified in control-spec.txt. Fixes bug 15881;
10916 bugfix on 0.2.5.2-alpha.
10918 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
10919 - Check for failures from crypto_early_init, and refuse to continue.
10920 A previous typo meant that we could keep going with an
10921 uninitialized crypto library, and would have OpenSSL initialize
10922 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
10923 when implementing ticket 4900. Patch by "teor".
10925 o Minor bugfixes (hidden services):
10926 - Fix a crash when reloading configuration while at least one
10927 configured and one ephemeral hidden service exists. Fixes bug
10928 16060; bugfix on 0.2.7.1-alpha.
10929 - Avoid crashing with a double-free bug when we create an ephemeral
10930 hidden service but adding it fails for some reason. Fixes bug
10931 16228; bugfix on 0.2.7.1-alpha.
10933 o Minor bugfixes (Linux seccomp2 sandbox):
10934 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
10935 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
10937 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
10938 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
10939 these when eventfd2() support is missing. Fixes bug 16363; bugfix
10940 on 0.2.6.3-alpha. Patch from "teor".
10942 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
10943 - Fix sandboxing to work when running as a relay, by allowing the
10944 renaming of secret_id_key, and allowing the eventfd2 and futex
10945 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
10947 - Allow systemd connections to work with the Linux seccomp2 sandbox
10948 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
10951 o Minor bugfixes (relay):
10952 - Fix a rarely-encountered memory leak when failing to initialize
10953 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
10954 from "cypherpunks".
10956 o Minor bugfixes (systemd):
10957 - Fix an accidental formatting error that broke the systemd
10958 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
10959 - Tor's systemd unit file no longer contains extraneous spaces.
10960 These spaces would sometimes confuse tools like deb-systemd-
10961 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
10963 o Minor bugfixes (tests):
10964 - Use the configured Python executable when running test-stem-full.
10965 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
10967 o Minor bugfixes (tests, also in 0.2.6.9):
10968 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
10969 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
10971 o Minor bugfixes (threads, comments):
10972 - Always initialize return value in compute_desc_id in rendcommon.c
10973 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
10974 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
10975 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
10976 - Remove undefined directive-in-macro in test_util_writepid clang
10977 3.7 complains that using a preprocessor directive inside a macro
10978 invocation in test_util_writepid in test_util.c is undefined.
10979 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
10981 o Code simplification and refactoring:
10982 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
10983 to ensure they remain consistent and visible everywhere.
10984 - Remove some vestigial workarounds for the MSVC6 compiler. We
10985 haven't supported that in ages.
10986 - The link authentication code has been refactored for better
10987 testability and reliability. It now uses code generated with the
10988 "trunnel" binary encoding generator, to reduce the risk of bugs
10989 due to programmer error. Done as part of ticket 12498.
10992 - Include a specific and (hopefully) accurate documentation of the
10993 torrc file's meta-format in doc/torrc_format.txt. This is mainly
10994 of interest to people writing programs to parse or generate torrc
10995 files. This document is not a commitment to long-term
10996 compatibility; some aspects of the current format are a bit
10997 ridiculous. Closes ticket 2325.
10999 o Removed features:
11000 - Tor no longer supports copies of OpenSSL that are missing support
11001 for Elliptic Curve Cryptography. (We began using ECC when
11002 available in 0.2.4.8-alpha, for more safe and efficient key
11003 negotiation.) In particular, support for at least one of P256 or
11004 P224 is now required, with manual configuration needed if only
11005 P224 is available. Resolves ticket 16140.
11006 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
11007 on an operating system that has not upgraded to OpenSSL 1.0 or
11008 later, and you compile Tor from source, you will need to install a
11009 more recent OpenSSL to link Tor against.) These versions of
11010 OpenSSL are still supported by the OpenSSL, but the numerous
11011 cryptographic improvements in later OpenSSL releases makes them a
11012 clear choice. Resolves ticket 16034.
11013 - Remove the HidServDirectoryV2 option. Now all relays offer to
11014 store hidden service descriptors. Related to 16543.
11015 - Remove the VoteOnHidServDirectoriesV2 option, since all
11016 authorities have long set it to 1. Closes ticket 16543.
11019 - Document use of coverity, clang static analyzer, and clang dynamic
11020 undefined behavior and address sanitizers in doc/HACKING. Include
11021 detailed usage instructions in the blacklist. Patch by "teor".
11022 Closes ticket 15817.
11023 - The link authentication protocol code now has extensive tests.
11024 - The relay descriptor signature testing code now has
11026 - The test_workqueue program now runs faster, and is enabled by
11027 default as a part of "make check".
11028 - Now that OpenSSL has its own scrypt implementation, add an unit
11029 test that checks for interoperability between libscrypt_scrypt()
11030 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
11031 and rely on EVP_PBE_scrypt() whenever possible. Resolves
11035 Changes in version 0.2.6.10 - 2015-07-12
11036 Tor version 0.2.6.10 fixes some significant stability and hidden
11037 service client bugs, bulletproofs the cryptography init process, and
11038 fixes a bug when using the sandbox code with some older versions of
11039 Linux. Everyone running an older version, especially an older version
11040 of 0.2.6, should upgrade.
11042 o Major bugfixes (hidden service clients, stability):
11043 - Stop refusing to store updated hidden service descriptors on a
11044 client. This reverts commit 9407040c59218 (which indeed fixed bug
11045 14219, but introduced a major hidden service reachability
11046 regression detailed in bug 16381). This is a temporary fix since
11047 we can live with the minor issue in bug 14219 (it just results in
11048 some load on the network) but the regression of 16381 is too much
11049 of a setback. First-round fix for bug 16381; bugfix
11052 o Major bugfixes (stability):
11053 - Stop crashing with an assertion failure when parsing certain kinds
11054 of malformed or truncated microdescriptors. Fixes bug 16400;
11055 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
11056 by "cypherpunks_backup".
11057 - Stop random client-side assertion failures that could occur when
11058 connecting to a busy hidden service, or connecting to a hidden
11059 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
11062 o Minor features (geoip):
11063 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
11064 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
11066 o Minor bugfixes (crypto error-handling):
11067 - Check for failures from crypto_early_init, and refuse to continue.
11068 A previous typo meant that we could keep going with an
11069 uninitialized crypto library, and would have OpenSSL initialize
11070 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
11071 when implementing ticket 4900. Patch by "teor".
11073 o Minor bugfixes (Linux seccomp2 sandbox):
11074 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
11075 these when eventfd2() support is missing. Fixes bug 16363; bugfix
11076 on 0.2.6.3-alpha. Patch from "teor".
11079 Changes in version 0.2.6.9 - 2015-06-11
11080 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
11081 requirements for receiving an HSDir flag, and addresses some other small
11082 bugs in the systemd and sandbox code. Clients using circuit isolation
11083 should upgrade; all directory authorities should upgrade.
11085 o Major bugfixes (client-side privacy):
11086 - Properly separate out each SOCKSPort when applying stream
11087 isolation. The error occurred because each port's session group was
11088 being overwritten by a default value when the listener connection
11089 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
11092 o Minor feature (directory authorities, security):
11093 - The HSDir flag given by authorities now requires the Stable flag.
11094 For the current network, this results in going from 2887 to 2806
11095 HSDirs. Also, it makes it harder for an attacker to launch a sybil
11096 attack by raising the effort for a relay to become Stable which
11097 takes at the very least 7 days to do so and by keeping the 96
11098 hours uptime requirement for HSDir. Implements ticket 8243.
11100 o Minor bugfixes (compilation):
11101 - Build with --enable-systemd correctly when libsystemd is
11102 installed, but systemd is not. Fixes bug 16164; bugfix on
11103 0.2.6.3-alpha. Patch from Peter Palfrader.
11105 o Minor bugfixes (Linux seccomp2 sandbox):
11106 - Fix sandboxing to work when running as a relaymby renaming of
11107 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
11108 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
11109 - Allow systemd connections to work with the Linux seccomp2 sandbox
11110 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
11113 o Minor bugfixes (tests):
11114 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
11115 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
11118 Changes in version 0.2.6.8 - 2015-05-21
11119 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
11120 fixes an authority-side bug in assigning the HSDir flag. All directory
11121 authorities should upgrade.
11123 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
11124 - Revert commit that made directory authorities assign the HSDir
11125 flag to relays without a DirPort; this was bad because such relays
11126 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
11129 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
11130 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
11131 a client authorized hidden service. Fixes bug 15823; bugfix
11134 o Minor features (geoip):
11135 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
11136 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
11140 Changes in version 0.2.7.1-alpha - 2015-05-12
11141 Tor 0.2.7.1-alpha is the first alpha release in its series. It
11142 includes numerous small features and bugfixes against previous Tor
11143 versions, and numerous small infrastructure improvements. The most
11144 notable features are several new ways for controllers to interact with
11145 the hidden services subsystem.
11147 o New system requirements:
11148 - Tor no longer includes workarounds to support Libevent versions
11149 before 1.3e. Libevent 2.0 or later is recommended. Closes
11152 o Major features (controller):
11153 - Add the ADD_ONION and DEL_ONION commands that allow the creation
11154 and management of hidden services via the controller. Closes
11156 - New "GETINFO onions/current" and "GETINFO onions/detached"
11157 commands to get information about hidden services created via the
11158 controller. Part of ticket 6411.
11159 - New HSFETCH command to launch a request for a hidden service
11160 descriptor. Closes ticket 14847.
11161 - New HSPOST command to upload a hidden service descriptor. Closes
11162 ticket 3523. Patch by "DonnchaC".
11164 o Major bugfixes (hidden services):
11165 - Revert commit that made directory authorities assign the HSDir
11166 flag to relays without a DirPort; this was bad because such relays
11167 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
11170 o Minor features (clock-jump tolerance):
11171 - Recover better when our clock jumps back many hours, like might
11172 happen for Tails or Whonix users who start with a very wrong
11173 hardware clock, use Tor to discover a more accurate time, and then
11174 fix their clock. Resolves part of ticket 8766.
11176 o Minor features (command-line interface):
11177 - Make --hash-password imply --hush to prevent unnecessary noise.
11178 Closes ticket 15542. Patch from "cypherpunks".
11179 - Print a warning whenever we find a relative file path being used
11180 as torrc option. Resolves issue 14018.
11182 o Minor features (controller):
11183 - Add DirAuthority lines for default directory authorities to the
11184 output of the "GETINFO config/defaults" command if not already
11185 present. Implements ticket 14840.
11186 - Controllers can now use "GETINFO hs/client/desc/id/..." to
11187 retrieve items from the client's hidden service descriptor cache.
11188 Closes ticket 14845.
11189 - Implement a new controller command "GETINFO status/fresh-relay-
11190 descs" to fetch a descriptor/extrainfo pair that was generated on
11191 demand just for the controller's use. Implements ticket 14784.
11193 o Minor features (DoS-resistance):
11194 - Make it harder for attackers to overload hidden services with
11195 introductions, by blocking multiple introduction requests on the
11196 same circuit. Resolves ticket 15515.
11198 o Minor features (geoip):
11199 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
11200 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
11203 o Minor features (HS popularity countermeasure):
11204 - To avoid leaking HS popularity, don't cycle the introduction point
11205 when we've handled a fixed number of INTRODUCE2 cells but instead
11206 cycle it when a random number of introductions is reached, thus
11207 making it more difficult for an attacker to find out the amount of
11208 clients that have used the introduction point for a specific HS.
11209 Closes ticket 15745.
11211 o Minor features (logging):
11212 - Include the Tor version in all LD_BUG log messages, since people
11213 tend to cut and paste those into the bugtracker. Implements
11216 o Minor features (pluggable transports):
11217 - When launching managed pluggable transports on Linux systems,
11218 attempt to have the kernel deliver a SIGTERM on tor exit if the
11219 pluggable transport process is still running. Resolves
11221 - When launching managed pluggable transports, setup a valid open
11222 stdin in the child process that can be used to detect if tor has
11223 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
11224 can be used by implementations to detect this new behavior.
11225 Resolves ticket 15435.
11227 o Minor features (testing):
11228 - Add a test to verify that the compiler does not eliminate our
11229 memwipe() implementation. Closes ticket 15377.
11230 - Add make rule `check-changes` to verify the format of changes
11231 files. Closes ticket 15180.
11232 - Add unit tests for control_event_is_interesting(). Add a compile-
11233 time check that the number of events doesn't exceed the capacity
11234 of control_event_t.event_mask. Closes ticket 15431, checks for
11235 bugs similar to 13085. Patch by "teor".
11236 - Command-line argument tests moved to Stem. Resolves ticket 14806.
11237 - Integrate the ntor, backtrace, and zero-length keys tests into the
11238 automake test suite. Closes ticket 15344.
11239 - Remove assertions during builds to determine Tor's test coverage.
11240 We don't want to trigger these even in assertions, so including
11241 them artificially makes our branch coverage look worse than it is.
11242 This patch provides the new test-stem-full and coverage-html-full
11243 configure options. Implements ticket 15400.
11245 o Minor bugfixes (build):
11246 - Improve out-of-tree builds by making non-standard rules work and
11247 clean up additional files and directories. Fixes bug 15053; bugfix
11250 o Minor bugfixes (command-line interface):
11251 - When "--quiet" is provided along with "--validate-config", do not
11252 write anything to stdout on success. Fixes bug 14994; bugfix
11254 - When complaining about bad arguments to "--dump-config", use
11255 stderr, not stdout.
11257 o Minor bugfixes (configuration, unit tests):
11258 - Only add the default fallback directories when the DirAuthorities,
11259 AlternateDirAuthority, and FallbackDir directory config options
11260 are set to their defaults. The default fallback directory list is
11261 currently empty, this fix will only change tor's behavior when it
11262 has default fallback directories. Includes unit tests for
11263 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
11264 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
11266 o Minor bugfixes (correctness):
11267 - For correctness, avoid modifying a constant string in
11268 handle_control_postdescriptor. Fixes bug 15546; bugfix
11270 - Remove side-effects from tor_assert() calls. This was harmless,
11271 because we never disable assertions, but it is bad style and
11272 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
11275 o Minor bugfixes (hidden service):
11276 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
11277 a client authorized hidden service. Fixes bug 15823; bugfix
11279 - Remove an extraneous newline character from the end of hidden
11280 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
11282 o Minor bugfixes (interface):
11283 - Print usage information for --dump-config when it is used without
11284 an argument. Also, fix the error message to use different wording
11285 and add newline at the end. Fixes bug 15541; bugfix
11288 o Minor bugfixes (logs):
11289 - When building Tor under Clang, do not include an extra set of
11290 parentheses in log messages that include function names. Fixes bug
11291 15269; bugfix on every released version of Tor when compiled with
11292 recent enough Clang.
11294 o Minor bugfixes (network):
11295 - When attempting to use fallback technique for network interface
11296 lookup, disregard loopback and multicast addresses since they are
11297 unsuitable for public communications.
11299 o Minor bugfixes (statistics):
11300 - Disregard the ConnDirectionStatistics torrc options when Tor is
11301 not a relay since in that mode of operation no sensible data is
11302 being collected and because Tor might run into measurement hiccups
11303 when running as a client for some time, then becoming a relay.
11304 Fixes bug 15604; bugfix on 0.2.2.35.
11306 o Minor bugfixes (test networks):
11307 - When self-testing reachability, use ExtendAllowPrivateAddresses to
11308 determine if local/private addresses imply reachability. The
11309 previous fix used TestingTorNetwork, which implies
11310 ExtendAllowPrivateAddresses, but this excluded rare configurations
11311 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
11312 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
11313 issue discovered by CJ Ess.
11315 o Minor bugfixes (testing):
11316 - Check for matching value in server response in ntor_ref.py. Fixes
11317 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
11319 - Set the severity correctly when testing
11320 get_interface_addresses_ifaddrs() and
11321 get_interface_addresses_win32(), so that the tests fail gracefully
11322 instead of triggering an assertion. Fixes bug 15759; bugfix on
11323 0.2.6.3-alpha. Reported by Nicolas Derive.
11325 o Code simplification and refactoring:
11326 - Move the hacky fallback code out of get_interface_address6() into
11327 separate function and get it covered with unit-tests. Resolves
11329 - Refactor hidden service client-side cache lookup to intelligently
11330 report its various failure cases, and disentangle failure cases
11331 involving a lack of introduction points. Closes ticket 14391.
11332 - Use our own Base64 encoder instead of OpenSSL's, to allow more
11333 control over the output. Part of ticket 15652.
11336 - Improve the descriptions of statistics-related torrc options in
11337 the manpage to describe rationale and possible uses cases. Fixes
11339 - Improve the layout and formatting of ./configure --help messages.
11340 Closes ticket 15024. Patch from "cypherpunks".
11341 - Standardize on the term "server descriptor" in the manual page.
11342 Previously, we had used "router descriptor", "server descriptor",
11343 and "relay descriptor" interchangeably. Part of ticket 14987.
11346 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
11347 and always use the internal Base64 decoder. The internal decoder
11348 has been part of tor since 0.2.0.10-alpha, and no one should
11349 be using the OpenSSL one. Part of ticket 15652.
11350 - Remove the 'tor_strclear()' function; use memwipe() instead.
11351 Closes ticket 14922.
11353 o Removed features:
11354 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
11355 fingerprinting we now recommend pluggable transports; for forward-
11356 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
11357 - Remove the undocumented "--digests" command-line option. It
11358 complicated our build process, caused subtle build issues on
11359 multiple platforms, and is now redundant since we started
11360 including git version identifiers. Closes ticket 14742.
11361 - Tor no longer contains checks for ancient directory cache versions
11362 that didn't know about microdescriptors.
11363 - Tor no longer contains workarounds for stat files generated by
11364 super-old versions of Tor that didn't choose guards sensibly.
11367 Changes in version 0.2.4.27 - 2015-04-06
11368 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
11369 could be used by an attacker to crash hidden services, or crash clients
11370 visiting hidden services. Hidden services should upgrade as soon as
11371 possible; clients should upgrade whenever packages become available.
11373 This release also backports a simple improvement to make hidden
11374 services a bit less vulnerable to denial-of-service attacks.
11376 o Major bugfixes (security, hidden service):
11377 - Fix an issue that would allow a malicious client to trigger an
11378 assertion failure and halt a hidden service. Fixes bug 15600;
11379 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
11380 - Fix a bug that could cause a client to crash with an assertion
11381 failure when parsing a malformed hidden service descriptor. Fixes
11382 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
11384 o Minor features (DoS-resistance, hidden service):
11385 - Introduction points no longer allow multiple INTRODUCE1 cells to
11386 arrive on the same circuit. This should make it more expensive for
11387 attackers to overwhelm hidden services with introductions.
11388 Resolves ticket 15515.
11391 Changes in version 0.2.5.12 - 2015-04-06
11392 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
11393 could be used by an attacker to crash hidden services, or crash clients
11394 visiting hidden services. Hidden services should upgrade as soon as
11395 possible; clients should upgrade whenever packages become available.
11397 This release also backports a simple improvement to make hidden
11398 services a bit less vulnerable to denial-of-service attacks.
11400 o Major bugfixes (security, hidden service):
11401 - Fix an issue that would allow a malicious client to trigger an
11402 assertion failure and halt a hidden service. Fixes bug 15600;
11403 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
11404 - Fix a bug that could cause a client to crash with an assertion
11405 failure when parsing a malformed hidden service descriptor. Fixes
11406 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
11408 o Minor features (DoS-resistance, hidden service):
11409 - Introduction points no longer allow multiple INTRODUCE1 cells to
11410 arrive on the same circuit. This should make it more expensive for
11411 attackers to overwhelm hidden services with introductions.
11412 Resolves ticket 15515.
11415 Changes in version 0.2.6.7 - 2015-04-06
11416 Tor 0.2.6.7 fixes two security issues that could be used by an
11417 attacker to crash hidden services, or crash clients visiting hidden
11418 services. Hidden services should upgrade as soon as possible; clients
11419 should upgrade whenever packages become available.
11421 This release also contains two simple improvements to make hidden
11422 services a bit less vulnerable to denial-of-service attacks.
11424 o Major bugfixes (security, hidden service):
11425 - Fix an issue that would allow a malicious client to trigger an
11426 assertion failure and halt a hidden service. Fixes bug 15600;
11427 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
11428 - Fix a bug that could cause a client to crash with an assertion
11429 failure when parsing a malformed hidden service descriptor. Fixes
11430 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
11432 o Minor features (DoS-resistance, hidden service):
11433 - Introduction points no longer allow multiple INTRODUCE1 cells to
11434 arrive on the same circuit. This should make it more expensive for
11435 attackers to overwhelm hidden services with introductions.
11436 Resolves ticket 15515.
11437 - Decrease the amount of reattempts that a hidden service performs
11438 when its rendezvous circuits fail. This reduces the computational
11439 cost for running a hidden service under heavy load. Resolves
11443 Changes in version 0.2.6.6 - 2015-03-24
11444 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
11446 It adds numerous safety, security, correctness, and performance
11447 improvements. Client programs can be configured to use more kinds of
11448 sockets, AutomapHosts works better, the multithreading backend is
11449 improved, cell transmission is refactored, test coverage is much
11450 higher, more denial-of-service attacks are handled, guard selection is
11451 improved to handle long-term guards better, pluggable transports
11452 should work a bit better, and some annoying hidden service performance
11453 bugs should be addressed.
11455 o Minor bugfixes (portability):
11456 - Use the correct datatype in the SipHash-2-4 function to prevent
11457 compilers from assuming any sort of alignment. Fixes bug 15436;
11458 bugfix on 0.2.5.3-alpha.
11460 Changes in version 0.2.6.5-rc - 2015-03-18
11461 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
11462 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
11464 o Major bugfixes (client):
11465 - Avoid crashing when making certain configuration option changes on
11466 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
11469 o Major bugfixes (pluggable transports):
11470 - Initialize the extended OR Port authentication cookie before
11471 launching pluggable transports. This prevents a race condition
11472 that occurred when server-side pluggable transports would cache the
11473 authentication cookie before it has been (re)generated. Fixes bug
11474 15240; bugfix on 0.2.5.1-alpha.
11476 o Major bugfixes (portability):
11477 - Do not crash on startup when running on Solaris. Fixes a bug
11478 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
11481 o Minor features (heartbeat):
11482 - On relays, report how many connections we negotiated using each
11483 version of the Tor link protocols. This information will let us
11484 know if removing support for very old versions of the Tor
11485 protocols is harming the network. Closes ticket 15212.
11487 o Code simplification and refactoring:
11488 - Refactor main loop to extract the 'loop' part. This makes it
11489 easier to run Tor under Shadow. Closes ticket 15176.
11492 Changes in version 0.2.5.11 - 2015-03-17
11493 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
11495 It backports several bugfixes from the 0.2.6 branch, including a
11496 couple of medium-level security fixes for relays and exit nodes.
11497 It also updates the list of directory authorities.
11499 o Directory authority changes:
11500 - Remove turtles as a directory authority.
11501 - Add longclaw as a new (v3) directory authority. This implements
11502 ticket 13296. This keeps the directory authority count at 9.
11503 - The directory authority Faravahar has a new IP address. This
11504 closes ticket 14487.
11506 o Major bugfixes (crash, OSX, security):
11507 - Fix a remote denial-of-service opportunity caused by a bug in
11508 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
11511 o Major bugfixes (relay, stability, possible security):
11512 - Fix a bug that could lead to a relay crashing with an assertion
11513 failure if a buffer of exactly the wrong layout was passed to
11514 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
11515 0.2.0.10-alpha. Patch from 'cypherpunks'.
11516 - Do not assert if the 'data' pointer on a buffer is advanced to the
11517 very end of the buffer; log a BUG message instead. Only assert if
11518 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
11520 o Major bugfixes (exit node stability):
11521 - Fix an assertion failure that could occur under high DNS load.
11522 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
11523 diagnosed and fixed by "cypherpunks".
11525 o Major bugfixes (Linux seccomp2 sandbox):
11526 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
11527 crash during attempts to call wait4. Fixes bug 15088; bugfix on
11528 0.2.5.1-alpha. Patch from "sanic".
11530 o Minor features (controller):
11531 - New "GETINFO bw-event-cache" to get information about recent
11532 bandwidth events. Closes ticket 14128. Useful for controllers to
11533 get recent bandwidth history after the fix for ticket 13988.
11535 o Minor features (geoip):
11536 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
11537 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
11540 o Minor bugfixes (client, automapping):
11541 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
11542 no value follows the option. Fixes bug 14142; bugfix on
11543 0.2.4.7-alpha. Patch by "teor".
11544 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
11545 14195; bugfix on 0.1.0.1-rc.
11547 o Minor bugfixes (compilation):
11548 - Build without warnings with the stock OpenSSL srtp.h header, which
11549 has a duplicate declaration of SSL_get_selected_srtp_profile().
11550 Fixes bug 14220; this is OpenSSL's bug, not ours.
11552 o Minor bugfixes (directory authority):
11553 - Allow directory authorities to fetch more data from one another if
11554 they find themselves missing lots of votes. Previously, they had
11555 been bumping against the 10 MB queued data limit. Fixes bug 14261;
11556 bugfix on 0.1.2.5-alpha.
11557 - Enlarge the buffer to read bwauth generated files to avoid an
11558 issue when parsing the file in dirserv_read_measured_bandwidths().
11559 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
11561 o Minor bugfixes (statistics):
11562 - Increase period over which bandwidth observations are aggregated
11563 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
11565 o Minor bugfixes (preventative security, C safety):
11566 - When reading a hexadecimal, base-32, or base-64 encoded value from
11567 a string, always overwrite the whole output buffer. This prevents
11568 some bugs where we would look at (but fortunately, not reveal)
11569 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
11573 Changes in version 0.2.4.26 - 2015-03-17
11574 Tor 0.2.4.26 includes an updated list of directory authorities. It
11575 also backports a couple of stability and security bugfixes from 0.2.5
11578 o Directory authority changes:
11579 - Remove turtles as a directory authority.
11580 - Add longclaw as a new (v3) directory authority. This implements
11581 ticket 13296. This keeps the directory authority count at 9.
11582 - The directory authority Faravahar has a new IP address. This
11583 closes ticket 14487.
11585 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
11586 - Fix an assertion failure that could occur under high DNS load.
11587 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
11588 diagnosed and fixed by "cypherpunks".
11590 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
11591 - Fix a bug that could lead to a relay crashing with an assertion
11592 failure if a buffer of exactly the wrong layout was passed to
11593 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
11594 0.2.0.10-alpha. Patch from 'cypherpunks'.
11595 - Do not assert if the 'data' pointer on a buffer is advanced to the
11596 very end of the buffer; log a BUG message instead. Only assert if
11597 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
11599 o Minor features (geoip):
11600 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
11601 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
11604 Changes in version 0.2.6.4-rc - 2015-03-09
11605 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
11606 attacker might be able to use in order to crash certain Tor
11607 directories. It also resolves some minor issues left over from, or
11608 introduced in, Tor 0.2.6.3-alpha or earlier.
11610 o Major bugfixes (crash, OSX, security):
11611 - Fix a remote denial-of-service opportunity caused by a bug in
11612 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
11615 o Major bugfixes (relay, stability, possible security):
11616 - Fix a bug that could lead to a relay crashing with an assertion
11617 failure if a buffer of exactly the wrong layout is passed to
11618 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
11619 0.2.0.10-alpha. Patch from "cypherpunks".
11620 - Do not assert if the 'data' pointer on a buffer is advanced to the
11621 very end of the buffer; log a BUG message instead. Only assert if
11622 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
11624 o Major bugfixes (FreeBSD IPFW transparent proxy):
11625 - Fix address detection with FreeBSD transparent proxies, when
11626 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
11629 o Major bugfixes (Linux seccomp2 sandbox):
11630 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
11631 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
11633 - Allow AF_UNIX hidden services to be used with the seccomp2
11634 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
11635 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
11636 crash during attempts to call wait4. Fixes bug 15088; bugfix on
11637 0.2.5.1-alpha. Patch from "sanic".
11639 o Minor features (controller):
11640 - Messages about problems in the bootstrap process now include
11641 information about the server we were trying to connect to when we
11642 noticed the problem. Closes ticket 15006.
11644 o Minor features (geoip):
11645 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
11646 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
11649 o Minor features (logs):
11650 - Quiet some log messages in the heartbeat and at startup. Closes
11653 o Minor bugfixes (certificate handling):
11654 - If an authority operator accidentally makes a signing certificate
11655 with a future publication time, do not discard its real signing
11656 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
11657 - Remove any old authority certificates that have been superseded
11658 for at least two days. Previously, we would keep superseded
11659 certificates until they expired, if they were published close in
11660 time to the certificate that superseded them. Fixes bug 11454;
11661 bugfix on 0.2.1.8-alpha.
11663 o Minor bugfixes (compilation):
11664 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
11666 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
11669 o Minor bugfixes (testing):
11670 - Fix endianness issues in unit test for resolve_my_address() to
11671 have it pass on big endian systems. Fixes bug 14980; bugfix on
11673 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
11674 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
11675 - When running the new 'make test-stem' target, use the configured
11676 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
11677 from "cypherpunks".
11678 - When running the zero-length-keys tests, do not use the default
11679 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
11682 o Directory authority IP change:
11683 - The directory authority Faravahar has a new IP address. This
11684 closes ticket 14487.
11687 - Remove some lingering dead code that once supported mempools.
11688 Mempools were disabled by default in 0.2.5, and removed entirely
11689 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
11693 Changes in version 0.2.6.3-alpha - 2015-02-19
11694 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
11695 the 0.2.6.x series. It introduces support for more kinds of sockets,
11696 makes it harder to accidentally run an exit, improves our
11697 multithreading backend, incorporates several fixes for the
11698 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
11700 If no major regressions or security holes are found in this version,
11701 the next version will be a release candidate.
11703 o Deprecated versions:
11704 - Tor relays older than 0.2.4.18-rc are no longer allowed to
11705 advertise themselves on the network. Closes ticket 13555.
11707 o Major features (security, unix domain sockets):
11708 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
11709 applications can reach Tor without having to create AF_INET or
11710 AF_INET6 sockets, meaning they can completely disable their
11711 ability to make non-Tor network connections. To create a socket of
11712 this type, use "SocksPort unix:/path/to/socket". Implements
11714 - Support mapping hidden service virtual ports to AF_UNIX sockets.
11715 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
11716 Implements ticket 11485.
11718 o Major features (changed defaults):
11719 - Prevent relay operators from unintentionally running exits: When a
11720 relay is configured as an exit node, we now warn the user unless
11721 the "ExitRelay" option is set to 1. We warn even more loudly if
11722 the relay is configured with the default exit policy, since this
11723 can indicate accidental misconfiguration. Setting "ExitRelay 0"
11724 stops Tor from running as an exit relay. Closes ticket 10067.
11726 o Major features (directory system):
11727 - When downloading server- or microdescriptors from a directory
11728 server, we no longer launch multiple simultaneous requests to the
11729 same server. This reduces load on the directory servers,
11730 especially when directory guards are in use. Closes ticket 9969.
11731 - When downloading server- or microdescriptors over a tunneled
11732 connection, do not limit the length of our requests to what the
11733 Squid proxy is willing to handle. Part of ticket 9969.
11734 - Authorities can now vote on the correct digests and latest
11735 versions for different software packages. This allows packages
11736 that include Tor to use the Tor authority system as a way to get
11737 notified of updates and their correct digests. Implements proposal
11738 227. Closes ticket 10395.
11740 o Major features (guards):
11741 - Introduce the Guardfraction feature to improves load balancing on
11742 guard nodes. Specifically, it aims to reduce the traffic gap that
11743 guard nodes experience when they first get the Guard flag. This is
11744 a required step if we want to increase the guard lifetime to 9
11745 months or greater. Closes ticket 9321.
11747 o Major features (performance):
11748 - Make the CPU worker implementation more efficient by avoiding the
11749 kernel and lengthening pipelines. The original implementation used
11750 sockets to transfer data from the main thread to the workers, and
11751 didn't allow any thread to be assigned more than a single piece of
11752 work at once. The new implementation avoids communications
11753 overhead by making requests in shared memory, avoiding kernel IO
11754 where possible, and keeping more requests in flight at once.
11755 Implements ticket 9682.
11757 o Major features (relay):
11758 - Raise the minimum acceptable configured bandwidth rate for bridges
11759 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
11760 20 KiB/sec.) Closes ticket 13822.
11762 o Major bugfixes (exit node stability):
11763 - Fix an assertion failure that could occur under high DNS load.
11764 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
11765 diagnosed and fixed by "cypherpunks".
11767 o Major bugfixes (mixed relay-client operation):
11768 - When running as a relay and client at the same time (not
11769 recommended), if we decide not to use a new guard because we want
11770 to retry older guards, only close the locally-originating circuits
11771 passing through that guard. Previously we would close all the
11772 circuits through that guard. Fixes bug 9819; bugfix on
11773 0.2.1.1-alpha. Reported by "skruffy".
11775 o Minor features (build):
11776 - New --disable-system-torrc compile-time option to prevent Tor from
11777 looking for the system-wide torrc or torrc-defaults files.
11778 Resolves ticket 13037.
11780 o Minor features (controller):
11781 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
11782 events so controllers can observe circuit isolation inputs. Closes
11784 - ControlPort now supports the unix:/path/to/socket syntax as an
11785 alternative to the ControlSocket option, for consistency with
11786 SocksPort and HiddenServicePort. Closes ticket 14451.
11787 - New "GETINFO bw-event-cache" to get information about recent
11788 bandwidth events. Closes ticket 14128. Useful for controllers to
11789 get recent bandwidth history after the fix for ticket 13988.
11791 o Minor features (Denial of service resistance):
11792 - Count the total number of bytes used storing hidden service
11793 descriptors against the value of MaxMemInQueues. If we're low on
11794 memory, and more than 20% of our memory is used holding hidden
11795 service descriptors, free them until no more than 10% of our
11796 memory holds hidden service descriptors. Free the least recently
11797 fetched descriptors first. Resolves ticket 13806.
11798 - When we have recently been under memory pressure (over 3/4 of
11799 MaxMemInQueues is allocated), then allocate smaller zlib objects
11800 for small requests. Closes ticket 11791.
11802 o Minor features (geoip):
11803 - Update geoip and geoip6 files to the January 7 2015 Maxmind
11804 GeoLite2 Country database.
11806 o Minor features (guard nodes):
11807 - Reduce the time delay before saving guard status to disk from 10
11808 minutes to 30 seconds (or from one hour to 10 minutes if
11809 AvoidDiskWrites is set). Closes ticket 12485.
11811 o Minor features (hidden service):
11812 - Make Sybil attacks against hidden services harder by changing the
11813 minimum time required to get the HSDir flag from 25 hours up to 96
11814 hours. Addresses ticket 14149.
11815 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
11816 services to disable the anti-scanning feature introduced in
11817 0.2.6.2-alpha. With this option not set, a connection to an
11818 unlisted port closes the circuit. With this option set, only a
11819 RELAY_DONE cell is sent. Closes ticket 14084.
11821 o Minor features (interface):
11822 - Implement "-f -" command-line option to read torrc configuration
11823 from standard input, if you don't want to store the torrc file in
11824 the file system. Implements feature 13865.
11826 o Minor features (logging):
11827 - Add a count of unique clients to the bridge heartbeat message.
11828 Resolves ticket 6852.
11829 - Suppress "router info incompatible with extra info" message when
11830 reading extrainfo documents from cache. (This message got loud
11831 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
11833 - Elevate hidden service authorized-client message from DEBUG to
11834 INFO. Closes ticket 14015.
11836 o Minor features (stability):
11837 - Add assertions in our hash-table iteration code to check for
11838 corrupted values that could cause infinite loops. Closes
11841 o Minor features (systemd):
11842 - Various improvements and modernizations in systemd hardening
11843 support. Closes ticket 13805. Patch from Craig Andrews.
11845 o Minor features (testing networks):
11846 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
11847 and the default on a testing network to 2 minutes. Drop the
11848 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
11849 keep the default on a testing network at 30 seconds. This reduces
11850 HS bootstrap time to around 25 seconds. Also, change the default
11851 time in test-network.sh to match. Closes ticket 13401. Patch
11853 - Create TestingDirAuthVoteHSDir to correspond to
11854 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
11855 HSDir flag for the listed relays regardless of uptime or ORPort
11856 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
11857 Partial implementation for ticket 14067. Patch by "teor".
11859 o Minor features (tor2web mode):
11860 - Introduce the config option Tor2webRendezvousPoints, which allows
11861 clients in Tor2webMode to select a specific Rendezvous Point to be
11862 used in HS circuits. This might allow better performance for
11863 Tor2Web nodes. Implements ticket 12844.
11865 o Minor bugfixes (client DNS):
11866 - Report the correct cached DNS expiration times on SOCKS port or in
11867 DNS replies. Previously, we would report everything as "never
11868 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
11869 - Avoid a small memory leak when we find a cached answer for a
11870 reverse DNS lookup in a client-side DNS cache. (Remember, client-
11871 side DNS caching is off by default, and is not recommended.) Fixes
11872 bug 14259; bugfix on 0.2.0.1-alpha.
11874 o Minor bugfixes (client, automapping):
11875 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
11876 no value follows the option. Fixes bug 14142; bugfix on
11877 0.2.4.7-alpha. Patch by "teor".
11878 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
11879 14195; bugfix on 0.1.0.1-rc.
11880 - Prevent changes to other options from removing the wildcard value
11881 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
11883 - Allow MapAddress and AutomapHostsOnResolve to work together when
11884 an address is mapped into another address type (like .onion) that
11885 must be automapped at resolve time. Fixes bug 7555; bugfix
11888 o Minor bugfixes (client, bridges):
11889 - When we are using bridges and we had a network connectivity
11890 problem, only retry connecting to our currently configured
11891 bridges, not all bridges we know about and remember using. Fixes
11892 bug 14216; bugfix on 0.2.2.17-alpha.
11894 o Minor bugfixes (client, IPv6):
11895 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
11896 flag is not set; and not because the NoIPv4Traffic flag was set.
11897 Previously we'd looked at the NoIPv4Traffic flag for both types of
11898 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
11900 o Minor bugfixes (compilation):
11901 - The address of an array in the middle of a structure will always
11902 be non-NULL. clang recognises this and complains. Disable the
11903 tautologous and redundant check to silence this warning. Fixes bug
11904 14001; bugfix on 0.2.1.2-alpha.
11905 - Avoid warnings when building with systemd 209 or later. Fixes bug
11906 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
11907 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
11908 Addresses ticket 14188.
11909 - Build without warnings with the stock OpenSSL srtp.h header, which
11910 has a duplicate declaration of SSL_get_selected_srtp_profile().
11911 Fixes bug 14220; this is OpenSSL's bug, not ours.
11912 - Do not compile any code related to Tor2Web mode when Tor2Web mode
11913 is not enabled at compile time. Previously, this code was included
11914 in a disabled state. See discussion on ticket 12844.
11915 - Remove the --disable-threads configure option again. It was
11916 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
11917 14819; bugfix on 0.2.6.2-alpha.
11919 o Minor bugfixes (controller):
11920 - Report "down" in response to the "GETINFO entry-guards" command
11921 when relays are down with an unreachable_since value. Previously,
11922 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
11923 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
11924 14116; bugfix on 0.2.2.9-alpha.
11925 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
11926 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
11928 o Minor bugfixes (directory authority):
11929 - Allow directory authorities to fetch more data from one another if
11930 they find themselves missing lots of votes. Previously, they had
11931 been bumping against the 10 MB queued data limit. Fixes bug 14261;
11932 bugfix on 0.1.2.5-alpha.
11933 - Do not attempt to download extrainfo documents which we will be
11934 unable to validate with a matching server descriptor. Fixes bug
11935 13762; bugfix on 0.2.0.1-alpha.
11936 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
11937 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
11938 - Enlarge the buffer to read bwauth generated files to avoid an
11939 issue when parsing the file in dirserv_read_measured_bandwidths().
11940 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
11942 o Minor bugfixes (file handling):
11943 - Stop failing when key files are zero-length. Instead, generate new
11944 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
11945 on all versions of Tor. Patch by "teor".
11946 - Stop generating a fresh .old RSA onion key file when the .old file
11947 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
11948 - Avoid overwriting .old key files with empty key files.
11949 - Skip loading zero-length extrainfo store, router store, stats,
11950 state, and key files.
11951 - Avoid crashing when trying to reload a torrc specified as a
11952 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
11955 o Minor bugfixes (hidden services):
11956 - Close the introduction circuit when we have no more usable intro
11957 points, instead of waiting for it to time out. This also ensures
11958 that no follow-up HS descriptor fetch is triggered when the
11959 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
11960 - When fetching a hidden service descriptor for a down service that
11961 was recently up, do not keep refetching until we try the same
11962 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
11963 - Successfully launch Tor with a nonexistent hidden service
11964 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
11965 14106; bugfix on 0.2.6.2-alpha.
11967 o Minor bugfixes (logging):
11968 - Avoid crashing when there are more log domains than entries in
11969 domain_list. Bugfix on 0.2.3.1-alpha.
11970 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
11972 - Don't log messages to stdout twice when starting up. Fixes bug
11973 13993; bugfix on 0.2.6.1-alpha.
11975 o Minor bugfixes (parsing):
11976 - Stop accepting milliseconds (or other junk) at the end of
11977 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
11978 - Support two-number and three-number version numbers correctly, in
11979 case we change the Tor versioning system in the future. Fixes bug
11980 13661; bugfix on 0.0.8pre1.
11982 o Minor bugfixes (path counting):
11983 - When deciding whether the consensus lists any exit nodes, count
11984 the number listed in the consensus, not the number we have
11985 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
11986 - When deciding whether we have any exit nodes, only examine
11987 ExitNodes when the ExitNodes option is actually set. Fixes part of
11988 bug 14918; bugfix on 0.2.6.2-alpha.
11989 - Get rid of redundant and possibly scary warnings that we are
11990 missing directory information while we bootstrap. Fixes part of
11991 bug 14918; bugfix on 0.2.6.2-alpha.
11993 o Minor bugfixes (portability):
11994 - Fix the ioctl()-based network interface lookup code so that it
11995 will work on systems that have variable-length struct ifreq, for
11997 - Fix scheduler compilation on targets where char is unsigned. Fixes
11998 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
12000 o Minor bugfixes (sandbox):
12001 - Allow glibc fatal errors to be sent to stderr before Tor exits.
12002 Previously, glibc would try to write them to /dev/tty, and the
12003 sandbox would trap the call and make Tor exit prematurely. Fixes
12004 bug 14759; bugfix on 0.2.5.1-alpha.
12006 o Minor bugfixes (shutdown):
12007 - When shutting down, always call event_del() on lingering read or
12008 write events before freeing them. Otherwise, we risk double-frees
12009 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
12012 o Minor bugfixes (small memory leaks):
12013 - Avoid leaking memory when using IPv6 virtual address mappings.
12014 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
12017 o Minor bugfixes (statistics):
12018 - Increase period over which bandwidth observations are aggregated
12019 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
12021 o Minor bugfixes (systemd support):
12022 - Fix detection and operation of systemd watchdog. Fixes part of bug
12023 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
12024 - Run correctly under systemd with the RunAsDaemon option set. Fixes
12025 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
12026 - Inform the systemd supervisor about more changes in the Tor
12027 process status. Implements part of ticket 14141. Patch from
12029 - Cause the "--disable-systemd" option to actually disable systemd
12030 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
12033 o Minor bugfixes (TLS):
12034 - Check more thoroughly throughout the TLS code for possible
12035 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
12037 o Minor bugfixes (transparent proxy):
12038 - Use getsockname, not getsockopt, to retrieve the address for a
12039 TPROXY-redirected connection. Fixes bug 13796; bugfix
12042 o Code simplification and refactoring:
12043 - Move fields related to isolating and configuring client ports into
12044 a shared structure. Previously, they were duplicated across
12045 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
12046 to copy them correctly had been the cause of at least one bug in
12047 the past. Closes ticket 8546.
12048 - Refactor the get_interface_addresses_raw() doom-function into
12049 multiple smaller and simpler subfunctions. Cover the resulting
12050 subfunctions with unit-tests. Fixes a significant portion of
12052 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
12053 only for version <= 0.2.2.24 which is now deprecated. Closes
12055 - Remove a test for a long-defunct broken version-one
12059 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
12060 for writing the OpenBSD-specific tips. Resolves ticket 13702.
12061 - Make the tor-resolve documentation match its help string and its
12062 options. Resolves part of ticket 14325.
12063 - Log a more useful error message from tor-resolve when failing to
12064 look up a hidden service address. Resolves part of ticket 14325.
12066 o Downgraded warnings:
12067 - Don't warn when we've attempted to contact a relay using the wrong
12068 ntor onion key. Closes ticket 9635.
12070 o Removed features:
12071 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
12072 longer silently accepted as an alias for "ExitNodes".
12073 - The --enable-mempool and --enable-buf-freelists options, which
12074 were originally created to work around bad malloc implementations,
12075 no longer exist. They were off-by-default in 0.2.5. Closes
12079 - Make the checkdir/perms test complete successfully even if the
12080 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
12081 - Test that tor does not fail when key files are zero-length. Check
12082 that tor generates new keys, and overwrites the empty key files.
12083 - Test that tor generates new keys when keys are missing
12084 (existing behavior).
12085 - Test that tor does not overwrite key files that already contain
12086 data (existing behavior). Tests bug 13111. Patch by "teor".
12087 - New "make test-stem" target to run stem integration tests.
12088 Requires that the "STEM_SOURCE_DIR" environment variable be set.
12089 Closes ticket 14107.
12090 - Make the test_cmdline_args.py script work correctly on Windows.
12091 Patch from Gisle Vanem.
12092 - Move the slower unit tests into a new "./src/test/test-slow"
12093 binary that can be run independently of the other tests. Closes
12095 - Avoid undefined behavior when sampling huge values from the
12096 Laplace distribution. This made unittests fail on Raspberry Pi.
12097 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
12100 Changes in version 0.2.6.2-alpha - 2014-12-31
12101 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
12102 It introduces a major new backend for deciding when to send cells on
12103 channels, which should lead down the road to big performance
12104 increases. It contains security and statistics features for better
12105 work on hidden services, and numerous bugfixes.
12107 This release contains many new unit tests, along with major
12108 performance improvements for running testing networks using Chutney.
12109 Thanks to a series of patches contributed by "teor", testing networks
12110 should now bootstrap in seconds, rather than minutes.
12112 o Major features (relay, infrastructure):
12113 - Complete revision of the code that relays use to decide which cell
12114 to send next. Formerly, we selected the best circuit to write on
12115 each channel, but we didn't select among channels in any
12116 sophisticated way. Now, we choose the best circuits globally from
12117 among those whose channels are ready to deliver traffic.
12119 This patch implements a new inter-cmux comparison API, a global
12120 high/low watermark mechanism and a global scheduler loop for
12121 transmission prioritization across all channels as well as among
12122 circuits on one channel. This schedule is currently tuned to
12123 (tolerantly) avoid making changes in network performance, but it
12124 should form the basis for major circuit performance increases in
12125 the future. Code by Andrea; tuning by Rob Jansen; implements
12128 o Major features (hidden services):
12129 - Make HS port scanning more difficult by immediately closing the
12130 circuit when a user attempts to connect to a nonexistent port.
12131 Closes ticket 13667.
12132 - Add a HiddenServiceStatistics option that allows Tor relays to
12133 gather and publish statistics about the overall size and volume of
12134 hidden service usage. Specifically, when this option is turned on,
12135 an HSDir will publish an approximate number of hidden services
12136 that have published descriptors to it the past 24 hours. Also, if
12137 a relay has acted as a hidden service rendezvous point, it will
12138 publish the approximate amount of rendezvous cells it has relayed
12139 the past 24 hours. The statistics themselves are obfuscated so
12140 that the exact values cannot be derived. For more details see
12141 proposal 238, "Better hidden service stats from Tor relays". This
12142 feature is currently disabled by default. Implements feature 13192.
12144 o Major bugfixes (client, automap):
12145 - Repair automapping with IPv6 addresses. This automapping should
12146 have worked previously, but one piece of debugging code that we
12147 inserted to detect a regression actually caused the regression to
12148 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
12149 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
12152 o Major bugfixes (hidden services):
12153 - When closing an introduction circuit that was opened in parallel
12154 with others, don't mark the introduction point as unreachable.
12155 Previously, the first successful connection to an introduction
12156 point would make the other introduction points get marked as
12157 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
12159 o Directory authority changes:
12160 - Remove turtles as a directory authority.
12161 - Add longclaw as a new (v3) directory authority. This implements
12162 ticket 13296. This keeps the directory authority count at 9.
12164 o Major removed features:
12165 - Tor clients no longer support connecting to hidden services
12166 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
12167 option has been removed. (There shouldn't be any hidden services
12168 running these versions on the network.) Closes ticket 7803.
12170 o Minor features (client):
12171 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
12172 is enabled, reject requests with IP addresses as hostnames.
12173 Resolves ticket 13315.
12175 o Minor features (controller):
12176 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
12177 write an unscheduled heartbeat message to the log. Implements
12180 o Minor features (geoip):
12181 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
12184 o Minor features (hidden services):
12185 - When re-enabling the network, don't try to build introduction
12186 circuits until we have successfully built a circuit. This makes
12187 hidden services come up faster when the network is re-enabled.
12188 Patch from "akwizgran". Closes ticket 13447.
12189 - When we fail to retrieve a hidden service descriptor, send the
12190 controller an "HS_DESC FAILED" controller event. Implements
12192 - New HiddenServiceDirGroupReadable option to cause hidden service
12193 directories and hostname files to be created group-readable. Patch
12194 from "anon", David Stainton, and "meejah". Closes ticket 11291.
12196 o Minor features (systemd):
12197 - Where supported, when running with systemd, report successful
12198 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
12199 - When running with systemd, support systemd watchdog messages. Part
12200 of ticket 11016. Patch by Michael Scherer.
12202 o Minor features (transparent proxy):
12203 - Update the transparent proxy option checks to allow for both ipfw
12204 and pf on OS X. Closes ticket 14002.
12205 - Use the correct option when using IPv6 with transparent proxy
12206 support on Linux. Resolves 13808. Patch by Francisco Blas
12209 o Minor bugfixes (preventative security, C safety):
12210 - When reading a hexadecimal, base-32, or base-64 encoded value from
12211 a string, always overwrite the whole output buffer. This prevents
12212 some bugs where we would look at (but fortunately, not reveal)
12213 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
12215 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
12216 just the part that's used. This makes it harder for data leak bugs
12217 to occur in the event of other programming failures. Resolves
12220 o Minor bugfixes (client, microdescriptors):
12221 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
12222 computing which microdescriptors to download. This keeps us from
12223 erroneous download behavior if two microdescriptor digests ever
12224 have the same first 160 bits. Fixes part of bug 13399; bugfix
12226 - Reset a router's status if its microdescriptor digest changes,
12227 even if the first 160 bits remain the same. Fixes part of bug
12228 13399; bugfix on 0.2.3.1-alpha.
12230 o Minor bugfixes (compilation):
12231 - Silence clang warnings under --enable-expensive-hardening,
12232 including implicit truncation of 64 bit values to 32 bit, const
12233 char assignment to self, tautological compare, and additional
12234 parentheses around equality tests. Fixes bug 13577; bugfix
12236 - Fix a clang warning about checking whether an address in the
12237 middle of a structure is NULL. Fixes bug 14001; bugfix
12240 o Minor bugfixes (hidden services):
12241 - Correctly send a controller event when we find that a rendezvous
12242 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
12243 - Pre-check directory permissions for new hidden-services to avoid
12244 at least one case of "Bug: Acting on config options left us in a
12245 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
12246 - When adding a new hidden service (for example, via SETCONF), Tor
12247 no longer congratulates the user for running a relay. Fixes bug
12248 13941; bugfix on 0.2.6.1-alpha.
12249 - When fetching hidden service descriptors, we now check not only
12250 for whether we got the hidden service we had in mind, but also
12251 whether we got the particular descriptors we wanted. This prevents
12252 a class of inefficient but annoying DoS attacks by hidden service
12253 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
12256 o Minor bugfixes (Linux seccomp2 sandbox):
12257 - Make transparent proxy support work along with the seccomp2
12258 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
12259 by Francisco Blas Izquierdo Riera.
12260 - Fix a memory leak in tor-resolve when running with the sandbox
12261 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
12263 o Minor bugfixes (logging):
12264 - Downgrade warnings about RSA signature failures to info log level.
12265 Emit a warning when an extra info document is found incompatible
12266 with a corresponding router descriptor. Fixes bug 9812; bugfix
12268 - Make connection_ap_handshake_attach_circuit() log the circuit ID
12269 correctly. Fixes bug 13701; bugfix on 0.0.6.
12271 o Minor bugfixes (misc):
12272 - Stop allowing invalid address patterns like "*/24" that contain
12273 both a wildcard address and a bit prefix length. This affects all
12274 our address-range parsing code. Fixes bug 7484; bugfix
12277 o Minor bugfixes (testing networks, fast startup):
12278 - Allow Tor to build circuits using a consensus with no exits. If
12279 the consensus has no exits (typical of a bootstrapping test
12280 network), allow Tor to build circuits once enough descriptors have
12281 been downloaded. This assists in bootstrapping a testing Tor
12282 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
12284 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
12285 header to directory servers. This allows us to obtain consensuses
12286 promptly when the consensus interval is very short. This assists
12287 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
12288 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
12289 - Stop assuming that private addresses are local when checking
12290 reachability in a TestingTorNetwork. Instead, when testing, assume
12291 all OR connections are remote. (This is necessary due to many test
12292 scenarios running all relays on localhost.) This assists in
12293 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
12294 0.1.0.1-rc. Patch by "teor".
12295 - Avoid building exit circuits from a consensus with no exits. Now
12296 thanks to our fix for 13718, we accept a no-exit network as not
12297 wholly lost, but we need to remember not to try to build exit
12298 circuits on it. Closes ticket 13814; patch by "teor".
12299 - Stop requiring exits to have non-zero bandwithcapacity in a
12300 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
12301 ignore exit bandwidthcapacity. This assists in bootstrapping a
12302 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
12303 on 0.2.0.3-alpha. Patch by "teor".
12304 - Add "internal" to some bootstrap statuses when no exits are
12305 available. If the consensus does not contain Exits, Tor will only
12306 build internal circuits. In this case, relevant statuses will
12307 contain the word "internal" as indicated in the Tor control-
12308 spec.txt. When bootstrap completes, Tor will be ready to build
12309 internal circuits. If a future consensus contains Exits, exit
12310 circuits may become available. Fixes part of bug 13718; bugfix on
12311 0.2.4.10-alpha. Patch by "teor".
12312 - Decrease minimum consensus interval to 10 seconds when
12313 TestingTorNetwork is set, or 5 seconds for the first consensus.
12314 Fix assumptions throughout the code that assume larger intervals.
12315 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
12317 - Avoid excluding guards from path building in minimal test
12318 networks, when we're in a test network and excluding guards would
12319 exclude all relays. This typically occurs in incredibly small tor
12320 networks, and those using "TestingAuthVoteGuard *". Fixes part of
12321 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
12323 o Code simplification and refactoring:
12324 - Stop using can_complete_circuits as a global variable; access it
12325 with a function instead.
12326 - Avoid using operators directly as macro arguments: this lets us
12327 apply coccinelle transformations to our codebase more directly.
12328 Closes ticket 13172.
12329 - Combine the functions used to parse ClientTransportPlugin and
12330 ServerTransportPlugin into a single function. Closes ticket 6456.
12331 - Add inline functions and convenience macros for inspecting channel
12332 state. Refactor the code to use convenience macros instead of
12333 checking channel state directly. Fixes issue 7356.
12334 - Document all members of was_router_added_t and rename
12335 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
12336 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
12337 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
12338 constant instead of hardcoded value. Fixes issue 13840.
12339 - Refactor our generic strmap and digestmap types into a single
12340 implementation, so that we can add a new digest256map
12344 - Document the bridge-authority-only 'networkstatus-bridges' file.
12345 Closes ticket 13713; patch from "tom".
12346 - Fix typo in PredictedPortsRelevanceTime option description in
12347 manpage. Resolves issue 13707.
12348 - Stop suggesting that users specify relays by nickname: it isn't a
12349 good idea. Also, properly cross-reference how to specify relays in
12350 all parts of manual documenting options that take a list of
12351 relays. Closes ticket 13381.
12352 - Clarify the HiddenServiceDir option description in manpage to make
12353 it clear that relative paths are taken with respect to the current
12354 working directory. Also clarify that this behavior is not
12355 guaranteed to remain indefinitely. Fixes issue 13913.
12358 - New tests for many parts of channel, relay, and circuitmux
12359 functionality. Code by Andrea; part of 9262.
12360 - New tests for parse_transport_line(). Part of ticket 6456.
12361 - In the unit tests, use chgrp() to change the group of the unit
12362 test temporary directory to the current user, so that the sticky
12363 bit doesn't interfere with tests that check directory groups.
12365 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
12369 Changes in version 0.2.6.1-alpha - 2014-10-30
12370 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
12371 includes numerous code cleanups and new tests, and fixes a large
12372 number of annoying bugs. Out-of-memory conditions are handled better
12373 than in 0.2.5, pluggable transports have improved proxy support, and
12374 clients now use optimistic data for contacting hidden services. Also,
12375 we are now more robust to changes in what we consider a parseable
12376 directory object, so that tightening restrictions does not have a risk
12377 of introducing infinite download loops.
12379 This is the first alpha release in a new series, so expect there to be
12380 bugs. Users who would rather test out a more stable branch should stay
12381 with 0.2.5.x for now.
12383 o New compiler and system requirements:
12384 - Tor 0.2.6.x requires that your compiler support more of the C99
12385 language standard than before. The 'configure' script now detects
12386 whether your compiler supports C99 mid-block declarations and
12387 designated initializers. If it does not, Tor will not compile.
12389 We may revisit this requirement if it turns out that a significant
12390 number of people need to build Tor with compilers that don't
12391 bother implementing a 15-year-old standard. Closes ticket 13233.
12392 - Tor no longer supports systems without threading support. When we
12393 began working on Tor, there were several systems that didn't have
12394 threads, or where the thread support wasn't able to run the
12395 threads of a single process on multiple CPUs. That no longer
12396 holds: every system where Tor needs to run well now has threading
12397 support. Resolves ticket 12439.
12399 o Removed platform support:
12400 - We no longer include special code to build on Windows CE; as far
12401 as we know, nobody has used Tor on Windows CE in a very long time.
12402 Closes ticket 11446.
12404 o Major features (bridges):
12405 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
12406 transports if they are configured via the "TOR_PT_PROXY"
12407 environment variable. Implements proposal 232. Resolves
12410 o Major features (client performance, hidden services):
12411 - Allow clients to use optimistic data when connecting to a hidden
12412 service, which should remove a round-trip from hidden service
12413 initialization. See proposal 181 for details. Implements
12416 o Major features (directory system):
12417 - Upon receiving an unparseable directory object, if its digest
12418 matches what we expected, then don't try to download it again.
12419 Previously, when we got a descriptor we didn't like, we would keep
12420 trying to download it over and over. Closes ticket 11243.
12422 o Major features (sample torrc):
12423 - Add a new, infrequently-changed "torrc.minimal". This file is
12424 similar to torrc.sample, but it will change as infrequently as
12425 possible, for the benefit of users whose systems prompt them for
12426 intervention whenever a default configuration file is changed.
12427 Making this change allows us to update torrc.sample to be a more
12428 generally useful "sample torrc".
12430 o Major bugfixes (directory authorities):
12431 - Do not assign the HSDir flag to relays if they are not Valid, or
12432 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
12434 o Major bugfixes (directory bandwidth performance):
12435 - Don't flush the zlib buffer aggressively when compressing
12436 directory information for clients. This should save about 7% of
12437 the bandwidth currently used for compressed descriptors and
12438 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
12440 o Minor features (security, memory wiping):
12441 - Ensure we securely wipe keys from memory after
12442 crypto_digest_get_digest and init_curve25519_keypair_from_file
12443 have finished using them. Resolves ticket 13477.
12445 o Minor features (security, out-of-memory handling):
12446 - When handling an out-of-memory condition, allocate less memory for
12447 temporary data structures. Fixes issue 10115.
12448 - When handling an out-of-memory condition, consider more types of
12449 buffers, including those on directory connections, and zlib
12450 buffers. Resolves ticket 11792.
12453 - When identity keypair is generated for first time, log a
12454 congratulatory message that links to the new relay lifecycle
12455 document. Implements feature 10427.
12457 o Minor features (client):
12458 - Clients are now willing to send optimistic data (before they
12459 receive a 'connected' cell) to relays of any version. (Relays
12460 without support for optimistic data are no longer supported on the
12461 Tor network.) Resolves ticket 13153.
12463 o Minor features (directory authorities):
12464 - Don't list relays with a bandwidth estimate of 0 in the consensus.
12465 Implements a feature proposed during discussion of bug 13000.
12466 - In tor-gencert, report an error if the user provides the same
12467 argument more than once.
12468 - If a directory authority can't find a best consensus method in the
12469 votes that it holds, it now falls back to its favorite consensus
12470 method. Previously, it fell back to method 1. Neither of these is
12471 likely to get enough signatures, but "fall back to favorite"
12472 doesn't require us to maintain support an obsolete consensus
12473 method. Implements part of proposal 215.
12475 o Minor features (logging):
12476 - On Unix-like systems, you can now use named pipes as the target of
12477 the Log option, and other options that try to append to files.
12478 Closes ticket 12061. Patch from "carlo von lynX".
12479 - When opening a log file at startup, send it every log message that
12480 we generated between startup and opening it. Previously, log
12481 messages that were generated before opening the log file were only
12482 logged to stdout. Closes ticket 6938.
12483 - Add a TruncateLogFile option to overwrite logs instead of
12484 appending to them. Closes ticket 5583.
12486 o Minor features (portability, Solaris):
12487 - Threads are no longer disabled by default on Solaris; we believe
12488 that the versions of Solaris with broken threading support are all
12489 obsolete by now. Resolves ticket 9495.
12491 o Minor features (relay):
12492 - Re-check our address after we detect a changed IP address from
12493 getsockname(). This ensures that the controller command "GETINFO
12494 address" will report the correct value. Resolves ticket 11582.
12496 - A new AccountingRule option lets Relays set whether they'd like
12497 AccountingMax to be applied separately to inbound and outbound
12498 traffic, or applied to the sum of inbound and outbound traffic.
12499 Resolves ticket 961. Patch by "chobe".
12501 o Minor features (testing networks):
12502 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
12503 the "Exit" flag regardless of their uptime, bandwidth, or exit
12504 policy. TestingTorNetwork must be set for this option to have any
12505 effect. Previously, authorities would take up to 35 minutes to
12506 give nodes the Exit flag in a test network. Partially implements
12509 o Minor features (validation):
12510 - Check all date/time values passed to tor_timegm and
12511 parse_rfc1123_time for validity, taking leap years into account.
12512 Improves HTTP header validation. Implemented with bug 13476.
12513 - In correct_tm(), limit the range of values returned by system
12514 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
12515 This means we don't have to deal with negative or too large dates,
12516 even if a clock is wrong. Otherwise we might fail to read a file
12517 written by us which includes such a date. Fixes bug 13476.
12519 o Minor bugfixes (bridge clients):
12520 - When configured to use a bridge without an identity digest (not
12521 recommended), avoid launching an extra channel to it when
12522 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
12524 o Minor bugfixes (bridges):
12525 - When DisableNetwork is set, do not launch pluggable transport
12526 plugins, and if any are running, terminate them. Fixes bug 13213;
12527 bugfix on 0.2.3.6-alpha.
12529 o Minor bugfixes (C correctness):
12530 - Fix several instances of possible integer overflow/underflow/NaN.
12531 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
12533 - In circuit_build_times_calculate_timeout() in circuitstats.c,
12534 avoid dividing by zero in the pareto calculations. This traps
12535 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
12537 - Fix an integer overflow in format_time_interval(). Fixes bug
12538 13393; bugfix on 0.2.0.10-alpha.
12539 - Set the correct day of year value when the system's localtime(_r)
12540 or gmtime(_r) functions fail to set struct tm. Not externally
12541 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
12542 - Avoid unlikely signed integer overflow in tor_timegm on systems
12543 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
12545 o Minor bugfixes (client):
12546 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
12547 BadExit flag are not considered worthy candidates. Fixes bug
12548 13066; bugfix on 0.1.2.3-alpha.
12549 - Use the consensus schedule for downloading consensuses, and not
12550 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
12551 - Handle unsupported or malformed SOCKS5 requests properly by
12552 responding with the appropriate error message before closing the
12553 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
12555 o Minor bugfixes (client, torrc):
12556 - Stop modifying the value of our DirReqStatistics torrc option just
12557 because we're not a bridge or relay. This bug was causing Tor
12558 Browser users to write "DirReqStatistics 0" in their torrc files
12559 as if they had chosen to change the config. Fixes bug 4244; bugfix
12561 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
12562 that our options have changed every time we SIGHUP. Fixes bug
12563 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
12565 o Minor bugfixes (controller):
12566 - Return an error when the second or later arguments of the
12567 "setevents" controller command are invalid events. Previously we
12568 would return success while silently skipping invalid events. Fixes
12569 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
12571 o Minor bugfixes (directory system):
12572 - Always believe that v3 directory authorities serve extra-info
12573 documents, whether they advertise "caches-extra-info" or not.
12574 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
12575 - When running as a v3 directory authority, advertise that you serve
12576 extra-info documents so that clients who want them can find them
12577 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
12578 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
12579 Previously, directories offering BRIDGE_DIRINFO and some other
12580 flag (i.e. microdescriptors or extrainfo) would be ignored when
12581 looking for bridges. Partially fixes bug 13163; bugfix
12584 o Minor bugfixes (networking):
12585 - Check for orconns and use connection_or_close_for_error() rather
12586 than connection_mark_for_close() directly in the getsockopt()
12587 failure case of connection_handle_write_impl(). Fixes bug 11302;
12588 bugfix on 0.2.4.4-alpha.
12590 o Minor bugfixes (relay):
12591 - When generating our family list, remove spaces from around the
12592 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
12593 - If our previous bandwidth estimate was 0 bytes, allow publishing a
12594 new relay descriptor immediately. Fixes bug 13000; bugfix
12597 o Minor bugfixes (testing networks):
12598 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
12599 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
12600 - Stop using the default authorities in networks which provide both
12601 AlternateDirAuthority and AlternateBridgeAuthority. Partially
12602 fixes bug 13163; bugfix on 0.2.0.13-alpha.
12604 o Minor bugfixes (testing):
12605 - Stop spawn test failures due to a race condition between the
12606 SIGCHLD handler updating the process status, and the test reading
12607 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
12609 o Minor bugfixes (testing, Windows):
12610 - Avoid passing an extra backslash when creating a temporary
12611 directory for running the unit tests on Windows. Fixes bug 12392;
12612 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
12614 o Minor bugfixes (windows):
12615 - Remove code to special-case handling of NTE_BAD_KEYSET when
12616 acquiring windows CryptoAPI context. This error can't actually
12617 occur for the parameters we're providing. Fixes bug 10816; bugfix
12620 o Minor bugfixes (zlib):
12621 - Avoid truncating a zlib stream when trying to finalize it with an
12622 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
12625 - Allow our configure script to build correctly with autoconf 2.62
12626 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
12627 - Improve the error message from ./configure to make it clear that
12628 when asciidoc has not been found, the user will have to either add
12629 --disable-asciidoc argument or install asciidoc. Resolves
12632 o Code simplification and refactoring:
12633 - Change the entry_is_live() function to take named bitfield
12634 elements instead of an unnamed list of booleans. Closes
12636 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
12637 Resolves ticket 12205.
12638 - Use calloc and reallocarray functions instead of multiply-
12639 then-malloc. This makes it less likely for us to fall victim to an
12640 integer overflow attack when allocating. Resolves ticket 12855.
12641 - Use the standard macro name SIZE_MAX, instead of our
12643 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
12644 functions which take them as arguments. Replace 0 with NO_DIRINFO
12645 in a function call for clarity. Seeks to prevent future issues
12647 - Avoid 4 null pointer errors under clang static analysis by using
12648 tor_assert() to prove that the pointers aren't null. Fixes
12650 - Rework the API of policies_parse_exit_policy() to use a bitmask to
12651 represent parsing options, instead of a confusing mess of
12652 booleans. Resolves ticket 8197.
12653 - Introduce a helper function to parse ExitPolicy in
12654 or_options_t structure.
12657 - Add a doc/TUNING document with tips for handling large numbers of
12658 TCP connections when running busy Tor relay. Update the warning
12659 message to point to this file when running out of sockets
12660 operating system is allowing to use simultaneously. Resolves
12663 o Removed features:
12664 - We no longer remind the user about configuration options that have
12665 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
12666 - Remove our old, non-weighted bandwidth-based node selection code.
12667 Previously, we used it as a fallback when we couldn't perform
12668 weighted bandwidth-based node selection. But that would only
12669 happen in the cases where we had no consensus, or when we had a
12670 consensus generated by buggy or ancient directory authorities. In
12671 either case, it's better to use the more modern, better maintained
12672 algorithm, with reasonable defaults for the weights. Closes
12674 - Remove the --disable-curve25519 configure option. Relays and
12675 clients now are required to support curve25519 and the
12677 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
12678 used to be deprecated synonyms for "StrictNodes", are now marked
12679 obsolete. Resolves ticket 12226.
12680 - Clients don't understand the BadDirectory flag in the consensus
12681 anymore, and ignore it.
12684 - Refactor the function that chooses guard nodes so that it can more
12685 easily be tested; write some tests for it.
12686 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
12687 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
12688 - Create unit tests for format_time_interval(). With bug 13393.
12689 - Add unit tests for tor_timegm signed overflow, tor_timegm and
12690 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
12691 tests (visible) fixes in bug 13476.
12692 - Add a "coverage-html" make target to generate HTML-visualized
12693 coverage results when building with --enable-coverage. (Requires
12694 lcov.) Patch from Kevin Murray.
12695 - Enable the backtrace handler (where supported) when running the
12697 - Revise all unit tests that used the legacy test_* macros to
12698 instead use the recommended tt_* macros. This patch was generated
12699 with coccinelle, to avoid manual errors. Closes ticket 13119.
12701 o Distribution (systemd):
12702 - systemd unit file: only allow tor to write to /var/lib/tor and
12703 /var/log/tor. The rest of the filesystem is accessible for reading
12704 only. Patch by intrigeri; resolves ticket 12751.
12705 - systemd unit file: ensure that the process and all its children
12706 can never gain new privileges. Patch by intrigeri; resolves
12708 - systemd unit file: set up /var/run/tor as writable for the Tor
12709 service. Patch by intrigeri; resolves ticket 13196.
12711 o Removed features (directory authorities):
12712 - Remove code that prevented authorities from listing Tor relays
12713 affected by CVE-2011-2769 as guards. These relays are already
12714 rejected altogether due to the minimum version requirement of
12715 0.2.3.16-alpha. Closes ticket 13152.
12716 - The "AuthDirRejectUnlisted" option no longer has any effect, as
12717 the fingerprints file (approved-routers) has been deprecated.
12718 - Directory authorities do not support being Naming dirauths anymore.
12719 The "NamingAuthoritativeDir" config option is now obsolete.
12720 - Directory authorities do not support giving out the BadDirectory
12722 - Directory authorities no longer advertise or support consensus
12723 methods 1 through 12 inclusive. These consensus methods were
12724 obsolete and/or insecure: maintaining the ability to support them
12725 served no good purpose. Implements part of proposal 215; closes
12728 o Testing (test-network.sh):
12729 - Stop using "echo -n", as some shells' built-in echo doesn't
12730 support "-n". Instead, use "/bin/echo -n". Partially fixes
12732 - Stop an apparent test-network hang when used with make -j2. Fixes
12734 - Add a --delay option to test-network.sh, which configures the
12735 delay before the chutney network tests for data transmission.
12736 Partially implements ticket 13161.
12739 Changes in version 0.2.5.10 - 2014-10-24
12740 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
12742 It adds several new security features, including improved
12743 denial-of-service resistance for relays, new compiler hardening
12744 options, and a system-call sandbox for hardened installations on Linux
12745 (requires seccomp2). The controller protocol has several new features,
12746 resolving IPv6 addresses should work better than before, and relays
12747 should be a little more CPU-efficient. We've added support for more
12748 OpenBSD and FreeBSD transparent proxy types. We've improved the build
12749 system and testing infrastructure to allow unit testing of more parts
12750 of the Tor codebase. Finally, we've addressed several nagging pluggable
12751 transport usability issues, and included numerous other small bugfixes
12752 and features mentioned below.
12754 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
12755 have accumulated many known flaws; everyone should upgrade.
12757 o Deprecated versions:
12758 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
12759 attention for some while.
12762 Changes in version 0.2.5.9-rc - 2014-10-20
12763 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
12764 series. It disables SSL3 in response to the recent "POODLE" attack
12765 (even though POODLE does not affect Tor). It also works around a crash
12766 bug caused by some operating systems' response to the "POODLE" attack
12767 (which does affect Tor). It also contains a few miscellaneous fixes.
12769 o Major security fixes:
12770 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
12771 today support TLS 1.0 or later, so we can safely turn off support
12772 for this old (and insecure) protocol. Fixes bug 13426.
12774 o Major bugfixes (openssl bug workaround):
12775 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
12776 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
12777 13471. This is a workaround for an OpenSSL bug.
12780 - Disable the sandbox name resolver cache when running tor-resolve:
12781 tor-resolve doesn't use the sandbox code, and turning it on was
12782 breaking attempts to do tor-resolve on a non-default server on
12783 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
12785 o Compilation fixes:
12786 - Build and run correctly on systems like OpenBSD-current that have
12787 patched OpenSSL to remove get_cipher_by_char and/or its
12788 implementations. Fixes issue 13325.
12790 o Downgraded warnings:
12791 - Downgrade the severity of the 'unexpected sendme cell from client'
12792 from 'warn' to 'protocol warning'. Closes ticket 8093.
12795 Changes in version 0.2.4.25 - 2014-10-20
12796 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
12797 (even though POODLE does not affect Tor). It also works around a crash
12798 bug caused by some operating systems' response to the "POODLE" attack
12799 (which does affect Tor).
12801 o Major security fixes (also in 0.2.5.9-rc):
12802 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
12803 today support TLS 1.0 or later, so we can safely turn off support
12804 for this old (and insecure) protocol. Fixes bug 13426.
12806 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
12807 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
12808 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
12809 13471. This is a workaround for an OpenSSL bug.
12812 Changes in version 0.2.5.8-rc - 2014-09-22
12813 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
12814 series. It fixes a bug that affects consistency and speed when
12815 connecting to hidden services, and it updates the location of one of
12816 the directory authorities.
12819 - Clients now send the correct address for their chosen rendezvous
12820 point when trying to access a hidden service. They used to send
12821 the wrong address, which would still work some of the time because
12822 they also sent the identity digest of the rendezvous point, and if
12823 the hidden service happened to try connecting to the rendezvous
12824 point from a relay that already had a connection open to it,
12825 the relay would reuse that connection. Now connections to hidden
12826 services should be more robust and faster. Also, this bug meant
12827 that clients were leaking to the hidden service whether they were
12828 on a little-endian (common) or big-endian (rare) system, which for
12829 some users might have reduced their anonymity. Fixes bug 13151;
12830 bugfix on 0.2.1.5-alpha.
12832 o Directory authority changes:
12833 - Change IP address for gabelmoo (v3 directory authority).
12836 Changes in version 0.2.4.24 - 2014-09-22
12837 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
12838 connecting to hidden services, and it updates the location of one of
12839 the directory authorities.
12842 - Clients now send the correct address for their chosen rendezvous
12843 point when trying to access a hidden service. They used to send
12844 the wrong address, which would still work some of the time because
12845 they also sent the identity digest of the rendezvous point, and if
12846 the hidden service happened to try connecting to the rendezvous
12847 point from a relay that already had a connection open to it,
12848 the relay would reuse that connection. Now connections to hidden
12849 services should be more robust and faster. Also, this bug meant
12850 that clients were leaking to the hidden service whether they were
12851 on a little-endian (common) or big-endian (rare) system, which for
12852 some users might have reduced their anonymity. Fixes bug 13151;
12853 bugfix on 0.2.1.5-alpha.
12855 o Directory authority changes:
12856 - Change IP address for gabelmoo (v3 directory authority).
12858 o Minor features (geoip):
12859 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
12863 Changes in version 0.2.5.7-rc - 2014-09-11
12864 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
12865 release series, and some long-standing bugs related to ORPort reachability
12866 testing and failure to send CREATE cells. It is the first release
12867 candidate for the Tor 0.2.5.x series.
12869 o Major bugfixes (client, startup):
12870 - Start making circuits as soon as DisabledNetwork is turned off.
12871 When Tor started with DisabledNetwork set, it would correctly
12872 conclude that it shouldn't build circuits, but it would mistakenly
12873 cache this conclusion, and continue believing it even when
12874 DisableNetwork is set to 0. Fixes the bug introduced by the fix
12875 for bug 11200; bugfix on 0.2.5.4-alpha.
12876 - Resume expanding abbreviations for command-line options. The fix
12877 for bug 4647 accidentally removed our hack from bug 586 that
12878 rewrote HashedControlPassword to __HashedControlSessionPassword
12879 when it appears on the commandline (which allowed the user to set
12880 her own HashedControlPassword in the torrc file while the
12881 controller generates a fresh session password for each run). Fixes
12882 bug 12948; bugfix on 0.2.5.1-alpha.
12883 - Warn about attempts to run hidden services and relays in the same
12884 process: that's probably not a good idea. Closes ticket 12908.
12886 o Major bugfixes (relay):
12887 - Avoid queuing or sending destroy cells for circuit ID zero when we
12888 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
12889 Found and fixed by "cypherpunks".
12890 - Fix ORPort reachability detection on relays running behind a
12891 proxy, by correctly updating the "local" mark on the controlling
12892 channel when changing the address of an or_connection_t after the
12893 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
12895 o Minor features (bridge):
12896 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
12897 cookie file for the ExtORPort g+r by default.
12899 o Minor features (geoip):
12900 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
12903 o Minor bugfixes (logging):
12904 - Reduce the log severity of the "Pluggable transport proxy does not
12905 provide any needed transports and will not be launched." message,
12906 since Tor Browser includes several ClientTransportPlugin lines in
12907 its torrc-defaults file, leading every Tor Browser user who looks
12908 at her logs to see these notices and wonder if they're dangerous.
12909 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
12910 - Downgrade "Unexpected onionskin length after decryption" warning
12911 to a protocol-warn, since there's nothing relay operators can do
12912 about a client that sends them a malformed create cell. Resolves
12913 bug 12996; bugfix on 0.0.6rc1.
12914 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
12915 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
12916 - When logging information about an EXTEND2 or EXTENDED2 cell, log
12917 their names correctly. Fixes part of bug 12700; bugfix
12919 - When logging information about a relay cell whose command we don't
12920 recognize, log its command as an integer. Fixes part of bug 12700;
12921 bugfix on 0.2.1.10-alpha.
12922 - Escape all strings from the directory connection before logging
12923 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
12925 o Minor bugfixes (controller):
12926 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
12927 bug 12864; bugfix on 0.2.5.1-alpha.
12928 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
12929 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
12932 o Minor bugfixes (compilation):
12933 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
12934 bugfix on 0.2.5.5-alpha.
12935 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
12936 0.2.5.1-alpha. Patch from "NewEraCracker".
12937 - In routerlist_assert_ok(), don't take the address of a
12938 routerinfo's cache_info member unless that routerinfo is non-NULL.
12939 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
12940 - Fix a large number of false positive warnings from the clang
12941 analyzer static analysis tool. This should make real warnings
12942 easier for clang analyzer to find. Patch from "teor". Closes
12945 o Distribution (systemd):
12946 - Verify configuration file via ExecStartPre in the systemd unit
12947 file. Patch from intrigeri; resolves ticket 12730.
12948 - Explicitly disable RunAsDaemon in the systemd unit file. Our
12949 current systemd unit uses "Type = simple", so systemd does not
12950 expect tor to fork. If the user has "RunAsDaemon 1" in their
12951 torrc, then things won't work as expected. This is e.g. the case
12952 on Debian (and derivatives), since there we pass "--defaults-torrc
12953 /usr/share/tor/tor-service-defaults-torrc" (that contains
12954 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
12958 - Adjust the URLs in the README to refer to the new locations of
12959 several documents on the website. Fixes bug 12830. Patch from
12961 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
12965 Changes in version 0.2.5.6-alpha - 2014-07-28
12966 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
12967 risk from guard rotation, and fixes a variety of other issues to get
12968 us closer to a release candidate.
12970 o Major features (also in 0.2.4.23):
12971 - Make the number of entry guards configurable via a new
12972 NumEntryGuards consensus parameter, and the number of directory
12973 guards configurable via a new NumDirectoryGuards consensus
12974 parameter. Implements ticket 12688.
12976 o Major bugfixes (also in 0.2.4.23):
12977 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
12978 implementation that caused incorrect results on 32-bit
12979 implementations when certain malformed inputs were used along with
12980 a small class of private ntor keys. This bug does not currently
12981 appear to allow an attacker to learn private keys or impersonate a
12982 Tor server, but it could provide a means to distinguish 32-bit Tor
12983 implementations from 64-bit Tor implementations. Fixes bug 12694;
12984 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
12988 - Perform circuit cleanup operations even when circuit
12989 construction operations are disabled (because the network is
12990 disabled, or because there isn't enough directory information).
12991 Previously, when we were not building predictive circuits, we
12992 were not closing expired circuits either. Fixes bug 8387; bugfix on
12993 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
12994 became more strict about when we have "enough directory information
12995 to build circuits".
12998 - Authorities now assign the Guard flag to the fastest 25% of the
12999 network (it used to be the fastest 50%). Also raise the consensus
13000 weight that guarantees the Guard flag from 250 to 2000. For the
13001 current network, this results in about 1100 guards, down from 2500.
13002 This step paves the way for moving the number of entry guards
13003 down to 1 (proposal 236) while still providing reasonable expected
13004 performance for most users. Implements ticket 12690.
13005 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
13007 - Slightly enhance the diagnostic message for bug 12184.
13009 o Minor bugfixes (also in 0.2.4.23):
13010 - Warn and drop the circuit if we receive an inbound 'relay early'
13011 cell. Those used to be normal to receive on hidden service circuits
13012 due to bug 1038, but the buggy Tor versions are long gone from
13013 the network so we can afford to resume watching for them. Resolves
13014 the rest of bug 1038; bugfix on 0.2.1.19.
13015 - Correct a confusing error message when trying to extend a circuit
13016 via the control protocol but we don't know a descriptor or
13017 microdescriptor for one of the specified relays. Fixes bug 12718;
13018 bugfix on 0.2.3.1-alpha.
13021 - Fix compilation when building with bufferevents enabled. (This
13022 configuration is still not expected to work, however.)
13023 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
13024 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
13026 - Compile correctly with builds and forks of OpenSSL (such as
13027 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
13028 0.2.1.1-alpha. Patch from "dhill".
13031 Changes in version 0.2.4.23 - 2014-07-28
13032 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
13033 guard rotation, and also backports several important fixes from the
13034 Tor 0.2.5 alpha release series.
13037 - Clients now look at the "usecreatefast" consensus parameter to
13038 decide whether to use CREATE_FAST or CREATE cells for the first hop
13039 of their circuit. This approach can improve security on connections
13040 where Tor's circuit handshake is stronger than the available TLS
13041 connection security levels, but the tradeoff is more computational
13042 load on guard relays. Implements proposal 221. Resolves ticket 9386.
13043 - Make the number of entry guards configurable via a new
13044 NumEntryGuards consensus parameter, and the number of directory
13045 guards configurable via a new NumDirectoryGuards consensus
13046 parameter. Implements ticket 12688.
13049 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
13050 implementation that caused incorrect results on 32-bit
13051 implementations when certain malformed inputs were used along with
13052 a small class of private ntor keys. This bug does not currently
13053 appear to allow an attacker to learn private keys or impersonate a
13054 Tor server, but it could provide a means to distinguish 32-bit Tor
13055 implementations from 64-bit Tor implementations. Fixes bug 12694;
13056 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
13060 - Warn and drop the circuit if we receive an inbound 'relay early'
13061 cell. Those used to be normal to receive on hidden service circuits
13062 due to bug 1038, but the buggy Tor versions are long gone from
13063 the network so we can afford to resume watching for them. Resolves
13064 the rest of bug 1038; bugfix on 0.2.1.19.
13065 - Correct a confusing error message when trying to extend a circuit
13066 via the control protocol but we don't know a descriptor or
13067 microdescriptor for one of the specified relays. Fixes bug 12718;
13068 bugfix on 0.2.3.1-alpha.
13069 - Avoid an illegal read from stack when initializing the TLS
13070 module using a version of OpenSSL without all of the ciphers
13071 used by the v2 link handshake. Fixes bug 12227; bugfix on
13072 0.2.4.8-alpha. Found by "starlight".
13075 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
13079 Changes in version 0.2.5.5-alpha - 2014-06-18
13080 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
13081 0.2.5.x release series, including a couple of DoS issues, some
13082 performance regressions, a large number of bugs affecting the Linux
13083 seccomp2 sandbox code, and various other bugfixes. It also adds
13084 diagnostic bugfixes for a few tricky issues that we're trying to
13087 o Major features (security, traffic analysis resistance):
13088 - Several major improvements to the algorithm used to decide when to
13089 close TLS connections. Previous versions of Tor closed connections
13090 at a fixed interval after the last time a non-padding cell was
13091 sent over the connection, regardless of the target of the
13092 connection. Now, we randomize the intervals by adding up to 50% of
13093 their base value, we measure the length of time since connection
13094 last had at least one circuit, and we allow connections to known
13095 ORs to remain open a little longer (15 minutes instead of 3
13096 minutes minimum). These changes should improve Tor's resistance
13097 against some kinds of traffic analysis, and lower some overhead
13098 from needlessly closed connections. Fixes ticket 6799.
13099 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
13101 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
13102 - Fix a memory leak that could occur if a microdescriptor parse
13103 fails during the tokenizing step. This bug could enable a memory
13104 exhaustion attack by directory servers. Fixes bug 11649; bugfix
13107 o Major bugfixes (security, directory authorities):
13108 - Directory authorities now include a digest of each relay's
13109 identity key as a part of its microdescriptor.
13111 This is a workaround for bug 11743 (reported by "cypherpunks"),
13112 where Tor clients do not support receiving multiple
13113 microdescriptors with the same SHA256 digest in the same
13114 consensus. When clients receive a consensus like this, they only
13115 use one of the relays. Without this fix, a hostile relay could
13116 selectively disable some client use of target relays by
13117 constructing a router descriptor with a different identity and the
13118 same microdescriptor parameters and getting the authorities to
13119 list it in a microdescriptor consensus. This fix prevents an
13120 attacker from causing a microdescriptor collision, because the
13121 router's identity is not forgeable.
13123 o Major bugfixes (relay):
13124 - Use a direct dirport connection when uploading non-anonymous
13125 descriptors to the directory authorities. Previously, relays would
13126 incorrectly use tunnel connections under a fairly wide variety of
13127 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
13128 - When a circuit accidentally has the same circuit ID for its
13129 forward and reverse direction, correctly detect the direction of
13130 cells using that circuit. Previously, this bug made roughly one
13131 circuit in a million non-functional. Fixes bug 12195; this is a
13132 bugfix on every version of Tor.
13134 o Major bugfixes (client, pluggable transports):
13135 - When managing pluggable transports, use OS notification facilities
13136 to learn if they have crashed, and don't attempt to kill any
13137 process that has already exited. Fixes bug 8746; bugfix
13140 o Minor features (diagnostic):
13141 - When logging a warning because of bug 7164, additionally check the
13142 hash table for consistency (as proposed on ticket 11737). This may
13143 help diagnose bug 7164.
13144 - When we log a heartbeat, log how many one-hop circuits we have
13145 that are at least 30 minutes old, and log status information about
13146 a few of them. This is an attempt to track down bug 8387.
13147 - When encountering an unexpected CR while writing text to a file on
13148 Windows, log the name of the file. Should help diagnosing
13150 - Give more specific warnings when a client notices that an onion
13151 handshake has failed. Fixes ticket 9635.
13152 - Add significant new logging code to attempt to diagnose bug 12184,
13153 where relays seem to run out of available circuit IDs.
13154 - Improve the diagnostic log message for bug 8387 even further to
13155 try to improve our odds of figuring out why one-hop directory
13156 circuits sometimes do not get closed.
13158 o Minor features (security, memory management):
13159 - Memory allocation tricks (mempools and buffer freelists) are now
13160 disabled by default. You can turn them back on with
13161 --enable-mempools and --enable-buf-freelists respectively. We're
13162 disabling these features because malloc performance is good enough
13163 on most platforms, and a similar feature in OpenSSL exacerbated
13164 exploitation of the Heartbleed attack. Resolves ticket 11476.
13166 o Minor features (security):
13167 - Apply the secure SipHash-2-4 function to the hash table mapping
13168 circuit IDs and channels to circuits. We missed this one when we
13169 were converting all the other hash functions to use SipHash back
13170 in 0.2.5.3-alpha. Resolves ticket 11750.
13172 o Minor features (build):
13173 - The configure script has a --disable-seccomp option to turn off
13174 support for libseccomp on systems that have it, in case it (or
13175 Tor's use of it) is broken. Resolves ticket 11628.
13177 o Minor features (other):
13178 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
13181 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
13182 - When running a hidden service, do not allow TunneledDirConns 0;
13183 this will keep the hidden service from running, and also
13184 make it publish its descriptors directly over HTTP. Fixes bug 10849;
13185 bugfix on 0.2.1.1-alpha.
13187 o Minor bugfixes (performance):
13188 - Avoid a bug where every successful connection made us recompute
13189 the flag telling us whether we have sufficient information to
13190 build circuits. Previously, we would forget our cached value
13191 whenever we successfully opened a channel (or marked a router as
13192 running or not running for any other reason), regardless of
13193 whether we had previously believed the router to be running. This
13194 forced us to run an expensive update operation far too often.
13195 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
13196 - Avoid using tor_memeq() for checking relay cell integrity. This
13197 removes a possible performance bottleneck. Fixes part of bug
13198 12169; bugfix on 0.2.1.31.
13200 o Minor bugfixes (compilation):
13201 - Fix compilation of test_status.c when building with MVSC. Bugfix
13202 on 0.2.5.4-alpha. Patch from Gisle Vanem.
13203 - Resolve GCC complaints on OpenBSD about discarding constness in
13204 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
13205 on 0.1.1.23. Patch from Dana Koch.
13206 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
13207 treatment of long and time_t as comparable types. Fixes part of
13208 bug 11633. Patch from Dana Koch.
13209 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
13210 11623; bugfix on 0.2.5.3-alpha.
13211 - When deciding whether to build the 64-bit curve25519
13212 implementation, detect platforms where we can compile 128-bit
13213 arithmetic but cannot link it. Fixes bug 11729; bugfix on
13214 0.2.4.8-alpha. Patch from "conradev".
13215 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
13216 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
13217 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
13220 o Minor bugfixes (Directory server):
13221 - When sending a compressed set of descriptors or microdescriptors,
13222 make sure to finalize the zlib stream. Previously, we would write
13223 all the compressed data, but if the last descriptor we wanted to
13224 send was missing or too old, we would not mark the stream as
13225 finished. This caused problems for decompression tools. Fixes bug
13226 11648; bugfix on 0.1.1.23.
13228 o Minor bugfixes (Linux seccomp sandbox):
13229 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
13230 11622; bugfix on 0.2.5.1-alpha.
13231 - Avoid crashing when re-opening listener ports with the seccomp
13232 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
13233 - Avoid crashing with the seccomp sandbox enabled along with
13234 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
13235 - When we receive a SIGHUP with the sandbox enabled, correctly
13236 support rotating our log files. Fixes bug 12032; bugfix
13238 - Avoid crash when running with sandboxing enabled and
13239 DirReqStatistics not disabled. Fixes bug 12035; bugfix
13241 - Fix a "BUG" warning when trying to write bridge-stats files with
13242 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
13244 - Prevent the sandbox from crashing on startup when run with the
13245 --enable-expensive-hardening configuration option. Fixes bug
13246 11477; bugfix on 0.2.5.4-alpha.
13247 - When running with DirPortFrontPage and sandboxing both enabled,
13248 reload the DirPortFrontPage correctly when restarting. Fixes bug
13249 12028; bugfix on 0.2.5.1-alpha.
13250 - Don't try to enable the sandbox when using the Tor binary to check
13251 its configuration, hash a passphrase, or so on. Doing so was
13252 crashing on startup for some users. Fixes bug 11609; bugfix
13254 - Avoid warnings when running with sandboxing and node statistics
13255 enabled at the same time. Fixes part of 12064; bugfix on
13256 0.2.5.1-alpha. Patch from Michael Wolf.
13257 - Avoid warnings when running with sandboxing enabled at the same
13258 time as cookie authentication, hidden services, or directory
13259 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
13260 - Do not allow options that require calls to exec to be enabled
13261 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
13262 bug 12043; bugfix on 0.2.5.1-alpha.
13263 - Handle failures in getpwnam()/getpwuid() when running with the
13264 User option set and the Linux syscall sandbox enabled. Fixes bug
13265 11946; bugfix on 0.2.5.1-alpha.
13266 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
13267 to avoid calling getaddrinfo() after installing the sandbox
13268 filters. Previously, it preloaded a cache with the IPv4 address
13269 for our hostname, and nothing else. Now, it loads the cache with
13270 every address that it used to initialize the Tor process. Fixes
13271 bug 11970; bugfix on 0.2.5.1-alpha.
13273 o Minor bugfixes (pluggable transports):
13274 - Enable the ExtORPortCookieAuthFile option, to allow changing the
13275 default location of the authentication token for the extended OR
13276 Port as used by sever-side pluggable transports. We had
13277 implemented this option before, but the code to make it settable
13278 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
13279 - Avoid another 60-second delay when starting Tor in a pluggable-
13280 transport-using configuration when we already have cached
13281 descriptors for our bridges. Fixes bug 11965; bugfix
13284 o Minor bugfixes (client):
13285 - Avoid "Tried to open a socket with DisableNetwork set" warnings
13286 when starting a client with bridges configured and DisableNetwork
13287 set. (Tor launcher starts Tor with DisableNetwork set the first
13288 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
13290 o Minor bugfixes (testing):
13291 - The Python parts of the test scripts now work on Python 3 as well
13292 as Python 2, so systems where '/usr/bin/python' is Python 3 will
13293 no longer have the tests break. Fixes bug 11608; bugfix
13295 - When looking for versions of python that we could run the tests
13296 with, check for "python2.7" and "python3.3"; previously we were
13297 only looking for "python", "python2", and "python3". Patch from
13298 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
13299 - Fix all valgrind warnings produced by the unit tests. There were
13300 over a thousand memory leak warnings previously, mostly produced
13301 by forgetting to free things in the unit test code. Fixes bug
13302 11618, bugfixes on many versions of Tor.
13304 o Minor bugfixes (tor-fw-helper):
13305 - Give a correct log message when tor-fw-helper fails to launch.
13306 (Previously, we would say something like "tor-fw-helper sent us a
13307 string we could not parse".) Fixes bug 9781; bugfix
13310 o Minor bugfixes (relay, threading):
13311 - Check return code on spawn_func() in cpuworker code, so that we
13312 don't think we've spawned a nonworking cpuworker and write junk to
13313 it forever. Fix related to bug 4345; bugfix on all released Tor
13314 versions. Found by "skruffy".
13315 - Use a pthread_attr to make sure that spawn_func() cannot return an
13316 error while at the same time launching a thread. Fix related to
13317 bug 4345; bugfix on all released Tor versions. Reported
13320 o Minor bugfixes (relay, oom prevention):
13321 - Correctly detect the total available system memory. We tried to do
13322 this in 0.2.5.4-alpha, but the code was set up to always return an
13323 error value, even on success. Fixes bug 11805; bugfix
13326 o Minor bugfixes (relay, other):
13327 - We now drop CREATE cells for already-existent circuit IDs and for
13328 zero-valued circuit IDs, regardless of other factors that might
13329 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
13331 - Avoid an illegal read from stack when initializing the TLS module
13332 using a version of OpenSSL without all of the ciphers used by the
13333 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
13335 - When rejecting DATA cells for stream_id zero, still count them
13336 against the circuit's deliver window so that we don't fail to send
13337 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
13339 o Minor bugfixes (logging):
13340 - Fix a misformatted log message about delayed directory fetches.
13341 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
13342 - Squelch a spurious LD_BUG message "No origin circuit for
13343 successful SOCKS stream" in certain hidden service failure cases;
13347 - Include a tor.service file in contrib/dist for use with systemd.
13348 Some distributions will be able to use this file unmodified;
13349 others will need to tweak it, or write their own. Patch from Jamie
13350 Nguyen; resolves ticket 8368.
13353 - Clean up several option names in the manpage to match their real
13354 names, add the missing documentation for a couple of testing and
13355 directory authority options, remove the documentation for a
13356 V2-directory fetching option that no longer exists. Resolves
13358 - Correct the documentation so that it lists the correct directory
13359 for the stats files. (They are in a subdirectory called "stats",
13361 - In the manpage, move more authority-only options into the
13362 directory authority section so that operators of regular directory
13363 caches don't get confused.
13366 - The contrib directory has been sorted and tidied. Before, it was
13367 an unsorted dumping ground for useful and not-so-useful things.
13368 Now, it is divided based on functionality, and the items which
13369 seemed to be nonfunctional or useless have been removed. Resolves
13370 ticket 8966; based on patches from "rl1987".
13373 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
13374 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
13375 - The TunnelDirConns and PreferTunnelledDirConns options no longer
13376 exist; tunneled directory connections have been available since
13377 0.1.2.5-alpha, and turning them off is not a good idea. This is a
13378 brute-force fix for 10849, where "TunnelDirConns 0" would break
13382 Changes in version 0.2.4.22 - 2014-05-16
13383 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
13384 alpha release series. These include blocking all authority signing
13385 keys that may have been affected by the OpenSSL "heartbleed" bug,
13386 choosing a far more secure set of TLS ciphersuites by default, closing
13387 a couple of memory leaks that could be used to run a target relay out
13388 of RAM, and several others.
13390 o Major features (security, backport from 0.2.5.4-alpha):
13391 - Block authority signing keys that were used on authorities
13392 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
13393 don't have any evidence that these keys _were_ compromised; we're
13394 doing this to be prudent.) Resolves ticket 11464.
13396 o Major bugfixes (security, OOM):
13397 - Fix a memory leak that could occur if a microdescriptor parse
13398 fails during the tokenizing step. This bug could enable a memory
13399 exhaustion attack by directory servers. Fixes bug 11649; bugfix
13402 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
13403 - The relay ciphersuite list is now generated automatically based on
13404 uniform criteria, and includes all OpenSSL ciphersuites with
13405 acceptable strength and forward secrecy. Previously, we had left
13406 some perfectly fine ciphersuites unsupported due to omission or
13407 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
13408 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
13409 - Relays now trust themselves to have a better view than clients of
13410 which TLS ciphersuites are better than others. (Thanks to bug
13411 11513, the relay list is now well-considered, whereas the client
13412 list has been chosen mainly for anti-fingerprinting purposes.)
13413 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
13414 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
13415 AES128. Resolves ticket 11528.
13416 - Clients now try to advertise the same list of ciphersuites as
13417 Firefox 28. This change enables selection of (fast) GCM
13418 ciphersuites, disables some strange old ciphers, and stops
13419 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
13420 Resolves ticket 11438.
13422 o Minor bugfixes (configuration, security):
13423 - When running a hidden service, do not allow TunneledDirConns 0:
13424 trying to set that option together with a hidden service would
13425 otherwise prevent the hidden service from running, and also make
13426 it publish its descriptors directly over HTTP. Fixes bug 10849;
13427 bugfix on 0.2.1.1-alpha.
13429 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
13430 - Avoid sending a garbage value to the controller when a circuit is
13431 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
13433 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
13434 - Stop leaking memory when we successfully resolve a PTR record.
13435 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
13437 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
13438 - Avoid 60-second delays in the bootstrapping process when Tor is
13439 launching for a second time while using bridges. Fixes bug 9229;
13440 bugfix on 0.2.0.3-alpha.
13442 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
13443 - Give the correct URL in the warning message when trying to run a
13444 relay on an ancient version of Windows. Fixes bug 9393.
13446 o Minor bugfixes (compilation):
13447 - Fix a compilation error when compiling with --disable-curve25519.
13448 Fixes bug 9700; bugfix on 0.2.4.17-rc.
13451 - Downgrade the warning severity for the the "md was still
13452 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
13453 for trying to diagnose this bug, and the current warning in
13454 earlier versions of tor achieves nothing useful. Addresses warning
13457 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
13458 - When we run out of usable circuit IDs on a channel, log only one
13459 warning for the whole channel, and describe how many circuits
13460 there were on the channel. Fixes part of ticket 11553.
13462 o Minor features (security, backport from 0.2.5.4-alpha):
13463 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
13464 leave the default at 8GBytes), to better support Raspberry Pi
13465 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
13467 o Documentation (backport from 0.2.5.4-alpha):
13468 - Correctly document that we search for a system torrc file before
13469 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
13473 Changes in version 0.2.5.4-alpha - 2014-04-25
13474 Tor 0.2.5.4-alpha includes several security and performance
13475 improvements for clients and relays, including blacklisting authority
13476 signing keys that were used while susceptible to the OpenSSL
13477 "heartbleed" bug, fixing two expensive functions on busy relays,
13478 improved TLS ciphersuite preference lists, support for run-time
13479 hardening on compilers that support AddressSanitizer, and more work on
13480 the Linux sandbox code.
13482 There are also several usability fixes for clients (especially clients
13483 that use bridges), two new TransPort protocols supported (one on
13484 OpenBSD, one on FreeBSD), and various other bugfixes.
13486 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
13487 have accumulated many known flaws; everyone should upgrade.
13489 o Major features (security):
13490 - If you don't specify MaxMemInQueues yourself, Tor now tries to
13491 pick a good value based on your total system memory. Previously,
13492 the default was always 8 GB. You can still override the default by
13493 setting MaxMemInQueues yourself. Resolves ticket 11396.
13494 - Block authority signing keys that were used on authorities
13495 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
13496 don't have any evidence that these keys _were_ compromised; we're
13497 doing this to be prudent.) Resolves ticket 11464.
13499 o Major features (relay performance):
13500 - Speed up server-side lookups of rendezvous and introduction point
13501 circuits by using hashtables instead of linear searches. These
13502 functions previously accounted between 3 and 7% of CPU usage on
13503 some busy relays. Resolves ticket 9841.
13504 - Avoid wasting CPU when extending a circuit over a channel that is
13505 nearly out of circuit IDs. Previously, we would do a linear scan
13506 over possible circuit IDs before finding one or deciding that we
13507 had exhausted our possibilities. Now, we try at most 64 random
13508 circuit IDs before deciding that we probably won't succeed. Fixes
13509 a possible root cause of ticket 11553.
13511 o Major features (seccomp2 sandbox, Linux only):
13512 - The seccomp2 sandbox can now run a test network for multiple hours
13513 without crashing. The sandbox is still experimental, and more bugs
13514 will probably turn up. To try it, enable "Sandbox 1" on a Linux
13515 host. Resolves ticket 11351.
13516 - Strengthen sandbox code: the sandbox can now test the arguments
13517 for rename(), and blocks _sysctl() entirely. Resolves another part
13519 - When the sandbox blocks a system call, it now tries to log a stack
13520 trace before exiting. Resolves ticket 11465.
13522 o Major bugfixes (TLS cipher selection):
13523 - The relay ciphersuite list is now generated automatically based on
13524 uniform criteria, and includes all OpenSSL ciphersuites with
13525 acceptable strength and forward secrecy. Previously, we had left
13526 some perfectly fine ciphersuites unsupported due to omission or
13527 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
13528 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
13529 - Relays now trust themselves to have a better view than clients of
13530 which TLS ciphersuites are better than others. (Thanks to bug
13531 11513, the relay list is now well-considered, whereas the client
13532 list has been chosen mainly for anti-fingerprinting purposes.)
13533 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
13534 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
13535 AES128. Resolves ticket 11528.
13536 - Clients now try to advertise the same list of ciphersuites as
13537 Firefox 28. This change enables selection of (fast) GCM
13538 ciphersuites, disables some strange old ciphers, and stops
13539 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
13540 Resolves ticket 11438.
13542 o Major bugfixes (bridge client):
13543 - Avoid 60-second delays in the bootstrapping process when Tor is
13544 launching for a second time while using bridges. Fixes bug 9229;
13545 bugfix on 0.2.0.3-alpha.
13547 o Minor features (transparent proxy, *BSD):
13548 - Support FreeBSD's ipfw firewall interface for TransPort ports on
13549 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
13550 10267; patch from "yurivict".
13551 - Support OpenBSD's divert-to rules with the pf firewall for
13552 transparent proxy ports. To enable it, set "TransProxyType
13553 pf-divert". This allows Tor to run a TransPort transparent proxy
13554 port on OpenBSD 4.4 or later without root privileges. See the
13555 pf.conf(5) manual page for information on configuring pf to use
13556 divert-to rules. Closes ticket 10896; patch from Dana Koch.
13558 o Minor features (security):
13559 - New --enable-expensive-hardening option to enable security
13560 hardening options that consume nontrivial amounts of CPU and
13561 memory. Right now, this includes AddressSanitizer and UbSan, which
13562 are supported in newer versions of GCC and Clang. Closes ticket
13565 o Minor features (log verbosity):
13566 - Demote the message that we give when a flushing connection times
13567 out for too long from NOTICE to INFO. It was usually meaningless.
13568 Resolves ticket 5286.
13569 - Don't log so many notice-level bootstrapping messages at startup
13570 about downloading descriptors. Previously, we'd log a notice
13571 whenever we learned about more routers. Now, we only log a notice
13572 at every 5% of progress. Fixes bug 9963.
13573 - Warn less verbosely when receiving a malformed
13574 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
13575 - When we run out of usable circuit IDs on a channel, log only one
13576 warning for the whole channel, and describe how many circuits
13577 there were on the channel. Fixes part of ticket 11553.
13579 o Minor features (relay):
13580 - If a circuit timed out for at least 3 minutes, check if we have a
13581 new external IP address, and publish a new descriptor with the new
13582 IP address if it changed. Resolves ticket 2454.
13584 o Minor features (controller):
13585 - Make the entire exit policy available from the control port via
13586 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
13588 - Because of the fix for ticket 11396, the real limit for memory
13589 usage may no longer match the configured MaxMemInQueues value. The
13590 real limit is now exposed via GETINFO limits/max-mem-in-queues.
13592 o Minor features (bridge client):
13593 - Report a more useful failure message when we can't connect to a
13594 bridge because we don't have the right pluggable transport
13595 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
13597 o Minor features (diagnostic):
13598 - Add more log messages to diagnose bug 7164, which causes
13599 intermittent "microdesc_free() called but md was still referenced"
13600 warnings. We now include more information, to figure out why we
13601 might be cleaning a microdescriptor for being too old if it's
13602 still referenced by a live node_t object.
13604 o Minor bugfixes (client, DNSPort):
13605 - When using DNSPort, try to respond to AAAA requests with AAAA
13606 answers. Previously, we hadn't looked at the request type when
13607 deciding which answer type to prefer. Fixes bug 10468; bugfix on
13609 - When receiving a DNS query for an unsupported record type, reply
13610 with no answer rather than with a NOTIMPL error. This behavior
13611 isn't correct either, but it will break fewer client programs, we
13612 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
13615 o Minor bugfixes (exit relay):
13616 - Stop leaking memory when we successfully resolve a PTR record.
13617 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
13619 o Minor bugfixes (bridge client):
13620 - Stop accepting bridge lines containing hostnames. Doing so would
13621 cause clients to perform DNS requests on the hostnames, which was
13622 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
13623 - Avoid a 60-second delay in the bootstrapping process when a Tor
13624 client with pluggable transports re-reads its configuration at
13625 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
13627 o Minor bugfixes (client, logging during bootstrap):
13628 - Warn only once if we start logging in an unsafe way. Previously,
13629 we complain as many times as we had problems. Fixes bug 9870;
13630 bugfix on 0.2.5.1-alpha.
13631 - Only report the first fatal bootstrap error on a given OR
13632 connection. This stops us from telling the controller bogus error
13633 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
13634 - Be more helpful when trying to run sandboxed on Linux without
13635 libseccomp. Instead of saying "Sandbox is not implemented on this
13636 platform", we now explain that we need to be built with
13637 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
13638 - Avoid generating spurious warnings when starting with
13639 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
13642 o Minor bugfixes (closing OR connections):
13643 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
13644 check if it's an or_connection_t and correctly call
13645 connection_or_close_for_error() rather than
13646 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
13648 - When closing all connections on setting DisableNetwork to 1, use
13649 connection_or_close_normally() rather than closing OR connections
13650 out from under the channel layer. Fixes bug 11306; bugfix on
13653 o Minor bugfixes (controller):
13654 - Avoid sending a garbage value to the controller when a circuit is
13655 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
13657 o Minor bugfixes (tor-fw-helper):
13658 - Allow tor-fw-helper to build again by adding src/ext to its
13659 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
13661 o Minor bugfixes (bridges):
13662 - Avoid potential crashes or bad behavior when launching a
13663 server-side managed proxy with ORPort or ExtORPort temporarily
13664 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
13666 o Minor bugfixes (platform-specific):
13667 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
13668 bug 11426; bugfix on 0.2.5.3-alpha.
13669 - When dumping a malformed directory object to disk, save it in
13670 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
13672 - Don't report failures from make_socket_reuseable() on incoming
13673 sockets on OSX: this can happen when incoming connections close
13674 early. Fixes bug 10081.
13676 o Minor bugfixes (trivial memory leaks):
13677 - Fix a small memory leak when signing a directory object. Fixes bug
13678 11275; bugfix on 0.2.4.13-alpha.
13679 - Free placeholder entries in our circuit table at exit; fixes a
13680 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
13681 - Don't re-initialize a second set of OpenSSL mutexes when starting
13682 up. Previously, we'd make one set of mutexes, and then immediately
13683 replace them with another. Fixes bug 11726; bugfix on
13685 - Resolve some memory leaks found by coverity in the unit tests, on
13686 exit in tor-gencert, and on a failure to compute digests for our
13687 own keys when generating a v3 networkstatus vote. These leaks
13688 should never have affected anyone in practice.
13690 o Minor bugfixes (hidden service):
13691 - Only retry attempts to connect to a chosen rendezvous point 8
13692 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
13694 o Minor bugfixes (misc code correctness):
13695 - Fix various instances of undefined behavior in channeltls.c,
13696 tor_memmem(), and eventdns.c that would cause us to construct
13697 pointers to memory outside an allocated object. (These invalid
13698 pointers were not accessed, but C does not even allow them to
13699 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
13700 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
13701 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
13702 fix some miscellaneous errors in our tests and codebase. Fixes bug
13703 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
13704 - Always check return values for unlink, munmap, UnmapViewOfFile;
13705 check strftime return values more often. In some cases all we can
13706 do is report a warning, but this may help prevent deeper bugs from
13707 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
13709 - Fix numerous warnings from the clang "scan-build" static analyzer.
13710 Some of these are programming style issues; some of them are false
13711 positives that indicated awkward code; some are undefined behavior
13712 cases related to constructing (but not using) invalid pointers;
13713 some are assumptions about API behavior; some are (harmlessly)
13714 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
13715 correct; and one or two are genuine bugs that weren't reachable
13716 from the rest of the program. Fixes bug 8793; bugfixes on many,
13720 - Build the torify.1 manpage again. Previously, we were only trying
13721 to build it when also building tor-fw-helper. That's why we didn't
13722 notice that we'd broken the ability to build it. Fixes bug 11321;
13723 bugfix on 0.2.5.1-alpha.
13724 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
13725 11061; bugfix on 0.2.4.7-alpha.
13726 - Correctly document that we search for a system torrc file before
13727 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
13729 - Resolve warnings from Doxygen.
13731 o Code simplifications and refactoring:
13732 - Remove is_internal_IP() function. Resolves ticket 4645.
13733 - Remove unused function circuit_dump_by_chan from circuitlist.c.
13734 Closes issue 9107; patch from "marek".
13735 - Change our use of the ENUM_BF macro to avoid declarations that
13738 o Deprecated versions:
13739 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
13740 attention for some while. Directory authorities no longer accept
13741 descriptors from relays running any version of Tor prior to Tor
13742 0.2.3.16-alpha. Resolves ticket 11149.
13745 - New macros in test.h to simplify writing mock-functions for unit
13746 tests. Part of ticket 11507. Patch from Dana Koch.
13747 - Complete tests for the status.c module. Resolves ticket 11507.
13748 Patch from Dana Koch.
13751 - Remove all code for the long unused v1 directory protocol.
13752 Resolves ticket 11070.
13755 Changes in version 0.2.5.3-alpha - 2014-03-22
13756 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
13757 two new anti-DoS features for Tor relays, resolves a bug that kept
13758 SOCKS5 support for IPv6 from working, fixes several annoying usability
13759 issues for bridge users, and removes more old code for unused
13762 The Tor 0.2.5.x release series is now in patch-freeze: no feature
13763 patches not already written will be considered for inclusion in 0.2.5.x.
13765 o Major features (relay security, DoS-resistance):
13766 - When deciding whether we have run out of memory and we need to
13767 close circuits, also consider memory allocated in buffers for
13768 streams attached to each circuit.
13770 This change, which extends an anti-DoS feature introduced in
13771 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
13772 better resist more memory-based DoS attacks than before. Since the
13773 MaxMemInCellQueues option now applies to all queues, it is renamed
13774 to MaxMemInQueues. This feature fixes bug 10169.
13775 - Avoid hash-flooding denial-of-service attacks by using the secure
13776 SipHash-2-4 hash function for our hashtables. Without this
13777 feature, an attacker could degrade performance of a targeted
13778 client or server by flooding their data structures with a large
13779 number of entries to be stored at the same hash table position,
13780 thereby slowing down the Tor instance. With this feature, hash
13781 table positions are derived from a randomized cryptographic key,
13782 and an attacker cannot predict which entries will collide. Closes
13784 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
13785 the default at 8GBytes), to better support Raspberry Pi users. Fixes
13786 bug 9686; bugfix on 0.2.4.14-alpha.
13788 o Minor features (bridges, pluggable transports):
13789 - Bridges now write the SHA1 digest of their identity key
13790 fingerprint (that is, a hash of a hash of their public key) to
13791 notice-level logs, and to a new hashed-fingerprint file. This
13792 information will help bridge operators look up their bridge in
13793 Globe and similar tools. Resolves ticket 10884.
13794 - Improve the message that Tor displays when running as a bridge
13795 using pluggable transports without an Extended ORPort listener.
13796 Also, log the message in the log file too. Resolves ticket 11043.
13798 o Minor features (other):
13799 - Add a new option, PredictedPortsRelevanceTime, to control how long
13800 after having received a request to connect to a given port Tor
13801 will try to keep circuits ready in anticipation of future requests
13802 for that port. Patch from "unixninja92"; implements ticket 9176.
13803 - Generate a warning if any ports are listed in the SocksPolicy,
13804 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
13805 AuthDirBadExit options. (These options only support address
13806 ranges.) Fixes part of ticket 11108.
13807 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
13810 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
13811 - Build without warnings under clang 3.4. (We have some macros that
13812 define static functions only some of which will get used later in
13813 the module. Starting with clang 3.4, these give a warning unless the
13814 unused attribute is set on them.) Resolves ticket 10904.
13815 - Fix build warnings about missing "a2x" comment when building the
13816 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
13817 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
13819 o Minor bugfixes (client):
13820 - Improve the log message when we can't connect to a hidden service
13821 because all of the hidden service directory nodes hosting its
13822 descriptor are excluded. Improves on our fix for bug 10722, which
13823 was a bugfix on 0.2.0.10-alpha.
13824 - Raise a control port warning when we fail to connect to all of
13825 our bridges. Previously, we didn't inform the controller, and
13826 the bootstrap process would stall. Fixes bug 11069; bugfix on
13828 - Exit immediately when a process-owning controller exits.
13829 Previously, tor relays would wait for a little while after their
13830 controller exited, as if they had gotten an INT signal -- but this
13831 was problematic, since there was no feedback for the user. To do a
13832 clean shutdown, controllers should send an INT signal and give Tor
13833 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
13834 - Stop attempting to connect to bridges before our pluggable
13835 transports are configured (harmless but resulted in some erroneous
13836 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
13837 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
13838 generating incorrect SOCKS5 responses, and confusing client
13839 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
13841 o Minor bugfixes (relays and bridges):
13842 - Avoid crashing on a malformed resolv.conf file when running a
13843 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
13844 - Non-exit relays no longer launch mock DNS requests to check for
13845 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
13846 non-exit relays stopped servicing DNS requests. Fixes bug 965;
13847 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
13848 - Bridges now report complete directory request statistics. Related
13849 to bug 5824; bugfix on 0.2.2.1-alpha.
13850 - Bridges now never collect statistics that were designed for
13851 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
13852 - Stop giving annoying warning messages when we decide not to launch
13853 a pluggable transport proxy that we don't need (because there are
13854 no bridges configured to use it). Resolves ticket 5018; bugfix
13856 - Give the correct URL in the warning message when trying to run a
13857 relay on an ancient version of Windows. Fixes bug 9393.
13859 o Minor bugfixes (backtrace support):
13860 - Support automatic backtraces on more platforms by using the
13861 "-fasynchronous-unwind-tables" compiler option. This option is
13862 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
13863 is on by default and table generation is not. This doesn't yet
13864 add Windows support; only Linux, OSX, and some BSDs are affected.
13865 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
13866 - Avoid strange behavior if two threads hit failed assertions at the
13867 same time and both try to log backtraces at once. (Previously, if
13868 this had happened, both threads would have stored their intermediate
13869 results in the same buffer, and generated junk outputs.) Reported by
13870 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
13871 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
13872 0.2.5.2-alpha; patch from Nick Hopper.
13874 o Minor bugfixes (unit tests):
13875 - Fix a small bug in the unit tests that might have made the tests
13876 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
13877 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
13880 - Remove all remaining code related to version-0 hidden service
13881 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
13882 the rest of bug 10841.
13885 - Document in the manpage that "KBytes" may also be written as
13886 "kilobytes" or "KB", that "Kbits" may also be written as
13887 "kilobits", and so forth. Closes ticket 9222.
13888 - Document that the ClientOnly config option overrides ORPort.
13889 Our old explanation made ClientOnly sound as though it did
13890 nothing at all. Resolves bug 9059.
13891 - Explain that SocksPolicy, DirPolicy, and similar options don't
13892 take port arguments. Fixes the other part of ticket 11108.
13893 - Fix a comment about the rend_server_descriptor_t.protocols field
13894 to more accurately describe its range. Also, make that field
13895 unsigned, to more accurately reflect its usage. Fixes bug 9099;
13896 bugfix on 0.2.1.5-alpha.
13897 - Fix the manpage's description of HiddenServiceAuthorizeClient:
13898 the maximum client name length is 16, not 19. Fixes bug 11118;
13899 bugfix on 0.2.1.6-alpha.
13901 o Code simplifications and refactoring:
13902 - Get rid of router->address, since in all cases it was just the
13903 string representation of router->addr. Resolves ticket 5528.
13905 o Test infrastructure:
13906 - Update to the latest version of tinytest.
13907 - Improve the tinytest implementation of string operation tests so
13908 that comparisons with NULL strings no longer crash the tests; they
13909 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
13912 Changes in version 0.2.4.21 - 2014-02-28
13913 Tor 0.2.4.21 further improves security against potential adversaries who
13914 find breaking 1024-bit crypto doable, and backports several stability
13915 and robustness patches from the 0.2.5 branch.
13917 o Major features (client security):
13918 - When we choose a path for a 3-hop circuit, make sure it contains
13919 at least one relay that supports the NTor circuit extension
13920 handshake. Otherwise, there is a chance that we're building
13921 a circuit that's worth attacking by an adversary who finds
13922 breaking 1024-bit crypto doable, and that chance changes the game
13923 theory. Implements ticket 9777.
13926 - Do not treat streams that fail with reason
13927 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
13928 since it could also indicate an ENETUNREACH connection error. Fixes
13929 part of bug 10777; bugfix on 0.2.4.8-alpha.
13931 o Code simplification and refactoring:
13932 - Remove data structures which were introduced to implement the
13933 CellStatistics option: they are now redundant with the new timestamp
13934 field in the regular packed_cell_t data structure, which we did
13935 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
13938 - Always clear OpenSSL bignums before freeing them -- even bignums
13939 that don't contain secrets. Resolves ticket 10793. Patch by
13941 - Build without warnings under clang 3.4. (We have some macros that
13942 define static functions only some of which will get used later in
13943 the module. Starting with clang 3.4, these give a warning unless the
13944 unused attribute is set on them.) Resolves ticket 10904.
13945 - Update geoip and geoip6 files to the February 7 2014 Maxmind
13946 GeoLite2 Country database.
13949 - Set the listen() backlog limit to the largest actually supported
13950 on the system, not to the value in a header file. Fixes bug 9716;
13951 bugfix on every released Tor.
13952 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
13953 exit node as a NOROUTE error, not an INTERNAL error, since they
13954 can apparently happen when trying to connect to the wrong sort
13955 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
13956 - Fix build warnings about missing "a2x" comment when building the
13957 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
13958 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
13959 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
13960 not entirely remove it from the connection lists. Fixes bug 9602;
13961 bugfix on 0.2.4.4-alpha.
13962 - Fix a segmentation fault in our benchmark code when running with
13963 Fedora's OpenSSL package, or any other OpenSSL that provides
13964 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
13965 - Turn "circuit handshake stats since last time" log messages into a
13966 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
13968 o Documentation fixes:
13969 - Document that all but one DirPort entry must have the NoAdvertise
13970 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
13973 Changes in version 0.2.5.2-alpha - 2014-02-13
13974 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
13975 like the "poor random number generation" fix and the "building too many
13976 circuits" fix. It also further improves security against potential
13977 adversaries who find breaking 1024-bit crypto doable, and launches
13978 pluggable transports on demand (which gets us closer to integrating
13979 pluggable transport support by default -- not to be confused with Tor
13980 bundles enabling pluggable transports and bridges by default).
13982 o Major features (client security):
13983 - When we choose a path for a 3-hop circuit, make sure it contains
13984 at least one relay that supports the NTor circuit extension
13985 handshake. Otherwise, there is a chance that we're building
13986 a circuit that's worth attacking by an adversary who finds
13987 breaking 1024-bit crypto doable, and that chance changes the game
13988 theory. Implements ticket 9777.
13989 - Clients now look at the "usecreatefast" consensus parameter to
13990 decide whether to use CREATE_FAST or CREATE cells for the first hop
13991 of their circuit. This approach can improve security on connections
13992 where Tor's circuit handshake is stronger than the available TLS
13993 connection security levels, but the tradeoff is more computational
13994 load on guard relays. Implements proposal 221. Resolves ticket 9386.
13996 o Major features (bridges):
13997 - Don't launch pluggable transport proxies if we don't have any
13998 bridges configured that would use them. Now we can list many
13999 pluggable transports, and Tor will dynamically start one when it
14000 hears a bridge address that needs it. Resolves ticket 5018.
14001 - The bridge directory authority now assigns status flags (Stable,
14002 Guard, etc) to bridges based on thresholds calculated over all
14003 Running bridges. Now bridgedb can finally make use of its features
14004 to e.g. include at least one Stable bridge in its answers. Fixes
14007 o Major features (other):
14008 - Extend ORCONN controller event to include an "ID" parameter,
14009 and add four new controller event types CONN_BW, CIRC_BW,
14010 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
14011 The new events are emitted in private Tor networks only, with the
14012 goal of being able to better track performance and load during
14013 full-network simulations. Implements proposal 218 and ticket 7359.
14014 - On some platforms (currently: recent OSX versions, glibc-based
14015 platforms that support the ELF format, and a few other
14016 Unix-like operating systems), Tor can now dump stack traces
14017 when a crash occurs or an assertion fails. By default, traces
14018 are dumped to stderr (if possible) and to any logs that are
14019 reporting errors. Implements ticket 9299.
14022 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
14023 not entirely remove it from the connection lists. Fixes bug 9602;
14024 bugfix on 0.2.4.4-alpha.
14025 - Do not treat streams that fail with reason
14026 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
14027 since it could also indicate an ENETUNREACH connection error. Fixes
14028 part of bug 10777; bugfix on 0.2.4.8-alpha.
14030 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
14031 - Do not allow OpenSSL engines to replace the PRNG, even when
14032 HardwareAccel is set. The only default builtin PRNG engine uses
14033 the Intel RDRAND instruction to replace the entire PRNG, and
14034 ignores all attempts to seed it with more entropy. That's
14035 cryptographically stupid: the right response to a new alleged
14036 entropy source is never to discard all previously used entropy
14037 sources. Fixes bug 10402; works around behavior introduced in
14038 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
14040 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
14041 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
14042 - Avoid launching spurious extra circuits when a stream is pending.
14043 This fixes a bug where any circuit that _wasn't_ unusable for new
14044 streams would be treated as if it were, causing extra circuits to
14045 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
14047 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14048 - No longer stop reading or writing on cpuworker connections when
14049 our rate limiting buckets go empty. Now we should handle circuit
14050 handshake requests more promptly. Resolves bug 9731.
14051 - Stop trying to bootstrap all our directory information from
14052 only our first guard. Discovered while fixing bug 9946; bugfix
14055 o Minor features (bridges, pluggable transports):
14056 - Add threshold cutoffs to the networkstatus document created by
14057 the Bridge Authority. Fixes bug 1117.
14058 - On Windows, spawn background processes using the CREATE_NO_WINDOW
14059 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
14060 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
14061 Vidalia set this option for us.) Implements ticket 10297.
14063 o Minor features (security):
14064 - Always clear OpenSSL bignums before freeing them -- even bignums
14065 that don't contain secrets. Resolves ticket 10793. Patch by
14068 o Minor features (config options and command line):
14069 - Add an --allow-missing-torrc commandline option that tells Tor to
14070 run even if the configuration file specified by -f is not available.
14071 Implements ticket 10060.
14072 - Add support for the TPROXY transparent proxying facility on Linux.
14073 See documentation for the new TransProxyType option for more
14074 details. Implementation by "thomo". Closes ticket 10582.
14076 o Minor features (controller):
14077 - Add a new "HS_DESC" controller event that reports activities
14078 related to hidden service descriptors. Resolves ticket 8510.
14079 - New "DROPGUARDS" controller command to forget all current entry
14080 guards. Not recommended for ordinary use, since replacing guards
14081 too frequently makes several attacks easier. Resolves ticket 9934;
14084 o Minor features (build):
14085 - Assume that a user using ./configure --host wants to cross-compile,
14086 and give an error if we cannot find a properly named
14087 tool-chain. Add a --disable-tool-name-check option to proceed
14088 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
14089 - If we run ./configure and the compiler recognizes -fstack-protector
14090 but the linker rejects it, warn the user about a potentially missing
14091 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
14093 o Minor features (testing):
14094 - If Python is installed, "make check" now runs extra tests beyond
14095 the unit test scripts.
14096 - When bootstrapping a test network, sometimes very few relays get
14097 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
14098 specify a set of relays which should be voted Guard regardless of
14099 their uptime or bandwidth. Addresses ticket 9206.
14101 o Minor features (log messages):
14102 - When ServerTransportPlugin is set on a bridge, Tor can write more
14103 useful statistics about bridge use in its extrainfo descriptors,
14104 but only if the Extended ORPort ("ExtORPort") is set too. Add a
14105 log message to inform the user in this case. Resolves ticket 9651.
14106 - When receiving a new controller connection, log the origin address.
14107 Resolves ticket 9698; patch from "sigpipe".
14108 - When logging OpenSSL engine status at startup, log the status of
14109 more engines. Fixes ticket 10043; patch from Joshua Datko.
14110 - Turn "circuit handshake stats since last time" log messages into a
14111 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
14113 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14114 - Improve the circuit queue out-of-memory handler. Previously, when
14115 we ran low on memory, we'd close whichever circuits had the most
14116 queued cells. Now, we close those that have the *oldest* queued
14117 cells, on the theory that those are most responsible for us
14118 running low on memory. Based on analysis from a forthcoming paper
14119 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
14120 - Generate bootstrapping status update events correctly when fetching
14121 microdescriptors. Fixes bug 9927.
14122 - Update to the October 2 2013 Maxmind GeoLite Country database.
14124 o Minor bugfixes (clients):
14125 - When closing a channel that has already been open, do not close
14126 pending circuits that were waiting to connect to the same relay.
14127 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
14130 o Minor bugfixes (relays):
14131 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
14132 exit node as a NOROUTE error, not an INTERNAL error, since they
14133 can apparently happen when trying to connect to the wrong sort
14134 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
14136 o Minor bugfixes (bridges):
14137 - Fix a bug where the first connection works to a bridge that uses a
14138 pluggable transport with client-side parameters, but we don't send
14139 the client-side parameters on subsequent connections. (We don't
14140 use any pluggable transports with client-side parameters yet,
14141 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
14142 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
14144 o Minor bugfixes (node selection):
14145 - If ExcludeNodes is set, consider non-excluded hidden service
14146 directory servers before excluded ones. Do not consider excluded
14147 hidden service directory servers at all if StrictNodes is
14148 set. (Previously, we would sometimes decide to connect to those
14149 servers, and then realize before we initiated a connection that
14150 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
14151 Reported by "mr-4".
14152 - If we set the ExitNodes option but it doesn't include any nodes
14153 that have the Exit flag, we would choose not to bootstrap. Now we
14154 bootstrap so long as ExitNodes includes nodes which can exit to
14155 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
14157 o Minor bugfixes (controller and command-line):
14158 - If changing a config option via "setconf" fails in a recoverable
14159 way, we used to nonetheless write our new control ports to the
14160 file described by the "ControlPortWriteToFile" option. Now we only
14161 write out that file if we successfully switch to the new config
14162 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
14163 - When a command-line option such as --version or --help that
14164 ordinarily implies --hush appears on the command line along with
14165 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
14166 only if it appeared later on the command line. Fixes bug 9578;
14167 bugfix on 0.2.5.1-alpha.
14169 o Minor bugfixes (code correctness):
14170 - Previously we used two temporary files when writing descriptors to
14171 disk; now we only use one. Fixes bug 1376.
14172 - Remove an erroneous (but impossible and thus harmless) pointer
14173 comparison that would have allowed compilers to skip a bounds
14174 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
14175 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
14176 - Fix an always-true assertion in pluggable transports code so it
14177 actually checks what it was trying to check. Fixes bug 10046;
14178 bugfix on 0.2.3.9-alpha. Found by "dcb".
14180 o Minor bugfixes (protocol correctness):
14181 - When receiving a VERSIONS cell with an odd number of bytes, close
14182 the connection immediately since the cell is malformed. Fixes bug
14183 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
14186 o Minor bugfixes (build):
14187 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
14188 turned off (that is, without support for v2 link handshakes). Fixes
14189 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
14190 - Fix compilation warnings and startup issues when running with
14191 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
14193 - Fix compilation on Solaris 9, which didn't like us having an
14194 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
14196 o Minor bugfixes (testing):
14197 - Fix a segmentation fault in our benchmark code when running with
14198 Fedora's OpenSSL package, or any other OpenSSL that provides
14199 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
14201 o Minor bugfixes (log messages):
14202 - Fix a bug where clients using bridges would report themselves
14203 as 50% bootstrapped even without a live consensus document.
14204 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
14205 - Suppress a warning where, if there's only one directory authority
14206 in the network, we would complain that votes and signatures cannot
14207 be uploaded to other directory authorities. Fixes bug 10842;
14208 bugfix on 0.2.2.26-beta.
14209 - Report bootstrapping progress correctly when we're downloading
14210 microdescriptors. We had updated our "do we have enough microdescs
14211 to begin building circuits?" logic most recently in 0.2.4.10-alpha
14212 (see bug 5956), but we left the bootstrap status event logic at
14213 "how far through getting 1/4 of them are we?" Fixes bug 9958;
14214 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
14216 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
14217 - Avoid a crash bug when starting with a corrupted microdescriptor
14218 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
14219 - If we fail to dump a previously cached microdescriptor to disk, avoid
14220 freeing duplicate data later on. Fixes bug 10423; bugfix on
14221 0.2.4.13-alpha. Spotted by "bobnomnom".
14223 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14224 - Correctly log long IPv6 exit policies, instead of truncating them
14225 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
14226 - Our default TLS ecdhe groups were backwards: we meant to be using
14227 P224 for relays (for performance win) and P256 for bridges (since
14228 it is more common in the wild). Instead we had it backwards. After
14229 reconsideration, we decided that the default should be P256 on all
14230 hosts, since its security is probably better, and since P224 is
14231 reportedly used quite little in the wild. Found by "skruffy" on
14232 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
14233 - Free directory authority certificate download statuses on exit
14234 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
14236 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14237 - If the guard we choose first doesn't answer, we would try the
14238 second guard, but once we connected to the second guard we would
14239 abandon it and retry the first one, slowing down bootstrapping.
14240 The fix is to treat all our initially chosen guards as acceptable
14241 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
14242 - Fix an assertion failure that would occur when disabling the
14243 ORPort setting on a running Tor process while accounting was
14244 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
14245 - When examining the list of network interfaces to find our address,
14246 do not consider non-running or disabled network interfaces. Fixes
14247 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
14248 - Avoid an off-by-one error when checking buffer boundaries when
14249 formatting the exit status of a pluggable transport helper.
14250 This is probably not an exploitable bug, but better safe than
14251 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
14254 o Removed code and features:
14255 - Clients now reject any directory authority certificates lacking
14256 a dir-key-crosscert element. These have been included since
14257 0.2.1.9-alpha, so there's no real reason for them to be optional
14258 any longer. Completes proposal 157. Resolves ticket 10162.
14259 - Remove all code that existed to support the v2 directory system,
14260 since there are no longer any v2 directory authorities. Resolves
14262 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
14263 options, which were used for designating authorities as "Hidden
14264 service authorities". There has been no use of hidden service
14265 authorities since 0.2.2.1-alpha, when we stopped uploading or
14266 downloading v0 hidden service descriptors. Fixes bug 10881; also
14267 part of a fix for bug 10841.
14269 o Code simplification and refactoring:
14270 - Remove some old fallback code designed to keep Tor clients working
14271 in a network with only two working relays. Elsewhere in the code we
14272 have long since stopped supporting such networks, so there wasn't
14273 much point in keeping it around. Addresses ticket 9926.
14274 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
14275 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
14276 - Remove data structures which were introduced to implement the
14277 CellStatistics option: they are now redundant with the addition
14278 of a timestamp to the regular packed_cell_t data structure, which
14279 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
14282 o Documentation (man page) fixes:
14283 - Update manpage to describe some of the files you can expect to
14284 find in Tor's DataDirectory. Addresses ticket 9839.
14285 - Document that all but one DirPort entry must have the NoAdvertise
14286 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
14288 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
14289 - Clarify the usage and risks of setting the ContactInfo torrc line
14290 for your relay or bridge. Resolves ticket 9854.
14291 - Add anchors to the manpage so we can link to the html version of
14292 the documentation for specific options. Resolves ticket 9866.
14293 - Replace remaining references to DirServer in man page and
14294 log entries. Resolves ticket 10124.
14297 - Make the "tor-gencert" tool used by directory authority operators
14298 create 2048-bit signing keys by default (rather than 1024-bit, since
14299 1024-bit is uncomfortably small these days). Addresses ticket 10324.
14302 Changes in version 0.2.4.20 - 2013-12-22
14303 Tor 0.2.4.20 fixes potentially poor random number generation for users
14304 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
14305 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
14306 and 4) have no state file in their DataDirectory (as would happen on
14307 first start). Users who generated relay or hidden service identity
14308 keys in such a situation should discard them and generate new ones.
14310 This release also fixes a logic error that caused Tor clients to build
14311 many more preemptive circuits than they actually need.
14314 - Do not allow OpenSSL engines to replace the PRNG, even when
14315 HardwareAccel is set. The only default builtin PRNG engine uses
14316 the Intel RDRAND instruction to replace the entire PRNG, and
14317 ignores all attempts to seed it with more entropy. That's
14318 cryptographically stupid: the right response to a new alleged
14319 entropy source is never to discard all previously used entropy
14320 sources. Fixes bug 10402; works around behavior introduced in
14321 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
14323 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
14324 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
14325 - Avoid launching spurious extra circuits when a stream is pending.
14326 This fixes a bug where any circuit that _wasn't_ unusable for new
14327 streams would be treated as if it were, causing extra circuits to
14328 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
14331 - Avoid a crash bug when starting with a corrupted microdescriptor
14332 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
14333 - If we fail to dump a previously cached microdescriptor to disk, avoid
14334 freeing duplicate data later on. Fixes bug 10423; bugfix on
14335 0.2.4.13-alpha. Spotted by "bobnomnom".
14338 Changes in version 0.2.4.19 - 2013-12-11
14339 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
14340 (1986-2013). Aaron worked on diverse projects including helping to guide
14341 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
14342 transparency to the U.S government's PACER documents, and contributing
14343 design and development for Tor and Tor2Web. Aaron was one of the latest
14344 martyrs in our collective fight for civil liberties and human rights,
14345 and his death is all the more painful because he was one of us.
14347 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
14348 a new circuit handshake and link encryption that use ECC to provide
14349 better security and efficiency; makes relays better manage circuit
14350 creation requests; uses "directory guards" to reduce client enumeration
14351 risks; makes bridges collect and report statistics about the pluggable
14352 transports they support; cleans up and improves our geoip database;
14353 gets much closer to IPv6 support for clients, bridges, and relays; makes
14354 directory authorities use measured bandwidths rather than advertised
14355 ones when computing flags and thresholds; disables client-side DNS
14356 caching to reduce tracking risks; and fixes a big bug in bridge
14357 reachability testing. This release introduces two new design
14358 abstractions in the code: a new "channel" abstraction between circuits
14359 and or_connections to allow for implementing alternate relay-to-relay
14360 transports, and a new "circuitmux" abstraction storing the queue of
14361 circuits for a channel. The release also includes many stability,
14362 security, and privacy fixes.
14365 Changes in version 0.2.4.18-rc - 2013-11-16
14366 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
14367 series. It takes a variety of fixes from the 0.2.5.x branch to improve
14368 stability, performance, and better handling of edge cases.
14371 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
14372 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
14373 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
14374 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
14375 them to solve bug 6033.)
14378 - No longer stop reading or writing on cpuworker connections when
14379 our rate limiting buckets go empty. Now we should handle circuit
14380 handshake requests more promptly. Resolves bug 9731.
14381 - If we are unable to save a microdescriptor to the journal, do not
14382 drop it from memory and then reattempt downloading it. Fixes bug
14383 9645; bugfix on 0.2.2.6-alpha.
14384 - Stop trying to bootstrap all our directory information from
14385 only our first guard. Discovered while fixing bug 9946; bugfix
14387 - The new channel code sometimes lost track of in-progress circuits,
14388 causing long-running clients to stop building new circuits. The
14389 fix is to always call circuit_n_chan_done(chan, 0) from
14390 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
14392 o Minor bugfixes (on 0.2.4.x):
14393 - Correctly log long IPv6 exit policies, instead of truncating them
14394 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
14395 - Our default TLS ecdhe groups were backwards: we meant to be using
14396 P224 for relays (for performance win) and P256 for bridges (since
14397 it is more common in the wild). Instead we had it backwards. After
14398 reconsideration, we decided that the default should be P256 on all
14399 hosts, since its security is probably better, and since P224 is
14400 reportedly used quite little in the wild. Found by "skruffy" on
14401 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
14402 - Free directory authority certificate download statuses on exit
14403 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
14405 o Minor bugfixes (on 0.2.3.x and earlier):
14406 - If the guard we choose first doesn't answer, we would try the
14407 second guard, but once we connected to the second guard we would
14408 abandon it and retry the first one, slowing down bootstrapping.
14409 The fix is to treat all our initially chosen guards as acceptable
14410 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
14411 - Fix an assertion failure that would occur when disabling the
14412 ORPort setting on a running Tor process while accounting was
14413 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
14414 - When examining the list of network interfaces to find our address,
14415 do not consider non-running or disabled network interfaces. Fixes
14416 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
14417 - Avoid an off-by-one error when checking buffer boundaries when
14418 formatting the exit status of a pluggable transport helper.
14419 This is probably not an exploitable bug, but better safe than
14420 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
14423 o Minor features (protecting client timestamps):
14424 - Clients no longer send timestamps in their NETINFO cells. These were
14425 not used for anything, and they provided one small way for clients
14426 to be distinguished from each other as they moved from network to
14427 network or behind NAT. Implements part of proposal 222.
14428 - Clients now round timestamps in INTRODUCE cells down to the nearest
14429 10 minutes. If a new Support022HiddenServices option is set to 0, or
14430 if it's set to "auto" and the feature is disabled in the consensus,
14431 the timestamp is sent as 0 instead. Implements part of proposal 222.
14432 - Stop sending timestamps in AUTHENTICATE cells. This is not such
14433 a big deal from a security point of view, but it achieves no actual
14434 good purpose, and isn't needed. Implements part of proposal 222.
14435 - Reduce down accuracy of timestamps in hidden service descriptors.
14436 Implements part of proposal 222.
14438 o Minor features (other):
14439 - Improve the circuit queue out-of-memory handler. Previously, when
14440 we ran low on memory, we'd close whichever circuits had the most
14441 queued cells. Now, we close those that have the *oldest* queued
14442 cells, on the theory that those are most responsible for us
14443 running low on memory. Based on analysis from a forthcoming paper
14444 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
14445 - Generate bootstrapping status update events correctly when fetching
14446 microdescriptors. Fixes bug 9927.
14447 - Update to the October 2 2013 Maxmind GeoLite Country database.
14449 o Documentation fixes:
14450 - Clarify the usage and risks of setting the ContactInfo torrc line
14451 for your relay or bridge. Resolves ticket 9854.
14452 - Add anchors to the manpage so we can link to the html version of
14453 the documentation for specific options. Resolves ticket 9866.
14454 - Replace remaining references to DirServer in man page and
14455 log entries. Resolves ticket 10124.
14458 Changes in version 0.2.5.1-alpha - 2013-10-02
14459 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
14460 on Linux, allows bridges that offer pluggable transports to report usage
14461 statistics, fixes many issues to make testing easier, and provides
14462 a pile of minor features and bugfixes that have been waiting for a
14463 release of the new branch.
14465 This is the first alpha release in a new series, so expect there to
14466 be bugs. Users who would rather test out a more stable branch should
14467 stay with 0.2.4.x for now.
14469 o Major features (security):
14470 - Use the seccomp2 syscall filtering facility on Linux to limit
14471 which system calls Tor can invoke. This is an experimental,
14472 Linux-only feature to provide defense-in-depth against unknown
14473 attacks. To try turning it on, set "Sandbox 1" in your torrc
14474 file. Please be ready to report bugs. We hope to add support
14475 for better sandboxing in the future, including more fine-grained
14476 filters, better division of responsibility, and support for more
14477 platforms. This work has been done by Cristian-Matei Toader for
14478 Google Summer of Code.
14479 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
14480 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
14481 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
14482 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
14483 them to solve bug 6033.)
14485 o Major features (other):
14486 - Add support for passing arguments to managed pluggable transport
14487 proxies. Implements ticket 3594.
14488 - Bridges now track GeoIP information and the number of their users
14489 even when pluggable transports are in use, and report usage
14490 statistics in their extra-info descriptors. Resolves tickets 4773
14492 - Make testing Tor networks bootstrap better: lower directory fetch
14493 retry schedules and maximum interval without directory requests,
14494 and raise maximum download tries. Implements ticket 6752.
14495 - Add make target 'test-network' to run tests on a Chutney network.
14496 Implements ticket 8530.
14497 - The ntor handshake is now on-by-default, no matter what the
14498 directory authorities recommend. Implements ticket 8561.
14501 - Instead of writing destroy cells directly to outgoing connection
14502 buffers, queue them and intersperse them with other outgoing cells.
14503 This can prevent a set of resource starvation conditions where too
14504 many pending destroy cells prevent data cells from actually getting
14505 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
14506 bugfix on 0.2.0.1-alpha.
14507 - If we are unable to save a microdescriptor to the journal, do not
14508 drop it from memory and then reattempt downloading it. Fixes bug
14509 9645; bugfix on 0.2.2.6-alpha.
14510 - The new channel code sometimes lost track of in-progress circuits,
14511 causing long-running clients to stop building new circuits. The
14512 fix is to always call circuit_n_chan_done(chan, 0) from
14513 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
14516 - Tor now builds each source file in two modes: a mode that avoids
14517 exposing identifiers needlessly, and another mode that exposes
14518 more identifiers for testing. This lets the compiler do better at
14519 optimizing the production code, while enabling us to take more
14520 radical measures to let the unit tests test things.
14521 - The production builds no longer include functions used only in
14522 the unit tests; all functions exposed from a module only for
14523 unit-testing are now static in production builds.
14524 - Add an --enable-coverage configuration option to make the unit
14525 tests (and a new src/or/tor-cov target) to build with gcov test
14529 - We now have rudimentary function mocking support that our unit
14530 tests can use to test functions in isolation. Function mocking
14531 lets the tests temporarily replace a function's dependencies with
14532 stub functions, so that the tests can check the function without
14533 invoking the other functions it calls.
14534 - Add more unit tests for the <circid,channel>->circuit map, and
14535 the destroy-cell-tracking code to fix bug 7912.
14536 - Unit tests for failing cases of the TAP onion handshake.
14537 - More unit tests for address-manipulation functions.
14539 o Minor features (protecting client timestamps):
14540 - Clients no longer send timestamps in their NETINFO cells. These were
14541 not used for anything, and they provided one small way for clients
14542 to be distinguished from each other as they moved from network to
14543 network or behind NAT. Implements part of proposal 222.
14544 - Clients now round timestamps in INTRODUCE cells down to the nearest
14545 10 minutes. If a new Support022HiddenServices option is set to 0, or
14546 if it's set to "auto" and the feature is disabled in the consensus,
14547 the timestamp is sent as 0 instead. Implements part of proposal 222.
14548 - Stop sending timestamps in AUTHENTICATE cells. This is not such
14549 a big deal from a security point of view, but it achieves no actual
14550 good purpose, and isn't needed. Implements part of proposal 222.
14551 - Reduce down accuracy of timestamps in hidden service descriptors.
14552 Implements part of proposal 222.
14554 o Minor features (config options):
14555 - Config (torrc) lines now handle fingerprints which are missing
14556 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
14557 - Support a --dump-config option to print some or all of the
14558 configured options. Mainly useful for debugging the command-line
14559 option parsing code. Helps resolve ticket 4647.
14560 - Raise awareness of safer logging: notify user of potentially
14561 unsafe config options, like logging more verbosely than severity
14562 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
14563 - Add a new configuration option TestingV3AuthVotingStartOffset
14564 that bootstraps a network faster by changing the timing for
14565 consensus votes. Addresses ticket 8532.
14566 - Add a new torrc option "ServerTransportOptions" that allows
14567 bridge operators to pass configuration parameters to their
14568 pluggable transports. Resolves ticket 8929.
14569 - The config (torrc) file now accepts bandwidth and space limits in
14570 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
14571 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
14574 o Minor features (build):
14575 - Add support for `--library-versions` flag. Implements ticket 6384.
14576 - Return the "unexpected sendme" warnings to a warn severity, but make
14577 them rate limited, to help diagnose ticket 8093.
14578 - Detect a missing asciidoc, and warn the user about it, during
14579 configure rather than at build time. Fixes issue 6506. Patch from
14582 o Minor features (other):
14583 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
14584 sockets in a single system call. Implements ticket 5129.
14585 - Log current accounting state (bytes sent and received + remaining
14586 time for the current accounting period) in the relay's heartbeat
14587 message. Implements ticket 5526; patch from Peter Retzlaff.
14588 - Implement the TRANSPORT_LAUNCHED control port event that
14589 notifies controllers about new launched pluggable
14590 transports. Resolves ticket 5609.
14591 - If we're using the pure-C 32-bit curve25519_donna implementation
14592 of curve25519, build it with the -fomit-frame-pointer option to
14593 make it go faster on register-starved hosts. This improves our
14594 handshake performance by about 6% on i386 hosts without nacl.
14595 Closes ticket 8109.
14596 - Update to the September 4 2013 Maxmind GeoLite Country database.
14599 - Set the listen() backlog limit to the largest actually supported
14600 on the system, not to the value in a header file. Fixes bug 9716;
14601 bugfix on every released Tor.
14602 - No longer accept malformed http headers when parsing urls from
14603 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
14604 bugfix on 0.0.6pre1.
14605 - In munge_extrainfo_into_routerinfo(), check the return value of
14606 memchr(). This would have been a serious issue if we ever passed
14607 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
14609 - On the chance that somebody manages to build Tor on a
14610 platform where time_t is unsigned, correct the way that
14611 microdesc_add_to_cache() handles negative time arguments.
14612 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
14613 - Reject relative control socket paths and emit a warning. Previously,
14614 single-component control socket paths would be rejected, but Tor
14615 would not log why it could not validate the config. Fixes bug 9258;
14616 bugfix on 0.2.3.16-alpha.
14618 o Minor bugfixes (command line):
14619 - Use a single command-line parser for parsing torrc options on the
14620 command line and for finding special command-line options to avoid
14621 inconsistent behavior for torrc option arguments that have the same
14622 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
14624 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
14625 9573; bugfix on 0.0.9pre5.
14627 o Minor fixes (build, auxiliary programs):
14628 - Stop preprocessing the "torify" script with autoconf, since
14629 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
14631 - The tor-fw-helper program now follows the standard convention and
14632 exits with status code "0" on success. Fixes bug 9030; bugfix on
14633 0.2.3.1-alpha. Patch by Arlo Breault.
14634 - Corrected ./configure advice for what openssl dev package you should
14635 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
14637 o Minor code improvements:
14638 - Remove constants and tests for PKCS1 padding; it's insecure and
14639 shouldn't be used for anything new. Fixes bug 8792; patch
14641 - Remove instances of strcpy() from the unit tests. They weren't
14642 hurting anything, since they were only in the unit tests, but it's
14643 embarrassing to have strcpy() in the code at all, and some analysis
14644 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
14645 0.2.3.8-alpha. Patch from Arlo Breault.
14647 o Removed features:
14648 - Remove migration code from when we renamed the "cached-routers"
14649 file to "cached-descriptors" back in 0.2.0.8-alpha. This
14650 incidentally resolves ticket 6502 by cleaning up the related code
14651 a bit. Patch from Akshay Hebbar.
14653 o Code simplification and refactoring:
14654 - Extract the common duplicated code for creating a subdirectory
14655 of the data directory and writing to a file in it. Fixes ticket
14656 4282; patch from Peter Retzlaff.
14657 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
14658 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
14659 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
14660 - Add a set of accessor functions for the circuit timeout data
14661 structure. Fixes ticket 6153; patch from "piet".
14662 - Clean up exit paths from connection_listener_new(). Closes ticket
14663 8789. Patch from Arlo Breault.
14664 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
14665 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
14666 - Use a doubly-linked list to implement the global circuit list.
14667 Resolves ticket 9108. Patch from Marek Majkowski.
14668 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
14671 Changes in version 0.2.4.17-rc - 2013-09-05
14672 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
14673 series. It adds an emergency step to help us tolerate the massive
14674 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
14675 circuit-level handshakes now effectively jump the queue compared to
14676 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
14677 big bug hindering bridge reachability tests.
14680 - Relays now process the new "NTor" circuit-level handshake requests
14681 with higher priority than the old "TAP" circuit-level handshake
14682 requests. We still process some TAP requests to not totally starve
14683 0.2.3 clients when NTor becomes popular. A new consensus parameter
14684 "NumNTorsPerTAP" lets us tune the balance later if we need to.
14685 Implements ticket 9574.
14688 - If the circuit build timeout logic is disabled (via the consensus,
14689 or because we are an authority), then don't build testing circuits.
14690 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
14691 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
14692 previously they did not, which prevented them from receiving
14693 successful connections from relays for self-test or bandwidth
14694 testing. Also, when a relay is extending a circuit to a bridge,
14695 it needs to send a NETINFO cell, even when the bridge hasn't sent
14696 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
14697 - If the time to download the next old-style networkstatus is in
14698 the future, do not decline to consider whether to download the
14699 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
14703 - Avoid double-closing the listener socket in our socketpair()
14704 replacement (used on Windows) in the case where the addresses on
14705 our opened sockets don't match what we expected. Fixes bug 9400;
14706 bugfix on 0.0.2pre7. Found by Coverity.
14708 o Minor fixes (config options):
14709 - Avoid overflows when the user sets MaxCircuitDirtiness to a
14710 ridiculously high value, by imposing a (ridiculously high) 30-day
14711 maximum on MaxCircuitDirtiness.
14712 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
14713 message is logged at notice, not at info.
14714 - Warn and fail if a server is configured not to advertise any
14715 ORPorts at all. (We need *something* to put in our descriptor,
14716 or we just won't work.)
14719 - Track how many "TAP" and "NTor" circuit handshake requests we get,
14720 and how many we complete, and log it every hour to help relay
14721 operators follow trends in network load. Addresses ticket 9658.
14722 - Update to the August 7 2013 Maxmind GeoLite Country database.
14725 Changes in version 0.2.4.16-rc - 2013-08-10
14726 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
14727 series. It fixes several crash bugs in the 0.2.4 branch.
14730 - Fix a bug in the voting algorithm that could yield incorrect results
14731 when a non-naming authority declared too many flags. Fixes bug 9200;
14732 bugfix on 0.2.0.3-alpha.
14733 - Fix an uninitialized read that could in some cases lead to a remote
14734 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
14735 Anybody running a hidden service on the experimental 0.2.4.x
14736 branch should upgrade. (This is, so far as we know, unrelated to
14738 - Avoid an assertion failure when processing DNS replies without the
14739 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
14740 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
14741 0.2.4.15-rc. Found by stem integration tests.
14744 - Fix an invalid memory read that occurred when a pluggable
14745 transport proxy failed its configuration protocol.
14746 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
14747 - When evaluating whether to use a connection that we haven't
14748 decided is canonical using a recent link protocol version,
14749 decide that it's canonical only if it used address _does_
14750 match the desired address. Fixes bug 9309; bugfix on
14751 0.2.4.4-alpha. Reported by skruffy.
14752 - Make the default behavior of NumDirectoryGuards be to track
14753 NumEntryGuards. Now a user who changes only NumEntryGuards will get
14754 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
14755 - Fix a spurious compilation warning with some older versions of
14756 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
14759 - Update to the July 3 2013 Maxmind GeoLite Country database.
14762 Changes in version 0.2.4.15-rc - 2013-07-01
14763 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
14764 series. It fixes a few smaller bugs, but generally appears stable.
14765 Please test it and let us know whether it is!
14768 - When receiving a new configuration file via the control port's
14769 LOADCONF command, do not treat the defaults file as absent.
14770 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
14773 - Issue a warning when running with the bufferevents backend enabled.
14774 It's still not stable, and people should know that they're likely
14775 to hit unexpected problems. Closes ticket 9147.
14778 Changes in version 0.2.4.14-alpha - 2013-06-18
14779 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
14780 present in 0.2.4.13-alpha.
14783 - When we have too much memory queued in circuits (according to a new
14784 MaxMemInCellQueues option), close the circuits consuming the most
14785 memory. This prevents us from running out of memory as a relay if
14786 circuits fill up faster than they can be drained. Fixes bug 9063;
14787 bugfix on the 54th commit of Tor. This bug is a further fix beyond
14788 bug 6252, whose fix was merged into 0.2.3.21-rc.
14790 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
14791 where we tried to solve this issue simply by imposing an upper limit
14792 on the number of queued cells for a single circuit. That approach
14793 proved to be problematic, since there are ways to provoke clients to
14794 send a number of cells in excess of any such reasonable limit. Fixes
14795 bug 9072; bugfix on 0.2.4.13-alpha.
14797 - Limit hidden service descriptors to at most ten introduction
14798 points, to slow one kind of guard enumeration. Fixes bug 9002;
14799 bugfix on 0.1.1.11-alpha.
14802 Changes in version 0.2.4.13-alpha - 2013-06-14
14803 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
14804 vulnerabilities, makes socks5 username/password circuit isolation
14805 actually actually work (this time for sure!), and cleans up a bunch
14806 of other issues in preparation for a release candidate.
14808 o Major bugfixes (robustness):
14809 - Close any circuit that has too many cells queued on it. Fixes
14810 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
14811 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
14812 - Prevent the get_freelists() function from running off the end of
14813 the list of freelists if it somehow gets an unrecognized
14814 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
14816 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
14817 when an exit connection with optimistic data succeeds immediately
14818 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
14820 - Fix a directory authority crash bug when building a consensus
14821 using an older consensus as its basis. Fixes bug 8833. Bugfix
14825 - Avoid a memory leak where we would leak a consensus body when we
14826 find that a consensus which we couldn't previously verify due to
14827 missing certificates is now verifiable. Fixes bug 8719; bugfix
14829 - We used to always request authority certificates by identity digest,
14830 meaning we'd get the newest one even when we wanted one with a
14831 different signing key. Then we would complain about being given
14832 a certificate we already had, and never get the one we really
14833 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
14834 resource to request the one we want. Fixes bug 5595; bugfix on
14836 - Follow the socks5 protocol when offering username/password
14837 authentication. The fix for bug 8117 exposed this bug, and it
14838 turns out real-world applications like Pidgin do care. Bugfix on
14839 0.2.3.2-alpha; fixes bug 8879.
14840 - Prevent failures on Windows Vista and later when rebuilding the
14841 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
14842 bugfix on 0.2.4.12-alpha.
14845 - Fix an impossible buffer overrun in the AES unit tests. Fixes
14846 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
14847 - If for some reason we fail to write a microdescriptor while
14848 rebuilding the cache, do not let the annotations from that
14849 microdescriptor linger in the cache file, and do not let the
14850 microdescriptor stay recorded as present in its old location.
14851 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
14852 - Fix a memory leak that would occur whenever a configuration
14853 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
14854 - Paste the description for PathBias parameters from the man
14855 page into or.h, so the code documents them too. Fixes bug 7982;
14856 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
14857 - Relays now treat a changed IPv6 ORPort as sufficient reason to
14858 publish an updated descriptor. Fixes bug 6026; bugfix on
14860 - When launching a resolve request on behalf of an AF_UNIX control
14861 socket, omit the address field of the new entry connection, used in
14862 subsequent controller events, rather than letting tor_dup_addr()
14863 set it to "<unknown address type>". Fixes bug 8639; bugfix on
14866 o Minor bugfixes (log messages):
14867 - Fix a scaling issue in the path bias accounting code that
14868 resulted in "Bug:" log messages from either
14869 pathbias_scale_close_rates() or pathbias_count_build_success().
14870 This represents a bugfix on a previous bugfix: the original fix
14871 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
14873 - Give a less useless error message when the user asks for an IPv4
14874 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
14878 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
14879 to tolerate bug 8093 for now.
14880 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
14881 in directory authority votes to describe whether they have enough
14882 measured bandwidths to ignore advertised (relay descriptor)
14883 bandwidth claims. Resolves ticket 8711.
14884 - Update to the June 5 2013 Maxmind GeoLite Country database.
14886 o Removed documentation:
14887 - Remove some of the older contents of doc/ as obsolete; move others
14888 to torspec.git. Fixes bug 8965.
14890 o Code simplification and refactoring:
14891 - Avoid using character buffers when constructing most directory
14892 objects: this approach was unwieldy and error-prone. Instead,
14893 build smartlists of strings, and concatenate them when done.
14896 Changes in version 0.2.4.12-alpha - 2013-04-18
14897 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
14898 process for lengthening the guard rotation period, makes directory
14899 authority opinions in the consensus a bit less gameable, makes socks5
14900 username/password circuit isolation actually work, and fixes a wide
14901 variety of other issues.
14904 - Raise the default time that a client keeps an entry guard from
14905 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
14906 2012 paper. (We would make it even longer, but we need better client
14907 load balancing first.) Also, make the guard lifetime controllable
14908 via a new GuardLifetime torrc option and a GuardLifetime consensus
14909 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
14910 - Directory authorities now prefer using measured bandwidths to
14911 advertised ones when computing flags and thresholds. Resolves
14913 - Directory authorities that have more than a threshold number
14914 of relays with measured bandwidths now treat relays with unmeasured
14915 bandwidths as having bandwidth 0. Resolves ticket 8435.
14917 o Major bugfixes (assert / resource use):
14918 - Avoid a bug where our response to TLS renegotiation under certain
14919 network conditions could lead to a busy-loop, with 100% CPU
14920 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
14921 - Avoid an assertion when we discover that we'd like to write a cell
14922 onto a closing connection: just discard the cell. Fixes another
14923 case of bug 7350; bugfix on 0.2.4.4-alpha.
14925 o Major bugfixes (client-side privacy):
14926 - When we mark a circuit as unusable for new circuits, have it
14927 continue to be unusable for new circuits even if MaxCircuitDirtiness
14928 is increased too much at the wrong time, or the system clock jumps
14929 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
14930 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
14931 which have resolved to internal addresses") is set, apply that
14932 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
14933 - When an exit relay rejects a stream with reason "exit policy", but
14934 we only know an exit policy summary (e.g. from the microdesc
14935 consensus) for it, do not mark the relay as useless for all exiting.
14936 Instead, mark just the circuit as unsuitable for that particular
14937 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
14938 - Allow applications to get proper stream isolation with
14939 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
14940 username/password authentication also offer "no authentication". Tor
14941 had previously preferred "no authentication", so the applications
14942 never actually sent Tor their auth details. Now Tor selects
14943 username/password authentication if it's offered. You can disable
14944 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
14945 bug 8117; bugfix on 0.2.3.3-alpha.
14947 o Major bugfixes (other):
14948 - When unable to find any working directory nodes to use as a
14949 directory guard, give up rather than adding the same non-working
14950 nodes to the directory guard list over and over. Fixes bug 8231;
14951 bugfix on 0.2.4.8-alpha.
14954 - Reject as invalid most directory objects containing a NUL.
14955 Belt-and-suspender fix for bug 8037.
14956 - In our testsuite, create temporary directories with a bit more
14957 entropy in their name to make name collisions less likely. Fixes
14959 - Add CACHED keyword to ADDRMAP events in the control protocol
14960 to indicate whether a DNS result will be cached or not. Resolves
14962 - Update to the April 3 2013 Maxmind GeoLite Country database.
14964 o Minor features (build):
14965 - Detect and reject attempts to build Tor with threading support
14966 when OpenSSL has been compiled without threading support.
14968 - Clarify that when autoconf is checking for nacl, it is checking
14969 specifically for nacl with a fast curve25519 implementation.
14971 - Warn if building on a platform with an unsigned time_t: there
14972 are too many places where Tor currently assumes that time_t can
14973 hold negative values. We'd like to fix them all, but probably
14976 o Minor bugfixes (build):
14977 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
14978 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
14979 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
14980 - Add the old src/or/micro-revision.i filename to CLEANFILES.
14981 On the off chance that somebody has one, it will go away as soon
14982 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
14983 - Build Tor correctly on 32-bit platforms where the compiler can build
14984 but not run code using the "uint128_t" construction. Fixes bug 8587;
14985 bugfix on 0.2.4.8-alpha.
14986 - Fix compilation warning with some versions of clang that would
14987 prefer the -Wswitch-enum compiler flag to warn about switch
14988 statements with missing enum values, even if those switch
14989 statements have a "default:" statement. Fixes bug 8598; bugfix
14992 o Minor bugfixes (protocol):
14993 - Fix the handling of a TRUNCATE cell when it arrives while the
14994 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
14995 - Fix a misframing issue when reading the version numbers in a
14996 VERSIONS cell. Previously we would recognize [00 01 00 02] as
14997 'version 1, version 2, and version 0x100', when it should have
14998 only included versions 1 and 2. Fixes bug 8059; bugfix on
14999 0.2.0.10-alpha. Reported pseudonymously.
15000 - Make the format and order of STREAM events for DNS lookups
15001 consistent among the various ways to launch DNS lookups. Fixes
15002 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
15003 - Correct our check for which versions of Tor support the EXTEND2
15004 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
15005 later, when support was really added in version 0.2.4.8-alpha.
15006 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
15008 o Minor bugfixes (other):
15009 - Correctly store microdescriptors and extrainfo descriptors with
15010 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
15011 Bug reported by "cypherpunks".
15012 - Increase the width of the field used to remember a connection's
15013 link protocol version to two bytes. Harmless for now, since the
15014 only currently recognized versions are one byte long. Reported
15015 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
15016 - If the state file's path bias counts are invalid (presumably from a
15017 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
15018 additional checks and log messages to the scaling of Path Bias
15019 counts, in case there still are remaining issues with scaling.
15020 Should help resolve bug 8235.
15021 - Eliminate several instances where we use "Nickname=ID" to refer to
15022 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
15023 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
15024 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
15026 o Minor bugfixes (syscalls):
15027 - Always check the return values of functions fcntl() and
15028 setsockopt(). We don't believe these are ever actually failing in
15029 practice, but better safe than sorry. Also, checking these return
15030 values should please analysis tools like Coverity. Patch from
15031 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
15032 - Use direct writes rather than stdio when building microdescriptor
15033 caches, in an attempt to mitigate bug 8031, or at least make it
15036 o Minor bugfixes (config):
15037 - When rejecting a configuration because we were unable to parse a
15038 quoted string, log an actual error message. Fixes bug 7950; bugfix
15040 - Behave correctly when the user disables LearnCircuitBuildTimeout
15041 but doesn't tell us what they would like the timeout to be. Fixes
15042 bug 6304; bugfix on 0.2.2.14-alpha.
15043 - When autodetecting the number of CPUs, use the number of available
15044 CPUs in preference to the number of configured CPUs. Inform the
15045 user if this reduces the number of available CPUs. Fixes bug 8002;
15046 bugfix on 0.2.3.1-alpha.
15047 - Make it an error when you set EntryNodes but disable UseGuardNodes,
15048 since it will (surprisingly to some users) ignore EntryNodes. Fixes
15049 bug 8180; bugfix on 0.2.3.11-alpha.
15050 - Allow TestingTorNetworks to override the 4096-byte minimum for
15051 the Fast threshold. Otherwise they can't bootstrap until they've
15052 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
15053 - Fix some logic errors when the user manually overrides the
15054 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
15057 o Minor bugfixes (log messages to help diagnose bugs):
15058 - If we fail to free a microdescriptor because of bug 7164, log
15059 the filename and line number from which we tried to free it.
15060 - Add another diagnostic to the heartbeat message: track and log
15061 overhead that TLS is adding to the data we write. If this is
15062 high, we are sending too little data to SSL_write at a time.
15063 Diagnostic for bug 7707.
15064 - Add more detail to a log message about relaxed timeouts, to help
15066 - Warn more aggressively when flushing microdescriptors to a
15067 microdescriptor cache fails, in an attempt to mitigate bug 8031,
15068 or at least make it more diagnosable.
15069 - Improve debugging output to help track down bug 8185 ("Bug:
15070 outgoing relay cell has n_chan==NULL. Dropping.")
15071 - Log the purpose of a path-bias testing circuit correctly.
15072 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
15074 o Minor bugfixes (0.2.4.x log messages that were too noisy):
15075 - Don't attempt to relax the timeout of already opened 1-hop circuits.
15076 They might never timeout. This should eliminate some/all cases of
15077 the relaxed timeout log message.
15078 - Use circuit creation time for network liveness evaluation. This
15079 should eliminate warning log messages about liveness caused
15080 by changes in timeout evaluation. Fixes bug 6572; bugfix on
15082 - Reduce a path bias length check from notice to info. The message
15083 is triggered when creating controller circuits. Fixes bug 8196;
15084 bugfix on 0.2.4.8-alpha.
15085 - Fix a path state issue that triggered a notice during relay startup.
15086 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
15087 - Reduce occurrences of warns about circuit purpose in
15088 connection_ap_expire_building(). Fixes bug 8477; bugfix on
15091 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
15092 - If we encounter a write failure on a SOCKS connection before we
15093 finish our SOCKS handshake, don't warn that we closed the
15094 connection before we could send a SOCKS reply. Fixes bug 8427;
15095 bugfix on 0.1.0.1-rc.
15096 - Correctly recognize that [::1] is a loopback address. Fixes
15097 bug 8377; bugfix on 0.2.1.3-alpha.
15098 - Fix a directory authority warn caused when we have a large amount
15099 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
15100 - Don't log inappropriate heartbeat messages when hibernating: a
15101 hibernating node is _expected_ to drop out of the consensus,
15102 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
15103 bugfix on 0.2.3.1-alpha.
15104 - Don't complain about bootstrapping problems while hibernating.
15105 These complaints reflect a general code problem, but not one
15106 with any problematic effects (no connections are actually
15107 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
15109 o Documentation fixes:
15110 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
15111 names match. Fixes bug 7768.
15112 - Make the torify manpage no longer refer to tsocks; torify hasn't
15113 supported tsocks since 0.2.3.14-alpha.
15114 - Make the tor manpage no longer reference tsocks.
15115 - Fix the GeoIPExcludeUnknown documentation to refer to
15116 ExcludeExitNodes rather than the currently nonexistent
15117 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
15120 - The tor-tsocks.conf is no longer distributed or installed. We
15121 recommend that tsocks users use torsocks instead. Resolves
15125 Changes in version 0.2.4.11-alpha - 2013-03-11
15126 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
15127 more robust, makes hidden service authentication work again, and
15128 resolves a DPI fingerprint for Tor's SSL transport.
15130 o Major features (directory authorities):
15131 - Directory authorities now support a new consensus method (17)
15132 where they cap the published bandwidth of servers for which
15133 insufficient bandwidth measurements exist. Fixes part of bug 2286.
15134 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
15135 serve any v2 directory information. Now we can test disabling the
15136 old deprecated v2 directory format, and see whether doing so has
15137 any effect on network load. Begins to fix bug 6783.
15138 - Directory authorities now include inside each vote a statement of
15139 the performance thresholds they used when assigning flags.
15140 Implements ticket 8151.
15142 o Major bugfixes (directory authorities):
15143 - Stop marking every relay as having been down for one hour every
15144 time we restart a directory authority. These artificial downtimes
15145 were messing with our Stable and Guard flag calculations. Fixes
15146 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
15148 o Major bugfixes (hidden services):
15149 - Allow hidden service authentication to succeed again. When we
15150 refactored the hidden service introduction code back
15151 in 0.2.4.1-alpha, we didn't update the code that checks
15152 whether authentication information is present, causing all
15153 authentication checks to return "false". Fix for bug 8207; bugfix
15154 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
15156 o Minor features (relays, bridges):
15157 - Make bridge relays check once a minute for whether their IP
15158 address has changed, rather than only every 15 minutes. Resolves
15159 bugs 1913 and 1992.
15160 - Refactor resolve_my_address() so it returns the method by which we
15161 decided our public IP address (explicitly configured, resolved from
15162 explicit hostname, guessed from interfaces, learned by gethostname).
15163 Now we can provide more helpful log messages when a relay guesses
15164 its IP address incorrectly (e.g. due to unexpected lines in
15165 /etc/hosts). Resolves ticket 2267.
15166 - Teach bridge-using clients to avoid 0.2.2 bridges when making
15167 microdescriptor-related dir requests, and only fall back to normal
15168 descriptors if none of their bridges can handle microdescriptors
15169 (as opposed to the fix in ticket 4013, which caused them to fall
15170 back to normal descriptors if *any* of their bridges preferred
15171 them). Resolves ticket 4994.
15172 - Randomize the lifetime of our SSL link certificate, so censors can't
15173 use the static value for filtering Tor flows. Resolves ticket 8443;
15174 related to ticket 4014 which was included in 0.2.2.33.
15175 - Support a new version of the link protocol that allows 4-byte circuit
15176 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
15177 a possible resource exhaustion issue. Closes ticket 7351; implements
15180 o Minor features (portability):
15181 - Tweak the curve25519-donna*.c implementations to tolerate systems
15182 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
15183 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
15184 the signs of types during autoconf. This is better than our old
15185 approach, which didn't work when cross-compiling.
15186 - Detect the sign of enum values, rather than assuming that MSC is the
15187 only compiler where enum types are all signed. Fixes bug 7727;
15188 bugfix on 0.2.4.10-alpha.
15190 o Minor features (other):
15191 - Say "KBytes" rather than "KB" in the man page (for various values
15192 of K), to further reduce confusion about whether Tor counts in
15193 units of memory or fractions of units of memory. Resolves ticket 7054.
15194 - Clear the high bit on curve25519 public keys before passing them to
15195 our backend, in case we ever wind up using a backend that doesn't do
15196 so itself. If we used such a backend, and *didn't* clear the high bit,
15197 we could wind up in a situation where users with such backends would
15198 be distinguishable from users without. Fixes bug 8121; bugfix on
15200 - Update to the March 6 2013 Maxmind GeoLite Country database.
15202 o Minor bugfixes (clients):
15203 - When we receive a RELAY_END cell with the reason DONE, or with no
15204 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
15205 status as "connection refused". Previously we reported these cases
15206 as success but then immediately closed the connection. Fixes bug
15207 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
15208 - Downgrade an assertion in connection_ap_expire_beginning to an
15209 LD_BUG message. The fix for bug 8024 should prevent this message
15210 from displaying, but just in case, a warn that we can diagnose
15211 is better than more assert crashes. Fixes bug 8065; bugfix on
15213 - Lower path use bias thresholds to .80 for notice and .60 for warn.
15214 Also make the rate limiting flags for the path use bias log messages
15215 independent from the original path bias flags. Fixes bug 8161;
15216 bugfix on 0.2.4.10-alpha.
15218 o Minor bugfixes (relays):
15219 - Stop trying to resolve our hostname so often (e.g. every time we
15220 think about doing a directory fetch). Now we reuse the cached
15221 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
15222 and 2410 (bugfix on 0.1.2.2-alpha).
15223 - Stop sending a stray "(null)" in some cases for the server status
15224 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
15226 - When choosing which stream on a formerly stalled circuit to wake
15227 first, make better use of the platform's weak RNG. Previously,
15228 we had been using the % ("modulo") operator to try to generate a
15229 1/N chance of picking each stream, but this behaves badly with
15230 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
15232 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
15233 Irix's random() only return 15 bits; Solaris's random() returns more
15234 bits but its RAND_MAX says it only returns 15, and so on. Motivated
15235 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
15237 o Minor bugfixes (directory authorities):
15238 - Directory authorities now use less space when formatting identical
15239 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
15242 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
15243 - Avoid leaking memory if we fail to compute a consensus signature
15244 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
15245 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
15247 - Fix a memory leak during safe-cookie controller authentication.
15248 Bugfix on 0.2.3.13-alpha.
15249 - Avoid memory leak of IPv6 policy content if we fail to format it into
15250 a router descriptor. Bugfix on 0.2.4.7-alpha.
15252 o Minor bugfixes (other code correctness issues):
15253 - Avoid a crash if we fail to generate an extrainfo descriptor.
15254 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
15255 this is CID 718634.
15256 - When detecting the largest possible file descriptor (in order to
15257 close all file descriptors when launching a new program), actually
15258 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
15259 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
15261 - Fix a copy-and-paste error when adding a missing A1 to a routerset
15262 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
15263 Bugfix on 0.2.4.10-alpha.
15264 - Fix an impossible-to-trigger integer overflow when estimating how
15265 long our onionskin queue would take. (This overflow would require us
15266 to accept 4 million onionskins before processing 100 of them.) Fixes
15267 bug 8210; bugfix on 0.2.4.10-alpha.
15269 o Code simplification and refactoring:
15270 - Add a wrapper function for the common "log a message with a
15274 Changes in version 0.2.4.10-alpha - 2013-02-04
15275 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
15276 certain attacks that flood the network with relays; changes the queue
15277 for circuit create requests from a sized-based limit to a time-based
15278 limit; resumes building with MSVC on Windows; and fixes a wide variety
15281 o Major bugfixes (directory authority):
15282 - When computing directory thresholds, ignore any rejected-as-sybil
15283 nodes during the computation so that they can't influence Fast,
15284 Guard, etc. (We should have done this for proposal 109.) Fixes
15286 - When marking a node as a likely sybil, reset its uptime metrics
15287 to zero, so that it cannot time towards getting marked as Guard,
15288 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
15292 - When a TLS write is partially successful but incomplete, remember
15293 that the flushed part has been flushed, and notice that bytes were
15294 actually written. Reported and fixed pseudonymously. Fixes bug
15295 7708; bugfix on Tor 0.1.0.5-rc.
15296 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
15297 ID: these could be used to create unexpected streams and circuits
15298 which would count as "present" to some parts of Tor but "absent"
15299 to others, leading to zombie circuits and streams or to a bandwidth
15300 denial-of-service. Fixes bug 7889; bugfix on every released version
15301 of Tor. Reported by "oftc_must_be_destroyed".
15302 - Rename all macros in our local copy of queue.h to begin with "TOR_".
15303 This change seems the only good way to permanently prevent conflicts
15304 with queue.h on various operating systems. Fixes bug 8107; bugfix
15307 o Major features (relay):
15308 - Instead of limiting the number of queued onionskins (aka circuit
15309 create requests) to a fixed, hard-to-configure number, we limit
15310 the size of the queue based on how many we expect to be able to
15311 process in a given amount of time. We estimate the time it will
15312 take to process an onionskin based on average processing time
15313 of previous onionskins. Closes ticket 7291. You'll never have to
15314 configure MaxOnionsPending again.
15316 o Major features (portability):
15317 - Resume building correctly with MSVC and Makefile.nmake. This patch
15318 resolves numerous bugs and fixes reported by ultramage, including
15319 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
15320 - Make the ntor and curve25519 code build correctly with MSVC.
15321 Fix on 0.2.4.8-alpha.
15324 - When directory authorities are computing thresholds for flags,
15325 never let the threshold for the Fast flag fall below 4096
15326 bytes. Also, do not consider nodes with extremely low bandwidths
15327 when deciding thresholds for various directory flags. This change
15328 should raise our threshold for Fast relays, possibly in turn
15329 improving overall network performance; see ticket 1854. Resolves
15331 - The Tor client now ignores sub-domain components of a .onion
15332 address. This change makes HTTP "virtual" hosting
15333 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
15334 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
15335 hosted on the same hidden service. Implements proposal 204.
15336 - We compute the overhead from passing onionskins back and forth to
15337 cpuworkers, and report it when dumping statistics in response to
15338 SIGUSR1. Supports ticket 7291.
15340 o Minor features (path selection):
15341 - When deciding whether we have enough descriptors to build circuits,
15342 instead of looking at raw relay counts, look at which fraction
15343 of (bandwidth-weighted) paths we're able to build. This approach
15344 keeps clients from building circuits if their paths are likely to
15345 stand out statistically. The default fraction of paths needed is
15346 taken from the consensus directory; you can override it with the
15347 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
15348 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
15349 and we have GeoIP information, also exclude all nodes with unknown
15350 countries "??" and "A1". This behavior is controlled by the
15351 new GeoIPExcludeUnknown option: you can make such nodes always
15352 excluded with "GeoIPExcludeUnknown 1", and disable the feature
15353 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
15354 gets you the default behavior. Implements feature 7706.
15355 - Path Use Bias: Perform separate accounting for successful circuit
15356 use. Keep separate statistics on stream attempt rates versus stream
15357 success rates for each guard. Provide configurable thresholds to
15358 determine when to emit log messages or disable use of guards that
15359 fail too many stream attempts. Resolves ticket 7802.
15361 o Minor features (log messages):
15362 - When learning a fingerprint for a bridge, log its corresponding
15363 transport type. Implements ticket 7896.
15364 - Improve the log message when "Bug/attack: unexpected sendme cell
15365 from client" occurs, to help us track bug 8093.
15368 - Remove a couple of extraneous semicolons that were upsetting the
15369 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
15370 bugfix on 0.2.2.1-alpha.
15371 - Remove a source of rounding error during path bias count scaling;
15372 don't count cannibalized circuits as used for path bias until we
15373 actually try to use them; and fix a circuit_package_relay_cell()
15374 warning message about n_chan==NULL. Fixes bug 7802.
15375 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
15376 actually link against nacl when we're configured to use it. Fixes
15377 bug 7972; bugfix on 0.2.4.8-alpha.
15378 - Compile correctly with the --disable-curve25519 option. Fixes
15379 bug 8153; bugfix on 0.2.4.8-alpha.
15381 o Build improvements:
15382 - Do not report status verbosely from autogen.sh unless the -v flag
15383 is specified. Fixes issue 4664. Patch from Onizuka.
15384 - Replace all calls to snprintf() outside of src/ext with
15385 tor_snprintf(). Also remove the #define to replace snprintf with
15386 _snprintf on Windows; they have different semantics, and all of
15387 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
15388 - Try to detect if we are ever building on a platform where
15389 memset(...,0,...) does not set the value of a double to 0.0. Such
15390 platforms are permitted by the C standard, though in practice
15391 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
15392 currently support them, but it's better to detect them and fail
15393 than to perform erroneously.
15395 o Removed features:
15396 - Stop exporting estimates of v2 and v3 directory traffic shares
15397 in extrainfo documents. They were unneeded and sometimes inaccurate.
15398 Also stop exporting any v2 directory request statistics. Resolves
15400 - Drop support for detecting and warning about versions of Libevent
15401 before 1.3e. Nothing reasonable ships with them any longer;
15402 warning the user about them shouldn't be needed. Resolves ticket
15405 o Code simplifications and refactoring:
15406 - Rename "isin" functions to "contains", for grammar. Resolves
15408 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
15409 with the natural logarithm function from the system libm. Resolves
15413 Changes in version 0.2.4.9-alpha - 2013-01-15
15414 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
15415 work more robustly.
15418 - Fix backward compatibility logic when receiving an embedded ntor
15419 handshake tunneled in a CREATE cell. This clears up the "Bug:
15420 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
15424 Changes in version 0.2.4.8-alpha - 2013-01-14
15425 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
15426 risks, adds a new stronger and faster circuit handshake, and offers
15427 stronger and faster link encryption when both sides support it.
15430 - Preliminary support for directory guards (proposal 207): when
15431 possible, clients now use their entry guards for non-anonymous
15432 directory requests. This can help prevent client enumeration. Note
15433 that this behavior only works when we have a usable consensus
15434 directory, and when options about what to download are more or less
15435 standard. In the future we should re-bootstrap from our guards,
15436 rather than re-bootstrapping from the preconfigured list of
15437 directory sources that ships with Tor. Resolves ticket 6526.
15438 - Tor relays and clients now support a better CREATE/EXTEND cell
15439 format, allowing the sender to specify multiple address, identity,
15440 and handshake types. Implements Robert Ransom's proposal 200;
15441 closes ticket 7199.
15443 o Major features (new circuit handshake):
15444 - Tor now supports a new circuit extension handshake designed by Ian
15445 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
15446 circuit extension handshake, later called "TAP", was a bit slow
15447 (especially on the relay side), had a fragile security proof, and
15448 used weaker keys than we'd now prefer. The new circuit handshake
15449 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
15450 function, making it significantly more secure than the older
15451 handshake, and significantly faster. Tor can use one of two built-in
15452 pure-C curve25519-donna implementations by Adam Langley, or it
15453 can link against the "nacl" library for a tuned version if present.
15455 The built-in version is very fast for 64-bit systems when building
15456 with GCC. The built-in 32-bit version is still faster than the
15457 old TAP protocol, but using libnacl is better on most such hosts.
15459 Clients don't currently use this protocol by default, since
15460 comparatively few clients support it so far. To try it, set
15461 UseNTorHandshake to 1.
15463 Implements proposal 216; closes ticket 7202.
15465 o Major features (better link encryption):
15466 - Relays can now enable the ECDHE TLS ciphersuites when available
15467 and appropriate. These ciphersuites let us negotiate forward-secure
15468 TLS secret keys more safely and more efficiently than with our
15469 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
15470 public relays prefer the (faster) P224 group, and bridges prefer
15471 the (more common) P256 group; you can override this with the
15474 Enabling these ciphers was a little tricky, since for a long time,
15475 clients had been claiming to support them without actually doing
15476 so, in order to foil fingerprinting. But with the client-side
15477 implementation of proposal 198 in 0.2.3.17-beta, clients can now
15478 match the ciphers from recent Firefox versions *and* list the
15479 ciphers they actually mean, so relays can believe such clients
15480 when they advertise ECDHE support in their TLS ClientHello messages.
15482 This feature requires clients running 0.2.3.17-beta or later,
15483 and requires both sides to be running OpenSSL 1.0.0 or later
15484 with ECC support. OpenSSL 1.0.1, with the compile-time option
15485 "enable-ec_nistp_64_gcc_128", is highly recommended.
15487 Implements the relay side of proposal 198; closes ticket 7200.
15490 - Avoid crashing when, as a relay without IPv6-exit support, a
15491 client insists on getting an IPv6 address or nothing. Fixes bug
15492 7814; bugfix on 0.2.4.7-alpha.
15495 - Improve circuit build timeout handling for hidden services.
15496 In particular: adjust build timeouts more accurately depending
15497 upon the number of hop-RTTs that a particular circuit type
15498 undergoes. Additionally, launch intro circuits in parallel
15499 if they timeout, and take the first one to reply as valid.
15500 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
15501 separate error codes; or at least, don't break for that reason.
15502 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
15503 - Update to the January 2 2013 Maxmind GeoLite Country database.
15505 o Minor features (testing):
15506 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
15507 (P-256) Diffie-Hellman handshakes to src/or/bench.
15508 - Add benchmark functions to test onion handshake performance.
15510 o Minor features (path bias detection):
15511 - Alter the Path Bias log messages to be more descriptive in terms
15512 of reporting timeouts and other statistics.
15513 - Create three levels of Path Bias log messages, as opposed to just
15514 two. These are configurable via consensus as well as via the torrc
15515 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
15516 The default values are 0.70, 0.50, and 0.30 respectively.
15517 - Separate the log message levels from the decision to drop guards,
15518 which also is available via torrc option PathBiasDropGuards.
15519 PathBiasDropGuards still defaults to 0 (off).
15520 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
15521 in combination with PathBiasExtremeRate.
15522 - Increase the default values for PathBiasScaleThreshold and
15523 PathBiasCircThreshold from (200, 20) to (300, 150).
15524 - Add in circuit usage accounting to path bias. If we try to use a
15525 built circuit but fail for any reason, it counts as path bias.
15526 Certain classes of circuits where the adversary gets to pick your
15527 destination node are exempt from this accounting. Usage accounting
15528 can be specifically disabled via consensus parameter or torrc.
15529 - Convert all internal path bias state to double-precision floating
15530 point, to avoid roundoff error and other issues.
15531 - Only record path bias information for circuits that have completed
15532 *two* hops. Assuming end-to-end tagging is the attack vector, this
15533 makes us more resilient to ambient circuit failure without any
15534 detection capability loss.
15536 o Minor bugfixes (log messages):
15537 - Rate-limit the "No circuits are opened. Relaxed timeout for a
15538 circuit with channel state open..." message to once per hour to
15539 keep it from filling the notice logs. Mitigates bug 7799 but does
15540 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
15541 - Avoid spurious warnings when configuring multiple client ports of
15542 which only some are nonlocal. Previously, we had claimed that some
15543 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
15546 o Code simplifications and refactoring:
15547 - Get rid of a couple of harmless clang warnings, where we compared
15548 enums to ints. These warnings are newly introduced in clang 3.2.
15549 - Split the onion.c file into separate modules for the onion queue
15550 and the different handshakes it supports.
15551 - Remove the marshalling/unmarshalling code for sending requests to
15552 cpuworkers over a socket, and instead just send structs. The
15553 recipient will always be the same Tor binary as the sender, so
15554 any encoding is overkill.
15557 Changes in version 0.2.4.7-alpha - 2012-12-24
15558 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
15559 directory mirrors for more robust bootstrapping; fixes more issues where
15560 clients with changing network conditions refuse to make any circuits;
15561 adds initial support for exiting to IPv6 addresses; resumes being able
15562 to update our GeoIP database, and includes the geoip6 file this time;
15563 turns off the client-side DNS cache by default due to privacy risks;
15564 and fixes a variety of other issues.
15566 o Major features (client resilience):
15567 - Add a new "FallbackDir" torrc option to use when we can't use
15568 a directory mirror from the consensus (either because we lack a
15569 consensus, or because they're all down). Currently, all authorities
15570 are fallbacks by default, and there are no other default fallbacks,
15571 but that will change. This option will allow us to give clients a
15572 longer list of servers to try to get a consensus from when first
15573 connecting to the Tor network, and thereby reduce load on the
15574 directory authorities. Implements proposal 206, "Preconfigured
15575 directory sources for bootstrapping". We also removed the old
15576 "FallbackNetworkstatus" option, since we never got it working well
15577 enough to use it. Closes bug 572.
15578 - If we have no circuits open, use a relaxed timeout (the
15579 95-percentile cutoff) until a circuit succeeds. This heuristic
15580 should allow Tor to succeed at building circuits even when the
15581 network connection drastically changes. Should help with bug 3443.
15583 o Major features (IPv6):
15584 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
15585 connectivity, then set the IPv6Exit flag to 1. Also make sure your
15586 exit policy reads as you would like: the address * applies to all
15587 address families, whereas *4 is IPv4 address only, and *6 is IPv6
15588 addresses only. On the client side, you'll need to wait until the
15589 authorities have upgraded, wait for enough exits to support IPv6,
15590 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
15591 ticket 5547, implements proposal 117 as revised in proposal 208.
15593 We DO NOT recommend that clients with actual anonymity needs start
15594 using IPv6 over Tor yet, since not enough exits support it yet.
15596 o Major features (geoip database):
15597 - Maxmind began labelling Tor relays as being in country "A1",
15598 which breaks by-country node selection inside Tor. Now we use a
15599 script to replace "A1" ("Anonymous Proxy") entries in our geoip
15600 file with real country codes. This script fixes about 90% of "A1"
15601 entries automatically and uses manual country code assignments to
15602 fix the remaining 10%. See src/config/README.geoip for details.
15603 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
15604 Country database, as modified above.
15606 o Major bugfixes (client-side DNS):
15607 - Turn off the client-side DNS cache by default. Updating and using
15608 the DNS cache is now configurable on a per-client-port
15609 level. SOCKSPort, DNSPort, etc lines may now contain
15610 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
15611 cache these types of DNS answers when we receive them from an
15612 exit node in response to an application request on this port, and
15613 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
15614 cached DNS answers of these types, we shouldn't use them. It's
15615 potentially risky to use cached DNS answers at the client, since
15616 doing so can indicate to one exit what answers we've gotten
15617 for DNS lookups in the past. With IPv6, this becomes especially
15618 problematic. Using cached DNS answers for requests on the same
15619 circuit would present less linkability risk, since all traffic
15620 on a circuit is already linkable, but it would also provide
15621 little performance benefit: the exit node caches DNS replies
15622 too. Implements a simplified version of Proposal 205. Implements
15625 o Major bugfixes (other):
15626 - Alter circuit build timeout measurement to start at the point
15627 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
15628 initialization). This should make our timeout measurements more
15629 uniform. Previously, we were sometimes including ORconn setup time
15630 in our circuit build time measurements. Should resolve bug 3443.
15631 - Fix an assertion that could trigger in hibernate_go_dormant() when
15632 closing an or_connection_t: call channel_mark_for_close() rather
15633 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
15635 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
15636 7655; bugfix on 0.2.4.6-alpha.
15639 - Add a new torrc option "ServerTransportListenAddr" to let bridge
15640 operators select the address where their pluggable transports will
15641 listen for connections. Resolves ticket 7013.
15642 - Allow an optional $ before the node identity digest in the
15643 controller command GETINFO ns/id/<identity>, for consistency with
15644 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
15645 - Log packaged cell fullness as part of the heartbeat message.
15646 Diagnosis to try to determine the extent of bug 7743.
15648 o Minor features (IPv6):
15649 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
15650 prefer to hand out virtual IPv6 addresses, since there are more of
15651 them and we can't run out. To override this behavior and make IPv4
15652 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
15653 or DNSPort you're using for resolving. Implements ticket 7571.
15654 - AutomapHostsOnResolve responses are now randomized, to avoid
15655 annoying situations where Tor is restarted and applications
15656 connect to the wrong addresses.
15657 - Never try more than 1000 times to pick a new virtual address when
15658 AutomapHostsOnResolve is set. That's good enough so long as we
15659 aren't close to handing out our entire virtual address space;
15660 if you're getting there, it's best to switch to IPv6 virtual
15664 - The ADDRMAP command can no longer generate an ill-formed error
15665 code on a failed MAPADDRESS. It now says "internal" rather than
15666 an English sentence fragment with spaces in the middle. Bugfix on
15667 Tor 0.2.0.19-alpha.
15668 - Fix log messages and comments to avoid saying "GMT" when we mean
15669 "UTC". Fixes bug 6113.
15670 - Compile on win64 using mingw64. Fixes bug 7260; patches from
15672 - Fix a crash when debugging unit tests on Windows: deallocate a
15673 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
15674 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
15677 - The DirServer option is now DirAuthority, for consistency with
15678 current naming patterns. You can still use the old DirServer form.
15680 o Code simplification and refactoring:
15681 - Move the client-side address-map/virtual-address/DNS-cache code
15682 out of connection_edge.c into a new addressmap.c module.
15683 - Remove unused code for parsing v1 directories and "running routers"
15684 documents. Fixes bug 6887.
15687 Changes in version 0.2.3.25 - 2012-11-19
15688 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
15689 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
15690 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
15691 programmer, and friend. Unstinting in his dedication to the cause of
15692 freedom, he inspired and helped many of us as we began our work on
15693 anonymity, and inspires us still. Please honor his memory by writing
15694 software to protect people's freedoms, and by helping others to do so.
15696 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
15697 significantly reduced directory overhead (via microdescriptors),
15698 enormous crypto performance improvements for fast relays on new
15699 enough hardware, a new v3 TLS handshake protocol that can better
15700 resist fingerprinting, support for protocol obfuscation plugins (aka
15701 pluggable transports), better scalability for hidden services, IPv6
15702 support for bridges, performance improvements like allowing clients
15703 to skip the first round-trip on the circuit ("optimistic data") and
15704 refilling token buckets more often, a new "stream isolation" design
15705 to isolate different applications on different circuits, and many
15706 stability, security, and privacy fixes.
15709 - Tor tries to wipe potentially sensitive data after using it, so
15710 that if some subsequent security failure exposes Tor's memory,
15711 the damage will be limited. But we had a bug where the compiler
15712 was eliminating these wipe operations when it decided that the
15713 memory was no longer visible to a (correctly running) program,
15714 hence defeating our attempt at defense in depth. We fix that
15715 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
15716 is unlikely to optimize away. Future versions of Tor may use
15717 a less ridiculously heavy approach for this. Fixes bug 7352.
15718 Reported in an article by Andrey Karpov.
15721 - Fix a harmless bug when opting against publishing a relay descriptor
15722 because DisableNetwork is set. Fixes bug 7464; bugfix on
15726 Changes in version 0.2.4.6-alpha - 2012-11-13
15727 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
15728 makes our defense-in-depth memory wiping more reliable, and begins to
15729 count IPv6 addresses in bridge statistics,
15732 - Fix an assertion failure that could occur when closing a connection
15733 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
15735 - Tor tries to wipe potentially sensitive data after using it, so
15736 that if some subsequent security failure exposes Tor's memory,
15737 the damage will be limited. But we had a bug where the compiler
15738 was eliminating these wipe operations when it decided that the
15739 memory was no longer visible to a (correctly running) program,
15740 hence defeating our attempt at defense in depth. We fix that
15741 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
15742 is unlikely to optimize away. Future versions of Tor may use
15743 a less ridiculously heavy approach for this. Fixes bug 7352.
15744 Reported in an article by Andrey Karpov.
15747 - Add GeoIP database for IPv6 addresses. The new config option
15749 - Bridge statistics now count bridge clients connecting over IPv6:
15750 bridge statistics files now list "bridge-ip-versions" and
15751 extra-info documents list "geoip6-db-digest". The control protocol
15752 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
15753 implementation by "shkoo", addressing ticket 5055.
15756 - Warn when we are binding low ports when hibernation is enabled;
15757 previously we had warned when we were _advertising_ low ports with
15758 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
15759 - Fix a harmless bug when opting against publishing a relay descriptor
15760 because DisableNetwork is set. Fixes bug 7464; bugfix on
15762 - Add warning message when a managed proxy dies during configuration.
15763 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
15764 - Fix a linking error when building tor-fw-helper without miniupnp.
15765 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
15766 - Check for closing an or_connection_t without going through correct
15767 channel functions; emit a warning and then call
15768 connection_or_close_for_error() so we don't assert as in bugs 7212
15770 - Compile correctly on compilers without C99 designated initializer
15771 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
15772 - Avoid a possible assert that can occur when channel_send_destroy() is
15773 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
15774 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
15775 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
15776 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
15777 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
15779 o Code simplification and refactoring:
15780 - Start using OpenBSD's implementation of queue.h, so that we don't
15781 need to hand-roll our own pointer and list structures whenever we
15782 need them. (We can't rely on a sys/queue.h, since some operating
15783 systems don't have them, and the ones that do have them don't all
15784 present the same extensions.)
15787 Changes in version 0.2.4.5-alpha - 2012-10-25
15788 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
15789 two important security vulnerabilities that could lead to remotely
15790 triggerable relay crashes, fix a major bug that was preventing clients
15791 from choosing suitable exit nodes, and refactor some of our code.
15793 o Major bugfixes (security, also in 0.2.3.24-rc):
15794 - Fix a group of remotely triggerable assertion failures related to
15795 incorrect link protocol negotiation. Found, diagnosed, and fixed
15796 by "some guy from France". Fix for CVE-2012-2250; bugfix on
15798 - Fix a denial of service attack by which any directory authority
15799 could crash all the others, or by which a single v2 directory
15800 authority could crash everybody downloading v2 directory
15801 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
15803 o Major bugfixes (also in 0.2.3.24-rc):
15804 - When parsing exit policy summaries from microdescriptors, we had
15805 previously been ignoring the last character in each one, so that
15806 "accept 80,443,8080" would be treated by clients as indicating
15807 a node that allows access to ports 80, 443, and 808. That would
15808 lead to clients attempting connections that could never work,
15809 and ignoring exit nodes that would support their connections. Now
15810 clients parse these exit policy summaries correctly. Fixes bug 7192;
15811 bugfix on 0.2.3.1-alpha.
15813 o Minor bugfixes (also in 0.2.3.24-rc):
15814 - Clients now consider the ClientRejectInternalAddresses config option
15815 when using a microdescriptor consensus stanza to decide whether
15816 an exit relay would allow exiting to an internal address. Fixes
15817 bug 7190; bugfix on 0.2.3.1-alpha.
15820 - Only disable TLS session ticket support when running as a TLS
15821 server. Now clients will blend better with regular Firefox
15822 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
15824 o Code simplification and refactoring:
15825 - Start using OpenBSD's implementation of queue.h (originally by
15827 - Move the entry node code from circuitbuild.c to its own file.
15828 - Move the circuit build timeout tracking code from circuitbuild.c
15832 Changes in version 0.2.3.24-rc - 2012-10-25
15833 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
15834 could lead to remotely triggerable relay crashes, and fixes
15835 a major bug that was preventing clients from choosing suitable exit
15838 o Major bugfixes (security):
15839 - Fix a group of remotely triggerable assertion failures related to
15840 incorrect link protocol negotiation. Found, diagnosed, and fixed
15841 by "some guy from France". Fix for CVE-2012-2250; bugfix on
15843 - Fix a denial of service attack by which any directory authority
15844 could crash all the others, or by which a single v2 directory
15845 authority could crash everybody downloading v2 directory
15846 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
15849 - When parsing exit policy summaries from microdescriptors, we had
15850 previously been ignoring the last character in each one, so that
15851 "accept 80,443,8080" would be treated by clients as indicating
15852 a node that allows access to ports 80, 443, and 808. That would
15853 lead to clients attempting connections that could never work,
15854 and ignoring exit nodes that would support their connections. Now
15855 clients parse these exit policy summaries correctly. Fixes bug 7192;
15856 bugfix on 0.2.3.1-alpha.
15859 - Clients now consider the ClientRejectInternalAddresses config option
15860 when using a microdescriptor consensus stanza to decide whether
15861 an exit relay would allow exiting to an internal address. Fixes
15862 bug 7190; bugfix on 0.2.3.1-alpha.
15865 Changes in version 0.2.4.4-alpha - 2012-10-20
15866 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
15867 vulnerability introduced by a change in OpenSSL, fixes a remotely
15868 triggerable assert, and adds new channel_t and circuitmux_t abstractions
15869 that will make it easier to test new connection transport and cell
15870 scheduling algorithms.
15872 o New directory authorities (also in 0.2.3.23-rc):
15873 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
15874 authority. Closes ticket 5749.
15876 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
15877 - Disable TLS session tickets. OpenSSL's implementation was giving
15878 our TLS session keys the lifetime of our TLS context objects, when
15879 perfect forward secrecy would want us to discard anything that
15880 could decrypt a link connection as soon as the link connection
15881 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
15882 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
15883 - Discard extraneous renegotiation attempts once the V3 link
15884 protocol has been initiated. Failure to do so left us open to
15885 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
15886 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
15888 o Internal abstraction features:
15889 - Introduce new channel_t abstraction between circuits and
15890 or_connection_t to allow for implementing alternate OR-to-OR
15891 transports. A channel_t is an abstract object which can either be a
15892 cell-bearing channel, which is responsible for authenticating and
15893 handshaking with the remote OR and transmitting cells to and from
15894 it, or a listening channel, which spawns new cell-bearing channels
15895 at the request of remote ORs. Implements part of ticket 6465.
15896 - Also new is the channel_tls_t subclass of channel_t, adapting it
15897 to the existing or_connection_t code. The V2/V3 protocol handshaking
15898 code which formerly resided in command.c has been moved below the
15899 channel_t abstraction layer and may be found in channeltls.c now.
15900 Implements the rest of ticket 6465.
15901 - Introduce new circuitmux_t storing the queue of circuits for
15902 a channel; this encapsulates and abstracts the queue logic and
15903 circuit selection policy, and allows the latter to be overridden
15904 easily by switching out a policy object. The existing EWMA behavior
15905 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
15907 o Required libraries:
15908 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
15909 strongly recommended.
15912 - Warn users who run hidden services on a Tor client with
15913 UseEntryGuards disabled that their hidden services will be
15914 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
15915 attack which motivated Tor to support entry guards in the first
15916 place). Resolves ticket 6889.
15917 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
15918 dhill. Resolves ticket 6982.
15919 - Option OutboundBindAddress can be specified multiple times and
15920 accepts IPv6 addresses. Resolves ticket 6876.
15922 o Minor bugfixes (also in 0.2.3.23-rc):
15923 - Don't serve or accept v2 hidden service descriptors over a
15924 relay's DirPort. It's never correct to do so, and disabling it
15925 might make it more annoying to exploit any bugs that turn up in the
15926 descriptor-parsing code. Fixes bug 7149.
15927 - Fix two cases in src/or/transports.c where we were calling
15928 fmt_addr() twice in a parameter list. Bug found by David
15929 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
15930 - Fix memory leaks whenever we logged any message about the "path
15931 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
15932 - When relays refuse a "create" cell because their queue of pending
15933 create cells is too big (typically because their cpu can't keep up
15934 with the arrival rate), send back reason "resource limit" rather
15935 than reason "internal", so network measurement scripts can get a
15936 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
15939 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
15940 - Free some more still-in-use memory at exit, to make hunting for
15941 memory leaks easier. Resolves bug 7029.
15942 - When a Tor client gets a "truncated" relay cell, the first byte of
15943 its payload specifies why the circuit was truncated. We were
15944 ignoring this 'reason' byte when tearing down the circuit, resulting
15945 in the controller not being told why the circuit closed. Now we
15946 pass the reason from the truncated cell to the controller. Bugfix
15947 on 0.1.2.3-alpha; fixes bug 7039.
15948 - Downgrade "Failed to hand off onionskin" messages to "debug"
15949 severity, since they're typically redundant with the "Your computer
15950 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
15951 - Make clients running with IPv6 bridges connect over IPv6 again,
15952 even without setting new config options ClientUseIPv6 and
15953 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
15954 - Use square brackets around IPv6 addresses in numerous places
15955 that needed them, including log messages, HTTPS CONNECT proxy
15956 requests, TransportProxy statefile entries, and pluggable transport
15957 extra-info lines. Fixes bug 7011; patch by David Fifield.
15959 o Code refactoring and cleanup:
15960 - Source files taken from other packages now reside in src/ext;
15961 previously they were scattered around the rest of Tor.
15962 - Avoid use of reserved identifiers in our C code. The C standard
15963 doesn't like us declaring anything that starts with an
15964 underscore, so let's knock it off before we get in trouble. Fix
15965 for bug 1031; bugfix on the first Tor commit.
15968 Changes in version 0.2.3.23-rc - 2012-10-20
15969 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
15970 vulnerability introduced by a change in OpenSSL, and fixes a variety
15971 of smaller bugs in preparation for the release.
15973 o New directory authorities:
15974 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
15975 authority. Closes ticket 5749.
15977 o Major bugfixes (security/privacy):
15978 - Disable TLS session tickets. OpenSSL's implementation was giving
15979 our TLS session keys the lifetime of our TLS context objects, when
15980 perfect forward secrecy would want us to discard anything that
15981 could decrypt a link connection as soon as the link connection
15982 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
15983 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
15984 - Discard extraneous renegotiation attempts once the V3 link
15985 protocol has been initiated. Failure to do so left us open to
15986 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
15987 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
15990 - Fix a possible crash bug when checking for deactivated circuits
15991 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
15992 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
15994 o Minor bugfixes (on 0.2.3.x):
15995 - Fix two cases in src/or/transports.c where we were calling
15996 fmt_addr() twice in a parameter list. Bug found by David
15997 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
15998 - Convert an assert in the pathbias code to a log message. The assert
15999 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
16000 bugfix on 0.2.3.17-beta.
16001 - Fix memory leaks whenever we logged any message about the "path
16002 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
16004 o Minor bugfixes (on 0.2.2.x and earlier):
16005 - Don't serve or accept v2 hidden service descriptors over a relay's
16006 DirPort. It's never correct to do so, and disabling it might
16007 make it more annoying to exploit any bugs that turn up in the
16008 descriptor-parsing code. Fixes bug 7149.
16009 - When relays refuse a "create" cell because their queue of pending
16010 create cells is too big (typically because their cpu can't keep up
16011 with the arrival rate), send back reason "resource limit" rather
16012 than reason "internal", so network measurement scripts can get a
16013 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
16014 - Correct file sizes when reading binary files on Cygwin, to avoid
16015 a bug where Tor would fail to read its state file. Fixes bug 6844;
16016 bugfix on 0.1.2.7-alpha.
16017 - Avoid undefined behavior when parsing the list of supported
16018 rendezvous/introduction protocols in a hidden service descriptor.
16019 Previously, Tor would have confused (as-yet-unused) protocol version
16020 numbers greater than 32 with lower ones on many platforms. Fixes
16021 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
16023 o Documentation fixes:
16024 - Clarify that hidden services are TCP only. Fixes bug 6024.
16027 Changes in version 0.2.4.3-alpha - 2012-09-22
16028 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
16029 assertion, resumes letting relays test reachability of their DirPort,
16030 and cleans up a bunch of smaller bugs.
16033 - Fix an assertion failure in tor_timegm() that could be triggered
16034 by a badly formatted directory object. Bug found by fuzzing with
16035 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
16038 - Fix a possible crash bug when checking for deactivated circuits
16039 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
16040 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
16041 - Allow routers to detect that their own DirPorts are running. When
16042 we removed support for versions_supports_begindir, we also
16043 accidentally removed the mechanism we used to self-test our
16044 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
16045 bugfix on 0.2.4.2-alpha.
16047 o Security features:
16048 - Switch to a completely time-invariant approach for picking nodes
16049 weighted by bandwidth. Our old approach would run through the
16050 part of the loop after it had made its choice slightly slower
16051 than it ran through the part of the loop before it had made its
16052 choice. Addresses ticket 6538.
16053 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
16054 by tor2web clients allows hidden services to identify tor2web
16055 clients through their repeated selection of the same rendezvous
16056 and introduction point circuit endpoints (their guards). Resolves
16060 - Enable Tor to read configuration, state, and key information from
16061 a FIFO. Previously Tor would only read from files with a positive
16062 stat.st_size. Code from meejah; fixes bug 6044.
16065 - Correct file sizes when reading binary files on Cygwin, to avoid
16066 a bug where Tor would fail to read its state file. Fixes bug 6844;
16067 bugfix on 0.1.2.7-alpha.
16068 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
16069 bugfix on 0.2.0.3-alpha.
16070 - When complaining about a client port on a public address, log
16071 which address we're complaining about. Fixes bug 4020; bugfix on
16072 0.2.3.3-alpha. Patch by Tom Fitzhenry.
16073 - Convert an assert in the pathbias code to a log message. The assert
16074 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
16075 bugfix on 0.2.3.17-beta.
16076 - Our new buildsystem was overzealous about rebuilding manpages: it
16077 would rebuild them all whenever any one of them changed. Now our
16078 dependency checking should be correct. Fixes bug 6843; bugfix on
16080 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
16081 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
16082 - Correct log printout about which address family is preferred
16083 when connecting to a bridge with both an IPv4 and IPv6 OR port.
16084 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
16086 o Minor bugfixes (code cleanliness):
16087 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
16088 with large values. This situation was untriggered, but nevertheless
16089 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
16090 - Reject consensus votes with more than 64 known-flags. We aren't even
16091 close to that limit yet, and our code doesn't handle it correctly.
16092 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
16093 - Avoid undefined behavior when parsing the list of supported
16094 rendezvous/introduction protocols in a hidden service descriptor.
16095 Previously, Tor would have confused (as-yet-unused) protocol version
16096 numbers greater than 32 with lower ones on many platforms. Fixes
16097 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
16098 - Fix handling of rendezvous client authorization types over 8.
16099 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
16100 - Fix building with older versions of GCC (2.95, for one) that don't
16101 like preprocessor directives inside macro arguments. Found by
16102 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
16103 - Switch weighted node selection rule from using a list of doubles
16104 to using a list of int64_t. This change should make the process
16105 slightly easier to debug and maintain. Needed to finish ticket 6538.
16107 o Code simplification and refactoring:
16108 - Move the generic "config" code into a new file, and have "config.c"
16109 hold only torrc- and state-related code. Resolves ticket 6823.
16110 - Move the core of our "choose a weighted element at random" logic
16111 into its own function, and give it unit tests. Now the logic is
16112 testable, and a little less fragile too.
16113 - Removed the testing_since field of node_t, which hasn't been used
16114 for anything since 0.2.0.9-alpha.
16116 o Documentation fixes:
16117 - Clarify that hidden services are TCP only. Fixes bug 6024.
16118 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
16122 Changes in version 0.2.3.22-rc - 2012-09-11
16123 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
16127 - Fix an assertion failure in tor_timegm() that could be triggered
16128 by a badly formatted directory object. Bug found by fuzzing with
16129 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
16132 - Avoid segfault when starting up having run with an extremely old
16133 version of Tor and parsing its state file. Fixes bug 6801; bugfix
16137 Changes in version 0.2.2.39 - 2012-09-11
16138 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
16142 - Fix an assertion failure in tor_timegm() that could be triggered
16143 by a badly formatted directory object. Bug found by fuzzing with
16144 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
16145 - Do not crash when comparing an address with port value 0 to an
16146 address policy. This bug could have been used to cause a remote
16147 assertion failure by or against directory authorities, or to
16148 allow some applications to crash clients. Fixes bug 6690; bugfix
16152 Changes in version 0.2.4.2-alpha - 2012-09-10
16153 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
16154 raises the default rate limiting even more, and makes the bootstrapping
16155 log messages less noisy.
16158 - Automatically forward the TCP ports of pluggable transport
16159 proxies using tor-fw-helper if PortForwarding is enabled. Implements
16163 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
16164 to 1GB/1GB. The previous defaults were intended to be "basically
16165 infinite", but it turns out they're now limiting our 100mbit+
16166 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
16167 last time we raised it).
16170 - Detect when we're running with a version of OpenSSL other than the
16171 one we compiled with. This has occasionally given people hard-to-
16173 - Log fewer lines at level "notice" about our OpenSSL and Libevent
16174 versions and capabilities when everything is going right. Resolves
16175 part of ticket 6736.
16176 - Directory authorities no long accept descriptors for any version of
16177 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
16178 These versions are insecure, unsupported, or both. Implements
16182 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
16183 to start with a triple-underscore so the controller won't touch it.
16184 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
16185 - Avoid segfault when starting up having run with an extremely old
16186 version of Tor and parsing its state file. Fixes bug 6801; bugfix
16188 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
16189 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
16190 - Don't follow the NULL pointer if microdescriptor generation fails.
16191 (This does not appear to be triggerable, but it's best to be safe.)
16192 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
16193 - Fix mis-declared dependencies on src/common/crypto.c and
16194 src/or/tor_main.c that could break out-of-tree builds under some
16195 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
16196 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
16197 6778; bugfix on 0.2.4.1-alpha.
16198 - Fix a harmless (in this case) build warning for implicitly
16199 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
16201 o Removed features:
16202 - Now that all versions before 0.2.2.x are disallowed, we no longer
16203 need to work around their missing features. Thus we can remove a
16204 bunch of compatibility code.
16206 o Code refactoring:
16207 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
16208 TCP ports to forward. In the past it only accepted two ports:
16209 the ORPort and the DirPort.
16212 Changes in version 0.2.4.1-alpha - 2012-09-05
16213 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
16214 bridgedb; lets relays use IPv6 addresses and directory authorities
16215 advertise them; and switches to a cleaner build interface.
16217 This is the first alpha release in a new series, so expect there to
16218 be bugs. Users who would rather test out a more stable branch should
16219 stay with 0.2.3.x for now.
16221 o Major features (bridges):
16222 - Bridges now report the pluggable transports they support to the
16223 bridge authority, so it can pass the supported transports on to
16224 bridgedb and/or eventually do reachability testing. Implements
16227 o Major features (IPv6):
16228 - Bridge authorities now accept IPv6 bridge addresses and include
16229 them in network status documents. Implements ticket 5534.
16230 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
16231 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
16232 to happen. Implements ticket 5535.
16233 - All kind of relays, not just bridges, can now advertise an IPv6
16234 OR port. Implements ticket 6362.
16235 - Directory authorities vote on IPv6 OR ports using the new consensus
16236 method 14. Implements ticket 6363.
16238 o Major features (build):
16239 - Switch to a nonrecursive Makefile structure. Now instead of each
16240 Makefile.am invoking other Makefile.am's, there is a master
16241 Makefile.am that includes the others. This change makes our build
16242 process slightly more maintainable, and improves parallelism for
16243 building with make -j. Original patch by Stewart Smith; various
16244 fixes by Jim Meyering.
16245 - Where available, we now use automake's "silent" make rules by
16246 default, so that warnings are easier to spot. You can get the old
16247 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
16249 o Minor features (code security and spec conformance):
16250 - Clear keys and key-derived material left on the stack in
16251 rendservice.c and rendclient.c. Check return value of
16252 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
16253 These fixes should make us more forward-secure against cold-boot
16254 attacks and the like. Fixes bug 2385.
16255 - Reject EXTEND cells sent to nonexistent streams. According to the
16256 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
16257 we were only checking for stream IDs that were currently in use.
16258 Found while hunting for more instances of bug 6271. Bugfix on
16259 0.0.2pre8, which introduced incremental circuit construction.
16261 o Minor features (streamlining);
16262 - No longer include the "opt" prefix when generating routerinfos
16263 or v2 directories: it has been needless since Tor 0.1.2. Closes
16265 - Remove some now-needless code that tried to aggressively flush
16266 OR connections as data was added to them. Since 0.2.0.1-alpha, our
16267 cell queue logic has saved us from the failure mode that this code
16268 was supposed to prevent. Removing this code will limit the number
16269 of baroque control flow paths through Tor's network logic. Reported
16270 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
16272 o Minor features (controller):
16273 - Add a "GETINFO signal/names" control port command. Implements
16275 - Provide default values for all options via "GETINFO config/defaults".
16276 Implements ticket 4971.
16278 o Minor features (IPv6):
16279 - New config option "AuthDirHasIPv6Connectivity 1" that directory
16280 authorities should set if they have IPv6 connectivity and want to
16281 do reachability tests for IPv6 relays. Implements feature 5974.
16282 - A relay with an IPv6 OR port now sends that address in NETINFO
16283 cells (in addition to its other address). Implements ticket 6364.
16285 o Minor features (log messages):
16286 - Omit the first heartbeat log message, because it never has anything
16287 useful to say, and it clutters up the bootstrapping messages.
16288 Resolves ticket 6758.
16289 - Don't log about reloading the microdescriptor cache at startup. Our
16290 bootstrap warnings are supposed to tell the user when there's a
16291 problem, and our bootstrap notices say when there isn't. Resolves
16292 ticket 6759; bugfix on 0.2.2.6-alpha.
16293 - Don't log "I learned some more directory information" when we're
16294 reading cached directory information. Reserve it for when new
16295 directory information arrives in response to a fetch. Resolves
16297 - Prevent rounding error in path bias counts when scaling
16298 them down, and use the correct scale factor default. Also demote
16299 some path bias related log messages down a level and make others
16300 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
16301 - We no longer warn so much when generating manpages from their
16304 o Code simplifications and refactoring:
16305 - Enhance our internal sscanf replacement so that we can eliminate
16306 the last remaining uses of the system sscanf. (Though those uses
16307 of sscanf were safe, sscanf itself is generally error prone, so
16308 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
16310 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
16311 - Move last_reachable and testing_since from routerinfo_t to node_t.
16312 Implements ticket 5529.
16313 - Add replaycache_t structure, functions and unit tests, then refactor
16314 rend_service_introduce() to be more clear to read, improve, debug,
16315 and test. Resolves bug 6177.
16316 - Finally remove support for malloc_good_size and malloc_usable_size.
16317 We had hoped that these functions would let us eke a little more
16318 memory out of our malloc implementation. Unfortunately, the only
16319 implementations that provided these functions are also ones that
16320 are already efficient about not overallocation: they never got us
16321 more than 7 or so bytes per allocation. Removing them saves us a
16322 little code complexity and a nontrivial amount of build complexity.
16324 o New requirements:
16325 - Tor maintainers now require Automake version 1.9 or later to build
16326 Tor from the Git repository. (Automake is not required when building
16327 from a source distribution.)
16330 Changes in version 0.2.3.21-rc - 2012-09-05
16331 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
16332 series. It fixes a trio of potential security bugs, fixes a bug where
16333 we were leaving some of the fast relays out of the microdescriptor
16334 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
16335 and cleans up other smaller issues.
16337 o Major bugfixes (security):
16338 - Tear down the circuit if we get an unexpected SENDME cell. Clients
16339 could use this trick to make their circuits receive cells faster
16340 than our flow control would have allowed, or to gum up the network,
16341 or possibly to do targeted memory denial-of-service attacks on
16342 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
16343 from July 2002, before the release of Tor 0.0.0. We had committed
16344 this patch previously, but we had to revert it because of bug 6271.
16345 Now that 6271 is fixed, this patch appears to work.
16346 - Reject any attempt to extend to an internal address. Without
16347 this fix, a router could be used to probe addresses on an internal
16348 network to see whether they were accepting connections. Fixes bug
16349 6710; bugfix on 0.0.8pre1.
16350 - Do not crash when comparing an address with port value 0 to an
16351 address policy. This bug could have been used to cause a remote
16352 assertion failure by or against directory authorities, or to
16353 allow some applications to crash clients. Fixes bug 6690; bugfix
16357 - Remove the upper bound on microdescriptor length. We were hitting
16358 the limit for routers with complex exit policies or family
16359 declarations, causing clients to not use them. Fixes the first
16360 piece of bug 6404; fix on 0.2.2.6-alpha.
16361 - Detect "ORPort 0" as meaning, uniformly, that we're not running
16362 as a relay. Previously, some of our code would treat the presence
16363 of any ORPort line as meaning that we should act like a relay,
16364 even though our new listener code would correctly not open any
16365 ORPorts for ORPort 0. Similar bugs in other Port options are also
16366 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
16369 - Avoid a pair of double-free and use-after-mark bugs that can
16370 occur with certain timings in canceled and re-received DNS
16371 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
16372 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
16373 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
16374 - Allow one-hop directory fetching circuits the full "circuit build
16375 timeout" period, rather than just half of it, before failing them
16376 and marking the relay down. This fix should help reduce cases where
16377 clients declare relays (or worse, bridges) unreachable because
16378 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
16379 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
16381 - Authorities no longer include any router in their microdescriptor
16382 consensuses for which they couldn't generate or agree on a
16383 microdescriptor. Fixes the second piece of bug 6404; fix on
16385 - Detect and reject attempts to specify both "FooPort" and
16386 "FooPort 0" in the same configuration domain. (It's still okay
16387 to have a FooPort in your configuration file, and use "FooPort 0"
16388 on the command line to disable it.) Fixes the second half of bug
16389 6507; bugfix on 0.2.3.3-alpha.
16390 - Make wildcarded addresses (that is, ones beginning with "*.") work
16391 when provided via the controller's MapAddress command. Previously,
16392 they were accepted, but we never actually noticed that they were
16393 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
16394 - Avoid crashing on a malformed state file where EntryGuardPathBias
16395 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
16396 - Add a (probably redundant) memory clear between iterations of
16397 the router status voting loop, to prevent future coding errors
16398 where data might leak between iterations of the loop. Resolves
16401 o Minor bugfixes (log messages):
16402 - Downgrade "set buildtimeout to low value" messages to "info"
16403 severity; they were never an actual problem, there was never
16404 anything reasonable to do about them, and they tended to spam logs
16405 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
16406 - Downgrade path-bias warning messages to "info". We'll try to get
16407 them working better in 0.2.4. Add internal circuit construction
16408 state to protect against the noisy warn message "Unexpectedly high
16409 circuit_successes". Also add some additional rate-limited notice
16410 messages to help determine the root cause of the warn. Fixes bug
16411 6475. Bugfix against 0.2.3.17-beta.
16412 - Move log message when unable to find a microdesc in a routerstatus
16413 entry to parse time. Previously we'd spam this warning every time
16414 we tried to figure out which microdescriptors to download. Fixes
16415 the third piece of bug 6404; fix on 0.2.3.18-rc.
16418 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
16419 change when the authority is deciding whether to accept a newly
16420 uploaded descriptor. Implements ticket 6423.
16421 - Add missing documentation for consensus and microdesc files.
16422 Resolves ticket 6732.
16425 Changes in version 0.2.2.38 - 2012-08-12
16426 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
16427 attack that could in theory leak path information.
16430 - Avoid an uninitialized memory read when reading a vote or consensus
16431 document that has an unrecognized flavor name. This read could
16432 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
16433 - Try to leak less information about what relays a client is
16434 choosing to a side-channel attacker. Previously, a Tor client would
16435 stop iterating through the list of available relays as soon as it
16436 had chosen one, thus finishing a little earlier when it picked
16437 a router earlier in the list. If an attacker can recover this
16438 timing information (nontrivial but not proven to be impossible),
16439 they could learn some coarse-grained information about which relays
16440 a client was picking (middle nodes in particular are likelier to
16441 be affected than exits). The timing attack might be mitigated by
16442 other factors (see bug 6537 for some discussion), but it's best
16443 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
16446 Changes in version 0.2.3.20-rc - 2012-08-05
16447 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
16448 series. It fixes a pair of code security bugs and a potential anonymity
16449 issue, updates our RPM spec files, and cleans up other smaller issues.
16452 - Avoid read-from-freed-memory and double-free bugs that could occur
16453 when a DNS request fails while launching it. Fixes bug 6480;
16454 bugfix on 0.2.0.1-alpha.
16455 - Avoid an uninitialized memory read when reading a vote or consensus
16456 document that has an unrecognized flavor name. This read could
16457 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
16458 - Try to leak less information about what relays a client is
16459 choosing to a side-channel attacker. Previously, a Tor client would
16460 stop iterating through the list of available relays as soon as it
16461 had chosen one, thus finishing a little earlier when it picked
16462 a router earlier in the list. If an attacker can recover this
16463 timing information (nontrivial but not proven to be impossible),
16464 they could learn some coarse-grained information about which relays
16465 a client was picking (middle nodes in particular are likelier to
16466 be affected than exits). The timing attack might be mitigated by
16467 other factors (see bug 6537 for some discussion), but it's best
16468 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
16471 - Try to make the warning when giving an obsolete SOCKSListenAddress
16472 a little more useful.
16473 - Terminate active server managed proxies if Tor stops being a
16474 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
16475 - Provide a better error message about possible OSX Asciidoc failure
16476 reasons. Fixes bug 6436.
16477 - Warn when Tor is configured to use accounting in a way that can
16478 link a hidden service to some other hidden service or public
16479 address. Resolves ticket 6490.
16482 - Check return value of fputs() when writing authority certificate
16483 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
16484 - Ignore ServerTransportPlugin lines when Tor is not configured as
16485 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
16486 - When disabling guards for having too high a proportion of failed
16487 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
16491 - Update our default RPM spec files to work with mock and rpmbuild
16492 on RHEL/Fedora. They have an updated set of dependencies and
16493 conflicts, a fix for an ancient typo when creating the "_tor"
16494 user, and better instructions. Thanks to Ondrej Mikle for the
16495 patch series. Fixes bug 6043.
16498 - Make it possible to set the TestingTorNetwork configuration
16499 option using AlternateDirAuthority and AlternateBridgeAuthority
16500 as an alternative to setting DirServer. Addresses ticket 6377.
16503 - Clarify the documentation for the Alternate*Authority options.
16505 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
16507 o Code simplification and refactoring:
16508 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
16509 10 lines. Also, don't nest them. Doing so in the past has
16510 led to hard-to-debug code. The new style is to use the
16511 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
16514 Changes in version 0.2.3.19-rc - 2012-07-06
16515 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
16516 series. It fixes the compile on Windows, reverts to a GeoIP database
16517 that isn't as broken, and fixes a flow control bug that has been around
16518 since the beginning of Tor.
16521 - Fix a bug handling SENDME cells on nonexistent streams that could
16522 result in bizarre window values. Report and patch contributed
16523 pseudonymously. Fixes part of bug 6271. This bug was introduced
16524 before the first Tor release, in svn commit r152.
16525 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
16526 June 2012 database, Maxmind marked many Tor relays as country "A1",
16527 which will cause risky behavior for clients that set EntryNodes
16528 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
16529 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
16530 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
16533 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
16534 bugfix on 0.2.1.10-alpha.
16537 Changes in version 0.2.3.18-rc - 2012-06-28
16538 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
16539 series. It fixes a few smaller bugs, but generally appears stable.
16540 Please test it and let us know whether it is!
16543 - Allow wildcarded mapaddress targets to be specified on the
16544 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
16545 - Make our linker option detection code more robust against linkers
16546 such as on FreeBSD 8, where a bad combination of options completes
16547 successfully but makes an unrunnable binary. Fixes bug 6173;
16548 bugfix on 0.2.3.17-beta.
16550 o Minor bugfixes (on 0.2.2.x and earlier):
16551 - Avoid a false positive in the util/threads unit test by increasing
16552 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
16553 - Replace "Sending publish request" log messages with "Launching
16554 upload", so that they no longer confusingly imply that we're
16555 sending something to a directory we might not even be connected
16556 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
16557 - Make sure to set *socket_error in all error cases in
16558 connection_connect(), so it can't produce a warning about
16559 errno being zero from errno_to_orconn_end_reason(). Bugfix on
16560 0.2.1.1-alpha; resolves ticket 6028.
16561 - Downgrade "Got a certificate, but we already have it" log messages
16562 from warning to info, except when we're a dirauth. Fixes bug 5238;
16563 bugfix on 0.2.1.7-alpha.
16564 - When checking for requested signatures on the latest consensus
16565 before serving it to a client, make sure to check the right
16566 consensus flavor. Bugfix on 0.2.2.6-alpha.
16567 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
16568 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
16570 o Minor bugfixes (on 0.2.3.x):
16571 - Make format_helper_exit_status() avoid unnecessary space padding
16572 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
16574 - Downgrade a message about cleaning the microdescriptor cache to
16575 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
16576 - Log a BUG message at severity INFO if we have a networkstatus with
16577 a missing entry for some microdescriptor. Continues on a patch
16579 - Improve the log message when a managed proxy fails to launch. Fixes
16580 bug 5099; bugfix on 0.2.3.6-alpha.
16581 - Don't do DNS lookups when parsing corrupted managed proxy protocol
16582 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
16583 - When formatting wildcarded address mappings for the controller,
16584 be sure to include "*." as appropriate. Partially fixes bug 6244;
16585 bugfix on 0.2.3.9-alpha.
16586 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
16587 Bugfix on 0.2.3.13-alpha.
16588 - Stop logging messages about running with circuit timeout learning
16589 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
16590 - Disable a spurious warning about reading on a marked and flushing
16591 connection. We shouldn't be doing that, but apparently we
16592 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
16593 - Fix a bug that stopped AllowDotExit from working on addresses
16594 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
16597 o Code simplification, refactoring, unit tests:
16598 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
16599 Libevent's notion of cached time when possible.
16600 - Remove duplicate code for invoking getrlimit() from control.c.
16601 - Add a unit test for the environment_variable_names_equal function.
16604 - Document the --defaults-torrc option, and the new (in 0.2.3)
16605 semantics for overriding, extending, and clearing lists of
16606 options. Closes bug 4748.
16609 Changes in version 0.2.3.17-beta - 2012-06-15
16610 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
16611 gets our TLS handshake back on track for being able to blend in with
16612 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
16613 with Vidalia, and otherwise continues to get us closer to a release
16617 - Enable gcc and ld hardening by default. Resolves ticket 5210.
16618 - Update TLS cipher list to match Firefox 8 and later. Resolves
16620 - Implement the client side of proposal 198: remove support for
16621 clients falsely claiming to support standard ciphersuites that
16622 they can actually provide. As of modern OpenSSL versions, it's not
16623 necessary to fake any standard ciphersuite, and doing so prevents
16624 us from using better ciphersuites in the future, since servers
16625 can't know whether an advertised ciphersuite is really supported or
16626 not. Some hosts -- notably, ones with very old versions of OpenSSL
16627 or where OpenSSL has been built with ECC disabled -- will stand
16628 out because of this change; TBB users should not be affected.
16631 - Change the default value for DynamicDHGroups (introduced in
16632 0.2.3.9-alpha) to 0. This feature can make Tor relays less
16633 identifiable by their use of the mod_ssl DH group, but at
16634 the cost of some usability (#4721) and bridge tracing (#6087)
16635 regressions. Resolves ticket 5598.
16636 - Send a CRLF at the end of each STATUS_* control protocol event. This
16637 bug tickled a bug in Vidalia which would make it freeze. Fixes
16638 bug 6094; bugfix on 0.2.3.16-alpha.
16641 - Disable writing on marked-for-close connections when they are
16642 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
16643 bug 5263; bugfix on 0.0.2pre13, where we first added a special
16644 case for flushing marked connections.
16645 - Detect SSL handshake even when the initial attempt to write the
16646 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
16647 - Change the AllowDotExit rules so they should actually work.
16648 We now enforce AllowDotExit only immediately after receiving an
16649 address via SOCKS or DNSPort: other sources are free to provide
16650 .exit addresses after the resolution occurs. Fixes bug 3940;
16651 bugfix on 0.2.2.1-alpha.
16652 - Fix a (harmless) integer overflow in cell statistics reported by
16653 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
16654 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
16655 right places and never depends on the consensus parameters or
16656 computes adaptive timeouts when it is disabled. Fixes bug 5049;
16657 bugfix on 0.2.2.14-alpha.
16658 - When building Tor on Windows with -DUNICODE (not default), ensure
16659 that error messages, filenames, and DNS server names are always
16660 NUL-terminated when we convert them to a single-byte encoding.
16661 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
16662 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
16663 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
16664 - Fix an edge case where TestingTorNetwork is set but the authorities
16665 and relays all have an uptime of zero, where the private Tor network
16666 could briefly lack support for hidden services. Fixes bug 3886;
16667 bugfix on 0.2.2.18-alpha.
16668 - Correct the manpage's descriptions for the default values of
16669 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
16671 - Fix the documentation for the --hush and --quiet command line
16672 options, which changed their behavior back in 0.2.3.3-alpha.
16673 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
16677 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
16678 more information to it, so that we can track it down in case it
16679 returns again. Mitigates bug 5235.
16680 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
16681 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
16682 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
16683 - Warn the user when HTTPProxy, but no other proxy type, is
16684 configured. This can cause surprising behavior: it doesn't send
16685 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
16686 directory traffic only. Resolves ticket 4663.
16687 - Issue a notice if a guard completes less than 40% of your circuits.
16688 Threshold is configurable by torrc option PathBiasNoticeRate and
16689 consensus parameter pb_noticepct. There is additional, off-by-
16690 default code to disable guards which fail too many circuits.
16691 Addresses ticket 5458.
16692 - Update to the June 6 2012 Maxmind GeoLite Country database.
16694 o Code simplifications and refactoring:
16695 - Remove validate_pluggable_transports_config(): its warning
16696 message is now handled by connection_or_connect().
16699 Changes in version 0.2.2.37 - 2012-06-06
16700 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
16701 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
16705 - Work around a bug in OpenSSL that broke renegotiation with TLS
16706 1.1 and TLS 1.2. Without this workaround, all attempts to speak
16707 the v2 Tor connection protocol when both sides were using OpenSSL
16708 1.0.1 would fail. Resolves ticket 6033.
16709 - When waiting for a client to renegotiate, don't allow it to add
16710 any bytes to the input buffer. This fixes a potential DoS issue.
16711 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
16712 - Fix an edge case where if we fetch or publish a hidden service
16713 descriptor, we might build a 4-hop circuit and then use that circuit
16714 for exiting afterwards -- even if the new last hop doesn't obey our
16715 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
16718 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
16719 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
16722 - Tell GCC and Clang to check for any errors in format strings passed
16723 to the tor_v*(print|scan)f functions.
16726 Changes in version 0.2.3.16-alpha - 2012-06-05
16727 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
16728 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
16729 currently). It also fixes a variety of smaller bugs and other cleanups
16730 that get us closer to a release candidate.
16732 o Major bugfixes (general):
16733 - Work around a bug in OpenSSL that broke renegotiation with TLS
16734 1.1 and TLS 1.2. Without this workaround, all attempts to speak
16735 the v2 Tor connection protocol when both sides were using OpenSSL
16736 1.0.1 would fail. Resolves ticket 6033.
16737 - When waiting for a client to renegotiate, don't allow it to add
16738 any bytes to the input buffer. This fixes a potential DoS issue.
16739 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
16740 - Pass correct OR address to managed proxies (like obfsproxy),
16741 even when ORListenAddress is used. Fixes bug 4865; bugfix on
16743 - The advertised platform of a router now includes only its operating
16744 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
16745 service pack level (for Windows) or its CPU architecture (for Unix).
16746 We also no longer include the "git-XYZ" tag in the version. Resolves
16749 o Major bugfixes (clients):
16750 - If we are unable to find any exit that supports our predicted ports,
16751 stop calling them predicted, so that we don't loop and build
16752 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
16753 which introduced predicted ports.
16754 - Fix an edge case where if we fetch or publish a hidden service
16755 descriptor, we might build a 4-hop circuit and then use that circuit
16756 for exiting afterwards -- even if the new last hop doesn't obey our
16757 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
16758 - Check at each new consensus whether our entry guards were picked
16759 long enough ago that we should rotate them. Previously, we only
16760 did this check at startup, which could lead to us holding a guard
16761 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
16762 - When fetching a bridge descriptor from a bridge authority,
16763 always do so anonymously, whether we have been able to open
16764 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
16765 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
16766 but we'll need to wait for bug 6010 before it's actually usable.
16768 o Major bugfixes (directory authorities):
16769 - When computing weight parameters, behave more robustly in the
16770 presence of a bad bwweightscale value. Previously, the authorities
16771 would crash if they agreed on a sufficiently broken weight_scale
16772 value: now, they use a reasonable default and carry on. Partial
16773 fix for 5786; bugfix on 0.2.2.17-alpha.
16774 - Check more thoroughly to prevent a rogue authority from
16775 double-voting on any consensus directory parameter. Previously,
16776 authorities would crash in this case if the total number of
16777 votes for any parameter exceeded the number of active voters,
16778 but would let it pass otherwise. Partial fix for bug 5786; bugfix
16782 - Rate-limit log messages when asked to connect anonymously to
16783 a private address. When these hit, they tended to hit fast and
16784 often. Also, don't bother trying to connect to addresses that we
16785 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
16786 reply makes us think we have been lied to, even when the address the
16787 client tried to connect to was "localhost." Resolves ticket 2822.
16788 - Allow packagers to insert an extra string in server descriptor
16789 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
16790 Resolves the rest of ticket 2988.
16791 - Raise the threshold of server descriptors needed (75%) and exit
16792 server descriptors needed (50%) before we will declare ourselves
16793 bootstrapped. This will make clients start building circuits a
16794 little later, but makes the initially constructed circuits less
16795 skewed and less in conflict with further directory fetches. Fixes
16797 - Close any connection that sends unrecognized junk before the
16798 handshake. Solves an issue noted in bug 4369.
16799 - Improve log messages about managed transports. Resolves ticket 5070.
16800 - Tag a bridge's descriptor as "never to be sent unencrypted".
16801 This shouldn't matter, since bridges don't open non-anonymous
16802 connections to the bridge authority and don't allow unencrypted
16803 directory connections from clients, but we might as well make
16804 sure. Closes bug 5139.
16805 - Expose our view of whether we have gone dormant to the controller,
16806 via a new "GETINFO dormant" value. Torbutton and other controllers
16807 can use this to avoid doing periodic requests through Tor while
16808 it's dormant (bug 4718). Fixes bug 5954.
16809 - Tell GCC and Clang to check for any errors in format strings passed
16810 to the tor_v*(print|scan)f functions.
16811 - Update to the May 1 2012 Maxmind GeoLite Country database.
16813 o Minor bugfixes (already included in 0.2.2.36):
16814 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
16815 Fixes bug 5346; bugfix on 0.0.8pre3.
16816 - Correct parsing of certain date types in parse_http_time().
16817 Without this patch, If-Modified-Since would behave
16818 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
16819 Esteban Manchado Velázques.
16820 - Make our number-parsing functions always treat too-large values
16821 as an error, even when those values exceed the width of the
16822 underlying type. Previously, if the caller provided these
16823 functions with minima or maxima set to the extreme values of the
16824 underlying integer type, these functions would return those
16825 values on overflow rather than treating overflow as an error.
16826 Fixes part of bug 5786; bugfix on 0.0.9.
16827 - If we hit the error case where routerlist_insert() replaces an
16828 existing (old) server descriptor, make sure to remove that
16829 server descriptor from the old_routers list. Fix related to bug
16830 1776. Bugfix on 0.2.2.18-alpha.
16831 - Clarify the behavior of MaxCircuitDirtiness with hidden service
16832 circuits. Fixes issue 5259.
16834 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
16835 - Prevent a null-pointer dereference when receiving a data cell
16836 for a nonexistent stream when the circuit in question has an
16837 empty deliver window. We don't believe this is triggerable,
16838 since we don't currently allow deliver windows to become empty,
16839 but the logic is tricky enough that it's better to make the code
16840 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
16841 - Fix a memory leak when trying to launch a DNS request when the
16842 network is disabled or the nameservers are unconfigurable. Fixes
16843 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
16844 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
16845 - Don't hold a Windows file handle open for every file mapping;
16846 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
16848 - Avoid O(n^2) performance characteristics when parsing a large
16849 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
16850 - Format more doubles with %f, not %lf. Patch from grarpamp to make
16851 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
16853 - Make our replacement implementation of strtok_r() compatible with
16854 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
16855 bugfix on 0.2.2.1-alpha.
16856 - Fix a NULL-pointer dereference on a badly formed
16857 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
16858 bugfix on 0.2.2.9-alpha.
16859 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
16860 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
16861 - Defensively refactor rend_mid_rendezvous() so that protocol
16862 violations and length checks happen in the beginning. Fixes
16864 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
16865 that IPv6 stuff will compile on MSVC, and compilation issues
16866 will be easier to track down. Fixes bug 5861.
16868 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
16869 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
16870 resource exhaustion, so that clients can adjust their load to
16871 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
16872 started using END_STREAM_REASON_RESOURCELIMIT.
16873 - Don't check for whether the address we're using for outbound
16874 connections has changed until after the outbound connection has
16875 completed. On Windows, getsockname() doesn't succeed until the
16876 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
16877 - If the configuration tries to set MyFamily on a bridge, refuse to
16878 do so, and warn about the security implications. Fixes bug 4657;
16879 bugfix on 0.2.0.3-alpha.
16880 - If the client fails to set a reasonable set of ciphersuites
16881 during its v2 handshake renegotiation, allow the renegotiation to
16882 continue nevertheless (i.e. send all the required certificates).
16883 Fixes bug 4591; bugfix on 0.2.0.20-rc.
16884 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
16885 option is set to 0 (which Vidalia version 0.2.16 now does when
16886 a SAVECONF attempt fails), perform other actions that SIGHUP
16887 usually causes (like reopening the logs). Fixes bug 5095; bugfix
16889 - If we fail to write a microdescriptor to the disk cache, do not
16890 continue replacing the old microdescriptor file. Fixes bug 2954;
16891 bugfix on 0.2.2.6-alpha.
16892 - Exit nodes don't need to fetch certificates for authorities that
16893 they don't recognize; only directory authorities, bridges,
16894 and caches need to do that. Fixes part of bug 2297; bugfix on
16896 - Correctly handle checking the permissions on the parent
16897 directory of a control socket in the root directory. Bug found
16898 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
16900 - When told to add a bridge with the same digest as a preexisting
16901 bridge but a different addr:port, change the addr:port as
16902 requested. Previously we would not notice the change. Fixes half
16903 of bug 5603; fix on 0.2.2.26-beta.
16904 - End AUTHCHALLENGE error messages (in the control protocol) with
16905 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
16907 o Minor bugfixes (on 0.2.3.x):
16908 - Turn an assertion (that the number of handshakes received as a
16909 server is not < 1) into a warning. Fixes bug 4873; bugfix on
16911 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
16912 we had reversed them when the answer was cached.) Fixes bug
16913 5723; bugfix on 0.2.3.1-alpha.
16914 - Work correctly on Linux systems with accept4 support advertised in
16915 their headers, but without accept4 support in the kernel. Fix
16916 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
16917 - When told to add a bridge with the same addr:port as a preexisting
16918 bridge but a different transport, change the transport as
16919 requested. Previously we would not notice the change. Fixes half
16920 of bug 5603; fix on 0.2.3.2-alpha.
16921 - Avoid a "double-reply" warning when replying to a SOCKS request
16922 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
16923 bugfix on 0.2.3.4-alpha.
16924 - Fix a bug where a bridge authority crashes if it has seen no
16925 directory requests when it's time to write statistics to disk.
16926 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
16928 - Don't try to open non-control listeners when DisableNetwork is set.
16929 Previously, we'd open all listeners, then immediately close them.
16930 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
16931 - Don't abort the managed proxy protocol if the managed proxy
16932 sends us an unrecognized line; ignore it instead. Fixes bug
16933 5910; bugfix on 0.2.3.9-alpha.
16934 - Fix a compile warning in crypto.c when compiling with clang 3.1.
16935 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
16936 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
16937 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
16938 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
16939 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
16940 - Resolve numerous small warnings and build issues with MSVC. Resolves
16943 o Documentation fixes:
16944 - Improve the manual's documentation for the NT Service command-line
16945 options. Addresses ticket 3964.
16946 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
16947 - Document the changes to the ORPort and DirPort options, and the
16948 fact that {OR/Dir}ListenAddress is now unnecessary (and
16949 therefore deprecated). Resolves ticket 5597.
16952 - Remove the torrc.bridge file: we don't use it for anything, and
16953 it had become badly desynchronized from torrc.sample. Resolves
16957 Changes in version 0.2.2.36 - 2012-05-24
16958 Tor 0.2.2.36 updates the addresses for two of the eight directory
16959 authorities, fixes some potential anonymity and security issues,
16960 and fixes several crash bugs.
16962 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
16963 known flaws, and nobody should be using them. You should upgrade. If
16964 you're using a Linux or BSD and its packages are obsolete, stop using
16965 those packages and upgrade anyway.
16967 o Directory authority changes:
16968 - Change IP address for maatuska (v3 directory authority).
16969 - Change IP address for ides (v3 directory authority), and rename
16973 - When building or running with any version of OpenSSL earlier
16974 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
16975 versions have a bug (CVE-2011-4576) in which their block cipher
16976 padding includes uninitialized data, potentially leaking sensitive
16977 information to any peer with whom they make a SSLv3 connection. Tor
16978 does not use SSL v3 by default, but a hostile client or server
16979 could force an SSLv3 connection in order to gain information that
16980 they shouldn't have been able to get. The best solution here is to
16981 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
16982 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
16983 to make sure that the bug can't happen.
16984 - Never use a bridge or a controller-supplied node as an exit, even
16985 if its exit policy allows it. Found by wanoskarnet. Fixes bug
16986 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
16987 and 0.2.0.3-alpha (for bridge-purpose descriptors).
16988 - Only build circuits if we have a sufficient threshold of the total
16989 descriptors that are marked in the consensus with the "Exit"
16990 flag. This mitigates an attack proposed by wanoskarnet, in which
16991 all of a client's bridges collude to restrict the exit nodes that
16992 the client knows about. Fixes bug 5343.
16993 - Provide controllers with a safer way to implement the cookie
16994 authentication mechanism. With the old method, if another locally
16995 running program could convince a controller that it was the Tor
16996 process, then that program could trick the controller into telling
16997 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
16998 authentication method uses a challenge-response approach to prevent
16999 this attack. Fixes bug 5185; implements proposal 193.
17002 - Avoid logging uninitialized data when unable to decode a hidden
17003 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
17004 - Avoid a client-side assertion failure when receiving an INTRODUCE2
17005 cell on a general purpose circuit. Fixes bug 5644; bugfix on
17007 - Fix builds when the path to sed, openssl, or sha1sum contains
17008 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
17010 - Correct our replacements for the timeradd() and timersub() functions
17011 on platforms that lack them (for example, Windows). The timersub()
17012 function is used when expiring circuits, while timeradd() is
17013 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
17014 bugfix on 0.2.2.24-alpha.
17015 - Fix the SOCKET_OK test that we use to tell when socket
17016 creation fails so that it works on Win64. Fixes part of bug 4533;
17017 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
17020 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
17021 Fixes bug 5346; bugfix on 0.0.8pre3.
17022 - Make our number-parsing functions always treat too-large values
17023 as an error, even when those values exceed the width of the
17024 underlying type. Previously, if the caller provided these
17025 functions with minima or maxima set to the extreme values of the
17026 underlying integer type, these functions would return those
17027 values on overflow rather than treating overflow as an error.
17028 Fixes part of bug 5786; bugfix on 0.0.9.
17029 - Older Linux kernels erroneously respond to strange nmap behavior
17030 by having accept() return successfully with a zero-length
17031 socket. When this happens, just close the connection. Previously,
17032 we would try harder to learn the remote address: but there was
17033 no such remote address to learn, and our method for trying to
17034 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
17035 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
17036 - Correct parsing of certain date types in parse_http_time().
17037 Without this patch, If-Modified-Since would behave
17038 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
17039 Esteban Manchado Velázques.
17040 - Change the BridgePassword feature (part of the "bridge community"
17041 design, which is not yet implemented) to use a time-independent
17042 comparison. The old behavior might have allowed an adversary
17043 to use timing to guess the BridgePassword value. Fixes bug 5543;
17044 bugfix on 0.2.0.14-alpha.
17045 - Detect and reject certain misformed escape sequences in
17046 configuration values. Previously, these values would cause us
17047 to crash if received in a torrc file or over an authenticated
17048 control port. Bug found by Esteban Manchado Velázquez, and
17049 independently by Robert Connolly from Matta Consulting who further
17050 noted that it allows a post-authentication heap overflow. Patch
17051 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
17052 bugfix on 0.2.0.16-alpha.
17053 - Fix a compile warning when using the --enable-openbsd-malloc
17054 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
17055 - During configure, detect when we're building with clang version
17056 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
17057 CFLAGS. clang doesn't support them yet.
17058 - When sending an HTTP/1.1 proxy request, include a Host header.
17059 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
17060 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
17061 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
17062 - If we hit the error case where routerlist_insert() replaces an
17063 existing (old) server descriptor, make sure to remove that
17064 server descriptor from the old_routers list. Fix related to bug
17065 1776. Bugfix on 0.2.2.18-alpha.
17067 o Minor bugfixes (documentation and log messages):
17068 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
17069 Fixes bug 4856; bugfix on Tor 0.0.6.
17070 - Update "ClientOnly" man page entry to explain that there isn't
17071 really any point to messing with it. Resolves ticket 5005.
17072 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
17073 directory authority option (introduced in Tor 0.2.2.34).
17074 - Downgrade the "We're missing a certificate" message from notice
17075 to info: people kept mistaking it for a real problem, whereas it
17076 is seldom the problem even when we are failing to bootstrap. Fixes
17077 bug 5067; bugfix on 0.2.0.10-alpha.
17078 - Correctly spell "connect" in a log message on failure to create a
17079 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
17080 - Clarify the behavior of MaxCircuitDirtiness with hidden service
17081 circuits. Fixes issue 5259.
17084 - Directory authorities now reject versions of Tor older than
17085 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
17086 inclusive. These versions accounted for only a small fraction of
17087 the Tor network, and have numerous known security issues. Resolves
17089 - Update to the May 1 2012 Maxmind GeoLite Country database.
17092 - When sending or relaying a RELAY_EARLY cell, we used to convert
17093 it to a RELAY cell if the connection was using the v1 link
17094 protocol. This was a workaround for older versions of Tor, which
17095 didn't handle RELAY_EARLY cells properly. Now that all supported
17096 versions can handle RELAY_EARLY cells, and now that we're enforcing
17097 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
17098 remove this workaround. Addresses bug 4786.
17101 Changes in version 0.2.3.15-alpha - 2012-04-30
17102 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
17103 the development branch build on Windows again.
17105 o Minor bugfixes (on 0.2.2.x and earlier):
17106 - Make sure that there are no unhandled pending TLS errors before
17107 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
17108 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
17109 Bugfix on 0.1.0.5-rc; fixes bug 4528.
17110 - Fix an assert that directory authorities could trigger on sighup
17111 during some configuration state transitions. We now don't treat
17112 it as a fatal error when the new descriptor we just generated in
17113 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
17114 - After we pick a directory mirror, we would refuse to use it if
17115 it's in our ExcludeExitNodes list, resulting in mysterious failures
17116 to bootstrap for people who just wanted to avoid exiting from
17117 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
17118 - When building with --enable-static-tor on OpenBSD, do not
17119 erroneously attempt to link -lrt. Fixes bug 5103.
17121 o Minor bugfixes (on 0.2.3.x):
17122 - When Tor is built with kernel headers from a recent (last few
17123 years) Linux kernel, do not fail to run on older (pre-2.6.28
17124 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
17125 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
17126 and 0.2.3.12-alpha.
17127 - Fix compilation with miniupnpc version 1.6; patch from
17128 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
17129 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
17130 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
17131 - Fix compilation on platforms without unistd.h, or where environ
17132 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
17135 - Directory authorities are now a little more lenient at accepting
17136 older router descriptors, or newer router descriptors that don't
17137 make big changes. This should help ameliorate past and future
17138 issues where routers think they have uploaded valid descriptors,
17139 but the authorities don't think so. Fix for ticket 2479.
17140 - Make the code that clients use to detect an address change be
17141 IPv6-aware, so that it won't fill clients' logs with error
17142 messages when trying to get the IPv4 address of an IPv6
17143 connection. Implements ticket 5537.
17145 o Removed features:
17146 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
17147 authorities needed to use it for a while to keep the network working
17148 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
17149 that was six months ago. As of now, it should no longer be needed
17153 Changes in version 0.2.3.14-alpha - 2012-04-23
17154 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
17155 candidate. It also dramatically speeds up AES: fast relays should
17156 consider switching to the newer OpenSSL library.
17158 o Directory authority changes:
17159 - Change IP address for ides (v3 directory authority), and rename
17163 - Avoid logging uninitialized data when unable to decode a hidden
17164 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
17165 - Avoid a client-side assertion failure when receiving an INTRODUCE2
17166 cell on a general purpose circuit. Fixes bug 5644; bugfix on
17168 - If authorities are unable to get a v2 consensus document from other
17169 directory authorities, they no longer fall back to fetching
17170 them from regular directory caches. Fixes bug 5635; bugfix on
17171 0.2.2.26-beta, where routers stopped downloading v2 consensus
17172 documents entirely.
17173 - When we start a Tor client with a normal consensus already cached,
17174 be willing to download a microdescriptor consensus. Fixes bug 4011;
17175 fix on 0.2.3.1-alpha.
17177 o Major features (performance):
17178 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
17179 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
17180 vectorized AES implementations as appropriate. These can be much,
17181 much faster than other AES implementations.
17183 o Minor bugfixes (0.2.2.x and earlier):
17184 - Don't launch more than 10 service-side introduction-point circuits
17185 for a hidden service in five minutes. Previously, we would consider
17186 launching more introduction-point circuits if at least one second
17187 had passed without any introduction-point circuits failing. Fixes
17188 bug 4607; bugfix on 0.0.7pre1.
17189 - Change the BridgePassword feature (part of the "bridge community"
17190 design, which is not yet implemented) to use a time-independent
17191 comparison. The old behavior might have allowed an adversary
17192 to use timing to guess the BridgePassword value. Fixes bug 5543;
17193 bugfix on 0.2.0.14-alpha.
17194 - Enforce correct return behavior of tor_vsscanf() when the '%%'
17195 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
17196 - When sending an HTTP/1.1 proxy request, include a Host header.
17197 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
17198 - Don't log that we have "decided to publish new relay descriptor"
17199 unless we are actually publishing a descriptor. Fixes bug 3942;
17200 bugfix on 0.2.2.28-beta.
17202 o Minor bugfixes (0.2.3.x):
17203 - Fix a bug where a bridge authority crashes (on a failed assert)
17204 if it has seen no directory requests when it's time to write
17205 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
17206 - Fix bug stomping on ORPort option NoListen and ignoring option
17207 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
17208 - In the testsuite, provide a large enough buffer in the tor_sscanf
17209 unit test. Otherwise we'd overrun that buffer and crash during
17210 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
17212 - Make sure we create the keys directory if it doesn't exist and we're
17213 about to store the dynamic Diffie-Hellman parameters. Fixes bug
17214 5572; bugfix on 0.2.3.13-alpha.
17215 - Fix a small memory leak when trying to decode incorrect base16
17216 authenticator during SAFECOOKIE authentication. Found by
17217 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
17220 - Add more information to a log statement that might help track down
17221 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
17222 non-IP address" messages (or any Bug messages, for that matter!),
17223 please let us know about it.
17224 - Relays now understand an IPv6 address when they get one from a
17225 directory server. Resolves ticket 4875.
17226 - Resolve IPv6 addresses in bridge and entry statistics to country
17227 code "??" which means we at least count them. Resolves ticket 5053;
17228 improves on 0.2.3.9-alpha.
17229 - Update to the April 3 2012 Maxmind GeoLite Country database.
17230 - Begin a doc/state-contents.txt file to explain the contents of
17231 the Tor state file. Fixes bug 2987.
17233 o Default torrc changes:
17234 - Stop listing "socksport 9050" in torrc.sample. We open a socks
17235 port on 9050 by default anyway, so this should not change anything
17237 - Stop mentioning the deprecated *ListenAddress options in
17238 torrc.sample. Fixes bug 5438.
17239 - Document unit of bandwidth related options in sample torrc.
17242 o Removed features:
17243 - The "torify" script no longer supports the "tsocks" socksifier
17244 tool, since tsocks doesn't support DNS and UDP right for Tor.
17245 Everyone should be using torsocks instead. Fixes bugs 3530 and
17246 5180. Based on a patch by "ugh".
17248 o Code refactoring:
17249 - Change the symmetric cipher interface so that creating and
17250 initializing a stream cipher are no longer separate functions.
17251 - Remove all internal support for unpadded RSA. We never used it, and
17252 it would be a bad idea to start.
17255 Changes in version 0.2.3.13-alpha - 2012-03-26
17256 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
17257 in managed pluggable transports, as well as providing other cleanups
17258 that get us closer to a release candidate.
17260 o Directory authority changes:
17261 - Change IP address for maatuska (v3 directory authority).
17264 - Provide controllers with a safer way to implement the cookie
17265 authentication mechanism. With the old method, if another locally
17266 running program could convince a controller that it was the Tor
17267 process, then that program could trick the controller into telling
17268 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
17269 authentication method uses a challenge-response approach to prevent
17270 this attack. Fixes bug 5185, implements proposal 193.
17271 - Never use a bridge or a controller-supplied node as an exit, even
17272 if its exit policy allows it. Found by wanoskarnet. Fixes bug
17273 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
17274 and 0.2.0.3-alpha (for bridge-purpose descriptors).
17275 - Only build circuits if we have a sufficient threshold of the total
17276 descriptors that are marked in the consensus with the "Exit"
17277 flag. This mitigates an attack proposed by wanoskarnet, in which
17278 all of a client's bridges collude to restrict the exit nodes that
17279 the client knows about. Fixes bug 5343.
17281 o Major bugfixes (on Tor 0.2.3.x):
17282 - Avoid an assert when managed proxies like obfsproxy are configured,
17283 and we receive HUP signals or setconf attempts too rapidly. This
17284 situation happens most commonly when Vidalia tries to attach to
17285 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
17286 bugfix on 0.2.3.6-alpha.
17287 - Fix a relay-side pluggable transports bug where managed proxies were
17288 unreachable from the Internet, because Tor asked them to bind on
17289 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
17290 - Stop discarding command-line arguments when TestingTorNetwork
17291 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
17292 0.2.3.9-alpha, where task 4552 added support for two layers of
17294 - Resume allowing the unit tests to run in gdb. This was accidentally
17295 made impossible when the DisableDebuggerAttachment option was
17296 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
17297 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
17298 0.2.3.11-alpha. Reported by Anthony G. Basile.
17300 o Minor bugfixes (on 0.2.2.x and earlier):
17301 - Ensure we don't cannibalize circuits that are longer than three hops
17302 already, so we don't end up making circuits with 5 or more
17303 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
17304 0.1.0.1-rc which introduced cannibalization.
17305 - Detect and reject certain misformed escape sequences in
17306 configuration values. Previously, these values would cause us
17307 to crash if received in a torrc file or over an authenticated
17308 control port. Bug found by Esteban Manchado Velázquez, and
17309 independently by Robert Connolly from Matta Consulting who further
17310 noted that it allows a post-authentication heap overflow. Patch
17311 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
17312 bugfix on 0.2.0.16-alpha.
17313 - Fix a compile warning when using the --enable-openbsd-malloc
17314 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
17315 - Directory caches no longer refuse to clean out descriptors because
17316 of missing v2 networkstatus documents, unless they're configured
17317 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
17318 0.2.2.26-beta. Patch by Daniel Bryg.
17319 - Update to the latest version of the tinytest unit testing framework.
17320 This includes a couple of bugfixes that can be relevant for
17321 running forked unit tests on Windows, and removes all reserved
17324 o Minor bugfixes (on 0.2.3.x):
17325 - On a failed pipe() call, don't leak file descriptors. Fixes bug
17326 4296; bugfix on 0.2.3.1-alpha.
17327 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
17328 until after we have received a CERTS cell. Fixes bug 4361; bugfix
17329 on 0.2.3.6-alpha. Patch by "frosty".
17330 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
17331 option, so that the IP stack doesn't decide to use it for IPv4
17332 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
17333 - Ensure that variables set in Tor's environment cannot override
17334 environment variables that Tor passes to a managed
17335 pluggable-transport proxy. Previously, Tor would pass every
17336 variable in its environment to managed proxies along with the new
17337 ones, in such a way that on many operating systems, the inherited
17338 environment variables would override those which Tor tried to
17339 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
17340 bugfix on 0.2.3.9-alpha for Windows.
17343 - A wide variety of new unit tests by Esteban Manchado Velázquez.
17344 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
17345 - Update to the March 6 2012 Maxmind GeoLite Country database.
17348 Changes in version 0.2.3.12-alpha - 2012-02-13
17349 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
17350 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
17351 when Tor is configured to use a pluggable transport like obfsproxy.
17354 - Fix builds when the path to sed, openssl, or sha1sum contains
17355 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
17357 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
17358 connections. This change should allow busy exit relays to stop
17359 running out of available sockets as quickly. Fixes bug 4950;
17360 bugfix on 0.2.2.26-beta.
17361 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
17362 would ask the bridge for microdescriptors, which are only supported
17363 in 0.2.3.x, and then fail to bootstrap when it didn't get the
17364 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
17365 - Properly set up obfsproxy's environment when in managed mode. The
17366 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
17367 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
17368 5076 and 5082; bugfix on 0.2.3.6-alpha.
17371 - Use the dead_strip option when building Tor on OS X. This reduces
17372 binary size by almost 19% when linking openssl and libevent
17373 statically, which we do for Tor Browser Bundle.
17374 - Fix broken URLs in the sample torrc file, and tell readers about
17375 the OutboundBindAddress, ExitPolicyRejectPrivate, and
17376 PublishServerDescriptor options. Addresses bug 4652.
17377 - Update to the February 7 2012 Maxmind GeoLite Country database.
17380 - Downgrade the "We're missing a certificate" message from notice
17381 to info: people kept mistaking it for a real problem, whereas it
17382 is seldom the problem even when we are failing to bootstrap. Fixes
17383 bug 5067; bugfix on 0.2.0.10-alpha.
17384 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
17385 managed pluggable transport server proxy's environment.
17386 Previously, we would put it there, even though Tor doesn't
17387 implement an 'extended server port' yet, and even though Tor
17388 almost certainly isn't listening at that address. For now, we set
17389 it to an empty string to avoid crashing older obfsproxies. Bugfix
17391 - Log the heartbeat message every HeartbeatPeriod seconds, not every
17392 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
17393 0.2.3.1-alpha. Bug reported by Scott Bennett.
17394 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
17395 bugfix on 0.2.3.11-alpha.
17396 - Update "ClientOnly" man page entry to explain that there isn't
17397 really any point to messing with it. Resolves ticket 5005.
17398 - Use the correct CVE number for CVE-2011-4576 in our comments and
17399 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
17402 o Code simplifications and refactoring:
17403 - Use the _WIN32 macro throughout our code to detect Windows.
17404 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
17408 Changes in version 0.2.3.11-alpha - 2012-01-22
17409 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
17410 the last step of the plan to limit maximum circuit length, includes
17411 a wide variety of hidden service performance and correctness fixes,
17412 works around an OpenSSL security flaw if your distro is too stubborn
17413 to upgrade, and fixes a bunch of smaller issues.
17416 - Now that Tor 0.2.0.x is completely deprecated, enable the final
17417 part of "Proposal 110: Avoiding infinite length circuits" by
17418 refusing all circuit-extend requests that do not use a relay_early
17419 cell. This change helps Tor resist a class of denial-of-service
17420 attacks by limiting the maximum circuit length.
17421 - Adjust the number of introduction points that a hidden service
17422 will try to maintain based on how long its introduction points
17423 remain in use and how many introductions they handle. Fixes
17425 - Try to use system facilities for enumerating local interface
17426 addresses, before falling back to our old approach (which was
17427 binding a UDP socket, and calling getsockname() on it). That
17428 approach was scaring OS X users whose draconian firewall
17429 software warned about binding to UDP sockets, regardless of
17430 whether packets were sent. Now we try to use getifaddrs(),
17431 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
17432 system supports. Resolves ticket 1827.
17434 o Major security workaround:
17435 - When building or running with any version of OpenSSL earlier
17436 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
17437 versions have a bug (CVE-2011-4576) in which their block cipher
17438 padding includes uninitialized data, potentially leaking sensitive
17439 information to any peer with whom they make a SSLv3 connection. Tor
17440 does not use SSL v3 by default, but a hostile client or server
17441 could force an SSLv3 connection in order to gain information that
17442 they shouldn't have been able to get. The best solution here is to
17443 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
17444 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
17445 to make sure that the bug can't happen.
17448 - Fix the SOCKET_OK test that we use to tell when socket
17449 creation fails so that it works on Win64. Fixes part of bug 4533;
17450 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
17451 - Correct our replacements for the timeradd() and timersub() functions
17452 on platforms that lack them (for example, Windows). The timersub()
17453 function is used when expiring circuits, while timeradd() is
17454 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
17455 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
17456 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
17457 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
17458 bug at runtime, not compile time, because some distributions hack
17459 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
17460 on 0.2.3.9-alpha. Found by Pascal.
17462 o Minor features (controller):
17463 - Use absolute path names when reporting the torrc filename in the
17464 control protocol, so a controller can more easily find the torrc
17465 file. Resolves bug 1101.
17466 - Extend the control protocol to report flags that control a circuit's
17467 path selection in CIRC events and in replies to 'GETINFO
17468 circuit-status'. Implements part of ticket 2411.
17469 - Extend the control protocol to report the hidden service address
17470 and current state of a hidden-service-related circuit in CIRC
17471 events and in replies to 'GETINFO circuit-status'. Implements part
17473 - When reporting the path to the cookie file to the controller,
17474 give an absolute path. Resolves ticket 4881.
17475 - Allow controllers to request an event notification whenever a
17476 circuit is cannibalized or its purpose is changed. Implements
17477 part of ticket 3457.
17478 - Include the creation time of a circuit in CIRC and CIRC2
17479 control-port events and the list produced by the 'GETINFO
17480 circuit-status' control-port command.
17482 o Minor features (directory authorities):
17483 - Directory authorities now reject versions of Tor older than
17484 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
17485 inclusive. These versions accounted for only a small fraction of
17486 the Tor network, and have numerous known security issues. Resolves
17488 - Authority operators can now vote for all relays in a given
17489 set of countries to be BadDir/BadExit/Invalid/Rejected.
17490 - Provide two consensus parameters (FastFlagMinThreshold and
17491 FastFlagMaxThreshold) to control the range of allowable bandwidths
17492 for the Fast directory flag. These allow authorities to run
17493 experiments on appropriate requirements for being a "Fast" node.
17494 The AuthDirFastGuarantee config value still applies. Implements
17496 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
17497 directory authority option (introduced in Tor 0.2.2.34).
17499 o Minor features (other):
17500 - Don't disable the DirPort when we cannot exceed our AccountingMax
17501 limit during this interval because the effective bandwidthrate is
17502 low enough. This is useful in a situation where AccountMax is only
17503 used as an additional safeguard or to provide statistics.
17504 - Prepend an informative header to generated dynamic_dh_params files.
17505 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
17506 EntryNodes will have no effect. Resolves issue 2571.
17507 - Log more useful messages when we fail to disable debugger
17509 - Log which authority we're missing votes from when we go to fetch
17510 them from the other auths.
17511 - Log (at debug level) whenever a circuit's purpose is changed.
17512 - Add missing documentation for the MaxClientCircuitsPending,
17513 UseMicrodescriptors, UserspaceIOCPBuffers, and
17514 _UseFilteringSSLBufferevents options, all introduced during
17515 the 0.2.3.x series.
17516 - Update to the January 3 2012 Maxmind GeoLite Country database.
17518 o Minor bugfixes (hidden services):
17519 - Don't close hidden service client circuits which have almost
17520 finished connecting to their destination when they reach
17521 the normal circuit-build timeout. Previously, we would close
17522 introduction circuits which are waiting for an acknowledgement
17523 from the introduction point, and rendezvous circuits which have
17524 been specified in an INTRODUCE1 cell sent to a hidden service,
17525 after the normal CBT. Now, we mark them as 'timed out', and launch
17526 another rendezvous attempt in parallel. This behavior change can
17527 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
17528 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
17529 - Don't close hidden-service-side rendezvous circuits when they
17530 reach the normal circuit-build timeout. This behavior change can
17531 be disabled using the new
17532 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
17533 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
17534 - Make sure we never mark the wrong rendezvous circuit as having
17535 had its introduction cell acknowledged by the introduction-point
17536 relay. Previously, when we received an INTRODUCE_ACK cell on a
17537 client-side hidden-service introduction circuit, we might have
17538 marked a rendezvous circuit other than the one we specified in
17539 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
17540 a warning message and interfered with the hidden service
17541 connection-establishment process. Fixes bug 4759; bugfix on
17542 0.2.3.3-alpha, when we added the stream-isolation feature which
17543 might cause Tor to open multiple rendezvous circuits for the same
17545 - Don't trigger an assertion failure when we mark a new client-side
17546 hidden-service introduction circuit for close during the process
17547 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
17550 o Minor bugfixes (log messages):
17551 - Correctly spell "connect" in a log message on failure to create a
17552 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
17554 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
17555 Fixes bug 4856; bugfix on Tor 0.0.6.
17556 - Fix the log message describing how we work around discovering
17557 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
17558 4837; bugfix on 0.2.2.9-alpha.
17559 - When logging about a disallowed .exit name, do not also call it
17560 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
17562 o Minor bugfixes (build fixes):
17563 - During configure, detect when we're building with clang version
17564 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
17565 CFLAGS. clang doesn't support them yet.
17566 - During configure, search for library containing cos function as
17567 libm lives in libcore on some platforms (BeOS/Haiku). Linking
17568 against libm was hard-coded before. Fixes the first part of bug
17569 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
17571 - Detect attempts to build Tor on (as yet hypothetical) versions
17572 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
17573 fix for bug 4533. Bugfix on 0.2.2.28-beta.
17574 - Preprocessor directives should not be put inside the arguments
17575 of a macro. This would break compilation with GCC releases prior
17576 to version 3.3. We would never recommend such an old GCC version,
17577 but it is apparently required for binary compatibility on some
17578 platforms (namely, certain builds of Haiku). Fixes the other part
17579 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
17582 o Minor bugfixes (other):
17583 - Older Linux kernels erroneously respond to strange nmap behavior
17584 by having accept() return successfully with a zero-length
17585 socket. When this happens, just close the connection. Previously,
17586 we would try harder to learn the remote address: but there was
17587 no such remote address to learn, and our method for trying to
17588 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
17589 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
17590 - Fix null-pointer access that could occur if TLS allocation failed.
17591 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
17592 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
17593 accidentally been reverted.
17594 - Fix our implementation of crypto_random_hostname() so it can't
17595 overflow on ridiculously large inputs. (No Tor version has ever
17596 provided this kind of bad inputs, but let's be correct in depth.)
17597 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
17598 - Find more places in the code that should have been testing for
17599 invalid sockets using the SOCKET_OK macro. Required for a fix
17600 for bug 4533. Bugfix on 0.2.2.28-beta.
17601 - Fix an assertion failure when, while running with bufferevents, a
17602 connection finishes connecting after it is marked for close, but
17603 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
17604 - test_util_spawn_background_ok() hardcoded the expected value
17605 for ENOENT to 2. This isn't portable as error numbers are
17606 platform specific, and particularly the hurd has ENOENT at
17607 0x40000002. Construct expected string at runtime, using the correct
17608 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
17609 - Reject attempts to disable DisableDebuggerAttachment while Tor is
17610 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
17611 - Use an appropriate-width type for sockets in tor-fw-helper on
17612 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
17615 - When sending or relaying a RELAY_EARLY cell, we used to convert
17616 it to a RELAY cell if the connection was using the v1 link
17617 protocol. This was a workaround for older versions of Tor, which
17618 didn't handle RELAY_EARLY cells properly. Now that all supported
17619 versions can handle RELAY_EARLY cells, and now that we're enforcing
17620 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
17621 remove this workaround. Addresses bug 4786.
17623 o Code simplifications and refactoring:
17624 - Use OpenSSL's built-in SSL_state_string_long() instead of our
17625 own homebrewed ssl_state_to_string() replacement. Patch from
17626 Emile Snyder. Fixes bug 4653.
17627 - Use macros to indicate OpenSSL versions, so we don't need to worry
17628 about accidental hexadecimal bit shifts.
17629 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
17631 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
17632 - Use the smartlist_add_asprintf() alias more consistently.
17633 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
17634 invalid value, rather than just -1.
17635 - Rename a handful of old identifiers, mostly related to crypto
17636 structures and crypto functions. By convention, our "create an
17637 object" functions are called "type_new()", our "free an object"
17638 functions are called "type_free()", and our types indicate that
17639 they are types only with a final "_t". But a handful of older
17640 types and functions broke these rules, with function names like
17641 "type_create" or "subsystem_op_type", or with type names like
17645 Changes in version 0.2.3.10-alpha - 2011-12-16
17646 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
17647 Tor's buffers code. Absolutely everybody should upgrade.
17649 The bug relied on an incorrect calculation when making data continuous
17650 in one of our IO buffers, if the first chunk of the buffer was
17651 misaligned by just the wrong amount. The miscalculation would allow an
17652 attacker to overflow a piece of heap-allocated memory. To mount this
17653 attack, the attacker would need to either open a SOCKS connection to
17654 Tor's SocksPort (usually restricted to localhost), or target a Tor
17655 instance configured to make its connections through a SOCKS proxy
17656 (which Tor does not do by default).
17658 Good security practice requires that all heap-overflow bugs should be
17659 presumed to be exploitable until proven otherwise, so we are treating
17660 this as a potential code execution attack. Please upgrade immediately!
17661 This bug does not affect bufferevents-based builds of Tor. Special
17662 thanks to "Vektor" for reporting this issue to us!
17664 This release also contains a few minor bugfixes for issues discovered
17668 - Fix a heap overflow bug that could occur when trying to pull
17669 data into the first chunk of a buffer, when that chunk had
17670 already had some data drained from it. Fixes CVE-2011-2778;
17671 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
17674 - If we can't attach streams to a rendezvous circuit when we
17675 finish connecting to a hidden service, clear the rendezvous
17676 circuit's stream-isolation state and try to attach streams
17677 again. Previously, we cleared rendezvous circuits' isolation
17678 state either too early (if they were freshly built) or not at all
17679 (if they had been built earlier and were cannibalized). Bugfix on
17680 0.2.3.3-alpha; fixes bug 4655.
17681 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
17682 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
17683 - Fix an assertion failure when a relay with accounting enabled
17684 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
17687 - Update to the December 6 2011 Maxmind GeoLite Country database.
17690 Changes in version 0.2.2.35 - 2011-12-16
17691 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
17692 buffers code. Absolutely everybody should upgrade.
17694 The bug relied on an incorrect calculation when making data continuous
17695 in one of our IO buffers, if the first chunk of the buffer was
17696 misaligned by just the wrong amount. The miscalculation would allow an
17697 attacker to overflow a piece of heap-allocated memory. To mount this
17698 attack, the attacker would need to either open a SOCKS connection to
17699 Tor's SocksPort (usually restricted to localhost), or target a Tor
17700 instance configured to make its connections through a SOCKS proxy
17701 (which Tor does not do by default).
17703 Good security practice requires that all heap-overflow bugs should be
17704 presumed to be exploitable until proven otherwise, so we are treating
17705 this as a potential code execution attack. Please upgrade immediately!
17706 This bug does not affect bufferevents-based builds of Tor. Special
17707 thanks to "Vektor" for reporting this issue to us!
17709 Tor 0.2.2.35 also fixes several bugs in previous versions, including
17710 crash bugs for unusual configurations, and a long-term bug that
17711 would prevent Tor from starting on Windows machines with draconian
17714 With this release, we remind everyone that 0.2.0.x has reached its
17715 formal end-of-life. Those Tor versions have many known flaws, and
17716 nobody should be using them. You should upgrade -- ideally to the
17717 0.2.2.x series. If you're using a Linux or BSD and its packages are
17718 obsolete, stop using those packages and upgrade anyway.
17720 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
17721 longer receive support after some time in early 2012.
17724 - Fix a heap overflow bug that could occur when trying to pull
17725 data into the first chunk of a buffer, when that chunk had
17726 already had some data drained from it. Fixes CVE-2011-2778;
17727 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
17728 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
17729 that it doesn't attempt to allocate a socketpair. This could cause
17730 some problems on Windows systems with overzealous firewalls. Fix for
17731 bug 4457; workaround for Libevent versions 2.0.1-alpha through
17733 - If we mark an OR connection for close based on a cell we process,
17734 don't process any further cells on it. We already avoid further
17735 reads on marked-for-close connections, but now we also discard the
17736 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
17737 which was the first version where we might mark a connection for
17738 close based on processing a cell on it.
17739 - Correctly sanity-check that we don't underflow on a memory
17740 allocation (and then assert) for hidden service introduction
17741 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
17742 bugfix on 0.2.1.5-alpha.
17743 - Fix a memory leak when we check whether a hidden service
17744 descriptor has any usable introduction points left. Fixes bug
17745 4424. Bugfix on 0.2.2.25-alpha.
17746 - Don't crash when we're running as a relay and don't have a GeoIP
17747 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
17748 we've had in the 0.2.3.x branch already.
17749 - When running as a client, do not print a misleading (and plain
17750 wrong) log message that we're collecting "directory request"
17751 statistics: clients don't collect statistics. Also don't create a
17752 useless (because empty) stats file in the stats/ directory. Fixes
17753 bug 4353; bugfix on 0.2.2.34.
17756 - Detect failure to initialize Libevent. This fix provides better
17757 detection for future instances of bug 4457.
17758 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
17759 function. This was eating up hideously large amounts of time on some
17760 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
17761 - Resolve an integer overflow bug in smartlist_ensure_capacity().
17762 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
17764 - Don't warn about unused log_mutex in log.c when building with
17765 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
17766 0.1.0.6-rc which introduced --disable-threads.
17767 - When configuring, starting, or stopping an NT service, stop
17768 immediately after the service configuration attempt has succeeded
17769 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
17770 - When sending a NETINFO cell, include the original address
17771 received for the other side, not its canonical address. Found
17772 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
17773 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
17774 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
17775 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
17776 occurred when a client tried to fetch a descriptor for a bridge
17777 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
17778 - Backport fixes for a pair of compilation warnings on Windows.
17779 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
17780 - If we had ever tried to call tor_addr_to_str on an address of
17781 unknown type, we would have done a strdup on an uninitialized
17782 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
17783 Reported by "troll_un".
17784 - Correctly detect and handle transient lookup failures from
17785 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
17786 Reported by "troll_un".
17787 - Fix null-pointer access that could occur if TLS allocation failed.
17788 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
17789 - Use tor_socket_t type for listener argument to accept(). Fixes bug
17790 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
17793 - Add two new config options for directory authorities:
17794 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
17795 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
17796 that is always sufficient to satisfy the bandwidth requirement for
17797 the Guard flag. Now it will be easier for researchers to simulate
17798 Tor networks with different values. Resolves ticket 4484.
17799 - When Tor ignores a hidden service specified in its configuration,
17800 include the hidden service's directory in the warning message.
17801 Previously, we would only tell the user that some hidden service
17802 was ignored. Bugfix on 0.0.6; fixes bug 4426.
17803 - Update to the December 6 2011 Maxmind GeoLite Country database.
17805 o Packaging changes:
17806 - Make it easier to automate expert package builds on Windows,
17807 by removing an absolute path from makensis.exe command.
17810 Changes in version 0.2.1.32 - 2011-12-16
17811 Tor 0.2.1.32 backports important security and privacy fixes for
17812 oldstable. This release is intended only for package maintainers and
17813 others who cannot use the 0.2.2 stable series. All others should be
17814 using Tor 0.2.2.x or newer.
17816 The Tor 0.2.1.x series will reach formal end-of-life some time in
17817 early 2012; we will stop releasing patches for it then.
17819 o Major bugfixes (also included in 0.2.2.x):
17820 - Correctly sanity-check that we don't underflow on a memory
17821 allocation (and then assert) for hidden service introduction
17822 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
17823 bugfix on 0.2.1.5-alpha.
17824 - Fix a heap overflow bug that could occur when trying to pull
17825 data into the first chunk of a buffer, when that chunk had
17826 already had some data drained from it. Fixes CVE-2011-2778;
17827 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
17830 - Update to the December 6 2011 Maxmind GeoLite Country database.
17833 Changes in version 0.2.3.9-alpha - 2011-12-08
17834 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
17835 a "DisableNetwork" security feature that bundles can use to avoid
17836 touching the network until bridges are configured, moves forward on
17837 the pluggable transport design, fixes a flaw in the hidden service
17838 design that unnecessarily prevented clients with wrong clocks from
17839 reaching hidden services, and fixes a wide variety of other issues.
17842 - Clients can now connect to private bridges over IPv6. Bridges
17843 still need at least one IPv4 address in order to connect to
17844 other relays. Note that we don't yet handle the case where the
17845 user has two bridge lines for the same bridge (one IPv4, one
17846 IPv6). Implements parts of proposal 186.
17847 - New "DisableNetwork" config option to prevent Tor from launching any
17848 connections or accepting any connections except on a control port.
17849 Bundles and controllers can set this option before letting Tor talk
17850 to the rest of the network, for example to prevent any connections
17851 to a non-bridge address. Packages like Orbot can also use this
17852 option to instruct Tor to save power when the network is off.
17853 - Clients and bridges can now be configured to use a separate
17854 "transport" proxy. This approach makes the censorship arms race
17855 easier by allowing bridges to use protocol obfuscation plugins. It
17856 implements the "managed proxy" part of proposal 180 (ticket 3472).
17857 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
17858 implementation. It makes AES_CTR about 7% faster than our old one
17859 (which was about 10% faster than the one OpenSSL used to provide).
17860 Resolves ticket 4526.
17861 - Add a "tor2web mode" for clients that want to connect to hidden
17862 services non-anonymously (and possibly more quickly). As a safety
17863 measure to try to keep users from turning this on without knowing
17864 what they are doing, tor2web mode must be explicitly enabled at
17865 compile time, and a copy of Tor compiled to run in tor2web mode
17866 cannot be used as a normal Tor client. Implements feature 2553.
17867 - Add experimental support for running on Windows with IOCP and no
17868 kernel-space socket buffers. This feature is controlled by a new
17869 "UserspaceIOCPBuffers" config option (off by default), which has
17870 no effect unless Tor has been built with support for bufferevents,
17871 is running on Windows, and has enabled IOCP. This may, in the long
17872 run, help solve or mitigate bug 98.
17873 - Use a more secure consensus parameter voting algorithm. Now at
17874 least three directory authorities or a majority of them must
17875 vote on a given parameter before it will be included in the
17876 consensus. Implements proposal 178.
17879 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
17880 They used to check that the timestamp was within 30 minutes
17881 of their system clock, so they could cap the size of their
17882 replay-detection cache, but that approach unnecessarily refused
17883 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
17884 the v3 intro-point protocol (the first one which sent a timestamp
17885 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
17886 - Only use the EVP interface when AES acceleration is enabled,
17887 to avoid a 5-7% performance regression. Resolves issue 4525;
17888 bugfix on 0.2.3.8-alpha.
17890 o Privacy/anonymity features (bridge detection):
17891 - Make bridge SSL certificates a bit more stealthy by using random
17892 serial numbers, in the same fashion as OpenSSL when generating
17893 self-signed certificates. Implements ticket 4584.
17894 - Introduce a new config option "DynamicDHGroups", enabled by
17895 default, which provides each bridge with a unique prime DH modulus
17896 to be used during SSL handshakes. This option attempts to help
17897 against censors who might use the Apache DH modulus as a static
17898 identifier for bridges. Addresses ticket 4548.
17900 o Minor features (new/different config options):
17901 - New configuration option "DisableDebuggerAttachment" (on by default)
17902 to prevent basic debugging attachment attempts by other processes.
17903 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
17904 - Allow MapAddress directives to specify matches against super-domains,
17905 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
17906 Implements issue 933.
17907 - Slightly change behavior of "list" options (that is, config
17908 options that can appear more than once) when they appear both in
17909 torrc and on the command line. Previously, the command-line options
17910 would be appended to the ones from torrc. Now, the command-line
17911 options override the torrc options entirely. This new behavior
17912 allows the user to override list options (like exit policies and
17913 ports to listen on) from the command line, rather than simply
17914 appending to the list.
17915 - You can get the old (appending) command-line behavior for "list"
17916 options by prefixing the option name with a "+".
17917 - You can remove all the values for a "list" option from the command
17918 line without adding any new ones by prefixing the option name
17920 - Add experimental support for a "defaults" torrc file to be parsed
17921 before the regular torrc. Torrc options override the defaults file's
17922 options in the same way that the command line overrides the torrc.
17923 The SAVECONF controller command saves only those options which
17924 differ between the current configuration and the defaults file. HUP
17925 reloads both files. (Note: This is an experimental feature; its
17926 behavior will probably be refined in future 0.2.3.x-alpha versions
17927 to better meet packagers' needs.) Implements task 4552.
17930 - Try to make the introductory warning message that Tor prints on
17931 startup more useful for actually finding help and information.
17932 Resolves ticket 2474.
17933 - Running "make version" now displays the version of Tor that
17934 we're about to build. Idea from katmagic; resolves issue 4400.
17935 - Expire old or over-used hidden service introduction points.
17936 Required by fix for bug 3460.
17937 - Move the replay-detection cache for the RSA-encrypted parts of
17938 INTRODUCE2 cells to the introduction point data structures.
17939 Previously, we would use one replay-detection cache per hidden
17940 service. Required by fix for bug 3460.
17941 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
17942 public key replay-detection cache from 60 minutes to 5 minutes. This
17943 replay-detection cache is now used only to detect multiple
17944 INTRODUCE2 cells specifying the same rendezvous point, so we can
17945 avoid launching multiple simultaneous attempts to connect to it.
17947 o Minor bugfixes (on Tor 0.2.2.x and earlier):
17948 - Resolve an integer overflow bug in smartlist_ensure_capacity().
17949 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
17951 - Fix a minor formatting issue in one of tor-gencert's error messages.
17953 - Prevent a false positive from the check-spaces script, by disabling
17954 the "whitespace between function name and (" check for functions
17956 - Fix a log message suggesting that people contact a non-existent
17957 email address. Fixes bug 3448.
17958 - Fix null-pointer access that could occur if TLS allocation failed.
17959 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
17960 - Report a real bootstrap problem to the controller on router
17961 identity mismatch. Previously we just said "foo", which probably
17962 made a lot of sense at the time. Fixes bug 4169; bugfix on
17964 - If we had ever tried to call tor_addr_to_str() on an address of
17965 unknown type, we would have done a strdup() on an uninitialized
17966 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
17967 Reported by "troll_un".
17968 - Correctly detect and handle transient lookup failures from
17969 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
17970 Reported by "troll_un".
17971 - Use tor_socket_t type for listener argument to accept(). Fixes bug
17972 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
17973 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
17974 bug 4532; found by "troll_un".
17976 o Minor bugfixes (on Tor 0.2.3.x):
17977 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
17979 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
17980 circuit for use as a hidden service client's rendezvous point.
17981 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
17982 with help from wanoskarnet.
17983 - Restore behavior of overriding SocksPort, ORPort, and similar
17984 options from the command line. Bugfix on 0.2.3.3-alpha.
17987 - Properly handle the case where the build-tree is not the same
17988 as the source tree when generating src/common/common_sha1.i,
17989 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
17990 bugfix on 0.2.0.1-alpha.
17992 o Code simplifications, cleanups, and refactorings:
17993 - Remove the pure attribute from all functions that used it
17994 previously. In many cases we assigned it incorrectly, because the
17995 functions might assert or call impure functions, and we don't have
17996 evidence that keeping the pure attribute is worthwhile. Implements
17997 changes suggested in ticket 4421.
17998 - Remove some dead code spotted by coverity. Fixes cid 432.
17999 Bugfix on 0.2.3.1-alpha, closes bug 4637.
18002 Changes in version 0.2.3.8-alpha - 2011-11-22
18003 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
18004 socketpair-related bug that has been bothering Windows users. It adds
18005 support to serve microdescriptors to controllers, so Vidalia's network
18006 map can resume listing relays (once Vidalia implements its side),
18007 and adds better support for hardware AES acceleration. Finally, it
18008 starts the process of adjusting the bandwidth cutoff for getting the
18009 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
18010 that tiny relays harm performance more than they help network capacity.
18013 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
18014 that it doesn't attempt to allocate a socketpair. This could cause
18015 some problems on Windows systems with overzealous firewalls. Fix for
18016 bug 4457; workaround for Libevent versions 2.0.1-alpha through
18018 - Correctly sanity-check that we don't underflow on a memory
18019 allocation (and then assert) for hidden service introduction
18020 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
18021 bugfix on 0.2.1.5-alpha.
18022 - Remove the artificially low cutoff of 20KB to guarantee the Fast
18023 flag. In the past few years the average relay speed has picked
18024 up, and while the "top 7/8 of the network get the Fast flag" and
18025 "all relays with 20KB or more of capacity get the Fast flag" rules
18026 used to have the same result, now the top 7/8 of the network has
18027 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
18028 - Fix a rare assertion failure when checking whether a v0 hidden
18029 service descriptor has any usable introduction points left, and
18030 we don't have enough information to build a circuit to the first
18031 intro point named in the descriptor. The HS client code in
18032 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
18033 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
18034 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
18035 - Make bridge authorities not crash when they are asked for their own
18036 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
18037 - When running as a client, do not print a misleading (and plain
18038 wrong) log message that we're collecting "directory request"
18039 statistics: clients don't collect statistics. Also don't create a
18040 useless (because empty) stats file in the stats/ directory. Fixes
18041 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
18044 - Allow Tor controllers like Vidalia to obtain the microdescriptor
18045 for a relay by identity digest or nickname. Previously,
18046 microdescriptors were only available by their own digests, so a
18047 controller would have to ask for and parse the whole microdescriptor
18048 consensus in order to look up a single relay's microdesc. Fixes
18049 bug 3832; bugfix on 0.2.3.1-alpha.
18050 - Use OpenSSL's EVP interface for AES encryption, so that all AES
18051 operations can use hardware acceleration (if present). Resolves
18054 o Minor bugfixes (on 0.2.2.x and earlier):
18055 - Detect failure to initialize Libevent. This fix provides better
18056 detection for future instances of bug 4457.
18057 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
18058 function. This was eating up hideously large amounts of time on some
18059 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
18060 - Don't warn about unused log_mutex in log.c when building with
18061 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
18062 0.1.0.6-rc which introduced --disable-threads.
18063 - Allow manual 'authenticate' commands to the controller interface
18064 from netcat (nc) as well as telnet. We were rejecting them because
18065 they didn't come with the expected whitespace at the end of the
18066 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
18067 - Fix some (not actually triggerable) buffer size checks in usage of
18068 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
18070 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
18071 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
18072 - When configuring, starting, or stopping an NT service, stop
18073 immediately after the service configuration attempt has succeeded
18074 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
18075 - When sending a NETINFO cell, include the original address
18076 received for the other side, not its canonical address. Found
18077 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
18078 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
18079 can pick them up when the tests aren't disabled. Bugfix on
18080 0.2.2.4-alpha which introduced tinytest.
18081 - Fix a memory leak when we check whether a hidden service
18082 descriptor has any usable introduction points left. Fixes bug
18083 4424. Bugfix on 0.2.2.25-alpha.
18084 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
18085 occurred when a client tried to fetch a descriptor for a bridge
18086 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
18088 o Minor bugfixes (on 0.2.3.x):
18089 - Make util unit tests build correctly with MSVC. Bugfix on
18090 0.2.3.3-alpha. Patch by Gisle Vanem.
18091 - Successfully detect AUTH_CHALLENGE cells with no recognized
18092 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
18093 Found by frosty_un.
18094 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
18095 it should still send a NETINFO cell to allow the connection to
18096 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
18098 - Log less loudly when we get an invalid authentication certificate
18099 from a source other than a directory authority: it's not unusual
18100 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
18102 - Tolerate servers with more clock skew in their authentication
18103 certificates than previously. Fixes bug 4371; bugfix on
18105 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
18106 on 0.2.3.4-alpha and 0.2.3.6-alpha.
18109 - Add two new config options for directory authorities:
18110 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
18111 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
18112 that is always sufficient to satisfy the bandwidth requirement for
18113 the Guard flag. Now it will be easier for researchers to simulate
18114 Tor networks with different values. Resolves ticket 4484.
18115 - When Tor ignores a hidden service specified in its configuration,
18116 include the hidden service's directory in the warning message.
18117 Previously, we would only tell the user that some hidden service
18118 was ignored. Bugfix on 0.0.6; fixes bug 4426.
18119 - When we fail to initialize Libevent, retry with IOCP disabled so we
18120 don't need to turn on multi-threading support in Libevent, which in
18121 turn requires a working socketpair(). This is a workaround for bug
18122 4457, which affects Libevent versions from 2.0.1-alpha through
18124 - Detect when we try to build on a platform that doesn't define
18125 AF_UNSPEC to 0. We don't work there, so refuse to compile.
18126 - Update to the November 1 2011 Maxmind GeoLite Country database.
18128 o Packaging changes:
18129 - Make it easier to automate expert package builds on Windows,
18130 by removing an absolute path from makensis.exe command.
18132 o Code simplifications and refactoring:
18133 - Remove some redundant #include directives throughout the code.
18134 Patch from Andrea Gelmini.
18135 - Unconditionally use OpenSSL's AES implementation instead of our
18136 old built-in one. OpenSSL's AES has been better for a while, and
18137 relatively few servers should still be on any version of OpenSSL
18138 that doesn't have good optimized assembly AES.
18139 - Use the name "CERTS" consistently to refer to the new cell type;
18140 we were calling it CERT in some places and CERTS in others.
18143 - Numerous new unit tests for functions in util.c and address.c by
18145 - The long-disabled benchmark tests are now split into their own
18146 ./src/test/bench binary.
18147 - The benchmark tests can now use more accurate timers than
18148 gettimeofday() when such timers are available.
18151 Changes in version 0.2.3.7-alpha - 2011-10-30
18152 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
18153 the new v3 handshake. It also resolves yet another bridge address
18157 - If we mark an OR connection for close based on a cell we process,
18158 don't process any further cells on it. We already avoid further
18159 reads on marked-for-close connections, but now we also discard the
18160 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
18161 which was the first version where we might mark a connection for
18162 close based on processing a cell on it.
18163 - Fix a double-free bug that would occur when we received an invalid
18164 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
18165 bugfix on 0.2.3.6-alpha.
18166 - Bridges no longer include their address in NETINFO cells on outgoing
18167 OR connections, to allow them to blend in better with clients.
18168 Removes another avenue for enumerating bridges. Reported by
18169 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
18170 cells were introduced.
18173 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
18174 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
18177 Changes in version 0.2.3.6-alpha - 2011-10-26
18178 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
18179 anonymity vulnerability where an attacker can deanonymize Tor
18180 users. Everybody should upgrade.
18182 This release also features support for a new v3 connection handshake
18183 protocol, and fixes to make hidden service connections more robust.
18186 - Implement a new handshake protocol (v3) for authenticating Tors to
18187 each other over TLS. It should be more resistant to fingerprinting
18188 than previous protocols, and should require less TLS hacking for
18189 future Tor implementations. Implements proposal 176.
18190 - Allow variable-length padding cells to disguise the length of
18191 Tor's TLS records. Implements part of proposal 184.
18193 o Privacy/anonymity fixes (clients):
18194 - Clients and bridges no longer send TLS certificate chains on
18195 outgoing OR connections. Previously, each client or bridge would
18196 use the same cert chain for all outgoing OR connections until
18197 its IP address changes, which allowed any relay that the client
18198 or bridge contacted to determine which entry guards it is using.
18199 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
18200 - If a relay receives a CREATE_FAST cell on a TLS connection, it
18201 no longer considers that connection as suitable for satisfying a
18202 circuit EXTEND request. Now relays can protect clients from the
18203 CVE-2011-2768 issue even if the clients haven't upgraded yet.
18204 - Directory authorities no longer assign the Guard flag to relays
18205 that haven't upgraded to the above "refuse EXTEND requests
18206 to client connections" fix. Now directory authorities can
18207 protect clients from the CVE-2011-2768 issue even if neither
18208 the clients nor the relays have upgraded yet. There's a new
18209 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
18210 to let us transition smoothly, else tomorrow there would be no
18213 o Major bugfixes (hidden services):
18214 - Improve hidden service robustness: when an attempt to connect to
18215 a hidden service ends, be willing to refetch its hidden service
18216 descriptors from each of the HSDir relays responsible for them
18217 immediately. Previously, we would not consider refetching the
18218 service's descriptors from each HSDir for 15 minutes after the last
18219 fetch, which was inconvenient if the hidden service was not running
18220 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
18221 - When one of a hidden service's introduction points appears to be
18222 unreachable, stop trying it. Previously, we would keep trying
18223 to build circuits to the introduction point until we lost the
18224 descriptor, usually because the user gave up and restarted Tor.
18225 Partly fixes bug 3825.
18226 - Don't launch a useless circuit after failing to use one of a
18227 hidden service's introduction points. Previously, we would
18228 launch a new introduction circuit, but not set the hidden service
18229 which that circuit was intended to connect to, so it would never
18230 actually be used. A different piece of code would then create a
18231 new introduction circuit correctly. Bug reported by katmagic and
18232 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
18234 o Major bugfixes (other):
18235 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
18236 that they initiated. Relays could distinguish incoming bridge
18237 connections from client connections, creating another avenue for
18238 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
18239 Found by "frosty_un".
18240 - Don't update the AccountingSoftLimitHitAt state file entry whenever
18241 tor gets started. This prevents a wrong average bandwidth
18242 estimate, which would cause relays to always start a new accounting
18243 interval at the earliest possible moment. Fixes bug 2003; bugfix
18244 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
18245 immensely in tracking this bug down.
18246 - Fix a crash bug when changing node restrictions while a DNS lookup
18247 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
18250 o Minor bugfixes (on 0.2.2.x and earlier):
18251 - When a hidden service turns an extra service-side introduction
18252 circuit into a general-purpose circuit, free the rend_data and
18253 intro_key fields first, so we won't leak memory if the circuit
18254 is cannibalized for use as another service-side introduction
18255 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
18256 - Rephrase the log message emitted if the TestSocks check is
18257 successful. Patch from Fabian Keil; fixes bug 4094.
18258 - Bridges now skip DNS self-tests, to act a little more stealthily.
18259 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
18260 bridges. Patch by "warms0x".
18261 - Remove a confusing dollar sign from the example fingerprint in the
18262 man page, and also make the example fingerprint a valid one. Fixes
18263 bug 4309; bugfix on 0.2.1.3-alpha.
18264 - Fix internal bug-checking logic that was supposed to catch
18265 failures in digest generation so that it will fail more robustly
18266 if we ask for a nonexistent algorithm. Found by Coverity Scan.
18267 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
18268 - Report any failure in init_keys() calls launched because our
18269 IP address has changed. Spotted by Coverity Scan. Bugfix on
18270 0.1.1.4-alpha; fixes CID 484.
18272 o Minor bugfixes (on 0.2.3.x):
18273 - Fix a bug in configure.in that kept it from building a configure
18274 script with autoconf versions earlier than 2.61. Fixes bug 2430;
18275 bugfix on 0.2.3.1-alpha.
18276 - Don't warn users that they are exposing a client port to the
18277 Internet if they have specified an RFC1918 address. Previously,
18278 we would warn if the user had specified any non-loopback
18279 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
18280 - Fix memory leaks in the failing cases of the new SocksPort and
18281 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
18282 fixes coverity CIDs 485, 486, and 487.
18285 - When a hidden service's introduction point times out, consider
18286 trying it again during the next attempt to connect to the
18287 HS. Previously, we would not try it again unless a newly fetched
18288 descriptor contained it. Required by fixes for bugs 1297 and 3825.
18289 - The next version of Windows will be called Windows 8, and it has
18290 a major version of 6, minor version of 2. Correctly identify that
18291 version instead of calling it "Very recent version". Resolves
18292 ticket 4153; reported by funkstar.
18293 - The Bridge Authority now writes statistics on how many bridge
18294 descriptors it gave out in total, and how many unique descriptors
18295 it gave out. It also lists how often the most and least commonly
18296 fetched descriptors were given out, as well as the median and
18297 25th/75th percentile. Implements tickets 4200 and 4294.
18298 - Update to the October 4 2011 Maxmind GeoLite Country database.
18300 o Code simplifications and refactoring:
18301 - Remove some old code to remember statistics about which descriptors
18302 we've served as a directory mirror. The feature wasn't used and
18303 is outdated now that microdescriptors are around.
18304 - Rename Tor functions that turn strings into addresses, so that
18305 "parse" indicates that no hostname resolution occurs, and
18306 "lookup" indicates that hostname resolution may occur. This
18307 should help prevent mistakes in the future. Fixes bug 3512.
18310 Changes in version 0.2.2.34 - 2011-10-26
18311 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
18312 can deanonymize Tor users. Everybody should upgrade.
18314 The attack relies on four components: 1) Clients reuse their TLS cert
18315 when talking to different relays, so relays can recognize a user by
18316 the identity key in her cert. 2) An attacker who knows the client's
18317 identity key can probe each guard relay to see if that identity key
18318 is connected to that guard relay right now. 3) A variety of active
18319 attacks in the literature (starting from "Low-Cost Traffic Analysis
18320 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
18321 discover the guard relays that a Tor user visiting the website is using.
18322 4) Clients typically pick three guards at random, so the set of guards
18323 for a given user could well be a unique fingerprint for her. This
18324 release fixes components #1 and #2, which is enough to block the attack;
18325 the other two remain as open research problems. Special thanks to
18326 "frosty_un" for reporting the issue to us!
18328 Clients should upgrade so they are no longer recognizable by the TLS
18329 certs they present. Relays should upgrade so they no longer allow a
18330 remote attacker to probe them to test whether unpatched clients are
18331 currently connected to them.
18333 This release also fixes several vulnerabilities that allow an attacker
18334 to enumerate bridge relays. Some bridge enumeration attacks still
18335 remain; see for example proposal 188.
18337 o Privacy/anonymity fixes (clients):
18338 - Clients and bridges no longer send TLS certificate chains on
18339 outgoing OR connections. Previously, each client or bridge would
18340 use the same cert chain for all outgoing OR connections until
18341 its IP address changes, which allowed any relay that the client
18342 or bridge contacted to determine which entry guards it is using.
18343 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
18344 - If a relay receives a CREATE_FAST cell on a TLS connection, it
18345 no longer considers that connection as suitable for satisfying a
18346 circuit EXTEND request. Now relays can protect clients from the
18347 CVE-2011-2768 issue even if the clients haven't upgraded yet.
18348 - Directory authorities no longer assign the Guard flag to relays
18349 that haven't upgraded to the above "refuse EXTEND requests
18350 to client connections" fix. Now directory authorities can
18351 protect clients from the CVE-2011-2768 issue even if neither
18352 the clients nor the relays have upgraded yet. There's a new
18353 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
18354 to let us transition smoothly, else tomorrow there would be no
18357 o Privacy/anonymity fixes (bridge enumeration):
18358 - Bridge relays now do their directory fetches inside Tor TLS
18359 connections, like all the other clients do, rather than connecting
18360 directly to the DirPort like public relays do. Removes another
18361 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
18362 - Bridges relays now build circuits for themselves in a more similar
18363 way to how clients build them. Removes another avenue for
18364 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
18365 when bridges were introduced.
18366 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
18367 that they initiated. Relays could distinguish incoming bridge
18368 connections from client connections, creating another avenue for
18369 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
18370 Found by "frosty_un".
18373 - Fix a crash bug when changing node restrictions while a DNS lookup
18374 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
18376 - Don't launch a useless circuit after failing to use one of a
18377 hidden service's introduction points. Previously, we would
18378 launch a new introduction circuit, but not set the hidden service
18379 which that circuit was intended to connect to, so it would never
18380 actually be used. A different piece of code would then create a
18381 new introduction circuit correctly. Bug reported by katmagic and
18382 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
18385 - Change an integer overflow check in the OpenBSD_Malloc code so
18386 that GCC is less likely to eliminate it as impossible. Patch
18387 from Mansour Moufid. Fixes bug 4059.
18388 - When a hidden service turns an extra service-side introduction
18389 circuit into a general-purpose circuit, free the rend_data and
18390 intro_key fields first, so we won't leak memory if the circuit
18391 is cannibalized for use as another service-side introduction
18392 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
18393 - Bridges now skip DNS self-tests, to act a little more stealthily.
18394 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
18395 bridges. Patch by "warms0x".
18396 - Fix internal bug-checking logic that was supposed to catch
18397 failures in digest generation so that it will fail more robustly
18398 if we ask for a nonexistent algorithm. Found by Coverity Scan.
18399 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
18400 - Report any failure in init_keys() calls launched because our
18401 IP address has changed. Spotted by Coverity Scan. Bugfix on
18402 0.1.1.4-alpha; fixes CID 484.
18404 o Minor bugfixes (log messages and documentation):
18405 - Remove a confusing dollar sign from the example fingerprint in the
18406 man page, and also make the example fingerprint a valid one. Fixes
18407 bug 4309; bugfix on 0.2.1.3-alpha.
18408 - The next version of Windows will be called Windows 8, and it has
18409 a major version of 6, minor version of 2. Correctly identify that
18410 version instead of calling it "Very recent version". Resolves
18411 ticket 4153; reported by funkstar.
18412 - Downgrade log messages about circuit timeout calibration from
18413 "notice" to "info": they don't require or suggest any human
18414 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
18415 bugfix on 0.2.2.14-alpha.
18418 - Turn on directory request statistics by default and include them in
18419 extra-info descriptors. Don't break if we have no GeoIP database.
18420 Backported from 0.2.3.1-alpha; implements ticket 3951.
18421 - Update to the October 4 2011 Maxmind GeoLite Country database.
18424 Changes in version 0.2.1.31 - 2011-10-26
18425 Tor 0.2.1.31 backports important security and privacy fixes for
18426 oldstable. This release is intended only for package maintainers and
18427 others who cannot use the 0.2.2 stable series. All others should be
18428 using Tor 0.2.2.x or newer.
18430 o Security fixes (also included in 0.2.2.x):
18431 - Replace all potentially sensitive memory comparison operations
18432 with versions whose runtime does not depend on the data being
18433 compared. This will help resist a class of attacks where an
18434 adversary can use variations in timing information to learn
18435 sensitive data. Fix for one case of bug 3122. (Safe memcmp
18436 implementation by Robert Ransom based partially on code by DJB.)
18437 - Fix an assert in parsing router descriptors containing IPv6
18438 addresses. This one took down the directory authorities when
18439 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
18441 o Privacy/anonymity fixes (also included in 0.2.2.x):
18442 - Clients and bridges no longer send TLS certificate chains on
18443 outgoing OR connections. Previously, each client or bridge would
18444 use the same cert chain for all outgoing OR connections until
18445 its IP address changes, which allowed any relay that the client
18446 or bridge contacted to determine which entry guards it is using.
18447 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
18448 - If a relay receives a CREATE_FAST cell on a TLS connection, it
18449 no longer considers that connection as suitable for satisfying a
18450 circuit EXTEND request. Now relays can protect clients from the
18451 CVE-2011-2768 issue even if the clients haven't upgraded yet.
18452 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
18453 that they initiated. Relays could distinguish incoming bridge
18454 connections from client connections, creating another avenue for
18455 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
18456 Found by "frosty_un".
18457 - When receiving a hidden service descriptor, check that it is for
18458 the hidden service we wanted. Previously, Tor would store any
18459 hidden service descriptors that a directory gave it, whether it
18460 wanted them or not. This wouldn't have let an attacker impersonate
18461 a hidden service, but it did let directories pre-seed a client
18462 with descriptors that it didn't want. Bugfix on 0.0.6.
18463 - Avoid linkability based on cached hidden service descriptors: forget
18464 all hidden service descriptors cached as a client when processing a
18465 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
18466 - Make the bridge directory authority refuse to answer directory
18467 requests for "all" descriptors. It used to include bridge
18468 descriptors in its answer, which was a major information leak.
18469 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
18470 - Don't attach new streams to old rendezvous circuits after SIGNAL
18471 NEWNYM. Previously, we would keep using an existing rendezvous
18472 circuit if it remained open (i.e. if it were kept open by a
18473 long-lived stream, or if a new stream were attached to it before
18474 Tor could notice that it was old and no longer in use). Bugfix on
18475 0.1.1.15-rc; fixes bug 3375.
18477 o Minor bugfixes (also included in 0.2.2.x):
18478 - When we restart our relay, we might get a successful connection
18479 from the outside before we've started our reachability tests,
18480 triggering a warning: "ORPort found reachable, but I have no
18481 routerinfo yet. Failing to inform controller of success." This
18482 bug was harmless unless Tor is running under a controller
18483 like Vidalia, in which case the controller would never get a
18484 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
18486 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
18487 enabled. Fixes bug 1526.
18488 - Remove undocumented option "-F" from tor-resolve: it hasn't done
18489 anything since 0.2.1.16-rc.
18490 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
18491 None of the cases where we did this before were wrong, but by making
18492 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
18493 - Fix a rare crash bug that could occur when a client was configured
18494 with a large number of bridges. Fixes bug 2629; bugfix on
18495 0.2.1.2-alpha. Bugfix by trac user "shitlei".
18496 - Correct the warning displayed when a rendezvous descriptor exceeds
18497 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
18499 - Fix an uncommon assertion failure when running with DNSPort under
18500 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
18501 - When warning about missing zlib development packages during compile,
18502 give the correct package names. Bugfix on 0.2.0.1-alpha.
18503 - Require that introduction point keys and onion keys have public
18504 exponent 65537. Bugfix on 0.2.0.10-alpha.
18505 - Do not crash when our configuration file becomes unreadable, for
18506 example due to a permissions change, between when we start up
18507 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
18509 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
18511 - Always NUL-terminate the sun_path field of a sockaddr_un before
18512 passing it to the kernel. (Not a security issue: kernels are
18513 smart enough to reject bad sockaddr_uns.) Found by Coverity;
18514 CID #428. Bugfix on Tor 0.2.0.3-alpha.
18515 - Don't stack-allocate the list of supplementary GIDs when we're
18516 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
18517 could take up to 256K, which is way too much stack. Found by
18518 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
18520 o Minor bugfixes (only in 0.2.1.x):
18521 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
18522 rely on them. Bugfix on 0.2.1.30.
18523 - Use git revisions instead of svn revisions when generating our
18524 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
18526 o Minor features (also included in 0.2.2.x):
18527 - Adjust the expiration time on our SSL session certificates to
18528 better match SSL certs seen in the wild. Resolves ticket 4014.
18529 - Allow nameservers with IPv6 address. Resolves bug 2574.
18530 - Update to the October 4 2011 Maxmind GeoLite Country database.
18533 Changes in version 0.2.3.5-alpha - 2011-09-28
18534 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
18535 bridge relays; fixes an assertion error that many users started hitting
18536 today; and adds the ability to refill token buckets more often than
18537 once per second, allowing significant performance improvements.
18540 - Bridge relays now do their directory fetches inside Tor TLS
18541 connections, like all the other clients do, rather than connecting
18542 directly to the DirPort like public relays do. Removes another
18543 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
18544 - Bridges relays now build circuits for themselves in a more similar
18545 way to how clients build them. Removes another avenue for
18546 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
18547 when bridges were introduced.
18550 - Fix an "Assertion md->held_by_node == 1 failed" error that could
18551 occur when the same microdescriptor was referenced by two node_t
18552 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
18554 o Major features (networking):
18555 - Add a new TokenBucketRefillInterval option to refill token buckets
18556 more frequently than once per second. This should improve network
18557 performance, alleviate queueing problems, and make traffic less
18558 bursty. Implements proposal 183; closes ticket 3630. Design by
18559 Florian Tschorsch and Björn Scheuermann; implementation by
18563 - Change an integer overflow check in the OpenBSD_Malloc code so
18564 that GCC is less likely to eliminate it as impossible. Patch
18565 from Mansour Moufid. Fixes bug 4059.
18567 o Minor bugfixes (usability):
18568 - Downgrade log messages about circuit timeout calibration from
18569 "notice" to "info": they don't require or suggest any human
18570 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
18571 bugfix on 0.2.2.14-alpha.
18573 o Minor features (diagnostics):
18574 - When the system call to create a listener socket fails, log the
18575 error message explaining why. This may help diagnose bug 4027.
18578 Changes in version 0.2.3.4-alpha - 2011-09-13
18579 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
18580 tweak to Tor's TLS handshake that makes relays and bridges that run
18581 this new version reachable from Iran again. It also fixes a few new
18582 bugs in 0.2.3.x, and teaches relays to recognize when they're not
18583 listed in the network consensus and republish.
18585 o Major bugfixes (also part of 0.2.2.33):
18586 - Avoid an assertion failure when reloading a configuration with
18587 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
18588 3923; bugfix on 0.2.2.25-alpha.
18590 o Minor features (security, also part of 0.2.2.33):
18591 - Check for replays of the public-key encrypted portion of an
18592 INTRODUCE1 cell, in addition to the current check for replays of
18593 the g^x value. This prevents a possible class of active attacks
18594 by an attacker who controls both an introduction point and a
18595 rendezvous point, and who uses the malleability of AES-CTR to
18596 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
18597 that these attacks are infeasible (requiring the attacker to send
18598 on the order of zettabytes of altered cells in a short interval),
18599 but we'd rather block them off in case there are any classes of
18600 this attack that we missed. Reported by Willem Pinckaers.
18602 o Minor features (also part of 0.2.2.33):
18603 - Adjust the expiration time on our SSL session certificates to
18604 better match SSL certs seen in the wild. Resolves ticket 4014.
18605 - Change the default required uptime for a relay to be accepted as
18606 a HSDir (hidden service directory) from 24 hours to 25 hours.
18607 Improves on 0.2.0.10-alpha; resolves ticket 2649.
18608 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
18609 authorities to abstain from voting on assignment of the HSDir
18610 consensus flag. Related to bug 2649.
18611 - Update to the September 6 2011 Maxmind GeoLite Country database.
18613 o Minor bugfixes (also part of 0.2.2.33):
18614 - Demote the 'replay detected' log message emitted when a hidden
18615 service receives the same Diffie-Hellman public key in two different
18616 INTRODUCE2 cells to info level. A normal Tor client can cause that
18617 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
18618 fixes part of bug 2442.
18619 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
18620 level. There is nothing that a hidden service's operator can do
18621 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
18623 - Clarify a log message specifying the characters permitted in
18624 HiddenServiceAuthorizeClient client names. Previously, the log
18625 message said that "[A-Za-z0-9+-_]" were permitted; that could have
18626 given the impression that every ASCII character between "+" and "_"
18627 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
18629 o Build fixes (also part of 0.2.2.33):
18630 - Clean up some code issues that prevented Tor from building on older
18631 BSDs. Fixes bug 3894; reported by "grarpamp".
18632 - Search for a platform-specific version of "ar" when cross-compiling.
18633 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
18636 - Fix a bug where the SocksPort option (for example) would get
18637 ignored and replaced by the default if a SocksListenAddress
18638 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
18642 - Relays now try regenerating and uploading their descriptor more
18643 frequently if they are not listed in the consensus, or if the
18644 version of their descriptor listed in the consensus is too
18645 old. This fix should prevent situations where a server declines
18646 to re-publish itself because it has done so too recently, even
18647 though the authorities decided not to list its recent-enough
18648 descriptor. Fix for bug 3327.
18651 - Relays now include a reason for regenerating their descriptors
18652 in an HTTP header when uploading to the authorities. This will
18653 make it easier to debug descriptor-upload issues in the future.
18654 - When starting as root and then changing our UID via the User
18655 control option, and we have a ControlSocket configured, make sure
18656 that the ControlSocket is owned by the same account that Tor will
18657 run under. Implements ticket 3421; fix by Jérémy Bobbio.
18660 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
18661 utility function used in the control-port code). This shouldn't
18662 ever happen unless Tor is completely out of memory, but if it did
18663 happen and Tor somehow recovered from it, Tor could have sent a log
18664 message to a control port in the middle of a reply to a controller
18665 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
18666 - Make 'FetchUselessDescriptors' cause all descriptor types and
18667 all consensus types (including microdescriptors) to get fetched.
18668 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
18670 o Code refactoring:
18671 - Make a new "entry connection" struct as an internal subtype of "edge
18672 connection", to simplify the code and make exit connections smaller.
18675 Changes in version 0.2.2.33 - 2011-09-13
18676 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
18677 TLS handshake that makes relays and bridges that run this new version
18678 reachable from Iran again.
18681 - Avoid an assertion failure when reloading a configuration with
18682 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
18683 3923; bugfix on 0.2.2.25-alpha.
18685 o Minor features (security):
18686 - Check for replays of the public-key encrypted portion of an
18687 INTRODUCE1 cell, in addition to the current check for replays of
18688 the g^x value. This prevents a possible class of active attacks
18689 by an attacker who controls both an introduction point and a
18690 rendezvous point, and who uses the malleability of AES-CTR to
18691 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
18692 that these attacks are infeasible (requiring the attacker to send
18693 on the order of zettabytes of altered cells in a short interval),
18694 but we'd rather block them off in case there are any classes of
18695 this attack that we missed. Reported by Willem Pinckaers.
18698 - Adjust the expiration time on our SSL session certificates to
18699 better match SSL certs seen in the wild. Resolves ticket 4014.
18700 - Change the default required uptime for a relay to be accepted as
18701 a HSDir (hidden service directory) from 24 hours to 25 hours.
18702 Improves on 0.2.0.10-alpha; resolves ticket 2649.
18703 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
18704 authorities to abstain from voting on assignment of the HSDir
18705 consensus flag. Related to bug 2649.
18706 - Update to the September 6 2011 Maxmind GeoLite Country database.
18708 o Minor bugfixes (documentation and log messages):
18709 - Correct the man page to explain that HashedControlPassword and
18710 CookieAuthentication can both be set, in which case either method
18711 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
18712 when we decided to allow these config options to both be set. Issue
18713 raised by bug 3898.
18714 - Demote the 'replay detected' log message emitted when a hidden
18715 service receives the same Diffie-Hellman public key in two different
18716 INTRODUCE2 cells to info level. A normal Tor client can cause that
18717 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
18718 fixes part of bug 2442.
18719 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
18720 level. There is nothing that a hidden service's operator can do
18721 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
18723 - Clarify a log message specifying the characters permitted in
18724 HiddenServiceAuthorizeClient client names. Previously, the log
18725 message said that "[A-Za-z0-9+-_]" were permitted; that could have
18726 given the impression that every ASCII character between "+" and "_"
18727 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
18730 - Provide a substitute implementation of lround() for MSVC, which
18731 apparently lacks it. Patch from Gisle Vanem.
18732 - Clean up some code issues that prevented Tor from building on older
18733 BSDs. Fixes bug 3894; reported by "grarpamp".
18734 - Search for a platform-specific version of "ar" when cross-compiling.
18735 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
18738 Changes in version 0.2.3.3-alpha - 2011-09-01
18739 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
18740 security, and provides client-side support for the microdescriptor
18741 and optimistic data features introduced earlier in the 0.2.3.x
18742 series. It also includes numerous critical bugfixes in the (optional)
18743 bufferevent-based networking backend.
18745 o Major features (stream isolation):
18746 - You can now configure Tor so that streams from different
18747 applications are isolated on different circuits, to prevent an
18748 attacker who sees your streams as they leave an exit node from
18749 linking your sessions to one another. To do this, choose some way
18750 to distinguish the applications: have them connect to different
18751 SocksPorts, or have one of them use SOCKS4 while the other uses
18752 SOCKS5, or have them pass different authentication strings to the
18753 SOCKS proxy. Then, use the new SocksPort syntax to configure the
18754 degree of isolation you need. This implements Proposal 171.
18755 - There's a new syntax for specifying multiple client ports (such as
18756 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
18757 multiple *Port entries with full addr:port syntax on each.
18758 The old *ListenAddress format is still supported, but you can't
18759 mix it with the new *Port syntax.
18761 o Major features (other):
18762 - Enable microdescriptor fetching by default for clients. This allows
18763 clients to download a much smaller amount of directory information.
18764 To disable it (and go back to the old-style consensus and
18765 descriptors), set "UseMicrodescriptors 0" in your torrc file.
18766 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
18767 "PortForwarding" config option), now supports Windows.
18768 - When using an exit relay running 0.2.3.x, clients can now
18769 "optimistically" send data before the exit relay reports that
18770 the stream has opened. This saves a round trip when starting
18771 connections where the client speaks first (such as web browsing).
18772 This behavior is controlled by a consensus parameter (currently
18773 disabled). To turn it on or off manually, use the "OptimisticData"
18774 torrc option. Implements proposal 181; code by Ian Goldberg.
18776 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
18777 - When using IOCP on Windows, we need to enable Libevent windows
18779 - The IOCP backend now works even when the user has not specified
18780 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
18781 Fixes part of bug 3752.
18782 - Correctly record the bytes we've read and written when using
18783 bufferevents, so that we can include them in our bandwidth history
18784 and advertised bandwidth. Fixes bug 3803.
18785 - Apply rate-limiting only at the bottom of a chain of filtering
18786 bufferevents. This prevents us from filling up internal read
18787 buffers and violating rate-limits when filtering bufferevents
18788 are enabled. Fixes part of bug 3804.
18789 - Add high-watermarks to the output buffers for filtered
18790 bufferevents. This prevents us from filling up internal write
18791 buffers and wasting CPU cycles when filtering bufferevents are
18792 enabled. Fixes part of bug 3804.
18793 - Correctly notice when data has been written from a bufferevent
18794 without flushing it completely. Fixes bug 3805.
18795 - Fix a bug where server-side tunneled bufferevent-based directory
18796 streams would get closed prematurely. Fixes bug 3814.
18797 - Fix a use-after-free error with per-connection rate-limiting
18798 buckets. Fixes bug 3888.
18800 o Major bugfixes (also part of 0.2.2.31-rc):
18801 - If we're configured to write our ControlPorts to disk, only write
18802 them after switching UID and creating the data directory. This way,
18803 we don't fail when starting up with a nonexistent DataDirectory
18804 and a ControlPortWriteToFile setting based on that directory. Fixes
18805 bug 3747; bugfix on Tor 0.2.2.26-beta.
18808 - Added a new CONF_CHANGED event so that controllers can be notified
18809 of any configuration changes made by other controllers, or by the
18810 user. Implements ticket 1692.
18811 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
18812 leak when using bufferevents, and lets Libevent worry about how to
18813 best copy data out of a buffer.
18814 - Replace files in stats/ rather than appending to them. Now that we
18815 include statistics in extra-info descriptors, it makes no sense to
18816 keep old statistics forever. Implements ticket 2930.
18818 o Minor features (build compatibility):
18819 - Limited, experimental support for building with nmake and MSVC.
18820 - Provide a substitute implementation of lround() for MSVC, which
18821 apparently lacks it. Patch from Gisle Vanem.
18823 o Minor features (also part of 0.2.2.31-rc):
18824 - Update to the August 2 2011 Maxmind GeoLite Country database.
18826 o Minor bugfixes (on 0.2.3.x-alpha):
18827 - Fix a spurious warning when parsing SOCKS requests with
18828 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
18829 - Get rid of a harmless warning that could happen on relays running
18830 with bufferevents. The warning was caused by someone doing an http
18831 request to a relay's orport. Also don't warn for a few related
18832 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
18834 o Minor bugfixes (on 2.2.x and earlier):
18835 - Correct the man page to explain that HashedControlPassword and
18836 CookieAuthentication can both be set, in which case either method
18837 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
18838 when we decided to allow these config options to both be set. Issue
18839 raised by bug 3898.
18840 - The "--quiet" and "--hush" options now apply not only to Tor's
18841 behavior before logs are configured, but also to Tor's behavior in
18842 the absence of configured logs. Fixes bug 3550; bugfix on
18845 o Minor bugfixes (also part of 0.2.2.31-rc):
18846 - Write several files in text mode, on OSes that distinguish text
18847 mode from binary mode (namely, Windows). These files are:
18848 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
18849 that collect those statistics; 'client_keys' and 'hostname' for
18850 hidden services that use authentication; and (in the tor-gencert
18851 utility) newly generated identity and signing keys. Previously,
18852 we wouldn't specify text mode or binary mode, leading to an
18853 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
18854 the DirRecordUsageByCountry option which would have triggered
18855 the assertion failure was added), although this assertion failure
18856 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
18857 - Selectively disable deprecation warnings on OS X because Lion
18858 started deprecating the shipped copy of openssl. Fixes bug 3643.
18859 - Remove an extra pair of quotation marks around the error
18860 message in control-port STATUS_GENERAL BUG events. Bugfix on
18861 0.1.2.6-alpha; fixes bug 3732.
18862 - When unable to format an address as a string, report its value
18863 as "???" rather than reusing the last formatted address. Bugfix
18866 o Code simplifications and refactoring:
18867 - Rewrite the listener-selection logic so that parsing which ports
18868 we want to listen on is now separate from binding to the ports
18872 - Building Tor with bufferevent support now requires Libevent
18873 2.0.13-stable or later. Previous versions of Libevent had bugs in
18874 SSL-related bufferevents and related issues that would make Tor
18875 work badly with bufferevents. Requiring 2.0.13-stable also allows
18876 Tor with bufferevents to take advantage of Libevent APIs
18877 introduced after 2.0.8-rc.
18880 Changes in version 0.2.2.32 - 2011-08-27
18881 The Tor 0.2.2 release series is dedicated to the memory of Andreas
18882 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
18883 a founder of the PETS community, a leader in our field, a mentor,
18884 and a friend. He left us with these words: "I had the possibility
18885 to contribute to this world that is not as it should be. I hope I
18886 could help in some areas to make the world a better place, and that
18887 I could also encourage other people to be engaged in improving the
18888 world. Please, stay engaged. This world needs you, your love, your
18889 initiative -- now I cannot be part of that anymore."
18891 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
18892 ready. More than two years in the making, this release features improved
18893 client performance and hidden service reliability, better compatibility
18894 for Android, correct behavior for bridges that listen on more than
18895 one address, more extensible and flexible directory object handling,
18896 better reporting of network statistics, improved code security, and
18897 many many other features and bugfixes.
18900 Changes in version 0.2.2.31-rc - 2011-08-17
18901 Tor 0.2.2.31-rc is the second and hopefully final release candidate
18902 for the Tor 0.2.2.x series.
18905 - Remove an extra pair of quotation marks around the error
18906 message in control-port STATUS_GENERAL BUG events. Bugfix on
18907 0.1.2.6-alpha; fixes bug 3732.
18908 - If we're configured to write our ControlPorts to disk, only write
18909 them after switching UID and creating the data directory. This way,
18910 we don't fail when starting up with a nonexistent DataDirectory
18911 and a ControlPortWriteToFile setting based on that directory. Fixes
18912 bug 3747; bugfix on Tor 0.2.2.26-beta.
18915 - Update to the August 2 2011 Maxmind GeoLite Country database.
18918 - Allow GETINFO fingerprint to return a fingerprint even when
18919 we have not yet built a router descriptor. Fixes bug 3577;
18920 bugfix on 0.2.0.1-alpha.
18921 - Write several files in text mode, on OSes that distinguish text
18922 mode from binary mode (namely, Windows). These files are:
18923 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
18924 that collect those statistics; 'client_keys' and 'hostname' for
18925 hidden services that use authentication; and (in the tor-gencert
18926 utility) newly generated identity and signing keys. Previously,
18927 we wouldn't specify text mode or binary mode, leading to an
18928 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
18929 the DirRecordUsageByCountry option which would have triggered
18930 the assertion failure was added), although this assertion failure
18931 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
18932 - Selectively disable deprecation warnings on OS X because Lion
18933 started deprecating the shipped copy of openssl. Fixes bug 3643.
18934 - When unable to format an address as a string, report its value
18935 as "???" rather than reusing the last formatted address. Bugfix
18939 Changes in version 0.2.3.2-alpha - 2011-07-18
18940 Tor 0.2.3.2-alpha introduces two new experimental features:
18941 microdescriptors and pluggable transports. It also continues cleaning
18942 up a variety of recently introduced features.
18945 - Clients can now use microdescriptors instead of regular descriptors
18946 to build circuits. Microdescriptors are authority-generated
18947 summaries of regular descriptors' contents, designed to change
18948 very rarely (see proposal 158 for details). This feature is
18949 designed to save bandwidth, especially for clients on slow internet
18950 connections. It's off by default for now, since nearly no caches
18951 support it, but it will be on-by-default for clients in a future
18952 version. You can use the UseMicrodescriptors option to turn it on.
18953 - Tor clients using bridges can now be configured to use a separate
18954 'transport' proxy for each bridge. This approach helps to resist
18955 censorship by allowing bridges to use protocol obfuscation
18956 plugins. It implements part of proposal 180. Implements ticket 2841.
18957 - While we're trying to bootstrap, record how many TLS connections
18958 fail in each state, and report which states saw the most failures
18959 in response to any bootstrap failures. This feature may speed up
18960 diagnosis of censorship events. Implements ticket 3116.
18962 o Major bugfixes (on 0.2.3.1-alpha):
18963 - When configuring a large set of nodes in EntryNodes (as with
18964 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
18965 random subset to be guards, and choose them in random
18966 order. Fixes bug 2798.
18967 - Tor could crash when remembering a consensus in a non-used consensus
18968 flavor without having a current consensus set. Fixes bug 3361.
18969 - Comparing an unknown address to a microdescriptor's shortened exit
18970 policy would always give a "rejected" result. Fixes bug 3599.
18971 - Using microdescriptors as a client no longer prevents Tor from
18972 uploading and downloading hidden service descriptors. Fixes
18976 - Allow nameservers with IPv6 address. Resolves bug 2574.
18977 - Accept attempts to include a password authenticator in the
18978 handshake, as supported by SOCKS5. This handles SOCKS clients that
18979 don't know how to omit a password when authenticating. Resolves
18981 - When configuring a large set of nodes in EntryNodes, and there are
18982 enough of them listed as Guard so that we don't need to consider
18983 the non-guard entries, prefer the ones listed with the Guard flag.
18984 - Check for and recover from inconsistency in the microdescriptor
18985 cache. This will make it harder for us to accidentally free a
18986 microdescriptor without removing it from the appropriate data
18987 structures. Fixes issue 3135; issue noted by "wanoskarnet".
18988 - Log SSL state transitions at log level DEBUG, log domain
18989 HANDSHAKE. This can be useful for debugging censorship events.
18990 Implements ticket 3264.
18991 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
18992 implements ticket 3439.
18994 o Minor bugfixes (on 0.2.3.1-alpha):
18995 - Do not free all general-purpose regular descriptors just
18996 because microdescriptor use is enabled. Fixes bug 3113.
18997 - Correctly link libevent_openssl when --enable-static-libevent
18998 is passed to configure. Fixes bug 3118.
18999 - Bridges should not complain during their heartbeat log messages that
19000 they are unlisted in the consensus: that's more or less the point
19001 of being a bridge. Fixes bug 3183.
19002 - Report a SIGNAL event to controllers when acting on a delayed
19003 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
19004 event to the controller if we acted on a SIGNAL NEWNYM command
19005 immediately, and otherwise not report a SIGNAL event for the
19006 command at all. Fixes bug 3349.
19007 - Fix a crash when handling the SIGNAL controller command or
19008 reporting ERR-level status events with bufferevents enabled. Found
19009 by Robert Ransom. Fixes bug 3367.
19010 - Always ship the tor-fw-helper manpage in our release tarballs.
19011 Fixes bug 3389. Reported by Stephen Walker.
19012 - Fix a class of double-mark-for-close bugs when bufferevents
19013 are enabled. Fixes bug 3403.
19014 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
19015 - Add SIGNAL to the list returned by the 'GETINFO events/names'
19016 control-port command. Fixes part of bug 3465.
19017 - Prevent using negative indices during unit test runs when read_all()
19018 fails. Spotted by coverity.
19019 - Fix a rare memory leak when checking the nodelist without it being
19020 present. Found by coverity.
19021 - Only try to download a microdescriptor-flavored consensus from
19022 a directory cache that provides them.
19024 o Minor bugfixes (on 0.2.2.x and earlier):
19025 - Assert that hidden-service-related operations are not performed
19026 using single-hop circuits. Previously, Tor would assert that
19027 client-side streams are not attached to single-hop circuits,
19028 but not that other sensitive operations on the client and service
19029 side are not performed using single-hop circuits. Fixes bug 3332;
19031 - Don't publish a new relay descriptor when we reload our onion key,
19032 unless the onion key has actually changed. Fixes bug 3263 and
19033 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
19034 - Allow GETINFO fingerprint to return a fingerprint even when
19035 we have not yet built a router descriptor. Fixes bug 3577;
19036 bugfix on 0.2.0.1-alpha.
19037 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
19038 on 0.2.2.4-alpha; fixes bug 3427.
19040 o Code simplification and refactoring:
19041 - Use tor_sscanf() in place of scanf() in more places through the
19042 code. This makes us a little more locale-independent, and
19043 should help shut up code-analysis tools that can't tell
19044 a safe sscanf string from a dangerous one.
19045 - Use tt_assert(), not tor_assert(), for checking for test failures.
19046 This makes the unit tests more able to go on in the event that
19048 - Split connection_about_to_close() into separate functions for each
19052 - On Windows, we now define the _WIN32_WINNT macros only if they
19053 are not already defined. This lets the person building Tor decide,
19054 if they want, to require a later version of Windows.
19057 Changes in version 0.2.2.30-rc - 2011-07-07
19058 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
19059 series. It fixes a few smaller bugs, but generally appears stable.
19060 Please test it and let us know whether it is!
19063 - Send a SUCCEEDED stream event to the controller when a reverse
19064 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
19065 discovered by katmagic.
19066 - Always NUL-terminate the sun_path field of a sockaddr_un before
19067 passing it to the kernel. (Not a security issue: kernels are
19068 smart enough to reject bad sockaddr_uns.) Found by Coverity;
19069 CID #428. Bugfix on Tor 0.2.0.3-alpha.
19070 - Don't stack-allocate the list of supplementary GIDs when we're
19071 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
19072 could take up to 256K, which is way too much stack. Found by
19073 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
19074 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
19075 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
19076 fixes part of bug 3465.
19077 - Fix a memory leak when receiving a descriptor for a hidden
19078 service we didn't ask for. Found by Coverity; CID #30. Bugfix
19082 - Update to the July 1 2011 Maxmind GeoLite Country database.
19085 Changes in version 0.2.2.29-beta - 2011-06-20
19086 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
19087 have bridge lines in their torrc but don't want to use them; gets
19088 us closer to having the control socket feature working on Debian;
19089 and fixes a variety of smaller bugs.
19092 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
19093 When we changed the default behavior to "use bridges if any
19094 are listed in the torrc", we surprised users who had bridges
19095 in their torrc files but who didn't actually want to use them.
19096 Partial resolution for bug 3354.
19099 - Don't attach new streams to old rendezvous circuits after SIGNAL
19100 NEWNYM. Previously, we would keep using an existing rendezvous
19101 circuit if it remained open (i.e. if it were kept open by a
19102 long-lived stream, or if a new stream were attached to it before
19103 Tor could notice that it was old and no longer in use). Bugfix on
19104 0.1.1.15-rc; fixes bug 3375.
19107 - Fix a bug when using ControlSocketsGroupWritable with User. The
19108 directory's group would be checked against the current group, not
19109 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
19110 bugfix on 0.2.2.26-beta.
19111 - Make connection_printf_to_buf()'s behavior sane. Its callers
19112 expect it to emit a CRLF iff the format string ends with CRLF;
19113 it actually emitted a CRLF iff (a) the format string ended with
19114 CRLF or (b) the resulting string was over 1023 characters long or
19115 (c) the format string did not end with CRLF *and* the resulting
19116 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
19117 fixes part of bug 3407.
19118 - Make send_control_event_impl()'s behavior sane. Its callers
19119 expect it to always emit a CRLF at the end of the string; it
19120 might have emitted extra control characters as well. Bugfix on
19121 0.1.1.9-alpha; fixes another part of bug 3407.
19122 - Make crypto_rand_int() check the value of its input correctly.
19123 Previously, it accepted values up to UINT_MAX, but could return a
19124 negative number if given a value above INT_MAX+1. Found by George
19125 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
19126 - Avoid a segfault when reading a malformed circuit build state
19127 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
19129 - When asked about a DNS record type we don't support via a
19130 client DNSPort, reply with NOTIMPL rather than an empty
19131 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
19132 - Fix a rare memory leak during stats writing. Found by coverity.
19135 - Update to the June 1 2011 Maxmind GeoLite Country database.
19137 o Code simplifications and refactoring:
19138 - Remove some dead code as indicated by coverity.
19139 - Remove a few dead assignments during router parsing. Found by
19141 - Add some forgotten return value checks during unit tests. Found
19143 - Don't use 1-bit wide signed bit fields. Found by coverity.
19146 Changes in version 0.2.2.28-beta - 2011-06-04
19147 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
19148 fixed a big bug in whether relays stay in the consensus consistently,
19149 we moved closer to handling bridges and hidden services correctly,
19150 and we started the process of better handling the dreaded "my Vidalia
19151 died, and now my Tor demands a password when I try to reconnect to it"
19155 - Don't decide to make a new descriptor when receiving a HUP signal.
19156 This bug has caused a lot of 0.2.2.x relays to disappear from the
19157 consensus periodically. Fixes the most common case of triggering
19158 bug 1810; bugfix on 0.2.2.7-alpha.
19159 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
19160 - Don't try to build descriptors if "ORPort auto" is set and we
19161 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
19163 - Resolve a crash that occurred when setting BridgeRelay to 1 with
19164 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
19165 - Apply circuit timeouts to opened hidden-service-related circuits
19166 based on the correct start time. Previously, we would apply the
19167 circuit build timeout based on time since the circuit's creation;
19168 it was supposed to be applied based on time since the circuit
19169 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
19170 - Use the same circuit timeout for client-side introduction
19171 circuits as for other four-hop circuits, rather than the timeout
19172 for single-hop directory-fetch circuits; the shorter timeout may
19173 have been appropriate with the static circuit build timeout in
19174 0.2.1.x and earlier, but caused many hidden service access attempts
19175 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
19176 on 0.2.2.2-alpha; fixes another part of bug 1297.
19177 - In ticket 2511 we fixed a case where you could use an unconfigured
19178 bridge if you had configured it as a bridge the last time you ran
19179 Tor. Now fix another edge case: if you had configured it as a bridge
19180 but then switched to a different bridge via the controller, you
19181 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
19185 - Add an __OwningControllerProcess configuration option and a
19186 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
19187 that when it exits, Tor will shut down. Implements feature 3049.
19188 - If "UseBridges 1" is set and no bridges are configured, Tor will
19189 now refuse to build any circuits until some bridges are set.
19190 If "UseBridges auto" is set, Tor will use bridges if they are
19191 configured and we are not running as a server, but otherwise will
19192 make circuits as usual. The new default is "auto". Patch by anonym,
19193 so the Tails LiveCD can stop automatically revealing you as a Tor
19197 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
19198 - Remove a trailing asterisk from "exit-policy/default" in the
19199 output of the control port command "GETINFO info/names". Bugfix
19201 - Use a wide type to hold sockets when built for 64-bit Windows builds.
19203 - Warn when the user configures two HiddenServiceDir lines that point
19204 to the same directory. Bugfix on 0.0.6 (the version introducing
19205 HiddenServiceDir); fixes bug 3289.
19206 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
19207 part of bug 2748; bugfix on 0.2.0.10-alpha.
19208 - Log malformed requests for rendezvous descriptors as protocol
19209 warnings, not warnings. Also, use a more informative log message
19210 in case someone sees it at log level warning without prior
19211 info-level messages. Fixes the other part of bug 2748; bugfix
19213 - Clear the table recording the time of the last request for each
19214 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
19215 Previously, we would clear our HS descriptor cache on SIGNAL
19216 NEWNYM, but if we had previously retrieved a descriptor (or tried
19217 to) from every directory responsible for it, we would refuse to
19218 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
19220 - Fix a log message that said "bits" while displaying a value in
19221 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
19223 - When checking for 1024-bit keys, check for 1024 bits, not 128
19224 bytes. This allows Tor to correctly discard keys of length 1017
19225 through 1023. Bugfix on 0.0.9pre5.
19228 - Relays now log the reason for publishing a new relay descriptor,
19229 so we have a better chance of hunting down instances of bug 1810.
19230 Resolves ticket 3252.
19231 - Revise most log messages that refer to nodes by nickname to
19232 instead use the "$key=nickname at address" format. This should be
19233 more useful, especially since nicknames are less and less likely
19234 to be unique. Resolves ticket 3045.
19235 - Log (at info level) when purging pieces of hidden-service-client
19236 state because of SIGNAL NEWNYM.
19239 - Remove undocumented option "-F" from tor-resolve: it hasn't done
19240 anything since 0.2.1.16-rc.
19243 Changes in version 0.2.2.27-beta - 2011-05-18
19244 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
19245 release, and also adds a few more general bugfixes.
19248 - Fix a crash bug when changing bridges in a running Tor process.
19249 Fixes bug 3213; bugfix on 0.2.2.26-beta.
19250 - When the controller configures a new bridge, don't wait 10 to 60
19251 seconds before trying to fetch its descriptor. Bugfix on
19252 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
19255 - Require that onion keys have exponent 65537 in microdescriptors too.
19256 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
19257 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
19258 Changed the limit to 512 characters by removing base64 newlines.
19259 Fixes bug 2752. Fix by Michael Yakubovich.
19260 - When a client starts or stops using bridges, never use a circuit
19261 that was built before the configuration change. This behavior could
19262 put at risk a user who uses bridges to ensure that her traffic
19263 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
19267 Changes in version 0.2.2.26-beta - 2011-05-17
19268 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
19269 also introduces a new "socksport auto" approach that should make it
19270 easier to run multiple Tors on the same system, and does a lot of
19271 cleanup to get us closer to a release candidate.
19273 o Security/privacy fixes:
19274 - Replace all potentially sensitive memory comparison operations
19275 with versions whose runtime does not depend on the data being
19276 compared. This will help resist a class of attacks where an
19277 adversary can use variations in timing information to learn
19278 sensitive data. Fix for one case of bug 3122. (Safe memcmp
19279 implementation by Robert Ransom based partially on code by DJB.)
19280 - When receiving a hidden service descriptor, check that it is for
19281 the hidden service we wanted. Previously, Tor would store any
19282 hidden service descriptors that a directory gave it, whether it
19283 wanted them or not. This wouldn't have let an attacker impersonate
19284 a hidden service, but it did let directories pre-seed a client
19285 with descriptors that it didn't want. Bugfix on 0.0.6.
19286 - On SIGHUP, do not clear out all TrackHostExits mappings, client
19287 DNS cache entries, and virtual address mappings: that's what
19288 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
19291 - The options SocksPort, ControlPort, and so on now all accept a
19292 value "auto" that opens a socket on an OS-selected port. A
19293 new ControlPortWriteToFile option tells Tor to write its
19294 actual control port or ports to a chosen file. If the option
19295 ControlPortFileGroupReadable is set, the file is created as
19296 group-readable. Now users can run two Tor clients on the same
19297 system without needing to manually mess with parameters. Resolves
19298 part of ticket 3076.
19299 - Set SO_REUSEADDR on all sockets, not just listeners. This should
19300 help busy exit nodes avoid running out of useable ports just
19301 because all the ports have been used in the near past. Resolves
19305 - New "GETINFO net/listeners/(type)" controller command to return
19306 a list of addresses and ports that are bound for listeners for a
19307 given connection type. This is useful when the user has configured
19308 "SocksPort auto" and the controller needs to know which port got
19309 chosen. Resolves another part of ticket 3076.
19310 - Add a new ControlSocketsGroupWritable configuration option: when
19311 it is turned on, ControlSockets are group-writeable by the default
19312 group of the current user. Patch by Jérémy Bobbio; implements
19314 - Tor now refuses to create a ControlSocket in a directory that is
19315 world-readable (or group-readable if ControlSocketsGroupWritable
19316 is 0). This is necessary because some operating systems do not
19317 enforce permissions on an AF_UNIX sockets. Permissions on the
19318 directory holding the socket, however, seems to work everywhere.
19319 - Rate-limit a warning about failures to download v2 networkstatus
19320 documents. Resolves part of bug 1352.
19321 - Backport code from 0.2.3.x that allows directory authorities to
19322 clean their microdescriptor caches. Needed to resolve bug 2230.
19323 - When an HTTPS proxy reports "403 Forbidden", we now explain
19324 what it means rather than calling it an unexpected status code.
19325 Closes bug 2503. Patch from Michael Yakubovich.
19326 - Update to the May 1 2011 Maxmind GeoLite Country database.
19329 - Authorities now clean their microdesc cache periodically and when
19330 reading from disk initially, not only when adding new descriptors.
19331 This prevents a bug where we could lose microdescriptors. Bugfix
19332 on 0.2.2.6-alpha. Fixes bug 2230.
19333 - Do not crash when our configuration file becomes unreadable, for
19334 example due to a permissions change, between when we start up
19335 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
19337 - Avoid a bug that would keep us from replacing a microdescriptor
19338 cache on Windows. (We would try to replace the file while still
19339 holding it open. That's fine on Unix, but Windows doesn't let us
19340 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
19341 - Add missing explanations for the authority-related torrc options
19342 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
19343 man page. Resolves issue 2379.
19344 - As an authority, do not upload our own vote or signature set to
19345 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
19346 it would get flagged as a duplicate. Resolves bug 3026.
19347 - Accept hidden service descriptors if we think we might be a hidden
19348 service directory, regardless of what our consensus says. This
19349 helps robustness, since clients and hidden services can sometimes
19350 have a more up-to-date view of the network consensus than we do,
19351 and if they think that the directory authorities list us a HSDir,
19352 we might actually be one. Related to bug 2732; bugfix on
19354 - When a controller changes TrackHostExits, remove mappings for
19355 hosts that should no longer have their exits tracked. Bugfix on
19357 - When a controller changes VirtualAddrNetwork, remove any mappings
19358 for hosts that were automapped to the old network. Bugfix on
19360 - When a controller changes one of the AutomapHosts* options, remove
19361 any mappings for hosts that should no longer be automapped. Bugfix
19363 - Do not reset the bridge descriptor download status every time we
19364 re-parse our configuration or get a configuration change. Fixes
19365 bug 3019; bugfix on 0.2.0.3-alpha.
19367 o Minor bugfixes (code cleanup):
19368 - When loading the microdesc journal, remember its current size.
19369 In 0.2.2, this helps prevent the microdesc journal from growing
19370 without limit on authorities (who are the only ones to use it in
19371 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
19372 Fix posted by "cypherpunks."
19373 - The microdesc journal is supposed to get rebuilt only if it is
19374 at least _half_ the length of the store, not _twice_ the length
19375 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
19376 - Fix a potential null-pointer dereference while computing a
19377 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
19379 - Avoid a possible null-pointer dereference when rebuilding the mdesc
19380 cache without actually having any descriptors to cache. Bugfix on
19381 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
19382 - If we fail to compute the identity digest of a v3 legacy keypair,
19383 warn, and don't use a buffer-full of junk instead. Bugfix on
19384 0.2.1.1-alpha; fixes bug 3106.
19385 - Resolve an untriggerable issue in smartlist_string_num_isin(),
19386 where if the function had ever in the future been used to check
19387 for the presence of a too-large number, it would have given an
19388 incorrect result. (Fortunately, we only used it for 16-bit
19389 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
19390 - Require that introduction point keys and onion handshake keys
19391 have a public exponent of 65537. Starts to fix bug 3207; bugfix
19394 o Removed features:
19395 - Caches no longer download and serve v2 networkstatus documents
19396 unless FetchV2Networkstatus flag is set: these documents haven't
19397 haven't been used by clients or relays since 0.2.0.x. Resolves
19401 Changes in version 0.2.3.1-alpha - 2011-05-05
19402 Tor 0.2.3.1-alpha adds some new experimental features, including support
19403 for an improved network IO backend, IOCP networking on Windows,
19404 microdescriptor caching, "fast-start" support for streams, and automatic
19405 home router configuration. There are also numerous internal improvements
19406 to try to make the code easier for developers to work with.
19408 This is the first alpha release in a new series, so expect there to be
19409 bugs. Users who would rather test out a more stable branch should
19410 stay with 0.2.2.x for now.
19413 - Tor can now optionally build with the "bufferevents" buffered IO
19414 backend provided by Libevent 2. To use this feature, make sure you
19415 have the latest possible version of Libevent, and pass the
19416 --enable-bufferevents flag to configure when building Tor from
19417 source. This feature will make our networking code more flexible,
19418 let us stack layers on each other, and let us use more efficient
19419 zero-copy transports where available.
19420 - As an experimental feature, Tor can use IOCP for networking on Windows.
19421 Once this code is tuned and optimized, it promises much better
19422 performance than the select-based backend we've used in the past. To
19423 try this feature, you must build Tor with Libevent 2, configure Tor
19424 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
19425 your torrc. There are known bugs here: only try this if you can help
19426 debug it as it breaks.
19427 - The EntryNodes option can now include country codes like {de} or IP
19428 addresses or network masks. Previously we had disallowed these options
19429 because we didn't have an efficient way to keep the list up to
19430 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
19431 - Exit nodes now accept and queue data on not-yet-connected streams.
19432 Previously, the client wasn't allowed to send data until the stream was
19433 connected, which slowed down all connections. This change will enable
19434 clients to perform a "fast-start" on streams and send data without
19435 having to wait for a confirmation that the stream has opened. (Patch
19436 from Ian Goldberg; implements the server side of Proposal 174.)
19437 - Tor now has initial support for automatic port mapping on the many
19438 home routers that support NAT-PMP or UPnP. (Not yet supported on
19439 Windows). To build the support code, you'll need to have libnatpnp
19440 library and/or the libminiupnpc library, and you'll need to enable the
19441 feature specifically by passing "--enable-upnp" and/or
19442 "--enable-natpnp" to configure. To turn it on, use the new
19443 PortForwarding option.
19444 - Caches now download, cache, and serve multiple "flavors" of the
19445 consensus, including a flavor that describes microdescriptors.
19446 - Caches now download, cache, and serve microdescriptors -- small
19447 summaries of router descriptors that are authenticated by all of the
19448 directory authorities. Once enough caches are running this code,
19449 clients will be able to save significant amounts of directory bandwidth
19450 by downloading microdescriptors instead of router descriptors.
19453 - Make logging resolution configurable with a new LogTimeGranularity
19454 option, and change the default from 1 millisecond to 1 second.
19455 Implements enhancement 1668.
19456 - We log which torrc file we're using on startup. Implements ticket
19458 - Ordinarily, Tor does not count traffic from private addresses (like
19459 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
19460 There is now a new option, CountPrivateBandwidth, to disable this
19461 behavior. Patch from Daniel Cagara.
19462 - New --enable-static-tor configure option for building Tor as
19463 statically as possible. Idea, general hackery and thoughts from
19464 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
19466 - If you set the NumCPUs option to 0, Tor will now try to detect how
19467 many CPUs you have. This is the new default behavior.
19468 - Turn on directory request statistics by default and include them in
19469 extra-info descriptors. Don't break if we have no GeoIP database.
19470 - Relays that set "ConnDirectionStatistics 1" write statistics on the
19471 bidirectional use of connections to disk every 24 hours.
19472 - Add a GeoIP file digest to the extra-info descriptor. Implements
19474 - The NodeFamily option -- which let you declare that you want to
19475 consider nodes to be part of a family whether they list themselves
19476 that way or not -- now allows IP address ranges and country codes.
19477 - Add a new 'Heartbeat' log message type to periodically log a message
19478 describing Tor's status at level Notice. This feature is meant for
19479 operators who log at notice, and want to make sure that their Tor
19480 server is still working. Implementation by George Kadianakis.
19482 o Minor bugfixes (on 0.2.2.25-alpha):
19483 - When loading the microdesc journal, remember its current size.
19484 In 0.2.2, this helps prevent the microdesc journal from growing
19485 without limit on authorities (who are the only ones to use it in
19486 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
19487 Fix posted by "cypherpunks."
19488 - The microdesc journal is supposed to get rebuilt only if it is
19489 at least _half_ the length of the store, not _twice_ the length
19490 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
19491 - If as an authority we fail to compute the identity digest of a v3
19492 legacy keypair, warn, and don't use a buffer-full of junk instead.
19493 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
19494 - Authorities now clean their microdesc cache periodically and when
19495 reading from disk initially, not only when adding new descriptors.
19496 This prevents a bug where we could lose microdescriptors. Bugfix
19499 o Minor features (controller):
19500 - Add a new SIGNAL event to the controller interface so that
19501 controllers can be notified when Tor handles a signal. Resolves
19502 issue 1955. Patch by John Brooks.
19503 - Add a new GETINFO option to get total bytes read and written. Patch
19504 from pipe, revised by atagar. Resolves ticket 2345.
19505 - Implement some GETINFO controller fields to provide information about
19506 the Tor process's pid, euid, username, and resource limits.
19509 - Our build system requires automake 1.6 or later to create the
19510 Makefile.in files. Previously, you could have used 1.4.
19511 This only affects developers and people building Tor from git;
19512 people who build Tor from the source distribution without changing
19513 the Makefile.am files should be fine.
19514 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
19515 so on. This is more robust against some of the failure modes
19516 associated with running the autotools pieces on their own.
19518 o Minor packaging issues:
19519 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
19520 already created. Patch from Andreas Stieger. Fixes bug 2573.
19522 o Code simplifications and refactoring:
19523 - A major revision to our internal node-selecting and listing logic.
19524 Tor already had at least two major ways to look at the question of
19525 "which Tor servers do we know about": a list of router descriptors,
19526 and a list of entries in the current consensus. With
19527 microdescriptors, we're adding a third. Having so many systems
19528 without an abstraction layer over them was hurting the codebase.
19529 Now, we have a new "node_t" abstraction that presents a consistent
19530 interface to a client's view of a Tor node, and holds (nearly) all
19531 of the mutable state formerly in routerinfo_t and routerstatus_t.
19532 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
19533 no longer link against Libevent: they never used it, but
19534 our library structure used to force them to link it.
19536 o Removed features:
19537 - Remove some old code to work around even older versions of Tor that
19538 used forked processes to handle DNS requests. Such versions of Tor
19539 are no longer in use as servers.
19541 o Documentation fixes:
19542 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
19543 - Add missing documentation for the authority-related torrc options
19544 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
19548 Changes in version 0.2.2.25-alpha - 2011-04-29
19549 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
19550 robust, routers no longer overreport their bandwidth, Win7 should crash
19551 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
19552 now prevents hidden service-related activity from being linkable. It
19553 provides more information to Vidalia so you can see if your bridge is
19554 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
19555 StrictNodes configuration options to make them more reliable, more
19556 understandable, and more regularly applied. If you use those options,
19557 please see the revised documentation for them in the manual page.
19560 - Relays were publishing grossly inflated bandwidth values because
19561 they were writing their state files wrong--now they write the
19562 correct value. Also, resume reading bandwidth history from the
19563 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
19564 - Improve hidden service robustness: When we find that we have
19565 extended a hidden service's introduction circuit to a relay not
19566 listed as an introduction point in the HS descriptor we currently
19567 have, retry with an introduction point from the current
19568 descriptor. Previously we would just give up. Fixes bugs 1024 and
19569 1930; bugfix on 0.2.0.10-alpha.
19570 - Clients now stop trying to use an exit node associated with a given
19571 destination by TrackHostExits if they fail to reach that exit node.
19572 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
19573 - Fix crash bug on platforms where gmtime and localtime can return
19574 NULL. Windows 7 users were running into this one. Fixes part of bug
19575 2077. Bugfix on all versions of Tor. Found by boboper.
19577 o Security and stability fixes:
19578 - Don't double-free a parsable, but invalid, microdescriptor, even if
19579 it is followed in the blob we're parsing by an unparsable
19580 microdescriptor. Fixes an issue reported in a comment on bug 2954.
19581 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
19582 - If the Nickname configuration option isn't given, Tor would pick a
19583 nickname based on the local hostname as the nickname for a relay.
19584 Because nicknames are not very important in today's Tor and the
19585 "Unnamed" nickname has been implemented, this is now problematic
19586 behavior: It leaks information about the hostname without being
19587 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
19588 introduced the Unnamed nickname. Reported by tagnaq.
19589 - Fix an uncommon assertion failure when running with DNSPort under
19590 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
19591 - Avoid linkability based on cached hidden service descriptors: forget
19592 all hidden service descriptors cached as a client when processing a
19593 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
19596 - Export GeoIP information on bridge usage to controllers even if we
19597 have not yet been running for 24 hours. Now Vidalia bridge operators
19598 can get more accurate and immediate feedback about their
19599 contributions to the network.
19601 o Major features and bugfixes (node selection):
19602 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
19603 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
19604 options. Previously, we had been ambiguous in describing what
19605 counted as an "exit" node, and what operations exactly "StrictNodes
19606 0" would permit. This created confusion when people saw nodes built
19607 through unexpected circuits, and made it hard to tell real bugs from
19608 surprises. Now the intended behavior is:
19609 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
19610 a node that delivers user traffic outside the Tor network.
19611 . "Entry", in the context of EntryNodes, means a node used as the
19612 first hop of a multihop circuit. It doesn't include direct
19613 connections to directory servers.
19614 . "ExcludeNodes" applies to all nodes.
19615 . "StrictNodes" changes the behavior of ExcludeNodes only. When
19616 StrictNodes is set, Tor should avoid all nodes listed in
19617 ExcludeNodes, even when it will make user requests fail. When
19618 StrictNodes is *not* set, then Tor should follow ExcludeNodes
19619 whenever it can, except when it must use an excluded node to
19620 perform self-tests, connect to a hidden service, provide a
19621 hidden service, fulfill a .exit request, upload directory
19622 information, or fetch directory information.
19623 Collectively, the changes to implement the behavior fix bug 1090.
19624 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
19625 a node is listed in both, it's treated as excluded.
19626 - ExcludeNodes now applies to directory nodes -- as a preference if
19627 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
19628 Don't exclude all the directory authorities and set StrictNodes to 1
19629 unless you really want your Tor to break.
19630 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
19631 - ExcludeExitNodes now overrides .exit requests.
19632 - We don't use bridges listed in ExcludeNodes.
19633 - When StrictNodes is 1:
19634 . We now apply ExcludeNodes to hidden service introduction points
19635 and to rendezvous points selected by hidden service users. This
19636 can make your hidden service less reliable: use it with caution!
19637 . If we have used ExcludeNodes on ourself, do not try relay
19638 reachability self-tests.
19639 . If we have excluded all the directory authorities, we will not
19640 even try to upload our descriptor if we're a relay.
19641 . Do not honor .exit requests to an excluded node.
19642 - Remove a misfeature that caused us to ignore the Fast/Stable flags
19643 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
19644 - When the set of permitted nodes changes, we now remove any mappings
19645 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
19647 - We never cannibalize a circuit that had excluded nodes on it, even
19648 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
19649 - Revert a change where we would be laxer about attaching streams to
19650 circuits than when building the circuits. This was meant to prevent
19651 a set of bugs where streams were never attachable, but our improved
19652 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
19653 - Keep track of how many times we launch a new circuit to handle a
19654 given stream. Too many launches could indicate an inconsistency
19655 between our "launch a circuit to handle this stream" logic and our
19656 "attach this stream to one of the available circuits" logic.
19657 - Improve log messages related to excluded nodes.
19660 - Fix a spurious warning when moving from a short month to a long
19661 month on relays with month-based BandwidthAccounting. Bugfix on
19662 0.2.2.17-alpha; fixes bug 3020.
19663 - When a client finds that an origin circuit has run out of 16-bit
19664 stream IDs, we now mark it as unusable for new streams. Previously,
19665 we would try to close the entire circuit. Bugfix on 0.0.6.
19666 - Add a forgotten cast that caused a compile warning on OS X 10.6.
19667 Bugfix on 0.2.2.24-alpha.
19668 - Be more careful about reporting the correct error from a failed
19669 connect() system call. Under some circumstances, it was possible to
19670 look at an incorrect value for errno when sending the end reason.
19671 Bugfix on 0.1.0.1-rc.
19672 - Correctly handle an "impossible" overflow cases in connection byte
19673 counting, where we write or read more than 4GB on an edge connection
19674 in a single second. Bugfix on 0.1.2.8-beta.
19675 - Correct the warning displayed when a rendezvous descriptor exceeds
19676 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
19678 - Clients and hidden services now use HSDir-flagged relays for hidden
19679 service descriptor downloads and uploads even if the relays have no
19680 DirPort set and the client has disabled TunnelDirConns. This will
19681 eventually allow us to give the HSDir flag to relays with no
19682 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
19683 - Downgrade "no current certificates known for authority" message from
19684 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
19685 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
19686 2917. Bugfix on 0.1.1.1-alpha.
19687 - Only limit the lengths of single HS descriptors, even when multiple
19688 HS descriptors are published to an HSDir relay in a single POST
19689 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
19690 - Write the current time into the LastWritten line in our state file,
19691 rather than the time from the previous write attempt. Also, stop
19692 trying to use a time of -1 in our log statements. Fixes bug 3039;
19693 bugfix on 0.2.2.14-alpha.
19694 - Be more consistent in our treatment of file system paths. "~" should
19695 get expanded to the user's home directory in the Log config option.
19696 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
19697 feature for the -f and --DataDirectory options.
19700 - Make sure every relay writes a state file at least every 12 hours.
19701 Previously, a relay could go for weeks without writing its state
19702 file, and on a crash could lose its bandwidth history, capacity
19703 estimates, client country statistics, and so on. Addresses bug 3012.
19704 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
19705 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
19706 clients are already deprecated because of security bugs.
19707 - Don't allow v0 hidden service authorities to act as clients.
19708 Required by fix for bug 3000.
19709 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
19710 by fix for bug 3000.
19711 - Ensure that no empty [dirreq-](read|write)-history lines are added
19712 to an extrainfo document. Implements ticket 2497.
19714 o Code simplification and refactoring:
19715 - Remove workaround code to handle directory responses from servers
19716 that had bug 539 (they would send HTTP status 503 responses _and_
19717 send a body too). Since only server versions before
19718 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
19719 keep the workaround in place.
19720 - Remove the old 'fuzzy time' logic. It was supposed to be used for
19721 handling calculations where we have a known amount of clock skew and
19722 an allowed amount of unknown skew. But we only used it in three
19723 places, and we never adjusted the known/unknown skew values. This is
19724 still something we might want to do someday, but if we do, we'll
19725 want to do it differently.
19726 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
19727 None of the cases where we did this before were wrong, but by making
19728 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
19729 - Use GetTempDir to find the proper temporary directory location on
19730 Windows when generating temporary files for the unit tests. Patch by
19734 Changes in version 0.2.2.24-alpha - 2011-04-08
19735 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
19736 prevented Tor clients from effectively using "multihomed" bridges,
19737 that is, bridges that listen on multiple ports or IP addresses so users
19738 can continue to use some of their addresses even if others get blocked.
19741 - Fix a bug where bridge users who configure the non-canonical
19742 address of a bridge automatically switch to its canonical
19743 address. If a bridge listens at more than one address, it should be
19744 able to advertise those addresses independently and any non-blocked
19745 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
19747 - If you configured Tor to use bridge A, and then quit and
19748 configured Tor to use bridge B instead, it would happily continue
19749 to use bridge A if it's still reachable. While this behavior is
19750 a feature if your goal is connectivity, in some scenarios it's a
19751 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
19752 - Directory authorities now use data collected from their own
19753 uptime observations when choosing whether to assign the HSDir flag
19754 to relays, instead of trusting the uptime value the relay reports in
19755 its descriptor. This change helps prevent an attack where a small
19756 set of nodes with frequently-changing identity keys can blackhole
19757 a hidden service. (Only authorities need upgrade; others will be
19758 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
19761 - When we restart our relay, we might get a successful connection
19762 from the outside before we've started our reachability tests,
19763 triggering a warning: "ORPort found reachable, but I have no
19764 routerinfo yet. Failing to inform controller of success." This
19765 bug was harmless unless Tor is running under a controller
19766 like Vidalia, in which case the controller would never get a
19767 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
19769 - Make directory authorities more accurate at recording when
19770 relays that have failed several reachability tests became
19771 unreachable, so we can provide more accuracy at assigning Stable,
19772 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
19773 - Fix an issue that prevented static linking of libevent on
19774 some platforms (notably Linux). Fixes bug 2698; bugfix on
19775 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
19776 the --with-static-libevent configure option).
19777 - We now ask the other side of a stream (the client or the exit)
19778 for more data on that stream when the amount of queued data on
19779 that stream dips low enough. Previously, we wouldn't ask the
19780 other side for more data until either it sent us more data (which
19781 it wasn't supposed to do if it had exhausted its window!) or we
19782 had completely flushed all our queued data. This flow control fix
19783 should improve throughput. Fixes bug 2756; bugfix on the earliest
19784 released versions of Tor (svn commit r152).
19785 - Avoid a double-mark-for-free warning when failing to attach a
19786 transparent proxy connection. (We thought we had fixed this in
19787 0.2.2.23-alpha, but it turns out our fix was checking the wrong
19788 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
19789 bug) and 0.2.2.23-alpha (the incorrect fix).
19790 - When warning about missing zlib development packages during compile,
19791 give the correct package names. Bugfix on 0.2.0.1-alpha.
19794 - Directory authorities now log the source of a rejected POSTed v3
19795 networkstatus vote.
19796 - Make compilation with clang possible when using
19797 --enable-gcc-warnings by removing two warning options that clang
19798 hasn't implemented yet and by fixing a few warnings. Implements
19800 - When expiring circuits, use microsecond timers rather than
19801 one-second timers. This can avoid an unpleasant situation where a
19802 circuit is launched near the end of one second and expired right
19803 near the beginning of the next, and prevent fluctuations in circuit
19805 - Use computed circuit-build timeouts to decide when to launch
19806 parallel introduction circuits for hidden services. (Previously,
19807 we would retry after 15 seconds.)
19808 - Update to the April 1 2011 Maxmind GeoLite Country database.
19811 - Create the /var/run/tor directory on startup on OpenSUSE if it is
19812 not already created. Patch from Andreas Stieger. Fixes bug 2573.
19814 o Documentation changes:
19815 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
19816 - Resolve all doxygen warnings except those for missing documentation.
19818 - Add doxygen documentation for more functions, fields, and types.
19821 Changes in version 0.2.2.23-alpha - 2011-03-08
19822 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
19823 they restart they don't lose their bandwidth capacity estimate. This
19824 release also fixes a diverse set of user-facing bugs, ranging from
19825 relays overrunning their rate limiting to clients falsely warning about
19826 clock skew to bridge descriptor leaks by our bridge directory authority.
19829 - Stop sending a CLOCK_SKEW controller status event whenever
19830 we fetch directory information from a relay that has a wrong clock.
19831 Instead, only inform the controller when it's a trusted authority
19832 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
19833 the rest of bug 1074.
19834 - Fix an assert in parsing router descriptors containing IPv6
19835 addresses. This one took down the directory authorities when
19836 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
19837 - Make the bridge directory authority refuse to answer directory
19838 requests for "all" descriptors. It used to include bridge
19839 descriptors in its answer, which was a major information leak.
19840 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
19841 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
19842 Tor would ignore their RelayBandwidthBurst setting,
19843 potentially using more bandwidth than expected. Bugfix on
19844 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
19845 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
19846 hidserv" in her torrc. The 'hidserv' argument never controlled
19847 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
19850 - Relays now save observed peak bandwidth throughput rates to their
19851 state file (along with total usage, which was already saved)
19852 so that they can determine their correct estimated bandwidth on
19853 restart. Resolves bug 1863, where Tor relays would reset their
19854 estimated bandwidth to 0 after restarting.
19855 - Directory authorities now take changes in router IP address and
19856 ORPort into account when determining router stability. Previously,
19857 if a router changed its IP or ORPort, the authorities would not
19858 treat it as having any downtime for the purposes of stability
19859 calculation, whereas clients would experience downtime since the
19860 change could take a while to propagate to them. Resolves issue 1035.
19861 - Enable Address Space Layout Randomization (ASLR) and Data Execution
19862 Prevention (DEP) by default on Windows to make it harder for
19863 attackers to exploit vulnerabilities. Patch from John Brooks.
19865 o Minor bugfixes (on 0.2.1.x and earlier):
19866 - Fix a rare crash bug that could occur when a client was configured
19867 with a large number of bridges. Fixes bug 2629; bugfix on
19868 0.2.1.2-alpha. Bugfix by trac user "shitlei".
19869 - Avoid a double mark-for-free warning when failing to attach a
19870 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
19872 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
19873 found by "cypherpunks". This bug was introduced before the first
19874 Tor release, in svn commit r110.
19875 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
19876 don't mention them in the manpage. Fixes bug 2450; issue
19877 spotted by keb and G-Lo.
19878 - Fix a bug in bandwidth history state parsing that could have been
19879 triggered if a future version of Tor ever changed the timing
19880 granularity at which bandwidth history is measured. Bugfix on
19881 Tor 0.1.1.11-alpha.
19882 - When a relay decides that its DNS is too broken for it to serve
19883 as an exit server, it advertised itself as a non-exit, but
19884 continued to act as an exit. This could create accidental
19885 partitioning opportunities for users. Instead, if a relay is
19886 going to advertise reject *:* as its exit policy, it should
19887 really act with exit policy "reject *:*". Fixes bug 2366.
19888 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
19889 - In the special case where you configure a public exit relay as your
19890 bridge, Tor would be willing to use that exit relay as the last
19891 hop in your circuit as well. Now we fail that circuit instead.
19892 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
19893 - Fix a bug with our locking implementation on Windows that couldn't
19894 correctly detect when a file was already locked. Fixes bug 2504,
19895 bugfix on 0.2.1.6-alpha.
19896 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
19897 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
19899 - Set target port in get_interface_address6() correctly. Bugfix
19900 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
19901 - Directory authorities are now more robust to hops back in time
19902 when calculating router stability. Previously, if a run of uptime
19903 or downtime appeared to be negative, the calculation could give
19904 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
19906 - Fix an assert that got triggered when using the TestingTorNetwork
19907 configuration option and then issuing a GETINFO config-text control
19908 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
19910 o Minor bugfixes (on 0.2.2.x):
19911 - Clients should not weight BadExit nodes as Exits in their node
19912 selection. Similarly, directory authorities should not count BadExit
19913 bandwidth as Exit bandwidth when computing bandwidth-weights.
19914 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
19915 - Correctly clear our dir_read/dir_write history when there is an
19916 error parsing any bw history value from the state file. Bugfix on
19917 Tor 0.2.2.15-alpha.
19918 - Resolve a bug in verifying signatures of directory objects
19919 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
19920 Fixes bug 2409. Found by "piebeer".
19921 - Bridge authorities no longer crash on SIGHUP when they try to
19922 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
19926 - Log less aggressively about circuit timeout changes, and improve
19927 some other circuit timeout messages. Resolves bug 2004.
19928 - Log a little more clearly about the times at which we're no longer
19929 accepting new connections. Resolves bug 2181.
19930 - Reject attempts at the client side to open connections to private
19931 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
19932 a randomly chosen exit node. Attempts to do so are always
19933 ill-defined, generally prevented by exit policies, and usually
19934 in error. This will also help to detect loops in transparent
19935 proxy configurations. You can disable this feature by setting
19936 "ClientRejectInternalAddresses 0" in your torrc.
19937 - Always treat failure to allocate an RSA key as an unrecoverable
19939 - Update to the March 1 2011 Maxmind GeoLite Country database.
19941 o Minor features (log subsystem):
19942 - Add documentation for configuring logging at different severities in
19943 different log domains. We've had this feature since 0.2.1.1-alpha,
19944 but for some reason it never made it into the manpage. Fixes
19946 - Make it simpler to specify "All log domains except for A and B".
19947 Previously you needed to say "[*,~A,~B]". Now you can just say
19949 - Add a "LogMessageDomains 1" option to include the domains of log
19950 messages along with the messages. Without this, there's no way
19951 to use log domains without reading the source or doing a lot
19954 o Packaging changes:
19955 - Stop shipping the Tor specs files and development proposal documents
19956 in the tarball. They are now in a separate git repository at
19957 git://git.torproject.org/torspec.git
19960 Changes in version 0.2.1.30 - 2011-02-23
19961 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
19962 change is a slight tweak to Tor's TLS handshake that makes relays
19963 and bridges that run this new version reachable from Iran again.
19964 We don't expect this tweak will win the arms race long-term, but it
19965 buys us time until we roll out a better solution.
19968 - Stop sending a CLOCK_SKEW controller status event whenever
19969 we fetch directory information from a relay that has a wrong clock.
19970 Instead, only inform the controller when it's a trusted authority
19971 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
19972 the rest of bug 1074.
19973 - Fix a bounds-checking error that could allow an attacker to
19974 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
19975 Found by "piebeer".
19976 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
19977 Tor would ignore their RelayBandwidthBurst setting,
19978 potentially using more bandwidth than expected. Bugfix on
19979 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
19980 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
19981 hidserv" in her torrc. The 'hidserv' argument never controlled
19982 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
19985 - Adjust our TLS Diffie-Hellman parameters to match those used by
19987 - Update to the February 1 2011 Maxmind GeoLite Country database.
19990 - Check for and reject overly long directory certificates and
19991 directory tokens before they have a chance to hit any assertions.
19992 Bugfix on 0.2.1.28. Found by "doorss".
19993 - Bring the logic that gathers routerinfos and assesses the
19994 acceptability of circuits into line. This prevents a Tor OP from
19995 getting locked in a cycle of choosing its local OR as an exit for a
19996 path (due to a .exit request) and then rejecting the circuit because
19997 its OR is not listed yet. It also prevents Tor clients from using an
19998 OR running in the same instance as an exit (due to a .exit request)
19999 if the OR does not meet the same requirements expected of an OR
20000 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
20002 o Packaging changes:
20003 - Stop shipping the Tor specs files and development proposal documents
20004 in the tarball. They are now in a separate git repository at
20005 git://git.torproject.org/torspec.git
20006 - Do not include Git version tags as though they are SVN tags when
20007 generating a tarball from inside a repository that has switched
20008 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20011 Changes in version 0.2.2.22-alpha - 2011-01-25
20012 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
20013 main other change is a slight tweak to Tor's TLS handshake that makes
20014 relays and bridges that run this new version reachable from Iran again.
20015 We don't expect this tweak will win the arms race long-term, but it
20016 will buy us a bit more time until we roll out a better solution.
20019 - Fix a bounds-checking error that could allow an attacker to
20020 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
20021 Found by "piebeer".
20022 - Don't assert when changing from bridge to relay or vice versa
20023 via the controller. The assert happened because we didn't properly
20024 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
20025 bug 2433. Reported by bastik.
20028 - Adjust our TLS Diffie-Hellman parameters to match those used by
20030 - Provide a log message stating which geoip file we're parsing
20031 instead of just stating that we're parsing the geoip file.
20032 Implements ticket 2432.
20035 - Check for and reject overly long directory certificates and
20036 directory tokens before they have a chance to hit any assertions.
20037 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
20040 Changes in version 0.2.2.21-alpha - 2011-01-15
20041 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
20042 continues our recent code security audit work. The main fix resolves
20043 a remote heap overflow vulnerability that can allow remote code
20044 execution (CVE-2011-0427). Other fixes address a variety of assert
20045 and crash bugs, most of which we think are hard to exploit remotely.
20047 o Major bugfixes (security), also included in 0.2.1.29:
20048 - Fix a heap overflow bug where an adversary could cause heap
20049 corruption. This bug probably allows remote code execution
20050 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
20052 - Prevent a denial-of-service attack by disallowing any
20053 zlib-compressed data whose compression factor is implausibly
20054 high. Fixes part of bug 2324; reported by "doorss".
20055 - Zero out a few more keys in memory before freeing them. Fixes
20056 bug 2384 and part of bug 2385. These key instances found by
20057 "cypherpunks", based on Andrew Case's report about being able
20058 to find sensitive data in Tor's memory space if you have enough
20059 permissions. Bugfix on 0.0.2pre9.
20061 o Major bugfixes (crashes), also included in 0.2.1.29:
20062 - Prevent calls to Libevent from inside Libevent log handlers.
20063 This had potential to cause a nasty set of crashes, especially
20064 if running Libevent with debug logging enabled, and running
20065 Tor with a controller watching for low-severity log messages.
20066 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
20067 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
20068 underflow errors there too. Fixes the other part of bug 2324.
20069 - Fix a bug where we would assert if we ever had a
20070 cached-descriptors.new file (or another file read directly into
20071 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
20072 on 0.2.1.25. Found by doorss.
20073 - Fix some potential asserts and parsing issues with grossly
20074 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
20077 o Minor bugfixes (other), also included in 0.2.1.29:
20078 - Fix a bug with handling misformed replies to reverse DNS lookup
20079 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
20080 bug reported by doorss.
20081 - Fix compilation on mingw when a pthreads compatibility library
20082 has been installed. (We don't want to use it, so we shouldn't
20083 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
20084 - Fix a bug where we would declare that we had run out of virtual
20085 addresses when the address space was only half-exhausted. Bugfix
20087 - Correctly handle the case where AutomapHostsOnResolve is set but
20088 no virtual addresses are available. Fixes bug 2328; bugfix on
20089 0.1.2.1-alpha. Bug found by doorss.
20090 - Correctly handle wrapping around when we run out of virtual
20091 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
20093 o Minor features, also included in 0.2.1.29:
20094 - Update to the January 1 2011 Maxmind GeoLite Country database.
20095 - Introduce output size checks on all of our decryption functions.
20097 o Build changes, also included in 0.2.1.29:
20098 - Tor does not build packages correctly with Automake 1.6 and earlier;
20099 added a check to Makefile.am to make sure that we're building with
20100 Automake 1.7 or later.
20101 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
20102 because we built it with a too-old version of automake. Thus that
20103 release broke ./configure --enable-openbsd-malloc, which is popular
20104 among really fast exit relays on Linux.
20106 o Major bugfixes, new in 0.2.2.21-alpha:
20107 - Prevent crash/heap corruption when the cbtnummodes consensus
20108 parameter is set to 0 or large values. Fixes bug 2317; bugfix
20111 o Major features, new in 0.2.2.21-alpha:
20112 - Introduce minimum/maximum values that clients will believe
20113 from the consensus. Now we'll have a better chance to avoid crashes
20114 or worse when a consensus param has a weird value.
20116 o Minor features, new in 0.2.2.21-alpha:
20117 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
20118 used on bridges, and it makes bridge scanning somewhat easier.
20119 - If writing the state file to disk fails, wait up to an hour before
20120 retrying again, rather than trying again each second. Fixes bug
20121 2346; bugfix on Tor 0.1.1.3-alpha.
20122 - Make Libevent log messages get delivered to controllers later,
20123 and not from inside the Libevent log handler. This prevents unsafe
20124 reentrant Libevent calls while still letting the log messages
20126 - Detect platforms that brokenly use a signed size_t, and refuse to
20127 build there. Found and analyzed by doorss and rransom.
20128 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
20131 o Minor bugfixes, new in 0.2.2.21-alpha:
20132 - Handle SOCKS messages longer than 128 bytes long correctly, rather
20133 than waiting forever for them to finish. Fixes bug 2330; bugfix
20134 on 0.2.0.16-alpha. Found by doorss.
20135 - Add assertions to check for overflow in arguments to
20136 base32_encode() and base32_decode(); fix a signed-unsigned
20137 comparison there too. These bugs are not actually reachable in Tor,
20138 but it's good to prevent future errors too. Found by doorss.
20139 - Correctly detect failures to create DNS requests when using Libevent
20140 versions before v2. (Before Libevent 2, we used our own evdns
20141 implementation. Its return values for Libevent's evdns_resolve_*()
20142 functions are not consistent with those from Libevent.) Fixes bug
20143 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
20145 o Documentation, new in 0.2.2.21-alpha:
20146 - Document the default socks host and port (127.0.0.1:9050) for
20150 Changes in version 0.2.1.29 - 2011-01-15
20151 Tor 0.2.1.29 continues our recent code security audit work. The main
20152 fix resolves a remote heap overflow vulnerability that can allow remote
20153 code execution. Other fixes address a variety of assert and crash bugs,
20154 most of which we think are hard to exploit remotely.
20156 o Major bugfixes (security):
20157 - Fix a heap overflow bug where an adversary could cause heap
20158 corruption. This bug probably allows remote code execution
20159 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
20161 - Prevent a denial-of-service attack by disallowing any
20162 zlib-compressed data whose compression factor is implausibly
20163 high. Fixes part of bug 2324; reported by "doorss".
20164 - Zero out a few more keys in memory before freeing them. Fixes
20165 bug 2384 and part of bug 2385. These key instances found by
20166 "cypherpunks", based on Andrew Case's report about being able
20167 to find sensitive data in Tor's memory space if you have enough
20168 permissions. Bugfix on 0.0.2pre9.
20170 o Major bugfixes (crashes):
20171 - Prevent calls to Libevent from inside Libevent log handlers.
20172 This had potential to cause a nasty set of crashes, especially
20173 if running Libevent with debug logging enabled, and running
20174 Tor with a controller watching for low-severity log messages.
20175 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
20176 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
20177 underflow errors there too. Fixes the other part of bug 2324.
20178 - Fix a bug where we would assert if we ever had a
20179 cached-descriptors.new file (or another file read directly into
20180 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
20181 on 0.2.1.25. Found by doorss.
20182 - Fix some potential asserts and parsing issues with grossly
20183 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
20186 o Minor bugfixes (other):
20187 - Fix a bug with handling misformed replies to reverse DNS lookup
20188 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
20189 bug reported by doorss.
20190 - Fix compilation on mingw when a pthreads compatibility library
20191 has been installed. (We don't want to use it, so we shouldn't
20192 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
20193 - Fix a bug where we would declare that we had run out of virtual
20194 addresses when the address space was only half-exhausted. Bugfix
20196 - Correctly handle the case where AutomapHostsOnResolve is set but
20197 no virtual addresses are available. Fixes bug 2328; bugfix on
20198 0.1.2.1-alpha. Bug found by doorss.
20199 - Correctly handle wrapping around to when we run out of virtual
20200 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
20201 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
20202 because we built it with a too-old version of automake. Thus that
20203 release broke ./configure --enable-openbsd-malloc, which is popular
20204 among really fast exit relays on Linux.
20207 - Update to the January 1 2011 Maxmind GeoLite Country database.
20208 - Introduce output size checks on all of our decryption functions.
20211 - Tor does not build packages correctly with Automake 1.6 and earlier;
20212 added a check to Makefile.am to make sure that we're building with
20213 Automake 1.7 or later.
20216 Changes in version 0.2.2.20-alpha - 2010-12-17
20217 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
20218 exploitable bugs. We also fix a variety of other significant bugs,
20219 change the IP address for one of our directory authorities, and update
20220 the minimum version that Tor relays must run to join the network.
20223 - Fix a remotely exploitable bug that could be used to crash instances
20224 of Tor remotely by overflowing on the heap. Remote-code execution
20225 hasn't been confirmed, but can't be ruled out. Everyone should
20226 upgrade. Bugfix on the 0.1.1 series and later.
20227 - Fix a bug that could break accounting on 64-bit systems with large
20228 time_t values, making them hibernate for impossibly long intervals.
20229 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
20230 - Fix a logic error in directory_fetches_from_authorities() that
20231 would cause all _non_-exits refusing single-hop-like circuits
20232 to fetch from authorities, when we wanted to have _exits_ fetch
20233 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
20235 - Fix a stream fairness bug that would cause newer streams on a given
20236 circuit to get preference when reading bytes from the origin or
20237 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
20238 introduced before the first Tor release, in svn revision r152.
20240 o Directory authority changes:
20241 - Change IP address and ports for gabelmoo (v3 directory authority).
20244 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
20245 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
20246 - Fix an off-by-one error in calculating some controller command
20247 argument lengths. Fortunately, this mistake is harmless since
20248 the controller code does redundant NUL termination too. Found by
20249 boboper. Bugfix on 0.1.1.1-alpha.
20250 - Do not dereference NULL if a bridge fails to build its
20251 extra-info descriptor. Found by an anonymous commenter on
20252 Trac. Bugfix on 0.2.2.19-alpha.
20255 - Update to the December 1 2010 Maxmind GeoLite Country database.
20256 - Directory authorities now reject relays running any versions of
20257 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
20258 known bugs that keep RELAY_EARLY cells from working on rendezvous
20259 circuits. Followup to fix for bug 2081.
20260 - Directory authorities now reject relays running any version of Tor
20261 older than 0.2.0.26-rc. That version is the earliest that fetches
20262 current directory information correctly. Fixes bug 2156.
20263 - Report only the top 10 ports in exit-port stats in order not to
20264 exceed the maximum extra-info descriptor length of 50 KB. Implements
20268 Changes in version 0.2.1.28 - 2010-12-17
20269 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
20270 exploitable bugs. We also took this opportunity to change the IP address
20271 for one of our directory authorities, and to update the geoip database
20275 - Fix a remotely exploitable bug that could be used to crash instances
20276 of Tor remotely by overflowing on the heap. Remote-code execution
20277 hasn't been confirmed, but can't be ruled out. Everyone should
20278 upgrade. Bugfix on the 0.1.1 series and later.
20280 o Directory authority changes:
20281 - Change IP address and ports for gabelmoo (v3 directory authority).
20284 - Update to the December 1 2010 Maxmind GeoLite Country database.
20287 Changes in version 0.2.1.27 - 2010-11-23
20288 Yet another OpenSSL security patch broke its compatibility with Tor:
20289 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
20290 also took this opportunity to fix several crash bugs, integrate a new
20291 directory authority, and update the bundled GeoIP database.
20294 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
20295 No longer set the tlsext_host_name extension on server SSL objects;
20296 but continue to set it on client SSL objects. Our goal in setting
20297 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
20298 bugfix on 0.2.1.1-alpha.
20299 - Do not log messages to the controller while shrinking buffer
20300 freelists. Doing so would sometimes make the controller connection
20301 try to allocate a buffer chunk, which would mess up the internals
20302 of the freelist and cause an assertion failure. Fixes bug 1125;
20303 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
20304 - Learn our external IP address when we're a relay or bridge, even if
20305 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
20306 where we introduced bridge relays that don't need to publish to
20307 be useful. Fixes bug 2050.
20308 - Do even more to reject (and not just ignore) annotations on
20309 router descriptors received anywhere but from the cache. Previously
20310 we would ignore such annotations at first, but cache them to disk
20311 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
20312 - When you're using bridges and your network goes away and your
20313 bridges get marked as down, recover when you attempt a new socks
20314 connection (if the network is back), rather than waiting up to an
20315 hour to try fetching new descriptors for your bridges. Bugfix on
20316 0.2.0.3-alpha; fixes bug 1981.
20319 - Move to the November 2010 Maxmind GeoLite country db (rather
20320 than the June 2009 ip-to-country GeoIP db) for our statistics that
20321 count how many users relays are seeing from each country. Now we'll
20322 have more accurate data, especially for many African countries.
20324 o New directory authorities:
20325 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
20329 - Fix an assertion failure that could occur in directory caches or
20330 bridge users when using a very short voting interval on a testing
20331 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
20333 - Enforce multiplicity rules when parsing annotations. Bugfix on
20334 0.2.0.8-alpha. Found by piebeer.
20335 - Allow handshaking OR connections to take a full KeepalivePeriod
20336 seconds to handshake. Previously, we would close them after
20337 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
20338 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
20340 - When building with --enable-gcc-warnings on OpenBSD, disable
20341 warnings in system headers. This makes --enable-gcc-warnings
20342 pass on OpenBSD 4.8.
20345 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
20346 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
20347 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
20348 Servers can start sending this code when enough clients recognize
20349 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
20350 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
20351 Patch from mingw-san.
20354 - Remove the old debian/ directory from the main Tor distribution.
20355 The official Tor-for-debian git repository lives at the URL
20356 https://git.torproject.org/debian/tor.git
20357 - Stop shipping the old doc/website/ directory in the tarball. We
20358 changed the website format in late 2010, and what we shipped in
20359 0.2.1.26 really wasn't that useful anyway.
20362 Changes in version 0.2.2.19-alpha - 2010-11-22
20363 Yet another OpenSSL security patch broke its compatibility with Tor:
20364 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
20367 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
20368 No longer set the tlsext_host_name extension on server SSL objects;
20369 but continue to set it on client SSL objects. Our goal in setting
20370 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
20371 bugfix on 0.2.1.1-alpha.
20374 - Try harder not to exceed the maximum length of 50 KB when writing
20375 statistics to extra-info descriptors. This bug was triggered by very
20376 fast relays reporting exit-port, entry, and dirreq statistics.
20377 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
20378 - Publish a router descriptor even if generating an extra-info
20379 descriptor fails. Previously we would not publish a router
20380 descriptor without an extra-info descriptor; this can cause fast
20381 exit relays collecting exit-port statistics to drop from the
20382 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
20385 Changes in version 0.2.2.18-alpha - 2010-11-16
20386 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
20387 us lately, makes unpublished bridge relays able to detect their IP
20388 address, and fixes a wide variety of other bugs to get us much closer
20389 to a stable release.
20392 - Do even more to reject (and not just ignore) annotations on
20393 router descriptors received anywhere but from the cache. Previously
20394 we would ignore such annotations at first, but cache them to disk
20395 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
20396 - Do not log messages to the controller while shrinking buffer
20397 freelists. Doing so would sometimes make the controller connection
20398 try to allocate a buffer chunk, which would mess up the internals
20399 of the freelist and cause an assertion failure. Fixes bug 1125;
20400 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
20401 - Learn our external IP address when we're a relay or bridge, even if
20402 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
20403 where we introduced bridge relays that don't need to publish to
20404 be useful. Fixes bug 2050.
20405 - Maintain separate TLS contexts and certificates for incoming and
20406 outgoing connections in bridge relays. Previously we would use the
20407 same TLS contexts and certs for incoming and outgoing connections.
20408 Bugfix on 0.2.0.3-alpha; addresses bug 988.
20409 - Maintain separate identity keys for incoming and outgoing TLS
20410 contexts in bridge relays. Previously we would use the same
20411 identity keys for incoming and outgoing TLS contexts. Bugfix on
20412 0.2.0.3-alpha; addresses the other half of bug 988.
20413 - Avoid an assertion failure when we as an authority receive a
20414 duplicate upload of a router descriptor that we already have,
20415 but which we previously considered an obsolete descriptor.
20416 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
20417 - Avoid a crash bug triggered by looking at a dangling pointer while
20418 setting the network status consensus. Found by Robert Ransom.
20419 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
20420 - Fix a logic error where servers that _didn't_ act as exits would
20421 try to keep their server lists more aggressively up to date than
20422 exits, when it was supposed to be the other way around. Bugfix
20425 o Minor bugfixes (on Tor 0.2.1.x and earlier):
20426 - When we're trying to guess whether we know our IP address as
20427 a relay, we would log various ways that we failed to guess
20428 our address, but never log that we ended up guessing it
20429 successfully. Now add a log line to help confused and anxious
20430 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
20431 - Bring the logic that gathers routerinfos and assesses the
20432 acceptability of circuits into line. This prevents a Tor OP from
20433 getting locked in a cycle of choosing its local OR as an exit for a
20434 path (due to a .exit request) and then rejecting the circuit because
20435 its OR is not listed yet. It also prevents Tor clients from using an
20436 OR running in the same instance as an exit (due to a .exit request)
20437 if the OR does not meet the same requirements expected of an OR
20438 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
20439 - Correctly describe errors that occur when generating a TLS object.
20440 Previously we would attribute them to a failure while generating a
20441 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
20443 - Enforce multiplicity rules when parsing annotations. Bugfix on
20444 0.2.0.8-alpha. Found by piebeer.
20445 - Fix warnings that newer versions of autoconf produced during
20446 ./autogen.sh. These warnings appear to be harmless in our case,
20447 but they were extremely verbose. Fixes bug 2020.
20449 o Minor bugfixes (on Tor 0.2.2.x):
20450 - Enable protection of small arrays whenever we build with gcc
20451 hardening features, not only when also building with warnings
20452 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
20455 - Make hidden services work better in private Tor networks by not
20456 requiring any uptime to join the hidden service descriptor
20457 DHT. Implements ticket 2088.
20458 - Rate-limit the "your application is giving Tor only an IP address"
20459 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
20460 - When AllowSingleHopExits is set, print a warning to explain to the
20461 relay operator why most clients are avoiding her relay.
20462 - Update to the November 1 2010 Maxmind GeoLite Country database.
20464 o Code simplifications and refactoring:
20465 - When we fixed bug 1038 we had to put in a restriction not to send
20466 RELAY_EARLY cells on rend circuits. This was necessary as long
20467 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
20468 active. Now remove this obsolete check. Resolves bug 2081.
20469 - Some options used different conventions for uppercasing of acronyms
20470 when comparing manpage and source. Fix those in favor of the
20471 manpage, as it makes sense to capitalize acronyms.
20472 - Remove the torrc.complete file. It hasn't been kept up to date
20473 and users will have better luck checking out the manpage.
20474 - Remove the obsolete "NoPublish" option; it has been flagged
20475 as obsolete and has produced a warning since 0.1.1.18-rc.
20476 - Remove everything related to building the expert bundle for OS X.
20477 It has confused many users, doesn't work right on OS X 10.6,
20478 and is hard to get rid of once installed. Resolves bug 1274.
20481 Changes in version 0.2.2.17-alpha - 2010-09-30
20482 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
20483 to use one-hop circuits (which can put the exit relays at higher risk,
20484 plus unbalance the network); fixes a big bug in bandwidth accounting
20485 for relays that want to limit their monthly bandwidth use; fixes a
20486 big pile of bugs in how clients tolerate temporary network failure;
20487 and makes our adaptive circuit build timeout feature (which improves
20488 client performance if your network is fast while not breaking things
20489 if your network is slow) better handle bad networks.
20492 - Exit relays now try harder to block exit attempts from unknown
20493 relays, to make it harder for people to use them as one-hop proxies
20494 a la tortunnel. Controlled by the refuseunknownexits consensus
20495 parameter (currently enabled), or you can override it on your
20496 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
20498 o Major bugfixes (0.2.1.x and earlier):
20499 - Fix a bug in bandwidth accounting that could make us use twice
20500 the intended bandwidth when our interval start changes due to
20501 daylight saving time. Now we tolerate skew in stored vs computed
20502 interval starts: if the start of the period changes by no more than
20503 50% of the period's duration, we remember bytes that we transferred
20504 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
20505 - Always search the Windows system directory for system DLLs, and
20506 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
20507 - When you're using bridges and your network goes away and your
20508 bridges get marked as down, recover when you attempt a new socks
20509 connection (if the network is back), rather than waiting up to an
20510 hour to try fetching new descriptors for your bridges. Bugfix on
20511 0.2.0.3-alpha; fixes bug 1981.
20513 o Major bugfixes (on 0.2.2.x):
20514 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
20516 - Fix a segfault that could happen when operating a bridge relay with
20517 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
20518 - The consensus bandwidth-weights (used by clients to choose fast
20519 relays) entered an unexpected edge case in September where
20520 Exits were much scarcer than Guards, resulting in bad weight
20521 recommendations. Now we compute them using new constraints that
20522 should succeed in all cases. Also alter directory authorities to
20523 not include the bandwidth-weights line if they fail to produce
20524 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
20525 - When weighting bridges during path selection, we used to trust
20526 the bandwidths they provided in their descriptor, only capping them
20527 at 10MB/s. This turned out to be problematic for two reasons:
20528 Bridges could claim to handle a lot more traffic then they
20529 actually would, thus making more clients pick them and have a
20530 pretty effective DoS attack. The other issue is that new bridges
20531 that might not have a good estimate for their bw capacity yet
20532 would not get used at all unless no other bridges are available
20533 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
20535 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
20536 - Ignore cannibalized circuits when recording circuit build times.
20537 This should provide for a minor performance improvement for hidden
20538 service users using 0.2.2.14-alpha, and should remove two spurious
20539 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
20540 - Simplify the logic that causes us to decide if the network is
20541 unavailable for purposes of recording circuit build times. If we
20542 receive no cells whatsoever for the entire duration of a circuit's
20543 full measured lifetime, the network is probably down. Also ignore
20544 one-hop directory fetching circuit timeouts when calculating our
20545 circuit build times. These changes should hopefully reduce the
20546 cases where we see ridiculous circuit build timeouts for people
20547 with spotty wireless connections. Fixes part of bug 1772; bugfix
20549 - Prevent the circuit build timeout from becoming larger than
20550 the maximum build time we have ever seen. Also, prevent the time
20551 period for measurement circuits from becoming larger than twice that
20552 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
20555 - When we run out of directory information such that we can't build
20556 circuits, but then get enough that we can build circuits, log when
20557 we actually construct a circuit, so the user has a better chance of
20558 knowing what's going on. Fixes bug 1362.
20559 - Be more generous with how much bandwidth we'd use up (with
20560 accounting enabled) before entering "soft hibernation". Previously,
20561 we'd refuse new connections and circuits once we'd used up 95% of
20562 our allotment. Now, we use up 95% of our allotment, AND make sure
20563 that we have no more than 500MB (or 3 hours of expected traffic,
20564 whichever is lower) remaining before we enter soft hibernation.
20565 - If we've configured EntryNodes and our network goes away and/or all
20566 our entrynodes get marked down, optimistically retry them all when
20567 a new socks application request appears. Fixes bug 1882.
20568 - Add some more defensive programming for architectures that can't
20569 handle unaligned integer accesses. We don't know of any actual bugs
20570 right now, but that's the best time to fix them. Fixes bug 1943.
20571 - Support line continuations in the torrc config file. If a line
20572 ends with a single backslash character, the newline is ignored, and
20573 the configuration value is treated as continuing on the next line.
20576 o Minor bugfixes (on 0.2.1.x and earlier):
20577 - For bandwidth accounting, calculate our expected bandwidth rate
20578 based on the time during which we were active and not in
20579 soft-hibernation during the last interval. Previously, we were
20580 also considering the time spent in soft-hibernation. If this
20581 was a long time, we would wind up underestimating our bandwidth
20582 by a lot, and skewing our wakeup time towards the start of the
20583 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
20585 o Minor bugfixes (on 0.2.2.x):
20586 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
20587 which were disabled by the circuit build timeout changes in
20588 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
20589 - Make sure we don't warn about missing bandwidth weights when
20590 choosing bridges or other relays not in the consensus. Bugfix on
20591 0.2.2.10-alpha; fixes bug 1805.
20592 - In our logs, do not double-report signatures from unrecognized
20593 authorities both as "from unknown authority" and "not
20594 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
20597 Changes in version 0.2.2.16-alpha - 2010-09-17
20598 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
20599 evident at exit relays), and also continues to resolve all the little
20600 bugs that have been filling up trac lately.
20602 o Major bugfixes (stream-level fairness):
20603 - When receiving a circuit-level SENDME for a blocked circuit, try
20604 to package cells fairly from all the streams that had previously
20605 been blocked on that circuit. Previously, we had started with the
20606 oldest stream, and allowed each stream to potentially exhaust
20607 the circuit's package window. This gave older streams on any
20608 given circuit priority over newer ones. Fixes bug 1937. Detected
20609 originally by Camilo Viecco. This bug was introduced before the
20610 first Tor release, in svn commit r152: it is the new winner of
20611 the longest-lived bug prize.
20612 - When the exit relay got a circuit-level sendme cell, it started
20613 reading on the exit streams, even if had 500 cells queued in the
20614 circuit queue already, so the circuit queue just grew and grew in
20615 some cases. We fix this by not re-enabling reading on receipt of a
20616 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
20617 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
20619 - Newly created streams were allowed to read cells onto circuits,
20620 even if the circuit's cell queue was blocked and waiting to drain.
20621 This created potential unfairness, as older streams would be
20622 blocked, but newer streams would gladly fill the queue completely.
20623 We add code to detect this situation and prevent any stream from
20624 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
20628 - Update to the September 1 2010 Maxmind GeoLite Country database.
20629 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
20630 not. This would lead to a cookie that is still not group readable.
20631 Closes bug 1843. Suggested by katmagic.
20632 - When logging a rate-limited warning, we now mention how many messages
20633 got suppressed since the last warning.
20634 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
20635 do individual connection-level rate limiting of clients. The torrc
20636 config options with the same names trump the consensus params, if
20637 both are present. Replaces the old "bwconnrate" and "bwconnburst"
20638 consensus params which were broken from 0.2.2.7-alpha through
20639 0.2.2.14-alpha. Closes bug 1947.
20640 - When a router changes IP address or port, authorities now launch
20641 a new reachability test for it. Implements ticket 1899.
20642 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
20643 2 no signature, 4 required" messages about consensus signatures
20644 easier to read, and make sure they get logged at the same severity
20645 as the messages explaining which keys are which. Fixes bug 1290.
20646 - Don't warn when we have a consensus that we can't verify because
20647 of missing certificates, unless those certificates are ones
20648 that we have been trying and failing to download. Fixes bug 1145.
20649 - If you configure your bridge with a known identity fingerprint,
20650 and the bridge authority is unreachable (as it is in at least
20651 one country now), fall back to directly requesting the descriptor
20652 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
20654 - When building with --enable-gcc-warnings on OpenBSD, disable
20655 warnings in system headers. This makes --enable-gcc-warnings
20656 pass on OpenBSD 4.8.
20658 o Minor bugfixes (on 0.2.1.x and earlier):
20659 - Authorities will now attempt to download consensuses if their
20660 own efforts to make a live consensus have failed. This change
20661 means authorities that restart will fetch a valid consensus, and
20662 it means authorities that didn't agree with the current consensus
20663 will still fetch and serve it if it has enough signatures. Bugfix
20664 on 0.2.0.9-alpha; fixes bug 1300.
20665 - Ensure DNS requests launched by "RESOLVE" commands from the
20666 controller respect the __LeaveStreamsUnattached setconf options. The
20667 same goes for requests launched via DNSPort or transparent
20668 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
20669 - Allow handshaking OR connections to take a full KeepalivePeriod
20670 seconds to handshake. Previously, we would close them after
20671 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
20672 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
20674 - Rate-limit "Failed to hand off onionskin" warnings.
20675 - Never relay a cell for a circuit we have already destroyed.
20676 Between marking a circuit as closeable and finally closing it,
20677 it may have been possible for a few queued cells to get relayed,
20678 even though they would have been immediately dropped by the next
20679 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
20680 - Never queue a cell for a circuit that's already been marked
20682 - Never vote for a server as "Running" if we have a descriptor for
20683 it claiming to be hibernating, and that descriptor was published
20684 more recently than our last contact with the server. Bugfix on
20685 0.2.0.3-alpha; fixes bug 911.
20686 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
20689 o Minor bugfixes (on 0.2.2.x):
20690 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
20691 down if a directory fetch fails and you've configured either
20692 bridges or EntryNodes. The intent was to mark the relay as down
20693 _unless_ you're using bridges or EntryNodes, since if you are
20694 then you could quickly run out of entry points.
20695 - Fix the Windows directory-listing code. A bug introduced in
20696 0.2.2.14-alpha could make Windows directory servers forget to load
20697 some of their cached v2 networkstatus files.
20698 - Really allow clients to use relays as bridges. Fixes bug 1776;
20699 bugfix on 0.2.2.15-alpha.
20700 - Demote a warn to info that happens when the CellStatistics option
20701 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
20702 Reported by Moritz Bartl.
20703 - On Windows, build correctly either with or without Unicode support.
20704 This is necessary so that Tor can support fringe platforms like
20705 Windows 98 (which has no Unicode), or Windows CE (which has no
20706 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
20709 - Add a unit test for cross-platform directory-listing code.
20712 Changes in version 0.2.2.15-alpha - 2010-08-18
20713 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
20714 fixes a variety of other bugs that were preventing performance
20715 experiments from moving forward, fixes several bothersome memory leaks,
20716 and generally closes a lot of smaller bugs that have been filling up
20720 - Stop assigning the HSDir flag to relays that disable their
20721 DirPort (and thus will refuse to answer directory requests). This
20722 fix should dramatically improve the reachability of hidden services:
20723 hidden services and hidden service clients pick six HSDir relays
20724 to store and retrieve the hidden service descriptor, and currently
20725 about half of the HSDir relays will refuse to work. Bugfix on
20726 0.2.0.10-alpha; fixes part of bug 1693.
20727 - The PerConnBWRate and Burst config options, along with the
20728 bwconnrate and bwconnburst consensus params, initialized each conn's
20729 token bucket values only when the connection is established. Now we
20730 update them if the config options change, and update them every time
20731 we get a new consensus. Otherwise we can encounter an ugly edge
20732 case where we initialize an OR conn to client-level bandwidth,
20733 but then later the relay joins the consensus and we leave it
20734 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
20735 - Fix a regression that caused Tor to rebind its ports if it receives
20736 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
20739 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
20740 should give us approximately 40-50% more Guard-flagged nodes,
20741 improving the anonymity the Tor network can provide and also
20742 decreasing the dropoff in throughput that relays experience when
20743 they first get the Guard flag.
20744 - Allow enabling or disabling the *Statistics config options while
20748 - Update to the August 1 2010 Maxmind GeoLite Country database.
20749 - Have the controller interface give a more useful message than
20750 "Internal Error" in response to failed GETINFO requests.
20751 - Warn when the same option is provided more than once in a torrc
20752 file, on the command line, or in a single SETCONF statement, and
20753 the option is one that only accepts a single line. Closes bug 1384.
20754 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
20755 Patch from mingw-san.
20756 - Add support for the country code "{??}" in torrc options like
20757 ExcludeNodes, to indicate all routers of unknown country. Closes
20759 - Relays report the number of bytes spent on answering directory
20760 requests in extra-info descriptors similar to {read,write}-history.
20761 Implements enhancement 1790.
20763 o Minor bugfixes (on 0.2.1.x and earlier):
20764 - Complain if PublishServerDescriptor is given multiple arguments that
20765 include 0 or 1. This configuration will be rejected in the future.
20766 Bugfix on 0.2.0.1-alpha; closes bug 1107.
20767 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
20768 Bugfix on 0.2.0.13-alpha; closes bug 928.
20769 - Change "Application request when we're believed to be offline."
20770 notice to "Application request when we haven't used client
20771 functionality lately.", to clarify that it's not an error. Bugfix
20772 on 0.0.9.3; fixes bug 1222.
20773 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
20774 would return "551 Internal error" rather than "552 Unrecognized key
20775 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
20776 - Users can't configure a regular relay to be their bridge. It didn't
20777 work because when Tor fetched the bridge descriptor, it found
20778 that it already had it, and didn't realize that the purpose of the
20779 descriptor had changed. Now we replace routers with a purpose other
20780 than bridge with bridge descriptors when fetching them. Bugfix on
20781 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
20782 refetch the descriptor with router purpose 'general', disabling
20784 - Fix a rare bug in rend_fn unit tests: we would fail a test when
20785 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
20786 on 0.2.0.10-alpha; fixes bug 1808.
20787 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
20788 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
20789 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
20790 Servers can start sending this code when enough clients recognize
20791 it. Also update the spec to reflect this new reason. Bugfix on
20792 0.1.0.1-rc; fixes part of bug 1793.
20793 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
20794 when we switch from being a public relay to a bridge. Otherwise
20795 there will still be clients that see the relay in their consensus,
20796 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
20798 - Instead of giving an assertion failure on an internal mismatch
20799 on estimated freelist size, just log a BUG warning and try later.
20800 Mitigates but does not fix bug 1125.
20801 - Fix an assertion failure that could occur in caches or bridge users
20802 when using a very short voting interval on a testing network.
20803 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
20805 o Minor bugfixes (on 0.2.2.x):
20806 - Alter directory authorities to always consider Exit-flagged nodes
20807 as potential Guard nodes in their votes. The actual decision to
20808 use Exits as Guards is done in the consensus bandwidth weights.
20809 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
20810 - When the controller is reporting the purpose of circuits that
20811 didn't finish building before the circuit build timeout, it was
20812 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
20813 - Our libevent version parsing code couldn't handle versions like
20814 1.4.14b-stable and incorrectly warned the user about using an
20815 old and broken version of libevent. Treat 1.4.14b-stable like
20816 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
20818 - Don't use substitution references like $(VAR:MOD) when
20819 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
20820 '$(:x)' to 'x' rather than the empty string. This bites us in
20821 doc/ when configured with --disable-asciidoc. Bugfix on
20822 0.2.2.9-alpha; fixes bug 1773.
20823 - Remove a spurious hidden service server-side log notice about
20824 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
20826 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
20828 - Correctly report written bytes on linked connections. Found while
20829 implementing 1790. Bugfix on 0.2.2.4-alpha.
20830 - Fix three memory leaks: one in circuit_build_times_parse_state(),
20831 one in dirvote_add_signatures_to_pending_consensus(), and one every
20832 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
20833 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
20835 o Code simplifications and refactoring:
20836 - Take a first step towards making or.h smaller by splitting out
20837 function definitions for all source files in src/or/. Leave
20838 structures and defines in or.h for now.
20839 - Remove a bunch of unused function declarations as well as a block of
20840 #if 0'd code from the unit tests. Closes bug 1824.
20841 - New unit tests for exit-port history statistics; refactored exit
20842 statistics code to be more easily tested.
20843 - Remove the old debian/ directory from the main Tor distribution.
20844 The official Tor-for-debian git repository lives at the URL
20845 https://git.torproject.org/debian/tor.git
20848 Changes in version 0.2.2.14-alpha - 2010-07-12
20849 Tor 0.2.2.14-alpha greatly improves client-side handling of
20850 circuit build timeouts, which are used to estimate speed and improve
20851 performance. We also move to a much better GeoIP database, port Tor to
20852 Windows CE, introduce new compile flags that improve code security,
20853 add an eighth v3 directory authority, and address a lot of more
20857 - Tor directory authorities no longer crash when started with a
20858 cached-microdesc-consensus file in their data directory. Bugfix
20859 on 0.2.2.6-alpha; fixes bug 1532.
20860 - Treat an unset $HOME like an empty $HOME rather than triggering an
20861 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
20862 - Ignore negative and large circuit build timeout values that can
20863 happen during a suspend or hibernate. These values caused various
20864 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
20865 - Alter calculation of Pareto distribution parameter 'Xm' for
20866 Circuit Build Timeout learning to use the weighted average of the
20867 top N=3 modes (because we have three entry guards). Considering
20868 multiple modes should improve the timeout calculation in some cases,
20869 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
20871 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
20872 right censored distribution model. This approach improves over the
20873 synthetic timeout generation approach that was producing insanely
20874 high timeout values. Now we calculate build timeouts using truncated
20875 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
20876 - Do not close circuits that are under construction when they reach
20877 the circuit build timeout. Instead, leave them building (but do not
20878 use them) for up until the time corresponding to the 95th percentile
20879 on the Pareto CDF or 60 seconds, whichever is greater. This is done
20880 to provide better data for the new Pareto model. This percentile
20881 can be controlled by the consensus.
20884 - Move to the June 2010 Maxmind GeoLite country db (rather than the
20885 June 2009 ip-to-country GeoIP db) for our statistics that count
20886 how many users relays are seeing from each country. Now we have
20887 more accurate data for many African countries.
20888 - Port Tor to build and run correctly on Windows CE systems, using
20889 the wcecompat library. Contributed by Valerio Lupi.
20890 - New "--enable-gcc-hardening" ./configure flag (off by default)
20891 to turn on gcc compile time hardening options. It ensures
20892 that signed ints have defined behavior (-fwrapv), enables
20893 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
20894 with canaries (-fstack-protector-all), turns on ASLR protection if
20895 supported by the kernel (-fPIE, -pie), and adds additional security
20896 related warnings. Verified to work on Mac OS X and Debian Lenny.
20897 - New "--enable-linker-hardening" ./configure flag (off by default)
20898 to turn on ELF specific hardening features (relro, now). This does
20899 not work with Mac OS X or any other non-ELF binary format.
20901 o New directory authorities:
20902 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
20906 - New config option "WarnUnsafeSocks 0" disables the warning that
20907 occurs whenever Tor receives a socks handshake using a version of
20908 the socks protocol that can only provide an IP address (rather
20909 than a hostname). Setups that do DNS locally over Tor are fine,
20910 and we shouldn't spam the logs in that case.
20911 - Convert the HACKING file to asciidoc, and add a few new sections
20912 to it, explaining how we use Git, how we make changelogs, and
20913 what should go in a patch.
20914 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
20915 event, to give information on the current rate of circuit timeouts
20916 over our stored history.
20917 - Add ability to disable circuit build time learning via consensus
20918 parameter and via a LearnCircuitBuildTimeout config option. Also
20919 automatically disable circuit build time calculation if we are
20920 either a AuthoritativeDirectory, or if we fail to write our state
20921 file. Fixes bug 1296.
20922 - More gracefully handle corrupt state files, removing asserts
20923 in favor of saving a backup and resetting state.
20924 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
20928 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
20930 - When a2x fails, mention that the user could disable manpages instead
20931 of trying to fix their asciidoc installation.
20932 - Where available, use Libevent 2.0's periodic timers so that our
20933 once-per-second cleanup code gets called even more closely to
20934 once per second than it would otherwise. Fixes bug 943.
20935 - If you run a bridge that listens on multiple IP addresses, and
20936 some user configures a bridge address that uses a different IP
20937 address than your bridge writes in its router descriptor, and the
20938 user doesn't specify an identity key, their Tor would discard the
20939 descriptor because "it isn't one of our configured bridges", and
20940 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
20941 Bugfix on 0.2.0.3-alpha.
20942 - If OpenSSL fails to make a duplicate of a private or public key, log
20943 an error message and try to exit cleanly. May help with debugging
20944 if bug 1209 ever remanifests.
20945 - Save a couple bytes in memory allocation every time we escape
20946 certain characters in a string. Patch from Florian Zumbiehl.
20947 - Make it explicit that we don't cannibalize one-hop circuits. This
20948 happens in the wild, but doesn't turn out to be a problem because
20949 we fortunately don't use those circuits. Many thanks to outofwords
20950 for the initial analysis and to swissknife who confirmed that
20951 two-hop circuits are actually created.
20952 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
20953 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
20954 - Eliminate a case where a circuit build time warning was displayed
20955 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
20958 Changes in version 0.2.1.26 - 2010-05-02
20959 Tor 0.2.1.26 addresses the recent connection and memory overload
20960 problems we've been seeing on relays, especially relays with their
20961 DirPort open. If your relay has been crashing, or you turned it off
20962 because it used too many resources, give this release a try.
20964 This release also fixes yet another instance of broken OpenSSL libraries
20965 that was causing some relays to drop out of the consensus.
20968 - Teach relays to defend themselves from connection overload. Relays
20969 now close idle circuits early if it looks like they were intended
20970 for directory fetches. Relays are also more aggressive about closing
20971 TLS connections that have no circuits on them. Such circuits are
20972 unlikely to be re-used, and tens of thousands of them were piling
20973 up at the fast relays, causing the relays to run out of sockets
20974 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
20975 their directory fetches over TLS).
20976 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
20977 that claim to be earlier than 0.9.8m, but which have in reality
20978 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
20979 behavior. Possible fix for some cases of bug 1346.
20980 - Directory mirrors were fetching relay descriptors only from v2
20981 directory authorities, rather than v3 authorities like they should.
20982 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
20983 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
20986 - Finally get rid of the deprecated and now harmful notion of "clique
20987 mode", where directory authorities maintain TLS connections to
20991 - In the util/threads test, no longer free the test_mutex before all
20992 worker threads have finished. Bugfix on 0.2.1.6-alpha.
20993 - The master thread could starve the worker threads quite badly on
20994 certain systems, causing them to run only partially in the allowed
20995 window. This resulted in test failures. Now the master thread sleeps
20996 occasionally for a few microseconds while the two worker-threads
20997 compete for the mutex. Bugfix on 0.2.0.1-alpha.
21000 Changes in version 0.2.2.13-alpha - 2010-04-24
21001 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
21002 problems we've been seeing on relays, especially relays with their
21003 DirPort open. If your relay has been crashing, or you turned it off
21004 because it used too many resources, give this release a try.
21007 - Teach relays to defend themselves from connection overload. Relays
21008 now close idle circuits early if it looks like they were intended
21009 for directory fetches. Relays are also more aggressive about closing
21010 TLS connections that have no circuits on them. Such circuits are
21011 unlikely to be re-used, and tens of thousands of them were piling
21012 up at the fast relays, causing the relays to run out of sockets
21013 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
21014 their directory fetches over TLS).
21017 - Finally get rid of the deprecated and now harmful notion of "clique
21018 mode", where directory authorities maintain TLS connections to
21020 - Directory authorities now do an immediate reachability check as soon
21021 as they hear about a new relay. This change should slightly reduce
21022 the time between setting up a relay and getting listed as running
21023 in the consensus. It should also improve the time between setting
21024 up a bridge and seeing use by bridge users.
21025 - Directory authorities no longer launch a TLS connection to every
21026 relay as they startup. Now that we have 2k+ descriptors cached,
21027 the resulting network hiccup is becoming a burden. Besides,
21028 authorities already avoid voting about Running for the first half
21029 hour of their uptime.
21032 Changes in version 0.2.2.12-alpha - 2010-04-20
21033 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
21034 handle and vote on descriptors. It was causing relays to drop out of
21038 - Many relays have been falling out of the consensus lately because
21039 not enough authorities know about their descriptor for them to get
21040 a majority of votes. When we deprecated the v2 directory protocol,
21041 we got rid of the only way that v3 authorities can hear from each
21042 other about other descriptors. Now authorities examine every v3
21043 vote for new descriptors, and fetch them from that authority. Bugfix
21045 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
21046 and a warning in or.h related to bandwidth_weight_rule_t that
21047 prevented clean compile on OS X. Fixes bug 1363; bugfix on
21049 - Fix a segfault on relays when DirReqStatistics is enabled
21050 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
21054 - Demote a confusing TLS warning that relay operators might get when
21055 someone tries to talk to their OrPort. It is neither the operator's
21056 fault nor can they do anything about it. Fixes bug 1364; bugfix
21060 Changes in version 0.2.2.11-alpha - 2010-04-15
21061 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
21062 libraries that was causing some relays to drop out of the consensus.
21065 - Directory mirrors were fetching relay descriptors only from v2
21066 directory authorities, rather than v3 authorities like they should.
21067 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
21068 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
21069 - Fix a parsing error that made every possible value of
21070 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
21071 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
21072 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
21073 about the option without breaking older ones.
21074 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
21075 that claim to be earlier than 0.9.8m, but which have in reality
21076 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
21077 behavior. Possible fix for some cases of bug 1346.
21080 - Experiment with a more aggressive approach to preventing clients
21081 from making one-hop exit streams. Exit relays who want to try it
21082 out can set "RefuseUnknownExits 1" in their torrc, and then look
21083 for "Attempt by %s to open a stream" log messages. Let us know
21085 - Add support for statically linking zlib by specifying
21086 --enable-static-zlib, to go with our support for statically linking
21087 openssl and libevent. Resolves bug 1358.
21090 - Fix a segfault that happens whenever a Tor client that is using
21091 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
21093 - When we cleaned up the contrib/tor-exit-notice.html file, we left
21094 out the first line. Fixes bug 1295.
21095 - When building the manpage from a tarball, we required asciidoc, but
21096 the asciidoc -> roff/html conversion was already done for the
21097 tarball. Make 'make' complain only when we need asciidoc (either
21098 because we're compiling directly from git, or because we altered
21099 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
21100 - When none of the directory authorities vote on any params, Tor
21101 segfaulted when trying to make the consensus from the votes. We
21102 didn't trigger the bug in practice, because authorities do include
21103 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
21106 - In the util/threads test, no longer free the test_mutex before all
21107 worker threads have finished. Bugfix on 0.2.1.6-alpha.
21108 - The master thread could starve the worker threads quite badly on
21109 certain systems, causing them to run only partially in the allowed
21110 window. This resulted in test failures. Now the master thread sleeps
21111 occasionally for a few microseconds while the two worker-threads
21112 compete for the mutex. Bugfix on 0.2.0.1-alpha.
21115 Changes in version 0.2.2.10-alpha - 2010-03-07
21116 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
21117 could prevent relays from guessing their IP address correctly. It also
21118 starts the groundwork for another client-side performance boost, since
21119 currently we're not making efficient use of relays that have both the
21120 Guard flag and the Exit flag.
21123 - Fix a regression from our patch for bug 1244 that caused relays
21124 to guess their IP address incorrectly if they didn't set Address
21125 in their torrc and/or their address fails to resolve. Bugfix on
21126 0.2.2.9-alpha; fixes bug 1269.
21128 o Major features (performance):
21129 - Directory authorities now compute consensus weightings that instruct
21130 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
21131 and no flag. Clients that use these weightings will distribute
21132 network load more evenly across these different relay types. The
21133 weightings are in the consensus so we can change them globally in
21134 the future. Extra thanks to "outofwords" for finding some nasty
21135 security bugs in the first implementation of this feature.
21137 o Minor features (performance):
21138 - Always perform router selections using weighted relay bandwidth,
21139 even if we don't need a high capacity circuit at the time. Non-fast
21140 circuits now only differ from fast ones in that they can use relays
21141 not marked with the Fast flag. This "feature" could turn out to
21142 be a horrible bug; we should investigate more before it goes into
21146 - Allow disabling building of the manpages. Skipping the manpage
21147 speeds up the build considerably.
21149 o Minor bugfixes (on 0.2.2.x):
21150 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
21151 Bugfix on 0.2.2.9-alpha.
21152 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
21153 config option. Bugfix on 0.2.2.7-alpha.
21154 - Ship the asciidoc-helper file in the tarball, so that people can
21155 build from source if they want to, and touching the .1.txt files
21156 doesn't break the build. Bugfix on 0.2.2.9-alpha.
21158 o Minor bugfixes (on 0.2.1.x or earlier):
21159 - Fix a dereference-then-NULL-check sequence when publishing
21160 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
21162 - Fix another dereference-then-NULL-check sequence. Bugfix on
21163 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
21164 - Make sure we treat potentially not NUL-terminated strings correctly.
21165 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
21167 o Code simplifications and refactoring:
21168 - Fix some urls in the exit notice file and make it XHTML1.1 strict
21169 compliant. Based on a patch from Christian Kujau.
21170 - Don't use sed in asciidoc-helper anymore.
21171 - Make the build process fail if asciidoc cannot be found and
21172 building with asciidoc isn't disabled.
21175 Changes in version 0.2.2.9-alpha - 2010-02-22
21176 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
21177 location of a directory authority, and cleans up a bunch of small bugs.
21179 o Directory authority changes:
21180 - Change IP address for dannenberg (v3 directory authority), and
21181 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
21182 service directory authority) from the list.
21185 - Make Tor work again on the latest OS X: when deciding whether to
21186 use strange flags to turn TLS renegotiation on, detect the OpenSSL
21187 version at run-time, not compile time. We need to do this because
21188 Apple doesn't update its dev-tools headers when it updates its
21189 libraries in a security patch.
21190 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
21191 that could happen on 32-bit platforms with 64-bit time_t. Also fix
21192 a memory leak when requesting a hidden service descriptor we've
21193 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
21195 - Authorities could be tricked into giving out the Exit flag to relays
21196 that didn't allow exiting to any ports. This bug could screw
21197 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
21198 1238. Bug discovered by Martin Kowalczyk.
21199 - When freeing a session key, zero it out completely. We only zeroed
21200 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
21201 patched by ekir. Fixes bug 1254.
21204 - Fix static compilation by listing the openssl libraries in the right
21205 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
21206 - Resume handling .exit hostnames in a special way: originally we
21207 stripped the .exit part and used the requested exit relay. In
21208 0.2.2.1-alpha we stopped treating them in any special way, meaning
21209 if you use a .exit address then Tor will pass it on to the exit
21210 relay. Now we reject the .exit stream outright, since that behavior
21211 might be more expected by the user. Found and diagnosed by Scott
21212 Bennett and Downie on or-talk.
21213 - Don't spam the controller with events when we have no file
21214 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
21215 for log messages was already solved from bug 748.)
21216 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
21218 - Make the DNSPort option work with libevent 2.x. Don't alter the
21219 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
21220 - Emit a GUARD DROPPED controller event for a case we missed.
21221 - Make more fields in the controller protocol case-insensitive, since
21222 control-spec.txt said they were.
21223 - Refactor resolve_my_address() to not use gethostbyname() anymore.
21224 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
21225 - Fix a spec conformance issue: the network-status-version token
21226 must be the first token in a v3 consensus or vote. Discovered by
21227 parakeep. Bugfix on 0.2.0.3-alpha.
21229 o Code simplifications and refactoring:
21230 - Generate our manpage and HTML documentation using Asciidoc. This
21231 change should make it easier to maintain the documentation, and
21232 produce nicer HTML.
21233 - Remove the --enable-iphone option. According to reports from Marco
21234 Bonetti, Tor builds fine without any special tweaking on recent
21235 iPhone SDK versions.
21236 - Removed some unnecessary files from the source distribution. The
21237 AUTHORS file has now been merged into the people page on the
21238 website. The roadmaps and design doc can now be found in the
21239 projects directory in svn.
21240 - Enabled various circuit build timeout constants to be controlled
21241 by consensus parameters. Also set better defaults for these
21242 parameters based on experimentation on broadband and simulated
21243 high latency links.
21246 - The 'EXTENDCIRCUIT' control port command can now be used with
21247 a circ id of 0 and no path. This feature will cause Tor to build
21248 a new 'fast' general purpose circuit using its own path selection
21250 - Added a BUILDTIMEOUT_SET controller event to describe changes
21251 to the circuit build timeout.
21252 - Future-proof the controller protocol a bit by ignoring keyword
21253 arguments we do not recognize.
21254 - Expand homedirs passed to tor-checkkey. This should silence a
21255 coverity complaint about passing a user-supplied string into
21256 open() without checking it.
21259 Changes in version 0.2.1.25 - 2010-03-16
21260 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
21261 prevent relays from guessing their IP address correctly. It also fixes
21262 several minor potential security bugs.
21265 - Fix a regression from our patch for bug 1244 that caused relays
21266 to guess their IP address incorrectly if they didn't set Address
21267 in their torrc and/or their address fails to resolve. Bugfix on
21268 0.2.1.23; fixes bug 1269.
21269 - When freeing a session key, zero it out completely. We only zeroed
21270 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
21271 patched by ekir. Fixes bug 1254.
21274 - Fix a dereference-then-NULL-check sequence when publishing
21275 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
21277 - Fix another dereference-then-NULL-check sequence. Bugfix on
21278 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
21279 - Make sure we treat potentially not NUL-terminated strings correctly.
21280 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
21284 Changes in version 0.2.1.24 - 2010-02-21
21285 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
21289 - Work correctly out-of-the-box with even more vendor-patched versions
21290 of OpenSSL. In particular, make it so Debian and OS X don't need
21291 customized patches to run/build.
21294 Changes in version 0.2.1.23 - 2010-02-13
21295 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
21296 again on the latest OS X, and updates the location of a directory
21299 o Major bugfixes (performance):
21300 - We were selecting our guards uniformly at random, and then weighting
21301 which of our guards we'd use uniformly at random. This imbalance
21302 meant that Tor clients were severely limited on throughput (and
21303 probably latency too) by the first hop in their circuit. Now we
21304 select guards weighted by currently advertised bandwidth. We also
21305 automatically discard guards picked using the old algorithm. Fixes
21306 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
21309 - Make Tor work again on the latest OS X: when deciding whether to
21310 use strange flags to turn TLS renegotiation on, detect the OpenSSL
21311 version at run-time, not compile time. We need to do this because
21312 Apple doesn't update its dev-tools headers when it updates its
21313 libraries in a security patch.
21314 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
21315 that could happen on 32-bit platforms with 64-bit time_t. Also fix
21316 a memory leak when requesting a hidden service descriptor we've
21317 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
21320 o Directory authority changes:
21321 - Change IP address for dannenberg (v3 directory authority), and
21322 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
21323 service directory authority) from the list.
21326 - Refactor resolve_my_address() to not use gethostbyname() anymore.
21327 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
21330 - Avoid a mad rush at the beginning of each month when each client
21331 rotates half of its guards. Instead we spread the rotation out
21332 throughout the month, but we still avoid leaving a precise timestamp
21333 in the state file about when we first picked the guard. Improves
21334 over the behavior introduced in 0.1.2.17.
21337 Changes in version 0.2.2.8-alpha - 2010-01-26
21338 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
21339 causing bridge relays to disappear. If you're running a bridge,
21343 - Fix a memory corruption bug on bridges that occurred during the
21344 inclusion of stats data in extra-info descriptors. Also fix the
21345 interface for geoip_get_bridge_stats* to prevent similar bugs in
21346 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
21347 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
21350 - Ignore OutboundBindAddress when connecting to localhost.
21351 Connections to localhost need to come _from_ localhost, or else
21352 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
21356 Changes in version 0.2.2.7-alpha - 2010-01-19
21357 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
21358 as laying the groundwork for further relay-side performance fixes. It
21359 also starts cleaning up client behavior with respect to the EntryNodes,
21360 ExitNodes, and StrictNodes config options.
21362 This release also rotates two directory authority keys, due to a
21363 security breach of some of the Torproject servers.
21365 o Directory authority changes:
21366 - Rotate keys (both v3 identity and relay identity) for moria1
21369 o Major features (performance):
21370 - We were selecting our guards uniformly at random, and then weighting
21371 which of our guards we'd use uniformly at random. This imbalance
21372 meant that Tor clients were severely limited on throughput (and
21373 probably latency too) by the first hop in their circuit. Now we
21374 select guards weighted by currently advertised bandwidth. We also
21375 automatically discard guards picked using the old algorithm. Fixes
21376 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
21377 - When choosing which cells to relay first, relays can now favor
21378 circuits that have been quiet recently, to provide lower latency
21379 for low-volume circuits. By default, relays enable or disable this
21380 feature based on a setting in the consensus. You can override
21381 this default by using the new "CircuitPriorityHalflife" config
21382 option. Design and code by Ian Goldberg, Can Tang, and Chris
21384 - Add separate per-conn write limiting to go with the per-conn read
21385 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
21386 but never per-conn write limits.
21387 - New consensus params "bwconnrate" and "bwconnburst" to let us
21388 rate-limit client connections as they enter the network. It's
21389 controlled in the consensus so we can turn it on and off for
21390 experiments. It's starting out off. Based on proposal 163.
21392 o Major features (relay selection options):
21393 - Switch to a StrictNodes config option, rather than the previous
21394 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
21395 "StrictExcludeNodes" option.
21396 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
21397 change during a config reload, mark and discard all our origin
21398 circuits. This fix should address edge cases where we change the
21399 config options and but then choose a circuit that we created before
21401 - If EntryNodes or ExitNodes are set, be more willing to use an
21402 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
21404 - Make EntryNodes config option much more aggressive even when
21405 StrictNodes is not set. Before it would prepend your requested
21406 entrynodes to your list of guard nodes, but feel free to use others
21407 after that. Now it chooses only from your EntryNodes if any of
21408 those are available, and only falls back to others if a) they're
21409 all down and b) StrictNodes is not set.
21410 - Now we refresh your entry guards from EntryNodes at each consensus
21411 fetch -- rather than just at startup and then they slowly rot as
21412 the network changes.
21415 - Stop bridge directory authorities from answering dbg-stability.txt
21416 directory queries, which would let people fetch a list of all
21417 bridge identities they track. Bugfix on 0.2.1.6-alpha.
21420 - Log a notice when we get a new control connection. Now it's easier
21421 for security-conscious users to recognize when a local application
21422 is knocking on their controller door. Suggested by bug 1196.
21423 - New config option "CircuitStreamTimeout" to override our internal
21424 timeout schedule for how many seconds until we detach a stream from
21425 a circuit and try a new circuit. If your network is particularly
21426 slow, you might want to set this to a number like 60.
21427 - New controller command "getinfo config-text". It returns the
21428 contents that Tor would write if you send it a SAVECONF command,
21429 so the controller can write the file to disk itself.
21430 - New options for SafeLogging to allow scrubbing only log messages
21431 generated while acting as a relay.
21432 - Ship the bridges spec file in the tarball too.
21433 - Avoid a mad rush at the beginning of each month when each client
21434 rotates half of its guards. Instead we spread the rotation out
21435 throughout the month, but we still avoid leaving a precise timestamp
21436 in the state file about when we first picked the guard. Improves
21437 over the behavior introduced in 0.1.2.17.
21439 o Minor bugfixes (compiling):
21440 - Fix compilation on OS X 10.3, which has a stub mlockall() but
21441 hides it. Bugfix on 0.2.2.6-alpha.
21442 - Fix compilation on Solaris by removing support for the
21443 DisableAllSwap config option. Solaris doesn't have an rlimit for
21444 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
21447 o Minor bugfixes (crashes):
21448 - Do not segfault when writing buffer stats when we haven't observed
21449 a single circuit to report about. Found by Fabian Lanze. Bugfix on
21451 - If we're in the pathological case where there's no exit bandwidth
21452 but there is non-exit bandwidth, or no guard bandwidth but there
21453 is non-guard bandwidth, don't crash during path selection. Bugfix
21455 - Fix an impossible-to-actually-trigger buffer overflow in relay
21456 descriptor generation. Bugfix on 0.1.0.15.
21458 o Minor bugfixes (privacy):
21459 - Fix an instance where a Tor directory mirror might accidentally
21460 log the IP address of a misbehaving Tor client. Bugfix on
21462 - Don't list Windows capabilities in relay descriptors. We never made
21463 use of them, and maybe it's a bad idea to publish them. Bugfix
21466 o Minor bugfixes (other):
21467 - Resolve an edge case in path weighting that could make us misweight
21468 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
21469 - Fix statistics on client numbers by country as seen by bridges that
21470 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
21471 intervals instead of variable 12-to-48-hour intervals.
21472 - After we free an internal connection structure, overwrite it
21473 with a different memory value than we use for overwriting a freed
21474 internal circuit structure. Should help with debugging. Suggested
21476 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
21479 o Removed features:
21480 - Remove the HSAuthorityRecordStats option that version 0 hidden
21481 service authorities could have used to track statistics of overall
21482 hidden service usage.
21485 Changes in version 0.2.1.22 - 2010-01-19
21486 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
21487 authorities -- it would tell you its whole history of bridge descriptors
21488 if you make the right directory request. This stable update also
21489 rotates two of the seven v3 directory authority keys and locations.
21491 o Directory authority changes:
21492 - Rotate keys (both v3 identity and relay identity) for moria1
21496 - Stop bridge directory authorities from answering dbg-stability.txt
21497 directory queries, which would let people fetch a list of all
21498 bridge identities they track. Bugfix on 0.2.1.6-alpha.
21501 Changes in version 0.2.1.21 - 2009-12-21
21502 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
21503 library. If you use Tor on Linux / Unix and you're getting SSL
21504 renegotiation errors, upgrading should help. We also recommend an
21505 upgrade if you're an exit relay.
21508 - Work around a security feature in OpenSSL 0.9.8l that prevents our
21509 handshake from working unless we explicitly tell OpenSSL that we
21510 are using SSL renegotiation safely. We are, of course, but OpenSSL
21511 0.9.8l won't work unless we say we are.
21512 - Avoid crashing if the client is trying to upload many bytes and the
21513 circuit gets torn down at the same time, or if the flip side
21514 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
21517 - Do not refuse to learn about authority certs and v2 networkstatus
21518 documents that are older than the latest consensus. This bug might
21519 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
21520 Spotted and fixed by xmux.
21521 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
21522 trigger platform-specific option misparsing case found by Coverity
21524 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
21525 trigger assert. Fixes bug 1173.
21528 Changes in version 0.2.2.6-alpha - 2009-11-19
21529 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
21530 support for the new lower-footprint "microdescriptor" directory design,
21531 future-proofing our consensus format against new hash functions or
21532 other changes, and an Android port. It also makes Tor compatible with
21533 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
21536 - Directory authorities can now create, vote on, and serve multiple
21537 parallel formats of directory data as part of their voting process.
21538 Partially implements Proposal 162: "Publish the consensus in
21540 - Directory authorities can now agree on and publish small summaries
21541 of router information that clients can use in place of regular
21542 server descriptors. This transition will eventually allow clients
21543 to use far less bandwidth for downloading information about the
21544 network. Begins the implementation of Proposal 158: "Clients
21545 download consensus + microdescriptors".
21546 - The directory voting system is now extensible to use multiple hash
21547 algorithms for signatures and resource selection. Newer formats
21548 are signed with SHA256, with a possibility for moving to a better
21549 hash algorithm in the future.
21550 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
21551 current and future memory pages via mlockall(). On supported
21552 platforms (modern Linux and probably BSD but not Windows or OS X),
21553 this should effectively disable any and all attempts to page out
21554 memory. This option requires that you start your Tor as root --
21555 if you use DisableAllSwap, please consider using the User option
21556 to properly reduce the privileges of your Tor.
21557 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
21558 to help Tor build correctly for Android phones.
21561 - Work around a security feature in OpenSSL 0.9.8l that prevents our
21562 handshake from working unless we explicitly tell OpenSSL that we
21563 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
21564 won't work unless we say we are.
21567 - Fix a crash bug when trying to initialize the evdns module in
21568 Libevent 2. Bugfix on 0.2.1.16-rc.
21569 - Stop logging at severity 'warn' when some other Tor client tries
21570 to establish a circuit with us using weak DH keys. It's a protocol
21571 violation, but that doesn't mean ordinary users need to hear about
21572 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
21573 - Do not refuse to learn about authority certs and v2 networkstatus
21574 documents that are older than the latest consensus. This bug might
21575 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
21576 Spotted and fixed by xmux.
21577 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
21578 - If all authorities restart at once right before a consensus vote,
21579 nobody will vote about "Running", and clients will get a consensus
21580 with no usable relays. Instead, authorities refuse to build a
21581 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
21582 - If your relay can't keep up with the number of incoming create
21583 cells, it would log one warning per failure into your logs. Limit
21584 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
21585 - Bridges now use "reject *:*" as their default exit policy. Bugfix
21586 on 0.2.0.3-alpha; fixes bug 1113.
21587 - Fix a memory leak on directory authorities during voting that was
21588 introduced in 0.2.2.1-alpha. Found via valgrind.
21591 Changes in version 0.2.1.20 - 2009-10-15
21592 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
21593 services at once, prepares for more performance improvements, and
21594 fixes a bunch of smaller bugs.
21596 The Windows and OS X bundles also include a more recent Vidalia,
21597 and switch from Privoxy to Polipo.
21599 The OS X installers are now drag and drop. It's best to un-install
21600 Tor/Vidalia and then install this new bundle, rather than upgrade. If
21601 you want to upgrade, you'll need to update the paths for Tor and Polipo
21602 in the Vidalia Settings window.
21605 - Send circuit or stream sendme cells when our window has decreased
21606 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
21607 by Karsten when testing the "reduce circuit window" performance
21608 patch. Bugfix on the 54th commit on Tor -- from July 2002,
21609 before the release of Tor 0.0.0. This is the new winner of the
21611 - Fix a remotely triggerable memory leak when a consensus document
21612 contains more than one signature from the same voter. Bugfix on
21614 - Avoid segfault in rare cases when finishing an introduction circuit
21615 as a client and finding out that we don't have an introduction key
21616 for it. Fixes bug 1073. Reported by Aaron Swartz.
21619 - Tor now reads the "circwindow" parameter out of the consensus,
21620 and uses that value for its circuit package window rather than the
21621 default of 1000 cells. Begins the implementation of proposal 168.
21623 o New directory authorities:
21624 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
21626 - Move moria1 and tonga to alternate IP addresses.
21629 - Fix a signed/unsigned compile warning in 0.2.1.19.
21630 - Fix possible segmentation fault on directory authorities. Bugfix on
21632 - Fix an extremely rare infinite recursion bug that could occur if
21633 we tried to log a message after shutting down the log subsystem.
21634 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
21635 - Fix an obscure bug where hidden services on 64-bit big-endian
21636 systems might mis-read the timestamp in v3 introduce cells, and
21637 refuse to connect back to the client. Discovered by "rotor".
21638 Bugfix on 0.2.1.6-alpha.
21639 - We were triggering a CLOCK_SKEW controller status event whenever
21640 we connect via the v2 connection protocol to any relay that has
21641 a wrong clock. Instead, we should only inform the controller when
21642 it's a trusted authority that claims our clock is wrong. Bugfix
21643 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
21644 - We were telling the controller about CHECKING_REACHABILITY and
21645 REACHABILITY_FAILED status events whenever we launch a testing
21646 circuit or notice that one has failed. Instead, only tell the
21647 controller when we want to inform the user of overall success or
21648 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
21650 - Don't warn when we're using a circuit that ends with a node
21651 excluded in ExcludeExitNodes, but the circuit is not used to access
21652 the outside world. This should help fix bug 1090. Bugfix on
21654 - Work around a small memory leak in some versions of OpenSSL that
21655 stopped the memory used by the hostname TLS extension from being
21659 - Add a "getinfo status/accepted-server-descriptor" controller
21660 command, which is the recommended way for controllers to learn
21661 whether our server descriptor has been successfully received by at
21662 least on directory authority. Un-recommend good-server-descriptor
21663 getinfo and status events until we have a better design for them.
21666 Changes in version 0.2.2.5-alpha - 2009-10-11
21667 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
21670 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
21672 o Directory authorities:
21673 - Temporarily (just for this release) move dizum to an alternate
21677 Changes in version 0.2.2.4-alpha - 2009-10-10
21678 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
21679 introduces a new unit test framework, shifts directry authority
21680 addresses around to reduce the impact from recent blocking events,
21681 and fixes a few smaller bugs.
21684 - Fix several more asserts in the circuit_build_times code, for
21685 example one that causes Tor to fail to start once we have
21686 accumulated 5000 build times in the state file. Bugfixes on
21687 0.2.2.2-alpha; fixes bug 1108.
21689 o New directory authorities:
21690 - Move moria1 and Tonga to alternate IP addresses.
21693 - Log SSL state transitions at debug level during handshake, and
21694 include SSL states in error messages. This may help debug future
21695 SSL handshake issues.
21696 - Add a new "Handshake" log domain for activities that happen
21697 during the TLS handshake.
21698 - Revert to the "June 3 2009" ip-to-country file. The September one
21699 seems to have removed most US IP addresses.
21700 - Directory authorities now reject Tor relays with versions less than
21701 0.1.2.14. This step cuts out four relays from the current network,
21702 none of which are very big.
21705 - Fix a couple of smaller issues with gathering statistics. Bugfixes
21707 - Fix two memory leaks in the error case of
21708 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
21709 - Don't count one-hop circuits when we're estimating how long it
21710 takes circuits to build on average. Otherwise we'll set our circuit
21711 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
21712 - Directory authorities no longer change their opinion of, or vote on,
21713 whether a router is Running, unless they have themselves been
21714 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
21717 o Code simplifications and refactoring:
21718 - Revise our unit tests to use the "tinytest" framework, so we
21719 can run tests in their own processes, have smarter setup/teardown
21720 code, and so on. The unit test code has moved to its own
21721 subdirectory, and has been split into multiple modules.
21724 Changes in version 0.2.2.3-alpha - 2009-09-23
21725 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
21728 - Fix an overzealous assert in our new circuit build timeout code.
21729 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
21732 - If the networkstatus consensus tells us that we should use a
21733 negative circuit package window, ignore it. Otherwise we'll
21734 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
21737 Changes in version 0.2.2.2-alpha - 2009-09-21
21738 Tor 0.2.2.2-alpha introduces our latest performance improvement for
21739 clients: Tor tracks the average time it takes to build a circuit, and
21740 avoids using circuits that take too long to build. For fast connections,
21741 this feature can cut your expected latency in half. For slow or flaky
21742 connections, it could ruin your Tor experience. Let us know if it does!
21745 - Tor now tracks how long it takes to build client-side circuits
21746 over time, and adapts its timeout to local network performance.
21747 Since a circuit that takes a long time to build will also provide
21748 bad performance, we get significant latency improvements by
21749 discarding the slowest 20% of circuits. Specifically, Tor creates
21750 circuits more aggressively than usual until it has enough data
21751 points for a good timeout estimate. Implements proposal 151.
21752 We are especially looking for reports (good and bad) from users with
21753 both EDGE and broadband connections that can move from broadband
21754 to EDGE and find out if the build-time data in the .tor/state gets
21755 reset without loss of Tor usability. You should also see a notice
21756 log message telling you that Tor has reset its timeout.
21757 - Directory authorities can now vote on arbitrary integer values as
21758 part of the consensus process. This is designed to help set
21759 network-wide parameters. Implements proposal 167.
21760 - Tor now reads the "circwindow" parameter out of the consensus,
21761 and uses that value for its circuit package window rather than the
21762 default of 1000 cells. Begins the implementation of proposal 168.
21765 - Fix a remotely triggerable memory leak when a consensus document
21766 contains more than one signature from the same voter. Bugfix on
21770 - Fix an extremely rare infinite recursion bug that could occur if
21771 we tried to log a message after shutting down the log subsystem.
21772 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
21773 - Fix parsing for memory or time units given without a space between
21774 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
21775 - A networkstatus vote must contain exactly one signature. Spec
21776 conformance issue. Bugfix on 0.2.0.3-alpha.
21777 - Fix an obscure bug where hidden services on 64-bit big-endian
21778 systems might mis-read the timestamp in v3 introduce cells, and
21779 refuse to connect back to the client. Discovered by "rotor".
21780 Bugfix on 0.2.1.6-alpha.
21781 - We were triggering a CLOCK_SKEW controller status event whenever
21782 we connect via the v2 connection protocol to any relay that has
21783 a wrong clock. Instead, we should only inform the controller when
21784 it's a trusted authority that claims our clock is wrong. Bugfix
21785 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
21786 - We were telling the controller about CHECKING_REACHABILITY and
21787 REACHABILITY_FAILED status events whenever we launch a testing
21788 circuit or notice that one has failed. Instead, only tell the
21789 controller when we want to inform the user of overall success or
21790 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
21792 - Don't warn when we're using a circuit that ends with a node
21793 excluded in ExcludeExitNodes, but the circuit is not used to access
21794 the outside world. This should help fix bug 1090, but more problems
21795 remain. Bugfix on 0.2.1.6-alpha.
21796 - Work around a small memory leak in some versions of OpenSSL that
21797 stopped the memory used by the hostname TLS extension from being
21799 - Make our 'torify' script more portable; if we have only one of
21800 'torsocks' or 'tsocks' installed, don't complain to the user;
21801 and explain our warning about tsocks better.
21804 - Add a "getinfo status/accepted-server-descriptor" controller
21805 command, which is the recommended way for controllers to learn
21806 whether our server descriptor has been successfully received by at
21807 least on directory authority. Un-recommend good-server-descriptor
21808 getinfo and status events until we have a better design for them.
21809 - Update to the "September 4 2009" ip-to-country file.
21812 Changes in version 0.2.2.1-alpha - 2009-08-26
21813 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
21814 Tor clients to bootstrap on networks where only port 80 is reachable,
21815 makes it more straightforward to support hardware crypto accelerators,
21816 and starts the groundwork for gathering stats safely at relays.
21819 - Start the process of disabling ".exit" address notation, since it
21820 can be used for a variety of esoteric application-level attacks
21821 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
21824 o New directory authorities:
21825 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
21829 - New AccelName and AccelDir options add support for dynamic OpenSSL
21830 hardware crypto acceleration engines.
21831 - Tor now supports tunneling all of its outgoing connections over
21832 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
21833 configuration options. Code by Christopher Davis.
21836 - Send circuit or stream sendme cells when our window has decreased
21837 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
21838 by Karsten when testing the "reduce circuit window" performance
21839 patch. Bugfix on the 54th commit on Tor -- from July 2002,
21840 before the release of Tor 0.0.0. This is the new winner of the
21843 o New options for gathering stats safely:
21844 - Directory mirrors that set "DirReqStatistics 1" write statistics
21845 about directory requests to disk every 24 hours. As compared to the
21846 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
21847 1) stats are written to disk exactly every 24 hours; 2) estimated
21848 shares of v2 and v3 requests are determined as mean values, not at
21849 the end of a measurement period; 3) unresolved requests are listed
21850 with country code '??'; 4) directories also measure download times.
21851 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
21852 number of exit streams and transferred bytes per port to disk every
21854 - Relays that set "CellStatistics 1" write statistics on how long
21855 cells spend in their circuit queues to disk every 24 hours.
21856 - Entry nodes that set "EntryStatistics 1" write statistics on the
21857 rough number and origins of connecting clients to disk every 24
21859 - Relays that write any of the above statistics to disk and set
21860 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
21861 their extra-info documents.
21864 - New --digests command-line switch to output the digests of the
21865 source files Tor was built with.
21866 - The "torify" script now uses torsocks where available.
21867 - The memarea code now uses a sentinel value at the end of each area
21868 to make sure nothing writes beyond the end of an area. This might
21869 help debug some conceivable causes of bug 930.
21870 - Time and memory units in the configuration file can now be set to
21871 fractional units. For example, "2.5 GB" is now a valid value for
21873 - Certain Tor clients (such as those behind check.torproject.org) may
21874 want to fetch the consensus in an extra early manner. To enable this
21875 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
21876 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
21877 as only certain clients who must have this information sooner should
21879 - Instead of adding the svn revision to the Tor version string, report
21880 the git commit (when we're building from a git checkout).
21883 - If any of the v3 certs we download are unparseable, we should
21884 actually notice the failure so we don't retry indefinitely. Bugfix
21885 on 0.2.0.x; reported by "rotator".
21886 - If the cached cert file is unparseable, warn but don't exit.
21887 - Fix possible segmentation fault on directory authorities. Bugfix on
21889 - When Tor fails to parse a descriptor of any kind, dump it to disk.
21890 Might help diagnosing bug 1051.
21892 o Deprecated and removed features:
21893 - The controller no longer accepts the old obsolete "addr-mappings/"
21894 or "unregistered-servers-" GETINFO values.
21895 - Hidden services no longer publish version 0 descriptors, and clients
21896 do not request or use version 0 descriptors. However, the old hidden
21897 service authorities still accept and serve version 0 descriptors
21898 when contacted by older hidden services/clients.
21899 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
21900 always on; using them is necessary for correct forward-compatible
21902 - Remove support for .noconnect style addresses. Nobody was using
21903 them, and they provided another avenue for detecting Tor users
21904 via application-level web tricks.
21906 o Packaging changes:
21907 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
21908 installer bundles. See
21909 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
21910 for details of what's new in Vidalia 0.2.3.
21911 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
21912 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
21913 configuration file, rather than the old Privoxy.
21914 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
21915 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
21916 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
21917 better compatibility with OS X 10.6, aka Snow Leopard.
21918 - OS X Vidalia Bundle: The multi-package installer is now replaced
21919 by a simple drag and drop to the /Applications folder. This change
21920 occurred with the upgrade to Vidalia 0.2.3.
21923 Changes in version 0.2.1.19 - 2009-07-28
21924 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
21925 services on Tor 0.2.1.3-alpha through 0.2.1.18.
21928 - Make accessing hidden services on 0.2.1.x work right again.
21929 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
21930 part of patch provided by "optimist".
21933 - When a relay/bridge is writing out its identity key fingerprint to
21934 the "fingerprint" file and to its logs, write it without spaces. Now
21935 it will look like the fingerprints in our bridges documentation,
21936 and confuse fewer users.
21939 - Relays no longer publish a new server descriptor if they change
21940 their MaxAdvertisedBandwidth config option but it doesn't end up
21941 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
21942 fixes bug 1026. Patch from Sebastian.
21943 - Avoid leaking memory every time we get a create cell but we have
21944 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
21945 fixes bug 1034. Reported by BarkerJr.
21948 Changes in version 0.2.1.18 - 2009-07-24
21949 Tor 0.2.1.18 lays the foundations for performance improvements,
21950 adds status events to help users diagnose bootstrap problems, adds
21951 optional authentication/authorization for hidden services, fixes a
21952 variety of potential anonymity problems, and includes a huge pile of
21953 other features and bug fixes.
21956 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
21959 Changes in version 0.2.1.17-rc - 2009-07-07
21960 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
21961 candidate for the 0.2.1.x series. It lays the groundwork for further
21962 client performance improvements, and also fixes a big bug with directory
21963 authorities that were causing them to assign Guard and Stable flags
21966 The Windows bundles also finally include the geoip database that we
21967 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
21968 should actually install Torbutton rather than giving you a cryptic
21969 failure message (oops).
21972 - Clients now use the bandwidth values in the consensus, rather than
21973 the bandwidth values in each relay descriptor. This approach opens
21974 the door to more accurate bandwidth estimates once the directory
21975 authorities start doing active measurements. Implements more of
21979 - When Tor clients restart after 1-5 days, they discard all their
21980 cached descriptors as too old, but they still use the cached
21981 consensus document. This approach is good for robustness, but
21982 bad for performance: since they don't know any bandwidths, they
21983 end up choosing at random rather than weighting their choice by
21984 speed. Fixed by the above feature of putting bandwidths in the
21985 consensus. Bugfix on 0.2.0.x.
21986 - Directory authorities were neglecting to mark relays down in their
21987 internal histories if the relays fall off the routerlist without
21988 ever being found unreachable. So there were relays in the histories
21989 that haven't been seen for eight months, and are listed as being
21990 up for eight months. This wreaked havoc on the "median wfu"
21991 and "median mtbf" calculations, in turn making Guard and Stable
21992 flags very wrong, hurting network performance. Fixes bugs 696 and
21993 969. Bugfix on 0.2.0.6-alpha.
21996 - Serve the DirPortFrontPage page even when we have been approaching
21997 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
21998 - The control port would close the connection before flushing long
21999 replies, such as the network consensus, if a QUIT command was issued
22000 before the reply had completed. Now, the control port flushes all
22001 pending replies before closing the connection. Also fixed a spurious
22002 warning when a QUIT command is issued after a malformed or rejected
22003 AUTHENTICATE command, but before the connection was closed. Patch
22004 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
22005 - When we can't find an intro key for a v2 hidden service descriptor,
22006 fall back to the v0 hidden service descriptor and log a bug message.
22007 Workaround for bug 1024.
22008 - Fix a log message that did not respect the SafeLogging option.
22012 - If we're a relay and we change our IP address, be more verbose
22013 about the reason that made us change. Should help track down
22014 further bugs for relays on dynamic IP addresses.
22017 Changes in version 0.2.0.35 - 2009-06-24
22019 - Avoid crashing in the presence of certain malformed descriptors.
22020 Found by lark, and by automated fuzzing.
22021 - Fix an edge case where a malicious exit relay could convince a
22022 controller that the client's DNS question resolves to an internal IP
22023 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
22026 - Finally fix the bug where dynamic-IP relays disappear when their
22027 IP address changes: directory mirrors were mistakenly telling
22028 them their old address if they asked via begin_dir, so they
22029 never got an accurate answer about their new address, so they
22030 just vanished after a day. For belt-and-suspenders, relays that
22031 don't set Address in their config now avoid using begin_dir for
22032 all direct connections. Should fix bugs 827, 883, and 900.
22033 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
22034 that would occur on some exit nodes when DNS failures and timeouts
22035 occurred in certain patterns. Fix for bug 957.
22038 - When starting with a cache over a few days old, do not leak
22039 memory for the obsolete router descriptors in it. Bugfix on
22040 0.2.0.33; fixes bug 672.
22041 - Hidden service clients didn't use a cached service descriptor that
22042 was older than 15 minutes, but wouldn't fetch a new one either,
22043 because there was already one in the cache. Now, fetch a v2
22044 descriptor unless the same descriptor was added to the cache within
22045 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
22048 Changes in version 0.2.1.16-rc - 2009-06-20
22049 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
22050 a bunch of minor bugs.
22053 - Fix an edge case where a malicious exit relay could convince a
22054 controller that the client's DNS question resolves to an internal IP
22055 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
22057 o Major performance improvements (on 0.2.0.x):
22058 - Disable and refactor some debugging checks that forced a linear scan
22059 over the whole server-side DNS cache. These accounted for over 50%
22060 of CPU time on a relatively busy exit node's gprof profile. Found
22062 - Disable some debugging checks that appeared in exit node profile
22066 - Update to the "June 3 2009" ip-to-country file.
22067 - Do not have tor-resolve automatically refuse all .onion addresses;
22068 if AutomapHostsOnResolve is set in your torrc, this will work fine.
22070 o Minor bugfixes (on 0.2.0.x):
22071 - Log correct error messages for DNS-related network errors on
22073 - Fix a race condition that could cause crashes or memory corruption
22074 when running as a server with a controller listening for log
22076 - Avoid crashing when we have a policy specified in a DirPolicy or
22077 SocksPolicy or ReachableAddresses option with ports set on it,
22078 and we re-load the policy. May fix bug 996.
22079 - Hidden service clients didn't use a cached service descriptor that
22080 was older than 15 minutes, but wouldn't fetch a new one either,
22081 because there was already one in the cache. Now, fetch a v2
22082 descriptor unless the same descriptor was added to the cache within
22083 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
22085 o Minor bugfixes (on 0.2.1.x):
22086 - Don't warn users about low port and hibernation mix when they
22087 provide a *ListenAddress directive to fix that. Bugfix on
22089 - When switching back and forth between bridge mode, do not start
22090 gathering GeoIP data until two hours have passed.
22091 - Do not complain that the user has requested an excluded node as
22092 an exit when the node is not really an exit. This could happen
22093 because the circuit was for testing, or an introduction point.
22097 Changes in version 0.2.1.15-rc - 2009-05-25
22098 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
22099 series. It fixes a major bug on fast exit relays, as well as a variety
22100 of more minor bugs.
22102 o Major bugfixes (on 0.2.0.x):
22103 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
22104 that would occur on some exit nodes when DNS failures and timeouts
22105 occurred in certain patterns. Fix for bug 957.
22107 o Minor bugfixes (on 0.2.0.x):
22108 - Actually return -1 in the error case for read_bandwidth_usage().
22109 Harmless bug, since we currently don't care about the return value
22110 anywhere. Bugfix on 0.2.0.9-alpha.
22111 - Provide a more useful log message if bug 977 (related to buffer
22112 freelists) ever reappears, and do not crash right away.
22113 - Fix an assertion failure on 64-bit platforms when we allocated
22114 memory right up to the end of a memarea, then realigned the memory
22115 one step beyond the end. Fixes a possible cause of bug 930.
22116 - Protect the count of open sockets with a mutex, so we can't
22117 corrupt it when two threads are closing or opening sockets at once.
22118 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
22119 - Don't allow a bridge to publish its router descriptor to a
22120 non-bridge directory authority. Fixes part of bug 932.
22121 - When we change to or from being a bridge, reset our counts of
22122 client usage by country. Fixes bug 932.
22123 - Fix a bug that made stream bandwidth get misreported to the
22125 - Stop using malloc_usable_size() to use more area than we had
22126 actually allocated: it was safe, but made valgrind really unhappy.
22127 - Fix a memory leak when v3 directory authorities load their keys
22128 and cert from disk. Bugfix on 0.2.0.1-alpha.
22130 o Minor bugfixes (on 0.2.1.x):
22131 - Fix use of freed memory when deciding to mark a non-addable
22132 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
22135 Changes in version 0.2.1.14-rc - 2009-04-12
22136 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
22137 series. It begins fixing some major performance problems, and also
22138 finally addresses the bug that was causing relays on dynamic IP
22139 addresses to fall out of the directory.
22142 - Clients replace entry guards that were chosen more than a few months
22143 ago. This change should significantly improve client performance,
22144 especially once more people upgrade, since relays that have been
22145 a guard for a long time are currently overloaded.
22147 o Major bugfixes (on 0.2.0):
22148 - Finally fix the bug where dynamic-IP relays disappear when their
22149 IP address changes: directory mirrors were mistakenly telling
22150 them their old address if they asked via begin_dir, so they
22151 never got an accurate answer about their new address, so they
22152 just vanished after a day. For belt-and-suspenders, relays that
22153 don't set Address in their config now avoid using begin_dir for
22154 all direct connections. Should fix bugs 827, 883, and 900.
22155 - Relays were falling out of the networkstatus consensus for
22156 part of a day if they changed their local config but the
22157 authorities discarded their new descriptor as "not sufficiently
22158 different". Now directory authorities accept a descriptor as changed
22159 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
22160 patch by Sebastian.
22161 - Avoid crashing in the presence of certain malformed descriptors.
22162 Found by lark, and by automated fuzzing.
22165 - When generating circuit events with verbose nicknames for
22166 controllers, try harder to look up nicknames for routers on a
22167 circuit. (Previously, we would look in the router descriptors we had
22168 for nicknames, but not in the consensus.) Partial fix for bug 941.
22169 - If the bridge config line doesn't specify a port, assume 443.
22170 This makes bridge lines a bit smaller and easier for users to
22172 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
22173 bytes (aka 20KB/s), to match our documentation. Also update
22174 directory authorities so they always assign the Fast flag to relays
22175 with 20KB/s of capacity. Now people running relays won't suddenly
22176 find themselves not seeing any use, if the network gets faster
22178 - Update to the "April 3 2009" ip-to-country file.
22181 - Avoid trying to print raw memory to the logs when we decide to
22182 give up on downloading a given relay descriptor. Bugfix on
22184 - In tor-resolve, when the Tor client to use is specified by
22185 <hostname>:<port>, actually use the specified port rather than
22186 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
22187 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
22188 - When starting with a cache over a few days old, do not leak
22189 memory for the obsolete router descriptors in it. Bugfix on
22191 - Avoid double-free on list of successfully uploaded hidden
22192 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
22193 - Change memarea_strndup() implementation to work even when
22194 duplicating a string at the end of a page. This bug was
22195 harmless for now, but could have meant crashes later. Fix by
22196 lark. Bugfix on 0.2.1.1-alpha.
22197 - Limit uploaded directory documents to be 16M rather than 500K.
22198 The directory authorities were refusing v3 consensus votes from
22199 other authorities, since the votes are now 504K. Fixes bug 959;
22200 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
22201 - Directory authorities should never send a 503 "busy" response to
22202 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
22206 Changes in version 0.2.1.13-alpha - 2009-03-09
22207 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
22208 cleanups. We're finally getting close to a release candidate.
22211 - Correctly update the list of which countries we exclude as
22212 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
22213 lark. Bugfix on 0.2.1.6-alpha.
22215 o Minor bugfixes (on 0.2.0.x and earlier):
22216 - Automatically detect MacOSX versions earlier than 10.4.0, and
22217 disable kqueue from inside Tor when running with these versions.
22218 We previously did this from the startup script, but that was no
22219 help to people who didn't use the startup script. Resolves bug 863.
22220 - When we had picked an exit node for a connection, but marked it as
22221 "optional", and it turned out we had no onion key for the exit,
22222 stop wanting that exit and try again. This situation may not
22223 be possible now, but will probably become feasible with proposal
22224 158. Spotted by rovv. Fixes another case of bug 752.
22225 - Clients no longer cache certificates for authorities they do not
22226 recognize. Bugfix on 0.2.0.9-alpha.
22227 - When we can't transmit a DNS request due to a network error, retry
22228 it after a while, and eventually transmit a failing response to
22229 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
22230 - If the controller claimed responsibility for a stream, but that
22231 stream never finished making its connection, it would live
22232 forever in circuit_wait state. Now we close it after SocksTimeout
22233 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
22234 - Drop begin cells to a hidden service if they come from the middle
22235 of a circuit. Patch from lark.
22236 - When we erroneously receive two EXTEND cells for the same circuit
22237 ID on the same connection, drop the second. Patch from lark.
22238 - Fix a crash that occurs on exit nodes when a nameserver request
22239 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
22240 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
22242 - Do not assume that a stack-allocated character array will be
22243 64-bit aligned on platforms that demand that uint64_t access is
22244 aligned. Possible fix for bug 604.
22245 - Parse dates and IPv4 addresses in a locale- and libc-independent
22246 manner, to avoid platform-dependent behavior on malformed input.
22247 - Build correctly when configured to build outside the main source
22248 path. Patch from Michael Gold.
22249 - We were already rejecting relay begin cells with destination port
22250 of 0. Now also reject extend cells with destination port or address
22251 of 0. Suggested by lark.
22253 o Minor bugfixes (on 0.2.1.x):
22254 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
22255 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
22256 - If we're an exit node, scrub the IP address to which we are exiting
22257 in the logs. Bugfix on 0.2.1.8-alpha.
22260 - On Linux, use the prctl call to re-enable core dumps when the user
22262 - New controller event NEWCONSENSUS that lists the networkstatus
22263 lines for every recommended relay. Now controllers like Torflow
22264 can keep up-to-date on which relays they should be using.
22265 - Update to the "February 26 2009" ip-to-country file.
22268 Changes in version 0.2.0.34 - 2009-02-08
22269 Tor 0.2.0.34 features several more security-related fixes. You should
22270 upgrade, especially if you run an exit relay (remote crash) or a
22271 directory authority (remote infinite loop), or you're on an older
22272 (pre-XP) or not-recently-patched Windows (remote exploit).
22274 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
22275 have many known flaws, and nobody should be using them. You should
22276 upgrade. If you're using a Linux or BSD and its packages are obsolete,
22277 stop using those packages and upgrade anyway.
22280 - Fix an infinite-loop bug on handling corrupt votes under certain
22281 circumstances. Bugfix on 0.2.0.8-alpha.
22282 - Fix a temporary DoS vulnerability that could be performed by
22283 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
22284 - Avoid a potential crash on exit nodes when processing malformed
22285 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
22286 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
22287 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
22290 - Fix compilation on systems where time_t is a 64-bit integer.
22291 Patch from Matthias Drochner.
22292 - Don't consider expiring already-closed client connections. Fixes
22293 bug 893. Bugfix on 0.0.2pre20.
22296 Changes in version 0.2.1.12-alpha - 2009-02-08
22297 Tor 0.2.1.12-alpha features several more security-related fixes. You
22298 should upgrade, especially if you run an exit relay (remote crash) or
22299 a directory authority (remote infinite loop), or you're on an older
22300 (pre-XP) or not-recently-patched Windows (remote exploit). It also
22301 includes a big pile of minor bugfixes and cleanups.
22304 - Fix an infinite-loop bug on handling corrupt votes under certain
22305 circumstances. Bugfix on 0.2.0.8-alpha.
22306 - Fix a temporary DoS vulnerability that could be performed by
22307 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
22308 - Avoid a potential crash on exit nodes when processing malformed
22309 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
22312 - Let controllers actually ask for the "clients_seen" event for
22313 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
22314 reported by Matt Edman.
22315 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
22317 - Fix a bug in address parsing that was preventing bridges or hidden
22318 service targets from being at IPv6 addresses.
22319 - Solve a bug that kept hardware crypto acceleration from getting
22320 enabled when accounting was turned on. Fixes bug 907. Bugfix on
22322 - Remove a bash-ism from configure.in to build properly on non-Linux
22323 platforms. Bugfix on 0.2.1.1-alpha.
22324 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
22325 headers. Bugfix on 0.2.0.10-alpha.
22326 - Don't consider expiring already-closed client connections. Fixes
22327 bug 893. Bugfix on 0.0.2pre20.
22328 - Fix another interesting corner-case of bug 891 spotted by rovv:
22329 Previously, if two hosts had different amounts of clock drift, and
22330 one of them created a new connection with just the wrong timing,
22331 the other might decide to deprecate the new connection erroneously.
22332 Bugfix on 0.1.1.13-alpha.
22333 - Resolve a very rare crash bug that could occur when the user forced
22334 a nameserver reconfiguration during the middle of a nameserver
22335 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
22336 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
22337 Bugfix on 0.2.1.7-alpha.
22338 - If we're using bridges and our network goes away, be more willing
22339 to forgive our bridges and try again when we get an application
22340 request. Bugfix on 0.2.0.x.
22343 - Support platforms where time_t is 64 bits long. (Congratulations,
22344 NetBSD!) Patch from Matthias Drochner.
22345 - Add a 'getinfo status/clients-seen' controller command, in case
22346 controllers want to hear clients_seen events but connect late.
22349 - Disable GCC's strict alias optimization by default, to avoid the
22350 likelihood of its introducing subtle bugs whenever our code violates
22351 the letter of C99's alias rules.
22354 Changes in version 0.2.0.33 - 2009-01-21
22355 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
22356 useful to users. It also finally fixes a bug where a relay or client
22357 that's been off for many days would take a long time to bootstrap.
22359 This update also fixes an important security-related bug reported by
22360 Ilja van Sprundel. You should upgrade. (We'll send out more details
22361 about the bug once people have had some time to upgrade.)
22364 - Fix a heap-corruption bug that may be remotely triggerable on
22365 some platforms. Reported by Ilja van Sprundel.
22368 - When a stream at an exit relay is in state "resolving" or
22369 "connecting" and it receives an "end" relay cell, the exit relay
22370 would silently ignore the end cell and not close the stream. If
22371 the client never closes the circuit, then the exit relay never
22372 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
22373 reported by "wood".
22374 - When sending CREATED cells back for a given circuit, use a 64-bit
22375 connection ID to find the right connection, rather than an addr:port
22376 combination. Now that we can have multiple OR connections between
22377 the same ORs, it is no longer possible to use addr:port to uniquely
22378 identify a connection.
22379 - Bridge relays that had DirPort set to 0 would stop fetching
22380 descriptors shortly after startup, and then briefly resume
22381 after a new bandwidth test and/or after publishing a new bridge
22382 descriptor. Bridge users that try to bootstrap from them would
22383 get a recent networkstatus but would get descriptors from up to
22384 18 hours earlier, meaning most of the descriptors were obsolete
22385 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
22386 - Prevent bridge relays from serving their 'extrainfo' document
22387 to anybody who asks, now that extrainfo docs include potentially
22388 sensitive aggregated client geoip summaries. Bugfix on
22390 - If the cached networkstatus consensus is more than five days old,
22391 discard it rather than trying to use it. In theory it could be
22392 useful because it lists alternate directory mirrors, but in practice
22393 it just means we spend many minutes trying directory mirrors that
22394 are long gone from the network. Also discard router descriptors as
22395 we load them if they are more than five days old, since the onion
22396 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
22399 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
22400 could make gcc generate non-functional binary search code. Bugfix
22402 - Build correctly on platforms without socklen_t.
22403 - Compile without warnings on solaris.
22404 - Avoid potential crash on internal error during signature collection.
22405 Fixes bug 864. Patch from rovv.
22406 - Correct handling of possible malformed authority signing key
22407 certificates with internal signature types. Fixes bug 880.
22408 Bugfix on 0.2.0.3-alpha.
22409 - Fix a hard-to-trigger resource leak when logging credential status.
22411 - When we can't initialize DNS because the network is down, do not
22412 automatically stop Tor from starting. Instead, we retry failed
22413 dns_init() every 10 minutes, and change the exit policy to reject
22414 *:* until one succeeds. Fixes bug 691.
22415 - Use 64 bits instead of 32 bits for connection identifiers used with
22416 the controller protocol, to greatly reduce risk of identifier reuse.
22417 - When we're choosing an exit node for a circuit, and we have
22418 no pending streams, choose a good general exit rather than one that
22419 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
22420 - Fix another case of assuming, when a specific exit is requested,
22421 that we know more than the user about what hosts it allows.
22422 Fixes one case of bug 752. Patch from rovv.
22423 - Clip the MaxCircuitDirtiness config option to a minimum of 10
22424 seconds. Warn the user if lower values are given in the
22425 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
22426 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
22427 user if lower values are given in the configuration. Bugfix on
22428 0.1.1.17-rc. Patch by Sebastian.
22429 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
22430 the cache because we already had a v0 descriptor with the same ID.
22431 Bugfix on 0.2.0.18-alpha.
22432 - Fix a race condition when freeing keys shared between main thread
22433 and CPU workers that could result in a memory leak. Bugfix on
22434 0.1.0.1-rc. Fixes bug 889.
22435 - Send a valid END cell back when a client tries to connect to a
22436 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
22437 840. Patch from rovv.
22438 - Check which hops rendezvous stream cells are associated with to
22439 prevent possible guess-the-streamid injection attacks from
22440 intermediate hops. Fixes another case of bug 446. Based on patch
22442 - If a broken client asks a non-exit router to connect somewhere,
22443 do not even do the DNS lookup before rejecting the connection.
22444 Fixes another case of bug 619. Patch from rovv.
22445 - When a relay gets a create cell it can't decrypt (e.g. because it's
22446 using the wrong onion key), we were dropping it and letting the
22447 client time out. Now actually answer with a destroy cell. Fixes
22448 bug 904. Bugfix on 0.0.2pre8.
22450 o Minor bugfixes (hidden services):
22451 - Do not throw away existing introduction points on SIGHUP. Bugfix on
22452 0.0.6pre1. Patch by Karsten. Fixes bug 874.
22455 - Report the case where all signatures in a detached set are rejected
22456 differently than the case where there is an error handling the
22458 - When we realize that another process has modified our cached
22459 descriptors, print out a more useful error message rather than
22460 triggering an assertion. Fixes bug 885. Patch from Karsten.
22461 - Implement the 0x20 hack to better resist DNS poisoning: set the
22462 case on outgoing DNS requests randomly, and reject responses that do
22463 not match the case correctly. This logic can be disabled with the
22464 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
22465 of servers that do not reliably preserve case in replies. See
22466 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
22468 - Check DNS replies for more matching fields to better resist DNS
22470 - Never use OpenSSL compression: it wastes RAM and CPU trying to
22471 compress cells, which are basically all encrypted, compressed, or
22475 Changes in version 0.2.1.11-alpha - 2009-01-20
22476 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
22477 week it will take a long time to bootstrap again" bug. It also fixes
22478 an important security-related bug reported by Ilja van Sprundel. You
22479 should upgrade. (We'll send out more details about the bug once people
22480 have had some time to upgrade.)
22483 - Fix a heap-corruption bug that may be remotely triggerable on
22484 some platforms. Reported by Ilja van Sprundel.
22487 - Discard router descriptors as we load them if they are more than
22488 five days old. Otherwise if Tor is off for a long time and then
22489 starts with cached descriptors, it will try to use the onion
22490 keys in those obsolete descriptors when building circuits. Bugfix
22491 on 0.2.0.x. Fixes bug 887.
22494 - Try to make sure that the version of Libevent we're running with
22495 is binary-compatible with the one we built with. May address bug
22497 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
22498 for bug 905. Bugfix on 0.2.1.7-alpha.
22499 - Add a new --enable-local-appdata configuration switch to change
22500 the default location of the datadir on win32 from APPDATA to
22501 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
22502 entirely. Patch from coderman.
22505 - Make outbound DNS packets respect the OutboundBindAddress setting.
22506 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
22507 - When our circuit fails at the first hop (e.g. we get a destroy
22508 cell back), avoid using that OR connection anymore, and also
22509 tell all the one-hop directory requests waiting for it that they
22510 should fail. Bugfix on 0.2.1.3-alpha.
22511 - In the torify(1) manpage, mention that tsocks will leak your
22515 Changes in version 0.2.1.10-alpha - 2009-01-06
22516 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
22517 would make the bridge relay not so useful if it had DirPort set to 0,
22518 and one that could let an attacker learn a little bit of information
22519 about the bridge's users), and a bug that would cause your Tor relay
22520 to ignore a circuit create request it can't decrypt (rather than reply
22521 with an error). It also fixes a wide variety of other bugs.
22524 - If the cached networkstatus consensus is more than five days old,
22525 discard it rather than trying to use it. In theory it could
22526 be useful because it lists alternate directory mirrors, but in
22527 practice it just means we spend many minutes trying directory
22528 mirrors that are long gone from the network. Helps bug 887 a bit;
22530 - Bridge relays that had DirPort set to 0 would stop fetching
22531 descriptors shortly after startup, and then briefly resume
22532 after a new bandwidth test and/or after publishing a new bridge
22533 descriptor. Bridge users that try to bootstrap from them would
22534 get a recent networkstatus but would get descriptors from up to
22535 18 hours earlier, meaning most of the descriptors were obsolete
22536 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
22537 - Prevent bridge relays from serving their 'extrainfo' document
22538 to anybody who asks, now that extrainfo docs include potentially
22539 sensitive aggregated client geoip summaries. Bugfix on
22543 - New controller event "clients_seen" to report a geoip-based summary
22544 of which countries we've seen clients from recently. Now controllers
22545 like Vidalia can show bridge operators that they're actually making
22547 - Build correctly against versions of OpenSSL 0.9.8 or later built
22548 without support for deprecated functions.
22549 - Update to the "December 19 2008" ip-to-country file.
22551 o Minor bugfixes (on 0.2.0.x):
22552 - Authorities now vote for the Stable flag for any router whose
22553 weighted MTBF is at least 5 days, regardless of the mean MTBF.
22554 - Do not remove routers as too old if we do not have any consensus
22555 document. Bugfix on 0.2.0.7-alpha.
22556 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
22557 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
22558 - When an exit relay resolves a stream address to a local IP address,
22559 do not just keep retrying that same exit relay over and
22560 over. Instead, just close the stream. Addresses bug 872. Bugfix
22561 on 0.2.0.32. Patch from rovv.
22562 - If a hidden service sends us an END cell, do not consider
22563 retrying the connection; just close it. Patch from rovv.
22564 - When we made bridge authorities stop serving bridge descriptors over
22565 unencrypted links, we also broke DirPort reachability testing for
22566 bridges. So bridges with a non-zero DirPort were printing spurious
22567 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
22568 - When a relay gets a create cell it can't decrypt (e.g. because it's
22569 using the wrong onion key), we were dropping it and letting the
22570 client time out. Now actually answer with a destroy cell. Fixes
22571 bug 904. Bugfix on 0.0.2pre8.
22572 - Squeeze 2-5% out of client performance (according to oprofile) by
22573 improving the implementation of some policy-manipulation functions.
22575 o Minor bugfixes (on 0.2.1.x):
22576 - Make get_interface_address() function work properly again; stop
22577 guessing the wrong parts of our address as our address.
22578 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
22579 send on that circuit. Otherwise we might violate the proposal-110
22580 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
22582 - When we're sending non-EXTEND cells to the first hop in a circuit,
22583 for example to use an encrypted directory connection, we don't need
22584 to use RELAY_EARLY cells: the first hop knows what kind of cell
22585 it is, and nobody else can even see the cell type. Conserving
22586 RELAY_EARLY cells makes it easier to cannibalize circuits like
22588 - Stop logging nameserver addresses in reverse order.
22589 - If we are retrying a directory download slowly over and over, do
22590 not automatically give up after the 254th failure. Bugfix on
22592 - Resume reporting accurate "stream end" reasons to the local control
22593 port. They were lost in the changes for Proposal 148. Bugfix on
22596 o Deprecated and removed features:
22597 - The old "tor --version --version" command, which would print out
22598 the subversion "Id" of most of the source files, is now removed. It
22599 turned out to be less useful than we'd expected, and harder to
22602 o Code simplifications and refactoring:
22603 - Change our header file guard macros to be less likely to conflict
22604 with system headers. Adam Langley noticed that we were conflicting
22605 with log.h on Android.
22606 - Tool-assisted documentation cleanup. Nearly every function or
22607 static variable in Tor should have its own documentation now.
22610 Changes in version 0.2.1.9-alpha - 2008-12-25
22611 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
22613 o New directory authorities:
22614 - gabelmoo (the authority run by Karsten Loesing) now has a new
22618 - Never use a connection with a mismatched address to extend a
22619 circuit, unless that connection is canonical. A canonical
22620 connection is one whose address is authenticated by the router's
22621 identity key, either in a NETINFO cell or in a router descriptor.
22622 - Avoid a possible memory corruption bug when receiving hidden service
22623 descriptors. Bugfix on 0.2.1.6-alpha.
22626 - Fix a logic error that would automatically reject all but the first
22627 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
22628 part of bug 813/868. Bug spotted by coderman.
22629 - When a stream at an exit relay is in state "resolving" or
22630 "connecting" and it receives an "end" relay cell, the exit relay
22631 would silently ignore the end cell and not close the stream. If
22632 the client never closes the circuit, then the exit relay never
22633 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
22634 reported by "wood".
22635 - When we can't initialize DNS because the network is down, do not
22636 automatically stop Tor from starting. Instead, retry failed
22637 dns_init() every 10 minutes, and change the exit policy to reject
22638 *:* until one succeeds. Fixes bug 691.
22641 - Give a better error message when an overzealous init script says
22642 "sudo -u username tor --user username". Makes Bug 882 easier for
22644 - When a directory authority gives us a new guess for our IP address,
22645 log which authority we used. Hopefully this will help us debug
22646 the recent complaints about bad IP address guesses.
22647 - Detect svn revision properly when we're using git-svn.
22648 - Try not to open more than one descriptor-downloading connection
22649 to an authority at once. This should reduce load on directory
22650 authorities. Fixes bug 366.
22651 - Add cross-certification to newly generated certificates, so that
22652 a signing key is enough information to look up a certificate.
22653 Partial implementation of proposal 157.
22654 - Start serving certificates by <identity digest, signing key digest>
22655 pairs. Partial implementation of proposal 157.
22656 - Clients now never report any stream end reason except 'MISC'.
22657 Implements proposal 148.
22658 - On platforms with a maximum syslog string length, truncate syslog
22659 messages to that length ourselves, rather than relying on the
22660 system to do it for us.
22661 - Optimize out calls to time(NULL) that occur for every IO operation,
22662 or for every cell. On systems where time() is a slow syscall,
22663 this fix will be slightly helpful.
22664 - Exit servers can now answer resolve requests for ip6.arpa addresses.
22665 - When we download a descriptor that we then immediately (as
22666 a directory authority) reject, do not retry downloading it right
22667 away. Should save some bandwidth on authorities. Fix for bug
22668 888. Patch by Sebastian Hahn.
22669 - When a download gets us zero good descriptors, do not notify
22670 Tor that new directory information has arrived.
22671 - Avoid some nasty corner cases in the logic for marking connections
22672 as too old or obsolete or noncanonical for circuits. Partial
22675 o Minor features (controller):
22676 - New CONSENSUS_ARRIVED event to note when a new consensus has
22677 been fetched and validated.
22678 - When we realize that another process has modified our cached
22679 descriptors file, print out a more useful error message rather
22680 than triggering an assertion. Fixes bug 885. Patch from Karsten.
22681 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
22682 controllers to prevent SIGHUP from reloading the
22683 configuration. Fixes bug 856.
22686 - Resume using the correct "REASON=" stream when telling the
22687 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
22688 - When a canonical connection appears later in our internal list
22689 than a noncanonical one for a given OR ID, always use the
22690 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
22692 - Clip the MaxCircuitDirtiness config option to a minimum of 10
22693 seconds. Warn the user if lower values are given in the
22694 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
22695 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
22696 user if lower values are given in the configuration. Bugfix on
22697 0.1.1.17-rc. Patch by Sebastian.
22698 - Fix a race condition when freeing keys shared between main thread
22699 and CPU workers that could result in a memory leak. Bugfix on
22700 0.1.0.1-rc. Fixes bug 889.
22702 o Minor bugfixes (hidden services):
22703 - Do not throw away existing introduction points on SIGHUP (bugfix on
22704 0.0.6pre1); also, do not stall hidden services because we're
22705 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
22706 by John Brooks. Patch by Karsten. Fixes bug 874.
22707 - Fix a memory leak when we decline to add a v2 rendezvous
22708 descriptor to the cache because we already had a v0 descriptor
22709 with the same ID. Bugfix on 0.2.0.18-alpha.
22711 o Deprecated and removed features:
22712 - RedirectExits has been removed. It was deprecated since
22714 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
22715 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
22716 - Cell pools are now always enabled; --disable-cell-pools is ignored.
22718 o Code simplifications and refactoring:
22719 - Rename the confusing or_is_obsolete field to the more appropriate
22720 is_bad_for_new_circs, and move it to or_connection_t where it
22722 - Move edge-only flags from connection_t to edge_connection_t: not
22723 only is this better coding, but on machines of plausible alignment,
22724 it should save 4-8 bytes per connection_t. "Every little bit helps."
22725 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
22726 for consistency; keep old option working for backward compatibility.
22727 - Simplify the code for finding connections to use for a circuit.
22730 Changes in version 0.2.1.8-alpha - 2008-12-08
22731 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
22732 builds better on unusual platforms like Solaris and old OS X, and
22733 fixes a variety of other issues.
22736 - New DirPortFrontPage option that takes an html file and publishes
22737 it as "/" on the DirPort. Now relay operators can provide a
22738 disclaimer without needing to set up a separate webserver. There's
22739 a sample disclaimer in contrib/tor-exit-notice.html.
22742 - When the client is choosing entry guards, now it selects at most
22743 one guard from a given relay family. Otherwise we could end up with
22744 all of our entry points into the network run by the same operator.
22745 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
22748 - Fix a DOS opportunity during the voting signature collection process
22749 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
22750 - Fix a possible segfault when establishing an exit connection. Bugfix
22754 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
22756 - Made Tor a little less aggressive about deleting expired
22757 certificates. Partial fix for bug 854.
22758 - Stop doing unaligned memory access that generated bus errors on
22759 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
22760 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
22761 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
22762 - Make USR2 log-level switch take effect immediately. Bugfix on
22764 - If one win32 nameserver fails to get added, continue adding the
22765 rest, and don't automatically fail.
22766 - Use fcntl() for locking when flock() is not available. Should fix
22767 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
22768 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
22769 could make gcc generate non-functional binary search code. Bugfix
22771 - Build correctly on platforms without socklen_t.
22772 - Avoid potential crash on internal error during signature collection.
22773 Fixes bug 864. Patch from rovv.
22774 - Do not use C's stdio library for writing to log files. This will
22775 improve logging performance by a minute amount, and will stop
22776 leaking fds when our disk is full. Fixes bug 861.
22777 - Stop erroneous use of O_APPEND in cases where we did not in fact
22778 want to re-seek to the end of a file before every last write().
22779 - Correct handling of possible malformed authority signing key
22780 certificates with internal signature types. Fixes bug 880. Bugfix
22782 - Fix a hard-to-trigger resource leak when logging credential status.
22786 - Directory mirrors no longer fetch the v1 directory or
22787 running-routers files. They are obsolete, and nobody asks for them
22788 anymore. This is the first step to making v1 authorities obsolete.
22790 o Minor features (controller):
22791 - Return circuit purposes in response to GETINFO circuit-status. Fixes
22795 Changes in version 0.2.0.32 - 2008-11-20
22796 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
22797 packages (and maybe other packages) noticed by Theo de Raadt, fixes
22798 a smaller security flaw that might allow an attacker to access local
22799 services, further improves hidden service performance, and fixes a
22800 variety of other issues.
22803 - The "User" and "Group" config options did not clear the
22804 supplementary group entries for the Tor process. The "User" option
22805 is now more robust, and we now set the groups to the specified
22806 user's primary group. The "Group" option is now ignored. For more
22807 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
22808 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
22809 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
22810 - The "ClientDNSRejectInternalAddresses" config option wasn't being
22811 consistently obeyed: if an exit relay refuses a stream because its
22812 exit policy doesn't allow it, we would remember what IP address
22813 the relay said the destination address resolves to, even if it's
22814 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
22817 - Fix a DOS opportunity during the voting signature collection process
22818 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
22820 o Major bugfixes (hidden services):
22821 - When fetching v0 and v2 rendezvous service descriptors in parallel,
22822 we were failing the whole hidden service request when the v0
22823 descriptor fetch fails, even if the v2 fetch is still pending and
22824 might succeed. Similarly, if the last v2 fetch fails, we were
22825 failing the whole hidden service request even if a v0 fetch is
22826 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
22827 - When extending a circuit to a hidden service directory to upload a
22828 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
22829 requests failed, because the router descriptor has not been
22830 downloaded yet. In these cases, do not attempt to upload the
22831 rendezvous descriptor, but wait until the router descriptor is
22832 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
22833 descriptor from a hidden service directory for which the router
22834 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
22838 - Fix several infrequent memory leaks spotted by Coverity.
22839 - When testing for libevent functions, set the LDFLAGS variable
22840 correctly. Found by Riastradh.
22841 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
22842 bootstrapping with tunneled directory connections. Bugfix on
22843 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
22844 - When asked to connect to A.B.exit:80, if we don't know the IP for A
22845 and we know that server B rejects most-but-not all connections to
22846 port 80, we would previously reject the connection. Now, we assume
22847 the user knows what they were asking for. Fixes bug 752. Bugfix
22848 on 0.0.9rc5. Diagnosed by BarkerJr.
22849 - If we overrun our per-second write limits a little, count this as
22850 having used up our write allocation for the second, and choke
22851 outgoing directory writes. Previously, we had only counted this when
22852 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
22853 Bugfix on 0.2.0.x (??).
22854 - Remove the old v2 directory authority 'lefkada' from the default
22855 list. It has been gone for many months.
22856 - Stop doing unaligned memory access that generated bus errors on
22857 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
22858 - Make USR2 log-level switch take effect immediately. Bugfix on
22861 o Minor bugfixes (controller):
22862 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
22863 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
22866 Changes in version 0.2.1.7-alpha - 2008-11-08
22867 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
22868 packages (and maybe other packages) noticed by Theo de Raadt, fixes
22869 a smaller security flaw that might allow an attacker to access local
22870 services, adds better defense against DNS poisoning attacks on exit
22871 relays, further improves hidden service performance, and fixes a
22872 variety of other issues.
22875 - The "ClientDNSRejectInternalAddresses" config option wasn't being
22876 consistently obeyed: if an exit relay refuses a stream because its
22877 exit policy doesn't allow it, we would remember what IP address
22878 the relay said the destination address resolves to, even if it's
22879 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
22880 - The "User" and "Group" config options did not clear the
22881 supplementary group entries for the Tor process. The "User" option
22882 is now more robust, and we now set the groups to the specified
22883 user's primary group. The "Group" option is now ignored. For more
22884 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
22885 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
22886 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
22887 - Do not use or believe expired v3 authority certificates. Patch
22888 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
22891 - Now NodeFamily and MyFamily config options allow spaces in
22892 identity fingerprints, so it's easier to paste them in.
22893 Suggested by Lucky Green.
22894 - Implement the 0x20 hack to better resist DNS poisoning: set the
22895 case on outgoing DNS requests randomly, and reject responses that do
22896 not match the case correctly. This logic can be disabled with the
22897 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
22898 of servers that do not reliably preserve case in replies. See
22899 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
22901 - Preserve case in replies to DNSPort requests in order to support
22902 the 0x20 hack for resisting DNS poisoning attacks.
22904 o Hidden service performance improvements:
22905 - When the client launches an introduction circuit, retry with a
22906 new circuit after 30 seconds rather than 60 seconds.
22907 - Launch a second client-side introduction circuit in parallel
22908 after a delay of 15 seconds (based on work by Christian Wilms).
22909 - Hidden services start out building five intro circuits rather
22910 than three, and when the first three finish they publish a service
22911 descriptor using those. Now we publish our service descriptor much
22912 faster after restart.
22915 - Minor fix in the warning messages when you're having problems
22916 bootstrapping; also, be more forgiving of bootstrap problems when
22917 we're still making incremental progress on a given bootstrap phase.
22918 - When we're choosing an exit node for a circuit, and we have
22919 no pending streams, choose a good general exit rather than one that
22920 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
22921 - Send a valid END cell back when a client tries to connect to a
22922 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
22923 840. Patch from rovv.
22924 - If a broken client asks a non-exit router to connect somewhere,
22925 do not even do the DNS lookup before rejecting the connection.
22926 Fixes another case of bug 619. Patch from rovv.
22927 - Fix another case of assuming, when a specific exit is requested,
22928 that we know more than the user about what hosts it allows.
22929 Fixes another case of bug 752. Patch from rovv.
22930 - Check which hops rendezvous stream cells are associated with to
22931 prevent possible guess-the-streamid injection attacks from
22932 intermediate hops. Fixes another case of bug 446. Based on patch
22934 - Avoid using a negative right-shift when comparing 32-bit
22935 addresses. Possible fix for bug 845 and bug 811.
22936 - Make the assert_circuit_ok() function work correctly on circuits that
22937 have already been marked for close.
22938 - Fix read-off-the-end-of-string error in unit tests when decoding
22939 introduction points.
22940 - Fix uninitialized size field for memory area allocation: may improve
22941 memory performance during directory parsing.
22942 - Treat duplicate certificate fetches as failures, so that we do
22943 not try to re-fetch an expired certificate over and over and over.
22944 - Do not say we're fetching a certificate when we'll in fact skip it
22945 because of a pending download.
22948 Changes in version 0.2.1.6-alpha - 2008-09-30
22949 Tor 0.2.1.6-alpha further improves performance and robustness of
22950 hidden services, starts work on supporting per-country relay selection,
22951 and fixes a variety of smaller issues.
22954 - Implement proposal 121: make it possible to build hidden services
22955 that only certain clients are allowed to connect to. This is
22956 enforced at several points, so that unauthorized clients are unable
22957 to send INTRODUCE cells to the service, or even (depending on the
22958 type of authentication) to learn introduction points. This feature
22959 raises the bar for certain kinds of active attacks against hidden
22960 services. Code by Karsten Loesing.
22961 - Relays now store and serve v2 hidden service descriptors by default,
22962 i.e., the new default value for HidServDirectoryV2 is 1. This is
22963 the last step in proposal 114, which aims to make hidden service
22964 lookups more reliable.
22965 - Start work to allow node restrictions to include country codes. The
22966 syntax to exclude nodes in a country with country code XX is
22967 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
22968 refinement to decide what config options should take priority if
22969 you ask to both use a particular node and exclude it.
22970 - Allow ExitNodes list to include IP ranges and country codes, just
22971 like the Exclude*Nodes lists. Patch from Robert Hogan.
22974 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
22975 Tor to fail to start if you had it configured to use a bridge
22976 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
22977 - When extending a circuit to a hidden service directory to upload a
22978 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
22979 requests failed, because the router descriptor had not been
22980 downloaded yet. In these cases, we now wait until the router
22981 descriptor is downloaded, and then retry. Likewise, clients
22982 now skip over a hidden service directory if they don't yet have
22983 its router descriptor, rather than futilely requesting it and
22984 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
22986 - When fetching v0 and v2 rendezvous service descriptors in parallel,
22987 we were failing the whole hidden service request when the v0
22988 descriptor fetch fails, even if the v2 fetch is still pending and
22989 might succeed. Similarly, if the last v2 fetch fails, we were
22990 failing the whole hidden service request even if a v0 fetch is
22991 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
22992 - DNS replies need to have names matching their requests, but
22993 these names should be in the questions section, not necessarily
22994 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
22997 - Update to the "September 1 2008" ip-to-country file.
22998 - Allow ports 465 and 587 in the default exit policy again. We had
22999 rejected them in 0.1.0.15, because back in 2005 they were commonly
23000 misconfigured and ended up as spam targets. We hear they are better
23001 locked down these days.
23002 - Use a lockfile to make sure that two Tor processes are not
23003 simultaneously running with the same datadir.
23004 - Serve the latest v3 networkstatus consensus via the control
23005 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
23006 - Better logging about stability/reliability calculations on directory
23008 - Drop the requirement to have an open dir port for storing and
23009 serving v2 hidden service descriptors.
23010 - Directory authorities now serve a /tor/dbg-stability.txt URL to
23011 help debug WFU and MTBF calculations.
23012 - Implement most of Proposal 152: allow specialized servers to permit
23013 single-hop circuits, and clients to use those servers to build
23014 single-hop circuits when using a specialized controller. Patch
23015 from Josh Albrecht. Resolves feature request 768.
23016 - Add a -p option to tor-resolve for specifying the SOCKS port: some
23017 people find host:port too confusing.
23018 - Make TrackHostExit mappings expire a while after their last use, not
23019 after their creation. Patch from Robert Hogan.
23020 - Provide circuit purposes along with circuit events to the controller.
23023 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
23025 - Fixed some memory leaks -- some quite frequent, some almost
23026 impossible to trigger -- based on results from Coverity.
23027 - When testing for libevent functions, set the LDFLAGS variable
23028 correctly. Found by Riastradh.
23029 - Fix an assertion bug in parsing policy-related options; possible fix
23031 - Catch and report a few more bootstrapping failure cases when Tor
23032 fails to establish a TCP connection. Cleanup on 0.2.1.x.
23033 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
23034 bootstrapping with tunneled directory connections. Bugfix on
23035 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
23036 - When asked to connect to A.B.exit:80, if we don't know the IP for A
23037 and we know that server B rejects most-but-not all connections to
23038 port 80, we would previously reject the connection. Now, we assume
23039 the user knows what they were asking for. Fixes bug 752. Bugfix
23040 on 0.0.9rc5. Diagnosed by BarkerJr.
23041 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
23042 service directories if they have no advertised dir port. Bugfix
23044 - If we overrun our per-second write limits a little, count this as
23045 having used up our write allocation for the second, and choke
23046 outgoing directory writes. Previously, we had only counted this when
23047 we had met our limits precisely. Fixes bug 824. Patch by rovv.
23048 Bugfix on 0.2.0.x (??).
23049 - Avoid a "0 divided by 0" calculation when calculating router uptime
23050 at directory authorities. Bugfix on 0.2.0.8-alpha.
23051 - Make DNS resolved controller events into "CLOSED", not
23052 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
23054 - Fix a bug where an unreachable relay would establish enough
23055 reachability testing circuits to do a bandwidth test -- if
23056 we already have a connection to the middle hop of the testing
23057 circuit, then it could establish the last hop by using the existing
23058 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
23059 circuits no longer use entry guards in 0.2.1.3-alpha.
23060 - If we have correct permissions on $datadir, we complain to stdout
23061 and fail to start. But dangerous permissions on
23062 $datadir/cached-status/ would cause us to open a log and complain
23063 there. Now complain to stdout and fail to start in both cases. Fixes
23064 bug 820, reported by seeess.
23065 - Remove the old v2 directory authority 'lefkada' from the default
23066 list. It has been gone for many months.
23068 o Code simplifications and refactoring:
23069 - Revise the connection_new functions so that a more typesafe variant
23070 exists. This will work better with Coverity, and let us find any
23071 actual mistakes we're making here.
23072 - Refactor unit testing logic so that dmalloc can be used sensibly
23073 with unit tests to check for memory leaks.
23074 - Move all hidden-service related fields from connection and circuit
23075 structure to substructures: this way they won't eat so much memory.
23078 Changes in version 0.2.0.31 - 2008-09-03
23079 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
23080 a big bug we're seeing where in rare cases traffic from one Tor stream
23081 gets mixed into another stream, and fixes a variety of smaller issues.
23084 - Make sure that two circuits can never exist on the same connection
23085 with the same circuit ID, even if one is marked for close. This
23086 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
23087 - Relays now reject risky extend cells: if the extend cell includes
23088 a digest of all zeroes, or asks to extend back to the relay that
23089 sent the extend cell, tear down the circuit. Ideas suggested
23091 - If not enough of our entry guards are available so we add a new
23092 one, we might use the new one even if it overlapped with the
23093 current circuit's exit relay (or its family). Anonymity bugfix
23094 pointed out by rovv.
23097 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
23098 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
23099 - Correctly detect the presence of the linux/netfilter_ipv4.h header
23100 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
23101 - Pick size of default geoip filename string correctly on windows.
23102 Fixes bug 806. Bugfix on 0.2.0.30.
23103 - Make the autoconf script accept the obsolete --with-ssl-dir
23104 option as an alias for the actually-working --with-openssl-dir
23105 option. Fix the help documentation to recommend --with-openssl-dir.
23106 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
23107 - When using the TransPort option on OpenBSD, and using the User
23108 option to change UID and drop privileges, make sure to open
23109 /dev/pf before dropping privileges. Fixes bug 782. Patch from
23110 Christopher Davis. Bugfix on 0.1.2.1-alpha.
23111 - Try to attach connections immediately upon receiving a RENDEZVOUS2
23112 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
23113 on the client side when connecting to a hidden service. Bugfix
23114 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
23115 - When closing an application-side connection because its circuit is
23116 getting torn down, generate the stream event correctly. Bugfix on
23117 0.1.2.x. Anonymous patch.
23120 Changes in version 0.2.1.5-alpha - 2008-08-31
23121 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
23122 in a lot of the infrastructure for adding authorization to hidden
23123 services, lays the groundwork for having clients read their load
23124 balancing information out of the networkstatus consensus rather than
23125 the individual router descriptors, addresses two potential anonymity
23126 issues, and fixes a variety of smaller issues.
23129 - Convert many internal address representations to optionally hold
23131 - Generate and accept IPv6 addresses in many protocol elements.
23132 - Make resolver code handle nameservers located at ipv6 addresses.
23133 - Begin implementation of proposal 121 ("Client authorization for
23134 hidden services"): configure hidden services with client
23135 authorization, publish descriptors for them, and configure
23136 authorization data for hidden services at clients. The next
23137 step is to actually access hidden services that perform client
23139 - More progress toward proposal 141: Network status consensus
23140 documents and votes now contain bandwidth information for each
23141 router and a summary of that router's exit policy. Eventually this
23142 will be used by clients so that they do not have to download every
23143 known descriptor before building circuits.
23145 o Major bugfixes (on 0.2.0.x and before):
23146 - When sending CREATED cells back for a given circuit, use a 64-bit
23147 connection ID to find the right connection, rather than an addr:port
23148 combination. Now that we can have multiple OR connections between
23149 the same ORs, it is no longer possible to use addr:port to uniquely
23150 identify a connection.
23151 - Relays now reject risky extend cells: if the extend cell includes
23152 a digest of all zeroes, or asks to extend back to the relay that
23153 sent the extend cell, tear down the circuit. Ideas suggested
23155 - If not enough of our entry guards are available so we add a new
23156 one, we might use the new one even if it overlapped with the
23157 current circuit's exit relay (or its family). Anonymity bugfix
23158 pointed out by rovv.
23161 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
23162 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
23163 - When using the TransPort option on OpenBSD, and using the User
23164 option to change UID and drop privileges, make sure to open /dev/pf
23165 before dropping privileges. Fixes bug 782. Patch from Christopher
23166 Davis. Bugfix on 0.1.2.1-alpha.
23167 - Correctly detect the presence of the linux/netfilter_ipv4.h header
23168 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
23169 - Add a missing safe_str() call for a debug log message.
23170 - Use 64 bits instead of 32 bits for connection identifiers used with
23171 the controller protocol, to greatly reduce risk of identifier reuse.
23172 - Make the autoconf script accept the obsolete --with-ssl-dir
23173 option as an alias for the actually-working --with-openssl-dir
23174 option. Fix the help documentation to recommend --with-openssl-dir.
23175 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
23178 - Rate-limit too-many-sockets messages: when they happen, they happen
23179 a lot. Resolves bug 748.
23180 - Resist DNS poisoning a little better by making sure that names in
23181 answer sections match.
23182 - Print the SOCKS5 error message string as well as the error code
23183 when a tor-resolve request fails. Patch from Jacob.
23186 Changes in version 0.2.1.4-alpha - 2008-08-04
23187 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
23190 - The address part of exit policies was not correctly written
23191 to router descriptors. This generated router descriptors that failed
23192 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
23194 - Tor triggered a false assert when extending a circuit to a relay
23195 but we already have a connection open to that relay. Noticed by
23196 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
23199 - Fix a hidden service logging bug: in some edge cases, the router
23200 descriptor of a previously picked introduction point becomes
23201 obsolete and we need to give up on it rather than continually
23202 complaining that it has become obsolete. Observed by xiando. Bugfix
23205 o Removed features:
23206 - Take out the TestVia config option, since it was a workaround for
23207 a bug that was fixed in Tor 0.1.1.21.
23210 Changes in version 0.2.1.3-alpha - 2008-08-03
23211 Tor 0.2.1.3-alpha implements most of the pieces to prevent
23212 infinite-length circuit attacks (see proposal 110); fixes a bug that
23213 might cause exit relays to corrupt streams they send back; allows
23214 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
23215 ExcludeExitNodes config options; and fixes a big pile of bugs.
23217 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
23218 - Send a bootstrap problem "warn" event on the first problem if the
23219 reason is NO_ROUTE (that is, our network is down).
23222 - Implement most of proposal 110: The first K cells to be sent
23223 along a circuit are marked as special "early" cells; only K "early"
23224 cells will be allowed. Once this code is universal, we can block
23225 certain kinds of DOS attack by requiring that EXTEND commands must
23226 be sent using an "early" cell.
23229 - Try to attach connections immediately upon receiving a RENDEZVOUS2
23230 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
23231 on the client side when connecting to a hidden service. Bugfix
23232 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
23233 - Ensure that two circuits can never exist on the same connection
23234 with the same circuit ID, even if one is marked for close. This
23235 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
23238 - When relays do their initial bandwidth measurement, don't limit
23239 to just our entry guards for the test circuits. Otherwise we tend
23240 to have multiple test circuits going through a single entry guard,
23241 which makes our bandwidth test less accurate. Fixes part of bug 654;
23242 patch contributed by Josh Albrecht.
23243 - Add an ExcludeExitNodes option so users can list a set of nodes
23244 that should be be excluded from the exit node position, but
23245 allowed elsewhere. Implements proposal 151.
23246 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
23247 ExcludeNodes and ExcludeExitNodes lists.
23248 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
23249 be more efficient. Formerly it was quadratic in the number of
23250 servers; now it should be linear. Fixes bug 509.
23251 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
23252 and n_conn_id_digest fields into a separate structure that's
23253 only needed when the circuit has not yet attached to an n_conn.
23256 - Change the contrib/tor.logrotate script so it makes the new
23257 logs as "_tor:_tor" rather than the default, which is generally
23258 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
23259 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
23260 warnings (occasionally), but it can also cause the compiler to
23261 eliminate error-checking code. Suggested by Peter Gutmann.
23262 - When a hidden service is giving up on an introduction point candidate
23263 that was not included in the last published rendezvous descriptor,
23264 don't reschedule publication of the next descriptor. Fixes bug 763.
23266 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
23267 HiddenServiceExcludeNodes as obsolete: they never worked properly,
23268 and nobody claims to be using them. Fixes bug 754. Bugfix on
23269 0.1.0.1-rc. Patch from Christian Wilms.
23270 - Fix a small alignment and memory-wasting bug on buffer chunks.
23273 o Minor bugfixes (controller):
23274 - When closing an application-side connection because its circuit
23275 is getting torn down, generate the stream event correctly.
23276 Bugfix on 0.1.2.x. Anonymous patch.
23278 o Removed features:
23279 - Remove all backward-compatibility code to support relays running
23280 versions of Tor so old that they no longer work at all on the
23284 Changes in version 0.2.0.30 - 2008-07-15
23286 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
23287 warnings (occasionally), but it can also cause the compiler to
23288 eliminate error-checking code. Suggested by Peter Gutmann.
23291 Changes in version 0.2.0.29-rc - 2008-07-08
23292 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
23293 hidden-service performance bugs, and fixes a bunch of smaller bugs.
23296 - If you have more than one bridge but don't know their keys,
23297 you would only launch a request for the descriptor of the first one
23298 on your list. (Tor considered launching requests for the others, but
23299 found that it already had a connection on the way for $0000...0000
23300 so it didn't open another.) Bugfix on 0.2.0.x.
23301 - If you have more than one bridge but don't know their keys, and the
23302 connection to one of the bridges failed, you would cancel all
23303 pending bridge connections. (After all, they all have the same
23304 digest.) Bugfix on 0.2.0.x.
23305 - When a hidden service was trying to establish an introduction point,
23306 and Tor had built circuits preemptively for such purposes, we
23307 were ignoring all the preemptive circuits and launching a new one
23308 instead. Bugfix on 0.2.0.14-alpha.
23309 - When a hidden service was trying to establish an introduction point,
23310 and Tor *did* manage to reuse one of the preemptively built
23311 circuits, it didn't correctly remember which one it used,
23312 so it asked for another one soon after, until there were no
23313 more preemptive circuits, at which point it launched one from
23314 scratch. Bugfix on 0.0.9.x.
23315 - Make directory servers include the X-Your-Address-Is: http header in
23316 their responses even for begin_dir conns. Now clients who only
23317 ever use begin_dir connections still have a way to learn their IP
23318 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
23321 - Fix a macro/CPP interaction that was confusing some compilers:
23322 some GCCs don't like #if/#endif pairs inside macro arguments.
23324 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
23325 Fixes bug 704; fix from Steven Murdoch.
23326 - When opening /dev/null in finish_daemonize(), do not pass the
23327 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
23328 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
23329 - Correctly detect transparent proxy support on Linux hosts that
23330 require in.h to be included before netfilter_ipv4.h. Patch
23332 - Disallow session resumption attempts during the renegotiation
23333 stage of the v2 handshake protocol. Clients should never be trying
23334 session resumption at this point, but apparently some did, in
23335 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
23336 found by Geoff Goodell.
23339 Changes in version 0.2.1.2-alpha - 2008-06-20
23340 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
23341 make it easier to set up your own private Tor network; fixes several
23342 big bugs with using more than one bridge relay; fixes a big bug with
23343 offering hidden services quickly after Tor starts; and uses a better
23344 API for reporting potential bootstrapping problems to the controller.
23347 - New TestingTorNetwork config option to allow adjustment of
23348 previously constant values that, while reasonable, could slow
23349 bootstrapping. Implements proposal 135. Patch from Karsten.
23352 - If you have more than one bridge but don't know their digests,
23353 you would only learn a request for the descriptor of the first one
23354 on your list. (Tor considered launching requests for the others, but
23355 found that it already had a connection on the way for $0000...0000
23356 so it didn't open another.) Bugfix on 0.2.0.x.
23357 - If you have more than one bridge but don't know their digests,
23358 and the connection to one of the bridges failed, you would cancel
23359 all pending bridge connections. (After all, they all have the
23360 same digest.) Bugfix on 0.2.0.x.
23361 - When establishing a hidden service, introduction points that
23362 originate from cannibalized circuits are completely ignored and not
23363 included in rendezvous service descriptors. This might be another
23364 reason for delay in making a hidden service available. Bugfix
23365 from long ago (0.0.9.x?)
23368 - Allow OpenSSL to use dynamic locks if it wants.
23369 - When building a consensus, do not include routers that are down.
23370 This will cut down 30% to 40% on consensus size. Implements
23372 - In directory authorities' approved-routers files, allow
23373 fingerprints with or without space.
23374 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
23375 controller can query our current bootstrap state in case it attaches
23376 partway through and wants to catch up.
23377 - Send an initial "Starting" bootstrap status event, so we have a
23378 state to start out in.
23381 - Asking for a conditional consensus at .../consensus/<fingerprints>
23382 would crash a dirserver if it did not already have a
23383 consensus. Bugfix on 0.2.1.1-alpha.
23384 - Clean up some macro/CPP interactions: some GCC versions don't like
23385 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
23388 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
23389 - Directory authorities shouldn't complain about bootstrapping
23390 problems just because they do a lot of reachability testing and
23391 some of the connection attempts fail.
23392 - Start sending "count" and "recommendation" key/value pairs in
23393 bootstrap problem status events, so the controller can hear about
23394 problems even before Tor decides they're worth reporting for sure.
23395 - If you're using bridges, generate "bootstrap problem" warnings
23396 as soon as you run out of working bridges, rather than waiting
23397 for ten failures -- which will never happen if you have less than
23399 - If we close our OR connection because there's been a circuit
23400 pending on it for too long, we were telling our bootstrap status
23401 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
23404 Changes in version 0.2.1.1-alpha - 2008-06-13
23405 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
23406 were making the Tor process bloat especially on Linux; makes our TLS
23407 handshake blend in better; sends "bootstrap phase" status events to
23408 the controller, so it can keep the user informed of progress (and
23409 problems) fetching directory information and establishing circuits;
23410 and adds a variety of smaller features.
23413 - More work on making our TLS handshake blend in: modify the list
23414 of ciphers advertised by OpenSSL in client mode to even more
23415 closely resemble a common web browser. We cheat a little so that
23416 we can advertise ciphers that the locally installed OpenSSL doesn't
23418 - Start sending "bootstrap phase" status events to the controller,
23419 so it can keep the user informed of progress fetching directory
23420 information and establishing circuits. Also inform the controller
23421 if we think we're stuck at a particular bootstrap phase. Implements
23423 - Resume using OpenSSL's RAND_poll() for better (and more portable)
23424 cross-platform entropy collection again. We used to use it, then
23425 stopped using it because of a bug that could crash systems that
23426 called RAND_poll when they had a lot of fds open. It looks like the
23427 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
23428 at startup, and to call RAND_poll() when we reseed later only if
23429 we have a non-buggy OpenSSL version.
23432 - When we choose to abandon a new entry guard because we think our
23433 older ones might be better, close any circuits pending on that
23434 new entry guard connection. This fix should make us recover much
23435 faster when our network is down and then comes back. Bugfix on
23436 0.1.2.8-beta; found by lodger.
23438 o Memory fixes and improvements:
23439 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
23440 to avoid unused RAM in buffer chunks and memory pools.
23441 - Speed up parsing and cut down on memory fragmentation by using
23442 stack-style allocations for parsing directory objects. Previously,
23443 this accounted for over 40% of allocations from within Tor's code
23444 on a typical directory cache.
23445 - Use a Bloom filter rather than a digest-based set to track which
23446 descriptors we need to keep around when we're cleaning out old
23447 router descriptors. This speeds up the computation significantly,
23448 and may reduce fragmentation.
23449 - Reduce the default smartlist size from 32 to 16; it turns out that
23450 most smartlists hold around 8-12 elements tops.
23451 - Make dumpstats() log the fullness and size of openssl-internal
23453 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
23454 patch to their OpenSSL, turn it on to save memory on servers. This
23455 patch will (with any luck) get included in a mainline distribution
23457 - Never use OpenSSL compression: it wastes RAM and CPU trying to
23458 compress cells, which are basically all encrypted, compressed,
23462 - Stop reloading the router list from disk for no reason when we
23463 run out of reachable directory mirrors. Once upon a time reloading
23464 it would set the 'is_running' flag back to 1 for them. It hasn't
23465 done that for a long time.
23466 - In very rare situations new hidden service descriptors were
23467 published earlier than 30 seconds after the last change to the
23468 service. (We currently think that a hidden service descriptor
23469 that's been stable for 30 seconds is worth publishing.)
23472 - Allow separate log levels to be configured for different logging
23473 domains. For example, this allows one to log all notices, warnings,
23474 or errors, plus all memory management messages of level debug or
23475 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
23476 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
23477 and stop using a warning that had become unfixably verbose under
23479 - New --hush command-line option similar to --quiet. While --quiet
23480 disables all logging to the console on startup, --hush limits the
23481 output to messages of warning and error severity.
23482 - Servers support a new URL scheme for consensus downloads that
23483 allows the client to specify which authorities are trusted.
23484 The server then only sends the consensus if the client will trust
23485 it. Otherwise a 404 error is sent back. Clients use this
23486 new scheme when the server supports it (meaning it's running
23487 0.2.1.1-alpha or later). Implements proposal 134.
23488 - New configure/torrc options (--enable-geoip-stats,
23489 DirRecordUsageByCountry) to record how many IPs we've served
23490 directory info to in each country code, how many status documents
23491 total we've sent to each country code, and what share of the total
23492 directory requests we should expect to see.
23493 - Use the TLS1 hostname extension to more closely resemble browser
23495 - Lots of new unit tests.
23496 - Add a macro to implement the common pattern of iterating through
23497 two parallel lists in lockstep.
23500 Changes in version 0.2.0.28-rc - 2008-06-13
23501 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
23502 performance bug, and fixes a bunch of smaller bugs.
23505 - Fix a bug where, when we were choosing the 'end stream reason' to
23506 put in our relay end cell that we send to the exit relay, Tor
23507 clients on Windows were sometimes sending the wrong 'reason'. The
23508 anonymity problem is that exit relays may be able to guess whether
23509 the client is running Windows, thus helping partition the anonymity
23510 set. Down the road we should stop sending reasons to exit relays,
23511 or otherwise prevent future versions of this bug.
23514 - While setting up a hidden service, some valid introduction circuits
23515 were overlooked and abandoned. This might be the reason for
23516 the long delay in making a hidden service available. Bugfix on
23520 - Update to the "June 9 2008" ip-to-country file.
23521 - Run 'make test' as part of 'make dist', so we stop releasing so
23522 many development snapshots that fail their unit tests.
23525 - When we're checking if we have enough dir info for each relay
23526 to begin establishing circuits, make sure that we actually have
23527 the descriptor listed in the consensus, not just any descriptor.
23529 - Bridge relays no longer print "xx=0" in their extrainfo document
23530 for every single country code in the geoip db. Bugfix on
23532 - Only warn when we fail to load the geoip file if we were planning to
23533 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
23534 - If we change our MaxAdvertisedBandwidth and then reload torrc,
23535 Tor won't realize it should publish a new relay descriptor. Fixes
23536 bug 688, reported by mfr. Bugfix on 0.1.2.x.
23537 - When we haven't had any application requests lately, don't bother
23538 logging that we have expired a bunch of descriptors. Bugfix
23540 - Make relay cells written on a connection count as non-padding when
23541 tracking how long a connection has been in use. Bugfix on
23542 0.2.0.1-alpha. Spotted by lodger.
23543 - Fix unit tests in 0.2.0.27-rc.
23544 - Fix compile on Windows.
23547 Changes in version 0.2.0.27-rc - 2008-06-03
23548 Tor 0.2.0.27-rc adds a few features we left out of the earlier
23549 release candidates. In particular, we now include an IP-to-country
23550 GeoIP database, so controllers can easily look up what country a
23551 given relay is in, and so bridge relays can give us some sanitized
23552 summaries about which countries are making use of bridges. (See proposal
23553 126-geoip-fetching.txt for details.)
23556 - Include an IP-to-country GeoIP file in the tarball, so bridge
23557 relays can report sanitized summaries of the usage they're seeing.
23560 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
23561 Robert Hogan. Fixes the first part of bug 681.
23562 - Make bridge authorities never serve extrainfo docs.
23563 - Add support to detect Libevent versions in the 1.4.x series
23565 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
23566 - Include a new contrib/tor-exit-notice.html file that exit relay
23567 operators can put on their website to help reduce abuse queries.
23570 - When tunneling an encrypted directory connection, and its first
23571 circuit fails, do not leave it unattached and ask the controller
23572 to deal. Fixes the second part of bug 681.
23573 - Make bridge authorities correctly expire old extrainfo documents
23577 Changes in version 0.2.0.26-rc - 2008-05-13
23578 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
23579 in Debian's OpenSSL packages. All users running any 0.2.0.x version
23580 should upgrade, whether they're running Debian or not.
23582 o Major security fixes:
23583 - Use new V3 directory authority keys on the tor26, gabelmoo, and
23584 moria1 V3 directory authorities. The old keys were generated with
23585 a vulnerable version of Debian's OpenSSL package, and must be
23586 considered compromised. Other authorities' keys were not generated
23587 with an affected version of OpenSSL.
23590 - List authority signatures as "unrecognized" based on DirServer
23591 lines, not on cert cache. Bugfix on 0.2.0.x.
23594 - Add a new V3AuthUseLegacyKey option to make it easier for
23595 authorities to change their identity keys if they have to.
23598 Changes in version 0.2.0.25-rc - 2008-04-23
23599 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
23602 - Remember to initialize threading before initializing logging.
23603 Otherwise, many BSD-family implementations will crash hard on
23604 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
23607 - Authorities correctly free policies on bad servers on
23608 exit. Fixes bug 672. Bugfix on 0.2.0.x.
23611 Changes in version 0.2.0.24-rc - 2008-04-22
23612 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
23613 v3 directory authority, makes relays with dynamic IP addresses and no
23614 DirPort notice more quickly when their IP address changes, fixes a few
23615 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
23617 o New directory authorities:
23618 - Take lefkada out of the list of v3 directory authorities, since
23619 it has been down for months.
23620 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
23624 - Detect address changes more quickly on non-directory mirror
23625 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
23627 o Minor features (security):
23628 - Reject requests for reverse-dns lookup of names that are in
23629 a private address space. Patch from lodger.
23630 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
23633 o Minor bugfixes (crashes):
23634 - Avoid a rare assert that can trigger when Tor doesn't have much
23635 directory information yet and it tries to fetch a v2 hidden
23636 service descriptor. Fixes bug 651, reported by nwf.
23637 - Initialize log mutex before initializing dmalloc. Otherwise,
23638 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
23639 - Use recursive pthread mutexes in order to avoid deadlock when
23640 logging debug-level messages to a controller. Bug spotted by nwf,
23641 bugfix on 0.2.0.16-alpha.
23643 o Minor bugfixes (resource management):
23644 - Keep address policies from leaking memory: start their refcount
23645 at 1, not 2. Bugfix on 0.2.0.16-alpha.
23646 - Free authority certificates on exit, so they don't look like memory
23647 leaks. Bugfix on 0.2.0.19-alpha.
23648 - Free static hashtables for policy maps and for TLS connections on
23649 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
23650 - Avoid allocating extra space when computing consensuses on 64-bit
23651 platforms. Bug spotted by aakova.
23653 o Minor bugfixes (misc):
23654 - Do not read the configuration file when we've only been told to
23655 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
23656 based on patch from Sebastian Hahn.
23657 - Exit relays that are used as a client can now reach themselves
23658 using the .exit notation, rather than just launching an infinite
23659 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
23660 - When attempting to open a logfile fails, tell us why.
23661 - Fix a dumb bug that was preventing us from knowing that we should
23662 preemptively build circuits to handle expected directory requests.
23663 Fixes bug 660. Bugfix on 0.1.2.x.
23664 - Warn less verbosely about clock skew from netinfo cells from
23665 untrusted sources. Fixes bug 663.
23666 - Make controller stream events for DNS requests more consistent,
23667 by adding "new stream" events for DNS requests, and removing
23668 spurious "stream closed" events" for cached reverse resolves.
23669 Patch from mwenge. Fixes bug 646.
23670 - Correctly notify one-hop connections when a circuit build has
23671 failed. Possible fix for bug 669. Found by lodger.
23674 Changes in version 0.2.0.23-rc - 2008-03-24
23675 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
23676 makes bootstrapping faster if the first directory mirror you contact
23677 is down. The bundles also include the new Vidalia 0.1.2 release.
23680 - When a tunneled directory request is made to a directory server
23681 that's down, notice after 30 seconds rather than 120 seconds. Also,
23682 fail any begindir streams that are pending on it, so they can
23683 retry elsewhere. This was causing multi-minute delays on bootstrap.
23686 Changes in version 0.2.0.22-rc - 2008-03-18
23687 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
23688 enables encrypted directory connections by default for non-relays, fixes
23689 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
23690 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
23693 - Enable encrypted directory connections by default for non-relays,
23694 so censor tools that block Tor directory connections based on their
23695 plaintext patterns will no longer work. This means Tor works in
23696 certain censored countries by default again.
23699 - Make sure servers always request certificates from clients during
23700 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
23701 - Do not enter a CPU-eating loop when a connection is closed in
23702 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
23703 diagnosed by lodger; bugfix on 0.2.0.20-rc.
23704 - Fix assertion failure that could occur when a blocked circuit
23705 became unblocked, and it had pending client DNS requests. Bugfix
23706 on 0.2.0.1-alpha. Fixes bug 632.
23708 o Minor bugfixes (on 0.1.2.x):
23709 - Generate "STATUS_SERVER" events rather than misspelled
23710 "STATUS_SEVER" events. Caught by mwenge.
23711 - When counting the number of bytes written on a TLS connection,
23712 look at the BIO actually used for writing to the network, not
23713 at the BIO used (sometimes) to buffer data for the network.
23714 Looking at different BIOs could result in write counts on the
23715 order of ULONG_MAX. Fixes bug 614.
23716 - On Windows, correctly detect errors when listing the contents of
23717 a directory. Fix from lodger.
23719 o Minor bugfixes (on 0.2.0.x):
23720 - Downgrade "sslv3 alert handshake failure" message to INFO.
23721 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
23722 left BandwidthRate and BandwidthBurst at the default, we would be
23723 silently limited by those defaults. Now raise them to match the
23724 RelayBandwidth* values.
23725 - Fix the SVK version detection logic to work correctly on a branch.
23726 - Make --enable-openbsd-malloc work correctly on Linux with alpha
23727 CPUs. Fixes bug 625.
23728 - Logging functions now check that the passed severity is sane.
23729 - Use proper log levels in the testsuite call of
23730 get_interface_address6().
23731 - When using a nonstandard malloc, do not use the platform values for
23732 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
23733 - Make the openbsd malloc code use 8k pages on alpha CPUs and
23735 - Detect mismatched page sizes when using --enable-openbsd-malloc.
23736 - Avoid double-marked-for-close warning when certain kinds of invalid
23737 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
23738 for bug 617. Bugfix on 0.2.0.1-alpha.
23739 - Make sure that the "NULL-means-reject *:*" convention is followed by
23740 all the policy manipulation functions, avoiding some possible crash
23741 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
23742 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
23743 actually works, and doesn't warn about every single reverse lookup.
23744 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
23747 - Only log guard node status when guard node status has changed.
23748 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
23749 make "INFO" 75% less verbose.
23752 Changes in version 0.2.0.21-rc - 2008-03-02
23753 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
23754 makes Tor work well with Vidalia again, fixes a rare assert bug,
23755 and fixes a pair of more minor bugs. The bundles also include Vidalia
23756 0.1.0 and Torbutton 1.1.16.
23759 - The control port should declare that it requires password auth
23760 when HashedControlSessionPassword is set too. Patch from Matt Edman;
23761 bugfix on 0.2.0.20-rc. Fixes bug 615.
23762 - Downgrade assert in connection_buckets_decrement() to a log message.
23763 This may help us solve bug 614, and in any case will make its
23764 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
23765 - We were sometimes miscounting the number of bytes read from the
23766 network, causing our rate limiting to not be followed exactly.
23767 Bugfix on 0.2.0.16-alpha. Reported by lodger.
23770 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
23771 OpenSSL versions should have been working fine. Diagnosis and patch
23772 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
23773 Bugfix on 0.2.0.20-rc.
23776 Changes in version 0.2.0.20-rc - 2008-02-24
23777 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
23778 makes more progress towards normalizing Tor's TLS handshake, makes
23779 hidden services work better again, helps relays bootstrap if they don't
23780 know their IP address, adds optional support for linking in openbsd's
23781 allocator or tcmalloc, allows really fast relays to scale past 15000
23782 sockets, and fixes a bunch of minor bugs reported by Veracode.
23785 - Enable the revised TLS handshake based on the one designed by
23786 Steven Murdoch in proposal 124, as revised in proposal 130. It
23787 includes version negotiation for OR connections as described in
23788 proposal 105. The new handshake is meant to be harder for censors
23789 to fingerprint, and it adds the ability to detect certain kinds of
23790 man-in-the-middle traffic analysis attacks. The version negotiation
23791 feature will allow us to improve Tor's link protocol more safely
23793 - Choose which bridge to use proportional to its advertised bandwidth,
23794 rather than uniformly at random. This should speed up Tor for
23795 bridge users. Also do this for people who set StrictEntryNodes.
23796 - When a TrackHostExits-chosen exit fails too many times in a row,
23797 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
23800 - Resolved problems with (re-)fetching hidden service descriptors.
23801 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
23802 and 0.2.0.19-alpha.
23803 - If we only ever used Tor for hidden service lookups or posts, we
23804 would stop building circuits and start refusing connections after
23805 24 hours, since we falsely believed that Tor was dormant. Reported
23806 by nwf; bugfix on 0.1.2.x.
23807 - Servers that don't know their own IP address should go to the
23808 authorities for their first directory fetch, even if their DirPort
23809 is off or if they don't know they're reachable yet. This will help
23810 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
23811 - When counting the number of open sockets, count not only the number
23812 of sockets we have received from the socket() call, but also
23813 the number we've gotten from accept() and socketpair(). This bug
23814 made us fail to count all sockets that we were using for incoming
23815 connections. Bugfix on 0.2.0.x.
23816 - Fix code used to find strings within buffers, when those strings
23817 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
23818 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
23819 - Add a new __HashedControlSessionPassword option for controllers
23820 to use for one-off session password hashes that shouldn't get
23821 saved to disk by SAVECONF --- Vidalia users were accumulating a
23822 pile of HashedControlPassword lines in their torrc files, one for
23823 each time they had restarted Tor and then clicked Save. Make Tor
23824 automatically convert "HashedControlPassword" to this new option but
23825 only when it's given on the command line. Partial fix for bug 586.
23827 o Minor features (performance):
23828 - Tune parameters for cell pool allocation to minimize amount of
23830 - Add OpenBSD malloc code from phk as an optional malloc
23831 replacement on Linux: some glibc libraries do very poorly
23832 with Tor's memory allocation patterns. Pass
23833 --enable-openbsd-malloc to get the replacement malloc code.
23834 - Add a --with-tcmalloc option to the configure script to link
23835 against tcmalloc (if present). Does not yet search for
23836 non-system include paths.
23837 - Stop imposing an arbitrary maximum on the number of file descriptors
23838 used for busy servers. Bug reported by Olaf Selke; patch from
23841 o Minor features (other):
23842 - When SafeLogging is disabled, log addresses along with all TLS
23844 - When building with --enable-gcc-warnings, check for whether Apple's
23845 warning "-Wshorten-64-to-32" is available.
23846 - Add a --passphrase-fd argument to the tor-gencert command for
23849 o Minor bugfixes (memory leaks and code problems):
23850 - We were leaking a file descriptor if Tor started with a zero-length
23851 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
23852 - Detect size overflow in zlib code. Reported by Justin Ferguson and
23854 - We were comparing the raw BridgePassword entry with a base64'ed
23855 version of it, when handling a "/tor/networkstatus-bridges"
23856 directory request. Now compare correctly. Noticed by Veracode.
23857 - Recover from bad tracked-since value in MTBF-history file.
23858 Should fix bug 537.
23859 - Alter the code that tries to recover from unhandled write
23860 errors, to not try to flush onto a socket that's given us
23861 unhandled errors. Bugfix on 0.1.2.x.
23862 - Make Unix controlsockets work correctly on OpenBSD. Patch from
23863 tup. Bugfix on 0.2.0.3-alpha.
23865 o Minor bugfixes (other):
23866 - If we have an extra-info document for our server, always make
23867 it available on the control port, even if we haven't gotten
23868 a copy of it from an authority yet. Patch from mwenge.
23869 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
23870 - Directory mirrors no longer include a guess at the client's IP
23871 address if the connection appears to be coming from the same /24
23872 network; it was producing too many wrong guesses.
23873 - Make the new hidden service code respect the SafeLogging setting.
23874 Bugfix on 0.2.0.x. Patch from Karsten.
23875 - When starting as an authority, do not overwrite all certificates
23876 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
23877 - If we're trying to flush the last bytes on a connection (for
23878 example, when answering a directory request), reset the
23879 time-to-give-up timeout every time we manage to write something
23880 on the socket. Bugfix on 0.1.2.x.
23881 - Change the behavior of "getinfo status/good-server-descriptor"
23882 so it doesn't return failure when any authority disappears.
23883 - Even though the man page said that "TrackHostExits ." should
23884 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
23885 - Report TLS "zero return" case as a "clean close" and "IO error"
23886 as a "close". Stop calling closes "unexpected closes": existing
23887 Tors don't use SSL_close(), so having a connection close without
23888 the TLS shutdown handshake is hardly unexpected.
23889 - Send NAMESERVER_STATUS messages for a single failed nameserver
23892 o Code simplifications and refactoring:
23893 - Remove the tor_strpartition function: its logic was confused,
23894 and it was only used for one thing that could be implemented far
23898 Changes in version 0.2.0.19-alpha - 2008-02-09
23899 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
23900 handshake, makes path selection for relays more secure and IP address
23901 guessing more robust, and generally fixes a lot of bugs in preparation
23902 for calling the 0.2.0 branch stable.
23905 - Do not include recognizeable strings in the commonname part of
23906 Tor's x509 certificates.
23909 - If we're a relay, avoid picking ourselves as an introduction point,
23910 a rendezvous point, or as the final hop for internal circuits. Bug
23911 reported by taranis and lodger. Bugfix on 0.1.2.x.
23912 - Patch from "Andrew S. Lists" to catch when we contact a directory
23913 mirror at IP address X and he says we look like we're coming from
23914 IP address X. Bugfix on 0.1.2.x.
23916 o Minor features (security):
23917 - Be more paranoid about overwriting sensitive memory on free(),
23918 as a defensive programming tactic to ensure forward secrecy.
23920 o Minor features (directory authority):
23921 - Actually validate the options passed to AuthDirReject,
23922 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
23923 - Reject router descriptors with out-of-range bandwidthcapacity or
23924 bandwidthburst values.
23926 o Minor features (controller):
23927 - Reject controller commands over 1MB in length. This keeps rogue
23928 processes from running us out of memory.
23930 o Minor features (misc):
23931 - Give more descriptive well-formedness errors for out-of-range
23932 hidden service descriptor/protocol versions.
23933 - Make memory debugging information describe more about history
23934 of cell allocation, so we can help reduce our memory use.
23936 o Deprecated features (controller):
23937 - The status/version/num-versioning and status/version/num-concurring
23938 GETINFO options are no longer useful in the v3 directory protocol:
23939 treat them as deprecated, and warn when they're used.
23942 - When our consensus networkstatus has been expired for a while, stop
23943 being willing to build circuits using it. Fixes bug 401. Bugfix
23945 - Directory caches now fetch certificates from all authorities
23946 listed in a networkstatus consensus, even when they do not
23947 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
23948 - When connecting to a bridge without specifying its key, insert
23949 the connection into the identity-to-connection map as soon as
23950 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
23951 - Detect versions of OS X where malloc_good_size() is present in the
23952 library but never actually declared. Resolves bug 587. Bugfix
23954 - Stop incorrectly truncating zlib responses to directory authority
23955 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
23956 - Stop recommending that every server operator send mail to tor-ops.
23957 Resolves bug 597. Bugfix on 0.1.2.x.
23958 - Don't trigger an assert if we start a directory authority with a
23959 private IP address (like 127.0.0.1).
23960 - Avoid possible failures when generating a directory with routers
23961 with over-long versions strings, or too many flags set. Bugfix
23963 - If an attempt to launch a DNS resolve request over the control
23964 port fails because we have overrun the limit on the number of
23965 connections, tell the controller that the request has failed.
23966 - Avoid using too little bandwidth when our clock skips a few
23967 seconds. Bugfix on 0.1.2.x.
23968 - Fix shell error when warning about missing packages in configure
23969 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
23970 - Do not become confused when receiving a spurious VERSIONS-like
23971 cell from a confused v1 client. Bugfix on 0.2.0.x.
23972 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
23973 introduction points for a hidden service have failed. Patch from
23974 Karsten Loesing. Bugfix on 0.2.0.x.
23976 o Code simplifications and refactoring:
23977 - Remove some needless generality from cpuworker code, for improved
23979 - Stop overloading the circuit_t.onionskin field for both "onionskin
23980 from a CREATE cell that we are waiting for a cpuworker to be
23981 assigned" and "onionskin from an EXTEND cell that we are going to
23982 send to an OR as soon as we are connected". Might help with bug 600.
23983 - Add an in-place version of aes_crypt() so that we can avoid doing a
23984 needless memcpy() call on each cell payload.
23987 Changes in version 0.2.0.18-alpha - 2008-01-25
23988 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
23989 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
23990 that can warn or reject connections to ports generally associated with
23991 vulnerable-plaintext protocols.
23993 o New directory authorities:
23994 - Set up dannenberg (run by CCC) as the sixth v3 directory
23998 - Fix a major memory leak when attempting to use the v2 TLS
23999 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
24000 - We accidentally enabled the under-development v2 TLS handshake
24001 code, which was causing log entries like "TLS error while
24002 renegotiating handshake". Disable it again. Resolves bug 590.
24003 - We were computing the wrong Content-Length: header for directory
24004 responses that need to be compressed on the fly, causing clients
24005 asking for those items to always fail. Bugfix on 0.2.0.x; partially
24009 - Avoid going directly to the directory authorities even if you're a
24010 relay, if you haven't found yourself reachable yet or if you've
24011 decided not to advertise your dirport yet. Addresses bug 556.
24012 - If we've gone 12 hours since our last bandwidth check, and we
24013 estimate we have less than 50KB bandwidth capacity but we could
24014 handle more, do another bandwidth test.
24015 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
24016 Tor can warn and/or refuse connections to ports commonly used with
24017 vulnerable-plaintext protocols. Currently we warn on ports 23,
24018 109, 110, and 143, but we don't reject any.
24021 - When we setconf ClientOnly to 1, close any current OR and Dir
24022 listeners. Reported by mwenge.
24023 - When we get a consensus that's been signed by more people than
24024 we expect, don't log about it; it's not a big deal. Reported
24028 - Don't answer "/tor/networkstatus-bridges" directory requests if
24029 the request isn't encrypted.
24030 - Make "ClientOnly 1" config option disable directory ports too.
24031 - Patches from Karsten Loesing to make v2 hidden services more
24032 robust: work even when there aren't enough HSDir relays available;
24033 retry when a v2 rend desc fetch fails; but don't retry if we
24034 already have a usable v0 rend desc.
24037 Changes in version 0.2.0.17-alpha - 2008-01-17
24038 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
24041 - Make the tor-gencert man page get included correctly in the tarball.
24044 Changes in version 0.2.0.16-alpha - 2008-01-17
24045 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
24046 Loesing, and generally cleans up a lot of features and minor bugs.
24048 o New directory authorities:
24049 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
24052 o Major performance improvements:
24053 - Switch our old ring buffer implementation for one more like that
24054 used by free Unix kernels. The wasted space in a buffer with 1mb
24055 of data will now be more like 8k than 1mb. The new implementation
24056 also avoids realloc();realloc(); patterns that can contribute to
24057 memory fragmentation.
24060 - Configuration files now accept C-style strings as values. This
24061 helps encode characters not allowed in the current configuration
24062 file format, such as newline or #. Addresses bug 557.
24063 - Although we fixed bug 539 (where servers would send HTTP status 503
24064 responses _and_ send a body too), there are still servers out
24065 there that haven't upgraded. Therefore, make clients parse such
24066 bodies when they receive them.
24067 - When we're not serving v2 directory information, there is no reason
24068 to actually keep any around. Remove the obsolete files and directory
24069 on startup if they are very old and we aren't going to serve them.
24071 o Minor performance improvements:
24072 - Reference-count and share copies of address policy entries; only 5%
24073 of them were actually distinct.
24074 - Never walk through the list of logs if we know that no log is
24075 interested in a given message.
24078 - When an authority has not signed a consensus, do not try to
24079 download a nonexistent "certificate with key 00000000". Bugfix
24080 on 0.2.0.x. Fixes bug 569.
24081 - Fix a rare assert error when we're closing one of our threads:
24082 use a mutex to protect the list of logs, so we never write to the
24083 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
24084 bug 575, which is kind of the revenge of bug 222.
24085 - Patch from Karsten Loesing to complain less at both the client
24086 and the relay when a relay used to have the HSDir flag but doesn't
24087 anymore, and we try to upload a hidden service descriptor.
24088 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
24090 - Do not try to download missing certificates until we have tried
24091 to check our fallback consensus. Fixes bug 583.
24092 - Make bridges round reported GeoIP stats info up to the nearest
24093 estimate, not down. Now we can distinguish between "0 people from
24094 this country" and "1 person from this country".
24095 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
24096 - Avoid possible segfault if key generation fails in
24097 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
24098 - Avoid segfault in the case where a badly behaved v2 versioning
24099 directory sends a signed networkstatus with missing client-versions.
24101 - Avoid segfaults on certain complex invocations of
24102 router_get_by_hexdigest(). Bugfix on 0.1.2.
24103 - Correct bad index on array access in parse_http_time(). Bugfix
24105 - Fix possible bug in vote generation when server versions are present
24106 but client versions are not.
24107 - Fix rare bug on REDIRECTSTREAM control command when called with no
24108 port set: it could erroneously report an error when none had
24110 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
24111 compressing large objects and find ourselves with more than 4k
24112 left over. Bugfix on 0.2.0.
24113 - Fix a small memory leak when setting up a hidden service.
24114 - Fix a few memory leaks that could in theory happen under bizarre
24116 - Fix an assert if we post a general-purpose descriptor via the
24117 control port but that descriptor isn't mentioned in our current
24118 network consensus. Bug reported by Jon McLachlan; bugfix on
24121 o Minor features (controller):
24122 - Get NS events working again. Patch from tup.
24123 - The GETCONF command now escapes and quotes configuration values
24124 that don't otherwise fit into the torrc file.
24125 - The SETCONF command now handles quoted values correctly.
24127 o Minor features (directory authorities):
24128 - New configuration options to override default maximum number of
24129 servers allowed on a single IP address. This is important for
24130 running a test network on a single host.
24131 - Actually implement the -s option to tor-gencert.
24132 - Add a manual page for tor-gencert.
24134 o Minor features (bridges):
24135 - Bridge authorities no longer serve bridge descriptors over
24136 unencrypted connections.
24138 o Minor features (other):
24139 - Add hidden services and DNSPorts to the list of things that make
24140 Tor accept that it has running ports. Change starting Tor with no
24141 ports from a fatal error to a warning; we might change it back if
24142 this turns out to confuse anybody. Fixes bug 579.
24145 Changes in version 0.1.2.19 - 2008-01-17
24146 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
24147 exit policy a little bit more conservative so it's safer to run an
24148 exit relay on a home system, and fixes a variety of smaller issues.
24151 - Exit policies now reject connections that are addressed to a
24152 relay's public (external) IP address too, unless
24153 ExitPolicyRejectPrivate is turned off. We do this because too
24154 many relays are running nearby to services that trust them based
24155 on network address.
24158 - When the clock jumps forward a lot, do not allow the bandwidth
24159 buckets to become negative. Fixes bug 544.
24160 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
24161 on every successful resolve. Reported by Mike Perry.
24162 - Purge old entries from the "rephist" database and the hidden
24163 service descriptor database even when DirPort is zero.
24164 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
24165 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
24166 crashing or mis-answering these requests.
24167 - When we decide to send a 503 response to a request for servers, do
24168 not then also send the server descriptors: this defeats the whole
24169 purpose. Fixes bug 539.
24172 - Changing the ExitPolicyRejectPrivate setting should cause us to
24173 rebuild our server descriptor.
24174 - Fix handling of hex nicknames when answering controller requests for
24175 networkstatus by name, or when deciding whether to warn about
24176 unknown routers in a config option. (Patch from mwenge.)
24177 - Fix a couple of hard-to-trigger autoconf problems that could result
24178 in really weird results on platforms whose sys/types.h files define
24179 nonstandard integer types.
24180 - Don't try to create the datadir when running --verify-config or
24181 --hash-password. Resolves bug 540.
24182 - If we were having problems getting a particular descriptor from the
24183 directory caches, and then we learned about a new descriptor for
24184 that router, we weren't resetting our failure count. Reported
24186 - Although we fixed bug 539 (where servers would send HTTP status 503
24187 responses _and_ send a body too), there are still servers out there
24188 that haven't upgraded. Therefore, make clients parse such bodies
24189 when they receive them.
24190 - Run correctly on systems where rlim_t is larger than unsigned long.
24191 This includes some 64-bit systems.
24192 - Run correctly on platforms (like some versions of OS X 10.5) where
24193 the real limit for number of open files is OPEN_FILES, not rlim_max
24194 from getrlimit(RLIMIT_NOFILES).
24195 - Avoid a spurious free on base64 failure.
24196 - Avoid segfaults on certain complex invocations of
24197 router_get_by_hexdigest().
24198 - Fix rare bug on REDIRECTSTREAM control command when called with no
24199 port set: it could erroneously report an error when none had
24203 Changes in version 0.2.0.15-alpha - 2007-12-25
24204 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
24205 features added in 0.2.0.13-alpha.
24208 - Fix several remotely triggerable asserts based on DirPort requests
24209 for a v2 or v3 networkstatus object before we were prepared. This
24210 was particularly bad for 0.2.0.13 and later bridge relays, who
24211 would never have a v2 networkstatus and would thus always crash
24212 when used. Bugfixes on 0.2.0.x.
24213 - Estimate the v3 networkstatus size more accurately, rather than
24214 estimating it at zero bytes and giving it artificially high priority
24215 compared to other directory requests. Bugfix on 0.2.0.x.
24218 - Fix configure.in logic for cross-compilation.
24219 - When we load a bridge descriptor from the cache, and it was
24220 previously unreachable, mark it as retriable so we won't just
24221 ignore it. Also, try fetching a new copy immediately. Bugfixes
24223 - The bridge GeoIP stats were counting other relays, for example
24224 self-reachability and authority-reachability tests.
24227 - Support compilation to target iPhone; patch from cjacker huang.
24228 To build for iPhone, pass the --enable-iphone option to configure.
24231 Changes in version 0.2.0.14-alpha - 2007-12-23
24233 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
24234 without a datadirectory from a previous Tor install. Reported
24236 - Fix a crash when we fetch a descriptor that turns out to be
24237 unexpected (it used to be in our networkstatus when we started
24238 fetching it, but it isn't in our current networkstatus), and we
24239 aren't using bridges. Bugfix on 0.2.0.x.
24240 - Fix a crash when accessing hidden services: it would work the first
24241 time you use a given introduction point for your service, but
24242 on subsequent requests we'd be using garbage memory. Fixed by
24243 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
24244 - Fix a crash when we load a bridge descriptor from disk but we don't
24245 currently have a Bridge line for it in our torrc. Bugfix on
24249 - If bridge authorities set BridgePassword, they will serve a
24250 snapshot of known bridge routerstatuses from their DirPort to
24251 anybody who knows that password. Unset by default.
24254 - Make the unit tests build again.
24255 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
24256 - Make PublishServerDescriptor default to 1, so the default doesn't
24257 have to change as we invent new directory protocol versions.
24258 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
24259 be included unless sys/time.h is already included. Fixes
24260 bug 553. Bugfix on 0.2.0.x.
24261 - If we receive a general-purpose descriptor and then receive an
24262 identical bridge-purpose descriptor soon after, don't discard
24263 the next one as a duplicate.
24266 - If BridgeRelay is set to 1, then the default for
24267 PublishServerDescriptor is now "bridge" rather than "v2,v3".
24268 - If the user sets RelayBandwidthRate but doesn't set
24269 RelayBandwidthBurst, then make them equal rather than erroring out.
24272 Changes in version 0.2.0.13-alpha - 2007-12-21
24273 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
24274 Goodell, fixes many more bugs, and adds a lot of infrastructure for
24277 o New directory authorities:
24278 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
24282 - Only update guard status (usable / not usable) once we have
24283 enough directory information. This was causing us to always pick
24284 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
24285 causing us to discard all our guards on startup if we hadn't been
24286 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
24287 - Purge old entries from the "rephist" database and the hidden
24288 service descriptor databases even when DirPort is zero. Bugfix
24290 - We were ignoring our RelayBandwidthRate for the first 30 seconds
24291 after opening a circuit -- even a relayed circuit. Bugfix on
24293 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
24294 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
24295 crashing or mis-answering these types of requests.
24296 - Relays were publishing their server descriptor to v1 and v2
24297 directory authorities, but they didn't try publishing to v3-only
24298 authorities. Fix this; and also stop publishing to v1 authorities.
24300 - When we were reading router descriptors from cache, we were ignoring
24301 the annotations -- so for example we were reading in bridge-purpose
24302 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
24303 - When we decided to send a 503 response to a request for servers, we
24304 were then also sending the server descriptors: this defeats the
24305 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
24308 - Bridge relays now behave like clients with respect to time
24309 intervals for downloading new consensus documents -- otherwise they
24310 stand out. Bridge users now wait until the end of the interval,
24311 so their bridge relay will be sure to have a new consensus document.
24312 - Three new config options (AlternateDirAuthority,
24313 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
24314 user selectively replace the default directory authorities by type,
24315 rather than the all-or-nothing replacement that DirServer offers.
24316 - Tor can now be configured to read a GeoIP file from disk in one
24317 of two formats. This can be used by controllers to map IP addresses
24318 to countries. Eventually, it may support exit-by-country.
24319 - When possible, bridge relays remember which countries users
24320 are coming from, and report aggregate information in their
24321 extra-info documents, so that the bridge authorities can learn
24322 where Tor is blocked.
24323 - Bridge directory authorities now do reachability testing on the
24324 bridges they know. They provide router status summaries to the
24325 controller via "getinfo ns/purpose/bridge", and also dump summaries
24326 to a file periodically.
24327 - Stop fetching directory info so aggressively if your DirPort is
24328 on but your ORPort is off; stop fetching v2 dir info entirely.
24329 You can override these choices with the new FetchDirInfoEarly
24333 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
24334 consensus documents when there are too many relays at a single
24335 IP address. Now clear it in v2 network status documents too, and
24336 also clear it in routerinfo_t when the relay is no longer listed
24337 in the relevant networkstatus document.
24338 - Don't crash if we get an unexpected value for the
24339 PublishServerDescriptor config option. Reported by Matt Edman;
24340 bugfix on 0.2.0.9-alpha.
24341 - Our new v2 hidden service descriptor format allows descriptors
24342 that have no introduction points. But Tor crashed when we tried
24343 to build a descriptor with no intro points (and it would have
24344 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
24345 by Karsten Loesing.
24346 - Fix building with dmalloc 5.5.2 with glibc.
24347 - Reject uploaded descriptors and extrainfo documents if they're
24348 huge. Otherwise we'll cache them all over the network and it'll
24349 clog everything up. Reported by Aljosha Judmayer.
24350 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
24351 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
24352 - When the DANGEROUS_VERSION controller status event told us we're
24353 running an obsolete version, it used the string "OLD" to describe
24354 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
24355 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
24356 - If we can't expand our list of entry guards (e.g. because we're
24357 using bridges or we have StrictEntryNodes set), don't mark relays
24358 down when they fail a directory request. Otherwise we're too quick
24359 to mark all our entry points down. Bugfix on 0.1.2.x.
24360 - Fix handling of hex nicknames when answering controller requests for
24361 networkstatus by name, or when deciding whether to warn about unknown
24362 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
24363 - Fix a couple of hard-to-trigger autoconf problems that could result
24364 in really weird results on platforms whose sys/types.h files define
24365 nonstandard integer types. Bugfix on 0.1.2.x.
24366 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
24367 - Don't crash on name lookup when we have no current consensus. Fixes
24368 bug 538; bugfix on 0.2.0.x.
24369 - Only Tors that want to mirror the v2 directory info should
24370 create the "cached-status" directory in their datadir. (All Tors
24371 used to create it.) Bugfix on 0.2.0.9-alpha.
24372 - Directory authorities should only automatically download Extra Info
24373 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
24376 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
24377 consumers. (We already do this on HUP.)
24378 - Authorities and caches fetch the v2 networkstatus documents
24379 less often, now that v3 is encouraged.
24380 - Add a new config option BridgeRelay that specifies you want to
24381 be a bridge relay. Right now the only difference is that it makes
24382 you answer begin_dir requests, and it makes you cache dir info,
24383 even if your DirPort isn't on.
24384 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
24385 ask about source, timestamp of arrival, purpose, etc. We need
24386 something like this to help Vidalia not do GeoIP lookups on bridge
24388 - Allow multiple HashedControlPassword config lines, to support
24389 multiple controller passwords.
24390 - Authorities now decide whether they're authoritative for a given
24391 router based on the router's purpose.
24392 - New config options AuthDirBadDir and AuthDirListBadDirs for
24393 authorities to mark certain relays as "bad directories" in the
24394 networkstatus documents. Also supports the "!baddir" directive in
24395 the approved-routers file.
24398 Changes in version 0.2.0.12-alpha - 2007-11-16
24399 This twelfth development snapshot fixes some more build problems as
24400 well as a few minor bugs.
24403 - Make it build on OpenBSD again. Patch from tup.
24404 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
24405 package-building for Red Hat, OS X, etc.
24407 o Minor bugfixes (on 0.1.2.x):
24408 - Changing the ExitPolicyRejectPrivate setting should cause us to
24409 rebuild our server descriptor.
24411 o Minor bugfixes (on 0.2.0.x):
24412 - When we're lacking a consensus, don't try to perform rendezvous
24413 operations. Reported by Karsten Loesing.
24414 - Fix a small memory leak whenever we decide against using a
24415 newly picked entry guard. Reported by Mike Perry.
24416 - When authorities detected more than two relays running on the same
24417 IP address, they were clearing all the status flags but forgetting
24418 to clear the "hsdir" flag. So clients were being told that a
24419 given relay was the right choice for a v2 hsdir lookup, yet they
24420 never had its descriptor because it was marked as 'not running'
24422 - If we're trying to fetch a bridge descriptor and there's no way
24423 the bridge authority could help us (for example, we don't know
24424 a digest, or there is no bridge authority), don't be so eager to
24425 fall back to asking the bridge authority.
24426 - If we're using bridges or have strictentrynodes set, and our
24427 chosen exit is in the same family as all our bridges/entry guards,
24428 then be flexible about families.
24431 - When we negotiate a v2 link-layer connection (not yet implemented),
24432 accept RELAY_EARLY cells and turn them into RELAY cells if we've
24433 negotiated a v1 connection for their next step. Initial code for
24437 Changes in version 0.2.0.11-alpha - 2007-11-12
24438 This eleventh development snapshot fixes some build problems with
24439 the previous snapshot. It also includes a more secure-by-default exit
24440 policy for relays, fixes an enormous memory leak for exit relays, and
24441 fixes another bug where servers were falling out of the directory list.
24444 - Exit policies now reject connections that are addressed to a
24445 relay's public (external) IP address too, unless
24446 ExitPolicyRejectPrivate is turned off. We do this because too
24447 many relays are running nearby to services that trust them based
24448 on network address. Bugfix on 0.1.2.x.
24451 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
24452 on every successful resolve. Reported by Mike Perry; bugfix
24454 - On authorities, never downgrade to old router descriptors simply
24455 because they're listed in the consensus. This created a catch-22
24456 where we wouldn't list a new descriptor because there was an
24457 old one in the consensus, and we couldn't get the new one in the
24458 consensus because we wouldn't list it. Possible fix for bug 548.
24459 Also, this might cause bug 543 to appear on authorities; if so,
24460 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
24462 o Packaging fixes on 0.2.0.10-alpha:
24463 - We were including instructions about what to do with the
24464 src/config/fallback-consensus file, but we weren't actually
24465 including it in the tarball. Disable all of that for now.
24468 - Allow people to say PreferTunnelledDirConns rather than
24469 PreferTunneledDirConns, for those alternate-spellers out there.
24472 - Don't reevaluate all the information from our consensus document
24473 just because we've downloaded a v2 networkstatus that we intend
24474 to cache. Fixes bug 545; bugfix on 0.2.0.x.
24477 Changes in version 0.2.0.10-alpha - 2007-11-10
24478 This tenth development snapshot adds a third v3 directory authority
24479 run by Mike Perry, adds most of Karsten Loesing's new hidden service
24480 descriptor format, fixes a bad crash bug and new bridge bugs introduced
24481 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
24482 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
24483 addresses many more minor issues.
24485 o New directory authorities:
24486 - Set up ides (run by Mike Perry) as the third v3 directory authority.
24489 - Allow tunnelled directory connections to ask for an encrypted
24490 "begin_dir" connection or an anonymized "uses a full Tor circuit"
24491 connection independently. Now we can make anonymized begin_dir
24492 connections for (e.g.) more secure hidden service posting and
24494 - More progress on proposal 114: code from Karsten Loesing to
24495 implement new hidden service descriptor format.
24496 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
24497 accommodate the growing number of servers that use the default
24498 and are reaching it.
24499 - Directory authorities use a new formula for selecting which nodes
24500 to advertise as Guards: they must be in the top 7/8 in terms of
24501 how long we have known about them, and above the median of those
24502 nodes in terms of weighted fractional uptime.
24503 - Make "not enough dir info yet" warnings describe *why* Tor feels
24504 it doesn't have enough directory info yet.
24507 - Stop servers from crashing if they set a Family option (or
24508 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
24510 - Make bridge users work again -- the move to v3 directories in
24511 0.2.0.9-alpha had introduced a number of bugs that made bridges
24512 no longer work for clients.
24513 - When the clock jumps forward a lot, do not allow the bandwidth
24514 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
24516 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
24517 - When the consensus lists a router descriptor that we previously were
24518 mirroring, but that we considered non-canonical, reload the
24519 descriptor as canonical. This fixes bug 543 where Tor servers
24520 would start complaining after a few days that they don't have
24521 enough directory information to build a circuit.
24522 - Consider replacing the current consensus when certificates arrive
24523 that make the pending consensus valid. Previously, we were only
24524 considering replacement when the new certs _didn't_ help.
24525 - Fix an assert error on startup if we didn't already have the
24526 consensus and certs cached in our datadirectory: we were caching
24527 the consensus in consensus_waiting_for_certs but then free'ing it
24529 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
24530 Request) if we need more v3 certs but we've already got pending
24531 requests for all of them.
24532 - Correctly back off from failing certificate downloads. Fixes
24534 - Authorities don't vote on the Running flag if they have been running
24535 for less than 30 minutes themselves. Fixes bug 547, where a newly
24536 started authority would vote that everyone was down.
24538 o New requirements:
24539 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
24540 it, it had no AES, and it hasn't seen any security patches since
24544 - Clients now hold circuitless TLS connections open for 1.5 times
24545 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
24546 rebuild a new circuit over them within that timeframe. Previously,
24547 they held them open only for KeepalivePeriod (5 minutes).
24548 - Use "If-Modified-Since" to avoid retrieving consensus
24549 networkstatuses that we already have.
24550 - When we have no consensus, check FallbackNetworkstatusFile (defaults
24551 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
24552 we start knowing some directory caches.
24553 - When we receive a consensus from the future, warn about skew.
24554 - Improve skew reporting: try to give the user a better log message
24555 about how skewed they are, and how much this matters.
24556 - When we have a certificate for an authority, believe that
24557 certificate's claims about the authority's IP address.
24558 - New --quiet command-line option to suppress the default console log.
24559 Good in combination with --hash-password.
24560 - Authorities send back an X-Descriptor-Not-New header in response to
24561 an accepted-but-discarded descriptor upload. Partially implements
24563 - Make the log message for "tls error. breaking." more useful.
24564 - Better log messages about certificate downloads, to attempt to
24565 track down the second incarnation of bug 546.
24567 o Minor features (bridges):
24568 - If bridge users set UpdateBridgesFromAuthority, but the digest
24569 they ask for is a 404 from the bridge authority, they now fall
24570 back to trying the bridge directly.
24571 - Bridges now use begin_dir to publish their server descriptor to
24572 the bridge authority, even when they haven't set TunnelDirConns.
24574 o Minor features (controller):
24575 - When reporting clock skew, and we know that the clock is _at least
24576 as skewed_ as some value, but we don't know the actual value,
24577 report the value as a "minimum skew."
24580 - Update linux-tor-prio.sh script to allow QoS based on the uid of
24581 the Tor process. Patch from Marco Bonetti with tweaks from Mike
24585 - Refuse to start if both ORPort and UseBridges are set. Bugfix
24586 on 0.2.0.x, suggested by Matt Edman.
24587 - Don't stop fetching descriptors when FetchUselessDescriptors is
24588 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
24589 reported by tup and ioerror.
24590 - Better log message on vote from unknown authority.
24591 - Don't log "Launching 0 request for 0 router" message.
24593 o Minor bugfixes (memory leaks):
24594 - Stop leaking memory every time we parse a v3 certificate. Bugfix
24596 - Stop leaking memory every time we load a v3 certificate. Bugfix
24597 on 0.2.0.1-alpha. Fixes bug 536.
24598 - Stop leaking a cached networkstatus on exit. Bugfix on
24600 - Stop leaking voter information every time we free a consensus.
24601 Bugfix on 0.2.0.3-alpha.
24602 - Stop leaking signed data every time we check a voter signature.
24603 Bugfix on 0.2.0.3-alpha.
24604 - Stop leaking a signature every time we fail to parse a consensus or
24605 a vote. Bugfix on 0.2.0.3-alpha.
24606 - Stop leaking v2_download_status_map on shutdown. Bugfix on
24608 - Stop leaking conn->nickname every time we make a connection to a
24609 Tor relay without knowing its expected identity digest (e.g. when
24610 using bridges). Bugfix on 0.2.0.3-alpha.
24612 - Minor bugfixes (portability):
24613 - Run correctly on platforms where rlim_t is larger than unsigned
24614 long, and/or where the real limit for number of open files is
24615 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
24616 particular, these may be needed for OS X 10.5.
24619 Changes in version 0.1.2.18 - 2007-10-28
24620 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
24621 hidden service introduction that were causing huge delays, and a big
24622 bug that was causing some servers to disappear from the network status
24623 lists for a few hours each day.
24625 o Major bugfixes (crashes):
24626 - If a connection is shut down abruptly because of something that
24627 happened inside connection_flushed_some(), do not call
24628 connection_finished_flushing(). Should fix bug 451:
24629 "connection_stop_writing: Assertion conn->write_event failed"
24630 Bugfix on 0.1.2.7-alpha.
24631 - Fix possible segfaults in functions called from
24632 rend_process_relay_cell().
24634 o Major bugfixes (hidden services):
24635 - Hidden services were choosing introduction points uniquely by
24636 hexdigest, but when constructing the hidden service descriptor
24637 they merely wrote the (potentially ambiguous) nickname.
24638 - Clients now use the v2 intro format for hidden service
24639 connections: they specify their chosen rendezvous point by identity
24640 digest rather than by (potentially ambiguous) nickname. These
24641 changes could speed up hidden service connections dramatically.
24643 o Major bugfixes (other):
24644 - Stop publishing a new server descriptor just because we get a
24645 HUP signal. This led (in a roundabout way) to some servers getting
24646 dropped from the networkstatus lists for a few hours each day.
24647 - When looking for a circuit to cannibalize, consider family as well
24648 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
24649 circuit cannibalization).
24650 - When a router wasn't listed in a new networkstatus, we were leaving
24651 the flags for that router alone -- meaning it remained Named,
24652 Running, etc -- even though absence from the networkstatus means
24653 that it shouldn't be considered to exist at all anymore. Now we
24654 clear all the flags for routers that fall out of the networkstatus
24655 consensus. Fixes bug 529.
24658 - Don't try to access (or alter) the state file when running
24659 --list-fingerprint or --verify-config or --hash-password. Resolves
24661 - When generating information telling us how to extend to a given
24662 router, do not try to include the nickname if it is
24663 absent. Resolves bug 467.
24664 - Fix a user-triggerable segfault in expand_filename(). (There isn't
24665 a way to trigger this remotely.)
24666 - When sending a status event to the controller telling it that an
24667 OR address is reachable, set the port correctly. (Previously we
24668 were reporting the dir port.)
24669 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
24670 command. Bugfix on 0.1.2.17.
24671 - When loading bandwidth history, do not believe any information in
24672 the future. Fixes bug 434.
24673 - When loading entry guard information, do not believe any information
24675 - When we have our clock set far in the future and generate an
24676 onion key, then re-set our clock to be correct, we should not stop
24677 the onion key from getting rotated.
24678 - On some platforms, accept() can return a broken address. Detect
24679 this more quietly, and deal accordingly. Fixes bug 483.
24680 - It's not actually an error to find a non-pending entry in the DNS
24681 cache when canceling a pending resolve. Don't log unless stuff
24682 is fishy. Resolves bug 463.
24683 - Don't reset trusted dir server list when we set a configuration
24684 option. Patch from Robert Hogan.
24685 - Don't try to create the datadir when running --verify-config or
24686 --hash-password. Resolves bug 540.
24689 Changes in version 0.2.0.9-alpha - 2007-10-24
24690 This ninth development snapshot switches clients to the new v3 directory
24691 system; allows servers to be listed in the network status even when they
24692 have the same nickname as a registered server; and fixes many other
24693 bugs including a big one that was causing some servers to disappear
24694 from the network status lists for a few hours each day.
24696 o Major features (directory system):
24697 - Clients now download v3 consensus networkstatus documents instead
24698 of v2 networkstatus documents. Clients and caches now base their
24699 opinions about routers on these consensus documents. Clients only
24700 download router descriptors listed in the consensus.
24701 - Authorities now list servers who have the same nickname as
24702 a different named server, but list them with a new flag,
24703 "Unnamed". Now we can list servers that happen to pick the same
24704 nickname as a server that registered two years ago and then
24705 disappeared. Partially implements proposal 122.
24706 - If the consensus lists a router as "Unnamed", the name is assigned
24707 to a different router: do not identify the router by that name.
24708 Partially implements proposal 122.
24709 - Authorities can now come to a consensus on which method to use to
24710 compute the consensus. This gives us forward compatibility.
24713 - Stop publishing a new server descriptor just because we HUP or
24714 when we find our DirPort to be reachable but won't actually publish
24715 it. New descriptors without any real changes are dropped by the
24716 authorities, and can screw up our "publish every 18 hours" schedule.
24718 - When a router wasn't listed in a new networkstatus, we were leaving
24719 the flags for that router alone -- meaning it remained Named,
24720 Running, etc -- even though absence from the networkstatus means
24721 that it shouldn't be considered to exist at all anymore. Now we
24722 clear all the flags for routers that fall out of the networkstatus
24723 consensus. Fixes bug 529; bugfix on 0.1.2.x.
24724 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
24725 extrainfo documents and then discard them immediately for not
24726 matching the latest router. Bugfix on 0.2.0.1-alpha.
24728 o Minor features (v3 directory protocol):
24729 - Allow tor-gencert to generate a new certificate without replacing
24731 - Allow certificates to include an address.
24732 - When we change our directory-cache settings, reschedule all voting
24733 and download operations.
24734 - Reattempt certificate downloads immediately on failure, as long as
24735 we haven't failed a threshold number of times yet.
24736 - Delay retrying consensus downloads while we're downloading
24737 certificates to verify the one we just got. Also, count getting a
24738 consensus that we already have (or one that isn't valid) as a failure,
24739 and count failing to get the certificates after 20 minutes as a
24741 - Build circuits and download descriptors even if our consensus is a
24742 little expired. (This feature will go away once authorities are
24745 o Minor features (router descriptor cache):
24746 - If we find a cached-routers file that's been sitting around for more
24747 than 28 days unmodified, then most likely it's a leftover from
24748 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
24750 - When we (as a cache) download a descriptor because it was listed
24751 in a consensus, remember when the consensus was supposed to expire,
24752 and don't expire the descriptor until then.
24754 o Minor features (performance):
24755 - Call routerlist_remove_old_routers() much less often. This should
24756 speed startup, especially on directory caches.
24757 - Don't try to launch new descriptor downloads quite so often when we
24758 already have enough directory information to build circuits.
24759 - Base64 decoding was actually showing up on our profile when parsing
24760 the initial descriptor file; switch to an in-process all-at-once
24761 implementation that's about 3.5x times faster than calling out to
24764 o Minor features (compilation):
24765 - Detect non-ASCII platforms (if any still exist) and refuse to
24766 build there: some of our code assumes that 'A' is 65 and so on.
24768 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
24769 - Make the "next period" votes into "current period" votes immediately
24770 after publishing the consensus; avoid a heisenbug that made them
24771 stick around indefinitely.
24772 - When we discard a vote as a duplicate, do not report this as
24774 - Treat missing v3 keys or certificates as an error when running as a
24775 v3 directory authority.
24776 - When we're configured to be a v3 authority, but we're only listed
24777 as a non-v3 authority in our DirServer line for ourself, correct
24779 - If an authority doesn't have a qualified hostname, just put
24780 its address in the vote. This fixes the problem where we referred to
24781 "moria on moria:9031."
24782 - Distinguish between detached signatures for the wrong period, and
24783 detached signatures for a divergent vote.
24784 - Fix a small memory leak when computing a consensus.
24785 - When there's no consensus, we were forming a vote every 30
24786 minutes, but writing the "valid-after" line in our vote based
24787 on our configured V3AuthVotingInterval: so unless the intervals
24788 matched up, we immediately rejected our own vote because it didn't
24789 start at the voting interval that caused us to construct a vote.
24791 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
24792 - Delete unverified-consensus when the real consensus is set.
24793 - Consider retrying a consensus networkstatus fetch immediately
24794 after one fails: don't wait 60 seconds to notice.
24795 - When fetching a consensus as a cache, wait until a newer consensus
24796 should exist before trying to replace the current one.
24797 - Use a more forgiving schedule for retrying failed consensus
24798 downloads than for other types.
24800 o Minor bugfixes (other directory issues):
24801 - Correct the implementation of "download votes by digest." Bugfix on
24803 - Authorities no longer send back "400 you're unreachable please fix
24804 it" errors to Tor servers that aren't online all the time. We're
24805 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
24807 o Minor bugfixes (controller):
24808 - Don't reset trusted dir server list when we set a configuration
24809 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
24810 - Respond to INT and TERM SIGNAL commands before we execute the
24811 signal, in case the signal shuts us down. We had a patch in
24812 0.1.2.1-alpha that tried to do this by queueing the response on
24813 the connection's buffer before shutting down, but that really
24814 isn't the same thing at all. Bug located by Matt Edman.
24816 o Minor bugfixes (misc):
24817 - Correctly check for bad options to the "PublishServerDescriptor"
24818 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
24819 - Stop leaking memory on failing case of base32_decode, and make
24820 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
24821 - Don't try to download extrainfo documents when we're trying to
24822 fetch enough directory info to build a circuit: having enough
24823 info should get priority. Bugfix on 0.2.0.x.
24824 - Don't complain that "your server has not managed to confirm that its
24825 ports are reachable" if we haven't been able to build any circuits
24826 yet. Bug found by spending four hours without a v3 consensus. Bugfix
24828 - Detect the reason for failing to mmap a descriptor file we just
24829 wrote, and give a more useful log message. Fixes bug 533. Bugfix
24832 o Code simplifications and refactoring:
24833 - Remove support for the old bw_accounting file: we've been storing
24834 bandwidth accounting information in the state file since
24835 0.1.2.5-alpha. This may result in bandwidth accounting errors
24836 if you try to upgrade from 0.1.1.x or earlier, or if you try to
24837 downgrade to 0.1.1.x or earlier.
24838 - New convenience code to locate a file within the DataDirectory.
24839 - Move non-authority functionality out of dirvote.c.
24840 - Refactor the arguments for router_pick_{directory_|trusteddir}server
24841 so that they all take the same named flags.
24844 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
24845 Unix users an easy way to script their Tor process (e.g. by
24846 adjusting bandwidth based on the time of the day).
24849 Changes in version 0.2.0.8-alpha - 2007-10-12
24850 This eighth development snapshot fixes a crash bug that's been bothering
24851 us since February 2007, lets bridge authorities store a list of bridge
24852 descriptors they've seen, gets v3 directory voting closer to working,
24853 starts caching v3 directory consensus documents on directory mirrors,
24854 and fixes a variety of smaller issues including some minor memory leaks.
24856 o Major features (router descriptor cache):
24857 - Store routers in a file called cached-descriptors instead of in
24858 cached-routers. Initialize cached-descriptors from cached-routers
24859 if the old format is around. The new format allows us to store
24860 annotations along with descriptors.
24861 - Use annotations to record the time we received each descriptor, its
24862 source, and its purpose.
24863 - Disable the SETROUTERPURPOSE controller command: it is now
24865 - Controllers should now specify cache=no or cache=yes when using
24866 the +POSTDESCRIPTOR command.
24867 - Bridge authorities now write bridge descriptors to disk, meaning
24868 we can export them to other programs and begin distributing them
24871 o Major features (directory authorities):
24872 - When a v3 authority is missing votes or signatures, it now tries
24874 - Directory authorities track weighted fractional uptime as well as
24875 weighted mean-time-between failures. WFU is suitable for deciding
24876 whether a node is "usually up", while MTBF is suitable for deciding
24877 whether a node is "likely to stay up." We need both, because
24878 "usually up" is a good requirement for guards, while "likely to
24879 stay up" is a good requirement for long-lived connections.
24881 o Major features (v3 directory system):
24882 - Caches now download v3 network status documents as needed,
24883 and download the descriptors listed in them.
24884 - All hosts now attempt to download and keep fresh v3 authority
24885 certificates, and re-attempt after failures.
24886 - More internal-consistency checks for vote parsing.
24888 o Major bugfixes (crashes):
24889 - If a connection is shut down abruptly because of something that
24890 happened inside connection_flushed_some(), do not call
24891 connection_finished_flushing(). Should fix bug 451. Bugfix on
24894 o Major bugfixes (performance):
24895 - Fix really bad O(n^2) performance when parsing a long list of
24896 routers: Instead of searching the entire list for an "extra-info "
24897 string which usually wasn't there, once for every routerinfo
24898 we read, just scan lines forward until we find one we like.
24900 - When we add data to a write buffer in response to the data on that
24901 write buffer getting low because of a flush, do not consider the
24902 newly added data as a candidate for immediate flushing, but rather
24903 make it wait until the next round of writing. Otherwise, we flush
24904 and refill recursively, and a single greedy TLS connection can
24905 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
24907 o Minor features (v3 authority system):
24908 - Add more ways for tools to download the votes that lead to the
24910 - Send a 503 when low on bandwidth and a vote, consensus, or
24911 certificate is requested.
24912 - If-modified-since is now implemented properly for all kinds of
24913 certificate requests.
24915 o Minor bugfixes (network statuses):
24916 - Tweak the implementation of proposal 109 slightly: allow at most
24917 two Tor servers on the same IP address, except if it's the location
24918 of a directory authority, in which case allow five. Bugfix on
24921 o Minor bugfixes (controller):
24922 - When sending a status event to the controller telling it that an
24923 OR address is reachable, set the port correctly. (Previously we
24924 were reporting the dir port.) Bugfix on 0.1.2.x.
24926 o Minor bugfixes (v3 directory system):
24927 - Fix logic to look up a cert by its signing key digest. Bugfix on
24929 - Only change the reply to a vote to "OK" if it's not already
24930 set. This gets rid of annoying "400 OK" log messages, which may
24931 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
24932 - When we get a valid consensus, recompute the voting schedule.
24933 - Base the valid-after time of a vote on the consensus voting
24934 schedule, not on our preferred schedule.
24935 - Make the return values and messages from signature uploads and
24936 downloads more sensible.
24937 - Fix a memory leak when serving votes and consensus documents, and
24938 another when serving certificates.
24940 o Minor bugfixes (performance):
24941 - Use a slightly simpler string hashing algorithm (copying Python's
24942 instead of Java's) and optimize our digest hashing algorithm to take
24943 advantage of 64-bit platforms and to remove some possibly-costly
24945 - Fix a minor memory leak whenever we parse guards from our state
24946 file. Bugfix on 0.2.0.7-alpha.
24947 - Fix a minor memory leak whenever we write out a file. Bugfix on
24949 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
24950 command. Bugfix on 0.2.0.5-alpha.
24952 o Minor bugfixes (portability):
24953 - On some platforms, accept() can return a broken address. Detect
24954 this more quietly, and deal accordingly. Fixes bug 483.
24955 - Stop calling tor_strlower() on uninitialized memory in some cases.
24956 Bugfix in 0.2.0.7-alpha.
24958 o Minor bugfixes (usability):
24959 - Treat some 403 responses from directory servers as INFO rather than
24960 WARN-severity events.
24961 - It's not actually an error to find a non-pending entry in the DNS
24962 cache when canceling a pending resolve. Don't log unless stuff is
24963 fishy. Resolves bug 463.
24965 o Minor bugfixes (anonymity):
24966 - Never report that we've used more bandwidth than we're willing to
24967 relay: it leaks how much non-relay traffic we're using. Resolves
24969 - When looking for a circuit to cannibalize, consider family as well
24970 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
24971 circuit cannibalization).
24973 o Code simplifications and refactoring:
24974 - Make a bunch of functions static. Remove some dead code.
24975 - Pull out about a third of the really big routerlist.c; put it in a
24976 new module, networkstatus.c.
24977 - Merge the extra fields in local_routerstatus_t back into
24978 routerstatus_t: we used to need one routerstatus_t for each
24979 authority's opinion, plus a local_routerstatus_t for the locally
24980 computed consensus opinion. To save space, we put the locally
24981 modified fields into local_routerstatus_t, and only the common
24982 stuff into routerstatus_t. But once v3 directories are in use,
24983 clients and caches will no longer need to hold authority opinions;
24984 thus, the rationale for keeping the types separate is now gone.
24985 - Make the code used to reschedule and reattempt downloads more
24987 - Turn all 'Are we a directory server/mirror?' logic into a call to
24989 - Remove the code to generate the oldest (v1) directory format.
24990 The code has been disabled since 0.2.0.5-alpha.
24993 Changes in version 0.2.0.7-alpha - 2007-09-21
24994 This seventh development snapshot makes bridges work again, makes bridge
24995 authorities work for the first time, fixes two huge performance flaws
24996 in hidden services, and fixes a variety of minor issues.
24998 o New directory authorities:
24999 - Set up moria1 and tor26 as the first v3 directory authorities. See
25000 doc/spec/dir-spec.txt for details on the new directory design.
25002 o Major bugfixes (crashes):
25003 - Fix possible segfaults in functions called from
25004 rend_process_relay_cell(). Bugfix on 0.1.2.x.
25006 o Major bugfixes (bridges):
25007 - Fix a bug that made servers send a "404 Not found" in response to
25008 attempts to fetch their server descriptor. This caused Tor servers
25009 to take many minutes to establish reachability for their DirPort,
25010 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
25011 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
25012 users configure that and specify a bridge with an identity
25013 fingerprint, now they will lookup the bridge descriptor at the
25014 default bridge authority via a one-hop tunnel, but once circuits
25015 are established they will switch to a three-hop tunnel for later
25016 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
25018 o Major bugfixes (hidden services):
25019 - Hidden services were choosing introduction points uniquely by
25020 hexdigest, but when constructing the hidden service descriptor
25021 they merely wrote the (potentially ambiguous) nickname.
25022 - Clients now use the v2 intro format for hidden service
25023 connections: they specify their chosen rendezvous point by identity
25024 digest rather than by (potentially ambiguous) nickname. Both
25025 are bugfixes on 0.1.2.x, and they could speed up hidden service
25026 connections dramatically. Thanks to Karsten Loesing.
25028 o Minor features (security):
25029 - As a client, do not believe any server that tells us that an
25030 address maps to an internal address space.
25031 - Make it possible to enable HashedControlPassword and
25032 CookieAuthentication at the same time.
25034 o Minor features (guard nodes):
25035 - Tag every guard node in our state file with the version that
25036 we believe added it, or with our own version if we add it. This way,
25037 if a user temporarily runs an old version of Tor and then switches
25038 back to a new one, she doesn't automatically lose her guards.
25040 o Minor features (speed):
25041 - When implementing AES counter mode, update only the portions of the
25042 counter buffer that need to change, and don't keep separate
25043 network-order and host-order counters when they are the same (i.e.,
25044 on big-endian hosts.)
25046 o Minor features (controller):
25047 - Accept LF instead of CRLF on controller, since some software has a
25048 hard time generating real Internet newlines.
25049 - Add GETINFO values for the server status events
25050 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
25053 o Removed features:
25054 - Routers no longer include bandwidth-history lines in their
25055 descriptors; this information is already available in extra-info
25056 documents, and including it in router descriptors took up 60%
25057 (!) of compressed router descriptor downloads. Completes
25058 implementation of proposal 104.
25059 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
25060 and TorControl.py, as they use the old v0 controller protocol,
25061 and are obsoleted by TorFlow anyway.
25062 - Drop support for v1 rendezvous descriptors, since we never used
25063 them anyway, and the code has probably rotted by now. Based on
25064 patch from Karsten Loesing.
25065 - On OSX, stop warning the user that kqueue support in libevent is
25066 "experimental", since it seems to have worked fine for ages.
25069 - When generating information telling us how to extend to a given
25070 router, do not try to include the nickname if it is absent. Fixes
25071 bug 467. Bugfix on 0.2.0.3-alpha.
25072 - Fix a user-triggerable (but not remotely-triggerable) segfault
25073 in expand_filename(). Bugfix on 0.1.2.x.
25074 - Fix a memory leak when freeing incomplete requests from DNSPort.
25075 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
25076 - Don't try to access (or alter) the state file when running
25077 --list-fingerprint or --verify-config or --hash-password. (Resolves
25078 bug 499.) Bugfix on 0.1.2.x.
25079 - Servers used to decline to publish their DirPort if their
25080 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
25081 were below a threshold. Now they only look at BandwidthRate and
25082 RelayBandwidthRate. Bugfix on 0.1.2.x.
25083 - Remove an optimization in the AES counter-mode code that assumed
25084 that the counter never exceeded 2^68. When the counter can be set
25085 arbitrarily as an IV (as it is by Karsten's new hidden services
25086 code), this assumption no longer holds. Bugfix on 0.1.2.x.
25087 - Resume listing "AUTHORITY" flag for authorities in network status.
25088 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
25090 o Code simplifications and refactoring:
25091 - Revamp file-writing logic so we don't need to have the entire
25092 contents of a file in memory at once before we write to disk. Tor,
25094 - Turn "descriptor store" into a full-fledged type.
25095 - Move all NT services code into a separate source file.
25096 - Unify all code that computes medians, percentile elements, etc.
25097 - Get rid of a needless malloc when parsing address policies.
25100 Changes in version 0.1.2.17 - 2007-08-30
25101 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
25102 X bundles. Vidalia 0.0.14 makes authentication required for the
25103 ControlPort in the default configuration, which addresses important
25104 security risks. Everybody who uses Vidalia (or another controller)
25107 In addition, this Tor update fixes major load balancing problems with
25108 path selection, which should speed things up a lot once many people
25111 o Major bugfixes (security):
25112 - We removed support for the old (v0) control protocol. It has been
25113 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
25114 become more of a headache than it's worth.
25116 o Major bugfixes (load balancing):
25117 - When choosing nodes for non-guard positions, weight guards
25118 proportionally less, since they already have enough load. Patch
25120 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
25121 will allow fast Tor servers to get more attention.
25122 - When we're upgrading from an old Tor version, forget our current
25123 guards and pick new ones according to the new weightings. These
25124 three load balancing patches could raise effective network capacity
25125 by a factor of four. Thanks to Mike Perry for measurements.
25127 o Major bugfixes (stream expiration):
25128 - Expire not-yet-successful application streams in all cases if
25129 they've been around longer than SocksTimeout. Right now there are
25130 some cases where the stream will live forever, demanding a new
25131 circuit every 15 seconds. Fixes bug 454; reported by lodger.
25133 o Minor features (controller):
25134 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
25135 is valid before any authentication has been received. It tells
25136 a controller what kind of authentication is expected, and what
25137 protocol is spoken. Implements proposal 119.
25139 o Minor bugfixes (performance):
25140 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
25141 greatly speeding up loading cached-routers from disk on startup.
25142 - Disable sentinel-based debugging for buffer code: we squashed all
25143 the bugs that this was supposed to detect a long time ago, and now
25144 its only effect is to change our buffer sizes from nice powers of
25145 two (which platform mallocs tend to like) to values slightly over
25146 powers of two (which make some platform mallocs sad).
25148 o Minor bugfixes (misc):
25149 - If exit bandwidth ever exceeds one third of total bandwidth, then
25150 use the correct formula to weight exit nodes when choosing paths.
25151 Based on patch from Mike Perry.
25152 - Choose perfectly fairly among routers when choosing by bandwidth and
25153 weighting by fraction of bandwidth provided by exits. Previously, we
25154 would choose with only approximate fairness, and correct ourselves
25155 if we ran off the end of the list.
25156 - If we require CookieAuthentication but we fail to write the
25157 cookie file, we would warn but not exit, and end up in a state
25158 where no controller could authenticate. Now we exit.
25159 - If we require CookieAuthentication, stop generating a new cookie
25160 every time we change any piece of our config.
25161 - Refuse to start with certain directory authority keys, and
25162 encourage people using them to stop.
25163 - Terminate multi-line control events properly. Original patch
25165 - Fix a minor memory leak when we fail to find enough suitable
25166 servers to choose a circuit.
25167 - Stop leaking part of the descriptor when we run into a particularly
25168 unparseable piece of it.
25171 Changes in version 0.2.0.6-alpha - 2007-08-26
25172 This sixth development snapshot features a new Vidalia version in the
25173 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
25174 the ControlPort in the default configuration, which addresses important
25177 In addition, this snapshot fixes major load balancing problems
25178 with path selection, which should speed things up a lot once many
25179 people have upgraded. The directory authorities also use a new
25180 mean-time-between-failure approach to tracking which servers are stable,
25181 rather than just looking at the most recent uptime.
25183 o New directory authorities:
25184 - Set up Tonga as the default bridge directory authority.
25187 - Directory authorities now track servers by weighted
25188 mean-times-between-failures. When we have 4 or more days of data,
25189 use measured MTBF rather than declared uptime to decide whether
25190 to call a router Stable. Implements proposal 108.
25192 o Major bugfixes (load balancing):
25193 - When choosing nodes for non-guard positions, weight guards
25194 proportionally less, since they already have enough load. Patch
25196 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
25197 will allow fast Tor servers to get more attention.
25198 - When we're upgrading from an old Tor version, forget our current
25199 guards and pick new ones according to the new weightings. These
25200 three load balancing patches could raise effective network capacity
25201 by a factor of four. Thanks to Mike Perry for measurements.
25203 o Major bugfixes (descriptor parsing):
25204 - Handle unexpected whitespace better in malformed descriptors. Bug
25205 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
25208 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
25209 GETINFO for Torstat to use until it can switch to using extrainfos.
25210 - Optionally (if built with -DEXPORTMALLINFO) export the output
25211 of mallinfo via http, as tor/mallinfo.txt. Only accessible
25215 - Do not intermix bridge routers with controller-added
25216 routers. (Bugfix on 0.2.0.x)
25217 - Do not fail with an assert when accept() returns an unexpected
25218 address family. Addresses but does not wholly fix bug 483. (Bugfix
25220 - Let directory authorities startup even when they can't generate
25221 a descriptor immediately, e.g. because they don't know their
25223 - Stop putting the authentication cookie in a file called "0"
25224 in your working directory if you don't specify anything for the
25225 new CookieAuthFile option. Reported by Matt Edman.
25226 - Make it possible to read the PROTOCOLINFO response in a way that
25227 conforms to our control-spec. Reported by Matt Edman.
25228 - Fix a minor memory leak when we fail to find enough suitable
25229 servers to choose a circuit. Bugfix on 0.1.2.x.
25230 - Stop leaking part of the descriptor when we run into a particularly
25231 unparseable piece of it. Bugfix on 0.1.2.x.
25232 - Unmap the extrainfo cache file on exit.
25235 Changes in version 0.2.0.5-alpha - 2007-08-19
25236 This fifth development snapshot fixes compilation on Windows again;
25237 fixes an obnoxious client-side bug that slowed things down and put
25238 extra load on the network; gets us closer to using the v3 directory
25239 voting scheme; makes it easier for Tor controllers to use cookie-based
25240 authentication; and fixes a variety of other bugs.
25242 o Removed features:
25243 - Version 1 directories are no longer generated in full. Instead,
25244 authorities generate and serve "stub" v1 directories that list
25245 no servers. This will stop Tor versions 0.1.0.x and earlier from
25246 working, but (for security reasons) nobody should be running those
25249 o Major bugfixes (compilation, 0.2.0.x):
25250 - Try to fix Win32 compilation again: improve checking for IPv6 types.
25251 - Try to fix MSVC compilation: build correctly on platforms that do
25252 not define s6_addr16 or s6_addr32.
25253 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
25256 o Major bugfixes (stream expiration):
25257 - Expire not-yet-successful application streams in all cases if
25258 they've been around longer than SocksTimeout. Right now there are
25259 some cases where the stream will live forever, demanding a new
25260 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
25261 reported by lodger.
25263 o Minor features (directory servers):
25264 - When somebody requests a list of statuses or servers, and we have
25265 none of those, return a 404 rather than an empty 200.
25267 o Minor features (directory voting):
25268 - Store v3 consensus status consensuses on disk, and reload them
25271 o Minor features (security):
25272 - Warn about unsafe ControlPort configurations.
25273 - Refuse to start with certain directory authority keys, and
25274 encourage people using them to stop.
25276 o Minor features (controller):
25277 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
25278 is valid before any authentication has been received. It tells
25279 a controller what kind of authentication is expected, and what
25280 protocol is spoken. Implements proposal 119.
25281 - New config option CookieAuthFile to choose a new location for the
25282 cookie authentication file, and config option
25283 CookieAuthFileGroupReadable to make it group-readable.
25285 o Minor features (unit testing):
25286 - Add command-line arguments to unit-test executable so that we can
25287 invoke any chosen test from the command line rather than having
25288 to run the whole test suite at once; and so that we can turn on
25289 logging for the unit tests.
25291 o Minor bugfixes (on 0.1.2.x):
25292 - If we require CookieAuthentication but we fail to write the
25293 cookie file, we would warn but not exit, and end up in a state
25294 where no controller could authenticate. Now we exit.
25295 - If we require CookieAuthentication, stop generating a new cookie
25296 every time we change any piece of our config.
25297 - When loading bandwidth history, do not believe any information in
25298 the future. Fixes bug 434.
25299 - When loading entry guard information, do not believe any information
25301 - When we have our clock set far in the future and generate an
25302 onion key, then re-set our clock to be correct, we should not stop
25303 the onion key from getting rotated.
25304 - Clean up torrc sample config file.
25305 - Do not automatically run configure from autogen.sh. This
25306 non-standard behavior tended to annoy people who have built other
25309 o Minor bugfixes (on 0.2.0.x):
25310 - Fix a bug with AutomapHostsOnResolve that would always cause
25311 the second request to fail. Bug reported by Kate. Bugfix on
25313 - Fix a bug in ADDRMAP controller replies that would sometimes
25314 try to print a NULL. Patch from tup.
25315 - Read v3 directory authority keys from the right location.
25316 - Numerous bugfixes to directory voting code.
25319 Changes in version 0.1.2.16 - 2007-08-01
25320 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
25321 remote attacker in certain situations to rewrite the user's torrc
25322 configuration file. This can completely compromise anonymity of users
25323 in most configurations, including those running the Vidalia bundles,
25324 TorK, etc. Or worse.
25326 o Major security fixes:
25327 - Close immediately after missing authentication on control port;
25328 do not allow multiple authentication attempts.
25331 Changes in version 0.2.0.4-alpha - 2007-08-01
25332 This fourth development snapshot fixes a critical security vulnerability
25333 for most users, specifically those running Vidalia, TorK, etc. Everybody
25334 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
25336 o Major security fixes:
25337 - Close immediately after missing authentication on control port;
25338 do not allow multiple authentication attempts.
25340 o Major bugfixes (compilation):
25341 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
25344 o Minor features (performance):
25345 - Be even more aggressive about releasing RAM from small
25346 empty buffers. Thanks to our free-list code, this shouldn't be too
25347 performance-intensive.
25348 - Disable sentinel-based debugging for buffer code: we squashed all
25349 the bugs that this was supposed to detect a long time ago, and
25350 now its only effect is to change our buffer sizes from nice
25351 powers of two (which platform mallocs tend to like) to values
25352 slightly over powers of two (which make some platform mallocs sad).
25353 - Log malloc statistics from mallinfo() on platforms where it
25357 Changes in version 0.2.0.3-alpha - 2007-07-29
25358 This third development snapshot introduces new experimental
25359 blocking-resistance features and a preliminary version of the v3
25360 directory voting design, and includes many other smaller features
25364 - The first pieces of our "bridge" design for blocking-resistance
25365 are implemented. People can run bridge directory authorities;
25366 people can run bridges; and people can configure their Tor clients
25367 with a set of bridges to use as the first hop into the Tor network.
25368 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
25370 - Create listener connections before we setuid to the configured
25371 User and Group. Now non-Windows users can choose port values
25372 under 1024, start Tor as root, and have Tor bind those ports
25373 before it changes to another UID. (Windows users could already
25375 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
25376 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
25377 on "vserver" accounts. (Patch from coderman.)
25378 - Be even more aggressive about separating local traffic from relayed
25379 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
25381 o Major features (experimental):
25382 - First cut of code for "v3 dir voting": directory authorities will
25383 vote on a common network status document rather than each publishing
25384 their own opinion. This code needs more testing and more corner-case
25385 handling before it's ready for use.
25388 - Directory authorities now call routers Fast if their bandwidth is
25389 at least 100KB/s, and consider their bandwidth adequate to be a
25390 Guard if it is at least 250KB/s, no matter the medians. This fix
25391 complements proposal 107. [Bugfix on 0.1.2.x]
25392 - Directory authorities now never mark more than 3 servers per IP as
25393 Valid and Running. (Implements proposal 109, by Kevin Bauer and
25395 - Minor change to organizationName and commonName generation
25396 procedures in TLS certificates during Tor handshakes, to invalidate
25397 some earlier censorware approaches. This is not a long-term
25398 solution, but applying it will give us a bit of time to look into
25399 the epidemiology of countermeasures as they spread.
25401 o Major bugfixes (directory):
25402 - Rewrite directory tokenization code to never run off the end of
25403 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
25405 o Minor features (controller):
25406 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
25407 match requests to applications. (Patch from Robert Hogan.)
25408 - Report address and port correctly on connections to DNSPort. (Patch
25409 from Robert Hogan.)
25410 - Add a RESOLVE command to launch hostname lookups. (Original patch
25411 from Robert Hogan.)
25412 - Add GETINFO status/enough-dir-info to let controllers tell whether
25413 Tor has downloaded sufficient directory information. (Patch
25415 - You can now use the ControlSocket option to tell Tor to listen for
25416 controller connections on Unix domain sockets on systems that
25417 support them. (Patch from Peter Palfrader.)
25418 - STREAM NEW events are generated for DNSPort requests and for
25419 tunneled directory connections. (Patch from Robert Hogan.)
25420 - New "GETINFO address-mappings/*" command to get address mappings
25421 with expiry information. "addr-mappings/*" is now deprecated.
25424 o Minor features (misc):
25425 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
25427 - The tor-gencert tool for v3 directory authorities now creates all
25428 files as readable to the file creator only, and write-protects
25429 the authority identity key.
25430 - When dumping memory usage, list bytes used in buffer memory
25432 - When running with dmalloc, dump more stats on hup and on exit.
25433 - Directory authorities now fail quickly and (relatively) harmlessly
25434 if they generate a network status document that is somehow
25437 o Traffic load balancing improvements:
25438 - If exit bandwidth ever exceeds one third of total bandwidth, then
25439 use the correct formula to weight exit nodes when choosing paths.
25440 (Based on patch from Mike Perry.)
25441 - Choose perfectly fairly among routers when choosing by bandwidth and
25442 weighting by fraction of bandwidth provided by exits. Previously, we
25443 would choose with only approximate fairness, and correct ourselves
25444 if we ran off the end of the list. [Bugfix on 0.1.2.x]
25446 o Performance improvements:
25447 - Be more aggressive with freeing buffer RAM or putting it on the
25449 - Use Critical Sections rather than Mutexes for synchronizing threads
25450 on win32; Mutexes are heavier-weight, and designed for synchronizing
25453 o Deprecated and removed features:
25454 - RedirectExits is now deprecated.
25455 - Stop allowing address masks that do not correspond to bit prefixes.
25456 We have warned about these for a really long time; now it's time
25457 to reject them. (Patch from croup.)
25459 o Minor bugfixes (directory):
25460 - Fix another crash bug related to extra-info caching. (Bug found by
25461 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
25462 - Directories no longer return a "304 not modified" when they don't
25463 have the networkstatus the client asked for. Also fix a memory
25464 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
25465 - We had accidentally labelled 0.1.2.x directory servers as not
25466 suitable for begin_dir requests, and had labelled no directory
25467 servers as suitable for uploading extra-info documents. [Bugfix
25470 o Minor bugfixes (dns):
25471 - Fix a crash when DNSPort is set more than once. (Patch from Robert
25472 Hogan.) [Bugfix on 0.2.0.2-alpha]
25473 - Add DNSPort connections to the global connection list, so that we
25474 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
25476 - Fix a dangling reference that could lead to a crash when DNSPort is
25477 changed or closed (Patch from Robert Hogan.) [Bugfix on
25480 o Minor bugfixes (controller):
25481 - Provide DNS expiry times in GMT, not in local time. For backward
25482 compatibility, ADDRMAP events only provide GMT expiry in an extended
25483 field. "GETINFO address-mappings" always does the right thing.
25484 - Use CRLF line endings properly in NS events.
25485 - Terminate multi-line control events properly. (Original patch
25486 from tup.) [Bugfix on 0.1.2.x-alpha]
25487 - Do not include spaces in SOURCE_ADDR fields in STREAM
25488 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
25491 Changes in version 0.1.2.15 - 2007-07-17
25492 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
25493 problems, fixes compilation on BSD, and fixes a variety of other
25494 bugs. Everybody should upgrade.
25496 o Major bugfixes (compilation):
25497 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
25499 o Major bugfixes (crashes):
25500 - Try even harder not to dereference the first character after
25501 an mmap(). Reported by lodger.
25502 - Fix a crash bug in directory authorities when we re-number the
25503 routerlist while inserting a new router.
25504 - When the cached-routers file is an even multiple of the page size,
25505 don't run off the end and crash. (Fixes bug 455; based on idea
25507 - Fix eventdns.c behavior on Solaris: It is critical to include
25508 orconfig.h _before_ sys/types.h, so that we can get the expected
25509 definition of _FILE_OFFSET_BITS.
25511 o Major bugfixes (security):
25512 - Fix a possible buffer overrun when using BSD natd support. Bug
25514 - When sending destroy cells from a circuit's origin, don't include
25515 the reason for tearing down the circuit. The spec says we didn't,
25516 and now we actually don't. Reported by lodger.
25517 - Keep streamids from different exits on a circuit separate. This
25518 bug may have allowed other routers on a given circuit to inject
25519 cells into streams. Reported by lodger; fixes bug 446.
25520 - If there's a never-before-connected-to guard node in our list,
25521 never choose any guards past it. This way we don't expand our
25522 guard list unless we need to.
25524 o Minor bugfixes (guard nodes):
25525 - Weight guard selection by bandwidth, so that low-bandwidth nodes
25526 don't get overused as guards.
25528 o Minor bugfixes (directory):
25529 - Correctly count the number of authorities that recommend each
25530 version. Previously, we were under-counting by 1.
25531 - Fix a potential crash bug when we load many server descriptors at
25532 once and some of them make others of them obsolete. Fixes bug 458.
25534 o Minor bugfixes (hidden services):
25535 - Stop tearing down the whole circuit when the user asks for a
25536 connection to a port that the hidden service didn't configure.
25539 o Minor bugfixes (misc):
25540 - On Windows, we were preventing other processes from reading
25541 cached-routers while Tor was running. Reported by janbar.
25542 - Fix a possible (but very unlikely) bug in picking routers by
25543 bandwidth. Add a log message to confirm that it is in fact
25544 unlikely. Patch from lodger.
25545 - Backport a couple of memory leak fixes.
25546 - Backport miscellaneous cosmetic bugfixes.
25549 Changes in version 0.2.0.2-alpha - 2007-06-02
25550 o Major bugfixes on 0.2.0.1-alpha:
25551 - Fix an assertion failure related to servers without extra-info digests.
25552 Resolves bugs 441 and 442.
25554 o Minor features (directory):
25555 - Support "If-Modified-Since" when answering HTTP requests for
25556 directories, running-routers documents, and network-status documents.
25557 (There's no need to support it for router descriptors, since those
25558 are downloaded by descriptor digest.)
25560 o Minor build issues:
25561 - Clear up some MIPSPro compiler warnings.
25562 - When building from a tarball on a machine that happens to have SVK
25563 installed, report the micro-revision as whatever version existed
25564 in the tarball, not as "x".
25567 Changes in version 0.2.0.1-alpha - 2007-06-01
25568 This early development snapshot provides new features for people running
25569 Tor as both a client and a server (check out the new RelayBandwidth
25570 config options); lets Tor run as a DNS proxy; and generally moves us
25571 forward on a lot of fronts.
25573 o Major features, server usability:
25574 - New config options RelayBandwidthRate and RelayBandwidthBurst:
25575 a separate set of token buckets for relayed traffic. Right now
25576 relayed traffic is defined as answers to directory requests, and
25577 OR connections that don't have any local circuits on them.
25579 o Major features, client usability:
25580 - A client-side DNS proxy feature to replace the need for
25581 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
25582 for DNS requests on port 9999, use the Tor network to resolve them
25583 anonymously, and send the reply back like a regular DNS server.
25584 The code still only implements a subset of DNS.
25585 - Make PreferTunneledDirConns and TunnelDirConns work even when
25586 we have no cached directory info. This means Tor clients can now
25587 do all of their connections protected by TLS.
25589 o Major features, performance and efficiency:
25590 - Directory authorities accept and serve "extra info" documents for
25591 routers. These documents contain fields from router descriptors
25592 that aren't usually needed, and that use a lot of excess
25593 bandwidth. Once these fields are removed from router descriptors,
25594 the bandwidth savings should be about 60%. [Partially implements
25596 - Servers upload extra-info documents to any authority that accepts
25597 them. Authorities (and caches that have been configured to download
25598 extra-info documents) download them as needed. [Partially implements
25600 - Change the way that Tor buffers data that it is waiting to write.
25601 Instead of queueing data cells in an enormous ring buffer for each
25602 client->OR or OR->OR connection, we now queue cells on a separate
25603 queue for each circuit. This lets us use less slack memory, and
25604 will eventually let us be smarter about prioritizing different kinds
25606 - Use memory pools to allocate cells with better speed and memory
25607 efficiency, especially on platforms where malloc() is inefficient.
25608 - Stop reading on edge connections when their corresponding circuit
25609 buffers are full; start again as the circuits empty out.
25611 o Major features, other:
25612 - Add an HSAuthorityRecordStats option that hidden service authorities
25613 can use to track statistics of overall hidden service usage without
25614 logging information that would be very useful to an attacker.
25615 - Start work implementing multi-level keys for directory authorities:
25616 Add a standalone tool to generate key certificates. (Proposal 103.)
25619 - Directory authorities now call routers Stable if they have an
25620 uptime of at least 30 days, even if that's not the median uptime
25621 in the network. Implements proposal 107, suggested by Kevin Bauer
25624 o Minor fixes (resource management):
25625 - Count the number of open sockets separately from the number
25626 of active connection_t objects. This will let us avoid underusing
25627 our allocated connection limit.
25628 - We no longer use socket pairs to link an edge connection to an
25629 anonymous directory connection or a DirPort test connection.
25630 Instead, we track the link internally and transfer the data
25631 in-process. This saves two sockets per "linked" connection (at the
25632 client and at the server), and avoids the nasty Windows socketpair()
25634 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
25635 for every single inactive connection_t. Free items from the
25636 4k/16k-buffer free lists when they haven't been used for a while.
25638 o Minor features (build):
25639 - Make autoconf search for libevent, openssl, and zlib consistently.
25640 - Update deprecated macros in configure.in.
25641 - When warning about missing headers, tell the user to let us
25642 know if the compile succeeds anyway, so we can downgrade the
25644 - Include the current subversion revision as part of the version
25645 string: either fetch it directly if we're in an SVN checkout, do
25646 some magic to guess it if we're in an SVK checkout, or use
25647 the last-detected version if we're building from a .tar.gz.
25648 Use this version consistently in log messages.
25650 o Minor features (logging):
25651 - Always prepend "Bug: " to any log message about a bug.
25652 - Put a platform string (e.g. "Linux i686") in the startup log
25653 message, so when people paste just their logs, we know if it's
25654 OpenBSD or Windows or what.
25655 - When logging memory usage, break down memory used in buffers by
25658 o Minor features (directory system):
25659 - New config option V2AuthoritativeDirectory that all directory
25660 authorities should set. This will let future authorities choose
25661 not to serve V2 directory information.
25662 - Directory authorities allow multiple router descriptors and/or extra
25663 info documents to be uploaded in a single go. This will make
25664 implementing proposal 104 simpler.
25666 o Minor features (controller):
25667 - Add a new config option __DisablePredictedCircuits designed for
25668 use by the controller, when we don't want Tor to build any circuits
25670 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
25671 so we can exit from the middle of the circuit.
25672 - Implement "getinfo status/circuit-established".
25673 - Implement "getinfo status/version/..." so a controller can tell
25674 whether the current version is recommended, and whether any versions
25675 are good, and how many authorities agree. (Patch from shibz.)
25677 o Minor features (hidden services):
25678 - Allow multiple HiddenServicePort directives with the same virtual
25679 port; when they occur, the user is sent round-robin to one
25680 of the target ports chosen at random. Partially fixes bug 393 by
25681 adding limited ad-hoc round-robining.
25683 o Minor features (other):
25685 - Add a new AutomapHostsOnResolve option: when it is enabled, any
25686 resolve request for hosts matching a given pattern causes Tor to
25687 generate an internal virtual address mapping for that host. This
25688 allows DNSPort to work sensibly with hidden service users. By
25689 default, .exit and .onion addresses are remapped; the list of
25690 patterns can be reconfigured with AutomapHostsSuffixes.
25691 - Add an "-F" option to tor-resolve to force a resolve for a .onion
25692 address. Thanks to the AutomapHostsOnResolve option, this is no
25693 longer a completely silly thing to do.
25694 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
25695 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
25696 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
25697 minus 1 byte: the actual maximum declared bandwidth.
25699 o Removed features:
25700 - Removed support for the old binary "version 0" controller protocol.
25701 This has been deprecated since 0.1.1, and warnings have been issued
25702 since 0.1.2. When we encounter a v0 control message, we now send
25703 back an error and close the connection.
25704 - Remove the old "dns worker" server DNS code: it hasn't been default
25705 since 0.1.2.2-alpha, and all the servers seem to be using the new
25708 o Minor bugfixes (portability):
25709 - Even though Windows is equally happy with / and \ as path separators,
25710 try to use \ consistently on Windows and / consistently on Unix: it
25711 makes the log messages nicer.
25712 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
25713 - Read resolv.conf files correctly on platforms where read() returns
25714 partial results on small file reads.
25716 o Minor bugfixes (directory):
25717 - Correctly enforce that elements of directory objects do not appear
25718 more often than they are allowed to appear.
25719 - When we are reporting the DirServer line we just parsed, we were
25720 logging the second stanza of the key fingerprint, not the first.
25722 o Minor bugfixes (logging):
25723 - When we hit an EOF on a log (probably because we're shutting down),
25724 don't try to remove the log from the list: just mark it as
25725 unusable. (Bulletproofs against bug 222.)
25727 o Minor bugfixes (other):
25728 - In the exitlist script, only consider the most recently published
25729 server descriptor for each server. Also, when the user requests
25730 a list of servers that _reject_ connections to a given address,
25731 explicitly exclude the IPs that also have servers that accept
25732 connections to that address. (Resolves bug 405.)
25733 - Stop allowing hibernating servers to be "stable" or "fast".
25734 - On Windows, we were preventing other processes from reading
25735 cached-routers while Tor was running. (Reported by janbar)
25736 - Make the NodeFamilies config option work. (Reported by
25737 lodger -- it has never actually worked, even though we added it
25739 - Check return values from pthread_mutex functions.
25740 - Don't save non-general-purpose router descriptors to the disk cache,
25741 because we have no way of remembering what their purpose was when
25743 - Add even more asserts to hunt down bug 417.
25744 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
25745 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
25746 Add a log message to confirm that it is in fact unlikely.
25748 o Minor bugfixes (controller):
25749 - Make 'getinfo fingerprint' return a 551 error if we're not a
25750 server, so we match what the control spec claims we do. Reported
25752 - Fix a typo in an error message when extendcircuit fails that
25753 caused us to not follow the \r\n-based delimiter protocol. Reported
25756 o Code simplifications and refactoring:
25757 - Stop passing around circuit_t and crypt_path_t pointers that are
25758 implicit in other procedure arguments.
25759 - Drop the old code to choke directory connections when the
25760 corresponding OR connections got full: thanks to the cell queue
25761 feature, OR conns don't get full any more.
25762 - Make dns_resolve() handle attaching connections to circuits
25763 properly, so the caller doesn't have to.
25764 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
25765 - Keep the connection array as a dynamic smartlist_t, rather than as
25766 a fixed-sized array. This is important, as the number of connections
25767 is becoming increasingly decoupled from the number of sockets.
25770 Changes in version 0.1.2.14 - 2007-05-25
25771 Tor 0.1.2.14 changes the addresses of two directory authorities (this
25772 change especially affects those who serve or use hidden services),
25773 and fixes several other crash- and security-related bugs.
25775 o Directory authority changes:
25776 - Two directory authorities (moria1 and moria2) just moved to new
25777 IP addresses. This change will particularly affect those who serve
25778 or use hidden services.
25780 o Major bugfixes (crashes):
25781 - If a directory server runs out of space in the connection table
25782 as it's processing a begin_dir request, it will free the exit stream
25783 but leave it attached to the circuit, leading to unpredictable
25784 behavior. (Reported by seeess, fixes bug 425.)
25785 - Fix a bug in dirserv_remove_invalid() that would cause authorities
25786 to corrupt memory under some really unlikely scenarios.
25787 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
25788 - Avoid segfaults when reading from mmaped descriptor file. (Reported
25791 o Major bugfixes (security):
25792 - When choosing an entry guard for a circuit, avoid using guards
25793 that are in the same family as the chosen exit -- not just guards
25794 that are exactly the chosen exit. (Reported by lodger.)
25796 o Major bugfixes (resource management):
25797 - If a directory authority is down, skip it when deciding where to get
25798 networkstatus objects or descriptors. Otherwise we keep asking
25799 every 10 seconds forever. Fixes bug 384.
25800 - Count it as a failure if we fetch a valid network-status but we
25801 don't want to keep it. Otherwise we'll keep fetching it and keep
25802 not wanting to keep it. Fixes part of bug 422.
25803 - If all of our dirservers have given us bad or no networkstatuses
25804 lately, then stop hammering them once per minute even when we
25805 think they're failed. Fixes another part of bug 422.
25808 - Actually set the purpose correctly for descriptors inserted with
25809 purpose=controller.
25810 - When we have k non-v2 authorities in our DirServer config,
25811 we ignored the last k authorities in the list when updating our
25813 - Correctly back-off from requesting router descriptors that we are
25814 having a hard time downloading.
25815 - Read resolv.conf files correctly on platforms where read() returns
25816 partial results on small file reads.
25817 - Don't rebuild the entire router store every time we get 32K of
25818 routers: rebuild it when the journal gets very large, or when
25819 the gaps in the store get very large.
25822 - When routers publish SVN revisions in their router descriptors,
25823 authorities now include those versions correctly in networkstatus
25825 - Warn when using a version of libevent before 1.3b to run a server on
25826 OSX or BSD: these versions interact badly with userspace threads.
25829 Changes in version 0.1.2.13 - 2007-04-24
25830 This release features some major anonymity fixes, such as safer path
25831 selection; better client performance; faster bootstrapping, better
25832 address detection, and better DNS support for servers; write limiting as
25833 well as read limiting to make servers easier to run; and a huge pile of
25834 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
25836 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
25837 of the Freenode IRC network, remembering his patience and vision for
25838 free speech on the Internet.
25841 - Fix a memory leak when we ask for "all" networkstatuses and we
25842 get one we don't recognize.
25843 - Add more asserts to hunt down bug 417.
25844 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
25847 Changes in version 0.1.2.12-rc - 2007-03-16
25849 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
25850 directory information requested inside Tor connections (i.e. via
25851 begin_dir cells). It only triggered when the same connection was
25852 serving other data at the same time. Reported by seeess.
25855 - When creating a circuit via the controller, send a 'launched'
25856 event when we're done, so we follow the spec better.
25859 Changes in version 0.1.2.11-rc - 2007-03-15
25860 o Minor bugfixes (controller), reported by daejees:
25861 - Correct the control spec to match how the code actually responds
25862 to 'getinfo addr-mappings/*'.
25863 - The control spec described a GUARDS event, but the code
25864 implemented a GUARD event. Standardize on GUARD, but let people
25865 ask for GUARDS too.
25868 Changes in version 0.1.2.10-rc - 2007-03-07
25869 o Major bugfixes (Windows):
25870 - Do not load the NT services library functions (which may not exist)
25871 just to detect if we're a service trying to shut down. Now we run
25872 on Win98 and friends again.
25874 o Minor bugfixes (other):
25875 - Clarify a couple of log messages.
25876 - Fix a misleading socks5 error number.
25879 Changes in version 0.1.2.9-rc - 2007-03-02
25880 o Major bugfixes (Windows):
25881 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
25882 of the usual GCC "%llu". This prevents a bug when saving 64-bit
25883 int configuration values: the high-order 32 bits would get
25884 truncated. In particular, we were being bitten by the default
25885 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
25886 and maybe also bug 397.)
25888 o Minor bugfixes (performance):
25889 - Use OpenSSL's AES implementation on platforms where it's faster.
25890 This could save us as much as 10% CPU usage.
25892 o Minor bugfixes (server):
25893 - Do not rotate onion key immediately after setting it for the first
25896 o Minor bugfixes (directory authorities):
25897 - Stop calling servers that have been hibernating for a long time
25898 "stable". Also, stop letting hibernating or obsolete servers affect
25899 uptime and bandwidth cutoffs.
25900 - Stop listing hibernating servers in the v1 directory.
25902 o Minor bugfixes (hidden services):
25903 - Upload hidden service descriptors slightly less often, to reduce
25904 load on authorities.
25906 o Minor bugfixes (other):
25907 - Fix an assert that could trigger if a controller quickly set then
25908 cleared EntryNodes. Bug found by Udo van den Heuvel.
25909 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
25911 - Fix a potential race condition in the rpm installer. Found by
25913 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
25914 of 2 as indicating that the server is completely bad; it sometimes
25915 means that the server is just bad for the request in question. (may fix
25916 the last of bug 326.)
25917 - Disable encrypted directory connections when we don't have a server
25918 descriptor for the destination. We'll get this working again in
25922 Changes in version 0.1.2.8-beta - 2007-02-26
25923 o Major bugfixes (crashes):
25924 - Stop crashing when the controller asks us to resetconf more than
25925 one config option at once. (Vidalia 0.0.11 does this.)
25926 - Fix a crash that happened on Win98 when we're given command-line
25927 arguments: don't try to load NT service functions from advapi32.dll
25928 except when we need them. (Bug introduced in 0.1.2.7-alpha;
25930 - Fix a longstanding obscure crash bug that could occur when
25931 we run out of DNS worker processes. (Resolves bug 390.)
25933 o Major bugfixes (hidden services):
25934 - Correctly detect whether hidden service descriptor downloads are
25935 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
25937 o Major bugfixes (accounting):
25938 - When we start during an accounting interval before it's time to wake
25939 up, remember to wake up at the correct time. (May fix bug 342.)
25941 o Minor bugfixes (controller):
25942 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
25943 clear the corresponding on_circuit variable, and remember later
25944 that we don't need to send a redundant CLOSED event. Resolves part
25946 - Report events where a resolve succeeded or where we got a socks
25947 protocol error correctly, rather than calling both of them
25949 - Change reported stream target addresses to IP consistently when
25950 we finally get the IP from an exit node.
25951 - Send log messages to the controller even if they happen to be very
25954 o Minor bugfixes (other):
25955 - Display correct results when reporting which versions are
25956 recommended, and how recommended they are. (Resolves bug 383.)
25957 - Improve our estimates for directory bandwidth to be less random:
25958 guess that an unrecognized directory will have the average bandwidth
25959 from all known directories, not that it will have the average
25960 bandwidth from those directories earlier than it on the list.
25961 - If we start a server with ClientOnly 1, then set ClientOnly to 0
25962 and hup, stop triggering an assert based on an empty onion_key.
25963 - On platforms with no working mmap() equivalent, don't warn the
25964 user when cached-routers doesn't exist.
25965 - Warn the user when mmap() [or its equivalent] fails for some reason
25966 other than file-not-found.
25967 - Don't warn the user when cached-routers.new doesn't exist: that's
25968 perfectly fine when starting up for the first time.
25969 - When EntryNodes are configured, rebuild the guard list to contain,
25970 in order: the EntryNodes that were guards before; the rest of the
25971 EntryNodes; the nodes that were guards before.
25972 - Mask out all signals in sub-threads; only the libevent signal
25973 handler should be processing them. This should prevent some crashes
25974 on some machines using pthreads. (Patch from coderman.)
25975 - Fix switched arguments on memset in the implementation of
25976 tor_munmap() for systems with no mmap() call.
25977 - When Tor receives a router descriptor that it asked for, but
25978 no longer wants (because it has received fresh networkstatuses
25979 in the meantime), do not warn the user. Cache the descriptor if
25980 we're a cache; drop it if we aren't.
25981 - Make earlier entry guards _really_ get retried when the network
25983 - On a malformed DNS reply, always give an error to the corresponding
25985 - Build with recent libevents on platforms that do not define the
25986 nonstandard types "u_int8_t" and friends.
25988 o Minor features (controller):
25989 - Warn the user when an application uses the obsolete binary v0
25990 control protocol. We're planning to remove support for it during
25991 the next development series, so it's good to give people some
25993 - Add STREAM_BW events to report per-entry-stream bandwidth
25994 use. (Patch from Robert Hogan.)
25995 - Rate-limit SIGNEWNYM signals in response to controllers that
25996 impolitely generate them for every single stream. (Patch from
25997 mwenge; closes bug 394.)
25998 - Make REMAP stream events have a SOURCE (cache or exit), and
25999 make them generated in every case where we get a successful
26000 connected or resolved cell.
26002 o Minor bugfixes (performance):
26003 - Call router_have_min_dir_info half as often. (This is showing up in
26004 some profiles, but not others.)
26005 - When using GCC, make log_debug never get called at all, and its
26006 arguments never get evaluated, when no debug logs are configured.
26007 (This is showing up in some profiles, but not others.)
26010 - Remove some never-implemented options. Mark PathlenCoinWeight as
26012 - Implement proposal 106: Stop requiring clients to have well-formed
26013 certificates; stop checking nicknames in certificates. (Clients
26014 have certificates so that they can look like Tor servers, but in
26015 the future we might want to allow them to look like regular TLS
26016 clients instead. Nicknames in certificates serve no purpose other
26017 than making our protocol easier to recognize on the wire.)
26018 - Revise messages on handshake failure again to be even more clear about
26019 which are incoming connections and which are outgoing.
26020 - Discard any v1 directory info that's over 1 month old (for
26021 directories) or over 1 week old (for running-routers lists).
26022 - Do not warn when individual nodes in the configuration's EntryNodes,
26023 ExitNodes, etc are down: warn only when all possible nodes
26024 are down. (Fixes bug 348.)
26025 - Always remove expired routers and networkstatus docs before checking
26026 whether we have enough information to build circuits. (Fixes
26028 - Put a lower-bound on MaxAdvertisedBandwidth.
26031 Changes in version 0.1.2.7-alpha - 2007-02-06
26032 o Major bugfixes (rate limiting):
26033 - Servers decline directory requests much more aggressively when
26034 they're low on bandwidth. Otherwise they end up queueing more and
26035 more directory responses, which can't be good for latency.
26036 - But never refuse directory requests from local addresses.
26037 - Fix a memory leak when sending a 503 response for a networkstatus
26039 - Be willing to read or write on local connections (e.g. controller
26040 connections) even when the global rate limiting buckets are empty.
26041 - If our system clock jumps back in time, don't publish a negative
26042 uptime in the descriptor. Also, don't let the global rate limiting
26043 buckets go absurdly negative.
26044 - Flush local controller connection buffers periodically as we're
26045 writing to them, so we avoid queueing 4+ megabytes of data before
26048 o Major bugfixes (NT services):
26049 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
26050 command-line flag so that admins can override the default by saying
26051 "tor --service install --user "SomeUser"". This will not affect
26052 existing installed services. Also, warn the user that the service
26053 will look for its configuration file in the service user's
26054 %appdata% directory. (We can't do the 'hardwire the user's appdata
26055 directory' trick any more, since we may not have read access to that
26058 o Major bugfixes (other):
26059 - Previously, we would cache up to 16 old networkstatus documents
26060 indefinitely, if they came from nontrusted authorities. Now we
26061 discard them if they are more than 10 days old.
26062 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
26064 - Detect and reject malformed DNS responses containing circular
26066 - If exits are rare enough that we're not marking exits as guards,
26067 ignore exit bandwidth when we're deciding the required bandwidth
26069 - When we're handling a directory connection tunneled over Tor,
26070 don't fill up internal memory buffers with all the data we want
26071 to tunnel; instead, only add it if the OR connection that will
26072 eventually receive it has some room for it. (This can lead to
26073 slowdowns in tunneled dir connections; a better solution will have
26074 to wait for 0.2.0.)
26076 o Minor bugfixes (dns):
26077 - Add some defensive programming to eventdns.c in an attempt to catch
26078 possible memory-stomping bugs.
26079 - Detect and reject DNS replies containing IPv4 or IPv6 records with
26080 an incorrect number of bytes. (Previously, we would ignore the
26082 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
26083 in the correct order, and doesn't crash.
26084 - Free memory held in recently-completed DNS lookup attempts on exit.
26085 This was not a memory leak, but may have been hiding memory leaks.
26086 - Handle TTL values correctly on reverse DNS lookups.
26087 - Treat failure to parse resolv.conf as an error.
26089 o Minor bugfixes (other):
26090 - Fix crash with "tor --list-fingerprint" (reported by seeess).
26091 - When computing clock skew from directory HTTP headers, consider what
26092 time it was when we finished asking for the directory, not what
26094 - Expire socks connections if they spend too long waiting for the
26095 handshake to finish. Previously we would let them sit around for
26096 days, if the connecting application didn't close them either.
26097 - And if the socks handshake hasn't started, don't send a
26098 "DNS resolve socks failed" handshake reply; just close it.
26099 - Stop using C functions that OpenBSD's linker doesn't like.
26100 - Don't launch requests for descriptors unless we have networkstatuses
26101 from at least half of the authorities. This delays the first
26102 download slightly under pathological circumstances, but can prevent
26103 us from downloading a bunch of descriptors we don't need.
26104 - Do not log IPs with TLS failures for incoming TLS
26105 connections. (Fixes bug 382.)
26106 - If the user asks to use invalid exit nodes, be willing to use
26108 - Stop using the reserved ac_cv namespace in our configure script.
26109 - Call stat() slightly less often; use fstat() when possible.
26110 - Refactor the way we handle pending circuits when an OR connection
26111 completes or fails, in an attempt to fix a rare crash bug.
26112 - Only rewrite a conn's address based on X-Forwarded-For: headers
26113 if it's a parseable public IP address; and stop adding extra quotes
26114 to the resulting address.
26117 - Weight directory requests by advertised bandwidth. Now we can
26118 let servers enable write limiting but still allow most clients to
26119 succeed at their directory requests. (We still ignore weights when
26120 choosing a directory authority; I hope this is a feature.)
26123 - Create a new file ReleaseNotes which was the old ChangeLog. The
26124 new ChangeLog file now includes the summaries for all development
26126 - Check for addresses with invalid characters at the exit as well
26127 as at the client, and warn less verbosely when they fail. You can
26128 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
26129 - Adapt a patch from goodell to let the contrib/exitlist script
26130 take arguments rather than require direct editing.
26131 - Inform the server operator when we decide not to advertise a
26132 DirPort due to AccountingMax enabled or a low BandwidthRate. It
26133 was confusing Zax, so now we're hopefully more helpful.
26134 - Bring us one step closer to being able to establish an encrypted
26135 directory tunnel without knowing a descriptor first. Still not
26136 ready yet. As part of the change, now assume we can use a
26137 create_fast cell if we don't know anything about a router.
26138 - Allow exit nodes to use nameservers running on ports other than 53.
26139 - Servers now cache reverse DNS replies.
26140 - Add an --ignore-missing-torrc command-line option so that we can
26141 get the "use sensible defaults if the configuration file doesn't
26142 exist" behavior even when specifying a torrc location on the command
26145 o Minor features (controller):
26146 - Track reasons for OR connection failure; make these reasons
26147 available via the controller interface. (Patch from Mike Perry.)
26148 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
26149 can learn when clients are sending malformed hostnames to Tor.
26150 - Clean up documentation for controller status events.
26151 - Add a REMAP status to stream events to note that a stream's
26152 address has changed because of a cached address or a MapAddress
26156 Changes in version 0.1.2.6-alpha - 2007-01-09
26158 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
26159 connection handles more than 4 gigs in either direction, we crash.
26160 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
26161 advertised exit node, somebody might try to exit from us when
26162 we're bootstrapping and before we've built our descriptor yet.
26163 Refuse the connection rather than crashing.
26166 - Warn if we (as a server) find that we've resolved an address that we
26167 weren't planning to resolve.
26168 - Warn that using select() on any libevent version before 1.1 will be
26169 unnecessarily slow (even for select()).
26170 - Flush ERR-level controller status events just like we currently
26171 flush ERR-level log events, so that a Tor shutdown doesn't prevent
26172 the controller from learning about current events.
26174 o Minor features (more controller status events):
26175 - Implement EXTERNAL_ADDRESS server status event so controllers can
26176 learn when our address changes.
26177 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
26178 can learn when directories reject our descriptor.
26179 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
26180 can learn when a client application is speaking a non-socks protocol
26182 - Implement DANGEROUS_SOCKS client status event so controllers
26183 can learn when a client application is leaking DNS addresses.
26184 - Implement BUG general status event so controllers can learn when
26185 Tor is unhappy about its internal invariants.
26186 - Implement CLOCK_SKEW general status event so controllers can learn
26187 when Tor thinks the system clock is set incorrectly.
26188 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
26189 server status events so controllers can learn when their descriptors
26190 are accepted by a directory.
26191 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
26192 server status events so controllers can learn about Tor's progress in
26193 deciding whether it's reachable from the outside.
26194 - Implement BAD_LIBEVENT general status event so controllers can learn
26195 when we have a version/method combination in libevent that needs to
26197 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
26198 and DNS_USELESS server status events so controllers can learn
26199 about changes to DNS server status.
26201 o Minor features (directory):
26202 - Authorities no longer recommend exits as guards if this would shift
26203 too much load to the exit nodes.
26206 Changes in version 0.1.2.5-alpha - 2007-01-06
26208 - Enable write limiting as well as read limiting. Now we sacrifice
26209 capacity if we're pushing out lots of directory traffic, rather
26210 than overrunning the user's intended bandwidth limits.
26211 - Include TLS overhead when counting bandwidth usage; previously, we
26212 would count only the bytes sent over TLS, but not the bytes used
26214 - Support running the Tor service with a torrc not in the same
26215 directory as tor.exe and default to using the torrc located in
26216 the %appdata%\Tor\ of the user who installed the service. Patch
26218 - Servers now check for the case when common DNS requests are going to
26219 wildcarded addresses (i.e. all getting the same answer), and change
26220 their exit policy to reject *:* if it's happening.
26221 - Implement BEGIN_DIR cells, so we can connect to the directory
26222 server via TLS to do encrypted directory requests rather than
26223 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
26224 config options if you like.
26226 o Minor features (config and docs):
26227 - Start using the state file to store bandwidth accounting data:
26228 the bw_accounting file is now obsolete. We'll keep generating it
26229 for a while for people who are still using 0.1.2.4-alpha.
26230 - Try to batch changes to the state file so that we do as few
26231 disk writes as possible while still storing important things in
26233 - The state file and the bw_accounting file get saved less often when
26234 the AvoidDiskWrites config option is set.
26235 - Make PIDFile work on Windows (untested).
26236 - Add internal descriptions for a bunch of configuration options:
26237 accessible via controller interface and in comments in saved
26239 - Reject *:563 (NNTPS) in the default exit policy. We already reject
26240 NNTP by default, so this seems like a sensible addition.
26241 - Clients now reject hostnames with invalid characters. This should
26242 avoid some inadvertent info leaks. Add an option
26243 AllowNonRFC953Hostnames to disable this behavior, in case somebody
26244 is running a private network with hosts called @, !, and #.
26245 - Add a maintainer script to tell us which options are missing
26246 documentation: "make check-docs".
26247 - Add a new address-spec.txt document to describe our special-case
26248 addresses: .exit, .onion, and .noconnnect.
26250 o Minor features (DNS):
26251 - Ongoing work on eventdns infrastructure: now it has dns server
26252 and ipv6 support. One day Tor will make use of it.
26253 - Add client-side caching for reverse DNS lookups.
26254 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
26255 - When we change nameservers or IP addresses, reset and re-launch
26256 our tests for DNS hijacking.
26258 o Minor features (directory):
26259 - Authorities now specify server versions in networkstatus. This adds
26260 about 2% to the size of compressed networkstatus docs, and allows
26261 clients to tell which servers support BEGIN_DIR and which don't.
26262 The implementation is forward-compatible with a proposed future
26263 protocol version scheme not tied to Tor versions.
26264 - DirServer configuration lines now have an orport= option so
26265 clients can open encrypted tunnels to the authorities without
26266 having downloaded their descriptors yet. Enabled for moria1,
26267 moria2, tor26, and lefkada now in the default configuration.
26268 - Directory servers are more willing to send a 503 "busy" if they
26269 are near their write limit, especially for v1 directory requests.
26270 Now they can use their limited bandwidth for actual Tor traffic.
26271 - Clients track responses with status 503 from dirservers. After a
26272 dirserver has given us a 503, we try not to use it until an hour has
26273 gone by, or until we have no dirservers that haven't given us a 503.
26274 - When we get a 503 from a directory, and we're not a server, we don't
26275 count the failure against the total number of failures allowed
26276 for the thing we're trying to download.
26277 - Report X-Your-Address-Is correctly from tunneled directory
26278 connections; don't report X-Your-Address-Is when it's an internal
26279 address; and never believe reported remote addresses when they're
26281 - Protect against an unlikely DoS attack on directory servers.
26282 - Add a BadDirectory flag to network status docs so that authorities
26283 can (eventually) tell clients about caches they believe to be
26286 o Minor features (controller):
26287 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
26288 - Reimplement GETINFO so that info/names stays in sync with the
26290 - Implement "GETINFO fingerprint".
26291 - Implement "SETEVENTS GUARD" so controllers can get updates on
26292 entry guard status as it changes.
26294 o Minor features (clean up obsolete pieces):
26295 - Remove some options that have been deprecated since at least
26296 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
26297 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
26298 to set log options.
26299 - We no longer look for identity and onion keys in "identity.key" and
26300 "onion.key" -- these were replaced by secret_id_key and
26301 secret_onion_key in 0.0.8pre1.
26302 - We no longer require unrecognized directory entries to be
26305 o Major bugfixes (security):
26306 - Stop sending the HttpProxyAuthenticator string to directory
26307 servers when directory connections are tunnelled through Tor.
26308 - Clients no longer store bandwidth history in the state file.
26309 - Do not log introduction points for hidden services if SafeLogging
26311 - When generating bandwidth history, round down to the nearest
26312 1k. When storing accounting data, round up to the nearest 1k.
26313 - When we're running as a server, remember when we last rotated onion
26314 keys, so that we will rotate keys once they're a week old even if
26315 we never stay up for a week ourselves.
26317 o Major bugfixes (other):
26318 - Fix a longstanding bug in eventdns that prevented the count of
26319 timed-out resolves from ever being reset. This bug caused us to
26320 give up on a nameserver the third time it timed out, and try it
26321 10 seconds later... and to give up on it every time it timed out
26323 - Take out the '5 second' timeout from the connection retry
26324 schedule. Now the first connect attempt will wait a full 10
26325 seconds before switching to a new circuit. Perhaps this will help
26326 a lot. Based on observations from Mike Perry.
26327 - Fix a bug on the Windows implementation of tor_mmap_file() that
26328 would prevent the cached-routers file from ever loading. Reported
26332 - Fix an assert failure when a directory authority sets
26333 AuthDirRejectUnlisted and then receives a descriptor from an
26334 unlisted router. Reported by seeess.
26335 - Avoid a double-free when parsing malformed DirServer lines.
26336 - Fix a bug when a BSD-style PF socket is first used. Patch from
26338 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
26339 to resolve an address at a given exit node even when they ask for
26341 - Servers no longer ever list themselves in their "family" line,
26342 even if configured to do so. This makes it easier to configure
26343 family lists conveniently.
26344 - When running as a server, don't fall back to 127.0.0.1 when no
26345 nameservers are configured in /etc/resolv.conf; instead, make the
26346 user fix resolv.conf or specify nameservers explicitly. (Resolves
26348 - Stop accepting certain malformed ports in configured exit policies.
26349 - Don't re-write the fingerprint file every restart, unless it has
26351 - Stop warning when a single nameserver fails: only warn when _all_ of
26352 our nameservers have failed. Also, when we only have one nameserver,
26353 raise the threshold for deciding that the nameserver is dead.
26354 - Directory authorities now only decide that routers are reachable
26355 if their identity keys are as expected.
26356 - When the user uses bad syntax in the Log config line, stop
26357 suggesting other bad syntax as a replacement.
26358 - Correctly detect ipv6 DNS capability on OpenBSD.
26360 o Minor bugfixes (controller):
26361 - Report the circuit number correctly in STREAM CLOSED events. Bug
26362 reported by Mike Perry.
26363 - Do not report bizarre values for results of accounting GETINFOs
26364 when the last second's write or read exceeds the allotted bandwidth.
26365 - Report "unrecognized key" rather than an empty string when the
26366 controller tries to fetch a networkstatus that doesn't exist.
26369 Changes in version 0.1.1.26 - 2006-12-14
26370 o Security bugfixes:
26371 - Stop sending the HttpProxyAuthenticator string to directory
26372 servers when directory connections are tunnelled through Tor.
26373 - Clients no longer store bandwidth history in the state file.
26374 - Do not log introduction points for hidden services if SafeLogging
26378 - Fix an assert failure when a directory authority sets
26379 AuthDirRejectUnlisted and then receives a descriptor from an
26380 unlisted router (reported by seeess).
26383 Changes in version 0.1.2.4-alpha - 2006-12-03
26385 - Add support for using natd; this allows FreeBSDs earlier than
26386 5.1.2 to have ipfw send connections through Tor without using
26387 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
26390 - Make all connections to addresses of the form ".noconnect"
26391 immediately get closed. This lets application/controller combos
26392 successfully test whether they're talking to the same Tor by
26393 watching for STREAM events.
26394 - Make cross.sh cross-compilation script work even when autogen.sh
26395 hasn't been run. (Patch from Michael Mohr.)
26396 - Statistics dumped by -USR2 now include a breakdown of public key
26397 operations, for profiling.
26400 - Fix a major leak when directory authorities parse their
26401 approved-routers list, a minor memory leak when we fail to pick
26402 an exit node, and a few rare leaks on errors.
26403 - Handle TransPort connections even when the server sends data before
26404 the client sends data. Previously, the connection would just hang
26405 until the client sent data. (Patch from tup based on patch from
26407 - Avoid assert failure when our cached-routers file is empty on
26411 - Don't log spurious warnings when we see a circuit close reason we
26412 don't recognize; it's probably just from a newer version of Tor.
26413 - Have directory authorities allow larger amounts of drift in uptime
26414 without replacing the server descriptor: previously, a server that
26415 restarted every 30 minutes could have 48 "interesting" descriptors
26417 - Start linking to the Tor specification and Tor reference manual
26418 correctly in the Windows installer.
26419 - Add Vidalia to the OS X uninstaller script, so when we uninstall
26420 Tor/Privoxy we also uninstall Vidalia.
26421 - Resume building on Irix64, and fix a lot of warnings from its
26422 MIPSpro C compiler.
26423 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
26424 when we're running as a client.
26427 Changes in version 0.1.1.25 - 2006-11-04
26429 - When a client asks us to resolve (rather than connect to)
26430 an address, and we have a cached answer, give them the cached
26431 answer. Previously, we would give them no answer at all.
26432 - We were building exactly the wrong circuits when we predict
26433 hidden service requirements, meaning Tor would have to build all
26434 its circuits on demand.
26435 - If none of our live entry guards have a high uptime, but we
26436 require a guard with a high uptime, try adding a new guard before
26437 we give up on the requirement. This patch should make long-lived
26438 connections more stable on average.
26439 - When testing reachability of our DirPort, don't launch new
26440 tests when there's already one in progress -- unreachable
26441 servers were stacking up dozens of testing streams.
26443 o Security bugfixes:
26444 - When the user sends a NEWNYM signal, clear the client-side DNS
26445 cache too. Otherwise we continue to act on previous information.
26448 - Avoid a memory corruption bug when creating a hash table for
26450 - Avoid possibility of controller-triggered crash when misusing
26451 certain commands from a v0 controller on platforms that do not
26452 handle printf("%s",NULL) gracefully.
26453 - Avoid infinite loop on unexpected controller input.
26454 - Don't log spurious warnings when we see a circuit close reason we
26455 don't recognize; it's probably just from a newer version of Tor.
26456 - Add Vidalia to the OS X uninstaller script, so when we uninstall
26457 Tor/Privoxy we also uninstall Vidalia.
26460 Changes in version 0.1.2.3-alpha - 2006-10-29
26462 - Prepare for servers to publish descriptors less often: never
26463 discard a descriptor simply for being too old until either it is
26464 recommended by no authorities, or until we get a better one for
26465 the same router. Make caches consider retaining old recommended
26466 routers for even longer.
26467 - If most authorities set a BadExit flag for a server, clients
26468 don't think of it as a general-purpose exit. Clients only consider
26469 authorities that advertise themselves as listing bad exits.
26470 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
26471 headers for content, so that we can work better in the presence of
26472 caching HTTP proxies.
26473 - Allow authorities to list nodes as bad exits by fingerprint or by
26476 o Minor features, controller:
26477 - Add a REASON field to CIRC events; for backward compatibility, this
26478 field is sent only to controllers that have enabled the extended
26479 event format. Also, add additional reason codes to explain why
26480 a given circuit has been destroyed or truncated. (Patches from
26482 - Add a REMOTE_REASON field to extended CIRC events to tell the
26483 controller about why a remote OR told us to close a circuit.
26484 - Stream events also now have REASON and REMOTE_REASON fields,
26485 working much like those for circuit events.
26486 - There's now a GETINFO ns/... field so that controllers can ask Tor
26487 about the current status of a router.
26488 - A new event type "NS" to inform a controller when our opinion of
26489 a router's status has changed.
26490 - Add a GETINFO events/names and GETINFO features/names so controllers
26491 can tell which events and features are supported.
26492 - A new CLEARDNSCACHE signal to allow controllers to clear the
26493 client-side DNS cache without expiring circuits.
26495 o Security bugfixes:
26496 - When the user sends a NEWNYM signal, clear the client-side DNS
26497 cache too. Otherwise we continue to act on previous information.
26500 - Avoid sending junk to controllers or segfaulting when a controller
26501 uses EVENT_NEW_DESC with verbose nicknames.
26502 - Stop triggering asserts if the controller tries to extend hidden
26503 service circuits (reported by mwenge).
26504 - Avoid infinite loop on unexpected controller input.
26505 - When the controller does a "GETINFO network-status", tell it
26506 about even those routers whose descriptors are very old, and use
26507 long nicknames where appropriate.
26508 - Change NT service functions to be loaded on demand. This lets us
26509 build with MinGW without breaking Tor for Windows 98 users.
26510 - Do DirPort reachability tests less often, since a single test
26511 chews through many circuits before giving up.
26512 - In the hidden service example in torrc.sample, stop recommending
26513 esoteric and discouraged hidden service options.
26514 - When stopping an NT service, wait up to 10 sec for it to actually
26515 stop. Patch from Matt Edman; resolves bug 295.
26516 - Fix handling of verbose nicknames with ORCONN controller events:
26517 make them show up exactly when requested, rather than exactly when
26519 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
26520 printing a duplicate "$" in the keys we send (reported by mwenge).
26521 - Correctly set maximum connection limit on Cygwin. (This time
26523 - Try to detect Windows correctly when cross-compiling.
26524 - Detect the size of the routers file correctly even if it is
26525 corrupted (on systems without mmap) or not page-aligned (on systems
26526 with mmap). This bug was harmless.
26527 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
26528 to open a stream fails; now we do in more cases. This should
26529 make clients able to find a good exit faster in some cases, since
26530 unhandleable requests will now get an error rather than timing out.
26531 - Resolve two memory leaks when rebuilding the on-disk router cache
26532 (reported by fookoowa).
26533 - Clean up minor code warnings suggested by the MIPSpro C compiler,
26534 and reported by some Centos users.
26535 - Controller signals now work on non-Unix platforms that don't define
26536 SIGUSR1 and SIGUSR2 the way we expect.
26537 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
26538 values before failing, and always enables eventdns.
26539 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
26540 Try to fix this in configure.in by checking for most functions
26541 before we check for libevent.
26544 Changes in version 0.1.2.2-alpha - 2006-10-07
26546 - Make our async eventdns library on-by-default for Tor servers,
26547 and plan to deprecate the separate dnsworker threads.
26548 - Add server-side support for "reverse" DNS lookups (using PTR
26549 records so clients can determine the canonical hostname for a given
26550 IPv4 address). Only supported by servers using eventdns; servers
26551 now announce in their descriptors whether they support eventdns.
26552 - Specify and implement client-side SOCKS5 interface for reverse DNS
26553 lookups (see doc/socks-extensions.txt).
26554 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
26555 connect to directory servers through Tor. Previously, clients needed
26556 to find Tor exits to make private connections to directory servers.
26557 - Avoid choosing Exit nodes for entry or middle hops when the
26558 total bandwidth available from non-Exit nodes is much higher than
26559 the total bandwidth available from Exit nodes.
26560 - Workaround for name servers (like Earthlink's) that hijack failing
26561 DNS requests and replace the no-such-server answer with a "helpful"
26562 redirect to an advertising-driven search portal. Also work around
26563 DNS hijackers who "helpfully" decline to hijack known-invalid
26564 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
26565 lets you turn it off.
26566 - Send out a burst of long-range padding cells once we've established
26567 that we're reachable. Spread them over 4 circuits, so hopefully
26568 a few will be fast. This exercises our bandwidth and bootstraps
26569 us into the directory more quickly.
26571 o New/improved config options:
26572 - Add new config option "ResolvConf" to let the server operator
26573 choose an alternate resolve.conf file when using eventdns.
26574 - Add an "EnforceDistinctSubnets" option to control our "exclude
26575 servers on the same /16" behavior. It's still on by default; this
26576 is mostly for people who want to operate private test networks with
26577 all the machines on the same subnet.
26578 - If one of our entry guards is on the ExcludeNodes list, or the
26579 directory authorities don't think it's a good guard, treat it as
26580 if it were unlisted: stop using it as a guard, and throw it off
26581 the guards list if it stays that way for a long time.
26582 - Allow directory authorities to be marked separately as authorities
26583 for the v1 directory protocol, the v2 directory protocol, and
26584 as hidden service directories, to make it easier to retire old
26585 authorities. V1 authorities should set "HSAuthoritativeDir 1"
26586 to continue being hidden service authorities too.
26587 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
26589 o Minor features, controller:
26590 - Fix CIRC controller events so that controllers can learn the
26591 identity digests of non-Named servers used in circuit paths.
26592 - Let controllers ask for more useful identifiers for servers. Instead
26593 of learning identity digests for un-Named servers and nicknames
26594 for Named servers, the new identifiers include digest, nickname,
26595 and indication of Named status. Off by default; see control-spec.txt
26596 for more information.
26597 - Add a "getinfo address" controller command so it can display Tor's
26598 best guess to the user.
26599 - New controller event to alert the controller when our server
26600 descriptor has changed.
26601 - Give more meaningful errors on controller authentication failure.
26603 o Minor features, other:
26604 - When asked to resolve a hostname, don't use non-exit servers unless
26605 requested to do so. This allows servers with broken DNS to be
26606 useful to the network.
26607 - Divide eventdns log messages into warn and info messages.
26608 - Reserve the nickname "Unnamed" for routers that can't pick
26609 a hostname: any router can call itself Unnamed; directory
26610 authorities will never allocate Unnamed to any particular router;
26611 clients won't believe that any router is the canonical Unnamed.
26612 - Only include function names in log messages for info/debug messages.
26613 For notice/warn/err, the content of the message should be clear on
26614 its own, and printing the function name only confuses users.
26615 - Avoid some false positives during reachability testing: don't try
26616 to test via a server that's on the same /24 as us.
26617 - If we fail to build a circuit to an intended enclave, and it's
26618 not mandatory that we use that enclave, stop wanting it.
26619 - When eventdns is enabled, allow multithreaded builds on NetBSD and
26620 OpenBSD. (We had previously disabled threads on these platforms
26621 because they didn't have working thread-safe resolver functions.)
26623 o Major bugfixes, anonymity/security:
26624 - If a client asked for a server by name, and there's a named server
26625 in our network-status but we don't have its descriptor yet, we
26626 could return an unnamed server instead.
26627 - Fix NetBSD bug that could allow someone to force uninitialized RAM
26628 to be sent to a server's DNS resolver. This only affects NetBSD
26629 and other platforms that do not bounds-check tolower().
26630 - Reject (most) attempts to use Tor circuits with length one. (If
26631 many people start using Tor as a one-hop proxy, exit nodes become
26632 a more attractive target for compromise.)
26633 - Just because your DirPort is open doesn't mean people should be
26634 able to remotely teach you about hidden service descriptors. Now
26635 only accept rendezvous posts if you've got HSAuthoritativeDir set.
26637 o Major bugfixes, other:
26638 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
26639 - When a client asks the server to resolve (not connect to)
26640 an address, and it has a cached answer, give them the cached answer.
26641 Previously, the server would give them no answer at all.
26642 - Allow really slow clients to not hang up five minutes into their
26643 directory downloads (suggested by Adam J. Richter).
26644 - We were building exactly the wrong circuits when we anticipated
26645 hidden service requirements, meaning Tor would have to build all
26646 its circuits on demand.
26647 - Avoid crashing when we mmap a router cache file of size 0.
26648 - When testing reachability of our DirPort, don't launch new
26649 tests when there's already one in progress -- unreachable
26650 servers were stacking up dozens of testing streams.
26652 o Minor bugfixes, correctness:
26653 - If we're a directory mirror and we ask for "all" network status
26654 documents, we would discard status documents from authorities
26655 we don't recognize.
26656 - Avoid a memory corruption bug when creating a hash table for
26658 - Avoid controller-triggered crash when misusing certain commands
26659 from a v0 controller on platforms that do not handle
26660 printf("%s",NULL) gracefully.
26661 - Don't crash when a controller sends a third argument to an
26662 "extendcircuit" request.
26663 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
26664 response; fix error code when "getinfo dir/status/" fails.
26665 - Avoid crash when telling controller stream-status and a stream
26667 - Patch from Adam Langley to fix assert() in eventdns.c.
26668 - Fix a debug log message in eventdns to say "X resolved to Y"
26669 instead of "X resolved to X".
26670 - Make eventdns give strings for DNS errors, not just error numbers.
26671 - Track unreachable entry guards correctly: don't conflate
26672 'unreachable by us right now' with 'listed as down by the directory
26673 authorities'. With the old code, if a guard was unreachable by
26674 us but listed as running, it would clog our guard list forever.
26675 - Behave correctly in case we ever have a network with more than
26676 2GB/s total advertised capacity.
26677 - Make TrackExitHosts case-insensitive, and fix the behavior of
26678 ".suffix" TrackExitHosts items to avoid matching in the middle of
26680 - Finally fix the openssl warnings from newer gccs that believe that
26681 ignoring a return value is okay, but casting a return value and
26682 then ignoring it is a sign of madness.
26683 - Prevent the contrib/exitlist script from printing the same
26684 result more than once.
26685 - Patch from Steve Hildrey: Generate network status correctly on
26686 non-versioning dirservers.
26687 - Don't listen to the X-Your-Address-Is hint if you did the lookup
26688 via Tor; otherwise you'll think you're the exit node's IP address.
26690 o Minor bugfixes, performance:
26691 - Two small performance improvements on parsing descriptors.
26692 - Major performance improvement on inserting descriptors: change
26693 algorithm from O(n^2) to O(n).
26694 - Make the common memory allocation path faster on machines where
26695 malloc(0) returns a pointer.
26696 - Start remembering X-Your-Address-Is directory hints even if you're
26697 a client, so you can become a server more smoothly.
26698 - Avoid duplicate entries on MyFamily line in server descriptor.
26700 o Packaging, features:
26701 - Remove architecture from OS X builds. The official builds are
26702 now universal binaries.
26703 - The Debian package now uses --verify-config when (re)starting,
26704 to distinguish configuration errors from other errors.
26705 - Update RPMs to require libevent 1.1b.
26707 o Packaging, bugfixes:
26708 - Patches so Tor builds with MinGW on Windows.
26709 - Patches so Tor might run on Cygwin again.
26710 - Resume building on non-gcc compilers and ancient gcc. Resume
26711 building with the -O0 compile flag. Resume building cleanly on
26713 - Run correctly on OS X platforms with case-sensitive filesystems.
26714 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
26715 - Add autoconf checks so Tor can build on Solaris x86 again.
26718 - Documented (and renamed) ServerDNSSearchDomains and
26719 ServerDNSResolvConfFile options.
26720 - Be clearer that the *ListenAddress directives can be repeated
26724 Changes in version 0.1.1.24 - 2006-09-29
26726 - Allow really slow clients to not hang up five minutes into their
26727 directory downloads (suggested by Adam J. Richter).
26728 - Fix major performance regression from 0.1.0.x: instead of checking
26729 whether we have enough directory information every time we want to
26730 do something, only check when the directory information has changed.
26731 This should improve client CPU usage by 25-50%.
26732 - Don't crash if, after a server has been running for a while,
26733 it can't resolve its hostname.
26736 - Allow Tor to start when RunAsDaemon is set but no logs are set.
26737 - Don't crash when the controller receives a third argument to an
26738 "extendcircuit" request.
26739 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
26740 response; fix error code when "getinfo dir/status/" fails.
26741 - Fix configure.in to not produce broken configure files with
26742 more recent versions of autoconf. Thanks to Clint for his auto*
26744 - Fix security bug on NetBSD that could allow someone to force
26745 uninitialized RAM to be sent to a server's DNS resolver. This
26746 only affects NetBSD and other platforms that do not bounds-check
26748 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
26749 methods: these are known to be buggy.
26750 - If we're a directory mirror and we ask for "all" network status
26751 documents, we would discard status documents from authorities
26752 we don't recognize.
26755 Changes in version 0.1.2.1-alpha - 2006-08-27
26757 - Add "eventdns" async dns library from Adam Langley, tweaked to
26758 build on OSX and Windows. Only enabled if you pass the
26759 --enable-eventdns argument to configure.
26760 - Allow servers with no hostname or IP address to learn their
26761 IP address by asking the directory authorities. This code only
26762 kicks in when you would normally have exited with a "no address"
26763 error. Nothing's authenticated, so use with care.
26764 - Rather than waiting a fixed amount of time between retrying
26765 application connections, we wait only 5 seconds for the first,
26766 10 seconds for the second, and 15 seconds for each retry after
26767 that. Hopefully this will improve the expected user experience.
26768 - Patch from Tup to add support for transparent AP connections:
26769 this basically bundles the functionality of trans-proxy-tor
26770 into the Tor mainline. Now hosts with compliant pf/netfilter
26771 implementations can redirect TCP connections straight to Tor
26772 without diverting through SOCKS. Needs docs.
26773 - Busy directory servers save lots of memory by spooling server
26774 descriptors, v1 directories, and v2 networkstatus docs to buffers
26775 as needed rather than en masse. Also mmap the cached-routers
26776 files, so we don't need to keep the whole thing in memory too.
26777 - Automatically avoid picking more than one node from the same
26778 /16 network when constructing a circuit.
26779 - Revise and clean up the torrc.sample that we ship with; add
26780 a section for BandwidthRate and BandwidthBurst.
26783 - Split circuit_t into origin_circuit_t and or_circuit_t, and
26784 split connection_t into edge, or, dir, control, and base structs.
26785 These will save quite a bit of memory on busy servers, and they'll
26786 also help us track down bugs in the code and bugs in the spec.
26787 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
26788 or later. Log when we are doing this, so we can diagnose it when
26789 it fails. (Also, recommend libevent 1.1b for kqueue and
26790 win32 methods; deprecate libevent 1.0b harder; make libevent
26791 recommendation system saner.)
26792 - Start being able to build universal binaries on OS X (thanks
26794 - Export the default exit policy via the control port, so controllers
26795 don't need to guess what it is / will be later.
26796 - Add a man page entry for ProtocolWarnings.
26797 - Add TestVia config option to the man page.
26798 - Remove even more protocol-related warnings from Tor server logs,
26799 such as bad TLS handshakes and malformed begin cells.
26800 - Stop fetching descriptors if you're not a dir mirror and you
26801 haven't tried to establish any circuits lately. [This currently
26802 causes some dangerous behavior, because when you start up again
26803 you'll use your ancient server descriptors.]
26804 - New DirPort behavior: if you have your dirport set, you download
26805 descriptors aggressively like a directory mirror, whether or not
26806 your ORPort is set.
26807 - Get rid of the router_retry_connections notion. Now routers
26808 no longer try to rebuild long-term connections to directory
26809 authorities, and directory authorities no longer try to rebuild
26810 long-term connections to all servers. We still don't hang up
26811 connections in these two cases though -- we need to look at it
26812 more carefully to avoid flapping, and we likely need to wait til
26813 0.1.1.x is obsolete.
26814 - Drop compatibility with obsolete Tors that permit create cells
26815 to have the wrong circ_id_type.
26816 - Re-enable per-connection rate limiting. Get rid of the "OP
26817 bandwidth" concept. Lay groundwork for "bandwidth classes" --
26818 separate global buckets that apply depending on what sort of conn
26820 - Start publishing one minute or so after we find our ORPort
26821 to be reachable. This will help reduce the number of descriptors
26822 we have for ourselves floating around, since it's quite likely
26823 other things (e.g. DirPort) will change during that minute too.
26824 - Fork the v1 directory protocol into its own spec document,
26825 and mark dir-spec.txt as the currently correct (v2) spec.
26828 - When we find our DirPort to be reachable, publish a new descriptor
26829 so we'll tell the world (reported by pnx).
26830 - Publish a new descriptor after we hup/reload. This is important
26831 if our config has changed such that we'll want to start advertising
26832 our DirPort now, etc.
26833 - Allow Tor to start when RunAsDaemon is set but no logs are set.
26834 - When we have a state file we cannot parse, tell the user and
26835 move it aside. Now we avoid situations where the user starts
26836 Tor in 1904, Tor writes a state file with that timestamp in it,
26837 the user fixes her clock, and Tor refuses to start.
26838 - Fix configure.in to not produce broken configure files with
26839 more recent versions of autoconf. Thanks to Clint for his auto*
26841 - "tor --verify-config" now exits with -1(255) or 0 depending on
26842 whether the config options are bad or good.
26843 - Resolve bug 321 when using dnsworkers: append a period to every
26844 address we resolve at the exit node, so that we do not accidentally
26845 pick up local addresses, and so that failing searches are retried
26846 in the resolver search domains. (This is already solved for
26847 eventdns.) (This breaks Blossom servers for now.)
26848 - If we are using an exit enclave and we can't connect, e.g. because
26849 its webserver is misconfigured to not listen on localhost, then
26850 back off and try connecting from somewhere else before we fail.
26853 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
26854 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
26855 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
26856 when the IP address is mapped through MapAddress to a hostname.
26857 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
26858 useless IPv6 DNS resolves.
26859 - Patch suggested by Karsten Loesing: respond to SIGNAL command
26860 before we execute the signal, in case the signal shuts us down.
26861 - Clean up AllowInvalidNodes man page entry.
26862 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
26863 - Add more asserts to track down an assert error on a windows Tor
26864 server with connection_add being called with socket == -1.
26865 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
26866 - Fix misleading log messages: an entry guard that is "unlisted",
26867 as well as not known to be "down" (because we've never heard
26868 of it), is not therefore "up".
26869 - Remove code to special-case "-cvs" ending, since it has not
26870 actually mattered since 0.0.9.
26871 - Make our socks5 handling more robust to broken socks clients:
26872 throw out everything waiting on the buffer in between socks
26873 handshake phases, since they can't possibly (so the theory
26874 goes) have predicted what we plan to respond to them.
26877 Changes in version 0.1.1.23 - 2006-07-30
26879 - Fast Tor servers, especially exit nodes, were triggering asserts
26880 due to a bug in handling the list of pending DNS resolves. Some
26881 bugs still remain here; we're hunting them.
26882 - Entry guards could crash clients by sending unexpected input.
26883 - More fixes on reachability testing: if you find yourself reachable,
26884 then don't ever make any client requests (so you stop predicting
26885 circuits), then hup or have your clock jump, then later your IP
26886 changes, you won't think circuits are working, so you won't try to
26887 test reachability, so you won't publish.
26890 - Avoid a crash if the controller does a resetconf firewallports
26891 and then a setconf fascistfirewall=1.
26892 - Avoid an integer underflow when the dir authority decides whether
26893 a router is stable: we might wrongly label it stable, and compute
26894 a slightly wrong median stability, when a descriptor is published
26896 - Fix a place where we might trigger an assert if we can't build our
26897 own server descriptor yet.
26900 Changes in version 0.1.1.22 - 2006-07-05
26902 - Fix a big bug that was causing servers to not find themselves
26903 reachable if they changed IP addresses. Since only 0.1.1.22+
26904 servers can do reachability testing correctly, now we automatically
26905 make sure to test via one of these.
26906 - Fix to allow clients and mirrors to learn directory info from
26907 descriptor downloads that get cut off partway through.
26908 - Directory authorities had a bug in deciding if a newly published
26909 descriptor was novel enough to make everybody want a copy -- a few
26910 servers seem to be publishing new descriptors many times a minute.
26912 - Fix a rare bug that was causing some servers to complain about
26913 "closing wedged cpuworkers" and skip some circuit create requests.
26914 - Make the Exit flag in directory status documents actually work.
26917 Changes in version 0.1.1.21 - 2006-06-10
26918 o Crash and assert fixes from 0.1.1.20:
26919 - Fix a rare crash on Tor servers that have enabled hibernation.
26920 - Fix a seg fault on startup for Tor networks that use only one
26921 directory authority.
26922 - Fix an assert from a race condition that occurs on Tor servers
26923 while exiting, where various threads are trying to log that they're
26924 exiting, and delete the logs, at the same time.
26925 - Make our unit tests pass again on certain obscure platforms.
26928 - Add support for building SUSE RPM packages.
26929 - Speed up initial bootstrapping for clients: if we are making our
26930 first ever connection to any entry guard, then don't mark it down
26932 - When only one Tor server in the network is labelled as a guard,
26933 and we've already picked him, we would cycle endlessly picking him
26934 again, being unhappy about it, etc. Now we specifically exclude
26935 current guards when picking a new guard.
26936 - Servers send create cells more reliably after the TLS connection
26937 is established: we were sometimes forgetting to send half of them
26938 when we had more than one pending.
26939 - If we get a create cell that asks us to extend somewhere, but the
26940 Tor server there doesn't match the expected digest, we now send
26941 a destroy cell back, rather than silently doing nothing.
26942 - Make options->RedirectExit work again.
26943 - Make cookie authentication for the controller work again.
26944 - Stop being picky about unusual characters in the arguments to
26945 mapaddress. It's none of our business.
26946 - Add a new config option "TestVia" that lets you specify preferred
26947 middle hops to use for test circuits. Perhaps this will let me
26948 debug the reachability problems better.
26950 o Log / documentation fixes:
26951 - If we're a server and some peer has a broken TLS certificate, don't
26952 log about it unless ProtocolWarnings is set, i.e., we want to hear
26953 about protocol violations by others.
26954 - Fix spelling of VirtualAddrNetwork in man page.
26955 - Add a better explanation at the top of the autogenerated torrc file
26956 about what happened to our old torrc.
26959 Changes in version 0.1.1.20 - 2006-05-23
26961 - Downgrade a log severity where servers complain that they're
26963 - Avoid a compile warning on FreeBSD.
26964 - Remove string size limit on NEWDESC messages; solve bug 291.
26965 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
26966 more thoroughly when we're running on windows.
26969 Changes in version 0.1.1.19-rc - 2006-05-03
26971 - Regenerate our local descriptor if it's dirty and we try to use
26972 it locally (e.g. if it changes during reachability detection).
26973 - If we setconf our ORPort to 0, we continued to listen on the
26974 old ORPort and receive connections.
26975 - Avoid a second warning about machine/limits.h on Debian
26977 - Be willing to add our own routerinfo into the routerlist.
26978 Now authorities will include themselves in their directories
26979 and network-statuses.
26980 - Stop trying to upload rendezvous descriptors to every
26981 directory authority: only try the v1 authorities.
26982 - Servers no longer complain when they think they're not
26983 registered with the directory authorities. There were too many
26985 - Backport dist-rpm changes so rpms can be built without errors.
26988 - Implement an option, VirtualAddrMask, to set which addresses
26989 get handed out in response to mapaddress requests. This works
26990 around a bug in tsocks where 127.0.0.0/8 is never socksified.
26993 Changes in version 0.1.1.18-rc - 2006-04-10
26995 - Work harder to download live network-statuses from all the
26996 directory authorities we know about. Improve the threshold
26997 decision logic so we're more robust to edge cases.
26998 - When fetching rendezvous descriptors, we were willing to ask
26999 v2 authorities too, which would always return 404.
27002 - Stop listing down or invalid nodes in the v1 directory. This will
27003 reduce its bulk by about 1/3, and reduce load on directory
27005 - When deciding whether a router is Fast or Guard-worthy, consider
27006 his advertised BandwidthRate and not just the BandwidthCapacity.
27007 - No longer ship INSTALL and README files -- they are useless now.
27008 - Force rpmbuild to behave and honor target_cpu.
27009 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
27010 - Start to include translated versions of the tor-doc-*.html
27011 files, along with the screenshots. Still needs more work.
27012 - Start sending back 512 and 451 errors if mapaddress fails,
27013 rather than not sending anything back at all.
27014 - When we fail to bind or listen on an incoming or outgoing
27015 socket, we should close it before failing. otherwise we just
27016 leak it. (thanks to weasel for finding.)
27017 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
27018 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
27019 - Make NoPublish (even though deprecated) work again.
27020 - Fix a minor security flaw where a versioning auth dirserver
27021 could list a recommended version many times in a row to make
27022 clients more convinced that it's recommended.
27023 - Fix crash bug if there are two unregistered servers running
27024 with the same nickname, one of them is down, and you ask for
27025 them by nickname in your EntryNodes or ExitNodes. Also, try
27026 to pick the one that's running rather than an arbitrary one.
27027 - Fix an infinite loop we could hit if we go offline for too long.
27028 - Complain when we hit WSAENOBUFS on recv() or write() too.
27029 Perhaps this will help us hunt the bug.
27030 - If you're not a versioning dirserver, don't put the string
27031 "client-versions \nserver-versions \n" in your network-status.
27032 - Lower the minimum required number of file descriptors to 1000,
27033 so we can have some overhead for Valgrind on Linux, where the
27034 default ulimit -n is 1024.
27037 - Add tor.dizum.com as the fifth authoritative directory server.
27038 - Add a new config option FetchUselessDescriptors, off by default,
27039 for when you plan to run "exitlist" on your client and you want
27040 to know about even the non-running descriptors.
27043 Changes in version 0.1.1.17-rc - 2006-03-28
27045 - Clients and servers since 0.1.1.10-alpha have been expiring
27046 connections whenever they are idle for 5 minutes and they *do*
27047 have circuits on them. Oops. With this new version, clients will
27048 discard their previous entry guard choices and avoid choosing
27049 entry guards running these flawed versions.
27050 - Fix memory leak when uncompressing concatenated zlib streams. This
27051 was causing substantial leaks over time on Tor servers.
27052 - The v1 directory was including servers as much as 48 hours old,
27053 because that's how the new routerlist->routers works. Now only
27054 include them if they're 20 hours old or less.
27057 - Resume building on irix64, netbsd 2.0, etc.
27058 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
27060 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
27061 and it is confusing some users.
27062 - Mirrors stop caching the v1 directory so often.
27063 - Make the max number of old descriptors that a cache will hold
27064 rise with the number of directory authorities, so we can scale.
27065 - Change our win32 uname() hack to be more forgiving about what
27066 win32 versions it thinks it's found.
27069 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
27071 - When the controller's *setconf commands fail, collect an error
27072 message in a string and hand it back to the controller.
27073 - Make the v2 dir's "Fast" flag based on relative capacity, just
27074 like "Stable" is based on median uptime. Name everything in the
27075 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
27076 - Log server fingerprint on startup, so new server operators don't
27077 have to go hunting around their filesystem for it.
27078 - Return a robots.txt on our dirport to discourage google indexing.
27079 - Let the controller ask for GETINFO dir/status/foo so it can ask
27080 directly rather than connecting to the dir port. Only works when
27081 dirport is set for now.
27083 o New config options rather than constants in the code:
27084 - SocksTimeout: How long do we let a socks connection wait
27085 unattached before we fail it?
27086 - CircuitBuildTimeout: Cull non-open circuits that were born
27087 at least this many seconds ago.
27088 - CircuitIdleTimeout: Cull open clean circuits that were born
27089 at least this many seconds ago.
27092 Changes in version 0.1.1.16-rc - 2006-03-18
27093 o Bugfixes on 0.1.1.15-rc:
27094 - Fix assert when the controller asks to attachstream a connect-wait
27095 or resolve-wait stream.
27096 - Now do address rewriting when the controller asks us to attach
27097 to a particular circuit too. This will let Blossom specify
27098 "moria2.exit" without having to learn what moria2's IP address is.
27099 - Make the "tor --verify-config" command-line work again, so people
27100 can automatically check if their torrc will parse.
27101 - Authoritative dirservers no longer require an open connection from
27102 a server to consider him "reachable". We need this change because
27103 when we add new auth dirservers, old servers won't know not to
27105 - Let Tor build on Sun CC again.
27106 - Fix an off-by-one buffer size in dirserv.c that magically never
27107 hit our three authorities but broke sjmurdoch's own tor network.
27108 - If we as a directory mirror don't know of any v1 directory
27109 authorities, then don't try to cache any v1 directories.
27110 - Stop warning about unknown servers in our family when they are
27111 given as hex digests.
27112 - Stop complaining as quickly to the server operator that he
27113 hasn't registered his nickname/key binding.
27114 - Various cleanups so we can add new V2 Auth Dirservers.
27115 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
27116 reflect the updated flags in our v2 dir protocol.
27117 - Resume allowing non-printable characters for exit streams (both
27118 for connecting and for resolving). Now we tolerate applications
27119 that don't follow the RFCs. But continue to block malformed names
27122 o Bugfixes on 0.1.0.x:
27123 - Fix assert bug in close_logs(): when we close and delete logs,
27124 remove them all from the global "logfiles" list.
27125 - Fix minor integer overflow in calculating when we expect to use up
27126 our bandwidth allocation before hibernating.
27127 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
27128 there are multiple SSLs installed with different versions.
27129 - When we try to be a server and Address is not explicitly set and
27130 our hostname resolves to a private IP address, try to use an
27131 interface address if it has a public address. Now Windows machines
27132 that think of themselves as localhost can work by default.
27135 - Let the controller ask for GETINFO dir/server/foo so it can ask
27136 directly rather than connecting to the dir port.
27137 - Let the controller tell us about certain router descriptors
27138 that it doesn't want Tor to use in circuits. Implement
27139 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
27140 - New config option SafeSocks to reject all application connections
27141 using unsafe socks protocols. Defaults to off.
27144 Changes in version 0.1.1.15-rc - 2006-03-11
27145 o Bugfixes and cleanups:
27146 - When we're printing strings from the network, don't try to print
27147 non-printable characters. This protects us against shell escape
27148 sequence exploits, and also against attacks to fool humans into
27149 misreading their logs.
27150 - Fix a bug where Tor would fail to establish any connections if you
27151 left it off for 24 hours and then started it: we were happy with
27152 the obsolete network statuses, but they all referred to router
27153 descriptors that were too old to fetch, so we ended up with no
27154 valid router descriptors.
27155 - Fix a seg fault in the controller's "getinfo orconn-status"
27156 command while listing status on incoming handshaking connections.
27157 Introduce a status name "NEW" for these connections.
27158 - If we get a linelist or linelist_s config option from the torrc
27159 (e.g. ExitPolicy) and it has no value, warn and skip rather than
27160 silently resetting it to its default.
27161 - Don't abandon entry guards until they've been down or gone for
27163 - Cleaner and quieter log messages.
27166 - New controller signal NEWNYM that makes new application requests
27167 use clean circuits.
27168 - Add a new circuit purpose 'controller' to let the controller ask
27169 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
27170 controller command to let you specify the purpose if you're
27171 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
27172 command to let you change a circuit's purpose after it's been
27174 - Accept "private:*" in routerdesc exit policies; not generated yet
27175 because older Tors do not understand it.
27176 - Add BSD-style contributed startup script "rc.subr" from Peter
27180 Changes in version 0.1.1.14-alpha - 2006-02-20
27181 o Bugfixes on 0.1.1.x:
27182 - Don't die if we ask for a stdout or stderr log (even implicitly)
27183 and we're set to RunAsDaemon -- just warn.
27184 - We still had a few bugs in the OR connection rotation code that
27185 caused directory servers to slowly aggregate connections to other
27186 fast Tor servers. This time for sure!
27187 - Make log entries on Win32 include the name of the function again.
27188 - We were treating a pair of exit policies if they were equal even
27189 if one said accept and the other said reject -- causing us to
27190 not always publish a new descriptor since we thought nothing
27192 - Retry pending server downloads as well as pending networkstatus
27193 downloads when we unexpectedly get a socks request.
27194 - We were ignoring the IS_FAST flag in the directory status,
27195 meaning we were willing to pick trivial-bandwidth nodes for "fast"
27197 - If the controller's SAVECONF command fails (e.g. due to file
27198 permissions), let the controller know that it failed.
27201 - If we're trying to be a Tor server and running Windows 95/98/ME
27202 as a server, explain that we'll likely crash.
27203 - When we're a server, a client asks for an old-style directory,
27204 and our write bucket is empty, don't give it to him. This way
27205 small servers can continue to serve the directory *sometimes*,
27206 without getting overloaded.
27207 - Compress exit policies even more -- look for duplicate lines
27209 - Clients now honor the "guard" flag in the router status when
27210 picking entry guards, rather than looking at is_fast or is_stable.
27211 - Retain unrecognized lines in $DATADIR/state file, so that we can
27212 be forward-compatible.
27213 - Generate 18.0.0.0/8 address policy format in descs when we can;
27214 warn when the mask is not reducible to a bit-prefix.
27215 - Let the user set ControlListenAddress in the torrc. This can be
27216 dangerous, but there are some cases (like a secured LAN) where it
27218 - Split ReachableAddresses into ReachableDirAddresses and
27219 ReachableORAddresses, so we can restrict Dir conns to port 80
27220 and OR conns to port 443.
27221 - Now we can target arch and OS in rpm builds (contributed by
27222 Phobos). Also make the resulting dist-rpm filename match the
27224 - New config options to help controllers: FetchServerDescriptors
27225 and FetchHidServDescriptors for whether to fetch server
27226 info and hidserv info or let the controller do it, and
27227 PublishServerDescriptor and PublishHidServDescriptors.
27228 - Also let the controller set the __AllDirActionsPrivate config
27229 option if you want all directory fetches/publishes to happen via
27230 Tor (it assumes your controller bootstraps your circuits).
27233 Changes in version 0.1.0.17 - 2006-02-17
27234 o Crash bugfixes on 0.1.0.x:
27235 - When servers with a non-zero DirPort came out of hibernation,
27236 sometimes they would trigger an assert.
27238 o Other important bugfixes:
27239 - On platforms that don't have getrlimit (like Windows), we were
27240 artificially constraining ourselves to a max of 1024
27241 connections. Now just assume that we can handle as many as 15000
27242 connections. Hopefully this won't cause other problems.
27244 o Backported features:
27245 - When we're a server, a client asks for an old-style directory,
27246 and our write bucket is empty, don't give it to him. This way
27247 small servers can continue to serve the directory *sometimes*,
27248 without getting overloaded.
27249 - Whenever you get a 503 in response to a directory fetch, try
27250 once more. This will become important once servers start sending
27251 503's whenever they feel busy.
27252 - Fetch a new directory every 120 minutes, not every 40 minutes.
27253 Now that we have hundreds of thousands of users running the old
27254 directory algorithm, it's starting to hurt a lot.
27255 - Bump up the period for forcing a hidden service descriptor upload
27256 from 20 minutes to 1 hour.
27259 Changes in version 0.1.1.13-alpha - 2006-02-09
27260 o Crashes in 0.1.1.x:
27261 - When you tried to setconf ORPort via the controller, Tor would
27262 crash. So people using TorCP to become a server were sad.
27263 - Solve (I hope) the stack-smashing bug that we were seeing on fast
27264 servers. The problem appears to be something do with OpenSSL's
27265 random number generation, or how we call it, or something. Let me
27266 know if the crashes continue.
27267 - Turn crypto hardware acceleration off by default, until we find
27268 somebody smart who can test it for us. (It appears to produce
27269 seg faults in at least some cases.)
27270 - Fix a rare assert error when we've tried all intro points for
27271 a hidden service and we try fetching the service descriptor again:
27272 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
27275 - Fix a major load balance bug: we were round-robining in 16 KB
27276 chunks, and servers with bandwidthrate of 20 KB, while downloading
27277 a 600 KB directory, would starve their other connections. Now we
27278 try to be a bit more fair.
27279 - Dir authorities and mirrors were never expiring the newest
27280 descriptor for each server, causing memory and directory bloat.
27281 - Fix memory-bloating and connection-bloating bug on servers: We
27282 were never closing any connection that had ever had a circuit on
27283 it, because we were checking conn->n_circuits == 0, yet we had a
27284 bug that let it go negative.
27285 - Make Tor work using squid as your http proxy again -- squid
27286 returns an error if you ask for a URL that's too long, and it uses
27287 a really generic error message. Plus, many people are behind a
27288 transparent squid so they don't even realize it.
27289 - On platforms that don't have getrlimit (like Windows), we were
27290 artificially constraining ourselves to a max of 1024
27291 connections. Now just assume that we can handle as many as 15000
27292 connections. Hopefully this won't cause other problems.
27293 - Add a new config option ExitPolicyRejectPrivate which defaults to
27294 1. This means all exit policies will begin with rejecting private
27295 addresses, unless the server operator explicitly turns it off.
27298 - Clients no longer download descriptors for non-running
27300 - Before we add new directory authorities, we should make it
27301 clear that only v1 authorities should receive/publish hidden
27302 service descriptors.
27305 - As soon as we've fetched some more directory info, immediately
27306 try to download more server descriptors. This way we don't have
27307 a 10 second pause during initial bootstrapping.
27308 - Remove even more loud log messages that the server operator can't
27310 - When we're running an obsolete or un-recommended version, make
27311 the log message more clear about what the problem is and what
27312 versions *are* still recommended.
27313 - Provide a more useful warn message when our onion queue gets full:
27314 the CPU is too slow or the exit policy is too liberal.
27315 - Don't warn when we receive a 503 from a dirserver/cache -- this
27316 will pave the way for them being able to refuse if they're busy.
27317 - When we fail to bind a listener, try to provide a more useful
27318 log message: e.g., "Is Tor already running?"
27319 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
27320 Goldberg can prove things about our handshake protocol more
27322 - MaxConn has been obsolete for a while now. Document the ConnLimit
27323 config option, which is a *minimum* number of file descriptors
27324 that must be available else Tor refuses to start.
27325 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
27326 if you log to syslog and want something other than LOG_DAEMON.
27327 - Make dirservers generate a separate "guard" flag to mean,
27328 "would make a good entry guard". Make clients parse it and vote
27329 on it. Not used by clients yet.
27330 - Implement --with-libevent-dir option to ./configure. Also, improve
27331 search techniques to find libevent, and use those for openssl too.
27332 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
27333 - Only start testing reachability once we've established a
27334 circuit. This will make startup on dirservers less noisy.
27335 - Don't try to upload hidden service descriptors until we have
27336 established a circuit.
27337 - Fix the controller's "attachstream 0" command to treat conn like
27338 it just connected, doing address remapping, handling .exit and
27339 .onion idioms, and so on. Now we're more uniform in making sure
27340 that the controller hears about new and closing connections.
27343 Changes in version 0.1.1.12-alpha - 2006-01-11
27344 o Bugfixes on 0.1.1.x:
27345 - The fix to close duplicate server connections was closing all
27346 Tor client connections if they didn't establish a circuit
27347 quickly enough. Oops.
27348 - Fix minor memory issue (double-free) that happened on exit.
27350 o Bugfixes on 0.1.0.x:
27351 - Tor didn't warn when it failed to open a log file.
27354 Changes in version 0.1.1.11-alpha - 2006-01-10
27355 o Crashes in 0.1.1.x:
27356 - Include all the assert/crash fixes from 0.1.0.16.
27357 - If you start Tor and then quit very quickly, there were some
27358 races that tried to free things that weren't allocated yet.
27359 - Fix a rare memory stomp if you're running hidden services.
27360 - Fix segfault when specifying DirServer in config without nickname.
27361 - Fix a seg fault when you finish connecting to a server but at
27362 that moment you dump his server descriptor.
27363 - Extendcircuit and Attachstream controller commands would
27364 assert/crash if you don't give them enough arguments.
27365 - Fix an assert error when we're out of space in the connection_list
27366 and we try to post a hidden service descriptor (reported by weasel).
27367 - If you specify a relative torrc path and you set RunAsDaemon in
27368 your torrc, then it chdir()'s to the new directory. If you HUP,
27369 it tries to load the new torrc location, fails, and exits.
27370 The fix: no longer allow a relative path to torrc using -f.
27373 - Implement "entry guards": automatically choose a handful of entry
27374 nodes and stick with them for all circuits. Only pick new guards
27375 when the ones you have are unsuitable, and if the old guards
27376 become suitable again, switch back. This will increase security
27377 dramatically against certain end-point attacks. The EntryNodes
27378 config option now provides some hints about which entry guards you
27379 want to use most; and StrictEntryNodes means to only use those.
27380 - New directory logic: download by descriptor digest, not by
27381 fingerprint. Caches try to download all listed digests from
27382 authorities; clients try to download "best" digests from caches.
27383 This avoids partitioning and isolating attacks better.
27384 - Make the "stable" router flag in network-status be the median of
27385 the uptimes of running valid servers, and make clients pay
27386 attention to the network-status flags. Thus the cutoff adapts
27387 to the stability of the network as a whole, making IRC, IM, etc
27388 connections more reliable.
27391 - Tor servers with dynamic IP addresses were needing to wait 18
27392 hours before they could start doing reachability testing using
27393 the new IP address and ports. This is because they were using
27394 the internal descriptor to learn what to test, yet they were only
27395 rebuilding the descriptor once they decided they were reachable.
27396 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
27397 to download certain server descriptors, throw them away, and then
27398 fetch them again after 30 minutes. Now mirrors throw away these
27399 server descriptors so clients can't get them.
27400 - We were leaving duplicate connections to other ORs open for a week,
27401 rather than closing them once we detect a duplicate. This only
27402 really affected authdirservers, but it affected them a lot.
27403 - Spread the authdirservers' reachability testing over the entire
27404 testing interval, so we don't try to do 500 TLS's at once every
27408 - If the network is down, and we try to connect to a conn because
27409 we have a circuit in mind, and we timeout (30 seconds) because the
27410 network never answers, we were expiring the circuit, but we weren't
27411 obsoleting the connection or telling the entry_guards functions.
27412 - Some Tor servers process billions of cells per day. These statistics
27413 need to be uint64_t's.
27414 - Check for integer overflows in more places, when adding elements
27415 to smartlists. This could possibly prevent a buffer overflow
27416 on malicious huge inputs. I don't see any, but I haven't looked
27418 - ReachableAddresses kept growing new "reject *:*" lines on every
27420 - When you "setconf log" via the controller, it should remove all
27421 logs. We were automatically adding back in a "log notice stdout".
27422 - Newly bootstrapped Tor networks couldn't establish hidden service
27423 circuits until they had nodes with high uptime. Be more tolerant.
27424 - We were marking servers down when they could not answer every piece
27425 of the directory request we sent them. This was far too harsh.
27426 - Fix the torify (tsocks) config file to not use Tor for localhost
27428 - Directory authorities now go to the proper authority when asking for
27429 a networkstatus, even when they want a compressed one.
27430 - Fix a harmless bug that was causing Tor servers to log
27431 "Got an end because of misc error, but we're not an AP. Closing."
27432 - Authorities were treating their own descriptor changes as cosmetic,
27433 meaning the descriptor available in the network-status and the
27434 descriptor that clients downloaded were different.
27435 - The OS X installer was adding a symlink for tor_resolve but
27436 the binary was called tor-resolve (reported by Thomas Hardly).
27437 - Workaround a problem with some http proxies where they refuse GET
27438 requests that specify "Content-Length: 0" (reported by Adrian).
27439 - Fix wrong log message when you add a "HiddenServiceNodes" config
27440 line without any HiddenServiceDir line (reported by Chris Thomas).
27443 - Write the TorVersion into the state file so we have a prayer of
27444 keeping forward and backward compatibility.
27445 - Revive the FascistFirewall config option rather than eliminating it:
27446 now it's a synonym for ReachableAddresses *:80,*:443.
27447 - Clients choose directory servers from the network status lists,
27448 not from their internal list of router descriptors. Now they can
27449 go to caches directly rather than needing to go to authorities
27451 - Directory authorities ignore router descriptors that have only
27452 cosmetic differences: do this for 0.1.0.x servers now too.
27453 - Add a new flag to network-status indicating whether the server
27454 can answer v2 directory requests too.
27455 - Authdirs now stop whining so loudly about bad descriptors that
27456 they fetch from other dirservers. So when there's a log complaint,
27457 it's for sure from a freshly uploaded descriptor.
27458 - Reduce memory requirements in our structs by changing the order
27460 - There used to be two ways to specify your listening ports in a
27461 server descriptor: on the "router" line and with a separate "ports"
27462 line. Remove support for the "ports" line.
27463 - New config option "AuthDirRejectUnlisted" for auth dirservers as
27464 a panic button: if we get flooded with unusable servers we can
27465 revert to only listing servers in the approved-routers file.
27466 - Auth dir servers can now mark a fingerprint as "!reject" or
27467 "!invalid" in the approved-routers file (as its nickname), to
27468 refuse descriptors outright or include them but marked as invalid.
27469 - Servers store bandwidth history across restarts/crashes.
27470 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
27471 get a better idea of why their circuits failed. Not used yet.
27472 - Directory mirrors now cache up to 16 unrecognized network-status
27473 docs. Now we can add new authdirservers and they'll be cached too.
27474 - When picking a random directory, prefer non-authorities if any
27476 - New controller option "getinfo desc/all-recent" to fetch the
27477 latest server descriptor for every router that Tor knows about.
27480 Changes in version 0.1.0.16 - 2006-01-02
27481 o Crash bugfixes on 0.1.0.x:
27482 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
27483 corrupting the heap, losing FDs, or crashing when we need to resize
27484 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
27485 - It turns out sparc64 platforms crash on unaligned memory access
27486 too -- so detect and avoid this.
27487 - Handle truncated compressed data correctly (by detecting it and
27489 - Fix possible-but-unlikely free(NULL) in control.c.
27490 - When we were closing connections, there was a rare case that
27491 stomped on memory, triggering seg faults and asserts.
27492 - Avoid potential infinite recursion when building a descriptor. (We
27493 don't know that it ever happened, but better to fix it anyway.)
27494 - We were neglecting to unlink marked circuits from soon-to-close OR
27495 connections, which caused some rare scribbling on freed memory.
27496 - Fix a memory stomping race bug when closing the joining point of two
27497 rendezvous circuits.
27498 - Fix an assert in time parsing found by Steven Murdoch.
27500 o Other bugfixes on 0.1.0.x:
27501 - When we're doing reachability testing, provide more useful log
27502 messages so the operator knows what to expect.
27503 - Do not check whether DirPort is reachable when we are suppressing
27504 advertising it because of hibernation.
27505 - When building with -static or on Solaris, we sometimes needed -ldl.
27506 - When we're deciding whether a stream has enough circuits around
27507 that can handle it, count the freshly dirty ones and not the ones
27508 that are so dirty they won't be able to handle it.
27509 - When we're expiring old circuits, we had a logic error that caused
27510 us to close new rendezvous circuits rather than old ones.
27511 - Give a more helpful log message when you try to change ORPort via
27512 the controller: you should upgrade Tor if you want that to work.
27513 - We were failing to parse Tor versions that start with "Tor ".
27514 - Tolerate faulty streams better: when a stream fails for reason
27515 exitpolicy, stop assuming that the router is lying about his exit
27516 policy. When a stream fails for reason misc, allow it to retry just
27517 as if it was resolvefailed. When a stream has failed three times,
27518 reset its failure count so we can try again and get all three tries.
27521 Changes in version 0.1.1.10-alpha - 2005-12-11
27522 o Correctness bugfixes on 0.1.0.x:
27523 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
27524 corrupting the heap, losing FDs, or crashing when we need to resize
27525 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
27526 - Stop doing the complex voodoo overkill checking for insecure
27527 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
27528 - When we were closing connections, there was a rare case that
27529 stomped on memory, triggering seg faults and asserts.
27530 - We were neglecting to unlink marked circuits from soon-to-close OR
27531 connections, which caused some rare scribbling on freed memory.
27532 - When we're deciding whether a stream has enough circuits around
27533 that can handle it, count the freshly dirty ones and not the ones
27534 that are so dirty they won't be able to handle it.
27535 - Recover better from TCP connections to Tor servers that are
27536 broken but don't tell you (it happens!); and rotate TLS
27537 connections once a week.
27538 - When we're expiring old circuits, we had a logic error that caused
27539 us to close new rendezvous circuits rather than old ones.
27540 - Fix a scary-looking but apparently harmless bug where circuits
27541 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
27542 servers, and never switch to state CIRCUIT_STATE_OPEN.
27543 - When building with -static or on Solaris, we sometimes needed to
27545 - Give a useful message when people run Tor as the wrong user,
27546 rather than telling them to start chowning random directories.
27547 - We were failing to inform the controller about new .onion streams.
27549 o Security bugfixes on 0.1.0.x:
27550 - Refuse server descriptors if the fingerprint line doesn't match
27551 the included identity key. Tor doesn't care, but other apps (and
27552 humans) might actually be trusting the fingerprint line.
27553 - We used to kill the circuit when we receive a relay command we
27554 don't recognize. Now we just drop it.
27555 - Start obeying our firewall options more rigorously:
27556 . If we can't get to a dirserver directly, try going via Tor.
27557 . Don't ever try to connect (as a client) to a place our
27558 firewall options forbid.
27559 . If we specify a proxy and also firewall options, obey the
27560 firewall options even when we're using the proxy: some proxies
27561 can only proxy to certain destinations.
27562 - Fix a bug found by Lasse Overlier: when we were making internal
27563 circuits (intended to be cannibalized later for rendezvous and
27564 introduction circuits), we were picking them so that they had
27565 useful exit nodes. There was no need for this, and it actually
27566 aids some statistical attacks.
27567 - Start treating internal circuits and exit circuits separately.
27568 It's important to keep them separate because internal circuits
27569 have their last hops picked like middle hops, rather than like
27570 exit hops. So exiting on them will break the user's expectations.
27572 o Bugfixes on 0.1.1.x:
27573 - Take out the mis-feature where we tried to detect IP address
27574 flapping for people with DynDNS, and chose not to upload a new
27575 server descriptor sometimes.
27576 - Try to be compatible with OpenSSL 0.9.6 again.
27577 - Log fix: when the controller is logging about .onion addresses,
27578 sometimes it didn't include the ".onion" part of the address.
27579 - Don't try to modify options->DirServers internally -- if the
27580 user didn't specify any, just add the default ones directly to
27581 the trusted dirserver list. This fixes a bug where people running
27582 controllers would use SETCONF on some totally unrelated config
27583 option, and Tor would start yelling at them about changing their
27585 - Let the controller's redirectstream command specify a port, in
27586 case the controller wants to change that too.
27587 - When we requested a pile of server descriptors, we sometimes
27588 accidentally launched a duplicate request for the first one.
27589 - Bugfix for trackhostexits: write down the fingerprint of the
27590 chosen exit, not its nickname, because the chosen exit might not
27592 - When parsing foo.exit, if foo is unknown, and we are leaving
27593 circuits unattached, set the chosen_exit field and leave the
27594 address empty. This matters because controllers got confused
27596 - Directory authorities no longer try to download server
27597 descriptors that they know they will reject.
27599 o Features and updates:
27600 - Replace balanced trees with hash tables: this should make stuff
27601 significantly faster.
27602 - Resume using the AES counter-mode implementation that we ship,
27603 rather than OpenSSL's. Ours is significantly faster.
27604 - Many other CPU and memory improvements.
27605 - Add a new config option FastFirstHopPK (on by default) so clients
27606 do a trivial crypto handshake for their first hop, since TLS has
27607 already taken care of confidentiality and authentication.
27608 - Add a new config option TestSocks so people can see if their
27609 applications are using socks4, socks4a, socks5-with-ip, or
27610 socks5-with-hostname. This way they don't have to keep mucking
27611 with tcpdump and wondering if something got cached somewhere.
27612 - Warn when listening on a public address for socks. I suspect a
27613 lot of people are setting themselves up as open socks proxies,
27614 and they have no idea that jerks on the Internet are using them,
27615 since they simply proxy the traffic into the Tor network.
27616 - Add "private:*" as an alias in configuration for policies. Now
27617 you can simplify your exit policy rather than needing to list
27618 every single internal or nonroutable network space.
27619 - Add a new controller event type that allows controllers to get
27620 all server descriptors that were uploaded to a router in its role
27621 as authoritative dirserver.
27622 - Start shipping socks-extensions.txt, tor-doc-unix.html,
27623 tor-doc-server.html, and stylesheet.css in the tarball.
27624 - Stop shipping tor-doc.html in the tarball.
27627 Changes in version 0.1.1.9-alpha - 2005-11-15
27628 o Usability improvements:
27629 - Start calling it FooListenAddress rather than FooBindAddress,
27630 since few of our users know what it means to bind an address
27632 - Reduce clutter in server logs. We're going to try to make
27633 them actually usable now. New config option ProtocolWarnings that
27634 lets you hear about how _other Tors_ are breaking the protocol. Off
27636 - Divide log messages into logging domains. Once we put some sort
27637 of interface on this, it will let people looking at more verbose
27638 log levels specify the topics they want to hear more about.
27639 - Make directory servers return better http 404 error messages
27640 instead of a generic "Servers unavailable".
27641 - Check for even more Windows version flags when writing the platform
27642 string in server descriptors, and note any we don't recognize.
27643 - Clean up more of the OpenSSL memory when exiting, so we can detect
27644 memory leaks better.
27645 - Make directory authorities be non-versioning, non-naming by
27646 default. Now we can add new directory servers without requiring
27647 their operators to pay close attention.
27648 - When logging via syslog, include the pid whenever we provide
27649 a log entry. Suggested by Todd Fries.
27651 o Performance improvements:
27652 - Directory servers now silently throw away new descriptors that
27653 haven't changed much if the timestamps are similar. We do this to
27654 tolerate older Tor servers that upload a new descriptor every 15
27655 minutes. (It seemed like a good idea at the time.)
27656 - Inline bottleneck smartlist functions; use fast versions by default.
27657 - Add a "Map from digest to void*" abstraction digestmap_t so we
27658 can do less hex encoding/decoding. Use it in router_get_by_digest()
27659 to resolve a performance bottleneck.
27660 - Allow tor_gzip_uncompress to extract as much as possible from
27661 truncated compressed data. Try to extract as many
27662 descriptors as possible from truncated http responses (when
27663 DIR_PURPOSE_FETCH_ROUTERDESC).
27664 - Make circ->onionskin a pointer, not a static array. moria2 was using
27665 125000 circuit_t's after it had been up for a few weeks, which
27666 translates to 20+ megs of wasted space.
27667 - The private half of our EDH handshake keys are now chosen out
27668 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
27670 o Security improvements:
27671 - Start making directory caches retain old routerinfos, so soon
27672 clients can start asking by digest of descriptor rather than by
27673 fingerprint of server.
27674 - Add half our entropy from RAND_poll in OpenSSL. This knows how
27675 to use egd (if present), openbsd weirdness (if present), vms/os2
27676 weirdness (if we ever port there), and more in the future.
27678 o Bugfixes on 0.1.0.x:
27679 - Do round-robin writes of at most 16 kB per write. This might be
27680 more fair on loaded Tor servers, and it might resolve our Windows
27681 crash bug. It might also slow things down.
27682 - Our TLS handshakes were generating a single public/private
27683 keypair for the TLS context, rather than making a new one for
27684 each new connections. Oops. (But we were still rotating them
27685 periodically, so it's not so bad.)
27686 - When we were cannibalizing a circuit with a particular exit
27687 node in mind, we weren't checking to see if that exit node was
27688 already present earlier in the circuit. Oops.
27689 - When a Tor server's IP changes (e.g. from a dyndns address),
27690 upload a new descriptor so clients will learn too.
27691 - Really busy servers were keeping enough circuits open on stable
27692 connections that they were wrapping around the circuit_id
27693 space. (It's only two bytes.) This exposed a bug where we would
27694 feel free to reuse a circuit_id even if it still exists but has
27695 been marked for close. Try to fix this bug. Some bug remains.
27696 - If we would close a stream early (e.g. it asks for a .exit that
27697 we know would refuse it) but the LeaveStreamsUnattached config
27698 option is set by the controller, then don't close it.
27700 o Bugfixes on 0.1.1.8-alpha:
27701 - Fix a big pile of memory leaks, some of them serious.
27702 - Do not try to download a routerdesc if we would immediately reject
27704 - Resume inserting a newline between all router descriptors when
27705 generating (old style) signed directories, since our spec says
27707 - When providing content-type application/octet-stream for
27708 server descriptors using .z, we were leaving out the
27709 content-encoding header. Oops. (Everything tolerated this just
27710 fine, but that doesn't mean we need to be part of the problem.)
27711 - Fix a potential seg fault in getconf and getinfo using version 1
27712 of the controller protocol.
27713 - Avoid crash: do not check whether DirPort is reachable when we
27714 are suppressing it because of hibernation.
27715 - Make --hash-password not crash on exit.
27718 Changes in version 0.1.1.8-alpha - 2005-10-07
27719 o New features (major):
27720 - Clients don't download or use the directory anymore. Now they
27721 download and use network-statuses from the trusted dirservers,
27722 and fetch individual server descriptors as needed from mirrors.
27723 See dir-spec.txt for all the gory details.
27724 - Be more conservative about whether to advertise our DirPort.
27725 The main change is to not advertise if we're running at capacity
27726 and either a) we could hibernate or b) our capacity is low and
27727 we're using a default DirPort.
27728 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
27730 o New features (minor):
27731 - Try to be smart about when to retry network-status and
27732 server-descriptor fetches. Still needs some tuning.
27733 - Stop parsing, storing, or using running-routers output (but
27734 mirrors still cache and serve it).
27735 - Consider a threshold of versioning dirservers (dirservers who have
27736 an opinion about which Tor versions are still recommended) before
27737 deciding whether to warn the user that he's obsolete.
27738 - Dirservers can now reject/invalidate by key and IP, with the
27739 config options "AuthDirInvalid" and "AuthDirReject". This is
27740 useful since currently we automatically list servers as running
27741 and usable even if we know they're jerks.
27742 - Provide dire warnings to any users who set DirServer; move it out
27743 of torrc.sample and into torrc.complete.
27744 - Add MyFamily to torrc.sample in the server section.
27745 - Add nicknames to the DirServer line, so we can refer to them
27746 without requiring all our users to memorize their IP addresses.
27747 - When we get an EOF or a timeout on a directory connection, note
27748 how many bytes of serverdesc we are dropping. This will help
27749 us determine whether it is smart to parse incomplete serverdesc
27751 - Add a new function to "change pseudonyms" -- that is, to stop
27752 using any currently-dirty circuits for new streams, so we don't
27753 link new actions to old actions. Currently it's only called on
27754 HUP (or SIGNAL RELOAD).
27755 - On sighup, if UseHelperNodes changed to 1, use new circuits.
27756 - Start using RAND_bytes rather than RAND_pseudo_bytes from
27757 OpenSSL. Also, reseed our entropy every hour, not just at
27758 startup. And entropy in 512-bit chunks, not 160-bit chunks.
27760 o Fixes on 0.1.1.7-alpha:
27761 - Nobody ever implemented EVENT_ADDRMAP for control protocol
27762 version 0, so don't let version 0 controllers ask for it.
27763 - If you requested something with too many newlines via the
27764 v1 controller protocol, you could crash tor.
27765 - Fix a number of memory leaks, including some pretty serious ones.
27766 - Re-enable DirPort testing again, so Tor servers will be willing
27767 to advertise their DirPort if it's reachable.
27768 - On TLS handshake, only check the other router's nickname against
27769 its expected nickname if is_named is set.
27771 o Fixes forward-ported from 0.1.0.15:
27772 - Don't crash when we don't have any spare file descriptors and we
27773 try to spawn a dns or cpu worker.
27774 - Make the numbers in read-history and write-history into uint64s,
27775 so they don't overflow and publish negatives in the descriptor.
27777 o Fixes on 0.1.0.x:
27778 - For the OS X package's modified privoxy config file, comment
27779 out the "logfile" line so we don't log everything passed
27781 - We were whining about using socks4 or socks5-with-local-lookup
27782 even when it's an IP in the "virtual" range we designed exactly
27784 - We were leaking some memory every time the client changes IPs.
27785 - Never call free() on tor_malloc()d memory. This will help us
27786 use dmalloc to detect memory leaks.
27787 - Check for named servers when looking them up by nickname;
27788 warn when we'recalling a non-named server by its nickname;
27789 don't warn twice about the same name.
27790 - Try to list MyFamily elements by key, not by nickname, and warn
27791 if we've not heard of the server.
27792 - Make windows platform detection (uname equivalent) smarter.
27793 - It turns out sparc64 doesn't like unaligned access either.
27796 Changes in version 0.1.0.15 - 2005-09-23
27797 o Bugfixes on 0.1.0.x:
27798 - Reject ports 465 and 587 (spam targets) in default exit policy.
27799 - Don't crash when we don't have any spare file descriptors and we
27800 try to spawn a dns or cpu worker.
27801 - Get rid of IgnoreVersion undocumented config option, and make us
27802 only warn, never exit, when we're running an obsolete version.
27803 - Don't try to print a null string when your server finds itself to
27804 be unreachable and the Address config option is empty.
27805 - Make the numbers in read-history and write-history into uint64s,
27806 so they don't overflow and publish negatives in the descriptor.
27807 - Fix a minor memory leak in smartlist_string_remove().
27808 - We were only allowing ourselves to upload a server descriptor at
27809 most every 20 minutes, even if it changed earlier than that.
27810 - Clean up log entries that pointed to old URLs.
27813 Changes in version 0.1.1.7-alpha - 2005-09-14
27814 o Fixes on 0.1.1.6-alpha:
27815 - Exit servers were crashing when people asked them to make a
27816 connection to an address not in their exit policy.
27817 - Looking up a non-existent stream for a v1 control connection would
27819 - Fix a seg fault if we ask a dirserver for a descriptor by
27820 fingerprint but he doesn't know about him.
27821 - SETCONF was appending items to linelists, not clearing them.
27822 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
27823 out and refuse the setconf if it would fail.
27824 - Downgrade the dirserver log messages when whining about
27828 - Add Peter Palfrader's check-tor script to tor/contrib/
27829 It lets you easily check whether a given server (referenced by
27830 nickname) is reachable by you.
27831 - Numerous changes to move towards client-side v2 directories. Not
27834 o Fixes on 0.1.0.x:
27835 - If the user gave tor an odd number of command-line arguments,
27836 we were silently ignoring the last one. Now we complain and fail.
27837 [This wins the oldest-bug prize -- this bug has been present since
27838 November 2002, as released in Tor 0.0.0.]
27839 - Do not use unaligned memory access on alpha, mips, or mipsel.
27840 It *works*, but is very slow, so we treat them as if it doesn't.
27841 - Retry directory requests if we fail to get an answer we like
27842 from a given dirserver (we were retrying before, but only if
27843 we fail to connect).
27844 - When writing the RecommendedVersions line, sort them first.
27845 - When the client asked for a rendezvous port that the hidden
27846 service didn't want to provide, we were sending an IP address
27847 back along with the end cell. Fortunately, it was zero. But stop
27849 - Correct "your server is reachable" log entries to indicate that
27850 it was self-testing that told us so.
27853 Changes in version 0.1.1.6-alpha - 2005-09-09
27854 o Fixes on 0.1.1.5-alpha:
27855 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
27856 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
27857 - Fix bug with tor_memmem finding a match at the end of the string.
27858 - Make unit tests run without segfaulting.
27859 - Resolve some solaris x86 compile warnings.
27860 - Handle duplicate lines in approved-routers files without warning.
27861 - Fix bug where as soon as a server refused any requests due to his
27862 exit policy (e.g. when we ask for localhost and he tells us that's
27863 127.0.0.1 and he won't do it), we decided he wasn't obeying his
27864 exit policy using him for any exits.
27865 - Only do openssl hardware accelerator stuff if openssl version is
27868 o New controller features/fixes:
27869 - Add a "RESETCONF" command so you can set config options like
27870 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
27871 a config option in the torrc with no value, then it clears it
27872 entirely (rather than setting it to its default).
27873 - Add a "GETINFO config-file" to tell us where torrc is.
27874 - Avoid sending blank lines when GETINFO replies should be empty.
27875 - Add a QUIT command for the controller (for using it manually).
27876 - Fix a bug in SAVECONF that was adding default dirservers and
27877 other redundant entries to the torrc file.
27879 o Start on the new directory design:
27880 - Generate, publish, cache, serve new network-status format.
27881 - Publish individual descriptors (by fingerprint, by "all", and by
27883 - Publish client and server recommended versions separately.
27884 - Allow tor_gzip_uncompress() to handle multiple concatenated
27885 compressed strings. Serve compressed groups of router
27886 descriptors. The compression logic here could be more
27888 - Distinguish v1 authorities (all currently trusted directories)
27889 from v2 authorities (all trusted directories).
27890 - Change DirServers config line to note which dirs are v1 authorities.
27891 - Add configuration option "V1AuthoritativeDirectory 1" which
27892 moria1, moria2, and tor26 should set.
27893 - Remove option when getting directory cache to see whether they
27894 support running-routers; they all do now. Replace it with one
27895 to see whether caches support v2 stuff.
27898 - Dirservers now do their own external reachability testing of each
27899 Tor server, and only list them as running if they've been found to
27900 be reachable. We also send back warnings to the server's logs if
27901 it uploads a descriptor that we already believe is unreachable.
27902 - Implement exit enclaves: if we know an IP address for the
27903 destination, and there's a running Tor server at that address
27904 which allows exit to the destination, then extend the circuit to
27905 that exit first. This provides end-to-end encryption and end-to-end
27906 authentication. Also, if the user wants a .exit address or enclave,
27907 use 4 hops rather than 3, and cannibalize a general circ for it
27909 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
27910 controller. Also, rotate dns and cpu workers if the controller
27911 changes options that will affect them; and initialize the dns
27912 worker cache tree whether or not we start out as a server.
27913 - Only upload a new server descriptor when options change, 18
27914 hours have passed, uptime is reset, or bandwidth changes a lot.
27915 - Check [X-]Forwarded-For headers in HTTP requests when generating
27916 log messages. This lets people run dirservers (and caches) behind
27917 Apache but still know which IP addresses are causing warnings.
27919 o Config option changes:
27920 - Replace (Fascist)Firewall* config options with a new
27921 ReachableAddresses option that understands address policies.
27922 For example, "ReachableAddresses *:80,*:443"
27923 - Get rid of IgnoreVersion undocumented config option, and make us
27924 only warn, never exit, when we're running an obsolete version.
27925 - Make MonthlyAccountingStart config option truly obsolete now.
27927 o Fixes on 0.1.0.x:
27928 - Reject ports 465 and 587 in the default exit policy, since
27929 people have started using them for spam too.
27930 - It turns out we couldn't bootstrap a network since we added
27931 reachability detection in 0.1.0.1-rc. Good thing the Tor network
27932 has never gone down. Add an AssumeReachable config option to let
27933 servers and dirservers bootstrap. When we're trying to build a
27934 high-uptime or high-bandwidth circuit but there aren't enough
27935 suitable servers, try being less picky rather than simply failing.
27936 - Our logic to decide if the OR we connected to was the right guy
27937 was brittle and maybe open to a mitm for unverified routers.
27938 - We weren't cannibalizing circuits correctly for
27939 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
27940 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
27941 build those from scratch. This should make hidden services faster.
27942 - Predict required circuits better, with an eye toward making hidden
27943 services faster on the service end.
27944 - Retry streams if the exit node sends back a 'misc' failure. This
27945 should result in fewer random failures. Also, after failing
27946 from resolve failed or misc, reset the num failures, so we give
27947 it a fair shake next time we try.
27948 - Clean up the rendezvous warn log msgs, and downgrade some to info.
27949 - Reduce severity on logs about dns worker spawning and culling.
27950 - When we're shutting down and we do something like try to post a
27951 server descriptor or rendezvous descriptor, don't complain that
27952 we seem to be unreachable. Of course we are, we're shutting down.
27953 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
27954 We don't use them yet, but maybe one day our DNS resolver will be
27955 able to discover them.
27956 - Make ContactInfo mandatory for authoritative directory servers.
27957 - Require server descriptors to list IPv4 addresses -- hostnames
27958 are no longer allowed. This also fixes some potential security
27959 problems with people providing hostnames as their address and then
27960 preferentially resolving them to partition users.
27961 - Change log line for unreachability to explicitly suggest /etc/hosts
27962 as the culprit. Also make it clearer what IP address and ports we're
27963 testing for reachability.
27964 - Put quotes around user-supplied strings when logging so users are
27965 more likely to realize if they add bad characters (like quotes)
27967 - Let auth dir servers start without specifying an Address config
27969 - Make unit tests (and other invocations that aren't the real Tor)
27970 run without launching listeners, creating subdirectories, and so on.
27973 Changes in version 0.1.1.5-alpha - 2005-08-08
27974 o Bugfixes included in 0.1.0.14.
27976 o Bugfixes on 0.1.0.x:
27977 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
27978 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
27979 it would silently using ignore the 6668.
27982 Changes in version 0.1.0.14 - 2005-08-08
27983 o Bugfixes on 0.1.0.x:
27984 - Fix the other half of the bug with crypto handshakes
27986 - Fix an assert trigger if you send a 'signal term' via the
27987 controller when it's listening for 'event info' messages.
27990 Changes in version 0.1.1.4-alpha - 2005-08-04
27991 o Bugfixes included in 0.1.0.13.
27994 - Improve tor_gettimeofday() granularity on windows.
27995 - Make clients regenerate their keys when their IP address changes.
27996 - Implement some more GETINFO goodness: expose helper nodes, config
27997 options, getinfo keys.
28000 Changes in version 0.1.0.13 - 2005-08-04
28001 o Bugfixes on 0.1.0.x:
28002 - Fix a critical bug in the security of our crypto handshakes.
28003 - Fix a size_t underflow in smartlist_join_strings2() that made
28004 it do bad things when you hand it an empty smartlist.
28005 - Fix Windows installer to ship Tor license (thanks to Aphex for
28006 pointing out this oversight) and put a link to the doc directory
28008 - Explicitly set no-unaligned-access for sparc: it turns out the
28009 new gcc's let you compile broken code, but that doesn't make it
28013 Changes in version 0.1.1.3-alpha - 2005-07-23
28014 o Bugfixes on 0.1.1.2-alpha:
28015 - Fix a bug in handling the controller's "post descriptor"
28017 - Fix several bugs in handling the controller's "extend circuit"
28019 - Fix a bug in handling the controller's "stream status" event.
28020 - Fix an assert failure if we have a controller listening for
28021 circuit events and we go offline.
28022 - Re-allow hidden service descriptors to publish 0 intro points.
28023 - Fix a crash when generating your hidden service descriptor if
28024 you don't have enough intro points already.
28026 o New features on 0.1.1.2-alpha:
28027 - New controller function "getinfo accounting", to ask how
28028 many bytes we've used in this time period.
28029 - Experimental support for helper nodes: a lot of the risk from
28030 a small static adversary comes because users pick new random
28031 nodes every time they rebuild a circuit. Now users will try to
28032 stick to the same small set of entry nodes if they can. Not
28033 enabled by default yet.
28035 o Bugfixes on 0.1.0.12:
28036 - If you're an auth dir server, always publish your dirport,
28037 even if you haven't yet found yourself to be reachable.
28038 - Fix a size_t underflow in smartlist_join_strings2() that made
28039 it do bad things when you hand it an empty smartlist.
28042 Changes in version 0.1.0.12 - 2005-07-18
28043 o New directory servers:
28044 - tor26 has changed IP address.
28046 o Bugfixes on 0.1.0.x:
28047 - Fix a possible double-free in tor_gzip_uncompress().
28048 - When --disable-threads is set, do not search for or link against
28049 pthreads libraries.
28050 - Don't trigger an assert if an authoritative directory server
28051 claims its dirport is 0.
28052 - Fix bug with removing Tor as an NT service: some people were
28053 getting "The service did not return an error." Thanks to Matt
28057 Changes in version 0.1.1.2-alpha - 2005-07-15
28058 o New directory servers:
28059 - tor26 has changed IP address.
28061 o Bugfixes on 0.1.0.x, crashes/leaks:
28062 - Port the servers-not-obeying-their-exit-policies fix from
28064 - Fix an fd leak in start_daemon().
28065 - On Windows, you can't always reopen a port right after you've
28066 closed it. So change retry_listeners() to only close and re-open
28067 ports that have changed.
28068 - Fix a possible double-free in tor_gzip_uncompress().
28070 o Bugfixes on 0.1.0.x, usability:
28071 - When tor_socketpair() fails in Windows, give a reasonable
28072 Windows-style errno back.
28073 - Let people type "tor --install" as well as "tor -install" when
28075 want to make it an NT service.
28076 - NT service patch from Matt Edman to improve error messages.
28077 - When the controller asks for a config option with an abbreviated
28078 name, give the full name in our response.
28079 - Correct the man page entry on TrackHostExitsExpire.
28080 - Looks like we were never delivering deflated (i.e. compressed)
28081 running-routers lists, even when asked. Oops.
28082 - When --disable-threads is set, do not search for or link against
28083 pthreads libraries.
28085 o Bugfixes on 0.1.1.x:
28086 - Fix a seg fault with autodetecting which controller version is
28090 - New hidden service descriptor format: put a version in it, and
28091 let people specify introduction/rendezvous points that aren't
28092 in "the directory" (which is subjective anyway).
28093 - Allow the DEBUG controller event to work again. Mark certain log
28094 entries as "don't tell this to controllers", so we avoid cycles.
28097 Changes in version 0.1.0.11 - 2005-06-30
28098 o Bugfixes on 0.1.0.x:
28099 - Fix major security bug: servers were disregarding their
28100 exit policies if clients behaved unexpectedly.
28101 - Make OS X init script check for missing argument, so we don't
28102 confuse users who invoke it incorrectly.
28103 - Fix a seg fault in "tor --hash-password foo".
28104 - The MAPADDRESS control command was broken.
28107 Changes in version 0.1.1.1-alpha - 2005-06-29
28109 - Make OS X init script check for missing argument, so we don't
28110 confuse users who invoke it incorrectly.
28111 - Fix a seg fault in "tor --hash-password foo".
28112 - Fix a possible way to DoS dirservers.
28113 - When we complain that your exit policy implicitly allows local or
28114 private address spaces, name them explicitly so operators can
28116 - Make the log message less scary when all the dirservers are
28117 temporarily unreachable.
28118 - We were printing the number of idle dns workers incorrectly when
28122 - Revised controller protocol (version 1) that uses ascii rather
28123 than binary. Add supporting libraries in python and java so you
28124 can use the controller from your applications without caring how
28125 our protocol works.
28126 - Spiffy new support for crypto hardware accelerators. Can somebody
28130 Changes in version 0.0.9.10 - 2005-06-16
28131 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
28132 - Refuse relay cells that claim to have a length larger than the
28133 maximum allowed. This prevents a potential attack that could read
28134 arbitrary memory (e.g. keys) from an exit server's process
28138 Changes in version 0.1.0.10 - 2005-06-14
28139 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
28140 libevent before 1.1a.
28143 Changes in version 0.1.0.9-rc - 2005-06-09
28145 - Reset buf->highwater every time buf_shrink() is called, not just on
28146 a successful shrink. This was causing significant memory bloat.
28147 - Fix buffer overflow when checking hashed passwords.
28148 - Security fix: if seeding the RNG on Win32 fails, quit.
28149 - Allow seeding the RNG on Win32 even when you're not running as
28151 - Disable threading on Solaris too. Something is wonky with it,
28152 cpuworkers, and reentrant libs.
28153 - Reenable the part of the code that tries to flush as soon as an
28154 OR outbuf has a full TLS record available. Perhaps this will make
28155 OR outbufs not grow as huge except in rare cases, thus saving lots
28156 of CPU time plus memory.
28157 - Reject malformed .onion addresses rather then passing them on as
28158 normal web requests.
28159 - Adapt patch from Adam Langley: fix possible memory leak in
28160 tor_lookup_hostname().
28161 - Initialize libevent later in the startup process, so the logs are
28162 already established by the time we start logging libevent warns.
28163 - Use correct errno on win32 if libevent fails.
28164 - Check and warn about known-bad/slow libevent versions.
28165 - Pay more attention to the ClientOnly config option.
28166 - Have torctl.in/tor.sh.in check for location of su binary (needed
28168 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
28169 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
28170 HttpProxyAuthenticator
28171 - Stop warning about sigpipes in the logs. We're going to
28172 pretend that getting these occasionally is normal and fine.
28173 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
28175 installer screens; and don't put stuff into StartupItems unless
28176 the user asks you to.
28177 - Require servers that use the default dirservers to have public IP
28178 addresses. We have too many servers that are configured with private
28179 IPs and their admins never notice the log entries complaining that
28180 their descriptors are being rejected.
28181 - Add OSX uninstall instructions. An actual uninstall script will
28185 Changes in version 0.1.0.8-rc - 2005-05-23
28187 - It turns out that kqueue on OS X 10.3.9 was causing kernel
28188 panics. Disable kqueue on all OS X Tors.
28189 - Fix RPM: remove duplicate line accidentally added to the rpm
28191 - Disable threads on openbsd too, since its gethostaddr is not
28193 - Tolerate libevent 0.8 since it still works, even though it's
28195 - Enable building on Red Hat 9.0 again.
28196 - Allow the middle hop of the testing circuit to be running any
28197 version, now that most of them have the bugfix to let them connect
28198 to unknown servers. This will allow reachability testing to work
28199 even when 0.0.9.7-0.0.9.9 become obsolete.
28200 - Handle relay cells with rh.length too large. This prevents
28201 a potential attack that could read arbitrary memory (maybe even
28202 keys) from the exit server's process.
28203 - We screwed up the dirport reachability testing when we don't yet
28204 have a cached version of the directory. Hopefully now fixed.
28205 - Clean up router_load_single_router() (used by the controller),
28206 so it doesn't seg fault on error.
28207 - Fix a minor memory leak when somebody establishes an introduction
28208 point at your Tor server.
28209 - If a socks connection ends because read fails, don't warn that
28210 you're not sending a socks reply back.
28213 - Add HttpProxyAuthenticator config option too, that works like
28214 the HttpsProxyAuthenticator config option.
28215 - Encode hashed controller passwords in hex instead of base64,
28216 to make it easier to write controllers.
28219 Changes in version 0.1.0.7-rc - 2005-05-17
28221 - Fix a bug in the OS X package installer that prevented it from
28222 installing on Tiger.
28223 - Fix a script bug in the OS X package installer that made it
28224 complain during installation.
28225 - Find libevent even if it's hiding in /usr/local/ and your
28226 CFLAGS and LDFLAGS don't tell you to look there.
28227 - Be able to link with libevent as a shared library (the default
28228 after 1.0d), even if it's hiding in /usr/local/lib and even
28229 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
28230 assuming you're running gcc. Otherwise fail and give a useful
28232 - Fix a bug in the RPM packager: set home directory for _tor to
28233 something more reasonable when first installing.
28234 - Free a minor amount of memory that is still reachable on exit.
28237 Changes in version 0.1.0.6-rc - 2005-05-14
28239 - Implement --disable-threads configure option. Disable threads on
28240 netbsd by default, because it appears to have no reentrant resolver
28242 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
28243 release (1.1) detects and disables kqueue if it's broken.
28244 - Append default exit policy before checking for implicit internal
28245 addresses. Now we don't log a bunch of complaints on startup
28246 when using the default exit policy.
28247 - Some people were putting "Address " in their torrc, and they had
28248 a buggy resolver that resolved " " to 0.0.0.0. Oops.
28249 - If DataDir is ~/.tor, and that expands to /.tor, then default to
28250 LOCALSTATEDIR/tor instead.
28251 - Fix fragmented-message bug in TorControl.py.
28252 - Resolve a minor bug which would prevent unreachable dirports
28253 from getting suppressed in the published descriptor.
28254 - When the controller gave us a new descriptor, we weren't resolving
28255 it immediately, so Tor would think its address was 0.0.0.0 until
28256 we fetched a new directory.
28257 - Fix an uppercase/lowercase case error in suppressing a bogus
28258 libevent warning on some Linuxes.
28261 - Begin scrubbing sensitive strings from logs by default. Turn off
28262 the config option SafeLogging if you need to do debugging.
28263 - Switch to a new buffer management algorithm, which tries to avoid
28264 reallocing and copying quite as much. In first tests it looks like
28265 it uses *more* memory on average, but less cpu.
28266 - First cut at support for "create-fast" cells. Clients can use
28267 these when extending to their first hop, since the TLS already
28268 provides forward secrecy and authentication. Not enabled on
28270 - When dirservers refuse a router descriptor, we now log its
28271 contactinfo, platform, and the poster's IP address.
28272 - Call tor_free_all instead of connections_free_all after forking, to
28273 save memory on systems that need to fork.
28274 - Whine at you if you're a server and you don't set your contactinfo.
28275 - Implement --verify-config command-line option to check if your torrc
28276 is valid without actually launching Tor.
28277 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
28278 rather than just rejecting it.
28281 Changes in version 0.1.0.5-rc - 2005-04-27
28283 - Stop trying to print a null pointer if an OR conn fails because
28284 we didn't like its cert.
28286 - Switch our internal buffers implementation to use a ring buffer,
28287 to hopefully improve performance for fast servers a lot.
28288 - Add HttpsProxyAuthenticator support (basic auth only), based
28289 on patch from Adam Langley.
28290 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
28291 the fast servers that have been joining lately.
28292 - Give hidden service accesses extra time on the first attempt,
28293 since 60 seconds is often only barely enough. This might improve
28295 - Improve performance for dirservers: stop re-parsing the whole
28296 directory every time you regenerate it.
28297 - Add more debugging info to help us find the weird dns freebsd
28298 pthreads bug; cleaner debug messages to help track future issues.
28301 Changes in version 0.0.9.9 - 2005-04-23
28302 o Bugfixes on 0.0.9.x:
28303 - If unofficial Tor clients connect and send weird TLS certs, our
28304 Tor server triggers an assert. This release contains a minimal
28305 backport from the broader fix that we put into 0.1.0.4-rc.
28308 Changes in version 0.1.0.4-rc - 2005-04-23
28310 - If unofficial Tor clients connect and send weird TLS certs, our
28311 Tor server triggers an assert. Stop asserting, and start handling
28312 TLS errors better in other situations too.
28313 - When the controller asks us to tell it about all the debug-level
28314 logs, it turns out we were generating debug-level logs while
28315 telling it about them, which turns into a bad loop. Now keep
28316 track of whether you're sending a debug log to the controller,
28317 and don't log when you are.
28318 - Fix the "postdescriptor" feature of the controller interface: on
28319 non-complete success, only say "done" once.
28321 - Clients are now willing to load balance over up to 2mB, not 1mB,
28322 of advertised bandwidth capacity.
28323 - Add a NoPublish config option, so you can be a server (e.g. for
28324 testing running Tor servers in other Tor networks) without
28325 publishing your descriptor to the primary dirservers.
28328 Changes in version 0.1.0.3-rc - 2005-04-08
28329 o Improvements on 0.1.0.2-rc:
28330 - Client now retries when streams end early for 'hibernating' or
28331 'resource limit' reasons, rather than failing them.
28332 - More automated handling for dirserver operators:
28333 - Automatically approve nodes running 0.1.0.2-rc or later,
28334 now that the the reachability detection stuff is working.
28335 - Now we allow two unverified servers with the same nickname
28336 but different keys. But if a nickname is verified, only that
28337 nickname+key are allowed.
28338 - If you're an authdirserver connecting to an address:port,
28339 and it's not the OR you were expecting, forget about that
28340 descriptor. If he *was* the one you were expecting, then forget
28341 about all other descriptors for that address:port.
28342 - Allow servers to publish descriptors from 12 hours in the future.
28343 Corollary: only whine about clock skew from the dirserver if
28344 he's a trusted dirserver (since now even verified servers could
28345 have quite wrong clocks).
28346 - Adjust maximum skew and age for rendezvous descriptors: let skew
28347 be 48 hours rather than 90 minutes.
28348 - Efficiency improvements:
28349 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
28350 it much faster to look up a circuit for each relay cell.
28351 - Remove most calls to assert_all_pending_dns_resolves_ok(),
28352 since they're eating our cpu on exit nodes.
28353 - Stop wasting time doing a case insensitive comparison for every
28354 dns name every time we do any lookup. Canonicalize the names to
28355 lowercase and be done with it.
28356 - Start sending 'truncated' cells back rather than destroy cells,
28357 if the circuit closes in front of you. This means we won't have
28358 to abandon partially built circuits.
28359 - Only warn once per nickname from add_nickname_list_to_smartlist
28360 per failure, so an entrynode or exitnode choice that's down won't
28362 - Put a note in the torrc about abuse potential with the default
28364 - Revise control spec and implementation to allow all log messages to
28365 be sent to controller with their severities intact (suggested by
28366 Matt Edman). Update TorControl to handle new log event types.
28367 - Provide better explanation messages when controller's POSTDESCRIPTOR
28369 - Stop putting nodename in the Platform string in server descriptors.
28370 It doesn't actually help, and it is confusing/upsetting some people.
28372 o Bugfixes on 0.1.0.2-rc:
28373 - We were printing the host mask wrong in exit policies in server
28374 descriptors. This isn't a critical bug though, since we were still
28375 obeying the exit policy internally.
28376 - Fix Tor when compiled with libevent but without pthreads: move
28377 connection_unregister() from _connection_free() to
28379 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
28380 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
28381 when we look through the connection array, we'll find any of the
28382 cpu/dnsworkers. This is no good.
28384 o Bugfixes on 0.0.9.8:
28385 - Fix possible bug on threading platforms (e.g. win32) which was
28386 leaking a file descriptor whenever a cpuworker or dnsworker died.
28387 - When using preferred entry or exit nodes, ignore whether the
28388 circuit wants uptime or capacity. They asked for the nodes, they
28390 - chdir() to your datadirectory at the *end* of the daemonize process,
28391 not the beginning. This was a problem because the first time you
28392 run tor, if your datadir isn't there, and you have runasdaemon set
28393 to 1, it will try to chdir to it before it tries to create it. Oops.
28394 - Handle changed router status correctly when dirserver reloads
28395 fingerprint file. We used to be dropping all unverified descriptors
28396 right then. The bug was hidden because we would immediately
28397 fetch a directory from another dirserver, which would include the
28398 descriptors we just dropped.
28399 - When we're connecting to an OR and he's got a different nickname/key
28400 than we were expecting, only complain loudly if we're an OP or a
28401 dirserver. Complaining loudly to the OR admins just confuses them.
28402 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
28403 artificially capped at 500kB.
28406 Changes in version 0.0.9.8 - 2005-04-07
28407 o Bugfixes on 0.0.9.x:
28408 - We have a bug that I haven't found yet. Sometimes, very rarely,
28409 cpuworkers get stuck in the 'busy' state, even though the cpuworker
28410 thinks of itself as idle. This meant that no new circuits ever got
28411 established. Here's a workaround to kill any cpuworker that's been
28412 busy for more than 100 seconds.
28415 Changes in version 0.1.0.2-rc - 2005-04-01
28416 o Bugfixes on 0.1.0.1-rc:
28417 - Fixes on reachability detection:
28418 - Don't check for reachability while hibernating.
28419 - If ORPort is reachable but DirPort isn't, still publish the
28420 descriptor, but zero out DirPort until it's found reachable.
28421 - When building testing circs for ORPort testing, use only
28422 high-bandwidth nodes, so fewer circuits fail.
28423 - Complain about unreachable ORPort separately from unreachable
28424 DirPort, so the user knows what's going on.
28425 - Make sure we only conclude ORPort reachability if we didn't
28426 initiate the conn. Otherwise we could falsely conclude that
28427 we're reachable just because we connected to the guy earlier
28428 and he used that same pipe to extend to us.
28429 - Authdirservers shouldn't do ORPort reachability detection,
28430 since they're in clique mode, so it will be rare to find a
28431 server not already connected to them.
28432 - When building testing circuits, always pick middle hops running
28433 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
28434 bug. (This is a kludge; it will go away when 0.0.9.x becomes
28436 - When we decide we're reachable, actually publish our descriptor
28438 - Fix bug in redirectstream in the controller.
28439 - Fix the state descriptor strings so logs don't claim edge streams
28440 are in a different state than they actually are.
28441 - Use recent libevent features when possible (this only really affects
28442 win32 and osx right now, because the new libevent with these
28443 features hasn't been released yet). Add code to suppress spurious
28445 - Prevent possible segfault in connection_close_unattached_ap().
28446 - Fix newlines on torrc in win32.
28447 - Improve error msgs when tor-resolve fails.
28449 o Improvements on 0.0.9.x:
28450 - New experimental script tor/contrib/ExerciseServer.py (needs more
28451 work) that uses the controller interface to build circuits and
28452 fetch pages over them. This will help us bootstrap servers that
28453 have lots of capacity but haven't noticed it yet.
28454 - New experimental script tor/contrib/PathDemo.py (needs more work)
28455 that uses the controller interface to let you choose whole paths
28457 "<hostname>.<path,separated by dots>.<length of path>.path"
28458 - When we've connected to an OR and handshaked but didn't like
28459 the result, we were closing the conn without sending destroy
28460 cells back for pending circuits. Now send those destroys.
28463 Changes in version 0.0.9.7 - 2005-04-01
28464 o Bugfixes on 0.0.9.x:
28465 - Fix another race crash bug (thanks to Glenn Fink for reporting).
28466 - Compare identity to identity, not to nickname, when extending to
28467 a router not already in the directory. This was preventing us from
28468 extending to unknown routers. Oops.
28469 - Make sure to create OS X Tor user in <500 range, so we aren't
28470 creating actual system users.
28471 - Note where connection-that-hasn't-sent-end was marked, and fix
28472 a few really loud instances of this harmless bug (it's fixed more
28476 Changes in version 0.1.0.1-rc - 2005-03-28
28478 - Add reachability testing. Your Tor server will automatically try
28479 to see if its ORPort and DirPort are reachable from the outside,
28480 and it won't upload its descriptor until it decides they are.
28481 - Handle unavailable hidden services better. Handle slow or busy
28482 hidden services better.
28483 - Add support for CONNECTing through https proxies, with "HttpsProxy"
28485 - New exit policy: accept most low-numbered ports, rather than
28486 rejecting most low-numbered ports.
28487 - More Tor controller support (still experimental). See
28488 http://tor.eff.org/doc/control-spec.txt for all the new features,
28489 including signals to emulate unix signals from any platform;
28490 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
28491 closestream; closecircuit; etc.
28492 - Make nt services work and start on startup on win32 (based on
28493 patch by Matt Edman).
28494 - Add a new AddressMap config directive to rewrite incoming socks
28495 addresses. This lets you, for example, declare an implicit
28496 required exit node for certain sites.
28497 - Add a new TrackHostExits config directive to trigger addressmaps
28498 for certain incoming socks addresses -- for sites that break when
28499 your exit keeps changing (based on patch by Mike Perry).
28500 - Redo the client-side dns cache so it's just an addressmap too.
28501 - Notice when our IP changes, and reset stats/uptime/reachability.
28502 - When an application is using socks5, give him the whole variety of
28503 potential socks5 responses (connect refused, host unreachable, etc),
28504 rather than just "success" or "failure".
28505 - A more sane version numbering system. See
28506 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
28507 - New contributed script "exitlist": a simple python script to
28508 parse directories and find Tor nodes that exit to listed
28510 - New contributed script "privoxy-tor-toggle" to toggle whether
28511 Privoxy uses Tor. Seems to be configured for Debian by default.
28512 - Report HTTP reasons to client when getting a response from directory
28513 servers -- so you can actually know what went wrong.
28514 - New config option MaxAdvertisedBandwidth which lets you advertise
28515 a low bandwidthrate (to not attract as many circuits) while still
28516 allowing a higher bandwidthrate in reality.
28518 o Robustness/stability fixes:
28519 - Make Tor use Niels Provos's libevent instead of its current
28520 poll-but-sometimes-select mess. This will let us use faster async
28521 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
28523 - pthread support now too. This was forced because when we forked,
28524 we ended up wasting a lot of duplicate ram over time. Also switch
28525 to foo_r versions of some library calls to allow reentry and
28527 - Better handling for heterogeneous / unreliable nodes:
28528 - Annotate circuits w/ whether they aim to contain high uptime nodes
28529 and/or high capacity nodes. When building circuits, choose
28531 - This means that every single node in an intro rend circuit,
28532 not just the last one, will have a minimum uptime.
28533 - New config option LongLivedPorts to indicate application streams
28534 that will want high uptime circuits.
28535 - Servers reset uptime when a dir fetch entirely fails. This
28536 hopefully reflects stability of the server's network connectivity.
28537 - If somebody starts his tor server in Jan 2004 and then fixes his
28538 clock, don't make his published uptime be a year.
28539 - Reset published uptime when you wake up from hibernation.
28540 - Introduce a notion of 'internal' circs, which are chosen without
28541 regard to the exit policy of the last hop. Intro and rendezvous
28542 circs must be internal circs, to avoid leaking information. Resolve
28543 and connect streams can use internal circs if they want.
28544 - New circuit pooling algorithm: make sure to have enough circs around
28545 to satisfy any predicted ports, and also make sure to have 2 internal
28546 circs around if we've required internal circs lately (and with high
28547 uptime if we've seen that lately too).
28548 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
28549 which describes how often we retry making new circuits if current
28550 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
28551 how long we're willing to make use of an already-dirty circuit.
28552 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
28553 circ as necessary, if there are any completed ones lying around
28554 when we try to launch one.
28555 - Make hidden services try to establish a rendezvous for 30 seconds,
28556 rather than for n (where n=3) attempts to build a circuit.
28557 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
28558 "ShutdownWaitLength".
28559 - Try to be more zealous about calling connection_edge_end when
28560 things go bad with edge conns in connection.c.
28561 - Revise tor-spec to add more/better stream end reasons.
28562 - Revise all calls to connection_edge_end to avoid sending "misc",
28563 and to take errno into account where possible.
28566 - Fix a race condition that can trigger an assert, when we have a
28567 pending create cell and an OR connection fails right then.
28568 - Fix several double-mark-for-close bugs, e.g. where we were finding
28569 a conn for a cell even if that conn is already marked for close.
28570 - Make sequence of log messages when starting on win32 with no config
28571 file more reasonable.
28572 - When choosing an exit node for a new non-internal circ, don't take
28573 into account whether it'll be useful for any pending x.onion
28574 addresses -- it won't.
28575 - Turn addr_policy_compare from a tristate to a quadstate; this should
28576 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
28577 for google.com" problem.
28578 - Make "platform" string in descriptor more accurate for Win32 servers,
28579 so it's not just "unknown platform".
28580 - Fix an edge case in parsing config options (thanks weasel).
28581 If they say "--" on the commandline, it's not an option.
28582 - Reject odd-looking addresses at the client (e.g. addresses that
28583 contain a colon), rather than having the server drop them because
28585 - tor-resolve requests were ignoring .exit if there was a working circuit
28586 they could use instead.
28587 - REUSEADDR on normal platforms means you can rebind to the port
28588 right after somebody else has let it go. But REUSEADDR on win32
28589 means to let you bind to the port _even when somebody else
28590 already has it bound_! So, don't do that on Win32.
28591 - Change version parsing logic: a version is "obsolete" if it is not
28592 recommended and (1) there is a newer recommended version in the
28593 same series, or (2) there are no recommended versions in the same
28594 series, but there are some recommended versions in a newer series.
28595 A version is "new" if it is newer than any recommended version in
28597 - Stop most cases of hanging up on a socks connection without sending
28601 - Require BandwidthRate to be at least 20kB/s for servers.
28602 - When a dirserver causes you to give a warn, mention which dirserver
28604 - New config option DirAllowPrivateAddresses for authdirservers.
28605 Now by default they refuse router descriptors that have non-IP or
28606 private-IP addresses.
28607 - Stop publishing socksport in the directory, since it's not
28608 actually meant to be public. For compatibility, publish a 0 there
28610 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
28611 smart" value, that is low for servers and high for clients.
28612 - If our clock jumps forward by 100 seconds or more, assume something
28613 has gone wrong with our network and abandon all not-yet-used circs.
28614 - Warn when exit policy implicitly allows local addresses.
28615 - If we get an incredibly skewed timestamp from a dirserver mirror
28616 that isn't a verified OR, don't warn -- it's probably him that's
28618 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
28619 cookies to disk and doesn't log each web request to disk. (Thanks
28620 to Brett Carrington for pointing this out.)
28621 - When a client asks us for a dir mirror and we don't have one,
28622 launch an attempt to get a fresh one.
28623 - If we're hibernating and we get a SIGINT, exit immediately.
28624 - Add --with-dmalloc ./configure option, to track memory leaks.
28625 - And try to free all memory on closing, so we can detect what
28627 - Cache local dns resolves correctly even when they're .exit
28629 - Give a better warning when some other server advertises an
28630 ORPort that is actually an apache running ssl.
28631 - Add "opt hibernating 1" to server descriptor to make it clearer
28632 whether the server is hibernating.
28635 Changes in version 0.0.9.6 - 2005-03-24
28636 o Bugfixes on 0.0.9.x (crashes and asserts):
28637 - Add new end stream reasons to maintenance branch. Fix bug where
28638 reason (8) could trigger an assert. Prevent bug from recurring.
28639 - Apparently win32 stat wants paths to not end with a slash.
28640 - Fix assert triggers in assert_cpath_layer_ok(), where we were
28641 blowing away the circuit that conn->cpath_layer points to, then
28642 checking to see if the circ is well-formed. Backport check to make
28643 sure we dont use the cpath on a closed connection.
28644 - Prevent circuit_resume_edge_reading_helper() from trying to package
28645 inbufs for marked-for-close streams.
28646 - Don't crash on hup if your options->address has become unresolvable.
28647 - Some systems (like OS X) sometimes accept() a connection and tell
28648 you the remote host is 0.0.0.0:0. If this happens, due to some
28649 other mis-features, we get confused; so refuse the conn for now.
28651 o Bugfixes on 0.0.9.x (other):
28652 - Fix harmless but scary "Unrecognized content encoding" warn message.
28653 - Add new stream error reason: TORPROTOCOL reason means "you are not
28654 speaking a version of Tor I understand; say bye-bye to your stream."
28655 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
28656 into the future, now that we are more tolerant of skew. This
28657 resolves a bug where a Tor server would refuse to cache a directory
28658 because all the directories it gets are too far in the future;
28659 yet the Tor server never logs any complaints about clock skew.
28660 - Mac packaging magic: make man pages useable, and do not overwrite
28661 existing torrc files.
28662 - Make OS X log happily to /var/log/tor/tor.log
28665 Changes in version 0.0.9.5 - 2005-02-22
28666 o Bugfixes on 0.0.9.x:
28667 - Fix an assert race at exit nodes when resolve requests fail.
28668 - Stop picking unverified dir mirrors--it only leads to misery.
28669 - Patch from Matt Edman to make NT services work better. Service
28670 support is still not compiled into the executable by default.
28671 - Patch from Dmitri Bely so the Tor service runs better under
28672 the win32 SYSTEM account.
28673 - Make tor-resolve actually work (?) on Win32.
28674 - Fix a sign bug when getrlimit claims to have 4+ billion
28675 file descriptors available.
28676 - Stop refusing to start when bandwidthburst == bandwidthrate.
28677 - When create cells have been on the onion queue more than five
28678 seconds, just send back a destroy and take them off the list.
28681 Changes in version 0.0.9.4 - 2005-02-03
28682 o Bugfixes on 0.0.9:
28683 - Fix an assert bug that took down most of our servers: when
28684 a server claims to have 1 GB of bandwidthburst, don't
28686 - Don't crash as badly if we have spawned the max allowed number
28687 of dnsworkers, or we're out of file descriptors.
28688 - Block more file-sharing ports in the default exit policy.
28689 - MaxConn is now automatically set to the hard limit of max
28690 file descriptors we're allowed (ulimit -n), minus a few for
28692 - Give a clearer message when servers need to raise their
28693 ulimit -n when they start running out of file descriptors.
28694 - SGI Compatibility patches from Jan Schaumann.
28695 - Tolerate a corrupt cached directory better.
28696 - When a dirserver hasn't approved your server, list which one.
28697 - Go into soft hibernation after 95% of the bandwidth is used,
28698 not 99%. This is especially important for daily hibernators who
28699 have a small accounting max. Hopefully it will result in fewer
28700 cut connections when the hard hibernation starts.
28701 - Load-balance better when using servers that claim more than
28702 800kB/s of capacity.
28703 - Make NT services work (experimental, only used if compiled in).
28706 Changes in version 0.0.9.3 - 2005-01-21
28707 o Bugfixes on 0.0.9:
28708 - Backport the cpu use fixes from main branch, so busy servers won't
28709 need as much processor time.
28710 - Work better when we go offline and then come back, or when we
28711 run Tor at boot before the network is up. We do this by
28712 optimistically trying to fetch a new directory whenever an
28713 application request comes in and we think we're offline -- the
28714 human is hopefully a good measure of when the network is back.
28715 - Backport some minimal hidserv bugfixes: keep rend circuits open as
28716 long as you keep using them; actually publish hidserv descriptors
28717 shortly after they change, rather than waiting 20-40 minutes.
28718 - Enable Mac startup script by default.
28719 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
28720 - When you update AllowUnverifiedNodes or FirewallPorts via the
28721 controller's setconf feature, we were always appending, never
28723 - When you update HiddenServiceDir via setconf, it was screwing up
28724 the order of reading the lines, making it fail.
28725 - Do not rewrite a cached directory back to the cache; otherwise we
28726 will think it is recent and not fetch a newer one on startup.
28727 - Workaround for webservers that lie about Content-Encoding: Tor
28728 now tries to autodetect compressed directories and compression
28729 itself. This lets us Proxypass dir fetches through apache.
28732 Changes in version 0.0.9.2 - 2005-01-04
28733 o Bugfixes on 0.0.9 (crashes and asserts):
28734 - Fix an assert on startup when the disk is full and you're logging
28736 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
28737 style address, then we'd crash.
28738 - Fix an assert trigger when the running-routers string we get from
28739 a dirserver is broken.
28740 - Make worker threads start and run on win32. Now win32 servers
28742 - Bandaid (not actually fix, but now it doesn't crash) an assert
28743 where the dns worker dies mysteriously and the main Tor process
28744 doesn't remember anything about the address it was resolving.
28746 o Bugfixes on 0.0.9 (Win32):
28747 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
28748 name out of the warning/assert messages.
28749 - Fix a superficial "unhandled error on read" bug on win32.
28750 - The win32 installer no longer requires a click-through for our
28751 license, since our Free Software license grants rights but does not
28753 - Win32: When connecting to a dirserver fails, try another one
28754 immediately. (This was already working for non-win32 Tors.)
28755 - Stop trying to parse $HOME on win32 when hunting for default
28757 - Make tor-resolve.c work on win32 by calling network_init().
28759 o Bugfixes on 0.0.9 (other):
28760 - Make 0.0.9.x build on Solaris again.
28761 - Due to a fencepost error, we were blowing away the \n when reporting
28762 confvalue items in the controller. So asking for multiple config
28763 values at once couldn't work.
28764 - When listing circuits that are pending on an opening OR connection,
28765 if we're an OR we were listing circuits that *end* at us as
28766 being pending on every listener, dns/cpu worker, etc. Stop that.
28767 - Dirservers were failing to create 'running-routers' or 'directory'
28768 strings if we had more than some threshold of routers. Fix them so
28769 they can handle any number of routers.
28770 - Fix a superficial "Duplicate mark for close" bug.
28771 - Stop checking for clock skew for OR connections, even for servers.
28772 - Fix a fencepost error that was chopping off the last letter of any
28773 nickname that is the maximum allowed nickname length.
28774 - Update URLs in log messages so they point to the new website.
28775 - Fix a potential problem in mangling server private keys while
28776 writing to disk (not triggered yet, as far as we know).
28777 - Include the licenses for other free software we include in Tor,
28778 now that we're shipping binary distributions more regularly.
28781 Changes in version 0.0.9.1 - 2004-12-15
28782 o Bugfixes on 0.0.9:
28783 - Make hibernation actually work.
28784 - Make HashedControlPassword config option work.
28785 - When we're reporting event circuit status to a controller,
28786 don't use the stream status code.
28789 Changes in version 0.0.9 - 2004-12-12
28791 - Clean up manpage and torrc.sample file.
28792 - Clean up severities and text of log warnings.
28794 - Make servers trigger an assert when they enter hibernation.
28797 Changes in version 0.0.9rc7 - 2004-12-08
28798 o Bugfixes on 0.0.9rc:
28799 - Fix a stack-trashing crash when an exit node begins hibernating.
28800 - Avoid looking at unallocated memory while considering which
28801 ports we need to build circuits to cover.
28802 - Stop a sigpipe: when an 'end' cell races with eof from the app,
28803 we shouldn't hold-open-until-flush if the eof arrived first.
28804 - Fix a bug with init_cookie_authentication() in the controller.
28805 - When recommending new-format log lines, if the upper bound is
28806 LOG_ERR, leave it implicit.
28808 o Bugfixes on 0.0.8.1:
28809 - Fix a whole slew of memory leaks.
28810 - Fix isspace() and friends so they still make Solaris happy
28811 but also so they don't trigger asserts on win32.
28812 - Fix parse_iso_time on platforms without strptime (eg win32).
28813 - win32: tolerate extra "readable" events better.
28814 - win32: when being multithreaded, leave parent fdarray open.
28815 - Make unit tests work on win32.
28818 Changes in version 0.0.9rc6 - 2004-12-06
28819 o Bugfixes on 0.0.9pre:
28820 - Clean up some more integer underflow opportunities (not exploitable
28822 - While hibernating, hup should not regrow our listeners.
28823 - Send an end to the streams we close when we hibernate, rather
28824 than just chopping them off.
28825 - React to eof immediately on non-open edge connections.
28827 o Bugfixes on 0.0.8.1:
28828 - Calculate timeout for waiting for a connected cell from the time
28829 we sent the begin cell, not from the time the stream started. If
28830 it took a long time to establish the circuit, we would time out
28831 right after sending the begin cell.
28832 - Fix router_compare_addr_to_addr_policy: it was not treating a port
28833 of * as always matching, so we were picking reject *:* nodes as
28834 exit nodes too. Oops.
28837 - New circuit building strategy: keep a list of ports that we've
28838 used in the past 6 hours, and always try to have 2 circuits open
28839 or on the way that will handle each such port. Seed us with port
28840 80 so web users won't complain that Tor is "slow to start up".
28841 - Make kill -USR1 dump more useful stats about circuits.
28842 - When warning about retrying or giving up, print the address, so
28843 the user knows which one it's talking about.
28844 - If you haven't used a clean circuit in an hour, throw it away,
28845 just to be on the safe side. (This means after 6 hours a totally
28846 unused Tor client will have no circuits open.)
28849 Changes in version 0.0.9rc5 - 2004-12-01
28850 o Bugfixes on 0.0.8.1:
28851 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
28852 - Let resolve conns retry/expire also, rather than sticking around
28854 - If we are using select, make sure we stay within FD_SETSIZE.
28856 o Bugfixes on 0.0.9pre:
28857 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
28858 but doesn't seem to be currently; thanks to Ilja van Sprundel for
28860 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
28861 instead. Impose minima and maxima for all *Period options; impose
28862 even tighter maxima for fetching if we are a caching dirserver.
28863 Clip rather than rejecting.
28864 - Fetch cached running-routers from servers that serve it (that is,
28865 authdirservers and servers running 0.0.9rc5-cvs or later.)
28868 - Accept *:706 (silc) in default exit policy.
28869 - Implement new versioning format for post 0.1.
28870 - Support "foo.nickname.exit" addresses, to let Alice request the
28871 address "foo" as viewed by exit node "nickname". Based on a patch
28873 - Make tor --version --version dump the cvs Id of every file.
28876 Changes in version 0.0.9rc4 - 2004-11-28
28877 o Bugfixes on 0.0.8.1:
28878 - Make windows sockets actually non-blocking (oops), and handle
28879 win32 socket errors better.
28881 o Bugfixes on 0.0.9rc1:
28882 - Actually catch the -USR2 signal.
28885 Changes in version 0.0.9rc3 - 2004-11-25
28886 o Bugfixes on 0.0.8.1:
28887 - Flush the log file descriptor after we print "Tor opening log file",
28888 so we don't see those messages days later.
28890 o Bugfixes on 0.0.9rc1:
28891 - Make tor-resolve work again.
28892 - Avoid infinite loop in tor-resolve if tor hangs up on it.
28893 - Fix an assert trigger for clients/servers handling resolves.
28896 Changes in version 0.0.9rc2 - 2004-11-24
28897 o Bugfixes on 0.0.9rc1:
28898 - I broke socks5 support while fixing the eof bug.
28899 - Allow unitless bandwidths and intervals; they default to bytes
28901 - New servers don't start out hibernating; they are active until
28902 they run out of bytes, so they have a better estimate of how
28903 long it takes, and so their operators can know they're working.
28906 Changes in version 0.0.9rc1 - 2004-11-23
28907 o Bugfixes on 0.0.8.1:
28908 - Finally fix a bug that's been plaguing us for a year:
28909 With high load, circuit package window was reaching 0. Whenever
28910 we got a circuit-level sendme, we were reading a lot on each
28911 socket, but only writing out a bit. So we would eventually reach
28912 eof. This would be noticed and acted on even when there were still
28913 bytes sitting in the inbuf.
28914 - When poll() is interrupted, we shouldn't believe the revents values.
28916 o Bugfixes on 0.0.9pre6:
28917 - Fix hibernate bug that caused pre6 to be broken.
28918 - Don't keep rephist info for routers that haven't had activity for
28919 24 hours. (This matters now that clients have keys, since we track
28921 - Never call close_temp_logs while validating log options.
28922 - Fix backslash-escaping on tor.sh.in and torctl.in.
28925 - Implement weekly/monthly/daily accounting: now you specify your
28926 hibernation properties by
28927 AccountingMax N bytes|KB|MB|GB|TB
28928 AccountingStart day|week|month [day] HH:MM
28929 Defaults to "month 1 0:00".
28930 - Let bandwidth and interval config options be specified as 5 bytes,
28931 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
28932 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
28933 get back to normal.)
28934 - If your requested entry or exit node has advertised bandwidth 0,
28936 - Be more greedy about filling up relay cells -- we try reading again
28937 once we've processed the stuff we read, in case enough has arrived
28938 to fill the last cell completely.
28939 - Apply NT service patch from Osamu Fujino. Still needs more work.
28942 Changes in version 0.0.9pre6 - 2004-11-15
28943 o Bugfixes on 0.0.8.1:
28944 - Fix assert failure on malformed socks4a requests.
28945 - Use identity comparison, not nickname comparison, to choose which
28946 half of circuit-ID-space each side gets to use. This is needed
28947 because sometimes we think of a router as a nickname, and sometimes
28948 as a hex ID, and we can't predict what the other side will do.
28949 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
28950 write() call will fail and we handle it there.
28951 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
28952 and smartlist_len, which are two major profiling offenders.
28954 o Bugfixes on 0.0.9pre5:
28955 - Fix a bug in read_all that was corrupting config files on windows.
28956 - When we're raising the max number of open file descriptors to
28957 'unlimited', don't log that we just raised it to '-1'.
28958 - Include event code with events, as required by control-spec.txt.
28959 - Don't give a fingerprint when clients do --list-fingerprint:
28960 it's misleading, because it will never be the same again.
28961 - Stop using strlcpy in tor_strndup, since it was slowing us
28963 - Remove warn on startup about missing cached-directory file.
28964 - Make kill -USR1 work again.
28965 - Hibernate if we start tor during the "wait for wakeup-time" phase
28966 of an accounting interval. Log our hibernation plans better.
28967 - Authoritative dirservers now also cache their directory, so they
28968 have it on start-up.
28971 - Fetch running-routers; cache running-routers; compress
28972 running-routers; serve compressed running-routers.z
28973 - Add NSI installer script contributed by J Doe.
28974 - Commit VC6 and VC7 workspace/project files.
28975 - Commit a tor.spec for making RPM files, with help from jbash.
28976 - Add contrib/torctl.in contributed by Glenn Fink.
28977 - Implement the control-spec's SAVECONF command, to write your
28978 configuration to torrc.
28979 - Get cookie authentication for the controller closer to working.
28980 - Include control-spec.txt in the tarball.
28981 - When set_conf changes our server descriptor, upload a new copy.
28982 But don't upload it too often if there are frequent changes.
28983 - Document authentication config in man page, and document signals
28985 - Clean up confusing parts of man page and torrc.sample.
28986 - Make expand_filename handle ~ and ~username.
28987 - Use autoconf to enable largefile support where necessary. Use
28988 ftello where available, since ftell can fail at 2GB.
28989 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
28990 log more informatively.
28991 - Give a slightly more useful output for "tor -h".
28992 - Refuse application socks connections to port 0.
28993 - Check clock skew for verified servers, but allow unverified
28994 servers and clients to have any clock skew.
28995 - Break DirFetchPostPeriod into:
28996 - DirFetchPeriod for fetching full directory,
28997 - StatusFetchPeriod for fetching running-routers,
28998 - DirPostPeriod for posting server descriptor,
28999 - RendPostPeriod for posting hidden service descriptors.
29000 - Make sure the hidden service descriptors are at a random offset
29001 from each other, to hinder linkability.
29004 Changes in version 0.0.9pre5 - 2004-11-09
29005 o Bugfixes on 0.0.9pre4:
29006 - Fix a seg fault in unit tests (doesn't affect main program).
29007 - Fix an assert bug where a hidden service provider would fail if
29008 the first hop of his rendezvous circuit was down.
29009 - Hidden service operators now correctly handle version 1 style
29010 INTRODUCE1 cells (nobody generates them still, so not a critical
29012 - If do_hup fails, actually notice.
29013 - Handle more errnos from accept() without closing the listener.
29014 Some OpenBSD machines were closing their listeners because
29015 they ran out of file descriptors.
29016 - Send resolve cells to exit routers that are running a new
29017 enough version of the resolve code to work right.
29018 - Better handling of winsock includes on non-MSV win32 compilers.
29019 - Some people had wrapped their tor client/server in a script
29020 that would restart it whenever it died. This did not play well
29021 with our "shut down if your version is obsolete" code. Now people
29022 don't fetch a new directory if their local cached version is
29024 - Make our autogen.sh work on ksh as well as bash.
29027 - Hibernation: New config option "AccountingMaxKB" lets you
29028 set how many KBytes per month you want to allow your server to
29029 consume. Rather than spreading those bytes out evenly over the
29030 month, we instead hibernate for some of the month and pop up
29031 at a deterministic time, work until the bytes are consumed, then
29032 hibernate again. Config option "MonthlyAccountingStart" lets you
29033 specify which day of the month your billing cycle starts on.
29034 - Control interface: a separate program can now talk to your
29035 client/server over a socket, and get/set config options, receive
29036 notifications of circuits and streams starting/finishing/dying,
29037 bandwidth used, etc. The next step is to get some GUIs working.
29038 Let us know if you want to help out. See doc/control-spec.txt .
29039 - Ship a contrib/tor-control.py as an example script to interact
29040 with the control port.
29041 - "tor --hash-password zzyxz" will output a salted password for
29042 use in authenticating to the control interface.
29043 - New log format in config:
29044 "Log minsev[-maxsev] stdout|stderr|syslog" or
29045 "Log minsev[-maxsev] file /var/foo"
29048 - DirPolicy config option, to let people reject incoming addresses
29049 from their dirserver.
29050 - "tor --list-fingerprint" will list your identity key fingerprint
29052 - Add "pass" target for RedirectExit, to make it easier to break
29053 out of a sequence of RedirectExit rules.
29054 - Clients now generate a TLS cert too, in preparation for having
29055 them act more like real nodes.
29056 - Ship src/win32/ in the tarball, so people can use it to build.
29057 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
29059 - New "router-status" line in directory, to better bind each verified
29060 nickname to its identity key.
29061 - Deprecate unofficial config option abbreviations, and abbreviations
29062 not on the command line.
29063 - Add a pure-C tor-resolve implementation.
29064 - Use getrlimit and friends to ensure we can reach MaxConn (currently
29065 1024) file descriptors.
29067 o Code security improvements, inspired by Ilja:
29068 - Replace sprintf with snprintf. (I think they were all safe, but
29070 - Replace strcpy/strncpy with strlcpy in more places.
29071 - Avoid strcat; use snprintf or strlcat instead.
29072 - snprintf wrapper with consistent (though not C99) overflow behavior.
29075 Changes in version 0.0.9pre4 - 2004-10-17
29076 o Bugfixes on 0.0.9pre3:
29077 - If the server doesn't specify an exit policy, use the real default
29078 exit policy, not reject *:*.
29079 - Ignore fascistfirewall when uploading/downloading hidden service
29080 descriptors, since we go through Tor for those; and when using
29081 an HttpProxy, since we assume it can reach them all.
29082 - When looking for an authoritative dirserver, use only the ones
29083 configured at boot. Don't bother looking in the directory.
29084 - The rest of the fix for get_default_conf_file() on older win32.
29085 - Make 'Routerfile' config option obsolete.
29088 - New 'MyFamily nick1,...' config option for a server to
29089 specify other servers that shouldn't be used in the same circuit
29090 with it. Only believed if nick1 also specifies us.
29091 - New 'NodeFamily nick1,nick2,...' config option for a client to
29092 specify nodes that it doesn't want to use in the same circuit.
29093 - New 'Redirectexit pattern address:port' config option for a
29094 server to redirect exit connections, e.g. to a local squid.
29097 Changes in version 0.0.9pre3 - 2004-10-13
29098 o Bugfixes on 0.0.8.1:
29099 - Better torrc example lines for dirbindaddress and orbindaddress.
29100 - Improved bounds checking on parsed ints (e.g. config options and
29101 the ones we find in directories.)
29102 - Better handling of size_t vs int, so we're more robust on 64
29104 - Fix the rest of the bug where a newly started OR would appear
29105 as unverified even after we've added his fingerprint and hupped
29107 - Fix a bug from 0.0.7: when read() failed on a stream, we would
29108 close it without sending back an end. So 'connection refused'
29109 would simply be ignored and the user would get no response.
29111 o Bugfixes on 0.0.9pre2:
29112 - Serving the cached-on-disk directory to people is bad. We now
29113 provide no directory until we've fetched a fresh one.
29114 - Workaround for bug on windows where cached-directories get crlf
29116 - Make get_default_conf_file() work on older windows too.
29117 - If we write a *:* exit policy line in the descriptor, don't write
29118 any more exit policy lines.
29121 - Use only 0.0.9pre1 and later servers for resolve cells.
29122 - Make the dirservers file obsolete.
29123 - Include a dir-signing-key token in directories to tell the
29124 parsing entity which key is being used to sign.
29125 - Remove the built-in bulky default dirservers string.
29126 - New config option "Dirserver %s:%d [fingerprint]", which can be
29127 repeated as many times as needed. If no dirservers specified,
29128 default to moria1,moria2,tor26.
29129 - Make moria2 advertise a dirport of 80, so people behind firewalls
29130 will be able to get a directory.
29131 - Http proxy support
29132 - Dirservers translate requests for http://%s:%d/x to /x
29133 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
29134 be routed through this host.
29135 - Clients ask for /tor/x rather than /x for new enough dirservers.
29136 This way we can one day coexist peacefully with apache.
29137 - Clients specify a "Host: %s%d" http header, to be compatible
29138 with more proxies, and so running squid on an exit node can work.
29141 Changes in version 0.0.8.1 - 2004-10-13
29143 - Fix a seg fault that can be triggered remotely for Tor
29144 clients/servers with an open dirport.
29145 - Fix a rare assert trigger, where routerinfos for entries in
29146 our cpath would expire while we're building the path.
29147 - Fix a bug in OutboundBindAddress so it (hopefully) works.
29148 - Fix a rare seg fault for people running hidden services on
29149 intermittent connections.
29150 - Fix a bug in parsing opt keywords with objects.
29151 - Fix a stale pointer assert bug when a stream detaches and
29153 - Fix a string format vulnerability (probably not exploitable)
29154 in reporting stats locally.
29155 - Fix an assert trigger: sometimes launching circuits can fail
29156 immediately, e.g. because too many circuits have failed recently.
29157 - Fix a compile warning on 64 bit platforms.
29160 Changes in version 0.0.9pre2 - 2004-10-03
29162 - Make fetching a cached directory work for 64-bit platforms too.
29163 - Make zlib.h a required header, not an optional header.
29166 Changes in version 0.0.9pre1 - 2004-10-01
29168 - Stop using separate defaults for no-config-file and
29169 empty-config-file. Now you have to explicitly turn off SocksPort,
29170 if you don't want it open.
29171 - Fix a bug in OutboundBindAddress so it (hopefully) works.
29172 - Improve man page to mention more of the 0.0.8 features.
29173 - Fix a rare seg fault for people running hidden services on
29174 intermittent connections.
29175 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
29177 - Fix more dns related bugs: send back resolve_failed and end cells
29178 more reliably when the resolve fails, rather than closing the
29179 circuit and then trying to send the cell. Also attach dummy resolve
29180 connections to a circuit *before* calling dns_resolve(), to fix
29181 a bug where cached answers would never be sent in RESOLVED cells.
29182 - When we run out of disk space, or other log writing error, don't
29183 crash. Just stop logging to that log and continue.
29184 - We were starting to daemonize before we opened our logs, so if
29185 there were any problems opening logs, we would complain to stderr,
29186 which wouldn't work, and then mysteriously exit.
29187 - Fix a rare bug where sometimes a verified OR would connect to us
29188 before he'd uploaded his descriptor, which would cause us to
29189 assign conn->nickname as though he's unverified. Now we look through
29190 the fingerprint list to see if he's there.
29191 - Fix a rare assert trigger, where routerinfos for entries in
29192 our cpath would expire while we're building the path.
29195 - Clients can ask dirservers for /dir.z to get a compressed version
29196 of the directory. Only works for servers running 0.0.9, of course.
29197 - Make clients cache directories and use them to seed their router
29198 lists at startup. This means clients have a datadir again.
29199 - Configuration infrastructure support for warning on obsolete
29201 - Respond to content-encoding headers by trying to uncompress as
29203 - Reply with a deflated directory when a client asks for "dir.z".
29204 We could use allow-encodings instead, but allow-encodings isn't
29205 specified in HTTP 1.0.
29206 - Raise the max dns workers from 50 to 100.
29207 - Discourage people from setting their dirfetchpostperiod more often
29208 than once per minute.
29209 - Protect dirservers from overzealous descriptor uploading -- wait
29210 10 seconds after directory gets dirty, before regenerating.
29213 Changes in version 0.0.8 - 2004-08-25
29214 o Port it to SunOS 5.9 / Athena
29217 Changes in version 0.0.8rc2 - 2004-08-20
29218 o Make it compile on cygwin again.
29219 o When picking unverified routers, skip those with low uptime and/or
29220 low bandwidth, depending on what properties you care about.
29223 Changes in version 0.0.8rc1 - 2004-08-18
29224 o Changes from 0.0.7.3:
29226 - Fix assert triggers: if the other side returns an address 0.0.0.0,
29227 don't put it into the client dns cache.
29228 - If a begin failed due to exit policy, but we believe the IP address
29229 should have been allowed, switch that router to exitpolicy reject *:*
29230 until we get our next directory.
29232 - Clients choose nodes proportional to advertised bandwidth.
29233 - Avoid using nodes with low uptime as introduction points.
29234 - Handle servers with dynamic IP addresses: don't replace
29235 options->Address with the resolved one at startup, and
29236 detect our address right before we make a routerinfo each time.
29237 - 'FascistFirewall' option to pick dirservers and ORs on specific
29238 ports; plus 'FirewallPorts' config option to tell FascistFirewall
29239 which ports are open. (Defaults to 80,443)
29240 - Be more aggressive about trying to make circuits when the network
29241 has changed (e.g. when you unsuspend your laptop).
29242 - Check for time skew on http headers; report date in response to
29244 - If the entrynode config line has only one node, don't pick it as
29246 - Add strict{entry|exit}nodes config options. If set to 1, then
29247 we refuse to build circuits that don't include the specified entry
29249 - OutboundBindAddress config option, to bind to a specific
29250 IP address for outgoing connect()s.
29251 - End truncated log entries (e.g. directories) with "[truncated]".
29253 o Patches to 0.0.8preX:
29255 - Patches to compile and run on win32 again (maybe)?
29256 - Fix crash when looking for ~/.torrc with no $HOME set.
29257 - Fix a race bug in the unit tests.
29258 - Handle verified/unverified name collisions better when new
29259 routerinfo's arrive in a directory.
29260 - Sometimes routers were getting entered into the stats before
29261 we'd assigned their identity_digest. Oops.
29262 - Only pick and establish intro points after we've gotten a
29265 - AllowUnverifiedNodes config option to let circuits choose no-name
29266 routers in entry,middle,exit,introduction,rendezvous positions.
29267 Allow middle and rendezvous positions by default.
29268 - Add a man page for tor-resolve.
29271 Changes in version 0.0.7.3 - 2004-08-12
29272 o Stop dnsworkers from triggering an assert failure when you
29273 ask them to resolve the host "".
29276 Changes in version 0.0.8pre3 - 2004-08-09
29277 o Changes from 0.0.7.2:
29278 - Allow multiple ORs with same nickname in routerlist -- now when
29279 people give us one identity key for a nickname, then later
29280 another, we don't constantly complain until the first expires.
29281 - Remember used bandwidth (both in and out), and publish 15-minute
29282 snapshots for the past day into our descriptor.
29283 - You can now fetch $DIRURL/running-routers to get just the
29284 running-routers line, not the whole descriptor list. (But
29285 clients don't use this yet.)
29286 - When people mistakenly use Tor as an http proxy, point them
29287 at the tor-doc.html rather than the INSTALL.
29288 - Remove our mostly unused -- and broken -- hex_encode()
29289 function. Use base16_encode() instead. (Thanks to Timo Lindfors
29290 for pointing out this bug.)
29291 - Rotate onion keys every 12 hours, not every 2 hours, so we have
29292 fewer problems with people using the wrong key.
29293 - Change the default exit policy to reject the default edonkey,
29294 kazaa, gnutella ports.
29295 - Add replace_file() to util.[ch] to handle win32's rename().
29297 o Changes from 0.0.8preX:
29298 - Fix two bugs in saving onion keys to disk when rotating, so
29299 hopefully we'll get fewer people using old onion keys.
29300 - Fix an assert error that was making SocksPolicy not work.
29301 - Be willing to expire routers that have an open dirport -- it's
29302 just the authoritative dirservers we want to not forget.
29303 - Reject tor-resolve requests for .onion addresses early, so we
29304 don't build a whole rendezvous circuit and then fail.
29305 - When you're warning a server that he's unverified, don't cry
29306 wolf unpredictably.
29307 - Fix a race condition: don't try to extend onto a connection
29308 that's still handshaking.
29309 - For servers in clique mode, require the conn to be open before
29310 you'll choose it for your path.
29311 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
29312 end relay cell, etc.
29313 - Measure bandwidth capacity over the last 24 hours, not just 12
29314 - Bugfix: authoritative dirservers were making and signing a new
29315 directory for each client, rather than reusing the cached one.
29318 Changes in version 0.0.8pre2 - 2004-08-04
29319 o Changes from 0.0.7.2:
29321 - Check directory signature _before_ you decide whether you're
29322 you're running an obsolete version and should exit.
29323 - Check directory signature _before_ you parse the running-routers
29324 list to decide who's running or verified.
29325 - Bugfixes and features:
29326 - Check return value of fclose while writing to disk, so we don't
29327 end up with broken files when servers run out of disk space.
29328 - Log a warning if the user uses an unsafe socks variant, so people
29329 are more likely to learn about privoxy or socat.
29330 - Dirservers now include RFC1123-style dates in the HTTP headers,
29331 which one day we will use to better detect clock skew.
29333 o Changes from 0.0.8pre1:
29334 - Make it compile without warnings again on win32.
29335 - Log a warning if you're running an unverified server, to let you
29336 know you might want to get it verified.
29337 - Only pick a default nickname if you plan to be a server.
29340 Changes in version 0.0.8pre1 - 2004-07-23
29342 - Made our unit tests compile again on OpenBSD 3.5, and tor
29343 itself compile again on OpenBSD on a sparc64.
29344 - We were neglecting milliseconds when logging on win32, so
29345 everything appeared to happen at the beginning of each second.
29347 o Protocol changes:
29348 - 'Extend' relay cell payloads now include the digest of the
29349 intended next hop's identity key. Now we can verify that we're
29350 extending to the right router, and also extend to routers we
29351 hadn't heard of before.
29354 - Tor nodes can now act as relays (with an advertised ORPort)
29355 without being manually verified by the dirserver operators.
29356 - Uploaded descriptors of unverified routers are now accepted
29357 by the dirservers, and included in the directory.
29358 - Verified routers are listed by nickname in the running-routers
29359 list; unverified routers are listed as "$<fingerprint>".
29360 - We now use hash-of-identity-key in most places rather than
29361 nickname or addr:port, for improved security/flexibility.
29362 - To avoid Sybil attacks, paths still use only verified servers.
29363 But now we have a chance to play around with hybrid approaches.
29364 - Nodes track bandwidth usage to estimate capacity (not used yet).
29365 - ClientOnly option for nodes that never want to become servers.
29366 - Directory caching.
29367 - "AuthoritativeDir 1" option for the official dirservers.
29368 - Now other nodes (clients and servers) will cache the latest
29369 directory they've pulled down.
29370 - They can enable their DirPort to serve it to others.
29371 - Clients will pull down a directory from any node with an open
29372 DirPort, and check the signature/timestamp correctly.
29373 - Authoritative dirservers now fetch directories from other
29374 authdirservers, to stay better synced.
29375 - Running-routers list tells who's down also, along with noting
29376 if they're verified (listed by nickname) or unverified (listed
29378 - Allow dirservers to serve running-router list separately.
29379 This isn't used yet.
29380 - ORs connect-on-demand to other ORs
29381 - If you get an extend cell to an OR you're not connected to,
29382 connect, handshake, and forward the create cell.
29383 - The authoritative dirservers stay connected to everybody,
29384 and everybody stays connected to 0.0.7 servers, but otherwise
29385 clients/servers expire unused connections after 5 minutes.
29386 - When servers get a sigint, they delay 30 seconds (refusing new
29387 connections) then exit. A second sigint causes immediate exit.
29388 - File and name management:
29389 - Look for .torrc if no CONFDIR "torrc" is found.
29390 - If no datadir is defined, then choose, make, and secure ~/.tor
29392 - If torrc not found, exitpolicy reject *:*.
29393 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
29394 - If no nickname is defined, derive default from hostname.
29395 - Rename secret key files, e.g. identity.key -> secret_id_key,
29396 to discourage people from mailing their identity key to tor-ops.
29397 - Refuse to build a circuit before the directory has arrived --
29398 it won't work anyway, since you won't know the right onion keys
29400 - Try other dirservers immediately if the one you try is down. This
29401 should tolerate down dirservers better now.
29402 - Parse tor version numbers so we can do an is-newer-than check
29403 rather than an is-in-the-list check.
29404 - New socks command 'resolve', to let us shim gethostbyname()
29406 - A 'tor_resolve' script to access the socks resolve functionality.
29407 - A new socks-extensions.txt doc file to describe our
29408 interpretation and extensions to the socks protocols.
29409 - Add a ContactInfo option, which gets published in descriptor.
29410 - Publish OR uptime in descriptor (and thus in directory) too.
29411 - Write tor version at the top of each log file
29412 - New docs in the tarball:
29414 - Document that you should proxy your SSL traffic too.
29417 Changes in version 0.0.7.2 - 2004-07-07
29418 o A better fix for the 0.0.0.0 problem, that will hopefully
29419 eliminate the remaining related assertion failures.
29422 Changes in version 0.0.7.1 - 2004-07-04
29423 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
29424 since internally we use 0.0.0.0 to signify "not yet resolved".
29427 Changes in version 0.0.7 - 2004-06-07
29428 o Updated the man page to reflect the new features.
29431 Changes in version 0.0.7rc2 - 2004-06-06
29432 o Changes from 0.0.7rc1:
29433 - Make it build on Win32 again.
29434 o Changes from 0.0.6.2:
29435 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
29439 Changes in version 0.0.7rc1 - 2004-06-02
29441 - On sighup, we were adding another log without removing the first
29442 one. So log messages would get duplicated n times for n sighups.
29443 - Several cases of using a connection after we'd freed it. The
29444 problem was that connections that are pending resolve are in both
29445 the pending_resolve tree, and also the circuit's resolving_streams
29446 list. When you want to remove one, you must remove it from both.
29447 - Fix a double-mark-for-close where an end cell arrived for a
29448 resolving stream, and then the resolve failed.
29449 - Check directory signatures based on name of signer, not on whom
29450 we got the directory from. This will let us cache directories more
29453 - Crank up some of our constants to handle more users.
29456 Changes in version 0.0.7pre1 - 2004-06-02
29457 o Fixes for crashes and other obnoxious bugs:
29458 - Fix an epipe bug: sometimes when directory connections failed
29459 to connect, we would give them a chance to flush before closing
29461 - When we detached from a circuit because of resolvefailed, we
29462 would immediately try the same circuit twice more, and then
29463 give up on the resolve thinking we'd tried three different
29465 - Limit the number of intro circuits we'll attempt to build for a
29466 hidden service per 15-minute period.
29467 - Check recommended-software string *early*, before actually parsing
29468 the directory. Thus we can detect an obsolete version and exit,
29469 even if the new directory format doesn't parse.
29470 o Fixes for security bugs:
29471 - Remember which nodes are dirservers when you startup, and if a
29472 random OR enables his dirport, don't automatically assume he's
29473 a trusted dirserver.
29475 - Directory connections were asking the wrong poll socket to
29476 start writing, and not asking themselves to start writing.
29477 - When we detached from a circuit because we sent a begin but
29478 didn't get a connected, we would use it again the first time;
29479 but after that we would correctly switch to a different one.
29480 - Stop warning when the first onion decrypt attempt fails; they
29481 will sometimes legitimately fail now that we rotate keys.
29482 - Override unaligned-access-ok check when $host_cpu is ia64 or
29483 arm. Apparently they allow it but the kernel whines.
29484 - Dirservers try to reconnect periodically too, in case connections
29486 - Fix some memory leaks in directory servers.
29487 - Allow backslash in Win32 filenames.
29488 - Made Tor build complain-free on FreeBSD, hopefully without
29489 breaking other BSD builds. We'll see.
29491 - Doxygen markup on all functions and global variables.
29492 - Make directory functions update routerlist, not replace it. So
29493 now directory disagreements are not so critical a problem.
29494 - Remove the upper limit on number of descriptors in a dirserver's
29495 directory (not that we were anywhere close).
29496 - Allow multiple logfiles at different severity ranges.
29497 - Allow *BindAddress to specify ":port" rather than setting *Port
29498 separately. Allow multiple instances of each BindAddress config
29499 option, so you can bind to multiple interfaces if you want.
29500 - Allow multiple exit policy lines, which are processed in order.
29501 Now we don't need that huge line with all the commas in it.
29502 - Enable accept/reject policies on SOCKS connections, so you can bind
29503 to 0.0.0.0 but still control who can use your OP.
29506 Changes in version 0.0.6.2 - 2004-05-16
29507 o Our integrity-checking digest was checking only the most recent cell,
29508 not the previous cells like we'd thought.
29509 Thanks to Stefan Mark for finding the flaw!
29512 Changes in version 0.0.6.1 - 2004-05-06
29513 o Fix two bugs in our AES counter-mode implementation (this affected
29514 onion-level stream encryption, but not TLS-level). It turns
29515 out we were doing something much more akin to a 16-character
29516 polyalphabetic cipher. Oops.
29517 Thanks to Stefan Mark for finding the flaw!
29518 o Retire moria3 as a directory server, and add tor26 as a directory
29522 Changes in version 0.0.6 - 2004-05-02
29523 [version bump only]
29526 Changes in version 0.0.6rc4 - 2004-05-01
29527 o Update the built-in dirservers list to use the new directory format
29528 o Fix a rare seg fault: if a node offering a hidden service attempts
29529 to build a circuit to Alice's rendezvous point and fails before it
29530 reaches the last hop, it retries with a different circuit, but
29532 o Handle windows socket errors correctly.
29535 Changes in version 0.0.6rc3 - 2004-04-28
29536 o Don't expire non-general excess circuits (if we had enough
29537 circuits open, we were expiring rendezvous circuits -- even
29538 when they had a stream attached. oops.)
29539 o Fetch randomness from /dev/urandom better (not via fopen/fread)
29540 o Better debugging for tls errors
29541 o Some versions of openssl have an SSL_pending function that erroneously
29542 returns bytes when there is a non-application record pending.
29543 o Set Content-Type on the directory and hidserv descriptor.
29544 o Remove IVs from cipher code, since AES-ctr has none.
29545 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
29546 o We were using an array of length zero in a few places.
29547 o win32's gethostbyname can't resolve an IP to an IP.
29548 o win32's close can't close a socket.
29551 Changes in version 0.0.6rc2 - 2004-04-26
29552 o Fix a bug where we were closing tls connections intermittently.
29553 It turns out openssl keeps its errors around -- so if an error
29554 happens, and you don't ask about it, and then another openssl
29555 operation happens and succeeds, and you ask if there was an error,
29556 it tells you about the first error. Fun fun.
29557 o Fix a bug that's been lurking since 27 may 03 (!)
29558 When passing back a destroy cell, we would use the wrong circ id.
29559 'Mostly harmless', but still worth fixing.
29560 o Since we don't support truncateds much, don't bother sending them;
29561 just close the circ.
29562 o check for <machine/limits.h> so we build on NetBSD again (I hope).
29563 o don't crash if a conn that sent a begin has suddenly lost its circuit
29564 (this was quite rare).
29567 Changes in version 0.0.6rc1 - 2004-04-25
29568 o We now rotate link (tls context) keys and onion keys.
29569 o CREATE cells now include oaep padding, so you can tell
29570 if you decrypted them correctly.
29571 o Add bandwidthburst to server descriptor.
29572 o Directories now say which dirserver signed them.
29573 o Use a tor_assert macro that logs failed assertions too.
29576 Changes in version 0.0.6pre5 - 2004-04-18
29577 o changes from 0.0.6pre4:
29578 - make tor build on broken freebsd 5.2 installs
29579 - fix a failed assert when you try an intro point, get a nack, and try
29580 a second one and it works.
29581 - when alice uses a port that the hidden service doesn't accept,
29582 it now sends back an end cell (denied by exit policy). otherwise
29583 alice would just have to wait to time out.
29584 - fix another rare bug: when we had tried all the intro
29585 points for a hidden service, we fetched the descriptor
29586 again, but we left our introcirc thinking it had already
29587 sent an intro, so it kept waiting for a response...
29588 - bugfix: when you sleep your hidden-service laptop, as soon
29589 as it wakes up it tries to upload a service descriptor, but
29590 socketpair fails for some reason (localhost not up yet?).
29591 now we simply give up on that upload, and we'll try again later.
29592 i'd still like to find the bug though.
29593 - if an intro circ waiting for an ack dies before getting one, then
29595 - we were reusing stale service descriptors and refetching usable
29599 Changes in version 0.0.6pre4 - 2004-04-14
29600 o changes from 0.0.6pre3:
29601 - when bob fails to connect to the rendezvous point, and his
29602 circ didn't fail because of the rendezvous point itself, then
29603 he retries a couple of times
29604 - we expire introduction and rendezvous circs more thoroughly
29605 (sometimes they were hanging around forever)
29606 - we expire unattached rendezvous streams that have been around
29607 too long (they were sticking around forever).
29608 - fix a measly fencepost error that was crashing everybody with
29612 Changes in version 0.0.6pre3 - 2004-04-14
29613 o changes from 0.0.6pre2:
29614 - make hup work again
29615 - fix some memory leaks for dirservers
29616 - allow more skew in rendezvous descriptor timestamps, to help
29617 handle people like blanu who don't know what time it is
29618 - normal circs are 3 hops, but some rend/intro circs are 4, if
29619 the initiator doesn't get to choose the last hop
29620 - send acks for introductions, so alice can know whether to try
29622 - bob publishes intro points more correctly
29623 o changes from 0.0.5:
29624 - fix an assert trigger that's been plaguing us since the days
29625 of 0.0.2prexx (thanks weasel!)
29626 - retry stream correctly when we fail to connect because of
29627 exit-policy-reject (should try another) or can't-resolve-address
29628 (also should try another, because dns on random internet servers
29630 - when we hup a dirserver and we've *removed* a server from the
29631 approved-routers list, now we remove that server from the
29632 in-memory directories too
29635 Changes in version 0.0.6pre2 - 2004-04-08
29636 o We fixed our base32 implementation. Now it works on all architectures.
29639 Changes in version 0.0.6pre1 - 2004-04-08
29641 - Hidden services and rendezvous points are implemented. Go to
29642 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
29643 hidden services. (This only works via a socks4a proxy such as
29644 Privoxy, and currently it's quite slow.)
29647 Changes in version 0.0.5 - 2004-03-30
29648 [version bump only]
29651 Changes in version 0.0.5rc3 - 2004-03-29
29652 o Install torrc as torrc.sample -- we no longer clobber your
29654 o Re-enable recommendedversion checking (we broke it in rc2, oops)
29655 o Add in a 'notice' log level for things the operator should hear
29656 but that aren't warnings
29659 Changes in version 0.0.5rc2 - 2004-03-29
29660 o Hold socks connection open until reply is flushed (if possible)
29661 o Make exit nodes resolve IPs to IPs immediately, rather than asking
29662 the dns farm to do it.
29663 o Fix c99 aliasing warnings in rephist.c
29664 o Don't include server descriptors that are older than 24 hours in the
29666 o Give socks 'reject' replies their whole 15s to attempt to flush,
29667 rather than seeing the 60s timeout and assuming the flush had failed.
29668 o Clean automake droppings from the cvs repository
29671 Changes in version 0.0.5rc1 - 2004-03-28
29672 o Fix mangled-state bug in directory fetching (was causing sigpipes).
29673 o Only build circuits after we've fetched the directory: clients were
29674 using only the directory servers before they'd fetched a directory.
29675 This also means longer startup time; so it goes.
29676 o Fix an assert trigger where an OP would fail to handshake, and we'd
29677 expect it to have a nickname.
29678 o Work around a tsocks bug: do a socks reject when AP connection dies
29679 early, else tsocks goes into an infinite loop.
29682 Changes in version 0.0.4 - 2004-03-26
29683 o When connecting to a dirserver or OR and the network is down,
29687 Changes in version 0.0.3 - 2004-03-26
29688 o Warn and fail if server chose a nickname with illegal characters
29689 o Port to Solaris and Sparc:
29690 - include missing header fcntl.h
29691 - have autoconf find -lsocket -lnsl automatically
29692 - deal with hardware word alignment
29693 - make uname() work (solaris has a different return convention)
29694 - switch from using signal() to sigaction()
29695 o Preliminary work on reputation system:
29696 - Keep statistics on success/fail of connect attempts; they're published
29697 by kill -USR1 currently.
29698 - Add a RunTesting option to try to learn link state by creating test
29699 circuits, even when SocksPort is off.
29700 - Remove unused open circuits when there are too many.
29703 Changes in version 0.0.2 - 2004-03-19
29704 - Include strlcpy and strlcat for safer string ops
29705 - define INADDR_NONE so we compile (but still not run) on solaris
29708 Changes in version 0.0.2pre27 - 2004-03-14
29710 - Allow internal tor networks (we were rejecting internal IPs,
29711 now we allow them if they're set explicitly).
29712 - And fix a few endian issues.
29715 Changes in version 0.0.2pre26 - 2004-03-14
29717 - If a stream times out after 15s without a connected cell, don't
29718 try that circuit again: try a new one.
29719 - Retry streams at most 4 times. Then give up.
29720 - When a dirserver gets a descriptor from an unknown router, it
29721 logs its fingerprint (so the dirserver operator can choose to
29722 accept it even without mail from the server operator).
29723 - Inform unapproved servers when we reject their descriptors.
29724 - Make tor build on Windows again. It works as a client, who knows
29726 - Clearer instructions in the torrc for how to set up a server.
29727 - Be more efficient about reading fd's when our global token bucket
29728 (used for rate limiting) becomes empty.
29730 - Stop asserting that computers always go forward in time. It's
29732 - When we sent a cell (e.g. destroy) and then marked an OR connection
29733 expired, we might close it before finishing a flush if the other
29734 side isn't reading right then.
29735 - Don't allow dirservers to start if they haven't defined
29736 RecommendedVersions
29737 - We were caching transient dns failures. Oops.
29738 - Prevent servers from publishing an internal IP as their address.
29739 - Address a strcat vulnerability in circuit.c
29742 Changes in version 0.0.2pre25 - 2004-03-04
29744 - Put the OR's IP in its router descriptor, not its fqdn. That way
29745 we'll stop being stalled by gethostbyname for nodes with flaky dns,
29748 - If the user typed in an address that didn't resolve, the server
29752 Changes in version 0.0.2pre24 - 2004-03-03
29754 - Fix an assertion failure in dns.c, where we were trying to dequeue
29755 a pending dns resolve even if it wasn't pending
29756 - Fix a spurious socks5 warning about still trying to write after the
29757 connection is finished.
29758 - Hold certain marked_for_close connections open until they're finished
29759 flushing, rather than losing bytes by closing them too early.
29760 - Correctly report the reason for ending a stream
29761 - Remove some duplicate calls to connection_mark_for_close
29762 - Put switch_id and start_daemon earlier in the boot sequence, so it
29763 will actually try to chdir() to options.DataDirectory
29764 - Make 'make test' exit(1) if a test fails; fix some unit tests
29765 - Make tor fail when you use a config option it doesn't know about,
29766 rather than warn and continue.
29767 - Make --version work
29768 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
29771 Changes in version 0.0.2pre23 - 2004-02-29
29773 - Print a statement when the first circ is finished, so the user
29774 knows it's working.
29775 - If a relay cell is unrecognized at the end of the circuit,
29776 send back a destroy. (So attacks to mutate cells are more
29778 - New config option 'excludenodes' to avoid certain nodes for circuits.
29779 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
29780 so you can collect coredumps there.
29782 - Fix a bug in tls flushing where sometimes data got wedged and
29783 didn't flush until more data got sent. Hopefully this bug was
29784 a big factor in the random delays we were seeing.
29785 - Make 'connected' cells include the resolved IP, so the client
29786 dns cache actually gets populated.
29787 - Disallow changing from ORPort=0 to ORPort>0 on hup.
29788 - When we time-out on a stream and detach from the circuit, send an
29789 end cell down it first.
29790 - Only warn about an unknown router (in exitnodes, entrynodes,
29791 excludenodes) after we've fetched a directory.
29794 Changes in version 0.0.2pre22 - 2004-02-26
29796 - Servers publish less revealing uname information in descriptors.
29797 - More memory tracking and assertions, to crash more usefully when
29799 - If the default torrc isn't there, just use some default defaults.
29800 Plus provide an internal dirservers file if they don't have one.
29801 - When the user tries to use Tor as an http proxy, give them an http
29802 501 failure explaining that we're a socks proxy.
29803 - Dump a new router.desc on hup, to help confused people who change
29804 their exit policies and then wonder why router.desc doesn't reflect
29806 - Clean up the generic tor.sh init script that we ship with.
29808 - If the exit stream is pending on the resolve, and a destroy arrives,
29809 then the stream wasn't getting removed from the pending list. I
29810 think this was the one causing recent server crashes.
29811 - Use a more robust poll on OSX 10.3, since their poll is flaky.
29812 - When it couldn't resolve any dirservers, it was useless from then on.
29813 Now it reloads the RouterFile (or default dirservers) if it has no
29815 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
29816 many users don't even *have* a /usr/local/sbin/.
29819 Changes in version 0.0.2pre21 - 2004-02-18
29821 - There's a ChangeLog file that actually reflects the changelog.
29822 - There's a 'torify' wrapper script, with an accompanying
29823 tor-tsocks.conf, that simplifies the process of using tsocks for
29824 tor. It even has a man page.
29825 - The tor binary gets installed to sbin rather than bin now.
29826 - Retry streams where the connected cell hasn't arrived in 15 seconds
29827 - Clean up exit policy handling -- get the default out of the torrc,
29828 so we can update it without forcing each server operator to fix
29830 - Allow imaps and pop3s in default exit policy
29832 - Prevent picking middleman nodes as the last node in the circuit
29835 Changes in version 0.0.2pre20 - 2004-01-30
29837 - We now have a deb package, and it's in debian unstable. Go to
29838 it, apt-getters. :)
29839 - I've split the TotalBandwidth option into BandwidthRate (how many
29840 bytes per second you want to allow, long-term) and
29841 BandwidthBurst (how many bytes you will allow at once before the cap
29842 kicks in). This better token bucket approach lets you, say, set
29843 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
29844 performance while not exceeding your monthly bandwidth quota.
29845 - Push out a tls record's worth of data once you've got it, rather
29846 than waiting until you've read everything waiting to be read. This
29847 may improve performance by pipelining better. We'll see.
29848 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
29849 from failed circuits (if they haven't been connected yet) and attach
29851 - Expire old streams that haven't managed to connect. Some day we'll
29852 have them reattach to new circuits instead.
29855 - Fix several memory leaks that were causing servers to become bloated
29857 - Fix a few very rare assert triggers. A few more remain.
29858 - Setuid to User _before_ complaining about running as root.
29861 Changes in version 0.0.2pre19 - 2004-01-07
29863 - Fix deadlock condition in dns farm. We were telling a child to die by
29864 closing the parent's file descriptor to him. But newer children were
29865 inheriting the open file descriptor from the parent, and since they
29866 weren't closing it, the socket never closed, so the child never read
29867 eof, so he never knew to exit. Similarly, dns workers were holding
29868 open other sockets, leading to all sorts of chaos.
29869 - New cleaner daemon() code for forking and backgrounding.
29870 - If you log to a file, it now prints an entry at the top of the
29871 logfile so you know it's working.
29872 - The onionskin challenge length was 30 bytes longer than necessary.
29873 - Started to patch up the spec so it's not quite so out of date.
29876 Changes in version 0.0.2pre18 - 2004-01-02
29878 - Fix endian issues with the 'integrity' field in the relay header.
29879 - Fix a potential bug where connections in state
29880 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
29883 Changes in version 0.0.2pre17 - 2003-12-30
29885 - Made --debuglogfile (or any second log file, actually) work.
29886 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
29887 adversary could force us into an infinite loop.
29890 - Each onionskin handshake now includes a hash of the computed key,
29891 to prove the server's identity and help perfect forward secrecy.
29892 - Changed cell size from 256 to 512 bytes (working toward compatibility
29894 - Changed cell length to 2 bytes, and moved it to the relay header.
29895 - Implemented end-to-end integrity checking for the payloads of
29897 - Separated streamid from 'recognized' (otherwise circuits will get
29898 messed up when we try to have streams exit from the middle). We
29899 use the integrity-checking to confirm that a cell is addressed to
29901 - Randomize the initial circid and streamid values, so an adversary who
29902 breaks into a node can't learn how many circuits or streams have
29906 Changes in version 0.0.2pre16 - 2003-12-14
29908 - Fixed a bug that made HUP trigger an assert
29909 - Fixed a bug where a circuit that immediately failed wasn't being
29910 counted as a failed circuit in counting retries.
29913 - Now we close the circuit when we get a truncated cell: otherwise we're
29914 open to an anonymity attack where a bad node in the path truncates
29915 the circuit and then we open streams at him.
29916 - Add port ranges to exit policies
29917 - Add a conservative default exit policy
29918 - Warn if you're running tor as root
29919 - on HUP, retry OR connections and close/rebind listeners
29920 - options.EntryNodes: try these nodes first when picking the first node
29921 - options.ExitNodes: if your best choices happen to include any of
29922 your preferred exit nodes, you choose among just those preferred
29924 - options.ExcludedNodes: nodes that are never picked in path building
29927 Changes in version 0.0.2pre15 - 2003-12-03
29928 o Robustness and bugfixes:
29929 - Sometimes clients would cache incorrect DNS resolves, which would
29930 really screw things up.
29931 - An OP that goes offline would slowly leak all its sockets and stop
29933 - A wide variety of bugfixes in exit node selection, exit policy
29934 handling, and processing pending streams when a new circuit is
29936 - Pick nodes for a path only from those the directory says are up
29937 - Choose randomly from all running dirservers, not always the first one
29938 - Increase allowed http header size for directory fetch.
29939 - Stop writing to stderr (if we're daemonized it will be closed).
29940 - Enable -g always, so cores will be more useful to me.
29941 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
29944 - Wrote a man page. It lists commonly used options.
29947 - Change default loglevel to warn.
29948 - Make PidFile default to null rather than littering in your CWD.
29949 - OnionRouter config option is now obsolete. Instead it just checks
29951 - Moved to a single unified torrc file for both clients and servers.
29954 Changes in version 0.0.2pre14 - 2003-11-29
29955 o Robustness and bugfixes:
29956 - Force the admin to make the DataDirectory himself
29957 - to get ownership/permissions right
29958 - so clients no longer make a DataDirectory and then never use it
29959 - fix bug where a client who was offline for 45 minutes would never
29960 pull down a directory again
29961 - fix (or at least hide really well) the dns assert bug that was
29962 causing server crashes
29963 - warnings and improved robustness wrt clockskew for certs
29964 - use the native daemon(3) to daemonize, when available
29965 - exit if bind() fails
29966 - exit if neither socksport nor orport is defined
29967 - include our own tor_timegm (Win32 doesn't have its own)
29968 - bugfix for win32 with lots of connections
29969 - fix minor bias in PRNG
29970 - make dirserver more robust to corrupt cached directory
29973 - Wrote the design document (woo)
29975 o Circuit building and exit policies:
29976 - Circuits no longer try to use nodes that the directory has told them
29978 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
29979 bitcounts (18.0.0.0/8).
29980 - Make AP connections standby for a circuit if no suitable circuit
29981 exists, rather than failing
29982 - Circuits choose exit node based on addr/port, exit policies, and
29983 which AP connections are standing by
29984 - Bump min pathlen from 2 to 3
29985 - Relay end cells have a payload to describe why the stream ended.
29986 - If the stream failed because of exit policy, try again with a new
29988 - Clients have a dns cache to remember resolved addresses.
29989 - Notice more quickly when we have no working circuits
29992 - APPort is now called SocksPort
29993 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
29995 - RecommendedVersions is now a config variable rather than
29996 hardcoded (for dirservers)
29997 - Reloads config on HUP
29998 - Usage info on -h or --help
29999 - If you set User and Group config vars, it'll setu/gid to them.
30002 Changes in version 0.0.2pre13 - 2003-10-19
30003 o General stability:
30004 - SSL_write no longer fails when it returns WANTWRITE and the number
30005 of bytes in the buf has changed by the next SSL_write call.
30006 - Fix segfault fetching directory when network is down
30007 - Fix a variety of minor memory leaks
30008 - Dirservers reload the fingerprints file on HUP, so I don't have
30009 to take down the network when I approve a new router
30010 - Default server config file has explicit Address line to specify fqdn
30013 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
30014 - Make listener connections not ever alloc bufs
30016 o Autoconf improvements:
30017 - don't clobber an external CFLAGS in ./configure
30018 - Make install now works
30019 - create var/lib/tor on make install
30020 - autocreate a tor.sh initscript to help distribs
30021 - autocreate the torrc and sample-server-torrc with correct paths
30023 o Log files and Daemonizing now work:
30024 - If --DebugLogFile is specified, log to it at -l debug
30025 - If --LogFile is specified, use it instead of commandline
30026 - If --RunAsDaemon is set, tor forks and backgrounds on startup